# 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

A protocol for handling Superwall's subscription-related logic with your own purchase implementation.

> **Info:** **This protocol is not required.** By default, Superwall handles all subscription-related logic automatically.

> **Warning:** When implementing PurchaseController, you must manually update [`subscriptionStatus`](/docs/ios/sdk-reference/subscriptionStatus) whenever the user's entitlements change.

## Purpose

Use this protocol only if you want complete control over purchase handling, such as when using RevenueCat, another third-party purchase framework, or your own external billing flow.

## Signature

```swift
public protocol PurchaseController: AnyObject {
  @MainActor
  func purchase(product: StoreProduct) async -> PurchaseResult
  
  @MainActor
  func restorePurchases() async -> RestorationResult
}
```

## Parameters

<TypeTable
  type="{
  purchase: {
    type: &#x22;product: StoreProduct&#x22;,
    description: &#x22;Called when user initiates purchasing. The `StoreProduct` may wrap an App Store product or, for custom paywall products in 4.15.0+, an API-backed product that must be purchased by your external billing system. Returns `PurchaseResult`.&#x22;,
    required: true,
  },
  restorePurchases: {
    type: &#x22;None&#x22;,
    description: &#x22;Called when user initiates restore. Implement your restore logic here. Returns `RestorationResult`.&#x22;,
    required: true,
  },
}"
/>

## Returns / State

* `purchase()` returns a `PurchaseResult` (`.purchased`, `.failed(Error)`, or `.cancelled`)
* `restorePurchases()` returns a `RestorationResult` (`.restored` or `.failed(Error?)`)

When using a PurchaseController, you must also manage [`subscriptionStatus`](/docs/ios/sdk-reference/subscriptionStatus) yourself.

## Handling Products

* For App Store-backed products, use `product.sk1Product` or `product.sk2Product`, or pass the product into your existing purchase SDK.
* For custom products introduced in `4.15.0`, Superwall will call your purchase controller with a `StoreProduct` that has no StoreKit backing product. In that case, use `product.productIdentifier` in your external billing system and return the matching `PurchaseResult`.
* Do not call `Superwall.shared.purchase(product)` for custom products. That helper is for StoreKit-backed purchases only.

### Monthly billing plans

iOS SDK `4.16.0` adds support for annual App Store subscriptions that are billed monthly. If you let Superwall handle purchases, no code changes are required. Superwall passes the selected billing plan to StoreKit automatically.

If your `PurchaseController` calls StoreKit 2 directly, pass the billing plan from `StoreProduct` into the StoreKit purchase options when it is available:

```swift
func purchase(product: StoreProduct) async -> PurchaseResult {
  guard let sk2Product = product.sk2Product else {
    return .cancelled
  }

  var options: Set<StoreKit.Product.PurchaseOption> = []

  if let token = product.introOfferToken {
    options.insert(.introductoryOfferEligibility(compactJWS: token.token))
  }

  if #available(iOS 26.4, macOS 26.4, tvOS 26.4, watchOS 26.4, visionOS 26.4, *),
    let billingPlanType = product.billingPlanType {
    let storeKitBillingPlan: StoreKit.Product.SubscriptionInfo.BillingPlanType

    switch billingPlanType {
    case .upFront:
      storeKitBillingPlan = .upFront
    case .monthly:
      storeKitBillingPlan = .monthly
    }

    options.insert(.billingPlanType(storeKitBillingPlan))
  }

  do {
    let result = try await sk2Product.purchase(options: options)

    switch result {
    case .success(.verified(let transaction)):
      await transaction.finish()
      return .purchased
    case .success(.unverified(_, let error)):
      return .failed(error)
    case .pending:
      return .pending
    case .userCancelled:
      return .cancelled
    @unknown default:
      return .cancelled
    }
  } catch {
    return .failed(error)
  }
}
```

`product.billingPlanType` is the billing plan that will actually be applied on the current device. It is `nil` when no plan is configured or when StoreKit cannot honor the selected plan, so purchase code can omit the option and let Apple use the default billing plan.

For a complete guide, see [Custom Store Products](/docs/ios/guides/custom-store-products).

## Usage

For implementation examples and detailed guidance, see [Using RevenueCat](/docs/ios/guides/using-revenuecat).

> **Tip:** This is commonly used with RevenueCat, StoreKit 2, or other third-party purchase frameworks where you want to maintain your existing purchase logic.