The embedded finance value chain describes the set of participants that together deliver a banking or payments feature inside a non-financial product. It replaces the single vertically integrated bank with a group of specialists, each owning one layer. Understanding who does what in this chain is the clearest way to see how embedded finance actually works and where the value sits.
From one bank to several specialists
In traditional banking, one licensed institution owned the whole chain: the customer relationship, the product, the technology, and the regulatory permissions. Embedded finance separates those layers so a non-financial company can offer money features without becoming a bank.
Bain and Company describe this shift in its research on the sector, setting out a chain that typically involves four kinds of participant: the end customer, the platform that owns the customer relationship, the software enabler that handles the technical and regulatory plumbing, and the licence or regulatory services provider that carries the permissions. Each layer does one thing well, and the product a customer sees is the sum of all four.
If the concept is new, What Is Embedded Finance? sets out the fundamentals before this article maps the roles.
The Four Layers of the Embedded Finance Value Chain
The end customer is the individual or business using the financial feature: paying, holding a balance, spending on a card, or borrowing. They usually experience it as part of a product they already use, not as a separate bank.
The platform is the brand that owns the relationship: an e-commerce tool, a marketplace, a logistics app, or vertical software. It decides which financial features to offer, sets the experience, and holds the customer data that makes those features relevant. Bain points to companies such as commerce and delivery platforms as examples of this archetype.
The software enabler supplies the technology that connects the platform to regulated infrastructure. It provides the accounts, cards, payments, and compliance tooling through APIs, so the platform does not build a banking stack from scratch. This is the layer that makes the model practical.
The licence or regulatory services provider carries the regulated permissions: holding funds, issuing e-money, acting as the card issuer of record, and taking responsibility for compliance obligations. This is the participant that makes the whole arrangement lawful.
Where the value sits
Bain estimates the revenue for platforms and enablers behind embedded finance in the United States at around 22 billion dollars in 2021, on course to more than double to 51 billion dollars by 2026, on transaction value expected to exceed 7 trillion dollars in the same year. The value is spread across the chain rather than captured by any single layer.
Platforms benefit from deeper engagement and new revenue from features their customers already want. Enablers earn from the technology and integration they provide across many platforms at once. Licence providers earn from the regulated services only they can offer. The customer benefits from finance that appears at the moment it is useful. The trends reshaping these economics are covered in Embedded Finance Trends to Watch in 2026.
The value chain at a glance
| Layer | Role | Owns |
|---|---|---|
| End customer | Uses the feature | The need being served |
| Platform | Owns the relationship | Brand, experience, data |
| Software enabler | Supplies technology | Accounts, cards, payments, APIs |
| Licence provider | Carries permissions | Custody, issuing, compliance |
Why the separation matters
The split is not only a description; it is a design principle. When each layer is distinct, responsibility is clear: the platform knows it does not hold funds, the enabler knows it supplies software rather than regulated services, and the licence provider knows where compliance sits. That clarity is what supervisors increasingly expect, and it is what lets a non-financial company launch a money feature without taking on a bank’s obligations.
It also shapes strategy. A platform choosing partners should be clear which layer each partner occupies, and should avoid arrangements where the roles blur. A software enabler that supplies technology should not be mistaken for the regulated institution, and a licence provider should not be expected to build the product experience.
Bringing it together
The embedded finance value chain works because each layer is distinct: the platform owns the customer, the enabler supplies the technology, and the licence provider carries the permissions. Getting those boundaries right is what makes an embedded product both practical and compliant. Artha operates as the software enabler layer through its open banking platform, supplying the technology while licensing and custody stay with clients and regulated partners. For the wider effect on how companies distribute finance, see Why Embedded Finance Is Reshaping How Companies Offer Money.
Frequently Asked Questions
What is the embedded finance value chain?
It is the set of participants that together deliver a financial feature inside a non-financial product: the end customer, the platform that owns the relationship, the software enabler that supplies the technology, and the licence provider that carries the regulated permissions.
Who holds the customer's money in this model?
The licence or regulatory services provider, a regulated institution. The platform owns the relationship and the software enabler supplies the technology, but neither holds funds on its own account.
Why did the single-bank model give way to a chain?
Because a non-financial company can reach customers and hold relevant data far better than a traditional bank, while lacking the licence and technology to run the product. Splitting the chain lets each participant contribute the layer it does best.
Where does the revenue come from?
From the transactions and services flowing through the product. Bain estimates US platform and enabler revenue more than doubling to 51 billion dollars by 2026, shared across the layers of the chain.
