Why digital goods get underwritten differently
A game top-up, an episode unlock, a monthly subscription and a mobile recharge have one thing in common: nothing is shipped. The customer pays, a balance changes on a server, and the transaction is finished. From a risk desk that looks like a problem. There is no tracking number, no signed delivery note and no physical return, so when a cardholder later tells their bank they do not recognise the charge, the merchant has very little a bank will accept as proof of delivery. Add an impulse purchase pattern, a high share of card-not-present traffic, refund requests that arrive weeks later, and minors using a parent's card, and you have a profile most acquirers price and monitor differently from a normal shop. The practical consequence is rarely outright rejection. It is conditions. Providers will board digital goods merchants, but they attach tighter dispute thresholds, longer reserve periods, lower initial volume caps and stricter category approval. Knowing that before you shop around saves you discovering the conditions after the integration is already built.
- Assume it is your category, not your company, that gets underwritten, and describe what you sell in plain words on the application.
- Expect lower initial monthly volume caps and a review after the first one to three months of live traffic.
- Budget for a higher effective cost than an ordinary e-commerce store of the same size.
- Keep the billing descriptor recognisable, because a charge the customer does not recognise is a dispute waiting to happen.
Rolling reserve: the clause that decides your cash flow
A rolling reserve is not a fee. It is a share of your processing volume that the provider holds back for a set period and releases later, and it is the contract term that most often surprises digital goods merchants. The mechanics are simple. The provider withholds an agreed percentage of each settlement batch, keeps it for an agreed number of days, then releases it, usually on a rolling basis so that once the first period has elapsed you receive current money plus the reserve from the earlier period. What matters is not the percentage on its own but the product of percentage, holding period and your volume. A small percentage held for six months can tie up more cash than a large percentage held for sixty days. Reserves come in other shapes too: an upfront deposit before you process anything, and a capped reserve that stops withholding once a ceiling is reached. Ask which shape is on the table, what triggers a review, and what happens to the balance if you close the account.
- Get the reserve percentage, the holding period and the release schedule into the contract itself, not into an email from a salesperson.
- Model the steady-state balance before signing: monthly volume multiplied by the reserve percentage multiplied by the months held.
- Ask what evidence triggers a reduction, such as several months of dispute ratios below an agreed level.
- Confirm what happens to the reserve balance after your final transaction if you decide to leave.
Chargeback ratios and the threshold you are actually measured against
Merchants often manage to a vague rule of thumb about staying under one per cent, but the schemes publish their own numbers and change them. Visa consolidated its fraud and dispute monitoring into a single programme, the Visa Acquirer Monitoring Program, and reduced the excessive merchant threshold in several regions to 150 basis points from April 2026, alongside a minimum monthly count of fraud and dispute events. Acquirer-level thresholds are lower still. The ratio covers card-not-present activity and combines fraud reports with disputes, so one problem transaction can register more than once. Two consequences matter commercially. First, your acquirer may impose its own lower ceiling on you, because your numbers roll up into its portfolio. Second, disputes resolved through pre-dispute tools before they become formal chargebacks may be excluded, which is why prevention tooling has a direct financial return rather than being a nice-to-have. Public pricing is only a first filter. Actual pricing changes with country, industry, volume, settlement currency, integration method and contract terms. Confirm against the provider's official pricing page or a written quote before you go live, and apply the same discipline to risk terms.
- Ask which monitoring programme applies to your region and what threshold your contract will hold you to.
- Track fraud reports separately from disputes, because both can feed the same combined ratio.
- Turn on pre-dispute alert handling if your provider offers it, and measure how many disputes get deflected.
- Review your ratio monthly against the ceiling in your contract rather than against an industry average.
Refund windows and the evidence you will wish you kept
Digital goods disputes are winnable, but only if the file is assembled at the moment of delivery rather than thirty days later when a bank asks for it. Build the record into the product flow rather than leaving it as a manual task for support. At minimum you want the account identifier the value was delivered to, a timestamped server-side record of that delivery, the IP address and device data captured at checkout, the version of the checkout the customer saw including price and currency, the authentication result if a step-up was used, and the refund policy exactly as it was displayed. Session replays help in some cases. So does a short, clear refund window that is easier to use than a bank dispute, because a large share of disputes are refund requests that found no obvious door. Keep the records for at least as long as the scheme allows a dispute to be filed, and make sure support can retrieve them without calling an engineer.
- Log delivery server-side against the account it was delivered to, not just against the order number.
- Store the exact price, currency and refund policy text shown at checkout alongside the order.
- Set a refund window that is short enough to be clear and long enough to be fair, then publish it on the checkout page.
- Give support a one-click refund in your own admin so a customer never has to escalate to their bank.
Why instant payments fit low-ticket digital goods
Account-to-account rails were built for a different job than cards, and the differences line up unusually well with digital goods. Confirmation arrives in seconds, so you can release content without holding a buffer. There is no card network in the middle, so the cost structure differs and is often lower. Most importantly, the money moves because the payer instructed their own bank to send it, which means there is no cardholder dispute right of the kind that produces chargebacks. That does not mean zero risk. Push-payment fraud and mistaken transfers exist, and some systems run a return mechanism with its own deadlines and eligibility rules. But the shape of the risk is different, and for a two-dollar episode unlock it is a better shape. Instant rails also suit the ticket size. India's UPI was designed around phone numbers and virtual addresses rather than sixteen-digit card numbers, which removes a lot of typing from a mobile checkout and a lot of failed attempts with it.
- Use instant rails wherever your customers already have them, and keep cards as the fallback for everyone else.
- Release content only on a server-to-server confirmation, never on a success screen rendered by the client.
- Check whether the rail runs a return or claim mechanism and what deadlines apply to your merchant account.
- Show prices in local currency, because a currency surprise at the payment step is a common reason for an abandoned top-up.
Which local methods convert for low-ticket digital goods
There is no universal list, but there is a reliable pattern: the methods that convert are the ones your customers used yesterday to pay for something small. In Brazil that means Pix first, with Boleto as the cash route for people who prefer to pay away from a screen. In Mexico it is SPEI for bank users and OXXO for cash. In India, UPI is not one option among several, it is the option, and RuPay covers local cardholders. In the Philippines, GCash and Maya cover most mobile users, while in Indonesia a single QRIS code reaches every major wallet. Thailand runs PromptPay alongside wallet brands, and Vietnam runs MoMo, ZaloPay and Viettel Money. Where digital goods are sold inside an app store, the store's own billing rules apply and you cannot route around them, so treat the web as a separate channel with its own stack. Start with two methods per market, measure payment-method share, and add a third only when the data shows customers looking for it.
- Pick one instant rail and one wallet or cash method per market, then let your own payment-method share data choose the third.
- Check that the rail supports recurring or tokenised payments before you build a subscription product on it.
- Confirm minimum ticket sizes, because some rails make very small payments uneconomic once fixed costs are included.
- Order the methods on the checkout by what your customers actually use, not by the order your provider lists them.
Questions to put to a provider before you sign
Ask these in writing and compare the answers side by side. Is my specific category approved, and by which legal entity in the group? What dispute threshold is in my contract, and who monitors it? Is there a reserve, what shape is it, and what triggers a review? How many days run from capture to funds available, and do weekends or local holidays change that? Which currencies can I settle in, and can I hold the local currency instead of being converted automatically? Does the platform support the recurring model my product needs, and on which methods? Is there a refund API, and are refunds charged? What fields come back in the settlement report so that finance can reconcile without manual work? And what are the exit terms: notice period, data export, and how long balances are held after the last transaction. Vague answers on any of these are themselves an answer.
- Get category approval in writing and name the legal entity that is actually contracting with you.
- Ask for a sample settlement report before you integrate rather than after.
- Test the full refund path in the sandbox, including partial refunds and refunds issued after settlement.
- Confirm the exit terms, including notice period and how long balances are held once the final transaction clears.
Questions merchants ask
Why is my game or short-drama app treated as high risk by payment providers?
Because there is nothing to ship and therefore nothing that proves delivery. When a cardholder disputes a charge, a merchant selling physical goods can show a tracking number and a signature, while a digital merchant usually cannot. Providers respond with conditions rather than refusals: tighter dispute thresholds, reserves, lower volume caps and closer category review.
What is a rolling reserve and how long does it usually last?
It is a percentage of each settlement batch that the provider withholds and releases later, on a rolling basis. Holding periods vary widely by industry and risk profile, and what matters is the combination of percentage, holding period and your monthly volume. Ask for all three in the contract, plus what evidence would trigger a reduction and how the balance is handled if you close the account. A capped reserve stops withholding once a ceiling is reached, which is easier to plan around.
Do instant payments like Pix and UPI have chargebacks?
Not in the card sense. The payer instructs their own bank to send the money, so there is no cardholder dispute right to reverse it. The risk instead takes other forms: push-payment fraud, mistaken transfers, and formal return mechanisms that operate on their own deadlines and eligibility rules. Check what your provider and the local scheme allow before assuming a payment is final.
Can I run a subscription on cash vouchers like Boleto or OXXO?
Not as an automatic recurring charge. A voucher is generated for one payment and must be taken somewhere and paid, so the customer has to act every period. Merchants handle this with a due-date reminder flow, a visible pending-renewal state and a grace period. For true automatic renewal you generally need a card on file or a rail that supports mandates.
Do I need a local company to sell digital goods in Brazil or India?
Often not, but it depends on the method, the country and the provider. Many cross-border merchants reach Pix or UPI through a provider that contracts with them offshore, while direct local acquiring usually requires a local entity and bank account. Confirm in writing which legal entity will contract with you and which one will settle to you.
What is the fastest way to reduce chargebacks on digital goods?
Make refunding easier than disputing. Use a recognisable billing descriptor, show price and currency clearly, send a receipt immediately, and put a self-service refund in the customer's account area. Then add delivery evidence logging and pre-dispute alert handling. Most disputes are refund requests that could not find a door. Track which reason codes dominate and fix the underlying cause rather than only defending the cases.