Dunning management: recovering payments that failed for boring reasons

Dunning management is the process of recovering payments that failed: retrying the charge, telling the customer, and escalating on a schedule until the payment succeeds or the account is closed. In a subscription business it is the difference between churn that customers chose and churn that happened to them.

The distinction has a name — involuntary churn — and it is usually larger than teams expect. Expired cards, cards reissued after a fraud alert, insufficient funds on the wrong day of the month, and issuer declines that would succeed on a retry all produce cancellations nobody intended, including the customer.

Retry on the decline reason, not on a fixed schedule

Declines are not all the same. A hard decline — card reported lost or stolen, account closed, do not honour — will not succeed on retry, and repeated attempts can attract scheme scrutiny. A soft decline — insufficient funds, temporary issuer problem, velocity limit — frequently succeeds later, and the useful question is when.

• Insufficient funds: retry timed around likely payday rather than the next morning.
• Temporary issuer decline: a short delay, then one or two further attempts.
• Expired card: no retry helps — this needs the customer to update details.
• Hard decline: stop retrying and ask for a new payment method.

The messages matter as much as the retries

1. Notify on the first failure, in plain language, saying what failed and what happens next.
2. Make updating the card a one-click action from the email, not a login puzzle.
3. Keep the tone neutral — the most common cause is a card that expired, not a decision.
4. Escalate gradually: reminder, then warning of suspension with a date, then suspension.
5. Stop when the account is closed, and say clearly what happens to the data.

Silent retries with no message are the worst configuration: the customer discovers the problem when service stops, having received nothing they could act on. The email is not a courtesy — for expired cards it is the only thing that can fix the payment.

The limits of dunning management automation

Account updater services, offered through the card schemes and most gateways, refresh stored card details when a card is reissued. They cover a meaningful share of failures without any customer action, and are usually the highest-return item in a dunning programme. They do not cover everything, and they do not remove the need for messaging.

Nor does dunning fix a customer who has decided to leave. Where a payment fails and the customer ignores three messages, the honest conclusion is usually that the subscription ended some time ago in their mind; recovering the payment postpones the cancellation rather than preventing it.

Where billing runs on invoices rather than stored cards, the same ladder applies with different steps, and the two often run side by side. Ettex Invoices keeps each invoice with its due date, the reminders sent and the payments applied, so a failed collection is visible as a state of the record and the escalation runs from the ledger. For an invoice that is simply unpaid rather than failed, the overdue invoice ladder is the right process, and credit control decides when to stop.