Skip to main content

Document Credentials

Organizations frequently receive scanned documents, photographs, PDFs, certificates, and records that must be interpreted before a trusted decision can be made. A document image may be useful evidence, but it is not automatically a verifiable credential.

UbID can transform verified information from a document or authoritative record into a governed digital credential when provenance, review, claim meaning, issuer responsibility, and lifecycle are clear.

Four distinct objects​

A safe solution distinguishes four objects that should not be treated as equivalent:

  1. Source document — the original physical or digital document presented for review.
  2. Extracted record — structured fields produced by OCR, barcode, machine-readable zones, digital signatures, or other parsing.
  3. Verification evidence — the checks, source references, review decisions, limitations, and policy applied.
  4. Verifiable credential — a new signed statement issued by an authorized institution.

Extraction does not prove authenticity. A readable field may still come from an altered, expired, unrelated, or unlawfully obtained document.

Appropriate use cases​

Document credentials may support:

  • educational certificates and degrees;
  • professional licences and training records;
  • permits and institutional authorizations;
  • identity attributes derived from approved documents;
  • employment or organizational evidence;
  • certified records and attestations;
  • portable summaries of an institutionally verified source.

The credential should represent the issuer's attestation, not merely copy every field from the source.

Example transformation flow​

  1. The holder submits or presents a source document through an approved channel.
  2. The system assesses capture quality and extracts relevant information.
  3. Verification checks evaluate signatures, codes, issuer information, dates, consistency, and recognized sources where available.
  4. Ambiguous or high-risk evidence is routed for authorized human review.
  5. Policy determines whether the evidence is sufficient for the intended credential.
  6. An authorized issuer creates a new credential containing approved claims.
  7. The credential is delivered to the holder and managed through its own lifecycle.

The source document and the credential may have different retention rules and different legal meanings.

Evidence quality and human review​

Automated checks can improve consistency, but they should communicate limitations. A governed result should distinguish:

  • successfully extracted information;
  • fields with low confidence or inconsistency;
  • evidence verified against a trusted source;
  • checks that were unavailable;
  • expired or incomplete material;
  • decisions made by an authorized reviewer;
  • the policy version used for issuance.

Human review remains important where evidence is ambiguous, high impact, or not supported by authoritative digital validation.

Privacy and document custody​

Source documents often contain more information than a credential requires. A document solution should:

  • extract and issue only purpose-relevant claims;
  • avoid embedding the complete document in every credential;
  • protect source files and derived records separately;
  • define retention and deletion for each data class;
  • restrict access to raw documents;
  • avoid placing personal data or predictable document hashes on a public blockchain;
  • support correction and challenge when extraction or interpretation is wrong.

What the credential proves​

A credential can prove that an identifiable issuer made a signed statement. Its trust also depends on:

  • the issuer's authority;
  • the quality and provenance of the source evidence;
  • the policy used to transform evidence into claims;
  • holder binding;
  • lifecycle status;
  • verifier acceptance policy.

A cryptographic signature does not turn an unreliable source into a truthful claim.

UbID product composition​

  • UbID Proof performs document and evidence assurance.
  • UbID Credential Cloud creates the governed credential.
  • UbID Wallet stores credentials and supporting documents under holder control.
  • UbID KeyVault protects institutional signing and encryption operations.
  • UbID Trust API supports controlled ingestion and issuance contracts.
  • UbID Pulse records service posture and evidence references.

Public documentation boundary​

Public documentation excludes document samples containing personal data, extraction rules, fraud indicators, confidence thresholds, customer schemas, institution registries, storage layout, key configuration, and operational endpoints.

See also UbID Proof, Cryptographic Protection, and Credential Lifecycle.