Chargeback Rebuttal Letter: Templates, Examples & How to Write One That Wins (2026)

A chargeback rebuttal letter is the written argument you submit to the cardholder's issuing bank to prove a disputed transaction was legitimate. Get it right and you win the money back. Get it wrong — vague claims, missing evidence, wrong reason code — and the chargeback stands, along with the fee.

This is the complete 2026 guide: what a rebuttal letter must contain, the exact structure Visa, Mastercard, and issuing banks look for, copy-paste templates for the most common reason codes (13.1, 10.4, 4853, 4855), and real examples for Stripe and PayPal disputes. It's written from inside [RecovraFlow](/), the [AI chargeback recovery platform](/#pricing) that drafts these letters automatically and submits them before the processor deadline.

What is a chargeback rebuttal letter?

A chargeback rebuttal letter (also called a dispute response letter, representment letter, or compelling evidence letter) is a formal document a merchant submits during representment — the stage after a chargeback is filed where the merchant re-presents the transaction to the issuing bank with evidence that the charge was valid.

The letter itself doesn't win the dispute. The evidence does. But the letter is what tells the issuer's dispute analyst — who has 30–90 seconds per case — what the evidence proves and why the cardholder's claim is false. A weak letter buries strong evidence. A strong letter turns average evidence into a win.

Industry win rates for represented disputes hover around 20–30% because most merchants send generic templates. Merchants using structured, reason-code-specific rebuttal letters with compelling evidence win 60–75% of the disputes they fight (Visa CE 3.0 outcomes 2024–2025).

When to send a rebuttal letter — and when not to

Fight the dispute only when you can prove the cardholder's claim is false. Sending a rebuttal you can't back with evidence just wastes the chargeback fee and time.

Fight it when: - The customer received the product (delivery confirmed to billing address) - AVS and CVV both matched on the original authorization - You have prior communication showing the customer acknowledged the purchase - The dispute reason is first-party misuse (friendly fraud) — see our [friendly fraud guide](/blog/friendly-fraud) - The product was delivered as described and the customer used it before disputing

Don't fight it when: - The card was genuinely stolen (true fraud — you'll lose and take a fraud-ratio hit) - You made a merchant error (double charge, wrong item, canceled subscription still billing) - Delivery failed or you can't prove delivery - The dispute is under Visa CE 3.0 and you don't meet the 120-day / two-prior-transactions bar

See [chargeback vs refund](/blog/chargeback-vs-refund) for the full decision tree.

The 7 parts of a winning rebuttal letter

Every strong rebuttal letter — regardless of network or reason code — contains the same seven sections in the same order. Issuers' dispute analysts are trained to scan for them.

### 1. Header block

Transaction ID, chargeback case ID, cardholder name (last 4 of card only — never the full PAN), transaction date, transaction amount, currency, merchant name (as it appears on the statement), and reason code. This lets the analyst match your response to the case in under 5 seconds.

### 2. One-sentence position statement

State plainly whether the transaction is valid and why. Example: *"The transaction was authorized by the cardholder, the product was delivered to the billing address on file, and the cardholder used the product for 47 days before filing this dispute."*

### 3. Transaction facts

The verifiable data points: AVS response, CVV response, IP address, device fingerprint, checkout timestamp, browser user-agent, and the exact billing and shipping addresses used.

### 4. Fulfillment evidence

Shipping carrier, tracking number, ship date, delivery date, and proof of delivery — signature, photo, or geolocation from UPS/FedEx/USPS/DHL. For digital goods: download logs, login timestamps, IP of first access.

### 5. Cardholder acknowledgement

Any prior communication that proves the cardholder knew about and accepted the purchase: order confirmation email opened, account login after delivery, product review left, prior successful refund request, or support ticket referencing the item. Under Visa CE 3.0, two prior undisputed transactions from the same cardholder within 120–365 days is the strongest single piece of compelling evidence you can submit.

### 6. Rebuttal of the specific claim

Address the exact reason code word for word. If the cardholder claims "item not received" (13.1), your paragraph starts with delivery proof. If they claim "product not as described" (13.3), it starts with the product listing, photos, and any prior positive interaction. Never write generic "the transaction is valid" language — issuers reject it on sight.

### 7. Evidence exhibit list

Numbered list of attachments with a one-line description of what each proves. Example: *"Exhibit A — UPS delivery confirmation with signature (proves Section 4). Exhibit B — customer service email dated 2026-05-14 acknowledging receipt (proves Section 5)."*

Chargeback rebuttal letter template (universal)

Copy this template and fill in the bracketed fields. It works for any card network and any processor; adapt Section 6 to the specific reason code.

``` CHARGEBACK REBUTTAL LETTER

To: [Issuing Bank Dispute Team] From: [Merchant Legal Name], [Merchant ID / MID] Date: [Response Date]

Case ID: [Chargeback Case ID] Transaction ID: [Original Transaction ID] Transaction Date: [YYYY-MM-DD] Transaction Amount: [Currency] [Amount] Cardholder: [First Name] [Last Initial], card ending [XXXX] Reason Code: [e.g., Visa 13.1 — Merchandise/Services Not Received]

POSITION [Merchant] respectfully disputes this chargeback. The transaction was authorized by the cardholder on [date], the product was delivered to the billing address on [date], and the cardholder [used / accessed / acknowledged receipt of] the product prior to filing this dispute on [dispute date].

TRANSACTION FACTS - AVS Response: [Full Match / Partial / No Match] - CVV Response: [Match / No Match] - Authorization IP: [IP address] - Device Fingerprint: [ID] - Checkout Timestamp: [ISO 8601] - Billing Address: [Address on file] - Shipping Address: [Address on file]

FULFILLMENT - Carrier: [UPS / FedEx / USPS / DHL] - Tracking Number: [Tracking #] - Ship Date: [YYYY-MM-DD] - Delivery Date: [YYYY-MM-DD, time] - Proof of Delivery: [Signature / Photo / Geolocation] — see Exhibit A

CARDHOLDER ACKNOWLEDGEMENT [One paragraph citing prior undisputed transactions, opened emails, account logins after delivery, or direct communication with support.]

REBUTTAL [Address the specific reason code claim. See templates below.]

EXHIBITS Exhibit A — [Proof of delivery] Exhibit B — [Order confirmation email + open log] Exhibit C — [AVS / CVV authorization log] Exhibit D — [Prior undisputed transaction records (CE 3.0)] Exhibit E — [Product description / photos / T&Cs at time of purchase]

We respectfully request that the disputed amount of [Currency] [Amount] be returned to [Merchant] as the transaction meets the compelling evidence standards of [Visa CE 3.0 / Mastercard First-Party Trust].

Sincerely, [Name], [Title] [Merchant] — [Contact email] ```

Rebuttal templates by reason code

### Visa 13.1 / Mastercard 4855 — Merchandise or services not received

``` REBUTTAL

The cardholder claims the merchandise was not received. Records show the product was shipped via [Carrier] on [ship date] under tracking number [tracking #] and delivered to the cardholder's billing address at [address] on [delivery date] at [time]. Proof of delivery is attached as Exhibit A, including [signature / photo / GPS coordinates matching the billing address within [X] meters].

The cardholder logged into their account on [date] — [X days] after delivery — from IP [IP] geolocated to [city, state] (Exhibit F). No support ticket, return request, or refund request was submitted at any point prior to this chargeback filed [X days] after delivery. ```

### Visa 10.4 / Mastercard 4837 — Fraud, card-not-present

``` REBUTTAL

The cardholder claims the transaction was not authorized. Records show the transaction passed both AVS (full match) and CVV (match) verification at authorization. The billing address on the order matches the address on file with the issuing bank. Two prior transactions from the same cardholder — [transaction ID 1] on [date] for [amount] and [transaction ID 2] on [date] for [amount] — were completed successfully and never disputed, satisfying the two-prior-transaction requirement of Visa Compelling Evidence 3.0 (Exhibit D).

The device fingerprint [ID] used at checkout matches the fingerprint from the cardholder's [X] prior successful purchases. The IP address [IP] at checkout geolocates to [city], within [X] miles of the billing address. ```

### Visa 13.3 / Mastercard 4853 — Not as described / defective

``` REBUTTAL

The cardholder claims the merchandise was not as described. The product listing at time of purchase (Exhibit E, archived [date]) accurately described [key attributes: size, material, features]. The cardholder received the product on [delivery date] and did not contact support until [X days] later. Support records (Exhibit G) show [no contact / a resolved contact / a positive review] before the chargeback was filed.

Under card network rules, "not as described" requires the cardholder to first attempt resolution with the merchant. No such attempt was made. The cardholder has retained the merchandise and did not accept the return label offered on [date]. ```

### Visa 12.6 / Mastercard 4834 — Duplicate processing

``` REBUTTAL

The cardholder claims duplicate processing. Records show the two transactions are separate purchases: order [ID 1] on [date] for [items] delivered to [address] on [date], and order [ID 2] on [date] for [different items] delivered to [address] on [date]. Both orders have distinct order numbers, distinct tracking numbers, and distinct fulfillment records (Exhibits A and B). ```

Stripe vs PayPal: format differences

Stripe collects evidence through structured fields (`evidence.uncategorized_text`, `evidence.customer_communication`, `evidence.shipping_documentation`, etc.) via the [Disputes API and Files API](/blog/stripe-chargeback-evidence). Paste your rebuttal letter into `uncategorized_text` and upload exhibits as separate files. Stripe forwards the packet to the issuer.

PayPal uses a single free-form `message` field on the dispute plus up to 10 file attachments, sent through the Customer Disputes API. Put the full rebuttal letter in the message field; attach exhibits separately.

Both processors have hard deadlines — usually 7–14 days for PayPal, 7–21 days for Stripe. Miss it and you automatically lose. [RecovraFlow](/) tracks deadlines and submits automatically.

Common rebuttal letter mistakes that lose disputes

1. Generic language. "The transaction is valid" without specifics is auto-rejected. Reference the exact reason code and address it directly. 2. Wrong reason code assumption. Reason codes change what counts as evidence. A 13.1 letter that argues authorization is irrelevant — the customer isn't disputing authorization, they're disputing delivery. 3. Emotional tone. "The customer is committing fraud" gets ignored. Stick to facts. 4. Missing timestamps. Every claim needs a date. Issuers reject arguments that can't be pinned to specific times. 5. No exhibit references. If a piece of evidence isn't referenced in the letter, the analyst won't dig for it. 6. Late submission. 30% of disputes are lost purely because merchants missed the deadline. 7. Skipping CE 3.0. Prior-transaction evidence is the single strongest compelling evidence available in 2026. Merchants who don't include it leave wins on the table.

How AI drafts rebuttal letters automatically

Writing a good rebuttal letter takes 45–90 minutes per case. At even 50 disputes a month, that's a full-time job.

RecovraFlow's engine pulls the dispute, order, shipping, AVS/CVV, and communication history from Stripe or PayPal, matches it against the reason code, drafts the letter using the seven-section structure above, attaches the correct exhibits via the [Stripe Files API](/blog/stripe-chargeback-evidence), and submits before the deadline. A human reviewer can approve every letter in one click, or auto-submit with the deadline as the trigger.

See how it works on our [chargeback management software guide](/blog/chargeback-management-software) or start a [14-day free trial](/signup).

FAQ

How long should a chargeback rebuttal letter be? One to two pages. Analysts spend 30–90 seconds per case. Longer letters bury the argument.

Do I need a lawyer to write a rebuttal letter? No. Rebuttal letters are commercial documents, not legal filings. Templates and processor-formatted evidence work fine.

Can I reuse the same rebuttal letter for every dispute? No. Each letter must reference the specific transaction, reason code, and cardholder-specific evidence. Generic letters lose.

What's the deadline to submit a rebuttal letter? Depends on network and processor: Stripe usually 7–21 days, PayPal 7–14 days, Visa 30 days, Mastercard 45 days. Miss it and you lose automatically.

Should I include the customer's full card number? Never. Last 4 digits only, per PCI DSS.

What's compelling evidence 3.0? Visa's 2023 framework that lets merchants win first-party misuse disputes by proving two prior undisputed transactions from the same cardholder within 120–365 days. See our [reason codes guide](/blog/chargeback-reason-codes) for details.

Bottom line

A winning chargeback rebuttal letter is short, structured, reason-code-specific, and backed by exhibits. Merchants who follow the seven-section template above and pair it with strong evidence win 60–75% of the disputes they fight — 2–3x the industry average.

Ready to automate the whole thing? [Start a 14-day free trial](/signup) or [see pricing](/#pricing).