Dunning Email Templates: A 5-Email Sequence

A failed payment email has one job: get a good customer to fix a payment problem before it quietly becomes a cancellation. Most subscribers who hit a failed payment never decided to leave — their card expired, their bank hiccuped, or the money was not in the account that day. The five templates below are a complete sequence you can copy, adapt to your brand, and run: a failure notice on day 0, a reminder on day 3, a card-update push on day 7, a consequence warning on day 11, and a final notice on day 15. Variables are in [BRACKETS]. The tone throughout is firm and human — clear about what happened and what happens next, with no threats and no manufactured urgency.

These templates assume retries are running behind the emails. While the sequence works the customer, your retry logic should be working the card — spaced, decline-code-aware attempts, never a retry on a hard decline. For the strategy behind the wording, see dunning emails that work; this page is the copy itself.

Before you copy: four rules the templates follow

• One ask per email. Every message asks for exactly one thing — update the card — and links straight to it. No surveys, no upsells, no "while you're here."
• The consequence is stated once, plainly, and only when it is real. Access pauses when the sequence ends because that is the actual policy. Nothing in these emails bluffs.
• Retries are mentioned honestly. When the system will try the card again, the email says so. Customers who know a retry is coming often simply leave the card alone and let it succeed.
• Every email works without the ones before it. Most readers open one message in the sequence, not five. Each template restates what failed, what to do, and by when.

Email 1 — Day 0: the failure notice

Subject: Your [PRODUCT] payment didn't go through

Hi [FIRST_NAME],

We tried to charge your [CARD_BRAND] ending in [CARD_LAST4] for your [PLAN_NAME] subscription ([AMOUNT]), and the payment didn't go through. This happens all the time — cards expire, banks flag routine charges, accounts run low before payday — and it doesn't affect your access right now.

We'll try the same card again over the next few days. If you've already replaced this card, or you'd rather use a different one, you can update your payment details here: [CARD_UPDATE_LINK]

That's all you need to do. If the retry succeeds, you'll never hear about this again.

— The [BRAND] team

Why it works: it lands while the customer still remembers subscribing, normalizes the failure instead of shaming it, and gives two paths — do nothing and let the retry work, or update the card now.

Email 2 — Day 3: the reminder

Subject: Still unable to process your [PRODUCT] payment

Hi [FIRST_NAME],

A quick follow-up: we still haven't been able to process your [PLAN_NAME] payment of [AMOUNT] on the card ending in [CARD_LAST4]. Your access is still fully active.

If the card on file is the one you want to use, no action is needed — we'll keep trying it. If that card has been replaced or you'd prefer a different one, updating it takes about a minute: [CARD_UPDATE_LINK]

If something else is going on — a billing question, a problem with the service — just reply to this email and a person will read it.

— The [BRAND] team

Why it works: it assumes a benign cause, repeats the single ask without repeating the pressure, and opens a reply path — some "failed payments" are actually support problems wearing a billing costume.

Email 3 — Day 7: the card-update push

Subject: Please update your card to keep [PRODUCT] active

Hi [FIRST_NAME],

We've tried your card ending in [CARD_LAST4] several times over the past week, and it still isn't going through. At this point, another automatic retry on the same card is unlikely to fix it — the most common reasons are a card that's been replaced, a new expiration date, or a block your bank can lift.

Updating your payment details takes about a minute, and your [PLAN_NAME] subscription continues without interruption: [CARD_UPDATE_LINK]

If you'd rather talk to your bank first, that works too — ask them about the declined charges from [BRAND], then update or confirm your card using the link above.

— The [BRAND] team

Why it works: day 7 is where the sequence stops pretending a retry will save it and says so honestly. Naming the likely causes gives the customer a concrete next step instead of a vague problem, and the link is the whole point of the email — subject-line tactics for this push are covered in our dunning email subject lines reference.

Email 4 — Day 11: the consequence warning

Subject: Your [PRODUCT] access pauses in [DAYS_LEFT] days unless your card is updated

Hi [FIRST_NAME],

This is a heads-up, not a surprise bill: your [PLAN_NAME] payment of [AMOUNT] is still outstanding, and if we can't collect it by [END_DATE], your access to [PRODUCT] will pause and your subscription will be cancelled.

Everything you've built in [PRODUCT] — [SAVED_WORK_EXAMPLE, e.g. "your projects, history, and settings"] — is tied to this account, and we'd rather keep it running than close it.

Updating your card takes about a minute: [CARD_UPDATE_LINK]

If you meant to cancel, you don't need to do anything — the subscription will end on [END_DATE] on its own, and there are no further charges.

— The [BRAND] team

Why it works: the consequence is specific, dated, and real, and the email respects both readings of the customer's silence — "I forgot" gets a clear rescue path, and "I meant to leave" gets a clean, charge-free exit. That second sentence does more for trust than any urgency line.

Email 5 — Day 15: the final notice

Subject: Final notice: your [PRODUCT] subscription ends today

Hi [FIRST_NAME],

Today is the last day of the payment window for your [PLAN_NAME] subscription. We haven't been able to collect [AMOUNT] on the card ending in [CARD_LAST4], so your access will pause today and the subscription will be cancelled.

One update before then keeps everything exactly as it is — no re-setup, no lost history: [CARD_UPDATE_LINK]

If today isn't the right time, that's understood. Your account details are on file, and restarting later starts from this same account — just reply to this email or update your card whenever you're ready.

Thanks for being a customer either way.

— The [BRAND] team

Why it works: it does exactly what it says, on the day it says, and then leaves the door open without a fake extension. Customers who churn here churn honestly — and a clean final notice is what makes a later winback conversation possible.

Running this sequence with Swipe Again

Swipe Again sends branded versions of exactly these five emails — your name, your colors, your card-update page — as part of its recovery sequence for subscription businesses. The emails are coordinated with decline-code-aware smart retries (up to 6 attempts over ~16 days, hard declines never retried) and SMS in the same sequence; our guide to dunning SMS covers when a text adds something email cannot. Cancel deflection — Discount, Pause, and Service offers — is included when a customer moves to cancel. It is $179/mo flat, no percentage of recovered revenue and no MRR tiers, with a 14-day trial, card upfront, and connection in about 2 minutes across Stripe, Recharge, Seal Subscriptions, Skio, Loop Subscriptions, Chargebee, Recurly, Braintree, and Paddle. The guarantee, verbatim: "Recover $179 in 30 days, guaranteed — or Swipe Again is free the next 30 days."

One benchmark for judging any sequence, including this one: in Churnkey's analysis of Stripe data, each additional dunning email touch adds roughly 1–2 points of recovery. Five considered touches are not five times the pressure — they are five separate chances for the one open that actually happens.

The bottom line

Copy the five templates, replace the brackets, and check three things before you send: every link goes to a card-update page that works on a phone, every date in the copy matches your real grace policy, and no sentence threatens something that will not actually happen. A sequence you can run honestly, on schedule, beats a cleverer one you cannot.

Frequently asked questions

How many dunning emails should you send for a failed payment?

Five is a workable full sequence: a notice on the day of failure, a reminder, a card-update push, a dated consequence warning, and a final notice at the end of the grace window. In Churnkey's analysis of Stripe data, each additional email touch adds roughly 1 to 2 points of recovery, so the later emails earn their place — provided each one restates the problem and the fix on its own.

What should a dunning email never say?

It should never threaten a consequence that will not happen, invent a deadline, or imply charges that are not real. Fake urgency trains customers to ignore the sequence and creates chargebacks and complaints when the bluff is called. State the actual policy once, plainly, and keep the exit as clean as the rescue path.

When should the card-update link appear in the sequence?

In every email, from day 0. Some failures are hard declines — an expired or replaced card — that no retry can fix, and those customers need the link immediately, not after a week of retries. The emphasis changes across the sequence, from optional in the early emails to the central ask by day 7, but the link never waits.

Should dunning emails come from the brand or a billing address?

From the brand the customer bought from, with a name and reply path they recognize. A payment problem is a trust moment: an email that looks like it came from an unknown billing service gets deleted or reported, while a branded email with a working reply address gets the card update — or a support conversation that saves the account another way.

Can I use these templates if my grace period is shorter than 15 days?

Yes — compress the dates, not the structure. Keep the order: notice, reminder, card-update push, dated warning, final notice. What matters is that the warning always precedes the end date by enough days for the customer to act, and that the final notice goes out on the day the policy actually takes effect.