13.56MHz H110-U
13.56MHz USB NFC / MIFARE Card Reader, Slim Pad, No Driver
- USB
- Desktop
Read range: Up to 80 mm
RFID readers
13.56MHz RFID & NFC Card Readers: ISO 14443A MIFARE and ISO 15693
Nine read-only 13.56MHz RFID and NFC readers for MIFARE Classic, NTAG and ICODE cards, in desktop, USB stick and keypad formats. Most read the card UID at up to 80 mm (the keypad model up to 50 mm) and pass it to your software as keyboard input or serial data.
13.56MHz 
13.56MHz H110-R
13.56MHz RS232 MIFARE Card Reader, Slim Pad, DB9 Serial
- RS232
- Desktop
Read range: Up to 80 mm
13.56MHz H120-U
13.56MHz USB NFC Reader, Flat Desktop Pad for MIFARE Cards
- USB
- Desktop
Read range: Up to 80 mm
13.56MHz 
13.56MHz H150-U
13.56MHz USB MIFARE Reader, Angled Desktop with Card Recess
- USB
- RS232
- Desktop
Read range: Up to 80 mm
13.56MHz H150-R
13.56MHz RS232 MIFARE Desktop Reader with Card Recess, DB9
- RS232
- Desktop
Read range: Up to 80 mm
13.56MHz H155-U
ISO 15693 USB RFID Reader for ICODE Tags, 13.56MHz Desktop
- USB
- Desktop
Read range: Up to 80 mm
13.56MHz Photos on request
13.56MHz H310-U
13.56MHz NFC Card Reader with Numeric Keypad, USB
- USB
- Keypad
Read range: Cards up to 50 mm (about 30 mm for consistent reads)
Every reader in this range does one job: it reads the unique ID (UID) of a 13.56MHz card and passes that number to the host. Eight models are 13.56MHz IC card readers for ISO 14443A (MIFARE Classic 1K / S50) cards, and also read MIFARE Classic 4K (S70), NTAG203 and, on some models, NTAG213. The ninth, the H155-U ISO 15693 USB reader, reads ICODE 2 tags. All nine are read-only: they do not write sectors, change keys or copy cards, and they do not read the NDEF content stored on NFC tags.
Typical buyers are integrators and software vendors who need a card number inside access-control, attendance, membership or POS software, and distributors who want a USB NFC card reader for every kind of counter. Four questions decide the model:
- Card standard. MIFARE and NTAG are ISO 14443A; ICODE is ISO 15693. One reader does not cover both.
- Host interface. USB keyboard output types the number at the cursor. RS232 and USB serial emulation deliver it to a port that your software reads.
- Number format. The default is a 10-digit decimal built from a 4-byte UID. If your system stores hex or reversed bytes, the format is set before shipment.
- Form factor. Slim or flat pad, angled desktop with card recess, USB stick or numeric keypad.
Cards on 125kHz? See the 125kHz RFID readers instead.
Model comparison
All nine models are read-only and output the card UID; none of them writes to cards. Ranges are for ISO-size cards and depend on the card and its surroundings, so key fobs and small labels read closer.
| Model | Frequency | Interface | Form factor | Read range |
|---|---|---|---|---|
| H110-U | 13.56 MHz | USB | Desktop | Up to 80 mm |
| H110-R | 13.56 MHz | RS232 | Desktop | Up to 80 mm |
| H120-U | 13.56 MHz | USB | Desktop | Up to 80 mm |
| H130-U | 13.56 MHz | USB | Desktop | 0–80 mm |
| H150-U | 13.56 MHz | USB, RS232 | Desktop | Up to 80 mm |
| H150-R | 13.56 MHz | RS232 | Desktop | Up to 80 mm |
| H155-U | 13.56 MHz | USB | Desktop | Up to 80 mm |
| H210-U | 13.56 MHz | USB | Plug-in | Up to 80 mm |
| H310-U | 13.56 MHz | USB | Keypad | Cards up to 50 mm |
How to choose a 13.56MHz card reader
Start with the card, not the reader. A 13.56MHz MIFARE reader and an ICODE reader look identical on a desk, but they speak different protocols.
- Identify the chip standard. MIFARE Classic and NTAG are ISO 14443A; ICODE labels are ISO 15693. The H155-U is the only ISO 15693 model here. The MIFARE Classic vs Ultralight vs NTAG213 guide compares the common ISO 14443A chips, and the ISO 14443 vs ISO 15693 guide explains the difference between the two standards.
- Check that your chip is listed. MIFARE DESFire, MIFARE Plus, ISO 14443B and FeliCa are not on any model's supported list. MIFARE Ultralight is ISO 14443A but not named, so test a sample first.
- Decide how the number reaches your software: keyboard input or a serial port (see the next section).
- Check the UID length. The default output is built from 4 bytes. NTAG tags carry a 7-byte UID and ISO 15693 tags an 8-byte UID; if your database stores the full UID, say so in your RFQ.
- Set range expectations. The desktop pads read up to 80 mm and the keypad up to 50 mm for cards (about 30 mm for consistent reads) and 15 mm for key fobs. If you need metres rather than centimetres, look at the UHF readers.
Keyboard, USB serial or RS232: how the card number reaches your software
| Interface | Models | How the number arrives | Good for |
|---|---|---|---|
| USB keyboard emulation | H110-U, H120-U, H130-U, H210-U, H310-U | Typed at the cursor, no driver | Staffed desks, spreadsheets, web forms, POS fields |
| USB with RS232 UART emulation | H150-U | Serial data read by your application (USB mode confirmed in the quotation) | Background capture without a focused text field |
| USB, mode confirmed per order | H155-U | Keyboard-style or serial, agreed in the quotation | ISO 15693 tag desks |
| RS232 (DB9) | H110-R, H150-R | 9600 bps 8-N-1 by default; 10-digit decimal or STX/ETX frame with BCC | Kiosks, controllers, PCs with a COM port |
Keyboard emulation is the fastest route to a working system: plug in, click into a field, present a card. Its limit is focus, because the number goes wherever the cursor is. Serial output removes that dependency and suits unattended equipment, at the cost of a few lines of code to open the port. The keyboard-wedge reader guide compares the two approaches, and the keyboard-emulation and RS232 / RS485 hubs list matching readers in other bands.
Card number formats: why the number may not match
A common question is "the reader shows a different number from the one in our system". The card is read correctly; the difference is how the UID is written down. One 4-byte UID can look like this:
| Format | UID 1F 8A 44 C3 |
|---|---|
| 8-digit hex | 1F8A44C3 |
| 10-digit decimal | 0529155267 |
| 8-digit hex, reversed byte order | C3448A1F |
| 10-digit decimal, reversed byte order | 3276048927 |
Take one enrolled card, compare its stored number with these variants using the card number converter, and put the matching format in your RFQ; the reader is preset to that custom output format before shipment. The card number formats guide covers the other variants you may meet.
Which model for which job
| Job | Model | Why |
|---|---|---|
| Enrolling MIFARE cards into access-control or attendance software | H110-U | 10 mm slim pad, keyboard output, 10-digit default |
| Counters that also use 125kHz or UHF desk readers | H120-U | Same flat pad as the L120-U and U120-U |
| Front desks in view of customers | H130-U | Glossy housing, controllable LED and buzzer |
| Software that reads a serial connection over USB | H150-U | UART emulation, card recess, NTAG213 listed |
| Kiosks, controllers and PCs with a DB9 COM port | H110-R or H150-R | RS232, framed output with checksum |
| Library, document or asset tags (ICODE) | H155-U | ISO 15693 |
| Laptops, hot desks, Android through OTG | H210-U | 10 g USB stick, no cable |
| Membership or canteen tills that also need number entry | H310-U | Keypad and reader in one, 10 digits + Enter |
For phones and tablets with USB-C, the H220-C USB-C NFC reader for Android plugs in directly. For cordless reading, see the H510-B pocket Bluetooth NFC reader.
Frequently asked questions
Can these 13.56MHz readers write or encode MIFARE cards?
No. All nine are read-only UID readers. They read the card's unique ID and pass it to your software; they do not write sectors, change keys or copy cards.
Can a 13.56MHz reader read 125kHz proximity cards?
No. Cards on 125kHz, such as EM4100 and TK4100, use a different frequency and need a 125kHz reader such as the L110-U 125kHz USB EM4100 reader. If you are unsure which type you have, send us a sample card and we check it.
Which 13.56MHz readers work without a driver?
The USB keyboard-emulation models, the H110-U, H120-U, H130-U, H210-U and H310-U, type the card number at the cursor on Windows XP to 10 and Linux, and on Android through a USB OTG adapter, with no driver. The RS232 models need only a serial port and your own software.
Do these readers support MIFARE DESFire, FeliCa or ISO 14443B cards?
They are not on any model's supported list, which covers MIFARE Classic 1K/4K, NTAG203, NTAG213 on some models, other ISO 14443A cards (UID) and ICODE 2 on the H155-U. Send a sample card if you are unsure and we confirm before you order.
What is the difference between ISO 14443A and ISO 15693 readers?
Both work at 13.56 MHz but use different protocols. ISO 14443A covers MIFARE Classic and NTAG cards; ISO 15693 covers vicinity tags such as ICODE 2, common on library items and asset labels. The H155-U reads ISO 15693; the other eight read ISO 14443A.
Why does the reader output a different number from the one printed on my card?
The printed number and the reader output are often the same UID in different formats: decimal vs hex, or reversed byte order. Compare them with the card number converter and ask for the matching output format before shipment.
Tell us your card, interface and quantity
Send the card or tag type, the host system and your volume. We reply within 1 business day with a suggested model and sample options.