Merchant of Record Explained

Selling software, SaaS, AI tools, or digital content internationally can open the door to rapid growth. It can also create a complicated operational burden involving sales tax, VAT, GST, payment processing, fraud prevention, chargebacks, invoicing, and customer support.

A Merchant of Record (MoR) is designed to take responsibility for much of that burden. Instead of acting only as a payment processor, an MoR becomes the legal seller in the transaction and manages key financial and compliance obligations on behalf of the digital business.

In one sentence: A Merchant of Record is the legal entity that sells a digital product to the end customer and assumes responsibility for processing the transaction, collecting and remitting applicable taxes, managing payment compliance, and handling disputes.

This guide explains what an MoR does, how it differs from a payment service provider and a payment facilitator, when a digital business may need one, and what founders should evaluate before choosing a provider.

What Is a Merchant of Record?

A Merchant of Record is the legal entity responsible for selling a product or service to the end customer. In a digital commerce arrangement, the MoR typically processes the payment, issues the customer-facing receipt or invoice, calculates and collects applicable indirect taxes, and manages transaction-related compliance obligations.

The distinction is important because a payment processor and a Merchant of Record perform different functions. A processor provides the technical infrastructure that moves money between a customer and a business. An MoR goes further by becoming the recognized seller of the product and taking on defined legal, financial, and operational responsibilities associated with the sale.

In practice, the software company still owns and operates its product. It sets the pricing, controls the user experience, develops the technology, and maintains the customer relationship. The MoR operates the transaction and compliance layer between the business and the buyer.

How the MoR transaction model works

The arrangement can be understood as two linked transactions:

1. The customer sale: The MoR sells the product to the customer, processes the payment, applies the relevant tax treatment, and provides the transaction documentation.
2. The business payout: The MoR consolidates the business’s sales and sends a payout according to the commercial agreement, generally after accounting for taxes, refunds, fees, and other applicable adjustments.

The exact contractual structure varies by provider and jurisdiction. Businesses should therefore review the provider’s terms to understand which obligations are transferred, which remain with the business, and how refunds, chargebacks, and customer support are handled.

Why “Going Global” Is More Complicated Than It Looks

A digital product may be available worldwide as soon as it is launched online, but global availability does not automatically mean global compliance is simple.

As customers arrive from different countries, states, and provinces, a business may need to address several overlapping requirements:

• Indirect taxes: Depending on the customer’s location and the nature of the product, the transaction may involve VAT, GST, sales tax, or another form of consumption tax.
• Registration and reporting: Tax authorities may require registration, periodic returns, recordkeeping, and remittance once applicable obligations are triggered.
• Payment compliance: Card payments involve requirements relating to security, authentication, data handling, and payment-network rules.
• Fraud and risk: Cross-border transactions can expose a business to stolen cards, account takeover, friendly fraud, and unusual purchasing patterns.
• Chargebacks: Disputes require evidence, deadlines, and operational processes. Excessive dispute activity can damage payment acceptance and commercial relationships.
• Localization: Buyers often expect familiar currencies, payment methods, receipts, languages, and checkout experiences.
• Revenue operations: Recurring businesses must manage failed payments, card expiry, retries, refunds, credits, upgrades, downgrades, and cancellations.

Building these capabilities internally may require tax specialists, legal advisers, finance operations, payment engineers, fraud tooling, and multiple third-party integrations. An MoR can consolidate many of those functions into one commercial and technical relationship.

Merchant of Record vs. PSP vs. PayFac

These terms are often used interchangeably, but they describe different roles in the payments ecosystem.

Payment Service Provider or payment gateway

A Payment Service Provider (PSP) supplies the infrastructure required to accept payments. It may provide card processing, payment methods, tokenization, payouts, and related APIs. However, using a PSP does not necessarily make the provider the legal seller of the product. In a conventional setup, the software company remains responsible for its own tax registrations, tax filings, commercial terms, refunds, and broader compliance obligations.

Payment Facilitator

A Payment Facilitator (PayFac) enables sub-merchants to accept payments through a master acquiring relationship. This can simplify onboarding and payment acceptance, but it does not automatically transfer the seller’s sales-tax and legal responsibilities to the PayFac.

Merchant of Record

An MoR acts as the seller or reseller in the customer transaction. Its responsibilities generally extend beyond payment acceptance to include tax calculation and remittance, transaction documentation, risk controls, refunds, and dispute management, subject to the provider’s agreement and the laws that apply to the transaction.

Comparison table

The table describes common models, not universal rules. The legal allocation of responsibility always depends on the provider agreement, the product category, the customer’s location, and applicable law.

What Happens Inside an MoR Platform?

A modern MoR platform may combine several operational functions in one system. The exact feature set varies, but the following capabilities are central to the model.

1. Tax calculation, collection, and remittance

The platform determines the customer’s location using information such as billing details, payment data, and other permitted signals. It then applies the relevant tax treatment, displays the amount at checkout, records the transaction, and—where covered by the agreement—handles registration, filing, and remittance obligations.

Businesses should confirm how the provider defines customer location, which taxes and jurisdictions are supported, how exemptions are handled, and whether the service covers marketplace, reseller, or other specialized rules.

2. Payment orchestration

An MoR may connect to multiple payment processors, acquirers, and local payment networks. Routing transactions across different rails can improve payment coverage and reduce dependence on a single provider. A robust system may also support authorization optimization, payment-method selection, currency conversion, and regional routing.

3. Subscription billing and revenue recovery

Recurring revenue businesses lose customers for reasons that have nothing to do with product satisfaction. Cards expire, bank accounts change, transactions receive soft declines, and temporary outages interrupt payment attempts.

An MoR platform may support automated retries, card-account updates, customer notifications, grace periods, and dunning workflows. These tools help recover legitimate revenue while giving customers a clear path to update their payment details.

4. Fraud prevention and authentication

Cross-border commerce requires a balance between reducing fraud and avoiding unnecessary declines. An MoR may use risk scoring, device and behavioral signals, velocity rules, and authentication mechanisms such as 3-D Secure to evaluate transactions in real time.

No fraud system eliminates all risk. Businesses should ask how the provider handles false positives, manual review, account takeovers, fraud-related refunds, and the customer experience when additional verification is required.

5. Chargeback and dispute management

A chargeback occurs when a customer disputes a payment through their bank or card issuer. Managing a dispute generally requires collecting evidence, meeting network deadlines, and presenting a coherent explanation of the transaction.

An MoR can centralize this process, coordinate evidence, respond to disputes, and manage the financial impact according to the commercial agreement. It is still important to understand exclusions, liability caps, reserve requirements, and the circumstances in which the business may remain responsible.

6. Localized checkout and settlement

Customers are more likely to complete purchases when the checkout experience reflects local expectations. Localization may include presenting prices in the buyer’s currency, offering familiar payment methods, displaying appropriate tax treatment, and providing locally understandable transaction documentation.

The business can then receive consolidated settlements rather than opening a separate merchant account and building a complete finance process in every market.

When Does a Business Need a Merchant of Record?

An MoR is most useful when the cost and risk of building a global payments operation exceed the value of managing it internally. The decision is especially relevant for businesses with digital products, recurring billing, international customers, or small finance and legal teams.

A simple decision framework is:

Common use cases

SaaS and subscription businesses often use an MoR when they sell recurring plans to customers in multiple jurisdictions and want a single operational layer for billing, tax, and payment recovery.

AI tools and developer products may benefit when a small team wants to launch internationally without dedicating engineering time to regional payment integrations and compliance operations.

Downloadable software and digital games may use an MoR to support direct web sales, downloadable content, upgrades, subscriptions, and international payment methods.

Digital creators and online services may consider an MoR when they need a more structured way to manage taxes, receipts, refunds, and global customer payments as sales volume increases.

Frequently Asked Questions

What does “Merchant of Record” mean in plain English?

It means that another company becomes the legal seller in the customer transaction. The customer buys the product from the MoR, and the MoR then pays the software company according to the agreed commercial arrangement.

Does using an MoR mean losing control of the brand or product?

Usually, no. The software company can continue to own the product, brand, pricing strategy, application, and user experience. However, the exact ownership and access rights for customer data, support interactions, and transaction records depend on the contract.

Is an MoR the same as a payment gateway?

No. A payment gateway or PSP primarily provides the technical infrastructure for accepting payments. An MoR acts as the legal seller and may assume additional tax, compliance, refund, and dispute responsibilities.

Is Stripe automatically a Merchant of Record?

Standard payment-processing services do not automatically make the software vendor an MoR. In a conventional setup, the vendor remains the seller and keeps its own tax and compliance responsibilities. Some payment providers offer separate managed products or services that may address parts of the MoR model, so businesses should review the specific product terms rather than rely on the provider’s brand name.3

Is an MoR always cheaper than building a payment stack internally?

Not necessarily. An MoR usually charges a premium for the additional services and liabilities it provides. It may nevertheless be more cost-effective when the alternative includes tax registrations, filings, legal support, engineering work, fraud tools, chargeback operations, and the cost of internal staff.

Can an MoR support recurring subscriptions?

Many MoR providers support subscriptions, recurring billing, payment retries, plan changes, refunds, and related workflows. Businesses should confirm the provider’s support for their billing model, pricing structure, geographic markets, and migration requirements.

A Modern Developer-Centric Approach: Kiwy

As software businesses become more international from the day they launch, founders increasingly need payment infrastructure that is both compliant and easy to integrate.

Kiwy is positioned as a modern billing and payments layer for software founders and digital creators. The value of a platform in this category is not limited to accepting a card. It is the ability to give developers a straightforward route from product launch to global monetization while reducing the amount of payment, tax, and back-office infrastructure they must assemble themselves.

When evaluating Kiwy—or any comparable platform—developers should look for:

• A hosted checkout experience that can be launched without building a complete payments frontend.
• Clear APIs and webhooks for provisioning access, handling subscription events, and synchronizing payment status with the product.
• Support for global tax and payment operations that matches the company’s target markets and product type.
• Transparent reporting and payouts that make revenue reconciliation straightforward.
• Reliable revenue recovery for failed recurring payments, refunds, and plan changes.
• Accessible support and documentation so a small engineering team can launch and operate confidently.

The right platform should allow a development team to focus on building, distributing, and improving its product while treating payments as a dependable infrastructure layer rather than a permanent compliance project.

Final Takeaway

A Merchant of Record is more than a payment button. It is a commercial and operational model that places a specialized provider between a digital business and its international buyers.

For the right company, an MoR can simplify indirect taxes, payment processing, invoicing, fraud prevention, subscription recovery, chargebacks, and global settlement. The result is a faster path to international sales and a smaller internal compliance burden.

The decision still requires careful review. Compare the provider’s total cost, contractual liability, supported markets, reporting, customer-data policies, payout terms, and product coverage. If those conditions align with the business’s needs, an MoR can become one of the most effective shortcuts to global digital growth.