Concept
🔗 Related
embedded finance cases · regulatory perimeter
Embedded finance is a financial service within a non-financial product: an account in Shopify, a card for an Uber driver, a loan at a store checkout, insurance when buying a ticket. Behind the storefront there is always a licensed player—a bank, neobank (e-money issuer), insurer, ManCo—and the non-financial company uses its license under contract. What this looks like for specific brands is covered in the embedded finance cases review.
For anyone building such a business, three questions matter: under whose license they operate, what is needed for a partner to onboard them, and where the boundary of their liability lies. There is no separate "embedded finance license"—each product is regulated according to its sector: payments as payments, credit as credit, insurance as insurance. Therefore, entry into each vertical is different, and it begins with choosing a model and a license-holding partner.
🍓 The cluster's core principle: you can outsource activity, but not liability—it remains with the license holder. This is how US banking supervision is structured (interagency guidance 2023), as well as EU DORA, the FCA regime (the principal is responsible for the appointed representative), and insurance (under NAIC, the insurer is responsible for the MGA program). The partner who "rents out" the license is obliged to control you—and will. Where supervision is heading is covered in the regulatory perimeter material.
Models and Where to Start
🔗 Related
white-label under CASP · US sponsor banks · UK host AIFM · third-party ManCo in the EU · BIN sponsorship for cards · EU/UK BaaS and neobank
Five main models. Each has its own license holder, its own minimum entry requirements, and its own supervision.
| Model | Under whose license | Minimum to start | Details |
|---|---|---|---|
| BaaS / sponsor bank (US) | partner bank: charter + FDIC | sponsor bank + middleware, ready BSA/AML package; go-live 3–12 weeks | Open |
| Rent-a-bank / true lender (US) | issuing bank of its state | partner bank + originate-and-assign scheme; true-lender legal risk | Open |
| Payment agents (EU/UK) | neobank/PI principal | agent registration through principal; own neobank — from €350K | Open |
| Appointed representative / fund hosting (UK) | host AIFM, FSMA s.39 | onboarding 4–6 weeks; investor due diligence at host | Open |
| Delegated authority / fronting (insurance) | fronting carrier / insurer | producer + MGA license, E&O, binding authority | Open |
The sixth vertical is crypto: white-label under someone else's CASP license with an EU passport (see white-label under CASP). Who specifically "rents out" the license is covered in dedicated reviews: US sponsor banks, UK host AIFM, third-party ManCo in the EU, BIN sponsorship for cards, EU/UK BaaS and neobank.
When It's Time for Your Own License
License rental means speed and a low entry barrier, but not forever. As volumes grow, the economics and supervisory burden flip: the partner takes a share of revenue and controls more tightly, while your own license becomes cheaper per transaction. Benchmarks vary by vertical—for card programs, around ~500K active cards is cited; in payments, the agent → own neobank transition is driven by turnover and desire for control; in funds—when management fees cover the cost of your own AIFM license. The 2025–26 trend reinforces this: in the US, some BaaS players are moving from "rental" to direct charter.
Jurisdictions
🔗 Related
Singapore — funds · Singapore — payments (PSA) · UAE (ADGM/DIFC) · Offshore (BVI/Cayman) · Malta (cell structures) · Hong Kong
The same models by country—breakdowns of licensing and hosting regimes: Singapore — funds · Singapore — payments (PSA) · UAE (ADGM/DIFC) · Offshore (BVI/Cayman) · Malta (cell structures) · Hong Kong.
This material is prepared as an expert review and does not constitute individual legal advice.