Revenue recovery

The cheapest revenue you will ever recover is the money you already earned

A meaningful share of subscription churn is not a decision — it is an expired card. These customers wanted to keep paying you. Four emails over two weeks recover most of them, and almost nobody writes them properly.

Full copy on this page · No signup · Nothing gated

In short

A failed payment series, or dunning sequence, is four emails across roughly two weeks while the payment is retried: a plain notice on the day of the decline, a clearer one at day three, a warning at day seven that names the date access changes, and a final notice at day fourteen. Industry estimates put involuntary churn — failures caused by card expiry, insufficient funds or a bank block rather than intent — at a large fraction of total subscription churn, which makes this the highest-return sequence most subscription businesses never build. The critical rule is that these are transactional service messages, so they must reach people who opted out of marketing. Full copy for all four is below.

InvoluntaryChurn from failed cards, not decisions. A large share of total churn
4 emailsOver about two weeks, matched to your retry schedule
TransactionalNot marketing. Must reach people who unsubscribed from campaigns
1 linkStraight to updating the card. Every extra step loses recoveries

The sequence

1Email 1 — the day the payment fails
SubjectYour payment didn't go throughProbably the card. Takes a minute to fix.

Hi {{first_name}},

We tried to charge {{amount}} for {{plan_name}} today and it didn't go through. Nothing has changed with your account.

The most common reason is a card that has expired or been replaced. Updating it takes about a minute: {{update_payment_link}}

We'll try again automatically on {{next_retry_date}}, so if you update before then it will just go through.

Update payment method

Why it is shaped this way: Calm, factual, and free of consequences. Day one is not the day to mention losing access — most failures resolve on the next retry without the customer doing anything, and a threatening first email creates support tickets and cancellations from people whose payment was about to succeed anyway. Naming the likely cause reassures somebody who briefly wonders whether they have been defrauded.

2Email 2 — day 3
SubjectStill can't process your payment for {{plan_name}}One minute to update. Here's exactly what to do.

Hi {{first_name}},

The retry on {{retry_date}} didn't go through either, so it is probably not a temporary issue.

Three things it usually is:

The card expired or was reissued · The bank declined an automatic payment it didn't recognise · Not enough available balance on the day we tried

Any of them are fixed the same way: {{update_payment_link}}

If the card looks fine to you, it is worth a quick call to your bank — they will sometimes block a recurring charge without telling anyone.

Update your card

Why it is shaped this way: By day three the passive path has failed, so this email has to help the customer diagnose. The bank-block line matters more than it looks: it is a genuinely common cause, it is invisible from the customer's side, and naming it converts a confused person who believes their card is fine into somebody who knows what to do next.

3Email 3 — day 7
SubjectAction needed: {{plan_name}} pauses on {{cutoff_date}}Everything stays as it is if you update before then.

Hi {{first_name}},

We still haven't been able to process {{amount}} for {{plan_name}}.

If it isn't resolved by {{cutoff_date}}, your account will {{specific_consequence}}. To be clear about what that means: {{what_is_retained}}, and {{what_stops_working}}.

Update here and nothing changes: {{update_payment_link}}

If there's a reason this is difficult right now, reply and tell me. We can usually work something out, and I'd rather do that than lose you over a card.

Update payment method

Why it is shaped this way: The first email that names a consequence, and it must be specific and true. 'Your account will be suspended' is vague enough to be frightening without being actionable; 'sending pauses on the 14th, your data and templates are kept' tells somebody exactly what they are deciding about. The offer to reply is not softness — a customer in financial difficulty who is given a route usually takes it, and a paused plan beats a cancellation.

4Email 4 — day 14
SubjectLast notice before {{plan_name}} pausesAfter today we stop trying. Your data stays for {{retention_period}}.

Hi {{first_name}},

This is the last email about the payment for {{plan_name}}. After today we'll stop retrying and the account will {{specific_consequence}}.

Your data stays for {{retention_period}}, so restarting later is a card update rather than a rebuild.

If you meant to cancel, no action needed and no hard feelings — thanks for the time you spent with us.

If you didn't: {{update_payment_link}}

Keep my account

Why it is shaped this way: Give the customer permission to leave. A significant share of failed payments are a passive cancellation — somebody who decided months ago and let the card lapse rather than clicking cancel — and pursuing them past this point produces spam complaints on a transactional stream you cannot afford to have flagged. Saying the data survives is what makes a later return cheap for both of you.

What goes wrong with this sequence

Sending them as marketingThis is the mistake that quietly destroys the whole sequence. A dunning email is a service message about an existing contract, and it has to reach somebody who unsubscribed from your newsletter. If these go out through your marketing suppression list, the customers you most need to reach are the ones who never see them. Send them transactionally and exclude them from marketing suppression, while still honouring genuine account-level opt-outs.
Not matching the emails to the retry scheduleIf your processor retries on days 3, 5 and 7 and your emails go out on days 1, 7 and 14, customers get told a payment failed after it already succeeded. Read the actual retry configuration and hang the emails off the retry events rather than off a fixed timer.
Making them log in to update the cardEvery step between the email and the card form loses recoveries. A tokenised link straight to the update page — short-lived and single-use, so it is safe to email — recovers materially more than 'log in to your account and go to billing'. This is the highest-leverage technical change available in the whole flow.
Threatening on day oneMost first failures clear on the next automatic retry. An immediate warning about suspension generates cancellations and support load from customers who were never at risk, and it burns the credibility you need on day seven when the warning is real.
Continuing after the final noticeYou said it was the last one. Continuing produces complaints against a transactional sending stream, which is far more damaging than complaints against a newsletter — that stream also carries your receipts and password resets, and it cannot afford a reputation problem.
No in-app or SMS backupEmail is one channel and this message matters more than most. A persistent in-app banner costs little and catches the customers who never open email. For high-value plans, a single SMS at day seven is proportionate.

Questions

Are dunning emails transactional or marketing?

Transactional. They concern an existing contractual relationship and contain no promotional content, which is what places them outside marketing consent requirements in most jurisdictions. That is also why they must be sent from a transactional stream rather than through a campaign tool that applies your marketing suppression list — the customer who unsubscribed from your newsletter still needs to know their card failed.

How many retries and over how long?

Most processors default to three or four attempts across one to two weeks, often with smart timing that targets days when balances are likely to be higher. Take the schedule from your processor rather than inventing one, and match the emails to it. Retrying far beyond two weeks recovers very little and increasingly annoys people who have already moved on.

Should I offer a discount to keep them?

Not in this sequence. A failed card is a payment problem, not a price objection, and offering money off in response teaches customers that letting a payment lapse produces a discount. If somebody replies saying cost is genuinely the issue, that is a real conversation and a smaller plan is usually the right answer.

What about SCA and 3D Secure failures?

These need their own wording, because the customer has to actively authenticate rather than fix a card. A generic 'your payment failed' leaves them updating a card that was never the problem. Detect the authentication-required decline code and send a variant that explains they need to approve the charge with their bank, with a direct link to do it.

Does this apply to annual plans too?

Yes, and the stakes are higher because the amount is larger and a decline is more likely on a big charge. Start the sequence earlier for annual renewals — a heads-up before the charge, not just after it fails — since a customer who is expecting the amount is far less likely to have it blocked by their bank.

Keep exploring

Transactional APIWhere these must send from, outside marketing suppression.Stripe integrationComing soon — today, send Stripe payment events in by webhook.Free trial sequenceThe sequence that runs before this one, when they first convert.Marketing and transactional togetherWhy running both on one platform stops them fighting for reputation.Email marketing for SaaSThe rest of the subscription lifecycle.All templatesWelcome, cart recovery, launch sequences and more.
Free · 7 days

Build this sequence in an afternoon.

Seven days of full access, no credit card. Paste the copy, set the timings, connect your store or signup form, and let it run.

Start your 7-day free trialSee all templates