Email to a Customer Who Filed a Chargeback: 8 Templates

A chargeback notification shows up in your payment processor's dashboard, not your inbox, so the instinct is to leave it there and let the bank handle it. That's half right. The bank fights the chargeback with the card network using evidence you submit through the processor.

The customer email is a separate track, aimed at the cardholder, and it does something the evidence packet can't: it asks them to just call their bank and withdraw the dispute, which is faster and cheaper than winning a formal review. This post has the eight emails, when to send each, and what to do when nobody replies.

When to send a chargeback response email#

Send it as soon as you see the dispute in your processor dashboard, ideally within 24-48 hours. The cardholder's memory of the transaction is freshest right after they filed, and most card networks give you a fixed window (usually 20-45 days depending on the reason code) to respond to the bank as well — sending the customer email first doesn't extend that clock.

Two situations call for it and one doesn't. Send when you believe this is friendly fraud (they forgot the subscription, a family member used the card, or they disputed instead of asking for a refund) or when you have clear proof of delivery and want to give them a chance to drop it before you escalate. Skip it if the transaction is confirmed stolen-card fraud — in that case there is no customer relationship to repair, and you go straight to evidence submission.

What a good chargeback email contains#

• The transaction date and last four digits of the card, so they can find it in their own statement without you sending the full number
• A short, neutral statement of what the charge was for — no accusatory language, no assumption of intent
• One clear ask: either withdraw the dispute by calling the number on the back of their card, or reply if they think it's an error
• A deadline that matches your dispute-response window, stated as a date, not a vague 'soon'
• No mention of legal action, collections, or account bans in the first email — save escalation language for the second attempt, if there is one

The templates#

Each template below is copy-paste ready. Replace every bracketed field before sending, and drop lines that don't apply to your situation — a template with irrelevant fields left in reads as generated, and generated reads as ignorable.

Template 1: The friendly-fraud clarification#

Use this when the charge is legitimate but you suspect the cardholder didn't recognize the merchant name on their statement — the single most common cause of an unnecessary dispute.

Subject: About your recent transaction with [COMPANY NAME]

Hi [CUSTOMER NAME],

We noticed a chargeback was filed on [TRANSACTION DATE] for a charge of [AMOUNT] on the card ending in [LAST 4]. This charge is for [PRODUCT/SERVICE], which we have on record as [DELIVERED/ACTIVE] as of [DATE].

Sometimes our statement descriptor ([DESCRIPTOR TEXT]) doesn't match the name customers expect, which is the most common reason for this kind of dispute. If that's what happened here, you can withdraw the dispute by calling the number on the back of your card and referencing dispute reason code [DISPUTE REASON CODE].

If you believe this charge is genuinely incorrect, reply to this email by [DEADLINE DATE] and we'll look into it together.

Thanks,

[YOUR NAME]

Template 2: The forgotten-subscription reminder#

Subject: Your [PRODUCT NAME] subscription and the recent dispute

Hi [CUSTOMER NAME],

We saw a chargeback come through on [TRANSACTION DATE] for [AMOUNT], and wanted to check in before it goes further. Our records show you've had an active [PLAN NAME] subscription since [START DATE], with the most recent renewal on [TRANSACTION DATE].

If this subscription slipped your mind, no hard feelings — you can cancel anytime from your account settings, and we're happy to close it out going forward. But because the service was active and used ([LAST ACTIVITY DATE]), we'd ask you to withdraw the dispute with your bank rather than dispute a charge for something you were using.

Let us know by [DEADLINE DATE] if you'd like help cancelling instead.

[YOUR NAME]

Template 3: The delivered-service evidence summary#

Subject: Documentation for your dispute on [TRANSACTION DATE]

Hi [CUSTOMER NAME],

We're responding to the chargeback filed on [TRANSACTION DATE] ([DISPUTE REASON CODE]) for [AMOUNT]. Before we submit our evidence to your bank, we wanted to share it with you directly, since it's often faster to resolve this way.

Service delivered: [DESCRIPTION]

Delivery confirmation: [TRACKING NUMBER / LOGIN TIMESTAMP / SIGNED RECEIPT]

Your acceptance of terms: [DATE, IP ADDRESS OR SIGNATURE REFERENCE]

If this matches your understanding, withdrawing the dispute avoids a formal review that can take [PROCESSOR'S TYPICAL TIMELINE] and doesn't change the outcome either way. If something here looks wrong, tell us — we'd rather fix it than argue about it.

[YOUR NAME]

Template 4: The withdraw-the-dispute request#

Use this as a direct, single-purpose ask when you've already established the facts and just need action.

Subject: Please withdraw the dispute on [TRANSACTION DATE]

Hi [CUSTOMER NAME],

Following up on the chargeback for [AMOUNT] filed on [TRANSACTION DATE]. Since [briefly restate why this charge is valid, e.g. "the order was delivered and signed for on the same day"], we'd ask you to call your card issuer and withdraw the dispute referencing case [DISPUTE REASON CODE].

This usually takes under five minutes on the phone with your bank. If you'd rather we handle it differently — a partial credit, a replacement, anything — reply and we'll sort it out directly instead of through the dispute process.

[YOUR NAME]

Template 5: The account-suspension notice#

Send this only after a first attempt went unanswered and your terms of service allow suspension for unresolved disputes on an active account. Say what happens, not what you feel about it.

Subject: Your [PRODUCT NAME] account is on hold

Hi [CUSTOMER NAME],

We haven't heard back regarding the chargeback filed on [TRANSACTION DATE], and per our terms of service, accounts with an open dispute on an active subscription are placed on hold until it's resolved. Your account access is currently paused as of [SUSPENSION DATE].

To restore access, either withdraw the dispute with your bank or reply here so we can work it out. We'd rather resolve this than lose you as a customer.

[YOUR NAME]

Template 6: The evidence-plus-alternative offer#

Subject: One more option on the [TRANSACTION DATE] dispute

Hi [CUSTOMER NAME],

We're preparing to submit evidence to your bank for the dispute on [TRANSACTION DATE], but before we do, we want to offer a faster resolution: a [REFUND/CREDIT/REPLACEMENT] of [AMOUNT], issued directly by us, in exchange for withdrawing the dispute.

This avoids a formal review for both of us and gets you a resolution in days instead of weeks. If that works, reply by [DEADLINE DATE] and we'll process it same-day.

[YOUR NAME]

Template 7: The subscription cancellation confusion#

Subject: About the dispute and your cancelled subscription

Hi [CUSTOMER NAME],

We saw a chargeback filed on [TRANSACTION DATE], and want to check whether this relates to a cancellation that didn't go through as expected. Our records show your subscription was [STILL ACTIVE / CANCELLED ON DATE], and the charge in question covers [BILLING PERIOD].

If you cancelled and were still charged, that's on us to fix — reply and we'll refund it directly, no dispute needed. If the subscription was active for that period, we'd ask you to withdraw the dispute instead.

[YOUR NAME]

Template 8: The final notice before escalation#

This is the last email in the sequence, sent only once, and only when the account is enterprise or high-value enough to justify one more attempt before you write off the relationship.

Subject: Final notice: chargeback on [TRANSACTION DATE]

Hi [CUSTOMER NAME],

This is our final follow-up on the chargeback filed [TRANSACTION DATE] for [AMOUNT]. We've submitted our evidence to your bank, including [BRIEF EVIDENCE SUMMARY]. If the dispute is decided in our favor, the charge will be reinstated along with any dispute fee ([FEE AMOUNT], per our terms).

We'd still rather resolve this directly — reply by [DEADLINE DATE] and we can find a solution before the bank's decision comes back.

[YOUR NAME]

The hard version: a customer who filed instead of replying#

The templates above assume the customer just needs the facts. The harder case is someone who emailed support three times, got a slow or unsatisfying answer, and disputed instead of writing a fourth email. That's not fraud — it's a broken support loop, and treating it like fraud makes it worse.

Start by pulling the full thread before you draft anything. If your last reply to them took more than 24-48 hours, or didn't actually resolve their issue, open with an apology for the delay before you get to the dispute at all. Then make the actual offer concrete: a specific credit, a specific fix, a specific date — not "we'll look into it."

The tell that you're dealing with this case rather than friendly fraud is tone: a friendly-fraud dispute reads confused when you follow up, and a broken-support dispute reads frustrated. Match the response to which one you're looking at, because the wrong template on the wrong case reads as a form letter to someone who already feels ignored.

What to do if there's no reply#

Where AI Emaily fits#

Chargeback emails are exactly the kind of writing that's easy to get right in a template and wrong under deadline pressure — the wrong tone, a missing transaction date, a threat that shouldn't be there. AI Emaily drafts replies in your voice from a Personal Context brain you set yourself, so a customer-support account can keep the fact-first, no-accusation tone across every dispute email without someone rewriting the same structure by hand each time.

Every draft still goes through Copilot review before it sends — nothing goes out on a dispute without a human reading it first, which matters more here than on almost any other email type. We build AI Emaily.