This is the SaveMyMRR console with three invented failed invoices dropped into it. Scrub through the seven days and watch what happens at each step: which retry lands, which email lands, and which invoice we lose. No account, no key, nothing to install.
The timings, the retry-before-email order and the day-7 stop are read from the same file the production worker runs. Only the three customers are made up.
Email only. No retry — Stripe tried the card seconds ago, trying it again would be theatre.
| Customer | Amount | Stripe decline code | Status |
|---|---|---|---|
| $29 | insufficient_funds | New | |
| $89 | card_expired | New | |
| $249 | do_not_honor | New |
insufficient_fundsThe card had no money on it on Tuesday. It had money on it on Wednesday. Retrying a working card 24 hours later is the easiest recovery there is, and Stripe Smart Retries already does it for free without us. We show this one so you can see it, not so we can bill you for it. If most of your failures look like this, turn on Smart Retries and keep your $29.
Dunning tools don't publish their cadence. Here's ours, generated from the same file the worker reads. Change the file, this table changes with it.
| When | What runs | Why there |
|---|---|---|
| Hour 0 | Email only. No retry — Stripe tried the card seconds ago, trying it again would be theatre. | Reach the customer while they still remember buying something from you. |
| Day 1 | Retry the card, then email if the retry fails. | 24 hours is the first moment a balance can plausibly have changed: payday, a transfer, a fraud block lifted. |
| Day 3 | Email only. | If day 1 didn't work, the same card rarely behaves differently on day 3. The email does the work here. |
| Day 5 | Retry the card one last time, then email if it fails. | Last realistic shot for a retry. Five days covers a weekend and, for most people, a payday. |
| Day 7 | Stop. The record is marked lost. | A week is where our patience ends. Past that, replies stop and spam complaints start. |
Every recovery in this console is an email plus a card retry. That is the whole product. Here's what we're missing next to the bigger tools, in plain sight:
To find out whether any of it is worth $29 at your size, the involuntary churn calculator does that arithmetic in your browser, and how it works walks through the Stripe key we ask for and what it can touch.
No. The three customers are invented and this page sends no email. What is real is the machinery around them: the hour offsets, the retry-before-email order and the day-7 stop are read from the same file the production worker runs.
This demo and the churn calculator need no account. Beyond that, no. The product's only job is to act on your failed invoices, and it can't see them without a Stripe restricted key. A sandbox would tell you nothing true about your own churn.
A retry only helps when something about the card changed: a balance, a bank block. Day 1 catches an overnight top-up, day 5 catches a weekend and a payday. Day 3 rarely changes anything, so it's an email instead.
Retrying does nothing, which is why the middle row of the demo fails its retry and gets paid by the email instead. The customer has to enter a new card. The button in our email sends them to Stripe's hosted invoice page to do exactly that.
No. Free detects the failed payments and lets you send an email or fire a retry by hand, one invoice at a time. The automatic sequence starts on Pro at $29/mo.
Money that came back after one of our actions. The demo keeps a separate column for invoices Stripe Smart Retries would very likely have collected on its own, because counting those as our wins would flatter the number without adding a cent to your bank account.
Seen enough to hand over a restricted key?
Start free — connect StripeFree plan, no card. You paste a Stripe restricted key; it's encrypted at rest and you can revoke it from your Stripe dashboard in one click.