Section 10A of the Information Technology Act, 2000 confirms that a contract cannot be denied enforceability only because the offer, acceptance or revocation happened electronically. In plain terms, Indian law recognises electronic contracts, provided the usual contract law requirements are met: lawful offer, acceptance, consideration, capacity and lawful object.
Section 10A does not make every document e-signable. You still need to check the IT Act exclusions, stamp duty, registration requirements, sector rules and evidence trail. For high-value or regulated agreements, confirm the signing method and execution process with counsel before rollout.
What Section 10A of the IT Act says
Section 10A was added to the Information Technology Act, 2000 to give legal recognition to contracts formed through electronic means.
The core rule is simple: where contract formation involves electronic records, a contract is not unenforceable only because electronic form or electronic means were used for the offer, acceptance or revocation.
You can read the Information Technology Act, 2000 on the official India Code page for the IT Act. The Act should be read with the Indian Contract Act, 1872, because Section 10A deals with the electronic form of contract formation, not every substantive contract requirement.
For a business user, Section 10A helps answer questions such as:
- Can a SaaS customer accept terms online? Yes, if the acceptance is properly captured.
- Can a vendor agreement be signed electronically? Usually yes, unless it falls under an exclusion or needs a special execution route.
- Can email acceptance create a contract? It can, if the facts show clear offer and acceptance.
- Can a clickwrap agreement be binding? It can, if the user had notice and gave affirmative acceptance.
Section 10A is not a shortcut around basic contract law. It only removes the objection that the contract used an electronic form.
What an electronic contract still needs to be valid
An electronic contract must still satisfy the same basic conditions as a paper contract.
1. Offer and acceptance
One party must make a clear offer, and the other must accept it. The acceptance should be unambiguous.
Examples:
- A customer clicks “I agree” to terms before account creation.
- A vendor signs a PDF purchase agreement through an e-signature workflow.
- A buyer replies by email accepting a quotation with specific commercial terms.
Weak examples include vague email replies such as “looks fine” where the final terms, authority and intention to contract are unclear.
2. Consideration
There must be consideration, unless an exception under contract law applies. In business contracts, this is usually straightforward: price for goods, fees for services, salary for employment or commission for sales.
3. Capacity and authority
The signer must have authority to bind the relevant party.
For companies and LLPs, check:
- Who is authorised under the board resolution, delegation matrix or power of attorney?
- Is the signer using their company email or a verified business identity?
- Does the agreement require two authorised signatories?
- Does the counterparty require a certified board resolution?
For internal controls, keep the authority proof with the signed contract. If you need to extract authority clauses across historic agreements, see our guide on AI clause extraction from contracts.
4. Lawful object and terms
The subject matter must be lawful. Section 10A will not save a contract that fails under contract law, public policy, sector regulation or another statute.
5. Reliable record of consent
For electronic contracts, evidence matters. Your process should capture who agreed, what they agreed to, when they agreed, and how the final version was protected from later alteration.
This is where audit trails, timestamping, signer authentication and final document hashing become operational controls, not just software features.
Section 10A vs electronic signature validity
Section 10A and electronic signature validity are related, but they are not the same rule.
| Topic | Main legal point | Practical meaning |
|---|---|---|
| Section 10A | Electronic contracts are not unenforceable only because they were formed electronically | Online offer and acceptance can create enforceable contracts |
| Section 5 of the IT Act | Electronic signatures get legal recognition where law requires a signature, subject to conditions | An e-signed document can satisfy signature requirements if the method is legally valid |
| Section 3 and 3A of the IT Act | Recognise digital signatures and electronic signatures | The signing method must fit the statutory framework |
| First Schedule exclusions | Certain documents are outside the IT Act’s electronic recognition framework | Some documents should not be executed only electronically |
For a broader explanation of signing methods, see Digital Signature vs Electronic Signature in India and Aadhaar eSign vs DSC in India: Which to Use.
Documents where Section 10A may not be enough
The IT Act does not apply equally to every document. The First Schedule of the Act excludes certain categories from electronic recognition.
Common exclusions include:
- Negotiable instruments, other than cheques.
- Powers of attorney.
- Trust deeds.
- Wills and other testamentary dispositions.
- Contracts for sale or conveyance of immovable property, or any interest in such property.
This means Section 10A should not be read as permission to e-sign every legal document in India. For example, a standard SaaS services agreement may be suitable for electronic execution, while a deed conveying immovable property requires separate legal review.
For a practical list, read Documents That Cannot Be eSigned in India: 2026 List.
How to use Section 10A in a contract workflow
Use this checklist before moving a contract type to electronic execution.
Step 1: Classify the document
Create a document-type matrix.
| Document type | Usually suitable for e-contracting? | Extra checks |
|---|---|---|
| SaaS subscription agreement | Yes | Clickwrap or signed order form evidence |
| NDA | Yes | Signer authority and confidentiality obligations |
| Employment offer letter | Usually yes | HR policy, labour law and acceptance trail |
| Vendor services agreement | Usually yes | Stamp duty, signatory authority, tax terms |
| Loan agreement | Depends | RBI, lender policy, stamp duty, KYC and evidence |
| Board resolution | Depends | Companies Act process, Articles, MCA filings if any |
| Property sale agreement | Often not suitable for electronic-only execution | Registration, stamp duty and IT Act exclusions |
| Power of attorney | Not suitable for electronic-only execution under IT Act recognition | Physical execution and notarisation/legalisation issues |
The word “usually” matters. You should test each document type against the contract value, governing law, counterparty type and sector rules.
Step 2: Check whether the IT Act excludes it
Before looking at convenience, ask whether the document falls under an excluded category.
If yes, do not rely only on Section 10A. Use counsel-approved physical execution or a hybrid process.
Step 3: Confirm the signing method
For India, common signing routes include:
- Aadhaar eSign through authorised eSign service providers.
- Digital Signature Certificate signing.
- Other electronic signature methods with supporting audit evidence, depending on the document and risk level.
The Controller of Certifying Authorities maintains official information on licensed certifying authorities and electronic signature infrastructure. See the Controller of Certifying Authorities website for the primary regulatory source.
For Aadhaar-based flows, the UIDAI explains the authentication ecosystem on its Aadhaar authentication page. Aadhaar eSign should be implemented only through authorised service providers and in compliance with applicable rules.
Step 4: Capture an audit trail
Your audit trail should answer five questions:
- Who signed?
- What document version did they sign?
- When did they sign?
- How was their identity or access verified?
- How do you know the document was not changed after signing?
A useful audit trail usually includes:
- Signer name and email or mobile identifier.
- IP address and device details, where lawfully collected.
- Timestamp for each event.
- Consent and authentication events.
- Final signed PDF.
- Document checksum or tamper-evidence record.
- Certificate information, if applicable.
If your team needs a single workflow for review, approval, e-signing and renewal tracking, ZiaSign provides legally binding e-signatures, approvals, obligations, renewals and contract lifecycle management in one workspace.
Step 5: Store the accepted version
Do not store only the latest template. Store the actual version accepted by the counterparty.
For clickwrap and online terms, keep:
- Terms version number.
- Date and time of acceptance.
- User account or customer identifier.
- IP/device logs, where appropriate.
- The screen or flow that presented the terms.
- Any linked policies incorporated by reference.
For negotiated contracts, keep:
- Final signed PDF.
- Approval history.
- Redline history, if material.
- Authority proof.
- Stamp duty proof.
- Renewal and termination dates.
Stamp duty and electronic contracts
Section 10A does not remove stamp duty. If an agreement is chargeable with stamp duty, electronic execution does not automatically make the duty disappear.
Stamp duty in India is a state-specific issue for many instruments. You should check:
- The nature of the instrument.
- The state whose stamp law applies.
- Whether e-stamping is available.
- Whether stamping must happen before or at execution.
- Consequences of under-stamping for admissibility and enforcement.
The central Indian Stamp Act, 1899 on India Code is a useful starting point, but many agreements require state-specific review. For material contracts, confirm the correct stamping process with counsel.
Worked example: SaaS vendor agreement
Assume an Indian SaaS company signs an annual vendor agreement with a cloud implementation partner.
Commercial terms:
- Annual fee: INR 12,00,000 plus GST.
- Term: 12 months.
- Payment: quarterly in advance.
- Governing law: India.
- Signers: CFO of customer and authorised partner signatory.
A practical execution plan:
- Legal approves the final agreement.
- Finance confirms tax and payment terms.
- Company secretary or operations team confirms signatory authority.
- Team checks applicable stamp duty for the state and instrument type.
- Agreement is e-signed using an approved method.
- Audit trail, signed PDF, authority proof and stamping proof are stored together.
- Renewal date is logged 90, 60 and 30 days before expiry.
Section 10A supports the electronic formation of the contract. It does not replace the stamp duty check, signatory authority check or evidence storage.
Board approvals and electronic contracts
Many business contracts need internal approval before signing. Section 10A does not decide whether the company’s internal approval process was valid.
For Indian companies, check:
- Articles of Association.
- Board-approved delegation of authority.
- Companies Act requirements for specific transactions.
- Whether the contract crosses internal value thresholds.
- Whether a board resolution or shareholder approval is needed.
If the contract is signed electronically without proper internal authority, the counterparty may still dispute capacity or authorisation. Your workflow should therefore link approval evidence to the final signed agreement.
Court admissibility and evidence
Electronic records can be used as evidence, but the process for proving them matters. India’s evidence law has specific rules for electronic records and certificates.
For current law, refer to the official Bharatiya Sakshya Adhiniyam, 2023 on India Code. Litigation teams should confirm evidentiary requirements with counsel, especially for high-value disputes.
From an operations perspective, assume you may one day need to prove:
- The signer had access to the signing email or mobile number.
- The signer completed the required authentication step.
- The document shown before signing matches the final document.
- The timestamp is reliable.
- The audit trail was not altered.
- The contract record was retained under a defensible retention policy.
Good evidence habits reduce avoidable disputes. They also make internal audits easier.
Practical checklist before relying on Section 10A
Use this checklist for each contract category.
| Check | Question | Owner |
|---|---|---|
| Document type | Is this document excluded under the IT Act? | Legal |
| Contract basics | Are offer, acceptance, consideration and lawful object clear? | Legal / Business |
| Signer authority | Is each signer authorised? | Legal / Company Secretary / Ops |
| Signing method | Is the e-sign method appropriate for the risk and law? | Legal / IT |
| Stamp duty | Has the correct state stamp duty treatment been confirmed? | Legal / Finance |
| Registration | Does the document need registration or notarisation? | Legal |
| Audit trail | Can we prove who signed what and when? | Ops / IT |
| Version control | Is the exact accepted version stored? | Legal Ops |
| Retention | Is the contract stored for the required period? | Legal / Finance |
| Dispute readiness | Can we produce evidence if challenged? | Legal |
Common mistakes with Section 10A
Treating Section 10A as a blanket e-sign permission
Section 10A validates electronic contracting as a mode of formation. It does not override exclusions, stamping, registration, sector rules or evidentiary requirements.
Ignoring the First Schedule exclusions
Some documents remain unsuitable for electronic-only execution under the IT Act framework. Always classify the document before sending it for e-signature.
Using weak acceptance flows
A buried link to terms may be harder to defend than an affirmative checkbox or signed order form. For online contracts, make acceptance clear and store the version accepted.
Forgetting stamp duty
A contract may be electronically valid but still under-stamped. That can create enforcement and admissibility problems.
Losing the audit trail
A signed PDF without event history may be harder to prove. Store the audit trail with the contract, not in a separate tool that no one can access later.
FAQ
Does Section 10A make electronic contracts valid in India?
Yes, Section 10A says a contract is not unenforceable only because electronic records or electronic means were used for offer, acceptance or revocation. The contract must still satisfy general contract law and other applicable legal requirements.
Is an email acceptance valid under Section 10A?
It can be, if the email shows clear acceptance of definite terms by a person with authority. In practice, disputes often turn on the facts: what was offered, what was accepted, whether terms were final and whether the sender had authority.
Does Section 10A apply to property sale agreements?
Be careful. The IT Act excludes contracts for sale or conveyance of immovable property, or any interest in such property, from its electronic recognition framework. Confirm the execution, stamping and registration route with property counsel.
Is Aadhaar eSign required for every electronic contract?
No. Aadhaar eSign is one recognised method, but not every electronic contract must use Aadhaar eSign. The right method depends on document type, risk, counterparty requirements and applicable law.
Does an electronically signed agreement need stamp paper?
If the instrument is chargeable with stamp duty, electronic signing does not remove that obligation. Check the applicable state stamp law and e-stamping process before execution.
Can foreign counterparties sign Indian contracts electronically?
Often yes, but you should check governing law, signing authority, authentication method, cross-border enforceability, tax documents and sector rules. For material contracts, get counsel to approve the execution process.
Closing note
Section 10A gives Indian businesses a clear legal foundation for electronic contracts. Use it with the rest of the legal checklist: document eligibility, valid signing method, stamp duty, authority, audit trail and retention.
For routine commercial contracts, a disciplined electronic workflow is usually safer than scattered emails and unsigned PDFs. For excluded, regulated or high-value documents, confirm the process with counsel before signing.
From the Zettaura team: Zettaura builds AI products for business teams, including ZiaSign for document review, legally binding e-signatures and contract lifecycle management. If your team is standardising electronic contract workflows, start with the legal checklist above and then choose tools that preserve evidence, approvals and renewal records.
