DEV Community

Swipe Again for Swipe Again

Posted on

Who Retries on Day Seven? Owning the Recharge Handover

Every Recharge store has a delegation setting, whether the merchant remembers setting it or not. Recharge can keep failed-payment recovery in-house, running its own native retry schedule and its own notices. Or the merchant can hand recovery to a third-party tool — but only by turning that delegation on, deliberately, in the settings. Until the switch is thrown, outside help politely defers and the native defaults run the case. A surprising share of subscription stores live in the gap between those two states: they believe they bought recovery, or believe the platform handles it, while in practice nobody owns day seven.

Day seven is where the question gets sharp. The first retry after a failed renewal is easy; every system makes one. By day seven the easy explanations have expired. The insufficient-funds subscriber has been paid or has not. The replaced card has been refreshed by the network or it never will be. The subscriber who meant to fix their details has either done it or drifted far enough that only a well-written message brings them back. What happens on day seven is therefore not a scheduling detail. It is the store's actual recovery policy, and it deserves to have been chosen rather than inherited.

Owning the handover starts with a one-sentence answer, written down: for a failed Recharge charge, this system retries, on these days, for these decline families, and that system writes to the subscriber, in our name, at these moments. Stores that cannot write the sentence have two systems improvising — native retries firing on one clock while a tool fires on another, stacking attempts on the same card on the same morning, which reads to an issuer like a merchant hammering a credential. Coordination is not a refinement. Two uncoordinated ladders are worse than either ladder alone.

The sentence also has to say what stops. A subscriber who cancels mid-recovery is finished, and every system touching the case should learn it at once; a recovery sequence that keeps emailing a person who already left is not persistence, it is a chargeback being composed in slow motion. A hard decline — a card reported lost or stolen, an account closed — stops the retries and moves the case to a single human message or to a clean ending. And a pause is not a failure: a subscriber who skips a month has told you exactly what they want, and a tool that counts their later resumption as a recovery is inflating the rate you are using to judge it.

Then there is the test nobody runs. Subscribe with your own card. Let a renewal fail. Watch what arrives, in what order, on your phone: the platform's notice, the tool's notice, both, neither. Save a new card and time what happens next — minutes, or days? Merchants who run this small piece of theatre almost always find something to fix within the hour, because the handover they configured in the abstract turns out to have a seam exactly where the subscriber stands.

For the full working picture of the switch, the settings around it, and the sequence that should run once delegation is real rather than assumed, a merchant's field guide to recharge dunning lays the handover out step by step, in the order a store actually meets the decisions.

The renewal file does not care who was supposed to be in charge. It only records what happened. Stores that recover well on Recharge are the ones that can name an owner for every day of the case — and that ownership, failure by failure, is what Swipe Again is built to provide once the handover is thrown: retries in the gaps of the native schedule, messages in the store's voice, and a hard stop the moment a subscriber says stop.

Top comments (0)