A seller account on the Government e-Marketplace can be created without a Digital Signature Certificate. Bidding, accepting a contract and several category approvals cannot be completed without one. Buyers on the buyer side need a certificate too, because evaluation reports and contracts have to be signed.

Both sides of the marketplace need a Class 3 certificate on a hardware token. The difference is only in what they sign.

When a seller needs a DSC

  • Accepting a contract after a bid is awarded
  • Signing the seller agreement and related undertakings
  • Certain OEM and reseller panel actions
  • Bid submission where the category requires a signed bid

Creating the account and browsing listings does not require one, which is why sellers often register first and buy the certificate later. That works until the first bid.

When a buyer department needs one

Government buyers sign evaluation reports, comparative statements and contracts on the portal. Those signatures require a certificate held by the individual officer, in their own name. A department-level certificate is not a substitute.

Which certificate

Class 3, for signing, on a USB token. This is the same certificate that works on CPPP and most state e-tendering portals, so a bidder active on more than one portal does not need separate hardware.

Registration flow

  1. Buy the certificate and load it onto the token.
  2. Install the token driver on the machine you will bid from.
  3. Register on GeM and link the certificate to the account.
  4. Confirm the certificate is visible to the portal.
  5. Test with a live bid rather than waiting for a deadline.

Step 5 is optional and worth doing anyway. A certificate that works in the token utility but not in the browser is a driver or browser-setting problem, and finding that out on deadline day is avoidable.

The mismatch that blocks most sellers

The certificate is issued against a PAN. The GeM seller account is registered against a PAN. If those two are not the same PAN, the portal will not accept the certificate.

This happens most with firms that registered on GeM under the proprietor's PAN and then bought a certificate against the company's PAN, or the reverse. Decide which PAN the account sits under before ordering.

Common issues after registration

Token not detected in the browser. Driver missing, or a browser blocking the signing extension. Install the driver from our downloads page and retry in a fresh session.

Certificate visible but signing fails. Usually an outdated signer package on the portal side. Clear the browser cache and reload the signing component.

Certificate expiring mid-bid-cycle. A bid cycle can run for weeks. If expiry falls inside that window, renew 30 days early rather than after the award.

Shared office machine, shared token. Do not. If two people file from one computer, each needs their own certificate so the signature identifies the person, not the desk.

Cost planning for a bidding firm

A firm bidding regularly needs, at minimum, one certificate and one token. Expect to renew every one to three years. The token is a one time purchase and carries across renewals.

Bid cycles also mean the certificate should never be allowed to lapse. Set the renewal reminder 45 days out, not 7.

Next steps

See DSC for GeM for our offering, or read DSC for e-tendering if you bid on multiple portals. To order, use the live price list or apply online.