MoR vs PSP: When the Premium Beats Doing It Yourself

Businesses selling digital products across borders need to identify which party is the seller and which entity has each tax, payment and dispute obligation. The answer depends on the product, customer, jurisdiction, transaction structure and contract. A PSP can process the payment; an MoR may act as seller for covered transactions and provide additional services.

This is the question that determines whether you use a Merchant of Record or a direct PSP. It is not a technical question — both systems can process the same transaction. It is a question about which entity carries which liability.

What a Merchant of Record Actually Is

A Merchant of Record (MoR) is generally the seller in the transactions it handles. It may sign customer-facing terms, appear on statements, and take on specified tax and payment duties, depending on the product, transaction, applicable law and agreement. In a typical card arrangement, the MoR is presented to the network as the merchant and manages disputes; the contract may pass costs or other responsibilities back to the underlying seller.

The underlying seller — typically a SaaS company, digital product creator, or developer tools vendor — supplies the product and brand, and may supply it through a reseller arrangement with the MoR, depending on the contract. The MoR pays the seller a net amount after its fees, taxes collected, and any other deductions specified in the agreement.

A PSP can process a payment without becoming the seller. In a direct PSP arrangement, the business commonly remains the seller and is responsible for tax, refund, dispute and other seller duties that applicable law and contract assign to it. An aggregated payment facilitator arrangement has its own structure and should not be assumed to be a MoR arrangement.

The key distinction is how the sale is structured and which party is responsible for each duty. An MoR may act as seller for the transactions it handles and take on specified customer-facing, tax and payment-operation duties. The underlying seller can retain product, contractual and other legal responsibilities, and the MoR agreement may provide recourse against the seller. A direct PSP ordinarily processes payment without becoming the seller; confirm the allocation under the relevant law and contract.

What the MoR Premium Actually Buys

MoR pricing often bundles services beyond payment processing, and may cost more than direct PSP processing. The total price varies by provider and product line, and changes often; compare current quotes and contract terms for the same transaction mix. Structures may include flat take rates, transaction fees, volume tiers or separate currency-conversion charges.

The more useful question is structural: what does the premium buy that you would otherwise have to build, buy, or absorb? In the typical MoR-versus-PSP comparison, the premium covers some or all of the following:

Tax registration, collection, and remittance within the agreed scope. Cross-border tax duties vary by jurisdiction, transaction, buyer and seller. For example, the EU One-Stop Shop (OSS) can simplify filings for eligible transactions, but it does not make every platform or MoR the liable supplier; some marketplaces are treated as suppliers only in specified cases. US state sales-tax duties depend on current nexus rules, product taxability and the entity legally responsible for the sale. A MoR may undertake specified registration, collection, filing or remittance duties under its product terms and applicable law. Confirm the covered transactions and any seller duties that remain. A direct PSP may offer tax tools, but payment processing or tax software alone does not establish that tax liability has transferred.

Fraud and chargeback operations. In a typical MoR arrangement, disputes are presented to the MoR as the network-facing merchant, and the MoR may provide screening and dispute handling. The agreement may pass dispute amounts, fees or other costs to the underlying seller. Card-network monitoring is governed by the applicable rules and account structure; do not assume that all network consequences stop with the MoR.

Tax invoices and records. Invoice and record requirements vary by jurisdiction and transaction. An MoR may issue invoices and maintain records for the sales it handles, subject to the product and applicable requirements. Confirm what it generates and what the seller must retain or provide.

Currency conversion and seller payouts. Some providers consolidate payouts or convert currencies. Confirm supported payout currencies, conversion pricing, timing and any additional fees for the chosen product. Direct PSPs may also offer these features, with availability and cost varying by provider.

Refund and dispute handling. The MoR may operate the customer refund and dispute workflow for covered transactions. The provider's policy and contract determine its decision rights, seller input and any refund or dispute amounts charged back to the seller.

Where MoR May Fit

These seller situations can make an MoR worth evaluating.

Indie developers, solo founders, and small SaaS companies selling globally from day one. The work of handling applicable digital VAT, US state sales tax and payment disputes can be significant. For a small team, an MoR's price may compare favorably with the cost of building and maintaining the services that its contract actually covers. A detailed comparison of MoR providers — Paddle, Polar, Lemon Squeezy, and FastSpring — shows how their products differ.

Digital product creators and information products. Course sellers, plugin and theme developers, AI-product builders, and digital marketplace operators may have lean finance operations. An MoR can handle specified tax and payment duties for eligible transactions, but sellers should verify residual responsibilities and contract recourse.

Companies launching into new markets quickly. An MoR can simplify market entry where it supports the product and jurisdiction and accepts the seller. Confirm the provider's coverage, onboarding decision, tax scope and any seller obligations. Some businesses use an MoR while assessing demand, then move transactions to direct PSP arrangements if the economics and compliance capacity justify it.

Where a Direct PSP May Fit

These seller situations can make a direct PSP worth evaluating.

High-volume sellers with mature finance operations. At sufficient scale, the MoR price may exceed the cost of assembling the relevant tax, dispute and payment operations internally or through specialist providers. There is no universal GMV threshold: the comparison depends on the jurisdictions, products, provider pricing, internal staffing and the duties the MoR agreement actually covers. Operators considering direct PSP should also review PSP contract red flags before signing.

B2B sellers with custom invoicing and contracting requirements. Enterprise B2B customers often require invoices issued directly from the vendor, contractual line items specific to the customer, custom payment terms (net-30, net-60, milestone billing), and frequently negotiate the underlying contract with the seller, not the MoR. MoR makes this awkward. The accounts-payable team at the buyer expects to see the vendor brand as the payee, and the contract holder is the vendor, not the MoR.

Regulated industries and marketplace operators. Financial services, regulated digital assets, healthcare and similar sectors may face licensing, contracting or product rules that make a third-party MoR unsuitable or unavailable for a particular flow. Marketplaces also have distinct seller and funds-flow structures and may need payment facilitator or marketplace-specific arrangements (such as Stripe Connect or Adyen for Platforms). Map the parties and obligations for the actual setup before selecting a model.

The Hybrid Pattern

The cleanest operator outcome is often neither MoR-only nor PSP-only but hybrid.

A common split: direct PSP for the home market (where the company already has tax registration and a finance team), MoR for the rest of the world (where the compliance overhead would be disproportionate to the early revenue). As specific international markets cross revenue thresholds, they migrate one at a time off MoR onto direct PSP plus tax automation.

Another split: by customer segment. Self-serve and SMB customers — the high-volume, low-touch segment where chargeback exposure is highest and tax complexity per dollar is highest — go through MoR. Enterprise contracts, which expect direct invoicing relationships and negotiated payment terms, go through direct PSP.

A third split: by payment method. Cards and global wallets go through MoR for the compliance package. Local A2A rails (Pix, UPI, local bank transfers) that the MoR does not yet support go through direct relationships in those markets, or through specialised local providers.

The hybrid stack has integration overhead — two payment systems, two reconciliation flows, two reporting surfaces — but it is often the most operationally honest configuration once a company has grown past pure MoR but has not yet justified a full in-house compliance build.

The Decision Framework

The right question is not "MoR or PSP" in the abstract — it is which infrastructure cost dominates for the specific business.

Start with the inventory of jurisdictions you sell to today and plan to enter in the next 12 months. For each, establish whether the product, customer type, transaction and volume create registration, collection, filing or invoicing duties, and which entity is responsible. Thresholds, marketplace rules and simplified schemes vary, so do not assume a single answer based on country alone.

Then count the headcount, software cost, and external advisor cost to build that compliance stack in-house. If that cost exceeds the MoR premium for your projected GMV, MoR is cheaper. If it is meaningfully below, direct PSP plus tax automation is cheaper.

Layer in the non-cost factors. Customer trust and statement branding: does the MoR brand on the statement create friction in your buyer's purchasing experience? Customer data ownership: does the MoR's standard arrangement restrict your access to customer email, billing data, or transaction history in ways your marketing or product team needs? Refund and dispute control: do you need direct authority over refund decisions, or are you comfortable with the MoR's policy?

Finally, the cost of optionality. Data access, export and migration obligations are contract-specific. Moving a billing relationship to a direct PSP may require customer action or payment-credential reauthorization; confirm the provider's technical and contractual exit path before estimating migration cost. The cost of staying on an MoR longer than needed is its premium. Leaving too early may require infrastructure that is not yet economical to operate.

A Note on the Stripe-Owned MoR Players

Stripe said in 2025 that it acquired Lemon Squeezy in 2024 as part of building Stripe Managed Payments, its merchant-of-record offering. That ownership does not establish a supported self-service migration from a Lemon Squeezy account to direct Stripe processing. Ask for the actual customer-data, subscription, payment-credential and tax-record exit path before assuming a switch will be simple.

When comparing providers, verify the specific product and contracting entity. An MoR offering and a payment-processing offering can assign different responsibilities, even within the same provider group.

When to Reassess

MoR-versus-PSP is not a one-time decision — understanding when a Merchant of Record stops making sense is as important as the initial selection. Reassess at three triggers.

First, when annual GMV approaches the point where the MoR premium exceeds the cost of an in-house compliance team plus tax-automation tooling. This is usually visible in the finance model before it shows up in the bank account, and the migration is significant enough that planning 6-12 months ahead is the right cadence.

Second, when the customer mix shifts toward segments that fit MoR poorly. A consumer-first SaaS company that signs its first enterprise contracts often finds the MoR-on-statement issue arises quickly. Either route enterprise through direct PSP from the start, or accept that the first dozen enterprise customers will be on MoR while you build the direct relationship.

Third, when the MoR's product gaps become commercially material. If the MoR does not support a critical payment method in a market that has become important to you — local A2A rails, regional wallets, specific buy-now-pay-later products, country-specific schemes — the friction outweighs the compliance value, and a direct relationship in that market (full or partial) is the answer.

The MoR question is structural. It is not "which payment vendor is cheapest" but "which entity carries which liability, and at what scale does each model break even." Answering it from the liability side first, and the pricing side second, gives you the answer that survives the next 24 months of growth — instead of one that has to be revisited every time the take-rate calculation shifts.