Merchant of Record vs payment processor: know who legally sells to the customer

A payment processor moves money for the merchant while the business usually remains the legal seller. A Merchant of Record, by contrast, can become the contractual seller to the customer and take responsibility for payment processing, certain taxes, refunds and other obligations under the service model. The commercial difference is much larger than which checkout page is used.

Start by identifying who is the legal seller

In a standard acquiring or gateway model, the business contracts with the customer and the processor handles the payment. Under a Merchant of Record model, the provider can contract with the customer as seller of record and then settle proceeds to the underlying business.

This affects invoices, customer terms, tax, chargebacks and the name the customer sees on payment records.

A Merchant of Record can take on indirect-tax administration

MoR services often calculate, collect and remit applicable sales taxes or VAT in markets where the model supports that responsibility.

The underlying business still needs accounting and tax advice because revenue recognition, permanent establishment and other tax questions do not disappear simply because the MoR handles checkout tax.

Disputes can be handled by the MoR rather than the underlying seller

Because the MoR is the payment merchant, it can manage card disputes, fraud tooling and refund processing with acquirers. The underlying business provides evidence and commercial support under the provider agreement.

Understand who ultimately bears losses. A provider can pass chargeback cost, reserves or fraud exposure back through settlement terms.

Customers need to recognise the statement descriptor and seller identity

Where the MoR name appears on card statements or invoices, the checkout should explain the relationship clearly. Otherwise customers can dispute a valid purchase because they do not recognise the billing entity.

Customer-support scripts should use the same legal and brand names shown during payment.

The business receives net settlement from the MoR

The provider can deduct payment fees, taxes, refunds, reserves and other charges before paying the underlying business.

Reconcile gross customer sales through every deduction to the net bank payout. Posting only the payout as revenue understates both sales and fees.

Compare control with administrative simplicity

An MoR can make global selling easier where tax, acquiring and local payment methods are complex. The trade-off is more dependence on one provider and less direct control over the customer payment relationship.

A mature merchant with local entities and acquiring may prefer direct processing. A smaller digital business can value the administrative outsourcing more highly.

Worked example: a software company sells a £100 subscription. Under direct processing, the software company is the seller and its processor moves the payment. Under an MoR model, the MoR may charge the customer, handle VAT and card processing, then remit the software company's agreed net amount. The same customer purchase creates very different contracts and accounting evidence.

Review provider failure and migration risk. If the MoR controls customer billing, stored credentials and tax registrations, leaving the provider can require a more complex migration than changing a normal gateway. Contract negotiations should cover data access, customer portability and termination.

Keep product liability and customer-service responsibilities clear. A Merchant of Record can handle payment and tax obligations while the underlying business still remains responsible for delivering the product and supporting customers under the commercial arrangement.

Check data portability before signing an MoR contract. Customer billing history, tax records and stored payment credentials can become deeply embedded in the provider. The exit plan should explain what data the business can export and how subscriptions continue after migration.

Review reserves and settlement delays under the MoR model. A provider taking more legal and payment responsibility can also hold funds or deduct risk reserves. Treasury should compare actual days-to-cash with direct acquiring, not only the headline provider fee.

For B2B sales, check whether customers accept invoices from the MoR rather than the software or service company they contracted with commercially. Some procurement departments require the legal seller on the invoice to match approved vendor records, which can affect enterprise sales.

Use a responsibility matrix covering seller identity, VAT or sales tax, payment acceptance, fraud, refunds, chargebacks, invoicing and customer support. The biggest MoR mistakes occur when both provider and underlying business assume the other party owns a task.

Compare settlement reserves under high-refund business models. Travel, events and digital subscriptions can create significant future refund exposure, and the MoR can protect itself by delaying or holding part of merchant proceeds. Treasury should model that cash restriction before choosing the service.