Use the security inside the document
Verify signed chip data against configured issuer trust material and keep the available anti-cloning outcomes visible.
Digital Identity
Know the person. Trust the evidence.
A readable document photo is only part of the evidence. VeriqoCheck Digital Identity brings the document, its chip and its presenter into one journey. Read supported ePassport information, verify issuer-signed chip data, attempt the available anti-cloning checks and assess whether the live presenter matches its portrait.
More confidence for decisions that matter.
Connect a live person to a supported ePassport through document capture, NFC chip authentication, liveness and face comparison.
Connect evidence to the presenter
Liveness and face comparison answer a different question from chip integrity: whether a live presenter matches the document portrait.
Explain the decision
Give authorised reviewers individual check outcomes instead of asking them to rely on an unexplained overall score.
Add age eligibility to the same journey
Request age extraction when needed. The additional check uses birth-date evidence from authenticated chip data.
How Digital Identity works
Document, chip and presenter checks in one journey, with individual outcomes for your team.
-
01
Scan document
Capture the photo page of a supported ePassport and read its document information.
-
02
Read passport chip
A compatible phone reads the chip and performs the available authentication checks.
-
03
Capture live selfie
Live face capture assesses presence and agreement with the document portrait.
-
04
Receive results
Receive the individual outcomes and overall decision. Apply your organisation’s policy.
Confirm ePassport, device and capture support before rollout. These steps describe Digital Identity; other products use different capture flows.
Passive Authentication: trust the signed data
The backend checks the chip’s signed security object, the Document Signer certificate against configured country-signing trust material and the hashes of captured data groups. This establishes trust in the issuer-signed data used by the chip checks.
Active Authentication: a challenge to the chip
A short-lived, one-time backend challenge is sent to the chip. The backend verifies the raw response against the trusted public key in DG15. The result is recorded as its own check.
ICAO Chip Authentication: fresh protected communication
The app reads security information in DG14 and performs key agreement with the physical chip. It establishes fresh secure-messaging keys and confirms protected communication through a new chip read. The backend accepts the app-reported pass only after Passive Authentication succeeds.
Independent checks, not a fallback
Active Authentication and Chip Authentication are attempted and recorded independently when supported. One passing result does not conceal an explicit failure from the other. Unsupported protocols remain labelled unsupported; chip evidence does not replace liveness or face comparison.
Add a minimum age without another disconnected journey
Request age extraction alongside Digital Identity. Your service applies its threshold using the returned age and verification status.
Operational use cases
- ✓High-assurance remote onboarding
- ✓Regulated account opening
- ✓Cross-border applicant journeys
- ✓Step-up identity workflows
What the product returns
- ✓Document and issuer-signed chip evidence
- ✓Separate Active Authentication and Chip Authentication statuses
- ✓Liveness and face-comparison outcomes
- ✓Overall decision and optional extracted age
i
Product boundary
A passed chip check does not by itself confirm the presenter. Protocol support, issuer trust material and document generations must be confirmed. Unsupported or missing checks remain visible; verification does not guarantee regulatory compliance.
Questions your team may ask.
Africa first means starting with the markets, documents and devices your customers use. Coverage and capture readiness are confirmed for your deployment; no universal document support or guaranteed compliance is implied.
What does the applicant need?
A supported ePassport, a compatible NFC-capable phone, the supported application and connectivity. Confirm the document generation, issuer trust material and capture readiness before rollout.
Does a passed chip check verify the presenter?
No. It supplies document-and-chip evidence. Liveness and face comparison assess the presenter separately.
What happens if a required check is unavailable?
Its status remains visible. Your organisation should apply a supported recovery or review policy, not interpret unavailable evidence as success.
Does this guarantee regulatory compliance?
No. VeriqoCheck supplies evidence for your decision. Your market and activity determine additional checks, consent and review requirements.
Make trust part of the joining experience.
Share your priority countries, ePassport generations and required assurance level. Let’s shape a tested journey.
Get started with VeriqoCheck