Template

Chargeback Evidence Checklist: Gather Everything Before You Submit

A field-by-field evidence checklist for Shopify merchants — organized by dispute type so nothing gets missed before the response window closes.

Jun 1, 2026
5 min read
English

The gap is almost always in the gathering, not the submitting

Most merchants who lose winnable disputes didn't fail at writing the response — they failed at assembly. They submitted what was easy to find, not what the issuer needed to see. Tracking was there; IP data wasn't. The delivery screenshot was there; the billing/shipping address match wasn't documented. The order existed; the authorization trail didn't.

Shopify Admin surfaces a lot of this automatically under Orders → [Order Number] → Timeline and the Fraud analysis panel — but it doesn't package it for dispute submission. That packaging is manual, and without a checklist, something always drops.

This template is organized by dispute category. Use the full checklist for the category that matches your reason code. Skip the others.


When to Run This Checklist

  • Immediately after a dispute appears in Shopify Payments (Admin → Finances → Disputes)
  • Before drafting any response letter
  • Before deciding whether to fight or accept — evidence gaps often change the call
  • After a loss, to identify what was missing (forensic use)

Response windows are typically 7–21 days depending on the card network and your processor — confirm with your processor. Running this checklist on day one preserves time to chase missing items (carrier confirmations, signed delivery records, customer email threads).


The Checklist Template

Section 1 — Order Baseline (Required for All Dispute Types)

Evidence ItemSourceStatus
Order confirmation (order ID, date, amount, line items)Shopify Admin → Orders → [ORDER ID][COLLECTED / MISSING / N/A]
Billing name and address on fileOrder detail page[COLLECTED / MISSING / N/A]
Shipping address used at checkoutOrder detail page[COLLECTED / MISSING / N/A]
AVS and CVV result codesShopify Payments transaction detail or processor dashboard[COLLECTED / MISSING / N/A]
IP address at time of orderShopify Admin → Fraud analysis panel[COLLECTED / MISSING / N/A]
Device fingerprint / browser info (if available)Fraud analysis panel or third-party app[COLLECTED / MISSING / N/A]
Fraud risk score and flags shown at order timeShopify Admin → Fraud analysis panel[COLLECTED / MISSING / N/A]
Customer account history (prior orders, account age)Admin → Customers → [CUSTOMER EMAIL][COLLECTED / MISSING / N/A]
Email address used at checkoutOrder detail page[COLLECTED / MISSING / N/A]

Section 2 — Fraud Disputes (Reason Codes: Visa 10.4, Mastercard 4853/4863, Amex FR2, etc.)

These are the highest-volume dispute type. The issuer's question is whether the cardholder authorized the transaction. Your evidence needs to answer that directly — not just prove the order shipped.

Evidence ItemSourceStatus
3DS authentication result (if 3DS was used)Processor or payment gateway logs[COLLECTED / MISSING / N/A]
Signed delivery confirmation or proof of in-person pickupCarrier portal or fulfillment records[COLLECTED / MISSING / N/A]
Delivery confirmation screenshot with timestamp and addressCarrier tracking page (UPS, FedEx, USPS, etc.)[COLLECTED / MISSING / N/A]
IP geolocation vs. billing address comparisonFraud analysis panel + IP lookup tool[COLLECTED / MISSING / N/A]
VPN or proxy flag (document presence OR absence)Fraud analysis panel or third-party tool[COLLECTED / MISSING / N/A]
Post-purchase customer communication (shipping notifications opened, login activity)Email platform (Klaviyo, Shopify Email) + Admin → Customer timeline[COLLECTED / MISSING / N/A]
Prior successful orders from same card or emailAdmin → Customers → order history[COLLECTED / MISSING / N/A]

Section 3 — Item Not Received (INR) Disputes

Evidence ItemSourceStatus
Carrier tracking number and full tracking historyShopify Admin → Orders → Fulfillment[COLLECTED / MISSING / N/A]
Delivery confirmation to the address on the orderCarrier portal[COLLECTED / MISSING / N/A]
Signature on delivery (if applicable — high-value orders)Carrier portal[COLLECTED / MISSING / N/A]
Shipping notification emails sent to customer (with timestamps)Email platform or Shopify notification logs[COLLECTED / MISSING / N/A]
Customer service contact log (did they contact you before disputing?)Help desk (Gorgias, Zendesk, email inbox)[COLLECTED / MISSING / N/A]
Proof shipping address matches billing (or documented mismatch)Order detail page[COLLECTED / MISSING / N/A]

Section 4 — Item Not as Described / Quality Disputes

Evidence ItemSourceStatus
Product listing / description at time of purchase (screenshot or archived version)Wayback Machine or internal archive[COLLECTED / MISSING / N/A]
Photos or specs of item shippedInternal product records or warehouse[COLLECTED / MISSING / N/A]
Return policy shown at checkout (screenshot)Storefront or Shopify checkout settings[COLLECTED / MISSING / N/A]
Customer communication about the complaint (and your response)Help desk or email[COLLECTED / MISSING / N/A]
Evidence customer did not attempt return before disputingHelp desk + returns platform[COLLECTED / MISSING / N/A]

Filled Example — Fraud Dispute, $340 Apparel Order

Evidence ItemSourceStatus
Order confirmation (Order #4821, Nov 3, $340.00, 2x jackets)Shopify Admin → Orders → #4821COLLECTED
Billing address: 412 Elm St, Austin TX 78701Order detail pageCOLLECTED
AVS result: Full match (Y). CVV: Match (M)Shopify Payments transaction detailCOLLECTED
IP address: 98.112.44.7 — geolocates to Austin, TX (matches billing)Fraud analysis panel + ipinfo.ioCOLLECTED
No VPN or proxy flag detectedFraud analysis panelCOLLECTED
Delivery confirmed Nov 7, 412 Elm St — FedEx tracking 7748291044FedEx tracking portalCOLLECTED
Shipping notification email opened Nov 4 at 9:14am (customer's device)Klaviyo email open logCOLLECTED
Customer account created 8 months prior — 3 prior orders, no disputesAdmin → Customers → jsmith@email.comCOLLECTED
3DS authentication resultProcessor logsMISSING — 3DS not enabled on this order

The missing 3DS entry is the honest part of this checklist. That gap doesn't kill the case — the IP match, AVS, delivery confirmation, and email open log are strong — but it's documented as absent so the response letter doesn't imply coverage that wasn't there. Issuers notice when merchants overclaim.


One Operational Note on Timing

Carrier signature records and email open logs are the two items most likely to disappear or become inaccessible after 30 days. Pull them the same day the dispute appears. Everything else can usually be reconstructed — those two often can't.

DisputeDesk pulls Shopify order data, fraud signals, and fulfillment records automatically at dispute creation. The items that still require manual collection — carrier portals, help desk threads, email platform logs — are flagged in the checklist view so nothing sits uncollected until day 18 of a 21-day window.

Key Takeaways

Run the checklist at dispute creation, not after drafting the response — missing items take time to chase, and some (carrier signatures, email open logs) expire.
Organize evidence by dispute category. Fraud disputes need authorization signals; INR disputes need delivery proof. Submitting the wrong evidence type doesn't help even if it's accurate.
Document what's missing, not just what's collected. Overclaiming coverage you don't have is one of the fastest ways to lose issuer credibility.
AVS match and delivery confirmation together are strong — but neither alone closes a fraud dispute. IP geolocation, device data, and post-purchase engagement fill the gap.
Shopify Admin's Fraud analysis panel and Order Timeline surface most baseline signals automatically. The items that require manual collection (carrier portals, help desk logs, email platforms) are the ones that get missed.

FAQ

Which evidence items matter most for fraud disputes?
IP geolocation matching the billing address, AVS/CVV results, 3DS authentication (if used), and post-purchase engagement (shipping email opens, account login after order) carry the most weight. Delivery confirmation matters too, but it proves shipment — not authorization. Issuers evaluating fraud reason codes are focused on whether the cardholder placed the order, not just whether it arrived.
What if I'm missing a key piece of evidence?
Document the gap honestly in your response rather than omitting it. If 3DS wasn't used, say so and lean on the signals you do have. Issuers are more skeptical of responses that appear to overclaim than responses that acknowledge a limitation and compensate with other strong evidence.
Does this checklist work for all card networks?
The evidence categories apply broadly across Visa, Mastercard, Amex, and Discover, but specific reason codes and required documentation vary by network. Confirm the exact evidence requirements for your reason code with your processor or acquirer before submitting.
How long do I have to submit a chargeback response?
Response windows vary — typically 7 to 21 days depending on the card network and your processor. Shopify Payments disputes show the deadline in Admin → Finances → Disputes. Confirm the exact window with your processor, and treat day one as the day to start collecting, not the day to start reading.

Disclaimer

This content is for informational purposes only and does not constitute legal advice.

Automate Your Chargeback Responses

DisputeDesk automatically tracks deadlines, collects evidence, and generates winning responses so you never miss a deadline again.