You've probably used embedded finance without ever calling it that. Buying now and paying later at checkout, getting a card issued by a rideshare app, or seeing an insurance offer pop up while booking a flight — these are all examples of financial services showing up inside apps that aren't banks at all.
What embedded finance actually means
Embedded finance is when a non-financial company builds banking, lending, payments or insurance features directly into its own product, usually by partnering with a licensed financial institution behind the scenes. The retailer, app or platform handles the customer-facing experience, while a regulated partner handles the underlying financial plumbing, licensing and compliance. This layered structure is what allows a familiar retail or travel brand to offer something that looks and feels like a bank product, even though it isn't a bank itself.
Why so many companies are doing it
For businesses, embedding finance can mean keeping customers inside their own app rather than sending them elsewhere to arrange payment or credit. For customers, it can mean a smoother checkout or fewer steps to access a service. This is why the trend has spread across retail, ride-hailing, software tools and even fitness apps, each quietly partnering with banks or payment providers to offer something that feels native to their platform. It also lets these companies gather useful data about spending habits within their own ecosystem, which can shape future products and marketing.
What to keep in mind as a user
Because the financial product is wrapped inside another brand's app, it's not always obvious who is actually regulating it or holding your money.
- Check the terms to see which licensed institution stands behind the service.
- Understand whether any credit or instalment product involves interest, fees or a credit check.
- Remember that convenience at checkout doesn't remove the need to read the terms.
Embedded finance is likely to keep expanding as more companies look for ways to serve customers without needing a banking licence themselves. As with any financial product, it's worth understanding who's behind it and what you're agreeing to — this article explains how the model works and isn't a recommendation to use any specific service.
How the arrangement is built, layer by layer
Before the money, the machinery. Embedded finance always has three parties, and knowing which is which tells you who to call when something goes wrong.
At the bottom sits a licensed institution — a bank or an e-money company. It holds the licence, carries the regulatory obligations, and in most countries it is the party whose deposit guarantee applies to your balance. In the middle sits a banking-as-a-service provider: the technical layer that turns banking functions into an interface other companies can plug into. On top sits the platform you actually see — the webshop, the rideshare app, the accounting package.
What that platform can offer depends on how deep the integration goes. Payments and checkout credit are the easiest to embed and therefore the most common. Card issuing is a step further: the platform hands out a card in its own name while the licensed party stands behind it. Accounts and lending are the deepest form, and the one where the platform starts to look like a bank without being one.
The reason so many non-financial companies bother: it keeps customers inside their own product. A bookkeeping platform that lets you pay a supplier bill directly is more useful than one that sends you to your bank, and every payment leaves data behind about what a customer buys and when. For the licensed party the trade is the opposite — it gives up the customer relationship in exchange for volume it would never reach on its own.
For users the practical questions are simple and worth asking before you keep money anywhere: which institution actually holds the balance, does the deposit guarantee apply, and who do you contact when a payment goes missing — the app or the bank behind it? The answer is usually in the small print at the bottom of the signup screen, in a sentence beginning with "banking services are provided by".
Follow the money: who earns what in the partnership
Most explanations of embedded finance stop at the technology — the API, the licensed bank in the background, the app in front. The part that decides whether such a partnership survives is commercial, and it is rarely spelled out: the two parties are splitting one customer between them.
Three revenue models turn up again and again, and they behave very differently:
- Revenue share — the platform keeps a slice of interchange or lending margin, often the larger slice, because it owns the customer relationship. Income scales with usage, so it grows quietly for years.
- Referral fee — a one-off payment for handing over a signed customer. Simple to agree on, but it gives the introducing party no reason to care what happens next.
- Recurring commission — a monthly cut for as long as the customer stays. The most demanding to administer and the only one that rewards both sides for keeping the customer happy.
That difference explains a pattern you can see from the outside: embedded finance built on referral fees tends to be pushed hard at signup and forgotten afterwards, while revenue-share and recurring models come with better support, because the platform loses money when you leave.
The mechanics of these agreements sit closer to partner marketing than to banking. Great Partners follows that field across Europe, including how recurring commission arrangements are structured and where they tend to break down.
As a user, the practical question is a small one: if the app disappeared tomorrow, whose product would you still have? With embedded finance the answer is usually the licensed institution behind it — worth knowing before you keep a balance somewhere.
