Why Every Merchant Services Company Needs a Formal ISV Strategy Before 2030

What Is a Formal ISV Strategy — and Why Does 2030 Matter

A formal ISV strategy is a documented plan that defines how a merchant services company will transition from a payment processing business to a software-enabled payments business. It specifies the verticals the company will target, the platform approach it will take (build, acquire, or partner), how payments will be embedded into software workflows, what revenue model will replace or supplement pure processing revenue, and how the company will measure and report its software penetration to investors, acquirers, and internal stakeholders. It is a strategic document — not a product roadmap — but it drives every product, sales, and partnership decision the company makes.

The 2030 deadline is not arbitrary. It reflects the convergence of three structural forces that are already reshaping the industry: vertical SaaS platforms with embedded payments are reaching scale in multiple verticals simultaneously; merchants are increasingly adopting software platforms that include payment processing as a feature rather than a separate procurement decision; and investors and acquirers are pricing ISOs on software penetration rather than processing volume. By 2030, these forces will have progressed far enough that an ISO without a formal ISV strategy will find its distribution channels, merchant relationships, and revenue model fundamentally altered — and not in its favor.

The practical implication is that the strategy needs to be in place by 2027-2028 to allow execution time before the market restructuring is complete. A strategy documented in 2028 and executed over 24-36 months gives the ISO a platform, a vertical focus, and a software-penetrated merchant base by 2030. A strategy first attempted in 2030 is a reaction to a market that has already moved — and the ISO will be executing from a position of weakness, not strength.

1. Pillar One: Vertical Selection

Choose verticals where the ISO has existing merchant density and the vertical SaaS window is still open: The verticals an ISO targets should be selected based on two criteria: where the ISO already has merchant relationships that can be converted to software-onboarded, and where a vertical SaaS incumbent has not yet achieved workflow lock. Restaurants, healthcare, auto repair, personal services, and multi-location operators each have different levels of vertical SaaS penetration. The ISO should map its existing merchant base by vertical, assess the competitive landscape in each, and prioritize the verticals where it has the most head start.

Avoid verticals where the incumbent has already won: In some verticals — restaurants, for example — a vertical SaaS platform (Toast) has already achieved significant workflow lock. Competing head-on in these verticals is possible but resource-intensive and low-probability. The ISV strategy should focus on verticals where the ISO can be the platform that achieves workflow lock — not on verticals where it is trying to displace an entrenched incumbent. The goal is to be the Toast of a different vertical, not to catch Toast in its own.

2. Pillar Two: Platform Decision — Build, Acquire, or Partner

Build — the highest control, highest cost, longest timeline: Building a software platform from scratch gives the ISO maximum control over features, roadmap, and differentiation. It also requires the most capital, engineering talent, and time — typically 18-36 months before the platform is market-ready. For most ISOs, this option is not practical unless the ISO has access to significant development resources and a multi-year execution runway before the 2030 deadline.

Acquire — the fastest path to an owned platform, at a financial cost: Acquiring an existing vertical SaaS company gives the ISO an owned platform with an existing merchant base, proven product-market fit, and an engineering team. The acquisition cost can be significant — vertical SaaS companies trade at premium multiples — but the time-to-market is the fastest of the three options. For ISOs with access to capital and a clear vertical target, acquisition is the most efficient path to platform ownership.

Partner (white-label) — the pragmatic middle path: A white-label platform partnership gives the ISO a branded software platform without the build cost or acquisition premium. The ISO deploys the platform under its own brand, owns the merchant relationship, and embeds payment processing — but does not own the underlying code. This is the fastest and most capital-efficient path, and for most ISOs, it is the right one. The trade-off is less control over the product roadmap, but the benefit is a platform in market in weeks, not years.

3. Pillar Three: Payment Embedding Model

Payments must be invisible — embedded in the workflow, not sold alongside it: The core principle of payment embedding is that the merchant should never experience payment processing as a separate decision. Payment is collected as part of the POS transaction, the online order, the appointment booking, or the invoice generation — it is a feature of the workflow, not a product. This invisibility is what makes the payment relationship defensible: the merchant does not shop for a different processor because they do not experience the current processor as a separate vendor.

The embedding model defines the revenue quality: When payments are embedded in a SaaS workflow, the revenue is structurally different from standalone processing revenue. It is recurring (because the SaaS subscription is recurring), it is bundled (because the payment fee is part of a larger invoice), and it is protected by the switching cost of the entire workflow. The ISV strategy must specify how payments will be embedded in each vertical workflow — what the merchant experiences, what the pricing model is, and how the revenue is recognized.

4. Pillar Four: Revenue Diversification Framework

Processing revenue alone is a declining asset: Interchange compression, increased competition, and the shift to embedded payments are all pressuring pure processing margins. An ISV strategy must define how the ISO will diversify its revenue base beyond processing — through SaaS subscription fees, hardware margins, ancillary services (loyalty, gift cards, capital lending), and data monetization. The goal is a revenue mix where processing is one stream among several, not the sole source of enterprise value.

The framework must specify target revenue mix by 2030: A practical ISV strategy sets a target — for example, 40% processing revenue, 30% SaaS subscription, 20% hardware and services, 10% ancillary — and defines the specific investments and partnerships needed to achieve that mix. Without a target, the revenue diversification is ad hoc and unmeasurable. With a target, the ISO can track progress quarterly and adjust its investments accordingly.

5. Pillar Five: Distribution Channel Ownership

The distribution channel is the moat — and it is being restructured: Historically, the ISO’s distribution channel was its sales force — reps who called on merchants and sold payment processing. That channel is being disrupted by vertical SaaS platforms, which distribute through software marketplaces, online signups, and partner referrals. The ISO’s ISV strategy must define how it will own or participate in the new distribution channels — not just how it will defend the old ones.

Owning the platform is owning the distribution: When the ISO deploys a white-label POS platform, it owns the distribution channel — every merchant on the platform is acquired through the ISO’s channel, and every additional module the merchant adopts deepens the distribution relationship. The ISO that owns the platform does not need to compete for distribution with vertical SaaS marketplaces, because it has its own marketplace — its merchant base. This is the most defensible form of distribution channel ownership available to an ISO.