How to Tailor Chargeback Evidence to Each Reason Code

Chargebacks?
No longer your problem.
Recover 4x more chargebacks and prevent up to 90% of incoming ones, powered by AI and a global network of 20,000+ merchants.
TL;DR:
- Every network uses its own code for the same complaint, such as Visa 13.1, Mastercard 4853, Amex C08, and Discover RG for non-receipt.
- Lead with the one record that answers the code, then add support; delivery proof does not answer a fraud claim.
- Fraud codes follow formal data rules: Visa CE3.0 for 10.4 and Mastercard First-Party Trust for 4837.
- Map legacy and processor labels to the current network code before choosing evidence.
- Track win rate by reason code to find the one missing record behind repeat losses.
Chargeback evidence is the transaction-specific record you submit to answer a cardholder’s dispute. Tailoring it means matching each document to the actual allegation, reason code, amount, and response requirements.
A delivery record can address non-receipt. It does not show that the cardholder authorized the payment. Start with the dispute notice, then build the response around facts you can prove. For the wider process, see our handbook on how to win chargeback disputes. Below is an evidence matrix by reason code for Visa, Mastercard, Amex, and Discover.
{{cta}}
Start With the Claim and the Response Deadline
Record these details from the case before you collect anything:
- Processor case ID and payment ID
- Card network and reason code
- Disputed amount and currency
- Submission deadline
Then read the cardholder’s narrative. A short category label may hide whether the customer disputes the whole order, one item, a renewal, or a promised credit. Use the chargeback reason-code guide for orientation, then confirm the rules in the case.
Codes belong to card networks, and similar complaints carry different codes on each network. Avoid copying a code from an old template. Set an internal review date ahead of the case response deadline.
Chargeback Evidence Matrix by Reason Code
This chargeback evidence matrix maps the most common dispute types to the code each network uses and the record that answers it first. Lead with that record, then add support.
| Dispute type | Visa | Mastercard / Amex / Discover / Lead evidence |
|---|---|---|
| Card-absent fraud | 10.4 | Mastercard: 4837, 4863 Amex: F29 Discover: UA02 Lead evidence: 3D Secure result, matching device and IP data, earlier undisputed orders |
| Not recognized | 10.4 (legacy 75) | Mastercard: 4863 Amex: F29 Discover: AA (4752) Lead evidence: Billing descriptor, order details, delivery proof tied to the cardholder |
| Not received | 13.1 | Mastercard: 4853 Amex: C08 Discover: RG (4755) Lead evidence: Carrier tracking with full delivery address, signature or photo, usage logs |
| Not as described or defective | 13.3 | Mastercard: 4853 Amex: C31, C32 Discover: RM (4553) Lead evidence: Listing shown at purchase, product photos, return policy and return records |
| Canceled recurring | 13.2 | Mastercard: 4841 or 4853 Amex: C28 Discover: AP (4541) Lead evidence: Enrollment terms, renewal notice, cancellation timeline, usage after the claimed cancellation |
| Credit not processed | 13.6 | Mastercard: 4853 Amex: C02 Discover: CD (4550) Lead evidence: Refund record with date, amount, and reference, or the policy that denies the credit |
| Duplicate or paid by other means | 12.6.1, 12.6.2 | Mastercard: 4834 Amex: P08, C14 Discover: DP (4534) Lead evidence: Two distinct orders, or proof the other payment was for a different purchase |
| Incorrect amount | 12.5 | Mastercard: 4831 Amex: P05 Discover: AW (4586) Lead evidence: Receipt showing the settled amount matched what the customer approved |
| Authorization error | 11.2, 11.3 | Mastercard: 4808 Amex: A01, A02, A08 Discover: AT (4863) Lead evidence: Authorization log with approval code, amount, and timestamp |
Sources: Chargeflow’s network guides to Visa chargeback reason codes, Mastercard chargeback reason codes, American Express chargeback reason codes, and Discover chargeback reason codes. Processors sometimes relabel codes, so check the label on your case.
Route Fraud Codes Through the Right Program
Fraud codes are the largest group, and they follow formal data rules. The compelling evidence each network accepts differs:
| Code | Program | What you must show |
|---|---|---|
| Visa 10.4 | Compelling Evidence 3.0 | 2+ undisputed sales 120 to 365 days old; 2 of 4 data elements match, one being IP or device ID |
| Mastercard 4837 | First-Party Trust | One element each for device, delivery, and additional identity |
| Amex F29 | No named program | Delivery proof, a contract, earlier undisputed sales, or matching device and IP data |
| Discover UA02 | No named program | Authorization, AVS and CVV results, 3D Secure data, device and IP history |
If a fraud case qualifies, say so in the first line of your response. If it does not, do not label it eligible. Build the case on authentication and delivery records instead.
Translate Legacy and Processor Labels
Old reports and some processors still show retired codes. Map them before you pick evidence:
- Visa legacy codes: 83 is now 10.4, 30 is 13.1, 53 is 13.3, 41 is 13.2, 85 is 13.6, 82 is 12.6.1, and 86 is 12.6.2.
- Mastercard consolidated codes: 4855, 4859, and 4860 are retired and now handled under 4853. 4807 and 4812 sit under 4808.
- Visa 12.1: late presentment moved under 11.3 in April 2024.
- Processor categories: Stripe groups codes into categories such as “fraudulent” or “product not received.” The network code still decides what evidence counts.
What Each Record Proves and Does Not Prove
Picking the right code is half the job. The other half is knowing the limits of each record:
| Dispute allegation | Useful transaction records | What those records do not establish alone |
|---|---|---|
| Unauthorized payment | Authentication results, account activity, relevant customer messages, and permitted transaction history | An address match or a successful authorization does not identify the person ordering. |
| Goods not received | Agreed delivery address, carrier delivery event, signature where available, and customer acknowledgment | A shipping label proves neither dispatch nor delivery. |
| Goods not as described | Listing shown at purchase, item specs, fulfillment record, complaint details, and return messages | Delivery alone does not answer a quality or description complaint. |
| Canceled subscription | Enrollment terms, renewal disclosure, cancellation timestamp, billing event, and service activity | A general subscription policy does not show what this customer accepted or canceled. |
| Credit not processed | Refund amount, currency, payment reference, status, and customer messages | An internal promise or a pending refund is not proof of a completed credit. |
| Duplicate or incorrect amount | Separate order IDs, payment captures, itemized receipts, and any adjustments | Two payment IDs alone do not explain why two charges were valid. |
Use this matrix as a preparation aid, not a network eligibility checklist. The fields in the processor’s response form control the submission. To make this repeatable, standardize evidence across dispute types but keep each argument specific. For a step-by-step view of automated chargeback evidence generation, see the linked guide.
{{cta}}
Build a Short, Traceable Case Narrative
Open with the disputed payment and the exact point you are answering. Then give a dated sequence: purchase, delivery or service, customer contact, and any refund or cancellation. Cite the supporting file beside each statement.
For example, a customer disputes one missing item from a three-item order. Show which items each parcel held and the delivery record for the disputed item. A scan for a different parcel leaves the claim unanswered. If the item never shipped, resolve the valid complaint instead of sending unrelated proof.
For digital goods, keep signup, login, access, download, and use as separate events. Record the timestamps without claiming that a login alone identifies the cardholder. The digital-goods dispute guide lists which records to keep before a case arrives.
A short chargeback letter template can organize the submission, but it cannot replace missing records. To shape the cover note itself, see how to write a chargeback response letter. Cut repeated policy text and claims you cannot back up.
Check Refunds and Cancellations Before Submitting
Compare support promises with payment-system events. If an agent promised a refund, find its actual status and reference. If a customer canceled, compare the request time with the billing event and the terms shown at signup. Explain any time-zone gap that changes the order of events.
Keep partial credits separate from the original amount and the remaining disputed balance. Check with the case owner before refunding a disputed payment; the double-refund workflow helps you avoid paying twice. Subscription teams should also review renewal and cancellation controls.
Prepare a Chargeback Evidence Packet the Reviewer Can Assess
Export readable records with dates, transaction references, and enough context to explain them. Label screenshots and separate original records from your notes. Hide unrelated customer data, but keep the facts the reviewer needs.
When reviewing recorded customer interactions or product walkthroughs, merchants may also need to understand the spoken details before organizing their supporting records. Adding captions can make this review process easier by turning spoken content into readable text. A Clideo subtitle generator can automatically generate subtitles, allow users to edit them, and export an SRT file for reference when reviewing video content internally.
For Stripe cases, the official response instructions allow one final submission that cannot be edited later. Reviewers do not open external content, including audio or video. Stripe also caps files at 4.5 MB in total and 19 pages for Mastercard cases.
Give one person the final check: case ID, amount, legible files, and the submission receipt. Use the internal dispute-workflow audit to find gaps between collection and submission. After you submit, the case moves into chargeback representment, and a rejected response can lead to pre-arbitration.
Measure Results by Reason Code
Tailoring only pays off if you track it. Measure your chargeback win rate by reason code and network, not as one blended number. A falling result on one code usually points to one missing record. The most common gaps are covered in our list of reasons merchants lose chargeback disputes.
Frequently Asked Questions
What are merchant chargeback reason codes?
Merchant chargeback reason codes are the alphanumeric labels a card network attaches to a dispute, such as Visa 13.1 or Mastercard 4837. Each code tells the merchant what the cardholder claims and which evidence can answer it.
What evidence should I send for Visa reason code 10.4?
For Visa reason code 10.4, send 3D Secure results, AVS and CVV matches, and device and IP data. If the card has 2 or more undisputed sales 120 to 365 days old with matching data, submit them under Compelling Evidence 3.0.
What is chargeback reason code R13?
Chargeback reason code R13 is an American Express code for No Reply. Amex charges back the sale when it does not receive the merchant’s inquiry response within the 20-day time frame.
Does delivery confirmation guarantee a chargeback win?
No. Delivery confirmation may support a non-receipt response, but its value depends on the item, address, and claim. On its own, it does not answer a fraud or quality claim.
Should I submit every document available?
No. Submit relevant, readable records that answer the claim within the processor’s limits. Extra material can hide the key facts or contradict your case narrative.
What if the evidence supports the customer’s complaint?
Accept or resolve the dispute through the processor’s workflow. Fix the underlying fulfillment, billing, or service issue instead of contesting with records that do not support your position.
Let Automation Match Evidence to Every Code
Chargeflow Automation reads the reason code on each dispute and pulls the matching records from your connected tools. You pay only on chargebacks we recover; see pricing. You can also explore Chargeflow’s automated chargeback recovery.
Recover Chargebacks Without the Paperwork
Chargeflow Automation builds and submits evidence for the chargebacks that still arrive.

Chargebacks?
No longer your problem.
Recover 4x more chargebacks and prevent up to 90% of incoming ones, powered by AI and a global network of 20,000 merchants.














.avif)


