Concepts
The mental model behind the Unchurn retention engine — how it scores eligibility, how it routes offers, what each offer is wagering on, and where Stripe stays the source of truth. Read these once before you integrate to make the rest of the docs make sense, or pull them up when the Quickstart leaves you with a question.
Start here if…
- You’ve never seen Unchurn before — How the cancel flow works is the right opener.
- You’re picking which offers to ship first — go straight to The five offers.
- A session in your dashboard says “manual cancellation request” and you want to know why — Eligibility.
- You’re setting up test and live environments — Test and live modes.
- You’re doing a security or trust-team review — Architecture.
All pages
| Page | What you’ll learn |
|---|---|
| How the cancel flow works | The life of one cancel session, from button click to Stripe change. |
| The five offers | The retention bet behind each offer, when to deploy it, when not to. |
| Eligibility | Why some subscriptions skip retention offers and go straight to a manual cancellation request. |
| Test and live modes | How the two modes stay separated and why the widget refuses to mix them. |
| Architecture | Which system owns the session, and where Stripe stays the source of truth. |
Looking for how to do something specific? Widget reference. Need the exact subscription shapes each offer applies to? Supported subscriptions.