Identifier format
Compare real card output with the identifiers in your records. Decide whether the application expects a prefix, delimiter or Enter key after the number.
UID / HID / INTEGRATION PATH
Put a card number into the right field.
A keyboard-emulation reader can enter a card identifier into an application that accepts text input. The useful purchase specification includes the output format and receiving workflow, not just the USB connector.
See the matching modelsDEFINE THE APPLICATION
Start with the parts that decide the fit.
Start with the identifier already used by your system. Define hexadecimal or decimal output, byte order, leading zeros and any prefix or suffix. Then check where the input goes when the reader is connected. UID input and authenticated card-data access are different requirements; choose the software path that matches the actual task.
Receiving workflow
Test focus changes, keyboard layout, repeated presentations and the complete operator workflow in the target software.
Firmware and cards
JustID firmware tiers differ in supported operations and standards. List your cards and confirm the selected tier instead of relying on the family name.
THE HARDWARE
UID keyboard readers
Protocols and connections depend on the selected configuration. Review the model details.
MAKE THE INQUIRY SPECIFIC
Tell us what the project needs.
- What card family and identifier format does your system use?
- Which receiving application, keyboard layout and target field?
- What prefix, suffix and repeat-reading behavior are needed?
Selection questions
Can a UID keyboard reader write NFC tags?
Card-number keyboard input is a different workflow from writing tags. Select a reader writer and suitable SDK or application when writing is required.
Will two readers output the same card number?
The displayed representation may differ. Confirm number base, byte order and formatting against your existing records.