01From document collection to attribute verification
Traditional onboarding often collects an entire document even when the service only needs one fact. A wallet-based workflow can be designed around narrower attribute requests, depending on the credential and use case.
Examples include proving an age threshold, retrieving specific identity fields for a regulated onboarding process, or verifying a driving entitlement without treating the complete document image as the primary artefact.
02Policies should match declared intended use
The European Digital Identity Regulation requires relying parties to declare their intended wallet use and the data they plan to request. It also states that relying parties shall not request data beyond what they indicated during registration.
Adminyra models requested attributes as verification policies so the application can use an approved policy instead of assembling arbitrary attribute requests at runtime.
03Less stored data, smaller breach impact
Data minimisation is not only a privacy principle. Reducing collected and retained identity data also reduces the amount of sensitive information a service must protect, govern and delete.
The Adminyra control plane therefore stores operational metadata separately and is explicitly designed not to persist wallet presentation payloads or identity claims in its normal transaction records.