What Is a Payment Facilitator (PayFac)? Full Guide

A payment facilitator, or PayFac, is a company that lets businesses accept card and other electronic payments as sub-merchants under its own master merchant account. Instead of each business applying for its own merchant account with a bank, the PayFac onboards them directly, often in minutes, and handles much of the setup, risk and compliance work.

If you run a software platform or marketplace, you’ve probably met this model already. When a yoga studio signs up for booking software and starts taking card payments the same afternoon, a payment facilitator is almost always behind it.

We work on the infrastructure side of this at ConnectPay, providing card acquiring and merchant services to businesses and platforms. In this guide, we explain how the PayFac model works, how it differs from an ISO, a processor and a PSP, which companies use it, and whether your platform should become a PayFac, partner with one, or do something in between.

What Is a Payment Facilitator (PayFac)?

If you’re asking what is a payment facilitator, the short answer is this: it’s a business that sits between merchants and the acquiring bank and turns many small merchants into sub-merchants under one master account.

Here’s what that means in practice. An acquiring bank, or acquirer, is the financial institution that processes card payments for merchants and settles the money to them. Traditionally, every business that wanted to accept cards needed its own merchant account with an acquirer, identified by its own merchant ID (MID). A PayFac changes that. It holds a single master merchant account and then boards its customers as sub-merchants beneath it.

So what is a PayFac responsible for? Quite a lot. It’s the merchant of record in the relationship with the acquirer. It underwrites each sub-merchant, deciding who gets approved and on what terms. And it takes on the financial risk. If a sub-merchant runs up chargebacks or fraud losses it can’t cover, the PayFac is on the hook.

For the businesses it serves, the benefit is simple: they don’t need to set up a traditional merchant account at all. The best-known examples are Stripe, Square, PayPal and Adyen for Platforms. We look at each of them in more detail later in this guide.

How Payment Facilitators Work

Let’s follow one sub-merchant through a payment facilitator platform, from sign-up to payout.

A small bakery signs up for an online ordering tool. During sign-up, it enters its business name, registration number, owner details, bank account, website and expected sales volume. In the background, the PayFac runs automated KYC (know your customer) and AML (anti-money laundering) checks. It verifies the company and its owners, screens them against sanctions lists, and assesses risk using data points such as business type, expected volume, average transaction size and refund history where available. Low-risk merchants are often approved within hours, sometimes instantly. Higher-risk cases go to manual review. For a sense of what thorough business checks involve, our guide to KYC requirements for corporates covers the detail.

Once approved, the bakery starts taking payments. Transactions flow through the PayFac’s master account to the acquirer and the card networks. The PayFac then settles the funds to the bakery, minus its fees, on a set schedule.

When something goes wrong, the PayFac handles it centrally. Chargebacks, disputes and fraud monitoring all run through one team and one system rather than through hundreds of separate bank relationships.

There’s also a step most guides skip. Visa and Mastercard both require payment facilitators to register with them through a sponsoring acquirer. That involves registration fees, compliance obligations and ongoing reporting. Once a sub-merchant grows past certain volume thresholds, the networks generally expect it to move to a direct merchant agreement with the acquirer.

Ready to upgrade your payment infrastructure?

Stop struggling with fragmented payment flows. Access dedicated IBANs, SEPA Instant, and seamless API integrations – all from a single, unified platform.

Contact Sales Explore Our Products

Payment Facilitator vs. ISO

The payment facilitator vs ISO question comes up constantly, partly because both models help merchants accept cards and both earn money from it. They work very differently, though.

An ISO (independent sales organization) is essentially a reseller. It finds merchants and refers them to an acquiring bank, which then opens a dedicated merchant account for each one. The ISO may handle sales and some support, but the merchant ends up with its own MID and its own contract with the bank.

A PayFac doesn’t refer anyone. It onboards the merchant itself as a sub-merchant under its own shared master account.

That difference shows up in three places.

1. Speed. ISO onboarding means a full individual underwriting review by the acquirer, with documents, credit checks and a decision that can take days or weeks. PayFac onboarding can finish within hours.
2. Liability. A PayFac assumes financial risk for its sub-merchants directly. Under the ISO model, liability generally sits with the merchant’s own account relationship with the acquirer.
3. Fit. ISOs suit established businesses with larger volumes that want negotiated, custom rates. PayFacs suit smaller businesses and platforms that value speed and simplicity over custom terms.

Neither model is better overall. They serve different merchants. Our roundup of the best merchant service providers shows both models side by side.

Payment Facilitator vs. Payment Processor (and PSP)

Three terms get mixed up here: payment processor, payment facilitator and payment service provider (PSP).

A payment processor is the backend infrastructure.

It moves transaction data between the merchant, the card networks and the banks, then sends back an approval or decline. It doesn’t onboard merchants or underwrite them. It’s the plumbing that every payment, PayFac or not, has to pass through.

A PSP is a broader term for any company that helps businesses accept payments.

People sometimes use it interchangeably with PayFac, but that’s not quite right. A PayFac is one specific kind of PSP, defined by offering sub-merchant accounts under a master MID. Some PSPs work this way. Others give each merchant its own dedicated merchant account, or only provide a gateway that connects to an account the merchant already has. Every PayFac is a PSP, but not every PSP is a PayFac.

Here’s a concrete contrast. A furniture retailer with €20 million in annual card sales applies through a PSP for its own merchant account. It submits financial statements, waits two weeks for underwriting, and gets a dedicated MID with negotiated rates. Meanwhile, a freelance photographer signs up to a booking app, fills in a short form and takes their first card payment the same day as a sub-merchant. The first route is a traditional merchant account. The second is the PayFac model.

The processor sits underneath both.

The partner layer on top, which adds compliance, onboarding and risk work, is what separates a payments partner from just a processor, as we explain in our piece on the cost of compliance.

Benefits of Using a Payment Facilitator

For sub-merchants and the platforms that serve them, a payment facilitator removes much of the friction of accepting payments. Here’s where the gains show up.

• Compliance gets lighter. The PayFac carries most of the PCI DSS burden, the card industry’s data security standard. Sub-merchants typically only complete a short self-assessment instead of a full audit.
• Pricing is easier to understand. Many PayFacs use flat-rate pricing, such as a fixed percentage plus a small fee per transaction, so a business knows what each sale will cost without decoding a statement.
• Onboarding is quick. Sub-merchants can start selling within hours, which matters for anyone who wants to get paid this week, not next month.
• Payment methods are broader. Cards, digital wallets and often local methods come through one integration.
• Contracts are more flexible. Most PayFacs don’t tie merchants into multi-year bank agreements or early termination fees.
• Fraud prevention comes built in. Risk scoring and transaction monitoring run in the background by default.

This model is especially valuable for software platforms that want to embed payment acceptance in their own product. When payments are part of the sign-up flow, onboarding quality decides how many merchants actually go live. We explain why in our article on seamless onboarding for marketplaces.

Examples of Payment Facilitators

The clearest way to understand the model is through the companies that made it mainstream.

• Stripe is the example most people start with. So, is Stripe a payment facilitator? Yes. Stripe also works as a processor and gateway, but its Stripe Connect product is a classic PayFac setup. Platforms use Connect to onboard their own users as sub-merchants. Stripe handles the underwriting and verification and is ultimately liable for chargebacks and losses that a sub-merchant can’t cover.
• Square brought the model to small, in-person businesses. Coffee shops, market stalls and hairdressers can sign up and start taking card payments without a merchant account application.
• PayPal works as a payment facilitator for millions of online sellers, from individuals to established e-commerce stores.
• Adyen for Platforms offers a similar sub-merchant setup for marketplaces and platforms. It’s aimed more at larger businesses and backed by Adyen’s own acquiring infrastructure.

If you’re comparing these providers for your own platform – start with our guide to Stripe alternatives.

How to Choose a Payment Facilitator

If you’re choosing a payment facilitator for your platform, these are the questions worth asking before you sign.

1. Which cards and payment methods does it accept? Check that it covers the major card networks plus the wallets and local methods your customers actually use. A PayFac that’s strong in the US may have gaps in Europe.
2. How transparent is the pricing? Flat rates look simple, but look for chargeback fees, payout fees, currency conversion markups, monthly minimums and rolling reserves. Ask for a full fee schedule, not a headline rate.
3. How strong are its security and fraud tools? Look for PCI DSS Level 1 certification, tokenization, 3-D Secure support and real-time fraud monitoring. Ask how it handles false positives too, because blocked legitimate payments cost you revenue. Good fraud prevention should protect you without getting in the way of genuine customers.
4. How fast is onboarding? Test the sign-up flow yourself. Count the steps and see how long approval takes.
5. Does it support international payments? If you sell across borders, check multi-currency support, settlement currencies and coverage in the countries you’re expanding into.

How to Become a Payment Facilitator

Some platforms reach a point where they want to become a payment facilitator themselves, mainly to capture more of the payments margin and control the experience. Here’s what that path involves at a high level.

1. First, you sign a master merchant agreement with a sponsoring acquiring bank. The bank reviews your business, finances and risk controls closely, because it’s lending you its access to the card networks.
2. Next, you register with the card networks. Visa and Mastercard both require this, with fees and ongoing compliance obligations.
3. You then need underwriting and risk infrastructure. You can build it or buy it: KYC and AML checks, transaction monitoring, chargeback handling and sub-merchant risk scoring. You’ll also need PCI DSS Level 1 compliance.
4. Finally, you set up a reserve account to cover potential losses from sub-merchants.

This is a significant investment in money, people and time. It usually only makes sense at meaningful transaction scale. Most platforms instead partner with an existing PayFac, or with infrastructure that lets them accept card payments without becoming registered themselves.

How ConnectPay Supports Payment Facilitator Models

To be clear, ConnectPay isn’t a card-network-registered payment facilitator. We work one layer down, as infrastructure for platforms that want PayFac-style payment acceptance.

A platform building this kind of model needs a few things underneath it: card acquiring to process and settle payments, a way to onboard merchants, and the compliance work that comes with handling other people’s money. That’s where we fit. We provide card acquiring and merchant services that platforms can build on.

As a licensed EMI, we also run AML and KYC compliance as part of our service. That matters here, because underwriting and compliance are some of the heaviest parts of any PayFac model, as we covered above. Platforms can lean on our existing processes instead of building their own from scratch.

If you’re working out how payments should fit into your platform, ConnectPay can help you map the options.

Decide If the PayFac Model Is Right for Your Platform

Choosing between a payment facilitator, an ISO relationship and a traditional processor isn’t really a vendor decision. It’s a business model decision.

Three factors usually settle it:

1. Transaction volume, because PayFac economics only work at scale.
2. Risk appetite: are you willing to absorb your merchants’ chargebacks and fraud losses?
3. How much underwriting and compliance work do you want to run yourself?

For most platforms, the honest answer is that they don’t need to become a registered PayFac. Partnering with one, or with infrastructure that supports the model, gets merchants paid quickly without taking on the full regulatory and financial burden. If your volumes grow, you can revisit the decision later with real data.

To see how we support platforms on the payments side, start with the options that match your volume and risk profile.