A customer's card expired at 2 a.m. Nobody decided to churn — but five weeks later they were gone.
If you run subscriptions or monthly retainers, you already have involuntary churn. It's the 20–40% of all churn that no customer ever chose: a card expires, a bank declines one charge, a reissued card replaces the old one, and the "cancellation" happens silently in your billing dashboard instead of in an email.
The customer isn't leaving. They're waiting for a working link.
The math that makes this the cheapest revenue you'll ever recover
Take 200 customers at $29/month. Card failure rates run 5–10% of charges monthly. At 8%, that's sixteen failed charges — $464 standing at a cliff every month, and roughly half of those customers quietly never coming back. About $2,700 a year, lost to cards, not to your product.
Recovering 50–70% of those charges costs two hours of work, once. Compare that to winning the same money from new sales (marketing) or from overdue invoices (awkwardness). Failed payments are the only revenue leak where the customer wants you to collect.
The four-touch sequence
The trick with dunning is the opposite of invoice chasing. Invoice collection escalates. Dunning de-escalates: every email assumes the customer is fine and the card is not.
Day 0 — instantly, on the failure event. Speed is the whole game; recovery rates fall off a cliff after 48 hours because the failed charge leaves working memory. One short email, plain subject line ("Your payment failed — update your card"), and one button to a prefilled, logged-in card update page. Never make a customer log in, find billing, and hunt. Every extra click is a recovered customer lost.
Day 3 — the expiry explanation. Second retry, and name the likely cause: cards on file expire. Reassure: no service interruption yet.
Day 7 — the second rail. Third retry plus alternatives: PayPal, bank transfer, a manual invoice. A meaningful share of silent failures are cards the bank blocked for recurring charges. Give those customers a door.
Day 12–14 — pause, don't delete. The account pauses (read-only, or downgrade to free), with the promise that nothing is deleted and everything returns exactly as it was. What never happens: silent deletion, or angry demand emails. Pausing an intending customer is how you hand them to a competitor's onboarding flow.
Retry logic, briefly
Ride every touch with a re-charge, but spread retries across different days and times — a card declined on the 1st for insufficient funds often succeeds after payday. Never retry more than ~4 times: hammering a card gets your merchant account flagged, not just the charge declined. If your processor has automatic card updater or smart retries, switch them on. And if failures suddenly spike across many customers at once, it's your gateway, not their wallets — pause the sequence and fix the rail first.
Pre-dunning beats dunning
The best failed payment never happens. Run a monthly query for cards expiring within 45 days and send one cheerful "update your card and notice nothing" email. Convert monthly customers to annual plans — every annual conversion removes eleven billing events, and billing events are where revenue dies.
The weekly five numbers
- Charges failed (count and dollars)
- Recovered (count, dollars, and which touch did it)
- Recovery rate as a trend — falling with flat failures means your emails broke, not the cards
- Median days-to-recover — creeping up means touch 1 is slow or in spam
- Paused-not-deleted count — customers in grace who need one more nudge
One person owns the read, fifteen minutes a week. Unowned automations silently rot; this one prints money when someone watches it.
A real-shaped example
A five-person studio bills 90 retainers at $350 ($31,500 MRR). Nine card failures in a month, $3,150. Their old habit: one email, eventually, a third recovered. After building the sequence in one afternoon: touch 1 alone recovered four within 24 hours, two reissued cards came back on the expiry email, one converted to bank transfer, one returned from the pause state at day 19. Seven of nine back — 78%, $2,450/month — for six emails of work.
The two that stayed gone? One was a customer who'd decided to leave and used the failed card as the exit. The pause notice got a real answer, which is worth knowing even when the answer is goodbye.
The full playbook — paste-in email structure, retry timing details, and the prevention checklist — is on the site: Failed Payment Recovery Sequence for Subscriptions & Retainers (one of 150 free ops notes for small teams).
Failed payments aren't churn. They're a customer silently asking you to make it easy to keep paying.
Running a small business or ops team? The Ops Starter Kit ($14) packs the checklists, templates, and runbooks from this article into ready-to-use form. Free First 30 Minutes incident response kit also available.
Top comments (0)