Merchant of Record: A Guide to Navigating Chargebacks
The MOR Model and Why It Creates Unique Chargeback Risk
The merchant of record is the entity that assumes legal and financial responsibility for a transaction at the point of sale. In practical terms, this means the MOR’s name appears on the cardholder’s statement, the MOR is liable for taxes and regulatory compliance, and the MOR absorbs chargeback liability when disputes arise.
For direct-to-consumer merchants operating their own accounts, that liability is self-contained. For MSPs managing portfolios of merchants, the MOR structure introduces a fundamentally different dynamic, particularly when a merchant is not the MOR of record for their own sales.
This arrangement is more common than it might appear. Platforms, marketplaces, software-as-a-service providers, and subscription businesses frequently operate through third-party MOR arrangements. A SaaS company may process payments through a reseller platform acting as the MOR. A marketplace vendor may never directly hold a merchant account at all. The transactions flow, but the liability chain between the seller, the MOR, and the acquirer can be opaque.
For MSPs, that opacity is a risk vector.
Why Chargebacks Don’t Follow Intuitive Lines
In a standard merchant account relationship, the chargeback process flows predictably. A cardholder disputes a transaction, the issuing bank initiates the chargeback, and the acquiring bank debits the merchant. Liability is clear, and dispute management responsibility sits with the merchant.
In a MOR arrangement, that clarity degrades. The entity whose name appears on the statement, the MOR, receives the chargeback. But the underlying transaction may have originated from a sub-merchant, a marketplace seller, or a third-party vendor who has no direct relationship with the acquiring bank and no mechanism to receive or respond to formal dispute notices.
The practical consequence: the MOR absorbs chargebacks from transactions it did not originate and may have limited visibility into. Sub-merchants generate disputes, but the MOR’s ratios take the impact. If the MOR is a PayFac or platform processing across hundreds or thousands of merchants, the aggregate exposure can be substantial.
MSPs who onboard MOR-based businesses without a clear understanding of the sub-merchant layer are inheriting that exposure indirectly. Portfolio chargeback ratios reflect activity at every level.
Where Dispute Volume Tends to Concentrate
Not all merchant categories carry equal risk under the MOR structure. Platforms and marketplaces that aggregate sellers operating in higher-risk verticals, including subscription services, digital goods, online travel, and nutraceuticals, can produce disproportionate dispute volumes relative to their transaction counts.
Several patterns recur. First, brand confusion: when a cardholder sees the MOR’s name on their statement rather than the name of the vendor they purchased from, unrecognized transaction disputes follow. Second, fulfillment disconnects: in multi-vendor environments, the MOR may have no direct knowledge of whether goods were shipped or services delivered, yet it receives the chargeback when a cardholder claims non-receipt. Third, subscription mechanics: platforms that manage recurring billing on behalf of sub-merchants frequently generate cancellation and authorization disputes when billing terms are unclear at the sub-merchant level.
Each of these patterns is addressable. But they require the MOR to have operational hooks into the transaction lifecycle, not just the payment infrastructure.
Liability Allocation and Contractual Exposure
One area that MSPs consistently need to pressure-test is the contractual allocation of chargeback liability between the MOR and its sub-merchants or platform partners. Agreements that do not explicitly define who bears dispute costs, who is responsible for representment, and what recourse exists when a sub-merchant becomes unresponsive create conditions for liability accumulation.
In the absence of clear contractual frameworks, chargebacks that originate at the sub-merchant level could potentially roll upward with no recovery mechanism. The MOR absorbs the loss. The acquirer absorbs the portfolio risk. The MSP inherits both.
This is not a hypothetical problem. It is a structural characteristic of the MOR model that requires active governance rather than passive assumption.
Chargeback Management in a MOR Environment
Managing chargebacks effectively under a MOR structure requires capabilities that go beyond standard alert subscriptions or manual review workflows.
At the dispute prevention layer, transaction clarity is critical. When cardholders cannot recognize a charge, disputes follow. Solutions that push enriched transaction and fulfillment data to cardholder banking apps and issuer call centers at the point of inquiry, before a dispute is formally filed, directly address the brand confusion problem. For MOR-based platforms, this kind of data sharing needs to be operationalized across every sub-merchant in the portfolio, not just at the MOR level.
At the alert management layer, the volume and velocity of disputes across a multi-merchant platform require consolidated, automated handling. Dispute alerts and chargeback alerts arriving across hundreds of sub-merchant transaction streams cannot be managed through fragmented processes. Centralized alert management with automated refund logic reduces response latency and prevents preventable chargebacks from reaching formal chargeback status.
At the representment layer, the evidentiary challenge in a MOR environment is meaningful. When the MOR did not originate the transaction, assembling compelling evidence, including proof of delivery, customer communication, and fulfillment records, requires integration with sub-merchant data sources. Automated data capture across connected ecommerce platforms and CRMs is a practical necessity at scale, not a convenience.
Card Network Monitoring Programs and the MOR
MSPs should be aware that card network monitoring programs evaluate chargeback and fraud performance at the MOR level, not at the sub-merchant level. This means that a platform processing across a broad seller base could potentially approach monitoring thresholds based on aggregate activity that no individual sub-merchant would generate on their own.
Visa’s VAMP program, for example, evaluates both the fraud-to-sales ratio and the non-fraud chargeback ratio against defined thresholds. A MOR operating at scale with insufficient dispute controls across its platform faces the compounding risk that activity distributed across many sellers aggregates into a single ratio that triggers network remediation. The consequences, including potential placement in a monitoring program, would fall on the MOR and, by extension, on the MSP’s portfolio performance.
Understanding this aggregation dynamic is important for MSPs when underwriting MOR-based merchants and when designing ongoing risk monitoring protocols.
What MSPs Should Evaluate When Onboarding MOR-Based Merchants
Due diligence for MOR-based merchants requires a materially different checklist than standard merchant onboarding. Several areas warrant close attention.
Sub-merchant composition is a foundational question. What industries do the sub-merchants operate in? What are the historical chargeback and dispute rates at the sub-merchant level? Does the MOR have visibility into that data, or does it operate with aggregated reporting only?
Contractual frameworks governing liability allocation between the MOR and its sub-merchants need direct review. A MOR with no enforceable recourse against sub-merchants generating excessive disputes is a concentrated liability risk.
Operational dispute management infrastructure, whether the MOR has functional alert integrations, an established representment process, and consistent monitoring in place, is as important as underwriting financials. A high-revenue platform with no dispute management infrastructure is a different risk profile than the raw transaction volume alone would suggest.
Chargeback history and trend data at both the MOR and sub-merchant level, where obtainable, provides the clearest signal.
The MSP’s Role in Structuring MOR Merchant Support
MSPs are positioned to add genuine value to MOR-based merchants precisely because the liability dynamics in this model tend to outpace what most platform operators anticipate. Dispute volumes that appear manageable at early scale can become a portfolio-level exposure when a platform matures and transaction volume grows.
Proactively equipping MOR-based merchants with integrated dispute management infrastructure, rather than waiting for ratio deterioration to surface, is both a risk mitigation strategy and a differentiating service offering. MSPs who can connect MOR clients to consolidated alert management, automated transaction transparency tools, and structured representment workflows provide a capability that most platform operators cannot build internally at the same level of reliability or network integration depth.
The merchant of record model is not inherently a liability. It is a structure that demands operational sophistication in proportion to the volume it carries. MSPs who understand that relationship, and who build their service offering around it, are better positioned to support MOR-based merchants sustainably.
Building a More Resilient MOR Portfolio
If your portfolio includes MOR-based merchants, or if you are evaluating onboarding platforms, marketplaces, or PayFac-adjacent businesses, the time to establish dispute management standards is before volume scales, not after ratios climb.
ChargebackHelp supports MSPs with integrated dispute management solutions designed for multi-merchant environments. From consolidated alert handling through RESOLVE to automated transaction transparency through DEFLECT and structured representment through RECOVER, we help MSPs build the operational infrastructure that MOR-based merchants require. If you would like to discuss how to structure chargeback management across your MOR portfolio, reach out to our team and we can walk through the right approach for your book of business.
Why ChargebackHelp?
ChargebackHelp offers a card-agnostic dispute management platform purpose-built for the operational complexity that MSPs manage at scale. Our solutions integrate Verifi CDRN, Ethoca Alerts, Visa RDR, Order Insight, and Consumer Clarity into a unified environment, enabling MSPs to deliver automated dispute management to their merchant portfolio without fragmented integrations or manual overhead. For MSPs supporting MOR-based merchants, that depth of integration translates directly into better portfolio performance, reduced monitoring program exposure, and a stronger service offering to merchant partners who need it most.
FAQs: Merchant of Record: A Guide to Navigating Chargebacks
Who is responsible for chargebacks in a merchant of record arrangement?
The merchant of record assumes primary liability for chargebacks, regardless of which sub-merchant or seller originated the transaction. This means the MOR’s chargeback ratios reflect aggregate dispute activity across all underlying merchants, even when the MOR had no direct role in fulfillment.
How does the MOR model affect a merchant’s chargeback ratio?
Because the MOR is the entity of record with the acquiring bank, all chargebacks from sub-merchant activity roll up into the MOR’s ratio. If sub-merchants generate elevated dispute volumes, the MOR’s ratio absorbs the impact. Consolidated dispute management across all sub-merchants is necessary to keep ratios within acceptable bounds.
What is the biggest operational risk for MSPs onboarding MOR-based merchants?
The most significant risk is insufficient visibility into sub-merchant dispute activity before it aggregates to a level that impacts the MOR’s ratios and triggers card network monitoring thresholds. MSPs who do not evaluate sub-merchant composition and dispute history during underwriting may inherit concentrated liability exposure.
Can MOR-based merchants use dispute alerts effectively?
Yes, but effective alert management at scale requires consolidation across all sub-merchant transaction streams. Individual alert subscriptions at the sub-merchant level are rarely sufficient when transaction volumes are significant. ChargebackHelp’s RESOLVE solution centralizes alert management into a single workflow, enabling MOR platforms to respond consistently and within required timeframes.
How does Visa’s VAMP program apply to merchant of record businesses?
VAMP evaluates chargeback and fraud performance at the entity level, which for a MOR means the aggregate of all sub-merchant activity. A platform whose individual sub-merchants each operate within acceptable limits could potentially breach VAMP thresholds at the MOR level if aggregate volume is sufficient. MSPs should model this aggregation dynamic when assessing MOR merchant risk.
What evidence challenges arise during representment for MOR-based chargebacks?
When the MOR did not originate the transaction directly, assembling compelling evidence requires access to sub-merchant fulfillment data, customer communication records, and order details. Without direct integration into sub-merchant data sources, representment quality can suffer. Automated data capture tools that connect to ecommerce platforms and CRMs help bridge this gap.
How should MSPs structure chargeback liability in MOR merchant agreements?
Agreements should explicitly define which party bears the cost of chargebacks and associated fees, who is responsible for representment, and what recourse the MOR has against sub-merchants generating excessive dispute activity. Without enforceable contractual terms, liability can accumulate at the MOR level with no recovery mechanism available to the MSP or the acquiring bank.
