Signer Identity Verification for High-Risk Agreements

Why identity verification determines enforceability

A signature proves intent, but only identity proofing proves who signed. In most jurisdictions, the evidentiary weight of an electronic signature depends primarily on the strength of signer identity verification. A signature backed by government-verified identity is far harder to repudiate than one backed by email access alone.

Identity verification methods compared

Different identity verification methods offer different levels of assurance. Match the method to the transaction risk.

	Assurance level	Best for
Email OTP	Low	Internal approvals, low-risk NDAs
SMS OTP	Low-Medium	Standard commercial agreements
Knowledge-based auth (KBA)	Medium	Financial services onboarding (US-focused)
eKYC (document + selfie)	Medium-High	Customer onboarding, employment contracts
National eID (Singpass, iAM Smart)	High	Government-linked transactions, QES
CA real-name verification	High	China reliable e-signatures, regulated filings

Matching verification to transaction risk

Use this risk matrix to determine the minimum identity verification level for different document types.

NDAs, internal approvals, policy acknowledgements. Email OTP or SMS OTP suffices. The signature proves intent; identity is assumed from the corporate email account.

Supplier agreements, service contracts, employment offers. Use eKYC (government ID document + selfie check) or SMS OTP with a verified phone number. Add audit trail with IP and timestamp.

Real estate, financial services, M&A, government filings. Require national eID (Singpass, iAM Smart) or CA-backed identity verification. Use QES where available.

When signers are in different countries, apply per-signer verification. A German counterparty uses eIDAS QES; a Vietnamese counterparty uses eKYC with VNeID. The evidence package satisfies the strictest jurisdiction.

Integrating national digital identity for signing

National eID systems provide the highest trust level for identity verification. Here is how major APAC eID systems integrate with signing workflows.

Singpass (Singapore)

Singpass verifies identity against NRIC data managed by GovTech Singapore. It supports OAuth-based login, MyInfo data retrieval, and digital service access. For QES, Singpass identity is combined with a CA-issued qualified certificate.

iAM Smart (Hong Kong)

iAM Smart verifies Hong Kong residents against HKID data. It provides identity proofing that can strengthen signing evidence. Available via government API for commercial applications.

VNeID (Vietnam)

Vietnam's national digital identity app, VNeID, provides identity verification at two levels. Level 1 covers basic identity; Level 2 adds biometric verification. Under Decree 337, electronic labour contracts require verified identity.

My Number Card (Japan)

Japan's My Number Card includes a digital signature certificate (JPKI). The Digital Agency is expanding integration pathways for private-sector digital services. My Number-based signatures qualify as electronic signatures under Japanese law.

Before signing

Classify document types by risk level
Map each signer jurisdiction to available identity methods
Configure eKYC provider (document + selfie) as fallback
Integrate national eID APIs where available
Set minimum verification level per document type
Test identity proofing flow with real users

After signing

Store identity verification result in evidence package
Include verification method, timestamp, and provider
Retain identity proof documents per regulatory requirements
Make evidence package exportable as sealed PDF
Enable re-verification if identity is challenged
Set retention period per jurisdiction rules

How eSign.AI handles identity verification

eSign.AI supports a layered identity verification approach with per-workflow configuration.

National eID as primary

eSign.AI integrates with Singpass, iAM Smart, CCCD, MyKad, and VNeID. When a national eID is available, it is the fastest and most reliable identity verification method — typically completing in under 10 seconds.

eKYC fallback

For signers without national eID, eSign.AI uses document-plus-selfie eKYC (via accredited providers). The signer photographs their ID document and takes a selfie with liveness detection. Processing takes 30-60 seconds.

Configurable per document type

Administrators set identity verification requirements per document template. An NDA requires only email OTP; an employment contract requires eID or eKYC; a real estate transfer requires QES with full identity proofing.

Frequently asked questions

Authentication confirms that the person accessing the system can use a specific email, phone, or device. Identity proofing confirms that the person is who they claim to be, typically by matching against government records or verified documents. For enforceable signatures, identity proofing is essential.

Team discussing the right eSignature approach for a business

Explore the right eSignature approach for your business

Talk to our team about eSignature requirements, compliance considerations, and document workflows across your target markets.

Keep reading

Solution Guides