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
Chennai South · Velachery Division · Palavakkam Class 3 DSC

Palavakkam Class 3 DSC for residential Businesses

Class 3 DSC for residential units around ECR Road, Palavakkam — with a documented, audit-ready process

Palavakkam residential and restaurants units around Palavakkam Beach with WhatsApp document intake and same-day filed-acknowledgement delivery. Call 9566-068-468.

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

How is Class 3 DSC different from Aadhaar eSign in Palavakkam, Chennai?

Class 3 DSC is a long-term PKI certificate (1/2/3 year validity) stored on a FIPS 140-2 USB token used for repeated signing across MCA, GST, TRACES and tenders. Aadhaar eSign is a one-time signature with a 30-minute certificate, no hardware token and is suitable for one-off documents like loan agreements or e-NACH mandates. eSign requires the signer to be a resident with an Aadhaar-linked mobile; DSC has no such restriction.

Transparent Pricing

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

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

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. Palavakkam 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. Palavakkam clients with Aadhaar-linked mobile complete the entire process on WhatsApp and receive the DSC within an hour.

Video KYC Fallback

For Palavakkam 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

Palavakkam 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 Palavakkam 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.

Key Benefits

What Palavakkam Clients Get

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

18% GST Input Credit on DSC Fee
DSC services are classified under SAC 998313 attracting 18% GST. GST-registered Palavakkam 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 — Palavakkam clients can file SPICe+, DIR-3 KYC or sign tender bids the same business day.
Section 5 IT Act Legal Equivalence
Documents signed with a Class 3 DSC enjoy Section 5 IT Act 2000 equal legal status with handwritten signatures, admissible in evidence under Section 65B of the Indian Evidence Act 1872 with the mandatory certificate per Anvar P.V. and Arjun Panditrao.
Mandatory MCA Compliance Covered
Every MCA21 e-form requiring DSC — incorporation, director KYC, financial statements, annual return, registered office change — signed by Palavakkam clients without portal-side rejection.
GST Rule 26 Signatory Compliance
Rule 26(1) CGST Rules mandates DSC for company and LLP filings on the GST portal — Class 3 organisation DSC of the authorised signatory delivered to Palavakkam corporate clients ensures uninterrupted GSTR-1, GSTR-3B and GSTR-9 filing.
TRACES TDS Filing Without Hiccups
Form 24Q, 26Q, 27Q and 27EQ quarterly filings on TRACES require Class 3 DSC for corporate deductors. Palavakkam companies file on or before the 31st of the month following the quarter without Section 234E late fee.
Comparison

Class 3 Signature DSC vs Class 3 Combo DSC

Why this matters here — Across Palavakkam, the business activity radiating outward from Palavakkam Beach and nearby commercial pockets. Practitioners note that with quick access via Palavakkam Bus Stop and feeder routes connecting Palavakkam to the rest of Chennai.

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

Documents for Class 3 DSC

Share documents via WhatsApp to 9566-068-468. No office visit required for Palavakkam 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 — Across Palavakkam, the cluster of residential, restaurants, hospitality businesses that defines Palavakkam'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
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
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 Aadhaar OTP paperless e-KYC routeOn due dateApplication form with Aadhaar OTP authentication and PAN verificationSame-day issuance possible if Aadhaar biometric lock is open and OTP delivers; failure of OTP route forces switch to video-verification with 1-2 day SLA, potentially missing same-day signing requirements
Class 3 DSC application submitted under video-verification e-KYC route2 daysApplication form with recorded verification video, PAN and Aadhaar / passport images1-2 working day standard SLA before certificate is issued; applicants needing same-day signing must plan ahead or default to Aadhaar OTP route; NRI and biometric-locked applicants have no faster option

Deadline pressure points we see in Palavakkam: Closer to Palavakkam, for the professional and salaried population of Palavakkam navigating personal-tax and home-office GST.

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 Palavakkam, Chennai 600041

Because PIN 600041 sits inside the Chennai South jurisdiction, the handling office for Palavakkam stays consistent across years, which matters when filings or approvals span cycles. Approvals, acknowledgements and queries for Palavakkam businesses tie back to the Velachery Division, so our Class 3 DSC cadence accounts for how that office works. Palavakkam (PIN 600041) falls under the Velachery Division of the Chennai South, the jurisdiction that handles statutory matters for businesses at this PIN. The 600xx geo-zone covering Palavakkam groups several locality clusters under common administration, keeping documentation expectations predictable.

Commercial activity in Palavakkam runs medium, so Class 3 DSC volumes scale through peak months and we staff the Palavakkam desk accordingly. The businesses clustered around ECR Road in Palavakkam drive the bulk of the Class 3 DSC workload we see each cycle. Vendors and customers tied to the Palavakkam Bus Stop network show up across the invoice trail we reconcile for Palavakkam Class 3 DSC clients. The coastal residential mid tier mix of Palavakkam shapes what lands in our workpapers — a blend of hospitality activity and the commercial pulse around ECR Road.

The business mix in Palavakkam centres on restaurants, and that sector carries its own Class 3 DSC quirks we plan for in advance. The restaurants firms we serve in Palavakkam value a Class 3 DSC partner who already understands their sector's compliance rhythm. Class 3 DSC for restaurants businesses in Palavakkam hinges on getting the sector's recurring entries right the first time. Mixed restaurants activity across Palavakkam means our Class 3 DSC team keeps sector playbooks ready rather than improvising per client.

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

We treat Palavakkam and Neelankarai as one catchment for Class 3 DSC, which keeps documentation and turnaround consistent. Coverage from Palavakkam naturally extends to Neelankarai, so group entities across the area share one Class 3 DSC workflow. Serving Palavakkam and Neelankarai from one team keeps Class 3 DSC turnaround identical across the cluster. A client relocating between Palavakkam and Neelankarai keeps the same Class 3 DSC file and the same team.

Recurring gaps in Palavakkam hospitality records are the first thing our Class 3 DSC review closes out. The Class 3 DSC mistakes we see most in Palavakkam are avoidable with disciplined intake, which our checklist enforces. Because we work repeatedly across Palavakkam, we can benchmark a new client's Class 3 DSC position against the locality norm. Each engagement in Palavakkam adds to a record of what the Chennai South jurisdiction expects, sharpening the next Class 3 DSC file.

Shifting principal place of business to Palavakkam means updating jurisdiction to the Chennai South, and we manage the paperwork end-to-end. A startup setting up near Palavakkam Beach in Palavakkam gets a Class 3 DSC foundation built for the Velachery Division from day one. New restaurants ventures in Palavakkam lean on us to stand up Class 3 DSC correctly before the first deadline rather than after a notice. We onboard new Palavakkam entities onto a Class 3 DSC cadence that is audit-ready from the very first cycle.

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

Class 3 DSC in Palavakkam — Complete Guide

Class 3 individual DSC for Palavakkam directors, partners and proprietors is used for MCA SPICe+, DIR-3 KYC, ITR signing under Section 140 of the Income-tax Act and personal e-Tendering. Class 3 organisation DSC is issued in the entity's name with the authorised signatory's name in the Subject DN — used for GST authorised signatory under Rule 26 CGST Rules, TRACES TDS filing, IceGate Customs and CPPP/GeM tendering.

Class 3 DSC in Palavakkam, Chennai

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

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

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

Does a Class 3 DSC need to be registered on the portal before use?

Yes. Simply holding the token is not enough — each portal requires a one-time registration mapping the DSC to your PAN or DIN and role. On MCA21 V3 the director registers the DSC against the DIN; on GST the authorised signatory registers it against the GSTIN before any DSC-signed filing is accepted.

Is video verification compulsory for a Class 3 DSC?

Under the CCA Identity Verification Guidelines, a short applicant-recorded video stating name and consent is mandatory for paperless Aadhaar e-KYC issuance. It is the step most often failed when the audio is unclear or the applicant reads a different script than instructed by the Certifying Authority.

What Palavakkam clients want to know before signing: Closer to Palavakkam, around the Palavakkam Beach catchment of Palavakkam.

Expert Guide

A complete walkthrough — Class 3 Dsc

Reading this guide locally — Across Palavakkam, on the Neelankarai-Kottivakkam corridor that passes through Palavakkam.

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.

Categories and types of Class 3 DSC

Encryption-only certificate

A Class 3 Encryption certificate carries a key-usage extension limited to keyEncipherment and dataEncipherment, and is designed for the use-case where the subscriber needs to receive confidential documents encrypted with their public key. The private key is used to decrypt incoming messages, and the public key is published in the CA's directory for senders to use as the encryption target. Encryption-only certificates are less common in standalone form because most subscribers also need signing capability, but they are required as a distinct credential in certain e-tendering workflows where the procuring entity encrypts the technical-bid documents to the bidder's public key for confidentiality during the pre-opening window. The corresponding cryptographic algorithm under the India PKI profile is RSA with PKCS#1 v1.5 or OAEP padding.

Combo (Signing plus Encryption) certificate

A Class 3 Combo certificate combines both signing and encryption capabilities in a single token, often through two physically-separate certificate-and-key-pairs stored on the same hardware token. Combo certificates are required for use-cases that involve both signing and confidentiality — notably e-tendering on CPPP, GeM, IREPS and several state e-procurement portals where the bidder signs the bid document with the signing certificate and the procuring entity encrypts feedback to the bidder using the encryption certificate. The ONDC seller-node TLS-mutual-authentication architecture similarly requires a Combo certificate. Combo certificates carry a higher unit cost than signing-only or encryption-only, but the practical convenience of a single token covering both use-cases drives most corporate procurement towards Combo.

Document Signer Certificate for bulk signing

A Document Signer Certificate is a specialised variant of the Class 3 Organisation DSC, introduced by the CCA in 2017 to enable unattended bulk signing in enterprise workflows (digital invoice signing under the GST e-invoice framework, bulk certificate issuance by educational institutions, contract-signing automation in financial services). The Document Signer Certificate is issued in the name of the legal entity (not an individual signatory) and is stored on a Hardware Security Module (HSM) compliant with FIPS 140-2 Level 3 or equivalent, rather than on a USB cryptographic token. The HSM-based storage allows the certificate to be invoked programmatically without manual PIN entry, supporting high-volume signing throughput. The CCA's 2017 office order specifying this variant requires additional CA-level controls including HSM audit logging and segregation of duties between the certificate-administration team and the signing-operation team.

Cryptographic standards and certificate format

X.509 v3 certificate structure

The Class 3 DSC issued under the India PKI framework follows the X.509 v3 certificate format specified in ITU-T Recommendation X.509 (08/2005) and IETF RFC 5280. The X.509 v3 certificate is a structured data object containing the certificate's version, serial number, signature algorithm identifier, issuer (the issuing CA's Distinguished Name), validity period (notBefore and notAfter dates), subject (the certificate holder's Distinguished Name), subject public-key information (the algorithm and the public key itself), and a set of v3 extensions including key usage, extended key usage, certificate policies, CRL distribution points and authority information access. The certificate is itself signed by the issuing CA's private key, with the signature appended to the certificate body, allowing any verifier with access to the CA's public key to confirm the certificate's authenticity.

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.

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.

What Palavakkam clients usually ask next: Closer to Palavakkam, for the professional and salaried population of Palavakkam navigating personal-tax and home-office GST.

Glossary

Plain-English glossary for this service

GST Common Portal

Indirect tax return registration and refund interface accepting digital signatures from companies and limited liability partnerships.

Income Tax e-Filing Portal

Direct tax submission platform mandating digital signatures for audit cases companies and political parties.

ICEGATE

Customs electronic data interchange portal accepting digital signatures from importers exporters and customs brokers.

Trademark e-Filing System

Intellectual property registry online portal requiring agent digital signatures on TM-A applications.

EPFO Unified Portal

Employee provident fund interface accepting employer digital signatures on monthly electronic challan returns.

Class 2 Discontinuation

CCA mandate effective January 2021 ending issuance of intermediate assurance certificates consolidating PKI under Class 3.

Certificate Class

Assurance tier reflecting depth of identity verification with Class 3 representing highest physical or biometric proofing.

Signing Certificate

Component of dual-purpose pair authorising electronic record signing distinct from encryption usage variant.

Encryption Certificate

Companion certificate enabling document confidentiality through public key encryption complementing signing functionality.

DGFT Portal

Foreign trade directorate platform requiring exporter digital signatures on import export code amendments and applications.

ROC Filing

Registrar of Companies submission process mandating directors and professionals affix Class 3 signatures on prescribed forms.

DSC Mapping

Portal registration linking subscriber public certificate to user account permitting signature based authentication.

By Industry

Industry-specific patterns in Palavakkam

How the local trade mix shapes this — Across Palavakkam, the business activity radiating outward from Palavakkam Beach and nearby commercial pockets.

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.
E-commerce Sellers
Common issue: E-commerce sellers operating through Amazon, Flipkart and Meesho marketplaces and registered on the GST portal as principal-place-of-business in one state with additional places of business in multiple states often face Class 3 DSC authentication failures when filing GSTR-1 and GSTR-3B for additional-place GSTINs. The GSTN authentication module verifies the certificate's Subject Distinguished Name against the registered authorised signatory of the GSTIN being filed, and a single-state DSC purchased without verifying the multi-state authorised-signatory record creates a mismatch at the moment of submission.
How we handle it: Map each GSTIN to a designated authorised signatory under REG-14 well before any filing window; procure Class 3 DSCs for each designated authorised signatory with the exact name format as on the GSTIN authorised-signatory record (initials, surnames, middle names must match character-for-character); reconcile the DSC-to-GSTIN mapping in a master sheet before each filing cycle; for high-volume sellers consider a Class 3 Document Signer Certificate to enable straight-through ASP-GSP integration via the NIC's e-invoice and GST API framework.
E-commerce Sellers
Common issue: E-commerce sellers participating in the Open Network for Digital Commerce (ONDC) launched in 2022 are required to authenticate their seller-node registrations and order-acknowledgement transactions using Class 3 DSC under the ONDC Network Policy. Sellers frequently provision a generic Signing-only DSC without realising that the ONDC protocol layer requires a Combo certificate (Signing plus Encryption) because the encrypted message-bus uses TLS-mutual-authentication with the seller's client certificate, in addition to digital-signature on individual order-events.
How we handle it: Procure a Class 3 Combo (Signing plus Encryption) DSC with key-usage extensions covering digitalSignature, nonRepudiation, keyEncipherment and dataEncipherment as specified in the ONDC Network Policy v1.0; provision the certificate in the seller-node's reverse-proxy configuration for TLS-mutual-authentication; capture the certificate fingerprint in the ONDC Registry record at the time of seller-node onboarding; rotate the certificate within thirty days of any team-member exit who had access to the seller-node infrastructure.
Construction Contractors
Common issue: Civil-works contractors bidding on PSU, central-government and state-government tenders through the Central Public Procurement Portal (CPPP), GeM and the various state e-procurement platforms (Tamil Nadu Tenders, Karnataka eProc, MahaTenders) routinely face Class 3 DSC compatibility issues at the bid-submission stage because each portal's signature-applet has its own quirks around the supported token brands, browser versions and key-usage extension requirements. A bid submitted minutes before the deadline can fail authentication and forfeit the EMD if the DSC environment is not pre-tested.
How we handle it: Pre-test the Class 3 DSC environment on each target portal at least seventy-two hours before any bid-submission deadline using the portal's mock-bid or test-signing workflow; preserve screenshots and timestamps of the successful test; in the production bid submission, sign at least sixty minutes before the deadline to allow recovery from any transient OCSP-responder lag; maintain a backup Class 3 DSC of a co-authorised signatory on a separate machine in case the primary signatory's DSC fails on the day of submission.
Case Studies

Anonymised engagements we have handled

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

Password recoveryTrading

DSC password forgotten — token reset within validity window saved ₹14,500 re-issuance

Issue: A trading-firm authorised signatory forgot the token password after a 6-month break following a medical procedure. The Class 3 DSC inside the token had 19 months of validity remaining. The first instinct was to apply for a fresh DSC at ₹1,500 plus token at ₹450, abandoning the 19 months of paid validity. The token-vendor's brute-force lockout had not yet triggered because the user had not attempted the password.
Approach: Initiated the issuing CA's password-reset workflow within the certificate validity — eMudhra supports password reset against the original e-KYC credentials using Aadhaar OTP re-authentication, with no fresh certificate cost. Verified the token was an ePass 2003 with the standard manufacturer's reset utility available. Reset the user PIN through the manufacturer utility after the issuing CA's identity re-verification. Avoided the lockout window by stopping all login attempts during the reset process.
Outcome: Token password reset within 6 working hours of request; existing 19-month DSC validity preserved; saved ₹14,500 across 7 group-company signatories who were going to be re-issued in panic; firm policy now mandates password-vault entry for every fresh DSC issuance with a dual-custody backup.
Individual vs organisationalServices

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

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

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

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

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

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

Why these Palavakkam engagements look the way they do: Closer to Palavakkam, the business activity radiating outward from Palavakkam Beach and nearby commercial pockets, which is why for the professional and salaried population of Palavakkam navigating personal-tax and home-office GST.

Client Reviews

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

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

Class 3 DSC is a long-term PKI certificate (1/2/3 year validity) stored on a FIPS 140-2 USB token used for repeated signing across MCA, GST, TRACES and tenders. Aadhaar eSign is a one-time signature with a 30-minute certificate, no hardware token and is suitable for one-off documents like loan agreements or e-NACH mandates. eSign requires the signer to be a resident with an Aadhaar-linked mobile; DSC has no such restriction.
Step 1 — applicant fills the CA's online application with PAN, name, email and mobile. Step 2 — UIDAI Aadhaar OTP is triggered to the Aadhaar-linked mobile and entered. Step 3 — UIDAI returns the e-KYC payload (name, photo, address) digitally signed. Step 4 — applicant records a 30-second video selfie reading a system-generated PIN. Step 5 — CA matches Aadhaar photo with video frame, generates the key pair and issues the DSC for download to the USB token.
The exact list depends on your case, but we send a short, plain-English checklist the moment you engage us — no jargon. Palavakkam clients can share documents as phone photos or scans over WhatsApp on 9566-068-468, and we flag immediately if anything is missing.
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.
Yes — we work comfortably in both Tamil and English, which makes explaining Class 3 DSC to Palavakkam clients straightforward. Ask your questions in whichever language you prefer, by call or WhatsApp on 9566-068-468.
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.
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.
We keep payment simple for Palavakkam 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.
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.
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.
It is simple: you share your requirement and documents over WhatsApp or email, we prepare and review the work, send it to you for approval, then complete the filing. Palavakkam clients get the same quality remotely as in person, with an update at every step.
Stamp duty is payable on the instrument irrespective of whether it is physically or digitally signed. Section 3 of the Indian Stamp Act 1899 charges duty based on the nature of the instrument. Several States (Maharashtra, Delhi, Karnataka) accept e-stamping. The DSC itself attracts no stamp duty — it is a certificate, not an instrument.
Yes. Fraudulent use of someone else's DSC attracts Section 66C (identity theft) of the IT Act 2000 punishable with up to 3 years imprisonment and fine up to ₹1 lakh. Publishing a false DSC for fraud is punishable under Section 73 and creating a DSC by fraudulent means under Section 74. Section 72 punishes breach of confidentiality by a CA officer with up to 2 years imprisonment.
The CCA is appointed under Section 17 of the IT Act 2000 and licenses Certifying Authorities under Section 21. The CCA exercises supervision under Sections 18-20, lays down standards (Section 19), and operates the Root Certifying Authority of India (RCAI). Licensed Certifying Authorities (CAs) currently include eMudhra, NSDL e-Governance (Protean), Sify Safescrypt, Capricorn, IDsign, VSign, NIC and IndusInd-RA. The CCA portal is cca.gov.in.
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.
Class 3 DSC near Palavakkam:

Across Palavakkam we look after firms on Pandian Salai, Estate 1st Cross street, Estate 1st Main Road, Estate Main road and 11th Cross Street as well as the 14th Street, 16th Street, 17th Street and 18th Street corridors — local Class 3 DSC without the cross-city travel.

Free Consultation Available

Ready for Expert Class 3 DSC in Palavakkam?

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