Identity & compliance
KYC Identity Verification
Know who is signing — before they sign
Powered by Didit.me: government ID, facial biometrics, and liveness detection elevate WPsigner signatures to eIDAS Advanced (AdES) with a stronger audit trail.
ID + biometrics + liveness, enforced before signing
Three checks. One verified signer.
A drawn signature is easy to dispute. KYC ties the signature to a verified identity before WPsigner unlocks signing.
Government ID check
OCR and authenticity checks for passports, national IDs, and driver's licenses from 190+ countries.
Biometric face match
The signer's selfie is compared to the photo on the ID so the person signing is the person on the document.
Liveness detection
Anti-spoofing video checks help block photos, masks, and replay attacks before signing is allowed.
How it works in the signing flow
Verification is part of the signer experience — not a separate portal your team has to chase manually.
- 1
Enable Didit KYC
Connect Didit in WPsigner integrations and turn on identity verification for the documents or workflows that need AdES-level assurance.
- 2
Signer opens the document
Before the signature pad unlocks, WPsigner starts the Didit verification session in the signing flow.
- 3
ID + selfie + liveness
The signer captures a government ID, takes a selfie, and completes liveness — typically in under 90 seconds.
- 4
Sign only after approval
WPsigner blocks signing until Didit confirms identity. The outcome is written to the audit trail; raw biometrics stay with Didit.
Built for eIDAS Advanced (AdES)
Under eIDAS Article 26, Advanced Electronic Signatures need a stronger link between the signer and the signature. Didit KYC provides that identity assurance before the document is sealed.
- Default SES for everyday documents
- Optional AdES path when KYC is required
- Full audit trail with verification outcome recorded
Evidence chain
- Government ID authenticity + OCR data
- Face match between selfie and ID photo
- Liveness / anti-spoofing result
- Signature events, IP, timestamps, and document hash in WPsigner
Privacy by design
Stronger identity does not mean turning your WordPress site into a biometric vault.
- WPsigner stores the verification outcome and session metadata needed for the audit trail — not raw biometric templates.
- Document files and signatures remain on your self-hosted WordPress server.
- Didit processes the ID and biometric check as the identity provider; you control when KYC is required per workflow.
Where teams use KYC
High-value contracts
Loan agreements, real estate, and enterprise deals where identity disputes are expensive.
Regulated industries
Healthcare, finance, legal, and HR workflows that need stronger attribution than a drawn signature alone.
Remote onboarding
Verify clients you never meet in person before they sign NDAs, service agreements, or employment paperwork.
Cross-border signing
Support IDs from 190+ countries when your signers and counterparties are not in the same jurisdiction.
Frequently asked questions
What is KYC identity verification in WPsigner?
KYC (Know Your Customer) in WPsigner uses Didit.me to verify that the signer is a real person matching a government-issued ID before they can complete an electronic signature.
How does Didit KYC elevate signatures to eIDAS Advanced?
By default, WPsigner creates Simple Electronic Signatures (SES). When Didit KYC is enabled, the signer must pass government ID, facial biometrics, and liveness checks before signing. That stronger identity link supports eIDAS Advanced Electronic Signature (AdES) requirements under Article 26.
Does WPsigner store biometric data?
No. WPsigner stores the verification result and related audit evidence. Raw biometric data is handled by Didit during the check and is not kept as a biometric database inside WPsigner.
How long does verification take?
Most signers complete ID capture, selfie, and liveness in under 90 seconds on a phone or laptop camera.
Which documents and countries are supported?
Didit supports government IDs from 190+ countries, including passports, national identity cards, and driver's licenses, depending on the document type available in each country.
Can I require KYC only on some documents?
Yes. Enable Didit for the workflows that need higher assurance — for example high-value contracts — while leaving standard SES signing for everyday documents.
Add verified identity to your WordPress signatures
Enable Didit KYC when you need AdES-level assurance — keep everyday documents simple, and raise the bar for high-stakes agreements.
Stop paying per envelope
Choose an annual or lifetime license with unlimited documents and no per-envelope fees. Keep control of your data and signing workflows.