DEV Community

Swipe Again for Swipe Again

Posted on

The Retry Clock Should Answer to the Decline, Not the Calendar

Ask ten subscription teams when they retry a failed payment and most will answer with a schedule: day one, day three, day seven, or some variation worn smooth by habit. Ask why those days, and the room usually goes quiet, because the honest answer is that the schedule came with the tool, or with a blog post, or with the last person who held the job. Schedules are not wrong. A retry has to happen sometime. But a schedule that ignores why the payment failed is a clock answering to itself, and the decline codes in any real file are patiently explaining that different failures keep different time.

Start with the failure that keeps calendar time most literally. Insufficient funds is a statement about a moment, not a person: on the morning of the attempt, the money was not there. Its remedy lives in other people's calendars — wage cycles, benefit payment dates, the first business day after a long weekend. Retrying this decline on a fixed day-three cadence is a lottery ticket. Retrying it near the subscriber's likely payday is a plan. The information needed is embarrassingly available: the day of the week the failure occurred, the rhythm of the month, and the patience to wait for a better morning instead of spending attempts on bad ones.

Expired and replaced cards keep the opposite time. They do not heal by waiting. Every day spent politely spacing retries against a dead credential is a day the subscriber drifts toward forgetting the subscription exists, while the fix — new details, entered once — takes two minutes whenever it happens. For this class the clock should be measured in hours to first contact, not days to first retry, and retries should mostly stop until the credential changes. Notes on when to retry failed payments, sorted by the clock each decline actually keeps is a useful corrective here, because it reframes the schedule as several clocks sharing one queue.

Authentication-required failures keep a third time: the subscriber's attention. The bank wants the cardholder to confirm the payment is genuine, which means the retry cannot succeed until a person has done something, and people do things in the margins of a day — the commute, the lunch break, the evening scroll. Contact for this class should land when acting is plausible, carry exactly one action, and expire gracefully, because a confirmation request discovered a week later reads as archaeology, not service.

Then there is the failure that should slow every clock down: the unexplained issuer refusal. Spaced attempts, a clear message, and an early verdict respect both the bank's opaque risk posture and the subscriber's patience. Compressing this class into a rapid schedule does not recover more subscribers. It recovers the same subscribers faster, annoys the rest sooner, and teaches issuers to associate your attempts with noise.

None of this requires exotic machinery. It requires sorting before scheduling: read the decline, assign its clock, then let the calendar be built from the file instead of imposed on it. Teams that make that one change usually discover their attempt count falls while their recoveries rise, which feels like a paradox until you see the file clearly. They were never short of retries. They were short of timing, and timing was sitting in the decline codes all along, waiting to be read. Write the clocks down where the whole team can see them, one line per decline family, and review them monthly against what actually recovered. A timing rule that cannot be pointed at will quietly revert to the old fixed schedule the first busy week nobody is watching the queue.


Published by Swipe Again — failed payment recovery at a flat $179/mo.

Top comments (0)