link
Developer Pages

# Get process


Page contents

This page describes the Get process service. You use this service to retrieve important information about a verification process:

  • The provider used (Onfido, ReadID etc.).
  • The process type (attended, unattended, selfie, video etc).
  • The status of the process (accepted, rejected etc.).
  • When the process started and when it was last updated.
  • Provider-specific information about different verification features used in the verification, e.g. facial similarity, document verification etc.
  • The final result with end-user information like first name, last name and date of birth.

# Response structure

The information in the Get process message response depends on the provider that was used and the current status of the process. For example, you will see different information in a process that is pending than in a process that is finished, e.g. accepted.

The structure of the obtained JSON in the response is divided into three main areas:

click-to-zoom

Here, Onfido is used as an example. The order of the elements may vary from provider to provider.

# Process information

This message area contains general information about the process, e.g. its internal unique ID, the provider that is used for performing the verification and the dates the process is created and last updated. This information is generated as soon as the process is created.

Here is a response example of Get process as soon as the process was created:

    {
        "provider": "onfido",
        "status": "pending",
        "processId": "4e48363a-37cb-4cff-8f91-afc9e52271fc",
        "createdAt": "2019-09-19T22:10:56Z",
        "updatedAt": "2019-09-19T22:10:56Z"
    }

For more detailed descriptions about status, see:

For all field descriptions, see the OpenAPI documentation.

# Status

The status of a process can either be final or not final:

  • pending and processing are not final, meaning the process is not yet finished and the status will still change.
  • accepted, rejected, inconclusive, canceled, failed are all final, meaning the process is now finished and, therefore, its status will not suffer any more changes.

# Not final

Status value Description
pending The process is created but the verification has not yet started.
processing The verification of the data in the process has started but is not yet finished.

# Final

Statuses that are final can be broken into finished with success or finished without success:

  • accepted, rejected, inconclusive mean the process was finished successfully, i.e. it was possible to obtain a result on the identity verification.

  • canceled and failed mean that the process ended without success, i.e., it was not possible to get a result.

Status value Success No success Description
accepted x The verification is finished successfully and it is accepted (i.e, the data is valid).
rejected x The verification is finished successfully and it is rejected (i.e, the data is not valid).
inconclusive x The verification is finished successfully and the result is inconclusive (i.e., the data might not be valid).
canceled x The verification is finished without success because it was cancelled by the end-user.
failed x The verification is finished without success because an error prevented the verification from completing. For example, it could be that the process has timed out due to inactivity on the end-user side or that the end-user has denied access to the camera or microphone.

You can find more information about why it failed in the OpenAPI docs > Get process > failReason description. This fail reason varies from provider to provider. For examples on failed processes, see the provider-specific sections further down on this page.

For details on how the final status is mapped for each provider, see Onfido, Electronic IDentification, ReadID, FaceTec, Signicat Paper and Connect.

# Provider-specific information

The Get Process response message contains a providerSpecific area with information about the verification process.

Here is an example from Onfido :


}
    "providerSpecific": {
        "facialSimilarity": {
            "result": "clear",
            "imageIntegrity": "clear",
            "faceComparison": "clear",
            "visualAuthenticity": "clear",
            "similarityScore": "high"
        }
    }
}

The contents depend on the information each provider shares and it is filled in gradually as the provider shares this information. For example, some providers start sharing information as soon as the identity document is uploaded, others share information when the verification is complete.

The information in this area is composed of one or more JSON elements containing information about the results of the identity document verification. The number and name of these elements are specific for each provider:

Provider JSON elements in the Get process response
Onfido facialSimilarity, documentVerification
Electronic IDentification ocr, manualApproval
ReadID session
FaceTec liveness, matching
Signicat Paper verification, features, mrz, mrzChecksum, mrzVerification, mrzFeatureMatching
Connect idtoken, userInfo, error

For more details about each of these fields, see the providerSpecific element in the OpenAPI docs for Get process.

# Normalised final result

After a verification is finished and if the result is accepted, the Assure API generates a finalResult element and adds it to the Get process response. This element contains a fixed summary of provider collated information. The available fields depend on the information obtained from the provider.

Here is an example of a finalResult response:

"finalResult": {
    "firstName": "MARIA PAULA",
    "lastName": "SANTOS MENDES",
    "dateOfExpiry": "2024-03-02",
    "gender": "F",
    "nationality": "PRT",
    "documentType": "passport",
    "documentNumber": "1234567890",
    "issuingCountry": "PRT",
    "dateOfBirth": "2002-04-29",
    "similarityScore": "high",
    "livenessDetected": "true",
    "personalIdentificationNumber": "FANTASYBANK1234567890"
}

For detailed descriptions of these parameters and values, see the OpenAPI documentation > Get process > finalResult.

The elements in the responses you get from the Assure API are normalised to follow the same format, e.g. for how the date format (birthdate, date of expiry etc.) should be written (for more details, see Key concepts > Normalisation).

Note about Connect

In processes using the Connect service (Signicat component for ID methods), the values of the fields in the final result are not normalised. However, Connect gives you the advantage of using any eID method through the Assure API.

# Onfido results

# Final status of Onfido processes

Onfido always performs a documentVerification. Depending on the process type you choose (see below), it can also perform a facialSimilarity verification between the picture/video of the end-user and the photo in the ID document.

Based on Onfido's results, the Assure API returns a final status for that process:

Assure API's "final status" Onfido result: documentVerification Onfido result: facialSimilarity
accepted The ID is valid. The faces match.
rejected The ID is not valid. (any)
inconclusive The ID is valid but suspicious. (any)
inconclusive (any) At least one of the facialSimilarity verifications did not succeed.

# Process types for Onfido

Process types for Onfido are:

  • document
  • documentSelfie
  • documentVideo

If the process type is documentSelfie or documentVideo, the final status depends on the result of both facialSimilarity and documentVerification. If the process type is document only, the final status depends exclusively on the result of documentVerification.

For detailed description of processType, see the OpenAPI docs).

# Download full result

In the Get process response, you get the results for Onfido's breakdown listing (e.g. visualAuthenticity) in the provider-specific area (see code example below). Information about the sub-breakdowns as it was obtained from the provider (e.g. "supported_document") is only returned in the provider's raw JSON result. This is available in a zip file obtained from the Download full result service.

# accepted (Onfido)

The status is accepted when all underlying verifications have passed. This means there are no indications the document is fraudulent.

This is a response example of an Onfido process that was accepted:

    {
        "provider": "onfido",
        "status": "accepted",
        "processId": "4e48363a-37cb-4cff-8f91-afc9e52271fc",
        "createdAt": "2019-09-19T22:10:56Z",
        "updatedAt": "2019-09-19T22:11:23Z",
        "finalResult": {
            "firstName": "MARIA PAULA",
            "lastName": "SANTOS MENDES",
            "dateOfExpiry": "2020-07-08",
            "gender": "F",
            "nationality": "PRT",
            "documentType": "identityCard",
            "documentNumber": "1234567890",
            "issuingCountry": "PRT",
            "dateOfBirth": "2002-04-29",
            "similarityScore": "high"
        },
        "providerSpecific": {
            "facialSimilarity": {
                "result": "clear",
                "imageIntegrity": "clear",
                "faceComparison": "clear",
                "visualAuthenticity": "clear",
                "similarityScore": "high"
            },
            "documentVerification": {
                "lastName": "SANTOS MENDES",
                "dateOfExpiry": "2020-07-08",
                "subResult": "clear",
                "dataConsistency": "clear",
                "gender": "F",
                "documentType": "identityCard",
                "documentNumber": "1234567890",
                "dateOfBirth": "2002-04-29",
                "ageValidation": "clear",
                "policeRecord": "clear",
                "dataValidation": "clear",
                "result": "clear",
                "firstName": "MARIA PAULA",
                "imageIntegrity": "clear",
                "nationality": "PRT",
                "issuingCountry": "PRT",
                "dataComparison": "clear",
                "visualAuthenticity": "clear",
                "compromisedDocument": "clear",
                "mrzLine1": "I<PRT122336694<ZY42<<<<<<<<<<<",
                "mrzLine2": "8302304F21207081PRT<<<<<<<<<<<6"
            }
        }
    }

In this example, clear is passed as value in the result and sub-result fields, which means all the underlying verifications have passed.

For more detailed field and value descriptions, see the providerSpecificelements for Onfido, i.e. facialSimilarity and documentVerification, in the Open API documentation > Get process.

# inconclusive (Onfido)

A process can get the inconclusive status if one of the facial similarity verifications did not succeed or if the document is suspected to be fraudulent.

This is a response example of an Onfido process that was inconclusive:

    {
        "provider": "onfido",
        "status": "inconclusive",
        "processId": "85210241-4e70-4451-8ea3-7cd3c4d8843a",
        "createdAt": "2019-09-23T10:05:53Z",
        "updatedAt": "2019-09-23T10:09:49Z",
        "providerSpecific": {
            "facialSimilarity": {
                "result": "consider",
                "similarityScore": "high"
            },
            "documentVerification": {
                "lastName": "SPECIMEN",
                "dateOfExpiry": "2024-11-01",
                "subResult": "suspected",
                "gender": "F",
                "documentType": "passport",
                "documentNumber": "00000000",
                "dateOfBirth": "2002-04-29",
                "result": "consider",
                "firstName": "LAERKE OEYVOR AASE",
                "nationality": "NOR",
                "issuingCountry": "NOR",
                "mrzLine1": "PVNORSPECIMEN<<LAERKE<OEYVOR<AASE<<<<<<<<<<<",
                "mrzLine2": "00000000<0NOR7505319F24110154197505311234586"
            }
        }
    }

In this example some of the underlying verifications has passed the valuesconsider and suspected.

An inconclusive result does not contain a finalResult element but contains some data obtained from the document.

See the following sub-sections for more details about the inconclusive reasons.

# Facial similarity verification (inconclusive)

At least one of the facialSimilarity verifications did not succeed. Reasons for this can be:

  • The quality and integrity of the uploaded files were not sufficient to perform a face comparison (imageIntegrity).
  • The face in the document does not match the face in the selfie/video (faceComparison).
  • The person in the selfie/video is not real, or no liveness was detected (visualAuthenticity).

For more details, see Onfido's provider specific element, facialSimilarity in the OpenAPI documentation.

# Suspected fraud (inconclusive)

It could also be that the document is suspected to be fraudulent, for example:

  • One or more validatable elements are incorrect, e.g. date of birth, expiry date etc. (dataValidation).
  • One or more visual elements are incorrect, e.g. it is a photo of a printed photo, the security features are not present etc. (visualAuthenticity).
  • The document is registered in Onfido's database as a compromised document (compromisedDocument).
  • The data in the document is not consistent, e.g. between the MRZ lines and the OCR extracted text on passport for expiry date, birth date etc. (dataConsistency).
  • The document is reported as stolen etc. (policeRecord).

For more detailed field and value descriptions, see Onfido's provider specific element, documentVerification, in the OpenAPI documentation.

# rejected (Onfido)

The verification cannot be processed further. Reasons for this may for example be poor image quality (imageIntegrity), unknown document type (documentType), the end-user is below the minimum accepted age (ageValidation) etc.

This is a response example of an Onfido process that was rejected:

    {
        "provider": "onfido",
        "status": "rejected",
        "processId": "88d490a0-7184-4aba-804d-4dac400f5660",
        "createdAt": "2019-09-23T15:43:37Z",
        "updatedAt": "2019-09-23T15:46:30Z",
        "providerSpecific": {
            "facialSimilarity": {
                "result": "consider",
                "similarityScore": "medium"
            },
            "documentVerification": {
                "result": "consider",
                "subResult": "rejected",
                "documentType": "unknown"
            }
        }
    }

A rejected result does not contain a finalResult element. Also, the provider-specific elements are few since there will probably be little data obtained from the document.

For more details, see Onfido's provider specific elements, imageIntegrity, documentTypeand ageComparison in the OpenAPI documentation.

# canceled (Onfido)

The verification was canceled (by the end-user).

{
    "status": "canceled",
    "processId": "60ff4aff-90ab-4f99-bcb8-63553d243ff1",
    "provider": "onfido",
    "processType": "documentSelfie",
    "notificationUrl": "https://webhook.site/#!/705bcdd5-72dc-4018-832f-5b64ba26b5d8",
    "createdAt": "2022-02-14T14:18:38Z",
    "updatedAt": "2022-02-14T14:18:38Z",
    "providerSpecific": {}
}

# failed (Onfido)

A process gets the failed status if an error prevented the verification from completing. Examples could be time-out and server errors, expired tokens, validation errors etc.

This is a response example of an Onfido process that failed:

{
    "status": "failed",
    "processId": "47d4021c-2744-4491-b0a7-b433345bfc74",
    "provider": "onfido",
    "processType": "documentSelfie",
    "notificationUrl": "https://webhook.site/#!/705bcdd5-72dc-4018-832f-5b64ba26b5d8",
    "createdAt": "2022-02-14T14:04:58Z",
    "updatedAt": "2022-02-14T14:05:06Z",
    "failReason": {
        "type": "upload_failed",
        "message": "There was a validation error on this request (status code 422) | Field errors: {face_detection=[Multiple faces in image. Please note this validation can be disabled by setting the advanced_validation parameter to false.]}"
    }
}

In this case, the end-user has tried to upload an image with multiple faces instead of taking a selfie. You can find more information about the failReason field in the OpenAPI documentation.

# Electronic IDentification result

# Final status of EID processes

Electronic IDentification returns information about whether the verification was accepted, rejected, inconclusive or failed. Assure API simply maps those values directly to the process' final status. Reasons for the process to be rejected is part of the response.

Electronic IDentification responses will always have an ocr element (see the code example below). For unattended and attended process types (respectively without or with an agent present), it will also have a manualApproval element. For more details about process types, see OpenAPI docs > Get process > processType.

# accepted (Electronic IDentification)

This is a response example of an Electronic IDentification process that was accepted:


    {
    "status": "accepted",
    "processId": "e0dea380-4219-4388-81bb-61a56ed73ef3",
    "provider": "eid",
    "providerSpecific": {
        "ocr": {
            "similarityScore": "high",
            "livenessDetected": "true",
            "features": [
                {
                    "name": "Header",
                    "found": true,
                    "bbox": {
                        "x": 84,
                        "y": 28,
                        "width": 248,
                        "height": 32
                    },
                    "side": "data"
                },
                {
                    "name": "OVI 2",
                    "found": true,
                    "bbox": {
                        "x": 596,
                        "y": 44,
                        "width": 32,
                        "height": 24
                    },
                    "side": "data"
                },
                {
                    "name": "Signature",
                    "found": true,
                    "bbox": {
                        "x": 402,
                        "y": 273,
                        "width": 217,
                        "height": 60
                    },
                    "side": "data"
                },
                {
                    "name": "Photo",
                    "found": true,
                    "bbox": {
                        "x": 32,
                        "y": 168,
                        "width": 141,
                        "height": 141
                    },
                    "side": "data"
                },
                {
                    "name": "OVI 1",
                    "found": true,
                    "bbox": {
                        "x": 12,
                        "y": 44,
                        "width": 72,
                        "height": 80
                    },
                    "side": "data"
                }
            ],
            "securityChecks": {
                "nonExpired": {
                    "valid": true
                },
                "notUnderage": {
                    "valid": true
                },
                "dataIntegrity": {
                    "valid": true
                },
                "livenessDetected": {
                    "valid": true
                },
                "notFaceSpoofing": {
                    "valid": true
                },
                "notBWCopy": {
                    "valid": true
                }
            },
            "documentNumber": "1234567890",
            "dateOfExpiry": "2025-10-05",
            "firstName": "MARIA PAULA",
            "lastName": "SANTOS MENDES",
            "documentType": "passport",
            "dateOfBirth": "2002-04-29",
            "gender": "F",
            "nationality": "PRT",
            "personalIdentificationNumber": "FANTASYBANK1234567890",
            "issuingCountry": "PRT"
        }
    },
    "processType": "substantial",
    "notificationUrl": "https://webhook.site/#!/705bcdd5-72dc-4018-832f-5b64ba26b5d8",
    "createdAt": "2021-06-09T10:04:42Z",
    "updatedAt": "2021-06-09T10:05:41Z"
}

For field descriptions, see the Open API documentation > Get process.

# rejected (Electronic IDentification)

The process gets the rejected status if one or more security checks are not valid. In this example, the reason is that the document has expired:















 












































    {
    "status": "rejected",
    "processId": "1cc14545-0396-4cbe-8501-8f2461a91dfe",
    "provider": "eid",
    "providerSpecific": {
        "ocr": {
            "features": [
                {
                    ...
                },
                ...
            ],
            "securityChecks": {
                "nonExpired": {
                    "valid": false
                },
                "notUnderage": {
                    "valid": true
                },
                "dataIntegrity": {
                    "valid": true
                },
                "livenessDetected": {
                    "valid": true
                },
                "notFaceSpoofing": {
                    "valid": true
                },
                "sidesMatch": {
                    "valid": true
                },
                "notBWCopy": {
                    "valid": true
                }
            },
            "socialSecurityNumber": "11926318740",
            "healthNumber": "1234567890",
            "taxNumber": "199693803",
            "similarityScore": "high",
            "livenessDetected": "true",
            "documentNumber": "1234567890",
            "dateOfExpiry": "2020-07-08",
            "firstName": "MARIA PAULA",
            "lastName": "SANTOS MENDES",
            "documentType": "identityCard",
            "dateOfBirth": "2002-04-29",
            "gender": "F",
            "nationality": "PRT",
            "personalIdentificationNumber": "FANTASYBANK1234567890",
            "issuingCountry": "PRT"
        }
    },
    "processType": "substantial",
    "notificationUrl": "https://webhook.site/#!/705bcdd5-72dc-4018-832f-5b64ba26b5d8",
    "createdAt": "2021-06-09T10:37:10Z",
    "updatedAt": "2021-06-09T10:38:04Z"
}

For field descriptions, see the Open API documentation > Get process.

# inconclusive (Electronic IDentification)

A process gets the inconclusive status in the following cases:

  • When the similarityScore value in the OCR analysis is other than high (see description of possible values for similarityScore under OpenAPI docs > Get process > providerSpecific > ocr)
  • When one or more features are not "found", e.g. if the end-user covers a visual element on the ID document while taking a photo of it.

If you get an inconclusive status, you should inspect the process response to find the reason.

In this example the status is inconclusive since both similarityScore is too low (verylow) and two features are missing (OVI 1 and OVI 2 = false).







 















 


























 









































{
    "status": "inconclusive",
    "processId": "e0dea380-4219-4388-81bb-61a56ed73ef3",
    "provider": "eid",
    "providerSpecific": {
        "ocr": {
            "similarityScore": "verylow",
            "livenessDetected": "true",
            "features": [
                {
                    "name": "Header",
                    "found": true,
                    "bbox": {
                        "x": 85,
                        "y": 37,
                        "width": 249,
                        "height": 33
                    },
                    "side": "data"
                },
                {
                    "name": "OVI 2",
                    "found": false,
                    "side": "data"
                },
                {
                    "name": "Signature",
                    "found": true,
                    "bbox": {
                        "x": 392,
                        "y": 281,
                        "width": 202,
                        "height": 65
                    },
                    "side": "data"
                },
                {
                    "name": "Photo",
                    "found": true,
                    "bbox": {
                        "x": 44,
                        "y": 178,
                        "width": 141,
                        "height": 141
                    },
                    "side": "data"
                },
                {
                    "name": "OVI 1",
                    "found": false,
                    "side": "data"
                }
            ],
            "securityChecks": {
                "nonExpired": {
                    "valid": true
                },
                "notUnderage": {
                    "valid": true
                },
                "dataIntegrity": {
                    "valid": true
                },
                "livenessDetected": {
                    "valid": true
                },
                "notFaceSpoofing": {
                    "valid": true
                },
                "notBWCopy": {
                    "valid": true
                }
            },
            "documentNumber": "1234567890",
            "dateOfExpiry": "2025-10-05",
            "firstName": "MARIA PAULA",
            "lastName": "SANTOS MENDES",
            "documentType": "passport",
            "dateOfBirth": "2002-04-29",
            "gender": "F",
            "nationality": "PRT",
            "personalIdentificationNumber": "FANTASYBANK1234567890",
            "issuingCountry": "PRT"
        }
    },
    "processType": "substantial",
    "notificationUrl": "https://webhook.site/#!/705bcdd5-72dc-4018-832f-5b64ba26b5d8",
    "createdAt": "2021-06-09T10:04:42Z",
    "updatedAt": "2021-06-09T10:05:41Z"
}

# failed (Electronic IDentification)

A process gets the failed status if an error prevented the verification from completing. Examples could be that the microphone access is denied by the end-user or that the process times out due to inactivity on the end-user side (usually after 3 minutes).

This is a response example of an Electronic IDentification process that failed:











 




{
    "status": "failed",
    "processId": "4644c061-e229-449a-b4db-643c7403bbdc",
    "provider": "eid",
    "processType": "substantial",
    "notificationUrl": "https://webhook.site/#!/705bcdd5-72dc-4018-832f-5b64ba26b5d8",
    "createdAt": "2021-04-15T08:25:04Z",
    "updatedAt": "2021-04-15T08:28:57Z",
    "failReason": {
        "id": "8ea0e55f-385f-47b7-a401-ef1db467a625",
        "type": "InactiveUser.Aborted",
        "message": "There has been no interaction with the video"
    }
}

In this case, you can find more information about why it failed in the failReason field. For more information, see the OpenAPI documentation.

# ReadID results

# Final status of ReadID processes

ReadID's response returns the data extracted from the document as well as the information about the results of the chip verification and chip clone detection.

Assure API uses the information in the chipVerification and chipCloneDetection fields to map the process' final status:

  • accepted:
    • chipVerification was successful.
    • chipCloneDetection was either successful or not available. This can happen with some older documents that do not support clone detection.
  • inconclusive: chipVerification was successful but chipCloneDetection failed. This means that it was not possible to check if the chip is real. Since this validation may fail for other reasons, we recommend that you allow the end-user to retry one or two more times.
  • rejected: chipVerification failed.

# accepted (ReadID)

This is a response example of a ReadID process that was accepted:

{
    "provider": "readid",
    "status": "accepted",
    "processId": "4e6aed00-f72a-4363-9d4a-418d66f5e49c",
    "providerSpecific": {
        "consolidatedIdentityData": {
            "chipVerification": "SUCCEEDED",
            "chipCloneDetection": "SUCCEEDED",
            "dateOfBirth": "2002-04-29",
            "dateOfExpiry": "2023-06-08",
            "documentCode": "P",
            "documentNumber": "P123456",
            "documentType": "passport",
            "gender": "F",
            "issuingCountry": "PRT",
            "nationality": "PRT",
            "personalIdentificationNumber": "123456789",
            "firstName": "MARIA PAULA",
            "lastName": "SANTOS MENDES"
        }
    },
    "finalResult": {
        "documentType": "passport",
        "firstName": "MARIA PAULA",
        "lastName": "SANTOS MENDES",
        "gender": "F",
        "nationality": "PRT",
        "dateOfBirth": "2002-04-29",
        "documentNumber": "P123456",
        "dateOfExpiry": "2023-06-08",
        "issuingCountry": "PRT",
        "personalIdentificationNumber": "123456789"
    },
    "processType": "ready",
    "createdAt": "2021-08-04T08:19:22Z",
    "updatedAt": "2021-08-04T08:21:56Z"
}

For field descriptions, see the Open API documentation > Get process.

# inconclusive (ReadID)

This is a response example of a ReadID process that was inconclusive:

{
    "provider": "readid",
    "status": "inconclusive",
    "processId": "36c9e4cb-9fe2-4326-a57b-ec1e7f6d2bbf",
    "providerSpecific": {
        "consolidatedIdentityData": {
            "chipVerification": "SUCCEEDED",
            "chipCloneDetection": "FAILED",
            "dateOfBirth": "2002-04-29",
            "dateOfExpiry": "2023-06-08",
            "documentCode": "P",
            "documentNumber": "M123456",
            "documentType": "passport",
            "gender": "F",
            "issuingCountry": "PRT",
            "nationality": "PRT",
            "personalIdentificationNumber": "123456789",
            "firstName": "MARIA PAULA",
            "lastName": "SANTOS MENDES"
        }
    },
    "processType": "ready",
    "createdAt": "2021-08-04T09:18:09Z",
    "updatedAt": "2021-08-04T09:24:01Z"
}

# rejected (ReadID)

This is a response example of a ReadID process that was rejected:

{
    "provider": "readid",
    "status": "rejected",
    "processId": "36c9e4cb-9fe2-4326-a57b-ec1e7f6d2bbf",
    "providerSpecific": {
        "consolidatedIdentityData": {
            "chipVerification": "FAILED",
            "chipCloneDetection": "SUCCEEDED",
            "dateOfBirth": "2002-04-29",
            "dateOfExpiry": "2023-06-08",
            "documentCode": "P",
            "documentNumber": "M123456",
            "documentType": "passport",
            "gender": "F",
            "issuingCountry": "PRT",
            "nationality": "PRT",
            "personalIdentificationNumber": "123456789",
            "firstName": "MARIA PAULA",
            "lastName": "SANTOS MENDES"
        }
    },
    "processType": "ready",
    "createdAt": "2021-08-04T09:18:09Z",
    "updatedAt": "2021-08-04T09:24:01Z"
}

For field descriptions, see the Open API documentation > Get process.

# FaceTec results

# Final status of FaceTec processes

Assure API uses the information in the liveness and matching fields to map the process' final status:

  • accepted: The end-user passed all liveness checks performed by FaceTec, and their face matched the face in the ID-photo/selfie image with matchLevel >= 6 (1/100,000 FAR).
  • inconclusive: The match level (matchLevel) between the face of the end-user and the face in the ID-photo/selfie image is between 1 (1/100 FAR) and 5 (1/10,000 FAR).
  • rejected: The end-user did not pass one or more of the liveness checks performed by FaceTec, or their face did not match the face in the ID-photo/selfie image.

# accepted (FaceTec)

This is a response example of a FaceTec process that was accepted:

{
   "processId":"fd3121cb-f9aa-4c77-bb65-97f6d82a9a02",
   "provider":"facetec",
   "status":"accepted",
   "finalResult":{
      "livenessDetected":"true",
      "similarityScore":"high"
   },
   "notificationUrl":"https://webhook.site/#!/705bcdd5-72dc-4018-832f-5b64ba26b5d8",
   "createdAt":"2021-11-11T15:23:35Z",
   "updatedAt":"2021-11-11T15:24:10Z",
   "providerSpecific":{
      "liveness":{
         "faceScanSecurityChecks":{
            "auditTrailVerificationCheckSucceeded":true,
            "replayCheckSucceeded":true,
            "faceScanLivenessCheckSucceeded":true,
            "sessionTokenCheckSucceeded":true
         },
         "error":false,
         "success":true
      },
      "matching":{
         "attempts":[
            {
               "algorithm":"facePortrait",
               "matchLevel":8,
               "imageProcessing":"faceFound",
               "success":true,
               "error":false
            }
         ],
         "algorithm":"facePortrait",
         "matchLevel":8,
         "imageProcessing":"faceFound",
         "success":true,
         "error":false
      }
   }
}

For field descriptions, see the Open API documentation > Get process and Start verification

# inconclusive (FaceTec)

This is a response example of a FaceTec process that was inconclusive:

{
   "processId":"1ca4c667-7132-45dc-a826-3bddaf4bc2a6",
   "provider":"facetec",
   "status":"inconclusive",
   "notificationUrl":"https://webhook.site/#!/705bcdd5-72dc-4018-832f-5b64ba26b5d8",
   "createdAt":"2022-04-21T13:44:37Z",
   "updatedAt":"2022-04-21T13:46:51Z",
   "providerSpecific":{
      "liveness":{
         "faceScanSecurityChecks":{
            "auditTrailVerificationCheckSucceeded":true,
            "replayCheckSucceeded":true,
            "faceScanLivenessCheckSucceeded":true,
            "sessionTokenCheckSucceeded":true
         },
         "error":false,
         "success":true
      },
      "matching":{
         "attempts":[
            {
               "algorithm":"facePortrait",
               "matchLevel":4,
               "imageProcessing":"faceFound",
               "success":true,
               "error":false
            },
            {
               "algorithm":"idPhoto",
               "matchLevel":5,
               "imageProcessing":"faceFound",
               "success":true,
               "error":false
            },
            {
               "algorithm":"idPhotoLowQuality",
               "matchLevel":5,
               "imageProcessing":"faceFound",
               "success":true,
               "error":false
            }
         ],
         "algorithm":"idPhotoLowQuality",
         "matchLevel":5,
         "imageProcessing":"faceFound",
         "success":true,
         "error":false
      }
   }
}

In this example, matchLevel was not high enough to get accepted.

For more details about matchLevel and other fields, see the providerSpecific element for FaceTec in the Open API documentation for Get process and Start verification.

# rejected (FaceTec)

This is a response example of a FaceTec process that was rejected. Here, liveness was detected in the recorded video of the user's face, but there was no match with the face on the ID-photo ("matchLevel":0):

{
   "processId":"5fe7a9b9-f781-44d1-b37b-6cc958ee7b7a",
   "provider":"facetec",
   "status":"rejected",
   "notificationUrl":"https://webhook.site/#!/705bcdd5-72dc-4018-832f-5b64ba26b5d8",
   "createdAt":"2021-11-12T13:52:10Z",
   "updatedAt":"2021-11-12T13:52:46Z",
   "providerSpecific":{
      "liveness":{
         "faceScanSecurityChecks":{
            "auditTrailVerificationCheckSucceeded":true,
            "replayCheckSucceeded":true,
            "faceScanLivenessCheckSucceeded":true,
            "sessionTokenCheckSucceeded":true
         },
         "error":false,
         "success":true
      },
      "matching":{
         "attempts":[
            {
               "algorithm":"facePortrait",
               "matchLevel":0,
               "imageProcessing":"faceFound",
               "success":false,
               "error":false
            },
            {
               "algorithm":"idPhoto",
               "matchLevel":0,
               "imageProcessing":"faceFound",
               "success":false,
               "error":false
            },
            {
               "algorithm":"idPhotoLowQuality",
               "matchLevel":0,
               "imageProcessing":"faceFound",
               "success":false,
               "error":false
            }
         ],
         "algorithm":"idPhotoLowQuality",
         "matchLevel":0,
         "imageProcessing":"faceFound",
         "success":false,
         "error":false
      }
   }
}

# Signicat Paper results

# Final status of Paper processes

Assure API's final status Description
accepted It was possible to read the document and verify the information.
inconclusive It was possible to read the document but the information could not be verified since the MRZ area was missing or unreadable. Documents without MRZ will never be accepted. They will be inconclusive if the data in the text fields are valid, or rejected if they are not valid. This means, only reading the text fields is not enough to guarantee that the data is valid.
rejected It was possible to read the document, but an error was found or at least one verification failed. List of errors is returned in the response.
failed It was not possible to read the document, since an error prevented the verification from continuing. For example, the end-user may have blocked the access to the camera on their device.
canceled The verification was cancelled by the end-user.

# accepted (Signicat Paper)

This is a response example of a Signicat Paper process that was accepted:

    {
        "processId": "processId",
        "provider": "signicatpaper",
        "status": "accepted",
        "createdAt": "createdAt",
        "updatedAt": "updatedAt",
        "finalResult": {
            "firstName": "Maria Paula",
            "lastName": "Santos Mendes",
            "dateOfExpiry": "2020-10-15",
            "gender": "F",
            "nationality": "PRT",
            "documentType": "passport",
            "documentNumber": "1234567890",
            "issuingCountry": "PRT",
            "dateOfBirth": "2002-04-29"
        },
        "providerSpecific": {
            "verification": {
                "type": "MRZ_FEATURE_COMPARISON",
                "status": "true"
            },
            "features": {
                "firstName": "Maria Paula",
                "lastName": "Santos Mendes",
                "dateOfExpiry": "2020-10-15",
                "issuingAuthority": "SEF SERV ESTR E FR0NTE1RAS",
                "gender": "F",
                "documentNumber": "1234567890",
                "dateOfBirth": "2002-04-29",
                "personalNumber": "1234567890",
                "dateOfIssue": "2015-10-15"
            },
            "mrz": {
                "firstName": "Maria Paula",
                "lastName": "Santos Mendes",
                "dateOfExpiry": "2020-10-15",
                "nationality": "PRT",
                "gender": "F",
                "documentType": "passport",
                "issuingCountry": "PRT",
                "documentNumber": "1234567890",
                "dateOfBirth": "2002-04-29",
                "personalNumber": "1234567890"
            },
            "mrzChecksum": {
                "dateOfExpiry": "VALID",
                "documentNumber": "VALID",
                "dateOfBirth": "VALID",
                "personalNumber": "VALID"
            },
            "mrzVerification": {
                "dateOfExpiry": "VALID",
                "documentType": "VALID",
                "issuingCountry": "VALID",
                "dateOfBirth": "VALID"
            },
            "mrzFeatureMatching": {
                "dateOfExpiry": "FULL_MATCH",
                "lastName": "FULL_MATCH",
                "issuingAuthority": "FOUND",
                "firstName": "FULL_MATCH",
                "documentNumber": "FULL_MATCH",
                "dateOfBirth": "FULL_MATCH",
                "driving_permits": "MISSING",
                "personalNumber": "LEVENSHTEIN1",
                "dateOfIssue": "VALID"
            }
        }
    }

For field descriptions, see the provider specific elements for Signicat Paper in the Open API documentation.

# rejected (Signicat Paper)

This is a response example of a Signicat Paper process that was rejected:


    {
        "processId": "processId",
        "provider": "signicatpaper",
        "status": "rejected",
        "createdAt": "createdAt",
        "updatedAt": "updatedAt",
        "finalResult": {
            "firstName": "Maria Paula",
            "lastName": "Santos Mendes",
            "dateOfExpiry": "2016-10-20",
            "gender": "F",
            "nationality": "PRT",
            "documentType": "passport",
            "documentNumber": "XY1101P52",
            "issuingCountry": "PRT",
            "dateOfBirth": "2002-04-29"
        },
        "providerSpecific": {
            "verification": {
                "type": "MRZ_ONLY",
                "status": "false"
            },
            "mrz": {
                "firstName": "Maria Paula",
                "lastName": "Santos Mendes",
                "dateOfExpiry": "2016-10-20",
                "nationality": "PRT",
                "gender": "F",
                "documentType": "passport",
                "issuingCountry": "PRT",
                "documentNumber": "XY1101P52",
                "dateOfBirth": "2002-04-29",
                "personalNumber": "1234567890"
            },
            "mrzChecksum": {
                "dateOfExpiry": "VALID",
                "documentNumber": "VALID",
                "dateOfBirth": "VALID",
                "personalNumber": "VALID"
            },
            "mrzVerification": {
                "dateOfExpiry": "INVALID",
                "documentType": "VALID",
                "issuingCountry": "VALID",
                "dateOfBirth": "VALID"
            },
            "errors": ["Invalid date_of_expiry: NOT in the future, value 2016-10-20"]
        }
    }

For field descriptions, see the provider specific elements for Signicat Paper in the Open API documentation.

# inconclusive (Signicat Paper)

This is a response example of a Signicat Paper process that was inconclusive:

    {
        "processId": "processId",
        "provider": "signicatpaper",
        "status": "inconclusive",
        "createdAt": "createdAt",
        "updatedAt": "updatedAt",
        "providerSpecific": {
            "verification": {
                "type": "FEATURES_ONLY",
                "status": "true"
            },
            "features": {
                "firstName": "Maria Paula",
                "lastName": "Santos Mendes",
                "issuingAuthority": "SEF SERV ESTR E FR0NTE1RAS",
                "gender": "UNEXPECTED_VALUE",
                "documentNumber": "47 00 006492 4",
                "dateOfBirth": "2002-04-29",
                "personalNumber": "1234567890",
                "dateOfIssue": "2000-08-23"
            },
            "featuresVerification": {
                "dateOfExpiry": "MISSING",
                "lastName": "FOUND",
                "issuingAuthority": "FOUND",
                "firstName": "FOUND",
                "documentNumber": "FOUND",
                "dateOfBirth": "VALID",
                "drivingPermits": "FOUND",
                "personalNumber": "FOUND",
                "dateOfIssue": "VALID"
            }
        }
    }

In this case, it was inconclusive because it was a document without MRZ ("FEATURES_ONLY").

For field descriptions, see the provider specific elements for Signicat Paper in the Open API documentation.

# failed (Signicat Paper)

A process gets the failed status if an error prevented the verification from completing. An example could be that the end-user has blocked access to the camera on the device.

This is a response example of a Signicat Paper process that failed:

{
  "status": "failed",
    "processId": "b16e9c37-dac5-4897-b6ba-055d5a1dadc3",
    "provider": "signicatpaper",
    "redactionRequested": false,
    "providerSpecific": {},
    "notificationUrl": "https://webhook.site/#!/705bcdd5-72dc-4018-832f-5b64ba26b5d8",
    "createdAt": "2021-04-29T11:57:02Z",
    "updatedAt": "2021-04-29T11:57:02Z",
    "failReason": {
        "type": "MicrophoneOrCameraPermissionDenied",
        "message": "No access to microphone/camera"
  }
}

In this case, you can find more information about why it failed in the failReason field. For more information, see the OpenAPI documentation.

# canceled (Signicat Paper)

This is a response example of a Signicat Paper process that was cancelled by the end-user:

{
    "status": "canceled",
    "processId": "9ae09849-6c4d-429f-92e5-607ce8913ac1",
    "provider": "signicatpaper",
    "redactionRequested": false,
    "notificationUrl": "https://webhook.site/#!/705bcdd5-72dc-4018-832f-5b64ba26b5d8",
    "createdAt": "2022-03-14T14:34:19Z",
    "updatedAt": "2022-03-14T14:34:19Z"
}

# Connect results

# Notes about the final result in Connect processes

  • The Connect provider's finalResult does not follow the same rules for normalisation as with the other providers. Since Connect allows using any eID method, this means that the Assure API never knows which ID method is used in each 'connect' process, thus it will not be able to normalise the values obtained.
  • If userInfo comes encrypted, there will be no finalResult in the Get Process response, even if the authentication was successful:
userInfo format finalResult
JSON Yes
JWT not encrypted Yes
JWT encrypted No

The userInfo format is contractually agreed.

JWT format example of userInfo:

"userInfo":"eyJraWQiOiJhbnkub2lkYy50ZXN0Lmp3ay52LjEiLCJhbGciOiJSUzI1NiJ9.eyJjb25zdW1lci5iaW4iOiJGQU5UQVNZQkFOSzEyMzQ1Njc4OTAiLCJzdWIiOiJGS2lqRnNFS1h6NTliWHVyd2FmdXl3UEVjbmF4YzZSMCIsImFkZHJlc3MiOnsiY291bnRyeSI6IkRFIiwicG9zdGFsX2NvZGUiOiIwMDAwQUEifSwiY29uc3VtZXIuaW5pdGlhbHMiOiJWSiIsImdlbmRlciI6IjEiLCJpZGluLnJhYm8uY29uc3VtZXIuYmluIjoiRkFOVEFTWUJBTksxMjM0NTY3ODkwIiwic2lnbmljYXQubmF0aW9uYWxfaWQiOiJGQU5UQVNZQkFOSzEyMzQ1Njc4OTAiLCJjb25zdW1lci5wcmVmZXJyZWRsYXN0bmFtZXByZWZpeCI6ImRlIiwiY29uc3VtZXIucGFydG5lcmxhc3RuYW1lIjoiSmFuc2VuIiwiZ2l2ZW5fbmFtZSI6IlZKIiwiY29uc3VtZXIubGVnYWxsYXN0bmFtZXByZWZpeCI6ImRlIiwiY29uc3VtZXIucHJlZmVycmVkbGFzdG5hbWUiOiJWcmllcy1KYW5zZW4iLCJpZGluLmNvbnN1bWVyLmxlZ2FsbGFzdG5hbWVwcmVmaXgiOiJkZSIsImZhbWlseV9uYW1lIjoiVnJpZXMifQ.Xp6fPz2UprQE21Y1Mbms4LkmydDy4caQUitZsB-2aytBTBNVaLO78U7MqszLCUaIE4fL0MHNmd7-eigDc_TOWQBqAYz_SVhXKMDw9tj1GYdp52T2kqytW86c6YaeQ20rGKxIR4e9jOOJj0N4lEwTMc67FAO9Lhy8r5EfJDnPt0mBhPhbUvYxII42tm0M12-3qBIHkdAhuyv-wv0RH9AymgZfRNWNnfJSPcj_9a9YpE692SZCz8U24IIQy6tSWh40fN40yfy_2Sc6M4sWi2Cs-UAvk0wifW5bpAjOwnj0bkoeTvqiljxch0LQKLNWVKWoxhICeHzuKKlA_bZyoXMGjA"

JSON format example of userInfo:

{
    "userInfo": {
        "consumer.bin": "FANTASYBANK1234567890",
        "sub": "FKijFsEKXz59bXurwafuywPEcnaxc6R0",
        "consumer.initials": "VJ",
        "gender": "1",
        "idin.rabo.consumer.bin": "FANTASYBANK1234567890",
        "signicat.national_id": "FANTASYBANK1234567890",
        "consumer.preferredlastnameprefix": "de",
        "consumer.partnerlastname": "Jansen",
        "given_name": "VJ",
        "test1": "country",
        "test2": "0000AA",
        "consumer.legallastnameprefix": "de",
        "consumer.preferredlastname": "Vries-Jansen",
        "idin.consumer.legallastnameprefix": "de",
        "family_name": "Vries"
    }
}

# Final status of Connect processes

The status of the Connect processes is mapped directly from the result of the authentication:

Process final status Description
accepted The end-user’s authentication was successful.
rejected The end-user’s authentication did not succeed.
canceled The authentication was canceled by the end-user.

# accepted (Connect)

This is a response example of a Connect process that was accepted. Here, the iDIN method is used as an example.

# JSON format

In this example, finalResult contains only a few fields. The used authentication method (in this case, iDIN), provides only the first name, last name, gender and personal number. Thus, that is the only information that the Assure API can add to finalResult. This is an example of an accepted Get process response for Connect:

{
    "processId": "44ab57ca-3d5e-458d-8b0c-e9a1a08e9cd9",
    "provider": "connect:idin",
    "status": "accepted",
    "createdAt": "2020-01-21T15:25:30Z",
    "updatedAt": "2020-01-21T15:26:08Z",
    "finalResult": {
        "firstName": "VJ",
        "lastName": "Vries",
        "gender": "1",
        "personalIdentificationNumber": "FANTASYBANK1234567890"
    },
    "providerSpecific": {
        "idToken":
        "eyJraWQiOiJhbnkub2lkYy50ZXN0Lmp3ay52LjEiLCJhbGciOiJSUzI1NiJ9.eyJhY3IiOiJ1cm46c2lnbmljYXQ6b2lkYzptZXRob2Q6aWRpbiIsImF1ZCI6ImNsaWVudC5hc3N1cmUuY29ubmVjdC5kZWxlZ2F0ZSIsInN1YiI6IkZLaWpGc0VLWHo1OWJYdXJ3YWZ1eXdQRWNuYXhjNlIwIiwibmJmIjoxNTc5NjIwMzY4LCJhbXIiOiJ1cm46a3NpOm5hbWVzOlNBTUw6Mi4wOmFjOmlESU4iLCJhdXRoX3RpbWUiOjE1Nzk2MjAzNjYsImlzcyI6Imh0dHBzOlwvXC9kZXYwMS5zaWduaWNhdC5jb21cL29pZGMiLCJleHAiOjE1Nzk2MjM5NjgsIm5vbmNlIjoiZjQwZGVlNjEtMmUwNy00YmE4LTgxZjAtYTJiMTViZTcxZjBjIiwiaWF0IjoxNTc5NjIwMzY4fQ.qCCyhOp16OMDPNOrAz-JbcuI5VRoGNnaGzD19GQAnBbqniFXCQakyLSbbZsjsXa0uxU0uEzpcOC131TP85cyIxQLH01Gw2kdZ9QN3YZyGQt6ZRk5wNczKi2OOD9tpB0nYKg9tglTcRylGwyXSkTba6YJ_jg_NvU_FkIx_5LIQtyI96AC3ValpZbv3KNnwttpR4L8IIRg3LcAYOVaIrm4aF_dgCctYJSEQlN3Kf0AuWr6drvbMFqhfKavWaC9rjuzNunFrf-msk4kYhsyiZ7dhUNLSUp-wIp-3ffeAjsErRjmMF5ss2lalMF9MriB36ZybqWCj5LYb4jYyPcDLBaUlA",
        "userInfo": {
            "consumer.bin": "FANTASYBANK1234567890",
            "sub": "FKijFsEKXz59bXurwafuywPEcnaxc6R0",
            "consumer.initials": "VJ",
            "gender": "1",
            "idin.rabo.consumer.bin": "FANTASYBANK1234567890",
            "signicat.national_id": "FANTASYBANK1234567890",
            "consumer.preferredlastnameprefix": "de",
            "consumer.partnerlastname": "Jansen",
            "given_name": "VJ",
            "consumer.legallastnameprefix": "de",
            "consumer.preferredlastname": "Vries-Jansen",
            "idin.consumer.legallastnameprefix": "de",
            "family_name": "Vries"
        }
    }
}

# JWT not encrypted format

In this example, the user information is in JWT format, but it is not encrypted. This allows the Assure API to get the information from there (by decoding the JWT) and fill the final result.

{
    "processId": "b7634e9e-7416-4ea2-bd6d-40a42c954f0d",
    "provider": "connect:idin",
    "status": "accepted",
    "createdAt": "2020-01-21T16:12:33Z",
    "updatedAt": "2020-01-21T16:13:01Z",
    "providerSpecific": {
        "idToken": "eyJraWQiOiJhbnkub2lkYy1lbmNyeXB0aW9uLnRlc3QuandrLnYuMyIsImN0eSI6IkpXVCIsImVuYyI6IkExMjhDQkMtSFMyNTYiLCJhbGciOiJSU0EtT0FFUCJ9.cl5eO0QH92ZjBWwgGOF_OTSNe4rC1vCD_-JfIUgBWNaIHljWm2IXBYw_BVVPDIwpDz6o9Z1iYfALB0Bahce1ffzcCFlaukT-7HM-F2h8iHktAnWeg2ynLH9PB5ACRZNDoM-9ADZ63_tIcgs2hiX_pQELbiDD-OJ63cKOuZbwQQmaZe9YeEH2aXvRR3ELC61g7QyYuico3HTfyCA1WxpmPNIceQWdm-KFMCiyJCPgoMxyW5nzN1VQrORPBKjnKfdqyoC8v9-8NcckUCURNbdul2s9dSyPmDM14Xc23LM6xSjqVh0bGvgOzrldGgq7EBNbxEP48g3BZviiBCs2cQU_vw.88iqzXAJiJH-8dpdw3QzZA.QoVKRhH1ocJCRDT-P3WS1ILrIp_lPzzba8xh41BxKev525DXrivhEhbppRUNU1YdW_1Xhk2eN41s_-5AE1p3oOKCmt5ckct5QyxqiuZaU056L7dWbv1aa3vPFiEnrTHt191FFwYLcKAz-o6S5xwJXYh8NucxXGd_MvyVKc9Oy9-Dm7ZXhlsBBGpseIQcYxMfaGxrtiCnOHrYj36WC6F25Ma0sr99tSej-83GIhSIk4jihjaTFxdlxdnpducV6hRxsZaXTwWGsmH74ryq2QjEqdGScZuu6qSkfoiABoUSVnPryE09P3SUIbHw8lJM304ZpJ5z2mHWRKbQvp2RGackfTMMmdNex64w-XqY0wVMj20A3FlnKxtuXHMm1KrtopTX3gMicRCX-VxU1hJZmzfriGMaXCWOonYevf1LYFlCgzUk2zQ5Cb2q9MY6Re11aWAu70DmO7TBXUKfR9Od6Yxx3JZH9Q32UzUbBe2J41YjbHxXSLsrihxNx71vVfkxfngf7NILrvafrOcC1bRpyv6LncKsr7qdzoQmz5bLtJF7tAb7zE4z5rndv0eOxE7UUTzbD6wBwQ_bBB-qmUciWQYujGgnqiB1k4lxsNSBUGFpq_YbQOftn-X-kxOC-UdlxaKNUu_GGriOLG-Q21aYLkigakh9gWa8pOKc2UVGQSGTDmONE_n-u-PCjSNE69U5_wnTA9MKka9taS5XANcwuQumLvT7BmJEEBjdyveFrn8HIz_0mn_B1fyzBa28m1MrFgU2WhtVN6ilsBVz9mhLQYqzKvO2V63bLFB7cHvdeFtbh9JBp2DdOpHXWbwXSFfoDKM877kZ_SKV71ZJP7-y2sGxgWZsg8CZUvHud-APhAqUjZJ4a9FAq80gIvH9APSMJE2SdvwzmOk5NaQUD5alqtnY49s-1nP8xKHspZ49irs1X9Avf52N3iNb2_GRLtGdWyuGoP640COcptup94oJ-0bJlcKj7C_kZzTswPSjpBS-5cyMFGqsgSEOn1KRZSCGUtCkYmG_KhSfcsbfHhs_WngP_j_7gnACKueTiQqD0XLBGKp7baj7DN2oNu-oEMfXBUDJGsXr1BGF3z2yCLUUPOgbV7PPnYOOQ12hi8KY3UJ6DbQ.TZZZyQIRNEDDpCu6kb_1FA",
        "userInfo": "eyJraWQiOiJhbnkub2lkYy50ZXN0Lmp3ay52LjEiLCJhbGciOiJSUzI1NiJ9.eyJjb25zdW1lci5iaW4iOiJGQU5UQVNZQkFOSzEyMzQ1Njc4OTAiLCJzdWIiOiJGS2lqRnNFS1h6NTliWHVyd2FmdXl3UEVjbmF4YzZSMCIsImFkZHJlc3MiOnsiY291bnRyeSI6IkRFIiwicG9zdGFsX2NvZGUiOiIwMDAwQUEifSwiY29uc3VtZXIuaW5pdGlhbHMiOiJWSiIsImdlbmRlciI6IjEiLCJpZGluLnJhYm8uY29uc3VtZXIuYmluIjoiRkFOVEFTWUJBTksxMjM0NTY3ODkwIiwic2lnbmljYXQubmF0aW9uYWxfaWQiOiJGQU5UQVNZQkFOSzEyMzQ1Njc4OTAiLCJjb25zdW1lci5wcmVmZXJyZWRsYXN0bmFtZXByZWZpeCI6ImRlIiwiY29uc3VtZXIucGFydG5lcmxhc3RuYW1lIjoiSmFuc2VuIiwiZ2l2ZW5fbmFtZSI6IlZKIiwiY29uc3VtZXIubGVnYWxsYXN0bmFtZXByZWZpeCI6ImRlIiwiY29uc3VtZXIucHJlZmVycmVkbGFzdG5hbWUiOiJWcmllcy1KYW5zZW4iLCJpZGluLmNvbnN1bWVyLmxlZ2FsbGFzdG5hbWVwcmVmaXgiOiJkZSIsImZhbWlseV9uYW1lIjoiVnJpZXMifQ.Xp6fPz2UprQE21Y1Mbms4LkmydDy4caQUitZsB-2aytBTBNVaLO78U7MqszLCUaIE4fL0MHNmd7-eigDc_TOWQBqAYz_SVhXKMDw9tj1GYdp52T2kqytW86c6YaeQ20rGKxIR4e9jOOJj0N4lEwTMc67FAO9Lhy8r5EfJDnPt0mBhPhbUvYxII42tm0M12-3qBIHkdAhuyv-wv0RH9AymgZfRNWNnfJSPcj_9a9YpE692SZCz8U24IIQy6tSWh40fN40yfy_2Sc6M4sWi2Cs-UAvk0wifW5bpAjOwnj0bkoeTvqiljxch0LQKLNWVKWoxhICeHzuKKlA_bZyoXMGjA"
   }
}

# rejected (Connect)

This is a response example of a Connect process that was rejected:

    {
        "processId": "1ad420ff-7b71-4322-8917-64fec28fe118",
        "provider": "connect:idin",
        "status": "rejected",
        "createdAt": "2020-01-21T16:37:21Z",
        "updatedAt": "2020-01-21T16:37:53Z",
        "providerSpecific": {
            "error": {
                "errorDescription": "The Resource Owner did not complete the login. urn:signicat:error:internal:Expired; ",
                "error": "access_denied"
            }
        }
    }

# inconclusive (Connect)

Connect processes do not have any inconclusive status.

# canceled (Connect)

This is a response example of a Connect process that was canceled:

    {
        "processId": "ab5739a7-92ad-429d-a6d9-7cb233b2865c",
        "provider": "connect:idin",
        "status": "canceled",
        "createdAt": "2020-01-28T12:24:58Z",
        "updatedAt": "2020-01-28T12:25:32Z",
        "providerSpecific": {
            "error": {
                "errorDescription": "The Resource Owner did not complete the login. urn:signicat:error:usercancel; The process was aborted by the end-user",
                "error": "access_denied"
            }
        }
    }
Last updated: 20/09/2023 12:20 UTC

← Files in dossier →