Mastercard Chargeback Reason Codes List 2026: Claim Evidence

A Mastercard chargeback reason code classifies the dispute condition reported in a case. The merchant must read the complaint and current processor instructions as well as the code before choosing evidence.

Mastercard chargeback reason codes, also called Mastercard dispute reason codes, are four-digit codes an issuing bank attaches to a disputed transaction to record the reported condition. Processor references such as Adyen's dispute reason-code reference group them into four families: Authorization, Fraud, Cardholder Disputes, and Point-of-Interaction Error. Each family calls for different evidence in representment, and conditions differ by reason, message system, region and stage, as the Mastercard Chargeback Guide, Merchant Edition (13 May 2025) explains.

If chargebacks are new to you, start with our guide on what is a chargeback for the underlying mechanics, then come back here for the codes. If you searched for a Mastercard chargeback guide 2026 edition, note that the current official merchant guide is dated May 2025 and this page is the code-to-claim lookup; the stages, deadlines and Mastercard chargeback rules are covered in the full guide. Some older numeric codes still appear on older processor statements and acquirer reports, so a legacy-to-current mapping table is included below, with the caveat that a provider's own interpretation decides.

Mastercard's system runs in parallel with Visa's, and the two networks do not always code the same underlying complaint the same way. A cardholder disputing "goods not as described" is commonly shown under 4853 on a Mastercard transaction but under a different code on a Visa one. We cover that mapping, and what it means for merchants who process both networks, later in this guide.

Reason codes were built for tracking payment issues, not for revealing intent. A code like 4837 (No Cardholder Authorization) records a claim of no authorization. It reads the same whether a card was genuinely stolen or the cardholder is disputing a purchase they made, a pattern known as friendly fraud, so a code alone does not establish the cause or the customer's intent. The evidence a merchant needs depends far more on the underlying story than on the code number.

{{cta}}

Mastercard Chargeback Reason Codes List (2026)

The table below is a chargeback reason codes list of the Mastercard chargeback codes merchants commonly see, organized by category. It is a lookup aid, not a complete list for every region and message system, and it should not replace the code, message text and instructions on your own case. Check the current Mastercard guide and your processor's mapping before relying on any one row.

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.

A Code Narrows the Question; the Complaint Selects the Proof

The code tells you which family of claim to expect. The complaint, the case notes and the processor instructions tell you which records actually answer it. Use the table below to match a claim family to the records that usually apply, and to see where a common packet falls short. Where those records live is covered in our guide to chargeback evidence sources.

Illustrative case, not a real dispute: two cases use 4853, but one alleges a canceled recurring payment and the other nonreceipt. Use cancellation and billing records for the first, and item-to-delivery records for the second. The common code does not make their evidence requirements identical.

Reason Code 4808: Authorization

4808 - Authorization-Related Chargeback

Mastercard reason code 4808 (the 4808 chargeback reason code) means the merchant either failed to secure authorization approval for a transaction or submitted the authorization request after the transaction date, subject to the conditions on the case. Processors often report a number of older, narrower authorization conditions under 4808, such as required authorization not obtained, multiple authorization requests, expired chargeback protection period, warning bulletin file matches, account number not on file, and unauthorized use of a Cardholder-Activated Terminal (CAT) device. Confirm the mapping with your provider.

Evidence merchants need to win 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

Common merchant mistakes that lose this dispute:

• 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 - No Cardholder Authorization

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. Read the full reason code 4837 breakdown for the complete evidence checklist.

4840 - Fraudulent Processing of Transactions

Reason code 4840 applies when multiple, separate transactions are processed in a short window following one card-present purchase the cardholder did authorize, which can point to a compromised terminal or skimmed card data used immediately after the legitimate sale.

4849 - Questionable Merchant Activity

Reason code 4849 is tied to merchants enrolled in Mastercard's Global Merchant Audit Program (GMAP), which targets high-risk merchants or those with unusually high transaction volumes. It can also apply to acquiring banks processing for a merchant named in a Mastercard Global Security Bulletin or flagged under the Mastercard Scam Merchant Monitoring Program.

4863 - Cardholder Does Not Recognize, Potential Fraud

Reason code 4863 covers card-not-present transactions the cardholder does not recognize on their statement and flags as suspected fraud, distinct from 4837 in that the cardholder is reporting uncertainty rather than a definite denial.

4870 and 4871 - Chip and Chip/PIN Liability Shift

Reason code 4870 applies when a counterfeit EMV chip card was used at a terminal that was not chip-capable, shifting fraud liability to the merchant under Mastercard's EMV liability shift rules. Reason code 4871 applies the same liability shift to a lost, stolen, or never-received chip card used at a non-compliant terminal.

Evidence merchants need to win 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 specifically: proof the merchant was not listed in the relevant Global Security Bulletin during the disputed period

Common merchant mistakes that lose this dispute:

• 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 GMAP or security bulletin 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 identifies a cardholder who was billed for a recurring payment or digital good after canceling, or without ever giving consent. Some processors and statements now show these claims under 4853, while 4841 still appears on others, so merchants processing subscriptions should watch for both and confirm the mapping with their provider.

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 merchants need to win 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

Common merchant mistakes that lose this dispute:

• 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 applies when the settled amount differs from what the cardholder authorized. Reason code 4842 covers late presentment, when a transaction is submitted for settlement outside Mastercard's required window (see our full breakdown of reason code 4842). Reason code 4846 applies when the wrong currency code was used or a required DCC disclosure was missing. Reason code 4850 covers disputed installment billing charges. Reason code 4999 is limited to Europe and applies when a sale was processed rather than the credit that should have been issued.

Evidence merchants need to win 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

Common merchant mistakes that lose this dispute:

• 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.

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

Merchants who process both networks quickly notice that the same customer complaint can get a different code depending on which network the card runs on. The categories map loosely, but the numbering schemes do not, so a rule built around a Mastercard code number will not automatically catch the Visa equivalent.

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.

Why Reason Code Accuracy Matters More in 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

Winning representment on any Mastercard reason code follows the same core workflow: identify the code and the complaint behind it, pull the evidence that claim specifically requires, and submit before the deadline. Deadlines depend on the case. Figures such as 45 days for a merchant response, or 120 days (sometimes 90) for a cardholder to file, appear in secondary guides, but conditions under Mastercard dispute rules differ by reason code, message system, region and stage, so use the due date in your processor's case notice rather than a fixed number. For the full walkthrough of each stage, from first notice through arbitration, see our guide to the chargeback process.

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}}

Frequently Asked Questions

How many Mastercard chargeback reason codes are there?

There is no single count that fits every region, message system and provider. The table in this guide lists 16 codes across four categories: Authorization (4808), Fraud (4837, 4840, 4849, 4863, 4870, 4871), Cardholder Disputes (4841, 4853, 4854), and Point-of-Interaction Error (4831, 4834, 4842, 4846, 4850, 4999). Older codes may still appear on legacy systems, so check your provider's mapping rather than treating the list as complete.

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?

It depends on the case. Conditions differ by reason code, message system, region and stage, and the actual deadline is the due date your processor shows on the case. Secondary guides often cite 45 days for a merchant response and 120 days (or 90 for some categories) for a cardholder to file, but those figures should not be treated as universal. Check the current Mastercard guide and your processor's instructions.

Can a merchant win a Mastercard chargeback dispute?

Yes, when the merchant submits representment within the deadline and includes the evidence that fits the claim, such as authorization records for 4808, AVS/CVV and device data for fraud codes, or proof of delivery and cancellation terms for cardholder disputes. Responses with vague or missing evidence for the cited condition are the ones most likely to lose.

What does Mastercard reason code 4837 mean?

Mastercard reason code 4837 means the cardholder is telling their issuer they never authorized, made, or benefited from the transaction, which is why it is classed as a fraud code rather than a cardholder-dispute code. It can follow a stolen card or a cardholder who does not recognize the merchant name, so AVS/CVV match data and device history carry the most weight, and delivery evidence alone does not prove 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.

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.