How Are Smart Contracts Enforced Under Philippine Law?

Introduction

Smart contracts are automated digital agreements that execute instructions when predetermined conditions are met. They may operate on blockchain networks, use digital assets or tokens, and automatically perform actions such as releasing payment, transferring rights, recording ownership, or imposing access restrictions.

Under Philippine law, however, the use of blockchain technology does not by itself determine whether a smart contract is valid or enforceable. The principal questions remain whether the parties gave valid consent, whether the subject matter and cause are lawful, whether the agreement can be attributed to the parties, and whether the electronic record and signature can be authenticated.

The Electronic Commerce Act recognizes electronic data messages, electronic documents, electronic signatures, and electronic contracts. It does not remove the substantive requirements imposed by the Civil Code and other applicable commercial laws.

What Is a Smart Contract?

A smart contract is generally a combination of legal terms and computer code. The legal terms describe the parties’ rights and obligations, while the code automatically performs an agreed action when specified conditions are satisfied.

For example, a smart contract may provide that a digital payment will be released when an oracle confirms delivery of goods. It may also record the transaction on a blockchain, making the transaction history difficult to alter.

Philippine law does not treat every blockchain program as a contract. Code may be merely an automated tool, a recordkeeping mechanism, or an internal operating process. It becomes legally significant as a contract only when the circumstances show an agreement supported by the elements required by law.

Electronic Contracts Under Philippine Law

Section 16 of the Electronic Commerce Act provides that an offer, acceptance, and other elements required for the formation of contracts may be expressed, demonstrated, and proved through electronic data messages or electronic documents. A contract cannot be denied validity or enforceability solely because its terms or elements are contained in electronic form.

Accordingly, a smart contract may satisfy the form of an electronic contract if the blockchain record, code, interface, or related electronic communications sufficiently show the parties’ agreement. The use of automated execution does not dispense with the need to prove that the parties intended to be legally bound.

Section 17 further provides that, between the originator and addressee of an electronic data message or electronic document, a declaration of will or other statement cannot be denied legal effect solely because it is in electronic form.

These provisions support the use of blockchain-based agreements, but they do not automatically resolve disputes concerning identity, authority, mistake, fraud, unlawful terms, defective consent, or the meaning of computer code.

What Makes a Smart Contract Enforceable?

A smart contract should be drafted and implemented so that the ordinary requirements for a valid contract are clearly established. In general, the agreement should demonstrate the following:

• Consent: The parties must knowingly and voluntarily agree to the transaction and its terms.
• Object: The subject matter must be determinate or determinable and must not be contrary to law, morals, good customs, public order, or public policy.
• Cause: The legal consideration or purpose of the agreement must be lawful.
• Authority: The person or entity interacting with the blockchain must have authority to bind the contracting party.
• Proof: The agreement must be capable of being authenticated and presented in evidence.

A blockchain transaction may prove that a wallet or cryptographic key initiated an action. It may not, standing alone, conclusively prove who controlled the key, whether the person had authority, or whether the person understood the legal consequences of the transaction.

Electronic Signatures and Digital Authentication

Section 8 of the Electronic Commerce Act recognizes an electronic signature as equivalent to a handwritten signature when the required procedure identifies the person to be bound, indicates that person’s access to the electronic document for purposes of consent or approval, is reliable and appropriate for the transaction, is necessary for the party to proceed, and allows the other party to verify the signature before proceeding.

For smart contracts, the relevant signature may consist of a cryptographic signature generated through a private key. The parties should nevertheless document how the wallet address, private key, account, or digital certificate is linked to the identified person or entity.

A sound agreement should specify:

• the wallet addresses or digital accounts authorized for the transaction;
• the person or entity controlling each authorized account;
• the procedure for approving and signing transactions;
• the effect of lost, compromised, suspended, or replaced keys;
• the method for verifying the transaction and the identity of the signer; and
• the circumstances under which an electronic signature will be treated as unauthorized.

The Philippine National Public Key Infrastructure Certificate Policy recognizes that the use and issuance of certificates are governed by, among others, the Electronic Commerce Act, the Data Privacy Act, and the government certification framework. Where a transaction uses digital certificates or government-issued digital signatures, the applicable certification policy and security procedures should also be observed.

Electronic Records as Evidence

Section 12 of the Electronic Commerce Act provides that an electronic data message or electronic document cannot be denied admissibility solely because it is in electronic form or is not in standard written form. Its evidentiary weight depends on the reliability of how it was generated, stored, or communicated, how its originator was identified, and other relevant circumstances.

In MCC Industrial Sales Corporation v. Ssangyong Corporation, G.R. No. 170633, 17 October 2007, the Supreme Court explained that an electronic document may be admissible when it satisfies the applicable rules on evidence and authentication. A printout or output may serve as the functional equivalent of an original document when it is shown to accurately reflect the relevant data.

For a blockchain-based agreement, parties should preserve more than the transaction hash. Useful evidence may include the signed agreement, source code, deployed code, transaction hash, block number, timestamp, wallet ownership records, audit logs, interface records, oracle inputs, system specifications, and communications showing consent.

A blockchain’s apparent immutability may support the integrity of a record, but immutability does not establish that the original data was accurate, that the oracle supplied correct information, or that the transaction was authorized.

Drafting the Written Agreement Alongside the Code

The safest approach is to use a written legal agreement that identifies and governs the smart contract code. The written agreement should state whether the code, the written text, or both constitute the parties’ binding agreement.

The contract should expressly address the following matters:

• Priority of terms: State whether the written agreement prevails over the code in case of inconsistency.
• Code version: Identify the exact code, deployment address, version, and applicable audit report.
• Execution conditions: Define the events that cause automated performance and the evidence required to establish them.
• Oracles: Identify the data sources, verification procedures, replacement mechanism, and consequences of inaccurate or unavailable data.
• Errors and vulnerabilities: Provide procedures for pausing, correcting, or suspending the system where permitted by law and agreed by the parties.

The agreement should also include governing law, dispute resolution, venue, notices, liability allocation, force majeure, confidentiality, data protection, intellectual property, and the legal effect of blockchain records.

Automation Does Not Eliminate Legal Defenses

Automated performance does not prevent a party from raising defenses recognized under Philippine law. Depending on the facts, disputes may involve lack of consent, mistake, fraud, undue influence, incapacity, lack of authority, illegality, breach, unjust enrichment, or impossibility of performance.

A clause stating that “code is law” may be relevant to the parties’ allocation of risk, but it should not be assumed to exclude mandatory Philippine law. Contractual provisions remain subject to law, public policy, and the requirements for a valid and enforceable agreement.

Similarly, a programmed transfer of an asset does not necessarily establish valid ownership or lawful transfer if another statute imposes registration, notarization, licensing, delivery, or other formal requirements. The electronic form of the agreement cannot be used to bypass mandatory legal formalities.

Consumer and Data Protection Considerations

Smart contracts offered to consumers should use clear and accessible terms. Automated execution may create significant risks where users do not understand the code, the transaction cannot be reversed, or the system relies on complex technical conditions.

NPC Circular No. 2023-04 recognizes that consent in a contract of adhesion may be valid for personal-data processing only when the contract contains the information necessary to demonstrate transparency, the processing is necessary and for a legitimate purpose, the processing is not excessive in relation to the contractual obligations, and the processing is fair and lawful.

Accordingly, developers and businesses should not rely on a blanket acceptance of code or general terms to justify unrelated personal-data processing. Privacy notices, consent mechanisms, retention rules, access controls, and procedures for handling data-subject requests should be addressed separately and clearly.

Notarization and Formal Requirements

Electronic contracting does not automatically make an instrument equivalent to a notarized document. Where the law requires a public document, acknowledgment, jurat, notarization, or registration, the parties should comply with the applicable formal requirement.

The Supreme Court’s Rules on Electronic Notarization recognize electronic notarization procedures, including in-person and remote electronic notarization, subject to the conditions and safeguards in the Rules. A party should therefore determine whether the transaction requires an electronic notarial act and whether the chosen notary and procedure are authorized under those Rules.

Electronic execution may establish the parties’ agreement, but it does not by itself establish compliance with every formal requirement applicable to the underlying transaction.

Typical Smart Contract Scenarios

Automated payment. A buyer and seller may agree that payment will be released after an oracle confirms delivery. The contract should identify the delivery evidence, the oracle, the verification method, and the remedy if the oracle is wrong.

Digital asset transfer. The parties may use a smart contract to transfer a token or digital asset. The agreement should identify the asset, the person authorized to transfer it, the legal rights represented by the token, and any applicable regulatory or registration requirements.

Escrow arrangement. A blockchain escrow may hold digital assets until specified conditions occur. The parties should provide for disputed events, failed conditions, death or incapacity, compromised keys, court orders, and the release or return of assets.

Automated penalty or deduction. A smart contract may automatically deduct an amount upon an alleged breach. The parties should consider whether the deduction is a valid stipulated consequence, whether notice and an opportunity to contest are required, and whether the result could violate mandatory law or public policy.

Recommended Drafting Process

1. Identify the legal transaction before designing the code.
2. Confirm the identity, capacity, and authority of each party.
3. Prepare a written agreement stating the commercial terms in clear language.
4. Map each contractual obligation to the corresponding code function.
5. Define external data, oracles, timing conditions, and failure scenarios.
6. Establish the signature, wallet-control, authentication, and audit procedures.
7. Conduct code review, security testing, and an independent audit where appropriate.
8. Preserve evidence of consent, deployment, execution, communications, and system changes.
9. Check whether the transaction requires notarization, registration, licensing, or regulatory approval.
10. Provide a dispute process that remains available despite automated execution.

Conclusion

Smart contracts can be enforceable in the Philippines when they accurately express a valid agreement and can be reliably attributed, authenticated, and proved. The Electronic Commerce Act prevents electronic form from being used as the sole reason to deny validity, enforceability, or admissibility.

That recognition is not an automatic approval of every blockchain transaction. Enforceability still depends on consent, authority, lawful subject matter and cause, compliance with mandatory formalities, reliable authentication, and evidence showing what the parties agreed to do.

Businesses using smart contracts should therefore treat code as part of a broader legal transaction. The written agreement should explain the code, allocate risks, identify the parties and data sources, address failures and disputes, and preserve evidence capable of being understood by a court or regulator.

About Nicolas and De Vega Law Offices

 Nicolas and de Vega Law Offices is a full-service law firm in the Philippines.  You may visit us at the 16th Flr., Suite 1607 AIC Burgundy Empire Tower, ADB Ave., Ortigas Center, 1605 Pasig City, Metro Manila, Philippines.  You may also call us at +632 84706126, +632 84706130, +632 84016392 or e-mail us at [email protected]. Visit our website https://ndvlaw.com.