What these configurations cover
Database Verification compares what an end user tells you against a record in a known database. Its configurations decide which Verification checks a template requires, and how closely a piece of information has to line up before it counts as a match.
Database Verification offers required or un-required Verification checks, acceptable countries, Identity Comparison checks with match groups that define acceptable match levels per attribute, and Verification check sub-configurations.
Where to find it in the Dashboard
- Documentation > Verification Checks lists every check available. Find the section for Database checks.
- Inquiries > Templates is where the change is made. Select a template that uses Database Verification, use the left panel of the Flow Editor to head to Verifications, select the Database Verification template, then open Checks. Some checks expand with an arrow to reveal further options.
Required checks and match requirements
Two kinds of setting sit here, and they interact.
Required checks decide what has to pass. A required check that fails fails the Inquiry, so the set you require is the strictness of the template.
Match requirements apply to the Identity Comparison check and are defined per field. They are what “match” means: whether a minor typo is tolerated, whether a common nickname counts, and how strictly dates and numeric fields are compared. Stricter requirements generally lower pass rates.
Match requirements work differently by region, and each region has its own guide:
- United States. Persona provides field specific matching logic by default, and in most cases the defaults need no customization. See Database Verification: Setting match requirements (United States).
- Outside the United States. Persona provides two options with strong defaults, full match and partial match. See Database Verification: Setting match requirements (Non-US & International).
A comparison check can only evaluate a field you actually collect. Before you set match requirements, confirm the fields used for comparison are collected earlier in your Inquiry Template flow, or are available in your Workflow.
When to reach for it
Reach for these settings when pass rates are lower than the risk justifies, or higher, and you want to move the line. For the full procedure, see Configuring Database Verification checks.
Plans Explained
Database Verification configurations by plan
| Startup Program | Essential Plan | Growth Plan | Enterprise Plan | |
|---|---|---|---|---|
| Database Verification configurations | Not Available | Available | Available | Available |