Documentation.

Last updated: October 2026

Moored has no frontend SDK. You hand the cancellation off to us, we run your deterministic rules against the billing provider, and we send the user home. Three steps, one snippet.

1. Hand off the cancellation

Point your app's cancel button at your project's exit URL, appending the subscription reference. Create the project first in your dashboard, then link out (grab the ready-made link plus React / Vue / HTML snippets under Dashboard → Installation — it follows this shape):

https://moored.org/exit/[project_id]?subscription_id=123&email=user@co.com&plan_mrr_cents=2900

That is the entire integration. No JavaScript to install, no webhooks to configure, no version to pin.

subscription_id

is required;

email

and

plan_mrr_cents

(2900 = $29.00) are optional — when your Dodo key is connected under Integrations, Moored resolves the email and plan value straight from the subscription, and the value powers your saved-MRR analytics.

2. We execute your rules

Moored reads the URL, pulls the subscription with your connected API keys, and runs your rule set in order. Each cancellation reason maps to exactly one action — discount, pause, or clean cancellation — applied through the provider's native API. No models, no latency, no surprises. Configure mappings under Dashboard → Rule Engine.

3. We return the user

After the offer is accepted or the cancellation completes, we redirect to your project's Success / Return URL (Dashboard → Project Settings → Routing). Pass per-session context back by templating it into the URL you save.

4. Connect billing providers

One project can hold Stripe, Paddle, Dodo Payments, and Lemon Squeezy simultaneously — the exit flow picks the right adapter per subscription. Paste keys under Dashboard → Integrations; they are AES-GCM encrypted at rest and only the last four characters are ever displayed back to you.

5. Design the exit modal

Dashboard → Design Editor offers a 48-block library (headers, reason pickers, offer cards, trust strips) with per-block sizing, plus brand color, logo, headline, and alignment controls. Advanced teams can inject raw HTML/CSS to override the modal completely. Press Test Cancel Flow to run the exact survey → offer → outcome machine against your live rules before shipping.

6. Sessions, tiers, and limits

Each unique customer entering the exit flow counts one Monthly Active Cancellation Session against your tier (Sandbox 10, Micro 30, Starter 100, Growth 350, Enterprise unlimited). Past the limit, visitors fall through to your provider's standard cancellation page and you get an upgrade nudge — a cancellation is never trapped. Track usage live under Dashboard → Billing.

7. Testing without charging anyone

Keep a Sandbox-tier project with test-mode gateway keys for rehearsal, use the landing-page sandbox for the raw UX, and replay gateway events any time from Admin → Webhook Simulator. Nothing in a simulator touches real money.

8. Security model

TLS everywhere, encrypted keys, per-project tenant isolation on every query, and irreversible password hashes. Full details live in the Privacy Policy. Questions or early-access requests: allurance.business@gmail.com.