# 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 # How to Test Paywalls with Local Currency for a Specific Country Learn how to preview your paywall as a user in a specific country would see it, including local currency and audience matching. When you create a campaign that targets users in a specific country, you may want to preview the paywall as those users would see it, with their local currency instead of your default. This requires two changes on your test device: matching the audience filter and changing the displayed currency. ### Matching country-based audience filters If your campaign uses `device.storeFrontCountryCode` to filter by country, your test device must report that same country to match the audience. On iOS, change your App Store region: 1. Open **Settings** on your device. 2. Tap your **Apple ID** at the top. 3. Go to **Media & Purchases** and tap **View Account**. 4. Tap **Country/Region** and select the country you want to test. > **Warning:** Changing your App Store region may require you to update your payment method to one valid in that country. You can switch back after testing. If your campaign uses `device.deviceLocale` instead (e.g. `en_GB`, `fr_FR`), change the device locale in **Settings > General > Language & Region** to match the target locale. ### Displaying local currency The currency shown on your paywall is determined by the App Store storefront country, not the device locale. To see prices in the currency a user in that country would see, change your App Store region using the steps above. The App Store returns product prices in the currency of the storefront country. For example, if your App Store region is set to France, prices will appear in EUR. If set to Japan, prices will appear in JPY. > **Note:** The actual price amount is determined by what you have configured in App Store Connect for each territory. The storefront country controls which currency and price tier is used. ### Summary of required changes | What you want to test | What to change | Where to change it | | ----------------------------------------------- | ------------------------ | ----------------------------------------------------------------------- | | Match a `storeFrontCountryCode` audience filter | App Store country/region | Settings > Apple ID > Media & Purchases > View Account > Country/Region | | Match a `deviceLocale` audience filter | Device locale | Settings > General > Language & Region | | See prices in local currency | App Store country/region | Settings > Apple ID > Media & Purchases > View Account > Country/Region | > **Tip:** If your campaign uses `storeFrontCountryCode`, changing the App Store region handles both matching the audience filter and displaying the correct local currency in one step.