Digital Identity
Verify a supported ePassport using NFC chip authentication, liveness and face comparison. Receive separate results for the document, chip and presenter checks.
Verify documents,
faces and phone numbers
Check identity documents, compare facial images, verify age and confirm access to a phone number. Choose the checks your service needs and receive results through the VeriqoCheck API.
Verification products
Choose a product based on the information you need to collect and the checks you need to perform.
Identity Document
Capture a supported identity document, extract its details and compare the document portrait with a selfie. Add liveness when required.
Document Scan
Extract names, document numbers and other available details from a supported identity document to reduce manual entry.
Age Verification
Check age using a supported identity document and a live selfie. Receive the verified age and assessment date, then apply your service’s minimum-age requirement.
Face Detection
Detect faces in submitted images. Identify missing faces, group photographs and captures that need another attempt.
Similarity Detection
Compare faces within a submitted set of photographs. See which comparisons meet your criteria and which need review.
How we protect
verification evidence
VeriqoCheck limits access to identity evidence, stores it privately and manages how it is deleted.
Evidence controls
-
Limited access
Session credentials expire and apply to specific actions.
-
Private storage
Evidence is kept in private storage.
-
Auditable changes
Verification status changes can be traced.
-
Managed deletion
Access can be revoked and evidence removed through a managed process.
Confirm access to a phone number
Verify that your customer can access the number they provided.
Request a code
With your customer’s consent, submit their number. We send a six-digit code via WhatsApp.
Confirm the code
Submit the code your customer enters to confirm access at the time of the check.
Retrieve the result
Get the status, phone number, customer reference and confirmation time through the API.
Codes expire after 10 minutes. Phone verification can run on its own.
View phone verificationFrom request to result
The steps depend on the product and capture method.
Select the checks
Choose the checks and evidence your onboarding process needs.
Collect the information
Guide the applicant through the required steps, such as scanning a document, reading a passport chip or taking a selfie.
Use the results
Review the outcomes and apply your approval rules, request another capture or refer the case for review.
What each check tells you
Choose the checks that give your service the evidence it needs.
| Check | What the result tells you |
|---|---|
| Document scanning | Which details could be extracted from the submitted document. |
| NFC chip authentication | Whether data from a supported chip passed the configured issuer and chip checks. |
| Face comparison | How closely the submitted facial images match. |
| Liveness | Whether the capture provides evidence that a live person was present. |
| Age verification | The person’s verified age on the assessment date. Your service applies its minimum-age rule. |
| Phone verification | Whether the customer could access the code sent to the number they provided. |
Use chip authentication to assess supported document chip data. Use face comparison and liveness to assess the presenter.
Connect verification to your application
Create verification requests and retrieve results through the API. Link each check to your customer records using the returned identifiers.
Phone verification example
A successful code confirmation returns 204 No Content. Use the GET endpoint to retrieve the verification result.
Phone verification result
JSON excerptGET
/v1/verifications/phone-verifications/{id}{
"id": "00000000-0000-4000-8000-000000000001",
"phoneNumber": "+447700900123",
"requesterReference": "customer-123",
"status": "VERIFIED",
"verifiedAt": "2026-11-12T10:01:00Z"
}Frequently asked questions
Can I run individual checks?
Yes. Choose individual checks for document scanning, age, photos or phone access. Digital Identity combines supported ePassport, NFC chip and presenter checks.
Compare productsWhich African identity documents are supported?
Coverage must be confirmed for your countries, issuing authorities, document types and generations. Our focus on African markets does not mean every document is supported. Share your priority markets so we can confirm a supported rollout.
How is age eligibility checked?
Age Verification uses trusted document birth-date evidence, live presence and face matching. It does not use a facial age estimate. The dedicated result returns age in completed years, verification status and the assessment date. Your application applies its minimum age to a VERIFIED result; INCONCLUSIVE and INCOMPLETE results do not establish that someone is underage.
Is NFC required for every product?
No. NFC chip verification is part of the supported Digital Identity journey. Document Scan, Identity Document, standalone Age Verification, Face Detection, Similarity Detection and Phone Verification do not require an NFC chip read.
Are Active Authentication and Chip Authentication the same?
No. Active Authentication checks the chip’s response to a challenge. Chip Authentication establishes fresh protected communication with the chip. They have separate outcomes and depend on trusted, issuer-signed chip data. Liveness and face comparison assess the presenter separately.
Read about Digital IdentityDoes verification guarantee regulatory compliance?
VeriqoCheck supplies evidence for your organisation’s decision. Your market, activity and obligations determine the additional checks, consent, review and access rules required. Confirm coverage and capture readiness before launch.
Contact us
Tell us what you need to verify, where your customers are based and how you want to integrate VeriqoCheck.
Prefer email? service@veriqocheck.com
We’ll use your details to respond to your enquiry. Read our Privacy Policy.