Last month, 47 of your customers' credit cards were declined. You didn't notice most of them. Stripe's default retry logic caught some. The rest? They silently churned. Their subscriptions expired. They moved on.

This is involuntary churn — customers who didn't choose to leave, but left because their payment failed and nobody fixed it. It accounts for 20-40% of all subscriber churn, and it's almost entirely preventable.

Why Payments Fail

Understanding why cards get declined helps you design better recovery:

| Reason | Frequency | Recoverability | |--------|-----------|----------------| | Insufficient funds | 35-40% | High (retry in 3-5 days when paycheck hits) | | Expired card | 25-30% | High (customer updates card if prompted) | | Bank fraud block | 10-15% | Medium (customer contacts bank to whitelist) | | Card replaced (new number) | 10-15% | High (35% of customers forget to update) | | Hard decline (closed account) | 5-10% | Low (need new payment method entirely) | | Processing error | 5% | Very high (retry immediately succeeds) |

The key insight: 60-70% of failed payments are recoverable if you retry at the right time and prompt the customer correctly.

Stripe's Default Retry Logic (And Why It's Not Enough)

Stripe automatically retries failed payments on a schedule: after 1 day, 3 days, 5 days, and 7 days. This is better than nothing, but it has limitations:

Fixed schedule doesn't account for paycheck cycles (retrying on a Monday vs. Friday matters)
No customer notification built in — the customer doesn't know their payment failed
Generic retry — same logic for a $10 subscription and a $10,000 annual contract
Gives up after 4 attempts — some cards just need a longer window

Most businesses leave Stripe's defaults in place and lose 30-40% of recoverable revenue.

The Smart Recovery Stack

Layer 1: Intelligent Retry Timing

Instead of fixed intervals, retry based on:

Day of week: Retry on Wednesday-Friday when bank balances are typically higher (post-paycheck)
Time of day: Retry at 6-8 AM local time when daily spending hasn't depleted the balance
Historical success: If a customer's card has failed before, use the timing that previously succeeded
Amount sensitivity: For high-value charges, split into smaller amounts or retry at different times

Layer 2: Customer Communication Sequence

Most customers don't know their payment failed. A proactive communication sequence:

Day 0 (immediate): Email: "Hey [name], your payment of $X didn't go through. This usually happens when your card expires or your bank flags the charge. [Update payment method →]"

Day 3: Email + in-app notification: "Just a heads up — we'll retry your payment tomorrow. If your card info has changed, you can update it here to avoid any interruption."

Day 7: Personal email from the founder: "I noticed your payment hasn't gone through. Is everything okay? I'd hate for you to lose access to [specific feature they use most]. Happy to help sort this out."

Day 14: Final notice: "Your subscription will be paused in 3 days unless we can process your payment. Click here to update your card — takes 30 seconds."

Layer 3: Payment Method Backup

Card updater services: Stripe's Automatic Card Updater catches most card replacements (new expiration dates, new card numbers) without customer action
Backup payment methods: Prompt customers to add a second card at signup
ACH/bank transfer fallback: For high-value subscriptions, offer direct bank debit as a backup

The Revenue Math

Let's run the numbers for a real business:

Assumptions:

500 active subscribers
$200/month average subscription
5% monthly payment failure rate
25 failed payments per month

Without recovery automation:

Stripe default retries recover: ~40% (10 of 25)
15 customers lost per month
Revenue lost: 15 × $200 = $3,000/month = $36,000/year

With smart recovery:

Intelligent retry recovers: 50% (13 of 25)
Customer communication recovers: additional 20% (5 of 25)
Total recovered: 70% (18 of 25)
7 customers lost per month (down from 15)
Revenue lost: 7 × $200 = $1,400/month = $16,800/year
Revenue saved: $19,200/year

And that's just direct revenue. Each recovered customer continues paying for months or years. At an average 18-month customer lifetime, recovering 8 extra customers per month saves $28,800 in lifetime value — per month.

Setting Up Recovery in 30 Minutes

If You Use Stripe

Enable Smart Retries: Stripe Dashboard → Settings → Billing → Subscription and emails → Enable Smart Retries (Stripe's ML-based retry timing)
Turn on failed payment emails: Same settings page → Enable "Send emails when payments fail"
Set up a dunning schedule: Configure how long before you cancel: recommend 21-28 days (gives 3-4 retry windows)
Add a customer portal: Stripe Customer Portal lets customers update their payment method self-service. Add a link to your app and all dunning emails.

If You Want Full Automation

Connect Stripe to an intelligence platform like NuMoon that:

Monitors every payment event in real time
Applies smart retry timing beyond Stripe's defaults
Sends personalized recovery emails based on failure reason
Escalates high-value failures to your team
Tracks recovery rate and revenue saved over time
Connects to your other tools for full context

Frequently Asked Questions

How quickly should I retry a failed payment?

Don't retry immediately — the same condition that caused the failure is still present. Wait at least 24 hours for the first retry. For insufficient funds, wait 3-5 days (targeting after a paycheck cycle). For processing errors, retry after 4-6 hours.

Should I lock customers out when their payment fails?

No — at least not immediately. Give a 7-14 day grace period. Locking out a customer on day 1 of a payment failure guarantees they churn. Keeping them active while you recover the payment gives you the best chance of saving the relationship.

What's the difference between voluntary and involuntary churn?

Voluntary churn is a customer choosing to cancel. Involuntary churn is a customer losing access because their payment failed. Involuntary churn is 20-40% of total churn and is almost entirely preventable with the right recovery system.

How much does failed payment recovery software cost?

Stripe's built-in tools are free. Dedicated dunning tools range from $50-$500/month. NuMoon includes payment failure monitoring as part of its revenue intelligence module starting at $399/month — along with 15 other AI modules for business operations.

The Easiest Revenue You'll Ever Recover

Failed payment recovery is the highest-ROI automation any subscription business can implement. It requires no new customers, no marketing spend, and no product changes. You're just collecting money that customers already agreed to pay.

Set up smart retries. Send recovery emails. Offer self-service card updates. These three things recover 60-70% of failed payments and save tens of thousands per year.

Take the free health scan to estimate how much revenue you're losing to failed payments right now.