AddThisFeature
Sign in

Subscription Cancellation Flow

Let people cancel without hiding what happens to their access and data.

involved Monetization

What it adds

A cancellation path that states the effective date, remaining access, data retention and any money involved, and can be undone before it takes effect.

What your agent is told to do

5
  1. 1

    Offer the choice between cancelling at the end of the paid period and cancelling immediately, and say what each one costs. Default to end-of-period.

  2. 2

    Disclose, on the confirmation screen, what happens to the account's data, how long it is retained, what access remains until the effective date, and whether anything is refundable.

  3. 3

    Let the user reverse the cancellation at any point before the effective date, and show the pending state everywhere the plan is displayed.

  4. 4

    Keep any reason survey optional and place it after the cancellation is already recorded. Do NOT gate the action behind a survey, a retention offer, or a support conversation — that converts churn into chargebacks.

  5. 5

    Subscription state, webhooks and payment methods are owned by Billing Portal; drive this flow from that state rather than tracking your own. Its rule that cancelled users keep access until the paid period ends still applies here.

Edge cases it handles

6
  • A cancellation that is scheduled but not yet effective is a distinct state. The UI must not describe the account as already cancelled or as fully active.
  • Immediate cancellation mid-period may generate a credit or may forfeit the remainder. Which one it is must be shown before confirming, not discovered afterwards.
  • An account already in a failed-payment grace period is cancelling from a different position. Do not promise access it does not have.
  • Cancellation by one admin affects every member of the workspace. Notify the owner, and refuse it from members who lack the permission.
  • The user may resubscribe before the effective date. Treat that as reversing the cancellation, not as a new subscription with a fresh trial.
  • If the provider call fails, the subscription is not cancelled. Report the failure — a confirmation screen shown over a failed request is the worst outcome here.

Definition of done

8
  • The user can choose between immediate and end-of-period cancellation, with the consequence of each stated.
  • The confirmation screen names the effective date, remaining access, data retention and any refund or credit.
  • A scheduled cancellation can be reversed by the user until its effective date.
  • No step of the flow requires answering a survey or contacting a human.
  • Pending cancellation is shown as its own state wherever plan status appears.
  • A failed provider call leaves the subscription unchanged and says so.
  • The feature matches the existing design system.
  • No existing functionality is broken.

Related features

How it works

  1. 1

    Copy the link

    Grab the Markdown instruction URL for this feature.

  2. 2

    Give it to your AI

    Paste it into Claude Code, Cursor, v0, Lovable — whatever you build with.

  3. 3

    It inspects, then implements

    Your agent reads your existing app first, then adds the feature to fit it.

Works with your stack

These instructions are written to adapt. They tell the agent to detect your framework, match your existing design system, and reuse what you already have — rather than assuming a particular stack.

Need it tighter than that? Customize the feature and tell it exactly what you're running.