What is a Payment Facilitator (PayFac)?

This model has influenced how payments work across industries, powering platforms like Shopify, Toast, and Mindbody - it's also created new responsibilities and risks for the businesses that take it on. This post breaks down what a PayFac is, how it works, and what it means for the businesses thinking about this path.

How a Payment Facilitator Actually Works

At the center of the PayFac model is something called a master merchant account. The PayFac holds this account with an acquirer bank, and every business that signs up under them - called a sub-merchant - processes payments through it. Instead of each business needing its own direct relationship with a bank, they all sit underneath the PayFac's umbrella.

This structure is what makes onboarding so fast. A traditional setup means a business has to apply for its own merchant account, go through underwriting, and wait. With a PayFac, that vetting happens at a lighter level and gets handled by the PayFac itself, so a new sub-merchant can start accepting payments in minutes instead of days or weeks.

There are a few key players that make this whole thing run.

• The PayFac - holds the master merchant account and takes on responsibility for its sub-merchants
• The sub-merchant - the business signing up to accept payments through the PayFac
• The acquirer - the bank that sponsors the master merchant account and settles funds
• The card networks - Visa, Mastercard, and others that set the rules for how transactions move

When a customer pays, the transaction flows up through the sub-merchant to the PayFac's master account. The acquirer then settles the funds, and the PayFac distributes the money to the sub-merchant after taking its fee. The card networks sit above this and govern how every transaction has to be handled.

The PayFac also takes on responsibility here - it handles compliance, monitors for fraud, and is accountable to the acquirer for everything its sub-merchants do. That is a real trade-off - it gives sub-merchants a much easier path to get started, but it means the PayFac carries the risk for the businesses it has on.

PayFac vs. Traditional Merchant Accounts: Key Differences

With a traditional merchant account, a business applies directly to a bank or acquirer and goes through a full underwriting process - it will take days or weeks - and the business gets its own dedicated account with its own pricing structure. A PayFac skips most of that by putting you under its existing master account instead.

Here is a comparison of the two models.

Factor	PayFac Model	Traditional Merchant Account
Setup time	Minutes to hours	Days to weeks
Underwriting	Light, automated checks	Full manual review
Fees	Flat rate per transaction	Interchange-plus or negotiated rates
Risk responsibility	PayFac holds it	Shared with the merchant
Control	Limited for sub-merchants	Greater autonomy

The speed of a PayFac setup is a benefit for smaller businesses or those that need to get moving fast. But that convenience comes with trade-offs worth thinking about.

Because you are a sub-merchant under a PayFac, you have less say over your account terms. The PayFac can put holds on your funds or terminate your account if your transaction activity looks unusual to them. You don't have a direct relationship with the bank, so there's less room to negotiate.

A traditional merchant account gives you more control and can work out cheaper at higher transaction volumes. The flat-rate pricing of a PayFac is easy to understand. But it does not scale as favorably once your revenue grows.

The right fit can depend on where your business is and how much friction you can tolerate in the setup process. Businesses with higher risk profiles may also want to explore what a high-risk payment processor can offer compared to a standard PayFac arrangement.

Who Carries the Risk (and Why It Matters)

When a sub-merchant processes a payment through a PayFac, the PayFac is the one legally on the hook with the acquiring bank. That means if a sub-merchant causes a chargeback, gets hit with fraud, or violates card network rules, the PayFac absorbs that financial and legal exposure - not the sub-merchant.

This is why PayFacs run KYC (Know Your Customer) checks before approving new sub-merchants. They need to verify who they're bringing onto the platform because a bad actor under their umbrella can become their problem - it's not bureaucracy for the sake of it - it's self-protection.

Chargebacks are one of the biggest pressure points. A chargeback happens when a customer disputes a charge and the funds get pulled back from the merchant. If that sub-merchant can't cover it, the PayFac eats the loss. Scale that across thousands of sub-merchants and the exposure can become something PayFacs have to manage very actively - which is why understanding your chargeback-to-transaction ratio matters so much.

That exposure is why PayFacs set transaction limits and sometimes place holds on funds. A brand-new sub-merchant processing an unusually large transaction volume is a warning sign that something could be off. Freezing or terminating an account is a financial safety measure - not a punitive one. Some PayFacs also use a rolling reserve to protect themselves against potential losses from their sub-merchant portfolio.

Compliance is another layer of this. PayFacs have to make sure their sub-merchants meet card network standards and don't operate in restricted industries. If a sub-merchant crosses into territory that violates those rules, the PayFac faces consequences from the networks.

So when a PayFac seems strict about onboarding or quick to flag an account, that behavior makes sense in this context. The scrutiny is not arbitrary gatekeeping - it reflects the responsibility they've taken on by sitting between the acquiring bank and every business on their platform, managing a portfolio of risk they've personally underwritten. Businesses that get cut off may need to look at what happens when Stripe or a similar platform closes your processing to understand their next steps.

The Business Case for Becoming a PayFac

The short answer is revenue and retention. When a platform controls the payment experience, it earns a cut of every transaction its users process. That piles up fast across thousands of sub-merchants.

There's also a strong argument from the user experience side. Merchants want to manage their business in one place, and the data supports this. Around 87% of U.S. merchants choose their payment provider at the same time they choose their business software. That means if your platform doesn't manage payments natively, you're giving a competitor a reason to win over your customers.

The global PayFac market reached $15.2 billion in 2024 and it's expected to hit $54.8 billion by 2033. That growth reflects how software platforms have decided that embedding payments is worth the effort.

Not every type of business is a natural fit for this model. But a few categories come up again and again.

Platforms and marketplaces use the PayFac model to move money between buyers and sellers without routing everyone through a separate payment provider. Vertical SaaS businesses - think software built for salons, gyms, or dental practices - embed payments because their users want everything in one tool. E-commerce platforms take a similar approach to merchants on their ecosystem instead of sending them elsewhere to set up processing.

The core appeal is that payments become a feature of the product instead of an afterthought. Users get a smoother experience, and the platform gets a new revenue stream that scales directly with its user base.

Becoming a PayFac isn't the only path. Some platforms use a model called PayFac-as-a-Service, which gives them many of the same benefits without taking on full registration - but that's a distinction worth its own explanation. Platforms carrying payment volume should also understand tools like a chargeback management platform to handle the dispute risk that comes with processing at scale.

The Setup, Costs, and Compliance Involved

To become a PayFac, you first need to register with the card networks - Visa and Mastercard - and get sponsored by a bank. That bank takes on liability for your sub-merchants, so they will want to see that your business is financially stable and that you have strong risk controls in place.

The cost to build a full PayFac stack from scratch can run into the hundreds of thousands of dollars. You need underwriting systems, onboarding flows, fraud monitoring, and settlement infrastructure, and that's before you factor in standard maintenance and staffing.

Compliance is a permanent part of the job. As a PayFac, you are responsible for PCI DSS compliance across your platform and your sub-merchants. You also take on KYC and AML obligations, which means you'll have to verify who you're onboarding and flag anything suspicious.

For businesses that don't want to build this themselves, PayFac-as-a-service providers like Stripe, Adyen, or Payrix let you get the sub-merchant experience without the full infrastructure burden. You give up some control and revenue share. But the time-to-launch is much shorter.

Factor	Build Your Own	Use a Platform
Setup Cost	$200K-$500K+	Low to none
Time to Launch	12-24 months	Weeks to months
Complexity	High	Moderate
Revenue Control	Full	Shared
Compliance Burden	On you entirely	Partly shared

For smaller businesses, building from scratch doesn't make financial sense. The volume of transactions has to be large enough to justify the investment, and reaching that scale takes time.

So, Is a PayFac the Right Move for You?

Before moving forward, it's worth being honest about where your business actually stands. To justify the infrastructure, you need the transaction volume, the technical team to build it, and the risk tolerance to own chargebacks and sub-merchant liability. If any of these are uncertain, PayFac-as-a-service is worth a look - it lets you capture some of the benefits without taking on the full regulatory and operational burden yourself.

In either case, the next step is the same - move from a general to a clear-eyed assessment of your situation, and let that drive the choice.