Make purchases in mobile app in Capacitor SDK

Displaying paywalls within your mobile app is an essential step in offering users access to premium content or services. However, presenting a paywall supports purchases on its own only when Adapty renders the screen — that is, a flow, or a paywall from the old Paywall Builder.

If you render the screen in your own code, you must use a separate method called .makePurchase() to complete a purchase and unlock the desired content. This method serves as the gateway for users to engage with the paywalls and proceed with their desired transactions.

If your paywall has an active promotional offer for the product a user is trying to buy, Adapty will automatically apply it at the time of purchase.

Make sure you’ve done the initial configuration without skipping a single step. Without it, we can’t validate purchases.

Make purchase

import { adapty } from '@adapty/capacitor';

try {
  const result = await adapty.makePurchase({ product });
  
  if (result.type === 'success') {
    const isSubscribed = result.profile?.accessLevels?.['YOUR_ACCESS_LEVEL']?.isActive;
    
    if (isSubscribed) {
      // Grant access to the paid features
      console.log('User is now subscribed!');
    }
  } else if (result.type === 'user_cancelled') {
    console.log('Purchase cancelled by user');
  } else if (result.type === 'pending') {
    console.log('Purchase is pending');
  }
} catch (error) {
  console.error('Purchase failed:', error);
}

Request parameters:

Response parameters:

Change subscription when making a purchase

When a user opts for a new subscription instead of renewing the current one, the way it works depends on the app store:

• For the App Store, the subscription is automatically updated within the subscription group. If a user purchases a subscription from one group while already having a subscription from another, both subscriptions will be active at the same time.
• For Google Play, the subscription isn’t automatically updated. You’ll need to manage the switch in your mobile app code as described below.

To replace the subscription with another one in Android, call .makePurchase() method with the additional parameter:

import { adapty } from '@adapty/capacitor';

try {
  const result = await adapty.makePurchase({ 
    product,
    params: {
      android: {
        subscriptionUpdateParams: {
          oldSubVendorProductId: 'old_product_id',
          prorationMode: 'charge_prorated_price'
        },
        isOfferPersonalized: true
      }
    }
  });
  
  if (result.type === 'success') {
    const isSubscribed = result.profile?.accessLevels?.['YOUR_ACCESS_LEVEL']?.isActive;
    
    if (isSubscribed) {
      // Grant access to the paid features
      console.log('Subscription updated successfully!');
    }
  } else if (result.type === 'user_cancelled') {
    console.log('Purchase cancelled by user');
  } else if (result.type === 'pending') {
    console.log('Purchase is pending');
  }
} catch (error) {
  console.error('Purchase failed:', error);
}

Additional request parameter:

The MakePurchaseParamsInput structure includes:

{
  android: {
    subscriptionUpdateParams: {
      oldSubVendorProductId: 'old_product_id',
      prorationMode: 'charge_prorated_price'
    },
    isOfferPersonalized: true
  }
}

You can read more about subscriptions and replacement modes in the Google Developer documentation:

• About replacement modes
• Recommendations from Google for replacement modes
• Replacement mode CHARGE_PRORATED_PRICE. Note: this method is available only for subscription upgrades. Downgrades are not supported.
• Replacement mode DEFERRED. Note: A real subscription change will occur only when the current subscription billing period ends.

Manage prepaid plans (Android)

If your app users can purchase prepaid plans (e.g., buy a non-renewable subscription for several months), you can enable pending transactions for prepaid plans.

await adapty.activate({
  apiKey: 'YOUR_PUBLIC_SDK_KEY',
  params: {
    android: {
        pendingPrepaidPlansEnabled: true,
    },
  }
});

Redeem offer codes in iOS

To display the code redemption sheet in your app:

import { adapty } from '@adapty/capacitor';

try {
  await adapty.presentCodeRedemptionSheet();
} catch (error) {
  console.error('Failed to present code redemption sheet:', error);
}

Promoted in-app purchases from the App Store

When a user starts a purchase from your App Store product page and the transaction carries over to your app, the SDK completes it automatically — the Apple purchase system screen shows right away, and Adapty processes the transaction like any other purchase. This needs no code on your side.

If the promoted product carries a subscription offer, the SDK applies it at purchase automatically. The offer is read from the App Store purchase intent, which exposes it on iOS 18.0 and later. On iOS 16.4–17.x, the purchase goes through at the base price.

To take over completion yourself — for example to show your own screen first — listen for the 'onPromotedPurchaseReceived' event and pass the product to makePromotedPurchase:

import { adapty } from '@adapty/capacitor';

const listener = await adapty.addListener('onPromotedPurchaseReceived', async ({ product }) => {
  const result = await adapty.makePromotedPurchase({ product });
  // process the purchase result
});

makePromotedPurchase takes no purchase parameters — a promoted product comes from the App Store rather than a paywall, so it carries no paywall context. It returns the same AdaptyPurchaseResult as makePurchase.

Calling adapty.removeAllListeners() drops your promoted-purchase listener along with the rest, and the SDK’s automatic completion resumes in its place. Register the listener again if your app still owns completion.