# 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 # Restoring & Managing Purchases Learn how users can manage and restore purchases made via the web. When users purchase through web checkout, they can access their account details via a plan management page. This URL is included in their receipt, which is sent to their email after a successful purchase. To retrieve the link, users must enter the email they used during checkout. Otherwise, to offer this link manually you can use the following URL format: ```plaintext https://{your URL in settings}.superwall.app/manage ``` By default, after a successful checkout, Superwall emails the address used at checkout with instructions and a redemption link to activate the purchase in your app. The email is sent from `Your app name ` with the subject `Your activation link from your app name`. ![](https://claude-centralize-agent-preamble-superwall-docs.staffbar.workers.dev/docs/images/web-checkout-redeem-email.png) > **Warning:** If your app uses Sign in with Apple and customers may check out with **Hide My Email**, configure > Apple's private email relay before launching web checkout. Apple can reject Superwall web checkout > emails sent to `privaterelay.appleid.com` addresses unless `superwall.app` is registered as an > email source. See [Web Checkout FAQ](/docs/web-checkout/web-checkout-faq#do-customers-who-use-sign-in-with-apple-hide-my-email-receive-web-checkout-emails) > for setup steps. If you want to disable these emails, use the "Disable Superwall Emails" setting in your Stripe app settings — see [how to disable the activation link email](/docs/support/web-checkout/3969573187-how-do-i-disable-the-activation-link-email-for-web-checkout). When this page is visited, users enter the email they used during checkout to receive a link to manage their purchase: ![](https://claude-centralize-agent-preamble-superwall-docs.staffbar.workers.dev/docs/images/web2app_manage.png) For the above example, the URL would be `https://caffeinepal.superwall.app/manage`. After entering their email, they will receive a link to restore access, manage subscriptions, update payment methods, view their billing history, and more: ![](https://claude-centralize-agent-preamble-superwall-docs.staffbar.workers.dev/docs/images/web2app_manage_details.png) For situations where a user needs to restore their purchases, check out the answer in this [F.A.Q](/docs/web-checkout/web-checkout-faq).