How to calculate your failed-payment rate (and what's normal)

Ask a SaaS founder their failed-payment rate and most can't answer, even though it's one of the most important numbers in a subscription business. It's the clearest measure of how much revenue you're losing to involuntary churn, the customers who lapse because a charge failed, not because they chose to leave. The good news: it's simple to calculate from data you already have. Here's how, and how to read the result.

The basic formula

Failed-payment rate is the share of recurring charges that fail: divide the number of failed payment attempts in a period by the total number of payment attempts in that period. If 1,000 renewal charges ran last month and 60 failed on the first attempt, that's a 6% first-attempt failure rate. You can calculate it per billing cycle or per month; the key is to be consistent about the window and about what counts as a failure.

First-attempt vs. final failure rate

There are really two rates worth knowing, and conflating them hides the story. The first-attempt failure rate counts charges that failed on the initial try, many of which recover on a retry. The final (net) failure rate counts charges that never succeeded after all retries, that's your true involuntary-churn number. The gap between the two tells you how much your processor's automatic retries are already recovering, and how much is still slipping through. Both matter: the first-attempt rate sizes the problem; the final rate sizes the loss.

How to pull it from your data

• Count total recurring charge attempts in your chosen window (from your processor's invoice/charge records).
• Count how many failed at least once (first-attempt rate) and how many never succeeded (final rate).
• Divide each by the total attempts. Track it over time, not just once.
• Segment by decline reason (expired card, insufficient funds, etc.) to see what's recoverable.

What's a 'normal' failed-payment rate?

There's no universal number, it varies by price point, customer type, and geography, but for subscription businesses a meaningful share of charges fail every cycle, and expired or reissued cards are the single most common cause. Rather than benchmark against an industry average, the useful comparison is your own rate over time and your first-attempt-vs-final gap. If your final failure rate is a nontrivial slice of your MRR and most of it traces to expired cards and declines, you have a large, recoverable pool, not a lost cause.

From the number to recovery

Calculating the rate is diagnosis; the treatment is prevention plus recovery. Warning customers before an expiring card fails shrinks the first-attempt rate; a clear recovery sequence after a failure shrinks the gap between first-attempt and final. Recoupe measures this against your real data and recovers the revenue your processor's retries leave behind, and it only counts a recovery when a customer acted on a Recoupe email, so the number you see is genuine reduction in your failed-payment loss.

Don't want to pull this by hand? A free 90-day audit calculates your failed-payment rate from your real Stripe data and shows exactly how much is recoverable.

Run a free audit