--- title: "Embedded Finance" url: "https://mahouse.world/glossary/embedded-finance" type: "glossary term" topic: "Embedded finance" author: "Ihor Vlasov" reviewed: "2026-09-20" published: "2026-08-06" --- # Embedded Finance Embedded finance is the offering of financial products — payments, accounts, lending, insurance, cards — inside a non-financial product at the point where the customer needs them: the loan in a software vendor's invoicing screen, the insurance sold with the ticket, the wallet inside the marketplace. The non-financial company distributes; a licensed provider supplies the regulated product through APIs; and the revenue is shared. It moved the distribution of finance into the software customers already use. **Also known as:** Embedded payments, Embedded lending, Embedded insurance, Finance as a feature ## Key facts - **Used at:** vertical software (payments and lending inside practice-management, restaurant, salon, logistics and construction software), marketplaces and gig platforms (payouts, wallets, instant pay), e-commerce (BNPL, insurance at checkout), accounting and ERP (cards, expense management, credit), travel and mobility (insurance, FX) - **Binding:** the embedded product is regulated exactly as it would be standalone — the licence sits with the provider, the distributor may need authorisation as an agent, distributor or credit broker depending on the product and jurisdiction, and consumer-protection, disclosure and AML rules apply at the point of sale; regulators in the UK, EU and US have scrutinised the "rent-a-licence" models where the provider's oversight of distributors was thin - **Typical economics:** payments embedded in vertical software commonly become 30–50% of the software company's revenue at a take rate of 0.3–1% of volume; embedded lending pays the distributor a referral or a share of margin; embedded insurance a commission of 10–30%; the provider keeps the balance and bears the regulatory and credit risk - **Typical build:** the distributor integrates the provider's APIs (onboarding, accounts, payments, cards, lending decisions) and owns the customer experience; the provider owns the licence, the compliance, the balance sheet and the scheme relationships; a banking-as-a-service platform often sits between them - **Parties:** the distributor (software or marketplace), the provider (bank, EMI, PI, lender, insurer), the BaaS or orchestration platform, the schemes, the regulator, and the end customer, who may not know which entity they are contracting with ## How embedded finance works in practice A software company serving 20,000 restaurants adds payments: every restaurant's card acceptance runs through the software, the company becomes a payment facilitator on an acquirer's licence, and it earns a share of the processing margin — on €4 billion of annual volume at 0.5% net, €20 million, more than its subscription revenue. It then adds working-capital advances, funded by a lending partner and repaid from card receipts, earning a share of the margin, and a business account and card issued by a BaaS provider. Each product is offered in the software where the restaurant already works, with the software's data (sales, seasonality, tenure) improving the underwriting. The restaurant sees one product; behind it are an acquirer, a lender, a bank, a card scheme and three contracts. The risks arrived with the growth. Providers that let distributors onboard customers with thin oversight were found by regulators to have outsourced their AML controls to companies that did not have them; several BaaS banks in the US received enforcement orders in 2023–2024, and their distributors' customers found their funds frozen. Distributors that built on one provider discovered the provider's limits, pricing changes or exit were their own. And the economics depend on the distributor's ownership of the customer: a software company whose customers process elsewhere earns nothing from payments; one that makes its payments the default earns a business. For a fintech provider, embedded distribution is growth without a sales force and risk without direct control; for an acquirer, an embedded-finance revenue line is valued for its stickiness and diligenced for its regulatory dependencies. For a software company, embedded finance is often the larger business hiding inside the one it built; for the licensed provider behind it, the oversight of its distributors is the licence. ## Example A vertical-software company for dental practices with €30 million of subscription revenue adds embedded payments through a payment-facilitator programme on an acquirer's licence. Year one: 35% of practices adopt; volume €600 million; net revenue €3.6 million. Year three: 70% adoption, €1.9 billion, €11 million net, plus €2 million from embedded working-capital loans funded by a lending partner (the software's data cuts the partner's default rate to 1.1% against 2.4% on its direct book) and €0.8 million from embedded equipment-financing referrals. The company's revenue is €47 million, of which €14 million is financial services at higher margin than software. A private-equity buyer values it at 9× revenue against 6× for a peer without payments, and its diligence spends a week on the acquirer contract, the payfac programme's compliance obligations and the lending partner's exit terms. ## Common mistakes - Building the whole embedded stack on one provider with no exit plan. - Distributors treating compliance as the provider's problem; the regulator sees both. - Providers scaling distribution without oversight of what distributors onboard. - Offering payments as an option rather than the default, and earning a fraction of the potential. - Valuing embedded revenue without reading the contracts it depends on. ## Related terms - [BaaS](https://mahouse.world/glossary/baas.md) - [Payment Facilitator](https://mahouse.world/glossary/payment-facilitator.md) - [Buy Now Pay Later](https://mahouse.world/glossary/buy-now-pay-later.md) - [Fintech](https://mahouse.world/glossary/fintech.md) - [API Banking](https://mahouse.world/glossary/api-banking.md) - [Revenue-Sharing Model](https://mahouse.world/glossary/revenue-sharing-model.md) — Ihor Vlasov, M&A FinTech Expert. Last reviewed 2026-09-20. https://mahouse.world/authors/ihor-vlasov