Mastercard Chargeback Reason Codes: The Full 2026 List

Mastercard is the second network most merchants deal with, and its reason-code system trips people up for one reason: the code number tells you nothing about the category. A Visa 13.1 announces itself as a consumer dispute. A Mastercard 4853 is just a number until you know the groups behind it.

This is the full 2026 reference for Mastercard chargeback reason codes. It covers how the codes are grouped, every code that matters to a card-not-present merchant, the evidence that wins each, and the key ways Mastercard differs from Visa — most importantly, the consolidated 4853 code.

How Mastercard reason codes are structured

Mastercard uses four-digit numeric codes, all beginning with 48 (a legacy of its older message-type numbering). The category is not encoded in the number, so you have to learn which group each code belongs to. There are four functional groups:

• Fraud — the cardholder claims they did not authorize the transaction, or a chip-liability shift applies.
• Authorization — the transaction was approved improperly.
• Point-of-interaction errors — the transaction was processed incorrectly.
• Cardholder disputes — a complaint about the goods or services received.

These map directly to the same four universal categories every network uses; Mastercard just numbers them differently. For the cross-network view, see the complete reason codes guide.

Fraud codes

Fraud is where card-not-present merchants spend most of their Mastercard time. As with every network, much of what arrives as “fraud” is actually friendly fraud — a real cardholder disputing a charge they made — which is why matching evidence to the exact code matters.

4837 (No Cardholder Authorization) is Mastercard’s flagship card-not-present fraud code, the counterpart to Visa’s 10.4. It is the code you will fight most often, and it is winnable with evidence that ties the transaction to the genuine cardholder. Our dedicated Mastercard reason code 4837 guide covers the winning approach in detail.

4863 (Cardholder Does Not Recognize) is worth distinguishing from 4837. Here the cardholder is not necessarily alleging fraud; they simply do not recognize the charge. These often resolve once you supply a clear merchant descriptor and transaction details, because the customer recognizes the purchase once reminded.

Authorization codes

Authorization disputes claim the transaction was approved when it should not have been. They are relatively uncommon for online merchants and are defended with authorization records.

Mastercard consolidated several older authorization reasons (required authorization not obtained, expired chargeback protection, and others) under 4808. The defense is documentary: your processor’s authorization records showing a valid approval.

Point-of-interaction error codes

These are Mastercard’s processing-error disputes — duplicates, wrong amounts, wrong currency, and similar mistakes.

Like 4808 on the authorization side, 4834 consolidates a range of older processing-error reasons: duplicate processing, incorrect amount, paid by other means, and late presentment among them. To win, show clean transaction records that contradict the specific error claimed — for a duplicate, proof the two charges are separate transactions.

Cardholder dispute codes

This is the group where Mastercard diverges most sharply from Visa, and where card-not-present merchants see the highest volume after fraud.

4853 (Cardholder Dispute) is the single most important Mastercard code to understand structurally. Mastercard consolidated what other networks split into many separate codes into this one broad code. A single 4853 can mean any of:

• Goods or services not received
• Goods or services not as described or defective
• Cancelled recurring transaction still billed
• Credit not processed (promised refund never issued)
• Cancelled merchandise or services

Because 4853 covers so much ground, the dispute will carry a sub-reason that narrows the claim. Read it, because it dictates your evidence:

4855 (Goods or Services Not Provided) overlaps with the not-received sub-reason of 4853 but is used specifically when the merchant failed to provide what was purchased — for example, a merchant that ceased operating before fulfilling. The defense is the same: proof of delivery or service provision.

How Mastercard differs from Visa

If you already know Visa’s system, three differences matter:

1. Consolidation. Visa splits consumer disputes into specific codes (13.1 not received, 13.2 cancelled recurring, 13.3 not as described, and so on). Mastercard folds nearly all of them into 4853 with a sub-reason. You get the same granularity, but you have to read the sub-reason to find it.
2. No category prefix. Visa’s 10.4 tells you it is fraud from the number alone. Mastercard’s 4837 tells you nothing until you know the groups. You must memorize or look up the group.
3. Longer response window. Mastercard typically gives merchants ~45 days to respond, versus roughly 20 to 30 for Visa — though, as always, your processor’s shorter internal deadline is the real one.

For the Visa side of this comparison, see the Visa chargeback reason codes guide.

Mastercard time limits

• Cardholder filing window: generally 120 days from the transaction or expected delivery, extended up to 540 days for interrupted or future-dated services.
• Merchant response window: roughly 45 days at the network level. Your processor’s internal deadline is shorter and governs your case — submit well before it, because a missed deadline forfeits the dispute automatically.

The bottom line

Mastercard’s codes reward merchants who learn the groups, because the numbers give nothing away. Fraud (4837, 4863) and cardholder disputes (the consolidated 4853, plus 4855) are where card-not-present merchants concentrate, and both are winnable — but only if you read the code and, for 4853, its sub-reason, then submit the exact evidence it calls for.

Assembling that evidence for every Mastercard code and sub-reason before the deadline is precisely the work automation handles well. DisputeDash reads the Mastercard code and sub-reason the moment your processor reports it, gathers the matched evidence — AVS/CVV, IP and device data, delivery tracking, refund records — and builds the rebuttal, so the right proof answers the right claim every time.