The Mastercard chargeback reason codes a Shopify store actually sees


TL;DR
Almost every Mastercard dispute on Shopify carries one of five codes: 4837 (no cardholder authorization), 4863 (cardholder does not recognize), 4853 (cardholder dispute, with several sub-conditions), 4834 (point-of-interaction error), and 4855 (goods or services not provided). Mastercard's current Chargeback Guide no longer lists 4863 or 4855 as standalone codes; both now run through 4837 and 4853. Below is what each code alleges, the Shopify evidence that answers it, and the Visa code it maps to.
A Mastercard dispute on Shopify carries a four-digit code, and in practice it is almost always one of five: 4837, 4863, 4853, 4834, or 4855. I read Mastercard's current Chargeback Guide to check what each one still means, and two of the five, 4863 and 4855, are not in it anymore. Here is what each code alleges, the Shopify evidence that answers it, and the Visa code it lines up with if that is the list you already know.
Why two of these five codes are not in the current guide
Mastercard revises its Chargeback Guide on a rolling basis, and a lot of what ranks for these code numbers is quoting an old edition. The copy I checked, the Chargeback Guide, Merchant Edition, dated 19 May 2026 and published at mastercard.com, does not contain the string 4863 anywhere in it. It does not contain 4855 either. Neither does the 13 May 2025 edition before it.
The allegations behind both numbers still happen constantly. Cardholders still say they do not recognize a charge, and goods still fail to arrive. Mastercard just does not track either one as its own numbered code anymore.
Note
Reason codes 4863 and 4855 are gone from Mastercard's current Chargeback Guide. The allegations still exist. 4863 now argues through 4837, no cardholder authorization. 4855 runs through 4853, cardholder dispute, as a named sub-condition rather than a code of its own.That is worth knowing before you build a response, because your processor might still hand you the old number. Stripe's own reason-code documentation, current as of this writing, still lists 4863 under an "Unrecognized" category and 4855 under "Product not received," separate from Mastercard's own guide. So the number on your dispute record could be either the retired code or its replacement, depending on which system generated it. Build the evidence off the allegation, not off the four digits.
The five codes, what they allege, and the Shopify evidence that answers each
Match the evidence to the specific claim, not to the fact that an order happened. Nobody is disputing that a purchase occurred. That is the same discipline behind chargeback representment explained without the vendor spin, applied here per Mastercard code instead of in general.
| Mastercard code | What the cardholder alleges | Shopify evidence that answers it | Visa equivalent |
|---|---|---|---|
4837 | No cardholder authorization: someone other than the cardholder made the purchase | AVS and CVV match results, 3-D Secure or other authentication data, the purchase IP and device data, and for a repeat customer, prior undisputed orders on the same card | 10.4 |
4863 | Cardholder does not recognize the transaction, filed as potential fraud | The same authorization evidence as 4837, plus the billing descriptor shown at checkout and any support message that references the order | No distinct Visa code; Visa runs this through 10.4 too |
4853 | Cardholder dispute: not as described or defective, goods or services not provided, or a cancelled recurring charge, depending on the sub-condition | The product page and specs as of the purchase date, carrier tracking with a delivery scan, or the subscription terms and cancellation log, matched to the specific sub-condition | 13.3, 13.1, or 13.2 |
4834 | Point-of-interaction error: billed twice, or the amount charged does not match the record | Transaction and settlement logs showing one successful charge, receipts distinguishing two genuinely separate charges, or a void and refund record | 12.6.1 |
4855 | Goods or services were never provided (now a named sub-condition inside 4853, not a standalone code) | Carrier tracking with a delivery scan, digital access or download logs, or service completion records | 13.1 |
Reason codes get revised between editions, as the last section just showed. Pull the current guide for the network in question rather than working from a saved list, mine included.
4837 and 4863 argue the same thing
Both codes are asking the same question: was this cardholder actually the one who authorized the charge. Mastercard's guide asks for address and card verification results, authentication data where 3-D Secure or an equivalent ran, and for repeat customers, a compelling-evidence path built on prior undisputed orders on the same card. That is a parallel concept to Visa's Compelling Evidence 3.0 under 10.4, not an identical test. Mastercard's own qualifying criteria are set in its guide, so do not assume Visa's window applies here too.
A 4863 case is the one most likely to actually be a billing descriptor problem rather than real fraud. A cardholder who does not recognize CORP*RDO on a statement is not lying about not recognizing it. If a meaningful share of your fraud-coded disputes are first-time customers on small orders, that pattern is worth checking against your descriptor before you assume it is criminal activity.
4853 absorbed 4855, and the sub-condition is what decides your evidence
4853 is the broadest of the five, and it is also the one where reading only the top-level code number gets you nowhere. The sub-condition, not-as-described, goods not provided, or cancelled recurring, is what tells you which evidence to pull.
Not as described or defective needs the product page and images as they stood on the purchase date, not today's listing, plus the exact variant ordered and the support thread if one exists.
Goods or services not provided, the allegation that used to carry its own code as 4855, needs carrier tracking with an actual delivery scan, the delivery address matched against the order, and a signature where the carrier captured one.
Cancelled recurring transaction still billed needs the terms accepted at signup, a cancellation log showing nothing filed before the renewal, and the renewal notice sent.
Assembling that packet by hand runs 20 to 45 minutes per case, and it is exactly what Reclaim assembles automatically once a dispute lands on a connected store, at no cost to install and no cut of what comes back.
4834 is bigger than duplicate billing
Stripe's documentation still calls 4834 "Duplicate Processing of a Transaction." Mastercard's current guide calls it "Point-of-Interaction Error," and the wider name matters, because the code covers more than a double charge. It also covers a mismatch between the amount authorized and the amount settled, and currency conversion errors at the point of sale.
If the allegation really is a duplicate charge, pull the transaction and settlement logs showing a single successful charge went through, or, if two charges genuinely happened, receipts that distinguish what each one paid for. A voided or refunded second attempt that still shows on a statement is the most common real cause, and the fix is proving the void or refund posted before the dispute was filed.
The honest part
There is no single response-window number for a Mastercard dispute, and a table that hands you one is guessing. Mastercard's own guide sets timeframes by code and by region, and those timeframes get revised, which is exactly how 4863 and 4855 disappeared as standalone entries between editions. A hardcoded day count in this article would risk being wrong for at least one of the five codes above by the time you read it.
What is stable is what shows up on your own dispute. Shopify's help documentation puts the practical window at 7 to 21 days depending on the case, shown as a due date on the dispute record in your admin, and that number applies whether the network behind it is Mastercard or Visa. Treat that date as the real one, set an internal cutoff a couple of days earlier, and confirm anything longer with your processor before you rely on it.
Nobody can promise you a win either. The issuing bank decides, and once it does, there is no second submission. The same evidence discipline that wins a 13.1 case wins a 4855 one, which is the approach in how to win a Shopify chargeback with evidence that answers the reason code. What changes between networks is the number on the case, not the argument you have to make.
Frequently asked questions
What is Mastercard reason code 4837?
No Cardholder Authorization. The cardholder claims someone other than them made the purchase. The evidence that answers it is proof the transaction was authorized: AVS and CVV match results, 3-D Secure or other authentication data, IP and device data, and, for repeat customers, prior undisputed orders on the same card.
Is Mastercard reason code 4863 still active?
It no longer appears as a standalone code in Mastercard's current Chargeback Guide (checked in the 19 May 2026 edition). The allegation it covered, the cardholder does not recognize the transaction, now argues through 4837. Some processors, including Stripe's own documentation, still reference 4863 directly, so you may see either number depending on your setup.
What does Mastercard reason code 4853 cover?
Cardholder Dispute, a broad category with several sub-conditions: not as described or defective, goods or services not provided, and a cancelled recurring transaction still billed, among others. The sub-condition, not the top-level code, determines which evidence answers the case.
How does Mastercard reason code 4834 differ from a Visa duplicate-processing dispute?
The allegation is the same core claim, being billed twice or an amount mismatch, and it maps to Visa's 12.6.1. Mastercard's current name for 4834 is Point-of-Interaction Error, which is broader than duplicate billing alone; it also covers amount and currency discrepancies at the point of sale.
What to check on your next Mastercard dispute
Pull the actual four-digit code off the dispute record rather than trusting Shopify's short label like "fraudulent" or "unrecognized." If it reads 4863 or 4855, treat it as the current guide does: build the fraud packet for 4863, and build the delivery or service-completion packet for 4855 under its 4853 sub-condition. The code number tells you which system generated it. The allegation is what you actually have to answer.