Merchant of Record Platforms Compared: Paddle, Lemon Squeezy, and Building It Yourself

Merchant of Record Platforms Compared: Paddle, Lemon Squeezy, and Building It Yourself

Selling digital products or SaaS globally, the most underestimated cost is not the processing fee. It is the compliance workload behind sales tax and VAT: dozens of countries, each with its own rates, registration thresholds, filing cycles, and invoice formats. The merchant of record model exists precisely for this problem. The platform becomes the legal seller and carries the tax liability, and you settle with the platform.

1. Three Roles That Are Easy to Confuse

An acquirer such as Stripe or Adyen moves money from the card and leaves the tax liability with you. A tax tool such as Stripe Tax calculates and files, but the legal entity is still yours, along with the penalties for mistakes. A merchant of record becomes the seller of record toward the consumer, taking on tax, refunds, chargebacks, and part of the compliance burden.

That distinction drives everything. MoR fees look higher, but what you remove is an entire tax and compliance function. Once that cost is priced in, many teams reach the opposite conclusion.

2. The Main MoR Platforms

2.1 Paddle

UK-founded and focused on SaaS and digital products, Paddle bundles checkout, subscription management, tax remittance, and fraud controls. Subscription support is among the more complete, covering trials, upgrades and downgrades, usage-based billing, and dunning. Its tax and invoicing backend is the core selling point. Onboarding is relatively strict, with higher compliance expectations for business model and product type.

2.2 Lemon Squeezy

Known for being developer-friendly and quick to launch, Lemon Squeezy provides hosted checkout, license keys, subscriptions, and tax remittance, suiting independent developers and small teams shipping digital products fast. It has been acquired by Stripe, so the long-term product direction should be checked against official announcements.

2.3 Verifone (formerly 2Checkout)

A long-established platform that combines MoR with acquiring, supporting merchant entities and payment methods across many regions. It fits teams already running traditional software licensing who need broader geographic coverage. The interface and documentation are more conventional, and integration is less brisk than the two above.

2.4 Capability Comparison

Rates and supported regions change, so verify against each provider's current pages.

3. Why MoR Fees Look Higher

An MoR effective rate is usually well above pure card acquiring. The fair comparison unbundles what it includes: tax calculation and filing, invoice compliance, refunds and chargebacks, consumer protection responsibilities in some regions, plus cross-border collection and FX. Outsourcing those to an accountant or a tax SaaS often costs no less than the MoR markup.

The real inflection point is business complexity. The more countries you sell into, the more varied your digital catalogue, and the more subscription tiers you run, the stronger the MoR case. If you only sell into one or two countries with a handful of SKUs, self-building is usually cheaper.

One hidden cost is easy to miss: errors and penalties. When you self-build tax, a misjudged rate, a late filing, or an invoice missing required elements can trigger assessments and fines, and those risks typically surface only after volume grows. An MoR transfers that uncertainty as well, at the price of a fixed rate you cannot optimize down. For early-stage teams this makes MoR closer to buying insurance than buying a service.

4. Pros and Cons

Strengths: tax liability transfers out, so you never build a global tax function; checkout and subscription capabilities work out of the box; refunds, chargebacks, and consumer compliance sit with the platform; time to launch is short, which suits rapid validation.

Constraints: higher effective rate; limited control over pricing, checkout experience, and brand presentation; strict review that can reject some business models; settlement cycles and account autonomy are weaker than an owned acquiring account; long-term dependence on a single platform creates pricing and migration risk.

5. Who It Fits

Good fit: digital products and SaaS sold across many countries; small teams with no dedicated tax staff; validation stage where speed to launch matters most; scattered buyer geography with widely varying rates.

Poor fit: single-market sales; very low ticket sizes where fees dominate; a need for heavily customized checkout and branding; an established tax and finance team willing to self-build.

6. Choosing Between MoR and Self-Built

Three decision lines: the number of countries you sell into, where beyond a certain count MoR becomes the lower-effort option; whether you have dedicated tax capacity, since if you do not, MoR wins; and whether you need deep checkout customization, which pushes you toward self-building. A common compromise is a split stack: an owned Stripe stack for core markets where rates and experience matter, and an MoR for the long tail where tax compliance would otherwise be disproportionate. For role definitions and combinations, see the cross-border payment selection matrix. For tax specifics, see the VAT and sales tax compliance guide. For the Stripe trade-offs, see the Stripe pros and cons analysis. For failed-payment recovery, see the subscription dunning and recovery guide. More options are collected under the Payment category.

Source: 16IDC original. Product capabilities, pricing and eligibility requirements follow www.paddle.com / www.lemonsqueezy.com / www.verifone.com and related official documentation and contract terms.