What Is Payment Facilitator?

A payment facilitator (PayFac) is a registered entity that simplifies merchant onboarding for card payment acceptance by processing transactions on behalf of sub-merchants under a single master merchant account. Instead of each merchant going through the traditional process of applying for and maintaining their own merchant account with an acquiring bank, the PayFac aggregates many merchants under its umbrella, handling onboarding, risk management, compliance, and payment processing.

## How the PayFac Model Works

In the traditional card payment model, each merchant must: 1. Apply for a merchant account with an acquiring bank. 2. Undergo underwriting (credit checks, business verification, risk assessment). 3. Wait days to weeks for approval. 4. Manage their own PCI compliance, chargeback monitoring, and bank relationship.

The PayFac model eliminates most of this friction. The PayFac holds the master merchant account with one or more acquiring banks and has been registered with the card networks (Visa, Mastercard) as a payment facilitator. When a new sub-merchant signs up:

1. The PayFac conducts streamlined KYC (Know Your Customer) and risk checks — often automated, taking minutes rather than days. 2. The sub-merchant is assigned an identifier under the PayFac's master merchant account. 3. Transactions are processed through the PayFac's acquiring relationship. 4. The PayFac handles settlement, splitting funds between its own fees and the sub-merchant's payout.

## PayFac Examples

The most prominent PayFacs include:

- **Stripe**: Perhaps the best-known PayFac, Stripe onboards merchants instantly through its Connect platform. Stripe holds acquiring relationships and processes all sub-merchant transactions under its master merchant ID. - **Square**: Enables small businesses to accept payments through its POS hardware and software, processing all transactions under Square's master merchant account. - **PayPal**: Operates as a PayFac for its merchant customers, allowing businesses to accept payments without a separate merchant account. - **Shopify Payments**: Acts as a PayFac for Shopify merchants, powered by Stripe's infrastructure.

## PayFac vs ISO (Independent Sales Organization)

Before PayFacs, ISOs (Independent Sales Organizations) were the primary intermediaries between merchants and acquirers. The key differences:

- **ISOs** refer merchants to acquiring banks but do not process transactions themselves. The merchant gets their own merchant ID, and the acquirer handles processing. ISOs earn referral commissions and may provide support, but the merchant-acquirer relationship is direct. - **PayFacs** process transactions under their own master merchant ID. The sub-merchant does not have a direct relationship with the acquirer. The PayFac owns the processing relationship and bears the primary risk.

## PayFac Responsibilities

Being a PayFac comes with significant responsibilities:

**Risk management**: The PayFac is liable for its sub-merchants' transactions. If a sub-merchant commits fraud or generates excessive chargebacks, the PayFac bears the financial loss (it can then attempt to recover from the sub-merchant). This is why PayFacs invest heavily in fraud detection, monitoring, and risk scoring.

**KYC and compliance**: PayFacs must verify sub-merchant identities, screen against sanctions lists, and ensure compliance with card network rules. While the onboarding process is faster than traditional underwriting, PayFacs still perform due diligence.

**PCI compliance**: The PayFac must maintain PCI DSS Level 1 compliance (the highest level) because it processes card data for multiple merchants. Sub-merchants benefit from the PayFac's PCI-compliant infrastructure without needing their own Level 1 certification.

**Settlement and payouts**: The PayFac receives settlement from its acquirer and is responsible for distributing funds to sub-merchants according to agreed terms.

## Becoming a PayFac

Companies that want to become a PayFac must register with the card networks (Visa and Mastercard each have registration programs), establish a master merchant account with an acquiring bank, achieve PCI DSS Level 1 compliance, build or license the technology for sub-merchant management, and invest in risk and compliance infrastructure. The process typically takes 6-12 months and requires significant upfront investment.

Alternatively, platforms can use "PayFac-as-a-Service" solutions offered by companies like Stripe Connect, Adyen for Platforms, or Payoneer, which provide the PayFac infrastructure without requiring the platform to register as a PayFac itself.

## PayFac vs Payment Orchestration

Payment facilitators and payment orchestrators serve different purposes. A PayFac provides the acquiring infrastructure and merchant account aggregation. A payment orchestrator routes transactions across multiple PSPs, acquirers, and payment methods to optimize cost, conversion, and reliability. Some platforms use both — operating as a PayFac for primary processing while using an orchestrator to route specific transactions through alternative providers.