MERCHANT OF RECORD
Merchant of Record vs Seller of Record: Who Does What?
Anyway Team
· 9 min read ·
Merchant of Record and Seller of Record can be the same company. Seller of Record identifies the party selling to the buyer; Merchant of Record identifies the merchant responsible for the payment transaction. In a SaaS reseller arrangement, an external MoR may also be the contractual seller while your team builds and supports the software.
The useful distinction is who owes each duty: payment handling, tax, refunds, delivery and support. The agreement, checkout disclosures and applicable law determine the arrangement; the two labels alone are not a universal division of responsibilities.
Merchant of Record vs Seller of Record at a glance
Question | Merchant of Record | Seller of Record |
|---|---|---|
What does the term identify? | The merchant responsible for the payment transaction | The party presented as selling to the buyer |
Can it be the SaaS company? | Yes, in a direct-sale setup | Yes |
Can an external MoR fill both roles? | Yes | Yes, where it contracts as the seller |
Who handles tax? | Check the legal structure, covered markets and service agreement | Seller duties also depend on the sale and applicable law |
Who administers refunds and disputes? | Usually the payment-side workflow for its covered sales | Customer obligations follow the sales agreement and law |
Who delivers and supports the software? | Often the SaaS supplier, even with an external MoR | Delivery may be performed by the supplier under the agreement |
These terms are sometimes used to compare selling directly with selling through an external MoR. That is a choice of business arrangement, rather than proof that a MoR cannot also be a Seller of Record. Paddle's explanation, for example, describes its MoR taking on the seller role.
What is a Merchant of Record?
The Merchant of Record is the entity recognized as merchant for the payment. It appears in transaction records and is accountable for the financial operation of the covered sale.
Its duties commonly include:
Collecting the customer payment
Maintaining the merchant relationship used for the transaction
Handling applicable transaction-tax duties within the covered arrangement; confirm the actual services and automation
Issuing transaction documents
Managing payment-side refunds and disputes
Keeping order, fee, and adjustment records
Paying net revenue to the product supplier
For a fuller definition, read the Merchant of Record guide.
What is a Seller of Record?
Seller of Record describes the party legally presented as selling the product or service to the buyer. The term focuses on the sales contract: what was promised, who must provide it, and who responds when the delivered service does not match the offer.
Seller duties can include:
Describing the product and commercial terms
Forming the customer contract
Making sure the product or service is delivered
Providing customer service for the sale
Applying cancellation and refund rights
Supplying the transaction documents required of the seller
In a direct SaaS sale, the software company may be both Merchant of Record and Seller of Record. In an MoR service arrangement, the provider may act as the contractual and payment seller for the transaction while the SaaS company supplies and supports the digital product under its agreement with the provider.
Why the terms are sometimes used interchangeably
For a simple purchase, the entity taking payment is often the same entity contracting with the buyer. The card statement, invoice, receipt, checkout terms, and refund process all point to one seller. In that case, Merchant of Record and Seller of Record describe two sides of the same transaction role.
The distinction becomes more visible in marketplaces, reseller structures, travel, ticketing, or multi-party commerce. One business may own the product, another may contract with the buyer, and another may appear in the payment chain. Contracts must specify who owns each duty.
For a SaaS founder choosing a provider, practical questions are more useful than the label:
Which entity is named at checkout?
Which entity appears on the invoice and payment record?
Who files transaction tax?
Who authorizes the refund?
Who answers payment questions?
Who supplies and supports the software?
What happens when a subscription renews or ends?
How the roles work in a direct SaaS sale
When a SaaS company sells directly through a payment processor, the company is usually both Seller of Record and Merchant of Record.
The buyer contracts with the SaaS company. The company controls delivery and support, and it also remains responsible for transaction tax, customer documents, payment administration, and sales records. Software providers may assist with each task, but the company retains the seller role.
This model suits a company that wants direct control and has people and systems assigned to the work.
How the roles work with an MoR provider
Under a typical digital-product MoR setup:
The SaaS founder lists an approved product through the MoR.
The customer sees the MoR seller disclosure at checkout.
The MoR collects payment; the tax treatment and included services must match the covered arrangement.
The MoR issues the invoice or receipt for the sale.
The founder’s application delivers access to the software.
The MoR records refunds, disputes, fees, and merchant balance changes.
The founder receives net revenue under the provider terms.
The founder still owes customers a working product and responsive product support. The MoR gives the transaction a legal seller and manages the payment-side work stated in the agreement.
How Anyway defines the sale
Anyway's MoR documentation states that, for eligible transactions, Anyway is both the seller of record and the buyer's contractual counterparty. The SaaS team supplies and supports the product. This is a concrete example of the two roles overlapping.
The current product supports hosted payment links, recurring Card/USD subscriptions, renewal tracking, refunds, chargeback workflows and payouts. Automated per-order tax calculation, collection and remittance has not launched, and current orders do not include a separate tax amount. That limitation does not establish a tax exemption; confirm the treatment of your actual sales.
The standard card and digital-wallet fee is 3.9% + $0.50 per successful transaction, with no monthly or setup fee. Payout fees are separate; see the fee schedule.
A signed webhook and server-side order check can connect a completed sale to an account in your app. The application grants access and handles product support. Read the buyer terms for the contractual arrangement rather than inferring it from a checkout logo.
A SaaS example: follow one sale from checkout to support
Imagine a customer buying a $20 monthly analytics plan. This is an illustrative workflow, not a real customer transaction.
Customer event | Direct sale through a processor | Covered sale through an external MoR |
|---|---|---|
Customer accepts the sale terms | Your SaaS business is the seller | The disclosed MoR entity is the seller under the arrangement |
Payment is completed | The processor handles payment; your business retains seller duties | The MoR handles its payment-side duties and creates the transaction record |
Customer needs product access | Your app grants access | Your app still grants access after verifying the paid order |
Customer cannot use a feature | Your product team investigates | Your product team still investigates |
Customer requests a refund | Your team uses the processor's workflow | Your team follows the MoR refund workflow and supplies requested evidence |
Before launch, put the checkout seller name, receipt or invoice details, refund contact and product-support contact side by side. If they conflict, resolve the arrangement before explaining it to buyers. For the choice between service models, see MoR vs payment processor.
What should appear in the customer journey?
A clear MoR checkout should make the parties understandable to the buyer.
Before payment
The product page should identify the product provider, price, billing schedule, delivery, cancellation, refund policy, terms, privacy information, and support contact.
At checkout
The buyer should see what is being purchased, the total charge, the billing frequency, and the entity acting as seller for the transaction.
After payment
The buyer should receive confirmation plus the applicable invoice or receipt. The SaaS application should grant the purchased access, and support should be available for product questions.
These details reduce confusion without forcing a founder to explain legal terminology to every buyer.
Which role matters most when comparing providers?
Check the actual arrangement first: who sells to the buyer, who manages payment-side issues, and who supplies the software. Then verify tax coverage, documents, support and refund responsibilities. Choosing a familiar label does not answer those questions.
Treat the provider agreement as the source of truth. Confirm that its seller disclosures, tax scope, customer documents, product rules, billing schedules, and payout terms match the way your SaaS is sold.
Give every transaction one clear seller
The best customer experience is not built on terminology alone. It comes from a sale in which checkout, legal seller, invoice, tax, delivery, support, and refund paths agree with one another.
Anyway provides that structure for SaaS and digital products by acting as MoR on covered transactions while giving developers a direct payment-link and webhook flow for product delivery.
Frequently asked questions
Are Merchant of Record and Seller of Record the same?
Yes, they can be the same entity. A company selling directly can hold both roles, and an external MoR may also become the contractual seller for covered sales. Product delivery can still be performed by the SaaS supplier.
Can the product owner be different from the Merchant of Record?
Yes. A SaaS founder can own and operate the product while an MoR acts as seller for covered customer transactions.
Who appears on the customer’s receipt?
The transaction document should identify the legal seller for the sale. In an MoR arrangement, that is generally the MoR entity specified at checkout and in the agreement.
Who supports the SaaS product in an MoR model?
The founder or SaaS company normally supports product use and delivery. The MoR manages the payment-side customer transaction according to its terms.
Is Anyway the Merchant of Record?
Yes. Anyway states that it acts as Merchant of Record for covered sales through Anyway Business.
Sources and related reading
Reviewed October 26, 2026. Terminology varies across providers and arrangements; the examples above do not assign duties under every contract or jurisdiction.
Best Merchant of Record for SaaS: compare providers once the required responsibilities are clear.