Aadhaar (UIDAI) 6
KYC & Onboarding 3
Digital Signatures 2
Data Privacy (DPDP) 2
MOSIP (National ID) 1
Products
Document eSigning platform
Send a document for signature from your own application, and get back a legally signed PDF with the evidence to prove who signed it.
The platform
Your system posts a document and a list of signers. QSigner does the rest, and tells you when it is done.
A template holds the document, where each signer signs, and the fields to fill in. Reuse it for every request.
Applicant, co-applicant, guarantor, witness. Sign in sequence or in any order, each with their own signature block.
Each signer gets their own link by SMS or email, with the expiry you set on the template.
Send values with the request and QSigner fills the PDF form — text, tick boxes and photographs — then flattens it before signing.
Send an AES-256 protected PDF and it stays AES-256 all the way to the signed copy. No downgrade, no stripped password.
Each organisation has its own templates, groups, API keys and document store, kept apart from every other.
How it works
Post the document and signers to one endpoint.
Each signer opens their link, consents and signs.
QSigner checks the signer is who the request said.
Download the signed PDF and its audit trail.
Identity & consent
A signature is only worth the evidence behind it. QSigner records who signed, what they agreed to, and from where.
Check the name, gender, year of birth and last four Aadhaar digits returned by e-KYC against the request. Set how close the name has to match.
Cap the number of signing attempts per signer. Past the limit the document cannot be signed.
Hold a consent for each signer and language. What the signer actually saw is stored with their acceptance.
Each acceptance keeps its own copy and hash of the consent text, so a later edit to the wording is visible rather than silent.
Link opened, OTP sent, consent accepted, signature embedded — with IP address, browser and session against each.
Documents and consent text are encrypted with AES-256-GCM on disk. Certificates and keys never leave your environment.
What is kept against each signature
Integrate
JSON over HTTPS, authenticated with an API key. Or use the QSigner web console and send nothing at all.
/Sign
Send the document, the signers and any field values. Returns a signing URL and a transaction id.
/Enquiry
Ask where a document stands: who has signed, who is pending, and the status of each.
/Download
Fetch the signed PDF with the certificate details of everyone who signed it.
Runs where you run