# 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 # Products To add products to your paywall, click the **Products** button from the **sidebar**: ![](https://2a2314a4-superwall-docs.staffbar.workers.dev/docs/images/pe-editor-products-sidebar.png)
> **Note:** If you haven't added products to your app, do that first. Check out this [doc](/docs/dashboard/products) for > more. ### Choosing products You can display as many products as you see fit on your paywall. Superwall will automatically fill in a name for the first three added ("primary", "secondary", and "tertiary") but you're free to name them anything else. Regardless, the name is used to reference them using Liquid Syntax in the editor. For example, `products.primary.price`. > **Tip:** It's important to remember that *you* retain full control over which of your products show in a paywall, and how. For example, use them along with [dynamic values](/docs/dashboard/dashboard-creating-paywalls/paywall-editor-dynamic-values) to hide or show them to create any U.X. your design calls for. ### Choosing a billing plan for annual iOS subscriptions If an annual iOS App Store product has a [monthly billing plan](/docs/dashboard/products#monthly-billing-plans-for-annual-ios-subscriptions), the product entry shows a **Billing plan** control after you add it to a paywall. Choose: | Option | What it does | | -------------------- | -------------------------------------------------------------------------------------------------------------------------- | | Monthly installments | Presents Apple's monthly billing plan where available. This is the default for products that offer a monthly billing plan. | | Up-front | Presents the up-front annual billing plan for this paywall slot. | This choice is stored per paywall product slot. That means the same annual App Store product can appear as monthly installments on one paywall and up-front annual billing on another paywall. The iOS SDK applies the selected plan during StoreKit 2 purchase on iOS SDK `4.16.0` or later. If the user's device or storefront cannot use the selected billing plan, StoreKit falls back to Apple's default plan. Use `products.selected.isBillingPlanAvailable` or the matching product variable to hide billing-plan-specific copy when the plan is not available. ### Understanding the selected product and selected product index variables The `products.selected` variable will always represent any product the user has selected on your paywall. By default, it will be the *first* product you've added. In addition, the `products.selectedIndex` variable will also be updated as products are selected. This opens up many patterns to use, such as customizing copy, images, videos, or anything else based on which product the user has tapped on. Many of our [built-in elements](/docs/dashboard/dashboard-creating-paywalls/paywall-editor-layout#adding-elements) which display products will update these values. If you wish to add a custom element which selects a product, **click** on the element and add a **[tap behavior](/docs/dashboard/dashboard-creating-paywalls/paywall-editor-styling-elements#tap-behaviors)** to choose a product (the selected index will update automatically as a result). ### Customizing pricing copy In my most cases, Superwall will format your product's price in a localized manner. For example, look at this paywall from left-to-right: 1. The primary product is displayed in the button. 2. Below it, the call-to-action button formats its text as `Subscribe for {{ products.selected.price }} / {{ products.selected.period }} `. 3. That means any selected product's price will display with a similar pattern in the call-to-action button. ![](https://2a2314a4-superwall-docs.staffbar.workers.dev/docs/images/pe-editor-products-template.png) You can use [Liquid syntax](https://shopify.github.io/liquid/) to format prices in several different ways. For example, if you wanted to show an annual price differently, you could write `Subscribe for only {{ products.primary.monthlyPrice }} / month.` to display the localized price in monthly terms. If a product cost $120.00 a year, then the text would read as "Subscribe for only $10.00 / month." Copy like this is achieved by using variables. To learn more about them, visit this [page](/docs/dashboard/dashboard-creating-paywalls/paywall-editor-variables). ### Offer pricing copy A common use-case is showing copy that reflects the selected product's trial or offer terms. Consider this example product: | Product Identifier | Trial | Trial Price | Price | Period | | ---------------------- | ------ | ----------- | ------ | ------ | | myapp.annual40.1wkFree | 1 week | Free | $39.99 | 1 year | In Superwall, all data for the one-week free trial is found in the `trial` liquid variables, which are a part of a `product`. Below, critical details about its duration, offer price and more are shown in the example paywall. Take note of the text box on the right, which shows how these variables can be used: ![](https://2a2314a4-superwall-docs.staffbar.workers.dev/docs/images/offerVars.png) ### Products missing App Store Connect API When using Apple-based products, Superwall will automatically fetch the product information from App Store Connect. However, if you haven't set up the App Store Connect API, you may see a message indicating that the product information is missing: ![](https://2a2314a4-superwall-docs.staffbar.workers.dev/docs/images/asc_invalid_pw.png) To resolve this, follow the steps in our [App Store Connect API setup guide](/docs/dashboard/dashboard-settings/overview-settings-revenue-tracking#app-store-connect-api).