Skip to main content

E-signature is an evidence problem, not a UI problem.

What makes a digitally signed credit contract defensible: identity, signature level, timestamp, retention — and where the chain breaks in a lending workflow.

Updated 8 min readMarkdown
E-signature is an evidence problem, not a UI problem.

The decision this quarter is not which signing screen to buy. It is which file you would rather hand a judge in three years: a PDF with a picture of a signature and a database row, or a record that shows who signed, in what capacity, at what moment, and that nothing changed after. The interface is reversible. The evidence is not.

The law is more settled than the market thinks. What is unsettled is the plumbing: which document gets which signature level, who validates the certificate, what proves the timestamp, and who keeps the original. An architecture problem dressed as a legal one.

What changed

1 July 2024 — three tiers of legal value, not one. Law on E-Transactions 20/2023/QH15 (in force 1 July 2024) makes a data message admissible, refuses to deny an e-signature value for being electronic, and reserves equivalence with a handwritten signature for a digital signature or a certified specialised e-signature. OTP, PIN and click-wrap can be evidence; they do not clear that bar.

10 April 2025 — the certificate became a control point. Decree 23/2025/NĐ-CP (in force 10 April 2025) covers certificates, specialised signatures, certificate authorities and signing software. An officer's certificate must name the title and organisation, which makes signing authority checkable.

1 July 2025 — electronic notarisation opened. Decree 104/2025/NĐ-CP (in force 1 July 2025) allows it, and some localities already run it for mortgages with online security registration. Readiness varies by locality, notary office and registry.

3 July 2024 — a court showed how the file is read. Appellate judgment 79/2024/DS-PT (3 July 2024, a provincial people's court), a transaction of roughly VND 11.9 billion: username, password and OTP on a registered device were accepted as the customer's will unless the customer proved bank fault. That is the bar a digital signature has to beat.

15 August 2026 — online lending got new limits. Circular 29/2026/TT-NHNN (in force 15 August 2026) sets a small-value loan at VND 200 million at people's credit funds and VND 400 million elsewhere, and requires each institution to set its own exposure limit for electronic-channel lending. Earlier contracts continue unless amended.

1 January 2026 — the identity record became regulated data. Law 91/2025/QH15 (in force 1 January 2026) governs the eKYC and biometric evidence the signature rests on — two records, two retention rules.

The decision framework

The Article 22.3 test is worth memorising, because every demo assumes it: the signature confirms the signer, is uniquely linked to them, sits under their control, detects later change, and is backed by a certificate and a secure creation device.

The chain breaks in a predictable order: the framework agreement never mentions electronic execution, the signature level is chosen by what the screen allows, the timestamp is the application server's clock, the export is a PDF, the mortgage is on paper. Each gap survives alone; together they are the file you lose.

# Criterion Weight What "high" looks like
1 Identity proofing 20% eKYC per Circular 09/2020/TT-NHNN, biometrics where Decision 2345/QĐ-NHNN applies
2 Signature level against value 20% Digital signature above the band where OTP stops being credible
3 Integrity and timestamp 15% Trusted timestamp, integrity service re-verifiable years later
4 Retention and export 15% Original data, full context, exportable for litigation
5 Authority of the bank's signer 10% Certificate names title and organisation; delegation current
6 Collateral continuity 10% Mortgage on the same chain, or a documented bridge
7 Certificate lifecycle and exit 10% Validity checked at signing, revocation stored, escrow on exit

Criterion 3 is the quiet one: an application log proves what your system recorded, not that the document existed unchanged. Criterion 6 is where the money is — a signed contract attached to a paper mortgage is a file with two halves and no bridge.

Options and trade-offs

Option Strength Risk Three-year cost shape
Tier by value — eKYC and OTP below a band, digital signature above Fast, fits existing flows, cheapest to start The band is a policy line, not a safe harbour; a disputed large loan still fails Low capex, per-signature fees growing with volume
Sign the credit contract, keep collateral on paper Strong instrument, minimal process change Split file; disputes over integrity and priority; reconciliation forever Signing licences plus unchanged notary and registration cost
Whole digital file, electronic notarisation where available Cleanest chain; one record from offer to registration Availability varies by locality and asset type; a fallback is mandatory Highest integration cost, lower handling cost later

A consumer loan and a mortgage should not be the same project.

The numbers

Three figures are regulatory, not estimated. VND 200 million at people's credit funds and VND 400 million elsewhere define a small-value loan. VND 11.9 billion was the transaction in the 2024 judgment that showed how much turns on the log. VND 20–50 million is the Decree 330/2026/NĐ-CP fine for personal-data processing in AI systems; deepfake face authentication can be fined up to VND 50 million.

There is no effort baseline in the source material, so I will not manufacture one. Cost is per signature, per timestamp, per notarisation and per year of retention, so the expensive item is rarely the licence. It is the evidence you did not store, found in year three. The AI rules already require machine-readable marking for generated content — metadata or a digital signature: the same primitive an evidence chain needs.

What I would do in 30, 60 and 90 days

First 30 days — map the file, not the flow.

  • List the documents in one credit product: framework agreement, offer, contract, collateral, disbursement instruction. For each, record the signature level and who signed.
  • Read the framework agreement for the clause permitting electronic execution. If absent, nothing downstream is protected.
  • Check whether the certificate validates at signing time and whether revocation is stored. Most implementations validate at issuance and never again.

Days 31–60 — fix authority and retention.

  • Set value bands with Legal and Risk, with the reason for each band written down.
  • Confirm every bank-side certificate carries title and organisation, and that delegation is current. A signature outside an officer's authority is worse than none.
  • Define retention: original data, full context, re-verification path, and an export format that survives the vendor.

Days 61–90 — run one product, then attack it.

  • Take one product end to end, including the collateral path where you actually lend.
  • Then the dry run that matters: hand the file to someone who did not build the process, and ask them to prove intent and integrity without the system.
  • Fix what they could not prove. That list is the roadmap.

What I would not do

  • I would not treat "digitally signed" as "enforceable". The signature proves intent; notarisation and registration prove the collateral.
  • I would not let OTP stand as the signature on a large secured loan. It may evidence intent; it is not the equivalence threshold.
  • I would not keep screenshots as evidence, or hand a court a PDF with no verifiable original behind it.
  • I would not promise a fully digital file before checking notarisation availability where the collateral sits.

For the non-technical sponsor

A signed PDF is not proof. What proves a loan is a chain: a verified identity, a signature at the right level, a trusted timestamp, the original record kept in full, and a notarised or registered collateral document connected to it. The cheap failure is the signing screen. The expensive one is finding, in year three, that the record cannot be shown to be unchanged.

Sources

  • Law on Electronic Transactions 20/2023/QH15 — the legal basis for electronic signatures and electronic contracts in Vietnam.
  • Decree 23/2025/NĐ-CP and Decree 104/2025/NĐ-CP — guidance recorded in the working notes for this article.
  • Circular 29/2026/TT-NHNN — banking-sector requirements recorded in the same notes.

Instrument numbers follow the working notes; deep links were not part of the source material and are therefore not asserted here.


Personal views. Client and employer details are anonymised. Figures are third-party estimates, not vendor quotes, and are dated November 2026.

No comments yet. Be the first to comment.