Skip to main content
A checklist for testing your App2Web flow before sending traffic to it. The testing tool itself — Paywall Previews — lets you run the full app-to-web checkout, including simulated or real purchases, without meeting production targeting.

​
Check the setup

  • The in-app App2Web paywall and hosted web paywall are linked and published.
  • The hosted web paywall is reached only through the in-app App2Web flow, not directly from a workflow.
  • Web products are attached correctly, and the normal IAP path remains available through continue in-app.
  • Targeting includes only eligible users and has been tested with an internal audience.
  • Checkout redirect URL, user identity, revenue tracking, and subscription management are configured.

​
Test with Paywall Previews

Open Paywall Previews (triple tap) and select your App2Web paywall.
  • Check the purchase mode in the preview settings before each session — eligible devices default to real purchases, which charge your card.
  • Run a simulated purchase and confirm no transaction or entitlement is created.
  • If the device is eligible, run a real purchase and confirm the entitlement is granted.
  • For Paddle paywalls, verify the California consent modal when it applies.
  • Clean up test purchases in your Paddle dashboard when done.

​
Test with a real trigger

Previews bypass targeting and skip paywall traits and post-purchase handlers. Before launch, run the flow through a real trigger on a physical device:
  • Open App2Web through a real trigger.
  • Tapping the web purchase CTA opens the linked hosted web paywall in the browser.
  • The product selected in the app is the product selected on the hosted web paywall.
  • Product selection and the web purchase action are separate, so the CTA cannot send the wrong product.
  • continue in-app opens the intended IAP purchase path.
  • Dismissing or abandoning web checkout returns the user to the expected place without granting access.
  • Complete a web purchase and confirm the app reopens with an active entitlement.
  • Confirm the purchase appears in Helium and your connected revenue or entitlement system.

​
Launch

  • Start with a small eligible audience and confirm the flow is healthy before expanding traffic.
  • Apple Pay readiness is on by default from the SDK versions listed in the Paddle and Stripe guides. If your audience doesn’t use the Paddle A2W Eligible or Stripe A2W Eligible preset, confirm webApplePayReadiness is arriving for your users before you add your own rule.