Embedded finance

Embedded finance is the delivery of financial services, such as accounts, payments, cards or lending, inside a non-financial company's own product, so its users get them without leaving the platform. The platform owns the customer experience. A licensed institution, usually a bank or e-money institution, provides the regulated service behind it.

section

Examples of embedded finance

ServiceExample
Embedded accountsA marketplace gives each seller an account with its own IBAN, so payouts land inside the platform
Embedded paymentsAccounting software lets users pay supplier invoices without logging in to a separate provider
Embedded cardsExpense or travel software issues company cards that its customers manage in the app
Embedded lendingA checkout offers buy now, pay later, or an e-commerce platform offers merchants working capital based on their sales
Embedded insuranceCover is offered at the point of sale, such as shipping or travel insurance
section

Who does what

Embedded finance splits the work between the brand the user sees and the regulated firm behind it, usually an e-money institution or a bank.
LayerRole
PlatformOwns the user relationship, the interface and distribution; earns fees or a revenue share
Licensed providerHolds the licence, issues the accounts or cards, holds client funds under safeguarding, runs AML checks on end users and answers to its supervisor
Technology layerAPIs that connect the two, often supplied by the licensed provider itself
Under EU law the platform can usually work in one of three ways: as a technical service provider that never touches client money, as a distributor or agent registered under the licensed provider's licence, or with its own licence as a payment service provider. Which one applies depends on what it actually does, so it's a question for legal advice early in the design.
section

Embedded finance vs banking as a service

The two terms describe the same arrangement from opposite ends. Embedded finance is what the end user sees: financial features inside a product that isn't a financial company. Banking as a service is the supply side: a licensed provider exposing accounts, payments and cards through APIs so other companies can build them in. Most embedded finance runs on banking as a service.
section

What platforms should check in a partner

  • whose name the IBAN is issued in, the end user's or a pooled account, which affects Verification of Payee results
  • who carries out know your business checks on end users, and how much the platform has to collect
  • how client funds are safeguarded and what happens if either party fails
  • which countries the licence is passported to, and which currencies and payment schemes are covered
  • who handles complaints, incidents and fraud cases, and how liability is split in the contract
section

Embedded finance at Narvi

Narvi offers two ways to embed financial services, both run under its e-money institution licence from the Finnish Financial Supervisory Authority, passported across the EEA. Banking as a Service is for platforms that want to build accounts and payments into their own product through an API. White label banking is for companies that want a branded banking portal for their customers without building one.
Banking as a ServiceWhite label banking
What you getAPI access to accounts, payments and onboarding, built into your own interfaceA ready-made online banking portal with your logo, colours and fonts
Who builds the interfaceYour developersNarvi, configured with your brand assets
AccountsDedicated IBANs created by API for each end user, with several per entity where funds must be kept apartDedicated IBANs in each customer's own name, plus multi-user access with roles for directors, accountants and staff
PaymentsSEPA, SEPA Instant and SWIFT to 100+ countries in 75+ currencies; inbound in EUR, USD and GBPSEPA, SEPA Instant and SWIFT to 100+ countries
IntegrationREST API with Node.js and Python libraries and real-time webhooks; public documentationNo-code setup; Narvi runs hosting, security updates and new releases
FitsFintechs, marketplaces, PSPs, SaaS platforms, crypto companiesCrypto exchanges and OTC desks, iGaming operators, accounting and legal firms, startup accelerators
In both, Narvi runs the regulated side: KYC and KYB onboarding of end users, transaction monitoring and regulatory reporting. Client funds are safeguarded at EU-regulated banks, as e-money rules require. The platform keeps the customer relationship and its brand. Its own regulatory position still depends on its role, as described above.Setup follows the same steps for both: a scoping call, integration or brand configuration, compliance setup for your customer base, testing, then go-live.
section

FAQ

The financial services in it are. The licensed provider is supervised; the platform is regulated only to the extent its role requires, for example as a registered agent or distributor.

Not usually, if a licensed partner provides the service and the platform never holds client funds. It depends on the exact role, so get legal advice.

No. Open banking lets third parties read account data or start payments from accounts held elsewhere, with the customer's consent. Embedded finance can use it, but often provides the accounts themselves.

Banking as a service gives a platform APIs to build financial features into its own interface. White label banking gives it a finished banking portal under its own brand. The licensed provider behind both is the same; the difference is who builds and runs the interface.
section
section
Last reviewed October 23, 2026Disclaimer
This publication is provided for general information purposes and does not constitute legal, tax, or other professional advice from Narvi Payments Oy Ab or its affiliates, and it is not intended as a substitute for obtaining advice from a financial advisor or any other professional.
section