Embedded Finance in Practice: Who Stands Behind Brand Financial Products

Concept

🔗 Related

Embedded finance

Embedded finance is easiest to understand through brands that have already embedded financial services. Shopify gives sellers an account and credit, Uber gives drivers a card, Ramp and Brex offer corporate cards, Toast provides loans to restaurants. None of these brands is a bank: behind each product stands someone else's charter, a licensed provider, and issuance infrastructure. The brand owns the customer and interface, while the bank holds the license, money, and liability.

For anyone building such a product, these cases read like an assembly blueprint. The pattern repeats: brand on top, beneath it a program manager or BaaS platform (Stripe, Marqeta, Branch), and at the foundation—a sponsor bank with a banking charter (Celtic, Column, Sutton, Evolve, WebBank, Fifth Third). Changing the vertical—account, card, credit—changes the provider and bank, but not the construction itself.

🍓 Your own license is almost never needed here. You need a sponsor bank and issuer-processor, and then everything comes down to two questions: who is responsible to the regulator (the bank) and who owns the customer (the brand). A breakdown of the model itself is in the Embedded finance article.

How It Works

A typical assembly is built in three layers. The sponsor bank holds the charter, FDIC insurance, and answers to the regulator—these are Celtic, Column, Sutton, Evolve, WebBank. The issuer-processor and program manager (Marqeta, Galileo, Stripe, Branch) provide card issuance, ledger, and API. The brand builds the storefront: onboarding, application, and support. Customer funds are held at the bank, not with the brand.

The economics work on distribution: the bank earns on deposit interest and a share of interchange, the processor on transactions, the brand on customer retention and additional revenue. The closer the brand gets to its own volume, the more the economics of intermediaries squeeze—which is why large players eventually pull functions in-house (McKinsey on embedded finance and BaaS).

Cases

🔗 Related

BaaS and sponsor banks

What exactly each brand embeds and whose banking charter stands behind the product (as of mid-2026; partner banks change over time).

• Shopify — Shopify Balance account and Shopify Capital credit directly in the store admin. Balance is built on Stripe Treasury, funds are placed with Fifth Third Bank N.A. (Member FDIC), the Balance card is issued by Celtic Bank. Shopify Capital is issued through Stripe with participation from Evolve Bank & Trust and Celtic Bank. Shopify does not hold its own license.
• Stripe — here the brand itself became infrastructure. Stripe Treasury gives platforms embedded accounts, Stripe Issuing—card issuance; behind them stand partner banks (Goldman Sachs, Citi, Cross River, Fifth Third, and others) and issuer banks like Celtic. This is an example of how embedded finance is already sold as a service for other brands—see BaaS and sponsor banks.
• Uber — Uber Pro Card, a debit Mastercard for drivers with instant access to earnings. Banking services are provided by Branch, the card is issued by Evolve Bank & Trust, issuance technology is provided by Marqeta. The financial product here is a driver retention tool, not a separate business.
• Ramp — corporate charge card and spend management. Ramp Visa Corporate Card is issued by Celtic Bank, Ramp Visa Commercial Card by Sutton Bank, cards for global companies by Column N.A. Ramp itself does not hold deposits or issue cards—it builds software on top of banks.
• Brex — corporate cards and business accounts for startups. Issuance relies on regulated banks Column N.A. and Sutton Bank, processing goes through Mastercard and Visa networks. Deposits and charter are with partner banks, product and customer with Brex.
• Toast — POS for restaurants and Toast Capital loans from $1K to $300K. Loans are issued by WebBank; repayment is a fixed percentage of daily card revenue, with no compound interest or personal guarantee. Access to restaurant sales data makes underwriting embedded.

What You Need to Replicate

🔗 Related

BIN sponsorship · issuer-processors · BaaS and sponsor banks · US sponsor banks overview

Building a similar product starts not with a license, but with choosing a vertical. Account and card—that's sponsor bank plus issuer-processor; credit—a partner bank ready to issue loans (like WebBank for Toast); cards under your own brand—BIN sponsorship (BIN sponsorship and issuer-processors).

Next—a legal entity, ready KYC/KYB and AML policy package, integration with the processor, and agreement with the sponsor bank. Through a vendor, go-live takes weeks, not years; the bank takes a share of interchange and access fee. Partnership requirements and economics are detailed in BaaS and sponsor banks and US sponsor banks overview.

What to Watch For

🔗 Related

BaaS-middleware

• Concentration on one bank. Evolve stands behind products from Shopify, Uber, and many others—a common partner bank becomes a common point of failure. It's important to understand which bank your product depends on and whether there's a backup.
• Where money is insured. FDIC pass-through operates at the partner bank level, within $250K per depositor, and covers bank failure but not intermediary failure. The Synapse collapse in 2024 showed how customers lose access to funds when middleware fails—see BaaS-middleware.
• Whose customer and whose data. The brand owns the customer relationship but operationally depends on the provider. Migration between banks (as with Shopify and Mercury) is a regular occurrence and is planned for in advance.

Applicable Regulation

🔗 Related

Embedded finance · HEVN

There is no separate "embedded finance" license—each product operates under the rules of its sector: accounts and cards under banking, credit under lending. In the US, this is the supervisory regime for third-party partnerships: the bank bears responsibility for the brand partner, and risk management must be commensurate with the program's significance (OCC Bulletin 2023-17).

The principle is consistent across the entire cluster: you can conduct activity under someone else's license, but responsibility remains with the license holder. For the brand, this means the bank tightly controls the program, and that's the normal price of a quick launch. The full model is in Embedded finance; business banking via API follows the same logic—in HEVN.

Key factual claims

• What exactly each brand embeds and whose banking charter stands behind the product (as of mid-2026; partner banks change over time).