How to Build a Chargeback Evidence Pack That Actually Gets Read

You can lose before the issuer evaluates a single document

Banks review hundreds of chargeback responses daily. A wall of unorganized documents gets skimmed. A focused, well-structured evidence pack gets read. The goal isn't to submit everything you have — it's to submit exactly what addresses the reason code, presented clearly enough that an analyst can follow it in under two minutes.

Start inside Shopify Admin before you pull a single document. Go to Orders > Select Order and confirm the dispute reason code and response deadline first. Then check Shopify Protect status — if the order shows PROTECTED, Shopify may cover the dispute and submission may not be required. If it shows ACTIVE or NONE, you're building the pack yourself. Merchants who skip this step often download every available document and submit a cluttered pack that buries the one piece of evidence that actually matters. Issuers don't dig for it — they move on.

From the same order view, pull the timeline (Order Details > View Timeline), customer information, shipping details, and payment data in sequence. Each field answers a different issuer question. The timeline establishes the sequence of events. Customer communications show merchant diligence. Shipping information addresses delivery. Payment data — specifically AVS and CVV match results — addresses fraud prevention. None of these sections should appear in your pack without a direct line to the dispute reason code. If a document doesn't refute the specific claim, cut it.

What evidence actually changes the outcome — and what doesn't

AVS Y is frequently over-relied on. It confirms the billing address provided matches the cardholder's bank records, which is useful context for a fraud dispute. What it doesn't confirm is that the cardholder authorized the transaction or received the goods. Issuers know this. Submitting AVS Y as your primary evidence in a fraud or non-receipt dispute signals that you don't have stronger proof — and that framing can hurt more than help. Present AVS Y as part of a broader fraud-prevention picture, not as standalone authorization proof. Visa and Mastercard may weigh AVS differently depending on processor routing — confirm the exact weight with your processor.

Tracking marked delivered carries the same structural problem. Carrier confirmation that a package reached the destination address is not proof the cardholder received it. In "item not received" disputes, issuers routinely see delivery confirmation and still find for the cardholder when there's no signature or explicit acknowledgment of receipt. If you have a customer email confirming the order arrived, that email does more work than the tracking number — but only if it's surfaced clearly. Buried in a PDF attachment on page six, it won't get read. Quote it directly in your response narrative.

Customer acknowledgment emails are the most underused evidence in this category. They demonstrate consent, satisfaction, and receipt in a single document. The failure mode isn't that merchants don't have them — it's that they include them without highlighting what they prove. If the email contains a line confirming delivery or expressing satisfaction with the order, pull that line into the body of your response. Don't make the analyst find it.

The $120 apparel dispute that should have been winnable

An apparel merchant received an "item not received" chargeback on a $120 order placed January 5th. The merchant shipped the next day. Tracking showed delivered on January 10th. The customer filed the chargeback on January 15th — five days after the carrier marked it delivered.

The merchant's evidence pack contained the tracking number, the AVS Y result from the original transaction, and the order confirmation email. On paper, that looks like a reasonable response. In practice, it was a weak one. The tracking number proved the carrier delivered to an address — not that the cardholder received the package. The AVS Y proved the billing address matched at authorization — not that the transaction was authorized by the cardholder. The order confirmation email proved the order was placed — not that the customer acknowledged receiving the goods.

What the merchant also had, buried in their email thread, was a customer reply from January 11th — one day after delivery — asking about a return. That email implicitly confirmed receipt. The customer knew the order had arrived because they were already asking about returning it. That single email, surfaced and quoted in the response, would have directly contradicted the "item not received" claim. It wasn't included because the merchant didn't recognize it as evidence.

The better response: lead with the January 11th customer email quoting the return inquiry, pair it with the tracking confirmation showing delivery on January 10th, and present AVS Y as supporting context for transaction legitimacy — not as the centerpiece. The timeline would have shown a five-day gap between delivery and dispute, with a customer-initiated contact in between. That sequence tells a coherent story. The original pack told three disconnected facts.

Decision lesson: A case like this is fightable when post-delivery customer contact exists and gets surfaced. It's weak when the merchant submits carrier data and authorization signals without connecting them to cardholder behavior. The evidence was there — the framing wasn't.

Before you submit: what to verify in Shopify Admin

Confirm the dispute status and response deadline under Orders > [Order] > Dispute. Missing the deadline ends the case regardless of evidence quality. Check Shopify Protect status — PROTECTED orders may not require a manual response. Verify the dispute reason code and map every piece of evidence you plan to include to that specific code; if a document doesn't address the reason, remove it. Pull the order timeline and identify any post-delivery customer contact — emails, chat logs, return requests — that implicitly or explicitly confirms receipt. Check the shipping section for tracking details and note whether a signature was captured. Pull payment information and confirm AVS and CVV match results, but plan to present them as supporting context, not primary proof. Finally, confirm your processor's exact response deadline — Shopify's displayed deadline and your acquirer's internal cutoff can differ, and the shorter one controls. DisputeDesk's pack assembly handles evidence organization and sequencing against the reason code; merchants still own the judgment call on which customer communications to surface and how to frame them. Decide whether to fight or accept before you start building — a $120 dispute with weak delivery proof and no post-delivery contact may cost more to fight than to absorb.