Your MCA DSC Doesn't Work on DGFT? Here's Why
Class 3 DSCs are portal-agnostic in theory, but DGFT registration failures are common. The two configuration checks that fix it.
You just picked up your Class 3 DSC last month, registered it on MCA, filed a few forms, and now you're trying to use it on the DGFT portal — and it fails. Two things are usually going on.
Check 1: Extended Key Usage attributes
The DGFT portal checks specific Extended Key Usage (EKU) attributes on the certificate. Some Certifying Authorities issue DSCs without the DGFT-required EKU set, especially when the issuing purpose was stated as "MCA" at application time. This can't always be fixed after issuance — sometimes reissuance is cleaner.
Check 2: Registration against your IEC
Even if the DSC is technically DGFT-compatible, it must be registered against your Import-Export Code before you can sign filings. First-time DGFT users often skip this and go straight to filing. Fix: register the DSC under "Register DSC" on the DGFT portal, using the exact same signatory PAN as the DSC holder.
The clean path forward
If your MCA DSC is under a year old and has the correct EKU set, register it against your IEC and you're done. If EKU is wrong, reissue with DGFT specified as one of the purposes at application. We do this in one working day for existing clients — see our DGFT DSC page.