H220-C USB-C NFC reader in white and black, front view with USB-C plugs

H220-C USB-C 13.56MHz NFC Reader for Android Phones, MIFARE UID

The H220-C is a 35 × 35 mm plug-in NFC reader for Android phones and tablets with a USB-C port and OTG support. It reads the UID of MIFARE Classic, NTAG203 and other ISO 14443A cards at 0–30 mm and types it as a 10-digit decimal number into whatever app has the cursor.

Frequency: 13.56 MHz
Cards / tags: MIFARE Classic 1K (S50), MIFARE Classic 4K (S70), NTAG203, other ISO 14443A cards
Interface: USB Type-C plug (USB OTG)
Output: Keyboard emulation: card number typed at the cursor
Read range: 0–30 mm front and back, 0–10 mm from the side

Request a quote for H220-C Order a sample Datasheet (PDF)

✓ Sample units for evaluation
✓ Output format confirmed for your software
✓ Private label & OEM options
✓ Reply within 1 business day

Why integrators choose the H220-C

No app to build — the card number is typed at the cursor, so web forms, spreadsheets and your existing Android app receive it as text.
13.56MHz reading for devices without NFC — adds MIFARE and NTAG UID reading to Android tablets, phones and handhelds that have a USB-C port and USB OTG support but no NFC chip.
ISO/IEC 14443A UID reading — MIFARE Classic 1K (S50), MIFARE Classic 4K (S70), NTAG203 and other 14443A cards.
Familiar number format — 10-digit decimal (4 bytes) by default, the same default as our H110-U USB desktop reader; other formats on request.
Powered by the phone — 5 V, 100 mA from the USB-C port, so there is no battery to charge.
Pocket size — 35 × 35 × 7 mm without the plug and about 20 g, in black or white.

Why use an external NFC reader on an Android phone

Many Android phones already have NFC, so why add hardware? There are three practical reasons.

Devices without NFC. Many tablets, budget phones and handheld terminals have no NFC chip. The H220-C adds 13.56MHz card reading through the USB-C port.
No app development. Reading a card with built-in NFC needs an app written for the Android NFC API. The H220-C types the UID at the cursor, so a browser-based system, spreadsheet or POS screen receives it like typed text.
A fixed tap point. The position of the built-in NFC antenna varies from one phone model to the next. With the H220-C, staff always tap the card on the same spot: the reader face.

Typical jobs: looking up MIFARE membership cards on a reception tablet, checking staff cards at an event entrance, and enrolling new cards into a web-based access or attendance system.

What the H220-C reads and what it outputs

The H220-C reads the UID (serial number) of ISO/IEC 14443A cards: MIFARE Classic 1K (S50), MIFARE Classic 4K (S70), NTAG203 and other 14443A cards. It reads the UID only. It does not read sector data or NDEF records, and it cannot write to cards.

By default the number is sent as a 10-digit decimal built from 4 bytes. MIFARE Classic 1K and 4K cards commonly use a 4-byte UID, so this covers the whole number. NTAG203 tags carry a 7-byte UID, so the default output shows only 4 of those bytes; if your system stores the full 7-byte UID, say so in your RFQ. If your software stores the UID in another format, such as hex, a custom output format can be set before shipment. See RFID card number formats, or compare numbers with the card number converter.

MIFARE DESFire and Plus, ISO 14443B, FeliCa and ISO 15693 are not listed for this model. For ISO 15693 (ICODE) labels on a PC, see the H155-U.

H220-C, L220-C or H210-U?

Choose by card frequency first, then by the host device.

Model	Cards	Host	Read range
H220-C	13.56MHz MIFARE Classic, NTAG203	Android phone or tablet, USB-C OTG	0–30 mm
L220-C	125kHz EM4100, TK4100	Android phone or tablet, USB-C OTG	0–30 mm
H210-U	13.56MHz MIFARE Classic, NTAG203	PC, USB-A port	Up to 80 mm

Not sure which frequency your cards use? Read 125kHz vs 13.56MHz, or send a sample card with your RFQ.

H220-C specifications

General
Model	H220-C
Frequency	13.56 MHz
Form factor	Plug-in reader with USB-C plug, for phones and tablets
Color	Black or white

Cards & reading
Standard	ISO/IEC 14443A (UID read)
Supported cards	MIFARE Classic 1K (S50), MIFARE Classic 4K (S70), NTAG203, other ISO 14443A cards
Read/write	Read-only (UID)
Read range	0–30 mm front and back, 0–10 mm from the side
Read time	0.2 s
Read interval	0.5 s

Interface & output
Interface	USB Type-C plug (USB OTG)
Output	Keyboard emulation: card number typed at the cursor
Default format	10-digit decimal (4 bytes)
Custom format	On request
Host systems	Android with USB OTG; Windows XP / 7 / 10 through an OTG adapter
App or SDK	None required on Android

Physical & environment
Power	5 V, 100 mA from the host
Indicator	2-color LED (blue: power, green: status)
Dimensions	35 × 35 × 7 mm (without plug)
Weight	Approx. 20 g
Package	71 × 71 × 19 mm, approx. 50 g packed
Operating temperature	-20 °C to +70 °C

Specifications of H220-C as supplied for the standard version. Read range depends on the card or tag, mounting surface and environment — we can test your own cards before you order.

Download the H220-C datasheet (PDF, A4)

Card, tag and system compatibility

Works with

✓MIFARE Classic 1K (S50) and 4K (S70) cards and key fobs (UID read)
✓NTAG203 and other ISO/IEC 14443A cards (UID read)
✓Android phones and tablets with a USB-C port and USB OTG support
✓Windows XP / 7 / 10 PCs through an OTG adapter

Not designed for

✕Writing, encoding or copying cards (read-only UID reader)
✕Reading MIFARE sector data or NDEF content
✕125kHz EM4100/TK4100 cards — use the L220-C
✕MIFARE DESFire / Plus, ISO 14443B, FeliCa and ISO 15693 (not listed for this model)
✕iPhone and iPad (iOS not listed) — the H510-B Bluetooth reader lists iOS
✕Phones and tablets without USB OTG support

Card not listed? Send us the card type or a photo and we will confirm compatibility before you buy.

Integration in 4 steps

1
Check that the phone or tablet supports USB OTG. On some models OTG has to be switched on in Settings.
2
Plug the H220-C into the USB-C port. The blue LED shows it has power; nothing needs to be installed on Android.
3
Open the target app and tap into the input field so the cursor is there.
4
Hold the card flat against the front or back of the reader, within 30 mm. The 10-digit card number is typed at the cursor.

OEM / ODM options for H220-C

◆Output format other than the default 10-digit decimal (for example hex) on request, set before shipment
◆Housing color: black or white
◆Logo and private-label packaging on request; feasibility and terms confirmed in your quotation

How OEM/ODM projects work →

Typical applications

H220-C FAQ

Does the H220-C need an app on the phone?

No. It types the card number at the cursor, so any app with a text field receives it. The phone or tablet must support USB OTG.

How close does the card have to be?

0–30 mm from the front or back of the reader and 0–10 mm from the side. For the most consistent reads, tap the card flat on the face.

Which number format does the H220-C output?

A 10-digit decimal number built from 4 bytes of the UID by default. That is the full UID of a typical 4-byte MIFARE Classic card, but only part of the 7-byte UID on NTAG203 tags. If your system stores hex, the full 7-byte UID or another format, state it in your RFQ and the output format is confirmed in your quotation.

Can it read MIFARE Classic sector data or write NFC tags?

No. The H220-C reads the card UID only. It does not read sectors or NDEF records, and it does not write or encode tags.

Will the H220-C work on a Windows PC?

Yes, on Windows XP, 7 and 10 through an OTG adapter. For a PC-only installation, the H110-U desktop reader or the H210-U USB stick is a better fit.