Best practices

Implement Database Validation effectively.

Use Database Validation as standalone verification method

Conduct identity verification to be protected from creation of fake accounts and reduce financial risks related to identity fraud without the need to submit ID documents.

Going live with Database Validation ensures reliability of user data by leveraging a global database, minimizing gaps in information:

  1. Configure the WebSDK and MobileSDK integration or use the Sumsub API.
  2. Set up the verification logic via Workflow Builder.
  3. Verify identity documents.

Combine Database Validation with other Sumsub solutions

Level up the entire verification process and decrease associated risks by implementing Database Validation checks as both the user Pre-Screening and Post-Screening stages.

Pre-Screening

Adding Database Validation as Pre-Screening to the initial part of user verification prevents fraudsters from going through the entire onboarding journey and reduces operational costs:

  1. Get started with Database Validation.
  2. Integrate the checks with your user verification flow via Workflow Builder.

Post-Screening

Implementing Global Database verification as Post-Screening to the later stage of user verification helps minimize document and synthetic fraud rates, ultimately preventing financial business losses:

  1. Get started with Database Validation.
  2. Integrate the global checks with your user verification flow via Workflow Builder.
  3. Enjoy the reduced risks of manual errors and comprehensive post-screening process.

Rely on fallback solution

Establish multiple steps in the user data verification processes to ensure the elimination of potential drop-offs and risk gaps that might occur if the existing verification methods are insufficient:

  1. Get started with Database Validation.
  2. Integrate the global checks with your user verification flow via Workflow Builder.