PUBLIC EVIDENCE
RAR Center contract · VNeID SSO/ShareInfo
VIETNAM AUTHORITATIVE IDENTITY
RAR/C06 · VNeID · SSO/ShareInfo — authoritative identity foundation
Mobile-ID publicly announced a contract with RAR Center on 10 Feb 2026 to implement electronic authentication through VNeID SSO/ShareInfo. describes authorised authentication/attribute sharing under service, consent and legal scope—not unrestricted population-database access.
SOURCEAuthoritative / document
CAPTUREDevice / SDK
VERIFYDocument + biometric
ASSUREPolicy + risk
DECIDEClaims / status
EVIDENCEAudit / trace
TRUST FABRIC
Authoritative source → CheckID
GoPaperless/Mobile-ID SSO provides an OpenID-oriented trust/authentication layer; CheckID adds document, biometric and assurance capabilities.
01CITIZENIdentity intent
02VNeIDeID channel
03RAR/C06Authoritative ecosystem
04SSO / ShareInfoAuthorised attributes
05GOPAPERLESS SSOIdentity layer
06CHECKIDDocument + biometric
07ASSURANCEPolicy / claims
08RPBank / government / enterprise
CLAIM BOUNDARY
What is published
Public contract/evidence supports the integration story; data access remains governed by purpose, consent, authority and service scope.
BOUNDARY
No unrestricted population-database claim.
TECHNICAL CONTENT
RAR/C06: authoritative identity context governed by purpose, consent and service scope
Source → Scope → Implementation → Evidence → Limitation
Role
RAR/C06 is described as an authoritative identity ecosystem/context, not as a database that CheckID can access without restriction. Query/sharing rights depend on authority, purpose, consent and licensed service scope.
Actor model
Public journeys distinguish the citizen/end-user, relying party, VNeID/eID/CCCD channel, the RAR/C06 ecosystem and the Mobile-ID/CheckID identity layer. CheckID is not presented as the authoritative source of record.
Attribute provenance
When an attribute comes from an authoritative source, result provenance distinguishes it from document-derived or user-declared data. The site does not publish an attribute catalogue if source/contract permission is absent.
Authorization and consent
SSO/authentication, user authorization/consent and ShareInfo/attribute sharing are different steps. does not use “SSO” as a synonym for permission to share identity data.
Failure
Source unavailable, consent denied, invalid token/session or out-of-scope service authorization are integration outcomes distinct from identity mismatch. They are not all labelled “verification failed”.
Audit boundary
Correlation between RP transaction, authorization context and CheckID process is described only with sourced identifiers. Public content does not reveal credentials, restricted endpoints or personal data.