Sub-Accounts Explained: The Infrastructure Behind Every Neobank You’ve Never Heard Of

In 2021, California’s Department of Financial Protection and Innovation ordered Chime, one of the most recognizable “banks” in America, with millions of customers, to stop calling itself a bank. The reason was simple: it isn’t one. Chime has never held a banking license. Every dollar sitting in a Chime account is actually held by The Bancorp Bank or Stride Bank, the licensed partners doing the regulated work behind Chime’s app.

Chime isn’t the exception. It’s closer to the rule. In this guide, we’ll pull back the curtain on how this actually works, what sits behind a neobank’s app when it isn’t licensed itself, how master account sub-accounts structures let one licensed provider serve thousands of end customers safely, why isolated customer balances are the detail that makes this model trustworthy rather than risky, and how a neobank infrastructure provider like WeWire plays this exact role for African and cross-border fintechs.

The Illusion of “Your Bank”

When you open a neobank app, you’re not typically opening an account at that company. You’re opening a sub-account nested inside that company’s own master account at a licensed bank or payment institution. The neobank owns the brand, the interface, the customer relationship, and the product roadmap. 

The licensed partner underneath owns the regulatory responsibility, deposit insurance, compliance, and the actual movement of funds through banking rails. Neobank founders don’t build it because getting your own charter takes years and tens of millions of dollars, and very few products need to clear that bar to be useful on day one.

What’s Actually Happening Behind the App

The mechanism is a neobank infrastructure provider sitting between the neobank’s app and the actual banking rails. That provider holds the licenses, money services business registration, payment service provider status, sometimes a full banking charter, and exposes an API that the neobank calls to create accounts, move money, and manage customers. This is the same structure that makes embedded finance for platforms work more broadly, just applied specifically to the “digital bank account” use case rather than marketplace payouts or payroll.

The infrastructure provider isn’t invisible by accident. It’s invisible by design. The whole point of the arrangement is that the end customer experiences one seamless brand, while the compliance and settlement work happens underneath, unadvertised.

Master Account, Sub-Accounts: The Technical Model

A neobank signs up with its infrastructure provider and gets one master account. From there, each of the neobank’s customers gets a sub-account provisioned underneath that master account, created programmatically the moment a new user completes onboarding.

This master account sub-accounts structure is what lets one licensed entity serve an unlimited number of end customers without opening a new regulatory relationship for each one. Each sub-account carries its own account number, its own transaction history, and its own KYC/KYB status, configured at whatever verification tier matches the risk of that particular customer. The neobank’s dashboard shows all of it, along with balances, money movement, and reconciliation across every sub-account it has created, giving full visibility without the neobank ever having to build its own ledger infrastructure.

Why Isolated Customer Balances Matter

This is the detail that separates a well-built neobank stack from a fragile one. Isolated customer balances mean that Customer A’s funds are never commingled with Customer B’s, or with the neobank’s own operating funds, even though both sub-accounts live under the same master account. That segregation matters enormously when something goes wrong.

The clearest cautionary example is Synapse, a banking-infrastructure provider that collapsed in 2024 and took down access to deposits for customers of several fintech apps that relied on it. Some account holders are still waiting to be made whole, according to Beancount’s analysis of the fintech charter boom that followed. The failure wasn’t that the sponsor-bank model is inherently unsafe. It’s that recordkeeping between the infrastructure layer and the underlying bank fell out of sync, and isolated customer balances weren’t cleanly reconciled when it mattered most.

It’s a reminder that the model only works when the neobank infrastructure provider underneath it maintains rigorous, real-time reconciliation, not just account segmentation on paper.

Why This Model Is Spreading Across BaaS Africa and Cross-Border Fintech

The same architecture that powers Chime in the US is scaling fast into emerging markets. The Middle East and Africa banking-as-a-service market is valued at $27.10 billion in 2026 and projected to reach $41.40 billion by 2031, with Nigeria specifically cited as gaining share as open banking expands, per Mordor Intelligence’s regional market report. That growth mirrors what’s happening in the US and Europe. It’s the same sub-accounts model, applied to markets where the demand for digital-first financial products is arguably even more acute, and where it’s increasingly relevant to founders building for the US, Canada, and Southeast Asia as well, not just African corridors specifically.

WeWire as the Neobank Infrastructure Provider Behind the Curtain

WeWire holds the licenses. A FINTRAC-registered Money Services Business and PSP license in Canada, plus a Global Business License with Treasury Activities authorization in Mauritius and exposes a sub-accounts API that lets any platform create and manage isolated accounts for its own end users, the same master account sub-accounts pattern described above, but backed by rails that have already processed over $3 billion in transaction volume for more than 3,000 registered businesses across 80+ countries of account registrations and 100+ countries of payment reach. 

Each sub-account carries genuinely isolated customer balances, configurable KYC/KYB tiers, and real-time visibility into money-in tracking. Between the licensing already in place, settlement across both fiat and stablecoin rails, and a sub-accounts architecture built for exactly this use case, WeWire is functioning as that same invisible infrastructure layer for the next generation of neobanks, built for African and cross-border corridors from day one.

Conclusion

The apps that feel most like “your bank” are often the ones with the least banking infrastructure of their own, and that’s not a flaw; it’s the model working as intended. What actually determines whether that model is trustworthy isn’t whether the neobank holds a license; it’s whether the neobank infrastructure provider underneath it built isolated customer balances and real reconciliation into the foundation, rather than bolting segmentation on after the fact. 

The next time an app impresses you with how “banky” it feels, there’s a good chance the real engineering achievement is happening one layer down, in a sub-account you’ll never see the name of.