What is a PayFac? Payment facilitators explained for platforms

Learn how the PayFac model works, the hidden costs of licensing in Europe, and why embedded payments are a faster, more pragmatic choice for SaaS.

Learn how the PayFac model works, the hidden costs of licensing in Europe, and why embedded payments are a faster, more pragmatic choice for SaaS.

What is a PayFac? blog banner

If you’re running a SaaS platform or marketplace in Europe, you’ve likely heard the term ‘payment facilitator’ (PayFac). It sounds powerful, even inevitable, like a milestone you’re supposed to reach once you hit a certain scale.

But the reality of becoming a PayFac is often quite different from the hype. While the model offers control and new revenue, it also introduces regulatory and operational complexity that can derail even the most focused product roadmap.

Let’s break down what a PayFac actually is, how the model works in the European context, and why most platforms are better served by an embedded payments approach. 

Key takeaways

  • A payment facilitator processes payments on behalf of other businesses under a centralised commercial and operational relationship with acquiring partners.

  • The model gives platforms control over the user experience and opens up new revenue streams.

  • Becoming a fully licensed PayFac in Europe is a slow, expensive process that requires 12 to 24 months and significant regulatory overhead.

  • Most SaaS platforms and marketplaces are better served by embedded payments, which provide the same benefits without the operational burden.

What is a payment facilitator?

A payment facilitator is a business that processes payments on behalf of other, smaller businesses. Traditionally, businesses needed direct business-acquiring relationships to accept card payments. Modern payment facilitators and PSPs simplify this by aggregating onboarding, compliance, and processing into a more streamlined experience.

A PayFac changes this by acting as an intermediary. They establish relationships with acquiring and regulated financial partners that allow them to onboard and manage sub-merchants more efficiently.

Imagine a commercial office building. In the old model, every startup that wanted a desk had to negotiate a long-term lease directly with the property owner, provide years of financial history, and wait for a board to approve them. A PayFac is like a flexible workspace provider that holds the master lease and lets tenants move in quickly, often within hours, because the provider has already handled the heavy lifting with the landlord.

For a restaurant software provider or a fitness booking platform, this means your users can start taking payments immediately. And it means you own the user experience, you can earn a margin on every transaction, and you make your software the central nervous system of your users’ businesses.

How does the PayFac model work?

In a standard setup, the flow of money is fragmented. A business connects to a gateway, which talks to a processor, which communicates with the banks and card networks. Traditionally, many businesses maintained direct contractual relationships with acquirers or payment providers.

In the PayFac model, you sit directly in the middle of that flow. The hierarchy looks like this:

  1. The card networks and banks: Provide the underlying infrastructure.

  2. The PayFac (you): Manages the sub-merchant relationship and assumes significant responsibility.

  3. The sub-merchants (your users): Operate under your umbrella.

By sitting in this position, you take on several responsibilities that used to belong to the bank. You take responsibility for onboarding, business due diligence, and fraud and compliance processes, whether directly or through regulated partners. If a sub-merchant disappears or goes bust, the financial liability often falls on you.

This is a fundamental change to your business model and legal standing.

PayFac vs. payment processor vs. payment gateway. What’s the difference?

These terms are often used interchangeably, but they shouldn’t be. Understanding the difference is vital.


Payment gateway

Payment processor

Payment facilitator (PayFac)

What it does

Securely captures and transmits payment data from the customer to the processor.

Processes and routes payment transactions between parties in the payment ecosystem.

Onboards and manages multiple sub-merchants under a centralised payments framework.

The role

The technology front door for payment data

The plumbing that moves the actual money

The business model layer is responsible for its sub-merchants

Who it serves

Businesses, platforms, and processors

Banks, PayFacs, and large direct businesses

Platforms and marketplaces that want to embed payments

Onboarding

N/A

Slow (days or weeks per business).

Fast (minutes or hours for sub-merchants).

The key distinction here is that a PayFac is not just technology. It’s a business model, with real financial and regulatory responsibility attached, which must be weighed carefully against the benefits. 

Why platforms find the PayFac model appealing

The attraction of PayFac for SaaS founders and product leads usually boils down to three things: revenue, control, and stickiness.

Payments are a high-margin, recurring revenue stream that scales with your user base as your platform grows. For many SaaS companies, payment revenue can eventually match or even exceed subscription revenue. It’s one of the main reasons investors find the embedded payments story so compelling.

Control means owning the full experience. When you handle payments, you control onboarding speed, checkout design, settlement timing, and how data flows back into your product. You no longer have to redirect users to a third-party payment page because everything lives inside your platform.

Stickiness is arguably the most powerful of the three. When a business's revenue flows through your software, switching to a competitor becomes a genuine operational risk. Churn drops, lifetime value rises, and your platform starts to function less like a tool and more like infrastructure. 

The spectrum: you don’t have to go all-in

Becoming a full PayFac isn’t a binary choice. There’s a spectrum, and most European platforms find their best fit somewhere in the middle.

Option 1: The referral model

You simply point your users to a third party. They sign up elsewhere, and you might get a small kickback.

  • The pros: No work, no risk.

  • The cons: You lose control over the brand, the user leaves your app to manage their money, and the revenue is negligible.

  • Best for: Very early-stage platforms testing the importance of payments.

Option 2: Embedded payments (PayFac-as-a-Service)

This is where you partner with a licensed provider that lets you embed the entire payment experience into your platform. They hold the licences and manage the compliance, KYC and risk, but you control the user interface and earn a meaningful revenue share.

  • The pros: You go live in weeks, not years. You get the branding and revenue of a PayFac without the regulatory burden.

  • The cons: You share the margin with your partner.

  • Best for: Growth-stage and scaling platforms that want payment revenue and control without the operational overhead.

Option 3: Full PayFac (the regulated or sponsored route)

You take on substantially more regulatory, operational, and financial responsibility, whether through your own licences, acquiring relationships, or regulated sponsorship structures.

  • The pros: Maximum control and the highest possible margin per transaction.

  • The cons: Massive upfront costs, long timelines, and permanent regulatory scrutiny and operational overhead.

  • Best for: Very large platforms processing billions annually, where payments are a core strategic pillar.

When does becoming a full PayFac make sense?

There are certain scenarios where the build route is the right one. You should only consider a full PayFac license if:

  • You are processing billions in annual volume, where a few basis points of extra margin outweigh the cost of a 10-person compliance team.

  • Payments is your primary product.

  • You have at least two years of runway and the appetite to be a regulated financial institution.

If you don’t meet all three of those criteria, the embedded payments model is almost certainly your best strategic move, especially in Europe.

The European reality: why it’s harder than it looks

Most of the advice you’ll find online about PayFac is written from a US perspective. In the US, the path involves registering with card networks through a sponsoring bank. It’s a large project, but the regulatory burden is relatively straightforward compared to Europe.

In Europe, platforms offering PayFac-like experiences often operate either under their own PI/EMI licence, through a licensed payments partner, or via sponsorship/acquiring relationships with regulated providers. This means you are applying for authorisation from a national regulator, such as the Dutch Central Bank (DNB), or BaFin in Germany.

This is an ambitious undertaking for a software company. Here’s what you’re actually signing up for:

Regulatory requirements

In Europe, the regulatory landscape is different and more demanding:

  • EU payment services regulation, currently under PSD2 and evolving through PSD3 and the proposed Payment Services Regulation, governs payment services across the EU.

  • EMD2 applies if you’re issuing or storing electronic money, such as wallet balances or stored-value accounts.

  • Passporting lets you extend a licence obtained in one EU country across the bloc, but it’s not automatic and comes with additional requirements.

  • Local payment method complexity means you’re not just processing cards. iDEAL in the Netherlands, Bancontact in Belgium, SEPA Direct Debit, Klarna, and dozens of others all need to be supported if you want to serve European merchants properly.

  • SCA (Strong Customer Authentication) requirements add technical complexity to every transaction flow.

Legal costs

You’ll need specialised legal counsel to navigate the application. We’ve seen platforms spend between €200,000 and €500,000 just to get through the door. Then there are the capital requirements. An EMI licence typically requires a minimum initial capital of €350,000, and you’ll need to maintain ongoing capital levels tied to your transaction volume.

The 12-24 month timeline

In most European jurisdictions, the timeline from starting an application to receiving approval is 12 to 24 months. During this time, your payment strategy is essentially on ice. You may not be able to launch your intended operating model until regulatory approvals and partner arrangements are in place.

Compliance and operations

You become a regulated financial entity. This means you need a dedicated compliance officer, robust anti-money laundering (AML) programmes, and transaction monitoring systems. You have to handle suspicious activity reporting and ensure you meet the strict requirements of Strong Customer Authentication (SCA).

Opportunity cost

This is the hidden killer. Every engineer you have building a proprietary settlement engine or a KYC dashboard is an engineer who isn’t building your core product. For a scaling SaaS company, the biggest risk is that your competitors will out-innovate your core features while you’re busy learning the nuances of regulatory reporting.

The regulatory bar in Europe is high, the landscape is fragmented, and the local payment method ecosystem is complex. For most European platforms, the smarter move is finding an experienced payments partner who has already solved these problems.

Why choose Mollie instead of becoming a PayFac? A more pragmatic path

If you’ve read this far, you probably fall into one of two scenarios:

  • Scenario A: You definitely don’t need to become a PayFac, but you do want to embed payments and earn revenue from them.

  • Scenario B: You were considering the PayFac route, but now you’re rethinking the complexity and timeline.

Either way, the answer is the same: find a payments partner that gives you the benefits of the PayFac model – control, revenue, and seamless onboarding – without requiring you to become one. This is exactly what Mollie Connect is built for.  

Mollie Connect lets SaaS platforms and marketplaces embed payments directly into your products. Your users onboard seamlessly inside your platform. You earn revenue on every transaction. You control the experience. And we support the underlying payments infrastructure, including licensing, compliance processes, KYC workflows, fraud management, settlement, and European payments operations.

Here’s what that looks like in practice:

  • Customisable onboarding: Your users sign up through your platform, not ours. Their experience stays entirely within your ecosystem.

  • Managed compliance: Lean on our status as a licensed payment service provider. We handle KYC, AML, and regulatory obligations so you don’t have to.

  • Split payments and payouts: Route funds between buyers, sellers, and your platform automatically – a critical feature for marketplaces.

  • Flexible revenue models: Set your own commissions, earn on every transaction, and build a scalable payments revenue stream.

  • Broad European coverage: Access local payment methods, multiple currencies, and support across Europe’s key markets from day one.

  • More than just payments: Open the door to embedded financial services like Mollie Capital, giving your users access to funding directly through your platform.

On top of all this, we also deal with the Dutch Central Bank and other European regulators. We handle evolving European payment security and SCA requirements. And because we were built in Europe, we have native support for the local payment methods your users actually need.

The other benefit is time. Instead of waiting 18 months for a licence, you can be live and generating revenue in a matter of weeks. You keep your engineers focused on what makes your software unique, while we provide the regulated financial infrastructure that makes it scale.

Ready to see how it works?

If you want to monetise payments and control your user experience without the multi-year licensing hurdle, we’re here to help. Schedule a quick call with our platform specialists to explore how Mollie Connect fits your roadmap.

FAQs: PayFac

How to become a PayFac?

Becoming a PayFac, particularly in Europe, is a major undertaking that transforms your software company into a regulated financial institution. The process generally involves:

  1. Securing a sponsor bank: Finding an acquiring bank that will sponsor your registration with card networks.

  2. Obtaining a regulatory license: Applying for a Payment Institution (PI) or Electronic Money Institution (EMI) licence from national regulators (like the DNB ).

  3. Meeting capital requirements: Proving you have the minimum required initial capital (often €125,000 to €350,000) and maintaining ongoing reserves.

  4. Building the infrastructure: Developing or integrating systems for sub-merchant onboarding, risk scoring, and settlement.

  5. Establishing a compliance programme: Hiring a specialised team to manage AML, KYC, and regulatory reporting.

Does a PayFac need a license in Europe?

Yes. To act as a PayFac in the EU or UK, you generally need to be authorised as a Payment Institution (PI) or an Electronic Money Institution (EMI). Handling third-party funds is a regulated activity.

What is the difference between a PayFac and an ISO?

An Independent Sales Organisation (ISO) typically acts as a sales agent for an acquirer. They might help with onboarding, but the business still has a direct agreement with the bank. A PayFac aggregates those merchants under its own account and takes on much more of the operational and financial risk.

Is Mollie a PayFac?

Mollie provides payment facilitation capabilities for many users and platforms, combining its licensed electronic money institution infrastructure with acquiring and banking partners to enable embedded payment experiences across Europe.

How does a PayFac make money?

PayFacs earn money through the spread – the difference between what they charge the sub-merchant and what the underlying processor charges them. They can also charge fees for faster payouts, specialised reporting, or additional embedded financial services.

Stay up to date

Never miss an update. Receive product updates, news and customer stories right into your inbox.

Form fields

Table of contents

Table of contents

MollieGrowthWhat is a PayFac? Payment facilitators explained for platforms
MollieGrowthWhat is a PayFac? Payment facilitators explained for platforms
MollieGrowthWhat is a PayFac? Payment facilitators explained for platforms
MollieGrowthWhat is a PayFac? Payment facilitators explained for platforms