Class 3 DSC: Signing and Encryption
A signing and encryption requirement must be matched to the certificate type accepted by your portal and issuing Certifying Authority (CA). Do not assume that one combined certificate is accepted for every applicant or workflow. CCA guidance says an individual’s signature and encryption certificates should be separate. Confirm the exact product configuration before ordering.
Price and availability
Verify your mobile number by OTP on the relevant Alpingo product page to view current prices. This Alpingo OTP is for account and price access; it is separate from the identity and mobile verification conducted by the issuing CA under its CCA-compliant process. The complete price, GST, token and shipping charges will be shown before you place an order. Confirm the total at checkout.
CA application and identity verification
The selected CA is responsible for checking the application and issuing the DSC. The CA determines the documents, KYC route, video or other verification steps required for the applicant and certificate. Follow the CA’s instructions and submit information through its designated application process. Alpingo can assist with available options but is not the issuing CA.
Under the current CCA Identity Verification Guidelines (CCA-IVG), the CA must complete the applicant’s mobile authentication before accepting advance payment for DSC issuance, except for specified organisational-person application routes. Alpingo’s OTP for viewing prices does not satisfy or replace that CA authentication.
Alpingo can assist with available options from PantaSign, Capricorn, VSign, iDSign and SignX, subject to current availability and the selected issuer’s requirements. Refund and cancellation rules can differ by issuing CA; review the selected issuer’s current terms before applying.
USB token compatibility and security
- Confirm the exact token model and serial-number series with the selected CA before applying. CA acceptance can depend on the certificate and current crypto-device requirements.
- Install token software and drivers only from the token manufacturer’s or CA’s official support source.
- The subscriber should keep the token and PIN under their control. Never share a PIN, private key, OTP, or download passcode.
- If a token or private key is lost or may be compromised, contact the issuing CA promptly about revocation and next steps. Reissue or recovery is subject to the CA’s rules.
How to order
- Check that the portal requires signing, encryption, or both, and confirm the certificate configuration with the CA.
- Select the relevant product and validity period, then verify your mobile number by OTP to view the price.
- Review the selected issuer’s terms and the complete charges at checkout.
- Complete the CA’s identity verification and follow its instructions to download and use the certificate.
Read the current CCA guidelines, including IVG 2.6, the CCA subscriber and token FAQs, and the CCA crypto-device security requirements. For order help, contact Alpingo.
USB crypto token: confirm current CA acceptance
CCA-CRYPTO v2.4 (14 August 2026) says crypto devices relying on a historical FIPS 140-2 certificate status are to discontinue DSC issuance based on fresh eKYC using those modules after 21 September 2026, except where specifically permitted. A token name or model label alone does not prove that its exact hardware, firmware, software, serial-number series, or application route is currently accepted.
Before ordering, confirm current acceptance and empanelment for the exact token configuration with the issuing CA, then check the receiving portal’s requirements. CCA-CRYPTO v2.4 · Current CCA guidelines · DSC document checklist and application procedure.