What Is a Payment Facilitator?

A payment facilitator, often called a PayFac, is a company that lets other businesses accept payments under its payment infrastructure instead of forcing each business to open a traditional merchant account from scratch.

This model matters because many software platforms, marketplaces, SaaS products, and B2B2C businesses want to monetize payments without becoming a full bank or processor. They need a practical way to onboard merchants, process transactions, manage risk, and earn revenue from payment volume.

Why Companies Care About Payment Facilitation

If you run a platform that already serves merchants or end users, payments can become more than an operational feature. Payments can improve the customer experience, create transaction-level data, and become a meaningful revenue stream.

The business model usually starts with three related concepts: revenue share, ISO relationships, and money-services or money-movement models. They are not the same thing, but they often appear together when a company is deciding how deeply it wants to participate in payment processing.

Revenue Share

So, want to begin with an example:

Let's say, you have a B2B2C Platform that provides services to apartment complexes or vacation housing. Your platform provides property management, floor plans, ledger management, accounting, billing, payments processing, and other services.

In order to process payments, your company needs to team up with a payment services provider, or PSP that facilitates digital or electronic payments processing. Your company reaches a revenue share agreement with the PSP on a volume in traffic of funds. The idea is to bring customers that are on your platform already, to work with your PSP. Usually, the PSP is a bank, or non-bank financial institution like Chase Paymentech, FirstData, Bank of America Merchant Services, and a lot more.

The main difference between your company and PSP is that the PSP has relevant licenses and rights to move funds for merchants and to charge for that a fee. This fee is usually called a Merchant Fee.

Now, we are going to talk about licenses and rights, and this is the time when I am going to talk about the second model, which is called ISO.

Before I am going to move to the next topic, I want to explain in a few words what merchant fees are.

So, every transaction that's processed via a PSP contains the total amount = merchant fees 3% usually + amount is going to be settled on the merchant's bank account. So, out of 3%, something is going to the card network and all the rest stays with the PSP. So, the revenue share is coming out of the leftover with PSP.

Practically what happens with companies that are in B2B2C business, these are illustrating ways to make more out of every transaction or in another way to call it RPU, which is revenue per user or RPC, which revenue per customer or RPT, which is revenue per transaction.

So, one of the ways, or models to become a sort of PSP is to apply for a relevant license and one of these licenses is called ISO. This kind of licence basically gives the honor to the company to resell Merchant Services and to nominate the merchant fee by themselves.

ISO Model

So, what is the ISO billing model?

First of all, ISO is an Independent Sales Organization. In the street language, it’s called a non-bank financial institution. ISO Company is a company that can and is able to resell Merchant Services for businesses. ISO is a licence that a company receives from a sponsor bank in other words, an ISO company that is hired by a business or a merchant to process its payments. And not less important than other benefits of being an ISO company is that an ISO company can nominate the merchant fees and as I mentioned before that it can be 3%, and sometimes more. Here are some of the known ISO companies: Braintree, Stripe, and Square. Basically, ISO is an organization that is a go-to “Partner,” for merchants to deal with anything that is related to payments processing and other related topics.

And it’s about time to discuss the most interesting billing model in my mind. I want to call this model even a business model. Yes, I am going to discuss MSB.

MSB Model

So, what is the MSB billing or business model?

MSB -Money Service Business. Several companies that I am sure you’ve heard of before are Western Union, MoneyGram, PayPal, Check Free, GoFundMe, Airbnb, ACE Cash, and lots more.

Basically, and in other words, an organization that has the MSB license has the right to charge end users a Service Fee for moving their fund from one location to another. Money charges services fee people for using their technology or channel to move money from one location to another. If you want to send money from America to Russian using MoneyGram, you need to pay MoneyGram a service fee that is most of the time even percentage of the sent or transferred amount. There is more usages of this model like cash checks, foreign currency exchange service , transferring stored value card in cash and all of these are services obligated.

Summary:

Merchant fees - amounts charged by a PSP per transaction

ISO - Independent Sales Organization

MSB - Money Service Business

What Is a Payment Facilitator (PayFac)?

A Payment Facilitator (PayFac) is a company that holds a master merchant account with an acquiring bank and provides payment acceptance services to smaller merchants — called sub-merchants — under that master account. Instead of each sub-merchant going through the full bank underwriting process to get their own merchant account, the PayFac underwrites, onboards, and takes on liability for them.

Think of a PayFac as the merchant of record for the acquiring bank. The acquiring bank has one relationship — with the PayFac. The PayFac then manages hundreds or thousands of sub-merchants, each of whom can start accepting payments almost instantly.

This is fundamentally different from the ISO model. An ISO introduces merchants to processors and earns residuals, but each merchant still gets their own direct merchant account with the acquirer. A PayFac aggregates merchants under its own account — faster onboarding, more control, but also more risk and regulatory responsibility.

How the PayFac Model Works

Here is how the money and liability flow in a PayFac structure:

1. Master Merchant Account: The PayFac is approved by an acquiring bank (e.g., Worldpay, Fiserv, Stripe) and holds a single master merchant account. This approval process involves extensive due diligence on the PayFac itself — financial strength, fraud controls, compliance program, and underwriting policies.

2. Sub-Merchant Onboarding: When a new merchant signs up to use the PayFac's platform, the PayFac underwrites them internally. This typically involves KYC (Know Your Customer) checks, identity verification, business validation, and risk scoring — all done in minutes or hours instead of weeks.

3. Transaction Processing: When a sub-merchant's customer pays, the funds flow to the PayFac's master account first. The PayFac then sweeps the sub-merchant's portion to their bank account, typically on a T+1 or T+2 schedule, minus the PayFac's fee.

4. Risk and Liability: If a sub-merchant commits fraud, triggers excessive chargebacks, or goes bankrupt with pending settlements, the PayFac is on the hook — not the acquiring bank. This is the core trade-off of the PayFac model: faster onboarding in exchange for owning the risk.

5. Revenue Model: PayFacs typically earn the spread between what they pay the acquirer (interchange + network fees + acquirer markup) and what they charge sub-merchants. At scale, this spread — often 0.3%–1.5% on volume — is highly profitable.

Leading Payment Facilitators and PayFac Platforms

Some of the largest technology companies in the world operate as Payment Facilitators:

Square (Block): The company that popularized the modern PayFac model for small businesses. Square underwrites merchants in minutes and charges a flat 2.6% + $0.10 for card-present transactions. It holds the master merchant account; every Square seller is a sub-merchant.

Stripe: Operates as a PayFac through Stripe Payments and offers Stripe Connect — a platform that lets software companies become PayFacs themselves (or use Stripe as the PayFac infrastructure). Processing hundreds of billions in annual volume.

PayPal / Braintree: PayPal was an early pioneer of the PayFac model for online merchants. Braintree, its developer-facing product, powers many of the largest e-commerce platforms.

Toast: A vertical PayFac for restaurants. Toast provides POS hardware, software, and payment processing — all in a single PayFac structure. This integration is why vertical SaaS companies increasingly embed payments via the PayFac model.

Mindbody, Vagaro, Housecall Pro: Examples of vertical SaaS platforms that have embedded payments as PayFacs within their specific industry verticals (fitness, salons, home services).

For companies that want PayFac economics without the full compliance and underwriting burden, PayFac-as-a-Service (PFaaS) platforms like Adyen for Platforms, Stripe Connect, Infinicept, and Payrix provide the infrastructure so software companies can offer sub-merchant onboarding without holding the master merchant account directly.

When to Become a Payment Facilitator (vs. ISO or Referral Partner)

Becoming a PayFac is a major business decision. Here is how to think about the trade-offs:

Become a PayFac when:

• You have a software platform with many SMB customers who need payment acceptance and you want to own the full payments P&L
• You process (or expect to process) $50M+ in annual payment volume — at this level the economics justify the compliance cost
• Fast sub-merchant onboarding is a competitive differentiator (seconds vs. days)
• You want to control the merchant experience end-to-end — pricing, dashboard, payouts, disputes
• You have the resources for underwriting, KYC/AML compliance, fraud monitoring, and chargeback management

Use ISO or referral instead when:

• Your payment volume is below ~$10M–20M annually — the PayFac compliance overhead won't be worth it
• You want revenue share without owning fraud and chargeback liability
• Your merchants are larger businesses who qualify for — and expect — direct acquiring relationships

Use PayFac-as-a-Service when:

• You want PayFac-like economics and onboarding speed but aren't ready for the full regulatory and risk ownership
• You're a SaaS company embedding payments for the first time
• Speed to market matters more than maximum margin

Frequently Asked Questions: Payment Facilitators

What is the difference between a PayFac and a payment processor?
A payment processor (acquirer) is the financial institution that connects merchants to card networks and settles funds. A PayFac is a company that sits between the acquirer and sub-merchants — it holds the master account and takes on underwriting and risk responsibility so sub-merchants don't need direct acquirer relationships.

How does a PayFac make money?
PayFacs earn the spread between the acquirer's blended cost (interchange + network fees + acquirer markup) and the rate charged to sub-merchants. They can also add flat per-transaction fees, monthly SaaS fees, chargeback handling fees, and premium features (instant payouts, virtual terminals, invoicing).

How long does it take to become a PayFac?
Full PayFac registration with an acquiring bank typically takes 6–12 months and requires a formal application, compliance documentation, underwriting policy, fraud monitoring infrastructure, and in some cases a reserve deposit. PayFac-as-a-Service platforms can reduce this to 4–8 weeks.

What are the risks of operating as a PayFac?
PayFacs own the fraud and chargeback risk for every sub-merchant. If a sub-merchant has high chargebacks, processes fraudulent transactions, or cannot cover settlements, the PayFac absorbs the loss. This is why robust KYC at onboarding and ongoing transaction monitoring are non-negotiable for PayFacs.

Do PayFacs need a special license?
PayFacs must register with Visa and Mastercard as a Payment Facilitator and comply with card network rules (Visa's PayFac program, Mastercard's Payment Facilitator Standards). They must also comply with PCI DSS, AML/KYC requirements, and applicable state money transmission laws depending on how their settlement flows are structured.

Related Reading

The PayFac model sits at the intersection of payments infrastructure, risk management, and software monetization. These posts provide essential context:

• Payment Processing Fees Explained — PayFacs earn revenue from the spread between interchange + acquirer costs and what they charge sub-merchants. This deep dive covers interchange rates, pricing models (interchange-plus, flat-rate, tiered), and how to calculate your effective rate.
• What Is a Chargeback? — As a PayFac, you own chargeback liability for every sub-merchant. Understanding dispute triggers, the chargeback lifecycle, and prevention strategies is non-negotiable for any PayFac's risk program.
• What Is BNPL? — Several vertical SaaS platforms operating as PayFacs are integrating BNPL options alongside card acceptance. Understanding how BNPL economics differ from card interchange helps inform your checkout monetization strategy.
• Network Tokenization vs. Vendor Tokenization — how network tokens from Visa, Mastercard and Amex improve authorization rates and lifecycle management for card-on-file transactions.