PayFac vs ISO
Definition
A PayFac (payment facilitator) owns the merchant relationship and onboards sub-merchants under its master MID, while an ISO (independent sales organization) acts as a sales agent referring merchants to a processor. PayFacs earn more per transaction but carry compliance and fraud liability; ISOs earn residual income with minimal operational overhead.
How It Works
A PayFac registers as a master merchant with a sponsoring bank and onboards businesses as sub-merchants — handling KYC/KYB, pricing, settlement, and compliance. The PayFac earns 60-100+ basis points per transaction. An ISO has a contractual relationship with a processor or acquiring bank to refer merchants. The processor handles underwriting and owns the merchant relationship. The ISO earns 10-30 basis points in residual income on referred volume.
Why ISVs Care
The PayFac model (or PayFac-as-a-Service) lets ISVs embed payments natively, control the merchant experience, and earn significantly higher per-transaction revenue. The ISO model is simpler to set up with lower risk, but offers less integration depth and weaker merchant lock-in. Most growth-stage ISVs choose a PFaaS provider (Finix, Tilled, Xplor Pay, Stripe Connect) that gives PayFac economics without full registration requirements.
The PayFac (Payment Facilitator) and ISO (Independent Sales Organization) models represent two fundamentally different approaches to how software companies can offer payment processing to their customers.
Understanding the distinction is critical for ISVs evaluating their payment strategy — it affects your revenue model, compliance obligations, merchant experience, and technical architecture.
The Core Difference
A PayFac is a master merchant that onboards sub-merchants under its own merchant ID. The PayFac owns the merchant relationship, controls pricing, and is liable for sub-merchant activity.
An ISO is a sales agent that refers merchants to a processor or acquiring bank. The bank owns the merchant relationship, handles underwriting, and carries the compliance burden. The ISO earns residuals on referred merchant volume.
For ISVs, This Distinction Matters Because:
- Onboarding speed: PayFac enables instant merchant activation within your software. ISO requires a separate application process that takes days.
- Revenue potential: PayFacs earn 60-100+ bps per transaction. ISOs typically earn 10-30 bps in residuals.
- User experience: PayFac = payments embedded in your software. ISO = a referral to an external payment provider.
- Liability: PayFac carries fraud and chargeback risk. ISO does not.
The Middle Ground: PayFac-as-a-Service
Most ISVs don’t need to choose between full PayFac registration and an ISO arrangement. PayFac-as-a-Service providers (Finix, Tilled, Xplor Pay, Stripe Connect) offer PayFac-like capabilities — fast onboarding, embedded experience, revenue sharing — without requiring your ISV to become a registered PayFac.
This is the path most growth-stage ISVs take: PFaaS economics with shared compliance responsibility.