Evidence pack and reply skeletons by dispute reason code · for Shopify, WooCommerce, Gumroad and Etsy sellers
Do these six things before you open another tab. Each maps to a document you will need later, and two of them expire.
fraudulent cases in your favour. Write it down with both values.product_not_received dispute is lost.The pattern is consistent across Stripe, Shopify Payments, PayPal and most acquiring banks: machine-readable records beat screenshots, and records that answer the reason code beat records that prove you are honest.
| Accepted | Usually rejected |
|---|---|
| Transaction record export showing AVS/CVV result | Screenshot of the order in your admin panel |
| Carrier tracking export with delivery scan and address | Photo of a shipping label |
| Email thread with timestamps and headers | Summary you typed of what the customer said |
| Signed delivery confirmation or signature capture | "We always ship within 24 hours" policy text |
| Refund policy shown at checkout with a timestamped capture | Refund policy PDF with no proof it was displayed |
| Access logs proving the customer used the product | Claims about how your product normally works |
Six families. For each: the evidence set, the one argument to make, and a reply skeleton you can adapt in five minutes.
Your argument: the cardholder authorised the transaction. Nothing else matters.
Subject: Rebuttal — fraudulent, order #{{ORDER_ID}}
The transaction was authorised by the cardholder.
1. AVS result: {{AVS_RESULT}} (address and postcode compared at authorisation)
2. CVV result: {{CVV_RESULT}}
3. Order placed from IP {{IP}}, city {{CITY}}, which matches the billing
location on file with the issuer.
4. Goods delivered to {{ADDRESS}} on {{DATE}}, tracking {{TRACKING}}.
5. This card has {{N}} prior completed orders with no dispute.
The cardholder did not contact us before filing. The order record,
authorisation response and delivery scan are attached as exported
files rather than images.
Your argument: the goods reached the address the customer supplied, and they did not tell you it was missing.
Subject: Rebuttal — product not received, order #{{ORDER_ID}}
The goods were delivered to the address supplied at checkout.
1. Tracking {{TRACKING}} shows a delivery scan on {{DATE}} at {{TIME}},
recorded against {{ADDRESS}} — the same address entered by the
customer on {{ORDER_DATE}}.
2. The delivery confirmation was emailed to {{EMAIL}} on {{DATE}}.
3. No contact from the customer regarding non-delivery exists before
{{DISPUTE_DATE}}. Inbox search attached.
Delivery to the customer-supplied address, with no prior complaint,
satisfies the requirement for this reason code.
Your argument: the product matched the listing, and the customer had a remedy they did not use.
Subject: Rebuttal — product not as described, order #{{ORDER_ID}}
The delivered product matched the description at the time of purchase.
1. The listing on {{ORDER_DATE}} described {{DESCRIPTION_POINT}}.
A timestamped capture is attached.
2. The customer downloaded or accessed the product on {{DATE}}
(log attached), which is after the delivery date.
3. We offered a {{REMEDY}} on {{DATE}} in reply to their message of
{{DATE}}. They did not respond or return the item.
A remedy was offered and not used; the description matched the item.
Your argument: two separate orders exist, or only one charge exists.
Subject: Rebuttal — duplicate charge, order #{{ORDER_ID}}
These are two distinct orders, not a duplicate.
1. Order {{ORDER_A}} placed {{DATE_A}} for {{ITEM_A}} — tracking {{TRACK_A}}
2. Order {{ORDER_B}} placed {{DATE_B}} for {{ITEM_B}} — tracking {{TRACK_B}}
3. Gateway authorisation IDs {{AUTH_A}} and {{AUTH_B}} are separate
transactions, both settled.
Both orders were shipped and delivered. Records attached as exports.
Your argument: the cancellation either did not happen before the billing date, or happened after it.
Subject: Rebuttal — subscription cancelled, order #{{ORDER_ID}}
The charge occurred before any cancellation was recorded.
1. Subscription began {{START_DATE}}. Billing was monthly on the
{{BILLING_DAY}} of each month.
2. The charge in dispute was raised on {{CHARGE_DATE}}.
3. The cancellation event in our system is timestamped {{CANCEL_DATE}},
which is after the charge date.
4. The cancellation policy shown at signup is attached with a
capture dated {{CAPTURE_DATE}}.
No cancellation existed at the time of billing. Event log attached.
Your argument: the refund was processed, or was never owed under your stated policy.
Subject: Rebuttal — credit not processed, order #{{ORDER_ID}}
The credit was processed on {{REFUND_DATE}}.
1. Refund reference {{REFUND_REF}} for {{AMOUNT}}, issued {{REFUND_DATE}}.
2. Gateway settlement record attached.
3. Card network timelines allow 5–10 business days for the credit to
appear on the cardholder statement. The dispute was filed
{{DISPUTE_DATE}}, which is {{DAYS}} days after the refund.
The credit exists; the dispute predates its appearance on the statement.
Most disputes are lost before they are filed, because the evidence no longer exists. Set up exports on a schedule so you are never reconstructing history during a deadline.
| Source | Typical retention | What to export and how often |
|---|---|---|
| Carrier tracking (USPS, UPS, FedEx, DHL) | ~60 days for detailed scans; proof of delivery longer | Monthly CSV of all tracking numbers with delivery scans |
| Shopify order data | Retained while store exists, but exports are manual | Monthly order export including addresses and gateway results |
| Gumroad / Etsy sales | Dashboard history is long, downloadable exports are limited | Quarterly CSV download, stored off-platform |
| Email threads | Depends on your provider; deletions are permanent | Keep support mail in a searchable archive, not a shared inbox that gets cleaned |
| Product page as sold | Changes are silent — no version history | Timestamped capture of each listing, updated whenever you edit it |
| Processor authorisation logs | Usually 120–180 days | Export the full transaction record at the moment of the dispute, not later |
The practical rule: if a document takes more than ten minutes to find, you will not have it when the deadline is running.
01_transaction_record.csv, 02_delivery_scan.pdf, 03_support_thread.eml. Reviewers open files with obvious names.Winning one dispute is a tactic. Keeping your chargeback ratio under control is the actual objective, because processors close accounts on ratio, not on individual cases.