How a Brand Launches Its Own Digital Wallet Without Becoming a Bank
Short answer: a retailer or consumer brand launches its own wallet by partnering with an FCA-authorised electronic money institution or bank that holds the licence and safeguards customer funds, building on that partner's banking-as-a-service APIs, and owning the app, the checkout and the customer relationship itself. The brand acts as the partner's agent or distributor, so it does not need its own e-money licence to go to market.
Most brands that want a wallet are not trying to become banks. They want what a wallet does for the business: stored value that brings customers back, faster checkout, loyalty that feels like money, and first-party data on how people pay. The obstacle is that holding customer funds is a regulated activity, and the gap between "we want a wallet" and "we are allowed to run one" is where most projects stall. This guide sets out how the banking-as-a-service model closes that gap, what the brand still has to own, and the decisions that are expensive to get wrong in the first ninety days.
Why brands want wallets, and why most should not build the regulated core
A branded wallet changes the economics of a customer relationship. Once a customer holds a balance with you, the next purchase starts inside your app rather than on a marketplace or a card network's terms. Loyalty points can behave like money. Refunds can land back in the wallet instead of on a card. For marketplaces and platforms, a wallet can also become the rail for paying sellers, drivers or creators.
None of that requires the brand to issue electronic money itself. In the UK, only an authorised electronic money institution (EMI), a bank or another permitted issuer can issue e-money and safeguard the funds behind it. Applying for your own EMI authorisation means capital requirements, safeguarding arrangements, a compliance function and a long application process. For a brand whose core business is retail, travel, hospitality or software, that is usually the wrong use of time and capital. The banking-as-a-service route exists precisely so that a non-financial business can offer a financial product without carrying the licence.
The trade-off is control. Renting the regulated core means working inside a partner's compliance model, onboarding rules and product limits. The brands that get the most from a wallet are the ones that understand those limits early and design the customer experience around them, rather than discovering them at launch.
The three layers of a branded wallet
Every brand wallet built on banking-as-a-service has the same three layers, whoever the providers are.
1. The licensed partner
An authorised EMI or bank issues the e-money or provides the account, safeguards customer funds and carries the core regulatory obligations: anti-money laundering controls, safeguarding, complaints handling and conduct rules. This is the firm the FCA holds responsible for the regulated activity.
2. The platform and APIs
A banking-as-a-service platform exposes accounts, balances, cards, payments and payouts through APIs. Sometimes the platform and the licensed partner are the same firm; sometimes a technology provider sits in front of a separate licence holder. Either way, this layer decides what your product can do and how quickly you can change it.
3. The brand's product
The brand owns the app, the checkout, the loyalty logic, the customer journeys and the data use. This is where differentiation lives, and it is the only layer customers actually see. It is also where most engineering effort goes, because onboarding flows, top-ups, spend, refunds, reconciliation and support all have to work cleanly on top of the partner's rules.
Keeping these layers distinct in your architecture matters more than it sounds. A wallet whose business logic is tangled into one provider's API is hard to extend and harder to move. A wallet with a clean internal ledger and a thin integration layer can add a second provider, a card or a new market without a rebuild.
Agent, distributor or your own licence: how the regulated relationship works
The FCA's perimeter guidance on agents and distributors draws the line that shapes most brand wallets. An authorised payment or e-money institution can appoint agents to provide payment services on its behalf. The principal registers each agent with the FCA and remains responsible for the agent's compliance; the agent does not need its own authorisation. A distributor of e-money markets, loads or redeems e-money for the institution, but only the institution itself can issue e-money, and a distributor cannot provide payment services.
In practice this gives a brand three routes:
- Distributor: the lightest-touch model, suited to a stored-value or loyalty wallet where the brand sells and loads value but the EMI provides the payment services.
- Agent: the brand provides payment services on the principal's behalf, registered by the principal. More scope, more oversight from the principal, and an onboarding process that takes time.
- Own authorisation: the brand becomes an EMI or payment institution itself. Full control, full regulatory burden, and only worth it when financial services are becoming a core line of business.
Because the principal carries the regulatory responsibility, it will want evidence of how you onboard customers, handle complaints, treat vulnerable customers and present the product. The FCA's Consumer Duty applies to how the product is distributed, and principals are expected to be able to adjust how their agents and distributors present services. Brands that arrive with that evidence move through partner onboarding faster than brands that treat it as paperwork for later.
This is general guidance, not legal advice. Innovify builds for regulated clients but is not itself an FCA-authorised firm, so take regulatory advice on the specific arrangement you choose.
What the brand still has to own
Renting the licence does not mean renting the responsibility for a good product. Four areas stay firmly with the brand, and they are where wallet projects are won or lost.
Onboarding and identity
Your partner sets the know-your-customer rules, but you design the journey. A wallet that asks for identity checks at the wrong moment, or fails customers without a clear next step, will see sign-ups drop away. Decide early which features need full verification and which can work with lighter checks, within the partner's policy.
Stored value and loyalty
The moment loyalty points can be converted into spendable balance, the line between a marketing scheme and e-money starts to matter. Map exactly which value is regulated e-money held by the partner and which is a promotional balance the brand controls, and make sure the customer can tell the difference.
Reconciliation and support
Every top-up, spend, refund and failed payment has to reconcile between your ledger and the partner's records. When it does not, customers see the wrong balance and support teams cannot explain why. Build the internal ledger and the reconciliation process as first-class parts of the product, not as afterthoughts.
Data and audit trail
Structured logs, clear data ownership and role-based access from the first sprint make partner due diligence, investor questions and incident reviews far easier. They are also what lets you prove to a principal that you are operating the product the way you said you would.
Scoping a first release that a partner will approve
The fastest wallets to market start narrow. Choose one customer segment and one money flow, typically onboarding, top-up and spend inside your own checkout, and get that working end to end before adding peer-to-peer transfers, cards or cross-border features. A narrow first release is easier for a partner to approve, easier to test with real customers and easier to support.
Three decisions deserve time in discovery because they are expensive to reverse:
- Partner fit over price: choose the licensed partner whose product scope, compliance tooling and onboarding model match what you want to launch in year one and year two, not the quickest integration this quarter.
- Ledger ownership: decide whether your platform keeps its own ledger of customer balances alongside the partner's records. Most brands that plan to scale do.
- A second partner: design the integration layer so that adding or switching provider is a project, not a rebuild. Provider lock-in is one of the most common regrets in embedded finance.
Cost and timeline depend on those choices, the number of money flows, the markets you serve and how much of the customer journey is bespoke. Our guide to embedded finance and digital wallets sets out the building blocks that drive that scope.
What is changing in the UK wallet market
The UK wallet opportunity may be about to widen. On 20 October 2026 the Competition and Markets Authority proposed opening iPhone contactless (NFC) access to rivals of Apple Pay, through both the secure element and host card emulation. It is a proposal in consultation, not a final decision. If it goes ahead, a UK brand's own wallet could, for the first time on that platform, offer tap-to-pay in store rather than only in-app and online payments.
That is a reason to design wallet architecture with in-store payments in mind, not a reason to wait. The brands best placed to use new device access, if it arrives, will be the ones that already have customers, balances and a working relationship with a licensed partner.
The regulatory direction is also clear on conduct. The FCA's approach to new technology has been to apply existing frameworks, including the Consumer Duty, rather than create special regimes. For a brand wallet, that means the standard is how fairly and clearly the product treats customers, whichever technology sits underneath.
Where Innovify fits
Innovify is a London-based fintech specialist that helps brands, retailers and platforms adopt fintech without becoming a bank. Non-financial businesses adopting fintech need specialists rather than generalists: clients do not pay us to learn the domain, because we arrive knowing payments, e-money and compliance, and we design compliance in from day one.
We work as an implementation partner across multiple fintech platforms, helping brands choose the right licensed partner and integration model, then building the wallet, ledger, onboarding and checkout on top. The payments foundations are proven: Innovify built Zilch's regulated BNPL wallet and checkout in four months, to PCI DSS and FCA requirements, and that product became the foundation Zilch took to market. For founders, Kwanji launched its FX and payments MVP with Innovify and secured £300K seed funding shortly after launch.
If you are scoping a branded wallet, start with our Embedded Finance & Digital Wallets practice. If you first want to test whether a wallet idea is worth funding, Innovify AI Labs can prototype it and test it with real users.
FAQ
Can a retailer launch a digital wallet without an e-money licence?
Yes. Most UK retailers launch a wallet by partnering with an FCA-authorised electronic money institution or bank that issues the e-money and safeguards funds. The retailer acts as the partner's agent or distributor and owns the app and customer experience.
What is the difference between an agent and a distributor for a wallet?
An agent provides payment services on behalf of an authorised firm, which registers the agent with the FCA and stays responsible for its compliance. A distributor markets, loads or redeems e-money for an e-money institution but cannot provide payment services, and only the institution can issue the e-money.
Who is responsible for compliance in a banking-as-a-service wallet?
The authorised partner carries the core regulatory responsibility for the regulated activity, including safeguarding and anti-money laundering controls. The brand is still responsible for how it designs and presents the product, and the partner will expect evidence of fair customer treatment under the Consumer Duty.
How should a brand scope the first version of its wallet?
Start with one customer segment and one money flow, usually onboarding, top-up and spend inside your own checkout. Add transfers, cards and new markets once that core flow works, reconciles and has been tested with real customers.
Does the CMA's iPhone NFC proposal change what a brand wallet can do?
Not yet. The Competition and Markets Authority proposed on 20 October 2026 to open iPhone contactless access to Apple Pay rivals, but it is a proposal in consultation. If adopted, UK brand wallets could offer tap-to-pay in store on iPhones, so it is worth designing for in-store payments now.
How do we avoid being locked into one banking-as-a-service provider?
Keep your own internal ledger of customer balances and put a thin integration layer between your product and the provider's APIs. That way adding a second provider or switching provider is an integration project rather than a rebuild of the wallet.
Conclusion
A branded wallet is within reach for any brand that treats it as a product line rather than a plug-in. The licensed partner carries the regulated core; the brand owns the experience, the ledger, the data and the evidence that it is running the product well. Get the partner, the ledger and the first money flow right, and the wallet can grow into cards, transfers and in-store payments as the market opens up.
