Requirements:
- API key pair
- DEV environment
- Finances added to your environment
Dummy auto results
dummyStatus, which defines the dummy session’s auto result.
| JSON key | Type | Description |
|---|---|---|
dummyStatus | String | Auto status of the verification. Possible values: APPROVED, DENIED, SUSPECTED, EXPIRED. See status vocabulary for details. |
Request example
Response example
A successful API call returns a JSON response with ascanRef that can be used to add a dummy manual status.
Dummy manual result
- The client’s verification must already be created. If not, generate a new token with
dummyStatusfirst. - For an approved verification, you need to provide both
FACE_MATCHandDOC_VALIDATEDstatuses.
Request parameters
| Key | Type | Description |
|---|---|---|
scanRef | String | A unique string identifying a client verification. |
manualFaceMatchResult | String | Dummy manual face status. Possible values: FACE_MATCH, FACE_MISMATCH, NO_FACE_FOUND, TOO_MANY_FACES, FACE_TOO_BLURRY, FACE_UNCERTAIN, FACE_NOT_ANALYSED, FACE_NOT_CHECKED, FACE_ERROR, AUTO_UNVERIFIABLE, FAKE_FACE. See status vocabulary for details. |
manualDocumentValidity | String | Dummy manual document status. Possible values: DOC_VALIDATED, DOC_INFO_MISMATCH, DOC_NOT_FOUND, DOC_NOT_FULLY_VISIBLE, DOC_NOT_SUPPORTED, DOC_FACE_NOT_FOUND, DOC_TOO_BLURRY, DOC_FACE_GLARED, MRZ_NOT_FOUND, MRZ_OCR_READING_ERROR, BARCODE_NOT_FOUND, DOC_EXPIRED, COUNTRY_MISMATCH, DOC_TYPE_MISMATCH, DOC_DAMAGED, DOC_FAKE, DOC_ERROR, AUTO_UNVERIFIABLE, DOC_NOT_ANALYSED, DOC_NAME_ERROR, DOC_SURNAME_ERROR, DOC_EXPIRY_ERROR, DOC_DOB_ERROR, DOC_PERSONAL_NUMBER_ERROR, DOC_NUMBER_ERROR, DOC_DATE_OF_ISSUE_ERROR, DOC_SEX_ERROR, DOC_NATIONALITY_ERROR. See status vocabulary for details. |