Embedded finance, unbundled: a map of who actually holds the risk

An embedded finance product looks, to the customer, like a feature of a software company: a payout button inside a marketplace, a card issued by a payroll platform, a loan offered at checkout. Underneath, there is always a licensed institution, and between the two there is a contract allocating responsibility.

Most of the sector's difficulties come down to a mismatch between where the customer thinks the risk sits, where the contract says it sits, and where the regulator says it sits, which is with the licensed entity, more or less regardless of what the contract says.

The layers

A conventional stack has four:

1. The distributor. The software company the customer actually uses. It owns the interface, the customer relationship and the brand.
2. The platform or enabler. Provides the ledger, the orchestration, the compliance tooling and the API. May be part of the licensed entity or a separate company.
3. The licensed institution. A bank, e-money institution or payment institution holding the permission that makes the product legal. It carries the regulatory obligation.
4. The scheme or network. Card networks, domestic payment schemes, or the central bank rails underneath everything.

Value tends to accrue at layer one. Obligation sits at layer three. That asymmetry is the structural tension in the model.

Where things break

Programme oversight. A licensed institution is responsible for the conduct of the programmes it sponsors, including customers it never sees. Building the oversight capability to supervise dozens of distributors is expensive, and it is a very different competence from running a bank.

Ledger truth. When the distributor shows a balance, the platform maintains a ledger and the bank holds the pooled account, three records must agree. Reconciliation failures between them are the most common cause of customers being unable to access funds during a partnership breakdown.

Onboarding accountability. Know-your-customer obligations belong to the licensed entity, but the onboarding experience is built by the distributor, who is measured on conversion. The incentives point in opposite directions and are resolved contractually rather than structurally.

Exit. Contracts that describe how a programme starts in great detail often describe how it ends in a paragraph. Migration of customers, funds and records to a new sponsor is slow, and the customer experiences the delay.

The diligence questions that matter

For anyone evaluating an embedded finance partnership, whether as a distributor, an investor or a corporate buyer, a short list separates the resilient arrangements from the fragile ones:

• Which legal entity holds customer funds, and under what protection regime?
• Who performs onboarding checks, who reviews them, and who can override a decline?
• How frequently are the distributor's ledger, the platform's ledger and the bank's account reconciled, and what is the break-resolution process?
• What is the notice period for programme termination, and what migration assistance is contractually owed?
• Has the licensed institution's supervisor examined this programme type before?

None of these are exotic. They are simply the questions the answer to which determines what happens on the worst day, and they are much easier to ask before signing than after.