Mastercard Chargeback Reason Codes: 2026 List and Evidence

Mastercard chargeback reason codes identify the issuer’s reported dispute condition. Use the lookup to find the claim, then select records that answer it. A code alone does not prove fraud. A 4837 claim can also be friendly fraud, where the cardholder made the purchase and disputes it anyway.

Mastercard Chargeback Reason Codes List (2026)

This lookup includes common, older and regional labels. Keep the original code and complaint, and check your processor’s current mapping. It is not a complete list for every payment route.

Frequency varies by merchant, region and product, and no single code is the most common for every business. Reason code 4853 is the broadest cardholder-dispute code and 4837 is the main no-authorization fraud code, so many merchants meet them often, but your own dispute data is the better guide.

How to read this lookup

Adyen's dispute reason-code reference groups codes into the four claim families. Conditions vary by reason, message system, region and stage; the Mastercard Chargeback Guide, Merchant Edition (13 May 2025) provides dated background.

New to chargebacks? Start with what is a chargeback. For current requirements, check Mastercard’s rules and compliance resources and your acquirer. Our guide to Mastercard chargeback rules covers the full process.

A Code Narrows the Question; the Complaint Selects the Proof

A code records a claim, not the customer’s intent. A 4837 allegation can involve stolen credentials or friendly fraud, so read the complaint, case notes and processor instructions before choosing evidence. Use the table below to match the claim to useful records. Our guide to chargeback evidence sources explains where to find them.

{{cta}}

Keep the Network Code and Processor Category Separate

A processor’s category is a routing label, not the full complaint. These examples from Stripe’s dispute category mapping show why the category name alone can send a merchant to the wrong records.

Reason Code 4808: Authorization

4808 - Authorization-Related Chargeback

Mastercard reason code 4808 (the 4808 chargeback reason code) identifies an authorization-related condition. Match the approval record and timing to the actual allegation; not every 4808 case claims that approval was never obtained. Older authorization labels may be mapped to it, including required authorization not obtained, expired chargeback protection period and account number not on file. Confirm the condition and message-system mapping with your provider.

Evidence to assess for representment:

• The valid authorization approval code and timestamp, showing it was obtained before settlement
• Proof the transaction was presented within the window that applies to the case, which can differ for pre-authorization holds, so confirm the number of days with your processor
• AVS/CVV match results if the authorization happened in a card-not-present setting
• Terminal and EMV compliance records if a chip card was involved

Erreurs courantes commises par les commerçants qui leur font perdre ce litige :

• Forcing through a hard-declined transaction and hoping it goes unnoticed
• Waiting too long to batch and settle after authorization is granted
• Not re-authorizing when a tip or added line item pushes the final amount above the original hold
• Running outdated terminal software that never earned EMV chip liability protection

Reason Codes 4837, 4840, 4849, 4863, 4870, 4871: Fraud

4837 - Absence d'autorisation du titulaire de la carte

Reason code 4837 (the 4837 chargeback reason code) covers disputes where the cardholder claims they did not authorize, approve, or participate in the transaction. It is one of the main fraud codes, and the claim can stem from a genuinely stolen card, a family member using the card without the primary holder's knowledge, or a cardholder who does not recognize the merchant name on their statement. Sharing order details with the bank through Ethoca Consumer Clarity can help that cardholder recognize the charge. Read the full reason code 4837 breakdown for the complete evidence checklist.

Check First-Party Trust for a 4837 Claim

For an eligible first-party-fraud case, ask your acquirer whether Mastercard First-Party Trust is available for your transactions. Mastercard’s First-Party Trust announcement in June 2025 described a U.S. launch and expansion to Canada, Latin America, the Caribbean and Asia Pacific. It describes enhanced evidence sharing that helps issuers distinguish genuine purchases from unauthorized use; confirm availability for your own route.

4840 - Fraudulent Processing of Transactions

Reason code 4840 is a provider-displayed fraudulent-processing label associated with additional transactions after a card-present purchase. Reconstruct the receipts, timestamps and authorization for each charge; authorization for one sale does not establish authorization for the others. Confirm the label and applicable conditions with the acquirer.

4849 - Questionable Merchant Activity

The 13 May 2025 merchant guide ties 4849 to a QMAP announcement or Mastercard-substantiated coercion. Read the acquirer notice and disputed period. Our Global Merchant Audit Program (GMAP) guide gives monitoring background, but high sales volume alone is not the condition. If a notice refers to the Mastercard Scam Merchant Monitoring Program, confirm the particular rule and chargeback condition instead of treating every monitoring program as interchangeable.

4863 - Cardholder Does Not Recognize, Potential Fraud

Reason code 4863 is a cardholder-does-not-recognize/potential-fraud label still displayed by some providers. Adyen’s reference describes a cardholder who does not recognize the transaction and denies authorizing it. Read the complaint and processor instructions; uncertainty about the descriptor alone does not establish the final cause.

4870 and 4871 - Chip and Chip/PIN Liability Shift

Reason code 4870 concerns counterfeit-chip liability-shift conditions. Reason code 4871 concerns lost, stolen or never-received PIN-preferring chip cards and the applicable terminal PIN capability. They are not identical terminal checks: retrieve the actual card-entry and cardholder-verification records and confirm the case’s region and liability-shift conditions.

Evidence to assess for representment:

• AVS and CVV2 match confirmations from the original transaction
• Device fingerprint, IP geolocation, and prior order history tying the cardholder to the account
• Delivery confirmation with signature or geotagged proof matching the billing or shipping address, though delivery alone is not proof of authorization
• A documented history of undisputed prior transactions from the same card, useful for building a friendly-fraud case
• For 4849: the actual QMAP announcement or coercion notice, plus records showing whether its stated conditions apply

Erreurs courantes commises par les commerçants qui leur font perdre ce litige :

• Treating every fraud-coded chargeback as criminal fraud, when a large share can be friendly fraud disputes that need a different evidence strategy
• Skipping CVV verification on card-not-present orders to reduce checkout friction
• Not retaining IP and device logs long enough to cover the full dispute window
• Ignoring QMAP or other relevant notices from the acquirer until a 4849 chargeback has already landed

Reason Codes 4841, 4853, 4854: Cardholder Disputes

4841 - Canceled Recurring or Digital Goods Transaction

Reason code 4841 is an older/provider-displayed label that can identify a canceled recurring payment or a qualifying digital-goods condition. These are different complaints; a digital-goods purchase is not necessarily a cancellation case. Related conditions may appear under 4853, so subscription merchants should preserve the original label and confirm the provider’s mapping.

4853 - Cardholder Dispute

Reason code 4853 (Mastercard chargeback code 4853, also searched as the 4853 reason code, 4853 chargeback reason code or 4853 cardholder dispute) is Mastercard's broadest cardholder-dispute code. Depending on the stated sub-condition, it can cover disputes of recurring transactions, credit posted as a purchase, addendum disputes, goods or services not as described or defective, digital goods purchases below a stated amount, goods or services not provided, credit not processed, counterfeit goods, incomplete transactions, and no-show hotel charges under Mastercard's Guaranteed Reservation Service. The issuer's supplementary message usually shows which variation applies, and each has its own evidence requirements. Read the full reason code 4853 breakdown for every variation.

4854 - Cardholder Dispute, Not Elsewhere Classified

Reason code 4854 is described as applying when a cardholder is dissatisfied with a transaction and asserts they could not resolve it directly with the merchant. It is generally described as exclusive to Mastercard's US region, with conditions on where the transaction occurred relative to the cardholder's billing address and on a minimum transaction amount. Because those conditions are specific, confirm them in the case instructions. The cardholder's claim of an inadequate merchant response can be enough to trigger the chargeback. Read the full reason code 4854 breakdown for the eligibility conditions.

Evidence to assess for representment:

• Itemized proof of delivery or service fulfillment, including tracking numbers, timestamps, and signed receipts
• The product or service description as it appeared at checkout, matched against what was actually delivered
• Subscription terms, renewal notices, and the cancellation policy the cardholder agreed to, needed for 4841 and recurring-billing disputes
• Communication logs showing the merchant attempted to resolve the issue directly, needed to answer 4854
• Refund or credit confirmation with the date, amount, and reference number tying it to the disputed transaction

Erreurs courantes commises par les commerçants qui leur font perdre ce litige :

• Not archiving product page and checkout copy, leaving no way to prove what the cardholder actually agreed to buy
• Making cancellation difficult enough that customers dispute the charge instead of cancelling directly
• Never documenting outreach to the cardholder before a dispute escalates to 4854
• Issuing a credit without a clear reference number the issuer can match to the original transaction

Reason Codes 4831, 4834, 4842, 4846, 4850, 4999: Point-of-Interaction Error

4834 - Point-of-Interaction Error

Reason code 4834 (the 4834 chargeback reason code) describes payment processing errors at the point of interaction, the physical location or device where a transaction happens, such as a POS terminal, checkout page, or ATM. Depending on the stated condition, it can cover double billing, a transaction amount changed without consent, loss/theft/damage charges applied without approval, duplicate submissions, and unauthorized Dynamic Currency Conversion (DCC). Read the full reason code 4834 breakdown for each of those scenarios in detail.

4831, 4842, 4846, 4850, and 4999 - The Remaining Processing-Error Codes

Reason code 4831 is an older amount-difference label. Late-presentment and currency/DCC complaints may appear under 4842 or 4846 in older records, but current processor mappings can place those conditions under 4834; see our full breakdown of reason code 4842 for the historical label. Reason code 4850 concerns installment billing, subject to the case and message system. For 4999, Adyen describes a Europe-region domestic dispute that does not fit another categorization, so the complaint must be read directly.

Evidence to assess for representment:

• Settlement and batch logs proving a transaction was not duplicated
• The original receipt showing the authorized amount matched what settled
• A currency disclosure or DCC consent screen shown to the cardholder before the transaction completed
• The installment plan agreement or terms, if 4850 is involved
• A timestamp proving the transaction was presented within Mastercard's required window

Erreurs courantes commises par les commerçants qui leur font perdre ce litige :

• Re-running a transaction "just in case" the first attempt failed, creating an accidental duplicate
• Applying DCC without a clear, documented opt-in from the cardholder
• Batching and submitting settlement late, especially around holidays or system outages
• Adjusting an amount after authorization, such as adding a surcharge, without new cardholder consent

Legacy Mastercard Reason Codes and Their Current Equivalents

Older numeric codes still turn up on legacy processor systems and statements. The table shows how they are commonly mapped to current codes. Treat it as a starting point only: legacy numeric labels and current dispute conditions should not be assumed interchangeable without your provider's interpretation, and the case message decides which condition applies.

Do not confuse chargeback codes with Mastercard MATCH reason codes. MATCH is Mastercard's separate merchant-listing system, and its reason codes describe why a merchant was listed, not why a cardholder disputed a charge.

4855, 4853 and 53: Match the Label to the Payment Route

Mastercard’s 13 May 2025 merchant guide recommends 4853 for applicable goods-or-services-not-provided cases, while allowing 4855 pending its eventual elimination. It also shows 53 for some Single Message System debit cases. Adyen’s current reference still includes older labels. Preserve the actual case value and confirm the conditions with the acquirer; do not add or remove a “48” prefix by assumption.

Mastercard vs. Visa Reason Codes: What Changes for Dual-Network Merchants

The same complaint can carry different codes across the two networks. For example, goods-not-as-described claims commonly appear under 4853 on Mastercard but a different code on Visa. The families map loosely, but the code numbers and specific requirements are not interchangeable. American Express uses its own letter codes; see the American Express chargeback reason codes guide.

For the full breakdown of every individual Visa code and how long merchants have to respond to each one, see our guide to Visa chargeback reason codes.

Pourquoi la précision des codes d'erreur revêtira davantage d'importance en 2026

Mastercard's 2026 update on the true cost of chargebacks cites Mastercard and Datos research forecasting 359 million global chargebacks a year by 2029, which is 37% growth from 2025. It also cites Mastercard and Javelin research estimating US merchant operational cost at USD 128 per chargeback (USD 82 internal and USD 46 third-party), excluding lost goods or services. These are forecasts and research estimates, not a measure of any single merchant's loss. More disputes arriving means less time to sort genuine fraud from friendly fraud, and reading the wrong reason code at intake leads to pulling the wrong evidence.

Network programs add a second pressure. Visa's VAMP fact sheet describes thresholds that depend on region and acquirer context, with a lower excessive-merchant ratio in effect from April 1, 2026 in several regions including the US, subject to minimum monthly fraud and dispute counts. That is a Visa program and does not apply to Mastercard disputes, so read Mastercard disputes against Mastercard's rules and your acquirer's notices. For how limits are set across programs, see our guide to chargeback threshold limits.

How to Win a Mastercard Chargeback Representment

Mastercard’s 120-Day Time Limit and the Merchant Response Deadline

Three clocks can apply to the same dispute. An issuer’s filing period does not give the merchant that much time to respond, and an acquirer’s network window may end after the processor’s merchant cutoff.

For the full walkthrough of each stage, from first notice through arbitration, see our guide to the chargeback process. Submit claim-specific evidence through the required channel before your processor cutoff.

Name one owner for submitting each case, whether the evidence is assembled by hand or through automation, so deadlines, evidence and the final submission are never split between people. A written chargeback response template helps that owner keep each reply tied to the specific claim. If the issuer does not accept the response, the next step may be a pre arbitration chargeback stage, whose options depend on the scheme flow and your processor.

Because fraud-code claims are hard to answer with delivery records alone, prevention often pays off first. A chargeback alert service can flag a dispute while it is still a bank inquiry, giving a merchant a window to refund or intervene before the formal chargeback clock starts. Pairing alerts with stronger checkout-level defenses, the kind covered in our ecommerce fraud prevention guide, keeps fewer 4837, 4863, 4870, and 4871 disputes from reaching representment in the first place.

Merchants who route Mastercard volume through more than one processor should confirm each payment service provider's dispute portal supports the evidence formats Mastercard expects. Evidence submitted in the wrong format or through the wrong channel can get a well-documented representment rejected on a technicality rather than the merits.

One emerging complication for 2026 is a transaction initiated by an AI shopping agent rather than the cardholder directly. Existing codes may not map cleanly to a purchase the cardholder never personally confirmed, so confirm with your processor how such a dispute is classified. Our Agentic commerce chargebacks evidence playbook covers what to capture at checkout.

{{cta}}

Foire aux questions

How many Mastercard chargeback reason codes are there?

No single count fits every region, message system and provider. This lookup includes 16 common, older and regional labels across the main claim families; it is not a list of 16 universally current conditions. Some debit routes show shorter labels, and legacy processor displays can differ from current mappings. Use the original case notice and provider instructions.

What is the most common Mastercard chargeback reason code?

No official ranking applies to every merchant. Reason code 4853 (Cardholder Dispute) is Mastercard's broadest cardholder-dispute code, and 4837 (No Cardholder Authorization) is the main no-authorization fraud code, so many merchants see them often. Your own dispute data shows which codes matter most for your business.

What is Mastercard reason code 4853 used for?

Reason code 4853 covers a range of cardholder complaints about a completed transaction, including recurring billing disputes, goods or services not as described or defective, goods never provided, counterfeit merchandise, credit not processed, and no-show hotel charges. The issuer typically adds a supplementary message specifying which variation applies, and the evidence differs for each.

How do Mastercard reason codes differ from Visa reason codes?

Both networks group disputes into similar families, but the numbering and specific evidence requirements differ. Mastercard uses four-digit numeric codes (4808, 4837, 4853, and so on), while Visa uses a decimal system (10.4, 11.3, 13.1, and so on). A merchant processing both networks needs a mapping between the two to avoid building evidence for the wrong requirement.

How long do merchants have to respond to a Mastercard chargeback?

The merchant response deadline is the date shown by the processor, which can be earlier than the acquirer’s network window. Adyen lists 40 days after Notification of Chargeback for several defendable Mastercard codes; other providers and stages differ. The issuer’s 120-day filing period in some conditions is a different clock. Confirm the case deadline.

Can a merchant win a Mastercard chargeback dispute?

Yes, when the issuer accepts a timely response that answers the applicable condition. Authorization records may address 4808, authentication and transaction history may support 4837, and delivery or cancellation records may address specific 4853 complaints. Evidence does not guarantee a win; match each statement to the records and follow the case instructions.

What does Mastercard reason code 4837 mean?

Mastercard reason code 4837 means the cardholder denies authorizing or participating in the transaction. It records a fraud allegation, not proof of the customer’s intent. Review authentication, account history and relevant transaction records against the actual case conditions. AVS/CVV results and delivery records may support the response, but none independently proves cardholder authorization.

What does Mastercard reason code 4808 mean?

Mastercard reason code 4808 means the transaction was processed without valid authorization or was submitted for settlement after the authorization window closed, subject to the case conditions. Processors often report several older authorization conditions under it, including required authorization not obtained, expired chargeback protection period, and account number not on file.

What does the reason code 4855 mean on a Mastercard chargeback?

Mastercard reason code 4855 refers to goods or services not provided. The 13 May 2025 merchant guide recommends 4853 for applicable cases while allowing the older 4855 label. Preserve the original case code and provide delivery or service records that address the complaint; confirm the current message-system mapping with your processor.

Does Mastercard’s 120-day chargeback time limit give merchants 120 days to respond?

No. A 120-day period in the relevant condition concerns the issuer’s filing window, not the merchant’s response allowance. The start event and exceptions depend on the condition and region. Track your processor’s response due date separately, then check any later-stage deadline with the acquirer if the case escalates.

Does a Mastercard reason code prove that the customer committed fraud?

No. It identifies a reported condition or allegation. Confirm the facts and applicable case conditions before labeling the cause or customer intent.

Should merchants use an old code list from a processor statement?

Read the actual statement and code context and the current provider mapping. Legacy numeric labels and current dispute conditions should not be assumed interchangeable without the provider's interpretation.

Get further background on any individual code from our reason-code database.

Connect relevant evidence collection and response submission with Chargeflow Automation. Get started now.