What Is Embedded Finance? A UK Guide for Brands That Are Not Banks

What Is Embedded Finance? A UK Guide for Brands That Are Not Banks

If you lead digital, commerce or product at a retailer, marketplace or platform, you have probably heard "embedded finance" in several meetings this year and been given a different definition each time. The term matters because it describes a real shift in who gets to offer financial products: the brand customers already use, not only the bank. It is also blurred with payments, banking as a service and open banking, which makes it hard to scope a project or to know which rules apply. This guide gives a plain definition, shows what embedded finance looks like in practice, outlines the UK regulatory position and ends with a way to choose a first use case.

What is embedded finance? A plain-English definition

Embedded finance is the practice of offering a financial product, such as a payment method, wallet, card, credit or insurance, inside a non-financial company's own app, website or checkout, with a regulated financial institution doing the regulated work behind the scenes.

Three tests help you recognise it:

• The customer experience belongs to the brand. The customer stays in your app or checkout. They do not get sent to a bank's website to complete the journey.
• The financial service is delivered by someone licensed to deliver it. The brand presents the product. A regulated partner, or the brand itself if it holds the right permissions, performs the regulated activity.
• The connection is technical. The brand's product talks to the provider's systems through APIs, so the financial feature behaves like any other feature in the product.

A simple example: a retailer's app lets a customer hold a balance, pay in store with a tap and see their rewards in the same place. The retailer designed the experience. A regulated provider holds and moves the money. Nobody had to download a banking app.

Two points of caution. First, "embedded finance" is a market description, not a legal category. What matters legally is which activity is being performed and by whom, and we return to that below. Second, embedding finance does not make a brand a bank. The aim for most non-financial brands is to launch a financial product without becoming one.

How embedded finance works: three parties and one customer

Every embedded finance programme, whatever the product, has the same basic shape. In outline there are three parties around one customer.

• The brand. This is you: the retailer, marketplace, platform or software business with the customer relationship. You own the product design, the journey, the customer communications and the commercial case.
• The infrastructure or platform provider. This is the technology layer that exposes financial capabilities, such as accounts, card issuing or payments, through APIs. Banking as a service is the best-known name for this model, although the term is used loosely.
• The regulated partner. This is an authorised firm, for example a bank or an electronic money institution, whose permissions allow the regulated activity to take place. Some programmes combine the platform and the regulated partner in one firm. Others separate them.

The exact split of responsibilities varies from programme to programme and is set by contract, so treat the outline above as a starting map rather than a rule. The point to take away is that the brand is rarely alone and rarely in control of every layer. Most of the hard questions in an embedded finance project are, in effect, questions about where one party's responsibility ends and the next begins.

Embedded payments versus embedded finance (and the terms around them)

Several neighbouring terms are used as if they were synonyms. They are not, and mixing them up is a common reason projects are scoped badly.

• Embedded payments means accepting or sending payments inside your own product, for example a checkout that never leaves your app, or a platform that pays its sellers. It is one part of embedded finance, and often the first.
• Embedded finance is the wider category. It includes payments but also holding money in a wallet, issuing cards, offering credit or pay-over-time options, and distributing insurance.
• Banking as a service (BaaS) describes how some regulated providers make their services available to other businesses through APIs. It is one way to deliver embedded finance, not a synonym for it.
• Open banking and open finance are about customers sharing their data, or authorising payments, through regulated third parties. They can be used inside an embedded product, but they are a different thing. Embedding is about the brand offering a product. Open banking is about access to account data and payment initiation with the customer's consent.

A practical way to keep them straight: embedded payments moves money, embedded finance offers a financial product, BaaS is a delivery model and open banking is a data and access model.

Embedded finance examples for retailers and platforms

Embedded finance is easiest to understand through the products brands actually launch. The five below cover most of the conversations we see with non-financial brands.

Digital wallets

A wallet lets customers hold a balance or store payment methods inside your product. For a retailer it can speed up checkout, make refunds and rewards simpler and keep customers inside the brand's own experience. What a wallet is, legally, depends on how it is built and what it holds, which is why the regulatory questions come early. Innovify's Embedded Finance & Digital Wallets page sets out the kind of wallet work we support.

Branded cards

A branded card, whether physical or virtual, puts the brand's name on the customer's payment instrument. It can be a loyalty tool, a way to reward spending or a way to give a platform's users access to their own funds. The card itself is issued through a regulated issuer, with the brand shaping the programme around it.

Buy now, pay later and pay-over-time

Offering customers a way to split a purchase is among the most visible forms of embedded finance at checkout. It is also credit, and credit is an area where the FCA's own material should be read carefully before any design decisions are made.

Loyalty and rewards

Loyalty programmes are often the gentlest on-ramp for a brand that has never offered a financial product. Points, cashback and stored rewards sit on a spectrum from pure marketing to something that looks much more like money, and where a particular design falls on that spectrum is a question to answer with proper advice.

Lending and insurance

Embedded lending, such as financing for a platform's merchants, and embedded insurance, such as cover offered at the point of sale, follow the same pattern: the brand knows the customer and the moment of need, while a regulated provider carries the regulated activity.

What the market evidence says

We try to separate reported fact from our own interpretation, so here is each in turn. The evidence below is from Innovify's own market monitoring in October 2026 and, in places, is summary-level, so read the original sources before relying on any detail.

Demand is specialist but commercially valuable. Ubersuggest data reviewed by Innovify in October 2026 puts UK searches for "embedded finance" at about 720 a month, with an estimated cost per click of about USD 20.78. That is a small audience, but advertisers evidently value it. Our interpretation: this is a term used by decision-makers researching a specific project, not by a mass audience. Separately, the same keyword research found that related terms such as "banking as a service" and "open finance" are low competition, which suggests the vocabulary around this topic is still settling. That is also our interpretation, and a reason to define your terms clearly in internal papers.

Providers are bundling capabilities. According to Finextra on 15 October 2026, Mastercard launched its Global Money Platform, which brings fiat and stablecoin accounts together through a single API. We cite it as an example of a wider pattern, not as a recommendation: card, wallet and account capabilities are increasingly offered together by one provider. Our interpretation is that a brand may soon be able to source several building blocks through one integration, which changes the build-or-assemble conversation.

The UK wallet landscape may change. Finextra reported on 20 October 2026 that the UK Competition and Markets Authority has proposed opening iPhone contactless (NFC) access to rivals of Apple Pay, through both Secure Element and host card emulation routes. It is a proposal only and is not final. If it were implemented, it could widen the options for brands wanting tap-to-pay wallets on iPhones. We would treat it as a development to watch, not a plan to build around.

Inertia is a competitor. Innovify's review of recent small-business payments research shared on LinkedIn in mid-October 2026 by Adyen, with Visa, and by Mastercard, points to inertia, the sense that "the current process works", as a brake on adoption of embedded payments among software and platform businesses. We have seen only a summary of that research, and our reading is medium-confidence. The practical lesson stands regardless: an embedded product has to be clearly better than what customers already do, and it has to work smoothly, because integration quality tends to matter more than stated enthusiasm.

The UK regulatory perimeter in outline

This section is an outline for orientation. It is not legal advice, and it does not describe the position for your particular product or organisation. Take advice from a suitably qualified adviser, and read the FCA's own material, before making decisions.

In the UK, financial services regulation attaches to activities, such as providing payment services, issuing electronic money, offering credit or distributing insurance. It does not attach to the label "embedded finance". The Financial Conduct Authority (FCA) is the main conduct regulator for most firms in this space, and the Prudential Regulation Authority (PRA) supervises banks and insurers on the prudential side.

For a non-financial brand, the practical question is usually: which party performs the regulated activity? In broad terms, a brand has three routes to consider:

1. Work under an authorised partner's permissions. The partner performs the regulated activity and the brand distributes or presents the product. The FCA's pages describe agent and similar models.
2. Seek the brand's own authorisation or registration. This is a significant undertaking and changes what the business is, so it is usually a considered strategic decision rather than a starting point.
3. Design a product that sits outside regulated activity. Sometimes a product can be built that does not trigger regulation. Whether a particular design does so depends on the facts and needs specialist advice.

Several topics come up repeatedly. In Innovify's own tests of what AI answer engines say about embedded finance, the FCA's website was the most-cited source (23 citations across the prompts tested in the 28 September 2026 baseline), and the topics we flagged as needing a clear FCA-anchored explanation were permissions, the agent and electronic money models, the payment services rules that derive from the second Payment Services Directive (PSD2) and data protection. Those are the places to start reading on fca.org.uk.

Two further points. Even where a regulated partner performs the regulated activity, the brand still designs the customer journey, and in our view the journey, the wording and the way problems are handled deserve the same scrutiny as the contract. Second, if your embedded experience uses AI, note that an FCA speech on 19 October 2026 on finance in the age of AI was reported as applying existing frameworks, including the Consumer Duty and senior-manager accountability, to AI rather than creating new rules for agents. Innovify's industry monitoring flagged that the primary source should be read before relying on detail, and we would say the same to you.

How to choose a first use case

Most brands do not need to launch everything. The strongest programmes start with one use case that fits the business, and then extend. These five questions help you choose.

1. What customer problem does it solve? Start from a friction you can already see in your data or your support queue, such as slow refunds, abandoned checkouts or repeat top-ups, not from the product that sounds most impressive.
2. How often will customers use it? Frequency creates habit. A feature used weekly teaches customers more than one used once a year.
3. How heavy is the regulation? Lighter-touch use cases, with a regulated partner carrying most of the load, are usually faster to bring to market. Heavier ones are not wrong, but they need a longer plan and earlier advice.
4. What does it need from your systems? Check where customer identity, order data and payments already live. The cost and delay of an embedded product is often in the integration, not in the financial feature itself.
5. How will you know it worked? Decide before launch what you will measure, such as checkout conversion, retention or basket size, and what result would make you stop, change course or extend.

Then test before you commit. A small, time-boxed test with real users will tell you more than a long internal debate. This is how Innovify AI Labs works for enterprise teams: it runs several proofs of concept in parallel, tests with real users and finishes with a business case ready for funding.

Common mistakes to avoid

• Treating it as a technology project only. The product, the regulatory structure and the operating model have to be decided together.
• Assuming the regulated partner handles everything. The partner carries the regulated activity. The brand still owns the customer relationship and the experience.
• Underestimating inertia. If the current way of paying works well enough, your product must offer a clear reason to change.
• Skipping the run phase. Customer support, reconciliation and monitoring are part of the product from the first day, not an afterthought.

Where Innovify fits

Innovify is a technology partner with deep expertise in banking, financial services, fintech and insurance. We help mid to large businesses, including brands that are not financial companies, build AI-native products, modernise their technology stack and launch fintech products. We act as an implementation partner across multiple fintech platforms, and we design compliance in from day one.

To be clear about our role: Innovify is a technology partner, not a regulated financial institution. We build for regulated clients and alongside regulated providers, and we do not give legal advice. If you are weighing a wallet, card or pay-over-time proposition, the useful first conversation is usually about which use case to start with and what the build needs to include. You can read more about our embedded finance and digital wallet work, or get in touch and we will talk it through.

FAQ

What is embedded finance in simple terms?

Embedded finance means a financial product is offered inside a non-financial company's own app, website or checkout. The customer stays in the brand's experience, while a regulated provider does the regulated work in the background. Common examples are wallets, branded cards, pay-over-time options and insurance offered at the point of sale.

Is embedded finance the same as embedded payments?

No. Embedded payments is one part of embedded finance. It covers taking or sending payments inside your own product. Embedded finance is wider and also covers holding money, issuing cards, offering credit and distributing insurance. Many brands start with payments and extend from there.

Does a retailer need to be authorised by the FCA to offer embedded finance?

It depends on the product, the structure and who performs the regulated activity, so there is no single answer. Many non-financial brands work with an authorised partner that carries the regulated activity, while others consider their own authorisation. This is not legal advice. Read the FCA's own material and take advice on your specific circumstances before you decide.

What are examples of embedded finance for retailers?

Typical examples are a digital wallet inside the retailer's app, a branded virtual or physical card, a buy now, pay later option at checkout, a loyalty or rewards scheme that holds value, and insurance or financing offered at the point of sale. Each involves a different regulatory position, so it is sensible to assess them one at a time.

Where should a brand start with embedded finance?

Start with one use case that solves a clear customer problem and that customers would use often. Check how heavily regulated it is, what it needs from your systems and how you will measure success. Then run a small test with real users before committing to a full build.

Conclusion

Embedded finance is a simple idea with a lot of detail underneath it: a brand offers a financial product inside its own experience, and a regulated provider carries the regulated activity. For a UK brand that is not a bank, the work is in choosing one use case that fits the business, understanding which party does what, and reading the FCA's own material alongside proper advice. Define the term clearly, start small, test with real customers and extend from there.