The month I found 7% of my MRR leaking to failed cards: an involuntary churn diary (2026)

Quick answer (2026): Involuntary churn is revenue you lose when a subscriber's card fails, not when they choose to cancel. In 2026, benchmarks from Baremetrics and others put it at roughly 20 to 40 percent of total SaaS churn, or close to 9 percent of MRR for the average subscription business. This is one founder's diary of finding a ~2.5% of MRR leak at $28K MRR, and recovering about two thirds of it with smart retries, pre-dunning emails, and a human-toned failed-payment sequence, not a new feature.

"I kept staring at the growth chart trying to figure out what I did wrong. It turned out I had not done anything wrong. Money was just leaking out of a hole I could not see."

That is the sentence the founder came back to twice while we talked through the strangest quarter of his bootstrapped SaaS. He runs a small B2B tool for operations teams, on plans between $49 and $99 a month, and he asked me to keep the product name private and change his first name. I will call him Diego. The numbers below are his real numbers, rounded and told the way he tracked them at the time.

This is a diary about the churn he could not see. Not the customers who quit, but the ones who stayed and paid him nothing anyway, because a card expired and no one told either of them.

The month the chart went flat and nothing looked wrong

Diego crossed roughly $28,000 in monthly recurring revenue in early 2026. Signups were steady. Demos were converting. Support was quiet. And yet for three months in a row, MRR barely moved. Up a few hundred dollars, down a few hundred, flat.

"My first instinct was that I had a retention problem," he said. He had written about a voluntary churn scare a while earlier, so his reflex was to look there again: onboarding, feature gaps, the usual retention checklist. He shipped two onboarding fixes and a requested feature. The chart stayed flat.

The thing about a flat MRR chart is that it hides two very different stories. New revenue coming in the front door can be exactly cancelled out by revenue quietly falling out the back. From the top line, growth and a leak look identical.

Splitting one churn number into two

The turn came when Diego stopped looking at churn as a single percentage. His dashboard showed a churn rate around 6 percent a month and he had always read that as "6 percent of customers decided to leave." It was not.

When he split it, roughly 40 percent of that churn was involuntary. These were not cancellations. They were failed payments: expired cards, insufficient funds, banks declining a renewal charge. The customer never opened a cancellation flow. They never sent an angry email. Their card simply did not go through, the subscription lapsed, and the dashboard counted them as churn exactly the same as someone who had rage-quit.

Once he pulled the failed-charge data out of Stripe and lined it up against his "churned" list, the overlap was uncomfortable. A large share of the people he had privately assumed were unhappy had never made a decision at all.

He is not an outlier. Baremetrics data suggests the average subscription business loses about 9 percent of monthly recurring revenue to failed payments, and cites Paddle research putting involuntary churn at 20 to 40 percent of total churn. A 2024 FlyCode explainer and a 2026 Slicker benchmark land in the same 20 to 40 percent range, with a healthy involuntary rate sitting under 1 percent of MRR per month.

You can watch founders discover this in real time. In one r/SaaS thread, an operator posted that about 12 percent of their MRR was failed payments, "not cancellations, not unhappy customers, just expired cards, insufficient funds, and retries that never happened." Others in the same corner of Reddit reported 18 and 23 percent of their churn turning out to be failed cards.

Diego's leak, in his own numbers

Here is the ledger he shared, labelled the way he now wishes he had labelled it a year earlier. All figures are self-reported and rounded.

"The part that stung," he said, "is that $1,350 a month was cheaper to get back than one new customer, and I had been ignoring it while paying to acquire strangers."

What he actually changed

None of the fixes were clever. That was the humbling part. In rough order of impact:

1. He turned on smarter retries instead of the default single attempt. Instead of one retry and a give-up, he moved to a scheduled sequence timed around paydays and card-cycle patterns. Stripe documents this as Smart Retries, which times attempts using historical success data rather than a fixed schedule. This alone caught a meaningful chunk, because a lot of "declines" are just a temporary insufficient-funds moment that clears two days later.

2. He added a pre-dunning email before the charge, not after. A short, plain note to customers whose card was about to expire that month, asking them to update it before the renewal. Catching an expiry before it fails is far easier than winning the customer back after their access has already been cut off.

3. He rewrote the failed-payment emails to sound like a human. The default "your payment failed" message read like a collections notice. He rewrote the sequence to sound like a person letting them know, with a one-click link to fix the card, and spaced the messages over several days instead of blasting them at once.

4. He put a visible update-card link inside the product. Not buried in billing settings. A gentle banner for accounts in a failed state, so an active daily user could fix it in the place they already were.

5. He emailed the people already marked "canceled." This was the emotional one. He wrote a genuinely apologetic note to accounts that had lapsed on a failed card, explaining what happened and offering to restore them. A real slice came straight back, which was the clearest proof of all that they had never wanted to leave.

What did not come back, and why chasing 100 percent is a trap

Diego is blunt that not all of it was recoverable. Hard declines, where a bank flatly refuses the card, and genuinely closed accounts do not come back no matter how good your emails are. He settled around a 65 percent recovery rate on the involuntary bucket and stopped pushing.

"There is a version of this where you turn into a debt collector and start harassing people, and you claw back another few percent and poison the relationship," he said. "I decided the ceiling for a small team is somewhere around two thirds, and the rest is the cost of doing business."

That matches what the vendors quietly admit too. Recovery tools report strong returns, but the honest framing is that involuntary churn is reducible, not eliminable. The goal is to stop it from being invisible, not to obsess over the last recoverable dollar.

The lesson he wanted on the record

The counter-consensus, in his words: most founders pour months into voluntary churn, the customers who choose to leave, because that story feels like a verdict on the product. Meanwhile the cheaper, faster win is sitting in the involuntary bucket, and those customers are not judging you at all. They already decided to stay. A bank just got in the way.

"I spent a quarter trying to build my way out of a flat chart," Diego said. "The fix was not a feature. It was five emails and a retry schedule I should have set up on day one."