DEVICE · CHECKID

CheckID-ET100

CheckID-ET100 is designed to meet tough security needs without sacrificing convenience. The device has a USB Type A female port allowing for it to be connected to a PC. Various biometric sensors such as SecuGen, SupreMa, ZKTeco and Morpho are supported by the card reader. The biometric sensor should be selected based on customer requirements.

CheckID-ET100 technical device illustration
CheckID-ET100Device → Middleware → SDK/API
3-LAYER MODEL

Hardware → Middleware → Platform

The device is part of the trust chain, not an isolated catalogue item.

01 · HARDWARE

Capture surface

  • NFC 13.56 MHz · ISO/IEC 14443 A/B
  • MRZ 300 dpi multispectral
  • Fingerprint (model capability)
02 · MIDDLEWARE

Driver / firmware / adapter

  • Device driver / firmware as applicable
  • Secure capture and local integration
  • Compatibility must follow device package
03 · PLATFORM

CheckID integration

  • SDK / adapter
  • REST / Kafka where applicable
  • Subject → Process → Evidence
SPECIFICATION

Source-backed technical specification

Field Published / source-backed value
Processor / host Cortex-A53 2.0 GHz
Memory 2/4 GB · 16/32/64 GB
Display 10.1" · 1280×800
Camera 5 MP
NFC / card NFC 13.56 MHz · ISO/IEC 14443 A/B
MRZ / document MRZ 300 dpi multispectral
Biometric Fingerprint (model capability)
Connectivity Wi-Fi · Bluetooth · Ethernet · cellular
Physical / OS 273×155×20 mm · 2.5 kg
INTEGRATION

Device → SDK → API → Evidence

Cross-navigation connects capture capabilities to CheckID process and evidence.

◈

SDK / Adapter

Capture and session integration.

SDK
◈

CheckID Process

Subject/process workflow selected by use case.

RESTKafka
◈

Evidence

Result, transaction context and audit trail.

Evidence
SOURCE-BOUND REFERENCE

CheckID-ET100: source-backed product specification

Source → Scope → Evidence → Limitation

Model and source

CheckID-ET100 · official CheckID public product source. Source status: SOURCE_BACKED.

Source-backed hardware

Cortex-A53; 10.1in; NFC; MRZ; camera; fingerprint. Only these sourced attributes are promoted to public specification in .

Middleware boundary

driver/firmware boundary. Concrete driver/firmware versions require separate source evidence when absent from the datasheet/matrix.

CheckID integration

SDK/API cross-link. Device capability does not imply every verification method is supported.

Publication rule

No CPU/OS/interface/certification is added beyond the matrix/datasheet. Compatibility is tied to tested configuration or source version.

Lifecycle and limitations

Where EOL, firmware compatibility or tested OS is not sourced, records a publication limitation rather than inferring it.