Embedded finance
Also known as: embedded payments, embedded lending, embedded banking, contextual finance
Embedded finance means financial services (payments, loans, accounts, cards, or insurance) built directly into a non-financial product, such as a ride-hailing app paying drivers instantly or an e-commerce platform offering merchant loans.
While it's often framed as every company becoming a bank, the reality is narrower: the brand owns the customer experience while a licensed partner quietly does the regulated work. When that partnership breaks, customers learn the difference quickly.
Embedded finance, explained at three levels
At home
Embedded finance works like a coffee shop inside a bookstore: you get the coffee without leaving the store, but a separate company runs the café. When your ride-share app pays you instantly, your online store offers a loan, or your airline sells travel insurance at checkout, the app provides the screens while a licensed bank, lender, or insurer does the regulated work behind them. You never visit a separate bank.
At work
Embedded finance means a non-financial company offers financial products, such as payments, accounts, cards, loans, or insurance, inside its own software. It doesn't become a bank. Instead, it partners with licensed providers, often through Banking-as-a-Service platforms, while keeping the customer experience under its own brand. Businesses care because financial features add revenue per customer, make their software harder to leave, and use data they already hold.
At home
Behind the friendly app sit three layers. The brand you see designs the screens. A technology provider connects the app to financial services through APIs. A regulated partner, usually a bank, licensed lender, or insurer, holds the money, issues the card, or makes the loan. Whether your balance is protected by deposit insurance depends on how that partner holds the funds and keeps its records, not on the app's brand, so the partner's name in the terms is the one that matters.
At work
Embedded finance products fall into a few types: embedded payments, such as checkout and payouts inside a platform; embedded lending, such as merchant cash advances; embedded accounts and cards; and embedded insurance at the point of sale. Lending is often the most valuable, because the platform sees real-time sales, bookings, or invoices and can underwrite better than a bank working from annual statements. The trade-offs are shared regulatory exposure, fraud and credit risk, and dependence on licensed partners who can change terms or exit.
At home
Embedded accounts are often held in pooled 'for benefit of' accounts at a partner bank, with a middleware company keeping the ledger of who owns what. If that ledger is wrong and the middleware fails, the bank may not know which customer owns which dollar. In my view, that's exactly what made the Synapse collapse so painful: the money existed, but the records didn't match.
At work
US regulators responded to BaaS failures with enforcement actions against partner banks and a proposed FDIC recordkeeping rule for custodial accounts. In Canada, payment service providers holding customer funds became subject to Bank of Canada supervision under the Retail Payment Activities Act, including fund safeguarding requirements from September 2025. Any embedded finance roadmap should include reconciliation controls, partner due diligence, and a plan for what happens if a partner exits.
Real-world examples
At home
Lena drives for a delivery app that offers an instant payout card. She gets her earnings minutes after each shift instead of waiting a week. When she checked the fine print, she saw the card was issued by a partner bank, not the delivery company itself.
At work
Carlos is a product manager at a software company serving independent gyms. His team added embedded payments and small cash advances based on each gym's membership revenue. Gym owners stayed longer because the software now handled their money too, and the payments revenue funded new features.
Common confusions
- If an app offers a bank account, the app is a bank. — Usually a licensed partner bank or financial institution holds the funds, and the app provides the interface.
- Money in embedded accounts is always deposit-insured. — Insurance depends on the account structure and accurate records. It isn't automatic just because a bank is involved.
- Embedded finance is only about payments. — It covers lending, cards, accounts, insurance, and investing, anywhere a financial service is built into another product.
For analysts
Embedded finance can add a revenue line, but it also adds a regulator to your business, indirectly at first. I'd require a partner-exit plan and daily reconciliation in any business case. If you can't explain who owns each customer dollar at any moment, you're not ready.
History & origin
Embedded payments arrived first, as platforms like Uber and Airbnb hid payments inside their apps in the late 2000s and early 2010s. Embedded lending followed: Shopify launched Shopify Capital in 2016, offering cash advances to merchants based on their sales data, and Amazon offered seller loans. By the late 2010s, Banking-as-a-Service providers let almost any software company offer accounts and cards through partner banks. The 2024 collapse of the middleware firm Synapse, which left thousands of end users unable to access their money for months, was a wake-up call for the whole model. In my opinion, embedded finance is a genuinely useful idea that grew faster than the controls needed to make it safe.