Platform

Solutions

Resources

Platform

Solutions

Resources

Blog

Involuntary churn vs voluntary churn: what's the difference, and how to reduce it

Involuntary churn explained for subscription businesses: what it is, how it differs from voluntary churn, what causes it, and how to reduce it without breaking the card networks’ rules.

Published:

·

14 min read

Illustrated cover for: Involuntary Churn vs Voluntary Churn: The $440B Problem SaaS Companies Underestimate

Involuntary churn is the subscribers you lose without them ever deciding to leave. A renewal payment fails, nobody fixes it in time, and an account that was perfectly happy on Monday is cancelled by the end of the month.

Voluntary churn is the other kind: a customer weighs up what they pay against what they get, and goes. The two look identical in a monthly churn report. They have different causes, different owners and very different fixes, which is why lumping them together is the most expensive mistake in subscription reporting.

Our position is simple. For most consumer subscription brands, involuntary churn is the cheapest churn to win back, because the customer never wanted to leave. It’s also the easiest to make worse, by retrying cards the networks have told you to leave alone.

A declaration of interest before we go further. OpenByte sells billing, payments and support software that’s built to reduce involuntary churn. That’s a reason to be sceptical of us, so every figure below links to where it came from, and where the evidence is weak we’ll say so.

The short version

What it is: subscribers lost because a payment failed or a billing process broke. Nobody chose to leave.

What causes it: declined renewals, expired or replaced cards, failed authentication, billing errors and service cut off too early.

What it isn’t: a product or pricing problem. A better product won’t fix a card that expired in March.

Who should care most: subscription businesses billing consumers monthly by card, where renewals cluster and every point of failure rate is real money.

What is involuntary churn?

Involuntary churn is the loss of subscribers whose subscriptions end because a payment or billing process failed, rather than because they chose to cancel. The most common cause is a declined renewal that isn’t recovered before the subscription lapses. It’s often called passive churn.

That’s the involuntary churn meaning most billing platforms use, and it’s the one we’ll stick to. One wrinkle: Stripe’s guide treats “passive churn” as something slightly different. If a vendor’s numbers look odd, check which definition they’re using before comparing.

The word that matters is “recovered”. A declined payment isn’t churn yet. It becomes involuntary churn only when your retries, emails and grace period all run out and the subscription is cancelled. Everything between the decline and the cancellation is your chance to fix it.

Voluntary vs involuntary churn: the difference

Voluntary churn is a customer decision. They cancel, they don’t renew, or they drop to a free plan, because they’ve decided the product isn’t worth what they’re paying. Involuntary churn involves no decision at all. The table sets out why the two need separate handling.

Aspect

Voluntary churn

Involuntary churn

What happens

The customer cancels or doesn’t renew

A payment or billing process fails

Customer intent

Wants to leave

Usually wants to stay

Typical causes

Price, product fit, a competitor, no longer needed

Declines, expired cards, failed authentication, billing errors

Who owns the fix

Product, pricing, marketing, customer success

Payments, billing, support

Main levers

Cancel flows, pause and downgrade options, win-back

Updaters, retry rules, dunning, grace periods

How fast it’s won back

Weeks or months, if at all

Often within days of the failure

Voluntary vs involuntary churn isn’t always a clean split. A customer who was already lukewarm may treat a failed payment as a convenient exit and simply not update their card.

That counts as involuntary in your data, but no amount of clever retrying will save it. It’s one reason to judge your recovery work on revenue recovered. The number of emails sent proves nothing.

Our view. Report the two separately or don’t report churn at all. A single churn number tells the product team their roadmap failed when the real culprit may be a batch of expired cards, and it tells finance nothing about which half of the problem is cheap to fix.

How much churn is involuntary?

Nobody independent measures this, so every figure comes from a vendor with something to sell. Here are the ones worth knowing, with what they’re based on.

Source

Figure

What it’s based on

Caveat

Recurly churn benchmarks (July 2026 data)

Involuntary churn 1.25%, voluntary 2.34%, total 3.60%

Recurly’s own merchant network

Sample and method not published

ProfitWell (now Paddle), 2018

20% to 40% of churn is involuntary

A report on “3,000+ companies”

No method published, eight years old

PYMNTS and FlexPay, January 2023

About half of churn caused by failed payments

Survey of subscription merchants

Sample size not stated, FlexPay sells recovery tools

Recurly’s figures put involuntary churn at roughly a third of the total, which sits comfortably inside the old 20% to 40% range. Treat that as a plausible ballpark for card-heavy consumer subscriptions. It isn’t a target. Your own split, measured properly, is the only number that counts.

Numbers to ignore

You’ll often see involuntary churn described as a “$440 billion” problem. We couldn’t trace that figure to any published method. The closest we found is an unsupported estimate in a vendor press release.

Recurly’s own headline, that failed payments could cost subscription businesses more than $129 billion in 2025, is at least explained. It’s modelled: Recurly applied the revenue lift it claims for its own tools to a market-size projection from 2021. It’s a sales estimate. Big round numbers make good headlines and poor business cases.

What causes involuntary churn?

Most guides stop at “failed payments”. That’s the biggest cause, but not the only one, and the others are often easier to fix. These are the five causes of involuntary churn we’d look for.

Cause

What happens

Typical fix

Declined renewals

The issuer declines the charge: insufficient funds, a fraud flag, a blocked card

Retry within network rules, ask the customer to update

Expired or replaced cards

The stored card details are out of date

Card account updaters, network tokens, pre-expiry reminders

Failed authentication

A payment needing customer authentication isn’t completed

A clear authentication path in your recovery emails

Billing errors

Wrong amount, duplicate charge, or a charge after cancellation

Billing that reads the same subscription record as everything else

Access cut too early

Service is suspended before recovery has finished

Grace periods tied to the dunning state

Declined renewals

Visa says insufficient funds is the most common reason cards are declined worldwide. That’s good news, because it’s temporary. Money arrives, and a retry a few days later often succeeds. Other declines are permanent, which is where retry rules come in (more on those below). Our guide to payment failure explains each decline code in detail.

Expired and replaced cards

Cards get reissued all the time: on expiry, after fraud, after a bank migration.

Mastercard’s updater page quotes Worldline research that about 40% of cardholders replace their cards each year. We haven’t seen the underlying study, so take the exact number lightly. The direction is clear enough: a long-tenure subscriber base is full of card details that have quietly gone stale.

Failed authentication

In Europe, a renewal that you initiate isn’t normally subject to strong customer authentication.

The European Banking Authority’s guidance says payee-initiated transactions “are therefore not subject to strong customer authentication”, as long as the mandate was authenticated when it was set up. Issuers can still ask for authentication, though, and a customer who never completes it looks exactly like a decline in your data.

Billing errors

A customer charged after cancelling, or charged twice, rarely churns quietly. They dispute the charge, and the relationship ends in a chargeback. These cases are few in number but expensive, and they’re nearly always caused by the billing system working from a different version of the subscription than the product.

Access cut too early

This is the one nobody counts. A payment fails, access is restricted the same day, and the customer experiences it as the product breaking. Some never come back to fix the card. In your reporting it looks like ordinary payment churn. In reality, your own entitlement rules caused it.

Our view. Before you buy anything, check the boring causes. Cancellation that doesn’t reach billing, access cut on day one, a card update page that needs a password reset. These cost nothing to fix and no vendor will ever mention them, because there’s nothing to sell you.

The card network rules most guides leave out

You can’t reduce involuntary churn by retrying harder. Visa and Mastercard both limit how often you can retry a declined payment, and both charge for breaking the rules. Almost none of the pages ranking for this topic say what the rules are, so here they are.

Visa’s Core Rules (October 2026 edition) sort declines into four categories. Category 1 means “issuer will never approve”, and a merchant “must never resubmit” the payment on the same card.

That covers codes such as 04, 07, 12, 14, 15, 41, 43, 46, 57, R0, R1 and R3. For the other categories, which include insufficient funds and expired cards, Visa allows up to 20 attempts in 30 days.

That limit has moved. When Visa introduced these rules in April 2021, the cap was 15 attempts in 30 days, and plenty of guides still say 15. If a source doesn’t give a date, check it with your acquirer.

Mastercard does it differently. Each decline can carry a Merchant Advice Code: MAC 03 means “do not try again”, MAC 21 means the customer has cancelled the payment, and codes 24 to 30 tell you how long to wait before retrying.

The fees for breaking these rules are small per attempt and large at volume. PayPal’s guidance for merchants lists Visa’s excessive retry fee at $0.10 domestic and $0.25 cross-border, and says Mastercard charges once you pass 10 retries in 24 hours or 35 in 30 days. Visa’s public rulebook doesn’t print the fee amounts, so confirm them with your acquirer.

Our view. If your billing system can’t tell you which decline category each failed renewal fell into, you’re probably already paying retry fees without knowing. Ask for the report before you ask for a smarter retry schedule.

How to reduce involuntary churn

Reducing involuntary churn is mostly about doing six unglamorous things well, in order. Each one stops a different kind of failure, so skipping the early ones makes the later ones work harder.

1. Keep card details current

Card account updaters fix stale cards before you ever charge them. Visa Account Updater passes on new card numbers and expiry dates, and flags closed accounts. Mastercard’s Automatic Billing Updater does the same. Many payment providers offer both, sometimes for a small fee per update.

Network tokens go a step further. The token stays valid when the physical card is replaced, so the renewal goes through as normal.

Visa reports a 4.3% increase in authorisation rates on card-not-present payments using tokens. Adyen, a payment provider, reported an average 3% uplift across its merchants. These are vendor figures, measured on their own traffic, but they’re consistent and the mechanism is sound.

2. Remind customers before cards expire

You know the expiry date of every card you store. A short email 30 days before it expires, with a direct link to update the card, prevents the failure before it happens. Updaters won’t catch every card, because not every issuer takes part, so reminders cover the gap.

3. Retry within the rules

Retry soft declines, like insufficient funds or a temporary issuer outage, on a schedule that gives the customer’s account time to recover. Never retry the declines the networks say will never succeed. Stripe’s Smart Retries, for example, defaults to up to eight retries within two weeks, and doesn’t retry codes such as lost or stolen cards.

Picture a consumer brand that renews 100,000 subscribers on the first of the month, with 8% declined first time. That’s 8,000 failed payments.

If half are insufficient funds and the rest are a mix of expired cards and permanent declines, the right schedule treats each group differently. Retrying all 8,000 every day for a fortnight would recover little extra and breach Visa’s rules on a few thousand of them. (These numbers are illustrative only.)

For more detail, see why payment retries fail at scale.

4. Ask the customer properly

When a retry won’t work, the customer has to act. Tell them quickly, tell them exactly what failed (“your card ending 4242 was declined”), and send them to a page where they can update the card in two steps without logging in. Use the channels they actually read: email, in-app messages, SMS if you have consent.

This is what dunning is, and it’s covered in depth in our dunning strategy playbook.

5. Give a grace period, and connect it to your dunning

Keep the customer’s access running while recovery is in progress. Someone still using the product has a reason to fix their card. Someone who’s been locked out has a reason to shrug. The grace period should end when your dunning sequence ends. A fixed day that nobody has linked to it helps no one.

6. Fix billing errors at source

Make sure cancellations, plan changes and refunds reach billing immediately. If the product, the billing system and the support desk each keep their own copy of the subscription, they’ll eventually disagree, and the customer finds out first.

Our view. If you only do one thing this quarter, do the first two. Updaters and expiry reminders stop failures happening at all, and a payment that never fails needs no retry, no email and no apology.

How to measure involuntary churn

You can’t reduce what you can’t see, and most businesses can’t see involuntary churn because the decline lives in the payment provider while the cancellation lives somewhere else. Fixing that starts with tagging every lost subscriber with a reason at the moment they leave.

Reason code

Type

Recorded when

Cancelled

Voluntary

The customer cancels

Didn’t renew

Voluntary

An annual plan lapses by choice

Payment failed

Involuntary

Dunning ends without recovery

Billing dispute

Involuntary

The account closes after a billing complaint or chargeback

Authentication not completed

Involuntary

A renewal fails on authentication and isn’t recovered

Unknown

Unclassified

No reason can be found

The payment failure code should be applied automatically when dunning ends. Typing it in by hand means it gets missed. And keep an eye on “unknown”. A big unclassified bucket usually hides involuntary churn that nobody tagged.

With the reasons in place, the involuntary churn rate is simple: subscribers lost to involuntary reasons in the period, divided by subscribers at the start of it. Track it by count and by revenue, monthly. For the general formulas, see our guide to subscription churn rate.

Two more numbers tell you whether your recovery is working:

  • Recovery rate: the share of failed renewals that are paid before the subscription ends.

  • Time to recovery: how long recovered payments take. The longer a payment stays failed, the less likely it is to recover.

Vendors publish recovery rates too. Stripe, for instance, says businesses using it recover 55% of failed payments on average. It doesn’t say how that’s measured, so treat it as context only.

How to reduce voluntary churn

This guide is mostly about the involuntary kind, but voluntary churn deserves a word, because the two meet at the cancel button. Three things help most.

  • Offer a pause or a cheaper plan before the exit. Some customers leaving on price would stay on less.

  • Ask why, once, at the moment of cancellation. One short question gives product and pricing teams something better than guesswork.

  • Run win-back for the right people. Someone who left a month ago over price may come back for a better offer. Someone who left over a bug won’t, until it’s fixed.

Voluntary churn is a product and value problem, so its fixes belong to the teams who own those. Don’t let a dunning project pretend to solve it.

Where involuntary churn reduction gets hard

None of the steps above is technically difficult. What makes it hard is that each one needs information held somewhere else. Expiry reminders need the card data from the payment provider. Decline-aware retries need the decline code. Grace periods need the dunning state. Support agents need to see all of it when the customer calls.

When the payment provider, the billing system, the help desk and the email tool are separate products, every one of those links is an integration that can break. That’s the gap OpenByte was built to close: payments, billing, support and messaging working from one customer record. You can see how it handles recovery on our dunning management page.

Frequently asked questions

What is involuntary churn?

Involuntary churn is when subscribers are lost because a payment or billing process failed, without them choosing to cancel. The usual cause is a declined renewal that isn’t recovered before the subscription ends. It’s often called passive churn.

What is voluntary churn?

Voluntary churn is when a customer decides to leave. They cancel, don’t renew, or move to a free plan, usually because of price, product fit or a competitor. It’s fixed by product, pricing and retention work.

What is the difference between voluntary and involuntary churn?

Voluntary churn is a decision by the customer. Involuntary churn happens without one, usually after a failed payment. The difference matters because involuntary churn can often be recovered within days, while voluntary churn needs changes to the product or the offer.

What causes involuntary churn?

The main causes are declined renewals, expired or replaced cards, failed authentication, billing errors, and access being cut off before recovery has finished. Declines for insufficient funds are the most common, and often succeed on a later retry.

How do you reduce involuntary churn?

Keep card details current with account updaters and network tokens, remind customers before cards expire, retry soft declines within card network rules, ask customers to update their card through a simple page, keep access running during a grace period, and fix billing errors at source.

How do you stop involuntary churn completely?

You can’t. Some cards are closed, some customers have no funds, and some would have left anyway. The goal is to recover every payment that can be recovered, without breaching card network retry rules or annoying customers who still want to stay.

What is a good involuntary churn rate?

There’s no independent benchmark. Recurly’s network data for July 2026 put involuntary churn at 1.25% against 2.34% voluntary, roughly a third of all churn. Compare yourself with your own trend first, since billing model and payment methods change the number a lot.

How does dunning reduce involuntary churn?

Dunning is the sequence of retries and messages after a payment fails. It reduces involuntary churn by retrying the payments that can succeed and prompting customers to update the cards that can’t. Good dunning is quick, specific, and sends customers to a simple update page.

How many times can you retry a failed subscription payment?

Under Visa’s current rules, up to 20 times in 30 days for declines that may later succeed, and never for declines like lost, stolen or closed cards. Mastercard charges fees beyond 10 retries in 24 hours or 35 in 30 days. Check the current limits with your acquirer.

Key takeaways

  • Involuntary churn is subscribers lost to failed payments and billing problems without any decision to leave, and it needs different fixes and owners from voluntary churn.

  • Independent figures don’t exist. Vendor data suggests roughly a quarter to a third of churn is involuntary, but only your own tagged data counts.

  • Visa allows up to 20 retries in 30 days for recoverable declines and never for its “will never approve” category. Mastercard’s advice codes tell you when to stop.

  • The cheapest wins come first: account updaters, network tokens and expiry reminders stop failures before they happen.

  • Measure it properly: tag every exit with a reason, apply the payment failure code automatically, and track recovery rate and time to recovery.

One exercise for this week: take last month’s cancelled subscriptions and split them three ways: chose to leave, payment failed, and unknown. If the last two together are bigger than you expected, that’s where to start.

Stop losing subscribers you should keep

See how OpenByte recovers failed payments, fixes billing mistakes and spots warning signs early, in one platform.

“

OpenByte transformed our support organisation. Agents resolve issues in minutes, not cycles. With full billing and payment context in every ticket, we’ve reduced churn and cut our OpEx materially.

Aaron Edwards

Systems & Technical Support Manager, Total Security

Stop losing subscribers you should keep

See how OpenByte recovers failed payments, fixes billing mistakes and spots warning signs early, in one platform.

“

OpenByte transformed our support organisation. Agents resolve issues in minutes, not cycles. With full billing and payment context in every ticket, we’ve reduced churn and cut our OpEx materially.

Aaron Edwards

Systems & Technical Support Manager, Total Security

Stop losing subscribers you should keep

See how OpenByte recovers failed payments, fixes billing mistakes and spots warning signs early, in one platform.

“

OpenByte transformed our support organisation. Agents resolve issues in minutes, not cycles. With full billing and payment context in every ticket, we’ve reduced churn and cut our OpEx materially.

Aaron Edwards

Systems & Technical Support Manager, Total Security