Not all Merchant of Records are created equal: How to evaluate what actually matters in 2026

Step one: Know what kind of business you are

The evaluation criteria that matters most, and the providers worth shortlisting, differ significantly by business model. With AI accelerating SaaS growth, identify which profile best describes where you expect to be in 12-18 months, not just where you are today.

From speaking to businesses across the software industry, we’ve found that:

1. App-native businesses moving to web monetization (gaming studios, consumer apps, productivity tools shifting from platform to direct web sales) often prioritize fraud and chargeback handling, mobile checkout conversion, and fee structure at volume.
2. B2B SaaS - self-serve to mid-market (subscription software expanding internationally, seat or usage-based) prioritize tax compliance and correct B2B VAT treatment, billing model flexibility, and ERP/CRM integration.
3. AI-native or usage-based businesses (API products, developer tools, token or credit-based billing with fast pricing iteration) prioritize native usage metering, developer-grade API quality, and pricing flexibility without engineering overhead.
4. Enterprise or multi-entity software (cybersecurity, CAD, enterprise SaaS with complex contracts and established sales motions) prioritize vendors multi-entity billing, enterprise procurement requirements (SSO, audit logs, SOC 2), and dedicated account management.
5. Creators or digital products (indie developers, micro-SaaS, no dedicated engineering or finance team) prioritize fee transparency, self-serve onboarding, checkout quality, and platform stability.

Different profiles tolerate different trade-offs. But all of them are exposed to the same three forces: revenue, cost, and risk.

What are you actually evaluating?

Before applying the evaluation framework, it's worth being precise about what an MoR is - and what it isn't.

A Merchant of Record is a legal entity that takes on the operational and regulatory responsibility of payments on behalf of your business. That includes:

• processing the payment
• collecting and remitting applicable taxes (VAT, GST, sales tax)
• handling chargebacks and disputes
• managing fraud liability
• ensuring compliance with local consumer protection regulations

A business can act as its own Merchant of Record, but you would need to build a payment stack that handles all of the above. By choosing an all-in one MoR solution instead, operational and legal liability is no longer the responsibility of your team. This matters now more than ever with AI-native companies internationalising SaaS at pace. Offloading liability means you avoid slowing down to fix compliance issues and disputes.

The biggest mistake operators make is assuming every MoR takes on the same level of liability operational burden. The market today actually reflects a spectrum of models:

1. Complete MoR platforms: Purpose-built to be the legal seller of record globally, handling compliance automatically and unconditionally. One contract, one API, one liability owner.
2. Specialist or hybrid MoR solutions: Assume liability in most scenarios, with documented carve-outs where the seller retains responsibility. These carve-outs are often small, but they tend to surface in exactly the markets where compliance is most complex.
3. Billing platforms with MoR add-ons: Treat subscription management as the core product and offer MoR functionality as optional or routed through a third-party partner. A payment service provider like Stripe or Braintree offering "managed" compliance as an add-on can become more costly than the headline transaction fee suggests, or may redistribute liability back to you in ways that only become visible when something goes wrong.

Understanding which category a vendor falls into is the first question to ask in any Merchant of Record evaluation. The answer is rarely in the headline.

The evaluation framework: Six considerations for your business

Every Merchant of Record decision ultimately comes down to three value outcomes you want the vendor to deliver: increase revenue, reduce cost, manage risk.

The six considerations below each map to one of those value outcomes. Use them to evaluate each Merchant of Record not as a feature checklist, but as a set of business consequences.

1. Optimization, retention, and experimentation - How does the platform actively help you grow net revenue outside of processing transactions?
2. Localization and global payment optimization - Do your customers see a checkout that is optimized to convert in their local market?
3. Architecture and integration complexity - How many systems need to work together, and who owns the maintenance burden when they don't?
4. Total cost of ownership - What does the platform actually cost when you factor in all the billing tools you need on top of the headline transaction rate?
5. Global coverage and compliance - Does the provider actually register, file, and remit tax globally on your behalf?
6. Operational ownership and liability - When a chargeback, tax audit, or compliance dispute arises, who is legally and financially responsible?

Let’s look at the impact each consideration has on your business, what best-in-class signals cover, and red flags to look out for.

Value outcome: Increase revenue

1. Optimization, retention, and experimentation

The question: How does the platform actively help you grow net revenue outside of processing transactions?

Why it matters: The right platform does not just process transactions, it compounds your ability to convert, recover, and retain revenue across the entire customer lifecycle.

MoR evaluation is often dominated by compliance and infrastructure considerations, but revenue optimization capabilities - checkout conversion, involuntary churn recovery, pricing experimentation - have a significant and often underestimated impact on net revenue retention and growth trajectory. And they’re crucial to staying ahead of your competitors in today’s market.

Checkout conversion: The highest-leverage question is whether the platform helps you convert browsers into buyers. A fully customizable checkout that maximizes revenue with minimal engineering effort is expected - but not always a given. Localized checkouts, mobile optimization, A/B testing, and frictionless trial-to-paid flows all compound to boost payment acceptance. For app-native businesses moving to the web, this is a first-order consideration.

Dunning and recovery: Involuntary churn accounts for 20-40% of total churn for SaaS companies. The difference between adequate and excellent dunning can represent several percentage points of annual net revenue retention. At $5M ARR, a 2% improvement in recovery is $100K per year. At $20M, it's $400K. Platforms vary significantly in recovery sophistication, but smart features include:

• automated retry timing
• card updater integrations
• proactive expiry handling
• customer-facing recovery flows
• exit surveys

Pricing model flexibility: Support for flat, per-seat, usage-based, and hybrid pricing models, with accurate proration logic and mid-cycle changes, reduces friction for pricing experimentation and PLG motions. This is especially critical for AI-native and B2B SaaS profiles - evaluate whether the platform supports the billing complexity you'll need in 12 months, not just today. 

Revenue recognition and reporting: Finance teams at Series B-plus companies typically need revenue recognition aligned with ASC 606 or IFRS 15. Some platforms handle this natively. Others require third-party integrations or manual adjustments for the monthly close.

Best-in-class signals: 

• Native dunning with smart retry logic, not just fixed intervals
• A/B checkout testing without engineering involvement
• Multiple billing models supported without workarounds
• Revenue recognition built into the platform rather than bolted on
• Exit survey and voluntary churn data surfaced for retention use

Red flags: 

• Revenue recognition requiring a separate third-party tool
• Checkout not customizable without engineering work
• Dunning that only offers basic fixed retry intervals
• No exit survey capability or churn recovery data
• Pricing experiments requiring a code deploy 

2. Localization and payment acceptance

The question: Do your customers see a checkout that is optimized to convert in their local market?

Why it matters: Localization gaps show up as conversion rates that never reach their potential. The distinction between supporting payments in a country and supporting the way consumers in that country actually prefer to pay is where your addressable market is won or lost.

There are several ways you can localize, outside of just language and currency, that are easily overlooked.

Payment method coverage has a direct and measurable impact on conversion rates and your target addressable market (TAM). Accepting only card payments in markets where local alternatives dominate - UPI in India, Pix in Brazil, iDEAL in the Netherlands (used for 80% of all online transactions), BLIK in Poland, PayPal in Germany - means leaving revenue on the table. 

Tax-inclusive and exclusive-pricing matters. Most European consumers expect to see prices with tax included whereas US consumers expect the reverse. Checkout experiences that do not adapt to local norms create friction that shows up directly in conversion data. 

Willingness to pay for the same software can vary by 20-40% between markets. Customer expectations in the Netherlands are very different to those in India. Adapting the price of your products for different markets ensures you don’t deter customers or leave revenue on the table - both of which impact your bottom line and global conversion rates. 

A Series B SaaS company expanding from the US to Germany, France, and the UK in the same quarter should not need to configure tax registration separately for each market, engage a VAT specialist, or manually verify digital services tax treatment per transaction. If a platform requires that, it is documenting the problem, not solving it.

Best-in-class signals: 

• Local payment methods enabled by default in target markets
• Automatic tax-inclusive or exclusive pricing displayed based on buyer location
• Market-based pricing that reflects local willingness to pay, not just currency conversion
• Checkout language and trust signals that adapt to the buyer's country

Red flags: 

• Vendors that “support’ sales into a market but don’t offer specific payment methods in that region
• Currency conversion that simply applies an FX rate to your US price without any localization of the amount
• No ability to set market-specific pricing

Value outcome: Reduce cost

3. Architecture and integration complexity

The question: How many systems need to work together, and who owns the maintenance burden when they don't?

Why it matters: Every additional integration point is an engineering liability and a maintenance cost, and both scale with your transaction volume and market footprint in ways that are easy to underestimate.

Architecture is frequently treated as a technical implementation detail, but it has significant long-term business consequences. The core distinction is between adopting one integrated system versus assembling a stack of components.

A PSP plus MoR add on typically means: 

1. your payment processor handles transaction processing
2. a tax compliance layer (Avalara, TaxJar, or the PSP's own module) handles calculation
3. a billing platform manages subscriptions and revenue logic. 

Each layer requires integration, maintenance, and coordination. When something breaks at the intersection of two systems, for example a tax calculation doesn’t match the billing record, or a chargeback workflow requires input from three different platforms, your team owns the debugging.

A full MoR platform consolidates this into a single integration: 

1. one API for payments, billing, tax, compliance, and customer management. 

The operational simplification is real, though the trade-off can be reduced flexibility to swap best-in-class point solutions for specific functions. 

The right question is not "which architecture is better?" It is: what is my team's actual capacity to manage complexity, and what does that complexity cost in engineering hours per quarter? 

For enterprise and multi-entity profiles, the integration checklist extends further: ERP connectivity (NetSuite, Sage, SAP), SSO, granular audit logs, and role-based permissions. For creator and early-stage profiles, a single integration with clean documentation is more valuable than architectural flexibility they'll never use.

Migration effort is consistently underestimated. Moving to any new MoR platform requires mapping existing subscription data, customer records, payment method tokens, and billing logic to the new system. At Paddle, we’ve supported implementation in as little as 2 weeks. But realistically you should plan for six to twelve weeks of parallel running if you have more than a few thousand active subscribers.

Best-in-class signals: 

• Single API that covers payments, billing, tax, and compliance
• Clear migration support with a defined timeline
• Native ERP, SSO, and audit log integrations for teams that need them
• One vendor relationship, not three or more

Red flags: 

• Vendor cannot clearly map out which systems need to integrate with yours and who owns each connection
• Core MoR features (tax, billing, compliance) require separate product activations or third-party tools
• Migration timelines that feel unrealistically short given your subscriber volume

4. Total cost of ownership

The question: What does the platform actually cost when you factor in all the tooling you need on top of the headline transaction rate?

Why it matters: The platform that appears cheapest at the headline transaction rate is rarely cheap once you account for compliance tooling, engineering time, finance overhead, and revenue foregone from inadequate recovery tools.

Published transaction rates are the wrong unit for comparing MoR solutions. The right unit is total cost of ownership across 12 months, which includes:

• Platform transaction fees and how they scale with volume
• Engineering time for integration, maintenance, and market expansion
• Tax compliance tooling costs if not bundled
• Chargeback management infrastructure and staffing
• Revenue foregone due to inadequate payment recovery
• Engineering overhead for adding currencies, payment methods, and markets over time

A platform charging 5% with full compliance, dunning, and global coverage may be substantially less expensive than a stack charging 2.9% in processing fees with $25-40K per year in compliance tooling, a 0.3 FTE in tax management, and 3% annual involuntary churn from weak recovery logic.

The build-vs-buy calculation follows the same logic. Many companies that build compliance infrastructure eventually discover they have created a maintenance obligation that scales with their transaction volume, their market footprint, and the rate of regulatory change - none of which slow down as you grow.

Best-in-class signals: 

• Transparent, all-in transaction rate that covers payments, billing, tax, compliance, and dunning with no mandatory add-ons
• Vendor provides volume discount tiers in writing
• Clear total-cost estimate that accounts for internal engineering and finance time, not just platform fees

Red flags: 

• A headline rate that looks competitive but requires separate subscriptions for tax tooling, billing management, analytics, or chargeback handling
• Core MoR features are only available at a custom-priced tier with no published rate
• Vendor is unable or unwilling to provide a fully loaded cost estimate
• Exit clauses that make switching prohibitively expensive

Value outcome: Manage risk

5. Global coverage and compliance

The question: Does the provider register, file, and remit tax on your behalf - and who is liable if something goes wrong?

Why it matters: Non-compliance is a financial and reputational liability that grows with every new market you enter. The gap between what providers claim to do and what they actually absorb on your behalf is where that risk lives.

A good Merchant of Record facilitates global growth from launch by handling tax and compliance so you don’t have to. Often, it’s not until you start seeing demand in new markets that the gaps between different MoRs and what they actually deliver becomes clear. And in the age of AI, that demand appears much sooner than ever before.

This can be the most consequential consideration - with the risk of hefty fines and consequences for non-compliance. The relevant questions are not just "how many countries do you cover?" but: 

1. Do you automatically register in new jurisdictions when my transaction volume triggers a filing obligation? 
2. Do you handle both B2B and B2C tax treatment correctly (which differ materially under EU VAT rules)? 
3. Who holds liability if a filing is late or incorrect? 

Some platforms cover 80-plus countries but require you to handle domestic tax compliance in your home market or specific jurisdictions where local regulations prevent full liability transfer. 80 countries sounds like a lot, but the US has over 13,000 sub-state tax jurisdictions alone. Consider the resource impact that responsibility will have on your team and where that time might be better spent.

Best-in-class signals: 

• Automatic registration you in new markets when your sales volume triggers an obligation
• Vendor that handles both B2B and B2C tax treatment across jurisdictions
• Full liability for late or incorrect filings taken on by the vendor, not you
• Support in every market as the legal seller of record

Red flags: 

• The list of jurisdictions where they do not hold full tax liability is unclear or hidden in the fine print
• Coverage excludes your home market or US sub-state level
• B2B reverse-charge treatment that is not handled automatically
• Liability language in the contract is vague about who is responsible

6. Operational ownership and liability

The question: When a chargeback, tax audit, or compliance dispute arises, who is legally and financially responsible?

Why it matters: At low volume, questions of operational ownership feel abstract. At $15M ARR and above, they become some of the most operationally significant decisions you have made.

This often matters most when things go wrong.

Chargebacks and disputes: an experienced Merchant of Record should handle the dispute process end-to-end. You do not need to staff a chargebacks workflow or maintain relationships with acquiring banks. In a hybrid or PSP model, chargeback liability stays with you. Companies crossing $10-15M ARR in transactional volume typically discover that dispute management at scale is a meaningful operational concern, not a minor administrative task. Read more on how chargebacks can hurt your business.

Compliance audits: If a tax authority questions a filing in Germany, California, or Australia, who responds? In a full MoR model, the platform does. In a build-your-own compliance stack, your finance team does, often with external legal counsel. The cost of a tax audit, even a routine inquiry, in a jurisdiction where you lack local expertise can easily exceed several months of platform fees.

Ask vendors directly: If a customer in France is incorrectly charged tax and files a complaint with a local authority, what is your exact process, and what do you need from us? The answer to this question reveals more about actual operational ownership than any sales deck.

Pricing experimentation: The pace of AI means businesses are building and testing faster than ever. Optimizing pricing and packaging is crucial to keep up with your competitors - but pricing experiments may feel risky or involve waiting on engineering teams, with internal handoffs creating operational drag. The right MoR gives you time back to test, iterate, and release quickly, supporting product production - not hindering it.

Ongoing overhead is also worth quantifying concretely. Finance teams running their own compliance stacks typically spend 30-50% of a finance hire's time on tax management and monitoring. That cost does not appear in a platform pricing comparison, but it is real.

Best-in-class signals: 

• Chargebacks handled end-to-end with no action required from your team
• Vendor responds directly to tax authority inquiries in every market
• Inclusive customer payment support
• A clear explanation of where liability sits for every jurisdiction

Red flags: 

• Automatic refund policies that let the provider resolve disputes without your approval
• Dispute workflows technically exist but require your team to respond within short windows or liability reverts to you
• Compliance coverage that is handled "in partnership with" you rather than owned entirely by the provider
• No dedicated customer billing support
• Chargeback liability stays with you even on a full MoR tier

Choosing how to evaluate a Merchant of Record platform, and ultimately which one to select, is a strategic infrastructure decision, not a procurement exercise.

Use this framework as a structured starting point. Map your requirements against the six considerations, identify which trade-offs are acceptable given your team's resources and growth trajectory, and approach vendor claims about liability coverage with specific, written questions rather than marketing summaries. The clearer you are about what you actually need from a Merchant of Record, the easier it becomes to find the platform that genuinely delivers it.

Where Paddle fits in

The growth of the Merchant of Record category validates what operators at scaling software companies have known for years: managing tax compliance, fraud liability, and cross-border payments in-house is an unsustainable distraction from building your products. More providers entering the market means more choice and encourages existing MoRs to improve their models to serve the growing demand.

We built the framework in this guide because the Merchant of Record decision is not one-size-fits-all, and the differences between different models can have real consequences for the growth of your business.

A complete MoR

Paddle is built specifically for SaaS, app, AI-native, and digital product companies. We exist to help digital product businesses operate and grow automatically - capturing more revenue, reducing cost, and managing risk through one unified platform across payments, billing, tax, compliance, fraud, retention, and buyer support.

Mapped against the three outcomes this guide is built around, we:

1. Increase revenue. Paddle improves revenue across the end-to-end monetization journey - with 2–6% higher authorisation rates across 100+ countries and 30+ payment methods, and up to 16% conversion improvement through localized, optimized checkouts.
2. Reduce cost. Stacked PSP plus MoR add-on solutions typically reach 7–10% or more in total cost once billing, tax tooling, and operational overhead are factored in. Paddle replaces that with a single, predictable all-in model - one rate, one integration, one vendor relationship.
3. Manage risk. Paddle handles tax and compliance across 270+ jurisdictions globally, taking on the regulatory burden end-to-end so you do not carry it internally - including chargebacks, compliance audits, and the growing complexity of consumer subscription regulation.

If Paddle sounds like the right Merchant of Record for your business, book a demo with our team to find out more.