The Maze: The UK's competition regulator wants Apple to give payment-app developers more ways to use the iPhone's contactless technology, on commercially workable terms. Its 20 October proposal targets the conditions for competing with Apple Pay. It does not launch a new payment service or cut anyone's fees today.
Source: Apple Developer. Documentation example of the existing European Economic Area contactless prompt, not a newly launched UK interface.
The Details:
UK access already exists, with conditions. Apple lets authorized developers build contactless transactions into their own iPhone apps through its existing platform. A payment provider needs the relevant financial permissions, Apple's authorization and an agreement covering commercial terms and applicable fees. UK users need an iPhone XS or later with compatible software, starting at iOS 18.1. They can choose an eligible app as their default contactless app. Holding the phone near a compatible payment terminal opens that app, with authentication if the phone is locked. The dispute concerns how viable competing services can become under those conditions.
The proposal changes both technology and terms. Contactless payments use a short-range wireless connection between the phone and terminal. Apple's current UK route uses a secure element, which stores payment information on the device. The Competition and Markets Authority, or CMA, proposes adding host-based card emulation, which stores payment information off the device. Apple already offers that alternative to eligible developers and users in the European Economic Area. The UK regulator also proposes principles for determining access prices and terms. It expects lower charges, while allowing Apple fair compensation. It is not proposing a fixed price or promising free access.
A proposed route is not an approved rollout. The consultation closes on 17 November 2026, with a final decision afterward. Apple objects that the proposed approach would weaken privacy and security protections. The CMA says its evidence does not show inherent security concerns with either technical standard. These are competing assessments; this announcement does not resolve the implementation's eventual security performance. Developers still have to meet financial-services rules and security requirements. No resulting UK wallet launch, customer uptake or merchant saving is established.
MarketMaze Take: Permission to connect is only the first part of payment competition. A developer also needs terms that support a business and a usable way for customers to pay. Apple's existing UK access makes this a test of whether an available interface can become a viable alternative to Apple Pay.
Country differences create a business constraint. Apple's separate UK and European Economic Area routes show why payment businesses must assess platform access market by market. A service built around one technical route cannot assume identical access elsewhere. The UK proposal could narrow that difference, but it changes no rules outside the UK and establishes no worldwide opening.
Lower access charges would not automatically lower a shop's bill. The regulator is targeting the terms developers face when using Apple's technology. That could improve a rival wallet's economics. Whether a provider launches, shoppers choose it and any benefit reaches merchants are further steps. Treat those as outcomes to establish after a decision, rather than savings already delivered.
Sources: CMA, Apple, Apple Developer, CMA consultation, PaymentsJournal
