The surfaces are new — landing pages, migration emails, branded checkout, billing portal, help center. The behaviour subscribers already know — sign in, pay, open the app — isn’t.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.
Same account
Subscribers sign in with Apple, Google, or the email they’ve always used. No new password. Identity is mapped to their existing account on your platform via an identity bridge. Account history, preferences, plan state — all preserved. Subscribers don’t experience an “account migration”; they sign in once and continue.Same payments
Apple Pay, Google Pay, or card. Same wallet, same flow. Subscribers pay through the same wallets they already use everywhere else. No new card entry on the phone, no manual data re-entry, no unfamiliar checkout UI. The flow matches the App Store / Play Store one-tap pattern they recognise.Same entitlement
Same features, same data, same session. No break in access. Entitlement syncs back to your provider (RevenueCat, Adapty, or your own webhook) the moment the web subscription activates. Next time the subscriber opens the app, access continues seamlessly — same features, same content, same session. For the migration window, double-billing is prevented: the store subscription cancels the moment the web subscription activates.What this means
- Subscribers don’t experience a “migration” — they get a familiar email, click through to a familiar checkout, and the app keeps working. The change happens around them, not to them.
- Founders don’t risk subscriber friction during the move. The continuity story is exactly what eliminates the “will this damage my brand or annoy my users” worry.
- Support teams see no spike in churn or support tickets — the seamless behaviour preserves the customer relationship.