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’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
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.
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.
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.
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 Verificationendpoint using the file and country_code parameters in multipart format.
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.
Using Advanced Electronic Signature (AES) always required users to upload an identity document before signing.
As a result, integrating Yousign in user flows that already required an identity verification step was creating friction since Signers were asked to upload their identity documents twice.
Pre-Identity Verification for AES, aims to provide a simpler way to integrate Yousign in complex flows by allowing you to verify an identity before giving signers access to the signing flow, all while maintaining Yousign’s secured and certified AES. This way, signers have to upload their identity documents only once in your entire business flow.
What's new?
A new signer parameter
You can now use the pre_identity_verification_required parameter when creating a Signer via the Signer creation endpoint or when updating a Signer to indicate that a signer will go through a pre-verification process.
POST /signature_requests/{signatureRequestId}/signers/{signerId}/identity_verification
to submit and verify an identity document before the signature process.
📘 To learn how to implement this in your flows, the conditions for using it, and how the signing flow changes when using pre-verification, check out our full guide :
Pre-identity verification guide for AES (link to guide).