A chargeback rebuttal letter is the cover letter a merchant submits with its evidence to contest a chargeback. A strong one names the reason code, answers the cardholder’s specific claim, and points the issuer to the exhibit that proves each point. Issuers review a large volume of disputes and decide on what is in front of them, so the letter should be short, factual, and built around the evidence that the reason code calls for.
This guide gives you a reusable structure, a template, the evidence each common Visa and Mastercard reason code needs, and sample letters you can adapt.
What Is a Chargeback Rebuttal Letter?
When a cardholder disputes a charge, the issuing bank pulls the funds back from the merchant and gives the merchant a chance to respond. That response is called chargeback representment, and the rebuttal letter is the narrative part of it. It tells the issuer why the chargeback is invalid and which evidence shows it. The issuer then decides whether to return the funds, which is usually the final stage of the chargeback process.
These two rules shape how to write the letter.
- You usually get one submission. Stripe’s dispute documentation says merchants have only one opportunity to submit a response, it cannot be edited afterward, and a missed deadline is an automatic loss.
- Your deadline is shorter than the network’s. Card networks give acquirers a response window, and processors then set their own, shorter cutoffs for merchants. Stripe says merchants usually have 7 to 21 days depending on the network, so check the deadline on every case.
Every case should be logged with its exact due date the day it arrives, since credit card chargeback time limits differ across Visa, Mastercard, Amex, and Discover.
Why the Letter Matters More Each Year
Chargeback volume is still rising. Mastercard’s true cost of a chargeback analysis, citing its 2025 State of Chargebacks report and Datos Insights, projects global chargeback volume to grow 24% from 2025 to 2028, reaching 324 million a year. Datos Insights data cited in the same analysis puts first- and third-party fraudulent chargebacks at about 45% of merchant chargeback volume globally. A clear, repeatable rebuttal format is how merchants keep up with that volume without lowering the quality of each response.
How to Write a Chargeback Rebuttal Letter in Six Steps
Every chargeback rebuttal letter follows the same order, whatever the reason code. Follow these six steps.
- Read the reason code and the claim. The reason code tells you what the cardholder alleges and what the issuer will accept as proof. Visa’s dispute management guidance warns that material outside the specific dispute condition may not be considered.
- Pull the full order record. Gather the authorization data (AVS and CVV results), device and IP data, shipping and delivery records, customer messages, and the policies the customer accepted at checkout.
- Open with the transaction facts. List your merchant name, the case or dispute number, the acquirer reference number (ARN) if you have it, the transaction date and amount, the last four digits of the card, and the reason code.
- State your position in one or two sentences. Say what happened and why the chargeback is invalid, in a neutral, professional tone.
- Walk through each exhibit. Label every piece of evidence (Exhibit A, Exhibit B) and write one line on what it proves, in chronological order.
- Request the outcome and submit on time. Ask the issuer to reverse the chargeback, then submit in the format your processor accepts.
Format rules vary by processor, so check them before you build the file. Stripe, for example, accepts PDF, JPEG, or PNG files up to 4.5 MB and fewer than 50 pages combined, with a maximum of 19 pages for Mastercard disputes, and it does not accept links, audio, or video. Adyen caps PDFs at 2 MB and rejects files that show full card numbers or identity documents.
Chargeback Rebuttal Template
This chargeback rebuttal template follows the six steps above. Replace each bracketed field with your own case details.
|
Response to chargeback [case number], [network] reason code [code and description] This response covers a [amount and currency] transaction with [legal business name and DBA] (merchant ID [MID]) on [date], made with the card ending in [last four]. Acquirer reference number (ARN) [ARN]. [One or two sentences stating what the customer purchased, what you did, and why the chargeback is invalid.] The following exhibits support this response. Exhibit A ([document]) shows [what it proves]. Exhibit B ([document]) shows [what it proves]. Exhibit C ([document]) shows [what it proves]. Based on the evidence above, we request that the chargeback be reversed and the funds of [Amount] returned to the merchant. [Name, title, contact email] |
Keep the finished letter to one page where possible. The exhibits carry the proof, and the letter’s job is to point the reviewer to them quickly.
Evidence by Chargeback Reason Code
Chargeback reason codes decide what the issuer looks for, so the same order can need different evidence depending on the claim. Visa groups disputes into four categories (10 Fraud, 11 Authorization, 12 Processing Errors, and 13 Consumer Disputes), while Mastercard handles most consumer complaints under one code, 4853 Cardholder Dispute, according to the Mastercard Chargeback Guide (May 13, 2025).
The table below maps the most common codes to the evidence that addresses them, based on Stripe’s reason code documentation.
| Visa code | Closest Mastercard code | Cardholder claim | Evidence that answers it |
|---|---|---|---|
| 10.4 Other Fraud (Card-Absent) | 4837 No Cardholder Authorization | "I did not make this purchase." | AVS and CVV matches, device and IP data, prior undisputed orders, customer messages, account login history |
| 13.1 Merchandise/Services Not Received | 4853 Cardholder Dispute (not provided) | "I never got it." | Carrier tracking and delivery confirmation, signature for high-value orders, digital access logs, delivery policy accepted at checkout |
| 13.3 Not as Described or Defective | 4853 Cardholder Dispute (not as described) | "It wasn't what was advertised." | Product listing as it appeared at purchase, fulfillment records, support conversations, return policy and proof the customer did not use it |
| 13.6 Credit Not Processed | 4853 Cardholder Dispute (refund not processed) | "I was promised a refund." | Refund record with timestamp and confirmation number, or the return policy showing the customer did not qualify |
| 13.2 Cancelled Recurring Transaction | 4853 Cardholder Dispute (recurring); some processors still show legacy code 4841 | "I cancelled this subscription." | Subscription terms accepted at sign-up, logs showing no cancellation or cancellation after the charge, usage after the cancellation date, billing notices |
| 12.6 Duplicate Processing / Paid by Other Means | 4834 Point-of-Interaction Error | "I was charged twice." | Transaction logs showing two separate orders, or proof that no other payment was received |
Send only the evidence that answers the claim on the table’s row. A return policy does nothing for a “not received” dispute, and Visa’s guidance stresses relevance and clarity over volume. The same approach applies to the less common chargeback reason codes for Visa, Mastercard, Amex, and Discover.
Visa Compelling Evidence 3.0 for Fraud Disputes
For Visa 10.4 fraud disputes, Visa Compelling Evidence 3.0 (CE 3.0) gives merchants a structured way to show that the cardholder made the purchase. The rule took effect April 15, 2023, and the Adyen Visa Compelling Evidence 3.0 FAQ summarizes the original requirements. The list below includes Visa’s October 24, 2026 expansion.
- At least two prior transactions on the same card or an associated credential, such as a token, that were not disputed or reported as fraud. Since October 24, 2026, these can come from one or more merchants, not only the merchant facing the dispute.
- Those transactions must have been processed more than 120 and no more than 365 days before the dispute date.
- At least two data elements must match across the transactions, from user ID or account login, IP address, delivery address, and device ID or fingerprint.
- At least one of the matching elements must be the IP address or the device ID.
Meeting these conditions does not guarantee a win. Visa and Adyen both describe compelling evidence as support for the merchant’s case, with the issuer still making the decision. Visa’s April 2026 Core Rules also introduced an update, in effect since October 24, 2026, that lets transactions from multiple merchants qualify as evidence under the CE 3.0 framework. Processor support for the expanded route varies, so ask yours how it applies the change.
Chargeback Rebuttal Letter Examples by Reason Code
The chargeback rebuttal letter examples below show how the template changes with the claim. Each chargeback rebuttal letter sample uses placeholder details. Replace them with your own case data and attach the exhibits to the letter names.
Visa 10.4 Other Fraud in a Card-Absent Environment (With CE 3.0 Data)
This letter is for a fraud claim on an online order where the merchant has two earlier undisputed orders with matching device and address data.
|
Response to chargeback #48213, Visa reason code 10.4 (Other Fraud, Card-Absent Environment) This response covers a $286.40 transaction with Northline Outdoor Co. on August 4, 2026, made with the card ending in 1142. The evidence shows the cardholder authorized this purchase. The order was placed from the same customer account, device, and IP address used for two earlier undisputed purchases on this card, and it shipped to the cardholder's verified billing address. Exhibit A is the order record showing an AVS full match and a CVV match. Exhibit B contains Visa Compelling Evidence 3.0 data for prior orders #39102 (February 11, 2026) and #40877 (March 30, 2026), showing the same device ID and IP address as the disputed order. Neither order was disputed. Exhibit C is the carrier tracking record showing delivery to the billing address on August 7, 2026. We request that this chargeback be reversed and $286.40 returned to the merchant. |
This letter works because it leads with the CE 3.0 match, the strongest evidence for a 10.4 claim, and keeps every exhibit tied to the question of who placed the order.
Visa 13.1 Merchandise/Services Not Received
Use this format when the customer says the order never arrived and you have carrier proof of delivery.
|
Response to chargeback #51907, Visa reason code 13.1 (Merchandise/Services Not Received) This response covers a $142.00 transaction with Brightwell Home on July 18, 2026, made with the card ending in 7730. The merchandise was delivered to the shipping address the cardholder entered at checkout on July 22, 2026, and the cardholder did not contact us about a missing package before filing the dispute. Exhibit A is the order confirmation showing the shipping address entered by the cardholder. Exhibit B is the carrier tracking record showing delivery to that address on July 22, 2026, with delivery photo. Exhibit C is the customer service log showing no contact from the cardholder between the order date and the dispute date. We request that this chargeback be reversed and $142.00 returned to the merchant. |
The same structure covers a Mastercard 4853 “goods not provided” dispute. For digital goods, swap the tracking record for download or login logs that show the customer accessed the product.
Visa 13.3 Not as Described or Defective
This letter answers a claim that the product did not match its listing, where the customer never used the return process.
|
Response to chargeback #50214, Visa reason code 13.3 (Not as Described or Defective Merchandise/Services) This response covers a $96.00 transaction with Arlo & Pine Apparel on June 2, 2026, made with the card ending in 3308. The jacket delivered matches the product listing the cardholder saw at purchase, including size, color, and material. The cardholder did not request a return under our 30-day return policy, which was shown and accepted at checkout. Exhibit A is the product listing as it appeared on June 2, 2026, with the size, color, and material highlighted. Exhibit B is the fulfillment record showing the SKU shipped matches the SKU ordered. Exhibit C is the checkout page showing the return policy and the cardholder's acceptance. We request that this chargeback be reversed and $96.00 returned to the merchant. |
Mastercard handles the same claim under 4853. If the customer did contact support, include the conversation and show that you offered a return or exchange.
Visa 13.6 Credit Not Processed
Use this format when you already issued the refund the cardholder says is missing.
|
Response to chargeback #52660, Visa reason code 13.6 (Credit Not Processed) This response covers a $219.99 transaction with Coastline Audio on May 9, 2026, made with the card ending in 5521. A full refund of $219.99 was issued to the same card on June 1, 2026, before the dispute was filed. Reversing this chargeback prevents the cardholder from being credited twice. Exhibit A is the refund record with timestamp, amount, and processor confirmation number. Exhibit B is the return receipt showing the item was received on May 30, 2026. We request that this chargeback be reversed and $219.99 returned to the merchant. |
A 13.6 rebuttal is usually straightforward when the refund is on record and can be matched to the disputed transaction, which is why matching refunds to open disputes should be a weekly task.
Visa 13.2 Cancelled Recurring Transaction
This letter covers a subscription charge the cardholder says came after cancellation.
|
Response to chargeback #53018, Visa reason code 13.2 (Cancelled Recurring Transaction) This response covers a $34.00 transaction with Steepwell Tea Club on September 1, 2026, made with the card ending in 6604. The cardholder did not cancel the subscription before the September 1 billing date. Our records show no cancellation request, and the cardholder logged in and changed the September box selection on August 27, 2026. Exhibit A contains the subscription terms accepted at sign-up, including the cancellation method and billing date. Exhibit B is the account activity log showing no cancellation and the box change on August 27, 2026. Exhibit C is the pre-billing reminder email sent August 25, 2026. We request that this chargeback be reversed and $34.00 returned to the merchant. |
Account activity after the claimed cancellation date is the strongest evidence for this code, so keep login and change logs for every subscriber.
Mastercard 4837 No Cardholder Authorization
This rebuttal chargeback letter for reason code 4837 answers a Mastercard fraud claim on a card-not-present order.
|
Response to chargeback #54772, Mastercard reason code 4837 (No Cardholder Authorization) This response covers a $412.75 transaction with Fieldstone Supply on August 19, 2026, made with the card ending in 9017. The evidence shows the cardholder authorized this transaction. The order was placed from the cardholder's existing account, which has a purchase history on this card, and was authenticated with 3-D Secure at checkout. Exhibit A is the authorization record showing the 3-D Secure authentication result. Exhibit B is the account history showing three prior orders on this card with the same shipping address. Exhibit C is the delivery confirmation to the cardholder's address on August 22, 2026. We request that this chargeback be reversed and $412.75 returned to the merchant. |
Authentication results are often central to a 4837 response, because a successful 3-D Secure authentication can shift fraud liability to the issuer when the transaction qualifies. Confirm the liability-shift status with your processor before relying on it. Keep the rest of the evidence focused on proving the account holder placed the order.
Common Mistakes That Lose Chargeback Disputes
Most lost disputes fail on presentation as often as on evidence. Stripe’s dispute evidence best practices and Visa’s merchant guidance point to the same avoidable mistakes.
- Sending the full terms of service or a link to them instead of the relevant excerpt.
- Including evidence that answers a different reason code.
- Writing an emotional or accusatory letter instead of a neutral one.
- Using color highlighting that disappears when the file is printed or converted, instead of bold text, callouts, or arrows.
- Submitting evidence that is not in English without a translation.
- Missing the processor’s deadline, which ends the dispute automatically.
Fixing these mistakes is the fastest way to learn how to win a chargeback dispute more often. The same principles hold for PayPal chargeback disputes and for winning a fraud dispute with a card issuer. At higher volumes, many merchants move to dispute management for merchants tools, including AI agents that automate chargeback rebuttals by collecting evidence and drafting the letter for each code.
Build Your Next Rebuttal Around the Reason Code
A chargeback rebuttal letter wins when it answers the exact claim behind the reason code with evidence the issuer can verify in a few minutes. Keep a template for each common code, store the evidence each one needs at the time of the order, and log every deadline the day a case arrives. Start with the codes that hit your business most often, write one sample letter for each, and review your win rate by code each month so you know which templates need stronger evidence.
Frequently Asked Questions
Charity Amancio
Charity Amancio specializes in SaaS solutions for global eCommerce businesses, including payments and risk management applications. She bridges the gap between technology and merchant needs, offering practical perspectives on the tools shaping eCommerce. Her insights appear regularly in B2B publications covering the digital commerce space.