Skip to main content
The MBKYC SDK reads Emirates ID cards through smart card readers and captures biometrics through fingerprint sensors. Beyond the specific models validated below, the SDK ships generic PC/SC and CCID drivers, so most standards-compliant readers work without a vendor-specific integration.
Legend — ✓ supported · — not supported on that platform. A device may support smart card reading, fingerprint capture, or both; the columns show what the SDK supports, which is not always everything the hardware can do.

​
Generic drivers (start here)

These cover the widest range of hardware. Reach for a vendor-specific entry only when a device isn’t a standard PC/SC or CCID reader, or when you need its fingerprint sensor.
The validated smart card readers below (ACS, Feitian, IDENTOS) are simply confirmed examples of PC/SC and CCID readers — they work through the generic drivers. If your reader is PC/SC (desktop) or USB CCID (Android) compliant, it should work even if it isn’t listed.

​
Smart card readers

​
Fingerprint sensors

Fingerprint capture for these devices is implemented directly in the SDK (a reverse-engineered protocol), so it works across platforms even where the vendor’s own plugin doesn’t.
Some combined SC+fingerprint devices are supported for smart card only because no fingerprint integration is available for them (e.g. IDENTOS Tactivo Mini / Tacmini OS, SecuGen Hamster Pro Duo). Use a sensor from the fingerprint table above for biometric methods.

​
How devices map to SDK components

On desktop, smart card and fingerprint support come from the signed services you install; on Android, from the service AARs you depend on. See the package matrix for coordinates and the Android guide for USB-attach wiring. Once the hardware and its service are in place, the readers surface through listSmartcardReaders() / listFingerprintReaders() with vendor-prefixed IDs (ccid:…, nfc:…, morpho:…).