e-Verification
Transactional identity verification for onboarding, re-verification, recovery and step-up, with source-linked evidence.
CheckID helps banks, financial institutions and government organisations identify, verify, authenticate and assure identities through a SaaS/API service with traceable evidence, clear responsibility boundaries and transparent technical architecture.
WHAT YOU BUY → HOW IT WORKS → WHY YOU CAN TRUST AND OPERATE IT
Transactional identity verification for onboarding, re-verification, recovery and step-up, with source-linked evidence.
Electronic identification using identity/eID data within the transaction scope, distinct from biometric 1:N identification.
Build sufficient evidence, holder binding and assurance to establish identity for the intended purpose.
KYB, representatives, authority to act and evidence for business customers.
Sandbox → provisioning → integration → UAT → production → operate → change → exit.
Identity Trust + Evidence Trust + Technical Trust + Service Trust.
Feature islands and shows how source, eID, biometrics, assurance and integration connect.
Person · organisation · representative · ownership · eID sources.
CCCD · VNeID · ePassport · NFC · document integrity.
Face · fingerprint · iris · palm; 1:1 and 1:N are separate tasks.
KYC · KYB · representative verification · verified claims · risk/policy.
OAuth2 · REST · Kafka · OpenAPI · SDK · Sandbox · trusted devices.
The business journey combines entity data and representative KYC rather than treating KYB as a company-data lookup.
The public story highlights the verified integration relationship without claiming unrestricted population-database access.
Electronic identity channel in the RAR/C06 ecosystem.
Mobile-ID public evidence supports VNeID SSO/ShareInfo integration; access is authorised and scoped.
OpenID Connect trust/authentication layer; certification remains product/version/role specific.
Scientific metrics and standards are explained as references; Mobile-ID numeric performance is published only when evidenced.
Capture quality · template · 1:1/1:N · liveness/PAD.
Enrollment · matching · identification · deduplication.
Capture · segmentation · template · verification / identification.
Palmprint and vascular biometrics are separate modalities.
Offline mock, sandbox account request and production documentation are three explicit environments.
Versioned source-driven contract · request/response · code tabs · result codes.
Synchronous API and contract-bounded event-driven integration.
Capture hardware → middleware → SDK → CheckID process → evidence.
Each entry clearly describes which area CheckID participates in and the corresponding source of confirmation.
| Organization | Industry | Usage type | Role of CheckID | Verification source |
|---|---|---|---|---|
| TPBank | Banking | API / SDK | Integrates identity verification services into the system | Contract |
| PVComBank | Banking | API / SDK | Integrates identity verification services into the system | Contract |
| VNPT | Telecommunications | Device | Reads chip-based Citizen Identity Cards (CCCD) and uses the data for identity verification / eKYC | Contract |
| ABBank | Banking | Device | Reads Citizen Identity Cards (CCCD) at the counter | Contract |
| SHB | Banking | Device | Reads Citizen Identity Cards (CCCD) at the counter | Contract |
| FPT | Technology | Device | CCCD readers for integrated systems | Contract |
| HTCSW | Technology | Device | CCCD readers for integrated systems | Contract |
These are Mobile-ID products, not customers.
| Product | Integration type | Role of CheckID |
|---|---|---|
| GoPaperless Workflow Portal | Device / API | Reads CCCD and verifies the identity of the signer |
| GoPaperless SSO | API | Verifies identity during login |
| BioSence | API | Registers user information using CCCD via NFC |
Request the exact next step: solution brief, architecture session, sandbox, device evaluation or evidence pack.
Every layer is described by role, input/output and evidence rather than repeated generic boxes.
Provides identity attributes or authentication results within the authorised scope.
Mobile, NFC, camera, reader and SDK turn a live interaction into processable evidence.
Document trust, biometric 1:1/1:N and government verification create a technical result.
Policy, risk and trust framework determine how the technical result is used.
KYC/KYB/authentication decisions remain traceable through transaction/evidence references.