LexisNexis InstantID Q&A Feature Guide

OneTrust supports an integration with LexisNexis' InstantID Q&A decision workflow for Data Subject Rights enterprise customers in order to verify the identity of a consumer before honoring their request. Using an implemented pre-approved decision workflow incorporated with LexisNexis products, customers can connect to their LexisNexis instance via OneTrust to initiate identity verification.

For additional information about LexisNexis and ID verification, see ID Verification Implementation Guide for OneTrust & LexisNexis and watch the Identity Verification: LexisNexis InstantID Q&A Integration official video demo.

Note:

This integration only works for accounts with published web forms.

Customer Requirements

  • OneTrust Enterprise DSAR license

  • Environment account enabled with the third-party ID verification preview feature. To enable access to this feature, please contact OneTrust Support.

  • LexisNexis environment configured with a stand-alone workflow for InstantID Q&A or workflows for Consumer InstantID.

To configure permissions and credentials

  1. Reach out to your consultant or submit a product support ticket asking to enable your account for third-party verification and to seed your system credentials.

    Ensure that you provide the following:

    • Account Name
    • Account ID
    • Environment
  2. You will also need to provide OneTrust with the following details from Experian for credential set up:
    • LexisNexis endpoint (e.g. https://staging.idms.lexisnexis.com/)
    • LexisNexis account number
    • LexisNexis username and password
    • LexisNexis workflow name

To enable ID verification integration

You can proceed with the ID verification integration once OneTrust has completed the configuration.

  1. On the Privacy Rights Automation menu, click Web forms.

    The Web forms screen appears.

  2. Hover over your desired web form to display and click the View button.

    The Web form customization screen appears.

  3. Go to the Verification tab.
  4. Enable the Enable Third-Party ID Validation setting.
  5. Select the LexisNexis configuration from the pre-configured provider list.

    LexisNexis configuration selected from the pre-configured provider list.
  6. Click the Save button.

Customization (Optional)

Form Fields

You will need to enable the form fields that will be collected from the consumer and sent to LexisNexis for validation.

Note:

Only seeded fields can and will be sent to LexisNexis. For more information, see Integration FAQs.

Email Templates

  • Verification failure email: sent to consumers when knowledge-based authentication (KBA) fails.

  • Check identity verification status email: sent when the initial request is submitted through the web form.

Verification Screens

Verification screens pull branding from Web Form > Form Styling in the Web Form Customization screen.

  • Verification Success: displays when pass is accepted.

  • Verification Failure: displays when LexisNexis returns an error.


Verification success screen with confirmation message and branding.

Verification failure screen showing error message returned by LexisNexis.

Error Screen

An error screen will be presented in the following scenarios:

  • LexisNexis service is down, resulting in time-out

  • Failed or incorrect credentials, resulting in time-out

  • Missing status or not understood response from LexisNexis service

For OneTrust customers wanting to test the error message, set up a different LexisNexis connection with an incorrect credential. The expectation is OneTrust will not be able to connect, resulting in the following error screen:


Error screen displayed when OneTrust cannot connect to LexisNexis due to incorrect credentials.

Staging vs. Production Credentials

Customers will receive two different sets of credentials from LexisNexis: one for Staging and one for Production. The information sets will include the following:

  • Account number

  • Workflow name

  • Username and password

  • URI

    Note:

    The difference in customers' URI is the account numbers and workflow names for Production and Staging.

Environment URIs

Integration FAQs

What fields can OneTrust send to LexisNexis?

OneTrust can ONLY send data to LexisNexis that is collected through the seeded web form fields, which includes the following:

  1. First Name

  2. Last Name

  3. Address

  4. City

  5. State

  6. Country

  7. Zip Code

  8. Date of Birth

  9. National ID (used to collect full or last four digits of SSN)

Which fields are required on the web form for the integration to work?

Customers will decide which fields to collect, though, not all of these personally identifiable information (PII) fields are required for the integration. Consultants should work with customers and LexisNexis to determine which PII fields the customer will require from the consumer.

Can I still add custom form fields to the web form?

Yes, but the custom fields will not be sent to LexisNexis.

If I already created a custom field for Date of Birth or SSN, can I use those fields for the LexisNexis integration?

No. You will need to replace (i.e. delete or disable) those fields and enable the seeded fields.

Will the integration still work if I rename the seeded fields (e.g. change “National ID” to “Social Security Number”)?

Yes. You can change the labels and descriptions on the seeded fields.

How can I tell which form fields are seeded?

Custom fields will have a trash icon displayed in the editor. Seeded fields cannot be deleted from the form, only disabled.


Example of a custom form field showing the trash icon in the editor

What if my credentials are incorrect or have issues connecting to LexisNexis?

If incorrect credentials are provided, such as a wrong or expired password, an error alert screen (same as seen above) will appear to the data subject. DSAR admins will see an "Error" status in the Request details screen with the request shown in the "Unverified" stage. OneTrust recommends to contact LexisNexis for further assistance and troubleshooting.

For additional reference, please see the diagram below.


Diagram showing the InstantID Q&A flow.

Quiz Workflow FAQs

Possible Verification Scenarios

Scenario

Was the Request created in OneTrust?

Quiz Generated

Quiz Answers Submitted

Quiz Answered Correctly

Request Status

Parent Verification Method to Track Overall Verification Workflow Result: LexisNexis Risk Defense Platform

Sub-verification Method to Track Step One: Verification of Initial PII Submitted Through Web Form InstantID

Sub-verification Method to Track Step Two: Grading of Quiz InstantID Q&A

Consumer successfully completes verification workflow (i.e. LexisNexis returns a result of PASS to OneTrust).

Y

Y

Y

Y

[Name of First Stage in Use Case Workflow]

Verified

Verified

Verified

Consumer completes the end-to-end verification workflow, including the quiz.

LexisNexis returns a result of FAIL to OneTrust.

Y

Y

Y

N

Unverified

Failed

Verified

Failed

Consumer submits request through OneTrust web form but a quiz is not generated.

LexisNexis returns a result of FAIL to OneTrust.

Y

N

N/A

N/A

Unverified

Failed

Failed

N/A

Consumer submits request through OneTrust web form.

LexisNexis generates quiz questions but consumer has not yet answered the quiz or abandons the quiz.

Y

Y

N

N/A

Unverified

Unverified

Verified

Unverified

Consumer submits request through OneTrust web form.

LexisNexis returns an error.

Y

N

N/A

N/A

Unverified

Error

N/A

N/A

Consumer submits request through OneTrust web form.

LexisNexis generates a quiz.

Consumer answers questions.

LexisNexis returns an error.

Y

Y

Y

Unknown

Unverified

Unverified

Verified

Error