Failed payments in SaaS: the revenue leak hiding in your churn numbers

The churn nobody chose

Most SaaS companies watch churn closely. Few separate the customers who decided to leave from the ones whose card simply failed.

That second group is involuntary churn, and it is bigger than it looks. Across subscription businesses, about 9% of monthly recurring revenue is at risk from failed payments every month (Baremetrics, 2026). On €100,000 MRR, that is roughly €9,000 a month put at risk without a single customer choosing to cancel.

The usual answer is: "Our payment provider retries it." That helps, but it is rarely enough. Default retry logic is built for the average merchant on a provider's network. Your customers, markets and contracts are not average.

You are not the only one: what the data shows

Failed payments are one of the most common, and least visible, revenue problems in SaaS. The 2026 numbers make the point:

• 9% of MRR at risk every month. Subscription businesses have around 9% of monthly recurring revenue at risk from failed payments (Baremetrics).
• Most failed payments are never won back. In a May 2026 sample of 119 US B2B SaaS companies, the median attempted recovery rate was just 12.7% (Baremetrics).
• Built-in retries are not closing the gap. 94% of those companies run their billing on Stripe, which retries failed payments automatically, and they still use a separate tool to recover them.
• International customers fail more often. Cross-border recurring card payments typically approve at 72–80%, against 85–90% for domestic ones (Airwallex).

If your churn feels stubborn, part of it may not be churn at all. It may be payments.

Why default retries leave money on the table

Payment providers handle the basics well. Stripe, for example, retries failed renewals with an AI model that learns from payments across its network, and new accounts get up to 8 retries within 2 weeks by default (Stripe docs). The problem is not that defaults are bad. It is what they cannot know:

• One policy for every customer. Unless someone sets up separate rules, a €20 monthly plan and a €20,000 annual contract get the same treatment.
• Network averages, not your data. The model learns from millions of merchants, not from your customers' paydays, countries or card mix.
• Retries are not recovery. A retry decides when to try again. It does not decide who to contact, how, or what else to offer.
• Nobody owns the number. Failed payments sit between product, finance and engineering, so no one watches them.

The result: revenue leaks quietly every month, and it shows up in your churn report as customers who "left".

Signs your SaaS is leaking revenue

You probably have a failed payment problem if:

• you cannot say what share of your churn is involuntary
• your retry settings are still your provider's defaults
• payment failure emails go out from a no-reply address
• nobody has looked at your decline codes in the last six months
• a growing share of your customers pay with foreign cards
• your churn has not improved, whatever you change in the product

If two or more sound familiar, it is worth a closer look.

How Leakproof Payments can help

Leakproof Payments is a payments consulting practice for SaaS companies. We find where your recurring revenue leaks, using your own payment data, and fix it on the stack you already run, whether that is Stripe, Adyen, Chargebee, Recurly or Paddle. You get a clear number for what you are losing, and a plan to win it back.

Are failed payments eating into your MRR? Contact Leakproof Payments to find out how much you could recover.