Skip to main content

Documentation Index

Fetch the complete documentation index at: https://recurr.dev/docs/llms.txt

Use this file to discover all available pages before exploring further.

The integration is deliberately minimal. Recurr is not a library you embed; it’s a platform that operates alongside your existing app and entitlement systems.

​
What you don’t do

  • No SDK install. No new package in your app, no version pin, no compatibility surface.
  • No app release. The mobile app binary stays untouched through the migration.
  • No engineering-team build of migration logic. The platform runs the campaigns, dashboards, and webhooks.
  • No new auth flow. Your existing identity provider continues to authenticate subscribers.

​
What you do

1

OAuth or API-key into your entitlement system

Recurr connects to your existing entitlement source (RevenueCat, Adapty, your own system) so it knows who’s an active subscriber. OAuth is preferred; API keys work for systems without OAuth support.
2

Stripe Connect

A Stripe Connect Standard account is created in your name. Web payments settle directly to your account — Recurr takes its platform fee as an application fee on each charge.
3

DNS record for branded checkout

A CNAME for subscribe.yourdomain.com (or similar) points at Recurr-hosted checkout. Subscribers stay on your branded domain throughout the flow.
4

Webhook subscription

Recurr sends webhooks back to your entitlement system as subscriptions activate, renew, lapse, or churn. Your existing entitlement check at app open continues to work — the entitlement record now includes web subscriptions alongside store ones.
For apps with a centralized entitlement source, the whole integration typically lands in 2–4 hours of engineering time total, distributed across the four steps above.
StoreKit-only apps with no backend or entitlement provider Recurr can write into are not a current fit. See technical readiness.

​
What runs the migration

Once integrated, the migration itself runs on Recurr’s platform:
  • Email cadence — composed, sent, and tracked per cohort
  • Web checkout — branded, hosted, optimized for migration conversion
  • Cohort selection — multi-axis filters against your subscriber + entitlement data
  • Wave gating — observability dashboards across pilot and migration waves
  • Reporting — like-for-like analytics that hold the fee mix constant
Your team’s ongoing involvement is 1–2 hours per week during active migration, primarily reviewing wave performance and signing off the next cohort. Entitlements sync →