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

Passkey in the Digital Signing Journey

Passkey supports authentication and transaction authorization; the confirmed signing infrastructure creates the digital signature.

Talk to an ArchitectDeveloper Center
ON THIS PAGE

Passkey in the Trusted SIC journey

Passkey confirms the user in the observed action. In the API, credential, digest, authorization, SAD and hash signing are distinct steps. The Alpha recording is not evidence of production deployment configuration.

Trusted SIC documentationAnnotated demonstrations

Responsibilities from digest to signed document

Integration responsibilities
RoleAction
Source applicationPrepare the exact version, calculate digests under configuration and retain record correlation.
Integration applicationCall authorize, retain token/SAD server-side and do not change digests after authorization.
SignerReview the request and confirm using the configured route.
Trusted SICProcess authorization and create signatures under the credential/contract.
Document assembly applicationEmbed signatures into the correct format, validate, reconcile and retain evidence.

Authorize → authorizeCheck → signHash → signPolling are distinct operations. Confirm token, SAD, signatures and responseID presence under the contract before deployment.

KEY DISTINCTION

Passkey is NOT the digital signature.

Reference architecture
  1. 01
    Intent and document

    Transaction summary → challenge

  2. 02
    Passkey

    User verification → authorization evidence

  3. 03
    Trusted SIC → CA / RSSP

    Handoff → signing credential → digital signature

  4. 04
    Verification

    Output → evidence and reconciliation

TRUSTED SIC

Passkey-enabled signing interaction profile

AUTHENTICATION

Passkey

Passwordless user verification where implemented.

AUTHORIZATION

Transaction Intent

Bind user approval to the signing transaction context.

SIGNATURE

CA/RSSP

Digital signature creation remains in applicable signing infrastructure.

Detailed Trusted SIC claims such as standards profiles, certifications or provider matrices are published only when confirmed by source evidence.

TRUSTED SIC CEREMONY

Passkey authenticates/authorizes; signing infrastructure creates the digital signature

Mobile-ID publicly lists Trusted Hub FIDO2 Server and FIDO2 Authenticator SDK certifications at module scope. Mobile-ID Sign uses that evidence for authentication/authorization capability without turning Passkey into a signature primitive or extending certification to all of Sign.

REFERENCE

Passkey authorization and digital signature creation

  1. 01
    Business application

    Finalize signing intent, document and transaction summary.

  2. 02
    User

    Review the content, parties and expected result before confirmation.

  3. 03
    Passkey / authenticator

    Perform the challenge and user verification under the deployment policy.

  4. 04
    Trusted SIC

    Bind authorization evidence to the transaction and document, then hand off within the permitted scope.

  5. 05
    CA / RSSP

    Create the signature using the signing credential; Passkey does not replace the provider signing key.

  6. 06
    Verification and evidence

    Validate the signed document and retain outcome and authorization evidence for 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

Two credentials, two responsibilities

Passkey

Authentication, user verification or authorization. Evidence must be bound to transaction intent.

Signing credential

The key and certificate create the signature in the applicable signing infrastructure. Location, algorithms and configuration require provider confirmation.

Passkey ≠ digital signing key

RELATED

Related content

Choose the next document for your task.

GoPaperless Digital SigningConnect business applications with approved signing routes through mobile, Agent and API; follow outcomes and transaction evidence.Product ExperienceExplore illustrative experiences for users, buyers and integrators, with a next action for each state.Industry SolutionsMap signing journeys, trust boundaries, evidence and integration patterns to industries with demanding legal and operational requirements.Developer CenterFrom document input to transactions, state and verification: Choose guidance for your integration task.
NEXT STEPDiscuss deployment requirements

SIC document versions

AuthorizeCheck/signPolling examples from 1.7.260928 are not described in Compact 1.7.261001. Do not infer removal or inclusion in the newer contract.

SIC 1.7.260928SIC 1.7.261001

Search Mobile-ID Sign

Local search inside the offline package.