Stripe Managed Payments: Stripe as Merchant of Record, Explained

For years the answer to “is Stripe a merchant of record?” was no, and the follow-up was a list: Paddle, Lemon Squeezy, Polar, Dodo Payments. That answer is now out of date. Stripe Managed Payments became generally available on 22 April 2026 to businesses in 39 countries, and in that mode Stripe — not your company — is the merchant of record for the sale.

If you have been choosing between “Stripe plus your own tax compliance” and “an MoR that owns the liability”, there is a third option now, and it comes from the incumbent. This is what it actually is, how you switch it on, and — the part the documentation spreads across several pages — everything it stops accepting once you do.

The short version:

• Managed Payments makes Stripe the merchant of record: it takes on sales tax, VAT, and GST liability, fraud, disputes, and buyer support.
• It is not a new API. Same api.stripe.com/v1, same secret key, same objects, no new webhook events.
• The entire opt-in is one parameter: managed_payments[enabled]=true on a Checkout Session or Payment Link, on API version 2025-03-31.basil or later.
• It rejects roughly twenty parameters rather than ignoring them — tax, payment-method, shipping, Connect, and post-sale fields all become unavailable.
• Access is gated by an eligibility review: digital products only, no Stripe Connect, no marketplaces, no embedded custom payment UI.
• Subscriptions can only be created through Checkout or Payment Links, and existing subscriptions cannot be moved into it.

Is Stripe a merchant of record now?

Yes, in Managed Payments mode — and only in that mode. Standard Stripe is unchanged: you remain the seller of record, you own the tax registrations, and you file the returns. When you enable Managed Payments on a checkout, Stripe becomes the legal seller for that transaction and takes on indirect tax compliance across more than 80 tax jurisdictions, along with fraud prevention, dispute handling, and transaction-level customer support.

This is the same trade every merchant of record offers: you give up the direct customer relationship on the receipt and a slice of revenue, and you stop having to register for VAT in a dozen countries. What is new is that you no longer have to leave Stripe to make it.

What does Managed Payments actually change?

Legally quite a lot, technically almost nothing — which is the surprising part. There is no separate API, no new base URL, no new credential, and no new set of objects to learn. You keep calling POST /v1/checkout/sessions with the same secret key, and Products, Prices, Customers, Subscriptions, and Invoices remain the ordinary objects you already use.

What changes is the shape of what Stripe will accept on the way in, and who appears on the paperwork on the way out. Concretely:

• Checkout and Payment Links only. Elements, embedded web components, and custom payment flows are unsupported.
• Stripe issues the invoices, as merchant of record, rather than you asking Checkout to create one.
• Stripe Tax is the only compatible tax solution, and third-party tax integrations are out.
• Stripe Connect, marketplaces, and platform-controlled accounts are unsupported outright.

How do you turn Managed Payments on?

You enable it once on the account, then per checkout with a single boolean. After Stripe approves your account, add managed_payments[enabled] to the session you already create:

curl https://api.stripe.com/v1/checkout/sessions \
  -u "$STRIPE_SECRET_KEY:" \
  -H "Stripe-Version: 2025-03-31.basil" \
  -d "mode=subscription" \
  -d "line_items[0][price]=price_123" \
  -d "line_items[0][quantity]=1" \
  -d "managed_payments[enabled]=true" \
  --data-urlencode "success_url=https://example.com/thanks"

The API version floor matters: Stripe documents 2025-03-31.basil or later, and older pinned versions will not recognize the parameter. The same flag works on Payment Links, where it is immutable after creation — you cannot enable or disable Managed Payments on an existing link, only create a new one.

If you use revenue-sdk, it is a factory option and every downstream call is unchanged:

import { createClient } from 'revenue-sdk';
import { stripe } from 'revenue-sdk/stripe';

const client = createClient({
  provider: stripe({
    secretKey: process.env.STRIPE_SECRET_KEY!,
    managedPayments: true,
  }),
});

const checkout = await client.checkouts.create({
  items: [{ product: 'price_123' }],
  customerEmail: '[email protected]',
  successUrl: 'https://example.com/thanks',
});

Which parameters does Managed Payments reject?

These parameters must be removed from the session — Stripe rejects them rather than ignoring them, so a checkout that worked yesterday fails outright the moment you set the flag. The lists differ slightly between subscriptions and one-time payments:

Three of these are worth calling out because they change behavior you may be relying on:

• adaptive_pricing is not configurable. You cannot turn it off, so the currency your buyer is charged in may differ from the currency on your Price. Any reporting that assumes those match needs revisiting.
• invoice_creation is gone on both modes. If you were setting it to make one-off purchases show up as invoices, stop — Stripe now draws up the invoice itself as merchant of record. This one bit us directly: revenue-sdk sends invoice_creation[enabled] on one-time sessions so that purchases reach orders.list, and adding Managed Payments meant gating that off.
• payment_intent_data.statement_descriptor is gone. The descriptor is Stripe’s to set now, because Stripe is the seller.

Can you migrate existing subscriptions to Managed Payments?

No. Only subscriptions created through a Managed Payments Checkout Session or Payment Link are covered, and there is no path to move an existing subscription into the programme. Subscriptions also cannot be created by calling POST /v1/subscriptions directly under Managed Payments — Checkout and Payment Links are the only entry points.

Practically, that means adopting Managed Payments on an established product is a forward-looking change: new customers land in the MoR flow, existing ones keep billing the way they always did, and you run both models side by side for as long as those subscriptions live. Budget for the reporting split.

How does Managed Payments compare to Paddle, Lemon Squeezy, Polar, and Dodo?

All five make someone else the merchant of record; they differ in what you can sell, where the checkout lives, and how much API you have to learn. The honest summary:

¹ Paddle runs a separate, gated partner programme where each sub-merchant becomes its own KYC’d Paddle seller. It is not Stripe Connect — no split payouts or application fees are documented — and it is absent from the public API reference.

Two rows carry the decision. “New API to learn” is why Managed Payments is compelling if you are already on Stripe: it is the only option here that does not ask you to integrate a second API, re-model your catalog, or re-learn a webhook signature scheme. The trade is that you give up Elements, Connect, and the checkout parameters listed above.

“Bring existing subscriptions in” cuts the other way, and it surprised us. Paddle, Lemon Squeezy, and Dodo all run assisted migrations that move live subscriptions — the card data goes vault-to-vault from your old processor, so customers never re-enter payment details. Stripe’s own MoR mode is the one option on this list that cannot take your existing subscribers. If you are adopting it on an established product, new customers go through Managed Payments and everyone already subscribed stays where they are, indefinitely.

One thing worth knowing about Lemon Squeezy

Lemon Squeezy is owned by Stripe, and in January 2026 its co-founder wrote that the team is building Stripe Managed Payments, with the stated goal of giving “Lemon Squeezy users an easy way to migrate to Stripe Managed Payments” — acknowledging “slower support responses and less frequent product updates” in the meantime.

Read that as maintained rather than actively developed: signups are still open, there is no announced sunset, and the API changelog was still moving in mid-2026. But if you are weighing Lemon Squeezy against Managed Payments as independent options, they are not independent — one team builds both, and only one of them is where the investment is going.

For what the underlying APIs look like side by side, see how the five billing APIs differ.

Should you use Managed Payments?

Use it if you sell digital products, you are already on Stripe, and tax compliance is the reason you were eyeing an MoR in the first place. It removes the strongest argument for leaving Stripe, and it costs you one boolean rather than a migration.

Do not use it if you need Connect, a marketplace model, Elements or a custom payment surface, physical goods, or B2B services — all are outside the eligibility rules, and no amount of integration work gets around them. And if you already run a mature Paddle or Lemon Squeezy integration that works, “Stripe does this now” is not on its own a reason to move; the subscriptions you have cannot come with you anyway.

Frequently asked questions

Is Stripe Managed Payments the same as Stripe Billing?

No. Stripe Billing is the subscription engine and is unchanged — the same Subscription and Invoice objects, whichever mode you are in. Managed Payments is a legal and compliance layer on top that changes who the merchant of record is. Subscriptions under Managed Payments still run on Billing.

Does Managed Payments need a different API key or SDK?

No. It uses your normal secret key and the standard Stripe API at api.stripe.com/v1. The only requirements are an account Stripe has approved for the programme, API version 2025-03-31.basil or later, and the managed_payments[enabled] parameter on the session.

Are there new webhook events for Managed Payments?

No new event types are documented. You keep handling the standard ones — checkout.session.completed, invoice.paid, customer.subscription.updated — and signature verification is unchanged. The managed_payments.enabled field appears on the Checkout Session, PaymentIntent, and Subscription objects, so you can tell which mode a record was created under.

Can I use Managed Payments for one-time payments?

Yes. Stripe added one-time payment support in September 2025, so both mode=payment and mode=subscription sessions work. Note that invoice_creation is rejected in both modes — Stripe generates the invoice itself.

Who is eligible for Stripe Managed Payments?

Access is granted after an eligibility review. Broadly: digital products only (SaaS, software, digital content, downloads), a business located in one of the supported countries, no Stripe Connect or marketplace model, and an eligible tax code on every product. Physical goods, B2B services, and anything requiring human delivery are excluded.

Is Lemon Squeezy being replaced by Stripe Managed Payments?

Not officially, but the direction is public. Lemon Squeezy is owned by Stripe, and in January 2026 its co-founder wrote that the team is building Stripe Managed Payments and wants to give Lemon Squeezy users “an easy way to migrate” to it. There is no announced sunset date and signups remain open, but Managed Payments is where that team’s effort is going.

Does revenue-sdk support Stripe Managed Payments?

Yes. Pass managedPayments: true to the stripe() factory and every client call keeps its shape; the SDK sends the flag and omits the parameters Managed Payments rejects. See the Stripe provider page for the option and its limitations.

Keep reading

• Stripe vs Polar vs Lemon Squeezy vs Paddle vs Dodo: How Their Billing APIs Differ — the field guide to all five APIs.
• Stripe SDK Alternatives for Multi-Provider Billing — when one SDK stops being enough.
• How to Normalize Subscription Status Across Billing Providers — one entitlement check for five providers.
• Capability matrix — what each provider supports, as data.