Quick answer: Subscription churn comes in two flavors. Voluntary, where customers actively cancel, and involuntary, where payments fail silently and the subscription lapses. Dunning is the structured process of recovering those failed payments through a sequence of automated retries and customer messages. To reduce both, fix the involuntary leak first with smart retry timing, card-updater services, and clear pre-dunning warnings. Then go after voluntary churn with pause options, downgrade paths, and proactive outreach before renewals. A well-run dunning flow typically recovers a meaningful share of failed charges that would otherwise be lost. For any subscription merchant, the most reliable lever is treating a failed payment as a recoverable event rather than a cancellation.
By the Wcart team, we build and support white-label ecommerce and multi-vendor marketplace software, so this is written from hands-on platform experience.
If you sell anything on a recurring basis (boxes, memberships, SaaS-style access, replenishment products) churn is the number that quietly decides whether you grow or stall. The frustrating part is that a large slice of churn isn’t customers choosing to leave. It’s cards expiring, banks declining, and renewal emails landing at the wrong moment. This guide breaks down both kinds of churn and gives you an operator-grade playbook for dunning that actually recovers revenue.
Voluntary vs involuntary churn: know which one you have
Before you build any retention tactic, measure where your churn actually comes from. The two categories need completely different solutions, and most teams over-invest in one while ignoring the other.
Voluntary churn
This is a customer deciding the product is no longer worth the price. They click cancel, they reply to a renewal email, or they let a contract lapse on purpose. Causes are usually value-related: weak onboarding, a product that doesn’t get used, a price increase, or a competitor. You fix voluntary churn with product, pricing, and lifecycle communication, not with payment plumbing.
Involuntary churn (the silent leak)
This is a payment that fails for a technical reason: an expired card, insufficient funds, a bank flagging the transaction as suspicious, or a card that was reissued after fraud. The customer never intended to leave. Often they don’t even know it happened. Industry practitioners consistently report that involuntary churn is a large and under-managed share of total subscription cancellations, frequently a double-digit percentage of failed renewals that could have been saved. This is where dunning lives, and it’s usually the fastest ROI you’ll find.
| Dimension | Voluntary churn | Involuntary churn |
|---|---|---|
| Root cause | Perceived value, price, competition | Card/bank/payment failures |
| Customer intent | Wants to leave | Wants to stay |
| Primary fix | Onboarding, pricing, pause/downgrade | Dunning, retries, card updater |
| Speed to recover | Slow, needs product change | Fast, process and config change |
| Tooling | Lifecycle email, surveys, offers | Retry logic, pre-dunning, account updater |
What dunning is and how the flow works
Dunning is the automated sequence that runs after a recurring charge fails. A solid flow has four moving parts: detection, retries, communication, and an exit path. Get the timing and tone right and you recover revenue without annoying healthy customers.
1. Detection and decline-code routing
Not all declines are equal. A payment processor returns a decline code, and the smartest dunning systems branch on it. A “hard” decline (stolen card, account closed, invalid number) shouldn’t be retried the same way as a “soft” decline (insufficient funds, temporary hold, issuer timeout). Soft declines are worth aggressive retrying. Hard declines need the customer to take action immediately. Reading these codes is the single highest-leverage thing most merchants are not doing. What actually happens when you ignore them: you keep slamming a closed account with retries, rack up processor fees, and tank your acceptance rate while the customer was never coming back anyway.
2. Smart retry scheduling
Retrying a failed card one minute later rarely works. Retrying on a smarter schedule does, because the underlying problem (low balance, daily limit, temporary hold) often clears within a few days. A common, sensible pattern is to space retries over roughly a week to two weeks, say day 0, day 3, day 5, and day 7, and to favor times like early in the month when balances are likelier to be funded. Don’t hammer the card, which can trigger fraud flags and worsen your acceptance rate.
3. Customer communication (the part most teams botch)
Every retry should be paired with a clear, friendly message. The message must do three things: tell the customer their payment didn’t go through, explain it’s easy to fix, and give a one-click update link. Tone matters. Lead with helpfulness, not threat. The first message can be soft (“we couldn’t process your renewal, no action needed yet, we’ll try again”), and later messages escalate gently toward urgency before the final lapse notice.
4. The exit path
Decide in advance what happens when retries are exhausted. Options include moving the customer to a paused state, downgrading to a free tier, or cancelling with a clear win-back trigger. Never silently delete the account. A graceful exit keeps the door open for recovery.
Pre-dunning: stop failures before they happen
The cheapest failed payment is the one that never fails. Pre-dunning is the proactive layer that catches problems ahead of the charge.
Card expiry warnings
You know when a stored card is going to expire. Email the customer two to four weeks before, with a one-click update link. This single tactic prevents a surprising share of involuntary churn because expired cards are one of the most common decline reasons.
Account updater / network tokenization
Card networks offer “account updater” services (and tokenization) that automatically refresh card details when a customer’s bank reissues a card. If your payment stack supports it, enabling it means many reissued cards keep working with zero customer action. This is one of the highest-impact, lowest-effort fixes available. The catch worth knowing: coverage isn’t total, since not every issuer participates and updates can lag the reissue by a billing cycle, so you still want retries and pre-dunning behind it. The major card networks document these programs publicly, and your processor exposes them as a toggle or API feature.
Renewal reminders
For higher-priced or annual plans, a friendly heads-up before renewal reduces both surprise chargebacks and involuntary failures, and it gives customers a clean moment to update payment details on their own terms.
Reducing voluntary churn
Dunning recovers payments. It doesn’t fix a product people stopped valuing. Pair your dunning work with these voluntary-churn levers.
Offer pause instead of cancel
A large portion of cancellations are situational. A customer is traveling, has too much stock, or is tightening spending. A prominent “pause” option converts many would-be cancellations into a temporary hold. A paused subscriber is far more likely to return than a cancelled one.
Build a downgrade path
If your only options are full price or nothing, you push price-sensitive customers all the way out. A smaller box, a lower-frequency plan, or a cheaper tier keeps the relationship (and some revenue) alive.
Run a cancellation flow that learns
When someone cancels, ask one short question about why. Route the answer to a relevant save offer (a discount for “too expensive,” a pause for “taking a break,” support for “not using it”). Even if you don’t save the customer, you collect the churn-reason data that tells you what to fix next.
Fix the first 30 days
Most subscription churn is decided early. Strong onboarding, getting the customer to the first real value fast, is the most durable churn reducer there is, and it costs nothing per save once it’s built.
Metrics to watch
You can’t improve what you don’t instrument. Track these at minimum:
| Metric | What it tells you |
|---|---|
| Gross vs net revenue churn | Whether expansion is offsetting losses |
| Involuntary churn rate | Size of the recoverable leak |
| Dunning recovery rate | Share of failed charges you win back |
| Payment acceptance rate | Health of your processor/routing |
| Save-offer take rate | Effectiveness of pause/downgrade flows |
For deeper background on how recurring billing and dunning fit into payment infrastructure, the Stripe Billing documentation is a clear, vendor-neutral primer on the underlying mechanics, and Wikipedia’s overview of churn rate covers the core definitions. For card-detail refresh programs, review the official documentation from networks such as Visa.
How this maps to a Wcart store
On a white-label subscription store, the practical setup looks like this: connect a processor that exposes decline codes and account-updater support, configure a retry schedule on soft declines, wire pre-dunning emails to card-expiry and renewal events, and expose pause/downgrade actions in the customer account area. The goal is to make involuntary churn a managed, recoverable event and to give customers low-friction alternatives to outright cancellation. If you’re building or migrating a recurring-revenue store, see Wcart for the platform side of this.
Frequently asked questions
What is dunning in subscriptions?
Dunning is the automated process of recovering failed recurring payments. When a renewal charge is declined, a dunning flow retries the payment on a schedule and sends the customer messages prompting them to update their payment method, so a technical failure does not turn into a lost subscriber.
What is the difference between voluntary and involuntary churn?
Voluntary churn is when a customer actively chooses to cancel because of price, value, or a competitor. Involuntary churn is when a payment fails for a technical reason, like an expired card, insufficient funds, or a bank decline, and the customer never intended to leave. Dunning targets involuntary churn.
How many times should I retry a failed payment?
There is no universal number, but a common, effective pattern is three to four retries spread over roughly one to two weeks (for example day 0, 3, 5, and 7) for soft declines. Avoid rapid repeated retries, which can trigger fraud flags and hurt your acceptance rate. Hard declines should prompt the customer to act rather than be retried blindly.
What is pre-dunning?
Pre-dunning is proactive prevention before a charge fails: sending card-expiry warnings, renewal reminders, and using account-updater services so cards are refreshed automatically. It stops many failures from ever happening, which is cheaper than recovering them afterward.
Does dunning hurt the customer experience?
Done badly, yes. Aggressive, threatening messages annoy people. Done well, it’s a helpful service: customers want their subscription to keep working, and a clear “your payment didn’t go through, here’s a one-click fix” message is appreciated. Tone and a short escalation arc are what separate good dunning from spammy dunning.
How much churn can dunning actually recover?
It varies widely by audience, price point, and decline mix, so be skeptical of any single guaranteed figure. In practice, a well-configured dunning flow recovers a meaningful portion of failed charges that would otherwise be lost, often enough to pay for itself many times over, especially when combined with account-updater and pre-dunning. Measure your own recovery rate rather than trusting a benchmark.
Should I offer a discount to stop someone from cancelling?
Sometimes, but not as a reflex. Discounts can save a price-sensitive customer, but they also train people to threaten cancellation for a deal and can erode margin. Often a pause or downgrade saves the relationship without permanently cutting price. Route the save offer to the stated cancellation reason rather than offering a blanket discount to everyone.
Leave a Reply