Resource · Comparison
PayFac vs. ISO: Which Model Fits Your Platform?
A PayFac holds a master merchant account and boards businesses as sub-merchants under it, owning their underwriting, risk, and more of the economics. An ISO resells and refers merchants to a processor, where each gets their own account and the processor holds the risk. The PayFac model gives more control and revenue but requires registration, sponsorship, and a compliance build; the ISO model is lighter but earns less. PayFac-as-a-Service is the middle path.
Same goal, two very different machines
If your platform wants to make money on payments, you'll quickly run into two acronyms, PayFac and ISO, that describe fundamentally different ways to get there. They're easy to blur together because both put a platform between merchants and a processor. But the difference comes down to one question: do you hold the merchant relationship and its risk, or do you refer it to someone who does? Everything else, the economics, the compliance burden, the control, follows from that single split.
Getting the choice right matters, because it shapes your build, your liability, and your revenue for years. The good news is that the decision is fairly legible once you see what each model actually requires.
The ISO model: refer and stay light
An ISO (independent sales organization) is, at its core, a reseller. It markets merchant accounts, signs merchants up, and refers them to a processor, but each merchant gets its own merchant account, and the processor holds the risk. The ISO earns referral or residual income on the volume it brings in. The appeal is the low overhead: no card-network registration to maintain, no sub-merchant underwriting to perform, no liability for a merchant's chargebacks. The trade-off is less control over the experience and a thinner slice of the economics. For a platform that wants payments revenue without becoming a risk-bearing entity, the ISO path is the lighter lift.
The PayFac model: aggregate and own it
A PayFac (payment facilitator) does the opposite. It holds a master merchant account, boards businesses as sub-merchants under it, and takes on their onboarding, underwriting, and risk itself. Because it owns the relationship, it controls the merchant experience, including instant onboarding, and captures more of the processing margin on every transaction. The price of that control is real: card-network registration, a sponsor bank's concurrence, a full KYC and risk-monitoring build, and liability for its sub-merchants' activity. The PayFac is doing work a bank used to do, and it carries the corresponding responsibility. (For the mechanics, see what is a payment facilitator.)
Side by side
| ISO | PayFac | |
|---|---|---|
| Merchant accounts | Each merchant gets their own | Sub-merchants under one master account |
| Who holds the risk | The processor | The PayFac |
| Onboarding speed | Standard underwriting | Can be instant (sub-merchant boarding) |
| Economics | Referral / residual share | Larger share of processing margin |
| Compliance build | Minimal | Registration, sponsorship, KYC, monitoring |
| Liability | Low | Significant |
| Best when | You want payments revenue, low overhead | You want control + margin at scale |
How to decide, and the third path
The honest decision rule is about scale and appetite. If you have the volume to justify the build and you want to own the payment experience and capture more margin, the PayFac model wins, its margin advantage compounds as you grow. If you'd rather avoid holding risk and the registration burden, and your volume is modest, the ISO model's low overhead can be the better net outcome.
But most platforms today don't pick a pure version of either. They take the middle path: PayFac-as-a-Service, which hands a platform the economics and merchant-experience control of a PayFac while a provider carries the card-network registration, sponsor relationship, and risk infrastructure. You act like a PayFac without spending years building one. If that sounds like your situation, see PayFac-as-a-Service, or if the referral model fits better, our ISO & agent program. Either way, talk to our platform team and we'll help you map the right one.
FAQ
PayFac vs. ISO FAQ
What's the difference between a PayFac and an ISO?
A PayFac (payment facilitator) holds a master merchant account and boards businesses as sub-merchants under it, taking on their underwriting and risk and keeping more of the processing economics. An ISO (independent sales organization) resells and refers merchants to a processor, where each merchant gets their own account and the processor holds the risk. In short: a PayFac aggregates and owns the risk; an ISO refers and doesn't. The PayFac model gives more control and revenue but requires registration, sponsorship, and a compliance build.
Should my platform be a PayFac or an ISO?
It depends on scale, control, and appetite for risk. If you want to own the payment experience, board sub-merchants instantly, and capture more margin, and you have the volume to justify the compliance build, the PayFac model (or PayFac-as-a-Service) fits. If you'd rather refer merchants and avoid holding risk and the registration burden, the ISO model is lighter. Many platforms start with PayFac-as-a-Service to get PayFac economics without building the full infrastructure themselves.
Is PayFac-as-a-Service a third option?
Effectively, yes, it's the middle path. PayFac-as-a-Service gives a platform the economics and merchant-experience control of a PayFac while a provider handles the card-network registration, sponsor relationship, and risk infrastructure. It lets a platform act like a PayFac without the multi-year build and ongoing compliance burden, which is why it's the most common way platforms enter payments today.
Which model makes more money?
The PayFac model generally captures more of the processing economics per transaction because the PayFac owns the relationship and the pricing, but it also carries the cost of compliance, risk, and the build. An ISO earns referral or residual income with far lower overhead and no risk exposure. So 'more money' depends on volume: at scale a PayFac's margin advantage compounds; below that, the ISO model's low overhead can be the better net outcome.
Not sure which model fits your platform?
Our platform team maps PayFac, ISO, and PayFac-as-a-Service against your volume, control, and risk appetite.