# MIFARE Ultralight C — HF Chip Encyclopedia

URL: https://proudtek.com/guides/mifare-ultralight-c-chip-encyclopedia/
Source URL: https://proudtek.com/guides/mifare-ultralight-c-chip-encyclopedia/
Generated: 2026-03-16T01:42:30.697Z
Kind: article
Publisher: Proud Tek Co., Limited
Author: Proud Tek Editorial Team (RFID & NFC Technical Content Team)
Published: 2026-04-19
Last Modified: 2026-06-10T18:00:00Z
Last Reviewed: 2026-06-10T18:00:00Z
Credentials: ISO 9001:2015, ISO 14001:2015, RoHS Compliant, CE Marking, REACH Compliant
Image: https://proudtek.com/landing-images/mifare-ultralight-c-chip-encyclopedia-hero.jpg
Image Alt: Fan of printed RFID cards including transit tickets, a clear card and a wooden card

## Description
MIFARE Ultralight C (NXP MF0ICU2) is the low-cost, paper-ticket-oriented HF 13.56 MHz chip that brought triple-DES authentication to single-use and...

## Summary
- MIFARE Ultralight C (NXP MF0ICU2) is the low-cost, paper-ticket-oriented HF 13.56 MHz chip that brought triple-DES authentication to single-use and...

## Buyer Guidance
- Best for: MIFARE Ultralight C — HF Chip Encyclopedia supports RFID and NFC evaluation, comparison, and sourcing decisions.
- Compare first: Compare MIFARE Ultralight C — HF Chip Encyclopedia against reader compatibility, chip family, material, and deployment environment.
- What to confirm: Confirm target application, compatibility requirements, customization needs, quantity, and sample expectations before quoting MIFARE Ultralight C — HF Chip Encyclopedia.

## FAQ
- Q: Is Ultralight C's 3DES still secure enough in 2026?
  A: For short-validity event tickets and single-use transit rides, yes. NIST SP 800-131A Rev. 2 deprecates 3DES for new US-government systems as of 2024 but permits legacy interoperability through 2030 (disallowed-after date 2030-12-31 for legacy data). Ultralight C tickets typically have a validity window measured in hours to days — a concert ticket is valid for one event, a transit single-ride is valid for ~90 minutes — so they age out faster than 3DES's deprecation window. The real threat model for a short-life ticket is opportunistic counterfeiting (someone duplicating a ticket they were shown), which 3DES prevents even with significant crypto budget because the attacker doesn't have the key. For long-validity credentials (multi-year membership cards, building access, government credentials with 3+ year life), migrate to NTAG424 DNA (AES-128 + SUN) or DESFire EV3 (AES-128 file system with per-file keys) before the 2030 NIST wall; any new deployment planned to still be in service in 2031 should specify AES, not 3DES.
- Q: When should I pick Ultralight C vs NTAG213?
  A: Pick Ultralight C when you need 3DES authentication (anti-cloning for event tickets. Stops the 'scan once, print fake tickets' attack), a one-way counter (single-use validation for turnstiles and transit gates), or compatibility with an installed base of Ultralight-aware transit/event readers (Deutsche Bahn, OV-chipkaart infrastructure, SkiData turnstiles). Pick NTAG213 when you need general-purpose NFC tagging (tap-to-URL, NDEF-based marketing campaigns, Apple Wallet-compatible URL pushes), faster reads (NTAG Fast Read 0x3A returns memory in bigger chunks, ~30% faster at long-range iPhone taps), or a unique per-chip Originality Signature (NTAG213 has it based on ECDSA over secp128r1; Ultralight C does not). Per-unit cost is similar at volume (NTAG213 ~€0.08-0.11 at 1M volume, Ultralight C ~€0.10-0.12), so the decision is driven by the feature mix not the price. Most new NFC business card, marketing sticker, and consumer-facing NDEF programs specify NTAG213 over Ultralight C.
- Q: Can the one-way counter on Ultralight C be reset or decremented?
  A: No. The counter is hardware-enforced monotonic at the silicon level; there is no command (authenticated or unauthenticated) to decrement or reset it. INCREMENT_COUNTER (0xA5) only increments; any other attempt returns NAK. This is by design. For single-use event tickets the counter is the anti-replay mechanism, and a resettable counter would destroy the security property. If the ticket is scanned erroneously (e.g., a turnstile bumps the counter before the door opens due to a network fault, trapping the customer outside a valid-seeming ticket) the fix is operational (issue a replacement ticket, refund, or manual override at the customer-service booth) rather than protocol-level (un-bump the counter). Plan your ticket issuance with enough counter headroom for expected misreads. A ticket with max-counter = 5 for a 4-ride pass tolerates one misread; for high-value events use max = 10 and enforce the actual entry count at the back-end event database.
- Q: How many key slots does Ultralight C support?
  A: One. Ultralight C stores a single 16-byte 3DES key in pages 44-47, which is used for the AUTHENTICATE (0x1A) handshake and for session-key derivation on protected page reads/writes. For multi-application credentials needing multiple access domains (e.g., transit + meal-card + library-access on one piece of plastic), use MIFARE Plus SE (multiple AES sector keys, 2KB memory), DESFire EV3 (full file-system with up to 28 applications per card, each with its own AES master key and file keys, 2-8 KB memory), or split the credential across multiple cards. Ultralight C's single-key model is appropriate for single-purpose tickets and single-application credentials where the simplicity of having one key to manage outweighs the lack of multi-domain separation.
- Q: Is there an 'Ultralight D' with AES?
  A: Not under that name, though NXP's naming conventions have evolved. NXP's AES-capable Ultralight-positioned chip is NTAG424 DNA (NT4H2421G0DU), which adds AES-128 CMAC, SUN (Secure Unique NFC) message format for tap-to-URL with per-tap-unique signed URLs, and CMAC-based tag authentication. NTAG424 DNA has 416 bytes of user memory (roughly 3× Ultralight C), AES-128 replacing 3DES, 10-year data retention, and 100,000 write endurance; the per-unit price at 1M volume is €0.15-0.25, roughly 50-100% above Ultralight C. If you were planning an 'Ultralight C successor with AES', NTAG424 DNA is the recommended chip for tap-to-URL and tap-to-authenticate use cases. For file-system multi-application use cases, migrate to DESFire EV3 instead.
- Q: What's the typical write endurance of Ultralight C in laundry or outdoor deployments?
  A: Write endurance is 10,000 cycles per page per the MF0ICU2 data sheet. Roughly 10× less than MIFARE Classic or NTAG21x (both 100k cycles) and 10× less than Ultralight EV1 (100k cycles). For deployments that write frequently (counter-bump per day for daily-use, per-use status updates for day-pass tickets, wash-cycle counter for laundry credentials written on every wash) this is a real constraint: 10k cycles at 1 write per day ≈ 27 years of use, at 1 write per hour during business hours ≈ 3 years. A card written once at issuance and only read thereafter (typical event-ticket pattern. The counter bumps once at entry, never again) will outlast its validity window by orders of magnitude. For frequently-written credentials, choose Ultralight EV1 (100k cycles, Originality Signature, 3 × 16-bit counters) or DESFire EV3 (100k cycles on the configuration blocks, effectively unlimited on the file-based counters which are implemented as authenticated operations rather than raw writes).
- Q: Does Ultralight C work with iPhone and Android for NDEF taps?
  A: Yes. iPhone (iOS 11+) and all recent Android phones (Android 4.x+ with NFC hardware) read Ultralight C as a standard NFC Forum Type 2 tag. NDEF-formatted user memory is accessible to stock wallet and browser apps via standard NFC tap-to-launch flows. The iPhone Shortcuts app, Apple Wallet App Clips, Google Wallet, and most third-party NFC reader apps work out of the box for reading URLs, vCards or other NDEF records written to Ultralight C. The 3DES authentication layer is NOT exposed to stock phone apps; applications requiring the 3DES handshake need a custom app using the native NFC APIs (Core NFC on iOS 13+ with the NFCNDEFReaderSession extended to NFCTagReaderSession for raw command exchange, android.nfc.tech.MifareUltralight on Android) to drive the AUTHENTICATE command directly. This is why consumer-facing Ultralight C deployments typically don't use the 3DES — they rely on UID-only reads in stock phone apps — while turnstile-reader deployments that ship dedicated hardware use the 3DES fully.

## Machine Routes
- JSON: https://proudtek.com/machine/guides/mifare-ultralight-c-chip-encyclopedia.json
- Text: https://proudtek.com/machine/guides/mifare-ultralight-c-chip-encyclopedia.txt