Identity
VNeID/eID/profile context.
How it works
From Identity to Signing Evidence
A unified lifecycle across identity, authorization, signing, verification and evidence.
ON THIS PAGE
TRUST LIFECYCLE
Identity → Authorization → Signature → Verification → Evidence
Document and policyVersion • signer • authority
VNeID / RS-HUBApplicable identity and signing service route
GoPaperless AgentDesktop application handoff
REST APIAsynchronous transaction integration
Trusted SICTransaction-bound authorization
CA / RSSPSignature creation with the applicable key and certificate
Verification and evidenceOutput • state • correlation
BOUNDARIES
Do not collapse trust layers.
Authentication is not authorization. Authorization is not signature creation. Signature creation is not verification.
Authentication / Authorization
Passkey or user approval.
Signature Creation
CA/RSSP signing infrastructure.
Verification
Certificate/status/time.
Evidence
Audit and transaction context.
CONTROL POINTS
Identity, authorization, signature and evidence answer four different questions
Mobile-ID Sign makes explicit who the participant is, what the participant approved, which infrastructure created the signature, and what the system can retain to prove the transaction.
Who is participating?
Identity/session sources provide permitted context.
What is the user approving?
Transaction/document summary should bind to user intent.
What creates the signature?
CA/RSSP/QSCD/HSM depend on route and credential.
How can it be proven?
Hash, certificate/status, time, callbacks and audit correlate to the transaction.
Do not collapse states
SSO success, consent success and signing success are not the same state.