If you run a SaaS and you're trying to figure out how to monetize payments, "ISO vs. ISV" is probably the first comparison you ran into. It's also the wrong place to stop.

The honest answer is that ISO vs. ISV is a 2012 question. The roles are still defined and worth understanding, but the modern decision for a software platform isn't really between them. It's about where you sit on a four-role spectrum that also includes the full PayFac model and PayFac-as-a-Service (PFaaS). Pick wrong and you either leave significant revenue on the table or take on compliance overhead your business doesn't need yet.

Bain & Company estimates that up to $35 trillion in payments could be addressed annually by independent software vendors worldwide, or roughly 15% of all payments globally. Every basis point your platform routes through your product is a real revenue line. The question is which model captures the most of it without burying you in compliance.

Here's the full picture.

What is an ISO?

An independent sales organization (ISO) is a third-party reseller that partners with an acquiring bank or processor to sell merchant accounts. The ISO's job is essentially distribution: sign up merchants, hand them off to the processor, and collect a residual on every transaction those merchants run.

ISOs don't hold funds. They don't own the merchant relationship at the product level. They don't carry chargeback risk. And they don't typically own the user experience, since the merchant interacts with the processor's tools rather than the ISO's.

Residuals on established portfolios usually land somewhere between 5 and 15 basis points. Setup is fast (a few weeks), and the compliance burden is light. For a SaaS platform considering this route in 2026, the question to ask is whether collecting referral economics on transactions you don't influence is really the model you want.

What is an ISV?

An independent software vendor (ISV) builds and sells software. In a payments context, that means a SaaS or vertical software platform that embeds payment processing into the product itself. A gym software's customers run cards through the gym software. A construction platform's GCs collect from owners through the construction platform. The merchant never leaves your product.

ISVs own the customer relationship and the product experience. They make money two ways: subscription revenue from the software, plus a share of the processing margin from a payments partner. Under a flat-rate partner model, that share typically runs in the 10 to 25 basis-point range, with integration timelines of a few weeks to a couple of months.

This is where most SaaS platforms start. It's also where most platforms hit a ceiling, since flat-rate economics are easy to set up but built to favor the processor, not you.

Where PayFac and PayFac-as-a-Service come Iin

Here's the part the standard ISO vs. ISV comparison misses.

Once a software platform starts processing meaningful volume, the next decision isn't whether to "stay" an ISV. It's how to operate as one. There are two paths beyond the flat-rate ISV model.

Full PayFac (Payment Facilitator)

A PayFac holds its own master merchant account and onboards sub-merchants underneath it. The PayFac owns the entire stack: underwriting, KYC/AML, settlement, risk, chargeback ops, and merchant experience. In exchange, it captures the full processing margin, typically 100 to 200 basis points before operating costs.

The catch is the lift. Setup runs 6 to 24 months and requires acquirer sponsorship, PCI DSS Level 1 certification, money transmitter licensing across most US states, and reserve capital. According to the Conference of State Bank Supervisors, 49 states plus DC require money transmitter licenses, with aggregate capital requirements that can run into the millions. Annual maintenance for a registered PayFac sits at $100K and up once you account for compliance staff, card-network reporting, and chargeback operations.

It's a serious commitment. And it makes financial sense (a $500K+ payback often clears full PayFac economics) but only above roughly $500M in annual GPV with a dedicated payments team.

PayFac-as-a-Service (PFaaS)

PayFac-as-a-Service lets a platform operate under an established PayFac's master merchant account without registering as one itself. You get interchange-plus pricing, meaningful revenue share, and control over merchant onboarding inside your product. Your partner handles acquirer sponsorship, card-network reporting, PCI Level 1, and capital reserves.

Revenue share for PFaaS typically runs 60 to 100 basis points, three to four times what flat-rate ISV economics deliver. Launch timelines compress to a few months instead of a year-plus. And you skip the upfront capital and ongoing compliance overhead entirely.

For platforms processing roughly $10M to $500M in annual GPV, this is almost always where the math works best.

Side-by-side: How the four roles compare

The picture this paints isn't really "ISO vs. ISV." It's a progression. Most modern SaaS platforms aren't choosing between ISO and ISV. They're choosing between flat-rate ISV partnerships, PFaaS, and (eventually) full PayFac registration.

Why most SaaS platforms land at PFaaS

The gap between flat-rate ISV economics and full PayFac registration is enormous, and most platforms outgrow the former long before they can justify the latter.

Consider a platform processing $50M in annual GPV. Under flat-rate ISV economics, it might earn $50K to $125K annually from payments. Under PFaaS, the same volume could generate $300K to $500K. Full PayFac in best-case scenarios clears closer to $1M, but with $100K to $750K in operating cost, dedicated headcount, and 12 to 24 months of build time before the first dollar lands. The marginal revenue rarely pencils until volume is substantially higher.

PFaaS captures most of the margin at a fraction of the overhead. That's why it's the answer for the broad middle of the SaaS market, and why the legacy ISO vs. ISV framing leaves so much money on the table.

Choosing the model that fits your platform

The practical decision usually comes down to three inputs: annual GPV, how strategic payments is to your business model, and your tolerance for compliance overhead.

If you're under $10M GPV and payments isn't core to your product yet, an ISV flat-rate partnership is the right place to start. The economics are modest, but the integration is fast and you're not over-investing in something that hasn't proven out.

If you're between $10M and $500M GPV and treating payments as a real revenue line, PFaaS is almost certainly the answer. You get interchange-plus economics, control over the merchant experience, and a launch timeline measured in months, without the registration weight of full PayFac.

If you're processing $500M+ GPV and either have or can fund a dedicated payments and compliance team, full PayFac becomes worth modeling seriously. Below that, the math doesn't clear.

How Coinflow closes this gap

For ISV platforms past flat-rate economics but not ready to take on the full PayFac compliance burden, Coinflow is built specifically for this gap.

Coinflow Launchpad delivers interchange-plus pricing, revenue share that's roughly 30% above what flat-rate processors return, and instant settlement powered by stablecoin rails. That means your sub-merchants get same-transaction access to funds instead of waiting two to three days.

We handle PCI DSS Service Provider Level 1, SOC 2, and embedded AML/KYC, so your engineering team stays focused on your product. Setup fees are zero, and pricing scales with your growth.

If you're trying to figure out which role fits your platform, schedule a call and we'll model it out with you.