What Is a Merchant of Record? Guide for Marketplaces & Retailers
.png)
May 25, 2026
.png)
Key Takeaways (TL;DR)
- What is a merchant of record: The merchant of record (MoR) is the legal entity responsible for processing a customer's payment, and with that comes liability for tax collection, regulatory compliance, chargebacks, refunds, and fraud.
- It's not just a payment concept: In distributed retail, the merchant of record question determines who owns the customer relationship, the checkout experience, and the financial accountability across a multi-supplier network.
- Two models exist: The retailer or marketplace operator acts as its own MoR (maintaining full control but absorbing all liability), or a third-party MoR assumes those responsibilities on behalf of the seller.
- For marketplace operators, this is a structural decision: Whether the platform or the supplier holds MoR status determines how tax liability, chargebacks, and compliance are distributed across the network.
- Key merchant of record responsibilities: payment processing, tax calculation and remittance, PCI-DSS compliance, fraud management, and chargeback resolution.
- Carro's role: Holding platform-as-MoR status requires infrastructure that most teams don't build in-house. Carro is the dropship platform and supplier orchestration layer that makes it operationally viable, handling the supplier-side complexity (real-time inventory sync, automated order routing, supplier payouts, and fulfillment tracking) so the platform can hold MoR status without building that infrastructure from scratch.
Table of Contents
- What Is a Merchant of Record: at a Glance
- Merchant of Record Definition: What It Actually Means?
- Merchant of Record Responsibilities: The Full Scope
- Merchant of Record vs. Seller of Record vs. Payment Service Provider
- Who Should Be the Merchant of Record in a Marketplace?
- The Distributed Retail Problem: Why MoR Status Gets Complicated?
- What Happens When the Supplier Holds MoR Status?
- What Happens When the Platform Holds MoR Status?
- Merchant of Record Responsibilities: Tax and Compliance in Practice
- The Cost of Getting MoR Status Wrong
- Operationalize the MoR Decision with Carro
- Everything You Need to Know About a Merchant of Record
- FAQs About What Is a Merchant of Record
What Is a Merchant of Record?: at a Glance
What Is a Merchant of Record?
The merchant of record is a legal entity that sells goods or services to an end customer. That sentence sounds simple. The implications are not. When a payment is processed, someone has to own the transaction. That ownership carries with it the obligation to collect and remit the correct sales tax or VAT, maintain PCI-DSS compliance, handle chargebacks and refunds, manage fraud, and answer to regulators if something goes wrong.
That entity, whatever it is, is the merchant of record. For most single-vendor retailers, this question answers itself: the retailer is the MoR. They sell the product, collect the money, and manage every obligation that follows.
In distributed retail, where a single storefront sells products fulfilled by dozens or hundreds of brand and supplier partners, the question becomes far more consequential. The merchant of record designation in this model is not a technicality. It is the decision that determines how liability, compliance, and customer accountability are structured across the entire network.
Every time a customer checks out, they are transacting with whoever holds MoR status. That entity's name may appear on the bank statement. That entity is responsible for the tax collected on the sale. That entity absorbs the chargeback if the transaction is disputed. In a marketplace with 200 suppliers, that question, "who is the MoR?", shapes the entire operating model.
Merchant of Record Responsibilities
Now that we've got a hang of what a merchant of record is, let's take a look at some of the key functions and responsibilities it is usually associated with.
It must be noted that a merchant of record's responsibilities often span far more than just payment processing. Most descriptions of the MoR role focus on the payment layer, which is accurate but incomplete, especially for marketplace operators who need to understand what they're absorbing when they take on MoR status across a distributed supplier network.
Here's a comprehensive scope of responsibilities relevant to an MoR:
Payment Processing and Settlement
The MoR maintains the merchant account, accepts payments across all supported methods, handles currency conversion for international transactions, and manages the settlement flow from the customer payment to the supplier payout. In a multi-supplier marketplace, this means every transaction, regardless of which supplier fulfilled the order, settles through the MoR's account structure.
Tax Calculation, Collection, and Remittance
This is the merchant of record responsibility that causes the most operational pain at scale. The MoR is required to calculate the correct tax rate at the point of sale based on the buyer's location, collect it, and remit it to the appropriate tax authority.
In the US, this means navigating 13,000+ taxing jurisdictions across 45 states that levy sales tax. Internationally, it means managing VAT registration thresholds, GST obligations, and country-specific digital services taxes. The MoR, not the supplier or the customer, is liable if any of this is miscalculated or unremitted.
According to TaxJar, a merchant of record operating across multiple jurisdictions will often be over the economic nexus threshold in more states and countries than the underlying business would be on its own, simply because it is aggregating transaction volume across many sellers. This expands the compliance surface area significantly.
PCI-DSS Compliance
The MoR is responsible for maintaining the security standards that govern how payment card data is handled, stored, and transmitted. PCI-DSS v4.0 became fully enforceable in March 2025, and compliance requires ongoing security updates, regular audits, and a defensible posture against card data breaches. This is not a one-time certification, but a continuous operational obligation.
Fraud Prevention and Chargeback Management
When a fraudulent transaction occurs, or when a legitimate customer disputes a charge, the merchant of record is the entity that absorbs the liability and manages the resolution.
In practice, this means maintaining fraud detection systems, building chargeback response workflows, managing relationships with card networks and acquiring banks, while also absorbing the financial exposure from disputes that aren't resolved in the MoR's favor.
For marketplace operators, this obligation compounds with scale. Each additional supplier adds transaction volume. Each incremental transaction adds chargeback exposure. Managing this at the network level, rather than supplier by supplier, is both the challenge and the advantage of holding centralized MoR status.
Regulatory Compliance
Beyond tax, the MoR must comply with financial regulations that vary by region: anti-money laundering (AML) requirements, know-your-customer (KYC) rules, GDPR in the EU, CCPA in California, and consumer protection laws that vary by jurisdiction. As marketplaces expand geographically, each new market adds a layer of regulatory obligation that sits on the MoR's balance sheet of risk.
Merchant of Record vs. Seller of Record vs. Payment Service Provider
These three terms are frequently conflated, and the confusion has real operational consequences. The merchant of record is the entity responsible for the transaction. It processes the payment, collects the tax, handles compliance, and absorbs the financial liability. The MoR's name appears on the buyer's bank statement. The MoR answers to regulators.
The seller of record (SoR) is the entity legally responsible for the product or service being sold. This is typically the brand or supplier. The SoR owns product liability: if the product causes harm, the SoR carries that exposure. In many distributed retail arrangements, the supplier is the SoR while the platform is the MoR. These are separate designations, and they can be held by different entities simultaneously.
A payment service provider (PSP), like Stripe, Adyen, or Braintree, processes the payment. It does not assume legal liability for the transaction. A PSP is a technology and banking intermediary: it does not collect tax, manage compliance, or absorb chargeback risk on the seller's behalf. The business using the PSP remains the MoR.
The key distinction that matters for marketplace operators: using a PSP does not transfer MoR status. The platform that integrates Stripe and uses it to process transactions across 200 suppliers is still the merchant of record for every one of those transactions. The PSP has no liability for the tax that wasn't collected in New Mexico.
Who Should Be the Merchant of Record in a Marketplace?
This is the question that most MoR content skips past, and it is the most operationally consequential decision a marketplace operator makes. There are two models. The platform holds MoR status, or the suppliers hold MoR status. In practice, there is a third hybrid model, but it is operationally fragile. Each has different implications for customer experience, compliance exposure, and operational complexity.
The decision is not primarily a financial one. It is a question of control. Who owns the checkout? Who owns the tax liability? Who owns the customer relationship at the moment of transaction? The answers to those questions should drive the MoR designation, not the other way around.
For most marketplace operators building towards a unified customer experience, the answer is clear: the platform should hold MoR status. The why and what of this status is explained in detail in the next section.
The Distributed Retail Problem: Why MoR Status Gets Complicated?
Distributed retail is a commerce model where inventory, fulfillment, and distribution are decentralized, but the customer experience is intended to be unified. This is the model Carro is built around: inventory lives across a supplier network, the operational complexity is absorbed by the infrastructure layer, and the customer experiences a single seamless checkout regardless of how many suppliers are behind it.
A buyer visits a single storefront, browses a curated assortment, and checks out. Behind that single checkout, the order might be fulfilled by three different suppliers across two countries.
The merchant of record question sits at the center of this model. The customer sees one checkout. They expect one tax line item, one transaction on their bank statement, one return process. The complexity of who owns what in the supplier network is invisible to them, and should remain so.
If the platform holds MoR status, that unified experience is achievable. Every transaction flows through the platform's payment and compliance infrastructure. Tax is calculated and collected centrally. The customer transacts with the platform.
If each supplier holds their own MoR status, the unified experience breaks. Each supplier calculates their own tax. Each supplier processes their own payment. The customer may see three separate transactions on their bank statement from three suppliers they have never heard of. The "single storefront" experience is an illusion.
This is the core insight that most merchants of record discussions miss: in distributed retail, MoR status is not just about tax and compliance efficiency. It is about whether the marketplace operator can actually control the customer experience. Complexity is distributed. The experience must be unified. That unification requires the platform to hold MoR status.
What Happens When the Supplier Holds MoR Status?
In a supplier-as-MoR model, each brand or supplier in the network maintains their own merchant accounts, collects their own tax, and processes their own payments for orders that route through the platform.
On the surface, this appears to reduce platform liability. The suppliers carry their own compliance obligations. The platform is not absorbing tax risk across the network.
In practice, the tradeoffs are significant.
- Customer experience degrades: The buyer sees the supplier's name on their bank statement, not the platform. Returns and refunds route to the supplier, not a centralized customer service operation. The platform cannot guarantee a consistent checkout experience because each supplier controls their own.
- Tax compliance remains fragmented: Each supplier applies its own tax logic, which may be incorrect or inconsistent. The platform has no visibility or control over whether the correct tax is being collected on transactions it is facilitating. In US states with marketplace facilitator laws, the platform may still bear secondary liability even when suppliers are nominally the MoR.
- Settlement is uncoordinated: The platform cannot enforce payment SLAs, manage payout timing, or reconcile financial performance across the network with any precision. Each supplier's settlement is a separate stream.
- Growth becomes operationally fragile: As the supplier network grows, each new supplier brings their own payment infrastructure, tax configuration, and compliance posture. The platform has no ability to standardize or audit this at scale.
The supplier-as-MoR model makes sense in two narrow contexts: very early-stage marketplaces where the platform has not yet built payment infrastructure, and pure-play B2B marketplaces where buyers expect to transact directly with suppliers. For consumer-facing marketplaces competing on experience, it is not sustainable.
What Happens When the Platform Holds MoR Status?
When the marketplace operator holds merchant of record status, every transaction in the network flows through a single legal and financial entity. The platform collects the payment. The platform calculates and collects tax. The platform manages chargebacks and fraud. The platform settles net amounts to suppliers after deductions.
The customer always transacts with the platform. The supplier network is invisible to the buyer. This model enables what distributed retail requires: a unified experience built on top of a distributed operational reality.
The operational requirements are significant, but they are manageable as infrastructure rather than ad hoc obligations:
- Payment infrastructure must handle multiple suppliers, currencies, and payout schedules from a single settlement architecture. The platform needs a merchant account capable of processing the full transaction volume, not individual supplier-level accounts.
- Tax compliance must be centralized. The platform calculates, collects, and remits tax for every transaction across every jurisdiction where it has nexus, regardless of which supplier fulfilled the order. This is a genuine compliance operation, not a checkbox.
- Chargeback management operates at the network level. When a buyer disputes a charge, the platform resolves it, drawing on supplier-level fulfillment data to build the dispute response. The supplier is accountable to the platform for fulfillment; the platform is accountable to the card network for the transaction.
- Supplier payouts flow from the platform after reconciliation: net of fees, returns, and adjustments. This creates a financial settlement layer that the platform must operate with precision and at scale.
Holding MoR status in a distributed retail model is an operational commitment. The question is not whether it is worth taking on; for consumer-facing marketplaces, it is the only model that preserves the customer experience. The question is what infrastructure exists to make it operationally viable.
Merchant of Record Responsibilities: Tax and Compliance in Practice
Tax compliance is the merchant of record responsibility most likely to create unexpected liability for marketplace operators who are scaling quickly. In the United States, 45 states levy sales tax, and economic nexus thresholds, the point at which an out-of-state seller must collect and remit tax, vary by state.
The South Dakota v. Wayfair decision in 2018 established that a business can trigger tax obligations in a state based solely on the volume of sales there, without any physical presence. A marketplace that crosses the $100,000 in sales or 200 transaction threshold in a given state has nexus there, and is required to register, collect, and remit.
For a platform-as-MoR, this applies to the aggregate transaction volume across all suppliers. A marketplace processing $5M in GMV annually may have nexus in 30 to 40 states. Each state requires its own registration, its own remittance schedule, and its own filing process.
Internationally, VAT registration thresholds vary by country. The EU's OSS (One Stop Shop) scheme simplifies this for EU-to-EU transactions, but cross-border sales from outside the EU into EU member states trigger their own registration requirements. Digital products and physical goods may be treated differently.
Marketplace facilitator laws add another layer. As of 2026, the majority of US states with sales tax have enacted marketplace facilitator legislation, which requires the platform facilitating the sale to collect and remit tax on behalf of third-party sellers. Even in a supplier-as-MoR model, the platform may be classified as a marketplace facilitator and required to collect tax regardless.
As per a leading payment solutions provider, a marketplace operator that sets terms or conditions for sales, processes customer payments, or handles ordering or delivery may qualify as a deemed seller in certain jurisdictions: an obligation that attaches to the platform irrespective of how the MoR designation is structured contractually between platform and supplier.
Getting this wrong carries consequences: back taxes, penalties, interest, and in some jurisdictions, personal liability for the business owner. The merchant of record designation is not an accounting preference, but a structural risk decision.
The Cost of Getting MoR Status Wrong
Most marketplace operators discover the MoR question in one of three ways: a tax audit, a chargeback dispute that escalates to the card network, or a compliance failure that surfaces during a financing or acquisition process. None of these are good times to learn that the MoR structure was not properly configured.
Tax Exposure Compounds Quietly
A marketplace that has been operating for two years without collecting tax in states where it has nexus has two years of uncollected tax liability sitting on its balance sheet.
When it surfaces, in an audit or during due diligence, the liability includes not just the principal but interest and penalties. State tax authorities have become more aggressive in pursuing marketplace facilitators since the Wayfair decision, and the statute of limitations is typically three to four years.
Chargebacks at Scale Are a Card Network Risk
When chargeback rates cross certain thresholds (1% for Visa, 1.5% for Mastercard's excessive programs), the acquiring bank faces consequences from the card network.
Banks pass that risk back to the merchant. A marketplace that does not manage chargebacks centrally, because suppliers are nominally handling their own disputes, may find itself facing account suspension or processing rate increases that affect the entire platform.
Compliance Gaps Affect Enterprise Partnerships and Financing
Investors and strategic partners conducting due diligence will examine the payment and compliance infrastructure. An MoR structure that is fragmented, undocumented, or reliant on suppliers' own compliance posture creates material risk flags. This is particularly acute for marketplace operators seeking Series A+ financing or exploring acquisition conversations.
The cost of cleaning up a poorly structured MoR arrangement post-hoc is significantly higher than building the right structure from the outset.
Operationalize the MoR Decision with Carro
For consumer-facing marketplaces, platform-as-MoR is the right structural choice. Making it operational requires infrastructure that most marketplace teams don't build in-house.
Carro (now powering Modern Dropship) is a dropship platform and supplier orchestration layer purpose-built for the distributed supplier model, not retrofitted from single-tenant tools. The operational layers that make platform-as-MoR viable are built into the platform's architecture rather than added on top of it. Adding suppliers doesn't require additional headcount or manual settlement workflows; the orchestration layer absorbs network complexity as supplier count grows.
Carro is built for US-based retailers and marketplace operators on Shopify, WooCommerce, BigCommerce, and Magento, and covers the full operational stack:
- Curated supplier network: Hand-matched introductions from a pool of over 1.5 million products, with suppliers evaluated for operational reliability before entering the network. Chargeback risk is reduced at the sourcing stage, not just managed after the fact.
- Real-time inventory sync: Live inventory positions across the supplier network prevent oversells at checkout rather than surfacing them in a support ticket.
- Automated order routing: Orders route to the correct supplier instantly, with SLA tracking and full fulfillment visibility: the data needed to defend a chargeback dispute.
- Financial settlement and supplier payouts: Automated reconciliation and net supplier payouts from a single source of truth, removing the manual operations that make MoR status expensive to hold at scale.
- Stack integration without replatforming: Native connections to existing commerce platforms, ERPs, and accounting systems. The operator's tax and payment infrastructure sits on top of Carro's supplier orchestration layer.
The FairGround scaled their supplier network without adding operational headcount. VYSN manages assortment across multiple platforms from one centralized place without operational friction. Both outcomes come from the same thing: infrastructure that absorbs supplier-side complexity so the platform can hold MoR status without the overhead that normally comes with it.
Book a demo with Carro to see how we help US-based marketplace operators operationalize distributed retail. Most teams are live within a few weeks, with no custom development required.
Everything You Need to Know About a Merchant of Record
FAQs About What Is a Merchant of Record
What is a merchant of record in simple terms?
A merchant of record is the legal entity that officially sells goods or services to a buyer. The MoR collects the payment, calculates and remits tax, handles refunds and chargebacks, and assumes regulatory liability for the transaction. In a marketplace, this is typically the platform, not the individual supplier, though the contractual arrangement can vary.
What are the main responsibilities of a merchant of record?
Merchant of record responsibilities include processing all customer payments, calculating and remitting sales tax or VAT to the relevant tax authorities, maintaining PCI-DSS compliance for payment card data, managing fraud detection and chargeback resolution, and complying with financial regulations in each jurisdiction where the MoR operates. In a multi-supplier marketplace, these obligations apply across every transaction in the network, regardless of which supplier fulfilled the underlying order. The MoR cannot delegate these obligations to suppliers without formally transferring MoR status.
What is the difference between a merchant of record and a payment service provider?
A merchant of record assumes legal and financial responsibility for a transaction, including tax, compliance, chargebacks, and fraud liability. A payment service provider (PSP) processes the payment but does not assume any of that liability. If a business uses Stripe to process payments, Stripe is the PSP, but the business remains the merchant of record and retains full tax and compliance obligations. The distinction matters because many marketplace operators assume that integrating a PSP transfers liability; it does not.
What is a marketplace facilitator, and how does it relate to the merchant of record?
A marketplace facilitator is a platform that facilitates sales between third-party sellers and buyers and is legally required to collect and remit tax on those transactions under marketplace facilitator laws. As of 2026, most US states with sales tax have enacted these laws. The merchant of record designation is a payment network and contractual concept; marketplace facilitator status is a tax law concept. A marketplace can be classified as a marketplace facilitator by state tax authorities even if the contractual MoR designation is the supplier. Both designations carry real obligations, and they can apply simultaneously.
What is the difference between a merchant of record and a seller of record?
The merchant of record is responsible for the transaction: payment, tax, compliance, and financial liability. The seller of record is responsible for the product: ownership, product liability, and the legal right to sell. In distributed retail, a marketplace platform is typically the MoR (it processes the payment and collects the tax), while the brand or supplier remains the seller of record (it owns the product and holds product liability). These are two separate legal designations that can be held by different entities at the same time.
What happens if a marketplace does not properly establish merchant of record status?
If merchant of record status is not properly established, the marketplace faces fragmented tax compliance, uncoordinated chargebacks, and a customer experience that breaks across supplier transactions. More concretely, unpaid sales tax from transactions in nexus states accumulates as a liability that compounds with interest and penalties, typically surfacing during a financing round, acquisition, or tax audit. In many US states, marketplace facilitator laws assign tax collection obligations to the platform regardless of how MoR status is contracted internally, meaning the platform may carry tax liability it was not accounting for.
Is the merchant of record always the same as the company the customer buys from?
Not always. In a third-party MoR model, the customer buys from a branded storefront, but the merchant of record processing the transaction is a different legal entity. The buyer may see the third-party MoR's name on their bank statement rather than the brand they purchased from. In distributed retail marketplaces, the platform typically holds MoR status and appears as the transaction entity, while the actual product comes from a supplier. The brand and the MoR are the same entity only when a retailer sells directly and has built or contracted its own payment and compliance infrastructure.
Related Posts
.png)
.png)
.png)
