.png)
Every Vidos demo follows the same fundamental pattern: a relying party requests credentials from your wallet using the OpenID4VP protocol, your wallet presents them, and the result drives the business flow. Different demos show different business outcomes, but the verification loop never changes.
This post breaks down that universal flow so you can see how the demos work end to end, how the Authorizer API fits in, and why the pattern aligns with privacy and compliance expectations under eIDAS 2.0.
Each demo is a reference implementation of a real-world eIDAS 2.0 use case. The suite is designed to be repeatable: if you understand one demo, you understand them all. That makes the flow the most valuable artifact in the demos because it explains the UX, the integration surface, and the security model in one place.
Just as important, the flow shows how a business can request, verify, and act on cryptographically signed credentials without collecting or storing personal data. Verification and policy checks happen server side, and the app only uses the disclosed claims needed to make a decision.
The demo app calls the Vidos Authorizer API to create a credential request. This request defines which attributes are required for the business decision. The relying party is explicit about what it needs, and nothing is requested outside that scope.
The Authorizer returns an authorisation URL. On desktop, the demo renders it as a QR code. On mobile, it can be a deep link. Either way, this URL is the handoff into the wallet experience.
The wallet displays the requested attributes and asks the user to approve or reject the presentation. This is where selective disclosure and explicit consent are enforced. The user decides what is shared.
While the wallet interaction is in progress, the demo app polls the Authorizer for status updates. The state machine is simple and observable:
This keeps the demo UI responsive without exposing wallet internals to the relying party.
If the presentation is authorised, the demo fetches the policy response. Server-side checks validate the presentation, integrity, and issuer trust. The demo then uses the disclosed claims to drive the business outcome in the UI. The app never needs to store personal data and instead uses what is required for the immediate decision.
The flow maps directly to eIDAS 2.0 privacy goals: selective disclosure, explicit consent, and minimal data retention. The reliance on server-side verification keeps sensitive cryptographic processing off the client and ensures consistent policy enforcement. That model is consistent with the PID Rulebook and the broader ARF documentation.
In practice, the demos show how a relying party can request exactly what it needs, get a high-assurance response, and avoid building a data warehouse of personal information. That is the core promise of EUDI-style verification, and the demos make it concrete.
The demos use two transport modes:
direct_post as the default transport. This is the core flow and is used in all demos.In the demo suite, DC API support is implemented with Multipaz and Valera wallets. If you are testing mobile UX, DC API is worth exploring, but the underlying verification loop remains the same.
If you are a relying party, start by tracing the five steps in one demo. The use case demo site has a full walkthrough at https://eudi-usecase.demo.vidos.id/how-demos-work and a list of scenarios to try at https://eudi-usecase.demo.vidos.id/#use-cases. Use the Authorizer developer testing tool at https://authorizer.demo.vidos.id to inspect requests and responses, then map each step to your own systems: where the request is created, how the wallet handoff happens, how you handle status updates, and where policy checks live.
If you are a wallet provider or issuer, use the same loop to validate interoperability. The demos are built for repeatable testing: you can confirm that your wallet handles consent properly, that your issuer’s credentials satisfy policy, and that the relying party can act on the disclosed claims.
All EUDI demos are different outcomes built on the same verification loop. Once you understand the five steps, you can reason about any use case in the suite. Try a demo, trace the flow end to end, and map each step to your own wallet, issuer, or relying party integration.
Have a question or want to chat about how Vidos can help? Reach out to our team of real-world practitioners today.
