didit-database-validation

Identity verification against government records is performed by validating personal data using 1x1 and 2x2 matching across 18 countries. This cross-check prevents synthetic identity fraud by returning full_match, partial_match, or no_match structured responses.

Database validation for Latin American and Spanish documents cross-checks personal data against trusted government and financial databases. It applies country-specific field mappings across 18 countries to verify identity authenticity and mitigate fraud.

Yes, you can use database validation for fintech onboarding and risk screening. It cross-checks personal data against government records using 1x1 and 2x2 matching, delivering auditable structured responses to satisfy identity verification workflows.

To start an identity verification check using API authentication, provide a valid id_number and issuing_state. This initiates the database validation process, mapping the data to country-specific fields and returning structured matching results.

The difference between 1x1 and 2x2 matching in identity verification is the depth of the data cross-check against government and financial records. Both methods validate personal data and return structured responses categorized as full_match, partial_match, or no_match.

Yes, database validation supports country-specific field mappings for identity checks across 18 countries. This ensures accurate validation of Latin American and Spanish documents by correctly aligning personal data with local government record formats.