Get Class 3 DSC application assistance, licensed Certifying Authority coordination, USB token guidance, and separate DGFT and ICEGATE registration support for your authorised signatory.
Select your requirement.
Understand the certificate type, issuing authority, USB token, and portal-registration steps needed for secure digital signing on DGFT, ICEGATE, e-tendering, and supported business portals.
A Class 3 Digital Signature Certificate is a higher-assurance credential used to authenticate an individual or authorised signatory and digitally sign electronic submissions. Under India's PKI framework, end-user DSCs are issued by Certifying Authorities licensed by the Controller of Certifying Authorities, not by consultants generally.
Class 3 private keys are generated and stored in an approved hardware cryptographic device, commonly called a DSC USB token, which remains under the subscriber's custody. The certificate, private key, and token are related but are not the same thing.
The correct Individual or Organisation route depends on the entity, authorised signatory, certificate fields, and target portal. DGFT and ICEGATE also require separate registration or update workflows even when one valid DSC is suitable for both.
DGFT DSC registration links a valid certificate to the relevant user and entity profile. Certificate information, PAN or entity details, and the authorised signatory must meet the current DGFT validation rules before licence, amendment, redemption, or other foreign-trade filings are signed.
ICEGATE provides separate services to register, update, and use a DSC. The certificate must belong to the relevant user, remain valid, and be registered for the applicable Customs workflow; DGFT registration does not complete this step.
Multi-portal setup: one valid certificate may be suitable for more than one portal, but acceptance, entity validation, registration, and signer-utility requirements must be completed separately for each system.
A DSC affects filing continuity, signatory validity, and whether trade and tax workflows can actually move on time.
Supports certificate-based digital signing where the target government, customs, tender, or business portal accepts the DSC type.
Improves continuity in export and customs workflows where portal access and digital authentication are mandatory.
Reduces rejection risk caused by the wrong signatory profile, incomplete mapping, or weak document preparation.
Keeps separate DGFT, ICEGATE, e-tendering, and corporate portal registrations aligned with the authorised signatory.
Exporters, importers, Customs users, tender participants, companies, LLPs, proprietors, and authorised signatories may need a Class 3 DSC where their target portal requires certificate-based signing. Not every business needs one, and the applicant route must match the portal and legal entity.
Exact records and verification methods vary by licensed CA. Aadhaar eKYC may verify identity, but Aadhaar eSign is a separate online signature service and is not another name for a token-based Class 3 DSC.
Individual route: PAN, contact details, photograph, and identity records required by the selected CA verification method.
Aadhaar eKYC may be available as an identity-verification route; it is not the same as Aadhaar eSign or the Class 3 certificate itself.
Organisation route: entity PAN and existence proof, applicant-to-organisation relationship, and authorised-signatory evidence where applicable.
Renewal or reissue: existing certificate and token details, expiry or loss information, and the portals on which the replacement must be registered.
We first confirm who should hold the DSC and whether the applicant is filing as an individual, proprietor, company signatory, LLP representative, or other authorised user.
PAN, Aadhaar, photo, business records, and signatory support are aligned before the request moves into verification.
The applicant completes the identity and organisation checks required by a CCA-licensed Certifying Authority, which is responsible for issuing the DSC.
The issued certificate and private key are configured in the approved crypto token under the subscriber's control, with current drivers or signer utility as required.
The DSC is registered or updated separately on DGFT, ICEGATE, or another supported portal, then tested in the intended signing workflow.
These are EXIMINQ package prices, not fixed Government of India fees. Confirm the included Certifying Authority certificate, crypto token, taxes, delivery, portal setup, and support before purchase.
Individual / Organisation
+ GST (2-year package configuration)
Signing + Encryption
+ GST (2-year package configuration)
A digital signature is only useful when the identity, token, and target portal all work together without blocking your filing.
A DSC only creates value when the right person holds it and the target portal accepts it. We review the signatory path first so DGFT, ICEGATE, and related workflows are built on the correct identity.
DGFT and ICEGATE registration are separate even when the same valid DSC is suitable for both. We coordinate the certificate, token, signer utility, and each portal's mapping steps.
A missing token, expired DSC, or changed authorised signatory can stop filings. We help coordinate CA renewal or reissue and the required portal update without treating private keys as transferable files.
We diagnose token detection, driver, signer utility, expiry, certificate selection, entity mismatch, and portal-registration issues before recommending a corrective step.
The certificate must come from a CCA-licensed Certifying Authority. Portal acceptance then depends on current DGFT, ICEGATE, or other system requirements, including identity alignment, registration, token access, and signer readiness.
The wrong signatory or weak organisational authorisation can prevent CA verification or portal registration.
Token expiry, loss, or renewal delay can stop urgent DGFT or customs filings.
A DSC that is issued correctly can still fail operationally if the target portal registration is incomplete.
Private keys, token PINs, OTPs, and Aadhaar authentication secrets must not be shared with a consultant or stored in ordinary service records.
A Class 3 Digital Signature Certificate is a higher-assurance digital identity credential used by an individual or authorised signatory to authenticate and digitally sign electronic submissions. A CCA-licensed Certifying Authority issues the certificate, and the subscriber's private key is stored in an approved hardware cryptographic device.
Certifying Authorities licensed by the Controller of Certifying Authorities issue DSCs to subscribers in India. EXIMINQ is not presented as a Certifying Authority; our role is application assistance, issuance coordination, token guidance, and portal registration support.
An Individual DSC identifies a person in an individual capacity, while an Organisation DSC also associates the subscriber with an organisation. The correct route depends on the entity, authorised-signatory relationship, certificate fields, and the validation rules of the target portal.
Use a valid DSC that meets the current DGFT transaction and entity-profile requirements. DGFT registration validates certificate and profile information, so PAN, entity details, signatory authority, certificate type, and the current signer utility must align.
Yes. DGFT and ICEGATE are separate systems with separate DSC registration or update workflows. A suitable certificate may work on both when each portal accepts its type and the identity details match, but registration on one portal does not configure the other.
A DSC USB token is an approved hardware cryptographic device used to protect the subscriber's private key. The token is not itself the certificate, must remain under the subscriber's custody, and should never be shared together with its PIN.
No. Aadhaar eKYC may be used as an identity-verification route during a DSC application, while Aadhaar eSign is a separate online electronic-signature service. A token-based Class 3 DSC uses a certificate and private key stored in an approved hardware cryptographic device.
Follow the issuing CA's current renewal or reissue process, then register or update the valid certificate on each required portal. A lost or damaged token can require revocation and reissue; the private key should not simply be copied to another device.
Common causes include an expired or unregistered certificate, entity or PAN mismatch, the wrong certificate selection, token-driver problems, a signer utility that is not running, or browser and portal-environment issues. Diagnose the current portal message before changing software or certificate settings.
Requirements vary by licensed CA, but commonly include applicant identity and contact details, organisation existence and PAN records, proof of the applicant's relationship with the entity, and authorised-signatory evidence such as an authorisation letter or applicable resolution.
It may be usable on multiple portals when the certificate type, identity fields, signing or encryption capability, and portal rules are compatible. Each portal can still require separate registration, drivers, signer utilities, or account mapping.
We assist with selecting the Individual or Organisation route, preparing records, coordinating with a licensed CA, configuring the crypto token, and registering or updating the DSC on supported portals such as DGFT and ICEGATE.
Useful when a valid DSC must also be matched with ICEGATE profile setup and Customs-filing readiness.
Relevant where customs or exporter workflows depend on both portal access and valid signatory-linked digital approval.
Important when document uploads, signing, and customs-facing digital execution need to work together.
Track current policy and portal-side changes that may affect DSC usage across trade-compliance workflows.
Class 3 DSC Services
A Class 3 Digital Signature Certificate authenticates an individual or authorised signatory for supported electronic filings. EXIMINQ assists with selecting the Individual or Organisation route, preparing identity and entity records, coordinating issuance through a CCA-licensed Certifying Authority, configuring the validated USB crypto token, and confirming the signing or encryption requirement.
Portal work continues after certificate issuance. We support separate DGFT DSC registration, ICEGATE registration or update, current driver and signer-utility checks, multi-portal mapping, renewal or reissue coordination, and lost-token troubleshooting. The certificate type, PAN or entity details, signatory authority, portal account, and current technical requirements must align before digital signing will work reliably.