How Payment Facilitator (PayFac) Works
A Payment Facilitator sits between an acquirer and the end businesses that want to accept card payments. Instead of each business negotiating its own acquiring relationship, the PayFac signs a master merchant agreement and then boards individual businesses as sub-merchants beneath it. The PayFac owns the contractual relationship with the card networks and the acquiring bank, and it takes on responsibility for everything that happens downstream.
Apply for a Master Merchant Account
The PayFac signs a direct agreement with a sponsoring acquirer and registers with Visa and Mastercard as a Payment Facilitator. This establishes the legal and financial framework under which all sub-merchants will operate.
Build Onboarding and KYC Infrastructure
The PayFac develops or licenses tools to collect business information, verify identities, screen against sanctions lists, and assess risk — all in real time. This is the engine that enables near-instant merchant approvals.
Board Sub-Merchants
Businesses apply through the PayFac's interface. The PayFac runs automated underwriting checks and, if approved, assigns the sub-merchant a unique identifier (sub-MID) under the master account. Approval typically takes minutes.
Process Transactions
When a sub-merchant's customer pays, the transaction flows through the PayFac's payment gateway and is authorized using the master merchant credentials. The card networks see the PayFac, not the individual sub-merchant.
Settle Funds and Manage Risk
The acquirer settles funds to the PayFac, which then disburses to individual sub-merchants — minus fees and any reserves held against potential chargebacks. The PayFac monitors sub-merchant activity continuously for fraud and compliance violations.
Why Payment Facilitator (PayFac) Matters
The PayFac model fundamentally changed the economics of merchant services by removing the friction of traditional acquiring. Businesses that once waited weeks for a merchant account can now accept payments the same day they sign up, which has fueled the explosion of software-led commerce platforms over the past decade.
The scale of this shift is significant. According to Nilson Report data, PayFacs and payment aggregators now process hundreds of billions of dollars in card volume annually across millions of sub-merchants globally. Stripe alone reported processing over $1 trillion in total payment volume in 2023, a figure made possible only by the PayFac aggregation model.
For software platforms, embedding payments via a PayFac model dramatically changes unit economics. Research from Andreessen Horowitz estimates that vertical SaaS companies with embedded payments generate 2–5× more revenue per customer than those offering software alone. PayFac-enabled platforms capture interchange revenue, platform fees, and financing margins that pure-software businesses cannot access.
Card Network Registration
Visa's payment facilitator program (VFAC) and Mastercard's Payment Facilitator program each have their own registration requirements, fees, and volume thresholds. A PayFac must be registered separately with each network whose cards it intends to process.
Payment Facilitator (PayFac) vs. Payment Service Provider (PSP)
The terms PayFac and payment service provider are often used interchangeably, but they have meaningful distinctions in how liability and merchant relationships are structured.
| Dimension | Payment Facilitator (PayFac) | Direct PSP / ISO |
|---|---|---|
| Merchant account ownership | PayFac holds master account; merchants are sub-merchants | Each merchant has their own merchant account |
| Onboarding speed | Minutes to hours (automated underwriting) | Days to weeks (manual underwriting by acquirer) |
| Liability for fraud/chargebacks | PayFac is liable for all sub-merchant activity | Merchant is directly liable; ISO may share risk |
| Card network visibility | Transactions appear under PayFac's MID | Transactions appear under merchant's own MID |
| Revenue model | Spread on interchange + platform fees | Commission on merchant fees (referral/agent) |
| Best for | SaaS platforms, marketplaces, high-volume onboarding | Enterprise merchants with complex acquiring needs |
Types of Payment Facilitator (PayFac)
Not all PayFac implementations look the same. The model has evolved into several distinct variants depending on the platform's goals, technical capabilities, and appetite for regulatory complexity.
Registered PayFac (Full PayFac): The platform completes full card network registration, signs directly with a sponsoring acquirer, and takes on complete liability and compliance obligations. Maximum revenue retention, maximum responsibility. Examples: Stripe, Square, Toast.
PayFac-as-a-Service (PFaaS): A software platform partners with a third-party PayFac infrastructure provider (such as Payrix, Infinicept, or Adyen for Platforms) to offer PayFac-like experiences without full registration. The provider handles compliance, risk, and acquiring relationships. Time to market is measured in months rather than years.
Marketplace / Managed PayFac: Platforms like marketplaces or gig-economy applications board a large number of sellers or service providers as sub-merchants. Card network rules (particularly Mastercard's marketplace program rules) have specific provisions for these use cases, including split-settlement and payout timing requirements.
Hybrid Model: Some platforms start as referral ISOs, then migrate to PFaaS, then ultimately become registered PayFacs as volume grows and economics justify the investment. This staged approach allows incremental risk and compliance build-out.
Best Practices
Adopting the PayFac model — whether as a full registrant or via a PFaaS partner — requires discipline across both business operations and technical implementation.
For Merchants (Sub-Merchants)
Understand what you are agreeing to when you sign up with a PayFac. You are a sub-merchant, not a direct customer of the bank. This means the PayFac can hold funds, terminate your account, or apply rolling reserves based on their own risk policies — often with limited notice. Read the acceptable use policy carefully, especially around prohibited industries and chargeback thresholds. Maintain a backup payment processing relationship if your business depends on uninterrupted payment acceptance.
For Developers and Platforms
Design your sub-merchant onboarding flow to collect KYC data at the point of signup, not as an afterthought. Lazy KYC — collecting minimal data upfront and enriching later — creates compliance gaps that regulators and card networks will scrutinize. Build transaction monitoring into your platform from day one: track velocity, average ticket size, and refund rates per sub-merchant. Use webhooks and real-time alerts to catch anomalies before they become chargebacks. When integrating with a PFaaS provider, abstract the provider behind your own API layer so you can switch vendors without rebuilding your product.
Common Mistakes
1. Underestimating compliance scope. Many platforms assume that using a PFaaS provider transfers all compliance obligations. In practice, the platform still owns KYC data collection, acceptable use policy enforcement, and often first-line fraud monitoring. Misunderstanding this split leads to regulatory exposure.
2. Inadequate reserve management. PayFacs are required to maintain reserves against potential sub-merchant chargebacks and fraud losses. Platforms that set reserves too low or release them too early face unexpected financial liability when a sub-merchant goes out of business or is terminated for fraud.
3. Ignoring card network rule updates. Visa and Mastercard update their PayFac program rules regularly. Platforms that do not have a process for tracking and implementing these updates risk non-compliance and potential de-registration.
4. Poor sub-merchant communication during holds or terminations. When a PayFac places a hold on funds or terminates a sub-merchant, the lack of clear communication is the most common source of reputational damage and legal disputes. Build transparent communication workflows into your risk operations.
5. Scaling before compliance infrastructure is ready. Fast-growing platforms sometimes onboard thousands of sub-merchants before their KYC, monitoring, and dispute management systems are mature enough to handle the volume. This creates a compliance backlog that can attract regulatory scrutiny and card network audits.
Payment Facilitator (PayFac) and Tagada
Payment orchestration platforms like Tagada work closely with the PayFac layer of the payment stack. Tagada sits above the PayFac or acquirer and provides routing logic, redundancy, and unified reporting across multiple payment providers — including PayFacs operating in different geographies or currencies.
Orchestration + PayFac
If your platform already operates as a PayFac or uses a PFaaS provider, Tagada can layer on top to add intelligent routing (e.g., sending transactions to the lowest-cost processor by card BIN), automatic failover when a processor is down, and consolidated analytics across all your payment flows — without disrupting your existing sub-merchant relationships.
For platforms exploring the PayFac model, Tagada's orchestration layer makes it easier to migrate from a single-processor setup to a multi-acquirer architecture as transaction volume grows — a natural next step after initial PayFac launch.