SDK · API

Digital signature crypto modules based on O‘zMSt

Ready-made server and client modules for digital signatures and encryption: server modules, a browser module with no installation, mobile libraries and libraries for 1C and Windows. The core modules are certified to the national standard.

How it fits together

Where each module runs

A signature is made on the user side, verified on the server, and the trust infrastructure confirms certificate status and timestamps. Modules can be used separately.

Pick a scenario to see its path on the diagram

Your application

  • Web systemWebsite, portal, back office
  • MobileAndroid · iOS
  • 1C and WindowsAccounting and desktop systems

Client module

  • EMICRYPTER · ISIGNERBrowser and desktop
  • Mobile librariesAndroid · iOS
  • ISIGNERX · DLL1C · Windows · .NET

Your server

  • ICRYPTERCLISigning, verification, certificates
  • ISIGNERCLISignature creation and checks
  • ICIPHERCLIData encryption

Trust infrastructure

  • OCSPCertificate status
  • Verify APIVerification and timestamp
  • KRCKey and certificate registration
  1. EMICRYPTER

    The page loads the module in the browser, nothing to install.

  2. ISIGNER

    Or the document is signed through the desktop application, including with a token.

  3. ISIGNERCLI

    The server receives the signature and verifies it together with the certificate.

  4. Verify API

    If needed, the signature is returned with a timestamp.

Which one to choose

Module comparison by capability

Marked is what the module includes according to the documentation. If unsure, describe your task and we will pick a set.

ModuleRuns onSigningSignature verificationCertificate issuanceKey generationEncryptionBest for
ICRYPTERCLIServerYesYesYesYesYesFull set for KRCs and the server side of systems
ISIGNERCLIServerYesYesNoNoNoOnly signing and signature verification are needed
ICIPHERCLIServerNoNoNoNoYesFile and channel encryption, protected storage
EMICRYPTERBrowserYesNoNoYesYesWeb application with no software to install for users
ISIGNERDesktopYesNoNoYesNoSigning from a web system and working with tokens
Mobile librariesAndroid · iOSYesNoNoYesYesSigning and keys inside a mobile app
ISIGNERX · LIBISIGNER.DLL1C · Windows · .NETYesNoNoNoNoSigning in 1C and Windows applications

Capabilities

  • Server modules

    Cross-platform modules for the server side of information systems and key registration centers. Licensed for your servers.

  • Browser module

    EMICRYPTER runs in the browser without installation, including mobile browsers.

  • Mobile and desktop libraries

    Android, iOS, Windows, .NET and 1C: signatures, keys, encryption.

  • Certification

    ICRYPTERCLI, ICIPHERCLI and EMICRYPTER are certified to the national standard.

Module lineup

  • ICRYPTERCLI

    Server module · certified

    A cross-platform module for the server side of information systems and KRCs: generating key certificates, verifying certificates and signatures, generating key pairs to protect data between server and client, encrypting and decrypting text data. License-protected: runs only on permitted servers for a set term, with a key generation limit.

    Used in: UNICON.UZ KRC, INFINBANK KRC

  • ISIGNERCLI

    Server module

    A lightweight version of ICRYPTERCLI: only creating and verifying digital signatures, without certificate issuance or encryption. A Java version is available as the LIBISIGNER library.

    Used in: State Customs Committee, Supreme Court, GCP, EISVO; Java version: Prosecutor’s Office

  • ICIPHERCLI

    Server module · certified

    Encrypts and decrypts binary data of unlimited size: protecting the channel between server and client and secure data storage. Licensed for your servers.

    Used in: IJRO system

  • EMICRYPTER

    Browser module · certified

    For web applications: needs no installation, loads in the browser together with the page, and works in mobile browsers too. Data encryption and decryption, digital signatures, key pair generation to protect data between server and client.

    Used in: IJRO system

  • ISIGNER

    Client application

    Installed on the user’s computer and works with the browser: creating signatures, generating a key pair and requesting key registration at the KRC, producing a QR code to pass the private key to the mobile app in encrypted form. Works with E-kalit, IKEY and ePass tokens.

    Used in: UNICON.UZ and INFINBANK KRC, State Customs Committee, Prosecutor’s Office, GCP, EISVO

  • Mobile libraries

    Android · iOS

    Creating signatures, generating a key pair, importing and saving a private key from a QR code, showing stored certificates, encrypting and decrypting data.

    Used in: INFINBANK mobile app

  • ISIGNERX and LIBISIGNER.DLL

    1C · Windows · .NET

    ISIGNERX embeds into 1C systems: creating signatures and showing certificates. LIBISIGNER.DLL is a library for Windows applications, with a .NET version.

Who it is for

O‘zMStBuilt on O‘zMSt algorithms

  • Developers of web and mobile services that need digital signatures
  • Companies building their own document workflow systems and key registration centers
  • Integrators deploying digital signatures for their customers

Frequently asked questions

How are the modules protected against unauthorized use?

Server modules are license-protected: they run only on the client’s permitted servers for a set term. In the key registration center the number of key generations is also limited.

Can a key be moved from the phone to the computer?

No. QR import works one way: ISIGNER on the computer shows the code, and the mobile app scans it and stores the key.

How do we connect the module to a web application?

A web application uses the EMICRYPTER browser module (no installation) or the ISIGNER client application that works with the browser. We pick the option for your project and help with integration.

Let’s talk

Need digital signatures or a secure system?

Tell us about the task: platform, scale, timeline. We will choose the right solution and show it working.

Or contact us directly

Your data is used only to reply to your request.