What Is a Payment Facilitator (PayFac)? A Complete Guide

A payment facilitator, often shortened to PayFac, is a payment model that lets a platform onboard businesses as sub-merchants under one master merchant account.

Instead of every seller, creator, merchant, or service provider applying for its own direct merchant account, the PayFac handles onboarding and payment operations on their behalf. This is why the model is common in SaaS platforms, marketplaces, creator platforms, booking platforms, and vertical software products that want to embed payments into the user experience.

The trade-off is simple: a PayFac gets more control over the merchant experience, but also takes on more responsibility for underwriting, risk, compliance, disputes, and funds movement.

How the PayFac model works

A registered PayFac operates with a sponsoring merchant acquirer, also called an acquiring bank. The acquirer provides the underlying master merchant account and connects the PayFac into the card networks.

The PayFac then signs up businesses underneath that structure as sub-merchants.

A simplified stack looks like this:

1. Card networks set the rules and route card transactions.
2. Merchant acquirer holds the banking relationship and ultimate network responsibility.
3. Payment facilitator operates under the acquirer and manages sub-merchants.
4. Sub-merchants accept payments through the PayFac’s master account.

This structure lets the PayFac offer faster onboarding and a more integrated payment experience. It also means the PayFac becomes the front line for risk, compliance, and merchant behavior.

What a PayFac actually owns

A PayFac is not just a payment interface. It usually owns several operational responsibilities that would otherwise sit with a bank, processor, or merchant account provider.

These responsibilities can include:

• Sub-merchant onboarding — collecting business, ownership, and identity information.
• Underwriting — deciding which businesses can be accepted.
• KYC, KYB, AML, and sanctions screening — checking whether merchants and beneficial owners meet compliance requirements.
• Risk monitoring — watching for fraud, suspicious behavior, excessive disputes, and prohibited activity.
• Funds flow and settlement — receiving settlement into the master account and distributing funds to sub-merchants.
• Chargeback and dispute handling — managing reversals, documentation, and merchant risk exposure.
• Ongoing reporting — providing required reports to the acquirer and card networks.
• PCI DSS obligations — maintaining the appropriate security posture for handling payment data.

This is why the PayFac model is operationally powerful but also compliance-heavy.

PayFac vs merchant acquirer

A PayFac and a merchant acquirer are not the same thing.

A merchant acquirer is the financial institution or acquiring bank registered with the card networks. It provides the banking relationship, supports merchant accounts, and ultimately carries responsibility for funds movement and network-level risk.

A payment facilitator sits underneath the acquirer. It does not replace the acquirer. It uses the acquirer’s sponsorship and master merchant account to onboard and manage sub-merchants.

In practical terms:

A PayFac cannot operate without an acquiring partner behind it.

PayFac vs ISO / MSP

PayFac and ISO are often confused because both sit between merchants and the payment system. The difference is how much responsibility each one takes on.

An ISO, or Independent Sales Organization, is mainly a sales and referral channel. Mastercard uses the related term MSP, or Member Service Provider. An ISO/MSP refers merchants to an acquirer or processor, but it typically does not touch funds, own underwriting, or carry chargeback liability.

A PayFac goes deeper into the payment flow. It onboards sub-merchants, touches settlement funds, owns underwriting, and carries more risk.

If a business wants to monetize payment processing without operating the risk stack, ISO/MSP may be enough. If a platform wants to embed payments deeply and own more of the merchant experience, PayFac may be the better direction.

Registered PayFac vs PayFac-as-a-Service

Becoming a fully registered PayFac is a major undertaking. It requires a sponsor bank, card-network registration, security validation, operating policies, compliance processes, sub-merchant monitoring, dispute workflows, reporting, and ongoing audits.

For many platforms, this is too expensive and too slow to build from scratch.

That is why some businesses use PayFac-as-a-Service or a managed PayFac model. In this setup, a provider already has much of the registration, risk, compliance, and infrastructure in place. The platform can embed payments faster without taking on the full burden of becoming a registered PayFac.

This route can make sense when a company wants the PayFac-like merchant experience but is not ready to own the full compliance and operational program.

What is a sub-merchant?

A sub-merchant is a business that accepts payments under a PayFac’s master merchant account instead of holding its own merchant account.

For example, a marketplace seller, SaaS customer, creator, tutor, service provider, or small merchant may be onboarded as a sub-merchant.

The sub-merchant usually contracts with the PayFac, not directly with the card networks or acquiring bank. It uses the PayFac’s payment infrastructure, onboarding process, and settlement flow.

That is why onboarding can be fast. The PayFac has already completed the heavy work with the acquirer and networks.

But sub-merchants are not free from responsibility. They still need to provide accurate business information, follow platform policies, respond to disputes, and meet applicable payment and compliance obligations.

When the PayFac model makes sense

The PayFac model usually makes sense when payment acceptance is part of the product experience.

It may be a fit for:

• SaaS platforms that serve many smaller merchants.
• Marketplaces that need to onboard sellers or service providers.
• Vertical software platforms that want to offer payments inside their workflow.
• Creator, booking, education, or service platforms that need fast merchant onboarding.
• Platforms that want more control over merchant experience, pricing, settlement, and payment data.

A PayFac model can support faster onboarding, a more unified payment experience, and stronger control over the merchant relationship.

But the business has to be ready for the compliance and risk responsibilities that come with that control.

When PayFac may not be the right answer

Not every business that wants to accept payments needs to become a PayFac.

If you are a single merchant, a direct merchant account or payment service provider may be enough.

If your goal is mainly to resell payment processing, ISO/MSP may be more suitable.

If your main challenge is selling across multiple countries, the PayFac model may not solve the real problem. Card-network PayFac models are built largely around card acceptance, while many markets rely heavily on local wallets, bank transfers, QR payments, real-time payment networks, and other local payment methods.

In that case, the question is not only “Should we become a PayFac?”

The better question may be: “How do we accept the payment methods local customers actually use?”

The cross-border angle

Cross-border merchants often face a different problem from domestic platforms.

They may need to accept Pix in Brazil, GCash or GoPay in Southeast Asia, UPI in India, Mada or STC Pay in the Middle East, international cards, and local payout methods across multiple markets.

A single acquirer usually cannot cover every local method in every region. A registered PayFac model also does not automatically provide local acquiring, local clearing, payout support, or market-specific payment methods.

That is where cross-border local acquiring becomes important.

Cross-border local acquiring focuses on helping businesses accept local payment methods, manage multiple markets, and simplify payment operations without registering as a card-network PayFac.

Where HaiPay fits

HaiPay is a licensed payment provider that facilitates cross-border local acquiring. It helps businesses accept local payment methods across many markets without registering with the card networks themselves.

HaiPay can support:

• Local payment methods.
• Local acquiring.
• Global acquiring.
• Multi-currency settlement.
• Standardized API access.
• Payment Link and hosted checkout.
• Order status sync.
• Automated reconciliation.
• Localized risk control.
• Refund, chargeback, and dispute handling support.
• Local payout in supported markets.

For businesses expanding internationally, the practical goal is often not to become a PayFac. It is to build a payment stack that supports local customer behavior, market expansion, settlement visibility, and operational control.

That is the role HaiPay is designed to support.

Key takeaway

A payment facilitator gives platforms more control over merchant onboarding and payment experience, but it also brings higher responsibility for risk, compliance, settlement, and monitoring.

Before choosing the PayFac path, businesses should decide what they actually need:

• Do they need to onboard many sub-merchants?
• Do they want to own the payment experience?
• Are they ready to carry underwriting and compliance responsibility?
• Do they need a full registered PayFac model, or is PayFac-as-a-Service enough?
• Is the real challenge card acceptance, or cross-border local payment coverage?

For many platforms, PayFac is a powerful model. For many cross-border merchants, local acquiring may solve the more urgent problem.

Sources

• Visa — Merchant Payment Providers: https://usa.visa.com/supporting-info/merchant-payment-providers.html
• Mastercard — Payment Facilitators: https://www.mastercard.com/us/en/business/support/payment-facilitators.html
• PCI Security Standards Council: https://www.pcisecuritystandards.org/