Guide · Embedded finance

What is embedded finance? Definition, examples and how it works

Embedded finance puts financial services such as payments, accounts, cards, FX and lending inside products whose main job is something else, like a marketplace, a SaaS tool or a platform for contractors. This guide explains what embedded finance means, how banking-as-a-service makes it work, real examples, the benefits and risks, and how a platform launches it.

Embedded finance, in one sentence

Embedded finance is the integration of financial services, such as payments, accounts, cards, FX, lending and insurance, directly into a non-financial product, so users never have to leave it to visit a bank. The marketplace, SaaS tool or platform offers the financial feature inside its own experience, while a regulated partner provides the rails behind the scenes, usually through an API.

When a ride-hailing app pays drivers the moment a trip ends, or a marketplace pays sellers in their own currency, that is embedded finance.

Embedded finance: definition and the main types

As a definition, embedded finance covers any financial service delivered inside a product whose main business is something else. The main types:

TypeWhat users getExample
Embedded paymentsPay, get paid and pay others inside the productCheckout in a booking app; seller payouts in a marketplace
Embedded banking (accounts)Account details, balances and statementsBusiness accounts inside an accounting tool
Embedded cardsPhysical or virtual cards issued by the platformSpend cards for a fleet or a gig workforce
Embedded FXCurrency conversion inside the productConverting supplier payments in a procurement platform
Embedded lendingCredit offered at the point of needPay-later at checkout; invoice finance in invoicing software
Embedded insuranceCover sold alongside a purchaseTravel insurance in a booking flow
Embedded investingSavings or investment featuresInterest-bearing balances in a payroll app

Embedded payments are the most common starting point. Our guide to embedded payments vs embedded finance explains where payments end and the wider field begins.

How it works: banking-as-a-service

Embedded finance runs on banking-as-a-service (BaaS): the layer of regulated accounts, payment rails and APIs that a bank or regulated provider exposes for others to build on.

  • BaaS is the engine: the authorisations, accounts, FX, settlement and compliance plumbing.
  • Embedded finance is the car: the financial feature a platform ships to its own users on top of that engine.

A typical set-up has three parties:

  1. The platform owns the product and the user relationship.
  2. The provider supplies the API, onboarding tools and operations, such as screening, payments and reconciliation.
  3. The regulated institution (a bank, e-money institution or payment institution) holds the money and is responsible for the regulated activity. Sometimes this is the provider itself.

The platform calls the provider’s API to create accounts, move money or convert currency, and receives status updates, usually by webhook. Our payment API integration guide covers the technical side: sandbox testing, idempotency keys, webhook verification and reconciliation.

Embedded finance in banking

For banks, embedded finance is a distribution model: instead of selling accounts and payments only through their own channels, they make them available to platforms through BaaS. The bank remains responsible for the regulated product and for checking the partners who distribute it, which is why bank-led BaaS programmes come with detailed partner due diligence.

Embedded finance examples

  • Gig and marketplace payouts. Paying drivers, sellers or creators quickly, in their own currency, from inside the platform.
  • Software with payments built in. Accounting, invoicing and ERP tools that pay suppliers and collect from customers without exporting files to a bank.
  • Branded accounts and cards. Platforms offering their own-brand accounts or cards to customers, run by a regulated partner.
  • Cross-border collection. Global businesses collecting in local currencies through virtual accounts, then converting when they choose.
  • Point-of-need credit and insurance. Pay-later at checkout, invoice finance in invoicing tools, and cover sold with a booking.

Embedded finance in B2B and SaaS

Business software is a natural home for embedded finance, because businesses already run their operations inside it:

  • ERP and accounting tools paying approved supplier invoices directly. Our guide to B2B payments covers the methods behind them.
  • Invoicing tools collecting payments by bank transfer and matching them automatically to invoices.
  • Procurement and spend platforms issuing cards and converting currency.
  • Vertical SaaS for sectors such as logistics, construction or hospitality, adding payments and payouts to the workflow its customers already use.

Why platforms adopt embedded finance

DriverWhat it means
Better experienceUsers stay inside one product instead of moving between a bank and the software
New revenueThe platform can earn on payments, FX or cards, often through a fee or revenue share
RetentionFinancial features are sticky; customers rarely switch once their money flows run through a product
Speed to marketLaunching through a partner’s API is faster than building rails and obtaining authorisations
Better dataPayment data helps with reconciliation, credit decisions and product design

For cross-border platforms the case is stronger still: embedding multi-currency accounts and FX removes the friction of customers juggling separate banks and currency providers in every market.

Risks and responsibilities

Embedded finance moves financial risk into products that were not built as financial businesses, so the platform has to manage it deliberately:

  • Regulation. The financial service is regulated even if the platform is not. In the EU, payment services fall under the Payment Services Directive; in the UK, the Payment Services Regulations 2017. Whether the platform needs its own authorisation depends largely on whether it receives or holds customers’ money.
  • Who holds the money. Users need to know where their money is held, by whom, and what protection applies. Deposit protection usually covers bank deposits, not money held by payment or e-money providers.
  • Onboarding and financial crime. Someone must verify users, screen payments and handle suspicious activity. Agree in writing who does what.
  • Dependence on the partner. If the provider changes terms, prices or risk appetite, the feature can change overnight. Check how you would move users if you had to.
  • Fair treatment. Prices, fees and limits should be clear to users before they use the feature.

How to launch embedded finance

  1. Start from the user problem. Which financial step do your users leave your product for today: paying suppliers, getting paid, converting currency?
  2. Choose the model. Decide whether you only move money for your own business, or whether your users will hold balances. The second needs more regulation and onboarding work.
  3. Choose a partner. Check its regulatory status on a public register, its coverage of your currencies and countries, its API and sandbox, and how it holds money.
  4. Agree responsibilities. Write down who onboards users, who screens payments, who handles disputes and support, and who owns each risk.
  5. Build, test and launch small. Integrate in a sandbox, test the failure cases, then launch to a small group before scaling.

Embedding cross-border payments with KwiikPay

KwiikPay provides the account, FX and payout side of cross-border finance by API, for a platform’s own money flows:

  • Accounts. Named GBP, EUR and USD accounts (virtual IBANs) in your company’s name, held apart from KwiikPay’s own money. See multi-currency business accounts.
  • FX. Conversion between 40+ currencies with the margin shown before you confirm.
  • Payouts. Payments to suppliers, sellers and contractors across 30+ corridors to 80+ countries, through regulated banking partners. Eligible customers can also use stablecoin settlement: USDC and EURC on Ethereum, and USDT on Ethereum, BSC and Tron.
  • The API. REST with JSON, idempotency keys, webhooks signed with HMAC-SHA256 and a free sandbox. API access depends on your plan; see the developer page, API payouts and the pricing page.

If you want your own customers to hold balances or accounts through your product, talk to us before you design for it. That is a different arrangement from paying out of your own accounts, with its own checks. The embedded finance use case has more detail.

KwiikPay onboards companies incorporated in the European Economic Area, the United Kingdom, Gibraltar, Switzerland and Canada, where any authorisation their activity requires is current. Companies elsewhere are assessed individually, with no presumption of approval. Account opening is by invitation: request an account and the team replies within one business day.

KwiikPay is a trading name of KWP Finance Limited — registered in Canada as a Payment Service Provider under the Retail Payment Activities Act (RPAA), supervised by the Bank of Canada, and as a Money Services Business with FINTRAC (MSB registration number C100000942), including dealing in virtual currency. These are registrations, not licences. KwiikPay is not authorised by the FCA. KwiikPay is not a bank; banking and e-money services are provided by regulated partner institutions.

Sources

Checked on 25 October 2026. This is general information, not legal advice.

FAQs

What is embedded finance in simple terms?

Embedded finance is when a non-bank product, such as a marketplace, a SaaS tool or a gig platform, offers financial services like payments, accounts, FX or cards directly inside its own app, instead of sending users to a separate bank. A regulated partner provides the financial plumbing through an API, and the product shows it under its own experience.

What is the difference between embedded finance and banking-as-a-service?

Banking-as-a-service (BaaS) is the infrastructure layer: the regulated accounts, payment rails and APIs that a bank or provider exposes for others to build on. Embedded finance is the outcome: the financial feature a platform builds on top of that infrastructure for its own users. BaaS is the engine; embedded finance is the car.

What are examples of embedded finance?

A ride-hailing app paying drivers instantly, a marketplace paying sellers in their own currency, an accounting tool letting businesses pay invoices without leaving the software, a platform issuing branded cards, an e-commerce checkout offering pay-later, or a booking platform selling travel insurance. In each case the financial service sits inside a product whose core business is not finance.

Why do platforms adopt embedded finance?

Mainly for a better user experience (no leaving the product), new revenue (a share of payment, FX or card fees), and stickier customers (financial features are hard to switch away from). For cross-border platforms it also removes the friction of users juggling separate banks and FX providers.

What is embedded banking?

Embedded banking is the part of embedded finance that puts bank-like accounts and services, such as account details, balances and payments, inside a non-bank product. The accounts are provided by a bank or regulated payment or e-money institution behind the scenes; the platform provides the experience.

What is embedded finance in B2B?

In business-to-business software, embedded finance means financial services built into the tools companies already use: paying suppliers from an ERP or accounting system, collecting invoices by bank transfer inside an invoicing tool, converting currency in a procurement platform, or offering trade credit at a B2B checkout.

Is embedded finance regulated?

The financial services are. Payments, e-money, deposits, lending and insurance are regulated activities, so a regulated institution must sit behind each product. Whether the platform itself needs an authorisation, registration or licence depends on what it does, especially whether it handles customers' money, and on the country. Take legal advice on your specific model.

Does KwiikPay offer embedded finance?

KwiikPay provides accounts, FX and payouts by API that a platform can build into its own money flows: holding GBP, EUR and USD, converting between 40+ currencies and paying out across 30+ corridors. If you want your own customers to hold balances or accounts through your product, talk to us before you design for it, because that is a different arrangement with its own checks.

Related
Embedded payments vs embedded finance → Embedded finance use case → Payment API integration guide → What are B2B payments? → Developers → API payouts →

Open your first IBAN today.

Open a multi-currency account, subject to KYB, screening and our risk appetite.

Talk to sales