Chargeback Reason Codes: Visa, Mastercard, Amex, Discover Guide
Visatk Team · · 9 min read · اقرأ بالعربية
Chargeback reason codes for Visa, Mastercard, Amex and Discover explained: code families, how to respond, what representment evidence wins, and prevention.

A chargeback notification usually arrives with a short code attached: 10.4, 4853, F29, UA02. That code is not a formality. It tells you what the cardholder claimed, which rules govern the dispute, what evidence can win it and how long you have to respond. Merchants who understand reason codes win more of the disputes worth fighting, accept the ones that are not, and fix the operational problems that cause chargebacks in the first place.
This guide walks through the reason code families used by Visa, Mastercard, American Express and Discover, explains how to respond, describes the evidence that works for each category, and closes with a practical prevention checklist. For quick lookups of individual codes, keep our chargeback reason codes reference open while you work.
How the Chargeback Process Works #
Although details differ by network, the lifecycle follows a common pattern:
- Dispute. The cardholder contacts their issuer and disputes a transaction.
- Chargeback. The issuer assigns a reason code and sends the chargeback through the network to your acquirer, which debits your account and notifies you.
- Response (representment). You either accept the chargeback or challenge it by submitting compelling evidence through your acquirer, within a deadline.
- Issuer review. The issuer reviews your evidence and either accepts it (you recover the funds) or continues the dispute.
- Pre-arbitration and arbitration. If the dispute continues, it may escalate. At arbitration the network makes a final decision, usually with significant fees for the losing party.
Timeframes vary by network, reason code and region, and your acquirer will normally give you a shorter internal deadline than the network's limit so it has time to process your submission. Always work to your acquirer's deadline.
Visa Reason Codes #
Visa groups disputes into four categories under its dispute resolution framework. The first number identifies the category; the decimal identifies the specific condition.
| Category | Common codes | What it means |
|---|---|---|
| 10 – Fraud | 10.1 EMV liability shift counterfeit; 10.2 EMV liability shift non-counterfeit; 10.3 other fraud card-present; 10.4 other fraud card-absent; 10.5 Visa fraud monitoring program | Cardholder says they did not authorize or participate in the transaction. |
| 11 – Authorization | 11.1 card recovery bulletin; 11.2 declined authorization; 11.3 no authorization | The transaction was processed without a valid authorization. |
| 12 – Processing errors | 12.1 late presentment; 12.2 incorrect transaction code; 12.3 incorrect currency; 12.4 incorrect account number; 12.5 incorrect amount; 12.6 duplicate processing / paid by other means; 12.7 invalid data | Something went wrong in how the transaction was submitted. |
| 13 – Consumer disputes | 13.1 merchandise/services not received; 13.2 cancelled recurring; 13.3 not as described or defective; 13.4 counterfeit merchandise; 13.5 misrepresentation; 13.6 credit not processed; 13.7 cancelled merchandise/services | Cardholder acknowledges the purchase but disputes the outcome. |
For card-absent fraud claims (10.4), Visa's Compelling Evidence 3.0 rules allow merchants to show that the cardholder previously completed undisputed transactions with matching identifiers, such as device ID or IP address plus account or shipping details. When the qualifying data is present, this can be a strong defense against "friendly fraud" claims. Check the current requirements with your acquirer, as the qualifying criteria are specific.
Mastercard Reason Codes #
Mastercard uses four-digit codes, and it has consolidated many older codes into a smaller set of broad ones.
| Code | Name | Typical scenario |
|---|---|---|
| 4808 | Authorization-related chargeback | No valid authorization, or the authorization was declined or expired. |
| 4834 | Point-of-interaction error | Duplicate processing, incorrect amount, late presentment, paid by other means. |
| 4837 | No cardholder authorization | Cardholder says they did not authorize a card-not-present transaction. |
| 4853 | Cardholder dispute | Goods not received, not as described, defective, cancelled recurring, credit not processed. |
| 4863 | Cardholder does not recognize – potential fraud | Cardholder does not recognize the transaction descriptor. |
| 4870 | Chip liability shift | Counterfeit fraud at a terminal that was not chip-capable. |
| 4871 | Chip/PIN liability shift | Lost or stolen card fraud where a PIN-capable terminal was not used. |
| 4849 | Questionable merchant activity | Merchant identified in a Mastercard fraud or compliance program. |
Code 4853 is very broad, so read the cardholder's dispute description carefully to understand which condition you are actually responding to.
American Express Reason Codes #
American Express uses alphanumeric codes grouped by a prefix letter. Because Amex often acts as both issuer and acquirer, its process can feel more direct, but evidence still matters.
| Prefix | Category | Examples |
|---|---|---|
| A | Authorization | A01 charge amount exceeds authorization; A02 no valid authorization; A08 authorization approval expired |
| C | Card member disputes | C02 credit not processed; C04 goods/services returned or refused; C05 goods/services cancelled; C08 goods/services not received; C14 paid by other means; C18 "no show" or CARDeposit cancelled; C28 cancelled recurring billing; C31 not as described; C32 damaged or defective |
| F | Fraud | F10 missing imprint; F14 missing signature; F24 no card member authorization; F29 card not present; F30 EMV counterfeit; F31 EMV lost/stolen/non-received |
| FR | Fraud full recourse programs | FR2 fraud full recourse program; FR4 immediate chargeback program; FR6 partial immediate chargeback program |
| M | Miscellaneous | M01 chargeback authorization; M10 vehicle rental capital damages; M49 vehicle rental theft or loss of use |
| P | Processing errors | P01 unassigned card number; P03 credit processed as charge; P04 charge processed as credit; P05 incorrect charge amount; P07 late submission; P08 duplicate charge; P22 non-matching card number; P23 currency discrepancy |
Discover Reason Codes #
Discover uses mostly two-letter codes, with a "UA" family for fraud.
| Group | Codes |
|---|---|
| Fraud | UA01 fraud card-present; UA02 fraud card-not-present; UA05 fraud chip counterfeit; UA06 fraud chip and PIN |
| Authorization | AT authorization noncompliance; DA declined authorization; EX expired card; NA no authorization; IN invalid card number |
| Processing | AW altered amount; CD credit/debit posted incorrectly; DP duplicate processing; IC illegible sales data; LP late presentation; PM paid by other means |
| Cardholder disputes | AA cardholder does not recognize; AP cancelled recurring; NF non-receipt of cash; RG non-receipt of goods or services; RM quality discrepancy; RN2 credit not received |
Network rules are updated periodically, so treat these tables as an orientation map and confirm current definitions with your acquirer or in the reason code lookup linked above.
Comparing the Families Across Networks #
Despite different numbering, the four networks describe the same underlying problems. Mapping them to common categories makes analytics and staff training much easier.
| Universal category | Visa | Mastercard | Amex | Discover |
|---|---|---|---|---|
| Fraud / unauthorized | 10.x | 4837, 4863, 4870, 4871 | F, FR | UA01–UA06 |
| Authorization | 11.x | 4808 | A | AT, DA, NA, EX |
| Processing errors | 12.x | 4834 | P | DP, LP, AW, PM |
| Consumer disputes | 13.x | 4853 | C | RG, RM, AP, RN2 |
How to Respond to a Chargeback #
Step 1: Decide whether to fight #
Not every chargeback should be contested. Accept the chargeback when:
- The claim is valid, for example you really did charge twice or never shipped the order.
- You lack the evidence the reason code requires.
- The transaction amount is smaller than the cost of preparing a response.
Fight when you have clear evidence that the transaction was authorized and the goods or services were delivered as described.
Step 2: Match evidence to the reason code #
The most common mistake in representment is sending a generic evidence pack. Issuers evaluate whether your evidence addresses the specific condition in the reason code.
| Dispute category | Strong evidence |
|---|---|
| Card-not-present fraud | AVS and CVV match results, 3-D Secure authentication data, device and IP data, prior undisputed orders from the same customer, account login history, delivery confirmation to the verified address, customer communication. |
| Not received | Carrier tracking with delivery confirmation to the billing or agreed address, signature where obtained, digital access or download logs with timestamps and IPs. |
| Not as described / defective | Product description at the time of sale, photos, customer correspondence, proof the item was not returned per your published return policy. |
| Cancelled recurring | Terms accepted at signup, cancellation policy, evidence the customer did not cancel per those terms, usage after the claimed cancellation date, renewal reminder emails. |
| Credit not processed | Refund policy shown at checkout, proof a refund was issued (with date and reference), or why the customer was not entitled to one. |
| Processing errors | Transaction records proving the amount, currency and date were correct; proof that two charges were separate purchases. |
| Authorization | Authorization approval code, date and amount matching the cleared transaction. |
AVS and CVV results are frequently decisive in fraud disputes. If you are unsure what a result code meant, look it up in our AVS and CVV response codes reference.
Step 3: Write a clear rebuttal letter #
- Open with a one-paragraph summary: what was purchased, when, by whom, and why the dispute is invalid.
- Reference the reason code directly and address its conditions point by point.
- Label each exhibit and refer to it in the text.
- Keep it factual and concise. Reviewers handle many cases; clarity wins.
- Redact unnecessary sensitive data, and never include full card numbers or security codes.
Step 4: Track outcomes #
Record each dispute's reason code, evidence submitted and outcome. Over time you will learn which codes you win and which you should accept immediately.
Investigating Fraud Chargebacks #
For fraud-coded disputes, determine whether you are facing true third-party fraud or "friendly fraud", where the real cardholder made the purchase but disputes it. Useful checks include:
- Compare the card's issuing country from a BIN lookup with the billing address, shipping address and IP geolocation.
- Check whether the IP was a proxy or hosting provider using the IP lookup.
- Look for prior successful orders from the same account or device.
- Review customer service contacts before and after the purchase.
The credit card fraud investigation tool helps bring those signals together for case notes.
Preventing Chargebacks #
The cheapest chargeback is the one that never happens. Prevention works on three fronts.
Reduce fraud #
- Use AVS, CVV and 3-D Secure on card-not-present transactions, with risk-based rules.
- Apply velocity limits and bot protection to stop card testing.
- Review high-risk orders before fulfillment.
Reduce confusion #
- Use a clear billing descriptor that matches your brand name, and include a contact phone or URL where supported.
- Send order confirmations, shipping notifications and receipts promptly.
- Make your refund and cancellation policies visible at checkout.
- Remind subscribers before renewals and trial conversions, and make cancelling easy.
Reduce operational errors #
- Capture only the authorized amount and settle promptly to avoid late presentment.
- Deduplicate submissions to prevent double charges.
- Process refunds quickly, and communicate refund timing to customers.
- Ensure your MCC accurately reflects your business. You can check category codes with the MCC lookup.
Use dispute alerts and pre-dispute tools #
Network and third-party pre-dispute services can notify you of disputes before they become chargebacks, or share order details with issuers so cardholders recognize their purchase. Resolving a dispute with a refund at that stage is usually better than a formal chargeback, which counts against your ratio and carries a fee.
Watch Your Chargeback Ratio #
Networks run monitoring programs that track merchants' dispute and fraud levels relative to transaction volume. Exceeding the thresholds can lead to fees, remediation plans or, in serious cases, termination of your merchant account. Track your ratio monthly by network, and investigate any upward trend early, since programs typically look at both counts and ratios.
Frequently Asked Questions #
What is the difference between a chargeback and a refund?
Can I win a fraud chargeback if the transaction used 3-D Secure?
Should I contact the customer after a chargeback?
How long do I have to respond?
Why do reason codes matter for prevention?
#chargebacks#reason codes#representment#dispute management#Visa#Mastercard
Payments, fraud-prevention and developer tools specialists.


