How Merchant of Record (MoR) Works
When a buyer completes a purchase, several entities may be involved behind the scenes — the platform, the actual seller, a payment processor, and a bank. The Merchant of Record is the single entity that the card networks, tax authorities, and the buyer's bank recognize as the legal seller. Understanding the step-by-step flow clarifies exactly where liability sits at each stage.
Buyer initiates checkout
The end customer selects a product or service and proceeds to pay. The checkout UI may be branded by the underlying seller, but the legal counterparty completing the sale is the MoR.
MoR captures payment
The merchant account used to authorize and capture funds belongs to the MoR, not the seller. The acquirer settles funds into the MoR's account.
Tax calculation and collection
At the point of sale, the MoR determines the applicable tax rate — VAT, GST, or US sales tax — based on the buyer's location and the product type. The correct tax amount is added to the transaction and collected from the buyer.
Revenue disbursement to seller
After deducting its fees and the applicable taxes, the MoR remits the net revenue to the underlying seller on an agreed schedule — typically weekly or monthly.
Tax remittance and compliance filing
The MoR registers with tax authorities in each applicable jurisdiction, files periodic returns, and remits collected taxes. The seller has no direct obligation to those tax bodies.
Chargeback and dispute handling
If the buyer disputes a charge, the chargeback is issued against the MoR's merchant account. The MoR manages the dispute process and may recover losses from the seller depending on the contract terms.
Why Merchant of Record (MoR) Matters
The global digital goods market is expected to exceed $500 billion by 2027, with cross-border transactions representing a growing share of that volume. Managing tax obligations across 80+ countries and maintaining compliant payment operations is one of the largest operational burdens for software and ecommerce businesses expanding internationally.
Research from Stripe and Paddle consistently shows that tax compliance is the top barrier to international expansion for SaaS companies, with 62% of software vendors citing it as a primary obstacle. A third-party MoR removes that barrier almost entirely — the seller plugs into an existing compliance infrastructure rather than building one. For marketplace operators, this is even more critical: a 2023 survey found that marketplaces using a third-party MoR launched in new markets 3.4× faster than those managing compliance internally.
Regulatory pressure is increasing
The EU's VAT in the Digital Age (ViDA) reform, effective 2025, extends real-time digital reporting requirements to all cross-border B2C digital sales. Sellers without a robust MoR or in-house compliance stack face significant filing risk.
Merchant of Record (MoR) vs. Payment Facilitator
These two models are frequently confused because both involve intermediaries processing payments on behalf of other businesses. The distinction is legal depth: a payment facilitator handles transaction processing; an MoR handles the entire legal relationship with the buyer.
| Dimension | Merchant of Record | Payment Facilitator |
|---|---|---|
| Legal seller to buyer | Yes — MoR appears on statement | No — sub-merchant is the seller |
| Tax liability | MoR collects and remits taxes | Sub-merchant handles taxes |
| Chargeback liability | MoR absorbs disputes | Sub-merchant holds primary risk |
| Merchant account | MoR's master account | PayFac's master account |
| Seller onboarding speed | Fast — seller has no licensing burden | Fast — but seller retains compliance |
| Seller control over pricing | Lower — MoR sets fee structure | Higher — merchant sets prices |
| Ideal for | SaaS, digital goods, global marketplaces | Gig economy platforms, service marketplaces |
Types of Merchant of Record (MoR)
Not every MoR arrangement looks the same. Sellers should understand the model variants before committing to a provider.
Full-service third-party MoR — Companies like Paddle, Lemon Squeezy, and FastSpring act as the legal seller for the entire transaction. The software vendor integrates an API or embeds a checkout widget. The MoR owns the customer billing relationship, issues invoices, and manages all taxes globally. Best for early-stage SaaS companies with no existing compliance infrastructure.
Marketplace MoR — Large platforms such as the Apple App Store, Google Play, and Steam act as the MoR for every transaction on their platform. Independent developers receive a revenue share but have zero tax or chargeback liability. The tradeoff is low margin and limited pricing control.
Self-managed MoR — Larger merchants build their own MoR capability by obtaining payment licenses, registering for VAT/GST in target markets, and managing merchant accounts directly. This maximizes margin and control but requires dedicated legal, finance, and engineering teams. Feasible at significant transaction volume (typically >$10M ARR).
Hybrid MoR — Some businesses use a third-party MoR for international markets while acting as their own MoR in their home market. This balances compliance coverage with cost optimization.
Best Practices
Choosing and operating within an MoR arrangement requires discipline on both the commercial and technical sides.
For Merchants
- Audit coverage before signing. Verify that the MoR is registered for taxes in every market you sell to. Gaps in VAT or GST registration in key markets expose your business even when you use a third party.
- Understand the fee structure fully. MoR providers typically charge a percentage of revenue plus a per-transaction fee. Model your blended cost across your product catalog and average order value before committing.
- Negotiate chargeback liability caps. Some MoR contracts allow excessive chargebacks to trigger clawbacks or service termination. Establish clear thresholds and dispute-resolution SLAs in writing.
- Map the customer communication flow. Buyers will see the MoR's name on their bank statement. Ensure the MoR supports co-branded receipts or recognizable descriptors to reduce friendly fraud and customer confusion.
- Plan for data residency. The MoR holds payment and tax data for your customers. Confirm the provider's data residency and retention policies align with GDPR, CCPA, or other applicable regulations.
For Developers
- Use the MoR's official SDK or API rather than building raw integrations. MoR platforms iterate quickly on tax logic; using official libraries ensures updates propagate automatically.
- Implement webhook listeners for all payment events. Subscription renewals, refunds, and chargeback notifications from the MoR should update your internal billing system in real time to avoid entitlement mismatches.
- Test with sandbox transactions across multiple tax jurisdictions. Validate that tax amounts, invoice formats, and currency rounding match the MoR's production behavior before going live.
- Store the MoR's transaction IDs. Cross-referencing the MoR's transaction identifiers with your internal order IDs is essential for dispute resolution and reconciliation.
Common Mistakes
Assuming the MoR eliminates all compliance obligations. Even with a third-party MoR handling taxes and chargebacks, sellers remain responsible for product compliance, export controls, sanctions screening, and consumer protection laws in their markets.
Selecting an MoR based on price alone. Low transaction fees may mask limited tax coverage, poor dispute support, or weak uptime SLAs. The cost of a compliance gap or a service outage during peak sales far exceeds the savings from a lower fee.
Failing to reconcile MoR payouts against internal revenue records. MoR disbursements reflect deductions for taxes, fees, chargebacks, and reserves. Without a systematic reconciliation process, revenue recognition errors and audit exposure accumulate quickly.
Not reviewing contract exit terms before signing. Migrating away from a third-party MoR requires updating payment flows, re-establishing tax registrations, and notifying buyers of statement descriptor changes. Evaluate exit clauses, data portability, and migration support before committing.
Conflating MoR with a payment gateway. Some merchants integrate an MoR's checkout widget while also running a separate gateway for other payment flows, creating duplicate fee structures and inconsistent compliance coverage. Clarify the scope of the MoR relationship and eliminate redundancy.
Merchant of Record (MoR) and Tagada
Payment orchestration and MoR arrangements intersect directly: orchestration platforms manage routing, fallback, and optimization across multiple processors, while an MoR determines which legal entity owns each transaction. Tagada's orchestration layer sits upstream of the MoR relationship — enabling merchants to route transactions intelligently while the MoR handles compliance and liability.
Orchestrate around your MoR
If your MoR supports multiple payment methods or regional processors, Tagada can orchestrate fallback routing and authorization optimization on top of the MoR's infrastructure — improving approval rates without changing the legal structure of your transactions. This is particularly effective for high-volume SaaS businesses selling across Europe and APAC.