IDealWALLET|BUSINESS
Your organization, connected to the EUDI Wallet
From November 2026, evidence from an EUDI wallet must be accepted. IDealWALLET|Business makes your organization ready for this — as an issuer, as a verifier, or as both.
The date is set
From this date, evidence from an EUDI Wallet must be accepted and verified — Article 45e eIDAS 2.0
From transport and banking to education, these are explicitly named in the regulation.
Publisher, holder, auditor — most organizations are all three at once.
We give you the tools to be EUDI-ready
IDealWALLET|Business covers all three required capabilities for your organization. In one interface, with a permissions system and interfaces for integration into your processes or specialist applications.
Receive and check
A customer presents proof, you verify the signature, trust anchor, and validity - and subsequently receive the data directly into your process. An identity document becomes a process that runs automatically. Whether on the same device or via QR code from device to device.
Design your own certificates
What information does your credential contain, what can be disclosed individually, and how does it appear in the wallet? Your experts design this themselves — in the guided assistant, without a single line of code. Alternatively, you can import existing definitions.
Issue certificates
From a template or an uploaded rulebook directly into the recipient's wallet — signed with a key that makes your organization unique and can never be copied. We can integrate additional receiving systems upon request.
We take care of your certificates
Anyone wishing to request credentials needs two certificates from the EUDI ecosystem: a wallet access certificate and a registration certificate. They verify that your organization is authorized to make requests in the first place—and which information it is requesting.
Procurement, integration, renewal: In IDealWALLET|Business, this process is fully automated. No paperwork, no manual follow-up upon expiration, no files for an administrator to upload anywhere.
Your specialist department designs the digital proof
Not IT, not a service provider, not a ticket in the backlog. Whoever is professionally responsible for the evidence also designs it—guided in three steps.
Step 1: Schema - What's in it
Attributes, data types, mandatory fields, permissible values. And for each entry: whether it may be disclosed individually — so that your proof can answer "over 18" without showing the date of birth.
Step 2: Design - What the proof looks like
How it appears in the wallet: your logo, your colors, your field labels. The credential looks like it comes from you—because it does.
Step 3: Exhibition conditions - Which requirements apply
Validity period, prerequisites, requirement to submit other proof. This establishes the conditions under which it will be issued — before the first piece of proof is sent out.
Import via JSON. The system will technically verify the structure and add it to your approval process.
Are supported. For the automated process, we will clarify standards, versions, code lists, and mapping rules in advance.
Drafting, reviewing, approving, and publishing are separate rights. Those who draft do not publish alone.
Your specialist applications do not need to know anything about EUDI
IDealWALLET|Business handles all communication with the wallets. Your systems communicate via a REST interface and receive data in JSON or XML format - no protocol, no cryptography issues, no libraries in your application.
A simple link is often enough for digital processes: integrated as a microservice, a verification or issuance step can be placed exactly where it belongs in your workflow - in the application form, the ordering process, or the registration step.
QR code and deep link as data structure
Same-device and cross-device flows
Data as JSON or XML
Your data storage
Your network isolation
Your operational responsibility
Hosting the way it suits you
Fully containerized, for Kubernetes and OpenShift. Operated on-premise in your data center or hosted by us upon request. No cloud outside the EU, no third-party access, portable with no vendor lock-in.
For isolated networks
Are direct connections between the internet and your internal network prohibited? In that case, a lean component in the DMZ can handle the wallet side and pass the data to the internal network via a secure connection. Your protected network remains secure.
On-premises
IDealWALLET|Business runs entirely within your own data center. Data, keys, and operations remain in your hands — nothing leaves your premises without your authorization. Built for government agencies and companies with strict requirements regarding data residency and IT security.
IDealWALLET|Business as a Service
Want to get started without installing anything? Then we will operate IDealWALLET|Business for you — in data centers within the EU, with updates, monitoring, and support from Dresden. You take care of your records, we'll take care of the rest.
[References that cite each other]
Standards-compliant, not invented by oneself
We are implementing the protocols and formats of the European framework.
This list is written for your IT architecture. It answers a single question: Does this fit with what we mandate? What the abbreviations mean can be found in the fundamentals.