How to write a chargeback rebuttal that banks actually read

Principles

1. Lead with the strongest point. The reader may stop after a paragraph.
2. One claim per sentence. Each one should be checkable.
3. Tie every claim to an exhibit. “Exhibit B shows the reminder sent on March 3.”
4. Follow the reason code. Argue what the code is about, not everything you know.
5. State facts, not feelings. No arguing the customer’s character.
6. End with a plain ask. Resolve in the merchant’s favor.

A weak and a strong version

Weak:

The customer clearly forgot they signed up. We have terms on our website and she never contacted us. This is obviously friendly fraud and we shouldn’t lose money because she changed her mind.

Strong:

The cardholder subscribed on [date] and accepted recurring billing of [amount] monthly (Exhibit A: terms v[x], accepted [timestamp]).

A reminder was emailed to [address] on [date], 5 days before the charge, with a cancel link (Exhibit B).

No cancellation request was received through any channel before [charge date] (Exhibit C).

The renewal was delivered on [date] (Exhibit D).

The strong version makes four checkable claims in the order a bank expects, each with a document behind it.

The order to argue it in

Each dispute type has an order that matches what the bank is asking. For a recurring-billing dispute it is consent, reminder, no cancellation, then delivery or use. For the others, see the guide for the reason code: Visa 13.1, Visa 13.3 and Visa 10.4.

Exhibits

• Letter each exhibit and cite it in the text.
• Use the system’s own export or a screenshot with a timestamp, not a summary in your words.
• Make every file open and legible. A corrupted attachment is a missing one.
• Redact full card numbers.

Check it like a skeptic

Before you submit, read the response as the bank would. Is any claim unsupported by an attached record? Is any required evidence missing? Zevron’s checker does this on every draft and blocks any claim without a known source.

Questions

Related guides