How to Write a Chargeback Rebuttal Letter (With Examples)

Your chargeback rebuttal letter is the single most important document in your dispute response. It's the narrative that ties your evidence together, explains why the chargeback is invalid, and guides the reviewer toward a decision in your favor. A well-crafted rebuttal letter can be the difference between recovering revenue and accepting a loss.

Yet most merchants treat the rebuttal letter as an afterthought—a generic paragraph stapled to a stack of documents. The merchants who consistently win disputes treat it as a legal brief: structured, specific, and directly responsive to the reason code.

This guide breaks down the exact structure, tone, and approach that produces winning rebuttal letters, with two complete examples you can adapt.

Why Your Rebuttal Letter Matters

When your dispute response reaches the card issuer, a reviewer will examine your case. This person reviews dozens of disputes daily. They're looking for clear, organized evidence that directly addresses the cardholder's claim. Your rebuttal letter serves three critical functions:

• It frames the narrative: The cardholder's version of events arrived first. Your rebuttal letter tells your side of the story and reframes the dispute on your terms.
• It organizes your evidence: Without context, a stack of receipts, screenshots, and logs is just noise. Your letter tells the reviewer what each piece of evidence proves and why it matters.
• It addresses the specific reason code: Each reason code has specific requirements for what the merchant must prove. Your letter should explicitly address each requirement point by point.

Anatomy of a Winning Rebuttal Letter

Every effective rebuttal letter follows the same four-part structure. This format works because it mirrors how dispute reviewers are trained to evaluate cases.

Part 1: Opening Statement (2-3 sentences)

State who you are, identify the transaction, and declare your position clearly. Include the dispute case number, transaction date, amount, and the reason code being disputed.

What it should sound like: "We are submitting this representment in response to chargeback case [number] filed under reason code [code] for a transaction of [amount] dated [date]. We respectfully dispute this chargeback and provide the following evidence demonstrating that the transaction was valid, authorized, and fulfilled as agreed."

Part 2: Evidence Summary (4-8 sentences)

This is the core of your letter. Walk through your key evidence points in logical order, connecting each one directly to the cardholder's claim. Be specific—include dates, times, tracking numbers, and reference the attached documents by name.

Structure this section around the specific requirements of the reason code. For an "item not received" dispute, lead with delivery confirmation. For an "unauthorized transaction" dispute, lead with authorization evidence (AVS match, CVV match, 3DS authentication).

Part 3: Supporting Documentation Reference (2-4 sentences)

List each attached document and briefly state what it proves. Number your exhibits and reference them by number in your evidence summary. This helps the reviewer quickly locate and verify each claim.

Part 4: Closing Statement (1-2 sentences)

Restate your position and request the chargeback be reversed. Keep it professional and concise.

Tone and Language Tips

The tone of your rebuttal letter matters more than most merchants realize. You're writing for a professional reviewer who will make a judgment call based on the evidence and how credibly it's presented.

Do: Be Professional and Factual

• Use neutral, professional language. Write like you're presenting evidence to a judge, not arguing with the customer.
• State facts, not opinions. "The item was delivered on March 5 and signed for by J. Smith (Exhibit C)" is a fact. "The customer is clearly lying" is an opinion that undermines your credibility.
• Be specific with dates, times, and amounts. Vague language ("the item was delivered around that time") weakens your case. Precision ("delivered March 5, 2026 at 2:47 PM EST, signed by J. Smith") strengthens it.
• Reference evidence explicitly. Every factual claim should point to an attached document. "As shown in Exhibit B, the cardholder's IP address (192.168.x.x) matches previous authenticated sessions."
• Keep it concise. One page is ideal. Two pages maximum. Longer letters suggest you're overcompensating for weak evidence.

Don't: Get Emotional or Accusatory

• Never call the customer a liar, scammer, or thief. Even if you believe it. Use phrases like "the evidence contradicts the cardholder's claim" instead.
• Don't express frustration or anger. "We are tired of dealing with fraudulent chargebacks" makes you look unprofessional, not sympathetic.
• Avoid legal threats. "We will pursue legal action" is irrelevant to the dispute reviewer and comes across as hostile.
• Don't blame the card network or issuer. "Your bank should have verified this" doesn't help your case and alienates the person deciding it.
• Don't include irrelevant information. Your company history, the customer's past behavior with other merchants, or industry statistics don't belong in a rebuttal letter.

Generic vs. Reason-Code-Specific Approach

The difference between a 20% win rate and a 60% win rate often comes down to whether your rebuttal addresses the specific reason code requirements.

Every reason code has a set of "compelling evidence" requirements defined by the card networks. For example, Visa's compelling evidence for reason code 13.1 (Merchandise/Services Not Received) includes proof of delivery to the cardholder's address, with a delivery date, carrier name, and tracking number. If your rebuttal letter doesn't specifically address these requirements, you're leaving win rate on the table.

Example 1: Item Not Received (Visa 13.1)

This example covers a dispute where a customer claims they didn't receive an order that was delivered and signed for.

Why This Example Works

• Opens by identifying the specific case, reason code, and transaction
• Establishes that the transaction was properly authorized (AVS + CVV match)
• Provides specific delivery details: carrier, tracking number, date, time, signature
• The signature name matches the cardholder—a powerful piece of evidence
• Every claim references a numbered exhibit
• Concise: the entire letter fits on one page

Example 2: Unauthorized Transaction (Visa 10.4)

This example covers a "friendly fraud" scenario where the cardholder claims they didn't make the purchase, but the evidence suggests otherwise.

Why This Example Works

• Establishes the cardholder has a history of undisputed transactions—undermining the "I didn't do this" claim
• Shows the same IP address and device were used for previous legitimate purchases
• Highlights 3D Secure authentication, which in many cases should have prevented this chargeback entirely
• Delivery to the same address used in undisputed orders contradicts fraud
• The post-delivery support contact is the strongest evidence—it proves the cardholder received and used the merchandise
• Builds a cumulative case rather than relying on a single piece of evidence

Formatting Best Practices

• One page, two max: Keep your letter concise. If you need more than two pages to make your case, your evidence is probably doing the heavy lifting—let it.
• Use clear headings: If your letter is longer than half a page, use section headers to help the reviewer navigate.
• Number your exhibits: Label every attached document (Exhibit A, Exhibit B, etc.) and reference them by label in your letter.
• Put the case details in the subject line or header: Case number, reason code, transaction date, and amount should be immediately visible.
• Use professional formatting: Standard business letter format. No colored text, no bold everything, no ALL CAPS (except for brief emphasis).
• PDF format: Submit your rebuttal letter and all evidence as clearly labeled PDFs. Avoid Word documents, image files, or compressed archives unless your processor requires them.

Adapting Your Letter for Different Reason Codes

While the structure stays the same, the content of your evidence summary must change based on the dispute type. Here's what to emphasize for the most common categories:

For detailed evidence requirements by reason code, see our complete evidence guide. For specific response deadlines, check the chargeback time limits by network.

Frequently Asked Questions

How long should a chargeback rebuttal letter be?

One page is ideal; two pages is the maximum. The rebuttal letter should frame and summarize your case, not replicate all your evidence. Let your attached exhibits carry the detailed proof. Reviewers spend 2-5 minutes per case—a concise letter that quickly conveys the key facts is far more effective than a lengthy narrative.

Should I use a template or write each letter from scratch?

Use a template for the structure but customize the content for every dispute. Your opening, closing, and format can stay consistent, but the evidence summary must be specific to each case and reason code. A good approach: maintain templates for each major reason code category, then fill in case-specific details for each dispute. Our response templates are designed for exactly this workflow.

What if I don't have strong evidence?

If you genuinely lack the evidence needed to counter the cardholder's claim, accepting the chargeback may be more cost-effective than submitting a weak response. Weak representments waste your time and can sometimes hurt your credibility with the issuer for future disputes. Focus your energy on improving documentation for future transactions. That said, always check what evidence you do have—sometimes merchants overlook valuable documentation like email correspondence or login records.

Can I submit a rebuttal letter after the deadline?

No. Card network deadlines are strict. If you miss the response window (30 days for Visa, 45 days for Mastercard, 20 days for Amex), you forfeit your right to represent the transaction. There is no appeal process for missed deadlines. See our time limits guide for exact deadlines by network and dispute stage.