Failed-payment recovery ladder

Failed-payment recovery ladder

When a subscription charge fails, the job is to recover the payment across a short series of messages that get more urgent over time — without ever tipping into a threat. Left to itself, the base model tends to write a single generic "your payment failed" note, and when asked for a final warning it reaches for collections-style language ("URGENT — settle your balance now to avoid losing access"). Both lose the recovery. These conventions steer it back.

Three principles run through every stage:

• Assume good faith. A failed charge is almost always an expired or maxed-out card, not a refusal to pay. Every message before the last one reads like you are helping the customer fix a glitch, not chasing a debtor.
• Lead with the fix, not the failure. The single clearest action in every message is updating the payment method. The failure is the context; the fix is the headline and the button.
• Escalate through clarity, not fear. Rising urgency comes from a concrete factual clock — when the card gets retried, the exact date access pauses — never from punitive, shaming, or legal wording.

The four stages

Send them in order over roughly two weeks. Do not skip a stage, and do not downgrade the account until the final notice has gone out and its stated deadline has passed.

Stage 1 — First notice (day 0)

A light, helpful heads-up sent the day the charge fails. Frame it as a small fixable hiccup: the card probably expired or was declined by the bank. Offer the update-payment action and stop there.

• Do not mention suspension, downgrade, or any consequence yet — it is far too early.
• Do not imply the customer did anything wrong. Keep it warm and low-stakes.

Stage 2 — Reminder (day ~3)

The automatic retry has run and failed again. A gentle nudge that reassures the customer nothing has changed yet — their account is still fully active — and repeats the one-click fix. Mention that the card will be tried again automatically so the clock feels routine, not punitive. Still no threat.

Stage 3 — Escalating reminder (day ~7)

Now name the consequence, once, as something you want to help them avoid. State the specific date