A prepaid balance with a wholesale code supplier is unsecured credit you extend to them: the money sits on their books, and if they fail, you queue with their other creditors. The working rules follow from that fact: start at the supplier’s minimum, never hold more than you can write off, and keep the steady-state balance near one week of order volume.
Vetting before the first transfer is its own discipline, covered in how to vet a gift card supplier. This article covers what comes after: sizing, monitoring and growing the balance.
Why suppliers require prepayment
Digital codes are bearer goods. Once delivered, a code can be redeemed in seconds by whoever holds it, and there is no repossession and no clawback if the buyer’s payment later bounces or reverses. A supplier shipping codes against card payments would be underwriting chargeback fraud on products that vanish instantly.
So the industry settled on prepay: you fund a balance by bank transfer, orders draw it down, and the supplier’s exposure to you is zero. Prepayment is normal and not, by itself, a warning sign. What varies between suppliers is everything around it: minimums, top-up friction, and how they behave when you ask for money back.
Sizing: three rules
Start at the minimum. The first deposit is the price of a live test, not working capital. Fund the smallest amount the supplier accepts, run real orders, redeem a few codes yourself, and only then add more.
Cap it at your write-off tolerance. At any moment the balance should be an amount you could lose entirely, with anger but without damage. If losing it would threaten payroll, it is too big, whatever the volume argument says.
In steady state, hold about one week of order volume. Enough that a busy weekend does not drain you, small enough that your exposure stays modest against monthly turnover. If you sell 5,000 in codes a week, a balance around 5,000 with a mid-week top-up does the job.
Monitor the balance like uptime
An empty balance does not fail loudly. Orders start returning insufficient-balance errors, your storefront keeps taking payments it cannot fulfil, and the first you hear of it is a customer asking where their code is. The insufficient-balance case is one of the standard order failure modes worth handling in code, but the better fix is never reaching it.
Set two thresholds. A warning level, around two to three days of typical volume, that prompts a human to schedule a top-up. A critical level, under one day, that alerts loudly and, if you sell high-value products, pauses the risky SKUs. Most suppliers expose the balance through an API or dashboard; poll it on a schedule rather than checking it when something breaks.
Top-ups: cadence and rails
Match the top-up rhythm to how money moves in practice. Bank transfers clear in hours domestically but can take days across borders, and weekends are where balances die: a Friday evening sales spike against a Monday transfer is two days of lost orders. If your volume swings, top up earlier than the arithmetic strictly requires.
Keep every top-up reconciled: the transfer from your bank, the credit on the supplier’s ledger, and the orders drawn against it should tie out line by line. The routine is the same one described in reconciliation for digital goods, and a balance that does not tie out is a conversation to have while the discrepancy is still small.
The path to credit terms
Prepay is where relationships start, not where they must stay. After months of steady volume, clean payment history and no dispute drama, many distributors will move good buyers to partial credit: net-7 or net-14 terms on a share of the volume, sometimes against a standing deposit. Ask once you have a record to point at, and bring numbers: monthly volume, order count, dispute rate. Credit terms shift the counterparty risk from you to them, which is why they are earned slowly.
Warning signs
- Pressure to fund far beyond your volume “for better pricing”. A supplier pushing a new buyer towards a balance many times their weekly volume is borrowing from you, not selling to you.
- Sudden increases in the minimum balance or minimum top-up, especially with short notice.
- Friction when you ask to withdraw or reduce the balance. A healthy supplier treats a drawdown as routine; a struggling one stalls, because your deposit may already be someone else’s payout.
- Balance discrepancies that keep resolving in the supplier’s favour.
Any one of these deserves a question. Two together deserve a smaller balance.
Frequently asked questions
How much should I deposit with a gift card supplier?
Start with the supplier’s minimum and treat it as the price of a live test. Once orders and redemptions run clean, grow the balance in steps towards roughly one week of your order volume, and never hold more than you could write off entirely if the supplier failed tomorrow.
Why do code suppliers require prepayment?
Because codes are bearer goods: once delivered they can be redeemed instantly and cannot be recovered, so a reversed payment leaves the supplier with a pure loss. A prepaid balance removes that exposure. It is standard practice across wholesale digital goods and not, by itself, a sign of a weak supplier.
How do I get credit terms with a distributor?
Build a record first: several months of consistent volume, on-time top-ups and a low dispute rate. Then ask for partial terms, such as net-7 on a share of your volume, rather than full credit at once. Distributors extend terms against demonstrated history, so bring your numbers to the conversation.
What happens to a prepaid balance if the code supplier fails?
You queue with the supplier’s other unsecured creditors, and in practice you should expect to recover little or nothing. The balance sits on their books, not yours, and no code inventory backs it. That is why the sizing rule is blunt: never hold more than you could write off entirely, and treat friction when you ask to withdraw funds as a signal to shrink the balance.
How do I set low-balance alerts for a supplier prepaid account?
Set two thresholds and poll the balance on a schedule through the supplier’s API or dashboard. A warning level at two to three days of typical order volume prompts a human to schedule a top-up; a critical level under one day alerts loudly and, for high-value products, pauses the risky SKUs. An empty balance fails silently through insufficient-balance errors, so never wait for a customer complaint to find it.