Stripe dunning is the quiet system that decides whether a failed payment becomes recovered revenue or silent churn. Most founders never touch it. They wire up billing, watch the money land, and assume every charge that fires actually clears. It doesn’t. Cards expire. Banks decline. Balances run dry on the first of the month. And when a charge fails, the customer usually has no idea anything happened.
That gap is where the money leaks out. Good news: a decent dunning flow catches most of it on autopilot. Here is how it works, and how to set yours up so it pays for itself.

What Stripe dunning actually is
Dunning is just an old-fashioned word for chasing a payment that didn’t go through. Stripe dunning is the version baked straight into Stripe Billing: the retries, the emails, and the rules that decide when to try a card again and when to walk away.
Two parts, working together. Stripe quietly re-attempts the charge at the moments it is most likely to clear. And it emails the customer to say something went sideways, nudging them to update the card or top up their balance. When either one lands, the invoice gets paid and nobody churns. When both strike out, the subscription eventually cancels itself.
Here is the part that catches people off guard. Most failed payments are recoverable with fast, well-timed follow-up, and businesses that automate the chase routinely claw back anywhere from 30 to 70 percent of what would otherwise just vanish. That is not a rounding error. For a lot of subscription businesses, a working dunning setup is the single highest-return change they can make to billing, full stop.
Why payments fail in the first place
Before you fix recovery, it helps to know what you are recovering from. Most failed charges are not fraud, and they are not angry customers rage-quitting. They are boring, mechanical hiccups.
The usual suspects: a card that expired and nobody updated it, not enough in the account on billing day, a bank that flagged a recurring charge as suspicious, a card reissued after some breach at a retailer three states away. None of it means the customer wants out. It just means the charge bounced and nobody got the memo.
So failed payment recovery is really a timing problem, not a persuasion problem. The customer already said yes. You are not selling them again. You are just getting a working card in front of Stripe before the subscription throws up its hands and cancels.
How Stripe Smart Retries handle the heavy lifting
The retry engine is the heart of Stripe dunning, and it is cleverer than it looks. Instead of hammering the card at fixed intervals like a broken robot, Stripe leans on a machine learning model trained on billions of transactions across its network to pick the retry times most likely to succeed. A card that failed at midnight might get retried mid-afternoon two days later, because that is when similar cards from that same issuer tend to clear.
You shape the behavior inside Stripe Billing. Head to Billing, then Revenue recovery, then Retries. Pick a Smart Retry window (one week, two weeks, three weeks, one month, or two months) or write a custom policy with up to three retries, each a set number of days after the last. One thing worth respecting: the card networks cap how often you can retry. Visa allows roughly 15 attempts on a card in a rolling 30 days, Mastercard is stricter still, and bursting past those limits can actually earn you fines. Stripe’s defaults stay comfortably inside the lines, which is a very good reason not to hand-roll your own retry loop.
Retries do a shocking amount of the work without the customer ever noticing. But retries alone are not a full strategy. Sometimes the card is genuinely dead, and no amount of retrying resurrects it. That is when the emails earn their keep.
Turning on the emails most people forget
This is the setting that quietly recovers the most money, and on a lot of accounts it ships switched off. Roughly 4 in 10 Stripe accounts have customer failure emails disabled, which means the customer has no clue their payment even failed. In your billing settings, under the section for managing failed subscription payments, there is an option to email customers when a card payment fails. Turn it on. Today.
The math makes the case on its own. A single failed-payment email tends to recover around 15 percent of failed charges by itself. A well-timed sequence of a few emails can push that into the 35 to 45 percent range. Same charges, same customers, just more chances to get a working card in front of them. For most subscription businesses, flipping that one switch is the highest-ROI billing change on the table.
Keep the tone human. The first email should read like a friendly heads-up, not a warning shot: your payment did not go through, here is a link to fix it. Save the firmer language for later in the sequence, after a couple of gentle nudges have gone quiet. Someone forgot to update a card. They did not rob a bank.
Building a Stripe dunning flow that actually recovers revenue
Put the pieces together and a solid Stripe dunning flow looks like this. A charge fails. Smart Retries quietly try the card again at the moments it is most likely to clear. In parallel, a short email sequence tells the customer what happened and hands them a one-click way to update their card. If everything strikes out after your chosen window, the subscription cancels and you get a clean signal that the relationship really is over.
A few habits separate the setups that recover 40 percent from the ones scraping 10. Give retries room to run: a two to three week window beats giving up after 48 hours, every time. Make the update-payment link impossible to miss in every single email. And watch your recovery rate the way you watch signups, because half a point here is pure margin, no acquisition cost attached.
Get your dunning flow humming and you have plugged a leak most of your competitors are still quietly bleeding from. If you want to wire these billing events into the rest of your stack, our guide to automated review collection shows how the same payment triggers can pull double duty. And Trophy Jar’s Stripe integration hooks straight into those same events.
The bottom line on stripe dunning
If there is one thing to take away about stripe dunning, it is that consistency wins. The businesses that get the most out of stripe dunning 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.
The payment that clears is the moment to ask for a review
[{“html”:”
Here is the connection most people miss. Stripe dunning is about catching the payments that fail. But the ones that succeed? They are a signal too, and almost nobody uses it. A charge just cleared. The customer is active, their card works, and the relationship is healthy at that exact second. That is the single best moment to ask how things are going.
“},{“html”:”
It doubles as an early-warning system. Fire a review request right after payment and you will surface a frustrated customer before they escalate to a chargeback or a public one-star tirade. You hear about the problem while it is still a quiet reply in your inbox, not a dispute Stripe is already clawing money back for. Catch it early and you usually keep both the customer and the cash.
“},{“html”:”
Trophy Jar handles that side automatically. It plugs into the same Stripe events your dunning flow already leans on, and the second a payment clears it sends a review request on its own. Happy customers post five-star reviews to Google or your own site. Unhappy ones route quietly back to you first. Same trigger that powers your recovery flow, now guarding your reputation and your cash flow at once.
“}]
Frequently Asked Questions
Does Stripe dunning cost extra?
The core dunning tools, Smart Retries and failed-payment emails included, are part of Stripe Billing, not a separate paid add-on. You set them up inside your Stripe Dashboard under Revenue recovery. Some businesses bolt on third-party tools for deeper email sequences, but Stripe’s built-in flow already recovers a meaningful chunk of failed payments on its own.
How much revenue can Stripe dunning actually recover?
It varies by business, but the benchmarks are strong. Businesses running automated dunning typically recover somewhere between 30 and 70 percent of failed payments. Turning on failed-payment emails alone tends to recover 20 to 30 percent more than retries by themselves, which is why enabling them is usually the first move you should make.
How many times should I retry a failed payment?
Let Stripe’s Smart Retries handle the timing. You can set a window from one week up to two months, or a custom policy with up to three retries. Just respect the card network limits: Visa allows roughly 15 attempts on a card in a rolling 30 days, and exceeding them can trigger fines. Stripe’s defaults stay safely inside those caps.
Related reading
Keep going: see automated review collection, Stripe review automation.
Turn every cleared Stripe payment into a fresh review
Your dunning flow already fires on Stripe payment events. Let Trophy Jar ride the same trigger to auto-send a review request the second a charge clears, catching unhappy customers before they dispute and turning happy ones into five-star proof. Start for $9/month.