06.05 · Concept
Chargebacks & the Evidence That Wins
Respond to a dispute with the evidence that actually decides it, and say what your dispute ratio costs you before anyone has won or lost.
Chargebacks are network-governed disputes with fees, deadlines, reason codes and monitoring consequences, not just refund arguments. Winning depends on matching compact evidence to the stated reason: authorisation, delivery, refund handling or fulfilment. The dispute ratio also has a cost before liability is decided, because processors and networks price the risk itself.
What this lesson answers
- what evidence wins a card chargeback dispute
- how does chargeback ratio cost money before losing
- what should a dispute response packet include
Notes
A chargeback is not just an angry customer asking for a refund; it is a card-network dispute process with rules, deadlines, reason codes, fees, and monitoring thresholds. The merchant may eventually win or lose the case, but the dispute can already cost money through chargeback fees, operational work, reserve requirements, higher processor pricing, or placement in network monitoring programs. That means your dispute ratio matters as an operating metric, not only as a legal outcome metric.
The evidence that wins is evidence that answers the specific reason code.
References
Common questions
- What evidence should I send for a chargeback?
- Send evidence that directly answers the reason code. For unauthorised use, show account history, device signals, delivery address, login activity, IP location or authentication results. For non-receipt, show carrier tracking and fulfilment records. For refund disputes, show refund timestamps and processor references. Do not send a generic log dump.
- Why can chargebacks cost money even if we win later?
- A chargeback can trigger fees, support work, reserves, processor repricing and network monitoring before the final decision. The ecosystem treats disputes as a risk signal, not only as confirmed merchant losses. A rising dispute ratio can therefore affect margins and payment operations even when individual cases are later reversed.
- How should engineers structure a dispute response?
- Treat it like a concise incident report. Start with the reason code, list the relevant identifiers, build a timeline of payment, account, fulfilment and refund events, then attach only the logs or documents that prove the key state transitions. The reviewer should not have to infer the argument from raw screenshots.
Short definition: what is Chargebacks & the Evidence That Wins?