Stripe failed payment recovery: what Smart Retries does and what is left to you
Stripe will retry a failed card for you. It will not write the email that makes someone fix it. Here is how the pieces fit, and three emails to copy.
By the Churnly team. Updated November 21, 2026.
Why a payment fails
A failed subscription charge falls into two groups. A soft decline can succeed later: insufficient funds, a temporary bank block, a card limit hit this week. A hard decline will not: a lost or stolen card, a closed account, an invalid number. Stripe publishes the full list of decline codes, and the ones it treats as non-retryable are listed on its Smart Retries page.
The distinction decides what you do next. For a soft decline you wait and retry. For a hard decline, retrying is pointless until the customer gives you a new card.
What Smart Retries does
Smart Retries uses signals such as how many devices have presented the card recently and the time of day to choose when to retry. Stripe enables it by default on new accounts, set to up to 8 retries within 2 weeks. You can lengthen the window (one week up to two months), or turn Smart Retries off and write a custom schedule of up to three retries.
When retries run out, the subscription moves to the status you choose: canceled, unpaid, left past due, or paused. Pick this on purpose. Canceled is final in Stripe, since you cannot reactivate a canceled subscription. Past due or unpaid keeps the record, and the customer can come back by paying.
It also helps to know what Smart Retries leaves alone. Hard declines are skipped until a new payment method appears. India-issued cards, and payment methods such as Cash App Pay, are not retried. Stripe's own docs list them.
The emails Stripe sends
Under Revenue recovery, Stripe can email customers after each failed payment, ahead of an expiring card (one month before), and when a payment needs 3D Secure confirmation. The email carries your branding and links to a hosted page where the customer updates the payment method.
These are worth keeping on. They are also the same for every customer and every business, which is why people ignore them. A message that sounds like it comes from a person, and mentions what they pay for, gets more attention than a receipt that says "payment failed".
A timeline you can copy
- Day 0, first failure. Stripe's email goes out. Add a short note from you if the customer is a larger account.
- Day 3. A plain reminder with one link. Soft declines often resolve by themselves by now, so this reaches only the ones that did not.
- Day 7. A personal message that offers help: a different card, a pause, or a reply to you directly.
- Day 12 to 14. A final notice that says the date access ends, if your retry window is two weeks.
- After cancellation. One win-back message a week later, with a link that restores the subscription.
Match these days to your retry window, not the other way round. A final notice that arrives after the last retry has already run is just an apology.
Three emails to copy
First reminder
Subject: Your card did not go through
Hi {first name}, your latest payment for {product} did not go through. It is usually an expired card or a bank block, and it takes a minute to fix: {update link}. Reply if anything looks wrong and I will sort it out.
{your name}
Personal follow-up
Subject: Still having trouble with your payment?
Hi {first name}, I noticed your payment for {product} is still failing and did not want you to lose access. If you would rather use another card, or pause for a month, tell me and I will set it up. Otherwise this link takes you to the card page: {update link}.
{your name}
Final notice
Subject: Your {product} access ends on {date}
Hi {first name}, we have tried your card several times without luck. Unless the payment goes through by {date}, your subscription will be canceled and you will lose {one specific thing they use}. You can fix it here: {update link}. If you meant to leave, no action is needed, and thank you for being a customer.
{your name}
Keep card updates easy
Every extra click costs you customers. Link straight to the hosted update page or the customer portal, check that the page works on a phone, and do not ask people to sign in first if you can avoid it. Stripe's automatic card updates already fix many expired cards before a customer sees a problem, so a share of the failures you see are the cards it could not update.
How to tell if it is working
Track one number: of the invoices that failed on the first attempt, what share were eventually paid? The recovery analytics page shows it. When you add your own emails, compare a few weeks before and after, and watch for a seasonal bump (card replacement waves, holiday spend) that is not your doing. Vendors publish recovery rates, but their methods and customer mix differ, so use your own history as the baseline.
Where a tool helps
Doing all this by hand works for a few failures a week. Past that, you want something that notices each failure and drafts the message. Churnly does that for Stripe: it spots the declined card, drafts the email or WhatsApp message and a payment retry, and waits for your approval. Compare it with dedicated dunning tools in Churnly vs Churn Buster and Churnly vs Baremetrics Recover. To see what failed payments cost you, use the churn calculator.
Keep reading
- Reduce churn on StripeFailed payments, cancellations and win-back, in the order to fix them.
- A cancellation flow on StripeThe portal cancellation page, retention coupon and pause, and where they stop.
- Churn cost calculatorPut your own numbers in and see what churn costs in a year.
Keep the customers you already have.
Connect Stripe and Churnly starts watching for failed payments and cancellations. Every message waits for your approval.
Start at $19/mo