Proof of concept with digital credentials
Test your use case with us.
We build a complete trial environment and test your use case with demo data, from issuance to revocation.
Testing exam registration
Test source and issuance
ACME University issues a fictional registration according to the rulebook and agreed issuance conditions.
Receiving and sharing
The test participant receives the credential in a test wallet and shares the requested data.
Verification
The test venue checks the credential according to the agreed trust and verification rules.
Revoke and check again
ACME revokes the credential. On a new verification, we check that it is no longer accepted as valid.
What does this proof of concept involve?
In this proof of concept, we set up a complete trial environment for your use case with digital credentials. We bring together trust agreements, the rulebook, test wallets and the participating organisations’ roles. We can build on existing agreements and develop any missing elements together.
Using demo data, we work through the full lifecycle: issuance, receipt, sharing, verification and revocation. We also check what happens after revocation or when a step fails. You see how the agreements, participants and technology work together, and what is still needed for a pilot or go-live. This service is delivered on the Ver.iD platform.
- Agreements and rulebook
- Meaning, data and rules for issuance, verification and maintenance.
- Parties and roles
- Data source owners, issuers, test participants and receiving parties with agreed responsibilities.
- Test environment and test wallets
- The agreed systems, wallets and demo data to test the entire journey.
Our guidance.
Our specialists help bring the parts together, walk through the entire journey and determine what is needed next.
A complete trial environment.
How do we bring all the elements together in a working trial? Together we develop the required trust agreements and rulebook, and configure the agreed systems and test wallets. Your team can then experience the complete use case in one trial environment.
Existing agreements, definitions and systems can be the starting point. Together we determine the missing parts and who fulfils each role. We can start within your organisation and involve other parties once their participation and test capabilities are agreed. Ver.iD handles key and certificate management for the trial environment.
- Trust agreements and rulebook
- ACME University defines what a registration proves and which rules apply to issuance, verification and revocation.
- Roles involved
- The student administration provides the source data, ACME issues and a test participant shares the credential with the test venue.
- Trial setup
- A test source, issuance and verification environment, test wallets and demo data to walk through the full lifecycle.
The entire journey.
How does this work for the participating parties, from issuance to revocation? We guide participants through issuing, receiving, sharing and verifying digital credentials with demo data. Revocation and the subsequent check are also part of the trial. You experience who does what and what each step delivers.
Together we also test expired credentials, incorrect data, refusal and outages. For each scenario we record what happens and which systems and wallet versions are used. We make clear which parts were actually tested and where a simulation is used.
The complete journey and exceptions
- Issuing and receiving
- The test participant receives the registration credential in the test wallet.
- Sharing and verifying
- The test venue checks the shared data according to the agreed rules.
- Revoking and verifying again
- After revocation, the credential is no longer accepted as valid at a new check.
- Expired credential
- The validity check rejects the credential.
- Participant refuses
- Sharing stops without transferring data.
- Incorrect data or issuer
- Invalid proof is rejected according to the agreed checks.
- Source or service unavailable
- The process returns an error and follows the agreed recovery path.
| Scenario | Expected response |
|---|---|
| Issuing and receiving | The test participant receives the registration credential in the test wallet. |
| Sharing and verifying | The test venue checks the shared data according to the agreed rules. |
| Revoking and verifying again | After revocation, the credential is no longer accepted as valid at a new check. |
| Expired credential | The validity check rejects the credential. |
| Participant refuses | Sharing stops without transferring data. |
| Incorrect data or issuer | Invalid proof is rejected according to the agreed checks. |
| Source or service unavailable | The process returns an error and follows the agreed recovery path. |
From trial to real-world use.
What do we still need to arrange to put this into use? You receive the agreed trial setup and findings, with insight into agreements, technology and organisational choices still to be developed. Together we determine the appropriate next step: adjust, prepare a pilot or stop.
We discuss outstanding questions, dependencies and who can take the next steps. A pilot or go-live requires further work on security, any necessary approvals and day-to-day operations. We agree the scope and delivery of that work separately.
- Experiences from the trial
- What worked in the trial setup and where did test participants encounter problems?
- Still to be developed
- Which agreements, integrations, security measures and operating tasks need further development?
- An appropriate next step
- Plan changes, prepare a pilot or decide to stop. Identify outstanding decisions, dependencies and who is responsible.
How we work together.
We agree in advance what your team wants to learn from the trial, which scenarios to include and when the trial is complete. You can start with what is already available. Together we identify the missing elements, the participants’ involvement and the schedule.
Your team brings practical knowledge and participants
You explain your use case and share available agreements and information about your data, processes and systems. Together we arrange the test access and demo data needed. You appoint a contact and involve people who can work through and assess the process.
Our specialists set up the trial
Our specialists develop the agreed trust arrangements and rulebook and set up the trial environment on the Ver.iD platform. We guide participants and record findings. Ver.iD handles the associated key and certificate management through the platform.
Participating parties confirm their contribution
We document in advance which parties actually participate, which systems we connect and what we simulate. Each party confirms its contribution and reviews the agreements within its role. We identify which conclusions still depend on missing participation or confirmation.
What you receive at completion
- A complete trial setup with the agreed systems and test wallets.
- The rulebook and trust agreements for the trial, with documented roles and open decisions.
- Findings on the complete lifecycle and exceptions, with next steps and the agreed handover.
We discuss the findings and outstanding questions with your team. The trial ends when the agreed scenarios have been run and the results handed over. Your organisation decides whether to make adjustments, prepare a pilot or stop.
We agree in advance which files, configuration and access you retain afterwards. Continued use and support are agreed separately. The trial uses demo data; a pilot or go-live requires separate agreements covering security, necessary approvals and operations, among other things.
Practical questions
Yes. We can use existing agreements and systems and develop the missing elements within the agreed trial. At the start, we determine the design work needed, where the trial will run and the access and demo data we need to arrange together.
- Can we start without a completed rulebook or our own test environment?
- Yes. We can use existing agreements and systems and develop the missing elements within the agreed trial. At the start, we determine the design work needed, where the trial will run and the access and demo data we need to arrange together.
- Can we begin before all our partners are involved?
- Yes. We can first run the trial within your organisation and involve partners when they are able to participate. We agree which roles are represented and which elements we simulate. The findings identify what still needs to be tested with the missing partners.
- What if the trial does not produce the expected result?
- We investigate whether the cause lies in the agreements, technology or process. We document the findings and remaining uncertainties. Your team can then decide whether adjustments, further investigation or stopping would be appropriate. Additional work is agreed separately.
- How much time will our team need to contribute, and what will the trial cost?
- Your team contributes domain knowledge, works through scenarios and reviews the findings. The time and costs depend on the design work, integrations, scenarios and coordination with participants. We start with a no-obligation conversation and agree the activities, schedule, costs and your team’s involvement in advance.
- Can we continue with the same environment after the trial?
- We agree this in advance, including which files and configuration you receive, how long access remains available and what support is included. For a pilot or go-live, we determine which elements can be reused and which additional setup and assessments are needed. A working trial is not yet a production environment.
Which use case would you like to test with us?
Tell us what you want to do with digital credentials and which agreements, systems and participants are already in place. Together we define the trial environment needed to test the full lifecycle.