Skip to main content
Ship an ebook, a font pack, a desktop binary, or a 9GB model checkpoint, and Macropay turns it into a customer entitlement. Attach files to a product as a File Downloads benefit and every buyer or active subscriber gets a private, signed URL the moment their order clears — no storage to host, no download gating to build, no S3 to babysit. And because Macropay is the merchant of record, the sale that unlocks the file is already tax-handled: we calculate and remit sales tax / VAT worldwide and sit on the customer’s statement as the seller, so you ship bytes instead of chasing compliance.

​
What you get

A File Downloads benefit can hold multiple files. Buyers of the product receive every enabled file in the benefit as a single bundle of downloads.

​
Create a File Downloads benefit

1

Open Benefits

Go to Benefits in the Dashboard sidebar.
2

Add a benefit

Click + Add Benefit.
3

Pick the type

Choose File Downloads as the Type.
4

Upload your files

Drag and drop files onto the dropzone (Feed me some bytes), or click it to open a file browser. Uploads stream straight into our storage as you add them.
Attach the benefit to any product — one-time or subscription — and it’s live. Every new order grants the files; cancelling a subscription revokes them.

​
Manage the files in a benefit

Click the filename to edit it inline. The new name is what customers see on their download.
Drag and drop files into the order you want them presented to customers.
Open the contextual menu (the dots) and choose Copy SHA-256 Checksum. Publish it alongside your release so customers can confirm the bytes they downloaded match what you shipped.
Open the contextual menu and choose to disable the file. This is the safe way to retire a file without destroying it — see access rules below.
Open the contextual menu and choose Delete.
Deleting a file is permanent — and it cuts off current customers too. A delete removes the file from Macropay and our S3 storage entirely (only the metadata is retained). Active subscribers and past buyers lose access immediately. If you only want to stop new grants, disable the file instead.

​
How access changes propagate

Enabling, disabling, adding, and deleting files each behave differently for people who already own the benefit. Here’s the full matrix:
Disabling preserves legacy access on purpose. Someone who bought before you disabled a file keeps their copy — useful for grandfathering older releases while you steer new buyers to the current version.
Re-enabling or adding files is retroactive. The moment you add a new file or re-enable an old one, every current customer and subscriber with the benefit is granted access. Treat the benefit as the live source of truth for what buyers can download — shipping a v2 asset is as simple as uploading it.

​
Pair downloads with usage or agent billing

File downloads cover the “deliver the artifact” half of a product. For products where value accrues after delivery — an agent customers run, an API they call, a model they query — combine the download with usage-based billing so the file is the on-ramp and metered usage is the revenue. A few patterns that work well:
  • SDK or CLI + metered API — ship the binary as a download, then meter calls against the AI proxy or your own ingested events.
  • Agent distribution — hand over an agent bundle as a file, then bill its real work via the Signals API and attach value receipts that certify the outcomes it produced.
  • Templates + credits — give away a starter file for free, then sell prepaid credits the customer burns down as they use the tooling.
In every case Macropay stays the merchant of record across the bundle: one checkout, one tax-handled order, and the file plus any metered usage settle under the same flat fee.