Reuse an Image Identity verification for an Advanced Electronic Signature (AES)

What is it ?

The Yousign API allows you, if you have already completed identification via the Image Identity verification endpoint, to reuse it in an advanced signature context to streamline your users' experience. Identification must be done recently.

The purpose of this feature is to perform identification prior to signing, but within the same flow for your end user.

🚧

Good to know

1. Please note that this feature is currently unavailable with Video Identity verification. Only with the Image Identity verification feature.
2. This feature differs from the ‘Pre-verify for an Advanced Electronic Signature’ function: with this feature, the Signer's identity is already verified thanks to a dedicated endpoint before you even trigger the Signature Request.

📘

What you can do

• Let a Signer skip the live identity verification step if they already passed Verify in your Workspace.
• Reference the previous verification directly on the Signer using the id of the previous identification already performed by the User
• Activate and sign as a regular AES: the Signer reviews their personal information, the document and can sign easily without an identification phase because the identification is already done via Image Identity Verification.

This feature can be very useful in the context of a KYC procedure carried out using Image Identity Verification, followed by a frictionless AES for signing.

Conditions to use the feature

📘

This feature requires activating a specific add-on and having credits dedicated to this use.  Please contact your customer representative to learn more.

This feature can only be used starting with the PRO plan and with a dedicated add-on. In Sandbox, plan/add-on restrictions are not enforced so you can test freely. Please contact your Sales representative to have the dedicated credits and to activate this feature.

How to use Pre Identity Verification with Advanced Electronic Signature ?

Image Identity verification

1. Initiate a new verification (endpoint)
   1. Ensure that the first name and last name match the identification document. This information will be frozen so that it can be reused without alteration within the AES.
2. Ensure the identification has the status ‘verified’ in order to be used (endpoint). The verification.identity_document.done webhook can be listened.
3. Once the decision has been verified,
   1. you have up to 7 days for the Signer to sign their AES. After that, the identification will be anonymized and if it is linked to an AES, ⚠️ the AES will be automatically cancelled (regardless of whether other Signer are included in the Signature Request). The credit will be consumed and will not be refunded.
   2. when an identification is attached to a Signature Request, it won’t be possible to reuse the identification for another Advanced e-Signature, a single identification can be used for a single signature only.
      1. Unless the signer has the status declined or aborted;
      2. or the Signature Request has the status canceled, rejected or declined.

Signature Request Preparation

1. Create a Signature Request (endpoint)
2. Add a Signer to the Signature Request using the dedicated endpoint, and specify the following fields in the Signer payload:
   1. signature_level must be set at advanced_electronic_signature (see API reference);
   2. firstname and lastname must be null too, the values will be retrieved from the identification. They cannot be changed after the initiation.
   3. verified_identity_id must be set with a valid previous verified Image Identity id
   4. identification_attestation_id must be null
   5. pre_identity_verification_required must be null
   6. You can set the parameter deliver_mode = none to minimize the sending of emails to the Signer
3. You can add new Signers to the Signature Request, but keep in mind that as soon as a Signer who has not yet signed and is linked to an expired ID enters the Signature process, the Signature Request will be automatically canceled for all Signers, even those who have already signed. That's why we recommend that you include few Signers, or make sure that Signers with valid IDs sign first.
4. Then, activate the Signature Request (endpoint). There will be no identification step for the Signer in our Advanced Electronic Signature flow, and the Signature will indeed have a certified advanced certificate.

Other information

1. In case of a Signature Request duplication, the vertified_identity_id won't be duplicate.

How to track the consumption

This feature requires specific credits. To monitor your usage:

• you can do so directly via the app thanks to the dedicated consumption page;
• or by calling the /v3/consumptions/detail endpoint to have the invited Signers level: advanced + identification_mode: via_verify.

Do not use the /v3/consumptions/records/identifications endpoint; it is primarily intended for QES, which charges based on identification attempts. For AES, consumption is based on invitations.