DEV Community

Swipe Again for Swipe Again

Posted on

Worked Example: Building a Retry Calendar Around Three Paydays

Take three subscribers whose renewals failed in the same week, and build the calendar a thoughtful operator would build for each. Subscriber A is salaried, paid on the last business day of the month. Subscriber B is paid every second Friday. Subscriber C works shifts and is paid weekly on Wednesdays, irregular amounts. All three failures read "insufficient funds." A fixed retry cadence — day 1, day 3, day 7, the industry default — treats them as the same case. They are not the same case, and the calendar shows why.

For A, the failure lands mid-month, eleven days before payday. Retrying on day 3 tests a bank balance that has not changed in any way that matters; the attempt spends goodwill and returns the same answer. The honest calendar for A is quiet: a friendly notice now, no retry until the day after payday, then one clean attempt. Total attempts: one or two, timed at the only moment the answer can change.

For B, the fortnightly rhythm makes the calendar a coin flip that can be loaded. A failure just after a payday Friday is probably not a timing problem at all — the money was there — and deserves fast escalation to card-checking. A failure just before a payday Friday is the opposite: wait forty-eight hours and retry once. Same decline code, opposite calendars, decided entirely by where the failure sits inside the pay cycle.

For C, the weekly rhythm means no retry is ever far from a payday, but the amounts vary, so the calendar needs a different discipline: retry on the Wednesday rhythm, but stop early. A case that has failed across two full pay cycles is no longer a timing case; it is a conversation case, and more attempts only rehearse the same answer.

A note on how the operator knows any of this: you do not need a customer's payroll records, and you should not ask for them. The pay rhythm is inferable from the failure pattern itself. A subscriber whose insufficient-funds failures always clear on the second attempt, four days later, is telling you where their payday sits; a subscriber whose renewals succeed on the 1st and fail on the 28th is drawing you their monthly curve one renewal at a time. Two or three cycles of honest attempt history per case is enough to place the next attempt intelligently — which is one more reason the attempt history has to be recorded cleanly, with the bank's answer attached, rather than summarised into a single "failed again" note that throws the evidence away.

The worksheet version of this exercise lives in the payday retry calendar, and its real lesson is not the grid — it is that "insufficient funds" is a scheduling diagnosis, not a verdict on the customer. Every retry placed before the balance can change is a guess dressed as diligence. Worse, repeated attempts against an empty account are not free: issuers notice retry behaviour, customers notice multiple pending charges, and both kinds of noticing outlast the case itself.

Operators who rebuild their cadence this way usually find they send fewer attempts and collect more money, which feels paradoxical only until the calendar is on the wall. The attempts that remain are the ones with a reason to succeed. The ones removed were never going to.

Automating that judgment — reading the failure, placing the next attempt where the customer's month says it can land, standing down the moment a card changes — is the work Swipe Again does at $179 a month flat, with a 30-day guarantee judged on total recovery — recover $179 or the next month is free. Draw the three calendars for your own last three insufficient-funds cases. If your current cadence gives all three the same dates, the calendar has found your leak.

Top comments (0)