Short answer: use a private object and issue a short-lived presigned URL only when a receipt export is ready. The URL grants temporary download access without making the bucket public, so the original file can remain available for audit while the link expires.
For a receipt pipeline, the important choice is not which storage API has the cleverest upload helper. It is where you draw the trust boundary. A worker writes the original receipt, your application authorizes the person asking for it, and a storage service signs a URL for the final transfer. Large-file throughput belongs on that last path; application servers should not proxy every byte.
What should the first useful download look like?
I start with three checks: the object is private, the URL has an expiration chosen for the actual download window, and the downloader sends no storage-control-plane credentials to the URL. That is the smallest useful experiment.…