# 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 # Forward Apple's Notifications from RevenueCat Keep RevenueCat's URL in App Store Connect and have RevenueCat forward Apple's App Store Server Notifications to Superwall. Apple sends an app's App Store Server Notifications to one URL per environment. If that URL is RevenueCat's, you don't have to give it up for Superwall to receive the same notifications. RevenueCat can forward each one to a second URL, and that URL can be your app's Superwall URL. Use this page when App Store Connect already shows a RevenueCat URL under **App Information → App Store Server Notifications**. If the URL field in App Store Connect is empty, set Superwall's URL there directly instead. See [Revenue Tracking](/docs/dashboard/dashboard-settings/overview-settings-revenue-tracking#option-1---app-store-connect-server-notifications). > **Note:** This is not RevenueCat's **Superwall** integration. That integration sends RevenueCat's own subscription events to Superwall, and is covered under [RevenueCat](/docs/dashboard/dashboard-settings/overview-settings-revenue-tracking#revenuecat). Forwarding passes Apple's original notifications through untouched. You can use either one, or both. ## Set up forwarding ## Copy your app's Superwall URL In the Superwall dashboard, open your iOS app's **Revenue tracking** page and copy the server notification URL. It's the same URL you would paste into App Store Connect.From the [Superwall CLI](/docs/agents/cli#app-store-connect):```bash superwall asc notification-url --app ```The URL contains your app's token. Treat it like a secret. ## Open the iOS app in RevenueCat In the RevenueCat dashboard, go to your iOS app under **Apps**, and scroll to **Apple Server to Server notification settings**. ## Paste the URL and save Paste the Superwall URL into **Apple Server Notification Forwarding URL**, then click **Save Changes**. Leave the URL in App Store Connect as it is. RevenueCat keeps receiving Apple's notifications, and sends a copy of each to Superwall. RevenueCat's documentation for this setting is [Apple App Store Server Notifications](https://www.revenuecat.com/docs/platform-resources/server-notifications/apple-server-notifications). Check it for which RevenueCat plans include forwarding and which environments it covers. ## If the field is already in use The field holds one URL. If RevenueCat already forwards Apple's notifications to your own server, keep that, and forward from your server to Superwall instead. See [Event Forwarding](/docs/dashboard/dashboard-settings/overview-settings-revenue-tracking#option-2---event-forwarding). The request your server receives through RevenueCat is still Apple's own, so forward its body unmodified. ## Check that it works After the next purchase, renewal, or cancellation, an Apple event appears under recent events on the **Revenue tracking** page. Sandbox purchases count. ## Forwarding doesn't choose your revenue provider Receiving Apple's notifications and choosing which source your revenue metrics count are separate settings. If RevenueCat's Superwall integration is also sending events for this app, both sources arrive and are stored. The **revenue provider** on the **Revenue tracking** page decides which one your charts count. See [Choosing a revenue provider](/docs/dashboard/dashboard-settings/overview-settings-revenue-tracking#choosing-a-revenue-provider).