Mastercard Chargeback Reason Codes: The Complete 2026 List

Mastercard chargeback reason codes are the four-digit codes an issuing bank attaches to every disputed transaction, telling the merchant exactly why the charge is being reversed. Mastercard sorts every code into one of four categories: Authorization, Fraud, Cardholder Disputes, and Point-of-Interaction Error, and each category calls for different evidence in representment.

If chargebacks are new to you, start with our guide on what is a chargeback for the underlying mechanics, then come back here for Mastercard's specific codes. Mastercard simplified its taxonomy in 2016, consolidating a longer legacy list into 16 active codes, but several of the old numeric codes still appear on older processor statements and acquirer reports, which is why we've included a legacy-to-current mapping table below.

Mastercard's system runs in parallel with Visa's, and the two networks don't always code the same underlying complaint the same way. A cardholder disputing "goods not as described" gets reason code 4853 on a Mastercard transaction but 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) reads the same whether a card was genuinely stolen or whether the cardholder is disputing a purchase they made and simply regret, a pattern known as friendly fraud. That's why the evidence a merchant needs to win depends far more on the underlying story than on the code number itself.

The Complete Mastercard Chargeback Reason Codes List (2026)

Below is every active Mastercard chargeback reason code, organized by category. This is the full current list, not a sample of the most common ones.

Reason Code 4808: Authorization

4808 - Authorization-Related Chargeback

Mastercard reason code 4808 means the merchant either failed to secure authorization approval for a transaction or submitted the authorization request after the transaction date. Mastercard folded several retired codes into 4808, including required authorization not obtained, multiple authorization requests, expired chargeback protection period, late presentment on the authorization side, warning bulletin file matches, account number not on file, and unauthorized use of a Cardholder-Activated Terminal (CAT) device.

Evidence merchants need to win representment:

• The valid authorization approval code and timestamp, showing it was obtained before settlement
• Proof the transaction was submitted within 7 calendar days of authorization, or 30 days if a pre-authorization hold was used
• 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 covers disputes where the cardholder claims they did not authorize, approve, or participate in the transaction. Mastercard treats it as one of the primary fraud codes, and it can stem from a genuinely stolen card, a family member using the card without the primary holder's knowledge, or a cardholder who doesn't 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, typically pointing to a compromised terminal or skimmed card data used immediately after the legitimate sale.

4849 - Questionable Merchant Activity

Reason code 4849 is exclusive 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.

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
• 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 are 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. Mastercard has signaled it is phasing this code out and folding it into 4853, but issuers still use it, so merchants processing subscriptions should keep watching for it.

4853 - Cardholder Dispute

Reason code 4853, previously 4841 in an older numbering scheme, is Mastercard's broadest cardholder-dispute code. It covers cardholder and issuer disputes of recurring transactions, credit posted as a purchase, addendum disputes, goods or services not as described or defective, digital goods purchases of $25 or less, goods or services not provided, credit not processed, counterfeit goods, incomplete transactions, and no-show hotel charges under Mastercard's Guaranteed Reservation Service. Read the full reason code 4853 breakdown for every variation and its specific evidence requirements.

4854 - Cardholder Dispute, Not Elsewhere Classified

Reason code 4854 applies when a cardholder is dissatisfied with a transaction and asserts they could not resolve it directly with the merchant. It is exclusive to Mastercard's US region, requires the transaction to have occurred in the same state (or within 100 miles) of the cardholder's billing address, and only applies to transactions above $50. The cardholder's claim of an inadequate merchant response is often enough on its own to trigger the chargeback. Read the full reason code 4854 breakdown for the exact 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 exactly as it appeared at checkout, matched against what was actually delivered
• Subscription terms, renewal notices, and the cancellation policy the cardholder agreed to, critical for 4841 and recurring-billing disputes
• Communication logs showing the merchant attempted to resolve the issue directly, critical for defeating 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 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. Mastercard consolidated several older, narrower codes under 4834, covering double billing, 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. 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

Mastercard's 2016 simplification retired several older codes, but issuers and legacy processor systems still reference them from time to time. Here is how the retired codes map to today's active codes.

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

Merchants who process both networks quickly notice that the same customer complaint gets a different code depending on which network the card runs on. The categories map closely, but the numbering schemes don't, so a rule built around a Mastercard code number won't 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 rules, fees, and time limits.

Why Reason Code Accuracy Matters More in 2026

Mastercard has said global chargeback volume is on track to climb from roughly 261 million disputes in 2025 to 324 million by 2028, a 24% increase in three years, which means more disputes are landing in merchant inboxes with less time to sort the genuine fraud from the friendly fraud. Getting the reason code wrong at intake, and therefore pulling the wrong evidence, is one of the most common reasons a winnable dispute gets lost anyway.

That misclassification is expensive. According to LexisNexis Risk Solutions' True Cost of Fraud Study, every dollar a business loses to fraud and chargebacks now costs $5.13 once fees, merchandise loss, and labor are factored in, up 52.7% from five years earlier. Visa's own compliance data adds another pressure point for dual-network merchants: its VAMP dispute-ratio threshold tightened to 1.5% effective April 1, 2026, so Mastercard disputes that spill into a merchant's overall risk profile can indirectly push a Visa portfolio into enrollment territory too.

How to Win a Mastercard Chargeback Representment

Winning representment on any Mastercard reason code follows the same core workflow: identify the code, pull the evidence that code specifically requires, and submit before the deadline. Merchants get 45 days to submit representment after a first chargeback; cardholders generally get 120 days to file in the first place, or 90 days for authorization and point-of-interaction codes. For the full walkthrough of each stage, from first notice through arbitration, see our guide to the chargeback process.

Because Mastercard's fraud-code evidence bar is stricter than its cardholder-dispute bar, the fastest win is often prevention. 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 Mastercard's formal chargeback clock even 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 actually supports the evidence formats Mastercard expects. A mismatch here, evidence submitted in the wrong format or through the wrong channel, is one of the most common reasons a well-documented representment still gets rejected on a technicality rather than the merits.

One emerging complication for 2026: transactions initiated by an AI shopping agent rather than the cardholder directly. Merchants are already asking how AI agent chargeback liability will be assigned when a card-on-file agent completes a purchase the cardholder never personally clicked "buy" on, and Mastercard's current fraud codes were not written with that scenario in mind. Our Agentic commerce chargebacks evidence playbook covers what to capture at checkout to stay ahead of it.

Frequently Asked Questions

How many Mastercard chargeback reason codes are there?

There are 16 active Mastercard chargeback reason codes as of 2026, spread 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). Several additional legacy codes still appear on older systems but map to one of these 16.

What is the most common Mastercard chargeback reason code?

Reason code 4853 (Cardholder Dispute) is the most common in practice because it is Mastercard's broadest catch-all, covering goods not received, not as described, defective, or a credit that was never processed. Reason code 4837 (No Cardholder Authorization) is the most common of the fraud-specific codes.

What is Mastercard reason code 4853 used for?

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

How do Mastercard reason codes differ from Visa reason codes?

Both networks group disputes into four similar categories, 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?

Merchants generally have 45 calendar days to submit representment after a first chargeback is initiated. Cardholders have up to 120 days from the transaction date to file the original dispute, or 90 days for authorization and point-of-interaction categories.

Can a merchant win a Mastercard chargeback dispute?

Yes, when the merchant submits representment within the deadline and includes the exact evidence that reason code requires, such as authorization records for 4808, AVS/CVV and device data for fraud codes, or proof of delivery and cancellation terms for cardholder disputes. Cases with vague or missing evidence for the specific code cited are the ones most likely to lose, regardless of the underlying facts.

Get further background on any individual code from our reason-code database, or see the companion list of Discover chargeback reason codes. Contact our team for details on recovering Mastercard chargebacks on autopilot.