Open banking and mobile money in London and Nairobi

Open banking and mobile money solve different access problems. In London, open banking usually adds services and payment choices for people or businesses that already have bank accounts. In Nairobi, mobile money combines a digital wallet or account with a widespread cash-in and cash-out network, allowing the phone and local agent to become an access point. Product leaders should not use adoption in one system as evidence that the other design will work.

The commercial lesson is to identify the missing layer. If customers already hold usable bank accounts, permissioned APIs can improve aggregation, payments and financial management. If converting physical cash into digital value is still essential, software alone is incomplete and the distribution network becomes part of the product.

London open banking builds on existing bank relationships

UK open banking allows regulated providers, with customer permission, to access account information or initiate payments through standardised bank interfaces. It can reduce manual data entry, support account aggregation and create alternatives to card payments. The user still needs an eligible account and a bank that participates in the framework.

Open Banking Limited's June 2026 Payments Fraud Monitor said UK open banking supported more than 19 million active user connections and over 40 million payments each month. A user connection is not necessarily a unique person. These are national figures covering consumers and small businesses, so they cannot be presented as London adoption and do not establish that every user receives the same outcome.

For a London product team, the API is only the middle of the journey. Customers must understand the consent request, select the correct account, authenticate with their bank and recover from errors. Providers also need a plan for consent expiry, unavailable banks, ambiguous payment status and customers with several accounts.

Nairobi mobile money joins digital service to physical distribution

Kenya's mobile-money system developed around the ability to send and receive value through a mobile account and convert between cash and digital funds through agents. The agent network matters because it extends service beyond bank branches and provides an operational bridge for cash-based households and merchants.

The Central Bank of Kenya publishes monthly national mobile-payment statistics covering registered accounts, active agents and agent cash-in and cash-out activity. Those figures demonstrate the scale of the national network. They are not a count of unique people and do not isolate Nairobi.

Kenya's National Payments Strategy 2022 to 2025 treated mobile money as part of a wider system that includes bank transfers, cards and other channels. The concluded strategy prioritised resilience, security, interoperability and customer-focused innovation. In September 2026, the Central Bank of Kenya published a draft National Payment System Policy and National Payment System Bill, 2026. Those documents were drafts rather than final rules on this article's research date. This policy progression matters for founders who might otherwise treat agent reach as a substitute for system governance.

Access is not the same as useful, affordable use

Opening a technical route does not guarantee that a person can or should use it. Open banking excludes people without a compatible account or a reliable way to authenticate. Mobile money can be constrained by handset access, identification, agent liquidity, fees, fraud, network availability or the distance to a trustworthy agent.

The 2024 Kenya FinAccess Household Survey found that formal financial access had increased nationally and that digital technology was an important driver. It also identified continuing exclusion, with lack of a mobile phone and identification among reported barriers. Nairobi was among the more included counties, but a county ranking does not describe every community or establish product quality.

Product teams should therefore measure completed tasks rather than account presence alone. Relevant outcomes include whether a customer can receive income, pay a bill, recover a mistaken transfer, understand a fee and access support. The system may be widely available while particular groups still face poor service.

The two models create different operating burdens

An API-led provider depends on banks, technical standards, consent and the relevant payment rails. Its operational work includes bank coverage, authentication journeys, interface changes, error handling and regulatory permissions. It may reach customers digitally without a physical network, but it inherits dependencies on existing accounts and banks.

An agent-led provider manages a human and physical layer. Agent onboarding, training, cash or electronic liquidity, commissions, security and monitoring affect the customer experience. A nearby agent who cannot complete a withdrawal is not effective access. A successful network needs incentives and controls that work at transaction level.

Both models face fraud and trust problems. A convincing impersonator can exploit an API consent journey, while a mobile-money user can be targeted through social engineering or an agent interaction. Warnings must be understandable at the moment of risk, and support must have the authority and information to act quickly.

Product leaders should start with the customer's constraint

A London fintech looking at Nairobi should ask whether its product assumes a bank account, continuous data, a particular identity document or digital-only support. A Nairobi company considering the UK should ask whether an agent function still adds value where banking apps and cards are already common. In both cases, the answer should come from observed user work, not a city narrative.

Hybrid approaches are possible. Open-banking data can support affordability or cash-flow tools, while mobile-money infrastructure can connect to banks and merchants. However, combining channels increases reconciliation and responsibility. The customer needs to know which company holds value, who executes a payment and where a complaint goes.

The investment decision should include distribution cost, failed-transaction support, fraud loss, compliance and partner dependence. A digital interface with poor completion or expensive exceptions is not necessarily more scalable than a managed physical network.

Limitations and geographic discipline

The strongest public evidence in this comparison is national. UK open-banking data cannot be narrowed to Greater London, and Kenyan mobile-money and FinAccess figures cannot be presented as Nairobi figures except where the source explicitly provides county data. London is a metropolitan area, while Nairobi county and city definitions require care.

The systems also serve different starting populations and use cases, so direct adoption ratios would mislead. Before publication, the article needs matched interviews with users and small businesses, city-level evidence where available, and common measures of cost, completion, fraud, complaints and repeat use. The conclusion is about routes to access, not which city is more financially included.