Dunning email templates that recover Stripe payments
Published 2026-04-29 · 11-minute read
Dunning email copy can be one of the highest-leverage things a SaaS founder writes and one of the most common things they outsource to a generic template. The templates below come from PayDam's built-in playbooks - the same ones we ship to customers running branded recovery on top of Stripe Smart Retries.
You can copy-paste them as a starting point, swap the merge tags for your own format, and run them through whatever email service you use. Or, if you'd rather not assemble the plumbing, see PayDam's pricing - the same 12 archetypes ship as ready-to-use playbooks on the Pro and Scale tiers.
We'll cover three things: what makes a dunning email work, the 12 voice archetypes and when each fits, and three worked examples in full showing the escalation pattern across a 5–7-day sequence.
The five parts of a dunning email that work
Strong dunning emails - regardless of voice - usually share the same five parts. If you're writing your own, this is the structural checklist:
- The subject line. Mentions the specific subscription or amount, and signals what action is needed. Generic "Action required" lines often give the customer too little context.
- The opening sentence. States exactly what failed (subscription name + amount) without burying the lede in pleasantries.
- The reassurance or context. A single line that normalizes the situation and lowers anxiety. Blame-free language usually reads better than accusatory language.
- The action step. One clear button and one secure URL. The button text matters: "Update payment method" is clearer and more action-specific than "Click here."
- The escape hatch. A reply-to instruction or "ignore this if you've already updated" line. Removes the anxiety of double-fixing or being wrongly billed.
Templates that skip any of these tend to fail in predictable ways: subjects that don't get opened, bodies that bury the action, buttons that nobody clicks because the language is corporate.
The 12 voice archetypes
Here's the catalog at a glance. Pick the one that matches your customer relationship, not just your product category - a meditation app aimed at busy executives might use Professional Notification, while a B2B accounting tool with a strong founder presence might use Personal from Founder.
| Archetype | Voice | Best for |
|---|---|---|
| Friendly Heads-Up | Indie / consumer SaaS, blame-free, contractions OK | Default for most consumer subscriptions |
| Professional Notification | Neutral B2B, no contractions, AP-inbox-safe subjects | Mature B2B brands; safe default if unsure |
| Personal from Founder | First-person from a named human, signed by the founder | Indie SaaS, small teams, high-trust relationships |
| Empathetic Service | Soft-touch, "no stress, we've got you" | Wellness, coaching, communities, relationship-led brands |
| Member Access | "Your membership" rather than "your subscription" | Clubs, communities, loyalty programs, content memberships |
| Usage-Based (Product-Led) | References active usage; loss-of-ongoing-work framing | Engaged SaaS - writing, building, tracking products |
| Invoice-First (AP-Friendly) | Procedural, formal, invoice number in every subject | B2B with AP-team forwarding; CFO-safe |
| Concierge / White-Glove | Premium, direct-to-human, reply-back encouraged | High-touch products with real human support |
| Minimalist / Developer-Friendly | Lowercase subjects, no marketing language, no emoji | Developer-tool SaaS where plain is the point |
| Direct & Urgent | Consequence-led, escalating fast, no small talk | Late-stage dunning or high-value B2B |
| E-Commerce / Physical Goods | "Delivery payment needs attention" - shipment-anchored urgency | Subscription boxes, DTC brands, recurring physical goods |
| Hospitality / Booking | Anchors to upcoming bookings or reservations | Hotels, fitness studios, clubs, venues, coworking |
Most teams pick one as their default and switch into Direct & Urgent for the last touch in the sequence. Mixing voices mid-sequence (warm Day 0 to firm Day 7+) is normal and effective; switching back the other way (cold Day 0 to soft Day 7) reads as inconsistent.
Worked example 1 - Friendly Heads-Up
For an indie or consumer SaaS, this is the safest default. The escalation moves from a light heads-up at Day 0 to "still no luck" at Day 3 to a firmer "{{days_overdue}} days in" at Day 5, all while staying conversational.
Day 0 - first touch (within hours of failure)
Body: Hey {{customer_name}}, we tried to renew {{subscription_name}} for {{amount}} and the card on file came back declined. It could be an expired card, a bank decline, or a billing-address mismatch.
Use the secure update page to help resolve it: [Update payment method]
If you've already updated things on your end, you can ignore this - we'll catch the next charge.
Day 3 - second touch
Body: We tried again on {{subscription_name}} and it didn't go through. Same story or a new one - either way, easiest fix is an updated payment method on file.
Quick fix through the secure update page: [Try again]
Reply if anything looks off - a real person reads these.
Day 5 - third touch (slightly firmer)
Body: Five days on and we still haven't been able to renew {{subscription_name}}. We're going to keep trying for a bit, and the account terms may apply if the card stays declined.
Update the payment method here: [Update payment method]
If something has changed and you'd rather pause or cancel, just reply - easier for both of us.
Notice the structure: the failure facts stay constant, the urgency notch goes up by one each touch, and the "ignore if you've fixed it / reply if something is wrong" escape hatch never goes away. That last line is what keeps the sequence from feeling automated.
Worked example 2 - Personal from Founder
For indie SaaS where the founder's name is public, this voice can feel more trustworthy than anonymous branded copy. The trick is owning the awkward moment instead of papering over it with corporate language.
Day 0 - first touch
Body: Hi {{customer_name}}, it's {{founder_first_name}} from {{company_name}}. Wanted to write directly because our system flagged your card as declined when we tried to charge {{amount}} for {{subscription_name}}.
Quick fix through the secure update page: [Update payment method]
If anything looks off, just reply - a real person will read it.
- {{founder_first_name}}
Day 3 - second touch
Body: Three days on and the card on file for {{subscription_name}} still isn't going through. I don't want to be a billing nag, but I also don't want you to lose access without seeing this.
Secure update page, in case it helps: [Sort it now →]
If something on our side is wrong, please tell me. I read all the replies.
The key is that this voice can only be deployed when the founder actually does read the replies. If support is fully outsourced or if the founder is too busy to respond within a day, this archetype overcommits and damages the relationship faster than a generic template would.
Worked example 3 - Direct & Urgent (late-stage)
For the last 1–2 touches in a sequence, or for high-value B2B accounts where the warm tone reads as soft, this voice carries the urgency without slipping into rude. Reserve it for where it earns its place - using it from Day 0 reads as threatening.
Day 0 - first touch (firmer than Friendly, still professional)
Body: The payment of {{amount}} for {{subscription_name}} has failed.
Update your payment method today to keep service uninterrupted: [Resolve now →]
Failure to resolve may result in account handling changes in line with our terms.
Day 3 - second attempt
Body: Our second attempt to collect {{amount}} for {{subscription_name}} has failed.
Update your billing details before the next scheduled attempt: [Update billing →]
Service continues at your risk until the balance is resolved.
The vocabulary tells: "action required," "failure to resolve," "service continues at your risk." No apologies, no "happens to everyone," no escape hatch. Reserve this for situations where the customer relationship has already moved past warmth - late-stage dunning on a $5K/mo enterprise account, not Day 0 on a $19/mo consumer subscription.
Subject-line patterns worth testing
Inbox preview text is one of the easiest surfaces to test in transactional email. Patterns worth starting with and testing against your own audience:
- Specific over generic. "Quick thing - your card just got declined" tells the customer more than "Action required."
- Amount or subscription name in the subject. Customers triage by what's at stake; "5 days in - still $49 unpaid" carries more information than "Payment overdue."
- Lowercase / casual on Day 0 for consumer; capitalized / formal for B2B. The visual style sets expectations before the body is read.
- Question or curiosity on early touches; consequence on late touches. "Still no luck on that card" → "Update billing required by Friday."
- Founder names can work for first-touch on indie SaaS. "Quick follow-up from {{founder_first_name}}" feels more personal than "Quick follow-up from the team."
Anti-patterns: what NOT to write
We've seen these mistakes enough times to call them out specifically:
- "Your account is suspended." Don't say it unless it's actually true. False urgency erodes trust faster than late dunning.
- "Click here to update your payment information." Generic anchor text underperforms specific labels. Use "Update payment method" or "Sort billing."
- "Dear valued customer." Either personalize with a merge tag or skip the salutation. The default fallback reads as automated.
- Long apology paragraphs. "We're sorry to bother you with this" pads the body without helping the customer take action. Lead with what failed and what to do.
- Multiple CTAs. One button, one URL. "Update payment method OR contact support OR view invoice" splits attention and lowers click-through on every option.
- Login walls. Avoid sending the customer to a generic account login from a dunning email. Signed invoice-specific recovery pages remove a major source of friction.
- "This is your final notice." Save consequence language for when there's an actual consequence on the immediate horizon. Premature finality reads as boy-who-cried-wolf and the next touch lands flat.
Sequence cadence - how many emails, how often
Three touches is a practical minimum for many teams; six is a reasonable upper bound for a 60-day window. A common pattern to start from:
- Day 0: first touch, warm/neutral framing - most recoveries happen here
- Day 3: second touch, slightly firmer ("still no luck")
- Day 7: third touch, now mentioning impact under the account terms
- Day 14: fourth touch, switch to firm voice if you've been warm
- Day 28: final touch before cancellation, consequence-led
Anything more frequent than every three days reads as harassment. Anything less frequent than every two weeks leaves customers thinking the issue resolved itself.
For longer windows (60–90 days, common on Pro and Scale tiers), insert one or two more touches at Day 21 and Day 42 with new subject angles - pre-cancellation warning, then last-chance.
Related reading: The complete guide to Stripe payment recovery · PayDam vs Stripe Smart Retries · What is Stripe dunning? · How PayDam works