EUDI Wallet vs. traditional KYC

A wallet presentation lets a customer share selected credentials or attributes with a relying party. The relying party verifies the requested evidence and decides how it fits its service. KYC may include identity verification, customer due diligence, risk assessment, and other checks determined by applicable rules and the organization’s risk policy.

• EUDI Wallet flow: request supported credential evidence and validate issuer and presentation proofs
• KYC process: define the relevant checks, review their results, and make customer acceptance decisions
• A verified wallet credential can contribute evidence without deciding the full KYC outcome

Wallet presentations can support a request for specific claims or a supported predicate, with disclosure behavior depending on credential format and profile. Traditional digital KYC flows may combine document capture, data checks, biometrics, or other methods depending on the provider and configuration. Review actual collection, processing, and retention for each implementation.

• Ask whether a threshold or specific attribute can answer the wallet use case
• Map every KYC requirement to an evidence source and validation step
• Compare the data each configured flow collects and retains, including fallbacks

Start by identifying which step a wallet presentation could support and which controls still need a separate source or decision. Coverage depends on available wallets, issued credentials, trusted issuers, jurisdiction, and the relying party’s registration and profile configuration.

• Keep screening, risk, eligibility, and account decisions in the organization’s policy process where required
• Provide a supported fallback when a customer cannot present a compatible credential
• Record the purpose, accepted issuers, requested claims, result handling, and retention for the flow