Ecommerce Chargeback Response Template
Two documents and three sheets that calculate each dispute's response deadline and check it against your own return records before you contest it.
Free download · No account needed
Dispute Register
[Company] — [n] open disputes, computed [date]
Deadline runs from the notification date, not the order date or the ship date. The network does not know when you shipped, only when it told you a cardholder disputed the charge.
| Dispute ID | SKU | Network | Reason Code | Notification Date | Deadline | Days Left | Return Pattern | Action |
|---|---|---|---|---|---|---|---|---|
| — | — | — | — | — | — | — | — | — |
| — | — | — | — | — | — | — | — | — |
| — | — | — | — | — | — | — | — | — |
| — | — | — | — | — | — | — | — | — |
Two response windows, and a third clock neither network prints
| Visa | 30 calendar days from the notification date, every reason code |
| Mastercard | 45 calendar days from the notification date, every reason code |
| Evidence | Starts decaying at the sale. A listing gets edited, a help desk thread ages out, and a dropshipped order with no label had nothing to cite from day one |
Return Pattern is checked before Action is recommended, not after: a SKU whose own returns already describe the disputed complaint gets refunded, since contesting a claim the store's own records confirm loses on the merits and adds a loss to the dispute record either way.
A chargeback template usually answers one clock and ignores the other. The network prints its response window on the notification, thirty calendar days on Visa and forty-five on Mastercard, so a deadline tracker is easy to build. The evidence a response needs runs on a second, unprinted clock. A listing's wording gets edited, a help desk thread ages out of retention, and a dropshipped order with no tracking number had nothing to cite from day one. A lost dispute also comes out of the next settlement deposit whether or not anyone ever computed the deadline.
Talbrook Outdoor Gear is an invented retailer with fourteen open disputes worth $2,129 this quarter. Five, all on the Cascade 2-Person Tent, are "not as described" claims, and the tent's return record already shows thirteen customers citing the identical seam failure. Eighteen affected units against 210 sold is an 8.6 percent complaint rate on one SKU, against a 2.15 percent return rate store-wide, and two of the five had lapsed into recorded losses before anyone cross-checked the pattern. The other nine disputes are unrelated products with no matching return history.
The Dispute Register computes each case's deadline from its network and notification date, and flags anything inside the last third of that window. Before recommending a response, it checks the disputed SKU against the Return Reason Analysis sheet. A matching return pattern means refund rather than contest: arguing a confirmed claim wastes the one allowed response and adds a loss either way. A case with no matching pattern gets checked against the Evidence Checklist, and only earns a contest recommendation when that reason code's evidence is in hand.
What's in the pack
Dispute Register sheet
One row per chargeback notification with the network's deadline computed and the return pattern checked before any status is set.
Evidence Checklist sheet
Every item a reason code actually requires, its typical source, and how fast it decays before the deadline does.
Return Reason Analysis sheet
Return rate by SKU with the dominant complaint and its share, so a batch defect surfaces before more disputes cite it. A confirmed batch is also a reorder point recalculated, not just a refund decision.
Response Templates by Reason Code
Five drafts, one per reason code this pack tracks, with brackets for the order and a rule to refund instead.
Prevention Note
Turns a return pattern into a cause: which batch, which supplier, what to do with the units on the shelf.
Two logging prompts
Turns a notification into a register row with its deadline computed, and checks a SKU's returns before a response gets drafted.
Response deadline alerts
Flags anything inside the last third of its response window, before a case lapses the way two of them did.
How it works
- 1
Open it or download it
Open the pack in River with the agent already primed on reason codes and return patterns, or take the blank documents and sheets away for free with no account.
- 2
Send the notification and your returns
Send the dispute notification with its reason code, plus your returns list for the same SKU and period. The second list changes the recommendation, and matching the SKU across both exports is easiest when your catalogue names it the same way everywhere.
- 3
Read the recommendation
Get a computed deadline, a return pattern match against your own records, and an evidence check against exactly what that reason code requires before anyone drafts a response.
- 4
Respond or refund, logged
Contest with the matching template and its evidence attached, or refund a confirmed batch and roll it into the Prevention Note before it becomes five more disputes.
Frequently asked questions
Is this template free?
Yes. Two documents, three sheets and two logging prompts with no signup and no card, and they are the same files the agent works in. Editing with AI is the optional path, where your own dispute notifications and returns list become the register.
What format are the downloaded files?
CSV for the Dispute Register, Evidence Checklist and Return Reason Analysis sheets, and Word for the Response Templates and Prevention Note, zipped together. Excel, Numbers, Sheets, Word, Pages and Google Docs all open them directly, and nothing needs converting.
Does my deadline always match the network's 30 or 45 day window?
Not always. Visa and Mastercard both set the merchant window at 30 and 45 calendar days on every reason code. Acquirers may impose tighter time limits on merchants so they have time to review and submit your documentation before the network's own deadline. Check the specific date on your notification rather than assuming the network default.
What counts as evidence for a chargeback I want to contest?
It depends on the exact reason code, not its plain-language label. A not-as-described claim wants the listing as it read at the time of sale and the refund policy on file. A merchandise-not-received claim wants a tracking number and a delivery scan, the same records a fulfilment reconciliation already isolates. The Evidence Checklist lists what each code actually requires.
Should I contest every chargeback where I have some evidence?
No. Check the SKU's own return history first. If other customers already returned the same product for the same reason, refunding is faster and avoids a loss on a claim your own records already confirm, which is what the Return Reason Analysis sheet is for.
What does Edit with AI actually do?
It installs the pack as a private Space and asks for your open dispute notifications and your returns list for the same period. From those it builds the register with deadlines computed, checks each SKU's return pattern, and flags which cases are worth contesting.
Find out which of your open disputes your own return records already settle
Download the blank pack as Word and CSV files, or open it in River, send your dispute notifications and returns list, and get the deadline and the refund-or-contest call back first.
Edit with AI