Subscription integration

Your paywall stays. Subscription status reaches your backend.

Keep Adapty and store billing exactly as they are. Backapp reads the access level your integration reports and uses it when your app calls a supported workflow — no webhook handlers or entitlement tables of your own.

Adapty · purchase completed
access level premium granted
● active
Backapp · subscription statusExample output
{
  "user_id": "user_8f2a…",
  "provider": "adapty",
  "access_level": "premium",
  "status": "active"
}
Transcription
request accepted
Image generation
request accepted
01

Keep your paywall

Paywalls, products and store receipts stay in Adapty. Backapp only needs to know the outcome.

02

No webhook plumbing

Backapp receives subscription events and keeps status current. You don’t host an endpoint or an entitlement table.

03

Checked on every request

Supported workflows read the user’s status before they run — the client can’t skip the paywall by calling the API directly.

How it works

Connect once. Status follows the user.

  1. 1
    Connect Adapty to your Backapp project.
    Add the Backapp integration in Adapty and paste the key into your project settings.
  2. 2
    Choose which access level counts as subscribed.
    Map an Adapty access level — e.g. premium — to “subscribed” in Backapp.
  3. 3
    Identify the user to Adapty with their Backapp ID.
    Purchases then land on the same user record. Supported workflows check that status on each request.
React Native · identify + purchase
// CONTENT PENDING: replace with the verified example
import { adapty } from 'react-native-adapty';

// 1. tell Adapty who this Backapp user is
await adapty.identify(user.id);

// 2. your paywall / purchase stays in Adapty
const profile = await adapty.makePurchase(product);

// 3. Backapp already has the status — just call a workflow
const res = await fetch(`${BACKAPP_API_URL}/ai/transcriptions`, {
  method: 'POST',
  headers: { Authorization: `Bearer ${token}` },
  body: form,
});
// 402 subscription_required if the access level isn't active

What Backapp knows about a subscription.

Status is stored on the user record. Your integration writes it; supported workflows read it. You never update it by hand.

Subscription fields on every user
provider
"adapty" today; RevenueCat when confirmed.
access_level
The Adapty access level currently granted, e.g. "premium".
status
active, trial, expired or none — what workflows check.
expires_at
When the current period ends.
will_renew
Whether the store expects the subscription to renew.
Available today

Adapty

Access levels from Adapty map directly to subscribed / not subscribed in Backapp. Trials, renewals and cancellations update automatically.

Scope being confirmed

RevenueCat

RevenueCat entitlement support is being scoped. It will follow the same model: entitlement → subscribed, checked per request.

Subscription in the stack

Status lives where the rest of Backapp can read it.

Identity, usage limits and AI workflows all look at the same subscription field — nothing to sync between systems.

Questions about subscriptions?

Do I need to change my paywall?

No. Paywalls, products and purchases stay in Adapty. Backapp only reads the resulting access level.

Does Backapp process payments?

No. Billing is handled by the App Store and Google Play through Adapty. Backapp never touches receipts or card details.

What happens when a subscription expires or is refunded?

Adapty reports the change and Backapp updates the user’s status. The next supported workflow request from that user is declined with subscription_required.

Can I let free users try a workflow?

Which workflows require an active subscription is configured per project; free allowances are covered under Usage and limits.

Is RevenueCat supported?

RevenueCat scope is being confirmed. Adapty is the supported integration today.

Ship without building entitlement logic.

Identity, subscriptions and AI workflows from one backend.