EUDI Wallet The EU Digital Identity Wallet, ready for your forms today.

What is the EUDI Wallet?

The European Digital Identity Wallet is an app that every EU member state provides to its citizens and residents, free of charge for private use. It holds the person identification data (PID: name, date of birth, nationality, address) issued by the state, and can also hold other credentials such as a driving licence, diplomas, professional qualifications or proof of age.

The legal basis is eIDAS 2.0, Regulation (EU) 2024/1183, which amends the eIDAS Regulation (EU) No 910/2014 and entered into force on 20 May 2024. The technical rules come from the EU Architecture and Reference Framework (ARF) and its implementing acts.

• The person decides: the wallet shows which data a service asks for, and nothing is shared without consent.
• Only what is needed: with selective disclosure a form can ask for name and address without seeing anything else.
• Verified at the source: the data are signed by the issuing authority, so they cannot be typed wrongly or faked.
• Accepted across the EU: a wallet from one member state works with services in all others.

Why it matters for forms

Most forms start with the same questions: who are you, when were you born, where do you live? Today people type these data again and again, make mistakes, and the organisation behind the form has no proof that they are true. The wallet changes that.

• Faster forms: one confirmation in the wallet fills name, date of birth and address.
• Fewer errors and less fraud: the data come signed from the issuing authority instead of being typed in.
• Data minimisation under the GDPR: the form receives only the data it asks for, and the person sees and approves it.
• No accounts to manage: people do not need yet another password for your forms.
• Ready before the deadline: if you must accept the wallet from the end of 2027, your forms already do.

Forms that accept only the EUDI Wallet

When you release a form that requires sign-in with a CodeB sign-in server such as phone.codeb.io, you can also tick Only with an EUDI Wallet. The sign-in then goes straight to the wallet: the visitor scans a QR code with their EUDI Wallet, or, in a browser that supports the W3C Digital Credentials API (for example current Chrome on Android with CodeB Wallet), chooses the wallet in the browser without a QR code. The form opens only when the sign-in server confirms a wallet sign-in; a password or passkey sign-in is refused for this form.

• How it is checked: the form server asks for the wallet sign-in with the OpenID Connect parameter acr_values=urn:codeb:acr:eudi-wallet and accepts only an ID token whose acr is urn:codeb:acr:eudi-wallet or urn:codeb:acr:eudi-wallet-linked (wallet linked to an existing account).
• Where: release dialog, under "Require sign-in with <server>". The option appears only when the sign-in server's OpenID Connect metadata offers the EUDI Wallet sign-in (acr_values_supported).
• What the form receives: the name from the person identification data (PID) and the attributes the sign-in server passes on to the form server (the server keeps an allow-list per form server); they pre-fill the form as with every sign-in.
• If the wallet sign-in does not succeed: the visitor sees why and a "Back to the form" button that starts the wallet sign-in again.
• Everything else stays: the sealed or signed PDF, the e-mails and forms without this option work as before.

Sign the submitted PDF in CodeB Wallet

A form that requires sign-in with a CodeB sign-in server can also ask the submitter to sign the submitted PDF with their own key in CodeB Wallet. Tick After submitting, offer to sign the PDF in CodeB Wallet in the release dialog, under "Require sign-in with <server>".

1. The person signs in, fills in and submits the form as usual. The submission is complete at this point: the sealed or signed PDF and the e-mails go out as before.
2. The person then receives an e-mail with a link. On a computer the link shows a QR code to scan with CodeB Wallet; on the phone it opens the wallet.
3. The wallet shows exactly the submitted PDF. The person confirms, and the wallet signs it with the key it holds.
4. The form server checks that the signed file is the submitted PDF with the signature added, and e-mails it to the person and the form owner. The page from the link offers it for download as well.

• Signature: advanced electronic signature (AdES, PAdES). It is qualified only when the certificate in the wallet says so. Signing is optional; whoever does not sign keeps the normal submission.
• Limits: PDFs up to 1 MB; the link works for 24 hours. The signing request runs through the signing service of phone.codeb.io with the person's own sign-in, so no extra account is needed.
• Set-up: the operator of the sign-in server registers the form server's web address for its sign-in client once ("browser origin"). Settings on the form server: "Offer signing in CodeB Wallet" and related fields in the "Remote seal and user signature" group.

CodeB Wallet: our own EUDI Wallet app

Besides accepting the state wallets, Aloaha builds its own wallet: CodeB Wallet, an EUDI Wallet app for Android, designed for eIDAS 2.0 (Regulation (EU) 2024/1183) and the EU Architecture and Reference Framework. It keeps your digital ID, driving licence and other cards on the phone, shows them in person or online, checks other people's IDs and signs PDFs. CodeB Wallet for Android is in a closed beta on Google Play for invited testers (sign-up on myeudi.app). There is no iPhone app yet; on an iPhone the CodeB web wallet runs in Safari. App and website are available in English, German, French and Maltese. CodeB Wallet is an independent wallet: not government-issued and not certified.

• Documents: person identification data (PID, including a German PID), the mobile driving licence (SD-JWT VC and ISO/IEC 18013-5 mdoc), a CodeB membership card and a Photo ID (ISO/IEC TS 23220-4), which can carry the chip data of the passport as ICAO Digital Travel Credential, only with the holder's consent. Received with OpenID4VCI from the CodeB issuer (phone.codeb.io) or by scanning the QR code of another issuer; the EU reference issuers can be chosen as well, and issuers are checked against ETSI trusted lists.
• Sign PDFs with the CodeB signing service: advanced electronic signatures (AdES) as PAdES B-T with trusted timestamp, made with the same Aloaha PDF technology as the eForms Server (Signatures). The document stays on the phone and every signature is confirmed. These are not qualified signatures. Signing requests that someone else, or an AI agent the person allowed, prepared on phone.codeb.io/sign-request are signed by scanning their QR code.
• Sign with your own signature card over NFC, the phone being the card reader: the Maltese eID card and Maltese residence cards with a signature certificate create a qualified electronic signature (QES), because the card holds a qualified certificate (CAN for the encrypted PACE connection, the signature PIN goes only to the card, the key never leaves the chip). Also supported: D-Trust Card 5.1 (QES) and 5.4 (qualified seal), the German health professional card HBA G2.1 (QES) and the health insurance card eGK G2.1 (advanced signature). The app shows whether the card certificate states a qualified signature; the qualified status comes from the card, not from the app.
• Passports and ID cards: the app reads the chip of ePassports and chip ID cards according to ICAO Doc 9303 with the CAN or the MRZ scanned by the camera, checks the issuing state's signature against the CSCA master lists and detects cloned chips. The CodeB PID provider can read the chip through the phone over an end-to-end protected channel (PACE, Chip Authentication, Secure Messaging) to issue a PID; a free CodeB account is opened the same way (a document-checked guest account, not an official identity).
• Show and check IDs: in person with ISO/IEC 18013-5 (QR code or NFC tap, data over Bluetooth Low Energy, also offline); online with OpenID for Verifiable Presentations (OpenID4VP), the standard the CodeB sign-in servers verify for your forms. Selective disclosure shares only what is needed, for example "over 18" instead of the date of birth; an online age check uses the EU proof-of-age attestation (closed beta, test credential). In verifier mode the same app checks another person's ID, including revocation.
• More: pseudonyms and passkeys, NFC access cards (CodeB Access), the phone as PKI card for Windows sign-in and a built-in 2FA authenticator (TOTP).
• Privacy and security: keys in the phone's secure hardware, PIN and optional biometrics, every share and signature confirmed. Documents and history stay on the phone, with no CodeB cloud and no ads, tracking or analytics.
• White label: issuers, banks, public bodies, associations and companies can offer the wallet under their own name, logo, colours and store listing (also not certified).

More on myeudi.app: manual, signing with the Maltese eID, D-Trust cards, free account, web wallet and changelog. Testers and white-label enquiries: info@aloaha.com.

Typical uses

• Public administration: applications and registrations that need a verified identity.
• Banks, insurers and utilities: customer onboarding and changes of address, with strong identification as required by law.
• Hotels and rentals: guest registration with verified name, date of birth and address, for example the German Meldeschein.
• Health and care: consent forms where it must be clear who signed.
• Education: enrolment with verified identity and, later, diplomas from the wallet.