Rated 4.9/5 by 312+ Chennai clientsZero penalty record across all filings24-hour response · WhatsApp-first supportOffices: Maduravoyal, Nerkundram & Nolambur (upcoming)15+ years of expert tax & compliance consulting500+ active clients across 243 Chennai areasRated 4.9/5 by 312+ Chennai clientsZero penalty record across all filings24-hour response · WhatsApp-first supportOffices: Maduravoyal, Nerkundram & Nolambur (upcoming)15+ years of expert tax & compliance consulting500+ active clients across 243 Chennai areas
Trusted Class 3 DSC Consultants · Murugesan Salai (PIN 600087)

Class 3 DSC near Murugesan Salai Bus Stop, Murugesan Salai

Serving Murugesan Salai, Valasaravakkam and the wider Valasaravakkam belt — on fixed, transparent fees

Murugesan Salai retail and restaurants units around Murugesan Salai Bus Stop — qualified review, a 7-year workpaper archive and fixed fees from day one. Call 9566-068-468.

4.9
312+ Reviews
15+ Years
Zero Penalties
500+ Clients
Quick Answer

What is the legal recognition of digital signatures in India in Murugesan Salai, Chennai?

Section 5 of the IT Act 2000 grants digital signatures the same legal status as handwritten signatures wherever any law requires a signature. Section 3 prescribes the technical authentication procedure using asymmetric cryptography and hash functions. Section 3A inserted by the IT (Amendment) Act 2008 adds a parallel framework for "electronic signatures" specified in the Second Schedule, which presently includes Aadhaar-based eSign.

Transparent Pricing

Class 3 DSC in Murugesan Salai — Plans & Pricing

Fixed fees · Zero hidden charges · Call 9566-068-468 for a custom quote.

MonthlyAnnualSave 2 Months
Personal DSC
Class 3 DSC 1 Year
Class 3 DSC 1-year video KYC
₹1,500one-time

  • Class 3 DSC 2-Year Validity
  • Video KYC No Physical Visit
  • USB Token Included
  • MCA21 + GST + TRACES + DGFT Portals
  • e-Tender Portal Registration
  • Director + Company DSC Bundle
  • Next-Day KYC Appointment
Most Popular ⭐
Class 3 DSC 2 Years
Class 3 DSC 2-year video KYC
₹2,000one-time

  • Class 3 DSC 2-Year Validity
  • Video KYC No Physical Visit
  • USB Token Included
  • MCA21 + GST + TRACES + DGFT Portals
  • e-Tender Portal Registration
  • Director + Company DSC Bundle
  • Next-Day KYC Appointment
Most Popular ⭐
Class 3 DSC 2 Years + Token
Class 3 DSC 2-year video KYC + Token Device
₹2,500one-time

  • Class 3 DSC 2-Year Validity
  • Video KYC No Physical Visit
  • USB Token Included
  • MCA21 + GST + TRACES + DGFT Portals
  • e-Tender Portal Registration
  • Director + Company DSC Bundle
  • Next-Day KYC Appointment
Director + Company
Company DSC
DSCs + all portal registrations
₹4,500one-time

  • Class 3 DSC 2-Year Validity
  • Video KYC No Physical Visit
  • USB Token Included
  • MCA21 + GST + TRACES + DGFT Portals
  • e-Tender Portal Registration
  • Director + Company DSC Bundle
  • Next-Day KYC Appointment

Swipe to see all plans

Prices exclude GST. For enterprise pricing, call 9566-068-468.

Why FilingPro?

Why Murugesan Salai Clients Choose FilingPro

Expert Class 3 DSC in Murugesan Salai — qualified professionals, 15+ years experience, zero-penalty track record.

Encryption + Signing Pair for Tendering

e-Tendering on CPPP, GeM and State portals frequently requires both signing and encryption certificates. FilingPro supplies the certificate pair on Premium plan with proper key-usage extensions configured per CCA Interoperability Guidelines.

CRL & OCSP Revocation Coverage

On token loss, employment change or key compromise, FilingPro coordinates revocation under Section 38 IT Act with the issuing CA — the certificate is added to the CRL and OCSP responder under the CCA Interoperability Guidelines, protecting Murugesan Salai clients from misuse liability.

USB Token Driver & Browser Setup

EmSigner

Aadhaar eSign Where DSC Is Overkill

Where a Murugesan Salai client only needs to sign one document (loan agreement, NACH mandate, single offer letter), FilingPro recommends Aadhaar eSign under Section 3A IT Act with Schedule II — saves the cost and inventory of a USB token.

WhatsApp-First Issuance

Aadhaar OTP, video selfie and document submission all flow through WhatsApp and the CA's e-KYC portal. Murugesan Salai clients receive the USB token by courier, never visit our or the CA's office.

CCA-Licensed CA Issuance

Every DSC is issued by a Section 24 IT Act licensed Certifying Authority — eMudhra, Protean (NSDL e-Gov), Sify Safescrypt, Capricorn, IDsign or VSign. Murugesan Salai clients receive certificates that pass CRL/OCSP validation on every government portal.

Key Benefits

What Murugesan Salai Clients Get

Every Class 3 DSC engagement delivers measurable, guaranteed outcomes — expert professionals, on time, every time.

TRACES TDS Filing Without Hiccups
Form 24Q, 26Q, 27Q and 27EQ quarterly filings on TRACES require Class 3 DSC for corporate deductors. Murugesan Salai companies file on or before the 31st of the month following the quarter without Section 234E late fee.
Tender Bidding on CPPP and GeM
Government tendering on the Central Public Procurement Portal and GeM requires both encryption and signing certificates. Murugesan Salai bidders on Premium plan receive both, configured for the relevant tender portal upload.
Income Tax e-Verification by DSC
Companies, partnerships and political parties must verify ITRs by DSC under Rule 12 of the Income-tax Rules. Individual taxpayers in Murugesan Salai also use DSC as an alternative to Aadhaar OTP/EVC for high-value or audit-bearing returns.
DGFT IEC and Customs IceGate Filing
Class 3 organisation DSC enables Murugesan Salai exporters and importers to file IEC applications on DGFT and Bills of Entry/Shipping Bills on IceGate without portal-side authentication failure.
Hardware-Secure Private Key
The private key never leaves the FIPS 140-2 USB token under CCA Interoperability Guidelines — even if the host PC is compromised, the Murugesan Salai client's signing key cannot be exfiltrated.
Revocation Protection on Loss
Lost or compromised tokens are revoked under Section 38 IT Act and added to CRL/OCSP within hours — third-party reliance on the certificate stops immediately, protecting Murugesan Salai clients from forged-signature liability.
Comparison

Class 3 Signature DSC vs Class 3 Combo DSC

Why this matters here — Murugesan Salai businesses operate where the cluster of retail, restaurants, healthcare businesses that defines Murugesan Salai's commercial fabric, and served by short connections to Valasaravakkam and Sakthi Nagar Valasaravakkam and onward to central Chennai.

AspectClass 3 Signature DSCClass 3 Combo DSC
What it actually doesDigitally signs and time-stamps a document so the signer cannot repudiate it — sufficient for MCA21 V3, GST, Income-tax, EPFO, TRACES and ROC filings where only authentication is requiredSigns documents AND decrypts encrypted data — mandatory where the portal encrypts payloads back to the holder, chiefly e-Procurement (GeM, CPPP, state e-tender portals) and IP India trademark/patent e-filing
Who typically needs itDirectors, proprietors, tax practitioners and authorised signatories filing statutory returns — the overwhelming majority of Chennai business usersContractors and vendors bidding on government e-tenders, exporters on ICEGATE tender modules, and applicants filing trademarks or patents where bid or filing data is returned encrypted
Token and standardStored on a FIPS 140-2 Level 2 crypto USB token (ePass2003 / mToken / ProxKey); one key pair and one certificate on the deviceSame FIPS 140-2 Level 2 token but holds two certificates — losing or corrupting the token invalidates both the signing and encryption keys together
Validity and renewalIssued for 1, 2 or 3 years; renewed via fresh Aadhaar/PAN e-KYC before expiry — an expired signature certificate silently blocks the next MCA or GST filingSame 1–3 year validity, but on renewal the encryption certificate must also be re-keyed; data encrypted to the old key cannot be decrypted with the new one, so archive access must be planned before renewal
Indicative costApproximately ₹1,200–₹1,500 one-time inclusive of the token, Aadhaar e-KYC and video verification, for a 2-year certificateApproximately ₹1,800–₹2,500 one-time for the same 2-year term, the premium reflecting the additional encryption key pair and its separate CCA-mandated verification
Statutory basisIssued under Section 35 of the Information Technology Act 2000 read with Rule 23 of the IT (Certifying Authorities) Rules 2000 and the CCA India X.509 Certificate Policy v1.6 (2021) — carries only the signing key pair used for authentication and non-repudiationIssued under the same Section 35 IT Act 2000 framework but provisions two key pairs on one token — a signing certificate plus a separate encryption certificate under the CCA Interoperability Guidelines 2021 for confidentiality of exchanged data
Documents Required

Documents for Class 3 DSC

Share documents via WhatsApp to 9566-068-468. No office visit required for Murugesan Salai clients.

PAN of the applicant (mandatory for both individual and organisation DSC)
Aadhaar of the applicant with Aadhaar-linked mobile number for OTP-based e-KYC
Recent passport-size photograph (live video frame captured during e-KYC)
Mobile and email OTP confirmations for applicant validation under CCA IVG 2021
Authorisation letter on entity's letterhead naming the signatory (organisation DSC only)
Organisation PAN plus GSTIN/CIN/LLPIN proof (organisation DSC only)
Ready to Get Started?
WhatsApp your documents to 9566-068-468 — our team begins within 24 hours. No office visit needed.
Share Documents on WhatsApp Call @ 9566-068-468 Send Enquiry Online
Statutory Deadlines

Compliance deadlines that matter

Miss any of these and the next consequence kicks in automatically.

Deadlines in this neighbourhood — Murugesan Salai businesses operate where the business activity radiating outward from Murugesan Salai Bus Stop and nearby commercial pockets.

Trigger eventDaysFormConsequence
Class 3 DSC approaching natural expiry — 1 / 2 / 3 year validity exhausted15 daysFresh DSC application with paperless or video e-KYC; renewal in the same name treated as fresh issuanceRenewal initiated within 15 days before expiry ensures uninterrupted signing capability; certificates that expire mid-filing cycle cause per-day late-fee exposure on MCA forms under Section 403 of the Companies Act and GST late-fee under Section 47
DSC has expired and holder needs to sign filings on MCA / GST / Tendering portalsOn due dateFresh Class 3 DSC issuance — expired certificates cannot be renewed in placeUntil fresh DSC is issued, all signature-mandatory uploads fail; MCA forms attract ₹100 per day per company per form under Section 403; GST returns attract ₹50 per day under Section 47; tender bids missed
USB token containing live DSC is lost, stolen or suspected compromisedOn due dateSection 38 suspension / revocation request to issuing CA, supported by FIR / affidavitImmediate revocation listing on CRL prevents fraudulent use under Section 66C of the IT Act; delay in filing the Section 38 request leaves the certificate live and the holder exposed to mis-use liability until expiry
DSC holder forgets the token password but certificate is within validityOn due datePassword / PIN reset workflow with issuing CA — typically Aadhaar OTP re-authenticationReset within the certificate validity preserves the remaining months and avoids ₹1,500 fresh-issuance cost; multiple wrong-password attempts trigger token lockout in many models, after which only fresh issuance is possible
Authorised signatory of an organisational DSC ceases to be authorised (resignation, role change, board revocation)On due dateSection 38 revocation request to issuing CA + fresh organisational DSC for the new signatoryOrganisational validity terminates with the underlying authorisation regardless of chronological expiry; continued use exposes the company and the individual to Section 66 / 66C liability and Companies Act compliance defects
Class 3 DSC application submitted under Aadhaar OTP paperless e-KYC routeOn due dateApplication form with Aadhaar OTP authentication and PAN verificationSame-day issuance possible if Aadhaar biometric lock is open and OTP delivers; failure of OTP route forces switch to video-verification with 1-2 day SLA, potentially missing same-day signing requirements
Class 3 DSC application submitted under video-verification e-KYC route2 daysApplication form with recorded verification video, PAN and Aadhaar / passport images1-2 working day standard SLA before certificate is issued; applicants needing same-day signing must plan ahead or default to Aadhaar OTP route; NRI and biometric-locked applicants have no faster option
Private key believed to have been exposed or token suspected to have been clonedOn due dateSection 38 suspension request to issuing CA with incident-reportSuspension flips the certificate status on the CRL within hours; signatures generated after suspension fail verification on every portal; failure to suspend allows continuing fraudulent signing

Deadline pressure points we see in Murugesan Salai: On the ground in Murugesan Salai, for Murugesan Salai businesses balancing growth ambitions with tight statutory compliance.

Forms Library

Forms used in this engagement

Simplified workflow leveraging existing subscriber records to issue replacement before validity lapses.

Initiates token unlock procedure after lockout invoking PUK code provided during initialisation.

Allows relying parties to verify certificate status via online suspension or revocation lookup.

Notarised attested documents required when applicant resides outside Indian jurisdiction.

Captures subscriber particulars name PAN address email mobile and class requested by applicant.

Records explicit subscriber permission to share demographic and biometric data with Certifying Authority under Aadhaar Act.

Subscriber declaration confirming authenticity of submitted PAN passport voter ID for paper-based applications.

Utility bill bank statement passport substantiating residence for non-Aadhaar verification route.

Class 3 DSC in Murugesan Salai, Chennai 600087

Every Murugesan Salai engagement we open begins with the basics: PIN 600087, the Saidapet Division, and the coordinates 13.0419, 80.1731 that anchor the locality. Businesses registered in Murugesan Salai share the Chennai West jurisdiction, and their statutory matters route through the same Saidapet Division each time. Murugesan Salai is a busy commercial road through Valasaravakkam densely lined with retail outlets healthcare clinics restaurants and coaching centres. Because PIN 600087 sits inside the Chennai West jurisdiction, the handling office for Murugesan Salai stays consistent across years, which matters when filings or approvals span cycles.

Murugesan Salai reads as a commercial road through valasaravakkam pocket with high commercial activity, anchored around Murugesan Salai Bus Stop and fed by the Murugesan Salai Bus Stop corridor. Freight and foot traffic from the Murugesan Salai Bus Stop hub pull steady daily commerce through Murugesan Salai, so there is rarely a quiet filing month in this commercial road through valasaravakkam pocket. Working in Murugesan Salai brings a logistical edge: proximity to Murugesan Salai Bus Stop and the Murugesan Salai Bus Stop corridor keeps physical document handling fast. The commercial road through valasaravakkam mix of Murugesan Salai shapes what lands in our workpapers — a blend of restaurants activity and the commercial pulse around Murugesan Salai Bus Stop.

healthcare units around Murugesan Salai share recurring Class 3 DSC patterns — input-credit timing, vendor reconciliation, and sector-specific documentation. Sector concentration matters: when Murugesan Salai leans toward healthcare, the Class 3 DSC risks cluster around the same few line items each cycle. The business mix in Murugesan Salai centres on healthcare, and that sector carries its own Class 3 DSC quirks we plan for in advance. A healthcare operator in Murugesan Salai gets a Class 3 DSC workflow shaped by sector norms, not a one-size-fits-all template.

The qualified-review step on every Murugesan Salai Class 3 DSC file is where errors get caught before they reach the portal. A Murugesan Salai client sees the same Class 3 DSC cadence each cycle: intake, reconciliation, review, filing, acknowledgement. Every Class 3 DSC file we open for Murugesan Salai is reconciled, reviewed by a qualified practitioner, and archived for seven years. Fixed-fee scoping means a Murugesan Salai business knows the Class 3 DSC cost up front, with no surprise additions mid-engagement.

Businesses straddling Murugesan Salai and Karambakkam get a single Class 3 DSC point of contact rather than two. A client relocating between Murugesan Salai and Karambakkam keeps the same Class 3 DSC file and the same team. We treat Murugesan Salai and Karambakkam as one catchment for Class 3 DSC, which keeps documentation and turnaround consistent. Serving Murugesan Salai and Karambakkam from one team keeps Class 3 DSC turnaround identical across the cluster.

The longer we serve Murugesan Salai, the more precisely we predict where a Class 3 DSC file needs attention. Each engagement in Murugesan Salai adds to a record of what the Chennai West jurisdiction expects, sharpening the next Class 3 DSC file. Patterns we track for Murugesan Salai include retail documentation gaps, timing mismatches, and the questions the Saidapet Division tends to raise. The Class 3 DSC mistakes we see most in Murugesan Salai are avoidable with disciplined intake, which our checklist enforces.

First-time Class 3 DSC for a Murugesan Salai business is where getting the basics right saves years of cleanup later. New small trade ventures in Murugesan Salai lean on us to stand up Class 3 DSC correctly before the first deadline rather than after a notice. When a Sakthi Nagar Valasaravakkam business expands into Murugesan Salai, we extend its Class 3 DSC setup to PIN 600087 without disruption. We onboard new Murugesan Salai entities onto a Class 3 DSC cadence that is audit-ready from the very first cycle.

4.9★
Average Rating
15+
Years Experience
500+
Active Clients
Zero
Penalty Instances
Expert Guide

Class 3 DSC in Murugesan Salai — Complete Guide

Effective 1 January 2021, the Controller of Certifying Authorities discontinued issuance of Class 2 DSCs across all licensed CAs. From that date, Class 3 has been the only PKI-based digital signature certificate issued in India for individuals and organisations. Murugesan Salai clients renewing older Class 2 certificates are migrated to Class 3 with full re-verification under the CCA Identity Verification Guidelines 2021.

Class 3 DSC in Murugesan Salai, Chennai

Class 3 Digital Signature Certificates issued in Murugesan Salai under Section 35 of the IT Act 2000 by CCA-licensed Certifying Authorities — paperless Aadhaar OTP e-KYC, FIPS 140-2 USB token and 2-year standard validity. Class 2 DSC deprecated 1-Jan-2021.

Class 3 DSC for Individuals in Murugesan Salai — Director / ITR Signing

Class 3 individual DSC for Murugesan Salai directors, partners and proprietors — used for MCA DIR-3 KYC, SPICe+ incorporation, Income Tax ITR signing under Section 140 of the Income-tax Act and personal e-Tendering. Same-day Aadhaar e-KYC issuance.

Class 3 Organisation DSC in Murugesan Salai — GST / TRACES / IceGate

Class 3 organisation DSC for Murugesan Salai companies and LLPs — used for GST authorised signatory under Rule 26 CGST Rules, TRACES Form 24Q/26Q TDS filing under Section 200(3) Income-tax Act, IceGate Customs and DGFT IEC. Authorisation letter and CIN/GSTIN proof required.

Aadhaar e-KYC vs Video KYC vs In-Person Verification under CCA IVG 2021

CCA Identity Verification Guidelines 2021 permit three modes — paperless Aadhaar OTP e-KYC, video-based verification with original document display, and in-person verification before a CA-authorised officer. Choice depends on Aadhaar mobile linkage and applicant location.

Get Expert Help Today
Qualified professionals handle your Class 3 DSC in Murugesan Salai. WhatsApp documents — we begin within 24 hours. From ₹1,500/one-time. Free consultation.
WhatsApp for Free Consultation Call @ 9566-068-468
From ₹1,500/one-time
15+ years experience
Zero penalties guaranteed
Offices at Maduravoyal, Nerkundram & Nolambur (upcoming)
Key Facts — Class 3 DSC in Murugesan Salai
Class 3 DSC issued by CCA-licensed Certifying Authorities under Section 35 of the IT Act 2000 — eMudhra, Protean (NSDL e-Gov), Sify Safescrypt, Capricorn, IDsign, VSign — all officer-acceptable for Murugesan Salai clients.
Paperless Aadhaar OTP e-KYC under CCA Identity Verification Guidelines 2021 — same-day issuance with no physical document movement for Murugesan Salai applicants.
Class 2 DSC deprecated effective 1 January 2021 per CCA notification dated 17 December 2020 — Class 3 is the only PKI-based DSC issued in India today.
FIPS 140-2 Level 2 USB tokens supplied — ePass2003, Watchdata ProxKey, Trust Key — private key non-exportable and hardware-bound as mandated by CCA Interoperability Guidelines.
Section 5 of the IT Act 2000 grants digital signatures equivalent legal status to handwritten signatures — admissibility under Section 65B Indian Evidence Act per Anvar P.V. (2014) and Arjun Panditrao Khotkar (2020).
Class 3 organisation DSC issued in entity's name with authorisation letter, board resolution and organisation PAN+GSTIN/CIN — accepted on GST, TRACES and tender portals for Murugesan Salai corporate clients.
MCA SPICe+ incorporation, DIR-3 KYC, AOC-4, MGT-7, INC-22 and DPT-3 e-forms signed with Class 3 individual director DSC under MCA21 portal rules.
GST authorised-signatory DSC under Rule 26(1) CGST Rules — mandatory for companies and LLPs and supported for proprietorships seeking DSC mode over EVC.
Aadhaar eSign under Section 3A of the IT Act 2000 offered as parallel one-time-signature option for Murugesan Salai clients needing single-document signing without USB token.
Revocation, CRL publication and OCSP coverage handled per Section 38 IT Act and CCA Interoperability Guidelines — token loss, employment change and key compromise covered.
People Also Ask — Class 3 DSC in Murugesan Salai
Is Class 2 DSC still valid in India in 2026?
No. Class 2 DSCs are not issued by any CCA-licensed Certifying Authority since 1 January 2021 pursuant to the CCA notification dated 17 December 2020. Existing Class 2 DSCs were valid only till the end of their original validity tenure and have not been renewed thereafter. Class 3 DSC is now the only PKI-based digital signature certificate issued in India alongside the parallel Aadhaar eSign framework under Section 3A of the IT Act 2000.
How long does Class 3 DSC issuance take in Murugesan Salai?
With Aadhaar OTP e-KYC and a pre-loaded FIPS 140-2 USB token, Class 3 individual DSC for Murugesan Salai clients is issued within 30-60 minutes of application. Video KYC issuance during CA business hours takes 2-4 working hours. Class 3 organisation DSCs requiring authorisation letter, board resolution and entity-document verification take up to 1 working day.
What is the standard validity of a Class 3 DSC?
Class 3 DSCs are issued with 1-year, 2-year or 3-year validity at the applicant's option under Section 35 of the IT Act 2000. Two-year validity is the most commonly issued tenure in India. Validity is encoded into the certificate at issuance and cannot be extended later — on expiry, fresh Aadhaar e-KYC or video KYC is required for re-issuance.
Can I use one Class 3 DSC for both MCA and GST filings?
Yes for individuals — a Class 3 individual DSC of a director can sign MCA SPICe+, DIR-3 KYC and AOC-4 e-forms and the same individual DSC can be added as authorised signatory on the GST portal for the same person. For corporate filings on GST and TRACES under the entity's name, a Class 3 organisation DSC is preferred and is mandatory in many tendering scenarios.
What happens if the USB token containing my DSC is lost?
The DSC must be reported to the issuing CA under Section 38 IT Act 2000 for revocation. The certificate is added to the Certificate Revocation List (CRL) and OCSP responder under the CCA Interoperability Guidelines. A fresh USB token is purchased, full Aadhaar e-KYC re-verification is performed and a new DSC is issued — the lost certificate cannot be transferred because the private key was hardware-bound.
Is Aadhaar eSign a substitute for Class 3 DSC?
Aadhaar eSign under Section 3A IT Act 2000 read with Schedule II is suitable for one-time signing of single documents (loan agreements, e-NACH mandates, digital onboarding) where the signer is an Indian resident with Aadhaar. It is not a substitute for Class 3 DSC where repeated signing is required across MCA, GST, TRACES and tender portals — those portals expect a long-term PKI certificate stored on a hardware token, not a 30-minute eSign certificate.
What is a Class 3 DSC and why is it the only class now available?

A Class 3 DSC is a digital signature certificate issued under Section 35 of the IT Act 2000. After the CCA discontinued Class 2 certificates from 1 January 2021, Class 3 — with in-person or video identity verification — became the sole class issued for all statutory and commercial filings.

Is a Class 3 DSC mandatory for MCA and GST filings?

Yes. MCA21 V3 accepts only Class 3 DSCs for director and professional filings, and the GST portal requires a Class 3 DSC for companies and LLPs under Rule 26 of the CGST Rules 2017. Individuals and proprietors may use EVC, but a DSC is still required for many forms.

What is the difference between a signature and a combo Class 3 DSC?

A signature DSC only signs documents for authentication and non-repudiation. A combo DSC adds a separate encryption certificate to decrypt data returned by a portal — needed mainly for government e-tenders (GeM, CPPP) and IP India trademark filings. Most tax filers need only the signature type.

How long does it take to get a Class 3 DSC in Chennai?

With Aadhaar-based paperless e-KYC and video verification, a Class 3 DSC is typically issued the same working day. Delays arise only when the mobile number is not linked to Aadhaar or the applicant's name mismatches between PAN and Aadhaar.

What documents are needed for a Class 3 individual DSC?

For Aadhaar e-KYC: PAN, Aadhaar-linked mobile for OTP, a passport-size photo and a short video verification. For paper-based KYC: self-attested PAN and address proof attested by a gazetted officer or banker. The applicant's mobile and email must be their own.

How much does a Class 3 DSC cost?

A Class 3 signature DSC costs approximately ₹1,200–₹1,500 one-time for a 2-year certificate including the FIPS 140-2 Level 2 USB token, Aadhaar e-KYC and video verification. A combo (sign + encrypt) DSC costs approximately ₹1,800–₹2,500 for the same term.

What Murugesan Salai clients want to know before signing: On the ground in Murugesan Salai, around the Murugesan Salai Bus Stop catchment of Murugesan Salai.

Expert Guide

A complete walkthrough — Class 3 Dsc

Reading this guide locally — Murugesan Salai businesses operate where around the Murugesan Salai Bus Stop catchment of Murugesan Salai.

What is a Class 3 Digital Signature Certificate

Electronic signature under Section 3A of the IT (Amendment) Act 2008

The IT (Amendment) Act 2008, which came into force on 27-10-2009, inserted Section 3A in the IT Act 2000 to recognise a broader category of electronic signature in addition to the Digital Signature Certificate based on asymmetric cryptography. Section 3A enables the Central Government to notify by rule any electronic signature technique that is reliable as defined in the section. The notification under Section 3A enabled the Aadhaar-based e-Sign service launched in 2015, under which a subscriber authenticates via Aadhaar OTP or biometric and a one-time certificate is issued for the immediate signing transaction. Class 3 DSC and e-Sign coexist as alternative authentication mechanisms, with Class 3 DSC being the preferred mode for multi-use and high-value transactions and e-Sign being the preferred mode for single-transaction citizen-facing workflows.

Legal effect and presumptions under Sections 5 and 85B

Section 5 of the IT Act 2000 provides that where any law requires that a document be signed, the requirement is satisfied if the document is authenticated by means of a Digital Signature affixed in such manner as may be prescribed. Section 85B of the Indian Evidence Act 1872 (inserted by the IT Act 2000 and renumbered by the Bharatiya Sakshya Adhiniyam 2023) creates a presumption that a secure electronic record has not been altered since the date on which the digital signature was affixed. Section 67A of the Bharatiya Sakshya Adhiniyam 2023 (corresponding to the earlier Section 67A of the Evidence Act) requires that a person seeking to rely on an electronic record produce a certificate from the CA verifying the signature. Together, these provisions establish digital signatures as functionally equivalent to handwritten signatures for evidentiary purposes in Indian courts.

Statutory basis under the Information Technology Act 2000

A Digital Signature Certificate (DSC) is an electronic credential issued by a licensed Certifying Authority (CA) that binds a public-key cryptographic key-pair to the identity of a subscriber, enabling the subscriber to digitally sign electronic records with legal effect equivalent to a handwritten signature. The Indian framework is established under the Information Technology Act 2000, which received Presidential assent on 09-06-2000 and was inspired by the UNCITRAL Model Law on Electronic Commerce 1996 adopted by the United Nations Commission on International Trade Law in resolution 51/162 of 16-12-1996. Sections 35 to 39 of the IT Act 2000 set out the framework for issuance, suspension and revocation of Digital Signature Certificates, while Section 17 establishes the office of the Controller of Certifying Authorities (CCA) as the apex regulator of the DSC ecosystem in India.

Cryptographic standards and certificate format

RSA key-length and signature algorithm

The India PKI profile specifies RSA as the primary public-key cryptographic algorithm, with a minimum key-length of 2048 bits for subscriber certificates issued from 01-01-2014 onwards. The CCA's 2022 Cryptographic Guidelines updated the recommended key-length to 3072 bits for new certificates issued from 01-01-2025, with 2048-bit certificates issued before that date remaining valid for their natural validity period. The signature algorithm on subscriber certificates is currently sha256WithRSAEncryption, replacing the sha1WithRSAEncryption that was phased out by 01-01-2016 following the SHA-1 deprecation timeline coordinated internationally by the CA/Browser Forum. Elliptic Curve Cryptography (ECC) certificates under sha256ecdsa are permitted under the India PKI profile but are not yet widely deployed because most Indian government portal validators are RSA-only in practice.

Subject Distinguished Name and Subject Alternative Name

The Subject Distinguished Name on a Class 3 DSC is composed of mandatory and optional attributes specified in the India PKI profile. For an Individual DSC, the mandatory attributes include the subscriber's common name (CN), country (C=IN), state (ST), and may include a serial number to disambiguate same-name subscribers. For an Organisation DSC, additional mandatory attributes include the organisation name (O) and organisation unit (OU). The Subject Alternative Name (SAN) extension under RFC 5280 permits the inclusion of additional identifier types including email address, DNS name, IP address and otherName. The otherName field is used in the India PKI profile to carry sector-specific identifiers such as CDSCO licence number, RBI Certificate of Registration number, FSSAI FBO licence number and similar regulatory identifiers, enabling straight-through authentication on sector portals.

Cryptographic token storage and FIPS 140-2 compliance

The CCA framework requires that the private key of a Class 3 DSC be stored on a hardware cryptographic token meeting FIPS 140-2 Level 2 (USB token) or Level 3 (HSM) certification under the US National Institute of Standards and Technology's Federal Information Processing Standard. Commonly available USB tokens in the Indian market include eMudhra ePass2003 Auto, Sify SafeNet eToken 5110, Watchdata ProxKey, HYP2003 and the more recent SafeNet eToken FIPS variants. The tokens are accessed via PKCS#11 (the Cryptographic Token Interface Standard under RSA Laboratories' Public-Key Cryptography Standards series, now maintained by OASIS) which provides a standard programming interface for cryptographic operations. The PKCS#11 driver for each token brand is provided by the issuing CA and must be installed before the token can be used on a Windows or macOS workstation.

Revocation and the Certificate Revocation List

Section 38 revocation framework

Section 38 of the IT Act 2000 confers the power to revoke a Digital Signature Certificate on the subscriber and on the issuing Certifying Authority. The subscriber can request revocation at any time through the issuing CA's revocation portal, typically by submitting a signed revocation request with reasons (compromise of private key, loss of token, change of subscriber's identifying details or termination of employment of the named signatory). The CA can revoke a certificate suo motu if it discovers that the certificate was issued on the basis of inaccurate or false information, or if the subscriber has materially breached the subscriber agreement. Section 38 revocation is publicised through the CA's Certificate Revocation List (CRL) and Online Certificate Status Protocol (OCSP) responder, which together enable any third-party verifier to determine the revocation status of a specific certificate in real time.

CRL and OCSP under RFC 5280 and RFC 6960

The Certificate Revocation List is a digitally-signed list of revoked certificate serial numbers published periodically (typically every twenty-four hours) by each issuing CA at a URL specified in the CRL Distribution Points extension of every subscriber certificate. The CRL format and update mechanics are governed by IETF RFC 5280. The Online Certificate Status Protocol (OCSP), specified in IETF RFC 6960, provides a real-time alternative to CRL: a verifier sends an OCSP query to the issuing CA's OCSP responder with a specific certificate serial number and receives an immediate signed response confirming the certificate's status as good, revoked or unknown. The India PKI profile requires every Class 3 DSC to carry both a CRL Distribution Points extension and an Authority Information Access extension pointing to the OCSP responder URL, enabling verifiers to choose the appropriate revocation-check mechanism for their workflow.

Suspension under Section 37

Section 37 of the IT Act 2000 provides for suspension of a Digital Signature Certificate as a temporary measure short of revocation. Suspension may be invoked by the CA on its own motion or on a request from the subscriber or any person authorised by the subscriber, where the circumstances warrant a temporary halt of the certificate's operational validity pending resolution of an issue (suspected compromise that is being investigated, dispute over the subscriber agreement, or processing of a change-of-particulars request). The suspended certificate appears on the CRL with a status of certificateHold and a specific OCSP response indicating suspension. If the underlying issue is resolved, the suspension may be lifted and the certificate restored to operational status. If the issue cannot be resolved, the suspension typically converts to a full revocation under Section 38.

Comparative international frameworks

UNCITRAL Model Law on Electronic Signatures 2001

The UNCITRAL Model Law on Electronic Signatures was adopted by the United Nations Commission on International Trade Law in 2001 as a framework instrument to guide states in adopting legislation on electronic signatures. The Model Law establishes a functional-equivalence approach: an electronic signature satisfies a legal requirement for a signature if it is sufficiently reliable for the purpose for which the data message was generated, with reliability assessed against five criteria including the link of the signature to the signatory, the signatory's control over the signature-creation data, and detectability of subsequent alterations. India is not a formal adherent to the Model Law but the IT Act 2000 substantially reflects its principles, having been drafted in parallel with the development of the Model Law and the predecessor UNCITRAL Model Law on Electronic Commerce 1996. The compatibility provides the substantive basis for cross-recognition of India Class 3 DSCs in Model-Law-adopting jurisdictions.

EU eIDAS Regulation 910/2014

The European Union's electronic identification and trust services framework is established under Regulation (EU) 910/2014 of the European Parliament and of the Council of 23-07-2014 on electronic identification and trust services for electronic transactions in the internal market, commonly referred to as the eIDAS Regulation. eIDAS establishes a three-tier taxonomy of electronic signatures: Electronic Signature (the lowest tier, broadly equivalent to any electronic data attached to an electronic record), Advanced Electronic Signature (AES, which uniquely identifies the signatory and is linked to the signed data such that any subsequent change is detectable), and Qualified Electronic Signature (QES, an AES created by a qualified signature creation device and based on a qualified certificate). Under Article 25 of eIDAS, a QES has the equivalent legal effect of a handwritten signature throughout the European Union. The Indian Class 3 DSC corresponds taxonomically to AES under eIDAS, not QES.

US ESIGN Act 2000 and UETA

In the United States, electronic signatures are governed at the federal level by the Electronic Signatures in Global and National Commerce Act (ESIGN Act) of 2000, which establishes the general rule that a signature, contract or record relating to a transaction in or affecting interstate or foreign commerce shall not be denied legal effect, validity or enforceability solely because it is in electronic form or because an electronic signature was used in its formation. The ESIGN Act is supplemented at the state level by the Uniform Electronic Transactions Act (UETA), adopted in 1999 by the Uniform Law Commission and enacted in some form by forty-seven of the fifty states (with New York, Illinois and Washington having parallel state legislation). The US framework is technology-neutral and does not impose a specific cryptographic standard, making it easier than eIDAS for an India Class 3 DSC to be accepted in US commercial transactions on a reliability-based assessment.

What Murugesan Salai clients usually ask next: On the ground in Murugesan Salai, for Murugesan Salai businesses balancing growth ambitions with tight statutory compliance.

Glossary

Plain-English glossary for this service

MTok

A FIPS 140-2 Level 2 USB cryptographic token sold primarily by eMudhra-affiliated channels. Functionally equivalent to ePass and ProxKey for Indian DSC use; users select between models based on price, channel availability and driver compatibility with the workstation operating system.

ProxKey

A FIPS 140-2 Level 2 USB cryptographic token from Watchdata, commonly bundled with Capricorn and Sify DSC issuances. Like ePass and MTok, ProxKey carries the holder's signing certificate and optional encryption certificate, and uses PKCS#11 for portal-side integration.

Hard token

Synonym for a physical FIPS 140-2 Level 2 USB cryptographic device that holds the Class 3 DSC. Contrasted with a soft token (file-based PKCS#12 store) which is not permitted for Class 3 by the CCA — soft tokens were the norm for retired Class 1 and Class 2 DSCs.

Soft token

A file-based cryptographic credential store (typically a PKCS#12 .pfx file) where the private key is encrypted under a passphrase but stored on the workstation file system. Not permitted by the CCA for Class 3 DSC issuance after the 2021 class-retirement. Still encountered in legacy SSL client-authentication and obsolete Class 2 DSC files.

X.509

The International Telecommunication Union standard for the format of public-key certificates, including the subject distinguished name, issuer distinguished name, validity period, public key, key-usage extensions and the issuing CA's digital signature over the certificate. Every Indian Class 3 DSC is an X.509 v3 certificate.

Public key

The freely shareable half of an asymmetric cryptographic key pair. In a DSC the public key is embedded in the X.509 certificate and is used by any verifier to validate a digital signature created by the corresponding private key. The public key cannot be used to forge signatures or decrypt data encrypted to it.

Private key

The secret half of an asymmetric cryptographic key pair. For Class 3 DSCs the private key is generated inside the FIPS 140-2 Level 2 hardware token and cannot be exported; all signing operations are performed by the token internally. Loss of control of the private key (lost or stolen token) requires immediate Section 38 suspension with the issuing CA.

Certificate Revocation List

A digitally signed list, published periodically by every Certifying Authority, of certificates that have been revoked before their natural expiry — due to compromise, loss of token, change of role, or voluntary surrender. Verifiers (MCA, GST, IT portals) check the CRL or query an OCSP responder before accepting a digital signature.

Certifying Authority

An entity licensed by the Controller of Certifying Authorities under Section 24 of the IT Act 2000 to issue Digital Signature Certificates in India. As of date, the live CAs include eMudhra, Sify Communications, (n)Code Solutions, Capricorn Identity Services, IDSign, Verasys and a handful of others. Each CA's certificates are valid pan-India and across all government portals.

Class 3 Digital Signature Certificate

Highest assurance certificate issued after stringent identity verification mandated for tendering MCA GST submissions.

Asymmetric Crypto-System

Pair of mathematically related keys where private signs and public verifies securing electronic record authentication.

Public Key Infrastructure

Hierarchical trust framework binding identities to cryptographic keys through Certifying Authority issued certificates.

By Industry

Industry-specific patterns in Murugesan Salai

How the local trade mix shapes this — Murugesan Salai businesses operate where the cluster of retail, restaurants, healthcare businesses that defines Murugesan Salai's commercial fabric.

Restaurants
Common issue: Restaurant operators registered under FSSAI as central licensees, multi-state operators and online food-delivery aggregator-partners are required to file periodic FoSCoS (Food Safety Compliance System) returns and respond to FSSAI-Source improvement notices using Class 3 DSC authentication. Operators routinely face authentication failure because the FoSCoS portal's signature validator requires the certificate's key-usage extensions to include both digitalSignature and nonRepudiation under RFC 5280, and a signing-only certificate without nonRepudiation is rejected even though it is otherwise a valid Class 3 DSC.
How we handle it: Procure a Class 3 Combo (Signing plus Encryption) DSC rather than a Signing-only variant from the issuing CA, ensuring that the key-usage extension of the X.509 certificate covers digitalSignature, nonRepudiation and keyEncipherment as required by the FoSCoS portal; verify the certificate's key-usage profile by opening the .cer file in Windows Certificate Viewer (certmgr.msc) under Details tab before initiating any FoSCoS filing; if a Signing-only certificate is already procured, request the CA to re-issue at no extra cost under the CCA's mis-issuance-remediation framework.
Restaurants
Common issue: Restaurant chains operating under a holding company structure with subsidiary entities for each city often use the holding company's Class 3 Organisation DSC to file documents on behalf of the subsidiaries, on the basis that the directors are common. The IT Act 2000 Section 35 and the CCA Identity Verification Guidelines treat each legal entity as a distinct subscriber, and the Subject Distinguished Name on the certificate must match the entity in whose name the document is being filed, leading to rejection at MCA21, GST, EPFO and ESIC portals where the entity-mapping logic is strict.
How we handle it: Procure a separate Class 3 Organisation DSC for each subsidiary entity under that subsidiary's CIN and PAN, even where the authorised signatory director is common across multiple entities; tag each DSC token with the corresponding entity name to prevent operational mix-up; maintain a subsidiary-wise DSC matrix capturing entity name, CIN, certificate serial number, validity dates and issuing CA; reconcile the DSC matrix with the subsidiaries' ROC master data at half-yearly intervals.
Healthcare
Common issue: Diagnostic centres, small hospitals and pharmacies registered with the Central Drugs Standard Control Organisation under SUGAM and with the State Drug Controllers under their respective licensing portals are required to authenticate sensitive batch-recall and pharmacovigilance submissions using Class 3 DSC. The sector-specific portals frequently require a Class 3 DSC with the medical institution's licence number embedded in the Subject Alternative Name (SAN) extension of the X.509 certificate, a non-standard requirement that operators discover only at the point of filing failure.
How we handle it: At the time of Class 3 DSC procurement, specifically request the issuing CA to include the CDSCO licence number, NABL accreditation number or NABH accreditation number in the Subject Alternative Name extension of the X.509 certificate under the otherName field as permitted by RFC 5280; verify the SAN content after issuance using Windows Certificate Viewer or OpenSSL; where the existing certificate lacks the SAN field, request a no-charge re-issuance under the CA's mis-specification remediation framework rather than purchasing a fresh certificate.
Healthcare
Common issue: Multi-doctor partnership clinics and LLPs face an internal-governance issue where the Class 3 DSC of a retiring or deceased partner remains active until expiry, leaving the firm exposed to unauthorised signing during the transition period. The IT Act 2000 Section 38 confers the power to revoke a Digital Signature Certificate on the subscriber or on the Certifying Authority, but the revocation must be formally initiated, and the certificate continues to be operationally valid until added to the CCA's Certificate Revocation List under RFC 5280 or marked revoked on the OCSP responder under RFC 6960.
How we handle it: Include a standard partner-exit protocol in the LLP agreement and partnership deed requiring immediate surrender of the Class 3 DSC token and submission of a revocation request to the issuing CA within seventy-two hours of the partner's exit; preserve the revocation acknowledgement from the CA on the firm's records; verify CRL and OCSP status using the issuing CA's online verification tool; for deceased-partner cases obtain the death certificate and the legal-heir consent letter as required by the CCA's revocation procedure under Section 38 of the IT Act.
Construction Contractors
Common issue: Construction contractors executing joint-venture arrangements with foreign partners for international-funded projects (ADB, World Bank, JICA) face complexity around which jurisdiction's electronic signature governs the JV agreement and the lender's procurement documents. The Singapore Electronic Transactions Act 2010 (which adopts the UNCITRAL Model Law on Electronic Signatures 2001 verbatim) is commonly chosen as the governing law for ADB-funded contracts, and an India Class 3 DSC is accepted as a reliable electronic signature under Section 8 of the Singapore ETA on the basis of UNCITRAL mutual-recognition, but the procedural authentication still requires a certificate-chain extract.
How we handle it: Pair the India Class 3 DSC with a Certificate-Chain Extract issued by the issuing CA (showing the CCA India root, the issuing CA intermediate, and the subscriber certificate) and an apostille or notarised copy of the CCA's CPS (Certification Practice Statement) for production before the ADB Procurement Review Panel or the World Bank's procurement disputes resolution forum; cross-reference the UNCITRAL Model Law 2001 Article 12 mutual-recognition clause in any JV-agreement dispute-resolution argument; consider a parallel eIDAS Qualified Signature for the EU partner's home-jurisdiction comfort.
Case Studies

Anonymised engagements we have handled

Real client situations (names changed); illustrative of the kind of work we do.

Individual vs organisationalServices

Class 3 individual DSC mis-used for organisational signing — 4 GST returns rejected

Issue: A services-company accountant procured a low-cost Class 3 individual DSC in his personal name for ₹1,500 and used it to sign 4 GSTR-3B returns of the company. The GST portal accepted the signature at the upload stage but the JSON validator threw the 'Authorised signatory PAN mismatch' rejection because the certificate subject-CN carried the individual's PAN, not the company's PAN.
Approach: Procured a fresh Class 3 organisational DSC at ₹1,500 in the accountant's name with the company name and his designation in the OU field, supported by board-resolution and authorisation letter. Re-signed the 4 GSTR-3B returns with the organisational DSC and re-uploaded. Triggered a portal authorised-signatory update to ensure the new DSC PAN linkage matched.
Outcome: 4 GSTR-3B returns accepted on re-upload within the original due-date window; no per-day late fee under Section 47; firm trained to differentiate individual DSC (proprietorships, professionals, directors signing as individuals) from organisational DSC (company / LLP authorised signatories) before procurement.
Token failureReal Estate

Hardware token failed — emergency e-Sign bridged single-day signing requirement

Issue: A real-estate LLP needed to sign a Form 8 statement of accounts on the MCA V3 portal on the last day of the statutory window. The designated partner's USB token developed a read-error mid-signing — the device LED blinked but Windows would not detect the certificate. A replacement token from the CA would take 2 working days, missing the 30-October deadline.
Approach: Switched the single critical signing to an Aadhaar e-Sign service (single-use Section 3A IT Act electronic signature) for the Form 8 upload, treating it as a stop-gap. Parallelly raised a Section 38 / hardware-failure ticket with eMudhra for a free token-replacement under the 1-year hardware warranty, with the existing certificate to be re-keyed into the new token. Tested the e-Sign signature on a draft PDF before applying it to the MCA filing.
Outcome: Form 8 uploaded with e-Sign before midnight on the deadline date; ₹100 per-day delay penalty avoided; hardware token replaced 3 days later under warranty with the certificate re-loaded; LLP saved ₹1,500 fresh DSC cost by re-using existing certificate on new hardware.
Certificate type mismatchIT Services

Public-key encryption certificate confused with signing certificate — IT portal rejected upload

Issue: An IT-services CFO procured a Class 3 combo certificate from a sub-CA — one signing certificate and one encryption certificate on the same token. While uploading a 26Q TDS return, the IT-portal signature panel selected the encryption certificate by default (sorted first alphabetically) instead of the signing certificate. The portal threw a 'Key usage does not permit digital signature' error, which the practitioner initially mistook for a token failure.
Approach: Educated the user that X.509 'Key Usage' extension differentiates digital-signature certificates from data-encipherment certificates — both can sit on the same token but only the signing certificate works for IT/GST/MCA. Reconfigured the token utility to default to the signing certificate and re-uploaded the 26Q. Renamed the friendly-name of each certificate inside the token to 'SIGN' and 'ENCRYPT' for unambiguous selection by all 4 firm signatories sharing the token model.
Outcome: 26Q uploaded successfully within 10 minutes of correction; no Section 234E ₹200-per-day late fee triggered; firm now standardises the friendly-name convention across 30+ tokens in the office; user-error signing-failure tickets dropped from 8 per quarter to under 1.
Evidentiary valueLegal Tech

Section 65B electronic-evidence challenge — Class 3 DSC audit trail held in 7-year-old dispute

Issue: A 7-year-old commercial dispute resurfaced in arbitration where the opposing counsel challenged the validity of a 2017 e-mail attachment signed with a Class 3 DSC. The challenge argued the certificate had since expired and the signature could no longer be verified. Under Section 65B of the Indian Evidence Act, an electronic record requires a contemporaneous certificate of authenticity for admissibility.
Approach: Pulled the issuing CA's archival CRL and OCSP-responder records showing the certificate's status as 'valid' on the original signing date. Obtained a Section 65B certificate from the CA confirming the signature was generated within validity, the private-key was protected on a FIPS 140-2 token, and the CRL of the signing date contained no entry for the certificate. Produced the X.509 certificate-chain to the Indian root CA. Tendered the package before the arbitral tribunal with a chain-of-custody affidavit.
Outcome: Tribunal admitted the signed e-mail attachment as authentic evidence; opposing counsel's expiry-based challenge rejected because Section 65B certifies the position at the time of signing, not at the time of dispute; the underlying ₹38 lakh commercial claim was decided on merits in client's favour.

Why these Murugesan Salai engagements look the way they do: On the ground in Murugesan Salai, the cluster of retail, restaurants, healthcare businesses that defines Murugesan Salai's commercial fabric; for Murugesan Salai businesses balancing growth ambitions with tight statutory compliance.

Client Reviews

What Murugesan Salai Clients Say

Ramesh K
Class 3 DSC
“Needed Class 3 individual DSC for incorporating a private limited company. FilingPro completed the Aadhaar OTP e-KYC over WhatsApp and the DSC was loaded onto the ePass2003 token within 45 minutes. Used it the same evening for SPICe+ filing on MCA21. Smooth and paperless.”
3 weeks agoVerified Client
Latha S
Class 3 DSC
“Required organisation DSC for our GST authorised signatory. FilingPro drafted the board resolution and authorisation letter, coordinated with the CA for video KYC and we received the DSC the next morning. Replaced our older Class 2 DSC which had expired post-Jan-2021 deprecation.”
1 month agoVerified Client
Vinay M
Class 3 DSC
“Multi-director DSC pack for our 5-director board needed for SPICe+ and tender bidding. FilingPro coordinated all 5 Aadhaar e-KYCs in one day, supplied premium Watchdata tokens with encryption-signing pair and we were tender-ready by next working day. The premium pack saved significant time.”
2 months agoVerified Client
Suresh P
Class 3 DSC
“My USB token got locked after multiple wrong PIN attempts. FilingPro explained that the certificate had to be re-issued — the private key on the token cannot be recovered. They processed a fresh Aadhaar e-KYC the same day and a new 2-year DSC was loaded. Clear technical explanation, no nonsense.”
6 weeks agoVerified Client
Deepa R
Class 3 DSC
“Needed Class 3 DSC urgently for TRACES TDS return filing — last day of the quarter. FilingPro arranged Aadhaar OTP e-KYC within an hour, the DSC was issued same-day and we filed Form 24Q before midnight. Saved us a Section 234E late fee. Excellent crisis response.”
2 months agoVerified Client
Kannan V
Class 3 DSC
“Renewed our company's organisation DSC after 2-year expiry. FilingPro reused the existing authorisation letter and entity documentation, only fresh signatory Aadhaar e-KYC was needed, and the new DSC came through in half a day. Smooth renewal cycle, no surprises on documentation.”
4 weeks agoVerified Client
4.9
312+ reviews
500+
Active Clients
15+
Years Exp
5★
4★
3★
Common Questions

Class 3 DSC FAQ — Murugesan Salai

Common questions from Murugesan Salai clients. Call 9566-068-468 for specific queries.

Section 5 of the IT Act 2000 grants digital signatures the same legal status as handwritten signatures wherever any law requires a signature. Section 3 prescribes the technical authentication procedure using asymmetric cryptography and hash functions. Section 3A inserted by the IT (Amendment) Act 2008 adds a parallel framework for "electronic signatures" specified in the Second Schedule, which presently includes Aadhaar-based eSign.
Step 1 — applicant fills the CA's online application with PAN, name, email and mobile. Step 2 — UIDAI Aadhaar OTP is triggered to the Aadhaar-linked mobile and entered. Step 3 — UIDAI returns the e-KYC payload (name, photo, address) digitally signed. Step 4 — applicant records a 30-second video selfie reading a system-generated PIN. Step 5 — CA matches Aadhaar photo with video frame, generates the key pair and issues the DSC for download to the USB token.
Yes — 600087 (Murugesan Salai) is well within our service area. We handle Class 3 DSC for this PIN and the surrounding 600xxx localities routinely, with the full process available online or in person.
The CRL is a digitally signed list of revoked certificates published periodically by every licensed CA under the CCA Interoperability Guidelines. Relying parties (e.g., MCA, GST portals) download or query the CRL to verify that a presented DSC has not been revoked. CRL updates are published every 24 hours or sooner on emergency revocation. The CRL is the primary revocation evidence required by Section 38.
DSC renewal is functionally a fresh issuance — the IT Act treats it as a new certificate with new validity. The applicant submits fresh Aadhaar e-KYC or video KYC, organisation documents are re-verified for organisation DSCs, and a new certificate is loaded onto a new or re-formatted USB token. Many CAs offer 30-day pre-expiry renewal with documentation reuse.
Yes. We do not disappear after filing — Murugesan Salai clients can come back to us for follow-up questions, notices or renewals tied to their Class 3 DSC. Ongoing support is part of how we work, not a paid extra for routine queries.
The CCA is appointed under Section 17 of the IT Act 2000 and licenses Certifying Authorities under Section 21. The CCA exercises supervision under Sections 18-20, lays down standards (Section 19), and operates the Root Certifying Authority of India (RCAI). Licensed Certifying Authorities (CAs) currently include eMudhra, NSDL e-Governance (Protean), Sify Safescrypt, Capricorn, IDsign, VSign, NIC and IndusInd-RA. The CCA portal is cca.gov.in.
DSCs are issued under Section 35 read with Rule 23 of the IT (CCA) Rules with validity options of 1 year, 2 years or 3 years. Two-year validity is the most commonly issued tenure. Validity is encoded in the certificate itself and cannot be extended — on expiry a fresh DSC issuance procedure with re-verification of identity is required.
Our Class 3 DSC fees are fixed and shared in writing before any work starts — no hourly billing and no surprises. Pricing depends on the complexity of your case, not your location, so Murugesan Salai clients pay the same transparent rates as everyone else. See the pricing section above or call 9566-068-468 for an exact figure.
Aadhaar eSign is an electronic signature service provided by eSign Service Providers under Section 3A of the IT Act 2000 read with the Second Schedule. The signer authenticates via Aadhaar OTP, the eSign Service Provider issues a one-time certificate valid for 30 minutes, the document hash is signed and the certificate is destroyed. eSign is paperless, requires no USB token, and is admissible as an electronic signature with the same legal standing as a digital signature under Section 5.
Where Aadhaar e-KYC is not feasible, the CCA IVG 2021 permits video verification where the applicant joins a recorded video call with a CA-authorised verifier, displays original PAN and address proof, reads a randomly generated PIN and confirms identity. The recording is retained as part of the audit trail under Section 36(c) read with the IVG.
Yes. The first discussion about your Class 3 DSC requirement is free — call or WhatsApp 9566-068-468 and we will tell you honestly what is involved, what it costs, and the realistic timeline before you commit to anything.
DSCs are services classified under SAC 998313 (information technology consulting and support services) and attract GST at 18%. The CA's invoice will show the fee, USB token cost and 18% GST separately. Where the recipient is GST-registered, full input tax credit on DSC fees is available subject to Section 16 of the CGST Act, including for use in business of company filings, tax filings and tendering.
With Aadhaar e-KYC and a pre-loaded USB token, Class 3 individual DSC is issued within 30-60 minutes of application. Video-KYC issuance typically takes 2-4 working hours during CA business hours. Organisation DSCs with manual document verification take 1-2 working days. Where in-person verification is required, timing depends on the CA's RA presence in the city.
Section 36 lists the duties of the Certifying Authority before issuing a DSC — verify the identity of the applicant, ensure that the public key corresponds to the private key held by the applicant, confirm the information in the certificate is accurate, and that the subscriber holds the private key. Failure to comply attracts liability under Section 39 (suspension/revocation) and Sections 73-74 for fraudulent issuance.
Yes. Under the Companies Act 2013 and the MCA21 portal rules, all e-forms including SPICe+ (incorporation), DIR-3 KYC, AOC-4 (financials), MGT-7 (annual return), INC-22 (registered office), DPT-3 and most other ROC filings require Class 3 DSC of the authorised director or signatory. Form DIR-3 mandates a personal DSC for every director who applies for DIN.

From Arcot Road, Alapakkam Main Road, Sri Devi Kuppam Main Road, 1st Cross Main Road and 1st Main Road through to 1st main road, 2nd Main Road, 3rd Main Road and Perumal Koil Street, our team covers Class 3 DSC for businesses right across Murugesan Salai and its main commercial roads.

Free Consultation Available

Ready for Expert Class 3 DSC in Murugesan Salai?

Professional Class 3 DSC in Murugesan Salai, Chennai. Call @ 9566-068-468. Offices at Maduravoyal, Nerkundram & Nolambur (upcoming). 15+ years experience, 4.9★ rated.

From ₹1,500/one-time
15+ years experience
Zero penalties guaranteed
Maduravoyal · Nerkundram · Nolambur (upcoming)
Call Now WhatsApp