Shopify Issuer Claim: The Pre-Submission Checklist That Changes Your Odds

The claim is already filed. Start here.

When an issuer claim surfaces in Shopify Admin → Payments → Disputes, the cardholder's bank has already made a preliminary decision: something went wrong, and the merchant needs to answer for it. The claim label tells you the dispute is live, the response window is running, and the issuer has a specific question they expect you to answer — not a general one.

Most merchants open the dispute, look at the dollar amount, and start pulling screenshots. That's the wrong sequence. Before you touch evidence, you need to verify five things. Getting any one of them wrong means you're building a response to the wrong question, or submitting evidence that doesn't map to what the issuer is actually evaluating.

Do this in order.

Step 1: Confirm the claimed amount matches the order

Open the dispute record in Shopify Admin → Payments → Disputes and compare the disputed amount to the original order total. They won't always match.

Partial-amount claims happen when a cardholder disputes one item from a multi-item order, or when a partial refund was already issued and the issuer's system didn't register it. If the disputed amount is lower than the order total, your evidence needs to address only the claimed portion — not the full transaction. Submitting a full-order receipt against a partial claim creates confusion and sometimes triggers issuer skepticism about whether you understand your own transaction.

If the disputed amount is higher than the order total, flag it immediately. That's a processor data error or a duplicate dispute. Confirm with your processor before submitting anything.

Internal note template: "Dispute [ID] — claimed $[X], order total $[Y], delta $[Z]. Reason: [partial refund already issued / processor error / unknown]. Confirm before building response."

Step 2: Read the reason code before you read the order

The reason code is the issuer's stated basis for the claim. It tells you what evidence wins — not what you think you already proved.

Shopify surfaces the reason code in the dispute detail view. The three categories you'll see most often:

• Fraud / Unauthorized (Visa 10.4, Mastercard 4837): The cardholder says they didn't authorize the transaction. The issuer wants authorization evidence — AVS, CVV, device fingerprint, behavioral signals. Delivery proof alone doesn't win this.
• Item Not Received / INR (Visa 13.1, Mastercard 4853-INR): The cardholder says the goods never arrived. The issuer wants delivery confirmation tied to the correct address. Authorization evidence alone doesn't win this.
• Not as Described / SNAD (Visa 13.3, Mastercard 4853-SNAD): The cardholder says what arrived didn't match what was advertised. The issuer wants product description evidence — listing copy, images, specs. Tracking numbers don't win this.

Merchants lose winnable claims by submitting the wrong evidence type. A merchant with a clean delivery confirmation for a fraud-coded dispute is answering a question the issuer didn't ask. The reason code is the question. Build the answer to that question specifically.

One sharp observation worth internalizing: the reason code and the cardholder's actual complaint are often different things. A customer who received a damaged item sometimes files under fraud because that's what the bank's dispute form defaulted to. The issuer evaluates based on the code they received — not the customer's real grievance. If the code doesn't match the customer's stated complaint in their pre-dispute contact with you, note that discrepancy in your response narrative. It matters.

Step 3: Pull the customer's full contact history before the dispute was filed

This is the check most merchants skip, and it's the one that most often changes the response strategy.

Go to the order in Shopify Admin → Orders → [Order] and review every customer-initiated contact: emails, chat logs, return requests, refund requests, anything timestamped before the dispute date. Then check your email platform or helpdesk for the same customer — Shopify's native timeline doesn't always capture every channel.

What you're looking for:

• Did the customer contact you about this order before filing the claim? If yes, what did they say, and how did you respond?
• Did you offer a resolution — refund, replacement, return label — that the customer accepted and then disputed anyway?
• Did the customer make no contact at all before the claim? That's a signal worth noting in your response narrative.

A merchant shipped a $220 skincare order. The customer emailed three days after delivery saying the wrong shade was sent. The merchant replied with a return label and a replacement offer. The customer never responded — and filed a chargeback two weeks later under "item not as described." The merchant almost submitted a standard SNAD response. Instead, they led with the contact thread: customer acknowledged receipt, merchant offered resolution, customer did not engage before filing. The issuer sided with the merchant.

Without pulling that contact history first, the response would have been weaker — and probably would have lost.

Step 4: Verify fulfillment status and carrier data

In Shopify Admin → Orders → [Order] → Fulfillments, confirm:

• Fulfillment was marked complete before the dispute date (not after — post-dispute fulfillment updates are a red flag to issuers)
• The shipping address on the fulfillment record matches the billing address, or if it doesn't, that you have a documented reason
• The carrier tracking number is active and returns a delivery scan, not just a label-created event
• If signature confirmation was required, that the carrier record shows it was obtained

"Label created" is not delivery. Issuers know this. Submitting a tracking number that only shows a label event — no carrier scans, no delivery confirmation — is worse than submitting nothing, because it signals you're not reading your own evidence carefully.

Also check whether the shipping address is a freight forwarder, reshipping address, or package locker. These don't automatically mean fraud, but they change the evidence you need. A delivery to a reshipping address with no prior customer contact is a harder fight than a delivery to a residential address with a signature scan.

Decision point: fight the claim or accept it now

Before you build a single piece of evidence, make this call explicitly.

Path A — Submit a response: You have the reason code mapped, the contact history reviewed, fulfillment confirmed, and at least two strong evidence signals that directly answer the issuer's question. The disputed amount exceeds your internal threshold for response effort. Go build the response.

Path B — Accept the dispute: The evidence is thin, the reason code doesn't match your available proof, the customer has a documented complaint you didn't resolve, or the disputed amount is below your cost-to-fight threshold. Accept it now, issue the refund if not already processed, and log the order for pattern analysis.

The consequences are asymmetric. Submitting a weak response doesn't just lose the dispute — it can contribute to your chargeback rate and, on some networks, affects how issuers weight future disputes from your merchant ID. Accepting a dispute you could have won costs you the transaction. Submitting a response you were always going to lose costs you the transaction plus the operational time, and in some processor configurations, a response fee.

Most merchants fight too many disputes. The ones with the best win rates are selective. If the pre-submission checklist surfaces two or more weak signals, accept and move on.

Step 5: Check policy acceptance and checkout confirmation

This step matters most for SNAD and INR claims, less so for fraud-coded disputes.

In Shopify Admin → Settings → Checkout, confirm your return and refund policy is linked at checkout — not just on a footer page. The issuer's question in a SNAD dispute is often: did the cardholder know what they were buying and what the return terms were? A policy that's technically published but buried three clicks from the product page is harder to defend than one surfaced at checkout.

For digital goods or subscription orders, confirm the order confirmation email includes explicit language about the product type, delivery method, and cancellation terms. Shopify's default order confirmation is generic. If you haven't customized it to include policy language, that's a gap — and it shows up in disputes.

Evidence narrative line you can adapt: "At checkout, the customer was presented with and accepted the store's return policy [link to policy page, archived version]. The order confirmation email sent to [customer email] on [date] included the following terms: [paste relevant excerpt]."

What the checklist surfaces that evidence alone doesn't

Running this sequence before building your response does something the evidence-first approach misses: it tells you whether you have a case worth making, and what kind of case it is.

A merchant who skips the contact history check and goes straight to pulling delivery screenshots will miss the email thread that either wins the dispute outright or reveals they should accept it. A merchant who skips the amount verification will submit a full-order receipt against a partial claim and look like they didn't read the dispute. A merchant who skips the reason code mapping will submit delivery proof for a fraud-coded dispute and wonder why they lost.

The issuer doesn't evaluate effort. They evaluate whether your response answers their specific question, with evidence that directly supports it. The checklist is how you make sure you're answering the right question before you spend time building the answer.

DisputeDesk automates the evidence pull and flags mismatches between reason codes and submitted evidence types — but the decision to fight or accept, and the narrative framing, still requires a human read of the order. Automation improves consistency; it doesn't replace the pre-submission judgment call.