01The integration shape
Your application creates a verification session using the relevant relying party and verification policy. Adminyra prepares the wallet interaction, handles the verifier flow and returns a controlled status to your backend.
The browser is never treated as the source of truth. Verification outcomes are intended to be consumed server-to-server, while front-end QR or same-device flows only initiate or display the session.
- Create a verification session
- Present a QR code or same-device wallet request
- Receive or poll the verification result
- Process a signed webhook in your backend
Stable API, evolving verifier core
EUDI technical specifications and wallet implementations continue to evolve. The API boundary is designed so those changes can be absorbed inside the verifier layer while customer-facing endpoints remain stable.
This separation also makes it possible to move verifier compute to dedicated EU infrastructure later without changing the URLs used by customers.
Sandbox before production
The sandbox is the first integration target. It allows software teams to model relying parties, applications and policies before production registration and certificate material are involved.
Production capabilities will be enabled deliberately rather than simulated. An endpoint will never claim that an identity was verified unless the production verifier and trust checks actually performed that verification.