Banking-as-a-Service (BaaS)
Also known as: BaaS, sponsor banking, bank partnership model, fintech partner bank
Banking-as-a-Service (BaaS) is a model in which licensed banks rent out their charters and infrastructure, through APIs, so other companies can offer accounts, debit cards, and payments under their own brand.
While BaaS powered a wave of fintech launches, it also blurred who was responsible for compliance, which led to a regulatory crackdown in the United States and one high-profile collapse.
Banking-as-a-Service (BaaS), explained at three levels
At home
Banking-as-a-Service works like a store-brand product made in someone else's factory. The app's name is on the box, but a licensed bank actually holds your money and issues your debit card behind the scenes. The app designs the screens and the customer experience, and the bank, often through a technology middleman, provides the real account. That's how an app that isn't a bank can still give you an account and a card.
At work
Banking-as-a-Service is a model in which a licensed bank lets other companies offer accounts, cards, and payments under their own brand through APIs. The company avoids getting its own bank licence, which can take years, and pays the bank and any technology provider fees. Businesses use it to launch financial products in months, but the bank stays responsible to regulators for compliance.
At home
Most BaaS accounts aren't separate bank accounts in your name. The partner bank usually holds one large pooled account for all of an app's customers, called a 'for benefit of' account, and a ledger, kept by the app or a middleware company, records how much of that pool belongs to you. The app shows your balance from that ledger. That's why the partner bank's name in the fine print matters: it is the institution actually holding your money and the one that determines deposit insurance.
At work
A typical BaaS stack has three layers: the sponsor bank, which holds the charter, the pooled accounts, and the regulatory responsibility; a middleware or BaaS platform, which provides APIs, ledgers, card issuing, and compliance tooling; and the brand, which owns the customer experience. Know your customer checks, fraud monitoring, complaints, and reconciliation are split between them by contract. Regulators hold the bank accountable regardless of what the contract says, which is why sponsor banks increasingly demand direct access to program data.
At home
Pass-through deposit insurance can protect each end user of a pooled account as if they held their own deposit, but only if the bank's records accurately show who owns what. When the ledger sits with a middleware company and drifts from the bank's records, nobody can prove each customer's share. While that requirement sounds like paperwork, in my opinion it's the whole ballgame. The Synapse failure showed that a missing ledger can turn insured deposits into months of frozen money.
At work
Post-crackdown, sponsor banks demand more: direct access to transaction data, their own compliance staff embedded in programs, and stricter onboarding. Some fintechs responded by seeking their own charters or acquiring banks. Outside the US, similar models exist through e-money licences in Europe and the UK and payment service provider registration in Canada, each with different rules on safeguarding customer funds.
Real-world examples
At home
Marcus opened an account with a popular budgeting app that offered a debit card. When the app announced it was shutting down, he found the partner bank's name in the terms. He contacted the bank directly and moved his balance out within a week.
At work
Sophie is a compliance lead at a fintech that offers business accounts through a sponsor bank. After the bank received a consent order, it required Sophie's team to share daily transaction files and adopt its anti-money-laundering procedures. The extra work slowed product launches but kept the partnership alive.
How it compares
| feature | Banking-as-a-Service (BaaS) | Own bank charter |
|---|---|---|
| Who holds the licence | The partner bank | The company itself |
| Time to launch | Months | Years |
| Control | Shared, dependent on partner | Full |
| Regulatory burden | Indirect, but rising | Direct and heavy |
| Partner risk | High if the bank or middleware exits | Not applicable |
BaaS trades control for speed. The partner bank is always the one regulators hold responsible.
For analysts
If your roadmap depends on a BaaS partner, the partner's regulatory health is a key risk, not a footnote. I'd track your sponsor bank's enforcement history and capital position the same way you'd track a critical supplier's finances.
History & origin
BaaS grew in the United States during the 2010s as small community banks discovered they could earn fees by sponsoring fintech programs, while middleware platforms handled the technical integration. Neobanks such as Chime were built on partner banks rather than their own charters. The model peaked during the 2020 and 2021 fintech funding boom. Then regulators stepped in: from 2022 onward, US banking agencies issued a string of consent orders against sponsor banks for weak anti-money-laundering and third-party controls. In April 2024, the middleware firm Synapse filed for bankruptcy, and reconciliation gaps left many end users unable to access tens of millions of dollars. My take is that BaaS wasn't flawed in principle, but too many participants assumed someone else was doing the compliance.