DEV Community

Swipe Again for Swipe Again

Posted on

The Cheapest Renewal Is the One You Warn About

Most recovery work starts after something has already broken. A charge fails, a clock starts, and a sequence of retries and emails tries to pull the account back. Pre-dunning starts earlier, in the quiet days before a renewal, when nothing is wrong yet except a card that is about to expire, a balance that is drifting low, or a subscriber who has forgotten the charge is coming at all. It is unglamorous work, and it is also the cheapest recovery there is, because a problem prevented never enters the failure statistics.

The clearest case is the expiring card. Issuers know the replacement is coming weeks before the old number stops working, and subscribers usually know too — they simply do not connect that fact to every subscription billed to the old card. A short notice sent while the old card still works, with a direct way to update the details, converts a certain future failure into a thirty-second task. Sent after the failure, the same message competes with retries, warnings, and the subscriber's suspicion that something has already gone wrong with their account.

The second case is the large or unusual renewal. An annual charge that is ten times the monthly amount a subscriber is used to seeing can trigger exactly the behaviour recovery teams dread: a declined authorisation, a fraud flag, or a chargeback filed in surprise. A plain reminder a few days ahead — the amount, the date, what it covers — removes the surprise without selling anything. Subscribers who intended to cancel get a fair chance to do so cleanly, which is better for everyone than a disputed charge and a poisoned payment history.

Timing is where pre-dunning is usually done badly. Send the warning too early and it is forgotten; send it the morning of the charge and there is no time to act. For card expiry, the useful window opens when the replacement card has typically arrived and closes a few days before the renewal. For amount warnings, two to four days is generally enough for a subscriber to move money or update a card. The fuller walkthrough in sending the warning while the old card still works sets out which renewals deserve a warning at all, because warning about every ordinary monthly charge teaches subscribers to ignore the messages that matter.

Restraint is the discipline here. A pre-dunning programme that emails everyone every month becomes background noise within a quarter, and its open rates collapse just as surely as any other overused channel. Reserve it for renewals with a identifiable risk: an expiring card on file, an amount well above the subscriber's usual charge, a first annual conversion, a payment method that failed soft last cycle and recovered late. Those are a small minority of any renewal run, which is precisely why a message about them still gets read.

Measured honestly, pre-dunning rarely produces dramatic numbers in a single month. Its effect shows up as absence — fewer expired-card failures in the run, fewer surprise disputes after annual renewals, a failure rate that stops spiking on predictable dates. Teams that track failures by reason, month over month, can see the category shrink. Teams that only track the total often credit their retries for an improvement their warnings actually caused, and then wonder why the gains stall.

Start with the expiry file alone. It is a finite list, the message writes itself, and the result is visible in the next renewal run. Add amount warnings for your largest tier once the first habit is in place. The rest of the prevention and recovery material is gathered at Swipe Again for operators who would rather prevent the failure than chase it.

Top comments (0)