MOBILE-ID SIGN · PRODUCT
Verification & Transaction Evidence
Link signed-document verification with transaction state and evidence records.
ON THIS PAGE
OPERATIONAL NOTES
Implementation decisions · Verification & Transaction Evidence
Results separate integrity, certificate/status, timestamp and policy decision when supported.
Do not collapse “valid” into an unexplained boolean; operations needs detail to investigate failures.
OPERATIONAL DETAIL
Verification outcome
A verification view should show the signed object/version, signer/certificate reference, integrity result, certificate/status result, trusted time where applicable and any policy limitation.
OPERATIONAL DETAIL
Verification must answer “valid under what context?”
A verification result is useful when it identifies the object/version checked, content integrity, signer/certificate reference, certificate status at validation time, trusted time/timestamp where applicable, and the policy/assumptions used. Mobile-ID Sign avoids presenting “VALID” as a permanent property of a document; the outcome is tied to a validation context and traceable evidence.
VALIDATION CONTEXT
A result is bound to its validation context
A verification result should be read together with its validation context: Which object/version was checked, when it was checked, which certificate/status source was used, and which evidence reference connects the result to the transaction. If a component cannot be checked or a status source is unavailable, the outcome should remain indeterminate rather than being promoted to valid.