Use EximSign to detect your DSC token, choose the correct certificate, sign an ICEGATE-ready XML file, and download the signed XML. Built for CHA teams, freight forwarders, consol agents, shipping lines, importers, and exporters.
EximSign is an independent third-party utility. It is not an official ICEGATE product.
DSC XML signing adds a digital signature from an authorized certificate to an XML file. The signature connects the file with the certificate holder and helps the receiving system verify that the signed XML was not changed after signing.
Sign XML files after document and filing checks are complete.
Move CGM or other manifest output into the DSC step without changing the source data.
Use a clear signing flow when an authorized XML submission needs a DSC.
Select the final XML file prepared by your filing system.
Connect the token and confirm that its certificate is visible.
Select the authorized and valid certificate for the transaction.
Enter the DSC token PIN in the signing utility.
Save the signed output and do not edit it before submission.
See the available certificate and choose the one meant for the filing user.
Keep your current filing system and use EximSign for the DSC XML signing step.
Run the signer from the Windows system where the DSC token and middleware are installed.
Reconnect the token, confirm its middleware is installed, and check whether Windows can see the certificate.
Check the holder name, validity dates, and the certificate authorized for the filing account.
Use the token PIN, check the keyboard state, and avoid repeated guesses that may lock the token.
| Area | ICEGATE-provided route | EximSign Signer Utility |
|---|---|---|
| Purpose | Part of the official portal or prescribed filing process. | A third-party signing utility used beside an existing filing process. |
| Workflow | Follows the current ICEGATE instructions for that service. | Upload XML, select the visible certificate, sign, and save the output. |
| Best fit | Use when the official route already meets the filing requirement. | Use when the team needs a focused Windows DSC XML signing step. |
| Support scope | Official portal access, rules, and service guidance. | EximSign utility setup and signing workflow guidance. |
Always follow the current ICEGATE requirement for the transaction you are submitting.
It is the process of adding a digital signature from an authorized certificate to an XML file so the receiving system can verify the signer and detect changes made after signing.
Install the Windows utility, connect the DSC token, select the final XML, choose the correct certificate, enter the token PIN, sign, and save the signed XML.
No. EximSign is an independent third-party signing utility. Users must still follow current ICEGATE rules and submission instructions.
It is intended for CHA teams, customs operations staff, freight forwarders, consol agents, shipping lines, importers, and exporters that need to sign filing XML with an authorized DSC.
Use it for XML files prepared by your filing workflow that require DSC signing. Confirm the required format and transaction rules before signing.
Compatibility depends on whether the token middleware is correctly installed and the certificate is visible to Windows. Test the current token and driver on the signing system.
Use the DSC class and certificate currently required for your ICEGATE account and transaction. Confirm the latest requirement with ICEGATE or your authorized account administrator.
EximSign is provided as a Windows desktop utility. Requirements shown by an ICEGATE browser signer or another utility are separate from the EximSign installation.
Common causes are an incomplete USB connection, missing or outdated token middleware, an unavailable certificate, or a signer that was opened before the token became ready.
Check whether the certificate is valid, visible in Windows, available through the token middleware, and installed for the current Windows user.
Check that you are entering the token PIN, verify the keyboard state, and avoid repeated guesses. Contact the token provider if the token becomes locked.
That depends on the token middleware, organizational authorization, and security policy. Install the required driver on each approved system and never share the token PIN.
Yes. The signing process adds signature data to the XML. Editing the signed file afterward can invalidate the signature, so submit the saved signed output unchanged.
Check token detection, certificate validity, PIN entry, XML readiness, and the selected output location one at a time. This separates DSC issues from file issues.
Download the current installer from this page, close any running older version, and complete the Windows installation before testing the DSC token again.
Keep the final XML, DSC token details, and the exact error message ready when you contact support.