Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
ISO/IEC 14443-3:2018 (also adopted as CAN/CSA-ISO/IEC 14443-3:18 and widely referred to as IEC 14443-3:2018) is the third part of the ISO/IEC 14443 series, which defines the physical and protocol characteristics of proximity cards (PICCs) and proximity coupling devices (PCDs). This standard specifies the initialization, anticollision, and selection protocols that enable a PCD to communicate with one or more PICCs in a contactless environment. It is fundamental to contactless smart card systems, NFC applications, and secure identification solutions.
The standard covers the data link layer of the contactless interface, specifically:
It applies to Proximity Integrated Circuit Cards (PICCs) operating at 13.56 MHz and the corresponding PCDs. The standard ensures interoperability between devices from different manufacturers, independent of higher‑layer applications.
All communication is based on frames that include a start bit, data bits (typically 8 bits per byte), an optional parity bit per byte, and an end bit. The standard defines two fundamental frame types:
| Command | Code (Type A) | Code (Type B) | Description |
|---|---|---|---|
| REQA | 0x26 | – | Request for Type A card presence |
| WUPA | 0x52 | – | Wake-up of Type A card |
| ANTICOLLISION | 0x93 / 0x95 / 0x97 | 0x1D | Collision resolution cascade |
| SELECT | 0x93 / 0x95 / 0x97 (with SEL code) | 0x0D | Card selection by full UID |
| HLTA | 0x50 | 0x10 (HALT) | Halt command to deselect card |
The standard defines several time intervals that must be respected to maintain reliable communication:
For Type A, a binary search tree anticollision method is used, based on the unique identifier (UID) length of 4, 7, or 10 bytes. The PCD sends cascaded anticollision loops, and each PICC responds with its UID bits. Collisions are detected at the bit level, and the PCD isolates one card by selecting a unique UID. Type B uses a slotted ALOHA approach, where cards pick a random slot and transmit their UID if no collision occurs. The standard specifies both mechanisms in detail to ensure deterministic behavior.
When implementing a PCD (reader) or PICC (card) compliant with IEC 14443-3:2018, the following aspects deserve special attention:
A PCD must support at least one interface type. Dual‑interface readers often implement both Type A and Type B sequentially. The initialization procedure for Type A begins with REQA at a fixed bit rate (106 kbps), while Type B starts with a request using a different framing and code. The standard does not require simultaneous support, but most commercial readers offer both.
Robust collision detection requires precise bit sampling. For Type A, the PCD must be able to detect the difference between an explicit bit (0 or 1) and a collision (both 0 and 1 received). This is usually handled by the analog front‑end and decoder logic. For Type B, the PCD must detect slot start times and handle multiple responses. Special care must be taken to avoid false collisions due to noise or weak coupling.
During the anticollision phase, the PCD may need to adjust the RF field strength to guarantee that all PICCs are powered correctly. The standard recommends that the field remain active throughout the entire initialization sequence, and any momentary interruptions (e.g., due to load modulation) must be within specified recovery times.
To claim compliance with IEC 14443-3:2018, products must undergo conformance testing that covers:
Conformance is typically verified using a dedicated test platform (e.g., a reference PCD) that simulates all required protocol sequences. The standard references ISO/IEC 10373-6 for test methods for proximity cards. Additionally, the GlobalPlatform and NFC Forum test suites include IEC 14443-3 conformance sections.
Products that pass accredited testing laboratories can be certified under the IEC System of Conformity Assessment Schemes (IECEE). For the Canadian adoption (CAN/CSA-ISO/IEC 14443-3:18), certification may be required for usage in regulated identification systems.
Technical reference material prepared 2026. This article is for informational purposes and does not replace the official standard text.