How to Recover Failed Payments in Stripe: Beyond Smart Retries

Stripe's Payment Recovery Stack

Stripe gives you several tools to handle failed payments. Understanding what's available — and what's missing — is the first step to maximizing recovery.

What Stripe Provides Out of the Box

1. Smart Retries — ML-powered retry timing (included with Stripe Billing)
2. Automatic card updates — updates stored card numbers when banks reissue cards
3. Configurable retry schedule — customize how many times and when to retry
4. Basic dunning emails — simple notification emails when payments fail
5. Webhooks — real-time events for invoice.payment_failed, customer.subscription.updated, etc.

What Stripe Doesn't Provide

1. Multi-step email sequences — you get one email, not a 4-6 email dunning campaign
2. Save offers — no built-in way to offer discounts, pauses, or downgrades
3. Pre-dunning alerts — no card expiration warnings
4. Recovery analytics — limited visibility into recovery rates and trends
5. Decline code-specific routing — Smart Retries doesn't differentiate strategies by decline type

Step 1: Configure Stripe's Built-in Tools

Before building anything custom, optimize Stripe's defaults.

Enable Smart Retries

In your Stripe Dashboard, go to Settings → Billing → Subscription and emails → Manage failed payments.

• Enable Smart Retries (Stripe's ML determines optimal retry times)
• Set your retry window to 21 days (this gives maximum time for recovery)
• Configure the number of retries to the maximum allowed

Enable Automatic Card Updates

Go to Settings → Billing → Automatic card updates.

This feature uses the card networks' Account Updater service to automatically update stored card numbers when banks reissue cards. It reduces payment failures by 25-35% and costs $0.25 per successful update — well worth it.

Configure Dunning Emails

Go to Settings → Billing → Subscription and emails → Email customers when payment fails.

Enable the default email and customize the content. It's basic, but better than nothing. Include:

• Your brand name and logo
• Clear explanation of the issue
• A link to update their payment method (Stripe provides this automatically)

Step 2: Set Up Webhook Listeners

To go beyond Stripe's defaults, you need to listen to payment events and take action. Here are the key webhooks:

Critical Webhooks

| Event | When It Fires | Your Action | |-------|--------------|-------------| | invoice.payment_failed | Payment attempt fails | Log failure, trigger dunning email | | invoice.paid | Payment succeeds (including retries) | Stop dunning sequence | | customer.subscription.updated | Subscription status changes | Track past_due → canceled | | customer.source.expiring | Card expiring soon | Send pre-dunning alert | | customer.subscription.deleted | Subscription canceled | Trigger win-back sequence |

Webhook Implementation

Set up a webhook endpoint in your application:

POST /api/webhooks/stripe

For each invoice.payment_failed event, extract:

• Customer ID — who needs to be contacted
• Invoice ID — which payment failed
• Attempt count — is this the first failure or a retry failure?
• Last payment error code — why did it fail? (insufficient_funds, expired_card, etc.)
• Amount — how much was the charge?

Use the decline code to determine your response:

• Soft declines (insufficient_funds, processing_error): Schedule retry + send informational email
• Hard declines (expired_card, invalid_number): Don't retry, send urgent email asking customer to update card

Step 3: Build a Customer Update Portal

Stripe provides a hosted payment method update page via the Customer Portal. To set this up:

1. Go to Settings → Billing → Customer portal
2. Enable the portal
3. Configure which actions customers can take (update payment method, manage subscriptions)
4. Generate portal links to include in your dunning emails

The portal URL can be generated via the API:

POST /v1/billing_portal/sessions

Include this link as your primary CTA in every dunning email. The fewer clicks it takes to update a payment method, the higher your recovery rate.

Step 4: Build a Dunning Email Sequence

Stripe's single email isn't enough. Build a multi-step sequence triggered by webhooks:

| Email | Trigger | Timing | |-------|---------|--------| | 1. Friendly notice | invoice.payment_failed (attempt 1) | Immediately | | 2. Reminder | invoice.payment_failed (attempt 2) | Day 3-4 | | 3. Value reminder | Scheduled | Day 7 | | 4. Save offer | Scheduled | Day 12 | | 5. Final notice | Scheduled | Day 14 (48h before cancellation) |

Use a transactional email service (Resend, Postmark, SendGrid) — not your marketing email tool. Transactional emails have higher deliverability and don't conflict with marketing sends.

Key implementation details:

• Stop the sequence immediately when invoice.paid fires
• Personalize with customer name, plan, amount, and card last 4 digits
• Track opens and clicks to identify customers who see the email but don't act
• Include both HTML and plain text versions

See our dunning email templates and payment failure templates for copy-paste examples.

Step 5: Implement Save Offers

When a customer hasn't responded to emails and cancellation is approaching, offer alternatives:

Option 1: Discount

Create a Stripe Coupon and apply it to the subscription:

POST /v1/coupons
  percent_off=20
  duration=repeating
  duration_in_months=3

Option 2: Pause

Update the subscription with pause_collection:

POST /v1/subscriptions/{sub_id}
  pause_collection[behavior]=void
  pause_collection[resumes_at]={timestamp}

Option 3: Downgrade

Change the subscription to a cheaper price:

POST /v1/subscriptions/{sub_id}
  items[0][id]={item_id}
  items[0][price]={cheaper_price_id}

Present these options in your Day 12 email with clear CTAs for each.

Step 6: Automate Win-Back

After a subscription is canceled (customer.subscription.deleted webhook), start a win-back sequence:

• Day 3: "Your data is safe, reactivate anytime"
• Day 7: Reactivation discount offer
• Day 14: Reminder with feature highlights
• Day 30: Final email before data cleanup

Win-back campaigns typically recover 5-15% of involuntarily churned customers.

Step 7: Monitor Recovery Metrics

Track these metrics weekly:

1. Recovery rate — failed payments recovered / total failed payments
2. Recovery by decline code — which codes have the best/worst recovery
3. Recovery by retry attempt — which attempt number succeeds most
4. Email engagement — open and click rates by email position
5. Save offer acceptance — which offers resonate most
6. Time to recovery — average days from failure to recovery

Target Benchmarks

| Metric | Good | Great | |--------|------|-------| | Overall recovery rate | 65% | 80%+ | | Soft decline recovery | 75% | 90%+ | | Hard decline recovery | 40% | 60%+ | | Dunning email open rate | 45% | 60%+ | | Save offer acceptance | 10% | 25%+ |

The Build vs. Buy Decision

Building everything above takes significant engineering time:

• Webhook handling + event processing: 2-3 days
• Email sequence logic + templates: 3-5 days
• Save offer implementation: 2-3 days
• Analytics dashboard: 3-5 days
• Testing + edge cases: 2-3 days
• Total: 2-4 weeks of engineering time

Plus ongoing maintenance: handling Stripe API changes, email deliverability issues, retry logic bugs, and optimization.

Dedicated dunning software handles all of this for $30-100/month. For most SaaS teams, buying saves weeks of engineering time and delivers better results out of the box.

Key Takeaways

1. Start with Stripe's built-in tools — enable Smart Retries, auto card updates, and basic dunning emails
2. Add webhook listeners — invoice.payment_failed and invoice.paid are essential
3. Build a 5-email dunning sequence — one email isn't enough
4. Route by decline code — soft declines get retried, hard declines get emails
5. Offer save alternatives — discounts, pauses, and downgrades retain customers
6. Track recovery metrics — target 70-85% overall recovery rate
7. Consider buying vs. building — dunning software saves 2-4 weeks of engineering and typically delivers higher recovery rates