Embedded Finance: Architecture, Use Cases and How to Build It in 2026
What embedded finance is and how to build it in 2026 - architecture, embedded finance vs banking as a service, payments, lending and insurance use cases and a real build roadmap.
10 min read
5 views
Key takeaways: embedded finance in 2026 5
What to understand before you embed financial products into your platform.
- Embedded finance vs BaaS Embedded finance is what the user sees, BaaS is the infrastructure behind it, open banking is the data layer.
- Five categories Payments, lending and BNPL, banking, insurance and investing, each offered at the point of intent.
- Layered architecture Product UX, an embedded-finance API and ledger layer, a BaaS or enabler, and a sponsor bank underneath.
- Build sequence Compliance and the ledger come before the UX. Pick one use case, then expand.
- Build vs buy Start with an enabler for speed, move regulated parts in-house as volume and economics grow.
Embedded finance is how non-bank companies put financial products – payments, accounts, cards, lending and insurance – directly inside their own apps, so customers never leave to use a bank. It is the biggest structural shift in FinTech right now, and in 2026 it is moving from a growth story to default product strategy for platforms. This guide explains what embedded finance is, the architecture behind it, the main use cases and how to build it, so you can decide where it fits before you commit engineering or sign with a FinTech development partner.
In short: embedded finance is the customer-facing financial product inside a non-bank experience. Banking as a service (BaaS) is the API infrastructure that connects it to a regulated bank, and open banking is permissioned data access. You build embedded finance by choosing a use case, integrating a BaaS or enabler over a sponsor bank, owning a ledger of record and wiring KYC and AML in from the start. US embedded finance transactions are projected to reach around $7 trillion in 2026, and platform and enabler revenue is set to roughly double to about $51 billion.
What is embedded finance
Embedded finance means offering a financial service at the exact moment a customer needs it, inside a product that is not a bank. When you pay inside Uber without opening a wallet app, split a checkout into instalments on a retailer’s site or open a business account inside the software that runs your shop, that is embedded finance.
Mechanically, a platform connects to regulated financial infrastructure through APIs and surfaces the result in its own interface. The customer sees the platform’s brand and flow. The bank, the card network and the compliance machinery sit behind the scenes. The value is context: a financial product offered where intent already exists converts far better than sending the user elsewhere, and it deepens the platform’s relationship and revenue per user.
The scale is why every platform is now evaluating it. US embedded finance transaction value is projected to climb from roughly $2.6 trillion to about $7 trillion in 2026, and analysts expect embedded finance to reach 10 to 15 percent of banking revenue pools by 2030.
Embedded finance vs banking as a service vs open banking
These three terms are constantly confused. They describe different layers of the same stack.
| Term | What it is | Who sees it | Where it sits |
|---|---|---|---|
| Embedded finance | A financial product inside a non-bank experience | The end customer | The visible top layer |
| Banking as a service (BaaS) | API infrastructure connecting platforms to a regulated bank | Hidden from the customer | The infrastructure layer |
| Open banking | Permissioned access to bank account data via API | Hidden, consent-based | The data layer |
The simple rule: embedded finance is what the user sees, BaaS is the infrastructure behind it and open banking is how data flows. A single embedded-payments feature can rely on all three at once. You design the embedded experience, you buy or build the BaaS connection and you use open banking where you need account data.
Why platforms are adding embedded finance
Embedded finance is spreading because it pays off on both sides of the screen.
For the platform:
- New revenue: interchange on cards, a share of payment and lending economics and lending margin where you extend credit.
- Higher retention and lifetime value: a financial product makes the platform harder to leave and increases revenue per user.
- Better data: transaction data sharpens underwriting, personalisation and product decisions.
- A stronger moat: owning the money flow deepens the customer relationship competitors cannot easily copy.
For the customer: finance at the moment of need, fewer steps, no context switch to a separate bank or lender, and offers tailored to what they are already doing. That context is why an embedded offer converts far better than redirecting the user elsewhere.
The types of embedded finance
Embedded finance is not one product. These are the five categories you will choose from, each with a proven 2026 example.
Embedded payments
The most mature category: in-app payments and one-click checkout that keep the transaction inside the product, as in Uber or Shopify checkout. Digital wallet adoption has pushed embedded payments into the mainstream. This is usually the first thing platforms embed – see our payment solutions development.
Embedded lending and BNPL
Credit offered at the point of need: buy now, pay later at checkout from Klarna or Affirm, and revenue-based financing such as Shopify Capital, Toast Capital and Amazon Lending offered to sellers inside the platform that already sees their cash flow. BNPL volume alone is projected near $576 billion by 2026.
Embedded banking
Accounts, balances and money movement inside a non-bank product, such as Stripe Treasury or Shopify Balance, so a merchant can hold and manage funds without a separate bank. This leans on the sponsor-bank relationship covered under banking software development.
Embedded insurance
Cover offered in context at the moment of purchase, such as trip protection inside a travel booking or accident cover attached to a ticket. Conversion is high because the risk and the purchase are right in front of the customer.
Embedded investing
Brokerage, savings or wealth features inside a non-financial app, letting users invest spare cash or round-ups without opening a separate brokerage account.
Which industries are adopting embedded finance
Any platform that already sits between a customer and a transaction is a candidate. The strongest fits in 2026:
- Vertical SaaS: software that runs a business (restaurants, salons, clinics) embeds payments, accounts and financing for the businesses it serves.
- Marketplaces: split payments, payouts to sellers and seller financing keep the money flow on-platform.
- E-commerce: checkout payments, BNPL and merchant cash advances lift conversion and merchant loyalty.
- Healthcare: patient payment plans and financing embedded in booking and billing flows.
- Logistics and mobility: instant driver and carrier payouts, fuel cards and working capital.
- Property and real estate: embedded rent payments, deposits and insurance.
The common thread is context: the platform already sees intent and cash flow, so a financial product offered there converts and underwrites better than a standalone one.
Embedded finance architecture
However simple it looks to the user, embedded finance is a layered system. Understanding the layers tells you what to build and what to buy.
From top to bottom: your product experience (the UX where the financial product appears), an embedded-finance API layer (your orchestration and ledger), a BaaS or enabler (the regulated connectivity) and a sponsor bank or processor (the licensed institution and card networks underneath).
The building blocks you assemble across those layers:
- KYC and onboarding: identity verification and risk checks before any account is opened.
- Accounts and ledger: a ledger of record you control, so balances always reconcile even when a provider’s data lags.
- Card issuing: virtual and physical cards through an issuer processor.
- Payments and money movement: pay-ins, payouts, transfers and reconciliation.
- Lending engine: credit decisioning, disbursement and repayment, where you offer credit.
- Compliance and monitoring: AML, sanctions screening and reporting wired into every flow.
The 2026 provider landscape maps neatly onto these blocks: Plaid for data and connectivity, Stripe and Stripe Treasury for payments and banking, Marqeta for card issuing, and BaaS platforms such as Unit or Railsr for licensed capabilities over a sponsor bank. How you combine them is the core design decision – see how we build FinTech.
How to build embedded finance into your product
A realistic build sequence, ordered so compliance and the ledger come before the shiny UX.
- Pick one use case where intent already exists in your product (payments, lending, accounts).
- Scope compliance and the sponsor-bank model before engineering, because they gate launch.
- Choose your route: a BaaS or enabler for speed, or direct integrations for control.
- Design your own ledger of record. Never rely solely on a provider’s balances.
- Wire in KYC, AML and sanctions screening at onboarding and at every transfer.
- Integrate the provider APIs (payments, card issuing, accounts) behind your own service layer.
- Build the in-context UX so the financial product feels native, not bolted on.
- Test reconciliation, edge cases and failure modes, then launch to a cohort.
- Monitor, reconcile daily and expand to more products once the first is stable.
Build vs buy: BaaS, enablers or in-house
You rarely build embedded finance entirely in-house, and you rarely should. The choice is how much of the stack to buy.
| Route | Speed | Control | Best when |
|---|---|---|---|
| Enabler / BaaS platform (Unit, Railsr) | Fast | Lower | You want to launch quickly with compliance and a sponsor bank included |
| Direct to sponsor bank + processors | Slower | Higher | You have volume, want better economics and own the relationships |
| Hybrid | Medium | Medium | Buy the regulated parts, build the ledger, orchestration and UX |
Most platforms start with an enabler to validate the product, then move regulated pieces in-house or direct to a sponsor bank as volume grows and the per-transaction economics start to matter. Whatever the route, keep your ledger, orchestration and customer relationship as yours.
Compliance and risk you cannot outsource
Using a BaaS provider does not transfer the obligation away from you. Regulators have made clear that the platform and the sponsor bank share responsibility, and BaaS oversight tightened through 2025 and 2026.
- KYC and AML: identity verification, sanctions screening and transaction monitoring are yours to get right, even when tooling is provided.
- The sponsor-bank relationship: you must understand who holds the licence and what they require of you.
- Data and privacy: financial data carries PCI DSS and privacy obligations.
- A ledger of record: you need your own source of truth for balances and disputes.
Treat compliance as core product, not a checkbox. Our compliance and RegTech solutions and the FinTech compliance checklist cover the controls in detail.
What embedded finance costs and how it pays back
Cost has three parts: enabler or provider fees (per transaction, per account or per card), the build (integration, ledger, UX and compliance engineering) and ongoing compliance and operations. Enabler routes lower the upfront build but cost more per transaction; direct routes invert that.
The payback comes from new revenue and retention. Platforms earn interchange on cards, a share of payment and lending economics, lending margin where they extend credit, and a meaningful lift in retention and lifetime value because the financial product makes the platform stickier. For the broader market context, see FinTech trends 2026.
Common mistakes when adding embedded finance
- Treating it as a feature, not a product. Embedded finance needs an owner, a roadmap and operations, not a one-off integration.
- Underestimating compliance. The obligation stays with you. Scope KYC, AML and the sponsor-bank model first.
- No ledger of record. Relying on a provider’s balances breaks reconciliation and disputes.
- Choosing the wrong enabler. Provider lock-in and limited control surface later, when economics matter.
- Embedding everything at once. Ship one use case, prove it, then expand.
How Pharos Production builds embedded finance
Pharos Production designs embedded finance as a product: a clean orchestration and ledger layer you own, the right BaaS or direct integrations underneath, KYC, AML and reconciliation built in, and an in-context UX that converts. We work across the FinTech software development stack, from payments to lending and accounts. If you are evaluating where embedded finance fits in your platform, tell us the use case and we will map the architecture, the build-versus-buy choice and the compliance path with you.
FAQ
Quick answers to common questions about custom software development, pricing, process and technology.
Type to filter questions and answers. Use Topic to narrow the list.
Showing all 7
No matches
Try a different keyword, change the topic, or clear filters
-
Embedded finance is when a non-bank company offers financial products - payments, accounts, cards, lending or insurance - directly inside its own app or platform, so customers never leave to use a bank. The platform connects to regulated financial infrastructure through APIs and surfaces the result under its own brand.
-
Embedded finance is what the customer sees: the financial product inside a non-bank experience. Banking as a service (BaaS) is the API infrastructure behind it that connects the platform to a regulated bank.
Open banking is the permissioned data layer. A single embedded feature can use all three.
-
Pick one use case where intent already exists, scope compliance and the sponsor-bank model first, choose a BaaS or direct integration, design your own ledger of record, wire in KYC and AML, integrate the provider APIs behind your own service layer, build an in-context UX, then launch to a cohort and expand.
-
In-app payments in Uber, one-click checkout on Shopify, buy now pay later from Klarna and Affirm, revenue-based financing such as Shopify Capital and Toast Capital, business accounts via Stripe Treasury and Shopify Balance, and travel insurance offered at checkout.
-
Cost has three parts: enabler or provider fees (per transaction, account or card), the build (integration, ledger, UX and compliance) and ongoing compliance and operations. An enabler route lowers the upfront build but costs more per transaction; going direct to a sponsor bank inverts that as volume grows.
-
Yes. The financial products are regulated, and oversight of BaaS tightened through 2025 and 2026.
Using a provider does not transfer the obligation away from you: the platform and the sponsor bank share responsibility for KYC, AML and consumer protection.
-
Usually not. Most platforms operate over a sponsor bank through a BaaS provider, so the licensed bank holds the licence while the platform delivers the experience.
You only need your own licence if you decide to become the regulated institution yourself.
Role: Founder and CTO, Pharos Production
Focus: Architecture, Web3 products, smart contract security, high-load systems
Experience: 23 years in production delivery
