Digital credential implementation
Take your application live.
We implement integrations, test your application and guide go-live on the Ver.iD platform.
- Acceptance
- Test findings assessed against the agreed criteria.
- Decision
- Your organisation assesses readiness and authorises rollout.
- Platform operations
- Tasks, contacts and responsibilities for platform operations and connected systems are documented.
What is needed to go live?
We configure your application with digital credentials for real data and users. We connect the required systems and supported wallets and prepare the agreed issuance, verification and revocation processes for production. An existing design or proof of concept can be the starting point.
Before go-live, we test the processes and agree security, privacy, responsibilities and liability with the participating parties, in line with the applicable trust framework. Ver.iD manages the associated keys and certificates through the platform. You can operate the platform yourself or have Ver.iD do so; we document the tasks and support agreed. This service is delivered on the Ver.iD platform.
- Your application
- The connected systems and processes for issuance, verification and revocation.
- Agreements between parties
- Roles, responsibilities and liability in line with the trust framework.
- Platform operations
- Ver.iD handles key and certificate management. We document responsibilities for other platform operations, changes and incidents.
Our guidance.
We configure your application on the Ver.iD platform and guide the go-live. With your team and the participating parties we coordinate processes, responsibilities and support.
Setup for production.
What technical and organisational work is needed before go-live? We configure your application on the Ver.iD platform and implement the required integrations. With the participating parties, we agree roles, responsibilities and liability in line with the applicable trust framework.
We define the production data, access and acceptance criteria, and manage the associated keys and certificates through the platform. The participating parties confirm the agreements relevant to their roles. We document who arranges the integrations and any necessary approvals, and which conditions must be met before go-live.
- Data and integrations
- The data source owner confirms which data is used, who gets access and how corrections are processed.
- Roles and liability
- The participating parties confirm their responsibilities and liability agreements within the applicable trust framework.
- Platform, keys and certificates
- Ver.iD configures the application on the platform and handles the associated key and certificate management. We document responsibilities for the other platform operations.
A controlled go-live.
How do we assess whether the application is ready to go live? We test the agreed issuance, verification and revocation processes, including the check after revocation and error handling. You receive findings that let your organisation assess whether the agreed criteria have been met.
We discuss any issues and coordinate privacy and security reviews with the responsible teams. We agree whether outstanding issues require fixes or postponement. Your organisation decides whether to go live. After approval, we carry out the agreed rollout with a fallback plan in case of problems.
- Process checks
- Which findings show that issuance, verification and revocation meet the agreed criteria?
- Deviations and remediation
- Which points are resolved before go-live and how do we fall back if rollout goes wrong?
- Go-live decision
- The people responsible for approval review the findings. Your organisation confirms the go-live decision.
Operations after go-live.
Who keeps the application running and what happens when something changes or goes wrong? You can operate the platform yourself or have Ver.iD do so. Ver.iD always handles the associated key and certificate management through the platform. We agree support, incident handling and responsibilities for connected systems.
We document the arrangements for security, certificate renewal and revocation, contacts and change handling. Your organisation and other participants remain responsible for their own data, processes and systems. This makes clear who does what when handling a change or incident.
- Platform operations
- Your organisation or Ver.iD handles the agreed platform operations. Ver.iD always handles the associated key and certificate management. We document security and incident-handling agreements.
- Data and own systems
- Data source owners and other participants manage their own data, processes and systems and communicate relevant changes.
- Contacts and support
- Contacts, availability and the handling of problems and changes are agreed in advance.
How we work together.
We agree in advance what will go into production, which conditions the application must meet and who authorises go-live. We coordinate the schedule with your team, suppliers and required integrations. We also agree the handover to operations before rollout.
Your organisation reviews and decides
You explain how the application, data and processes work and share available design and testing work. You arrange contacts and access to your own systems. The people responsible for privacy, security and liability review the findings and confirm the relevant decisions. Your organisation decides on acceptance and go-live.
Our specialists implement the application
We configure the application on the Ver.iD platform, implement the agreed integrations and test how it works. We discuss findings and any remedial work or postponement with your team. After approval, we carry out the agreed rollout with a fallback plan.
Other parties confirm their contribution
Data source owners, system suppliers, wallet providers and any framework administrators confirm their integrations, conditions and support. Together we document who arranges missing access, permission or participation. Dependent production processes only go live once the necessary conditions are met.
Operations teams take over their tasks
Your organisation can operate the platform itself or have Ver.iD do so. Ver.iD always handles the associated key and certificate management through the platform. The operations teams confirm tasks, contacts and support for changes and incidents. Each party remains responsible for its own data, processes and systems.
What you receive at handover
- The agreed production setup and integrations on the Ver.iD platform.
- Acceptance-test results, outstanding issues and an agreed rollout and recovery plan.
- Agreements and documentation on platform operations and the responsibilities of your team, Ver.iD and other parties.
We complete implementation with the agreed go-live, documentation and handover to the designated operations teams. Remaining actions are assigned an owner and a next step. Ongoing operations and support follow separately documented agreements.
Practical questions
No. We can build on an existing design, earlier trial or partial integration. Together we assess what can be reused for production on the Ver.iD platform and what still needs development or testing. You do not need to repeat earlier stages with us.
- Do we need to complete an exploration or proof of concept with you first?
- No. We can build on an existing design, earlier trial or partial integration. Together we assess what can be reused for production on the Ver.iD platform and what still needs development or testing. You do not need to repeat earlier stages with us.
- Can we start if a supplier or integration is not ready yet?
- Yes, with work that does not depend on it. Together we determine which parts can start, who arranges the missing integration or permission and what this means for the schedule. The affected production processes only go live once the necessary conditions are met and your organisation approves.
- What happens if something goes wrong during rollout?
- We agree in advance when to pause the rollout, who decides and how to fall back. If problems occur, we assess with your team which recovery action is needed and whether it is appropriate to continue the rollout. We document who carries out the action and how those involved are informed.
- How much involvement is needed from our team, and what determines the costs?
- Your team contributes knowledge of processes and systems, arranges access and reviews the results. The required integrations, existing setup and coordination with other parties determine the work and costs. We start with a no-obligation conversation and agree the activities, schedule, team involvement and costs in advance. We discuss additional work before expanding the engagement.
- Who helps us with changes or incidents after go-live?
- Before go-live, we document the operations teams, contacts, availability and support. You can operate the platform yourself or have Ver.iD do so. Ver.iD always handles the associated key and certificate management through the platform. The parties involved remain responsible for their connected systems and own processes.
Which application would you like to bring into production?
Tell us what you want to do with digital credentials and which design, testing and systems are already available. In the first conversation we determine what is needed for production on the Ver.iD platform, who should be involved and which go-live and operating agreements are required.