If you're a software company looking to monetize the payment volume flowing through your platform, you'll eventually encounter two terms: Payment Facilitator (PayFac) and Independent Sales Organization (ISO). Both are structures for participating in the economics of payment processing. But they work differently, carry different revenue potential, and suit different stages of business.
Most of the content explaining these models is written by companies that sell one of the two. That's a problem, because the answer isn't which model is better — it's which model matches where you are right now and how much of the payment margin you're ready to capture.
What an ISO Actually Does
An Independent Sales Organization is a registered entity that refers merchants to a payment processor. The ISO doesn't process payments itself. It acts as a distribution channel — finding merchants, boarding them onto a processor's platform, and earning a residual on the processing volume those merchants generate.
For a software company, the ISO path usually takes the form of an ISV Referral program. You partner with a processor (Fiserv, Worldpay, Global Payments, or others), embed their payment acceptance into your product via APIs, and earn a revenue share on merchant volume. The processor handles underwriting, compliance, settlement, risk management, and merchant support.
The economics are straightforward: you earn 5 to 25 basis points on gross volume, depending on the processor and your negotiating position. On $30 million in annual merchant volume, that's $15,000 to $75,000 per year. Essentially free money — you carry no operational burden and no risk exposure.
The trade-off is equally straightforward: you don't control the merchant experience, you don't own the merchant relationship in payments terms, and you're earning a fraction of the total margin on each transaction.
What a Payment Facilitator Does
A Payment Facilitator is a registered entity that aggregates merchants under its own merchant ID. Instead of referring merchants to a processor, the PayFac boards merchants as sub-merchants, underwrites them (within parameters set by the acquiring bank and card networks), manages compliance, handles disputes, and processes payments on their behalf.
The PayFac owns more of the stack — and earns more of the economics. Instead of collecting a residual, you set the merchant rate, buy processing at wholesale (interchange plus a processor spread), and keep the difference. Net margins typically range from 30 to 90+ basis points depending on volume, vertical, and how you've structured your pricing.
On that same $30 million in volume, PayFac economics produce $90,000 to $270,000 in annual net revenue. The ceiling is meaningfully higher.
The trade-off: you're now responsible for merchant onboarding, KYC/AML compliance, transaction monitoring, reserve management, chargeback response, and regulatory reporting. You need staff — or a managed service provider — who understands payment operations. Implementation costs range from $50K for managed PayFac services to $500K+ for a full direct registration.
The Economic Comparison
The math is simple but often ignored. Here's a side-by-side at three volume levels:
At $10M annual volume: ISO earns $5K–$25K. PayFac earns $30K–$90K.
At $50M annual volume: ISO earns $25K–$125K. PayFac earns $150K–$450K.
At $100M annual volume: ISO earns $50K–$250K. PayFac earns $300K–$900K.
The gap widens with every dollar of volume. At smaller scales, the ISO model is efficient — you're earning revenue with no operational cost. As volume grows, the opportunity cost of staying in ISO becomes the dominant factor.
When to Choose the ISO / Referral Path
The ISO model is right when your payments volume is under $30–50 million annually, you have fewer than 200 merchants processing, your team has no payments operations experience, or you're early enough in your product lifecycle that payments is a feature, not a business line.
It's also the right choice if your vertical carries elevated risk — high average ticket sizes, high chargeback rates, or regulatory complexity. In those cases, letting the processor carry the risk exposure is worth the economic trade-off.
The ISO model lets you generate payments revenue in weeks rather than months, with minimal implementation cost and zero ongoing operational burden. For many platforms, this is the correct starting point.
When to Choose the PayFac Path
PayFac economics become compelling when your annual merchant volume exceeds $50 million and is growing, you have 150+ merchants processing consistently, you can staff at least one person who understands payment operations (or you're willing to use a managed PayFac service), and the checkout and payment experience is core to your product differentiation.
The managed PayFac model — sometimes called PayFac-as-a-Service or PayFac Lite — has made this path accessible to platforms that previously couldn't afford or staff a full PayFac registration. You get most of the economics with a fraction of the operational burden.
The Migration Question
Can you start as an ISO and move to PayFac later? Yes. Many platforms do. The transition involves re-boarding merchants under new agreements, which creates some operational friction and occasional churn. Plan for 3–6 months of migration work depending on merchant count.
The smart approach: if you have any visibility into your volume trajectory, choose your initial ISO partner with future migration in mind. Some processors offer a clear path from referral to their own managed PayFac program. Others make migration deliberately difficult. Ask about the migration path before you sign your first referral agreement.
The Decision That Matters More Than the Model
The most common mistake is treating ISO vs. PayFac as a permanent, binary choice rather than a stage-appropriate one. Companies get comfortable in referral programs, the residuals start to feel meaningful, and they stop evaluating whether they've crossed the threshold.
Run the math annually. The economics shift faster than most teams realize, especially in high-growth verticals where merchant count and average volume are both increasing.
The right model today should match where you are. The mistake is staying in it after you've outgrown it.
The Margin Multiplier models revenue across all four embedded payments approaches — ISV Referral, Enhanced Residuals, PayFac Lite, and Full PayFac — in about 60 seconds. Start there if you want to see where you fall.