Chip cards may behave differently depending on the operating system on a given computer. The following lists the basic requirements of each operating system and tested card readers. The operation of other card readers has not been tested and we do not know their compatibility in the DigiDoc4 client application. If USB adapter is used (USB HUB/expander, OTG, etc.), you must make sure that it is a device intended for data transmission.
However, you can find information on supported operating systems here.
Windows, macOS and Ubuntu
- ACR39U-UF (Type-C cable)
- ACS ACR 38 (USB)
- Alcor Micro AU9540 (USB)
- Axagon CRE-SM4 (USB)
- Dell Broadcom internal card reader (WUDF driver)
- Gemalto CT30 (USB)
- Gemalto Ezio CT710 (PinPad, USB, manufacturer driver)
- Lenovo internal card reader Alcor Micro (manufacturer driver)
- Omnikey Cardman 1021 (USB)
- Omnikey CardMan 3021 (USB)
- Omnikey CardMan 3121 (USB)
- Omnikey Cardman 3821 (PinPad, USB, manufacturer driver)
- Pluss ID v3 (USB)
- SCM SCR 3310 (USB)
- Lindy 42764 (USB, type C)
- ACR38U PocketMate Smart Card Reader
- ACR39U PocketMate II Smart Card Reader
- SCR3500 B Smart Card Reader
- SCR3500 C Smart Card Reader
- FEITIAN iR301U
The name and model of the card reader are generally visible on the label affixed to the reader (usually on the back). The product ID can be found in DigiDoc4 diagnostics.
- On Windows, the card reader generally works with all drivers (manufacturer, Microsoft universal drivers). Replacing card reader manufacturer’s driver with standard Windows drivers instructions can be found here.
- In the case of Linux and macOS, the default installed driver (USB CCID) was tested.
- If the standby and hibernate functions were used with the ID-card still in the reader and any ID-software component open, there may be problems accessing the data on the card.
Usually, it is enough to remove and re-insert the card into the reader. In some cases, the ID-software component (such as DigiDoc4) will have to be re-launched and the computer restarted.
- For PinPad readers, there may be problems with Windows terminal solutions. Terminal systems are not an environment that is officially supported by ID-software.
- There may be a need to limit PinPad mode (on HP and Dell keypad card readers). To do this, a key must be added to the Windows registry. The values of the key can be found on the GitHub website.
- Some unsupported card readers may cause the ID-card to lock itself for self-defence.
NOTE: If you have knowledge of anything that is different from what is posted here, kindly share it with us.