Purchases with RevenueCat
Subscriptions and in-app purchases through Apple and Google, with products and prices kept in your RevenueCat account.
- Asks for
- The public SDK key for each platform
- Runs in
- Native development and release builds
What RevenueCat does here
RevenueCat is the payment connector for digital purchases, subscriptions and premium access through the Apple and Google stores. Products, prices, entitlements and store credentials live in your RevenueCat account; Appsanic holds only the public SDK keys.
Set it up
Connect your Apple and Google apps in RevenueCat, create the store products, attach them to entitlements and add packages to an offering. Then save the matching public SDK keys in Connectors.
- In RevenueCat, create products, entitlements and an offering for your app.
- In Appsanic, open Connectors, choose RevenueCat and enter the public SDK key for each platform.
- Ask Sanic AI, or write the code, to build a subscription screen that loads real offering prices and connects purchase and restore buttons.
- Use active entitlements to decide what a person can see. Protected data on a backend must check paid access on the server too.
Test on a device
The browser preview and Expo Go cannot run the payment SDK, so purchases are tested in a native development build with store testing accounts. Check the connector's availability in code before offering a purchase. Appsanic never fakes a successful payment.
A Test Store key is optional and works only in a development build; Apple and Google keys follow the store account's own sandbox rules, so choosing Test in Appsanic alone does not make billing a sandbox.
What to try on a device
- A successful purchase, and a cancelled one.
- A pending payment and a restore on a second device.
- Repeated taps, entitlement changes and a refund.