Chargeback Reason Codes: How Visa, Mastercard, and Amex Number Them

A chargeback notice rarely says "the customer says the product wasn't as described." It says something like "Reason Code 85" or "13.1" or "C08," and a merchant who does not know what that number means will waste the response window looking in the wrong place. Each card network keeps its own numbering system, the same underlying complaint can carry a different code on different networks, and the numbering has changed over time as networks consolidated categories. This guide is a map from the number on the notice to the actual factual question being asked, not a full response playbook — the ten guides elsewhere on this site cover writing the actual evidence for each scenario.

Three separate numbering systems, one underlying set of complaints

Visa, Mastercard, and American Express each publish their own reason-code lists, and a processor dashboard usually shows whichever network's code applies to that card. There is no universal cross-network number; "credit not processed" is Visa reason code 85 under the legacy system (Visa has also introduced newer numeric groupings such as 13.x for consumer disputes), the equivalent under Mastercard is commonly listed as C02, and American Express uses its own alphanumeric codes such as C08. Treat the network shown on the transaction as the only numbering system that matters for that specific case — do not assume a code number carries the same meaning across networks.

Within a single network, the codes cluster into families. Visa's consumer-dispute codes largely fall in the 13.x range (for example, merchandise/services not received, not as described, canceled recurring, credit not processed), while Visa's fraud and authorization-related codes use different number ranges entirely. Mastercard's dispute categories are grouped by chargeback reason (cardholder dispute, fraud, authorization, processing errors), each with its own code prefix. American Express labels many categories with a letter prefix (A, C, F, M, P, R) followed by a number, and the letter roughly indicates the category — for example, several "C" codes relate to processing errors, including credit not processed.

Why the exact code changes what evidence matters

The code is the network's shorthand for the specific factual question the cardholder or issuer is asking. A "credit not processed" code asks whether a refund the merchant agreed to (or was required to make) was actually issued and posted. It does not ask whether the original sale was valid, so proof of the original transaction is not the evidence that resolves it — proof of the refund, or proof no refund was owed, is. A "not as described" code asks about the condition or nature of what was delivered relative to the listing, which calls for product specifications, photos, and support communications, not a refund ledger.

Confusing the categories is a common and avoidable loss. A merchant who receives a "not as described" dispute and responds only with a delivery-confirmation tracking number has not addressed the actual claim; delivery evidence answers a "not received" dispute, not a description dispute. Read the exact reason description on the notice, not just the number, because processors sometimes summarize the category in plain language alongside the code.

A representative mapping (verify the live notice)

Treat this table as a starting orientation, not a lookup you should cite to a customer or an issuer. Network rulebooks are revised, code numbers get retired or renumbered, and processors sometimes map a network's raw code to their own internal label on the merchant dashboard. Before building a response, confirm the current code and its stated description directly in the processor's dispute portal or the current network chargeback guide, and match it to the correct scenario guide on this site.

The number tells you the network's theory, not the customer's whole story

A dispute can be filed under the wrong code — a cardholder who actually never received the item might get coded as "not as described" by a call-center agent who typed the wrong category, or a bank might apply a fraud code when the real issue is a service cancellation the merchant never processed. If the evidence you have clearly answers a different, closely related question than the one the code technically asks, include both: address the coded question directly, and note the discrepancy with supporting facts. Do not simply argue that "the code is wrong" without also answering the substance, because a technical objection alone rarely overturns a dispute.

Filing and response windows differ by network too

Just as the codes differ, so do the clocks. Visa, Mastercard, and Amex each set their own cardholder filing windows and merchant response windows, and those windows can also vary based on the specific reason code and whether it is a first chargeback, a pre-arbitration, or arbitration stage. The deadline printed on the actual processor notice controls the immediate task — a general "60 days" or "120 days" figure repeated from an old article is not reliable enough to build a real deadline around. Calendar the date on the current notice the same day it arrives.

What to do with the code before you touch a single document

Write down four things before pulling any evidence: the exact code and its label from the current notice, the network, the transaction amount and date, and the response deadline. Then open this site's scenario guide that matches the label — "not as described," "not received," "duplicate processing," "credit not processed," "canceled recurring," or the fraud/card-not-present guide — and follow its evidence checklist. The code is the entry point into the right process, not the process itself.

When the code does not map cleanly to any scenario guide

Some codes are narrow or network-specific enough that no single-scenario page will match exactly — authorization-related codes, processing-error codes tied to currency or account-number mismatches, or codes specific to a card-present terminal failure. In those cases, read the network's own current description of the code closely, gather the transaction-processing records that speak directly to that description, and consider requesting written clarification from the acquirer or processor about which evidence they expect. Guessing at a mismatched evidence type wastes the response window; a short clarifying question to the payment processor rarely does.

Keep a running log by code, not just by dispute

If chargebacks recur, track them by network and code rather than only by total count. A cluster of "credit not processed" disputes usually points to a refund-processing delay inside the business, while a cluster of "not as described" disputes usually points to a listing or fulfillment problem. The code-level pattern is often more actionable than an aggregate chargeback-rate number, because it tells you which operational process to fix first.

What changes when a case escalates past the first chargeback

A reason code assigned at the first chargeback stage does not always stay fixed if the case escalates to pre-arbitration or arbitration. Some networks allow the issuing bank to re-code a case at a later stage if new information changes which category best fits the dispute, and the evidence standard at arbitration is often stricter than the standard for a first-round response. Track the code shown at each stage separately rather than assuming the original code will be the one that matters if the case goes further, and re-read the notice at every stage rather than reusing the same evidence packet without checking whether the stated reason changed.