The ISO vs. Vertical SaaS War Has Begun: Restaurants, Healthcare, Auto Repair

What Is the Vertical SaaS War — and Why Is It Happening Now

For most of the ISO industry’s history, competition was horizontal: ISOs competed with each other on processing rates, service quality, and terminal availability. The competitive battlefield was the same regardless of the merchant — restaurant, retailer, service business — and the switching cost was low because the relationship was defined by a rate, not by a workflow. That structure is breaking apart, and the force breaking it is vertical SaaS.

Vertical SaaS platforms are industry-specific software companies that embed payments into a workflow merchant already uses. Toast owns the restaurant’s ordering, kitchen display, and inventory system — and processes payments as a feature of that workflow. Jane App owns the therapist’s appointment scheduling, clinical notes, and client billing — and handles payment as part of the booking flow. ShopWare owns the auto repair shop’s job tracking, parts ordering, and invoicing — and collects payment when the invoice is generated. None of these companies started as payment companies. They started as workflow companies that made payments invisible by making them automatic.

The result is a form of competitive disintermediation that rate competition cannot counter. A restaurant owner who runs Toast does not think about their payment processor — they think about their POS system. The payment is embedded in a workflow the merchant depends on for daily operations, which means switching the payment processor requires switching the operating system. The switching cost is no longer 5 basis points — it is the entire operational infrastructure of the business. ISOs that have not yet been affected by this dynamic are not in a safe position. They are in a waiting position.

1. The Three Verticals Under Active Attack

Restaurants — Toast has already won this battle: Toast is not trying to win the payment processing market from the outside. It won by owning the restaurant workflow — table management, kitchen display, online ordering, inventory — and making payment a feature of that system. A restaurant on Toast does not shop for a payment processor; they use the system they already run their business on. Toast’s embedded payments now process billions in volume annually, and the ISO that was previously the restaurant’s payment provider is a distant second — or gone. The lesson from restaurants is not that ISOs lost. It is that they lost because they never owned the workflow.

Healthcare and wellness — Jane App and the scheduling lock: Therapist, counselor, and health practice scheduling platforms have followed the same playbook. Jane App, SimplePractice, and similar platforms own the appointment scheduling, client intake, clinical notes, and billing workflow for tens of thousands of health providers. When a therapist books a session through Jane App, payment is collected as part of the booking flow. The provider never thinks about their payment processor — they think about their scheduling system. ISOs serving health providers are experiencing the same disintermediation dynamic as restaurants, just on a slower timeline. The timeline is not an excuse. The same structural logic applies.

Auto repair and trades — the job-costing invasion: Auto repair shops and trades businesses — HVAC, plumbing, electrical — are being targeted by vertical platforms built for their specific workflows. ShopWare and similar platforms offer job costing, parts ordering, work order management, and invoicing — and embed payment collection in the invoice. The merchant who manages their entire job in the platform has no reason to use a separate payment processor. This vertical is earlier in its SaaS adoption curve than restaurants or healthcare, which means the window to own the workflow before a vertical SaaS incumbent does is still open — but it is closing.

2. Why Workflow Ownership Beats Rate Competition Every Time

Rate competition assumes the merchant is shopping for rates: The entire ISO sales model — identify a merchant, propose a rate, win the business — is predicated on the merchant actively comparing payment processors. Vertical SaaS platforms eliminate this behavior by making payment invisible. A merchant on Toast does not compare payment rates because they do not experience payment as a separate decision. It is a feature of their scheduling and ordering system. The competitive dynamic that ISOs have optimized for — rate selling — does not exist in a vertical SaaS relationship, which means ISOs selling on rate are optimizing for a market that is shrinking.

Switching cost is no longer 5 basis points: In a rate-competition world, the switching cost is low — the merchant finds a better rate, signs new paperwork, swaps a terminal configuration, and done. In a workflow-ownership world, the switching cost is the entire operational infrastructure of the business. Switching payment processors in Toast means switching POS systems, re-entering menu items, retraining staff, and rebuilding the kitchen display configuration. A merchant who saves 10 basis points by switching to a different processor still has to run their restaurant. They will not do it. The ISO that was competing on rate has already lost the moment the merchant adopted the vertical SaaS platform — they just have not sent the cancellation notice yet.

The ISO is disintermediated before they know it: What makes the vertical SaaS threat so dangerous is that the ISO may not realize they have been disintermediated until the damage is structural. A merchant may continue to use the ISO’s processing for months after adopting a vertical SaaS platform, which creates a false sense of relationship security. The ISO’s volume is stable, the merchant is nominally active, and there is no immediate crisis. Then, at the next renewal, the ISO discovers that the merchant has embedded the vertical SaaS payment into their workflow — and the renewal conversation is not about rate. It is about switching an operating system. By then, it is too late.

3. The ISO Response: Pre-Emptive Workflow Ownership

Own the workflow before vertical SaaS does: The most effective defense against vertical SaaS disintermediation is to be the platform that owns the merchant’s workflow before a vertical SaaS competitor arrives. This means deploying a white-label POS and software platform — not just a terminal — at the point of merchant onboarding. The ISO who owns the platform owns the relationship, the data, and the switching cost. Merchants who run their operations on the ISO’s platform do not shop for Toast or Jane App because they are already running their business on a system that does everything they need.

Prioritize verticals where the window is still open: In restaurants, the window for ISOs to own the workflow is narrow — Toast has already won significant market share. In healthcare and auto repair, the window is wider but closing. ISOs should conduct a vertical-by-vertical assessment of where vertical SaaS incumbents have already achieved workflow lock, where they are gaining, and where the field is still open. The open fields — early-adoption verticals, underserved industries, emerging market segments — are where pre-emptive workflow ownership has the highest return.

Convert existing processing-only merchants before they are approached: For the existing processing-only merchant base, the priority is accelerating the move onto the ISO’s software platform before a vertical SaaS vendor makes contact. This is a sales motion — not a renewal conversation — and it requires a different pitch: not “save on rates,” but “build the operational infrastructure of your business with a platform that grows with you.” The ISO that brings a merchant onto their platform in Q1 owns that merchant’s workflow for the next three to five years. The ISO that waits for the merchant to be approached by a vertical SaaS company in Q3 is already behind.

Specialize in vertical-specific integrations: ISOs that serve healthcare merchants should have integrations with the scheduling and practice management systems their merchants use. ISOs serving restaurants should have ordering, inventory, and kitchen display integrations. ISOs serving auto repair should have job-costing and parts database integrations. The ISO that integrates deeply into the vertical-specific workflows that merchants depend on is the ISO that cannot be easily disintermediated — because the switching cost includes not just the POS but also the integrated systems that run the business.