Verify
Verify digital credentials.
In Ver.iD Studio, choose which data to request from wallets. The platform checks the credentials’ origin and validity and returns the result to your application.
Bring digital credentials into your process.
During verification, someone uses a wallet to share data from digital credentials with your organisation, for example about a qualification or membership. The platform checks the origin, digital signature and validity before your application uses the result.
In Ver.iD Studio, you set up data requests for different processes. The verification overview shows what happened during each request. Ver.iD handles the wallet exchange and manages the required access certificates, registration certificates and associated keys.
One managed connection across wallets and trust frameworks.
Ver.iD takes care of managing the required access certificates, registration certificates and associated keys. The platform handles the exchange and technical verification across different wallets and trust frameworks.
Your organisation uses these capabilities through one platform. Your team does not have to organise wallet connections and specialist certificate and key management separately.
More about trust frameworks- Access and registration certificates
- The platform manages the certificates your wallet connection requires.
- Associated keys
- Ver.iD manages these keys and their use.
- Wallet exchange
- The platform handles the connection and technical checks.
Configure data requests for each process.
Configure multiple data requests in Studio for different processes or applications. For each request, choose which data to ask for and how it maps to your application’s fields.
Your applications start the configured requests and process the results. This lets you manage different use cases from the same environment.
Find suitable digital credentials
| Attribute |
|---|
| Registration number |
| Candidate reference |
| Exam code |
Keep track of every data request.
Use the verification overview to see when your data requests were carried out and how they progressed. It contains only information about execution, such as timestamps and statuses. The data shared from the wallet is not stored in this overview.
This helps you understand what happened within the platform and investigate issues in context.
Explore the integration- Data request
- Which configured data request was carried out.
- Timestamps
- When events occurred during the verification.
- Status
- Whether the verification is ongoing, completed or interrupted.
What you need for verification.
A clear data request
Decide which data your process needs and how you will use it. Choose the digital credentials that fit those needs.
Trusted issuers and relevant rules
Decide which issuers you trust and under which conditions you accept their credentials. Follow the rules that apply to your use case or trust framework.
A connected application
Your application starts the data request, validates the returned result and determines the next step. Also define what happens when someone cancels sharing or required data is missing.
Need guidance on configuration or integration? Explore Services
Practical questions about Verify.
Studio shows which wallets and data are available for your organisation and environment. Check the combination you want to use there. Supporting a format does not mean that every credential or issuer is accepted.
- Where can I find the available wallets and data?
Studio shows which wallets and data are available for your organisation and environment. Check the combination you want to use there. Supporting a format does not mean that every credential or issuer is accepted.
- Is verification the same as logging in?
No. Verification provides data for your process. Login also establishes a connection to an account or session. Use the separate wallet login integration for that; your application remains responsible for account linking and access rules.
Explore Login- Does the verification overview store shared wallet data?
No. The verification overview contains only information about execution, such as timestamps and statuses. The data shared from the wallet is not stored in this overview. Your own application determines how it processes and, if needed, stores the data it receives.
- Which registrations and certificates are needed?
Ver.iD manages the required access and registration certificates and associated keys for your wallet connection. Participation as a relying party in the EUDI ecosystem involves registration and certificate requirements. The steps depend on your role, Member State and configuration. Ver.iD’s own provision of access and registration certificates depends on Member State authorisation and the service statuses below.
Relying party access certificates
PlannedNot yet availableRelying party registration certificates
PlannedNot yet available
What data does your process need?
Discuss your data needs, accepted sources and application. Together, we identify the available integration and checks that fit.