EU Jurisdiction · Made in Malta · eIDAS 2 / ARF 3.0

Malta EU ID Wallet software

A complete European Digital Identity Wallet stack built by Aloaha Limited in Malta: a personal wallet your users carry, a Business Wallet your accounting team uses, and a Wallet Relying Party verifier registered with the EU reference registry. Ships on-premise or Malta-managed. No US-cloud dependency. Aligned with eIDAS 2 (Regulation (EU) 910/2014 as amended by 2024/1183) — which covers the full European Economic Area (30 countries: 27 EU by December 2026 + Norway, Iceland, Liechtenstein following with roughly one additional year) — and the Architecture Reference Framework 3.0.

Why Malta. Malta is inside the EU single market and inside eIDAS jurisdiction, with an English-language legal system, an active Data Protection Commissioner (IDPC), and a mature financial-services regulator. Personal Identification Data issued here is recognised by every EU Reference Wallet without additional bilateral arrangements. Data stays inside EU jurisdiction end-to-end — no US-cloud, no CLOUD Act exposure.

Three products, one stack

Personal EU Wallet

A wallet your users install (web PWA + native iOS/Android). Receives PID + mDL + PhotoID + EHIC + PDA1 issuance from any European catalogue issuer. Presents credentials via OpenID for Verifiable Presentations to any WRP.

Business Wallet

A wallet your accounting / operations team uses. Signs invoices with CSC v2 to PAdES-B-LTA (GoBD-compliant), verifies incoming credentials, sits inside your existing SSO. On-premise or Malta-managed.

Wallet Relying Party verifier

An OpenID4VP verifier registered with registry.serviceproviders.eudiw.dev. Accepts credentials from any EU Reference Wallet. Publishes a WRP certificate + intended-use certificate per ARF 3.0 §5.

All three surfaces share one identity, one crypto module, one audit trail, and one deployment story. Buy the stack, deploy one surface, extend to the others when you're ready.

What you can issue + verify today

Issuance (as PID Provider + non-qualified EAA Provider)

  • Personal Identification Data (PID) — the core eIDAS 2 credential. Issued as urn:eudi:pid:1 per ARF 3.0. Accepted by the EU Reference Wallet without additional trust anchors when consumed inside our jurisdiction.
  • Mobile Driving Licence (mDL) — ISO/IEC 18013-5 profile.
  • PhotoID, EHIC (health insurance), PDA1 (posted-worker), Diploma, Learning Credential, Employee Attestation, MSISDN, Power of Representation, IBAN, Tax number, Loyalty, Seafarer, Reservation — the 27-credential EU reference issuer catalogue.

Verification (as Wallet Relying Party)

  • OpenID for Verifiable Presentations — the ARF-mandated presentation protocol. Registered WRP entry at /eudi-registration.html with live proof surface (Wallet Provider attestation, OpenID Federation entity statement, EU Trusted List, DID document, machine-readable RP metadata).
  • haip-vp:// scheme — the EU reference verifier scheme.
  • DCQL queries for selective disclosure.
  • Formats: dc+sd-jwt, mso_mdoc, jwt_vc.

Signing (GoBD-compliant, eIDAS AdES)

PAdES B-B / B-T / B-LT / B-LTA via the Cloud Signature Consortium v2 API, the personal EU Wallet, or the Business Wallet. Every signature carries an RFC 3161 qualified timestamp under a QTSP on the EU LOTL — the immutability signal that lets German GoBD (BMF letter 2019) recognise the archive without a WORM appliance. See /gobd-compliant-invoice-signing.html for the practitioner guide.

PAdES-B-LTARFC 3161CSC v2eIDAS AdESGoBD

Deployment

  • On-premise. Windows Server + IIS + our SIP bridge. Deploy inside your own datacentre or your own Azure/AWS EU region. You keep the keys, we ship the software.
  • Malta-managed. Multi-tenant, hosted from our Malta datacentre. Per-tenant isolation (each tenant is its own IIS site, its own App_Data directory, its own signing key). You get the SLA; we get the ops burden.
  • OEM / white-label. Embed the wallet + issuer stack in your product; see /wallet-oem.html.

Independent proof surfaces

Every claim on this page is machine-verifiable from a third party, not just our word:

Frequently asked questions

What is Aloaha's Malta EU ID wallet software?

Aloaha's Malta EU ID wallet software is a European Digital Identity Wallet stack built by Aloaha Limited in Malta. It consists of three products on one stack: a Personal EU Wallet for your users, a Business Wallet for accounting and operations teams, and a Wallet Relying Party verifier. All three share one identity, one crypto module, one audit trail and one deployment story, so you can deploy one surface and extend to the others later.

Is Aloaha's EU ID wallet software eIDAS 2 compliant?

Aloaha's EU ID wallet software is aligned with eIDAS 2 (Regulation (EU) 910/2014 as amended by 2024/1183) and with the Architecture Reference Framework (ARF) 3.0. Aloaha issues PID as a PID Provider and other credentials as a non-qualified EAA Provider, and its signatures are eIDAS advanced electronic signatures (AdES).

Why is Aloaha's EU ID wallet software built in Malta?

Aloaha's EU ID wallet software is built in Malta because Malta is inside the EU single market and inside eIDAS jurisdiction. Malta also has an English-language legal system, an active Data Protection Commissioner (IDPC) and a mature financial-services regulator. Data stays inside EU jurisdiction end-to-end, with no US-cloud dependency and no CLOUD Act exposure.

Which credentials can Aloaha's Malta EU wallet stack issue?

Aloaha's Malta EU wallet stack issues Personal Identification Data (PID) as urn:eudi:pid:1 per ARF 3.0 and a Mobile Driving Licence (mDL) on the ISO/IEC 18013-5 profile. It also covers the 27-credential EU reference issuer catalogue, including PhotoID, EHIC, PDA1, Diploma, Learning Credential, Employee Attestation, MSISDN, Power of Representation, IBAN, Tax number, Loyalty, Seafarer and Reservation.

How does Aloaha's Wallet Relying Party verifier work?

Aloaha's Wallet Relying Party verifier is an OpenID for Verifiable Presentations verifier registered with the EU reference registry at registry.serviceproviders.eudiw.dev. It accepts credentials from any EU Reference Wallet, uses DCQL queries for selective disclosure, supports the haip-vp:// scheme, and handles the dc+sd-jwt, mso_mdoc and jwt_vc formats. It publishes a WRP certificate and intended-use certificate per ARF 3.0 §5.

How can Aloaha's EU ID wallet software be deployed?

Aloaha's EU ID wallet software ships in three ways. On-premise runs on Windows Server and IIS in your own datacentre or your own Azure or AWS EU region, and you keep the keys. Malta-managed is multi-tenant hosting from Aloaha's Malta datacentre with per-tenant isolation (own IIS site, own App_Data directory, own signing key). OEM / white-label lets you embed the wallet and issuer stack in your own product.

Can Aloaha's EU wallet stack sign documents for German GoBD archiving?

Yes, Aloaha's EU wallet stack signs PDFs as PAdES B-B, B-T, B-LT or B-LTA via the Cloud Signature Consortium v2 API, the Personal EU Wallet or the Business Wallet. Every signature carries an RFC 3161 timestamp from a QTSP on the EU LOTL, which the page describes as the immutability signal that lets German GoBD recognise the archive without a WORM appliance. The signatures are eIDAS advanced electronic signatures (AdES).

How can I independently verify Aloaha's EU wallet claims?

Aloaha's EU wallet claims can be checked against public, machine-readable endpoints. These are the EU Reference Registry entry at registry.serviceproviders.eudiw.dev, the OpenID Federation entity statement at /.well-known/openid-federation, the EU Trusted List at /.well-known/trust-list.xml, the Wallet Provider attestation at /.well-known/wallet-provider.jwt and the RP metadata at /.well-known/eudi-relying-party.json.

How do I get a quote for Aloaha's Malta EU ID wallet software?

You can request a quote for Aloaha's Malta EU ID wallet software through the contact page. Procurement teams can start with the EUDIW procurement readiness page, which maps the stack to typical tender requirements, and developers can read the wallet API reference, the CSC v2 signing API and the Business Wallet API.