# 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 # RevenueCat Revenue Tracking Send RevenueCat's subscription events to Superwall with a RevenueCat webhook, so your revenue charts count RevenueCat's purchases, renewals and refunds. If RevenueCat handles your app's purchases, it can send its subscription events to Superwall. Superwall uses them for revenue metrics, so purchases, renewals, cancellations and refunds show up in your charts. You set this up with a webhook in RevenueCat that points at your app's Superwall URL. Superwall shows the URL on the app's **Revenue tracking** page. ## Requirements * An iOS or Android app in Superwall, with your role allowed to change the app. The webhook URL carries a token, so members who can only view the app can't see or create it. * A RevenueCat project with your app in it. RevenueCat lists webhooks as a Pro plan feature. See RevenueCat's [webhooks documentation](https://www.revenuecat.com/docs/integrations/webhooks). ## Set up the webhook ## Choose RevenueCat as the revenue provider In Superwall, open your app and click **Integrations** in the sidebar. Under **Revenue tracking**, open the app's revenue tracking page. In the **Revenue provider** card, choose **RevenueCat**.If the app already has a revenue provider, or another source has been sending events, Superwall asks you to confirm first. See [Choosing a revenue provider](/docs/dashboard/dashboard-settings/overview-settings-revenue-tracking#choosing-a-revenue-provider).The **RevenueCat** option opens and shows three steps under **RevenueCat webhook**. ![The Revenue provider card with RevenueCat chosen, showing the RevenueCat webhook steps and the Create webhook URL button](https://superwall.com/docs/images/revenuecat-webhook/revenuecat-webhook-create.jpg) ## Copy the URL If the app doesn't have a URL yet, click **Create webhook URL**. Then click the copy button next to the URL. ![The RevenueCat webhook steps with the app](https://superwall.com/docs/images/revenuecat-webhook/revenuecat-webhook-url.jpg) The URL looks like `https://integrations.superwall.com/integrations/revenue-cat/webhook?pk=`. The token at the end is the same one RevenueCat's old Superwall integration used, so an app that had one keeps it. Treat the URL like a secret. ## Add the webhook in RevenueCat Click **Open RevenueCat**. It opens RevenueCat's form for a new webhook, which asks which project to add it to. Choose the project your app is in.You can also get there yourself: open the project in RevenueCat, go to **Integrations**, choose **Webhooks**, then **Create new webhook**.Fill in **Webhook name**, such as "Superwall", and paste the URL you copied into **Webhook URL**.Leave **Authorization header value** empty. The token is already in the URL, and Superwall reads that header first, so a value there stops the webhook from reaching your app. ## Send Production, Sandbox and all events Set **Environment to send events for** to **Both Production and Sandbox**, and **Event type** to **All events**. Leave **App** on **All apps**, unless your RevenueCat project holds both an iOS and an Android app (see below). Then click **Add webhook**. ![RevenueCat](https://superwall.com/docs/images/revenuecat-webhook/revenuecat-add-webhook.jpg) ## iOS and Android apps in one RevenueCat project Each Superwall app has its own webhook URL. If one RevenueCat project holds both your iOS and Android app, you'll have two Superwall apps. Add a webhook for each, and filter each one to its own app: 1. Copy the URL from the iOS app's **Revenue tracking** page in Superwall. Add it as a webhook in RevenueCat, and set **App** to your iOS app. 2. Do the same with the Android app's URL, and set that webhook's **App** to your Android app. Don't add both URLs without an app filter. Each event would then be sent to Superwall twice. Keep both Superwall apps in the same project. To add the second app to a project, see [Add a platform to a project](/docs/dashboard/creating-applications#add-a-platform-to-a-project). If both apps already exist, see [Projects](/docs/dashboard/dashboard-settings/overview-settings-projects). When you create a project for both platforms and choose **RevenueCat** under **Set up revenue tracking**, the setup shows both URLs, each named by its platform, with these same steps. ## Check that it works After the next purchase, renewal or cancellation, RevenueCat's events appear under **Recent events** on the **Revenue tracking** page. Sandbox purchases count. ## Limitations * The webhook sends RevenueCat's own events, not Apple's App Store Server Notifications. Some Superwall features, such as webhooks and integrations, need Apple's own notifications. If RevenueCat's URL is in App Store Connect, have RevenueCat forward them to Superwall. See [Forward Apple's Notifications from RevenueCat](/docs/dashboard/dashboard-settings/overview-settings-revenue-tracking-revenuecat-forwarding). * Choosing RevenueCat as the revenue provider only changes what your revenue metrics count. Apple's notifications keep arriving, and webhooks and other integrations still use them. See [Server Notifications](/docs/dashboard/dashboard-settings/app-store-server-notifications). ## Related * [Revenue Tracking](/docs/dashboard/dashboard-settings/overview-settings-revenue-tracking) * [Forward Apple's Notifications from RevenueCat](/docs/dashboard/dashboard-settings/overview-settings-revenue-tracking-revenuecat-forwarding) * [Migrating from RevenueCat to Superwall](/docs/dashboard/guides/migrating-from-revenuecat-to-superwall)