Stripe dunning smart retries are the quiet machinery that win back money you already earned and nearly lost. Here is how it goes. A card gets declined. A subscription payment fails at 2am. The customer has no idea. And instead of that account silently churning, Stripe waits, then tries again at a smarter moment. Most founders never see any of it happen. That is sort of the point. But understand what is going on under the hood and you can recover more, lose fewer customers, and stop bleeding revenue you never should have lost.

Start with the outcome, because the outcome is the whole reason this feature exists. Money back in your account. Zero effort from you.
Every subscription business has a leak. It is called involuntary churn, and it has nothing to do with customers who wanted to leave. Their card expired. The bank flagged the charge as unusual. There were insufficient funds on a Tuesday that would have cleared by Friday. These people still want your product. The payment just did not go through this time.
That is the job of stripe dunning smart retries. When a recurring charge fails, Stripe does not shrug and give up on the first attempt. It retries on a schedule, and with Smart Retries switched on, it picks the timing with a machine learning model instead of a fixed calendar. Stripe says businesses recover around 55 percent of failed payments on average through its revenue recovery tools. Fair warning: independent data from B2C accounts runs a good bit lower, closer to 25 to 35 percent depending on your customer base. Even so, a conservative recovery rate turns a real dent in monthly revenue into a rounding error.
The short version? Failed payment recovery is not a nice-to-have. For anything with recurring billing, it is one of the highest-return settings in your whole Stripe account. And most people never touch it.

Type your business name and see where you rank against your competitors. Free, no signup.
Trophy Jar asks every customer for a review automatically, from $9 a month.Start now
Here is what makes Smart Retries different from a dumb cron job.
Stripe dunning smart retries lean on a machine learning model trained on billions of transactions across the Stripe network. The model weighs more than 500 attributes per attempt. Stripe sorts them into a handful of buckets: who the customer is and how their card usually behaves, what kind of business you run, the full history of that specific card including the exact decline code it just threw, the product mix you bill on, and timing signals like the hour of the day, the day of the week, and the week of the month.
That last bucket is the interesting one. A fixed schedule retries every failed card at, say, 9am three days later. The model does not think in fixed schedules. It has seen enough of the network to know that some payments clear far more reliably at certain moments, often right around when balances tend to refresh. A human would never spot the pattern. A model trained on the whole network already has.
The practical result is that failed payment recovery gets timed around real bank behavior instead of your billing calendar. You do not configure any of that logic yourself. You turn it on, pick a window, and let the model do the rest.
Turning this on takes about two minutes in the dashboard.
Go to Billing, then Revenue recovery, then Retries. That is where you enable stripe dunning smart retries and choose a recovery window: 1 week, 2 weeks, 3 weeks, 1 month, or 2 months. Within whatever window you pick, the model schedules multiple attempts. Stripe’s recommended default is 8 tries within 2 weeks, which is a sane starting point for most subscription businesses.
Want to control the exact cadence yourself? Switch Smart Retries off and build a custom schedule instead. On Stripe’s base billing tier a custom schedule lets you set up to three retries, each spaced a set number of days apart. You trade the AI timing for full predictability. For most teams the smart option wins. But if your customers are highly seasonal, or you already run a dunning rhythm that works, the manual route is right there.
While you are in Revenue recovery, this is also where you set up your dunning emails, the messages that tell a customer their payment failed and nudge them to update their card. Retries recover the silent wins. Emails recover the customers who actually need to do something. Switch on both. For a deeper look at how the whole billing connection fits together, see our Stripe integration overview.
No retry engine is magic. It helps to know the edges.
Stripe dunning smart retries cannot recover a hard decline on their own. When a bank returns a hard decline code, a lost card, a stolen card, a closed account, a card flagged for fraud, Stripe will not keep hammering a dead card. The retry stays scheduled and the attempt count keeps ticking up, but nothing actually fires until a new payment method shows up on the customer. So for hard declines, recovery hangs entirely on the customer coming back to update their card. That is a communication problem, not a retry problem.
There is a quieter gap too. Retries recover the payment. They do nothing for the relationship. A customer whose card failed, who then got three dunning emails, who felt a flicker of friction with your billing, is a customer whose confidence just wobbled. You won the charge. You did not necessarily win back the goodwill. And nothing tells you which of these recovered customers is now quietly annoyed and eyeing the exit.
Retries are invisible as a growth lever, too. They plug a leak. They do not build the kind of trust that stops the leak from mattering in the first place.
Getting the most out of stripe dunning smart retries is mostly about not treating it as set-and-forget.
A few things worth doing. Keep card details fresh before they fail. Stripe’s card account updater refreshes expired and reissued cards automatically, at no extra cost, which stops a whole category of declines from ever happening. Write dunning emails that sound like a person and not a debt collector, because the tone of that email often decides whether a customer updates their card or just shrugs and cancels. And watch your recovery rate over time, not once, so you catch it when a window change or a price change moves the number.
The bigger idea is this. Pair stripe dunning smart retries with a moment of positive contact and a purely defensive system starts building loyalty instead. A failed payment is a stress point. A successful recovery is a chance to flip that stress into reassurance. That is where a review request comes in, which is exactly what the next section is about.
If there is one thing to take away about stripe dunning smart retries, it is that consistency wins. The businesses that get the most out of stripe dunning smart retries are the ones that make it a steady habit rather than a one-off push, and let the results build on their own.
Reviews increasingly shape which businesses buyers and search engines trust. For context, see Google’s guidelines on reviews.
Here is the cashflow angle that retries alone miss. A recovered payment is the perfect moment to ask the customer one simple thing. How is it going? A short review request fired right after a successful charge does double duty. Happy customers leave you a public 5-star review. Unhappy ones tell you privately, before the next renewal, while you still have time to fix it and keep the revenue.
That is the difference between recovering a payment and protecting a customer. Retries stop the money leaking out this month. A well-timed review request after payment catches the disputes, the confusion, and the quiet frustration early, which is where real churn actually starts. You find out someone is unhappy while they are still a customer, not after they charge back or cancel.
Trophy Jar automates exactly this. It connects to Stripe, watches for the payment to clear, and sends the review request for you. Happy customers boost your reputation. Unhappy ones get routed straight to you. You can see how the automatic side works in our guide to automated review collection. No spreadsheets, no reminders, no chasing.
They are Stripe’s automated system for recovering failed subscription payments. When a recurring charge fails, Stripe retries it on a schedule, and with Smart Retries enabled, a machine learning model picks the timing most likely to succeed instead of using a fixed calendar. Dunning is the wider recovery flow, including emails, that surrounds those retries.
You choose a window in the dashboard: 1 week, 2 weeks, 3 weeks, 1 month, or 2 months. Stripe’s recommended default is 8 attempts within 2 weeks. If you build a custom schedule instead, the base billing tier lets you set up to three retries, each a set number of days apart.
Not on their own. When a bank returns a hard decline code, such as a lost, stolen, or closed card, Stripe cannot keep charging the same card. The retry stays scheduled and the attempt count keeps rising, but nothing executes until the customer adds a new payment method. Recovering hard declines depends on getting the customer to update their card.
Keep going: see automated review collection, Stripe review automation.
Retries win the charge back. A review request right after the payment clears wins back the customer, catching disputes early and turning happy clients into public proof. Trophy Jar connects to Stripe and does it automatically. Start for $9/month.