1. Introduction

Programmable money smart contract payment failure claims in Singapore concern civil disputes arising when digital money, tokenised deposits, stablecoins, central bank digital currencies (CBDCs), or other blockchain-based payment instruments fail to execute their intended payment obligations.

A smart contract is a computer program deployed on a blockchain or other digital platform that automatically performs specified actions when predetermined conditions are satisfied.

For example, a commercial agreement may provide that:

A buyer transfers tokenised money into a smart contract.

The seller uploads evidence of delivery.

The smart contract verifies the delivery condition.

Payment is automatically released to the seller.

If the conditions are not fulfilled, the payment remains locked or is returned.

A payment failure may occur because of defective code, incorrect transaction inputs, oracle malfunction, blockchain congestion, unauthorised transactions, inadequate digital-wallet security, or a failure to satisfy contractual conditions.

Singapore's legal framework addresses these disputes through ordinary contract law, electronic transactions legislation, tort law, restitution, property principles, and applicable financial regulatory requirements.

Important legal distinction: Singapore does not have a comprehensive standalone body of legislation governing every smart contract payment failure. The established cases discussed below provide relevant principles by analogy. They should not be represented as judgments specifically deciding every type of programmable-money dispute.

2. Legal framework governing programmable money payments

A. Contractual enforceability

The principal contractual question is whether the parties intended to create legally binding obligations through their smart contract arrangement.

Relevant principles include:

Offer and acceptance.

Intention to create legal relations.

Consideration.

Certainty of contractual terms.

Capacity and authority.

Performance and breach.

Remedies for non-performance.

A smart contract's computer code may constitute the mechanism for performing an agreement, but the code does not necessarily contain the entire legal agreement.

For example, a written commercial agreement may provide that payment is conditional upon delivery, while the deployed smart contract mistakenly releases payment before delivery.

The court may need to determine whether the written agreement, the computer code, or both represent the parties' contractual obligations.

B. Electronic Transactions Act 2010

The Electronic Transactions Act 2010 (ETA) provides an important statutory foundation for electronic contracting.

Its relevance includes:

Legal recognition of electronic records.

Recognition of electronic signatures.

Formation and validity of electronic contracts.

Attribution of electronic communications.

Automated electronic transactions.

Evidential recognition of electronic records.

The ETA is particularly relevant where parties enter agreements through digital platforms without conventional handwritten signatures.

However, legal recognition of an automated transaction does not automatically establish that every automated payment is authorised, correctly executed, or legally irreversible.

C. Payment Services Act 2019

The Payment Services Act 2019 (PSA) regulates specified payment services and digital payment token activities.

Depending on the arrangement, relevant issues may include:

Digital payment token dealing.

Digital payment token exchange services.

Cross-border money transfers.

Domestic money transfers.

E-money issuance.

Safeguarding and regulatory compliance.

Not every programmable-money arrangement necessarily constitutes a regulated payment service. Classification depends on the instrument, activities performed, and applicable statutory definitions.

D. Civil liability and restitution

Where programmable payments fail, affected parties may pursue claims involving:

Breach of contract.

Negligent software development.

Misrepresentation.

Unjust enrichment.

Money had and received.

Conversion, where the relevant property requirements are satisfied.

Breach of fiduciary duty.

Breach of confidence.

Injunctive relief and proprietary remedies where legally available.

3. Major types of programmable-money payment failure claims

A. Smart contract execution failure

This occurs when the programmed payment does not execute despite the contractual conditions being fulfilled.

Examples include:

The buyer deposits the required digital currency, but payment is not released.

The seller fulfils delivery obligations, but the payment remains locked.

A smart contract incorrectly identifies a completed transaction as incomplete.

The payment instruction is executed twice.

A coding defect prevents the transfer of funds.

Legal consequences: The claimant may pursue breach of contract, damages, specific relief where appropriate, or restitution depending on the facts.

B. Oracle malfunction and incorrect payment instructions

Smart contracts frequently depend on external data sources known as oracles.

For example, a smart contract may release payment after an oracle confirms that goods have arrived at a specified location.

If the oracle provides incorrect information, the smart contract may:

Release payment prematurely.

Refuse to release an amount that is legally due.

Transfer funds to an unintended recipient.

Calculate an incorrect payment amount.

The central legal question is which party assumed responsibility for the accuracy and reliability of the external data.

Potential defendants include the platform operator, oracle provider, software developer, or contracting party, depending on their respective duties.

C. Unauthorised programmable payments

An unauthorised payment may arise when:

A private key is stolen.

A wallet is compromised.

A malicious person changes payment instructions.

A third party exploits a software vulnerability.

An employee exceeds delegated payment authority.

The court must distinguish between a technically valid blockchain transaction and a legally authorised transaction.

A transaction recorded on a blockchain does not, by itself, establish the consent or authority of the person whose assets were transferred.

D. Double payment and duplicate execution

A smart contract may execute the same payment obligation more than once because of:

Incorrect retry mechanisms.

Duplicate transaction submissions.

Faulty application programming interfaces.

Inadequate transaction validation.

Improper reconciliation between blockchain and banking systems.

A claimant may seek recovery of the duplicate amount through contractual or restitutionary proceedings.

E. Frozen or trapped programmable money

Digital funds may become inaccessible because of:

Defective smart-contract code.

Lost or inaccessible private keys.

Incorrect multi-signature requirements.

Blockchain protocol changes.

Platform insolvency.

Regulatory restrictions.

The legal issue is whether the defendant has a contractual or proprietary obligation to restore access, release the funds, or compensate the claimant.

4. Important Singapore case laws

The following decisions provide judicial principles relevant to programmable money, automated transactions, cryptocurrency ownership, payment obligations, and digital-asset recovery.

Case 1. Quoine Pte Ltd v B2C2 Ltd [2020] SGCA(I) 2

Leading Singapore authority

Facts:

Quoine operated a cryptocurrency trading platform. B2C2 used automated trading software to conduct cryptocurrency transactions.

Because of an operational failure affecting the platform's market-data systems, the automated software executed trades at highly abnormal exchange rates.

Quoine subsequently cancelled the trades and reversed the relevant account transactions.

B2C2 commenced proceedings alleging breach of contract and breach of trust.

Legal issues:

Whether contracts generated by algorithms were legally binding.

Whether the transactions could be avoided because of unilateral mistake.

Whether the platform operator could reverse completed transactions.

Whether cryptocurrency credited to an account was held on trust.

Decision:

The Court of Appeal upheld the breach-of-contract claim. It concluded that Quoine was not contractually entitled to cancel the completed transactions under the relevant agreement.

However, it reversed the finding of breach of trust because the necessary intention to create an express trust had not been established.

Legal principles:

Contracts may be formed through automated algorithms.

The absence of direct human participation does not automatically invalidate a contract.

The programmer's knowledge may be relevant when determining unilateral mistake in deterministic algorithmic transactions.

Platform operators must comply with contractual provisions governing transaction reversals.

Cryptocurrency balances and trust ownership are separate legal questions.

Application to programmable money:

This is the most directly relevant Singapore authority.

If a smart contract executes a payment incorrectly, a platform operator cannot necessarily reverse the transaction merely because it considers the result commercially abnormal.

The court must examine the contractual terms, the parties' knowledge, the circumstances of execution, and any applicable mistake doctrine.

Case 2. B2C2 Ltd v Quoine Pte Ltd [2019] SGHC(I) 3

Facts:

B2C2 challenged Quoine's cancellation of automatically executed cryptocurrency trades.

The dispute involved automated trading software, cryptocurrency balances, platform obligations, and the reversal of completed transactions.

Legal issues:

Whether completed automated transactions were contractually binding.

Whether Quoine had authority to reverse the transactions.

Whether cryptocurrency balances could be held on trust.

Whether the platform's conduct constituted breach of contract.

Decision:

The Singapore International Commercial Court found in favour of B2C2 on its breach-of-contract and breach-of-trust claims.

The Court of Appeal subsequently upheld the contractual result but reversed the trust finding in Quoine Pte Ltd v B2C2 Ltd [2020] SGCA(I) 2.

Legal principles:

Automated trading arrangements can create enforceable contracts.

Express contractual terms governing transaction finality are important.

The existence of cryptocurrency balances does not automatically resolve the question of beneficial ownership.

Application:

This decision is relevant when programmable-money users challenge the reversal of completed payments or the failure of an exchange to honour its contractual settlement obligations.

The appellate judgment must be followed when stating the final legal position.

Case 3. CLM v CLN [2022] SGHC 46

Facts:

The dispute involved cryptocurrency assets and an alleged misappropriation of digital assets.

The claimant sought proprietary protection and injunctive relief concerning cryptocurrency.

Legal issues:

Whether cryptocurrency could be recognised as property.

Whether digital assets could be protected through proprietary remedies.

Whether injunctions could be granted to prevent further dealings with disputed cryptocurrency.

Decision:

The Singapore High Court recognised that cryptocurrency could constitute property capable of being protected by proprietary injunctions.

Legal principles:

Digital assets may attract proprietary protection under Singapore law. Their intangible and blockchain-based nature does not necessarily prevent the court from granting appropriate remedies.

Application:

If a smart contract mistakenly transfers programmable money to another wallet, a claimant may seek urgent proprietary relief where the relevant legal requirements are satisfied.

However, the claimant must establish the relevant proprietary interest; technical control of a wallet is not automatically equivalent to beneficial ownership.

Case 4. Janesh s/o Rajkumar v Unknown Person [2022] SGHC 264

Facts:

The dispute concerned a Bored Ape Yacht Club non-fungible token (NFT) used as collateral in a cryptocurrency-related lending arrangement.

The claimant alleged that the NFT had been wrongfully taken or transferred following a dispute concerning the loan.

Legal issues:

Whether NFTs could constitute property.

Whether digital assets could be protected by injunctions.

Whether conventional proprietary remedies could operate in blockchain disputes.

Decision:

The High Court recognised that the NFT was capable of being treated as property and granted proprietary relief in the circumstances.

Legal principles:

Intangible digital assets may attract property-law protection.

Blockchain-based ownership interests can be relevant to proprietary injunction proceedings.

Courts can adapt conventional legal remedies to digital-asset disputes.

Application:

Where programmable money is represented by a token or transferred through an NFT-linked payment arrangement, this case may support an argument for proprietary protection.

It does not, however, establish that every tokenised payment automatically transfers ownership of the underlying real-world asset.

Case 5. ByBit Fintech Ltd v Ho Kai Xin [2023] SGHC 199

Facts:

The dispute involved cryptocurrency assets transferred in connection with an employment relationship.

The claimant alleged that the defendant had misappropriated cryptocurrency through unauthorised transfers.

Legal issues:

Whether cryptocurrency constituted property.

Whether cryptocurrency could be the subject of a trust.

Whether a constructive trust could arise in circumstances involving wrongful appropriation.

Decision:

The High Court recognised cryptocurrency as property and considered the availability of constructive trust remedies in relation to the disputed digital assets.

Legal principles:

Cryptocurrency can be recognised as property under Singapore law.

Digital assets may be capable of forming the subject matter of a trust.

Wrongful acquisition or retention of digital assets may give rise to proprietary remedies, depending on the circumstances.

Application:

Where an employee, intermediary, or payment administrator wrongfully redirects programmable money, a claimant may consider contractual, equitable, and proprietary claims.

This is especially relevant to disputes involving corporate wallets, automated treasury systems, and delegated payment authority.

Case 6. Cheong Jun Yoong v Three Arrows Capital Ltd [2024] SGHC 21

Facts:

The proceedings concerned digital assets and questions arising from the insolvency-related affairs of Three Arrows Capital.

The case involved issues concerning the legal treatment and location of digital assets.

Legal issues:

The legal situs of digital assets.

The significance of control over cryptocurrency.

The application of private international law to digital assets.

The relevance of digital-asset location in insolvency and recovery proceedings.

Legal principles:

The case is important for understanding how Singapore courts approach the location and legal treatment of digital assets in cross-border disputes.

Application:

A programmable-money payment failure may involve parties, wallets, developers, and blockchain infrastructure situated in different countries.

This case is relevant when determining jurisdiction, applicable law, and the legal location of digital assets for recovery proceedings.

Case 7. Rio Christofle v Tan Chun Chuen [2023] SGHC 66

Facts:

The claimant agreed to sell 12.14 Bitcoin to the defendant for S$320,000.

The claimant transferred the Bitcoin to the wallet address specified by the defendant, but the agreed payment was not made in full.

The claimant sought recovery of the outstanding amount or return of the cryptocurrency.

Legal issues:

Whether a cryptocurrency sale agreement was enforceable.

Whether failure to pay the agreed consideration constituted breach of contract.

Whether restitutionary recovery was available as an alternative.

Decision:

The High Court treated the dispute principally as a contractual claim, with unjust enrichment pleaded in the alternative.

Legal principles:

Cryptocurrency transactions may be governed by ordinary contractual principles.

A party's obligation to pay the agreed consideration is not eliminated merely because cryptocurrency has been transferred.

Restitution may be relevant where the contractual basis for retaining the transferred asset is absent or has failed.

Application:

This decision is relevant when a smart contract successfully transfers programmable money but the counterparty fails to provide the corresponding payment, goods, or services.

It illustrates the distinction between successful technical execution and fulfilment of the parties' wider contractual obligations.

Case 8. Fantom Foundation Ltd v Multichain Foundation Ltd [2024] SGHC 173

Facts and legal relevance:

This case concerned a dispute arising from the Multichain cross-chain bridge ecosystem and the control and recovery of digital assets.

It is relevant to the legal risks surrounding blockchain infrastructure, digital-asset control, and the consequences of failures involving cross-chain arrangements.

Application:

A programmable-money payment may involve several blockchain networks, bridges, custodians, and payment intermediaries. A failure at one stage may prevent the recipient from receiving the intended asset.

The case provides additional context for examining responsibility and remedies in complex digital-asset disputes.

Note: This is an infrastructure-related digital-asset authority, rather than a direct judgment on smart-contract payment failure.

5. Legal causes of action available to claimants

Singapore claimants may rely on several civil-law causes of action.

A. Breach of contract

A claimant must generally establish:

An enforceable contractual relationship.

The relevant contractual payment obligation.

Failure to perform that obligation.

Loss caused by the breach.

For example, a company agrees to pay a supplier S$100,000 through a programmable payment arrangement once delivery is confirmed.

The supplier completes delivery, but the smart contract fails to release the payment.

The supplier may bring a contractual claim for the unpaid amount and any recoverable consequential loss.

B. Negligence

Negligence may arise where a developer, platform operator, or service provider owes an applicable duty of care and breaches that duty.

Possible failures include:

Failure to conduct reasonable security testing.

Failure to identify known coding vulnerabilities.

Failure to maintain payment infrastructure.

Failure to implement reasonable transaction safeguards.

Failure to address foreseeable system risks.

The claimant must establish duty, breach, causation, and legally recoverable damage.

A developer is not automatically liable merely because software malfunctions. Contractual allocation of responsibility and the actual scope of the developer's undertaking are important.

C. Unjust enrichment

Unjust enrichment may arise where one party receives or retains a benefit at another party's expense without a sufficient legal basis.

For example:

A smart contract mistakenly transfers 50 digital tokens to an unintended recipient.

The recipient retains the tokens despite knowing that the payment was erroneous.

Depending on the circumstances, the sender may pursue restitutionary relief.

The court must examine the applicable unjust-enrichment requirements, including the relevant unjust factor and any available defences.

D. Proprietary recovery

Where a claimant has a legally recognised proprietary interest in transferred cryptocurrency or other digital assets, proprietary remedies may be available.

Relevant remedies include:

Proprietary injunctions.

Freezing injunctions.

Tracing.

Disclosure orders.

Constructive trusts where established.

Orders preventing dissipation of disputed assets.

CLM v CLN is particularly important in this area.

eLitigation+1

6. Allocation of liability among participants

Programmable-money payment failures may involve multiple participants.

Liability depends on the contractual structure and the particular duties owed by each participant.

Example: Oracle-related payment failure

A Singapore company enters into a digital supply agreement with a foreign supplier.

The smart contract provides for automatic payment once delivery is verified by an external oracle.

The oracle incorrectly reports successful delivery.

The smart contract transfers the payment even though the goods were never delivered.

Potential claims may include:

Breach of the supply agreement.

Restitution against the recipient.

Negligence against the oracle provider, if a duty exists.

Contractual claims against the platform operator.

Proprietary recovery proceedings where the transferred assets remain identifiable and the claimant establishes the necessary interest.

The court would examine whether the payment represented contractual performance, whether the transfer was authorised, and which party assumed the relevant risks.

7. Important legal defences

Defendants in programmable-money disputes may raise several defences.

1. Valid contractual execution

The defendant may argue that the smart contract performed precisely according to the agreed contractual terms.

2. Unilateral mistake

A party may argue that the transaction resulted from a legally operative mistake. The principles in Quoine v B2C2 are particularly relevant.

3. Lack of causation

A developer may argue that the loss resulted from incorrect instructions supplied by the claimant rather than defective programming.

4. Contributory negligence

Where a negligence claim is established, the defendant may argue that the claimant's own lack of reasonable care contributed to the damage.

5. Contractual exclusions and limitations

A platform may rely on limitation-of-liability provisions, subject to their incorporation, interpretation, and enforceability.

6. Third-party interference

A defendant may argue that a hacker, compromised wallet, or independent service provider caused the failure.

7. Restitutionary defences

A defendant may rely on applicable defences to unjust-enrichment claims, depending on the circumstances.

Importantly, blockchain immutability is not a complete legal defence. A transaction may be technically irreversible while still giving rise to an enforceable obligation to compensate or restore value.

8. Remedies available under Singapore civil law

A. Contractual damages

Damages may compensate the claimant for loss caused by non-performance.

They may include:

Unpaid contractual amounts.

Reasonably foreseeable financial losses.

Additional transaction costs.

Losses caused by delayed payment.

Other proven consequential losses, subject to ordinary contractual rules.

B. Specific performance

A court may grant specific performance where the legal requirements are satisfied.

This may be relevant where the payment obligation involves unique digital assets or circumstances in which monetary damages would be inadequate.

C. Restitution

Restitution may require the recipient to return an unjustified benefit.

D. Injunctions

A court may restrain a defendant from transferring, selling, or dissipating disputed digital assets.

E. Tracing and disclosure

Where assets have moved through several wallets or exchanges, claimants may seek appropriate tracing and disclosure remedies.

F. Equitable compensation

Where breach of trust or fiduciary duty is established, equitable remedies may be available.

9. Evidence required in programmable-money litigation

Digital-payment disputes require a combination of conventional contractual evidence and technical blockchain evidence.

Particular attention should be given to preserving blockchain records, system logs, timestamps, wallet addresses, and the precise version of the deployed smart contract.

10. Practical hypothetical disputes

Scenario 1: Automatic payment failure

Potential breach of contract

A Singapore buyer deposits tokenised money into a smart contract. Delivery is completed, but the smart contract does not release the funds.

Potential remedy: Contractual damages and appropriate relief concerning the locked assets.

Scenario 2: Duplicate payment

A payment gateway submits the same transaction twice because of a software retry defect.

Restitution and negligence issues

Potential remedy: Recovery of the duplicate payment and, where established, damages against a responsible service provider.

Scenario 3: Incorrect oracle information

An oracle mistakenly confirms that a commercial milestone has been achieved, triggering payment.

Potential remedy: Contractual and restitutionary claims, together with possible negligence claims.

Scenario 4: Unauthorised wallet transfer

An employee uses delegated wallet credentials to transfer company funds into a personal wallet.

Property and trust claims

Potential remedy: Recovery of digital assets, proprietary injunctions, tracing, and contractual or fiduciary claims where applicable.

11. Critical legal issues and future developments in Singapore

Several issues are likely to become increasingly significant as programmable money becomes more widely used.

A. Legal finality versus technical finality

A blockchain may record a transaction permanently, but the legal system must still determine whether the transfer was authorised and whether the underlying obligation was satisfied.

B. Tokenised deposits and stablecoin redemption

Disputes may arise where issuers or intermediaries fail to redeem digital tokens in accordance with contractual promises.

C. Cross-border smart contract disputes

A transaction may involve Singapore parties, overseas developers, international exchanges, and decentralised infrastructure.

Jurisdiction, applicable law, service of proceedings, and enforcement become important.

D. Smart contract audit responsibility

Courts may need to determine whether developers, auditors, and platform operators assumed responsibility for identifying particular vulnerabilities.

E. Insolvency and customer assets

If a payment platform becomes insolvent, questions may arise over whether customer digital assets are held on trust, are part of the platform's own assets, or give rise only to contractual claims.

The distinction highlighted in Quoine v B2C2 is especially important here.

F. Programmable central bank money

Future disputes involving central bank digital currency or tokenised deposits may require courts to distinguish between the legal status of the money, the payment instruction, and the technology used to execute the transaction.

12. Conclusion

Singapore's civil-law framework is capable of addressing many disputes arising from programmable-money smart contract payment failures through established doctrines of contract, negligence, restitution, trusts, property, and electronic transactions.

The most important judicial authority is Quoine Pte Ltd v B2C2 Ltd [2020] SGCA(I) 2 because it directly addresses automated algorithmic transactions, contractual enforceability, mistake, and attempted reversal of completed cryptocurrency trades.

The decisions in CLM v CLN, Janesh, and ByBit further demonstrate the developing recognition of proprietary interests in digital assets. Rio Christofle illustrates the continuing importance of ordinary contractual payment obligations in cryptocurrency transactions.

The central legal principle is that successful technical execution does not necessarily establish valid contractual performance, while technical failure does not automatically extinguish an underlying payment obligation. Liability must be determined by examining contractual intention, authorisation, the responsibilities assumed by each participant, causation, and the available civil remedies.

13. Summary of principal cases

Research qualification: These authorities do not all decide smart-contract payment failure claims directly. They establish relevant principles that may be applied to such claims. In particular, Cheong Jun Yoong should not be treated as a final determination of every underlying trust or asset-ownership issue, and the precise holding of each case must be considered in its procedural and factual context.