KoltrixChargebacks and payment disputes: handling them by email
A customer disputes a charge with their bank. How to prevent most disputes, reply fast, gather evidence from your email and keep the relationship if you can.
On this page(7 sections)
- What a chargeback is
- Prevention: the emails that stop disputes
- Make the charge recognisable
- Warn before charging
- Handle failed payments gracefully
- Make refunds quick and easy
- Make it easy to reach you
- When the dispute arrives
- 1. Check the deadline and read the reason
- 2. Look up the customer
- 3. Decide: accept, refund or contest
- 4. Gather the evidence
- 5. Write a clear response
- Should you email the customer?
- Possible fraud
- Learn from the pattern
- Key takeaways
A notification arrives from your payment processor: a customer has disputed a charge. The money has already been pulled back, you have a few days to respond, and a fee has been added. The customer, who a week ago seemed happy, never wrote to you.
Chargebacks feel unfair, but they are a normal cost of taking payments, and most are avoidable. Your inbox is part of the story twice: before the dispute, where clear emails prevent it, and after, where your records are the evidence. This guide covers both. It is general information, not legal or financial advice, and the rules vary by card network, processor and country, so read your processor's current guidance.
What a chargeback is
A chargeback is a reversal of a card payment that the customer asks their bank to make. The bank pulls the money back from you and asks you to prove the charge was legitimate. If you cannot, or do not respond, you usually lose the amount and pay a fee.
Customers dispute charges for several reasons:
- They do not recognise it. The statement shows a name or descriptor they do not associate with you.
- They forgot they subscribed, or a free trial turned into a paid plan.
- They wanted a refund and found disputing faster than asking.
- They believe it is fraud, sometimes correctly, when their card was stolen.
- They were unhappy with the product or service.
- A family member or a colleague made the purchase.
- A refund was promised and not completed.
Notice that many of these are communication problems, not bad faith.
Prevention: the emails that stop disputes
Make the charge recognisable
- Use a clear statement descriptor that matches your product name, and include a support contact if your processor allows it.
- Send a receipt straight after each payment with the product, amount, date and a link to billing. See invoice and receipt emails.
Warn before charging
- Send a reminder before a trial ends and before an annual renewal, saying what will be charged, when and how to cancel. See trial-ending emails without pressure and annual renewal reminder emails.
- Make cancellation easy to find, and send a confirmation when it happens. See cancellation confirmation emails.
Handle failed payments gracefully
Clear, calm messages about failed payments and expiring cards reduce confusion and surprise charges.
Make refunds quick and easy
If asking for a refund is easy, fewer people go to their bank. Keep a simple policy, answer billing questions fast and process agreed refunds the same day. Refund and billing emails has templates.
Make it easy to reach you
A visible support address and a quick first reply is cheap insurance. See first response time versus resolution time.
When the dispute arrives
1. Check the deadline and read the reason
Your processor's dashboard shows the reason code and the date by which you must respond. Missing it usually means automatic loss. Put the date in your calendar at once.
2. Look up the customer
- Is there an account, a login history or usage?
- Which emails did you send: receipt, renewal notice, support replies?
- Did they contact you before? Search your shared inbox for the address and name.
- Did they ask for a refund or cancellation that you missed?
Repeat contacts and reopened conversations shows how to read the history in a thread.
3. Decide: accept, refund or contest
- Accept when the customer is right, for example you missed a cancellation. Fighting costs time and may cost more.
- Refund the customer directly if they are reasonable and the dispute is still open. Check your processor's rules, because refunding can sometimes lead to paying twice or not stopping the dispute.
- Contest when you have clear evidence that the service was delivered and the charge was valid.
4. Gather the evidence
Typical evidence includes:
- the receipt and the invoice you sent, with dates;
- proof the customer used the product: logins, features used, files created, messages sent;
- copies of the emails confirming the purchase, the renewal reminder and the terms the customer accepted;
- the customer's support messages, showing they received help or never complained;
- the refund policy as it was shown at the time of purchase;
- delivery records for physical goods or access logs for digital ones.
Your email is strong evidence: it shows what you told the customer and when. Export the relevant messages as PDF or text, with headers showing dates and addresses.
5. Write a clear response
Processors usually ask for a short statement and attachments. Keep it factual:
- who the customer is and what they bought;
- when they were charged and how they were told;
- how they used the service;
- what contact you had;
- why the charge was valid.
Avoid emotion, accusations and long stories.
Should you email the customer?
Often yes, in a calm, short message. Be careful: some processors and banks prefer you do not pressure the customer to withdraw a dispute, and rules differ. Check your processor's guidance before asking someone to cancel a dispute.
A neutral message might say:
Hi Jordan,
I saw that the charge of USD 29 on 3 October was disputed with your bank.
I want to make sure this is resolved properly. If something was wrong
with the charge or the service, please reply and tell me, and I will
fix it or refund you straight away.
If it was a mistake or the charge was not recognised, here is the
receipt for reference: [link].
Best,
SamDo not threaten, and do not say the account will be closed unless that follows your documented terms.
Possible fraud
If the customer says they did not make the purchase, take it seriously. Their card may have been stolen, or someone used your service with stolen details.
- Check for suspicious patterns: many accounts from one source, mismatched countries, odd email addresses.
- Cancel the account and stop further use.
- Do not contest if you believe the charge was fraudulent.
- Look at your signup and payment checks to see what you can tighten.
Be careful with requests that ask you to refund to a different account or card; this is a common scam. See BEC and invoice fraud red flags and verifying identity for account access requests.
Learn from the pattern
Count disputes and note the reasons.
- Many "unrecognised" charges suggest a descriptor or receipt problem.
- Many trial-to-paid disputes point to a weak reminder email.
- Many "refund promised" cases show a gap in your refund process.
- A high dispute rate can bring warnings or fees from your processor, and in serious cases restrictions, so watch it as a metric.
Share findings with whoever owns billing and with your escalation path.
Key takeaways
- Most chargebacks come from confusion, forgotten subscriptions or slow refunds, so clear emails prevent them.
- Make charges recognisable, warn before renewals and make cancelling and refunding easy.
- When a dispute arrives, note the deadline, check the history and decide whether to accept, refund or contest.
- Your emails are evidence: receipts, reminders, support threads and terms.
- Treat disputes as feedback, and check your processor's rules for what you may say to the customer.
Start with Koltrix
Your domain, one inbox, and an API that sends.
A team inbox where AI sorts and drafts (nothing is sent without your click), plus the transactional API and SMTP relay your product sends with. 7 days free, no card.
