[{"data":1,"prerenderedAt":725},["ShallowReactive",2],{"eidas2/eudi-wallet":3},{"id":4,"title":5,"author":6,"body":7,"description":711,"extension":712,"meta":713,"navigation":714,"path":715,"publishedAt":716,"seo":717,"stem":718,"tags":719,"updatedAt":716,"__hash__":724},"eidas2Articles/eidas2/eudi-wallet.md","What Is the EUDI Wallet? A Complete Guide to the EU Digital Identity Wallet","Tamino Baumann",{"type":8,"value":9,"toc":665},"minimark",[10,19,22,27,34,41,55,57,61,67,72,75,80,83,88,91,96,99,104,107,110,114,121,124,128,135,139,146,149,177,179,183,186,190,193,207,210,214,217,231,234,238,241,252,255,257,261,264,309,312,314,318,325,328,349,352,356,374,378,393,395,399,410,414,469,473,486,500,502,506,513,517,520,524,527,531,534,538,541,552,554,558,561,565,573,577,584,588,591,594,596,600,603,606,610,613,617,620,624,627,631,634,638,641,645,663],[11,12,13,14,18],"p",{},"The ",[15,16,17],"strong",{},"EUDI Wallet"," (European Digital Identity Wallet, also abbreviated as EUDIW) is a digital identity app for EU citizens and residents. It lets users store official credentials — such as a national ID, driving licence, or professional qualification — on their mobile device and share them securely with public services and businesses across the EU.",[20,21],"hr",{},[23,24,26],"h2",{"id":25},"what-is-the-eudi-wallet","What is the EUDI Wallet?",[11,28,29,30,33],{},"The EUDI Wallet holds digital credentials and lets users prove facts about themselves — their identity, age, qualifications, or permissions — without sharing more than necessary. Users stay in full control of what they share through ",[15,31,32],{},"selective disclosure",": individual attributes can be revealed from a credential without exposing the full document. Proving to a venue that you are over 18, for example, shares only an age confirmation — not your name, address, or exact date of birth.",[11,35,36,37,40],{},"Businesses and services that request credentials — called ",[15,38,39],{},"Verifiers"," or Relying Parties — may only ask for attributes they have formally registered and declared a purpose for. The wallet warns users if a request goes beyond that.",[11,42,43,44,47,48,50,51,54],{},"Each EU member state must offer at least one EUDI Wallet to citizens and residents by the end of 2026, provided by public authorities or certified private organisations. Three types of organisations make the ecosystem work: ",[15,45,46],{},"Issuers"," (governments and businesses that issue credentials into the wallet), ",[15,49,39],{}," (businesses and services that request credentials from the wallet), and ",[15,52,53],{},"Wallet Providers"," (the organisations that build and operate the wallets).",[20,56],{},[23,58,60],{"id":59},"what-you-can-do-with-the-eudi-wallet","What you can do with the EUDI Wallet",[11,62,63,66],{},[15,64,65],{},"The EUDI Wallet has four core capabilities."," All of them are defined by the Architecture and Reference Framework (ARF) — the technical specification that governs how every wallet, issuer, and verifier in the EU must behave. The current version is ARF v2.8.0.",[68,69,71],"h3",{"id":70},"_1-store-and-present-credentials","1. Store and present credentials",[11,73,74],{},"The wallet can work with four categories of credentials, from government credentials (e.g. national ID, birth certificate) to everyday credentials (e.g. gym membership, loyalty card):",[11,76,77],{},[15,78,79],{},"PID — Person Identification Data",[11,81,82],{},"The core digital ID that every certified EUDI Wallet must hold. Issued by a government-appointed institution in each member state, the PID contains mandatory attributes including family name, given name, date of birth, place of birth, and nationality. It is recognised across all EU member states and is required to activate a certified eIDAS 2 wallet (EUDI Wallet).",[11,84,85],{},[15,86,87],{},"PuB-EAA — Public Electronic Attestations of Attributes",[11,89,90],{},"Official government documents issued digitally by public-sector bodies: civil registries, tax authorities, immigration authorities. Examples include birth certificates, residence permits, and tax IDs. PuB-EAAs carry the same legal weight as their paper originals.",[11,92,93],{},[15,94,95],{},"QEAA — Qualified Electronic Attestation of Attributes",[11,97,98],{},"Digital credentials based on verified data from public authorities — for example, a company formation document sourced from an official companies register. Issued by Qualified Trust Service Providers (QTSPs). QEAA carry the same legal weight as paper originals.",[11,100,101],{},[15,102,103],{},"EAA — Non-Qualified Electronic Attestations of Attributes",[11,105,106],{},"Everyday credentials such as boarding passes, online learning certificates, professional memberships, and loyalty cards. Any business can issue EAAs (as a Non-Qualified EAA Provider) to reduce friction and improve user experience.",[11,108,109],{},"Credentials can be presented both online and offline. Offline proximity presentation (e.g. showing a mobile driving licence to a police officer) uses ISO/IEC 18013-5 and does not require an internet connection.",[68,111,113],{"id":112},"_2-identify-and-authenticate","2. Identify and authenticate",[11,115,116,117,120],{},"Users can present their PID to authenticate and access public and private online services across the EU — for example, logging into a national health portal, accessing social security services, or opening a bank account online. The wallet maintains a full ",[15,118,119],{},"transaction log"," — a dashboard showing every past interaction with a Relying Party — and gives users the right to request data erasure under GDPR Article 17 and to report suspicious Relying Parties to national data protection authorities.",[11,122,123],{},"Strong Customer Authentication (SCA) for electronic payments is also supported: wallet units can authenticate payment transactions (amount, payee) in compliance with PSD2 Article 97 requirements, enabling secure and seamless payment flows without a separate authenticator app.",[68,125,127],{"id":126},"_3-sign-documents-with-qualified-electronic-signatures","3. Sign documents with qualified electronic signatures",[11,129,130,131,134],{},"Users can sign documents digitally directly from the wallet — without needing a separate tool or service. The signatures produced are ",[15,132,133],{},"qualified electronic signatures (QES)",", which carry the same legal weight as a handwritten signature across all EU member states under eIDAS 2, and are provided free of charge by default.",[68,136,138],{"id":137},"_4-authenticate-with-pseudonyms","4. Authenticate with pseudonyms",[11,140,141,142,145],{},"Users can present a ",[15,143,144],{},"pseudonym"," to a Relying Party in situations where their full identity is not required. A pseudonym allows the Relying Party to recognise the same user across sessions without learning who they are. Relying parties are legally required under eIDAS 2 to accept pseudonyms where identification is not mandated by law (Article 5b(9)). Pseudonyms are generated and stored encrypted locally within the wallet.",[11,147,148],{},"The ARF v2.8.0 defines four pseudonym use cases, at different stages of specification:",[150,151,152,159,165,171],"ul",{},[153,154,155,158],"li",{},[15,156,157],{},"Pseudonymous account access"," — a user authenticates to a service using a pseudonym instead of their identity, and the service links that pseudonym to an account for future logins.",[153,160,161,164],{},[15,162,163],{},"Attribute registration with pseudonym"," — partially specified. A user can combine a pseudonym with a verified credential (e.g. proving age without revealing identity), but a common cryptographic binding mechanism is still being standardised.",[153,166,167,170],{},[15,168,169],{},"Rate-limited participation"," — use case defined (e.g. enforcing \"one participation per person\" in a vote without identity disclosure), but the underlying protocol is not yet specified in this version of the ARF.",[153,172,173,176],{},[15,174,175],{},"Linked pseudonymous flows across services"," — use case defined (e.g. using the same pseudonym with a merchant and a delivery carrier), but no common specification exists yet.",[20,178],{},[23,180,182],{"id":181},"ecosystem-roles-who-does-what-in-the-eudi-wallet-ecosystem","Ecosystem roles: who does what in the EUDI Wallet ecosystem",[11,184,185],{},"The wallet doesn't exist in isolation — three types of organisations make the ecosystem work, and most businesses affected by eIDAS 2 will fall into one or more of these roles.",[68,187,189],{"id":188},"issuer","Issuer",[11,191,192],{},"Issuers are governments and businesses that create and issue digital credentials into a user's wallet. An Issuer must:",[150,194,195,198,201,204],{},[153,196,197],{},"Issue credentials in the required formats (SD-JWT VC, ISO/IEC 18013-5, W3C VC for EAAs)",[153,199,200],{},"Register in the eIDAS 2 Trusted Lists",[153,202,203],{},"Implement OID4VCI with the HAIP profile for issue credentials into the EUDI Wallet",[153,205,206],{},"Manage the full credential lifecycle: issuance, updates, suspension, and revocation",[11,208,209],{},"Examples: national identity authorities (PID Providers), universities issuing diplomas, banks issuing account verification credentials.",[68,211,213],{"id":212},"verifier-relying-party","Verifier (Relying Party)",[11,215,216],{},"Verifiers are businesses and services that request digital credentials from a user's wallet. A Verifier must:",[150,218,219,222,225,228],{},[153,220,221],{},"Register as a Verifier in the eIDAS 2 Trusted Lists and declare which attributes will be requested",[153,223,224],{},"Implement OID4VP (with HAIP) and ISO/IEC 18013-7 for online verification",[153,226,227],{},"Implement ISO/IEC 18013-5 for offline (proximity) verification",[153,229,230],{},"Support all required credential formats (SD-JWT VC, ISO/IEC 18013-5, W3C VC for EAAs)",[11,232,233],{},"Examples: banks verifying identity for account opening, airlines checking travel credentials, healthcare providers verifying insurance.",[68,235,237],{"id":236},"wallet-provider","Wallet Provider",[11,239,240],{},"Wallet Providers build and operate the wallets used by citizens. They must:",[150,242,243,246,249],{},[153,244,245],{},"Manage the full wallet lifecycle: activation, management, suspension, and revocation",[153,247,248],{},"Ensure the wallets support the required standards and features",[153,250,251],{},"Get certified as a trusted Wallet Provider in the eIDAS2 ecosystem",[11,253,254],{},"Wallet Providers can be member states themselves or certified private organisations.",[20,256],{},[23,258,260],{"id":259},"eudi-wallet-compliance-deadlines","EUDI Wallet compliance deadlines",[11,262,263],{},"eIDAS 2 sets legally binding deadlines for both governments and businesses.",[265,266,267,283],"table",{},[268,269,270],"thead",{},[271,272,273,277,280],"tr",{},[274,275,276],"th",{},"Deadline",[274,278,279],{},"Who",[274,281,282],{},"What",[284,285,286,298],"tbody",{},[271,287,288,292,295],{},[289,290,291],"td",{},"End of 2026",[289,293,294],{},"All 27 EU Member States",[289,296,297],{},"Must offer at least one certified EUDI Wallet to all citizens and residents.",[271,299,300,303,306],{},[289,301,302],{},"End of 2027",[289,304,305],{},"Private-sector businesses",[289,307,308],{},"Banks, energy providers, telecoms, transport operators, and others that require strong user authentication and are not micro or small enterprises must accept EUDI Wallets.",[11,310,311],{},"Source: Regulation (EU) 2024/1183 and the eIDAS 2 Implementing Acts.",[20,313],{},[23,315,317],{"id":316},"the-regulatory-framework-eidas-2-regulation-eu-20241183","The regulatory framework: eIDAS 2 (Regulation EU 2024/1183)",[11,319,320,321,324],{},"The EUDI Wallet is created and governed by ",[15,322,323],{},"Regulation (EU) 2024/1183",", also known as eIDAS 2. The regulation was adopted by the European Parliament on 29 February 2024, published in the Official Journal on 30 April 2024, and entered into force on 20 May 2024.",[11,326,327],{},"eIDAS 2 was introduced to fix three core failures of the original eIDAS regulation from 2016:",[329,330,331,337,343],"ol",{},[153,332,333,336],{},[15,334,335],{},"Fragmented national implementations."," The original eIDAS gave rise to dozens of incompatible national identity systems. Cross-border recognition remained limited.",[153,338,339,342],{},[15,340,341],{},"Narrow scope."," eIDAS focused almost entirely on electronic signatures and did not provide a framework for broader digital identity covering education, health, finance, or travel.",[153,344,345,348],{},[15,346,347],{},"Reliance on physical presence."," Identity proofing under eIDAS required physical interaction, which became untenable during the COVID-19 pandemic and is incompatible with digital-first services.",[11,350,351],{},"eIDAS 2 addresses these gaps by introducing the EUDI Wallet across all 27 EU member states. But a regulation sets legal obligations — it does not tell engineers and product teams exactly how to build a compliant system. That is the job of two further layers: the Implementing Acts and the Architecture and Reference Framework.",[68,353,355],{"id":354},"architecture-and-reference-framework-arf","Architecture and Reference Framework (ARF)",[11,357,13,358,360,361,368,369,373],{},[15,359,355],{}," could be seen as the technical blueprint published by the European Commission that describes how the regulation should be implemented in practice. It defines what each ecosystem actor (Issuer, Verifier, Wallet Provider) must do, how they must interact, and what protocols, credential formats, and security mechanisms are required. Crucially, the ARF is non-binding — it is a design specification, not law. The current version is ",[362,363,367],"a",{"href":364,"rel":365},"https://eudi.dev/2.8.0/",[366],"nofollow","ARF v2.8.0",". A full explanation is available on the ",[362,370,372],{"href":371},"/eidas2","eIDAS 2 hub page",".",[68,375,377],{"id":376},"implementing-acts","Implementing Acts",[11,379,380,381,383,384,388,389,373],{},"Where the ARF is a blueprint, the ",[15,382,377],{}," are law. They are the regulations that take the technical rules from the ARF and the findings from the ",[362,385,387],{"href":386},"#the-large-scale-pilots-real-world-eudi-wallet-deployments","Large-Scale Pilots"," and codify them as legally binding requirements — covering credential formats, protocols, certification, Relying Party registration, and more. Every wallet, issuer, and verifier operating in the EU must comply with them. They are published incrementally as the ecosystem matures. For a full breakdown, see the ",[362,390,392],{"href":391},"/white-paper/eidas2-implementers-guide","eIDAS 2 Implementers Guide",[20,394],{},[23,396,398],{"id":397},"technical-standards-how-the-eudi-wallet-actually-works","Technical standards: how the EUDI Wallet actually works",[11,400,401,402,405,406,409],{},"For a wallet issued in Germany to work with a bank in Portugal, every actor in the ecosystem needs to follow the same technical standards. The EUDI Wallet therefore mandates specific ",[15,403,404],{},"credential formats"," — the structure in which identity data is encoded — and ",[15,407,408],{},"exchange protocols"," — the rules for how that data moves between a wallet, an issuer, and a verifier. Both are covered below.",[68,411,413],{"id":412},"credential-formats","Credential formats",[265,415,416,429],{},[268,417,418],{},[271,419,420,423,426],{},[274,421,422],{},"Format",[274,424,425],{},"Use case",[274,427,428],{},"Selective disclosure",[284,430,431,444,456],{},[271,432,433,438,441],{},[289,434,435],{},[15,436,437],{},"SD-JWT VC (IETF)",[289,439,440],{},"Mandatory for PID, PuB-EAA, QEAA. Used for online flows.",[289,442,443],{},"Yes",[271,445,446,451,454],{},[289,447,448],{},[15,449,450],{},"ISO/IEC 18013-5 (mDL/mdoc)",[289,452,453],{},"Mandatory for PID, PuB-EAA, QEAA. Supports both online (via ISO/IEC 18013-7) and offline proximity verification.",[289,455,443],{},[271,457,458,463,466],{},[289,459,460],{},[15,461,462],{},"W3C VC (VCDM v2.0)",[289,464,465],{},"Optional. Can only be used for EAAs. Does not support selective disclosure.",[289,467,468],{},"No",[68,470,472],{"id":471},"exchange-protocols","Exchange protocols",[11,474,475,482,483,373],{},[15,476,477],{},[362,478,481],{"href":479,"rel":480},"https://docs.walt.id/concepts/data-exchange-protocols/openid4vci",[366],"OID4VCI (OpenID for Verifiable Credential Issuance)"," is the protocol used by an Issuer to deliver a credential into a wallet. It is built on OAuth 2.0 and OpenID Connect and must be implemented with the ",[15,484,485],{},"HAIP (High Assurance Interoperability Profile)",[11,487,488,495,496,499],{},[15,489,490],{},[362,491,494],{"href":492,"rel":493},"https://docs.walt.id/concepts/data-exchange-protocols/openid4vp",[366],"OID4VP (OpenID for Verifiable Presentations)"," is the protocol used by a Verifier to request and receive a credential from a wallet. It is also required with the HAIP profile and is complemented by ",[15,497,498],{},"ISO/IEC 18013-7"," for remote mdoc verification flows.",[20,501],{},[23,503,505],{"id":504},"the-large-scale-pilots-real-world-eudi-wallet-deployments","The Large-Scale Pilots: real-world EUDI Wallet deployments",[11,507,508,509,512],{},"To validate the ARF and build real-world experience before the 2026 deadline, the European Commission funded four ",[15,510,511],{},"Large-Scale Pilots (LSPs)"," starting in May 2023:",[68,514,516],{"id":515},"potential","POTENTIAL",[11,518,519],{},"The largest of the four pilots: 140+ public and private partners from 19 EU Member States and Ukraine. Tested six use cases — eGovernment services, bank account opening, SIM card registration, mobile driving licence (mDL), qualified e-Signature, and ePrescription — across national and cross-border settings.",[68,521,523],{"id":522},"ewc-eu-digital-wallet-consortium","EWC (EU Digital Wallet Consortium)",[11,525,526],{},"80 partners from 24 countries. Tested three use cases: travelling (including Digital Travel Credentials), payments, and organisational digital identities.",[68,528,530],{"id":529},"nobid","NOBID",[11,532,533],{},"34 public and private partners from 6 countries (Denmark, Germany, Iceland, Italy, Latvia, Norway). Tested the EUDI Wallet for payments across three use cases: payment transactions, digital signatures, and cross-border identification.",[68,535,537],{"id":536},"dc4eu","DC4EU",[11,539,540],{},"99 institutions from 22 countries, backed by 43 public organisations and 49 private entities. Focused on education (digital diplomas, recognition of professional qualifications) and social security (Portable Document A1, European Health Insurance Card).",[11,542,543,544,547,548,551],{},"All four pilots concluded in 2025. Two additional pilots — ",[15,545,546],{},"APTITUDE"," and ",[15,549,550],{},"WE BUILD"," — launched in 2025 and are currently active. Pilot findings feed directly back into updates to the ARF and the Implementing Acts.",[20,553],{},[23,555,557],{"id":556},"building-eudi-wallet-infrastructure-the-three-approaches","Building EUDI Wallet infrastructure: the three approaches",[11,559,560],{},"Every organisation affected by eIDAS 2 — whether as an Issuer, Verifier, or Wallet Provider — must implement technical infrastructure. There are three strategic paths:",[68,562,564],{"id":563},"build-applications-buy-infrastructure-recommended","Build applications, buy infrastructure (recommended)",[11,566,567,568,572],{},"Only build the UI and application layer. Use a proven, standards-compliant infrastructure provider for credential issuance, verification, and wallet back-end. This delivers the fastest time to market with the lowest technical risk, since all protocol complexity (OID4VCI, OID4VP, HAIP, trust list integration) is handled by the infrastructure layer (e.g. the ",[362,569,571],{"href":570},"/eidas2#infrastructure","walt.id Enterprise Stack",").",[68,574,576],{"id":575},"build-applications-own-infrastructure","Build applications, own infrastructure",[11,578,579,580,583],{},"Use open-source infrastructure (such as the ",[362,581,582],{"href":570},"walt.id Community Stack",") to retain full control of the technical stack while avoiding the overhead of implementing protocols from scratch. This approach suits organisations with strong engineering teams that require data sovereignty or specific integration requirements, but need proven, actively maintained libraries rather than implementing OID4VCI and OID4VP themselves.",[68,585,587],{"id":586},"build-everything-in-house","Build everything in-house",[11,589,590],{},"Implement the full stack from scratch: credential standards, exchange protocols, key management, revocation, trust registry integration. This is the highest complexity path and carries significant ongoing maintenance cost as the ARF and Implementing Acts continue to evolve. It is viable only for organisations with dedicated identity engineering teams and a long-term roadmap that justifies the investment.",[11,592,593],{},"Most organisations building EUDI-compliant systems choose option 1 or 2. The protocol complexity alone — implementing OID4VCI with the HAIP profile, ISO/IEC 18013-5 mdoc encoding, Wallet Unit Attestations — represents months of specialised engineering work.",[20,595],{},[23,597,599],{"id":598},"frequently-asked-questions","Frequently asked questions",[68,601,26],{"id":602},"what-is-the-eudi-wallet-1",[11,604,605],{},"The EUDI Wallet (European Digital Identity Wallet) is a digital wallet mandated by EU Regulation 2024/1183 (eIDAS 2) that allows EU citizens and residents to store verified digital credentials — such as a national ID, driving licence, or professional qualification — and share them securely with public and private services across the EU. Every member state must offer at least one EUDI Wallet by the end of 2026.",[68,607,609],{"id":608},"when-will-the-eudi-wallet-be-available","When will the EUDI Wallet be available?",[11,611,612],{},"All 27 EU Member States must offer at least one certified EUDI Wallet to citizens and residents by the end of 2026. Large-Scale Pilots have already successfully tested EUDI Wallets in real-world scenarios across banking, government, healthcare, travel, and payments. The EU reference wallet implementation and testing tools are already publicly available.",[68,614,616],{"id":615},"what-can-you-do-with-the-eudi-wallet","What can you do with the EUDI Wallet?",[11,618,619],{},"The EUDI Wallet has four core capabilities: (1) store and present credentials; (2) identify and authenticate to online services, including payment SCA; (3) create qualified electronic signatures and seals with legal equivalence across the EU; and (4) authenticate using pseudonyms where full identity disclosure is not required.",[68,621,623],{"id":622},"is-the-eudi-wallet-mandatory","Is the EUDI Wallet mandatory?",[11,625,626],{},"For EU member states, yes — they must provide at least one certified EUDI Wallet by end of 2026. For citizens, use is voluntary. For businesses in regulated industries (e.g. banking, energy, transport), accepting the EUDI Wallet becomes mandatory by end of 2027.",[68,628,630],{"id":629},"what-is-eudiw","What is EUDIW?",[11,632,633],{},"EUDIW is an informal shorthand for the EU Digital Identity Wallet, used in some EC communications and earlier pilot documentation. It is not used in the current Architecture and Reference Framework (ARF v2.8.0), which uses \"EUDI Wallet\" throughout. The regulation text (Regulation EU 2024/1183) uses \"European Digital Identity Wallet\" as the full name. All three refer to the same digital identity application.",[68,635,637],{"id":636},"how-secure-is-the-eudi-wallet","How secure is the EUDI Wallet?",[11,639,640],{},"The EUDI Wallet is held to the highest identity security standard in the EU (Level of Assurance High). Every certified wallet must pass a formal conformance assessment, store credentials securely, only share what the user approves, and keep a full log of every interaction that users can audit and use to request data deletion under GDPR.",[68,642,644],{"id":643},"what-technical-standards-does-the-eudi-wallet-use","What technical standards does the EUDI Wallet use?",[11,646,647,648,547,651,654,655,658,659,662],{},"Two credential formats are mandatory: ",[15,649,650],{},"SD-JWT VC",[15,652,653],{},"ISO/IEC 18013-5"," (the mdoc format used by mobile driving licences). W3C Verifiable Credentials (VCDM v2.0) is a third, optional format — but only for non-qualified EAAs. For issuance, wallets use ",[15,656,657],{},"OID4VCI"," with the HAIP profile; for verification, ",[15,660,661],{},"OID4VP"," and ISO/IEC 18013-7, also with HAIP.",[20,664],{},{"title":666,"searchDepth":667,"depth":667,"links":668},"",2,[669,670,677,682,683,687,691,697,702],{"id":25,"depth":667,"text":26},{"id":59,"depth":667,"text":60,"children":671},[672,674,675,676],{"id":70,"depth":673,"text":71},3,{"id":112,"depth":673,"text":113},{"id":126,"depth":673,"text":127},{"id":137,"depth":673,"text":138},{"id":181,"depth":667,"text":182,"children":678},[679,680,681],{"id":188,"depth":673,"text":189},{"id":212,"depth":673,"text":213},{"id":236,"depth":673,"text":237},{"id":259,"depth":667,"text":260},{"id":316,"depth":667,"text":317,"children":684},[685,686],{"id":354,"depth":673,"text":355},{"id":376,"depth":673,"text":377},{"id":397,"depth":667,"text":398,"children":688},[689,690],{"id":412,"depth":673,"text":413},{"id":471,"depth":673,"text":472},{"id":504,"depth":667,"text":505,"children":692},[693,694,695,696],{"id":515,"depth":673,"text":516},{"id":522,"depth":673,"text":523},{"id":529,"depth":673,"text":530},{"id":536,"depth":673,"text":537},{"id":556,"depth":667,"text":557,"children":698},[699,700,701],{"id":563,"depth":673,"text":564},{"id":575,"depth":673,"text":576},{"id":586,"depth":673,"text":587},{"id":598,"depth":667,"text":599,"children":703},[704,705,706,707,708,709,710],{"id":602,"depth":673,"text":26},{"id":608,"depth":673,"text":609},{"id":615,"depth":673,"text":616},{"id":622,"depth":673,"text":623},{"id":629,"depth":673,"text":630},{"id":636,"depth":673,"text":637},{"id":643,"depth":673,"text":644},"A complete guide to the EUDI Wallet (European Digital Identity Wallet): what it is, how it works, the technical standards it uses, compliance deadlines, and how organizations build compliant infrastructure.","md",{},true,"/eidas2/eudi-wallet","2026-04-14",{"title":5,"description":711},"eidas2/eudi-wallet",[720,721,722,723],"eudi wallet","eudiw","eidas2","eu digital identity","6HijX3DQbSOPstcskXnDDAQviJ6xsl2Yek64XzWRjuM",1776267566217]