You can now verify whether a bank account belongs to a given personal account holder by comparing their name with the one retrieved from the bank.

To use this feature, provide the first_name and last_name fields when calling the endpoint [POST /verifications/bank_account_connections].

Yousign automatically compares these values with the bank account holder’s name and returns a failed status if the match is below the minimum acceptable level.

For more details about comparison rules and match levels, please refer to our dedicated guide.

With checks, you can now compare if a Document belongs to a given person by comparing their information with extracted data.

To use checks, add the optional checks object when requesting a new Document Analysis (see endpoint). Yousign will then compare input data with the extracted data and return a failed status if the data don't match at the minimum acceptable level.

For more details on comparison rules and match levels, please read the following guide.

We have released a new Workflow Dashboard that allows you to monitor Workflow sessions directly in our app. This feature brings visibility to processes that were previously only available via the API.

What you can do with the Workflow Dashboard:
• View all Workflow sessions with their current status (completed, awaiting, blocked).
• Track the progress of each action, including Identity Verification, Bank Account Verification, Company Verification, Proof of Address, Watchlist Screening, and Signature Requests.
• Access clear visual indicators for each step.

Who can access it?
The Workflow Dashboard is visible in the app menu for API customers and API trial users with the Admin or Owner role.
To get started, you need to create a Workflow Template.

Important note
The Workflow Dashboard provides monitoring and visibility only. Workflow orchestration still needs to be managed through API calls.

👉 Learn more in our dedicated guide section.

With this new service we provide our customers with a simple way to accurately extract data from a document.

Right now we only support two types of documents :

• French Social Welfare Card.
• French Social Welfare Certificate.

But support for more documents are coming soon. To use this service, simply call the following endpoint by specifying the type :

• social_security

For more details on the service’s capabilities and implementation, check the full guide here.

Two new Webhook events have been added to help you detect when a Signature Request notification email fails to reach a Signer or an Approver.

These events are triggered when a notification email cannot be delivered due to reasons such as an invalid email address, a full inbox, spam filtering, etc.

New available events are:

• signer.notification_delivery_failed (API reference link)
• approver.notification_delivery_failed (API reference link)

These events allow you to:

• Detect notification delivery issues.
• Implement automated retries or alternative communication methods.
• Reduce manual support efforts.

Only the delivery failure of the initial notification email to a Signer or Approver triggers a Webhook. Failures for OTP codes, Reminders, or Followers notifications are not exposed.

To learn more about this feature, please consult our documentation.

You can now orchestrate entire contracting processes with our new Workflows feature.

Workflows allow you to design complete verification and signature journeys (KYC, KYB, etc.) tailored to your needs — all steps managed by Yousign in a single flow.

How it works:

1. Our team sets up a Workflow Template based on your use case.
2. You create a Workflow Session for each customer journey using the template.
3. Run the Workflow Session by creating the necessary Verifications and Signature Requests via API.
4. Track the progress of your Workflow Sessions directly in your in-app dashboard (coming soon).

With Workflows, you benefit from a streamlined user experience, centralised data, and faster integration.

Learn more in our dedicated guide.

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.

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.