Embedded Payments for Platforms and ISVs: What's the Difference Between a PayFac and an MSP?

Quick answer: A payment facilitator (PayFac) enables a platform to onboard its users as sub-merchants under a master merchant account, while a merchant service provider (MSP) typically helps individual businesses obtain and manage their own merchant accounts.

Your users have high expectations, and you want to meet them. So what would make for the best user experience? If your users could onboard, accept payments, and manage transactions all without ever having to leave your software.

The challenge comes when you look at how to make that happen. It raises the questions: who handles onboarding, underwriting, fraud, and payouts behind the scenes?

This is the decision platforms and independent software vendors (ISVs) face when they add embedded payments. Pick the wrong model, and you might take on compliance work you weren't ready for or lose control over the experience your customers see. Pick the right one, and embedded payments become a steady revenue line.

So, let's explore the details of what embedded payments actually are, how a PayFac differs from an ISO/MSP, and how to choose the model that fits your platform.

What are embedded payments?

Embedded payments are payments built directly into a software product, so users can pay or get paid without ever having to leave the platform.

It's a bit like a scheduling app that lets a salon collect payment at checkout, or a marketplace that moves money between buyers and sellers automatically.

Common examples include:

• SaaS platforms accepting payments on behalf of their customers
• Vertical software letting businesses take payments inside the app
• Marketplaces facilitating transactions between buyers and sellers

ISVs add embedded payments because it creates a better customer experience, removes disconnected third-party tools, and opens a new revenue line.

One important distinction before moving on: embedded payments describe what the customer sees, e.g., payments built into your software. PayFac, ISO/MSP, and PayFac-as-a-Service describe how your platform operates those payments behind the scenes. Same front end, very different back-end structures.

Embedded payments vs. traditional payments

The main difference is how much of the payment experience your platform is responsible for.

Embedded payments connect your software to a payment processor through an API. Basically, this means that your transactions happen inside your product instead of redirecting users to a third-party checkout. The processor handles the movement of money, while your platform controls the experience.

With traditional payments, a merchant signs up directly with a processor and uses a separate portal. Embedded payments keep everything, from onboarding to reporting, inside your platform.

What is a PayFac?

A payment facilitator (PayFac) is a master merchant that onboards other businesses as sub-merchants under one shared merchant ID.

Instead of each sub-merchant applying for their own account, your platform does the heavy lifting. As a PayFac, your platform will be responsible for:

• Merchant onboarding and KYC/KYB verification
• Underwriting
• Risk and fraud monitoring
• Chargebacks and disputes
• PCI DSS and card network compliance
• Settlement and funding

A PayFac still operates under a sponsor acquirer. The difference is who owns onboarding, underwriting, and risk, not independence from the acquirer.

This model gives your platform more control over the entire experience. You'll be able to manage onboarding, create a fully branded experience for your users, have much greater pricing flexibility, and retain a larger share of payment revenue.

It is a major commitment, not a small step up: registration, a sponsor bank relationship, a compliance team, and capital. In return, you get to give your users a more customized experience.

Understanding ISO/MSPs

An ISO/MSP is a business registered through a sponsor bank to sell merchant processing on an acquirer's behalf.

ISO (independent sales organization) is Visa's term, while MSP (member service provider) is Mastercard's term for the same role.

Together, they form the industry term "ISO/MSP." This model typically earns residuals on the processing volume it brings in. The acquirer owns underwriting and the risk book, while the ISO/MSP still operates under network rules and sponsor oversight.

PayFac vs ISO/MSP: a side-by-side comparison

Does my platform need to be a PayFac to make money from embedded payments?

No. A common misconception is that a platform has to register as a PayFac to earn from embedded payments. This isn't true.

There are several other ways to share in payment revenue: revenue-sharing agreements, processing markups, formal partner programs, or a PayFac-as-a-Service arrangement. With the latter, a provider handles the PayFac responsibilities while your platform still earns a cut.

How do you choose the right embedded payments model?

Now that you've seen what options are available, how do you choose which is right for your platform? Start by asking these questions:

• Payment volume: Is there enough volume to justify the investment?
• Merchant count: How many businesses will you onboard and support?
• Control: Do you need to own underwriting, pricing, and payout timing?
• Time to market: How quickly do you need embedded payments live?
• Internal expertise: Do you have payments, risk, and compliance staff?
• Operational burden: Who handles disputes and merchant support?
• Revenue goals: Is this a feature, or a real revenue line?

If most of your answers pointed toward speed, simplicity, and limited internal resources, a managed model is likely your starting point. If you found yourself circling control, margin, and scale, a PayFac path deserves a closer look.

Most platforms begin with a managed-payments partner as a simpler option, then revisit the question of greater control once volume and internal capability justify the investment.

Frequently asked questions

Know your payment options

You do not need to become a full PayFac to unlock new revenue. But the model you pick decides how much compliance, risk, and control you take on, and that decision is expensive to reverse.

Canyon Payments helps platforms and ISVs choose the model and build it: the integration, the onboarding flow, the gateway connector, and the migration if you switch later. We also support ISVs who want a PayFac-like model without registering as a PayFac: the branded, in-platform experience for your users, with underwriting and compliance sitting with the sponsor or provider behind it. If you are weighing a PayFac path against a managed model, talk to us before you commit to the compliance build.