Chargeback Evidence Best Practices: Format for the Analyst, Not the File

The analyst has 90 seconds. Build for that.

When a chargeback response lands at the issuing bank, it goes to a queue. The analyst working that queue is reviewing dozens of cases the same day. Your evidence pack doesn't get a careful read — it gets a scan. If the narrative isn't obvious in the first page and the supporting documents don't map directly to the claim, the analyst moves on.

This is the operational reality most merchants ignore. They pull everything from Shopify Admin under Orders > Disputes, attach it as a single PDF or a stack of screenshots, and write a three-paragraph narrative that buries the key facts. The evidence exists. The case is still lost.

The fix isn't more evidence. It's better architecture.

Start with the narrative — one paragraph, three facts

The narrative is the first thing the analyst reads. It sets the frame for every document that follows. Most merchant narratives fail because they tell a story instead of making a case.

Write one paragraph. It should contain exactly three things: what the cardholder is claiming, what actually happened, and the specific evidence that proves it. Nothing else.

Sample narrative (adapt this):

"The cardholder disputes charge #4821 dated March 14 as unauthorized. The order was placed using the card's billing address, shipped to the same address, and delivered March 17 with carrier confirmation (UPS 1Z9X4R). AVS returned a full match at authorization. The cardholder's email address on file received order confirmation and shipping notification — both opened before the dispute was filed. Evidence is organized below in the order referenced here."

That's it. No background on your business. No explanation of your return policy unless it's directly relevant. No apologies. The analyst now knows exactly what to look for and in what order.

Sequence the documents to match the narrative

After the narrative, every document should appear in the same order the narrative referenced it. If you mentioned AVS first, the AVS result is page 2. If you mentioned delivery confirmation second, that's page 3. The analyst should never have to search for a document you referenced.

This sounds obvious. Almost no one does it. Merchants typically attach documents in the order they pulled them — order confirmation, then tracking, then AVS, then email logs — which is the order of collection, not the order of argument.

Reorder before you submit. The sequence is part of the evidence.

Label every document with what it proves, not what it is

A screenshot labeled "Order Confirmation" tells the analyst what the document is. A screenshot labeled "Order Confirmation — billing address matches cardholder address on dispute" tells the analyst what it proves. These are not the same thing.

Issuers are not required to interpret your evidence. If the connection between a document and your claim isn't explicit, many analysts won't make the inference — especially under time pressure.

Add a one-line header or annotation to every exhibit:

• "Delivery Confirmation — delivered to billing address March 17, 3:42 PM"
• "AVS Result — full match on billing ZIP and street number at authorization"
• "Email Open Log — shipping notification opened March 15, 9:11 AM, before dispute filed March 19"

If you're submitting a PDF, add these as text annotations or a cover label on each page. If you're submitting through Shopify Payments' dispute response interface, include these labels in the text fields adjacent to each upload.

Decision point: one document or annotated bundle?

When submitting through Shopify Payments, you'll typically have the option to upload multiple individual files or combine everything into a single PDF. This is a real decision with real consequences.

Path A — Individual files: Easier to generate quickly. Each document is clearly separated. The risk: the analyst sees a list of attachments with no narrative thread connecting them. Without a cover narrative that references each file by name, the sequence breaks down.

Path B — Annotated single PDF: More work upfront, but the narrative, labels, and documents are physically inseparable. The analyst can't accidentally skip a file. The sequence is locked. For disputes above roughly $300, or any case where the evidence requires interpretation (mixed signals, partial delivery, digital access logs), the annotated bundle is the stronger format. For straightforward low-value disputes with clean delivery confirmation, individual files are acceptable.

If you're unsure which format your acquirer or processor prefers, confirm directly — some processors have file size limits or preferred formats that override this choice.

The $340 apparel dispute that had the right evidence and still lost

A merchant shipped a $340 jacket order with full AVS match, signature-required delivery, and an email open log showing the shipping notification was opened two days before the dispute was filed. The cardholder claimed the charge was unauthorized.

The merchant submitted all of it — but as four separate screenshots with no labels, no narrative, and no ordering logic. The AVS result was the last attachment. The email log was second, but the analyst had no context for what it was proving. The delivery confirmation was first, but the dispute reason was unauthorized transaction, not non-receipt — so the analyst's first question was about authorization, not delivery.

The issuer ruled for the cardholder. The merchant had every piece of evidence needed to win. The case failed on presentation.

When the merchant resubmitted (where the processor allowed a resubmission — confirm this option with your acquirer before counting on it), they led with a narrative that explicitly connected the AVS match to the authorization question, moved the email open log to position two as proof the cardholder had account access before the dispute, and labeled the delivery confirmation as corroborating context. The resubmission reversed the decision.

Same evidence. Different architecture.

What to cut

Most evidence packs are too long because merchants include documents that don't answer the issuer's specific question. The issuer's question is always a variation of one thing: did this transaction happen as the merchant claims, and is the cardholder's claim credible?

Cut anything that doesn't directly answer that question for this specific dispute reason:

• Your return policy — irrelevant to unauthorized transaction disputes; relevant (but often over-explained) to item not as described disputes
• Product photos — rarely move issuers on fraud disputes; occasionally useful on item not as described if the photo directly contradicts the cardholder's claim
• Full order history for the customer — only include if prior purchase history directly undermines the cardholder's claim (e.g., repeat buyer claiming they never shopped with you)
• Screenshots of your website's checkout flow — almost never useful unless the dispute is specifically about whether the cardholder consented to a charge

Every page you add that doesn't answer the issuer's question is a page that dilutes the pages that do.

When evidence signals conflict — say so explicitly

Some disputes have mixed signals: AVS matched but the shipping address was a freight forwarder. Delivery confirmed but the IP at checkout was flagged. Email opened but from a different device than the one that placed the order.

The instinct is to hide these conflicts or hope the analyst doesn't notice. That's the wrong move. Analysts are trained to look for inconsistencies. If they find one you didn't address, it undermines your entire submission.

Address conflicts directly in the narrative. Frame them with context.

Sample conflict acknowledgment (adapt this):

"The shipping address differs from the billing address on this order. The customer's account history shows three prior orders shipped to this same alternate address, all fulfilled without dispute. This pattern is consistent with a known secondary delivery location, not a redirect by an unauthorized party."

This is not an admission of weakness. It's a demonstration that you've reviewed the full picture and the conflict doesn't support the cardholder's claim. Analysts respond better to merchants who show their reasoning than to merchants who submit a clean-looking pack that ignores obvious questions.

Internal note before you submit

Before submitting any response, log a brief internal note in your dispute tracking system (or directly in the Shopify Admin order notes field under the relevant order). This note should capture: the dispute reason code, the evidence submitted and in what order, any conflicts acknowledged, and the submission deadline.

Sample internal note:

"Dispute [ID] — reason: unauthorized. Submitted: narrative + AVS result + email open log + delivery confirmation, in that order. Conflict noted: shipping address differs from billing; addressed in narrative with prior order history. Deadline: April 3. Submitted: March 29."

This note exists for two reasons. First, if the dispute escalates or requires a resubmission, you know exactly what you already argued and what you didn't. Second, if a pattern emerges across multiple disputes — same evidence type failing repeatedly — you can identify it operationally instead of relitigating each case from scratch.

Automation improves consistency, not certainty

DisputeDesk can pull and organize evidence from Shopify Admin automatically — order data, AVS results, fulfillment records, email logs — and sequence them into a structured response. That consistency matters: it removes the formatting errors and sequencing failures that kill otherwise-winnable cases.

But automation doesn't write the narrative for mixed-signal disputes. It doesn't decide whether to acknowledge a freight-forwarder address or how to frame a prior-purchase pattern. High-risk reviews still require a human read before submission. The tool handles the architecture; the merchant owns the argument.