Reason Code

What Is a Reason Code?

A reason code is a short alphanumeric label that a card network assigns to a chargeback or dispute to explain the underlying cause. When a cardholder contacts their issuing bank to challenge a transaction, the bank selects a reason code that categorizes the claim. That code then travels through the card network to the acquirer and merchant, defining what happened and what evidence is needed to contest the dispute.

Each card network maintains its own reason code system. Visa uses a decimal notation (such as 10.4 for card-not-present fraud), while Mastercard uses four-digit codes starting with 48 (such as 4837 for unauthorized transactions). American Express and Discover have their own schemes. Despite the different formats, all networks organize reason codes around the same core question: why does the cardholder believe this transaction should be reversed?

Reason codes serve a dual purpose. For cardholders, they formalize a complaint into a structured process with defined rules and timelines. For merchants, they specify exactly what evidence is required to defend a transaction during representment: the formal process of challenging a chargeback with supporting documentation.

How It Works

When a cardholder initiates a dispute, the issuing bank reviews the claim and assigns a reason code from the relevant card network's classification system. The process follows a structured path:

1. The cardholder contacts their issuing bank to report an issue with a transaction
2. The issuer evaluates the claim and selects the appropriate reason code from the network's catalog
3. A chargeback is filed with the assigned reason code and transmitted to the acquirer
4. The acquirer notifies the merchant, who reviews the code to understand the specific allegation
5. Based on the reason code, the merchant gathers the required evidence and submits a representment package within the network's deadline
6. The issuer reviews the evidence and either reverses the chargeback or upholds it

The reason code is not merely a label: it dictates the rules of engagement. Different codes carry different evidence requirements, response deadlines, and escalation paths. A fraud-related code demands different proof than a processing error code, even if the disputed amount is identical.

Visa Reason Code Categories

Visa organizes its reason codes into four numbered categories, each covering a distinct type of dispute:

Visa's 10.4 code (card-absent fraud) is among the most commonly filed: it covers online, phone, and mail-order transactions that the cardholder says they never authorized. Code 13.1 (merchandise not received) is equally frequent in e-commerce, where delivery disputes are common.

Mastercard Reason Code Categories

Mastercard uses four-digit codes that start with 48. Over time, Mastercard has consolidated several legacy codes into broader categories:

Mastercard's 4853 has absorbed several retired codes (including the former 4841 and 4855), making it an umbrella code that covers a wide range of consumer complaints. Merchants must read the sub-reason documentation within a 4853 dispute to understand the specific claim.

Response Deadlines

Each card network imposes strict time limits for merchant responses. Missing these deadlines results in an automatic loss, regardless of the strength of the merchant's evidence:

• Visa: merchants generally have 30 days from when the chargeback is filed to submit representment evidence
• Mastercard: merchants typically have 45 days to respond to a first chargeback and 30 days for pre-arbitration cases
• Acquirers and processors may impose shorter internal deadlines, sometimes giving merchants only 5 to 10 days in practice

If representment fails, the dispute can escalate to pre-arbitration and eventually arbitration, where the card network makes a final binding decision. Each escalation stage has its own deadlines and fees.

Reason Codes vs. Decline Codes

Reason codes and decline codes serve related but distinct purposes. A decline code is returned in real time during authorization to explain why a transaction was rejected before it settles: insufficient funds, expired card, or suspected fraud. The transaction never completes.

A reason code, by contrast, applies after a transaction has already been authorized and settled. The cardholder received the goods or service, the merchant received payment, and then the cardholder disputes the charge. The reason code categorizes why the completed transaction is being reversed.

Transaction Lifecycle and Code Types:

Authorization Phase:
  Card presented → Authorization request → Approved or Declined
  If declined → Decline Code returned (e.g., "51: Insufficient Funds")
  If approved → Transaction settles normally

Post-Settlement Phase:
  Cardholder disputes charge → Issuer files chargeback
  Reason Code assigned (e.g., Visa 10.4: Card-Absent Fraud)
  Merchant receives reason code → Gathers evidence → Representment

Use Cases

Merchant Dispute Strategy

Reason codes are the foundation of any representment strategy. Different codes require fundamentally different evidence:

• Fraud codes (Visa 10.4, Mastercard 4837): merchants need proof of cardholder identity verification, such as 3D Secure authentication records, AVS match results, or CVV confirmation
• Authorization codes (Visa 11.x): merchants must produce valid authorization approval codes and transaction receipts showing the issuer approved the charge
• Processing error codes (Visa 12.x, Mastercard 4834): merchants provide transaction records demonstrating the correct amount, single processing, and accurate account details
• Consumer dispute codes (Visa 13.x, Mastercard 4853): merchants submit delivery confirmation, tracking data, signed receipts, or refund records, depending on the sub-reason

Chargeback Ratio Monitoring

Card networks monitor merchants' chargeback ratios and can place merchants into monitoring programs if dispute rates exceed thresholds. Reason code analysis helps merchants identify patterns: a spike in fraud codes might indicate a data breach, while a cluster of "merchandise not received" disputes could signal shipping problems.

Visa's reason code 10.5 is specifically tied to the Visa Fraud Monitoring Program and is filed when Visa's own systems flag a merchant's transaction patterns as suspicious, rather than in response to an individual cardholder complaint.

Payment Processor Integration

Payment processors and gateways translate network-specific reason codes into standardized categories for merchants. Platforms like Stripe group the hundreds of codes from Visa, Mastercard, American Express, and other networks into eight unified categories, simplifying the merchant's response workflow regardless of which network originated the dispute.

Crypto-Funded Card Payments

When consumers use crypto-funded cards to make purchases, the transaction still flows through traditional card networks. If a dispute arises, standard reason codes apply. However, blockchain transactions introduce unique challenges: on-chain transfers are irreversible, creating a "reversal gap" where a processor may need to refund fiat even though the underlying crypto has already been delivered, swapped, or withdrawn.

Crypto-enabled payment processors are developing methods to map on-chain evidence (wallet addresses, transaction hashes, and settlement timestamps) to traditional reason code frameworks. This on-chain data can strengthen representment cases by providing immutable proof of delivery or authorization that traditional payment systems lack. For a deeper exploration of how dispute processes interact with blockchain payments, see Payment Dispute Resolution: Crypto Chargebacks.

Friendly Fraud and Reason Code Ambiguity

One significant challenge with reason codes is that they classify the type of dispute, not the intent behind it. A reason code like Visa 10.4 (card-absent fraud) reads identically whether the card was genuinely stolen or whether the cardholder made the purchase themselves and later regretted it. This pattern, known as friendly fraud or first-party fraud, accounts for a significant share of all chargebacks.

The ambiguity creates a burden on merchants. A legitimate fraud claim and a friendly fraud claim carry the same reason code, same evidence requirements, and same consequences if the merchant cannot successfully represent. Tools like fraud scoring and transaction monitoring help merchants distinguish between genuine fraud and buyer's remorse, but the reason code itself offers no signal.

Risks and Considerations

Misclassification

Issuers sometimes assign the wrong reason code to a dispute. A cardholder who did not receive their merchandise might file under a fraud code rather than a consumer dispute code, or vice versa. Misclassification can leave merchants preparing the wrong evidence, wasting representment efforts and reducing win rates.

Network Fragmentation

Each card network maintains its own code system, and these systems evolve independently. Mastercard has consolidated several legacy codes into broader categories, while Visa maintains more granular distinctions. Merchants operating across multiple networks must track different codes, different evidence requirements, and different response deadlines simultaneously.

Compressed Response Windows

While networks allow 30 to 45 days for representment, acquirers and processors often impose much shorter internal deadlines. Merchants may realistically have only 5 to 10 days to identify the reason code, gather the corresponding evidence, and submit a response. Automated dispute resolution systems help, but smaller merchants without dedicated chargeback teams often miss windows and lose by default.

Evolving Code Systems

Card networks periodically update their reason code catalogs: merging codes, retiring legacy identifiers, and introducing new categories to reflect emerging payment patterns. Mastercard's consolidation of codes 4841 and 4855 into the broader 4853 code is one example. Merchants and their payment partners must stay current with these changes to ensure their dispute management systems remain accurate.

This glossary entry is for informational purposes only and does not constitute financial or investment advice. Always do your own research before using any protocol or technology.