1. Introduction

Algorithmic contract formation disputes arise when parties disagree about whether a legally binding contract was created through automated software, artificial intelligence systems, electronic platforms, trading algorithms, or smart contracts.

Traditional contract law generally examines offer, acceptance, consideration where required, intention to create legal relations, capacity, certainty of terms, and compliance with applicable formalities. Algorithmic contracting complicates these questions because software may communicate offers, accept orders, negotiate prices, or execute transactions without a person reviewing each individual action.

For example, an online trading algorithm may accept an order at an unintended price, an automated purchasing system may place duplicate orders, or a chatbot may communicate a commercial commitment that the business later disputes.

The central legal question is whether the conduct of the parties and the operation of the relevant system created an enforceable agreement.

Algorithmic contract formation disputes may involve:

Automated offer and acceptance.

AI-generated negotiations and contractual promises.

Electronic ordering and confirmation systems.

Trading bots and algorithmic pricing.

Smart contracts and self-executing transactions.

Software errors and mistaken electronic communications.

Automated acceptance of online terms and conditions.

Unauthorized transactions and agency disputes.

Conflicting software records and transaction logs.

Contract cancellation, restitution, and damages.

Core principle: The use of an algorithm does not, by itself, prevent a contract from forming. The decisive issues are the applicable law, the parties' conduct, the authority of the system or its operator, and whether the ordinary requirements of contract formation have been satisfied.

2. Meaning and legal nature of algorithmic contract formation

Algorithmic contract formation occurs when software or an automated system performs one or more functions that contribute to creating a contractual relationship.

A. Automated offer and acceptance

A business may publish an electronic offer, and a customer may accept it by clicking a button, submitting an order, or completing an automated checkout process.

Disputes may arise where the system records an acceptance but the business claims that the transaction was incomplete, unauthorized, or subject to further approval.

Courts examine the platform's terms, the wording of the communication, the sequence of events, and whether the parties objectively manifested an intention to enter a contract.

B. AI-assisted negotiations

AI systems may draft proposals, negotiate commercial terms, generate quotations, or communicate with customers.

The legal questions include whether the AI communication constituted an offer, whether the person or organization operating the system authorized the communication, and whether the other party reasonably understood it as a binding commitment.

An AI-generated statement is not automatically a contractual promise. Its legal effect depends on the context, authority, wording, and applicable contract law.

C. Algorithmic trading

Trading systems may automatically submit or accept bids and offers. Software defects, incorrect market data, or unexpected interactions between trading algorithms can produce disputed transactions.

The parties may disagree about whether an erroneous trade is binding, whether an established cancellation rule applies, or whether a party may obtain rescission or damages.

D. Smart-contract formation

Smart contracts execute programmed instructions when specified conditions occur. A transaction may automatically transfer cryptocurrency, securities, or other digital assets.

However, technical execution and legal formation are distinct questions. A blockchain transaction may have occurred even though a party disputes the existence, validity, interpretation, or enforceability of the underlying agreement.

E. Agency and authority

A business that deploys an automated system may be legally responsible for contracts formed through that system, depending on the applicable rules of agency and attribution.

Relevant questions include whether the system was authorized to conclude transactions, whether its use exceeded that authority, and whether the counterparty knew or should have known about any relevant limitation.

3. Essential legal elements of algorithmic contract formation

1. Offer

The system must communicate a sufficiently definite proposal or other legally recognized manifestation of willingness to contract. A mere invitation to negotiate or display of goods may not be an offer.

2. Acceptance

The response must satisfy the applicable acceptance rules. An automated confirmation may establish acceptance, but its meaning depends on the wording and structure of the transaction.

3. Authority and attribution

The court must determine whether the system's actions can legally be attributed to the person or business alleged to have entered the contract.

4. Certainty and intention

The essential terms must be sufficiently certain, and the parties must satisfy the applicable requirements for an intention to create legal relations.

5. Electronic evidence

Logs, timestamps, API messages, order confirmations, source code, and system configurations may help establish what was communicated, when acceptance occurred, and whether the transaction was authorized.

4. Leading case laws on algorithmic contract formation disputes

The following cases provide important principles concerning electronic acceptance, automated transactions, pricing errors, and algorithmic trading. Some directly concern automated systems; others establish foundational rules applicable to algorithmic contracting.

Case 1: Thornton v Shoe Lane Parking Ltd (1971)

Citation: [1971] 2 QB 163, Court of Appeal, England and Wales.

Facts: Thornton drove into an automated car park and received a ticket from a machine. The car park operator sought to rely on exclusionary terms displayed at the premises and associated with the ticket. An accident subsequently occurred, raising questions about the terms governing the contract.

Legal issue: When was the contract formed through an automated machine, and could additional terms introduced after formation become part of the agreement?

Decision: The Court of Appeal held that the contract was formed when the customer inserted money into the machine and the machine issued the ticket. The operator could not incorporate a particularly onerous exclusion clause that had not been adequately communicated before the contract was formed.

Legal principle: A contract can be formed through an automated machine. Contract formation occurs at the legally relevant point in the transaction, and terms introduced afterward may not become binding.

Relevance: This case is important for automated checkout systems, digital kiosks, self-service platforms, and software that completes transactions once a user performs a specified action.

Case 2: Entores Ltd v Miles Far East Corporation (1955)

Citation: [1955] 2 QB 327, Court of Appeal, England and Wales.

Facts: The parties negotiated a contract through telex communications between London and Amsterdam. A dispute arose concerning where acceptance occurred and which court had jurisdiction.

Legal issue: Where is a contract formed when acceptance is communicated through an instantaneous electronic communication system?

Decision: The Court of Appeal held that acceptance communicated by telex generally becomes effective when received by the offeror, rather than when dispatched by the offeree.

Legal principle: For instantaneous communications, receipt is ordinarily central to determining when acceptance becomes effective. The precise rule may depend on the communication method and circumstances.

Relevance: The reasoning is applicable by analogy to electronic order confirmations, API-based transactions, and systems in which software automatically transmits acceptance messages. It helps determine whether a contract existed at the time of a disputed automated transaction.

Case 3: Brinkibon Ltd v Stahag Stahl und Stahlwarenhandelsgesellschaft mbH (1983)

Citation: [1983] 2 AC 34, House of Lords, United Kingdom.

Facts: A contract was negotiated and accepted through telex communications between parties in different countries. The parties disputed where the contract had been made, which affected the applicable jurisdiction.

Legal issue: Whether the rules governing instantaneous communications could be applied mechanically to every electronic transaction.

Decision: The House of Lords emphasized that the place and time of formation must be determined by examining the circumstances, the parties' intentions, and sound business practice.

Legal principle: There is no universal rule that resolves every electronic communication dispute. The communication system, the parties' arrangements, and the transaction's circumstances may determine when and where acceptance becomes effective.

Relevance: This decision is useful for cross-border algorithmic contracts, automated trading systems, and distributed platforms in which offers and acceptance messages may pass through multiple servers and jurisdictions.

Case 4: Butler Machine Tool Co Ltd v Ex-Cell-O Corporation (England) Ltd (1979)

Citation: [1979] 1 WLR 401, Court of Appeal, England and Wales.

Facts: A seller quoted a price for machinery under terms that included a price-variation clause. The buyer responded with an order on different terms, and the parties exchanged documents containing conflicting contractual conditions.

Legal issue: Which terms governed the agreement when the parties exchanged inconsistent offers, acceptances, and standard-form documents?

Decision: The Court of Appeal held that the contract was governed by the buyer's terms, which the seller had accepted through the subsequent exchange.

Legal principle: Contract formation depends on the objective meaning of the parties' communications and conduct. Where terms conflict, the court must determine which proposal was accepted and whether the parties reached agreement.

Relevance: Algorithmic procurement platforms and automated business-to-business ordering systems often exchange standard terms without human review. This case illustrates why system design must clearly establish which terms govern a transaction.

Case 5: Chwee Kin Keong v Digilandmall.com Pte Ltd (2005)

Citation: [2005] SGHC 153; [2005] 1 SLR(R) 502, Singapore High Court.

Facts: An online retailer mistakenly listed Hewlett-Packard laser printers at an extraordinarily low price because of a pricing error. Several purchasers placed large orders through the website. The retailer attempted to cancel the transactions after discovering the mistake.

Legal issue: Whether online orders created binding contracts despite the seller's pricing error and whether the purchasers could rely on the apparent offers when they knew or suspected that the prices were erroneous.

Decision: The Singapore High Court examined electronic offer and acceptance, unilateral mistake, and the purchasers' knowledge of the error. It concluded that the purchasers could not enforce the transactions in the circumstances because the relevant mistake was sufficiently apparent and the purchasers knew of it or had reason to recognize it.

Legal principle: Electronic transactions remain subject to ordinary principles of contract formation and mistake. Automated acceptance does not necessarily make a transaction enforceable when the other party knows that a fundamental error has occurred.

Relevance: This is one of the most useful authorities for algorithmic pricing disputes, automated online orders, erroneous product listings, and mass transactions generated by software. It demonstrates that the legal consequences of a system error depend on both the transaction and the parties' knowledge.

Case 6: Quoine Pte Ltd v B2C2 Ltd (2020)

Citation: [2020] SGCA(I) 02, Singapore Court of Appeal.

Facts: B2C2 operated an algorithmic cryptocurrency trading system on Quoine's digital asset exchange. A software-related problem affected the exchange's pricing and liquidity mechanisms, resulting in trades at prices significantly different from prevailing market prices. Quoine subsequently reversed the trades, leading to a dispute over contractual rights and mistake.

Legal issue: Whether the trades were binding and whether they could be reversed on the basis of unilateral mistake when the transactions were generated by automated algorithms.

Decision: The Singapore Court of Appeal dismissed Quoine's appeal and upheld the result in favour of B2C2. The court considered the contractual arrangements governing the exchange and the applicable principles of unilateral mistake in the context of algorithmic trading.

Legal principle: Where a transaction is concluded automatically, the relevant state of knowledge and intention must be assessed within the legal framework applicable to the parties and their systems. Courts must distinguish the algorithm's operation from the legal consequences of the parties' contractual arrangements.

Relevance: This is a leading case for algorithmic contract disputes involving cryptocurrency exchanges, automated trading, software malfunction, pricing anomalies, and attempts to reverse completed transactions. It illustrates that a trade executed by software cannot necessarily be undone merely because one party later considers its result commercially undesirable.

Case 7: South West Terminal Ltd v Achter Land & Cattle Ltd (2023)

Citation: 2023 SKKB 116, Court of King's Bench for Saskatchewan, Canada.

Facts: A grain buyer sent a text message containing a purchase contract to a farmer. The farmer responded with a thumbs-up emoji. When the farmer failed to deliver the grain, the buyer alleged breach of contract, while the farmer disputed the significance of the emoji.

Legal issue: Whether the emoji, viewed in the context of the parties' previous dealings and communications, constituted acceptance of the contractual offer.

Decision: The court held that the thumbs-up emoji constituted acceptance in the circumstances and found that a binding contract had been formed.

Legal principle: Contractual acceptance is assessed objectively in context. Electronic communications need not use traditional formal language if the parties' conduct and communications demonstrate acceptance under the applicable law.

Relevance: This decision is relevant to contracts formed through messaging applications, automated communication platforms, and AI-assisted negotiation systems. It demonstrates that electronic acceptance can take nontraditional forms, although the case did not itself concern an AI system or a trading algorithm.

5. Legal framework in India

Algorithmic contract formation disputes in India are generally assessed under the established principles of contract law, electronic transactions, evidence, and agency.

A. Indian Contract Act, 1872

The Indian Contract Act provides the primary statutory framework for determining whether a legally enforceable agreement has been formed.

Relevant provisions include:

Section 2: Defines key concepts such as proposal, promise, and agreement.

Sections 3–4: Address communication of proposals, acceptances, and revocations.

Section 7: Requires acceptance to be absolute and unqualified.

Section 10: Sets out the essential requirements for agreements to become contracts.

Sections 13–22: Address consent, free consent, and matters including mistake.

Section 73: Provides for compensation for loss or damage caused by breach of contract.

The provisions must be applied to the actual facts. An automated response may constitute acceptance, but only if the communication and conduct satisfy the applicable legal requirements.

B. Information Technology Act, 2000

The Information Technology Act is particularly relevant to electronic contract formation.

Section 10A provides that contracts formed through electronic means are not unenforceable merely because electronic records or electronic authentication were used in their formation.

The Act's provisions concerning attribution, acknowledgment, and the time and place of dispatch and receipt of electronic records may also be relevant, depending on the circumstances.

This framework supports electronic contracting without eliminating the need to establish the underlying contractual requirements.

C. Agency and automated systems

Where a company deploys an algorithm to accept orders or negotiate prices, the court may need to determine whether the system's conduct is attributable to the company.

Relevant considerations include:

The scope of the system's authorized functions.

The terms communicated to customers or counterparties.

The company's representations about automated transactions.

Whether the other party knew of a limitation or malfunction.

Whether the system's operation was consistent with the parties' established course of dealing.

An algorithm does not independently become a contracting legal person merely because it generates communications or executes transactions.

D. Electronic evidence

The Bharatiya Sakshya Adhiniyam, 2023, is relevant to proving the communications and system events that allegedly created a contract.

Evidence may include order logs, server timestamps, API messages, emails, chatbot transcripts, source-code records, system settings, and electronic payment confirmations. Their admissibility and evidentiary value depend on the applicable statutory requirements and the circumstances in which the records were created and maintained.

6. Common causes of algorithmic contract disputes

7. Remedies available in algorithmic contract formation disputes

The appropriate remedy depends on whether a contract was formed, whether it was valid, and whether a party breached an enforceable obligation.

Damages for breach of contract: Compensation may be available where a binding contract existed and a party failed to perform its obligations.

Rescission or avoidance: A contract may be set aside where the applicable legal requirements for mistake, misrepresentation, fraud, or another recognized ground are satisfied.

Restitution: A party may seek recovery of money or property transferred without a sufficient legal basis.

Specific performance: A court may order performance of contractual obligations where the applicable law permits that remedy and damages are inadequate.

Declaratory relief: A court may determine whether a contract was formed, which terms apply, or whether an attempted cancellation was lawful.

Injunctions: In appropriate cases, a court may restrain further transfers or preserve assets pending resolution of the dispute.

A software malfunction does not automatically entitle a party to cancel a transaction. The claimant must establish the relevant legal basis for the remedy sought.

8. Preventive measures for businesses using algorithms

Businesses can reduce contractual uncertainty through sound system design and clear contractual documentation.

Define when an offer becomes binding and when acceptance takes effect.

Specify whether an order confirmation acknowledges receipt or constitutes final acceptance.

Establish clear rules for obvious pricing errors and erroneous automated transactions.

Record the version of the applicable terms accepted by each party.

Maintain reliable transaction logs and synchronized timestamps.

Set authorization limits for AI agents and trading algorithms.

Establish procedures for software failures, duplicate orders, and disputed transactions.

Provide clear escalation and correction mechanisms without assuming that every completed transaction can be unilaterally reversed.

9. Conclusion

Algorithmic contract formation disputes demonstrate how traditional contract law applies to transactions carried out through automated technology. The cases discussed establish that automated transactions can create binding agreements, that electronic acceptance must be assessed objectively, and that software errors do not automatically invalidate completed contracts.

The most important authorities include Thornton v Shoe Lane Parking Ltd, Entores Ltd v Miles Far East Corporation, Chwee Kin Keong v Digilandmall.com Pte Ltd, and Quoine Pte Ltd v B2C2 Ltd. Together, they illustrate the significance of the timing of acceptance, the communication of contractual terms, the parties' knowledge of errors, and the rules governing automated trading.

For Indian disputes, the Indian Contract Act, 1872, and the Information Technology Act, 2000, provide the principal starting points. Ultimately, the court must determine whether the parties objectively formed an agreement, whether the algorithm's conduct can be attributed to the relevant party, and whether the alleged error provides a recognized legal ground for avoiding the contract or obtaining compensation.