Chargeback Reason Code
A chargeback reason code is the category the card scheme assigns to a dispute — fraud, authorisation, processing error, or consumer dispute (not received, not as described, cancelled recurring, credit not processed) — which tells the merchant why the payment was reversed, what evidence would win a representment, and how long everyone has. Visa's are numbers like 10.4 and 13.1, Mastercard's like 4837 and 4853.
- Also known as
- Reason code, Dispute reason code, Chargeback category
- Used at
- every chargeback notification, the merchant's dispute dashboard, representment strategy, and the fraud-ratio programmes (which count only fraud codes)
- Binding
- the scheme rules attach to each code the conditions the issuer must meet to file it, the evidence the merchant may submit, and the time limits — typically 120 days from the transaction for the cardholder to dispute, 30 days for the merchant to respond
- Typical families (Visa)
- 10.x fraud (10.4 card-absent fraud is the commonest code in e-commerce); 11.x authorisation (no authorisation, declined); 12.x processing errors (duplicate, wrong amount, late presentment); 13.x consumer disputes (13.1 merchandise not received, 13.2 cancelled recurring, 13.3 not as described, 13.6 credit not processed); Mastercard's 4837 (fraud), 4853 (cardholder dispute), 4834 (point-of-interaction error), 4808 (authorisation) map to the same families
- Typical reading
- a high share of fraud codes with matching logins is friendly fraud; 13.2 is a cancellation problem; 13.1 is a delivery-proof problem; 12.x is the merchant's own processing
- Parties
- the issuer (which chooses the code from the cardholder's complaint), the scheme (which defines them), the acquirer and the merchant (which respond by code)
How reason codes work in practice
A cardholder tells her bank she does not recognise a charge; the bank files a chargeback under the fraud code (Visa 10.4). The merchant's dispute team reads the code and knows the rule: to win, it must show the cardholder made the purchase — under Compelling Evidence 3.0, two prior undisputed transactions from the same device or account, or delivery to the cardholder's address with a signature. A different cardholder says the item never arrived: 13.1, and the winning evidence is tracked delivery. A third cancelled a subscription and was charged again: 13.2, and the merchant needs the cancellation record showing no cancellation before the charge. Each code is a question, and the merchant's evidence is the answer.
The codes also reveal the business. A merchant whose disputes are 70% fraud codes but whose logs show the cardholders logged in has a friendly-fraud problem and a representment opportunity; one whose disputes are 13.1 has a fulfilment or a shipping-notification problem; one with 12.x has a payments-processing problem of its own. The fraud codes alone count toward the schemes' fraud-monitoring programmes, so an issuer's choice of code — fraud when the cardholder says "I don't recognise this" — shapes the merchant's regulatory position.
For dispute-management vendors the code taxonomy is the product: automated evidence assembly by code, and the win rates by code are the sales pitch.
Example
A marketplace analyses 2,400 chargebacks in a quarter by code: 58% Visa 10.4 / Mastercard 4837 fraud; 22% 13.1 not received; 11% 13.3 not as described; 6% 13.6 credit not processed; 3% processing errors. Cross-referenced with its data: 80% of the "fraud" disputes come from accounts with a login in the disputed week — friendly fraud, representable under CE 3.0 with a projected 40% win rate; the 13.1 disputes cluster on three sellers with no tracked shipping — a seller policy, not a dispute problem; the 13.6 cases are refunds it processed and the issuer did not see — a descriptor and timing fix. Six months later: fraud-code disputes down 30% through representment deterrence, 13.1 down 60% after mandatory tracking, 13.6 near zero. The code mix was the diagnosis.
Common mistakes
- Treating every chargeback the same and submitting the same evidence for every code. - Ignoring the code mix, which is a free diagnostic of the business. - Missing the response window because the notification's code was not understood. - Assuming a fraud code means third-party fraud when the login says otherwise. - Building fraud tooling for a dispute problem that is really fulfilment.