When a software-as-a-service (SaaS) company sells a subscription to a customer in Germany, someone has to collect German value-added tax (VAT), remit it to the right authority, handle any disputes, and assume liability if something goes wrong. The merchant of record (MoR) is the legal seller that owns those responsibilities. This is either your business or a provider you’ve designated to act in your place.

Below, we cover what the merchant of record for SaaS businesses is, how the global compliance burden is divided by market, and how to evaluate the trade-offs before committing.

Key takeaways

• The merchant of record is the legal seller on the transactions it covers. It takes on indirect-tax compliance, fraud and chargeback liability, and dispute management.

• Some MoR arrangements support transaction-level coverage, which lets SaaS businesses route specific geographies or customer segments through them rather than switching their full payment stack.

• The compliance burden of selling SaaS internationally grows with every new market you enter. An MoR arrangement shifts a big portion of that work to the provider.

What is a merchant of record for SaaS?

A merchant of record for SaaS is the legal entity that sells your software and assumes legal liability for the transactions.

In a standard payment flow, you’re the seller of record on every transaction. You collect revenue, pay a payment provider to process it, and own every legal responsibility that comes with being the seller, including tax, disputes, and fraud liability.

Under a merchant of record model, the MoR provider becomes the legal seller on each transaction. Customers are technically purchasing from the MoR, which collects gross revenue from the customer and pays out the net amount to you after retaining its fees and the applicable tax. The MoR handles tax registration, calculation, and remittance in the markets it supports.

Here’s what an MoR handles on your behalf:

• Tax calculation: This happens in real time based on the customer’s location, product type, and applicable rates.

• Tax remittance: The MoR collects, holds, and pays tax to the relevant authority on your behalf.

• Dispute management: This is handled from beginning to end, including response documentation and timeline management that chargebacks require.

• Post-purchase support: Billing-related issues route through the outside MoR rather than your support queue.

Some MoR arrangements apply across your entire payment infrastructure, while others are more flexible and allow you to assign only certain transactions. Stripe Managed Payments lets you designate specific transaction types, geographies, or customer segments as MoR-eligible rather than forcing an all-or-nothing switch.

Why do SaaS companies use a merchant of record?

Some SaaS teams aren’t equipped to manage the compliance obligations involved in global selling. That’s where a merchant of record comes in.

Early-stage SaaS teams typically use an MoR if they don’t have enough resources to manage tax registration, VAT filings, and chargebacks across jurisdictions. These processes require documentation, response timelines, and institutional knowledge that small teams typically lack.

Growth-stage teams often use an MoR when they hit an inflection point expanding into new regions and realise that their existing setup doesn’t grow. For example, selling into the EU requires either registering for VAT in each member state or using the EU’s One Stop Shop (OSS) scheme, both of which demand ongoing administration.

Larger SaaS businesses sometimes use an MoR selectively to cover long-tail markets where the compliance cost can outweigh the revenue. They maintain their own infrastructure in regions where they already have scale.

What global compliance challenges does a merchant of record solve for SaaS?

Selling SaaS internationally without an MoR means running your own tax compliance operation in every market that taxes digital services. This can become complicated quickly, because digital services taxes apply differently across jurisdictions, and the rules are specific.

For example:

• In the EU, B2C SaaS sales charge VAT based on the customer’s location. For instance, if you sell to a customer in France, you owe French VAT. B2B SaaS sales use the reverse charge mechanism, meaning the buyer has to account for VAT in their home country. Each EU country has its own rate, though you can use OSS to reduce some of the filing burden.

• Canada has goods and services tax (GST) and harmonised sales tax (HST) with province-level variations.

• Japan, South Korea, and Singapore each have separate digital goods tax regimes.

• In the US, each state levies sales tax on digital services differently.

Penalties for non-compliance range from interest on unpaid tax to formal audits. Being unregistered in a market you’re actively selling into creates a liability that compounds with every transaction. And rules change frequently, so staying current requires monitoring regulatory changes across every market.

An MoR can take over many of these compliance obligations. They handle tax registration, collection, and filing and stay up-to-date with changing rules to ensure ongoing compliance. When a country updates its digital services tax threshold, the MoR is responsible for keeping track—not you.

How do you implement a merchant of record for your SaaS product?

With Stripe Managed Payments, implementation is designed to require minimal changes to an existing integration. If you’re already using Stripe Checkout or Stripe Billing, the engineering lift is small.

Since Stripe Managed Payments works on a transaction-level model, you’ll first designate which transactions or geographies should route through Managed Payments. Tax will be automatically calculated for those transactions going forward. Stripe will appear as the seller of record on those transactions, which is what triggers the liability transfer.

Your existing Stripe integration architecture, how you handle subscription lifecycle events, webhooks, and revenue reporting in your own systems, and your customer-facing product and pricing pages all stay the same.

What are the trade-offs of using a merchant of record for SaaS?

The MoR model comes with trade-offs. Consider the following before committing to an arrangement:

• Revenue recognition: Revenue treatment depends on principal-versus-agent analysis under ASC 606 and IFRS 15, two accounting standards, and might differ from your current setup. This affects how SaaS revenue is reported and how it looks to investors or acquirers. Confirm the treatment with your accounting team before you commit.

• Tax classification decisions: When you’re the MoR, your team takes the position on how your product is classified for tax purposes (subject to local authority review). When an MoR provider handles this, those positions are theirs. If your SaaS product has unusual pricing structures or bundled services, you’ll want to understand exactly how classification calls are made.

• Customer-facing seller identity: In markets where the MoR appears on receipts and billing correspondence, some customers will notice. B2C SaaS businesses rarely encounter this, but enterprise SaaS sellers occasionally face this question from procurement teams that scrutinise vendor relationships.

• Platform dependency: Routing transactions through an MoR creates a dependency on that provider’s infrastructure, compliance practices, dispute policies, and financial stability. If any of those change, your business can be affected. Read the contract carefully and understand what happens in edge cases before you have to deal with one.

How Stripe Payments can help

Stripe Payments provides a unified, global payments solution that helps any business – from scaling startups to global enterprises – accept payments online, in person and around the world.

Stripe Payments can help you:

• Optimise your checkout experience: Create a frictionless customer experience and save thousands of engineering hours with prebuilt payment UIs, access to 125+ payment methods and Link, a wallet built by Stripe.

• Expand to new markets faster: Reach customers worldwide and reduce the complexity and cost of multicurrency management with cross-border payment options, available in 195 countries across 135+ currencies.

• Unify payments in person and online: Build a unified commerce experience across online and in-person channels to personalise interactions, reward loyalty and grow revenue.

• Improve payments performance: Increase revenue with a range of customisable, easy-to-configure payment tools, including no-code fraud protection and advanced capabilities to improve authorisation rates.

• Move faster with a flexible, reliable platform for growth: Build on a platform designed to scale with you, with 99.999% historical uptime and industry-leading reliability.

Learn more about how Stripe Payments can power your online and in-person payments or get started today.