What Is a Payment Facilitator? PayFac Model Explained
Getting a merchant account the traditional way takes weeks. A payment facilitator skips most of that. Merchants sign up under the PayFac's master account as sub-merchants and start accepting card payments in hours — sometimes minutes.
For platforms and marketplaces, the PayFac model has become the standard payment solution for embedding payments without building acquiring infrastructure from scratch. Stripe, Square, and PayPal built their businesses on this structure. So have thousands of SaaS companies that handle payments inside their own products without their users ever talking to a bank.
How the PayFac Model Works
A payment facilitator holds a master merchant account with an acquiring bank. That's the core of the structure. Rather than every merchant going through their own underwriting and approval process, the PayFac does it once — then onboards individual businesses as sub-merchants underneath that master account.
The money flow works like this:
- A customer makes a payment to a sub-merchant
- The funds flow into the PayFac's master merchant account
- The PayFac deducts its fee (typically a percentage plus a flat amount)
- The remaining funds are settled to the sub-merchant, usually within 1–2 business days
The PayFac handles the acquirer relationship, the compliance work, and the fraud monitoring. Sub-merchants get payment acceptance without touching any of it.
Fast onboarding is possible because of this structure. Traditional merchant accounts need full underwriting: financial statements, processing history, risk assessment. The PayFac has already cleared that bar for itself. Adding a new sub-merchant only takes a simplified KYC check, which runs in minutes.
Payment Facilitator vs. Traditional Merchant Account
The differences between a payment facilitator relationship and a direct merchant account show up in four areas:
| Factor | Traditional Merchant Account | Payment Facilitator |
|---|---|---|
| Approval time | 2–4 weeks | Minutes to 48 hours |
| Underwriting | Full due diligence, financial statements | Simplified KYC, basic verification |
| Fees | Interchange-plus or negotiated flat rate | Slightly higher per-transaction rate |
| Setup | Paperwork-heavy, bank relationship required | Self-serve, API or dashboard signup |
| PCI scope | Merchant is in scope | Reduced scope — PayFac manages most requirements |
| Liability for fraud | Merchant bears own risk | PayFac bears risk for sub-merchant portfolio |
For small businesses and startups, the traditional route is slow and often not even available. Acquirers won't underwrite merchants below certain volume thresholds. A PayFac absorbs that risk and handles the bank relationship on their behalf.
The math shifts at higher volumes. Merchants with strong processing history and significant transaction flow can often negotiate better interchange rates through a direct merchant account than they'd get on a PayFac's standard pricing.
Payment Facilitator vs. Payment Processor vs. ISO
These three terms get mixed up constantly. The differences matter.
Most people in payments have a vague sense that processors, ISOs, and PayFacs are different things. The actual distinction comes down to liability.
Worldpay routes your transaction data to the card network. TSYS does the same. Neither company cares much what happens to your business — they're infrastructure providers. No merchant relationship, no underwriting responsibility, no exposure when chargebacks pile up.
ISOs are different in one specific way: they actually sign merchants. An ISO acts as a sales arm for an acquiring bank, finding merchants and setting them up with accounts. The ISO earns a revenue share. But legally the merchant answers to the acquirer. If that merchant turns fraudulent, the ISO walks away clean.
That's the gap a payment facilitator fills — and it's a big one. Sub-merchants sign with the PayFac directly. The PayFac underwrites them, processes their transactions, and holds the liability for everything that goes wrong. Fraud losses, chargeback shortfalls, compliance failures — all of it lands on the PayFac's balance sheet. That's why PayFac underwriting is more than a checkbox and why monitoring doesn't stop at onboarding.
Advantages of Using a Payment Facilitator
For merchants who want a fast payment solution without navigating the complexity of direct bank relationships, the PayFac model offers real advantages:
- Fast onboarding — approval in minutes or hours, not weeks; some platforms enable payments in under 15 minutes
- No direct bank relationship required — the PayFac handles all acquirer communications and negotiations
- Reduced PCI scope — the PayFac manages most PCI DSS compliance obligations at the master account level
- Built-in fraud monitoring — PayFacs run transaction monitoring across their entire sub-merchant portfolio
- Unified reporting — single dashboard covering all payment activity, chargebacks, and settlements
- Works for platforms and marketplaces — PayFac structure is well-suited to SaaS platforms that need to embed payments for their users
Risks and Responsibilities for PayFacs
The PayFac model concentrates compliance and financial risk in one place. For businesses that want to become a PayFac rather than just use one, that means taking on a serious operational burden.
The core responsibilities:
- Chargeback liability — if a sub-merchant can't cover chargebacks, the PayFac pays. This applies to the entire portfolio, not just individual merchants
- Fraud monitoring — PayFacs must detect and terminate risky sub-merchants before losses accumulate
- Visa/Mastercard thresholds — chargeback ratios are monitored at the master account level. Visa's VDMP (Visa Dispute Monitoring Program) triggers review when the portfolio exceeds 0.9% chargebacks; higher thresholds can result in fines or termination
- PCI DSS compliance — the PayFac is responsible for maintaining compliance at the master account level and ensuring sub-merchants follow card data handling rules
- AML and KYC obligations — ongoing monitoring of sub-merchants for suspicious transaction patterns, not just at onboarding
- Sub-merchant termination — PayFacs must be able to offboard merchants quickly when risk thresholds are breached
None of this is cheap to build. Stripe has published figures suggesting full PayFac infrastructure runs $50,000–$500,000 for PCI compliance alone, $600,000 or more for merchant management systems, and over $1 million for licensing in multiple jurisdictions.
Who Uses Payment Facilitators?
Traditional acquirers wouldn't underwrite food trucks, market stalls, or solo practitioners. Square built its entire early business serving that ignored group. PayPal did something similar for e-commerce sellers who had no realistic path to a merchant account in the early 2000s. Both scaled into massive businesses precisely because the existing system left those customers out.
Smaller merchants, freelancers, and new companies without processing history are still the natural fit for PayFac onboarding. But the growth in recent years has come from a different direction.
Platforms and marketplaces now drive a large share of PayFac adoption. Gym management software that processes membership payments, gig economy apps that split payouts between workers and the platform, project tools with built-in billing — none of those want to manage acquiring relationships. They either integrate with an existing payment facilitator or register as one to control the payment experience inside their product.
Notable examples:
- Stripe — operates as a PayFac in most markets; Stripe Connect provides PayFac-as-a-service for platforms
- Square — classic PayFac model, built around small merchants using card readers
- PayPal — functions as a PayFac; eBay used PayPal as its PayFac for over a decade
- Adyen for Platforms — targets enterprise marketplaces and platforms needing full PayFac functionality
Amazon processes payments through proprietary infrastructure and doesn't operate as a registered PayFac.
How PayFacs Make Money
Charge a sub-merchant 2.9% + $0.30. Pay interchange of roughly 1.5–2.0% plus acquirer fees. Keep the difference. That spread — often 0.5–1.0% plus the flat portion — is how a PayFac makes money on every transaction that flows through its platform.
It's a thin margin per transaction. It becomes a very large number at scale.
Additional revenue comes from:
- Monthly platform or subscription fees for access to the dashboard, reporting, and support
- Hardware revenue for card readers and terminals (significant for Square)
- Value-added services such as fraud tools, chargeback dispute management, analytics, and lending products
- Currency conversion on cross-border transactions
Square processed over $200 billion in gross payment volume in 2023. Even a fraction of a percent on that volume produces substantial income — which explains why payment facilitation has attracted so much capital.
Should Your Business Become a PayFac?
Registering as a payment facilitator is expensive to do right. PCI compliance alone runs $50,000–$500,000. Add $600,000+ for merchant management infrastructure, and over $1 million for licensing in multiple jurisdictions. Most businesses don't have the volume or the risk appetite to justify it.
The profile that actually makes sense:
- High transaction volume — below $50M+ annually, compliance costs likely outweigh the margin benefit
- Platform or marketplace model — many merchants under your umbrella, with you controlling the onboarding experience
- Need for payment control — you want to set pricing, manage settlement timing, and own the merchant relationship directly
- Technical and compliance capacity — engineers and compliance staff who can build and maintain the infrastructure long-term
For everyone else, PayFac-as-a-service is the practical payment solution. Stripe Connect, Adyen for Platforms, and Payrix let platforms offer payment facilitation to their users without any of the licensing burden. The platform owns the user experience and earns revenue share; the actual PayFac infrastructure handles compliance, underwriting, and settlement in the background.
For merchants extending into cryptocurrency — whether for international reach, lower transaction fees, or customer preference — Plisio provides a crypto payment gateway that works alongside traditional PayFac solutions, letting merchants accept digital assets without managing wallet infrastructure.
