# 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

# Localizing Paywalls with Dynamic Values

How to display localized paywall text using dynamic values and the device locale, without needing the built-in localization feature.

You can localize your paywall text for multiple languages using dynamic values in the paywall editor. This approach uses the device's locale to conditionally display different text for each language, and works on any Superwall plan.

### How it works

The paywall editor exposes `device.deviceLocale` (e.g. `en_US`, `fr_FR`) and `device.deviceLanguageCode` (e.g. `en`, `fr`) as built-in variables. By combining these with dynamic values, you can set up rules that show different text depending on the user's language.

### Step-by-step setup

1. Open your paywall in the editor and click on the text component you want to localize.
2. Click on the text property in the component editor, then choose **Dynamic** from the dropdown. This opens the dynamic values editor.
3. Click **Add Value**, then configure a rule:
   * Set the **if** condition to `device.deviceLanguageCode` **equals** your target language code (e.g. `fr` for French).
   * Set the **then** value to the translated string for that language.
   * Repeat this for each language you want to support. Use the **otherwise** value for your default language (typically English).
4. Apply the same approach to every text component on your paywall that needs localization.
5. Click **Publish** to save your changes. The paywall will now display the correct text based on the user's device language.

For example:

| Condition                               | Then value                    |
| --------------------------------------- | ----------------------------- |
| `device.deviceLanguageCode` equals `fr` | Commencez votre essai gratuit |
| `device.deviceLanguageCode` equals `es` | Comienza tu prueba gratuita   |
| Otherwise                               | Start your free trial         |

> **Tip:** Use `device.deviceLanguageCode` (e.g. `en`, `fr`) when you want to match broadly by language. Use `device.deviceLocale` (e.g. `en_US`, `en_GB`, `fr_FR`) when you need region-specific variants.

### Testing localized text

To test your localized paywall, change your device's language in the system settings and reopen the paywall. The dynamic values will evaluate based on the updated locale.

You can also preview different language states directly in the editor by temporarily changing the value of `device.deviceLanguageCode` in the **Variables** sidebar.

> **Note:** This approach is separate from the built-in localization feature available on the Startup plan, which provides AI-powered translations and a dedicated localization management UI. If you need to localize many paywalls or manage translations at scale, consider using the built-in localization tools instead.