Payment Facilitation as a Service: How PayFac Models Are Reshaping Modern Payment Processing

The payment facilitator model, often called PayFac, has emerged as one of the most transformative forces in the payment processing industry. Pioneered by companies like Stripe, Square, and PayPal, the PayFac model enables platforms, marketplaces, and software providers to offer payment acceptance to their sub-merchants without each one needing to obtain a traditional merchant account. Instead, the platform becomes the merchant of record with the card networks and sponsors sub-merchants under its own processing relationship. This model has dramatically reduced the friction of payment acceptance, enabling millions of small businesses to accept card payments for the first time.

In 2026, the PayFac model has evolved significantly. The rise of PayFac-as-a-Service (PFaaS) providers has made it possible for virtually any platform or software company to become a payment facilitator without building the complex infrastructure from scratch. PFaaS providers offer the technology stack, regulatory compliance framework, underwriting capabilities, and risk management systems that a PayFac needs, packaged as a turnkey solution. This has opened the PayFac model to a much broader range of businesses, including those in high-risk industries that were previously excluded from the PayFac ecosystem.

How the PayFac Model Works

In the traditional payment processing model, each merchant must establish its own direct relationship with an acquiring bank, complete a full underwriting application, sign a merchant services agreement, and obtain its own merchant identification number from the card networks. This process can take weeks and requires significant documentation. For a software platform that serves thousands of small merchants, requiring each one to go through this process individually is impractical and would severely limit the platform's ability to offer integrated payment processing.

The PayFac model solves this problem by creating a hierarchical structure. The payment facilitator registers with Visa and Mastercard as a payment facilitator, which requires the PayFac to obtain a sponsor bank relationship and meet the networks' registration requirements. Once registered, the PayFac can onboard sub-merchants under its own merchant identification number, using its own underwriting criteria and risk management systems. The sub-merchants do not need to obtain their own merchant accounts. Instead, they enter into a contractual relationship with the PayFac, which handles all payment processing on their behalf.

From the card network's perspective, the PayFac is the merchant. All transactions from all sub-merchants settle to the PayFac, which then manages the settlement of funds to individual sub-merchants according to its own schedule and rules. This settlement responsibility creates significant operational and risk management requirements, as the PayFac must have systems in place to handle failed settlements, reserve funds, and regulatory obligations.

PayFac-as-a-Service: The Technology Stack

Becoming a payment facilitator requires a substantial technology investment. The PayFac must integrate with the card networks or an acquiring bank, build or license a transaction processing engine, implement a sub-merchant onboarding system with Know Your Customer (KYC) and identity verification capabilities, build a settlement engine that can calculate fees and distribute funds to sub-merchants, develop a risk management system for monitoring sub-merchant activity, implement chargeback management and dispute resolution workflows, and maintain compliance with PCI DSS, anti-money laundering regulations, and card network rules. Building this infrastructure from scratch typically costs millions of dollars and requires 12 to 24 months of development time.

PayFac-as-a-Service providers have emerged to eliminate this barrier. Companies like Stripe Connect, Finix, Infinicept, and others offer comprehensive PFaaS platforms that provide the full technology stack needed to operate as a payment facilitator. These platforms handle transaction processing, sub-merchant onboarding and KYC, settlement and funds distribution, risk monitoring and compliance, chargeback management, and reporting and analytics. The platform integrates with the PayFac's existing software through APIs, allowing the platform to offer payment processing as an integrated feature of its core product.

The PFaaS model has evolved to support different levels of integration. Some platforms want full control over the sub-merchant experience, including the ability to set their own pricing, manage their own risk criteria, and customize the onboarding flow. Other platforms prefer a more hands-off approach, where the PFaaS provider handles underwriting and risk decisions directly. The choice between these approaches depends on the platform's risk appetite, regulatory obligations, and the complexity of its sub-merchant base.

Regulatory and Compliance Obligations

Operating as a payment facilitator carries significant regulatory obligations. In the United States, PayFacs must register with Visa and Mastercard as payment facilitators, which requires meeting the networks' financial stability, operational capability, and risk management standards. PayFacs must also register in each state where they onboard sub-merchants, as money transmission laws apply to the settlement of funds to sub-merchants. The regulatory landscape is complex, with 49 states and the District of Columbia having money transmission licensing requirements, each with different application processes, bonding requirements, and reporting obligations.

Anti-money laundering and KYC requirements are a critical compliance area for PayFacs. The Bank Secrecy Act requires PayFacs to implement customer identification programs, verify the identity of each sub-merchant, screen against Office of Foreign Assets Control sanctions lists, monitor transactions for suspicious activity, and file Suspicious Activity Reports when required. The Financial Crimes Enforcement Network has issued specific guidance on the application of AML requirements to payment facilitators, making clear that PayFacs bear the primary responsibility for their sub-merchants' compliance.

For PayFacs operating in high-risk verticals, compliance obligations are even more demanding. Card networks impose additional monitoring requirements on PayFacs whose sub-merchant base includes high-risk merchant categories. Visa's Global Brand Protection Program and Mastercard's Merchant Monitoring Program apply to PayFacs as well as individual merchants, and a PayFac with a high concentration of high-risk sub-merchants faces elevated scrutiny. PayFacs serving high-risk verticals must invest in more sophisticated underwriting, real-time transaction monitoring, and chargeback prevention systems to maintain their network registrations.

Revenue Models and Economics

The economics of the PayFac model are compelling for platforms that can achieve sufficient scale. PayFacs typically earn revenue from multiple sources including the spread between the interchange rate they pay and the rate they charge sub-merchants, monthly platform or gateway fees charged to sub-merchants, per-transaction fees in addition to the percentage markup, and ancillary services such as chargeback management, fraud screening, and reporting. Successful PayFacs can achieve payment processing margins of 100 to 300 basis points on the volume they process, with additional revenue from fixed fees.

The PFaaS model changes the revenue structure. PFaaS providers typically charge a percentage of the payment volume processed through the platform, ranging from 10 to 50 basis points, plus fixed monthly fees for platform access and support. The PayFac retains the remaining markup, which means that platforms with higher volumes can negotiate lower PFaaS fees and achieve better economics. For platforms that process less than $10 million annually, the economics of becoming a PayFac may not justify the investment, and referring payment processing to a third-party provider with a revenue share arrangement may be more cost-effective.

For high-risk merchants considering the PayFac model as sub-merchants, the advantages are significant. PayFacs typically offer faster onboarding than traditional merchant accounts, with some platforms approving sub-merchants in minutes rather than days or weeks. PayFac pricing, while often higher than the best negotiated traditional merchant account rates, is typically transparent and predictable. However, high-risk sub-merchants face unique challenges in the PayFac ecosystem, including more frequent reserve requirements and the risk of account holds or terminations when the PayFac's risk systems flag unusual activity.

The Future of PayFac and PFaaS

The PayFac model continues to evolve rapidly. Cross-border payment facilitation is growing, with PayFacs onboarding sub-merchants in multiple countries and settling funds in multiple currencies. Regulatory harmonization efforts, particularly in Europe where the Payment Services Directive has created a more uniform regulatory framework, are making it easier for PayFacs to operate across borders. In the United States, efforts to create a streamlined money transmission licensing framework through the Conference of State Bank Supervisors' model legislation are progressing, though the regulatory patchwork remains challenging.

Embedded finance is the natural extension of the PayFac model. Platforms that start with payment processing are increasingly adding lending, card issuing, and banking services to their offerings, creating comprehensive financial services platforms that serve their sub-merchants' full financial needs. The PFaaS providers are evolving to support this expansion, offering modular financial services infrastructure that platforms can assemble according to their specific needs and regulatory obligations. For high-risk merchants, the expansion of embedded finance through the PayFac model could open access to capital and financial services that have historically been difficult to obtain from traditional providers.

As the PayFac ecosystem matures, the distinction between payment facilitators and traditional acquirers is blurring. Traditional acquirers are launching PayFac solutions, and PayFacs are acquiring traditional processing capabilities. The end state is likely a unified processing ecosystem where the choice between PayFac and traditional merchant account depends on the specific needs of the merchant and the capabilities of the platform through which they process payments.