Chargeback Management Services - Dispute Response Jul/ 21/ 2026 | 0
Dispute Response reviews thousands of chargeback notifications, and the most expensive mistake we see isn’t a weak rebuttal. It’s a merchant answering the wrong accusation — sending a refund policy to fight a fraud claim, or delivery proof to fight a processing error.
The reason code on your notification is not decoration. It’s the formal charge against you, and it dictates which evidence can win, which deadline applies, and whether the case is worth fighting at all.
Here’s the good news: you don’t need to memorize a hundred codes. Every code across all four networks collapses into four families — fraud, authorization, processing errors, and cardholder disputes. Learn the four families and you can read any code in seconds.
This guide gives you the decoder: the key codes for Visa, Mastercard, American Express, and Discover, what each family accuses you of, and exactly how to respond to each one.
Four Networks, Dozens of Codes, Four Accusations
When Visa rebuilt its dispute system in 2018 (Visa Claims Resolution), it collapsed 22 legacy reason codes into four numbered categories — and quietly confirmed what dispute analysts already knew. There are only four things a cardholder or bank can accuse you of:
- Fraud — “The cardholder never authorized this.”
- Authorization — “The merchant processed this without valid approval.”
- Processing error — “The merchant charged it wrong.”
- Cardholder dispute — “The purchase was real, but something went wrong with it.”
Mastercard, Amex, and Discover use different numbering, but every code they issue maps onto the same four accusations. That mapping is the skill. The tables below do it for you.
Visa Reason Codes (10.x – 13.x)
Visa’s first digit pair tells you the family instantly.
| Family | Key codes | The accusation |
| 10.x Fraud | 10.1–10.3 (card-present/EMV), 10.4 card-absent fraud, 10.5 fraud monitoring | “I didn’t make this purchase” |
| 11.x Authorization | 11.1 card recovery, 11.2 declined auth, 11.3 no auth | “You processed without valid authorization” |
| 12.x Processing errors | 12.1 late presentment, 12.5 incorrect amount, 12.6 duplicate/paid by other means | “You charged it wrong” |
| 13.x Cardholder disputes | 13.1 not received, 13.2 cancelled recurring, 13.3 not as described, 13.6 credit not processed, 13.7 cancelled merchandise | “The purchase went wrong” |
For most online merchants, two codes dominate the queue: 10.4 (card-absent fraud — where most friendly fraud hides) and 13.1 (merchandise not received).
Mastercard Reason Codes (48xx)
Mastercard consolidated aggressively, so a few codes carry almost all the volume.
| Family | Key codes | The accusation |
| Fraud | 4837 no cardholder authorization, 4849 questionable activity, 4870/4871 chip liability shift | “I didn’t make this purchase” |
| Authorization | 4808 authorization-related | “No valid approval” |
| Processing errors | 4834 point-of-interaction error | “You charged it wrong” |
| Cardholder disputes | 4853 cardholder dispute (the catch-all) | “The purchase went wrong” |
Watch 4853 closely. Mastercard folded not-received, not-as-described, cancelled-recurring, and credit-not-processed claims into this single code — so you must read the dispute’s supporting detail to know which specific accusation you’re answering.
American Express Codes (Letter Prefixes)
Amex acts as both network and issuer, and its letters map cleanly:
| Prefix | Family | Examples |
| F | Fraud | F24 no cardmember authorization, F29 card not present |
| A | Authorization | A02 no valid authorization, A08 approval expired |
| P | Processing errors | P05 incorrect amount, P08 duplicate charge |
| C | Cardholder disputes | C08 not received, C28 cancelled recurring, C31 not as described |
One Amex quirk worth respecting: because Amex is the issuer, inquiries often arrive before a formal chargeback. Answer the inquiry well and the chargeback never happens.
Discover Codes (Two-Letter Codes)
| Family | Key codes |
| Fraud | UA02 card-not-present fraud, UA01 card-present, UA05/UA06 chip fraud |
| Authorization | Codes for expired/invalid or missing authorization |
| Processing errors | DP duplicate processing, LP late presentation, AW altered amount |
| Cardholder disputes | RG non-receipt of goods, RM quality dispute, RN2 credit not processed, AP recurring payments |
Different alphabet, same four families.
How to Respond — by Family, Not by Code
This is where the decoder pays off, because your response strategy is set at the family level:
- Fraud codes (10.4, 4837, F29, UA02): Fight with authentication and history — 3-D Secure results, AVS/CVV matches, IP and device logs, and Visa’s Compelling Evidence 3.0 purchase history. Our guide to winning a chargeback covers the exact CE 3.0 requirements.
- Cardholder dispute codes (13.x, 4853, C-codes, RG/RM): Fight with documents — signed delivery, cancellation logs, product listings, correspondence. Then run the packet through the 7-step representment process.
- Authorization and processing codes (11.x/12.x, 4808/4834, A/P codes, DP/LP): Usually don’t fight. These describe your operational errors — duplicates, late presentment, missing auths — and the bank has the settlement records to prove it. Refund fast where you’re wrong, and fix the process that caused it. If the ticket is small either way, our RDR vs. traditional chargebacks breakdown shows when auto-resolution beats any fight.
Two families reward evidence. Two families reward operational honesty. Merchants who treat all four the same lose money in both directions.
“But the Code Is Wrong — This Isn’t Fraud”
Correct, and it happens constantly. Visa has estimated that as many as three in four disputes may be friendly fraud: real purchases filed under fraud codes because “I don’t recognize this” is the easiest box for a cardholder to tick.
Here’s the mindset shift: the reason code isn’t the truth — it’s the accusation you must answer. You don’t win a 10.4 by arguing the customer is lying. You win it by answering the fraud claim on its own terms: this device, this IP, this address has purchased from you before, undisputed. The evidence tells the truth. Your job is to aim it at the code.
Turn Your Codes Into a Prevention Map
Reason codes are also your cheapest analytics tool. Tally your last 90 days of disputes by code and the pattern will point at a fixable process.
A Dispute Response client — a meal-kit subscription service — found that 13.2/4853 “cancelled recurring” claims made up 44% of their chargebacks. The cause wasn’t fraud. Their cancellation flow required a phone call. They added one-click online cancellation and clear renewal emails, and that category fell by more than half within two billing cycles — cheaper than winning those disputes would ever have been.
Every code cluster has an equivalent fix: 13.1 clusters point at delivery confirmation gaps, 12.6 duplicates point at retry logic, descriptor confusion feeds 10.4.
The takeaway: Read the first digits (or letter), identify the family, and you know your strategy: authenticate against fraud codes, document against dispute codes, concede and repair on authorization and processing codes — and tally everything, because your reason-code mix is a map of what to fix.
Conclusion
Merchants drown in reason codes because they read them one at a time, mid-panic, with a deadline running. Read them as four families instead, and every notification arrives pre-sorted: this is the accusation, this is the evidence, this is whether we fight.
Bookmark this page for the next notification — and if you’d rather have every incoming dispute decoded, triaged, and answered for you, Dispute Response does exactly that. Get a free analysis of your reason-code mix at dispute-response.com and see what your last 90 days of codes say about where your revenue is leaking.
