Home
/
#PayDecoding
/
Who’s Who in Payments? ISVs, ISOs, PayFacs, PSPs, Acquirers (2026)
Who’s Who in Payments? #PayDecoding cover
PayFac
ISV
Acquiring
Embedded Payments
Merchant Services

Who’s Who in Payments? ISVs, ISOs, PayFacs, PSPs, Acquirers (2026)

Ludovic Plisson
Ludovic Plisson
Chief Brand Officer
LinkedIn

Explained to kids!

A payment facilitator (PayFac) is a helper that collects card payments for lots of small sellers at once, then gives each seller its share. It works with other helpers: one builds the software, one sells the card machines, and a bank makes sure the money really moves.

Let’s see it in real life…

Isaac goes to the school spring fair with his grandma.
There are twenty stands: cakes, books, plants and face painting.
None of the stands has its own card machine.
Instead, the parents’ association runs one big pay desk for everyone, and Grandma pays there with her card.
Each stand writes down what it sold in a notebook the association gave them.
On Monday, the association gives each stand its share. The cake stand gets the most!
Behind the desk, a bank makes sure the card money really arrives, and checks that the fair is a real school fair.
“So the association is like one big piggy bank for all the stands?” asks Isaac.
That is a payment facilitator.

Tiny recap

  • It means… one helper collects payments for many small sellers and pays each of them back.
  • It helps when… small sellers want to accept cards without each signing up with a bank.
  • Watch out for… the helper must know every seller well, because if one seller cheats, the helper has to fix it.

…detailed for specialists

A payment facilitator (PayFac) is a company that signs up smaller merchants as sub-merchants under its own master relationship with an acquirer, collects their card payments and pays them out. It sits in a chain with ISVs, ISOs, PSPs and acquirers, and each player has a different legal status, scheme role and level of risk.

Getting these roles right matters in 2026. Software platforms are turning into payment providers, acquirers are consolidating, Visa now monitors fraud and disputes at portfolio level, and EU rules on platforms that handle funds are tightening. The label on a website says little: what counts is who holds the license, who is registered with the schemes, and who pays when things go wrong.

Who’s who in payments: three lenses

Each company in the chain can be described in three ways, and they often do not match:

  • Legal status: is it licensed to hold or move third-party funds? In the EU, that means a bank, a payment institution or an e-money institution.
  • Card scheme role: is it registered with Visa and Mastercard, and as what: acquirer, payment facilitator, marketplace, or agent?
  • Business model: software vendor, sales channel, aggregator, gateway or full-stack provider.

A single company can combine several roles. Some providers are licensed acquirers and also act as PayFacs for platforms. Some software vendors are registered PayFacs, others only refer merchants and take a revenue share.

The five roles, one by one

ISV (independent software vendor)

Builds the software merchants run their business on: restaurant POS, salon booking, practice management, e-commerce platform. An ISV embeds payments to earn revenue and keep customers. It may not touch funds at all: it can refer merchants to a PSP, partner with a PayFac, or become one. When its merchants sell both in store and online, the ISV also has to connect the two channels, the subject of unified commerce.

ISO (independent sales organization)

A sales agent for an acquirer. Under Visa’s rules, an ISO does not process transactions, receive settlement funds or access card data. When a merchant signs with an ISO, it signs with the acquirer. ISOs must be registered with the schemes by their acquirer.

PayFac (payment facilitator)

A scheme role. The PayFac signs merchant agreements on the acquirer’s behalf and can receive settlement for its sub-merchants, which it then pays out. All Visa requirements still apply to each sponsored merchant. When a sponsored merchant exceeds US$1 million in annual Visa sales, the acquirer must be added to its merchant agreement. The PayFac owns onboarding, monitoring and, in practice, the first loss.

PSP (payment service provider)

A broad commercial term for any company that lets merchants accept payments: gateway, processing, payment methods, sometimes acquiring. In Europe, “PSP” also has a legal meaning under PSD2: a licensed provider of payment services. A gateway that never touches funds and a licensed acquirer can both call themselves PSPs.

Acquirer

The licensed member of Visa and Mastercard that contracts with merchants, or with PayFacs, and settles card payments to them. The acquirer remains responsible for the acts of its merchants and of every entity operating between it and them.

Two related roles complete the picture: the marketplace, which brings buyers and sellers together on its own branded platform and receives settlement on their behalf, and the merchant servicer, a provider such as a gateway that the merchant hires directly and that never receives funds.

How a card payment flows through them

  1. The customer pays in the merchant’s software, built by an ISV.
  2. The payment goes through a gateway or PSP to the acquirer, which sends it to the card scheme and the issuer for authorization.
  3. At settlement, the acquirer pays the PayFac (or the merchant directly, if there is no PayFac).
  4. The PayFac splits the funds, deducts its fees and pays out each sub-merchant.
  5. If a chargeback comes back, it travels the same chain in reverse.

Who’s who in payments in numbers (2026)

Regulation: what the license covers

Card scheme registration and a financial license are two different things. A PayFac registered with Visa and Mastercard still needs a legal basis to hold its sub-merchants’ money. In Europe, that means a payment or e-money license, or a model where a licensed partner holds the funds.

Some platforms have relied on the commercial agent exclusion. Under the Payment Services Regulation, agreed in April 2026 and still awaiting formal adoption in October 2026, it will apply only when the platform acts for one side of the deal, buyer or seller, and has real scope to negotiate or conclude the sale. EBA guidelines are expected to clarify it, and platforms that handle both buyer and seller funds should prepare for a license or a licensed partner.

Who’s who: what changes for PSPs, PayFacs and platforms

Pick the right model

An ISV has three options: refer merchants to a provider for a revenue share, run a managed PayFac model where a partner carries registration and compliance, or become a full PayFac. Each step up brings more revenue, more control over onboarding and pricing, and more liability.

Own the onboarding

A PayFac must know each sub-merchant: identity, beneficial owners, business model, expected volumes. Fast onboarding is a sales argument, but it is also where fraud and dispute risk enter. Checking payout accounts with Verification of Payee is now part of good practice in the euro area.

Monitor and pay out

Split payments, reserves, payout schedules and per-merchant risk monitoring are the daily work. Card testing and disputes on one sub-merchant can push the whole portfolio over a scheme threshold, so velocity limits and dispute ratios should be tracked per sub-merchant. NORBr provides the white-label payment infrastructure to route, onboard, pay out and analyze, under your own brand.

Is becoming a PayFac worth it in 2026?

For software platforms with many small merchants and a clear vertical, payments can be a strong revenue line, and owning the experience keeps customers. But being a PayFac is a regulated, risk-bearing business. Start by mapping who holds the license, who is registered with the schemes and who pays for losses, then choose the model that fits your size.

Frequently Asked Questions

What is a payment facilitator (PayFac)?

A payment facilitator is a company registered with the card schemes through an acquirer that onboards smaller merchants as sub-merchants, collects their card payments and pays them out. It handles onboarding and risk monitoring, and bears the first loss if a sub-merchant fails.

What is the difference between an ISO and a PayFac?

An ISO is a sales agent: it sells an acquirer’s services, but the merchant contracts with the acquirer and the ISO never receives funds. A PayFac signs merchants on the acquirer’s behalf, can receive settlement and pays out its sub-merchants.

What is the difference between a PSP and an acquirer?

PSP is a broad term for any provider that lets merchants accept payments, from gateways to full-stack processors. An acquirer is the licensed member of the card schemes that contracts with merchants and settles card payments to them. Some PSPs are also acquirers.

Is an ISV a payment provider?

Not necessarily. An ISV builds business software and can embed payments by referring merchants to a provider, partnering with a PayFac, or registering as a PayFac itself. Only in the last case does it carry scheme obligations and merchant risk.

When does a sub-merchant need a direct contract with the acquirer?

Under Visa rules, when a sponsored merchant exceeds US$1 million in annual Visa sales, the acquirer must be added to its merchant agreement. The PayFac can continue to process transactions and receive settlement for that merchant.

The best infrastructure is the one your clients

Discretion isn’t a feature we sell. It’s how the product is built.

Book a demo