Status Error Codes
For every verification, we run a series of third party APIs to do KYC, KYB, AML, phone number fraud detection etc. This series of steps is called a workflow. If for some reason a workflow fails, we set the status of that verification session as FAILED and give a reason for the failure under status_reasons. Following are the possible codes for those status_reasons
| Status Reason Code | Description |
|---|---|
| THIRD_PARTY_RESPONSE_ERROR | Unable to parse third-party response. |
| THIRD_PARTY_API_FAILED | Third Party API Failed. |
| DOCUMENT_NOT_SUPPORTED | Third Party API does not support given document. |
| COUNTRY_NOT_SUPPORTED | Third Party API does not support given country. |
| REGISTRY_NOT_AVAILABLE | Unable to connect to a registry that we can normally service. |
| API_DATA_REQUIREMENTS_NOT_MET | Missing required fields to run the API. |
| WORKFLOW_CONFIG_ERROR | Workflow failed due to invalid workflow conditions. |
| REQUEST_TOO_LARGE | The request entity too large than limits defined by server. |
| CUSTOM_ERROR_CODE | In this case, a custom error message is returned explaining more details. |
Updated 12 months ago