Embedded finance lets platforms sell banking, lending, insurance or payments as part of a product a customer already uses, capturing financial-services margin and retention. A banking-as-a-service layer supplies the licensed infrastructure behind it, while the platform takes on balance-sheet and compliance exposure it did not previously carry.
Where does the revenue in embedded finance actually go?
The obvious answer, that banks earn it, is mostly wrong now. When a vertical SaaS company or a marketplace embeds a card, a lending product or an insurance offer into its existing workflow, the interchange, interest spread or premium share flows largely to the platform, not to the licensed institution underneath it. The bank or program manager takes a fee for the license and the rails, and the platform keeps the rest.
That reallocation is the entire commercial logic of embedded finance. A platform that already owns the customer relationship, the transaction data and the login screen is better positioned to sell a financial product at the moment it is needed than a bank that has none of those things. The distribution advantage is worth more than the balance sheet, which is why the software company keeps most of the margin even though it is not the one lending the money or holding the deposit.
This is a genuine shift in where financial-services profit pools sit, not a repackaging of an existing bank product under a new label. A decade ago a merchant needing working capital applied to a bank; now the same merchant is offered a line of credit inside the point-of-sale software it already logs into daily, priced against data the bank never had access to and offered before the merchant thought to go looking for it.
- 01
Identify the transaction moment
Find where a customer already needs credit, insurance or a payment to move, inside the existing product flow.
- 02
Pick a BaaS partner
Evaluate the sponsor bank behind the provider, not just the API, since that relationship is the fragile point.
- 03
Underwrite with platform data
Use transaction and usage history already on the platform rather than a generic credit application.
- 04
Own the compliance surface
Build KYC, dispute handling and AML monitoring into the product rather than treating it as the partner's problem alone.
What is the banking-as-a-service layer that makes this possible?
Banking-as-a-service providers sit between the platform and a chartered bank, exposing account creation, card issuing, payment movement and compliance tooling through an API. The platform never becomes a bank; it licenses the capability, and the BaaS provider handles KYC, AML monitoring, ledgering and the regulatory reporting that a chartered institution requires of anyone touching its balance sheet.
This layer is what turned embedded finance from a multi-year banking partnership into something a product team can ship in a quarter. Before it existed, a platform wanting to offer a branded card or a lending product needed its own bank charter negotiations, its own compliance hires and years of lead time, which kept embedded finance out of reach for all but the largest companies.
It also means the platform's financial product is only as reliable as the BaaS provider's own bank relationships, which have proven to be the fragile part of the stack. When a sponsor bank pulls back from a program, sometimes over its own regulatory pressure rather than anything the platform did, the platform's financial product can stop functioning overnight, taking the trust it built with customers down with it.
Why are platforms embedding financial services in the first place?
Two reasons dominate, and neither is really about financial services. The first is retention: a merchant with a lending relationship or a payments account tied to a platform is materially harder to switch away from than one using the platform for software alone, because leaving means unwinding a financial relationship, not just canceling a subscription.
The second is revenue mix. Software margins compress as categories mature and competitors converge on features, which flattens pricing power over time. A lending spread or a payments take rate is a new, largely uncorrelated revenue line layered onto the same customer base, and it tends to scale with the customer's own transaction volume rather than with seat count, which is a different and often larger growth curve.
For platforms built on payment orchestration infrastructure, adding a lending or issuing product is often a smaller technical lift than the commercial upside implies, because the transaction routing and reconciliation work is already in place. The harder part is rarely the integration; it is deciding how much underwriting risk the platform is willing to hold before the economics stop working in its favor.
| Bank-led | Platform-led (embedded) | |
|---|---|---|
| Customer relationship | Owned by the bank | Owned by the platform |
| Underwriting data | Credit bureau and application | Live transaction and usage history |
| Who captures the margin | The bank | Mostly the platform, via program fees to the bank |
What risk does a platform take on by embedding finance?
Balance-sheet exposure is the first cost, even when a bank partner technically holds the assets. A platform that extends working-capital credit to its merchants is underwriting a portfolio, and losses on that portfolio hit the platform's economics even when the loans formally sit on a partner bank's books through a program agreement, because the platform typically absorbs first-loss risk or shares in it.
Compliance exposure is the second, and it is less visible until it isn't. Anti-money-laundering monitoring, dispute handling and consumer-protection rules do not disappear because a fintech partner is doing the technical work behind the scenes. Regulators increasingly hold the platform accountable for its users' experience, treating the software brand the customer sees as the accountable party regardless of which entity holds the license.
The BaaS partnerships that made embedding fast are the same partnerships that concentrate this exposure in a small number of sponsor banks, which means a single regulatory action against one bank can disrupt financial products across dozens of unrelated platforms at once. A platform evaluating embedded finance is really evaluating how much of that concentrated, correlated risk it is willing to inherit, and whether the retention and revenue gains are large enough to justify carrying it through a downturn, not just through a period when credit losses are low and regulators are inattentive.
Which verticals is embedded finance spreading fastest in?
Vertical SaaS is the clearest case: software built for a single industry, whether that is salons, veterinary clinics or construction firms, already sits inside every transaction its customers process, which makes payments and then lending a natural extension rather than a new sales motion. The provider already knows the business's revenue pattern to the day, which is a better underwriting signal than most banks ever see.
Marketplaces follow a similar path but from the other direction, using embedded finance to solve trust and cash-flow problems between buyers and sellers, such as seller financing, instant payouts or buyer protection tied to escrow. The marketplace is not just distributing a financial product; it is often solving a problem, delayed settlement or seller cash-flow gaps, that its own two-sided structure created in the first place.
Both patterns work because the platform's product usage already generates the data needed to underwrite the financial product, which is the advantage a bank starting from a credit application alone does not have. Ongoing fintech and platform research tracks which verticals are moving from payments into lending and insurance first, and why some categories, healthcare and regulated professional services among them, are moving far more slowly than the general trend suggests.