The first failed attempt on a Recharge renewal tells you very little. Cards fail on first attempts for forgettable reasons — a bank's overnight batch hiccup, a limit brushed at the wrong hour, a customer travelling. What the first failure really does is open a short window, measured in days, during which the renewal is still easy to save. How a shop uses that window, and especially what its second attempt looks like, decides far more renewals than any later heroics.
A good second attempt is not simply the first attempt repeated. Before it fires, three things should have had a chance to change. The customer should have received one clear message that names the product they are about to lose, not just an amount. The card situation should have been checked — an updated card anywhere in the account should replace the one that failed, silently, before another decline is burned. And the timing should reflect the failure reason: a funds-related decline retried on a plausible payday is a different bet from the same decline retried the next morning.
Most default setups do none of those three things between attempts one and two. The interval is a fixed number of days, the message is the platform's stock wording, and the same card is presented again in the hope that the bank feels differently. Sometimes it works — banks do feel differently — and that occasional success disguises how much is being left inside the window while it is still open.
This is the practical case for recharge dunning built around the second attempt window: arrange the sequence so the highest-judgement actions land early, while the customer still considers the subscription current, instead of saving the effort for a final attempt after they have mentally already lost the product and started shopping for its replacement.
The handover setting matters here more than most shops realise. Recharge can let a third-party tool run the recovery, but that only works when the shop's own settings actually hand the retries over — otherwise two systems take turns with the same customer, messages overlap, and neither record is complete. Whichever system owns the case should own it wholly: its timing, its messages, its stopping rule. A renewal with two owners has none.
Watch, too, what the second attempt does to reporting. Shops that judge recovery only at the end of a long sequence cannot see that most of their saves happen early, and they over-invest in late-stage pressure that mostly annoys people who were never going to pay. Plot saves by attempt number for one month. The shape of that curve is the sequence's real design document — it shows where to add care, where to add patience, and where to stop.
The message inside that window deserves the same early care. A subscriber whose renewal has just failed has usually not noticed anything yet — the product may still be working, the next delivery may still be expected. The first message is therefore not an alarm; it is a piece of information, best delivered in the tone of a shop that expects the problem to be simple. Name the product, name the date of the failed attempt, and give one link that goes straight to updating the card, with no detour through a generic account page. Save the firmer wording for later in the window, if it is needed at all. Shops that open with urgency spend their credibility before the case has earned it, and then have nothing left to say when a case genuinely reaches its last chance.
None of this needs a rebuild of the store. It needs the existing sequence read as a window rather than a schedule: check the card, send the one good message, time the retry to the reason, and keep a single clear record of the case from first failure to final outcome.
That window-first reading is how Swipe Again approaches Recharge renewals — one owner per case, the best work done early, and every outcome counted once against the attempt that actually earned it.
Top comments (0)