# 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

# Localization

> **Warning:** The legacy editor is deprecated. Please visit the docs covering our new
> [editor](/docs/dashboard/dashboard-creating-paywalls/paywall-editor-overview).

You can localize paywalls for specific locales. The SDK will select the appropriate paywall locale based on the device's locale settings. If the chosen locale is not available, the English version will be displayed.

Select a paywall from the dashboard and click on **EN** to show the locale dropdown. Then click on &#x2A;*Edit localizations ->**:

![](https://2a2314a4-superwall-docs.staffbar.workers.dev/docs/images/18dfbe0-Screenshot_2023-03-03_at_12.37.47.png)

Click **Download Template** to download the strings file for all of your paywalls:

![](https://2a2314a4-superwall-docs.staffbar.workers.dev/docs/images/8e8f90f-Screenshot_2023-03-03_at_11.59.38.png)

This file follows a `"original text" = "translated text"` format for each of your paywall text elements. You should translate all the strings in the file into your desired language. [Variables](/docs/dashboard/dashboard-creating-paywalls/paywall-editor-variables) inside text fields will be replaced with `{}` in the original text.

> 🚧
>
> English-language variables such as `{ primary.trialPeriodText }` cannot be localized as these are substituted by the SDK in English only. If you want to localize these, you'll need to hardcode them into the paywall with text, e.g. "3-day", so that their text can be picked up and substituted by the localization template.

Once you’ve completed translation, click **Add Language**:

![](https://2a2314a4-superwall-docs.staffbar.workers.dev/docs/images/cb0577f-Screenshot_2023-03-03_at_12.00.42.png)

Then select from a locale from the dropdown:

![](https://2a2314a4-superwall-docs.staffbar.workers.dev/docs/images/17a093d-Screenshot_2023-03-03_at_12.00.49.png)

Upload your translation by clicking on the **Upload Button**:

![](https://2a2314a4-superwall-docs.staffbar.workers.dev/docs/images/c195353-Screenshot_2023-03-03_at_12.26.41.png)

Then click on the pop up and select your strings file:

![](https://2a2314a4-superwall-docs.staffbar.workers.dev/docs/images/fe3607e-Screenshot_2023-03-03_at_12.27.21.png)

Click the `**<- Paywall Editor**` button to head back to your paywall. You can preview your localized paywall by selecting the newly translated locale from your localization dropdown:

![](https://2a2314a4-superwall-docs.staffbar.workers.dev/docs/images/8a40add-Screenshot_2023-03-03_at_12.44.52.png)

You can also preview it on device using the [In-App Previews](/docs/sdk/quickstart/in-app-paywall-previews).

### Third Party Localization

If you choose to use a third party localization service, Superwall supports a few! We support Lokalise and Crowdin.

Once configured, Superwall will automatically synchronize your strings to your chosen provider and subscribe to updates.

> 👇
>
> Superwall won't grab translated variables until they've been marked as "Reviewed" or "Approved" in your chosen provider.

#### Lokalise

To set up Lokalise, you'll need to [generate an API key](https://app.lokalise.com/profile) from your dashboard.

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

Grant the token `read and write` access to your project.

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

Once you've got the token, head on over to Superwall and select Settings -> Localization. Choose `Lokalise` from the dropdown and enter your API key.

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

Once you've added a valid API key, you should see a dropdown for the Lokalise project to use.

Select your project, click save, then start localizing!

#### Crowdin

To set up Crowdin, you'll need to [generate an API key](https://crowdin.com/settings#api-key).

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

Grant the API key the `webhooks` and all `projects` scopes.

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

Once you've got the token, head on over to Superwall and select Settings -> Localization. Choose `Crowdin` from the dropdown and enter your API key.

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

Once you've added a valid API key, you should see a dropdown for the Crowdin project to use.

Select your project, click save, then start localizing!