A cancellation flow on Stripe, and where it stops
Stripe gives you a hosted cancellation page, a reason survey and a retention coupon without any code. Here is how to set them up, what they cannot do, and when it is worth adding a tool.
By the Churnly team. Updated November 21, 2026.
What a cancellation flow is for
When a customer decides to leave, you have one short moment to learn why and, if it makes sense, offer something that changes their mind. A good flow does three things: it asks one question, it offers a single relevant alternative, and it makes cancelling easy if the customer still wants to go. Hiding the cancel button costs you trust and invites chargebacks, so do not.
Set up the Stripe customer portal
The customer portal is Stripe's hosted page for managing a subscription. Cancellation is on by default. Under Settings, Billing, Customer portal in the Dashboard you can configure the cancellation page:
- Collect a cancellation reason. Choose which of Stripe's reasons customers see: too expensive, need more features, found an alternative, no longer needed, customer service, ease of use, quality, other. An "other" answer lets them type free text.
- Show lost benefits. Write a short message (up to 80 characters) for each marketing feature on your product, so the cancel page reminds people what they will lose. Do this in the Product catalog, per feature.
- Offer a retention coupon. In the Cancellations section, pick a coupon from the dropdown, or create one inline. It is offered when someone cancels.
The selected reason is stored on the subscription, appears in Sigma, and arrives in the customer.subscription.updated webhook. In the API it is cancellation_details.feedback, with values such as too_expensive, missing_features and switched_service.
You can also send a customer straight to the cancel step with a portal deep link. That helps when you want your own button, in an email or in your app, to land on the right page.
Pause, the offer people forget
Stripe can pause payment collection on a subscription for a set time or until you resume it. The subscription stays active, invoices keep generating, and Stripe stops collecting. You decide whether those invoices stay as drafts, are marked uncollectible, or are voided, through pause_collection[behavior]. Set resumes_at and billing restarts on its own.
Note the trade-off. A paused subscription still has access unless you remove it, so decide first whether a pause means free service for a month or a locked account. Stripe's pause page makes that distinction clearly, and there is a separate option to pause the subscription itself.
Cancel now or at period end
By default the API cancels immediately. Setting cancel_at_period_end to true lets the customer keep what they paid for until the period ends, and you can still stop the cancellation until then ("Don't cancel" in the Dashboard, or setting the flag back to false). How the portal handles period-end cancellation depends on the subscription's billing mode, so test with a real subscription in a sandbox before you rely on it. The cancel subscriptions page has the details.
The period-end route buys you something useful. Between the click and the end date you still have an active customer to talk to.
What to offer for each reason
- Too expensive. A time-limited coupon or a cheaper plan. Ask what they would pay, if you can.
- Missing features. Ask which one. If it is on your roadmap, say when. A discount does not fix a gap.
- Found an alternative. Ask which and why. Keep the door open and skip the discount.
- No longer needed. A pause or a downgrade to a smaller plan, and a promise to keep their data.
Where the built-in version stops
- One coupon for everyone. The portal offers the coupon you select. The docs do not describe choosing a different offer for different reasons. Someone who says "too expensive" and someone who says "I no longer need it" get the same thing.
- No conversation. A reason goes into a field. Nobody replies, unless you build that yourself.
- Little testing. You cannot run two versions of the page and compare saves.
- Nothing after the click. Once the subscription ends, Stripe's automations can send a confirmation email, optionally with a reason survey, but not a win-back sequence.
A small, honest flow you can run today
- Turn on cancellation reasons and the lost-benefits copy.
- Create one retention coupon you could live with: for example, 25% off for three months, one redemption per customer.
- Email yourself, or your team, when
customer.subscription.updatedshows a scheduled cancellation, using a Stripe automation or a webhook. - Reply to each person within a day. A real answer from the founder does more than any page.
- Once a month, count reasons. If "too expensive" is a fifth of your cancellations, test pricing, not coupons.
When to add a tool
If you get more cancellations than you can answer, or you want different offers by reason and by plan, look at a dedicated flow. Churnkey, ProsperStack and Raaft embed one in your product. Churnly works differently: it has no cancel page, but it notices a scheduled cancellation in Stripe, drafts a personal save (a message, a coupon or a pause) and waits for your approval. We compare all of them in the comparison hub, including what Stripe's built-in tools cover.
Keep reading
- Reduce churn on StripeFailed payments, cancellations and win-back, in the order to fix them.
- Win back canceled customersSegment by reason, a 7, 30 and 90 day cadence, five short letters.
- Churn prevention software comparedPrices and coverage for Churnkey, Churn Buster and the rest.
Keep the customers you already have.
Connect Stripe and Churnly starts watching for failed payments and cancellations. Every message waits for your approval.
Start at $19/mo