Send us your controller model, card type and install environment. We'll shortlist compatible hardware and quote within 24 hours.
Modules for mixed credential populations, with LF/HF, proprietary-card and selected Bluetooth or mobile configurations. Confirm the returned data and platform requirements with actual credentials.
30 × 16 mm OEM module that reads 125 kHz EM and HID Prox-compatible cards plus MIFARE, DESFire, FeliCa and ICODE at 13.56 MHz, over 3.3 V UART or USB.
Our most complete module: BLE 5.1 plus iCLASS, iCLASS SE, Seos and HID Prox compatibility, EM, MIFARE/DESFire/FeliCa cards and NFC mobile credentials.
30 × 30 mm USB module that reads and writes LEGIC advant and LEGIC prime and also handles MIFARE, DESFire, MIFARE Plus, NTAG, FeliCa and ICODE credentials.
Dual-frequency OEM module listing iCLASS, iCLASS SE, Seos and HID Prox compatibility, EM and MIFARE/DESFire cards, and NFC mobile credentials incl. Apple Wallet.
Dual-frequency module with BLE 5.1 that reads HID Prox-compatible and EM credentials plus MIFARE, DESFire, FeliCa and ICODE, over 3.3 V UART or USB.
Dual-frequency module with BLE 5.1 for Bluetooth virtual cards and data pass-through, reading EM4100-family, MIFARE, DESFire, FeliCa and ICODE credentials.
HF-only OEM module listing iCLASS, iCLASS SE and Seos compatibility alongside MIFARE, DESFire, FeliCa and ICODE, with 3.3 V UART and USB on a 30 × 16 mm board.
Dual-frequency OEM module for EM4100-family and 13.56 MHz MIFARE, DESFire, FeliCa and ICODE credentials, without HID formats, on a 30 × 16 × 8.8 mm board.
The smallest board in our multi-technology range: 25 × 15 × 3.0 mm and about 1.4 g, reading 125 kHz and 13.56 MHz credentials over 3.3 V UART or USB.
13.56 MHz module built around the LEGIC SM-4200 chip that reads and writes LEGIC cards and returns MIFARE, iCLASS, FeliCa and ICODE UIDs over TTL serial.
Low-frequency OEM module that reads HID Prox-compatible and EM4100/4200/4305 credentials, with 3.3 V UART and USB on one header and an external 490 µH coil.
Multi-technology modules help an OEM support an installed mix of credentials within one product. The XM range includes EM and compatible prox options, mixed LF/HF boards and LEGIC-compatible configurations. Some models add Bluetooth or NFC mobile credentials, but these features differ by build.
Define the data the host must receive. A UID or card serial number may differ from the protected credential number an existing system uses. Proprietary-card support should be evaluated against the exact card generation, format and authorized integration rather than a family name alone.
Phone access also depends on provisioning and the platform that issues the credential. Confirm enrollment, application commands and supported devices with a sample setup. The credential migration guide explains why legacy identification and authenticated card data need separate checks.
Compare Wiegand, OSDP and RS485 reader interfaces: wiring, cable limits, AES-128 Secure Channel and steps for a compatible access-control migration.
125 kHz cards are cheap but easy to clone; 13.56 MHz cards add memory and, on DESFire-class chips, AES security. Compare range, chips, security and migration.
Wiegand 26-bit is an even parity bit, 8-bit facility code, 16-bit card number and odd parity bit. Convert card numbers to hex and back with the calculator.
Elevator card readers for car panels and lift lobbies: anti-clone encrypted cards, QR codes for visitors, Wiegand or RS485 output to the floor controller.
Turnstile card readers, QR scanners and face terminals for tripod, swing and speed gates, with Wiegand, RS485, RS232 or TTL output to the gate board.
Build an RFID asset tracking system: on-metal, ceramic and tie-on tags matched to each asset, handheld audits, smart cabinets and IP67 HF heads for tooling.
No. The XM category also includes single-band specialist modules. Check the frequencies and credential list for the selected SKU.
That depends on the read mode and format. Compare actual output from sample cards with the enrolled credential data.
No. The issuing platform and provisioning process are part of the integration. Confirm the supported mobile workflow for the exact module build.
Send your card type, interface and quantity. You get a quote, lead time and compatibility notes within 24 hours — samples available for most items.
