Embedded finance is when a company that is not a bank, a retailer, an airline, a ride-hailing app or a software platform, builds banking, payments, lending or insurance straight into its own app, so you never visit a bank to use them. The brand is on the screen, but a licensed bank still holds the money behind it.

How embedded finance actually works

The model has two layers. In front is the brand you see and trust. Behind it is a regulated bank that holds the charter, takes the deposits and carries the legal obligations. Connecting them is a set of software links, usually called banking-as-a-service, or BaaS, that lets the brand offer accounts, cards or loans without becoming a bank itself.

So when a shopping app offers you a debit account or a checkout loan, it has not been granted a banking license. It has rented access to one. The appeal is obvious on both sides: the brand adds a financial product and a new revenue line without years of regulatory work, and the bank picks up deposits and fee income it would not otherwise reach.

Where you have already used it

Embedded finance is more common than the term suggests. The buy-now-pay-later option at an online checkout is embedded lending. A debit account offered inside a gig-work or delivery app is an embedded bank account. A store card that lives entirely in a retailer's app, or insurance offered the moment you book a flight or buy a phone, are embedded finance too.

What these share is that the financial product appears at the exact moment you need it, inside an app built for something else. That convenience is the whole pitch, and it is real.

What it means day to day

For most people, embedded finance is a convenience worth using with eyes open. Paying in installments at a checkout, tapping a card issued through an app, or buying cover at the point of sale are all low-stakes when the sums are small and the money moves straight through. The calculation changes when an app invites you to hold a balance, to treat it as a savings account, or to route your paycheck through it. That is when the question of which bank stands behind the feature, and whether your name is on the account there, stops being academic.

Embedded finance versus banking-as-a-service

The two terms get used interchangeably, but they describe different layers. Embedded finance is the outcome you see: a financial product living inside a non-financial app. Banking-as-a-service is the infrastructure underneath that makes it possible, the regulated bank exposing its systems through software so partners can plug in. Every embedded-finance product runs on some form of BaaS. Not every BaaS arrangement is consumer-facing; some sit between businesses. Keeping the two straight helps, because the risks, from compliance to the recordkeeping failures that have hurt customers, mostly live in the BaaS layer where money and responsibility change hands.

The catch: who holds your money

The split between the brand and the bank is where the risk lives. Your money does not sit with the app. It sits in an account at the partner bank, and the protections that come with it, including federal deposit insurance, depend on that bank, not on the brand you dealt with.

That distinction is easy to miss, because the app never mentions it. Deposit insurance from the Federal Deposit Insurance Corporation covers you if the insured bank fails. It does not cover you if the non-bank middleware or the app itself fails, even though that is the company you actually handed your money to. For how that coverage works, see how FDIC insurance works.

What the Synapse collapse exposed

The gap stopped being theoretical in 2024. Synapse Financial Technologies, a middleware company that connected about 100 fintech apps, including Yotta, Juno and Dave, to partner banks, filed for bankruptcy in April 2024. Roughly $265 million of end-user funds were frozen, and customers were locked out of their accounts from May 2024.

The reason was the plumbing. Synapse moved customer money among several partner banks and kept the record of whose money was where. The banks were not required to hold those individual records, so when Synapse failed, no one could reliably reconstruct the ledgers. The court-appointed trustee, Jelena McWilliams, identified a "$65 to $95 million shortfall" between the Synapse, bank and fintech records. Because the banks themselves had not failed, deposit insurance did not step in.

The regulators' response

Regulators took note. In September 2024 the FDIC proposed a rule, "Recordkeeping for Custodial Accounts," published in the Federal Register on October 2, 2024. It would require banks that hold these pooled custodial accounts to keep records identifying each beneficial owner and that owner's balance, and to reconcile those records at least once each business day. FDIC director Jonathan McKernan said plainly that Synapse's failure resulted in significant hardship for consumers.

The proposal drew opposing pressure: some lawmakers pushed the FDIC to finalize it, while fintech and community-bank groups argued its scope was too broad. The debate over exactly how to close the gap was still live into 2025. The simpler lesson for a customer did not wait for a rule: convenience and deposit insurance are not the same thing.

How to think about using it

Embedded finance is genuinely useful, and for everyday payments the risk is small. A reasonable rule of thumb is to know which regulated bank actually holds the money, and whether it is held in an account in your name that federal insurance would cover directly, before leaving a balance inside a finance feature in a non-bank app. If the app cannot answer that clearly, that is itself worth knowing.