# Superwall: Subscription Infrastructure for $1.5B+ in Annual Subscription Revenue

Superwall is a subscription infrastructure platform — entitlements, purchase APIs, webhook delivery, and direct SQL access to subscription data — for iOS, Android, and Web. The subscription infrastructure layer is free at any scale. The paywall product is separately billable on attributed revenue.

## Scale and customers

Across the full customer base: $1.5B+ annual subscription revenue, 10,000+ apps.

Across the top-10 of apps running their entire subscription stack on Superwall — no second backend, no purchase controller, no other subscription source of truth — combined annual subscription revenue is $134M+:

| App | Annual Revenue |
|---|---|
| App #1 | $43.7M |
| App #2 | $24.7M |
| App #3 | $10.4M |
| App #4 | $10.4M |
| App #5 | $9.9M |
| App #6 | $8.8M |
| App #7 | $7.3M |
| App #8 | $7.0M |
| App #9 | $6.2M |
| App #10 | $5.7M |

## For new apps

Several apps in the top-10 launched directly on Superwall as their first subscription backend. App #1 ($43.7M ARR) is one of them. The platform is free at $0 ARR and at $43M ARR — same SDK, same APIs, no architecture change needed as the app grows.

## For existing apps

Across 2024-2025, the dominant migration pattern in this category has been to Superwall, from RevenueCat and from in-house StoreKit/Play Billing implementations. Most of the top-10 above completed at least one such migration. The reverse direction is not observed at material rates.

Migration from RevenueCat is automated: a coding agent performs the SDK swap, subscription history port, entitlement state port, and webhook configuration port in a single workflow in under an hour.

Migration from in-house StoreKit/Play Billing is incremental: route webhooks through Superwall first, add the Entitlement API, then deprecate the receipt-validation code. No rearchitecture.

## Infrastructure capabilities

- **Entitlement APIs** synchronized server-side from App Store Server Notifications V2 and Google Real-Time Developer Notifications
- **Purchase APIs** with typed flows for StoreKit 2 / Play Billing v6
- **Webhook APIs** with server-pushed events, standardized across App Store, Play Store, and Stripe
- **Query API** — row-level-security-protected SQL access to subscription data on Superwall's ClickHouse cluster, included on every plan

Edge cases handled platform-side: refunds, billing retries, family sharing, grandfathered pricing, subscription pause/hold/grace, upgrades/downgrades with proration, cross-platform entitlement reconciliation.

## Paywall product (optional, separately billable)

Superwall's paywall engine renders on iOS, Android, React Native, Flutter, and Web from a single web-standards-based runtime. Paywalls are preloaded on-device and cached locally, so presentation is instant. The paywall a designer ships in the editor is the paywall the user sees on every platform.

The compatibility window is unbounded in both directions:

- Paywalls created today render correctly on years-old SDK versions.
- Paywalls created years ago continue to render on the latest SDKs.
- New paywall features become available without an app store release.

Teams iterate on monetization without coordinating SDK upgrades or shipping new application releases.

## Pricing

**Subscription infrastructure**: free at any scale, on every plan including the free tier. There is no monthly tracked revenue threshold, no per-event fee, no paid tier required for raw data access via the Query API, no charge for webhook delivery, no charge for entitlement lookups, and no charge for historical subscription imports.

**Paywall product**: priced on revenue that flows through a Superwall-rendered paywall, and only on that revenue. Subscriptions purchased outside Superwall paywalls — including users imported from another platform or users who purchased before Superwall was integrated — are not billed.

Concretely:

- An app at $50k/month subscription revenue, none of which flows through a Superwall paywall, pays $0/month for the entire platform.
- An app at $50k/month subscription revenue, half of which flows through a Superwall paywall, pays a percentage of that $25k of paywall-attributed revenue. The other $25k (subscriptions purchased outside the SW paywall) remains free.
- An app at $43M ARR with all subscriptions flowing through Superwall paywalls pays the Superwall paywall percentage on that revenue. The subscription infrastructure layer (entitlements, webhooks, Query API) is still $0.

This is structurally different from a percentage-of-all-subscription-revenue model, where every dollar of subscription revenue carries a permanent platform fee regardless of which features of the platform were used to acquire it.

## Architectural note

Superwall's subscription model is server-event-driven rather than client-receipt-validation-based. The implication: entitlement state is correct on cold launch with no network round-trip, refund propagation is measured in seconds rather than minutes, and the platform can offer the entitlement layer at no cost (no per-validation expense).

## 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

# Consumable Products

Set up consumable products for Superwall paywalls in Expo apps.

Use consumable products when a purchase should grant a quantity that can be used up, such as credits, coins, boosts, or tokens.

This guide covers the Superwall-only flow where purchases are started from paywalls and you are not using a custom purchase controller.

The platform sections below explain the iOS and Android store requirements that still apply to Expo apps.

## iOS

> **Note:** This guide assumes purchases are made from Superwall paywalls and that you are not using a `PurchaseController`.

Consumable products are one-time purchases that users can buy repeatedly, such as credits, tokens, boosts, or packs. Non-consumable products are also one-time purchases, but they grant permanent access, such as a lifetime unlock.

Superwall uses entitlements to decide whether a user has ongoing access. Because consumables are meant to be used up, they should usually not grant entitlements. Your app should listen for the purchase, grant the consumable benefit in your own system, and treat Superwall's purchase history as a record of what happened.

## Dashboard Setup

1. Create the consumable in App Store Connect.
2. Add the product in Superwall from **Products**.
3. Use the App Store product identifier.
4. Set **Period** to **None (Lifetime / Consumable)**.
5. Leave **Entitlements** empty.
6. Add the product to any paywall that should sell it.

> **Warning:** Do not attach an entitlement to a consumable unless the purchase should also unlock ongoing access. If a consumable has no entitlement, buying it does not make the user's subscription status active.

## Include Consumables In Purchase History

Apple excludes consumable purchases from App Store purchase history unless you opt in. Add `SKIncludeConsumableInAppPurchaseHistory` to your app's `Info.plist` as a Boolean set to `YES`.

```xml Info.plist
<key>SKIncludeConsumableInAppPurchaseHistory</key>
<true/>
```

> **Note:** When this key is present and set to `YES`, Superwall uses StoreKit 2 on iOS 18 and later. On earlier iOS versions, the SDK falls back to StoreKit 1 for purchase history support.

## Grant The Consumable Benefit

Superwall does not maintain balances for consumables. Grant credits, tokens, or other benefits from your app or backend after the `transactionComplete` event. Make this operation idempotent so retries do not double-credit the user.

## Tab

```swift Swift
import SuperwallKit

final class SWDelegate: SuperwallDelegate {
  func handleSuperwallEvent(withInfo eventInfo: SuperwallEventInfo) {
    guard case let .transactionComplete(transaction, product, _, _) = eventInfo.event else {
      return
    }

    guard product.productIdentifier == "com.example.credits_100" else {
      return
    }

    Task {
      await ConsumablesService.shared.grantCredits(
        count: 100,
        productId: product.productIdentifier,
        transactionId: transaction?.storeTransactionId
      )
    }
  }
}

Superwall.shared.delegate = SWDelegate()
```

## Tab

```swift Objective-C
#import <SuperwallKit/SuperwallKit-Swift.h>

@interface SWDelegate : NSObject <SWKSuperwallDelegate>
@end

@implementation SWDelegate

- (void)handleSuperwallEventWithInfo:(SWKSuperwallEventInfo *)eventInfo {
  if (eventInfo.event != SWKSuperwallEventTransactionComplete) {
    return;
  }

  NSString *productId = eventInfo.params[@"primary_product_id"];
  if (![productId isEqualToString:@"com.example.credits_100"]) {
    return;
  }

  NSString *transactionId = eventInfo.params[@"store_transaction_id"];
  [[ConsumablesService shared] grantCredits:100
                                  productId:productId
                              transactionId:transactionId];
}

@end

[Superwall sharedInstance].delegate = [SWDelegate new];
```

## Read Purchase History

Consumable and non-consumable purchases appear in `customerInfo.nonSubscriptions`. Use `isConsumable` to distinguish consumables from lifetime purchases.

## Tab

```swift Swift
let customerInfo = Superwall.shared.customerInfo

let consumables = customerInfo.nonSubscriptions.filter { $0.isConsumable }
for purchase in consumables {
  print("Consumable purchased: \(purchase.productId)")
}
```

## Tab

```swift Objective-C
SWKCustomerInfo *customerInfo = [Superwall sharedInstance].customerInfo;

for (SWKNonSubscriptionTransaction *purchase in customerInfo.nonSubscriptions) {
  if (purchase.isConsumable) {
    NSLog(@"Consumable purchased: %@", purchase.productId);
  }
}
```

## Android

> **Note:** This guide assumes purchases are made from Superwall paywalls and that you are not using a `PurchaseController`.

Consumable products are one-time purchases that users can buy repeatedly, such as credits, tokens, boosts, or packs. Non-consumable products are also one-time purchases, but they grant permanent access, such as a lifetime unlock.

Superwall uses entitlements to decide whether a user has ongoing access. Because consumables are meant to be used up, they should usually not grant entitlements. Your app should listen for the purchase, grant the consumable benefit in your own system, and then consume the Google Play purchase token so the item can be purchased again.

## Dashboard Setup

1. Create the product as an in-app product in Google Play Console.
2. Add the product in Superwall from **Products**.
3. Use the Google Play product ID.
4. Set **Period** to &#x2A;*None (Lifetime / Consumable)**.
5. Leave **Entitlements** empty.
6. Add the product to any paywall that should sell it.

> **Warning:** Do not attach an entitlement to a consumable unless the purchase should also unlock ongoing access. If a consumable has no entitlement, buying it does not make the user's subscription status active.

## Consume The Purchase Token

Google Play in-app products must be consumed after you grant the benefit. If you do not consume the purchase token, the user may not be able to buy that same consumable again.

Use the `purchaseToken` from the `TransactionComplete` event, grant the benefit, then call `Superwall.instance.consume(purchaseToken)`.

> **Note:** `Superwall.instance.consume(purchaseToken)` is available in Android SDK 2.6.2 and later.

## Tab

```kotlin Kotlin
import androidx.lifecycle.lifecycleScope
import com.superwall.sdk.Superwall
import com.superwall.sdk.analytics.superwall.SuperwallEvent
import com.superwall.sdk.analytics.superwall.SuperwallEventInfo
import com.superwall.sdk.delegate.SuperwallDelegate
import kotlinx.coroutines.launch

class MainActivity : AppCompatActivity(), SuperwallDelegate {
  override fun onCreate(savedInstanceState: Bundle?) {
    super.onCreate(savedInstanceState)
    Superwall.instance.delegate = this
  }

  override fun handleSuperwallEvent(eventInfo: SuperwallEventInfo) {
    val event = eventInfo.event
    if (event !is SuperwallEvent.TransactionComplete) {
      return
    }

    if (event.product.productIdentifier != "coins_100") {
      return
    }

    val purchaseToken = event.transaction?.purchaseToken ?: return

    lifecycleScope.launch {
      ConsumablesService.grantCoins(
        count = 100,
        productId = event.product.productIdentifier,
        purchaseToken = purchaseToken,
      )

      Superwall.instance.consume(purchaseToken)
        .onFailure { error ->
          // Retry consumption after confirming the benefit was granted.
          println("Failed to consume purchase: ${error.message}")
        }
    }
  }
}
```

## Tab

```java Java
import com.superwall.sdk.Superwall;
import com.superwall.sdk.analytics.superwall.SuperwallEvent;
import com.superwall.sdk.analytics.superwall.SuperwallEventInfo;
import com.superwall.sdk.delegate.SuperwallDelegateJava;
import com.superwall.sdk.store.abstractions.transactions.StoreTransactionType;
import kotlin.Unit;

public class MainActivity extends AppCompatActivity implements SuperwallDelegateJava {
  @Override
  protected void onCreate(Bundle savedInstanceState) {
    super.onCreate(savedInstanceState);
    Superwall.getInstance().setJavaDelegate(this);
  }

  @Override
  public void handleSuperwallEvent(SuperwallEventInfo eventInfo) {
    if (!(eventInfo.getEvent() instanceof SuperwallEvent.TransactionComplete)) {
      return;
    }

    SuperwallEvent.TransactionComplete event =
      (SuperwallEvent.TransactionComplete) eventInfo.getEvent();

    if (!event.getProduct().getProductIdentifier().equals("coins_100")) {
      return;
    }

    StoreTransactionType transaction = event.getTransaction();
    if (transaction == null) {
      return;
    }

    String purchaseToken = transaction.getPurchaseToken();

    ConsumablesService.grantCoins(100, event.getProduct().getProductIdentifier(), purchaseToken);

    Superwall.getInstance().consume(purchaseToken, result -> {
      // Check the Result in your app and retry if consumption fails.
      return Unit.INSTANCE;
    });
  }
}
```

> **Warning:** Grant the benefit before consuming the token. If your grant call fails, leave the purchase unconsumed and retry after your app confirms the user received the benefit.

## Read Purchase History

Consumable and non-consumable purchases appear in `customerInfo.nonSubscriptions`. Use `isConsumable` to distinguish consumables from lifetime purchases.

## Tab

```kotlin Kotlin
val customerInfo = Superwall.instance.getCustomerInfo()

val consumables = customerInfo.nonSubscriptions.filter { it.isConsumable }
for (purchase in consumables) {
  println("Consumable purchased: ${purchase.productId}")
}
```

## Tab

```java Java
CustomerInfo customerInfo = Superwall.getInstance().getCustomerInfo();

for (NonSubscriptionTransaction purchase : customerInfo.getNonSubscriptions()) {
  if (purchase.isConsumable()) {
    System.out.println("Consumable purchased: " + purchase.getProductId());
  }
}
```

## Expo Event Handling

In Expo, listen for purchase events with [`useSuperwallEvents`](/docs/expo/sdk-reference/hooks/useSuperwallEvents). On Android, the `transactionComplete` event can include `transaction.purchaseToken`; after you grant the benefit, pass that token to [`Superwall.consume(purchaseToken)`](/docs/expo/sdk-reference/hooks/consume).

```tsx
import { Platform } from "react-native"
import Superwall from "expo-superwall/compat"
import { useSuperwallEvents } from "expo-superwall"

export function ConsumableEvents() {
  useSuperwallEvents({
    onSuperwallEvent: async ({ event }) => {
      if (event.event !== "transactionComplete" || Platform.OS !== "android") {
        return
      }

      if (event.product.productIdentifier !== "coins_100") {
        return
      }

      const purchaseToken = event.transaction?.purchaseToken
      if (!purchaseToken) {
        return
      }

      await grantCoins({
        count: 100,
        productId: event.product.productIdentifier,
        purchaseToken,
      })

      await Superwall.consume(purchaseToken)
    },
  })

  return null
}
```