Home › Registrations › Digital Signature Certificate (DSC)
DIGITAL SIGNATURE CERTIFICATE · CLASS 3 · E-FILING SUPPORT
Get practical guidance for a Digital Signature Certificate used in MCA filings, business e-tendering and other supported portals. Understand the right certificate, licensed issuing authorities, identity verification and secure usage.
✓ Certificate selection guidance · ✓ CA application checklist · ✓ MCA DSC association support
CLASS 3 DSC · LICENSED CERTIFYING AUTHORITIES
Match the DSC type to the portal and intended use.
Follow the licensed CA’s KYC or video-verification route.
Use the applicable token, software and PIN safely.
DSC SUPPORT · APPLICATION · MCA ASSOCIATION
Tell us whether you need a new DSC, renewal/re-issue guidance, or assistance associating an existing certificate with the MCA portal. We can help you understand the appropriate next steps.
Independent procedural guidance. Digital Signature Certificates are issued by licensed Certifying Authorities, not by Online Tax Filings.
Provide your contact details and the type of DSC support required. Never enter OTPs, token passwords/PINs, private keys, Aadhaar numbers or other sensitive credentials here.
✓ Licensed Certifying Authorities issue DSCs under the Indian PKI framework
✓ Class 3 DSC verification and secure key-storage requirements depend on CCA policy
✓ MCA and tender portals may have their own DSC association or signing steps
A PRACTICAL GUIDE TO DIGITAL SIGNATURE CERTIFICATES
This guide explains how DSCs are issued through licensed Certifying Authorities, how identity verification and secure signing work, what business users should check before applying, and when DSC association is needed on MCA or other platforms.
A Digital Signature Certificate (DSC) is an electronic credential that links a verified subscriber identity with a public key. Under India’s digital-signature framework, it supports cryptographic signing of electronic records and helps recipients verify that signed material has not been altered.
A DSC is not a scanned handwritten signature or a picture pasted into a PDF. It is issued by a licensed Certifying Authority (CA) and used through compatible software, secure keys and supported portals.
A CA verifies the subscriber before issuing a certificate.
A cryptographic signature can reveal later changes to signed content.
The receiving portal determines acceptable signing methods.
The subscriber must protect signing credentials and hardware.
Online Tax Filings can assist with application readiness and portal use; only a licensed CA issues the actual DSC.
Online Tax Filings provides independent assistance to entrepreneurs, directors, LLP partners and authorised business users who need digital-signature guidance. We help clarify certificate types, paperwork, identity-verification steps and portal-specific signing requirements.
Our support can include reviewing applicant categories, explaining Certifying Authority procedures, and helping a business user understand MCA association steps or typical signing errors after issuance.
Check Class 3 and intended signing application.
Review identity and organisation particulars.
Understand token and portal readiness.
Identify likely association or configuration problems.
We do not act as the Controller of Certifying Authorities or independently issue certificates.
Company directors, authorised signatories, designated LLP partners, tax professionals, tender participants and other persons may require a DSC when a specific electronic filing system mandates it.
A business itself may authorise a signatory, but the relevant portal’s user role and applicable certificate identity fields still need to match. Not every filing or applicant requires the same certificate.
Corporate electronic forms and authorised filings.
Designated partner and other eligible MCA submissions.
Certain e-procurement and bidding workflows.
Where their role permits regulated e-filing.
Confirm the precise portal and filing before selecting a certificate; use of eSign may be supported separately on some services.
The Controller of Certifying Authorities (CCA) describes certificate assurance classes and corresponding verification and key-storage requirements. Class 3 is a higher-assurance certificate used for many business-oriented digital-signing workflows.
The same Class 3 assurance framework applies across licensed CAs. However, a certificate also needs the required subscriber details and suitable purpose for the platform where it will be used.
Class reflects certificate-verification requirements.
Signing and encryption are different functions.
Individual and organisational details may matter.
Always confirm target-portal requirements.
Higher-assurance Class 3 is not automatically valid for every filing if mandatory data fields or certificate-purpose requirements are missing.
DSCs for end users are issued through Certifying Authorities licensed by the CCA. Applicants should use a CA or its authorised channel and verify the relevant issuing details through official CCA resources.
A Registration Authority may assist applicants with forms, supporting records or cryptographic devices, but the licensed CA remains responsible for verification and issuance under the applicable framework.
Online Tax Filings is an independent consultant; never imply it is the certificate-issuing CA.
DSC application pathways can differ depending on whether the subscriber signs in an individual capacity or as a person associated with an organisation. The certificate may include PAN, organisational identifiers or other fields relevant to the intended service.
Prepare details that accurately match the subscriber and the filing platform. If a director or professional uses MCA services, the business-user profile and mapped identifiers must be considered separately from certificate issuance.
Personal identity and matching contact information.
Identity fields aligned with the MCA account.
Professional identifiers where the portal requires them.
Organisation and authorisation records when applicable.
A company name on a document does not make every certificate an organisation-linked DSC.
Supporting information varies by the chosen CA, certificate type and verification path. Applicants may be asked for an identity document, address details, contact information, business affiliation or authorisation where applicable.
CCA guidance recognises paper-based verification, Aadhaar eKYC and other approved KYC approaches. Always rely on the currently authorised CA’s checklist instead of uploading sensitive identity records into a general public enquiry form.
Do not send Aadhaar copies, PAN copies, OTPs, token PINs or private-key files via general website enquiry.
Licensed CAs follow assurance-appropriate subscriber verification requirements. For certain Class 3 pathways, CCA policy provides for a physical verification or video verification process; the exact permitted route depends on the CA and applicable identity-validation method.
Applicants should understand that a verification call is not the same as sharing token PINs. A legitimate verification procedure must be completed through the CA or its authorised flow.
Use only the CA-supported identity-validation route.
Complete the authorised workflow where required.
Check spellings, affiliations and subscriber category.
Never disclose signing PINs, passwords or OTPs.
Verification policies and accepted methods can change; current instructions from the licensed CA take precedence.
For Class 3 certificates, CCA describes secure hardware cryptographic device requirements for private-key generation and storage. The token or cryptographic device should be obtained and used through the applicable CA-supported process.
Signing software may also require a compatible token driver or bridge application. Token devices should remain under the subscriber’s custody and their PINs must never be shared with an agent or an outside person.
Keep signing keys protected within approved devices.
Confirm the CA-supported hardware and driver.
Only the authorised subscriber should control the PIN.
Follow CA guidance; never export signing private keys.
Avoid using unknown drivers or third-party tools that claim to bypass device security.
On the Ministry of Corporate Affairs (MCA) portal, signing and submitting certain electronic forms can require associating a valid DSC with the appropriate user profile. Association maps a DSC to a portal account; this is separate from obtaining the DSC itself.
MCA guidance explains the importance of the right business-user role, matching identifiers and compatible desktop utility when associating a certificate. A profile mismatch can cause the portal to report an association problem even if the DSC itself is valid.
MCA interface labels and client-utility requirements may change. Follow the live MCA portal and latest help documents.
Many e-procurement systems use digital certificates to authenticate authorised bidders or sign uploaded bid documents. Portal acceptance may depend on certificate class, subscriber details, organisation affiliation and sign/encryption requirements.
Before obtaining a DSC for a tender, check the exact tender portal’s published technical prerequisites and supported token/drivers. Tender-specific signing and encryption requirements should not be assumed from MCA requirements.
Check the correct e-procurement platform.
Ensure bidder and representative information matches.
Confirm signing versus encryption needs.
Use supported browser, drivers and utilities.
A valid DSC alone does not guarantee eligibility to participate in a specific government tender.
A signing certificate is intended to help verify the origin and integrity of an electronic signature. Encryption certificates and their key-management practices serve a different function: protecting content from unauthorised reading.
Certain platforms need one function, while other workflows may specify both. Select certificate purposes based on the actual transaction rather than ordering an unspecified “all-purpose DSC”.
The CCA advises that an individual’s signing and encryption certificates should be distinct.
A DSC has a validity period established at issuance. Users should check the certificate’s actual expiry date in their CA portal or certificate details before an MCA filing, tender submission or other time-sensitive transaction.
If a certificate expires, is revoked or needs changes, the subscriber should follow the licensed CA’s renewal or re-issuance procedure and update portal association when necessary. Re-issuance is not automatically the same as editing an existing certificate.
Inspect certificate details before a planned filing.
Follow the CA’s current applicant process.
Recheck MCA/tender associations when certificates change.
Use CA support if credentials or devices are compromised.
No fixed processing or delivery timeframe is promised; CA verification and portal behaviour determine each case.
If a token is lost, a signing device is compromised or private-key access may have been exposed, the certificate holder should promptly contact the issuing CA using its official support channel and follow the applicable revocation or re-issue process.
Do not ask an outside person to retrieve a token PIN by unsafe software or share remote access to a device containing a private signing key. Document any affected pending filings and obtain advice for secure restoration.
Security concerns should be escalated to the issuing CA; a certificate image or scanned signature is not a substitute for a lost private key.
DSC failures can arise from expired certificates, inconsistent subscriber information, absent token drivers, unsupported operating environments, incorrectly associated user identifiers or a wrong certificate purpose for the target portal.
The safest diagnostic approach is to isolate the issue: check certificate validity and recognised hardware first, then profile mapping, browser/bridge requirements and portal-specific error guidance.
Verify subscriber name, PAN or relevant account IDs.
Check drivers and supported hardware.
Verify MCA profile role and mapping.
Consult the target portal’s own supported setup.
Never share passwords, one-time passcodes or token PINs with a website support representative.
A DSC is used to create cryptographic digital signatures accepted by supported portals, such as certain MCA filings and electronic procurement processes. Usage depends on the platform.
No. DSCs are issued by Certifying Authorities licensed by the Controller of Certifying Authorities. Online Tax Filings offers independent application and usage guidance.
Class 3 is a higher-assurance certificate category under India PKI with specified identity-verification and secure key-storage controls. Confirm the class required by your portal.
Class 3 certificates are commonly used for qualifying business filings, but the identity fields, certificate purpose and MCA business-user association must also meet the portal’s requirements.
They are different signing mechanisms. A hardware-token DSC typically uses a subscriber certificate, while eSign is a separate supported electronic-signature service with its own authentication workflow.
The licensed CA determines the applicable identity, address and organisation documents or eKYC route. Use its current checklist rather than assuming all applicants have identical requirements.
For Class 3 certificates, CCA describes private-key generation and storage in secure hardware cryptographic devices. Some other electronic-signature services follow different mechanisms.
Certificates bind to subscriber identities and approved roles. Each authorised signer should follow the requirements relevant to that person and the target filing platform.
Common causes include using the wrong MCA user role, identifier mismatch or associating a certificate to another profile. Follow MCA V3 instructions and verify profile details.
A current valid certificate is ordinarily required to create new accepted signatures. Review the issuing CA’s renewal or re-issuance procedure and the target portal’s requirements.
Contact the issuing CA through an official channel for security, revocation and re-issuance guidance. Do not disclose PINs or private keys to intermediaries.
Not necessarily. Portals may differ in subscriber fields, signing/encryption needs, certificate class and technical compatibility. Verify each platform before applying.
Use official CCA and Ministry of Corporate Affairs sources for authoritative information about licensed Certifying Authorities, DSC verification standards, eSign and portal association. Review the current versions of guidance when applying.
These links are independent government references. Online Tax Filings is not affiliated with CCA, MCA or any licensed Certifying Authority.
If you need support choosing a certificate for company filings, understanding CA identity verification, preparing an organisation application or resolving MCA DSC association, Online Tax Filings can help you plan the appropriate steps.
Use the enquiry form immediately below the hero. Tell us the intended portal, applicant category and general assistance required; never include passwords, tokens, OTPs or complete identity-document details in the form.
Actual DSC approval, issuance and certificate policy remain with the chosen licensed Certifying Authority; acceptance of signatures depends on the destination portal.
DSC APPLICATION GUIDANCE
Understand Class 3, CA verification, secure tokens, certificate purpose and MCA V3 association before you sign important business forms.
Independent DSC application guidance, tax and business compliance assistance for entrepreneurs, companies and professionals across India.
Support with certificate selection, MCA V3 association and secure digital-signing readiness.
© 2026 Online Tax Filings. All rights reserved.
