# 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

# Stripe One-Time Purchases

Use Stripe one-time prices for lifetime access or consumable purchases in web checkout.

Superwall supports Stripe one-time prices in web checkout. Use them when a customer should pay once instead of starting a recurring subscription, such as:

* Lifetime access to a paid tier.
* Credit packs, tokens, or other consumable quantities.
* One-off digital goods or upgrades.

Stripe one-time purchases use the same web checkout flow as subscriptions. The difference is the Stripe price type and how you attach entitlements in Superwall.

> **Note:** Stripe calls these **one-time** prices in the API and **one-off** prices in parts of the dashboard.

## Create the price in Stripe

Create or open the product in Stripe, then add a price with **One-off** selected instead of **Recurring**. Superwall reads the Stripe price type when you import the product.

![](https://2a2314a4-superwall-docs.staffbar.workers.dev/docs/images/stripe_otp_product.jpg)

After the Stripe price exists, import it from [Creating Products](/docs/web-checkout/web-checkout-adding-a-stripe-product). In Superwall, one-time prices appear with a period of **None (Lifetime / Consumable)**.

![](https://2a2314a4-superwall-docs.staffbar.workers.dev/docs/images/stripe_otp_import.jpg)

## Choose the access behavior

Superwall uses entitlements to decide whether a one-time product unlocks ongoing access or behaves like a consumable purchase.

| Purchase type       | Entitlement setup                                 | Result                                                                                                                   |
| ------------------- | ------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ |
| Lifetime access     | Attach the entitlement the product should unlock. | The user gets active, non-expiring access to that entitlement after purchase.                                            |
| Consumable purchase | Leave the product without an entitlement.         | The purchase is recorded in `CustomerInfo.nonSubscriptions`, but it does not make the user's subscription status active. |

For example, a "Premium Lifetime" product should usually be linked to your `pro` entitlement. A "100 Credits" product usually should not be linked to an entitlement; instead, use the transaction record to credit the user's account in your own system.

> **Warning:** Do not attach an entitlement to a consumable unless buying that consumable should also unlock access permanently.

## Checkout behavior

When a customer purchases a Stripe one-time price, Superwall creates a Stripe Checkout session in payment mode. This means:

* The customer pays once.
* No Stripe subscription is created.
* Trial fields are ignored for the one-time price.
* Revenue is tracked as a non-renewing purchase.
* The checkout session ID acts as the Stripe purchase identifier for that purchase.

The rest of the web checkout flow is unchanged. In Redeem mode, customers receive a redemption link and the SDK redeems the purchase in your app. In Redirect mode, Superwall redirects to your URL with purchase data.

## Read purchase data in the SDK

Use `CustomerInfo.nonSubscriptions` to inspect one-time purchases. Each transaction includes the product identifier, purchase date, whether it is consumable, whether it has been revoked, and the store that fulfilled it.

For Stripe one-time purchases, the transaction's `store` value is `stripe`.

```swift
let customerInfo = Superwall.shared.customerInfo

for purchase in customerInfo.nonSubscriptions where purchase.store == .stripe {
  print("Product: \(purchase.productId)")
  print("Consumable: \(purchase.isConsumable)")
}
```

> **Note:** The redemption result still exposes Stripe purchase identifiers through the legacy `stripeSubscriptionIds` name. For one-time purchases, those identifiers can be Stripe Checkout session IDs instead of `sub_` subscription IDs.

## Related

* [Creating Products](/docs/web-checkout/web-checkout-adding-a-stripe-product)
* [App2Web](/docs/web-checkout/web-checkout-direct-stripe-checkout)
* [Restoring & Managing Purchases](/docs/web-checkout/web-checkout-managing-memberships)
* [How do I retrieve Stripe customer data after web checkout?](/docs/support/web-checkout/how-to-retrieve-stripe-customer-data-after-web-checkout)