Payment Facilitator (PayFac)

What Is a Payment Facilitator?

A payment facilitator, commonly called a PayFac, is a company that enables other businesses (called sub-merchants) to accept electronic payments by processing those transactions under its own master merchant identification number (MID). Rather than each merchant applying for a separate merchant account with an acquirer, the PayFac acts as an intermediary: it registers with the card networks (Visa, Mastercard) through a sponsoring acquiring bank, receives a master MID, and then onboards sub-merchants under that umbrella.

The PayFac model was formally introduced by the card networks around 2011, evolving from earlier payment aggregator concepts. The key motivation was enabling faster merchant onboarding while maintaining transparency into sub-merchant identities for compliance purposes. Companies like Stripe, Square, and PayPal popularized this model by letting businesses start accepting payments within hours rather than navigating weeks of traditional bank underwriting.

The global payment facilitation market was valued at approximately $15.2 billion in 2024, with projections reaching $54.8 billion by 2033. PayFacs are expected to handle more than $4 trillion in payment volume globally, reflecting the model's dominance in modern commerce.

How It Works

The PayFac model involves three primary parties working together to process transactions:

1. The acquirer (sponsoring bank) provides the payment infrastructure and card network access. It underwrites the PayFac itself, not individual sub-merchants.
2. The PayFac holds the master merchant account. It recruits, onboards, and manages sub-merchants. All transactions flow through its master MID.
3. Sub-merchants are the end businesses accepting payments. Each may receive a unique sub-MID for granular reporting, but transactions settle through the PayFac's master account.

When a customer makes a purchase from a sub-merchant, the transaction routes through the PayFac's master merchant account. The PayFac aggregates payments from all its sub-merchants, settles with the acquiring bank, and then distributes funds to each sub-merchant on a scheduled basis.

PayFac vs. Traditional Merchant Accounts

In the traditional model, each merchant applies directly to an acquiring bank for its own merchant account. This process involves extensive paperwork, credit checks, and underwriting that can take days to weeks. The merchant maintains a direct banking relationship and bears full responsibility for compliance.

PayFac Responsibilities

Operating as a PayFac comes with significant obligations. The PayFac assumes liability for all sub-merchant activity and must implement robust systems across several areas:

• KYC and onboarding: verifying sub-merchant identities, checking OFAC sanctions lists and card network MATCH lists, and confirming business legitimacy before activation
• Risk monitoring: continuously analyzing transaction patterns for fraud, applying processing caps or reserves where needed, and managing chargebacks across the portfolio
• PCI DSS compliance: maintaining Level 1 or Level 2 certification as a service provider, securing all cardholder data, and ensuring sub-merchants also meet compliance standards
• Settlement and funding: distributing funds to sub-merchants on a defined schedule, handling reconciliation, and generating tax documentation

Becoming a registered PayFac typically requires 12 to 18 months of preparation and hundreds of thousands of dollars in implementation costs. Mastercard charges an initial registration bundle fee of $5,200. The economics generally only make sense for platforms processing $50 million or more in annual volume.

Card Network Rules and Compliance

PayFacs operate under strict rules set by the card networks. Recent years have brought significant changes to how these rules are enforced:

• Visa launched its Acquirer Monitoring Program (VAMP) in April 2025, imposing stricter fraud and dispute rate thresholds on acquirers and their PayFac partners. Lower thresholds took effect in January 2026.
• Visa relaxed certain structural rules in 2025: PayFacs can now contract with sub-merchants in different countries, and new verticals like registered marketplaces and bill payment service providers became eligible for the model.
• In the United States, PayFacs handling fiat currency typically need money transmitter licenses in most states, with surety bond requirements ranging from $25,000 to over $1 million depending on the jurisdiction.
• In Europe, PSD3 (Payment Services Directive 3) reached provisional agreement in November 2025, strengthening consumer protection and fraud prevention requirements for payment service providers including PayFacs.

Use Cases

Software Platforms and Marketplaces

The most common PayFac use case is software platforms that embed payments into their products. A restaurant management platform, for example, can onboard new restaurants and enable payment acceptance within its own interface rather than directing each restaurant to set up a separate merchant account. This creates a seamless experience and generates additional revenue for the platform through transaction fees.

E-Commerce and Retail

Online marketplaces use the PayFac model to let individual sellers accept payments without friction. The marketplace acts as the merchant of record, handling all payment complexity behind the scenes. This is how platforms like Shopify Payments and Amazon's marketplace operate: sellers focus on their products while the platform manages payment processing, compliance, and settlement cycles.

Crypto Payment Processing

Cryptocurrency payment processors like BitPay and Coinbase Commerce use a structurally similar aggregation model. A single entity manages wallets, compliance, and fiat conversion for many merchants. The processor maintains the regulatory licenses, implements KYC procedures, and handles the complexity of converting crypto payments to fiat settlement.

This parallel extends to platforms built on Bitcoin Layer 2 solutions. A payment service built on a protocol like Spark could aggregate merchant payment processing in the same way: onboarding sub-merchants, managing compliance, and settling transactions, while leveraging the speed and low cost of off-chain Bitcoin transfers and stablecoins on Bitcoin.

PayFac-as-a-Service

A rapidly growing segment is PayFac-as-a-Service (PFaaS), where infrastructure providers handle the technical and regulatory complexity of becoming a PayFac. This reduces time to market from months to weeks and makes the model accessible to smaller platforms that cannot justify the cost of building PayFac infrastructure from scratch. Mastercard has publicly endorsed PFaaS as the future of payment facilitation, and providers like Finix, Payrix, and Infinicept specialize in this space.

Why It Matters

The PayFac model fundamentally changed how businesses access payment infrastructure. Before PayFacs, small businesses faced significant barriers: lengthy application processes, high fees, and complex compliance requirements. By aggregating these responsibilities under a single entity, PayFacs democratized access to electronic payments.

For developers building payment applications, understanding the PayFac model is essential. Whether integrating traditional card processing through platforms like Stripe or building crypto-native payment solutions using Bitcoin rails, the core pattern is the same: a trusted intermediary simplifies the complexity of accepting payments for many merchants. As explored in the Bitcoin merchant payments guide, crypto payment platforms are increasingly adopting this same aggregation approach to bridge the gap between digital assets and merchant commerce.

Risks and Considerations

Concentration Risk

Because all sub-merchants process through the PayFac's master account, a compliance failure or fraud event at the PayFac level can affect every sub-merchant. If the acquiring bank terminates the PayFac relationship, all sub-merchants lose payment processing simultaneously. This single point of failure contrasts with the traditional model where each merchant's account is independent.

Liability Exposure

PayFacs bear full financial liability for their sub-merchants' chargebacks, fraud losses, and compliance failures. A single bad actor among thousands of sub-merchants can generate significant losses. Effective risk monitoring requires sophisticated systems and constant vigilance, particularly for high-risk merchant categories.

Regulatory Complexity

Operating across jurisdictions means navigating different regulatory regimes simultaneously. Card network rules evolve frequently: Visa's VAMP program introduced new monitoring thresholds, and Mastercard's fee structures change periodically. In the crypto space, regulations like the GENIUS Act (signed into law in 2025 for payment stablecoins) and the EU's MiCA framework add additional layers of compliance for platforms bridging traditional and digital payments. Keeping up with these changes requires dedicated compliance resources.

Fund Flow Risks

Since funds from all sub-merchant transactions initially flow into the PayFac's master account before distribution, there is inherent counterparty risk. Sub-merchants depend on the PayFac's financial health and operational reliability for timely settlement. Regulatory frameworks require PayFacs to segregate settlement funds and use them only for sub-merchant payouts, but enforcement varies by jurisdiction.

This glossary entry is for informational purposes only and does not constitute financial or investment advice. Always do your own research before using any protocol or technology.