Issue
Issue digital credentials.
Set up issuance in Ver.iD Studio and issue digital credentials from your own systems to wallets.
Your data as a digital credential.
Issuance lets you provide data from your organisation as a digitally signed credential, such as confirmation of membership or completion of a course. The recipient stores the credential in a wallet and can share it later. Other parties can check where the credential came from and whether its contents have changed.
A trust framework sets out who may issue credentials, the responsibilities of each party and which credentials they trust. Electronic attestations of attributes under eIDAS 2.0 are also subject to legal requirements for the issuer and the issuance process.
In Ver.iD Studio, you configure which credentials you issue, which data they contain and which wallets you issue them to. Your systems supply the data and start issuance. The platform handles the exchange, signing and management of the associated keys and certificates.
One integration for different wallets.
Wallets can use different data formats and issuance protocols. Ver.iD handles these differences for the supported wallets in your configuration. Your application supplies the data, starts issuance and receives the result.
The platform handles the exchange with the wallet and guides the user through receiving the credential. You can use embedded elements in your application or the Ver.iD gateway.
Secure signing that meets the applicable requirements.
Ver.iD handles signing and manages the associated keys and certificates in line with the security requirements of your issuance setup. Specialist security hardware protects the signing keys.
Your organisation uses the signing infrastructure it needs through the platform. Ver.iD operates and manages that specialist infrastructure.
Managed by Ver.iD; the private key stays within the management environment.
Keep control of every issuance.
Your system determines which data is issued and who may receive the credential. Ver.iD links the supplied data to the issuance session and performs the technical checks required by the selected configuration.
Your application receives the issuance result and links it to the original request.
- Source record
- Alex Jansen
- Verified recipient
- Alex Jansen
Only issue if the person is employed by Acme.
HR records: active employment
The verified identity must match the employee record.
Alex Jansen matches this employee record
Follow the agreed binding to the identity and receiving wallet.
Identity and wallet linked according to the rulebook
Ready to issue
What you need to issue credentials.
A suitable rulebook
The credential’s meaning, data and rules must be defined. You can use an existing rulebook.
Source data and authority to issue
Your organisation supplies the data and determines who may receive the credential. A trust framework may set conditions for participation and issuance.
A configured integration
In Studio, you configure the credential, wallets and data mapping. Your application starts issuance requests and processes the result.
Need guidance on design or implementation? Explore Services
Practical questions about issuance.
- Which wallets can receive my credential?
That depends on the digital credential, data format and issuance configuration. In Studio, you choose from the wallets available for your organisation’s issuance setup. Availability may differ between testing and production.
Explore the wallet directory- What happens when the source data changes?
A signed credential is not edited after issuance. Issue a new credential for changed data. During configuration, decide how to handle the earlier credential and which revocation options its type supports. Revocation does not automatically remove the credential from the wallet.
Explore credential management- What do you record about the issuance process?
Only information about execution, such as timestamps and statuses. The data sent to the wallet in the digital credential is not stored in this record.
- Is a credential in an EUDI Wallet always qualified?
No. EUDI includes different credential categories. A qualified electronic attestation of attributes, or QEAA, requires an issuance service qualified for that purpose. Ver.iD does not currently provide QEAA issuance.
More about eIDAS 2.0
Discuss your issuance.
Which data do you want to provide, and where should the evidence be usable? In a first conversation, we look at your application, existing design and system integration to establish the configuration you need.