Near Field Communication
Near-field communication is the short-range wireless standard — a few centimetres, a fraction of a second — through which a contactless card or phone exchanges payment data with a terminal, and through which a phone can act as a terminal itself. It is the physical layer under every tap; EMV is the logic above it. Who controls a phone's NFC chip controls who can build a wallet on it, which is why Apple's was opened in 2024.
- Also known as
- NFC, NFC payments, Proximity payments
- Used at
- contactless card and phone payments, transit ticketing, access cards, tap-to-pay on smartphones (the phone as terminal), and device pairing
- Binding
- the ISO/IEC 14443 and 18092 standards for the radio; EMVCo's contactless specifications for the payment exchange; platform rules — Apple's until 2024 restricted the iPhone's NFC payment function to Apple Pay; the DMA commitments and the 2024 iOS changes opened it to third-party wallets in the EU and later elsewhere
- Typical range and speed
- under 4 cm, a transaction exchange in 300–500 milliseconds; the card is powered by the terminal's field, the phone by its own battery in host-card-emulation mode
- Typical roles
- a card in "card emulation" answering a terminal; a phone emulating a card (a wallet); a phone reading a card (tap-to-pay acceptance, where the phone is the terminal)
- Parties
- the standards bodies, the chip and handset makers, the platform owners (Apple, Google), the wallet providers, the terminal vendors, and the regulators who decided the chip was infrastructure
How near-field communication works in practice
A terminal generates a radio field. A card placed in it draws power from the field, wakes its chip, and exchanges the EMV contactless data with the terminal — the card's identity, a one-time cryptogram, the amount — in under half a second; the terminal then sends the authorisation over the network as usual. A phone does the same with software: in host-card emulation the wallet app answers the terminal as a card would, with a token in place of the card number and the phone's biometric as the cardholder verification. Reversed, the phone's NFC reader can read a customer's card: tap-to-pay on a smartphone turns any phone into a terminal, with the acceptance software handling the EMV kernel and the security.
The strategic fact is control of the chip. Android phones exposed NFC to any app from 2013; Apple restricted the iPhone's NFC payment interface to Apple Pay, so every bank and fintech that wanted its card on an iPhone went through Apple and paid its fee. The EU's competition case and the DMA changed that in 2024: Apple committed to let third-party wallets use the NFC interface in the EEA, and extended access under conditions elsewhere. For fintechs it opened a product — their own tap-to-pay in their own app — and a negotiation with a platform that still sets the terms.
For payments M&A the NFC layer is inside the terminal fleets, the tap-to-pay software vendors, and the wallet platforms that provision cards to phones.
Example
A neobank in the EU pays Apple about €1.2m a year in per-transaction fees for its customers' Apple Pay usage and has no way to offer its own tap-to-pay on iPhones. After the 2024 NFC opening it builds tap-to-pay into its own app: a nine-month project, €2m, and a certification with the schemes. In its first year 9% of iPhone customers switch their default wallet to the neobank's app — the ones who use its budgeting features at the point of payment — and the Apple fee on those transactions ends. The saving is modest; the strategic gain is a product Apple used to own, and a customer relationship at the moment of payment.
Common mistakes
- Assuming NFC is the payment; it is the radio, and EMV is the payment. - Building a wallet for iPhones before 2024 and discovering the chip was closed. - Terminal fleets without NFC, replaced early. - Confusing tap-to-pay acceptance (the phone as terminal) with contactless payment (the phone as card). - Reading the DMA's opening as free; the platform's terms and certification remain.