What Is Embedded Finance?

What is embedded finance?

Embedded finance is the integration of a financial product into a service whose main purpose is something else. Instead of visiting a bank, lender or insurer separately, a customer accesses that product while shopping, running a business or using another platform.

Examples include instalment credit offered at checkout, a payment account inside accounting software, or insurance offered during a travel booking. The financial service becomes part of an existing activity rather than a separate destination.

The important distinction is between the interface and the provider. A retailer or software company may control what the customer sees, while a bank, payment institution, lender or insurer supplies the regulated product behind it. Sometimes the platform itself holds the necessary permissions.

Embedded finance is therefore a distribution model, not a licence category. The rules depend on the underlying activity, the entities performing it and the jurisdiction involved.

How embedded finance works

An embedded product commonly involves three layers:

• The platform: the retailer, marketplace or software provider that owns the customer experience.
• The technology layer: systems that connect the platform to financial providers, often through application programming interfaces, or APIs.
• The financial provider: the entity responsible for supplying the account, payment service, loan or insurance contract.

One company may perform several roles. Equally, an apparently simple feature can depend on multiple subcontractors and regulated entities.

Example: a marketplace seller account

Consider a marketplace that lets sellers receive sales proceeds into an account and spend the balance using a card.

The seller begins an application within the marketplace. A financial provider checks identity and business information, performs required screening and decides whether to open the account. These checks can be presented through the marketplace without becoming the marketplace’s own regulated service.

When a customer buys something, the payment is processed and the seller’s entitlement is recorded. Depending on the structure, money may reach an individual account or a pooled account supported by records identifying each seller’s balance. Fees, refunds and reserves can affect the amount available to withdraw.

The displayed balance is therefore only one part of the arrangement. The seller also needs to know who legally holds the money, when it becomes available and what happens if the marketplace or provider fails.

Common types of embedded finance

Payments

Embedded payments let customers pay without leaving the platform’s normal workflow. Examples include payment acceptance in appointment-booking software and automated collection within subscription-management tools.

Behind the interface, providers may handle payment authorisation, acquiring, settlement, fraud controls and refunds. A platform can integrate a licensed payment provider without itself becoming a bank, but its exact role still matters for regulation.

Accounts and cards

Business software can offer an account for receiving funds, paying suppliers or managing expenses. A card may let staff spend from that balance under employer-defined controls.

The account might be a bank deposit account, a payment account or an electronic-money account. Similar-looking dashboards do not make these products legally equivalent.

Lending

Embedded lending places a credit offer where a funding need arises: at checkout, when purchasing equipment or inside a seller dashboard.

The lender assesses eligibility and sets contractual terms, potentially using transaction data supplied by the platform. Repayment might occur through scheduled instalments or deductions from future sales. Customers should distinguish loans from other financing structures, such as receivables purchases; the legal rights and disclosure requirements can differ.

Insurance

Embedded insurance offers cover alongside a related purchase or activity, such as travel, equipment hire or deliveries.

The insurer underwrites the risk, while the platform may distribute the policy or introduce the customer. A convenient purchase process does not remove the need to check exclusions, excesses, cancellation rights and claims procedures.

Embedded finance versus related concepts

Banking-as-a-service

Banking-as-a-service, or BaaS, describes arrangements through which a bank makes banking capabilities available to another business, often using APIs.

Embedded finance describes the customer-facing result. BaaS can support that result, but not all embedded finance involves banking: an insurer or non-bank lender may supply the underlying product.

A technology provider advertising BaaS is not necessarily a bank. Customers and business partners should identify the actual licence holder and contractual provider.

Open banking

Open banking enables authorised access to account information or payment initiation under applicable rules and customer permission. It can help an embedded lender assess cash flow or let a customer pay directly from a bank account.

It does not, by itself, authorise a platform to accept deposits, lend or issue electronic money.

Digital wallets

A wallet is an interface or product that can hold payment credentials, monetary value or digital assets. It may support embedded finance, but the word ‘wallet’ says little about legal protection. A stored-value wallet and a tool that merely stores card details operate differently.

Why businesses use it — and where the trade-offs arise

Embedded finance can remove repeated data entry and connect financial actions to business records. For example, accounting software can match an outgoing payment to an invoice automatically, reducing manual reconciliation.

Platforms may earn referral fees, transaction fees, subscription revenue or a share of product income. Financial providers gain a distribution channel and, where lawful, access to relevant customer data.

These incentives can also create conflicts. The most prominently displayed credit offer may not be the cheapest available elsewhere. A platform may make switching difficult if payments, records and financing are tightly connected.

Access can also depend on the platform relationship. If a marketplace closes a seller’s trading account, the seller should understand whether the associated financial account remains accessible and how outstanding funds or loans will be handled.

Regulation: the activity matters more than the branding

Financial permissions generally attach to particular entities and activities. A partner’s licence does not automatically cover everything a platform does. Introducing customers, arranging products, handling funds and making credit decisions can trigger different obligations.

European Union

PSD2 provides a framework for payment services, while EMD2 governs electronic-money institutions. Banks operate under a separate banking framework. Depending on its role, a platform may act as an agent, distributor, outsourced service provider or regulated provider in its own right.

Payment institutions and electronic-money institutions must protect relevant customer funds through applicable safeguarding arrangements. Those funds are not automatically bank deposits covered by a deposit guarantee scheme.

Lending and insurance bring additional EU and national requirements. MiCA may be relevant where cryptoassets are involved; it is not a general embedded-finance licence. Check the national competent authority’s register and guidance, alongside European Banking Authority resources, as frameworks evolve.

United Kingdom

The FCA authorises or registers many payment and electronic-money firms and regulates relevant consumer-credit and insurance activities. Banks are subject to a separate authorisation and supervisory framework involving the PRA and FCA.

Safeguarding by a payment or electronic-money institution is different from Financial Services Compensation Scheme protection for eligible bank deposits. Relevant retail activities may also fall within the Consumer Duty. The provider’s permissions and the specific product determine which requirements apply.

United States

Embedded finance commonly combines bank partnerships with non-bank technology providers. Federal and state requirements can overlap, including bank supervision, money-transmission licensing, lending rules and consumer-protection obligations.

FDIC insurance protects eligible deposits at insured banks against bank failure, not the failure of a non-bank app itself. Where funds are held through an intermediary, pass-through insurance depends on satisfying applicable ownership and recordkeeping requirements. Customers should not assume that a partner bank’s name makes every platform balance insured or immediately recoverable.

Switzerland

FINMA distinguishes between banks, holders of a FinTech licence and other financial-market participants. The FinTech licence permits certain deposit-taking activities within defined limits and restrictions, including restrictions on investing deposits or paying interest.

Deposits accepted under that licence are not protected by Swiss deposit insurance. Anti-money-laundering supervision or affiliation is also not equivalent to a banking licence. Check the entity’s precise status rather than relying on the label ‘Swiss regulated’.

United Arab Emirates

The Central Bank of the UAE oversees relevant banking, payment and stored-value activities within its remit. The Dubai International Financial Centre and Abu Dhabi Global Market have separate financial-services regulators and frameworks.

A permission issued in one framework should not be assumed to authorise every activity elsewhere in the UAE. Check the provider, service, customer location and territorial scope of its permission.

Singapore

The Monetary Authority of Singapore regulates payment services under the Payment Services Act, with separate frameworks for banking and other financial activities.

A payment institution’s licence is not a bank licence. Applicable safeguarding requirements depend on the service and licence category; payment balances should not automatically be treated as insured bank deposits. MAS’s directory helps establish which activities an entity is permitted to conduct.

What to check before using an embedded product

The main questions are practical, not just regulatory:

• Who is the provider? Find the legal entity named in the financial contract, not only the platform’s trading name.
• What is the product? Establish whether the balance is a deposit, electronic money, pending settlement or another claim.
• Where does the money go? Ask about individual versus pooled accounts, safeguarding and any applicable deposit protection.
• What does it cost? Include conversion charges, late fees, withdrawal costs and charges triggered by leaving the platform.
• Who uses the data? Check what the platform and provider share, for which purposes, and whether optional uses can be declined.
• Who resolves problems? Identify the complaints contact, available external redress and the process for disputed transactions.
• Can the service be exited? Check withdrawal rights, data export, outstanding repayments and what happens if a provider partnership ends.

The bottom line

Embedded finance changes where a financial product is accessed, not the need to understand its legal structure. Its strongest practical benefit is connecting a financial action directly to the activity that requires it.

A useful test is to look past the interface: identify the provider, follow the money and understand the protection and exit arrangements. Those details matter more than whether the experience feels like banking.