Banking-as-a-Service (BaaS) lets non-bank companies embed banking products — accounts, cards, payments, lending — into their own apps by plugging into a licensed bank’s infrastructure via APIs. It powers most neobanks and embedded finance, but creates a chain of responsibility that regulators increasingly scrutinise.
Behind most neobanks and ’embedded finance’ features sits a quieter business model: Banking-as-a-Service. BaaS is the infrastructure layer that lets any company offer banking products without becoming a bank. Understanding it explains how fintech really works underneath, and why the regulatory spotlight is now turning toward it. This guide breaks down the model, its players and its risks.
What is BaaS?
A model where licensed banks expose their regulated capabilities via APIs, letting non-banks embed accounts, cards and payments into their own products.
Who uses BaaS?
Neobanks, fintechs and increasingly non-financial brands embedding finance — from retailers to software platforms offering accounts or cards.
What is the main risk?
A chain of responsibility between the brand, the BaaS provider and the licensed bank can blur accountability, which regulators are scrutinising.
What is Banking-as-a-Service?
Banking-as-a-Service is a model in which a licensed bank makes its regulated capabilities — holding deposits, issuing cards, processing payments, originating loans — available to other companies through APIs. A non-bank business can then offer these banking products to its own customers under its own brand, without holding a banking licence itself. The licensed bank provides the regulated foundation; the brand provides the customer relationship and experience.
This three-layer structure — licensed bank, BaaS technology provider, and customer-facing brand — is the engine behind much of modern fintech. When a neobank without its own licence offers you an account, or a software platform lets you open a business account inside its app, BaaS is almost certainly what makes it possible.
Why has BaaS grown so quickly?
BaaS grew because it dramatically lowers the barrier to offering financial products. Obtaining a banking licence is slow, expensive and capital-intensive; BaaS lets a company launch banking features in months instead of years by renting a licensed bank’s capabilities. This unlocked a wave of neobanks and embedded-finance features that would otherwise have been impossible for non-banks to build.
For the licensed banks providing the infrastructure, BaaS opens a new revenue stream and customer reach without building consumer-facing products. For the brands, it turns finance into a feature they can embed to deepen customer relationships and capture new revenue. This mutual benefit fuelled rapid growth across the ecosystem.
Who actually uses Banking-as-a-Service?
The users span a wide range. Neobanks without their own licence are classic BaaS customers. Beyond them, software platforms embed business accounts and cards for their users, retailers offer branded payment cards and financing, gig-economy platforms provide instant-payout accounts to workers, and countless apps add wallets and payments. Increasingly, non-financial brands use BaaS to weave finance into their core product.
This is the foundation of ’embedded finance’ — the idea that financial services appear at the point of need inside non-financial products. BaaS is the plumbing that makes embedded finance possible, which is why it has become one of the most strategically important layers in the modern financial stack.
What are the risks and regulatory concerns with BaaS?
The central risk is the chain of responsibility. With a brand, a BaaS provider and a licensed bank each playing a part, accountability for compliance, customer protection and risk management can blur. If something goes wrong — a compliance failure, a provider collapse, mishandled funds — customers can be caught between parties unsure who is responsible. Regulators have grown increasingly concerned about this diffusion of accountability.
As a result, supervision of BaaS arrangements is tightening, with licensed banks held more firmly responsible for the activities they enable and clearer expectations on how customer funds are safeguarded. For anyone building on or using BaaS, understanding where regulatory responsibility actually sits — a recurring theme across the fintech and transfers hub — is essential rather than optional.
How does BaaS differ from open banking?
The two are often confused but are distinct. Open banking is about sharing existing bank data and initiating payments with customer consent — it opens up access to data held by banks. BaaS is about building new banking products: a non-bank uses a licensed bank’s infrastructure to offer accounts, cards and payments under its own brand. Open banking shares; BaaS builds.
They are complementary layers of the modern financial stack. A fintech might use BaaS to offer accounts and open banking to aggregate a customer’s other accounts. Understanding the difference clarifies how fintech products are assembled: BaaS provides the regulated foundation to create banking services, while open banking provides connectivity to data and payments across existing institutions.
What does the BaaS provider actually do?
The BaaS provider sits between the licensed bank and the brand, providing the technology layer that makes the partnership work: APIs the brand integrates with, orchestration of accounts and cards, compliance and onboarding tooling, transaction processing, and the middleware that translates the bank’s regulated capabilities into developer-friendly services. It abstracts the complexity of the underlying bank into something a brand can build on quickly.
This middle layer is where much of the practical value and risk concentrates. A strong BaaS provider makes integration fast and compliance manageable; a weak one creates operational fragility. Because the provider orchestrates the relationship between brand and bank, its reliability and compliance capability are critical to the whole arrangement working safely.
Why are regulators tightening their focus on BaaS?
Regulators have grown concerned because the multi-party BaaS structure can obscure who is responsible for compliance, customer protection and risk management. When responsibilities are spread across a brand, a provider and a bank, gaps can emerge — inadequate anti-money-laundering controls, unclear handling of customer funds, or confusion over who answers when things go wrong. Several high-profile problems have sharpened this scrutiny.
The regulatory response has been to hold licensed banks more firmly accountable for the activities they enable through BaaS, and to demand clearer safeguarding of customer funds and robust oversight of partners. For anyone building on BaaS, this means compliance cannot be an afterthought delegated entirely to the provider — responsibility, as explored across the fintech and transfers hub, ultimately traces back through the chain.
What is the future of Banking-as-a-Service?
BaaS is likely to keep growing as embedded finance expands, but with greater regulatory rigour and consolidation. Expect tighter standards for safeguarding funds, clearer accountability across the chain, and a shake-out that favours providers with strong compliance and stable banking relationships. The weaker, compliance-light providers face pressure as supervision intensifies.
For the ecosystem, this maturation is healthy: more robust BaaS infrastructure enables embedded finance to scale on a sounder footing. For brands and fintechs, the lesson is to choose BaaS partners for compliance strength and durability, not just speed and price. BaaS remains a foundational layer of modern finance, but one entering a more disciplined phase.
How does BaaS enable embedded finance?
BaaS is the engine beneath embedded finance. When a software platform offers its users a business account, or a retailer issues a branded card, it is almost always using BaaS to access a licensed bank’s capabilities through APIs. BaaS abstracts the regulatory and technical complexity of banking into developer-friendly services, so a brand can embed accounts, cards, payments or lending without becoming a bank itself.
Without BaaS, embedded finance would be impossible for most companies, because obtaining a banking licence is slow, costly and capital-intensive. By providing the regulated foundation as a service, BaaS lowers the barrier from years and millions to months and manageable cost. This is why the growth of embedded finance and the growth of BaaS are inseparable — one is the visible product, the other the invisible infrastructure, both central to the fintech and transfers hub.
What should a company evaluate before building on BaaS?
A company considering BaaS should evaluate several dimensions beyond price and API quality. How strong is the provider’s compliance infrastructure, and how clearly are anti-money-laundering and customer-protection responsibilities allocated? Which licensed banks does it work with, and how stable are those relationships? How is customer money safeguarded? What happens to your customers if the provider or its bank partner fails? And does the arrangement satisfy your own regulatory obligations?
These questions matter because operational and reputational risk flows back to the brand even when regulatory responsibility sits with the bank. A failure in the chain — a compliance lapse or a provider collapse — harms the brand’s customers and reputation regardless of where formal accountability lies. Choosing a BaaS partner for compliance strength and durability, not just speed and cost, is the disciplined approach that protects both the business and its customers.
What is the bottom line on Banking-as-a-Service?
Banking-as-a-Service is the foundational infrastructure that lets non-banks offer banking products by renting a licensed bank’s regulated capabilities through APIs. It powers most neobanks and the entire embedded-finance movement, lowering the barrier to offering financial services from years to months. Its three-layer structure — brand, BaaS provider, licensed bank — is one of the most important and least visible parts of modern finance.
The critical caveat is the chain of responsibility, which can blur accountability and which regulators are increasingly scrutinising. For anyone building on or using BaaS, choosing partners for compliance strength and understanding where responsibility ultimately sits is essential. As BaaS matures into a more disciplined phase, it remains a powerful enabler — central to the trends across the fintech and transfers hub — but one that rewards diligence over speed alone.
Is BaaS right for every company?
BaaS is not right for everyone. It suits companies with engaged users and a genuine use case for embedded financial products, the willingness to take on compliance responsibilities, and the diligence to choose a strong partner. Companies without a clear financial use case, or without capacity to manage the responsibilities involved, may find BaaS more burden than benefit. As with any infrastructure decision, it rewards a clear strategic rationale over following a trend.
Frequently Asked Questions
Is BaaS the same as a neobank?
No. BaaS is the infrastructure layer; a neobank is often a customer-facing brand built on top of BaaS, though some neobanks hold their own licence.
Does BaaS mean the brand is a bank?
Not necessarily. The brand provides the experience while a licensed bank behind the scenes provides the regulated capability and usually holds the funds.
Why are regulators focused on BaaS?
Because the multi-party chain can blur accountability for compliance and customer protection, prompting tighter supervision of the licensed banks involved.
Can any company offer banking through BaaS?
Many can embed financial features via BaaS, but they must still meet compliance obligations, and the licensed bank partner ultimately carries regulatory responsibility.
Discover more from Kurums | Business Intelligence
Subscribe to get the latest posts sent to your email.
