With this release, we're introducing two new features that allow you to integrate your OpenID4VC issuance flow with existing systems: Authorization Servers, and Attribute Providers.

Authorization servers are external OAuth 2.0 servers that you can integrate with Paradym to add an additional layer of authentication during the credential issuance process. When an authorization server is configured, users must authenticate with that OAuth 2.0 server before they can receive their credentials. This allows you to gate credential issuance behind your own authentication system or a third-party identity provider.

Attribute providers are external HTTPS endpoints that Paradym can call during OpenID4VC issuance to fetch attribute values for a credential. This lets you keep your source of truth in existing systems and populate credentials dynamically, instead of sending all attribute values when creating an offer. This avoids storing any attribute data in Paradym at all.

To learn more about these features, please check out the Authorization Servers and Attribute Providers documentation.

Paradym now supports full localization for credential templates, attributes, and issuer/verifier profiles. You can provide translations in multiple locales to improve the user experience across different regions.

With localization support, you can translate:

• Credential template names and descriptions: Display credential types in the user's preferred language (e.g., "University Degree" / "Universitair Diploma")
• Credential attributes: Translate individual claim names (e.g., "First Name" / "Voornaam")
• Issuer and verifier display names: Show your organization's name in multiple languages

All localized metadata is automatically included in OpenID4VCI issuer and OpenID4VP verifier metadata, allowing wallets to detect and display content in the user's language without additional configuration.

Localization is supported for SD-JWT VC and mDoc credentials. You can configure a default locale on your profile, and add translations for over 80 supported languages using BCP47 language tags (e.g., "nl-NL", "de-DE", "fr-FR").

To start using localization, check out the Localization documentation or configure it through the API or dashboard when creating or updating credential templates and profiles.

The deprecated did property has been removed from the project profile API response. This property was deprecated over a year ago.

All DIDs associated with your project can be queried through the DIDs API.

OpenID4VC Issuance sessions now have a new offerRetrieved state, allowing you to react to the user having retrieved the credential offer.

This can be useful if you want to hide the deeplink or QR after is has been clicked/scanned, to prevent the user from scanning it multiple times.

The new state value can be subscribed to through webhooks using the new openid4vc.issuance.offerRetrieved event. You can read more in the webhooks documentation. If you want to use the new event but only subscribe to specific events for you webhooks, you should update the webhook to also listen to the new offer retrieved event.

A few issues have been fixed that were preventing users from creating and revoking API Keys.

Encryption keys in OpenID4VP authorization requests client_metadata.jwks.keys array now contain the alg parameter (ECDH-ES) when encryption is enabled on a request. This helps wallet implementations find the correct key for encryption.

An issue has been resolved where mediator events were not correctly delivered from the mediator instance to the Paradym webhook sender, which resulted in mediated didcomm messages not correctly being delivered.

To better integrate with external certificate authorities Paradym now supports defining the required capabilities when creating a certificate signing request. The certificate signing request will be adjusted based on capabilities, and validated against the requested capabilities when the certificate is imported.

Currently one a single signMdl capability is supported, which can only be used for issuerSignCredential certificates and is enabled by default for this certificate type.

The signMdl capability enables signing ISO 18013-5 mDLs, and ensures the mdlDS extended key usage is present in the certificate signing request and imported certificate. When this capability is enabled, the imported certificate must adhere to Document Signer Certificate requirements as defined in ISO 18013-5 Table B.3.

This capability only covers signing mDLs. Without this capability on the certificate, you cannot issue mDLs. ISO 23220-4 is a pending standard that defines generic mDoc signing capabilities, and introduces a new mdocDS extended key usage. In the future an additional capability will be added for this, which will impact non-mDL signing.

Paradym now supports version 1 of the OpenID for Verifiable Credentials suite of specifications.

Existing projects will keep using the existent version (from now on called "legacy"), which is based on draft 21 of the OpenID for Verifiable Presentations specification, and drafts 11 through 14 of the OpenID for Verifiable Credential Issuance specification.

New projects will automatically be configured to use version 1. The OpenID4VC version can be changed on a per project basis in the dashboard under Settings → Profile. Old projects can also be upgraded by updating the configuration.

Upgrading to V1 of OpenID4VC is a one-time operation, and cannot be reverted. If migration is not possible but already want to use V1 you can create a new project. In the future all legacy projects will be migrated to V1.

Some notable changes when updating to V1 of OpenID4VC:

• Response encryption is enabled by default for OpenID4VP. Previously, this was only the case for when requesting mDOCs.
• SD-JWT VCs and associated Token Status Lists signed with X509 certificates do not include an iss field anymore.
• SD-JWT VCs, associated Token Status Lists, and OpenID4VP requests signed with an X509 certificate do not include the root certificate in the x5c header anymore to adhere to HAIP requirements.
• OpenID4VP requests signed with an X509 certificate now use the x509_hash client id prefix instead of the x509_san_dns to adhere to HAIP requirements.

Paradym now supports creating Certificate Signing Requests (CSRs) for externally signed certificates. This allows you to use certificates signed by external certificate authorities instead of only using root certificates created within Paradym.

The certificate signing requests are based on PKCS#10, a common format for requesting an external signature on a certificate.

Certificate signing requests can be created for both issuer (issuerSignCredential) and verifier (verifierSignRequest) leaf certificates through the API or dashboard. Once your CSR is signed by an external certificate authority, you can import the resulting certificate back into Paradym. Certificate signing requests are automatically removed after 30 days if no certificate has been imported.

To start using certificate signing requests, check out the Trust -> My Certificates tab in the Paradym dashboard, Create a certificate signing request through the API, or read more in the Certificates documentation.

Creating externally signed certificates is not available in the Free tier, and only available to the Pro and Custom tiers.