36C77619R0003-0003006.pdf

Identity Verification Tool (IVT)

Supplement to the

Identity Management Toolkit (IdM TK)

User Guide

May 2015

V1.0

Department of Veterans Affairs

Office of Information and Technology (OI&T)

Identity Management (IdM) ii Identity Verification Tool (IVT) Supplement to the IdM TK User Guide V1.0 May 2015

Revision History

Date Revision Description Author

05/15/15 1.0 First Release Hemmy, E. (PM), Smith, L. (Testing Engineer)

May 2015 Identity Verification Tool (IVT) Supplement to the IdM TK User Guide V1.0 iii

Table of Contents

1. Introduction

1.1. Purpose

1.2. Scope

1.3. Target Audience

1.3.1. VRM IAM Integrated Project Team (IPT)

1.3.2. VRM IAM Sub-IPT

1.3.3. Healthcare Identity Management (HC IdM)

1.3.4. MVI Development Partners

1.3.5. MVI Development Leads

1.3.6. MVI End Users

1.4. References

1.5. Definitions

1.5.1. Identity Verification Tool (IVT)

1.5.2. Experian

1.5.3. Precise ID

1.5.4. Identity Inquiry

1.5.5. Identity Response

1.5.6. Pinning and Unpinning a record

1.5.7. Correlating an IVT record

1.5.8. Unlinking a record

1.5.9. Name Lineage Inquiry

1.5.10. Ongoing Monitoring

1.5.11. MVI Score

1.5.12. IVT Score

1.5.13. Final Decision

1.5.13.1. Final Decision of RF0

1.5.13.2. Final Decision of RF1

1.5.13.3. Final Decision of RF2

1.5.13.4. Final Decision of RF3

1.5.13.5. Final Decision of ACC

2. Decisioning Strategy

3. IVT Enhancements to IdM TK

3.1. Batch Interface

3.2. System Inquiry (Real Time) Interface

3.3. User Inquiry (Single Query) Interface

3.4. Name Lineage Interface

4. System Inquiry (Real Time) Instructions iv Identity Verification Tool (IVT) Supplement to the IdM TK User Guide V1.0 May 2015

5. User Inquiry (Single Query) Instructions

6. IVT Remote Data View

6.1. Personal Information

6.2. Fraud Risk Indicator

6.3. Most Likely Fraud Type

6.4. Previous Residential Addresses

6.5. Other Matches Based on SSN

6.6. Matching Records Against Phone Search

6.7. SSN Validation

6.7.1. SSN Issue State

6.7.2. SSN Deceased Code

6.7.3. SSN Format Code

6.7.4. SSN Issue Start Range/End Range

6.7.5. SSN Issue Result Code

6.8. Fraud Shield

6.9. Gramm-Leach-Bliley Act Verification Details

6.10. Precise ID Summary Information

6.10.1. Inquiry Date

6.10.2. Inquiry Time

6.10.3. Reference ID/PIN

6.10.4. Precise ID Score

6.10.5. Matching Criteria

6.10.6. Final Decision

6.10.6.1. Final Decision of RF0

6.10.6.2. Final Decision of RF1

6.10.6.3. Final Decision of RF2

6.10.6.4. Final Decision of RF3

6.10.6.5. Final Decision of ACC

6.10.7. Address Code

6.10.8. Phone Code

6.10.9. Address Type Code

6.10.10. Address Unit Mismatch

6.10.11. Phone Unit Mismatch

6.10.12. SSN Code

6.11. Office of Foreign Assets Control (OFAC) Alert

6.12. High Risk Address Information

6.13. High Risk Phone Information

6.14. Name Lineage

7. Correlation Comparison

8. Unlinking the 200IVT Correlation

May 2015 Identity Verification Tool (IVT) Supplement to the IdM TK User Guide V1.0 v

8.1. Unlinking the 200IVT Correlation Instructions

Appendix A - Section Description and Code Translations

Glossary

Index vi Identity Verification Tool (IVT) Supplement to the IdM TK User Guide V1.0 May 2015

Table of Figures

Figure 1. No IVT Matches Found

Figure 2. VA Decisioning Strategy for IVT

Figure 3. 200IVT EXPERIAN DATA Correlation in Real Time

Figure 4. 200IVT EXPERIAN DATA Correlation Hyperlink

Figure 5. Search Experian and Add The Selected IVT Correlation to MVI

Figure 6. Identity Verification Tool Remote Data View

Figure 7. IVT Remote Data View showing OFAC Alert

Figure 8. High Risk Address and Phone Information

Figure 9. Name Lineage

Figure 10. Selecting Correlations to Compare

Figure 11. Correlation Comparison including 200IVT EXPERIAN DATA

Figure 12. Unlink Correlation tab

Figure 13. Select Correlation to Unlink

Figure 14. Submit Unlink

Figure 15. Confirmation Message

May 2015 Identity Verification Tool (IVT) Supplement to the IdM TK User Guide V1.0 vii

Table of Tables

Table 1. Experian Decision Points

Table 2. Remote Data View Section Descriptions

Table 3. Personal Information Section Field Descriptions

Table 4. Most Likely Fraud Type Codes

Table 5. SSN Deceased Codes

Table 6. SSN Format Codes

Table 7. SSN Issue Result Code

Table 8. Fraud Shield Indicators

Table 9. GLB Application Rules (by Rule Number)

Table 10. GLB Application Rules (By Category)

Table 11. Final Decision

Table 12. Address Codes

Table 13. Phone Verification Codes

Table 14. Address Type Codes

Table 15. Address Unit Mismatch Codes

Table 16. Phone Verification Unit Mismatch Codes

Table 17. SSN Codes

Table 18. OFAC Codes

May 2015 Identity Verification Tool (IVT) Supplement to the IdM TK User Guide V1.0 1

1. Introduction The Identity Verification Tool (IVT) provides the Department of Veterans Affairs (VA) with the capability to extend identity verification, authorization and resolution within the current Master

Veterans Index (MVI) system. Using Experian, an external commercial identity verification vendor, the IVT provides matching and correlation of records, as well as secondary and tertiary validation of new and existing identity records. The IVT also provides VA with information

(data and reports) related to potential matches, non-matches, and updates of identity information

(through single query). When a match occurs within the MVI graphical user interface (GUI), the

IVT will integrate the Experian Precise ID database with the Identity Management Toolkit (IdM

TK) and display the real-time Precise ID information.

1.1. Purpose

This user manual presents the interface between the VA Master Veteran Index (MVI) systems and Experian Identity Verification Services utilizing Experian’s Precise ID suite of products and options for the purpose of enhancing the existing MVI identity verification processes.

The MVI is the authoritative Enterprise Identifier for all Veterans within the Department of

Veterans Affairs. MVI collects and analyzes identity information from a variety of sources such as the Department of Defense and individual VA VistA facilities. MVI provides record correlation between several of those entities and the Primary View, which is the MVI master identity record of each Veteran. The IdM TK provides a multi-entity identity inquiry user interface that will be leveraged and adapted to provide real time identity verification inquiries to

Experian systems in the same manner currently used to access and view other external entity identity data (DoD, VistA, etc.).

The Experian Precise ID tool is essential to the success of this project. Precise ID for Identity

Screening will verify the identity of a consumer and raise flags on possible fraudulent data elements. The Identity Screening is an essential verification tool for streamlining the application processing and reducing fraud. Experian will leverage an existing production interface, Precise

ID XML Gateway API (Option 1 - ID Screening), to provide synchronous inquiry and response actions for such triggers as new identity record creation or manual user inquiries.

This user guide details the process of submitting VA identity records to Experian for verification and linking, retrieving the inquiry results and linked data elements, and making appropriate correlations for matched records within the IdM TK. It shows the screens used to display the correlations and data for individual records in MVI and explains new terminology used for the communication between MVI and Experian.

2 Identity Verification Tool (IVT) Supplement to the IdM TK User Guide V1.0 May 2015

1.2. Scope

This user guide specifies the interfaces between the VA MVI systems and Experian systems and the purpose of the data exchange. This document will explain and display all new IVT functionality and provide translations of all Experian codes.

1.3. Target Audience

The target audiences for this user guide include the following:

1.3.1. VRM IAM Integrated Project Team (IPT)

This group is responsible for approving and prioritizing all the development efforts for MVI.

1.3.2. VRM IAM Sub-IPT

This group is responsible for the detailed analysis of the Identity Management (IdM) business requirements.

1.3.3. Healthcare Identity Management (HC IdM)

This group consists of the business owners of the identity data.

1.3.4. MVI Development Partners

This group is responsible for supporting the delivery, implementation, and maintenance of the

MVI system. The current development partners include the following:

o Engility (PMO Support) o IAM Program Office o Austin Information Technology Center (AITC) o Product Support o Development Vendors: Veterans Enterprise Technology Solutions, Inc. (VETS), Hybrid, 7Delta, and Experian

1.3.5. MVI Development Leads

This group is responsible for the implementation of approved requirements.

1.3.6. MVI End Users

MVI End Users are anyone who interfaces with the IdM TK on a regular basis as part of his/her job.

1.4. References

The references used to develop this user guide include the following:

May 2015 Identity Verification Tool (IVT) Supplement to the IdM TK User Guide V1.0 3

Identity and Access Management (IAM) Identity Services, Identity Verification

Requirements Specification Document (RSD), Department of Veterans Affairs, V.1, dated February 2015

Identity Verification Interface Control Document (ICD), V.4, dated January 2015

Identity Management ToolKit (IdM TK) User Guide, V2.0.5.15, Increment 14, Maintenance Release 1, dated April 2015

1.5. Definitions

1.5.1. Identity Verification Tool (IVT)

Identity Verification Tool (IVT) will provide matching and correlating of MVI records with an external commercial identity verification vendor.

1.5.2. Experian

Experian is the external commercial identity verification vendor for the IVT.

1.5.3. Precise ID

Precise ID is an Experian-owned consumer authentication tool that utilizes data sources to produce actionable fraud alert notification and identity screening for the VA.

1.5.4. Identity Inquiry

An Identity Inquiry is the submission of VA record information from MVI systems to Experian systems for consumer matching and pinning. This transaction type occurs within the System

Inquiry (Real Time) Interface, User Inquiry (Single Query) Interface and Batch Interface.

Identity Inquiries utilize data from the MVI Primary View for matching.

1.5.5. Identity Response

An Identity Response is the transactional answer to the Identity Inquiry. The Identity Response comes from Experian systems to MVI systems in the form of matched identity data or error codes. This transaction type occurs within the System Inquiry (Real Time) Interface, User

Inquiry (Single Query) Interface and Batch Interface.

1.5.6. Pinning and Unpinning a record

Pinning of an Identity Inquiry is done on the Experian side when Experian analytics show enough confidence that an MVI inquiry record is a match to their database. Matches between

MVI and the Precise ID database will be “pinned” by Experian in order to identify which records should be targeted for ongoing monitoring by Experian.

Unpinning occurs on the Experian side if the IdM TK chooses to not accept the Experian matched record. Unpinning can occur in two circumstances. The first is when Experian has

4 Identity Verification Tool (IVT) Supplement to the IdM TK User Guide V1.0 May 2015 pinned a new MVI record, and sent the record back to the IdM TK. Upon reviewing the record, the IdM TK user then decides not to correlate the record to the Primary View based on the MVI

Score. The second is when Experian has pinned the record on their side, and sent the record back to IdM TK. Upon reviewing the record, the IdM TK user then decides to correlate the record to the Primary View. After linking the record, the user can search Experian, look at the

200IVT data view, and decide there should not be a correlation with the record. The user can then unlink the record.

Unpinning is transparent to the user and occurs as part of the existing Unlink function within

IdM TK. VA unpin records are submitted from MVI systems to Experian systems for unpinning and exclusion from the ongoing monitored population. This transaction type occurs within the

System Inquiry (Real Time) Interface, User Inquiry (Single Query) Interface and Batch Interface.

1.5.7. Correlating an IVT record

An IVT Correlation is added by selecting the Add the Selected IVT Correlation option within the IdM TK. An Identity Inquiry is sent to Experian using either the System Inquiry (Real Time)

Interface or the User Inquiry (Single Query) Interface. After Experian has matched the VA record with an Experian identity, the record will be “pinned” within Experian systems. Upon

“pinning” the record, Experian will return the identity verification details to VA. IdM TK will process the identity verification data from Experian and perform a comparison of the identity traits provided by Experian and Primary View using the probabilistic matching algorithm for reciprocal matching. The IdM TK will determine whether there is a match between the VA record and Experian identity based on the reciprocal match threshold. IdM TK shall display IVT

Search Results allowing the IdM TK user to choose whether to create or not create the 200IVT correlation using the Add the Selected IVT Correlation to MVI button. Once a correlation exists, IdM TK will display the IVT correlation information under the All Correlations box.

If an Identity Inquiry is sent to Experian using the User Inquiry (Single Query) Interface, and

Experian does NOT match the VA record with an Experian identity, the record will not be pinned on the Experian side. The IdM TK will display the phrase No IVT Matches Found under the IVT Search Results box on the Correlations page. See Figure 1. No IVT Matches

Found.

May 2015 Identity Verification Tool (IVT) Supplement to the IdM TK User Guide V1.0 5

Figure 1. No IVT Matches Found

If, during the System Inquiry (Real Time) Interface or Batch Interface, IdM TK determines there is not a match on an identity record with Experian, it will log the unmatched identities and queue them for unpinning by Experian. Logging of the unmatched records is an automated process that is transparent to the user.

1.5.8. Unlinking a record

The IdM TK User can manually unlink the IVT correlation at any time by following the Unlink procedures in the IdM TK User Guide or the Unlinking the 200IVT Correlation section on page 24 in this user guide. Unlinking disables the selected correlation within the record. An IdM TK user can also enable the inactive IVT correlation or perform a fresh search with Experian and add a new correlation replacing the inactive correlation.

1.5.9. Name Lineage Inquiry

MVI Identity records are submitted from MVI systems to Experian systems for matching and name lineage data retrieval. This transaction type occurs within the User Inquiry (Single Query)

Interface and will appear on the IVT remote data view page in the IdM TK. The Name Lineage section lists name variations that are associated with the Identity record from credit data inquiries and credit data updates to Experian.

1.5.10. Ongoing Monitoring

When a new identity is added to MVI, the record creation will trigger an identity inquiry to

Experian for verification and data response. The identity match response file will contain

Experian identity data elements such as Name, Address, SSN, DOB, etc. for the record inquired upon. If a match is made with Experian, MVI will perform a reciprocal match on the response identity data to determine if the response data meets the reciprocal match criteria. If both a match is made with Experian and the reciprocal match is within the acceptable MVI threshold, a correlation is created. Additionally, MVI will respond to Experian with records that initially matched during the Experian inquiry but did not pass the MVI reciprocal match approval threshold. These records will be removed (unpinned) from the ongoing Experian monitoring list.

The final MVI-correlated, Experian-pinned, matched, and approved population will be

6 Identity Verification Tool (IVT) Supplement to the IdM TK User Guide V1.0 May 2015 maintained by Experian to provide a mechanism for future ongoing population monitoring of data updates and fraud alerts.

1.5.11. MVI Score

MVI Score is an individual score given to a record within the IdM TK when a reciprocal comparison is performed against the Experian response data. This score is used to determine automatic correlation thresholds within MVI and can be independently adjusted specific to the

IVT project and Experian data responses.

1.5.12. IVT Score

IVT Score is an individual score, between 1 and 999, given to a record by Experian. This score can be used to help determine the overall fraud risk. The lower the IVT score, the lower

Experian’s confidence is in the identity.

1.5.13. Final Decision

The HC IdM group approved the Decisioning Strategy for the IVT which yields the following decision points: RF0, RF1, RF2, RF3, and ACC. IdM TK users should take the Final Decision code into consideration, along with the MVI Score and IVT Score, when considering whether to correlate the MVI record.

1.5.13.1. Final Decision of RF0

Based on the Identity Inquiry, Experian does not have confidence in a possible match for this record and will not pin the record. No Search results will be returned, and thus, no correlation will be possible. The RF0 decision is also given to a record that has a blocked 9013 code, indicating the consumer has placed a self-imposed block on his/her credit record. In both circumstances, the message No IVT Matches Found will be displayed under the IVT Search

Results.

1.5.13.2. Final Decision of RF1

The RF1 decision will be returned if there is no match to the inquiry address or there is low confidence in the Name/Address matching criteria. It would be pinned and able to be correlated, but may result in a lower-confidence inquiry response.

1.5.13.3. Final Decision of RF2

The RF2 decision will be returned when a record has a Precise ID score of less than 400 or has

Fraud Shield codes that indicate fraud is most likely present.

May 2015 Identity Verification Tool (IVT) Supplement to the IdM TK User Guide V1.0 7

1.5.13.4. Final Decision of RF3

The RF3 decision will be returned when the SSN for a record is considered by the SSA to be a deceased individual. The RF3 decision is given to a record that has a 9001 code, indicating the identity is deceased.

1.5.13.5. Final Decision of ACC

The Final Decision is to accept the record. Based on the Decisioning Strategy, the MVI record is acceptable with a high confidence level.

2. Decisioning Strategy The IVT Decisioning Strategy was developed through a coordinated effort between HC IdM and the development contractor, VETS, Inc. Through many iterations, the stakeholders determined how the IdM TK could best utilize the plethora of consumer identity data available in Experian's databases in order to get the best identity verification of the VA's MVI records. The strategy had to account for things such as incomplete MVI records, foreign addresses, and inaccurate entries, as well as a vast array of codes and data, in order to make the best possible match of data to provide an effective and helpful tool to the VA. The strategy shows the gates through which a record travels and the Final Decision awarded to that record based on the path it travels and the consumer data in the record. See Figure 2. VA Decisioning Strategy for IVT.

8 Identity Verification Tool (IVT) Supplement to the IdM TK User Guide V1.0 May 2015

Figure 2. VA Decisioning Strategy for IVT

Table 1. Experian Decision Points shows the decision points displayed in the Decisioning

Strategy and the subsequent steps taken by the interface depending on the Final Decision return value.

May 2015 Identity Verification Tool (IVT) Supplement to the IdM TK User Guide V1.0 9

3. IVT Enhancements to IdM TK The Identity Verification solution consists of the following software interfaces:

3.1. Batch Interface

The Batch Interface describes the MVI Core enhancements specific to the submission of batch files containing the current full MVI population to Experian for initial VA full population identity verification and to process the Experian response files for MVI correlation, rejection or further action.

3.2. System Inquiry (Real Time) Interface

The System Inquiry Interface describes the MVI Core enhancements designed to provide automated, real-time submission of identification verification inquiries for new MVI records to

Experian for matching and to process the Experian response files for MVI correlation, rejection or further action.

3.3. User Inquiry (Single Query) Interface

The User Inquiry (Single Query) Interface describes the IdM TK enhancements designed to provide user-initiated, real-time submission of identity verification inquiries to Experian for matching and to process the Experian response files for MVI correlation, rejection or further action. IdM TK users will be able to manually perform inquiries to Experian just as the users can perform inquires to DoD or VistA facilities. Users will have the option to create or reject the creation of a 200IVT EXPERIAN DATA correlation based on the MVI score, the Final

Decision, and the manual review of the identity data.

The User (Single Query) Inquiry Interface will also provide the ability to mark a record for unpinning with Experian as a direct function of the inquiry/search function of any previously established 200IVT correlation. Users will click the UNLINK button on the Compare

Correlations tab to unpin the record, in the same manner as for a DoD or VistA record.

Transparent to the user, the User Inquiry Interface will collect records marked for unpinning and submit a batch file to Experian via the Precise ID Customer Management Batch channel using the Experian STS service. These records will be unpinned within Experian systems.

3.4. Name Lineage Interface

The Name Lineage section lists name variations that are associated with the MVI Inquiry record from credit data inquiries and credit data updates to Experian. The Name Lineage Interface initiates from within the IdM TK as a result of manual user interaction. When the user clicks the hyperlink for the 200IVT EXPERIAN DATA correlation on the Compare Correlations tab, an inquiry is submitted to Experian. The immediate, synchronous Experian response will contain name lineage information. The Interface will display the name lineage information on the IVT remote data view page.

10 Identity Verification Tool (IVT) Supplement to the IdM TK User Guide V1.0 May 2015

4. System Inquiry (Real Time) Instructions User Instructions are not applicable for System Inquiry. When a new record is entered into the

IdM TK, this real time inquiry to Experian will automatically occur. Users will see the 200IVT

EXPERIAN DATA correlation when they look at the new record in the IdM TK. See Figure 3.

200IVT EXPERIAN DATA Correlation in Real Time. The 200IVT EXPERIAN DATA correlation will be added automatically if it meets or exceeds the MVI threshold match score of

13.2. Users can click the UNLINK button on the Compare Correlations tab to unlink the record, in the same manner as for a DoD or VistA correlation.

Figure 3. 200IVT EXPERIAN DATA Correlation in Real Time

The IdM TK provides the ability for the user to view the Experian data by clicking the 200IVT

EXPERIAN DATA correlation hyperlink. See Figure 4. 200IVT EXPERIAN DATA Correlation

Hyperlink.

May 2015 Identity Verification Tool (IVT) Supplement to the IdM TK User Guide V1.0 11

Figure 4. 200IVT EXPERIAN DATA Correlation Hyperlink

5. User Inquiry (Single Query) Instructions The User Inquiry Interface or Single Query feature will extend the current Remote Data display pattern utilized in the IdM TK to allow users to manually perform inquiries to the Experian

Precise ID Database. To initiate a manual identity verification inquiry to Experian, the user would follow the same steps as if the user were looking for a DoD correlation in IdM TK. Refer to sections Manage Persons and Correlations in the IdM TK User Guide or follow these steps:

1. After searching for an individual, users can click the Search Experian button to get remote data from Experian. See the top green arrow in Figure 5. Search Experian and

Add The Selected IVT Correlation to MVI.

2. IdM TK users will decide whether to correlate the record based on a review of the MVI score, the IVT score, and the IVT Final Decision. If the user decides to add an IVT correlation to MVI, the user can click the radio button next to the record to be added and then click Add The Selected IVT Correlation to MVI. See the bottom green arrow in

Figure 5. Search Experian and Add The Selected IVT Correlation to MVI. The screen does not automatically refresh to display the IVT correlation added. The user must go back to the Home screen then search for the same record again. The new 200IVT correlation will then appear under Correlations.

12 Identity Verification Tool (IVT) Supplement to the IdM TK User Guide V1.0 May 2015

Figure 5. Search Experian and Add The Selected IVT Correlation to MVI

The IdM TK user has the ability to remove the 200IVT EXPERIAN DATA correlation at any time based on a manual review of the identity data in the IVT remote data view.

6. IVT Remote Data View After clicking the 200IVT EXPERIAN DATA hyperlink, the user will be directed to the IVT remote data view page to view the Experian data associated with the MVI record. The remote data view provides a large amount of data returned from Experian. See Figure 6. Identity

Verification Tool Remote Data View.

May 2015 Identity Verification Tool (IVT) Supplement to the IdM TK User Guide V1.0 13

Figure 6. Identity Verification Tool Remote Data View

The alert pop-up message only appears for a record that has the potential to be a possible Fraud

Risk. If this alert appears, the user will have to click OK to close the pop-up before proceeding.

Also note that the field named Fraud Risk Indicator will be highlighted in red with a Y (for Yes) when Fraud Shield codes are listed in the Fraud Shield section of the IVT remote data view screen. See Fraud Shield section on page 15 in this user guide for more explanation.

Table 2. Remote Data View Section Descriptions identifies the sections within the IVT remote data view and the data displayed within those sections. In sections where there are multiple codes unique to the Experian data, a further detailed table will be provided in subsequent sections.

14 Identity Verification Tool (IVT) Supplement to the IdM TK User Guide V1.0 May 2015

6.1. Personal Information

The Personal Information section provides Personal Identifiable Information on the identity of the record. The date listed next to Updated title refers to the last time that the record was updated at Experian. Table 3. Personal Information Section Field Descriptions provides a description of all fields in the Personal Information Section.

6.2. Fraud Risk Indicator

The Fraud Risk Indicator field will alert the IdM TK user if there is a possible fraud situation associated with the MVI record. Based on the VA Decisioning Strategy, this indicator will be set to Y (for Yes) when Experian has enough data to consider potential fraud. The field will be highlighted red and an alert pop-up message with the text, Experian Potential Fraud Risk

Alert, will appear when the IdM TK user opens the IVT remote data view. See Figure 6.

Identity Verification Tool Remote Data View. The IdM TK user will have to acknowledge the alert by clicking OK on the pop-up window. The IdM TK user will then be able to further examine sections such as Fraud Shield and Gramm-Leach-Bliley Act Rules for more of an explanation of the potential fraud.

6.3. Most Likely Fraud Type

Most Likely Fraud Type (MLFT) codes indicate the type of fraud risk as calculated by the

Experian scoring model. Experian uses the MLFT code for credit information scoring models.

Table 4. Most Likely Fraud Type Codes provides a list of the fraud type codes that can be returned from Precise ID.

6.4. Previous Residential Addresses

The Previous Residential Addresses section consists of addresses from the United States Post

Office's Change of Address Master List, as well as additional sources such as utility companies

(i.e. users turn on/off their utilities when moving to a new location and have to start/stop service at an address). The IVT will list up to 10 previous addresses associated with the MVI record.

There are no codes associated with this section. If response data is sent, it will include the

Address, City, State, Zip Code, Date Reported to Experian, and Date Edited by Experian

(through updates).

6.5. Other Matches Based on SSN

This section will list any other identities that are or have been associated with the Inquiry SSN.

If no data is present in Experian Precise ID database, this section will remain empty with the phrase No Matching Records Found. If response data is sent, it will include: Last name, First

Name, Middle Initial, Address, City, State, Zip Code, Phone, Date of Birth, Date Reported to

Experian, and Date Edited by Experian (through updates).

May 2015 Identity Verification Tool (IVT) Supplement to the IdM TK User Guide V1.0 15

6.6. Matching Records Against Phone Search

The Matching Records Against Phone Search section will list addresses that are or have been associated with the Inquiry Phone Number. If no data is present in Experian Precise ID database, this section will remain empty with phrase No Matching Phone Records Found. If response data is sent, it will include: Last name, First Name, Middle Initial, Address, City, State, Zip

Code, Phone, Date of Birth, Date Reported to Experian, and Date Edited by Experian (through updates).

6.7. SSN Validation

The SSN Validation Section uses information provided by the Social Security Administration

(SSA) to validate the SSN submitted in the Inquiry. The first four columns in the SSN

Validation Section are self-explanatory from the Inquiry MVI record: Last Name, First Name, Middle Initial, and Inquiry SSN. The remaining columns are addressed here.

6.7.1. SSN Issue State

The SSN Issue State will show the two-letter state abbreviation for the state in which the SSN was issued. For example, a SSN issued in Minnesota would display MN in the SSN Issue State box.

6.7.2. SSN Deceased Code

The SSN Deceased Code is based on the Deceased Master File of the Social Security

Administration. See Table 5. SSN Deceased Codes.

6.7.3. SSN Format Code

The SSN Format Code field will identify if the Inquiry SSN is properly formatted. See Table 6.

SSN Format Codes.

6.7.4. SSN Issue Start Range/End Range

The SSN Issue Start Range is the year, in format YYYY, that the SSA began issuance for that particular SSN. The SSN Issue End Range is the year, in format YYYY, that the SSA stopped issuance for that particular SSN. There are no codes associated with these fields.

6.7.5. SSN Issue Result Code

The SSN Issue Result Code provides information on the veracity of the issuance of the SSN.

See Table 7. SSN Issue Result Code.

6.8. Fraud Shield

This section will return Fraud Shield (FS) information which is used to determine potential problems with an identity, indicating possible fraud. FS codes, a short explanatory title in the

Text column, and a description of the Fraud Shield code are displayed in the IVT remote data

16 Identity Verification Tool (IVT) Supplement to the IdM TK User Guide V1.0 May 2015 view if returned by Experian for the MVI record. Experian may return no Fraud Shield codes, one FS code or several FS codes.

If any of the following FS codes (also referred to as Fraud Shield Indicators or FSIs) are present, their severity will change the Final Decision:

FS02 Inquiry address first reported < 90 days

FS06 Inquiry age younger than SSN issue date

FS10 Inquiry address is a type of high risk address

FS13 High probability SSN belongs to another

FS14 Input SSN format invalid

FS15 Inquiry Address reported cautious

FS16 FILE: Type of high risk address

FS18 FILE: Address reported cautious

If any of the listed Fraud Shield codes are returned, then, instead of recommending accepting, the

Final Decision will be set to RF2, which means there is a potential Identity Fraud Risk. IVT will set the Fraud Risk Indicator to Y (for Yes). IdM TK users will see a Potential Fraud Risk Alert pop-up when opening the IVT remote data view. See Table 8. Fraud Shield Indicators.

6.9. Gramm-Leach-Bliley Act Verification Details

The Gramm-Leach-Bliley (GLB) Act Verification Detail Application Rules are shared application rules based on the Gramm-Leach-Bliley Act. Enacted in 1999, the GLB Act requires financial institutions to explain their information sharing practices with their customers and to explain to customers their right to ‘opt out’ if they don’t want their information shared with certain third parties.

The GLB Detail section contains the rules triggered based on inconsistencies with the inquiry data itself or compared to other inquiries submitted for the same consumer. GLB Detail Rules provide another layer of understanding of the fraud threat a record may represent. The severe conditions are also reported through the Fraud Shield codes in the Fraud Shield section.

The following sections detail the GLB Rules that could be returned for the consumer. The two tables referenced show the GLB Application Rules listed by rule number and also listed by category. The IVT remote data view shows the code listed by rule number and the description of that rule number. The GLB Application Rules (By Rule Number) would be a useful tool when looking at the results on the remote data view page. See Table 9. GLB Application Rules (by

Rule Number). The IdM TK user may choose to investigate further by referring to the category that the rule falls under, which can be done by looking at the table for GLB Application Rules

(By Category). See Table 10. GLB Application Rules (By Category).

May 2015 Identity Verification Tool (IVT) Supplement to the IdM TK User Guide V1.0 17

6.10. Precise ID Summary Information

The Experian Precise ID toolkit combines a wide range of fraud-fighting and identity authentication tools that utilize industry-leading data sources to provide an accurate picture of each applicant. Precise ID fraud scores quickly and accurately assess the level of fraud risk through underlying validation and verification score elements to ensure a person’s identity.

Included in the Precise ID Summary Information on the IVT remote data view are the following fields: Inquiry Date, Inquiry Time, Reference ID/PIN, Precise ID Score, Matching Criteria, Final Decision, Address Code, Phone Code, Address Type Code, Address Unit Mismatch, Phone

Unit Mismatch and SSN Code. These categories are explained in follow-on sections.

6.10.1. Inquiry Date

The Inquiry Date is the date from the Experian server when the inquiry record was received.

6.10.2. Inquiry Time

The Inquiry Time is the time stamp from the Experian server when the inquiry record was received.

6.10.3. Reference ID/PIN

The Reference ID/PIN is a unique alpha-numeric code assigned to each MVI record by Experian when a match is made between that MVI record and the identity found in Precise ID.

6.10.4. Precise ID Score

Precise ID Score is the score provided by Precise ID for each identity, ranging from 1-999, with a lower score representing a higher risk of fraud. The higher the score indicates the higher the confidence in the identity. Based on the HC IdM approved VA Decisioning Strategy, Precise ID scores falling below 400 will result in an RF2 Final Decision Value, indicating fraud is most likely present. The Potential Fraud Risk Alert pop-up will display when the IVT remote data view is opened.

6.10.5. Matching Criteria

Matching Criteria lists the data elements used by Precise ID to determine the match. Matching criteria values will be either Name/Address or Name/SSN depending on how the match was done by Experian for the MVI record. Based on the HC IdM approved VA Decisioning Strategy, the

IVT will try to match the MVI record on the name and address. If the address is incomplete or it is a foreign address, the IVT will attempt to match the MVI record on the name and SSN. If the

IVT cannot match either way, the IVT Search Results will display the phrase NO IVT MATCHES

FOUND.

6.10.6. Final Decision

Final Decision provides the reference code determined by the VA Decisioning Strategy based on the Experian algorithms and the processing of the MVI identity data. The HC IdM group approved the Decisioning Strategy for the IVT which yields the following decision points: RF0, RF1, RF2, RF3, and ACC. See Table 11. Final Decision. IdM TK users should take the Final

18 Identity Verification Tool (IVT) Supplement to the IdM TK User Guide V1.0 May 2015

Decision code into consideration, along with the MVI Score and IVT Score when considering whether to correlate the MVI record.

6.10.6.1. Final Decision of RF0

Based on the Identity Inquiry, Experian does not have confidence in a possible match for this record and will not pin the record. No Search results will be returned, and thus, no correlation will be possible. The RF0 decision is also given to a record that has a blocked 9013 code, indicating the consumer has placed a self-imposed block on his/her credit record.

6.10.6.2. Final Decision of RF1

The RF1 decision will be returned if there is no match to the inquiry address or there is low confidence in the Name/Address matching criteria. It would be pinned and able to be correlated, but may result in a lower-confidence inquiry response.

6.10.6.3. Final Decision of RF2

The RF2 decision will be returned when a record has a Precise ID score of less than 400 or has

Fraud Shield codes that indicate fraud is most likely present.

6.10.6.4. Final Decision of RF3

The RF3 decision will be returned when the SSN for a record is considered by the SSA to be a deceased individual. The RF3 decision is given to a record that has a 9001 code, indicating the identity is deceased.

6.10.6.5. Final Decision of ACC

The Final Decision is to accept the record. Based on the Decisioning Strategy, the MVI record is acceptable with a high confidence level.

6.10.7. Address Code

The IVT will first attempt to match on the name and address of an MVI record. There are different levels of confidence regarding the Name/Address match. The return codes are grouped by levels of confidence with 5 (Exact Match) having the highest confidence and 0 having no confidence. Address Match codes in Level 0, 1, 2, and certain codes in Level 3 will result in a

Final Decision of RF1, indicating that there is a lower confidence in the Name/Address match.

See Table 12. Address Codes.

May 2015 Identity Verification Tool (IVT) Supplement to the IdM TK User Guide V1.0 19

6.10.8. Phone Code

The Phone Code field displays the phone verification result code which verifies if the Inquiry phone number is verified against the inquiry address, or if not, what the phone number verifies

to. See Table 13. Phone Verification Codes.

6.10.9. Address Type Code

The Address Type Code categorizes what type of address the Inquiry address is, i.e. business, PO box, office, seasonal, single family dwelling. This gives another indication of possible fraud activity. See Table 14. Address Type Codes.

6.10.10. Address Unit Mismatch

The Address Unit Mismatch Code verifies the unit number of the Inquiry address. It is based on the Inquiry address and indicates whether it is part of a multi-unit dwelling. See Table 15.

Address Unit Mismatch Codes.

6.10.11. Phone Unit Mismatch

The Phone Unit Mismatch Code verifies the unit number of the address associated with the

Inquiry phone number. Like the Address Unit Mismatch code, it is based on the Inquiry address and indicates whether it is part of a multi-unit dwelling. See Table 16. Phone Verification Unit

Mismatch Codes.

6.10.12. SSN Code

The SSN code gives an overview of the accuracy of the Inquiry SSN. See Table 17. SSN Codes.

6.11. Office of Foreign Assets Control (OFAC) Alert

The Office of Foreign Assets Control (OFAC) of the United States Department of the Treasury administers and enforces economic and trade sanctions based on U.S. foreign policy and national security goals against targeted foreign countries and regimes, terrorists, international narcotics traffickers, those engaged in activities related to the proliferation of weapons of mass destruction, and other threats to the national security, foreign policy or economy of the U.S. As part of its enforcement efforts, OFAC publishes a list of individuals and companies owned or controlled by, or acting for or on behalf of, targeted countries. It also lists individuals, groups, and entities, such as terrorists and narcotics traffickers designated under programs that are not country-specific. Collectively, such individuals and companies are called Specially Designated

Nationals (SDNs). Their assets are blocked and U.S. persons are generally prohibited from dealing with them.

The OFAC box will only appear on the remote data view page when results are returned for the input record. See Figure 7. IVT Remote Data View showing OFAC Alert and Table 18. OFAC

Codes.

20 Identity Verification Tool (IVT) Supplement to the IdM TK User Guide V1.0 May 2015

NOTE: Notify the VHA 10P2 OIA HC IdM SMEs mail group if a record has an OFAC Alert.

Figure 7. IVT Remote Data View showing OFAC Alert

6.12. High Risk Address Information

The High Risk Address Information section will list addresses that were associated with the

Inquiry address and deemed to be a high risk for fraudulent activity. Examples of high risk addresses are those that are affiliated with political activity or are a public bar or tavern. If no data is present in Experian's Precise ID database, this section will not appear on the IVT remote data view. If response data is sent, this section will include Name, Address Line, City, State, Zip, and Phone. See Figure 8. High Risk Address and Phone Information. The title, High Risk

Address Information, will be followed with the number of high risk businesses associated with the Inquiry address, such as 2 high risk businesses at this address.

6.13. High Risk Phone Information

The High Risk Phone Information section will list addresses that were associated with the

Inquiry phone number and deemed to be a high risk for fraudulent activity. Examples of high risk addresses associated with a phone number are similar to those of the High Risk Address

May 2015 Identity Verification Tool (IVT) Supplement to the IdM TK User Guide V1.0 21 section: a bar's address, a politically affiliated entity's address, or any address that is not a typical residential address. If no data is present in Experian's Precise ID database, this section will not appear on the IVT remote data view. If response data is sent, this section will include Name, Address, City, State, Zip, and Phone. See Figure 8. High Risk Address and Phone Information.

The title, High Risk Phone Information, will not be followed with the number of high risk businesses associated with the phone number. Experian does not return that data; therefore, it will not populate the screen.

Figure 8. High Risk Address and Phone Information

6.14. Name Lineage

The Name Lineage section is located between the Personal Information section and the Previous

Residential Information section. See Figure 9. Name Lineage. In the few instances when the

OFAC section appears after the Personal Information section, the Name Lineage section will appear after the OFAC alert section.

The Name Lineage section lists names that are associated with the Inquiry record. Experian will return a compilation of consumer credit data collected from credit inquiries and credit data contributor updates. This section will list up to six lines of name variations that are currently on file for the Primary Applicant’s credit profile in Experian's databases.

The Name Lineage section lists name variations such as nicknames, similar names or also known as (AKA) names (i.e. James, Jim, Jimmy). The Name Lineage column headers are: First Name, Middle Initial, Last Name, 2nd Last Name, Suffix, and Type Code. The first three columns are self-explanatory. The fourth column, 2nd Last Name, will be populated with the second name of

22 Identity Verification Tool (IVT) Supplement to the IdM TK User Guide V1.0 May 2015 a hyphenated name. For example, for the last name Hewitt-Sanchez, Sanchez would be listed in the 2nd Last Name column. The Suffix column will list any suffixes related to the name (i.e. SR for Senior; JR for Junior, III for the third person with the same name). The Type Code column will list the following: A, which stands for AKA; N, which stands for Nickname; or S, which stands for Similar Name. Also, the Type Code field could be blank which means the name returned matches the input name. The Co-Applicant field in the Name Lineage section will list the first name of any person who has co-signed a loan with the Inquiry record name. The Co-

Applicant field will be blank if there is no Co-Applicant data returned.

Figure 9. Name Lineage

7. Correlation Comparison To compare the 200IVT EXPERIAN DATA to other correlations, follow the same steps as if comparing a DoD or VistA correlation in MVI. Refer to sections Manage Persons and

Correlations in the IdM TK User Guide or follow these steps.

1. Once the IdM TK user has added the IVT correlation to the IdM TK and can see the

200IVT EXPERIAN DATA correlation under the Correlations tab, the user can then compare the correlations for that MVI record.

2. The IdM TK user should place a checkmark next to the correlations in order to compare them. Next, click Compare Correlations. See Figure 10. Selecting

Correlations to Compare.

May 2015 Identity Verification Tool (IVT) Supplement to the IdM TK User Guide V1.0 23

Figure 10. Selecting Correlations to Compare

3. The IdM TK will then display the 200IVT EXPERIAN DATA correlation on the

Correlation Comparison page. All selected correlations will appear next to the

Primary View column to allow the user to compare the data fields across columns.

Figure 11. Correlation Comparison including 200IVT EXPERIAN DATA provides a view of how the 200IVT EXPERIAN DATA correlation displays on the Compare

Correlations screen in the IdM TK. The top green arrow in Figure 11. Correlation

Comparison including 200IVT EXPERIAN DATA points to the 200IVT EXPERIAN

DATA correlation column.

24 Identity Verification Tool (IVT) Supplement to the IdM TK User Guide V1.0 May 2015

Figure 11. Correlation Comparison including 200IVT EXPERIAN DATA

8. Unlinking the 200IVT Correlation After the user adds the 200IVT EXPERIAN DATA correlation, he/she will likely review the

IVT remote data view. After reviewing the IVT remote data, the IdM TK user may decide to unlink the 200IVT correlation. The IdM TK user would follow the same steps as if unlinking a

DoD or VistA correlation in MVI. Refer to section Unlink an Active Correlations in the IdM TK

User Guide or follow these steps to unlink a 200IVT EXPERIAN DATA correlation.

May 2015 Identity Verification Tool (IVT) Supplement to the IdM TK User Guide V1.0 25

8.1. Unlinking the 200IVT Correlation Instructions

1. From the Navigation Bar, click on Manage Persons >Search. Enter the search criteria for an MVI record. The Primary View is displayed.

2. Click Correlations. The Correlations are displayed.

3. Select the correlations you want to compare by putting a checkmark in the box of the correlation in the Station ID column.

4. Click Compare Correlations button.

5. The Correlation Comparison page will display with the selected correlations in side-by-side columns.

6. Scroll to the bottom of the columns and click CREATE UNLINK TASK. See

Figure 11. Correlation Comparison including 200IVT EXPERIAN DATA.

7. The Task Details tab will display with details on the task Unlink Correlation. See

Figure 12. Unlink Correlation tab.

8. At the top of the page, click Unlink Correlation tab.

Figure 12. Unlink Correlation tab

9. The page will now display the side-by-side correlations under Comparison of

Identity Traits. Click button next to the title of the column 200IVT EXPERIAN

DATA. See Figure 13. Select Correlation to Unlink.

26 Identity Verification Tool (IVT) Supplement to the IdM TK User Guide V1.0 May 2015

Figure 13. Select Correlation to Unlink

10. Scroll down to the end of the column. Click Submit Unlink button. See Figure

14. Submit Unlink. NOTE: You can check DNL if you want to perform the

Unlink and include the correlation and ICN in the DNL (Do Not Link) file.

Figure 14. Submit Unlink

May 2015 Identity Verification Tool (IVT) Supplement to the IdM TK User Guide V1.0 27

11. Pop-up message will appear with the question: Are you sure you want to

UNLINK the correlation at 200IVT? See Figure 15. Confirmation

Message. Click OK.

Figure 15. Confirmation Message

12. Page will refresh. The confirmation message is displayed indicating the correlation was successfully unlinked. Click OK. User can also navigate to the

Task Audit tab to view the completed action.

28 Identity Verification Tool (IVT) Supplement to the IdM TK User Guide V1.0 May 2015

Appendix A - Section Description and Code Translations

Table 1. Experian Decision Points

Item Decision Point Decision Point

Value

Final

Decision

Value

Un-

PIN?

Proceed to

Correlation

Additional

Information to

Display

1 No PIN Match N/A RF0 N/A N/A N/A

2 Address Code Not Match RF1 No Yes N/A

3 Result Score 9013 Blocked (9013) RF0 Yes No N/A

4 Result Score 9001 Deceased (9001) RF3 No Yes

Deceased

Indicator = Y

5 PID Score < 400 RF2 No Yes Identity Risk = Y

Fraud shield indicator

One or more FS indicators present from list determined by business group RF2 No Yes Identity Risk = Y

7 Passed All Criteria N/A ACC No Yes N/A

Table 2. Remote Data View Section Descriptions

Remote Data View Section Description Display

Personal Information Identity Information returned from

Experian

Always Displays

Office of Foreign Assets Control

(OFAC) Alert

This alert shows the match of this record against the Treasury

Department’s terrorist list.

Only displays when OFAC information is present

Previous Residential Addresses Provides additional addresses that are associated with this record.

Information obtained from sources such as utility companies; could be up to 10 addresses

Message will indicate if there are no previous residential addresses to display

Other Matches Based on SSN Other Names that have been associated with this SSN…