Free Report
2026 Data
No Signup Required
Covers
· 5 payment processors
· MRR bracket breakdown
· Recovery rate benchmarks
· India-specific data
· Involuntary churn split
Free Report · 2026 Data · No Signup
7.9% of subscription payments fail every month. Most SaaS companies recover less than half. This is the breakdown nobody else publishes — by processor, MRR bracket, and geography.
7.9%
average monthly payment failure rate across SaaS in 2026
42%
of all failures caused by expired cards — fully preventable before they happen
$1.3B
in recoverable SaaS revenue lost to involuntary churn annually
Key findings
Key findings
The median SaaS company recovers 30–45% of failed payments using processor-native retries only. Top-quartile companies recover 65–75%. The gap is not retry timing — it's the number of recovery layers running simultaneously.
Expired cards cause 42% of all subscription payment failures. Every one of these is preventable with card health monitoring 30+ days before renewal. Most SaaS companies never send a pre-expiry email.
Indian SaaS on Razorpay faces 8–15% payment failure rates — versus 3–6% for US SaaS on Stripe. RBI e-mandate authentication pushes failure rates to 20–40% on card payments above ₹5,000. No other published benchmark covers this.
Mobile app subscriptions on RevenueCat: 72% of annual subscribers cancelled in Year 1 in 2026, up from 56% in 2025. Once they cancel, annual reactivation sits at 5%.
20–40% of what most SaaS analytics tools classify as voluntary churn is a billing failure the customer never initiated. Most founders are fixing onboarding when the leak is in the billing layer.
By processor
By processor
Most published benchmarks assume Stripe. If you're on Razorpay, Paddle, RevenueCat, or Cashfree — the failure profile is different. Here's what actually fails, by processor.
Best card updater network; Smart Retries native; largest partner bank coverage
Merchant of Record model — Paddle absorbs more failure risk before it reaches you
RBI e-mandate friction; UPI Autopay mandate success at 30–50%; ₹5k auth threshold
Similar RBI compliance burden; fewer card updater partnerships than Stripe
App Store/Play Store own billing cycle; grace period logic varies by store
India — what nobody else benchmarks
Payments above ₹5,000 on Indian cards require additional authentication under RBI e-mandate rules. This single regulation pushes failure rates to 20–40% in affected subscription categories. UPI Autopay reduces friction but initial mandate success rates sit at 30–50% — meaning nearly half of customers who try to subscribe via UPI fail before the first payment. No other published benchmark covers this because no other recovery tool natively supports Razorpay.
Recovery rates
Recovery rates
The difference between median (30–45%) and top-quartile (65–75%) recovery isn't a single better tactic. It's all five layers running at the same time.
| Approach | Recovery rate | What it misses |
|---|---|---|
| Processor-native only (e.g. Stripe Smart Retry) | 20–35% | No emails, no card updater, fixed schedule regardless of failure code |
| Smart retry + dunning emails | 40–55% | No card health monitoring, no pre-expiry outreach |
| Smart retry + dunning + card updater | 55–65% | No SMS, no per-decline-code retry logic |
| All 5 layers simultaneously | 65–75% | — |
Source: Recurly Subscription Economy Index, Baremetrics, ProfitWell — aggregated 2026. Recovery rates measured within 30 days of initial failure.
By MRR bracket
By MRR bracket
The percentage looks small. The dollar amount doesn't. Based on 7.9% failure rate and 60% recoverable with proper tooling.
| MRR | Fails/month | Recoverable/month | Annual recovery gap |
|---|---|---|---|
| $10k | $790 | $474 | $5,688 |
| $30k | $2,370 | $1,422 | $17,064 |
| $50k | $3,950 | $2,370 | $28,440 |
| $80k | $6,320 | $3,792 | $45,504 |
| $100k | $7,900 | $4,740 | $56,880 |
| $200k | $15,800 | $9,480 | $113,760 |
At $50k MRR, $2,370/month is recoverable with the right tooling. That's $28,440/year — revenue already earned, already billed, just lost before it landed in the bank.
India
India-specific · Razorpay · UPI · e-Mandate
Indian SaaS founders on Razorpay, Cashfree, and PayU face payment failure dynamics that US-focused benchmark reports don't cover at all — because none of them support these processors.
RBI e-Mandate Authentication
20–40%
Card payments above ₹5,000 require additional two-factor authentication at mandate creation. This single regulation pushes failure rates well above the global average in affected subscription categories.
UPI Autopay Mandate Creation
30–50%
UPI Autopay is growing but initial mandate success rates sit at 30–50%. Nearly half of customers who try to subscribe via UPI fail before the first payment is taken. The transaction success rate is high; onboarding is not.
Cross-Border Transactions
1.5–2×
Indian founders selling globally face 1.5–2× the domestic failure rate on international card transactions, with fewer card updater network partners available than US-native processors.
An Indian SaaS at ₹40L MRR ($50k) isn't losing 3–6% like a US Stripe business. They're losing 8–15% before any recovery attempt. The recovery gap is wider — and historically, the tooling available to fix it has been nearly nonexistent.
The diagnosis
The diagnosis
20–40% of what your analytics dashboard shows as churned customers is a customer who never chose to leave. Their card expired. A bank declined. Nobody caught it in time. They disappeared from your subscriber list. Your MRR chart recorded it as churn. You responded by fixing onboarding.
Most SaaS founders spend months optimising the wrong variable. Not because they're wrong about the product — but because they've never separated the billing failure rate from the actual retention problem. They're diagnosing with incomplete data.
Three questions that reveal if billing is your problem
What is your current monthly payment failure rate? If you don't know this number, that's the finding.
What percentage of your churn is involuntary vs voluntary? Separate these before changing anything else in the product.
What is your current recovery rate vs the 65–75% that top-quartile companies achieve?
Split your churn right now — see how much is billing vs product:
Splitter
On Stripe, roughly 30% of subscription churn is involuntary — payment failures, not product decisions. At $50k MRR, that's $450/mo that's fixable without touching the product.
Payment processor
Stripe accounts: ~30% of subscription churn is billing failures, not cancellations
Total churn / mo
$2k
3% of MRR
Involuntary / mo
$450
payment failures
Voluntary / mo
$1k
chose to cancel
Saveable / year
$3k
at up to 60% recovery
12-month MRR projection
with vs without involuntary churn recovery
Involuntary churn benchmarks are per-processor averages. Connect your account to measure your actual split.
Connects to Stripe in under 5 minutes. Starts recovering the same day.
Common questions
Common questions
The average transaction failure rate across SaaS is 7.9%. B2B SaaS on corporate cards typically sees 4–6%. B2C on consumer and prepaid cards runs 8–15%. Indian SaaS on Razorpay faces 8–15% due to RBI e-mandate compliance requirements — significantly higher than the global average.
Companies using only processor-native retries recover 20–35%. Adding dunning email sequences brings this to 40–55%. Full-stack recovery — smart retry with code-specific logic, card health monitoring, dunning email, SMS, and cancellation interception — achieves 65–75%. The industry median sits at 30–45%.
Expired cards cause 42% of all subscription payment failures — fully preventable with pre-expiry outreach 30+ days before renewal. Insufficient funds account for 30–35%. Card issuer declines (do_not_honor, generic_decline) make up 15–20%. Network and technical errors account for the remainder.
Stripe sees 3–6% failure rates with access to card updater networks and built-in Smart Retries. Razorpay sees 8–15% due to RBI e-mandate requirements and UPI Autopay mandate creation success rates of 30–50%. The gap is structural — Indian payment infrastructure has different compliance overhead that standard dunning tools are not built to handle.
At $50k MRR with a 7.9% failure rate, approximately $3,950 fails monthly. At a 60% recovery rate, $2,370 per month is recoverable — $28,440 per year. Revenue already earned and lost before it landed.
Research across subscription businesses shows 20–40% of total churn is involuntary — caused by payment failures, not deliberate cancellations. For Indian SaaS on Razorpay, this share is higher due to structurally elevated failure rates. Most SaaS analytics tools do not separate these categories, making this the most common misdiagnosis in churn analysis.
According to RevenueCat's 2026 State of Subscription Apps report, 72% of annual subscribers cancelled in Year 1 — up from 56% in 2025. Monthly first renewal rates range from 42–61% by category. Annual reactivation after cancellation sits at just 5%.
The median recovery rate is 30–45% — what most companies achieve with default processor tools. A good target is 55–65%. Top-quartile (65–75%) requires dedicated tooling: code-specific retry logic, multi-step dunning, card health monitoring, and cancellation interception running simultaneously.
Involuntary churn is subscription cancellation caused by payment failure — not a deliberate customer decision. The card expired, the bank declined, or authentication failed. The customer still wanted the product. Involuntary churn accounts for 20–40% of total SaaS churn and is fixable with dedicated billing infrastructure.
Dunning is the process of automatically retrying failed subscription payments and notifying customers to update their payment details. Effective dunning combines code-specific retry timing, multi-step email sequences, SMS, and a card update portal. Companies with dedicated dunning recover 55–75% of failed payments versus 20–35% with processor defaults.
UPI Autopay mandate creation success rates in India sit at 30–50%, meaning nearly half of customers who attempt to set up recurring payments via UPI fail before the first payment is taken. Once a mandate is created, transaction success rates are higher — but the onboarding failure rate is a significant revenue leak point for Indian SaaS.
RBI e-mandate regulations require additional two-factor authentication for card payments above ₹5,000. For SaaS products priced above this threshold, this single regulation pushes payment failure rates to 20–40% at mandate creation — far above the global average of 7.9%. UPI Autopay is the RBI-approved alternative but carries its own 30–50% mandate creation failure rate.
Stripe Smart Retry uses machine learning to retry failed payments on an optimised schedule but applies the same timing logic regardless of why the payment failed. Dedicated dunning adds code-specific retry windows (insufficient_funds waits for bank cycle; expired_card skips retries and fires a card update email), multi-step email sequences, SMS, card health monitoring, and cancellation interception. Stripe Smart Retry recovers 20–35% of failures; full-stack dedicated dunning recovers 65–75%.
Paddle sees 3–6% monthly failure rates — similar to Stripe. As a Merchant of Record, Paddle absorbs more payment failure risk before it reaches the SaaS business, and operates its own fraud and decline handling. This makes Paddle failure rates structurally lower than Razorpay or Cashfree for the same customer segment.
Related free tools
See your numbers
Connect your processor and Recurflux pulls 90 days of failed charge data in under 60 seconds. You'll see your exact failure rate, your current recovery rate, and how much is still in the recovery window — before paying anything.
Stripe · Paddle · Razorpay · Cashfree · RevenueCat · 5 minutes to connect