What is Banking-as-a-Service (BaaS)?
Banking-as-a-Service (BaaS) is a model where a licensed bank exposes its core banking capabilities through APIs, allowing non-bank companies to embed accounts, payments, and other financial services into their own products. The non-bank company builds the customer-facing experience. The licensed bank provides the infrastructure, regulatory coverage, and money-handling capability underneath it.
The BaaS market is estimated at around $5 billion in 2025, with projected growth to $19 billion by 2035, driven by embedded finance adoption and maturing regulatory frameworks across the EU, UK, and US.
How does BaaS work?
BaaS operates through a three-tier structure. Each layer has a distinct role.
- The licensed bank sits at the foundation. It holds the regulatory approvals and maintains the core banking infrastructure. It is the entity whose license makes the whole arrangement work. Compliance, capital adequacy, and regulatory reporting all sit here.
- The BaaS platform sits in the middle. It builds the technology layer that connects the bank's systems to third parties via APIs. Some BaaS providers are the licensed bank itself. Others are independent technology companies sitting between the bank and the end user.
- The distributor sits at the top. This is the fintech, marketplace, or non-financial company building a customer-facing product using the BaaS layer. A neobank, an expense management platform, or a payroll tool can all be distributors. They build the user experience. The bank and BaaS platform handle the regulated activity underneath.
What does BaaS enable?
A non-bank company accessing BaaS can offer financial products without going through the years-long process of obtaining its own banking license. Depending on what the BaaS provider exposes, a distributor can typically offer:
- Bank accounts and IBANs for their users
- Payment initiation via ACH, wire, SEPA, or FedNow
- Debit or prepaid card issuing
- KYC and AML compliance services
- Foreign exchange and multi-currency account features
- Virtual accounts and sub-account structures for fund segregation
What is the difference between BaaS and embedded finance?
These two terms are closely related but describe different things.
Embedded finance is the end result: financial features available inside a non-financial product. When a ride-sharing app lets drivers receive instant payouts, or a SaaS platform offers a business checking account, that is embedded finance.
BaaS is the infrastructure model that makes embedded finance possible. It is the layer of licensed capabilities, APIs, and compliance infrastructure that a distributor builds on top of.
BaaS is how you build embedded finance. Embedded finance is what the customer sees.
What is the difference between BaaS and a sponsor bank?
A sponsor bank is a licensed bank that provides a fintech with access to payment rails and regulatory coverage, typically through an FBO account structure. The fintech originates ACH, issues prepaid cards, or processes payments under the sponsor bank's license.
BaaS is a broader term for the same concept, often implying a more productized, API-first arrangement. A sponsor bank relationship can be a BaaS arrangement if the bank exposes its services through APIs. Not all sponsor bank relationships are built on BaaS infrastructure, and not all BaaS providers are traditional banks.
What happened with Synapse and why it matters
The Synapse collapse in 2024 is the most significant BaaS failure to date. It reshaped how regulators and participants think about the model. Synapse was a BaaS middleware provider connecting banks and fintechs. When it filed for bankruptcy in April 2024, the court-appointed trustee initially reported an $85 million reconciliation gap between what end users were owed and what the partner banks actually held. That figure was later revised to between $65 million and $96 million. Over 100,000 customers lost access to their funds for months.
The collapse exposed a structural vulnerability in the three-tier model. When the middleware layer fails, the ledger of who owns what can become contested. Regulators responded with enforcement actions against BaaS-connected banks over gaps in compliance programs, reconciliation practices, and third-party oversight.
The lesson is clear. Payment reconciliation, flow of funds documentation, and fund segregation are not just good practice. They are the specific failure points regulators now scrutinize in BaaS arrangements.
Why BaaS matters for payment platforms
For fintechs and payment platforms that are not licensed banks, BaaS is how they access the banking infrastructure they need to operate. Without it, they would need to obtain their own banking license, a multi-year process requiring significant capital and regulatory engagement.
With it, they can launch payment products, issue cards, and hold customer funds inside their platform while remaining inside a licensed regulatory framework. The tradeoff is dependence on the BaaS provider's infrastructure and compliance controls, and the need to manage the relationship carefully to avoid the kind of reconciliation and oversight gaps that brought Synapse down.
