What is Payment Facilitator?

What Is a Payment Facilitator?

A payment facilitator -- commonly shortened to PayFac -- is a company that has been registered with the card networks (Visa, Mastercard, etc.) to onboard, underwrite, and manage sub-merchants under its own master merchant account. PayFacs enable smaller businesses to accept card payments without going through the traditional merchant account application process.

Think of a PayFac as a middleman with formal authority. The card networks have specifically approved the PayFac to bring merchants onto the payment network, take responsibility for their compliance, and manage the risk they represent. This is more than just processing payments -- it is a regulated role with specific obligations.

How the PayFac Model Works

In the traditional payment model, every merchant has a direct relationship with an acquiring bank. They apply for a merchant account, undergo underwriting, receive their own merchant identification number (MID), and manage their own PCI DSS compliance. This works well for large businesses but creates barriers for smaller ones.

The PayFac model changes this:

• Master merchant account -- The PayFac holds the relationship with the acquiring bank and maintains one or more master merchant accounts.
• Sub-merchant onboarding -- Instead of applying to a bank, new merchants sign up through the PayFac. The PayFac handles identity verification (KYC), risk assessment, and compliance checks.
• Transaction processing -- Sub-merchant transactions are processed under the PayFac's master MID. The PayFac's payment descriptor may appear on the customer's bank statement, sometimes alongside the sub-merchant's name.
• Fund management -- The PayFac receives settlement funds and distributes them to sub-merchants according to agreed schedules.
• Ongoing monitoring -- The PayFac is responsible for monitoring sub-merchant transactions for fraud, chargebacks, and compliance issues.

PayFac Responsibilities

Becoming a PayFac is not trivial. The card networks impose significant requirements:

• Registration -- The company must register with each card network through a sponsoring acquiring bank.
• Underwriting -- The PayFac must perform due diligence on every sub-merchant, including identity verification, business validation, and risk assessment.
• PCI DSS compliance -- The PayFac must be PCI DSS compliant and must ensure its sub-merchants meet applicable requirements.
• Transaction monitoring -- Ongoing monitoring for suspicious activity, excessive chargebacks, and prohibited business types.
• Chargeback management -- The PayFac bears ultimate responsibility for chargebacks if a sub-merchant cannot cover them.
• Regulatory compliance -- Adherence to all applicable financial regulations, anti-money laundering requirements, and card network rules.

PayFac vs Payment Aggregator

These terms overlap significantly, and many companies operate as both. The key distinction is that "payment facilitator" is a formal designation granted by the card networks, while "payment aggregator" is a broader, less formal term for any company that pools merchants under a shared account.

In practice, a PayFac is a payment aggregator that has gone through the formal registration process and accepted the regulatory obligations that come with it. Companies like Stripe and Square are registered PayFacs -- they have been approved by the card networks to onboard and manage sub-merchants.

Who Becomes a PayFac?

The PayFac model is popular with:

• Software platforms -- SaaS companies that want to embed payments into their product (e.g., a restaurant management platform that processes payments for its restaurant clients).
• Marketplaces -- Online marketplaces that need to onboard sellers quickly and manage payments across multiple parties.
• Payment companies -- Dedicated payment service providers that offer turnkey payment acceptance to businesses of all sizes.

Becoming a PayFac requires significant investment in technology, compliance infrastructure, and risk management. Many companies that want embedded payment capabilities choose to use a "PayFac-as-a-Service" provider instead of building the infrastructure themselves.

PayFacs and Telephone Payments

PayFacs primarily focus on online and in-person payment channels. Telephone payment capabilities -- particularly secure, PCI-compliant phone payments -- are not a standard feature of most PayFac platforms. This means businesses using a PayFac for their primary payment processing may need a separate solution for handling phone payments securely.

The PCI DSS compliance dimension is particularly important here. While the PayFac handles compliance for online transactions processed through its platform, telephone payments introduce a different set of challenges involving voice channels, call recordings, and agent access to card data. These require specialised technology to address.

The Economics of Being a PayFac

The PayFac model creates a distinct economic structure. The PayFac negotiates wholesale processing rates with its acquiring bank based on its total transaction volume across all sub-merchants. It then charges sub-merchants a markup on those rates, keeping the spread as revenue.

This can be highly profitable at scale. A PayFac processing billions in annual volume can negotiate very low interchange-plus rates and charge sub-merchants a flat fee that includes a healthy margin. The trade-off is the risk -- the PayFac absorbs chargeback losses from sub-merchants who cannot cover them, bears the cost of fraud monitoring and compliance infrastructure, and carries the regulatory burden of managing potentially thousands of sub-merchants.

PayFac-as-a-Service

Not every company that wants embedded payments needs to become a full PayFac. PayFac-as-a-Service providers offer the economic and onboarding benefits of the PayFac model without requiring the company to build all the infrastructure and take on all the regulatory obligations themselves.

In this model, a technology company partners with a PayFac-as-a-Service provider that handles the acquiring bank relationship, compliance, and fund management. The technology company still controls the sub-merchant experience and can embed payments into their platform, but the heavy lifting of regulation, risk, and settlement is handled by the service provider.

This approach has accelerated the adoption of embedded payments across software-as-a-service platforms in industries from healthcare to hospitality. It allows software companies to offer payments as a feature without becoming regulated financial entities themselves.