OpenID4VC Verification sessions now have a new requestRetrieved state, allowing you to react to the user having retrieved the verification request.

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.verification.requestRetrieved event. You can read more in the webhooks documentation. If you want to use the new event but only subscribe to specific events for your webhooks, you should update the webhook to also listen to the new request retrieved event.

You can now import X.509 certificates where the hash algorithm uses a different length than the key size. This means you can import an X.509 certificate with a P-256 that is signed using ECDSA with SHA-384 or SHA-512 hashing algorithms. ECDSA certificates signed by Paradym will still always use ECDSA with SHA-256 when using the P-256 key type.

With this release, we are expanding the OpenID4VC Issuance capabilities when using an Attribute Provider. The Attribute Provider can now defer the issuance of a credential, in case it is not ready yet. For more information, please check the Attribute Providers documentation.

To make getting started with verifications easier, we've added pre-made presentation templates for verifying Person Identification Data (PID) and Mobile Driving Licences (mDL).

You can select these templates directly from the dashboard when creating a presentation template, and adjust the requested attributes to fit your use case.

The default expiration time for OpenID4VC verification requests and issuance offers has been increased from 5 to 15 minutes.

For both cases, you can now optionally provide an expiration time using the new expirationInMinutes field when creating a verification request or credential offer.

When importing an externally signed certificate for a Certificate Signing Request, you can now include intermediate certificates that form part of the certificate chain. This allows you to work with certificate authorities that use multi-level PKI hierarchies, where the leaf certificate is not directly signed by the root certificate.

Intermediate certificates can be provided via the parentCertificates field when importing a certificate throug hthe API. When improting a certificate through the dashboard, it can be provided as a PEM-encoded chain in the certificate field. The certificates should be ordered from leaf-adjacent to root-adjacent. Any root certificate included in this list will be ignored.

To learn more, please check out the Certificates documentation.

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.