# 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 retrieve Stripe customer data after web checkout?

Learn how to access the Stripe customer ID and email after a user completes a web checkout purchase.

## Context

After a user completes a web checkout purchase via Stripe, you may need to access their Stripe customer ID and email for integration with your backend systems or third-party services.

## Answer

Use the `didRedeemLink(result:)` delegate method to access Stripe customer data when a redemption link is successfully processed.

### Accessing Stripe customer ID and email

When the redemption result is successful, the `RedemptionInfo` object contains a `PurchaserInfo` with the customer's email and store identifiers:

```swift
func didRedeemLink(result: RedemptionResult) {
    guard case let .success(_, redemptionInfo) = result else { return }

    // Get the customer's email
    let email = redemptionInfo.purchaserInfo.email

    // Get the Stripe customer ID and Stripe purchase identifiers
    if case let .stripe(customerId, subscriptionIds) = redemptionInfo.purchaserInfo.storeIdentifiers {
        print("Stripe Customer ID: \(customerId)")
        print("Stripe purchase IDs: \(subscriptionIds)")

        // Send to your backend or analytics
        sendToBackend(
            stripeCustomerId: customerId,
            email: email,
            subscriptionIds: subscriptionIds
        )
    }
}
```

> **Note:** The `subscriptionIds` value keeps its legacy name for compatibility. For Stripe subscriptions, it contains `sub_` IDs. For Stripe one-time purchases, it can contain Stripe Checkout session IDs.

### What happens if the user kills the app during checkout?

If a user completes the Stripe checkout but terminates the app before returning, the `didRedeemLink(result:)` callback will not fire. However, their purchase is not lost.

**Recovery mechanisms:**

1. **Redemption email**: After a successful Stripe checkout, Superwall automatically sends the customer an email with an activation link. When they tap it, your app opens and `didRedeemLink` fires with the Stripe customer ID and email.

2. **Plan management page**: Users can visit `https://{yoursubdomain}.superwall.app/manage`, enter their email, and receive a new redemption link.

3. **Automatic entitlement sync**: The SDK polls for web entitlements when the app enters foreground, so subscription and entitlement status updates automatically. However, this sync only updates access and does not trigger `didRedeemLink`, meaning you will not receive the Stripe customer ID or email through this path.

> **Warning:** To programmatically receive the Stripe customer ID and email, the user must tap a redemption link (either from the automatic email or the manage page).

### Stripe metadata

Superwall automatically includes your app user ID in Stripe checkout metadata. For subscriptions, it is also included in subscription metadata. The key `_sw_app_user_id` contains the user ID you set via `Superwall.shared.identify(userId:)`.

This allows you to correlate Stripe purchases with your users directly in Stripe or through webhooks.

## Related

* [Post-Checkout Redirecting](/docs/sdk/guides/web-checkout/post-checkout-redirecting)
* [Stripe One-Time Purchases](/docs/web-checkout/web-checkout-stripe-one-time-purchases)
* [How do I disable the activation link email for web checkout?](/docs/support/web-checkout/3969573187-how-do-i-disable-the-activation-link-email-for-web-checkout)
* [Web Checkout FAQ](/docs/web-checkout/web-checkout-faq)