Payment Facilitator (PayFac) vs ISO: What’s the Difference?

PayFac vs ISO is one of the first decisions a software platform makes when it adds payments.

Updated September 2026.

If you are a software platform, marketplace, or SaaS company thinking about adding payments, you will quickly run into two acronyms: PayFac (Payment Facilitator) and ISO (Independent Sales Organisation). Both models let you offer card-acceptance to other businesses — but the economics, liability, and time-to-market are completely different. This guide explains exactly what each model is, where they differ, and how to choose.

What Is a Payment Facilitator (PayFac)?

A Payment Facilitator (PayFac) is a company that has signed a master merchant agreement directly with an acquiring bank and card network (Visa, Mastercard). Under this agreement, the PayFac takes on full liability for all payments processed by its sub-merchants — the businesses that sign up to use the PayFac’s platform.

Classic examples of PayFacs: Square, Stripe, PayPal, Adyen for Platforms, and WooPayments. When a small business signs up for Square, Square is the merchant of record — not the small business. Square handles onboarding, underwriting, risk, settlement, and chargebacks on behalf of every sub-merchant.

Key characteristics of a PayFac:

Holds a master merchant account with an acquirer
Instantly (or near-instantly) onboards sub-merchants — no individual merchant applications
Controls the user experience end-to-end: checkout, dashboard, payouts
Bears chargeback liability and fraud risk for sub-merchants
Earns a spread between the interchange rate charged by the acquirer and the rate charged to sub-merchants
Must comply with card network PayFac registration requirements (Visa PFAC, Mastercard Payment Facilitator programmes)

What Is an ISO (Independent Sales Organisation)?

An ISO (Independent Sales Organisation) is a registered reseller of payment processing services. An ISO does not hold its own merchant accounts — it sells merchant accounts issued by an acquiring bank. Each merchant the ISO brings on gets their own individual merchant ID (MID) directly with the acquirer.

ISOs typically partner with processors such as First Data (Fiserv), TSYS, or Worldpay. A Merchant Service Provider (MSP) is the Mastercard equivalent of an ISO — the terms are often used interchangeably.

Key characteristics of an ISO:

Resells acquiring services under a bank sponsorship agreement
Each merchant gets their own MID — the ISO is not the merchant of record
Merchants go through a full bank underwriting process (can take days to weeks)
ISO earns residuals: a share of the interchange and processing fees the merchant pays
The merchant is liable for its own chargebacks, with the acquiring bank as backstop, not the ISO (unless the ISO has contractually agreed to share risk)
Lower capital requirements and regulatory burden than a PayFac

PayFac vs ISO: Key Differences

Factor	PayFac	ISO
Merchant of record	PayFac (master MID)	Individual merchant (own MID)
Onboarding speed	Instant to minutes	Days to weeks
Chargeback liability	Sub-merchant first; PayFac backstops	Merchant first; acquirer backstops
Capital requirement	High (reserve funds, compliance)	Low to moderate
Revenue model	Spread on interchange	Residual commissions
User experience control	Full (white-label checkout)	Limited (redirects to processor)
Card network registration	Required (Visa PFAC / MC PayFac)	Required (Visa ISO / MC MSP)
Time to market	6–18 months (full build) or weeks (PayFac-as-a-Service)	2–4 months
Best for	SaaS platforms, marketplaces, embedded finance	Sales-led merchant acquisition, independent agents

PayFac vs ISO: Pros and Cons

PayFac — Pros

Instant onboarding: sub-merchants can start accepting payments in seconds, dramatically reducing friction.
Higher revenue per merchant: the spread on interchange is significantly larger than ISO residuals for high-volume sub-merchants.
Full UX control: you own the checkout, dashboard, and reconciliation experience — no redirects to a third-party processor UI.
Embedded finance foundation: once you are a PayFac, adding lending, cards, and banking features is much easier.

PayFac — Cons

Risk and liability: you absorb chargeback and fraud losses that any sub-merchant cannot cover. A single bad actor can create significant exposure.
Compliance overhead: card network registration, PCI DSS Level 1, KYB/AML programmes, and ongoing monitoring are mandatory.
Capital requirement: acquirers often require a rolling reserve (typically 5–10% of processing volume held for 90–180 days).
Build cost: a full PayFac build is a 12–18 month, multi-million dollar programme. PayFac-as-a-Service providers (Stripe, Finix, Payrix) shorten this considerably but take a cut of revenue.

ISO — Pros

Low barrier to entry: no reserves, no direct liability for chargebacks, lighter compliance posture.
Proven economics: residual income is predictable and compounds as the merchant portfolio grows.
No technology build: the processor provides the gateway, reporting, and terminal infrastructure.

ISO — Cons

Slow onboarding: bank underwriting takes days or weeks — a major friction point in a self-serve SaaS context.
Limited UX control: merchants often interact directly with the processor’s portal, diluting your brand.
Lower revenue ceiling: residuals are a fraction of the spread a PayFac earns.

PayFac vs ISO: Which Model Should You Choose?

The right choice depends on three variables: merchant volume, technical capacity, and risk appetite.

Choose a PayFac model if: you are a vertical SaaS platform or marketplace with hundreds or thousands of SMB customers, you want frictionless in-product onboarding, and you have (or can build) the engineering and compliance infrastructure to support it. Even if a full PayFac build is too expensive, a PayFac-as-a-Service platform (Stripe Connect, Finix, Payrix) delivers most of the UX benefits without the full regulatory burden.

Choose an ISO model if: you are primarily a sales organisation acquiring merchants in person or via a broker channel, onboarding speed is not a critical competitive differentiator, and you want to minimise capital and compliance exposure. ISOs work well for independent agents, regional acquirers, and distribution-led businesses.

Many platforms start as an ISO to move quickly, then migrate to PayFac (or PayFac-as-a-Service) as volume and margin pressure makes the upgrade worthwhile. The tipping point is typically around $10–20M in annual processing volume, where the spread advantage of the PayFac model starts to meaningfully outperform ISO residuals.

PayFac vs ISV: Where Software Platforms Fit

An ISV (independent software vendor) is not a payment role like a PayFac or an ISO. It is a type of business: a software company, such as a salon booking tool, property management system, or field-service app, whose customers need to accept payments. The real question for an ISV is which payment model to adopt. There are three:

Model	How it works	Revenue for the ISV	Risk and liability	Time to launch
Referral partner	The ISV refers its customers to a processor or ISO, which signs them up directly	Low (small revenue share)	None	Days
Managed PayFac (PayFac-as-a-Service)	Payments are embedded in the software through a platform such as Stripe Connect, Adyen for Platforms, or Finix; the provider remains the PayFac	Medium (share of processing margin)	Mostly carried by the provider	Weeks
Full PayFac	The ISV registers with the card networks and owns underwriting, onboarding, and risk	High (full spread on processing)	Carried by the ISV	6–18 months

Most ISVs start with a referral or managed PayFac model and only become a full PayFac once processing volume is large enough to justify the compliance, reserves, and risk operations. For a deeper look at the PayFac model itself, see What Is a Payment Facilitator?

ISO vs PayFac vs Payment Orchestrator

A payment orchestrator is often confused with both, but it plays a different role. ISOs and PayFacs determine who owns the merchant relationship and who carries liability. A payment orchestrator is a routing layer that sits on top of one or more processors or PayFacs and decides where each transaction goes: which processor, which retry path, which fallback when a provider is down. An orchestrator does not onboard merchants or hold a merchant ID. A business can use an orchestrator regardless of whether its merchant accounts come from an ISO, a PayFac, or a direct acquirer. More on this in What Is Payment Orchestration?

PayFac-as-a-Service: The Middle Ground

Since 2018, a third category has emerged: PayFac-as-a-Service (PFaaS). Providers like Stripe Connect, Finix, Payrix, and WePay (Chase) allow platforms to offer instant sub-merchant onboarding and embedded payments without registering as a full PayFac themselves. The PFaaS provider holds the master MID and manages compliance; the platform gets the UX and a share of the revenue.

PFaaS is now the default choice for most early-stage and growth-stage platforms that want PayFac economics without the capital and compliance investment of building in-house.

PayFac vs ISO: Key Takeaways

In PayFac vs ISO, the core difference is who holds the merchant account: the PayFac, or each merchant.
A PayFac offers instant onboarding and more revenue, but carries more risk and compliance work.
An ISO is lighter to run, but merchants onboard more slowly and the ISO earns less.
PayFac-as-a-Service is the middle ground in the PayFac vs ISO decision for most growing platforms.

Frequently Asked Questions: PayFac vs ISO

What is the main difference between a PayFac and an ISO?

A PayFac holds a master merchant account and onboards sub-merchants under it — making the PayFac the merchant of record and financially responsible for sub-merchant chargebacks and fraud it cannot recover. An ISO resells individual merchant accounts issued by a bank; each merchant gets their own MID the merchant is liable for its own chargebacks, with the acquiring bank as backstop.

Is Stripe a PayFac or an ISO?

Stripe operates as a PayFac (Payment Facilitator). When businesses sign up for Stripe, they become sub-merchants under Stripe’s master merchant account. Stripe is the merchant of record, handles underwriting, and is liable for chargebacks its sub-merchants cannot cover.

Do I need to register with Visa and Mastercard to become a PayFac?

Yes. Visa and Mastercard both require Payment Facilitators to register with them directly. Visa calls this the PFAC (Payment Facilitator) programme; Mastercard has a similar PayFac registration. Registration involves fees, compliance attestations, and ongoing reporting requirements.

Can an ISO become a PayFac?

Yes, and many do. The transition typically involves signing a new master merchant agreement with an acquiring bank, registering with card networks, building or buying underwriting and risk infrastructure, and setting up a reserve account. It is a significant investment but unlocks considerably higher economics at scale.

What is the difference between a PayFac and a PSP?

The terms are often used interchangeably, but there is a technical distinction. A PSP (Payment Service Provider) is the broader category — any company that provides payment processing services. A PayFac is a specific type of PSP that holds a master merchant account and onboards sub-merchants. All PayFacs are PSPs, but not all PSPs are PayFacs.

What is the difference between an ISV and a PayFac?

An ISV is a software company whose customers need to take payments. A PayFac is a payment role: a company that holds a master merchant account and onboards sub-merchants under it. An ISV can partner with a PayFac, use a managed PayFac platform, or become a PayFac itself.

Is a PayFac better than an ISO?

Neither is better in general. A PayFac model suits platforms that want instant onboarding, control over the payment experience, and a larger share of processing revenue, and that can carry the risk. An ISO model suits sales-led businesses that want recurring residuals without owning underwriting or chargeback liability.