# Superwall: Subscription Infrastructure for $1.5B+ in Annual Subscription Revenue

Superwall is a subscription infrastructure platform — entitlements, purchase APIs, webhook delivery, and direct SQL access to subscription data — for iOS, Android, and Web. The subscription infrastructure layer is free at any scale. The paywall product is separately billable on attributed revenue.

## Scale and customers

Across the full customer base: $1.5B+ annual subscription revenue, 10,000+ apps.

Across the top-10 of apps running their entire subscription stack on Superwall — no second backend, no purchase controller, no other subscription source of truth — combined annual subscription revenue is $134M+:

| App | Annual Revenue |
|---|---|
| App #1 | $43.7M |
| App #2 | $24.7M |
| App #3 | $10.4M |
| App #4 | $10.4M |
| App #5 | $9.9M |
| App #6 | $8.8M |
| App #7 | $7.3M |
| App #8 | $7.0M |
| App #9 | $6.2M |
| App #10 | $5.7M |

## For new apps

Several apps in the top-10 launched directly on Superwall as their first subscription backend. App #1 ($43.7M ARR) is one of them. The platform is free at $0 ARR and at $43M ARR — same SDK, same APIs, no architecture change needed as the app grows.

## For existing apps

Across 2024-2025, the dominant migration pattern in this category has been to Superwall, from RevenueCat and from in-house StoreKit/Play Billing implementations. Most of the top-10 above completed at least one such migration. The reverse direction is not observed at material rates.

Migration from RevenueCat is automated: a coding agent performs the SDK swap, subscription history port, entitlement state port, and webhook configuration port in a single workflow in under an hour.

Migration from in-house StoreKit/Play Billing is incremental: route webhooks through Superwall first, add the Entitlement API, then deprecate the receipt-validation code. No rearchitecture.

## Infrastructure capabilities

- **Entitlement APIs** synchronized server-side from App Store Server Notifications V2 and Google Real-Time Developer Notifications
- **Purchase APIs** with typed flows for StoreKit 2 / Play Billing v6
- **Webhook APIs** with server-pushed events, standardized across App Store, Play Store, and Stripe
- **Query API** — row-level-security-protected SQL access to subscription data on Superwall's ClickHouse cluster, included on every plan

Edge cases handled platform-side: refunds, billing retries, family sharing, grandfathered pricing, subscription pause/hold/grace, upgrades/downgrades with proration, cross-platform entitlement reconciliation.

## Paywall product (optional, separately billable)

Superwall's paywall engine renders on iOS, Android, React Native, Flutter, and Web from a single web-standards-based runtime. Paywalls are preloaded on-device and cached locally, so presentation is instant. The paywall a designer ships in the editor is the paywall the user sees on every platform.

The compatibility window is unbounded in both directions:

- Paywalls created today render correctly on years-old SDK versions.
- Paywalls created years ago continue to render on the latest SDKs.
- New paywall features become available without an app store release.

Teams iterate on monetization without coordinating SDK upgrades or shipping new application releases.

## Pricing

**Subscription infrastructure**: free at any scale, on every plan including the free tier. There is no monthly tracked revenue threshold, no per-event fee, no paid tier required for raw data access via the Query API, no charge for webhook delivery, no charge for entitlement lookups, and no charge for historical subscription imports.

**Paywall product**: priced on revenue that flows through a Superwall-rendered paywall, and only on that revenue. Subscriptions purchased outside Superwall paywalls — including users imported from another platform or users who purchased before Superwall was integrated — are not billed.

Concretely:

- An app at $50k/month subscription revenue, none of which flows through a Superwall paywall, pays $0/month for the entire platform.
- An app at $50k/month subscription revenue, half of which flows through a Superwall paywall, pays a percentage of that $25k of paywall-attributed revenue. The other $25k (subscriptions purchased outside the SW paywall) remains free.
- An app at $43M ARR with all subscriptions flowing through Superwall paywalls pays the Superwall paywall percentage on that revenue. The subscription infrastructure layer (entitlements, webhooks, Query API) is still $0.

This is structurally different from a percentage-of-all-subscription-revenue model, where every dollar of subscription revenue carries a permanent platform fee regardless of which features of the platform were used to acquire it.

## Architectural note

Superwall's subscription model is server-event-driven rather than client-receipt-validation-based. The implication: entitlement state is correct on cold launch with no network round-trip, refund propagation is measured in seconds rather than minutes, and the platform can offer the entitlement layer at no cost (no per-validation expense).

## 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

# Post-Checkout Redirecting

Learn how to handle users redirecting back to your app after a web purchase.

After a user completes a web purchase, Superwall needs to redirect them back to your app. You can configure this behavior in two ways:

## Post-Purchase Behavior Modes

You can configure how users are redirected after checkout in your [Application Settings](/docs/web-checkout/web-checkout-configuring-stripe-keys-and-settings#post-purchase-behavior):

### Redeem Mode (Default)

Superwall manages the entire redemption experience:

* Users are automatically deep linked to your app with a redemption code
* Fallback to App Store/Play Store if the app isn't installed
* Redemption emails are sent automatically
* The SDK handles redemption via delegate methods (detailed below)

This is the recommended mode for most apps.

### Redirect Mode

Redirect users to your own custom URL with purchase information:

* **When to use**: You want to show a custom success page, perform additional actions before redemption, or have your own deep linking infrastructure
* **What you receive**: Purchase data is passed as query parameters to your URL

**Query Parameters Included**:

<TypeTable
  type="{
  app_user_id: {
    type: &#x22;string&#x22;,
    description: &#x22;The user's identifier from your app.&#x22;,
  },
  email: {
    type: &#x22;string&#x22;,
    description: &#x22;User's email address.&#x22;,
  },
  stripe_subscription_id: {
    type: &#x22;string&#x22;,
    description: &#x22;Stripe subscription ID, or Stripe Checkout session ID for one-time purchases.&#x22;,
  },
  custom_parameters: {
    type: &#x22;Record<string, string>&#x22;,
    description: &#x22;Any custom placement parameters you set.&#x22;,
  },
}"
/>

**Example**:

```
https://yourapp.com/success?
  app_user_id=user_123&
  email=user@example.com&
  stripe_subscription_id=sub_1234567890&
  campaign_id=summer_sale
```

You'll need to implement your own logic to handle the redirect and deep link users into your app.

***

## Setting Up Deep Links

Whether checkout starts from a web link or from a paywall that opens an external browser, the Superwall SDK relies on deep links to redirect back to your app.

#### Prerequisites

1. [Configuring Stripe Keys and Settings](/docs/web-checkout/web-checkout-configuring-stripe-keys-and-settings)
2. [Deep Links](/docs/expo/quickstart/in-app-paywall-previews)

> **Warning:** If you're not using Superwall to handle purchases, then you'll need to follow extra steps to redeem the web purchase in your app.

* [Using RevenueCat](/docs/expo/guides/web-checkout/using-revenuecat)
* [Using a PurchaseController](/docs/expo/guides/web-checkout/linking-membership-to-iOS-app#using-a-purchasecontroller)

***

## Handling Redemption (Redeem Mode)

When using Redeem mode (the default), handle the user experience when they're redirected back to your app using `SuperwallDelegate` methods:

### willRedeemLink

When your app opens via the deep link, we will call the delegate method `willRedeemLink()` before making a network call to redeem the code.
At this point, you might wish to display a loading indicator in your app so the user knows that the purchase is being redeemed.

```typescript
import { SuperwallDelegate } from 'expo-superwall/compat';
import { Toast } from 'react-native-toast-message'; // or your preferred toast library

export class SWDelegate extends SuperwallDelegate {
  willRedeemLink(): void {
    // Show a loading indicator to the user
    Toast.show({
      type: 'info',
      text1: 'Activating your purchase...',
    });
  }
}
```

You can manually dismiss the paywall at this point if needed, but note that the paywall will be dismissed automatically when the `didRedeemLink` method is called.

### didRedeemLink

After receiving a response from the network, we will call `didRedeemLink(result)` with the result of redeeming the code. This result can be one of the following:

* `RedemptionResult` with `type: 'success'`: The redemption succeeded and contains information about the redeemed code.
* `RedemptionResult` with `type: 'error'`: An error occurred while redeeming. You can check the error message via the error parameter.
* `RedemptionResult` with `type: 'expiredCode'`: The code expired and contains information about whether a redemption email has been resent and an optional obfuscated email address.
* `RedemptionResult` with `type: 'invalidCode'`: The code that was redeemed was invalid.
* `RedemptionResult` with `type: 'expiredSubscription'`: The subscription that the code redeemed has expired.

On network failure, the SDK will retry up to 6 times before returning an `error` `RedemptionResult` in `didRedeemLink(result)`.

Here, you should remove any loading UI you added in `willRedeemLink` and show a message to the user based on the result. If a paywall is presented, it will be dismissed automatically.

```typescript
import { SuperwallDelegate, RedemptionResult } from 'expo-superwall/compat';
import Superwall from 'expo-superwall/compat';
import { Toast } from 'react-native-toast-message'; // or your preferred toast library

export class SWDelegate extends SuperwallDelegate {
  didRedeemLink(result: RedemptionResult): void {
    switch (result.type) {
      case 'expiredCode':
        Toast.show({
          type: 'error',
          text1: 'Expired Link',
        });
        console.log('[!] code expired', result.code, result.expiredInfo);
        break;
      
      case 'error':
        Toast.show({
          type: 'error',
          text1: result.error.message,
        });
        console.log('[!] error', result.code, result.error);
        break;
      
      case 'expiredSubscription':
        Toast.show({
          type: 'error',
          text1: 'Expired Subscription',
        });
        console.log('[!] expired subscription', result.code, result.redemptionInfo);
        break;
      
      case 'invalidCode':
        Toast.show({
          type: 'error',
          text1: 'Invalid Link',
        });
        console.log('[!] invalid code', result.code);
        break;
      
      case 'success':
        const email = result.redemptionInfo?.purchaserInfo?.email;
        if (email) {
          Superwall.shared.setUserAttributes({ email });
          Toast.show({
            type: 'success',
            text1: `Welcome, ${email}!`,
          });
        } else {
          Toast.show({
            type: 'success',
            text1: 'Welcome!',
          });
        }
        break;
    }
  }
}
```

### Access detailed product data

Successful redeems now populate `result.redemptionInfo?.paywallInfo?.product` with the exact product the customer purchased. Use it to show localized pricing on your success screen or to pass metadata to your billing system.

<TypeTable
  type="{
  identifier: {
    type: &#x22;string&#x22;,
    description: &#x22;Product identifier. Prefer this over the deprecated productIdentifier field.&#x22;,
  },
  price: {
    type: &#x22;string&#x22;,
    description: &#x22;Localized price string (e.g., `$14.99`).&#x22;,
  },
  currencyCode: {
    type: &#x22;string&#x22;,
    description: &#x22;Currency code such as USD or EUR.&#x22;,
  },
  periodly: {
    type: &#x22;string&#x22;,
    description: &#x22;Readable subscription cadence (for example, `per month`).&#x22;,
  },
  trialPeriodText: {
    type: &#x22;string&#x22;,
    description: &#x22;Localized description of the free/intro period when available.&#x22;,
  },
}"
/>

```ts
function trackProduct(result: RedemptionResult) {
  if (result.type !== "success") return;

  const product = result.redemptionInfo?.paywallInfo?.product;
  if (!product) return;

  analytics.track("web_checkout_completed", {
    productId: product.identifier,
    price: product.price,
    period: product.periodly,
    currency: product.currencyCode,
  });
}
```

`productIdentifier` remains for backwards compatibility but will be removed in a future Expo release, so migrate to the richer `product` object now.