A failed payment email is one of the most commercially important emails you will send, and one of the easiest to get wrong. The default template in most billing tools reads like a legal notice. That tone kills conversions. Most failed payments are expired cards, not intentional non-payment, and the email that recovers them is helpful, not threatening.
The mental model for a failed payment email.
Before writing a single word, establish who you are writing to. The vast majority of failed payments happen because a credit card expired, a card was replaced after fraud, or a bank declined a charge for security reasons. The customer is not trying to avoid paying you. They probably do not even know the payment failed.
That mental model should shape every word. You are not a collections department contacting a delinquent account. You are a helpful product company letting a customer know about a minor administrative issue they can resolve in one minute. Write from that position and the tone writes itself.
The emails that recover the highest percentage of failed payments share three qualities: they are short, they assume good faith, and they offer one clear path to fix the problem. Everything else is noise that reduces the chance the reader acts.
Three tone errors that hurt payment recovery.
1. Leading with the threat.
Emails that open with 'Your account will be suspended in 24 hours' or 'Action required: payment overdue' put the reader on the defensive immediately. The framing treats the customer as a debtor, not a subscriber who probably just has an expired card. Most failed payments are not intentional non-payment. The person on the other end is not trying to steal your product.
2. Multiple warnings in the same email.
Some templates pack three different warnings into the first paragraph: your subscription is past due, your account may be suspended, and your data could be at risk. Piling on creates anxiety that makes the reader less likely to act, not more. One clear problem, one clear action, one email.
3. Passive voice and corporate distance.
A payment failed email written like a legal notice ('it has come to our attention that payment has not been received') creates distance at the exact moment you need warmth. The customer relationship is at risk. This is not the moment for formal corporate language. Write to the person.
Three failed payment emails, ready to adapt.
These are the three sends in a standard dunning sequence. Adapt the product name, plan name, and CTA link. The tone is intentionally plain. Do not dress it up with marketing copy.
First email (send within hours of the failed charge)
Subject line
Quick heads up about your payment
Email body
Hey [First name],
Your [Plan name] subscription payment did not go through today. This usually means the card on file has expired or been updated.
It's a quick fix. You can update your payment details here:
[Update payment details button]
Your account is still active and nothing changes for you right now. If this was just a hiccup with your card, sorting it out takes about a minute.
Let us know if you run into anything.
The GetFluxly team
Tone note: warm, no blame, one clear action. The subject line is conversational and does not trigger spam filters with words like 'overdue' or 'urgent.'
Second email (3 to 4 days later, if unresolved)
Subject line
Still having trouble with your payment?
Email body
Hey [First name],
We sent a note a few days ago about a payment issue on your account. Wanted to follow up in case the first email got buried.
Your [Plan name] subscription is still active, but we will need a valid payment method on file to keep it that way.
[Update payment details button]
If something is going on and you need a hand, just reply to this email. We are happy to help.
GetFluxly
Tone note: empathetic follow-up, not a second warning. Acknowledges the email may have been missed. Offers human help as a real option.
Third email (7 to 8 days later, final notice before access changes)
Subject line
Your [Plan name] access changes in 2 days
Email body
Hey [First name],
We have tried to reach your card a couple of times and have not been able to process a payment. Your account access will change to the free tier in 2 days unless you update your payment details.
[Update payment details button]
If you want to keep your current setup, it takes about a minute to add a new card. All your data and automations will stay exactly as they are.
And if you have decided [Plan name] is not the right fit right now, no hard feelings. Your data will still be here if you come back.
GetFluxly
Tone note: honest about the consequence (access changes) without using words like 'suspended' or 'terminated.' The last paragraph leaves the door open, which reduces hard churn.
The five rules that produce better payment recovery copy.
1. Use the customer's first name. Personalization in a dunning email is not a nice touch. It is the difference between a legal notice and a message from someone who knows you. Pull the first name from the customer profile and use it in the opening line.
2. Say the problem in one sentence. 'Your payment did not go through.' That is the whole problem. Do not bury it in a paragraph. Say it clearly in the first sentence so the reader knows immediately what this email is about and can decide to act.
3. One CTA, not three. Update payment details. That is the only action in the email. No link to the help center, no invitation to upgrade, no social share. One problem, one fix, one button.
4. Tell them their access is still active (if it is). Many customers assume that a failed payment means their account is already gone. If their account is still active, say so. It removes a reason to abandon and motivates them to act quickly to keep what they have.
5. Offer a real exit. In the last email before access changes, give the customer permission to leave gracefully. Something like 'if [Product] is not the right fit right now, no hard feelings.' This one sentence reduces hard churn to a soft churn that leaves the door open for return.
For the mechanics of building a full dunning sequence as an automation, including retry logic and timing, read the complete dunning email sequence guide. For the broader context of where payment recovery fits in your lifecycle email program, see the lifecycle email automation pillar.
Failed payment emails, answered.
What should the subject line of a failed payment email say?
Keep it simple and neutral. Something like 'Quick heads up about your payment' or 'We had trouble processing your payment' works well. Avoid words like 'urgent,' 'overdue,' or 'action required' in the subject line. Those words either trigger spam filters or put the reader on the defensive before they open the email.
How many failed payment emails should I send before canceling an account?
Three emails over 7 to 10 days is the standard sequence for SaaS: one within hours of the failed charge, one follow-up at day 3 to 4, and a final notice at day 7 to 8 before access changes. Some products send a fourth at the very last moment. See the dunning email sequence guide for the mechanics of setting this up as an automation.
Should a failed payment email be from a person or from the company?
From a person if your product has a support or success team. Something like 'Sarah from GetFluxly' feels more human than 'The GetFluxly Team.' If you are a solo founder, send it from your own name. First-person emails get higher reply rates, which matters when the customer has a question or a real hardship they want to explain.
What tone should a failed payment email use?
Helpful and factual, not threatening. The mental model that produces the best copy is: write as if a trusted customer support person is sending a note to a longtime user who probably just has an expired card. Assume good faith on the customer's part. State the problem clearly, provide one obvious path to fix it, and leave the door open for them to reply if something is going on.
What is the difference between a failed payment email and a dunning sequence?
A failed payment email is the individual message. A dunning sequence is the full automated series of emails sent after a payment fails, spaced out over days until the payment is recovered or the subscription changes state. This post focuses on the copy and tone of individual failed payment emails. For the mechanics and setup of a full dunning sequence, see the dedicated dunning sequence guide.
If you want to automate the full dunning sequence rather than manage individual sends, GetFluxly can trigger the first email within minutes of a failed payment event from your billing system via the HTTP Events API, then run the follow-up sequence automatically with branching logic that exits the moment payment recovers. See pricing or visit the integrations page for ESP and billing tool connection details.