Three models dominate the conversation when a business decides how to structure its payment operations: the merchant of record (MoR), the payment facilitator (PayFac), and payment orchestration. They are often discussed as if they were competing answers to the same question, but they solve different problems, sit at different layers of the payment stack, and carry very different tradeoffs on liability, control, tax, cost, and data ownership. Choosing among them (or combining them) shapes how much operational burden a business carries, how much margin it keeps, how much control it retains over the customer relationship, and how easily it can scale across markets.
The comparison below defines all three models precisely, sets them against every dimension that matters, and offers a decision framework for choosing the right one based on business stage, growth ambition, and where the business wants to sit on the control-versus-convenience spectrum.
Before the deeper analysis, the short version of each:
The essential distinction: MoR and PayFac are about who is responsible for the transaction and the compliance around it, while orchestration is about how transactions are routed and optimized across providers. This is why orchestration can coexist with the other two models rather than strictly competing with them.
A merchant of record is the legal entity authorized to sell goods or services to the customer and held responsible for the transaction. When a business sells through a third-party MoR, that MoR becomes the reseller of record: its name appears on the customer’s card statement, and it takes on the financial and legal liability for the sale.
The MoR model bundles a comprehensive set of responsibilities:
The appeal is obvious for businesses that want to sell globally without building the tax, compliance, and payments infrastructure themselves. A SaaS company selling into 40 countries would otherwise need to register for tax in each, monitor rate changes, file returns, and manage the compliance overhead. An MoR collapses all of that into a single relationship, in exchange for a percentage of each transaction.
The tradeoff is control and margin. The MoR takes a meaningful cut (typically higher than a pure payment processing fee), owns the customer payment relationship, controls the checkout to a significant degree, and sits between the business and its transaction data. For businesses whose payment optimization, customer insight, and retention execution are competitive advantages, handing those to an MoR can be an expensive trade. Common MoR providers include Paddle, and the Apple App Store and Google Play Store operate as MoRs for apps sold through them.
A payment facilitator (PayFac) is a service provider that holds a master merchant account with an acquiring bank and onboards businesses as sub-merchants underneath that master account. Instead of each business applying directly to a bank for its own merchant account (a process that can take weeks and requires underwriting, credit checks, and bank negotiation), businesses join the PayFac’s platform and begin processing payments quickly.
The PayFac model handles:
Stripe, Square, and PayPal built their growth on the PayFac model. It is the reason a new online store can start accepting cards in minutes instead of waiting weeks for a merchant account. The model is especially common in platform payments, marketplace payments, and vertical SaaS, where a platform wants to embed payments for the businesses operating on it.
The critical limitation, and the point that most surprises businesses, is tax. A PayFac generally does not calculate, file, or remit the business’s sales tax. The business remains the legal seller and stays fully responsible for tax registration, filing, and rate management. The PayFac simplifies payment acceptance, but the compliance and tax liability largely remain with the business. A PayFac also does not, by itself, provide the multi-provider routing and optimization that orchestration delivers, because the sub-merchant processes through the PayFac’s own infrastructure.
For the distinction between the PayFac approach and a traditional payment service provider setup, Gr4vy’s guide on what a PSP does covers the underlying roles.
Payment orchestration is a technology layer that sits between a business’s checkout and the underlying payment providers, connecting to multiple PSPs, acquirers, fraud tools, and payment methods through a single integration and routing each transaction intelligently across them. Unlike the MoR and PayFac models, orchestration does not change who is legally responsible for the transaction. The business remains the merchant, keeps full ownership of its provider relationships and transaction data, and retains liability, while gaining flexibility and optimization.
Payment orchestration handles:
The orchestration model is built for businesses that treat payments as a strategic function rather than a commodity. It keeps the business in control of the customer relationship, preserves margin by enabling competition among providers, and unlocks the authorization rate improvements that come from routing each transaction to the provider most likely to approve it. For a full treatment, see Gr4vy’s guide on what a payment orchestration platform is.
The distinction from a PSP specifically (a common point of confusion) is covered in Gr4vy’s guide on the difference between payment orchestration and a PSP.
The three models across every dimension that matters for a structural decision:
| Dimension | Merchant of Record | Payment Facilitator | Payment Orchestration |
|---|---|---|---|
| What it is | Legal seller of record | Master merchant onboarding sub-merchants | Technology routing layer across providers |
| Who is the legal seller | The MoR | The business (sub-merchant) | The business |
| Whose name on the statement | The MoR | Usually the business or PayFac descriptor | The business |
| Tax responsibility | MoR handles fully | Business retains | Business retains |
| Chargeback and dispute handling | MoR handles | Shared, largely business | Business, with tooling support |
| Fraud liability | MoR absorbs | Largely business | Business, with tooling support |
| Speed to launch | Fast | Fastest | Moderate (integration required) |
| Control over checkout and UX | Limited | Moderate | Full |
| Ownership of transaction data | Limited | Moderate | Full |
| Multi-provider routing | No (MoR’s providers) | No (PayFac’s infrastructure) | Yes, core capability |
| Margin impact | Highest cost | Moderate | Lowest per-transaction, preserves negotiating power |
| Vendor lock-in risk | Highest | Moderate | Lowest |
| Best for | Global sellers wanting to offload tax and compliance | Small businesses and platforms wanting fast onboarding | Enterprises optimizing performance and retaining control |
The pattern across the table: the MoR model trades the most control for the most offloaded complexity, the PayFac model trades some control for speed and simplicity, and orchestration retains the most control while adding optimization and flexibility.
The clearest way to understand the three models is to place them on a spectrum from maximum convenience to maximum control.
Maximum convenience (MoR). The business offloads tax, compliance, chargebacks, fraud, and the legal seller role. In return, it gives up control over the customer payment relationship, accepts a higher cost, and cedes ownership of much of its transaction data. This is the right trade for businesses whose priority is entering many markets fast without building infrastructure, and whose payment operations are not a source of competitive advantage.
Middle ground (PayFac). The business gets fast onboarding and simplified payment acceptance while remaining the legal seller. It keeps more control than under an MoR but still processes through the PayFac’s infrastructure and retains tax and much compliance responsibility. This is the right trade for early-stage businesses prioritizing speed, and for platforms embedding payments for the businesses on them.
Maximum control (orchestration). The business keeps the legal seller role, full data ownership, full checkout control, and its own provider relationships, while gaining multi-provider routing, optimization, and redundancy. In return, it takes on an integration project and retains tax, compliance, and liability responsibility. This is the right trade for enterprises whose payment performance materially affects revenue and who want to preserve negotiating power across providers.
The spectrum also explains why the models are not mutually exclusive.
Yes, and increasingly they are. The models operate at different layers, which means a business can use more than one at once.
MoR plus orchestration. A growing pattern is for businesses to use the MoR model for tax and compliance offloading in complex markets while running orchestration underneath to optimize routing and retain data visibility. Some modern MoR providers build orchestration-style infrastructure into their offering (connecting multiple processors, supporting local payment methods, and routing transactions), which blurs the line between the two. The strategic question becomes how much control the business wants to keep versus how much complexity it wants to offload.
PayFac plus orchestration. A platform operating as a PayFac for the businesses on it can run orchestration underneath to route the aggregate transaction volume across multiple acquirers, improving authorization rates and adding redundancy for all its sub-merchants at once.
The key insight: because orchestration is a technology layer rather than a legal or liability structure, it can sit underneath either of the other two models. The choice between MoR and PayFac is a question about liability and compliance structure; the choice to add orchestration is a question about routing, optimization, and control. They answer different questions.
The right choice depends on business stage, growth model, and strategic priorities.
A few points of confusion come up repeatedly when businesses evaluate these models.
“Orchestration and MoR are alternatives to each other.” They operate at different layers. MoR is a liability and compliance structure; orchestration is a routing technology. A business can use both. The real question is how much control to keep versus how much complexity to offload.
“A PayFac handles my taxes.” Generally it does not. The business remains the legal seller under a PayFac model and stays responsible for tax calculation, filing, and remittance. This is the single most common surprise for businesses that chose a PayFac expecting MoR-style tax handling.
“An MoR gives me the best authorization rates.” Not necessarily. Authorization rate optimization comes from routing each transaction to the provider most likely to approve it, which is an orchestration capability. An MoR uses its own provider relationships, which the business does not control or optimize directly.
“Orchestration is only for very large enterprises.” Orchestration produces the largest returns at high volume, but the flexibility, redundancy, and data ownership benefits apply well below the enterprise tier. The break-even depends on volume, market complexity, and how much payment performance affects the specific business.
“Choosing one model locks me in forever.” The models can be migrated between and combined. A business might start with a PayFac for speed, add orchestration as volume grows, and use an MoR for specific complex markets. The structure should evolve with the business.
Cost structure differs meaningfully across the three models, and it is one of the most important factors in the decision.
Merchant of record typically carries the highest cost, because the MoR is absorbing tax compliance, fraud liability, chargeback management, and the legal seller role, and prices accordingly. The MoR’s fee is usually a percentage of each transaction that exceeds pure payment processing costs. For businesses that would otherwise spend heavily on tax compliance infrastructure and international expansion, the all-in cost can still be favorable, but the headline per-transaction rate is the highest of the three.
Payment facilitator costs sit in the middle. The PayFac’s pricing (often a flat rate or a percentage plus fixed fee) is simple and predictable, which suits smaller businesses, but it is typically less favorable at scale than negotiated direct processing rates. As volume grows, the convenience premium of the PayFac model becomes more expensive relative to alternatives.
Payment orchestration carries a platform cost but preserves the most margin at scale, because it lets the business negotiate directly with providers, route to the lowest-cost qualified provider for each transaction, and capture the authorization rate improvements that come from intelligent routing. For high-volume businesses, the routing optimization and provider competition that orchestration enables typically more than offset the platform cost.
For a broader treatment of how payment costs break down, see Gr4vy’s guide on payment compliance and regulations and the related discussion of international card acquiring.
A merchant of record becomes the legal seller of the goods or services and takes on full responsibility for tax, compliance, chargebacks, and fraud. A payment facilitator holds a master merchant account and onboards businesses as sub-merchants, simplifying payment acceptance but generally leaving the business as the legal seller responsible for its own tax and much of its compliance. The core difference is liability: an MoR assumes it, a PayFac largely does not.
No. A merchant of record is a legal and liability structure where a third party becomes the seller and assumes tax and compliance responsibility. Payment orchestration is a technology layer that routes transactions across multiple providers while the business remains the merchant and keeps liability, control, and data ownership. They operate at different layers and can be used together.
Generally no. Under a payment facilitator model, the business remains the legal seller and stays responsible for calculating, filing, and remitting its own sales tax, VAT, or GST. This is different from a merchant of record, which does handle tax across jurisdictions. The tax distinction is the most common source of confusion between the two models.
Yes. Because orchestration is a technology layer rather than a liability structure, it can operate underneath a merchant of record arrangement. A business might use an MoR to offload tax and compliance in complex markets while running orchestration to optimize routing and retain data visibility. Some modern MoR providers build orchestration-style routing into their own infrastructure.
Payment orchestration typically produces the best authorization rates because it routes each transaction to the provider most likely to approve it and adds retry and failover logic across multiple providers. A merchant of record uses its own provider relationships that the business does not control directly, and a payment facilitator processes through its own infrastructure, so neither offers the multi-provider routing that drives authorization optimization.
It depends on volume and complexity. A payment facilitator is often cheapest and simplest for low-volume businesses. A merchant of record carries the highest per-transaction cost but can be cost-effective for businesses that would otherwise build expensive global tax infrastructure. Payment orchestration preserves the most margin at higher volume because it enables direct provider negotiation and lowest-cost routing, offsetting its platform cost.
Not usually. A payment facilitator simplifies payment acceptance under a master merchant account but leaves the business as the legal seller. A merchant of record becomes the legal seller itself. Some providers combine elements of both, and some PayFacs act as the merchant of record for their sub-merchants in specific arrangements, but the two models are structurally distinct.
Many global SaaS businesses use a merchant of record to offload the substantial burden of global tax compliance, since selling digital goods into many countries creates complex tax registration and filing obligations. However, SaaS businesses that treat payment performance and customer data as competitive advantages often prefer orchestration, sometimes combined with an MoR for the most complex markets, to retain control while still managing compliance complexity.
No. Payment orchestration sits above your PSPs and routes transactions across them. You keep your PSP relationships (and can add more), and the orchestration layer decides which one processes each transaction. This is different from replacing a PSP; orchestration coordinates multiple PSPs rather than substituting for them.
The common trigger is scale. As transaction volume grows, the flat convenience pricing of a PayFac becomes more expensive relative to negotiated direct processing, and the lack of multi-provider routing starts to cost measurable authorization rate and redundancy benefits. Businesses often add orchestration when payment performance becomes material to revenue or when they want to add a second provider.
Marketplaces have used all three depending on their structure. Many operate as payment facilitators for their sellers, some use a merchant of record model, and many run orchestration underneath to route the aggregate volume across multiple acquirers for better authorization rates and redundancy. The right structure depends on who the marketplace wants to be the legal seller and how much payment optimization matters to its economics.
The choice among merchant of record, payment facilitator, and payment orchestration is really two decisions. The first is a liability and compliance decision: how much of the tax, regulatory, and fraud burden does the business want to offload, and is it willing to give up control and margin to do so? That decision points toward an MoR (offload the most), a PayFac (offload some, gain speed), or keeping the responsibility in-house. The second is an optimization decision: does the business want to route transactions across multiple providers to improve authorization rates, reduce cost, and add redundancy? That decision points toward orchestration, which can sit underneath whichever liability structure the business chooses.
For businesses whose payment performance materially affects revenue, and who want to keep control of the customer relationship and transaction data, orchestration is the layer that delivers optimization without giving up ownership. It coexists with the other models rather than forcing an either-or choice.
Gr4vy’s cloud-native payment orchestration platform connects a business to more than 400 PSPs and payment methods through a single integration, routing each transaction intelligently while the business keeps full control, ownership, and flexibility. If you’re weighing these models for your own payment operations, contact our team for a walkthrough of where orchestration fits alongside or instead of the other approaches.
A customer sees a charge on their card statement they do not recognize, or a…
Payment orchestration sits at the intersection of two fast-moving trends: the shift of nearly all…
San Mateo, July 28: Wizlo, the operating system powering end-to-end telehealth infrastructure for modern e-commerce…
Picture a large retailer on the busiest sales day of its year. Its single acquiring…
Every time a customer pays with a card, an invisible piece of infrastructure does the…
Payment orchestration is easier to understand through what it does than through how it is…