Merchant of Record: Simplify Global Payments for SMEs
2026-04-21
Your UK sales ledger is tidy. Your direct debits run on schedule. The finance team knows how to turn bank files into valid SEPA XML, upload them, and move on with the month-end close.
Then the business starts selling beyond its home market.
At first, that sounds like a straightforward win. More customers, more subscriptions, more invoices. In practice, the admin load changes shape overnight. A sale to a customer in another European market isn’t just another payment. It can mean different VAT treatment, different checkout expectations, different refund rules, and a bigger burden on the person reconciling settlements back to the bank.
That’s where the idea of a merchant of record matters. Not as fintech jargon, and not as a shiny growth tactic. It matters because it changes who is legally selling, who carries core payment and tax responsibilities, and how your team handles the daily reality of SEPA collections, transfers, refunds, and reconciliation.
The Scaling Problem Every SME Faces
A common pattern shows up when a small or mid-sized business grows. The company proves demand in the UK, gets its billing process under control, and starts taking orders from customers elsewhere in Europe. The commercial side feels exciting. The operational side gets messy very quickly.
The finance manager often sees the first warning signs. Customer payments arrive through one provider, refunds go out another way, VAT questions land in the inbox, and support asks why the statement descriptor doesn’t match the brand name a customer recognises. The original setup still works domestically, but cross-border selling exposes every weak join in the process.
Where growth starts to hurt
The pressure usually lands in four places at once:
- Tax treatment: A domestic process that felt manageable becomes harder when customer location affects VAT handling.
- Payment acceptance: Buyers expect familiar payment methods and a checkout flow they trust.
- Compliance burden: PSD2, Strong Customer Authentication, invoicing rules, and consumer protection obligations stop being abstract legal topics.
- Reconciliation workload: Finance teams have to match more moving parts across gateways, banks, and internal records.
If that sounds familiar, you’re not dealing with a niche issue. You’re dealing with the normal challenges of cross-border e-commerce that appear when a business expands faster than its payment and compliance stack.
Why internal workarounds stop working
Many SMEs respond by adding another payment provider, another spreadsheet, or another manual review step. That can keep things moving for a while, but it doesn’t solve the underlying problem. It just spreads responsibility across more tools and more people.
When a business expands internationally, the bottleneck usually isn’t demand. It’s the hidden operational work attached to each sale.
A merchant of record offers a different route. Instead of building an in-house tax and payment compliance engine, the business outsources the legal seller role for those transactions. That shift can remove a large chunk of the cross-border burden before your team has to create new internal processes to cope with it.
What Is a Merchant of Record
A merchant of record is the legal entity that sells to the customer and takes responsibility for the transaction. That’s the practical definition, but it helps to think about it in more familiar commercial terms.
A good analogy is a master distributor.
If your company sells software, subscriptions, training access, or another digital product, you still create and deliver the product. But the merchant of record sits between you and the buyer for the commercial transaction itself. The customer checks out through the merchant of record. The receipt comes from the merchant of record. The merchant of record then pays you according to your agreement.
The simplest way to picture it
Without a merchant of record, your business is the direct seller. That means you’re on the hook for the payment flow, the tax handling, and a large share of the legal and operational liability.
With a merchant of record, the transaction chain changes:
- Your customer buys through the MoR
- The MoR processes the payment and acts as seller
- The MoR handles the relevant transaction obligations
- Your business receives settlement from the MoR
Core idea: A merchant of record doesn’t just move money. It takes on seller liability for the transaction.
That sentence is where many readers get tripped up. A payment gateway and a merchant of record are not the same thing.
Why people confuse MoRs with payment providers
A gateway or payment service provider helps route and authorise payments. That’s important, but it’s only one slice of the workflow. It doesn’t automatically mean that provider becomes the legal seller, calculates and remits taxes for you, or assumes responsibility for the wider transaction.
A merchant of record does more. It sits at the commercial centre of the sale.
For a busy finance manager, the difference is practical rather than theoretical:
- A gateway helps a payment happen.
- A merchant of record takes ownership of the sale mechanics and the related liabilities.
What stays with your business
Using a merchant of record doesn’t mean handing over your whole business. You still own the product, the commercial strategy, and the customer proposition. You still decide what you’re selling and why.
What changes is the operating model around the sale. That matters most when the sales footprint widens across countries and your internal team doesn’t want to become a specialist unit for tax registrations, payment disputes, and compliance edge cases.
The Four Pillars of MoR Responsibility
Once you stop thinking of a merchant of record as a payment tool and start thinking of it as an operating model, its responsibilities become easier to understand. In practice, most of the value sits in four areas.
Global payment and payout management
The first pillar is the movement of money. The merchant of record handles customer-facing payment acceptance and then settles funds to your business.
For finance teams, this can simplify the front end of the process. Instead of maintaining a patchwork of local methods, currencies, and checkout logic yourself, the MoR handles the commercial payment layer. That often includes card processing and, depending on the model, support for bank-based flows that matter to European operations.
For a team working with SEPA bank files, the key practical effect is that incoming customer payments may no longer appear as a long list of individual receipts into your own merchant accounts. You may receive consolidated settlements instead, which changes reconciliation logic and reporting.
Tax and VAT handling
This is often the biggest reason businesses adopt the model.
Following the UK Supreme Court’s ruling on 12 November 2021 in KP Mall Limited v Revenue and Customs Commissioners, digital services sold to UK consumers by non-UK businesses triggered VAT obligations, and the ruling mandated 20% VAT on B2C digital supplies regardless of supplier location. HMRC data showed that in 2022, VAT collections from digital services exceeded £2.5 billion, up from £2 billion in 2021, and HMRC enforced non-compliance penalties on 15% of audited digital sellers in 2023, according to this merchant of record guide from Nexway.
That single development captures why MoRs became more important. VAT on digital sales isn’t something a growing firm can treat as a side task any more.
If the tax rule depends on where the buyer is, scale creates complexity faster than most SMEs expect.
A merchant of record typically calculates, collects, files, and remits the relevant indirect tax for covered transactions. That can remove a large amount of quarterly admin from a lean finance team.
Legal and financial compliance
The third pillar is compliance. This includes payment rules, authentication requirements, record-keeping expectations, and consumer-facing obligations attached to the transaction.
If you already spend time reading about regulatory compliance, you know the hard part isn’t just understanding the rule. It’s embedding the rule into live operational workflows without slowing sales down.
For UK and European firms, this matters because cross-border payments and digital sales touch multiple frameworks at once. A merchant of record sits in that zone and takes responsibility for the transaction-level compliance work that would otherwise sit with your own business.
Customer support and financial admin
The fourth pillar is the long tail of each sale. That’s the part teams often underestimate.
A completed payment still generates admin tasks:
- Refunds: Someone has to process them correctly and track the accounting effect.
- Chargebacks: Someone has to receive the dispute, manage evidence, and absorb the workflow load.
- Invoices and receipts: Someone has to issue compliant documentation in the right name.
- Transaction records: Someone has to maintain clean data for finance and audit use.
In a direct model, that someone is your team. In a merchant of record model, much of that sits with the MoR.
For an SME, that’s not glamorous work. But it’s exactly the kind of work that swallows time and creates risk when no one owns it clearly.
Choosing Your Model MoR vs Alternatives
The merchant of record model isn’t the only way to sell internationally. It sits alongside payment facilitators, marketplaces, and more direct payment setups. The right choice depends on what you’re trying to optimise: speed, control, margin, brand ownership, or operational simplicity.
The market is clearly moving. UK e-commerce sales reached £221 billion in 2023, representing 27% of total retail, and 68% of UK SaaS and digital firms used MoRs in 2024, up from 42% in 2020, to handle £45 billion in cross-border transactions. The same source notes that HMRC’s digital VAT gap narrowed to 11% (£1.1 billion) in 2023 from 17% in 2021, and that Stripe’s UK metrics showed MoR users achieved 15% faster market entry with 0.5% dispute rates versus a 1.8% industry average, according to The Payments Association’s explanation of the merchant of record model.
A practical comparison
| Criterion | Merchant of Record (MoR) | Payment Facilitator (PayFac) | Marketplace |
|---|---|---|---|
| Who is the legal seller | The MoR | Usually your business | Often the marketplace operator for marketplace transactions |
| Who carries core tax responsibility | The MoR for covered sales | Largely your business | Often split by marketplace rules and jurisdiction |
| Who handles payment processing | The MoR | The PayFac infrastructure supports your business | The marketplace |
| Who controls branding most directly | Shared, often less than direct processing | More control retained by your business | Least control |
| Who owns more of the customer relationship | Mixed | Usually your business | Often the marketplace holds more of it |
| Best fit | Fast international expansion with reduced compliance burden | Businesses wanting easier onboarding but more direct responsibility | Sellers willing to trade control for platform reach |
When an MoR makes the most sense
A merchant of record is usually strongest when your business wants to enter markets quickly without building a full internal tax and payment compliance function.
That tends to suit:
- Lean SaaS teams selling across borders
- Digital businesses with limited finance and legal capacity
- SMEs that want one operating model across multiple countries
- Teams under pressure to launch quickly without expanding headcount first
When alternatives may fit better
A PayFac or direct merchant setup may suit firms that want tighter control over checkout, data, and customer ownership. A marketplace can suit firms that prioritise distribution over brand control.
A useful way to think about it is this:
An MoR reduces operational responsibility. The trade-off is that you give up some direct control.
If you’re reviewing broader payment architecture before choosing, this overview of international payment gateways is a useful companion because it helps separate gateway capability from MoR liability transfer.
How an MoR Impacts Your SEPA and Bank File Workflows
For UK and European finance teams, the merchant of record question becomes real at the point of reconciliation. That’s where abstract strategy turns into daily work.
If you manage SEPA direct debits, outgoing credit transfer files, or bank uploads from ERP exports, a merchant of record changes the rhythm of your workflow. It doesn’t remove the need for disciplined bank operations. It changes what you’re reconciling and where the control points sit.
Your reconciliation pattern changes first
In a direct setup, your finance team may reconcile a high volume of individual customer transactions against internal invoices or subscription records.
In a merchant of record setup, the pattern often shifts to periodic settlement reconciliation. Instead of matching each end-customer payment directly through your own banking and PSP rails, you match the settlement report from the MoR to internal sales data, refunds, and expected payouts.
That can simplify one side of the process, but it also creates a new dependency. Your reporting quality is now tied to how clearly the MoR exports transaction, refund, fee, and settlement data.
SEPA direct debit and credit transfer still matter
An MoR doesn’t make SEPA irrelevant. It changes where SEPA sits.
You may still use SEPA rails for:
- Receiving business settlements into your bank account
- Paying suppliers and partners from those settled funds
- Issuing bulk refunds or credits
- Running non-customer collections using SEPA Direct Debit mandates that stay outside the MoR model
For many finance teams, that means your bank file process remains central even if customer-facing payment liability moves elsewhere. If your team is also handling multi-entity banking, treasury setup, or expansion logistics, practical issues such as setting up business bank accounts for non-UK residents can become part of the same operational conversation.
Mandates, exceptions, and file generation
The detail that catches teams out is exception handling. A merchant of record may streamline the sale, but your back office still has to process things like supplier payouts, manual credits, internal transfers, and edge-case refunds. Those often sit outside the glossy sales demo and land back with finance.
If your business also runs collections directly, this guide to automating SEPA direct debit collection helps map where direct debit automation fits alongside a broader payment stack.
Here’s a useful primer before you redesign workflows:
The operational takeaway
The biggest shift isn’t technical. It’s accounting logic.
Your team moves from managing many customer-level payment events toward managing fewer, larger settlement events plus separate bank-file activity for operational payments. That can be cleaner, but only if you design the handoff between MoR reports, ledger entries, and SEPA file generation carefully.
Finance teams don’t lose complexity with a merchant of record. They relocate it. Good implementations relocate it to places that are easier to control.
The Pros and Cons of MoR for Growing Businesses
A merchant of record can be a smart move for a growing business. It can also be the wrong fit if you choose it for the wrong reasons.
The strongest case for using one is focus. If your team wants to spend time on pricing, product, collections discipline, and clean reporting, outsourcing transaction liability can remove a large amount of specialist work from a small organisation.
Where the model helps
The benefits are usually most obvious when a company is expanding into more than one market and doesn’t want to build a mini compliance department.
Key advantages include:
- Faster market entry: You avoid building every tax and compliance process before selling.
- Less operational drag: Finance and ops teams deal with fewer transaction responsibilities directly.
- Reduced internal compliance load: The MoR takes on the seller role for covered transactions.
- Cleaner scaling path: The business can expand without stitching together multiple providers immediately.
The downsides that deserve more attention
The standard sales pitch for merchant of record services often downplays the trade-offs.
A contrarian view from Numeral argues that long-term costs can be higher than many firms expect. It notes that MoRs can erode margins by 15-20% through chargeback liabilities that are not fully shifted, and that 40% of MoR users in the FCA’s 2025 sandbox trials faced reconciliation delays with SEPA Credit Transfer mandates. The same source says 72% of UK PYMEs cited integration opacity as a key barrier in those trials and surveys, as described in this discussion of MoR drawbacks from Numeral.
That matters because the problems are not theoretical. They show up in cash application, treasury timing, and month-end reporting.
A balanced decision rule
An MoR is often a good fit when compliance complexity is blocking growth more than margin pressure is. It can be a poor fit when your economics depend on tight cost control, your billing flows are unusual, or your finance team needs fully transparent transaction-level control.
The real question isn’t whether a merchant of record is good or bad. It’s whether the responsibilities it removes are more expensive than the control you give up.
For many SMEs, the answer will be yes at one stage of growth and no at another. That’s normal. The model isn’t a permanent badge of maturity. It’s a strategic operating choice.
Your MoR Implementation and Integration Checklist
Choosing a merchant of record isn’t just a vendor selection exercise. It’s a redesign of part of your commercial and finance operating model. The best implementations start with blunt questions and a clear data flow, not a glossy demo.
What to ask before you sign
Start with a shortlist of practical questions. If a provider answers these vaguely, expect pain later.
- Country coverage: Which countries and transaction types does the provider support under its MoR model?
- Tax scope: Which taxes does it calculate, collect, file, and remit, and for which sales scenarios?
- Checkout control: How much can your team customise branding, pricing display, and customer experience?
- Data export: What transaction, refund, settlement, and fee data can finance pull out regularly?
- SEPA relevance: How are settlements paid to your bank, and what reporting fields are available for reconciliation?
- Refund handling: Who initiates refunds, and how do those events appear in reports?
- Dispute workflow: What evidence can your team see when chargebacks or customer disputes arise?
- Contract exit: What happens to recurring billing relationships and reporting access if you leave?
How the technical flow usually works
Most merchant of record implementations follow a predictable pattern, even when the front-end checkout looks different.
- Checkout starts: The customer enters a hosted checkout or embedded flow.
- The MoR processes the sale: Payment acceptance, tax calculation, and transaction handling occur inside the MoR environment.
- Your systems receive event data: Webhooks or API calls tell your product and finance stack what happened.
- Reports arrive later: Settlement files, refund records, and transaction summaries feed accounting and reconciliation.
For teams mapping those connections into existing payment architecture, this guide on integrating a payment gateway is useful because it highlights the technical handoff points that often get overlooked in project plans.
Why SCA handling matters so much
Strong Customer Authentication is one of the biggest hidden workloads in self-managed payment setups.
Under UK PSD2 regulations, the merchant of record assumes full liability for Strong Customer Authentication, and this has been shown to reduce unauthorised payment fraud by up to 70%. The model typically includes 3D Secure 2.0 and dynamic risk checks, and benchmarks cited by Stripe show 99.5% authorisation rates for MoR setups versus 92% for self-managed PSPs, according to this Stripe explanation of merchant of record SCA responsibilities.
That matters operationally because SCA isn’t just a compliance box. Poor authentication handling causes failed payments, support tickets, and manual intervention.
Practical rule: If your team doesn’t want to build and maintain SCA logic itself, test the MoR’s authentication flow as carefully as you test pricing and settlement.
How to make reconciliation workable
The best finance teams treat MoR reconciliation as a system design problem, not a monthly hero effort.
Use this checklist:
- Define a settlement key: Decide what internal reference links MoR settlements to orders, subscriptions, or invoices.
- Separate transaction layers: Keep end-customer sales events distinct from MoR settlement events in your ledger logic.
- Map refunds clearly: Decide whether refunds reduce future settlements or appear as separate flows.
- Document timing gaps: Record the normal lag between sale date, payout date, and bank receipt date.
- Test edge cases: Run failed payments, partial refunds, disputes, and currency mismatches before go-live.
- Agree an exception queue: Name the person or team that handles unreconciled items within a fixed review cycle.
What a good implementation looks like
A good MoR integration does three things well. It gives commercial teams a launch path, it gives product teams clear event handling, and it gives finance a reporting structure that survives audit and month-end pressure.
If one of those three is weak, the whole arrangement feels more complicated than it should.
Is a Merchant of Record Your Next Strategic Move
A merchant of record is not just a payment choice. It’s a decision about what your business wants to own.
If your company is selling across the UK and Europe and your internal team is spending too much time on transaction compliance, tax handling, and payment admin, an MoR can remove a real operational burden. That’s especially useful when the business wants to expand without hiring specialist tax, legal, and payments staff first.
If, on the other hand, your margins are tight, your billing flows are unusual, or your finance team needs direct control over every customer transaction and settlement detail, the trade-off may be too expensive. In that case, a more direct setup might fit better even if it creates more responsibility in-house.
A sensible next step is to review your current process in plain terms:
- List what your team handles today across tax, disputes, refunds, and payment compliance
- Identify where SEPA workflows interact with sales operations
- Measure the reporting and reconciliation work created by your current setup
- Ask whether growth is being slowed by compliance work or by lack of control
That last question matters most.
For many UK and European PYMEs, the answer won’t be permanent. A merchant of record can be the right model during one stage of expansion and the wrong one later. The point is to choose deliberately, with full visibility into how the model affects your bank operations, settlement logic, and internal workflows.
Your finance stack still needs reliable SEPA file handling either way. Whether customer liability sits with an MoR or with your own entity, clean bank files remain essential for transfers, refunds, payouts, and collections. Validating bank details with an IBAN validator before file generation prevents avoidable rejects.
If your team still works from Excel, CSV, JSON, or legacy AEB bank files, ConversorSEPA can help you turn those inputs into valid SEPA XML quickly and securely. It’s built for finance teams, advisers, and technical staff who need a practical way to prepare remittances, automate bank-file generation, and reduce formatting errors without adding more manual work.
Frequently Asked Questions
- What is a merchant of record and how is it different from a payment gateway?
- A merchant of record is the legal entity that sells to the customer and assumes responsibility for the transaction, including tax, compliance, and disputes. A payment gateway only routes and authorises payments without taking on seller liability or handling tax obligations.
- How does a merchant of record handle VAT for cross-border sales?
- A merchant of record typically calculates, collects, files, and remits the relevant indirect tax for covered transactions in each jurisdiction. This removes the need for your business to register for VAT in every country where you sell, saving significant quarterly admin for lean finance teams.
- Does using a merchant of record affect SEPA bank file workflows?
- Yes, it changes your reconciliation pattern. Instead of matching individual customer payments, your finance team reconciles periodic settlement reports from the MoR against internal sales data. SEPA rails remain important for receiving settlements, paying suppliers, and running collections outside the MoR model.
- When should an SME consider using a merchant of record?
- An MoR makes the most sense when compliance complexity is blocking growth more than margin pressure. It's especially suited for lean SaaS teams, digital businesses with limited finance capacity, and SMEs expanding across multiple European markets without specialist tax and legal staff.
