DEV Community

Swipe Again
Swipe Again

Posted on

Stripe Retries Well. The Awkward Cases Are Still Yours.

Stripe's native retry machinery is genuinely good at the ordinary case. A card with room on it, a bank having a quiet afternoon, a balance that lands two days later than the renewal expected — Smart Retries reads those signals better than any fixed schedule a small team could hand-tune, and it recovers a healthy share of failures without anyone writing a single email. If your recovery plan starts there, it starts in the right place. The mistake is assuming the plan also ends there.

The awkward cases are the ones the schedule cannot see. A subscriber whose card was replaced after a fraud alert now holds a new number the vault has not caught up with. A finance contact who approved the subscription in spring has left the company, and the renewal notice is landing in a dead inbox. A customer who fully intends to stay has a card locked behind an authentication challenge that only they can clear, on a phone they check twice a week. None of these are timing problems, so no retry time, however cleverly chosen, fixes them. Each one needs a person to be told something specific, in plain language, while there is still time to act.

That is the honest way to read stripe dunning: not as a replacement for the platform's own machinery, but as the layer that handles what a schedule structurally cannot. The platform retries the card. Somebody still has to reach the human attached to the card, and the reaching has its own craft — a first message that reads like a service note rather than a threat, a card-update page that opens cleanly on a phone, a cadence that stops the moment the customer responds instead of marching on through a template sequence.

A useful weekly habit makes the boundary visible. Open the list of invoices currently inside the retry window and sort it twice: once by amount, once by age of failure. The amount sort tells you where the money is. The age sort tells you where the silence is — the accounts that have failed, been retried, and said nothing at all. Silence is information. A customer who replies, even angrily, is still in a relationship with you. A customer who says nothing through three attempts is usually a customer who never saw the message, cannot act on it, or has quietly decided to let the subscription lapse and is using the failed payment as the exit. Each of those three silences has a different honest response, and none of them is a fourth identical retry.

None of this diminishes what the platform does. It locates the work correctly. Billing platforms are excellent at the mechanics of trying again; they are not built to notice that the billing contact changed jobs in March, or that your annual customer's renewal lands the week their company freezes spending. That noticing is an operator's job, and it stays an operator's job no matter which processor runs the charge.

The teams that recover well on Stripe tend to describe their setup in two sentences, not one: the platform handles the retries, and a deliberate process handles everything the retries surface but cannot solve. The second sentence is where the recovered revenue the schedule alone leaves behind is actually won.

That second sentence — watching the surfaced cases and acting while the window is still open — is the working idea behind Swipe Again, built for Stripe merchants who want the awkward cases owned rather than abandoned to the schedule.

Top comments (0)