Refund, dispute, chargeback: three different things
Merchants lose money by treating these as the same event. A refund is you giving money back, on your own terms, at your own speed, usually keeping the customer relationship and paying only the processing cost you agreed. A dispute is a cardholder asking their issuer to look at a transaction; it may still be resolved in your favour. A chargeback is the formal reversal, where funds are pulled from your account and you may pay a fee on top, whether or not you win. The commercial difference is large. A refund costs you the order and a small fee. A chargeback costs you the order, a fee, staff time to respond, and a mark on the ratio your acquirer monitors. That ratio is what determines whether your pricing, your reserve or your account itself survives the next review. The practical lesson is unglamorous: make refunding easier than disputing.
- Publish a refund policy at checkout and make it short enough that customers actually read it.
- Give support a one-click refund so a customer never has to escalate to their bank.
- Track refunds and chargebacks separately, because they have very different costs and consequences.
- Monitor your dispute ratio monthly against the ceiling written into your contract.
How a card chargeback actually runs
The sequence is broadly the same across the schemes. The cardholder contacts their issuer with a complaint. The issuer files a dispute, funds are provisionally reversed, and your acquirer or provider notifies you. You get a window to respond with evidence, after which the issuer either accepts your case, rejects it, or escalates to a further stage. Timelines run in weeks rather than days, and the filing window for the cardholder can be long, so a dispute can arrive long after you closed the books on that month. Merchants are also measured, not just charged. Visa consolidated its fraud and dispute monitoring into a single programme and reduced the excessive merchant threshold in several regions to 150 basis points from April 2026, with a minimum monthly count. Acquirer-level thresholds are lower, which means your acquirer will watch you closely. Disputes resolved before they become formal chargebacks may not count against you, so prevention tooling pays directly.
- Respond inside the stated window every time, even when you think the case is unwinnable.
- Assign one owner for disputes so nothing expires in a shared inbox.
- Use pre-dispute alerts if your provider offers them, and measure how many disputes get deflected.
- Review the reason codes monthly, because they point directly at the operational fix.
Why most local methods have no chargeback
Card dispute rights exist because a card transaction is an authorisation given to a merchant to pull funds. Local payment methods mostly work the other way round: the payer instructs their own bank or wallet to push money to you. Brazil's Pix is the clearest case, operated by the central bank and settled in seconds, where the payer's instruction is the authorisation. India's UPI works the same way, with the customer approving a collect request in their own app. Cash vouchers are even simpler, because no account is debited at all; the customer hands over banknotes. Once the money has moved, there is no scheme rule that lets the payer pull it back unilaterally. That is why merchants selling digital goods often prefer these rails: the dispute exposure that dominates their cost base simply is not there. It is also why the same merchants need a different risk plan rather than no risk plan.
- Do not copy your card-side dispute playbook onto local rails, because the mechanics do not transfer.
- Check each rail individually, since some wallet products layer their own buyer protection on top.
- Track the claim or return mechanisms that do exist, and assign an owner to respond to them.
- Remember that no chargeback does not mean no cost, because refunds and fraud still exist.
The risk you get instead: irreversible payments and fraud claims
Removing chargebacks removes one risk and reveals another. Push-payment fraud, where a customer is tricked into sending money, produces a victim who will come to you even though the scheme gives them no reversal right. Account takeover in a wallet works the same way. Mistaken payments, duplicate payments and payments made by a child on a parent's phone all land on your support desk regardless of what the rulebook says. Some systems formalise a response: Brazil's Pix has a special return mechanism for cases with a founded suspicion of fraud or operational failure, with defined request and analysis windows and explicit exclusions for commercial disagreements. The merchant-side consequence is that funds in your account can be blocked while a claim is assessed. So the practical posture is to keep strong fraud controls on instant rails, keep a clear voluntary refund path, and treat an early response as cheaper than an escalation.
- Run fraud screening on instant payments, not only on cards, because the exposure has moved.
- Respond to fraud claims quickly, since blocked funds cost you more than a fast refund does.
- Learn the local return mechanism's deadlines and exclusions before you need them.
- Keep a voluntary refund path for mistaken payments, because it protects the relationship cheaply.
The evidence to keep
Evidence only helps if it exists at the moment it is needed, which means it has to be produced automatically by your systems rather than assembled by hand. For physical goods keep the order record, the delivery confirmation with signature or scan, the tracking number and the carrier's status history, and any customer communication about the order. For digital goods keep the account identifier the value was delivered to, a timestamped server-side delivery log, the IP address and device data from checkout, the authentication result, and the price, currency and refund policy as displayed. Across both, keep the billing descriptor the customer saw on their statement, because an unrecognisable descriptor is one of the most common causes of a dispute. Retain records for at least as long as the scheme allows a dispute to be filed, and make them retrievable by support without an engineer.
- Store the billing descriptor with the order so you can prove the charge was recognisable.
- Log delivery server-side with the recipient identifier, not just against the order number.
- Capture the checkout version, price, currency and refund policy text as the customer saw them.
- Make the evidence pack retrievable by a support agent in one action, without engineering help.
How reserves work
A reserve is money the provider holds back from your settlements as a buffer against future disputes, refunds or claims. It is not a fee and it remains yours, but it changes your cash flow in ways that new merchants consistently underestimate. A rolling reserve withholds a percentage of each settlement batch and releases it after an agreed holding period, so after the first period you receive current money plus the earlier reserve. An upfront reserve asks for a lump sum before you process anything. A capped reserve withholds until a ceiling is reached and then stops. The number that matters is not the percentage but the steady-state balance: monthly volume multiplied by the percentage multiplied by the holding period in months. Ask what triggers a review and a reduction, get the terms into the contract rather than an email, and confirm how long the balance is held after your final transaction if you leave.
- Calculate the steady-state reserve balance before you sign, not after the first settlement.
- Ask what performance evidence triggers a reduction, such as a sustained low dispute ratio.
- Get reserve terms into the contract itself, including the release schedule and the post-termination hold.
- Model the reserve against your working capital, because it is cash you cannot spend meanwhile.
Questions merchants ask
What is the difference between a refund and a chargeback?
A refund is you returning money on your own terms, usually keeping the customer and paying only agreed processing costs. A chargeback is a formal reversal initiated through the cardholder's issuer, where funds leave your account, a fee is often applied, and a mark lands on the dispute ratio your acquirer monitors. Choose dynamic whenever orders must be matched to payments without a person reading a bank statement.
Do Pix, UPI or cash voucher payments have chargebacks?
Generally no. Those methods are push payments, where the payer instructs their own bank or hands over cash, so there is no cardholder reversal right. You still face push-payment fraud, mistaken payments and, on some rails, a formal return mechanism with its own deadlines and exclusions. Ask your provider which claim or return process applies to your account and who responds to it.
What chargeback ratio should I stay under?
Follow the threshold written into your contract rather than an industry rule of thumb. Visa consolidated fraud and dispute monitoring into one programme and reduced the excessive merchant threshold in several regions to 150 basis points from April 2026, subject to a minimum monthly count, while acquirer-level thresholds are lower still. Your acquirer may hold you to a tighter number than the scheme does.
How long do I have to respond to a chargeback?
Response windows are set by the scheme and passed through your acquirer or provider, and they are short enough to miss if a notification sits in a shared inbox. Assign a named owner, set an internal deadline earlier than the external one, and respond every time, even on cases you expect to lose.
Is a rolling reserve the same as a fee?
No. A reserve is your money withheld for a period and then released, while a fee is gone. The cost of a reserve is the cash you cannot use meanwhile. Work out the steady-state balance by multiplying monthly volume by the reserve percentage by the number of months held. Ask what performance record would trigger a review, and get the reduction terms into the contract.
What evidence wins a digital goods dispute?
A server-side delivery log tied to the account that received the value, the IP address and device data from checkout, the price and currency as displayed, the authentication result, and a recognisable billing descriptor. Support should be able to assemble this in one action, without waiting for an engineer. Add the customer's communication history, because a documented refund offer often changes the outcome.