Skip to main content
Recurr’s default Google Play posture is also out-of-app. Google’s own payments policy FAQ states that developers can communicate outside the app about alternative purchase options, including by email and other channels outside the app.

​
Default lane

  • Subscriber is contacted outside the app
  • Checkout happens on web
  • The Play-distributed app is not changed for the migration path
  • The app continues to grant access after web billing is active
  • Subscribers who remain on Play billing keep using the app

​
Why this matters

The migration does not need to turn the Android app into an alternate-billing prompt. The program can operate through owned channels and web surfaces while preserving the existing in-app product experience.

​
Why not an in-app route?

Platform alternate-billing programs can add program rules, reporting requirements, regional constraints, or platform fee exposure. Recurr’s default lane keeps the migration outside the app. The subscriber is reached through owned channels, checkout happens on web, and the existing Play purchase path can remain available for subscribers who stay there.

​
Refunds and support

Google Play and web billing have different refund and support paths. Migration support language should make the distinction clear so subscribers know where to go for store billing, web billing, cancellation, or app-access questions. For source policy, see Google’s Payments policy FAQ.