Skip to main content

Chargeback response template: the Stripe dispute rebuttal, and the email to send the customer first

Six templates for a disputed payment on software or a subscription: two emails to the customer, three evidence summaries for the processor's response form, and the email for a dispute you decide to accept.

The templates

The first two are emails to the customer and the last is the email for a dispute you accept. The three in the middle are evidence summaries for the processor: paste the body into the free-text field of the dispute form, use the subject line as its title, and attach every document a line refers to. Delete any line you cannot back up.

To the customer: a dispute just arrived

Subject: About your [amount] payment to [Product] on [date]

Hi [Name], I have had a notice that a payment of [amount] to [Product] on [date] has been disputed with your bank. I wanted to check with you directly, in case there has been a mix-up. On your statement it appears as [the statement descriptor, for example: ACME SOFTWARE]. It was for [a yearly subscription to Product / a Product licence], bought with the email address [customer email]. If you recognise it now, you can tell your bank the charge was yours and ask them to withdraw the dispute. If you do not, or you think I got something wrong, reply and tell me. I would much rather sort it out with you than through the bank. [Your name]
To the customer: they recognise it now

Subject: Re: About your [amount] payment to [Product]

Hi [Name], Thanks for getting back to me, and no harm done: [statement descriptor] is not the most obvious name to see on a statement. [I have since changed it to something clearer.] To close the dispute, please contact your bank, tell them the charge was yours, and ask them to withdraw it. It also helps if you reply here with a line saying the same, so I can include it in my response to the bank. Your [subscription / licence] keeps working as normal in the meantime. [Your name]
Rebuttal: product not received (downloadable software)

Subject: Dispute [dispute ID]: [Product] licence delivered and activated

The cardholder bought [Product], a downloadable [Mac app / software licence], on [date] for [amount], using the email address [customer email]. The product was delivered immediately and has been used: - [date and time]: purchase completed; licence key emailed to [customer email]. Receipt and delivery email attached. - [date and time]: the app was downloaded from [our website / download link]. - [date and time]: the licence was activated on [number] device(s). Activation log attached, with [device identifiers / IP addresses, if you record them]. - [date]: the most recent use of the licence [or: the most recent licence check]. - [Any emails from the cardholder after purchase, for example: on date they asked how to move the licence to a new Mac, and were answered the same day. Attached.] At checkout the cardholder accepted our terms of sale and refund policy [link, screenshot attached], which [offers a refund within 30 days on request]. We have no record of a refund request before the dispute was opened. We ask that the dispute be decided in our favour.
Rebuttal: subscription cancelled

Subject: Dispute [dispute ID]: [Product] subscription active, no cancellation received

The cardholder subscribed to [Product] on [date] at [amount] per [month / year], using the email address [customer email]. The disputed payment of [amount] on [date] is the renewal for [the period it covers]. We have no record of a cancellation before this payment: - The subscription can be cancelled at any time from [the billing page / Settings, then Billing] or by replying to any email from us. This is stated at checkout and in our terms [link, screenshot attached]. - There is no cancellation in our billing system, and no email or message from the cardholder asking to cancel before [date]. All correspondence with the cardholder is attached. - [A renewal reminder was sent to customer email on date. Attached.] - The cardholder continued to use [Product] after the renewal: most recent [sign-in / licence check] on [date]. The service was provided for the period charged. We ask that the dispute be decided in our favour.
Rebuttal: fraudulent or unrecognised

Subject: Dispute [dispute ID]: purchase made and used by the cardholder

The payment of [amount] on [date] was for [Product], a [software subscription / software licence]. Evidence that the purchase was made by the cardholder, or with their knowledge: - The billing name and email match the account: [name], [customer email]. [The payment passed the CVC and postal code checks.] - The customer has made [number] earlier payments with the same card since [date], none of them disputed. - [The purchase was made from the same IP address or device as those earlier payments. Details attached.] - The product has been used since the purchase: [activation and sign-in dates]. - [The cardholder emailed us on date, from the same address, about using the product. Attached.] On the cardholder's statement the charge appears as [statement descriptor], which is the name of our [product / business]. We ask that the dispute be decided in our favour.
Accepting a dispute you should not fight

Subject: Your [Product] dispute: you will get the money back

Hi [Name], I have looked into the [amount] payment you disputed, and you are right: [you asked me to cancel on date and I missed it / you were charged twice / describe the mistake]. I am sorry. I have accepted the dispute, so the money goes back to you through your bank, and you do not need to do anything else. [I have also cancelled your subscription, so there will be no further charges.] If there is anything else I got wrong, reply and tell me. [Your name]

Subject lines for the email to the customer

Name the product, the amount and the date, so they can match the email to the line on their statement, and leave the words chargeback and dispute out of the first one. It is a question, not a notice, and a customer who feels accused stops reading.

  • About your [amount] payment to [Product] on [date]
  • A question about your [Product] payment on [date]
  • Re: [their last subject line] (if they had written to you before)
  • Your [Product] dispute: you will get the money back

The evidence that tends to matter for software

  • Proof of delivery and use. The licence key email, download records, activation logs with dates, sign-ins. For software this does the job a tracking number does for a parcel. Stripe’s evidence fields include one for access and activity logs.
  • The terms they accepted at checkout. Your refund and cancellation policy, and how it was shown: a screenshot of the checkout page with the policy next to the pay button is worth more than a link to a page that may have changed since.
  • Receipts and invoices sent to the customer’s email address, with the dates they went out.
  • Communications. Their emails to you after the purchase, especially ones asking how to use the product. An email about activating a licence is hard to square with a claim that nothing arrived.
  • History. Earlier payments from the same card or account that were never disputed. For fraud claims especially, a customer who paid you four times before is evidence.
  • Facts in date order, on one page. Whoever reviews it reads a lot of these. A timeline with attachments does more than an argument, and anger or accusations against the cardholder do nothing for you.

Respond before the deadline, or decide not to

Every Stripe dispute shows the date by which you must respond. Miss it and the dispute is decided in the cardholder’s favour, whatever your evidence. Once you submit, you generally cannot add to the response, so gather everything first. Stripe also charges a dispute fee, and its pricing page lists what applies to your account.

That makes some disputes cheaper to accept than to fight:

  • You were wrong. They asked to cancel and you missed it, you charged twice, a trial converted without the reminder you promised. Accept, apologise and fix whatever let it happen.
  • The card really was stolen. Accept, deactivate the licence, and do not email the address on the account, which belongs to whoever used the card.
  • The amount is smaller than your time. One month of a small subscription is rarely worth an hour of gathering logs and screenshots.
  • You have no evidence. If you do not record activations or keep the checkout terms, a response is a letter asking to be believed.

Card networks also watch how many disputes a business receives, and a high rate can mean extra fees or losing the ability to take cards. The cheapest dispute is the one that never opens: a clear statement descriptor (set in your Stripe settings) that matches the name customers know, a refund when someone asks for one within reason, and a reply to every cancellation request.

Where a dispute is usually explained

The explanation for a dispute is often in your inbox, not in Stripe. The customer who replied “please cancel” to a receipt three weeks before the renewal. The one who emailed on day two asking how to activate the licence, which is the best evidence you have that the software arrived. The one who wrote once, heard nothing, and went to their bank instead.

With Stripe connected, Moorline shows a customer’s plan and payments beside their emails, read-only, so the disputed charge and the conversation about it sit on one screen while you write the response. It cannot refund a payment, accept a dispute or submit evidence; all of that happens in Stripe. What it does earlier is keep the “please cancel” email on your list until it is done and the customer has been told, which is how a dispute never gets filed. If the conversation starts as a refund request instead, how to decline a refund request politely covers when saying no costs more than the refund.

Questions people ask

How do I respond to a chargeback?

Through your payment processor, before the deadline shown on the dispute. Choose the evidence that answers the dispute reason, write a short factual summary in date order, and attach the receipt, the terms the customer accepted, proof they received and used the product, and your emails with them. Email the customer as well: if it was a misunderstanding, they can ask their bank to withdraw it. This is not legal advice; your processor and the card networks set the rules.

What evidence wins a chargeback for software?

Nothing guarantees a result, but for downloadable software and subscriptions the evidence that tends to matter is proof of delivery and use (licence delivery, activation logs, download records, sign-ins), the terms and refund or cancellation policy shown at checkout, receipts, and emails from the customer after the purchase. Match it to the reason: usage records answer "not received", a missing cancellation request answers "subscription cancelled".

Can I refund a customer after they open a chargeback?

On Stripe, not for a payment that is already formally disputed: accepting the dispute is how the money goes back to them, and refunding as well would pay them twice. Other processors have their own rules, so check yours. The cheap moment to refund is before the dispute, when the customer first asks.

How long do I have to respond to a Stripe dispute?

The deadline is shown on each dispute in your Stripe dashboard, and it is set by the card network, so it varies. It can be shorter than you expect, so start on the day the dispute arrives rather than near the end. If you do not respond in time, the dispute is decided in the cardholder’s favour, whatever evidence you had.

Is it worth fighting a small chargeback?

Often not. Stripe charges a fee for disputes (its pricing page says what applies to your account, including whether anything comes back if you win), a good response takes an hour or more, and a win is never certain. Fight when the evidence is clear and you did nothing wrong. Accept when you were at fault, the card was really stolen, or the amount is smaller than your time.