A chargeback reason code is a code, defined by each card network, that a card issuer must include when it raises a chargeback. The code states the ground for the dispute, for example that the cardholder did not authorise the payment, did not receive the goods or was charged twice. It tells the merchant and its acquirer what the issuer is claiming, which rules apply, how long each side has to act and what evidence can defeat the claim.
Each network has its own set of codes, and they are revised from time to time. Visa uses numeric codes grouped into four categories, while Mastercard uses four-digit codes. Other networks, such as American Express and Discover, have their own systems. Acquirers and dispute tools often map these to common categories so that merchants can manage disputes across brands. Reason codes play a similar role to the ACH return codes used for bank debits in the United States.
Main categories
Despite differences in numbering, most networks group disputes into broadly similar types:
- Fraud. The cardholder says they did not make or authorise the transaction. Outcomes often depend on authentication and chip liability shift rules.
- Authorisation. The merchant processed a payment without a valid authorisation, after a decline, or after the authorisation had expired.
- Processing errors. Problems such as duplicate charges, incorrect amounts, wrong currency, late presentment or a charge to the wrong account.
- Consumer disputes. The cardholder authorised the payment but has a complaint, such as goods or services not received, not as described, defective, cancelled, or a refund not processed.
Examples of network codes
| Network | Code | Meaning |
|---|---|---|
| Visa | 10.4 | Other fraud in a card-absent environment |
| Visa | 10.1 | EMV liability shift counterfeit fraud |
| Visa | 11.3 | No authorisation |
| Visa | 12.6 | Duplicate processing or paid by other means |
| Visa | 13.1 | Merchandise or services not received |
| Visa | 13.2 | Cancelled recurring transaction |
| Visa | 13.3 | Not as described or defective merchandise or services |
| Visa | 13.6 | Credit not processed |
| Mastercard | 4837 | No cardholder authorisation |
| Mastercard | 4853 | Cardholder dispute, covering issues such as goods not received or not as described |
| Mastercard | 4808 | Authorisation-related chargeback |
| Mastercard | 4834 | Point-of-interaction error, such as duplicate processing |
| Mastercard | 4870 | Chip liability shift |
Visa's categories are numbered 10 for fraud, 11 for authorisation, 12 for processing errors and 13 for consumer disputes. Mastercard consolidated many older codes into a smaller set, with 4853 covering most consumer disputes.
How codes shape the dispute
Each reason code comes with conditions the issuer must meet before using it, such as contacting the merchant first for some consumer disputes, and with a time limit for filing. It also defines the remedies available to the merchant. For a goods-not-received claim, proof of delivery to the cardholder's address can be decisive. For card-absent fraud, evidence that the payment was authenticated through 3-D Secure, or compelling evidence that the same customer made earlier undisputed purchases with the same device or account, may win the case. For a cancelled recurring transaction, the merchant needs to show the customer did not cancel or was clearly told the terms. Sending evidence that does not answer the specific code usually fails.
Using reason codes in practice
Merchants analyse their reason codes to find the root causes of disputes. A high share of fraud codes suggests weak fraud screening or a lack of authentication; many "not recognised" disputes point to an unclear billing descriptor; frequent "credit not processed" codes show slow refunds. Acquirers and dispute service providers use the same data to decide which chargebacks are worth contesting through chargeback representment, and to monitor a merchant's chargeback ratio. Some codes, such as those linked to scheme fraud monitoring programmes, cannot be contested at all.
Limitations
Reason codes do not always reflect what really happened. Cardholders sometimes describe a dispute in a way that leads to a fraud code even though they made the purchase, a form of friendly fraud, and issuers may choose codes that make the dispute easier to win. Frequent rule changes also mean merchants must keep their dispute processes up to date. For these reasons, merchants are encouraged to treat reason codes as a starting point and to combine them with their own transaction and customer data when deciding how to respond. A general overview of disputes is given under chargeback lifecycle.