EUDI Wallet vs. document verification

An EUDI Wallet flow requests issuer-signed data from a credential in the holder’s wallet. The verifier checks the credential and presentation proofs against the request, accepted issuers, and configured trust. A document-verification flow usually starts from a photo or scan of an identity document; providers may add document-authenticity analysis, a selfie, or liveness checks.

• Wallet flow: verify the requested credential claims and holder or device proof
• Document flow: inspect submitted document images and any additional checks enabled by the provider
• Exact assurance depends on credential, issuer, wallet, vendor configuration, and operating rules

Wallets can let a person approve a request for particular attributes or predicates. A document-image flow may expose the full document image and its printed details to the service or provider. Actual collection, processing, and retention depend on the selected integration and product.

• Request only the wallet claims your decision needs
• Check whether an image or biometric sample is collected, where it is processed, and how long it is retained
• Treat consent screens and data minimization as part of the full relying-party flow

A wallet path can fit services that accept a compatible credential and can establish issuer trust. A document path may remain necessary when users lack a compatible wallet credential, when a workflow requires document imagery, or when a provider’s separate fraud checks are part of the risk model.

• Confirm wallet, credential, issuer, and request-profile coverage in target markets
• Define a secure fallback for unsupported wallets or unavailable credentials
• Evaluate downstream identity, fraud, KYC/AML, and eligibility requirements separately