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
CCA-Licensed Class 3 DSC · George Town

George Town Class 3 DSC for wholesale Businesses

Class 3 DSC cadence for George Town firms near Parrys Bus Terminus — handled by a qualified, in-house team

George Town wholesale and hardware units around Parry's Corner by qualified experts with a 15+ year, zero-penalty record. 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 George Town, 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 George Town — 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 George Town Clients Choose FilingPro

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

Aadhaar eSign Where DSC Is Overkill

Where a George Town 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. George Town 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. George Town clients receive certificates that pass CRL/OCSP validation on every government portal.

Paperless Aadhaar OTP e-KYC

Identity verification under the CCA IVG 2021 is completed via Aadhaar OTP authentication and a 30-second video selfie. George Town clients with Aadhaar-linked mobile complete the entire process on WhatsApp and receive the DSC within an hour.

Video KYC Fallback

For George Town 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.

Key Benefits

What George Town Clients Get

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

DGFT IEC and Customs IceGate Filing
Class 3 organisation DSC enables George Town 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 George Town 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 George Town clients from forged-signature liability.
Section 3A eSign Optionality
Where the use case is one-off signing, George Town 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 George Town clients claim full input tax credit on professional fees and CA charges under Section 16 CGST Act, lowering effective cost by 18%.
Same-Day MCA / GST / Tender Readiness
With paperless Aadhaar e-KYC, Class 3 individual DSC is issued in 30-60 minutes — George Town clients can file SPICe+, DIR-3 KYC or sign tender bids the same business day.
Comparison

Class 3 Signature DSC vs Class 3 Combo DSC

Why this matters here — In George Town, the business activity radiating outward from Parry's Corner and nearby commercial pockets; with quick access via Parrys Bus Terminus and feeder routes connecting George Town to the rest of Chennai.

AspectClass 3 Signature DSCClass 3 Combo DSC
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
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
Documents Required

Documents for Class 3 DSC

Share documents via WhatsApp to 9566-068-468. No office visit required for George Town 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 — In George Town, the cluster of wholesale, hardware, books businesses that defines George Town's commercial fabric.

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
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
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 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
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
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 George Town: For George Town engagements specifically — for George Town units balancing production cycles with monthly GST and quarterly TDS 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 George Town, Chennai 600001

Businesses registered in George Town share the Chennai North jurisdiction, and their statutory matters route through the same Sowcarpet Division each time. Every George Town engagement we open begins with the basics: PIN 600001, the Sowcarpet Division, and the coordinates 13.0925, 80.2880 that anchor the locality. For Class 3 DSC at PIN 600001, understanding the Sowcarpet Division's documentation norms removes most of the friction from the process. Because PIN 600001 sits inside the Chennai North jurisdiction, the handling office for George Town stays consistent across years, which matters when filings or approvals span cycles.

Most commerce in George Town — invoices, expenses, purchases and statutory records — eventually surfaces in the Class 3 DSC working file we maintain for clients here. Freight and foot traffic from the Parrys Bus Terminus hub pull steady daily commerce through George Town, so there is rarely a quiet filing month in this wholesale heart of tamil nadu pocket. Each Class 3 DSC cycle for George Town reflects its commercial rhythm — invoices generated near Sowcarpet, expenses routed through the Parrys Bus Terminus freight network. George Town sustains a very high flow of commerce for a wholesale heart of tamil nadu locality, and that flow is the raw material for the Class 3 DSC files we close here.

The textile firms we serve in George Town value a Class 3 DSC partner who already understands their sector's compliance rhythm. A textile operator in George Town gets a Class 3 DSC workflow shaped by sector norms, not a one-size-fits-all template. For a textile business in George Town, the Class 3 DSC scope is rarely generic; we tailor the checklist to how that sector actually transacts. The textile character of George Town commerce influences everything from invoice formats to the supporting documents a Class 3 DSC review needs.

Document intake for George Town clients runs over WhatsApp, so there is no office visit and no paper shuffle for a Class 3 DSC engagement. Working papers for George Town Class 3 DSC engagements stay archived and retrievable, which makes any later notice or query straightforward to answer. Turnaround for George Town Class 3 DSC is deterministic — fixed fee, a scoped timeline, and a same-business-day acknowledgement once filed. We keep a repeatable Class 3 DSC checklist for George Town so nothing in the cycle is improvised or missed.

From the same George Town team we also serve Royapuram and other nearby localities without re-onboarding clients. Coverage from George Town naturally extends to Royapuram, so group entities across the area share one Class 3 DSC workflow. Proximity to Royapuram means a George Town engagement can extend across the locality cluster with no change in cadence. We treat George Town and Royapuram as one catchment for Class 3 DSC, which keeps documentation and turnaround consistent.

Patterns we track for George Town include spices documentation gaps, timing mismatches, and the questions the Sowcarpet Division tends to raise. The Class 3 DSC mistakes we see most in George Town are avoidable with disciplined intake, which our checklist enforces. Because we work repeatedly across George Town, we can benchmark a new client's Class 3 DSC position against the locality norm. The longer we serve George Town, the more precisely we predict where a Class 3 DSC file needs attention.

For a new business incorporating in George Town or shifting its principal place of business here, Class 3 DSC setup is one of the first things to get right. Shifting principal place of business to George Town means updating jurisdiction to the Chennai North, and we manage the paperwork end-to-end. New hardware ventures in George Town lean on us to stand up Class 3 DSC correctly before the first deadline rather than after a notice. First-time Class 3 DSC for a George Town 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 George Town — 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. George Town 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 George Town, Chennai

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

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

Class 3 organisation DSC for George Town 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 George Town. 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 George Town
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 George Town clients.
Paperless Aadhaar OTP e-KYC under CCA Identity Verification Guidelines 2021 — same-day issuance with no physical document movement for George Town 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 George Town 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 George Town 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 George Town
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 George Town?
With Aadhaar OTP e-KYC and a pre-loaded FIPS 140-2 USB token, Class 3 individual DSC for George Town 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 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 happens if my Class 3 DSC token is lost or damaged?

The certificate on a lost or corrupted FIPS token cannot be recovered — the private key never leaves the device by design. You must apply for a fresh certificate with new e-KYC and re-register it on every portal. Report misuse risk to the issuing Certifying Authority for revocation.

Can an NRI or foreign national obtain a Class 3 DSC?

Yes. A foreign national or NRI can obtain a Class 3 DSC using an apostilled or consular-attested passport and address proof, with video verification. Indian PAN is required where the DSC is used for MCA or Income-tax filings; DIN-linked director DSCs additionally need the PAN or passport on record with the MCA.

What George Town clients want to know before signing: For George Town engagements specifically — on the Royapuram-Sowcarpet corridor that passes through George Town.

Expert Guide

A complete walkthrough — Class 3 Dsc

Reading this guide locally — In George Town, on the Royapuram-Sowcarpet corridor that passes through George Town.

What is a Class 3 Digital Signature Certificate

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.

Class 3 versus retired Class 2 certificates

Historically, DSCs were issued in three classes — Class 1, Class 2 and Class 3 — corresponding to progressively higher levels of identity verification. Class 1 was issued on the basis of an email-address verification alone and was suitable for low-value transactions. Class 2 was issued on the basis of identity-document and address-document verification and was the workhorse certificate for income-tax e-filing, MCA21 and most government portals for over a decade. Class 3 has historically required in-person verification or video-verification with biometric authentication and was reserved for high-value transactions such as e-tendering and e-procurement. The CCA's Office Order of 28-12-2020 mandated the discontinuance of Class 2 DSC from 01-01-2021, leaving Class 3 as the single class of DSC for all use-cases. The transition was completed by mid-2021 with the entire ecosystem migrated to Class 3 by issuing CAs.

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.

Revocation and the Certificate Revocation List

Compromised-key protocol

Where the subscriber has reason to believe that the private key associated with the Class 3 DSC has been compromised (lost token, stolen token, suspected malware on the host machine, or exposure of the token PIN to an unauthorised person), the subscriber must immediately initiate revocation under Section 38 and notify the issuing CA. Most issuing CAs offer a twenty-four-hour helpline for emergency revocation initiation. The compromised-key protocol involves: (a) immediate revocation request on the CA's portal or helpline, (b) the CA's publication of the revoked serial number on the CRL and OCSP responder within twenty-four hours (typically much faster), (c) the subscriber's review of all documents signed during the compromise window to identify any unauthorised signings, and (d) procurement of a fresh certificate to restore signing capability.

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.

Comparative international frameworks

Singapore Electronic Transactions Act 2010

Singapore's Electronic Transactions Act 2010 (which replaced the earlier ETA 1998) is one of the most cleanly-drafted electronic-transactions statutes in the Asia-Pacific region and adopts the UNCITRAL Model Law on Electronic Commerce 1996 and the UNCITRAL Model Law on Electronic Signatures 2001 substantially verbatim. The ETA 2010 establishes a Secure Electronic Signature standard analogous to the AES under eIDAS, and provides for mutual recognition of foreign electronic signatures under Section 8 where the foreign signature is shown to be reliable. The Section 8 reliability assessment looks at factors including the sophistication of the equipment, the nature of the transaction, the parties' course of dealing and any consent provided. India Class 3 DSCs are routinely accepted in Singapore-governed commercial transactions under this Section 8 reliability framework.

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.

Use-cases for Class 3 DSC in Indian compliance

MCA21 v3 corporate filings

The MCA21 v3 portal launched by the Ministry of Corporate Affairs in 2023 (replacing the earlier MCA21 v2 platform that had been in operation since 2006) is one of the most extensive consumers of Class 3 DSC in India. Every form filed on MCA21 v3 — DIR-3 KYC, AOC-4, MGT-7, INC-22, MGT-14 and the numerous transactional and event-based forms — requires a Class 3 DSC of the authorised signatory and the certifying professional. The v3 architecture introduced strengthened signature-verification logic including SHA-256 hashing under PKCS#7 detached signature format, OCSP-based real-time revocation check (replacing the v2 platform's daily-CRL-cache approach), and Subject DN-to-MCA-record matching at the form-validation stage, reducing the incidence of post-filing rejection but increasing the importance of pre-filing DSC-environment validation.

GST portal and e-invoice signing

The Goods and Services Tax Network (GSTN) portal accepts Class 3 DSC for authentication of registration applications (REG-01, REG-14), return filings (GSTR-1, GSTR-3B, GSTR-9, GSTR-9C), refund claims (RFD-01) and the various notice-reply workflows. For companies and LLPs, Class 3 DSC is mandatory; for other entity types (proprietorships, HUF), Aadhaar-based e-Sign is permitted as an alternative. The GST e-invoice framework introduced under Notification 13/2020-Central Tax and operationalised from 01-10-2020 requires invoices generated by notified taxpayers to be digitally signed by the Invoice Registration Portal (IRP) using its own Class 3 Document Signer Certificate before the signed JSON is returned to the taxpayer with an Invoice Reference Number (IRN). The architecture preserves the taxpayer's option to also affix their own Class 3 DSC on the underlying invoice for additional evidentiary weight.

Income-tax e-filing and ITBA

The Income Tax Department's e-filing portal accepts Class 3 DSC for filing ITR-5 (LLPs and firms), ITR-6 (companies) and ITR-7 (trusts and societies), where DSC authentication is mandatory; for individual returns and HUF returns, Aadhaar-based e-Sign and Electronic Verification Code (EVC) are permitted alternatives. The Department's internal Income Tax Business Application (ITBA) accepts Class 3 DSC from authorised representatives and chartered accountants in proceedings under Section 144B (faceless assessment), Section 250 (faceless appeal) and Section 274 (faceless penalty), where the authorised representative's professional DSC carries evidentiary weight against the assessing officer's digitally-signed assessment order. The 2024-25 transition to fully electronic assessment proceedings has accelerated the need for chartered accountants and lawyers to maintain valid Class 3 DSCs as a professional-practice requirement.

What George Town clients usually ask next: For George Town engagements specifically — for George Town units balancing production cycles with monthly GST and quarterly TDS compliance.

Glossary

Plain-English glossary for this service

Encryption certificate

The X.509 certificate inside a DSC token whose Key Usage extension permits 'dataEncipherment' and 'keyEncipherment'. It is used to encrypt documents or e-mails to the certificate holder such that only the corresponding private key can decrypt them. The encryption certificate cannot be used to apply a digital signature on a return or form even though it resides on the same token.

Individual DSC

A Class 3 DSC issued in the personal name of the applicant where the subject-CN carries the individual's name and PAN. Used by proprietors, professionals, partners signing in personal capacity, and directors signing on their own (DIR-3 KYC for example). The certificate does not associate the holder with any organisation.

Organisational DSC

A Class 3 DSC issued in the name of an authorised individual but associating him to a specific organisation through the Organisation (O) and Organisational Unit (OU) attributes in the subject distinguished name. Used by company authorised signatories, LLP designated partners and society office bearers. Issuance requires a board resolution or authorisation letter and the certificate's organisational validity tracks the underlying authorisation.

Aadhaar OTP e-KYC

The fastest issuance route for a Class 3 DSC where the applicant's identity is verified through a one-time password sent to the Aadhaar-registered mobile. Subject to Aadhaar biometric-lock status being open, the DSC can be issued on the same day. Requires PAN-Aadhaar linkage status to be 'operative' and the registered mobile to be reachable at the time of OTP.

Video verification e-KYC

Issuance route for a Class 3 DSC where the applicant records a short verification video reading an OTP and displaying PAN and Aadhaar documents. Used when Aadhaar OTP route is unavailable due to biometric lock, mobile-number mismatch or NRI status. Standard SLA is 1-2 working days and is the only route available for many organisational and NRI applications.

USB token FIPS 140-2 Level 2

Cryptographic hardware token compliant with the United States National Institute of Standards Federal Information Processing Standard 140-2, Security Level 2. The CCA mandates that all Class 3 DSCs be stored on a FIPS 140-2 Level 2 (or higher) certified hardware token. The private key never leaves the token and signing operations are performed inside the token's secure element.

ePass

A widely used FIPS 140-2 Level 2 USB cryptographic token manufactured by Feitian, sold in India as ePass 2003 and ePass 2003 Auto. Compatible with all major Indian Certifying Authorities and supports the standard PKCS#11 interface used by browser plug-ins and signing utilities on MCA, GST and IT portals.

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.

By Industry

Industry-specific patterns in George Town

How the local trade mix shapes this — In George Town, the business activity radiating outward from Parry's Corner and nearby commercial pockets.

Logistics and Warehousing
Common issue: Logistics and warehousing operators registered on the e-Way Bill portal, the FASTag commercial-vehicle portal and the National Logistics Portal (Marine) frequently require Class 3 DSC for periodic compliance filings and dispute responses. Multi-state logistics aggregators face the additional complication that the e-Way Bill portal under Rule 138 of the CGST Rules accepts e-Sign as a permitted alternative to Class 3 DSC for most filings but reverts to mandatory DSC-only for cancellation requests and bulk-generation workflows beyond specified thresholds.
How we handle it: Map each high-volume filing to its prescribed authentication method (e-Sign permitted vs Class 3 DSC mandatory) by reference to the e-Way Bill API documentation, the FASTag commercial-vehicle portal user manual and the NLP-Marine portal terms; procure a Class 3 DSC of the operations manager or compliance officer (whoever has standing authority under the corporate authorisation matrix) with appropriate Organisation tagging; consider Document Signer Certificate on HSM for very-high-volume e-Way-Bill generation where the operator's monthly volume exceeds the e-Sign throughput limit.
Financial Services
Common issue: NBFCs registered with the RBI, fintech firms and insurance brokers frequently require Class 3 DSC for filings on the RBI's COSMOS portal, IRDAI's BAP portal and the SEBI SCORES system. The financial-services sector's signature requirements are governed by sector-specific regulations including the RBI's Master Direction on Digital Signing (2023) which mandates Class 3 Combo DSC with FIPS 140-2 Level 2 token storage and the additional requirement that the certificate's Subject DN include the entity's RBI Certificate of Registration (CoR) number in the Subject Alternative Name field for NBFCs.
How we handle it: Procure Class 3 Combo Organisation DSCs for each authorised signatory captured in the RBI/IRDAI/SEBI authorised-signatory list; instruct the issuing CA to include the RBI CoR number, IRDAI registration number or SEBI registration number in the Subject Alternative Name field; store the tokens in physical safe custody under the entity's Information Security Policy aligned to the RBI Master Direction on IT Outsourcing 2023; document the DSC-procurement, token-issuance, certificate-renewal and revocation events in the audit trail expected at the next RBI/IRDAI/SEBI inspection.
Agro-processing
Common issue: Food-processing, dairy-processing and agro-input units registered with FSSAI as central licensees and with the Ministry of Food Processing Industries under the Pradhan Mantri Kisan Sampada Yojana scheme require Class 3 DSC for the FoSCoS portal, the PMKSY claim portal and the FCI procurement portal. Agro-processors operating during the seasonal procurement window face high-volume document signing requirements compressed into a short period, often discovering at peak season that their existing single-signatory DSC throughput is insufficient.
How we handle it: Procure Class 3 Combo Organisation DSCs for each of the principal authorised signatory and at least one backup signatory at least sixty days before the procurement season; consider a Class 3 Document Signer Certificate on HSM for unattended bulk signing of procurement-receipt acknowledgements where the daily volume exceeds two hundred documents; reconcile the FSSAI FBO-licence number, the PMKSY beneficiary identifier and the FCI vendor code with the Subject Alternative Name of the certificate to ensure straight-through portal authentication.
IT Services
Common issue: Software development firms and IT consultancies operating as private limited companies frequently procure individual Class 3 DSCs for their authorised signatories without realising that MCA21 v3 filings under the Companies Act 2013 routinely require both signatory and professional certifications, and that DGFT IEC filings, GST authentication and EPFO ECR submissions each accept different certificate variants. The fragmented procurement leads to mid-filing failures because the cryptographic key-usage extensions under X.509 v3 differ between signing-only and signing-plus-encryption certificates issued under the ETSI EN 319 411 baseline that India CAs adopted from 2018.
How we handle it: Procure a Class 3 Combo (Signing plus Encryption) DSC for each director-signatory under the eMudhra, Sify, NCode, Capricorn, Verasys, ProDigital or IDsign hierarchy that maps to the Controller of Certifying Authorities (CCA) root under Section 17 of the IT Act 2000; specify Organisation-type certificate where the company name is to appear on the Subject Distinguished Name field of the X.509 certificate; preserve the FIPS 140-2 Level 2 USB cryptographic token securely and avoid drive-letter sharing across machines to prevent the CCA-CRL flagging the certificate for suspected key-compromise.
IT Services
Common issue: SaaS and ITeS exporters issuing Software Technology Parks of India (STPI) softex declarations and DGFT shipping-bill amendments often use the same Class 3 DSC token across multiple authorised signatories on a shared workstation, treating the cryptographic key-pair as a generic office password rather than a personal credential. The IT (Amendment) Act 2008's Section 3A treats the private key as legally equivalent to the subscriber's handwritten signature, and the CCA's Identity Verification Guidelines 2018 (revised 2022) make the subscriber personally liable for any document signed using that key, leaving the company exposed in contract-authenticity and bank-mandate disputes.
How we handle it: Allocate one Class 3 DSC token per authorised signatory under the e-KYC process notified by the CCA in line with the Aadhaar-based paperless onboarding framework introduced in 2018; record the issued certificate's serial number, validity dates and key-usage extensions in the company's DSC register; revoke the certificate immediately on signatory exit through the issuing CA's revocation portal so that the certificate is added to the CRL and OCSP responder under RFC 6960 within twenty-four hours, foreclosing residual signing capability.
Case Studies

Anonymised engagements we have handled

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

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.
e-KYC failureProfessional Services

Aadhaar OTP e-KYC failed on biometric lock — switched to video verification same evening

Issue: A 64-year-old practising chartered accountant applied for a fresh 2-year Class 3 DSC for GST and IT-portal signing 2 days before his existing certificate's expiry. The Aadhaar OTP e-KYC route failed at the biometric-lock stage because the applicant had locked his Aadhaar biometrics on UIDAI 3 years earlier and forgotten the unlock PIN. The unlock-PIN reset itself takes 1-2 working days, but the practitioner had 11 GST returns and 4 ITR uploads scheduled in the next 48 hours.
Approach: Switched the application from Aadhaar OTP route to video-verification e-KYC same evening with a Class 3 sub-CA (Sify). Pre-recorded the verification video reading the OTP and showing PAN and Aadhaar card in a single take. Submitted within the 1-2 day SLA window. In parallel filed the UIDAI biometric-unlock request as fallback. Loaded the new DSC onto a fresh MTok token and tested digital-signing on the GST portal before the first morning return upload.
Outcome: DSC issued within 22 hours through video verification; 11 GST returns and 4 ITR uploads completed within the 48-hour scheduling window; no late fees on any return; biometric unlock arrived 2 days later as the secondary recovery channel; old DSC let to expire naturally without revocation cost.

Why these George Town engagements look the way they do: For George Town engagements specifically — the business activity radiating outward from Parry's Corner and nearby commercial pockets; for George Town units balancing production cycles with monthly GST and quarterly TDS compliance.

Client Reviews

What George Town 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 — George Town

Common questions from George Town 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.
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.
Yes. Getting Class 3 DSC right early saves small George Town businesses from penalties and rework later, and our fixed, modest fees are designed with smaller operators in mind. We will tell you honestly if something is not needed yet.
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.
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 main office is at Plot No. 6, Alapakkam Main Road (opposite KVB Bank), Maduravoyal – 600095, with a branch at No. 22 Reddy Street, Nerkundram – 600107. Both are an easy reach from George Town, and a third office at Nolambur is opening shortly. Most clients, though, never need to visit.
FIPS 140-2 is the United States NIST standard for cryptographic modules. CCA mandates that the private key of a Class 3 DSC be stored on a hardware crypto-token certified to FIPS 140-2 Level 2 (or higher) — the certificate cannot be exported, copied or backed up from the token. Approved tokens include Watchdata ProxKey, ePass2003, Trust Key and HYP2003. The token is non-transferable and is destroyed on expiry or compromise.
Yes. The Income Tax e-filing portal at incometax.gov.in accepts Class 3 DSC for ITR verification under Section 140 of the Income-tax Act 1961. DSC is one of the four e-verification modes alongside Aadhaar OTP, net-banking EVC and bank-account EVC. For companies, partnerships and political parties DSC verification of ITR is mandatory under Rule 12 of the Income-tax Rules.
Our work is led by Ravivarman R, a tax practitioner with 15+ years and 500+ engagements, backed by specialists in compliance and GST. We base every Class 3 DSC recommendation on current law and your actual facts — not generic templates — and we are happy to explain the reasoning.
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.
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.
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.
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.
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.
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.
In-person verification is the fallback verification method under the IVG where the applicant physically appears before a CA-authorised registration officer with original PAN and Aadhaar/passport. IPV is mandatory for organisation DSCs in certain configurations and where Aadhaar e-KYC and video KYC both fail. Section 36 of the IT Act mandates that the CA verify the identity of the applicant before issuance.
Class 3 DSC near George Town:

Across George Town we look after firms on Muthuswamy Road, North Fort Road, RBI Subway, Rajaji Salai and Royapuram Harbour Bridge as well as the Broadway Road, Esplanade, Evening Bazaar Road and Netaji Subhash Chandra Bose Road corridors — local Class 3 DSC without the cross-city travel.

Free Consultation Available

Ready for Expert Class 3 DSC in George Town?

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