Home
Apps
Tools
KAZTOKEN mobile

KAZTOKEN mobile

1.0

v2.3.3.0 by Digital Flow Innovations LLP

Download on the Google Play

⇒ What’s .APK / .XAPK file and how to install?

KAZTOKEN mobile

Download

About KAZTOKEN mobile

KAZTOKEN mobile (Package Name: kz.digiflow.kaztokenmobile) is developed by Digital Flow Innovations LLP and the latest version of KAZTOKEN mobile 2.3.3.0 was updated on December 26, 2024. KAZTOKEN mobile is in the category of Tools. You can check all apps from the developer of KAZTOKEN mobile. Currently this app is for free. This app can be downloaded on Android 5.0+ on APKFab or Google Play. All APK/XAPK files on APKFab.com are original and 100% safe with fast download.

KAZTOKEN mobile application allows you to use your KAZTOKEN device (USB token or smart-card) in conjunction wit your mobile device.
How to use:
- Install the app
- Launch it
- Start it
- Install internal TLS certificate (using the link or by clicking on notification) to trusted list - required for the browser to be able to access Websocket service
- Open your browser and use services integrated with KNCA (such as https://egov.kz)
IMPORTANT!
We can not guarantee that your mobile device has the necessary capabilities to interact with USB devices. Usually OTG or Type-C support is sufficient.
The following KAZTOKEN devices are supported:
- classic USB KAZTOKEN device;
- KAZTOKEN micro;
- KAZTOKEN smart-card;
- KAZTOKEN smart-card NFC;
- KAZTOKEN type-C.
To connect KAZTOKEN USB device to your mobile device you can use OTG or Type-C adapter.
To use KAZTOKEN smart-card with your mobile device you can use one of the following methods:
- smart-card reader with micro USB or Type-C connector;
- smart-card reader with classic USB connector in conjunction with OTG or Type-C adapter;
- Bluetooth smart-card reader ACS ACR3901.
KAZTOKEN smart-card NFC can communicate with NFC enabled devices directly.
Does trusting TLS certificate weakens security of mobile device?
We did our best to minimize risks:
- certificates are generated on each device during the first launch of the service, we do not use pregenerated certificates;
- we generate two certificates: CA and service;
- we do not store CA private key, it's used only once to issue service certificate;
- we recommend to trust the CA certificate.