# 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

# Stripe Setup

Connect Superwall to Stripe using the official Stripe app and configure your settings.

Once you've created a [Stripe app](/docs/web-checkout/web-checkout-creating-an-app), you'll need to connect it with Stripe and fill in a few settings. This is a one-time setup that connects Superwall to Stripe. The easiest way to get started is to click on the link in your overview page, which will take you to your app's [Settings](/docs/dashboard/dashboard-settings/overview-settings) page:

![](https://2a2314a4-superwall-docs.staffbar.workers.dev/docs/images/web2app_prompt.jpeg)

### Application settings

Fill out metadata about your iOS app in this section.

![](https://2a2314a4-superwall-docs.staffbar.workers.dev/docs/images/web2app_settings.png)

1. **Icon:** An icon to represent your app, we recommend using the same one that your iOS app does. This will appear on the checkout and subscription management pages.

2. **Application Name:** The name of your app, we recommend using the same name as your iOS app.

3. **Support URL:** A URL to your support page. This will be shown on the checkout and subscription management pages.

4. **Support Email:** An email you provide customers for support questions and general reach out

5. **Redeemable on Desktop:** If your app is an iPad app on Mac, enable this option so that users can redeem products on their Mac. If you aren't using iPads Apps on the Mac, you can disable this. If this is disabled, Superwall enforces redemption on an iOS device.

Once you've filled out this information, **click** on the **Update Application** button.

### Post-Purchase Behavior

Configure what happens after a user completes a purchase on the web:

![](https://2a2314a4-superwall-docs.staffbar.workers.dev/docs/images/web-checkout-post-purchase-behavior.png)

**Redeem (Default)**: Superwall manages the entire redemption flow. Users are automatically deep linked to your app with a redemption code, with fallback to the App Store/Play Store if the app isn't installed. This is recommended for most apps.

**Redirect**: Redirect users to your own custom URL with purchase information passed as query parameters. Use this when you need to:

* Show a custom success or onboarding page
* Perform additional verification or actions before redemption
* Integrate with your own deep linking infrastructure

When using Redirect mode, you'll need to provide a **Redirect URL** (must start with `https://`). Purchase data will be appended as query parameters:

* `app_user_id` - User's app identifier
* `email` - User's email address
* `stripe_subscription_id` - Stripe subscription ID, or Stripe Checkout session ID for one-time purchases
* Any custom placement parameters you've set

Learn more about [post-checkout redirecting](/docs/sdk/guides/web-checkout/post-checkout-redirecting).

> **Note:** This application setting is the default for Web Checkout purchases. A web checkout paywall
> can override it for a specific purchase button with a **Redeem Purchase** after-purchase
> action. See [Redeem Purchase for web checkout](/docs/dashboard/dashboard-creating-paywalls/paywall-editor-styling-elements#redeem-purchase-for-web-checkout).

### Web Paywall Domain

This is the domain your paywalls will be shown from. This was set when the Stripe app was created, and cannot be changed.

![](https://2a2314a4-superwall-docs.staffbar.workers.dev/docs/images/web-checkout-domain-section.png)

### Apple Pay domain setup

If you want Apple Pay to appear in Stripe Checkout, add your Superwall web paywall domain as a Stripe payment method domain. Stripe requires the exact domain that hosts checkout to be registered before domain-based payment methods such as Apple Pay can appear.

For a Superwall web checkout app, register the domain shown in **Web Paywall Domain**. For example, if your Superwall checkout links use `https://caffeinepal.superwall.app`, register `caffeinepal.superwall.app` in Stripe.

> **Note:** Register the Superwall subdomain only. Do not include `https://`, a path, or the root
> `superwall.app` domain.

## Open payment settings in Stripe

In Stripe, open **Settings**, then select **Payments**.
![](https://2a2314a4-superwall-docs.staffbar.workers.dev/docs/images/stripe-settings-payments.png)

## Open payment method domains

In the Payments settings, open **Payment method domains**.
![](https://2a2314a4-superwall-docs.staffbar.workers.dev/docs/images/stripe-payment-method-domains.jpg)

## Add your Superwall domain

Click **Add a new domain**, enter your Superwall web paywall domain, then save it.
![](https://2a2314a4-superwall-docs.staffbar.workers.dev/docs/images/stripe-add-superwall-domain.jpg)

After Stripe validates the domain, it should appear as enabled. Apple Pay may still be hidden if the customer is not using a supported device, browser, card, country, or currency.

> **Tip:** Stripe settings are mode-specific. If you use sandbox checkout, repeat this setup with **Test mode**
> enabled in Stripe. Then repeat it again in live mode before launching.

For more details, see Stripe's [payment method domain registration docs](https://docs.stripe.com/payments/payment-methods/pmd-registration).

### Stripe Live Configuration

To connect Stripe with Superwall, you'll use the official Superwall Stripe app:

#### Step 1: Visit the Stripe Marketplace

Visit the [Superwall app on Stripe Marketplace](https://marketplace.stripe.com/apps/superwall):

![](https://2a2314a4-superwall-docs.staffbar.workers.dev/docs/images/stripe/step-1-marketplace.png)

#### Step 2: Install the App

Click **Install app** to begin the authorization flow:

![](https://2a2314a4-superwall-docs.staffbar.workers.dev/docs/images/stripe/step-2-install.png)

#### Step 3: Continue Installation

Click **Continue** to proceed with the installation:

![](https://2a2314a4-superwall-docs.staffbar.workers.dev/docs/images/stripe/step-3-continue.png)

#### Step 4: Generate API Keys

Click **Generate keys** to create your API keys:

![](https://2a2314a4-superwall-docs.staffbar.workers.dev/docs/images/stripe/step-4-generate-key.png)

#### Step 5: Confirm Key Generation

Click **Generate keys** again to confirm:

![](https://2a2314a4-superwall-docs.staffbar.workers.dev/docs/images/stripe/step-5-generate-key-2.png)

#### Step 6: Copy Your Keys

After installation, you'll receive a **Publishable Key** and a **Restricted Secret Key** with the proper permissions already configured. Copy both keys:

![](https://2a2314a4-superwall-docs.staffbar.workers.dev/docs/images/stripe/step-6-copy-keys.png)

#### Step 7: Configure Superwall

Paste the keys into the corresponding fields in Superwall:

* **Publishable Key**: Your Stripe publishable key from the app
* **Secret Key**: The restricted secret key provided by the app

Then **click** on **Update Configuration** to save your changes.

This section should say "Configured" at the top right if setup was successful:

![](https://2a2314a4-superwall-docs.staffbar.workers.dev/docs/images/web2app_live_config.png)

### Adaptive Pricing

If you want web checkout customers to pay in their local currency, enable [Stripe Adaptive Pricing](/docs/web-checkout/web-checkout-adaptive-pricing) in Stripe's payment settings after connecting your Stripe keys. Adaptive Pricing is configured in Stripe separately for live and sandbox mode.

### Managed Payments

After your Stripe keys are configured, you can enable [Managed Payments](/docs/web-checkout/web-checkout-managed-payments) from **Settings**, then **Stripe Configuration**. Managed Payments uses Stripe as merchant of record for eligible Stripe web checkout payments through Stripe Connect, including tax calculation and compliance.

The **Managed Payments** switch is available only for eligible Superwall accounts and connected Stripe accounts. If the switch is not visible, or if Stripe asks you to accept Connect terms before enabling it, follow the Managed Payments guide before launching.

### Stripe Sandbox Configuration

> **Note:** The Superwall Stripe app provides both live and test mode keys. Make sure you're in the correct mode in your Stripe dashboard when copying keys.

For sandbox/test mode, switch to **Test mode** in your Stripe dashboard (toggle in the top-right corner), then follow these steps:

#### Step 1: Access the Superwall App

Navigate to the Superwall app in your Stripe dashboard. If already installed, find it under **Apps**:

![](https://2a2314a4-superwall-docs.staffbar.workers.dev/docs/images/stripe-test/step-1-install-page.png)

#### Step 2: Install in Test Mode

If you haven't installed the app in test mode yet, click **Install app**:

![](https://2a2314a4-superwall-docs.staffbar.workers.dev/docs/images/stripe-test/step-2-install.png)

#### Step 3: Continue Installation

Click **Continue** to proceed:

![](https://2a2314a4-superwall-docs.staffbar.workers.dev/docs/images/stripe-test/step-3-continue.png)

#### Step 4: Reveal Your API Keys

Click **Reveal test key** to view your test mode API keys:

![](https://2a2314a4-superwall-docs.staffbar.workers.dev/docs/images/stripe-test/step-4-reveal-api-key.png)

#### Step 5: Copy Your Test Keys

Copy both the **Publishable Key** and **Secret Key**:

![](https://2a2314a4-superwall-docs.staffbar.workers.dev/docs/images/stripe-test/step-5-copy-api-key.png)

#### Step 6: Configure Superwall

Paste both keys into the Sandbox Configuration fields in Superwall, then **click** on the **Update Configuration** button.

This section should say "Configured" at the top right if setup was successful.

### iOS configuration

Superwall uses the details here to handle deep links back to your app after a purchase occurs. **All of this information is required.**

![](https://2a2314a4-superwall-docs.staffbar.workers.dev/docs/images/web-checkout-ios-config.png)

1. **Apple Custom URL Scheme:** Add your app's custom URL scheme. If you haven't set on up, read [here for instructions](/docs/sdk/quickstart/in-app-paywall-previews).
2. **Apple App ID:** Your iOS app's ID. If you're unsure of your app's ID, you find it in **[App Store Connect](https://appstoreconnect.apple.com) -> Select your App -> General -> App Information -> Apple ID**:

![](https://2a2314a4-superwall-docs.staffbar.workers.dev/docs/images/web2app_app_id.png)

3. **Bundle ID:** Your iOS app's bundle ID. You can find this in Xcode -> Targets -> General -> Identity -> Bundle Identifier.
4. **Team ID:** The team ID that your iOS app belongs to. To find this, visit **[Apple Developer](https://developer.apple.com) -> Account -> Membership details -> Team ID**. It's obscured here, but it'll be where the arrow points in the image below:

![](https://2a2314a4-superwall-docs.staffbar.workers.dev/docs/images/web-checkout-team-id.png)

### Confirm setup

Once you've filled out all of these fields, you should see **Configured** for each section:

![](https://2a2314a4-superwall-docs.staffbar.workers.dev/docs/images/web2app_keys.jpeg)

Next, you'll need to create some products in Stripe.