Quick answer
Electronic signatures are legally recognized in India, but the legal effect of a signature depends on the signing method, the type of document, the evidence available, and whether the transaction is excluded under Indian law. The IT Act, 2000 supports electronic records, electronic signatures, and electronic contract formation, subject to First Schedule exclusions, Contract Act essentials, stamp and local formalities, and BSA 2023 evidence rules. eSignIQ is not a Certifying Authority and does not issue DSC or Aadhaar eSign.
- IT Act ss. 3–5 and 10A support digital/electronic signatures and electronic contracts (subject to reliability and exclusions).
- First Schedule (s. 1(4)) still excludes certain negotiable instruments, most powers of attorney, trusts, and wills; the former immovable-property entry was omitted in 2022.
- BSA 2023 (from 1 July 2024) is the current evidence framework for electronic records, older IEA 65B language is historical.
- Stamp duty and registration rules are separate from “electronic execution is allowed.”
Key takeaways
- India’s IT Act, 2000 gives legal recognition to electronic records (s. 4) and electronic signatures (s. 5), defines digital signatures (s. 3) and broader electronic signatures / reliable authentication techniques (s. 3A), and supports electronic contract formation (s. 10A), subject to First Schedule exclusions and other law.
- Section 1(4) plus the First Schedule still keep certain categories outside the IT Act’s electronic framework (notably many negotiable instruments, most powers of attorney, trusts, and wills). Serial 5 (contracts for sale/conveyance of immovable property) was omitted by MeitY notification S.O. 4720(E) (2022); property deals can still face stamp, registration, and local formalities.
- eSignIQ is not a Certifying Authority under the Controller of Certifying Authorities (CCA) regime and does not issue Digital Signature Certificates (DSC) or Aadhaar eSign.
- From 1 July 2024, electronic-record evidence themes that operators often associated with Indian Evidence Act s. 65B are addressed under the Bharatiya Sakshya Adhiniyam, 2023 (notably ss. 61–63 and related presumptions). Treat older “65B only” checklists as historical.
- Electronic execution does not remove stamp duty. State stamp laws and e-stamping processes may still apply, there is no universal rate table on this page.
- Typed or drawn signatures on a guided platform can be electronic signatures in the broad IT Act sense when reliability and process themes are met; DSC / Second Schedule techniques are a different assurance path for use cases that require them.
Primary laws at a glance
Information Technology Act, 2000
Legal recognition of electronic records and electronic signatures; digital signatures; reliable electronic signature / authentication techniques; electronic contracts; Certifying Authorities; First and Second Schedules.
Why it matters: Primary statute most teams mean when asking whether e-signatures are “legal in India.”
Official source: Information Technology Act, 2000Indian Contract Act, 1872
Offer, acceptance, consideration, capacity, free consent, and other contract essentials.
Why it matters: Electronic form does not replace ordinary contract-law requirements. An electronic signature on an invalid bargain does not cure defects in formation.
Official source: Indian Contract Act, 1872Bharatiya Sakshya Adhiniyam, 2023
Admissibility and related rules for electronic or digital records (including certificate requirements under s. 63) and presumptions concerning electronic agreements, signatures, and certificates (ss. 85–87 themes).
Why it matters: Current courtroom framing for electronic evidence after 1 July 2024; replaces the older IEA 65B-centric checklist many guides still reprint.
Official source: Bharatiya Sakshya Adhiniyam, 2023
Are electronic signatures legal in India?
For many everyday commercial and operational documents, yes: Indian law recognizes electronic records and electronic signatures and does not deny a contract validity solely because it was formed through electronic means. The starting point is the Information Technology Act, 2000 (“IT Act”), read with the Indian Contract Act, 1872 for formation essentials, and, when a dispute reaches evidence rules, the Bharatiya Sakshya Adhiniyam, 2023 (“BSA”).
“Legal” in practice means more than a green checkmark on a product page. Teams still need to confirm (1) the document is not outside the IT Act via section 1(4) and the First Schedule, (2) any method-specific or sector-specific requirement (for example, a Digital Signature Certificate where an institution demands one), (3) stamp and registration duties where applicable, and (4) that the process can show who signed what, when, and with what intent.
eSignIQ helps organizations prepare, send, and complete documents with typed, drawn, or uploaded signature marks inside a guided workflow. That is an electronic-signature process in the broad sense. It is not the same as obtaining a DSC from a licensed Certifying Authority, and it is not Aadhaar eSign.
Educational only
Use this guide to structure diligence with counsel, not as a substitute for advice on your document set.
Which laws govern electronic signatures in India?
Several statutes interact. The IT Act is the technology and e-commerce recognition statute. Contract law still decides whether a bargain exists. Evidence law decides how electronic material is presented and presumed in proceedings. Stamp and registration regimes remain largely state-driven and sit beside electronic execution.
| Law | Role for e-signature operators | Where to read |
|---|---|---|
| IT Act, 2000 | Recognition of electronic records/signatures; DSC / CA regime; First Schedule exclusions; s. 10A electronic contracts | India Code, IT Act |
| Indian Contract Act, 1872 | Offer, acceptance, consideration, capacity, consent, still apply to electronic deals | India Code, Contract Act |
| Bharatiya Sakshya Adhiniyam, 2023 | Electronic/digital record admissibility themes (ss. 61–63) and related presumptions (ss. 85–87) | India Code, BSA |
| State stamp / registration laws | Duty, e-stamping, and registration formalities, separate from IT Act recognition | State statutes / SHCIL or state e-stamp portals |
MeitY publishes policy material for the IT ecosystem; the Controller of Certifying Authorities (CCA) oversees licensed Certifying Authorities that issue DSCs. Always prefer primary text on India Code over secondary blog summaries when stakes are high.
Electronic signature vs digital signature (DSC) in India
Indian law uses precise terms. Section 3 of the IT Act addresses authentication of electronic records by a digital signature, asymmetric cryptography tied to a subscriber’s private key and Digital Signature Certificate ecosystem. Section 3A recognizes electronic signatures and electronic authentication techniques that are reliable and that may be specified in the Second Schedule. Sections 4 and 5 give legal recognition to electronic records and electronic signatures. Section 10A addresses contracts formed through electronic means.
In product language, “electronic signature” often means typed name, drawn mark, uploaded image, or click-to-agree inside a platform. “Digital signature” in India usually points to DSC / PKI methods under the CCA–CA framework. Both sit under the broader electronic-signature conversation, but they are not interchangeable when a counterparty, regulator, or filing system requires a DSC.
| Method | How it works | Typical evidence | Legal treatment (careful) | Common use | Main limitation |
|---|---|---|---|---|---|
| Typed-name signature | Signer types a name into a signature field on an electronic record | Name field, timestamps, IP/device if logged, consent events | May be an electronic signature under broad IT Act concepts when reliability and association themes are met; not the same as a DSC presumption package | Routine commercial / HR packets (subject to counsel) | Weaker attribution if authentication is thin |
| Drawn signature | Signer draws a mark on screen or pad | Image of mark + process log | Same broad electronic-signature conversation as typed marks, process quality drives evidential usefulness | Users who want a handwritten-looking mark | Visual similarity to wet ink does not equal DSC treatment |
| Uploaded signature image | Signer uploads a scan or image of a signature | Image file + association to the record + audit events | Can evidence intent if the process ties the image to the specific document and signer identity cues | Repeat signers with a stored mark | Images can be copied; authenticity depends on surrounding controls |
| Click-to-accept | Checkbox / button affirming agreement to displayed terms | Click event, terms version, timestamp, identity cues | Can support assent for many online contracts; still needs Contract Act essentials and eligibility | Online terms, simple acceptances | Disputes often turn on what was displayed and who clicked |
| Platform-based electronic signature (eSignIQ-style) | Guided fields, ordered signing, status, retention of final PDF + event history | Completion certificate-style exports, audit history (plan-gated), final PDF | Operational electronic-signature workflow; not a licensed CA product | Multi-party vendor, sales, and HR packs | Does not replace DSC or Aadhaar eSign where those are mandated |
| Aadhaar-based eSign (where applicable) | Aadhaar-linked electronic authentication / signature services through authorized channels | Provider-issued eSign artefacts under applicable rules | Prescribed / regulated path for use cases that require it, distinct from casual type/draw | Workflows that specifically require Aadhaar eSign | eSignIQ does not provide Aadhaar eSign |
| Digital Signature Certificate (DSC) | Asymmetric crypto; certificate from a licensed Certifying Authority under CCA oversight | Cryptographic signature + certificate chain | IT Act s. 3 digital signature path; often required by portals and filings | Institutional / government / bank portals that mandate DSC | eSignIQ is not a CA and does not issue DSC |
If a bank portal, government filing, or enterprise policy says “DSC only,” a typed platform signature will not substitute for that requirement, even though both may be “electronic” in everyday speech.
When is an electronically signed agreement enforceable?
Enforceability is a contract-law and remedies question, not only an IT Act recognition question. Parties still need competent parties, lawful object, free consent, and the other essentials that apply to paper contracts. Section 10A helps remove the objection that a contract is invalid solely because electronic means were used; it does not invent consideration or fix a void bargain.
Process quality matters commercially even before a courtroom. Counterparties care whether the signer had authority, whether the final PDF matches what was offered, whether required fields were completed, and whether you can show a coherent timeline. For multi-party packs, ordered signing and status tracking reduce “who signed which version?” disputes.
Sector rules can add requirements (employment, financial services, healthcare, government procurement). Treat this guide as a map of national e-signature themes, then layer industry counsel where needed.
Evidence and admissibility under the BSA, 2023
Older Indian practice materials often centered on section 65B of the Indian Evidence Act, 1872 for electronic records. That framing is historical for current proceedings. The Bharatiya Sakshya Adhiniyam, 2023, enforced from 1 July 2024, is the statute operators should map to when discussing electronic or digital records in evidence.
BSA sections 61–63 address electronic and digital records, including certificate requirements under section 63. In substance, operators should expect attention to integrity of the electronic record (commonly discussed via hash / identification of the record), who is competent to certify under the statute, and dual-signatory / prescribed certification formalities as set out in the Act, counsel should apply the exact statutory text to the facts. Sections 85–87 themes cover presumptions as to electronic agreements, electronic signatures and electronic signature certificates, and related electronic records, again, read the primary sections rather than relying on marketing paraphrases.
Platform audit history and completed PDFs help reconstruct events; they do not automatically equal a completed s. 63 certificate package. If litigation is reasonably foreseeable, involve counsel early on what to retain and who can certify.
- Signer name and email
- Verified phone number where used
- Signing timestamp
- IP or device information where lawfully collected
- Consent to sign electronically
- Authentication events
- Document version identifier
- Completion certificate or equivalent export
- Tamper-evident or integrity metadata where available
- Complete activity log
- Final signed document
- Secure retention history
- Privacy: collect only authentication and device information that is necessary, proportionate and handled according to applicable privacy requirements.
- Document who operated the system and who can speak to how records were generated, relevant to certification roles under BSA s. 63.
- Separate marketing “audit trail” claims from courtroom certificate formalities; treat dual-signatory / statutory certificate steps as counsel-driven.
This section is intentionally cautious. Evidence outcomes turn on pleadings, objections, and how records were produced, not on a product screenshot.
Which documents may be suitable for electronic signing?
Many routine business documents are candidates for electronic execution when they are not First Schedule exclusions and no separate statute or policy demands wet ink, notarization, DSC-only filing, or other special form. Suitability is always “may be,” never “always is.”
| Document type (examples) | Why teams consider e-sign | Extra caution |
|---|---|---|
| NDAs, mutual confidentiality | Speed; clear acceptance of defined terms | Authority of signer; governing law clauses |
| Vendor / supplier agreements, SOWs | Remote countersign; version control | Stamp duty; commercial negotiation history |
| Sales contracts, order forms, quotes accepting online | Faster close; fewer print–scan loops | Consumer / sector rules if B2C |
| HR offer letters, acknowledgements, policy receipts | Distributed workforce onboarding | Labor compliance; local language needs |
| Internal approvals and operational checklists | Auditability of who approved what | Not a substitute for board/statutory formality where required |
If a document sits near an exclusion (for example, instruments that look like negotiable instruments, or instruments that function as powers of attorney), pause and get a legal read before migrating to any electronic method.
Documents and transactions outside the IT Act (First Schedule)
Section 1(4) of the IT Act states that nothing in the Act applies to documents or transactions specified in the First Schedule (the Central Government may amend the Schedule by Official Gazette notification). For those categories, you should not assume IT Act electronic-record / electronic-signature recognition applies.
As reflected on India Code (including amendments via MeitY notification S.O. 4720(E), dated 26 September 2022), the First Schedule currently focuses on four live exclusion categories. Serial number 5, contracts for the sale or conveyance of immovable property or any interest in such property, was omitted in 2022. Omission from the First Schedule means the IT Act is no longer blocked by that former entry; it does not by itself erase stamp duty, registration under the Registration Act, 1908, or local conveyancing formalities.
| Sl. | Category (accurate paraphrase) | Practical note |
|---|---|---|
| 1 | A negotiable instrument as defined in s. 13 of the Negotiable Instruments Act, 1881, other than a cheque, or a demand promissory note or bill of exchange issued in favour of or endorsed by an entity regulated by the RBI, NHB, SEBI, IRDAI, or PFRDA | Many private-party negotiable instruments remain excluded; regulated-entity carve-outs narrowed the exclusion in 2022. |
| 2 | A power-of-attorney under the Powers-of-Attorney Act, 1882, except those that empower an entity regulated by the RBI, NHB, SEBI, IRDAI, or PFRDA to act for, on behalf of, and in the name of the person executing them | Most private PoAs remain outside; limited regulated-entity PoAs were carved out of the exclusion in 2022. |
| 3 | A trust as defined in s. 3 of the Indian Trusts Act, 1882 | Trust instruments remain excluded from IT Act applicability via the Schedule. |
| 4 | A will under the Indian Succession Act, 1925 (s. 2(h)), including any other testamentary disposition by whatever name called | Wills and testamentary dispositions remain excluded. |
| 5 | Omitted (2022), former entry covered contracts for sale/conveyance of immovable property or any interest therein | IT Act exclusion removed; stamp, registration, and local property formalities may still apply independently. |
Always verify the live First Schedule text on India Code before relying on secondary summaries. Gazette amendments can change carve-outs. Seek advice from an Indian lawyer or relevant registration authority before attempting to execute an excluded or exclusion-adjacent document electronically.
Warning
Do not electronically execute First Schedule–excluded instruments on the assumption that IT Act recognition will cure form. Wills, trusts, and many powers of attorney and negotiable instruments remain high-risk for casual e-sign migration.
Stamp duty and electronic execution
Electronic execution does not remove stamp duty. If an instrument is chargeable under the applicable state stamp law, parties still need to address stamping, including e-stamping where the state provides it, according to that state’s rules and timelines.
Rates, franking, adjudication, and penalties for under-stamping vary by state and instrument type. This guide intentionally does not publish a rate table. Build a stamp checklist with finance and counsel for the states where you execute volume agreements.
eSignIQ does not calculate stamp duty and does not file stamp instruments for you. Treat stamping as a parallel compliance track to the signing workflow.
Are typed or drawn signatures valid in India?
A typed name, drawn signature, or uploaded image can function as an electronic signature when it is a reliable electronic authentication technique associated with an electronic record in line with IT Act concepts (including s. 3A reliability themes) and when the document is otherwise eligible. Validity is about the whole process, identity cues, intent, association with the specific record, retention, not about whether the pixels look like calligraphy.
That said, “valid electronic signature” in the IT Act sense is not a promise of enforceability for every dispute, and it is not a substitute for DSC where DSC is mandated. For higher-risk packets, teams often raise assurance with stronger signer authentication, clearer disclosures, and richer audit retention rather than arguing about font choice.
Aadhaar eSign vs DSC vs platform e-signature
Three labels get mixed in Indian buying conversations:
- DSC, cryptographic digital signature backed by a certificate from a licensed Certifying Authority under the CCA framework.
- Aadhaar eSign, Aadhaar-linked electronic signature services offered through authorized channels for use cases that require that method.
- Platform electronic signature, guided type/draw/upload or click-to-agree workflows on products such as eSignIQ.
Choose the method the counterparty, regulator, or filing system requires. eSignIQ addresses the third category. It is not a CA, does not issue DSC, and does not provide Aadhaar eSign. If your workflow truly requires DSC or Aadhaar eSign, obtain those through authorized providers and keep eSignIQ for packets that fit platform e-signature.
What should you record when collecting electronic signatures?
Operators who later need to explain a signing event usually wish they had kept more than a final PDF. A practical retention checklist:
- Final completed document (PDF) and the exact version presented to each signer.
- Signer identity fields collected (name, email, role/title if captured).
- Timestamps for invite, open, sign, decline, and completion.
- Signing order and whether sequential constraints were enforced.
- IP address / user agent or similar technical metadata if your platform logs them.
- Any authentication step used (for example, email OTP or sender-side 2FA context).
- Disclosure / consent language shown before signing, if used.
- Hash or integrity metadata for the completed file where available.
- Access controls: who in your org could edit fields after send.
- Retention schedule aligned with contract term, limitation periods, and privacy duties.
On eSignIQ, Business-plan audit history and standard status tracking help assemble much of this operational picture. Map exports to your counsel’s BSA evidence plan when disputes are foreseeable.
Cross-border signing with an Indian counterparty
Cross-border packs add choice-of-law, jurisdiction, and data-transfer questions on top of IT Act recognition. An Indian company may sign on eSignIQ with an overseas counterparty, but “we used an electronic signature” does not decide which country’s courts hear a dispute or which privacy rules govern personal data in the packet.
Spell out governing law and dispute resolution in the contract. Confirm whether any party’s local rules demand wet ink, notarization, apostille, or a specific signature assurance level. For personal data leaving India or entering India, follow applicable privacy and contractual transfer expectations, this guide does not provide a transfer mechanism checklist.
If the deal is governed by Indian law but performance or assets sit elsewhere, still clear First Schedule and stamp issues for the Indian instrument, then address foreign formalities separately.
How eSignIQ helps (verified product capabilities)
eSignIQ is built for prepare–send–complete electronic signature workflows. For India-facing teams, use it where platform electronic signatures fit your risk and counsel guidance, and pair it with DSC / Aadhaar eSign / stamp processes when those are separately required.
- Upload PDF or Word documents and place signature and form fields for each recipient.
- AI-assisted field placement on Business plans to speed preparation.
- Scoped signer links so recipients complete without unnecessary account friction.
- Live request status so senders see who still needs to sign.
- Automated reminders on Pro+ plans to reduce stalled packets.
- Ordered (sequential) signing on Pro+ plans for multi-party packs.
- Audit-friendly event history on Business plans for operational reconstruction.
- Reusable templates for repeat document types.
- TLS in transit, optional sender 2FA, and the controls described on the Security page.
eSignIQ does not act as a licensed Certifying Authority, does not issue Digital Signature Certificates, does not provide Aadhaar eSign, does not calculate or remit stamp duty, and does not guarantee legal validity or courtroom outcomes. Those boundaries are intentional: keep legal and regulated PKI steps with the right licensed channels.
See plans and security
Compare plan gates on Pricing, then review technical controls on Security.
View pricingPractical risk levels for electronic signing
This is a practical operator framework, not a classification defined by Indian law. Use it to decide how much identity verification, legal review, and evidence retention to apply, then confirm with counsel for your templates.
Lower risk (illustrative)
- Examples: routine internal acknowledgements, basic operational approvals, non-sensitive checklists.
- Often sufficient: clear document display, typed or drawn mark, email-linked invite, standard retention.
- Still confirm the packet is not First Schedule–adjacent and that stamp rules do not unexpectedly apply.
Medium risk (illustrative)
- Examples: employment agreements, vendor contracts, NDAs, commercial service agreements.
- Raise assurance: stronger signer identification, authority checks, ordered signing for multi-party packs, Business-grade audit retention where available, stamp owner assigned by state.
- Legal review of templates before wide rollout.
Higher risk (illustrative)
- Examples: high-value contracts, regulated transactions, documents requiring registration, disputed-authority situations, cross-border packs, instruments near First Schedule exclusions, DSC-mandated filings.
- Expect counsel involvement, possible DSC or Aadhaar eSign via authorized channels, careful stamp/registration planning, and an evidence plan mapped to BSA s. 63 themes.
- Do not force these into a casual click-to-sign template without a legal read.
Separate compliance tracks
- Signing workflow (platform electronic signature).
- PKI / DSC or Aadhaar eSign when mandated.
- Stamp and registration.
- Evidence retention / BSA readiness.
How this guide is kept current
Legal content needs a deliberate update process. Editorial legal research for this page was completed on the researched date shown above. We aim to re-review at least every six months, or earlier when a statute, schedule, notification, or court interpretation material to this topic changes.
This is an editorial policy, not a claim that monitoring is automatic. Before relying on any summary, confirm the live text on India Code and related official sources. Update dates on this page change only after a substantive review, not on every website deployment.
- Check IT Act status, First Schedule, and Second Schedule techniques
- Check BSA and related evidence practice notes
- Check stamp / registration themes without inventing rates
- Check CCA / DSC and Aadhaar eSign positioning vs product capabilities
- Refresh official links and FAQ accuracy
Final summary
Electronic signatures are generally recognized in India under the IT Act, 2000, with electronic contracts supported by section 10A, while the Indian Contract Act, 1872 still governs formation essentials. First Schedule exclusions continue for key categories (with 2022 amendments narrowing some negotiable-instrument and power-of-attorney carve-outs and omitting the former immovable-property exclusion). Evidence practice for electronic records now sits primarily under the Bharatiya Sakshya Adhiniyam, 2023, including section 63 certificate themes, not older IEA 65B-only checklists. Stamp duty remains a separate obligation.
Use eSignIQ for eligible guided electronic signature workflows: upload, fields, templates, scoped links, status, reminders and ordered signing on eligible plans, and Business audit history, with TLS/2FA/security controls as documented. Do not treat eSignIQ as a CA, DSC issuer, Aadhaar eSign provider, stamp calculator, or legal guarantor. When in doubt, read India Code and ask Indian counsel before you migrate a template library.
Frequently asked questions
Sources and official references
Primary and official references used for editorial research. Verify live text before relying on any summary.
- India Code, Information Technology Act, 2000, accessed 2026-07-26
Primary statute; confirm live First Schedule text and sections 3, 3A, 4, 5, 10A, 1(4).
- India Code, Bharatiya Sakshya Adhiniyam, 2023, accessed 2026-07-26
Current evidence framework (ss. 61–63, 85–87 themes); enforced from 1 July 2024.
- India Code, Indian Contract Act, 1872, accessed 2026-07-26
- Ministry of Electronics and Information Technology (MeitY), accessed 2026-07-26
Policy context for the IT Act ecosystem; prefer primary Act text for operative rules.
- Controller of Certifying Authorities (CCA), accessed 2026-07-26
Licensed CA / DSC oversight. Site availability can be intermittent; verify via alternate official channels if needed.
Disclaimer
This guide provides general information and is not legal advice. Laws, rules and court interpretations may change. Consult a qualified Indian lawyer for advice about a particular agreement, signing method or transaction. eSignIQ is not a law firm, not a Certifying Authority, and does not guarantee that any document, signature method, or workflow will be valid, admissible, stamp-compliant, or enforceable.
Prepare, send and track routine business agreements
eSignIQ can help you run a more consistent electronic signing workflow. Assess the right method and formalities for each transaction with qualified counsel.