Embedded Finance vs BaaS: What Financial Institutions Need to Know
Embedded finance and banking-as-a-service (BaaS) are often treated as interchangeable. For software companies, the distinction may be largely academic. For financial institutions, however, embedded finance and BaaS represent a strategic fork: two business models with different revenue streams, customers, and risk profiles. Choosing the wrong model — or drifting into one without a clear decision — can leave a bank invisible behind another company’s app or exposed to regulatory liability.
This article is about that choice. Embedded Finance for Banks covers what embedded finance is and where the revenue sits. Here, we go one level up: which model your financial institution should run or if it should be both.
Embedded Finance vs BaaS: The Difference
IN SHORT
Banking-as-a-service (BaaS) is the infrastructure model: a licensed bank rents its charter, rails, and balance sheet to non-banks through APIs so they can offer financial products under their own brand. Embedded finance is the experience model: financial services delivered inside the digital tools a customer already uses. BaaS is one-way embedded finance gets built — but for a bank that already holds the license and the customer relationship, the two models point in opposite strategic directions.
Why It’s a Strategic & Not a Vocabulary Problem
For a fintech, BaaS is a means and embedded finance is the end. For a bank, each is a distinct way to make money from the same shift — and they are not interchangeable:
- Run the BaaS model and you become the regulated engine behind other companies’ financial products. Your revenue is program and platform fees, a share of interchange, and deposits gathered through partners. The end customer belongs to the fintech; you are the invisible utility.
- Run the embedded finance model and you put your own services — payments, lending, cashflow — inside the workflow your SMB customers already live in, under your brand. Your revenue is fee income, retained deposits, and lending margin. The customer stays yours.
The tell is who the SMB thinks they’re banking with. Under BaaS, it’s the app. Under embedded finance, it’s you. The two markets are even sized differently, and that gap signals where the value concentrates.
The infrastructure layer is a fraction of the services layer it enables. Most of the money is not in renting the rails; it’s in owning the experience on top of them — which is the embedded finance side of the line.
The BaaS Model: Real Revenue, Concentrated Risk
BaaS is a legitimate business for the right institution. A bank with spare balance-sheet capacity and a mature compliance function can wholesale its charter to fintechs and earn fee and deposit income at scale. But 2024 made the risk profile impossible to ignore, and any financial institution weighing the model has to price that in.
|
~$22.7B Global BaaS (infrastructure) market, 2025 |
~$145B Embedded finance (services) market, 2025 |
7 US sponsor banks hit with severe enforcement actions in 2024 |
Sources: Fortune Business Insights, Banking-as-a-Service Market; Fortune Business Insights, Embedded Finance Market; S&P Global Market Intelligence (2025).
- When the middleware fails, the bank is left holding it. In April 2024, Synapse — a BaaS middleware provider connecting fintech apps to their partner banks — filed for bankruptcy, and tens of thousands of end customers were frozen out of their accounts when the platform and the banks could not reconcile who owned what. The lesson regulators drew: a sponsor bank must be able to independently reconstruct every customer’s balance, without relying on a partner’s ledger.
- The liability sits with the charter, not the fintech. Across 2022–2025, US regulators issued a wave of consent orders against sponsor banks, most tied to Bank Secrecy Act and third-party-oversight failures. Whatever a partnership contract says about who handles compliance, it is the chartered bank that answers to the FDIC, OCC, and Federal Reserve.
- The financials showed it. BaaS community banks operating under consent orders underperformed their peers in 2024 — lower net interest margins, higher charge-offs, and declines in deposits and loans — as the cost of remediation landed.
THE BaaS LESSON FOR SMB-SERVING BANKS
BaaS can generate revenue, but it concentrates regulatory and reputational risk on the one party that can least offload it — the bank. If you pursue it, compliance maturity, not pricing, is the entry fee. For most financial institutions whose goal is to defend and deepen their own SMB relationships, that risk is pointed in the wrong direction.
The Embedded Finance Model: Defend the Relationship You Already Have
Embedded finance inverts the bet. Instead of powering someone else’s product, the financial institution moves the products it already owns to where the SMB now operates — inside digital banking, under the FI’s brand. The strategic logic differs in three ways:
- The customer stays yours. The SMB experiences your environment, not a third party’s, so the deposit relationship, the cross-sell, and the data behind them all stay in-house.
- The revenue is durable and rate independent. Fee income from embedded payments, lending, and cashflow tools does not rise and fall with the spread. (The pillar breaks down where that revenue sits.)
- The risk is the same as you already manage. You are serving your own customers inside your own compliance perimeter — not underwriting a partner’s end-users you never onboarded.
That is why, for a FI that already holds licenses and SMB relationships, embedded finance is usually the more direct play. It captures the margin a platform would otherwise intermediate, and it does so without taking on the sponsor-bank risk profile.
Embedded Finance vs BaaS: How the Two Models Compare
Our previous article frames these terms as infrastructure vs. experience layers. This table is about the business decision each model implies for a licensed bank.
|
Dimension |
Banking-as-a-Service |
Embedded finance |
|
Your role |
Regulated infrastructure behind others’ products |
Owner of the branded customer experience |
|
Primary revenue |
Program and platform fees, interchange share, partner deposits |
Fee income, retained deposits, lending margin |
|
Whose brand the SMB sees |
The fintech’s |
Yours |
|
Who owns the relationship and data |
The fintech partner |
You |
|
Where regulatory liability lands |
On you — for partners’ end-customers you didn’t onboard |
On you — for your own customers, inside your existing perimeter |
|
Compliance burden |
High and outward-facing: third-party oversight and BSA/AML for partners |
The compliance you already run for your own book |
|
Best fit when |
You have balance-sheet capacity to wholesale and a mature partner-oversight function |
You want to keep the SMB relationship and grow durable fee income |
How to Choose — and When the Answer Is “Both”
Three questions settle the model for most banks:
- Whose customer do you want? If the answer is “ours,” embedded finance is the model. If you are genuinely content to be the invisible engine and monetize the charter, BaaS is on the table.
- What is your compliance appetite? BaaS means owning the regulatory risk for customers whom other companies onboard. If your third-party-oversight function is not built for that, the enforcement wave of 2024 is a preview, not a warning.
- Where is the durable revenue for you? For most SMB-serving banks it is in defending deposits and fee income from customers who stay — the embedded finance thesis, not the wholesale one.
|
If your bank… |
The model that fits |
|
Wants to keep the SMB relationship, brand, and data |
Embedded finance |
|
Wants new fee and deposit income without a multi-year engineering build |
Embedded finance via a white-label partner |
|
Has excess balance-sheet capacity and a mature partner-oversight function to wholesale the charter |
Banking-as-a-service |
|
Serves SMBs directly and also wants a wholesale distribution line |
Both — run as separate businesses |
The two are not mutually exclusive. A large institution can run a BaaS line for wholesale distribution and an embedded finance strategy for its own direct SMB customers. But they are different businesses with different owners, budgets, and risk committees — and the mistake is treating one as a lightweight version of the other. Decide deliberately.
Executing the Embedded Finance Model
Choosing the model is the first fork. The second is how to stand it up — build in-house, buy a point solution, or partner with a white-label provider — and that is where most programs stall. The execution view, and why programs stall before they produce a dollar of revenue, is in What It Takes to Capture the Revenue. The full weighted build-vs-buy-vs-partner matrix, technology-stack map, vendor-evaluation checklist, and ROI model live in the Embedded Finance Strategy Guide.
How 9Spokes Fits — the Embedded Finance Model, Done Right
9Spokes is a white-labeled data insights platform built for financial institutions that serve SMBs — the partner route to the embedded finance model. It embeds inside your existing digital channels via single sign-on, keeps your brand front and center, and delivers the hardest layer — aggregation, normalization, insight, and banker-facing intelligence — from one stack, so the customer, the relationship, and the revenue stay yours.
- SMB Financial Hub — the customer-facing product. SMBs connect accounts across 800+ financial and business service providers for a unified view of their finances under your brand: consolidated cash position, automated cashflow forecasts, spending trends, and merchant data.
- Customer Insights Hub — the internal-facing product. The same consented data, shaped for relationship, credit, product, and marketing teams: cross-sell signals with wallet-share insight, sharper credit decisions, and early risk flags.
TAKE THE NEXT STEP
Unlock new revenue streams from your SMB customers.
See how 9Spokes embeds financial insights inside your existing digital channels — under your brand, on your rails, and measurable in deposits, lending, fee income, and retention.