How to Reply When a Customer Threatens a Chargeback

When a customer threatens a chargeback, reply fast and stay calm. Find the payment, ask what went wrong, and offer a clear fix or refund before they go to their bank. Don't argue, don't threaten them back, and don't promise anything you can't deliver. Most of these messages come from people who are frustrated or confused. They aren't usually trying to cheat you. Solving the real problem is nearly always cheaper and faster than fighting a dispute.

The rest of this guide covers why timing matters, a step-by-step way to write the reply, sample replies you can adapt, and what changes once the customer has actually filed a dispute.

Why the timing matters

A chargeback threat is still a support conversation. A filed dispute is a payment process with fees, deadlines and rules you don't control. Stripe's documentation lays out the difference clearly. Other payment processors work differently, so check your provider's docs too.

Documented facts (Stripe):

• Disputes cost money even when you're in the right. In the US, Stripe charges a $15 fee for each dispute, plus a $15 counter fee if you contest it. The counter fee is refunded if you win (Stripe dispute pricing). Fees vary by country, and outside Mexico the dispute fee itself is non-refundable (Stripe: How disputes work).
• Once a dispute is open, you can't just refund. While a dispute is open, you can't issue a refund outside the dispute process, and the disputed amount is taken from your balance (Stripe: How disputes work).
• Fully refunded payments can't be disputed, but partially refunded ones can. Card network rules even allow a customer to dispute the full amount of a payment you partly refunded (Stripe: Fraud prevention best practices).
• Disputes are slow. After a chargeback is created you usually have 7 to 21 days to respond, and the whole process can take 2 to 3 months (Stripe: How disputes work).
• Disputes count against you. Each dispute raises your dispute rate with the card network, even if the customer later withdraws it (Stripe: Withdrawing disputes). Stripe notes that for very small businesses (for example, under 100 payments a month), one or two disputes can noticeably affect that rate (Stripe: Fraud prevention best practices).

What this means in practice (analysis): for a small product, resolving the issue in the inbox is almost always better than winning a dispute. The window to do that is the time between the threat and the filing.

Step-by-step: how to write the reply

1. Reply quickly, even if you can't solve it yet

A slow reply can push a frustrated customer to file. If you need time to investigate, say so and give a realistic timeframe. Our guide to using reply time estimates covers how to set expectations without overpromising.

2. Find the payment before you write anything else

Look up the customer, the charge date, the amount, the plan and any earlier conversations. Check for these common causes:

• They don't recognize the charge. Your statement descriptor may not match your product name. Stripe recommends a descriptor that uses your website domain or business name (Stripe: Fraud prevention best practices).
• They forgot a renewal. Annual plans are a common case.
• They were charged twice, or charged after they thought they'd cancelled.
• The product didn't do what they expected. Sometimes that's a bug. Sometimes it's a mismatch with what they thought they were buying.
• Someone else used their card. This is possible fraud, and you handle it differently (see below).

3. Acknowledge the problem without repeating the threat

You don't need to say "chargeback" back to them. Focus on the issue behind it: an unexpected charge, a feature that doesn't work, a cancellation that didn't go through. Calmly naming what happened lowers the temperature more than any reassurance will.

4. Offer one clear way forward

Be specific: what you'll do, how much, and when. Vague replies like "we'll look into it" tend to make people escalate. Your options usually include:

• A full refund. This is the cleanest option when the charge was a mistake or the customer got little value.
• Cancelling the subscription to stop future charges.
• A fix or workaround if the product problem is solvable.
• A partial refund or credit, but only if the customer clearly agrees. Remember that a partially refunded payment can still be disputed for the full amount.

If the request falls outside your refund policy, you still have choices. See how to reply when customers ask for policy exceptions.

5. Say what will happen next

Tell them when the refund will be issued and roughly when it should appear on their statement, while being clear that their bank controls that last part. Confirm in writing once it's done.

6. Keep everything in writing

Save the conversation, the charge details, any proof of cancellation or usage, and the refund confirmation. If a dispute happens anyway, you'll need this evidence. Stripe also notes that issuers expect to see that customers were shown your refund and cancellation policies before purchase (Stripe: Fraud prevention best practices).

Sample replies (hypothetical)

These are illustrative templates, not real customer exchanges. Edit them to fit your product, your policy and your own voice.

When the customer doesn't recognize the charge

Hi Sam,

>

Thanks for flagging this, and sorry for the confusion. I found a charge of $49.00 on March 3 for an annual plan of [Product] under this email address. On your statement it shows up as "PRODUCTCO".

>

If you didn't mean to renew, I can refund it in full today and cancel the plan so it doesn't renew again. Just reply "refund" and I'll take care of it. If you don't recognize the account at all, let me know that too, and I'll refund it and lock the account.

>

Alex

When they forgot to cancel a renewal

Hi Priya,

>

Sorry about the surprise renewal. I can see you haven't used the app since January, so I've cancelled your subscription and issued a full refund of $120. Your bank usually takes a few business days to show it, but that timing depends on them.

>

You'll get a refund receipt by email shortly. If anything still looks off on your statement next week, reply here and I'll check it.

>

Alex

When the product isn't working for them

Hi Marco,

>

I'm sorry the sync has been failing. That's on us, and I understand why you're frustrated after paying for it.

>

I can do one of two things, whichever you prefer:

1. Look at your logs today and try to get sync working. If I can't fix it within two business days, I'll refund you in full.

2. Refund you in full right now and cancel the subscription.

>

Just tell me which one works for you.

>

Alex

If the customer has already tried a fix that failed, see how to reply when a customer says the fix didn't work. If the frustration comes from a wrong assumption about what the product does, see how to reply when a customer misunderstands your product.

What to avoid

• Threatening them back. Lines like "Filing a chargeback is fraud" or "We'll send this to collections" escalate the situation and can look bad if a dispute ends up in front of the card issuer.
• Quoting policy before you understand the problem. Lead with the facts of their charge, not your terms of service.
• Negotiating in circles. One clear offer is better than three rounds of back-and-forth.
• Promising bank timelines you can't control. You control when you issue the refund. The bank controls when it shows up.
• Asking for a refund confirmation as a condition of help. Just resolve it.

If you suspect the payment is fraud

If the customer says they never made the purchase, take it seriously. Stripe recommends immediately refunding any payment you're confident is fraudulent (unless it's covered by liability shift, such as with 3D Secure). That avoids the dispute fee and the hit to your dispute rate (Stripe: Fraud prevention best practices). Then secure or close the account involved.

If the customer has already filed

Once a formal dispute is open, the rules change:

1. You probably can't refund directly. On Stripe, you can't issue a refund outside the dispute process while the dispute is open (Stripe: How disputes work).
2. You can still ask them to withdraw it. Stripe suggests contacting the customer, resolving the issue, and asking them to withdraw the dispute with their card issuer (Stripe: Withdrawing disputes).
3. Submit evidence anyway, before the deadline. Stripe warns that even if the customer withdraws, you can still lose the dispute if you don't submit evidence. You can only submit once, and not after the deadline (Stripe: Withdrawing disputes).
4. Or accept it. For low-value disputes, accepting can make more sense than spending time contesting (Stripe: Withdrawing disputes).

A calm, factual reply still helps here. Tell the customer what you found, what you're willing to do, and what they'd need to do with their bank.

App store purchases are different

If the customer paid through the App Store, you usually can't refund them yourself. Apple handles refund requests through reportaproblem.apple.com. Your reply should apologize, point them to that page, and, if you can, offer to help with the underlying problem.

Should you use an AI draft for these replies?

Chargeback threats involve money, deadlines and sometimes fraud, so they need human judgment. An AI-drafted first version can save time on the routine parts, like looking up the charge and structuring the reply. But you should check every amount, date and promise before it goes out. Our AI draft or manual reply decision guide covers when each approach fits. SupportMe, for example, is built so that nothing sends without your approval, which matters most for messages like these.

It also helps to add a "billing complaint" section to your support reply checklist: charge found, cause identified, one clear offer, timeline stated, conversation saved.

Conclusion

A chargeback threat usually means a customer has a billing or product problem and doesn't trust you to fix it. Answer quickly, find the charge, name the real issue, and make one clear, specific offer. Before a dispute is filed, a full refund ends the matter cleanly. After it's filed, your options narrow and the process takes weeks. Fix your statement descriptor, refund obvious mistakes and fraud without arguing, and keep records of everything.

References

• Stripe: How disputes work
• Stripe: Fraud prevention best practices
• Stripe: Withdrawing disputes
• Stripe Support: June 2025 pricing updates for disputes
• Apple Support: Request a refund for apps or content that you bought from Apple