Embedded Finance: When Every App Becomes a Bank
Written with AI assistance and reviewed by the NorwegianSpark SA editorial team.
Embedded finance is what happens when a company that is not a bank starts offering banking products inside its own app. Shopify lends to merchants. Uber issues debit cards to drivers. A checkout page offers to split a purchase into four payments. None of those companies holds a banking licence. Someone else does, and the arrangement is invisible at the point where you use it.
That invisibility is the whole subject. Embedded finance is genuinely convenient, and the same structure produced one of the worst consumer outcomes in recent fintech history. It is worth understanding the plumbing before you keep a meaningful balance in an app that is not a bank.
The three-party structure
Almost every embedded-finance product is three companies wearing one brand.
- The platform — Shopify, Uber, an airline, a retailer. It owns the app, the brand on the card and the customer relationship. This is the only one you interact with.
- The licensed bank — the entity that actually holds the deposits, carries the charter and answers to a regulator. Its name is usually in small print on a terms page.
- The middleware, or Banking-as-a-Service (BaaS) provider — the software layer between the two. It moves the money, handles onboarding and compliance tooling, and keeps the ledger of who owns which part of the balance.
Your convenience comes from the first. Your legal protection, if any, comes from the second. And the record of what you personally own frequently lives in the third — which is the part almost nobody checks, and the part that failed.
Where it goes wrong: the ledger, not the bank
Deposit insurance protects you when a bank fails. It does not protect you when the software company sitting between you and the bank fails. Those are different events, and the marketing rarely distinguishes them.
Synapse was a BaaS middleware provider serving consumer apps including the savings app Yotta. It filed for Chapter 11 bankruptcy in April 2024. The court-appointed trustee later reported that customers of the fintechs using Synapse had roughly $265 million in balances, while the partner banks held roughly $180 million against those accounts — a shortfall of up to $96 million, as reported by NBC News. Around 85,000 Yotta customers lost access to their money. Debit cards stopped working, transfers stopped processing, and some people waited more than a year for partial recovery.
No bank failed. Deposit insurance was never triggered, because it insures the failure of a chartered institution, not the collapse of a bookkeeping layer. The funds were pooled in accounts at real, solvent, insured banks — but only Synapse held the ledger saying which dollars were whose, and its bankruptcy destroyed the ability to reconstruct that. CNBC's account of the episode is worth reading in full if you keep savings in an app.
The lesson generalises well beyond one company: "FDIC-insured" on a fintech landing page describes where the money is parked, not who is obliged to prove it is yours.
The partner banks came under pressure too
The bank side of the model has also tightened. Blue Ridge Bank built a large BaaS business — around 50 fintech partnerships — and entered a consent order with the US Office of the Comptroller of the Currency in January 2024 over anti-money-laundering programme failings, which barred it from adding new fintech relationships without permission. It cut the partnerships back, rebuilt its risk function, and exited the business entirely; its chief executive Billy Beale put it as "we just threw BaaS out the door", per Banking Dive. The consent order was later terminated and the bank returned to conventional community banking.
That matters to you as a customer for one practical reason: when a partner bank exits, the apps built on top of it have to migrate to a new one, and migrations are exactly when access interruptions and record-keeping gaps appear.
What embedded finance is genuinely good at
None of this makes the category bad. The products that work best share a shape: the financial service is an extension of data the platform already holds, not a general-purpose bank account.
- Merchant and seller lending — a marketplace can see your sales history, so it can underwrite a working-capital advance faster and with less paperwork than a bank that starts from nothing.
- Instant payout of earnings — for gig and platform workers, being paid at the end of a shift instead of at the end of a fortnight is a real cash-flow improvement.
- Point-of-sale instalments — transparent, fixed-term instalments on a large purchase can be cheaper than revolving credit, provided the term is genuinely fixed and interest-free.
- Business accounts inside the tool you already run on — reconciliation is far less painful when payouts and bookkeeping share one system, which is why platform-native business accounts have stuck.
What tends to work badly is the general savings account with an unusually attractive rate, offered by a brand with no banking history, several intermediaries deep. That is the exact shape that failed.
Five questions worth asking before you keep money there
- Which regulated entity holds the deposit? It should be named, in plain text, on the app's own site. If you cannot find a bank's legal name in under two minutes, treat that as the answer.
- Is this a deposit or a stored balance? An e-money or payments balance is a different legal product from a bank deposit and usually carries safeguarding rules rather than deposit insurance.
- Who keeps the ledger? If the platform and the bank do not each hold a record of your individual balance, you are relying on a third party's bookkeeping surviving that party's insolvency.
- What is the recovery route if the app disappears? A good provider can tell you which bank to contact directly. If the only route back to your money is the app itself, the app is a single point of failure.
- How much would you be comfortable losing access to for six months? Not losing — losing access to. That was the real experience in 2024, and it is the more likely failure mode.
Where to put the balance instead
For money you need reliably, the boring version is safer: an account with a bank that holds its own licence, where the protection scheme and the account provider are the same institution. Our guides on how to judge a neobank's safety and on what actually separates digital banks from traditional ones go through how to verify that, and the bank account switching guide covers moving without breaking direct debits.
If you are running a business rather than a household, the trade-off is different and often favours the platform-native option — see the best business neobanks for where that holds up.
The verdict
Embedded finance has made financial products more accessible and much better fitted to the moment you need them, and it is not going away. The consumer risk is not that the technology is flimsy; it is that the brand on the app and the institution holding the money are different, and the chain between them can be longer than it looks.
Use it for what it is good at — credit and payouts attached to a platform that already knows your business — and keep the balance you actually depend on with an institution whose name is on both the licence and the account. Understanding how neobanks make money and what open banking permits makes the rest of these arrangements much easier to read.
This is general information, not financial advice.
Banks mentioned in this article
Affiliate disclosure: The links above are affiliate links. We may earn a commission at no extra cost to you.


