Every freelancer who has ever sent a contract to sign over a phone has had the same quiet worry: is a signature the client typed with their thumb actually worth anything? If it ever came to a dispute, would it hold up, or is it just a name in a box?
It is a fair question, and the answer matters more now that so much freelance work is agreed over WhatsApp and email. Here is the plain version, written for freelancers and not for lawyers — with a note at the end on where you genuinely should not rely on it.
A quick disclaimer: this is a practical explainer, not legal advice. For a high-value or unusual engagement, talk to a lawyer.
The short answer: yes, with conditions
Electronic signatures are legally recognised in India. The Information Technology Act, 2000 gives electronic signatures and electronic records the same legal standing as their paper equivalents, and electronic records are admissible as evidence in Indian courts — as long as they meet the certification requirements the law sets out, which we come to below.
So a freelance service agreement your client signs electronically is, for ordinary project work, a real agreement. The conditions are about how it is signed and what proof sits behind it — which is where most of the confusion lives.
What the law actually recognises
The IT Act treats a couple of different things as valid, and it helps to know which is which:
- Digital signatures — the certificate-based kind (a DSC), built on cryptographic keys. These carry a strong legal presumption of validity and are what companies use for filings and high-value contracts.
- Aadhaar-based eSign — an electronic signature tied to Aadhaar e-KYC. Also carries a statutory presumption and is widely used for online agreements.
- Other electronic signatures and records — a signature typed or drawn and confirmed through a verification step. These are valid and admissible too, but their weight in a dispute depends on the evidence around them, rather than a built-in legal presumption.
For a ₹40,000 design project or a standard freelance NDA, that last category is normally what you are using — and for that kind of work, it is generally enough.
What you cannot sign electronically
This is the part worth memorising, because the exceptions are specific. The IT Act does not apply to a short list of documents, which means these still need traditional signatures:
- Wills and other testamentary dispositions
- Negotiable instruments other than a cheque (for example, a promissory note)
- Powers of attorney
- Trust deeds
- Any contract for the sale or conveyance of immovable property
Notice what is not on that list: an ordinary freelance service agreement, a project contract, or a standard NDA. Those are exactly the documents freelancers deal with — and they are fair game for e-signing.
What actually makes an e-signature hold up
Here is the thing most people miss. A signature is only as good as your ability to prove, later, that a specific person agreed to a specific document at a specific time. That proof is the audit trail.
"A name typed in a box" and "a signature verified with an OTP, timestamped, with a record of the version that was signed" are both electronic signatures — but only one of them is easy to stand behind if a client later says "I never agreed to that."
The admissibility of electronic records in court is governed by what used to be Section 65B of the Indian Evidence Act, 1872, and is now Section 63 of the Bharatiya Sakshya Adhiniyam, 2023, which came into force on 1 July 2024. In practice, what these provisions ask for is a reliable record of how the electronic document was produced and stored. So the useful question is not "is my e-signature legal" — it usually is — but "can I show who signed, when, and how it was verified."
Where a simple e-signature is enough — and where it is not
For most freelance situations, an OTP-verified electronic signature with a clear audit trail is more than enough:
- Project and service agreements
- Scope and deliverables sign-offs
- Standard non-disclosure agreements
- Retainer terms
Where you should reach for a certificate-based DSC, an Aadhaar eSign, or a lawyer instead:
- Anything on the excluded list above (property, wills, powers of attorney)
- High-value contracts where the other side is likely to fight
- Agreements that need to be registered or stamped under state law
- Anything with long-term exclusivity or large liability
The rule of thumb: the bigger the stakes, the more formal the signature should be.
How Riffit handles this
When you send a contract through Riffit, the client signs with a typed or drawn signature confirmed by an OTP, and every signed contract comes with a separate audit-trail record — who signed, when, from where, and how it was verified — structured to address the Section 65B / Section 63 requirements for electronic records. That is the difference between "I have a signed PDF somewhere" and "I have a record I can point to."
It will not turn a property sale deed into something you can sign on your phone — nothing can, by law. But for the service agreements freelancers actually send, it removes the guesswork.
If you are putting one together, start with a solid freelance contract template for India, and the full guide to sending a contract your client will sign covers the whole flow end to end.
FAQ
Yes. Electronic signatures and electronic records are recognised under the Information Technology Act, 2000, and electronic records are admissible as evidence. A few document types are excluded — wills, powers of attorney, trusts, most negotiable instruments, and contracts for the sale of immovable property — but ordinary freelance service agreements are not among them.
Written by
Aaqil · Founder, Riffit
Runs 11pixels Design Studio in Bangalore. Built Riffit because invoicing from a laptop in traffic wasn't an option. Writes about invoicing, contracts, freelancing, and running a solo business in India.