Payment Facilitator (PayFac)
Business model where company becomes master merchant and onboards sub-merchants under their account. Used by platforms like Shopify and Stripe.
Overview
What is Payment Facilitator?
Payment facilitation lets a platform become a master merchant and onboard its own sub-merchants underneath it, rather than each sub-merchant getting its own individual account. That comes with full responsibility for risk, compliance, and underwriting across every sub-merchant — the PayFac must register with the card networks and maintain its own reserves. Shopify and Stripe Connect are the best-known examples. In exchange, the platform captures the processing revenue itself and controls the entire payment experience.
Becoming a PayFac means building a real onboarding pipeline: a master merchant account, a KYC and underwriting flow that runs on every sub-merchant that signs up, and ongoing operations to distribute funds, charge fees, monitor performance, and terminate merchants that turn risky. Because every transaction runs through the master account, the platform assumes the full risk for every sub-merchant beneath it — not just its own.
The economics can be substantial: a platform with 5,000 sub-merchants processing $200M can capture 0.5-1% of that as revenue — $1M-2M annually — while controlling onboarding, pricing, and the entire customer experience. That upside comes with a real entry cost, typically $100K-500K+ in startup investment plus ongoing compliance and liability, which is why most platforms use PayFac-as-a-Service (Stripe Connect and similar) rather than registering as a direct PayFac themselves.
The risk side is not theoretical: weak sub-merchant underwriting can let prohibited businesses onboard undetected, and card networks have rejected platforms outright over a high-risk sub-merchant mix, forfeiting the investment already made. Direct PayFacs are expected to monitor chargebacks and terminate sub-merchants exceeding roughly 1.5%, and to maintain 10-15% volume reserves as a buffer against exactly this kind of exposure.
In depth
Everything you need to know.
You register as a PayFac and establish a master merchant account, then build a sub-merchant onboarding flow that runs KYC and underwriting on every business that signs up underneath you. All transactions process through the master account, so you assume the full risk for every sub-merchant. From there, you distribute funds, charge your own fees, monitor performance, terminate risky merchants, and maintain the reserves the networks require.
A platform with 5,000 customers processing $200M can capture 0.5-1% of that as revenue — $1M-2M annually — while controlling onboarding, pricing, and the entire customer experience. That comes at a cost: $100K-500K+ in startup investment plus ongoing compliance and liability. This is why most platforms use PayFac-as-a-Service (Stripe Connect and similar) rather than becoming a direct PayFac themselves.
Illustrative example — not a specific client engagement.
- SaaS 8,000 merchants, $300M became PayFac via Stripe Connect. $1.2M annual revenue. $80K investment.
- Marketplace attempted direct. $200K investment. Networks rejected high-risk mix. Lost investment.
- Weak underwriting. 50 prohibited merchants. $150K fines, offboard all, 6-month monitoring.
- Use PayFac-as-a-Service (Stripe Connect, Adyen)
- Direct PayFac: budget $300K+ first year
- Robust underwriting: verify, check TMF, assess risk
- Monitor chargebacks - terminate exceeding 1.5%
- Maintain 10-15% volume reserves
- Don't attempt for high-risk
- Set clear standards
- Underestimating startup - $100K-500K+
- Not understanding liability - all chargebacks
- Weak underwriting - risky merchants
- Not monitoring performance
- Attempting high-risk verticals
- Not maintaining reserves
Keep exploring
Related terms
Put this to work
for your business.
MIDs structures high-risk acquiring across 30+ banks — smart routing, fraud and chargeback control built in. Tell us your category and volume and we'll build the setup around it.