Digital Signature Certificates for e-Tendering: Class, Type and Common Errors

A digital signature certificate is how you sign a bid on an e-procurement portal. It is also the single credential in the whole process that must never leave the hands of the person it names, and the one most often handed to somebody else for convenience.

What a DSC is

A DSC is a certificate issued by a licensed Certifying Authority under the Information Technology Act, binding a cryptographic key pair to a named individual or organisation. Signing a document with it produces a signature that can be verified as coming from that certificate.

For e-tendering it is normally issued on a hardware cryptographic token, which is what you plug into the machine when signing.

Which class and type

E-procurement portals generally require a Class 3 certificate, which involves in-person or equivalent verification of the applicant's identity.

Two types matter:

• A signing certificate, used to sign the bid
• An encryption certificate, used where the portal encrypts the financial bid so it cannot be opened before the scheduled opening time

Many portals require both. Some tenders specify the type explicitly. Check the portal's requirement before buying, because a signing-only certificate on a portal that needs both means a second purchase and a lost week.

The certificate should be in the name of the authorised signatory of the bidding entity, and organisational details on the certificate should match the entity's records. See who may sign a bid.

The rule that has no exceptions

A DSC belongs to the individual it names and must not be shared. Not with a colleague, not with a consultant, not with a service provider, not with a platform.

Anything signed with your certificate is signed by you, legally and practically. Handing the token to someone else means every declaration they submit is your declaration, including the ones in the affidavits and undertakings whose consequences reach into debarment.

Avsar never asks for a DSC and never submits a bid. Submission happens on the government portal, under the bidder's own signature. See the FAQ.

Setting it up before you need it

The mechanical failures on submission day are almost all avoidable, and almost all of them are setup:

• Install the CA's drivers and the token utility on the machine you will submit from
• Install the portal's own signing component, which is often a separate download
• Check the browser, since portal signing components have specific browser and Java requirements that lag current versions
• Register the DSC on the portal and map it to your login. A valid certificate that is not mapped will not sign
• Do a test signature on the portal well before the closing date

Do this once, on one machine, and use that machine for submissions.

The errors that appear on closing day

"Certificate not registered" or "DSC mismatch." The certificate on the token is not the one mapped to the login. Common after renewal, when a new certificate is installed but never re-mapped.

Token not detected. Driver, USB port or a machine that has changed since the last submission.

Expired certificate. Certificates are issued for a validity period, usually a small number of years. An expired certificate cannot sign anything.

Signatory has changed. The person named on the certificate has left, and the bid needs the current authorised signatory. This requires a new certificate, not a workaround.

Renewal

Set a reminder well before expiry, because renewal involves the same verification as issue and takes days, not hours. Then re-register the renewed certificate on every portal you bid through, which is the step that gets forgotten.

A firm that bids on several portals should keep a list of them for exactly this reason.

In the wider process

The DSC is the mechanical link between your documents and a valid submission. Submitting an e-tender covers the last 48 hours in full, and documents required for a government tender covers what you will be signing.