If you’re evaluating merchant of record providers, you’ve probably noticed they all lead with the same promise: hand us the transaction, and we’ll take the hard parts off your plate. Tax compliance, fraud management, disputes, cross-border complexity: all handled, so you can focus on your product.

That pitch can be compelling, but before you commit, it’s worth asking what you’re actually signing up for. Platforms that have gone down the MoR route often find themselves running into problems they didn’t anticipate:

• Merchants are confused about who they actually paid, and the support tickets land with you
• Disputes and refunds follow policies you didn’t set and can’t change
• Payouts are delayed or held for reasons outside your control
• Payments feel like a bolted-on feature rather than a native part of your product
• Your ability to monetize payments is capped, because a third party controls the commercial layer

None of this shows up in the sales process. It shows up later, when payments are already embedded in your product and switching is painful.

This article will walk you through what merchant of record actually means in practice, when it’s the right call, and when it isn’t, so you can make the right decision before you’re locked in.

We’ll cover:

• What is a merchant of record (MoR)?
• When MoR makes sense, and when it doesn’t
• What you actually lose when an MoR sits in your transaction
• Why embedded payments can often be a better model for vertical SaaS
• Why use Fiska for embedded payments?

Fiska is an embedded payments platform built exclusively for SaaS platforms. Read on to find out more about us, or book a call here.

What is a merchant of record (MoR)?

A merchant of record is the legal entity responsible for the transaction with the end customer.

In a typical MoR provider setup, the MoR sits in the payment flow as a reseller. The buyer purchases from the MoR, the MoR processes the payment, and then remits funds to you.

Because the MoR is legally responsible for the sale, it typically owns liabilities like:

• Tax compliance (sales tax, VAT, GST)
• Chargebacks, disputes, and refunds (under their policies)
• Fraud management and risk controls
• Payment compliance obligations tied to checkout and payment data

The main benefit of MoR is that it outsources this operational burden.

But that structure also changes what you can control as a platform: because the MoR needs authority over parts of the experience and the policy layer to manage its own risk.

That trade-off is fine when compliance is your main bottleneck. But this loss of control can become a real problem when embedded payments are crucial to your SaaS platform.

When MoR makes sense, and when it doesn’t

When MoR is worth it

MoR is often worth it when the main thing you sell is your own product to end users, and your biggest concern is solving the admin that comes with selling it globally.

In particular, MoR tends to make sense if you are:

• Selling SaaS subscriptions or digital products directly to end customers (not merchants)
• Expanding into multiple countries or US states, and tax compliance is becoming a blocker
• Prioritizing speed and simplicity over margin and customization
• Willing to accept a more standardized payment and billing setup in exchange for outsourcing the hard parts

Why the merchant of record model doesn’t make sense for most vertical SaaS platforms

For vertical SaaS platforms, your goal isn’t just to process payments: it’s to embed payments into your product as a native feature, and build a revenue stream around them. MoR tends to constrain that.

That’s because to manage risk, the MoR needs to control key parts of the payment experience, such as:

• How the buyer sees the transaction on statements, receipts, and invoices
• What your users experience when a refund, dispute, or compliance review happens
• How quickly funds are released, and what triggers holds or reserves
• How pricing and fees are presented, and what flexibility you have to package payments into your product

For a vertical SaaS platform, this means relinquishing a lot of control. As a result, you can end up with a payment offering you can’t fully shape, improve, or monetize: even though it lives inside your platform and affects your brand.

MoR can mean less control over your monetization model

Because MoR providers sit between you and the commercial layer of the transaction, it’s hard to package payments into your pricing, set your own margins, or build a revenue model that improves as your volume grows.

You can’t easily:

• Package payments into your subscription tiers
• Decide how you present pricing and fees to your merchants
• Improve your take rate as transaction volume scales
• Use payments to increase ARPU without overhauling your core SaaS pricing

Payments end up as a pass-through cost rather than a revenue lever.

Likewise, when disputes, holds, or payout delays occur, the resolution lies with the MoR. You end up fielding support tickets for problems you don’t own and can’t fully resolve. Your merchants get pulled into someone else’s policies, communications, and support paths: but they think of it as your product. That friction can erode trust in your platform.

Why embedded payments can be a better solution for many vertical SaaS platforms

Embedded payments give you what MoR trades away: control over the experience, ownership of the commercial model, and the ability to build payments into your product as a genuine feature without turning payments into a second business.

Payments become part of the product, not a separate system

Embedded payments let you design the payment journey around your vertical, so it feels native rather than bolted on. In vertical SaaS, payment events live inside operational workflows: invoices, deposits, booking refunds, tips, in-person and online transactions. If you can’t shape those flows, payments stay external to your platform instead of driving adoption and retention.

You keep control over pricing and monetization

With embedded payments, you decide how to package payments into your tiers, what you charge merchants, and how your margin improves as volume grows. That’s difficult when a third party controls the commercial layer of the transaction.

You completely own the customer relationship

Your platform stays the primary experience. Users aren’t pulled into someone else’s policies or support paths, and your brand stays front and center throughout the payment journey, not just around it.

Why choose Fiska for embedded payments

Fiska specializes in helping software platforms monetize payments and improve the in-app experience.

Here’s what you get when you use Fiska:

1. Turn payments into a growth driver, with a true revenue-share model

With providers like Stripe, your costs are fixed, your margins are capped, and you have little influence over how payment revenue scales as your platform grows. Even at high volumes, payments can remain a pass-through cost rather than a meaningful revenue stream.

Fiska operates a true revenue share, splitting the total payment revenue generated above interchange. This gives you control without forcing you to change how you price your merchants. You can continue to offer simple, fixed pricing while financially benefiting from the value created by payments.

We also never charge platform fees, so we only earn when you do.

What you get:

• A clear baseline cost (interchange-based)
• Flexibility to set your own merchant pricing and packaging
• A revenue model that scales with adoption and volume, rather than capping your upside early

Read more: Why Fiska doesn’t charge fixed fees (and how our partnership model works)

2. Optimize your payment strategy without becoming a payments expert

Your focus should stay on building great software, not navigating the complexity of payments. Yet developing in-house payments expertise is expensive, time-consuming, and distracting.

Fiska gives you access to experienced payments leadership without expanding your team. We act as your fractional Head of Payments, working closely with your team to understand your product, commercial model, and growth plans.

Our discovery process is deliberately thorough, so we can design and implement a payment setup that fits your business and supports sustainable revenue as you scale. You can read more about how to get started with Fiska here.

When you need help, you can contact us via email, phone, video call, or even Slack.

Your team remains the first point of contact for merchants, handling everyday questions around onboarding, configuration, and product usage, so you retain full ownership of the relationship.

But if issues become more complex, such as technical failures, reconciliation challenges, or edge-case payment behavior, Fiska steps in as second-line support. Our specialists can work directly with your merchants to solve problems if you’re unable to.

3. A true omnichannel API built specifically for SaaS platforms

Legacy payment providers were not built for modern software companies. The result is fragmented integrations, inconsistent capabilities across channels, and documentation that slows development teams down.

Fiska is a software company at its core. Our single white-label unified API supports true omnichannel payments, including ecommerce and in-person transactions, through one integration. This reduces development effort, shortens time to market, and makes it easier to expand into new channels without re-architecting your payments stack.

Our platform and support model are designed by people who have built and operated SaaS products themselves, so the technology fits the way modern software teams work — not the other way around.

Read more: Omnichannel payment solutions for SaaS: A complete guide

Scale your payments without complexity with Fiska

MoR can be a strong fit if your goal is global SaaS billing and you want the simplest way to outsource tax and compliance.

But the argument for MoR breaks down when you’re a vertical SaaS platform trying to build embedded payments into your product. The model solves compliance by trading away control, and control is the foundation of everything you’re trying to build: a native payment experience, a scalable revenue stream, and a merchant relationship that stays yours.

Fiska helps you capture the revenue and branding control you need while we handle the infrastructure and operational heavy lifting. You get a world-class payments experience inside your platform, without adding operational overhead.

If you’re ready to turn payments into a growth lever rather than a constraint, let’s talk.

Book a call with our payment experts to find out how Fiska can help.

FAQ: Merchant of Record for SaaS platforms

Do vertical SaaS platforms need a MoR provider to embed payments?

No. Under the merchant of record model, the MoR takes legal responsibility for the transaction, including tax obligations, regulatory compliance, and fraud prevention. That can simplify global payment processing for SaaS businesses, but it is not required to embed payments into a vertical SaaS platform. For most vertical SaaS platforms, the trade-offs on control and economics can make it the wrong choice.

When does a MoR provider make sense?

Most often when you sell subscriptions or digital products globally, and your main constraint is global tax compliance, managing sales tax, VAT, and local tax across multiple jurisdictions. If your roadmap is embedded payments as a product, you should pressure test the MoR model’s trade-offs around control and economics carefully before committing, particularly if the checkout experience and customer experience are important to your platform.

Does a MoR provider manage subscriptions and recurring payments?

Yes. MoR providers typically handle subscription management, recurring billing, retries, and payment compliance as part of their model, including credit card and debit card retries, churn reduction logic, and customer data handling in line with standards like PCI-DSS and GDPR. The question is whether that approach fits your platform’s payments strategy and experience goals, or whether it limits them.

What’s the difference between MoR and embedded payments?

With the MoR model, a third party such as Paddle or Lemon Squeezy sits in the transaction as the seller of record, owning the liability and with it significant control over the checkout experience, payment options, and commercial layer. They act as both the payment processor and the merchant of record, handling currency conversion, international payments, and global tax compliance on your behalf.

With embedded payments, your platform stays the primary experience. You retain control over how payment methods are presented, how pricing is structured, and how customer support is handled when issues arise. You work directly with a payment service provider or payment gateway rather than routing transactions through a third party. The trade-off is that embedded payments require either more build effort or the right partner to handle the payment infrastructure for you.