Understanding verification results

This section explains the structure and meaning of the verification result provided by the API. Understanding these results is crucial for making informed decisions about customer identity and risk.

Verification Result Structure

The verification result is returned as a JSON object with the following fields:

Final Result

Status:

• Type: String

• Values: true, false, unknown

• Description: The final determination of the identity's truthfulness.

  • true: The identity is considered valid based on the provided information.

  • false: The identity is considered invalid, indicating a high probability of fraud.

  • unknown: The API could not reach a conclusive determination.

Confidence:

• Type: Number (0-100)

• Description: A numerical representation of the API's confidence in the Result. A higher score indicates greater confidence.

• A confidence score of 95% or higher is required for a True or False result.

Reasoning:

• Type: String

• Description: A detailed explanation of the logic and criteria used to determine the Result.

Action Recommendations

Result: "true"

• Proceed with the user, offer them your service or product.

• Consider logging the verification result for auditing purposes.

Result: "false"

• Immediately stop the user from proceeding.

• Flag the user for potential fraud.

• Implement additional security measures to prevent future attempts.

• Inform your security team.

Result: "unknown"

• Carefully review the Reasoning field.

• Request additional information or clearer documents from the user.

• Rerun the verification with the new information.

• If after the second attempt the result is still unknown, you may want to manually review the data.

Details

The "details" section provides a granular breakdown of individual verification components, offering insights into the factors that contributed to the final verification result. This section helps you understand the specific assessments made during the verification process.

Details Structure

The "details" section contains information about each component that was verified. Each component object contains the following fields:

Component:

• Type: String

• Description: The name or type of the verification component (e.g., document, name, selfie).

Result:

• Type: String

• Values: true, false, flagged

• Description: The determination of the component's validity.

  • true: The component passed verification.

  • false: The component failed verification.

  • flagged: The component passed basic checks but raised potential concerns.

Reasoning:

• Type: String

• Description: A detailed explanation of the logic and criteria used to determine the Result.

Explanation of "Flagged" Status

The "flagged" status indicates that a component passed basic checks but exhibited characteristics that warrant further review. This could be due to:

• Slight inconsistencies in data.

• Unusual document patterns.

• Inability to verify certain information.

You should carefully review the "Reasoning" field to determine if a flagged component poses a significant risk.

Action Recommendations

True Components:

• These components are considered valid.

False Components:

• These components indicate a failure and should be treated as a high-risk indicator.

Flagged Components:

• Carefully review the "Reasoning" field to understand the potential concerns.

• Request additional information from the user if necessary.

• Make a judgment call based on the available information and your risk tolerance.

Status

• Type: String

• Values: Initiated , GeneratingLivenessCheck , AwaitingLivenessCheck, GeneratingLivenessCheck, Running, Completed, Failed

• Description: The status of the verification request.

  • Initiated: Think of this as "Request Received." You've successfully sent your request, and our system has acknowledged it and is starting to work on it.

  • GeneratingLivenessCheck : We're creating the unique liveness check links you’ll need to send to your user(s) for their liveness checks. This is an automated step in the process.

  • AwaitingLivenessCheck: Now it's the users' turn! We are waiting for them to complete the liveness check process. Their action is required to move forward with the verification.

  • Running: Great news! All the necessary information, including liveness checks, has been received. Our system is now actively reviewing everything to make a verification decision.

  • Completed: The verification process is finished, and a decision has been made. You should now be able to access the result of the verification.

  • Failed: Something went wrong during the process, and we couldn't complete your request. Please try submitting your request again. If the issue persists, you might want to check the details of your request or contact support.

Input

• Type: Map

• Description: An object containing some input for the verification, like the name of the person or business being verified (e.g., john_doe, book_business).

Associated Persons

• Type: String

• Description: Lists the names of associated persons included in a business verification request, along with the result of their verification

• Result: True, False, Unknown

• Name: The name of the associated person