Should a software company selling worldwide use a merchant of record or a payment processor directly?

Short answer: If you’re a small or midsize software company selling subscriptions worldwide—especially to consumers—a merchant of record (MoR) is often the simpler starting point. Use a payment processor directly when you’re ready to own the tax and compliance work in exchange for more control and potentially lower costs.

The key distinction: a processor moves money; it generally doesn’t make you compliant everywhere you sell. With a standard processor setup, your company usually remains the merchant of record and is responsible for determining where tax registration, collection, filing, and remittance are required. Tax-calculation tools can help, but they don’t automatically take over those obligations. (stripe.com)

An MoR typically acts as the legal seller for covered transactions and handles defined responsibilities such as collecting and remitting applicable taxes. In return, it may cost more and impose constraints on checkout, invoicing, refunds, or the customer experience. The exact responsibilities depend on the provider’s contract and which products and transactions it covers. (paddle.com)

Practical rule of thumb: Start with an MoR if global tax administration would distract your team from building and selling the product. Consider moving to a direct-processing model—or using different models for different transactions—once you have the volume and expertise to compare the full costs: fees, tax tools and advisers, registrations, filings, and internal staff time. Some providers now offer MoR coverage for selected transactions, so it may not have to be an all-or-nothing choice. (stripe.com)

Before signing, check whether the MoR covers your specific software and customer types, where it operates, who handles refunds and disputes, what appears on customer invoices or card statements, and how customer data and revenue reporting work. For a major launch or a complex B2B setup, confirm the tax and contract details with a qualified adviser.

Short answer: For most software companies selling to buyers in many countries, a merchant of record (MoR) is the simpler default. A payment processor makes more sense once you have the tax and finance staff to handle compliance and enough volume to justify the work. Most of the sources below are written by MoR vendors, so check their fee and tax-coverage claims yourself.

The core difference is who the legal seller is. A processor moves the money, and you remain the seller. An MoR becomes the seller of record, so it takes on tax collection and remittance, fraud, and chargeback liability. One source puts it simply: a payment processor like Stripe only moves the money, so you stay the seller and the tax is yours.

Why an MoR usually fits a global software seller:

• Tax is the biggest burden. On a processor, you owe the VAT, you handle the chargebacks, and you file the tax returns. Each new market adds rules and possibly registrations, and for most independent software sellers going global, that work costs more than the higher MoR rate.
• Registration volume is large. One guide notes that without an MoR, you'd need to register for VAT across EU countries, and track US sales tax in over 12,400 jurisdictions.
• Early-stage teams benefit most. Early-stage SaaS companies selling in many countries from day one often find an MoR simplifies things significantly.

What you give up:

• Cost. Processor fees are lower. In one worked example for a $30 US card sale, Stripe alone came to $1.17 in total fees, while Lemon Squeezy came to $2.00 and Gumroad to $4.67. The gap is larger on high-volume or high-ticket sales. Typical MoR fee ranges reported are 4–8% per transaction, though pricing varies by provider.
• Control. As revenue grows, the fees and loss of checkout control become significant disadvantages. Some MoRs also limit how you customize billing and checkout.
• Liability is contractual, not absolute. You may still have your own corporate income tax and business obligations in your home jurisdiction, so an MoR doesn't cover everything.

When a processor is the better choice:

• You already have tax and accounting capacity, or a finance hire you can make.
• Most revenue comes from one or two countries where you can manage registrations.
• Volume is high enough that the fee difference matters more than the compliance work.
• You need deep checkout, pricing, or enterprise invoicing control. For large B2B deals, reverse-charge VAT handling and invoicing can differ from consumer sales, so consider that separately.

Practical approach: Ask three questions: Where are your customers (especially EU, UK, US, Canada, Australia)? Are they mostly consumers or businesses? Can someone on your team own registrations, filings, and disputes? If the answers point to many markets, consumers, and a small team, start with an MoR. Revisit the decision as revenue grows, and get advice from a tax professional in your home jurisdiction before committing, since the rules vary by country and change often.

Deciding between a Merchant of Record (MoR) and a payment processor depends primarily on whether you want to outsource the legal and financial complexities of global sales or maintain full, direct control over your operations.

There is no "better" option; there is only the right fit for your current stage of growth and operational capacity.

At a Glance: Key Differences

When to Choose a Merchant of Record (MoR)

Choose an MoR (e.g., Paddle, Lemon Squeezy) if your primary goal is to minimize operational overhead and scale internationally without building a complex finance backend.

• Global Compliance Headaches: If you are selling digital goods or software globally, you are subject to VAT, GST, and US sales tax laws in every jurisdiction where you have customers. An MoR takes on the legal liability for these taxes.
• Limited Resources: If you are a small team or solo founder, you likely do not have the time or expertise to manage tax registrations, filings, and fraud disputes in dozens of countries.
• Speed to Market: An MoR allows you to start selling worldwide almost immediately because they already have the necessary legal entities and compliance frameworks in place.

When to Choose a Payment Processor

Choose a payment processor (e.g., Stripe, PayPal) if you prioritize brand control, lower fees, and deep integration.

• Desire for Full Control: You want total ownership over the customer relationship, checkout experience, and data. You do not want another company appearing as the "seller" on your customers' bank statements.
• Lower Transaction Costs: If your volume is high, the 4%–8% fees charged by MoRs can become very expensive. A processor’s lower, transparent fees allow you to keep more revenue.
• Operational Maturity: If your company is already established, has a finance team, or uses dedicated tax compliance software (like Stripe Tax + an accountant), you may be well-equipped to handle the compliance layer yourself.
• Specific Business Needs: You may need complex checkout flows, custom split-testing, or specific product categories that MoR platforms might restrict or prohibit.

Summary Recommendation

• Start with an MoR if: You are an early-stage SaaS company, selling globally to B2C customers, and want to avoid the "tax/legal trap" so you can focus entirely on product development.
• Use a Payment Processor if: You have the administrative capacity to handle compliance, your sales are primarily domestic or B2B (where tax rules are often simpler), and you want to optimize for lower fees and total control.

Note: Some companies choose a hybrid approach, using an MoR for specific international markets where compliance is too difficult to manage, while using a processor for their home market.

For most software companies selling worldwide—especially early-stage SaaS or digital-product businesses—I’d start with a merchant of record (MoR). It simplifies international selling by making the MoR the legal seller for covered transactions and taking on much of the indirect-tax work, along with payment disputes and related support. ¹²

The trade-off: an MoR typically charges for more than payment processing, and it may constrain aspects of pricing, checkout, or customer support. Direct processing can offer more control, but a payment processor alone generally doesn’t assume your seller-side tax and compliance responsibilities. ¹²

Practical approach: compare the MoR’s all-in fees and contract terms against the total cost of direct processing—including tax registrations, filings, compliance staff or advisers, and dispute handling. Verify exactly which countries, products, and transaction types the MoR covers; responsibility may apply only to eligible transactions or supported jurisdictions. ¹⁹

Bottom line: If global reach and low operational burden are your priorities, lean MoR. If you’re large enough to justify the compliance operation and need maximum control, consider direct processing. Either way, get advice on your specific tax and legal obligations; an MoR arrangement does not automatically resolve every obligation your company may have. ¹

Sources: ¹ Stripe’s MoR guide · ² Paddle’s MoR explainer · ⁹ Stripe Managed Payments documentation