Supported wallets
LutraID works with wallets that implement OpenID4VCI 1.0 for issuance and OpenID4VP 1.0 for presentation, with SD-JWT VC (dc+sd-jwt) or ISO mdoc (mso_mdoc) credentials. That is what EUDI Wallets use under eIDAS 2.0. Compatibility depends on the protocol features below; wallets tested with LutraID are listed under Tested wallets.
What a wallet needs
| Area | LutraID uses |
|---|---|
| Issuance | OpenID4VCI 1.0, pre-authorized code (with optional transaction code) or authorization code |
| Proof of key | proofs.jwt; EC keys P-256, P-384 or P-521 |
| Holder binding | JWK, COSE_Key or x5c |
| Presentation | OpenID4VP 1.0, DCQL, signed request object by reference (request_uri) |
| Client identifier | x509_san_dns: or x509_hash: |
| Response mode | direct_post or direct_post.jwt |
| Network | HTTPS to a publicly resolvable host |
Tested wallets
Wallets that have completed issuance and presentation with LutraID.
| Wallet | Platform | Formats | Issuance | Presentation | Tested |
|---|
No wallets are listed yet. Until they are, any wallet that meets the requirements above should work; try yours in Sandbox and tell us the result.
What does not work
- DID-based holder binding.
jwt_vc_json,ldp_vcand other W3C VC formats.vc+sd-jwtis accepted on input only.presentation_definition(Presentation Exchange); requests use DCQL only.- Deferred and batch issuance.
Trust in Sandbox and Production
Sandbox documents chain to a test root. A wallet accepts them only once that root is installed on the device; see Testing. In Production, when the issuer's assurance profile requires a wallet attestation, the attestation must chain to a trusted wallet provider, so wallets without one cannot receive those documents.
Try your wallet
- Follow the Quickstart to issue the demo document to your wallet in Sandbox.
- Run the age check against it.
- If either step fails, Troubleshooting and the record's diagnostics show where the wallet stopped. Tell us which wallet and version you used.
Last updated: 26 October 2026.