# 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

# Web Checkout Links

Learn how to use campaigns and placements to present web paywalls using Superwall's web checkout links.

Once you've [created a Stripe app](/docs/web-checkout/web-checkout-creating-an-app), [configured Stripe with Superwall](/docs/web-checkout/web-checkout-configuring-stripe-keys-and-settings) via the [Superwall Stripe app](https://marketplace.stripe.com/apps/superwall) and have [created Stripe products](/docs/web-checkout/web-checkout-adding-a-stripe-product) — you're ready to configure a campaign to show a web paywall.

> **Note:** Before you proceed, recall that web checkout has all of the advantages of the Superwall platform. If you are unfamiliar with how to create campaigns or what a placement is — we recommend you read through the [introduction](/docs/using-the-dashboard) documentation and [campaigns doc](/docs/dashboard/dashboard-campaigns/campaigns) first.

### Understanding placements in web checkout

There are two primary differences between web checkout and the typical Superwall campaign flow:

1. **Placements become unique URLs** which, in turn, show your paywall. These are called *web checkout links*.
2. **User variables** are not available in audience filtering.

Other than that, everything operates as a normal Superwall campaign would. For example:

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

Here, the placement `black-friday-promo` presents a paywall. If the app's URL in [settings](/docs/web-checkout/web-checkout-configuring-stripe-keys-and-settings) is `caffeinepal`, then the URL for this placement would be `https://caffeinepal.superwall.app/black-friday-promo`. Visiting that web checkout link presents a paywall:

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

Conceptually, you can think of these web checkout links performing a similar function as registering a placement does in our mobile SDK:

```swift
Superwall.shared.register(placement:"black-friday-promo") { _ in }
```

This means that you now can use web checkout with all of the same powerful features that Superwall offers, such as A/B testing, paywall targeting and more. Again, these work just like any other campaign would in Superwall. The interface is the same, so now you create placements, start creating audience filters and more:

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

Also, remember to create responsive paywalls. Users can view your checkout page on a laptop, phone and other varying sized viewports. For some quick tips, check out this blog post over adapting paywalls to look great on [iPad](https://superwall.com/blog/how-to-create-adaptable-paywalls-for-iphone-and-ipad-using-superwall).

### A note on the `$home` placement

Every campaign has a `$home` placement out of the box. This placement acts a "default" link, and isn't required to be part of the URL as other placements are. For example:

```plaintext
// This works 
https://caffeinepal.superwall.app/$home

// And this also works, even though `$home` isn't in the URL
https://caffeinepal.superwall.app/
```

This is useful so that even if a user visits your web checkout link, and there isn't a placement in the URL — they'll still see a paywall.

### How query string parameters work

You can attach query string parameters to any web checkout link by appending them to the URL:

```html
https://caffeinepal.superwall.app/black-friday-promo?name=jordan
```

This will pass the `name` parameter to the placement, and you can use it in your audience filters. For example, you could create a filter that only shows the paywall if the `name` parameter is equal to `jordan`:

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

Or, you could access them in your paywall using the same flow as you would for [placement parameters](/docs/using-placement-parameters):

1. In the paywall editor, add a variable.
2. Make it a `parameter` type. Match the `name` to the query string parameter key (here, that would be `name`).
3. Set the value type, then click **Create**.
4. Now, you can use that variable in your paywall:

This makes it easy to show in your paywall:

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

Then, if the URL is visited, the audience filter matches from above — and we can see the value on the paywall, too:

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

Of course, this is a simplistic example — but this is useful for personalization, seasonal events, influencer campaigns and more. Any query string parameter you pass can be used in the paywall, and in audience filters.

### Localized checkout prices

Web checkout links support [Stripe Adaptive Pricing](/docs/web-checkout/web-checkout-adaptive-pricing). When Adaptive Pricing is enabled in Stripe, customers can see localized currency in the Stripe checkout flow based on their location.

This does not change how you build campaigns or placements in Superwall. Create the web checkout link as usual, then let Stripe localize the checkout price when the customer starts payment.

### Automatically populating user emails in checkout flows

> **Tip:** This section is Web2App only (starting from a web link). For App2Web (starting from an iOS paywall), see [App2Web](/docs/web-checkout/web-checkout-direct-stripe-checkout#prefill-email).

There is a special query string parameter you can use to automatically populate the user's email in the checkout flow. This is useful for pre-filling the email field in the checkout form, so that users don't have to enter it manually. Simply add `email` and set the value to the user's email address:

```html
https://caffeinepal.superwall.app/black-friday-promo?email=myemail@yahoo.com
```

When the Stripe checkout flow launches, the email is now filled out automatically:

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

### Automatically populating appUserId in checkout flows

There is a set of special query string parameters which will set the appUserId for the subscription. This overrides the default behavior where Superwall will automatically assign an anonymous identifier. You may pass `uid`, `user`, or `app_user_id` to override the default.

```html
https://caffeinepal.superwall.app/black-friday-promo?app_user_id=my-custom-id
```

This identifier will show up in Stripe metadata & webhooks. The app\_user\_id will be put into the `client_reference_id` field on a Stripe Checkout Session and will be included on the subscription metadata under `_sw_app_user_id`