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.

The maximum length for Webhook endpoints (URLs) has been extended to 1024 characters.

This update applies whether Webhooks are configured from the App or via the API.

To learn more about Webhooks, please consult our dedicated guide.

You can now request a Bank Account Verification Lookup directly from a bank account details file in pdf.

By adding the file body parameter in your request, Yousign will extract the IBAN from the file and perform the Bank Account Verification Lookup from the extracted IBAN number (see the Bank Account Lookup Verification endpoint)

For more details, read our dedicated guide section.

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.

You can now initiate the verification of a person's Proof of Address document.

Verification results can be retrieved either through a Webhook event or via a dedicated endpoint.

For more details on this service and guidance on performing optimal verifications, please refer to our Proof of Address Verification 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.

Available from July 21

When a Qualified Electronic Signature (QES) attempt fails due to a mismatch between the Signer’s provided name and the name extracted from their ID document, you will now be able to retrieve the extracted names and reuse them to retry the identification.

Here’s how it works:

• When the identification fails, you will continue to receive the webhook **signer.identification_failed** (link to API reference) as is already the case.
• In the case of a first name or last name error, and after the Signer clicks on the consent button to share the extracted information, you'll receive the signer.identification_blocked (link to API reference) webhook containing the extracted first name (expected_first_name) and last name (expected_last_name).
• Use the Unblock Signer endpoint (link to API reference):
  POST /signature_requests/{signatureRequestId}/signers/{signerId}/unblock_identification. It's possible to use this endpoint without any update on the Signer's names just to unblock the Signer (but the Signer will risk triggering the same error again due to a mismatch of first name and/or last name).
• Update the Signer with the extracted names using the dedicated endpoint (link to API reference):
  PATCH /signature_requests/{signatureRequestId}/signers/{signerId}

⚠️ Please note: Once this feature goes live on July 21. For our existing customers, we will wait for your approval before giving you access to the feature, to avoid blocked Signers without the possibility of unblocking them with the right correction.

For more details, refer to our dedicated guide section (link to guide).