# 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

# Multiple Choice

Capture user selections with multiple choice elements for branching, personalization, and data collection.

The multiple choice element presents a set of options for users to select from. It is commonly used in onboarding flows to gather preferences, capture survey responses, or enable [branching](/docs/dashboard/dashboard-creating-flows/linking-pages) based on user input.

### Adding a multiple choice element

To add a multiple choice element:

1. In the left sidebar, click **+** to add a new element.
2. Choose **Multiple Choice** under the "Onboarding" header.

![](https://claude-centralize-agent-preamble-superwall-docs.staffbar.workers.dev/docs/images/component_add_mc.jpg)

A multiple choice component has configuration options to add items, randomize ordering, and more. Select it from the sidebar, and you'll see these options on the right sidebar:

![](https://claude-centralize-agent-preamble-superwall-docs.staffbar.workers.dev/docs/images/comps_mc_props.jpg)

### Selection mode

You can configure whether users select one option or multiple:

* **Single-select:** Users pick one option. The selection replaces any previous choice.
* **Multi-select:** Users can pick multiple options. All selections are stored.

### Randomize order

Enable **Randomize order** to shuffle the options each time the element appears. This is useful for surveys where you want to reduce selection bias from item ordering.

### Items

Each choice has two parts:

* **Label:** The text users see (e.g., "Grow subscriptions").
* **Value:** The internal value stored when selected (e.g., `goal_grow`).

Keep values short and consistent. Use lowercase letters and underscores for readability (e.g., `preferred_plan`, `user_goal`).

To add more choices, click **+ Add** in the component editor. You can reorder choices by dragging them.

### Using selections

Any multiple choice item is available as a variable. You can view variables either from the left side [variables](/docs/dashboard/dashboard-creating-paywalls/paywall-editor-variables) menu, or via the floating toolbar. Either case, it's exposed via **Element -> Multiple Choice**.

Two variables are available for each multiple choice element:

* **`selectedValue`:** The programmatic value of the selected choice (e.g., `goal_grow`). Use this for routing conditions, storing as user attributes, or any logic that depends on a stable internal value.
* **`selectedLabel`:** The display label of the selected choice (e.g., "Grow subscriptions"). This is useful for showing the user's selection back to them in text on a later page. If localization is active, `selectedLabel` returns the translated label for the user's locale.

When a user makes a selection, these variables can be used in several ways:

* **Routing conditions:** Branch the flow based on what the user selected. See [branching](/docs/dashboard/dashboard-creating-flows/linking-pages#branching).
* **User attributes:** Store the selection as a user attribute for later personalization or analytics.
* **Dynamic values:** Reference the selection in text elsewhere on the page or in later pages.

### Using selections for branching

Multiple choice is the primary way to enable conditional branching in flows. After a user selects an option, you can route them to different pages based on their choice.

For example, if you ask "What is your primary goal?" with options like "Grow subscriptions" and "Reduce churn," you can send each group to a tailored page.

See [Linking Pages](/docs/dashboard/dashboard-creating-flows/linking-pages) for detailed branching setup.

### Localization

Multiple choice labels can be localized just like text elements. When you add a language in the [localization panel](/docs/dashboard/dashboard-creating-paywalls/paywall-editor-localization), choice labels are included alongside your other translatable strings. This means:

* **AI Localize** translates choice labels automatically with the rest of your text.
* **CSV export/import** includes choice labels as rows, so your translation workflow covers them.
* **Missing translation filters** account for choice labels, so you can spot untranslated options.
* **Outdated detection** flags choice labels when the base text changes after translation.

When a user makes a selection while localization is active, the `selectedLabel` variable returns the translated text for their locale.

> **Tip:** Multiple choice elements work in both standalone paywalls and multi-page flows. In flows, they unlock branching. In paywalls, they can capture preferences before purchase.