A dunning email is the automated message you send when a subscription payment fails, asking the customer to update their card. Below are 12 dunning email examples you can copy — a full recovery sequence, templates by decline reason, and special cases — plus the anatomy of one that actually recovers revenue, and the subject lines that get opened.
Recovery emails are where most failed-payment revenue is actually won back. Automatic card retries catch the charges that will clear on their own; the emails recover the rest — but only if they are written well. A generic "your payment failed" blast underperforms badly. A short, personal, decline-reason-specific sequence, sent at the right time, can recover a large share of what would otherwise be lost. Here is exactly how to write them, with templates you can paste in today.
Key takeaways
- Use a 4–5 email sequence over ~3 weeks (Day 1, 3, 7, 14, 21) — the first two recover most of the revenue.
- Personalize by decline reason: an expired card, insufficient funds, and an SCA prompt each need a different message.
- Every email needs one calm subject, the exact reason, one obvious button, reassurance, and a one-click unsubscribe.
- Send at a human hour in the customer's timezone — not whenever the charge happened to fail.
The anatomy of a dunning email that recovers
Before the templates, it helps to see the shape. Almost every high-performing recovery email has the same six parts — miss one and conversion drops:
- A calm, honest subject line. No ALL CAPS, no fake alarm. "A quick heads-up about your payment" beats "URGENT: ACTION REQUIRED."
- A personal greeting. Use the first name and write as a person, not a billing system.
- The exact reason. If you know it failed because the card expired, say so — it tells the customer precisely what to fix.
- One obvious button. A single "update your card" call to action. Competing links kill conversion.
- Reassurance and a gentle deadline. Tell them their account is safe for now, and (later in the sequence) when it will not be.
- A one-click unsubscribe. Non-negotiable for deliverability — and it keeps you out of the spam folder.
The core recovery sequence (5 templates)
This is the backbone: five emails over three weeks that escalate gently from a friendly heads-up to a respectful final notice. Send them alongside automatic retries. Replace anything in [brackets] with your own details.
Hi [First name],
Just a quick note — we tried to process your latest [Product] payment of [amount] today and it didn’t go through. No stress, this happens all the time and it’s usually a 30-second fix.
You can update your card here: [update link]
Your account is fully active in the meantime. Thanks for being a customer!
— [Your name], [Product]
Hi [First name],
We tried your card again and it still isn’t going through. To keep your [Product] account running without interruption, could you update your payment details?
Update in one click: [update link]
If you’ve already updated it, you can ignore this — thank you!
Hi [First name],
Your [Product] payment is still outstanding, and we’d hate for you to lose access to [key benefit] over a card issue.
It takes less than a minute to fix: [update link]
Any questions, just reply to this email — a real person will help.
Hi [First name],
We still haven’t been able to process your payment, so your [Product] account is scheduled to pause on [date] unless the card is updated.
Keep everything running: [update link]
We’d genuinely like to keep you — if something’s changed or you’re unsure, just reply and we’ll sort it out together.
Hi [First name],
This is the last reminder — after several attempts we still can’t process your payment, so your [Product] subscription will be cancelled on [date].
You can still keep it active by updating your card now: [update link]
If this is goodbye, thank you for being a customer. You’re always welcome back, and your data will be here if you return.
Templates by decline reason (4 templates)
The single biggest upgrade over a generic sequence is matching the message to why the card failed. A hard decline like an expired card needs a different ask than a soft decline like insufficient funds. These four cover the most common reasons.
Hi [First name],
The card we have on file for [Product] has expired, so your latest payment couldn’t go through. Adding a current card takes about 30 seconds:
[update link]
That’s all it takes to keep everything running — thanks!
Hi [First name],
Your recent payment didn’t clear — often that’s just a timing thing with available funds. We’ll automatically try again in a couple of days, so you may not need to do anything.
Prefer to use a different card? You can switch here anytime: [update link]
Hi [First name],
Your bank declined the latest charge for [Product]. This is usually a quick fix — either your bank needs to approve the payment, or a different card will work.
Update or switch cards here: [update link]
If it keeps happening, a quick call to your bank usually clears it.
Hi [First name],
Your bank needs you to confirm this payment for security — a common step for customers in Europe. It only takes a moment:
[authentication link]
Once you approve it, you’re all set. Thanks for verifying!
Special-situation templates (3 templates)
Three more that catch revenue the core sequence misses — before a failure, long after one, and at the trial-to-paid moment.
Hi [First name],
A small heads-up — the card on file for [Product] expires on [expiry], which is before your next payment on [date]. Updating it now means no interruption:
[update link]
Thanks for staying ahead of it!
Hi [First name],
A while ago your [Product] subscription ended because a payment didn’t go through — and we never want a card glitch to be the reason someone leaves.
If you’d like to pick up where you left off, you can reactivate in one click: [reactivate link]
No pressure at all — just wanted you to know the door’s open (and your data is still here).
Hi [First name],
Your free trial of [Product] ends on [date]. To keep your account and everything you’ve set up, add a payment method before then:
[add card link]
Not ready? No worries — reply and tell us what’s holding you back, and we’ll help.
Which email in the sequence recovers the most?
Recoveries are heavily front-loaded. The first two emails typically do most of the work, which is why getting Day 1 right matters more than adding a sixth or seventh message:
15 dunning email subject lines that get opened
The email cannot recover anything if it is not opened. These subject lines are calm, specific, and curiosity-free-of-alarm — swap in your product name:
- A quick heads-up about your [Product] payment
- We couldn't process your last payment
- Your card on file needs a quick update
- Small issue with your [Product] subscription
- Don't lose access to [Product]
- Your card on file has expired
- We'll try your payment again in a couple of days
- One quick step to confirm your payment
- Action needed: your account will pause soon
- Your [Product] payment is still outstanding
- Final notice: [Product] access ends [date]
- Heads-up: your card expires before your next payment
- Keep your [Product] account running
- A 30-second fix for your [Product] account
- We'd love to keep you at [Product]
Dunning email best practices (and mistakes to avoid)
- Do send from a real person's name and a monitored reply-to address.
- Do keep each email short — one idea, one button.
- Do send at a human hour in the customer's local timezone.
- Don't use fake urgency or countdown timers that aren't real.
- Don't send the same generic email five times — personalize by reason and by position in the sequence.
- Don't keep emailing addresses that bounce or complain; suppress them or you'll wreck your sender reputation.
Write these yourself, or automate them?
These templates will get you a long way. The question is whether maintaining the whole system by hand is a good use of your time.
✓ Pros
- +Templates are free and you can send them from tools you already have.
- +Full control over voice and content.
- +Fine for low volumes where you can watch each failure by hand.
✕ Cons
- –Personalizing per decline reason, per sequence position, in each timezone is a lot of manual setup.
- –You still need retries, SCA handling, suppression and deliverability management around the emails.
- –Nothing here recovers the failures that already happened before you set it up.
A tool closes that gap. Revova writes a unique AI email per decline reason, sends it at the right local time, runs the retries and pre-dunning around it, and its Lost Revenue Finder recovers past failures too — flat $29–$79/month, no commission. For the wider setup, see our guide on how to recover failed Stripe payments and our comparison of the best payment recovery tools.
Frequently asked questions
What is a dunning email?
A dunning email is an automated message sent to a customer when their subscription payment fails, asking them to update their payment method so their service continues. Good dunning emails are personalized to the specific decline reason, sent on a timed sequence, and include a single one-click link to fix the card.
How many dunning emails should I send?
Most effective sequences use four to five emails over about three weeks — commonly Day 1, 3, 7, 14 and 21. The first two recover the majority; the later ones add urgency and a final notice before the subscription is cancelled. Sending more than that rarely helps and risks annoying customers.
What should a dunning email say?
Lead with a calm, honest heads-up that a payment did not go through, state the specific reason if you know it, and give one obvious button to update the card. Keep it short, write it as if it came from a person, reassure the customer their account is safe for now, and always include a one-click unsubscribe.
When is the best time to send dunning emails?
Send at a human hour in the customer’s own timezone — around 8:30am local tends to perform well — rather than whenever the charge happened to fail. Space the sequence over days so retries can hit a payday, and avoid late-night sends that feel automated.
Do dunning emails actually work?
Yes. Personalized, well-timed dunning emails on top of automatic card retries can recover a large share of failed payments — pushing total recovered revenue into the 40–60% range for many businesses. Generic "your payment failed" templates underperform badly, which is why personalization matters.
Should I write dunning emails myself or automate them?
You can start with templates like the ones below, but maintaining per-reason personalization, correct timing, timezone sends, deliverability and suppression by hand is a lot of ongoing work. A tool like Revova writes a unique email per decline reason automatically and sends it at the right time, so you set it up once.
Let AI write and send these for you
Revova turns this whole playbook into an automatic system — a unique recovery email per decline reason, sent at the perfect local time, with retries and pre-dunning built in. Start free and see what you've already lost.
Start my 14-day free trial →No credit card · Free Lost Revenue scan · 30-day money-back guarantee
