Merchant of Record vs PSP: Why Payment Processing Isn’t Enough

Cross-border eCommerce growth introduces payment complexity, compliance exposure, tax liability, and fraud risk. Many companies assume that implementing a Payment Service Provider (PSP) solves these challenges.

It does not.

Understanding the difference between a Merchant of Record (MoR) and a PSP is critical for mid-market and enterprise brands scaling internationally. A PSP facilitates payment processing, while a Merchant of Record assumes legal and financial responsibility for the transaction.

That structural distinction changes everything.

Learn how Gapp Group operates as a compliant transaction partner on our eCommerce Merchant of Record page.

What Is a Payment Service Provider (PSP)?

A Payment Service Provider enables merchants to accept electronic payments.

PSPs typically:

• Route transactions to acquiring banks
• Handle authorization requests
• Support multiple payment methods
• Provide fraud screening tools
• Manage technical payment integration

PSPs focus on payment facilitation.

They do not assume:

• Tax calculation or remittance
• Regulatory reporting responsibility
• Legal ownership of the transaction
• Chargeback liability at the structural level

For a broader overview of payment infrastructure, see our guide to eCommerce payment processing.

What Is a Merchant of Record (MoR)?

A Merchant of Record is the legal entity that sells the product to the end customer and assumes responsibility for the transaction.

Under a Merchant of Record model:

• The MoR processes the payment
• The MoR calculates, collects, and remits applicable taxes
• The MoR manages regulatory compliance
• The MoR assumes fraud and chargeback oversight
• The MoR handles settlement execution

Your company remains the Seller of Record, maintaining product ownership and customer relationships.

For a detailed breakdown, review Merchant of Record responsibilities.

The difference is not technical — it is structural.

Merchant of Record vs PSP: Core Differences

1. Legal Responsibility

PSP: Provides payment rails.

MoR: Becomes the legal seller for transaction purposes and assumes compliance obligations.

2. Tax Handling

PSP: Does not assume tax liability.

MoR: Calculates, collects, and remits VAT, GST, and applicable sales taxes in relevant jurisdictions.

For deeper tax context, see cross-border taxation for eCommerce.

3. Compliance & Regulatory Oversight

PSP: May provide tools but does not assume reporting liability.

MoR: Assumes transaction-level regulatory compliance responsibility.

This includes oversight tied to international payment and settlement frameworks.

4. Fraud & Chargeback Management

PSP: Offers fraud detection tools.

MoR: Integrates fraud risk oversight within a broader compliance framework.

Learn more about this integration in our guide to fraud risk management with Merchant of Records.

5. Cross-Border Infrastructure

PSPs can process international transactions.

They do not restructure international liability.

As global expansion accelerates, brands must evaluate whether they need:

• Technical processing support
  or
• Transaction-level structural responsibility

For infrastructure context, see our article on what are cross-border payments.

When Is a PSP Enough?

A PSP may be sufficient if:

• You operate in a single country
• You manage tax registration internally
• You accept limited international exposure
• Your compliance footprint is minimal

However, as international sales increase, complexity compounds.

When You Need a Merchant of Record Instead of a PSP

You should evaluate a Merchant of Record model if:

• You are expanding into multiple international markets
• VAT, GST, or sales tax registration thresholds are approaching
• Cross-border fraud rates are rising
• Regulatory oversight is becoming burdensome
• Settlement complexity affects forecasting

If your payment infrastructure is creating operational strain, it may be time to reassess your structure.

See our framework on when to switch to a Merchant of Record.

Can a PSP and Merchant of Record Work Together?

Yes.

A Merchant of Record may integrate with underlying payment processors or PSP infrastructure while assuming transaction responsibility.

The PSP handles routing.

The MoR handles legal and compliance structure.

The distinction is not either/or — it is responsibility versus facilitation.

FAQs: Merchant of Record vs PSP

Final Thoughts: Processing Payments Is Not the Same as Owning the Transaction

Payment infrastructure is often mistaken for compliance infrastructure.

They are not the same.

A PSP enables transactions. A Merchant of Record assumes responsibility for them.

For mid-market and enterprise eCommerce brands expanding internationally, that distinction becomes increasingly important.

Gapp Group operates as the Merchant of Record — assuming payment processing responsibility, tax calculation and remittance, regulatory oversight, fraud monitoring, and settlement execution — while your company remains the Seller of Record.

If you are evaluating your global payment structure, explore our eCommerce Merchant of Record solution or contact our team to discuss your expansion strategy.

International growth requires infrastructure — not just integration.