# 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

# Using RevenueCat

Handle a deep link in your app and use the delegate methods to link web checkouts with RevenueCat.

After purchasing from a web paywall, the user will be redirected to your app by a deep link to redeem their purchase on device. Please follow our [Post-Checkout Redirecting](/docs/android/guides/web-checkout/post-checkout-redirecting) guide to handle this user experience.

> **Note:** If you're using Superwall to handle purchases, then you don't need to do anything here.

> **Warning:** You only need to use a `PurchaseController` if you want end-to-end control of the purchasing pipeline. The recommended way to use RevenueCat with Superwall is by putting it in observer mode.

If you're using your own `PurchaseController`, you should follow our [Redeeming In-App](/docs/android/guides/web-checkout/linking-membership-to-iOS-app) guide.

### Using a PurchaseController with RevenueCat

If you're using RevenueCat, you'll need to follow [steps 1 to 4 in their guide](https://www.revenuecat.com/docs/web/integrations/stripe) to set up Stripe with RevenueCat. Then, you'll need to
associate the RevenueCat customer with the Stripe subscription IDs returned from redeeming the code. You can do this by extracting the ids from the `RedemptionResult` and sending them to RevenueCat's API
by using the `didRedeemLink(result:)` delegate method:

> **Warning:** This flow is for Stripe subscriptions. Stripe one-time purchases can return Stripe Checkout session IDs through the same legacy `stripeSubscriptionIds` field, but those IDs are not Stripe subscription IDs. Handle one-time purchases with Superwall entitlements or your own backend instead of sending those IDs to RevenueCat's Stripe subscription endpoint.

```kotlin
import com.revenuecat.purchases.Purchases
import com.superwall.sdk.Superwall
import com.superwall.sdk.delegate.SuperwallDelegate
import com.superwall.sdk.models.redemption.RedemptionResult
import kotlinx.coroutines.CoroutineScope
import kotlinx.coroutines.Dispatchers
import kotlinx.coroutines.launch
import kotlinx.coroutines.withContext
import okhttp3.MediaType.Companion.toMediaType
import okhttp3.OkHttpClient
  import okhttp3.Request
  import okhttp3.RequestBody.Companion.toRequestBody
  import org.json.JSONObject
  import java.io.IOException

class SWDelegate : SuperwallDelegate {
  private val client = OkHttpClient()
  private val coroutineScope = CoroutineScope(Dispatchers.IO)
  
  // The user tapped on a deep link to redeem a code
  override fun willRedeemLink() {
    Log.d("Superwall", "[!] willRedeemLink")
    // Optionally show a loading indicator here
  }

  // Superwall received a redemption result and validated the purchase with Stripe.
  override fun didRedeemLink(result: RedemptionResult) {
    Log.d("Superwall", "[!] didRedeemLink: $result")
    // Send Stripe IDs to RevenueCat to link purchases to the customer

    // Get a list of subscription ids tied to the customer.
    val stripeSubscriptionIds = when (result) {
      is RedemptionResult.Success -> result.stripeSubscriptionIds
      else -> null
    } ?: return

    val revenueCatStripePublicAPIKey = "strp....." // replace with your RevenueCat Stripe Public API Key
    val appUserId = Purchases.sharedInstance.appUserID

    // In the background using coroutines...
    coroutineScope.launch {
        // For each subscription id, link it to the user in RevenueCat
        stripeSubscriptionIds.forEach { stripeSubscriptionId ->
        try {
          val json = JSONObject().apply {
            put("app_user_id", appUserId)
            put("fetch_token", stripeSubscriptionId)
          }

          val requestBody = json.toString()
            .toRequestBody("application/json".toMediaType())

          val request = Request.Builder()
            .url("https://api.revenuecat.com/v1/receipts")
            .post(requestBody)
            .addHeader("Content-Type", "application/json")
            .addHeader("Accept", "application/json")
            .addHeader("X-Platform", "stripe")
            .addHeader("Authorization", "Bearer $revenueCatStripePublicAPIKey")
            .build()

            client.newCall(request).execute().use { response ->
              val responseBody = response.body?.string().orEmpty()

              if (!response.isSuccessful) {
                throw IOException("RevenueCat responded with ${response.code}: $responseBody")
              }

              Log.d("Superwall", "[!] Success: linked $stripeSubscriptionId to user $appUserId: $responseBody")
            }
        } catch (e: Exception) {
          Log.e("Superwall", "[!] Error: unable to link $stripeSubscriptionId to user $appUserId", e)
        }
      }

      /// After all network calls complete, invalidate the cache
      Purchases.sharedInstance.getCustomerInfo(
        onSuccess = { customerInfo ->
          /// If you're using RevenueCat's `UpdatedCustomerInfoListener`, or keeping Superwall Entitlements in sync
          /// via RevenueCat's listener methods, you don't need to do anything here. Those methods will be
          /// called automatically when this call fetches the most up to date customer info, ignoring any local caches.

          /// Otherwise, if you're manually calling `Purchases.sharedInstance.getCustomerInfo` to keep Superwall's entitlements
          /// in sync, you should use the newly updated customer info here to do so.
          
          /// You could always access web entitlements here as well
          /// val webEntitlements = Superwall.instance.entitlements.web
        },
        onError = { error ->
          Log.e("Superwall", "Error getting customer info", error)
        }
      )

      // After all network calls complete, update UI on the main thread
      withContext(Dispatchers.Main) {
        // Perform UI updates on the main thread, like letting the user know their subscription was redeemed
      }
    }
  }
}
```

> **Note:** The example surfaces non-200 responses and network exceptions so you can add retries, user messaging,
> or monitoring. Customize the error handling to fit your production logging and UX.

> **Warning:** If you call `logIn` from RevenueCat's SDK, then you need to call the logic you've implemented
> inside `didRedeemLink(result:)` again. For example, that means if `logIn` was invoked from
> RevenueCat, you'd either abstract out this logic above into a function to call again, or simply
> call this function directly.

The web entitlements will be returned along with other existing entitlements in the `CustomerInfo` object accessible via RevenueCat's SDK.

If you're logging in and out of RevenueCat, make sure to resend the Stripe subscription IDs to RevenueCat's endpoint after logging in.