PayFac Meaning
Definition
PayFac is an abbreviation for Payment Facilitator — an entity registered with card networks (Visa, Mastercard) that acts as a master merchant, enabling sub-merchants to accept card payments under the PayFac's merchant identification number (MID) without each sub-merchant needing their own merchant account.
How It Works
A PayFac obtains a single master merchant account from a sponsoring bank and registers with card networks as a payment facilitator. Sub-merchants are onboarded under this master MID through automated KYC/KYB checks. Transactions from all sub-merchants process through the PayFac's infrastructure, and the PayFac handles settlement — splitting funds between itself (its markup) and the sub-merchant.
Why ISVs Care
The PayFac model is the foundation of embedded payments for ISVs. Understanding what a PayFac is — and the distinction between being a registered PayFac vs. using PayFac-as-a-Service — is essential for any ISV evaluating how to monetize payments within its software.
PayFac means Payment Facilitator — the business model that lets software platforms onboard merchants for card payments in minutes instead of days, while earning revenue on every transaction.
PayFac: The Short Definition
A Payment Facilitator is a company that:
- Holds a master merchant account with an acquiring bank
- Is registered with Visa and Mastercard as a payment facilitator
- Onboards sub-merchants under its own merchant ID
- Processes, settles, and splits payment funds on behalf of those sub-merchants
The most recognizable PayFacs are Square, Stripe, and PayPal — but the model extends far beyond consumer-facing companies. Hundreds of vertical software companies (ISVs) now operate as PayFacs or use PayFac-as-a-Service to embed payments into their platforms.
Why “PayFac” Keeps Coming Up
If you’re researching payment integration for your software company, you’ve probably encountered “PayFac” dozens of times. Here’s why it matters:
Before PayFacs existed, every merchant needed their own merchant account — a process involving paper applications, credit checks, underwriting, and 3-7 business days of waiting. This was incompatible with modern software where users expect to be live in minutes.
PayFacs changed this by aggregating merchants under a single account. The PayFac takes responsibility for vetting merchants and monitoring transactions, which lets it onboard new sub-merchants almost instantly.
For ISVs, this means your software can include “start accepting payments” as a native feature — not a separate process that sends merchants to a third party.
The PayFac Ecosystem
The term “PayFac” shows up in several contexts:
Registered PayFac
A company that has completed full PayFac registration with card networks and a sponsoring bank. This requires significant capital ($500K-$2M+), a compliance team, and ongoing risk management.
PayFac-as-a-Service (PFaaS)
A provider that lets ISVs act like a PayFac without the registration. The PFaaS company holds the PayFac registration; the ISV integrates their APIs and gets PayFac-like merchant onboarding and revenue sharing.
PayFac Model
The broader concept of aggregating merchants under a master MID, regardless of who holds the registration. When people say “the PayFac model,” they mean this approach to payment facilitation.
PayFac vs. Traditional Payment Processing
| Aspect | Traditional (ISO/Agent) | PayFac Model |
|---|---|---|
| Merchant onboarding | 3-7 days | Minutes |
| Each merchant needs | Own merchant account | Sub-merchant under master MID |
| Underwriting | Processor handles | PayFac handles |
| Settlement | Direct to merchant | PayFac splits funds |
| ISV revenue | Residual (5-15 bps) | Revenue share (20-100+ bps) |
| Risk liability | Processor/ISO | PayFac |
PayFac Registration Requirements
Becoming a registered PayFac involves:
- Sponsoring bank: An acquiring bank that agrees to underwrite the PayFac’s master merchant account
- Card network registration: Filing with Visa and Mastercard as a Payment Facilitator participant
- Compliance: PCI DSS Level 1 certification, KYC/KYB procedures, transaction monitoring, chargeback management
- Capital: Financial reserves to cover potential losses from sub-merchant fraud or chargebacks
- Technology: APIs for merchant onboarding, transaction processing, settlement splitting, and reporting
The total investment and timeline make full registration practical only for ISVs processing $100M+ annually with a clear payment revenue strategy.
Should Your ISV Become a PayFac?
For most ISVs, the answer is “not yet” — but PayFac-as-a-Service makes the benefits accessible without the investment. Start with PFaaS to validate the payment revenue opportunity, then evaluate full registration once your aggregate volume justifies the economics.
The key insight: you don’t need to be a registered PayFac to benefit from the PayFac model. PFaaS providers let ISVs offer the same merchant experience and earn meaningful revenue from day one.