# 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

# Sandbox Purchases

Test with your web paywalls by using sandbox products.

### Purchase flow overview

When a user clicks on a button to purchase a product, the process will switch over to Stripe's checkout flow:

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

Once the purchase goes through successfully, they'll be taken to a page where Superwall prompts them to:

1. Download the app.
2. Click the redemption link.

> **Note:** Users should click the redemption link *on the device where the app is installed*. If the setting for "Redeemable on Desktop" is diabled, they'll be prompted to continue on an iOS device.

## Tab

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

## Tab

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

From there, the [redemption flow](/docs/sdk/guides/web-checkout/linking-membership-to-iOS-app) occurs.

### Testing a purchase

To test a purchase:

1. Add a [sandbox product](/docs/web-checkout/web-checkout-adding-a-stripe-product#creating-sandbox-products-to-test-with) to a paywall.
2. Visit the paywall URL and checkout.
3. Choose "Card" for the payment method.
4. For the card number, use `4242 4242 4242 4242` with any expiration date later than today, any CVC and fill out the name and zip code.

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

This will allow you to checkout and go through the entire flow to debug issues, test it out on a device and more.

### Testing Adaptive Pricing

If you enabled [Stripe Adaptive Pricing](/docs/web-checkout/web-checkout-adaptive-pricing), test local currency presentment with a location-formatted email address. Add `+location_XX` before the `@`, where `XX` is a two-letter country code.

For Web2App, pass the email through the checkout link and URL-encode the `+` character:

```plaintext
https://caffeinepal.superwall.app/black-friday-promo?email=test%2Blocation_FR@example.com
```

For App2Web, set the user's `email` attribute to a location-formatted email before starting checkout. If you also set `stripe_customer_id`, use a Stripe test customer whose email includes the same `+location_XX` suffix.