Skip to main content
Commerce Security Authority
Category: Chargebacks and Disputes

Chargeback Reason Code

Also known as: Dispute Reason Code, Reason Code
Simply put

A chargeback reason code is a short code that a cardholder's bank assigns to a disputed transaction to explain why the charge is being reversed. It tells the merchant and payment processor the specific reason behind the dispute, such as fraud, a processing error, or goods not received. Each card network uses its own set of codes, so the same underlying dispute may appear under different codes depending on the network.

Formal definition

A chargeback reason code is a 2- to 4-digit alphanumeric identifier supplied by the issuing bank when initiating a chargeback, used to classify the basis for the dispute and to determine applicable defense or representment requirements. Codes are network-specific and are typically grouped into categories; for example, Visa organizes codes with leading digits denoting category (10 for Fraud, 11 for Authorization, 12 for Processing Errors, 13 for Consumer/Cardholder Disputes), while Mastercard organizes reason codes under categories such as Authorization, Cardholder Disputes, Fraud, and Processing Errors. Equivalent disputes carry different codes across networks—for instance, 'merchandise or service not received' may be cited as 13.1 (Visa), 4853 (Mastercard), or C08 (American Express). Reason codes also appear in adjacent dispute events such as Requests for Information (RFI) and Notifications of Fraud (NOF); the specific code sets, categories, and defense requirements are defined and periodically revised by each card brand and network, so practitioners should confirm current values against the governing network's published dispute documentation.

Why it matters

Chargeback reason codes are the primary language through which issuers, merchants, and payment processors communicate about a dispute. Because the code assigned by the cardholder's bank identifies the stated basis for the reversal—such as fraud, an authorization problem, a processing error, or a cardholder dispute like merchandise not received—it directly shapes how a merchant can respond and what evidence may be required to contest the chargeback through representment. Misreading or mishandling a reason code can lead to a defense that fails to address the actual grounds of the dispute.

A significant practical challenge is that each card network maintains its own code set. The same underlying dispute can appear under different codes depending on the network: for example, 'merchandise or service not received' may be cited as 13.1 on Visa, 4853 on Mastercard, or C08 on American Express. Teams that process transactions across multiple networks must therefore map equivalent disputes across differing code schemes rather than assuming a single universal code. Reason codes also surface in adjacent dispute events such as Requests for Information (RFI) and Notifications of Fraud (NOF), broadening the contexts in which accurate interpretation matters.

Because the code sets, category groupings, and associated defense requirements are defined and periodically revised by each card brand and network, reliance on outdated code lists can undermine dispute handling. Practitioners should confirm current values and requirements against the governing network's published dispute documentation rather than assuming that a given code or category remains fixed over time.

Who it's relevant to

Merchant Dispute and Chargeback Teams
These teams rely on the reason code to determine the grounds of a dispute and to assemble an appropriate representment. Because defense requirements differ by code and network, and because equivalent disputes appear under different codes across Visa, Mastercard, and American Express, accurate code interpretation is central to their day-to-day work.
Payment Processors and Acquirers
Processors and acquirers relay reason codes between issuers and merchants and support dispute workflows across multiple networks. They must account for network-specific code sets and categories, and for related events such as RFIs and NOFs, when routing and reporting disputes.
Fraud Analysts
Fraud-related reason codes, grouped under each network's Fraud category, help analysts identify disputes attributed to fraudulent activity. Because a fraud code reflects the issuer's stated basis rather than a confirmed determination, analysts should treat it as one input alongside other evidence when investigating.
Compliance and Risk Management
Teams responsible for monitoring dispute and chargeback activity need to work from current, network-specific code sets, since categories, codes, and defense requirements are periodically revised by each card brand and network. Confirming values against the governing network's published dispute documentation helps keep reporting and response processes accurate.

Inside Chargeback Reason Code

Reason Code Identifier
A code assigned by a card brand or network to categorize the stated basis for a chargeback, such as fraud, authorization issues, processing errors, or consumer disputes. The specific code values, groupings, and wording are defined by each card brand and vary by network and region.
Dispute Category
The broad classification a reason code falls under, commonly including fraud-related disputes, authorization-related disputes, processing errors, and cardholder disputes over goods or services. Categories and their scope differ across card brands.
Fraud-Related Codes
Reason codes indicating the transaction is disputed as unauthorized or fraudulent, which may correspond to card-present or card-not-present scenarios. These codes may interact with liability shift rules that are governed by card brand and network rules and can vary by region.
Evidence and Response Requirements
Each reason code is typically associated with defined documentation a merchant may submit to represent or dispute the chargeback, along with time frames set by the card brand or network. Requirements and deadlines are network-specific and subject to change.
Liability Indicator Context
The context in which a reason code may point toward merchant, issuer, or cardholder liability, determined by card brand and network rules rather than by the reason code label alone.

Common questions

Answers to the questions practitioners most commonly ask about Chargeback Reason Code.

Does a chargeback reason code prove that fraud actually occurred?
No. A chargeback reason code describes the category of dispute the issuer or cardholder has raised, not a proven finding of fraud. A fraud-related reason code indicates the basis on which the transaction is being disputed; it does not by itself establish that fraud took place, that the merchant is liable, or that the dispute will be resolved against the merchant. Whether the dispute is ultimately upheld depends on the representment evidence and the card brand and network rules that govern the case.
Are chargeback reason codes standardized across all card networks?
No. Reason codes, their numbering, their descriptions, and the evidence and timeframes associated with them are defined by each card brand and network individually, and they can differ by region. A code that carries a particular meaning under one network does not necessarily map to the same meaning under another. Because these rules are set and revised by the networks, you should confirm current codes and their handling against the applicable network's published rules rather than assuming a single universal scheme.
How should a merchant map an incoming chargeback reason code to an internal dispute workflow?
Group incoming codes by the type of dispute they represent, for example fraud-related, authorization or processing errors, and cardholder disputes over goods or services, then route each group to the team and evidence template best suited to respond. Because codes and their meanings vary by network and region and change over time, maintain the mapping against each network's current published rules rather than hard-coding assumptions, and revalidate it when networks update their dispute frameworks.
What evidence is typically relevant when representing a fraud-related reason code?
The relevant evidence depends on the specific code and the governing network rules, and it differs between card-present and card-not-present scenarios. Merchants generally assemble records supporting that the transaction was legitimately authorized and delivered, which may include authorization data, delivery or service records, and any authentication results available for the transaction. Because acceptable evidence and submission timeframes are defined by each network and may vary by region, confirm the required documentation against the applicable network's current dispute rules before responding.
How can reason codes inform fraud and dispute analytics without being misread?
Reason codes can be used to segment disputes by category and to observe trends over time, which may help identify where losses concentrate. Treat them as indicators of how disputes are being classified rather than as confirmed root causes, since a given code reflects the basis asserted for a dispute, not a verified outcome. Because code definitions differ by network and region and change over time, normalize codes carefully before aggregating, and avoid comparing raw counts across networks as if the codes were equivalent.
Does responding to a chargeback reason code have any effect on PCI DSS scope or stored data handling?
Managing chargebacks and PCI DSS obligations are separate concerns. Representment may involve retaining transaction and dispute records, but this does not authorize storing sensitive authentication data, such as full track data, card verification values, or PINs, which must not be retained after authorization even when encrypted. Any cardholder data retained to support disputes remains subject to the applicable controls, and where account identifiers appear in dispute records, apply the same masking, truncation, or protection practices you use elsewhere. Confirm specific data-handling requirements against the current published standard.

Common misconceptions

Chargeback reason codes are standardized and identical across all card brands.
Reason code values, wording, categories, and associated rules are defined independently by each card brand and network, and they vary by region and change over time. Practitioners should confirm codes against the current published rules of the relevant network.
A fraud reason code always means the transaction was genuine third-party fraud.
A fraud-labeled chargeback may in practice reflect friendly or first-party fraud, chargeback fraud, or a cardholder dispute rather than confirmed unauthorized use. The reason code reflects the stated basis of the dispute, not a verified determination of fraud type.
The reason code determines who bears financial liability.
Liability and any applicable liability shift are governed by card brand and network rules, which vary by region and change. The reason code provides context but does not by itself decide the outcome or the liable party.

Best practices

Map incoming chargebacks to the current, published reason code definitions of the specific card brand and network involved, rather than relying on a fixed or cross-brand reference, since codes and rules vary by network and region and change over time.
Track the response documentation and time frames associated with each reason code as defined by the relevant network, and build workflows that meet those network-specific deadlines.
Distinguish fraud-labeled chargebacks that may reflect friendly or first-party fraud or chargeback fraud from confirmed third-party fraud, and analyze patterns to inform dispute handling and fraud controls.
Retain transaction, authentication, and delivery evidence that supports representment for the applicable reason code categories, while ensuring that any stored data complies with PCI DSS controls and that sensitive authentication data is not stored after authorization.
Monitor changes to card brand and network chargeback rules and reason code sets on an ongoing basis, and update internal mappings and procedures accordingly.
Treat liability shift outcomes as governed by network rules that vary by region, and confirm the applicable rules for each dispute rather than assuming a fixed liability result from the reason code.