Payments facilitator
What is a payments facilitator?
Payments facilitator (PayFac) is a company that holds its own with an and lets other businesses accept card payments as sub-merchants underneath it. Each sub-merchant processes under the facilitator's master account instead of applying for a merchant account of its own.
The model exists because direct merchant account setup is slow: a business applies to an acquiring bank, waits through , and signs its own processing agreement. A facilitator does that work once. It contracts with an acquiring bank and its , then resells acceptance to sub-merchants under its own registration, which turns onboarding into a same-day step inside its product. The trade is liability: the facilitator answers to the acquiring bank for the chargebacks and its sub-merchants generate. Vertical SaaS, marketplaces, and booking or invoicing platforms use the model to put checkout inside software their customers already run their business on.
Key facts
- Also known as: PayFac, payfac, payment facilitator
- Holds: a master merchant account and (MID) with an acquiring bank, plus a facilitator registration with the card schemes
- Onboards: sub-merchants, which process under the facilitator's MID rather than their own
- Carries: underwriting, , and liability for every sub-merchant it approves
- Used by: vertical SaaS, marketplaces, and platforms that embed checkout in their own product
How it works
- Registration. The facilitator signs with an acquiring bank and registers with the card schemes. That registration produces the master MID all sub-merchant activity runs through, and it defines what the facilitator may do on a sub-merchant's behalf.
- Sub-merchant onboarding. Applicants submit business and ownership details. The facilitator runs identity, sanctions, and fraud screening itself rather than routing each application to the bank, which is what compresses setup from weeks to hours.
- Processing. Sub-merchant transactions are authorized and cleared under the facilitator's MID. To the scheme and the , the traffic belongs to the facilitator's account.
- Settlement. The acquiring bank settles funds to the facilitator, which splits the batch and pays each sub-merchant its share, net of fees.
- Risk and disputes. Chargebacks land on the facilitator's account first. It works the dispute, recovers the amount from the sub-merchant, and watches its portfolio ratio, because scheme monitoring programs assess the facilitator's aggregate volume.
Why it matters
- Onboarding speed. Underwriting happens once at the facilitator level, so a sub-merchant can take its first payment the day it signs up instead of waiting on a bank application.
- Payments become product revenue. A platform operating as a facilitator earns a margin on every transaction its sub-merchants process, on top of subscription fees.
- One counterparty for the bank. The acquiring bank underwrites and monitors a single registered entity rather than thousands of small businesses, which is why it accepts sub-merchants it would decline individually.
Common issues
- Statement confusion. Sub-merchant charges appear under a built from the facilitator's setup. When the doesn't recognize the name on the statement, the charge comes back as a friendly-fraud chargeback the facilitator has to defend.
- Portfolio risk. One sub-merchant with a dispute spike raises the ratio the schemes measure across the whole master account, and any remediation program attaches to the facilitator's registration.
- Volume graduation. Scheme rules limit how much a single sub-merchant may process under a facilitator before it needs a merchant account of its own. Those limits are set by each scheme and revised periodically, so the current figure comes from the scheme rules or the acquiring bank.
- Operational load. Underwriting, settlement splits, and dispute handling move from the bank to the facilitator, which needs the staff, reserves, and systems to run them.
