DGFT DSC document checklist

DGFT DSC document checklist begins with one practical question: which portal or transaction will rely on the certificate? A Digital Signature Certificate is not simply a generic USB product. The correct choice depends on the applicant, the certificate function, the validity period and the rules of the destination system. Prepare the IEC, organisation and authorised signatory details commonly needed for a DGFT application.

Check the requirement before you buy

For an individual application, the certificate identity normally needs to align with the applicant’s accepted identity records. An organisation case adds the relationship between the applicant and the entity. Import-export, tender, tax and corporate-filing systems may each ask for different registrations or mappings. Check those requirements before payment so that a technically valid certificate is also suitable for the intended workflow.

Understand signing, encryption and tokens

Signing and encryption are different functions. Signing helps authenticate the signer and detect changes to a document. Encryption protects information so it can be read only by an intended recipient. Some workflows need signing only, while others may require both. A compatible cryptographic token may also be necessary. Never disclose the token PIN, OTP or private key to an agent or support person.

Use a controlled application process

A sensible application journey includes a requirement pre-check, a written quote, a case-specific document list, approved identity verification, CA review, issuance and setup guidance. Timelines should be described as estimates because mismatched records, poor document images, video verification issues or CA review can introduce delays. Start before a filing deadline and respond promptly to correction requests.

Keep copies of the final quote and application reference. After issuance, store the token securely, use a strong unique PIN, restrict access to the authorised signer and register the certificate only on trusted portals. If the token is lost or compromise is suspected, stop using it and contact the issuer for revocation guidance. For help in Chandigarh or remotely across India, share the portal name and applicant type with our team for a focused pre-check.