Dunning Email Examples: Templates That Actually Recover Failed Payments
Most dunning email advice gives you one generic template and calls it done. That's wrong. Here's what actually works — and the reasoning behind every word.
Executive Summary (TL;DR)
- •The failure type (soft decline, expired card, SCA) should dictate the email — one template doesn't fit all.
- •Tone matters more than most founders expect: empathetic and personal outperforms formal and transactional every time.
- •The single most important element: a direct link to fix the problem — not to your settings page, your dashboard, or a support form.
- •Speed is a competitive advantage: emails sent within 1 hour of failure convert significantly better than those sent 24+ hours later.
What Makes a Dunning Email Work?
Before we get to examples, let's establish what separates a high-converting dunning email from the generic billing noise that gets ignored. There are six principles. Every example in this article is built around them.
Subject line
Should be informative, not alarming. “Quick heads up about your subscription” outperforms “URGENT: Your payment failed” because panic triggers avoidance, not action.
Opening line
Use the customer's first name. Start with what happened — not a corporate “We hope this email finds you well.” They need context in 5 seconds or they're gone.
Value reminder
Mention what they stand to lose access to. Not as a threat — as a helpful reminder of why fixing this matters. “To keep your access to [feature]” works.
Direct CTA
One link. It should go directly to where they can fix the problem — the Stripe billing portal, not your dashboard. Every extra click is a conversion killer.
Tone
Warm, personal, blame-free. The customer probably doesn't know the charge failed. Start from that assumption. “Looks like” is better than “Your payment has failed.”
Timing
Within 1 hour of the failure. Customer's access is still active, the issue is fresh, and they haven't rationalized the churn yet. Recovery rates drop hard after 24 hours.
Every example below is annotated against these six principles. The WHY is more valuable than the template itself — because your situation is different, but the psychology doesn't change.
Dunning Email Example #1: Soft Decline (Insufficient Funds / Temporary Block)
Soft declines are the most common failure type. The card is valid. The customer hasn't left. Their bank just blocked the charge temporarily — maybe insufficient funds at billing time, maybe a suspicious activity flag, maybe a daily limit.
The customer has a 50–70% chance of recovery if you act quickly. The strategy: inform without alarming, and let them know you'll retry automatically so they don't need to panic.
email — soft decline
Soft DeclineWhy this works — line by line
Subject line
“Quick heads up” signals this is informational, not a crisis. Curiosity without alarm. The customer opens to understand, not to defend themselves. Compare to “Payment failed for [Product]” — same information, but now it reads like a failure notification that triggers dread.
Opening: “Looks like” + blame deflection
“Looks like” is softer and more accurate than “Your payment failed.” You're not accusing them of anything — you're reporting an observation. The phrase “not anything you did wrong” does critical psychological work: it eliminates shame before it can form, making the customer more likely to take action rather than avoid the email.
Value reminder + access statement
“Your account is still active” prevents the panic spiral. Many customers assume the worst — that they've already been cut off. Reassuring them immediately keeps the email collaborative rather than adversarial. Then “To keep access to [key feature]” reminds them what's at stake without threatening them.
The automatic retry escape hatch
For soft declines, Stripe will retry automatically. Telling the customer this removes the urgency pressure — they don't have to do anything right now if their bank resolves it. Counterintuitively, removing pressure increases conversion: customers who feel trusted are more likely to update their card proactively.
Dunning Email Example #2: Hard Decline (Expired Card)
Hard declines are permanent. The card is gone — expired, replaced, canceled. Stripe won't retry successfully no matter how many times it tries. You need the customer to add a new card. That's the only path to recovery.
Recovery rate is 30–45% — lower than soft declines because it requires action. The email needs to make that action as frictionless as possible, and it needs to communicate the deadline without sounding like a collections department.
email — hard decline / expired card
Hard DeclineWhy this works — line by line
Subject: “needs an update” not “has expired”
“Needs an update” frames this as a routine maintenance task — something the reader can handle — rather than a failure state that happened to them. “Expired” in the subject can feel like an accusation. “Update” implies agency and ease.
Opening: normalizing the problem
“Banks do this pretty regularly, usually without much warning” is doing heavy lifting here. It's true, and saying it out loud makes the customer feel less embarrassed. Most people with an expired card didn't notice it expired — this gives them an out and removes the shame barrier.
CTA: “about 30 seconds”
Friction estimation matters. Saying “30 seconds” anchors the perceived effort low before they click. It's accurate — updating a card in Stripe's billing portal really does take under a minute. Customers who think a task is easy are far more likely to start it immediately.
Deadline + human fallback
The deadline (“until [date]”) is essential for hard declines — unlike soft declines, these won't resolve themselves. State it plainly without making it feel like a threat. Then immediately follow it with the human fallback: “I'm real and I'll see this.” This disarms the “corporate billing system” perception that makes people tune out.
Dunning Email Example #3: SCA / 3D Secure Failure
SCA failures are the most mishandled failure type in bootstrapped SaaS. Most tools either ignore them or send the same generic “payment failed” email. That doesn't work — the customer can't just “update their card.” They need to complete an authentication challenge.
The good news: recovery is high if you handle it correctly. The customer's card is fine, their intent to pay is there — they just need to complete one extra step that their bank requires.
email — SCA / 3D Secure failure
SCA / 3DSWhy this works — line by line
Subject: “One quick step”
Sets expectations precisely. It's one step, it's quick, the word “keep” implies their access is still active and this is maintenance — not a crisis. The customer opens with a clear mental model of what's required before they even read the body.
Naming the technical thing in plain language
Most customers have no idea what “3D Secure” or “authentication required” means, but they've seen 3DS challenges before on banking apps. Calling it “a security thing on their end” is accurate and non-threatening. The parenthetical “(called 3D Secure)” acknowledges the technical name without making the email feel like a documentation page.
The “10 seconds” anchor + future reassurance
Like the “30 seconds” in the expired card email, a time anchor removes the perceived friction barrier. Then: “Your card stays on file and future renewals will go through automatically.” This addresses the unstated fear: “Will I have to do this every month?” Resolving that concern makes the click feel like a final resolution, not a temporary fix.
Want copy-paste ready versions?
The email generator tool has the same templates formatted for immediate use — including the payment update link placeholder and subject line variants. This article goes deep on the why; the tool is for when you just need to ship.
The Worst Dunning Email You Can Send (And Why Most Tools Send It)
Before we get to timing and subject lines, let's look at what not to do. This is essentially what Stripe's default failed payment notification looks like. Most SaaS billing tools send something similar.
bad example — do not use
Avoid thisWhat's wrong with this email
No failure type context
The email doesn't tell the customer WHY the payment failed. Did their card expire? Did they run out of funds? Did the bank block it? Without context, customers can't take the right action — and many won't take any.
“Dear Customer” — instant trust destroyer
You have their first name in Stripe. Using “Dear Customer” signals you don't care enough to personalize — and if you don't care, why should they? It immediately sets a transactional, adversarial tone.
Closing threat with no human
“Your subscription will be cancelled” as the final note leaves the customer with anxiety, not direction. And signing off as “The [Product] Team” makes it clear this is automated — there's no one to reply to. A human signature and a reply invitation consistently increases response and recovery rates.
Email Timing: When to Send Each Dunning Email
Timing is the second most important variable after content. Here's the framework — and the reasoning behind each timing decision.
Email 1: Immediately on failure (within 1 hour)
The most important email. Customer's access is still active. They haven't rationalized the churn. Match the email to the failure type. For SCA failures, this is critical — your verification link has a limited validity window.
Email 2: Day 3 follow-up (roadmap for Dunning Lite)
A gentler second touch for customers who missed the first email. Shorter, more direct. Reference the first email. For hard declines, this is the “just in case you missed it” send.
Email 3: Day 7 — the final notice (roadmap)
Communicate the cancellation deadline clearly. Not a threat — a service update. “Access pauses on [date]” is factual and respectful. Include the update link prominently. This is the last chance before delinquent churn.
Subscription cancels
After this, recovery requires a full win-back campaign. Much harder. Don't let it get here.
Where Dunning Lite is today
Currently, Dunning Lite sends Email 1 — the immediate recovery email on failure. The Day 3 and Day 7 follow-up sequence is on the roadmap. Even with a single well-timed email, the recovery improvement over silence is significant. That's where most bootstrapped SaaS are starting from.
Subject Lines That Get Opens (Not Panic)
Your subject line determines whether the email gets opened. And for a dunning email, an unopened email is a lost customer. Here's the principle: be informative, not alarming. Convey what happened, hint at the easy fix, and keep it short enough to read in a notification.
✓ Do this
“Quick heads up about your [Product] subscription”
✗ Not this
“URGENT: Your payment has failed”
Calm and informational vs. panic-inducing. Open rate difference is meaningful.
✓ Do this
“Your card on file needs an update”
✗ Not this
“Your subscription is at risk of cancellation”
“Needs an update” signals a solvable task. “At risk” triggers anxiety and avoidance.
✓ Do this
“One quick step to keep your [Product] active”
✗ Not this
“Action required: Complete 3D Secure authentication”
“One quick step” sets expectations. The technical jargon in the bad version confuses most people.
✓ Do this
“Heads up: your [Product] renewal didn't go through”
✗ Not this
“Payment declined for [Product] subscription #INV-00428”
The invoice number is irrelevant to the customer — it's internal data that makes the email feel cold.
✓ Do this
“Still time to keep your access — quick note”
✗ Not this
“Final notice: Update your payment or lose access”
“Still time” is reassuring. “Final notice” feels like collections and triggers defensive avoidance.
Automate Your Dunning Emails with Dunning Lite
Writing good dunning emails is one thing. Getting them delivered within minutes of a failure, matched to the right failure type, with the right payment update link, consistently, every time — that's the automation problem.
Dunning Lite connects to your Stripe account and handles this automatically. When Stripe fires an invoice.payment_failed webhook, Dunning Lite classifies the failure and sends an AI-crafted recovery email with a humanized tone — matching the failure type — within minutes.
< 5 min
to connect your Stripe account
< 1 hr
from failure to customer email sent
$29/mo
flat rate — no commission
A note on “AI-crafted”
The emails Dunning Lite sends are AI-crafted with a humanized tone — personalized by failure type, using the customer's name and your product name. They're designed to feel like they came from a founder, not a billing system. We don't claim they're “human-written” — we claim they're written to sound like a human who cares, which is what actually converts.
Frequently Asked Questions
How is a dunning email different from a regular transactional email?
A transactional email (receipt, password reset, welcome) is informational — no specific action needed. A dunning email has one job: get the customer to take a specific action before their subscription cancels. That changes the tone, the structure, the urgency calibration, and the CTA. Most transactional email frameworks handle dunning poorly because they're optimized for information delivery, not conversion.
Should I send dunning emails from my own domain or a billing tool?
From your own domain, signed with your name. The moment the customer sees “billing@[tool].com” in the from address, the email is de-personalized. Your recovery rate drops because the relationship context disappears. Dunning Lite sends from your configured sender — the email appears to come from you.
How many dunning emails should I send before canceling?
The research suggests 3 emails over 7–14 days hits the right balance between thoroughness and customer experience. After 3 emails with no response, most of the recoverable customers have recovered. The remaining ones either genuinely want to cancel or have moved on — sending more emails degrades your sender reputation and annoys customers who've already decided to leave.
What's the difference between these templates and the ones on the email generator tool?
The email generator is optimized for practical use — copy, customize, deploy. This article goes deeper into the reasoning behind each element, the psychology of what converts, and what not to do. Use both: understand the why here, grab the templates there.
Do dunning emails affect deliverability?
Yes — but not in the way most founders worry about. Dunning emails sent to valid customers with genuine relationships rarely trigger spam filters. The bigger risk is sending too many emails (aggressive cadences), or using templates that look like phishing attempts (urgent language, generic sender names). The tone examples in this article are specifically calibrated to avoid spam triggers while maintaining real urgency.
See these emails in action
Dunning Lite sends recovery emails matched to the failure type — automatically, within minutes of the charge failing. $29/month flat, no commission, Early Access open now.