
How to recover failed payments and reduce subscription churn
Build the dunning flow that wins back failed payments, a cancel flow that offers pause and skip first, and the numbers that show subscription churn early.
The Wizel Team
Email marketing strategist · · 9 min read
On this page
- Two kinds of churn, two playbooks
- Retry soft declines, email hard ones
- Build the dunning flow in Klaviyo
- Stop failures before they happen
- Make the billing reminder a plan choice
- The cancel flow: offer the smaller ask that fits the reason
- Pause and skip without hiding a cadence problem
- The numbers a subscription store should watch
- Build a failed-payment recovery flow in Klaviyo
- Frequently asked
Some subscribers leave because they decided to. Many leave because a card expired and nobody fixed it. The two need opposite fixes, and the cheap one is easy to miss because it hides inside total churn. This guide builds the failed-payment flow, the billing reminder and the cancel flow, and names the numbers that tell you each one is working.
20-40%
of subscription churn is typically failed payments, not a decision to leave
A well-run recovery flow wins back half or more of it, because those customers still want the product. The retention chapter has the short version of the dunning emails and the cancel flow, and the series on how to run modern email marketing shows where subscriptions fit. Here is the build.
Two kinds of churn, two playbooks
| What differs | Voluntary churn | Involuntary churn |
|---|---|---|
| Cause | The customer chose to leave: price, value, done with the product | The payment failed: an expired or declined card, insufficient funds |
| Signal | A cancellation | A failed charge |
| Fix | Change the offer or the experience | Get a working card on file |
| Cost to fix | High: you have to re-earn the decision | Low: the customer still wants the product |
Fix involuntary churn first. It's a recovery problem, fast and cheap, not a retention problem. On accounts that already keep most subscribers past the first rebill, failed payments can become most of the churn that's left, and larger subscription brands run a dedicated dunning tool for them rather than rely on the subscription app's default retries.
Retry soft declines, email hard ones
Not every failed card is worth retrying:
| Decline | Common reasons | What recovers it |
|---|---|---|
| Soft | Insufficient funds, a temporary hold, over the limit, the bank timing out | Retrying the same card on a schedule |
| Hard | Expired card, closed account, reported lost or stolen, "do not honor" | Only a new card from the customer, so email at once |
Retrying a hard decline burns processor fees and can nudge the card issuer toward flagging you. Most soft declines clear within a few days, so when you retry matters more than how often. A sane schedule for a soft decline, set in your subscription app:
- 1.On the failed charge, to catch a momentary glitch.
- 2.Two days later, once small holds have cleared.
- 3.Three days after that, aimed at a Friday or Monday to straddle a likely payday.
- 4.Four days after that, the last automated try. Then stop and let the emails do the work.
Build the dunning flow in Klaviyo
Dunning is customer service, not debt collection: assume the customer wants the product and just needs to fix a card. If it runs in Klaviyo rather than the subscription app, set it up like this:
- Trigger on the subscription app's failed-payment event, and turn off the app's own dunning emails so nobody gets two of everything. The app's retries keep running underneath.
- Split on failure count. A first failure gets the friendly heads-up, a second a more urgent version.
- Write plain text from a person, with SMS alongside for SMS subscribers.
- One button: update payment. Link straight to the hosted card-update page, with no login and no hunting through account settings.
- Keep a grace period. A few days of continued service removes panic and buys the retries time.
- Stop the moment it's fixed. A working card must end every remaining retry and email at once. A "your payment failed" email after someone fixed it costs more trust than anything else in the flow.
- Add a post-cancel wave. When a subscription cancels for non-payment, a separate short sequence asks them to update the card to restart.
The four emails themselves (a heads-up the day it fails, a reminder 2-3 days later, a last chance at 5-6 days that names the pause date, and a "paused, your setup is saved" note) are in the retention chapter. Write each around what's at risk, not the debt: "Your coffee refill is on hold" beats "Payment failed: action required". The reminder names the next box, the streak or the price they locked in; the last chance gives a date: "We'll pause your plan on Friday unless we can update your card."
How many touches is a judgment call. Some agencies send 15 or more plain-text touches alongside the retries on accounts where failed payments are most of the churn. The longer the run, the more the stop-when-fixed rule matters.
Stop failures before they happen
The cheapest recovered payment is the one that never failed. Turn on your payment processor's account updater (network tokenization), which refreshes card numbers and expiry dates when banks reissue cards; check that your processor or subscription app supports it. Then email anyone whose card expires next month: "Your card on file ends in May. Update it now so your next order isn't interrupted." Stores without subscriptions need that email too if customers save cards for one-tap reorders.
One failure you can plan for: switching payment processor or subscription platform when saved cards can't move. Ask both providers whether cards can be migrated, because one practitioner estimates a forced re-entry can lose half or more of active subscribers. If it has to happen:
- 1.Lead with what they'll lose, only if it's true ("you're about to lose your subscriber price"). No discount yet.
- 2.Send an email a day, plus SMS to SMS subscribers, for 4-5 days, each with a one-tap link to the update page.
- 3.Then offer a modest thank-you discount for updating.
- 4.Keep a re-entry flow running: anyone not yet updated and not reminded in the last 24 hours goes back in.
- 5.Move anyone who never updates to a win-back segment.
Make the billing reminder a plan choice
The retention chapter sets the timing (3 days before the charge) and the skip, pause and swap links. The copy decides whether the reminder saves anyone. One agency ranked reminder styles across its subscription clients:
| Style | Example | Effect on churn |
|---|---|---|
| Plain disclosure only | "Your plan renews in 3 days" | Worst |
| Soft hero copy | "Your best results are still ahead" | Better |
| Free-gift framing, only if a gift really ships | "A free gift is in this box, nothing to do" | Better still |
| Plan upgrade, one click in the email | "Switch to quarterly and save $30" | Best |
The upgrade turns "stay or cancel?" into "monthly or quarterly?". Show the new price and next billing date before they accept. Practitioners split on when to start: some run it from the first reminder, others keep the first for reassurance ("here's how this works from now on") and save upgrades and add-ons for later rebills. The first charge is the biggest churn moment, so test before you put an upgrade there. Don't send the same reminder forever, either: it's the most-opened email in the subscription.
Order it as value first, then add-ons and swaps through the app's one-click links, then a results timeline or a testimonial, with the manage-subscription link last. Whether to cross-sell at all is contested, so test a version without add-ons and judge on cancellations as well as add-on revenue. In every version, the charge date, the amount and how to skip or cancel sit in readable body text, never only in fine print or an image.
The cancel flow: offer the smaller ask that fits the reason
A cancel click is a negotiation, not a goodbye. Ask why in one question, then offer what fixes that reason, with cancelling still one tap away:
| They say | Offer instead |
|---|---|
| Too much product, it's piling up | Skip the next order, or stretch the frequency (every 60 days instead of 30) |
| Too expensive right now | Pause for 30-60 days, a smaller plan, or a one-time loyalty discount |
| Travelling or a life change | Pause with a set restart date |
| Want to try something else | Swap the product, flavor or size |
| Don't need it anymore | Let them go cleanly, and win them back later |
Keep money off for the one reason that is about money, and make it once. A cancel button that always pays out becomes a coupon, the way constant discounts teach customers to wait. Pause, skip and swap solve the other reasons without repricing the product.
Don't hide the cancel button or force a phone call; that breeds resentment and chargebacks. Some subscription apps can block cancelling for a set period after signup (30 days in one), and one practitioner prefers 7-10 days with "give it a fair shot first" messaging. Use a lock only as a minimum term stated clearly before purchase, and check each market's rules first: some require cancelling online to be as easy as signing up.
Pass the cancel reason from the subscription app into Klaviyo as a profile property and branch the post-cancel emails on it: 1-2 straight after cancelling, each offering the alternative that fits the reason, and at most one more a few weeks later. After that, regular campaigns carry the win-back, around 30-60 days on, with something new rather than a desperate discount. A new flavor, size or product gives someone who already knows yours a reason to return.
Pause and skip without hiding a cadence problem
Make pausing easy, because a hard pause flow pushes people to cancel, and a paused subscriber keeps their setup, price and habit. Send three emails around a pause: a confirmation straight away, a reminder midway of what they're missing, and a reason to continue just before it resumes, so the pause doesn't become a cancel.
Read skips at two levels. For one subscriber, a skip beats a cancel, and practitioners find subscribers who skip often end up worth more over their lifetime. Across a cohort, a skip rate above 15% means the default cadence doesn't match real use; the retention chapter covers fixing it. A request to stretch the frequency is an early sign of falling use too: confirm it, then within a week suggest something that complements what they already get.
The numbers a subscription store should watch
Auto-renew keeps reorder and repeat rates near 100% whatever is happening, so they tell you nothing. Read cancellations and failed payments instead, which live in the subscription app, not in Klaviyo orders:
| Number | What it is | Watch for |
|---|---|---|
| Payment recovery rate | Recovered charges ÷ failed charges | 50%+ is a well-run flow; below 25%, fix the timing or the button |
| Involuntary churn rate | Failed-payment losses ÷ active subscribers | Should fall; report it apart from total churn |
| Save rate | Saves ÷ people who entered the cancel flow | Rising means the offers match the real reasons |
| Skip rate | Skips, tracked by cadence option | Above 15%: the cadence is out of step |
| Cancel rate | Cancels, tracked by cadence option and signup cohort | Cancels bunching at one billing cycle, most often the first charge |
| Support tickets per 100 subscribers | A proxy for experience quality | Rising means something in the experience is wrong |
| Net contribution margin per subscriber | Revenue less product, shipping and support costs, over 90-180 days | Whether a cadence or offer really pays |
If you track only one, make it payment recovery rate: it isolates the flow from everything else. Then watch the subscribers who stopped clicking but still renew, the tail that cancels next. When people cancel tells you why: a cancel on signup day points to how the purchase was set up, an early cancel to onboarding, a later one to a habit that never formed. And trust a rate only when it rests on 500+ delivered emails and 50+ events.
If you run this for clients, get access to the subscription app's cancellations and failed payments before you judge anything from Klaviyo, and check whether the app's own dunning emails are still switched on before you build yours.
This week, pull two figures from the subscription app: how many charges failed last month, and how many were recovered. If recovery is under half, turn on the card updater and build the dunning flow before you touch the cancel flow. How much of the rest applies depends on how the store sells, which is where email marketing by store type picks up.
Build a failed-payment recovery flow in Klaviyo
- 1
Turn on the card updater
Enable your payment processor's account updater so reissued cards refresh automatically, if your processor or subscription app supports it.
- 2
Set the retry schedule
Retry soft declines about 4 times, 2-4 days apart and aimed at paydays. Don't retry hard declines such as expired or closed cards; email at once.
- 3
Trigger the flow on the failed-payment event
Start the Klaviyo flow from the subscription app's failed-payment event, split on failure count, and turn off the app's own dunning emails.
- 4
Send the heads-up
On the day of the failure, send a plain-text email from a person with one button that opens the hosted card-update page.
- 5
Remind, then set a deadline
Two to three days later, restate what's at risk. At five to six days, name the date the plan pauses.
- 6
Pause and leave the door open
When the grace period ends, pause the plan, say the setup is saved, and start a short update-your-card-to-restart sequence.
- 7
End it the moment payment works
Make a successful payment stop every remaining email and retry at once.
- 8
Catch expiring cards early
Email customers whose card on file expires next month, before the charge fails.
Frequently asked questions
What is a dunning email sequence?
A short series of emails sent when a subscription payment fails, asking the customer to update their card. A good one runs 3-4 emails over about a week alongside payment retries, each with one button to the card-update page, and stops the moment the payment goes through.
How many times should you retry a failed subscription payment?
About 4 attempts for a soft decline, 2-4 days apart and aimed at likely paydays, then stop and rely on email. Hard declines, such as an expired or closed card, can't be fixed by retrying, so email the customer at once.
What is a good failed payment recovery rate?
As a rule of thumb, a well-run flow recovers half or more of failed payments. Below 25%, fix the timing and the update-payment button first.
Should I offer a discount when a subscriber cancels?
Only when the reason is price, and only once. For other reasons, offer what fixes them: skip or stretch the frequency for too much product, pause for a life change, swap for someone who wants something different.
When should a subscription billing reminder go out?
About 3 days before the charge, framed around what's arriving, with the charge date, the amount and how to skip or cancel stated plainly in the body.


