Civil Law and UAE Programmable Law and Automated Obligation Systems

1. Introduction

Programmable law refers to legal rights and obligations that are expressed partly or wholly through computer-readable rules, algorithms, smart contracts, automated transaction systems, or other software.

An automated obligation system goes one step further. Instead of a person manually performing every contractual step, software automatically performs an obligation when predefined conditions are satisfied.

Examples include:

• automatic payment after delivery confirmation;
• automatic release of escrow;
• smart-contract transfer of digital assets;
• automatic calculation of interest;
• automated margin calls;
• insurance payouts triggered by verified events;
• automatic platform refunds;
• algorithmic execution of securities or digital-asset transactions;
• automated enforcement of contractual conditions.

The UAE has an unusually important statutory basis for this area. Federal Decree-Law No. 46 of 2021 on Electronic Transactions and Trust Services expressly recognises contracts formed between automated electronic systems. Article 11 provides that a contract may be formed between automated electronic mediums programmed in advance and remains valid and enforceable even without direct human intervention.

At the same time, the new Federal Decree by Law No. 25 of 2025 promulgating the Civil Transactions Law replaced the 1985 Civil Transactions Law from 1 June 2026. Therefore, current UAE civil-law analysis must use the 2025 Civil Transactions Law for transactions governed by the new regime, while older cases may require historical treatment.

2. Meaning of Programmable Law

Traditional civil law works through a relatively simple sequence:

Legal rule → Human decision → Contractual performance → Breach → Court remedy

Programmable law introduces another layer:

Legal rule → Contractual rule → Code/algorithm → Automatic execution → Legal consequence

For example:

“If the buyer deposits AED 1 million, release the digital asset to the buyer.”

A smart contract might automatically execute this instruction.

The important legal question is:

Does the execution of computer code itself determine the parties' legal rights, or is the code merely a mechanism for implementing an underlying legal agreement?

Under UAE law, automatic electronic contracting is legally recognised, but that does not mean that computer code can override mandatory legislation, public policy, consumer protections, court orders or other legal restrictions.

3. UAE Legal Framework

A. Federal Decree-Law No. 46 of 2021

This is the most directly relevant federal legislation.

Article 5 — Electronic documents

Electronic documents do not lose legal force merely because they are electronic.

Article 10 — Electronic contracts

Offer and acceptance may be expressed electronically.

A contract does not lose:

• validity;
• evidential value; or
• enforceability

merely because it is made through electronic documents.

Article 11 — Automated electronic transactions

This is particularly important for programmable law.

The law expressly permits contracts between automated electronic systems that have been programmed in advance.

Such contracts remain legally effective even where there is no direct human intervention at the moment the contract is formed.

The legislation also recognises a transaction between an automated system belonging to one person and another person where the latter knows, or should know, that the system will operate automatically.

4. What Is an Automated Obligation?

An automated obligation is an obligation whose performance is triggered or carried out automatically by technology.

For example:

Ordinary contract

A buyer must pay AED 100,000 within 30 days.

Human actors:

Buyer → payment → Seller

Automated contract

A smart contract contains:

If delivery is digitally verified, automatically transfer AED 100,000.

The structure becomes:

Delivery verification → algorithm → payment

The legal obligation remains contractual, but performance is automated.

5. Programmable Law Is Not the Same as Smart Contracts

These concepts should be distinguished.

Programmable law

A broader concept involving the conversion of legal rules into machine-readable or computational rules.

Smart contract

A software-based mechanism that automatically performs specified transactions or contractual functions, often using blockchain or distributed-ledger technology.

Automated electronic transaction

A statutory concept recognised by UAE Federal Decree-Law No. 46 of 2021.

Automated obligation system

A broader practical category that may include:

• smart contracts;
• banking algorithms;
• automated payment systems;
• escrow systems;
• insurance triggers;
• trading systems;
• digital platforms.

Therefore:

Every smart contract may involve programmable obligations, but not every programmable obligation is a blockchain smart contract.

6. Relationship Between Code and Contract

A major civil-law issue is whether:

“Code is law.”

In a strict sense, this proposition is too broad.

Computer code determines what a technological system will execute. But the legal validity of that execution remains subject to the applicable law.

Suppose a program automatically transfers property because a programmed condition has been satisfied.

The code may successfully execute the transfer.

However, a court may still need to determine:

• whether a valid contract existed;
• whether consent existed;
• whether the parties had capacity;
• whether the transaction was lawful;
• whether the programmed condition was valid;
• whether the code contained an error;
• whether fraud occurred;
• whether the transaction violated mandatory legislation;
• whether damages resulted.

Thus:

Technical execution ≠ automatic legal validity of every consequence.

7. Consent in Automated Contracting

Traditional contract law asks:

Did the parties consent?

Automated contracting adds:

Did the parties consent to the operation of the automated system?

Under Article 11 of Federal Decree-Law No. 46 of 2021, direct human intervention at the time of automated contracting is unnecessary where the statutory conditions are satisfied.

This is important because a person may have consented earlier to a system that subsequently executes thousands of transactions automatically.

For example:

A trading company programs its system to purchase goods whenever the price falls below AED 100.

The computer purchases 500 units at AED 95.

The company generally cannot argue merely:

“No employee clicked the purchase button.”

The legal framework specifically contemplates automated transactions.

8. Attribution

A second important question is:

Who is legally responsible for the action of the machine?

The UAE Electronic Transactions Law contains attribution rules for electronic documents and transactions. The system does not become an independent legal person simply because it acts automatically.

Normally, the legal analysis traces the automated action back to:

• the person controlling the system;
• the person who programmed or authorised it;
• the contracting party;
• the relevant intermediary or service provider.

Therefore:

Automation changes the method of performance; it does not automatically eliminate human legal responsibility.

9. Errors in Automated Systems

One of the most difficult problems is an algorithmic error.

Suppose a smart contract is programmed:

If A occurs, pay AED 1 million.

Due to a programming error, the system interprets a completely different event as A and pays the money.

Questions arise:

1. Was there a valid contract?
2. What did the parties intend?
3. Was the code the contractual text?
4. Was the programming error known?
5. Who created the error?
6. Who controlled the system?
7. Was the receiving party aware of the mistake?
8. Can restitution be claimed?
9. Was the transaction irreversible?

These questions cannot always be answered simply by looking at the blockchain record.

10. Smart Contracts and Digital Assets in the UAE

The DIFC has developed particularly significant legal infrastructure for digital assets.

The DIFC Digital Economy Court Rules now expressly define a digital asset to include a cryptoasset, digital token, smart contract, or other digital/coded representation of value, rights, obligations, assets or transactions.

The Digital Economy Court can hear claims involving:

• blockchain;
• distributed-ledger technology;
• digital assets;
• artificial intelligence;
• automated dispute resolution;
• DAOs;
• DeFi;
• DApps;
• digital signatures;
• digital identity;
• digital payments;
• Web3 transactions. 

This demonstrates that UAE legal institutions increasingly treat automated legal and financial systems as ordinary subjects of civil adjudication rather than as legally invisible technology.

11. Automated Performance and Good Faith

Automation does not remove the principle of good faith.

A party cannot necessarily rely on a software function to obtain an unfair result if the underlying contractual or legal framework does not permit that result.

This becomes particularly important where:

• the code contains an obvious error;
• one party exploits a programming defect;
• a platform deliberately manipulates the algorithm;
• the automated mechanism contradicts the underlying agreement;
• the system produces an unintended windfall.

The UAE civil-law system therefore needs to reconcile:

certainty of automated execution

with

good faith, legitimate expectations and prohibition of abuse.

12. Automated Obligations and Liability

A programmable obligation may produce several forms of liability.

Contractual liability

If the automated system fails to perform a contractual obligation.

Tort liability

If an algorithm causes independent damage to another person.

Professional liability

If the system was negligently designed, audited or operated.

Platform liability

Where an intermediary controls the automated infrastructure.

Custodial liability

Where an entity holds digital assets and automatically transfers them when conditions are met.

Restitution

Where an automated system transfers something without a valid legal basis.

13. Case Laws

Important qualification: reported UAE mainland judgments directly deciding the modern concept of “programmable law” are still limited. The following authorities therefore include important DIFC digital-economy cases and cases concerning electronic contracting, automated systems, digital assets and contractual obligations. DIFC decisions are not automatically binding on mainland UAE courts, but they are particularly relevant to UAE digital-law development.

Case 1 — Gate Mena DMCC / Huobi Mena FZE v Tabarak Investment Capital Ltd

[2023] DIFC CA 002

This is one of the most important UAE-region authorities for digital assets.

The dispute involved Bitcoin transferred into a custodial arrangement and the obligations associated with control and release of the cryptocurrency.

The DIFC Court of Appeal considered the nature of Bitcoin and the significance of control over a digital asset. The Court also considered the contractual obligations of the cryptocurrency custodian.

The Court noted that the DIFC Digital Assets Law subsequently addressed digital assets as intangible property and dealt expressly with control and title, although that legislation was not retrospective.

Principle

A digital transaction can create legally enforceable obligations even though the underlying asset and its control mechanism are technological.

Case 2 — Gate Mena DMCC / Huobi Mena FZE v Tabarak Investment Capital Ltd

[2024] DIFC DEC 002

This later Digital Economy Court decision is particularly useful for automated obligation systems.

The Court considered the precise nature of Tabarak's obligation concerning Bitcoin held in custody. It distinguished between an obligation to exercise reasonable care and an obligation to achieve a particular result.

The contractual wording and the degree of control exercised over the asset were important in determining the nature of the obligation.

Principle

Technology does not determine the legal standard of performance by itself.

The court still asks:

What obligation did the parties legally undertake?

Case 3 — ICICI Bank Ltd v Bavaguthu Raghuram Shetty

[2022] DIFC CFI 034

This case involved guarantees bearing electronic or copied signatures.

The Court examined whether electronic signatures had actually been authorised by the alleged signatory.

It found that an electronic or copied signature is not automatically invalid merely because it is not a traditional wet-ink signature. The critical question included whether its application was authorised.

The Court of Appeal confirmed the importance of the question whether the electronic signature was authorised by the person concerned.

Principle

Digital execution requires legal attribution.

The fact that a computer can place a signature on a document does not by itself establish that the relevant person legally authorised the signature.

Case 4 — Ondina v Olin

[2025] DIFC CFI 046

This case dealt with contractual modification through email and electronic signature.

The Court examined whether email communications could satisfy the requirement for a signed written variation.

The Court held that the relevant electronic communications could satisfy the electronic-signature requirement because the email contained electronically stored information and the sender used her name with the intention of signing/confirming the agreement.

Principle

A legally relevant contractual act may be accomplished through electronic communication where the applicable statutory requirements are satisfied.

This is highly relevant to automated contracting because an automated system can operate on the basis of a previously established electronic contractual framework.

Case 5 — Naho v Neukirchi

[2024] DIFC SCT 415

The Court considered the statutory concept of an electronic signature.

It referred to the DIFC Electronic Transactions Law, under which an electronic signature can satisfy a legal requirement for a signature where the statutory conditions are met.

The case illustrates the broader judicial acceptance of electronic methods for establishing contractual consent.

Principle

Electronic form does not prevent a transaction from having legal consequences merely because traditional paper signatures are absent.

Case 6 — Dimension B+ Ltd v Saleh Abdelkarim Hussain Abdelrahman Almaazmi

[2024] DIFC CFI 094

The case concerned a disputed agreement bearing an alleged electronic signature.

The defendant argued that the electronic signature had been attached without consent and therefore challenged the validity of the agreement and jurisdiction clause.

The case demonstrates the importance of proving:

• authenticity;
• authority;
• attribution;
• consent;
• integrity of the electronic record.

Principle

The existence of electronic code or an electronic signature does not eliminate the need for proof of legal authorisation.

Case 7 — Tavira Securities Ltd v Re Point Ventures FZCO & Others

[2017] DIFC CFI 026

The dispute concerned contractual obligations to settle securities trades.

The Court considered the contractual relationship and the obligations arising from transactions in financial instruments.

Although not a smart-contract case, it is relevant by analogy because automated financial systems frequently execute securities transactions based upon predetermined contractual instructions.

Principle

Automated execution of a financial transaction does not eliminate the underlying contractual obligations.

Case 8 — Hexagon Holdings (Cayman) Ltd v DIFC Authority & DIFC Investments LLC

[2019] DIFC CFI 013

The Court considered contractual obligations, including the importance of express contractual terms concerning the timing and nature of performance.

The case illustrates that contractual programming or automation cannot be separated from ordinary rules of contractual interpretation.

Principle

Even where contractual obligations are expressed through sophisticated systems, courts must determine what the parties legally agreed and the consequences attached to the relevant obligation.

14. Case-Law Table

15. Programmable Obligations and Mistake

A particularly difficult issue is mistaken execution.

Suppose:

Code says: transfer 100 tokens if X occurs.

But because of a coding error:

1,000 tokens are transferred.

The legal analysis should not simply be:

“The blockchain executed it, therefore it is final.”

Instead, a court may need to examine:

1. the written contract;
2. the code;
3. parties' intention;
4. system specifications;
5. representations made before execution;
6. knowledge of the error;
7. whether the recipient exploited the error;
8. applicable restitution rules;
9. whether the transaction is reversible;
10. whether third-party rights intervened.

16. Code Versus Natural-Language Contract

There are potentially three different documents:

1. Legal contract

Example:

“Seller shall transfer the asset after payment.”

2. Technical specification

Example:

“System will release asset when payment confirmation = TRUE.”

3. Computer code

Example:

IF payment_verified = TRUE THEN transfer_asset()

These three layers may not always say exactly the same thing.

This creates a major legal question:

Which layer controls if they conflict?

The contract should ideally specify:

• whether code is legally controlling;
• whether natural-language terms prevail;
• who controls the oracle;
• what happens after system failure;
• how errors are corrected;
• whether emergency suspension is permitted;
• how disputes are resolved.

17. Oracle Problems

Smart contracts often require external information.

For example:

“Pay insurance compensation if rainfall exceeds 200 mm.”

The blockchain itself cannot necessarily know rainfall.

An oracle supplies the external information.

This creates legal risks:

• incorrect data;
• manipulated data;
• delayed data;
• conflicting data sources;
• oracle failure;
• malicious intervention.

Thus, the oracle itself can become an important participant in the obligation system.

18. Automated Payment Systems

A UAE business could establish:

Delivery confirmed → system verifies delivery → payment automatically released.

Advantages include:

• speed;
• lower transaction costs;
• reduced administrative work;
• predictable execution;
• auditability;
• reduced need for manual intervention.

But risks include:

• incorrect delivery data;
• fraudulent confirmation;
• system failure;
• duplicate payment;
• cyberattack;
• erroneous programming;
• inability to reverse payment.

The legal contract should therefore contain an override mechanism.

19. Consumer Protection and Automated Obligations

Automation cannot be used to contract out of mandatory consumer protections.

For example, an online platform should not simply program:

“All refunds are automatically prohibited.”

If mandatory UAE consumer law provides a consumer remedy, software cannot legitimately eliminate that statutory right merely by placing a condition in code.

This illustrates:

Private code < Mandatory law

where mandatory law applies.

20. Public Policy Limits

Programmable contracts must also comply with:

• public order;
• mandatory legislation;
• licensing requirements;
• financial regulation;
• consumer protection;
• data protection;
• sanctions requirements;
• anti-money-laundering requirements;
• court orders.

Therefore, a smart contract should not be understood as a legal mechanism capable of operating outside the legal system.

21. Automated Enforcement

The most significant development is the possibility of self-executing obligations.

Traditional enforcement:

Breach → notice → lawsuit → judgment → execution

Automated enforcement:

Trigger → algorithm → automatic execution

This can be useful for:

• escrow;
• payment;
• collateral;
• royalties;
• digital assets;
• supply chains.

But automatic execution raises a fundamental civil-law issue:

Should every technically executable obligation also be legally enforceable?

The answer is not necessarily yes.

The legal system remains responsible for deciding questions such as:

• validity;
• consent;
• mistake;
• fraud;
• illegality;
• restitution;
• damages;
• public policy.

22. UAE Digital Economy Court

The DIFC's Digital Economy Court is especially important for this subject.

Its rules expressly cover claims involving:

• smart contracts;
• digital assets;
• blockchain;
• AI;
• automatic dispute resolution;
• DAOs;
• DeFi;
• DApps;
• digital signatures;
• digital identity;
• digital payments. 

This is significant because it creates an institutional framework capable of dealing with disputes generated by automated legal and technological systems.

23. Advantages of Programmable Obligations

1. Certainty

Predefined conditions can make performance predictable.

2. Speed

Performance can occur immediately after a trigger.

3. Transparency

Blockchain transactions can provide an auditable record.

4. Reduced administrative costs

Fewer manual steps are required.

5. Reduced opportunistic behaviour

A party may have less ability to deliberately delay performance.

6. Automatic calculation

Interest, penalties or payments can be calculated automatically, subject always to applicable law.

24. Risks

1. Coding error

The code may not accurately reflect the agreement.

2. Oracle failure

External information may be wrong.

3. Cyberattack

A malicious actor may manipulate the system.

4. Irreversibility

Some blockchain transactions cannot easily be reversed.

5. Attribution problems

It may be difficult to identify who authorised the transaction.

6. Jurisdiction

Parties and servers may be located in different countries.

7. Legal ambiguity

Code may execute something that the legal system considers invalid.

8. Human oversight

Completely automated systems may lack an effective mechanism for exceptional circumstances.

25. Recommended Legal Architecture

A sophisticated UAE programmable contract should contain two layers.

Layer 1 — Legal layer

It should specify:

• parties;
• rights;
• obligations;
• governing law;
• dispute resolution;
• remedies;
• termination;
• force majeure;
• mistake;
• liability;
• data protection;
• emergency intervention.

Layer 2 — Technical layer

It should specify:

• code;
• triggers;
• APIs;
• oracle;
• authentication;
• security;
• audit mechanisms;
• automated payment;
• suspension mechanism;
• recovery mechanism.

The two layers should expressly state which controls if there is a conflict.

26. Key Legal Formula

The subject can be remembered as:

Valid Legal Obligation + Valid Consent + Authorised Automation + Reliable Code + Lawful Trigger + Proper Attribution + Legal Remedy = Enforceable Automated Obligation

Automation alone is insufficient.

27. Important Distinction

28. Short Exam Answer

Programmable law and automated obligation systems in UAE civil law refer to the use of software, algorithms, electronic systems and smart contracts to create, perform or enforce legal obligations. Federal Decree-Law No. 46 of 2021 is particularly important because Article 10 recognises electronic contracts and Article 11 expressly validates contracts concluded between automated electronic systems even without direct human intervention.

The modern UAE approach increasingly recognises digital assets and smart contracts as subjects of legal rights and obligations. The DIFC Digital Economy Court Rules expressly include smart contracts, blockchain, digital assets, AI, automated dispute resolution, DAOs, DeFi and DApps within its digital-economy jurisdiction.

Cases such as Gate Mena v Tabarak, ICICI Bank v Shetty, Ondina v Olin, Naho v Neukirchi, Dimension B+ v Almaazmi, and Tavira Securities v Re Point Ventures demonstrate that technological execution does not eliminate traditional questions of consent, attribution, contractual interpretation, authority and legal responsibility.

Conclusion

UAE civil law is moving from a model in which legal obligations are primarily human-executed toward one in which some obligations can be machine-executed.

The most important statutory development is Article 11 of the UAE Electronic Transactions and Trust Services Law, which expressly recognises automated electronic contracting.

However, automation does not replace civil law.

A computer can execute a transaction, but civil law still determines:

• whether the obligation was valid;
• whether consent existed;
• who is responsible;
• whether the code accurately represented the agreement;
• whether a mistake occurred;
• whether performance was lawful;
• whether restitution is available;
• whether damages are recoverable.

The central principle is therefore:

Code may automate performance, but law determines the legal status and consequences of that performance.

The UAE's recognition of automated electronic transactions, together with the DIFC's specialised Digital Economy Court and its express jurisdiction over smart contracts and blockchain disputes, provides a significant legal foundation for the development of programmable private law and automated obligation systems.