Why it matters
A failed payment is often a temporary card or approval problem, not a decision to leave. Dunning combines retries, clear notices and a defined access policy during recovery.
Billing state and product entitlement state must agree. Customers should know what still works during a grace period and when service will change if payment is not fixed.
Decisions to make
- Set retry timing and the maximum recovery window.
- Choose which features remain available during grace.
- Define who receives payment-failure notices in a team account.
- Decide when a customer becomes read-only, paused or cancelled.
- Plan how successful late payment restores access.
Build checklist
- Model payment failure, retry, grace and recovery as explicit states.
- Make billing webhooks idempotent and tolerant of out-of-order events.
- Show the current state and deadline in the customer console.
- Test renewal failure, payment-method update and late recovery.
- Audit entitlement changes caused by billing events.
Common mistakes
- Locking everyone out on the first transient payment failure.
- Continuing full service forever because billing and access never reconcile.
- Sending failure notices only to a departed account owner.
Tools & references
3 starting points to compare or study. Check fit, maintenance, terms and current capabilities before choosing one.
