Merchant of Record (MoR): Do You Need One or Just a Payment Provider?

A Merchant of Record can remove a significant amount of payment, tax and transaction administration from a business.

But that does not mean every company selling internationally, launching subscriptions or expanding into new markets needs one.

The more important question is:

Who should actually be responsible for the sale to the customer?

For many established businesses, the company can remain the seller and Merchant of Record while using a payment service provider, gateway or acquirer to process payments.

For others — particularly some SaaS, software and digital-product businesses selling across multiple countries — using a third-party Merchant of Record can transfer responsibility for parts of the transaction such as payment processing, tax collection, refunds, disputes and local compliance.

This guide explains the difference and, importantly, when the additional Merchant of Record layer may not be necessary.

Quick Summary: Merchant of Record

• A Merchant of Record (MoR) is the entity taking responsibility for the transaction with the customer.
• Your own company can be the Merchant of Record. You do not necessarily need to outsource this role.
• A third-party MoR generally takes a wider role than a payment gateway, PSP or acquirer.
• The MoR model can be particularly relevant to businesses selling digital products, software or subscriptions internationally.
• A payment provider can process a transaction without becoming the seller to the customer.
• A Payment Facilitator (PayFac) simplifies payment acceptance and merchant onboarding but is not automatically the Merchant of Record for every transaction.
• Using an MoR can reduce operational complexity, but it can also affect cost, customer ownership, payment data, reporting, refunds and your ability to move providers later.
• Before choosing an MoR, establish exactly who contracts with the customer, who collects the money, who handles tax, who owns the payment relationship and what happens if you leave.

Find Your New Processor

What is a Merchant of Record?

A Merchant of Record is the entity responsible for the transaction made with the customer.

That distinction matters because accepting a payment and being responsible for the underlying sale are not necessarily the same thing.

For example, a business might sell software directly to a customer while a payment provider processes the card transaction.

In that arrangement, the software company may remain responsible for:

• the customer contract;
• the product or service being sold;
• applicable taxes;
• refund policies;
• customer complaints;
• chargeback exposure;
• regulatory obligations relevant to its service; and
• the commercial relationship with the customer.

The payment provider is providing the infrastructure used to accept the payment.

A third-party Merchant of Record arrangement goes further.

Depending on the contractual structure, the MoR may become the entity through which the customer transaction is made and may take responsibility for areas including payment acceptance, tax calculation and collection, refunds, disputes and transaction-level compliance.

The easiest way to understand Merchant of Record: who is selling?

Before comparing MoR providers, start with the commercial flow.

The practical question is therefore not simply:

“Which Merchant of Record provider should we use?”

It is:

“Do we want another company to sit within the commercial transaction at all?”

Merchant of Record vs payment service provider

A payment service provider helps a business accept payments.

Depending on the provider and arrangement, the PSP may supply:

• payment gateway technology;
• card processing;
• merchant acquiring;
• alternative payment methods;
• fraud tools;
• tokenisation;
• recurring payments;
• multi-currency acceptance;
• settlement;
• reporting; and
• other payment infrastructure.

Using a PSP does not necessarily transfer responsibility for the underlying customer sale.

For a conventional merchant relationship, the business generally remains responsible for its customer, product, tax position, refunds and wider commercial obligations while the PSP processes the payment.

This is one reason an established business should not assume that international growth automatically requires a Merchant of Record.

A sufficiently capable international PSP or acquiring structure may provide many of the payment capabilities required while allowing the business to retain the direct customer relationship.

Read our guide to local acquiring vs a global PSP when expanding into Europe.

Merchant of Record vs Payment Facilitator

A Payment Facilitator, usually shortened to PayFac, helps other businesses accept payments through payment infrastructure arranged by the PayFac.

This can simplify merchant onboarding because the underlying businesses may operate as sub-merchants within the PayFac structure rather than each building a conventional direct acquiring relationship from scratch.

However:

PayFac does not automatically mean Merchant of Record.

The important distinction remains who is responsible for the actual sale.

A platform can facilitate payments for its customers without becoming the seller of everything those customers sell.

Businesses comparing these models may also find our guide to Payment Facilitators and PayFac models useful.

Merchant of Record vs embedded payments

Embedded payments are also different.

A SaaS business or software platform can integrate payment functionality directly into its product while its individual business customers remain the merchants selling to their own customers.

The platform may provide:

• merchant onboarding;
• integrated checkout;
• payment reporting;
• recurring payments;
• commercial pricing;
• payment support; and
• a branded or white-label experience.

None of those features automatically makes the platform Merchant of Record.

For established SaaS businesses, the distinction is important because becoming part of the payments proposition does not necessarily mean becoming responsible for every underlying customer sale.

Read our guides to embedded payments for SaaS and software platforms and white-label merchant processing.

Merchant of Record vs marketplace payments

Marketplaces introduce another layer of complexity because several parties may exist within the same payment journey:

Buyer → marketplace → seller → payment provider → payout

The marketplace may control elements such as:

• customer checkout;
• seller onboarding;
• split payments;
• commissions;
• seller payouts;
• refunds;
• disputes;
• transaction reporting; and
• platform rules.

That does not mean every marketplace uses exactly the same Merchant of Record structure.

The legal seller, payment flow, seller agreements, tax position and provider arrangement need to be considered together.

For the payment side specifically, see our split payment gateway guide for marketplaces and platforms.

Find Your New Processor

When does a Merchant of Record make sense for SaaS?

SaaS and digital-product businesses are among the businesses most likely to consider a third-party MoR.

One reason is international expansion.

A software business selling subscriptions to consumers in multiple countries may need to consider:

• VAT, GST or sales tax;
• customer location;
• local tax registrations;
• payment methods;
• currencies;
• refund rules;
• disputes;
• fraud;
• recurring billing;
• invoicing; and
• local commercial requirements.

An MoR may consolidate some of these responsibilities into one commercial arrangement.

That can be attractive where the alternative is building significant internal tax, payments and transaction-management infrastructure.

However, businesses should compare the MoR model against the alternative:

remaining Merchant of Record themselves and building the appropriate PSP, acquiring, tax and operational infrastructure around their own business.

Does selling internationally mean you need a Merchant of Record?

No.

Many businesses sell internationally while remaining Merchant of Record themselves.

A business may use a global PSP, local acquiring, multiple acquiring relationships or other international payment infrastructure without outsourcing the underlying sale.

The decision becomes more relevant when the problem you are trying to solve extends beyond accepting the payment.

For example:

• managing tax registrations across many consumer markets;
• handling large numbers of international disputes;
• supporting local transaction requirements;
• reducing internal operational complexity;
• launching quickly into multiple jurisdictions; or
• avoiding building a large transaction-compliance function internally.

Who handles VAT and sales tax under a Merchant of Record model?

This depends on the legal structure, the type of product or service, customer location and jurisdiction.

For digital services in particular, the identity of the party making the supply can affect which business is responsible for accounting for VAT.

HMRC guidance distinguishes between simply processing a payment and operating a digital platform that is treated as making the supply.

This is why the contract matters.

Do not assume that inserting a payment provider into checkout automatically transfers tax responsibility.

Businesses considering an MoR for tax reasons should obtain appropriate tax advice on the specific countries, products and contractual structure involved.

Who handles refunds and chargebacks?

A third-party Merchant of Record commonly has greater involvement in refunds and disputes than a conventional payment processor.

However, businesses should not stop at the phrase:

“We handle chargebacks.”

Ask what that means commercially.

Establish:

• who responds to the dispute;
• who provides supporting evidence;
• who carries the financial loss;
• whether chargeback costs can be passed back to your business;
• how refund decisions are made;
• whether reserves or delayed payouts can apply;
• what fraud thresholds exist; and
• what happens if dispute levels increase.

The contractual allocation of the work and the contractual allocation of the financial risk are not necessarily the same thing.

Who owns the customer relationship?

This is one of the most important questions for an established business.

Before using a third-party MoR, understand what changes from the customer's perspective.

Ask:

• Who is identified as the seller at checkout?
• Whose name appears on invoices and receipts?
• What descriptor may appear on the customer's card statement?
• Who sends refund communications?
• Who handles payment-related customer support?
• Who controls transaction data?
• Who owns stored payment credentials?
• Who controls recurring billing?

A solution that removes operational work can still create commercial dependency.

What happens if you want to leave your Merchant of Record?

This should be assessed before signing the contract, not when the business eventually wants to migrate.

For subscription businesses in particular, ask:

• Can stored payment credentials be migrated?
• Are card details held in a portable vault?
• Are provider-specific tokens being used?
• Are network tokens involved?
• Who owns subscription records?
• Can recurring billing mandates move?
• What customer data can be exported?
• What happens to active refunds and disputes?
• Is there a migration or termination fee?
• How long will the outgoing provider support transition?

Payment portability can be particularly important for a subscription business with thousands of customers.

For more on this, read our guide to moving stored cards, tokens and recurring payments when changing provider.

Does a Merchant of Record reduce PCI DSS responsibilities?

It may reduce the amount of payment-card data your own systems need to handle, depending on the technical integration.

However, businesses should not assume that using an external provider automatically removes every payment-security responsibility.

PCI DSS applies to organisations that store, process or transmit cardholder data, as well as entities that can affect the security of the cardholder-data environment.

The exact scope therefore depends on how checkout, tokenisation, integrations and payment data are structured.

How much does a Merchant of Record cost?

There is no meaningful universal MoR price.

Commercial structures vary according to factors such as:

• transaction volume;
• transaction value;
• countries;
• currencies;
• payment methods;
• product type;
• refund levels;
• chargeback exposure;
• tax requirements;
• fraud risk;
• support requirements;
• payout arrangements; and
• the services included within the MoR proposition.

The right comparison is therefore not simply:

MoR fee vs PSP transaction fee.

A more useful commercial comparison is:

For larger businesses, percentage-point differences in payment economics can become significant at scale.

Compare the total commercial model, not only the headline rate.

When might you NOT need a Merchant of Record?

A third-party MoR may add little value if your business:

• operates mainly in one or a small number of markets;
• already has appropriate tax infrastructure;
• wants direct control of the customer relationship;
• has an established payments team;
• already manages refunds and disputes effectively;
• has a strong direct acquiring or PSP relationship;
• requires highly customised payment infrastructure;
• wants control over payment routing;
• wants to negotiate acquiring economics directly; or
• places a high value on payment-data portability.

In those situations, the better solution may simply be a more capable payment provider rather than a completely different Merchant of Record model.

Merchant Advice Service view

Do not start with the provider category. Start with the responsibility you are trying to outsource.

If the problem is simply that your existing payment provider cannot support your currencies, integrations, subscription model or international growth, changing PSP or acquiring structure may solve it.

If the problem is that the business does not want to build the tax, dispute and transaction infrastructure required to sell directly across multiple markets, a Merchant of Record becomes much more relevant.

For established businesses, we would define the desired operating model first:

Customer → seller → checkout → payment provider → acquiring → settlement → tax → refunds → disputes

Then determine which parts of that chain the business wants to own.

What should you ask a Merchant of Record provider?

Before signing an agreement, establish:

1. Who is legally contracting with the customer?
2. Which transactions will the MoR cover?
3. Which countries and currencies are supported?
4. Which taxes does the provider calculate, collect and remit?
5. Who carries chargeback and fraud losses?
6. How are refunds handled?
7. Who owns transaction and customer data?
8. Can stored payment credentials be migrated?
9. How and when are funds paid to your business?
10. Can reserves or payout delays be applied?
11. What happens if the business grows significantly?
12. What are the total transaction and non-transaction costs?
13. What happens when the contract ends?

Merchant of Record or new payment provider?

For some businesses, Merchant of Record is exactly the right model.

For others, it is solving a problem that could be addressed more simply through:

• a different PSP;
• direct acquiring;
• local acquiring;
• multiple acquirers;
• an acquirer-agnostic gateway;
• embedded payments;
• a PayFac model;
• better tax infrastructure; or
• a redesigned payment integration.

If you are comparing the wider market, read our guide to comparing UK payment providers.

Businesses with bespoke payment infrastructure should also read our enterprise guide to changing payment provider with a custom API.

Find Your New Processor

Sources & further reading

• HM Revenue & Customs — VAT rules for supplies of digital services to consumers, including digital platforms, gateways and marketplaces.
• PCI Security Standards Council — PCI Data Security Standard (PCI DSS).
• Stripe — Merchant of Record guidance and Merchant of Record vs Payment Facilitator explanations.

Important: Merchant of Record structures can have tax, contractual, regulatory and legal implications that vary by business model and jurisdiction. This article provides general payments information and is not legal or tax advice. Businesses should obtain appropriate professional advice before changing the entity responsible for customer transactions.

Related Merchant Advice Service guides

• Compare UK Payment Providers
• Embedded Payments for SaaS & Platforms
• White-Label Merchant Processing
• Local Acquiring vs Global PSP for European Expansion
• Changing Payment Provider With a Custom API
• Moving Stored Cards, Tokens & Recurring Payments
• Split Payment Gateways for Marketplaces & Platforms

Disclosure: Merchant Advice Service is an independent UK business-to-business payments information, comparison and provider-matching service. MAS may receive a referral fee or commission from a partner if an introduction results in a completed account, product or service. This does not affect our editorial approach or the information provided in this guide. Provider suitability depends on the individual business and remains subject to the provider's own underwriting, pricing and terms.