Chargeback Response Letter Template for Service Businesses

When a chargeback notice arrives, most service business owners open a blank document and freeze. What goes first? How formal should it be? What does the reviewer actually need to see? The blank page is the bottleneck, not the evidence itself.

This guide gives you the skeleton of a chargeback response letter, section by section, with placeholder fields you can fill in for any dispute. Below the template, you will find explanations of what makes each section effective and the mistakes that weaken an otherwise strong case.

If you need the full step-by-step response process, start with How to Respond to a Chargeback as a Service Business first, then come back here for the letter structure.

What a Response Letter Actually Is

A chargeback response letter (sometimes called a rebuttal letter or representment letter) is the written narrative you submit to your payment processor alongside your evidence. It is not a legal brief. It is not a customer complaint letter. It is a factual document that tells a dispute reviewer three things:

1. What the customer alleges (the reason code).
2. What actually happened (the chronology of events).
3. What evidence you have attached to support your version (the evidence index).

The reviewer is not your friend or your adversary. They are processing dozens of cases. A clear, organized letter that connects facts to exhibits makes their job easier and your case stronger.

The Template Structure

A strong response letter for a service business has four sections. Each one serves a specific function. Do not skip any of them.

Section 1: Case Summary (One Paragraph)

The summary goes at the top of the letter. It is one paragraph, five to seven sentences, covering the essential facts. Here is the structure with placeholder fields:

On [DATE OF ORIGINAL TRANSACTION], [CUSTOMER NAME] authorized a payment of [AMOUNT] for [SERVICE DESCRIPTION] provided by [YOUR BUSINESS NAME]. The service was performed on [SERVICE DATE] at [LOCATION, if applicable]. The cardholder has filed a dispute under reason code [CODE] alleging [ONE-SENTENCE DESCRIPTION OF ALLEGATION]. This response provides documentation showing that the service was authorized, performed as agreed, and [delivered/completed/accepted] by the customer. Attached are [NUMBER] exhibits supporting this response.

Why this works: The reviewer reads this first paragraph and immediately knows the transaction, the dispute, and your position. Every fact in this paragraph should be verifiable by an attached exhibit. If you write something here that you cannot back up with documentation, remove it.

Common mistake: Writing a multi-page opening that tells the story of your business, your reputation, and how unfair the dispute is. The reviewer does not need your company history. They need facts tied to this specific transaction.

Section 2: Chronology of Events

List every material event in date order, from the first customer interaction to the dispute notice. Use this format:

[DATE] - [EVENT DESCRIPTION] (See Exhibit [LETTER/NUMBER])

Example:
March 3, 2026 - Customer signed service agreement for deck staining, 400 sq ft, total $450 (See Exhibit A)
March 5, 2026 - Booking confirmation email sent; customer replied "confirmed" (See Exhibit B)
March 11, 2026 - Appointment reminder sent via text message (See Exhibit C)
March 12, 2026 - Service performed at customer's residence, completion photos taken (See Exhibit D)
March 12, 2026 - Follow-up email sent with completion summary; no response received (See Exhibit E)
April 2, 2026 - Chargeback notice received, reason code 13.1, "Services Not Received"

Why this works: A chronology converts a messy dispute into a clear timeline. The reviewer can trace the transaction from authorization to dispute without flipping through pages of unstructured narrative. Each entry links to an exhibit, so the reviewer can verify any point instantly.

Common mistake: Including events that are not relevant to the allegation. If the dispute is "service not provided," your chronology should focus on authorization, scheduling, service delivery, and confirmation. Internal meetings, pricing discussions with your team, or your marketing history do not belong here.

Section 3: Evidence Index

The evidence index is a one-page table listing every exhibit, what it is, and the specific fact it establishes. Structure each row like this:

Exhibit [LETTER] | [DOCUMENT DESCRIPTION] | [FACT ESTABLISHED]

Example:
Exhibit A | Signed service agreement dated March 3, 2026 | Customer authorized $450 charge for deck staining
Exhibit B | Email thread, March 5-6, 2026 | Customer confirmed booking and acknowledged cancellation policy
Exhibit C | Text message screenshot, March 11, 2026 | Appointment reminder sent; customer replied "see you tomorrow"
Exhibit D | Time-stamped completion photos, March 12, 2026 | Service was performed at customer's residence
Exhibit E | Follow-up email, March 12, 2026 | Customer was notified of completion and given opportunity to raise concerns

Why this works: The reviewer can understand your entire case from this single page without reading any exhibit. Each row answers: what is this document, and what does it prove? If an exhibit does not prove something relevant to the allegation, it does not belong in the index or the packet. For detailed guidance on choosing and scoring evidence, see What Evidence to Submit for a Chargeback Dispute.

Common mistake: Listing exhibits without stating what fact each one establishes. "Exhibit D: Photos" tells the reviewer nothing. "Exhibit D: Time-stamped completion photos showing finished deck staining at customer's address" tells them exactly what to expect.

Section 4: Exhibits

Attach your evidence in the order listed in the evidence index. Label each exhibit clearly at the top of the page (Exhibit A, Exhibit B, etc.). If the document is an email thread, highlight or annotate the relevant passage without altering the original content.

Formatting guidance:

• Combine all pages into a single PDF if your processor portal requires it.
• Keep screenshots at full resolution. Cropped or blurry images undermine credibility.
• If an exhibit spans multiple pages, number them (Exhibit D, page 1 of 3).
• Remove duplicate documents. Submit only the clearest copy of each piece of evidence.

Adapting the Template to Common Reason Codes

The template structure above works for any dispute, but the emphasis shifts depending on the reason code.

"Unauthorized transaction" (e.g., Visa 10.4, Mastercard 4837): Lead with authorization evidence. Your strongest exhibit is the signed agreement, booking confirmation, or electronic signature that ties the cardholder to the payment. Identity evidence (AVS match, IP address, email match) supports the authorization.

"Service not provided" (e.g., Visa 13.1, Mastercard 4855): Lead with fulfillment evidence. Time-stamped photos, completion forms, GPS data, and post-service communication that proves the work was done. Your chronology should clearly show the gap between "service performed" and "dispute filed."

"Not as described" (e.g., Visa 13.3, Mastercard 4853): Lead with scope and terms documentation. Show what was agreed (the signed proposal or statement of work), then show what was delivered (completion records). The gap between "agreed scope" and "delivered scope" is the reviewer's focus.

"Credit not processed" (e.g., Visa 13.6, Mastercard 4860): Lead with refund evidence or terms documentation. Either show the refund was already issued (with processor confirmation), or show that no refund was owed under the terms the customer acknowledged.

What Not to Include

A response letter weakened by unnecessary material is a common loss. Leave out:

• Emotional language. "This customer is lying" does not help. State what the records show.
• Character assessments. The customer's motives are not your concern. The evidence is.
• Fabricated or reconstructed records. If a document did not exist before the dispute, do not create it now. AI can help you draft a narrative, but it cannot generate evidence. For more on this, see the verification step in our response guide.
• Legal threats. Threatening to sue the customer in a response letter does not improve your case.
• Unrelated transactions. Unless a pattern of disputes from the same customer is directly relevant and provable, stick to the transaction at issue.

Before You Submit: The Verification Pass

Read the completed letter one more time with this checklist:

1. Every date in the summary and chronology matches the source document.
2. Every dollar amount is correct to the cent.
3. Every exhibit label in the letter matches the actual exhibit label on the attached document.
4. Every factual statement is supported by an attached exhibit. If it is not, either attach the exhibit or remove the statement.
5. The letter contains no unsupported conclusions ("the customer clearly knew," "this is obviously fraud").
6. The tone is neutral and professional throughout.

A single factual error (a wrong date, a mismatched amount) can undermine an otherwise strong response. The verification pass takes ten minutes and protects hours of work.

Why a Template Saves More Than Time

The structure above is not a formality. It matches the way dispute reviewers process cases. Summary first, timeline second, evidence map third, exhibits last. When your response follows this flow, the reviewer does not have to reorganize your argument in their head. That reduces the chance of misunderstanding and increases the chance your evidence gets the attention it deserves.

Most service businesses lose disputes not because their evidence is weak, but because their response is disorganized. A clear template fixes the organization problem so you can focus on the evidence itself. To build the strongest possible evidence packet, read our evidence guide. To reduce the number of disputes you face in the first place, see How to Prevent Chargebacks Before They Happen.