Skip to content

Signing methods

QSign supports three signing methods. They differ in how the signer’s identity is established and how strong the cryptographic evidence is. All three produce a tamper-evident, auditable result.

The signer’s intent and consent are captured — timestamp, IP address, and user-agent are recorded at the moment they agree to sign. On completion, a platform tamper seal is applied. Best for everyday business documents, internal approvals, and NDAs. Aligns with frameworks such as the US ESIGN Act / UETA.

Identity is asserted by the government Aadhaar OTP flow via the NSDL/Protean gateway; the returned PKCS#7 signature is validated and embedded. This is an IT-Act-aligned electronic signature in India that needs no hardware token.

A PKI / X.509 digital signature (RSA), optionally with an RFC-3161 trusted timestamp, giving cryptographic non-repudiation. DSC signing uses a hardware USB token and requires the desktop DSC agent. Best for high-assurance and statutory use.