Use Adapty flows with your own payment system

You don’t have to move your purchases to Adapty to use its flows. In Observer mode, your code keeps making every purchase, while Adapty renders the paywall or onboarding, decides who sees it, A/B tests it, and reports on the result.

This guide covers what changes, what doesn’t, and what the setup takes.

Tip

New to flows? The Flow & Paywall Builder covers what you can build before you wire any of this up.

What stays yours, what Adapty takes over

Your code keeps:

  • The purchase call
  • Finishing and acknowledging transactions
  • Granting and revoking access
  • Renewals and billing retries

Adapty takes over:

Nothing about your billing changes. Adapty renders the flow and hands the purchase tap to your code, which makes the charge.

Create your products in Adapty

Skip this section if nothing in your flow shows a price or takes a purchase — a flow of onboarding screens alone needs no products in Adapty.

As soon as a screen presents products, create a product in Adapty for each subscription or one-time purchase it offers. A flow reads the price on the card from the product, so the card shows the current store price, you can A/B test that price, and Adapty groups revenue by product in analytics.

A product in Adapty points at the store product you already sell, so creating one doesn’t move billing: your code still makes every charge. Each product names an access level, and in Observer mode Adapty doesn’t grant it — your code keeps owning access — but a product needs one.

The Adapty CLI creates products without opening the dashboard. Install it (Node.js 18 or later) and sign in:

npm install -g adapty
adapty auth login

Get your app ID, then the access level to attach — every new app starts with a premium one:

adapty apps list
adapty access-levels list --app <app-id>

Then create one Adapty product for each store product you sell, using the product IDs from App Store Connect and Google Play Console:

adapty products create --app <app-id> --title "Monthly" --access-level-id <access-level-id> --period monthly --ios-product-id com.example.monthly --android-product-id com.example.monthly --android-base-plan-id monthly

Pass --period lifetime for a one-time purchase, and --stripe-product-id with --stripe-price-id (or the Paddle pair) for something you sell on the web. products create lists every flag. Store product IDs can’t be changed after creation, so pointing a product at a different store product means creating a new product.

Warning

A product element with nothing assigned blocks saving and publishing, so you find out in the builder. A Purchase action with no product set saves fine and fails on the device — the button does nothing. Set a product on every Purchase action.

Or skip products and write prices as static text

A flow with no product element saves and publishes, so you can type prices into the text and have your own code decide what a tap buys. What it costs you:

  • You keep every price in two places — the store and the flow’s text — and they drift as soon as you change one.
  • No price A/B tests, which is most of what a flow is for.
  • Charts and integrations group revenue less cleanly, since Adapty only learns the product from the transaction you report.
  • Your code maps each tapped element to a product, instead of receiving one from the flow.

Set it up

  1. Activate the SDK in Observer mode. Turn on observerMode when you configure the SDK: iOS, Android, React Native, Flutter, Unity, Kotlin Multiplatform, Capacitor.
  2. Create your products in Adapty, unless nothing in the flow shows a price. One CLI command per product — see Create your products in Adapty.
  3. Build the flow. See the Flow & Paywall Builder for the screens, set up purchases for products on a paywall screen, and create a placement to decide where the flow appears in your app.
  4. Present the flow and make the purchase in your own code. Adapty hands the purchase tap to a handler you register.
  5. Report the transaction with the paywall variation ID of the purchased product, so the purchase reaches analytics attributed to the paywall that sold it.

Steps 4 and 5 differ per platform. In every snippet, flow is the AdaptyFlow you fetched for the placement, product is the AdaptyPaywallProduct the user tapped, and myPurchaseApi or yourBillingClient stands in for the purchase code you already have.

Observer mode limits

  • Adapty doesn’t grant access: It doesn’t respond to purchase events by giving or restricting paid access, and it doesn’t handle renewals or billing retries. Your own code owns access levels.
  • Your code finishes its own transactions: Adapty doesn’t finish or acknowledge the purchases your code makes, so closing each one stays your job.
  • Reporting isn’t optional: The variationId you pass with a report is the only link between a purchase and the flow that produced it. Report every transaction, or your flow metrics and A/B test results are wrong.

If you’re already using another vendor

Observer mode only requires that your code makes the purchase — not whose SDK that code calls. Flows work the same on top of RevenueCat, Superwall, or Qonversion as on top of your own StoreKit or Billing Library code.

Three decisions to make before you ship:

  • One system finishes each transaction: Two SDKs both finishing the same purchase is the most common failure here.
  • One system owns access: Adapty grants nothing in Observer mode, so keep access levels where they are.
  • Report each purchase once: Reporting the same transaction from two places distorts your analytics.

To move off the other vendor entirely instead, see Migrate from RevenueCat or Migrate from Superwall.

Let Adapty make the purchase instead

Tip

Your app buys through Adapty here, so the code side is a normal Adapty integration. Follow the quickstart or Migrate from RevenueCat, or hand it to the SDK integration skill.

Observer mode is the quick way in. If you want to keep RevenueCat’s analytics but avoid the Observer mode limits, invert the two: Adapty runs in full mode and completes every purchase, while RevenueCat runs in its own observer mode and records the purchases Adapty makes.

Adapty then knows which flow, placement, and A/B test variation produced each charge, and it grants access levels and handles renewals, billing retries, and refunds.

On the RevenueCat side, set purchasesAreCompletedBy to your app when you configure its SDK — .myApp on iOS, MY_APP on Android. RevenueCat’s Using the SDK with your own IAP code has the configuration for each platform, the StoreKit version iOS requires, and the syncPurchases() call that pulls in purchases a customer already made. Give both SDKs the same user ID — Adapty’s customer user ID and RevenueCat’s appUserID — or the two dashboards describe different people.

Warning

This arrangement ends RevenueCat entitlements as your source of truth, and Adapty access levels take that role. RevenueCat keeps observing, and its dashboard keeps reporting, but it now learns of each purchase second-hand and within the coverage limits its own documentation lists. Anything that reads RevenueCat entitlements today — your app, your backend, a web or desktop build — either moves to Adapty or reads a copy. Settle that before you ship. Nothing else moves: the RevenueCat account, its history, and its integrations stay where they are.