NFC

NFC (Near Field Communication) is a short-range wireless connectivity technology that exchanges data between two devices placed within about 4 centimeters of each other, using magnetic induction at 13.56 MHz. In hardware connectivity, it is the interface behind contactless payments in phones, transit and access cards, and tap-to-pair accessories.

NFC grew out of RFID and contactless smart card standards such as ISO/IEC 14443 and FeliCa, and is specified by ISO/IEC 18092 and the NFC Forum. Its defining property is deliberate very short range, which makes an intentional tap the user’s act of consent and limits casual interception.

How NFC communicates through magnetic induction

NFC communicates by coupling two loop antennas through a shared magnetic field, much like the windings of a transformer. The initiating device drives its antenna with a 13.56 MHz carrier; a nearby target antenna picks up that field and can even draw its operating power from it, which is why passive cards and tags need no battery.

Data travels by modulating the field. The reader changes the amplitude of its carrier to send bits, and a passive target answers by load modulation, switching a load on its antenna so the reader detects tiny changes in its own field. Because field strength falls very steeply with distance in the near field, range is limited to a few centimeters by physics rather than by software.

The table summarizes the key physical and protocol parameters of NFC.

NFC operating modes and tag types

An NFC device can work in three operating modes, each suited to a different task. In reader/writer mode, a phone reads or programs a passive tag. In card emulation mode, the device behaves like a contactless smart card toward a payment or access terminal. In peer-to-peer mode, two active devices exchange data directly, a mode now rarely used by mainstream phones.

Passive tags are grouped into NFC Forum tag types that differ in memory, speed and security. Most messages stored on tags follow the NDEF (NFC Data Exchange Format), which wraps records such as URLs, text or Bluetooth pairing data in a common structure readable by any compliant phone.

NFC compared with Bluetooth and other wireless links

NFC is not a replacement for Bluetooth but a complement to it. Bluetooth offers meters of range and megabits of throughput for continuous streams; NFC offers centimeter range, instant setup and minimal power. Many accessories therefore use NFC only to start a Bluetooth pairing, a pattern called connection handover.

Security and the secure element

NFC payments are secure because of cryptography in the card or phone, not because of the short range alone. In a phone, payment credentials live in a secure element, a tamper-resistant chip, or are handled through host card emulation with cloud-issued tokens. Each transaction uses a one-time cryptogram and a device token instead of the real card number, so a captured exchange cannot be replayed.

The main remaining threats are relay attacks, in which an attacker forwards the radio exchange to a distant terminal, and unauthorized skimming of cards in pockets. Relay attacks are mitigated by distance-bounding timing checks and by requiring biometric or PIN confirmation on phones. Plain Type 2 tags have no meaningful protection, so their content can be read or copied by anyone nearby.

Integrating NFC into hardware and avoiding problems

Designing NFC into a device is mainly an antenna problem. The antenna loop must be tuned to 13.56 MHz with matching capacitors, and nearby metal shifts that tuning. Phones place the coil behind a non-metal section of the back cover, often using ferrite sheets to shield it from the battery.

• Metal surfaces under a tag detune it; use on-metal tags with a ferrite layer.
• Misaligned antennas cause failed reads; users must learn where the coil sits on the device.
• Thick cases with metal plates or magnets can block both payments and tag reading.
• Writable tags left unlocked can be overwritten with malicious links; lock them after programming.
• Assuming NFC means encryption is a mistake: protection depends entirely on the tag type and application.

In everyday language

NFC is the technology that makes a tap work. When you hold a phone or card very close to a reader, the two exchange a short message through an invisible magnetic field, much like two coils whispering to each other. The tiny card does not even need a battery, because the reader’s field powers it.

Its strength is that it only works when things almost touch. That makes it convenient and gives a clear moment of intent: nothing happens until you deliberately bring the devices together.

Seen in the real world

A city transit operator replaces paper tickets with a contactless system. Gate readers accept ISO/IEC 14443 cards, bank cards and phones in card emulation mode. Each gate must complete a transaction in about 300 milliseconds so that passengers can walk through without stopping, which NFC’s fast setup makes possible.

During the pilot, staff notice frequent failed taps from riders who keep cards in wallets alongside other contactless cards. The two cards answer at once and confuse the reader, a problem known as card clash. Signage advising riders to tap a single card, plus reader firmware that handles collisions more gracefully, cuts failed taps sharply. The outcome is faster boarding at peak hours and a clearer understanding that user behavior matters as much as the radio link.