If you're running a SaaS on Stripe, you probably assume Stripe handles failed payments for you. And technically, it does. Stripe has a built-in feature called Smart Retries that automatically retries failed charges.
So why are you still losing 5-10% of your MRR every month?
Because Stripe's retries are designed to work at scale across millions of businesses. They're not optimized for your specific situation. Here's what's actually happening behind the scenes and why it's not enough.
How Stripe's Smart Retries Work
When a payment fails, Stripe automatically schedules retries over a period of time (usually up to 4 weeks, depending on your settings). Stripe uses machine learning across their entire network to pick retry times that have the best chance of succeeding.
Sounds great in theory. In practice, there are real limitations.
Problem 1: Stripe Doesn't Know Why the Payment Really Failed
When a bank declines a charge, it sends back a decline code. But these codes are often vague or misleading. A "generic_decline" could mean a dozen different things. Stripe's retry logic treats many of these the same way.
But the optimal strategy is completely different depending on the actual reason:
- Insufficient funds: Retry on the 1st or 15th of the month (payday for most people). Retrying the next day is usually pointless.
- Expired card: Don't retry at all. The card is dead. You need to contact the customer and ask them to update their payment method.
- Rate limit / processing error: Retry within hours. It's a temporary technical issue.
- Do not honor: Often a fraud flag. Retrying aggressively can get your Stripe account flagged.
A smart retry system classifies the decline reason and applies a different strategy for each. Stripe's retries don't go this deep for individual accounts.
Smart retry timing based on decline classification can double your recovery rate
Problem 2: Retries Alone Don't Recover Expired Cards
This is the big one. A significant portion of failed payments (roughly 25-40%) come from expired credit cards. No amount of retrying will fix an expired card. You need to reach the customer and ask them to update their payment method.
Stripe can send a basic email asking customers to update their card. But it's a single, generic email with low urgency. Compare that to a well-crafted dunning sequence: multiple emails over several days, with increasing urgency, clear CTAs, and personalized messaging. The difference in recovery rates is massive.
Problem 3: Email Open Rates Are Declining
Even if you set up a dunning email sequence, you're fighting an uphill battle. Email open rates for transactional messages have been declining year over year:
- Average open rate for dunning emails: 20-30%
- Percentage that lands in spam or promotions tab: 30-50%
- Customers who actually click and update their card: 5-15%
Your customer's payment failed, you sent a recovery email, and there's a good chance they never saw it.
This is why channels like WhatsApp (with 90%+ open rates) are becoming relevant for payment recovery. When someone gets a WhatsApp message, they see it. Period.
Problem 4: No Visibility Into What's Happening
Stripe gives you basic metrics on retries, but there's no dedicated dashboard showing:
- How much revenue is at risk right now
- Which customers have failing payments and why
- What's been recovered vs. what's been lost
- Which retry strategy is working best
Without this data, you're flying blind. You don't know if Stripe recovered 20% or 60% of your failed payments last month. You just see the net MRR change and attribute everything to "churn."
The Real Recovery Rate Numbers
| Strategy | Recovery Rate |
|---|---|
| Stripe Smart Retries only | ~38% |
| Stripe + basic dunning emails | ~50-55% |
| Smart retries + dunning sequence + WhatsApp | ~65-75% |
The gap between "Stripe default" and "fully optimized" is 30-35 percentage points. On $10,000 MRR with a 9% failure rate, that's the difference between recovering $342/month and $600+/month.
What You Should Do
If you're under $3k MRR, Stripe's default retries are probably fine. The dollar amount you're losing isn't worth the time investment yet.
If you're between $3k-$50k MRR, you're in the range where failed payment recovery has real ROI but enterprise tools ($250+/mo) don't make financial sense. This is where lightweight dunning tools that integrate with Stripe pay for themselves many times over.
If you're above $50k MRR, you should definitely have a dedicated recovery solution in place. At this scale, every percentage point of recovery rate is worth thousands per year.
Whatever your MRR, start by checking your actual failed payment data. We wrote a step-by-step guide on how to check failed payments in your Stripe dashboard.