A click can matter, but context still matters
Many business and consumer agreements are formed through websites, email, apps and electronic procurement systems. India’s Information Technology Act, 2000 addresses recognition of electronic records and signatures, and section 10A states that a contract is not unenforceable solely because proposals, acceptance, revocation or related communications took electronic form. That principle does not mean every click creates a valid contract, that every electronic record proves who clicked, or that every kind of document can be electronic.
This is a general overview of selected central provisions, not advice about a particular platform, transaction or signature. Formation, authority, consent, statutory form requirements and excluded documents need transaction-specific review. Preserve the actual terms and version presented to the person accepting them.
What section 10A does and does not say
Section 10A of the Information Technology Act provides that a contract is not to be deemed unenforceable solely because electronic form or means were used for the communication of proposals, acceptance, revocation of proposals or acceptances, as the case may be. It removes a form-based objection in that defined situation. It does not dispense with ordinary contract questions such as offer, acceptance, certainty, capacity, consent, authority, consideration where required, or compliance with a separate law.
Sections 4 and 5 address legal recognition of electronic records and electronic signatures, subject to the Act and its conditions. Section 1(4), read with the First Schedule as amended, excludes specified documents or transactions from the Act’s application. The schedule has been amended, so a list copied from an older Act PDF should not be treated as the current exclusion list. Amendments and notifications can affect the schedule; the precise current text and document type must be checked before relying on electronic execution. Exclusion from this Act’s recognition framework does not itself answer every question about a transaction or whether another law permits a particular electronic process.
An illustrative example
A fictional equipment supplier emails a customer a quotation with a link to online terms. The customer’s procurement employee clicks “accept,” but later the company says the employee lacked authority and that the linked terms changed after acceptance.
A reliable record would help establish which quotation and terms were presented, when they were available, the acceptance event and its timestamp, the employee’s role or authority, any confirmation email, subsequent performance, and the version history. It would not automatically settle whether the employee had authority or whether an acceptance was legally effective. Those questions depend on evidence, the company’s authorization arrangements, the communications and applicable law.
Evidence and process checklist
- Preserve the offer, order, linked terms and attachments in the exact version shown at the time, with a reliable capture date and version identifier.
- Record the identity and role of the person acting, the method of authentication, and the basis for believing that person could bind the relevant party. Avoid storing unnecessary sensitive data in the contract file.
- Keep event logs showing proposal, acceptance, revocation or amendment, with time zone, system clock source and any confirmation delivered to the parties.
- Retain the acceptance screen and the complete terms, not only a database flag or screenshot that omits the surrounding content.
- Record how changes to terms are communicated and whether renewed acceptance is captured. Keep old and new versions separately.
- Preserve related performance evidence: delivery, payment, invoices, support requests and communications. Later conduct may be relevant but does not always cure a formation defect.
- Check whether the transaction or instrument falls within the current First Schedule, and whether another statute requires a particular form, signature, registration or attestation.
Limits and primary sources
An electronic record is not self-authenticating simply because it exists. This article does not explain evidentiary admissibility, certificate requirements or the Bharatiya Sakshya Adhiniyam; those are a distinct topic and should not be conflated with whether electronic contracts are recognized. It also does not address consumer-specific disclosures, regulated electronic signatures, cross-border choice of law, stamp duty, notarisation or land transactions.


