# 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

# App2Web

Link U.S. customers from iOS paywalls to Safari for Stripe checkout.

For customers on the United States App Store storefront, you can add calls to action in your iOS paywalls that open Stripe checkout outside of your app in Safari or the user's default browser.

Do not present Stripe Checkout inside your iOS app using an in-app browser, `SFSafariViewController`, `WKWebView`, or another embedded web view. For external purchase links, the checkout flow should leave the app and open in the external browser.

> **Note:** Apple's App Review Guidelines allow United States storefront apps to include buttons, external links, or calls to action for purchase methods other than in-app purchase. Review [Guideline 3.1.1(a)](https://developer.apple.com/app-store/review/guidelines/#business) before submitting your app.

![](https://claude-centralize-agent-preamble-superwall-docs.staffbar.workers.dev/docs/images/web_checkout_direct_to_stripe.jpg)

## Configure Web Checkout

First, follow the [web checkout setup guide](/docs/web-checkout#getting-setup) to create a Stripe app and configure your web checkout settings. Specifically, you'll need to complete the first three steps. This includes installing the [Superwall Stripe app](https://marketplace.stripe.com/apps/superwall), setting up your app's settings, and adding your Superwall web paywall domain to Stripe if you want Apple Pay to appear in checkout.

## Add a Stripe product to an iOS paywall

Select a paywall and add a Stripe product to it. This lets users start an external browser checkout flow from the paywall. Stripe products are prepended with "stripe" in the product selector:
![](https://claude-centralize-agent-preamble-superwall-docs.staffbar.workers.dev/docs/images/web-checkout-select-product.png)

## Create a campaign for U.S. customers

Since the policy applies to customers on the United States storefront, create a campaign filter that matches those customers. Use `storeFrontCountryCode` equals `USA`, like this:> **Note:** For App Review, explain that U.S. storefront customers can tap a paywall call to action that opens an external browser for Stripe checkout. Non-U.S. storefront customers should continue using Apple in-app purchase unless another regional policy applies.

![](https://claude-centralize-agent-preamble-superwall-docs.staffbar.workers.dev/docs/images/web-checkout-app2web-campaign-filter.png)

## Respond to Checkout

From there, the flow works the same way as web checkout. Once the payment succeeds in the external browser, the [Superwall delegate](/docs/sdk/guides/using-superwall-delegate) functions `willRedeemLink()` and `didRedeemLink(result:)` will be called when the user returns through the deep link. You can use these functions to show any specific UI as described in our [Post-Checkout Redirecting](/docs/sdk/guides/web-checkout/post-checkout-redirecting) docs.Additionally, entitlement and subscription status will update automatically. For lifetime one-time products, the linked entitlement becomes active without an expiration. For consumables, inspect `CustomerInfo.nonSubscriptions` and grant the purchased quantity in your own system. If you're using a `PurchaseController`, refer to [the docs here](/docs/sdk/guides/web-checkout/linking-membership-to-iOS-app#using-a-purchasecontroller).

If you need to test checkout, learn how [here](/docs/web-checkout/web-checkout-testing-purchases).

### Apple Pay

App2Web checkout opens from your iOS paywall into the Superwall-hosted Stripe checkout page. If you want Apple Pay to appear there, add your `*.superwall.app` web paywall domain to Stripe's payment method domains before testing or launching.

See [Apple Pay domain setup](/docs/web-checkout/web-checkout-configuring-stripe-keys-and-settings#apple-pay-domain-setup) for the full setup steps.

### Localized checkout prices

App2Web supports [Stripe Adaptive Pricing](/docs/web-checkout/web-checkout-adaptive-pricing) for the external Stripe checkout step. Enable Adaptive Pricing in Stripe, then users who leave the app for checkout can see localized currency based on their location.

Keep the campaign filter aligned with Apple's external purchase rules. Adaptive Pricing changes the currency shown during Stripe checkout; it does not change which users should be eligible to see an external purchase link in your app.

### Prefill customer information

When starting checkout from an iOS paywall (App2Web), you can prefill customer information in two ways:

#### Email

Stripe will automatically prefill the email field if you set the user's `email` as a [User Attribute](/docs/sdk/quickstart/setting-user-properties) in your app before initiating checkout.

#### Stripe Customer ID

If you already have a Stripe customer ID for your user, you can set it as the `stripe_customer_id` user attribute. This will associate the checkout session with the existing Stripe customer, automatically prefilling their saved information and payment methods:

```swift
Superwall.shared.setUserAttributes([
    "email": user.email,
    "stripe_customer_id": user.stripeCustomerId
])
```

> **Note:** When both `stripe_customer_id` and `email` are provided, the Stripe customer ID takes precedence. The checkout session will use the existing customer's information rather than creating a new customer.