VNeID / RS-HUB
VNeID-linked signing journey with applicable CA/RSSP.
Explore →Abstract VNeID/RS-HUB and Passkey/Trusted SIC routes from business applications through a unified orchestration layer.
Regardless of route, the business application should receive normalized state, result and evidence.
Version • signer • authority
Applicable identity and signing service route
Desktop application handoff
Asynchronous transaction integration
Transaction-bound authorization
Signature creation with the applicable key and certificate
Output • state • correlation
Mobile-ID Sign keeps policy, credential, provider and channel separate so a business application does not hard-code every CA/RSSP or user journey.
If the table is wider than its frame, scroll horizontally to see all columns; use arrow keys when the table region has focus.
| Factor | Decision question |
|---|---|
| Channel | Mobile, desktop Agent or API? |
| Identity context | Which VNeID/session/profile context is permitted? |
| Authorization | How does the user approve the transaction content? |
| Credential | Which credential/certificate is eligible? |
| Provider | Which CA/RSSP is allowed by policy? |
| Fallback | May the route/provider change on failure? |
| Evidence | What result and audit context must return? |
Fallback is not allowed merely because another route is technically reachable when policy/assurance does not allow it.
Choose a topic to review implementation details.