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.
App-owned Android HCE service used for mdoc NFC engagement and retrieval.
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.
Client identifier scheme established while authenticating an OpenID4VP request.
Configuration for creating a MobileWallet.
Holder-key choice for one accepted configuration or dataset.
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.
Accepted configuration/dataset and its holder-key choice.
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.
One credential instance, backed by an existing platform wallet key.
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 of a presentation request.
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.
User or host action accepted by a proximity session.
Deterministic result of dispatching an action.
Action kinds used for state-derived UI affordances without constructing an action payload.
Validated output of one recognized, versioned wallet application profile.
One locally validated, display-safe application authorization value.
One candidate made available to an application-profile adapter.
Dependency-free parsed request facts supplied to application-profile adapters.
Versioned wallet-owned interpreter for application-specific request data.
Exact request and compatible candidates supplied to a versioned application profile.
Ordered registry requiring at most one profile to recognize a request.
Result of asking one application profile to recognize and validate the exact request.
How the holder approves data release. Transport selection remains independent.
Timing of the holder's deliberate approval for a locally completed response.
Bearer selection policy kept separate from the app-visible session state.
Complete BLE bearer configuration; it cannot exist unless BLE retrieval is selected.
BLE roles a holder may prepare for one in-person presentation.
Side-effect-free prerequisite snapshot. No radio resource or session material has been created.
Result returned by an application-owned certificate-revocation source.
Immutable configuration for one single-use proximity session.
Shared standards-profile, path, revocation, RICAL, and product-trust evaluator.
Actual connected route, independent of the methods configured or advertised.
Eligible wallet credential projected without raw credential or key material.
Current status of a credential at the explicit application status boundary.
Explicit, optionally network-backed status boundary. The SDK itself performs no hidden lookup.
Application-owned transport for explicit CRL distribution-point requests.
A complete DER CRL retrieved by the application's network/cache policy.
Reader-certificate CRL evaluator for ProximityReaderRevocationPolicy.Check.
Certificates whose CRL status the hosting application requires.
Holder authentication frozen for a reviewed document response.
Explicit allowlist and preference applied before an immutable review is constructed.
Generic device-signed value proposed by a recognized application profile.
One satisfiable document request in an immutable review snapshot.
Credential and disclosure choice for exactly one reviewed document request.
Dependency-free namespace and element identifier.
Prepared engagement presented by the host UI.
Engagement that actually won the reader connection.
Stable, non-sensitive failure exposed by the Wallet SDK.
Layer-stable error category; raw dependency and platform exceptions are never exposed.
Exact holder-key authorization context for a frozen approved submission.
One protected-key operation required by a frozen approved document response.
Privacy-safe outcome of a system surface performed by the host application.
Conventional NFC Forum handover selection; provisional NFCv2 has its own session variant.
Complete conventional NFC retrieval length contract.
Result of an explicit holder decision made before connection.
Opaque one-use approval. Hosts may display or cancel it, but cannot construct or expand its scope.
Versioned mdoc interoperability boundary selected for one proximity session.
Reader-asserted purpose hint associated with the selected use case.
Display-safe reader authentication and trust fact for holder consent.
Authentication result whose trust payload exists only after successful verification.
Scope covered by one reader-authentication statement.
Scope-aware summary for the reviewed documents; raw statement evidence remains available.
Cryptographic validity of reader authentication, kept separate from trust.
Result of validating the reader certificate path against explicitly configured trust material.
Exact verified reader evidence supplied to an application-owned trust policy.
Policy applied after reader authentication and trust facts have been evaluated.
Explicit application boundary for OCSP, CRL, or another reader-certificate status source.
Revocation behavior selected for reader trust.
Reader-certificate revocation fact, kept independent from path validity and product trust.
Explicit application-provisioned Reader CA certificate and optional display label.
Immutable shared reader-trust policy.
Trust decision supplied by the hosting wallet application.
Explicit trust boundary for verified reader certificate evidence.
Kind of public reader-trust material represented by an import preview.
Import review which must be explicitly confirmed before its settings are persisted.
Complete holder-owned Reader Authentication settings snapshot.
Strict codec and importer for holder-owned Reader Authentication settings.
Trust outcome after valid reader authentication.
Recovery action supported by the phase that reported a failure.
Normalized host remediation suggested by a side-effect-free prerequisite check.
One requested or alternative data element shown during consent.
Nonempty conventional retrieval plan used by QR or NFC handover.
Immutable holder-consent snapshot bound to one exchange and exact request.
Opaque identity issued by the wallet for one consent review.
Why a request needs a fresh review.
Immutable policy for one explicitly configured RICAL provider.
Application-owned evaluator for ecosystem-specific RICAL trust-constraint semantics.
Supplies the latest application-selected RICAL without an implicit SDK network request.
Exact active RICAL supplied by an application-owned provider boundary.
Explicit application-provisioned root for one RICAL provider.
Exact RICAL signer evidence passed to an application-owned revocation source.
Explicit application boundary for RICAL-signer OCSP, CRL, or another status source.
Revocation behavior selected for one RICAL provider's signer certificate.
Optional RICAL evidence fact. A match never establishes product trust by itself.
One RICAL trust constraint, with each value CBOR-encoded as unpadded Base64URL.
Runtime evidence is independent of whether the host selected a method.
Single-use, wallet-owned proximity presentation session.
Owns engagement and compatible retrieval together for one single-use session.
A wallet-verified request that can be approved before a new connection. This is not permission to share.
Display-only receipt. Its data is not an authorization token and cannot be replayed.
Public Wallet SDK session state; each variant carries only data valid for that phase.
Persisted Reader CA trust material selected by the holder.
Persisted, already validated static qualification RICAL provider.
Complete holder choice for the current review; it is rebound and revalidated before response generation.
Bearer actually carrying the connected session.
One transport's independent support dimensions.
Selected edition-2 use case projected for review.
Registry used when the current platform or application has no registration integration.
Default status policy relies on the locally verified MSO validity interval only.
Default policy: validity is reported, but no reader certificate becomes trusted implicitly.
OAuth 2.0 client-attestation configuration used during mobile issuance.