Class III DSC

Class III DSC is the highest trust level of Digital Signature Certificate in India's PKI framework, issued only after in-person or video-based identity verification of the applicant by a licensed Certifying Authority, and is the universal requirement for submitting bids on all Indian government e-procurement portals.

What is a Class III DSC?

India's PKI (Public Key Infrastructure) framework under the IT Act classifies Digital Signature Certificates into levels based on the identity verification rigor applied during issuance. Class III DSC requires the most stringent verification: the applicant (the authorised signatory or individual in whose name the DSC is issued) must either appear in person at a Registration Authority or complete a video-based KYC process with PAN and Aadhaar verification.

This in-person or video verification ensures that a Class III DSC uniquely and reliably identifies the holder, making it legally sufficient for high-stakes transactions such as government tender submission. All Indian government e-procurement portals, CPPP, GePNIC, IREPS, NHAI, CPWD eTendering Portal, and state portals, require Class III DSC exclusively. Class I or Class II certificates are not accepted for e-tendering.

Class III DSCs come in two variants: signing-only (for document authentication) and combo (signing plus encryption). Government e-tender portals require the combo variant because bid documents must be both encrypted (so technical bids cannot be read before opening) and signed (to verify authorship). The DSC is stored on a physical e-Token hardware device and protected by a PIN.

Why Class III DSC matters for Indian government suppliers

Every supplier participating in e-tenders must hold a valid Class III DSC (combo type). This is a non-negotiable, day-one operational requirement. Attempting to submit a bid with an expired, incorrect class, or malfunctioning DSC results in automatic portal rejection. Companies should budget for DSC procurement, renewal, and backup tokens as part of their tendering operations.

Example

A manufacturer's accounts manager, designated as the authorised signatory for tender submission, visits an eMudhra Registration Authority to apply for a Class III DSC. He presents his PAN card, Aadhaar card, company authorisation letter, and a passport photo. The RA verifies his identity in person and issues a Class III combo DSC on a USB e-Token, valid for 2 years. The manager configures this DSC on the company laptop used for bid submission, tests it on the CPPP portal's DSC check utility, and successfully submits bids on CPPP, the Haryana GePNIC portal, and IREPS using the same token.

Frequently Asked Questions

What is the difference between Class III signing DSC and Class III combo DSC for tenders?

A Class III signing DSC only digitally signs documents to authenticate authorship. A Class III combo DSC both signs and encrypts documents. Government e-procurement portals require combo because bids must be encrypted so technical evaluators cannot see financial bids until the financial opening date. Suppliers must ensure they purchase the combo (signing + encryption) variant.

Which Certifying Authorities are authorised to issue Class III DSC in India?

Authorised CAs licensed by the Controller of Certifying Authorities (CCA) include eMudhra, Sify SafeScrypt, nCode Solutions (GNFC), Capricorn CA, CDAC, and a few others. All are accepted on government e-procurement portals. The CA choice does not affect portal compatibility, only cost and service convenience.

Can a Class III DSC issued in one person's name be used for another person's submissions?

No. A DSC is tied to the specific individual whose identity was verified during issuance. Using another person's DSC to sign and submit a bid is illegal under the IT Act and constitutes misrepresentation in the tender process. Each authorised signatory must hold their own DSC.

What should I do if my Class III DSC fails on bid submission day?

First, test on an alternative computer; some failures are machine-specific due to browser settings or Java issues. Second, use the backup DSC if one was pre-configured. Third, contact the portal's helpdesk immediately, most portals have provisions for technical difficulties reported before the deadline. Submit a manual application to the tender authority with documented technical proof if the portal cannot be resolved in time.