Dunning for subscription businesses: recovering failed payments

What is dunning, and why does involuntary churn matter?

Dunning is the old word for asking someone to pay what they owe. In a subscription business it means something narrower and more mechanical: the routine that starts the moment a renewal charge fails. The card is retried, the customer is told, a link to update the card goes out, and access is kept or paused while the account is fixed. Done well, the customer barely notices. Done badly, they notice when their service stops.

The reason it deserves a process of its own is involuntary churn, the customers you lose because a payment failed rather than because they chose to cancel. These people wanted to stay. Their card expired in March, or their salary landed two days after your billing date, and nobody gave them an easy way to fix it.

Run an illustration. A business with 2,000 subscribers at 30 euros a month sees 5 percent of renewals fail in a given month: 100 failed charges, 3,000 euros of revenue on hold. Suppose retries recover 40 of them and reminders bring back another 30. The 30 that remain are 900 euros of monthly revenue gone, and if the same thing happens every month, that is 360 subscribers a year who never meant to leave. The numbers are invented for illustration, so run the same sum on your own book. Recovering a failed payment costs very little per customer next to winning a new one.

Why do card payments fail on renewal?

Four causes cover most of it. Expiry is the simplest: the card on file reached its end date, or the bank reissued it after a fraud scare. Card networks run updater services that pass new card details to merchants automatically, so ask your payment provider whether yours is switched on; it fixes a share of these before anyone has to be asked.

Insufficient funds is the second, and the most timing-sensitive. The money is often there a few days later. Issuer declines are the third: the customer's bank refused the charge for its own reasons, from a fraud rule tripped by an unfamiliar merchant to a spending limit. Banks signal these with decline codes, and the codes split into two families. A soft decline, such as insufficient funds or a temporary bank error, may succeed on a later attempt. A hard decline, such as a lost, stolen or closed card, will not. Visa, for one, sorts declines into categories, never allows a retry after a decline that says the card will never be approved, and caps retries on the rest.

The fourth cause is particular to Europe. Under the second Payment Services Directive, PSD2, customers in the European Economic Area must pass strong customer authentication, a check with two independent factors such as the phone and a fingerprint, for most online card payments. Recurring charges the merchant starts on a schedule are generally outside that rule, as long as the first payment was authenticated and the later ones are correctly flagged. But the issuing bank decides, and some still ask for authentication on a renewal. When that happens the charge comes back declined with a request for authentication, and no amount of retrying will clear it. The customer has to open a link and approve the payment themselves.

When should you retry a failed payment?

Read the decline code first, then decide. Hard declines get no retry at all; they go straight to a message asking for a new card. Authentication requests get no retry either; they go straight to a message with an approval link. Only soft declines enter the retry schedule.

For those, spacing beats frequency. Three or four attempts over roughly two weeks is a common pattern: one a day or two after the failure, one a few days later, one near the end of the grace period. Where you can, aim attempts at the days money tends to arrive, such as the first working day of the month or the usual payday in your market, and at a time of day when the account has had overnight deposits clear. Retrying the same card every few hours mostly produces more declines and more fraud flags at the issuer, and can breach the card networks' retry limits.

If you automate dunning, this is the logic to write down first, because it is where the most avoidable declines come from. And tell the customer before the second retry, not after the last. Someone who knows a charge failed can move money or switch cards. Someone who doesn't finds out when their account locks.

What should the reminders say, and when does a call beat an email?

A subscription reminder has an easier job than an invoice chase: the customer usually wants the service and just needs a frictionless way to keep it. So each message carries the same three things: what failed and why in plain words ("your card ending 4412 expired"), what happens next and when ("your plan stays active until 21 October"), and one button that fixes it. No login wall, no hunt through settings. Automated payment reminders do this well because they never forget, never send the wrong tone on a busy day, and fire in step with the retry schedule.

A typical sequence runs four steps. On the day of the failure, a short note that something went wrong with the payment, not with the customer. Around day 3, a reminder with the update link and the date access changes. Around day 7, something more personal. Before the grace period ends, a final notice that says plainly what will pause and how to restore it.

That day 7 step is where a call starts to earn its place. Email works for the customer who simply hadn't noticed. It does little for the one who has noticed and is avoiding it, or for higher-value accounts where losing the customer costs far more than a call. A short phone conversation can find out whether the problem is the card, the money or the product, and offer the right fix on the spot: a new payment date, a cheaper plan, a pause instead of a cancellation. The trouble is that few teams have the people to make those calls consistently, which is why many now automate them. AI payment reminder calls, voice software that holds a real conversation rather than playing a recording, can make that day 7 call to every eligible account and log what was agreed. In Europe the caller must say it is an AI, under the EU AI Act's transparency rule.

Manual dunning, a collection agency or AI: which fits?

Dunning ends when the grace period does. Once access is paused or the subscription cancelled with money still owed, you are no longer fixing a payment method; you are asking someone to settle a debt. The rules change with it. Collections law on contact hours, frequency and privacy applies in full, and the tone has to fit someone who may now be in real difficulty rather than someone with an expired card. Many subscription businesses simply write off small balances at this point and focus on winning the customer back. For larger balances, the question is who does the work of recovering them, and that depends on where the account sits.

Each option suits a different point on the timeline. Dunning automation software covers the early stretch cheaply; an agency earns its fee only once your own sequence has run and the account has gone silent.