Merchant of Record: Pros, Cons & When to Use One for SaaS

A merchant of record (MoR) is a third party that takes on legal responsibility for your sales — handling taxes, invoicing, compliance, and chargebacks so you don't have to. For SaaS companies selling globally, it's an appealing shortcut to tax compliance from day one.

But the merchant of record pros and cons aren't always obvious upfront. The fees compound as you grow, and you give up more control than most founders expect. This guide breaks down exactly what you get and what you give up, compares the main MoR platforms for SaaS, and helps you decide whether it's the right call for where your business is right now.

What is a merchant of record?

A merchant of record is a company that acts as the legal seller in a transaction. When you use an MoR, your customers are technically buying from the MoR — not from you. The MoR appears on their bank statement, collects payment, calculates and remits taxes, and handles any disputes or refunds. You remain the product creator and service provider; the MoR handles the commercial and compliance layer in between.

This is different from a payment processor like Stripe or PayPal. A payment processor handles the technical transfer of funds — but you remain the legal seller and are responsible for your own tax obligations. An MoR goes further: it becomes the seller of record, fully absorbing tax registration, calculation, filing, and dispute liability across every country it supports. The trade-off for that convenience is a cut of every transaction and reduced control over the customer relationship.

How a merchant of record works

When a customer buys from you through an MoR, the flow works like this:

1. The customer reaches your checkout, which is hosted or powered by the MoR
2. The MoR collects payment, applying the correct tax rate for the customer's location
3. The MoR generates a compliant invoice or receipt on their own behalf (as the legal seller)
4. The MoR remits the collected tax to the relevant authority — you never touch it
5. The MoR pays you the net amount after their fee and any payment processing costs

Because the MoR is the legal seller, it also owns the compliance risk. If a tax authority has questions about a transaction, they go to the MoR. If a customer disputes a charge, the MoR handles it. You are shielded from direct liability for those transactions — but you are also one step removed from your own customers.

Pros of using an MoR for SaaS

Tax compliance is handled entirely

The biggest draw for SaaS companies is complete tax abstraction. VAT in the EU, GST in Australia and Canada, sales tax across US states — the MoR registers where required, charges the right rate, and remits to the tax authority. You don't need to track registration thresholds, stay current on rate changes, or file returns in dozens of jurisdictions. For early-stage companies with no tax expertise in-house, this can remove a significant compliance burden.

Global reach from day one

MoRs are already registered to collect and remit taxes in the countries they support. That means you can sell to customers in 100+ countries on launch day without any additional setup — no waiting for VAT registrations to be approved, no engaging local advisers, no registering in each new market before you make your first sale.

Fraud and chargeback protection

MoRs take responsibility for payment fraud and chargeback disputes. They have fraud detection built in and handle disputes directly with card networks. If a fraudulent transaction slips through, the loss is typically absorbed by the MoR, not you.

Compliant invoicing across markets

The MoR generates legally compliant invoices and receipts for every transaction, in the correct format for the customer's jurisdiction. This includes VAT invoices for EU B2B customers and the specific invoice fields required by local tax laws — which can be complex to get right on your own.

Cons of using an MoR for SaaS

Cost compounds as you scale

MoR platforms typically charge 3–6% of each transaction, on top of standard payment processing fees (usually 1.5–3% plus a fixed amount per transaction). At early stage, that's a reasonable price for eliminating compliance overhead. But the math shifts fast. On $500,000 ARR, MoR fees alone can run $15,000–$30,000 per year. On $2M ARR, that's $60,000–$120,000 — enough to hire a finance person who could manage compliance directly, or to cover a tax tool and still come out ahead.

You lose control of the checkout

When you use an MoR, your checkout is the MoR's checkout. You have limited ability to customize the payment experience, offer your own payment methods, or run conversion experiments. If the MoR's checkout doesn't support a payment method popular in a specific region — or simply converts worse than a custom-built flow would — you absorb that impact.

Customer data stays with the MoR

The MoR processes your customers' payment and billing data, which means it sits with them, not you. If you later want to switch MoRs, migrate to direct billing, or use billing data for analytics and dunning workflows, you may face significant data portability constraints. This is a bigger issue than it sounds for businesses that eventually want to own their customer relationships fully.

Pricing flexibility is limited

MoRs work best with standard, predictable billing models. Custom enterprise pricing, usage-based billing, metered models, free trials with complex terms, or heavy proration logic can be difficult or impossible to implement within an MoR's billing engine. As your pricing evolves beyond simple monthly or annual tiers, the MoR can become a constraint rather than a convenience.

Popular MoR platforms for SaaS

Platform	Best for	Fee	Key trade-off
Paddle	B2B SaaS, mid-market	~5% + payment processing	Strong B2B invoicing and VAT handling; checkout customization is limited
FastSpring	Software and digital downloads	~5.9% + payment processing	Established platform with broad country coverage; older UI
Lemon Squeezy	Indie developers and small SaaS	5% + $0.50 per transaction	Simple, fast setup; less suited to high volumes or complex billing

Each differs in supported countries, checkout flexibility, and the depth of their billing engine. Paddle is the most commonly used by B2B SaaS companies with international customers; Lemon Squeezy is popular with solo founders and indie developers launching quickly.

The decision framework: MoR vs. handling taxes yourself

Ask yourself these five questions before committing to an MoR:

1. Do you have tax expertise in-house? If you're early stage with no finance team, an MoR removes real compliance risk. If you have a finance function that can set up and manage tax automation software, you may not need it.

2. What does the fee cost over two years, not just now? Model MoR fees at your projected ARR in 12 and 24 months. The number that looks small today can become the single largest line item in your operating costs.

3. How important is checkout control? If conversion optimization is a priority — custom payment methods, branded experience, A/B testing — a standardized MoR checkout will work against you.

4. How complex is your pricing? Simple monthly and annual tiers work well with MoRs. Usage-based, metered, or custom enterprise pricing models often don't.

5. Will you need to own your billing data later? If you anticipate migrating to direct billing, building dunning workflows, or using payment data for analytics, consider how difficult it will be to extract that data from the MoR.

When an MoR makes sense

• You're launching globally from day one with no finance team and want zero compliance setup
• Your pricing is simple — fixed monthly or annual plans with no custom negotiation
• You're selling to consumers or small businesses where checkout branding is less critical
• Your transaction volume is low enough that the percentage fee doesn't materially affect margins
• You want to test international markets quickly before committing to a full compliance stack

When it doesn't make sense (and what to use instead)

• You're past $300–500k ARR and the MoR fee is becoming a significant cost line
• Your checkout conversion matters, and you need control over the payment experience
• You're selling to enterprise customers who pay via invoice or bank transfer, not a hosted checkout
• Your billing model is usage-based, custom, or complex in ways an MoR can't accommodate
• You want to own your customers' payment and billing data

In these cases, a direct payment processor (Stripe, Braintree) combined with a dedicated tax compliance tool is typically the better path. You keep full control of checkout, pricing, and customer data — and you automate the compliance parts separately.

Quaderno handles the tax layer that an MoR would otherwise cover: calculating the correct VAT, GST, or sales tax rate on every transaction, generating compliant invoices localized to language and currency, monitoring registration thresholds across jurisdictions, and producing filing-ready tax reports. You keep everything else — your checkout, your pricing model, your customer relationships — without the per-transaction fee.

If you'd rather keep full control of your checkout and customer data, see how Quaderno compares to an MoR.

Frequently asked questions

What is a merchant of record?

A merchant of record (MoR) is a company that takes legal responsibility for a sale on behalf of another business. The MoR appears on the customer's bank statement, handles payment processing, and is responsible for calculating, collecting, and remitting taxes in every jurisdiction where the sale occurs. Popular MoR platforms for SaaS businesses include Paddle, FastSpring, and Lemon Squeezy.

What is the difference between a merchant of record and a payment processor?

A payment processor (like Stripe or Braintree) handles the technical transfer of funds from buyer to seller — but the seller remains the merchant of record and is responsible for their own tax obligations. An MoR goes further: it becomes the legal seller of record, taking on full responsibility for taxes, compliance, and payment disputes. The trade-off is that an MoR takes a larger cut and removes control from the seller.

Do I need a merchant of record for SaaS?

Not necessarily. An MoR is one approach to managing global tax compliance, but not the only one. Early-stage SaaS companies selling in many countries from day one often find an MoR simplifies things significantly. However, as revenue grows, the fees (typically 3–6% of revenue on top of standard payment processing costs) and loss of checkout control become significant disadvantages. Many SaaS companies use tax compliance software like Quaderno instead, which automates VAT, GST, and sales tax without handing over control of the customer relationship.

How much does a merchant of record cost?

MoR platforms typically charge between 3% and 6% of each transaction, in addition to standard payment processing fees. On $500,000 ARR, that's $15,000–$30,000 per year purely in MoR fees. Some platforms also charge monthly subscription fees or additional fees for currency conversion and international transactions. The total cost of ownership should be compared against the cost of handling tax compliance directly.

What are the best merchant of record platforms for SaaS?

The most commonly used MoR platforms for SaaS and digital products are Paddle (strong global coverage, used by many B2B SaaS companies), FastSpring (well established, good for digital downloads and software), and Lemon Squeezy (popular with indie developers for its simple pricing). Each differs in supported countries, pricing structure, and the degree of checkout customisation they allow.