What is embedded finance? It’s the practice of building financial services, such as payments, accounts, loans and insurance, directly into products that aren’t financial at all. You use it when you pay for a ride inside a taxi app, split a purchase into instalments at an online checkout, or open a business account inside the software you already use to run your shop.
The scale is significant. Bain & Company has projected that embedded finance transactions in the US will exceed $7 trillion in 2026, more than 10% of all US financial transactions. We lead with transaction value because estimates of embedded finance revenue vary widely depending on how each research firm defines the market. For 2026, they range from roughly $85 billion to $155 billion.
At ConnectPay, we provide licensed finanzas integradas infrastructure for European platforms. In this guide, we explain what embedded finance is, its five main types, real examples, how it works and what it delivers. We also cover the risk most guides leave out: what happens when the regulated infrastructure underneath fails.
What Is Embedded Finance?
So, what is embedded finance at its core? It’s the integration of financial services into non-financial applications, so customers can use them without going to a separate bank, lender or insurer.
The simplest way to understand it is as a shift in where finance happens. Traditionally, financial services were a destination. You went to a bank to open an account, applied to a lender for a loan, and bought insurance from an insurer. Embedded finance turns those services into features. They appear inside the product you’re already using, at the moment you need them.
That’s why embedded finance is especially common in three kinds of businesses. E-commerce sites embed payments and point-of-sale credit at checkout. Marketplaces embed payments, payouts and seller accounts. SaaS platforms embed business accounts, cards and financing for the companies that use their software.
It’s also broader than many people assume. Embedded finance isn’t just banking. It covers payments, lending, insurance and investing as well. Embedded banking, where accounts and cards are built into a non-financial product, is one type within the category, not the category itself.
The company offering the service is usually not a bank. It’s a software business, retailer or platform working with a licensed financial provider behind the scenes. Customers see a feature in a familiar app. Underneath, a regulated institution holds the money, carries the licence and handles compliance.
Types of Embedded Finance
Embedded finance products fall into five main types. Each one brings a different set of embedded finance capabilities into a non-financial product.
- Banca integrada builds banking services, such as accounts, cards and deposits, into non-financial platforms. A bookkeeping app that lets small businesses open a current account and get a debit card without leaving the software is a typical example. We cover this type in depth in our guide to embedded banking.
- Pagos integrados make paying and getting paid part of the app or website itself. Customers pay without being redirected to another site, and platforms can collect and send funds without separate tools. Ride-hailing apps, where payment happens automatically at the end of a trip, are the clearest example.
- Préstamos integrados offers loans or credit at the point of sale or point of need. That includes buy now, pay later at checkout, as well as working capital offered to merchants based on their sales data inside a platform.
- Seguros integrados builds coverage into the purchase process. Travel insurance offered when you book a flight, or device protection when you buy a phone, are common examples.
- Inversión integrada adds investment options to an existing product experience, such as a banking or payroll app that lets users invest spare change or put part of their salary into a fund.
Which type to start with depends on where money already moves in your product. A marketplace usually starts with payments and payouts, because money already flows between buyers and sellers. A SaaS platform for small businesses often starts with accounts or cards, because its customers already run their finances alongside the software.
In practice, most products combine more than one type. A marketplace might embed payments for buyers, accounts for sellers and financing for growing vendors, all on the same platform. Many of these are powered by Banking-as-a-Service providers, as we explain in our article on how BaaS works.
¿Estás listo para actualizar tu infraestructura de pagos?
Deja de lidiar con flujos de pago fragmentados. Accede a IBAN específicos, SEPA Instant e integraciones API sin complicaciones, todo ello desde una única plataforma unificada.
Real-World Examples of Embedded Finance
Some of the most useful embedded finance examples come from companies most people don’t think of as financial at all.
- American Airlines offers co-branded credit cards, including through Citi, promoted directly to travellers when they book and when they fly. Customers get credit and loyalty rewards without seeking out a card separately. That’s embedded lending and payments working together.
- Uber builds financial tools into its driver app, including fast cash-out of earnings and a debit account for drivers. Drivers can access their pay soon after a trip instead of waiting for a weekly payout. That’s embedded banking and payments.
- Klarna lets shoppers split purchases into instalments at checkout across thousands of online stores. The credit decision happens inside the checkout flow, in seconds. That’s embedded lending in its most recognizable form.
- Tesla offers its own insurance to buyers in several US states, presented during the vehicle purchase process and priced using data about the car. That’s embedded insurance.
- Shopify Balance gives merchants a business account inside the Shopify platform, so sales revenue lands where they already manage their store. That’s embedded banking.
These examples of embedded finance span five different companies and four different types. That variety is the point. Embedded finance isn’t a synonym for banking or for payments. It’s a way of delivering any financial service inside a product people already use. For how this compares with the infrastructure model behind it, see our comparison of embedded finance vs. Banking-as-a-Service.
How Embedded Finance Works
The technology behind embedded finance is mostly about connections. APIs, the interfaces that let software systems talk to each other, act as the bridge between a non-financial platform and the licensed financial institution or infrastructure provider behind it.
When a customer opens an account inside a software app, the app sends the request through an API to a licensed provider. The provider runs identity checks, opens the account and returns the details. The customer only sees the app.
In most setups, three parties are involved. The brand owns the customer relationship and the product experience. The infrastructure provider supplies the APIs, ledgers and compliance tooling. The licensed institution holds the funds and carries the regulatory responsibility. Sometimes the second and third are the same company. Sometimes they’re separate, with the infrastructure provider sitting between the brand and a sponsor bank. That structure matters more than it looks, as the risk section below explains.
For more on the API layer, see our article on the role of APIs in embedded finance.
Embedded finance is what the customer sees: the account, payment or loan inside a familiar product. Banking-as-a-Service is the licensed infrastructure underneath that makes it possible. Our overview of proveedores de servicios financieros integrados explains how different providers fill that role.
Benefits of Embedded Finance
The benefits of embedded finance show up for both the businesses that offer it and the customers who use it.
- Conversion improves. When payment or financing options sit directly inside checkout, fewer customers abandon their purchase on the way to another site or application. Vendors commonly report conversion uplifts of 15% to 50% or more after adding embedded payments or point-of-sale financing. Those are vendor-reported figures, not guarantees. The results depend heavily on the product, the audience and how well the feature is implemented.
- New revenue streams open up. Platforms can earn from card interchange, payment fees, interest-sharing on lending or commissions on insurance. For many SaaS companies, embedded financial services have become a meaningful second revenue line.
- Customer insight gets richer. When transactions happen inside your product, you understand how customers buy, pay and manage money. That helps you improve the product, personalize offers and spot risk earlier.
- Services become contextual. Financial products appear exactly when and where they’re relevant: insurance when you book, financing when you buy, an account when you start getting paid. Customers don’t have to go looking.
- Customers benefit too. They get financial services that fit how they already work, often with faster access to funds, fewer forms and less switching between apps. A freelancer paid through a platform can see earnings and spend them in one place, rather than waiting for a bank transfer and reconciling it later.
- Businesses also keep customers longer. A business that runs its revenue, payments and cards through a platform has more reasons to keep using it. Our article on the benefits of embedded finance for businesses and consumers goes into each of these in more detail.
The Real Risk Behind Embedded Finance: Sponsor Bank Dependency
Here’s what most guides to embedded finance skip. Nearly every embedded finance product depends on a regulated institution underneath the software. In the US, that’s usually a sponsor bank, often connected through a middleware provider. In Europe, it’s a licensed bank, EMI or payment institution.
That dependency is the whole opportunity. It’s what lets a software company offer accounts or cards without becoming a bank. It’s also the biggest risk. If the infrastructure underneath fails, the polished product on top fails with it.
This isn’t hypothetical. In 2024, the sector went through a wave of regulatory action and failure. In the US, sponsor banks including Blue Ridge Bank and Evolve Bank & Trust faced enforcement action over their fintech partnerships, and middleware provider Synapse collapsed. In Europe, Solaris faced supervisory restrictions and needed rescue funding, following Railsr’s administration in 2023.
Synapse is the clearest case study. When it collapsed in April 2024, more than 100,000 people lost access to over $265 million held across several fintech apps. Synapse kept the records of who owned what, while the money sat in pooled accounts at partner banks. When those records didn’t match the banks’ records, nobody could say with confidence whose money was whose. The bankruptcy trustee estimated the shortfall at between $65 million and $95 million. Many customers had believed their funds were protected exactly like ordinary bank deposits.
What does a sound setup look like instead? Customer balances are recorded by, or reconciled daily with, the institution that actually holds the money. Client funds are safeguarded or insured in a way the customer can understand. And there’s a clear plan for what happens to customer funds if any party in the chain fails, whether that’s the brand, the infrastructure provider or the bank.
Since then, regulators have tightened oversight, and compliance costs have risen across the sector. For businesses, the practical lesson is simple. Before choosing an embedded finance or BaaS partner, ask directly:
- which licensed institution holds the money?
- who keeps the customer-level records?
- has that institution faced regulatory action?
Who Offers Embedded Finance Infrastructure?
The examples earlier in this guide were end-user products. Behind them sit infrastructure providers that supply the embedded finance capabilities those products are built on. This is a short map of that layer, not a ranked comparison.
- En EE. UU., Unidad is one of the best-known platforms. It provides accounts, cards, payments and lending through APIs for software companies, working with partner banks that hold the funds.
- Treasury Prime provides embedded banking software, and since 2024 has focused on selling it directly to banks that run their own fintech programs.
- Synctera offers a BaaS platform connected to a choice of sponsor banks, giving businesses more flexibility over their banking partner.
- Column takes a different approach. It’s a nationally chartered bank that offers its own APIs directly to developers, with no separate middleware layer.
In Europe, the model often looks different because providers can hold their own licences. ConnectPay is an EMI licensed in Lithuania, providing accounts, cards, payments and compliance through APIs to platforms across the European Economic Area.
Whichever provider you consider, a few questions separate a strong partner from a risky one:
- Who holds the licence? Is it the provider itself, or a bank behind it?
- Where is customer money held, and how is it safeguarded or insured?
- Who keeps the customer-level records, and how often are they reconciled with the institution holding the funds?
- What happens if the provider fails? Is there a documented plan for returning customer funds?
When you compare providers, look beyond the API documentation. Ask about the licence behind the product, how funds are safeguarded, and how records are kept. For a related perspective, see our article on how neobanks benefit from embedded finance.
How ConnectPay Fits Into Embedded Finance
ConnectPay provides licensed embedded finance infrastructure for European platforms. Through our APIs, businesses can offer multi-currency accounts with IBANs, card issuing, SEPA and SWIFT payments, and built-in AML and KYC compliance as part of their own products.
That links directly to the risk covered above. We operate under our own EMI licence, supervised by the Bank of Lithuania. Our clients aren’t relying on a separate sponsor bank relationship that we don’t control, or on a middleware layer sitting between them and the licensed institution. The entity that provides the API is the same entity that holds the licence and safeguards client funds.
For example, a European marketplace can give each seller an IBAN account, issue cards to its larger vendors and pay out across SEPA, all through one integration with one licensed provider. Client money is kept in segregated accounts, separate from our own operating funds, as EMI rules require. Customer-level records sit with the licensed institution responsible for them.
None of this removes the need for due diligence. You should ask us the same questions you’d ask anyone else. But it does mean the answers are simpler. If you want to see how this works in practice, our Banca como servicio page explains the setup.
Embedded Finance Is Only as Strong as What’s Underneath It
Embedded finance makes financial services feel effortless: an account opened in seconds, a loan approved at checkout, a payout landing minutes after a job is done. But that polish depends entirely on the regulated infrastructure underneath it.
The 2024 enforcement wave and the Synapse collapse showed what happens when that layer fails. Customers didn’t lose access because the app stopped working. They lost access because nobody could reliably say where their money was.
So when you evaluate an embedded finance product or partner, look past the feature list. Ask who provides the licensed infrastructure, who holds the funds, who keeps the records, and how that provider has been supervised. Those answers matter more than any feature demo. Embedded finance will keep growing as more software becomes the place where businesses and consumers manage money. The providers that last will be the ones whose foundations hold up under pressure.
If you’re building embedded finance for European customers, talk to ConnectPay about how licensed infrastructure can sit underneath your product.







