Merchant of Record
What Is a Merchant of Record? Definition and How It Works
Definition
A Merchant of Record (MoR) is the legal entity named on the consumer's payment transaction. The MoR accepts the payment, assumes liability for the sale, manages tax collection and remittance, and bears chargeback and compliance responsibility.
How it works
The Merchant of Record concept defines who is legally and contractually responsible for a consumer transaction. In a standard direct merchant model the merchant is their own MoR: they have a direct acquiring relationship, their name appears on the consumer's statement, and they are responsible for all obligations arising from the transaction including tax collection, compliance, chargebacks, refunds, and fraud liability.
In an MoR model a third-party company acts as the MoR on behalf of the actual seller. The MoR has the acquiring relationship, processes the payment, collects tax, and appears on the consumer's bank statement. The underlying seller receives revenue minus the MoR's fees and applicable taxes. This arrangement is common in software and digital goods distribution where the MoR handles the global tax and compliance complexity of selling digital products across multiple jurisdictions.
The MoR model has implications for chargebacks: the MoR bears primary chargeback liability and manages dispute resolution with the acquirer. The underlying merchant must contractually indemnify the MoR for disputes arising from their products or fulfilment failures.
Not all marketplace or platform models are MoR models. A marketplace that facilitates transactions but where the seller appears on the statement is not an MoR; it is a marketplace. A platform where the platform name appears on the statement and the platform is contractually liable is an MoR.
Why it matters
The MoR handles VAT/GST registration, collection, and remittance across all selling jurisdictions; underlying merchants are freed from cross-border tax compliance complexity. Chargebacks hit the MoR, not the underlying merchant; however the MoR will contractually flow back dispute costs through indemnification or holdbacks.
Merchants using an MoR do not need their own acquiring agreement, PCI compliance program, or direct acquirer relationship. MoR fees often exceed what a merchant with direct acquiring could achieve at scale; the convenience premium must be weighed against true cost of acceptance. The MoR's name on the consumer's statement rather than the merchant's name can cause consumer confusion increasing friendly fraud chargebacks.
With PXP
PXP works with merchants and platforms that operate direct acquiring models or transition from MoR arrangements to direct acquiring as their scale makes it cost-effective. PXP's platform handles the acquiring infrastructure and chargeback management that MoR platforms provide.
Frequently asked questions
What is the difference between a Merchant of Record and a Payment Facilitator?
A Merchant of Record (MoR) is the legal entity named on the consumer transaction. They are responsible for the sale, tax, and compliance. A Payment Facilitator (PayFac) is a specific acquiring model where a master merchant enables sub-merchants to accept payments under the PayFac's acquiring agreement. The PayFac is not necessarily the MoR for the underlying transaction. MoR and PayFac are related but distinct: an MoR may use a PayFac structure for acquiring, but being a PayFac does not automatically make an entity the MoR.
When does the MoR model make sense for a digital goods merchant?
The MoR model makes most sense for: digital goods merchants selling to consumers in many tax jurisdictions where per-country VAT/GST registration would require significant compliance overhead; early-stage companies that lack the scale to justify direct acquiring setup costs; and companies prioritising speed to market. As a merchant's volume grows the MoR fee differential versus direct acquiring becomes increasingly significant.
Who appears on the consumer's bank statement in an MoR arrangement?
In a true MoR arrangement the MoR's name, rather than the underlying seller's name, appears on the consumer's bank statement. This can cause recognition issues: consumers who don't recognise the charge may initiate a chargeback. MoR platforms mitigate this with statement descriptor conventions that include the product name alongside the MoR name.
Can a merchant be their own Merchant of Record and still use an MoR platform?
No. By definition if a merchant is their own MoR they accept the payment, collect the tax, and bear the compliance obligations. If they use an MoR platform then that platform is the MoR. Some merchants use hybrid models: they are the MoR in their primary market but use an MoR platform for expansion markets where the compliance overhead of direct registration is not yet justified.
Revolutionize your business with PXP
Take complete control of your commerce and payments with one platform.
Get Started