EUDI Wallet provider: who supplies EU digital identity wallet infrastructure
Organisations evaluating the EU Digital Identity Wallet usually start from a product question and end at a supplier question: who actually builds and runs this. Credenco is a Dutch supplier of EUDI Wallet infrastructure, founded in 2021, and covers all three roles of the credential flow rather than one corner of it.
What an EUDI Wallet provider actually supplies
Procurement in this market is rarely for one product. Four capabilities have to be in place before a single credential moves, and a supplier either covers them or leaves them to you.
Issuance
Turning a record you already hold, a diploma, a registration, an employment fact, into a signed credential a wallet will accept. This is the part a verifiable credentials issuance API does, and the interface for it is OpenID4VCI.
Issuance ServiceHolding
Organisations receive credentials too: licences, certificates, mandates. They need somewhere to keep them, and a way to present them again when a counterparty asks. A person uses a phone wallet for this; an organisation needs a service.
Holder ServiceVerification
Asking for exactly the attributes you need, then checking the signature, the issuer and the revocation status before acting on what you were given. Getting this wrong is the expensive failure mode, because it looks like it works.
Verification ServiceTrust and lifecycle
Keys, revocation, status publication and the registrations that make a signature mean something to a stranger. This is the work that is easy to leave out of a pilot and impossible to leave out of production.
Business WalletThe full triangle: issue, hold, verify
Most suppliers in this market occupy one corner of the credential flow. That is workable until the corners have to meet: the issuer signs in one format, the verifier expects another, revocation lives somewhere neither of them reads, and the integration cost lands on the organisation that bought all three.
Credenco covers issuing, holding and verifying in one product line, with the Business Wallet tying them together. An organisation does not have to assemble a trust chain from three suppliers and then own the seams between them. Where you only need one corner, you can still take just that one.
What to ask a digital identity wallet vendor
These six questions separate suppliers faster than a feature list does. They are worth asking of every vendor on your shortlist, including us.
- Which of the three roles do you build yourself, and which do you resell? The answer decides who you call when the flow breaks between two of them.
- Which specifications do you implement, by name and version, and where can we see them running against someone else’s wallet?
- Where does the data sit, who operates the signing keys, and what leaves our jurisdiction?
- What happens when a credential has to be withdrawn? Revocation is the question that exposes whether a demo was a product.
- What is already in production or in a named pilot, and may we speak to the organisation running it?
- If we leave, what stays usable? Credentials issued in an open format remain verifiable without you; credentials in a proprietary one do not.
Standards and interfaces
Credenco is an OpenID4VCI provider for issuance and implements OpenID4VP for presentation. Credentials are issued as SD-JWT and mdoc, following the W3C Verifiable Credentials data model. The Business Wallet is eIDAS 2.0 compliant, DIIP v5 conformant and verified against the WE BUILD interoperability test bed. The verifiable credentials issuance API, the guides and the full API reference are public, so an integration team can read the interface before anyone signs anything.
Where this is already running
In a market this young, a named comparable deployment carries more weight than a feature comparison. These are public, and each one has its own write-up.
The sector pages set out what changes in each market, with the regulation that drives the timing.
Three ways to start
Try it yourself
Create a Business Wallet and issue and verify a credential without talking to anyone first.
Scoped pilot
One credential type, one counterparty, one flow proven end to end before anything widens.
Talk it through
Bring the process you want to change and we will tell you whether credentials are the right instrument for it.
Technical deep dive
This page explains what the technology does and who it affects. Our developer documentation covers the implementation itself: the messages, the fields and the worked examples an integration team needs.
Read the technical documentationRelated terms
Frequently asked questions
What is an EUDI Wallet provider?
In everyday use the phrase covers two different things. Member states provide the citizen wallet that eIDAS 2.0 obliges them to offer, and they are the only ones who can. Separately, organisations need software to issue credentials into those wallets, to hold the credentials the organisation itself receives, and to verify what is presented to them. That second kind of supplier is what most organisations are looking for when they search for an EUDI Wallet provider, and it is what Credenco is.
Do we have to be a government to use this?
No. Any organisation that issues documents, receives them, or has to check them can use the same infrastructure. Credenco works with public bodies, but also with banks, employers, healthcare organisations and supply chains. The sector decides which credentials matter, not whether the technology applies.
What is the difference between a wallet and a verifiable credentials platform?
A wallet is where a credential is kept, usually on a phone that belongs to a person. A verifiable credentials platform is the infrastructure around it: what creates the credential, what signs it, what publishes its revocation status, and what checks it when it is presented. An organisation almost always needs the platform. Whether it also needs a wallet of its own depends on whether it receives credentials as well as issues them.
Which standards does Credenco implement?
OpenID4VCI for issuance and OpenID4VP for presentation, with credentials in SD-JWT and mdoc format and the W3C Verifiable Credentials data model. The Business Wallet is eIDAS 2.0 compliant and DIIP v5 conformant, and is verified against the WE BUILD interoperability test bed. Nothing in the stack is a proprietary format.
How do we avoid supplier lock-in?
Ask any supplier which parts of what they deliver are described in a public specification and which are their own invention. Credentials issued through open standards stay readable by any conformant wallet or verifier, so the credentials you have issued keep working if you change supplier. That is a property of the standards, not a promise from us, which is why it is worth asking every vendor the same question.
Can we start small?
That is the normal route in this market. Most organisations start with one scoped use case, one credential type and one counterparty, then widen it once the flow has been proven end to end. You can also create a Business Wallet yourself and try issuing and verifying before talking to anyone.