Short answer: the storage API pattern I choose for private marketplace files uses backend-issued presigned URLs for direct browser uploads, server-side auth and validation, then a separate object HEAD check before readiness; callback webhooks are only for asynchronous processing.
The browser should move the bytes, but it shouldn't decide ownership. This keeps large-file traffic away from the application process while preserving an authorization point that can answer a plain question: may this user write this exact key?
One rule matters most: an upload response is not a readiness signal.
Keep that boundary.
Why is completion a separate signal?
A marketplace has at least two states that look deceptively similar: the browser finished sending bytes, and the application accepted an object for download. Collapsing them creates the storage equivalent of acknowledging a queue message before the side effect commits.…