DSC Application, Renewal or Revocation Stuck? Fix It Fast

Who this guide is for

This guide is for anyone in India whose Digital Signature Certificate journey has hit a wall. That includes:

• Company directors and LLP partners who need a DSC to file incorporation forms (SPICe+, FiLLiP) or annual compliance forms (AOC-4, MGT-7) on the MCA21 portal.
• GST-registered businesses and their authorised signatories who must sign GSTR returns, amendments, or appeals with a DSC—and whose filing deadline is approaching.
• Income tax filers (companies, LLPs, audit-mandatory firms) who need a DSC registered on the income tax e-filing portal to submit their ITR verification.
• Government procurement participants—vendors on GeM (Government e-Marketplace) and bidders on e-tender portals—for whom a valid Class 3 DSC is mandatory to submit bids.
• DGFT and customs filers who sign ICEGATE and DGFT applications electronically.
• Anyone who needs to revoke a DSC because a USB token was lost, stolen, or the authorised signatory has changed, and the revocation request is not moving.

Note: As of the current CCA guidelines, Class 3 DSC is the only class being issued in India. Class 1 and Class 2 certificates are no longer issued. If you hold a legacy Class 2 certificate that has expired, you need a fresh Class 3 DSC—not a renewal of the old certificate.

What you can do this weekend

Friday evening

Gather the information you need before any offices open. Log in to your CA's portal and note your application reference number and the current status shown. Take a screenshot. Also note the exact wording of any error or rejection reason—this is your evidence. Check whether video KYC is shown as completed or pending: most CA portals display this clearly in the application tracker.

If you do not yet have an application, visit cca.gov.in/licensed_ca.html to confirm you are using a licensed CA. There are over 20 licensed CAs in India including eMudhra, (n)Code Solutions, Capricorn, Protean, XtraTrust, Vsign, and others. Use only a CA on this official list.

Saturday

Address the most common blockers:

• Video KYC pending: Most CAs schedule video verification on business days, but some operate on Saturdays. Check your CA's site for a "reschedule video verification" link and book the earliest slot. Prepare by keeping your original Aadhaar card or PAN card visible and ensuring good lighting and a stable internet connection. The video session typically takes 5 to 10 minutes.
• Name mismatch: The name on your DSC application must match your PAN card exactly—including middle name or initial. If there is a discrepancy, log in to the CA portal and upload a corrected document set. Many CAs allow re-submission without cancelling the application.
• Token or driver issue: If your certificate has been issued but the portal is not detecting it, install or reinstall the USB token driver from the CA's download page. Plug the token directly into a laptop USB port (avoid hubs). Install the correct version of the emsigner utility—each portal (Income Tax, GST, MCA) provides its own download link. Disable popup blockers for the portal domain.
• Payment not confirmed: If your payment was debited but the portal still shows "pending payment," take a screenshot of the bank transaction and email or WhatsApp it to your CA's support team with your application reference number.

Sunday

If the issue is not resolved by self-help, draft a formal written complaint to the CA's support email or grievance email (usually listed on their website). Use the complaint template in this guide. Keep the email brief, factual, and include your application reference number, the date you applied, the issue, what you have already tried, and your deadline. Send it Sunday night so it lands first thing on Monday morning. Also prepare your CPGRAMS login at pgportal.gov.in in case you need to escalate to CCA on Monday.

Documents and evidence checklist

Step-by-step action plan

Step 1: Check your application status on the CA portal

Log in to your Certifying Authority's customer portal. Most licensed CAs (eMudhra, XtraTrust, Protean, etc.) provide an application tracker. Note the status label: "Application Received", "Video KYC Pending", "Under Processing", "Issued", or a rejection reason. If it says "Issued" but you cannot use the DSC on a portal, skip to Step 4.

Step 2: Complete or redo video KYC (Live Video Verification)

Video KYC is currently the standard verification method for all DSC applications in India, both fresh and renewal. If your video session failed—due to poor lighting, document not visible, or connectivity—you will need to reschedule. Your CA will send a new link or allow booking from the portal. During the session:

• Sit in a well-lit room with your face clearly visible.
• Keep your original PAN card or Aadhaar card ready to show the camera.
• The verification officer will ask you to state your name and the purpose of the DSC.
• The entire session takes about 5 to 10 minutes.

If Aadhaar-based eKYC is offered by your CA, that route is faster—it uses OTP-based Aadhaar authentication and eliminates the scheduled video session for individual applicants.

Step 3: Correct document or name mismatches

The single most common delay cause is a mismatch between the name on the application and the name on supporting documents. The name must appear exactly as on your PAN card. If your PAN says "RAMESH KUMAR SHARMA", do not write "Ramesh K. Sharma" on the form. Re-upload the corrected documents through the CA portal. If the portal does not allow re-upload, call the CA's helpdesk and ask them to unlock the application for document resubmission.

Step 4: Register the issued DSC on the relevant portal

Getting the DSC from the CA is only half the job. You must register it on each portal you intend to use it with:

• Income Tax (e-filing portal): Log in at incometax.gov.in, go to Profile > Register DSC, download and run the emsigner utility, insert your USB token, and follow the on-screen steps. The DSC must match the PAN of the taxpayer account.
• GST portal: Log in at gst.gov.in, go to My Profile > Register / Update DSC, install the emsigner, and register. The DSC must match the authorised signatory's PAN on that GSTIN.
• MCA21 portal: MCA has its own emsigner utility. Download it from the MCA portal's help section, install, and attach the DSC during form submission rather than a separate registration step.
• GeM / e-tender portals: Each portal has its own DSC registration process—follow the portal-specific DSC guide. Most require you to install the portal's signing utility and test it before submitting a live bid.

If the portal still does not detect the DSC after installing the emsigner utility, try: a different browser, a direct USB port (not a hub), updating Java, disabling antivirus temporarily for the signing step, and checking that your token PIN is correct (tokens typically lock after several wrong attempts).

Step 5: For renewal — start at least 30 days early

Renewal is essentially a fresh application. You will go through the same video KYC process and pay the CA's current renewal fee. Your token may be reusable if it is compatible. Begin the process at least 30 days before the existing DSC expires to avoid any gap in your ability to sign filings. If your DSC expires mid-filing, you will need to complete the renewal, download the new certificate to your token, and then re-sign and resubmit the entire form.

Step 6: For revocation — act immediately if your token is lost

If your USB token is lost or stolen, or if the authorised signatory has changed (e.g., a director has resigned), revoke the DSC as soon as possible. Delay creates a window for misuse of your digital identity. To revoke:

1. Log in to your CA's portal (or request the CA to initiate revocation if you cannot log in).
2. Navigate to the revocation section and select the reason (loss, theft, key compromise, change of signatory).
3. Download the revocation request form, fill it, and upload the signed version.
4. The CA will verify the request and update the Certificate Revocation List (CRL). You will receive a confirmation.
5. After revocation, apply for a fresh DSC with a new USB token.

If the CA is not processing your revocation request and you are concerned about misuse, escalate urgently to the CA's grievance officer and in parallel raise the issue with CCA.

Step 7: Contact the CA's grievance or support desk

If the above steps do not clear the blockage, contact the CA directly—by email, phone, and if available, a formal grievance or complaint form on their website. Quote your application reference number and state the issue clearly. Ask for a response within a specific number of business days (three to five is reasonable). Keep a copy of every communication.

For guidance on your broader compliance obligations, see our guides on GST registration and filing GST returns. If you are dealing with a government grievance, the guide on using CPGRAMS is also useful.

Escalation ladder

Copy-paste complaint template

Replace the text in square brackets with your own details before sending.

When RTI can help

The Controller of Certifying Authorities (CCA) is a statutory authority under the Ministry of Electronics and Information Technology (MeitY) and is a public authority under the Right to Information Act, 2005. This means you can file an RTI application to CCA to obtain:

• Information about the standards, service-level obligations, and compliance requirements that licensed CAs must meet under the IT Act, 2000 and CCA regulations.
• Whether a specific CA has been found non-compliant, penalised, or has had its licence suspended or revoked by CCA.
• The status of any complaint or grievance you have already filed with CCA—if CCA has not responded to your CPGRAMS grievance, an RTI can ask for the record of action taken.
• Policy decisions: for example, if CCA issued any advisory or circular about video KYC requirements that your CA may be violating.

You can file an RTI online at rtionline.gov.in addressed to the Central Public Information Officer (CPIO), Controller of Certifying Authorities, MeitY. If unsatisfied with the reply, you can file a First Appeal under Section 19 within 30 days. For a deeper understanding of how to use RTI as a citizen tool, see The RTI Playbook and the broader Practical Guides hub.

When RTI will not help

Certifying Authorities themselves—eMudhra, (n)Code Solutions, Capricorn, XtraTrust, Protean, Vsign, and others—are private companies. The RTI Act does not apply to private entities. You cannot file an RTI to get your individual application processed or to demand documents from a private CA.

For complaints against a private CA, your remedies are:

• CA grievance officer (contractual obligation the CA has to its customers).
• CCA as the regulator — CCA can take action against a CA for service violations.
• Consumer court — CAs are service providers under the Consumer Protection Act. If a delay caused financial loss, you can file in your District Consumer Disputes Redressal Forum.
• CPGRAMS — file via pgportal.gov.in under MeitY if CCA is the appropriate authority to regulate the matter.

Also note: RTI cannot force any authority to meet a specific deadline for your individual case. It is a tool for information and accountability, not emergency processing.

Common mistakes to avoid

• Applying too close to the deadline. DSC issuance normally takes one to two working days, but document issues or a failed video KYC can extend this. Always start at least two weeks before a critical filing deadline.
• Using an unlicensed or unverified DSC vendor. Many resellers operate online. Always verify the CA you are buying from is listed on cca.gov.in/licensed_ca.html. Unlicensed DSCs are not valid for government portals.
• Assuming renewal carries over automatically. A DSC does not auto-renew. The certificate simply stops working after expiry. You must initiate renewal yourself, go through video KYC again, and download the new certificate to your token before the old one expires.
• Forgetting to register the DSC on the portal after issuance. Getting the certificate from the CA is not enough. You must register it on each portal (Income Tax, GST, MCA) separately, using that portal's own emsigner utility.
• Locking the token PIN with repeated wrong attempts. USB tokens typically lock permanently (or require a complex reset) after a certain number of wrong PIN entries. If you forget your PIN, contact the CA before guessing repeatedly.
• Not revoking a lost token immediately. If your USB token is lost or stolen, every day you wait is a day someone could potentially use your digital identity to sign filings on your behalf. Revoke first, apply fresh second.
• Using the wrong emsigner version. Each portal (Income Tax, GST, MCA) distributes its own version of the emsigner utility. Using the wrong version—or an outdated version—will cause detection failures even with a perfectly valid DSC.
• Not updating browser and Java settings. Older browser versions or incorrectly configured Java settings (especially the Java security exception site list) are behind many "DSC not detected" complaints. Keep browsers updated and add the portal URL to Java's exception list.
• Confusing cloud DSC with token-based DSC. Some CAs now offer cloud-based or mobile-based DSC signing (especially for GST). This eliminates the USB token but works differently from hardware token DSCs. Confirm which type is accepted by your specific portal before purchasing.