What continues
- App access
- Subscriber identity
- Plan entitlement
- Support path
- Renewal expectation
- Product experience
How it works
Most customers already have a place where subscription access is resolved: RevenueCat, Adapty, Stripe, Paddle, Firebase, or a custom backend. Recurr maps web subscription state into that access model so the app can continue recognizing paid subscribers after the billing rail changes.What is checked before launch
Before live migration, Recurr and the customer confirm:- The canonical subscriber identifier
- The current entitlement or access source
- How web subscription state is represented
- How renewal, cancellation, refund, and failed-payment states propagate
- How support diagnoses an access issue