Introduction
Tap an RFID card at a door reader, and the system may grant access or display a name or room number. Are those details on the card? In some systems, yes. In others, the card carries an identifier that points to a database record. Cards designed for other applications may hold additional data. What a particular card contains depends on its chip, encoding, and the system using it.
What Types of Data Can an RFID Card Store?
Card contents vary by chip and application. An RFID card may contain an identifier, application data, or information used to control access to its memory. Some cards contain more than one of these types of data.
Card identifiers
An identifier is a number or code that distinguishes one card from another. Depending on the chip, it may be assigned during manufacturing or written when the card is prepared for use. A system can use that identifier to find a related database record. The identifier itself may contain no name or access permissions.
Application data
Some RFID cards have memory for information used by a particular application. A system might write an expiry date, for example, or other data needed to use the card. Whether such information resides on the card or in a database depends on the system’s design. Available memory does not tell us how much of it has been used.
Information used to control access to the card
Some chips use keys and access settings to limit which parts of memory can be read or changed. These controls vary by chip. A reader that obtains a card’s identifier may still be unable to access other data on the card.
What Is Stored on the Card vs. in the Database?
Information displayed or used by an RFID system may come from the card, a database, or both. In one common design, a reader obtains an identifier from the card. Access control software then uses that identifier to find a database record containing details such as a person’s name and permitted doors.
A company, for example, may issue employee cards carrying identifiers while managing access permissions in its system. An administrator can update an employee’s permissions in the database. With this design, the card does not need to be rewritten when those permissions change.
Other systems place application data on the card. A hotel lock operating without a live connection to the front desk system, for example, may use data encoded on a hotel key card to decide whether to unlock. Required data varies by lock system. A name, room number, or access decision appearing in software does not reveal where each detail is stored.
For more on how a card communicates with a reader, see What Is RFID Card? Understanding How RFID Card Technology Works.
How Does the Data Differ by RFID Card Type?
“RFID card” describes a physical format. Cards that look alike may contain different chips, with different memory layouts and access features. The chip and its encoding determine what data a card contains. Frequency and protocol affect which readers can communicate with it.
| Card type | What it may store | What to keep in mind |
|---|---|---|
| 125 kHz fixed-ID card | A factory-set identifier | In a typical application, a reader obtains the fixed identifier and the system uses it to find a related record. |
| 125 kHz programmable card | Data written in a format supported by the chip and its configuration | A programmable card is not a general-purpose storage device. Compatibility with an existing reader must be checked. |
| 13.56 MHz smart card | An identifier and, depending on the chip, data stored in memory areas or application files | Capacity, data organization, and access controls vary between chip families. |
| UHF card-format tag | Depending on the chip, EPC, tag identifier (TID), and user memory areas | Contents depend on the chip and its encoding. These UHF memory terms do not describe every RFID card. |
A card with a MIFARE chip has a different memory layout from many 125 kHz cards and UHF card-format tags. Cards containing the same chip model can also hold different application data when encoded for different systems. Contactless IC cards can be made with different chips, so the card format alone does not identify its memory layout. To determine what a particular card stores, check its chip model and the issuing system’s encoding specification.
How Much Data Can an RFID Card Store?
Storage capacity varies by chip. Some chips mainly provide an identifier; others have memory for application data.
For example, ZF Card’s contactless IC card options list 1 KB of memory for MIFARE Classic 1K, 4 KB for MIFARE Classic 4K, and 2 KB, 4 KB, or 8 KB for different MIFARE DESFire EV1 versions. These figures refer to the listed chip models. They do not necessarily represent the space available for application data.
A chip may use part of its memory for data organization or access settings. The issuing system may use only a portion of the remaining space. If your application needs data stored on the card, confirm the chip model and the amount of memory your system can use.
Can RFID Card Data Be Read, Changed, or Protected?
Reading an identifier does not give a reader access to every piece of data on a card. Depending on the chip and its configuration, certain memory areas may require authentication before reading or writing is allowed.
The ability to change data also varies. A manufacturer-set identifier on a fixed-ID card is not intended to be rewritten. Other cards allow writing to certain memory areas, although keys or access settings may limit who can make changes. Some restrictions can be changed with proper authorization; others may be permanent.
For a specific card, check what the system reads, which memory areas it can update, and what credentials those operations require.
How Do You Specify the Right Card and Encoding for Your System?
Begin with the equipment and software the new card must work with. Gather available specifications for the current card, reader, or hotel lock. Confirm the required chip or protocol, operating frequency, and data the system needs to read or write. Cards operating at the same frequency may still use incompatible formats or access settings.
Next, decide whether your team will encode the cards or whether they need encoding before delivery. For pre-encoded cards, agree on the data format and each party’s encoding responsibilities with the card supplier and system provider. Include any protected-data requirements in the technical specification.
Test a sample in the actual system before ordering in volume. Check whether the reader recognizes the card and whether required functions, such as opening a door or updating card data, work as intended.
Conclusion
An RFID card may contain an identifier, application data, or information that controls access to its memory. After reading the card, a system may also retrieve details from a database. The chip and encoding determine what is stored on a particular card.
Need an RFID Card for Your System?
Contact ZF Card with details about your application and any available specifications for your reader, lock, or current card. Include encoding requirements if you have them. ZF Card can help narrow down chip options and discuss sample testing with your equipment.
FAQs
Does a blank RFID card already contain data?
“Blank” usually means a card has not been encoded for a particular application. Its chip may still contain a manufacturer-set identifier or other factory data. Contents before encoding vary by chip.
Does an RFID card store my name or personal information?
It depends on the system. Many cards provide an identifier linked to personal details in a database. Some systems also write personal information to the card.
Can two RFID cards look identical but store different data?
Yes. Cards with the same appearance can carry different identifiers or application data. They may also contain different chips, affecting the data they support and the readers that can use them.