What Should a SaaS Send After a Failed Payment?

What should a SaaS company send a customer after a failed payment?

Send a short, calm email right away that says the payment did not go through, names the plan and amount, and gives a one-click link to update the payment method. Follow up a few times before any service change, each message clearer about the deadline. Treat the customer as someone with an expired card, not a debtor.

Failed payments are one of the quietest causes of churn in subscription software. The customer did not decide to leave. Their card expired, their bank flagged a charge, or their company changed corporate cards. Yet if nobody handles it well, the account still ends up canceled.

This is often called involuntary churn, and it is one of the most fixable kinds. I build lifecycle and billing-adjacent automations for B2B SaaS teams, and the failed payment flow is one of the first places I look when a company wants to improve retention without changing the product. Here is what to send, when, and why.

Why do failed payments matter so much for a B2B SaaS company?

Because every failed payment that is not recovered becomes churn from a customer who never chose to leave. These customers often still use and like the product. Losing them is pure waste. A good recovery flow, combining automatic retries and clear emails, saves revenue that would otherwise disappear without anyone noticing.

In B2B, the person whose card is on file is often not the person who uses the product every day. The finance contact might be on vacation, or the card might belong to someone who has left the company. Your recovery emails need to reach someone who can actually fix the problem.

The cost of getting this wrong is also reputational. A harsh, threatening email to a loyal customer whose card simply expired can damage a relationship that took months to build.

What should happen automatically before any email goes out?

Your billing system should retry the charge automatically, because many failures are temporary. Stripe's documentation, for example, says Stripe Billing can automatically retry failed subscription and invoice payments, and that its Smart Retries feature uses AI to choose the best times to retry. Emails should run alongside these retries, not replace them.

Stripe's docs describe the recommended default Smart Retries setting as 8 tries within 2 weeks, and they let you choose other policies. Other billing platforms have their own retry options, so check your provider's official documentation for what is available and what is switched on by default.

Retries cannot fix everything. Stripe's documentation lists hard decline codes, such as a lost or stolen card, where it cannot automatically retry the payment until the customer provides a new payment method. For those failures, the email is the only real path to recovery, so it needs to go out quickly.

Make sure your systems know about each failure. Stripe sends an invoice.payment_failed webhook event that you can use to trigger emails, update your CRM, or alert your customer success team.

What should the first failed payment email say?

Keep it short and helpful: the payment for a named plan did not go through, here is the amount, here is a secure link to update the card, and nothing changes yet. Avoid words like overdue, delinquent, or suspended in the first message. Most customers fix the problem quickly when the path is clear.

The subject line should be plain and specific, something like "Your payment for the Team plan did not go through." Clever subject lines can look like phishing, which is the last thing you want on a billing email.

The update link matters more than the copy. It should go straight to a secure page where the customer can update their card in a few clicks, ideally without needing to remember a password. Every extra step loses people.

Send it from a recognizable sender, such as your billing team with your company name, and make sure replies reach a human. Customers with billing questions should never hit a dead end.

How many follow-up emails should you send, and when?

A common pattern is three to four emails over about two weeks: the first right after the failure, a reminder a few days later, a clearer notice about upcoming service changes, and a final notice before suspension. Align the timing with your retry schedule so customers are never told about a problem that has already been fixed.

Each follow-up should be slightly more direct about consequences, but never hostile. The second email can mention that you will keep trying the card. The third can say clearly what will happen and when if the payment is not updated. The last should give a specific date.

Stop the sequence immediately when the payment succeeds. Nothing annoys a customer more than a final warning arriving after they already fixed their card. That means your email tool must listen for the successful payment event, not just run on a fixed schedule.

For high-value accounts, add a human step. A short personal note or call from the account owner after the second failed attempt often works better than any automated message.

Who should receive the failed payment emails in a B2B account?

Send them to the billing contact on file, and copy or notify the account owner or admin in the product. Many B2B payment failures go unresolved because the only person notified is a finance contact who left or never checks that inbox. Reaching two people doubles the chance someone acts.

Collect a billing contact separately from the admin during signup or onboarding. Many B2B buyers prefer invoices and payment notices to go to a shared finance address, and they will appreciate the option.

Show an in-app banner to admins as well. A short, polite notice in the product reaches the people who use it every day and care about not losing access.

Log each failure and recovery in your CRM, so account managers see billing problems alongside everything else they know about the account. This is the kind of lifecycle signal I map in what each stage of a B2B SaaS lifecycle email program does.

What should happen if the payment is never recovered?

Follow the policy you have set and communicated: pause, downgrade, or cancel the subscription after the final notice. Stripe's documentation lists options such as canceling the subscription, marking it unpaid, leaving it past due, or pausing it when retries are exhausted. Whatever you choose, make it easy for the customer to come back.

Pausing or downgrading is often kinder than canceling outright, because it preserves the customer's data and setup. A customer who returns a week later to find everything still there is far more likely to stay.

Send a clear final message when the change happens, explaining what changed and exactly how to restore access. Then treat these accounts as a win-back segment, not a lost cause. My guide to running a win-back campaign for churned B2B customers covers how to approach them later.

Some of these customers will also have wanted to cancel anyway. If they reply saying so, handle it like any cancellation and learn from it. My piece on what a SaaS cancellation page should say covers that conversation.

What are the most common mistakes in failed payment emails?

The most common mistakes are threatening language in the first message, a no-reply sender, a payment link that requires logging in, emails that keep arriving after the payment succeeds, and sending only to a billing contact who never sees them. Each one turns a fixable card problem into avoidable churn.

Another mistake is silence. Some companies rely only on automatic retries and send nothing. When the retries run out, the account cancels and the customer is surprised. A surprised customer is much less likely to come back.

Finally, avoid generic copy that could come from any company. Name the plan, the amount, and your product clearly, so the customer recognizes the email instantly and trusts it.

What should you do next?

Check your billing system's retry settings and confirm they are switched on. Then review your failed payment emails: make the first one calm and short, add a direct update link, set up follow-ups that stop when the payment succeeds, and send them to both the billing contact and an admin.

Recovering failed payments is one of the least glamorous retention projects, and one of the most reliable. The customers you save never wanted to leave in the first place.

If you want help building the billing alerts, CRM updates, and email flows behind payment recovery, reach out at pravinkumar.co. Let's chat.