MIFARE Classic 1K RFID Keyfobs

No. NXP Classic EV1 1K operates at 13.56 MHz using ISO/IEC 14443 Type A, with the Classic command and authentication behavior. The installed reader must support the required chip and configured credential mode, and the controller and software must interpret the result correctly. A shared frequency does not establish DESFire application compatibility. Wiegand or OSDP describes reader-to-controller communication rather than the keyfob chip. Confirm the approved specification and validate enrollment and actual access with the system administrator.

No. The NXP Classic EV1 1K reference has 1,024 bytes of total EEPROM, arranged as 16 sectors with four 16-byte blocks each. Each sector includes a trailer for keys and access-control information, and sector 0 also contains a manufacturer-programmed, write-protected block. Application space depends on the approved memory map and access conditions. Agree the required data fields and usable blocks with the issuer; do not size an application from the 1K label alone or overwrite security settings as ordinary data.

The NXP Classic EV1 1K data sheet describes 4-byte NUID and 7-byte UID delivery variants. NUID means Non-Unique ID, so it must not be advertised as globally unique. Confirm the exact variant and identifier handling expected by the reader, controller and enrollment software. The manufacturer block is programmed and write protected during chip production; visible serial printing and system credential-number allocation are separate specifications. Reading an identifier is not the same as authenticating protected data, and changing identifier length can require system changes.

NXP states that Classic EV1 1K - 4K is not recommended for new designs and points to DESFire Light on that product page. Its Classic family guidance directs security-relevant applications to the DESFire and Plus families. Classic uses the legacy CRYPTO1 mechanism; a tougher housing or custom logo does not improve that cryptography. Have the system owner review the required security architecture and migration path. A different chip family requires its own reader, application, key-management and enrollment validation; it is not an automatic replacement for the installed credential.

Have the system owner define whether the application uses identifier enrollment or protected sector data, and assign personalization to an authorized issuer. Supply non-secret reader, chip, memory-map and data-format requirements for quotation. Keep master keys, sector keys, credential dumps and personal member records within the approved issuing process. Use newly issued test credentials, validate the intended controller decision and event log, and check expiry, revocation and replacement at the relevant sites. Agree the sample record and any allowed configuration changes before production.

Send the approved chip and identifier variant, reader and controller models, issuing-software requirements, authorized personalization scope and sample acceptance plan. Confirm the housing or mold, dimensions, keyring attachment, print or engraving, visible numbering and relevant handling or cleaning exposure. Request MOQ for the exact configuration and quantity per design, and separate sample, setup, unit price and freight charges. Confirm availability, production readiness, delivery destination and import responsibilities in the quote. No fixed housing dimension, read distance, ingress rating or delivery time applies to every keyfob construction.