.png)
Testing verifiable credential flows requires a wallet that trusts your verifier. The EUDI reference wallet validates verifier signing certificates against a hardcoded trust store, which means testing with different verifiers typically requires building custom wallet versions with the appropriate trust configuration.
We've created a pre-configured EUDI wallet build that already trusts the Vidos Authorizer signing certificate. This lets you start testing credential presentation flows immediately, without setting up a build environment or managing trust configuration.
The EU Digital Identity Wallet is a reference implementation of a digital identity wallet that supports W3C Verifiable Credentials and decentralised identifiers. It demonstrates how wallets can implement the European Digital Identity framework.
The wallet uses OpenID4VP (OpenID for Verifiable Presentations), which enables verifiable credential presentation over HTTP using OAuth 2.0 authorisation flows. It supports both remote presentation scenarios (same-device and cross-device flows via QR codes) and proximity scenarios (Bluetooth with reader authentication).
Our test build is a fork of the official reference implementation, pre-configured to trust the Vidos Authorizer. The only difference is the trust configuration; the wallet's behavior and features remain identical to the upstream version.
The current trust model in EUDI wallets is certificate-based. When a verifier wants to request credentials, it creates an Authorisation Request signed with its private key. The wallet validates this signature using the verifier's certificate, but that certificate must exist in the wallet's trust store, a list of trusted certificates embedded in the application at build time.
This creates a testing challenge. Each verifier has its own signing certificate, and the wallet only accepts requests from explicitly trusted verifiers. To test with a new verifier, you need to rebuild the wallet with that verifier's certificate added to the trust store.
This applies to both remote and proximity scenarios. For remote presentation, the wallet validates the Authorisation Request signature. For proximity presentation, the wallet validates the reader authentication certificate that proves the verifier's identity during the Bluetooth exchange.
For developers, this means you can't use a stock EUDI wallet to test with arbitrary verifiers. You need access to an Android build environment, the wallet's source code, signing keys, and knowledge of where to add trust anchors. This friction slows down development and makes it harder to experiment with credential flows.
Custom builds are a transitional solution. The EU has adopted Commission Implementing Regulation (CIR) 2025/848, which establishes a Wallet Relying Party Registration system. This regulation shifts the trust model from hardcoded certificates to dynamic registry queries.
Here's how it will work: Verifiers (relying parties) register with a trusted authority, either at the Member State level or with an EU-level registry. This registration proves their legitimate intent to request credentials and includes information about what credentials they're authorised to request. When a wallet receives an Authorisation Request, it queries the registry at runtime to validate that the verifier is registered and trusted. Trust decisions become dynamic rather than build-time decisions.
The benefits are significant. Wallets no longer need custom builds to trust new verifiers. Governance becomes centralised, making it easier to add or revoke verifier trust based on compliance and behavior. The ecosystem becomes more scalable, since adding a new verifier doesn't require updating and redistributing wallet applications. This aligns with the broader EU digital identity framework, which aims for interoperability and consistent trust mechanisms across member states.
CIR 2025/848 was adopted in February 2025, but implementation requires infrastructure. Member States need to build registration systems, define operational procedures, and establish governance models. There's no specific timeline yet for when these registries will be operational in production.
Until that infrastructure is in place, custom wallet builds remain the practical approach for testing. The test wallet we've provided bridges this gap, letting you experiment with credential flows today while the ecosystem develops the registration infrastructure.
You can download the latest version of the test wallet from the GitHub releases page. Expand the Assets section and download the APK file.
For installation, you have two options. If you have Android Debug Bridge (ADB) set up, you can run adb install <path-to-apk> to install directly from your computer. Alternatively, download the APK directly on your Android device and open it. You'll need to enable "Install from unknown sources" for your browser if prompted.
The wallet requires Android 10 or higher (API level 29). On first launch, you'll be asked to create a PIN for authentication. After that, the wallet is ready to use. The Vidos Authorizer signing certificate is already configured in the trust store, so you can immediately test presentation flows.
One important note: this is a test build intended for development and experimentation. Production deployments should build their own wallet version with appropriate trust configuration, security hardening, and compliance measures for their specific requirements. For complete installation instructions, see the guide in the Vidos documentation.
Once the wallet is installed, visit https://authorizer.demo.vidos.id to test credential presentation flows. The demo tool lets you configure authorisation requests, specify which attributes to request, and test both same-device and cross-device flows.
A typical flow looks like this: Visit the demo site, configure your credential request by selecting the attributes you want to request, and generate an authorisation request. You can either scan the displayed QR code from another device or use the same-device flow. The wallet opens and displays the requested attributes. You select which attributes to share (you must share at least one), authenticate with your PIN, and the presentation completes. The demo site will show the verification result and the attributes that were shared.
What makes this work is the trust relationship. The wallet recognises the Vidos Authorizer as a trusted verifier because its certificate is in the trust store. You'll see trust indicators in the wallet UI, and the flow proceeds without warnings or trust errors. This is the experience users should have with registered verifiers once Relying Party Registration is operational.
For more information about the Authorizer's capabilities and configuration options, see the Authorizer documentation.
Custom builds are necessary today, but they're a temporary solution to a transitional problem. The test wallet removes the friction of building and configuring your own wallet, letting you focus on developing and testing verifiable credential flows.
As the EU's Relying Party Registration infrastructure comes online, this entire process will become simpler. Wallets will dynamically trust registered verifiers, and developers won't need pre-configured builds. Until then, the test wallet provides an immediate path to testing with the Vidos Authorizer.
Download the test wallet from the releases page, test presentation flows at authorizer.demo.vidos.id, and explore the full documentation to learn more about EUDI wallet integration.
Have a question or want to chat about how Vidos can help? Reach out to our team of real-world practitioners today.
