It is a common assumption that a signed PDF, emailed back and forth, is enough to hold someone to an agreement. In an Indian courtroom, that assumption can fail. Legal recognition of an electronic contract and the admissibility of that contract as evidence are two different things — and getting the second right is what protects you when a deal goes wrong.
Recognition is not the same as proof
The Information Technology Act, 2000 gives electronic records and electronic signatures the same legal standing as their paper equivalents. That is what makes an online agreement valid. But validity only settles whether a contract can exist in electronic form. When a dispute reaches a court, the separate question is whether the document can be admitted as evidence — and that is governed by the law of evidence, not the IT Act alone.
The electronic-evidence requirement
For years, Section 65B of the Indian Evidence Act, 1872 set out how an electronic record may be proved: broadly, that a computer output is admissible if it is accompanied by a certificate describing how the record was produced and confirming the integrity of the system that produced it. That framework now continues under the Bharatiya Sakshya Adhiniyam, 2023, which replaced the 1872 Act. The practical point has not changed: an electronic record usually needs an accompanying certificate, and a court will look closely at whether the record is complete and unaltered.
A document is only as strong as the record of how it was executed. The signature is the easy part; the evidence around it is what survives scrutiny.
What a court actually looks for
Beyond the certificate, a judge is weighing reliability. Three things tend to matter most in practice:
1. Identity of the signers
Who signed, and how was that person verified? An Aadhaar-based eSign, backed by an eKYC check, ties a signature to a verified identity far more convincingly than a typed name or a pasted image of a signature.
2. Integrity of the document
Can you show the contract was not altered after signing? A tamper-evident seal and a cryptographic hash captured at the moment of execution let you demonstrate that the version in court is the version that was signed.
3. A complete audit trail
When was it sent, viewed, signed and stamped? A timestamped trail — including IP, device and the sequence of events — turns “we agree this was signed” into “here is exactly how it was signed.”
Stamping still counts
Admissibility can also turn on stamp duty. An instrument that is insufficiently stamped may be impounded before a court will even consider it. e-Stamping the contract for the correct state duty at the point of execution removes that obstacle and keeps the document ready to be relied upon.
Putting it together
A digital contract that stands up in court is rarely the product of one feature. It is the combination — verified identity, valid signature, correct stamping, a tamper-evident record and a clean audit trail — assembled at the moment of execution and preserved afterwards. That is the difference between a file that looks signed and an instrument you can confidently produce as proof.
This is a sample article for layout purposes and is general information, not legal advice. Laws and stamp-duty rates vary by state and change over time — confirm the current position for your situation before relying on it.