Skip to main content
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.

Paddle onboarding

Account setup, payment link, connecting Paddle to Helium, entitlements and rollout.

Build an App2Web paywall

Add web products and a hosted web paywall to an existing in-app paywall.

App2Web previews

Test the full app-to-web flow on device with simulated or real purchases.

Go-live checklist

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

Set up

Paddle Onboarding Guide

Step-by-step Paddle setup for App2Web: account, payment link, connecting Paddle to Helium, building paywalls, adding web checkout to your app, entitlements, testing and rollout.

Build an App2Web Paywall

Add web checkout to an existing in-app purchase paywall.

Test & launch

App2Web Paywall Previews

Test the full app-to-web checkout flow — simulated or real purchases — before your paywall is live.

App2Web Go-Live Checklist

A short checklist for testing your App2Web flow before launch.

Reference

App2Web FAQ

Paywalls, attribution, experiments, and entitlements with Paddle.