Chargeback Playbook: Match Evidence to Reason Codes and Win More Disputes

The process itself is not complicated: the cardholder disputes with the issuing bank, the issuer notifies the acquirer, the merchant submits evidence within the deadline, and the card network decides. What actually decides the outcome is whether your documents map onto that specific reason code and whether they arrive before the deadline. For the process overview see the Refund and Chargeback Handling Guide; this article is about execution.

1. Understand the three time windows

1.1 The merchant response window

The window between receiving a chargeback notice and submitting evidence varies by card network and acquirer, typically from several business days to around twenty. The acquirer states a firm cutoff in the notice, and that date governs; do not estimate from memory. Missing it effectively means forfeiting.

1.2 Representment

After you submit, the case goes to review. Success here is not about arguing well but about letting a reviewer see supporting proof within seconds, so ordering, labelling and clarity matter far more than length.

1.3 Pre-arbitration and arbitration

Even a won representment can be disputed again, moving to a higher tier with materially higher cost and effort. For small-ticket orders, decide whether pursuing further is worth the cost rather than worth the principle.

2. Evidence by dispute type

Reason code systems are updated periodically. The table groups disputes by type and lists representative codes for orientation. Always confirm current code definitions against the network's rules and the code description your acquirer provides.

Dispute type Representative codes Core evidence Supporting evidence
Goods or services not received Visa 13.1, Mastercard 4855, Amex C08 Tracking number plus carrier delivery record with signature or delivery scan Customer receipt confirmation, shipping notification, buyer communication
Not as described or damaged Visa 13.3, Amex C31 or C32 Product page screenshots, quality control records, packaging specification Side-by-side comparison of buyer photos, sampling records from comparable orders
Unauthorised or fraud Visa 10.4, Mastercard 4837 or 4863, Amex F29 3DS result, AVS and CVV match results, IP and device fingerprint, account history Prior successful orders on the same card, registration and login logs, address consistency
Duplicate or incorrect amount Visa 12.5 or 12.6, Amex P05 Transaction records matched to order values, refund records Reconciliation logs, support transcripts
Cancelled subscription still charged Visa 13.2, Amex C28 Cancellation record with time, channel and operator Cancellation confirmation email, cancellation clause in the terms, login and action logs
Refund not processed Visa 13.6, Amex C02 Refund initiation date, refund receipt, bank processing timelines Refund notification email, reconciliation documents

A useful rule: evidence must answer when, who and what. Material with inconsistent timestamps is often worse than no material at all.

3. Building the evidence package

3.1 Start with a reusable base

Template the identity and order layer: order number, purchase time, amount, currency, shipping details, IP, device information, payment method. Each dispute then only needs variables swapped, which speeds up response considerably.

3.2 Add business-specific documents

  • Physical goods: the delivery chain matters most, especially last-mile dispatch and signature;
  • Digital goods and services: delivery logs, activation records, usage records;
  • Subscriptions: visibility of the cancellation path, confirmation, and consent records;
  • High tickets: contracts, quotations, correspondence.

3.3 Presentation

One PDF structured as claim, evidence, page reference, with the conclusion on the first page. Reviewers have limited time, so put the single most persuasive page first.

4. Prevention tools beat representment

  • Visa: Rapid Dispute Resolution can defuse a dispute with a refund before it is formally filed, and Order Insight lets merchants see order detail before a dispute and clarify proactively. Both cut chargeback rates directly.
  • Mastercard: Ethoca Alerts provides pre-dispute alerts, and Consumer Clarity gives issuers transaction context before a dispute.
  • 3DS2 and liability shift: fraud-type transactions authenticated through 3DS may shift liability to the issuer, which materially improves outcomes on unauthorised disputes.

Availability depends on your acquirer and markets, so confirm fees and eligibility criteria before enabling.

5. Turn chargeback rate into an early-warning metric

5.1 Fix the definition

Counting disputes over transactions and disputes over value produce very different numbers. Pick one definition for internal reporting, keep it stable, and align it with your acquirer's.

5.2 Attribute by cause, not just total

Split monthly chargebacks into fraud, service, logistics and operational categories to see whether the fix belongs in risk rules, support process or a logistics partner. See Payment Fraud Prevention Strategies for categorisation.

5.3 Set an alert line, not a ceiling

Trigger internal alerts well before you approach a network monitoring threshold. By the time an acquirer sends a remediation notice, the best adjustment window has usually passed.

6. Four common mistakes

First, treating chargebacks as a support issue; they are simultaneously a risk, logistics and product-description issue. Second, submitting screenshots without structure, which is close to submitting nothing. Third, appealing everything regardless of value, where small tickets cost more to fight than they are worth. Fourth, ignoring prevention, since tools such as RDR and Ethoca remove more disputes than representment wins.

For integration and account strategy see the Cross-Border Payment Selection Matrix; for risk differences between acquirers see Stripe Pros and Cons and the Adyen Guide. More payment options are listed under Payment.

Source: 16IDC original. Product capabilities, pricing and eligibility requirements follow usa.visa.com / www.mastercard.us and related official documentation and contract terms.