Dunning Email Templates: 7 Failed-Payment Sequences

A dunning email asks a subscriber to update their card after a payment fails, before their account is paused. Most subscription businesses send one or two generic ones and miss most of the revenue they could recover.

From the businesses I've helped, the teams that recover the most aren't running the most aggressive retry schedules. They treat the dunning email as a customer-communication problem.

Get the sequence right and you recover most of the failed charges a one-email setup never collects.

Key takeaways

• A full 7-step sequence split by decline type targets 60%+ failed-payment recovery.
• The day-1 email holds the highest open rate, 41%, and recovery rate, 13%.
• Failed payments cost the average subscription business 9% of monthly revenue.
• Emails 1 through 3 carry most recovery, which drops to 4% by day 15.
• Retrying a hard decline triggers per-attempt card-network fees and recovers nothing.
• A card-update request after retries exhaust is the most-skipped high-leverage step.

What is a dunning email?

A dunning email is an automated message sent to a subscriber after a payment fails, prompting them to update their card and restore the subscription before it pauses. It targets involuntary churn, the subscription loss that comes from billing failures rather than a customer choosing to leave.

The email fixes a payment credential problem before the subscriber's service stops. That is why the tone of a dunning email stays informational and helpful, where a collections letter would be adversarial.

A subscriber whose card expired still wants the product, so the email's only task is to make updating the card fast.

That scope draws a hard line. Dunning recovers payments that failed on their own, the involuntary kind of churn. It never fires when a customer actively cancels, which is your cancel flow's job. Nor does it fire on a chargeback, because that is a dispute rather than a retry event.

Why most dunning sequences underperform

Most dunning sequences send one or two generic emails with no timing logic, no decline-type split, and no card-update prompt. So they recover a fraction of what a segmented sequence would.

The gap is not effort. A single email cannot match the payment event that triggered it.

The decline type decides what recovery action is even possible, and the two types call for opposite moves:

Treat both the same way and you waste money on the half you should leave alone. Retrying a hard decline raises your dispute risk for a subscriber who is already gone.

The timing matters as much as the split. Baremetrics Recover data from 2026 shows the day-of-failure email drives a 13.25% recovery rate at a 41.29% open rate, the strongest of any step. A sequence that stops at one email abandons every point of recovery after it.

One caveat on the benchmarks ahead. They come from Baremetrics Recover customers, who already run sophisticated dunning, so read them as what a strong sequence reaches, not a floor. 

A team sending one generic email today recovers less, which means the room to improve is larger than the numbers suggest.

The 7-step dunning sequence: what to send, when, and why

The 7-Step Dunning Sequence maps every recovery touchpoint from the day of failure through the post-dunning winback, with each email keyed to its decline type. Each step assumes the previous one ran and failed, so the order matters as much as the copy.

The sequence runs seven steps across two tracks:

1. Day-1 soft-decline notice opens the soft-decline track the day the charge fails.
2. Day-3 urgency nudge follows once a retry has run and failed.
3. Day-7 final warning is the last email before the account pauses.
4. Hard-decline notice replaces the soft track entirely when the card is dead.
5. Card-update request fires after soft retries exhaust without recovery.
6. Post-dunning winback lands after the window closes and the account pauses.
7. Account-updater success confirmation closes the loop on a silent recovery.

Steps 1 through 3 are the soft-decline track, where retries are still in play, and step 4 is the hard-decline track, where retries must stop. The recovery tail, steps 5 through 7, covers the handoff out of dunning whichever track the failure took.

Step 1: Day-1 soft-decline notice

Send the first email the same day the charge fails, inside the first four hours, while the subscriber is still active and unaware. This is the highest-recovering step in the sequence, so the copy stays plain and blames nothing:

• Subject line: Your payment didn't go through, here's how to fix it
• Body: A friendly opener, one line on what failed, a one-click update link, and a brief note on the access they lose if it stays unresolved.

Leave retry timing out of this email. A line like "we'll try again in 3 days" reads as a threat and gives the subscriber a reason to wait. This is the step that recovers the most, so the only job is a frictionless fix.

Step 2: Day-3 urgency nudge

Send the second email three days after the failure, once a retry attempt has run and failed, and let the tone shift to gently urgent. The subscriber has seen one notice, so this email acknowledges that and raises the stakes a notch:

• Subject line: Still having trouble? Let's fix your payment
• Body: Note that this is the second message, name the service they're at risk of losing, and repeat the update link as the single clear action.

This step recovers almost as much as the day-of-failure email. The subscriber who skipped the first notice is often the one who simply missed it, so the nudge works as a plain reminder.

Step 3: Day-7 final warning

Send the third email seven days after the failure, just before the account pauses, and let the copy earn its urgency as the last message before service stops. State plainly what happens next and when:

• Subject line: Final notice: update your payment to keep [Service Name]
• Body: A clear statement that access pauses on a specific date, with the update link as the most prominent element on the page.

This step holds its recovery rate level with the day-3 nudge. The honesty is what works. A real deadline the subscriber can act on beats vague pressure, and naming the pause date gives them a reason to click now.

Step 4: Hard-decline notice (no retry)

When the failure is a hard decline, send this email in place of the entire soft-decline track, and do not retry the charge. A hard decline means the card is dead or flagged, so retrying recovers nothing and adds risk:

• Subject line: Action required: we can't charge your card
• Body: A plain statement that the card can't be charged, no decline reason (the network prohibits sharing it), and a direct link to add a new card.

The retry ban is firm. Retrying a hard decline can break card-network rules from the first attempt and trigger per-attempt fees, covered in full in the card network rules section below. The only path forward on a hard decline is a new card, so this email asks for exactly that.

Step 5: Card-update request (account updater prompt)

Send the card-update request after soft-decline retries exhaust without recovery, typically day 7 to 10, if your platform supports account updater. This is the highest-leverage step most sequences never include:

• Subject line: We tried to update your card automatically, here's what to check
• Body: Explain that the card on file couldn't be refreshed automatically, then link to the payment-method update page.

Account updater automatically refreshes stored card credentials when a card expires or is reissued. On the cards it can't reach, this email is the manual fallback.

Most generic sequences stop after the third warning, which leaves the subscribers whose cards simply aged out unrecovered.

Step 6: Post-dunning winback

Send the winback email one to three days after the dunning window closes, once the account is paused or cancelled, and treat it as a different message. Dunning asks the customer to fix a payment problem, while winback asks them to choose to come back:

• Subject line: We had to pause your [Service Name] account
• Body: An empathetic note with no guilt, a clear reactivation link, and a pause option if your platform offers one.

That shift in intent is the whole point of the step. A subscriber who reached this stage has stopped responding to payment reminders, so a fourth "update your card" email reads as noise. 

A message that acknowledges the pause and makes returning easy gives them a reason to come back.

Step 7: Account-updater success confirmation

Send a confirmation the moment account updater refreshes the card and the retry charge succeeds, closing the loop on a recovery the subscriber never had to act on. 

Teams treat account updater as something that runs in the background, so they skip this step. Send it anyway:

• Subject line: You're all set, your payment went through
• Body: Confirm the renewal, state the next billing date, and add a one-line reminder of the value they keep.

The email costs almost nothing. It prevents support tickets from subscribers who saw a failed-charge notice from their bank and want to know their account is fine. The sequence also ends on a resolved note rather than a silent recovery the customer half-noticed.

Use the churn rate calculator to size the revenue at stake before you choose a sequence length.

Subject line and copy rules that actually move open rates

Dunning subject lines that name the specific service at risk and include a clear action verb beat vague urgency lines on open rate. The subscriber often doesn't know anything is wrong, so the subject has to tell them.

Stripe recommends naming the service and leading with an action verb. The shape it suggests is "[Action Required] - [Payment Issue] - [Business Name]." A subscriber mid-sequence is often still using the product with no idea a charge failed.

A vague subject reads as marketing. A specific one tells the subscriber something is wrong with their account.

That day-of-failure email peaks at a 41% open rate, well above the 20-30% benchmark for email. It reaches the subscriber while they're still active.

Recovery holds through the first week, then drops sharply, so most of the money sits in the first three emails:

Recovery rates per step come from Baremetrics Recover, 2026.

Open rate is only a proxy for the outcome. A higher open rate that drives lower recovery loses to a lower open rate with a one-click link that recovers more. So optimize the link, not only the subject line.

Baremetrics Recover data confirms the day-1 email at 41% open drives 13% recovery, while later emails with comparable open rates recover far less.

Card network rules every dunning sequence must respect

Visa and Mastercard cap how often you can retry a failed charge, and most dunning sequences break the limits. Hard declines must never be retried, soft declines are capped, and exceeding either triggers per-attempt fees.

Persistent violators also risk processor monitoring on top of the fees.

The specific caps and fee amounts live in the passive churn guide, which holds the Mastercard and Visa retry figures. What matters for sequencing your emails is the operational rule those limits create.

Once retries hit the network limit without recovering the charge, stop retrying and shift to the card-update request in Step 5. Burning attempts past the cap costs fees and recovers nothing, because a card that hasn't paid after several timed retries usually needs a new number.

Retry discipline is one piece of the wider dunning management playbook.

One boundary is worth knowing. Retry limits apply per card, per merchant, per amount, and a subscriber who updates their card and triggers a fresh charge resets the counter. Smart retry systems track this for you.

Build the retry logic yourself and you track it at the processor level, or you risk crossing a limit you can't see.

FAQ

What's the difference between a dunning email and a collections letter?

A dunning email asks an active subscriber to fix a failed payment so service continues, while a collections letter pursues a debt a customer already owes..

Should I include a discount or offer in a dunning email?

No, skip the discount in a dunning email, because a failed payment is a credential problem, not a price objection. A discount delays the cancel rather than fixing the cause, and it trains subscribers to let payments fail to earn one.

What happens when a subscriber ignores every dunning email?

Once the dunning window closes with no recovery, the account pauses or cancels and the subscriber moves to a winback sequence. Winback shifts the ask, inviting them to choose to return where dunning asked them to fix a card.

How do I identify whether a decline is soft or hard?

Your payment processor returns a decline code with every failed charge, and that code tells you which track to send.