Merchant of Record Explained: When You Should Stop Being the Seller

Pull up the credit card statement for your last SaaS subscription. Look at the line. There is a decent chance the name on it is not the company whose product you actually use. It might say "PADDLE.NET* COMPANYNAME" or "LEMONSQUEEZY*COMPANY" or some other intermediary you have never heard of. That is not a billing quirk. It is a deliberate legal arrangement called a Merchant of Record — and for a growing share of online businesses, it is the difference between shipping software and drowning in international tax filings.

This guide explains what a Merchant of Record actually is, how it differs from a payment processor (the two get conflated constantly), what it costs, when it makes sense, and how to evaluate the providers that have flooded the market over the past two years.

What "Merchant of Record" Actually Means

A Merchant of Record (MoR) is the legal seller of a product or service from the perspective of the customer, the card networks, and the tax authorities. When you sell through an MoR, the MoR is the entity that:

• Appears on the cardholder's statement
• Holds the merchant account with Visa, Mastercard, and other card networks
• Collects the payment and sends you the proceeds (minus its fee)
• Calculates, collects, and remits sales tax, VAT, and GST in every jurisdiction the buyer lives in
• Handles chargebacks, refunds, and fraud disputes
• Issues the invoice and stands behind the transaction in case of a regulatory audit

You — the company that built the product — become the supplier of the underlying goods or services to the MoR, who then resells them to the end customer. Legally, it is a wholesale-retail relationship even though the customer experience feels like buying directly from you.

That single legal substitution is what unlocks the model's value. Every compliance obligation that ordinarily attaches to "the seller" attaches to the MoR instead.

Merchant of Record vs. Payment Processor

These two terms get used interchangeably and they should not be. The differences are not cosmetic — they determine who is liable when something goes wrong.

A payment processor (Stripe, Square, Adyen in its standard mode, Authorize.net) is the technical pipe. It authorizes the card, moves the money, and deposits it in your bank account. It does not become the seller. You are still the merchant. You sign a merchant agreement. You are responsible for chargebacks. You owe sales tax in every state where you have nexus. You collect and remit VAT in every country where you cross the digital-services threshold. The processor's job ends at "did the card work."

A Merchant of Record sits one layer up. It is itself a customer of payment processors — but for you, it is the seller. The MoR signs the merchant agreements, takes on the chargeback liability, files the tax returns, and absorbs the risk of fraud loss. You get a payout that looks more like a royalty than a bank deposit.

The simplest test: open the receipt. If your company's legal name is on it, you are the merchant of record. If a third party's name is on it, the third party is.

What a Merchant of Record Actually Handles for You

The pitch is "we handle everything." In practice, the things that "everything" includes are surprisingly granular. A typical MoR takes over:

Payment infrastructure. Card processing, ACH, SEPA, iDEAL, PIX, Boleto, regional wallets like Alipay and PayPay. Most MoRs accept dozens of methods and dozens of currencies, with the foreign-exchange leg priced in.

Sales tax in the United States. Forty-five states plus D.C. now have economic nexus rules. Most use a $100,000 threshold; large states like California and Texas use $500,000. Once you cross a threshold in a state, you must register, file, and remit, regardless of where your office is. Several states (Illinois, Alaska, Utah) have removed the older 200-transaction trigger in the last two years, which actually simplifies the picture but does not eliminate the registration burden.

VAT, GST, and digital-services taxes worldwide. More than 140 countries now require foreign sellers of digital services to register and remit indirect taxes. EU VAT, UK VAT, Australian GST, New Zealand GST, Singapore GST, Indian GST on OIDAR services, Canadian GST/HST/QST, Japanese consumption tax — the list keeps growing. An MoR maintains registrations in all of these jurisdictions and remits on your behalf.

Invoicing in formats that satisfy local law. Several countries require specific invoice formats, sequential numbering, or even government-pre-cleared invoices (Italy, Mexico, India, Chile). An MoR generates them.

Chargebacks and fraud. When a cardholder disputes a charge, the MoR fights the chargeback. When fraud occurs, the MoR eats the loss. Card-not-present fraud rates run 0.5%–2% in many SaaS verticals; on $1M of revenue, that liability adds up.

PCI compliance and security. The MoR is the entity in scope for PCI-DSS, not you. Your application never touches a card number.

Subscription mechanics. Dunning emails, smart retries on failed cards, proration on plan changes, cancellation flows, refunds — all wrapped into the platform.

Customer support for billing. The MoR typically owns first-line billing support, which removes a meaningful chunk of work from your inbox.

What an MoR Does Not Handle

Equally important: an MoR does not give you tax cover for everything.

It does not handle your corporate income tax. If you are a Delaware C-corp, you still file a 1120. If you are a UK Ltd, you still file your CT600. The MoR is collecting and remitting indirect taxes on the customer's transaction; your business's profit is still your business's problem.

It does not handle payroll, employee benefits, or contractor payments. Those are separate systems entirely.

It does not eliminate regulated-industry compliance. If you sell financial products, healthcare data, or anything age-restricted, the MoR will not magically make you compliant with KYC, HIPAA, or age-verification rules. You still need those controls.

It often does not handle enterprise contracts well. If your buyer wants a manually negotiated MSA, custom payment terms, or a wire transfer with a 60-day NET, most MoRs are awkward fits. They are designed for high-volume, self-serve transactions.

The Real Cost: Fees vs. Hidden Overhead

The headline numbers look expensive. Most MoRs price somewhere between 4% + $0.40 and 8% + $0.50 per transaction. Compare that to a bare payment processor at 2.9% + $0.30 and the MoR looks like it is taking double or triple.

Run the math past the headline, though, and the picture changes:

• A US sales tax automation tool (Avalara, TaxJar, Anrok, Numeral) costs between $1,000 and $30,000 per year depending on transaction volume and number of state registrations. Filing fees and registration fees on top.
• A multi-jurisdiction VAT automation tool runs $5,000 to $50,000 annually.
• A fraud platform (Sift, Signifyd, Stripe Radar at scale) runs 0.1%–1% of revenue.
• Subscription billing software (Chargebee, Recurly, Stripe Billing) runs 0.5%–2% of revenue at scale.
• Chargeback losses and PCI compliance program: variable, but real.
• The accountant or operations hire who manages all of the above: $80,000–$180,000 fully loaded.

Add it up. Below roughly $30,000–$50,000 in monthly recurring revenue, the unbundled stack is usually cheaper. Above it, the MoR is often comparable or cheaper, and the operational simplification is a real benefit even when the bill is higher. The breakeven shifts down — meaning the MoR becomes attractive sooner — if you sell internationally from day one, because international tax registration is what really gets expensive on the unbundled side.

When You Should Use an MoR

You sell digital products or SaaS to customers in many countries. This is the canonical use case. The compliance load of selling globally is the single biggest justification for the model.

You are a small team without a finance or operations hire. If "the founder does the bookkeeping at 11pm" describes your company, an MoR is buying back your weekends.

Your typical transaction is self-serve and under a few thousand dollars. MoRs are optimized for credit-card checkout. They are not built for $200,000 enterprise deals with custom terms.

Chargeback exposure scares you. Some verticals — info products, gaming, certain communities — see chargeback rates that can get a regular merchant account suspended. Letting an MoR carry that risk is sometimes the only way to operate.

You want to launch globally without a year of legal work. Standing up legal entities, opening bank accounts, registering for VAT in each EU member state — it is months of work and tens of thousands in fees. An MoR effectively rents you that infrastructure.

When You Should Not Use an MoR

You sell B2B in the US only and you have nexus in just a handful of states. A processor plus a sales-tax tool covers it.

You sell large-deal enterprise software with negotiated contracts. The MoR's checkout-shaped pricing and rigid terms get in the way.

Your margins are thin and your transaction sizes are large. A 6% MoR fee on a $50,000 deal is $3,000. A 2.9% processor fee is $1,450. The math gets ugly fast on big tickets.

You need full control of the customer relationship for compliance reasons. Some regulated industries cannot legally cede the seller relationship to a third party.

The Provider Landscape in 2026

The market consolidated a lot in 2024 and 2025. Stripe acquired Lemon Squeezy in mid-2024, then launched its own first-party MoR product in private beta in 2026 — a signal that the model is here to stay. Paddle remains the long-running incumbent. A wave of newer, cheaper, developer-first options (Polar, Creem, Dodo Payments, Fungies) compete on price and DX, mostly aimed at indie SaaS and digital products.

Rough current pricing:

• Paddle: 5% + $0.50, no separate international fee
• Lemon Squeezy (now Stripe-owned): 5% + $0.50
• Polar: ~4% + $0.40, open source, developer-focused
• Creem: ~3.9% + $0.40, free SEPA payouts
• Stripe MoR (beta): ~3.5% on top of standard processing
• Cleverbridge / FastSpring: enterprise-flavored, custom pricing, traditionally higher

Pick on three axes: total cost (including currency conversion and international card surcharges), developer experience (do their SDKs and webhooks fit your stack), and the geographic mix of your customers (some MoRs are stronger in EU, others in LATAM, others in APAC).

How an MoR Changes Your Books

Switching to an MoR changes the shape of your accounting. Three things to know going in:

You are no longer recognizing gross revenue from end customers. You are recognizing the payout from the MoR. That is a fundamentally different revenue stream from a tax and audit perspective. Talk to your accountant before flipping the switch.

Your reports will not match the MoR's reports unless you reconcile carefully. Currency conversion, refund timing, and chargeback debits all create lag and noise. Build a monthly reconciliation routine from day one.

Your books need to track unit economics separately. The MoR's fee is essentially a cost of revenue. If you want to know your true gross margin, you need to model the all-in MoR cost (fees + chargebacks + currency spread) as a line item, not bury it.

This is exactly the kind of situation where a transparent, auditable accounting setup pays off. When the MoR's monthly statement arrives, you want to be able to trace each payout, fee, refund, and tax remittance to the right entry in your books — and have a reviewer be able to do the same a year later when you are raising money or selling the business.

Common Mistakes and How to Avoid Them

Treating the MoR fee as a sunk cost. It is a price you can negotiate at scale. Most providers will discount meaningfully above $1M ARR.

Ignoring the FX leg. Some MoRs spread foreign exchange aggressively. On a global business, FX can cost more than the headline fee.

Forgetting the underlying business still has tax obligations. The MoR handles indirect tax on transactions. Your company's income tax, payroll tax, and franchise taxes are unchanged.

Not exporting your data. If the MoR holds your subscription state and you ever want to migrate, you need an export plan. Check the data-portability terms before you sign.

Cancelling your sales-tax registrations too quickly. If you previously had nexus in states or VAT registrations, do not deregister until you have confirmed you no longer have a filing obligation in those jurisdictions for prior periods. The IRS and EU tax authorities do not let you walk away from past obligations because you switched models.

Keep Your Financials Clear from Day One

Whether you stay on a payment processor or move to a Merchant of Record, the underlying truth is the same: clean, transparent financial records are what make either model survivable when growth, an audit, or an acquisition arrives. Beancount.io provides plain-text accounting that gives you complete visibility into every transaction, fee, and tax remittance — no black boxes, no vendor lock-in, and a record that any auditor or future CFO can read. Get started for free and see why developers and finance teams running global software businesses are choosing version-controlled, AI-ready books.