Mobile-ID · Digital Trust
ISO/IEC 27001 · FIDO2 · OpenID — View scope
Mobile-ID SignGoPaperless Digital Signing
VIGet Started
INTEGRATION

RAR/C06 Integration

Distinguish SSO, ShareInfo and signing routes in services provided through RAR/C06, with explicit responsibilities.

Explore platformDeveloper Center
ON THIS PAGE
RAR/C06 · VNEID

Identity services and signing routes remain separate layers

Mobile-ID publicly documents cooperation with RAR Center for SSO/ShareInfo; The site does not infer ownership of VNeID or RS-HUB.

Enterprise AppBusiness context
→
GoPaperlessTransaction orchestration
→
RAR/C06External identity boundary
→
VNeID SSO / ShareInfoIdentity / attributes
→
Signing authorizationSeparate user intent
→
RS-HUB / ProviderApplicable signing route
→
EvidenceResult + audit
RAR/C06 · VNEID

Separate public evidence from project architecture

Mobile-ID publicly states that it signed a contract with the RAR Center on 10/02/2026 for VNeID SSO/ShareInfo services. Mobile-ID Sign does not expand that statement into a claim that every RS-HUB or signing flow is already production.

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

Separate public evidence from project architecture
CapabilityEvidenceStatus
VNeID SSOMobile-ID publicly states a contract with RAR Center for VNeID SSO/ShareInfo dated 10/02/2026Publicly documented
ShareInfoSame public statement covers ShareInfoPublicly documented
RS-HUB signing routeIncluded as project/reference architecture in Sign; no reviewed public source here proves the exact production contractReference
SEQUENCE

Business transaction and exception paths

SSO, ShareInfo and signing are separate transactions. The exception model covers cancellation, denial, timeout, unavailable attributes, provider failure and reconciliation.

Reference architecture
  1. 01
    Business application

    Request and correlation reference

  2. 02
    Mobile-ID

    Orchestrate → redirect → track

  3. 03
    RAR/C06 / VNeID / RS-HUB

    Contract-scoped services; user authentication and consent where applicable

  4. 04
    CA / RSSP

    Separate signing authorization → signature → verification

REFERENCE

Sequence linking identity, attributes and signing

  1. 01
    Enterprise application

    Persist the business reference and request state; prepare the approved redirect.

  2. 02
    Mobile-ID

    Orchestrate the request and maintain separate correlation for authentication, attribute sharing and signing.

  3. 03
    RAR/C06 / VNeID

    Authenticate through the applicable service; the user grants or denies consent.

  4. 04
    ShareInfo / callback

    Receive authorized attributes and validate the state against the initiated request.

  5. 05
    User / RS-HUB

    Request separate signing authorization on the applicable route; login is not consent to sign.

  6. 06
    CA / RSSP

    Create the signature within provider scope and return it for validation and reconciliation.

REFERENCE

Exception lane and recovery responsibility

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

Exception lane and recovery responsibility
OutcomeApplication / operator action
Cancel or denyReturn the user outcome; do not initiate signing.
Timeout or expired challengeReconcile first; create a new request only with renewed user confirmation.
Callback state mismatchReject and investigate correlation, session and redirect binding.
Attribute unavailable or deniedApply business policy; never substitute inferred identity data.
Signing provider unavailablePreserve the uncertain state; reconcile or escalate without silently switching routes.
REFERENCE

Responsibility boundaries and evidence

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

Responsibility boundaries and evidence
ComponentResponsibilityEvidence to review
EnterpriseBusiness record, representative authority and acceptanceRecord reference, version and approval
Mobile-IDContract-scoped orchestration, correlation and handoffRequest, callback, state and audit
RAR/C06 / VNeIDApplicable identity / attribute serviceAuthentication result and consent scope
CA / RSSPSigning credential and signature creationCertificate, signed output and verification
RELATED

Related content

Choose the next document for your task.

Your first signing transactionWalk through a synthetic transaction and understand why request acceptance is not signing completion.Signing transaction modelLink the document, signer, purpose and route to the source business record.Webhooks and state reconciliationReceive events safely, handle duplicates and ordering, and reconcile against the transaction state source.Errors, retry and recoveryDistinguish input, access, conflict and provider failures before deciding whether to retry.
NEXT STEPDiscuss deployment requirements

Search Mobile-ID Sign

Local search inside the offline package.