Stripe Managed Payments vs Merchant of Record: what changes for your finance team

Stripe launched Managed Payments in April 2025, built from its Lemon Squeezy acquisition. The product makes Stripe the merchant of record on transactions you select, handling tax, fraud and disputes.

For engineering, it changes almost nothing. For finance, it changes four things. So what should your finance team actually prepare for?

Start with the cost, because it is where most evaluations stop too early.

Managed Payments adds 3.5% per successful transaction on top of standard Stripe processing. At 2.9% + $0.30 base, your floor is 6.4% + $0.30.

That floor rises with each layer. Stripe Billing for recurring revenue adds roughly 0.7%. International cards add around 1.5%. Currency conversion adds about 1%.

A SaaS business selling internationally on subscriptions lands near 9.6% + $0.30 effective.

Three further changes land on finance rather than on engineering.

Revenue recognition shifts. When Stripe becomes the legal seller, you are no longer selling to your end customer. Your revenue arrives from Stripe, net of their fees, which changes how you book gross versus net.

Tax obligations disappear selectively. Managed Payments can apply per market, per product or per transaction, which means your finance team manages a split estate where some sales carry VAT obligations and others do not.

Reconciliation gets more complex, not less, because two settlement models now coexist in one account.

That selective coverage is Stripe’s genuine innovation and its hidden cost. An all-in Merchant of Record removes the split entirely.

At InflowPay, the rate is 4% + $0.35 all-in, with no stacked surcharges and four-day settlement.

In this article we break down what changes, line by line.

What Stripe Managed Payments Actually Does?

Managed Payments makes Stripe the merchant of record on transactions you designate, through its Link consumer network.

That legal transfer moves four responsibilities off your side.

Indirect tax. Stripe calculates, collects, files and remits sales tax, VAT and GST across more than 80 countries on covered transactions. Registrations in those jurisdictions become its obligation rather than yours.

Fraud prevention. Screening and authentication run on Stripe’s infrastructure, with its own risk models applied.

Dispute handling. Stripe responds to chargebacks directly rather than passing them to you for representment.

Transaction-level customer support. Buyers manage purchases, update payment methods and raise issues through Link, which removes a category of support tickets from your team.

Two characteristics distinguish it from the rest of the category.

Coverage is selective

This is the genuine innovation. You apply Managed Payments per market, per product or per transaction rather than across your entire business.

A company might use it for European sales where VAT complexity is highest, while remaining merchant of record domestically. That flexibility has no equivalent among standalone MoR providers.

It sits inside your existing Stripe setup

For teams already on Stripe, there is no migration. Managed Payments works alongside Stripe Billing for recurring revenue and Stripe Sigma for analysis, and the dashboard stays the same.

Two limits apply to eligibility.

The product covers digital goods: SaaS, software, digital content and downloads. Physical goods sit outside its scope.

Availability has expanded since launch but coverage is not universal, which means your markets and your product category both need checking rather than assuming.

The Real Cost: What Your Finance Team Will Actually Pay

The published figure is 3.5% added to standard Stripe processing. That number is accurate and incomplete, because it describes one layer in a stack.

Start with the floor. Stripe processing runs 2.9% + $0.30, and Managed Payments adds 3.5% on covered transactions. A domestic one-time purchase therefore costs 6.4% + $0.30.

That is the cheapest case, and most businesses do not have it.

Stripe Billing adds roughly 0.5% to 0.8% on recurring revenue. A domestic subscription business lands around 7.1%.

International cards add approximately 1.5%. Selling across borders brings you to roughly 8.6%.

Currency conversion adds about 1% where your settlement currency differs from the transaction currency, which is the normal case for international sales. That takes you to roughly 9.6% + $0.30.

A SaaS business selling subscriptions internationally, which describes most companies evaluating this product, pays close to ten percent of gross revenue.

Why the comparison usually gets made wrong?

Finance teams evaluating this typically compare 3.5% against a standalone provider’s full rate, and the comparison is not valid.

The 3.5% is a surcharge, not a price. It sits on top of processing you were already paying, plus every other layer your business configuration requires.

A standalone Merchant of Record charging 4% all-in is not more expensive than 3.5%. It is less expensive than 6.4%, and considerably less than 9.6%.

The number to model is your effective blended rate across your actual transaction mix, not the headline surcharge.

Run that calculation on last quarter’s volume before deciding. Most teams find the gap wider than they expected.

What Changes in Your Accounting and Reconciliation?

Four things shift the moment Stripe becomes the legal seller on part of your volume.

• Revenue recognition moves from gross customer sales to a net relationship with Stripe
• Your counterparty changes, since you now sell to Stripe rather than to end customers
• Tax filings disappear selectively, for covered transactions only
• Two settlement models coexist inside the same Stripe account
• Your VAT estate becomes split, with obligations remaining on uncovered sales
• Dispute accounting changes, since Stripe handles representment directly
• Customer records fragment, with Link holding part of the relationship

Among these, the split estate creates the most work, and it is the direct consequence of Stripe’s selective coverage.

Applying Managed Payments to European sales while remaining merchant of record domestically means your finance team maintains two regimes simultaneously. Some transactions carry VAT obligations, others do not. Some reconcile against customer payments, others against Stripe settlements.

That duality is manageable. It is also the opposite of the simplification most teams expect when adopting a Merchant of Record.

Revenue recognition deserves early attention from your accountant. When Stripe is the legal seller, your arrangement with them determines whether you book gross revenue with a cost of sale, or net revenue only.

The treatment affects your reported top line materially, which matters for investor reporting, covenant calculations and valuation multiples. Resolve it before implementation rather than at year end.

Reconciliation complexity rises rather than falls in the first months, because your team learns two flows instead of replacing one.

An all-in Merchant of Record avoids this entirely by applying one model across all transactions.

When Stripe Managed Payments Is the Right Choice?

Four situations make it the better option, and they are specific enough to self-select against.

You are already deeply integrated with Stripe. If your billing, analytics and internal tooling sit on Stripe Billing and Sigma, Managed Payments requires no migration. That saved engineering work has real value, and it is the strongest argument for the product.

You need coverage in specific markets only. Selective application is genuinely useful here. A company facing VAT complexity in Europe while trading comfortably at home can apply it where the burden exists and nowhere else.

No standalone Merchant of Record offers that granularity.

Your volume skews domestic. At the 6.4% floor without international uplifts or conversion layers, the economics are considerably better than the headline stack suggests.

You want optionality. Stripe positions Managed Payments as reversible: you can move transactions back under your own merchant of record status as you grow. For a company expecting to build its own tax function eventually, that path matters.

Three situations argue against it.

You sell internationally on subscriptions. This is the profile where the stack compounds hardest, landing near 9.6%. An all-in provider at 4% is a materially different cost structure.

You sell physical goods. Managed Payments covers digital products only.

You want one model, not two. Selective coverage means your finance team maintains a split estate: two settlement flows, two tax regimes, two reconciliation paths. That complexity is the cost of the flexibility.

The honest framing: Managed Payments is a strong product for Stripe-native companies with concentrated needs. It is an expensive one for international subscription businesses.