# 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 # PurchaseController An interface for handling Superwall's subscription-related logic with your own purchase implementation. > **Info:** **This interface is not required.** By default, Superwall handles all subscription-related logic automatically using Google Play Billing. > **Warning:** When implementing PurchaseController, you must manually update [`subscriptionStatus`](/docs/android/sdk-reference/subscriptionStatus) whenever the user's entitlements change. ## Purpose Use this interface only if you want complete control over purchase handling, such as when using RevenueCat or other third-party purchase frameworks. ## Signature ```kotlin interface PurchaseController { suspend fun purchase( activity: Activity, product: StoreProduct, basePlanId: String?, offerId: String? ): PurchaseResult suspend fun restorePurchases(): RestorationResult } ``` ```java // Java uses the callback-based PurchaseControllerJava interface. public interface PurchaseControllerJava { void purchase( ProductDetails productDetails, String basePlanId, String offerId, kotlin.jvm.functions.Function1 completion ); void restorePurchases( kotlin.jvm.functions.Function2 completion ); } ``` > **Info:** Starting in `2.8.0`, Kotlin's `PurchaseController.purchase()` receives a `StoreProduct` (instead of the Billing Library's `ProductDetails`), which also supports [custom store products](#custom-store-products). For Google Play products, access the underlying `ProductDetails` through `product.rawStoreProduct?.underlyingProductDetails`. The default implementation of this method routes Google Play products to the older `purchase(activity, productDetails, basePlanId, offerId)` overload, so existing implementations of that overload keep working unchanged. That older overload is now deprecated; implement the `StoreProduct`-based method above going forward, and implement it directly if you need to support custom store products. `PurchaseControllerJava` remains a callback-based API that receives `ProductDetails`. It does not support custom store products. ## Parameters ## Returns / State * `purchase()` returns a `PurchaseResult` (`.Purchased()`, `.Failed(errorMessage: String)`, `.Cancelled()`, or `.Pending()`) * `restorePurchases()` returns a `RestorationResult` (`.Restored()` or `.Failed(Throwable?)`) When using a PurchaseController, you must also manage [`subscriptionStatus`](/docs/android/sdk-reference/subscriptionStatus) yourself. ## Custom store products Products configured on a custom store in the Superwall dashboard (e.g. Stripe or your own payment backend) can be attached to paywalls. Their metadata (price, subscription period, trial) is fetched from the Superwall API instead of Google Play, and purchases for them are routed through your `PurchaseController`, bypassing Google Play Billing entirely. * Kotlin `PurchaseController` implementations can check `product.isCustomProduct` in `purchase()` to detect a custom product and fulfill and persist it through their own payment flow. `PurchaseControllerJava` does not support custom store products. * After your billing system grants the entitlement, call `Superwall.instance.setSubscriptionStatus(...)` to synchronize that entitlement state with Superwall. The SDK does not fulfill or persist custom purchases automatically. * `StoreProduct.customTransactionId` is an SDK-generated identifier you can use as the original transaction identifier in your own analytics. * Requires configuring the SDK with a `PurchaseController`. ## Usage For implementation examples and detailed guidance, see [Using RevenueCat](/docs/android/guides/using-revenuecat).