# 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

# General

Use the Settings area to set up API keys, metadata and more.

To access settings for your Superwall account, **click** the **Settings** button in the sidebar:

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

<br />

## Tab

Under the General section, you can set or edit metadata and some integration API keys for your app:
![](https://2a2314a4-superwall-docs.staffbar.workers.dev/docs/images/overview-settings-general.png)
> **Note:** Some sections will hide or show depending on the platform your app is on. For example, for an
> Android app, Superwall will hide Apple-specific items.

**Name**<br />
The name for your application in Superwall. This isn't user-facing and only used within Superwall. You can change it anytime.**Apple App ID**<br />
Fill in your app's Apple identifier here. You can find it by going to **App Store Connect -> General -> App Information**.**Bundle ID**<br />
Fill in your iOS app's bundle identifier exactly as it appears in App Store Connect or Xcode. Bundle IDs are case-sensitive, and the casing must match when configuring Apple keys such as your In-App Purchase configuration.**Apple Custom URL Scheme**<br />
We use URL schemes to perform deep link logic and for in-app previews of paywalls for iOS apps. To learn more about setting up deep links, visit this [doc](/docs/sdk/quickstart/in-app-paywall-previews#using-deep-links-to-present-paywalls).

## Tab

### Application settingsHere, you can enter metadata about your iOS app that corresponds to your Stripe integration.
![](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) **Web Paywall Domain:** The domain your paywalls will be shown from. This was set when the Stripe app was created, and cannot be changed.

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

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

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

6) **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.### Stripe Live ConfigurationThis section allows you to connect Stripe keys with Superwall. You will need a:1) **Publishable Key:** A Stripe publishable key. Stripe creates this key for you, you don't need to generate it yourself.
2) **Secret Key:** A Stripe secret key that you create. Once you've made one, paste it here.You can find these keys [in your Stripe account](https://dashboard.stripe.com/settings/apps/com.superwall.stripe-rak). If you need help getting set up, check out the docs [here](/docs/web-checkout/web-checkout-configuring-stripe-keys-and-settings).### Stripe Sandbox ConfigurationThe sandbox configuration allows you to test purchasing flows with your web checkout integration. If you need to find these keys, you can find them in [your Stripe account](https://dashboard.stripe.com/test/settings/apps/com.superwall.stripe-rak).1) **Publishable Key:** A Stripe publishable key. Stripe creates this key for you, you don't need to generate it yourself.
2) **Secret Key:** A Stripe secret key that you create. Once you've made one, paste it here.### iOS configurationThis section has critical information for your iOS app. Without it, web checkout won't work.1) **Apple Custom URL Scheme (no slashes)**: Your custom URL scheme. If you haven't set this up, view the [documentation](/docs/sdk/quickstart/in-app-paywall-previews).
2) **Apple App ID**: Your app's Apple ID. You can find this in **App Store Connect -> General -> App Information**.
![](https://2a2314a4-superwall-docs.staffbar.workers.dev/docs/images/web2app_app_id.png)