Downloads

Application forms, USB token drivers, CCA root chain certificates and utilities for every Certifying Authority we supply. All free to download.

Getting your certificate onto a token

The download utility is the application that pulls your issued certificate from the Certifying Authority and writes it onto your USB token. Each CA uses its own, and they are not interchangeable — a Vsign utility will not download an eMudhra certificate.

Whichever CA issued your certificate, the order is the same:

1. Install the driver for your USB token from the USB Token Drivers sections below, and plug the token in.
2. Run the download utility for your Certifying Authority. The Vsign DSC download utility, version 3.5, is below — version 3.4 is there too if you need to fall back. There is a step-by-step guide to installing and using it if you would rather follow it screen by screen.
3. Enter the reference number and credentials issued when your certificate was approved.

If the utility cannot see your token, it is almost always a missing driver.

The driver depends on your token, not your Certifying Authority

This trips people up constantly. If you are searching for an “eMudhra token driver” or a “Vsign driver”, what you actually need is the driver for the physical token you were given — ePass, ProxKey, TrustKey, Gemalto, StarKey or U-Key. The Certifying Authority that issued your certificate does not change which driver you need.

Look at the token itself, or its packaging, for the make, then take the matching driver from the USB Token Drivers section below. They are the same drivers whether your certificate came from Vsign, eMudhra, (n)Code or Sify. If you cannot identify your token, call us and we will work it out from the token’s appearance or your order.

FIPS 140-2 or FIPS 140-3? Try the other one

Token makers have moved their hardware from FIPS 140-2 to the newer FIPS 140-3 standard, and the two generations need different drivers even when the token is the same make and looks identical. HyperPKI HYP2003, mToken CryptoID, Precision InnaIT and Watchdata ProxKey all now ship in both generations.

There is no reliable way to tell them apart by sight, so the practical rule is simple: if the driver you installed does not detect your token, uninstall it and install the same make from the other section. A token bought recently is more likely to be FIPS 140-3; one that has been in a drawer since 2023 is almost certainly FIPS 140-2.

• USB Token Drivers (FIPS 140-3) — newer tokens.
• USB Token Drivers (Vsign Repository) — FIPS 140-2 tokens, plus ePass 2003, SafeNet and the previous ProxKey build.

Help for your Certifying Authority

Each authority runs its own application, verification and download process.

• Vsign — the DSC download utility is below, and verification is now a face scan on your phone rather than a recorded video.
• ProdigiSign — complete eKYC and track your DSC status , including video verification.
• Pantasign — video verification and eKYC , plus the PantaCharge utility.

If you are still choosing, the documents and process guide covers what an application needs.

Forms, drivers and root certificates