DID / VC · eIDAS 2.0 system builds
We build the capability for an institution to issue and verify credentials itself, from the ground up. The standards choices — SD-JWT VC or mdoc, which DID method — are decided with you rather than handed to you.
Services
Connecting to the systems you already run, meeting the regulation that applies to you, getting through the test suites. It is also the work that produced Veritra.
We build the capability for an institution to issue and verify credentials itself, from the ground up. The standards choices — SD-JWT VC or mdoc, which DID method — are decided with you rather than handed to you.
Verification added to a service that already exists. OID4VP presentation verification goes into your sign-in or identity-check flow, and we build the endpoint that accepts requests coming from a wallet.
We help an implementation get through the OpenID Foundation conformance suites. The traps we hit taking 62 issuer, 10 verifier and 12 wallet modules through ourselves are what you are buying.
On-chain work in an identity context: an agent identifier held on-chain and bound to a verified operator identity, or entitlement to a tokenised asset expressed as a credential. We design and implement both.
Kick-off
Goals and constraints first. What we will not build gets settled before what we will.
Requirements
Credential schemas, trust model, systems to integrate with. Written down.
Design · build
Progress shared weekly.
Verification
Conformance suite and integration testing. Results are submitted as they come out.
Handover
Operator training and incident procedures included.
Contract form
Fixed scope — priced against deliverables
Working mode
Remote-first · kick-off and handover on site
Maintenance
Annual option · includes standards revisions
An undefined scope is fine at this stage. We start by agreeing what not to build.