Failed Payment Recovery

A subscriber's card expires in March. The April charge fails on a Tuesday. The system retries Thursday, fails again, retries the following week, fails a third time, and cancels the subscription. Nobody decided anything. The customer still wants the product, still has the money, and still likes your brand. They just got dropped by a billing routine.

That's involuntary churn, and for most subscription brands it's a meaningful slice of total cancellations — a slice that requires no persuasion to win back, because there was never a decision to reverse.

Voluntary vs involuntary churn: why the split comes first

Before you fix churn, you have to separate it. Voluntary churn is a customer choosing to leave: too much product, too expensive, didn't work, life changed. It's a lifecycle problem, and the causes are worth studying properly — we cataloged them in why subscribers cancel.

Involuntary churn is a payment failure: expired card, insufficient funds, a bank declining a recurring charge it doesn't recognize, a card reissued after fraud. The customer's intent never changed.

These need completely different fixes, and blending them into one churn number hides the cheapest revenue in the business. The first diagnostic in any subscription audit is simply: what percentage of last quarter's cancellations were payment failures? Most brands have never run it.

Why involuntary churn is the fastest revenue you'll recover

Every other retention lever costs persuasion. Win-back flows need an offer. Save flows need a concession. Acquisition needs ad spend. Failed-payment recovery needs a working card number.

There's no discount to fund, no margin to give away, no new customer to buy. You're reconnecting a paying relationship that broke on a technicality. That's why it sits at the top of the fix list in every subscription retention program we build — it pays back before anything else has finished being built.

Pre-dunning: fix it before it fails

The best failed-payment recovery happens before the payment fails. Card expiry dates are known in advance, which makes the failure predictable — and preventable.

A pre-dunning flow reaches subscribers whose card expires before their next charge date, ideally two to three weeks out, with a single job: update the card while nothing is broken. The tone matters. This is a service message, not a billing threat — "your card on file expires next month, here's a one-tap link to update it so your next order isn't interrupted." Customers respond well to it because it protects something they want.

Pre-dunning is unglamorous and consistently outperforms the recovery flows that run after a failure, for an obvious reason: nothing has gone wrong yet, so there's no friction, no embarrassment and no lapse in service to explain.

Retry logic: timing beats volume

When a charge does fail, the retry schedule decides most of the outcome — and the default settings in most subscription platforms are not tuned for it.

Retrying the same card three times in three days mostly produces three declines. Payment failures often have a rhythm behind them: insufficient funds on the 28th may clear on the 1st. Spacing retries across paydays recovers more than hammering them together. Retry too many times too fast and you also risk the bank flagging the merchant, which makes future attempts harder.

The other half is the account updater service, which automatically receives new card details when a bank reissues a card. It's an unexciting integration that quietly removes a whole category of failure — and many brands simply haven't switched it on.

The dunning sequence: what to actually say

A dunning flow is a short, escalating sequence, and each message should carry a different job.

The first message, sent within hours of the failure, is informational and low-drama: something went wrong with the payment, here's the one-tap fix. The second, a few days later, adds specificity — which order is affected, what happens if it isn't resolved, when the next attempt will run. The third, near the end of the retry window, is the honest last call: the subscription will pause unless the card is updated.

Two rules keep this from feeling hostile. Lead with the consequence for the customer (a missed shipment), not for you (a failed charge). And never make the customer hunt — every message should contain a direct, authenticated link to the card-update page, not an instruction to log in and navigate to billing.

Give the escalation a second channel

Email is the default channel for dunning and it's the wrong place to end. A billing message is exactly the kind of time-sensitive, personally relevant note that SMS handles better than any other channel — and by the third message in a dunning sequence, you're talking to someone who hasn't opened the first two.

The sequencing rule is simple: email leads, SMS escalates near the end of the retry window, and both point at the same one-tap update link.

Measuring recovery properly

Four numbers tell you whether this is working. The involuntary share — what percentage of cancellations came from payment failures — is your opportunity size. Recovery rate is the percentage of failed payments that end in a successful charge. Days to recovery matters because a subscriber recovered on day two never missed a shipment, while one recovered on day twenty had a service gap they may remember at the next renewal. And pre-dunning save rate isolates how much failure you prevented rather than repaired.

Improvements here flow straight into customer lifetime value, because every recovered subscriber keeps paying on a relationship you already own.

Where it fits

Failed-payment recovery is the fastest win, not the whole job. Once the involuntary leak is closed, the voluntary side needs its own work — onboarding that gets subscribers to value quickly, cadence controls that offer a pause instead of an exit, and a save-first cancellation flow. We covered that half in building a retention engine that reduces early churn.

It's the pattern behind the subscription programs we rebuild, including the lifecycle overhaul in our MoonBrew case study, where a fast-growing subscription brand had outpaced its own retention systems: fix what's leaking mechanically, then fix what's leaking behaviorally.