PSP vs MOR: Payment Service Provider vs Merchant of Record Explained

At some point, every business selling online has to make payment decisions. And most of them make it without fully understanding what they're actually choosing between. Two of the most common choices of payment partners are a Payment Service Provider and a Merchant of Record. One processes your payments, and the other legally owns them.

In this guide, you'll learn what a Payment Service Provider (PSP) and Merchant of Record (MoR) are, and how each handles payment processing, taxes, compliance, fraud, and chargebacks differently. You'll also discover their integration approaches, advantages and limitations, decision frameworks for choosing between them, and best practices for using each effectively.

Key Takeaways

• Understanding PSP vs MoR helps Indian businesses selling internationally choose the right payment infrastructure, balancing operational simplicity (MoR) against control and lower costs (PSP).
• PSP (Payment Service Provider) processes payments technically accepting cards, wallets, and bank transfers via gateway integration. Examples: Stripe, Razorpay, Adyen, Cashfree.
• MoR (Merchant of Record) is the legal seller, handling not just payment processing but tax remittance, compliance, fraud, chargebacks, and customer disputes. Examples: Lemon Squeezy (Stripe), Paddle, FastSpring.
• You can use both: Many growth-stage businesses use a PSP (Razorpay, Stripe) for domestic markets and an MoR (Lemon Squeezy, Paddle) for cross-border digital sales.
• For Indian businesses: RBI's PA-CB (Payment Aggregator - Cross Border) framework adds another layer. Receiving cross-border payments to India requires a PA-CB-licensed entity, which most foreign MoRs are not, making FEMA-compliant settlement a separate consideration.

A payment service provider facilitates electronic payment transactions among different parties like customers, businesses, and banks. With the help of a PSP, you can accept payment in a variety of ways like credit cards, debit cards, digital wallets, and bank transfers, all from a single platform or using integration.

Before the existence of PSPs, accepting card payments meant setting up a merchant account with a bank. A process that was slow, paperwork-heavy, and inaccessible for smaller businesses. PSPs changed that. Now, they provide both a merchant account and a payment gateway, so that you can collect and manage your payments in a much simpler and more efficient way.

A Merchant of Record is the legal entity that sells goods or services to the end customer. Basically, they take on all payment-related liabilities like collecting sales tax, ensuring PCI compliance, and handling refunds and chargebacks.

When a customer pays, it's the MOR's name that shows up on their bank statement, not yours. This is because the MOR acts as a reseller. It buys from you and sells to your customer, which is why all the legal and financial responsibility sits with them, not you. You still sell your product. The MOR handles everything around the transaction itself.

Both a PSP and an MOR help you get paid. But the similarity ends there.

A PSP gives you the technical infrastructure to process payments. That's it. Everything else, taxes, compliance, fraud liability, chargebacks, stays with you. A PSP primarily focuses on the transmission and authorization of payment data, and typically requires merchants to manage all additional aspects of the sales process separately.

An MOR goes much further. It acts as an all-in-one e-commerce partner, taking full ownership and responsibility for the entire transaction lifecycle. It will manage payment processing, global tax compliance, and fraud prevention, and free you to focus on growth.

Have a look at this PSP vs MOR table to further understand their differences:

Both PSP and MOR are important links in the payments chain, but as we know, what each one is actually responsible for is very different. Let’s see how. 

What is a PSP responsible for?

A PSP's job is technical. It gives the infrastructure to process payments, manages payment gateways, connects with banks and card networks, and makes sure that all transactions are authorized and settled. Its responsibilities cover:

• Payment processing, under which it accepts, authorizes, and settles customer transactions.
• Fraud detection tools to flag suspicious transactions, though ultimate liability often stays with the merchant. 
• PCI compliance, so the payment infrastructure meets security standards. But the merchant remains responsible for their own compliance.

Everything else, including taxes, chargebacks, refunds and regulatory compliance, stays with the business.

What is an MoR responsible for?

An MOR goes much further. It also handles the legal and financial leg of the entire transaction lifecycle, from the moment the customer pays to the moment funds are settled. An MOR:

• Calculates, collects, and remits sales tax, VAT, or GST to the correct authority, depending on where your business and customers are located.
• Handles PCI DSS, KYC, and AML requirements on behalf of the business.
• Takes primary responsibility to detect and prevent fraudulent transactions.
• Manages disputes with banks and card companies directly, without the business needing to get involved.
• Handles transaction-related data in compliance with privacy regulations.

With a PSP, compliance is something you have to handle. Your business retains full liability for tax compliance, regulatory adherence, and customer disputes. The PSP just processes the payment and steps back. Tax registrations, data privacy laws, fraud liability, chargeback management, all of this is your problem to solve, often across multiple jurisdictions.

With an MOR, that burden shifts. The MOR assumes liability for tax compliance, calculating, collecting, and remitting the correct sales tax, VAT, or GST to the appropriate global tax authorities, as well as adhering to payment regulations like PCI DSS and other regional financial laws.

Here's what that looks like in practice:

Tax compliance

Since taxes on digital goods are almost always calculated based on the customer's location rather than the seller's, an MOR must be able to calculate, collect, and remit taxes wherever its customers are. A PSP doesn't touch any of this.

PCI DSS and data security

When a business uses an MOR, its CRM and integrated systems receive all customer and transaction details except full credit card numbers, shielding the business from the PCI DSS compliance burden entirely. With a PSP, the business is responsible for maintaining its own PCI compliance posture.

Data privacy

If the MOR sells to EU customers or processes EU personal data, it must comply with GDPR to maintain strict standards for processing and maintaining customer data. That obligation falls on the MOR.

Regulatory monitoring

A third-party MOR monitors the ever-changing regulatory landscape and ensures that businesses remain compliant as laws change and new rules are enacted. With a PSP, that monitoring falls to the business, which in practice often means keeping legal counsel on retainer familiar with global tax and payment regulations.

In the case of issues with a payment like a fraudulent transaction, a disputed charge, or a customer demanding a refund. Someone has to deal with it. Who that is depends entirely on whether you're using a PSP or an MOR.

With  PSP

A PSP routes payments, tokenizes data, and settles funds, but you remain the legal merchant, responsible for fraud liability, handling chargebacks, and issuing customer invoices. The PSP may provide basic fraud detection tools to flag suspicious transactions, but unlike an MOR that assumes responsibility for outcomes, a PSP only provides detection tools, the liability for what happens next remains with the business.

That means if a fraudulent transaction slips through, the loss is yours. If a customer disputes a charge, your finance team handles it. With a PSP, your company retains the risk and is responsible for fighting chargebacks and bearing losses from fraud.

With an MOR

An MOR assumes liability for fraudulent transactions and chargebacks, directly absorbing the financial loss. It takes ownership of the outcome.

MORs get involved in customer disputes directly. They investigate chargeback claims, represent the merchant's interests, and communicate with customers about issues. They also manage related documentation and process refunds and returns. None of that lands on your team.

A PSP typically provides software to integrate directly with e-commerce websites or point-of-sale systems. It establishes technical connections with acquiring banks and card networks, and enables merchants to accept different payment methods without needing to partner with a particular bank. For a business, this means dropping a PSP integration into their platform and gaining access to cards, digital wallets, and local payment methods in one move. 

Many MoRs also offer easy integration with popular e-commerce platforms, shopping carts, and other business systems, making it easier for businesses to get up and running. The difference is what comes bundled with that integration. The MoR ensures seamless transaction processing through PSP integrations, merchant account management, and payment gateway setup and maintenance, all handled on the business's behalf.

For SaaS companies and digital product sellers in particular, instead of a patchwork of disparate components, businesses can leverage a robust all-in-one solution that seamlessly integrates with existing systems. 

Once either model is integrated, a business can:

• Accept payments across multiple currencies and payment methods from day one
• Customize the currency, preferred payment options, and checkout experience for customers right from the start
• Extend to new markets through configuration rather than rebuilding the entire payment stack
• Scale internationally without the friction of establishing legal entities in each country

Both models come with real advantages. Both come with real tradeoffs. The one that's right for you depends entirely on what stage your business is at and how much of the payment complexity you want to own. 

MOR

PSP

The decision between a MoR and a PSP is a choice between control and convenience. Both serve a purpose, the question is which one fits your business better.

A PSP is likely the right fit if:

• You sell in one primary market, and your tax footprint is still limited
• You have in-house finance and legal support for tax compliance 
• You want lower baseline processing fees and full control over your payment stack
• Your business only requires a third party to process payments, without taking on broader financial responsibilities

A MoR makes more sense if:

• Cross-border growth, speed, and liability offload are your priorities
• Your team is spending product time on billing and compliance work 
• Your priority is to reduce operational overhead, accelerate global expansion, and mitigate risk 
• You're entering markets where local tax registration, VAT compliance, and dispute management would otherwise fall entirely on your team

Be it a MoR you’re working with, a PSP, or both, how you use them matters as much as which one you pick. A few best practices can help you out.

If you're using a PSP

• Test your integration in a sandbox environment before going live. Verify functionality before real customers are involved.
• Prioritize a PSP with fast settlement times. Delays in receiving funds can strain your cash flow.
• Make sure your PSP is PCI DSS compliant and offers good fraud detection tools. You can’t compromise with security. 
• Build your compliance infrastructure in-house or with legal counsel, as your PSP won't do it for you.

If you're using an MOR

• Clarify upfront exactly which markets and tax jurisdictions the MOR covers. Not all MORs operate everywhere.
• Ask for a clear breakdown of all fees. Some MORs absorb PSP costs inside their rate, while others pass them through as separate line items. 
• Ensure the MOR has infrastructure in place for dunning management and automatic card updaters if you run a subscription model, basic recurring billing isn't enough.
• Review the contract for revenue remittance schedules. Know exactly when and how your net revenue reaches you after deductions.

The choice between a PSP and an MOR depends on which one fits where your business is right now. A PSP gives you the infrastructure to get started quickly and keep costs lean. An MOR gives you the coverage to scale without the compliance burden catching up with you. Neither is the wrong answer. The wrong answer is picking one without understanding what you're actually signing up for.

For Indian businesses receiving international payments, there's another layer to consider. Getting funds into India efficiently, compliantly, and without losing money along the way. Something Xflow does very well.

Xflow is a cross-border payment infrastructure built specifically for businesses bringing money into India. Transparent FX rates, same-day INR settlement, automatic and free e-FIRA generation, and APIs that integrate in under two weeks, so your payments infrastructure works as hard as the rest of your business. 

To learn more about Xflow, visit its website now!