Why does a Database Verification fail?

Common causes

Here are common reasons a Database Verification may fail:

  • User's input differs from what's in a known database: There are many legitimate reasons why what a user enters may not match what's in a known database. For example, they may make typos, or put in a nickname instead of their legal first name. Or, they might have several last names, and only enter part of it. They may have entered a typo in their SSN. 
  • End users who are "thin-file": If your end user is "thin-file," they may not appear in a known database, and thus may fail a Database Verification. Thin-file means that the individual has a thin credit history or small to no financial footprint, and most Database Verifications run off of credit headers that are based on credit history. For a thin-file user, you're likely to see many "Missing" match results in their Database Verification.
  • Identity database record is out of date: The record in a known database may sometimes be out of date. For example, if an individual moves, there may be lag time between when they move and when their new address is picked up.

 

What to do next


If an applicant does not pass ID Verification, and it is not clear to you why, you can reach out to our support desk directly and we will research with our report processor directly. Email our support desk using the Need Some Help? button in the bottom right corner of the screen when logged in, or directly via support@rentapplication.net.