Explained to kids!
When a shop wants to take cards, it needs a bank that handles card money. Two kinds of helpers can bring the shop to that bank. An ISO introduces the shop, and the shop signs with the bank itself. A PayFac signs with the bank once, then lets many small shops sell under its roof.
Let’s see it in real life…
Olu and his dad make a hot sauce that everyone at school asks for. This summer, they want to sell it at the Saturday market.
At the market, there are two ways to get a card machine.
Mrs. Adeyemi walks around the stalls with a folder. She knows the market’s bank well. “I introduce you, you sign your own paper with the bank, and the bank gives you your own machine,” she says. “It takes a few weeks.”
For every stall she brings, the bank gives Mrs. Adeyemi a small thank-you each month. She never touches the stall’s money.
Mr. Costa runs the big food hall at the end of the market. He signed one paper with the bank, a long time ago. Now twenty small cooks sell under his roof, with his machines.
“Set up your table here, and you can take cards this afternoon,” he tells Dad.
At the end of the day, all the card money goes to Mr. Costa first. He keeps a little, then pays each cook their share.
When a customer says “this sauce is not what I ordered”, the bank asks Mr. Costa, not the cook. Mr. Costa has to sort it out, and he checks his cooks carefully before letting them in.
Dad chooses Mr. Costa for the summer. Olu counts: forty-two bottles sold, cards tapped on Mr. Costa’s machine.
Next spring, the sauce is so popular that Dad signs his own paper with the bank, with Mrs. Adeyemi’s help.
That is a PayFac, and that is an ISO.
Tiny recap
- It means… an ISO introduces shops to the bank and gets a thank-you. A PayFac signs once and lets many small shops sell under its roof.
- It helps when… a small shop wants to start today (PayFac), or a bigger shop wants its own deal with the bank (ISO).
- Watch out for… the PayFac is responsible for all its cooks. If one of them cheats, the PayFac has to pay.
…detailed for specialists
PayFac vs ISO compares the two ways a company resells card acceptance. An ISO (independent sales organization) introduces merchants to an acquirer, which signs and funds each merchant directly. A payment facilitator (PayFac) signs one agreement with the acquirer, then onboards merchants as sub-merchants under its own master account, receives their settlement and carries their risk.
In 2026, the choice shapes how software platforms, ISOs and PSPs make money from payments. The ISO model is cheap to start and light on liability. The PayFac model keeps the merchant relationship, the data and most of the margin, but demands scheme registration, risk capital and an operations team. A third option, PayFac-as-a-service, now sits between the two. We describe each actor in who’s who in payments; here we compare the two reseller contracts line by line.
What is an ISO?
An ISO is a sales and service agent registered by an acquirer. It markets the acquirer’s processing, signs up merchants and often services them, but the merchant agreement is between the merchant and the acquirer. Visa and Mastercard call the role a third-party agent (Visa) or member service provider (Mastercard), and ISOs must register with the card brands through their sponsor. The ISO is paid in residuals: a share of the processing fees each merchant pays, for as long as the merchant stays. It does not touch funds and does not carry credit or fraud risk, which is also why its share is small.
What is a payment facilitator?
Visa defines a payment facilitator as a third-party agent that signs a merchant acceptance agreement with a seller on behalf of an acquirer and receives settlement proceeds from the acquirer on behalf of the underlying seller, known as a sponsored merchant or sub-merchant. An entity that does only one of the two is still a PayFac. Mastercard’s wording is close: a service provider that is registered by an acquirer and facilitates transactions on behalf of submerchants, governed by Rule 7.8 of the Mastercard Rules.
The PayFac therefore holds the merchant relationship. It onboards in minutes with its own KYB, prices as it likes, receives the money and pays out. In exchange, Visa’s model paper is blunt about where the risk sits: acquirers are responsible for the acts of both PFs and sponsored merchants, and the acquirer passes that liability to the PayFac by contract.
PayFac vs ISO: the seven differences that matter
- Who holds the merchant agreement. ISO: the acquirer, with the merchant directly. PayFac: the PayFac, on behalf of the acquirer. Visa notes a sponsored merchant may be required to sign a direct merchant agreement with an acquirer, depending on annual Visa sales volume, so very large sub-merchants eventually leave the umbrella.
- Registration. Both are registered by the sponsoring acquirer. Visa’s third-party agent program charges $5,000 USD for initial registration and annual renewal for ISO and PSP categories (PSP is Visa’s registration term covering payment facilitators), per region. The PayFac also needs a documented risk and financial review by the acquirer before its first transaction.
- Onboarding. ISO: the acquirer underwrites each merchant, typically in days or weeks. PayFac: the PayFac underwrites, within the acquirer’s policy, often in minutes for low-risk merchant category codes.
- Funding. ISO: never. PayFac: it receives and directs settlement of transaction proceeds from the acquirer, then pays each sub-merchant. That makes the PayFac a money-handling business, with safeguarding and, in Europe, licensing questions.
- Liability. ISO: none beyond its sales conduct. PayFac: chargebacks, fraud losses and fines of every sub-merchant roll up to it, and then to the acquirer. The chargeback monitoring programs count the whole portfolio.
- Who the merchant of record is. In both models, the merchant stays the seller of record: its name on the descriptor, its taxes, its disputes. A PayFac is not a merchant of record, even though it receives the funds.
- Economics. The ISO earns a residual on the acquirer’s price. The PayFac sets its own price above a wholesale buy rate, and keeps the spread.
PayFac vs ISO in numbers (2026)
- Take rate: a Bain ladder cited in a 2026 market study puts an owned payment facilitator at 60 to 100 basis points of net take against 10 to 40 basis points for a retail ISO arrangement.
- Build cost: the same ladder estimates roughly $200,000 to $800,000 of upfront build for a PayFac-alternative model, and $1 million to $3 million for a rented full PayFac stack.
- Registration: $5,000 USD initial and annual Visa fee for ISO and PSP agents, per region.
- Embedded finance: Bain forecast embedded finance to reach $7 trillion of US transaction value in 2026, 10% of US financial transactions, most of it payments embedded in software.
- Speed: Mastercard’s 2025 paper on PayFac-as-a-service claims it can collapse the time to market for new PayFacs from months to weeks and merchant onboarding from weeks to minutes.
What is PayFac-as-a-service, or a managed PayFac?
Most software platforms want PayFac economics without PayFac operations. PayFac-as-a-service (PFaaS) answers that: a registered PayFac or acquirer provides the master merchant account, the scheme registration, the risk program and the funding engine, and the platform runs onboarding, pricing and the merchant experience under its own brand. Mastercard describes the model as one where PFaaS platforms include capabilities to handle the regulatory compliance and risk management burden, and expects hundreds of new PayFac formations a quarter.
The spectrum then has four steps: referral partner (an ISO in all but name), managed PayFac, registered PayFac, and licensed PayFac with its own acquiring license. The journey from the first to the last is the subject of embedded payments for SaaS: from referral partner to PayFac and of the #TheShot episode From partner to PayFac: the real journey. Each step adds margin and adds obligations.
PayFac vs ISO: what changes for PSPs, PayFacs and platforms
Onboarding is the product
An ISO fills in the acquirer’s form. A PayFac owns the form: KYB, beneficial owners, MCC assignment, sanctions screening, and a decision within the acquirer’s policy. The acquirer still audits it, so every decision needs a trail: who approved, on which document, when. Running the same file through several acquirers is covered in multi-acquirer merchant onboarding without the email chain.
Settlement and payouts
A PayFac receives one settlement from the acquirer and must split it into sub-merchant balances, fees, reserves and payouts, then reconcile both sides. An ISO reads a residual report once a month. The difference is a ledger.
Risk and disputes
Under a PayFac, one sub-merchant’s chargebacks hit the master account’s ratio. Velocity rules, pre-chargeback alerts and per-merchant reserves are not options, they are the condition for keeping the sponsorship. Portfolio-level views, like those in Platform Supervision, exist for that reason.
Pricing: buy rate versus sell rate
The PayFac buys processing at interchange-plus from its acquirer and sells blended or IC++ pricing to sub-merchants. The spread is its revenue, and interchange fees are the floor. The payment revenue solution page shows how ISVs model that spread.
Running ISOs and PayFacs on one platform
Many PSPs do both: they sponsor PayFac programs for software platforms and run ISO and agent channels for direct merchants. Keeping one merchant file, one set of acquirer applications and per-program rules is what meta-program management describes. NORBr Onboarding Workflow runs the KYB and approval steps for sub-merchants and referred merchants under the operator’s brand, with Applications & Partner Sharing sending each acquirer only the data it needs. Acquirers and processors already connected are listed under connectors. For the US market, where the PayFac model was born, see payment methods in the United States; for a longer read on how acquiring roles keep shifting, the Payments Library carries Merchant Acquiring Industry Dynamics.
PayFac or ISO: which one to choose in 2026?
Choose the ISO model when payments are a side revenue and the team is a sales team: low cost, low liability, a residual that compounds. Choose the PayFac model when payments are part of the product: instant onboarding, control of pricing and data, and margin several times higher, paid for with registration, risk capital and an operations stack. Choose PayFac-as-a-service when you want the second without building the third. Whatever the model, the merchant stays the seller of record, the acquirer stays liable to the schemes, and the scheme fee for the registration is the smallest cost on the list.
Frequently Asked Questions
What is the difference between a PayFac and an ISO?
An ISO introduces merchants to an acquirer; the merchant signs with the acquirer and the ISO earns a residual. A payment facilitator signs one agreement with the acquirer, onboards merchants as sub-merchants under its own account, receives their settlement and carries their risk. In both models, the merchant stays the seller of record.
Does a PayFac need to register with Visa and Mastercard?
Yes. The sponsoring acquirer registers the PayFac with each scheme after a risk and financial review. Visa’s third-party agent program charges $5,000 USD for initial registration and for each annual renewal of ISO and PSP agents per region; Mastercard registration follows Rule 7.8 of its rules.
Who is liable for chargebacks under a PayFac?
The PayFac. Visa states that acquirers are responsible for the acts of both PayFacs and sponsored merchants, and acquirers pass that liability to the PayFac by contract. Every sub-merchant’s chargebacks count in the PayFac’s ratio, which is why PayFacs monitor merchants and hold reserves.
How much more does a PayFac earn than an ISO?
Industry benchmarks put an owned PayFac at roughly 60 to 100 basis points of net take on volume, against 10 to 40 basis points for a retail ISO arrangement. The gap pays for scheme registration, risk capital, funding operations and a compliance team that an ISO does not need.
What is PayFac-as-a-service?
A model where a registered PayFac or acquirer provides the master account, scheme registration, risk program and funding, while a software platform runs onboarding and pricing under its own brand. Mastercard says it cuts a PayFac launch from months to weeks. See NORBr x Payplug on PayFac-as-a-service.
