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 documents only – no risk code or CDD Report is generated.
• In addition to checking the status in webhook notifications, you can check the status of a specific signature workflow any time via a Get signature status request.
• In addition to checking the status in webhook notifications, you can check the status of a specific signature workflow any time via a Get signature status request.
Statuses
Possible statuses include:
Status | Description | Action |
---|---|---|
new | The workflow is successfully created. | Wait for pending status. |
pending | The client is eligible for a signature. | Wait. The signature flow starts automatically. |
selfie_required | We need a selfie from the client to check they are 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 Status codes: 3105 , 3541 , 3550 | Upload a selfie within 24 hours or the status changes to error . |
kyc_required | A new Identity Verification case is required for the client because they didn't pass one or more eligibility checks. Status codes: 140 , 1021 , 1035 , 1039 , 1201 , 1202 , 3204 , 3311 , 4110 , 4145 | Create a new workflow that includes IDV and QES . |
user_consent_required | The client is eligible for a signature and can proceed to the document approval step. | Get the signature details, and then approve the documents to sign. If you don't approve the documents within: • 2 hours: The signature flow expires, you receive a 422 error, and you must create a new workflow for a signature only. • 24 hours: The status changes to error . |
confirmation_required | The document approval step was successful and the client can proceed to the signature confirmation step. | Confirm the signature. If you don't make the request within: • 1 hour: The signature flow expires, you receive a 422 error, and you must create a new workflow for a signature only. • 24 hours: The status changes to error . |
Pending flow onlypending_verification | The client has completed the signature flow, but we are still processing the related Identity Verification case. | Wait for the next status notification. |
Pending flow onlyinvalid_signature | The extracted certificate details don't match the confirmed details from the related Identity Verification case. Status codes: 3311 | Create a new workflow for a signature only. |
signed | The signed documents are available. | Download the signed documents. |
error | An error occurred. If the system can recover after the error, the status changes to a previous status. Status codes: 6001 , 6002 , 6003 , 6004 , 6005 , 6006 , 6007 , 6008 , 6009 , 6010 | If the system can't recover, create a new workflow for a signature only. |
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 code | Description | Action |
---|---|---|
140 | We found a potential sanctions hit. | Create a new workflow that includes IDV and QES . |
1021 | The ID document type in the successful Identity Verification case isn't supported for this nationality. | Create a new workflow that includes IDV and QES . |
1035 | The client isn't eligible for a signature. | You can't retry. |
1201 | The Identity Verification case isn't compliant. | Create a new workflow that includes IDV and QES . |
1202 | The client isn't eligible for a signature because the related Identity Verification case status is completed_unacceptable . | You can't retry. |
3105 | The signature flow selfie isn't the same person as in the Identity Verification case selfie. | Upload a new selfie. |
3204 | The ID document used in the successful Identity Verification case is expired. | Create a new workflow that includes IDV and QES . |
3311 | Pending verification flow: The certificate details don't match the ID document. | Create a new workflow for a signature only. |
3541 | The device model used for the signature flow doesn't match the one used for the Identity Verification case. | Upload a selfie. |
3550 | The phone number of the device used for the signature flow doesn't match the one used for the Identity Verification case. | Upload a selfie. |
4110 | We found a confirmed sanctions hit. The client isn't eligible for a signature. | You can't retry. |
4145 | The client's geolocation is in a prohibited country. | Ask the client to retry from a non-prohibited country. |
6001 | There was a fatal error while creating the certificate. | Create a new workflow for a signature only. |
6002 | There was an error while creating the certificate. | Re-approve the documents to sign. |
6003 | There was a communication error while creating the certificate. | Re-approve the documents to sign. |
6004 | There was a fatal error while signing the document(s). | Create a new workflow for a signature only. |
6005 | There was an error while signing the documents. | Re-confirm the signature. |
6006 | There was a communication error while signing the documents. | Re-confirm the signature. |
6007 | Pending verification flow: There was a fatal error while countersigning the documents. | Create a new workflow for a signature only. |
6008 | The signature flow timed out. | Create a new workflow for a signature only. |
6009 | The signature flow wasn't initialized. | Create a new workflow for a signature only. |
6010 | The client's mobile phone number is invalid. | Create a new workflow for a signature only and provide a valid mobile phone number. |
Updated 20 days ago