Merchant of Record vs Payment Facilitator: A Technical Breakdown
Merchant of Record vs Payment Facilitator: two models, often confused
The Merchant of Record vs Payment Facilitator question comes up constantly because both terms describe entities that sit between a buyer and an underlying merchant in a payment flow. They share enough surface area to be regularly confused.
Structurally, they're different. Different legal liability. Different regulatory burden. Different operational scope.
Getting the Merchant of Record vs Payment Facilitator distinction right matters because choosing the wrong model creates either compliance gaps or unnecessary complexity.
Payment Facilitator (PayFac) defined
A Payment Facilitator is a master merchant that aggregates many sub-merchants under its own merchant identification number (MID). Examples: Stripe, Square, PayPal, Adyen for Platforms.
The PayFac onboards the sub-merchants, handles KYC/AML, and processes their card transactions. The sub-merchants are the actual sellers. They own the customer relationship, they own the product, and they're legally accountable for the sale.
What the PayFac does:
- Aggregates payment processing under one MID
- Handles fraud detection and chargeback workflow at the platform layer
- Pays out to sub-merchants on a schedule
- Maintains PCI-DSS compliance for the payment infrastructure
What the PayFac does NOT do:
- Sell the product
- Issue invoices for the underlying transaction
- Collect or remit sales tax / VAT (the sub-merchant does)
- Carry product liability or warranty obligations
Merchant of Record (MoR) defined
A Merchant of Record is the legal entity that sells the product. They are the seller in the transaction. The product is sold under their legal name.
What the MoR does:
- Sells the product under its own legal name
- Issues invoices in its name
- Collects and remits transaction taxes (VAT, sales tax, GST) under its tax registration
- Carries product liability under consumer protection law
- Owns the merchant relationship with card networks
- Handles refunds, chargebacks, and customer disputes as the seller
The MoR can also be the PayFac (rare), use a PayFac for processing (common), or have a direct merchant account with an acquirer (also common).
Merchant of Record vs Payment Facilitator: the four key differences
1. Who is the legal seller?
PayFac: the sub-merchant. The PayFac is the payment platform.
MoR: the MoR itself. The MoR's name is on the receipt.
2. Who handles tax collection and remittance?
PayFac: the sub-merchant. The PayFac just processes the money.
MoR: the MoR itself. The transaction is on the MoR's tax registration.
3. Who carries product liability and warranty?
PayFac: the sub-merchant.
MoR: the MoR.
4. Regulatory burden on the PayFac/MoR provider
PayFac: PCI-DSS, money transmitter laws, KYC, AML, card network rules.
MoR: all of the above PLUS sales tax registration in every operating market, EPR compliance for relevant categories, product safety, importer of record obligations.
The MoR carries strictly more regulatory burden. Which is the structural reason MoR providers cost more than payment-only providers.
Merchant of Record vs Payment Facilitator: when to use each model
Use a PayFac when:
You have your own legal entity in every market you operate. You want to use a payment platform to handle the processing layer. You're fine being the legal seller, the tax-registered entity, and the customer-facing brand. Most direct ecommerce setups fit this profile when the brand has its own infrastructure.
Use a MoR when:
You don't have legal entities in your target markets. You don't want to register for VAT in 5+ countries. You want a partner to be the seller of record so you can avoid the local registrations and tax obligations. Cross-border expansion is the typical fit.
Can you use both?
Yes. The MoR (e.g. eBrands) is the legal seller. Underneath, the MoR uses a PayFac (e.g. Adyen, Stripe) to process the actual card transactions. The customer sees the MoR on the receipt. The MoR uses the PayFac for the technical payment layer.
Cost comparison
Pure PayFac fees: 2.5-3.5% on transactions plus per-transaction fees. That's it.
MoR fees: Higher than that, because the MoR is also providing tax compliance, regulatory work, and seller-of-record liability. Typical MoR pricing for consumer goods runs 6-10% commission on revenue plus a monthly retainer, plus channel/market setup fees.
Comparing the rate cards directly is misleading. A PayFac at 3% doesn't include the cost of running tax registrations, EPR compliance, customs accounts, customer service, and channel operations in 5+ countries. Which can easily run €100K-€300K per market in standalone setup costs.
The Merchant of Record vs Payment Facilitator confusion: thinking Stripe is a MoR
Stripe markets itself in some contexts as offering MoR-like services (Stripe Atlas for company formation, Stripe Tax for tax calculation, Stripe Connect for sub-merchant management). It's still primarily a PayFac, not a MoR. Stripe doesn't take on legal seller responsibility for your transactions.
If you need a true MoR. One that becomes the legal seller in your markets. You need a different provider. Here's a comparison of 11 MoR providers, sorted by what they actually cover.
For physical goods brands specifically: why SaaS-focused MoRs (Paddle, Stripe Tax, Lemon Squeezy) don't fit consumer goods.
