Almost every fintech founder or ISO principal we advise reaches the same fork in the road: build a Payment Facilitator (PayFac) model, or stay an Independent Sales Organization (ISO) referring merchants into an acquirer’s platform. The two models look similar from the outside — both put you between a merchant and card acceptance — but the licensing burden, balance-sheet exposure, and margin profile are fundamentally different. Getting this decision wrong is expensive to unwind once merchants are onboarded.
What Actually Separates a PayFac From an ISO
An ISO refers or resells an acquirer’s merchant services under the acquirer’s own merchant agreements — the acquirer underwrites, boards, and holds the compliance obligation for every sub-merchant. A PayFac, by contrast, signs merchants under its own master merchant agreement with a sponsoring bank or acquirer, and takes on the underwriting, KYB, monitoring, and — critically — the liability for those sub-merchants’ chargebacks and fraud.
- Speed to onboard is the PayFac’s headline advantage — merchants can be live in minutes rather than days, because the PayFac owns the underwriting decision instead of routing it to a bank.
- Balance sheet exposure shifts to the PayFac — reserves, chargeback liability, and fraud losses sit with you, not the sponsor bank.
- Regulatory and scheme obligations multiply under a PayFac model — Visa and Mastercard registration, PCI DSS Level 1 obligations at scale, and ongoing sponsor bank oversight all apply.
Where the Economics Genuinely Favour Each Model
ISOs earn residual income on a stable, largely passive revenue share — attractive if your core business is elsewhere and payments is a value-add, not the product. PayFacs capture significantly more margin per merchant because they control pricing, but that margin has to fund underwriting infrastructure, a risk team, reserve capital, and sponsor bank fees that scale with volume, not just merchant count.
We generally steer clients toward the PayFac model only once they can show a repeatable, technology-driven onboarding flow across a reasonably homogeneous merchant base — vertical SaaS platforms embedding payments are the clearest case. A diverse, high-risk merchant mix without a clear underwriting thesis is exactly where PayFac economics break down.
“The PayFac model doesn’t fail because the licensing is hard — it fails when a business becomes a PayFac before it has the underwriting discipline to be one.”
The Sponsor Bank Relationship Is the Real Gatekeeper
Neither model happens without a sponsor bank or acquirer willing to carry the risk behind you. ISOs need an acquirer with the right vertical appetite and competitive residual splits. PayFacs need a sponsor bank comfortable with the underwriting framework, reserve methodology, and monitoring tooling you propose — and that conversation goes considerably better with a well-documented risk framework already in hand, rather than a plan sketched during the application.
What We Recommend Before You Commit to Either Model
- Map your target merchant base’s risk profile honestly before choosing — a PayFac model on a high-risk, undifferentiated portfolio invites reserve and chargeback problems fast.
- Model the true cost of underwriting, monitoring, and compliance infrastructure against the incremental margin a PayFac structure actually delivers.
- Engage sponsor bank conversations early — their risk appetite, not your preference, ultimately determines what’s achievable.
- Consider a hybrid path: start as an ISO to prove merchant demand, then transition to PayFac once volume and underwriting data justify the infrastructure spend.