What a Payment Facilitator Does and How It Differs from a Merchant Processor
A payment facilitator (PayFac) lets you accept payments on behalf of other merchants instead of processing them yourself
A payment facilitator is a company that sits between customers, merchants, and the bank. Instead of each small business signing its own merchant account with a bank or processor, the PayFac holds one master account and brings merchants under it. The PayFac handles the underwriting, compliance, funding, and dispute resolution for all those sub-merchants. You see this model most often with point-of-sale systems, invoicing platforms, and marketplaces that want to let their users accept payments without leaving the platform.
The key difference from a traditional merchant processor: a processor connects you directly to the bank and card networks. A PayFac connects you to the bank, then connects other merchants to you. The PayFac takes on the liability and regulatory responsibility for those sub-merchants. That's why PayFacs are useful for platforms—they can onboard merchants in minutes instead of days, because the PayFac has already done the heavy compliance lifting.
If you're a small business owner, you probably won't become a PayFac yourself. But you might use one without realizing it. If you sell through Shopify, Square, or a niche invoicing tool, and payments flow through that platform's system, you're likely using a PayFac model. The platform is the PayFac; you're the sub-merchant.
Key Takeaways
- A PayFac holds one master merchant account and brings other merchants under it, rather than each merchant holding their own account with a bank.
- PayFacs handle underwriting, compliance, and disputes for all their sub-merchants, which is why onboarding is faster than traditional merchant accounts.
- PayFacs are regulated by the card networks and must maintain reserve funds and insurance to cover chargebacks and fraud losses from their sub-merchants.
- Most small business owners use PayFacs indirectly through platforms like Shopify or Square, not by becoming a PayFac themselves.
- The cost to become a PayFac is high—you need banking relationships, compliance infrastructure, and technology—so it's only practical for large platforms.
How a PayFac differs from a traditional merchant processor
A traditional merchant processor is a middleman between you and the bank. You sign a merchant agreement with the processor, the processor connects you to the card networks and the acquiring bank, and payments flow through that chain. The bank holds your merchant account. The processor handles the technical side—routing transactions, settling funds, reporting—but the bank is ultimately responsible for your account and can shut it down if you breach the agreement.
A PayFac is a different legal structure. The PayFac holds the merchant account with the bank. When you become a sub-merchant under a PayFac, you don't have a direct relationship with the bank. The PayFac is liable for your transactions, your chargebacks, and your compliance. That liability is why PayFacs can onboard merchants faster—they've already vetted themselves heavily, so they can make faster decisions about sub-merchants. It's also why PayFacs charge higher fees: they're taking on more risk.
From a customer's perspective, the difference is invisible. A payment processed through a PayFac looks the same on a credit card statement as one processed through a traditional processor. The difference matters to the business owner because it affects how fast you can start accepting payments, what fees you pay, and what happens if there's a dispute or chargeback.
Why platforms use the PayFac model
Platforms use PayFacs because they solve a specific problem: how to let users accept payments without forcing each user to open a merchant account. Imagine you run an invoicing platform and want to let your customers accept payments directly through your software. If each customer had to open their own merchant account, onboarding would take days and many would give up. With a PayFac model, you can onboard a new merchant in minutes because the compliance and banking relationship is already done.
PayFacs also let platforms control the payment experience. Square, for example, is a PayFac. When you use Square, you're not signing a merchant agreement with a bank—you're using Square's master account. Square decides the fees, the settlement timing, the dispute process. That control is valuable for platforms because it lets them offer a consistent experience and bundle payments with other services.
The trade-off is cost and complexity. Becoming a PayFac requires a banking relationship, compliance infrastructure, fraud monitoring, and reserve funds to cover losses. That's why only large platforms do it. A small business can't afford to become a PayFac; it would cost hundreds of thousands of dollars to set up and maintain.
The regulatory and financial responsibility of a PayFac
A PayFac is regulated by Visa, Mastercard, and the acquiring bank. The PayFac must maintain certain standards: it has to monitor its sub-merchants for fraud and money laundering, it has to hold reserve funds to cover chargebacks and losses, and it has to report to the card networks regularly. If a sub-merchant commits fraud or processes illegal transactions, the PayFac is on the hook financially.
This is why PayFacs are selective about who they bring on. A traditional processor might accept almost any merchant because the bank is ultimately liable. A PayFac has to be more careful because it's taking the loss. Many PayFacs use automated underwriting to screen merchants quickly, but they're still checking for red flags: high chargeback rates, high-risk industries, or signs of fraud.
PayFacs also have to maintain reserve funds—money set aside to cover chargebacks, refunds, and fraud losses. The amount depends on the PayFac's risk profile and the card networks' requirements. This reserve is one reason PayFacs charge higher fees than traditional processors. They're not just processing payments; they're holding capital to cover losses.
When you might encounter a PayFac as a business owner
If you use Shopify, Square, Toast, Stripe, or similar platforms to accept payments, you're using a PayFac. These companies hold the merchant account and you're a sub-merchant under them. You don't see this in the contract language most of the time—the platforms just say you can accept payments through them—but legally, that's what's happening.
The advantage to you is simplicity. You don't have to apply for a merchant account, you don't have to negotiate with a bank, and you can start accepting payments in minutes. The disadvantage is that you have less control. You can't negotiate fees directly with the card networks, and if the PayFac decides to shut down your account, you lose access to payments immediately. You also can't easily switch to another processor without changing platforms.
Some industries—high-risk businesses like CBD retailers, online gambling, or travel agencies—may find it harder to get accepted by a PayFac because the PayFac is taking on more liability. In those cases, a traditional merchant processor might be easier to work with, though fees will be higher.
The cost of becoming a PayFac versus using one
If you're a small business, you will never become a PayFac. The cost is prohibitive. You need a banking relationship with an acquiring bank willing to hold your master merchant account—most banks require millions in revenue or a venture capital backing to consider it. You need compliance infrastructure: fraud monitoring, KYC (know-your-customer) processes, chargeback management, and reporting systems. You need reserve funds, insurance, and legal counsel. The total cost to launch a PayFac is typically in the hundreds of thousands of dollars, and ongoing compliance costs are substantial.
Using a PayFac, on the other hand, costs you a percentage of each transaction—typically 2.9% plus $0.30 per transaction for card payments, though this varies widely. You might also pay monthly fees for additional features. These fees are higher than what a large business with its own merchant account would pay, but lower than what you'd pay if you tried to get a merchant account on your own as a small business.
The trade-off is worth it for most small businesses because the alternative—getting your own merchant account—is slow, expensive, and requires a lot of paperwork. A PayFac lets you start accepting payments immediately and scale without renegotiating with a bank.
Frequently Asked Questions
Is my money safe with a PayFac?
Yes, in the sense that the PayFac is regulated and required to hold reserve funds. Your transactions are processed through the card networks, so chargebacks and disputes are handled the same way as with any processor. However, if the PayFac goes out of business, there can be delays in accessing your funds. Most PayFacs carry insurance and maintain reserves specifically to prevent this.
Can I switch from a PayFac to a traditional processor?
Yes, but it depends on the platform. If you're using Shopify or Square, you're locked into their payment system—you can't easily switch to a different processor without leaving the platform. If you're using a standalone PayFac, you can usually migrate to a traditional processor, though you'll need to set up a new merchant account and update your payment settings.
Why do PayFacs charge higher fees than traditional processors?
PayFacs take on more liability and regulatory responsibility than traditional processors. They hold the merchant account, manage chargebacks, and cover fraud losses. They also have to maintain reserve funds and compliance infrastructure. Those costs are built into the fees you pay.
What happens if my PayFac shuts down my account?
You lose the ability to accept payments through that platform immediately. Your funds should be settled within a few days, but you'll need to set up a new payment processor to keep accepting payments. This is why it's important to understand the terms of service and keep your account in good standing.
Do I need to do anything different if I'm using a PayFac instead of a traditional processor?
No. From your perspective, accepting payments works the same way. The difference is behind the scenes—how the money flows and who's liable for disputes. You don't need to change your operations or your accounting.