What Is Banking as a Service? How UK Brands Should Think About BaaS Before Choosing a Platform

What Is Banking as a Service? How UK Brands Should Think About BaaS Before Choosing a Platform

Banking as a service, or BaaS, is a way for a company that is not a bank to offer financial products, such as accounts, cards, wallets or payments, by connecting to a licensed institution through a platform. The phrase is easy to say and hard to pin down, and that is the problem for brand teams. Many cannot tell what a BaaS provider actually does, who holds the licence and what stays their own responsibility. This guide sets out the layers, what each one owns, a checklist for choosing a platform and a view of consolidation risk. It is written for heads of embedded finance, digital leaders and product owners at UK brands and fintechs, and it is general information, not legal advice.

What is banking as a service?

Banking as a service is an arrangement in which a regulated financial institution makes its regulated products available to another company through technology, usually APIs, so that the other company can offer those products under its own brand.

In plain terms, the brand builds the customer experience and the regulated institution provides the regulated capability underneath. The brand does not become a bank. It does, however, take on real responsibilities, which is where most misunderstandings start.

Three points make the definition useful rather than abstract.

• The licence sits with a regulated firm, not with the brand. In the UK, whether a firm can issue e-money, hold customer funds or run payments depends on its permissions from the FCA. Which permissions are needed for which activity is a regulatory question, so check the FCA's own material and take advice.
• The technology and the licence are different things. A BaaS platform can be a technology layer that connects to a licensed institution, or the licensed institution can offer the technology itself. Buyers often assume the two are the same.
• "BaaS" describes infrastructure, not a product. Customers never buy banking as a service. They buy a wallet, a card, a savings pot or a payment feature that happens to run on it.

The four layers and what each one owns

The cleanest way to understand BaaS is to separate four layers. Real arrangements blur them, and one firm can occupy more than one, but the questions you ask a provider are easier to frame when you know which layer you are speaking to. This is our general explanation of how the market is commonly organised. Individual contracts and regulatory models differ.

Layer one: the licensed institution

This is the regulated firm that holds the relevant permissions, for example as an authorised e-money institution or a bank. Broadly, it is the layer that is answerable to the regulator for the regulated activity, and it typically sets conditions on how the product may be run, including onboarding, monitoring and the handling of customer money.

For a brand, the point is simple. Whoever the licensed institution is, its rules flow down to you. You should know its name, what it is authorised to do and what it expects of you.

Layer two: the BaaS platform

The platform is the technology layer. It exposes the licensed institution's capabilities through APIs and tools: opening accounts, issuing cards, moving money, holding balances and ledger functions, and often connections to schemes and data sources. Some platforms are run by the licensed institution. Others are separate companies that work with one or more institutions.

The platform's job is to make the regulated capability usable by developers. It does not, by itself, answer for the regulated activity. Which firm answers for what should be spelt out in contracts.

Layer three: the programme manager

The programme manager runs the product programme on top of the platform and the institution. Depending on the arrangement, this can include onboarding design, customer support, fraud and transaction monitoring operations, reporting to the licensed institution and oversight of compliance processes. Some brands run the programme themselves. Others use a specialist, or the platform provides this role.

This layer is often the least visible and the most consequential. Many launch delays come from unclear ownership of day-to-day operations rather than from missing technology.

Layer four: the brand

The brand owns the customer relationship, the proposition and the experience. It decides who the product is for, what it is called, how it is marketed and how it fits into the existing customer journey. It also carries the reputational risk when something goes wrong, whatever the contract says about who is at fault.

That last point is worth holding on to. In our view, customers do not distinguish between your brand and the institution behind it. If a payment fails or funds are delayed, they contact you.

BaaS and embedded finance: how they relate

People often use BaaS and embedded finance as if they were synonyms. They are related but not the same.

• BaaS is the supply side. It is the infrastructure that makes regulated services available through technology.
• Embedded finance is the demand side. It is the practice of placing a financial service inside a product or journey the customer already uses, such as a retailer's app or a platform's checkout.

A brand that wants to offer a wallet in its app is doing embedded finance. To do it, it will usually use BaaS infrastructure. Our embedded finance work starts from that distinction: the brand's job is to design the proposition, and the infrastructure choice follows from it, not the other way round.

What stays with the brand

Using BaaS does not move every responsibility to someone else. Whatever the exact contractual model, brand teams should plan for the following to stay with them, at least in part.

• The customer relationship and complaints handling. Customers will see the brand as the provider.
• Product design and marketing. Financial promotions and customer communications may be subject to FCA rules, and what you publish under your own brand is your own to get right. Check the FCA's material and take advice for your product.
• Oversight of your providers. In our view, you should understand and manage the firms you depend on. Check what your regulated partner contractually expects of you.
• Operational readiness. Support, exception handling, fraud operations and reconciliation will not run themselves, whichever layer technically owns them.
• Data and integration. The customer experience depends on the quality of your own systems and how they connect to the platform.

None of this is an argument against BaaS. It is an argument for being clear about who owns what before you sign.

Reading how UK providers describe their status

UK providers describe their regulatory status in different ways, and the differences matter. Providers also market their authorisations, and marketing language can run ahead of the detail.

One example from Innovify's partner research, with the provider deliberately unnamed: a UK card and e-money provider announced on its own blog that it had received FCA authorisation as an Authorised Electronic Money Institution on 28 May 2026. Since late September 2026, its LinkedIn posts have included UK-specific content aimed at small businesses. These are the provider's own claims as we observed them, not independently verified.

We draw one lesson from this, and it is analysis rather than reported fact. Authorisation is becoming a selling point, and buyers should treat it as a starting point for questions. What exactly is the firm authorised to do? Is it the party that will hold your customers' funds? Does the authorisation cover the product you want to launch? The FCA publishes a public register of authorised firms, and the FCA's own material is the right place to check a firm's status and permissions.

The same caution applies to the models in which a brand works with a regulated firm, for example as its agent or as a customer of an authorised provider. Those models carry different responsibilities and different regulatory consequences. We do not set out the detail here, because the FCA's published material is the right primary source and your legal adviser should confirm what applies to you.

A checklist for choosing a BaaS platform

Choosing a platform is a business decision first and a technical one second. Use these questions in this order.

1. Who is the licensed institution, and what is it permitted to do? Ask for the name, the permissions that matter for your product and where you can verify them. Do not rely on a sales deck.
2. Who holds customer funds, and how are they protected? Ask the provider to explain the arrangements in writing and have your adviser review them.
3. Which layers does the provider cover, and which are yours? Map onboarding, monitoring, support, complaints, reporting and reconciliation to a named owner on each side.
4. What does the platform actually expose? Look at the APIs, sandbox, documentation and error handling. A platform you cannot test properly is a platform you cannot plan around.
5. How does it fit your existing stack? Consider identity, payments, loyalty, CRM and finance systems. Integration is where much of the effort sits.
6. What are the commercial terms and exit terms? Understand fees, minimums, term, and what happens to your customers, data and tokens if you leave. Plan the exit before you need it.
7. How will it behave under stress? Ask about service levels, incident handling, scheme and regulator reporting, and how the provider treats a customer who is vulnerable or in difficulty.
8. How does the provider handle change? Products, rules and ownership all change. Ask how you will be told and how much notice you will get.
9. Can you run a small, real launch first? A limited pilot with real users will tell you more than any specification.

Two further points make the checklist more useful. First, score providers on the same questions and write down the answers, so the decision can be explained later to your board, your risk function and your own partners. Second, involve compliance and legal at the start, not at contract stage.

Consolidation: why it belongs in your selection

The BaaS market has been changing hands. In October 2026, This Week in Fintech, summarising company announcements, reported two deals: a digital-asset custodian acquired a payouts platform, and the acquisition of a BaaS provider completed. We have deliberately not named the companies, and we report this as third-party reporting rather than our own finding.

Innovify's market research reads these as signs of continued consolidation across payments, BaaS and digital-asset infrastructure. Two deals do not make a trend on their own, and the reporting we have does not say how any customer was affected. What follows is our general reasoning, not evidence about any particular provider.

• Ownership can change over the life of a contract. A platform you choose today may belong to a different company in future, with different priorities.
• Roadmaps follow owners. Features that matter to a retailer may matter less to a new parent.
• Concentration is a risk in its own right. If one provider sits under your whole proposition, a change at that provider is a change for you.

The practical response is to build for change at the point of selection. Prefer architecture in which your customer experience and your own data are separable from the platform. Keep integration points narrow. Ask what would happen to your service if the provider changed hands, and record the answer. How to examine a specific provider in a specific deal is a separate subject, and one to approach with your advisers.

Questions retailers and brands should ask first

Brands that are not financial companies often start from the wrong end. They begin with a provider shortlist when the first job is to decide what the proposition is.

• What customer problem does the financial feature solve? A wallet that gives customers faster refunds is a different product from one that holds stored value.
• What do you want to own? The data, the relationship, the economics or all three. The answer shapes the model you choose.
• How much of the operation do you want to run? Your appetite for running operations decides how much of layer three you take on.
• What is your first market? For UK brands, UK regulation and UK customer expectations come first, and international plans can follow.

Where Innovify fits

Innovify is a technology partner with deep expertise in banking, financial services, fintech and insurance, and we design compliance in from day one. We are an implementation partner across multiple fintech platforms, which means we help brands, retailers and platforms work out the proposition first and then build the product and integrations on the infrastructure that suits it.

If you are weighing up a BaaS route, our Embedded Finance & Digital Wallets page describes how we approach it. We build for regulated clients. We are not an FCA-authorised firm and we do not give legal or regulatory advice, so your compliance function and advisers should confirm what your own obligations are.

A sensible first conversation is short: the proposition, the four layers and who owns what. It usually shows within a session which questions to put to providers.

FAQ

What is banking as a service in simple terms?

Banking as a service is an arrangement in which a licensed financial institution makes regulated products, such as accounts, cards or payments, available to another company through APIs so that company can offer them under its own brand. The brand builds the customer experience and does not become a bank. Responsibilities are shared between the institution, the platform, any programme manager and the brand, and the split depends on the contract and the regulatory model.

What is the difference between BaaS and embedded finance?

BaaS is the infrastructure that makes regulated financial services available through technology, while embedded finance is the practice of placing a financial service inside a product or journey the customer already uses. A retailer that adds a wallet to its app is doing embedded finance, and it will usually use BaaS infrastructure to do it. One describes the supply side and the other the customer-facing product.

Who holds the licence in a BaaS arrangement?

The licence is held by the regulated institution behind the platform, such as an authorised e-money institution or a bank, not by the brand. In some models a brand operates under the authorisation of a regulated firm, for example as its agent, and the responsibilities differ by model. Check the FCA's published material and the FCA register, and take advice on what applies to your circumstances.

What should a retailer check before choosing a BaaS provider?

A retailer should check who the licensed institution is and what it may do, who holds customer funds, which operational tasks the provider covers and which remain with the retailer, and what the exit terms are. It should also test the platform in a sandbox, ask how change and ownership events are handled and run a limited pilot before scaling. Involve compliance and legal advisers from the start.

Is consolidation among BaaS providers a risk for brands?

Consolidation can be a risk because ownership, roadmaps and priorities can change over the life of a contract. In October 2026, This Week in Fintech reported that a BaaS provider's acquisition had completed and that a payouts platform had been acquired by a digital-asset custodian. We treat that as context, not as evidence about any one provider. Brands can respond by keeping their customer experience and data separable from the platform and by agreeing change and exit terms at the outset.

Conclusion

Banking as a service gives brands a route to financial products without becoming a bank, but it does not remove responsibility. Understand the four layers, know who holds the licence and decide what stays with you. Choose a platform with the checklist above, read each provider's regulatory claims as a starting point for questions and build with consolidation in mind. Confirm the regulatory detail with the FCA's own material and your advisers.