.png)
The EUDI ecosystem is moving fast. Teams now have clearer policy direction, stronger technical specifications, and published use case manuals. But one gap remains common across product and engineering teams: converting that guidance into a working implementation you can actually test.
We are launching Vidos EUDI Use Case Demos to help close that gap.
This launch is designed to be practical. You can run the journey yourself in the browser, inspect the code, and use it as a baseline for your own internal experiments.
The first public demo is VidosDemoBank, a banking scenario built to show realistic wallet-based user journeys, not just isolated protocol calls.
In the current flow, users can:
These are the same kinds of actions teams often need to model when designing EUDI-ready customer experiences: onboarding, returning access, and step-up identity confirmation for sensitive actions.
Most teams evaluating EUDI verifier journeys face the same challenge: they can read specifications, but they still need a concrete, runnable reference to align architecture, UX, and delivery decisions.
The goal of this demonstrator is to provide that reference.
Instead of starting from a blank repository, teams can work from a real implementation that already expresses key identity flow patterns. That shortens time-to-learning and improves stakeholder alignment across product, engineering, and compliance.
The demo and repository are built to let teams validate implementation choices early:
These are exactly the kinds of technical and product details that are easier to understand in a running application than in diagrams alone.
This launch is aligned with the direction and structure of the published EUDI use case manuals, especially for identification and payment-related journeys.
Useful references:
To keep the scope clear: this demonstrator shows practical identity and confirmation journeys in a banking context. It is intended as an implementation reference and learning tool, not as a statement of full production or regulatory completeness for all payment-authentication scenarios.
Identity systems depend on trust. For implementation teams, trust is stronger when behavior is inspectable.
By releasing the code under MIT license, this project gives teams a transparent baseline they can review, run, adapt, and discuss internally. That makes it easier to:
In other words, this is not just a live demo to click through. It is also an inspectable reference for real engineering conversations.
This demonstrator is useful for:
If your team is currently translating EUDI requirements into roadmap items, this can help you move from abstract planning to practical implementation decisions faster.
Vidos EUDI Use Case Demos are built for one purpose: helping teams make EUDI wallet journeys tangible, testable, and easier to implement.
If you are designing EUDI-ready services, start by trying the live demonstrator, then inspect the code and map what you learn into your own delivery plan.
Have a question or want to chat about how Vidos can help? Reach out to our team of real-world practitioners today.
