Chargeback Response Playbook: What to Check Before You Submit

You can lose before the issuer evaluates a single document

Most lost disputes are operational losses, not evidence losses. The issuer never gets to weigh your tracking screenshot or your AVS match because the response arrived misaligned with the reason code, missed a deadline, or omitted the one document that directly addressed the cardholder's claim. By the time the evidence package lands at the issuer, the case was already decided — by what the merchant did or didn't do in the 48 hours after the chargeback hit Shopify.

That's the frame for everything below. The question isn't whether you have evidence. It's whether the evidence you have actually addresses the specific reason code on the dispute, whether it's complete, and whether it was assembled before the deadline — not after. Shopify Admin surfaces all of this if you know where to look, but it doesn't tell you when your package is mismatched or when a piece of proof that looks strong is actually insufficient for the network that issued the card.

Chargeback response timelines vary by region and by network; verify your exact deadline with your acquirer. Visa and Mastercard have different evidence requirements for the same dispute category — confirm with your processor which standard applies before you build the package. Shopify Payments surfaces fraud analysis data that third-party gateways may not expose in the same way, so the workflow below assumes Shopify Payments unless noted.

The Shopify Admin walkthrough — in sequence, not at random

Start at Shopify Admin > Orders > Chargeback Details. The reason code is the first thing to lock down. Failure to verify the reason code before pulling evidence is the single most common source of mismatched submissions — merchants build a delivery-proof package for what they assume is an "item not received" dispute, then discover the actual code is "unauthorized transaction," which requires a completely different evidence set. Issuers disregard evidence that doesn't directly address the reason code. Cross-check the code against what you're planning to submit before you pull a single screenshot.

Once the reason code is confirmed, move to Shopify Admin > Orders > Order Details > Fulfillment. Verify the tracking number is present, that it's linked to the correct carrier, and that the delivery status shown in Shopify matches what the carrier's own tracking page shows. Inaccurate shipping data or a missing tracking number quietly kills delivery proof — not because the package wasn't delivered, but because the evidence chain breaks. Pull a screenshot of the carrier tracking page directly, timestamped, showing the delivery event. If the carrier page shows "delivered" but Shopify's fulfillment record shows a different status, resolve that discrepancy before submission. Issuers require clear delivery confirmation to counter "item not received" claims, and a mismatch between your Shopify record and the carrier record creates an opening for the cardholder's bank to dismiss the proof.

Next, go to Shopify Admin > Customers > Customer Profile and pull the full communication history. This step gets skipped more than any other. If you contacted the customer before the chargeback was filed — a shipping update, a response to a delivery inquiry, a refund offer — that communication is evidence of proactive resolution. Issuers may favor the cardholder if the merchant's record shows no engagement with the problem. The absence of communication doesn't just weaken the case; it actively signals to the issuer that the merchant was unresponsive. Export the relevant email thread or message log and include it in the package.

Finally, check Shopify Admin > Settings > Payments > Fraud Analysis. The fraud analysis record shows the signals Shopify captured at the time of the transaction — AVS result, CVV result, IP geolocation, device fingerprint, and any risk flags. For unauthorized-transaction disputes, this record is part of your due-diligence argument. Issuers are more likely to side with merchants who can demonstrate that the transaction passed standard fraud screening at the time of authorization. Pull the fraud analysis summary and include it. If the transaction was flagged and you fulfilled anyway, that's a liability — don't include it without context, and consider whether the case is worth fighting at all.

The $500 fashion dispute that looked fightable and wasn't

A fashion retailer processes a $250 average-order-value transaction on March 1st. AVS returns Y — billing address matches. The item ships March 2nd with a tracking number. The carrier marks it delivered on March 5th. On March 10th, the customer files a chargeback for "item not received." The merchant has AVS Y, a tracking number, and a delivery confirmation. On paper, this looks like a winnable case.

It isn't — at least not as assembled. The delivery confirmation shows the package reached the address. It does not show the cardholder received it. There's no signature. There's no carrier photo of the delivery. The tracking record proves the carrier's last scan, not possession by the intended recipient. Issuers know this distinction and apply it consistently. "Delivered to address" and "received by cardholder" are not the same claim, and the evidence package only proves the first one.

The AVS Y match has the same structural problem. AVS Y indicates the billing address provided at checkout matched the address on file with the bank. It does not prove the cardholder authorized the transaction. In stolen-card scenarios, the fraudster has the billing address. Issuers argue — correctly — that AVS Y alone doesn't establish authorization. Framed in isolation, AVS Y is weak. Framed as one data point in a pattern — matching billing address, matching IP geolocation, device fingerprint consistent with prior orders from the same customer, no prior dispute history — it becomes part of a coherent authorization argument. The merchant in this scenario submitted AVS Y and tracking confirmation and nothing else. The issuer sided with the cardholder.

The communication record made it worse. The customer had emailed on March 7th asking about the delivery. The merchant hadn't responded before the chargeback was filed on March 10th. That three-day gap, with no merchant response visible in the record, read to the issuer as an unresponsive seller. The customer's bank had no reason to doubt the "item not received" claim.

What would have made this case fightable: a carrier delivery photo, a signature confirmation, or — if neither existed — a proactive response to the March 7th email that documented the merchant's attempt to resolve the issue before the dispute was filed. The evidence wasn't missing because the merchant didn't have it. The carrier photo existed; the merchant just didn't pull it. The email thread existed; the merchant just didn't include it. This is the operational loss pattern. The case was lost in the assembly, not at the issuer.

Decision lesson: Tracking marked delivered is necessary but not sufficient for "item not received" disputes. If you don't have a signature or a carrier delivery photo, your response needs the customer communication record to show the merchant engaged before the chargeback was filed. Without one of those two anchors, the case is weak regardless of how clean the AVS and tracking data look.

Evidence that looks strong and the gaps issuers actually exploit

AVS Y and delivery confirmation are the two most commonly over-relied-on evidence types in Shopify merchant dispute responses. Both are real signals. Neither is sufficient on its own, and issuers in both the Visa and Mastercard networks are trained to identify exactly where each one breaks down.

AVS Y proves address match at authorization. It does not prove cardholder possession of the card, cardholder intent to purchase, or cardholder receipt of the goods. In a true fraud scenario, the fraudster has the billing address — that's why the AVS matched. In a friendly fraud scenario, the cardholder provided their own address, which also matches, but they're disputing the charge anyway. AVS Y is most useful as a corroborating signal when paired with IP geolocation match, device fingerprint consistency, and no prior dispute history from the same customer. Frame it as part of a pattern, not as standalone proof of authorization. Visa and Mastercard may weigh AVS differently depending on processor routing; confirm with your processor which network rules apply to the specific dispute.

Delivery confirmation has a parallel problem. The carrier's "delivered" scan proves the package reached the address on the label. It does not prove the cardholder was home, signed for it, or received it from a neighbor or building manager. For high-value orders — roughly $150 and above, though the threshold varies by merchant category — signature confirmation at delivery is the standard that actually holds up. If you're shipping without signature confirmation on orders above your average dispute value, you're accepting that delivery proof will be structurally weak in any "item not received" dispute. Carrier delivery photos, where available, are the next-best option. Screenshot them directly from the carrier portal and include them in the package — don't rely on Shopify's fulfillment record alone.

Customer communication records are under-used and often decisive. A timestamped email exchange showing the merchant responded to a delivery inquiry, offered a replacement, or initiated a refund before the chargeback was filed reframes the dispute from "merchant ignored the problem" to "cardholder bypassed resolution." That reframe matters to issuers. It doesn't guarantee a win, but it removes the easiest path to a cardholder-favorable ruling. DisputeDesk surfaces the communication record during evidence assembly and flags gaps in the timeline — but the merchant has to verify the actual content of those communications and confirm they're included before submission.

Before you submit: the pre-submission sequence

Run this sequence in order. Don't submit until every item is resolved.

1. Verify the dispute status and deadline. Open Shopify Admin > Orders > Chargeback Details. Confirm the response deadline shown. Then confirm that deadline with your acquirer directly — Shopify's displayed deadline may not account for processor-specific cutoffs or regional variations. Missing the deadline forfeits the dispute regardless of evidence quality.

2. Check Shopify Protect status. If the order shows PROTECTED under Shopify Protect, Shopify covers the dispute cost and you don't need to submit a response. If the status is ACTIVE (order eligible but dispute not yet covered) or NONE (not covered), you're responsible for the response. Confirm the status before spending time on evidence assembly.

3. Lock down the reason code. Read the reason code in Chargeback Details. Map it to the evidence type it requires. "Item not received" requires delivery proof and ideally customer communication. "Unauthorized transaction" requires fraud analysis data, AVS/CVV results, and transaction consistency signals. "Item not as described" requires product documentation, your return policy, and any pre-sale communication about the item. Building the wrong package for the right dispute is a common and entirely avoidable loss.

4. Pull fulfillment data from Order Details. Verify the tracking number, carrier, and delivery status. Cross-reference the carrier's own tracking page — don't rely solely on Shopify's fulfillment record. Screenshot the carrier page showing the delivery event with timestamp. If signature confirmation or a delivery photo is available from the carrier portal, pull those too.

5. Pull the customer communication record. Go to Shopify Admin > Customers > Customer Profile. Export or screenshot the full message history relevant to this order. Flag any pre-chargeback contact from the customer and any merchant response. If the customer contacted you and you didn't respond before the dispute was filed, note that gap — it's a liability in the response, and you need to decide whether to address it directly or whether it makes the case not worth fighting.

6. Pull the fraud analysis record. Go to Shopify Admin > Settings > Payments > Fraud Analysis. Document the AVS result, CVV result, and any risk indicators. For unauthorized-transaction disputes, include this in the package. For "item not received" disputes, it's supporting context — include it if the signals are clean, skip it if the transaction was flagged.

7. Match the evidence package to the reason code. Lay out every document you're planning to submit and verify that each one directly addresses the specific reason code. Remove anything that doesn't. Add anything that's missing. A tight, on-point package outperforms a voluminous one that includes irrelevant documents — issuers reviewing high volumes of disputes respond better to focused submissions.

8. Run the fight-or-accept math. Dispute fees, staff time, and win probability all factor into whether submitting a response is worth it. For disputes below your processor's dispute fee threshold — confirm that number with your acquirer — accepting the chargeback may be cheaper than fighting it even if you'd win. For disputes above that threshold with strong evidence, fight. For disputes above that threshold with structurally weak evidence (no signature, no delivery photo, no customer communication), assess honestly before committing to a response.