NFC-A vs NFC-F

NFC-A vs NFC-F: ISO 14443 Type A vs Sony FeliCa — The East-West NFC Divide

NFC-A and NFC-F are both recognized NFC communication technologies operating at 13.56 MHz, but they have historically dominated different geographies and application ecosystems. NFC-A, based on ISO 14443 Type A, is the global standard behind NTAG consumer tags, MIFARE transit cards, and EMV contactless payments. NFC-F, based on Sony's FeliCa specification (JIS X 6319-4, ISO 18092), dominates Japanese transit (Suica, PASMO, Icoca), mobile payments (Osaifu-Keitai), and other East Asian markets. Both technologies are supported by modern NFC Forum devices — but they are rarely interchangeable in practice.

Overview

NFC-A (ISO 14443ISO 14443Standard for contactless smart cards at 13.56 MHz (Types A and B)View full → Type A) uses 100% ASK modulationASK modulationSignal amplitude variation encodingencodingData writing to NFC tags during manufacturing productionView full → data on 13.56 MHz carrierView full → with Modified Miller bit coding on the downlink. The base data rate is 106 kbps. All NFC ForumNFC ForumIndustry body developing NFC standards, specifications, and certifications since 2004View full → Type 2 (NTAG 213/215/216) and most NFC Forum Type 4 tags (MIFARE DESFire, NTAG 424 DNA) are NFC-A. MIFARE Classic, MIFARE Ultralight, and virtually all Western access and payment card ICs are Type A.

NFC-F (FeliCa) uses Manchester-encoded FSK (Frequency Shift Keying) modulation — specifically, a 2.12 MHz subcarrier for uplink and a 2.1 MHz subcarrier for the field. FeliCa supports data rates of 212 kbps and 424 kbps natively (versus 106 kbps base for NFC-A). The FeliCa chip contains a system code and service code structure — a hierarchical memory addressing model distinct from ISO 14443's sector/block or file system approach. FeliCa chips (RC-S962, RC-S965 series from Sony) are used in IC cards issued by transit operators across Japan.

Key Differences

Modulation: NFC-A uses 100% ASK/Modified Miller. NFC-F uses Manchester/FSK with 212 or 424 kbps — higher native data rate than NFC-A's 106 kbps base.
Data rate: NFC-F transmits at 212 or 424 kbps by default. NFC-A starts at 106 kbps (though 212/424/848 kbps modes exist in ISO 14443).
Memory model: NFC-A chips use block/sector addressing (MIFARE Classic, NTAG) or file-system APDUs (MIFARE DESFire, NTAG 424 DNA). FeliCa uses a service/system code hierarchy with area and service blocks.
Security: Modern NFC-A chips (MIFARE DESFire EV3, NTAG 424 DNA) use AES-128. FeliCa Standard uses a proprietary DES/3DES-based cryptographic system; FeliCa Plug adds AES-128. MIFARE Classic's CRYPTO1 is broken; FeliCa's DES-based crypto has known theoretical weaknesses but no public large-scale breach.
NDEF support: NFC-A chips (NTAG, Type 2 tags) ship NDEF-formatted. NFC-F as NFC Forum Type 3 tags require NDEF mapping via a defined wrapper — supported but less common in consumer deployments.
Geographic deployment: NFC-A: globally dominant. NFC-F: Japan, Taiwan, Hong Kong (Octopus card historically), South Korea (T-money transit uses a hybrid).
Smartphone support: Both are supported natively by modern NFC controllers. Android has supported NFC-F via the HostApduService and IsoDep APIs since early versions. iOS supports NFC-F reading/writing via Core NFC (iPhone 7+, iOS 11+), though writing to FeliCa cards from iOS requires entitlement approval from Apple.

Technical Comparison

Parameter	NFC-A (ISO 14443 Type A)	NFC-F (FeliCa, JIS X 6319-4)
Standard	ISO 14443 Type A	JIS X 6319-4 / ISO 18092 (NFC-F)
Operating frequency	13.56 MHz	13.56 MHz
Modulation (downlink)	100% ASK / Modified Miller	Manchester / FSK
Native data rates	106 / 212 / 424 / 848 kbps	212 / 424 kbps
Anti-collisionAnti-collisionProtocol for selecting individual tags from multiple in RF fieldView full →	Bit-oriented binary search	SENSF_REQ/RES slot-based
NFC Forum tag type	Type 1, 2, 4	Type 3
NDEF support	Native (Types 1, 2, 4)	Via Type 3 NDEF mapping
Memory model	Block/sector (MIFARE) / NDEF / Files (DESFire)	System code / service code / block
Security	AES-128, ECC, password (chip-dependent)	DES/3DES (Standard), AES (Plug)
Key chip examples	NTAG, MIFARE, ST25TA	Sony RC-S962, RC-S965, RC-S300
Primary geography	Global	Japan, East Asia
Transit deployments	London TfL, NYC MTA, Singapore EZ-Link	Suica, PASMO, Icoca, TOICA
Mobile payment	Apple Pay, Google Pay (worldwide NFC-A)	Osaifu-Keitai (NFC-F on Android, Japan)
iOS write support	Full (standard)	Restricted (entitlement required)

Use Cases

NFC-A Dominant Scenarios

Global consumer NFC tags: NTAG 213/215/216 and NTAG 424 DNA cover the entire consumer smart label, product authenticationauthenticationIdentity verification of NFC tags/readers via passwords or cryptographyView full →, and NFC business card market.
International transit cards: London Oyster (MIFARE DESFire), New York MTA (MIFARE DESFire EV3), Singapore EZ-Link, and hundreds of other systems use Type A.
EMV contactless payments: All global EMV contactless implementations are NFC-A (or NFC-B) — NFC-F is not used in the EMV payment ecosystem.
NFC Forum certificationNFC Forum certificationInteroperabilityInteroperabilityCross-manufacturer device/tag compatibility guaranteeView full → testing program for NFC products and devicesView full →: The majority of NFC Forum-certified tag products are Type A. Certification testing infrastructure is overwhelmingly Type A-oriented.
Building access and enterprise security: MIFARE DESFire EV3 and NTAG 424 DNA are Type A — the standard for enterprise building access globally.

NFC-F Dominant Scenarios

Japanese transit: Suica (JR East), PASMO (Tokyo Metro), Icoca (JR West), and all 10 interoperable Japanese IC transit systems run on FeliCa. ~80 million Suica cards in circulation as of 2024.
Japanese mobile payment (Osaifu-Keitai): Android handsets in Japan implement FeliCa Secure Element for mobile transit and payment, marketed as Osaifu-Keitai ("mobile wallet"). Available since 2004 on NTT Docomo devices.
Apple Pay Suica: Apple implemented FeliCa support in the iPhone 8 and later (Japanese models) specifically to enable Apple Pay Suica — a significant engineering investment reflecting FeliCa's market importance.
Electronic money (e-money): Edy (Rakuten Pay), nanaco (Seven-Eleven), and WAON (AEON) are Japanese e-money systems built on FeliCa chips.
Student ID and corporate access in Japan: Some Japanese universities and corporations use FeliCa-based credentials for building access and cafeteria payments.

When to Choose Each

Choose NFC-A when:

The deployment is outside Japan and East Asia
EMV contactless paymentcontactless paymentNFC tap-to-pay via phones, cards, or wearables (EMV)View full → is part of the system
NFC Forum certified NDEF tags (NTAG, MIFARE Ultralight) are required
AES-128 security (NTAG 424 DNA, MIFARE DESFire EV3) is specified
Maximum global smartphone read compatibility is required

Choose NFC-F when:

The deployment is in Japan or integrating with Japanese transit infrastructure
Osaifu-Keitai or Japanese e-money interoperability is required
You are developing for the Japanese market where FeliCa handsets are dominant
Integration with JR East Suica, Tokyo Metro PASMO, or other Japanese IC card networks

Conclusion

NFC-A and NFC-F represent the global vs Japanese NFC ecosystem divide. NFC-A dominates everywhere outside Japan and East Asia, backed by the MIFARE, NTAG, and EMV ecosystems. NFC-F owns Japan's transit and mobile payment infrastructure — a 20+ year lead embodied in 80 million+ Suica cards and the Osaifu-Keitai platform. Both are supported by modern NFC controllers in smartphones worldwide, meaning reading NFC-F tags is universally possible — but building NFC-F card applications requires FeliCa licensing from Sony and ecosystem integration unavailable outside Japan's infrastructure.