A customer disputes a charge with their credit card company, and the money is pulled from your account before you even know it happened. You have the order record, the delivery confirmation, and the email exchange showing they received exactly what they paid for. Now you have to write a chargeback dispute response that presents the facts clearly enough to win the case.
Writing a polite email template to dispute chargeback claims submitted by credit card customers is not about being forceful. It is about presenting evidence in the exact format the card network expects, within the response window, and with a tone that reads as factual rather than defensive.
The step-by-step process below covers how to structure a dispute from the moment the chargeback appears to the moment you submit your response. Three copy-ready templates handle different scenarios, followed by the common mistakes that sink otherwise winnable disputes and a checklist to run before submission.
Understand What a Chargeback Actually Is Before You Respond
A chargeback is not a refund request. It is a formal dispute filed by the cardholder with their issuing bank, which reverses the transaction and forces the merchant to prove the charge was legitimate.
From the moment the chargeback is filed, the money is typically held or withdrawn from your account. Your response goes to the acquiring bank, which forwards it to the issuing bank, which makes the final decision. Understanding that chain matters because it tells you what to write and who actually reads it.
Most chargebacks fall into one of these categories:
- Fraudulent charge. The cardholder claims they never authorized the transaction.
- Product not received. The customer says the goods or services were never delivered.
- Product not as described. The customer claims what arrived did not match what was advertised.
- Subscription not canceled. The customer says they canceled but were still charged.
- Duplicate processing. The customer claims they were charged more than once for the same purchase.
Each category requires different evidence. A "product not received" dispute needs tracking data. A "not as described" dispute needs the product listing, the customer's order confirmation, and any correspondence showing they accepted the item. Knowing the category tells you exactly which documents to attach.
Walk Through the Dispute Response Step by Step
Chargeback responses have a deadline, usually seven to twenty-one days depending on the processor and card network. Missing that window means the chargeback stands automatically. Work through these steps in order.
- Confirm the deadline first. Find the response due date in the notification. This sets your entire timeline.
- Identify the reason code. The code determines what the cardholder claimed and what evidence you need to submit.
- Gather the evidence. Pull together the order confirmation, proof of delivery, signed agreements, IP logs, communication history, and any policy disclosures the customer saw.
- Match the evidence to the claim. Do not dump every document you have. Submit only what addresses the specific reason code.
- Write a short, factual cover letter. The email or document that accompanies your evidence should be brief and structured. Long narratives weaken the submission.
- Submit through the correct channel. Use the portal or process your processor requires. Do not reply to the chargeback notification email unless instructed.
- Save everything. Keep a copy of your submission, the evidence, and the confirmation of receipt. You may need it if the case escalates.
The cover letter is where most disputes are won or lost. It should state the transaction date, the amount, the reason code you are rebutting, and a short paragraph explaining why the evidence proves the charge was legitimate. Do not argue with the customer. Address the bank, not the cardholder.
If you sell services rather than physical goods, the evidence set looks different. Service chargebacks rely on signed agreements, IP logs, usage data, and communication records showing the customer received what they paid for. Physical goods rely on tracking, delivery confirmation, and signatures.
Copy-Ready Templates for Disputing Chargeback Claims
Each template below fits a different reason code. Replace every bracketed placeholder, attach the evidence, and submit through the channel your payment processor requires.
Option 1: Product Delivered — Rebutting "Item Not Received"
Use this when the cardholder claims the product was never delivered but you have delivery confirmation.
Subject line options:
- Chargeback response — case [Case Number], reason code [Code]
- Evidence submission for transaction [Transaction ID]
- Rebuttal to chargeback claim on order [Order Number]
To: [Acquiring Bank or Processor Chargeback Department]
Subject: Chargeback rebuttal — case [Case Number]
Dear Dispute Resolution Team,
I am submitting evidence to rebut the chargeback filed on transaction [Transaction ID] for [Amount] on [Transaction Date], reason code [Code].
Summary of facts:
- The customer placed order [Order Number] on [Order Date] through [Sales Channel].
- Payment of [Amount] was processed on [Transaction Date] and confirmed.
- The order was shipped on [Ship Date] via [Carrier] with tracking number [Tracking Number].
- Delivery was confirmed on [Delivery Date] at [Delivery Address], as shown in the attached carrier documentation.
- The customer [Signed for the package / Received the package per GPS tracking / Acknowledged receipt in writing on [Date]].
Evidence attached:
1. Order confirmation showing the customer's name, address, and order details
2. Payment transaction record
3. Carrier tracking record showing delivery confirmation
4. [Any Additional Evidence, such as a signed delivery receipt or customer communication]
The evidence demonstrates that the transaction was legitimate and the product was delivered as agreed. I respectfully request that the chargeback be reversed.
Please contact me if additional information is required before the response deadline.
Sincerely,
[Your Name]
[Company Name]
[Contact Details]Option 2: Service Delivered — Rebutting "Product Not as Described"
Use this when the cardholder claims the service did not meet expectations but you have records showing otherwise.
Subject line options:
- Chargeback response for [Service Name] — case [Case Number]
- Service delivery evidence for transaction [Transaction ID]
- Rebuttal submission — reason code [Code]
To: [Acquiring Bank or Processor Chargeback Department]
Subject: Chargeback rebuttal — case [Case Number]
Dear Dispute Resolution Team,
I am submitting evidence to rebut the chargeback filed on transaction [Transaction ID] for [Amount] on [Transaction Date], reason code [Code].
Summary of facts:
- The customer engaged [Company Name] for [Service Description] on [Agreement Date].
- The scope, deliverables, and terms were documented in [Agreement or Contract Reference] and accepted by the customer on [Acceptance Date].
- The service was delivered on [Delivery Date] as evidenced by [Specific Proof, such as completion report, access logs, or delivered files].
- The customer [Acknowledged Completion / Continued to Use the Service / Provided Feedback] on [Date].
Evidence attached:
1. Signed agreement or accepted terms of service
2. Delivery documentation showing the service was provided
3. Communication records demonstrating the customer's acknowledgment
4. Usage logs or access records confirming the customer received the service
The evidence shows the service was delivered as described in the agreed scope. The cardholder's claim does not reflect the documented transaction. I respectfully request that the chargeback be reversed.
Sincerely,
[Your Name]
[Company Name]
[Contact Details]Option 3: Subscription — Rebutting "Canceled but Charged"
Use this when the cardholder claims they canceled a subscription before the disputed charge.
Subject line options:
- Subscription chargeback response — case [Case Number]
- Evidence of active subscription for transaction [Transaction ID]
- Rebuttal to cancellation claim — [Customer Reference]
To: [Acquiring Bank or Processor Chargeback Department]
Subject: Chargeback rebuttal — case [Case Number]
Dear Dispute Resolution Team,
I am submitting evidence to rebut the chargeback filed on transaction [Transaction ID] for [Amount] on [Transaction Date], reason code [Code].
Summary of facts:
- The customer subscribed to [Service Name] on [Subscription Date] and agreed to [Billing Terms] at signup.
- The subscription remained active and the customer used the service through [Last Usage Date], as confirmed by account access logs.
- The customer was charged [Amount] on [Transaction Date] per the agreed billing cycle.
- No cancellation request was received before the charge date, as confirmed by [Cancellation System Records / Email History].
Evidence attached:
1. Subscription signup confirmation showing the agreed billing terms
2. Account usage logs demonstrating active use of the service
3. Cancellation system records showing no cancellation request before the charge
4. [Any Customer Communication Received After the Charge]
The evidence demonstrates the customer's subscription was active at the time of the charge. The cancellation policy was disclosed at signup and no cancellation was submitted before the billing date. I respectfully request that the chargeback be reversed.
Sincerely,
[Your Name]
[Company Name]
[Contact Details]Which Mistakes Sink Otherwise Winnable Disputes?
Most chargeback disputes are lost because of how the response was assembled, not because the merchant was wrong. These are the errors that consistently cost merchants cases they should have won.
- Missing the response deadline. The most common reason disputes are lost automatically. The deadline is firm and no extension is granted.
- Submitting irrelevant evidence. Dumping hundreds of pages does not help. Submit only what addresses the specific reason code.
- Writing an emotional narrative. Banks are not persuaded by frustration. They respond to facts, dates, and documentation.
- Arguing with the cardholder instead of answering the bank. Address the issuing bank's reason code, not the customer's perceived motives.
- Failing to prove the correct transaction. Make sure the transaction ID, amount, and date in your response match the chargeback notice exactly.
- Missing the cardholder's name and billing address. The issuing bank needs to verify the transaction matches their records.
- Using the wrong submission channel. Responding by email when the processor requires a portal submission means the response was never recorded.
- Skipping documentation on services. Service chargebacks require proof of delivery in a different form than physical goods. Access logs and usage records matter.
- Not confirming receipt of the submission. Always save the confirmation number or acknowledgment so you have a record.
One mistake that damages future disputes is failing to analyze the pattern. If chargebacks come from the same customer segment or the same product, the problem may be in the sales process, the product description, or the refund policy rather than individual transactions.
Run This Checklist Before You Submit the Dispute
Review these points before submitting any chargeback response. It takes a few minutes and can make the difference between winning and losing the case.
- The response deadline has been confirmed and is not at risk
- The reason code has been identified and your response addresses it specifically
- Every document submitted relates to the transaction in dispute
- The transaction ID, amount, and date match the chargeback notice exactly
- The cardholder's name and billing address are included
- The cover letter is short, factual, and addressed to the bank
- All attachments are legible and labeled clearly
- The submission is going through the correct channel
- A confirmation number or acknowledgment has been saved
- The full submission package has been archived for future reference
- Any patterns across multiple chargebacks have been reviewed
Once the dispute is submitted, mark the expected decision date on your calendar. If the chargeback is reversed, close the case and note the outcome. If the decision goes against you, review the issuing bank's explanation carefully, because it often identifies exactly what evidence was missing and how to strengthen your next response.
Frequently Asked Questions
Q: How do I dispute a chargeback claim from a credit card customer?
A: Respond within the deadline specified in the chargeback notice, identify the reason code, and submit evidence that directly addresses the claim. Include the order confirmation, proof of delivery or service, and any communication with the customer. Write a short cover letter that states the facts and addresses the bank rather than the customer.
Q: What evidence do I need to win a chargeback dispute?
A: The evidence depends on the reason code. For product not received claims, you need shipping and delivery confirmation. For product not as described claims, you need the original product listing and acceptance records. For subscription disputes, you need signup confirmation, usage logs, and cancellation records. Submit only what addresses the specific claim.
Q: How long do I have to respond to a chargeback?
A: Response windows vary by card network and payment processor, typically between seven and twenty-one days from the chargeback notification. Check the specific deadline in your notice and submit well before it. Missing the window means the chargeback stands automatically without review.
Q: Can I contact the customer directly to resolve a chargeback?
A: In most cases, no. Contacting the cardholder directly about a chargeback can violate card network rules and weaken your position. All communication should go through the banks involved in the dispute. If you have a pre-existing relationship with the customer, focus on resolving the underlying issue separately from the formal chargeback process.
Q: What if my chargeback dispute is denied?
A: Review the issuing bank's explanation carefully, since it usually identifies the specific evidence that was missing. You may have the option to appeal or submit additional documentation depending on the processor and card network. If the amount is small, weigh the cost of further action against the value of the disputed transaction.