You can now create multiple credential templates for the same credential type. This works for AnonCreds (reusing an existing schema), mDOC (using the same doctype) and SD-JWT VC (using the same VCT).

This enables you to have mulitple variants of the same credential type, which can be useful for e.g. using different templates and branding for different university diplomas, but still using the same credential type. It can also be useful when drafting up changes to a credential you're issuing, and creating a new template to not impact any issuance flows using the old template.

Example issuance templates for PID and mDL

The documentation has been extended with example issuance templates. Initially we have added the following credentials:

• Issue Person Identification Data (PID) as SD-JWT VC based on the EU Architecture Reference Framework.
• Issue ISO 18013-5 Mobile Driving License as mDOC based on ISO 18013-5.

Both templates also contain example payloads so you can easily use test your new credential template with the Paradym Wallet. Once you have created a credential template, you can also easily create a presentation template based on the credential template from within the dashboard.

If you want us to add specific credential templates, please let us know in the Paradym Slack!

The link contained within the QR code of the authorizationRequestQrUri now correctly includes the client_id and client_id_scheme parameters, resolving interoperability issues with the Paradym Wallet.

You can now issue mDOCs via OpenID for Verifiable Credentials, with X509 certificates!

Start by creating a new X509 root certificate for issuance in the "Trust" page within the dashboard, or using the Certificates API.

When creating an mDOC credential template, you will now need to select the X509 root certificate you created. The root certificate will automatically be used to generate document signing certificates for the issuance of the mDOC credentials.

The expiration for OpenID4VP requests has been increased from 2 minutes to 5 minutes.

The increased expiration time helps prevent failed presentations due to the user taking a bit longer to go through the presentation flow.

You can now issue SD-JWTs via OpenID4VC with X509 certificates!

Start by creating a new X509 root certificate for issuance in the "Trust" page within the dashboard, or using the new Certificates API.

When creating an SD-JWT credential template, you will now be able to select the X509 root certificate you created. The root certificate will automatically be used to generate document signing certificates for the issuance of the SD-JWT credentials.

The mDOC debugger now shows a document selector if a DeviceResponse contains multiple mDOCs. Previously only the first document was selected.

We have also improved the error handling for the mDOC and SD-JWT VC debuggers, showing the internal error message if the parsing failed. Since the tool is used for debugging, it makes sense to display the internal error message.

Try it out in our mDOC debugger or SD-JWT VC debugger.

You can now sign your OpenID4VC presentation requests with X509 certificates!

Users can now create a X509 root certificate for the verification use case in the "Trust" page within the dashboard, or using the new Certificates API.

The root certificate will automatically be used to generate signing certificates for the requests.

Resolved several issues with the invitation page showing an error screen after an invitation was successfully scanned.

The invitation page now correctly handles all states and shows whether an invitation is completed, expired, or could not be found.

For privacy reasons we will show the successful completion screen on the invitation page even if the issuance or verification failed. The completion screen is mostly to indicate to the user that the invitation has been processed by the wallet.

You can now filter DIDComm issuance and verification session based on the didcommConnectionId and didcommInvitationId in the API.

Try it out with the Retrieve DIDComm issuance sessions and Retrieve DIDComm verification sessions endpoints.

Users on the Pro or Custom tier can now create new projects, and edit the members of a project directly from within the dashboard!

While this feature has been available through the API for a while, the same functionlity is now also available in the dashboard.

To create a new project from the dashboard, select the project selector in the top-left corner, and click the + icon. Managing project members can be done in the in the Members page of the Settings tab within a project.

Read more about it in the add projects and members documentation.