Verification
Signature Verification
Validate signature, certificate, chain, status and timestamp where applicable.
ON THIS PAGE
VALIDATION FLOW
Verification does not stop at “Signed”.
ISMSOrganizational governance and certificate scope
VNeID / OpenIDIdentity and federated authentication
FIDO2 / Trusted SICAuthentication and authorization • module scope
CA / RSSPCertificate and infrastructure-scoped signing
Verification and evidenceTransaction outcomes • not organizational certification
PUBLICATION DISCIPLINE
Only claim profiles actually implemented/tested.
Do not infer LTV/LTA or specific ETSI validation profiles unless the implementation is demonstrated.
OPERATIONAL NOTES
Implementation decisions · Signature Verification
Signing time, trusted timestamp and system event time are different concepts.
Results need machine-readable status and human-readable reason when supported by the production contract.
OPERATIONAL DETAIL
Verification depth
Verification should separate document integrity, signature integrity, certificate chain/status, time/timestamp and policy outcome. “Valid” is a result produced under a specific validation context, not a permanent property of a PDF.
OPERATIONAL DETAIL
Trust verification separates evidence layers
Certificate-chain/status checking, signed-object integrity, trusted time and transaction evidence answer different questions. A validator may confirm the cryptographic signature while the business system still needs to verify document version, signer authority, transaction state and the policy under which the result is accepted. Mobile-ID Sign keeps these layers visible instead of reducing trust to a green checkmark.