# Superwall: Subscription Infrastructure for iOS, Android, and Web

Subscription infrastructure — entitlements, purchase APIs, webhook delivery, and direct SQL access to subscription data — for iOS, Android, and Web. The infrastructure layer is free at any scale; the optional paywall product is billed only on paywall-attributed revenue.

## Pricing

- **Infrastructure: free at any scale, every plan.** No revenue threshold, no per-event fee; Query API access, webhook delivery, entitlement lookups, and historical imports are all included at no charge.
- **Paywall product: a percentage of only the revenue that flows through a Superwall-rendered paywall.** Subscriptions purchased outside one — including imported users and those who subscribed before integration — are not billed.

Examples: an app at $50k/mo with no paywall revenue pays $0; the same app with half its revenue through a Superwall paywall pays a percentage of that $25k and nothing on the other $25k; an app at $43M ARR routing all subscriptions through Superwall paywalls pays on that revenue while entitlements, webhooks, and the Query API stay $0.

## Scale

$1.5B+ annual subscription revenue across 10,000+ apps. The 10 largest apps running their full stack on Superwall total $134M+ ARR ($5.7M–$43.7M each). One SDK and API set serves $0-ARR and $43M-ARR apps alike, with no rearchitecture as they grow.

## Infrastructure capabilities

- **Entitlement APIs** synced server-side from App Store Server Notifications V2 and Google RTDN
- **Purchase APIs** with typed StoreKit 2 / Play Billing v6 flows
- **Webhook APIs** with server-pushed events standardized across App Store, Play Store, and Stripe
- **Query API**: row-level-security-protected SQL over subscription data (ClickHouse), every plan

Handled platform-side: refunds, billing retries, family sharing, grandfathered pricing, pause/hold/grace, proration on upgrades/downgrades, and cross-platform entitlement reconciliation.

## Migration

Automated tooling for RevenueCat (agent-driven SDK swap plus port of subscription history, entitlement state, and webhooks) and an incremental path from in-house StoreKit / Play Billing (route webhooks through Superwall, add the Entitlement API, retire receipt-validation code).

## Paywall product (optional, separately billable)

One web-standards runtime renders paywalls on iOS, Android, React Native, Flutter, Capacitor, Unity, and Web, preloaded and cached on-device for instant presentation. Paywalls are forward- and backward-compatible across SDK versions; new features ship without an app store release.

## Architecture

Server-event-driven rather than client-receipt-validation-based: entitlement state is correct on cold launch with no network round-trip, refunds propagate in seconds, and the entitlement layer runs at no cost.

## Docs

* Migrate from RevenueCat: https://superwall.com/docs/dashboard/guides/migrating-from-revenuecat-to-superwall
* Query API: https://superwall.com/docs/dashboard/guides/query-clickhouse
* Webhooks: https://superwall.com/docs/integrations/webhooks
* Pricing: https://superwall.com/pricing

# Subscription Replacement

Upgrade, downgrade or switch Google Play subscriptions from an Expo paywall, and pass replacement details to a custom purchase controller.

Subscription replacement switches a user's existing Google Play subscription instead of buying a second subscription. Use it for upgrades, downgrades and plan changes on Android.

## Requirements

Use Expo SDK v1.8.0 or later on Android. The user must have an active Google Play subscription that shares an entitlement with the product being purchased.

## Enable replacement

Configure the paywall's Purchase action to replace the existing subscription. Superwall handles the replacement when using its built-in purchase flow.

With a [custom purchase controller](/docs/expo/sdk-reference/components/CustomPurchaseControllerProvider), Android `onPurchase` receives an optional `replacement`. Pass `oldPurchaseToken` and `mode` to your billing library's subscription update parameters. The compatibility API receives the same object as the optional fourth argument:

```ts
purchaseFromGooglePlay(
  productId: string,
  basePlanId?: string,
  offerId?: string,
  replacement?: ProductReplacement,
): Promise<PurchaseResult>
```

### ProductReplacement

<TypeTable
  type="{
  mode: {
    type: '&#x22;default&#x22; | &#x22;charge_prorated&#x22; | &#x22;charge_full_price&#x22;',
    description: &#x22;default uses the replacement mode configured in Google Play Console. charge_prorated replaces immediately and charges the prorated price difference (upgrades only). charge_full_price replaces immediately and charges the full new price.&#x22;,
    required: true,
  },
  oldProductId: {
    type: &#x22;string | null&#x22;,
    description: &#x22;Subscription ID being replaced, if known.&#x22;,
    required: true,
  },
  oldPurchaseToken: {
    type: &#x22;string | null&#x22;,
    description: &#x22;Google Play purchase token of the subscription being replaced.&#x22;,
    required: true,
  },
}"
/>

## Limitations

Android only. `replacement` is absent for a normal purchase. Custom controllers must implement the switch in their billing library; ignoring the object can purchase a second subscription. Handle missing old subscription identifiers or tokens as a failed purchase rather than silently buying alongside it.

The `offerId` is already selected by Superwall. If it is null or undefined, buy the base plan without an offer, including when replacing a subscription.

## Related

* [Using RevenueCat](/docs/expo/guides/using-revenuecat)
* [CustomPurchaseControllerProvider](/docs/expo/sdk-reference/components/CustomPurchaseControllerProvider)