Skip to main content
Our Database Validation process includes automated checks against authoritative sources to ensure the authenticity of user data. This page outlines the potential warnings you might encounter during the validation process.

​
Configurable Verification Settings

Your application can be configured to handle different validation outcomes by setting specific actions for each risk category:
  1. Partial Match Action
    • REVIEW: Sessions with a partial match are set to “In Review” for manual assessment.
    • DECLINE: Sessions with a partial match are automatically declined.
  2. No Match Action
    • REVIEW: Sessions with no match are set to “In Review.”
    • DECLINE: Sessions with no match are automatically declined.

​
Database Validation Warnings

Tag
Description
COULD_NOT_PERFORM_DATABASE_VALIDATION
The system couldn’t perform the database validation. Please fill in the required fields for this country to automatically proceed with the validation.
DATABASE_VALIDATION_PARTIAL_MATCH
The system identified a partial match in the database validation, requiring further investigation.
DATABASE_VALIDATION_NO_MATCH
The system identified no match in the database validation, requiring further investigation.
When a COULD_NOT_PERFORM_DATABASE_VALIDATION warning is received, the check will be automatically re-triggered once the missing KYC data is provided and saved in the console.
There’s no need for manual intervention—the system will initiate a new validation as soon as the required fields are properly populated. When this warning occurs, the session status is automatically set to In Review until the required information is provided and the validation can be completed.

​
Warning Types

Each risk is assigned a warning type based on your application’s configuration settings. Warnings fall into three severity categories: