Chargebacks Dispute: How to Read the Case Before You Build the Response

Read the dispute before you touch the evidence

A chargeback lands. The instinct is to open the order, grab tracking, screenshot the confirmation, and submit. That sequence produces a lot of lost cases.

The problem isn't the evidence — it's that the merchant never diagnosed what the dispute is actually claiming. Reason codes are compressed. A Visa 13.1 filed as "merchandise not received" might be a genuine non-delivery, a reshipper intercept, a family fraud situation, or a cardholder who received the item and is lying. Each of those requires a different response. The same tracking confirmation that wins one loses another.

Open Shopify Admin → Orders → Disputes and look at three things before you pull a single file: the reason code, the claim amount relative to the original order, and the dispute date relative to the fulfillment date. Those three data points tell you more about what actually happened than the evidence folder will.

Step 1: Map the reason code to what the cardholder is actually asserting

Reason codes are network shorthand. They don't tell you what the cardholder said to their bank — they tell you which dispute category the issuer accepted. Those are different things.

Visa 13.1 (Merchandise/Services Not Received) and Visa 10.4 (Other Fraud — Card Absent) require completely different evidence stacks. A 13.1 is a fulfillment dispute — you need to prove delivery. A 10.4 is an authorization dispute — you need to prove the cardholder authorized the transaction. Submitting delivery confirmation to a 10.4 is answering the wrong question. Issuers don't award points for effort.

Mastercard splits this differently. MC 4853 covers a broad range of "cardholder disputes" including not-received and not-as-described. MC 4837 is the unauthorized transaction code. The evidence requirements diverge sharply. Confirm the exact code in your Shopify Disputes panel — the label displayed sometimes truncates; the code number is what matters for network rules.

Quick mapping:

• Not received (Visa 13.1 / MC 4853 subtype): Prove delivery to the cardholder's address. Carrier confirmation plus signature if available. Behavioral signals if no signature.
• Unauthorized (Visa 10.4 / MC 4837): Prove the cardholder authorized the transaction. AVS, CVV, device fingerprint, prior purchase history, IP match to billing address.
• Not as described (Visa 13.3 / MC 4853 subtype): Prove the item matched the listing. Product photos, spec sheets, return policy acknowledgment, any pre-shipment communication.
• Credit not processed (Visa 13.6 / MC 4853 subtype): Prove the refund was issued, or prove the refund wasn't owed under your stated policy.

If the reason code doesn't match the cardholder's actual complaint — and sometimes it doesn't, because issuers file under whatever code fits their intake process — note the mismatch in your internal record. It occasionally matters at arbitration.

Step 2: Check the fulfillment timeline against the dispute date

The gap between shipment and dispute tells you something. A dispute filed two days after delivery is a different risk profile than one filed 90 days later.

Early disputes (within a week of delivery) skew toward true fraud or genuine non-receipt. Late disputes (60–90 days post-delivery, near the network filing window) skew toward friendly fraud — the cardholder waited until the last viable moment. That distinction changes how you weight your evidence and how skeptical you should be of the claim.

Pull the fulfillment timestamp from the order detail in Shopify Admin. Compare it to the dispute date shown in the Disputes panel. If the carrier marked delivery on day 3 and the dispute was filed on day 87, that timeline is part of your narrative. Document it explicitly — don't assume the issuer will notice.

Sample evidence narrative line: "Order fulfilled and carrier-confirmed delivered on [date]. Dispute filed [X] days later, [Y] days before the Visa 120-day filing window closed. No prior contact from the cardholder regarding non-receipt."

Step 3: Identify what you can prove and what you can only imply

Most merchants treat all evidence as equivalent. It isn't. There's a hierarchy.

Proof: Carrier delivery confirmation with GPS coordinates or photo. Signed delivery receipt. Access logs showing the account was used post-delivery. Customer service communication where the cardholder references the order.

Strong inference: AVS full match plus CVV match on a transaction that matches the cardholder's billing address. IP geolocation consistent with billing address. Prior successful orders from the same card and address.

Weak inference: Order confirmation email sent. Tracking number issued. No return request filed. These establish process, not outcome.

Issuers — particularly on Visa — are increasingly skeptical of weak inference evidence submitted as if it were proof. A merchant who submits five weak-inference documents alongside one strong-proof document often loses because the volume of weak evidence dilutes the strong piece. Lead with proof. Follow with inference. Cut anything that doesn't add signal.

The $420 apparel dispute that was misread from the start

A merchant received a Visa 13.1 on a $420 apparel order. Carrier showed delivered. AVS was Y. The merchant submitted tracking, order confirmation, AVS result, and a screenshot of the product listing.

They lost.

What the merchant missed: the shipping address was a freight forwarder — a known reshipper address in a ZIP code that had appeared in two prior fraud disputes on the account. The cardholder's billing address was in a different state. AVS matched billing, not shipping. The carrier delivered to the forwarder, not to the cardholder.

The issuer's position: the cardholder never received the merchandise. The merchant proved delivery to a third-party address. That's not the same thing.

The correct response would have required the merchant to either (a) acknowledge the reshipper risk and argue the cardholder authorized the forwarding address — with supporting evidence — or (b) concede the dispute and flag the order pattern internally. Instead, they submitted standard delivery evidence to a non-standard delivery scenario and lost a fightable case on the wrong argument.

The reshipper flag was visible in the Shopify order detail — the shipping address company field contained a suite number format consistent with freight forwarding. It wasn't checked before submission.

Decision point: Fight with full evidence or fight with targeted evidence

Once you've mapped the reason code and assessed your evidence quality, you face a real choice — not a procedural one.

Path A: Submit everything you have. Volume signals effort. Some issuers respond to completeness. Risk: weak evidence dilutes strong evidence. Issuer reads five documents, focuses on the two that raise questions, and rules against you. This path loses more often than merchants expect on high-value disputes.

Path B: Submit only what directly answers the reason code. Tight, targeted, narrative-led. Risk: if your strong evidence has a gap, there's nothing else in the file to compensate. This path wins more often when the core evidence is genuinely strong — and loses faster when it isn't.

The decision rule: if your best evidence directly answers the reason code claim, go targeted. If your best evidence only implies an answer, go broad and lead with the strongest piece. Never submit evidence that contradicts your narrative — a customer service note saying "we'll look into the delivery issue" in a dispute where you're claiming clean delivery is a case-killer.

Step 4: Write the narrative before you attach the files

The narrative is the frame. Evidence without a narrative is a document dump. Issuers process high volumes — a response that requires the reviewer to construct the argument from raw attachments loses to a response that hands them the conclusion and supports it.

Write three sentences before you attach anything:

1. What happened: "The cardholder placed a $420 order on [date], which was fulfilled and carrier-confirmed delivered to the address provided at checkout on [date]."
2. Why the claim is inconsistent with the record: "No contact was received from the cardholder prior to the dispute filing. The dispute was filed [X] days after confirmed delivery."
3. What the evidence shows: "Attached: carrier delivery confirmation with timestamp, AVS match result, and order history showing two prior successful transactions from the same card."

That's the structure. Adjust the facts. Don't expand it into a paragraph — issuers don't reward length.

In Shopify Payments disputes, this narrative goes into the response description field in the Disputes panel. Keep it under 300 words. If you're using a third-party processor, confirm the submission format — some require PDF attachments with narrative embedded; others have structured fields. Format mismatches cause rejections that look like losses.

Step 5: Internal note before you close the workflow

Win or lose, log what happened. Not for compliance — for pattern recognition.

Internal note format: "[Date] — [Reason code] — [Outcome] — [What evidence was submitted] — [What the issuer focused on] — [What we'd do differently]."

Most merchants skip this. Six months later, they're losing the same dispute type for the same reason and have no record of having seen it before. DisputeDesk surfaces these patterns across dispute history — but the note still matters for merchant-side context that automation can't infer from structured data alone.

Flag orders that show reshipper addresses, mismatched IP geolocation, or first-time high-value purchases in the internal note. Those flags feed future pre-authorization decisions, not just dispute responses.

Where the workflow breaks in practice

The most common operational failure isn't missing evidence — it's submitting before the case is diagnosed. A merchant gets a dispute notification, opens the Disputes panel, sees a deadline, and starts pulling files. The reason code gets a two-second glance. The fulfillment timeline doesn't get checked. The narrative gets written after the files are attached, which means it describes the evidence rather than arguing the case.

Deadline pressure drives this. Shopify surfaces the response deadline prominently in the Disputes panel — which is correct, because missing it is fatal. But merchants misread urgency as "submit fast" when it means "submit correctly before the deadline." Those are different instructions.

If the deadline is more than 48 hours out, spend the first hour on diagnosis. Read the reason code. Check the timeline. Assess the evidence quality. Write the narrative. Then attach files. That sequence produces better outcomes than the reverse.

If the deadline is under 24 hours and the case is complex, that's a triage decision: submit what you have with a clean narrative, or concede and recover the time. A rushed submission with contradictory evidence is often worse than a concession — it can affect your dispute ratio without improving your win rate.