1. Blog
  2. Payment recovery

Dunning email templates for failed SaaS payments

Four copy-paste dunning emails for Stripe subscriptions: the first failed payment, the reminder, the final notice and the expiring card.

Payment recovery

The short version

A good dunning sequence is four short emails: one the day a payment fails, a reminder a few days later, a final notice before the subscription ends, and a warning before a card expires. Each one says what happened in a sentence, carries one link to update the card, and never threatens.

When a renewal charge fails, most customers haven’t decided to leave. Their card expired, their bank flagged the charge, or the account was short that week. The email you send next decides whether they fix it or drift away without noticing.

Below are four templates you can paste into your billing tool and adjust. Words in curly braces are placeholders: swap them for your own merge fields. The timings match a common default of day 0, 3, 7 and 10 after the failure, so change them to fit your billing cycle.

What every dunning email needs#

  • One sentence on what happened: the charge failed, for which product, and the last four digits of the card if you have them.
  • One link: straight to a page where they can update the card. No login, no “go to Settings → Billing”.
  • What happens next: their access is fine for now, and when it will stop if nothing changes.
  • A reply-to that a person reads: some customers will answer with a question instead of clicking.

Template 1: the payment just failed#

  • When: the day the charge fails.
  • Subject: Your {product} payment didn’t go through
  • Goal: tell them calmly. Most people fix it on the first email if the link works.

“Hi {first name}, we tried to charge your card ending {last4} for {product} today and your bank declined it. This happens, usually because a card expired or was replaced. You can update your card here: {update link}. Your account is working as normal while you do. Questions? Just reply to this email. {your name}”

Why it works: it explains without blaming, names the likely cause so they know what to check, and the only thing to do is click.

Template 2: the friendly reminder#

  • When: about three days after the failure, if the card still hasn’t been updated.
  • Subject: Quick reminder about your {product} card
  • Goal: catch the people who saw the first email and meant to deal with it later.

“Hi {first name}, a quick follow-up: the payment for {product} is still outstanding because the card ending {last4} was declined. It takes about a minute to fix: {update link}. If something changed and you’d rather switch plans or pause, reply and tell us. {your name}”

Why it works: it’s shorter than the first email, and it opens a door for customers whose budget changed, so a quiet failure becomes a conversation instead of a lost account.

Template 3: the final notice#

  • When: a day or two before you stop retrying and the subscription ends. With the default above, day 10.
  • Subject: Your {product} account will be paused on {date}
  • Goal: give a clear, honest deadline. This is the email that gets read.

“Hi {first name}, we still haven’t been able to collect your {product} payment. If the card isn’t updated by {date}, your subscription will end and your team will lose access to {what they’ll lose}. Your data stays safe if you come back. Update your card here: {update link}. If you meant to cancel, no action is needed. {your name}”

Why it works: a real date and a concrete loss are clearer than “urgent” in the subject line. Saying they don’t need to act if they meant to cancel keeps it honest, and it’s the email customers are least likely to resent.

Template 4: the card is about to expire#

  • When: a couple of weeks before the expiry date on the card, before any charge fails.
  • Subject: The card on your {product} account expires soon
  • Goal: turn a future failed payment into a non-event.

“Hi {first name}, the card ending {last4} that pays for {product} expires at the end of {month}. To keep things running without a hiccup, add your new card here: {update link}. Already got a replacement from your bank? It takes a minute. {your name}”

Why it works: nothing has gone wrong yet, so the tone can be light. It’s the cheapest recovery there is, because the payment never fails.

Stripe’s built-in emails or your own?#

Stripe Billing can send a failed-payment email after each failed charge and an expiring-card email a month before the card expires, using your Stripe branding settings and a link to a Stripe-hosted page where the customer updates the card. If you have nothing today, turning those on is a sensible first step.

Writing your own sequence is worth it when you want the wording, timing and sender to sound like you, when you want a reminder and a final notice with a date, or when you want replies to reach a person. Pick one source for each email, though: if Stripe and your own tool both send a failed-payment notice, the customer gets two.

For the copy itself, read why failed payments are churn nobody chose, and check how much of your churn is involuntary with the churn rate calculator.

ExitLoop sends a four-email dunning sequence for Stripe subscriptions, with editable wording and timing, a branded card-update page and expiring-card reminders. See how payment recovery works or what’s included.

Common questions

How many dunning emails should I send?

Three or four over about ten days to two weeks: one when the charge fails, a reminder, and a final notice with a date. Add an expiring-card warning before failures happen.

What should the subject line of a dunning email say?

Say what happened in plain words, like “Your {product} payment didn’t go through”. Clear beats clever, and it beats “URGENT” too.

Should a dunning email mention cancelling?

The final notice should. Saying no action is needed if they meant to cancel keeps the sequence honest and stops it reading like a threat.

  • dunning email templates
  • failed payment email
  • dunning emails
  • expiring card email
  • stripe billing
Found this useful? Pass it on.
Written byThe ExitLoop team

Building cancel flows and payment recovery for Stripe

The next customer who clicks cancel might stay

Try the customer experience first, then connect your own Stripe account.