How a Retailer Launches a Digital Wallet on a BaaS Stack: Agent, Authorised E-Money Partner or Own Licence?
A retailer that wants to launch a digital wallet, whether to hold stored value, speed up checkout or build loyalty into a payment product, soon meets a question that has nothing to do with design. Under whose permission will the wallet operate? In the UK, the answer determines who is responsible to customers and to the regulator, what the retailer must build and run itself, and how much control it keeps over the product. There are three broad routes: act as an agent of an authorised firm, partner with an authorised e-money institution under its programme, or obtain your own authorisation. This guide explains each in plain terms and where banking-as-a-service platforms fit. It is analysis, not legal advice.
Start with the question, not the platform
Most wallet projects begin by shortlisting banking-as-a-service platforms. That is understandable, because platforms are visible and sell hard. But the platform is the second decision. The first is the regulatory route, because it determines which platforms are even suitable and what they will expect from you.
A retailer launching a wallet is usually a commerce business, not a financial-services firm. Innovify's view is that this is the most useful framing: the retailer's job is to launch a wallet without becoming a bank, and the routes below are different ways of dividing the regulated work between the retailer and a firm that already carries it.
Throughout this guide we point to primary sources. The FCA publishes its expectations in its Handbook and guidance, and its Financial Services Register shows which firms are authorised and in what capacity. The UK legislation behind e-money and payment services is the Electronic Money Regulations 2011 and the Payment Services Regulations 2017. We name them so you know where to look. We do not summarise their detail, because requirements change, depend on the structure of your product and must be confirmed with the FCA's published guidance and your legal advisers.
Route one: act as an agent of an authorised firm
Under this route, the retailer operates the wallet as an agent of a firm that is itself authorised to provide the relevant services. The authorised firm remains responsible for the regulated activity and for the retailer's conduct as its agent, and it will want to see that the retailer's processes, systems and staff meet its standards.
What it tends to suit
This route can suit a retailer that wants a wallet quickly, has limited appetite for regulatory complexity and is comfortable with the authorised firm setting the rules. The retailer's role is closer to a distribution and customer-experience role, with the regulated engine sitting elsewhere.
What the retailer carries
Even as an agent, the retailer is not free of obligations. In broad terms it should expect to:
- operate within the authorised firm's compliance framework, including the controls, training and reporting that framework requires
- accept oversight, audit and in some cases termination rights over the arrangement
- handle customer communications and complaints in line with the authorised firm's requirements
- protect customer data in line with data-protection law, including GDPR
The trade-offs
The agent route usually offers the shortest path to launch and the lightest direct regulatory load. In exchange, the retailer depends on the authorised firm for the regulated service, has less control over how the product is designed and may find it harder to change provider later. How an agent arrangement is recognised and registered is a matter of the FCA's published guidance, and you should confirm the exact status for your structure rather than assume it.
Route two: partner with an authorised e-money institution
In the second route, the retailer partners with an authorised e-money institution and launches the wallet under that institution's licence or programme. The retailer typically takes a role often described as programme manager or distributor, owning the brand, the customer relationship and much of the product, while the institution holds the permissions and provides the regulated service.
The labels used for these roles vary between providers, and the exact regulatory status depends on how the arrangement is structured. This is the single most important thing to confirm in writing before you build. Two arrangements that look similar commercially can have different regulatory consequences.
What it tends to suit
This route can suit a retailer that wants more control over the product and customer experience than an agent usually has, is prepared to take on more operational responsibility, but does not want to pursue its own authorisation. It is a common pattern for businesses that are building a wallet as a durable product rather than a short-term feature.
What the retailer carries
The institution carries the permissions. The retailer still typically carries a substantial share of the work, including:
- designing customer onboarding and verification to meet the institution's requirements
- operating or commissioning fraud monitoring, transaction monitoring and customer support
- managing customer complaints and communications
- maintaining the integrations between its own systems and the institution's platform
- meeting the institution's reporting, audit and oversight expectations
The trade-offs
A partner programme can offer a good balance between control and regulatory load, but it depends on the quality of the institution and the contract. Because the institution's permissions underpin the whole product, the retailer should understand how customer funds are protected, what happens if the relationship ends and how easily the wallet could move to another provider.
Route three: obtain your own authorisation
The third route is to become an authorised firm in your own right. The retailer applies to the FCA, and if successful, carries the regulated activity directly. It will have its own obligations around safeguarding customer funds, governance, capital, systems and controls, and ongoing reporting. We have deliberately not quoted figures, timelines or thresholds, because they depend on the type of authorisation and change over time. The FCA's published guidance is the place to find them.
What it tends to suit
This route tends to suit a retailer for whom the wallet is strategic, long-term and central to the business, and which has the appetite and resource to run a regulated entity. It gives the greatest control over the product and its economics, and the least dependence on a third party.
What the retailer carries
Everything described under the other routes, plus direct accountability to the regulator. That includes senior individuals who are answerable for the firm's conduct and controls, an authorisation process that must be completed before launch, and a permanent compliance function. It is a different kind of organisation from a retailer, and the decision should be taken by the board with legal advice, not by a product team.
The trade-offs
Own authorisation offers control and independence, but it is the slowest and most demanding route to market, and it changes the nature of the business. For many retailers it is a destination reached after starting under a partner, not the first step.
Where banking-as-a-service platforms fit
Banking-as-a-service, often shortened to BaaS, describes platforms that package financial infrastructure so that a business can launch products without building it all. The term is easy to misread. A BaaS platform is a technology and services layer. It does not, by itself, answer the question of whose permissions the wallet runs under.
In practice, a wallet launch usually combines several categories of provider.
- A BaaS platform that provides the core services and interfaces your wallet builds on.
- An authorised e-money institution or issuing partner whose permissions cover the regulated activity. Sometimes the platform and the institution are the same firm, and sometimes they are not.
- A payment processor or card issuer-processor where the wallet supports cards or payment acceptance.
- Identity, verification and fraud tooling that supports onboarding and ongoing monitoring.
- Your own systems, including the app, the commerce platform and customer service tooling.
The useful question to ask any platform is not "what can you do?" but "under whose permissions does this operate, and what does that mean for us?" Ask the same question of any development partner. Our own embedded finance and digital wallets work is the context for this view: we would start from the regulated-partner model rather than from the technology. We deliberately do not name individual platforms here, because the right choice depends on the route and the product.
We have written separately about the broader entry decision for embedded finance, including financial-services-led and commerce-led approaches, and about what it takes to build a wallet. This guide is narrower. It is about the permission model behind the wallet, and it should be read as a complement to those pieces.
How to choose between the routes
There is no universally correct route. The decision depends on a small number of questions, and we suggest working through them in order.
- How central is the wallet to your business? A feature that supports checkout points towards the lighter routes. A core product that you expect to run for years points towards a partner programme or, eventually, your own authorisation.
- How much control do you need? If you need to shape the product, the customer journey and the commercial terms, an agent arrangement may feel restrictive.
- How much regulatory responsibility can you carry? Be realistic about whether you can staff compliance, fraud and operations, and about who in your organisation would be accountable.
- How quickly must you launch? Speed usually favours the routes that rely on an authorised firm's existing permissions.
- What is your exit position? Consider what happens if the relationship ends. Portability of customers, balances and data matters more than it appears at the start.
- What will the authorised firm require of you? Ask for its requirements in writing before you commit, and compare more than one.
In our view, retailers often begin with a lighter route and revisit the question as the wallet grows; that is our judgement rather than a measured finding. Choosing a route that does not close off that path is a sensible design goal.
Questions to put to any provider or partner
Whichever route you favour, the quality of the answers you receive will tell you a good deal.
- Which firm's permissions does the wallet operate under, and how can we verify them on the Financial Services Register?
- What is our regulatory status under this structure, and where is that written down?
- How are customer funds protected, and what happens to them if the arrangement ends?
- What do you require from us on onboarding, monitoring, complaints and reporting?
- How do you handle data protection and the roles of controller and processor?
- What would it take to move the wallet to another provider?
- What would you advise us not to do?
Where Innovify fits
Innovify is a technology partner with deep expertise in banking, financial services, fintech and insurance. We help mid to large businesses build AI-native products, modernise their technology stack and launch fintech products, including for retailers and platforms entering financial services. As an implementation partner across multiple fintech platforms, we aim to provide a fast, compliant route to launching financial products, and we design compliance in from day one. We build for regulated clients and are not a substitute for the FCA's guidance or for legal advice.
If you are deciding how to structure a wallet launch, Innovify's work on embedded finance and digital wallets is a good place to see how we approach it, and we are glad to talk through how the routes above would change what needs to be built.
FAQ
What are the routes to launching a digital wallet in the UK?
A UK retailer can generally launch a wallet by acting as an agent of an authorised firm, by partnering with an authorised e-money institution under its programme, or by obtaining its own authorisation. Each divides regulated responsibility differently. The exact status depends on the structure and must be confirmed with the FCA's published guidance and your legal advisers.
Does a retailer need an e-money licence to launch a wallet?
Not necessarily. A retailer may launch a wallet under an authorised firm's permissions, as an agent or through a partner programme, without holding its own authorisation. Whether you need your own depends on how the product is structured and what activities you carry out. Confirm your position with the FCA's guidance and legal advice before building.
What is the difference between an agent and a partner programme?
In an agent arrangement, the retailer acts on behalf of an authorised firm, which remains responsible for the regulated activity. In a partner programme, the retailer typically owns the brand and customer relationship and takes a programme manager or distributor role under an institution's licence. Labels vary, so confirm the regulatory status in writing.
Is a banking-as-a-service platform the same as an e-money licence?
No. A banking-as-a-service platform is a technology and services layer that packages financial infrastructure. It does not by itself determine whose regulatory permissions the wallet operates under. Ask which authorised firm's permissions apply, and check that firm on the FCA's Financial Services Register.
What obligations does a retailer keep when using a partner's licence?
A retailer typically keeps responsibility for customer onboarding to the partner's standards, fraud and transaction monitoring, complaints handling, data protection and integration with the partner's platform. It will also be subject to the partner's audit and reporting requirements. The specifics depend on the contract and structure, so confirm them before you build.
Where can I check the rules and who is authorised?
The FCA publishes its Handbook and guidance, and its Financial Services Register lists authorised and registered firms. The legislation behind e-money and payment services is the Electronic Money Regulations 2011 and the Payment Services Regulations 2017. Use these primary sources, together with your legal advisers, rather than relying on a summary.
Conclusion
Launching a retailer wallet on a banking-as-a-service stack starts with a regulatory decision, not a platform selection. Acting as an agent, partnering under an authorised institution's programme and seeking your own authorisation each divide responsibility differently, and each affects what you must build and run. Choose the route that matches how central the wallet is, how much control you need and how much regulatory responsibility you can carry, confirm your status in writing and check the primary sources before you commit.
