Card Emulation Mode
An NFC operating mode where the device behaves as a contactless smart card. Used for mobile payments (Apple Pay, Google Pay), transit passes, and access badges. Can be implemented via secure element (SE) or Host Card Emulation (HCE).
What Is Card Emulation Mode?
Card Emulation modeCard Emulation modeDevice acts as contactless smart card for payments and accessView full → lets an NFC-enabled smartphone or wearable behave as a contactless smart card, responding to an external NFC reader's RF field exactly as a physical card would. This mode powers mobile payments (Apple Pay, Google Pay), digital transit passes, virtual hotel keys, and electronic identity credentials.
How It Works
- External reader generates the field: A POS terminal or transit gate energizes its antenna.
- Phone responds as card: The NFC controller detects the field and responds via load modulation.
- Protocol exchange: Reader and phone communicate using ISO 14443 APDUs (Application Protocol Data Units).
- Transaction completes: Within 200-500 ms.
Implementation Approaches
Secure Element (SE) Based
A Secure Element stores credentials in tamper-resistant hardware. The NFC controllerNFC controllerDedicated IC managing NFC protocol stack in readers/smartphonesView full → routes traffic directly to the SE, bypassing the OS. Provides hardware-level security, works offline, and has lowest latency. Used by Apple Pay.
Host Card Emulation (HCE)
HCE routes traffic to the phone's application processor, where software handles APDU exchange. No hardware SE dependency. Introduced in Android 4.4. Used by Google Pay and custom access solutions.
AID Routing
When multiple card applications exist (payment, transit, access), AID-based routing determines which handles incoming commands. Each application registers its Application Identifiers. When the reader sends SELECT with a specific AID, traffic routes to the matching application.
Security
- Tokenization: One-time tokens replace actual card numbers.
- Biometric gating: Transactions require fingerprint, face, or PIN verification.
- Dynamic cryptograms: Unique signatures per transaction prevent replay.
- SE isolation: On SE-based implementations, credentials are hardware-isolated from the OS.
Use Cases
- Contactless payments: The primary use case — tap-to-pay at millions of EMV terminals worldwide via Apple Pay, Google Pay, and Samsung Pay.
- Digital transit passes: Suica, Oyster, ORCA, and other transit cards stored digitally on smartphones and smartwatches.
- Access control: Virtual employee badges, hotel room keys, and car keys replacing physical cards.
- Loyalty and coupons: Digital loyalty cards presented directly at POS terminals without physical cards.
- Student and employee IDs: Campus cards for dining hall access, library services, and secure printing.
On iOS, card emulation is managed exclusively through Apple Wallet and the embedded secure element — third-party apps cannot perform arbitrary card emulation. On Android, developers can implement custom card emulation using HostApduService for HCE-based applications.
Related Terms
Related Guides
Pertanyaan yang Sering Diajukan
The NFC glossary is a comprehensive reference of technical terms, acronyms, and concepts used in Near Field Communication technology. It is designed for developers, product managers, and engineers who work with NFC and need clear definitions of terms like NDEF, APDU, anti-collision, and ISO 14443.
Each glossary term is cross-referenced with related NFC chips, standards, and other terms. For example, the term 'AES-128' links to chips that support AES encryption (NTAG 424 DNA, DESFire EV2/EV3), and the term 'ISO 14443' links to all chips compliant with that standard.
Yes. NFCFYI provides glossary definitions in 15 languages including English, Korean, Japanese, Chinese, Spanish, Portuguese, Hindi, Arabic, French, Russian, German, Turkish, Vietnamese, Indonesian, and Thai. Use the language selector in the header to switch languages.