Embedded finance is the integration of licensed financial services — payments, lending, insurance, deposit accounts, and card products — directly into non-financial software platforms, marketplaces, and customer journeys. Rather than redirecting users to a bank or insurer, the platform delivers the financial product at the moment of need, invisibly powered by a regulated infrastructure partner. This article defines the term precisely, maps its technical architecture, surveys its principal categories and real-world deployments, and distinguishes it from the closely related but narrower concept of Banking-as-a-Service.
Embedded finance describes the distribution of regulated financial products through non-financial digital interfaces via application programming interfaces (APIs) and white-label infrastructure, such that the end user experiences the financial service as a native feature of the host platform rather than a separate product from a separate institution. The term entered mainstream usage circa 2019–2020, though the underlying concept has older roots — store credit cards and retail instalment plans are analogue precursors. Contemporary embedded finance is distinguished by its API-first delivery, the speed with which a non-financial company can go to market, and the breadth of product categories it encompasses. Embedded finance is frequently conflated with Banking-as-a-Service (BaaS), but the two operate at different layers of the stack. BaaS is a supply-side concept: it describes the technical and regulatory infrastructure through which a licensed bank or electronic money institution (EMI) exposes its balance sheet, licences, and core capabilities to third parties via APIs. Embedded finance is a demand-side outcome: it is what the end customer experiences when a vertical SaaS platform, marketplace, or consumer app embeds those BaaS capabilities into its own product surface. In practice, BaaS is typically the engine; embedded finance is the vehicle the end user sees. No single ISO standard governs the term "embedded finance" as a defined category. However, the regulatory instruments that govern each product category within it are well established: the EU's Payment Services Directive 2 (PSD2, 2015/2366/EU) covers payments and account access; the Consumer Credit Directive (2008/48/EC, being revised under CCD2) governs consumer lending; Solvency II (2009/138/EC) and the Insurance Distribution Directive (IDD, 2016/97/EU) apply to embedded insurance; MiFID II (2014/65/EU) applies where investment products are offered. In the United States, embedded finance products trigger a patchwork of federal and state-level regulation depending on category, issuer charter type, and geography. Related but distinct terms include "open banking" (the regulatory mandate compelling banks to share account data via APIs, which enables but does not define embedded finance), "vertical SaaS" (industry-specific software platforms that are a common host for embedded finance features), and "super-app" (a single application bundling multiple financial and non-financial services, common in South-East Asia).
The architecture of an embedded finance deployment typically involves three distinct layers operating in concert: the frontend platform, the BaaS middleware provider, and the licensed regulated entity. Layer 1 — The frontend platform. This is the non-financial company with the customer relationship: a restaurant point-of-sale system, a gig-economy app, an e-commerce marketplace, a payroll platform, or a vertical SaaS tool for a specific trade. The platform has distribution but lacks a financial licence and the operational infrastructure to manage regulated products. It integrates financial capabilities through APIs or SDKs provided by the BaaS layer, surfacing them inside its own user interface with its own branding. Layer 2 — The BaaS provider. The BaaS provider acts as infrastructure middleware. It abstracts the complexity of licence compliance, card scheme membership, SEPA connectivity, AML/KYC orchestration, and ledger management behind a set of developer-friendly APIs. The BaaS provider may itself hold a licence (e.g. an EMI licence) or it may operate as a technology intermediary that connects to an underlying licensed principal. It handles programme configuration, transaction routing, dispute management, and regulatory reporting on behalf of its platform clients. Critically, a capable BaaS provider can reduce a platform's time to market from years to weeks. Layer 3 — The licensed regulated entity. Ultimately, a regulated institution — a bank, an EMI, a lender, or an insurer — sits at the base of the stack, providing the licence, the balance sheet, the scheme memberships (Visa, Mastercard), and in many cases the safeguarded client funds. In some models, the BaaS provider and the licensed entity are the same organisation; in others they are separate. The lifecycle in practice. Consider a restaurant management SaaS offering embedded working-capital loans. A restaurant operator applies for credit inside the SaaS dashboard. The platform passes KYB data to the BaaS provider's underwriting API; the BaaS provider scores the merchant using revenue data it already holds from integrated payment processing; the licensed lender makes the credit decision and disburses funds to the merchant's embedded account — all within the same interface the operator uses to manage reservations and inventory. Repayment is deducted automatically from daily card settlement. The restaurant operator never visits a bank branch or a separate lender's website. This is embedded lending in a complete form. Each product category follows an analogous pattern: the financial event (a payment, a loan draw-down, an insurance trigger, a card transaction) happens invisibly within the platform's workflow, at precisely the moment of highest relevance to the user.
Embedded finance does not sit under a single regulatory regime; instead, each product category it encompasses attracts the regulation that would apply to that product regardless of its delivery channel. The embedded wrapper does not create a regulatory exemption — it only changes who the customer faces. European Union. The foundational instrument for embedded payments is PSD2 (Directive 2015/2366/EU), which requires any entity in the payment chain to hold an appropriate authorisation — a Payment Institution (PI) or Electronic Money Institution (EMI) licence — or to operate as an agent of a licensed entity. The EBA's Guidelines on Outsourcing (EBA/GL/2019/02) govern the relationship between a licensed entity and the BaaS provider or platform that operates on its behalf, imposing requirements around contractual protections, audit rights, and concentration risk. For embedded lending, the revised Consumer Credit Directive (CCD2, Directive 2023/2225/EU) tightens responsible lending obligations that apply whether credit is offered on a bank website or embedded in a checkout flow. DORA (Regulation 2022/2554/EU), applicable from January 2025, imposes ICT resilience requirements on financial entities and their critical third-party providers, directly affecting BaaS providers serving EU-regulated principals. United Kingdom. Post-Brexit, the FCA supervises embedded finance through the Electronic Money Regulations 2011, the Payment Services Regulations 2017, the Consumer Credit Act 1974 (for lending), and increasingly the Consumer Duty (PS22/9, effective July 2023), which requires firms to deliver good outcomes for retail customers regardless of whether financial products are distributed directly or through embedded channels. United States. No single federal embedded finance framework exists. Depending on product type, platforms may engage with OCC-chartered banks (which may issue cards under federal preemption), state-licensed money transmitters, state-licensed lenders, or FDIC-insured institutions acting as programme banks. The CFPB's supervisory authority extends to non-bank entities offering certain financial products, meaning platforms embedding consumer financial services may face direct examination. A consistent cross-jurisdictional theme is that regulatory responsibility cannot be fully outsourced: the licensed entity remains ultimately accountable for the conduct of the platform distributing its products.
Embedded finance encompasses five principal product categories, each with distinct mechanics and leading real-world deployments. Embedded payments is the most mature category — payment acceptance or disbursement capabilities built into a non-financial platform. Shopify Payments, Square, and Toast (restaurant POS) all embed card acceptance directly into their merchant software, eliminating the need for a separate payment gateway relationship. Disbursement-side examples include Uber and Lyft paying drivers instantly via embedded accounts (Uber Pro Card, Lyft Direct) rather than through weekly bank transfers — a product that also exemplifies embedded banking. Embedded lending integrates credit decisioning and origination at the point of need. Shopify Capital analyses merchant GMV data to offer working-capital advances within the Shopify dashboard. Klarna and Affirm embed instalment credit at e-commerce checkouts. Toast Capital offers restaurant loans underwritten using the POS operator's own revenue data. The informational advantage of the platform — it already knows the borrower's revenue, behaviour, and operational patterns — often produces superior underwriting relative to traditional lenders operating without that data. Embedded insurance attaches coverage to a purchase or activity at the moment it is most relevant. Tesla offering car insurance at the point of vehicle purchase, rideshare platforms offering per-trip driver coverage, and travel booking platforms offering trip cancellation at checkout are canonical examples. Embedded investing allows non-financial platforms to offer fractional share purchases, robo-advisory, or savings products. Acorns (round-up investing linked to debit spend) and Cash App Investing (buying equities inside a P2P payments app) are widely cited examples. Embedded banking — the issuance of accounts, IBANs, and debit or prepaid cards to a platform's users or employees — is the category most directly enabled by card issuing infrastructure and native IBAN issuance. Expense management platforms issuing employee cards, gig platforms issuing driver accounts, and B2B marketplaces holding supplier funds are all examples. Market scale. Multiple independent forecasts — including those from Lightyear Capital, Bain & Company, and Simon-Kucher — project the global embedded finance market reaching approximately $380 billion in revenue by 2029, up from an estimated $65–90 billion in 2023. The B2B segment (embedded finance for business users within vertical SaaS) is widely identified as the fastest-growing sub-segment, driven by platforms seeking to monetise the float, data, and loyalty effects that financial products generate alongside their core SaaS revenue.
Codego functions as the regulated BaaS infrastructure layer that enables non-financial platforms across Europe to deploy embedded finance programmes without building bank-grade compliance and scheme connectivity in-house. Operating under an NBB electronic-money distribution licence and pan-EU passporting, with Codego Europe SIA in active EMI authorisation, Codego holds dual BIN sponsorship on both Visa and Mastercard — an uncommon combination that gives programme partners flexibility in scheme routing and co-branding. For platforms embedding payments and card products, Codego's white-label card and card issuing infrastructure supports virtual card delivery on day one and physical card despatch within fifteen days of programme go-live. SEPA Instant and SWIFT connectivity are available from the outset, with native EU IBANs issued across six countries — removing the need for a platform to source a separate IBAN sponsor. Apple Pay and Google Pay provisioning completes within 24 hours of card issuance. For platforms requiring a more comprehensive embedded banking layer — including account management, ledger services, and multi-currency capabilities — Codego's white-label bank and core banking infrastructure provides the necessary foundation. Crypto-native platforms can extend their offering through white-label crypto card products, with stablecoin and crypto-funded cards supported via on-the-fly fiat conversion. Configuration is managed through a self-service portal, and the BaaS platform documentation is structured for integration teams rather than procurement committees. For platforms exploring which embedded finance products align with their vertical, Codego's programme scoping questionnaire maps requirements to the appropriate infrastructure components before any commercial engagement begins.