# 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

# Why is my webhook's originalAppUserId different from the user ID I set?

## Context

When receiving webhook events from Superwall, you may notice that the originalAppUserId in the webhook payload doesn't match the user ID you set using the identify API. This is important for tracking user transactions and attributing payments correctly.

## Answer

To ensure the correct user ID appears in webhook events, you need to use a compatible SDK version:

* For iOS: SDK version 4.6.0 or higher

* For Android: Use the latest SDK version and configure `passIdentifiersToPlayStore` in your `SuperwallOptions`

* For Expo: expo-superwall version 0.2.7 or higher

**Timing Requirement:** You must call `identify()` with your custom user ID **before** any transactions are made. If you call `identify()` after a purchase has already occurred, the webhook will still contain the original alias ID (starting with `$superwallAlias:`) rather than your custom user ID.

**Best Practice:** Call `identify()` immediately after user login or authentication in your app, before presenting any paywalls or allowing purchases. This ensures all subsequent transactions will be attributed to your custom user ID in webhook events.

Important: For users who have already made transactions on a lower SDK version, the originalAppUserId will remain incorrect even after updating. This only affects historical transactions - new transactions from new users will show the correct ID after updating to the compatible SDK version.

## Additional Android Configuration

For Android apps, you must also configure the SDK to pass user identifiers to the Play Store:

val options = SuperwallOptions()
options.passIdentifiersToPlayStore = true
Superwall.configure(applicationContext, "YOUR\_API\_KEY", options)

Ensure your user IDs do not contain personally identifiable information (PII), as this could prevent transmission to the Play Store.