NFC-A vs NFC-B

NFC-A vs NFC-B: ISO 14443 Type A and Type B Modulation Differences

NFC-A and NFC-B are the two communication technology variants defined in ISO 14443 for proximity contactless smart cards and NFC tags. Both operate at 13.56 MHz, both support the same data rates (106, 212, 424, and 848 kbps), and both share the same ISO 14443ISO 14443Standard for contactless smart cards at 13.56 MHz (Types A and B)View full →-4 block transmission protocol (T=CL) at the transport layer. Their differences lie in the physical layer: modulation depth, bit coding, and the initialization and anti-collisionanti-collisionProtocol for selecting individual tags from multiple in RF fieldView full → procedures. Understanding these differences explains why MIFARE and NTAG tags are Type A while SIM cards, e-passports in some countries, and certain smart card ICs are Type B.

Overview

NFC-A (ISO 14443 Type A) uses 100% Amplitude Shift Keying (ASK) modulation on the downlink (reader to tag) with Modified Miller bit coding. The high modulation depth briefly drops the RF field to zero — this strong modulation makes Type A highly robust in the presence of interference and metallic surfaces. Tag-to-reader communication (uplink) uses load modulationload modulationPassive tagPassive tagBatteryless tag powered by reader's electromagnetic fieldView full → response technique varying load impedanceView full → with Manchester codingManchester codingSelf-clocking bit encodingencodingData writing to NFC tags during manufacturing productionView full → using signal transitionsView full →. Anti-collision follows a bit-oriented binary search tree protocol using the 4-7 byte unique identifier (UID/NFCID).

NFC-B (ISO 14443 Type B) uses 10% ASK modulationASK modulationSignal amplitude variation encoding data on 13.56 MHz carrierView full → on the downlink with NRZ-L bit coding. The reduced modulation depth keeps the RF field continuously active at ~90% amplitude during data transmission. Uplink uses BPSK (Binary Phase Shift Keying) load modulation with NRZ-L coding. Anti-collision is byte-oriented (REQB/ATTRIB/HALTB commands), using a slot-marker approach with 1–16 time slots.

Key Differences

• Modulation depth: Type A uses 100% ASK (field briefly collapses). Type B uses 10% ASK (field remains at ~90% during transmission). The sustained field in Type B can benefit passive tag power stability during complex transactions.
• Bit coding (downlink): Type A uses Modified Miller encoding. Type B uses NRZ-L. Modified Miller provides better clock recovery at the tag because pauses are distinct; NRZ-L is simpler to decode but requires continuous carrier.
• Uplink coding: Type A uses Manchester subcarrier coding. Type B uses BPSK. BPSK (Type B) provides slightly better noise immunity in some environments.
• Anti-collision protocol: Type A anti-collision is bit-oriented, operating on the UID one bit at a time — well-suited for distinguishing multiple tags with different UIDs via binary tree search. Type B uses slot-based (ALOHA-style) anti-collision — simpler for the tag but potentially less deterministic with many tags.
• Chip ecosystem: Type A dominates the market. NTAG (213/215/216/424 DNA), MIFARE (Classic, DESFire, Ultralight, Plus), ICODE, and most NFC ForumNFC ForumIndustry body developing NFC standards, specifications, and certifications since 2004View full → tags are Type A. Type B is used by NXP SmartMX series (some configurations), STMicroelectronics ST19 / ST33 secure elements, Infineon SLE 77/97, and national government identity programs that standardized on Type B (France, some Asian national eID programs, and some e-passport variants).

Technical Comparison

Use Cases

NFC-A Dominant Scenarios

• NFC consumer tags and smart labels: NTAG 213/215/216 and NTAG 424 DNA are all Type A. The vast majority of NFC tags on the market are Type A due to MIFARE and NTAG market dominance.
• Transit fare media: MIFARE Classic, MIFARE DESFire, MIFARE Plus — all Type A — are used by the majority of global transit systems.
• Building access control: HID iCLASS (DESFire compatible), MIFARE DESFire EV3, and NTAG 424 DNA-based access credentials are all Type A.
• Contactless payments (Visa payWave): Many Visa contactless implementations prefer Type A. Mastercard PayPass supports both.
• NFC Forum Type 2 and Type 4 tags: By specification, these are Type A.

NFC-B Dominant Scenarios

• Government eID programs: France's national identity card (CNI), certain Asian national eID programs, and ICAO 9303-compliant e-passports in several countries use Type B Secure Element chips (STMicroelectronics, Infineon).
• Health insurance cards: The French Vitale card and several European health cards use Type B chips.
• SIM-based NFC applications: ETSI standards for SIM-embedded NFC (UICC NFC) in some implementations use Type B secure elements.
• Contactless banking cards (Mastercard PayPass Type B): Some banking markets deployed Mastercard PayPass on Type B chips — fully interoperable with payWave readers.
• EMV multi-interface cards (Type B): Chip-and-PIN cards from certain issuers (especially European) use Type B dual-interface chips.

When to Choose Each

From a product designer's perspective, the choice is typically determined by the chip family selected:

You will use NFC-A when:

• You select NTAG (213, 215, 216, 424 DNA) — all Type A
• You select MIFARE (Classic, DESFire, Ultralight, Plus) — all Type A
• You want the largest ecosystem of readers, encoders, and management software
• You are building NFC Forum Type 2 or Type 4 tags

You will use NFC-B when:

• Your system integrates a Type B secure element (ST33, Infineon SLE 77/97)
• You are deploying in a government identity program that has standardized on Type B
• You are integrating with banking infrastructure that uses Type B EMV cards
• Your NFC readerNFC readerActive device generating RF field to initiate communication with tagsView full → must interoperate with e-passports or national eID that use Type B

In practice, all modern NFC readers and NFC-enabled devices support both Type A and Type B — a reader that supports only one technology would be non-compliant with the NFC Forum and EMV specifications.

Conclusion

NFC-A and NFC-B are not competing technologies — they are parallel physical-layer specifications within the same ISO 14443 standard, designed to accommodate different IC manufacturing traditions and national standardization preferences. NFC-A holds ~90%+ of the consumer tag, transit card, and access control market through the MIFARE and NTAG ecosystems. NFC-B holds a significant position in government eID, e-passport, and European health card deployments. Every NFC-compliant reader handles both — making the choice of Type A vs Type B a chip selection decision rather than a system architecture decision.