Monetization
Managed Payments
Turn on Stripe Managed Payments for your web checkout: Stripe becomes the merchant of record — tax in 80+ countries, fraud, chargebacks, and buyer support handled — while your paywalls, campaigns, and redemption flow stay the same.
What it does
-
Stripe becomes the merchant of record. Eligible checkout sessions run with Stripe Managed Payments and are sold through Link, Stripe's consumer brand — Stripe is the legal seller on those transactions, not you.
-
Tax handled in 80+ countries. Sales tax, VAT, and GST are calculated from product classification and buyer location, then filed and remitted by Stripe — no registrations, no remittance calendar.
-
Fraud and disputes are Stripe's queue. Fraud prevention runs automatically, and Stripe manages chargebacks — including submitting dispute evidence on your behalf.
-
Buyers get transaction-level support. Receipts, payment questions, and subscription management go through Link — while you keep issuing refunds and updating subscriptions from your own dashboard and API.
-
Your funnel doesn't change. Products, paywalls, campaigns, placement URLs, redemption links, and membership management all keep working — Managed Payments changes who owns the payment, not how your funnel runs.
-
Roll it out on your terms. iOS and Android paywalls with Stripe products can follow the account default, force Managed Payments, or force the standard Stripe flow — and analytics events record which mode each transaction ran, so managed vs standard is a breakdown, not a guess.
How it works
Complete the standard web checkout setup first: create a Web Checkout app, connect Stripe with the official Superwall Stripe app and keys, and add the Stripe products you want to sell — each with the correct product tax code in Stripe.
Then open Settings ▸ Stripe Configuration in your Web Checkout app and turn on the Managed Payments switch. Superwall checks whether your connected Stripe account and each active product can use Managed Payments; if Stripe requires it, you accept the Stripe Connect terms and flip the switch again. If any product is ineligible, Stripe's reason is listed so you can fix it and recheck — usually a product tax code.
Read the Managed Payments guideAt checkout, Superwall resolves the paywall-level override first and falls back to the app-wide default. If the resolved setting is Managed Payments, the Stripe Checkout session is created with it enabled and Stripe is the seller of record for that purchase. Live and sandbox Stripe environments validate separately, so verify your live configuration before launch even if you first tested the switch in sandbox.
Roll it out gradually
You don't have to move every payment at once. Leave the account default off and force Managed Payments on a single paywall to pilot it, or turn the default on and exclude the paywalls you're not ready to migrate. Because the mode is recorded on every transaction event, you can compare managed and standard payments side by side before committing the rest of your traffic. The pilot playbook walks through that rollout step by step, and the merchant-of-record playbook covers why teams hand the seller role to Stripe in the first place.
Get started
Read the Web Checkout overview if you're new to selling on the web with Superwall, then follow the Managed Payments guide to enable it — or create a Superwall account and set up web checkout first.
Read the Web Checkout overview