Database Validation
Sumsub’s Database Validation solution enables businesses to confirm customer personal, identity document, and other relevant types identification details against verified records from a range of reliable data sources.
Our product flow is designed to deliver seamless end user data verification in three possible ways:
- Data Enrichment — comprehensive information enrichment by verifying unique personal identifier(s) against authoritative government, banking, and credit sources (e.g., National identification number).
- Validity Check — validating the status and ownership of the applicant's identity or document information against official government sources.
- 1x1 Matching — matching applicant’s identity information against one of the available sources in the country.
The solution helps regulated organizations meet their AML/CDD compliance requirements, while simultaneously preventing the risk of synthetic identity fraud, reducing processing times to ~4.5 seconds, and effortlessly reaching over 5 billion users globally.
Overall, Database Validation offers a trustworthy and compliant approach to customer personal and identity document checks, all through an effortless end user experience.
Use case
Fast customer identity and document validation that ensures a seamless experience through a well-recognized user flow, while adhering to both national and international regulatory requirements.
How Database Validation works
The verification process is typically completed in under 5 seconds, requiring minimal user action; it is simple and streamlined to enhance the customer journey that ensures a high level of identity proofing.
Database Validation flow
Data Enrichment
Step-by-step user verification journey:
- Applicant enters their unique personal identifier(s) on the application interface.
- System instantly retrieves all personal data and ensures its rightful ownership.
- Sumsub additionally cross-checks relevant user information to ensure a complete identity match.
- The data verification is successfully completed.

Validity Check
Step-by-step user verification journey:
- Applicant enters their unique personal identification or identity document attribute(s) on the application interface.
- System checks the information against authoritative government sources.
- Sumsub additionally cross-checks relevant user information to ensure a complete identity match and data ownership.
- The data verification is successfully completed.

1x1 Matching
Step-by-step user verification journey:
- Applicant enters their identity and address details on the application interface.
- System checks the information against all available sources in the country.
- Sumsub matches the data against one or two of the sources.
- The data verification is successfully completed.

NoteFor the supported data input methods in each Database Validation Product, please check the Solution availability table below.
Solution benefits
Database Validation delivers the following advantages to your business:
- Coverage. Reach verified records of over 5 billion customers globally with the use of a single solution.
- Compliance. Ensure full compliance with the applicable AML/CDD guidelines for electronic customer identification.
- Fraud Prevention. Enhance the onboarding security with advanced data verification and methodology.
- Seamless Integration. Easily integrate the solution into your systems through Sumsub's flexible API and SDK frameworks.
Solution availability
The following is a list of countries where Database Validation is currently available:
Note that this list is constantly updated and expanded.
|
Method |
Input data |
Output data |
Source type |
Coverage |
|---|---|---|---|---|
|
ENRICHMENT
|
|
|
Government
|
97%
|
|
|
Government
|
97%
|
|
|
|
Government
|
97%
|
|
Method |
Input data |
Output data |
Source type |
Coverage |
|---|---|---|---|---|
|
VALIDITY CHECK
|
Passport
Driver's license
|
|
Government
|
95%
|
|
|
Government
|
99%
|
|
Method |
Input data |
Output data |
Source type |
Coverage |
|---|---|---|---|---|
|
ENRICHMENT
|
|
|
Government
|
65%
|
|
|
Government
|
95%
|
|
|
|
Government
|
95%
|
|
|
|
Government
|
90%
|
|
|
VALIDITY CHECK
|
|
|
Government
|
95%
|
|
Method |
Input data |
Output data |
Source type |
Coverage |
|---|---|---|---|---|
|
VALIDITY CHECK
|
|
|
Government
|
96%
|
|
1x1 MATCHING
|
|
|
Aggregated
|
70%
|
|
Method |
Input data |
Output data |
Source type |
Coverage |
|---|---|---|---|---|
|
1x1 MATCHING
|
|
|
Aggregated
|
96%
|
|
Method |
Input data |
Output data |
Source type |
Coverage |
|---|---|---|---|---|
|
ENRICHMENT
|
|
|
Government
|
96%
|
|
|
Government
|
96%
|
|
Method |
Input data |
Output data |
Source type |
Coverage |
|---|---|---|---|---|
|
1x1 MATCHING
|
|
|
Aggregated
|
90%
|
|
Method |
Input data |
Output data |
Source type |
Coverage |
|---|---|---|---|---|
|
ENRICHMENT
|
|
|
Government
|
96%
|
|
Method |
Input data |
Output data |
Source type |
Coverage |
|---|---|---|---|---|
|
ENRICHMENT
|
|
|
Banking
|
95%
|
|
1x1 MATCHING
|
|
|
Aggregated
|
90%
|
|
Method |
Input data |
Output data |
Source type |
Coverage |
|---|---|---|---|---|
|
VALIDITY CHECK
|
|
|
Commercial
|
97%
|
|
Method |
Input data |
Output data |
Source type |
Coverage |
|---|---|---|---|---|
|
1x1 MATCHING
|
|
|
Government
|
90%
|
|
Method |
Input data |
Output data |
Source type |
Coverage |
|---|---|---|---|---|
|
ENRICHMENTK
|
|
|
Government
|
95%
|
|
Method |
Input data |
Output data |
Source type |
Coverage |
|---|---|---|---|---|
|
VALIDITY CHECK
|
|
|
Government
|
95%
|
|
Method |
Input data |
Output data |
Source type |
Coverage |
|---|---|---|---|---|
|
VALIDITY CHECK
|
|
|
Government
|
97%
|
|
1x1 MATCHING
|
|
|
Aggregated
|
90%
|
|
Method |
Input data |
Output data |
Source type |
Coverage |
|---|---|---|---|---|
|
VALIDITY CHECK
|
|
|
Government
|
96%
|
|
Method |
Input data |
Output data |
Source type |
Coverage |
|---|---|---|---|---|
|
ENRICHMENT
|
|
|
Government
|
95%
|
|
|
Government
|
95%
|
|
Method |
Input data |
Output data |
Source type |
Coverage |
|---|---|---|---|---|
|
1x1 MATCHING
|
|
|
Aggregated
|
85%
|
|
Method |
Input data |
Output data |
Source type |
Coverage |
|---|---|---|---|---|
|
ENRICHMENT
|
|
|
Aggregated
|
97%
|
|
|
Aggregated
|
97%
|
|
|
|
Government
|
97%
|
|
|
VALIDITY CHECK
|
|
|
Government
|
97%
|
CURP status codes
When verifying a CURP (Clave Única de Registro de Población), RENAPO may return different status codes depending on the individual’s registration history. These statuses indicate whether the CURP is valid and active, or has been deactivated due to various reasons such as administrative changes, death, or judicial orders.
- Active statuses (AN, AH, RCC, RCN) represent valid CURPs that can be used for identity verification.
- Inactive statuses are considered invalid and must be rejected during verification.
|
CURP status |
Description |
Registration status |
Comments |
|---|---|---|---|
|
AN |
Normal registration |
Active |
– |
|
AH |
Registration with homonymy (duplicate name handling). |
Active |
– |
|
RCC |
Registration updated with changes that affect the CURP key itself (e.g., identity or registry data changes). |
Active |
CURPs that had a modification impacting the key. |
|
RCN |
Registration updated with changes that do not affect the CURP key. |
Active |
– |
|
BAP |
Cancelled due to apocryphal/invalid supporting document. |
Inactive |
CURPs generated with fraudulent or invalid documentation. |
|
BSU |
Cancelled for non-use. |
Inactive |
CURPs with no activity since issuance (not revised, printed, or used). To reactivate, a request must be made through the CURP module. |
|
BD |
Cancelled due to death |
Inactive |
– |
|
BDM |
Cancelled administratively. |
Inactive |
CURPs deactivated at the request of the issuing authority. |
|
BDP |
Cancelled due to adoption. |
Inactive |
CURPs replaced with new identity data after adoption. |
|
BJD |
Cancelled by judicial order. |
Inactive |
CURPs deactivated following a court ruling. |
|
Method |
Input data |
Output data |
Source type |
Coverage |
|---|---|---|---|---|
|
ENRICHMENT
|
|
|
Banking
|
80%
|
|
Method |
Input data |
Output data |
Source type |
Coverage |
|---|---|---|---|---|
|
ENRICHMENT
|
|
|
Government
|
80%
|
|
|
Government
|
92%
|
|
|
|
Government
|
96%
|
|
|
|
Government
|
96%
|
|
|
|
Government
|
96%
|
|
|
|
Government
|
96%
|
|
|
|
Government
|
96%
|
|
Method |
Input data |
Output data |
Source type |
Coverage |
|---|---|---|---|---|
|
ENRICHMENT
|
|
|
Banking
|
97%
|
|
Method |
Input data |
Output data |
Source type |
Coverage |
|---|---|---|---|---|
|
ENRICHMENT
|
|
|
Government
|
96%
|
|
|
Government
|
96%
|
|
Method |
Input data |
Output data |
Source type |
Coverage |
|---|---|---|---|---|
|
1x1 MATCHING
|
|
|
Government
|
90%
|
|
Method |
Input data |
Output data |
Source type |
Coverage |
|---|---|---|---|---|
|
VALIDITY CHECK
|
|
|
Government
|
25%
|
|
Method |
Input data |
Output data |
Source type |
Coverage |
|---|---|---|---|---|
|
ENRICHMENT
|
|
|
Credit
|
67%
|
|
|
Government
|
97%
|
|
|
|
Credit
|
97%
|
|
|
|
Government
|
89%
|
|
Method |
Input data |
Output data |
Source type |
Coverage |
|---|---|---|---|---|
|
1x1 MATCHING
|
|
|
Aggregated
|
90%
|
|
Method |
Input data |
Output data |
Source type |
Coverage |
|---|---|---|---|---|
|
1x1 MATCHING
|
|
|
Government
|
90%
|
|
Method |
Input data |
Output data |
Source type |
Coverage |
|---|---|---|---|---|
|
1x1 MATCHING
|
|
|
Government
|
90%
|
|
VALIDITY CHECK
|
|
|
Government
|
97%
|
|
Method |
Input data |
Output data |
Source type |
Coverage |
|---|---|---|---|---|
|
VALIDITY CHECK
|
|
|
Government
|
96%
|
|
1x1 MATCHING
|
|
|
Aggregated
|
95%
|
|
Method |
Input data |
Output data |
Source type |
Coverage |
|---|---|---|---|---|
|
VALIDITY CHECK
|
|
|
Government
|
96%
|
|
Method |
Input data |
Output data |
Source type |
Coverage |
|---|---|---|---|---|
|
ENRICHMENT
|
|
|
Aggregated
|
92%
|
|
|
Aggregated
|
96%
|
|
|
|
Credit
|
85%
|
|
|
|
Aggregated
|
92%
|
|
Method |
Input data |
Output data |
Source type |
Coverage |
|---|---|---|---|---|
|
1x1 MATCHING
|
|
|
Government
|
90%
|
|
|
Government
|
90%
|
|
Method |
Input data |
Output data |
Source type |
Coverage |
|---|---|---|---|---|
|
ENRICHMENT
|
|
|
Government
|
95%
|
NoteSumsub currently supports three data verification methods: Enrichment, 1x1 Matching, and Validity Check. You can customize these on the go based on the country, population coverage, and regulatory requirements.
- To get started with Enrichment and Validity Check, reach out to your Customer Success Manager or Support team.
- To get started with 1x1 Matching, follow the instructions provided in this article. Read more about the decision-making logic behind these methods in this article.
Updated 13 minutes ago