The ISO-to-ISV Shift: Why Payments Companies Are Becoming Software Companies

The Traditional ISO Model Is Under Pressure

For decades, ISOs built their businesses on a straightforward model: sign merchants, place them with a processor, collect residuals. It worked because merchants needed someone to navigate the complexity of payment acceptance.

That model is now being squeezed from both sides. Square, Stripe, and Toast made self-service onboarding trivial for small merchants. Meanwhile, larger merchants increasingly expect software-integrated payments — not standalone terminals and separate portals.

The result: the pure-play ISO that only sells processing is becoming a commodity. The ISOs growing fastest are the ones adding software to the equation.

What the ISO-to-ISV Transition Actually Looks Like

An ISV (Independent Software Vendor) builds or owns software that merchants use to run their business — point of sale, inventory management, appointment scheduling, invoicing. Payments are embedded inside that software, creating a seamless experience for the merchant and a stickier, higher-margin relationship for the company.

The transition from ISO to ISV typically follows one of three paths:

1. Build. Develop proprietary software for a vertical you already serve well. This is the highest investment but offers the most control. David Robinson of MyDevTeam estimates a serious vertical SaaS build requires $200K-$500K and 12-18 months to reach market-ready state.
2. Buy. Acquire an existing software company in your target vertical. Faster to market but requires capital and integration expertise. Many ISOs are taking this route with SBA loans or private equity backing.
3. Partner. White-label or deeply integrate with existing software providers. Lower risk and investment, but less differentiation. This is the entry point for most ISOs exploring the transition.

Why Valuations Change Everything

Here’s the number that drives the ISO-to-ISV transition: valuation multiples. A traditional ISO portfolio typically sells for 3-5x annual residuals. A software company with embedded payments sells for 10-20x annual revenue.

That’s not a marginal improvement — it’s a fundamentally different business. An ISO generating $2M in annual residuals might sell for $8-10M. The same revenue wrapped in proprietary software could be worth $20-40M.

The economics also improve on a per-merchant basis. Software subscription fees plus embedded payments revenue typically generate 3-5x more per merchant than processing alone, with significantly lower churn because merchants are locked into the software workflow.

The Role of AI in Accelerating the Shift

Artificial intelligence is lowering the barrier to software development. ISOs that previously couldn’t afford to build custom vertical software are now using AI-assisted development to create MVPs faster and cheaper. But the real opportunity isn’t just building software — it’s using AI to make the payments operation itself more intelligent.

Automated merchant profiling, intelligent processor matching, and predictive portfolio analytics are capabilities that used to require large engineering teams. Platforms like Twill embed this intelligence directly into the ISO workflow, giving smaller organizations the operational leverage of much larger competitors.

Getting Started

You don’t need to become a software company overnight. The most successful transitions start with identifying the vertical where you have the deepest expertise, mapping the software tools your merchants already use, and finding the integration points where embedded payments add the most value.

The ISOs that will thrive in the next decade are the ones that think of themselves as technology companies that happen to process payments — not payments companies that happen to use technology.