A new parameter document_navigation_disabled is now available in the Custom Experience creation endpoint POST /custom_experiences (link to API reference)

  • By default, this parameter is set to false, meaning navigation buttons are displayed to let Signers quickly switch between documents - if there is more than one document uploaded - in a Signature Request;
  • If this parameter is set to true, then a Signer must scroll through all of the documents in order to sign a document.

This setting exists in the Custom Experience to enable you to manage the navigation flexibility for documents in the signature flow that you want to give to your signers.

For more details about Custom Experience, read our dedicated guide section.

Driving licenses are temporarily no longer supported in the Identity Document Verification.

This change was introduced to maintain verification accuracy while we work on a more robust solution.

Impact of this change

  • Any verification request with the parameter type=driver_license now returns a 400 Bad Request error.
  • If a driver’s license is submitted during a verification, it will return an inconclusive status with error code IDDV_1408. These verifications will not be billed.

We recommend checking your current integration to ensure they do not allow driver_license as a document type.

Other supported document types remain unchanged and fully functional.

You can now add a Signature Date Field to your documents. It is automatically filled when a signer completes their signature and can be customized to display different date and time formats. It may also be used to show a calculated date (e.g., signature date + 3 months).

For more details, please refer to our dedicated guide.

We have introduced new error codes to provide more precise feedback during the QES identification process. These errors help Signers understand the reason for a failure and successfully retry the identification.

  • document_version_not_accepted: the document is not compatible, or its version does not meet security standards.
  • document_not_original: the provided document is not the original (e.g., photo or photocopy).
  • face_identity_inconsistency: a mismatch was detected between the ID photo and the recorded video.
  • altered_materials: a technical compliance issue was detected during video capture (e.g., non-original device, webcam, or operating system).

For more details, please refer to our dedicated guide.

You can now integrate an IBAN check solution, that directly checks if the account exists with the bank themselves.

We leverage the Sepamail bank network to do account checks directly with the bank in charge of the account. You can confirm key banking data, such as the account holder’s name, IBAN, account status, etc…

It is possible to perform a check on natural person or a legal person.

For more details on this service and guidance on performing optimal verifications, please refer to our Bank account lookup guide.

You can now integrate an open-banking and IBAN check solution, that is directly connected to the banks in Europe.

We provide a link-based flow , allowing the user to connect to their bank on mobile or desktop. Through this process, you can retrieve key banking data, such as the account holder’s name, IBAN, account status, etc…

It is possible to perform a natural person or legal person check.

For more details on this service and guidance on performing optimal verifications, please refer to our Bank account connection guide.

We have improved how you access the Sandbox environment in the Yousign application.

Previously, you had to enable Sandbox mode on each individual page. Now, you can switch globally to Sandbox mode using a new toggle in the side menu.

This change makes navigating and testing in the Sandbox environment much easier.

For more details on how to use Sandbox mode, please consult our dedicated help center article.