Failed Payment Recovery
Recover failed renewals with timely, specific prompts and a grace period, before customers lose access they still want.
7 states6 edge casesDesktop + Mobile
01The problem
A large share of SaaS churn is involuntary: cards expire, banks decline renewals, limits are hit. The customer still wants the product, but nobody tells them clearly, or the person who sees the warning isn't the person who can fix it. Access is cut, data appears gone, and a recoverable payment becomes a lost customer.
02When to use
Use when
- Any recurring subscription billed by card
- Products where the user and the billing owner are different people
- Usage-based plans that charge at the end of a period
Avoid when
- Invoiced customers paying by bank transfer — use invoice reminders with due dates instead.
- Prepaid credit products with no recurring charge.
03Recommended UX
Statecraft recommendation
When a renewal fails, keep full access through a defined grace period, show a persistent in-app banner only to people who can fix billing, and give them a one-step card update that retries the payment immediately.
04Desktop behaviour
On desktop the alert is a slim, persistent banner across the top of the app for billing admins, linking straight to the card update.
Desktop rules
- Banner states the problem, the deadline and the fix: “Payment failed. Update your card by 14 Nov to keep Pro.”
- Banner is dismissible for the session only; it returns on the next visit until resolved.
- Members without billing rights see a quieter notice naming who can fix it.
- Escalate tone as the deadline approaches — neutral, then warning, then danger in the last 3 days.
05Mobile behaviour
Most customers act on the failure email, often on their phone. The link must land on a page where the fix takes under a minute.
Mobile rules
4 mobile rules are included in Pro.
Statecraft Pro
Unlock the full pattern
Get the complete interaction flow, states, edge cases, mobile rules and implementation prompt.
- Interaction flow · 6 steps
- 4 mobile rules
- 7 states
- 6 edge cases with recommendations
- 5 microcopy comparisons
- Accessibility notes
- Developer notes
- Claude Code / Codex implementation prompt
Edge cases covered in this pattern
- Viewer isn't the billing owner
- Card updated, retry fails again
- Bank requires authentication
- Grace period ends
- Paying after suspension
- Multiple failed invoices