Chargeback Rebuttal Letters: Templates & Complete Guide

What a Rebuttal Letter Does

A chargeback rebuttal letter (also called a representment letter or dispute response letter) is a formal document submitted to the card network — via your acquiring bank — that challenges the chargeback and presents the merchant's case for reversal.

The rebuttal letter does not win the dispute alone. It introduces and connects the evidence. An analyst reviewing your case will spend — at most — two to three minutes on it. They need to understand your position immediately, locate the supporting exhibits without hunting, and see the explicit connection between the evidence and the disputed claim.

A weak rebuttal letter creates confusion, buries evidence, and forces the analyst to make interpretive leaps. A strong rebuttal letter removes all ambiguity — it states clearly why the chargeback should be reversed, labels the exhibits, and connects each one to the specific allegation.

The Core Structure

Every effective rebuttal letter follows the same basic structure regardless of reason code:

1. Header information: Merchant name, merchant account number, dispute/case reference number, transaction date, transaction amount, cardholder name (last four digits), reason code.
2. Opening statement: One or two sentences stating your position and the basis for reversal. Clear, direct, specific. Example: "This chargeback should be reversed. The merchandise was delivered to the cardholder's confirmed shipping address on [date], as evidenced by the carrier tracking record in Exhibit A."
3. Transaction summary: Brief description of what was purchased, when, and at what price. Confirms basic transaction facts before moving to the dispute.
4. Response to the specific allegation: Address the reason code directly. What is the cardholder claiming? What evidence disproves it? For each exhibit, state explicitly: what it is, what it shows, and how it relates to the claim.
5. Exhibit list: Numbered list of all exhibits included with the letter. Label each exhibit consistently — if the letter refers to "Exhibit A — Carrier Tracking Record," the document itself should be labelled with the same name and number.
6. Closing request: Explicit request for reversal. Example: "Based on the evidence presented, we respectfully request that this chargeback be reversed and the transaction amount of $[X] be returned to our account."

Language That Wins

Card network analysts use specific terminology to categorise dispute outcomes. Using this terminology in your rebuttal letter signals that you understand the dispute framework — and maps your response to the categories the analyst is evaluating.

Phrases that carry technical weight:

• "The merchandise was received by the cardholder" — directly addresses goods not received claims
• "The transaction was authorised by the legitimate cardholder" — addresses fraud claims
• "The service was rendered as agreed and as described" — addresses not-as-described and services not received claims
• "The cardholder contacted us on [date] with a question about [X], demonstrating acknowledgement of the transaction" — establishes post-transaction contact as evidence of cardholder involvement
• "Delivery was confirmed by [carrier] on [date] to [address]" — factual delivery confirmation
• "The subscription terms, including the recurring charge amount and cancellation policy, were disclosed at sign-up and are evidenced in Exhibit [X]" — subscription authorisation language

Language to avoid:

• Emotional language ("unfair," "dishonest customer," "fraud" as a label for the cardholder without evidence)
• Irrelevant background ("we have been in business for 10 years" — not relevant to this dispute)
• Vague assertions ("we are confident our products always arrive" — not evidence)
• Threats ("we will pursue legal action" — inappropriate in this context)

Template: Goods Not Received Rebuttal

Use this template for Visa 13.1, Mastercard 4855, or equivalent "merchandise not received" reason codes:

Template: Unauthorised Transaction Rebuttal

Use this for Visa 10.4, Mastercard 4837/4840, or equivalent fraud reason codes. Note: these are harder to win without 3DS authentication.

Template: Cancelled Subscription Rebuttal

Use for Visa 13.2, Mastercard 4841, or equivalent recurring transaction reason codes:

Common Mistakes That Lose Winnable Disputes

Most rebuttal letter failures are avoidable. These are the most common errors:

Wrong evidence for the reason code. A merchant submitting delivery confirmation for an "unauthorised transaction" dispute has provided irrelevant evidence. The reason code determines what evidence is relevant — review the specific code before building the submission.

Unlabelled exhibits. If the letter references "Exhibit A — Carrier Tracking" but the attached document isn't labelled, the analyst must guess which attachment is which. Label every document clearly.

Missing the connection. Including a delivery confirmation without explicitly stating "this confirms delivery on [date] to [address]" in the letter body forces the analyst to interpret the evidence. Make every connection explicit.

Too long. Multi-page narrative responses are rarely more persuasive than concise, structured submissions. Most strong rebuttal letters are 1–2 pages. The exhibits do the evidentiary work; the letter organises and introduces them.

Late submission. A perfect rebuttal letter submitted after the deadline is an automatic loss. Track deadlines per-network (20 days for Amex, 30 days for Visa, 45 days for Mastercard) from the notification date — not from the transaction date.

Accepting chargebacks that should be contested. Many merchants accept chargebacks by default because building a response seems complicated. For disputes with clear delivery records, authorisation data, or subscription documentation, the response is often straightforward and the recovery is worth the effort.