Every few years, a payment model gets positioned as the answer to everything. The Merchant of Record is having that moment right now and for good reason. For a particular type of business, at a particular stage, it genuinely solves hard problems. But the way it is being marketed to founders and finance teams sometimes papers over significant limitations that only become visible once you are locked in.
This piece is not a takedown of the MoR model. It is an honest assessment of what it does well, what it costs you, and how to know whether it is the right structure for where your business actually is, not where a sales deck assumes you are.
- What the Merchant of Record Model Actually Means
- The Business Problems MoR Was Built to Solve
- The Real Costs and Trade-Offs
- MoR vs. Direct Acquiring At a Glance
- When MoR Is the Right Call
- When MoR Creates More Problems Than It Solves
- The Hybrid and Exit Path
- Questions to Ask Before Signing with an MoR Provider
- Conclusion
- FAQs
What the Merchant of Record Model Actually Means
The term gets used loosely, so it is worth being precise. When a company acts as your Merchant of Record, they become the legally recognised seller in every transaction your customer completes. Their name is on the contract with the acquirer. They collect the money, remit the applicable taxes, handle refunds, absorb chargeback liability, and are responsible for compliance with local consumer protection law.
You, as the software company or digital goods seller, receive the net revenue after their fee is deducted. From a regulatory and legal standpoint, your customer bought from the MoR not from you.
This is fundamentally different from a payment gateway, which simply routes transaction data, or a Payment Service Provider (PSP), which processes payments on your behalf but leaves the merchant relationship and its obligations with you.
Well-known providers operating in this space include Paddle, FastSpring, and Digital River. Each has a slightly different commercial model, but the structural principle is the same: they own the transaction, and they carry the legal weight that comes with it.
The Business Problems MoR Was Built to Solve
The MoR model did not appear arbitrarily. It emerged as a direct response to very real friction points that digital businesses face when they try to sell internationally.
Selling into the United States means dealing with economic nexus thresholds that vary state by state. Add Canada, Australia, India, and Southeast Asia, and you have a tax compliance operation that can easily demand a dedicated team or a significant external accountancy spend. An MoR absorbs this entirely; they register for tax in each jurisdiction, file returns, and handle any audits. You receive your revenue net of tax already sorted.
Compliance and liability offloading is the second major draw. PCI DSS compliance, strong customer authentication requirements under PSD2, local consumer protection laws governing refunds and cooling-off periods the MoR takes on all of this. For a founder-led business where the payments stack is not a core competency, this is genuinely valuable risk transfer.
Speed to market matters more than many finance teams acknowledge. Setting up direct acquiring relationships across multiple geographies takes months entity registration, local banking relationships, integration work, compliance checks. An MoR can have you accepting payments in 50 countries within weeks.
The fit with SaaS and digital goods is particularly strong. Subscription billing, seat-based pricing, usage-based models, free trials converting to paid these are all well-supported by established MoR platforms. If your product is software, e-learning, or digital media, the infrastructure is ready.
Consider a concrete scenario: A 12-person B2B SaaS company based in the UK, preparing to launch across Western Europe. Their finance function is one part-time financial controller. VAT registration in Germany, France, Spain, Italy, and the Netherlands plus ongoing filing would cost somewhere between £30,000 and £60,000 per year in external accountancy fees alone, before considering the internal time. An MoR that charges 5% of revenue on €500,000 of European ARR costs €25,000. At that volume, the maths are clear.
The Real Costs and Trade-Offs
The MoR model has a price beyond the headline fee, and businesses that do not examine it carefully before signing often find themselves surprised later.
Margin compression becomes significant at scale. MoR fees typically range from 3.5% to 6%+ of gross revenue, depending on the provider, the transaction volume, and the geographic mix. For a business doing $2M ARR, that is a manageable cost of simplicity.
For a business doing $15M ARR, it is a seven-figure annual spend on a service you may no longer need or that direct acquiring could replace at a fraction of the cost.
Brand experience is partially out of your control. In many MoR arrangements, the provider’s name appears on the customer’s bank statement rather than yours. For B2C businesses with strong brand recognition, this creates customer confusion and unnecessary support queries. For B2B businesses where invoice presentation matters, it can create friction in finance department approvals.
Checkout customisation is constrained. The MoR controls the payment infrastructure, and their checkout is typically their checkout. Payment method availability, the localisation of the payment experience, retry logic for failed transactions, and 3DS handling are all governed by their platform decisions not yours. Businesses that want to optimise conversion through checkout testing often find this limiting.
Customer payment data stays with the MoR. This is the point that receives the least attention in the early stages and causes the most pain later. The tokenised card data, the transaction history, the payment method preferences these typically sit in the MoR’s vault, not yours. When you want to migrate to direct acquiring, you cannot take that data with you without significant contractual negotiation, and sometimes not at all. Your churn modelling, fraud detection, and personalisation capabilities are all constrained by what data the MoR shares back with you through their APIs.
Revenue recognition becomes a CFO-level conversation. Under IFRS 15 and ASC 606, when a third party is the legal seller, you are reporting net revenue not gross. For businesses that track gross revenue as a primary growth metric or that are approaching a fundraising round or acquisition where revenue multiples matter, the distinction is commercially significant. Finance teams should model this before signing.
MoR vs. Direct Acquiring At a Glance
| Factor | Merchant of Record | Direct Acquiring |
| Tax & compliance responsibility | MoR handles it | You handle it |
| Fee structure | 3.5–6%+ of revenue | 0.3–1.5% interchange + scheme fees |
| Speed to market | Weeks | Months |
| Checkout control | Limited | Full |
| Customer data ownership | MoR retains | You retain |
| Chargeback management | MoR manages | You manage |
| Revenue reporting | Net (principal/agent) | Gross |
| Best fit | Early-stage, digital, multi-market | Scaling, volume-driven, brand-led |
When MoR Is the Right Call
With the full picture in view, the MoR model is clearly the right choice in specific circumstances.
You are pre-Series A, or early Series A, and your payments function is not resourced. You are selling digital goods or SaaS. You need to be in 15 or more countries without setting up legal entities in each. Your average transaction value is modest, your volume is high, and your margins can absorb the fee. Your priority right now is growth velocity, not payment cost optimisation.
In these conditions, the MoR model does exactly what it promises. It removes a category of operational and legal complexity from a business that cannot afford to build the in-house capability to manage it. The fee is a rational cost of focus.
A useful practical heuristic: if the cost of setting up and managing compliant tax and acquiring infrastructure yourself would exceed the MoR fee on your projected revenue, the MoR is the better economic choice. At early volumes, this calculation almost always favours the MoR.
When MoR Creates More Problems Than It Solves
The circumstances where MoR becomes the wrong answer are equally well-defined.
Revenue scale changes the economics. Once you are generating $8M–$15M or more in gross revenue, the difference between a 5% MoR fee and a 0.8% direct acquiring cost is a material number.
At $10M, that gap is roughly $420,000 per year. At that point, building a proper payments function or hiring a payments consultancy to design and manage the transition is almost always financially justified.
Physical goods and services are a poor fit. The MoR model was built for digital. Most established providers either will not support physical goods at all, or apply terms that make it economically unworkable. If you have hybrid revenue digital subscriptions alongside physical fulfilment the MoR typically cannot serve the whole business cleanly.
High-risk verticals are frequently excluded. Businesses in gaming, gambling, nutraceuticals, financial services, and similar categories will find that mainstream MoR providers decline to board them. The MoR’s own acquiring relationships constrain who they can serve.
Chargeback visibility and dispute management suffer. When the MoR owns the acquiring relationship, your visibility into chargeback data, reason codes, and dispute outcomes is mediated through their platform. Businesses with sophisticated fraud or dispute management requirements find this indirect relationship a genuine operational constraint.
Customer experience and brand ownership matter more. At a certain scale, the checkout is a brand touchpoint. Conversion optimisation through A/B testing, localised payment method selection, and seamless post-payment flows become revenue decisions. MoR platforms offer limited flexibility here compared to direct integrations with acquirers and payment orchestration layers.
5 Signals You Have Outgrown Your MoR
- MoR fees now exceed £300,000–£500,000 annually
- You are losing checkout conversion to payment method gaps
- Customer support queries reference the MoR’s name, not yours
- Your fraud team cannot access raw transaction data
- You are in a fundraising or M&A process where gross revenue reporting matters
The Hybrid and Exit Path
Some businesses use the MoR model as a market entry tool rather than a permanent infrastructure decision. They launch in a new region through an MoR to test product-market fit without committing to local entity setup and direct acquiring. Once volume justifies it typically $2M–$5M ARR from a single region they migrate to direct acquiring for that geography while retaining the MoR for smaller or newer markets.
This is a legitimate strategy, but it requires deliberate planning from the start. The key questions to resolve before signing with any MoR:
- What are the data portability provisions in the contract? Can you export tokenised card data to a new acquirer or vault provider?
- What is the contractual notice period for termination?
- How deeply does the MoR’s checkout integrate into your product, and what does unpicking it cost?
- Will the MoR support a parallel running period during migration?
Businesses that do not ask these questions before signing sometimes find the MoR relationship is easier to start than to end.
Questions to Ask Before Signing with an MoR Provider
Before committing to an MoR arrangement, finance and payments leads should work through the following:
On data and ownership:
- Who legally owns the customer payment data, and on what terms can it be transferred?
On brand and customer experience:
- What name appears on the customer’s bank statement?
- What control do we have over checkout design, payment method selection, and localisation?
On economics:
- What is the all-in fee including currency conversion, refund processing, and failed payment fees?
- How does pricing change as our volume scales?
On risk and disputes:
- How are chargebacks handled, and what visibility do we have into dispute outcomes?
- What are the reserve requirements, and under what conditions are reserves held or increased?
On exit:
- What are the termination notice requirements?
- What data migration support is provided if we move to direct acquiring?
Conclusion
The Merchant of Record model is not broken. It is a well-designed solution to a real set of problems but those problems belong to a specific type of business at a specific stage of growth. For an early-stage, digital-first company selling globally without a payments team, it removes a category of complexity that would otherwise consume disproportionate operational resources.
For a scaling business with real payment volumes, direct acquiring relationships, and a finance function capable of managing tax compliance, the same model becomes an expensive structural constraint. The fee is too high, the data control is too limited, and the checkout flexibility is too restricted to justify the simplicity premium.
The decision is not about which model is better in the abstract, it is about which model fits your business, your volume, and your growth trajectory right now. And it is about having the foresight to plan the transition before you need it, not after you are already constrained by it.
Payment Mentors works with businesses at both ends of this decision evaluating whether an MoR arrangement still makes sense, designing the migration to direct acquiring when it does not, and building the payments infrastructure that scales with the business rather than limiting it.
FAQs
1: What is a Merchant of Record and how is it different from a payment gateway?
A Merchant of Record (MoR) is the legally recognised seller in a transaction. They handle tax collection, compliance, chargebacks, and refunds on your behalf. A payment gateway simply routes transaction data between your site, the acquirer, and the card networks; it does not take on any legal or compliance responsibility. With a gateway, you remain the merchant of record and carry all associated obligations yourself.
2: What is the difference between a Merchant of Record and a Payment Service Provider (PSP)?
A PSP processes payments on your behalf but keeps you as the legal merchant meaning tax obligations, chargeback liability, and compliance remain with you. An MoR goes further: they become the legal seller, absorbing all of those responsibilities. The trade-off is that a PSP gives you more control and lower fees, while an MoR offers more simplicity and compliance coverage at a higher cost.
3: Is the Merchant of Record model only suitable for SaaS businesses?
It is most commonly used in SaaS and digital goods software, e-learning, digital media, and subscriptions because the model was built around digital transactions. Most established MoR providers do not support physical goods or high-risk verticals. However, any digital-first business selling across multiple jurisdictions without in-house payments expertise could benefit from the MoR structure, regardless of whether they are strictly a SaaS company.
4: How much does a Merchant of Record typically charge?
MoR fees generally range from 3.5% to 6% or more of gross transaction revenue, depending on the provider, transaction volumes, geographic mix, and currency conversion requirements. Additional fees often apply for refunds, failed payments, and chargebacks. At low volumes, this is typically competitive with the cost of building compliant in-house infrastructure. At higher volumes typically above $8M–$10M ARR the economics usually favour migrating to direct acquiring.
5: Who owns the customer payment data when using an MoR?
In most MoR arrangements, the provider retains the tokenised card data and transaction records, since they are the legal merchant. You typically receive transaction data through APIs, but the underlying payment credentials remain in the MoR’s vault. This has significant implications for fraud management, personalisation, and future migration businesses planning to eventually move to direct acquiring should negotiate data portability clauses before signing.
6: Can I switch away from a Merchant of Record provider later?
Yes, but it requires planning. Moving away from an MoR involves rebuilding checkout infrastructure, establishing direct acquiring relationships, handling tax registration in relevant jurisdictions, and most critically migrating customer payment data. Some providers offer data portability; others do not. Review termination notice periods, data export provisions, and migration support terms carefully before entering any MoR agreement. Building an exit strategy at the start is far less painful than negotiating one under commercial pressure.
7: Does using a Merchant of Record affect how I report revenue?
Yes. Under IFRS 15 and ASC 606, when a third party is the legal seller in a transaction, the business typically reports revenue on a net basis not gross. This means revenue figures will appear smaller than if you were reporting gross transaction value through direct acquiring. For businesses approaching fundraising rounds, acquisitions, or public markets, this distinction can affect valuation multiples and investor perception. Finance teams should model this before committing to an MoR structure.
8: What happens when a customer raises a chargeback under an MoR arrangement?
Since the MoR is the legal merchant, they manage the chargeback process directly with the acquirer and card networks. You are typically notified and may be asked to provide evidence to support the dispute, but the MoR handles the formal response. The downside is that your direct visibility into chargeback reason codes, outcomes, and patterns is limited which can constrain your ability to optimise fraud prevention and reduce dispute rates independently.
9: Does the Merchant of Record model work for subscription and recurring billing?
Yes, recurring billing is actually one of the strongest use cases for the MoR model. Established providers like Paddle and FastSpring have mature subscription management infrastructure built in, including dunning logic, failed payment retries, proration for plan changes, and automated tax handling on renewals. For a SaaS business that wants subscription billing without building it from scratch, this is one of the MoR’s most practical advantages.
10: Can a business use an MoR for some markets and direct acquiring for others?
Yes, and this hybrid approach is increasingly common. Businesses often use an MoR for smaller or newer markets where the volume does not justify direct acquiring infrastructure, while running direct acquiring relationships in their core high-volume regions. The key challenge is operational complexity managing two parallel payment stacks requires clear internal ownership, consistent reporting across systems, and careful customer experience management to avoid inconsistency at checkout.
11: What types of businesses are typically rejected by MoR providers?
Most mainstream MoR providers decline businesses in high-risk or regulated verticals, including online gambling and gaming, financial services and forex, nutraceuticals and supplements, adult content, and certain categories of marketplace or peer-to-peer transactions. This is because the MoR’s own acquiring relationships constrain which merchant types they can board. If your business falls into any of these categories, you will likely need direct acquiring through a specialist high-risk acquirer rather than an MoR solution.
12: What questions should I ask an MoR provider before signing a contract?
The most critical questions cover five areas: data ownership and portability rights if you migrate away; termination notice periods and exit provisions; the full fee structure including refund, failed payment, and currency conversion fees; how chargebacks and disputes are managed and what visibility you retain; and which product categories and geographies are excluded from coverage. Many businesses focus on the headline fee and overlook exit and data terms which tend to be the most commercially painful clauses later in the relationship.