Merchant of Record (MoR)

What Is a Merchant of Record?

A merchant of record (MoR) is the legal entity authorized to process a customer's payment for goods or services. When a customer checks their credit card or bank statement, the MoR's name is what appears next to the charge. More importantly, the MoR is the entity that card networks, tax authorities, and regulators hold accountable for the transaction.

Any business that sells directly to customers is, by default, its own merchant of record. But as commerce has gone global, the compliance burden of being an MoR has grown significantly: collecting and remitting sales tax or VAT across hundreds of jurisdictions, maintaining PCI DSS certification, handling chargebacks, and navigating fraud liability. This has created a market for third-party MoR services that assume these responsibilities on behalf of sellers.

The MoR model is distinct from the payment facilitator (PayFac) model. A PayFac like Stripe or Square simplifies payment acceptance, but the seller remains the legal entity responsible for tax compliance and disputes. An MoR like Paddle or FastSpring becomes the legal reseller, assuming full financial and regulatory liability for the transaction.

How It Works

When a third-party MoR handles a sale, two transactions occur simultaneously behind the scenes:

1. The customer pays the MoR directly. The MoR's name appears on the bank statement, and the MoR is the counterparty in any dispute.
2. The MoR purchases the product or service from the seller (the actual creator or vendor) and remits the proceeds minus fees, taxes, and any chargeback deductions.

From a legal perspective, the MoR is a reseller. It buys from you and sells to the customer. This structure is what allows the MoR to assume tax and compliance obligations: it is the legal seller, not merely a payment processor routing funds.

MoR Responsibilities

The merchant of record handles several critical functions:

• Tax calculation, collection, and remittance across all applicable jurisdictions (sales tax, VAT, GST)
• Chargeback management and primary financial liability for disputes
• Refund processing and customer payment support
• PCI DSS compliance and cardholder data security
• Fraud detection and prevention
• Regulatory compliance including KYC, AML, and data privacy laws (GDPR, CCPA)

MoR vs. Payment Facilitator vs. Payment Processor

These three models are often confused. The key distinction lies in who bears legal and financial responsibility for the sale:

MoR-as-a-Service Platforms

Several platforms offer MoR as a managed service, primarily targeting SaaS companies and digital product sellers who need global reach without building tax and compliance infrastructure:

• Paddle: full MoR for SaaS and software companies, handling tax remittance in over 100 jurisdictions, fraud protection, chargeback management, and subscription billing. Pricing is typically 5% + $0.50 per transaction.
• Lemon Squeezy: developer-focused MoR platform for digital products, with built-in global tax remittance, PCI-compliant checkout, and post-sale dispute handling.
• FastSpring: comprehensive ecommerce MoR processing payments in over 240 countries and territories, covering the full lifecycle from checkout to tax filing.

The trade-off with using an MoR service is clear: you give up control and margin in exchange for compliance coverage. MoR platforms typically charge 5-10% per transaction (compared to 2-3% for a standard payment gateway), and payout cycles are slower because the MoR must deduct taxes and fees before remitting funds to the seller.

When Platforms Are the MoR

Many large platforms act as the MoR for transactions on their marketplace:

• Apple App Store and Google Play Store process all payments, appear on customer statements, handle refunds and chargebacks, and manage tax compliance. Developers are the "seller of record" (SoR), responsible only for the product itself.
• Amazon Marketplace typically acts as MoR for third-party seller transactions. Amazon's name appears on credit card statements and Amazon handles disputes and data privacy obligations. Vendors remain responsible for inventory, fulfillment, and product compliance.

This split between MoR and SoR is common on large platforms. The MoR handles payment processing and financial liabilities, while the SoR handles customer service, delivery, and product quality.

Use Cases

SaaS and Digital Products

The most common MoR use case is software and digital product sales. A SaaS company selling subscriptions globally would need to register for VAT in every EU member state, collect and remit sales tax across U.S. states with economic nexus laws, handle GST in Australia and New Zealand, and manage dozens of other tax regimes. An MoR service eliminates this burden entirely.

Global Marketplace Commerce

Marketplaces connecting buyers and sellers across borders use the MoR model to simplify compliance. Rather than requiring every seller to handle tax registration and chargeback management independently, the marketplace (or its MoR partner) assumes these responsibilities centrally.

Crypto-to-Fiat Commerce

As more merchants accept cryptocurrency payments, the MoR role becomes particularly relevant. The IRS classifies all stablecoins as property rather than currency (Notice 2014-21), meaning that receiving stablecoins as payment is treated as ordinary income at fair market value at the time of receipt. Even minor price fluctuations between $0.99 and $1.01 must be tracked, and converting between stablecoins (for example, USDC to USDT) constitutes a taxable event.

Starting in 2026, brokers must report cost basis for crypto transactions under Form 1099-DA rules, and designated stablecoin sales exceeding $10,000 in aggregate require reporting. For businesses acting as their own MoR while accepting crypto, this compliance burden is substantial.

This is one area where Bitcoin merchant payment solutions and dollar-denominated Bitcoin payments are evolving: by settling transactions through stablecoins on fast Layer 2 networks like Spark, merchants can reduce settlement times and interchange fees while maintaining clear records for MoR tax obligations.

International Tax Compliance

One of the primary drivers of MoR adoption is the expanding global web of digital services taxes. Recent developments include:

• The Philippines enacted a 12% VAT on foreign digital services effective June 2025
• Chile introduced VAT withholding for non-resident digital vendors in January 2026
• Poland is mandating its National E-invoicing System (KSeF) starting February 2026
• Croatia, Malaysia, France, and Germany all have e-invoicing mandates rolling out through 2026-2027
• U.S. state-level economic nexus laws continue expanding, requiring tax collection based on sales activity rather than physical presence

For a seller handling their own MoR responsibilities, each new jurisdiction means another tax registration, another set of filing deadlines, and another compliance obligation. MoR services absorb this complexity by maintaining registrations globally and calculating taxes in real time at checkout.

There is an important trade-off: because MoR providers have already exceeded registration thresholds in most jurisdictions, customers may pay taxes they would not have owed if the seller had sold directly and remained below the local threshold. This can make prices slightly higher in smaller markets.

Risks and Considerations

Higher Costs

MoR services charge significantly more than standard payment processors. At 5-10% per transaction, the merchant discount rate is roughly double what a direct processing arrangement would cost. For high-volume businesses, this margin difference can be substantial.

Slower Payouts

Because MoR platforms deduct taxes, fees, and potential chargeback reserves before remitting funds, payout cycles are typically measured in weeks rather than the 1-2 business days common with direct payment settlement. This impacts cash flow, particularly for smaller businesses.

Loss of Customer Relationship

Since the MoR is the legal seller, the MoR's name appears on customer statements rather than the seller's brand. This can create confusion for customers who see an unfamiliar charge and file a chargeback. Some MoR providers mitigate this by allowing customized statement descriptors, but the legal entity remains the MoR.

Vendor Lock-in

Migrating away from an MoR provider means transferring all tax registrations, customer billing relationships, and subscription data. Because the MoR legally owns the customer payment relationship, switching providers or bringing MoR functions in-house can be complex and disruptive.

Shared Compliance Responsibility

Even when using an MoR, sellers retain some compliance obligations. Under PCI DSS v4.0, merchants must verify their provider's compliance status annually and maintain written agreements. The MoR handles the heavy lifting, but the seller cannot fully abdicate oversight.

Why It Matters for Crypto Commerce

The merchant of record model is increasingly relevant as cryptocurrency payment adoption accelerates. As of early 2026, 88% of U.S. merchants report receiving customer inquiries about crypto payments, and global crypto spend is projected to grow from $16 billion in 2024 to $38 billion by 2030.

For businesses accepting Bitcoin or stablecoins on Bitcoin, the MoR question is critical: who bears the tax reporting burden for property-classified digital assets? Who handles the compliance implications of settlement in a volatile asset? Solutions like dollar-denominated payments on fast settlement layers reduce some of this friction by allowing near-instant conversion and clear cost-basis tracking, but the underlying MoR obligations remain.

As stablecoin regulation matures globally, the intersection of MoR responsibilities and crypto commerce will continue to evolve. Businesses building payment infrastructure today need to understand both the traditional MoR framework and how it applies to digital asset transactions.

This glossary entry is for informational purposes only and does not constitute financial or investment advice. Always do your own research before using any protocol or technology.