Most failed-payment recovery starts watching the day you install it. That is a strange place to start, because the biggest pool of recoverable revenue is usually sitting behind you: every subscription that failed in the last ninety days and quietly churned, was written off, or is still sitting in a past-due state nobody is working.
A failed payment is not a dead customer. Cards get replaced. Bank balances refill on payday cycles. A card that hard-declined in week one sometimes succeeds in week five for reasons that have nothing to do with you. The failure ages; the intent that created the subscription does not age as fast.
So when Swipe Again connects to a billing platform, it does not just wait for the next failure. It backfills: up to ninety days of historical failed payments are pulled in and worked through the same recovery flow as a fresh failure — decline-aware retry timing, a branded card-update page, and dunning email and SMS where the merchant has consent on file. The way the recovery flow works is identical for a failure from this morning and one from two months ago.
There are limits worth respecting. A backfill is not a license to hammer old cards: every attempt still has to respect the platform's rules, the customer's consent, and sensible attempt ceilings, and some failures — a card reported stolen, an account closed for fraud — should never be retried at all. Decline codes tell you which is which, if you read them before you schedule rather than after.
But the failures that are merely stale rather than dead are real revenue, already earned once, sitting in a report most merchants never open. The cheapest new customer is the one who already subscribed. The second cheapest is the one whose card failed last month and who still thinks they are subscribed.
Top comments (0)