Payment facilitator (PayFac)
Also known as: PayFac, payment facilitation, sub-merchant model, PayFac-as-a-service
A payment facilitator (PayFac) is a company that lets businesses start accepting card payments almost instantly by onboarding them as 'sub-merchants' under the PayFac's own master merchant account.
While it looks like a simple sign-up form, the PayFac is taking on the underwriting, monitoring, and first-loss risk that an acquiring bank would otherwise carry. That's why accounts sometimes get frozen without warning.
Payment facilitator (PayFac), explained at three levels
At home
If you've ever bought crafts from a market vendor who took your card on a phone reader, that vendor likely used a payment facilitator like Square. Instead of each vendor getting their own bank approval, the PayFac sets them up in minutes under its own account.
At work
For a small business, a PayFac is the fastest way to accept cards. You sign up online, get approved quickly, and pay a simple flat rate. The trade-off is less negotiating power and the risk that your account could be paused if your activity looks unusual.
At home
A PayFac flips the usual order of checks. A traditional acquirer reviews a business before approving it. A PayFac approves sellers in minutes with basic identity checks, then watches their activity closely afterward. Its risk systems compare each seller's sales against what's normal for that type of business. A sudden spike in sales, lots of refunds, or orders for goods you'll ship months later can trigger a review or a hold on your payouts while the PayFac checks things out.
At work
A PayFac holds a master merchant account with a sponsoring acquirer and registers with the card networks. It onboards sub-merchants under that account, runs know your customer checks, sets pricing, and usually controls settlement, receiving funds first and paying each sub-merchant. Software platforms that become PayFacs earn a share of processing fees but take on compliance, chargeback liability, and fraud monitoring. 'PayFac-as-a-service' providers offer a middle path, handling the regulated work while the platform keeps the customer relationship.
At home
The PayFac is liable to its acquirer if a sub-merchant runs up chargebacks and disappears, so it manages that risk after onboarding rather than before. It scores each seller continuously and uses rolling reserves, payout delays, and volume caps tuned to each one. While instant onboarding opened card acceptance to millions of tiny businesses, in my opinion the frozen-account horror stories are its visible cost. Underwriting after approval is cheaper than before, but it's far more jarring when it happens.
At work
Becoming a full PayFac means network registration, sponsor-bank approval, a PCI DSS Level 1 environment if you touch card data, funds flow and reconciliation systems, and an underwriting team. Card networks also cap sub-merchant volume before a business must get its own merchant agreement. For most software companies, the economics favour a managed PayFac partnership until payment volume is large enough to justify the operational burden.
Real-world examples
At home
Nadia started selling handmade candles at weekend markets. She downloaded a card-reader app, verified her identity, and took her first card payment the same afternoon. When she later ran a big holiday pre-order, the provider briefly held her payouts until the orders shipped.
At work
Jerome is CFO at a scheduling software company for physiotherapy clinics. The company became a payment facilitator through a PayFac-as-a-service partner, letting clinics take payments inside the software. Payments revenue grew to a significant share of the company's total within two years.
How it compares
| feature | Payment facilitator (PayFac) | Direct merchant account |
|---|---|---|
| Onboarding time | Minutes to a day | Days to weeks |
| Who underwrites | The PayFac, mostly after sign-up | The acquirer, before approval |
| Pricing | Usually flat rate | Often negotiable, interchange-plus |
| Account holds | More common | Less common once approved |
| Best for | Small or new businesses | Larger, established businesses |
A PayFac trades lower setup friction for higher fees and more monitoring after sign-up.
For analysts
For software companies, becoming a PayFac is one of the most reliable ways to add revenue, but I'd model the risk and operations costs honestly. The fee share looks great until the first large chargeback loss lands on your balance sheet.
History & origin
Before PayFacs, a small business needed its own merchant account from an acquirer, which meant applications, credit checks, and weeks of waiting. Card networks created the payment facilitator category around 2012, formalizing a model that PayPal had used for years and that Square (launched in 2010) and Stripe (2011) used to reach millions of tiny businesses. The networks set rules on sub-merchant volume limits, registration, and monitoring. Software companies later became PayFacs themselves to earn payments revenue inside their platforms. In my view, the PayFac model did more to democratize card acceptance than any technology change. It was a risk-allocation innovation, not a technical one.