A payment facilitator, usually shortened to PayFac or PF, is a company that holds one master merchant account with an acquiring bank and lets many smaller businesses process card payments underneath it as sub-merchants. Instead of each seller applying to a bank for their own account, they onboard through the PayFac, which owns the underwriting, compliance, and money movement.
For a marketplace operator, the PayFac question usually shows up the moment you start collecting payments and paying out sellers. Do you become a registered payment facilitator yourself, or do you sit on top of a provider like Stripe Connect that already handles the hard parts? The answer changes your timeline, your costs, and your regulatory exposure by a wide margin.
This guide explains what a payment facilitator actually is, how the model works mechanically, how it differs from a marketplace, a payment aggregator, and an ISO, and when registering as a PayFac is worth it versus using a managed solution.
What is a payment facilitator (PayFac)?
A payment facilitator is a registered entity that contracts with an acquiring bank to onboard and process payments for sub-merchants under its own master merchant account. The PayFac underwrites each sub-merchant, manages PCI compliance and KYC, settles funds, and takes on the financial liability that an acquiring bank would normally place on the merchant directly. Stripe, Square, and Shopify Payments all operate as payment facilitators.
The card networks, primarily Visa and Mastercard, created the PayFac designation to let one approved party sign up businesses quickly without each one going through full bank underwriting. That speed is the point: a sub-merchant can often start accepting payments in minutes rather than the days or weeks a traditional merchant account takes. In exchange, the facilitator absorbs real obligations and is responsible for the activity of every sub-merchant on its master account, including fraud, chargebacks, and regulatory violations.
How does the payment facilitator model work?
The PayFac model works by nesting many sub-merchants inside one master merchant account, with the facilitator acting as the layer between those sellers and the acquiring bank. The facilitator boards each sub-merchant, screens them, processes their transactions, and distributes settled funds. The bank sees one relationship; the sub-merchants see a fast, simple onboarding flow and never deal with the bank directly.
Here is the flow in order:
- The PayFac registers with an acquiring bank and the card networks, and opens a master merchant account.
- A sub-merchant applies through the PayFac’s onboarding flow, submitting business and identity details.
- The PayFac underwrites the applicant, running KYC and risk checks against card network and regulatory rules.
- The sub-merchant goes live under the master account, identified by its own sub-merchant ID.
- Transactions are processed through the PayFac’s infrastructure and routed to the acquiring bank.
- Funds are settled to the PayFac, which then distributes payouts to each sub-merchant, often net of fees.
What is a master merchant account?
A master merchant account is the single account a payment facilitator holds with its acquiring bank, under which all of its sub-merchants transact. The facilitator owns this account and the liability attached to it, while sub-merchants operate as identified nodes beneath it rather than as direct account holders. This structure is what lets a PayFac onboard new sellers in minutes instead of weeks.
The card networks still require visibility into the businesses transacting under the master account. Once a sub-merchant crosses certain processing volume thresholds set by Visa and Mastercard, the facilitator must register that sub-merchant with the networks and report it. Below those thresholds, the sub-merchant can transact under the master account with lighter formal registration.
How does underwriting work for sub-merchants?
The payment facilitator underwrites every sub-merchant itself, taking over the risk assessment a bank would normally perform on a standalone merchant. The PayFac verifies the business, checks the owners against sanctions and watchlists, assesses the risk of the business model, and decides whether to board the applicant. If a sub-merchant generates fraud or unpaid chargebacks, the facilitator is on the hook financially.
This is the heaviest responsibility in the model. Underwriting is not a one-time check; the facilitator monitors transaction patterns continuously, watches for volume spikes or chargeback ratios that breach card network limits, and can suspend a sub-merchant. For a marketplace, this is where understanding your sellers matters. Tracking supply quality and transaction behavior is part of how you keep risk in check, which is exactly the kind of monitoring Twosided is built to make visible.
PayFac vs marketplace vs payment aggregator vs ISO
These four models all sit between sellers and the banking system, but they differ in who holds the merchant account, who carries liability, and who controls the money flow. A marketplace and a PayFac are often conflated, but a marketplace is a business model while a payment facilitator is a payments role; a marketplace can use a PayFac, become one, or neither. An ISO sells accounts but never holds funds, and “aggregator” is the older name for what is now formalized as a PayFac.
| Model | Holds merchant account? | Underwrites sellers? | Touches the funds? | Carries liability? |
|---|---|---|---|---|
| Payment facilitator (PayFac) | Yes — one master account | Yes | Yes — settles and pays out | Yes — fully |
| Marketplace | Depends on setup | Only if also a PayFac | Often, via a provider | Depends on structure |
| Payment aggregator | Yes — aggregates sub-merchants | Yes | Yes | Yes |
| ISO (Independent Sales Org) | No — refers merchants to a bank | No | No | No (reseller only) |
A few distinctions worth being precise about:
- Payment aggregator vs PayFac: these describe the same structure of pooling sub-merchants under one account. “Aggregator” is the term the card networks used before “payment facilitator” became the formal designation. Treat them as the same model, with PayFac being the current standard term.
- ISO vs PayFac: an Independent Sales Organization resells merchant accounts on behalf of an acquirer. It refers and supports merchants but does not hold the account, move money, or carry liability. A PayFac does all three.
- Marketplace vs PayFac: a marketplace is defined by connecting buyers and sellers, not by how it processes payments. Most marketplaces are not registered PayFacs; they use a provider that handles facilitation, which keeps liability and compliance off their plate. The two-sided marketplace guide covers the business model itself.
When should a marketplace become a registered PayFac?
A marketplace should consider registering as a payment facilitator only when its payment volume is large enough that owning the economics and the onboarding experience outweighs the cost and risk of running compliance in-house. For most early and scaling marketplaces, the answer is no — a managed solution like Stripe Connect captures the speed of the PayFac model without the registration, underwriting, and liability burden.
Registering as a PayFac means you take on the full stack: a banking relationship, PCI DSS Level 1 compliance, a KYC and underwriting program, fraud and chargeback liability, ongoing card network reporting, and the engineering to run settlement and payouts. That is a serious operating commitment, not a feature flag.
Becoming a registered PayFac tends to make sense when several of these are true:
- High and predictable volume — you process enough that even small per-transaction savings add up to meaningful margin.
- Onboarding is your product — sub-second seller activation is a competitive edge worth controlling end to end.
- You want the take-rate economics — owning facilitation lets you capture spread you would otherwise pay to a provider. The marketplace take-rate is central to whether this math works.
- You have compliance capacity — a team or partner who can run KYC, monitoring, and reporting reliably.
If most of those are not true yet, you are better served by Stripe Connect or another managed platform. It is also worth surveying the field of Stripe Connect alternatives before committing, because the right managed provider often delays or removes the need to register at all.
What does a payment facilitator cost?
Running as a registered payment facilitator carries both upfront and ongoing costs that are far higher than the per-transaction fee most operators focus on. You pay for registration and sponsorship, compliance audits, underwriting tooling, fraud monitoring, and the engineering to maintain it all. A managed provider folds these into a single processing rate instead, which is why it is cheaper until you reach real scale.
The cost layers of being a PayFac include:
- Card network registration and bank sponsorship fees, paid to get and keep your facilitator status.
- PCI DSS Level 1 compliance, the highest tier, which requires an annual audit by a Qualified Security Assessor.
- Underwriting and KYC systems, whether built or licensed, plus the staff to run them.
- Fraud and chargeback losses, which you absorb directly because you carry liability.
- Settlement and payout engineering, including the work to handle payment splitting across sellers and your platform fee.
By contrast, a managed provider’s pricing is mostly the processing rate plus platform fees. According to Stripe’s published US pricing, standard online card payments run 2.9% + $0.30 per successful charge, with marketplace platform features priced on top. You trade some margin for the provider carrying the compliance and liability you would otherwise fund yourself.
What are the PCI-DSS and KYC obligations?
A payment facilitator must meet PCI DSS Level 1, the strictest compliance tier, and run a full KYC and underwriting program for every sub-merchant it boards. PCI DSS governs how card data is stored, processed, and transmitted, and Level 1 applies to the highest-volume processors with an annual on-site or independent audit. KYC obligations require verifying each sub-merchant’s identity and screening against sanctions and fraud lists.
PCI DSS, the Payment Card Industry Data Security Standard, is maintained by the PCI Security Standards Council. Level 1 is the most demanding of its merchant levels and requires a yearly assessment by a Qualified Security Assessor rather than a self-assessment questionnaire. As a PayFac, you are responsible for your own compliance and for ensuring sub-merchants meet their requirements.
KYC, Know Your Customer, sits alongside this. You must collect and verify identifying information on each sub-merchant and their beneficial owners, screen them, and keep monitoring for suspicious activity. Get this wrong and you face card network fines, frozen funds, or loss of facilitator status. With a managed provider, most of this obligation shifts to them, which is the single biggest reason marketplaces avoid registering until they have to.
What are PayFac-as-a-service and managed options?
PayFac-as-a-service and managed payment platforms let a marketplace get most of the PayFac model’s benefits without registering as a facilitator itself. These providers hold the master merchant account, handle underwriting, compliance, and payouts, and expose APIs so sellers onboard fast and money splits automatically. You stay focused on the marketplace while the provider carries the regulated layer.
The real categories worth knowing are:
- Managed marketplace payment platforms — Stripe Connect is the most widely used. It onboards sellers, splits payments, and handles payouts and much of the compliance on your behalf. See the Stripe Connect pricing breakdown for what that costs in practice.
- Marketplace software with payments built in — platforms like Sharetribe bundle the marketplace and the payment flow together so you do not integrate facilitation from scratch.
- PayFac-as-a-service / managed PayFac — providers such as Stripe, Adyen, and Finix offer programs that let a company adopt a facilitator model with the provider handling sponsorship, compliance tooling, and risk infrastructure. This sits between fully managed and fully registered, giving more control than Stripe Connect without you registering directly with the card networks.
Money mechanics matter regardless of which route you pick. Understanding how funds move, including escrow payments for held transactions and what a payout actually involves, helps you choose the model that fits your marketplace and cash-flow needs.
Whichever path you take, your job as an operator is to watch the numbers underneath it: seller volume, chargeback ratios, take rate, and supply health. Get started with Twosided for free to connect Stripe Connect or Sharetribe in about five minutes and get plain-English answers about your GMV, payouts, and marketplace risk, without becoming a payments expert first.
FAQs
What is the difference between a payment facilitator and a payment aggregator?
A payment facilitator and a payment aggregator describe the same model: pooling many sub-merchants under one master merchant account. “Aggregator” was the original term used by the card networks, while “payment facilitator” or PayFac is the formal, registered designation used today. In practice the two terms are interchangeable, with PayFac being the current standard.
Is Stripe a payment facilitator?
Yes, Stripe operates as a payment facilitator. It holds master merchant accounts with acquiring banks and lets businesses process payments as sub-merchants under it, handling underwriting, compliance, and payouts. Stripe Connect extends this to marketplaces, letting a platform onboard sellers and split payments without registering as a PayFac itself, since Stripe carries that role.
Does my marketplace need to become a registered PayFac?
Most marketplaces do not need to register as a payment facilitator. A managed provider like Stripe Connect delivers fast seller onboarding and automatic payment splitting while carrying the compliance and liability. Registering as a PayFac usually only makes sense at high, predictable volume where owning the economics and onboarding outweighs the cost of running underwriting and PCI compliance in-house.
What is a sub-merchant?
A sub-merchant is a business that processes card payments under a payment facilitator’s master merchant account rather than holding its own account with a bank. The PayFac underwrites and onboards each sub-merchant, gives it a sub-merchant ID, and distributes its settled funds. This structure lets sellers start accepting payments quickly, often within minutes, instead of waiting for bank approval.
What compliance does a payment facilitator need?
A payment facilitator must meet PCI DSS Level 1, the strictest data security tier, with an annual audit by a Qualified Security Assessor. It must also run KYC, verifying the identity of every sub-merchant and screening for sanctions and fraud, plus ongoing transaction monitoring. Failure can mean card network fines, frozen funds, or loss of facilitator status.
What is the difference between a PayFac and an ISO?
A PayFac holds a master merchant account, underwrites sub-merchants, moves money, and carries liability. An ISO, or Independent Sales Organization, only refers and supports merchants on behalf of an acquiring bank. The ISO never holds the merchant account, never touches the funds, and carries no financial liability. A PayFac is an active processor; an ISO is essentially a reseller.