Every program manager running a multi-vertical business knows this moment. A client asks for something specific — a fleet card with vehicle-level controls, a healthcare benefits card with product-level eligibility restrictions, a corrections program with separate purse structures for commissary, phone, and release funds. Sales wants to say yes. Product knows it'll be complicated. Engineering knows it'll be expensive. Operations knows the margin will shrink before the program even launches.
The platform is the reason that moment keeps happening. And the platform is the reason it doesn't have to.
Program managers profitably serve niche verticals by running them on infrastructure that configures vertical-specific rules, purse structures, and spend controls in real time — without commissioning new development for every client requirement. When the platform handles the complexity, the vertical is profitable. When it can't, every new vertical carries the cost of a new build.
This guide covers what that infrastructure needs to do, what the current market offers, and what multi-vertical program management looks like when the infrastructure is built for it.
The business case for a genuinely configurable platform is simple. Every vertical a program manager can serve from the same infrastructure is a revenue stream that doesn't require a separate integration budget. Every client requirement met through configuration rather than development is margin that stays in the business rather than funding a development sprint.
The inverse compounds over time. A program manager who needs custom development to serve fleet adds cost to every fleet program. One who can't serve corrections at all leaves that revenue on the table entirely. Across a multi-year platform contract with a growing client base, those costs and forgone revenues are significant.
Configurability isn't a technical preference. It's a commercial requirement for a program manager who wants to grow a multi-vertical operation sustainably.
Program managers today are navigating between two platform generations, and both have real limitations.
Legacy platforms carry the advantages of scale: established scheme relationships, deep compliance infrastructure, and proven transaction reliability. But they weren't built for real-time configurability. Launching a new vertical on a legacy platform typically means a change request, a development sprint, and a timeline that turns a client opportunity into a months-long internal project.
First-generation modern platforms solved the speed problem. API-first architectures and faster onboarding made it possible to launch programs quickly. But many were designed around a specific use case — usually consumer payments or basic debit card issuance — and their configurability has limits that only become visible when a client's requirements get complex.
A Next Gen platform closes that gap. It combines the scale and compliance depth of legacy infrastructure with the real-time configurability that complex niche verticals require. That combination is what makes saying yes profitable rather than costly.
Episode Six is a global provider of enterprise-grade ledger and card infrastructure, and the Episode Six platform was built specifically to support multi-vertical program management at scale. The question isn't whether a niche vertical can be served. It's how quickly and at what cost.
Each vertical has specific operational requirements that a general-purpose card platform may not support natively. Understanding those requirements is the starting point for figuring out whether a platform can serve them profitably.
Fleet. Fleet card programs need spend controls that operate at the merchant category level, the merchant level, and the transaction level simultaneously. A fleet operator needs to restrict fuel purchases by card, set per-transaction limits by vehicle, and enable or disable non-fuel categories by driver. Those controls need to update in real time as fleet policies change.
Healthcare. Healthcare payment programs — benefits cards, flexible spending account cards, health savings account cards — often require spend controls that distinguish eligible from ineligible categories at the product level rather than just the merchant level. That precision is a configuration requirement on a platform designed for it, not a development project.
Government disbursements. Government benefit programs require auditable transaction records, configurable restrictions by category and amount, and support for multiple benefit streams within a single wallet. Compliance requirements are strict and often specific to the disbursing entity. The platform needs to handle program variation across a large recipient population without bespoke infrastructure for each program.
Corrections. Corrections programs typically involve multiple distinct purse structures — commissary, telephone, and release funds — each with its own rules, balances, and access controls. Managing those structures for a large population, within the compliance and security requirements of the corrections environment, requires a platform that treats multi-purse architecture as a standard configuration.
Campus payments. Campus card programs span meal plans, laundry, printing, event access, and retail, often operating across both closed-loop and open-loop environments from a single card. Routing transactions to the right balance in real time, by location and category, requires a platform that can hold multiple logical wallets on a single card natively.
What all of these verticals share is a requirement for configuration at a level of granularity that most platforms treat as edge-case complexity. That level of granularity is exactly the kind of complexity Episode Six is designed to configure, rather than hardcode.
The failure modes in multi-vertical program management follow a consistent pattern.
Rigidity at the rules layer. The most common limitation is a platform that offers spend controls as a fixed menu rather than a configurable rule engine. When a client's requirement falls outside the available options, the answer is either a workaround that compromises the product or a development request that erodes the economics.
Separate infrastructure for separate verticals. Some program managers end up running different platforms for different verticals because no single platform supports all of them. Managing multiple vendor relationships, multiple integration stacks, and multiple compliance frameworks is a direct drag on profitability.
Multi-purse limitations. Many platforms support a single balance per card. Programs that require multiple purse structures — corrections, healthcare, campus, and government disbursements all often need this — require platforms that handle multi-purse natively as a configuration option, not a custom build.
Slow time to configure. Even on platforms with real-time configuration capability in principle, building a new program often requires vendor involvement, testing coordination, and release cycles. The difference between configuring a new vertical in hours and waiting weeks for a vendor to implement it is the difference between a profitable client expansion and an unprofitable one.
Berkeley Payment, a program manager operating across multiple verticals and geographies, migrated hundreds of programs — each with its own client requirements, rule sets, and program variation — to the Episode Six platform in under five months. The speed of that migration reflected both the platform's architecture and an implementation model that treated the project as a dedicated program, not a support queue.
Monavate has issued more than 6.3 million cards and processed over £6.5 billion in transactions on the Episode Six platform, operating across 50+ countries. That scale across a diverse program portfolio demonstrates what sustainable economics look like when infrastructure handles complexity through configuration rather than custom development.
The common thread is clear. New verticals, new client requirements, and new market expansions are program configuration exercises. They're not development projects.
Want to know which verticals your current platform is making too expensive to serve? Talk to Episode Six about configuring your program portfolio for growth. episodesix.com/industry/program-managers | episodesix.com/product/issuer-processing
Episode Six is The World's Local Processor™. As a global provider of enterprise-grade card issuing and ledger infrastructure for financial technology companies, banks, and brands, Episode Six delivers the innovative capabilities needed to compete with disruptors and lead the market. Flexibility, adaptability, and resilience are built into the core of Episode Six's platform, ensuring clients maintain a market-leading position. Episode Six operates in over 50 countries, powering millions of accounts and billions in payments globally, with an expanding team located in the US, Canada, UK, Europe, Japan, Singapore, Hong Kong, Australia, and India. Investors include HSBC, Mastercard, SBI Investment Co Ltd, Anthos Capital, Avenir, and Japan Airlines.