Where do each partner’s customer funds sit at the program and end-customer level? Do the bank, processor, and card network record each transaction in the same way? Can the bank produce a complete audit trail without reconstructing it from several systems?
For sponsor banks, these questions ultimately determine whether a fintech program can operate with control at scale.
The 2024 Synapse collapse showed why these questions matter. The consequences were immediate. Synapse’s records did not align with records held by partner banks. As the parties worked to reconcile discrepancies, customers were left unable to access their funds.
Separately, in June 2024, the Federal Reserve issued an enforcement action against Evolve Bank & Trust. It cited shortcomings in risk management, anti-money-laundering controls, and consumer compliance related to the bank’s fintech partnerships. For a deeper look at this failure mode, see The BaaS Collapse Was a Ledger Story.
Modernizing the core and modernizing the payment infrastructure around it are two different projects. They do not have to happen in sequence. Importantly, banks can modernize the operating layer around the core today. They do not have to wait for a core migration to begin or become part of the roadmap.
The problem: sponsor bank requirements live above the core
A modern core gives a bank greater flexibility. It supports faster product configuration and real-time processing instead of batch processing. Those gains are real. However, sponsor banking requires something more.
The bank must know how much belongs to each partner, program, and end customer at any moment. It must reconcile its records with those of every party involved in a transaction. It must also onboard new partners without launching bespoke integration projects. And it must provide regulators with a complete audit trail on demand.
These are ledger and fund segmentation requirements. They are addressed above the core, in the operating layer that manages segmentation, card issuing and processing, multi-rail orchestration, and reconciliation.
The core remains the bank’s system of record for its own accounts. However, holding program and end-customer balances requires a different design. Sponsor programs need segmentation, routable identifiers, and partner-level reporting. That calls for infrastructure built specifically for the job.
The gap rarely appears in a demo. Instead, the cracks become visible as transaction volume grows. They also surface when a second fintech launches on the same rails and operations teams must manually reconcile multiple systems.
A question that should take seconds can turn into a lengthy process. Compliance reviews create another challenge when teams must reconstruct data across systems to produce a complete audit trail. And when a bank wants to onboard a new partner, another bespoke integration can become a barrier to growth.
The promise: the operating layer does not wait on the migration
The instinct is often to sequence the work. Modernize the core first, then address the payment and program layer.
But that approach ties a bank’s partnership roadmap to its core migration schedule. A core migration takes time. Fintech demand does not pause while the bank completes it.
These two projects do not share a timeline. A bank can put the operating layer in place now, regardless of where it stands in its core migration cycle. It can connect that infrastructure to the core it uses today or adopts next year.
The product: infrastructure connected to the core
Qolo adds an infrastructure layer that connects to and operates on top of a bank’s existing core. It is core-agnostic and does not require a core replacement.
Quantum Ledger is Qolo’s embedded ledger. It provides real-time, hierarchical ledgering and balance visibility across programs, entities, virtual accounts, and cardholders.
Qolo’s Virtual Account Management for banks creates operational virtual accounts with routable identifiers and configurable structures. These are not simply reporting tags.
Qinetic Issuing is Qolo’s first-party card issuing and processing stack for commercial and embedded programs. It supports virtual and physical cards across credit, debit, and prepaid constructs.
Qascade Money orchestrates supported payment rails through a connected platform. These include ACH, wire, RTP, FedNow, and card-related flows.
Because these capabilities use the same ledger architecture, supported card and payment movements can be recorded, viewed, and reconciled in one system.
This is the difference between adding isolated point solutions and adding a connected infrastructure layer. The bank retains oversight of its partner programs. Meanwhile, Qolo provides the ledger, account structures, issuing, orchestration, and reconciliation capabilities beneath them.
The proof: Qolo runs on top of existing cores today
Qolo is deployed at some of the largest U.S. banks on top of their existing core environments. No core Qolo is deployed at some of the largest U.S. banks on top of their existing core environments. No core replacement was required.
These banks can modernize their capabilities without waiting for a multi-year core migration to finish. They can address their sponsor banking infrastructure needs while maintaining their existing core environments.
The strategic question
Banks considering sponsor banking should ask two separate questions:
- Is our core positioned for the future?
- Does our operating layer provide the fund visibility, control, and auditability that fintech partners and regulators require today?
The strongest strategy addresses both questions on separate timelines.
The bank that wins the next partnership will not simply be the one with the newest core. It will be the one that can show partners and regulators how money is structured, moved, and reconciled.