RFID & NFC Readers for POS, Membership and Loyalty Cards

The problem: member numbers typed at the counter

When a cashier asks for a phone number or copies a member ID from a card, the queue slows down and points land on the wrong account. Each error then needs a manual correction and an apology to the member.

POS and loyalty software vendors want a reader that fills the member field on any till without drivers or device code. Retailers, gyms, clubs, canteens and hotels often add a second problem: a mixed card estate. Older magnetic-stripe cards sit alongside newer contactless cards and fobs, and the tills range from Windows PCs to Android terminals and iPads.

How card reading solves it

A member card already carries a unique number: the chip ID of an RFID card or fob, or the data on its magnetic stripe. The reader reads it when the member presents or swipes the card and types it into the active POS field, just as a keyboard-wedge barcode scanner would. The POS looks up the account and applies points, discounts or a prepaid balance from its own database.

That last point matters. Our 125 kHz and 13.56 MHz readers are read-only and use only the card’s UID, so balances and points must live in your software, keyed to the card number. A lost card is then blocked and replaced in software, and nothing of value is stored on the card itself.

These readers identify members. They are not payment terminals and do not process bank cards.

Choosing the right reader

Starting a new card program? Choose the card first, then the reader. A lookup-based loyalty scheme only needs a unique ID, so 125 kHz EM4100/TK4100 cards and fobs are enough. Choose 13.56 MHz MIFARE Classic if the same card must also work with other 13.56 MHz systems on site, such as door access or a canteen, or if some tills are iPads, because the Bluetooth H510-B reads 13.56 MHz cards. Before the card print run, test one printed card on the reader you plan to use: the number printed on the card should match the number the reader types into the POS.

A Track 2 USB magstripe reader, the M180-U, is also available; see all magnetic stripe card readers. For more RFID options, browse USB-C OTG readers for Android terminals, Bluetooth RFID card readers and the keyboard-emulation readers.

Integration notes

Keyboard input. The reader types into whichever field has focus, so the cursor must be in the member field (or the POS must keep it there) when the card is presented. Keep the till’s input language on English (US) so digits arrive unchanged. The guide to keyboard-wedge RFID readers covers focus and layout pitfalls.

Number format. The USB and USB-C RFID models in the table output the 10-digit decimal of the 32-bit ID by default. The H510-B outputs 8-digit hex by default and can be set to 10-digit decimal or 10-digit hex. If you are replacing readers in a running scheme, send an example card with the number your system already holds for it; the pad, stick and USB-C readers can be supplied with a matching custom output format. The RFID card number converter is a quick way to check.

MIFARE and NTAG. The 13.56 MHz models read the UID only, not the card’s data sectors. MIFARE Classic 1K/4K cards usually have a 4-byte UID, which fits the 10-digit default. NTAG tags have a 7-byte UID, so if members use NTAG stickers or fobs, tell us and we confirm the output format first. See MIFARE Classic vs Ultralight vs NTAG213.

Magnetic stripe. The M170-U reads tracks 1, 2 and 3, all tracks or any two, with a bi-directional swipe at 15–120 cm/s and a head life of at least 800,000 passes. A PC setting utility selects the tracks, start and end sentinels, Enter and the beeper. Check which track holds your member number with magnetic stripe tracks 1, 2 and 3 explained.

Tablets and iPads. The USB-C models need OTG support on the terminal and read at 0–30 mm from the front or back. The H510-B pairs over Bluetooth without a password (stable to 10 m) or through its 2.4G USB dongle, and appends Enter by default. Its USB cable is for charging only, not data.

What to send us for a quote

1. One of each member card type you issue, or clear photos: RFID card, fob, sticker or magnetic-stripe card.
2. The POS platform at each till: Windows PC, Android terminal (USB-C and OTG support), iPad or phone.
3. The member number your system stores for one of those cards, and whether it needs Enter or Tab after it.
4. The counter layout: desk pad, USB stick, keypad or swipe reader.
5. Quantities per store and the number of stores.
6. OEM requirements, such as your branding or a fixed output format for your POS software. See OEM and ODM options.

POS and loyalty software vendors can have readers supplied with the output their software expects. Price, MOQ and lead time are confirmed in your quotation. Request samples to test at a real till, or contact us with the details above.