05.05 · Concept
Dunning, Cancellation & the End
Design what happens over the days after a renewal fails, and keep cancelling a subscription from being the same event as revoking access.
Dunning is a designed recovery flow after a recurring charge fails, not an immediate subscription death. Treat billing status, customer messages and product access as separate tracks, so retries, reminders, grace behaviour and final closure can change independently without deleting entitlement or ending contracts by accident.
What this lesson answers
- how should dunning work after a failed renewal
- difference between cancellation and access revocation
- subscription states after recurring payment failure
Notes
Dunning is the recovery process after a recurring payment fails. The payment failure is not the end of the subscription; it is the start of a short, designed state machine. A good system decides when to retry the card, when to email or notify the customer, when to ask for updated payment details, when to pause benefits, and when to finally mark the subscription as unpaid or ended.
The useful mental model is a timeline with separate tracks for billing state, customer communication, and product access. On day zero the renewal invoice fails.
Common questions
- What should happen when a subscription renewal payment fails?
- The account should move into a recovery flow rather than being ended immediately. Typical handling includes retrying the charge, notifying the customer, requesting updated payment details and deciding whether access remains full, limited or paused. The right sequence depends on product risk, customer value, support impact and how likely recovery is.
- Why should cancellation and access revocation be separate events?
- Cancellation is a decision to stop future billing, while access revocation is a product entitlement decision. Keeping them separate prevents one billing problem from deleting access too early, breaking contracts or losing a recoverable customer. It also makes accounting and customer support much easier to reason about.
- What states should a subscription dunning flow include?
- A practical flow usually distinguishes active, past due, grace, restricted, cancelled, expired and written off states. The important part is not the exact names, but that state transitions are explicit. Billing events should feed the lifecycle, not directly command the product to shut users out.
Short definition: what is Dunning, Cancellation & the End?