> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tryhelium.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Helium is a paywall platform for mobile apps. Paywalls, workflows, triggers, targeting and experiments are configured in the dashboard (https://app.tryhelium.com); the SDK's job is to initialize, present a paywall for a trigger, and report purchases.
> Pick the SDK page for the user's platform: /sdk/quickstart-ios (Swift), /sdk/quickstart-android (Kotlin), /sdk/quickstart-react-native, /sdk/quickstart-flutter. Method names differ per platform; copy them from the page for that platform, never from another platform's page.
> Pages under /sdk/quickstart-ios-v3 and /sdk/quickstart-android-v0 are legacy SDK versions. Use them only when the user is on that version; for upgrades use the /migrations pages.
> For live dashboard data (paywalls, workflows, metrics) connect the Helium MCP server at https://app.tryhelium.com/api/mcp (see /ai-tools/mcp). For SQL over events, revenue, subscriptions and users use the Data Access API (/data-access/overview) and the helium-data-access skill (/data-access/agent-skill). This documentation site also exposes a docs-search MCP server at https://docs.tryhelium.com/mcp.
> Web checkout (App2Web) with Stripe or Paddle is a separate flow from in-app purchases; start at /web-checkout/overview.
> Every page is available as Markdown by appending .md to its URL. The full index is at https://docs.tryhelium.com/llms.txt.

# Web checkout (App2Web)

> Send users from an in-app paywall to a Stripe or Paddle checkout in the browser and bring them back with access unlocked. Start here for App2Web setup, testing and launch.

App2Web adds a web checkout path to a Helium paywall. The user taps a web product on your in-app paywall, Helium opens a hosted web paywall in the browser, the purchase completes with your payment provider, and the user returns to your app with the entitlement granted.

> [card] [Paddle onboarding](https://docs.tryhelium.com/guides/paddle-onboarding-guide.md)
>
> Account setup, payment link, connecting Paddle to Helium, entitlements and rollout.

> [card] [Build an App2Web paywall](https://docs.tryhelium.com/guides/build-app2web-paywall.md)
>
> Add web products and a hosted web paywall to an existing in-app paywall.

> [card] [App2Web previews](https://docs.tryhelium.com/guides/app2web-previews.md)
>
> Test the full app-to-web flow on device with simulated or real purchases.

> [card] [Go-live checklist](https://docs.tryhelium.com/guides/app2web-go-live-checklist.md)
>
> What to verify before you launch.

## How the pieces fit

1. **Payment provider**: products and prices are created in Paddle (or Stripe) and synced to Helium.
2. **Paywalls**: an in-app paywall with a purchase action on a web product, linked to a hosted web paywall built in the same editor.
3. **SDK**: the Helium SDK handles the hand-off to the browser and the return to the app. Minimum SDK versions are listed in [Paywall previews](https://docs.tryhelium.com/guides/paywall-previews.md#app2web-previews).
4. **Entitlements**: provider webhooks tell Helium (and RevenueCat, if you use it) about the purchase so access unlocks when the user returns.

Have a question that isn't covered? See the [App2Web FAQ](https://docs.tryhelium.com/guides/app2web-faq.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.