Failed renewals have different causes: temporary funding problems, expired cards or hard declines. Recovery depends on your customers, payment methods and follow-up. Start with a measured baseline, then coordinate Stripe retries and customer communication.
Before you start
Access to Stripe revenue recovery and customer-email settings.
Failed-invoice history with a defined currency basis and recovery window.
An authenticated billing route and an agreed customer access policy.
Scope
Recovery operations and measurement, not guaranteed recovery rates. Configure and test changes in a sandbox before applying them to live billing.
Step 1
Audit your current recovery rate
Choose a cohort of failed invoices and a fixed recovery window, for example 14 days. Use cohorts old enough to have completed that window. Measure both invoice count and recovered amount, separating currencies or converting consistently. Keep the same definitions before and after any change.
Smart Retries is usually already on. Stripe's recommended default is 8 tries within 2 weeks, and the schedule is configurable. In the Stripe Dashboard, open Billing → Revenue recovery → Retries to see what your account uses. Hard declines require a new payment method before collection can resume. attempt_count may increase even when a scheduled retry does not execute a charge, so inspect payment outcomes too.
Coordinate automated and manual retries so collection attempts don't overlap.
Step 3
Understand automatic card updates
Automatic card updates are enabled by default for saved cards when the issuer supplies updated details. Coverage depends on the card and issuer; supported cards cannot be predicted in advance. An update can help with an expired or replaced card, but it does not resolve every decline.
Watch out
Do not look for a separate toggle in Stripe Billing. Check your contract and current Stripe terms for any per-update fee, and offer customers a secure way to update their payment method.
Step 4
Coordinate payment recovery emails
An illustrative three-email sequence
Day 0
Failure
Soft reminder
Day 4
Email #2
“Service may pause”
Day 10
Email #3
Last call
Day 15
Retries exhausted
Apply your policy
Coordinate reminders with Stripe Smart Retries
Configurable schedule; hard declines need a new payment method
Illustrative reminder dates, not Stripe defaults. Match your retry and access policy; stop on payment.
Review Stripe's email settings before adding your own reminders, so customers don't receive duplicates. Use the three dunning email templates below as a starting point and adjust their dates to your retry window and access policy. Use a monitored reply address, state any service interruption accurately and stop reminders as soon as payment succeeds.
Email 1 · Day 0 · Soft reminder
Subject: Your payment didn't go through
Hi {{first_name}}, we couldn't charge your card for your {{plan}} subscription. We'll retry automatically in the next few days, but if your card has changed or expired, please update it.
Button: Update payment details
Email 2 · Day 4 · Service may pause
Subject: Action needed: your {{plan}} access may pause
Hi {{first_name}}, we still haven't been able to collect your {{amount}} payment. To avoid any interruption, please update your payment method before {{date}}. Reply to this email if you need a hand.
Button: Update payment details
Email 3 · Day 10 · Last call
Subject: Last reminder about your {{plan}} subscription
Hi {{first_name}}, this is our last reminder: your {{amount}} payment is still unpaid. If it isn't settled, your subscription will be {{paused/cancelled}} on {{date}}. It only takes a minute to fix.
Button: Update payment details
Measure deliverability and outcomes; more emails don't automatically mean more recovery.
Tip
Placeholders in {{double braces}} come from your own customer data. Point every button at your billing page (step 5), never at a generated portal session URL, and set {{paused/cancelled}} in email 3 to what your policy actually does (step 6).
Step 5
Give customers a secure path to the portal
Link emails to an authenticated billing route in your app, for example /billing. After authentication and a server-side ownership check, create a fresh Stripe customer portal session and redirect to it. Never trust a browser-supplied customer ID or bypass authentication to shorten the flow.
import Stripe from "stripe";
const stripe = new Stripe(process.env.STRIPE_SECRET_KEY!);
// Emails link to /billing, never to a portal session URL.
app.get("/billing", requireLogin, async (req, res) => {
// req.user comes from your session, never from the query string or body.
const account = await db.accounts.findById(req.user.accountId);
if (!account?.stripeCustomerId) return res.redirect("/pricing");
const session = await stripe.billingPortal.sessions.create({
customer: account.stripeCustomerId, // loaded from your database
// Not /billing, or the customer loops back into the portal.
return_url: `${process.env.APP_URL}/settings/billing`,
});
res.redirect(303, session.url);
});
Express + TypeScript sketch: requireLogin and db stand for your own authentication middleware and data layer. The Stripe customer ID is read from your database for the signed-in account, so a customer can only open their own portal.
Tip
A generated portal session expires after 5 minutes if unused, or within 1 hour of the latest activity once used: it is not a persistent email link. Alternatively, use Stripe's reusable portal login link, which requires Stripe email authentication.
Step 6
Define your final cancellation policy
Choose what happens once retries are exhausted: keep the subscription recoverable, mark it unpaid or cancel it, according to your terms and Stripe configuration. Align the retry window from step 2, your access policy and your customer notices. The retry window is not a cancellation deadline.
Step 7
Track recovery as a KPI
Track recovery as one number, reviewed next to your recurring revenue at risk:
Recovery rate = recovered invoice amount ÷ failed invoice amount, same cohort and window
Invoice amounts and MRR are different measures: do not label one as the other. Investigate changes in decline reasons, delivery, payment methods and cohort maturity before attributing a change to your reminders.
A reliable recovery process combines measured outcomes, clear customer messages and controlled payment attempts. Improve it against your own baseline.
Estimate from your own mature failure cohorts, recoverable balances and costs. Recovered invoice cash is not necessarily recovered MRR: taxes, billing intervals and one-off items can differ. No recovery rate or return on engineering effort is guaranteed.
Should I send dunning emails from Stripe or my own ESP?+
Either can fit. Compare branding, delivery monitoring, implementation cost and the controls you need. Coordinate both systems to avoid duplicate reminders, and stop your own sequence on successful payment.
How many times does Stripe retry a failed payment?+
Stripe's recommended default is 8 tries within 2 weeks, with Smart Retries choosing when to try. You can change the number of tries and the window in Billing → Revenue recovery → Retries. attempt_count can rise without a charge being made, so check payment outcomes rather than the counter.
What happens when Stripe's retries are exhausted?+
Stripe applies the action set in your subscription settings: cancel the subscription, mark it unpaid or leave it past due. The invoice can still be paid afterwards, for example once the customer updates their card. Choose that action deliberately (step 6).
Does Stripe send failed-payment emails automatically?+
Only if you turn them on in Stripe Billing's customer email settings. Stripe can then tell the customer a payment failed and send them to a Stripe-hosted page to update their card. Check these settings before adding your own sequence, so customers don't receive duplicates.
Do Smart Retries fix hard declines?+
No. Retrying the same card does not fix a hard decline, such as a closed or stolen card: the customer has to add a new payment method. That is why a secure way to update it (step 5) matters.
How do I send customers a link to update their card?+
Email a link to a billing page in your app, such as /billing. After sign-in, your server creates a fresh Stripe customer portal session and redirects to it (code in step 5). Don't email a portal session URL: it expires. Stripe also offers a reusable portal login link that authenticates the customer by email.