The Ultimate Chargeback Rebuttal Letter Template (by Reason Code)

Your evidence can be airtight and still lose if the bank reviewer can’t see the argument. The rebuttal letter is what turns a folder of attachments into a case the issuer can rule on in seconds — and it’s the piece most merchants either skip or pad with emotion. Here’s how to write one that wins, with a template you can copy today.

What a rebuttal letter is (and isn’t)

A rebuttal letter is the cover letter that accompanies your representment evidence when you fight a chargeback. Its job is narrow and important: state the transaction, name the customer’s claim, and show — point by point — how your evidence disproves it.

It is not the evidence itself. The tracking number, the AVS result, the signed terms — those are your exhibits. The letter’s job is to connect each exhibit to the dispute and tell the bank what it proves. Evidence establishes the facts; the letter makes the argument. You need both, and the letter is what a busy reviewer actually reads.

The anatomy of a winning rebuttal letter

Every strong rebuttal letter has the same seven parts, in this order:

1. Header — your business name, the case/dispute ID, the reason code, and the date.
2. Transaction summary — order number, amount, date, card details on file, in the first line so the reviewer has the anchor immediately.
3. The customer’s claim — state it plainly, in one sentence. Naming it shows you’re answering the actual dispute.
4. Your rebuttal — the core argument, matched to the reason code.
5. Evidence list — each exhibit labeled, with a short note on what it proves.
6. Conclusion — a direct request to reverse the chargeback.
7. Signature — name, title, contact.

Keep it to one page. Reviewers spend very little time per case; a tight, factual letter beats a long, emotional one every time.

The copy-paste template

Fill in every [BRACKETED] placeholder. Delete any exhibit line you’re not including. This is the general-purpose version; swap in the reason-specific variant paragraphs from the next section.

[YOUR BUSINESS NAME]
[Business Address]
[Support Email]  |  [Support Phone]

Date: [DATE]
Re: Chargeback Rebuttal — Dispute/Case ID [CASE ID]
Reason Code: [REASON CODE] — [REASON DESCRIPTION]

To the Dispute Resolution Team at [ISSUING BANK / PROCESSOR],

We are writing to dispute the chargeback filed against the following
transaction, which we believe is valid and should be reversed.

TRANSACTION DETAILS
  Order number:      [ORDER NUMBER]
  Transaction date:  [TRANSACTION DATE]
  Amount:            [AMOUNT] [CURRENCY]
  Cardholder name:   [CUSTOMER NAME]
  Card (last 4):     [LAST 4 DIGITS]
  Descriptor:        [BILLING DESCRIPTOR AS SHOWN ON STATEMENT]

THE CARDHOLDER'S CLAIM
  The cardholder claims: [ONE-SENTENCE SUMMARY OF THE DISPUTE].

OUR RESPONSE
  [REASON-SPECIFIC REBUTTAL PARAGRAPH — see variants below.]

  The customer agreed to our terms and conditions at the time of
  purchase on [DATE], including our [REFUND / CANCELLATION / SHIPPING]
  policy, a copy of which is included as Exhibit [X].

SUPPORTING EVIDENCE
  Exhibit A — [ITEM]: proves [WHAT IT PROVES].
  Exhibit B — [ITEM]: proves [WHAT IT PROVES].
  Exhibit C — [ITEM]: proves [WHAT IT PROVES].
  Exhibit D — [ITEM]: proves [WHAT IT PROVES].

CONCLUSION
  The evidence above demonstrates that this was a valid, authorized
  transaction and that the goods/services were delivered as described.
  We respectfully request that this chargeback be reversed in full and
  the funds returned to our account.

Sincerely,
[YOUR NAME]
[YOUR TITLE], [YOUR BUSINESS NAME]
[CONTACT EMAIL / PHONE]

Reason-specific variant paragraphs

Drop the matching paragraph into the OUR RESPONSE section and cite the matching exhibits. The reason code decides everything — for the full catalog see chargeback reason codes.

Variant A — Fraud / unauthorized (Visa 10.4, Mastercard 4837)

Your goal is to prove the legitimate cardholder made the purchase. Lean on authentication and identity matching. (Reason-specific detail lives in Visa reason code 10.4.)

This transaction was authenticated and authorized by the cardholder.
The billing address passed AVS verification (full match) and the
correct CVV was provided at checkout. The transaction was authenticated
via 3-D Secure [if applicable]. It originated from IP address [IP] and
device [DEVICE ID], which match [NUMBER] prior undisputed purchases by
this cardholder dating to [EARLIEST DATE]. The order was delivered to
the cardholder's verified billing address. Under Visa Compelling
Evidence 3.0, this established transaction history confirms a legitimate,
cardholder-initiated purchase.

Cite: AVS/CVV results, 3-D Secure record, IP/device log, prior-transaction history, delivery confirmation to billing address.

Variant B — Merchandise not received (Visa 13.1)

Your goal is to prove delivery. For physical goods, carrier tracking is decisive; for digital goods, the access trail is.

The purchased goods were delivered to the cardholder. Carrier [CARRIER]
tracking number [TRACKING NUMBER] confirms delivery on [DELIVERY DATE]
to [DELIVERY ADDRESS], which matches the cardholder's address on file.
[For high-value orders: Delivery was confirmed by signature, attached as
Exhibit X.] [For digital goods: The customer accessed/downloaded the
product on [DATE/TIME] from IP address [IP], with login activity logged
on [DATES], confirmed in the access logs attached.]

Cite: carrier tracking with delivery status, signature confirmation, address match; for digital, download/access and login logs with IP.

Variant C — Not as described / defective (Visa 13.3, Mastercard 4853)

Your goal is to prove the customer received what was advertised and agreed to your policies.

The product delivered matches the description the customer reviewed and
agreed to at purchase. Exhibit [X] is the exact product listing as shown
at checkout; Exhibit [Y] shows the item as shipped. The customer accepted
our return and refund policy (Exhibit [Z]) at the time of purchase and did
not contact us to request a return or report a defect before filing this
dispute. [If applicable: Our support records show the following
communication with the customer: [SUMMARY].]

Cite: the product description/listing, photos of the item shipped, accepted return/refund policy, all customer communications.

Variant D — Subscription / recurring cancelled (Visa 13.2)

Your goal is to prove the charge was authorized and the service wasn’t validly cancelled before it.

This recurring charge was authorized under the subscription terms the
customer accepted at signup on [DATE] (Exhibit [X]), which disclose the
billing frequency and cancellation process. We have no record of a
cancellation request before the disputed charge on [DATE]. Our logs show
the customer continued to access the service on [DATES] after the alleged
cancellation, confirmed in Exhibit [Y]. A renewal reminder was sent on
[DATE] prior to the charge.

Cite: signup terms accepted, cancellation policy, usage logs after alleged cancel date, renewal-reminder record.

Dos and don’ts

Do:

• Match the letter and evidence to the reason code — this is the whole game.
• Lead with the transaction details so the reviewer has the anchor immediately.
• Say what each exhibit proves, don’t just list attachments.
• Stay factual and concise — one page.
• Submit before the deadline (often 7–21 days at the processor); a perfect letter filed late is an automatic loss.

Don’t:

• Don’t be emotional or accusatory. “The customer is lying” persuades no one; the evidence does the work.
• Don’t send generic evidence that ignores the reason code.
• Don’t make claims your evidence can’t back — an unsupported assertion undercuts the whole letter.
• Don’t include irrelevant attachments that bury the exhibits that matter.
• Don’t skip the letter and dump raw files; the reviewer won’t build your argument for you.

For how the letter fits into the complete representment process, see how to win a chargeback dispute.

Skip the letter-writing entirely

Writing a tailored rebuttal letter for every dispute — correct reason-code variant, right exhibits cited, before each processor’s deadline — is exactly the repetitive work that gets rushed or missed when volume climbs.

DisputeDash builds the rebuttal letter for you automatically. It reads the reason code the moment your processor reports the dispute, gathers the matching evidence (order data, tracking across 1,200+ carriers, AVS/CVV, IP, device, customer comms), assembles the letter with the right argument for that code, and submits before the deadline. You can review and edit every case or run it fully automatic. Start on the free analytics tier with no card.