Chargeback Evidence Packs That Get Read: A Merchant Assembly Playbook

Start with the analyst's constraint, not your evidence inventory

Issuer analysts review dozens of disputes per shift. The average time spent on a merchant response before a decision is made is under two minutes — and that's generous. When a response lands as a 22-page PDF with screenshots in random order, no narrative, and three different tracking numbers, the analyst doesn't dig in. They skim, find nothing conclusive fast, and move on.

The evidence pack fails before a single piece of evidence is evaluated. That's the operational problem this playbook addresses.

When a chargeback lands in Shopify Admin under Orders > Disputes, your first job is not to collect everything you have. It's to decide what the issuer needs to see — in what order — to reach a decision in your favor without working for it.

Step 1: Identify the single question the issuer is trying to answer

Every dispute reason code maps to one core question. Not a theme. One question.

• Unauthorized transaction (fraud): Did the cardholder authorize this charge?
• Product not received: Did the merchant deliver what was ordered?
• Not as described: Did the product match what was represented at purchase?
• Credit not processed: Did the merchant issue a refund they agreed to issue?

Pull the reason code from the dispute record in Shopify Admin. Map it to one of these questions. Write that question at the top of an internal note — not in the submission, just for your own assembly process. Every piece of evidence you include should answer that question directly or support a piece of evidence that does. If it doesn't, it doesn't go in.

This is the filter most merchants skip. They include everything because everything feels relevant. It isn't. A delivery photo is relevant to a not-received claim. It's noise in a not-as-described dispute.

Step 2: Build the narrative first — attach files second

The narrative is not a cover letter. It's the decision document. The issuer should be able to read the narrative alone and understand what happened, what you're asserting, and where in the attached evidence they can verify each assertion.

Write it in three blocks:

1. What the cardholder ordered and when. One sentence. Order date, item, amount.
2. What you did and when. Fulfillment date, carrier, tracking number, delivery confirmation date and status. If digital: access date, IP, device.
3. Why the dispute assertion doesn't hold. Direct, factual, no editorializing.

Sample narrative for a not-received dispute:

"Order #4821 was placed on March 3, 2024 for one [item], $187.00. The order was fulfilled March 4 via UPS (tracking: 1Z999AA10123456784). Carrier confirmed delivery to the address on file on March 7 at 2:14 PM with a delivery photo. The cardholder's shipping address matches the billing address on the card. No contact was received from the cardholder prior to the dispute filing on March 19."

That's 74 words. An analyst reads it in 20 seconds and knows exactly what to look for in the attachments. That's the target.

Avoid: "We take customer satisfaction very seriously and always strive to..." — this is invisible to analysts and wastes the first sentence they'll actually read.

Step 3: Sequence the evidence to match the narrative

Attach files in the order they're referenced in the narrative. If the narrative mentions the order confirmation first, that's page one. Tracking confirmation is page two. Delivery photo is page three. AVS match result is page four.

Label every attachment. "Screenshot_2024_03_07" tells the analyst nothing. "UPS_delivery_confirmation_March7" tells them exactly what they're looking at before they open it. Shopify's dispute response interface under Payments > Disputes > [dispute ID] > Add Evidence accepts file uploads with custom names — use them.

If you're submitting a PDF bundle, add a one-line table of contents at the top:

Page 1: Order confirmation | Page 2: Shipping label | Page 3: UPS delivery confirmation | Page 4: Delivery photo | Page 5: AVS match result

This is not bureaucratic overhead. It's the difference between an analyst finding your delivery photo in 10 seconds versus abandoning the search.

Decision point: Single PDF bundle vs. individual file uploads

This is a real operational choice with different consequences depending on your processor and dispute volume.

Single PDF bundle: Easier to control sequence and labeling. Analyst sees one document with a clear flow. Risk: if the file is large or poorly formatted, it may not render cleanly in the issuer's review system. Some acquirers have file size caps — confirm with your processor before assuming a 40-page PDF will transmit cleanly.

Individual file uploads: Each file is labeled and discrete. Easier to swap out one piece without rebuilding the whole pack. Risk: the issuer sees files in whatever order the system displays them, which may not match your narrative sequence. If you go this route, number the file names: "01_order_confirmation," "02_tracking," "03_delivery_photo."

For Shopify Payments disputes specifically, the dispute response interface renders uploaded files in upload order — so sequence matters at upload time, not just at naming time. For third-party gateways routed through Stripe, Braintree, or others, confirm rendering behavior with your gateway; it varies.

Step 4: Cut everything that doesn't answer the core question

A merchant shipped a $340 apparel order, had full AVS match, delivery confirmation, a photo, and the customer's prior purchase history showing three previous orders to the same address. The response was 18 pages. Pages 9 through 18 were: the product listing, size guide, return policy, terms of service, and a screenshot of the customer's account profile showing their birthday.

The issuer ruled for the cardholder. The analyst note cited "insufficient delivery evidence" — which was on page 3, buried under the product listing that came before it.

The delivery evidence was there. The pack was assembled in the order the merchant thought of things, not the order the analyst needed them. The product listing and return policy were irrelevant to a not-received claim. They didn't support the case — they obscured it.

Cut rule: if removing a piece of evidence doesn't weaken your answer to the core question, remove it. Return policies belong in not-as-described disputes. Size guides belong nowhere in a fraud dispute. Prior purchase history belongs in an unauthorized transaction response — not a delivery dispute.

Step 5: Handle contradictory signals explicitly

This is where most playbooks go silent, and it's where real disputes get complicated.

A merchant had a $520 electronics order with full AVS match, delivery confirmation, and a signature on file — but the shipping address was a freight forwarder, and the IP at checkout was flagged as a VPN exit node. The merchant submitted the delivery confirmation and AVS match and said nothing about the forwarder or the IP.

The issuer flagged both in their review. The merchant's silence on those signals read as either ignorance or evasion. The case was lost.

When your evidence pack contains signals that cut against you — a VPN IP, a reshipper address, a billing/shipping mismatch, a delivery to a neighbor — address them directly in the narrative. Don't bury them. Don't omit them. Issuers see the transaction data. If you don't acknowledge a red flag, they assume you didn't notice it, which undermines the credibility of everything else you submitted.

Sample language for a reshipper address situation:

"The shipping address is a freight forwarding service. The cardholder's account shows two prior orders shipped to the same forwarding address, both fulfilled without dispute. The current order followed the same pattern."

That's not an admission. It's context. It reframes the signal from "suspicious" to "consistent with prior behavior." That's a winnable position. Silence is not.

Step 6: Internal note before you close the workflow

Before submitting, log a one-line internal note in the order timeline or your dispute tracking system:

"Dispute #[ID] — [reason code] — submitted [date] — core assertion: delivery confirmed March 7, no prior contact from cardholder — 5 attachments, PDF bundle — response deadline [date]."

This is not for the issuer. It's for you, or whoever handles the escalation if the dispute is lost and you need to evaluate a second chargeback from the same customer, or if the case goes to arbitration. Disputes that go to arbitration with no internal documentation are almost always handled worse than disputes where someone logged what was submitted and why.

DisputeDesk auto-logs submission metadata for disputes processed through the platform — but merchants running manual workflows through Shopify Payments' native dispute interface need to create this record themselves. The order timeline note field works. A shared Notion doc works. A Slack thread does not — it gets lost.

What a complete, readable pack actually looks like

For a not-received dispute on a $200–$500 physical goods order, a well-assembled pack is typically 4–6 pages or files:

1. Narrative (1 page, 3 paragraphs max)
2. Order confirmation with billing/shipping address visible
3. Shipping label or fulfillment confirmation
4. Carrier tracking with delivery status and timestamp
5. Delivery photo (if available from carrier)
6. AVS/CVV match result (pull from Shopify Payments transaction detail or your gateway's transaction log)

That's it. For a fraud dispute where prior purchase history is your strongest signal, add one page showing previous non-disputed transactions from the same card, same address, same device fingerprint — and reference it explicitly in the narrative.

Anything beyond 8 pages for a standard dispute is almost certainly padding. Padding loses cases.

The format failure that kills otherwise-winnable responses

Blurry screenshots. This is not a minor aesthetic issue. An issuer analyst looking at a 400×300 pixel screenshot of a tracking page where the delivery timestamp is illegible cannot use that as evidence. They won't zoom in and enhance it. They'll note "delivery confirmation unclear" and move on.

Pull full-page screenshots at 100% zoom. If the carrier's tracking page is the source, export the PDF version where available — UPS, FedEx, and USPS all offer printable tracking confirmations that render cleanly. If you're screenshotting, use a tool that captures at full resolution. Confirm the timestamp, address, and status are all legible before you attach the file.

The same applies to order confirmation emails. If the email client renders it at 60% width with clipped columns, the billing address may be cut off. The billing address is often the single most important field in an unauthorized transaction dispute. If it's not visible, the evidence doesn't prove what you think it proves.