RFID / NFC Access
Applies to: Emiko platform, RFID / NFC access
Audience: Customers & partners
Last updated: 2026-01-25
Purpose
This article explains how RFID / NFC credentials are used in the Emiko system, including how access works locally and offline, and how card IDs must be stored to function correctly.
It exists to ensure:
correct enrollment of RFID / NFC credentials
predictable access behavior
understanding of offline operation
correct storage of card IDs in Emiko
1. RFID / NFC Technology Used in Emiko
Emiko uses RFID technology operating at 13.56 MHz, also commonly referred to as:
RFID (High Frequency)
NFC (Near Field Communication)
These terms describe the same underlying technology and are often used interchangeably.
2. How RFID / NFC Access Works in Emiko
Emiko access control is designed to work locally at the equipment, without depending on a live network connection.
Normal operation
Emiko distributes the access list to the GSM controller installed in the equipment
The GSM controller stores this access list locally
When a card is presented:
The RFID reader reads the card ID
The GSM controller validates the card locally
Access is granted or denied immediately
Offline operation (Key benefit)
If GSM, WiFi, or internet is unavailable:
The GSM controller continues to:
read RFID / NFC cards
validate access locally
activate services (e.g. power outlets)
RFID / NFC access continues to work even when the network is down.
Important notice
Changes in Emiko are not applied instantly.
It can take up to 20 minutes for changes to take effect, including:
adding customers
adding or assigning RFID / NFC keys
changing access rights
updating validity periods (From / To)
For changes to be distributed, the GSM device must be online.
If the device is offline, updates will be applied when it comes online again.
3. What Is Read from an RFID / NFC Card
From each card or key, the system reads:
the unique card identifier (UID / CSN) only
The system does not read:
cardholder name
stored value
access rights stored on the card
application data
All access rules are defined and distributed via Emiko.
4. How Card IDs Are Converted and Stored (Important)
When a card is read, the system automatically:
reads the card’s unique identifier
converts it to a standard internal format
stores the value as an uppercase hexadecimal (HEX) string
This conversion is automatic and always consistent.
What this means
Card IDs must be stored exactly as the HEX value
Matching is exact
Formatting must not be changed
Example
After reading a card, the ID is represented as:
078C68BB
This exact value must be stored in Emiko.
5. Adding RFID / NFC Keys in Emiko
RFID / NFC keys must be registered in Emiko before they can be used for access.
Required: USB RFID / NFC Reader
To register a card or key, a USB RFID / NFC reader connected to a PC is used.
The USB reader is used to:
read the card’s unique identifier (UID)
display the UID as a HEX value
Saving the key in Emiko
The following steps are required:
Read the card using the USB reader
Copy the HEX value exactly as shown
Save this value in Emiko RFID Management
Assign access rights as required
Only keys saved in Emiko will be distributed to the equipment and allow access.
6. USB Table Reader for Enrollment (Optional)
We offer a compatible USB RFID / NFC table reader for administration and onboarding.
The reader:
operates at 13.56 MHz (RFID / NFC)
reads card UID only
is pre-configured to match Emiko’s requirements
If supplied by us, the reader is:
ready to use
tested with Emiko
suitable for batch enrollment and office setup
7. Key Takeaway
RFID / NFC access is validated locally in the equipment
Card IDs must match the HEX value stored in Emiko
Access continues to work offline
Changes may take up to 20 minutes and require the device to be online