Qualified Electronic Signature Statuses
Integrations guide
This page sets out possible statuses and explanatory status codes for Qualified Electronic Signature workflows.
Notes
• The output for Qualified Electronic Signature is the signed document(s) only – no risk code or CDD Report is generated.
• In addition to checking the status of a specific signature workflow in webhook notifications, you can make Get signature status requests as required.
• In addition to checking the status of a specific signature workflow in webhook notifications, you can make Get signature status requests as required.
Statuses
Possible statuses include:
Status | Guidance |
---|---|
new | |
Description: The workflow is successfully created. Action: Wait for pending status. | |
pending | |
Description: The client is eligible for a signature. Action: Wait. The signature flow starts automatically. | |
selfie_required | |
Description: We need a selfie to check the client is the same person as in the related Identity Verification case, which was processed: • More than 24 hours ago, or • Less than 24 hours ago but the device model is different Action: • SDK integration: Handled by the SDK. • API integration: Upload a selfie within 24 hours or the status changes to error . Status codes: 3105 3541 3550 | |
kyc_required | |
Description: A new Identity Verification case is required because the client didn't pass one or more eligibility checks. Action: Create a new workflow that includes Identity Verification and Qualified Electronic Signature. Status codes: 140 1021 1035 1039 1201 1202 3204 3311 4110 4145 | |
user_consent_required | |
Description: The client is eligible for a signature and can proceed to the Document approval step. Action: • SDK integration: Handled by the SDK. • API integration: Get the signature details, and then approve the documents to sign. If the documents aren't approved within 2 hours, the signature flow expires: • SDK integration: If the client tries again, an error message is displayed. • API integration: You receive a 422 error and must create a new workflow for Qualified Electronic Signature only. If the documents aren't approved within 24 hours, the status changes to error and you must create a new workflow for Qualified Electronic Signature only. | |
confirmation_required | |
Description: The Document approval step was successful and the client can proceed to the Signature confirmation step. Action: • SDK integration: Handled by the SDK. • API integration: Confirm the signature. If the signature isn't confirmed within 1 hour, the signature flow expires: • SDK integration: If the client tries again, an error message is displayed. • API integration: You receive a 422 error, and must create a new workflow for Qualified Electronic Signature only. If the signature isn't confirmed within 24 hours, the status changes to error and you must create a new workflow for Qualified Electronic Signature only. | |
pending_verification | |
Pending verification flow only | Description: The client has completed the signature flow, but we are still processing the related Identity Verification case. Action: Wait for the next status. |
invalid_signature | |
Pending verification flow only | Description: The extracted certificate details don't match the confirmed details from the related Identity Verification case. Action: Create a new workflow for Qualified Electronic Signature only. Status code: 3311 |
signed | |
Description: The signed documents are available. Action: Download the signed documents. | |
error | |
Description: An error occurred. If the system can recover after the error, the status changes to a previous status. Action: If the system can't recover, create a new workflow for Qualified Electronic Signature only. Status codes: 6001 6002 6003 6004 6005 6006 6007 6008 6009 6010 |
Status flow diagram
The pathways for statuses are as follows:
Status codes
Statuses can be accompanied by one or multiple of the following status codes:
Status | Guidance |
---|---|
140 | |
Description: We found a potential sanctions hit. Status: kyc_required Action: Create a new workflow that includes Identity Verification and Qualified Electronic Signature. | |
1021 | |
Description: The ID document type in the successful Identity Verification case isn't supported for this nationality. Status: kyc_required Action: Create a new workflow that includes Identity Verification and Qualified Electronic Signature. | |
1035 | |
Description: The client isn't eligible for a signature. Status: kyc_required Action: None. You can't retry. | |
1201 | |
Description: The Identity Verification case isn't compliant. Status: kyc_required Action: Create a new workflow that includes Identity Verification and Qualified Electronic Signature. | |
1202 | |
Description: The client isn't eligible for a signature because the related Identity Verification case status is completed_unacceptable . Status: kyc_required Action: None. You can't retry. | |
3105 | |
Description: The signature flow selfie isn't the same person as in the Identity Verification case selfie. Status: selfie_required Action: • SDK integration: Handled by the SDK. • API integration: Upload a new selfie. | |
3204 | |
Description: The ID document used in the successful Identity Verification case is expired. Status: kyc_required Action: Create a new workflow that includes Identity Verification and Qualified Electronic Signature. | |
3311 | |
Pending verification flow only Description: The certificate details don't match the ID document. Status: invalid_signature Action: Create a new workflow for Qualified Electronic Signature only. | |
3541 | |
Description: The device model used for the signature flow doesn't match the one used for the Identity Verification case. Status: selfie_required Action: • SDK integration: Handled by the SDK. • API integration: Upload a new selfie. | |
3550 | |
The phone number of the device used for the signature flow doesn't match the one used for the Identity Verification case. Status: selfie_required Action: • SDK integration: Handled by the SDK. • API integration: Upload a new selfie. | |
4110 | |
Description: We found a confirmed sanctions hit. Status: kyc_required The client isn't eligible for a signature. Action: None. You can't retry. | |
4145 | |
Description: The client's geolocation is in a prohibited country. Status: kyc_required Action: Ask the client to retry from a non-prohibited country. If the status of the related Identity Verification case is: • completed_acceptable : Create a new workflow for Qualified Electronic Signature only. • inconsistent_data or invalid_data : Create a new workflow that includes Identity Verification and Qualified Electronic Signature. | |
6001 | |
Description: There was a fatal error while creating the certificate. Status: error Action: If the status of the related Identity Verification case is: • completed_acceptable : Create a new workflow for Qualified Electronic Signature only. • inconsistent_data or invalid_data : Create a new workflow that includes Identity Verification and Qualified Electronic Signature. | |
6002 | |
Description: There was an error while creating the certificate. Action: • SDK integration: Handled by the SDK. • API integration: Re-approve the documents to sign. | |
6003 | |
Description: There was a communication error while creating the certificate. Status: error Action: • SDK integration: Handled by the SDK. • API integration: Re-approve the documents to sign | |
6004 | |
Description: There was a fatal error while signing the document(s). Status: error Action: If the status of the related Identity Verification case is: • completed_acceptable : Create a new workflow for Qualified Electronic Signature only. • inconsistent_data or invalid_data : Create a new workflow that includes Identity Verification and Qualified Electronic Signature. | |
6005 | |
Description: There was an error while signing the documents. Status: error Action: • SDK integration: Handled by the SDK. • API integration: Re-confirm the signature. | |
6006 | |
Description: There was a communication error while signing the documents. Status: error Action: • SDK integration: Handled by the SDK. • API integration: Re-confirm the signature. | |
6007 | |
Pending verification flow only Description: There was a fatal error while countersigning the documents. Status: error Action: Create a new workflow for Qualified Electronic Signature only. | |
6008 | |
Description: The signature flow timed out. Status: error Action: If the status of the related Identity Verification case is: • completed_acceptable : Create a new workflow for Qualified Electronic Signature only. • inconsistent_data or invalid_data : Create a new workflow that includes Identity Verification and Qualified Electronic Signature. | |
6009 | |
Description: The signature flow wasn't initialized. Status: error Action: If the status of the related Identity Verification case is: • completed_acceptable : Create a new workflow for Qualified Electronic Signature only. • inconsistent_data or invalid_data : Create a new workflow that includes Identity Verification and Qualified Electronic Signature. | |
6010 | |
Description: The client's mobile phone number is invalid. Status: error Action: If the status of the related Identity Verification case is: • completed_acceptable : Create a new workflow for Qualified Electronic Signature only and provide a valid mobile phone number. • inconsistent_data or invalid_data : Create a new workflow that includes Identity Verification and Qualified Electronic Signature. |
Updated 6 months ago