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
Padi Pudunagar Bus Stop catchment · Padi Class 3 DSC

Padi Class 3 DSC — Chennai North

Class 3 DSC for industrial units around TI Cycles (Murugappa Group), Padi — backed by a 15+ year track record

Class 3 DSC for Padi firms under Chennai North (Ambattur Division) — fixed fee, deterministic turnaround and archived working papers. Call 9566-068-468.

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

What is the difference between Class 1 Class 2 and Class 3 DSC historically in Padi, Chennai?

Class 1 was the lowest assurance level used only for email and webmail signing and has been functionally deprecated. Class 2 was issued after pre-verified database identity check and was used for MCA, Income Tax and GST filings till 31 December 2020. Class 3 is the highest assurance level requiring physical or video-based personal verification under the CCA Identity Verification Guidelines and is now the only PKI-based DSC issued in India.

Transparent Pricing

Class 3 DSC in Padi — 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 Padi Clients Choose FilingPro

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

Video KYC Fallback

For Padi applicants whose Aadhaar mobile linkage is inactive, video-based KYC under the IVG 2021 is conducted by a CA-authorised verifier with original PAN and address-proof display. Issuance completes in 2-4 working hours.

FIPS 140-2 USB Token Supplied

ePass2003, Watchdata ProxKey or Trust Key tokens supplied with every DSC — certified to FIPS 140-2 Level 2 (or Level 3 on Premium plan) as mandated by CCA Interoperability Guidelines. The private key cannot be exported or copied.

Class 2 Deprecation Migration

Padi clients holding pre-1-Jan-2021 Class 2 DSCs that have expired or are nearing expiry are migrated to Class 3 with full Aadhaar e-KYC re-verification — no continuity of older Class 2 certificates is permitted under the CCA notification dated 17-Dec-2020.

Authorisation Letter & Board Resolution Drafting

For Padi corporate clients, FilingPro drafts the authorisation letter on the entity's letterhead and the board resolution naming the signatory — accepted format across CCA-licensed CAs for organisation DSC issuance.

Multi-Director Pack Coordination

For Padi companies needing the full board's DSCs (Premium plan — 5 directors), FilingPro coordinates all five Aadhaar e-KYCs sequentially in a single working day with USB tokens preloaded and shipped together.

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.

Key Benefits

What Padi Clients Get

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

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 Padi 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 Padi 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 Padi 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 Padi clients from forged-signature liability.
Section 3A eSign Optionality
Where the use case is one-off signing, Padi clients are routed to Aadhaar eSign under Section 3A IT Act with Schedule II — no token, no driver, just OTP-based 30-minute signing certificate.
18% GST Input Credit on DSC Fee
DSC services are classified under SAC 998313 attracting 18% GST. GST-registered Padi clients claim full input tax credit on professional fees and CA charges under Section 16 CGST Act, lowering effective cost by 18%.
Comparison

Class 3 Signature DSC vs Class 3 Combo DSC

Why this matters here — Padi businesses operate where the cluster of industrial, engineering, residential businesses that defines Padi's commercial fabric, and served by short connections to Ambattur and Korattur 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 Padi 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 — Padi businesses operate where the business activity radiating outward from Padi Flyover 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
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
One-time signing requirement and no Class 3 DSC available (e-Sign alternative)On due dateAadhaar e-Sign single-use signature under Section 3A of the IT Acte-Sign generates and destroys the signing key in a single transaction — no token, no renewal, no recovery; suitable as a stop-gap for one-off filings but not for repeat use because each invocation is a fresh transaction
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
Hardware token develops a read-error or LED-failure under warrantyOn due dateHardware-replacement ticket with issuing CA / token vendor; existing certificate re-keyed onto replacement tokenReplacement within 1-3 working days under standard 1-year hardware warranty preserves the existing certificate validity; out-of-warranty failures require fresh DSC issuance
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

Deadline pressure points we see in Padi: Closer to Padi, for Padi units balancing production cycles with monthly GST and quarterly TDS compliance.

Forms Library

Forms used in this engagement

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.

Board resolution authorising designated signatory to obtain certificate for entity filings.

Entity GSTIN proof submitted for organisation class certificates linked to company filings.

Mandatory identity document cross-verified with Income Tax database during application processing.

Recent colour photograph affixed on physical application or uploaded for digital workflow.

Subscriber recites application reference number on camera fulfilling identity proofing requirement.

Class 3 DSC in Padi, Chennai 600050

Statutory correspondence for Padi businesses routes through the Ambattur Division, so we align every Class 3 DSC engagement to that jurisdiction from the start. Every Padi engagement we open begins with the basics: PIN 600050, the Ambattur Division, and the coordinates 13.1031, 80.1924 that anchor the locality. Padi is an industrial-residential locality anchored by Murugappa Group's TI Cycles plant and several engineering units. GST clients include manufacturing units, B2B engineering supplies and supporting retail. We keep a cycle-by-cycle record of how the Ambattur Division of the Chennai North handles Padi filings and approvals.

Document pickup near Padi Pudunagar is a same-hour errand for our Padi engagements rather than the half-day a typical Chennai client expects. Padi sustains a high flow of commerce for a industrial residential mixed locality, and that flow is the raw material for the Class 3 DSC files we close here. Padi reads as a industrial residential mixed pocket with high commercial activity, anchored around Padi Pudunagar and fed by the Padi Pudunagar Bus Stop corridor. The industrial residential mixed mix of Padi shapes what lands in our workpapers — a blend of engineering activity and the commercial pulse around Padi Pudunagar.

The residential character of Padi commerce influences everything from invoice formats to the supporting documents a Class 3 DSC review needs. The residential firms we serve in Padi value a Class 3 DSC partner who already understands their sector's compliance rhythm. A residential operator in Padi gets a Class 3 DSC workflow shaped by sector norms, not a one-size-fits-all template. Mixed residential activity across Padi means our Class 3 DSC team keeps sector playbooks ready rather than improvising per client.

Our Padi Class 3 DSC process is built to be predictable, documented, and on time, cycle after cycle. The qualified-review step on every Padi Class 3 DSC file is where errors get caught before they reach the portal. A Padi client sees the same Class 3 DSC cadence each cycle: intake, reconciliation, review, filing, acknowledgement. From the first Class 3 DSC cycle, a Padi engagement is set up to be audit-ready rather than reconstructed under pressure later.

Class 3 DSC clients in Korattur are handled by the same practitioners who run our Padi desk. Coverage from Padi naturally extends to Korattur, so group entities across the area share one Class 3 DSC workflow. A client relocating between Padi and Korattur keeps the same Class 3 DSC file and the same team. Group companies spread across Padi and Korattur consolidate their Class 3 DSC under one engagement with us.

Each engagement in Padi adds to a record of what the Chennai North jurisdiction expects, sharpening the next Class 3 DSC file. The Class 3 DSC mistakes we see most in Padi are avoidable with disciplined intake, which our checklist enforces. Common patterns in the Ambattur Division give Padi businesses an early-warning map we use to pre-empt Class 3 DSC issues. Because we work repeatedly across Padi, we can benchmark a new client's Class 3 DSC position against the locality norm.

Relocating a registered office into Padi (PIN 600050) changes the assessing division, and we handle that Class 3 DSC transition cleanly. New residential ventures in Padi lean on us to stand up Class 3 DSC correctly before the first deadline rather than after a notice. Shifting principal place of business to Padi means updating jurisdiction to the Chennai North, and we manage the paperwork end-to-end. First-time Class 3 DSC for a Padi business is where getting the basics right saves years of cleanup later.

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

Class 3 DSC in Padi — Complete Guide

Class 3 DSC is a long-term certificate (1/2/3 year validity) on a FIPS 140-2 USB token used for repeated MCA, GST, TRACES and tender signing. Aadhaar eSign under Section 3A of the IT Act 2000 is a one-time 30-minute certificate suitable for single-document signing without hardware. FilingPro evaluates Padi clients' use cases and recommends the right tool — frequently both, with Class 3 for compliance filings and eSign for one-off agreements.

Class 3 DSC in Padi, Chennai

Class 3 Digital Signature Certificates issued in Padi 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 Padi — Director / ITR Signing

Class 3 individual DSC for Padi 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 Padi — GST / TRACES / IceGate

Class 3 organisation DSC for Padi 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 Padi. 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 Padi
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 Padi clients.
Paperless Aadhaar OTP e-KYC under CCA Identity Verification Guidelines 2021 — same-day issuance with no physical document movement for Padi 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 Padi 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 Padi 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 Padi
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 Padi?
With Aadhaar OTP e-KYC and a pre-loaded FIPS 140-2 USB token, Class 3 individual DSC for Padi 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 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 validity period should I choose for a Class 3 DSC?

Class 3 DSCs are issued for 1, 2 or 3 years. A 2-year term is the common choice — it balances cost against re-verification effort. The certificate cannot be extended; a fresh e-KYC is required at renewal, so renew a few days before expiry to avoid a filing block.

Can one Class 3 DSC be used on multiple government portals?

Yes. A single Class 3 signature DSC works across MCA21 V3, GST, Income-tax, TRACES, EPFO, ICEGATE and DGFT once registered on each portal. It must be registered under the correct role on each site — for example mapped to the authorised signatory on the GST portal under Rule 26.

What Padi clients want to know before signing: Closer to Padi, in the industrial-residential mixed micro-market of Padi.

Expert Guide

A complete walkthrough — Class 3 Dsc

Reading this guide locally — Padi businesses operate where on the Ambattur-Korattur corridor that passes through Padi.

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 Padi clients usually ask next: Closer to Padi, for Padi units balancing production cycles with monthly GST and quarterly TDS compliance.

Glossary

Plain-English glossary for this service

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.

Certifying Authority

Licensed entity under Section 24 authorised to issue suspend and revoke digital signature certificates.

Controller of Certifying Authorities

Apex regulator under Section 17 supervising licensing audit and root certificate operations across India.

Root Certificate

Self-signed top-level certificate anchoring trust chain operated by Controller signing all licensed Certifying Authority certificates.

Subscriber

Natural person or organisational representative in whose name certificate is issued holding signing key responsibility.

By Industry

Industry-specific patterns in Padi

How the local trade mix shapes this — Padi businesses operate where the cluster of industrial, engineering, residential businesses that defines Padi's commercial fabric.

Retail Trade
Common issue: Retail chains incorporated as private limited companies routinely require Class 3 DSCs for multiple directors to file MCA21 v3 forms such as DIR-3 KYC, AOC-4 and MGT-7, but procure only Individual-category certificates rather than Organisation-category, on the misunderstanding that the certificate type is irrelevant. MCA21 v3 introduced in 2023 strengthened the signature-verification logic to require an Organisation-type certificate with the company's CIN reflected in the Organisation Unit field of the X.509 subject for filings made on behalf of the company, while continuing to accept Individual-type for personal-capacity filings such as DIR-3 KYC.
How we handle it: Procure Class 3 Organisation DSCs for each director-signatory with the company name and CIN captured in the Organisation and Organisation Unit fields of the X.509 Subject Distinguished Name, using the issuing CA's Organisation-verification process that requires the certificate of incorporation, board resolution authorising the signatory and PAN of the company; retain Class 3 Individual DSCs for personal filings such as DIR-3 KYC; maintain a director-wise DSC register to track which director holds which category of certificate against which prescribed filing.
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.
Case Studies

Anonymised engagements we have handled

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

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.
Inventory auditCA Firm

13 stale DSCs in firm inventory — quarterly audit recovered ₹19,500 of latent licensing

Issue: A mid-sized firm with 60 active client signatories had accumulated 13 tokens in the office locker — 7 expired, 4 unused due to client offboarding, and 2 of unknown attribution. No central register existed mapping tokens to client / certificate / expiry / signatory. Risk of latent Section 38 exposure if any expired or orphaned token was inadvertently re-used.
Approach: Conducted a 1-day token-inventory audit. For each token, ran the manufacturer utility to read the certificate metadata (subject-CN, issuer-CN, validity dates, key-usage), cross-mapped to client records. 7 expired tokens were physically destroyed under a 2-witness protocol with destruction certificates. 4 client-offboarded tokens were returned to clients with handover acknowledgments. 2 unattributable tokens were revoked through the issuing CA under abundant-caution Section 38 filings.
Outcome: Token inventory reduced from 13 to 0 stale units; 5 client signatories migrated to fresh 2-year DSCs at ₹1,500 each yielding ₹7,500 of firm revenue plus ₹12,000 of token margin; central token register implemented with quarterly audit cadence; zero unmapped tokens in subsequent 2 audit cycles.
Validity expiryCorporate Compliance

DSC validity expired mid-AOC-4 filing — 6 of 18 March-31 deadline filings hit late fee

Issue: An 18-company audit portfolio was being uploaded on MCA V3 between 25-March and 31-March. On 28-March the director DSC of a holding-company nominee, common across 6 group entities, expired. The expiry date had been masked in the token-listing utility because the renewal reminder had been sent to a resigned employee's email. Six AOC-4 filings stalled with the 'DSC not valid' error mid-upload. Per-day delay penalty under Section 403 is ₹100 per company per day with no upper limit.
Approach: Triggered fresh Class 3 paperless e-KYC issuance with eMudhra under Aadhaar OTP for same-day delivery; parallelly re-validated the director DIN-DSC association on MCA after the new certificate was downloaded into a fresh ePass token. Used the affidavit-based delay-condonation reasoning in the cover note while uploading on 29-March. For 2 entities where the auditor DSC was also stale, refreshed both signatories through video-verification e-KYC the same evening with a 1-day SLA.
Outcome: 5 of 6 AOC-4 forms uploaded on 29-March with the new DSC, escaping any per-day penalty; 1 entity slipped 1 day attracting ₹100 fee; no Section 92 delay because MGT-7 was already filed; new 2-year DSC validity captured in the firm's compliance calendar with 45-day pre-expiry alerts.
Token lossTendering

Lost ePass token containing live DSC — Section 38 suspension filed within 4 hours

Issue: A government-tendering proprietor lost his ePass 2003 USB token on a flight transit. The token held a 22-month-remaining Class 3 organisational DSC mapped to GeM and CPPP portals worth ₹4.6 crore of active bid commitments. Public-key fingerprint of the lost DSC was already on 3 live tender PDFs. Risk of mis-use under Section 66C of the IT Act and bid-bond forfeiture if a competing bidder picked up and signed.
Approach: Within 4 hours of loss, filed Section 38 IT Act suspension request with the issuing CA (eMudhra) supported by an FIR copy filed at the originating airport police station. Triggered the CRL (certificate revocation list) update so any document signed after the suspension hour would fail signature-verification. Parallelly applied for a fresh Class 3 DSC under paperless e-KYC with same-day issuance on a fresh FIPS 140-2 Level 2 hard token. Mapped the new DSC to GeM and CPPP portals on day 2 and re-signed all 3 live bid PDFs with the new key.
Outcome: Lost DSC entered CRL within 6 hours; no fraudulent signature surfaced in the next 90 days; 3 live bids re-signed with the new key before the bid-opening date; ₹4.6 crore tender pipeline preserved; firm now mandates dual-token policy for all bid-signing directors.

Why these Padi engagements look the way they do: Closer to Padi, the business activity radiating outward from Padi Flyover and nearby commercial pockets, which is why for Padi units balancing production cycles with monthly GST and quarterly TDS compliance.

Client Reviews

What Padi 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 — Padi

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

Class 1 was the lowest assurance level used only for email and webmail signing and has been functionally deprecated. Class 2 was issued after pre-verified database identity check and was used for MCA, Income Tax and GST filings till 31 December 2020. Class 3 is the highest assurance level requiring physical or video-based personal verification under the CCA Identity Verification Guidelines and is now the only PKI-based DSC issued in India.
Under the CCA Identity Verification Guidelines 2021, DSCs can be issued through paperless e-KYC where the applicant authenticates using Aadhaar OTP via the UIDAI gateway and a video selfie is captured. The CA receives the e-KYC response from UIDAI, matches the live photograph and issues the DSC the same day with no physical document movement.
Padi (PIN 600050) falls under the Ambattur Division, Chennai North commissionerate. Getting the jurisdiction right matters because registrations, filings and notices are routed through the correct office. We confirm and handle the right jurisdiction for every Padi engagement.
Online Certificate Status Protocol (OCSP) defined in RFC 6960 is a real-time alternative to CRL where a relying party queries the CA's OCSP responder for the status of a single certificate and receives an immediate "good", "revoked" or "unknown" response. CCA-licensed CAs operate OCSP responders alongside CRL publication and many e-government portals use OCSP for real-time signature verification.
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.
Yes, we regularly take over part-completed Class 3 DSC work. Share what has been done so far on WhatsApp 9566-068-468 and we will review it, point out anything that needs correcting, and continue from where you are.
A digitally signed electronic record is admissible in evidence under Section 65B of the Indian Evidence Act 1872 read with Section 5 of the IT Act 2000. The Supreme Court in Anvar P.V. v. P.K. Basheer (2014) 10 SCC 473 held that a Section 65B(4) certificate is mandatory for electronic records, and in Arjun Panditrao Khotkar v. Kailash Kushanrao Gorantyal (2020) 7 SCC 1 reaffirmed the mandatory nature of the certificate, overruling Shafhi Mohammad.
No. The CCA notified vide circular dated 17 December 2020 the discontinuation of Class 2 DSCs effective 1 January 2021. From that date only Class 3 DSCs are issued by licensed CAs. Aadhaar-based eSign under Section 3A continues as a parallel paperless mechanism. Existing Class 2 DSCs continued only till expiry of their original validity and have not been renewed since 1-Jan-2021.
Yes — we handle Class 3 DSC for individuals and businesses across Padi (PIN 600050) and nearby Korattur. The work is done end-to-end by our own team, with documents collected online over WhatsApp or email and in-person meetings available at our Maduravoyal and Nerkundram offices. Call 9566-068-468 to begin.
DSCs come in two functional types — signing (used for digital signatures and authentication) and encryption (used to encrypt documents that only the certificate holder can decrypt). For tendering on CPPP and GeM both signing and encryption certificates are typically required. Encryption certificates do not produce a signature in the legal sense; their statutory framework is the IT Act's broader provisions on secure electronic records.
Section 38 of the IT Act 2000 governs revocation. Grounds include compromise of the private key, request by the subscriber, change of employment for organisation DSCs, death of the subscriber, or material change in information. The subscriber files a revocation request with the issuing CA who publishes the certificate to the Certificate Revocation List (CRL) and updates OCSP within the timelines set in the CCA's Interoperability Guidelines.
We keep payment simple for Padi clients — pay digitally by UPI or bank transfer against a proper invoice. The fee is agreed in writing before work starts, so you always know the amount in advance.
For Class 3 individual DSC the applicant submits: PAN of the applicant, Aadhaar (with linked mobile for OTP) or alternative photo ID and address proof, recent passport-size photograph, mobile and email for OTP confirmation, and a signed application form. With Aadhaar e-KYC the entire process is paperless. The applicant must hold a personal mobile number registered with UIDAI for OTP delivery.
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.
A lost or damaged token containing a valid DSC must be reported to the issuing CA who will revoke the DSC and add it to the CRL. A fresh USB token is purchased, full Aadhaar e-KYC re-verification is performed and a new DSC is issued. The previous certificate cannot be "transferred" to the new token because the private key is hardware-bound and was destroyed with the lost device.
USB tokens use a token-PIN that is set during driver installation. After 5-10 incorrect PIN attempts (manufacturer-specific) the token gets locked. Watchdata ProxKey and ePass2003 provide an admin PIN reset utility — if the admin PIN is also lost, the token must be re-initialised which destroys the existing DSC. A fresh DSC issuance with full re-verification is then required. There is no way to recover a destroyed DSC private key.

We serve businesses in every part of Padi, from 18th Main Road, 3rd Main Road, Park Road, SIDCO Industrial Road and SIDCO Nagar 4th Main Road to the School Road, Chennai - Tiruttani - Renigunta Road, Jawaharlal Nehru Road (100 Feet Road) and New Avadi Road commercial pockets, with Class 3 DSC handled end to end.

Free Consultation Available

Ready for Expert Class 3 DSC in Padi?

Professional Class 3 DSC in Padi, 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