Chargeback Response Kit

Evidence pack and reply skeletons by dispute reason code · for Shopify, WooCommerce, Gumroad and Etsy sellers

6 reason codesreply skeletonsretention windowsfirst-hour card
The one thing to understand before anything else. A chargeback is not a customer service problem. It is an evidence contest with a deadline. You do not win by explaining your refund policy, being polite, or being right. You win by handing the processor the specific records that match the specific reason code, inside the window. Everything below exists to make that mechanical.

1 · The first hour

Do these six things before you open another tab. Each maps to a document you will need later, and two of them expire.

  1. Pull the transaction record from your processor, not from your store admin. You need the AVS and CVV result fields, the IP address, and the exact timestamp. Export it as a file, not a screenshot.
  2. Export the tracking record from the carrier. Take the raw export or the API response, not a picture of the tracking page. If the scan shows delivery, note the exact address the scan was recorded against.
  3. Compare shipping address to billing address. If they match, that single fact decides most fraudulent cases in your favour. Write it down with both values.
  4. Check whether the customer contacted you first. Search your support inbox for their email and order number. A message asking for a refund that was never answered is the most common reason a product_not_received dispute is lost.
  5. Note the reason code exactly as written, including the numeric code if your processor gives one. Two codes that sound identical ("not received" vs "not as described") need completely different evidence.
  6. Write the deadline down on paper. Not in your head. The window is usually 7–20 days, and it does not pause for weekends.

2 · What processors actually accept

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.

AcceptedUsually rejected
Transaction record export showing AVS/CVV resultScreenshot of the order in your admin panel
Carrier tracking export with delivery scan and addressPhoto of a shipping label
Email thread with timestamps and headersSummary 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 captureRefund policy PDF with no proof it was displayed
Access logs proving the customer used the productClaims about how your product normally works

3 · Reason code playbook

Six families. For each: the evidence set, the one argument to make, and a reply skeleton you can adapt in five minutes.

3.1 · Fraudulent / card not authorised

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.

3.2 · Product not received

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.

3.3 · Product not as described / unacceptable

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.

3.4 · Duplicate charge

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.

3.5 · Subscription cancelled

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.

3.6 · Credit not processed

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.

4 · Retention windows — the part that quietly loses cases

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.

SourceTypical retentionWhat to export and how often
Carrier tracking (USPS, UPS, FedEx, DHL)~60 days for detailed scans; proof of delivery longerMonthly CSV of all tracking numbers with delivery scans
Shopify order dataRetained while store exists, but exports are manualMonthly order export including addresses and gateway results
Gumroad / Etsy salesDashboard history is long, downloadable exports are limitedQuarterly CSV download, stored off-platform
Email threadsDepends on your provider; deletions are permanentKeep support mail in a searchable archive, not a shared inbox that gets cleaned
Product page as soldChanges are silent — no version historyTimestamped capture of each listing, updated whenever you edit it
Processor authorisation logsUsually 120–180 daysExport 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.

5 · Response timing and format

6 · Ratio protection, not just individual wins

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.

Support. Reply to your purchase receipt with your platform and the reason code, and you get a concrete answer on which evidence set to use. This document is a working reference, not legal advice; processors decide outcomes.