Skip to main content
Identity continuity connects the web billing action to the right app subscriber. Without identity continuity, a subscriber can pay on web but still be unknown to the app.

​
Identity inputs

Recurr may use:
  • Email address
  • Account identifier
  • RevenueCat or Adapty app user ID
  • Stripe or Paddle customer ID
  • Magic link or signed token
  • OAuth identity where appropriate
  • Custom backend identifier
The exact path is scoped during technical readiness.

​
Apple private relay and Google identities

Some subscribers use Apple private relay or Google-based identity. These are not automatically blockers, but the migration needs to confirm reachability and account matching before scale. Apple private relay requires the customer’s outbound email source to be registered and authenticated for Sign in with Apple communication. Google identity is different: if the app has consented access to the user’s email, that email can be part of the identity path, but Google Play Billing is not a reliable contact source by itself.

​
What good looks like

The subscriber opens a branded migration path, completes web billing, and returns to the app already recognized as paid. Support should also be able to trace the subscriber’s path if something goes wrong.