Skip to main content
Recurr’s default Apple posture is conservative: migration runs outside the app binary. That means the migration path uses owned channels and web surfaces rather than putting an external purchase prompt inside the iOS app.

​
Default lane

  • Subscriber is contacted through email or another owned channel
  • Subscriber completes checkout on web
  • The app binary is not changed for the migration path
  • The in-app purchase option is not removed as part of the migration
  • App access continues through the customer’s existing access model

​
Why this matters

The policy question is not just “can web billing exist?” The question is whether the app is directing users inside the iOS app to external payment in a way Apple prohibits, or whether the migration is operating through out-of-app communication and web surfaces. Nostos is designed around the second path.

​
Why not an in-app route?

Some platform-approved in-app or region-specific routes can come with extra platform conditions: entitlement applications, reporting obligations, eligibility limits, revised review risk, or additional platform fees. Recurr’s default lane avoids relying on those programs. The subscriber is reached through owned channels, completes billing on the web, and the app continues to provide access without turning the app binary into the place where the commercial switch is made.

​
Access after migration

After the subscriber moves billing rails, the app still needs to recognize the subscriber as paid. Recurr integrates with the customer’s access model - for example RevenueCat, Adapty, Stripe, Paddle, Firebase, or a custom backend - so access continuity is preserved.

​
Policy review

Apple policy changes over time, and regional rules can differ. Recurr reviews the customer-specific posture during migration scoping and documents the approach in the Migration Hub. For source policy, see Apple’s App Review Guidelines.