A payment facilitator, or PayFac, is a company that has been approved by an acquiring bank to process card payments on behalf of other businesses, called sub-merchants, under its own master merchant account. Rather than each business obtaining its own merchant account through the traditional underwriting process, the PayFac sponsors sub-merchants under its umbrella, taking on the financial and compliance responsibility for their payment activity.
The PayFac model allows software companies, marketplaces, and platforms to embed payment acceptance directly into their products and onboard merchants in minutes rather than days or weeks. The PayFac handles merchant underwriting, onboarding, risk management, funding, and compliance, while the sub-merchant simply accepts payments through the platform.
PayFac status fundamentally changes the economics of payment processing for software companies. By controlling the payment stack, the PayFac earns a share of payment revenue on every transaction rather than simply referring merchants to a third-party processor.
Diving Deeper into Payment Facilitator
The payment facilitator model is one of the most significant structural developments in the payments industry over the past two decades. It emerged as software platforms recognized that offering integrated payment acceptance was both a product improvement for their customers and a substantial revenue opportunity. Rather than directing merchants to external processors and losing that revenue to a third party, platforms could become the processor themselves — or close to it — by obtaining PayFac status.
Understanding how the PayFac model works, how it differs from the ISO model, and what it takes to operate as a PayFac illuminates both the business opportunity and the operational complexity involved.
How the PayFac Model Works
A PayFac obtains a master merchant account from an acquiring bank. This master account is registered with Visa and Mastercard under the PayFac’s name. The PayFac then onboards sub-merchants — businesses that want to accept card payments — under this master account rather than establishing individual merchant accounts for each one.
When a sub-merchant processes a transaction, it flows through the PayFac’s master merchant account. The acquiring bank settles funds to the PayFac, which then distributes the appropriate amounts to each sub-merchant after deducting its fees. The PayFac owns the funds flow, the pricing relationship with the sub-merchant, and the customer experience of payment acceptance.
Sub-Merchant Onboarding
One of the defining features of the PayFac model is fast sub-merchant onboarding. Because the PayFac has already been approved by the acquiring bank and registered with the card networks, it can onboard sub-merchants using its own underwriting process rather than submitting each merchant for bank review. Well-designed PayFac onboarding flows can approve and activate sub-merchants in minutes using automated identity verification, business verification, and risk scoring.
Funds Flow and Settlement
The PayFac controls the funds flow from settlement through distribution. Funds settle from the card networks to the acquiring bank, then to the PayFac’s master account. The PayFac then splits and distributes funds to sub-merchants on its own funding schedule. This control over funds flow is both a significant responsibility — the PayFac must manage float, reconciliation, and sub-merchant disputes — and a significant commercial advantage, enabling the PayFac to monetize the float and offer differentiated funding terms.
PayFac vs. ISO
The PayFac and ISO models are both distribution channels for payment acceptance, but they differ fundamentally in their structure, economics, and risk profile.
An ISO refers merchants to an acquiring bank and earns residuals on the transaction volume those merchants generate. The ISO does not control the merchant account, the funds flow, or the pricing beyond what they negotiate with the acquiring bank. The ISO’s relationship with the merchant is commercial and service-oriented rather than financial.
A PayFac owns the merchant relationship end to end. It controls onboarding, pricing, funds flow, and customer experience. It earns the full processing margin rather than a residual share. In exchange, it assumes the financial liability for sub-merchant activity, the compliance obligations of a registered PayFac, and the operational complexity of managing a payment platform.
The Registered PayFac Model
Becoming a registered PayFac requires formal registration with Visa and Mastercard, sponsorship by an acquiring bank, and meeting capital and compliance requirements set by the card networks. This is a significant undertaking that requires dedicated compliance and risk infrastructure.
An alternative is the PayFac-as-a-Service model, where a company accesses PayFac-like economics and control through a third-party platform rather than registering directly. Companies like Stripe, Adyen, and others offer software platforms the ability to monetize payments with faster time to market than full PayFac registration, in exchange for a share of the economics.
Risk and Compliance Obligations
The PayFac assumes substantial risk and compliance obligations by sponsoring sub-merchants.
Financial liability for sub-merchant chargebacks is the most significant financial risk. If a sub-merchant generates chargebacks they cannot fund, the PayFac is responsible for the loss. This requires the PayFac to maintain rigorous sub-merchant underwriting and ongoing monitoring, reserve management, and chargeback management capabilities.
Compliance with card network rules flows through the PayFac to all of its sub-merchants. The PayFac must ensure that every sub-merchant it sponsors complies with prohibited business type restrictions, PCI DSS requirements, and transaction processing standards. A violation by a sub-merchant is a violation by the PayFac.
Why Software Companies Become PayFacs
The economics of the PayFac model are compelling for software platforms with large merchant bases. A platform with ten thousand merchants each processing fifty thousand dollars per month at a twenty basis point margin earns one million dollars per month in payment revenue. The same platform operating as an ISO referring merchants to a third-party processor might earn a fraction of that in residuals while giving up the payment relationship entirely.
Beyond revenue, integrated payments improve the platform’s product by simplifying the merchant experience, increase retention by creating switching costs, and provide transaction data that can inform product development and risk decisions.