CheckID
CustomersPartners
VIEN
Contact
Home/CheckID Platform/Verified Claims
PLATFORM · CHECKID

Verified Claims

Represent verified attributes with process, source and evidence metadata.

Talk to an expertDeveloper quick start
CAPABILITYInput → Processing → Output
CONTROLPolicy · risk · standard
EVIDENCEResult · trace · scope
VERIFIED IDENTITY RESULT

JWT · verified_claims · trust framework

The source API contains claim_sources/JWT and verified_claims. distinguishes source implementation from current OpenID standard alignment and certification status.

Source contractSections 3.4, 3.6 and Appendix A · final_result / claim_sources
Authoritative / verified source context
↓
Document + process evidence
↓
Verification / assurance context
↓
Signed verified identity result
JWT PAYLOAD — CONCEPTUAL REDACTIONSOURCE SHAPE 
{
  "iss": "https://id.mobile-id.vn",
  "sub": "<SUBJECT_ID>",
  "verified_claims": {
    "verification": {
      "trust_framework": "<TRUST_FRAMEWORK>"
    },
    "claims": {
      "name": "<VERIFIED_NAME>",
      "dob": "<VERIFIED_DOB>"
    }
  }
}
Certification boundaryUse of OpenID Identity Assurance concepts/profile in the source does not imply OpenID Identity Assurance certification.
TECHNICAL REFERENCE

Verified Claims: from CheckID result to assurance metadata

Source provenance → verification metadata → verified attributes → relying party

Standard model

OpenID Identity Assurance Schema Definition 1.0 incorporating errata set 1 (Final, July 2026) standardizes `verified_claims` for identity claims with verification metadata.

No invented field mapping

Public documentation does not map `subject_id`, `process_id` or a CheckID result to OpenID fields without an implementation mapping. A mapping needs object/field/source/status/limitation.

Provenance

A verified attribute needs appropriate source and verification context; a user-declared claim does not become verified simply because it is transported through OIDC.

Request/response

Actual request/response examples are published only from OP/API sources. Any conceptual example is explicitly labeled “illustrative — not CheckID API contract”.

Wallet landscape

OpenID4VCI 1.0 and OpenID4VP 1.0 are Final specifications from 2025, but remain REFERENCE/Requires applicability assessment unless CheckID implementation evidence exists.

Privacy

Relying parties should request attributes appropriate to purpose; assurance metadata does not remove data-minimization, consent/authorization or retention obligations.

Authoritative technical references