Chargeback Reason Codes Explained

Every chargeback that lands in your processor dashboard arrives with a reason code attached. That code is not bureaucratic noise. It is the issuing bank’s formal statement of why the dispute was filed and, more practically, the specification for what evidence you need to submit if you want to contest it.

Merchants who treat reason codes as explanations are already losing the dispute. The code is a blueprint. Each one maps to a defined evidence requirement under Visa’s and Mastercard’s operating rules. Submitting the wrong evidence for the code you received, or submitting the right evidence for the wrong code, produces the same result: a lost representment.

This guide covers the current active codes for Visa and Mastercard, what each one means in plain operational terms, and what evidence the card networks require to contest each category. American Express and Discover use separate systems covered separately.

How Visa Organizes Its Reason Codes

Visa uses a decimal numbering system that tells you the category before you read the description. The first two digits identify the category: 10 for fraud, 11 for authorization, 12 for processing errors, and 13 for consumer disputes. The digit after the decimal identifies the specific reason within that category. Visa retired code 12.1 Late Presentment in April 2024 and folded it into 11.3, bringing the current active code count to 23.

The fraud category, codes 10.1 through 10.5, covers disputes where the cardholder or issuer claims the transaction was unauthorized. These are the most serious codes from a risk management perspective because a sustained volume of fraud codes contributes directly to the ratio that Visa’s VAMP monitoring program tracks. Code 10.4, Other Fraud in a Card-Absent Environment, is the single most common code for e-commerce merchants. It is the catch-all for card-not-present fraud disputes and the code most frequently used in friendly fraud cases where the cardholder did authorize the transaction but later denies it.

The authorization category, codes 11.1 through 11.3, covers situations where something went wrong with the authorization process. Code 11.1 applies when the card was on the Card Recovery Bulletin at the time of the transaction. Code 11.2 covers declined authorizations that were processed anyway. Code 11.3 covers transactions where no authorization was obtained at all, and also absorbed the retired 12.1 Late Presentment function. Authorization disputes are largely merchant or processor errors rather than cardholder claims, which means they are difficult to contest because the procedural failure is usually documented.

The processing errors category, codes 12.2 through 12.7, covers mistakes in how the transaction was submitted. Incorrect transaction code, incorrect currency, incorrect account number, incorrect amount, duplicate processing, and invalid data each have their own code. Code 12.6 covers both duplicate processing and transactions paid by other means under the same code number. These disputes are also typically merchant-side errors that are hard to contest when the underlying mistake actually occurred.

The consumer disputes category, codes 13.1 through 13.9, covers cardholder complaints about the goods or services themselves. This is the most defensible category when documentation exists. Code 13.1 covers merchandise or services not received. Code 13.2 covers canceled recurring transactions. Code 13.3 covers merchandise or services that were not as described or arrived defective. Code 13.7 covers canceled merchandise or services. These codes require evidence that the product was delivered, the service was rendered, or the cancellation was not properly requested.

The Visa Code That Changed How Disputes Work

Code 10.4 is the most important code for any e-commerce merchant to understand in detail because Visa introduced a specific defense mechanism for it that fundamentally changed the representment landscape.

Compelling Evidence 3.0 is a Visa rule that allows merchants to defeat a 10.4 dispute by demonstrating that the same cardholder, on the same device, completed at least two prior undisputed transactions with the merchant in the 120 days before the disputed transaction. If those two prior transactions exist and the device and customer profile data match, the dispute is presumptively non-fraud regardless of what the cardholder claims. The issuer cannot simply accept the cardholder’s denial and award the chargeback. The full rules governing Compelling Evidence 3.0 and all dispute conditions are published in Visa’s Core Rules document at corporate.visa.com, updated April 18, 2026.

For merchants who store customer profile data, IP addresses, and device fingerprints at the time of each transaction, Compelling Evidence 3.0 is a significant shift. For merchants who do not capture that data, it changes nothing. The rule rewards merchants who build the evidence at the point of sale rather than scrambling for it after a dispute arrives.

How Mastercard Organizes Its Reason Codes

Mastercard uses four-digit numeric codes rather than Visa’s decimal system. The codes cluster by function but are not organized with the same category-prefix logic. The codes most relevant to card-not-present merchants sit in three groups.

The fraud codes center on 4837, the primary code for card-not-present unauthorized transaction claims. Code 4837 is the Mastercard equivalent of Visa’s 10.4 and is the most common fraud code e-commerce merchants receive. Code 4863, Cardholder Does Not Recognize, sits adjacent to 4837 and covers cases where the cardholder sees an unfamiliar charge but has not definitively claimed fraud. The distinction between 4863 and 4837 matters because 4863 disputes are often won by demonstrating a clear billing descriptor and evidence of the customer’s interaction with the merchant. Code 4849 covers transactions tied to merchants flagged under Mastercard’s Global Merchant Audit Program. Codes 4870 and 4871 cover chip liability shift scenarios that primarily affect card-present transactions.

The cardholder dispute codes center on 4853, which is Mastercard’s broadest dispute code. Code 4853 covers goods or services not received, merchandise not as described, credit not processed, and several other sub-conditions all under the same top-level code. When a merchant receives a 4853 dispute, the specific sub-condition stated in the notice determines what evidence is needed. Merchants should read the dispute notice fully rather than responding to 4853 generically. Mastercard has been consolidating older codes into 4853 over recent cycles, including folding code 4841 Canceled Recurring into 4853 in some regions.

The authorization and processing error codes center on 4808 for authorization-related chargebacks and 4834 for point-of-interaction errors including duplicate transactions and incorrect amounts.

Response Deadlines by Network

Deadlines in chargeback disputes are absolute. Missing a representment window means the dispute is lost regardless of how strong the evidence is.

For Visa disputes, merchants have 30 days from the date of the dispute notification to submit representment. Cardholders have up to 120 days from the transaction date or the expected delivery date, whichever is later, to file most dispute codes.

For Mastercard disputes, merchants have 45 days from the dispute notification to respond. Cardholders have 120 days from the transaction date for most codes including 4837 and 4853. Code 4853 can extend to 540 days in certain sub-conditions involving non-receipt of services with a future delivery date.

The practical implication is that a merchant can receive a chargeback nearly four months after a transaction settled, and in some Mastercard cases nearly 18 months later. Maintaining transaction records, delivery confirmations, and customer communication logs for a minimum of 18 months from the transaction date is the only way to have evidence available when late disputes arrive.

What Evidence Each Category Requires

The evidence requirement follows the code category. Fraud codes require proof that the cardholder authorized and participated in the transaction: AVS and CVV match confirmation, IP address and device fingerprint at the time of checkout, delivery confirmation with the address matching the billing address, customer communication records, and for 10.4 disputes specifically, prior transaction history under Compelling Evidence 3.0 where applicable.

Authorization codes require proof that valid authorization was obtained at the time of the transaction: the authorization code, the date and amount it was obtained for, and proof that the transaction was submitted within the required timeframe.

Processing error codes require proof that the specific error did not occur: a single transaction record where duplicate processing is alleged, the correct transaction amount where an incorrect amount is alleged, or evidence that payment by other means did not happen where that sub-condition is claimed.

Consumer dispute codes require proof related to the specific claim: signed delivery confirmation or tracking with delivery to the billing address for non-receipt claims, evidence that the subscription cancellation was not properly requested for canceled recurring claims, and product documentation and customer communication for not-as-described disputes.

The process of compiling and submitting that evidence is representment, covered in the representment guide coming in this cluster. The full framework for how chargeback ratios are calculated and what monitoring programs track is in the complete guide to chargebacks.

What Reason Codes Do Not Tell You

A reason code describes what the cardholder claimed, not what actually happened. Code 10.4 means the cardholder told their bank they did not authorize the transaction. It does not mean they are telling the truth. Code 13.1 means the cardholder told their bank the merchandise was not received. It does not mean the package was not delivered.

This distinction is operationally important because the evidence needed to win a representment is evidence that contradicts the claim in the code, not evidence that proves the merchant behaved well in general. A merchant who submits a refund policy document in response to a 10.4 dispute has submitted irrelevant evidence. The 10.4 code is a fraud claim, not a satisfaction claim. The evidence needed is proof of authorization, not proof of a returns process.

Reading the reason code before gathering evidence, and mapping the evidence to the specific claim the code represents, is the mechanical step that determines whether representment succeeds or fails.

Frequently Asked Questions

What does a chargeback reason code tell a merchant?

A reason code identifies the category of dispute the issuing bank has filed on the cardholder’s behalf. It tells the merchant what the cardholder claimed and, under card network operating rules, what evidence is required to contest the dispute through representment. The code is not a finding of fact. It is the cardholder’s stated reason for disputing the charge.

What is the most common chargeback reason code for e-commerce merchants?

Visa reason code 10.4, Other Fraud in a Card-Absent Environment, and Mastercard reason code 4837, No Cardholder Authorization, are the most common codes for card-not-present merchants. Both codes cover unauthorized transaction claims and together account for the majority of e-commerce chargeback volume at most high-risk merchants.

How long does a merchant have to respond to a chargeback?

Visa disputes require representment within 30 days of the dispute notification. Mastercard disputes allow 45 days. These deadlines are absolute under card network operating rules. Missing the representment window means the dispute is lost regardless of the available evidence.

What is Visa Compelling Evidence 3.0?

Compelling Evidence 3.0 is a Visa rule that allows merchants to defeat a 10.4 dispute by demonstrating that the same cardholder completed at least two prior undisputed transactions with the merchant using the same device and customer profile in the 120 days before the disputed transaction. When those prior transactions are documented, the dispute is presumptively non-fraud. The rule only applies to Visa code 10.4 and requires that the prior transaction data was captured at the point of sale.