# CheckID: information verification through VNeID

Proposes a server API for consent checking or information matching under a legitimate purpose. The partner submits information for checking; Mobile-ID coordinates and returns outcomes with references rather than source personal data for correction.

## Problem

Distinguish no response, explicit refusal, mismatch and technical failure. An absent result is not a mismatch conclusion.

## Scope

- Consent checking and information matching are distinct modes.
- Manage purpose, references, outcomes and timestamps.
- The partner retains business acceptance decisions.

## Boundaries

Sign-in ≠ information sharing ≠ digital signing. The result does not replace complete eKYC, biometrics, due diligence or corporate representation checks.

## Prerequisites

- Agree mode, fields, purpose and connection permissions.
- Obtain the official API, matching rules and sandbox.

## Pilot

Test consent, refusal, expiry, missing data and uncertain outcomes. Reconcile using references and verify that responses do not disclose out-of-scope source data.

## Source document

https://docs.mobile-id.vn/Proposals/MobileID_CheckID_VNeID_Integration_Proposal_V3.pdf

V3; 28 pages; Vietnamese PDF.

Observed source version; confirm implementation scope.
- Service overview: 3
- Journey and consent: 6
- Results and states: 10
- Implementation and acceptance: 14
- Reference design appendices: 21
