link

# Get process


Page contents

This topic describes how to use the Get process service. This service is useful since its response provides plenty of information, for example:

  • Which provider and process type are used in the verification?
  • When was the data in the process last updated?
  • Is the verification process finished?
  • What is the result?
  • Which data does the provider obtain?

The service also provides the most common result information like first name, last name and date of birth.

This section details all the information that can be retrieved for a process, depending on the provider, processType and status variables. This section does not detail the results for each documentType/documentCountry since that list is too broad and also continuously changing. If you need details about specific cases, contact Signicat at support@signicat.com.

# Response structure

The information in the Get process response message depends on the used provider and the time of the flow you call this service. Time points can be as soon as the process is created, after the images are uploaded or after a verification is finished. The structure of the obtained JSON in the response changes over time and is divided into three main areas:

  1. Process information
  2. Provider-specific information
  3. Normalised final result

click-to-zoom

# 1. 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"
    }
Parameter Description Type
processId The process' unique identifier string
provider The provider used in the identity proofing . enum: Provider
createdAt The process' created date. Date: Normalisation values
updatedAt The process' updated date. Date: Normalisation values
status The current state of the process. Indicates whether the identity proofing process is complete (accepted, rejected, inconclusive) or not (canceled, failed) and what is the outcome. For more details about the statuses, see Enum > Process status. For details on how each final status is mapped for each provider's final result, see the provider-specific information in the following sections, e.g. for Onfido. enum: Process status

# 2. Provider-specific information

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

Here is an example of a providerSpecific element (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 More details
Onfido facialSimilarity, documentVerification Onfido results
Electronic IDentification ocr, manualApproval Electronic IDentification results
ReadID session ReadID results
Signicat Paper verification, features, mrz, mrzChecksum, mrzVerification, mrzFeatureMatching Paper results
Connect idtoken, userInfo, error Connect results

# 3. 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. For example, the final result of a process with "provider":"onfido" and "processType":"document" will never contain information about similarityScore or livenessDetected, since an Onfido process only verifies the ID document and will not have that type of information available.

Here is an example of a finalResult response:

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

Parameter descriptions:

Parameter Description Type
firstName The end-user's given name. String
lastName The end-user's surname. String
dateOfExpiry The document's date of expiry. Date: Normalised values
dateOfBirth The end-user's date of birth. Date: Normalised values
gender The end-user's gender. enum: Gender
nationality The end-user's nationality. String: Normalised values
documentType The document type. enum: Document type
documentNumber The document number. String
issuingCountry The issuing country of the document. String: Normalised values
similarityScore The similarity level between the end-user's face and the photo in the ID. enum: Similarity score
livenessDetected Liveness detected during the process. Boolean
personalIdentificationNumber The official personal identification number scheme used in a country. String

In processes using Signicat Connect, 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.

The following sub-sections details the results by provider. It also includes explanations of the final status in the process and how to interpret the information in the response.

# Onfido results

# Final status mapping between Onfido and Assure API

Onfido always performs a verification of the document (documentVerification). Depending on the process type you choose, it can also perform a facial similarity verification between the picture/video of the end-user and the photo in the ID document (facialSimilarity). 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 (1)
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

(1) If processType is documentSelfie or documentVideo, the final status depends on the result of both facialSimilarity and documentVerification. If processType is document only, the final status depends exclusively on the result of documentVerification.

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

# accepted (Onfido)

All underlying verifications have passed. This means there are no indications the document is fraudulent.

Onfido result values:

  • facialSimilarity: clear (result)
  • documentVerification: complete (status), clear (result, subResult)

This is an example of a Get process response for 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 HENDES",
            "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 HENDES",
                "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"
            }
        }
    }

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

# inconclusive (Onfido)

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

This is an example of a Get process response for 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"
            }
        }
    }

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

The following sub-sections describe potential reasons for the inconclusive status.

# facialSimilarity verifications (inconclusive)

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

  • imageIntegrity: The quality and integrity of the uploaded files were not sufficient to perform a face comparison.
    • face_detected: A single face of good enough quality is not found in both the document image and the live photo/video.
    • source_integrity: The live photo/video is not trustworthy, i.e. may have been digitally tampered, from a fake webcam or from other dubious sources.
  • faceComparison: The face in the document does not match the face in the live photo/video.
  • visualAuthenticity
    • spoofing_detection: The person in the live photo/video is not real (a spoof).
    • liveness_detected (video only): The numbers and/or head movements were not correctly executed.

Onfido result values:

  • facialSimilarity: consider (result)
  • documentVerification: any (status and subResult)

# Suspected fraud (inconclusive)

The inconclusive status could also mean that the document is suspected to be fraudulent. Reasons for this could be:

  • dataValidation: One or more algorithmically validatable elements are incorrect:
    • date_of_birth
    • expiry_date
    • mrz
    • gender
    • document_numbers
  • visualAuthenticity: One or more visual (non-textual) elements are incorrect:
    • original_document_present: A photo of a printed photo or a photo of a digital screen (may be configured to map to caution).
    • digital_tampering: Name was altered, for example.
    • picture_face_integrity: The pictures of the person identified on the document show signs of tampering or alteration. In most cases, this will focus on the primary picture. It may also apply to the secondary and tertiary pictures when documents contain them.
    • security_features: Security features expected on the document are missing or wrong.
    • template: The document doesn’t match the expected template for the document type and country.
    • fonts: Fonts in the document don’t match the expected ones.
  • dataConsistency: Asserts whether data represented in multiple places in the document is consistent, for example, between MRZ lines and OCR extracted text on passports.
    • date_of_expiry
    • document_type
    • gender
    • date_of_birth
    • nationality
    • issuing_country
    • document_numbers
    • first_name
    • last_name
  • compromisedDocument: Document is found in Onfido's database.
  • policeRecord: Document is recorded as lost, stolen or compromised.

Onfido result values:

  • facialSimilarity: clear/consider (result)
  • documentVerification: complete (status), consider (result), suspected (subResult)

# Other underlying verifications (inconclusive)

Other underlying verifications did not succeed but they don’t necessarily point to a fraudulent document:

  • imageIntegrity: The document has not sufficient quality to verify:
    • colour_picture: The image of the document is not in colour (may be configured to map to rejected)
    • conclusive_document_quality: The document image has not good enough quality to perform a fraud inspection (for example, parts of the document are not visible).
  • dataComparison (if enabled): One or more elements provided by the end-user did not match the information in the document:
    • first_name
    • last_name
    • gender
    • date_of_birth
  • dataValidation: Asserts whether the algorithmically validatable elements are correct:
    • document_expiration: The document has expired.
  • visualAuthenticity: One or more visual (non-textual) elements are incorrect:
    • face_detection: No face is detected in the document.

Onfido result values:

  • facialSimilarity: clear/consider (result)
  • documentVerification: complete (status), consider (result), caution (subResult)

# rejected (Onfido)

The verification cannot be processed further. Reasons for this may be:

  • imageIntegrity: The document has not sufficient quality to verify:
    • supported_document: The document isn’t supported by Onfido
    • image_quality: The document image quality is too low for processing.
  • ageComparison: The age of the end-user is too low:
    • minimum_accepted_age: The standard threshold is 16 years (can be configured to another minimum value).

Onfido result values:

  • facialSimilarity: clear/consider (result)
  • documentVerification: complete (status), consider (result), rejected (subResult)

Example of a rejected response for Onfido:

    {
        "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"
            }
        }
    }

As you can see, 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 field descriptions, see Response elements and fields (Onfido).

# canceled (Onfido)

The verification was canceled (by the user).

Onfido result values: documentVerification: withdrawn (result)

# 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 etc.

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

{
  "processId": "ad0eaa47-3215-4078-a417-a1292c9f4740",
  "status": "failed",
  "createdAt": "2021-04-27T13:34:49Z",
  "updatedAt": "2021-04-27T13:34:49Z",
  "provider": "onfido",
  "processType": "documentSelfie"
  "failReason": {
    "type": "expired_token",
    "message": "The token has expired, please request a new one"
  }
}

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

# Response elements and fields (Onfido)

This is an overview of the different response elements and fields for Onfido with links to further reading:

  • General process elements:processId, provider, createdAt, updatedAt and status. For more information, see the 1. Process information section.
  • finalResult element: For more information, see the 3. Normalised final result section.
  • providerSpecific elements: The facialSimilarity element contains information about the facial similarity report). The documentVerificationelement contains information about the document report. For descriptions of the fields in these two elements, see the Open API documentation > Get process.

# Electronic IDentification results

# Final status mapping between Electronic IDentification and Assure API

Electronic IDentification returns information about whether the verification was acceptedrejected, 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 processTypes, it will also have a manualApproval element.

# accepted (Electronic IDentification)

This is an example of a Get process response for 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 HENDES",
            "documentType": "passport",
            "dateOfBirth": "2002-04-29",
            "gender": "F",
            "nationality": "PRT",
            "personalIdentificationNumber": "FANTASYBANK1234567890",
            "issuingCountry": "PRT"
        }
    },
    "processType": "substantial",
    "notificationUrl": "https://labs.signicat.com/assure-test-server-dev/assure/callback",
    "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 HENDES",
            "documentType": "identityCard",
            "dateOfBirth": "2002-04-29",
            "gender": "F",
            "nationality": "PRT",
            "personalIdentificationNumber": "FANTASYBANK1234567890",
            "issuingCountry": "PRT"
        }
    },
    "processType": "substantial",
    "notificationUrl": "https://labs.signicat.com/assure-test-server-dev/assure/callback",
    "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 Enums > similarityScore)
  • 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 HENDES",
            "documentType": "passport",
            "dateOfBirth": "2002-04-29",
            "gender": "F",
            "nationality": "PRT",
            "personalIdentificationNumber": "FANTASYBANK1234567890",
            "issuingCountry": "PRT"
        }
    },
    "processType": "substantial",
    "notificationUrl": "https://labs.signicat.com/assure-test-server-dev/assure/callback",
    "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 an example of a Get process response for an Electronic IDentification process that failed:











 




{
    "status": "failed",
    "processId": "4644c061-e229-449a-b4db-643c7403bbdc",
    "provider": "eid",
    "processType": "substantial",
    "notificationUrl": "https://labs.signicat.com/proxy",
    "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 Enums > Process status and the OpenAPI documentation.

# Response elements and fields (Electronic IDentification)

This is an overview of the different response elements and fields for Electronic IDentification with links to further reading:

  • General process elements:processId, provider, createdAt, updatedAt and status. For more information, see the 1. Process information section.
  • finalResult element: For more information see the 3. Normalised final result section.
  • providerSpecific elements: The ocr element contains information obtained from the document by the OCR analysis. The manualApproval element contains information obtained after an agent has manually approved the identity request. The manualApproval fields here are similar to the ones in ocr but may have been improved. For more information, see the ocrand manualApproval elements in the OpenAPI documentation.

# ReadID results

# Final status mapping between ReadID and Assure API

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 an example of a Get process response for 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 HENDES"
        }
    },
    "finalResult": {
        "documentType": "passport",
        "firstName": "MARIA PAULA",
        "lastName": "SANTOS HENDES",
        "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 an example of a Get process response for 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 HENDES"
        }
    },
    "processType": "ready",
    "createdAt": "2021-08-04T09:18:09Z",
    "updatedAt": "2021-08-04T09:24:01Z"
}

# rejected (ReadID)

This is an example of a Get process response for 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 HENDES"
        }
    },
    "processType": "ready",
    "createdAt": "2021-08-04T09:18:09Z",
    "updatedAt": "2021-08-04T09:24:01Z"
}

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

# Response elements and fields (ReadID)

This is an overview of the different response elements and fields for ReadID with links to further reading:

# Signicat Paper results

# Final status mapping between Assure API and Signicat Paper

Assure API's final status Signicat Paper status Signicat Paper verificationStatus Signicat Paper verificationType Description
accepted COMPLETED true MRZ_ONLY or MRZ_AND_FEATURES It was possible to read the document and verify the information.
inconclusive COMPLETED true FEATURES_ONLY It was possible to read the document but could not verify the information (there is no MRZ to use for verification).
rejected COMPLETED false 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
canceled MISSING The verification was canceled.

# accepted (Signicat Paper)

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

    {
        "processId": "processId",
        "provider": "signicatpaper",
        "status": "accepted",
        "createdAt": "createdAt",
        "updatedAt": "updatedAt",
        "finalResult": {
            "firstName": "Maria Paula",
            "lastName": "Santos Hendes",
            "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 Hendes",
                "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 Hendes",
                "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 Open API documentation > Get process.

# rejected (Signicat Paper)

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


    {
        "processId": "processId",
        "provider": "signicatpaper",
        "status": "rejected",
        "createdAt": "createdAt",
        "updatedAt": "updatedAt",
        "finalResult": {
            "firstName": "Willeke Liselotte",
            "lastName": "De Bruijn",
            "dateOfExpiry": "2016-10-20",
            "gender": "F",
            "nationality": "NLD",
            "documentType": "passport",
            "documentNumber": "XY1101P52",
            "issuingCountry": "NLD",
            "dateOfBirth": "1965-03-10"
        },
        "providerSpecific": {
            "verification": {
                "type": "MRZ_ONLY",
                "status": "false"
            },
            "mrz": {
                "firstName": "Willeke Liselotte",
                "lastName": "De Bruijn",
                "dateOfExpiry": "2016-10-20",
                "nationality": "NLD",
                "gender": "F",
                "documentType": "passport",
                "issuingCountry": "NLD",
                "documentNumber": "XY1101P52",
                "dateOfBirth": "1965-03-10",
                "personalNumber": "999999990"
            },
            "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 Open API documentation > Get process.

# inconclusive (Signicat Paper)

This is an example of a Get process response for 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": "Elisabeth",
                "lastName": "Ul5Und",
                "issuingAuthority": "STATENS VEGVESEN",
                "gender": "UNEXPECTED_VALUE",
                "documentNumber": "47 00 006492 4",
                "dateOfBirth": "1979-06-28",
                "personalNumber": "280679 32635",
                "dateOfIssue": "2000-08-23"
            },
            "featuresVerification": {
                "dateOfExpiry": "MISSING",
                "lastName": "FOUND",
                "issuingAuthority": "FOUND",
                "firstName": "FOUND",
                "documentNumber": "FOUND",
                "dateOfBirth": "VALID",
                "drivingPermits": "FOUND",
                "personalNumber": "FOUND",
                "dateOfIssue": "VALID"
            }
        }
    }

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

# 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 an example of a Get process response for a Signicat Paper process that failed:

{
  "status": "failed",
    "processId": "b16e9c37-dac5-4897-b6ba-055d5a1dadc3",
    "provider": "signicatpaper",
    "redactionRequested": false,
    "providerSpecific": {},
    "notificationUrl": "https://labs.signicat.com/",
    "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 Enums > Process status and the OpenAPI documentation.

# Response elements and fields (Signicat Paper)

This is an overview of providerSpecificelements for Signicat Paper (for more details per element, see the OpenAPI documentation.):

  • verification: This element contains information about the type of verification that was done by SignicatPaper. Either it verified both the MRZ area and the textual fields of the document or it was able to only check one of those.
  • features: This element contains information that was retrieved from the fields that were obtained directly from the document.
  • mrz: This element contains the information that was retrieved from MRZ reading of the document.
  • mrzChecksum: This element contains information about the quality of some of the "feature" fields that were extracted from the document.
  • mrzVerification: This element contains information about evaluations done on some of the extracted fields in MRZ.
  • mrzFeatureMatching: This element provides matching results from comparing the values of the "expected features" in "mrz" and "fields".
  • redactionResult: Provides information about the redaction results.

Notes about redaction:

  • This information only exists if "redact" is sent in the request body.
  • The redaction results do not have any impact on the process' final status. The process status indicates the success of the verification and redaction is a parallel feature.

See the separate Redaction section for details.

# Connect results

Connect results contain the following elements in the providerSpecific area:

  • idToken: Token issued as a result of the end-user authentication. It is always returned in JWT format (encrypted or not, depending on the contract agreement).
  • userInfo: User information that can be accessed after the authentication is successful. It can be returned in JSON or JWT format (encrypted or not, depending on the contract agreement).
  • error: Displayed only if an error occurred. Information about any problem that may have happened during the authentication process. Always returned in JSON format.

Notes about finalResult in Connect processes: The Connect provider's finalResult does not follow the same rules for normalisation as with 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. Note: 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 mapping between Assure API and Connect

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 an example of a Get process response for 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 an example of a Get process response for 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 an example of a Get process response for 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: 9/15/2021, 4:02:15 PM