4 Chargeback Response Templates and Evidence Checklists

A chargeback response template is a reusable structure for a merchant's case on a disputed payment. You adapt it to each claim and back it with evidence. It is also called a chargeback rebuttal letter, dispute template or representment letter.

People search for it under many names: chargeback rebuttal letter sample, rebuttal template, chargeback dispute letter template, chargeback form template or representment letter sample. The four templates below cover all of them. Each one is labeled by dispute type, so you can pick the right one.

Fighting fraudulent chargebacks takes time. A reusable structure saves work only when you check each letter against the actual claim.

Costs are rising too. Mastercard cites 2026 Mastercard/Datos research forecasting 359 million chargebacks a year worldwide by 2029, 37% more than in 2025.

It also cites Mastercard/Javelin research putting US merchant cost at USD 128 per chargeback (USD 82 internal plus USD 46 third-party), before lost goods. See the Mastercard analysis of the true cost of a chargeback and Chargeflow's chargeback statistics report.

Many disputes are called friendly fraud: the cardholder disputes a payment the merchant believes was valid. Visa puts friendly fraud at about 20% of fraudulent disputes globally, and up to 30% for high-volume online merchants. It cites the 2025 Global eCommerce Payments & Fraud Report (see Visa's friendly fraud insights).

A dispute does not show the cardholder's intent. So state what your records show, and stop there.

A response succeeds or fails on two things:

1. Following the processor's response steps and case due date
2. Gathering relevant evidence that answers the actual claim

Below are four templates with sample rebuttal letters. For a line-by-line walkthrough, read how to write a chargeback response letter. Adapt each letter to the case and submit before your deadline. For all codes by network, see chargeback reason codes. For strategy, see how to win chargeback disputes.

{{cta}}

The Universal Chargeback Rebuttal Letter Framework

Every rebuttal letter, whatever the reason code, uses the same five parts. Explain what each exhibit proves, and leave out records that do not address the claim. Extra files and unproven identity claims make a response harder to follow (see Stripe's dispute evidence best practices).

1. Transaction identification. Open with the transaction ID, case number, amount, date and the card's last four digits. This lets the reviewer match your letter to the right case.
2. Direct rebuttal of the claim. State the cardholder's claim in plain words, then your position in one sentence. Do not make the reviewer guess what you dispute.
3. Supporting evidence list. Label each exhibit (Exhibit A, B, C) and say what it proves. This is the largest part of the letter, and where evidence for the reason code goes.
4. Policy or terms reference. Quote the exact line from your refund, terms or shipping policy that the cardholder saw at checkout. Add the date it applied.
5. Closing ask. End with a short, calm request to rule in your favor based on the evidence. Add contact details for questions.

The four templates below apply this framework to the reason codes merchants dispute most. Template #4 covers unauthorized claims, where friendly fraud comes up most.

Chargeback Template Emphasis by Reason Code Category

Not every exhibit matters equally in every dispute. Use this table to decide what to lead with before you start writing:

Chargeback Reason Codes by Network (Quick Reference)

Each template below maps to one of these common dispute types. Match your chargeback to the right reason code before you write, and read how to fight each reason code for the evidence each one needs:

Mastercard now routes most not-received and not-as-described claims through 4853 (Cardholder Dispute). Old codes 4855 and 4842 may still show in some dashboards. They map to 4853 and 4834. For full lists, see the American Express chargeback reason codes, Discover chargeback reason codes, Mastercard chargeback reason codes and Visa chargeback reason codes guides.

Validate the Template Before You Submit It

A template only helps when every field matches the case. Each dispute type needs different records. Login checks do not answer a cancel date, and delivery does not prove every product detail (see Stripe's dispute categories and evidence). Run this check before you send any template below.

Copyable template opening (sample structure, not a real case): "We contest the [amount] dispute on payment [ID] because [specific fact that answers the claim]. Exhibit E1 records [fact]. Exhibit E2 links [record] to the disputed order. Any earlier credit is listed below." Replace every bracketed field before you submit.

One owner per case. Name a single person or system as the submitter for each case. If your team responds manually, Chargeflow automation should not also submit that case, and the reverse.

Chargeback Response Template #1: Physical Goods Not Received

Order-not-received chargeback notices use these reason codes:

• AMEX C08: Goods/Services Not Received or Only Partially Received
• Discover RG: Non-Receipt of Goods, Services, or Cash
• Mastercard 4853: Cardholder Dispute, goods or services not provided (legacy code 4855)
• Visa 13.1: Merchandise/Services Not Received

Before you respond, consider contacting the customer to understand the issue. Keep a record of any tracking details you send. That message can support your case. A sample chargeback letter to the customer should state the order, amount and tracking details, and say nothing about intent.

Key documents to include in your response:

• Order details (no personal data)
• Tracking and delivery proof for every package in the order
• Customer messages and any other supporting evidence

How to write a chargeback dispute template letter to the bank:

Subject Line: TRN #XYZ, CHG-BK CODE: XXX X

To whom it may concern,

We have reviewed TRN XYZ and contest chargeback [add chargeback number] for $[add dollar amount], reason code "Order Not Received."

{Exhibit A}: [Customer's name] made the card payment on [add date] with a card ending in [add last four digits].

{Exhibit B}: We delivered [list the disputed items and every shipment] to the stated address on [add delivery date]. The carrier was [add carrier], tracking number XXXXXX.

{Exhibit C}: [Include only if true] We contacted the cardholder on [add date] with the order tracking details. The attached record shows [the response received, or that no response was received].

Please review the attached documents, which answer the claim that the product was not received, and rule in our favor.

If you have any questions or need further details, please reply directly to this email.

Sincerely,
[Add your details]

Pro tip: If your carrier offers GPS confirmation or delivery photos, add them as another exhibit. They can serve as compelling evidence for physical goods. Check which file types your processor accepts. Do not claim the whole order arrived based on one parcel.

Chargeback Response Template #2: Digital Goods Not Received

These reason codes cover this type of chargeback:

• AMEX C08: Goods/Services Not Received or Only Partially Received
• Discover RG: Non-Receipt of Goods, Services, or Cash
• Mastercard 4853: Cardholder Dispute, goods or services not provided (legacy code 4855)
• Visa 13.1: Merchandise/Services Not Received

Digital goods claims are hard because there is no tracking number. Records of access to the purchase-linked account take its place. For more, see our guide to digital goods chargebacks. Before you respond, capture a screenshot or log showing the item was delivered or accessed. Attach it as an exhibit instead of sending it to the issuer separately.

Documents to include in your response:

• Order details (no personal data)
• Email confirmation and redemption code
• Date of redemption, server logs, and timestamps
• Device and IP address data showing access to the digital product
• Customer messages

How to write a chargeback rebuttal letter to the bank using this chargeback dispute template:

Subject Line: TRN #XYZ, CHG-BK CODE: XXX X

To whom it may concern,

We have reviewed TRN XYZ and contest chargeback [add chargeback number] for $[add dollar amount], reason code "Merchandise Not Received."

{Exhibit A}: [Customer's name] made the payment on [add date] with a card ending in [add last four digits].

{Exhibit B}: We sent the order confirmation and redemption code to the email address provided at the time of the transaction on [add date].

{Exhibit C}: The purchase-linked account [add license or account ID] accessed the digital item on [add date] at [add time and time zone]. The attached server logs and IP records show this. These records show access to the account. They do not by themselves show who was using it.

{Exhibit D}: [Include only if true] We contacted the cardholder on [add date] with the redemption details.

Please review the attached documents, which answer the claim that the digital goods were not received, and rule in our favor.

If you have any questions or need further details, please reply directly to this email.

Sincerely,
[Add your details]

Pro tip: Session logs and device or IP records can link access to the purchase-linked account. Ask your platform or host to pull them before the due date. Include only records about the disputed purchase.

Stripe Digital Goods Representment Evidence Template

For Stripe cases on digital goods, use this annotated version of the template above. For a sample evidence packet, see what proof Stripe accepts for digital goods disputes. Fill in every bracketed field before you submit.

We contest the [amount and currency] [claim] on Stripe payment [payment ID] and order [order ID]. The purchase provided [specific digital entitlement]. Exhibit E1 links the payment to the entitlement created at [timestamp and time zone]. Exhibit E2 records access for [purchase-linked account] and [access event].

Exhibit E3 records [the description at purchase, or the cancellation and billing timeline] that answers the claim. An earlier credit of [amount] appears as refund [ID] on [date], leaving [actual disputed balance]. These records show [specific fulfillment or timeline fact]. They do not prove cardholder authorization on their own.

• E1: ties the payment to the entitlement, so the reviewer sees the same purchase on both records.
• E2: shows delivery or access, and only for the account linked to the purchase.
• E3: answers the specific claim, such as what was described at purchase or when a cancellation happened.
• Earlier credit: list any refund separately so the disputed balance is right.

For an unauthorized claim, use login and account records, not the delivery paragraph alone. Include only records that matter, and hide unrelated personal data. Submission through Stripe's case controls is final. Stripe forwards the evidence, and the issuer decides, so check everything before you send (see Stripe's guide to responding to disputes). These rules are specific to Stripe.

Chargeback Response Template #3: Product or Service Not as Described

These reason codes cover this type of chargeback:

• AMEX C31: Goods/Services Not As Described
• Discover RM: Cardholder Disputes Quality of Goods or Services
• Mastercard 4853: Cardholder Dispute, not as described or defective
• Visa 13.3: Not as Described or Defective Merchandise/Services

Product not as described disputes are common. Social commerce adds to them, because photos can differ from the real product. Before you respond, ask the cardholder exactly how the item differs from your listing. Their answer helps you address each point.

Documents to include in your response:

• Shipping details, with tracking and proof of delivery
• Your refund or cancellation policy as shown on your website at the time of purchase
• Customer messages
• Product details, images, description and product URL
• Screenshots of your website's product listing at the time of the transaction (use archive tools if needed)

How to write a chargeback response template letter to the bank for this dispute type:

Subject Line: TRN #XYZ, CHG-BK CODE: XXX X

To whom it may concern,

We have reviewed TRN XYZ and contest chargeback [add chargeback number] for $[add dollar amount], reason code "Not as Described."

{Exhibit A}: We delivered the package to the cardholder's address on [add date] via [add carrier], tracking number XXXXXX.

{Exhibit B}: Per our refund policy, "[add your refund policy text]." The policy was shown at checkout on [add date].

{Exhibit C}: On [add date], we asked the cardholder how the item differs from the order. They described it as "xxxxxxxxx." The email thread (Exhibit D) and the listing show [how each point compares with the listing].

{Exhibit D}: Screenshots of our product page at the time of purchase, showing the description and images shown before checkout.

Please review the attached documents, which answer each point in the claim, and rule in our favor.

If you have any questions or need further details, please reply directly to this email.

Sincerely,
[Add your details]

Pro tip: If you have a product demo or unboxing video, add it as extra evidence where your processor accepts that format. Delivery alone does not prove the product matched every detail in the listing, so answer each point separately.

Chargeback Response Template #4: Unauthorized Transaction

These reason codes cover this type of chargeback:

• AMEX F29: Card Not Present
• Discover UA02: Fraud - Card Not Present Transaction
• Mastercard 4837: No Cardholder Authorization
• Mastercard 4863: Cardholder Does Not Recognize - Potential Fraud
• Visa 10.4: Fraud - Card-Absent Environment

Unauthorized transaction chargebacks are where friendly fraud is alleged most often. The cardholder may say they did not make a purchase your records link to their account.

These cases are hard to win when real fraud happened. So base the response on records tied to the payment, and claim no more than they show. Many merchants use chargeback alerts to stop disputes early.

If the payment was authenticated with 3D Secure version 2 (3DS2), include the result and response code in your letter. Whether liability moves to the issuer depends on the result, the network rules and your processor, so follow its fraud dispute instructions.

AVS and CVV results, email receipts and delivery to the billing address support your case. They do not prove who placed the order. If an AI agent placed the order for the cardholder, add the consent record as an exhibit. See AI agent chargeback liability and the agentic commerce chargebacks evidence playbook.

Documents to include in your response:

• Order details (no personal data)
• Order confirmation email
• Shipping details, with tracking and delivery proof
• 3DS2 authentication response code (if applicable)
• Device fingerprinting and IP address logs at the time of the transaction
• AVS (Address Verification System) and CVV match results
• Prior order history on the same account
• Customer messages

How to write a chargeback rebuttal letter example to the bank with this template:

Subject Line: TRN #XYZ, CHG-BK CODE: XXX X

To whom it may concern,

We have reviewed TRN XYZ and contest chargeback [add chargeback number] for $[add dollar amount], reason code "Unauthorized Transaction."

{Exhibit A}: [Customer's name] is the name on the payment made on [add date] with a card ending in [add last four digits]. [If applicable] The payment was authenticated via 3DS2 with response code [add code]. The processor's fraud dispute instructions decide how that result applies.

{Exhibit B}: At [add time] on [add date], we sent an order confirmation to the email on the order. That email is linked to the account history in Exhibit E.

{Exhibit C}: We delivered the package to the stated address on [add delivery date] via [add carrier], tracking number XXXXXX.

{Exhibit D}: [Include only if true] On [add date] we contacted the cardholder with the order tracking details. The attached record shows [the response received].

{Exhibit E}: Prior orders and account activity linked to this account: [add dates and order IDs].

We ask that you please review the attached documents addressing the cardholder's claim and find this dispute in our favor.

If you have any questions or need further details, please reply directly to this email.

Sincerely,
[Add your details]

Visa Compelling Evidence 3.0 Checklist for Friendly Fraud Claims

For a Visa 10.4 dispute, Visa Compelling Evidence 3.0 (CE 3.0) lets you swap the identity argument in Template #4 for a data match. When every criterion is met, liability shifts back to the issuer.

CE 3.0 took effect on 15 April 2023 and applies only to reason code 10.4. Check each row before you add a CE 3.0 exhibit (source: Visa CE 3.0 merchant readiness guide):

Worked example (sample, not a real case): A cardholder disputes a $180 order on 1 September 2026 under Visa 10.4. Your records show undisputed orders on 2 March 2026 (183 days earlier) and 10 November 2025 (295 days earlier). Each used the same user ID and device ID as the disputed order.

Both fall inside the 120 to 365 day window, and two elements match, one being the device ID. So the case qualifies. Add one exhibit to Template #4:

{Exhibit F}: CE 3.0 data. Prior undisputed transactions [ID 1, date] and [ID 2, date] share user ID [value] and device ID [value] with the disputed transaction.

If only the shipping address and user ID match, the case does not qualify. Neither is an IP address or device ID, so the standard Template #4 evidence applies.

Mastercard First-Party Trust. Mastercard announced its First-Party Trust program in October 2023, with US rollout starting in 2024 (The Paypers).

Merchants share three types of data: device identity (IP address, device ID, fingerprint), proof of delivery (shipping address, email) and other identity factors, such as account login or phone number.

Disputes that meet the data rules get chargeback protection (see Mastercard's First-Party Trust overview). Ask your acquirer if it supports the program first. To compare it with CE 3.0, see Visa CE3.0 vs Mastercard First-Party Trust.

How to Strengthen Any Chargeback Response Template

Regardless of which chargeback template you use, strong rebuttal packages share a few traits:

• Lead with a short cover letter. Open with a one-paragraph case summary before the exhibits, so the reviewer can scan your argument.
• Label and reference every exhibit. Label each piece of evidence (Exhibit A, B, C) and refer to it in the letter.
• Keep it factual, not emotional. Reviewers check evidence against reason codes and network rules. Your chargeback dispute template should read like a brief, not a complaint.
• Track the case due date. The due date in your processor's dispute record controls your response. Network windows differ by network, region and dispute stage, and processors often set shorter dates. See our chargeback time limit guide and respond before the date on the case. A missed deadline can mean an automatic loss.
• Customize for each network. The letter structure stays the same, but reason codes, evidence rules and deadlines vary by network. Check current chargeback rules and your processor's instructions before you submit.
• Pull data from your payment stack. Your payment service provider can usually supply AVS, CVV and 3DS2 data. Ask for it as soon as a dispute arrives. The chargeback evidence sources map shows where each record comes from.

A stronger factual record supports your response, but it does not guarantee the issuer's decision. Issuers weigh evidence against network rules, and outcomes vary by case.

When to Use Automated Chargeback Management Instead

A manual template is a good start, but it does not scale. Each case needs research, edits and its own deadline. Automated chargeback management tools can gather evidence and track deadlines. Pair chargeback protection and template-based responses with a wider ecommerce fraud prevention plan to cover both prevention and recovery. See how merchants use Chargeflow for examples.

{{cta}}

Frequently Asked Questions About Chargeback Response Templates

Can I reuse a chargeback response template?

You can reuse a template as a structure. But the claim, dates, amounts, exhibits and request must match each case.

What should I remove from a chargeback response?

Remove accusations, extra policy text, unproven win-rate claims and anything your records do not show.

What should a chargeback response template include?

A strong template has a subject line with the transaction number and reason code, and a short opening that says you contest the chargeback. It then lists labeled exhibits, such as order records, shipping proof and customer messages. It ends with a request to rule in your favor. Tailor each letter to the reason code and the actual claim.

What is a chargeback rebuttal letter?

A chargeback rebuttal letter, or representment letter, is the written case you send through your processor to fight a chargeback. It is the core document in chargeback representment. It presents your evidence and explains why the payment was valid.

For how chargebacks work end to end, see what is a chargeback. A good rebuttal letter refers to each exhibit and answers the cardholder's stated reason.

Can I use the same chargeback dispute template for all reason codes?

The structure stays the same for every code, but the evidence must fit the claim. A "not as described" letter needs the listing at purchase and your return policy. An "unauthorized transaction" letter needs authentication and account history. Always match your evidence to the network rules and your processor's instructions.

How many chargeback response templates should a merchant have?

At minimum, keep templates for the four common dispute types on this page: physical goods not received, digital goods not received, not as described and unauthorized transactions. If you see other types, such as subscription cancellation or credit not processed, add templates for those too.

What is the deadline for submitting a chargeback response?

The due date in your processor's dispute record controls. Windows vary by network, region and stage, and processors may set shorter dates. Track the date on your own case and submit before it. Missing it can mean an automatic loss, however strong your letter is.

Does using a chargeback response template guarantee a win?

No. A template gives structure, but the issuer decides based on your evidence, the reason code and network rules. Clear, complete records that answer the claim are easier to review than a rushed reply.

What evidence is most persuasive in a chargeback rebuttal letter?

Evidence that answers the cardholder's claim. For delivery disputes, that is carrier confirmation for every shipment, with GPS or photo proof where possible. For digital goods, it is access logs and timestamps for the purchase-linked account.

For unauthorized payments, it is the authentication result and linked account history, without claiming they prove identity. Put evidence in date order and refer to it in your letter.

How do I format a chargeback template letter?

Use a subject line with the transaction and reason code, a professional greeting ("To whom it may concern") and a body with numbered exhibits. Close with a polite, firm request to rule in your favor. Keep the tone calm. You are presenting evidence.

What's the difference between a chargeback rebuttal letter and a chargeback response template?

They are the same document from two angles. A response template is the reusable structure you fill in each time. A rebuttal letter is the finished letter for one transaction. Every letter on this page follows the five-part framework above.

What is friendly fraud in a chargeback?

Friendly fraud is a chargeback filed on a purchase the cardholder made or authorized. Often they forgot it, did not recognize the billing name or wanted a refund without returning the item.

Visa puts it at about 20% of fraudulent disputes globally, and up to 30% for high-volume online merchants. Answer it with records tied to the payment, not claims about the cardholder's intent.

How do you dispute a friendly fraud chargeback?

Match the response to the reason code, usually Visa 10.4, Mastercard 4837 or 4863, Amex F29 or Discover UA02. Attach authentication results, device and IP logs, delivery records and past undisputed orders.

For Visa 10.4, check Compelling Evidence 3.0 first. If two past undisputed payments share two data elements with the disputed one, liability shifts back to the issuer. The payments must be 120 to 365 days old, and one element must be the IP address or device ID.

Is there a sample chargeback rebuttal letter to send to the bank?

Yes. This page has four merchant chargeback dispute letter samples: physical goods not received, digital goods not received, not as described and unauthorized transaction. Each has a subject line with the transaction and reason code, labeled exhibits and a closing request.

Replace every bracketed field with your case facts, then submit through your processor or acquirer. It forwards the letter to the issuing bank.

How do merchants win a chargeback dispute?

Answer the exact reason code with evidence for the claim. Submit before the due date, and leave out anything your records cannot prove. Carrier confirmation answers not-received claims. Listing screenshots and messages answer not-as-described claims. Authentication results plus CE 3.0 data answer Visa card-absent fraud claims. Even a complete response does not guarantee the issuer's decision.

Gather evidence and submit responses with Chargeflow Automation. Get started now.