Send, sign, and seal documents with evidence designed for Qatar’s e-transactions law — in Arabic and English. Built in Doha for GCC business, with cryptographic evidence on every signature.
The legal basis
Qatar recognised electronic signatures in Decree-Law No. 16 of 2010 on Electronic Commerce and Transactions. Article 28 gives an e-signature evidential weight when the signature data is uniquely linked to the signatory and under their sole control at the time of signing. SahlSign records the signer’s one-time-code (OTP) verification and seals the document; signatures under the signer’s sole control need a certificate-based tier.
In 2025 the Communications Regulatory Authority (CRA) added a formal Trust Services regime (Decision 3/2025, QA-TSF), aligning Qatar with the international SES/AES/QES tier model. SahlSign is not a CRA-licensed trust service provider. A well-evidenced electronic signature is generally recognised for most commercial documents — contracts, offers, NDAs, HR paperwork — though enforceability depends on the document and the evidence, and some documents are excluded.
SahlSign strengthens every signature with evidence that supports authenticity if a signature is challenged: signer verification by one-time code (OTP), a tamper-evident audit trail, a PAdES digital seal, and an RFC 3161 trusted timestamp.
Read the full 2026 legal guide to electronic signatures in Qatar ←
Compare e-signature laws across the GCC & MENA ←
This page is general information, not legal advice.
Every completion certificate lists each signer, the full audit timeline with timestamps and IP addresses, and the original and signed document hashes, with a QR code to verify it online — evidence your legal team can rely on if a signature is disputed, not a generic checkmark.
True RTL signing ceremony, Arabic typed signatures rendered correctly, and bilingual Arabic/English certificates of completion.
PAdES digital seal, RFC 3161 trusted timestamp, signer verification by one-time code (OTP), and a tamper-evident hash-chained audit trail — verifiable by anyone at our public verify page.
Send by email; signers verify with a one-time code and sign from any device — desktop or phone, Arabic or English.
Offer letters, employment contracts, and policy acknowledgements — signed before day one, archived with a bilingual certificate.
Sequential approval chains for POs and contracts — each signer in turn, with the full order enforced server-side.
Lease agreements and handover forms signed remotely by landlord, tenant, and agent — no office visit.
Close deals the same day: send, OTP-verify, sign, and receive the sealed PDF plus completion certificate automatically.
QFC, QSTP, and mainland entities run the same flow — and every party receives the same sealed, bilingual certificate of completion.
Signers in Saudi, the UAE, Bahrain, Kuwait, or Oman? Everyone signs the same envelope and receives the same sealed certificate.
Yes, for most commercial documents — with exceptions. eSign, e-sign, e-signature, and electronic signature all name the same thing, and it is generally recognised in Qatar under Decree-Law 16/2010, with the CRA’s 2025 Trust Services framework on top. SahlSign is an eSign platform built for Qatar: Arabic-first, with a bilingual certificate of completion and full audit trail for every document.
Yes, for most commercial documents — with exceptions. Decree-Law 16/2010 (Article 28) gives electronic signatures evidential weight when the signature data is uniquely linked to the signatory and under their sole control. The CRA’s 2025 Trust Services regime added a formal tier framework on top. Many commercial documents can be e-signed in Qatar; enforceability depends on the document and the evidence, and some documents are excluded.
Like most jurisdictions, Qatar excludes certain instruments from electronic execution — matters of personal status (marriage, divorce), and documents requiring notarisation or registration such as real-estate title transfers. Day-to-day commercial contracts are not excluded.
No platform can guarantee a court outcome. SahlSign produces evidence that supports authenticity if a signature is challenged: signer verification by one-time code (OTP), a hash-chained tamper-evident audit trail, a PAdES digital seal with an RFC 3161 trusted timestamp, and a bilingual completion certificate with the full audit timeline and document hashes.
No. Signers receive an email link, verify with a one-time code, and sign from any device — in Arabic or English.
Natively. The signing ceremony is true RTL, typed Arabic signatures render correctly in the sealed PDF, and every completion certificate is bilingual Arabic/English — because it was built Arabic-first, not translated.
Free plan includes 5 documents a month. Signers never need an account.
Start free