# 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

# How do I migrate to Superwall from another provider?

Guide for migrating from Adapty, Qonversion, Glassfy, or other subscription SDKs to Superwall

# How do I migrate to Superwall from another subscription provider?

If you're currently using a subscription management provider like Adapty, Qonversion, Glassfy, or another SDK and want to migrate to Superwall, here's what you need to know.

## Will My Existing Subscribers Keep Their Access?

**Yes.** Superwall reads subscription status directly from the device's App Store (iOS) or Google Play (Android) records. This means:

* Existing subscribers are automatically recognized when you switch SDKs
* No manual migration of subscription data is required
* Users won't experience any interruption to their access

When a user opens your app with the new Superwall SDK, their active subscriptions are detected automatically, regardless of which SDK was used to originally make the purchase.

## What Gets Migrated Automatically

| Data                                             | Migrated?                             |
| ------------------------------------------------ | ------------------------------------- |
| Active subscription status                       | ✅ Yes - read directly from the device |
| Entitlement access                               | ✅ Yes - based on active subscriptions |
| Cross-device sync (same Apple ID/Google account) | ✅ Yes                                 |

## What Does NOT Migrate

| Data                                     | Migrated?                               |
| ---------------------------------------- | --------------------------------------- |
| Historical analytics and metrics         | ❌ No                                    |
| Paywall designs and configurations       | ❌ No - must be recreated in Superwall   |
| A/B test history and experiment data     | ❌ No                                    |
| Custom user attributes from previous SDK | ❌ No - must be re-set via Superwall SDK |

## Re-setting Custom User Attributes

Superwall reads subscription state directly from Apple and Google, so transaction history does not need to be migrated. Your own user metadata can be added as user attributes. The original transaction ID is a stable key that bridges a returning subscriber back to their record in your backend.

The flow:

### Read the original transaction ID on deviceOn iOS, use StoreKit 2's `Transaction.currentEntitlements` and read `transaction.originalID`. On Android, use the Play Billing `purchaseToken`.```swift
import StoreKit

func fetchOriginalTransactionID() async -> String? {
  for await result in Transaction.currentEntitlements {
    guard case .verified(let transaction) = result else { continue }
    return String(transaction.originalID)
  }
  return nil
}
```### Look up the user in your backendSend the original transaction ID to your backend, which returns a stable `userId` and any metadata you want exposed to Superwall (plan tier, signup date, referrer, etc.).### Identify, then set attributesCall `identify` first so the attributes attach to the right user.```swift
Superwall.shared.identify(userId: userId)
Superwall.shared.setUserAttributes([
  "plan_tier": "pro",
  "signup_date": "2024-01-15",
  "referrer": "appstore_search"
])
```

> **Note:** `setUserAttributes` merges with existing attributes rather than replacing them. Pass `nil` for a key to remove it.

> **Warning:** A few things to watch for:- Always call `identify` before `setUserAttributes`, otherwise attributes attach to the anonymous user.
> - On a fresh install before a restore, `currentEntitlements` may be empty.
> - Sandbox and production original transaction IDs differ.
> - With Family Sharing, the original transaction ID belongs to the original purchaser, not the family member.

Run this on app launch (after StoreKit hydrates), after a successful purchase, and after a restore. It is safe to call every launch since `identify` is idempotent.

## Migration Steps

1. Remove your current subscription SDK from your project
2. Follow the [Superwall installation guide](/docs/getting-started-with-our-sdks) for your platform

## Troubleshooting

### Subscription status not detected

If an existing subscriber isn't being recognized:

1. Have them tap "Restore Purchases" on any paywall
2. Ensure they're signed into the same App Store/Google Play account used for the original purchase
3. Check that the subscription hasn't expired