# 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

# Customer Center

Let customers manage purchases, restore transactions, request refunds, and contact support from a native screen.

The Customer Center is a native self-service screen for purchases. It can show active and expired subscriptions, one-time purchases, and entitlements. Customers can restore purchases, manage or cancel subscriptions, change plans, request refunds, open support links, and contact your team. It supports App Store and Google Play purchases as well as Superwall web checkout.

Expo SDK v1.6.0 adds Customer Center support on iOS and Android. The default configuration is ready to use; configure it only when you want to change the screens, paths, appearance, or support details.

## Present the Customer Center

Call `presentCustomerCenter()` from a component inside `<SuperwallProvider />`. Its promise resolves when the screen is dismissed:

```tsx
import { Button } from "react-native";
import { useSuperwall } from "expo-superwall";

export function ManagePurchasesButton() {
  const { presentCustomerCenter } = useSuperwall();

  return (
    <Button
      title="Manage purchases"
      onPress={() => {
        void presentCustomerCenter({
          onAction: (action, pathId, purchase) => {
            if (action.type === "custom") {
              openAccountSettings(action.identifier);
            }
            console.log("Customer Center path selected", pathId, purchase?.productId);
          },
        });
      }}
    />
  );
}
```

The `onAction` callback runs before an action. Built-in paths continue automatically. A `custom` path does not perform an action on its own, so handle it in this callback. The callback's `purchase` is `null` for screen-level actions such as Restore purchases.

Only one Customer Center can be presented at a time. Calling `presentCustomerCenter()` while it is already open resolves immediately. The promise also resolves immediately if the native screen cannot be presented. Use `dismissCustomerCenter()` to dismiss it from your app.

The compatibility API is available for apps using `expo-superwall/compat`:

```tsx
import Superwall from "expo-superwall/compat";

await Superwall.shared.presentCustomerCenter();
```

## Configure the screen

Set `customerCenter` on the provider's `options` to customize the default screen. Omitted fields keep their native defaults:

```tsx
<SuperwallProvider
  apiKeys={{ ios: "ios_key", android: "android_key" }}
  options={{
    customerCenter: {
      support: { email: "support@example.com" },
      appearance: {
        accent: { light: "#5B5FEF", dark: "#9A9DFF" },
      },
    },
  }}
>
  {/* Your app */}
</SuperwallProvider>
```

You can also pass `configuration` to `presentCustomerCenter()` to override the provider configuration for one presentation. Use `managementScreen` and `noPurchasesScreen` to choose screen titles and paths, or `support` to set a support email, app version, or web subscription-management URL. See the [Customer Center API reference](/docs/expo/sdk-reference/customer-center) for all fields and path types.

With the compatibility API, pass the same configuration through `SuperwallOptions` when configuring:

```tsx
import Superwall from "expo-superwall/compat";
import { SuperwallOptions } from "expo-superwall/compat";

await Superwall.configure({
  apiKey: "YOUR_API_KEY",
  options: new SuperwallOptions({
    customerCenter: { support: { email: "support@example.com" } },
  }),
});
```

To ask the app before restoring purchases, pass `shouldRestorePurchases`. Return `false` to cancel, such as when the customer declines to sign in. If the callback throws, the restore proceeds. `onSurveyComplete` and `onRefundRequestComplete` let you respond to those outcomes. The Customer Center also emits Superwall events; see [Customer Center and Teleport events](/docs/expo/sdk-reference/hooks/useSuperwallEvents#customer-center-and-teleport-events).

## Platform notes

* On iOS, Customer Center requires iOS 15 or later and SuperwallKit 4.18.0. Building with Expo SDK v1.6.0 requires Xcode 26 or later.
* On Android, the Customer Center uses the native SDK's full-screen activity and requires Superwall Android 2.8.5 or later; Expo v1.6.0 includes Android 2.8.7.
* `checksAppStoreForUpdates` and the `userCancelled` refund status are iOS only. Refund requests on Android open Google Play's order history; `success` means that page opened, not that Google granted a refund.

For the complete API, callbacks, and event fields, see the [Customer Center API reference](/docs/expo/sdk-reference/customer-center).