Payment Facilitators (PayFacs): How the Model Works for Merchants and Platforms

Quick answer: what is a Payment Facilitator?

A Payment Facilitator, usually shortened to PayFac, is a payments business that operates within an acquiring relationship and facilitates card payments for merchants that participate in its programme.

Mastercard defines a Payment Facilitator as a service provider registered by an acquirer to facilitate transactions on behalf of sub-merchants.

This is different from a traditional arrangement where every merchant establishes the same type of direct acquiring relationship independently.

Depending on the PayFac model, the Payment Facilitator can take responsibility for significant parts of the merchant lifecycle, including:

• merchant onboarding
• Know Your Customer (KYC) and Know Your Business (KYB) checks
• risk assessment
• sub-merchant management
• transaction monitoring
• payment technology
• payouts or settlement processes
• chargeback management
• ongoing merchant compliance.

However, the PayFac does not operate independently of the wider acquiring and card-network ecosystem.

An acquiring partner remains an important part of a traditional Payment Facilitator structure, and card-network rules govern how PayFacs and their sub-merchants operate.

Find Your New Processor

How does a PayFac work?

A simplified Payment Facilitator structure might look like this:

Merchant / Sub-Merchant → Payment Facilitator → Acquirer → Card Network → Card Issuer

The merchant interacts primarily with the Payment Facilitator.

The PayFac operates within a wider acquiring programme that connects those merchants into the card-payment ecosystem.

Depending on the model, the PayFac may provide much of the merchant-facing experience, including:

• online registration
• identity verification
• business verification
• payment acceptance
• dashboard and reporting
• pricing
• refunds
• payout information
• customer support.

The merchant may therefore experience the PayFac as its payment provider even though an underlying acquirer and other payment organisations also sit within the transaction chain.

What is a sub-merchant?

A sub-merchant is a merchant operating within a Payment Facilitator programme.

Rather than every business establishing an identical standalone acquiring structure directly with the sponsoring acquirer, the PayFac manages participating merchants within its programme.

The exact terminology can vary between card networks and payment structures, and merchants may also encounter descriptions such as:

• sponsored merchant
• sub-merchant
• connected account
• seller
• platform merchant.

These terms should not automatically be assumed to mean exactly the same legal or card-scheme structure.

Does a PayFac mean the merchant does not have a merchant account?

It is more accurate to say that the merchant participates within a different acquiring structure.

Older explanations of Payment Facilitators often say that merchants “do not need merchant accounts”.

That can be misleading.

The business still needs an acquiring arrangement that enables it to accept card payments.

What changes is how that merchant sits within the acquiring programme.

In a PayFac structure, the merchant is commonly onboarded and identified as a sub-merchant or sponsored merchant within the Payment Facilitator's programme rather than establishing the same type of direct acquiring arrangement independently.

This distinction matters when considering:

• Merchant IDs
• underwriting
• settlement
• risk ownership
• contract structure
• provider switching.

Who is the acquirer in a PayFac model?

A traditional Payment Facilitator works with an acquiring partner.

The acquirer connects the PayFac programme into the card-payment system and carries important acquiring and card-network responsibilities.

Mastercard states that an acquirer must register a service provider as a Payment Facilitator before it operates as one within the Mastercard ecosystem.

View Mastercard's Payment Facilitator information.

A platform evaluating a PayFac arrangement should therefore understand:

• who the underlying acquiring partner is
• which countries the acquiring relationship covers
• which Merchant Category Codes are supported
• what risk appetite applies
• which currencies are supported
• who controls material underwriting decisions
• what happens if the acquiring relationship changes.

Is a PayFac regulated in the UK?

The regulatory position depends on the services and structure involved rather than simply whether a company calls itself a PayFac.

The Financial Conduct Authority's guidance on the Payment Services Regulations explains that acquiring payment transactions is a regulated payment service.

The FCA specifically states that the definition of acquiring is likely to capture “master merchant” or Payment Facilitator models where the business contracts with payees to provide acquiring services.

View the FCA's guidance on acquiring payment transactions.

This should not be interpreted as meaning every company providing technology to a PayFac needs the same regulatory permissions.

The FCA also distinguishes acquiring from purely technical services such as:

• payment processing
• data storage
• payment terminals
• online payment gateways.

The regulatory position therefore depends on what the business actually does.

Is a PayFac the same as a PSP?

No. The terms overlap, but they are not interchangeable.

Payment Service Provider, or PSP, is a broader term.

In UK regulation, Payment Service Provider has a formal meaning under the Payment Services Regulations.

Within the payments industry, PSP is also commonly used more broadly to describe companies providing combinations of:

• payment gateways
• processing
• acquiring
• payment methods
• fraud tools
• reporting
• other payment services.

A Payment Facilitator can therefore be a type of PSP depending on the structure and services being provided.

But not every PSP is a Payment Facilitator.

For a broader explanation, read our Payment Service Providers (PSPs) guide.

PayFac vs ISO: what is the difference?

A Payment Facilitator and an Independent Sales Organisation perform different functions within the payments ecosystem.

A simple way to think about the distinction is:

An ISO primarily helps distribute acquiring services.

A PayFac operates much more deeply within the merchant-payment programme.

Read our ISO vs PayFac vs PSP vs Acquirer guide for a full comparison.

PayFac vs traditional merchant account

A traditional merchant-account relationship and a PayFac model can both enable a business to accept card payments.

The difference is primarily in the structure.

Neither model is automatically better.

The appropriate structure depends on the merchant and the payment use case.

Does a PayFac provide instant approval?

Not necessarily.

PayFac technology can make onboarding considerably more automated than traditional manual merchant-account processes.

However, that should not be confused with guaranteed or unconditional approval.

The PayFac still needs to manage areas such as:

• identity verification
• business verification
• sanctions screening
• merchant-category controls
• fraud risk
• chargeback risk
• prohibited activities
• ongoing monitoring.

Some merchants can therefore be activated very quickly.

Others may require further information, manual review or may fall outside the PayFac's permitted risk appetite.

For more information about onboarding, read our Fast Merchant Account Approval guide.

Why can PayFac onboarding be faster?

The PayFac model can allow onboarding and payment activation to be built directly into a software or platform experience.

Instead of:

Merchant → separate paper or online acquiring application → manual setup → separate integration

the journey can be closer to:

Merchant → platform registration → embedded KYC/KYB → eligibility decision → payment activation

This can remove friction for businesses that fit the programme's criteria.

The important qualification is:

faster onboarding does not mean no underwriting or no ongoing risk controls.

What happens after a PayFac merchant goes live?

Risk assessment does not necessarily stop at account activation.

A Payment Facilitator may continue monitoring areas including:

• transaction volumes
• average transaction values
• chargebacks
• refunds
• fraud
• changes to the business model
• products being sold
• customer geography
• website activity
• other merchant-risk indicators.

If activity moves outside the expected profile, the PayFac may request additional information or take action under its risk procedures.

This is one reason merchants should provide accurate information during onboarding rather than treating a quick signup process as a substitute for explaining the business properly.

Find Your New Processor

Who settles funds in a PayFac model?

The funds flow depends on the structure.

The merchant should therefore establish:

• which legal entity is responsible for settlement
• who appears on the merchant's bank statement
• how frequently payouts are made
• whether the PayFac controls payout scheduling
• who can delay or hold settlement
• how refunds and chargebacks are funded
• what happens to merchant balances if the payment relationship ends.

This is particularly important for platforms handling payments on behalf of large numbers of merchants or sellers.

Can a PayFac hold or delay merchant funds?

Payment Facilitator arrangements can include controls over merchant payouts, reserves and risk management, subject to the relevant commercial, acquiring and regulatory structure.

A merchant should understand the circumstances in which:

• payouts can be delayed
• a rolling reserve may be introduced
• funds may be retained against refunds or chargebacks
• additional verification may be required.

The exact rights and responsibilities should be set out in the provider's agreement.

Merchants should not assume that rapid initial onboarding means funds will always be settled without further review.

How are chargebacks handled by a PayFac?

The PayFac commonly forms an important part of the chargeback-management process for its sub-merchants.

Depending on the model, this can include:

• receiving dispute information
• notifying the sub-merchant
• collecting evidence
• debiting disputed funds
• monitoring chargeback levels
• taking action against merchants with excessive dispute activity.

The underlying acquirer and card networks also remain relevant to the wider dispute process.

Who sets the PayFac's risk appetite?

Risk appetite is rarely controlled by one factor.

The merchant categories a PayFac can support may be influenced by:

• the PayFac's own risk policy
• the sponsoring acquirer
• card-network rules
• regulation
• geography
• transaction values
• chargeback exposure
• financial exposure.

This is why a platform cannot assume that becoming or using a PayFac automatically allows it to accept every merchant its software serves.

Are PayFacs suitable for high-risk businesses?

Sometimes, but not automatically.

A Payment Facilitator programme is built around a defined merchant and risk profile.

Some PayFac programmes focus on relatively straightforward small-business or platform merchants.

Others may support more specialised sectors.

The relevant question is not:

“Does this PayFac accept high risk?”

It is:

“Does this particular programme and its acquiring partner have appetite for our exact business model and MCC?”

Businesses with complex requirements may need a specialist acquiring route rather than a mainstream embedded PayFac model.

Why are PayFacs important for software platforms?

The growth of embedded payments has made the PayFac model particularly important to software companies.

Consider a booking platform serving 5,000 independent businesses.

Without embedded payments, every customer may need to:

• find its own merchant account
• choose a gateway
• complete a separate integration
• enter payment credentials into the platform.

With an embedded payment model, the platform can potentially incorporate payment onboarding directly into its software.

This can create a user journey such as:

Create account → verify business → activate payments → start taking bookings.

The software platform can also potentially generate revenue from the payment service rather than simply referring customers elsewhere.

What types of software businesses use PayFac models?

PayFac and embedded-payment models are particularly relevant to vertical software businesses including:

• booking platforms
• EPOS systems
• property-management software
• practice-management systems
• marketplaces
• ticketing platforms
• field-service software
• hospitality software
• education platforms
• business-management systems.

The common feature is that payments become part of the software product rather than an external service the customer must arrange independently.

What is embedded payments?

Embedded payments refers to integrating payment functionality directly into another product or platform.

The customer can then access payments as part of the wider software experience.

Embedded payments does not automatically mean that the software company itself has become a traditional full Payment Facilitator.

The underlying infrastructure could instead be provided through:

• a PayFac
• PayFac-as-a-Service
• a PSP
• an acquiring platform
• another embedded-payments provider.

This distinction matters when understanding who controls merchant onboarding, risk, settlement and compliance.

What is PayFac-as-a-Service?

Becoming a traditional Payment Facilitator can require significant payments expertise, acquiring relationships, card-network registration, risk operations, compliance capability and technical infrastructure.

As a result, technology providers now offer models commonly described as:

• PayFac-as-a-Service
• managed PayFac
• embedded-payments infrastructure
• white-label payments.

These can allow a software platform to control more of the merchant experience without independently building every part of a traditional PayFac programme.

Responsibilities may be divided between:

• the software platform
• the payments infrastructure provider
• the acquirer
• other regulated or technical organisations.

The term “PayFac-as-a-Service” is itself used differently across the market, so platforms should ask exactly which responsibilities they are assuming.

PayFac vs PayFac-as-a-Service

Is Stripe a PayFac?

Large modern payment businesses can perform several payments roles and should not always be reduced to one label.

Stripe provides payment infrastructure that can support businesses directly as well as platforms building embedded payment experiences.

Its public information describes traditional Payment Facilitator models alongside technology-led payment facilitation and embedded-payment infrastructure.

View Stripe's explanation of payment facilitation.

The more useful question for a merchant or platform is therefore:

“Which Stripe product and payment structure are we actually using?”

rather than simply:

“Is Stripe a PayFac?”

Is Square a PayFac?

Payment companies can operate PayFac-style or sponsored-merchant structures while also providing a much broader range of payment and software services.

Again, merchants should focus on the exact contractual and acquiring arrangement rather than trying to place a large payments business into a single category.

Is a marketplace automatically a PayFac?

No.

A marketplace is a commercial business model connecting buyers and sellers.

A PayFac is a particular payments model.

A marketplace might use PayFac infrastructure to:

• onboard sellers
• accept payments
• manage seller payment accounts
• facilitate payouts.

But operating a marketplace does not automatically make the marketplace itself a Payment Facilitator.

For platforms that also need to divide transactions between multiple parties, see our Split Payment Gateways guide.

Is a PayFac the same as Merchant of Record?

No.

A PayFac facilitates payment acceptance for participating merchants.

A Merchant of Record model generally involves a wider commercial relationship where the Merchant of Record becomes the entity responsible for the transaction presented to the customer and can assume broader responsibilities around the sale.

Depending on the model, those responsibilities can include:

• customer billing
• tax
• refunds
• chargebacks
• consumer-facing transaction obligations.

The two models should not be treated as interchangeable.

What are the advantages of using a PayFac?

Depending on the merchant and platform, potential benefits can include:

• streamlined onboarding
• integrated KYC and KYB
• embedded payments
• simplified technical integration
• centralised reporting
• integrated payouts
• one platform for software and payments
• potentially faster activation for eligible merchants.

For software businesses, another major benefit is commercial.

Payments can become part of the platform's own product and revenue model.

What are the disadvantages of using a PayFac?

The model can also create limitations.

These may include:

• merchant acceptance limited by the PayFac's programme rules
• less control over the underlying acquiring relationship
• provider-specific settlement arrangements
• less flexibility for unusual merchant categories
• dependency on the platform's payment infrastructure
• potential complexity when moving merchants elsewhere
• payout or reserve controls imposed under the programme.

For larger merchants, the commercial pricing available through a PayFac should also be compared with direct or specialist acquiring alternatives.

Can a business outgrow a PayFac?

Potentially.

A PayFac arrangement that works extremely well for a small or growing business may become less appropriate if the merchant later requires:

• very high transaction volumes
• negotiated acquiring economics
• multiple acquirers
• international acquiring
• multiple Merchant IDs
• specialist risk appetite
• greater control over payment credentials
• payment orchestration
• complex settlement arrangements.

That does not mean every growing merchant needs to leave a PayFac.

It means the payment architecture should be reviewed as the business changes.

What happens if you want to leave a PayFac?

The answer depends on the provider and payment architecture.

Businesses should establish:

• what happens to stored customer payment credentials
• whether tokens can be migrated
• how recurring payments move
• whether the existing payment integration can remain
• what happens to historic transaction data
• how outstanding refunds and chargebacks are handled
• when final payouts are made.

For businesses with stored cards or subscriptions, leaving a PayFac can therefore involve more than simply opening another payment account.

Read our Changing Payment Gateway: Moving Stored Cards, Tokens and Recurring Payments guide.

Find Your New Processor

What should merchants ask before choosing a PayFac?

• Who is the underlying acquiring partner?
• Will we operate as a sub-merchant or sponsored merchant?
• Who carries out our underwriting?
• Which Merchant Category Codes do you support?
• Who settles our funds?
• What is the normal payout period?
• When can payouts be delayed?
• Can a reserve be introduced?
• Who manages chargebacks?
• Who provides the gateway?
• Who stores customer payment credentials?
• What happens to those credentials if we leave?
• Can the platform support our expected transaction volume?
• Can it support our countries and currencies?
• What happens if our business model changes?

What should a software platform ask before becoming or using a PayFac?

Platforms need to ask an additional set of questions.

• Do we really need to become a traditional PayFac?
• Could PayFac-as-a-Service meet the requirement instead?
• Who will perform KYC and KYB?
• Who will own merchant underwriting?
• Who will monitor transaction risk?
• Who manages chargebacks and reserves?
• Who holds the acquiring relationship?
• Which merchant sectors can the programme support?
• How will merchant pricing work?
• How will the platform earn revenue from payments?
• Who handles merchant customer support?
• What happens if the platform changes payment infrastructure later?

For many platforms, the decision is no longer simply:

“Should we become a PayFac?”

It is:

“How much of the payment stack do we actually want to own?”

Our view: PayFac is a payments operating model, not simply a faster merchant account

Payment Facilitators are sometimes described simply as a way to open merchant accounts faster.

That understates what the model actually represents.

A PayFac is fundamentally about how merchants are onboarded, managed and connected to acquiring infrastructure.

For an individual merchant, that can create a simple and highly integrated experience.

For a software company, it can provide the foundation for embedded payments across thousands of customers.

But the simplicity visible to the merchant is supported by a much more complicated structure underneath involving:

• acquiring
• card-network rules
• merchant identification
• KYC and KYB
• underwriting
• transaction monitoring
• settlement
• risk management.

Understanding that underlying structure is much more useful than treating every PayFac as simply another PSP or payment gateway.

How Merchant Advice Service helps businesses understand PayFac and embedded-payment models

Merchant Advice Service helps businesses and platforms understand the payment structure required for their particular model.

This can include:

• Payment Facilitators
• PSPs
• ISOs
• acquirers
• payment gateways
• embedded payments
• marketplaces
• split payments
• multiple Merchant IDs
• multiple acquirers
• payment orchestration
• complex payment integrations.

The objective is to understand who needs to do what within the payment chain before choosing the provider or architecture.

For the wider industry structure, read our ISO vs PayFac vs PSP vs Acquirer guide.

About Merchant Advice Service

Merchant Advice Service is a UK business-to-business payments information, comparison and provider-matching service.

Founded in 2016, MAS helps businesses understand their payment requirements and identify payment providers or specialist partners that may be relevant to the way they operate.

We provide information and support across areas including:

• merchant accounts
• payment gateways
• integrated and embedded payments
• higher-risk merchant accounts
• international acquiring
• multiple currencies
• specialist payment integrations
• more complex provider requirements.

Merchant Advice Service is not an acquiring bank or payment processor and does not make final underwriting decisions.

The MAS information, matching and introduction service is free to businesses. MAS may receive commission or a referral fee from some commercial partners where an introduction results in a completed product or account.

For full information about how our service operates, provider matching, independence and commercial relationships, read How Merchant Advice Service Works.

Find Your New Processor

Sources and industry references

This guide was reviewed and updated in August 2026 using UK regulatory guidance and primary card-network and payments-industry sources.

Financial Conduct Authority — Acquiring Payment Transactions

FCA perimeter guidance explains the definition of acquiring under the Payment Services Regulations and specifically discusses master-merchant and Payment Facilitator models.

FCA Handbook: Payment Services and Acquiring

Financial Conduct Authority — Payment Services Regulations

The FCA's payment-services guidance explains the UK Payment Services Regulations 2017 and the types of regulated payment services they cover.

FCA: Payment Services Regulations and Electronic Money Regulations

Mastercard — Payment Facilitators

Mastercard defines a Payment Facilitator as a service provider registered by an acquirer to facilitate transactions on behalf of sub-merchants and publishes information about registered Payment Facilitators.

Mastercard: Payment Facilitators

Visa — Third Party Agent Registration

Visa publishes information about the registration of third-party agents operating within its payments ecosystem.

Visa: Third Party Agent Registration

Stripe — Payment Facilitation

Stripe's payment-facilitation information provides a current industry example of traditional PayFac and technology-led embedded-payment models.

Stripe: Payment Facilitation

Editorial and commercial disclosure

Merchant Advice Service is an independent payments information, comparison and provider-matching service.

The term Payment Facilitator can be used within card-network, regulatory and commercial contexts. The exact responsibilities of an individual PayFac depend on its acquiring relationships, regulatory status, card-network arrangements, technology and contracts.

This article provides general information about commonly encountered Payment Facilitator structures and should not be interpreted as legal or regulatory advice about the status of an individual company.

Our editorial content may reference payment providers, card networks, regulators and technology businesses regardless of whether Merchant Advice Service has a commercial relationship with them.

Where organisations are named for technical, regulatory or market examples, inclusion does not constitute a recommendation and should not be taken to mean that Merchant Advice Service can introduce businesses to that organisation.

MAS may receive commission or a referral fee from some commercial partners where a business chooses to proceed following an introduction. Commercial relationships do not determine which organisations may be referenced within our independent educational content.

Organisations have not paid for inclusion in this article unless explicitly stated.

Payment Facilitator programmes, acquiring arrangements, merchant acceptance, settlement, pricing, regulatory status and card-network requirements can change. Businesses and platforms should confirm the current position with the relevant providers before entering into an arrangement.