Read an ID
Capture a card identifier in an existing application.
Confirm the output format, byte order and host input method. A UID reader is not necessarily a card writer.
RFIDAK / Reader selection
RFID reader writers.
Start with the card
and the software.
Choose the reader for the operation you need: capture an ID, write a tag or integrate a card application. Then confirm the protocol, host connection and exact model.
HF/NFC options are the focus here. LF and UHF requirements need a separate reader selection.
01 / Required operation
What must the reader do?
Write a tag
Encode NFC links, membership data or project records.
Confirm writable memory, command support and the read-back test for the actual tag.
Integrate a system
Connect a reader to a kiosk, controller or network.
Confirm the interface, power, driver or API, host platform and hardware revision.
03 / Model references
Compare named hardware
Use these references to discuss your requirement. Request current supply and documentation for the exact model before placing an order.
ACS ACR122U
USB NFC reader with PC/SC and CCID support.
Use the manufacturer documentation to check the supported card types and software interface.
ACS model documentation →
µFR Nano
HF reader with vendor API and SDK integration.
Legacy family: for a new design, confirm the current replacement, availability and migration requirements.
Review catalog entry →
µFR Nano Online
Network NFC integration; connectivity varies by hardware version.
Legacy family: confirm the exact network variant and current supply before selecting it for a rollout.
Review catalog entry →Manufacturer references: ACS ACR122U, Digital Logic µFR Nano and legacy notice, Nano Online connectivity. These manufacturers’ model specifications do not establish the specification of another reader.
04 / Project review
Bring your requirement.
We’ll help narrow the model.
Start with these three choices. On the next page, add the card chip if known, software details, quantity and delivery country so we can review the configuration.
Evaluation cost, accessories, supply timing and warranty are confirmed in the quotation.
Skip the choices and contact us →Before a rollout
Approve the complete workflow
before a rollout.
- Identify the configuration. Record reader model, firmware, card chip, host system and driver or SDK version.
- Run the complete operation. Test the required read, write or authentication flow and verify returned data in the application.
- Check the installation. Test orientation, enclosure, power, reconnection and normal operator handling.
- Record acceptance. Keep the test result with the agreed model, accessories, quantity and delivery terms.
Buyer questions
Reader compatibility,
in plain terms.
Can one RFID reader writer work with every RFID card?
Select the reader for the card frequency, protocol and required operation. USB describes the host connection, not the card technology. A matching frequency alone does not establish support for reading memory, writing records or authenticating an application.
Can an HF NFC reader encode UHF inventory labels?
An HF 13.56 MHz NFC reader is not a substitute for a UHF reader. Send the label chip and country of use when requesting UHF equipment so the reader and operating region can be reviewed separately.
Does reading a card UID prove that writing or secure access works?
A UID read only demonstrates that operation. Writing memory or using a protected card application can require different commands, authentication and software support. Define the required transaction and test it with a representative card before approving the hardware.
Will a USB reader work with my existing application?
Check the application’s supported reader interfaces. For example, ACS documents ACR122U as PC/SC and CCID compatible, while Digital Logic documents its own API and communication protocol for µFR Nano. Request a working test on your host and software; the USB plug alone is not enough.
What determines reader price, MOQ and delivery?
The exact model, hardware revision, accessories, evaluation quantity and rollout quantity define the quotation. Confirm available stock, sample cost, freight, warranty and any SDK or firmware service charges. This selection page does not provide a single price or delivery promise for different readers.
Can I use a general reader to encode hotel or access-control cards?
The installed system must support the reader, chip and credential format. Share the lock or platform name and the supported encoding interface. A general reader should not be assumed to replace a system-specific encoder; the approval test must cover the complete authorized issuance workflow.
Match the reader and the credential.
Review the cards or labels that will be used in your actual test.