Glossary

Embedded Finance

Integrating financial services like payments, lending, or insurance directly into non-financial apps and platforms.

Key Takeaways

  • Embedded finance integrates financial services directly into non-financial platforms, letting users access payments, lending, and banking without leaving the apps they already use. It relies on Banking-as-a-Service infrastructure to deliver these capabilities via APIs.
  • The technology stack consists of three layers: licensed sponsor banks, BaaS middleware platforms that expose banking functions as APIs, and the non-financial apps that embed those services for end users. Companies like Stripe, Unit, and Plaid power this infrastructure.
  • Bitcoin and stablecoin rails are extending embedded finance beyond traditional banking: platforms can now embed instant cross-border payments and settlement using cryptocurrency infrastructure without requiring users to interact with exchanges or wallets directly.

What Is Embedded Finance?

Embedded finance is the integration of financial services: payments, lending, insurance, banking, and investments: directly into non-financial software platforms and digital experiences. Instead of redirecting users to a bank or financial institution, the financial product appears natively within the app where the user already spends their time.

When a Shopify merchant receives a loan offer inside their dashboard, or an Uber driver gets instant payouts to a branded debit card, or a shopper splits a purchase into four installments at checkout: that is embedded finance. The financial service meets the user at the point of need, not the point of bank.

The concept is distinct from Banking-as-a-Service (BaaS), though the two are deeply intertwined. BaaS is the delivery mechanism: the APIs and infrastructure that make embedding possible. Embedded finance is what gets delivered: the financial product experienced by the end user inside a non-financial context. Open banking regulations have further accelerated this trend by mandating that banks expose customer data through standardized APIs.

How It Works

Embedded finance operates through a three-layer architecture that separates regulatory compliance, technical infrastructure, and user-facing distribution.

The Three-Layer Stack

  1. Sponsor banks hold the banking charter and regulatory licenses. They provide FDIC-insured accounts, originate loans, and ensure compliance with banking regulations. Examples include Evolve Bank & Trust, Cross River Bank, and Celtic Bank.
  2. BaaS middleware platforms sit between banks and applications. They expose banking functions (account creation, card issuing, money movement, lending) as modular APIs. Platforms like Unit, Treasury Prime, Synctera, and Galileo handle the complexity of bank integration so developers do not have to.
  3. Non-financial platforms are the consumer-facing apps that embed the services. An e-commerce platform, ride-hailing app, or SaaS tool integrates the BaaS APIs and presents financial products under its own brand.

A Typical Integration

A platform embedding financial services typically connects several specialized providers. The following pseudocode illustrates how an e-commerce platform might wire together embedded lending at checkout:

// Embedded lending integration at checkout
const checkoutSession = await createCheckout({
  merchant_id: "shop_abc123",
  amount: 1200.00,
  currency: "USD",
});

// BaaS provider pre-qualifies buyer for installment loan
const lendingOffer = await baasProvider.preQualify({
  customer_id: checkoutSession.customer_id,
  amount: checkoutSession.amount,
  // Sponsor bank originates the loan
  bank_partner: "cross_river",
});

if (lendingOffer.approved) {
  // Offer appears natively in checkout UI
  displayInstallmentOption({
    monthly_payment: lendingOffer.monthly_amount,
    term_months: lendingOffer.term,
    apr: lendingOffer.apr,
  });
}

From the buyer's perspective, the installment option appears as a native part of checkout. Behind the scenes, the platform coordinated with a BaaS provider and sponsor bank to originate a regulated loan product.

Key Infrastructure Components

The embedded finance stack relies on specialized providers for each function:

FunctionProvider ExamplesRole
Financial data accessPlaidConnects apps to users' bank accounts
Payments processingStripeFull-stack payments, treasury, and lending
Card issuingMarqeta, LithicVirtual and physical card creation via API
Money movementModern TreasuryPayment operations and reconciliation
Identity and KYCAlloyVerification and compliance automation
BaaS platformsUnit, SyncteraFull banking functions as modular APIs

Use Cases

Buy Now, Pay Later

BNPL is the most visible form of embedded lending. Providers like Klarna and Affirm integrate directly into merchant checkout flows, offering installment plans without requiring shoppers to apply for a separate credit product. Klarna processed roughly $2.8 billion in revenue in 2024, capturing approximately 35% of the global BNPL market. This model embeds a payment facilitator and lender into a single checkout experience.

Platform Lending

Shopify Capital exemplifies embedded lending for businesses. Merchants see pre-qualified loan offers directly in their Shopify dashboard, with no separate application process. Repayment happens automatically as a percentage of daily sales. Shopify originated approximately $4.2 billion in merchant financing in 2025, demonstrating how platforms with rich transaction data can underwrite credit more effectively than traditional lenders.

Gig Worker Banking

Ride-hailing and delivery platforms embed banking services for their workforce. Uber offers instant payouts, a branded debit card with fuel cashback, and in-app financial management. Over 70% of Uber drivers use the instant payout feature. These embedded financial products improve driver retention and reduce the platform's reliance on third-party payroll providers.

Embedded Insurance

Travel booking platforms offer trip insurance at checkout. E-commerce marketplaces embed product protection plans. Auto dealerships bundle gap insurance into financing. In each case, the insurance product appears contextually at the moment the customer is most likely to purchase it, rather than requiring a separate interaction with an insurance provider.

Embedded Crypto and Stablecoin Payments

A growing category of embedded finance uses Bitcoin and stablecoin rails instead of traditional banking infrastructure. Stripe's $1.1 billion acquisition of Bridge in early 2025 signaled the convergence: Bridge provides a single API to move value between fiat and stablecoins, enabling platforms in over 100 countries to embed real-time payments and cross-border settlement without correspondent banking relationships.

On the Bitcoin side, protocols like Spark enable non-financial platforms to embed self-custodial Bitcoin and stablecoin transactions. By providing instant settlement on a Bitcoin Layer 2 with native Lightning Network interoperability, Spark allows developers to integrate dollar-denominated Bitcoin payments into any application through an SDK: no exchange accounts, no custodial intermediaries, and no multi-day settlement cycles.

Why It Matters

Embedded finance reshapes how financial services are distributed. Instead of competing for direct customer relationships, financial institutions increasingly power experiences inside other platforms. According to Bain & Company, U.S. embedded finance transaction value is projected to reach $7 trillion by 2026, accounting for roughly 10% of all U.S. financial transactions.

For platforms, the economics are compelling. SaaS companies that add embedded financial services can increase revenue two to five times over their software-only baseline. For users, the benefit is reduced friction: financial services appear where and when they are needed, rather than requiring context switches to separate banking apps.

The convergence of embedded finance with cryptocurrency infrastructure is particularly significant for cross-border payments. Traditional embedded finance still relies on correspondent banking for international transfers, introducing delays and fees. Stablecoin-based embedded payments bypass these intermediaries entirely, enabling near-instant global settlement at a fraction of the cost. As adjusted stablecoin transaction volumes grew 91% to $10.9 trillion in 2025, this approach is moving from experimental to mainstream.

Risks and Considerations

Regulatory Complexity

Embedded finance creates layered regulatory exposure. When a non-financial platform offers banking products, questions of compliance responsibility become complex. The 2024 collapse of Synapse, a BaaS middleware firm, left approximately $85 million in end-user funds unaccounted for and over 200,000 accounts frozen. The incident prompted the FDIC to propose new rules requiring banks to maintain accurate beneficial-owner recordkeeping in custodial accounts. Multiple sponsor banks received consent orders from regulators for inadequate oversight of fintech partnerships throughout 2024 and 2025.

Counterparty and Platform Risk

Users of embedded financial products may not realize their funds are held by a sponsor bank, not the platform they interact with daily. If the middleware layer fails (as Synapse demonstrated), reconciling which funds belong to which users across multiple platforms becomes extremely difficult. The "true lender" doctrine adds further complexity: courts increasingly examine which party bears real economic risk in bank-fintech lending partnerships, regardless of how contracts are structured.

Data Privacy and Security

Embedding financial services requires sharing sensitive financial data across multiple providers. Each additional layer in the stack: platform, BaaS provider, sponsor bank, card issuer: introduces another surface for data breaches and compliance obligations. Platforms must navigate PCI DSS requirements, banking privacy regulations, and increasingly stringent data protection laws like the EU's DORA (Digital Operational Resilience Act), which took effect in January 2025.

Concentration and Lock-In

Platforms that build financial services on a single BaaS provider face significant switching costs. If that provider faces regulatory action, goes bankrupt, or changes terms, the platform's financial products may be disrupted. Diversifying across multiple providers adds engineering complexity, which is why payment orchestration layers have emerged to abstract provider dependencies.

This glossary entry is for informational purposes only and does not constitute financial or investment advice. Always do your own research before using any protocol or technology.