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

ShareInfo & Controlled Attribute Sharing

Receive authorized attributes under purpose and consent; validate callbacks and data boundaries.

Explore platformDeveloper Center
ON THIS PAGE

From consent to a correlated sharing result

RSS 1.11.260911 §2.9–2.10 describes sharing initialization and retrieval. Sign-in, sharing consent and signing results are three separate objects.

Sharing correlation and result
Field/headerMeaning
x-rp-idCaller reference, retained to reconcile the application request.
x-billcode-idService tracking reference; do not rename it transaction_id.
data.transaction_codeSharing initialization reference; not shared attributes or a signature.
x-transaction-code / x-target-codeHeaders in the lookup table; source examples differ and must be confirmed before calls.
data.user_info_tokenJWS result token; verify origin and scope under the confirmed trust contract.
Read sharing initialization operation · Read retrieval operation
EVIDENCE REGISTER

Evidence & publication scope

PUBLICLY DOCUMENTED

ShareInfo

Mobile-ID public company timeline · 10/02/2026

Publicly documented within RAR/VNeID cooperation; the site does not expand it into full KYC.

REFERENCE

Consent boundary

Attribute sharing

Attribute sharing is described only within applicable consent/scope.

REFERENCE

Data minimization

Policy principle

Applications should request only the data needed for the transaction.

SHAREINFO

Attribute sharing is purpose- and consent-bound

Mobile-ID Sign does not equate ShareInfo with an entire KYC process. Only attributes requested within service scope and appropriate consent/authorization belong to the transaction; specific fields are not invented without a contract.

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.