Embedded finance: build, buy or connect
The question is not whether to embed financial services, but how much of the regulated stack you want to own — and how much you want to rent.
Embedded finance is often presented as a technology decision. It is more usefully understood as a decision about where value sits in your business, and how much of the regulated stack you are prepared to operate.
Build
Building means obtaining permissions, selecting or constructing processing, and running the operational and compliance functions yourself. It offers the greatest control and the strongest long-term asset, and it demands capital, governance and time. It suits businesses for whom financial services are the product rather than an enhancement to something else.
Buy
The acquisition route — a licensed entity, a portfolio or a platform — can compress years into months. It also imports whatever you acquire: legacy systems, conduct history, cost base and cultural assumptions. Due diligence has to examine the licence and the technology, but also the operational reality behind both.
Connect
Connecting means using an existing platform to reach institutions that already hold the permissions and operate the infrastructure. The economics are shared, the time to market is shorter, and the product can be extended as the commercial case develops.
For most platforms, connectivity is the sensible starting point. The important discipline is designing the integration so that it does not become a ceiling: consistent internal abstractions for accounts, payments and cards mean that a change of provider is an implementation detail rather than a rebuild.
What to examine before choosing
- Who owns the customer relationship, and who owns the data? The answer affects everything from pricing to product design.
- Which regulated activities are involved? Accepting deposits, issuing payment instruments and lending each carry different permissions and obligations.
- What happens when a provider changes its mind? Concentration on a single partner is a commercial risk, not only a technical one.
- How portable is the integration? If switching providers would take a year, the arrangement is closer to a joint venture than a vendor relationship.
- Who handles conduct, complaints and disputes? These obligations do not disappear because the technology is outsourced.
The orchestration layer
The most durable pattern is a thin internal layer that normalises providers: one internal model for an account, a payment or a card, with provider-specific mapping held at the edge. It costs some engineering up front and preserves optionality later.
Embedded finance rewards businesses that are clear about what they want to own. The rest can be connected.
This note is general commentary and does not constitute legal, regulatory or investment advice. Specific permissions and obligations depend on your business, jurisdiction and the institutions involved.