Chargeback and Dispute Management: A Merchant Playbook
By PayEurasia Team · 2 October 2026 · 6 min read
Last updated 2 October 2026
Why disputes happen, how they differ across cards, wallets and bank rails, and the evidence and process that keep dispute ratios under control.
Every merchant who accepts payments at scale eventually faces disputes. In South Asia the mechanics differ from the card-centric model most guides describe: wallet and bank-rail payments rarely have formal chargeback schemes, but they do have complaint channels, reversals and regulator escalations that behave like chargebacks in practice. This playbook explains how disputes arise, how to answer them, and how to keep them from threatening your processing relationships.
What this guide covers
- How disputes differ by payment method
- The root causes behind most disputes
- Building an evidence pack
- Response workflows and deadlines
- Keeping ratios below thresholds
- Prevention through product design
How disputes differ by payment method
Card payments carry a formal chargeback lifecycle with reason codes, response windows and arbitration. Mobile wallets such as bKash, Nagad, JazzCash, Easypaisa, eSewa and Khalti instead route complaints through the wallet operator, which may freeze or reverse funds while it investigates. UPI complaints flow through the payer's bank and NPCI's dispute framework, with defined turnaround times.
Bank transfers over IMPS, NEFT, BEFTN or Raast are hardest to reverse once credited, but a payer bank can still raise a recall on fraud grounds. Treat every rail as disputable; only the process and the timeline change.
The root causes behind most disputes
Genuine fraud is a minority of disputes. Most come from payers who do not recognise the descriptor on their statement, customers who were never told how long a service would take to activate, and failed deliveries that support never resolved. Friendly fraud — a real customer disputing a real payment — sits in between and grows whenever refunds are hard to obtain.
Map each dispute to a cause category. Within a month the pattern is usually obvious, and the fix is often a clearer descriptor, a confirmation message or a faster refund path rather than a risk rule.
Building an evidence pack
Winning a dispute depends on evidence prepared before the dispute exists. Capture the payer identifier, IP address, device fingerprint, timestamps, the terms accepted at checkout and proof of delivery or service usage. Store them against the transaction ID so they can be exported in one step.
Keep responses factual and short. Reviewers read hundreds of cases; a one-page summary with a timeline and three attached proofs beats a long narrative every time.
Response workflows and deadlines
Every dispute should enter a queue with an owner, a due date and a status. Response windows on card schemes can be as short as a week, and wallet operators may decide within days. Missing a deadline is an automatic loss regardless of merit.
Automate the parts that do not need judgement: fetching evidence, drafting the response template and alerting on approaching deadlines. Reserve human time for deciding whether to accept or contest.
Keeping ratios below thresholds
Providers monitor dispute ratios — disputes divided by transactions over a period. Crossing monitoring thresholds leads to reserves, higher fees or termination. Track your ratio daily per method and per provider so you see a spike before your provider does.
Proactive refunds are the most effective lever. Refunding a clearly unhappy customer costs the transaction value; losing a dispute costs that value plus a fee plus ratio damage. For high-risk verticals, where thresholds are tighter, this trade-off matters even more.
Prevention through product design
Use a recognisable descriptor that matches your brand. Send an instant confirmation with the amount, the merchant name and a support contact. Publish a clear refund policy and honour it quickly. Each of these removes a common reason for a payer to contact their bank instead of you.
Combine that with the controls described in the payment fraud prevention guide so genuine fraud is stopped before settlement rather than disputed afterwards.
Frequently asked questions
Do mobile wallets have chargebacks?
Not in the card-scheme sense, but wallet operators handle complaints and can freeze or reverse funds. The practical effect is similar, so treat wallet complaints with the same discipline.
What dispute ratio is safe?
It depends on the provider and vertical, but most monitoring programmes start acting well below 1%. Aim to stay as low as possible and track the trend daily.
Should I contest every dispute?
No. Contest when your evidence is strong. Accepting weak cases quickly saves time and keeps focus on the cases you can win.
How long should evidence be kept?
At least as long as the longest dispute window on any method you accept, and longer where local record-keeping rules require it.
Can refunds reduce disputes?
Yes. A fast, visible refund path is the single most effective way to prevent friendly-fraud disputes.
Where PayEurasia fits
PayEurasia runs local collections and payouts across Bangladesh, India, Pakistan and Nepal behind a single API, one reconciliation model and one settlement relationship. Provider redundancy sits behind that API, so an acquirer outage degrades approval rates instead of stopping money movement.
If you are scoping an integration, the API overview explains the object model and the API documentation covers authentication, webhooks and error handling. Merchant onboarding lists the documents needed before a live account is issued, and Compliance sets out the KYC and AML framework applied to every merchant.
Related guides
Talk to PayEurasia
Working in a high-risk vertical across South Asia? We can probably help.
Request integration →