The Chargeback Response Template for Small Teams

A chargeback is not a refund. It is a dispute filed with the customer's bank, and if you do nothing, the bank rules against you by default — you lose the sale, the goods, and pay a fee on top. A chargeback response template is the difference between losing by silence and winning by paperwork: read the reason code, assemble one evidence pack, send one rebuttal letter before the deadline. Most small teams lose disputes they would have won, for the simple reason that nobody owned the reply.

1. The clock starts the day the dispute lands

• Respond in days, not weeks — processors give a window that is often 7 to 10 days from the dispute notice (it varies by processor and card network; check your dashboard's deadline and write it on the calendar the same hour). Evidence submitted on deadline day is evidence rushed; aim to submit at half-time.
• The fee is real either way — winning the dispute usually does not refund the chargeback fee (commonly $15–$100 depending on processor). That fee is why refund-first beats dispute-fighting (see section 6).
• Your ratio is watching — disputes divided by transactions is tracked by the card networks. Visa's monitoring threshold has historically sat at 0.9% and keeps moving lower. Cross it and you land in a monitoring program with fines and, in the worst case, a terminated merchant account. Log the ratio monthly; it takes two minutes.
• One owner, named — disputes die in shared inboxes. Assign them to one person with a standing order: check the disputes tab every business day. The standing orders template is where that check belongs.

2. Read the reason code before writing a word

Every dispute carries a reason code, and the code tells you which evidence wins. Answer the code, not your feelings.

• Fraud / unauthorized (e.g. Visa 10.4) — the cardholder says it wasn't them. Winning evidence: proof of delivery to the address on file, matching AVS/CVV results, the customer's login IP and device data, prior undisputed orders from the same card.
• Product not received (e.g. Visa 13.1) — winning evidence: tracking with delivery confirmation and signature, dated photos, the shipping address the customer entered at checkout.
• Not as described / quality — winning evidence: the product page the customer saw (screenshot with date), listing copy and photos, any support conversation where expectations were set.
• Subscription / recurring billed after cancel — winning evidence: the terms accepted at signup, the cancellation policy, usage logs after the alleged cancel date, and the self-serve cancel trail (with the save offer on the other side of it). If your cancellation truly requires an email, own it — see section 6.
• Duplicate / amount wrong — usually a processing error on your side. Check first; if it's real, refund and don't fight. Fighting a correct claim burns the ratio for nothing.

3. The evidence pack: five items, one PDF

Processors read fast. Assemble a single PDF, five items or fewer, labeled in the order the reason code cares about:

1. Proof of fulfillment — tracking link, delivery confirmation, signature capture; for digital goods, download logs and access timestamps.
2. Transaction proof — order ID, timestamp, AVS/CVV match results, the IP and device used.
3. Customer history — prior undisputed purchases from the same card or account.
4. The terms they accepted — checkout screenshot or log showing refund policy, cancellation policy, and what the descriptor will look like on their statement.
5. The conversation — relevant emails or tickets, chronological, trimmed to the parts that matter.

Some processors submit device and IP data for you automatically on Visa fraud disputes (compelling-evidence programs); ask yours what they send and build your pack for what's left.

4. The response template (paste in, fill brackets)

Keep it under 250 words. Decision-makers skim; the PDF carries the proof.

Re: Dispute [CASE ID] — order [ORDER ID], [AMOUNT], [DATE]

We believe this dispute should be reversed. The reason code given was [CODE — e.g., "fraud, card-absent"]. The evidence shows otherwise:

1. The order was delivered on [DATE] to the address the cardholder entered at checkout; tracking [NUMBER] shows [DELIVERED / SIGNED BY NAME].
2. AVS and CVV both matched ([RESULTS]), and the order was placed from IP [IP] using the account [ACCOUNT] that has [N] prior successful purchases on this card.
3. The cardholder received the product and used it: [ACCESS LOG / DOWNLOAD / USAGE EVIDENCE, DATED].
4. At checkout the cardholder accepted our [REFUND/CANCELLATION POLICY], disclosed before payment; the statement descriptor reads [DESCRIPTOR].

We have never had prior contact from the cardholder about this order — no support ticket, email, or refund request. We remain happy to resolve this directly; our support address is [SUPPORT EMAIL].

Evidence is attached as a single labeled PDF. Thank you for reviewing.

[NAME, ROLE, BUSINESS]

Adjust the numbered items to the reason code — a "product not received" dispute needs item 1 first, not item 2.

5. The five rules that win

• Answer the reason code — not the injustice you feel. Analysts match evidence to the code.
• Facts, dates, numbers — no adjectives. "Delivered 14:32, signed by J. Alvarez" beats "we definitely shipped it."
• Never pressure the customer — no "withdraw the dispute or else." Contacting a cardholder to argue a dispute can itself look like fraud and always looks like desperation. Offer normal support; let the evidence speak.
• Submit at half-time, not at the wire — rushed packs miss items; late packs count for nothing.
• Log every dispute — date, amount, code, outcome, evidence used. The log is your ratio dashboard and your prevention data (which products, which countries, which month).

6. Prevention beats rebuttal, every time

• A descriptor that says your name — register the statement descriptor with your processor so the charge line reads like you ([BRAND] + [PRODUCT]), not a legal entity nobody recognizes. Unrecognized descriptors cause a large share of "fraud" disputes that are really confusion.
• AVS and CVV on — two checkboxes that kill most stolen-card attempts before they become disputes.
• Receipt emails that orient — order summary, descriptor warning ("this will appear as X on your statement"), support link, delivery promise.
• Refund-first policy — a refund costs the sale; a chargeback costs the sale plus a non-refundable fee plus ratio damage plus the goods. If a customer is angry, refund fast and log it. The payment outage playbook uses the same triage logic when a backlog clears.
• Self-serve cancellation — if canceling a subscription takes an email and three days, you are manufacturing "recurring billed after cancel" disputes. Make cancel a button.
• Signature on big orders — anything over roughly $200 ships with signature confirmation. The fee is cheaper than one lost dispute.

7. When to accept the loss

Not every dispute deserves a fight. Accept it when the amount is smaller than the hours you'd spend, when the claim is plausibly right (fighting correct claims trains the bank to ignore you), or when the outcome is genuinely grey ("friendly fraud" where the household member ordered — real, common, and hard to prove). Accept means: refund mentally, eat the fee, add the card and email to your block list, and move on. A second dispute from the same customer is not a pattern to study; it is a pattern to prevent.

A worked example: the $480 order

A five-person store sells a $480 B2B order. Eleven days later, a Visa 10.4 dispute lands: unauthorized. The owner spends forty minutes: pulls tracking (delivered, signed at the customer's front desk), AVS/CVV (both matched), order IP (same city as the delivery address), and finds two prior orders on the same card, undisputed. He fills the template, numbers the evidence to the code, attaches one PDF, submits on day four of the ten-day window. The bank reverses the dispute in twelve days; the sale is kept; the fee is not returned — and the block-list habit plus the descriptor fix prevent the next one from arriving at all. Total cost: forty minutes and a $20 fee he would have paid anyway.

Related pages

• Overdue Invoice Collection Ladder — the client-payment clock that starts before a dispute ever exists
• Payment Outage Playbook — chargeback triage when a processor backlog clears
• Seasonal Peak Readiness Checklist — surge sales bring surge disputes
• Invoice Fraud / BEC Prevention Checklist — the inbound-payment cousin of the dispute
• Daily Ops Audit Checklist — where the ten-minute disputes-tab check lives
• Admin First-Week Runbook — wire the descriptor, AVS, and receipt email on day one
• Month-End Close Checklist — the monthly pass that names every statement line and gives disputes a daily owner
• Price Increase Announcement Template — surprise price changes are dispute fuel; announced ones are not

A chargeback is a paperwork fight with a deadline, and the paperwork wins. Read the reason code, send one labeled PDF at half-time with the paste-in letter, refund instead of fighting when a refund is the honest answer, and fix the descriptor so the next customer recognizes you on their statement. Small teams win disputes they prepare for — silence is the only move that always loses.