SaaS failed payment rate benchmarks.
What's normal. What's fixable.

What is a typical failed payment rate for SaaS?

The average failed payment rate for SaaS businesses is 5–15% of monthly billing attempts, according to Recurflux platform data across thousands of subscriptions. Consumer SaaS (direct-to-consumer apps, mobile subscriptions) see rates at the high end — 10–20%. B2B SaaS with longer-tenure customers and business credit cards see rates at the low end — 2–8%. The average across all segments is approximately 9–12%.

What percentage of failed payments are recoverable?

Industry benchmarks indicate 50–75% of failed subscription payments are recoverable with a properly configured dunning system. The remainder are hard declines — fraudulent cards, lost/stolen cards, permanently closed accounts — that cannot be retried regardless of approach. Of recoverable payments, 30–40% are recovered with default Stripe Smart Retries alone, 50–65% with a basic dunning email sequence added, and 65–75% with code-specific retry logic and a 5-step dunning sequence.

How much MRR is at risk from payment failures?

At a 10% monthly failure rate, $100K MRR has $10,000 at risk every month — $120,000 annually. Of that, approximately 60% is recoverable with a well-configured system, meaning $72,000 per year is recoverable. The cost of a payment recovery platform ($59–$159/month) generates 30–80x ROI on recovered revenue at this MRR level. The math becomes more extreme at higher MRR.

What is a good payment recovery rate for SaaS?

A recovery rate of 60–75% of failed payments is achievable with code-specific retry logic and a multi-step dunning sequence. Recovery rates below 40% indicate reliance on default processor behavior only. Recovery rates above 75% are possible but require additional layers like SMS dunning, card health monitoring to reduce failure volume, and LTV-weighted retry prioritization.

Which payment failure codes are most common in SaaS?

Across Stripe subscriptions, the most common failure codes by volume are: insufficient_funds (25–35% of failures), do_not_honor (15–25%), generic_decline / card_declined (10–20%), expired_card (8–15%), and try_again_later (5–10%). The top 5 codes account for approximately 80% of all payment failures. Each has a different optimal retry schedule and dunning message.

Does failed payment rate vary by billing cycle?

Yes. Monthly billing has higher failure rates than annual billing because cards are charged 12x more often per year, giving more opportunities for expiry, limit changes, and bank-side blocks. Consumer SaaS on monthly billing typically sees 12–18% failure rates. Annual billing reduces this to 3–6% per cycle, though the revenue at risk per failure is 12x higher.