Embedded finance is what happens when banking stops being a place you go and becomes a feature of something else you are already doing. When a ride-hailing app pays its drivers instantly, when an online store offers instalments at checkout, or when an accounting tool lets a small business open an account without visiting a bank, that is embedded finance at work. This explainer sets out how the model is structured, which participants play which role, and where the genuine risks lie.
What is embedded finance, precisely?
Embedded finance is the integration of regulated financial products — payments, lending, insurance, or deposit-style accounts — directly into a non-financial digital product, so the user never has to leave that experience to transact. The distinguishing feature is context: the financial service appears at the exact moment it is useful, inside a journey the customer came for another reason. A standalone banking app is a destination; embedded finance is a capability woven into someone else’s destination.
The idea is not entirely new — store cards and airline co-branded credit have existed for decades — but modern embedded finance is defined by application programming interfaces (APIs) that let a software company plug in a financial function in weeks rather than build a bank. The shift is as much about distribution as technology: the company that owns the customer relationship can now attach a financial product to it without becoming a licensed institution itself.
How the value chain is structured
Behind almost every embedded-finance experience sits a layered supply chain. Understanding who occupies each layer is the key to understanding the model, because responsibility and economics are split across them.
| Layer | Role | Typical participant |
|---|---|---|
| Licensed provider | Holds the banking, e-money or lending licence; provides the regulated rails, accounts and safeguarding | A bank or e-money / payment institution |
| Enabler / middleware (BaaS) | Exposes the licensed capability through developer-friendly APIs; handles onboarding, ledgering and compliance tooling | A Banking-as-a-Service or infrastructure provider |
| Distributor / brand | Owns the customer, the interface and the moment of sale; embeds the product into its own journey | A retailer, marketplace or SaaS platform |
| End customer | Experiences the financial product as a native feature of the brand | A consumer or business user |
The critical point is that the layers do not share responsibility equally. The distributor captures the customer relationship and much of the perceived value, but the licensed provider carries the regulatory burden. Banking-as-a-Service, the supply side of this model, is the wholesale provision of a licensed institution’s capabilities to non-banks — it is what makes embedding possible at scale. Because embedded payments sit at the heart of most of these journeys, the mechanics overlap heavily with the account-access and payment-initiation plumbing described in our explainer on how open banking works.
What actually gets embedded
Embedded finance is an umbrella. The main product families are:
- Embedded payments. Accepting and disbursing money inside a platform — checkout, marketplace pay-ins and pay-outs, and instant settlement for gig workers or sellers.
- Embedded lending. Offering credit at the point of need: instalment plans and buy-now-pay-later at checkout, or working-capital advances offered to a marketplace’s sellers based on their transaction history.
- Embedded insurance. Presenting a relevant cover at the moment of purchase — travel cover with a flight, device protection with electronics, or shipment cover with a logistics booking.
- Embedded accounts and cards. Issuing a store of value or a payment card to a platform’s users, so funds and spending stay within the ecosystem.
Why is embedded finance growing?
Several structural forces push in the same direction. On the technology side, the spread of open APIs and cloud infrastructure has driven the cost and time of integrating a financial product sharply down. On the regulatory side, licensing regimes for e-money and payment institutions in many jurisdictions created a class of regulated entities that could specialise in providing rails to others. And on the demand side, platforms discovered that a well-placed financial feature can lift conversion, deepen engagement and open a revenue line adjacent to their core business.
For the distributing brand, the appeal is contextual data and timing: a marketplace knows a seller’s cash flow, so it can offer credit precisely when it is useful and price risk with information a traditional lender would not have. For the licensed provider, embedding offers reach into customer segments it could not efficiently acquire on its own. That mutual benefit is the engine of the model.
How the economics work across the stack
Because value and responsibility are split across the layers, so is the money. The licensed provider typically earns from the underlying regulated activity — interchange or scheme fees on card and payment volume, net interest or fees on credit, premium share on insurance — and often charges the enabler for access to its licence and balance sheet. The enabler, or Banking-as-a-Service provider, monetises the middleware: platform fees, per-transaction or per-account charges, and revenue share on the products it makes easy to embed. The distributing brand captures the customer-facing upside — a share of transaction economics, higher conversion, and the retention value of keeping users inside its ecosystem.
That split explains a recurring tension in the model. The brand owns the relationship and much of the perceived value, but it depends on partners it does not control for the regulated capability. The licensed institution carries the compliance burden but is a step removed from the customer. Sustainable arrangements are the ones where each layer’s economics genuinely reflect the risk it bears — and where the contract makes that allocation explicit rather than leaving it to be discovered when something goes wrong. Analysts studying the sector pay close attention to which layer captures durable margin, because that tends to reveal where the real leverage in the model sits.
Which businesses are embedding finance?
Embedded finance is easiest to understand through the verticals adopting it, because the relevant financial product follows naturally from each platform’s core transaction. Marketplaces and e-commerce platforms embed payments and seller financing, using transaction history to underwrite advances that a traditional lender could not price as well. Ride-hailing, delivery and logistics platforms embed instant pay-outs and cards for their workers, and sometimes insurance tied to a trip or shipment. Software-as-a-service tools — accounting, invoicing, payroll, practice management — embed accounts, payments and lending so that a small business can manage money without leaving the tool it already runs its operations in. Property, travel and healthcare platforms embed payments and point-of-sale insurance at the moment a booking or purchase is made.
The common thread is data and timing. A platform sees a slice of its customers’ activity that a bank does not, and it sees it at the precise moment a financial product becomes relevant. That contextual advantage — not a lower cost of capital — is what lets embedded finance offer products that feel more useful and better-timed than a standalone equivalent. It is also why the model tends to work best where the platform already has a high-frequency, transactional relationship with its users rather than an occasional one.
Where the risks and headwinds sit
The same layering that makes embedded finance flexible also makes it fragile if governance is weak. Three risk themes recur.
Regulatory perimeter and liability. The licensed institution remains accountable for the regulated activity even when a partner controls the interface. Supervisors in several markets have made clear that a bank cannot outsource its responsibility for anti-money-laundering controls, safeguarding of customer funds, or fair treatment of customers. Where the division of duties between bank, enabler and brand is vague, problems surface quickly — which is one reason financial-crime and compliance technology has become integral to these arrangements.
Operational dependency. An embedded product depends on a chain of third parties. If the enabler has an outage, or the underlying bank withdraws a programme, the brand’s financial feature can stop working with little the brand can do directly. Concentration on a small number of infrastructure providers is a systemic consideration regulators watch.
Consumer clarity. When finance is frictionless and contextual, customers may not fully register that they are taking on credit or an insurance obligation. Ensuring disclosures, affordability checks and complaint routes work inside an embedded flow is a live area of supervisory attention, particularly for point-of-sale credit.
How analysts approach the sector
Because embedded finance cuts across banking, payments, insurance and software, sizing it is genuinely difficult and any single headline number should be treated with caution. A more defensible approach segments the market by product type (payments, lending, insurance, accounts), by distribution vertical (retail, mobility, SaaS, healthcare), and by layer of the stack (licence, enabler, distributor), then studies each cell for participant types, unit economics and regulatory exposure rather than reaching for a single total. This structural, segment-first method is the same discipline we set out in our guides to market sizing and how to read a market report.
For business readers, the practical questions are consistent: which layer are you in, who holds the licence, how is liability allocated in the contract, and how resilient is the chain of providers beneath the experience? Answer those, and the marketing gloss on embedded finance gives way to a model you can actually evaluate. For related coverage, see the banking and financial services hub.
