# 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 # Why Are Users Still Seeing a Removed Paywall? Troubleshoot why some users continue to see a paywall that you have removed from all campaigns, and learn how to reset sticky assignments. ## Symptoms * A user purchases through or sees a paywall that no longer exists in any active campaign. * You replaced an old paywall with a new one, but some users still see the old version. * 100% of users should be seeing a new paywall, yet reports of the old paywall persist. ## Cause Superwall uses **sticky assignments** to ensure consistent user experiences during experiments. When a user is first assigned to a paywall variant, that assignment is stored on the server and persists indefinitely. This means: * Removing a paywall from a campaign does not automatically clear existing assignments. * Users who were previously assigned to the old paywall will continue to see it, even if it is no longer attached to any audience. * Changing presentation percentages or swapping paywalls only affects **new users** who have not yet been assigned. This behavior is intentional. It preserves experiment integrity and allows you to keep existing users on old pricing while testing new pricing with new users. However, it can be surprising when you want all users to see a new paywall immediately. > **Note:** Calling `Superwall.shared.reset()` clears on-device data but does **not** clear server-side assignments. The old assignment will be restored the next time the user triggers the placement. ## Solution To force all previously-assigned users onto your new paywall, you need to reset the assignments in the dashboard. ### Open the campaignGo to **Campaigns** in the Superwall dashboard and select the campaign where the old paywall was previously configured.### Navigate to the audience's experimentClick the **Paywalls** tab for the relevant audience. You should see the old paywall variant listed, possibly with a count of assigned users still shown next to it.### Reset the assignmentsClick the **refresh icon** next to the assignment count for the old paywall variant. This clears all stored assignments for that variant, forcing those users to be reassigned based on your current campaign configuration the next time they trigger the placement. > **Warning:** Resetting assignments also resets the experiment stats for that audience. If you need to preserve metrics, consider setting the old paywall's presentation percentage to 0% instead of resetting, then allowing new assignments to naturally flow to the new paywall. ## Preventing This in the Future When replacing a paywall in a campaign, keep these points in mind: * **Swap, then reset.** After adding the new paywall and removing the old one, reset assignments so existing users are reassigned. * **Use presentation percentages.** If you want a gradual rollout, set the old paywall to 0% and the new one to 100%. New users will see the new paywall, but existing users will keep their current assignment until you reset. * **Remove vs. reset.** Removing a paywall from an audience does not reset its assignments. You must explicitly reset assignments to clear them.