DEV Community

Swipe Again
Swipe Again

Posted on

Retry Timing Is a Promise About How You See the Customer

Two teams can run the same number of retries and get completely different results. The difference is rarely effort. It is timing — not timing as a growth hack, but timing as a reading of why the payment failed in the first place. A retry fired without that reading is just a second refusal waiting to happen, and banks notice patterns of refusals in a way customers never see but merchants eventually pay for.

Begin with the decline itself, because it narrows the calendar more than most teams realise. An insufficient-funds decline is a statement about a moment, not about a person: the money was not there then. Retrying that evening repeats the same fact. Retrying after the customer's likely payday tests a new fact. An expired or replaced card is the opposite problem — time alone fixes nothing, and the right move is detection and a clear update request, with a retry held ready for the moment fresh details land. A generic decline sits between the two: it rewards a spaced, varied approach rather than either a rush or a wait.

Payday aiming is the highest-value habit in this whole discipline, and it is also the simplest to describe. Most people are paid on recognisable rhythms — weekly, fortnightly, monthly, on set dates. A renewal that fails just before a common payday deserves a patient, deliberate second attempt just after it. A renewal that fails just after payday deserves a faster follow-up, because the timing explanation is already weakening and the cause is probably something else. Neither move requires knowing any individual's salary date; the calendar patterns of a whole customer base are enough to shift real money.

Spacing protects you as well as the customer. Attempts clustered tightly together can look, to an issuing bank, like a merchant who does not take no for an answer, and repeated declines on the same card do a merchant's standing no favours. A schedule with air in it — attempts separated by days, varied sensibly, and capped at a number you can defend — reads as diligence rather than desperation, to banks and to customers alike. The customer side matters too: nobody trusts a service that charges their card every morning for a week, even if one of those charges eventually succeeds.

There is also a stopping question, and honest timing includes it. After a sensible number of well-aimed attempts across a fair window — measured in weeks, not days — a case that has produced no payment, no card update, and no reply has given you its answer. Continuing to retry past that point does not recover revenue; it manufactures decline history and teaches the customer that your renewal notices can be safely ignored. A clean stop, with a final clear message and a simple way back, preserves both the relationship and the option of a later winback that actually lands.

For the practical rules in one place — intervals by decline family, how long a full sequence should run, and when to stop and hand the case to a human message instead — see this timing guide on when to retry failed payments without turning patience into guesswork. It is written as working rules a small team can adopt on a Monday, not as theory.

Adopt them in that spirit: write your timing rules down, apply them consistently for a quarter, and then change one variable at a time based on what your own queue teaches you. Timing learned from your own renewals compounds. Timing copied from a benchmark resets every time your customer mix changes.

That discipline is built into Swipe Again: payday-aimed retries, card-update attempts that fire when new details arrive, and quiet hours respected, all on a flat fee — so the calendar works for the customer, and the recovery follows.

Top comments (0)