Embedded finance

Embedded finance describes financial products delivered inside a non-financial company's own experience: a marketplace paying its sellers into accounts it issues, a vertical SaaS platform offering its customers a card, a retailer offering credit at checkout. The financial product is not a destination the customer visits; it is a feature of something they already use.

Why it happens

Platforms embed finance for three reasons, usually in this order. It removes friction from something the customer already does through them — getting paid, paying suppliers, financing stock. It creates a revenue line, most often from interchange, payment margin or lending spread. And it increases retention, because a customer whose money moves through your platform is substantially harder to displace.

What it requires underneath

Almost no platform embedding finance holds the licence for it. The product sits on infrastructure bought in: a banking-as-a-service provider for accounts and payments, an issuer and BIN sponsor for cards, an identity provider for onboarding, a monitoring vendor for AML, and a ledger to hold it all together. The platform owns the experience and the customer relationship; the regulated entity owns the product.

That division is the central design decision of any embedded finance build, and it is where the licence model question becomes unavoidable.

What it is not

Embedded finance is not the same as being a fintech. A platform that distributes a regulated product under someone else's authorisation carries real obligations — conduct, complaints, AML cooperation, marketing compliance — but does not become the regulated firm. Confusing the two, in either direction, causes most of the surprises in the first year of an embedded finance programme.