Mastercard Chargeback Reason Codes: What Shopify Merchants Actually Need to Check

The code tells you what the issuer is looking for — not what you think you already proved

When a Mastercard chargeback lands in Shopify Admin under Payments > Disputes, the reason code is the first thing to read carefully — not because it explains the cardholder's complaint, but because it tells you exactly what the issuer expects you to disprove. The two codes Shopify merchants encounter most are 4837 (No Cardholder Authorization) and 4853 (Cardholder Dispute — Goods or Services Not as Described). They require fundamentally different evidence packages, and conflating them is one of the fastest ways to lose a winnable case.

Code 4837 puts the burden on you to demonstrate that the transaction was authorized and that the goods reached the cardholder. Code 4853 requires documented proof that the item matched its description and that you made a good-faith attempt to resolve the issue directly with the customer before the dispute was filed. Submitting delivery confirmation against a 4853 dispute — or submitting a refund policy against a 4837 — signals to the issuer that you didn't read the code. Response deadlines vary by acquirer; confirm your exact window with your processor, because missing it forfeits the case regardless of how strong the evidence is.

Mastercard's dispute resolution timeline — what changed and what it means operationally

Mastercard has restructured its dispute resolution framework several times over the past decade, most significantly through its Dispute Resolution Initiative (MDRI), which rolled out in phases starting around 2018 and continued with refinements through 2022–2023. The core shift: Mastercard tightened the conditions under which issuers can file chargebacks and introduced pre-dispute requirements — meaning issuers are now expected to attempt resolution with the cardholder before filing certain dispute types. For merchants, this matters because it changed the evidentiary bar at second presentment and reduced some frivolous filings, but it also shortened the window in which merchants can respond effectively.

Mastercard also moved away from a purely numeric reason code system toward a hybrid structure that groups codes under broader dispute categories. The numeric codes (4837, 4853, 4855, etc.) remain in use and are what you'll see surfaced in most acquirer and Shopify dispute records, but the underlying rules governing each code have been updated. Confirm with your processor which version of the Mastercard rules your acquirer is operating under — rule interpretations at the issuer level can vary, and some acquirers lag on adopting updated frameworks. What this means practically: the evidence requirements described below reflect current Mastercard guidelines, but your acquirer's chargeback team may apply them with slight variation.

What to check in Shopify Admin before you build the response

Work through this in order. Skipping steps here is where operational losses happen — not at the evidence stage.

Dispute status and deadline. Go to Shopify Admin > Payments > Disputes. Confirm the dispute is still open and note the response deadline. If Shopify Protect status shows PROTECTED on the order, Shopify may cover the dispute — verify this before spending time building a response package.

Order details and address consistency. Pull up the order under Admin > Orders > Order Details. Check whether the billing address and shipping address match. A mismatch doesn't automatically mean fraud, but issuers flag it as a risk indicator under 4837. If there's a mismatch and no additional verification on file, the case is weaker than it looks.

AVS result. Go to Admin > Payments > Transaction Details. Confirm the AVS result was captured and what it returned. AVS Y is useful supporting evidence — it indicates the billing address matched the card issuer's records — but it does not prove the cardholder authorized the transaction or received the goods. Treat it as one data point, not a standalone defense. AVS result impacts can differ between Visa and Mastercard; confirm with your processor how much weight your acquirer assigns it.

Fulfillment and tracking status. Under Admin > Orders > Fulfillment, verify that tracking was updated promptly and that the carrier status shows delivered. Delayed shipment updates can cause merchants to miss the response window entirely on 4853 disputes, where perceived service failure is already the issuer's frame.

Customer communication log. Under Admin > Orders > Customer Communication, pull every interaction — pre-sale, post-sale, complaint threads, refund requests. For 4853, issuers require proof that you attempted to resolve the issue directly before the dispute was filed. No communication log means no defense on service disputes. DisputeDesk organizes this evidence into a structured response package, but the merchant still needs to verify that the communication record is complete and accurate before submission.

Fight or accept. Run the math. If the order value is below your processor's dispute fee threshold, or if the evidence gaps are significant, accepting may be the lower-cost outcome. A weak response doesn't just lose — it can affect your dispute ratio.

Shopify Payments vs. third-party gateways — how reason codes surface differently

If you're on Shopify Payments, dispute records appear directly in Admin > Payments > Disputes with the reason code pre-populated, a response deadline surfaced in the UI, and a structured evidence submission interface. Shopify Payments is powered by Stripe on the back end, which means the reason code you see has already been translated from the raw Mastercard code into Shopify's dispute interface — in most cases the mapping is accurate, but the label in the UI may be a plain-language category rather than the raw numeric code. Always cross-reference with your processor statement or dispute notification email to confirm the exact Mastercard code before building your response.

If you're running a third-party gateway — Braintree, Authorize.net, PayPal, or a direct acquirer integration — dispute records do not appear in Shopify Admin's Disputes section at all. You'll receive chargeback notifications through the gateway's own portal or by email, and you'll submit evidence through that gateway's interface, not through Shopify. The Shopify order record is still your primary source for fulfillment data, communication logs, and order details, but the dispute workflow lives entirely outside Shopify Admin. This matters because third-party gateways vary significantly in how much time they give you to respond, how they surface the raw reason code, and what evidence formats they accept. Confirm all of this with your gateway before a dispute lands — not after.

One practical difference: Shopify Payments merchants benefit from Shopify Protect on eligible orders, which can cover the disputed amount entirely. Third-party gateway merchants have no equivalent protection. If you're evaluating gateway options and chargebacks are a meaningful cost center, that asymmetry is worth factoring in.

Major Mastercard reason codes Shopify merchants actually see

4837 — No Cardholder Authorization

The cardholder is claiming they did not authorize the transaction. This is the most common fraud-adjacent code and the one most merchants respond to incorrectly. The issuer's question is narrow: did the legitimate cardholder initiate this purchase? Everything else — whether the goods were delivered, whether the product was as described — is secondary until you answer that question.

What the issuer needs to see: Evidence that the transaction was authorized by the cardholder. This means: AVS match (Admin > Payments > Transaction Details), billing/shipping address consistency (Admin > Orders > Order Details), CVV match if captured, device fingerprint or IP address data if available through your fraud tools, and — most decisively — post-delivery communication from the cardholder that places them in contact with the order after it arrived. A return request, a complaint email, a chat thread referencing the order: any of these directly contradicts an unauthorized transaction claim.

The trap: Merchants submit AVS Y plus carrier delivery confirmation and consider the case covered. AVS Y confirms the billing address matched the card issuer's records — it does not confirm the cardholder placed the order. Delivery confirmation confirms the package reached the address — it does not confirm the cardholder received it. Issuers handling 4837 disputes know that account takeover and card-present data theft can produce both. Without post-delivery cardholder contact or signature confirmation, you've proved fulfillment, not authorization.

Fight vs. concede: Fight if you have post-delivery cardholder communication, signature confirmation, or strong device/IP data tying the order to the cardholder. Concede if the only evidence is AVS Y and tracking — the case is weak and a loss affects your dispute ratio.

4853 — Cardholder Dispute (Goods or Services Not as Described or Not Received)

The cardholder is claiming either that the goods or services didn't match what was advertised, or that they never received them. This code covers a wide range of complaints — wrong item, damaged item, significantly not as described, or non-delivery — and the evidence package shifts depending on which sub-claim is in play.

What the issuer needs to see: For not-as-described: your product listing at the time of purchase (screenshot or archived version), photos of what was shipped if available, and documented communication showing the customer described the problem and you responded with a resolution offer. For not-received: carrier tracking showing delivered (Admin > Orders > Fulfillment), shipping confirmation with timestamp, and any post-shipment communication. In both cases, the issuer wants to see that you attempted to resolve the issue before the dispute was filed.

The trap: Submitting the order confirmation email as the primary evidence. That email confirms purchase terms were communicated before the problem arose — it doesn't address the dispute at all. For not-as-described claims, merchants also frequently submit their return policy without showing they actually offered a resolution. Issuers want to see the exchange, not the policy.

Fight vs. concede: Fight if you have documented resolution attempts and the product listing clearly matches what was shipped. Concede if there's no communication log, if the product genuinely differed from the listing, or if the customer never received a response from you before filing.

4855 — Goods or Services Not Provided

The cardholder is claiming they paid for something that was never delivered — digital or physical. This is distinct from 4853 in that the claim is pure non-delivery, not a quality or description dispute.

What the issuer needs to see: Proof of delivery or proof of service fulfillment. For physical goods: carrier tracking with delivery confirmation (Admin > Orders > Fulfillment), ideally with signature. For digital goods: access logs, download records, IP-timestamped delivery confirmation, or email delivery receipts showing the digital product was sent and accessed. For services: completion documentation, client sign-off, or service delivery records.

The trap: For digital merchants, submitting only the order confirmation email. That proves the purchase was processed — not that the digital product was delivered or accessed. Access logs or download records are what close this case.

Fight vs. concede: Fight if you have carrier confirmation with signature or digital delivery logs. Concede if the item genuinely wasn't delivered or if the only proof is an internal order record with no external delivery confirmation.

4863 — Cardholder Does Not Recognize Transaction

The cardholder is not claiming outright fraud — they're claiming they don't recognize the charge. This is softer than 4837 and often resolves at the issuer level if the merchant can provide enough context for the cardholder to identify the purchase. It can, however, escalate to a full fraud claim if the merchant's response doesn't clarify the transaction.

What the issuer needs to see: Transaction details that help identify the purchase — merchant descriptor as it appeared on the statement, order date, item description, billing address used, and any communication sent to the cardholder at the time of purchase. The goal is to give the issuer enough to go back to the cardholder and say: here's what this charge was.

The trap: Treating 4863 like a 4837 and submitting a full fraud defense package. The cardholder may simply not recognize your merchant descriptor — a common issue for Shopify stores whose billing descriptor doesn't match their storefront name. Check what descriptor appears on Mastercard statements (Admin > Payments > Settings or through your processor) and include it explicitly in the response.

Fight vs. concede: Almost always worth responding with transaction context. The bar is low and many 4863 disputes resolve without escalation once the issuer has enough detail to identify the charge.

4834 — Duplicate Processing

The cardholder is claiming the same transaction was processed more than once. This is an operational error claim, not a fraud claim.

What the issuer needs to see: Transaction records showing that only one charge was processed for the order (Admin > Payments > Transaction Details). If a duplicate did occur — a double-click at checkout, a payment retry that processed twice — the correct response is to issue a refund for the duplicate immediately, not to fight the chargeback.

The trap: Merchants sometimes submit order confirmation emails for both transactions as evidence that both were legitimate orders. If the cardholder only placed one order and two charges appeared, that's a duplicate regardless of whether two order records exist.

Fight vs. concede: Fight only if transaction records clearly show a single charge and the cardholder is mistaken. If a duplicate charge occurred, refund it and document the refund in your response — fighting a legitimate duplicate processing claim damages your relationship with the issuer.

4831 — Transaction Amount Differs

The cardholder is claiming the amount charged differs from what they agreed to pay. This covers unauthorized price changes, currency conversion disputes, and tip or surcharge additions the cardholder didn't authorize.

What the issuer needs to see: The original order total as agreed at checkout (Admin > Orders > Order Details), the transaction amount as processed (Admin > Payments > Transaction Details), and documentation showing the cardholder agreed to the final amount — checkout confirmation, order summary email, or signed receipt if applicable.

The trap: Submitting only the transaction record without showing what the cardholder agreed to at checkout. If the amounts match, the case is straightforward. If there's a discrepancy — a currency conversion the cardholder didn't anticipate, a shipping surcharge added post-checkout — the merchant needs to show where the cardholder was informed of the final amount before the charge processed.

Fight vs. concede: Fight if the amount charged matches the agreed checkout total and you can document it. Concede or refund the difference if a surcharge or conversion wasn't clearly disclosed.

4807 — Warning Bulletin File

The card used in the transaction appeared on Mastercard's warning bulletin — a list of cards flagged for fraud or compromise. This is an authorization-level failure, meaning the transaction should not have been approved in the first place.

What the issuer needs to see: This code is difficult to fight because the liability typically rests with the merchant for accepting a flagged card. The primary defense is demonstrating that your payment system performed the required authorization checks and that the card was not on the bulletin at the time of the transaction. Confirm with your processor whether your authorization setup queries the warning bulletin in real time.

Fight vs. concede: Concede in most cases unless your processor can confirm the card was not flagged at the time of authorization. This is a technical dispute that requires processor-level documentation, not merchant-level evidence.

Code-to-evidence mapping

The $480 apparel order that AVS and tracking couldn't save

An apparel merchant processed a $480 order on March 1st. AVS returned Y — billing address matched. The order shipped March 3rd. Carrier tracking marked it delivered March 5th. On March 10th, the cardholder filed a chargeback under reason code 4837, claiming the transaction was unauthorized.

The merchant submitted the standard package: AVS Y match, tracking confirmation showing delivered, and the order confirmation email. On paper, it looked covered. The issuer upheld the chargeback.

Here's where the case fell apart. AVS Y confirms that the billing address on file with the issuer matched what the merchant submitted — it does not confirm that the cardholder placed the order or that they received the package. Tracking marked delivered confirms the carrier dropped the package at the address — it does not confirm the cardholder personally received it. The order confirmation email confirms the purchase terms were sent — it does not confirm the cardholder was the one who placed the order. Three pieces of evidence, none of which directly addressed the issuer's actual question: did the cardholder authorize this transaction and take possession of the goods?

The better response would have included post-delivery customer communication — any message from the cardholder referencing the order after the delivery date, a return request, a complaint, anything that places the cardholder in contact with the order after it arrived. That kind of evidence directly contradicts an unauthorized transaction claim. Without it, the merchant handed the issuer a clean path to uphold the dispute.

The billing address and shipping address also matched on this order — which the merchant didn't flag in the response. Noting address consistency, combined with AVS Y, would have strengthened the authorization argument. Neither alone is decisive, but together they narrow the issuer's room to sustain a fraud claim.

Decision lesson: AVS Y plus delivery confirmation is a starting point, not a complete defense. A 4837 case is fightable when you can show post-delivery contact from the cardholder or a signature confirming receipt. Without either, the evidence package proves fulfillment — not authorization — and issuers know the difference.

What evidence actually moves issuers — and what doesn't

AVS Y, delivery confirmation, and order acknowledgment emails are the three pieces of evidence most merchants default to. All three have real weaknesses that experienced issuers will cite.

AVS Y is useful as corroboration — it shows the billing address matched, which is a friction point for fraudsters. But it doesn't prove the cardholder authorized the transaction, and issuers handling 4837 disputes know that account takeover and card-present data theft can produce AVS matches. Frame AVS Y as part of a broader set, not the centerpiece.

Tracking marked delivered is similarly limited. Carrier confirmation shows the package reached the address — it doesn't show who received it. For high-value orders, signature confirmation at delivery is the evidence that closes this gap. If the order shipped without signature required, that's a fulfillment decision that weakens the dispute response. Pair delivery confirmation with any post-delivery customer communication to reinforce that the cardholder interacted with the order after it arrived.

Customer acknowledgment emails — order confirmations, shipping notifications — confirm that the purchase terms were communicated. They don't prove receipt or satisfaction. For 4853 disputes, what issuers want to see is evidence of your resolution attempt: a refund offer, a replacement offer, a documented exchange where the customer described the problem and you responded. An order confirmation email sent before the problem arose doesn't address the dispute at all. Mastercard's interpretation of reason codes can vary by issuer; confirm with your processor how your acquirer weights each evidence type for the specific code you're responding to.

Pre-arbitration and second presentment — which codes escalate and what changes

If the issuer upholds the chargeback after your first response, you may have the option to escalate to second presentment (also called re-presentment) and, beyond that, to pre-arbitration. Not every code is worth escalating, and the evidentiary bar rises at each stage.

4837 disputes escalate most frequently. If your first response was rejected, the issuer has already reviewed your authorization evidence and found it insufficient. At second presentment, you need materially new evidence — not a repackaged version of what you already submitted. Post-delivery cardholder communication that wasn't in the first response, a signed delivery confirmation that wasn't included, or device/IP data from your fraud platform that ties the session to the cardholder's known behavior are the categories that can shift the outcome. Resubmitting AVS Y and tracking after a first-response loss is not a second presentment strategy — it's a way to confirm the issuer's original decision.

4853 disputes escalate when the merchant can show that a resolution was offered and rejected before the dispute was filed, or that the product genuinely matched its description and the cardholder's claim is demonstrably inaccurate. At pre-arbitration, Mastercard itself reviews the case, and the losing party pays arbitration fees — currently in the hundreds of dollars. Before escalating a 4853 to pre-arbitration, confirm with your processor that the transaction value justifies the fee exposure and that your evidence package is materially stronger than what the issuer already reviewed.

4863 disputes rarely reach second presentment because they typically resolve at first response if the merchant provides sufficient transaction context. If a 4863 escalates, it usually means the cardholder has upgraded the claim to outright fraud — at which point it effectively becomes a 4837 and should be treated as one.

4834 and 4831 disputes almost never reach pre-arbitration. If the merchant's records show a single charge at the agreed amount, the case resolves at first response. If the records show a duplicate or a discrepancy, the correct action is a refund, not escalation.

One procedural note: Mastercard's pre-arbitration process has specific filing deadlines that are tighter than first-response windows. Confirm the exact timeline with your processor before deciding to escalate — missing the pre-arbitration filing deadline closes the option permanently. DisputeDesk tracks escalation deadlines and flags cases where second presentment evidence is materially stronger than the first response, so merchants aren't making that call blind.