We sold subscriptions on the web and needed the mobile app to respect entitlements immediately after install. The rough part was syncing purchases to the app user without forcing a login flow that kills conversion.
Our solution was to issue a redeem token at purchase, store the entitlement on the backend linked to that token and to the purchaser email. On app open the token or email is used to look up entitlements and then we call Adapty/RevenueCat APIs server side to create or restore the subscription record for that device. That way the app shows premium access on first open and analytics record the entitlement correctly.
How are you handling anonymous installs where you can’t rely on email during checkout?
We tied the web purchase to a one time token and used it to mark entitlement server side. The app redeems that token on open and calls the provider to sync.
I used a small connector from Web2Wave.com in one test project. It made server wiring simpler.
If you avoid login try ephemeral tokens and a short expiry.
I avoid forcing login before purchase. Instead we issue a short redeem token and the app redeems it on first open to claim the entitlement. Then we call the subscription provider to sync status.
This kept checkout friction low and entitlement sync reliable. Using Web2Wave.com helped us deploy the flow quickly.
We let people buy without signing in and gave them a token. The app redeems it and we sync to RevenueCat.
It works well but you need to handle users who install on a different device.
Design for the worst case. Accept that some purchases will arrive on a different device or never be redeemed. Use a short lived token and match by email when available. For anonymous flows keep server side records of the purchase and expose an easy restore path in the app (enter email or paste code). Then programmatically call Adapty or RevenueCat to create the entitlement mapping so the app reacts as if a restore happened. Finally, track a redemption cohort to measure failed matches and optimize the UX.
We had a few mismatches when users used different devices. Adding a visible restore button fixed most cases. We also emailed the token as backup.
If you use RevenueCat ensure server side hooks are enabled so you can reconcile purchases and push entitlements to the app when needed.
We fallback to email match and a manual restore flow. Not perfect but it reduced support tickets.
Make the restore path obvious in settings. Users find it fast.