Direct Answer
A merchant of record is responsible for the customer-facing sale, including the transaction’s refund and dispute obligations. It may be the business supplying the product, a platform, or a reseller under the relevant arrangement. A merchant-of-record service can take on specified payment and tax duties, but it does not automatically remove every obligation from the product supplier.
Source: Stripe, “Understand the merchant of record in a Connect integration” (Payment-network merchant role in Stripe Connect); Paddle, “Paddle Master Services Agreement” (Paddle supplier contract; software and digital-content resale), accessed 2026-09-03.
The seller role is different from the processing role
The merchant of record, often shortened to MoR, identifies who stands behind the customer’s transaction. A payment processor provides transaction-processing services; that function alone does not identify the seller. In platform payments, the seller role must be consistent with the commercial arrangement and the payment setup.
Source: Stripe, “Understand the merchant of record in a Connect integration” (Payment-network merchant role in Stripe Connect); Stripe, “What a merchant of record does and why it matters” (Stripe regular direct-payment role example), accessed 2026-09-03.
Why the distinction matters
A customer should be able to identify the responsible seller across the purchase journey. Review the checkout, terms, receipt and card-statement description together. The statement description is the text used to identify a charge on the customer’s account. Do not assume a logo or a chosen description, by itself, establishes who carries the legal duties.
Source: Stripe, “Understand the merchant of record in a Connect integration” (Payment-network merchant role in Stripe Connect), accessed 2026-09-03.
Illustrative example: software sold through a reseller
Imagine a software developer appoints a reseller as merchant of record. The customer buys through the reseller, but still uses software maintained by the developer. A billing question and a software defect need not follow the same support path. The operating plan should say who answers each request and who supplies the information needed to resolve it.
Source: Paddle, “Paddle Master Services Agreement” (Paddle supplier contract; software and digital-content resale), accessed 2026-09-03.
This distinction appears in a real contract: Paddle’s supplier agreement assigns it first-tier order support while retaining technical and delivery support duties for the supplier. The same agreement retains supplier obligations for accurate product information. Delegating the sale therefore does not mean delegating every part of the product business.
Source: Paddle, “Paddle Master Services Agreement” (Paddle supplier contract; software and digital-content resale), accessed 2026-09-03.
Build a responsibility map before launch
Decision | Question to settle in the agreement |
|---|---|
Customer-facing seller | Which legal entity is identified to the customer? |
Refunds and disputes | Who decides, communicates and ultimately bears the cost? |
Transaction taxes | Which products, territories and tax duties are covered? |
Product support | Who handles defects, access issues and delivery questions? |
Supplier information | Who provides and updates product and business details? |
Source: Stripe, “Understand the merchant of record in a Connect integration” (Payment-network merchant role in Stripe Connect); Stripe, “How Managed Payments works” (Stripe Managed Payments service scope only); Paddle, “Paddle Master Services Agreement” (Paddle supplier contract; software and digital-content resale), accessed 2026-09-03.
Common mistakes
- Equating a merchant-of-record service with universal tax coverage. Check the service’s stated territories and exclusions.
- Equating dispute handling with protection from every dispute cost. A contract can assign handling and financial liability differently.
- Treating the reseller arrangement as a transfer of product support. Check the duties retained by the supplier.
Source: Stripe, “How Managed Payments works” (Stripe Managed Payments service scope only); Paddle, “Paddle Master Services Agreement” (Paddle supplier contract; software and digital-content resale), accessed 2026-09-03.
For example, Stripe’s Managed Payments documentation expressly leaves tax compliance for transactions in uncovered countries with the business. This is a provider-specific exception worth checking, not a statement about the coverage of every merchant-of-record service.
Source: Stripe, “How Managed Payments works” (Stripe Managed Payments service scope only), accessed 2026-09-03.
What to read next
Use the related payment processor and merchant acquirer entries to separate the seller role from payment infrastructure. Before adopting an arrangement, have the responsible commercial and legal teams complete the responsibility map against the actual contract.
Source: Stripe, “Understand the merchant of record in a Connect integration” (Payment-network merchant role in Stripe Connect); Paddle, “Paddle Master Services Agreement” (Paddle supplier contract; software and digital-content resale), accessed 2026-09-03.
Editorial note: AI-assisted educational content prepared for HaiPay. It is not investment, legal or tax advice. The cited sources explain the concepts; your provider agreement and applicable rules govern your arrangement.
FAQ
No. Processing a payment and being the responsible seller are different roles. In a platform arrangement, identify the merchant of record from the commercial relationship and the relevant payment configuration rather than the processor’s name alone.
Source: Stripe, “Understand the merchant of record in a Connect integration” (Payment-network merchant role in Stripe Connect); Stripe, “What a merchant of record does and why it matters” (Stripe regular direct-payment role example), accessed 2026-09-03.
Not automatically. Service coverage can depend on the territory, product and agreement. For example, Stripe’s Managed Payments documentation leaves compliance for transactions in uncovered countries with the business. Review the duties actually included rather than relying on the service label.
Source: Stripe, “How Managed Payments works” (Stripe Managed Payments service scope only), accessed 2026-09-03.
Not necessarily. A contract can separate payment and order support from technical or product support. Paddle’s supplier agreement, for example, retains technical and delivery support responsibilities for the supplier.
Source: Paddle, “Paddle Master Services Agreement” (Paddle supplier contract; software and digital-content resale), accessed 2026-09-03.
Check the agreement as well as the customer-facing seller role. A provider may manage the process while recovering amounts or fees from the supplier. Handling a dispute is not the same promise as absorbing its financial cost.
Source: Paddle, “Paddle Master Services Agreement” (Paddle supplier contract; software and digital-content resale), accessed 2026-09-03.
Sources
Related terms
Acquiring and settlement
Payment Processor
A payment processor is a service that handles transaction messages between businesses, financial institutions, and payment networks during authorization, capture, and related status updates.
Acquiring and settlement
Merchant Acquirer
A merchant acquirer is a payment service provider that contracts with businesses to accept and process card payments on behalf of participating card networks.
Acquiring and settlement
Merchant Account
A merchant account is an account used to accept and manage card-payment proceeds before they reach a business bank account.
Usage Guide
Read GuideAcquiring Decisions
What Is Payment Acceptance? How It Works and How to Improve Acceptance Rates
Need help mapping your payment stack?
Increase conversion with local methods, FX-aware checkout, and unified reconciliation.
Contact Us