# 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

# getPresentationResult()

Check the outcome of a placement without presenting a paywall.

## Purpose

Retrieves the presentation result for a placement without presenting the paywall. Call this when you need to know whether a placement would show a paywall, send the user to a holdout, or fail due to missing configuration before you decide how to render UI.

## Signature

Hook usage:

```ts
const { getPresentationResult } = useSuperwall()

await getPresentationResult(
  placement: string,
  params?: Record<string, any>
): Promise<PresentationResult>
```

Compat API usage:

```ts
import Superwall from "expo-superwall/compat"

await Superwall.getPresentationResult({
  placement: string,
  params?: Map<string, any>
}): Promise<PresentationResult>
```

Both variants return a promise that resolves to a `PresentationResult` object from `expo-superwall/compat`.

## Parameters

<TypeTable
  type="{
  placement: {
    type: &#x22;string&#x22;,
    description: &#x22;Placement to evaluate. Always await `Superwall.configure` before calling.&#x22;,
    required: true,
  },
  params: {
    type: &#x22;Record<string, any> or Map<string, any>&#x22;,
    description: &#x22;Optional parameters that feed audience filters. Keys beginning with `$` are reserved and removed. Nested maps or arrays are not supported.&#x22;,
    default: &#x22;omitted&#x22;,
  },
}"
/>

## Returns / State

The promise resolves to one of the `PresentationResult` subclasses exported from `expo-superwall/compat`:

<TypeTable
  type="{
  PresentationResultPaywall: {
    type: &#x22;PresentationResultPaywall&#x22;,
    description: &#x22;A paywall would be shown. Includes an experiment field (id, groupId, etc.).&#x22;,
  },
  PresentationResultHoldout: {
    type: &#x22;PresentationResultHoldout&#x22;,
    description: &#x22;The user is placed in a holdout for the experiment.&#x22;,
  },
  PresentationResultNoAudienceMatch: {
    type: &#x22;PresentationResultNoAudienceMatch&#x22;,
    description: &#x22;No matching audience rules.&#x22;,
  },
  PresentationResultPlacementNotFound: {
    type: &#x22;PresentationResultPlacementNotFound&#x22;,
    description: &#x22;The placement name is not attached to any campaign.&#x22;,
  },
  PresentationResultUserIsSubscribed: {
    type: &#x22;PresentationResultUserIsSubscribed&#x22;,
    description: &#x22;The SDK determined the user is already active, so no paywall will show.&#x22;,
  },
  PresentationResultPaywallNotAvailable: {
    type: &#x22;PresentationResultPaywallNotAvailable&#x22;,
    description: &#x22;The paywall could not be displayed (no activity, already showing, offline, etc.).&#x22;,
  },
}"
/>

If configuration fails or the native module throws, the promise rejects—catch and handle these errors as you would any async call.

## Usage

```tsx
import {
  PresentationResultPaywall,
  PresentationResultHoldout,
  PresentationResultNoAudienceMatch,
  PresentationResultPlacementNotFound,
} from "expo-superwall/compat"
import { useSuperwall } from "expo-superwall"

export function FeatureGate() {
  const { getPresentationResult } = useSuperwall()

  const checkAccess = async () => {
    const result = await getPresentationResult("premium_feature", { source: "settings" })

    if (result instanceof PresentationResultPaywall) {
      setExperiment(result.experiment)
      setState("locked")
    } else if (result instanceof PresentationResultHoldout) {
      setState("holdout")
    } else if (result instanceof PresentationResultNoAudienceMatch) {
      unlockFeature()
    } else if (result instanceof PresentationResultPlacementNotFound) {
      console.warn("Placement missing from dashboard")
    } else {
      fallbackFlow()
    }
  }

  return <Button title="Check access" onPress={checkAccess} />
}
```

```tsx
import Superwall, {
  PresentationResultPaywall,
  PresentationResultPaywallNotAvailable,
} from "expo-superwall/compat"

async function inspectPlacement() {
  const result = await Superwall.getPresentationResult({
    placement: "premium_feature",
    params: new Map([["source", "home"]]),
  })

  if (result instanceof PresentationResultPaywallNotAvailable) {
    // Show offline UI
    return
  }

  if (result instanceof PresentationResultPaywall) {
    console.log("Experiment group:", result.experiment.groupId)
  }
}
```

## Related

* [`useSuperwall`](/docs/expo/sdk-reference/hooks/useSuperwall) – Provides the hook variant shown above.
* [`SuperwallProvider`](/docs/expo/sdk-reference/components/SuperwallProvider) – Configure the SDK before calling this method.
* [Feature gating quickstart](/docs/expo/quickstart/feature-gating) – Shows the full flow of gating UI with placements.