In short: The CodeB Wallet is a wallet for the European Digital Identity (EUDI wallet) under eIDAS 2.0 for Android phones, developed by Aloaha Limited (Malta) – the maker of ZUGFeRD Pro. It stores identity data (PID), the mobile driving licence and membership cards, presents them in person or online, checks other people's IDs and signs PDFs: advanced (AdES) via the CodeB signing service, or qualified (QES) with the Maltese eID or a D-Trust signature card that you simply hold against the phone. The app is not a government wallet and is not certified; access is by invitation. Official website: myeuid.app.
The CodeB Wallet at a glance
| Feature | CodeB Wallet |
|---|---|
| Type | Wallet for the European Digital Identity (EUDI) under eIDAS 2.0 (Regulation (EU) 2024/1183), developed according to the EU Architecture and Reference Framework (ARF) |
| Manufacturer | Aloaha Limited, Pembroke, Malta – PKI, PDF and digital signatures since 2003; CodeB is a trademark of Aloaha Limited |
| Platform | Android with NFC |
| Credentials | Personal identification data (PID, including the German PID), mobile driving licence (mDL), CodeB membership card |
| Signing | AdES via the CodeB signing service; QES with the Maltese eID or residence permit and the D-Trust Card 5.1; qualified seal with the D-Trust Card 5.4 |
| Privacy | Documents and history stay on the phone, no CodeB cloud, no ads, no tracking |
| Languages | English, German, Maltese (follows the phone's language, can be changed under Settings → Language) |
| Countries | Built for the EU framework; initial focus on Malta, Germany and Austria |
| Access | by invitation (request via info@aloaha.com); not certified |
| For businesses | Available as a white-label app with your own name and logo |
What the CodeB Wallet can do
| Function | Details |
|---|---|
| Store credentials | PID (also the German PID, separate from the EU PID), mobile driving licence and membership card as SD-JWT VC and ISO mdoc, issued via OpenID4VCI; choose an issuer in the app or scan the issuer's QR code; a document held in both formats appears as one card |
| Present in person | by QR code or NFC tap, data transfer via Bluetooth Low Energy according to ISO/IEC 18013-5 – also offline; both Bluetooth roles for more readers |
| Present online | via OpenID4VP; every request is confirmed with PIN or biometrics |
| Share only what is needed | selective disclosure, e.g. "over 18" without the date of birth (SD-JWT VC and mdoc) |
| Verify IDs | verifier mode as an ISO/IEC 18013-5 reader for another person's ID, driving licence or age, with revocation check and a clear result; nothing is stored; back-to-back verification via NFC without a QR code |
| Trust list | manage trusted issuer certificates; the CodeB certificate is built in, others can be imported |
| Read passports and ID cards | read the chip according to ICAO Doc 9303 with the CAN or the MRZ (camera); the issuing state's signature and the authenticity of the chip are checked |
| PID from the ID chip | the PID provider reads the chip through the phone over an end-to-end encrypted channel (PACE, Chip Authentication, Secure Messaging); the phone can neither read nor alter the data |
| Sign PDFs via the signing service | PAdES B-T with a trusted timestamp via the CodeB signing service – advanced electronic signature (AdES); every signature is confirmed by the user |
| Sign PDFs with a signature card | hold your own signature card against the phone via NFC; the private key never leaves the chip; the app shows whether the card's certificate is qualified (details below) |
| Signing requests from websites | sign PDFs from a website via QR code or "Open in CodeB Wallet"; several documents are confirmed once and signed together, the signed PDFs go straight back to the website |
| Free CodeB account | create it in the app with a passport or ID card (chip check) and an e-mail code; 5 signatures of your own PDFs per day plus a test PID; presenting and verifying work without an account |
| History, status and reminders | on-device history (what was shared or signed, when and with whom), automatic status and revocation checks, renewal before expiry, local reminders without sending data |
| Accessibility | TalkBack, very large text and reduced animations (European Accessibility Act) |
Qualified PDF signatures with the Maltese eID and D-Trust cards
The CodeB Wallet turns the Android phone into a card reader: no computer, no USB reader, no browser plug-in. The card itself creates the signature; the app embeds it as PAdES (ETSI EN 319 142) with a trusted timestamp, so common PDF programs can validate it. Only a hash value is sent to the timestamp service – the PDF stays on the phone.
| Card | Result |
|---|---|
| Maltese eID card and Maltese residence permit with a signing certificate | qualified electronic signature (QES) – fully tested with real cards |
| D-Trust Card 5.1 (Standard RSA and Multi ECC) | qualified electronic signature (QES) of a person |
| D-Trust Card 5.4 (Standard RSA and Multi ECC) | qualified electronic seal of an organisation |
| German health professional card (HBA G2.1) and electronic health card (eGK G2.1) | signature with the card's certificate; with the eGK an advanced signature (AdES) via the authentication certificate – details on myeuid.app |
Generation 4 D-Trust cards are not supported because they lack a contactless interface; the app recognises them and points you to a card reader on a computer. A new card with a transport PIN must first be switched to your own PIN with the issuer's tools.
How to sign a PDF with your signature card
- On the home screen, tap Sign → Select document and choose the PDF.
- Review the document and tap Sign with signature card.
- Enter the 6-digit card access number (CAN) printed on the card – the app suggests the last CAN that worked.
- Hold the card flat against the back of the phone until signing has finished (from Android 14 the app shows where the NFC antenna is).
- Enter the signature PIN. The card creates the signature, the app adds the timestamp.
- The "Document signed" confirmation shows the card used and whether its certificate is qualified; save or share the PDF.
Security: The CAN only opens the encrypted channel (PACE); the PIN travels only over this channel to the chip and is not stored by the app. A wrong PIN is never retried automatically, and the remaining attempts are shown. If the card is removed too early, nothing is signed – the app continues as soon as the card is back in place. Blocked PINs are reset by the card issuer (for the Maltese eID, Identity Malta), not by the app. The qualification of the signature comes from the card and its certificate – the app itself is not certified.
CodeB Wallet and ZUGFeRD: signing e-invoices
The CodeB signing service used by the wallet is the same service through which the Aloaha ZUGFeRD SDK signs finished ZUGFeRD PDFs with SignPDFRemote (German) – as do the ZUGFeRD GUI, the PDF Viewer and the command-line tool zugcmd. The result is an advanced signature (AdES, PAdES B-B to B-LTA).
- Automatic invoice signing: you do not need the app to sign from your own application – the SDK talks to the signing service directly, server to server.
- Individual PDFs on the phone: with the wallet you sign a PDF yourself – via the signing service, or qualified with your Maltese eID or D-Trust card.
- Signing requests: on a website (on the CodeB test server at
phone.codeb.io/sign-request.html) you upload PDFs and invite signers; they scan the QR code or tap "Open in CodeB Wallet", sign on their phone, and at the end everyone receives the link to the signed PDF.
Privacy and security
- Documents and history stay on the phone – there is no CodeB cloud.
- The keys are held in the phone's secure hardware and protected by PIN or biometrics.
- No ads, no tracking, no analytics in the app; the myeuid.app website sets no cookies and loads nothing from third parties.
- The history shows when a document was shared and with whom; you can ask a verifier to delete data or report a verifier.
Standards
eIDAS 2.0 and ARF, OpenID4VCI, OpenID4VP, ISO/IEC 18013-5, SD-JWT VC, ISO mdoc, PAdES Baseline B-T (ETSI EN 319 142), ETSI Trusted Lists, ICAO Doc 9303 (PACE, BAC, Chip and Active Authentication, Passive Authentication), ISO/IEC TS 23220-4 with ICAO DTC Type 1, ISO/IEC 7816-4/-8 with CAdES/PAdES and qcStatements for card signatures, and ETSI TS 119 461 v2.1.1 (designed for the extended level of identity proofing, not certified).
Access by invitation
The CodeB Wallet is developed continuously (changelog). Access is by invitation: the app on Google Play is available to invited users whose Google account uses the approved e-mail address. To request access, e-mail info@aloaha.com.
White label for businesses
Organisations can offer the wallet as their own app: with their own name, logo, colours and store listing, preconfigured issuers, documents and services. Signing uses your own signing service or NFC signature cards; Aloaha in Malta provides updates and maintenance. The white-label version is not certified either. Enquiries to info@aloaha.com with the subject "CodeB Wallet White Label".
Further pages on myeuid.app
- CodeB Wallet – home page (also in German and Maltese)
- User guide
- Signing PDFs with the Maltese eID
- Signature and seal cards from D-Trust
- German health professional and health cards
- Free CodeB account
The detailed presentation of the CodeB Identity Wallet on YouTube:
Playing connects to YouTube (Google) – privacy · watch on YouTube
Frequently asked questions
What is the CodeB Wallet?
The CodeB Wallet is an app for Android phones for the European Digital Identity (EUDI wallet) under eIDAS 2.0, made by Aloaha Limited, Malta. It stores identity data (PID), the mobile driving licence and membership cards, presents them, checks other people's IDs and signs PDFs.
Can I create qualified signatures with the CodeB Wallet?
Yes, with a suitable signature card: the Maltese eID (also residence permits with a signing certificate) and the D-Trust Card 5.1 produce a qualified electronic signature (QES), the D-Trust Card 5.4 a qualified electronic seal. The card is held against the phone via NFC. Signatures via the CodeB signing service are advanced electronic signatures (AdES).
Is the CodeB Wallet a government EUDI wallet?
No. The CodeB Wallet is developed according to eIDAS 2.0 and the ARF, but it is not a government wallet and it is not certified.
Which phones does the CodeB Wallet run on?
On Android phones; NFC is needed for signature cards and for reading ID chips.
What does the CodeB Wallet cost?
myeuid.app does not state a price for the app itself. Presenting and verifying documents work without an account; the free CodeB account allows 5 signatures of your own PDFs per day via the signing service.
Do I need the CodeB Wallet to sign ZUGFeRD invoices?
No. The Aloaha ZUGFeRD SDK signs finished ZUGFeRD PDFs with SignPDFRemote directly server to server via the CodeB signing service (AdES). You only need the wallet if you want to sign a PDF yourself on your phone.
Where does my data stay?
On your phone. Documents and history are not stored in a CodeB cloud, the keys are held in the device's secure hardware, and the app contains no ads and no tracking.
How do I get access to the CodeB Wallet?
By e-mail to info@aloaha.com. Access is by invitation; the app on Google Play is available to invited users whose Google account uses the approved e-mail address.