Persona Help Center
Database Verification (Turkey)
The ability to use the pre-built Database Verification (TR) solution is available on select plans. Customers can contact your Customer Success Manager or Customer Support for more information.
Database Verification (TR) Features
Persona's Database Verification product offers the ability to verify attributes of an individual against authoritative Turkish databases. This helps your business gain an understanding of users associated with Turkey. Using the out-of-the-box Turkish Database Verification, you can verify attributes like name, date of birth, address, and certain national identification numbers against known matches in authoritative databases.
Learn more about Database Verification.
Inputs
Using the default set up for Turkish Database Verification, users are asked to provide their details through an Inquiry flow. There are 4 required inputs for Database Verification (TR):
- Name of the individual
- Birthdate
- National ID - Türkiye Cumhuriyeti Kimlik Numarası (T.C. Kimlik)
- Address details
An Inquiry template's Screen Step that is used in the default solution for Database Verification (TR) to collect the necessary attributes to run the Verification.
Outputs
The Database Verification checks whether the information above presents a sufficient match in our Turkish databases. To learn how to understand Database Verification results, check out this article.
Configuration Options
The default attributes and match configurations on the out-of-the-box Database Verification (TR) solution are recommended settings suitable for most businesses seeking a balance of high assurance and user conversion.
Match Requirements
The Database Verification configurations and checks specify what it means for a user’s information to “match” against a known database.
The match requirements rules for Database Verification (TR) can be viewed and adjusted under the Identity Comparison check when viewing your specific Verification Template in the dashboard. It is recommended to proceed with caution when deviating from the default match requirements for Database Verification (TR) as it can directly impact your user's ability to proceed through the Inquiry flow.
An example of match requirement configurations for a Database Verification.
Plans Explained
| Startup Program | Essential Plan | Growth Plan | Enterprise Plan | |
|---|---|---|---|---|
| Database Verification (TR) | Not Available | Not Available | Available | Available |