Chargeback rebuttal letter: one page, written for a reviewer with a checklist

A chargeback rebuttal letter is the covering document a merchant submits with its representment evidence. It states the transaction, the reason code being answered, and what each attached document proves. It is read quickly by somebody working through a queue, and it should be written for exactly that reader.

Merchants consistently write the wrong document here. What arrives is a page of indignation about the customer, or a long narrative of the order history with the relevant facts buried in the middle. What is needed is a short, factual mapping between the requirement and the evidence.

The chargeback rebuttal letter structure that works

1. Header: merchant name, transaction date, amount, last four digits of the card, authorisation code, case or ARN reference, and the reason code.
2. One sentence stating your position: the transaction was authorised and the goods were delivered, or the service was provided, or the refund was already issued.
3. A numbered list of the evidence, each line naming the document and what it establishes — "Exhibit 3: delivery confirmation signed at the cardholder’s billing address on 12 March".
4. Where the code requires a specific fact, address that fact explicitly rather than leaving it to be inferred.
5. A closing sentence requesting reversal of the chargeback.
6. Nothing else. No argument about the customer’s character, no commercial history, no complaint about the process.

Tone is not neutral in effect

Anger reads as weakness in this format. A letter accusing the cardholder of fraud, without the evidence the fraud code requires, gets the same outcome as a blank page — and it costs the reviewer’s goodwill on the next case from the same merchant. Keep it factual: what was ordered, what was delivered, what was agreed, what is attached. If the evidence is strong the tone does not matter; if it is weak, the tone will not save it.

Redact what the reviewer does not need. Full card numbers, unrelated customer data and internal notes should not travel with the submission — the file is handled by third parties, and sending more personal data than required is a separate problem you do not want alongside a dispute.

Templates, and their limit

A template per reason-code family saves real time, because the structure and most of the wording are constant. What cannot be templated is the mapping of evidence to the specific requirement, and a letter where that section is generic is a letter that loses. Build three or four templates by family, keep the exhibit list as the part that is written fresh each time, and review the templates when your win rate by code shifts.

Where the letters live

Ettex Docs holds the templates with version history so a change made after a run of losses is traceable, Ettex Records keeps the submitted letter with its exhibits against the transaction, and the evidence file it summarises is covered in chargeback representment.

To be clear: this is documents and records, not chargeback software or legal advice. The requirements per code come from the network rules, and a specialist provider is the right purchase above a modest dispute volume.