Evidence

Evidence Architecture

Connect source records, documents, signers, authorization, results and exceptions within a transaction record.

Browse records Security architecture

ON THIS PAGE

EVIDENCE PACKAGE

Every signature should be reconstructable in context.

DOCUMENT

Document

ID, version, hash, purpose.

SIGNER

Identity

Subject/profile and applicable identity context.

INTENT

Authorization

Consent/user action/transaction authorization.

SIGNATURE

Signature

Signature, credential and provider reference.

VALIDATION

Verification

Validation result, time and status.

AUDIT

Audit

Transaction ID, events and correlation.

REFERENCE MODEL

Production evidence fields may differ.

Map evidence fields to the approved API and audit schema for the deployment.

EVIDENCE ARCHITECTURE

An evidence package is a transaction record, not a certificate

Mobile-ID Sign describes the schema as Conceptual until a production schema is published. The goal is to show Business/Security/Operations what must be reconciled: Actor, document reference/hash, authentication/authorization events, signing route, certificate/status, validation and audit timeline.

If the table is wider than its frame, scroll horizontally to see all columns; use arrow keys when the table region has focus.

An evidence package is a transaction record, not a certificate
Evidence item	Purpose	Publication status
Transaction ID	Cross-system correlation	Conceptual
Document reference/hash	Bind transaction to content	Conceptual
Authentication / authorization event	Record user interaction	Conceptual
Signing route / provider	Execution context	Conceptual
Certificate / status	Trust context	Conceptual
Validation result	Integrity/status result	Conceptual
Audit timeline	Operational reconstruction	Conceptual

CONCEPTUAL EVIDENCE MODEL

Evidence is a transaction object, not a certificate logo

The structure below is conceptual until an approved production schema is published. It separates what happened, who/what authorized it, how the signature was produced and how the result was verified.

SigningTransaction ├── BusinessContext ├── DocumentEvidence │ ├── DocumentId / Version │ └── Hash ├── IdentityEvidence ├── AuthenticationEvidence ├── AuthorizationEvidence ├── SigningEvidence │ ├── Route / Provider │ ├── CertificateReference │ └── SignatureReference ├── TimeEvidence ├── VerificationEvidence ├── CallbackEvidence └── AuditEvents

CONCEPTUAL MODEL

EVIDENCE TIMELINE

Every major event should be attributable and traceable

Where the production service exposes evidence, each event should preserve actor, time, action, result and correlation to the signed object.

Reference architecture

SigningTransaction

Document and signer

Version • identity • authority

Actions and outcomes

Authorization • signature • validation • events

REFERENCE

Transaction evidence structure