What Is a Payment Facilitator (Payfac)? How It Works and Whether to Become One

A payment facilitator, or payfac, is a company that lets many businesses accept card payments under its own master merchant account with an acquiring bank, so each business doesn't need an individual merchant account. For a software platform or marketplace, becoming one gives you control over onboarding, checkout, and payments revenue. It also moves underwriting, fraud losses, and compliance work onto your team.

This guide is written for founders, product leads, and finance leads deciding whether the payfac model fits their platform. It covers how the structure works, how money moves, how a payfac differs from an ISO, processor, gateway, and acquirer, what you take on, and what the alternatives look like.

What is a payment facilitator?

A payment facilitator is a registered intermediary that onboards businesses, called sub-merchants, and processes their card payments under the payfac's own merchant account. The payfac is the party the card networks (Visa and Mastercard) and the acquiring bank hold responsible for those sub-merchants. The sub-merchant signs a services agreement with the payfac, not a traditional merchant agreement with a bank.

Square and PayPal are the familiar examples of this structure at consumer scale. Software platforms use the same model to embed payments inside their product.

Master merchant vs sub-merchant

The master merchant is the payfac. It holds the merchant account, the sponsoring acquirer relationship, and the network registration. Every sub-merchant's transactions flow through that single account.

A sub-merchant is the business actually selling something: a yoga studio using scheduling software, a host on a rental platform, a contractor invoicing through a field service app. Sub-merchants skip the standalone application, which is why a payfac can onboard them quickly. The trade-off is that the payfac must do the vetting the bank would otherwise do, and it answers for the outcome.

How a payfac transaction and settlement flow works

A card payment moves through authorization first, then clearing and settlement later. The payfac sits between the sub-merchant and the acquirer for the money, and usually also controls the checkout experience.

1. The cardholder enters card details at the sub-merchant's checkout, which the platform hosts.
2. A payment gateway encrypts the data and sends the authorization request onward.
3. The processor routes the request over the Visa or Mastercard network to the issuing bank.
4. The issuer approves or declines, and the response travels back along the same path to the checkout.
5. Approved transactions are batched for clearing. The card networks calculate what each party owes.
6. The acquirer settles funds to the payfac's account, net of interchange, network assessments, and acquirer fees.
7. The payfac deducts its own fees and pays out the remainder to each sub-merchant, according to the payout schedule in their agreement.

Step 7 is where the payfac business model lives. The difference between what the payfac charges the sub-merchant and what the acquirer charges the payfac is the platform's payments margin. It is also where reconciliation gets difficult, because one settlement deposit from the acquirer covers hundreds or thousands of individual sub-merchant transactions, refunds, and chargebacks.

Payfac vs ISO vs processor vs gateway vs acquirer

These five terms describe different jobs, and one company often does several of them. The table separates the roles.

Payment facilitator vs payment processor

A processor moves transaction data and funds. A payfac decides who gets to accept cards in the first place. A payfac typically uses a processor (sometimes its acquirer's own processing platform) to do the technical routing, so you'll often see both in one payments stack. The processor doesn't underwrite your sub-merchants. The payfac does.

Payment facilitator vs acquirer

The acquirer is the bank with direct membership in the card networks. The payfac is a customer of the acquirer, registered through the acquirer as permitted to aggregate sub-merchants. The acquirer is the one that sponsors the payfac, sets risk limits, and ultimately holds the network relationship. A payfac cannot exist without one.

Payment facilitator vs payment gateway

A gateway is a technology layer. It encrypts card data and passes it along, and it takes no position on who is allowed to be a merchant. You can run a gateway with traditional merchant accounts and never become a payfac. Conversely, every payfac needs a gateway or its own equivalent to take payments.

Payfac vs ISO

An ISO sells and supports merchant accounts but doesn't hold the master relationship with the networks. Each merchant has its own agreement with the underlying acquirer. A payfac pools merchants under one account and takes on the risk. For a platform, the ISO route is closer to a referral arrangement, which is covered below.

What your platform takes on when it becomes a payfac

Becoming a payfac moves six responsibilities from the bank to you. Each one needs a named owner, tooling, and budget before launch.

Underwriting and KYC/KYB

You verify who each sub-merchant is before they can take a payment. KYC covers the individuals involved, and KYB covers the business: legal entity, ownership, and business type. Screening against sanctions and watchlists is part of this. You'll also need a policy for which business categories you accept and which you refuse, because your acquirer will hold you to the risk limits you agree on.

Sub-merchant onboarding

Onboarding is also a product problem. A long application costs you activation. A short one with weak checks costs you fraud. Most platforms try to collect data inside the existing signup flow and automate approval for clean applications, sending only the unusual ones to manual review.

Risk and chargebacks

The payfac is generally liable when a sub-merchant can't cover a chargeback or refund. If a vacation rental host cancels a stay, keeps the deposit, and disappears, the cardholder's dispute lands on your master account. That makes reserve policies, payout timing, transaction monitoring, and dispute handling real operating functions, not back-office afterthoughts. Fraud tooling such as card-not-present screening and 3D Secure reduces exposure but doesn't remove it.

PCI scope

Any entity that stores, processes, or transmits card data falls under PCI DSS. A payfac is typically assessed at a higher service-provider level than an ordinary merchant. Hosted fields, tokenization, and redirect checkouts shrink what touches your own servers, and that choice affects your compliance burden more than almost anything else in the technical design.

Card network registration through a sponsoring acquirer

Visa and Mastercard require payment facilitators to be registered, and the registration runs through a sponsoring acquiring bank. The acquirer reviews your business, your risk controls, and your financials, then files with the networks. Program rules and requirements vary by acquirer and change over time, so confirm current terms with the acquirer and your own counsel before you commit engineering time.

Funding and reconciliation

You need ledgers that tie each sub-merchant's transactions, fees, refunds, reserves, and chargebacks back to the acquirer's settlement file. Finance teams underestimate this. A payout error is a customer-facing problem, and a reconciliation gap is an accounting problem, and both land on the same team.

How to become a payment facilitator: the sequence

The path generally runs in this order, though the details differ by acquirer:

1. Pick a sponsoring acquirer and agree on program terms, risk limits, and reserve requirements.
2. Design the underwriting policy and the sub-merchant agreement with legal counsel.
3. Build or buy onboarding, KYC/KYB, and transaction monitoring.
4. Decide your checkout architecture to control PCI scope.
5. Complete the acquirer's review and the network registration it files on your behalf.
6. Stand up funding, payouts, and reconciliation, then test with a small group of sub-merchants before opening wider.

Payfac-as-a-service and referral models

Full payfac status is one end of a spectrum. Two other models let a platform offer embedded payments with far less of the burden.

In a payfac-as-a-service arrangement, a provider that is already registered carries the master merchant relationship, underwriting, and most compliance work. You integrate its APIs and present payments under your own brand. You earn a share of the payments revenue, usually smaller than a full payfac would earn, and you give up some control over onboarding rules, payout timing, and pricing.

In a referral or ISO-style model, you send your customers to a processor or acquirer. They sign their own merchant agreements, and you earn a referral payment or residual. You carry almost no risk, and you also get little control over the customer experience. Your users leave your onboarding flow to apply elsewhere.

Becoming a full payfac tends to make sense when payments volume through your platform is large enough that the margin funds a risk and compliance team, when you need control over onboarding and payout timing to differentiate your product, and when your sub-merchant base is predictable enough to underwrite. It tends to be the wrong move when your volume is still small or uncertain, when your sub-merchants operate in high-dispute categories you don't understand, or when your engineering team is better spent on your core product. Plenty of platforms start with a service model and revisit full registration once volume justifies it.

Should you become a payment facilitator? A decision checklist

Answer these honestly. Several "no" answers point toward a partner model.

• Do you process enough card volume through your platform that payments margin materially changes your revenue?
• Does owning onboarding and payout timing give you a product advantage you can't get from a partner?
• Can you name the person responsible for underwriting policy, and the person responsible for chargeback losses?
• Do you have, or can you hire, risk, compliance, and payments operations staff?
• Can your balance sheet absorb chargeback and fraud losses and any reserve the acquirer requires?
• Do your sub-merchants fall into low-to-moderate risk categories you understand?
• Is your finance team ready to reconcile sub-merchant ledgers to acquirer settlement files?
• Have you discussed program terms with an acquirer and reviewed them with counsel?

Platform types that use the model

Software platforms are the most common case. Vertical SaaS products for restaurants, fitness studios, salons, and home services embed payments so the customer never leaves the app, and the platform earns on every transaction.

Marketplaces use payfacs for a different reason: money has to be split. A buyer pays once, and funds go to the seller minus the marketplace's fee. Handling that split under one master account is much cleaner than asking every seller to hold a separate merchant account.

Property and vacation rental software is a good illustration of the risk side. Guests pay deposits weeks or months before a stay, so the time between payment and service delivery is long, and that gap raises chargeback exposure. Platforms that handle property management payment processing (rent, deposits, owner payouts) or vacation rental payment processing (booking payments, security deposits) have to think carefully about payout timing, reserves, and dispute evidence. The operational design matters as much as the registration.

Questions to ask an acquirer or payfac partner

Ask these before signing anything, and get the answers in writing.

On program structure

• Do you sponsor new payfacs, or do you only offer a payfac-as-a-service product?
• Who is the master merchant of record for my sub-merchants?
• What business categories are prohibited or restricted under your program?

On risk and liability

• Who bears chargeback and fraud losses, and under what conditions does liability shift to me?
• What reserves, deposits, or guarantees do you require?
• How do you set and change my processing limits?

On pricing and data

• Is pricing interchange-plus or blended? Will I see interchange, network assessments, and your markup as separate line items?
• What reporting and settlement files do I get, and in what format?
• What happens to my pricing if my card mix changes?

On operations and exit

• Who handles sub-merchant support, and who handles disputes?
• What are the onboarding and underwriting requirements for each sub-merchant?
• If we leave, can we migrate sub-merchants and tokens, and what are the terms?

Why pricing transparency matters when you earn margin on payments

If you earn margin on payments, you need to know your true cost on every transaction. Under a blended or flat-rate arrangement, the acquirer or processor quotes one rate and keeps interchange, network assessments, and its own markup bundled together. Interchange varies by card type, so a mix shift toward premium rewards cards or commercial cards can quietly cut your margin even though your sub-merchant rate hasn't changed.

Interchange-plus pricing separates the costs. You see the interchange set by the card networks, the assessments, and the provider's fixed markup. That lets you set your own sub-merchant pricing with a clear view of what you actually keep, and it makes it possible to check whether your provider's markup is what the contract says.

There is a real trade-off. Interchange-plus statements are more detailed and harder to reconcile than a single flat percentage. Flat-rate pricing is simpler to understand and forecast for small sellers. Many platforms buy on an interchange-plus basis and still charge their own sub-merchants a simple flat rate, so the complexity stays on the platform's side. The point is that you choose how much of that visibility to pass along instead of having it hidden from you.

Frequently Asked Questions

Check your pricing before you commit

Whatever model you choose, the cost structure underneath it decides how much margin your platform keeps. Pulse Pay offers direct Visa and Mastercard acquiring with interchange-plus pricing, plus automated sub-merchant onboarding with KYC and AML checks. It also offers a free IC++ audit, which compares your current statements against an interchange-plus structure so you can see where your costs sit before you negotiate with an acquirer or payfac partner.