13.56MHz H220-C
USB-C 13.56MHz NFC Reader for Android Phones, MIFARE UID
- USB
- Plug-in
Read range: 0–30 mm front and back, 0–10 mm from the side
RFID readers
USB-C OTG RFID & NFC Readers for Android Phones and Tablets
Plug-in readers that connect straight to the USB-C port of an Android phone or tablet, take power from it and type the card or tag number into any app. Three models cover 13.56MHz NFC, 125kHz EM4100 and UHF EPC tags.
13.56MHz 
125kHz L220-C
USB-C 125kHz EM4100 RFID Reader for Android Phones
- USB
- Plug-in
Read range: 0–30 mm front and back, 0–10 mm from the side
UHF A USB-C OTG RFID reader turns an Android phone or tablet into a card-reading terminal without an app project. The reader plugs into the Type-C port, draws 5 V / 100 mA from the device and types the card number at the cursor, the same way a keyboard would. Whatever is on screen receives the number as text: a web form, a spreadsheet, or a POS or access-control app.
Typical buyers are software vendors and integrators whose field staff already carry Android devices: security teams checking badges, attendance and event operators, installers enrolling cards, and asset teams checking UHF labels. Distributors offer them as an add-on for the same customers.
Three decisions cover most projects. First, the card frequency: phone NFC reads 13.56MHz only, so 125kHz EM4100 badges need the L220-C and UHF tags need the U220-C, while the H220-C covers MIFARE and NTAG cards. Second, the number format your software expects. Third, the host device, which must support USB OTG. All three models are read-only, share a 35 × 35 × 7 mm housing and also work on a Windows PC through an OTG adapter.
Model comparison
All three models share the same 35 × 35 × 7 mm USB-C housing, power draw and Android OTG requirement, so choose by the card or tag frequency you need to read.
How to choose a USB-C phone RFID reader
- Identify the card or tag. Is it a 125kHz proximity card such as EM4100 or TK4100, a 13.56MHz MIFARE Classic or NTAG card, or a UHF label? The frequency decides the model, and no reader in this range covers two frequencies. If you are unsure, read 125kHz vs 13.56MHz RFID readers or send a sample card with your RFQ.
- Decide which number you need. The H220-C and L220-C output the card UID or ID as a 10-digit decimal (4 bytes) by default, and a custom format can be set before shipment. Note that 7-byte UIDs, such as those on NTAG203 tags, do not fit in that default 4-byte output. The U220-C types the EPC followed by Enter. Match this to what your database already stores; RFID card number formats explains the common variants.
- Check the host device. You need an Android phone or tablet with a USB-C port and USB OTG support. iOS is not listed for these models; for iPhone and iPad, look at the Bluetooth H510-B or U510-B, which list iOS support.
- Set range expectations. The 13.56MHz and 125kHz models read at 0–30 mm from the front or back and 0–10 mm from the side; the UHF model reads at 0–5 cm. These are tap-to-read devices for one card at a time, not long-range readers.
13.56MHz, 125kHz and UHF phone readers compared
| Model | Frequency | Cards / tags | Read range | Default output | Typical job |
|---|---|---|---|---|---|
| H220-C | 13.56 MHz | MIFARE Classic 1K/4K, NTAG203, other ISO 14443A (UID) | 0–30 mm | 10-digit decimal | Membership and staff cards on tablets without NFC |
| L220-C | 125 kHz | EM4100, TK4100, SMC4001 (ID) | 0–30 mm | 10-digit decimal | Badge checks and enrollment for EM4100 access systems |
| U220-C | 902–928 MHz | ISO 18000-6C (EPC) | 0–5 cm | EPC + Enter | Checking one UHF label or asset tag at a time |
All three take 5 V / 100 mA from the host, weigh about 20 g, operate from -20 °C to +70 °C and come in black or white. For FDX-B and EMID animal microchips, the same housing is available as the A220-C in our animal ID range.
How the keyboard output works on Android
These readers use keyboard emulation. Each read is typed wherever the cursor is, exactly as if someone had typed the number. Plan for three things:
- Focus. If no text field is active, the number goes nowhere. Design the screen so the input field has focus when staff are expected to read a card.
- Enter as a trigger. The U220-C sends Enter after the EPC, so a form can submit or a search can run on each read. For the H220-C and L220-C, state the exact string your app expects when you order.
- On-screen keyboard. Android may hide the on-screen keyboard while a keyboard-type device is connected. If staff also type by hand, turn the on-screen keyboard back on in the device's keyboard settings.
Because nothing is installed, the same reader works in a browser-based system, a spreadsheet app or your own Android app. For background, see what a keyboard-wedge RFID reader is; desktop and handheld models with the same output are listed under keyboard-emulation RFID readers.
OTG checklist before a rollout
- Confirm OTG on the exact device model. Some phones and tablets need OTG switched on in Settings, and some switch it off again after a period without use.
- Check the case. Thick or rugged cases can stop the plug from seating fully in the port.
- Test with your real cards and tags. Range depends on card and tag construction, and small UHF tags or tags on metal may need to be held closer.
- Pilot before volume. Order sample units, run them in your own app on your own devices, then confirm the output format for the production order.
The full step-by-step setup is in the USB-C RFID/NFC reader OTG checklist.
Frequently asked questions
Can an Android phone read 125kHz RFID cards without an external reader?
No. Phone NFC works at 13.56 MHz only, so 125kHz EM4100 and TK4100 cards need external hardware such as the L220-C, which plugs into the USB-C port.
Do these USB-C readers need an app or driver on Android?
No app is needed. The reader types the card or tag number at the cursor in any app. The phone or tablet must support USB OTG; on some models it has to be switched on in Settings.
Do the USB-C readers work with iPhone or iPad?
iOS is not listed for these models. For iPhone and iPad, look at our Bluetooth readers: the H510-B (13.56MHz) and U510-B (UHF) list iOS support.
Can a USB-C phone reader write or copy cards?
No. All three are read-only. The H220-C and L220-C read the card UID or ID number, and the U220-C reads the EPC. To write UHF tags, use a desktop reader/writer such as the U120-U.
What read range should I expect?
0–30 mm from the front or back and 0–10 mm from the side for the H220-C and L220-C, and 0–5 cm for the U220-C. They are designed for tapping one card or tag at a time.
Can I use the same reader on a Windows PC?
Yes, on Windows XP, 7 and 10 through an OTG adapter. For PC-only installations, a USB desktop reader with a cable, such as the L110-U or H110-U, is more practical.
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.