Skip to main content
Access continuity is the goal. The implementation depends on the access model your app already uses. Recurr does not need to replace RevenueCat, Adapty, Stripe, Paddle, Firebase, or your custom backend. It needs to fit into the system that already decides whether a subscriber has access.

​
Common access models

RevenueCat

Recurr maps web subscription state into the app’s existing RevenueCat-backed access model where applicable.

Adapty

Recurr works with the existing subscription and entitlement model rather than replacing the app-side SDK.

Stripe or Paddle

Web billing state can be recognized directly where the payment rail is already connected to access.

Custom backend

Custom access logic is scoped during technical readiness and pilot onboarding.

​
What needs to be true

Before migration, the team confirms:
  • The canonical subscriber identifier
  • The source of truth for app access
  • The state changes that grant, renew, cancel, or revoke access
  • How web subscription state enters that model
  • How support diagnoses access issues

​
What subscribers see

The best implementation is invisible to subscribers. They move to web billing, return to the app, and keep using the product.