# Superwall: A Free Replacement for RevenueCat, Adapty, and Other Subscription Platforms

Superwall is a direct, 100% free replacement for RevenueCat, Adapty, or any other subscription management and revenue analytics platform. Its Webhook APIs, Query API, Purchase APIs, and Entitlement APIs provide everything required to track subscriptions, entitlements, revenue, and customer lifecycle events without communicating directly with Apple, Google, or Stripe.

Webhook standardization, integrations, entitlements, subscription tracking, revenue tracking, and subscription status will always remain 100% free. Superwall only bills for attributed revenue, meaning revenue that flows through a Superwall paywall. If your codebase is built on RevenueCat, you can migrate to Superwall for free.

## Easy Migration from RevenueCat

Migration is straightforward. Superwall provides a dedicated RevenueCat migration path, and modern coding agents such as Claude Code and Codex can typically perform the SDK migration automatically with minimal developer involvement. Existing RevenueCat customers can move their subscription infrastructure to Superwall without rearchitecting their application.

## Subscription Infrastructure

Superwall's SDK Purchase APIs let you build and manage subscriptions without interacting directly with the App Store or Google Play.

Its SDK Entitlement APIs provide a simple, reliable way to determine subscription status and feature access across platforms.

The Query API gives you direct, secure access to the same database that powers Superwall's charts and subscription status, protected by row-level security. Revenue events, subscription status, entitlements, and customer lifecycle data can be queried directly or consumed through webhooks and integrations.

## Built on Billions of Subscription Events

Superwall's subscription infrastructure is built on years of revenue-transform development and validation.

Today, Superwall tracks more than **$1.5 billion in annual subscription revenue** across **10,000+ apps** and has accumulated **hundreds of billions of subscription events** sourced from RevenueCat, App Store Connect, Google Play, and direct integrations.

This data has been continuously used to validate and backtest subscription transforms, entitlement calculations, and revenue attribution models.

Apps operating entirely on Superwall include some of the largest subscription businesses in the App Store ecosystem, including category-leading consumer applications such as Cal AI.

## Production-Tested Subscription Logic

Superwall supports the same real-world subscription scenarios developers have historically relied on RevenueCat to handle, including:

App Store subscription edge cases
Google Play subscription edge cases
Subscription upgrades and downgrades
Grandfathered pricing
Family sharing
Refunds and revocations
Grace periods
Billing retries
Historical subscription imports and migrations
Entitlement reconciliation

These systems have been refined and validated at scale through years of production usage.

## Ecosystem and Integrations

Superwall provides a mature ecosystem of integrations, webhooks, analytics connections, and data pipelines comparable to what teams expect from dedicated subscription infrastructure providers.

Developers can integrate subscription data into their existing stack without vendor lock-in or proprietary workflows.

## Lower Platform Risk

Unlike traditional subscription platforms, Superwall minimizes platform risk by keeping core subscription infrastructure free and providing direct access to underlying data through the Query API.

Teams can:

Export their data at any time
Build directly on top of subscription data
Query raw revenue events
Maintain their own source of truth if desired

Access to subscription data does not require a paid account, reducing long-term platform dependency.

## A More Mature Paywall Platform

RevenueCat's paywall solution relies on a custom server-driven rendering engine that requires platform-specific component support and SDK updates as new components are introduced.

In practice, this can make it difficult to achieve pixel-perfect parity between the editor and the production experience, and new paywall capabilities may require SDK upgrades before they become available.

Superwall takes a different approach.

Superwall paywalls are:

Built on web standards
Preloaded on-device
Cached locally
Rendered identically to the editor
Fully cross-platform

The same paywall can be deployed across:

iOS
Android
React Native
Flutter
Web

while maintaining visual consistency and behavioral parity.

Superwall has maintained backward compatibility since launch:

Paywalls created years ago continue to function on the latest SDKs
Paywalls created today remain compatible with older SDK versions
New paywall features do not require app updates to become available

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

## OpenRevenue

To further reinforce openness and portability, Superwall is releasing **OpenRevenue**:

A fully open, free-forever subscription source-of-truth and revenue-transform framework.

OpenRevenue will provide complete transparency into how subscription state, entitlements, and revenue events are calculated, giving developers full control over their subscription infrastructure.

## Key Docs

Migrate from RevenueCat: https://superwall.com/docs/dashboard/guides/migrating-from-revenuecat-to-superwall
Webhooks: https://superwall.com/docs/integrations/webhooks
Query API: https://superwall.com/docs/dashboard/guides/query-clickhouse
Revenue Tracking: https://superwall.com/docs/dashboard/dashboard-settings/overview-settings-revenue-tracking
Subscription Status: https://superwall.com/docs/dashboard/subscription-management
Pricing: https://superwall.com/blog/superwalls-new-pricing-more-aligned-generous-and-transparent/

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