Search docs/
Native SolutionsCore Device


Purchases is a cross platform solution for managing in-app subscriptions. A backend is also provided via RevenueCat


Server-side receipt validation
➡️ Webhooks - enhanced server-to-server communication with events for purchases, renewals, cancellations, and more
🎯 Subscription status tracking - know whether a user is subscribed whether they're on iOS, Android or web
📊 Analytics - automatic calculation of metrics like conversion, mrr, and churn
📝 Online documentation up to date
🔀 Integrations - over a dozen integrations to easily send purchase data where you need it
💯 Well maintained - frequent releases
📮 Great support - Help Center
🤩 Awesome new features

Getting Started

For more detailed information, you can view our complete documentation at

Stuck on a Cordova issue?

If you're building a serious project, you can't afford to spend hours troubleshooting. Ionic’s experts offer premium advisory services for both community plugins and premier plugins.

Contact Us Today!


ionic cordova plugin add cordova-plugin-purchasesnpm install @ionic-native/purchasesnpm install cordova-plugin-purchasesnpm install @ionic-native/purchasesionic cap sync
Ionic Native Enterprise comes with fully supported and maintained plugins from the Ionic Team. Learn More or if you're interested in an enterprise version of this plugin Contact Us

Supported Platforms

  • Android
  • iOS


Using React? See here.

1. Get a RevenueCat API key

Log in to the RevenueCat dashboard and obtain a free API key for your application.

2. Initialize the SDK

You should only configure Purchases once (usually on app launch) as soon as your app has a unique user id for your user. This can be when a user logs in if you have accounts or on launch if you can generate a random user identifier.

 import { Platform } from "@ionic/angular";
 import { Purchases } from "@ionic-native/purchases/ngx";

 constructor(public platform: Platform, private purchases: Purchases) {
     platform.ready().then(() => {
         this.purchases.setDebugLogsEnabled(true); // Enable to get debug logs
         this.purchases.setup("my_api_key", "my_app_user_id");

3. Displaying Available Products

Purchases will automatically fetch the latest active entitlements and get the product information from Apple or Google. This means when users launch your purchase screen, products will already be loaded.

Below is an example of fetching entitlements and launching an upsell screen.

     .subscribe(entitlements => ,
                error => );

4. Make a purchase

When it comes time to make a purchase, Purchases has a simple method, makePurchase. The code sample below shows the process of purchasing a product and confirming it unlocks the "my_entitlement_identifier" content.

     .subscribe(response => {
         if (response.purchaserInfo.activeEntitlements.includes("my_entitlement_identifier")) {
             // Unlock content
     ({ error, userCancelled }) => // Error making purchase. You can check error.userCancelled to check if user cancelled the purchase

makePurchase handles the underlying framework interaction and automatically validates purchases with Apple and Google through our secure servers. This helps reduce in-app purchase fraud and decreases the complexity of your app. Receipt tokens are stored remotely and always kept up-to-date.

5. Get Subscription Status

Purchases makes it easy to check what active subscriptions the current user has. This can be done two ways within the .purchaserInfo method:

  1. Checking active Entitlements - this lets you see what entitlements (from RevenueCat dashboard) are active for the user.
  2. Checking the active subscriptions - this lets you see what product ids (from iTunes Connect or Play Store) are active for the user.
     .subscribe(info => {
         // Option 1: Check if user has access to entitlement (from RevenueCat dashboard)
         const isPro =
             info.activeEntitlements !== "undefined" &&
         // Option 2: Check if user has active subscription (from App Store Connect or Play Store)
         const isPro =
             info.activeSubscriptions !== "undefined" &&
     error => );

Since the SDK updates and caches the latest PurchaserInfo when the app becomes active, the completion block in .purchaserInfo won't need to make a network request in most cases.

Restoring Purchases

Restoring purchases is a mechanism by which your user can restore their in-app purchases, reactivating any content that had previously been purchased from the same store account (Apple or Google).

If two different App User IDs try to restore transactions from the same underlying store account (Apple or Google) RevenueCat will create an alias between the two App User IDs and count them as the same user going forward.

This is a common if your app does not have accounts and is relying on RevenueCat's random App User IDs.

     .subscribe(info => {
          //... check purchaserInfo to see if entitlement is now active
     error => );

If you've provided your own App User ID, calling restoreTransactions could alias the logged in user to another generated App User ID that has made a purchase on the same device.

By default, RevenueCat will not let you reuse an App or Play Store account that already has an active subscription. If you set allowSharingAppStoreAccount = True the SDK will be permissive in accepting shared accounts, creating aliases as needed.

By default allowSharingAppStoreAccount is True for RevenueCat random App User IDs but must be enabled manually if you want to allow permissive sharing for your own App User IDs.


You can enabled detailed debug logs by setting debugLogsEnabled = true. You can set this before you configure Purchases.

this.purchases.setup("my_api_key", "my_app_user_id");


On iOS, disabling OS_ACTIVITY_MODE in your XCode scheme will block debug logs from printing in the console. If you have debug logs enabled, but don't see any output, go to Product -> Scheme -> Edit Scheme... in Xcode and uncheck the OS_ACTIVITY_MODE environment variable.

Example output:

[Purchases] - DEBUG: Debug logging enabled.
[Purchases] - DEBUG: SDK Version - 2.0.0
[Purchases] - DEBUG: Initial App User ID - (null)
[Purchases] - DEBUG: GET /v1/subscribers/<APP_USER_ID>
[Purchases] - DEBUG: GET /v1/subscribers/<APP_USER_ID>/products
[Purchases] - DEBUG: No cached entitlements, fetching
[Purchases] - DEBUG: Vending purchaserInfo from cache
[Purchases] - DEBUG: applicationDidBecomeActive
[Purchases] - DEBUG: GET /v1/subscribers/<APP_USER_ID>/products 200


An entitlement represents features or content that a user is "entitled" to. With Entitlements, you can set up your available in-app products remotely and control their availability without the need to update your app. For more information on configuring entitlements, look at our entitlements documetation.

Sample App

We've added an example showing a simple example using Purchases with the RevenueCat backend. Note that the pre-registered in app purchases in the demo apps are for illustration purposes only and may not be valid in App Store Connect. Set up your own purchases with RevenueCat when running the example.

Additional iOS Setup

Add Strip Frameworks Phase

The App Store, in it's infinite wisdom, still rejects fat frameworks, so we need to strip our framework before it is deployed. To do this, add the following script phase to your build.

  1. In Xcode, in project manager, select your app target.
  2. Open the Build Phases tab
  3. Add a new Run Script, name it Strip Frameworks
  4. Add the following command "${PROJECT_DIR}/../../node_modules/cordova-plugin-purchases/src/ios/" (quotes included)

Next Steps

Reporting Issues

You can use Github Issues to report any bugs and issues with Purchases. Here is some advice for users that want to report an issue:

  1. Make sure that you are using the latest version of Purchases. The issue that you are about to report may be already fixed in the latest master branch version:
  2. Providing reproducible steps for the issue will shorten the time it takes for it to be fixed - a Gist is always welcomed!
  3. Since some issues are Sandbox specific, specifying what environment you encountered the issue might help.

Technical Support or Questions

If you have questions or need help integrating Purchases please contact us or email instead of opening an issue.

Feature Requests

If there is something you'd like to see included or feel anything is missing you can add a feature to our public roadmap. If the feature already exists, or you see something else you'd like, upvote it.


Purchases SDK is free to use but some features require a paid plan. You can find more about that on our website on the pricing plan page.