E-Signature Software India 2026: IT Act Validity, Prices

E-signatures are legally recognised in India under the Information Technology Act, 2000, but not every e-signature is equal and not every document can be e-signed. Section 3A lets a subscriber authenticate an electronic record with an electronic signature or authentication technique that is "considered reliable" and specified in the Second Schedule. That is the legal home of Aadhaar-based eSign, offered through Certifying Authorities licensed by the Controller of Certifying Authorities (CCA). The Act's First Schedule excludes documents such as wills, powers of attorney, trusts, negotiable instruments other than cheques, and contracts for the sale of immovable property. For everyday commercial contracts, platforms such as Leegality, Zoho Sign, DocuSign and Adobe Acrobat Sign are widely used. The right choice depends on whether you need Aadhaar eSign, e-stamping, or simple click-to-sign at scale.

This article is general information, not legal advice. Take advice from a qualified lawyer for high-value or disputed documents.

Executive summary

• The law distinguishes reliable, Schedule-listed signatures. Section 3A(2) sets reliability tests: the signature data must be linked to the signatory and to no other person, and any alteration must be detectable. Aadhaar eSign and DSC-based signatures are the strongest evidence in India.
• Some documents are excluded by the Act. The First Schedule lists negotiable instruments (other than cheques), powers of attorney, trusts, wills and contracts for sale or conveyance of immovable property.
• Indian platforms price per signature. Leegality's Basic plan lists Aadhaar eSign at ₹25 per signatory, non-Aadhaar eSign at ₹15, and digital stamping at ₹45 per stamp paper plus stamp duty and ₹500 per stamp order.
• Global platforms price per user. Adobe Acrobat Standard for teams is listed at ₹1,582 per licence per month (annual, billed monthly, excluding GST). Zoho Sign's free plan includes 5 envelopes per month. DocuSign's pricing page did not load for us.
• Stamp duty still applies. An e-signature does not replace stamp duty. Use e-stamping where the state and document require it.

Market context

The legal framework. The Information Technology Act, 2000 (as amended) provides:

• Section 3A(1): "a subscriber may authenticate any electronic record by such electronic signature or electronic authentication technique which (a) is considered reliable; and (b) may be specified in the Second Schedule."
• Section 3A(2) treats a signature as reliable if, among other conditions, the signature creation data or authentication data are linked to the signatory "and to no other person", and alterations after signing are detectable.
• Section 1(4) and the First Schedule: the Act does not apply to (1) negotiable instruments other than cheques, (2) powers of attorney, (3) trusts, (4) wills and other testamentary dispositions, and (5) contracts for the sale or conveyance of immovable property or any interest in it.
• Section 10A recognises the validity of contracts formed through electronic means.

The eSign service. The Controller of Certifying Authorities explains that "eSign services are facilitated by trusted third party service providers - currently Certifying Authorities (CA) licensed under the IT Act". It uses e-KYC authentication with biometric or OTP options. CCA publishes e-authentication guidelines, eSign Service Provider (ESP) empanelment rules and Application Service Provider (ASP) on-boarding guidelines on the same page. Most Indian e-signature software acts as an ASP connected to one or more ESPs.

Other rules to keep in mind:

• CERT-In Directions (28 April 2022): body corporates must report listed cyber incidents within 6 hours and keep ICT logs for 180 days in India (PDF). A compromised signing account or a leaked contract repository can be a reportable incident.
• DPDP Act, 2023 and DPDP Rules, 2025: signing workflows collect names, phone numbers, email addresses and sometimes Aadhaar-linked details. The Rules have an 18-month phased compliance timeline (PIB).

We have not found an official statistic on e-signature adoption in India, so we make no quantitative market claims.

Types of electronic signatures used in India

Evaluation framework

App Advisor's methodology for e-signature software for Indian companies:

Vendor comparison

Official prices as shown on vendor pages in September 2026. "Not published" means we could not read a price on the page we accessed.

Other India-focused options on App Advisor include SignDesk, eMudhra emSigner and eSign by NSDL. Browse the e-signature software category and the document management category.

How to read the pricing models:

• Per-signatory pricing (Leegality Basic) suits low or seasonal volume: you pay only when documents are executed. The page says you pay only for successful executions.
• Per-user pricing (Adobe, Zoho Sign paid plans) suits teams that send many documents each month. An envelope cap per user (such as Zoho Sign Standard's 25) can push heavy senders to a higher tier.
• Adobe's licence also includes PDF editing, which may replace a separate PDF tool.

Total cost of ownership

Illustrative model — assumptions stated. An NBFC-style lending partner or HR team executing agreements. Assumptions:

• 400 agreements per month, each with 2 signatories (customer + company), i.e. 800 signatures per month.
• Scenario 1 uses Aadhaar eSign for all signatories on Leegality Basic list prices. (A real business of this size would probably negotiate a higher plan; this only shows the maths.)
• Scenario 2 uses 5 Adobe Acrobat Standard for teams licences at list price, with simple electronic signatures.
• Stamp duty varies by state and document and is excluded from both.
• Integration and setup: an assumed ₹50,000 one-time in both cases (our assumption).

Interpretation:

1. The cheaper scenario is not automatically better. For loan and credit documents, the evidentiary strength of Aadhaar eSign may justify the cost.
2. A hybrid often wins: Aadhaar eSign for customer-facing, high-risk documents and simple signatures for internal approvals.
3. At this volume, a custom plan from an Indian platform will likely beat Basic list prices. Ask for a quote.
4. Also check Leegality's non-Aadhaar eSign at ₹15/signatory for documents that do not need Aadhaar-based evidence.

Implementation roadmap

Weeks 1–2: Legal mapping

• List every document type you sign. Mark First Schedule exclusions (wills, POAs, trusts, non-cheque negotiable instruments, immovable property sale contracts). These stay on paper or follow specific registration processes.
• Decide the signature type per document: Aadhaar eSign, DSC or simple e-signature.
• Confirm stamp duty and e-stamping needs with counsel, state by state.

Weeks 3–4: Platform setup

• Create templates with signing order, fields and reminders.
• Enforce MFA for senders and admins; restrict template editing.
• Integrate with CRM, HRMS or loan management systems through the API.

Weeks 5–6: Pilot

• Run 50–100 real documents. Verify audit trails and certificate details, and download final PDFs.
• Train staff on consent language and on handling signer queries.

Weeks 7–8: Scale and govern

• Roll out to all teams. Set retention rules for signed documents.
• Add signed-document repositories to your backup and incident response plans.

Risks and compliance checklist

• First Schedule check: no excluded document type is being e-signed.
• Signature type matched to risk: Aadhaar eSign or DSC for high-value or regulated documents.
• Stamp duty: e-stamping or physical stamping applied as required.
• Audit trail: IP address, timestamps, OTP/e-KYC evidence and certificate data kept with each signed file.
• CERT-In 6-hour reporting: incident process covers compromised signing accounts and contract repositories.
• 180-day logs within India: platform access logs retained or exported.
• DPDP Act: notice and purpose limitation for signer data; access limited; retention and deletion defined.
• Data localisation: where regulators (for example, for regulated lenders) or contracts require it, confirm where documents are stored.
• Vendor due diligence: confirm the platform's ESP/CA relationship for Aadhaar eSign.

KPIs to track

How to choose

• Choose an Indian specialist such as Leegality when you need Aadhaar eSign, e-stamping and high-volume API workflows, especially in lending, insurance, HR and real estate services (excluding sale deeds).
• Choose Zoho Sign if you already run Zoho apps and want per-user plans with a free entry tier.
• Choose Adobe Acrobat Sign if teams also need PDF editing, and global counterparties expect Adobe workflows.
• Choose DocuSign for multinational contracts and CLM needs. Get INR quotes, since the pricing page did not load for us.
• For HR-specific onboarding flows, compare tools in the HRMS software category. For contract repositories, see document management software.

Questions to ask an e-signature vendor

1. Which licensed Certifying Authorities or eSign Service Providers do you connect to for Aadhaar eSign, and what happens if one is unavailable?
2. Do you support DSC tokens as well as Aadhaar eSign in the same workflow?
3. Which states does your e-stamping service cover, and how is stamp duty paid and evidenced?
4. What exactly does the audit certificate contain, and can we download it with every document?
5. Where are signed documents and audit logs stored, and can logs be exported for 180-day retention in India?
6. What are the per-signature, per-stamp and platform fees at our expected volume, in INR and excluding GST?
7. How do you handle signer data under the DPDP Act, including retention and deletion?

Use cases by department

The same platform can serve several teams, but each has different legal and evidence needs.

Building a defensible audit trail

Whatever the signature type, the evidence around the signature decides how well it holds up in a dispute. Make sure every signed document can be matched to:

1. Identity evidence: the e-KYC response reference for Aadhaar eSign, the certificate details for a DSC, or verified email and mobile OTP events for simple signatures.
2. Intent: a clear consent statement shown to the signer before signing.
3. Integrity: a tamper-evident final PDF; any change after signing should be detectable, in line with the reliability conditions in Section 3A(2).
4. Timeline: timestamps for sending, viewing, signing and completion, taken from synchronised clocks.
5. Retention: storage of the signed PDF and the audit certificate together, for as long as the limitation period and your retention policy require.

Common mistakes

• E-signing a power of attorney or a property sale agreement, which the Act does not cover.
• Treating an e-signature as a substitute for stamp duty.
• Letting several employees use one shared sender account, which weakens attribution.
• Sending signing links over unverified WhatsApp numbers without OTP verification.
• Not downloading completed documents into the company's own repository, and relying entirely on the vendor's account.

FAQs

Sources

• Information Technology Act, 2000 (updated) — India Code
• Controller of Certifying Authorities — eSign
• Leegality pricing
• Zoho Sign pricing
• Adobe Acrobat for teams pricing (India)
• DocuSign eSignature plans
• CERT-In Directions under Section 70B(6), 28 April 2022
• PIB: Digital Personal Data Protection Rules, 2025