Compare merchant-of-record providers for SaaS before deciding who should own payments, sales tax or VAT, invoices, refunds, disputes, payout risk, and buyer support. Start with the operating model, then run the fee calculator.
A merchant of record can be the seller of record for your SaaS checkout. That can reduce tax, invoice, refund, dispute, and buyer-support work, but it can also trade away checkout control, payout flexibility, and migration simplicity. Compare MoR providers against a direct Stripe-style processor plus tax software, not against card fees alone.
| Input | Why it changes the shortlist | Where to model it |
|---|---|---|
| Customer geography | Global customers make tax, VAT, invoices, payment methods, and support ownership more important. | Open global SaaS model |
| Average order value | Fixed checkout fees matter more for low-ticket SaaS and less for annual-heavy plans. | Open low-ticket model |
| Billing complexity | Seats, upgrades, trials, coupons, invoices, webhooks, and failed payments can rule out otherwise attractive providers. | Open annual-heavy model |
| Migration tolerance | Subscriptions, customer records, tax history, and invoice exports can make switching later expensive. | Open provider scorecard |
A merchant of record can sit between your software business and the buyer. Depending on provider and plan, it may handle payment acceptance, tax calculation, tax remittance, invoices, refunds, disputes, fraud controls, and buyer support.
MoR fees usually look higher than direct processing fees because they bundle more work. The practical question is whether the higher fee is cheaper than building and operating those workflows yourself.
Paddle, Lemon Squeezy, Polar, and Creem are common merchant-of-record candidates for SaaS, developer tools, digital downloads, and software products. Stripe-style processing can still win when you want more control and can own the surrounding operations.
Compare order size, customer geography, refund rate, chargeback rate, support needs, tax complexity, and migration risk. If customer geography is uncertain, run conservative and aggressive scenarios before choosing.
| Provider route | Why SaaS founders shortlist it | What to verify first |
|---|---|---|
| Paddle | Established merchant-of-record checkout path for SaaS and software teams that want bundled payment and tax operations. | Plan fit, checkout flexibility, invoicing needs, migration path, and whether custom pricing changes the public model. |
| Lemon Squeezy | Simple merchant-of-record commerce path for software, subscriptions, paid templates, and digital downloads. | International, PayPal, subscription, payout, product eligibility, and whether its checkout flow fits the buyer experience. |
| Polar | Developer-friendly monetization route with merchant-of-record positioning and public software-focused pricing. | Plan economics, payout fees, dispute fees, international-card extras, and whether its workflow covers your subscription needs. |
| Stripe-style direct processing | More checkout and billing control when your team can own tax, invoices, disputes, refunds, and support operations. | Stripe Tax or tax-software cost, registrations, filing, remittance, support time, and international card fees. |
| Decision area | MoR question | Direct-processing question |
|---|---|---|
| Tax and invoices | Which taxes, invoices, and remittance workflows are included? | Who will monitor thresholds, register, file, and answer invoice questions? |
| Subscription control | Can the MoR support coupons, upgrades, downgrades, trials, and webhooks? | Can your team build and maintain the billing behavior you need? |
| Customer experience | Will the buyer recognize the seller name and checkout flow? | Can your own checkout reduce confusion, disputes, and support tickets? |
| Migration risk | How hard is it to export customers, subscriptions, and payment history later? | How much finance, tax, and support process must be created before migration? |
Start with the SaaS pattern that most resembles your business. The provider that wins for a small domestic product may not win for a global subscription product, and the direct-processing option changes once tax, invoices, refunds, and support work are included.
| Scenario | Open calculator | Comparison focus |
|---|---|---|
| Pre-launch global SaaS | Early global launch | Whether MoR simplicity is worth paying for before tax operations exist. |
| Low-ticket monthly SaaS | Low-ticket subscription model | Fixed fees, subscription fees, failed payments, and whether annual billing helps. |
| Digital product plus subscriptions | Mixed software sales | Checkout, license keys, digital delivery, subscriptions, and tax support in one stack. |
| Scaling SaaS with finance support | High-volume comparison | Volume pricing, payout rules, migration support, and whether direct processing regains control. |
Last checked: June 28, 2026. Public pricing pages are useful for modeling, but final fees can depend on country, payment method, volume, payout route, custom agreement, and whether the provider is acting as the full merchant of record.
| Provider route | What to verify before choosing |
|---|---|
| Paddle | Pay-as-you-go rate, low-ticket and invoice rules, custom pricing, migration support, and what is included in MoR coverage. |
| Lemon Squeezy | Base transaction fee, international and PayPal checks, subscription payment checks, payout fees, and custom pricing triggers. |
| Polar | Starter versus paid plan economics, international-card extras, payout fees, dispute fees, and Early Member plan status if applicable. |
| Stripe-style direct processing | Local card rate, international cards, currency conversion, Stripe Tax or tax-software cost, Billing, invoices, disputes, and support work. |
A merchant of record comparison should include more than payment percentage. Estimate hours spent on tax setup, invoice support, refund handling, dispute response, accounting cleanup, and country-specific customer questions. Those hours are part of the cost of direct processing, even when they do not appear on the payment statement.
Compare the provider you would choose today with the provider you would choose after growth. A $3,000 MRR side project, a $30,000 MRR global SaaS, and a $300,000 MRR company with finance support may all make different MoR decisions. The best answer changes as the operating burden changes.
The main calculator compares merchant-of-record and direct processing economics from one set of SaaS assumptions.
Open a MoR comparison scenarioIt is most useful for global SaaS, digital products, developer tools, and small teams that do not want to run tax and payment operations themselves.
No. It is often easier operationally, but direct processing can still be better if you have the right tax, finance, and support workflows in place.
Check subscription migration, customer records, invoices, taxes, payout timing, webhooks, failed payment recovery, and how refunds and disputes are handled.
Yes, if global sales are part of the plan. You may not need to choose an MoR immediately, but comparing early helps avoid a checkout and tax setup that becomes painful to unwind later.