Sign PDF documents using Aadhaar OTP authentication through an eSign provider. Explore an online signing workflow or API integration for your business, without requiring the signer to own a USB DSC token.
Review → Consent → Authenticate → Signed PDF
The document. The signer.
The signed record.
Business agreement
The signer reviews the document
Use the Aadhaar-linked
mobile number
Short-lived signing certificate issued for the transaction.
Aadhaar eSign is an online electronic signature service introduced by the Government of India. It lets any Aadhaar holder sign a digital document by entering their 12-digit Aadhaar number and a one-time password sent to their registered mobile.
Behind the scenes, the request is processed by an eSign Service Provider licensed by the CCA (Controller of Certifying Authorities). The ESP fetches eKYC from UIDAI, generates a short-lived digital signature certificate, and seals it into your PDF as a cryptographic PKCS#7 signature.
The result is a document that is certificate-signed and tamper-evident — without printers, couriers, or USB tokens. SignSecure provides both a no-code signing experience (SignPad) and a developer API (SignLift) on top of this same licensed gateway.
Aadhaar eSign uses UIDAI’s biometric and demographic database to verify the signer in real time. Identity is proven before the signature is applied — not after.
The eSign request travels through a CCA-licensed eSign Service Provider (ESP). SignSecure integrates with licensed gateways to facilitate the signing workflow.
eSign is recognized within the Indian electronic-signature framework. Check document-specific requirements and acceptance with the receiving organization.
The Aadhaar OTP workflow combines document review, consent, authentication, and a certificate-based signature through an eSign service provider.
Prepare the PDF in SignPad or your integrated application. Add recipients and signature fields, then confirm the signing method for the document.
PDF preparation02The signer reviews the document and gives consent in the eSign provider flow. Aadhaar authentication establishes identity for signing.
Consent and authenticationThe signer receives an OTP on the Aadhaar-linked mobile number and enters it in the provider flow. Completion depends on OTP delivery and successful authentication.
Aadhaar-linked mobileThe provider issues a short-lived signing certificate for the transaction. Retain the signed PDF and available transaction evidence, and check the signature with a compatible PDF reader.
Certificate-based signatureAllow time for document review, OTP delivery, and any retry needed by the signer.
Retain the signed document and available consent and transaction records for your workflow.
Aadhaar authentication connects the signing transaction to the authenticated signer.
Start with the people sending documents and the system that needs the signed PDF.
For operations, HR, and business teams
Prepare and route documents through a web signing workflow. Choose Aadhaar eSign when it meets the document and recipient requirements.
For developers and technology teams
Connect signing to your application, HRMS, or ERP. Review the current integration documentation and provider flow with SignSecure before implementation.
Start with the document and its recipient. Then choose the authentication and signing setup your signers can use.
| Requirement | Electronic signature | Aadhaar eSign | USB-token DSC |
|---|---|---|---|
| Signing method | Draw, type, or upload a signature | Online authentication and a short-lived certificate | An existing certificate held on a USB token |
| Signer prerequisites | Access to the signing invitation | Aadhaar-linked mobile for the OTP workflow | Valid DSC, USB token, driver, and compatible software |
| Hardware | A supported phone or computer | A supported phone or computer; no signing token | Compatible computer and USB token |
| Identity evidence | Depends on the workflow and authentication used | Aadhaar authentication through the eSign provider | Identity verified when the certificate is issued |
| Workflow fit | Remote document review and signature capture | Remote recipients who can complete Aadhaar OTP authentication | Certificate holders signing PDFs or using a compatible portal |
| Before choosing | Check authentication and evidence requirements | Check document eligibility and recipient acceptance | Check required certificate type and portal compatibility |
These are workflow differences, not a universal ranking of legal validity. Check document-specific requirements, recipient acceptance, and any separate stamping or registration steps.
Evaluate the complete document journey, from signer access to retaining the signed record.
Route offer letters, employment agreements, and policy acknowledgements to remote hires. Check signer access to Aadhaar OTP and store completion records with the employee file.
Collect signatures on supplier agreements and declarations. Confirm who is authorised to sign for each business and keep the final agreement linked to the vendor record.
Send service agreements and engagement letters to customers. Define the signing order and confirm document eligibility, recipient acceptance, and any stamping requirements.
Evaluate signing within a specific lending or onboarding journey. Have your compliance team confirm the product, document, KYC, and recordkeeping requirements before rollout.
Legal framework and evidence
The Controller of Certifying Authorities describes eSign as a legally recognized electronic signature service under the Information Technology Act framework. The process includes signer consent, authentication and certificate-based signing.
Check whether your document and receiving organization accept the chosen method. Electronic signing does not by itself complete any separate stamping, registration or document-specific formalities.
Read the CCA eSign overviewThe signer reviews the document and completes the authentication required by the eSign provider.
The provider issues a short-lived signing certificate. A USB DSC token is not required for this flow.
Retain the signed PDF and available transaction evidence. Check the signature and certificate using a PDF reader that supports validation.
Put it into practice
Choose the signing journey with your users, technical team and document requirements in mind.
For the Aadhaar OTP flow, the signer needs access to the mobile number registered with Aadhaar. Plan a suitable alternative for signers who cannot complete this authentication.
Use SignPad to prepare documents and invite recipients. For an application integration, discuss the authentication journey, completion status and signed-document retrieval with our API team.
Share expected volumes and signer counts to obtain a quote. Confirm billing units, failed-transaction treatment, data retention and the evidence required by your receiving organization.
Legal status, pricing, security, and integration — everything teams ask before switching to Aadhaar eSign.
Aadhaar eSign is an online electronic signature service that uses Aadhaar authentication and a short-lived signing certificate. In the OTP workflow, the signer reviews the document, gives consent, and authenticates using their Aadhaar-linked mobile number. A USB signing token is not required.
The Controller of Certifying Authorities describes eSign as legally recognised within the Information Technology Act framework. Acceptance still depends on the document, recipient, and applicable requirements. Electronic signing does not replace separate stamp duty, registration, or other formalities. Check those requirements before selecting a signing method.
The signer needs an Aadhaar number, access to the mobile number linked to it, an internet connection, and a supported browser. The provider flow may support a Virtual ID. Confirm prerequisites before sending documents, especially when recipients cannot receive the OTP.
Request a quote with your expected monthly volume, number of signers per document, and whether you need a web workflow or API integration. Confirm the billing unit, minimum commitment, credit validity, taxes, and treatment of failed or expired requests before buying.
Ask for the current data flow and retention policy covering SignSecure and the eSign service provider. Review which identifiers and audit records each party processes, access controls, retention periods, deletion, and support access before production use.
Aadhaar eSign obtains a short-lived certificate through online authentication for the signing transaction. USB-token DSC signing uses a previously issued certificate and needs the token, its driver, and compatible signing software. Choose based on recipient acceptance, signer access, and your workflow; a portal requiring a particular DSC may not accept Aadhaar eSign.
Discuss an Aadhaar eSign API integration with SignSecure. Map document preparation, signer consent and authentication, completion handling, retries, and signed-document storage. Request the current API documentation and evaluation access to verify endpoints, authentication, callbacks, and limits for your integration.
Evaluate it for a specific product and document workflow with your compliance team. Signing is one step in onboarding or lending; it does not by itself satisfy every KYC, consent, recordkeeping, or regulatory requirement. Confirm the applicable rules and receiving institution’s acceptance.
Use a PDF reader that supports digital signature validation. Inspect the signer certificate, certificate chain, signature status, and whether the document changed after signing. Validation can depend on trust settings and certificate-status information. Retain the original signed PDF and available consent and transaction evidence.
The Aadhaar OTP workflow cannot complete without access to the linked mobile number. Resolve the mobile linkage through UIDAI’s supported process or choose another signing method that meets your document and recipient requirements. SignPad also supports electronic signatures and DSC signing through SignBridge.
Choose a web workflow with SignPad or discuss an Aadhaar eSign API integration. Start with your document requirements, signer access and expected volume.
Signer consent · Aadhaar-linked mobile · Signed PDF records
