From Back Office to Power Player: How Program Management Took Over Payments

Program management didn't arrive fully formed. It was built, piece by piece, and shaped by every new technology, regulatory shift, and market demand that the payments industry threw at it.

To understand where program management stands today, you have to understand how it got
here and where the industry saw value worth nurturing.

Before There Was a Name for It

Payments have been around long before the history books; at their most basic, they are the
exchange of value. But the introduction of payment cards in the 1950s changed the operational
equation in ways that would take decades to fully play out, bringing payments into the spotlight.
‍
The first card programs emerged in the form of “chargeback cards”, comparable to today’s credit
cards, that were fully owned and operated by issuing banks. Banks performed every operational
function, including issuance, authorizations, settlement, fraud management, and reconciliation,
all under one roof.
‍
During this time, card networks began to emerge to connect institutions, but the infrastructure
outside the bank was limited. Control was centralized at the bank, and the system worked well
because the complexity was still manageable.
‍
What's easy to miss looking back is that program management was already happening. It simply
wasn't called that. The responsibilities existed inside the bank, handled by teams building
processes in real time as the system expanded. The discipline of program management existed
before the definition did.

The 1980s: The First Seeds of Outsourcing

The 1980s changed the landscape in ways the industry hadn't anticipated. Alongside traditional
credit cards, a new wave of prefunded cards, including debit cards, gift cards, and stored-value
programs, arrived on the scene and quickly became a staple. Alongside the emergence of EMV
chip technology, the diversity of different card programs and players added several layers of
complexity. The product set was no longer simple or uniform.
‍
With that expansion came early processors who began handling routing and settlement. For the
first time, banks were no longer managing the entire payments ecosystem in-house. Some

"program-like" functions, such as card fulfillment and basic reconciliation, started moving outside
the bank walls, even as banks maintained tight control over the rest.
‍
These were modest steps, but they mattered. They established the precedent that card program
operations could be handled by parties other than the issuing bank — and that specialization
had value. Program management functions were now being outsourced, and the discipline's
foundation was being laid, even if no one yet used the term “Program Managers”.
‍

The 2000s: Program Management Finds Its Name

In the 2000s, Fintech arrived. Startups saw the opportunity that payment programs represented
and wanted in. The problem was that obtaining a full bank charter was expensive, slow, and the
regulatory complexity made it nearly impossible for new companies to clear.
‍
BIN Sponsorship solved that problem. For the first time, fintechs could issue cards under a
bank's existing network membership without holding a charter of their own, and the door opened
to accelerated innovation in payments.
‍
But BIN Sponsorship also created a new kind of complexity. These fintechs now answered to
multiple parties simultaneously — banks, networks, and regulators — each with different
requirements and motivations. Coordinating across all of them while maintaining compliance
and actually scaling a program was more than most companies could manage on their own.
That's where program management found its name. It became the dedicated layer between
fintechs and their regulatory obligations, coordinating relationships, maintaining compliance
through expert guidance, and giving these companies the operational foundation to scale
without compromising their programs or the safety of their customers.
‍
With the need clear and the role defined, program management became an official part of the
payments ecosystem. And it was just getting started.

The 2010s: The BaaS Era Test

Following BIN Sponsorship, banks began offering even more services to non-bank companies,
effectively creating the term Banking-as-a-Service. Like BIN Sponsorship, this innovation
brought with it a wave of energy and investment that reshaped what was possible.
‍
The premise was compelling: give fintechs and brands API access to banking infrastructure and
let them move fast. In the beginning, it lived up to the excitement as Neobanks and branded
programs launched at a pace nobody had seen before.

Then, the industry hit a wall. With so many players and no source of truth to tie them together,
consumer safety was put at risk, and those who had scaled carelessly were hit with
enforcement actions and consent orders as their programs unwound.
‍
The issue was not the pace of innovation; it was that the model had treated compliance as
something to address later, and it turned out that later arrived all at once. More fundamentally,
the legacy BaaS structure created gaps in accountability as banks could see only pieces of the
programs that the fintech controlled. Compliance posture, risk exposure, and operational health
fell between parties, each responsible for something, but no one was responsible for everything.

The Next Generation NXTMOVES is Building: Lifecycle Ownership

Today, the industry recognizes that the same mistake cannot be repeated. However, that truth
does not mean never using BaaS or avoiding fintech partnerships – it means finding a solution
to the disjointed system.
‍
Done right, program management is the operating system of a card program and the function
that owns the full lifecycle from concept through launch and scale, integrating compliance,
operations, performance, and growth into a single unified framework.
‍
NXTMOVES was founded by banking and payments veterans who watched this evolution
firsthand — and who built a company specifically designed for where the industry has arrived.

Lifecycle ownership. The old model was optimized to get a program off the ground with a
compliant structure at the outset. The modern model also optimizes for what happens after
launch through continuous oversight, refighting, and performance analysis.
‍
Compliance as a foundation, not a ceiling. Traditional program managers stop at compliance.
The new generation starts there and builds everything else on top of it, ensuring a program is
ready to scale safely and securely from day one.
‍
Real-time intelligence. Legacy reporting cycles, or a lack thereof, is what caused the BaaS
reckoning. Today, banks and businesses need real-time visibility into what's working, what's not,
and where growth is coming from. Additionally, regulators need to be able to view every layer
upon request to ensure the program stays compliant.
‍
Dedicated infrastructure. One-size-fits-all doesn't work when your product, your audience, and
your market are specific to you. Programs built to last are built on infrastructure designed for
them. Customization is about more than faster placement; it is about program adoption and
overall success.
‍
Program management started as something that happened inside banks without a name. It
became an outsourced function as the product set grew too complex to manage internally. It
found its identity when BIN Sponsorship made fintech possible. And it matured into a strategic discipline when the BaaS era exposed what happens when no one truly owns the whole program.
‍
Every change was driven by an industry need and adapted to serve it as it evolved. Program
management has grown alongside payments since the beginning, taking on a larger role as the
industry demanded it. Today, next-generation program management is the difference between a
program that succeeds and one that stalls.

‍