On October 20, 2026, the UK Competition and Markets Authority (CMA) proposed rules that would give third-party developers access to iPhone near-field communication (NFC) through both Host Card Emulation (HCE) and the Secure Element (SE). The proposal is still under consultation, and Apple’s current access arrangements remain in place while the CMA considers responses. The CMA consultation notice sets the deadline at 11:59 p.m. on November 17, 2026.
What iPhone NFC access could cover
NFC is short-range wireless communication. The draft covers payment and non-payment transactions, including in-store and transit payments, account-to-account payments, digital identity, loyalty credentials, car and hotel keys, and corporate badges.
The proposal would let developers request access through HCE, the software-based route that uses device hardware outside the Secure Element, or through the Secure Element, an embedded security component. The existing SE access route would continue under the draft, which would also require Apple to make HCE available.
How access, fees and safeguards would work
The proposed rules cover more than the technical connection. They also set out how developers could apply, how fees would be handled, and what protections would apply to access decisions.
| Area | What the draft proposes | Practical effect |
| NFC routes | Apple would provide access through HCE and the Secure Element. Developers could request either route or both. | Developers could choose a route suited to their app’s use. |
| Access process | Published access terms and timelines, a complaint process, and protections for developers’ commercially sensitive information. | Developers would have a defined process for requests and complaints. |
| Fees | Apple could charge fees. The draft calls for fair, reasonable, transparent and non-discriminatory terms, with cost, value, flexibility and administrative simplicity among the considerations. | Access would not have to be free, and the proposal sets no fixed tariff. |
| Default contactless app | Users could choose an authorized third-party NFC app as the default. An API would let developers check default status, and Apple could not limit API calls or prompts to change the default. | Users could select another eligible app without Apple Pay being removed. |
| Supporting iOS functions | Apple would provide access to certain functions needed for features comparable to Express Mode and Power Reserve. | Third-party apps could build support for similar functions. |
| Access safeguards | Apple could refuse or interrupt access in specified cases involving legal or industry-standard noncompliance, including serious security, privacy or integrity risks. | Access would remain subject to the draft’s compliance and risk conditions. |
For users, the most visible proposed change is the ability to select an authorized third-party contactless app as the default. The draft does not remove Apple Pay or automatically switch a user to another app.
Apple raises privacy and security concerns
Apple says it opposes requiring an approach with lower privacy and security protections. The CMA’s consultation gives a provisional assessment that both HCE and SE can support secure payment use with appropriate safeguards, while noting that SE may offer advantages for some high-assurance, non-payment uses.
