Merchant of Record for SaaS Startups: MoR Options Compared

If you’ve started selling a SaaS product to customers outside your home country, you’ve probably run into a question that has nothing to do with your product: who is responsible for collecting and paying sales tax or VAT in every one of those countries? For most early-stage founders, the honest answer is “not us, we didn’t think about it” — and that’s exactly the gap a Merchant of Record is built to close.

This guide covers what a Merchant of Record actually does, why it matters more than it sounds like it should for a small SaaS team, and how the three platforms founders ask about most — Lemon Squeezy, Paddle, and Polar — compare in practice.

What a Merchant of Record Actually Is

A Merchant of Record (MoR) is the legal entity that sells your product to your customer. That distinction matters more than it sounds. When a customer buys your subscription through a MoR, the MoR is technically the seller on record — they issue the invoice, collect the payment, and are legally responsible for calculating and remitting the correct sales tax, VAT, or GST for that customer’s location. You get paid a net payout after they’ve handled all of that.

Compare that to a standard payment processor like plain Stripe or PayPal. A processor moves money from your customer’s card to your bank account, but you remain the legal seller. That means you’re the one who has to figure out whether you owe VAT in Germany, GST in Australia, or sales tax in a dozen US states — and file and remit it, potentially in each of those places separately, once you cross that country’s registration threshold.

For a solo founder or a two-person team, that second scenario is a genuine trap. Global tax compliance is a specialized, ongoing obligation — not a one-time setup task — and getting it wrong can mean penalties long after you’ve moved on to other problems.

Why a Founder Might Choose an MoR Over Plain Stripe

The core value proposition of an MoR is simple: it absorbs the global tax compliance problem so you don’t have to build a tax team, hire an accountant in every country, or track threshold rules yourself. In exchange for a higher percentage take rate than a bare payment processor, you get:

• Automatic tax calculation and remittance across the countries the platform supports, without you registering for VAT/GST in each one yourself.
• Invoicing and receipts generated and sent on your behalf, formatted to satisfy each jurisdiction’s requirements.
• Chargeback and fraud handling that’s largely managed by the platform rather than left entirely to you.
• One integration that covers checkout, subscription billing, and tax — rather than stitching together a processor, a tax engine, and an invoicing tool separately.

This isn’t a compliance nicety — it’s the difference between being able to sell globally on day one versus needing a finance function you don’t have yet. That’s precisely why MoR platforms have become a default recommendation for indie SaaS founders and small teams, even though the fee is real.

Lemon Squeezy, Paddle, and Polar Compared

All three describe themselves as Merchant of Record platforms built for software and digital products, but they differ in maturity, ecosystem, and who they’re built for.

Platform	What it is	Tax handling	Best for
Lemon Squeezy	MoR built specifically for indie SaaS and digital products, acquired by Stripe	Full MoR — handles global sales tax/VAT on transactions it processes	Solo founders and small SaaS teams wanting a simple, developer-friendly checkout and subscription flow
Paddle	Longer-established MoR aimed at SaaS companies from early stage through growth	Full MoR — global tax compliance is a core product feature	Teams that want a more mature platform with deeper subscription management and reporting as they scale
Polar	Newer, open-source-friendly MoR built around a more developer-centric, API-first workflow	Full MoR, positioned for global compliance similar to the others	Developer-led teams and open-source-adjacent projects who want tighter API/webhook control and a leaner setup

A few practical notes worth weighing beyond the table:

• Lemon Squeezy now operates as part of Stripe following its acquisition. It’s still onboarding new merchants as of this writing, but founders should check Stripe’s current published documentation before committing, since integration details can shift after an acquisition.
• Paddle has been in the MoR space longer and tends to show up more often in conversations about scaling subscription billing, dunning, and revenue recovery once a SaaS product has real volume.
• Polar leans into an open, API-first philosophy that appeals to technical founders who want more control over the integration surface, and it’s popular in developer-tool and open-source-adjacent communities specifically.

None of these is universally “the best” — the right one depends on how much you value ecosystem maturity (Paddle), simplicity and Stripe-adjacent trust (Lemon Squeezy), or a developer-first API experience (Polar). Take-rate percentages on all three change periodically, so check each platform’s current pricing page directly rather than relying on a number that may already be stale by the time you read it.

When a Full MoR Is Worth It vs Handling Payments Yourself

Not every SaaS MVP needs a Merchant of Record on day one. The decision usually comes down to where your customers actually are and how much operational overhead you’re willing to carry yourself.

A standard processor (plain Stripe) plus your own tax handling makes sense when:

• You’re selling almost exclusively in one country and haven’t crossed that country’s tax registration threshold yet.
• You’re still validating demand and don’t yet have paying customers outside a single, simple jurisdiction.
• You have (or plan to get) an accountant who can manage the limited tax scope you actually have.

A Merchant of Record starts paying for itself when:

• You have or expect customers in multiple countries, especially the EU, UK, or other VAT/GST regions with low registration thresholds.
• You don’t have — and don’t want to build — an in-house finance function to track tax obligations across jurisdictions.
• You’d rather pay a higher per-transaction fee than spend founder time on tax compliance instead of the product.

For most early SaaS teams building with a lean simple tech stack, the MoR decision follows the same principle as every other early tooling choice: don’t build what you don’t need yet, but don’t avoid a managed service that removes a real, recurring operational burden either. Global tax compliance is exactly that kind of burden — it’s not a problem that gets easier to solve later, it accumulates.

How an MoR Fits Alongside Your Backend

It’s worth being direct about something that search results sometimes muddy: a Merchant of Record and a backend platform like Supabase are not competitors, and comparing them head-to-head doesn’t make sense — they solve entirely different problems. Supabase (or Firebase, or any backend-as-a-service) stores your application data, manages user accounts, and tracks subscription state inside your product. An MoR like Lemon Squeezy handles the actual money movement, checkout page, invoicing, and tax remittance outside your product.

In a typical MVP stack, the two work together: a customer completes checkout through the MoR’s hosted page, the MoR fires a webhook to your backend when the subscription is created or renewed, and your backend (running on Supabase or similar) updates that user’s access level accordingly. Getting this webhook-driven sync right is worth planning early — it’s the same category of integration decision covered in how to plan Supabase for a growing SaaS product, just applied to billing state instead of user data.

If you’re also weighing where subscription pricing itself fits into your MVP validation plan, a pricing hypothesis template for B2B SaaS founders is a useful companion read before you lock in a billing platform.

The Bottom Line

A Merchant of Record isn’t a payments upgrade — it’s an outsourced tax and compliance function wrapped around your checkout. For a founder selling to customers in more than one country, that’s a meaningfully different problem than “which processor has the lowest fee,” and it’s worth evaluating Lemon Squeezy, Paddle, and Polar on tax coverage, integration style, and ecosystem fit rather than fee percentage alone, since published rates change and are easy to get wrong secondhand. Whichever you pick, it sits alongside your backend, not in competition with it — your MVP still needs both.

Frequently Asked Questions

What is a Merchant of Record, and how is it different from Stripe?

A Merchant of Record (MoR) is the legal seller of your product. It collects payment from your customer, remits global sales tax and VAT on your behalf, and pays you the net amount. Plain Stripe is a payment processor — it moves money but leaves you as the legal seller responsible for calculating, collecting, and filing tax yourself in every jurisdiction you sell into.

Do I need a Merchant of Record for an early-stage SaaS product?

Not always. If you're only selling in one country and revenue is small, handling tax yourself (or with a processor plus a tax add-on) can be manageable. A MoR becomes worth it once you have customers in multiple countries, since tracking VAT/GST thresholds and filings yourself becomes a real operational burden a small team usually can't absorb.

Is Lemon Squeezy still available after the Stripe acquisition?

Yes, Lemon Squeezy operates as part of Stripe and continues onboarding new merchants as of this writing. Founders evaluating it should check Stripe's current published terms directly, since acquisition integrations can change product scope and pricing over time.

How does a Merchant of Record work with a backend like Supabase?

They handle separate jobs and are typically used together, not compared against each other. Supabase (or a similar backend) stores your application data, user accounts, and subscription state; the MoR handles the actual checkout, payment collection, invoicing, and tax compliance, then notifies your backend via webhooks so you can update access and entitlements.

What's the main tradeoff of using a Merchant of Record instead of Stripe directly?

You give up some flexibility and pay a higher take rate than a standard processor, in exchange for not having to register for tax in every country you sell into, build invoicing and refund flows yourself, or monitor VAT/GST thresholds. For a solo founder or small team, that tradeoff is usually worth it early on.