Embedded Finance and Payments: What Operators Actually Need to Build

Embedded finance transactions in the US will reach $7 trillion in 2026. Global embedded finance revenue is projected at $230 billion by 2025, with B2B embedded payments accounting for $2.6 trillion of that. The numbers are real, but the infrastructure behind them is frequently misunderstood — particularly the distinction between Banking-as-a-Service (BaaS) and embedded finance, and what building each actually requires.

Most operators planning to embed financial products make the same error: they start with the customer experience they want to deliver and work backward, only to discover mid-build that the licensing requirements, banking partner constraints, and technical dependencies were never mapped into the project plan. The result is Solaris-style compliance failures (Germany’s largest BaaS platform raised emergency capital in early 2025 to address AML control deficiencies) or long-delayed launches when sponsor banks apply more stringent conditions than anticipated.

BaaS vs Embedded Finance: The Distinction That Matters

These terms are used interchangeably in vendor marketing, but they describe different positions in the value chain.

Banking-as-a-Service (BaaS) is infrastructure provisioning. A BaaS provider — Marqeta, Stripe Treasury, Unit, Bond, Synctera, Treasury Prime — supplies the underlying banking capabilities: account ledgers, payment rails access, card issuing, and regulatory licensing through a sponsor bank relationship. The BaaS provider holds the technical and in some cases regulatory infrastructure; the operator distributes it under their brand.

Embedded finance is the distribution model. An operator embeds financial products (a business account, a lending product, a card) into their non-financial platform — Shopify embedding merchant lending, Uber embedding driver earnings access, Grab embedding consumer credit. The financial product enhances the core platform’s value proposition and creates monetization independent of the core transaction fee.

The practical distinction for operators: if you are a platform distributing financial products to your user base, you’re in embedded finance. If you are building infrastructure that other platforms will use to embed financial products, you’re in BaaS. The technical and regulatory requirements are materially different, and conflating the two leads to misspecified architectures.

The Technical Stack: What You Actually Need to Build

An embedded finance product (let’s say a business account with a debit card) requires five infrastructure layers:

1. Sponsor Bank Relationship

In the US, embedded finance products that hold customer funds must be backed by an FDIC-insured depository institution. The sponsor bank provides the charter, the regulatory umbrella, and in some cases the payment rails access (ACH, Fedwire). This is not a vendor selection — it’s a regulated partnership that requires due diligence on the bank’s program management capabilities, examination history, and concentration risk policies.

Sponsor banks have become more cautious since the 2024 regulatory scrutiny of BaaS partnerships. The OCC and FDIC issued joint guidance in 2024 requiring sponsor banks to conduct more rigorous oversight of their fintech partners, including third-party risk management programs and real-time transaction monitoring. Smaller sponsor banks (Blue Ridge Bank, Evolve Bank & Trust) that took on too many BaaS programs faced enforcement actions. The pool of sponsor banks willing to take on new programs has narrowed, and deal timelines have extended from 3–6 months to 6–12 months.

2. BIN Sponsorship and Card Program Setup

A debit or prepaid card requires a BIN (Bank Identification Number) licensed from Visa or Mastercard. BINs are held by licensed financial institutions — either the sponsor bank or a BIN sponsor who is a principal member of the card network. The BIN sponsor is liable to the card network for all transactions processed under that BIN.

Marqeta’s 2024 acquisition of TransactPay (a European BIN sponsor) illustrates the infrastructure value of controlling BIN sponsorship directly. For most operators, the practical path is to use a card issuing platform (Marqeta, Stripe Issuing, Adyen Issuing) that manages the BIN sponsorship relationship on their behalf in exchange for per-card and per-transaction fees.

The key commercial terms to negotiate in a BIN sponsorship arrangement:

• Per-card fee (typically $0.50–$2.00/month per active card)
• Per-transaction fee (typically $0.02–$0.10 per transaction, separate from interchange)
• Interchange passthrough rate (how much of the earned interchange flows to the operator)
• Program volume minimums and ramp schedule

3. Ledger Architecture

Every embedded finance product requires a ledger — a system of record that tracks account balances, pending transactions, holds, and settlements. This is where most operators underestimate complexity. The ledger must handle:

• Real-time balance updates on debit card spend
• ACH credit and debit postings with appropriate hold periods
• Float management (the period between when funds are received and when they settle)
• Reconciliation against the sponsor bank’s actual account balances
• Regulatory reporting requirements (CTRs, SARs if you’re in the money transmission space)

Building a ledger from scratch is a multi-year engineering project. The practical options are: using the ledger embedded in a BaaS platform (Unit, Synapse pre-bankruptcy, Treasury Prime), building on top of a core banking platform (Thought Machine, 10x Banking), or using a dedicated ledger vendor (Synctera, Mambu). Each has different capabilities for real-time balance accuracy, transaction throughput, and regulatory audit trail requirements.

4. KYB/KYC and Compliance Infrastructure

Embedded business accounts require KYB (Know Your Business) verification for each enrolled entity — not just the individual user. KYB involves verifying business registration, beneficial ownership (all owners with 25%+ equity), and in higher-risk cases, source of funds. The FATF recommendations and FinCEN’s CDD Rule in the US require financial institutions (and by extension their BaaS partners) to conduct and document this verification.

The KYB stack is different from consumer KYC. For operators:

• Business entity verification: Secretary of State filings, EIN verification, registered agent confirmation. Vendors include Middesk, Veriff (business tier), and LexisNexis RiskView Business.
• Beneficial ownership: Identity verification of each beneficial owner at the individual level (government ID + liveness check). Same vendors as consumer KYC (Jumio, Onfido, Persona).
• Ongoing monitoring: Sanctions screening (OFAC, UN, EU lists), adverse media monitoring, and periodic re-verification for higher-risk accounts (AML obligations).

The compliance cost per business account onboarded ranges from $5–$50 depending on risk tier and automation level. For embedded finance programs targeting SMEs, this cost must be modeled into unit economics from day one — it is not recoverable through interchange alone at low account values.

5. Regulatory Licensing

Depending on the product and jurisdiction, the operator may need their own licenses in addition to relying on the sponsor bank’s charter:

• Money transmitter license (MTL) — Required in most US states if the operator holds funds in transit between parties, rather than simply providing access to a bank account.
• Consumer lending license — Required for credit products in most US states; at the federal level, lending through a bank partner (using the bank’s charter) can preempt state licensing requirements, but recent court decisions on “true lender” doctrine have complicated this.
• E-money institution (EMI) license — The EU/UK equivalent for holding stored value. Required for most embedded wallet products; MiCA adds an additional layer for crypto-adjacent products.

Real-World Deployments: What the Economics Look Like

Shopify Balance: Shopify’s embedded business account for merchants. Built on Stripe Treasury (which in turn relies on sponsor bank relationships). Shopify Capital originated $4.2 billion in merchant cash advances and loans in 2025. The lending revenue ($205 million in 2024) is cross-subsidized by Shopify’s payments and SaaS revenue, which allows Shopify to offer capital at rates that standalone lenders couldn’t sustain profitably.

Grab PayLater: Grab’s BNPL product, licensed as a digital credit product under MAS (Monetary Authority of Singapore) regulations. Requires a moneylender license in Singapore, separate from Grab Financial’s broader e-money license. PayLater is embedded in the Grab app at checkout for food delivery, ride-hailing, and merchant payments. The credit underwriting uses Grab’s transaction history as a primary data source — a structural advantage over standalone lenders who lack the behavioral data.

Uber Money: Uber’s driver earnings access product, which allows drivers to access their day’s earnings in real time rather than waiting for weekly ACH. Built on Marqeta’s issuing infrastructure with a Visa debit card. The product reduces driver churn (a key operational metric for Uber) by solving a real liquidity problem for gig workers who live paycheck-to-paycheck. The unit economics work because Uber is not primarily monetizing the card — it’s monetizing driver retention.

The Regulatory Risk That Operators Underestimate

The single largest risk in embedded finance is sponsor bank compliance failure. When a sponsor bank faces regulatory enforcement (as Blue Ridge Bank did in 2023, and as multiple other BaaS sponsor banks did through 2024), fintech programs operating under that bank’s charter are suspended or migrated — often with little notice and significant operational disruption.

Operators who build on a single sponsor bank have concentrated regulatory risk. The mitigation is either:

• Multi-bank program architecture (different products or user segments on different banks), which adds reconciliation complexity
• Working with BaaS platforms that have multi-bank redundancy built in (Unit and Synctera both offer multi-bank architectures)
• Pursuing direct licensing (expensive and slow, but eliminates sponsor bank concentration risk for at-scale programs)

Embedded finance at scale is not a product decision — it’s a regulatory architecture decision. The operators who get it right design the compliance and bank partnership structure before specifying the product experience, not after.