What every chargeback reason code actually tells you, how the four card networks organize chargeback reason codes, which categories are growing fastest, and what to do when one lands
A chargeback reason code is the short alphanumeric label a card issuer attaches to a dispute to say why the cardholder is challenging a charge. It is the single most useful piece of information on a dispute, because it dictates the deadline, the evidence that will win, and whether the smart move is to fight or refund. Read the code correctly and the rest of the response follows; misread it and you waste a representment you could have won.
The catch is that each network runs its own system. Visa, Mastercard, American Express, and Discover use different formats and group disputes differently, and the codes change as the networks consolidate and modernize their rules. This guide maps the four systems, shows the representative codes merchants see most, explains which categories are climbing and why, and connects each code to the right action. For the full program that keeps disputes from being filed in the first place, pair it with our guide to chargeback prevention in ecommerce.
What Is a Chargeback Reason Code?
Chargeback reason codes are a network-assigned identifier that categorizes the reason for a payment dispute. When a cardholder contests a charge, their issuing bank files the chargeback under a specific code, and that code travels with the dispute through the network to the merchant’s acquirer. The code determines three things that matter operationally: the response window, the compelling evidence the network will accept, and the dispute category, which tells you whether you are looking at true fraud, an authorization or processing problem, or a consumer dispute.
Chargeback reason codes generally sort into four buckets, whatever the network calls them: fraud, authorization errors, processing errors, and consumer (cardholder) disputes. The fastest-growing bucket is no longer classic third-party fraud. It is consumer disputes and fraud claims driven by first-party (friendly) fraud, where a real customer disputes a charge they actually made.
How the Four Card Networks Organize Reason Codes
The networks share the same underlying logic but express it differently:
- Visa uses a two-part numeric format tied to four dispute categories (10, 11, 12, 13) under Visa Claims Resolution and the current Visa dispute rules.
- Mastercard uses four-digit codes (the 48xx series) and has been consolidating several older codes into broader ones.
- American Express uses letter-prefixed codes grouped by category (fraud, authorization, processing error, card member dispute).
- Discover uses two-letter codes grouped into similar categories.
Because Amex and Discover both issue cards and run their own networks, merchants dispute directly with the network rather than through a separate issuer, but the reason-code logic still applies.
Visa Reason Codes: The Four Dispute Categories
Visa organizes every dispute into one of four categories, with a specific condition code beneath it. Per Visa’s Dispute Management Guidelines for Merchants and the Visa Core Rules, the categories and the codes merchants see most often are:
| Category | Common code | What it means |
|---|---|---|
| 10: Fraud | 10.4 | Other Fraud, Card-Absent Environment (the most common ecommerce fraud dispute) |
| 11: Authorization | 11.3 | No Authorization obtained for the transaction |
| 12: Processing Errors | 12.5 | Incorrect Amount charged |
| 12: Processing Errors | 12.6 | Duplicate Processing (charged twice) |
| 13: Consumer Disputes | 13.1 | Merchandise or Services Not Received |
| 13: Consumer Disputes | 13.2 | Cancelled Recurring Transaction |
| 13: Consumer Disputes | 13.3 | Not as Described or Defective Merchandise or Services |
| 13: Consumer Disputes | 13.6 | Credit Not Processed |
| 13: Consumer Disputes | 13.7 | Cancelled Merchandise or Services |
Category 13 is where most ecommerce disputes now cluster, and it is also where first-party fraud hides, because a “not received” or “not as described” claim from a customer who did receive a working product is functionally friendly fraud dressed as a consumer dispute.
Mastercard Reason Codes
Mastercard uses four-digit chargeback reason codes and has been folding older, narrower codes into broader ones. Per the Mastercard Chargeback Guide, the codes merchants encounter most are:
| Code | What it means |
|---|---|
| 4837 | No Cardholder Authorization (cardholder says they did not authorize the charge) |
| 4863 | Cardholder Does Not Recognize, Potential Fraud |
| 4853 | Cardholder Dispute (the broad consumer-dispute code that is absorbing several older ones) |
| 4855 | Goods or Services Not Provided (being consolidated into 4853) |
| 4834 | Point-of-Interaction Error (for example, a duplicate charge or incorrect amount) |
| 4870 | Chip Liability Shift (counterfeit fraud on a non-EMV transaction) |
The consolidation trend matters: as Mastercard routes more disputes through 4853, the code alone tells you less, and the underlying claim detail plus the transaction history tell you more. That shift rewards merchants who capture order-time evidence rather than reacting to the code in isolation.
American Express and Discover Reason Codes
American Express groups its letter-prefixed codes by category: F codes for fraud, A codes for authorization, P codes for processing errors, and C codes for card member disputes (for example, a “goods or services not received” or “not as described” claim). Discover uses two-letter codes sorted into the same broad categories.
Because both networks act as their own issuers, merchants respond to them directly, and the response requirements are defined in each network’s merchant dispute guidelines. Treat the category, not just the specific code, as your first read: a fraud-category code calls for authentication and delivery evidence, while a card member dispute calls for proof the product matched its description and was delivered as promised. Always confirm the current code and its evidence requirements against the network’s own documentation, since these are revised periodically.
Which Reason Codes Are Growing, and Why
The mix has shifted decisively toward consumer disputes and first-party fraud claims. Mastercard’s research on first-party trust reports that first-party (friendly) fraud now accounts for more than 45% of all chargebacks, and Visa’s friendly fraud insights estimate it makes up as much as 30% of disputes for high-volume online merchants. The Merchant Risk Council’s Global eCommerce Payments and Fraud Report now ranks refund and policy abuse as the top fraud threat in ecommerce, ahead of traditional payment fraud.
Two forces explain the trend. First, genuine fraud has trained consumers that disputing a charge is easy, so more of them reach for the dispute button as a refund shortcut, which lands as a consumer-dispute or fraud-claim code even though the customer received the goods. Second, the FTC reported roughly $16 billion in consumer fraud losses for 2025, the highest on record, which keeps dispute volume inflated across the board. The practical takeaway: the reason codes rising fastest are exactly the ones where the code says “fraud” or “not received” but the truth is a customer working a policy.
What to Do With a Reason Code
A reason code is an instruction, not a verdict. Work it in this order:
- Read the category first. Fraud and authorization codes point to screening and authentication gaps; processing codes point to billing hygiene; consumer-dispute codes point to evidence and policy. Each has a different owner and a different fix.
- Check the deadline the code sets. Response windows differ by network and code, and they are unforgiving. Miss the window and the case is lost regardless of merit.
- Decide fight or refund on the evidence, not the emotion. Fight the cases your order-time evidence actually supports, and refund the ones it does not. Visa’s Compelling Evidence 3.0 rules, covered in our chargeback prevention guide, let merchants defeat certain fraud claims using the cardholder’s own prior purchase history.
- Match the evidence to the code. A “not received” code wants tracking and delivery confirmation; a fraud code wants device, IP, and authentication data; a “not as described” code wants product photos, listings, and policy acknowledgment.
- Feed outcomes back into prevention. If the same code keeps recurring from the same patterns, that is a screening or policy signal. For the behavioral tells that separate genuine disputes from first-party abuse, see the five signs a chargeback is actually fraud.
How Wyllo Helps
Chargeback reason codes describe disputes one at a time; the losses come from patterns that span many. Wyllo is the risk intelligence platform for commerce, built to read intent across the whole customer journey so the signal behind a reason code becomes a decision rather than a filing.
- Wyllo Chargeback Management handles dispute responses and representment end to end, matching evidence to each reason code, with chargeback protection for eligible orders.
- Wyllo Payment Fraud Protection screens transactions with AI plus expert human review, stopping the fraud that becomes tomorrow’s fraud-category disputes.
- Wyllo Claim and Policy Abuse Prevention catches the first-party abuse hiding behind consumer-dispute codes, before it converts into a chargeback.
Less reaction. More reason.
Frequently Asked Questions
What is a chargeback reason code?
A chargeback reason code is a network-assigned identifier that states why a cardholder disputed a charge. It travels with the dispute from the issuing bank to the merchant and determines the response deadline, the evidence the network will accept, and the dispute category (fraud, authorization, processing error, or consumer dispute).
What is Visa reason code 10.4?
Visa reason code 10.4 is “Other Fraud, Card-Absent Environment.” It is the most common fraud dispute in ecommerce and indicates the cardholder claims a card-not-present transaction was fraudulent. Winning it typically requires authentication data and evidence linking the cardholder to the order, such as matching device, IP, and prior purchase history.
What is Mastercard reason code 4837?
Mastercard reason code 4837 is “No Cardholder Authorization,” used when a cardholder says they did not authorize a charge. It is most often either genuine third-party fraud or a legitimate charge the cardholder failed to recognize. Delivery confirmation, authentication, and order-history evidence are central to a response.
How long do I have to respond to a chargeback?
The response window depends on the network and the specific reason code, and it is strict. Missing it forfeits the case regardless of merit. Confirm the exact deadline for each dispute against the network’s current rules, and build your workflow to respond well inside it rather than at the edge.
Which reason code is used for friendly fraud?
There is no single “friendly fraud” code, which is what makes it hard to see. First-party fraud arrives disguised under fraud codes (a cardholder falsely claiming they did not authorize a charge) and consumer-dispute codes (falsely claiming an item was not received or not as described). Detecting it means looking past the code to the customer’s history and behavior.
Do chargeback reason codes change?
Yes. The networks periodically revise, add, and consolidate codes, as Mastercard has done by folding narrower codes into 4853. Always verify the current code and its evidence requirements against the issuing network’s own documentation rather than a static list.
Bringing It Together
A chargeback reason code is the most actionable field on any dispute, but only if you read it in context. The code sets the deadline and the evidence bar; the category tells you which team owns the fix; and the trend across codes tells you where your program is leaking. With consumer-dispute and fraud-claim codes rising on the back of first-party abuse, the merchants who win are the ones who stop treating each code as an isolated filing and start connecting the pattern behind it.
Codes will keep shifting as the networks modernize their rules. The durable advantage is not memorizing every code but building the evidence and intelligence to answer any of them, and to prevent the disputes worth preventing. Start with Wyllo Chargeback Management for the dispute layer, or explore the broader Wyllo platform for connected intelligence across the full customer journey.
