Guide
Cancellation Confirmation: Best Practices for SaaS Exit Screens
The confirmation step is where customers commit to leaving. It should state what changes on submit: last billing date, access cutoff, and whether the subscription ends immediately or at period end.
Flow patterns: cancellation flow examples. Offboarding hub: SaaS customer offboarding.
Last updated October 23, 2026
What the confirm screen must show
- Product name and plan being canceled
- Immediate vs end-of-period cancel — match Stripe fields you set
- Last day of access
- Link to export data if not completed earlier
- Primary button label that says cancel, not euphemisms
Confirmation email
- Send a receipt-style email when cancel completes
- Repeat access end date and billing stop date
- Support contact for billing disputes — not a win-back coupon by default
- Do not bury unsubscribe from marketing in the cancel flow
Avoid dark patterns
Equal visual weight for “confirm cancel” and “go back.” Do not require phone calls to finish cancel. See when to skip retention offers for offer ethics.
Align copy with Stripe state
Wording should reflect cancel_at_period_end vs immediate delete. Technical timing: Stripe scheduled cancellation timing.
Confirm step in your embedded flow
ChurnIntel supports structured steps through to Stripe cancel completion.