September 21, 2026 · Muhammad Umar
Stripe Managed Payments: What It Actually Covers
- Payments & Marketplaces
Stripe's new merchant-of-record product for SaaS checkouts handles tax, fraud, and disputes — but it excludes Connect marketplaces entirely.
What Managed Payments Actually Takes Off Your Plate
Stripe shipped Managed Payments in its 2026-04-22 (dahlia) API version, adding a managed_payments.enabled parameter to Checkout Sessions and Payment Links. Turn it on and Stripe becomes the merchant of record: it handles indirect tax compliance — sales tax, VAT, and GST — in more than 80 countries, along with fraud prevention, dispute management, and transaction-level customer support. Those are four separate operational surfaces that a seller running standard Stripe Payments would otherwise own directly.
Stripe's own framing targets digital-goods sellers — “sell digital products such as SaaS, software, and digital content or downloads.” The trade is real: once enabled, Stripe automatically manages certain Connect-, tax-, and shipping-related parameters, and you can't manually override them. Customers also interact with Link, not your brand, at checkout, on receipts, and for post-purchase support, and see the purchase as “Sold through Link.”
The Exclusion That Rules Out Most Marketplaces
Before scoping Managed Payments into any architecture, check Stripe's own comparison table: Managed Payments is compatible only with Checkout and Payment Links, not Elements, the hosted invoice page, or embeddable web components. “Support for platforms” is listed as flatly unsupported, versus available with Connect for standard Stripe products.
Stripe's eligibility documentation is explicit about why: Managed Payments “supports direct integrations only.” It doesn't support Connect platforms, Express accounts, or accounts controlled by a platform. Access is further gated by a Stripe eligibility review that considers factors such as business type and geography, and the seller's business must be based in a supported location.
That single exclusion is the scoping decision. A two-sided marketplace or platform business model — where payments route through Connect on behalf of other sellers — can't use Managed Payments, full stop. It's a fundamentally different product from a Connect-based marketplace payment architecture, where the platform itself remains responsible for tax and dispute handling, not Stripe.
What to Check Before Proposing It
For a straightforward direct-to-customer SaaS or digital-content checkout, Managed Payments removes real engineering and compliance surface area: tax registration and remittance across dozens of jurisdictions, fraud rule tuning, and first-line dispute response all shift to Stripe. Scope the decision around three questions before committing engineering time: Is this a direct integration, or does it route through Connect for a platform or marketplace model? Does the checkout need Elements or another integration beyond Checkout and Payment Links? And is the seller prepared to hand checkout-page and post-purchase branding to Link — Managed Payments checkouts don't support custom domains, and customers manage orders through Link's own tools, not yours. Get those three answers before the eligibility review, not after.