Automatic delivery for digital products: how it works

The promise of a digital product is that the buyer has it seconds after paying. Manual delivery breaks that promise every time you sleep, travel or get busy, and it invites mistakes: the same key sent to two people, a file link pasted into the wrong email. A digital delivery system does three jobs: wait for a payment that’s really confirmed, hand over exactly what was bought, and take back what it can when an order is refunded. Here’s how each works, product by product.

What “payment confirmed” should mean

Instant delivery after payment is only safe if “payment” means money that really arrived. On ShopFast an order is created, and delivered, only when all of this holds:

• the payment comes from the provider itself, checked by its signature where it signs and always read back with your credentials;
• it’s for the checkout ShopFast created;
• it’s complete, not pending, partly paid or held;
• the amount and currency are exactly the checkout’s total, so a payment a cent short delivers nothing;
• it hasn’t been counted before, so a notification sent twice never makes a second order.

A checkout that only ran out of time still delivers when its exact total arrives late, such as a pending PayPal payment or slow crypto confirmations. Prices always come from your store, never from the buyer’s browser. The details are in how every payment is checked.

Automatic delivery for digital products, type by type

Product	What the buyer gets once the payment is confirmed
License keys	One unused key from the option’s pool, never handed to anyone else
Files	Private files through signed download links, with a link expiry and a download limit you set
Memberships	Access for as long as the membership runs
Discord roles	The role, the moment they pay
Telegram access	A single-use, expiring invite only they can use
Bundles	Every product inside, each delivered its own way
Message	A text you write for every buyer, such as instructions or an invite link
Dynamic delivery	Whatever your own system returns at the moment of sale

Buyers find what they bought in three places: the order page, which shows it the moment payment confirms; the receipt email, which carries it too; and their account library, which keeps every order. A lost email never means a lost product.

Auto deliver license keys

Keys are where automation matters most, because a key can never go to two people. Every product option has its own key pool. Keys are sealed (encrypted) as you add them, and a key you paste twice is dropped. When a payment confirms, one unused key is taken from the pool and marked sold, so two buyers paying at the same moment still get different keys. An option can also draw from a shared pool when its own runs out.

Each option has a low-stock threshold that sends you a stock alert before the pool runs dry. When a key fails later, buyers press Key not working? on their order page and, within your replacement policy, get a fresh key from the same pool while the old one is revoked. The full setup is in how to sell license keys, and the same applies to game keys.

Deliver files after payment

Files are private on ShopFast. Each order gets its own signed download links, with an expiry and a download limit you set, so a link shared in a forum stops working instead of becoming a free mirror. A full refund stops the order’s links working.

Files change, and buyers who paid for version 1 expect version 2. Catalog → Updates posts a changelog, with a new file if you have one, to everyone who owns the product, by email, Discord DM and Telegram, with filters by option and purchase date. It shows under “What’s new” in the buyer’s library (updates to owners). See how this fits selling ebooks and selling software.

Access that starts and ends by itself

Some products are access, not a file. Discord roles are granted the moment the buyer pays and removed on a refund or when a membership ends. Telegram access sends a single-use invite, valid for 24 hours by default, that only the buyer can use. Access ends with the option’s duration, after a set number of days, or never, and it’s removed on a refund or a chargeback (Telegram access).

Nobody on your team adds or removes members by hand. More in selling Discord roles and selling Telegram channel access.

When delivery should wait

Automatic doesn’t mean unconditional. A good delivery system knows when to hold back:

• Fraud holds. Fraud Shield holds orders flagged at payment: they’re paid, but nothing is delivered until you approve them, and Why held? explains the decision (Fraud Shield).
• Payments you confirm by hand. Gift card payments are delivered after you redeem the code, and skins payments after the trade is confirmed.
• Products that are down. With a product’s status set to Down, auto-pause can stop its sales until it’s fixed, so nobody pays for something that doesn’t work (product status).

Holding back at the right moment is also how you avoid most chargebacks; see how to prevent chargebacks on digital goods.

Connect delivery to your own system

If what you sell is created on demand, such as an access code from your own service or a key your server generates, dynamic delivery lets a product fetch what it hands over from your own system at the moment of sale (dynamic delivery). Signed webhooks tell your other systems about each order as it happens (webhooks).

Test it before a buyer does

Simulate first sale on Get started runs a real order through checkout and delivery with a TEST- key. Store Test mode runs for 1, 24 or 72 hours, and its test orders use TEST- keys, never touch your real key pool and never count in sales or payouts (get started). For the bigger picture of setting up a store, read how to sell digital products.