Teams evaluating EUDI Wallet integration often get stuck between protocol documentation and real product flows. The demo bank closes that gap. It is a runnable, inspectable reference that combines PID-based onboarding, sign-in, and authorisation moments in one end-to-end journey.
This post explains what the demo includes, how verification works, and the scope of the implementation.
The demo bank is a full-stack reference app for PID-based identification and wallet flows. It is open source and available as a live demo.
The repository is organised as a monorepo with client/, server/, and shared/ workspaces for the demo bank use case. It is designed for evaluation and learning with simplified business logic.
The demo bank focuses on common banking moments where identity confirmation matters:
The actions are simulated. The point is to show when and how wallet verification is inserted into a user journey.
The demo supports two presentation modes and multiple credential formats:
dc+sd-jwt)mso_mdoc)These options are visible in the UI and the code, which makes the demo a practical reference for teams deciding how to structure their own verifier flows. For the protocols, see OID4VP and the Digital Credentials API.
PID attributes are disclosed with user consent and used to drive decisions in the flow. The demo uses the policy response and disclosed claims from the authoriser to determine whether a user can proceed.
This keeps the decision logic explicit and inspectable, which is the main purpose of the demo.
The demo aligns with EUDI use case guidance and focuses on identity confirmation, while payment authentication and PSD2 SCA are out of scope. The business logic is simplified for clarity.
This is a strong baseline for product discovery, technical evaluation, or internal workshops:
Have a question or want to chat about how Vidos can help? Reach out to our team of real-world practitioners today.
