Package-level declarations
Types
Android framework boundary for official holder CREATE_CREDENTIAL request and response handling.
Verified Android Credential Manager create input after caller and protocol extraction.
Android CREATE_CREDENTIAL OpenID4VCI request after Credential Manager extraction.
Android CREATE_CREDENTIAL acknowledgement returned to Credential Manager after OpenID4VCI completes.
Android framework boundary for official holder Activity request and response handling.
Verified Android Credential Manager input after caller and selected-entry extraction.
Android Credential Manager metadata registry adapter.
One mdoc credential projected into Apple's IdentityDocumentServices registration model.
Outcome of reading the shared projection, with "absent" and "unreadable" kept apart.
Desired IdentityDocumentServices registration state of the one wallet that owns this App Group.
Runtime authorization state of Apple's IdentityDocumentServices provider registration.
App-to-extension desired-state bridge for Apple's IdentityDocumentServices registration store.
Android and iOS facade for the walt.id wallet SDK.
Parsed request shape Apple exposes before the user grants access to the raw Annex C request.
Consent preview for an ISO 18013-7 Annex C presentation.
Two-phase Annex C input. Android supplies raw fields immediately; Apple may defer them.
Raw post-consent Annex C data required to sign and encrypt a response.
Result returned after a mobile wallet has been initialized with signing material and a DID.
Client identifier scheme established while authenticating an OpenID4VP request.
Configuration for creating a MobileWallet.
Credential offer input for MobileWalletIssuanceRequest.
Outcome of synchronizing the platform registry with the current wallet credential metadata.
Platform adapter for metadata-only registration. Android framework types never cross this boundary.
One matcher-visible field. Values are individual decoded claims, never the raw credential payload.
Matcher-visible credential metadata supplied to a platform credential registry.
Cross-process wallet access required by native document-provider extensions.
Selects who owns the encrypted wallet database key.
Truthful platform capability snapshot, including runtime and registration availability.
Runtime support for one protocol/format/protection combination.
Credential formats exposed through the platform Digital Credentials integration.
Consent preview retained by the SDK until MobileWallet.submitDigitalCredentialPresentation.
Protocol identifiers understood by platform Digital Credentials APIs.
Verifier and transaction metadata extracted from an OpenID4VP request received through a Digital Credentials API.
Authentication applied to a Digital Credentials request.
OS-mediated response. dataJson is returned to the platform and is never direct-posted over HTTP.
Protection applied to the response returned to the requesting platform.
Observable mobile wallet session event.
High-level protocol flow that emitted a MobileWalletEvent.
Progress state represented by a MobileWalletEvent.
Android MobileWallet factory backed by Android KeyStore and an app-private SQLDelight database.
Platform factory that wires MobileWallet to Android or iOS storage and key infrastructure.
iOS MobileWallet factory backed by Keychain/Secure Enclave managed keys, the Crypto2 software-key fallback, and a native SQLDelight database.
App-facing input for starting an OpenID4VCI issuance session.
Key algorithms supported by the mobile wallet bootstrap flow.
Localized display metadata normalized from issuer, credential, or verifier protocol metadata.
Wallet-local persistence configuration.
A wallet credential that satisfies one DCQL credential query in the presentation request.
A required presentation credential-query combination.
User-selected presentation credential option.
Claim or selective-disclosure value that may be shared for a matched credential.
User-selected selectively disclosable claim for a selected presentation credential option.
OAuth 2.0 and OpenID4VP 1.0 authorization error codes supported by the wallet.
Preview of an OpenID4VP presentation request before the wallet submits a VP token.
Opaque presentation preview handle. It is valid only for the wallet that created it.
Result of resolving and validating an OpenID4VP request for presentation preview.
Partial request context retained when an OpenID4VP request is invalid.
Verifier and transaction metadata extracted from a presentation request.
Result of answering an OpenID4VP presentation request.
Reader authentication state. Only MobileWalletReaderTrust.Trusted means a reader was identified, and reaching it requires both a valid signature and an accepting application trust policy.
The two outcomes an application trust policy may return.
Application trust policy for a cryptographically verified Annex C reader certificate chain.
Authentication established for an OpenID4VP Authorization Request or Request Object.
Response-encryption state selected for an OpenID4VP presentation request.
Selected platform registry entry no longer maps to a current wallet credential.
Transaction data profile accepted by the mobile wallet.
Typed OpenID4VP verifier metadata needed by mobile presentation-review interfaces.
Registry used when the current platform or application has no registration integration.
Secure default: a valid signature alone does not establish that a reader is trusted.
OAuth 2.0 client-attestation configuration used during mobile issuance.