What is a payment facilitator (PayFac)? 2026 complete guide

Key Takeaways:

• A payment facilitator (payfac) is a third-party service that lets businesses accept and manage payments without setting up individual merchant accounts with a bank.

• Payfacs sit between acquiring banks and businesses, handling onboarding, compliance, fraud monitoring, and fund settlement under a master merchant account.

• Airwallex operates as a global payfac, giving platforms and marketplaces the infrastructure to accept payments, onboard sub-merchants, and offer embedded financial services, all in one place.

A payment facilitator, often called a payfac, is a third-party service that lets businesses accept electronic payments without needing to establish a direct relationship with an acquiring bank.

Instead of going through a lengthy application process for their own merchant account, businesses can operate as sub-merchants under the payfac's master account and start accepting payments quickly.

In this guide, you'll learn how payment facilitators work, who the key parties are, how the model compares to payment processors, acquirers, and independent sales organisations (ISOs), and how to decide whether a payfac is right for your business.

What is a payment facilitator?

A payment facilitator, or payfac, is a company that helps other businesses accept payments without each business having to set up its own merchant account with an acquiring bank.

The payfac holds a master merchant account with an acquirer and lets other businesses, known as sub-merchants, process payments through it. This means businesses can get set up to accept payments without going through the full merchant account application process themselves.

What does a payment facilitator do?

A payfac typically handles much of the work involved in getting businesses set up and keeping their payments running, including:

• Onboarding sub-merchants: Reviewing businesses and approving them to accept payments.

• Providing payment infrastructure: Giving businesses the technology they need to accept and process payments.

• Managing risk: Monitoring transactions for fraud and other unusual activity.

• Handling compliance: Making sure sub-merchants meet relevant payment industry and regulatory requirements.

• Managing disputes: Helping handle chargebacks and other payment disputes.

• Settling funds: Moving processed payments to the businesses that received them.

By handling these responsibilities centrally, a payfac can make it faster and simpler for businesses to start accepting payments.

Some examples of payment facilitators include Airwallex, Stripe, Square, and PayPal. Businesses can use these platforms to start accepting card payments without setting up a traditional merchant account directly with an acquiring bank.

3 parties in the payfac model

The payfac model involves three main parties:

The acquiring bank

The acquiring bank, or acquirer, is the financial institution that holds the payfac's master merchant account.

It is connected to card networks such as Visa and Mastercard, allowing transactions to be processed on behalf of merchants.

The acquirer also takes on financial risk associated with those transactions, including chargebacks and certain fraud losses. As a result, it sets requirements that the payfac must meet when onboarding and monitoring its sub-merchants.

The payment facilitator

The payment facilitator sits between the acquirer and its sub-merchants.

It provides the technology and processes that businesses need to accept payments, while taking responsibility for onboarding, transaction monitoring and other operational and compliance requirements.

The payfac also acts as the main point of contact for many payment-related issues, such as disputes and account management.

The sub-merchant

The sub-merchant is the business that uses the payfac's infrastructure to accept payments.

Instead of setting up its own merchant account with an acquirer, it processes payments under the payfac's master merchant account.

This can make onboarding much faster. Depending on the payfac and the business, a sub-merchant may be able to start processing payments within hours rather than waiting days or weeks for a traditional merchant account setup.

How does a payment facilitator work?

When a customer pays a sub-merchant, the payment goes through the payfac's payment infrastructure rather than directly from the customer's bank to the business.

The payfac sends the transaction through the relevant card network, such as Visa or Mastercard, to the customer's issuing bank for authorisation. If the payment is approved, the transaction moves to settlement, and the payfac pays the funds to the sub-merchant, usually after deducting its fees.

The payfac's master merchant account sits at the centre of this process.

Transactions from its sub-merchants are processed under this account, while the payfac manages the relationship with each sub-merchant. The acquiring bank therefore works directly with the payfac rather than onboarding each sub-merchant individually.

The transaction flow, step by step

Here's what happens when a customer makes a card payment through a payfac:

• The customer makes a payment. For example, they pay for an order from a business selling through an online marketplace.

• The payment details go to the payfac. The sub-merchant's checkout sends the transaction data to the payfac's payment gateway or processing platform.

• The payfac sends the transaction for authorisation. The transaction is routed through the relevant card network to the customer's issuing bank.

• The issuing bank approves or declines the payment. Its response travels back through the card network to the payfac.

• The payfac confirms the result. The payfac sends the approval or decline back to the sub-merchant's checkout.

• The transaction is settled. Once the funds are received through the payment system, the payfac pays the sub-merchant, typically after deducting its applicable fees.

How do payfacs make money?

Payfacs generally generate revenue from transaction fees and additional payment services. Here’s a quick breakdown:

• Transaction fees: A payfac typically charges sub-merchants a fee for each transaction. It then pays the relevant processing and acquiring costs, with the difference contributing to its revenue.

• Value-added services: Payfacs may also charge for additional features such as fraud monitoring, faster payouts, reporting and dispute management. Depending on the provider, there may also be platform, subscription or onboarding fees.

For platforms that embed payment functionality into their own product, payments can also become a revenue stream in their own right.

Instead of simply paying a third party to process payments, the platform can earn revenue from the payment services it provides to its users.

Payfac vs payment processor vs acquirer vs ISO

The payments industry uses a lot of overlapping terms, so it can be difficult to see how a payment facilitator fits into the wider payments ecosystem. Here's how the main roles differ:

Payfac vs payment processor

A payment processor provides the infrastructure that moves transaction data between merchants, card networks and banks. A payfac uses payment processing infrastructure but also onboards and manages sub-merchants, including their risk and compliance requirements.

In short: A processor handles the transaction; a payfac also manages the businesses processing those transactions.

Payfac vs acquirer

An acquirer is the financial institution that provides acquiring services and, in the payfac model, holds the payfac's master merchant account. The payfac sits between the acquirer and its sub-merchants, managing their onboarding, payments and ongoing risk.

In short: The acquirer provides the acquiring relationship; the payfac manages the sub-merchants.

Payfac vs ISO

An independent sales organisation (ISO) helps sell or support payment services on behalf of an acquirer, processor or other payment provider. Unlike a payfac, an ISO typically does not hold a master merchant account or manage payment processing for the businesses it refers.

In short: An ISO helps businesses access payment services; a payfac provides the infrastructure and manages them as sub-merchants.

What does a payfac do?

A payment facilitator does more than process payments. It also takes on much of the work involved in onboarding, monitoring and supporting the businesses that use its payment infrastructure.

Here's what that typically involves:

Merchant onboarding

Before a business can start accepting payments through a payfac, it needs to be onboarded.

The payfac verifies the business and its owners, checks for sanctions and other risk factors, and assesses whether the business meets its requirements for accepting payments.

With digital onboarding, much of this process can happen in minutes. This can be considerably faster than a business applying for its own merchant account and going through the underwriting process independently.

The payfac is also responsible for making sure the sub-merchants it accepts meet the requirements set by its acquiring partner and the relevant card networks.

KYC and AML compliance

Payfacs typically carry out Know Your Customer (KYC) and Anti-Money Laundering (AML) checks as part of merchant onboarding and ongoing monitoring.

This can include:

• Verifying the identity of the business and its beneficial owners

• Screening businesses and individuals against sanctions and other watchlists

• Assessing the merchant's risk profile

• Monitoring transactions for suspicious activity

The exact requirements vary by market and the payfac's regulatory and acquiring arrangements, but these controls are an important part of managing payment risk and meeting applicable legal and regulatory obligations.

Risk and fraud monitoring

The payfac continues to monitor a sub-merchant after it has been approved. It may look for unusual transaction patterns, signs of fraud, sudden changes in payment volume or unusually high chargeback rates.

If a business's risk profile changes, the payfac may take action such as requesting more information, placing restrictions on the account, delaying payouts or, where appropriate, suspending or terminating payment services.

Because the payfac sits between the acquirer and its sub-merchants, it also takes on financial exposure when something goes wrong. The exact allocation of liability varies by arrangement, but the payfac generally has a strong incentive to identify and manage risky merchants.

PCI DSS compliance

Payfacs must meet the requirements of PCI DSS (Payment Card Industry Data Security Standard) when their services involve the storage, processing or transmission of cardholder data.

By handling much of the payment infrastructure themselves, payfacs can reduce the PCI DSS burden for their sub-merchants. For example, using hosted payment pages or tokenisation can limit the amount of sensitive card data that a business's own systems handle.

This doesn't necessarily mean the sub-merchant has no PCI DSS responsibilities. What the merchant needs to do depends on how its payment setup works and which parts of the payment process it handles itself.

Fund settlement

Once payments have been processed, the funds need to reach the sub-merchant. The payfac manages this settlement process, typically deducting its fees before paying out the remaining amount to the sub-merchant.

Payout timing varies by provider and risk profile. Depending on the arrangement, businesses may receive funds on a same-day, next-day or rolling schedule.

Dispute and chargeback management

If a customer disputes a card transaction, the payfac helps manage the resulting chargeback process. This can involve notifying the sub-merchant, collecting supporting evidence and submitting a response through the relevant payment channels.

If the dispute is ultimately decided in the customer's favour, the transaction amount may be returned to the customer. The payfac may also be exposed to the associated costs, depending on its agreement with the sub-merchant and acquirer.

Payfacs therefore monitor chargeback rates across their sub-merchants and may take action when a business's dispute rate becomes unusually high. This helps protect both the payfac and its acquiring relationship.

Should you become a payfac?

Platforms and marketplaces that want to offer embedded payments generally have two options: become a registered payment facilitator or use a payfac-as-a-service provider.

Becoming a registered payfac gives a platform more control over its payments setup, but it also means taking on the associated compliance, risk management and operational responsibilities.

This typically requires a sponsoring acquirer, card-network registration and the infrastructure to onboard and monitor sub-merchants.

For many platforms, using a payfac-as-a-service provider is a simpler way to offer embedded payments.

The provider handles much of the underlying acquiring, compliance and risk infrastructure, while the platform can focus on its own product and customer experience.

The right approach depends on factors such as payment volume, resources, risk appetite and how much control the platform needs over its payments operation.

How Airwallex supports the payfac model

If you’re looking for a payments infrastructure provider for your platform, Airwallex is a good option.

Our Payments for Platforms solution gives platforms and marketplaces the infrastructure to onboard sellers, accept payments and manage fund flows without building your own payments infrastructure or registering as a PayFac. Here’s what you can do with Airwallex:

Onboard sub-merchants through Connected Accounts

You can create and manage connected accounts programmatically. Airwallex handles the required onboarding checks, including identity verification, AML and sanctions screening, while you manage the account experience through APIs or embedded components.

Accept payments and manage fund flows

Accept payments through 160+ local payment methods across 180+ countries, then split and route funds to connected accounts after deducting your platform fees.

Keep payments within your platform

Airwallex supports embedded and branded onboarding and payment experiences through pre-built components, hosted flows and APIs, enabling platforms to keep users within their own product experience. 

Frequently asked questions (FAQs)

What is a sub-merchant?

A sub-merchant is a business that processes payments under a payment facilitator's master merchant account rather than holding its own direct account with an acquiring bank. The payfac onboards the sub-merchant, runs compliance checks, and takes on financial responsibility for transactions processed on the sub-merchant's behalf. Sub-merchants operate under the payfac's terms and risk policies, and trade some independence for much faster setup and lower operational overhead.

What is the difference between a payfac and a payment processor?

A payment processor handles the technical routing of a transaction between the merchant, card network, and banks. It moves data. A payment facilitator does this and more: it holds a master merchant account, onboards sub-merchants, manages compliance and risk, and settles funds directly. Many payfacs use a payment processor as part of their infrastructure, but the two roles are distinct.

What is the difference between a payfac and an acquirer?

An acquiring bank holds the master merchant account and connects the payfac to card networks like Visa and Mastercard. It bears ultimate financial responsibility for all transactions. A payfac registers with the acquirer, operates under the acquirer's rules, and manages its own layer of sub-merchant risk and compliance. The acquirer's relationship is with the payfac, not with individual sub-merchants.

What is the difference between a payfac and an ISO?

An independent sales organisation (ISO) resells merchant services on behalf of an acquiring bank or payment processor. ISOs connect merchants to a processor, after which the merchant has a direct relationship with that processor. A payfac operates differently: sub-merchants never establish a direct relationship with the acquirer. They operate entirely under the payfac's account, with the payfac handling onboarding, compliance, and settlement on their behalf.

What is a payfac-as-a-service?

Payfac-as-a-service (PFaaS) is a model where a third-party provider gives a platform the benefits of payment facilitation (fast sub-merchant onboarding, branded payment flows, transaction revenue) without requiring that platform to register as a payfac itself. The provider holds the acquirer relationship and compliance infrastructure. The platform integrates via API. This is the model most platforms use in practice.

How do payment facilitators make money?

Payfacs typically earn revenue in two ways. First, through the margin between what they charge sub-merchants per transaction and the lower rate they pay to the acquirer. Second, through fees on value-added services such as instant payouts, fraud monitoring, dispute management, and platform or onboarding fees. For platforms using a payfac-as-a-service model, payments can also become a direct revenue stream: the platform earns a share of transaction fees generated by its users.

What is a payfac vs a merchant of record?

A merchant of record (MoR) takes on full commercial and legal responsibility for a transaction, including tax collection, refunds, and chargeback liability. A payfac facilitates payment processing for sub-merchants but leaves chargeback and tax responsibility with those sub-merchants. The MoR model is common in software distribution and marketplaces where the platform wants to fully own the buyer relationship. The payfac model is more common where the platform wants to embed payments without taking on full commercial liability.

What are some examples of payment facilitators?

Well-known payment facilitators include Stripe, Square, and PayPal, each of which allows businesses to start accepting card payments quickly under their master merchant account. Airwallex operates as a global payfac, providing payment facilitation infrastructure to platforms and marketplaces across more than 180 countries.