You can now verify a person’s or company’s banking information by analyzing the file containing these details (“RIB”).

For more details about this service, refer to our Document Verification guide.

📘

Beta feature

The Bank Account Details Verification feature is currently in Beta and available to a limited number of clients. If you’re interested in accessing this new product, you can join the waiting list here.

It is now possible to create a new sealed document from an existing sealed document.

Changes has been done on the POST/electronic_seal_documents endpoint.

Please consult our dedicated guide to learn more about this feature.

We now support all characters from Latin Extended-A, including Czech & Turkish alphabet (ex: ř, š, ğ, ...) in the first_name and last_name fields.

You can now collect and verify a person’s ID document using their smartphone camera.

For more details about this service, refer to our Document Verification guide.

📘

Beta feature

The Identity Verification feature is currently in Beta and available to a limited number of clients. If you’re interested in accessing this new product, you can join the waiting list here.

It’s now possible to suspend or reactivate an existing app User with the PATCH /users/{userId} endpoint.

For more details, visit our documentation.

It’s now possible to:

• Retrieve a given User by providing a User ID with the GET /users/{userId} endpoint.
• Change a User’s role from admin to member or from member to admin with the PATCH /users{userId} endpoint.

For more details, visit our documentation.

You can now request Consents from Signers directly in the Signature Request process.

This allows you to create and assign Consents to one or multiple Signers, which will be recorded in the Audit Trail for both Simple Electronic Signature (SES) and Advanced Electronic Signature (AES).

Please consult our dedicated guide to learn more about Consent Requests.

Here are the recent improvements to Workspaces in Sandbox:

• You can now create, read, update, and delete Workspaces within the Sandbox environment.
• Signature Requests must be created within a Workspace in the same environment. For example, Signature Requests in Sandbox must be created in Sandbox Workspaces.
• A default Workspace is automatically created in Sandbox when you generate your first API Key in the Sandbox environment.

For more details on managing Workspaces, please refer to the API reference.

A new parameter has been added to the webhook configuration to provide better customisation: it is now possible to specify a list workspace when a Webhook is created or updated.

The webhook will only be triggered for events happening on resources belonging to the listed workspaces.

For more information, visit our documentation.

Before this improvement, the first name and last name contained in a QES signer's certificate were necessarily the first of the first names and birth name. From now on, a certificate generate for the qualified level can contain any first names as long as it is present on the identity document used, regardless of its position on the ID document, and a usage name (such as a married name, for example) if it is also present on the identity document.

The condition remains the same: the identity declared by the Sender and the identity on the ID document must strictly match.

Find out more about parsing rules here.

You will find all information about the Yousign QES in our guide.