Skip to main content

Wallet compatibility

This page records which wallets have been tested with EUDIPLO and which features worked. EUDIPLO itself is tested against the OpenID Foundation conformance suite for OID4VCI and OID4VP with every change, so a wallet that passes the same suite should work without wallet-specific configuration.

If a conformant wallet does not work with EUDIPLO, open an issue.

Wallet QA resultsโ€‹

Wallet QA runs a wallet through a catalog of issuance, presentation and rejection tests against EUDIPLO and decides each verdict from EUDIPLO's session evidence. Its published results are on the Wallet QA results page, with a JSON feed at /v1/published.

The results are not a certification. Each entry shows one wallet build on one date, and you can repeat a test with the same build. An entry is either recorded by the Wallet QA instance itself or self-reported from another instance, and a pass that rests on the tester's answers instead of protocol evidence is marked as tester-attested.

The tables below are maintained by hand from reported runs. Besides the tested version and supported features, they hold the notes and log locations for each wallet that a test run does not record.

Tested walletsโ€‹

WalletProviderDownloadDetails
EU Reference ImplementationECAndroidDetails
Paradym WalletAnimoAndroid / iOSDetails
MultipazMultipazAndroidDetails
AV Reference ImplementationECAndroidDetails

Feature matrixโ€‹

WalletAuthPreIAEDPoPAttDC APIAnnex CSD-JWTmdoc
Reference Implementationโœ…โœ…n/aโœ…โœ…n/aโ€”โœ…โœ…
Paradym Walletโœ…โœ…n/aโœ…n/aโœ…โ€”โœ…โœ…
Multipazโœ…โœ…n/aโœ…n/aโœ…โ€”โœ…โœ…
AV Reference Implementationโ€”โœ…n/aโ€”โ€”โ€”โœ…n/aโœ…
ColumnMeaning
AuthOID4VCI authorization code flow
PreOID4VCI pre-authorized code flow
IAEOID4VCI interactive authorization endpoint
DPoPDPoP-bound access tokens
AttWallet attestation (OAuth client attestation)
DC APIOID4VP over the Digital Credentials API
Annex CISO 18013-7 Annex C (org-iso-mdoc) over the Digital Credentials API
SD-JWTSD-JWT VC credentials (dc+sd-jwt)
mdocmdoc credentials (mso_mdoc)
Valuesโœ… works ยท โ€” not yet tested with EUDIPLO ยท n/a the wallet does not support the feature

Reference Implementationโ€‹

  • Version tested: 2026.02.26-Demo
  • Last verified: February 26, 2026
  • Notes: requires wallet attestation.
  • Logs: in the app, Settings โ†’ Retrieve Logs.

Paradym Walletโ€‹

  • Version tested: 1.20.2
  • Last verified: September 21, 2026
  • Notes: the status list and the credential must be signed with the same certificate. The wallet cannot yet handle differing trusted_authorities in a DCQL query; such queries result in no match.
  • Logs: in the app, Settings โ†’ Export Logs.

Multipazโ€‹

  • Version tested: 2026.W24.0-impl-verification-links-17-git-6cfc8e8
  • Last verified: June 17, 2026
  • Notes: shows the credential's logo on the card.

AV Reference Implementationโ€‹

  • Version tested: July 2026 demo build (Android, Digital Credentials API in Chrome)
  • Last verified: July 9, 2026
  • Notes:
    • Tested for ISO 18013-7 Annex C: mdoc issuance with the pre-authorized code flow, and org-iso-mdoc presentation over the Digital Credentials API, including HPKE response decryption and DeviceAuth verification.
    • mdoc-only wallet; SD-JWT VC does not apply.
    • Its reference IACA and document signer certificates carry a malformed issuerAltName extension. EUDIPLO parses them with a tolerant X.509 extension parser (reported upstream).

Testing a new walletโ€‹

Protocol conformance is tested automatically; wallet-specific behavior still needs a run with the wallet itself. There are two ways to do it:

Wallet QA (hosted)Your own EUDIPLO
ForWallet developers with a build they can configureAnyone, including store builds of a wallet
Wallet buildMust trust the Wallet QA test rootMust accept your EUDIPLO's certificates (requirements)
SetupNone: open conformance.eudiplo.devEUDIPLO on a public HTTPS URL
VerdictDecided from EUDIPLO's session evidence and your checklist answersYou judge each step yourself
ResultPublished on the results pageReported in an issue

With Wallet QAโ€‹

The hosted instance at conformance.eudiplo.dev runs EUDIPLO as issuer and verifier and needs nothing installed besides the wallet.

  1. Trust the test root in your wallet build. The instance signs credentials and presentation requests with certificates from the Wallet QA test root. Download it from /trust/wallet-qa-test-root.der and check its SHA-256 fingerprint against /trust/trust.json. A wallet installed from an app store does not trust this root, so it rejects the instance's presentation requests and may refuse its credentials; test a store build against your own EUDIPLO, with certificates the wallet already accepts (see Wallet and registrar requirements). The start page shows under This instance what the wallet has to trust.
  2. Run the tests and publish. Open the instance, create a workspace for your wallet build, run the tests from the catalog and press Publish results. The tester guide walks through each step, the verdicts and troubleshooting, and explains how to run Wallet QA locally.

Against your own EUDIPLOโ€‹

  1. Set up EUDIPLO. Follow Foundation and Issue your first credential. A mobile wallet needs a public HTTPS URL, so set PUBLIC_URL to a tunnel or public host. Without the CLI, a minimal container is:

    docker run -d --name eudiplo -p 3000:3000 \
    -e PUBLIC_URL=https://your-public-host.example \
    -e MASTER_SECRET="$(openssl rand -base64 32)" \
    -e AUTH_CLIENT_ID=root \
    -e AUTH_CLIENT_SECRET="$(openssl rand -base64 24)" \
    ghcr.io/eudiplo/eudiplo:latest
  2. Start with a known-good configuration. Create a credential configuration from a template (for example PID as SD-JWT VC), make sure the tenant has signing keys and certificates, and leave DPoP off for the first run.

  3. Test issuance. The pre-authorized code flow is required: create an offer, scan it, and confirm the credential is stored. Then test the authorization code flow if the wallet supports it, and confirm that a redeemed or expired offer is rejected.

  4. Test presentation. Create a request from a presentation configuration and run it cross-device (QR code on another device) and, if supported, same-device. Confirm the session completes with the expected claims, then repeat with a query that requests fewer claims to check selective disclosure.

  5. Record the result. Note the wallet name and exact version, device and OS version, which flows passed or failed, configuration changes you needed (for example DPoP off), and error messages or wallet logs.

Report resultsโ€‹

  • Tested with Wallet QA: publish the results from your workspace (Publish results), or upload the workspace JSON report on a hosted instance. They appear on the results page.
  • Wallet works: open an issue with the wallet compatibility template and include the results you recorded in Against your own EUDIPLO, so the wallet can be added to this page.
  • Wallet fails: check the notes above, then open an issue with reproduction steps, EUDIPLO and wallet versions, and the session logs.
  • Questions: ask in the Discord community.