# 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

# refreshCustomerInfo

Fetch the user's latest entitlements from Superwall after your server reports a purchase, and get updated CustomerInfo with async/await or a completion handler.

`refreshCustomerInfo()` fetches entitlements from Superwall, even if they were fetched recently. Use it after your server reports a custom store purchase to make the updated access available in your app. Unlike [`getCustomerInfo()`](/docs/ios/sdk-reference/getCustomerInfo), it forces a server refresh.

## Requirements

Available in SuperwallKit `4.19.0` and later. [Configure Superwall](/docs/ios/sdk-reference/configure) before calling it. Your server must have reported the purchase to Superwall; this method does not query your billing provider.

## Signature

```swift
@discardableResult
public func refreshCustomerInfo() async -> CustomerInfo

public func refreshCustomerInfo(completion: @escaping (CustomerInfo) -> Void)
```

<TypeTable
  type="{
  completion: {
    type: &#x22;(CustomerInfo) -> Void&#x22;,
    description: &#x22;Called with the updated customer info, or the current value if the fetch fails. Only used by the completion-handler overload.&#x22;,
  },
}"
/>

## Usage

After your server confirms it has reported the purchase:

```swift
let customerInfo = await Superwall.shared.refreshCustomerInfo()
print(customerInfo.entitlements)
```

Or use a completion handler:

```swift
Superwall.shared.refreshCustomerInfo { customerInfo in
  DispatchQueue.main.async {
    self.updatePurchaseHistory(customerInfo)
  }
}
```

The fetched entitlements update [`customerInfo`](/docs/ios/sdk-reference/customerInfo) and [`entitlements`](/docs/ios/sdk-reference/entitlements). The SDK already refreshes entitlements in the background after a successful custom product purchase, including when your `PurchaseController` returns `.purchased`. Call this method if server reporting finishes later. Apps also refresh entitlements on foreground, including apps without web paywalls.

## Limitations

* If the fetch fails, the method returns the current `customerInfo`; it does not throw. A returned value alone does not confirm the server has granted access.
* In [Test Mode](/docs/ios/guides/test-mode), it makes no request and returns the test mode customer info.
* A `PurchaseController` remains responsible for managing [`subscriptionStatus`](/docs/ios/sdk-reference/subscriptionStatus).

## Related

* [Custom Store Products](/docs/ios/guides/custom-store-products)
* [`getCustomerInfo()`](/docs/ios/sdk-reference/getCustomerInfo)
* [`customerInfo`](/docs/ios/sdk-reference/customerInfo)