ST25TA64K
ST25TA64K
ST25TA64K — 64 Kbit / 8 KB
- Memory: 8 KB (64 Kbit) EEPROM
- Standard: ISO/IEC 14443 Type A, NFC Forum Type 4 Tag
- UID: 7-byte
- Security: 128-bit passwords (separate read/write access)
ST25TA64K — 64 Kbit / 8 KB
- Access control credentials for office, hotel, gym, and fleet systems where UID-based or password-protected authentication is sufficient
- Smart posters, NDEF-based marketing, and product information delivery
- Loyalty and membership programmes with issuer-controlled read/write access
- Digital identity tags linked to off-chip records (patient ID, staff badging)
- Asset tagging with controlled rewritable storage
ST25TA64K — 64 Kbit / 8 KB
- ST25PC-NFC software for Windows (desktop configuration, encoding, memory management)
- ST25 NFC Tap app (iOS and Android) for lightweight encoding and NDEF writing via smartphone
- NDEF file can be permanently locked after encoding, prevents unauthorised rewriting
- Separate read and write passwords allow issuer-controlled access
- Highest memory capacity of the three ST chip types available in NFCKEY
ST25TN01K
ST25TN01K
ST25TN01K — 1.6 Kbit / 208 B
- Memory: 1.6 Kbit EEPROM (208 bytes user memory)
- Standard: ISO/IEC 14443 Type A, NFC Forum Type 2 Tag
- UID: 7-byte
- Security: TruST25™ digital signature, permanent write locks at block level, configurable kill mode
ST25TN01K — 1.6 Kbit / 208 B
- Brand protection and anti-counterfeiting using TruST25™ digital signature
- Consumer engagement and product information via NDEF URL on tap
- Smart labelling, asset tagging, and inventory identification
- Loyalty interactions where each tap returns dynamic content
ST25TN01K — 1.6 Kbit / 208 B
- ST25PC-NFC software (Windows) for desktop configuration, encoding, and tag management
- ST25 NFC Tap app (iOS and Android) for NDEF writing and tag programming via smartphone
- Augmented NDEF (ANDEF) configuration enables the tag to respond with dynamic content without rewriting EEPROM
- TruST25™ verification requires reader-side cryptographic validation (ECC) using ST's published public key for the chip family
- TruST25™ digital signature verifies chip authenticity and helps prevent counterfeiting
- Kill mode enables permanent deactivation, relevant for single-use or privacy-sensitive deployments
- Augmented NDEF (ANDEF) allows the tag to return dynamic content per tap without modifying stored data
- Unique Tap Code (UTC) generates a changing 3-digit value on each read, useful for engagement verification
ST25TV16KC
ST25TV16KC
ST25TV16KC — 16 Kbit / 2 KB
- Memory: 16 Kbit EEPROM (2 KB)
- Standard: ISO/IEC 15693, NFC Forum Type 5 Tag
- UID: 8-byte (64-bit, ISO/IEC 15693)
- Security: Three 64-bit passwords, up to four independently configurable memory areas with read/write protection, TruST25™ digital signature
ST25TV16KC — 16 Kbit / 2 KB
- Industrial asset management and item-level tagging
- Pharmaceutical labelling and supply chain tracking
- Library, document, and inventory management on existing ISO 15693 infrastructure
- Logistics and returnable container tracking
- Brand protection and anti-counterfeiting using TruST25™ digital signature
ST25TV16KC — 16 Kbit / 2 KB
- ST25PC-NFC software (Windows) for desktop configuration, encoding, and memory area setup
- ST25 NFC Tap app (iOS and Android) for NDEF writing and tag programming via smartphone
- Compatible with existing ISO 15693 / NFC Type 5 reader infrastructure (industrial, library, and logistics systems)
- Memory partitioning into up to four areas is configured at encoding time, each with independent read/write password protection
- Uses an 8-byte UID per the ISO 15693 standard, distinct from the 7-byte UID of the two ISO 14443-A chips in the NFCKEY portfolio
- Compatible with existing ISO 15693 / NFC Type 5 reader infrastructure widely deployed in industrial, library, and logistics environments
- Up to four independent memory areas, each with separate read/write protection
- TruST25™ digital signature embedded for product authentication and anti-counterfeiting
- Configurable kill mode for permanent deactivation in privacy-sensitive or single-use deployments