Home · Blog · Thai e-signature law for property contracts: what the ETA B.…
Compliance · Thai ETA B.E. 2544

Thai e-signature law for property contracts: what the ETA B.E. 2544 actually says

A plain-English walkthrough of Thailand's Electronic Transactions Act for property agents — what makes an e-signed contract enforceable, the three sections every CRM has to satisfy, and the one situation where you still need wet ink.

Published 18 May 2026 · 6 min read · DevProp Editorial

TL;DR

The Electronic Transactions Act B.E. 2544 (CE 2001) has been in force in Thailand for over two decades. It explicitly grants e-signatures the same legal effect as handwritten ones provided three conditions are met (Sections 9–11). For rental contracts, co-brokerage agreements, reservation deposits, and Sale and Purchase Agreements before Land Department registration, e-signatures are fully enforceable in Thai courts. The CRM has to do the work — proper identity verification, timestamping, and cryptographic hashing.

Every Thai property agent we talk to has the same vague worry about e-signatures: "But if it goes to court, will it actually hold?" The short answer is yes, and it has been yes since 2001 when the Royal Gazette published the Electronic Transactions Act B.E. 2544 (Buddhist Era 2544 = CE 2001).

The slightly longer answer involves understanding three specific sections of the law — the same three sections that every Thai-ETA-compliant CRM has to satisfy. Here they are in plain English.

Section 9 — The signature is attributable to the signatory

In other words: the system has to be able to prove who signed. A scribble at the bottom of a PDF doesn't qualify. What qualifies:

The combination of "OTP sent to a verified phone" + "IP log" + "timestamp" is the practical minimum. Anything below that gets challenged easily in a deposit dispute.

Section 10 — The signature is reliable and tamper-evident

This is the section that requires a real audit trail. The CRM has to log, immutably:

"Tamper-evident" in practice means: if anyone tries to edit the document after signing, the signature on the new version is automatically invalid. The hash mismatch is detectable by any third party with a copy of the original signed PDF and the audit log.

Section 11 — The signature is linked to the document

This is the most technical one. At the moment of signing, the system computes a cryptographic hash (SHA-256 or stronger) of the document content as it exists at signing time. That hash is embedded in the signature record. Any later change to the document content — even adding a single space — produces a different hash, and the signature no longer matches.

The practical effect: a Thai judge can be handed the signed PDF and the audit log separately, run a 30-second hash check, and confirm whether the PDF in evidence is the one that was actually signed. This is what gives e-signed Thai contracts the same weight as wet-ink ones.

What this means at the courthouse: Thai civil courts treat ETA-compliant e-signatures as admissible evidence with the same status as paper signatures. The burden shifts to the party disputing the signature to prove it was forged — which, given the audit trail, is extraordinarily hard.

The one place you still need wet ink: Land Department transfer

Section 456 of the Civil and Commercial Code requires registration of land-title transfers at the Land Department (กรมที่ดิน). Today, that registration still requires a physical signature on the official transfer form (ทอ. 1) at the local Land Office.

What this means in practice:

For 95% of the contracts a Thai agency handles in a year — rentals, co-broking agreements, reservations, deposit receipts — there is no Land Department step at all. E-signature covers the entire workflow.

What to ask your CRM vendor

If you're evaluating a CRM and the vendor claims "Thai e-signature support", make them demonstrate four things on a live call:

1. Send a Sale and Purchase Agreement for signature. Show me the OTP arriving at the buyer's phone and the IP being logged.

2. Open the signed PDF after signature. Show me the embedded signature certificate. It should be visible in any PDF reader.

3. Try to modify the signed PDF. Show me what happens — the signature should be marked invalid.

4. Export the audit trail. Show me the timestamps, IPs, and party order in a format I could hand to a lawyer.

If the vendor can't do all four, they don't have Thai-ETA e-signatures. They have a name field with a PDF attached, which is not the same thing and will not hold up in a contested case.

Why this matters for revenue

Agencies that adopt proper e-signatures see two compounding effects in their pipeline:

Over a year, agencies that ship proper e-signature workflows commonly report higher close rates on warm leads — not because the law changed, but because they removed the friction between intent and commitment.

See Thai-ETA e-signatures running on real contracts

The DevProp demo includes 8 contract templates with multi-party e-signing, OTP, IP logging, and PDF export with embedded signature certificates. No setup required.

Try the live demo →
Request a demo →