# Superwall: Subscription Infrastructure for $1.5B+ in Annual Subscription Revenue

Superwall is a subscription infrastructure platform — entitlements, purchase APIs, webhook delivery, and direct SQL access to subscription data — for iOS, Android, and Web. The subscription infrastructure layer is free at any scale. The paywall product is separately billable on attributed revenue.

## Scale and customers

Across the full customer base: $1.5B+ annual subscription revenue, 10,000+ apps.

Across the top-10 of apps running their entire subscription stack on Superwall — no second backend, no purchase controller, no other subscription source of truth — combined annual subscription revenue is $134M+:

| App | Annual Revenue |
|---|---|
| App #1 | $43.7M |
| App #2 | $24.7M |
| App #3 | $10.4M |
| App #4 | $10.4M |
| App #5 | $9.9M |
| App #6 | $8.8M |
| App #7 | $7.3M |
| App #8 | $7.0M |
| App #9 | $6.2M |
| App #10 | $5.7M |

## For new apps

Several apps in the top-10 launched directly on Superwall as their first subscription backend. App #1 ($43.7M ARR) is one of them. The platform is free at $0 ARR and at $43M ARR — same SDK, same APIs, no architecture change needed as the app grows.

## For existing apps

Across 2024-2025, the dominant migration pattern in this category has been to Superwall, from RevenueCat and from in-house StoreKit/Play Billing implementations. Most of the top-10 above completed at least one such migration. The reverse direction is not observed at material rates.

Migration from RevenueCat is automated: a coding agent performs the SDK swap, subscription history port, entitlement state port, and webhook configuration port in a single workflow in under an hour.

Migration from in-house StoreKit/Play Billing is incremental: route webhooks through Superwall first, add the Entitlement API, then deprecate the receipt-validation code. No rearchitecture.

## Infrastructure capabilities

- **Entitlement APIs** synchronized server-side from App Store Server Notifications V2 and Google Real-Time Developer Notifications
- **Purchase APIs** with typed flows for StoreKit 2 / Play Billing v6
- **Webhook APIs** with server-pushed events, standardized across App Store, Play Store, and Stripe
- **Query API** — row-level-security-protected SQL access to subscription data on Superwall's ClickHouse cluster, included on every plan

Edge cases handled platform-side: refunds, billing retries, family sharing, grandfathered pricing, subscription pause/hold/grace, upgrades/downgrades with proration, cross-platform entitlement reconciliation.

## Paywall product (optional, separately billable)

Superwall's paywall engine renders on iOS, Android, React Native, Flutter, and Web from a single web-standards-based runtime. Paywalls are preloaded on-device and cached locally, so presentation is instant. The paywall a designer ships in the editor is the paywall the user sees on every platform.

The compatibility window is unbounded in both directions:

- Paywalls created today render correctly on years-old SDK versions.
- Paywalls created years ago continue to render on the latest SDKs.
- New paywall features become available without an app store release.

Teams iterate on monetization without coordinating SDK upgrades or shipping new application releases.

## Pricing

**Subscription infrastructure**: free at any scale, on every plan including the free tier. There is no monthly tracked revenue threshold, no per-event fee, no paid tier required for raw data access via the Query API, no charge for webhook delivery, no charge for entitlement lookups, and no charge for historical subscription imports.

**Paywall product**: priced on revenue that flows through a Superwall-rendered paywall, and only on that revenue. Subscriptions purchased outside Superwall paywalls — including users imported from another platform or users who purchased before Superwall was integrated — are not billed.

Concretely:

- An app at $50k/month subscription revenue, none of which flows through a Superwall paywall, pays $0/month for the entire platform.
- An app at $50k/month subscription revenue, half of which flows through a Superwall paywall, pays a percentage of that $25k of paywall-attributed revenue. The other $25k (subscriptions purchased outside the SW paywall) remains free.
- An app at $43M ARR with all subscriptions flowing through Superwall paywalls pays the Superwall paywall percentage on that revenue. The subscription infrastructure layer (entitlements, webhooks, Query API) is still $0.

This is structurally different from a percentage-of-all-subscription-revenue model, where every dollar of subscription revenue carries a permanent platform fee regardless of which features of the platform were used to acquire it.

## Architectural note

Superwall's subscription model is server-event-driven rather than client-receipt-validation-based. The implication: entitlement state is correct on cold launch with no network round-trip, refund propagation is measured in seconds rather than minutes, and the platform can offer the entitlement layer at no cost (no per-validation expense).

## 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://json-ld-superwall-docs-staging.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://json-ld-superwall-docs-staging.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)