Payment Facilitator
Entity that aggregates merchant payment acceptance under a master account, enabling sub-merchant onboarding.
A payment facilitator (PayFac) is an entity that has contracted directly with a payment network (Visa, Mastercard) and sponsoring bank to accept payments on behalf of multiple sub-merchants under its own master merchant account. Rather than requiring each merchant to individually undergo the traditional bank merchant account application process, a PayFac assumes the underwriting burden and enables rapid merchant onboarding—sometimes in minutes rather than weeks.
PayFacs operate by aggregating transactions from many smaller merchants under their master account. The PayFac is responsible for risk management, compliance, and settlement to sub-merchants. They receive merchant discount fees from each transaction, retain their markup, and remit the remainder to sub-merchants. Examples include Stripe, Square, PayPal, and Braintree—all function as PayFacs for the small and medium businesses that use their platforms.
The PayFac model differs from a traditional ISO (Independent Sales Organization): ISOs refer merchants to acquiring banks and earn commissions, but each merchant gets their own merchant account with the acquiring bank. PayFacs onboard sub-merchants under their own master account, providing a fully managed payments infrastructure without the merchant needing a bank relationship.
Becoming a registered PayFac requires: registration with Visa and Mastercard, a sponsoring acquiring bank relationship, demonstrated risk management and underwriting capabilities, compliance infrastructure (PCI DSS, AML, KYC), and sufficient financial resources to cover losses. PayFac registration takes 6–12+ months and significant compliance investment.
Software platforms in vertical SaaS (practice management, restaurant POS, e-commerce) increasingly embed PayFac capabilities as a revenue enhancement strategy—enabling payments monetization without losing customers to payment providers.
FAQs
What is the difference between a payment facilitator and an ISO?
An ISO (Independent Sales Organization) markets and resells merchant accounts on behalf of acquiring banks—the bank still owns the merchant relationship, and the merchant has their own merchant account with the bank. A PayFac owns the merchant relationship by aggregating merchants under their own master account—sub-merchants have a relationship with the PayFac, not directly with the bank. ISOs earn referral commissions; PayFacs retain the full merchant discount fee and remit to merchants. PayFacs have more control, more revenue potential, and more responsibility (risk, compliance, chargebacks). ISOs have lower overhead and risk but less revenue potential per merchant.
What is PayFac-as-a-Service and why are software companies using it?
PayFac-as-a-Service (PFaaS) providers like Stripe Connect, Adyen for Platforms, and PayFac by Checkout.com allow software companies to offer PayFac-like payment capabilities—rapid sub-merchant onboarding, embedded payments, revenue sharing—without becoming a registered PayFac themselves. The PFaaS provider handles the registration, compliance, risk management, and bank relationships, while the software platform accesses the capability through API and earns a revenue share per transaction. This model allows vertical SaaS companies to monetize payments within their platforms without the 6–12 month registration process and compliance investment required for direct PayFac registration.
How do PayFacs manage fraud and risk for their sub-merchants?
PayFacs bear ultimate responsibility for losses from fraud, chargebacks, and compliance violations across their sub-merchant portfolio. Risk management approaches include: KYB (Know Your Business) screening during sub-merchant onboarding (business verification, beneficial ownership verification, prohibited business checks); transaction monitoring with ML-based fraud scoring; chargeback monitoring and merchant education; velocity checks limiting transaction frequency and amounts; holds and reserves on high-risk merchant accounts; automated merchant account suspension for fraud patterns; and exposure limits capping how much loss a single sub-merchant can generate. The sophistication of risk operations is a key differentiator between PayFacs.
Related Terms
EMV Chip
Payment card microprocessor chip generating a unique cryptogram for each transaction, preventing card fraud.
Tokenization
Replacing sensitive payment data with a non-sensitive substitute token that has no exploitable value.
Digital Wallet
Software application storing payment credentials and enabling transactions without physical cards.
ISO 20022
Global financial messaging standard enabling richer, more structured payment data across institutions.
