Vigilant
Just explore Start now

Payments Glossary · Risk & Compliance

Chargeback Reason Codes

Also called dispute reason codes, Visa reason codes, Mastercard reason codes

Network-assigned codes that classify why a dispute was filed and dictate exactly what evidence can win it.

What it is

Every chargeback carries a reason code assigned by the issuer. The code is not bureaucratic trivia. It determines the category of dispute, the time limits, and, most importantly, the specific evidence the network will accept as a valid rebuttal. Submitting the right documents against the wrong code loses. The four families are consistent across networks even though the numbering is not. Fraud covers unauthorized use and card-absent fraud. Authorization covers transactions processed without valid authorization or after a decline. Processing errors cover duplicates, incorrect amounts, currency errors and late presentment. Consumer disputes cover goods or services not received, not as described, defective, cancelled recurring transactions and credit not processed. Visa restructured its dispute categories under Visa Claims Resolution, grouping codes into fraud, authorization, processing errors and consumer disputes, with allocation handling fraud and authorization automatically and collaboration governing the rest. Mastercard maintains its own code set with similar families. Amex and Discover run their own. Because the codes change and the evidence lists change with them, the reliable move is not memorizing numbers. It is pulling the current requirement for the specific code from your processor's dispute portal or the network rules before assembling a response.

Why it matters to your business

The reason code tells you whether you have a case before you spend two hours on it. Not received is often winnable with delivery confirmation. Unauthorized on a card-present chip transaction is usually the issuer's problem, not yours. Cancelled recurring transaction is usually lost unless your cancellation records are impeccable. Sort your last twelve months of disputes by code. The pattern almost always points at one operational fix: a descriptor, a shipping process, a cancellation workflow, a refund policy nobody can find. This is education, not legal advice; code definitions and evidence requirements are set by network rules that change.

Where it gets contested

The practical fight is over code selection. Issuers choose the code, and a cardholder describing dissatisfaction can end up filed under a fraud code, which is far more damaging to the merchant because fraud codes feed fraud monitoring programs in addition to dispute counts. Merchants have no mechanism to reclassify. There is also a longstanding argument about evidence lists. Networks specify what compelling evidence looks like, and for digital goods, services and subscriptions the specified evidence often does not exist in a form the merchant can produce, which merchants read as an unwinnable category by design. In the gray area, an industry of dispute response vendors has grown up around template libraries keyed to reason codes. Some genuinely improve win rates. Some simply file the same document against every code and bill per case. The difference is measurable only if you track outcomes by code, which almost nobody does.

How to check it yourself

Export your last twelve months of chargebacks with the reason code column included and count them by code. If one code is more than a third of your volume, that is an operations problem with a name, not a chargeback problem.

Receipts

Claims above that are checkable, with where to check them. Published so you do not have to take anyone's word for it.