Embedded finance and banking as a service, usually shortened to BaaS, get used as if they mean the same thing. They don’t. BaaS is the regulated infrastructure: a licensed bank renting out its rails through an API. Embedded finance is what the customer actually sees: a financial product built into a non-bank’s own app or checkout.
The distinction sounds academic until a platform buys the wrong thing. A software company that wants to offer its users a business account doesn’t need to become a bank. A company that wants to launch its own banking brand needs a lot more than an integration. Getting embedded finance vs banking as a service right is the difference between those two projects.
What is banking as a service?
Banking as a service is a model in which a licensed bank, or a regulated electronic money institution, provides banking functions to third parties through APIs, usually white-labelled. The Wharton primer on BaaS describes it as a regulated institution offering its infrastructure as a service, so another business can plug banking features into its own product.
The functions on offer are the building blocks of a bank: accounts, card issuing, payments, and sometimes lending. The bank holds the licence and carries the regulatory weight. The partner consumes the rails through code. Providers such as ClearBank, Solaris and Treasury Prime sit in this layer, powering products that carry someone else’s brand on the front.
Not every BaaS provider holds the same kind of licence, and it matters for what they can offer. A provider with a full banking licence can support deposits and lending. One operating on an electronic money institution licence can issue e-money and process payments, but it can’t take deposits or lend in the same way.
So a platform shopping for BaaS is really shopping for a licence scope too. A mismatch between what it wants to offer and what its provider is allowed to do tends to surface late and expensively.
BaaS is a supply relationship. It answers how a financial feature gets built and who is licensed to run it. By itself it says nothing about where that feature shows up.
What is embedded finance?
Embedded finance is a financial product offered inside a non-financial company’s own platform, at the moment the customer needs it. The customer never leaves the app they came to use.
The examples are everywhere once you look. A checkout that offers instalment credit at the point of sale. An accounting tool that opens a business account without sending you to a bank. A marketplace that pays its sellers through wallets built into the dashboard. In each case a company whose main business isn’t banking has put a financial product in front of its users.
Embedded finance answers a different question from BaaS: not how the feature is built, but what the customer experiences and who distributes it. The financial service stops being a separate errand and becomes part of the flow the customer is already in.
The reason non-banks bother is commercial. A financial product inside the flow lifts conversion and keeps the customer on the platform, and it opens a revenue line the business didn’t have before. Software companies, marketplaces and retailers have moved into finance with no ambition to become banks: the account or the credit line is a feature that makes the core product stickier, not a business they want to run and be licensed for.
So what is the actual difference?
BaaS is the how. Embedded finance is the what. That is the whole distinction, and most of the confusion comes from collapsing the two.
BaaS vs embedded finance is infrastructure versus experience. You can have one without the other. A challenger bank built on a BaaS provider is BaaS-powered, but it is still a financial brand in its own right, not embedded in anyone else’s product. A retailer offering a branded card is doing embedded finance, but it relies on a licensed provider underneath to make it legal. Embedded finance almost always sits on top of BaaS or a direct banking licence; BaaS doesn’t always end up embedded.
| Dimension | Banking as a service | Embedded finance |
|---|---|---|
| What it is | Regulated banking infrastructure via API | A financial product inside a non-bank platform |
| Who supplies it | A licensed bank or e-money institution | Any consumer or business-facing platform |
| Who holds the licence | The bank or EMI | The platform usually doesn’t; it relies on a provider |
| What the customer sees | Usually nothing; it sits behind the brand | The financial product, in the app they already use |
| Its role | Infrastructure supplier | Distribution channel |
Where does open banking fit?
Open banking is the third term people fold into this, and it is a different thing again. It is about sharing data, not providing banking functions.
Under the UK regime, mandated by the Competition and Markets Authority to implement PSD2, banks let authorised third parties access account data, and initiate payments, with the customer’s explicit consent, through standardised APIs. The FCA oversees these activities and the consumer-consent rules around them. The model runs well beyond Britain: the EU through PSD2, Australia through its Consumer Data Right, and comparable regimes now live across much of Asia. Open banking moves data and payment instructions. It doesn’t hand a platform a bank account to offer.
So a budgeting app that reads your transactions to categorise your spending is using open banking. A retailer offering its own branded card is using embedded finance built on BaaS. That is why the answer to “is embedded finance the same as open banking” is no: one distributes a financial product, the other shares data and initiates payments.
Who is responsible when it goes wrong?
This is where “who holds the licence” stops being semantics and starts costing money.
The licensed bank underneath keeps the regulatory responsibility, and it can’t delegate it. In a 2024 joint statement, US banking regulators were blunt about this: a bank can’t hand its anti-money-laundering obligations to a fintech partner, and it stays accountable for compliance regardless of which functions it delegates. They pressed for contracts that spell out who does what, down to who maintains the ledger and who controls the accounts held for the end users.
That ledger point isn’t a technicality. In many BaaS arrangements the fintech keeps the record of which customer owns what, while the bank holds the pooled funds. If the two sets of books stop reconciling, or the bank loses sight of the partner’s records, customers can find themselves locked out of their own money while the two sides argue over whose number is right.
A 2024 collapse of a US banking-as-a-service middleware left exactly that gap. It is why regulators now want the ledgering and account-control questions settled in the contract before anything goes live.
The principle travels. Whatever the jurisdiction, the party with the licence is the party a regulator holds responsible. For a platform choosing an embedded-finance route, that has a practical consequence: the bank underneath is on the hook, so it will scrutinise you, your onboarding and your controls before it lets you near its rails. A cheap, light-touch BaaS relationship that skips that scrutiny is usually a sign the risk has been parked somewhere it will resurface.
Which does your platform actually need?
Strip the jargon and it comes down to what you are trying to do.
If you want to add a financial product to your own platform without becoming a bank, you want embedded finance, delivered through a BaaS provider or partner bank. If you want to build a financial brand or a neobank, you need BaaS, or your own licence, because you are the financial product now. If all you need is to read a customer’s bank data or trigger a payment from their existing account, that is open banking, and neither of the other two.
Most platforms discover they want the first of those and only think they want the second. Naming the project correctly at the start saves a lot of wasted procurement.
FAQs
Is embedded finance the same as banking as a service? No. Banking as a service is the regulated infrastructure a licensed bank provides through APIs. Embedded finance is the financial product a non-bank offers inside its own platform, usually built on top of BaaS.
Is embedded finance the same as open banking? No. Open banking is consent-based data sharing and payment initiation between banks and third parties. Embedded finance is the distribution of an actual financial product inside a non-financial app.
Do you need a banking licence for embedded finance? Usually not. The point of embedded finance is that a non-bank can offer financial products by relying on a licensed BaaS provider or partner bank that holds the licence and the compliance obligations.
What is a BaaS provider? A licensed bank or electronic money institution that packages banking functions, such as accounts, cards and payments, and offers them to other businesses through APIs so those businesses can build financial features without a licence of their own.
Can you use open banking and embedded finance together? Yes, and platforms often do. A lending product embedded in a checkout might use open banking to read the applicant’s bank data for an affordability check, then use a BaaS provider to issue the credit. They solve different parts of the same journey.
