Monetization
Teleport Checkout
Send iOS users from your paywall to a checkout page you design, take payment in the browser with Apple Pay or a card, and bring them back to the app unlocked.
Web checkout on iOS usually means a hand-off to someone else's page. The user taps buy, waits on a spinner, and lands on a generic checkout that looks nothing like the paywall that sold them. Then iOS asks whether to open your app, and the paywall that started it all just closes. Every one of those seams is a place a purchase can leak out. Teleport keeps the whole trip inside one design you control.
A checkout page that still looks like your paywall
In the paywall editor, add a page to a multi-page paywall and mark it as the Checkout Page. Design it like any other page, with a button that buys a Stripe product. Route buttons on your in-app pages to it, and those connections show on the canvas as Opens in Browser. When a user taps one, the checkout page opens in their default browser on your web paywall domain, with the product they tapped already selected.
Set up a checkout pageWhat changes compared with a generic web checkout
-
It opens without a wait. Superwall prepares the checkout page in the background while the paywall is open, so it usually loads right away instead of spinning while a session is created.
-
Apple Pay or a card. Choose Apple Pay (the default, with a card payment sheet wherever the browser can't show it) or the payment sheet alone.
-
No "Open in App?" prompt on the way back. Add
applinks:<subdomain>.superwall.linkto your associated domains and Return to App opens your app directly. -
Your after-purchase actions still run. When the user comes back, the paywall runs the purchase button's after-purchase actions just like an App Store purchase: thank-you pages, state changes, and closing all work.
-
The sale stays attributed. User attributes, placement parameters, form input, and free trial eligibility carry over to the checkout page, along with the paywall, experiment, and variant that started it.
While the user is in the browser
Your paywall doesn't sit there frozen. It shows a waiting screen with Complete in Browser, which reopens the checkout page, and Cancel, which runs the purchase button's On Abandon actions. The paywall also checks the checkout's status, so a user who pays and switches back to your app on their own gets access without tapping anything.
See the waiting screenMeasure it like any other paywall
Teleport adds two events: teleport_open when the paywall
opens its checkout page, and teleport_return when a return
link brings the user back, with a reason of purchased or closed. Purchases also report transaction_start and transaction_complete with the paywall, experiment, and
variant that started the checkout. So you can test the checkout page
itself, not just the paywall in front of it.
Who it's for
-
Apps already selling on the web through App-to-Web Checkout who want the browser step to look and behave like their paywall.
-
Growth designers who want to design and test the checkout page the same way they design and test the paywall.
-
Growth teams chasing purchases that drop off between the tap and the payment.
Get started
Teleport needs the Superwall iOS SDK 4.18.0 or later and is turned on per app. The checkout page options appear once a paywall has a Stripe product. On Android, and on older iOS SDK versions, buying a Stripe product opens Stripe Checkout instead. Teleport links users out of your app to buy, so show it to the same United States storefront audience you use for App-to-Web. Read the October update for the launch notes.
Read the Teleport checkout guide