Skip to main content

prompt-user-to-confirm-their-data

Depending on your use case, you may need to display the user's data to them and have them confirm it's correct.

Why We Recommend You Do This

In general, we recommend you have the user confirm their data for two reasons:

  1. Transparency: By displaying the user's data to them, you ensure they're aware of what data you've received about them.
  2. Accuracy: Although Verified provides very high quality data, we can never guarantee all data will be perfectly accurate. By having the user confirm their data, you can better avoid inaccuracies. Depending on your use case, you may want to give the user the ability to edit their data.

However, for some use cases, it may be appropriate and make more sense to not display the user's data to them or have them confirm it. Choose the approach that's best for your use case, but make sure it's compliant with regulations.

You May Be Required to Do This

If you're subject to financial data regulations — for example, if you're opening a financial account for a user with the data we return about them — you are required to have the user confirm their data.

We recommend that you:

  1. Use a form with autofilled inputs
  2. Include information about where the data comes from

a. Use a form with autofilled inputs​

We recommend that you display the user's data using a form with autofilled inputs. You only need to display the user's credential data (their identity data, like their address or birth date). You don't need to display any metadata, though you can choose to if it's relevant.

You can enable or disable each input depending on whether you want the user to be able to edit the data it contains. The upside of allowing the user to edit data is that it allows them to correct any inaccuracies. The downside is that user input isn't verified and may make fraud more likely.

Mask Social Security Numbers

We require you to mask Social Security Numbers because they're particularly sensitive:

  • Mask the first 5 digits so the client only displays the last 4 digits.
  • If you allow the user to edit the SSN, clear the entire value when they start editing (so they don't just edit the last 4 digits).

b. Include information about where the data comes from​

Including some information about where the data comes from helps users understand the magic of 1-Click Signup and feel comfortable with it. We recommend this language:

We use Verified to autofill your data from trusted sources, so you don't have to enter it manually.

You can include this information in a variety of ways, for example as a tooltip on a "Where This Data Comes From" button.

Possible Data Inaccuracies

The most common inaccuracy is an outdated address. We keep user addresses up to date as much as possible, but if the user has moved very recently, we may not yet have their current address.

Less commonly, a user may have an outdated name, if they've recently had it legally changed and we haven't yet updated it.

Some data points, like date of birth and SSN, should never change, but it's still possible (in very rare cases) for these to be inaccurate. So, if having perfectly accurate data is crucial for your use case, we recommend that you have users confirm it.