# 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

# Creating Products

Create products in Stripe to show on your web paywalls.

### Adding products

Once your app is configured with Stripe, you can create products to show on your web paywalls. To get started, **click** on **Products** from the overview page:

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

> **Note:** Complete your Stripe setup first by following the steps in [Configuring Stripe Keys and Settings](/docs/web-checkout/web-checkout-configuring-stripe-keys-and-settings).

Next, **click** on the **+ Import Products** button in the top right corner:

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

You'll be given a choice to add either a:

1. **Live Product:** These are for production purchases and flows.
2. **Sandbox Product:** These are for testing purchases and flows.

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

> **Note:** Superwall supports both sandbox and live products. To learn more about their differences, here's a
> good overview from [Stripe's documentation](https://docs.stripe.com/test-mode).

### Using Stripe products

If you've already created products in Stripe, you can import them into Superwall now. All you need to do is select the "Product" and the rest of the fields should automatically populate with its data when you select them. You will need to choose which entitlement or entitlements a product should grant a user access to:

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

Once you're done **click** on the **Save** button and your product is ready to be used in a paywall.

### Creating new products in Stripe

To create new products, **click** on the **Create Product in Stripe** link:

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

{" "}

From there, fill in all of the fields presented to you in Stripe:

1. **Name:** The product name, i.e. "Pro", "Premium", etc.
2. **Description:** A description of the product, this will show up in checkout.
3. **Image:** An image representing the product, this will show up in checkout. Optional.
4. **Product tax code:** The tax code classification for the product. Refer to your territories tax codes for more information.
5. **Recurring vs One-off:** For subscriptions, choose "Recurring". For lifetime access, credit packs or other consumables, choose "One-off".
6. **Amount:** The price of your product, and what it will renew at if it's recurring.
7. **Billing period:** The billing period for the product, i.e. "Monthly", "Yearly", etc.

If you plan to use [Managed Payments](/docs/web-checkout/web-checkout-managed-payments), pay close attention to the Stripe **Product tax code**. Superwall asks Stripe for Managed Payments eligibility and shows Stripe's ineligibility reasons when a product needs to be fixed before Managed Payments can be enabled.

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

Once you've finished filling out pricing details, product name and all other metadata, **click** on the **Add product** button at the bottom right of the form. You should be redirected to your Stripe products page:

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

Now, when you return to Superwall, select your product from the **Products** drop down, and when you select the other fields, Superwall will pull in the data for you (aside from trials, which you choose when adding a Stripe product). Here, the new "Scores Annual" product created in Stripe shows up in the products menu now:

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

Be sure to associate the correct entitlement to the product as well.

> **Tip:** For Stripe one-time prices, Superwall shows the period as **None (Lifetime / Consumable)**. Link lifetime products to an entitlement, and usually leave consumable products without one. Learn more in [Stripe One-Time Purchases](/docs/web-checkout/web-checkout-stripe-one-time-purchases).

### Adding products to paywalls

Adding Stripe products to web paywalls works the exact same way as it does for mobile paywalls. Check out the docs [here](/docs/dashboard/dashboard-creating-paywalls/paywall-editor-products). For a quick overview:

1. Open the paywall editor.
2. On the left sidebar click on **Products**.
3. Choose the products to add, as in the image below:

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

Keep in mind that to test products, it's as simple as adding a test product to a paywall and performing the checkout flow. For more information, please refer to [Testing purchases](/docs/web-checkout/web-checkout-testing-purchases).

### Sandbox products

Sandbox products are used to test purchases. When you create one, you can add it to any web paywall to test check out flows. You create sandbox products the same you create other products, just choose "Sandbox Product" when creating a product. You'll see a sandbox banner at the top of Stripe when you create these types of products:

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

Once you've created a sandbox product in Stripe, import them to Superwall the same way as you would a normal product, and then they are ready for use in a paywall. Within the products page, Superwall will show which environment each product belongs to:

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

When testing with sandbox products, you can see their details in the Overview page. **For this to work, all products on a paywall must be test products.** Put differently, the sandbox metrics won't show here if you mixed and matched live and sandbox products on the same paywall when testing:

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

### Free trials

Trials are controlled by Superwall, they are not set up in Stripe. When you go to add a product, you choose the terms. You can also reuse the same product ID multiple times to create different trial lengths. This is a powerful capability, as it avoids the need to create a similar product over and over just to offer different trial terms. For example, you can use the same product ID with a one week trial, no trial, 3 day trial, and any other terms you need — these will all be represented as individual products you can add to paywalls.