Skip to main content

Individual wallet units

Register and manage the wallet units of natural persons (their wallet apps), and revoke a wallet unit, its key attestations or a whole keystore type.

Create individual wallet unit

Registers an individual wallet unit in advance: the wallet of a natural person in a mobile app on one device. A mobile wallet that is not registered registers itself, authorised, at its first Wallet Unit Attestation (WUA) request, so this operation is optional. Use it to register a wallet unit before that request, or with `isAuthorised: false` to hold its WUA requests until you authorise it with [Update individual wallet unit](/docs/openid4vc-api/config-update-digital-wallet-open-id-individual-wallet-unit).

Update individual wallet unit revocation status

Revokes or suspends every Wallet Unit Attestation (WUA) of an individual wallet unit (TS3 section 2.5.1): the wallet provider sets each status list entry of its WUAs, also an entry that the wallet unit reuses for an issuer. In the same change the wallet unit loses its authorisation (`isAuthorised: false`, `attestationStatus: revoked`), so it gets no new WUA until you authorise it again with [Update individual wallet unit](/docs/openid4vc-api/config-update-digital-wallet-open-id-individual-wallet-unit).

Update individual wallet unit keystore type revocation status

Changes the status of one keystore type of the individual wallet units (TS3 section 2.5.2), for example after a weakness of a device keystore is known. Every key attestation of the type, of every individual wallet unit, gets the status on its status list entry, and the wallet provider records the status of the type. While the type is `Revoked` or `Suspended`, the wallet provider issues no new key attestation of it. `Operational` makes the key attestations of the type valid again and the type usable.