EUDI Wallet Verification Platform

Wallet verification banks can demo, pilot, and deploy.

Smart Verifier Gateway gives banks a ready-made relying party gateway for EUDI wallet flows: request generation, trust validation, credential verification, auditability, and a clean bank-facing result handoff.

Protected demo access

Enter your demo access token once to open the protected bank walkthrough without hitting an authorization error.

If the current page URL already includes access_token=..., this field will be prefilled automatically.
Hosted Demo Run the end-to-end flow from wallet request to bank-style inbox.
Trust Layer Issuer, TL/LOTL, revocation, SD-JWT, and holder binding support.
Integration Ready Demo inbox today, outbound webhook delivery next for customer systems.

For Product Teams

Show a believable bank journey without building a full onboarding stack. The verifier demonstrates where verified identity data lands and how a bank would consume it.

For Architecture Reviews

Explain the relying party boundary clearly: request generation, wallet interaction, trust validation, result normalization, and downstream delivery.

For Pilot Readiness

Move from demo mode to customer integration by swapping the built-in inbox for webhook delivery and customer-specific configuration.

What the platform covers

This product is designed to stop at the right boundary: it does the wallet verification work and hands a normalized result to the bank, instead of trying to become the bank’s whole onboarding stack.

Inside the verifier

  • OpenID4VP request generation
  • QR and deep-link entry points
  • SD-JWT and mdoc verification flows
  • Trust list and revocation validation
  • Audit trail and operator visibility

Handed off to the bank

  • Normalized identity result payload
  • Verification status and timestamps
  • Issuer and trust context
  • Event history for troubleshooting
  • Webhook or inbox delivery model

Deployment footprint

The current environment is live at https://verifier.wardershield.com. Public wallet routes remain open for the relying party flow, while demo and operator surfaces stay protected behind access tokens.

Public flow

  • GET /api/request
  • GET /api/request/<id>
  • POST /api/callback
  • GET /api/status/<id>

Protected surfaces

  • /api/demo/* for bank-facing walkthroughs
  • /api/admin/* for operator diagnostics
  • Bearer token or query token support for demos