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).

You can now create and manage Signature Requests across both the API and the App, no matter where it has been initiated.

A Signature Request initiated via the API will be instantly accessible and editable in the App under the corresponding Workspace.

Conversely, a Signature Request created from the App can now be fetched, updated, and managed programmatically via the API, enabling custom workflows and automation.

Learn more about this new capability in our dedicated guide section.

This service checks whether the person appears on international sanctions lists or is known as a Politically Exposed Person (PEP).

You can request a Watchlist Verification by providing a natural person's first name, last name and birth date. Verification results can be retrieved either through a Webhook event or via a dedicated endpoint.

For more details about this service, please refer to our Watchlist verification guide.

You can now control the order in which multiple Approvers validate a Signature Request by setting the parameter ordered_approvers to true in the Signature Request creation endpoint.

When enabled:

• Approvers will be notified and required to approve one after the other.
• The order is based on how Approvers are added. You can override it using the insert_after_id parameter when creating or updating an Approver.

For more details, refer to this guide.

Introducing Company Verification from a company identification file

You can now request a Company Verification by uploading a company identification file using the dedicatedInitiate a Company Verification endpoint using the file and country_code parameters in multipart format.

We currently only support : French Company Identification Documents (KBIS). See our full guide here.

New responses on the Retrieve a Company Verification Details endpoint and verification.company.done Webhook.

To reflect this change the response payloads have been updated to include a new node containing the extracted data from the document

New company verification status.

To clearly indicate a failure in the extraction, we are introducing a new company verification status called inconclusive . Inconclusive company verifications are not billed. More details can be found in our documentation here.

The following limits now apply on Sandbox during the API trial period:

• Maximum recipients per Signature Request:
  • 5 Signers
  • 5 Approvers
  • 5 Followers
• Daily sending limit:
  • 100 Signature Requests

For more details, see the Limits guide.