DevelopersGuide InstantIDQA94

Lexi sNexi s
I nstant I D
Q&A
Devel oper s Gui de
Confidential and Proprietary
FIN11016 July 2014
TheLexisNexisInstantIDQ&Aservicesarenotprovidedby"consumerreportingagencies,"asthat
termisdef inedintheFairCreditReportingAct(15U.S.C.1681,etseq.)("FCRA")orconstitute
"consumerreports,"asthattermisdef inedintheFCRA.Accordingly,neitherLexisNexisInstantID
Q&AnorRSAIdentityVerif ication,poweredbyLexisNexismaybeusedinwholeorinpartasafactor
indeterminingeligibilityforcredit,insurance,employmentoranotherpurposeinconnectionwith
whichaconsumerreportmaybeusedundertheFCRA.
LexisNexis,LexisandtheKnowledgeBurstlogoareregisteredtrademarksofReedElsevierProperties
Inc.,usedunderlicense.InstantIDisaregisteredtrademarkofLexisNexisRiskSolutionsFLInc.Other
productsorservicesmaybetrademarksorregisteredtrademarksoftheirrespectivecompanies.
2013LexisNexis.Allrightsreserved.
LexisNexisRiskSolutionsFLInc.shallnotbeliablefortechnicaloreditorialerrorsoromissions
containedherein.Theinformationinthispublicationissubjecttochangewithoutnoticeandis
providedWITHOUTWARRANTYOFANYKIND.THEENTIRERISKARISINGOUTOFTHEUSEOF
THISINFORMATIONREMAINSWITHRECIPIENT.INNOEVENTSHALLLEXISNEXISRISK
SOLUTIONSFLINC.BELIABLEFORANYDIRECT,CONSEQUENTIAL,INCIDENTAL,SPECIAL,
PUNITIVE,OROTHERDAMAGESWHATSOEVER(INCLUDING,WITHOUTLIMITATION,
DAMAGESFORLOSSOFBUSINESSPROFITS,BUSINESSINTERRUPTION,ORLOSSOFBUSINESS
INFORMATION),EVENIFLEXISNEXISRISKSOLUTIONS,HASBEENADVISEDOFTHE
POSSIBILITYOFSUCHDAMAGES.
Thelimitedwarrantiesfortheseproductsandservicesareexclusivelysetforthinthelicenseagreement
orotheragreementsaccompanyingsuchproductsorservices.Nothinghereinshouldbeconstruedas
constitutingafurtheroradditionalwarranty.Duetothenatureoftheoriginofpublicrecord
information,thepublicrecordsandcommerciallyavailabledatasourcesusedinreportsmaycontain
errors.Sourcedataissometimesreportedorenteredinaccurately,processedpoorlyorincorrectly,and
isgenerallynotfreefromdefect.Thisproductorserviceaggregatesandreportsdata,asprovidedby
thepublicrecordsandcommerciallyavailabledatasources,andisnotthesourceofthedata,norisita
comprehensivecompilationofthedata.Beforerelyingonanydata,itshouldbeindependentlyverif ied.
Contents| 3
FIN11016 July 2014
CONTENTS
Chapter 1: Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
About this Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Audience. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Guide Organization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Instruction Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Notes and Warnings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Guidelines and Best Practices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
InstantID Q&A Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Integration Toolkit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Documentation Suggestions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Support and Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Chapter 2: Getting Started. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Getting Started Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
The Architectural Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Architectural Benefits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Compliance with Industry Standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Ease of Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
A Typical User Flow with KBA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Basic Exchange of SOAP Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Anatomy of a SOAP Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Envelope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Body . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Types of Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Anatomy of a SOAP Response. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Types of Responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Contents| 4
FIN11016 July 2014
Implementation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Direct Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Netview Web Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Implementation Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Implementation Stages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Setting Up Your Application Environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
System Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Authentication Methods for Connecting to the Web Service. . . . . . . . . . . . . . . . 28
User Name and Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Client Certificate. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Change the Temporary Password for Your Integrated User Account. . . . . . . . . 30
Requesting and Installing an X.509 Client Certificate. . . . . . . . . . . . . . . . . . . . . . . . 30
Request a Client Certificate from LexisNexis . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Install a Client Certificate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Chapter 3: Designing Verification Workflows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Designing Verification Workflows Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Application Design Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Flowcharts Used in This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
iCheck Workflow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Flowchart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
iAuth Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Flowchart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
General Guidelines and Best Practices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Review the Netview Web Portal as a User Interface Sample. . . . . . . . . . . . . . . 41
Introduce the Authentication Process to the End-User . . . . . . . . . . . . . . . . . . . . 41
Obtain User Consent before Performing Verifications . . . . . . . . . . . . . . . . . . . . 42
Disable the "Submit" Button after a Message Is Sent . . . . . . . . . . . . . . . . . . . . . 42
Do Not Submit Request During Refresh or with Back Button. . . . . . . . . . . . . . . 42
Add Help Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Contents| 5
FIN11016 July 2014
Chapter 4: Integrating with Identity Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Integrating with Identity Verification Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
The Integration Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Connecting to the Identity Verification Web Service. . . . . . . . . . . . . . . . . . . . . . . . . 46
URL for Authentication with User Name and Password . . . . . . . . . . . . . . . . . . . 47
URL for Authentication with a Client Certificate . . . . . . . . . . . . . . . . . . . . . . . . . 47
SOAP End Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Using a Local WSDL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Guidelines and Best Practices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Properly Handle IP Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Send Credentials with Each SOAP Request . . . . . . . . . . . . . . . . . . . . . . . . . 49
SOAP Message Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Working with These Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
iAuth Verification: One Round of Questions, User Passes. . . . . . . . . . . . . . . . . 51
Sending an IdentityVerification Message. . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Receiving a transactionResponse Message . . . . . . . . . . . . . . . . . . . . . . . . . 55
Sending a Continuation Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Receiving Another transactionResponse Message . . . . . . . . . . . . . . . . . . . . 68
iAuth Verification: Two Rounds of Questions, User Fails . . . . . . . . . . . . . . . . . . 69
Receiving the Second Round of Questions . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Receiving the transactionResponse Message: Failed Status . . . . . . . . . . . . 71
iAuth Verification: Questions Presented Sequentially. . . . . . . . . . . . . . . . . . . . . 72
Sending the IdentityVerification Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Receiving the First Question . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Sending the First Continuation Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Receiving the Second Question. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Sending the Second Continuation Request . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Receiving the Third Question. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Sending the Third Continuation Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Receiving the transactionResponse Message Result . . . . . . . . . . . . . . . . . . 83
Contents| 6
FIN11016 July 2014
iCheck Verification: User Passes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Receiving the transactionResponse Response . . . . . . . . . . . . . . . . . . . . . . . 87
iCheck Verification: OFAC Check Enabled. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
iCheck Verification: Disambiguating Question . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Sending the Continuation Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Receiving the Next transactionResponse Message: User Passed . . . . . . . 102
iCheck Verification: User Fails Age Verification . . . . . . . . . . . . . . . . . . . . . . . . 103
Sending the IdentityVerification Request . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Receiving the transactionResponse Message. . . . . . . . . . . . . . . . . . . . . . . 106
iAuth Verification (UK): Disambiguating Question, User Passes . . . . . . . . . . . 110
Sending the Continuation Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Receiving the Set of Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Sending the Next Continuation Request . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Receiving the Next transactionResponse Message: User Passed . . . . . . . 120
iAuth Verification: Spanish . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
iLocate Match Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
transactionResponse Message with Match Summary Information . . . . . . . 124
Table Generated by Client Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Error: Transaction Expired . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Receiving the Error Message. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Error: User Under 18 Years of Age. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Data in Person Element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Verifications in the United States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Contents| 7
FIN11016 July 2014
Additional Data Required with Verification Options . . . . . . . . . . . . . . . . . . . . . 133
Recommended Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
LexID. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Retrieving a Users LexID for the First Time . . . . . . . . . . . . . . . . . . . . . . . . 134
Providing a Users LexID in a Transaction Request. . . . . . . . . . . . . . . . . . . 134
Receiving a Users LexID in a Transaction Response. . . . . . . . . . . . . . . . . 135
Verifications in the United Kingdom . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
General Guidelines and Best Practices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Send as Much Identity Data As Possible . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Include Proper Designations in Military Addresses. . . . . . . . . . . . . . . . . . . . . . 136
Do Not Send Parameters with Empty Values . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Values for xs:string Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
XML Long Data Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Enforce Consistent Phone Number Format . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
US Implementations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
UK Implementations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Store the Transaction ID Returned in a Transaction Response . . . . . . . . . . . . 138
Capture Consumers IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
If the User is Behind a Proxy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
If the User is Not Behind a Proxy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Chapter 5: Testing Your Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Testing Cycle Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Simulated Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Testing Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Connecting to the Test Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Send a Request in Simulated Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Simulator Mode Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Send a Request in Testing Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Contents| 8
FIN11016 July 2014
Chapter 6: Going Live with Your Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Going Live with Your Integration Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Connecting to the Production Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Send a Request in Live Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Chapter 7: API Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
API Reference Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
WSDL Location. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Service Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Service Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
WSDL Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Target Namespace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
WSDL Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Port Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
WSDL Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Binding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
WSDL Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
Request and Response Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
How the Message Documentation Is Organized. . . . . . . . . . . . . . . . . . . . . . . . 162
Root Element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
WSDL Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Message Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
IdentityVerification Message. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Root Element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
WSDL Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Message Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
continuation Message. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Root Element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Contents| 9
FIN11016 July 2014
Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
WSDL Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Message Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
transactionResponse Message. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Root Element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
WSDL Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
Message Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
account-activity-type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
account-maintenance-type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
account-origination-type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
account-type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
account-verification-type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
address-type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
answer-type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
answers-type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
bill-to-type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
birthdate-type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
callcenter-type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
choice-type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
choices-type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
complex-detail-type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
continue-settings-type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
credential-type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
customer-service-type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
external-responses-type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
identity-verification-settings-type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
information-type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
internationalization-type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
Contents| 10
FIN11016 July 2014
ivr-type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
online-type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
ordered-by-type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
person-type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
phone-number-type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
point-of-sale-type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
product-category-type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
product-type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
purchase-type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
question-type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
questions-type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
risk-assessment-type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
risk-component-type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
security-question-type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
settings-type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
ship-to-type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
shipping-type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
simple-detail-type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
special-feature-type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
text-type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
transaction-status-type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
transaction-type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
uk-address-type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
venue-type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
Appendix A: Error, Failure, and Information Codes . . . . . . . . . . . . . . . . . . . . . . . . 219
Error, Failure, and Information Codes Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 220
Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
Failure Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
Information Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
Contents| 11
FIN11016 July 2014
Appendix B: Question Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
Question Text Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
US Implementations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
UK Implementations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
Appendix C: Sample Request and Response Messages . . . . . . . . . . . . . . . . . . . . 244
Sample Request and Response Messages Overview . . . . . . . . . . . . . . . . . . . . . . 245
Working with the Sample Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
File Content. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
Index of Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
Appendix D: Request Message Quick Reference . . . . . . . . . . . . . . . . . . . . . . . . . . 249
Request Message Quick Reference Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
IdentityVerification Message. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
When the User is Living in the United States . . . . . . . . . . . . . . . . . . . . . . . . . . 250
When the User is Living in the United Kingdom . . . . . . . . . . . . . . . . . . . . . . . . 255
continuation Message. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258
Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
Introduction| 12
FIN11016 July 2014
Chapt er 1
I nt roduct i on
I n Thi s Chapt er
AboutthisGuide,
page13
InstantIDQ&A
Documentation,
page15
Integration
Toolkit,page16
Documentation
Suggestions,page
16
Supportand
Resources,page16
Introduction| 13
FIN11016 July 2014
About this Guide
LexisNexis
InstantID
Q&Aprovidesawebservicethatperformsrealtimeidentityverif ication.This
guidedescribeshowtointegrateyouronlineapplication,callcenterapplication,orbackenddata
processingsystemwiththewebservice,whichisreferredtointhisguideasIdentityVerif ication.
Audience
Thisguideiswrittenfordevelopersresponsibleforintegratingtheironlineapplication,callcenter
application,orbackenddataprocessingsystemwithIdentityVerif ication.
Guide Organization
Thisguideisorganizedaccordingtothedifferentstagesofintegratinganonlineapplication,call
centerapplication,orbackenddataprocessingsystemwithIdentityVerif ication.
Theguideisorganizedintothefollowingchapters.
Chapter Description
1 Introduction Generalintroductiondescribingthisguide.
2 GettingStarted ProvidesanoverviewoftheIdentityVerificationarchitectural
model;introducestheIdentityVerificationimplementation
process;describeshowtosetupyourenvironmentforan
implementation.
3 DesigningVerification
Workflows
Providesinformationtoassistyouindesigningtheverification
workflowsbetweenyourapplicationandIdentityVerification.
4 Integratingwith
IdentityVerification
DescribeshowtoconnecttotheIdentityVerificationweb
serviceandwalksyouthroughSOAPmessagingexamplesfor
varioustypesofIdentityVerificationtransactions.
Introduction| 14
FIN11016 July 2014
Conventions
Weusethefollowingconventionstorelateinformation.
I nst r uct i on St eps
ThestepsnecessarytocompleteactionsinIdentityVerif icationareprovidedinthisdocument.These
instructionsmayincludetheresultsoftheactionsorotherinformationtokeepinmindasyou
completethesteps.
5 TestingYour
Integration
DescribeshowtotestyourapplicationsintegrationwithIdentity
Verificationusingsimulationandtestingmodes.
6 GoingLivewithYour
Integration
Providesguidelinesfordeployingyourapplicationinthe
productionenvironment.
7 APIReference Providesareferencetotheapplicationprogramminginterface
fortheIdentityVerificationwebservice.
A Error,Failure,and
InformationCodes
DescribesthecodesthatmaybereturnedbyIdentity
Verification.
B QuestionText Identifiesthequestiontextdisplayedforeachquestiontype
availablewithUSandUKimplementations.
C SampleRequestand
ResponseMessages
Providescompletesamplerequestandresponsemessagesso
thatyoucanseetherelationshipoftheinputandoutputdata.
D RequestMessage
QuickReference
Providesaquickreferencetotheminimumsetofparameters
requiredinarequestmessagesenttoIdentityVerification.
Glossary DefinestermsrelatedtoIdentityVerificationandNetview.
Chapter Description
Introduction| 15
FIN11016 July 2014
Textyoushouldenterisshowninadifferentfont.
Forexample:EnterSampleDBintheDatabasef ield.
Rightclickmenusareonlydescribedininstructionsiftheyaretheonlymeansofperformingatask.
Thefollowingisanexampleofsteps.
Sample Steps
1 ClickPri nt Report.
TheWatchlistReportisdisplayedinaReportPreviewwindow.
2 ClickPri nt.
Not es and Warni ngs
This is a note icon. It precedes helpful information.

i This is a warning icon. It precedes information to help prevent you from negatively affecting your
Identity Verification system or processes.
Gui del i nes and Best Pract i ces
Designguidelinesandbestpracticesareflaggedbythefollowingicon:
Forexample:
Considertheseguidelinesandbestpracticeswhendesigningyourverif ication
workflows.
InstantID Q&A Documentation
FormoreinformationonIdentityVerif ication,seethefollowingdocumentation:
GettingStartedGuide:ProvidesanoverviewofLexisNexisIdentityVerif icationanddescribeshow
toaccesstheNetviewWebPortal.
Introduction| 16
FIN11016 July 2014
NetviewQuickReferenceGuides:Thesedocuments(forNetviewusersandoneforNetview
administrators)providequickreferenceinformationforloggingontotheNetviewPortaland
performingNetviewfunctions.
NetviewHelp(onlinehelpsystem):DescribeshowtousetheNetviewWebPortal.Theonline
helpisavailablewithinNetviewbyclickingtheHelplinkinthetoprightcorneroftheNetview
window.
YourTechnicalSolutionsConsultantcanassistyouwithaccesstothesedocuments.
Integration Toolkit
Foryourintegration,yourassignedTechnicalSolutionsConsultantwillprovideatoolkit,which
containssampleSOAPrequestandresponsemessages.Formoreinformation,seeSampleRequestand
ResponseMessages,page244.
Documentation Suggestions
Yoursuggestionsfordocumentimprovementarewelcome.Sendcommentsorsuggestionsviaemailto:
TechnicalPublications@lexisnexis.com
Support and Resources
Forcustomersupport,pleasecontactyourassignedTechnicalSolutionsConsultant.
CustomersupportisalsoavailablebycontactingLexisNexiscustomersupportat8882702836and
selectingOption1oremailingIIDQA.support@lexisnexis.com.
Getting Started| 17
FIN11016 July 2014
Chapt er 2
Get t i ng Start ed
I n Thi s Chapt er
GettingStarted
Overview,page18
TheArchitectural
Model,page18
Implementation
Process,page25
SettingUpYour
Application
Environment,
page28
Requestingand
Installingan
X.509Client
Certif icate,page
30
Getting Started| 18
FIN11016 July 2014
Getting Started Overview
ThischapterintroducestheIdentityVerif icationarchitecturalmodel.Italsopresentsahighlevel
outlineoftheIdentityVerif icationimplementationprocessanddescribeshowtosetupyour
developmentenvironment.
ForanoverviewofIdentityVerif ication,seetheGettingStartedGuide.GettingStartedalsodescribes
howtoaccesstheNetviewWebPortal,whichprovidesverif icationprocessingthroughawebportal.
The Architectural Model
IdentityVerif icationfunctionalityisprovidedbyaLexisNexishostedwebservice,sothereisnoneed
foryourcompanytodeployaKnowledgebasedAuthentication(KBA)serverwithinitsinfrastructure.
YouintegrateyourwebsiteorothercustomerfacingchannelswithIdentityVerif icationviaaSOAP
(SimpleObjectAccessProtocol)interfaceoveranHTTPSconnection.
SOAPdef inestheformatofstandardXMLmessagesthatareusedtocommunicateamongsystems.
BecausetheXMLmessageformatisstandardized,SOAPcanbeusedtocommunicateamongmultiple
computerarchitectures,languages,andoperatingsystems.TheIdentityVerif icationAPIsupports
documentstyleSOAP1.1.
HTTPSisaprotocolusedforcommunicationbetweenwebbrowsersandwebsites.Itworksinthe
samemannerasHTTP,exceptitprovidessecurityandprivacythroughtheuseofencryption.Identity
Verif icationsupports128bitSSLconnections.
Architectural Benefits
IdentityVerif icationswebservicesarchitectureoffersseveralbenef itsoverotherintegrationschemes,
includingcompliancewithindustrystandardsandeaseofintegration.
Getting Started| 19
FIN11016 July 2014
Compl i ance wi t h I ndust ry Standards
IdentityVerif icationsserviceorientedarchitecture(SOA)isstandardsbasedandWSIBasicProf ile
Version1.1compliant.WSIisanopenindustryorganizationdesignedtopromotewebservices
interoperabilityacrossplatforms,operatingsystems,andprogramminglanguages.
Ease of I nt egrat i on
BecauseitisWSIcompliant,IdentityVerif icationofferseaseofintegrationthroughawidevarietyof
developmenttoolsforMicrosoft.NETandSunsJavabasedclients.
TheIdentityVerif icationWSDL(WebServiceDef initionLanguage)providesanXMLgrammarthat
describesalltheinformationneededtoinvokethewebservicefromyourclientapplication.TheWSDL
canbeinterpretedbyaSOAPtoolkitprovidedwithyourdevelopmentenvironment,providinganeasy
interfacefordevelopingagainstthewebservice.
A Typical User Flow with KBA
ThefollowingillustrationdescribesatypicaluserflowforanIdentityVerif icationverif icationthat
usesKBAtoauthenticateauser:
Getting Started| 20
FIN11016 July 2014
Getting Started| 21
FIN11016 July 2014
Basic Exchange of SOAP Messages
TheSOAPmessagesyourapplicationsendstoIdentityVerif icationarecalledrequestmessages;the
messagesthatIdentityVerif icationreturnsarecalledresponsemessages.
Thebasicexchangeoftheserequestandresponsemessagesrequirestheinteractionofthree
components:
Consumer(User):Thisisthepersonwhoseidentityyouwishtoverify.
ClientApplication(SOAPClient):Thisisyourcompanysapplication.Itmaybeaconsumer
facingapplication,suchasawebsite,oritmaybeapointofsaleorcallcenterapplicationwherea
salesrepresentativeorcallcenteragentisgatheringinformationfromtheconsumer(user)and
enteringitintotheapplication.TheclientapplicationcreatesanXMLdocumentcontainingaSOAP
requestmessage.
IdentityVerificationWebService(SOAPServer):ThisistheLexisNexishostedwebservicethat
providestheIdentityVerif icationfunctionality.IdentityVerif icationlistensforSOAPmessages,and
distributesandinterpretsSOAPdocuments.
Thefollowingf igureillustratesthisbasicexchangeofmessages:
Aftertheuserinitiatesatransactionthatrequirestheiridentitytobeverif ied,theclientapplication
sendsaSOAPrequesttotheIdentityVerif icationserviceoverHTTPS.Uponreceivingtherequest,
IdentityVerif icationprocessesitandreturnsaSOAPresponsewiththeappropriatestatus:Passed,
Failed,Error,orQuestions.TheenduserneverinteractsdirectlywiththeIdentityVerif icationsystem,
andhasnovisibilityintotheroleplayedbyLexisNexisintheauthenticationprocess.Theclienthasfull
controlovertheinteractionwiththeenduserviatheclientapplication.
Getting Started| 22
FIN11016 July 2014
Thefollowingf igureillustratesanexamplewhereKBAisusedtoverifytheidentityofausertryingto
resetapassword.
Anatomy of a SOAP Request
ASOAPrequestisanXMLdatastructuresenttoawebserviceintheformofadocument.
ASOAPrequestsenttotheIdentityVerif icationserviceconsistsoftwomainsections:theEnvelope
andtheBody.SOAPrequestsmayalsoincludeaHeader,butoneisnotrequiredwithmessagessentto
IdentityVerif ication.
Getting Started| 23
FIN11016 July 2014
Envel ope
Thissectionidentif iesthenamespacesthatareusedbytherestofthemessage.AllrequeststoIdentity
Verif icationmustlistthesethreenamespacesinthemessageenvelope:
SOAPEnvelopenamespace
xmlns:SOAPENV="http://schemas.xmlsoap.org/soap/envelope/"
XMLSchemaforInstances
xmlns:xsi="http://www.w3.org/2001/XMLSchemainstance"
XMLSchemaforDataTypes
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
Additionalnamespacescanbedef inedwithintheBodyofthemessage.
ThefollowingcodeisanexampleofanEnvelope:
<?xmlversion="1.0"encoding="UTF8"?>
<SOAPENV:Envelope
xmlns:SOAPENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchemainstance">
ThemessageBodygoeshere.
</SOAPENV:Envelope>
Body
TheBodyisthemainpayloadofthemessage.WhenthereisnoHeaderinthemessage,theBodyisthe
f irstchildoftheEnvelope.
TheBodyidentif iestheoperationthattheapplicationwantstheIdentityVerif icationserviceto
perform,andincludesmultipleXMLelementsthatsendthenecessaryoperationparameters.Italso
identif iesanadditionalnamespace,def inedintheschema,thatdescribesdatatypesspecif icto
ThefollowingcodeisanexampleofaBody:
Getting Started| 24
FIN11016 July 2014
<SOAPENV:Body>
<m:transactionidentityverification
xmlnsm="java:com.verid.carbon.integration.datatypes">
<settings>
<accountname>Customers:ABC</accountname>
<mode>live</mode>
<ruleset>abc</ruleset>
<task>iauth</task>
</settings>
Otherelementsgohere.
</m:transactionidentityverification>
</SOAPENV:Body>
where:
<m:transactionidentityverificationindicatesthenameoftheoperationyouare
requesting.
xmlnsm="java:com.verid.carbon.integration.datatypes">identif iesanamespacewith
def initionsofIdentityVerif icationdatatypes.
As shown in the sample above, all operations must include a settings element. The parameters
required in the settings element will depend on the operation you are requesting.
Types of Requests
TheclientsystemcansendtwotypesofrequestmessagestotheIdentityVerif icationservice:
IdentityVerification:Thisisamessagethatinitiatesaverif ication.Itidentif iesthetypeof
verif icationtoperform(iAuth,iCheck)andprovidesdataabouttheuserandthetransaction.
continuation:ThisisamessagethatcontainstheusersanswerstoquestionssentfromIdentity
Verif icationtotheclientapplication.
Getting Started| 25
FIN11016 July 2014
Anatomy of a SOAP Response
ASOAPresponseisanXMLdocumentreturnedfromawebservicetotheSOAPclient.TheSOAP
responsedocumentthattheIdentityVerif icationservicereturnsisstructuredliketherequestexcept
thattheBodycontainsthetransactionresult.
Types of Responses
AtransactionResponsemessageistheresponsetoalltypesofrequestmessages.AtransactionResponse
messagetakesoneofthefollowingforms:
Questions:AresponsecontainingasetofKBAquestionsthatareintendedtobepresentedtothe
user,answered,andthensentbacktoIdentityVerif icationinacontinuationmessage.Aresponse
canbeconf iguredtoreturnquestionsinaset(allatonce)orsequentially(oneatatime).
Passed:Aresponseindicatingthattheuserwassuccessfullyauthenticated.
Failed:Aresponseindicatingthattheusercouldnotbesuccessfullyauthenticatedortheuserdid
notfulf illalloftherequirementsdef inedforthetransaction(forexample,agedidnotexceedthe
minimumagethreshold).
Error:AresponseindicatingthatIdentityVerif icationencounteredaconditionthatpreventedit
fromprocessingtheinformationitreceivednormally.
Implementation Process
TherearetwomethodsforimplementingIdentityVerif icationataclientsite:directintegrationand
theNetviewWebPortal.Manyclientsdevelopanauthenticationsolutionthatcombinesboth
methods.
IdentityVerif icationprovidestwoseparateLexisNexishostedimplementationenvironments:Testand
Production.
Getting Started| 26
FIN11016 July 2014
Direct Integration
AdirectintegrationiswhentheclientintegratestheirapplicationwithIdentityVerif icationviaaweb
servicesapplicationprogramminginterface.Thereisneveranydirectcommunicationbetweenthe
IdentityVerif icationwebserviceandtheconsumer;theclientapplicationmanagesthepresentation
layer,determiningwhen,where,andhowtheverif icationprocessispresentedtoitsendusers.
Adirectintegrationcanbeimplementedwithconsumerfacingapplications,suchasanonlinebanking
website,andwithapplicationsusedbycallcenterorretailserviceagents.
Netview Web Portal
Netviewprovidesverif icationprocessingwithaneasytousewebportalthatcanbeimplementedat
callcentersandretailserviceagents.Clientswhouseadirectintegrationforperformingverif ications
stillf indNetviewusefulforrunningreportsaboutthoseverif icationtransactions.
ForinformationonaccessingNetview,seetheGettingStartedGuide.OnceloggedontoNetview,you
canaccesstheNetviewonlinehelpsystemforinstructiononusingtheNetviewfeatures.
Implementation Environments
IdentityVerif icationprovidestwoseparateLexisNexishostedimplementationenvironments:
Test:Thisenvironmentallowsyoutotestanewdirectintegrationortestchangestoanexisting
directintegration.Thetestenvironmentisfullyfunctional,allowingyoutotestallfeaturesofyour
applicationbeforegoingintoproduction.
Production:Thisenvironmentisusedwhenyougolivewithyourintegration.Initially,youmay
golivewithapilotprogramthatdeploystoalimitedaudienceonly.
You are not billed for transactions processed in the test environment; you are billed for transactions
in the production environment unless those transactions are run in testing or simulated mode. If you
have questions about transaction billing, contact your LexisNexis Technical Solutions Consultant.
Getting Started| 27
FIN11016 July 2014
Implementation Stages
ThefollowingtablebrieflydescribesthemainstagesinvolvedinanIdentityVerif icationdirect
integrationimplementation:
Stage For more information, see...
SettingupYourApplicationEnvironment
Duringthisstage,youcheckthatyoumeetallsystemrequirements
andobtainthenecessarycredentialsforconnectingwiththe
IdentityVerificationserviceviaanSSLconnection.
"SettingUpYourApplicationEnvironment"
onpage28
DesigningVerificationWorkflows
Duringthisstage,youidentifyanddesigntheverification
workflowsbetweenyourapplicationandIdentityVerification.
Typically,youwillworkwithothermembersofyour
implementationteam(suchasusabilityexpertsandbusiness
analysts)whoareresponsiblefordefiningtheflowofinformation
toyourendusers.
"DesigningVerificationWorkflows"onpage
36
IntegratingwiththeIdentityVerificationWebService
Duringthisstage,youmodifyyourclientapplicationscodeto
communicatewiththeIdentityVerificationwebserviceviaSOAP
messages.
"IntegratingwithIdentityVerification"on
page44
TestingYourIntegration
Duringthisstage,youtestyourintegrationinaLexisNexishosted
testenvironment.Firstyouuseasimulatorthatenablesyouto
forcethedifferentresponsetypestoensurethatyourintegrationis
handlingthemproperly.Thenyoutestyourintegrationagainsta
testserver.
Duringthisiterativestage,youreviewandreviseyourapplication
basedontestresults.
"TestingYourIntegration"onpage140
RunningaPilotandGoingLive
Duringthisstage,youdeployyourapplicationintheproduction
environment.Youmayfirstrunapilotprogramintheproduction
environmenttotestyourapplicationonacontrolledbasis.
"GoingLivewithYourIntegration"onpage
151
Getting Started| 28
FIN11016 July 2014
Setting Up Your Application Environment
Beforebeginningyourintegration,followthesestepstosetupyourapplicationenvironment:
1 Checkthatyoumeetallsystemrequirements.Formoreinformation,see"SystemRequirements"on
page28.
2 ObtaincredentialsforconnectingwiththeIdentityVerificationwebservice.Formoreinformation,see
"AuthenticationMethodsforConnectingtotheWebService"onpage28.
3 LogontotheNetviewWebPortaltochangethepasswordforyourintegrateduseraccount.Formore
information,see"ChangetheTemporaryPasswordforYourIntegratedUserAccount"onpage30.
System Requirements
Yourclientapplication(SOAPclient)mustsupportthefollowing:
DocumentstyleSOAP1.1
WSIBasicProf ileVersion1.1compliantservices
SincetheIdentityVerif icationAPIrunsasawebservice,thereisnothingthatyouneedtoinstall
relatedtotheIdentityVerif icationAPI.TheonlysoftwareyouneedtoinstalltousetheAPIisthe
softwarefortheintegrateddevelopmentenvironmentthatyouusetowriteormodifyyourapplication.
Forexample,ifyouplantowriteyourclientapplicationinJava,youwillneedtoinstallJavaandalsoa
SOAP1.1compatibletoolkit.
Authentication Methods for Connecting to the Web Service
AllcommunicationbetweenyourapplicationandtheIdentityVerif icationwebservicemustusethe
HTTPSprotocol.HTTPSisasecureversionofHTTP.ItworksinthesamemannerasHTTP,exceptit
providessecurityandprivacythroughtheuseofencryptionusinga128bitSSL(SecureSocketsLayer)
connection.
IdentityVerif icationofferstwowaystoauthenticatetothewebservice:usernameandpasswordora
clientcertif icate.
Getting Started| 29
FIN11016 July 2014
ContactyourITsecuritygroupwhendecidingwhichauthenticationmethodtousewithyour
application.
User Name and Password
IdentityVerif icationcanauthenticatecredentialsviaausernameandpasswordasdef inedinthe
HTTP1.0Protocol'sBasicAuthenticationScheme.Theuserforadirectintegrationisreferredtoasan
integrateduser.AnintegratedusercanbeusedtoconnectwithIdentityVerif icationthroughitsAPI.
YourLexisNexisTechnicalSolutionsConsultantprovidesyouwiththeusernameandtemporary
passwordforyourintegrateduser.Afterreceivingthesecredentials,youshouldlogontoNetviewto
changethepassword.Forinstructions,see"ChangetheTemporaryPasswordforYourIntegratedUser
Account"onpage30.
Every new user, including an integrated user, is automatically prompted to change password the first
time the user logs on to Netview. Therefore you should log on to Netview with your integrated user
credentials before you go live with your application. If you log on to Netview and change the
password of your integrated user while your application is live, your application will not be able to
connect with Identity Verification because it will be sending the old password.
Cl i ent Cer t i f i cat e
YoucanauthenticateyourconnectionwiththeIdentityVerif icationwebserviceusinganX.509client
certif icate.Aclientcertif icate,alsoknownasanSSLcertif icateoradigitalcertif icate,isacertif icate
thatusesadigitalsignaturetobindapublickeywithinformationabouttheholderofthecertif icate.
X.509isthestandardthatdef ineswhatgoesintothecertif icate.Whenyourapplicationattemptsto
connecttoIdentityVerif icationusingaclientcertif icate,theIdentityVerif icationwebserververif ies
thecertif icateisauthenticbeforeestablishingtheconnectionandallowingthetransactionto
continue.
Formoreinformationonrequestingandinstallingaclientcertif icate,see"RequestingandInstalling
anX.509ClientCertif icate"onpage30.
Even if you plan to use a client certificate, you still need the credentials for your accounts integrated
user because you need that user name and password to log on to Netview to request a client
certificate.
Getting Started| 30
FIN11016 July 2014
Change the Temporary Password for Your Integrated User Account
WhenyourLexisNexisTechnicalSolutionsConsultantcreatedanintegrateduseraccountforyour
implementation,theTechnicalSolutionsConsultantsetapasswordfortheaccount.Beforeyou
continuewithyourimplementation,logontoNetviewtochangethistemporarypassword.
Change the Temporary Password for Your Integrated User Account
1 AccessthefollowingURLinyourInternetbrowsertologontotheNetviewWebPortal:
https://netview.verid.com/transact/
2 EntertheusernameandpasswordprovidedtoyoubyyourLexisNexisTechnicalSolutionsConsultant
andthenclickOK.
YouareautomaticallypromptedwiththeChangePasswordform.
3 IntheNewpasswordandVerifypasswordfields,enteranewpassword.Thepasswordmustcontainat
leasteightcharactersandmeetallthefollowingcriteria:
Containsalphauppercasecharacters(AZ)
Containsalphalowercasecharacters(az)
Containsnumericcharacters(09)
Containsnonalphanumericcharacters(forexample,!,?,%)
Thefirstthreecharactersareunique
Be sure to enter a very strong password. As this password is sent with API requests, and does not
need to be remembered or typed by a Netview user, you can create a complex password.
4 ClickChangePassword.
Requesting and Installing an X.509 Client Certificate
ToconnectwiththeIdentityVerif icationwebserviceusingaclientcertif icate,youmustrequesta
clientcertif icatefromLexisNexisandtheninstallthatcertif icateonthemachinewhereyourclient
applicationisrunning.
Getting Started| 31
FIN11016 July 2014
A certificate expires one year after it is issued. An expired certificate cannot be reissued; you must
instead request a new certificate. If a certificate expires for an integrated user, your application will
no longer be able to perform any transactions until a new certificate is issued and your application is
updated to use that certificate. To avoid this situation, LexisNexis sends a reminder emails to users
31 and 14 days before the certificate expires.
Request a Client Certificate from LexisNexis
Before You Begi n
CheckthatyourLexisNexisTechnicalSolutionsConsultanthasprovidedyouwiththecredentials
(usernameandpassword)foryouraccountsintegrateduser.
WorkwithyourITsecuritygrouptogenerateakeypairandaPKCS10Certif icateSigningRequest
(CSR).
Thekeypairisapairofcryptographickeys,apublicencryptionkeyandaprivatedecryptionkey,
thatareusedtoprotectthecertif icate.
TheCSRisamessagesenttoacertificateauthority(CA)toapplyforaclientcertificate.Inthisprocedure,
yousubmityourCSRthroughNetview,whichsendsittoIdentityVerificationsinternalCA.
The procedure for generating a key pair and CSR varies depending on the certificate utilities
available with your development platform. For example, the keytool utility is provided with the Java
Development Kit (JDK).
Whencreatingthekeypair,followtheserules:
Whenpromptedforcommonnameorusername,enterthenameforyouraccountsintegrated
userasprovidedtoyoubyyourLexisNexisTechnicalSolutionsConsultant.
SpecifyRSAforthekeyalgorithmand2048forthekeysize.TheLexisNexisproductsecuritypolicy
requiresthatsystemsusecertificateswith2048bitkeys;1024bitkeysaresupportedforbackward
compatibilityonly,andwillnolongerbesupportedinafuturereleaseofIdentityVerification.
WhencreatingtheCSR,savethePKCS10CSRfilewitha.csrfileextension.
Request a Client Certificate
1 AccessthefollowingURLinyourInternetbrowsertologontoNetview:
2 EntertheusernameandpasswordprovidedtoyoubyyourLexisNexisTechnicalSolutionsConsultant
andthenclickOK.Besuretousethesameintegratedusernamespecifiedforthecommonnamewhen
creatingtheCSR.
Getting Started| 32
FIN11016 July 2014
3 FromtheConfigurationmenu,clickSSL Certi fi cati ons > Request a Certi fi catetodisplaythe
CertificateRequestInformationform.
4 Pastethecontentsofthe.csrfileintothetextboxandclickSubmi t.
Getting Started| 33
FIN11016 July 2014
Iftherequestcannotbeprocessed(forexample,ifthereissomethingwrongwiththerawrequest),an
errormessageprovidemoresinformation.Resubmitanewrequestaccordingtotheguidelines
provided.
Iftherequestcanbeprocessed,aStatusdialogboxopens,listingtheIDnumberassignedtothe
request.
IdentityVerif icationsendsanotif icationemailtotheRISGLOVerIDCertReqemailgroupandtoan
authorizedpartyatyourcompany.Theauthorizedpartywasconf iguredbyaLexisNexisTechnical
SolutionsConsultantwhenyourcompanysaccountwascreated.Theauthorizedpartyisresponsible
forapprovingthecertif icaterequest.Youarenotif iedbyemailwhenyourcertif icaterequestis
approved.
Foraflowchartofthecertif icateapprovalprocess,seetheGettingStartedGuide.
Next St eps
AfteryoureceiveanemailfromLexisNexisindicatingthatyourcertif icaterequestisapproved,install
thecertif icate.Forinstructions,see"InstallaClientCertif icate"onpage33.
Install a Client Certificate
Before You Begi n
Requestaclientcertif icatefromLexisNexis.Forinstructions,see"RequestaClientCertif icatefrom
LexisNexis"onpage31.
Getting Started| 34
FIN11016 July 2014
Install the Certificate
1 AccessthefollowingURLinyourInternetbrowsertologontotheNetviewWebPortal:
2 Entertheusernameandpasswordusedwhenyousubmittedthecertificaterequest.
3 FromtheConfigurationmenu,selectMy Prof i l e.
4 ClicktheCerti fi catestab.
5 Inthestatuslineforthecertificateyourequested,clickI nstal l todisplaytheStatusdialogbox.
Thetoptextboxdisplaysthecontentsofasinglecertificate;thebottomtextboxdisplaysa
certificatechaininPKCS7format.
6 Copythecontentsofthecertificate(intheformatrequiredbyyoursystemscertificatestore)intoanew
textfile.Forexample,copythefileinPKCS7formatintoafilecalledIdentityVerificationCertificate.p7b.
Getting Started| 35
FIN11016 July 2014
7 Usethecertificationutilityavailableforyourplatformtoimportthenewcertificateintothecertificate
store.
Designing Verification Workflows | 36
FIN11016 July 2014
Chapt er 3
Desi gni ng Veri f i cat i on
Workfl ows
I n Thi s Chapt er
Designing
Verif ication
Workflows
Overview,page37
Application
DesignProcess,
page37
FlowchartsUsed
inThisChapter,
page38
iCheckWorkflow,
page38
iAuthWorkflow,
page39
General
Guidelinesand
BestPractices,
page41
FIN11016 July 2014
Designing Verification Workflows Overview
Duringthedesignstageofyourimplementation,youneedtoidentifyanddesigntheverif ication
workflowsbetweenyourapplicationandIdentityVerif ication.
Thischapterpresentsatypicalworkflowforthethreeverif icationtypesthatIdentityVerif icationcan
perform.Italsoprovidesgeneraldesignguidelinesandbestpracticesthatyoushouldconsiderduring
thedesignprocess.
Beforeyoulookattheworkflowsinthischapter,youshouldreviewtheGettingStartedGuide,
IntroducingIdentityVerif icationchapter,tounderstandeachverif icationtypeandtheoverall
IdentityVerif icationtransactionflow.
Application Design Process
Todesigntheverif icationworkflowsforyourclientapplication,youtypicallyworkwithother
membersofyourimplementationteam(suchasusabilityexpertsandbusinessanalysts)whoare
responsiblefordef iningtheflowofinformationtoyourendusers.
BecauseIdentityVerif icationishighlyconf igurable,oneofthef irststepsinthedesignprocessis
understandinghowyouraccounthasbeenconf igured.Customconf igurationsettingsareorganized
intoparametersets,alsoknownasrulesets,thatgovernmanyaspectsofthesystemsbehavior.For
example,aparametersetdef inesthequestiontypestouseduringaniAuthverif ication.
WhenyourIdentityVerif icationaccountwasestablished,aLexisNexisTechnicalSolutionsConsultant
workedwithyouoramemberofyourteamtocompletetheSystemConf igurationForm.Thisform
recordeddatathattheTechnicalSolutionsConsultantthenusedtocreateaparametersetappropriate
foryourimplementation.WhenyousendaSOAPrequesttoIdentityVerif ication,youmustspecify
whichparametersettouseforthattransaction.Youmayhavemultipleparametersetsforyouraccount
totriggerdifferentbehaviorfordifferenttransactions.Fordetailsonspecifyingtheappropriate
parameterset,see"SendinganIdentityVerif icationMessage"onpage51.
FIN11016 July 2014
Flowcharts Used in This Chapter
Eachworkflowinthischapterisdescribedbyaflowchart.Theflowchartsarecolorcodedtohelpyou
quicklyunderstandwhodoeswhatintheflow:
iCheck Workflow
AniCheckperformsidentityproof ingtoconf irmthatanidentityexistsbycheckingthatthedata
abouttheuser(forexample:name,address,andphonenumber)matchesdatacollectedfrompublic
recordsandotherdatasources.Inaddition,aniCheckcanperformidentityfraudmonitoringand/or
riskassessmentcheckstoauthenticateauser.
Formoreinformationonidentityproof ing,identityfraudmonitoring,andriskassessment,seethe
GettingStartedGuide.
FIN11016 July 2014
Flowchart
The Error will describe the type of
issue, such as a missing
parameter.
End User
Initiates transaction
with client
application.
The end user initiates
a transaction that you
have integrated with
the Identity
Verification service.
Client Application
Prompts user for
data needed for
transaction (e.g.,
name, address).
End User
Enters requested
data.
Identity Verification
Can the user be located?
Client Application
Sends SOAP
request to Identity
Verification.
Can the information be
processed?
Identity
Verification
Performs any
configured preID
checks.
Does the user pass the
preID checks?
Identity
Verification
Performs any
configured postID
checks.
postID checks?
Identity
Verification
Performs iLocate.
Identity
Verification
Sends result of
Error to client
application.
Identity
Verification
Sends result of
Failed to client
application.
Identity
Verification
Sends result of
Passed to client
application.
YES
YES YES
NO
NO
NO
NO
YES
FIN11016 July 2014
iAuth Workflow
AniAuthisdesignedforhighrisktransactions.First,IdentityVerif icationperformsidentityproof ing
toconf irmthatanidentityexists.ThenitusesKBA,riskassessment,andidentityfraudmonitoringto
authenticationtheuser.
Formoreinformationonidentityproof ing,KBA,identityfraudmonitoring,andriskassessment,see
theGettingStartedGuide.
FIN11016 July 2014
Flowchart
The Error will describe the type of
issue, such as a missing
parameter.
End User
Initiates transaction
with client
application.
The end user initiates
a transaction that you
have integrated with
the Identity
Verification service.
Client Application
Prompts user for
data needed for
transaction (e.g.,
name, address).
End User
Enters requested
data.
Can the user be located?
Client Application
Sends SOAP
request to Identity
Verification.
processed?
Identity
Verification
Performs any
configured preID
checks.
preID checks?
Identity
Verification
Builds profile and
generates
questions.
Identity
Verification
Sends questions to
client application.
Client Application
Presents questions
to end user.
End User
Answers questions.
Client Application
Sends SOAP
request with
answers to Identity
Verification.
processed?
Identity
Verification
Scores answers.
User passes KBA
questions?
Identity
Verification
Performs any
configured postID
checks.
postID checks?
Identity
Verification
Performs iLocate.
Identity
Verification
Sends result of
Error to client
application.
Identity
Verification
Sends result of
Failed to client
application.
Identity
Verification
Sends result of
Passed to client
application.
YES
YES YES
YES
YES
YES
NO
NO
NO
NO
NO
NO
FIN11016 July 2014
General Guidelines and Best Practices
Considertheseguidelinesandbestpracticeswhendesigningyourverif ication
workflows.
During the design process, keep in mind that Identity Verification will not perform a verification on a
person who is less than 18 years old. For an example of the message returned when a user is less
than 18, see "Integrating with Identity Verification" on page 44.
Review the Netview Web Portal as a User Interface Sample
TheNetviewWebPortalistheIdentityVerif icationInternetapplicationforcallcenterrepresentatives.
IfyouarenotplanningtouseNetview,butareplanningtointegrateyourowncallcenterapplication
withIdentityVerif ication,thenNetviewprovidesausefuldesignsample.Reviewitforideason
designingtheuserinterfaceofyourcallcenterintegration.
Introduce the Authentication Process to the End-User
Beingaskedpersonalquestionsmayalarmanenduserifheorshedoesnotunderstandthereasonfor
thequestioning.Whenperformingauthenticationswheretheenduserisexpectedtoanswerquestions,
LexisNexisrecommendsthatyouinformtheuser,inadvanceofthequestions,thatforsecurityreasons
theymustanswerseveralquestionstoproceedwiththetransaction.Forexample:
Foryourownprotection,youmaybeaskedtoanswerafewmultiplechoicequestionsinordertoverify
youridentity,andpreventsomeoneelsefromfraudulentlyusingyourpersonalinformation.
Youshouldalsodisplaybriefinstructionstoassisttheenduserinproperlyansweringthequestions,for
example:
PleaseselectallanswersthatapplyandclickSubmi t Answers.Besuretoanswerallquestions.
FIN11016 July 2014
Obtain User Consent before Performing Verifications
Toperformverif ications,IdentityVerif icationmayusedataprovidedbyacreditreferenceagency.
Consultwithyourlegaldepartmenttounderstandyourcompanyslegalrequirementsforobtaininga
usersconsenttotheverif icationprocess.Itmaybenecessaryforyoutodisplayaconsentagreementin
yourapplication.
Disable the "Submit" Button after a Message Is Sent
DisablethebuttonusedtosubmitanIdentityVerif icationmessageoracontinuationmessageafterthe
informationissubmittedtopreventtheuserfrompressingitmorethanonce.Submittingan
IdentityVerif icationmessagemultipletimesduringthesameverif icationattemptmayresultinthe
billingofunwantedtransactions.Submittingacontinuationmessagemultipletimesmayresultina
transactionResponsemessagecontaininganinvalid_transaction_continueerrorcode.
Do Not Submit Request During Refresh or with Back Button
Ensurethatyourapplicationdoesnotsubmitarequestwhentheuserrefreshesthebrowserorclicks
theBackbuttonasitcouldresultinduplicateIdentityVerif icationorcontinuationrequestsduringthe
sameverif icationattempt.SubmittinganIdentityVerif icationmessagemultipletimesduringthesame
verif icationattemptmayresultinthebillingofunwantedtransactions.Submittingacontinuation
messagemultipletimesmayresultinatransactionResponsemessagecontainingan
invalid_transaction_continueerrorcode.
Add Help Text
Helptextisreturnedasahelptextelementwithcertainquestiontypes.Thistextmaybehelpfulto
userswhentheyareattemptingtoanswerspecif icquestions.Forexample,thefollowinghelptextis
returnedwithaquestionthataskstheusertoselectanaddressfromalist:
FIN11016 July 2014
<helptext>
<language>english</language>
<statement>Theaddresslistedmaybepartial,
misspelledorcontainminornumbering
variationsfromyouractualaddress</statement>
</helptext>
Designyourapplicationtodisplaythishelptextbelowtheassociatedquestionorinapopupwindow
accessedbyaHel pbutton.
Foranexampleofamessagethatreturnshelptext,see"Questions"onpage57.
< Back Next > Cancel
With which of the following addresses have you ever
been associated?
123 Main Street
523 Harrison Blvd.
27 Fertiledale Road
8 Swallow Street
397 Marblehead Way
The address listed may be partial, misspelled
or contain minor numbering variations from
your actual address.
Integrating with Identity Verification| 44
FIN11016 July 2014
Chapt er 4
I nt egrat i ng wi t h
I dent i t y Veri f i cat i on
I n Thi s Chapt er
Integratingwith
Identity
Verif ication
Overview,page45
TheIntegration
Process,page45
Connectingtothe
Identity
Verif icationWeb
Service,page46
SOAPMessage
Examples,page49
DatainPerson
Element,page132
General
Guidelinesand
BestPractices,
page135
FIN11016 July 2014
Integrating with Identity Verification Overview
ThischapterprovidesinformationneededtointegrateyourclientapplicationwiththeIdentity
Verif icationwebservice.
The Integration Process
WhenbuildinganapplicationtointerfacewiththeIdentityVerif icationwebservice,youmustconnect
withtheIdentityVerif icationservicesWSDL(WebServicesDef initionLanguage)usingthetools
availablewithyoursoftwaredevelopmentenvironment.AWSDLisadocumentwritteninXMLthat
describesawebservice.ItprovidesalltheinformationaSOAPclientneedstointerfacewiththe
service,includingthelocationofthewebservice(knownastheendpoint)andadescriptionofthe
operationssupportedbytheservice.
YourdevelopmentenvironmentincludesaSOAPtoolkitthatcaninterprettheWSDLtogeneratecode
forbuildingSOAPrequestmessagesthatIdentityVerif icationcanunderstandandconsumingSOAP
responsemessagesthatIdentityVerif icationsendstoyourclientapplication.
FIN11016 July 2014
Thef igureonthenextpageshowslinesfromtheIdentityVerif icationWSDLthatdescribeoneofthe
datatypesyoucanincludeinaSOAPrequest.
ForadetaileddescriptionoftheWSDL,see"APIReference"onpage154.
ForannotatedexamplesofSOAPrequestandresponsemessages,see"SOAPMessageExamples"on
page49.
FortheURLoftheIdentityVerif icationwebserviceWSDL,see"ConnectingtotheIdentity
Verif icationWebService"onpage46.
Foralistofguidelinesandbestpracticesthatyoushouldconsiderduringyourintegration,see"General
GuidelinesandBestPractices"onpage135.Somespecif icguidelinesarealsopresentedthroughoutthis
chapterwiththeirrelatedtopics.
Connecting to the Identity Verification Web Service
AllcommunicationbetweenyourapplicationandtheIdentityVerif icationwebservicemustusethe
HTTPSprotocol.HTTPSisasecureversionofHTTP.ItworksinthesamemannerasHTTP,exceptit
providessecurityandprivacythroughtheuseofencryptionusinga128bitSSL(SecureSocketsLayer)
connection.
These lines of the WSDL
describe the address-
context-type, which can be
included in a SOAP request to
identify the context of a
persons address. The
restriction element identifies
all valid string values for that
data type.
FIN11016 July 2014
WhenyourclientapplicationsendsaSOAPrequesttotheIdentityVerif icationwebservice,itmust
includeauthenticationcredentialsintheHTTPheaderoftherequest.Withoutthesecredentials,your
applicationcannotconnectwiththewebservice.
YoucanconnecttotheIdentityVerif icationwebserviceusingeitherusernameandpasswordora
clientcertif icate.Forinformationonobtainingauthenticationcredentials,see"Authentication
MethodsforConnectingtotheWebService"onpage28.Youcanusethesamecredentialsforboththe
testandproductionenvironments.
YouneedtopointtoadifferentURLdependingontheauthenticationmethodthatyouareusing.
URL for Authentication with User Name and Password
IfyouareauthenticatingwithusernameandpasswordwhenconnectingwithIdentityVerif ication,
usetheWSDLatoneofthefollowinglocationstoaccessthecorrectSOAPendpoint.
URL for Authentication with a Client Certificate
Ifyouareusingaclientcertif icatewhenconnectingwithIdentityVerif ication,usetheWSDLatoneof
thefollowinglocationstoaccessthecorrectSOAPendpoint.
Environment WSDL URL
Production https://netview.verid.com/carbon/ws?WSDL
Test https://staging.verid.com/carbon/ws?WSDL
Environment WSDL URL
Production https://netviewcert.verid.com/carbon/ws?WSDL
Test https://stagingcert.verid.com/carbon/ws?WSDL
FIN11016 July 2014
SOAP End Points
TheIdentityVerif icationWSDLidentif iestheSOAPendpointofthewebservice.Theendpointisthe
URLtowhichyourclientapplicationneedstoconnect.Thefollowingtableidentif iestheendpointfor
eachenvironmentandtypeofauthentication.
Using a Local WSDL
Toimproveperformance,youcansaveacopyoftheIdentityVerif icationWSDLlocallyanduseit
duringintegration.
Guidelines and Best Practices
ConsidertheseguidelinesandbestpracticeswhenconnectingwiththeIdentity
Verif icationwebservice.
Pr oper l y Handl e I P Addr esses
TheIdentityVerif icationserviceissetuptoensurethatserviceinterruptionsareataminimum.This
resultsintheoccasionalneedforLexisNexistochangeitsIPaddressestofailoverduringemergencies
Environment
Type of
Authentication
End Point
Production usernameand
password
https://netview.verid.com:443/carbon/ws
clientcertificate https://netviewcert.verid.com:443/carbon/ws
Test usernameand
password
https://staging.verid.com:443/carbon/ws
clientcertificate https://stagingcert.verid.com:443/carbon/ws
FIN11016 July 2014
ortoprovidesystemavailabilityduringscheduledmaintenanceperiods.Followtheseguidelineswhen
connectingwiththeIdentityVerif icationwebservice:
DonotaccesstheIdentityVerif icationwebserviceviaadirectIPaddress.Instead,accessitviathe
locationslistedonthepreviouspage.
Donotusehosttableentriesand/orindef initelycachetheIdentityVerif icationIPaddresswhenit
isinitiallyresolvedatthestartupofyourwebserver.Instead,LexisNexisrecommendsthatyouuse
theTTL(TimetoLive)valuesontheLexisNexispublishedDNSlookups.Ifitisnotpossiblefor
youtousetheLexisNexisTTLvalues,thenyoushouldperformDNSlookupsregularly(aminimum
ofevery10minutes)ontheIdentityVerif icationURLtoensureanychangesarepickedupassoonas
possible.
Usinghosttableentriesorindef initelycachingtheIPaddresscanresultintheinabilityofyour
IdentityVerif icationtransactiontraff ictoseamlesslymigratewhenanIPaddressischanged.
Send Credent i al s wi t h Each SOAP Request
Includeyourauthenticationcredentials(username/passwordorclientcertif icate)intheHTTPheader
ofallSOAPrequeststoavoidanHTTP401(Unauthorized)errorcode.
SOAP Message Examples
ThisfollowingsectionsprovideexampleSOAPmessagerequestsandresponsesforthefollowing
verif icationscenarios:
iAuthVerif ication:OneRoundofQuestions,UserPasses,page51
iAuthVerif ication:TwoRoundsofQuestions,UserFails,page69
iAuthVerif ication:QuestionsPresentedSequentially,page72
iCheckVerif ication:UserPasses,page84
iCheckVerif ication:OFACCheckEnabled,page94
iCheckVerif ication:DisambiguatingQuestion,page97
iCheckVerif ication:UserFailsAgeVerif ication,page103
iAuthVerif ication(UK):DisambiguatingQuestion,UserPasses,page110
FIN11016 July 2014
iAuthVerif ication:Spanish,page121
iLocateMatchSummary,page124
Error:TransactionExpired,page130
Error:UserUnder18YearsofAge,page131
Working with These Examples
Considerthefollowingwhenworkingwiththeseexamples:
TheseexamplesshowjustafewofthemanytypesofIdentityVerif icationtransactionresults.Itis
importantthatyoubuildyourapplicationtohandleallpossibleresultsforeachtypeofverif ication
thatyouwillrequest.
Theseexampleswalkyouthroughthemaincontentoftherequestsandresponsesbutdonotshow
themessagesintheirentirety.Forsamplesofcompletemessages,see"SampleRequestand
ResponseMessages"onpage244.
WhilemostoftheexamplesshowaUStransaction,youcanstillrefertothemforaUK
implementation.ThedifferencebetweenaUSandaUKtransactionistheaddressparameterused
tosendtheaddressofthepersonbeingverif ied.ThetwoUKexamplesshowtheUKaddress
parameter.
Theseexamplesshowthemostcommonlyincludedparametersforeachmessage.Foracomplete
referencetotheIdentityVerif icationAPI,see"APIReference"onpage154Foraquickreferenceto
theminimumsetofparametersrequiredinarequestmessage,see"RequestMessageQuick
Reference"onpage249.
Youshouldreviewthef irstiAuthexamplebeforelookingattheothers;itprovidesmoredetailon
thecommonelementsincludedinallmessages.
FIN11016 July 2014
iAuth Verification: One Round of Questions, User Passes
ThissectionstepsthroughthecontentofexamplerequestandresponsemessagesforaniAuth
verif icationwheretheuserispresentedwithoneroundofauthenticationquestionsbeforebeingable
toresethisonlinebankingpassword.
In the iAuth Verification: One Round of Questions, User Passes example, the user is associated
with an account for which the LexID feature is enabled, therefore, this users LexID is returned in the
transaction response (see"Transaction Status" on page 55). For more information, see "LexID" on
page 134.
Additionally, the user is associated with an account for which the Verification and Fraud Prevention
Services integration feature is enabled, therefore, a response from LexisNexis
Flex ID is included
in the main TransactionResponse message (see"External Responses" on page 60). For more
information on the Verification and Fraud Prevention Services integration feature, contact your
Technical Solutions Consultant.
Sendi ng an I dent i t yVeri f i cat i on Message
YourclientapplicationshouldsendanIdentityVerif icationmessagetoinitiateaverif ication.The
IdentityVerif icationmessageidentif iesthetypeofverif icationtoperformandprovidesdataonthe
useryouaretryingtoauthenticate.
Root El ement
Thetransactionidentityverif icationelementistherootelementforthismessage.Itidentif iesa
namespacethatdef inesdatatypesspecif ictotheIdentityVerif icationwebservice.Thisrootelement
containschildelementsthatprovideallthedetailsthatIdentityVerif icationneedstoperformthe
verif ication.
<SOAPENV:Envelopexmlns:SOAPENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:SOAPENC="http://schemas.xmlsoap.org/soap/encoding/"xmlns:xsi="http://www.w3.org/
2001/XMLSchemainstance"xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<SOAPENV:Body>
xmlns:m="java:com.verid.carbon.integration.datatypes">
Set t i ngs
Thesettingselementprovidesaccountinformationanddetailsabouttheverif icationyouwouldlike
IdentityVerif icationtoperform.Thisexampledef inestheseparameters:
FIN11016 July 2014
accountname(mandatory):TheaccountnameprovidedtoyoubyLexisNexis.
mode(mandatory):Specif iesthatthetransactionshouldberuninlivemodeintheproduction
environment.Otherpossiblevaluesinclude:
simulated:Usethismodetosimulatethetransaction,returningacannedresponse.
testing:Usethismodetofullyprocessthetransactioninthetestenvironment.
pilot:Usethismodetofullyprocessthetransactionintheproductionenvironmentduringa
pilotprogram.
ruleset(mandatory):Specif iesthattheabcparametersetshouldgoverntheoperationofthe
transaction.TheparametersetisyourcompanyscustomIdentityVerif icationconf iguration;
contactyourLexisNexisTechnicalSolutionsConsultantifyoudonotknowthenameofyour
parameterset.Formoreinformationonparametersets,see"ApplicationDesignProcess"onpage
37.
task(mandatory):RequeststhatIdentityVerif icationperformaniauthverif ication.Theother
possiblevalueisicheck.
referenceid(optional):Allowsyoutospecifyaninternaltrackingnumberforthetransaction.The
valueisreturnedinthetransactionResponsemessageinthereferenceidparameter.Ifyougenerate
reportsusingtheNetviewWebPortal,thevalueofthisparameterdisplaysintheReference#f ield.
i Do not use this parameter to specify any personal identifiable information or sensitive data such as
credit card numbers. While all Identity Verification data is secure and tightly controlled, the
reference-id value is not encrypted and therefore does not have the highest level of security.
<settings>
<mode>live</mode>
<task>iauth</task>
<referenceid>12879876tr</referenceid>
</settings>
Person
Thepersonelementprovidespersonalinformationabouttheenduser.Thefollowingparametersare
requiredwhenverifyingtheidentityofauserlivingintheUnitedStates.Foranexampleofaperson
elementforauserlivingintheUnitedKingdom,see"iAuthVerif ication(UK):Disambiguating
Question,UserPasses"onpage110.
namef irst
FIN11016 July 2014
namelast
addresswiththesechildelements:
addressstreet1
addresscity
addressstate
addresscontext:Specif iesthatthisisthepersonsprimaryaddress.Otherpossiblevaluesare
secondary,previous,vacation,business,andother.
Whenenteringamilitaryaddress,besuretoincludethepropermilitarydesignations.
Formoreinformation,see"IncludeProperDesignationsinMilitaryAddresses"onpage
136.
Valuesarealsodef inedforthefollowingoptionalparameters:customerid,phonenumber,ande
mail.
<person>
<namefirst>John</namefirst>
<namelast>Sample</namelast>
<customerid>904390490390349</customerid>
<email>jsample@example.com</email>
<address>
<addressstreet1>1MainStreet</addressstreet1>
<addresscity>Boston</addresscity>
<addressstate>MA</addressstate>
<addresszip>02101</addresszip>
<addresscontext>primary</addresscontext>
</address>
<phonenumber>
<phonenumber>1234567890</phonenumber>
<phonenumbercontext>home</phonenumbercontext>
</phonenumber>
</person>
FIN11016 July 2014
Iftherequestincludeda9digitsocialsecuritynumber,thentheaddresswouldbe
optional.Foramatrixofpersonelementdatarequirements,basedonverif icationtype,
see"DatainPersonElement"onpage132.
Transact i on
Thetransactionelementspecif iesdetailsaboutthetypeoftransactionthepersonisperforming.Itcan
includeeitheranaccountverif icationelementorapurchaseelement.Thisexampleincludesan
accountverif icationelementthatdef inestheseparameters:
accountmaintenance(optional):Specif iesthatthetransactionisanaccountmaintenancetask.
Insteadofaccountmaintenance,youcanspecifyaccountactivityoraccountorigination.Inthis
example,theaccountmaintenanceelementdef inestheseparameters:
accountcategory:Specif iesthatthetransactionisinthebankingcategory.Therearemany
possiblevalues,includingbrokerage,retail,publicrecords,andcreditcards.
accountmaintenancecategory:Specif iesthatthepersonisattemptingtoperformapass
wordreset.
See"APIReference"onpage154foracompletelistofpossibleaccountandaccountmaintenance
categories.
account:Specif iesdetailsabouttheaccount.Thiselementdef inesavalueforthecustomerid,
whichisitsonlymandatoryparameter.
venue(mandatory):Specif iesthatthetransactionistakingplaceonline.Otherpossiblevaluesare
callcenter,batch,netview,pointofsale,customerservice,andivr.Thevenueparameteralso
specif iesthecredentialmethod(basic)andtheIPaddressofthemachineonwhichtheuser
initiatedthetransaction.
activitydate(mandatory):Specif iesthedateandtimeofthetransactioninISO8601format.
<transaction>
<accountverification>
<accountmaintenance>
<accountcategory>banking</accountcategory>
<accountmaintenancecategory>passwordreset<
/accountmaintenancecategory>
<account>
</account>
</accountmaintenance>
<venue>
FIN11016 July 2014
<online>
<credential>
<credentialmethod>basic</credentialmethod>
<ipaddress>216.40.82.206</ipaddress>
</credential>
</online>
</venue>
<activitydate>20100501T10:04:12.803Z</activitydate>
</accountverification>
</transaction>
</SOAPENV:Body>
</SOAPENV:Envelope>
Recei vi ng a t ransact i onResponse Message
IdentityVerif icationrespondstotheIdentityVerif icationrequestwithatransactionResponsemessage.
Thismessageprovidesdetailsaboutthestatusofthetransactionanddirectionsforcontinuing.
Root El ement
Thetransactionresponseelementistherootelementforthismessage.Itidentif iesanamespacethat
def inesdatatypesspecif ictotheIdentityVerif icationwebservice.Thisrootelementcontainschild
elementsthatprovideallthedetailsthatIdentityVerif icationneedstoperformtheverif ication.
env:Envelopexmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<env:Header/>
<env:Body>
<java:transactionresponse
xmlns:java="java:com.verid.carbon.integration.datatypes">
Transact i on Stat us
Thetransactionstatuselementismandatory.Itprovideshighleveldetailsaboutthecurrentstatusof
thetransaction,thetransactionnumber,andtheresultofthetransaction.Inthisexample,itincludes
theseparameters:
FIN11016 July 2014
transactionresult(mandatory):Inthisexample,theresultisquestions,whichmeansthatthe
messagecontainsasetofKBAquestionswhichshouldbepresentedtotheenduser,answered,and
thensentbacktoIdentityVerif icationinacontinuationmessage.
Otherpossibletransactionresultvaluesare:
passed:Thepersonwassuccessfullyauthenticated.
failed:Thepersoncouldnotbelocated,didnotpasstheauthenticationprocess,ordidnot
fulf illalloftherequirementsdef inedforthetransaction(forexample,thepersonsagedid
notexceedtheminimumthreshold).
error:IdentityVerif icationencounteredaconditionthatpreventeditfromprocessingthe
receivedinformationnormally(forexample,therequestdidnotincludearequiredparame
ter).
transactionid:ThisisauniqueIDassignedtothetransactionbyIdentityVerif ication.Youmust
includethisIDwhensendinganycontinuationmessagesassociatedwiththetransaction.
transactionrequestid:ThisisauniqueIDassignedtothespecif icrequest.
accountstransactionidandreferenceid:Bothoftheseparametersreturnthereferenceid,as
providedbytheclientapplicationintherequestmessage.Whenareferenceidisnotprovidedin
therequest,itisreturnedas0.
The reference-id is returned in two parameters to maintain backward-compatibility with applications

designed with an earlier version of the Identity Verification web service.
specialfeature:Inthisexample,thespecialfeatureparameterreturnsaLexID,whichisaunique
identif ierassignedtotheuserbyLexisNexis.ALexIDisreturnedinthisexamplebecausetheLexID
featureisenabledfortheusersaccount.Formoreinformation,see"LexID"onpage134.
<transactionstatus>
<transactionid>1020025529082</transactionid>
<transactionrequestid>1020026858609</transactionrequestid>
<accountstransactionid>12879876tr</accountstransactionid>
<transactionresult>questions</transactionresult>
<specialfeature>
<specialfeaturecode>LexID</specialfeaturecode>
<specialfeaturevalue>007976577987</specialfeaturevalue>
</specialfeature>
</transactionstatus>
FIN11016 July 2014
Quest i ons
Thequestionselementprovidesasetofquestionsthattheclientapplicationshouldusetochallenge
theenduser.Forthepurposeofthisdocument,onlyoneofthequestionsisshowninthisexample.The
questionsetid,questionid,andchoiceidvaluesneedtobereturnedinthecontinuationmessageto
identifytheusersanswer.
Dependingonyouraccountconf iguration,questionsarereturnedeitheroneatatime(sequentially)or
inagroup.Thisexampleshowsthemreturnedinagroup.Presentingquestionssequentiallyis
recommendedwhentheenduserinteractsdirectlywiththeapplication(forexample,anonline
bankingapplicationversusacallcenterapplication).Byshowingonlyonequestionatatime,a
fraudulentusercannotlookaheadatotherquestionsforusefulcontext.Foranexampleofquestions
presentedsequentially,see"iAuthVerif ication:QuestionsPresentedSequentially"onpage72.
Foralistofthequestionsthatmaybeasked,see"QuestionText"onpage233.
<questions>
<questionsetid>11020026091051</questionsetid>
<question>
<questionid>11020043061360</questionid>
<answertype>single</answertype>
<text>
<statement>Basedonyourbackground,inwhatcityis'32Shaker
Ave'?</statement>
</text>
<choice>
<choiceid>11020128803663</choiceid>
<text>
<statement>Billerica</statement>
</text>
</choice>
<choice>
<text>
FIN11016 July 2014
<statement>Holbrook</statement>
</text>
</choice>
<choice>
<text>
<statement>NorthEaston</statement>
</text>
</choice>
<choice>
<text>
<statement>NorthWeymouth</statement>
</text>
</choice>
<choice>
<text>
<statement>Worcester</statement>
</text>
</choice>
<choice>
<text>
<statement>Ihaveneverbeenassociatedwiththisaddress
</statement>
</text>
</choice>
<helptext>
<statement>Theaddresseslistedmaybepartial,misspelledor
containminornumberingvariationsfromyouractual
FIN11016 July 2014
address</statement>
</helptext>
</question>
</questions>
I nf ormat i on
Theinformationelementprovidesadditionalinformationtoassistyouininterpretingandpresenting
informationtoyourusers.Forexample,theinformationelementisusedtopresentdetailsaboutan
errororfailure.
Inthefollowingmessage,theinformationelementpresentstextthatmaybepresentedinacallcenter
applicationtointroducethelistofiAuthquestionstothecallcenteragent(asshownintheexample
screenbelow).
<information>
<informationcode>questiondetails</informationcode>
<detailcode>iauth.questions.set1</detailcode>
<detaildescription>iAuthQuestionSet1</detaildescription>
<simpledetail>
<text>Initialsetofauthenticationquestions</text>
</simpledetail>
</information>
<information>
<informationcode>presentationdetails</informationcode>
<detailcode>presentation.response.title</detailcode>
<detaildescription>Presentation:Aresponse
title</detaildescription>
<simpledetail>
<text>Initialsetofauthenticationquestions</text>
</simpledetail>
</information>
FIN11016 July 2014
Theexampleabovealsoshowshowinformationfromthehelptextelement(includedinthequestions
elementonthepreviouspage)canbepresentedwiththequestiontoprovideclarif icationforthe
customer.
Ext ernal Responses
Theexternalresponseselementincludesresponsemessagesreturnedfromservicesthatintegratewith
IdentityVerif ication.Forinformationontheparametersinthiselement,seeexternalresponsestype,
page187.
Inthisexample,theFlexIDResponseExparameterholdsaresponsefromtheFlexIDservice,including
FlexID,InstantID,andFraudPointelements,scoresandcodes.Thisexternalresponseisreturned
becausetheVerif icationandFraudPreventionServicesintegrationfeatureisenabledfortheusers
account.TheFlexIDResponseExparameterpresentsvariousdetailsregardingtheusersauthentication,
includingasetofuniqueverif icationscores.FormoreinformationontheVerif icationandFraud
PreventionServicesintegrationfeature,contactyourTechnicalSolutionsConsultant.
As part of the Verification and Fraud Prevention Services integration feature, it is possible to receive
a response from either the InstantID or FraudPoint service, instead of receiving a response from the
Flex ID service, as shown in this example. For information on the relationship between the three
service providers, see the Response Values Reference Guide for Verification and Fraud Prevention
Services Integrations, Scores and Codes chapter.
Text provided
in the
information
element.
Text provided in
the help-text
element can be
read to the
customer to
provide
clarification.
FIN11016 July 2014
For the full list of structures received in a response message from the various Verification and Fraud
Prevention services, see the Response Values Reference Guide for Verification and Fraud
Prevention Services Integrations, Response Message Structures chapter.
<externalresponses>
<FlexIDResponseEx>
<response>
<Header>
<Status>0</Status>
<TransactionId>18071837R216884</TransactionId>
</Header>
<Result>
<InputEcho>
<Name>
<First>James</First>
<Last>Sample</Last>
</Name>
<Address>
<StreetAddress1>3877HarrisonBlvd</StreetAddress1>
<City>Springfield</City>
<State>MA</State>
<Zip5>01101</Zip5>
</Address>
<Age>0</Age>
</InputEcho>
<UniqueId>103976172631</UniqueId>
<NameAddressPhone>
<Summary>0</Summary>
</NameAddressPhone>
<VerifiedElementSummary>
<FirstName>true</FirstName>
<LastName>true</LastName>
<StreetAddress>false</StreetAddress>
<City>true</City>
<State>true</State>
<Zip>true</Zip>
<HomePhone>false</HomePhone>
FIN11016 July 2014
<DOB>false</DOB>
<DOBMatchLevel>0</DOBMatchLevel>
<SSN>false</SSN>
<DL>false</DL>
</VerifiedElementSummary>
<ValidElementSummary>
<SSNValid>false</SSNValid>
<SSNDeceased>false</SSNDeceased>
<DLValid>false</DLValid>
<PassportValid>false</PassportValid>
<AddressPOBox>false</AddressPOBox>
<AddressCMRA>false</AddressCMRA>
<SSNFoundForLexID>false</SSNFoundForLexID>
</ValidElementSummary>
<NameAddressSSNSummary>6</NameAddressSSNSummary>
<ComprehensiveVerification>
<ComprehensiveVerificationIndex>20
</ComprehensiveVerificationIndex>
<RiskIndicators>
<RiskIndicator>
<RiskCode>79</RiskCode>
<Description>TheinputSSN/TINwasmissingorincomplete
</Description>
<Sequence>2</Sequence>
</RiskIndicator>
<RiskIndicator>
<Description>Theinputaddressmaybeinvalidaccording
topostalspecifications
</Description>
</RiskIndicator>
<RiskIndicator>
<Description>Theinputdateofbirthwasmissingor
incomplete
FIN11016 July 2014
</Description>
</RiskIndicator>
<RiskIndicator>
<Description>Theinputphonewasmissingorincomplete
</Description>
</RiskIndicator>
</RiskIndicators>
</ComprehensiveVerification>
<CustomComprehensiveVerification>
<ComprehensiveVerificationIndex>0
</ComprehensiveVerificationIndex>
</CustomComprehensiveVerification>
<Models>
<Model>
<Name>FraudPoint</Name>
<Scores>
<Score>
<Type>0to999</Type>
<Value>600</Value>
<RiskIndices>
<RiskIndex>
<Name>StolenIdentityIndex</Name>
<Value>1</Value>
</RiskIndex>
<RiskIndex>
<Name>SyntheticIdentityIndex</Name>
<Value>1</Value>
</RiskIndex>
<RiskIndex>
<Name>ManipulatedIdentityIndex</Name>
<Value>1</Value>
</RiskIndex>
<RiskIndex>
FIN11016 July 2014
<Name>VulnerableVictimIndex</Name>
<Value>1</Value>
</RiskIndex>
<RiskIndex>
<Name>FriendlyFraudIndex</Name>
<Value>1</Value>
</RiskIndex>
<RiskIndex>
<Name>SuspiciousActivityIndex</Name>
<Value>1</Value>
</RiskIndex>
</RiskIndices>
<HighRiskIndicators>
<HighRiskIndicator>
<Description>TheinputSSN/TINwasmissing
orincomplete</Description>
</HighRiskIndicator>
<HighRiskIndicator>
<Description>Theinputphonewasmissingor
incomplete</Description>
<HighRiskIndicator>
<Description>Theinputdateofbirthwas
missingorincomplete</Description>
<HighRiskIndicator>
<Description>Incompleteverification
</Description>
FIN11016 July 2014
<HighRiskIndicator>
<Description>Theinputaddressmaybeinvalid
accordingtopostalspecifications
</Description>
<HighRiskIndicator>
<RiskCode>9D</RiskCode>
<Description>Changeofaddressfrequency
</Description>
</HighRiskIndicators>
</Score>
</Scores>
</Model>
</Models>
<InstantIDVersion>0</InstantIDVersion>
</Result>
</response>
</FlexIDResponseEx>
</java:transactionresponse>
</env:Body>
</env:Envelope>
Sendi ng a Cont i nuat i on Message
WhentheclientapplicationhasgatheredanswerstotheKBAquestionsfromtheuser,thenitneedsto
sendacontinuationrequestmessagetoIdentityVerif ication.
Root El ement
Thetransactioncontinueelementistherootelementforthismessage.
FIN11016 July 2014
xmlns:SOAPENC="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsi="http://www.w3.org/2001/XMLSchemainstance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<SOAPENV:Body>
<m:transactioncontinuexmlns:m="java:com.verid.carbon.integration.datatypes">
Set t i ngs
ThesettingselementrepeatsaccountinformationprovidedintheIdentityVerif icationmessageand
includesthetransactionidparameter.Thetransactionidvaluemustmatchthevalueincludedinthe
transactionResponsemessage.
<settings>
<mode>live</mode>
</settings>
Answers
Theanswerselementprovidestheusersanswerstothesetofmultiplechoicequestions.Thefollowing
parametersarerequired:
questionssetid:ThisisauniqueIDassignedtothesetofquestionsbyIdentityVerif ication.
answer:Youshouldincludeananswerparameterforeachoftheanswersprovidedbytheuser.Each
answerparametermustincludethefollowing:
questionid:ThisistheuniqueIDforaspecif icquestion.
choices:Thisparameteridentif iesthechoiceIDsforoneormoreanswersselectedbythe
user.Ifthequestionwasasingleanswerquestion,thenthisparametercanincludeonlyone
choiceidparameter;ifthequestionwasamultipleanswerquestion,thenthisparametercan
includeuptothenumberofchoicesoffered.
<answers>
<answer>
<choices>
FIN11016 July 2014
</choices>
</answer>
<answer>
<choices>
</choices>
</answer>
<answer>
<choices>
</choices>
</answer>
<answer>
<choices>
</choices>
</answer>
<answer>
<choices>
</choices>
</answer>
</answers>
</m:transactioncontinue>
</SOAPENV:Body>
</SOAPENV:Envelope>
In the example shown above, the first answer element corresponds to the question shown in the
Questions example.
FIN11016 July 2014
Recei vi ng Anot her t ransact i onResponse Message
IdentityVerif icationrespondstothecontinuationrequestwithanothertransactionResponsemessage.
Aswiththef irstresponse,thestatusofthisresponsecouldbepassed,failed,error,orquestions.
Whetheranothersetofquestionsisreturneddependsonthescoringofanswerstothef irstsetof
questions,aswellastheclientsparameterset.
Inthisexample,themessagereturnsastatusofpassed.Theinformationelementisusedtodescribe
thestatus.
<env:Header/>
<env:Body>
<transactionstatus>
<accountstransactionid>0</accountstransactionid>
<referenceid>0</referenceid>
<transactionresult>passed</transactionresult>
<information>
<informationcode>passeddetails</informationcode>
<detailcode>passed</detailcode>
<detaildescription>Transactionhas
passed</detaildescription>
<simpledetail>
<text>Theindividualhaspassedtherequestedverification
process.</text>
</simpledetail>
</information>
</env:Body>
</env:Envelope>
FIN11016 July 2014
iAuth Verification: Two Rounds of Questions, User Fails
ThissectionstepsthroughaniAuthexampleliketheonepresentedintheprevioussection,butinthis
exampletheuserdoesnotpassthef irstroundofquestions.Anotherroundofquestionsispresented,
theuserdoesnotpassthisroundeitherandtheauthenticationfails.
Recei vi ng t he Second Round of Quest i ons
Inthisexample,thecontinuationmessagereturnedtwooutoffourcorrectanswerstothef irstround
ofquestions.Basedonhowthequestionsweregraded(asdef inedintheclientsparameterset),this
resultedinatransactionResponsemessagewithanothersetofquestions.
Onlyoneofthequestionsisshowninthisexample.ThequestionsetIDisthesameastheIDforthe
f irstroundofquestions.
<transactionstatus>
<questions>
<question>
<text>
<statement>Whichofthefollowingpeoplehaveyouknown?
</statement>
</text>
<choice>
<text>
<statement>BertWhite</statement>
FIN11016 July 2014
</text>
</choice>
<choice>
<text>
<statement>ByranBolton</statement>
</text>
</choice>
<choice>
<text>
<statement>GildaGalvin</statement>
</text>
</choice>
<choice>
<text>
<statement>LindaSampson</statement>
</text>
</choice>
<choice>
<text>
<statement>WayneBurrell</statement>
</text>
</choice>
<choice>
<text>
<statement>IdonotknowANYofthepeoplelisted</statement>
</text>
FIN11016 July 2014
</choice>
<helptext>
<statement>Namesmaybelistedaslastnamefirstname,include
maidennamesorcontainslightmisspellings.
</statement>
</helptext>
</question>
Recei vi ng t he t ransact i onResponse Message: Fai l ed St at us
Withthesecondroundofquestions,theuseransweredonlytwooutofthreequestionscorrectly.Based
onhowthequestionsweregraded(asdef inedintheclientsparameterset),thisresultedintheuser
failingtheverif icationasshowninthefollowingtransactionResponsemessage:
<env:Envelopexmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<env:Header/>
<env:Body>
<java:transactionresponsexmlns:java="java:com.verid.carbon.integration.
datatypes">
<transactionstatus>
<transactionresult>failed</transactionresult>
<information>
<informationcode>faileddetails</informationcode>
<detailcode>failed_iauth_questions</detailcode>
<detaildescription>Failed:iAuthQuestions</detaildescription>
<simpledetail>
<text>Theindividualfailedtocorrectlyanswerenoughof
thepresentedquestions.</text>
</simpledetail>
</information>
FIN11016 July 2014
</env:Body>
</env:Envelope>
iAuth Verification: Questions Presented Sequentially
ThissectionstepsthroughaniAuthexamplewherethequestionsarepresentedoneatatimerather
thaninagroup.LexisNexisrecommendspresentingquestionssequentiallywhentheenduserinteracts
directlywiththeapplication(forexample,anonlinebankingapplicationversusacallcenter
application).Byshowingonlyonequestionatatime,afraudulentusercannotlookaheadatother
questionsforusefulcontext.
Sendi ng t he I dent i t yVeri f i cat i on Request
YourclientapplicationshouldsendanIdentityVerif icationmessagetoinitiateaniAuthverif ication.
TheIdentityVerif icationmessageidentif iesthetypeofverif icationtoperformandprovidesdataon
theuseryouaretryingtoauthenticate.
Root El ement
Thetransactionidentityverif icationelementistherootelementforthismessage.
<SOAPENV:Body>
Set t i ngs
Inthisexample,thetaskparameterissettoiauth.Forinformationontheotherparametersinthis
element,see"Settings"onpage51.
<settings>
<mode>live</mode>
FIN11016 July 2014
<task>iauth</task>
</settings>
Person
Forinformationontheparametersinthiselement,see"Person"onpage52.
Recei vi ng t he Fi rst Quest i on
Thef irsttransactionResponsemessagepresentsthef irstofthreequestions.
<env:Header/>
<env:Body>
<transactionstatus>
<questions>
<question>
<text>
<statement>Whichnumbersmatchthemiddletwodigitsofyour
socialsecuritynumber.(Forexample,123456789
wouldbe'45')</statement>
</text>
<choice>
FIN11016 July 2014
<text>
<statement>2and4</statement>
</text>
</choice>
<choice>
<text>
</text>
</choice>
<choice>
<text>
</text>
</choice>
<choice>
<text>
</text>
</choice>
<choice>
<text>
</text>
</choice>
<choice>
FIN11016 July 2014
<text>
<statement>Noneoftheabove</statement>
</text>
</choice>
<helptext>
<statement>Forexample,ifyourSocialSecurityNumberis12345
6789,thenyouwouldselect'45'</statement>
</helptext>
</question>
</questions>
<information>
<detailcode>iauth.questions.sequential</detailcode>
<detaildescription>iAuthQuestionSequential</detaildescription>
<simpledetail>
<text>Sequentialquestionpresentation</text>
</simpledetail>
</information>
<information>
<detaildescription>Presentation:Aresponsetitle</detaildescription>
<simpledetail>
</simpledetail>
</information>
</env:Body>
</env:Envelope>
Sendi ng t he Fi rst Cont i nuat i on Request
Thef irstcontinuationrequestsendstheusersanswertothef irstquestion.
FIN11016 July 2014
<SOAPENV:Body>
<settings>
<mode>live</mode>
</settings>
<answers>
<answer>
<choices>
</choices>
</answer>
</answers>
</SOAPENV:Body>
</SOAPENV:Envelope>
Recei vi ng t he Second Quest i on
ThenexttransactionResponsepresentsthesecondofthreequestions.NotethatthequestionsetIDis
thesameastheIDforthef irstquestion.
<env:Header/>
<env:Body>
<transactionstatus>
FIN11016 July 2014
<questions>
<question>
<text>
<statement>Basedonyourbackground,inwhatcountyis'765Main
St'?</statement>
</text>
<choice>
<text>
<statement>Bristol</statement>
</text>
</choice>
<choice>
<text>
<statement>Franklin</statement>
</text>
</choice>
<choice>
<text>
<statement>Hampshire</statement>
</text>
</choice>
<choice>
FIN11016 July 2014
<text>
<statement>Norfolk</statement>
</text>
</choice>
<choice>
<text>
<statement>Suffolk</statement>
</text>
</choice>
<choice>
<text>
<statement>Ihaveneverbeenassociatedwiththisaddress
</statement>
</text>
</choice>
<helptext>
address</statement>
</helptext>
</question>
</questions>
<information>
<simpledetail>
</simpledetail>
FIN11016 July 2014
</information>
<information>
<simpledetail>
</simpledetail>
</information>
</env:Body>
</env:Envelope>
Sendi ng t he Second Cont i nuat i on Request
Thesecondcontinuationrequestsendstheusersanswertothesecondquestion.
<SOAPENV:Body>
<settings>
<mode>live</mode>
</settings>
<answers>
<answer>
<choices>
</choices>
</answer>
FIN11016 July 2014
</answers>
</SOAPENV:Body>
</SOAPENV:Envelope>
Recei vi ng t he Thi rd Quest i on
ThenexttransactionResponsepresentsthelastofthreequestions.NotethatthequestionsetIDisthe
sameastheIDforthef irsttwoquestions.
<env:Header/>
<env:Body>
<transactionstatus>
<questions>
<question>
<text>
<statement>Whichofthefollowingstreetaddressesin
'Westfield'haveyoueverlivedatorbeenassociated
with?</statement>
</text>\
<choice>
<text>
FIN11016 July 2014
<statement>15LenoxSt</statement>
</text>
</choice>
<choice>
<text>
<statement>38ChristopherRd</statement>
</text>
</choice>
<choice>
<text>
<statement>49SnowHillSt</statement>
</text>
</choice>
<choice>
<text>
<statement>57SpringfieldSt</statement>
</text>
</choice>
<choice>
<text>
<statement>75BellevueSt</statement>
</text>
</choice>
<choice>
<text>
FIN11016 July 2014
<statement>Either1)Noneoftheaboveor2)Ihavenever
livedorownedpropertyinthiscity</statement>
</text>
</choice>
<helptext>
address</statement>
</helptext>
</question>
</questions>
<information>
<simpledetail>
</simpledetail>
</information>
<information>
<simpledetail>
</simpledetail>
</information>
</env:Body>
</env:Envelope>
Sendi ng t he Thi rd Cont i nuat i on Request
Thethirdcontinuationrequestsendstheusersanswertothethirdquestion.
FIN11016 July 2014
<SOAPENV:Body>
<settings>
<mode>live</mode>
</settings>
<answers>
<answer>
<choices>
</choices>
</answer>
</answers>
</SOAPENV:Body>
</SOAPENV:Envelope>
Recei vi ng t he t ransact i onResponse Message Resul t
Theuseransweredallthreequestionscorrectlyandpassedtheverif ication.
<env:Header/>
<env:Body>
<transactionstatus>
FIN11016 July 2014
<information>
<detaildescription>Transactionhaspassed</detaildescription>
<simpledetail>
process.</text>
</simpledetail>
</information>
</env:Body>
</env:Envelope>
iCheck Verification: User Passes
ThissectionstepsthroughthecontentofsamplerequestandresponsemessagesforaniCheck
verif icationthatisbeingdonetoverifytheidentityofacustomerpurchasinganitemfromanonline
merchant.
In the iCheck Verification: User Passes example, the user is associated with an account for which
the Verification and Fraud Prevention Services integration feature is enabled, therefore, a response
from LexisNexis
InstantID
is included in the main TransactionResponse message (see"External

Responses" on page 89). For more information on the Verification and Fraud Prevention Services
integration feature, contact your Technical Solutions Consultant.
YourclientapplicationshouldsendanIdentityVerif icationmessagetoinitiateaniCheckverif ication.
Root El ement
FIN11016 July 2014
<SOAPENV:Body>
Set t i ngs
Inthisexample,thetaskparameterissettoicheck.Forinformationontheotherparametersinthis
<settings>
<mode>live</mode>
<task>icheck</task>
</settings>
Person
Forinformationontheparametersinthiselement,see"Person"onpage52.
<person>
<namefirst>Jane</namefirst>
<email>jane_sample@example.com</email>
<address>
</address>
<phonenumber>
FIN11016 July 2014
</phonenumber>
</person>
If the request included a 9-digit social security number, then the address would be optional. For a
matrix of personal data requirements, based on verification type, see "Data in Person Element" on
page 132.
Transact i on
Thisexampleincludesapurchaseelementthatdef inestheseparameters:
order(optional):Providesdetailsabouttheordertheuserisattemptingtoplace.Inthisexample,
theorderelementdef inesvaluesfortheseparameters:
itemtype(mandatory):Includeschildelementsthatprovidedetailsabouttheitembeing
ordered.Inthisexample,theorderisforoneitem.Youmustincludeanitemtypeelementfor
eachitemintheorder.Theitemtypeelementmustdef ineproductcategory.Inthisexample,
italsodef inesmodel,code,productquantity,peritemamount,anddata.Thedataelementis
usedtoprovidedescriptivetextabouttheitem.
totalamount(mandatory):Specif iesthetotalamountofthepurchase(59.99).
merchant(optional):Specif iesthenameofthemerchant.
paymentmethod(optional):Inthisexample,themethodofpaymentiscreditcard.
account(mandatory):Providesdetailsabouttheusersaccount.Inthisexample,theuserdoesnot
haveanaccountwiththeonlinemerchant.ThisparameterisusedtosendacustomerID(customer
id)numberthatisassignedbythemerchantsecommerceapplicationwhenthecustomerplacesan
order.
venue:Specif iesthatthetransactionistakingplaceonline.Otherpossiblevaluesarecallcenter,
batch,netview,pointofsale,customerservice,andivr.Thevenueparameteralsospecif iesthe
credentialmethod(basic)andtheIPaddressofthemachineonwhichtheuserinitiatedthe
transaction.
activitydate:Specif iesthedateandtimeofthetransactioninISO8601format.
<transaction>
<purchase>
<order>
<itemtype>
<productcategory>gameortoy</productcategory>
<model>NscaleNewYorkCentralEngine</model>
FIN11016 July 2014
<code>NPT98657</code>
<productquantity>1</productquantity>
<peritemamount>59.99</peritemamount>
<data>
<heading>ProductDescription</heading>
<simpledetail>Black,antiqueNscaleengine;
front&rearcouplingincluded</simpledetail>
</data>
</itemtype>
<totalamount>59.99</totalamount>
<merchant>Harry'sTrainEmporium</merchant>
</order>
<paymentmethod>creditcard</paymentmethod>
<account>
</account>
<venue>
<online>
<credential>
</credential>
</online>
</venue>
<transactiondate>20100615T13:20:05.768Z</transactiondate>
</purchase>
</transaction>
</SOAPENV:Body>
Recei vi ng t he t ransact i onResponse Response
Thismessageprovidesdetailsaboutthestateofthetransactionanddirectionsforcontinuing.
FIN11016 July 2014
Root El ement
Thetransactionresponseelementistherootelementforthismessage.
<env:Header/>
<env:Body>
Inthisexample,theresultispassed,whichmeansthattheuserwassuccessfullyauthenticated.Because
ofasettingintheclientsparameterset,theresponseincludesaninformationelementthatidentif ies
theIPaddressscountryoforigin.
Forinformationonotherparametersinthiselement,see"Transaction"onpage54.
<transactionstatus>
<information>
<detaildescription>Transactionhaspassed
</detaildescription>
<simpledetail>
process.</text>
</simpledetail>
</information>
<information>
<informationcode>informationdetails</informationcode>
<detailcode>ipcountryorigin</detailcode>
FIN11016 July 2014
<detaildescription>IPaddresscountryoforigin:
</detaildescription>
<complexdetail>
<heading>IPAddressCountryofOrigin</heading>
<simpledetail>
<text>US</text>
</simpledetail>
<simpledetail>
<text>UnitedStates</text>
</simpledetail>
</complexdetail>
</information>
Ext ernal Responses
page187.
Inthisexample,theinstantIDResponseparameterholdsaresponsefromtheInstantIDservice,
includingbothInstantIDandFraudPointscoresandcodes.Thisexternalresponseisreturnedbecause
theVerif icationandFraudPreventionServicesintegrationfeatureisenabledfortheusersaccount.
TheinstantIDResponseparameterpresentsvariousdetailsfromInstantIDandFraudPointregarding
theusersauthentication,includingasetofuniqueverif icationscores.Formoreinformationonthe
Verif icationandFraudPreventionServicesintegrationfeature,contactyourTechnicalSolutions
Consultant.
a response from either the FraudPoint or Flex ID service, instead of receiving a response from the
InstantID service, as shown in this example. For information on the relationship between the three
<externalresponses>
<instantIDResponse>
<response>
<Header>
FIN11016 July 2014
<Status>0</Status>
</Header>
<Result>
<InputEcho>
<Name>
<Last>Sample</Last>
</Name>
<SSN>123456789</SSN>
<UseDOBFilter>true</UseDOBFilter>
<DOBRadius>2</DOBRadius>
<Passport>
<Number/>
<ExpirationDate/>
<Country/>
<MachineReadableLine1/>
<MachineReadableLine2/>
</Passport>
</InputEcho>
<UniqueId>103976172631</UniqueId>
<VerifiedInput>
<Name>
<Last>Sample</Last>
</Name>
<SSN>123456789</SSN>
</VerifiedInput>
<DOBVerified>false</DOBVerified>
<NameAddressSSNSummary>9</NameAddressSSNSummary>
<NameAddressPhone>
<Summary>0</Summary>
</NameAddressPhone>
<ComprehensiveVerificationIndex>20</ComprehensiveVerificationIndex>
<RiskIndicators>
<RiskIndicator>
FIN11016 July 2014
<Description>Theinputaddresswasmissing</Description>
</RiskIndicator>
<RiskIndicator>
<Description>Theinputdateofbirthwasmissingorincomplete
</Description>
</RiskIndicator>
...
</RiskIndicators>
<PotentialFollowupActions>
<FollowupAction>
<RiskCode>C</RiskCode>
<Description>VerifynamewithAddress(viaDL,utilitybill,
DirectoryAssistance,paycheckstub,orotherGovernment
IssuedID)</Description>
</FollowupAction>
<FollowupAction>
<RiskCode>D</RiskCode>
<Description>Verifyphone(DirectoryAssistance,utilitybill)
</Description>
</FollowupAction>
</PotentialFollowupActions>
<SSNInfo>
<Valid>G</Valid>
<IssuedLocation>Springfield</IssuedLocation>
<IssuedStartDate>
<Year>1990</Year>
<Month>1</Month>
<Day>1</Day>
</IssuedStartDate>
<IssuedEndDate>
<Year>1991</Year>
<Month>12</Month>
FIN11016 July 2014
<Day>31</Day>
</IssuedEndDate>
</SSNInfo>
<ChronologyHistories>
<ChronologyHistory>
<Address>
<StreetNumber>3877</StreetNumber>
<StreetName>Harrison</StreetName>
<StreetSuffix>BLVD</StreetSuffix>
<StreetAddress1>3877HarrisonBlvd</StreetAddress1>
<City>Springfield</City>
<State>MA</State>
<Zip5>01101</Zip5>
<Zip4>01101</Zip4>
</Address>
<DateFirstSeen>
<Year>2011</Year>
<Month>3</Month>
</DateFirstSeen>
<DateLastSeen>
<Year>2013</Year>
<Month>10</Month>
</DateLastSeen>
<IsBestAddress>true</IsBestAddress>
</ChronologyHistory>
...
</ChronologyHistories>
<AdditionalScore1>0</AdditionalScore1>
<AdditionalScore2>0</AdditionalScore2>
<CurrentName>
<Last>Sample</Last>
</CurrentName>
<Models>
<Model>
FIN11016 July 2014
<Scores>
<Score>
<Type>0to999</Type>
<Value>490</Value>
<RiskIndices>
<RiskIndex>
<Value>7</Value>
</RiskIndex>
<RiskIndex>
<Value>1</Value>
</RiskIndex>
...
</RiskIndices>
<RiskIndicators>
<RiskIndicator>
<Description>Theinputaddresswasmissing
</Description>
</RiskIndicator>
<RiskIndicator>
</RiskIndicator>
...
</RiskIndicators>
</Score>
</Scores>
</Model>
</Models>
<RedFlagsReport>
<Version>1</Version>
<RedFlags>
<RedFlag>
FIN11016 July 2014
<Name>MissingInputCodes</Name>
<HighRiskIndicator>
<Description>Theinputphonewasmissingorincomplete
</Description>
...
</RedFlag>
</RedFlags>
</RedFlagsReport>
<PassportValidated>false</PassportValidated>
<DOBMatchLevel>0</DOBMatchLevel>
</Result>
</response>
</instantIDResponse>
</externalresponses>
</env:Body>
</env:Envelope>
iCheck Verification: OFAC Check Enabled
verif icationthatisbeingdonetoverifytheidentityofacustomerattemptingtowithdrawmoneyfrom
theironlinebankingaccount.ThistransactionisgovernedbyaparametersetwheretheIdentityRisk
ScorefeatureandanOFAC(Off iceofForeignAssetControl)listcheckareenabled.
TheIdentityRiskScoreisanumericvalue,0to1000,thatquantif iestheriskoffraudassociatedwith
anidentityduringatransaction.Thecloserthenumberisto1000,thegreatertheriskoffraud.An
accountcanbeconf iguredwithariskscorethresholdsothatthetransactionwillbedeniedifthescore
exceedsacertainvalue.Inthisexample,theriskscoreisbelowthethreshold.Formoreinformationon
theIdentityRiskScorefeature,seeNetviewHelp.
FIN11016 July 2014
WithanOFAClistcheck,IdentityVerif icationsearchesfortheusersnameontheSpecially
DesignatedNationals(SDN)listpublishedbyOFAC.TheSDNlistcontainsnamesofforeign
individualswhohavebeenidentif iedaspotentialthreatstotheUSandareblockedfromtakingpartin
f inancialactivitieswithintheUnitedStates,includingopeningnewbankaccountsandbrokerage
accounts.ThistypeofcheckisalsoreferredtoasaPatriotActsearchbecausetheTheUSPatriotAct
requirescheckingindividualsagainsttheOFACSDNlistinordertocomplywithSection326.
Therequestmessageforthisexampleincludesanaccountverif icationelementthatdef inesthese
parameters:
accountactivity:Specif iesthatthetransactionisanonmaintenanceaccountactivityforan
establishedaccount.Inthisexample,theorderaccountactivityelementdef inesvaluesforthese
parameters:
accounttransaction:Specif iesthattheproductcategory(thetasktheuserisattempting)isa
withdrawal.
totalamount,beginningbalance,andendingbalance:Specif iesastartingandendingbal
ance,andthetotalamountofthetransaction.Theuserisattemptingtowithdraw$10,000
fromanaccountthathas$150,000.
venue:Specif iesthatthetransactionistakingplaceonline.Thevenueparameteralsospecif iesthe
credentialmethod(basic)andtheIPaddressofthemachineonwhichtheuserinitiatedthe
transaction.
activitydate:Specif iesthedateandtimeofthetransactioninISO8601format.
<transaction>
<accountactivity>
<account>
</account>
<accounttransaction>
<productcategory>withdrawal</productcategory>
</accounttransaction>
<totalamount>10000</totalamount>
FIN11016 July 2014
<beginningbalance>150000</beginningbalance>
<endingbalance>140000</endingbalance>
</accountactivity>
<venue>
<online>
<credential>
</credential>
</online>
</venue>
</transaction>
</SOAPENV:Body>
</SOAPENV:Envelope>
Thetransactionresponsemessagereturnsastatusofpassed.Thisclientsparametersetisconf igured
sothatIdentityVerif icationdeniesatransactionforanyuserwithariskscoregreaterthan700.This
usersriskscoreis481.
<env:Header/>
<env:Body>
<transactionstatus>
<riskassessment>
FIN11016 July 2014
<riskscore>481.0</riskscore>
</riskassessment>
<information>
<simpledetail>
<text>Theindividualhaspassedtherequestedverificationprocess.
</text>
</simpledetail>
</information>
<information>
<detailcode>ipatriot</detailcode>
<detaildescription>Patriotcompliancestatus:</detaildescription>
<simpledetail>
<text>TheindividualwasnotfoundontheOFAClist</text>
</simpledetail>
</information>
</env:Body>
</env:Envelope>
iCheck Verification: Disambiguating Question
Insomeinstances,itisdiff icultforIdentityVerif icationtolocatethepersontobeverif iedbasedon
thedataprovided.Thiscanhappenwhen,forexample,theindividualhasrecentlychangednamesdue
toamarriageorwhenajuniorandseniorwiththesamenameliveatthesameaddress.Ifonlyname
andaddressareprovided,IdentityVerif icationneedsmoredatatolocatetheuserbeforeperforming
theverif ication.Tohandlesituationswheretheidentityoftheuserisnotclear,IdentityVerif ication
canbeconf iguredtopresentadisambiguatingquestiontoselecttheappropriateindividualfrom
severalpossiblematches.
Inthisexample,IdentityVerif icationreturnsadisambiguatingquestion.Theuseranswersthis
questioncorrectlyandpassestheverif ication.
FIN11016 July 2014
Inthisexample,theusersf irstnameisMichaelbutheisknownbyhismiddlename,James.He
enteredJamesintheFirstNamef ield,whichresultedinambiguityduringthelocateprocess.
<person>
<namefirst>James</namefirst>
<email>samplej@myemail.com</email>
<address>
<addressstreet1>3877HarrisonBlvd</addressstreet1>
<addresscity>Springfield</addresscity>
</address>
</person>
Thetransactionresponseincludesadisambiguatingquestion.
<env:Header/>
<env:Body>
<transactionstatus>
<questions>
FIN11016 July 2014
<question>
<text>
<statement>Whichofthefollowingfirstnameshaveyoualsobeen
knownby?</statement>
</text>
<choice>
<text>
<statement>Billy</statement>
</text>
</choice>
<choice>
<text>
<statement>Buddy</statement>
</text>
</choice>
<choice>
<text>
<statement>Howard</statement>
</text>
</choice>
<choice>
<text>
<statement>Michael</statement>
</text>
FIN11016 July 2014
</choice>
<choice>
<text>
<statement>Richard</statement>
</text>
</choice>
<choice>
<text>
</text>
</choice>
<helptext>
<statement>Inordertoclarifyyouridentity,pleaseselectthe
firstnamethatbestmatchesanamethatyoumayhave
usedrecentlyorareassociatedwith.Notethatthere
maybeslightmisspellings.Theseare
unintentional.</statement>
</helptext>
</question>
</questions>
<information>
<detailcode>icheck.disambiguate</detailcode>
<detaildescription>iLocateDisambiguate</detaildescription>
<complexdetail>
<heading>DisambiguateMultiplePossibleIdentityMatches</heading>
<simpledetail>
<text>LexisNexishasidentifiedmorethanonepersonmatchingthe
giveninformation.</text>
</simpledetail>
<simpledetail>
FIN11016 July 2014
<text>Priortocontinuingwiththeauthentication,pleaseanswer
thefollowingquestioninordertoensurethatthe
properindividualislocated:</text>
</simpledetail>
</complexdetail>
</information>
<information>
<simpledetail>
<text>DisambiguateMultiplePossibleIdentityMatches</text>
</simpledetail>
</information>
</env:Body>
</env:Envelope>
Sendi ng t he Cont i nuat i on Request
Thecontinuationmessageprovidesacorrectanswertothedisambiguatingquestion.
<SOAPENV:Body>
<settings>
<mode>live</mode>
</settings>
<answers>
<answer>
FIN11016 July 2014
<choices>
</choices>
</answer>
</answers>
</SOAPENV:Body>
</SOAPENV:Envelope>
Recei vi ng t he Next t ransact i onResponse Message: User Passed
ThenexttransactionResponsemessageindicatesthattheuserhaspassedtherequestedverif ication
process.
<env:Header/>
<env:Body>
<transactionstatus>
<information>
<simpledetail>
process.</text>
</simpledetail>
</information>
FIN11016 July 2014
</env:Body>
</env:Envelope>
iCheck Verification: User Fails Age Verification
verif icationwhereanagethresholdisenabled.Inthisexample,a20yearolduserisattemptingto
orderalcoholfromanonlinemerchant.Forthistransaction,theusermustbeatleast21yearsold.
In the iCheck Verification: User Fails Age Verification example, the user is associated with an
account for which the Verification and Fraud Prevention Services integration feature is enabled,
therefore, a response from LexisNexis
FraudPoint
is included in the main TransactionResponse

message (see"External Responses" on page 107). For more information on the Verification and
Fraud Prevention Services integration feature, contact your Technical Solutions Consultant.
YourclientapplicationshouldsendanIdentityVerif icationmessagetoinitiateaniCheckverif ication.
Root El ement
<SOAPENV:Body>
Set t i ngs
Inthisexample,thetaskparameterissettoicheck.Forinformationontheotherparametersinthis
<settings>
FIN11016 July 2014
<mode>live</mode>
<task>icheck</task>
</settings>
Person
Becausetheageverif icationthresholdparameterisenabled,thebirthdateelementisrequired.For
informationonotherparametersinthiselement,see"Person"onpage52.
When possible, Identity Verification determines the age of the user from public records, rather than
from birthdate data sent in the request. In this example, an incorrect birthdate was provided, but
Identity Verification reviewed public records to determine that the user is only 20 years old.
<person>
<namefirst>Sam</namefirst>
<email>ssample@example.net</email>
<address>
</address>
<birthdate>
<year>1988</year>
<month>10</month>
<day>2</day>
</birthdate>
<phonenumber>
</phonenumber>
</person>
FIN11016 July 2014
If the request included a 9-digit social security number, then the address would be optional. For a
matrix of personal data requirements, based on verification type, see "Data in Person Element" on
page 132.
Transact i on
Thisexampleincludesapurchaseelementthatdef inesanorderofalcoholfromanonlinemerchant.
Forinformationonotherparametersinthiselement,see"Transaction"onpage54.
<transaction>
<purchase>
<order>
<itemtype>
<productcategory>alcohol</productcategory>
</itemtype>
<totalamount>139.99</totalamount>
<merchant>eGrapeVineyards</merchant>
</order>
<paymentmethod>creditcard</paymentmethod>
<account>
</account>
<venue>
<online>
<credential>
</credential>
</online>
</venue>
<transactiondate>20100615T13:20:05.768Z</transactiondate>
</purchase>
</transaction>
</SOAPENV:Body>
</SOAPENV:Envelope>
FIN11016 July 2014
Recei vi ng t he t ransact i onResponse Message
Thismessageprovidesdetailsaboutthestatusofthetransactionanddirectionsforcontinuing.
Root El ement
Thetransactionresponseelementistherootelementforthismessage.Itidentif iesanamespacethat
def inesdatatypesspecif ictotheIdentityVerif icationwebservice.Thisrootelementcontainschild
elementsthatprovideallthedetailsthatIdentityVerif icationneedstoperformtheverif ication.
<env:Header/>
<env:Body>
Thetransactionstatuselementismandatory.Itprovideshighleveldetailsaboutthecurrentstatusof
thetransaction,thetransactionnumber,andtheresultofthetransaction.Inthisexample,theresultis
failed,whichmeansthattheuserdoesnotmeettheagethresholdandcannotbeauthenticated.
Forinformationonotherparametersinthiselement,see"TransactionStatus"onpage55.
<transactionstatus>
<information>
<detailcode>denial_age_verification_threshold</detailcode>
<detaildescription>Denial:AgeThresholdNotMet</detaildescription>
<simpledetail>
<text>Individualdoesnotappeartobetherequiredagebasedon
FIN11016 July 2014
availablerecords</text>
</simpledetail>
</information>
Ext ernal Responses
page187.
Inthisexample,theFraudPointResponseExparameterholdsaresponsefromtheFraudPointservice,
includingFraudpointscoresandcodesandInstantIDredflagriskcodes.Thisexternalresponseis
returnedbecausetheVerif icationandFraudPreventionServicesintegrationfeatureisenabledforthe
usersaccount.TheFraudPointResponseExparameterpresentsvariousdetailsregardingtheusers
authentication,includingasetofuniqueverif icationscores.FormoreinformationontheVerif ication
andFraudPreventionServicesintegrationfeature,contactyourTechnicalSolutionsConsultant.
a response from either the InstantID or Flex ID services, instead of receiving a response from the
FraudPoint service, as shown in this example. For information on the relationship between the three
<externalresponses>
<FraudPointResponseEx>
<response>
<Header>
<Status>0</Status>
</Header>
<Result>
<InputEcho>
<Name>
<Last>Sample</Last>
</Name>
FIN11016 July 2014
<SSN>123456789</SSN>
</InputEcho>
<Attributes/>
<RedFlagsReport>
<Version>1</Version>
<RedFlags>
<RedFlag>
<Name>MissingInputCodes</Name>
<HighRiskIndicator>
<HighRiskIndicator>
</Description>
<HighRiskIndicator>
<Description>Theinputdateofbirthwasmissing
orincomplete</Description>
</RedFlag>
</RedFlags>
</RedFlagsReport>
<Models>
<Model>
<Scores>
<Score>
<Type>0to999</Type>
<Value>490</Value>
<RiskIndices>
FIN11016 July 2014
<RiskIndex>
<Value>7</Value>
</RiskIndex>
<RiskIndex>
<Value>1</Value>
</RiskIndex>
<RiskIndex>
<Name>ManipulatedIdentityIndex</Name>
<Value>1</Value>
</RiskIndex>
<RiskIndex>
<Name>VulnerableVictimIndex</Name>
<Value>1</Value>
</RiskIndex>
<RiskIndex>
<Name>FriendlyFraudIndex</Name>
<Value>1</Value>
</RiskIndex>
<RiskIndex>
<Name>SuspiciousActivityIndex</Name>
<Value>1</Value>
</RiskIndex>
</RiskIndices>
<RiskIndicators>
<RiskIndicator>
</Description>
</RiskIndicator>
<RiskIndicator>
</RiskIndicator>
FIN11016 July 2014
<RiskIndicator>
<Description>Theinputdateofbirthwas
missingorincomplete
</Description>
</RiskIndicator>
<RiskIndicator>
<Description>Incompleteverification
</Description>
</RiskIndicator>
<RiskIndicator>
<RiskCode>9D</RiskCode>
<Description>Changeofaddressfrequency
</Description>
</RiskIndicator>
</RiskIndicators>
</Score>
</Scores>
</Model>
</Models>
</Result>
</response>
</FraudPointResponseEx>
</env:Body>
</env:Envelope>
iAuth Verification (UK): Disambiguating Question, User Passes
ThissectionstepsthroughaniAuthexamplewheretheuserlivesintheUnitedKingdom.Identity
Verif icationinitiallyhasdiff icultylocatingthepersonbasedonthedataprovidedandtherefore
returnsadisambiguatingquestion.Basedonthisanswer,IdentityVerif icationlocatestheuserand
thenreturnsthesetofauthenticationquestions.Theuseranswersthesecorrectlyandpassesthe
verif ication.
FIN11016 July 2014
YourclientapplicationshouldsendanIdentityVerif icationmessagetoinitiateaniAuthverif ication.
Root El ement
<SOAPENV:Body>
Set t i ngs
Inthisexample,thetaskparameterissettoiauth.Forinformationontheotherparametersinthis
<settings>
<accountname>Customers:ExampleUKBank</accountname>
<mode>live</mode>
<ruleset>ukbank</ruleset>
<task>iauth</task>
</settings>
Person
Thepersonelementprovidespersonalinformationabouttheenduserbeingauthenticated.
Parametershighlightedinredarerequired.BecausetheuserlivesintheUK,theukaddressparameter
isused.ForUSaddresses,theaddressparametermustbeused.Forinformationonotherparametersin
theukaddressparameter,see"ukaddresstype"onpage215.
<person>
<namefirst>James</namefirst>
<namelast>Williams</namelast>
FIN11016 July 2014
<ukaddress>
<street1>16Ridgemount</street1>
<housename>Flat1</housename>
<town>Weybridge</town>
<postcode>KT139JD</postcode>
<context>primary</context>
</ukaddress>
</person>
The name-first and name-last parameters are required.

Asshownabove,thehousenameparameterisusedtospecifythehousenameorflatnumber.
Transact i on
Thisexampleincludesanaccountverif icationelementthatdef inestheseparameters:
accountmaintenance(optional):Specif iesthatthetransactionisanaccountmaintenancetask.
Insteadofaccountmaintenance,youcanspecifyaccountactivityoraccountorigination.Inthis
example,theaccountmaintenanceelementdef inestheseparameters:
accountcategory:Specif iesthatthetransactionisinthebankingcategory.Therearemany
possiblevalues,includingbrokerage,retail,publicrecords,andcreditcards.
accountmaintenancecategory:Specif iesthatthepersonisattemptingtoorderanewcard
(ordercard).
See"APIReference"onpage154foracompletelistofpossibleaccountandaccountmaintenance
categories.
venue(mandatory):Specif iesthatthetransactionistakingplaceonline.Otherpossiblevaluesare
callcenter,batch,netview,pointofsale,customerservice,andivr.Thevenueparameteralso
specif iesthecredentialmethod(basic)andtheIPaddressofthemachineonwhichtheuser
initiatedthetransaction.
activitydate(mandatory):Specif iesthedateandtimeofthetransactioninISO8601format.
<transaction>
<accountmaintenance>
<accountcategory>banking</accountcategory>
FIN11016 July 2014
<accountmaintenancecategory>ordercard
</accountmaintenancecategory>
<account>
</account>
</accountmaintenance>
<venue>
<online>
<credential>
</credential>
</online>
</venue>
</transaction>
</SOAPENV:Body>
</SOAPENV:Envelope>
Thismessageprovidesdetailsaboutthestatusofthetransactionanddirectsyouonthenextsteps.
Root El ement
Thetransactionresponseelementistherootelementforthismessage.
<env:Header/>
<env:Body>
FIN11016 July 2014
Inthisexample,IdentityVerif icationhastroublematchingtheindividualsidentitytothelocateddata.
Thetransactionresponseincludesadisambiguatingquestioninordertoselecttheappropriate
individualfromseveralpossiblematches.
Forinformationonotherparametersinthiselement,see"TransactionStatus"onpage55.
<transactionstatus>
<questions>
<question>
<text>
<statement>Whichofthefollowingfirstnameshaveyoualsobeen
knownby?</statement>
</text>
<choice>
<text>
<statement>Edward</statement>
</text>
</choice>
<choice>
<text>
<statement>Charles</statement>
FIN11016 July 2014
</text>
</choice>
<choice>
<text>
<statement>Clive</statement>
</text>
</choice>
<choice>
<text>
<statement>Terence</statement>
</text>
</choice>
<choice>
<text>
<statement>Harry</statement>
</text>
</choice>
<choice>
<text>
</text>
</choice>
<helptext>
<statement>Inordertoclarifyyouridentity,pleaseselectthe
firstnamethatbestmatchesanamethatyoumayhave
usedrecentlyorareassociatedwith.Notethatthere
maybeslightmisspellings.Theseare
FIN11016 July 2014
unintentional.</statement>
</helptext>
</question>
</questions>
<information>
<detailcode>icheck.disambiguate</detailcode>
<detaildescription>iLocateDisambiguate</detaildescription>
<complexdetail>
<heading>DisambiguateMultiplePossibleIdentityMatches</heading>
<simpledetail>
<text>LexisNexishasidentifiedmorethanonepersonmatchingthe
giveninformation.</text>
</simpledetail>
<simpledetail>
<text>Priortocontinuingwiththeauthentication,pleaseanswer
thefollowingquestioninordertoensurethattheproper
individualislocated:</text>
</simpledetail>
</complexdetail>
</information>
<information>
<simpledetail>
<text>DisambiguateMultiplePossibleIdentityMatches</text>
</simpledetail>
</information>
</env:Body>
</env:Envelope>
FIN11016 July 2014
Sendi ng t he Cont i nuat i on Request
Thecontinuationmessageprovidesacorrectanswertothedisambiguatingquestion.Thequestionset
id,questionid,andchoiceidvaluesneedtobereturnedinthecontinuationmessagetoidentifythe
usersanswer.
<SOAPENV:Body>
<settings>
<mode>live</mode>
</settings>
<answers>
<answer>
<choices>
</choices>
</answer>
</answers>
</SOAPENV:Body>
</SOAPENV:Envelope>
Recei vi ng t he Set of Quest i ons
Thenexttransactionresponseincludesthequestionselementwithasetofthreequestions.Forthe
purposeofthisdocument,onlyoneofthequestionsisshown.
<questions>
FIN11016 July 2014
<question>
<text>
<statement>Whichofthefollowingpeoplehaveyouknown?
</statement>
</text>
<choice>
<text>
<statement>ChristineTaylor</statement>
</text>
</choice>
<choice>
<text>
<statement>GeorginaJames</statement>
</text>
</choice>
<choice>
<text>
<statement>HildaHodgeman</statement>
</text>
</choice>
<choice>
<text>
<statement>MarySampson</statement>
</text>
</choice>
FIN11016 July 2014
<choice>
<text>
<statement>SamuelSutherland</statement>
</text>
</choice>
<choice>
<text>
</text>
</choice>
<helptext>
<statement>Namesmaybelistedaslastnamefirstname,include
maidennamesorcontainslightmisspellings.
</statement>
</helptext>
</question>
Sendi ng t he Next Cont i nuat i on Request
Thenextcontinuationmessageprovidescorrectanswerstoallthreequestions.
<SOAPENV:Body>
<settings>
<mode>live</mode>
</settings>
FIN11016 July 2014
<answers>
<answer>
<choices>
</choices>
</answer>
<answer>
<choices>
</choices>
</answer>
<answer>
<choices>
</choices>
</answer>
<answer>
<choices>
</choices>
</answer>
</answers>
</SOAPENV:Body>
</SOAPENV:Envelope>
Recei vi ng t he Next t ransact i onResponse Message: User Passed
ThenexttransactionResponsemessageindicatesthattheuserhaspassedtherequestedverif ication
process.
FIN11016 July 2014
<env:Header/>
<env:Body>
<transactionstatus>
<information>
<simpledetail>
process.</text>
</simpledetail>
</information>
</env:Body>
</env:Envelope>
iAuth Verification: Spanish
ThissectionshowssamplerequestandresponsemessagesforaniAuthverif icationthatissettoreturn
questionsinSpanish.MostoftheexampleisthesameastheiAuthexampleonpage51.Thissection
highlightsonlytheparametersspecif ictotheinternationalizationparameter.
FIN11016 July 2014
Set t i ngs
Thesettingselementincludestheinternationalizationparameter,whichspecif iesthatquestions
shouldbepresentedinSpanish.Thelanguageparametercanalsobesettoenglishorinformalspanish.
Whennotspecif ied,languagedefaultstoenglish.
<settings>
<mode>live</mode>
<task>iauth</task>
<internationalization>
<language>spanish</language>
</internationalization>
</settings>
Quest i ons
ThequestionselementprovidesasetofquestionswritteninSpanish.Forthepurposeofthis
document,onlyoneofthequestionsisshowninthisexample.
<questions>
<question>
<text>
<statement>Decualdelossiguientesvehculosha
sidopropietario,haalquilado,ofirmadocomopartede
suresponsabilidad?</statement>
</text>
FIN11016 July 2014
<choice>
<text>
<statement>1994ToyotaCorolla</statement>
</text>
</choice>
<choice>
<text>
<statement>1999PorscheBoxster</statement>
</text>
</choice>
<choice>
<text>
<statement>2000DodgeDurango</statement>
</text>
</choice>
<choice>
<text>
<statement>2001DodgeRamPickup</statement>
</text>
</choice>
<choice>
<text>
<statement>2003OldsmobileAleroGL2</statement>
</text>
</choice>
<choice>
FIN11016 July 2014
<text>
<statement>Nuncahetenidoasociacinalguna
conlosvehculospresentados.</statement>
</text>
</choice>
<helptext>
<statement>Estopuedequeincluyaalvehculoquepudo
habervendidorecientementeoporelcualhayafirmado
unafianza.</statement>
</helptext>
</question>
</questions>
iLocate Match Summary
TheiLocateMatchSummaryisafeaturethatcanbeenabledinaparametersetforUS
implementations(thisfeatureisnotsupportedwithUKimplementations).WheniLocateMatch
Summaryisenabledandausercannotbelocatedbasedonthedatasubmitted,IdentityVerif ication
providesasummaryofthematchqualityforcombinationsofdataattributes.Matchqualityislabeled
asgood,moderate,orpoor.Forexample,ifname,address,andDOBaresubmitted,thematch
summarylabelsthebestmatchencounteredforthecombinationsofnameandaddress,nameand
DOB,andaddressandDOB.Italsoidentif ieswhethertheaddresscouldbeverif iedasdeliverableby
theUSPostalService.
t ransact i onResponse Message wi t h Mat ch Summary I nf ormat i on
ThefollowingexampleshowsaresponsemessagethatincludesiLocateMatchSummaryinformation
intheinformationelement.Theinformationelementalsoincludestextthatcanbeusedtogenerate
promptsforacallcenteragenttocorrectdataandprovideadditionaldataabouttheuser.
Followingthemessageisasamplefromacallcenterapplicationthatshowsatablewithmatch
summaryinformation.
FIN11016 July 2014
<env:Header/>
<env:Body>
datatypes">
<transactionstatus>
<information>
<detailcode>individual_not_found</detailcode>
<detaildescription>Failed:IndividualNot
Located</detaildescription>
<simpledetail>
<text>IdentityVerificationwasunabletolocatethe
individualbasedontheinformationprovided.</text>
</simpledetail>
<simpledetail>
<text>PleaserefertoyourQuickReferenceGuidefortips
onretryingtheverification.</text>
</simpledetail>
</information>
<information>
<detailcode>callcenterassist</detailcode>
<detaildescription>CallCenterAssist
details</detaildescription>
<complexdetail>
<heading>parameter.custom.callcenterassist.retry.limit.
threshold</heading>
<simpledetail>
<text>10</text>
</simpledetail>
</complexdetail>
FIN11016 July 2014
<complexdetail>
<heading>correction.to.name</heading>
<simpledetail>
<text>Providecorrectiontonameentered</text>
</simpledetail>
</complexdetail>
<complexdetail>
<heading>provide.previous.name</heading>
<simpledetail>
<text>Providepreviousname</text>
</simpledetail>
</complexdetail>
<complexdetail>
<heading>correction.to.address</heading>
<simpledetail>
<text>Providecorrectionstotheaddressentered</text>
</simpledetail>
</complexdetail>
<complexdetail>
<heading>provide.previous.address</heading>
<simpledetail>
<text>Providepreviousaddress</text>
</simpledetail>
</complexdetail>
<complexdetail>
<heading>provide.birthdate</heading>
<simpledetail>
<text>ProvideDateofBirth</text>
</simpledetail>
</complexdetail>
<complexdetail>
<heading>provide.ssn4</heading>
<simpledetail>
<text>ProvidelastfourdigitofSSN</text>
</simpledetail>
FIN11016 July 2014
</complexdetail>
<complexdetail>
<heading>provide.ssn9</heading>
<simpledetail>
<text>ProvidefullSSN</text>
</simpledetail>
</complexdetail>
</information>
<information>
<detailcode>ipcountryorigin</detailcode>
<detaildescription>IPaddresscountryof
origin:</detaildescription>
<complexdetail>
<heading>IPAddressCountryofOrigin</heading>
<simpledetail>
<text>US</text>
</simpledetail>
<simpledetail>
<text>UnitedStates</text>
</simpledetail>
</complexdetail>
</information>
<information>
<detailcode>ilocate.match.summary</detailcode>
<detaildescription>DetailsoftheiLocatematchsummary
process</detaildescription>
<complexdetail>
<heading>name.address.match</heading>
<complexdetail>
<heading>description</heading>
<simpledetail>
<text>NameandAddress</text>
</simpledetail>
FIN11016 July 2014
</complexdetail>
<complexdetail>
<heading>match.quality</heading>
<simpledetail>
<text>moderate.match</text>
</simpledetail>
</complexdetail>
</complexdetail>
<complexdetail>
<heading>name.dob.match</heading>
<complexdetail>
<simpledetail>
<text>NameandDateofBirth</text>
</simpledetail>
</complexdetail>
<complexdetail>
<simpledetail>
<text>good.match</text>
</simpledetail>
</complexdetail>
</complexdetail>
<complexdetail>
<heading>address.dob.match</heading>
<complexdetail>
<simpledetail>
<text>AddressandDateofBirth</text>
</simpledetail>
</complexdetail>
<complexdetail>
<simpledetail>
<text>poor.match</text>
</simpledetail>
FIN11016 July 2014
</complexdetail>
</complexdetail>
<complexdetail>
<heading>address.delivery.point.verified</heading>
<complexdetail>
<simpledetail>
<text>AddressverifiedasdeliverablebyUSPostal
Service</text>
</simpledetail>
</complexdetail>
<complexdetail>
<simpledetail>
<text>good.match</text>
</simpledetail>
</complexdetail>
</complexdetail>
</information>
</env:Body>
</env:Envelope>
Tabl e Generat ed by Cl i ent Appl i cat i on
Thefollowingscreenshotshowsatablegeneratedinaclientscallcenterapplicationtopresentthe
iLocateMatchSummaryinformationtoacallcenteragent.
FIN11016 July 2014
Error: Transaction Expired
ThissectionshowsaresponsetothesameiAuthexamplepresentedonpage51,butinthisexamplethe
continuationmessageisnotsentwithintheallottedtimeperiodandthetransactionexpires.
YourIdentityVerif icationaccountisconf iguredwithaTimeoutparameterthatdeterminesthe
maximumtimeallowedforacontinuationmessagetobesentinresponsetoatransactionResponse
messagewithasetofquestions.Ifthemessageisnotsentwithintheallowedtime,anerrorisreturned
inthenexttransactionResponsemessage.
The Timeout parameter is configured by LexisNexis. For more information on this parameter, or to
change its value, contact your Technical Solutions Consultant.
Recei vi ng t he Error Message
Inthisexample,theTimeoutparameterissetto600secondsandthecontinuationresponsewasnot
sentuntil12minutesafterreceivingthequestions.Theerrorisreturnedintheinformationelementof
thetransactionResponse.
<env:Header/>
<env:Body>
FIN11016 July 2014
<transactionstatus>
<transactionresult>error</transactionresult>
<information>
<informationcode>errordetails</informationcode>
<detailcode>transaction_expired</detailcode>
<detaildescription>Error:Transaction
Expired</detaildescription>
<simpledetail>
<text>Thequestionspresentedwerenotansweredinthe
allottedtime.</text>
</simpledetail>
</information>
</env:Body>
</env:Envelope>
Error: User Under 18 Years of Age
IdentityVerif icationdoesnotperformanytypeofverif icationonapersonwhoislessthan18yearsold.
Theresponsemessageonthenextpageshowstheresponsetoarequestwhentheuserdoesnotmeet
thisagethreshold.
Thiserrorisdifferentthantheresultofaverif icationwhereanagethresholdissetintheclients
parameterset.Ifauserdoesnotmeettheagethresholddef inedinaparameterset(forexample,the
useris19andmustbeatleast21yearsold),thenIdentityVerif icationfailstheuserandreturnsthe
denial_age_verif ication_thresholdfailurecode(see"iCheckVerif ication:UserFailsAgeVerif ication"
onpage103).
When possible, Identity Verification determines the age of the user from public records, rather than
from birthdate data sent in the request. In this example, a birthdate was not provided; Identity
Verification determined from public records that the user is 16 years old.
FIN11016 July 2014
<env:Header/>
<env:Body>
datatypes">
<transactionstatus>
<transactionresult>error</transactionresult>
<information>
<informationcode>errordetails</informationcode>
<detailcode>invalid_transaction_initiate</detailcode>
<detaildescription>Error:InvalidTransaction
Initiate</detaildescription>
<simpledetail>
<text>InvalidDOB:Mustbeatleast18yearsoldin
'person'tag.</text>
</simpledetail>
</information>
</env:Body>
</env:Envelope>
Data in Person Element
Dependingonthetypeofverif icationandtheverif icationoptionsdef inedintheclientsparameter
set,IdentityVerif icationrequiresvaryingamountsofdatatodescribetheuserbeingauthenticated.For
APIdetailsonthepersondatatype,see"persontype"onpage192.Notethatalthoughonlyalimited
setofdataelementsarerequired,themoreinformationyouprovideaboutauser,thegreaterthe
chancethatIdentityVerif icationwillbeabletolocatethatusersidentityduringtheiLocateprocess.
FIN11016 July 2014
Verifications in the United States
Thefollowingtableidentif iesthepersondatarequiredwithverif icationsintheUS,dependingonthe
amountofsocialsecuritynumberdatathatisprovided(allninedigits,justthelastfourdigits,orno
SSN).
The LexID feature is designed so that a unique LexisNexis ID can be provided independent of any
other person data (see "LexID" on page 134). If you provide a LexID in the transaction request with
no other person data, the following requirements are not relevant.
Additional Data Required with Verification Options
Additionaldataisrequiredwhenthefollowingoptionsareconf iguredinyourparameterset:
PatriotAct/OFACListVerification:MustalsoincludeStreet,City,State,ZipCode,DateofBirth,
andPhoneNumber.
AgeVerification:MustalsoincludeDateofBirth.
DriversLicenseVerification:MustalsoincludeDriversLicenseNumberandDriversLicense
State.
SSN (All 9 Digits) SSN (Last 4 Digits) No SSN
9digitSSN
SSNType
FirstName
LastName
Last4digitsofSSN
SSNType
FirstName
LastName
StreetAddress
City
State
ZipCode
AddressContext
SSNType
FirstName
LastName
StreetAddress
City
State
ZipCode
AddressContext
FIN11016 July 2014
Recommended Paramet ers
Althoughphonenumberandemailaddressareneverrequired,LexisNexisrecommendsthatyou
includetheminthepersonelementwhenpossible.
LexID
ALexisNexis
LexIDisauniqueidentif ierfreeofanysensitivepersonallyidentifyinginformation.An
endusersLexIDcanbeprovidedinatransactionrequestwithotherpersondata,suchasaphone
numberoranemailaddress;orindependentofanypersondata.TheusersLexIDisalsoreturnedas
partofthetransactionresponsemessage.WhenyouprovideausersLexIDaspartofausersperson
data,IdentityVerif icationusesthisIDtolocateandauthenticatetheuser.
The LexID feature must be enabled as part of your accounts parameter set in order for you to
receive it in a transaction response. If you are not sure whether this feature is enabled or if you
would like to enable it, contact your Technical Solutions Consultant.
The LexID feature is not available for verifications performed in the UK.
Ret ri evi ng a User s LexI D f or t he Fi rst Ti me
YoucanretrieveausersLexIDbysendingatransactionrequestwiththeminimallyrequiredperson
dataforthatuser.Foralistoftherequiredpersondata,see"Verif icationsintheUnitedStates"onpage
133.
IftheLexIDfeatureisenabledforyouraccount,IdentityVerif icationdisplaystheusersLexIDinthe
transactionresponse,aspartofthespecialfeatureparameter(see"specialfeature"onpage214).The
usersLexIDisreturnedregardlessofwhetherthelexIDparameterwasprovidedinthetransaction
request.ForanexampleofascenariowhereausersLexIDisreturned,see"iAuthVerif ication:One
RoundofQuestions,UserPasses"onpage51.
If you are not sure whether the LexID feature is enabled or if you would like to enable it, contact
your Technical Solutions Consultant.
Provi di ng a User s LexI D i n a Transact i on Request
YouprovideausersLexIDaspartofthepersondatainatransactionrequest,usingthelexID
parameter.Formoreinformation,see"lexID"onpage192.
FIN11016 July 2014
IfyoudonotknowausersLexIDandwouldliketoprovideit,youf irstneedtoretrievetheusers
LexID.Formoreinformation,see"RetrievingaUsersLexIDfortheFirstTime"onpage134.
Recei vi ng a User s LexI D i n a Tr ansact i on Response
IftheLexIDfeatureisenabledforyouraccount,IdentityVerif icationdisplaystheusersLexIDaspart
ofthetransactionresponse,regardlessofwhetherthelexIDparameterisprovidedinthetransaction
request.ForanexampleofascenariowhereausersLexIDisreturned,see"iAuthVerif ication:One
RoundofQuestions,UserPasses"onpage51.
If you are not sure whether the LexID feature is enabled or if you would like to enable it, contact
your Technical Solutions Consultant.
Verifications in the United Kingdom
WithiAuthandiCheckverif icationsintheUK,thefollowingdataisrequiredinthepersonelement:
Forename
Surname
Postcode
StreetAddress
AddressContext
General Guidelines and Best Practices
Considertheseguidelinesandbestpracticeswhenintegratingyourapplicationwith
Send as Much Identity Data As Possible
Themoreinformationyouprovideaboutauser,thegreaterthechancethatIdentityVerif icationis
abletolocatethatusersidentityduringtheiLocateprocess.
FIN11016 July 2014
Include Proper Designations in Military Addresses
WhensubmittingmilitaryaddressestoIdentityVerif ication,ensurethemilitarydesignationsareused
withintheappropriateparametersoftheaddresselement:
IncludeAPOorFPOintheaddresscityparameter.
Includethevalidtwolettercodeintheaddressstateparameter:
AE(ArmedForcesEurope,MiddleEast,AfricaandCanada)
AA(ArmedForcesAmericas)
AP(ArmedForcesPacif ic)
Includeoneofthefollowingforthezipcodeofthemilitaryunit:
Thef ivedigitzipcodeintheaddresszipparameter
Thef ivedigitzipcode+4intheaddresszipplus4parameter
Thefollowingexampleshowstheaddresselementwithamilitaryaddress:
<address>
<addressstreet1>Unit45013Box2666</addressstreet1>
<addresscity>APO</addresscity>
<addressstate>AP</addressstate>
</address>
Do Not Send Parameters with Empty Values
Donotsendaparameterwithanemptyvalue,asshownwiththeaddresscountryparameterinthe
followingexample:
<address>
<addressstreet1>Unit45013Box2666</addressstreet1>
<addresscity>APO</addresscity>
<addressstate>AP</addressstate>
<addresscountry></addresscountry>
</address>
Instead,donotincludetheparameterintherequest.
FIN11016 July 2014
Values for xs:string Data Types
Unlessvaluesarepredef ined,youcanenterastringwithanycharactersintheUnicodecharacterset
whenenteringavalueforaparameterofthexs:stringdatatype.
Toincludeacharacterthathassignif icanceinthemarkupofanXMLdocument(forexample,aless
thansign:<),youmustescapethecharacter.Forexample:
&forthe&(ampersand)character
<forthe<(lessthansign)
>forthe>(greaterthansign)
Seehttp://www.w3.org/TR/xmlschema-2/formoreinformationonhandlingxs:stringdatatypes.
XML Long Data Values
Whenenteringavalueforaparameterthatisanxs:longdatatype,youcanenteravaluebetween
9223372036854775808and922337203685477580.Thexs:longdatatypeisa64bitdatatype.Donot
confuseitwiththe32bitlongintdatatypewhichacceptsvaluesbetween2,147,483,648and
2,147,483,647only.
Enforce Consistent Phone Number Format
Withthephonenumberparameter,theWSDLsupportsanycharacterstringupto20characters.
WhileIdentityVerif icationisabletoparsedifferentstringformatsthatincludeacompletephone
number,LexisNexisrecommendsthatyoudesignyourapplicationsothattheusermustenterthe
numberinaconsistentformat.Thisresultsinmoremeaningfulandconsistentdatawhenviewing
reports.Also,withUSimplementations,acertainformatisrequiredwhenprocessingANI/callerID
spoof ingchecks.
US I mpl ement at i ons
WithUSimplementations,designyourapplicationsotheusermustenteraphonenumberinxxxxxx
xxxxformat.
<phonenumber>
FIN11016 July 2014
</phonenumber>
UK I mpl ement at i ons
WithUKimplementations,designyourapplicationtoallowtheusertoenterupto10numberswitha
spacebetweeneachnumbergroup.Forexample,2012345678or1161234567.
<phonenumber>
</phonenumber>
Store the Transaction ID Returned in a Transaction Response
IdentityVerif icationassignsauniqueIDtoeachtransactionthatitprocesses,andincludesthisIDin
everytransactionresponsemessageitreturnsduringthetransaction.
<transactionstatus>
...
...
DesignyourapplicationtostorethetransactionIDwithothertransactiondatasothatitcanbeused
fordiagnosticsintheeventoffraudorafalsefailure.
Ifyoudiscoveranissuewithatransaction,youcanprovidethetransactionIDtoLexisNexis.A
transactionIDisthefastestandeasiestwayforLexisNexistosearchtheIdentityVerif icationdatabase
forinformationaboutaparticulartransaction.
YoucanalsousethetransactionIDtoenteradispositionaboutatransaction.Adispositionprovides
datatoLexisNexisaboutatransactionthatwasdeterminedtohavebeenassociatedwithfraud.For
informationonenteringdispositions,seeNetviewHelp.
FIN11016 July 2014
ProvidingfeedbacktoLexisNexisaboutfalsefailuresandknowncasesoffraudhelpsLexisNexistune
yourorganization'sconf iguration,aswellasanalyzesystemfeaturesinanefforttocontinuously
improvetheIdentityVerif icationservice.
Capture Consumers IP Address
Ifpossible,capturetheIPaddressoftheconsumersdeviceandsenditwiththetransactionrequest.
Theipaddressparameterisinthecredentialtypedatatype,whichispartofthetransactionelement.
Formoreinformation,see"credentialtype"onpage184.
<venue>
<online>
<credential>
</credential>
</online>
</venue>
HowyoucapturetheIPaddressdependsonwhetherornottheuserisaccessingtheInternetfrom
behindaproxy.
I f t he User i s Behi nd a Proxy
Iftheuserisbehindaproxy,thenyoushouldsendthevalueoftheXForwardedFor(XFF)special
header.TheXFFHTTPheaderisthestandardforidentifyingtheoriginatingIPaddressofaclient
connectingtoawebserverthroughanHTTPproxy.XFFheadersaresupportedbymostproxyservers,
soiftheuserisbehindaproxythentherequestmessagemostlikelyincludestheXFFspecialheader.
WithoutusinganXFFheaderorsimilartechnique,anyconnectionmadethroughaproxywillreveal
theoriginatingIPaddressoftheproxyserver,nottheuser'sdevice.
I f t he User i s Not Behi nd a Proxy
IftheuserisnotbehindaproxyandyourapplicationiswritteninJava,youcanobtaintheusersIP
addressusingtheHttpServletRequestgetRemoteAddr()method.Forexample:
FIN11016 July 2014
Stringip_address=request.getRemoteAddr();
Testing Your Integration| 140
FIN11016 July 2014
Chapt er 5
Test i ng Your
I nt egrat i on
I n This Chapt er
TestingCycle
Overview,page141
Connectingtothe
TestEnvironment,
page142
SimulatorMode
Values,page143
SendaRequestin
TestingMode,
page150
FIN11016 July 2014
Testing Cycle Overview
LexisNexisprovidesatestenvironmentinwhichyoucantestyourintegrationbeforedeployingitto
yourcustomers.Therearetwotestingmodes:simulatedandtesting.Themodeisspecif iedinthe
settingselementofeachrequestyousendtotheIdentityVerif icationwebservice.
i When performing verifications in simulated or testing mode, do not use the names of famous people
as it may trigger an audit of LexisNexis. Instead, use your data or customer data.
Simulated Mode
First,testallthebasicfunctionsofyourintegrationbysendingrequestsinsimulatedmode.In
simulatedmode,IdentityVerif icationdoesnotfullyprocessarequestbutinsteadreturnsacanned
response.Thisenablesyoutoforcedifferentresponsetypestoensurethatyourintegrationishandling
themproperly.Youcannottestyourcustomparametersetinsimulatedmode.
Forinstructionsonrunningatransactioninsimulatedmode,seeSendaRequestinSimulatedMode,
page142.
Testing Mode
Aftercompletingyoursimulatedtestcycleandf ixinganybugsthatwereidentif ied,youshouldsend
requestsintestingmode.Intestingmode,IdentityVerif icationfullyprocessestherequestsandallows
youtotestyourapplicationandthecustombehaviordef inedinyourparameterset.Youarenotbilled
fortransactionsprocessedintestingmode,butthereisalimittothenumberoftesttransactionsyou
canprocess.
Forinstructionsonrunningatransactionintestingmode,seeSendaRequestinTestingMode,page
150.
FIN11016 July 2014
Connecting to the Test Environment
YoucanconnectwiththeIdentityVerif icationtestenvironmentusingeitherusernameandpassword
oraclientcertif icate.AccesstheWSDLforthetestenvironmentatoneofthefollowingURLs:
Whenusingusernameandpasswordforauthentication,usetheIdentityVerif icationWSDLatthis
locationtoaccessthecorrectSOAPendpoint:
https://staging.verid.com/carbon/ws?WSDL
Whenauthenticatingusingaclientcertif icate,usetheIdentityVerif icationWSDLatthislocation
toaccessthecorrectSOAPendpoint:
https://stagingcert.verid.com/carbon/ws?WSDL
FormoreinformationonaccessingtheIdentityVerif icationWSDL,see"IntegratingwithIdentity
Verif ication"onpage44.
It is possible to perform your testing against the production environment instead of the test
environment. In the production environment, you are not charged a transaction fee for any
transactions run in testing or simulated mode. Check with your Technical Solutions Consultant to
determine which environment you should use during your testing cycle.
Send a Request in Simulated Mode
Insimulatedmode,IdentityVerif icationdoesnotfullyprocessarequestbutinstead,returnsa
cannedresponse.
Tosendarequestmessageinsimulatedmode:
Setthefollowinginthesettingselement:
Setthemodeparameterequaltosimulated.
Includethesimulatormodeparameterandsetittothevalueoftheresponsescenarioyouwishto
simulate.See"SimulatorModeValues"onpage143foralistofpossiblevalues.
FIN11016 July 2014
Exampl e
Thefollowingsettingselementdirectsthesimulatortorespondtoacontinuationmessageasthough
theuserfailedtheKBAquestions.Therulesetparameterisignoredbythesimulatorsinceresponses
arepredef inedanddoesnotvarybasedonsettingsdef inedinaparameterset.
<settingsxmlns="">
<mode>simulated</mode>
<simulatormode>failediauthquestions</simulatormode>
<task>iauth</task>
</settings>
Simulator Mode Values
Thefollowingtabledescribessimulatormodevaluesthatsimulateerrorandfailureresponses.The
tablealsoidentitieswhetheramodecanbeusedwithanIdentityTransactionmessage,Continuation
message,orboth.
Value Description
Identity
Transaction
Continuation
random Thismoderandomlyselectsfromamongtheother
simulationmodesandreturnsaresponse.
Yes Yes
ValuesthatSimulateErrors
communications_error TherewasacommunicationserrorwithintheIdentity
Verificationsystem.
Yes Yes
FIN11016 July 2014
internal_
application_
error
Therewasaninternalapplicationerrorwithinthe
IdentityVerificationsystem.
Yes Yes
invalid_
information
Thesubmittedcontinuationrequestdidnotcontain
completequestionanswerdetails(forexample,the
requestcontainedanswerstoonly2ofthe3questions).
No Yes
invalid_login IdentityVerificationreceivedinvalidlogininformation. Yes Yes
invalid_mode Aninvalidmodewasprovidedinthesettingstype
elementoftherequest.
Yes Yes
invalid_parameterlist Thespecifiedparameterset(ruleset)doesnotexist. Yes No
invalid_
simulator_mode
Thespecifiedsimulatormodevalueisnotvalid. Yes Yes
invalid_
transaction_
continue
Therewasanerrorassociatedwithacontinuation
request.Caninclude,butisnotlimitedtoinvalid
messagestructure,missinginformation,oratransaction
thathasalreadybeenclosed.
No Yes
invalid_
transaction_
initiate
Therewasanerrorwithintheinitialtransactionrequest.
Caninclude,butisnotlimitedtoinvalidcharacters
includedintherequestormissingdataelements.
Yes No
no_test_tokens Theallocatednumberoftesttransactionsassociated
withyouraccounthasbeenexceeded.
Yes No
transaction_
expired
Thetimeallocatedtoansweringquestionsexpired. No Yes
Value Description
Identity
Transaction
Continuation
FIN11016 July 2014
unknown_
database_
response
IdentityVerificationreceivedanunknownresponse
fromthedatabase.
Yes Yes
xml_data_
integrity
ThestructureoftheXMLmessagereceivedisinvalidor
becamecorruptintransit.
Yes Yes
ValuesthatSimulateFailures
address.
warnings
Anaddressassociatedwiththeindividualmeetsthe
client'sdefinitionofahighriskaddress.
Yes No
age.match.
quality
Thesubmittedbirthdatedidnotmatchthepublic
records.
Yes No
age.
notavailable
Thebirthdateoftheindividualcouldnotbedetermined
fromthepublicrecords.
Yes No
age.under.
threshold
Theindividualdoesnotmeettheagerequirements. Yes No
blocked Thetransactionwasblockedbecauseitwasa
subsequentattempttoauthenticateauser,without
modifyingdataelementsthataddressthereasonfora
previousfailure/denial.Forexample,ifthesystem
returnedanIndividualnotLocatedmessagewitha
previousrequestwithinaconfiguredlookbackperiod,
andyouthenattemptedtoauthenticatethesameuser
withoutchanginganyoftheprovideddata,Identity
Verificationissuesthismessageandblockthe
transaction.
Yes No
call_center_
assist
Theindividualwasnotlocated.Theapplicationshould
presentarequestforcorrectingpersonalinformation.
Yes No
Value Description
Identity
Transaction
Continuation
FIN11016 July 2014
denial Thetransactionwasdenied.Currently,thisgeneral
denialcodeisonlyassociatedwiththeIdentity
Verificationexclusionlistfeature,whichisaclient
specificgraylistoption.
Yes No
denial_address_
violation_pobox
ThesubmittedaddressisPObox. Yes No
denial_address_
violation_
general
Thesubmittedaddressisageneraldeliveryaddress. Yes No
denial_address_
warning
Theindividualisassociatedwithahighriskaddress. Yes No
denial_age_
verification_
mismatch
Thesubmitteddateofbirthdoesnotmatchthe
discovereddateofbirthwithintheconfiguredthreshold.
Yes No
denial_age_
verification_
not_provided
Thebirthdateisrequiredandwasnotprovidedinthe
request.
Yes No
denial_age_
verification_
threshold
Theindividualdoesnotmeettheagerequirements. Yes No
denial_age_
verification_
undetermined
Thebirthdateoftheindividualcouldnotbedetermined
fromthediscoveredrecords.
Yes No
denial_aml_
check_not_pass
TheindividualdidnotpassanAntiMoneyLaundering
(AML)check.
(ThismodeissupportedwithUKimplementationsonly.)
Yes No
Value Description
Identity
Transaction
Continuation
FIN11016 July 2014
denial_
cumulative_
transaction_
activity_amount
Theindividualhasexceededtheallowedcumulative
dollarlimitfortransactionsfortheconfiguredperiodof
time.
Yes No
denial_
cumulative_
transaction_
activity_
frequency
Theindividualhasexceededtheallowedtransaction
attemptlimitfortheconfiguredperiodoftime.
Yes No
denial_
currentaddress_
notcurrent
Thesubmittedpostaladdressdoesnotappeartobe
current.
Yes No
denial_
currentaddress_
notfound
Thesubmittedaddresscouldnotbefound. Yes No
denial_
currentaddress_
notmostrecent
Thesubmittedpostaladdressdoesnotappeartobethe
mostrecent.
Yes No
denial_driverslicense_
match_failure
Thesubmitteddriverslicensedoesnotsufficiently
matchthediscoveredinformation.
Yes No
denial_
driverslicense_
not_provided_
failure
Driverslicenseinformationwasnotsubmittedanditis
mandatorybasedonsettingsintheparameterset.
Yes No
Value Description
Identity
Transaction
Continuation
FIN11016 July 2014
denial_
driverslicense_
undiscovered_
failure
Adriverslicenserecordcouldnotbefoundthat
matchesthesubmittedinformation.
Yes No
denial_group_
iauth_failure_
frequency
Theindividualhasexceededthelimitofpreviouslyfailed
iAuthtransactionswithintheconfiguredperiodoftime
acrossadefinedgroupofaccounts.
Yes No
denial_group_
transaction_
frequency
Theindividualhasexceededtheallowedtransaction
attemptlimitwithinadefinedgroupofaccountsforthe
configuredperiodoftime.
Yes No
denial_iauth_
failed_too_
recently
TheindividualhaspreviouslyfailedaniAuthwithinthe
Yes No
denial_identity_event Anidentityeventwasdiscoveredfortheindividual.An
identityeventindicatesthatarecordabouttheuserwas
foundindatacollectedfromANI/callerIDspoofing
services,IPaddresslookupservices,andpublicrecord
searchcompanies.Forexample,anidentityeventcan
indicatethatsomeonerecentlypurchasedapublic
recordsearchabouttheuser,orthattheusersphone
numberwasthedestinationphonenumberofaspoofed
call.
Yes No
denial_
individual_
reported_dead
Theindividualisreportedtobedeceased. Yes No
denial_ip_
flagging
TheoriginatingIPaddressviolatedoneormoreofthe
configuredrulesfortheaccount.Forexample,theIP
Addressexhibitsanonymizingbehavior.
Yes No
Value Description
Identity
Transaction
Continuation
FIN11016 July 2014
denial_
phonenumber_
not_match
Thesubmittedphonenumberdoesnotmatchanyofthe
phonenumbersdiscoveredfortheindividual.
Yes No
denail_
phonenumber_
not_provided
Thephonenumberwasnotsubmittedanditis
mandatorybasedonsettingsintheparameterset.
Yes No
denial_risk TheindividualhasexceededtheallowedIdentityRisk
Scorethreshold.
Yes No
denial_ssn_dob_
mismatch
Thesubmitteddateofbirthisaftertheissuancedateof
thediscoveredSSNoftheindividual.
Yes No
denial_ssn_
match_violation
ThesubmittedSSNdoesnotmatchthediscoveredSSN
withintheconfiguredthreshold.
Yes No
denial_ssn_not_
provided
TheSSNwasnotsubmittedanditismandatorybasedon
settingsintheparameterset.
Yes No
failed_iauth_
questions
TheindividualfailedtheiAuthquestions. No Yes
failed_icheck Theindividualcouldnotbesufficientlyverifiedbasedon
theinformationprovided.
Yes No
individual_not_
found
Basedontheinformationprovided,theindividualcould
notbelocated.
Yes No
insufficient_
info_for_
questions
Theindividualhasbeenlocated,butthereisinsufficient
datatopresenttheconfiguredminimumnumberof
questions.
Yes Yes
Value Description
Identity
Transaction
Continuation
FIN11016 July 2014
Send a Request in Testing Mode
Intestingmode,IdentityVerif icationfullyprocessestherequestsandallowsyoutotestyour
applicationandthecustombehaviordef inedinyourparameterset.
Tosendarequestmessageintestingmode,setthemodeparameterinthesettingselementequalto
testing.
Exampl e
Thefollowingsettingselementspecif iesthatthetransactionshouldbeprocessedintestingmode.In
testingmode,youcanspecifythecustomparametersetconf iguredforyouraccount.
<settingsxmlns="">
<mode>testing</mode>
<task>iauth</task>
</settings>
ipcountry_
denial
TheIPaddressassociatedwiththetransactionwas
denied.
Yes No
multiple_
individuals_
found
Multipleindividualswerefoundbasedonthe
informationsubmittedanditwasnotpossibleto
uniquelyidentifytheindividualandpresentadefinitive
setofquestions.
Yes No
passed Thetransactionpassed. Yes Yes
questions Questionsfortheindividualtoanswer. Yes Yes
Value Description
Identity
Transaction
Continuation
Going Live with Your Integration| 151
FIN11016 July 2014
Chapt er 6
Goi ng Li ve wi t h Your
I nt egrat i on
I n Thi s Chapt er
GoingLivewith
YourIntegration
Overview,page152
Connectingtothe
Production
Environment,
page152
SendaRequestin
LiveMode,page
152
FIN11016 July 2014
Going Live with Your Integration Overview
Thischapterprovidesguidelinesfordeployingyourapplicationintheproductionenvironment.This
stageisoftenreferredtoasgoinglive.
Connecting to the Production Environment
Whenyouarereadytogolivewithyourapplication,youneedtoconnectwiththeproduction
environmentratherthanthetestenvironment.
YoucanconnectwiththeIdentityVerif icationproductionenvironmentusingeitherusernameand
passwordoraclientcertif icate.AccesstheWSDLfortheproductionenvironmentatoneofthe
followingURLs:
Whenusingusernameandpasswordforauthentication,usetheIdentityVerif icationWSDLatthis
locationtoaccessthecorrectSOAPendpoint:
https://netview.verid.com/carbon/ws?WSDL
Whenauthenticatingusingaclientcertif icate,usetheIdentityVerif icationWSDLatthislocation
toaccessthecorrectSOAPendpoint:
https://netviewcert.verid.com/carbon/ws?WSDL
FormoreinformationonaccessingtheIdentityVerif icationWSDL,see"ConnectingtotheIdentity
Verif icationWebService"onpage46.
Send a Request in Live Mode
Afteryourpilotiscompleteandalldesiredchangesareimplementedandtested,youarereadytogo
livewithyourapplication.
Tosendarequestmessageinlivemode:
Setthemodeparameterinthesettingselementequaltolive.
FIN11016 July 2014
Example
<settingsxmlns="">
<mode>live</mode>
<task>iauth</task>
</settings>
API Reference| 154
FIN11016 July 2014
Chapt er 7
API Ref erence
I n Thi s Chapt er
APIReference
Overview,page155
WSDLLocation,
page155
Service
Description,page
156
Requestand
Response
Messages,page162
IdentityVerif ication
Message,page164
API Reference| 155
FIN11016 July 2014
API Reference Overview
ThischapterprovidesanapplicationprogrammingreferencefortheIdentityVerif icationwebservice.
Fortaskorientedinformationontheoverallintegrationprocess,see"IntegratingwithIdentity
Verif ication"onpage44
WSDL Location
Theoperationsprovidedbyawebservicearedef inedinaWSDL.TheWSDLfortheIdentity
Verif icationwebserviceislocatedatoneofthefollowingURLs.
FormoreinformationonaccessingtheWSDL,see"ConnectingtotheIdentityVerif icationWeb
Service"onpage46.
Environment Type of Authentication WSDL URL
Production usernameandpassword https://netview.verid.com/carbon/
ws?WSDL
clientcertificate https://netviewcert.verid.com/carbon/
ws?WSDL
Test usernameandpassword https://staging.verid.com/carbon/
ws?WSDL
clientcertificate https://stagingcert.verid.com/carbon/
ws?WSDL
API Reference| 156
FIN11016 July 2014
Service Description
ThissectiondescribestheIdentityVerif icationwebservice.Subsequentsectionsprovidedetailson
eachoftherequestandresponsemessagessupportedbytheservice,andthedatatypesincludedin
thosemessages.
Service Name
ThenameoftheIdentityVerif icationwebserviceisCarbonWebService.
Theservicedef initionintheWSDLidentif iesthelocation,orendpoint,ofthewebservice.The
followinglinesofsourcearefromtheWSDLfortheproductionenvironment;theWSDLforthetest
environmentidentif iesadifferentendpoint.
WSDL Sour ce
<s0:servicename="CarbonWebService">
<s0:portbinding="s2:CarbonSoapBinding"name="CarbonSoapPort">
<s3:addresslocation="https://netview.verid.com:443/carbon/ws"/>
</s0:port>
</s0:service>
</s0:service>
In the source code above, <s0:port binding="s2:CarbonSoapBinding" name="CarbonSoapPort"> is

the end point.
Target Namespace
AnamespaceisacollectionofXMLelementsandattributesidentif iedbyanInternationalized
ResourceIdentif ier(IRI).TheIdentityVerif icationwebservice(CarbonWebService)usesthehttp://
www.w3.org/2001/XMLSchemanamespace,whichisadeclaredandreservednamespacethatcontains
elementsandattributesdef inedbytheWorldWideWebConsortium(W3C).Seethefollowing
documentsformoredetailsontheXMLschema:
XML Schema Part 1: Structures
XML Schema Part 1: data types
API Reference| 157
FIN11016 July 2014
AWSDLcandeclareatargetnamespace.Atargetnamespaceisanamespaceforanadditional
collectionofelementsandattributesthatareneededforaparticularservice.Thetargetnamespacefor
theCarbonWebServiceishttp://integration.carbon.verid.com.
WhenyourwebsiteapplicationsendsSOAPrequeststotheCarbonWebService,the
CarbonWebServicechecksthattheelementsandattributesinthatrequestexistinthedeclared
namespaces.
WSDL Sour ce
<s0:definitionsname="CarbonServiceDefinitions"targetNamespace="http://
integration.carbon.verid.com"xmlns=""xmlns:s0="http://schemas.xmlsoap.org/wsdl/"
xmlns:s1="java:com.verid.carbon.integration.datatypes"xmlns:s2="http://
integration.carbon.verid.com"xmlns:s3="http://schemas.xmlsoap.org/wsdl/soap/">
Port Type
Aporttypeisanamedsetofoperationsandtheinputandoutputmessagesusedforthoseoperations.
TheCarbonWebServiceincludesoneporttype,whichdef inessixoperations.
API Reference| 158
FIN11016 July 2014
Clickontherequest(input)andresponse(output)messageslistedinthistableformoredetail.
WSDL Sour ce
<wsd:portTypename="Carbon">
<wsd:operationname="identityVerification">
<wsd:inputmessage="tns:IdentityVerification"/>
<wsd:outputmessage="tns:transactionResponse"/>
</wsd:operation>
<wsd:operationname="continuation">
name Carbon
operations identityVerification Thisoperationisusedtoinitiateaverification.
Duringthisoperation,yourapplicationsendsa
messagethattellsIdentityVerificationwhattype
ofverificationtoperformandprovidesthe
necessarydataonthepersonandthe
transaction.
Request:IdentityVerificationMessage
Response:transactionResponseMessage
continuation Duringthisoperation,yourapplicationsendsa
messagewithanswersprovidedbytheuserin
responsetothesetofverificationquestions
presentedbyIdentityVerification.
Request:continuationMessage
Response:transactionResponseMessage
authenticationCheck Thisoperationisnotyetsupported.
resume Thisoperationisnotyetsupported.
disposition Thisoperationisnotyetsupported.
assertion Thisoperationisusedbydataproviders
applicationswhensendinginformationto
IdentityVerification.
API Reference| 159
FIN11016 July 2014
<wsd:inputmessage="tns:continuation"/>
</wsd:operation>
<wsd:operationname="resume">
<wsd:inputmessage="tns:resume"/>
</wsd:operation>
<wsd:operationname="authenticationCheck">
<wsd:inputmessage="tns:authentication"/>
</wsd:operation>
<wsd:operationname="disposition">
<wsd:inputmessage="tns:disposition"/>
</wsd:operation>
<wsd:operationname="assertion">
<wsd:inputmessage="tns:assertion"/>
<wsd:outputmessage="tns:assertionResponse"/>
</wsd:operation>
</wsd:portType>
API Reference| 160
FIN11016 July 2014
Binding
Abindingdef inesthemessageformatandthetransportprotocolforoperationsandmessagesdef ined
byaparticularporttype.TheCarbonporttypehasonebinding.
WSDL Sour ce
<wsd:bindingname="CarbonSoapBinding"type="tns:Carbon">
<soap:bindingstyle="document"transport="http://schemas.xmlsoap.org/soap/http">
<wsd:operationname="identityVerification">
<soap:operation/>
<wsd:input>
<soap:bodyparts="IdentityVerificationMsg"use="literal"/>
</wsd:input>
<wsd:output>
<soap:bodyparts="TransactionResponseMsg"use="literal"/>
name CarbonSoapBinding
operations identityVerification
continuation
resume
authenticationCheck
disposition
assertion
style document
Withadocumentstylebinding,SOAPmessages
senttoIdentityVerificationshouldbeplaced
directlyintothebodyportionoftheSOAP
envelope;theyshouldnotbeenclosedwithina
wrapperelement,whichisthecasewithRPCstyle
bindings.
transport http://schemas.xmlsoap.org/soap/http
Thisvalueindicatesthetransportmethod(HTTP)
thatshouldbeusedtosend/receivemessages.
API Reference| 161
FIN11016 July 2014
</wsd:output>
</wsd:operation>
<wsd:operationname="continuation">
<soap:operationstyle="document"/>
<wsd:input>
<soap:bodyparts="TransactionContinueMsg"use="literal"/>
</wsd:input>
<wsd:output>
</wsd:output>
</wsd:operation>
<wsd:operationname="resume">
<wsd:input>
<soap:bodyparts="TransactionResumeMsg"use="literal"/>
</wsd:input>
<wsd:output>
</wsd:output>
</wsd:operation>
<wsd:operationname="authenticationCheck">
<wsd:input>
<soap:bodyparts="TransactionAuthenticationMsg"use="literal"/>
</wsd:input>
<wsd:output>
</wsd:output>
</wsd:operation>
<wsd:operationname="assertion">
<wsd:input>
<soap:bodyparts="AssertionMsg"use="literal"/>
</wsd:input>
<wsd:output>
<soap:bodyparts="AssertionResponseMsg"use="literal"/>
API Reference| 162
FIN11016 July 2014
</wsd:output>
</wsd:operation>
<wsd:operationname="disposition">
<soap:operation/>
<wsd:input>
<soap:bodyparts="DispositionMsg"use="literal"/>
</wsd:input>
</wsd:operation>
</wsd:binding>
Request and Response Messages
Thenextfewsectionsdescribethefollowingrequest(input)andresponse(output)messagesusedto
communicatewiththeIdentityVerif icationwebservice:
IdentityVerif icationMessage,page164
continuationMessage,page166
transactionResponseMessage,page167
How the Message Documentation Is Organized
Thedocumentationforeachmessageincludesfoursubsections:RootElement,Parameters,WSDL
Source,andMessageSample.
Root El ement
Thissectionidentif iestherootelementofthemessage.
API Reference| 163
FIN11016 July 2014
Par amet er s
Thissectionprovidesatabledescribingthevalidparametersfortherootelementofthemessage.The
tableincludesfourcolumns:
WSDL Sour ce
ThissectiondisplaysthetextforthatmessagefromtheWSDLf ile.
Message Sampl e
Thissectionprovideslinkstomessagesamplesin"IntegratingwithIdentityVerif ication"onpage44.
Name NameoftheXMLelement.
Type Nameofthedatatype.
DatatypeswiththexsprefixaresimpledatatypesthatarepartoftheXMLschema
namespacedefinedat:xmlns:xs="http://www.w3.org/2001/XMLSchema"
DatatypeswiththestnsprefixaredefinedintheIdentityVerificationWSDL.Some
ofthesearecomplexdatatypes,whichmeanstheyaremadeupofotherXML
elements.Clickontheparameternametolinktoanothertabledescribingthe
parametersthatcomprisethecomplextype.
Description DescribestheparameterandlistsordescribesitsValidvalues.Whereapplicable,
specifiesamaximum/minimumnumberofcharacters.
Required Specifieswhethertheparameterisrequired(Yes/No)andhowmanytimesitcanbe
includedinamessage:
1:Mandatory;mustbeincludedonce.
1ormore:Mandatory;mustbeincludedatleastonce.
0or1:Optional;canbeincludedonce.
0ormore:Optional;canbeincludedoneormoretimes.
SomeoptionalparametersareflaggedasRecommended.Whiletheparameteris
notrequired,LexisNexisrecommendsthatyouincludeittoassistwiththelocate
processorwithdiagnostictestingintheeventofanerrororfailure.
API Reference| 164
FIN11016 July 2014
IdentityVerification Message
AnIdentityVerif icationmessageprovidesaccountanduserinformationabouttheuserwhoseidentity
youaretryingtoverify.UsethismessagewhensendingarequestforanIdentityVerif icationoperation
duringalltypesofIdentityVerif icationtransactions.
Foraquickreferencetotheminimumsetofparametersthatshouldbeincludedinan
IdentityVerif icationmessage,see"IdentityVerif icationMessage"onpage164.
Root Element
transactionidentityverif ication
Parameters
ThefollowingtabledescribestheparametersforanIdentityVerif icationmessage.
Name Data Type Description Required
settings stns:identity
verification
settingstype
Providesaccountinformationand
identifiesthetypeofverificationyou
wantIdentityVerificationtoperform.
Validvalues:See"settingstype"on
page205.
Yes
1
person stns:persontype Providesinformationabouttheuser.
Validvalues:See"persontype"on
page192.
Yes
1
API Reference| 165
FIN11016 July 2014
WSDL Source
<wsd:messagename="IdentityVerification">
<wsd:partname="IdentityVerificationMsg"element="types:transactionidentity
verification"/>
</wsd:message>
Message Sample
"SendinganIdentityVerif icationMessage"onpage51.
transaction stns:transaction
type
Identifiesthattheverificationis
neededforeitherapurchaseoran
accounttransaction;provides
informationaboutthetransaction.
Account transactions
can include transactions
that involve a purchase.
Typically, purchase
transactions are for
purchases made by
users who do not have
an account with the
client and account
transactions are for
transactions, including
purchases, made by
users who have an
account with the client.
Validvalues:See"transactiontype"
onpage214.
No
0or1
identity
assertion
Youdonotneedtousethisparameter.Itisusedbydataprovidersapplicationswhen
sendinginformationtoIdentityVerification.
API Reference| 166
FIN11016 July 2014
continuation Message
AcontinuationmessageissentasaresponsetoasetofquestionsduringaniAuthauthentication.It
includestheanswersprovidedbytheuserwhoseidentityisbeingverif ied.Usethismessagewhen
continuinganiAuthauthentication.
Foraquickreferencetotheminimumsetofparametersthatshouldbeincludedinacontinuation
message,see"continuationMessage"onpage258.
Root Element
transactioncontinue
Parameters
Thefollowingtabledescribesthevalidparametersforacontinuationmessage.
settings stns:continue
settingstype
Providesaccountinformationandthe
transactionIDthatwasreturnedby
IdentityVerificationinthe
transactionResponsemessage.
Validvalues:See"settingstype"on
page205.
Yes
1
answers stns:answerstype Containstheanswersprovidedbythe
userinresponsetothesetof
questions.
Validvalues:See"answerstype"on
page179.
No
0or1
API Reference| 167
FIN11016 July 2014
WSDL Source
<wsd:messagename="continuation">
<wsd:partname="TransactionContinueMsg"element="types:transactioncontinue"/>
</wsd:message>
Message Sample
"SendingaContinuationMessage"onpage65.
transactionResponse Message
AtransactionResponsemessageprovidesdetailsaboutthestatusoftheverif icationanddirections
aboutthenextsteptheclientapplicationmusttake.
Theclientapplicationreceivesthistypeofmessageinresponsetoallrequestmessages.
Root Element
transactionresponse
Parameters
Thefollowingtabledescribesthevalidparametersforanauthenticationmessage.
transaction
status
stns:transaction
statustype
Provideshighleveldetailsaboutthe
currentstatusofthetransaction,the
transactionnumber,andtheresultof
thetransaction.
Validvalues:See"transactionstatus
type"onpage212.
Yes
1
API Reference| 168
FIN11016 July 2014
WSDL Source
<wsd:messagename="authentication">
<wsd:partname="TransactionAuthenticationMsg"element="types:transaction
authenticationcheck"/>
</wsd:message>
Message Sample
"ReceivingatransactionResponseMessage"onpage55.
Data Types
ThissectiondescribesthedatatypesusedinIdentityVerif icationSOAPmessages.
externalresponses stns:external
responsestype
Providesafullresponsemessage
fromservicesthatintegratewith
IdentityVerification.
Validvalues:See"transactionstatus
type"onpage212
questions stns:questions
type
Providesasetofquestionsthatthe
clientapplicationshouldpresentto
theuser.
Validvalues:See"accountactivity
type"onpage170.
No
0or1
information stns:information
type
Providesinformationrelatedtothe
statusofthetransaction.For
example,itmayincludeanerrorcode
anderrormessagewhenthe
transactionrequestresultsinan
error.
Validvalues:See"informationtype"
onpage188.
No
0ormore
API Reference| 169
FIN11016 July 2014
Clickonadatatypeformoreinformation.
ThefollowingdatatypesarelistedintheWSDLbutareeithernotneededornotsupportedforclient
applications:
accountactivitytype,page170
accountmaintenancetype,page171
accountoriginationtype,page173
accounttype,page174
accountverificationtype,page175
addresstype,page177
answertype,page179
answerstype,page179
billtotype,page180
birthdatetype,page180
callcentertype,page181
choicetype,page182
choicestype,page183
complexdetailtype,page183
credentialtype,page184
credentialtype,page184
customerservicetype,page186
identityverificationsettingstype,page187
informationtype,page188
internationalizationtype,page189
ivrtype,page190
onlinetype,page190
order,page191
orderedbytype,page192
persontype,page192
phonenumbertype,page196
pointofsaletype,page197
productcategorytype,page197
producttype,page199
purchasetype,page200
questiontype,page202
accountactivitytype,page170
riskassessmenttype,page204
riskcomponenttype,page205
securityquestiontype,page205
settingstype,page205
shiptotype,page209
settingstype,page205
simpledetailtype,page211
texttype,page212
transactionstatustype,page212
transactiontype,page214
ukaddresstype,page215
venuetype,page218
assertiontype
batchtype
browsertype
businesstype
headerfieldstype
httpheadertype
identityassertiontype
netviewtype
securityquestiontype
transportlayertype
verificationtype
API Reference| 170
FIN11016 July 2014
account-activity-type
Thisdatatypeprovidesdetailsforaverif icationrelatedtoanaccountactivitytransaction,suchasa
withdrawalortransferoffunds.
account stns:accounttype Typeofaccount.
Validvalues:See"accounttype"on
page174.
Yes
1
account
transaction
stns:producttype Detailsabouttheproducttheuseris
tryingtopurchaseormodify.
Validvalues:See"producttype"on
page199.
No
0ormore
totalamount xs:decimal Totalamountofthetransaction.
Validvalues:Adecimalvalue.Donot
includeathousandsseparator(for
example,use2500.00ratherthan
2,500.00).
Youcanenterawholenumber.
No
0or1
beginning
balance
xs:decimal Beginningbalanceintheusers
account.
10,000.00).
No
0or1
ending
balance
xs:decimal Endingbalanceintheusersaccount.
12,500.00).
No
0or1
API Reference| 171
FIN11016 July 2014
account-maintenance-type
Thisdatatypeprovidesdetailsforaverif icationrelatedtoanaccountmaintenancetransaction.
accountcategory stns:account
categorytype
Typeofaccount.
Validvalues:
banking
brokerage
retirementsavings
retail
utilityservice
loanapplication
creditapplication
phoneservice
cellularphoneservice
cabletvservice
satellitetvservice
internetservice
moneytransfer
onlineaccount
emailaccount
mortgageapplication
publicrecords
creditcard
No
0or1
API Reference| 172
FIN11016 July 2014
account
maintenance
category
stns:account
maintenance
categorytype
Typeofmaintenancetransaction.
Validvalues:
addresschange
phonenumberchange
closeaccount
beneficiarychange
additionalaccount
namechange
passwordreset
passwordchange
adduser
removeuser
changebillinginformation
addpayee
changepayee
linkaccount
pinchange
emailchange
viewevent
addjointaccountholder
reorderchecks
ordercard
stoppayment
addalerts
No
0or1
maintenance
detail
xs:string Informativetextaboutthe
maintenancetransaction.
Validvalues:Astringofcharacters.
Formoreinformation,see"Valuesfor
xs:stringDataTypes"onpage137.
No
0or1
Validvalues: Seeaccounttype,page
174.
Yes
1
API Reference| 173
FIN11016 July 2014
account-origination-type
Thisdatatypeprovidesdetailsforaverif icationrelatedtoanaccountoriginationtransaction.
data stns:complex
detailtype
Additionaldetailpresentedina
bullettypehierarchyofpoints.
Validvalues:See"complexdetail
type"onpage183.
No
0or1
Name Type Description Required
account
category
stns:account
categorytype
Typeofaccount.
Validvalues:
banking
brokerage
retirementsavings
retail
utilityservice
loanapplication
creditapplication
phoneservice
cellularphoneservice
cabletvservice
satellitetvservice
internetservice
moneytransfer
onlineaccount
emailaccount
mortgageapplication
publicrecords
creditcard
No
0or1
API Reference| 174
FIN11016 July 2014
account-type
Thisdatatypeprovidesdetailsabouttheusersaccount.
security
question
stns:security
questiontype
Notsupported.
voice
enrollment
xs:boolean Notsupported.
Validvalues: See"accounttype"onpage174.
Yes
1
accountnumber stns:account
numbertype
Usersaccountnumber.
Validvalues:Astringofcharacters.Formore
information,see"Valuesforxs:stringDataTypes"on
page137.
No
0or1
account
transactionid
stns:account
transactionidtype
AccounttransactionID.
page137.
No
0or1
accountname stns:account
nametype
Usersaccountname.
page137.
No
0or1
API Reference| 175
FIN11016 July 2014
account-verification-type
InanIdentityVerif icationrequest,thetransactionparameterspecif iesthatthetransactioniseithera
purchaseoranaccountverif ication.Ifthetransactionisanaccountverif ication,usethisdatatypeto
specifythatthetransactionisoneofthefollowingtypes:
AccountMaintenancetransactionsupdateormaintaintheusersaccountwithactivitiessuchas
changingapassword,changinganaddress,orclosinganaccount.
AccountActivitytransactionsusetheaccountforamonetaryactivity,suchasmakingawithdrawal
ortransferringfunds.
AccountOriginationtransactionsestablishanewuseraccount.
customerid stns:customerid
type
UserscustomerID.
Validvalues: Astringofcharacters.Formore
page137.
Yes
1ormore
account
maintenance
stns:account
maintenance
type
Detailsaboutthetypeofmaintenancetransaction.
Validvalues: See"accountmaintenancetype"onpage
171.
No
Recommended
Mutuallyexclusive;
enteroneonly
account
activity
stns:account
activitytype
Detailsabouttheaccountactivitytransaction.
Validvalues: See"accountactivitytype"onpage170.
account
origination
stns:account
originationtype
Detailsaboutanaccountoriginationtransaction.
Validvalues: See"accountoriginationtype"onpage
173.
API Reference| 176
FIN11016 July 2014
venue stns:venuetype Typeofenvironmentwherethetransactionistaking
place.
Validvalues: See"venuetype"onpage218.
Yes
1
activitydate stns:transaction
datetype
Dateandtimeofthetransaction.
Validvalues:DatetimevaluesareintheISO8601date
andtimeformat:
YYYYMMDDTHH:MM:SS.SSSZ
Hoursarein24hourformat(forexample,1:00:00pm
is13:00:00).Unlessotherwisespecified,alldatetime
valuesarerecordedinCoordinatedUniversalTime
(UTC),alsoknownasGreenwichMeanTime(GMT)or
Zulu(timezonezero).
Example:
20100615T13:20:05.768Z
Yes
1
risk
assessment
stns:risk
assessmenttype
Usedbytheclienttoprovidedataevaluatingtherisk
associatedwiththetransaction,includingariskscore,
threatassessment,andriskcomponent.
Risk data that you provide in this data

type is unrelated to the Identity Risk
Score feature that can be enabled for
your account. When the Identity Risk
Score feature is enabled, Identity
Verification generates a risk score from
0 to 1000, that quantifies the risk of
fraud associated with a transaction. The
Identity Risk Score can be used as an
additional threshold for passing/failing a
transaction. For more information on the
Identity Risk Score, see Netview Help.
Validvalues:See"riskassessmenttype"onpage204.
No
0or1
API Reference| 177
FIN11016 July 2014
address-type
ThisdatatypeprovidesaddressdetailsforauserintheUnitedStates.ForusersintheUnitedKingdom,
see"ukaddresstype"onpage215.
Whenenteringamilitaryaddress,besuretoincludethepropermilitarydesignations.
Formoreinformation,see "Include Proper Designations in Military Addresses" on page 136.
addressstreet1 xs:string Firstoronlylineofstreetaddress.
Validvalues:Astringofcharacters.Formoreinformation,
see"Valuesforxs:stringDataTypes"onpage137.
Maximumcharacters:150
Yes
1
addressstreet2 xs:string Secondlineofstreetaddress,ifapplicable.
No
0or1
suite xs:string Suiteorapartmentnumber.
No
0or1
addresscity xs:string Cityofaddress.
Validvalues: Astringofcharacters.Formoreinformation,
Yes
1
addressstate xs:string Stateofaddress.
Validvalues:AvalidtwoletterUSPSstatecode
(seehttp://www.usps.com/ncsc/lookups/
usps_abbreviations.html#states).
Maximumcharacters:2
Yes
1
API Reference| 178
FIN11016 July 2014
addresszip xs:string Zipcodeofaddress.
Validvalues:AstringoffivenumericdigitsinNNNNN
format.
Yes
1
addresszip
plus4
xs:string +4digitsofthezipcode.Forexample,ifthefullzipcodeis
123456789,thenenter6789forthisparameter.
Validvalues: AstringoffournumericdigitsinNNNN
format.
No
0or1
addresscountry xs:string Countryofaddress.
Validvalues:USorUSA
No
0or1
addresscontext stns:address
contexttype
Functionoftheaddressfortheuser.Forexample:primary
addressversusavacationaddress.
Validvalues:
primary
secondary
previous
vacation
business
other
Yes
1
addressyearsat xs:decimal Yearsofresidenceattheaddress.
Validvalues:Adecimalvalue.Forexample:1.3,0.2.
No
0or1
occupation
startdate
xs:date Datewhentheuserstartedlivingorworkingatthe
address.
Validvalues: ThedateinYYYYMMDDformat.
No
0or1
API Reference| 179
FIN11016 July 2014
answer-type
Thisdatatypeisusedinacontinuationmessagetoprovideausersanswertoaparticularquestion.
answers-type
Thisdatatypeisusedinacontinuationmessagetoprovideausersanswerstothesetofmultiple
choicequestions.
questionid xs:long IDforaparticularquestion,asprovidedinthe
transactionResponsemessagesentbyIdentityVerification.
Validvalues:
Anintegervaluebetween9223372036854775808and
9223372036854775807
Yes
1
choices stns:choicestype Answerprovidedbytheuser.
Validvalues:See"choicestype"onpage183.
No
0or1
questionsetid xs:long IDforthesetofquestions,asprovidedinthe
transactionResponsemessagesentbyIdentityVerification.
Validvalues:
9223372036854775807
Yes
1
answer stns:answertype Answersprovidedbytheusertoeachofthequestions
presentedfromthequestionset.
Validvalues:See"answertype"onpage179.
No
0ormore
API Reference| 180
FIN11016 July 2014
bill-to-type
Thisdatatypespecif iestowhomtheordershouldbebilled.
birthdate-type
Thisdatatypespecif iestheusersbirthdate.
The user must be at least 18 years old. Identity Verification cannot perform a verification on a
person who is less than 18 years old.
sameas stns:sameastype Specifiesbillingtheuserwhoplacedtheorder.
Validvalue:
orderedby
Yes
Mutually
exclusive;
mustinclude
one
person stns:persontype Specifiescontactinformationfortheusertowhomthe
ordershouldbebilled.
Validvalues:See"persontype"onpage192.
year stns:yeartype Specifiestheyearoftheusersbirthdate.
Validvalues:
Fourdigitinteger.
Forexample:1970
Yes
1
month stns:monthtype Specifiesthemonthoftheusersbirthdate.
Validvalues:
Integerbetween1and12.
Forexample:5forMay
Yes
1
API Reference| 181
FIN11016 July 2014
callcenter-type
Thisdatatypeprovidesdetailsaboutthecallmadebytheusertothecallcenter.
day stns:daytype Specifiesthedayoftheusersbirthdate.
Validvalues:
Integerbetween1and31.
Yes
1
callerphone
number
xs:string Callersphonenumber.
Validvalues:Astringofnumericalcharacters.For
example:1234567890.
No
0or1
credential
method
stns:credential
methodtype
Identifiesthetypeofcredentialusedtoauthenticatethe
user.
Validvalues:
ssn
securityquestion
pin
basic
certificate
token
federated
driverslicense
passport
photoidcard
accountid
birthdate
none
No
0ormore
API Reference| 182
FIN11016 July 2014
choice-type
ThisdatatypeisprovidedinatransactionResponsemessage.Itprovidesananswerwitha
correspondingchoiceID.
callerid xs:string TextdisplayedoncallerIDwhenthecallisreceivedatthe
callcenter.
Validvalues:Astringofcharacters.See"Valuesfor
No
0or1
choiceid xs:long IDcorrespondingtoaparticularmultiplechoiceanswer.
Validvalues:
9223372036854775807
Yes
1
text stns:texttype MultiplechoiceanswercorrespondingtothechoiceID.
Validvalues: See"texttype"onpage212.
No
0ormore
API Reference| 183
FIN11016 July 2014
choices-type
Thisdatatypeisusedinacontinuationmessagetoidentifyausersanswertoamultiplechoice
question.
complex-detail-type
Thisdatatypeallowsyoutosendorreceiveanarrayoftextstrings.Anelementofthisdatatypecan
containalistof0ormorecomplexorsimpledetailarrays.Acomplexdetailtypeelementcannot
containbothsimpleandcomplexdetailarrays.
choiceid xs:long ID,asprovidedinthetransactionResponsemessage,for
theanswerthattheuserchoseforaparticularquestion.
Validvalues:
9223372036854775807
No
0ormore
heading xs:string Headingtextforthedata.
Yes
1
simpledetail stns:simple
detailtype
Singlestringoftextprovidingadditionaldetailaboutthe
transaction.
Validvalues:See"simpledetailtype"onpage211.
No
0ormore
complexdetail stns:complex
detailtype
Youcanincludeacomplexdetailparameterwithina
complexdetailparameters.
No
0ormore
API Reference| 184
FIN11016 July 2014
continue-settings-type
Thisdatatypeusesthesettingstypedatatypeasitsbasedef inition.Foracompletelistofparameters
validforthisdatatype,see"settingstype"onpage205.
credential-type
Thisdatatypeprovidesdetailsaboutthecredentialusedtoauthenticatetheuser.
credential
method
stns:credential
methodtype
user.
Validvalues:
ssn
securityquestion
pin
basic
certificate
token
federated
driverslicense
passport
photoidcard
accountid
birthdate
none
Yes
1ormore
username stns:username
type
Usernameoftheusermakingtheonlinetransaction.
No
0or1
domain stns:domaintype Domainoftheonlinesite.
No
0or1
API Reference| 185
FIN11016 July 2014
organizational
unit
stns:organizational
unittype
Organizationalunit,suchasSales,asdefinedbytheLDAP
oucomponent.
No
0or1
httpheader stns:httpheader
type
Thisparameteriscurrentlynotsupported.IfyouwishtosendHTTPheader
informationinthecredentialtypeelement,contactyourTechnicalSolutions
Consultant.
ipaddress stns:ipaddress
type
IPaddressoftheconsumersdevicefromwhichtheonline
transactionisinitiated.Iftheconsumerisaccessingthe
Internetfrombehindaproxy,besuretosendtheIP
addressoftheconsumersdeviceandnottheoriginating
addressoftheproxyserver.Forguidelinesondoingthis,
see"CaptureConsumersIPAddress"onpage139.
No
0or1
Recommended
machineid stns:machineid
type

The machine-id parameter is not
supported.
No
0or3
API Reference| 186
FIN11016 July 2014
customer-service-type
Thisdatatypeidentif iesthetypeofcredentialusedforacustomerservicetransaction.
credential
method
stns:credential
methodtype
userfortheonlinetransaction.
Validvalues:
ssn
securityquestion
pin
basic
certificate
token
federated
driverslicense
passport
photoidcard
accountid
birthdate
none
No
0ormore
API Reference| 187
FIN11016 July 2014
external-responses-type
identity-verification-settings-type
Thisdatatypeusesthesettingstypedatatypeasitsbasedef inition.Foracompletelistofparameters
validforthisdatatype,see"settingstype"onpage205.
instantId
Response
instantId
Response
PassesaresponsefromtheInstantID,FlexID,or
FraudPointservice.Thisparameterisreturnedwhenthe
FraudPreventionServicesintegrationfeatureisenabled
fortheaccount.
Validvalues:SeetheResponseValuesReferenceGuide
forVerificationandFraudPreventionServices
Integrations,ResponseMessageStructureschapter.
No
0ormore
API Reference| 188
FIN11016 July 2014
information-type
ThisdatatypeisusedintransactionResponsemessagestoprovideadditionalinformationaboutthe
statusofthetransaction.Itmaybeused,forexample,toprovideanerrorcodeanderrormessagewhen
thetransactionrequestresultsinanerror.
information
code
stns:information
codetype
Identifiesthetypeofinformationbeingreturned.
Validvalues:
questiondetails
passeddetails
faileddetails
errordetails
specialfeaturedetails
informationdetails
threatdetails
voiceiddetails
dispositiondetails
presentationdetails
Yes
1
detailcode xs:string Identifiesanerror,failure,orinformationcode.
Validvalues:See"Error,Failure,andInformationCodes"on
page219foralistofcodes.
Yes
1
detail
description
xs:string Stringoftextcorrespondingtothedetailcode.
Yes
1
complexdetail stns:complex
detailtype
Arrayoftextstrings(multiplelinesoftext)providing
additionaldetailaboutthetransaction.
Validvalues:See"complexdetailtype"onpage183.
No
0ormore
simpledetail stns:simple
detailtype
Singlestringoftextprovidingadditionaldetailaboutthe
transaction.
Validvalues:See"simpledetailtype"onpage211.
No
0ormore
API Reference| 189
FIN11016 July 2014
internationalization-type
Thisdatatypeprovidesinformationaboutthelanguageinwhichtheverif icationquestionsare
provided.
language stns:languagetype Identifiesthelanguage.
Validvalues:
spanish
informalspanish
english
No
0or1
languagevenue stns:language
venuetypeI
Identifiestheenvironmentwherethelanguageisused.
Validvalues:
callcenter
pointofsale
online
ivr
No
0or1
API Reference| 190
FIN11016 July 2014
ivr-type
ThisdatatypedescribesthetypeofcredentialusedwithanIVR(InteractiveVoiceResponse)
authentication.
online-type
Thisdatatypeprovidesdetailsaboutthecredentialusedwithanonlineauthentication.
credential
method
stns:credential
methodtype
consumerforthetransaction.
Validvalues:
ssn
securityquestion
pin
basic
certificate
token
federated
driverslicense
passport
photoidcard
accountid
birthdate
none
No
0ormore
credential stns:credential
type
Providesinformationaboutthecredentialusedto
authenticatetheuserfortheonlinetransaction.
Validvalues:See"credentialtype"onpage184.
No
0or1
API Reference| 191
FIN11016 July 2014
order
Thisdatatypeprovidesdetailsaboutanordertheuserisattemptingtoplace.
itemtype stns:producttype Detailsabouttheitemordered.
Validvalues:See"producttype"onpage199.
Yes
1ormore
totalamount xs:decimal Totalamountoftheorder.
Validvalues:Adecimalvalueofarbitraryprecision.A
wholenumbercanbeusedforadecimalvalue.Donot
includeathousandsseparator(forexample,use1100.50
ratherthan1,100.50).
Yes
1
totaltax xs:decimal Totaltaxappliedtotheorder.
No
0or1
totalshipping xs:decimal Totalcostofshippingfortheorder.
No
0or1
merchant xs:string Nameorotheridentifierofthemerchant.
No
0or1
API Reference| 192
FIN11016 July 2014
ordered-by-type
Thisdatatypeidentif ieswhoplacedtheorder.
person-type
Thisdatatypeprovidesinformationabouttheuser.
WhilealloftheseparametersarelistedasoptionalintheWDSL,someofthemare
requiredbasedonthetypeoftransaction,whetheritisaUSorUKtransaction,and
whetherornotasocialsecuritynumberisprovided.Forasummaryofthese
requirements,see"DatainPersonElement"onpage132.
sameas stns:sameastype Specifiesthattheuserwhoplacedtheorderisthesameas
thepersontowhomtheorderisbilled.
Validvalue: billto
Yes
Mutually
exclusive;
must
include
one
person stns:persontype Specifiescontactinformationfortheuserplacingtheorder.
lexID xsstring UsersLexID.ALexIDisauniqueLexisNexisidentifier
freeofanysensitivepersonallyidentifying
information.Formoreinformation,see"LexID"on
page134.
Validvalues:Astringofcharactersindicatingthe
usersLexID.Forexample:007976577987.See
"Valuesforxs:stringDataTypes"onpage137.
No
0or1
API Reference| 193
FIN11016 July 2014
nameprefix xsstring Usersnameprefix,ifapplicable.
Validvalues:Astringofcharacters.Forexample:Mr.
Mrs.,Ms.,Dr.See"Valuesforxs:stringDataTypes"on
page137.
No
0or1
namefirst xsstring Usersfirstname(forename).
Validvalues: Astringofcharacters.See"Valuesfor
Yes
1
namemiddle xsstring Usersmiddlename.
No
0or1
namelast xsstring Userslastname(surname).
Maximum characters:50
Yes
1
namesuffix xsstring Usersnamesuffix.
Validvalues: Astringofcharacters.Forexample:Jr.II,
III.See"Valuesforxs:stringDataTypes"onpage137.
No
0or1
customerid stns:customerid
type
UserscustomerID.
No
0ormore
email stns:emailtype Usersemailaddress.
No
0ormore
API Reference| 194
FIN11016 July 2014
ssn xs:string Userssocialsecuritynumber.
Validvalues: Astringofnumericalcharacters.
Maximumcharacters:9
No
0or1
ssntype stns:ssntype Typeofsocialsecuritynumber.
Validvalues:
ssn4
ssn9
nossn
No
0or1
driverslicense
number
xsstring Usersdriverslicensenumber.
No
0or1
driverslicense
state
xsstring Stateinwhichusersdriverslicensewasissued.
Validvalues: AvalidtwoletterUSPSstatecode
(seehttp://www.usps.com/ncsc/lookups/
usps_abbreviations.html#states).
No
0or1
birthdate stns:birthdate
type
Usersdateofbirth.
Validvalues: See"birthdatetype"onpage180.
No
0or1
Requiredwhen
anagethreshold
isenabled
address stns:addresstype Address(es)associatedwithauserlivingintheUnited
States.ThisparameterisrequiredifaSSNisnot
provided.
Validvalues:See"addresstype"onpage177.
No
0ormore
RequiredwithUS
transactions
unlessssn9is
provided
API Reference| 195
FIN11016 July 2014
ukaddress stns:ukaddress
type
Primaryaddressassociatedwithauserlivinginthe
UnitedKingdom.
Validvalues:See"ukaddresstype"onpage215.
AlthoughtheWSDLindicatesthatyoucanenter
multipleaddresses,IdentityVerificationcurrently
supportsonlyoneukaddressdatatypeinarequest.
Yes
1
phonenumber stns:phone
numbertype
Phonenumber(s)associatedwiththeuser.
Validvalues: See"persontype"onpage192.
No
0ormore
Recommended
occupation xs:string Usersoccupation.
No
0or1
riskassessment stns:risk
assessmenttype
Risk data that you provide in this data

type is unrelated to the Identity Risk
Score feature that can be enabled for
your account. For more information on
the Identity Risk Score feature, see
Netview Help.
No
0or1
API Reference| 196
FIN11016 July 2014
phone-number-type
Thisdatatypeprovidestheusersphonenumberandthecontextinwhichthenumberisused.
phonenumber xs:string Usersphonenumber.
Validvalues:Astringofcharacters.
The WSDL supports any character string

up to 20 characters. LexisNexis
recommends that you design your
application so that the user must enter the
number in a consistent format. This will
result in more meaningful and consistent
data when viewing reports. For more
information, see "Enforce Consistent
Phone Number Format" on page 137.
Yes
1
phonenumber
context
stns:phone
numbercontext
type
Contextinwhichthephonenumberisassociatedwith
theuser.
Validvalues:
home
business
mobile
fax
pager
other
Yes
1
API Reference| 197
FIN11016 July 2014
point-of-sale-type
Thisdatatypeprovidesdetailsaboutapointofsaletransaction.
product-category-type
Thisdatatypeidentif iestheproductcategory.Itisasimpledatatypeelementbasedonthexs:string
datatype.Thevalidvaluesforthisdatatypeare:
credential
method
stns:credential
methodtype
userforthetransaction.
Validvalues:
ssn
securityquestion
pin
basic
certificate
token
federated
driverslicense
passport
photoidcard
accountid
birthdate
none
No
0ormore
merchantzip
code
xs:string Merchantszipcode.
Validvalues:Astringofnumericalcharacters.
No
0or1
API Reference| 198
FIN11016 July 2014
accounting
alcohol
amusementandrecreation
services
apparel
audio
autorentalandLeasing
automotiveservice
baby
backgroundcheck
bond
book
cableorpaytelevision
services
calleridspoofing
camera
certificateofdeposit
computer
concert
constructionmaterial
cosmetic
creditcheck
electronics
equipmentrental
footwear
furnitureorhomefurnishings
future
gameortoy
gas
grocery
hotel
insurance
investmentadvice
jewelry
kitchenandhousewares
lawnandgardenequipment
membershiporganizations
moneytransferin
moneytransferout
motorvehicle
music
musicalinstrument
officeproduct
option
petsupplies
realestate
restaurant
software
sportingandathleticproduct
sportingevent
sportsandrecreationclub
stock
subscriptionsonlinecontent
subscriptionsother
subscriptionsperiodical
tobacco
toolsandhardware
truckingorcourierservice
videopurchase
videorental
wager
other
deposit
withdrawal
billpayment
API Reference| 199
FIN11016 July 2014
product-type
Thisdatatypeprovidesdetailsabouttheproducttheuseristryingtoorder/modify.
product
category
stns:product
categorytype
Productcategory.
Validvalues:See"productcategorytype"onpage197.
Yes
1
model xs:string Productmodel.
Validvalues:Astringofcharacters.See"Valuesforxs:string
DataTypes"onpage137.
No
0or1
vendor xs:string Productvendor.
No
0or1
code xs:string Productcode.
No
0or1
symbol xs:string Productsymbol.
No
0or1
transaction
direction
stns:transaction
directiontype
Direction(buyorsell)ofthepurchasingtransaction.
Validvalues:
buy
sell
No
0or1
productquantity xs:integer Numberofitemsordered.
Validvalues:Awholenumber.
No
0or1
peritem
amount
xs:decimal Priceoftheitem.
Validvalues:Adecimalvalueofarbitraryprecision.Awhole
numbercanbeusedforadecimalvalue.Donotincludea
thousandsseparator(forexample,use1100.50ratherthan
1,100.50).
No
0or1
API Reference| 200
FIN11016 July 2014
purchase-type
Thisdatatypeprovidesdetailsaboutthepurchasetheuserisattemptingtomake.
transactiondate stns:transaction
datetype
Validvalues:DatetimevaluesareintheISO8601dateand
timeformat:
Hoursarein24hourformat(forexample,1:00:00pmis
13:00:00).Unlessotherwisespecified,alldatetimevalues
arerecordedinCoordinatedUniversalTime(UTC),also
knownasGreenwichMeanTime(GMT)orZulu(timezone
zero).
Example:
20100615T13:20:05.768Z
No
0or1
data stns:complex
detailtype
Arrayoftextstrings(multiplelinesoftext)providing
additionaldetailabouttheproduct.
Validvalues:See"complexdetailtype"onpage183.
No
0or1
order Providesorderinformation.
Validvalues:See"order"onpage191.
No
0or1
API Reference| 201
FIN11016 July 2014
payment
method
stns:payment
method
Methodofpayment.
Validvalues:
storecredit
giftcard
moneytransfer
cash
check
creditcard
debitcard
phone
billgeneral
billpaper
margin
other
No
0or1
shipping stns:shippingtype Describestheshippingmethodandthebilltoandshipto
information.
Validvalues: See"shippingtype"onpage210.
No
0or1x
account stns:accounttype Describestheusersaccount.
Validvalues: See"accounttype"onpage174.
Yes
1
venue stns:venuetype Typeofenvironmentwherethetransactionistakingplace.
Validvalues: See"venuetype"onpage218.
Yes
1
transactiondate stns:transaction
datetype
Validvalues:DatetimevaluesareintheISO8601dateand
timeformat:
Hoursarein24hourformat(forexample,1:00:00pmis
13:00:00).Unlessotherwisespecified,alldatetimevalues
arerecordedinCoordinatedUniversalTime(UTC),also
knownasGreenwichMeanTime(GMT)orZulu(timezone
zero).
Example:
20100615T13:20:05.768Z
Yes
1
API Reference| 202
FIN11016 July 2014
question-type
ThisdatatypeprovidesaquestioninasetofquestionspresentedinatransactionResponsewhenthe
transactionresultisquestions.
riskassessment
type
stns:risk
assessmenttype
Risk data that you provide in this data type

is unrelated to the Identity Risk Score
feature that can be enabled for your
account. For more information on the
Identity Risk Score feature, see Netview
Help.
No
0or1
questionid xs:long Identifierforthequestion.Eachquestionwithinasetof
questionshasauniqueID.ThisIDwillneedtobeincluded
inthecontinuationrequestmessagesentwiththeusers
responses.
Validvalues:
Avaluebetween9223372036854775808and
9223372036854775807
Yes
1
answertype stns:answer
selectiontype
Specifiesthetypeofanswerrequiredforthequestion:
singleanswerormultipleanswer.
Validvalues:
single
multiple
Yes
1
API Reference| 203
FIN11016 July 2014
questions-type
ThisdatatypeprovidesasetofmultiplechoicequestionsinatransactionResponsewhenthe
transactionresultisquestions.
text stns:texttype Specifiesthetextofthequestionandthelanguageinwhich
itispresented.
Validvalues:See"texttype"onpage212.
Foralistofthequestiontextpresentedwitheachtypeof
question,see"QuestionText"onpage233
No
0ormore
choice stns:choicetype Specifiesmultiplechoiceanswerstothequestion.
Validvalues:See"choicetype"onpage182.
Yes
1ormore
helptext stns:texttype Specifieshelptextthatcanbedisplayedtoassisttheuserin
understandingandansweringthequestion.
Validvalues:See"texttype"onpage212.
No
0ormore
questionsetid xs:long Identifierforthesetofquestions.ThisIDwillneedtobe
includedinthecontinuationrequestmessagesentwiththe
usersresponses.
Validvalues:
9223372036854775807
Yes
1
question stns:questiontype Questiontobepresentedtotheuser.
Validvalues:See"questiontype"onpage202.
Yes
1ormore
API Reference| 204
FIN11016 July 2014
risk-assessment-type
Thisdatatypeprovidestheriskassessmentdata.
riskscore stns:riskscore Inatransactionrequest,thisparameterisusedtoprovide
ascorespecifiedbytheclient,quantifyingtherisk
associatedwiththetransactionortheuser.
Riskdatathatyouprovideinatransactionrequestis
unrelatedtotheIdentityRiskScorefeature.Formore
informationontheIdentityRiskScorefeature,seeNetview
Help.
Inatransactionresponse,thistypereturnstheIdentity
RiskScore.TheIdentityRiskScoreisanumericvalue,0to
1000,thatquantifiestheriskoffraudassociatedwiththe
transaction.Thegreaterthenumber,thegreatertheriskof
fraud.
Validvalues: Adoubleprecision64bitfloatingpointtype.
Donotincludeathousandsseparator.
Yes
1
threat
assessment
stns:threat
assessment
Thelevelofriskassociatedwiththetransactionoruser.
Thisdatatypeisnotincludedinatransactionresponse
message.
Validvalues:
high
medium
low
indeterminate
No
0or1
riskcomponent stns:risk
componenttype
Usedbytheclienttospecifyariskcategoryand
correspondingriskscore.Thisdatatypeisnotincludedina
transactionresponsemessage.
Validvalues:See"riskcomponenttype"onpage205.
No
0ormore
API Reference| 205
FIN11016 July 2014
risk-component-type
Thisdatatypeprovidesariskscorecorrespondingtoaparticularriskcategory.Thisdatatypeisnot
includedintheriskassessmenttypereturnedinatransactionresponsemessage.
security-question-type
Thisdatatypeisnotsupported.
settings-type
ThisdatatypemustbeprovidedinallrequestssenttotheIdentityVerif icationservice.Itprovides
accountinformationandidentif iesthetypeofverif icationyouwantIdentityVerif icationtoperform.
Thisdatatypeisthebasetypeforidentityverif icationsettingstypeandcontinuesettingstype.
riskcategory stns:riskcategory Riskcategory.
Validvalues:
transaction
identity
verification
biometric
total
credit
Yes
1
riskscore stns:riskscore Usedbytheclienttospecifyascorequantifyingtherisk
associatedwiththetransactionortheuser.
Validvalues: Adoubleprecision64bitfloatingpointtype.
Donotincludeathousandsseparator.
Yes
1
API Reference| 206
FIN11016 July 2014
Thefollowingtableliststheparametersinthebasetypeandtheextensionsfortheidentity
verif icationsettingstypeandcontinuesettingstype.
accountname stns:account
name
type
Specifiestheclientsaccountname.Thisistheaccount
nameprovidedtoyoubyLexisNexis.
Validvalues:Astringofcharacters.See"Integratingwith
IdentityVerification"onpage44
Yes
1
mode stns:modetype Modeinwhichthetransactionshouldberun.
Validvalues:
simulated:Usethismodetosimulatethetransaction,
returningacannedresponse.
testing:Usethismodetofullyprocessthetransaction
inthetestenvironment.
pilot:Usethismodetofullyprocessthetransactionin
theproductionenvironmentduringapilotprogram.
live:Usethismodetoprocessthetransactioninthe
productionenvironmentafteryouhavegonelivewith
yourimplementation.
Yes
1
Thisis
listedas
optionalin
theWSDL,
butitis
required.
ruleset xs:string Specifiestheparametersetthatshouldbeused.A
parameterset,alsoknownasaruleset,referstothe
specificsettingsusedtogoverntheoperationofa
transactionforeachIdentityVerificationclient.Contact
yourTechnicalSolutionsConsultantforthenameofyour
parameterset.
Formoreinformationonparametersets,see"Application
DesignProcess"onpage37.
Yes
1
Thisis
listedas
optionalin
theWSDL,
butitis
required.
API Reference| 207
FIN11016 July 2014
simulatormode stns:simulator
modetype
Ifthevalueofthemodeparameterissimulated,thenthis
parametergovernstheresponsegivenbyIdentity
Verification.FormoreinformationonrunningIdentity
Verificationinsimulatedmode,see"TestingYour
Integration"onpage140
Validvalues:
Specifythesimulatormodevaluefortheresponseyou
wishtosimulate,orspecifyrandomtorandomlyselecta
simulatormodevalue.Foralistofvalidvalues,see
"SimulatorModeValues"onpage143.
No
0or1
attachmenttype stns:attachment
type
Typeofattachmentsentwiththerequest.
Validvalues:
xml
grammar
wav
No
0or1
specialfeature stns:special
featuretype
Specifiesaspecialfeaturecodeand/orspecialfeature
valueforacustomfeaturethatwasdevelopedforyour
companybyLexisNexis.ContactyourTechnicalSolutions
Consultantforthisvalue.
Validvalues:See"specialfeaturetype"onpage211.
No
0ormore
internationalization stns:
internationalizatio
ntype
Providesinformationaboutthelanguageinwhichthe
KBAquestionswillbeprovided.
Validvalues:See"internationalizationtype"onpage189.
No
0ormore
API Reference| 208
FIN11016 July 2014
referenceid stns:referenceid
type
Specifiesaninternaltrackingnumber,definedbythe
client,forthetransaction.Thisvalueisreturnedinboth
theaccountstransactionidparameterandreferenceid
parameterofthetransactionResponsemessage.Also,if
yougeneratereportsusingtheNetviewWebPortal,the
valueofthisparameterdisplaysintheReference#field.
Do not use this parameter to specify any

personal identifiable information or
sensitive data, such as credit card
numbers. While all Identity Verification
data is secure and tightly controlled, the
reference-id value is not encrypted and
therefore does not have the highest level
of security.
No
0ormore
Additionalsettingsparametersforidentityverificationsettingstype(usedinIdentityVerificationmessages)
task stns:tasktype Specifiesthetypeoftransaction.Formoreinformation
onthepossibletransactiontypes,see"Designing
VerificationWorkflows"onpage36
Validvalues:
icheck
iauth
iautoandiagearenolongersupported.
Yes
1
sequenceid xs:integer SpecifiesasequenceIDassignedbyLexisNexis.ThisIDis
usedbyLexisNexisfortestinganddiagnostics.
Validvalues:Awholenumber.
No
0or1
agent xs:string SpecifiesanameorotherIDfortheCallCenterAgent
sendingtherequest.
No
0or1
API Reference| 209
FIN11016 July 2014
ship-to-type
Thisdatatypeidentif iestheusertowhomtheordershouldbeshipped.
patriotact
compliance
xs:boolean Specifieswhetheryourcompanymustbeincompliance
withSection326ofthePatriotAct.
Validvalues:
trueor1
falseor0
No
0or1
parent
transactionid
stns:transaction
idtype
InternalfeatureusedbyIdentityVerificationtotrack
retries.Youdonotneedtoincludethisparameter.
Validvalues:
9223372036854775807
No
0or1
Additionalsettingsparametersforcontinuesettingstype(usedincontinuationmessages)
transactionid stns:transaction
idtype
SpecifiesthetransactionIDprovidedbyIdentity
VerificationinthetransactionResponsemessage.
Validvalues:
9223372036854775807
Yes
1
sameas stns:sameastype Specifiesthattheordershouldbeshippedtotheordered
bycontactpersonorthebilltocontactperson.
Validvalues:
orderedby
billto
Yes
Mutually
exclusive;
mustinclude
one
API Reference| 210
FIN11016 July 2014
shipping-type
Thisdatatypeidentif iesbillingandshippinginformation.
persontype stns:persontype Specifiesthepersontowhomtheordershouldbeshipped.
Yes
Mutually
exclusive;
mustinclude
one
billto stns:billtotype Personwhoshouldbebilledfortheorder.
Validvalues:See"billtotype"onpage180.
Yes
1
shipto stns:shiptotype Persontowhomtheordershouldbeshipped.
Validvalues:See"shiptotype"onpage209.
Yes
1
shipping
method
stns:shipping
method
Shippingmethod.
Validvalues:
ground
priorityovernight
nextdayair
instorepickup
seconddayair
priorityground
No
0or1
API Reference| 211
FIN11016 July 2014
simple-detail-type
Thisdatatypeallowsyoutosendtextualdata.Notethatanelementofthistypecanbeincludedwithin
acomplexdetailtype.
special-feature-type
Thisdatatypemaybeincludedinthesettingselementofarequestmessagetospecifyaspecialfeature
codeand/orspecialfeaturevalueforacustomfeaturethatwasdevelopedforyourcompanyby
LexisNexis.ContactyourTechnicalSolutionsConsultantforthesevalues.
WhenacustomfeatureisusedbyIdentityVerif icationtoprocessarequest,thisdatatypeisincluded
inthetransactionResponsemessage.
text xs:string Descriptiveinformation.
Yes
1
specialfeature
code
stns:special
featurecodetype
CodeprovidedbyLexisNexistoidentifyaspecialfeature.
Minimumcharacters: 3
No
0or1
specialfeature
value
stns:special
featurevaluetype
ValueprovidedbyLexisNexistoidentityaspecialfeature.
No
0or1
API Reference| 212
FIN11016 July 2014
text-type
ThisdatatypeisusedinatransactionResponsemessagewhenpresentingaquestionoranswer.
transaction-status-type
ThisdatatypeisusedinatransactionResponsemessage.
language stns:languagetype Languageinwhichthequestion/answerispresented.
Validvalues:
spanish
informalspanish
english
Yes
1
statement xs:string Question/answertext.
Yes
1
transactionid stns:transaction
idtype
UniqueIDassignedtothetransactionbyIdentity
Verification.
Validvalues:
9223372036854775807
For diagnostic purposes, you should store

the transaction-id with your transaction
data. For more information, see "Store the
Transaction ID Returned in a Transaction
Response" on page 138.
No
0or1
API Reference| 213
FIN11016 July 2014
transaction
requestid
stns:transaction
idtype
UniqueIDassignedtothetransactionrequestbyIdentity
Verification.
Validvalues:
9223372036854775807
No
0or1
accounts
transactionid
xs:string Trackingnumber,asdefinedbytheclientinthereference
idparameterinthesettingselementoftherequest
message.Ifreferenceidisnotincludedintherequest
message,thenthevalueofthisparameterisreturnedas
0.
No
0ormore
referenceid xs:string Trackingnumber,asdefinedbytheclientinthereference
idparameterinthesettingselementoftherequest
message.Ifreferenceidisnotincludedintherequest
message,thenthevalueofthisparameterisreturnedas
0.
The reference-id is returned in both this

parameter and the accounts-transaction-id
parameter to maintain backward-
compatibility with applications designed
with an earlier version of the Identity
Verification web service.
No
0ormore
API Reference| 214
FIN11016 July 2014
transaction-type
Thisdatatypeidentif iesthattheverif icationisneededforeitherapurchaseoranaccountverif ication.
Accountverif icationscanincludetransactionsthatinvolveapurchase.Typically,purchase
transactionsareforpurchasesmadebyuserswhodonothaveanaccountwiththeclientandaccount
transaction
result
stns:transaction
resulttype
Resultofthetransaction.
Validvalues:
questions:AsetofKBAquestionswhichareintendedto
bepresentedtotheuser,answered,andthensentback
toIdentityVerificationinacontinuationmessage.
passed:Theuserwassuccessfullyauthenticated.
failed:Theusercouldnotbesuccessfullyauthenticated
ortheuserdidnotfulfillalloftherequirementsdefined
forthetransaction(forexample,theusersagedidnot
exceedtheminimumthreshold).
error:IdentityVerificationencounteredacondition
thatpreventeditfromprocessingtheinformation
normally.Forexample,therequestdidnotincludea
requiredparameterortheuserisunder18yearsof
age.
Yes
1
riskassessment stns:risk
assessmenttype
IdentifiestheIdentityRiskScorecalculatedbyIdentity
Verificationforthetransaction.TheIdentityRiskScore
quantifiestheriskoffraudassociatedwithanidentity
duringaniAuthoriChecktransaction.Ariskscorecan
rangefrom0to1000,where1000indicatesthegreatest
levelofrisk.ForinformationoninterpretinganIdentity
RiskScore,seeNetviewHelp.
No
0or1
specialfeature stns:special
featuretype
Specifiesaspecialfeaturecodeand/orspecialfeature
valueforacustomfeaturethatwasdevelopedforyour
companybyLexisNexis.ContactyourTechnicalSolutions
Consultantforthisvalue.
Validvalues:See"specialfeaturetype"onpage211.
No
0ormore
API Reference| 215
FIN11016 July 2014
verif icationtransactionsarefortransactions,includingpurchases,madebyuserswhohaveanaccount
withtheclient.
uk-address-type
ThisdatatypeprovidesaddressdetailsforauserintheUnitedKingdom.ForusersintheUnitedStates,
seeaddresstype.
purchase stns:purchasetype Providesdetailsaboutapurchase.
Validvalues:See"purchasetype"onpage200.
Yes
Mutually
exclusive;
must
includeone
account
verification
stns:account
verificationtype
Providesdetailsaboutatransactiontiedtotheusers
account.
Validvalues:See"accountverificationtype"onpage175.
housename xs:string Housename.Usethisparametertoprovideahousename
and/orflatnumber(forexample:OakHouseFlat1).
Valid values:Astringofcharacters.Formoreinformation,
No
0or1
housenumber xs:string Housenumber.Insteadofusingthisparametertosend
housenumber,youcanincludeitinthestreet1parameter.
Maximumcharacters:Thisparameterplusstreet1should
notexceed32characters.
No
0or1
API Reference| 216
FIN11016 July 2014
street1 xs:string Firstoronlylineofstreetaddress.Youcanenterhouse
numberseparatelyinthehousenumberparameter,oryou
canincludeitinthisparameter(forexample:10Strawberry
Lane).
Maximumcharacters:Thisparameterplushousenumber
shouldnotexceed32characters.
Yes
1
street2 xs:string Secondlineofstreetaddress,ifapplicable.
No
0or1
district xs:string Districtname.
No
0or1
town xs:string Townname.
No
0or1
county xs:string Countyname.
No
0or1
postcode xs:string Validpostalcodeoftheaddress.
Yes
1
context stns:address
contexttype
Functionoftheaddressfortheuser.Currently,onlythe
primaryaddressisvalid.
Validvalue:primary
Yes
1
API Reference| 217
FIN11016 July 2014
yearsat xs:decimal Yearsofresidenceattheaddress.
Validvalues:Adecimalvalue.Forexample:1.3,0.2.
No
0 or 1
API Reference| 218
FIN11016 July 2014
venue-type
Thisdatatypedescribesthetypeofenvironmentwherethetransactionistakingplace.
online stns:onlinetype SpecifiesthatIdentityVerificationisbeingcalledaspartof
anonlinesolution.
Validvalues:See"onlinetype"onpage190.
Yes
Mutually
exclusive;
must
includeone
callcenter stns:callcenter
type
SpecifiesthatIdentityVerificationisbeingcalledaspartof
acallcentersolution.
Validvalues:See"callcentertype"onpage181.
batch stns:batchtype SpecifiesthatIdentityVerificationisbeingcalledaspartof
abatchsubmission.
ThisparameterisusedbytheNetviewWebPortal;youwill
notneeditinyourclientapplication.
netview stns:netviewtype SpecifiesthatIdentityVerificationisbeingcalledbythe
NetviewWebPortal.
ThisparameterisusedbytheNetviewWebPortal;youwill
notneeditinyourclientapplication.
pointofsale stns:pointofsale
type
apointofsalesolution.
Validvalues: See"pointofsaletype"onpage197.
customer
service
stns:customer
servicetype
acustomerservicesolution.
Validvalues: See"customerservicetype"onpage186.
ivr stns:ivrtype SpecifiesthatIdentityVerificationisbeingcalledaspartof
anIntegratedVoiceResponsesolution.
Validvalues: See"ivrtype"onpage190.
Error, Failure, and Information Codes | 219
FIN11016 July 2014
Appendi x A
Error, Fai l ure, and
I nf ormat i on Codes
I n Thi s Chapt er
Error,Failure,and
Information
CodesOverview,
page220
FailureCodes,
page222
Information
Codes,page228
FIN11016 July 2014
Error, Failure, and Information Codes Overview
Thisappendixdescribestheerror,failure,andinformationcodesthatIdentityVerif icationreturnsin
theinformationtypeelementofatransactionResponsemessage.Inthecodetablespresentedinthis
appendix,theCodecolumnliststhetextstringreturnedinthedetailcodeparameter,andthef irstline
oftheDescriptioncolumnliststhetextstringreturnedinthedetaildescriptionparameter.
Underthecodeisalistoftheverif icationtypes(iCheckoriAuth)forwhichthecodemaybereturned.
Formoreinformationontheinformationtypeelement,see"informationtype"onpage188.
Error Codes
Thefollowingcodesdescribeerrorsthatpreventarequestfrombeingprocessed.
Code Description
communications_error
(Allverificationtypes)
Error:NetworkCommunications
TherewasanetworkcommunicationserrorwithintheIdentityVerification
system.
internal_application_error
Error:Internal
TherewasaninternalIdentityVerificationerrorwithintheIdentityVerification
system.
invalid_information
(iAuth)
Error:InvalidInformation
Thesubmittedcontinuationrequestdidnotcontaincompletequestionanswer
details(forexample,therequestcontainedanswerstoonly2ofthe3
questions).
invalid_login
Error:InvalidLogin
IdentityVerificationreceivedinvalidlogininformation.
FIN11016 July 2014
invalid_mode
Error:InvalidMode
Aninvalidmodewasprovidedinthesettingstypeparameteroftherequest.See
"mode"onpage206.
invalid_parameterlist
Error:InvalidRuleSet
Thespecifiedparameterset(ruleset)doesnotexist.
invalid_simulator_mode
Error:InvalidSimulatorMode
Thespecifiedsimulatormodevalueisnotvalid.See"SimulatorModeValues"on
page143
invalid_transaction_continue
(iAuth)
Error:InvalidTransactionContinue
Therewasanerrorassociatedwithacontinuationrequest.Caninclude,butis
notlimitedtoinvalidmessagestructure,missinginformation,oratransaction
thathasalreadybeenclosed.
invalid_transaction_initiate
Error:InvalidTransactionInitiate
Therewasanerrorwithintheinitialtransactionrequest.Caninclude,butisnot
limitedtoinvalidcharactersincludedintherequestormissingdataelements.
no_test_tokens
Error:NoTestTokensRemaining
Theallocatednumberoftesttransactionsassociatedwiththeaccounthasbeen
exceeded.
transaction_expired
Error:TransactionExpired
Thetimeallocatedtoansweringquestionsexpired.
unknown_database_response
Error:UnknownDatabaseResponse
IdentityVerificationreceivedanunknownresponsefromthedatabase.
xml_data_integrity
Error:XMLDataIntegrity
ThestructureoftheXMLmessagereceivedisinvalidorbecamecorruptin
transit.
Code Description
FIN11016 July 2014
Failure Codes
Thefollowingcodesdescribewhyaverif icationfailed.
Code Description
blocked
(iCheck,iAuth)
Blocked:PriortoiLocate
Thetransactionwasblockedbecauseitwasasubsequentattemptto
authenticateauser,withoutmodifyingdataelementsthataddressthe
reasonforapreviousfailure/denial.Forexample,ifthesystemreturned
anIndividualnotLocatedmessagewithapreviousrequestwithina
configuredlookbackperiod,andyouthenattemptedtoauthenticatethe
sameuserwithoutchanginganyoftheprovideddata,Identity
Verificationissuethismessageandblockthetransaction.
denial
(iCheck,iAuth)
Denial:AfteriLocate
Thetransactionwasdenied.Currently,thisgeneraldenialcodeisonly
associatedwiththeIdentityVerificationidentityexceptionlistfeature.
denial_address_violation_dpv
(iCheck,iAuth)
Denial:InvalidPostalDeliveryPoint
Theaddressprovidedisnotavaliddeliverypoint.
denial_address_violation_pobox
(iCheck,iAuth)
Denial:POBox
TheaddressprovidedisaPObox.
denial_address_violation_general
(iCheck,iAuth)
Denial:GeneralDeliveryAddress
Theaddressprovidedisageneraldeliveryaddress.
denial_address_warning
(iCheck,iAuth)
Denial:CriticalAddressWarningEncountered
Anaddressassociatedwiththeusermeetstheclient'sdefinitionofahigh
riskaddress.
denial_age_verification_mismatch
(iCheck,iAuth)
Denial:AgeMismatch
Thedateofbirthprovideddoesnotmatchthediscovereddateofbirth
FIN11016 July 2014
denial_age_verification_not_provided
(iCheck,iAuth)
Denial:AgeNotProvided
Thebirthdateisrequiredandwasnotprovidedintherequest.
denial_age_verification_threshold
(iCheck,iAuth)
Denial:AgeThresholdNotMet
Theuserdoesnotmeettheagerequirements.
denial_age_verification_undetermined
(iCheck,iAuth)
Denial:AgeUndetermined
Thebirthdateoftheusercouldnotbedeterminedfromthediscovered
records.
denial_aml_check_not_pass
(iCheck,iAuth)
Denial:UKKBAAMLcheck
TheuserdidnotpassanAntiMoneyLaundering(AML)check.
(AssociatedwithUKverificationsonly.)
denial_cifas_existing
(iCheck,iAuth)
Denial:IndividualfoundonCIFASlist
TheusersnameislinkedtoafraudincidentontheCIFASNationalFraud
Database.
denial_credit_fraud_victim
(iCheck,iAuth)
Denial:creditfraudcheck
TheuserhasaFraudFlagAlertonhis/hercreditfile,indicatingidentity
theftactivity.
denial_cumulative_transaction_activity
_amount
(iCheck,iAuth)
Denial:CumulativeAmount
Theuserhasexceededtheallowedcumulativedollarlimitfor
transactionsfortheconfiguredperiodoftime.
denial_cumulative_transaction_activity
_frequency
(iCheck,iAuth)
Denial:CumulativeFrequency
Theuserhasexceededtheallowedtransactionattemptlimitforthe
denial_currentaddress_notcurrent
(iCheck,iAuth)
Denial:AddressNotCurrent
Thepostaladdressprovideddoesnotappeartobecurrent.
Code Description
FIN11016 July 2014
denial_currentaddress_notfound
(iCheck,iAuth)
Denial:AddressNotFound
Theaddressprovidedcouldnotbefound.
denial_currentaddress_notmostrecent
(iCheck,iAuth)
Denial:AddressCurrentButNotMostRecent
Thepostaladdressprovideddoesnotappeartobethemostrecent.
denial_driverslicense_match_failure
(iCheck,iAuth)
Denial:FailedDriversLicenseMatch
Thedriverslicenseprovideddoesnotsufficientlymatchthediscovered
information.
denial_driverslicense_not_provided_fai
lure
(iCheck,iAuth)
Denial:DriversLicenseNotProvided
Driverslicenseinformationwasnotsubmittedanditismandatorybased
onsettingsintheparameterset.
denial_driverslicense_undiscovered_fai
lure
(iCheck,iAuth)
Denial:DriversLicenseUndiscovered
Adriverslicenserecordcouldnotbefoundthatmatchesthesubmitted
information.
denial_group_iauth_failure_frequency
(iAuth)
Denial:GroupiAuthFailureFrequency
TheuserhasexceededthelimitofpreviouslyfailediAuthtransactions
withintheconfiguredperiodoftimeacrossadefinedgroupofaccounts.
denial_group_transaction_frequency
(iCheck,iAuth)
Denial:GroupFrequency
Theuserhasexceededtheallowedtransactionattemptlimitacrossa
definedgroupofaccountsfortheconfiguredperiodoftime.
denial_iauth_failed_too_recently
(iAuth)
Denial:FailediAuthtooRecently
TheuserhaspreviouslyfailedaniAuthwithintheconfiguredperiodof
time.
Code Description
FIN11016 July 2014
denial_identity_event
(iCheck,iAuth)
Denial:IdentityEvent
Anidentityeventwasdiscoveredfortheuser.Anidentityeventindicates
thatarecordabouttheuserwasfoundindatacollectedfromANI/caller
IDspoofingservices,IPaddresslookupservices,andpublicrecordsearch
companies.Forexample,anidentityeventcanindicatethatsomeone
recentlypurchasedapublicrecordsearchabouttheuser,orthatthe
usersphonenumberwasthedestinationphonenumberofaspoofed
call.
denial_individual_reported_dead
(iCheck,iAuth)
Denial:ReportedDeceased
Thepersonisreportedtobedeceased.
denial_ip_flagging
(iCheck,iAuth)
Denial:IPBlocked
TheoriginatingIPaddressviolatedoneormoreoftheconfiguredrules
fortheaccount.Forexample,theIPAddressexhibitsanonymizing
behavior.
denial_ofac_existing
(iCheck,iAuth)
Denial:IndividualfoundonOFAClist
TheusersnameappearsonanSDNlistpublishedbyOFAC.
denial_phonenumber_not_match
(iCheck,iAuth)
Denial:PhoneNumberVerification
Thesubmittedphonenumberdoesnotmatchanyofthephonenumbers
discoveredfortheuser.
denial_phonenumber_not_provided
(iCheck,iAuth)
Denial:PhoneNumberNotProvided
Thephonenumberwasnotsubmittedanditismandatorybasedon
denial_risk
(iCheck,iAuth)
Denial:Risk
Thesystemcanevaluateseveralfactorsdiscoveredatruntimeanddistill
themintoasingleIdentityRiskScore.Theriskscoreforthistransaction
exceedstheriskthresholddefinedintheparameterset,thereforethe
verificationfailed.
Code Description
FIN11016 July 2014
denial_ssn_dob_mismatch
(iCheck,iAuth)
Denial:SSNDOBMismatch
Thedateofbirthprovidedisaftertheissuancedateofthediscovered
SSNoftheuser.
denial_ssn_match_violation
(iCheck,iAuth)
Denial:SSNMismatch
TheSSNprovideddoesnotmatchthediscoveredSSNwithinthe
configuredthreshold.
denial_ssn_not_provided
(iCheck,iAuth)
Denial:SSNNotProvided
TheSSNwasnotsubmittedanditismandatorybasedonsettingsinthe
parameterset.
failed_iauth_questions
(iAuth)
Failed:iAuthQuestions
TheuserfailedtopasstheiAuthquestions.
failed_icheck
(iCheck)
Failed:iCheck
Theusercouldnotbesufficientlyverifiedbasedontheinformation
provided.
Recommendation:
Confirmpersonalinformationiscorrectandresubmitifanycorrections
aremade.Ifnocorrectionsareneeded,obtainmorepersonal
information(forexample:SSN9anddateofbirth)orapreviousaddress.
individual_not_found
(iCheck,iAuth)
Failed:IndividualNotLocated
Basedontheinformationprovided,theusercouldnotbelocated.
Recommendation:
Confirmpersonalinformationiscorrectandresubmitifanycorrections
aremade.Ifnocorrectionsareneeded,obtainmorepersonal
information(forexample:SSN9anddateofbirth)orapreviousaddress.
insufficient_info_for_questions
(iAuth)
Failed:InsufficientInfoforQuestions
Theuserhasbeenlocated,butthereisinsufficientdatatopresentthe
configuredminimumnumberofquestions.
Code Description
FIN11016 July 2014
ipcountry_denial
(iCheck,iAuth)
Denial:IPCountry
ThiscodeisreturnedwhenworkinginSimulatedmodeonly.
TheusersIPaddressviolatedoneormoreoftheconfiguredrulesforthe
account.ExamplesincludeIPAddressesthatexhibitanonymizing
behaviororareassociatedwithacountryontheclient'scountrydenial
list.
multiple_individuals_found
(iCheck,iAuth)
Failed:MultipleIndividualsLocated
Multipleindividualswerefoundbasedontheinformationsubmittedand
itwasnotpossibletouniquelyidentifytheuserandpresentadefinitive
setofquestions.
Recommendation:
Resubmitafterobtainingmorepersonalinformation(forexample:SSN9
anddateofbirth)orapreviousaddress.
pend_instant_id_thresholds_not_met
(iCheck,iAuth)
Pend:InstantIDverificationfailed
TheverificationisdeniedbecausethescorereturnedbytheInstantID
servicedidnotmeetthethreshold.
ThiscodeisreturnedwhenworkingwiththeVerificationandFraud
PreventionServicesintegrationfeature.
Foranexampleofaresponsemessage,see"iCheckVerification:User
Passes"onpage84.
Code Description
FIN11016 July 2014
Information Codes
Thefollowingcodesprovideinformationaboutthestatusofarequest.
Code Description
address.warnings
(iCheck,iAuth)
Addresswarningsencounteredbythetransaction
Anaddressassociatedwiththeusermatchedtheclient'sdefinitionofa
highriskaddress.
age.match.quality
(iCheck,iAuth)
Agematchqualityinformation:
Thedateofbirthprovideddoesnotmatchthediscovereddateofbirth
age.notavailable
(iCheck,iAuth)
Ageinformationabouttheindividualisnotavailable
Adateofbirthcouldnotbedeterminedfortheuserbasedonthe
discoveredrecords.
age.under.threshold
(iCheck,iAuth)
Individualdoesnotappeartobeovertheconfiguredthresholdforthe
transaction
Thediscoveredageoftheuserdoesnotexceedtheconfiguredthreshold.
callcenterassist
(iCheck,iAuth)
CallCenterAssistdetails
Theuserwasnotlocatedbasedonthesubmittedinformation.TheCall
CenterAssistfeaturesuggestswhichpersonalinformationshouldbe
checkedforerrorsoraddedtotherequest.
FIN11016 July 2014
cifas
(iCheck,iAuth)
CIFAScheckstatus
IftheusersnameisnotlinkedtoafraudincidentontheCIFASNational
FraudDatabase,theinformationcodereads:Theindividualwasnot
foundontheCIFASlist.
IftheusersnameislinkedtoafraudincidentontheCIFASNationalFraud
Database,oneofthefollowinginformationcodesisdisplayed:
Iftheaccountisconfiguredtoissueawarning,theinformationcode
reads:
Warning:Thesubmittedpersonalinformationmatchestheidentityof
anindividualontheCIFASlist.
Iftheaccountisconfiguredtodenythetransaction,theinformation
codereads:
Denial:Thesubmittedpersonalinformationmatchestheidentityofan
individualontheCIFASlist.
dcheck.address.dpv
(iCheck,iAuth)
Detailsabouttheenteredaddress'sDPVstatus
Theaddressprovidedisnotavaliddeliverypoint.
dcheck.address.general
(iCheck,iAuth)
Detailsabouttheenteredaddress'sGeneraldeliverystatus
Theaddressprovidedisageneraldeliveryaddress.
dcheck.address.pobox
(iCheck,iAuth)
Detailsabouttheenteredaddress'sPOBoxstatus
TheaddressprovidedisaPObox.
dcheck.aml.check.not.pass
(iCheck,iAuth)
DetailsaboutUKKBAAMLcheck
TheuserdidnotpassanAntiMoneyLaundering(AML)check.
dcheck.credit.fraud.not.pass
(iCheck,iAuth)
Warning:Theindividualisavictimofcreditfraud
TheuserhasaFraudFlagAlertonhis/hercreditfile,indicatingidentity
theftactivity.
dcheck.currentaddress.not.current
(iCheck,iAuth)
Detailsaboutcurrentaddressverification
Thepostaladdressprovideddoesnotappeartobecurrent.
Code Description
FIN11016 July 2014
dcheck.currentaddress.not.found
(iCheck,iAuth)
Thepostaladdressprovidedcouldnotbefound.
dcheck.currentaddress.not.mostrecent
(iCheck,iAuth)
Thepostaladdressprovideddoesnotappeartobethemostrecent.
dcheck.identity.event
(iCheck,iAuth)
DataCheckIdentityEvent
Anidentityeventwasdiscoveredfortheuser.Anidentityeventindicates
thatarecordabouttheuserwasfoundindatacollectedfromANI/caller
IDspoofingservices,IPaddresslookupservices,andpublicrecordsearch
companies.Forexample,anidentityeventcanindicatethatsomeone
recentlypurchasedapublicrecordsearchabouttheuser,orthatthe
usersphonenumberwasthedestinationphonenumberofaspoofed
call.
dcheck.phonenumber.not.match
(iCheck,iAuth)
Detailsaboutphonenumberverification
Thephonenumberprovideddoesnotmatchanyofthephonenumbers
discoveredfortheuser.
dcheck.phonenumber.not.provided
(iCheck,iAuth)
Detailsaboutphonenumberverification
Aphonenumberwasnotsubmittedanditismandatorybasedon
dcheck.ssn.dob.mismatch
(iCheck,iAuth)
DetailsabouttheSSNDOBmismatchresult
Thedateofbirthprovidedisaftertheissuancedateofthediscovered
SSNoftheuser.
dcheck.ssn.match
(iCheck,iAuth)
DetailsabouttheSSNmatchresult
TheSSNprovideddoesnotmatchthediscoveredSSNwithinthe
configuredthreshold.
driverslicense.warnings
(iCheck,iAuth)
Driver'sLicensewarningsencounteredbythetransaction
Thedriverslicenseprovideddoesnotsufficientlymatchthediscovered
information.
Code Description
FIN11016 July 2014
iauth.question.details
(iAuth)
iAuthquestiondetails
Thiscodecontainsdetailsonthequestionsthatwerepresented,suchas
thetypeofquestionandtheoutcome.
icheckescalation
(iCheck)
EscalationtoiAuthreason:
ThetransactionwasescalatedtoaniAuthverification.
iid.warning
(iCheck,iAuth)
DetailsabouttheInstantIDverificationresponsewarning
TheInstantIDserviceverifiedtheconsumer,andthetransactionreturned
awarningmessageorresultedinescalationtoiAuth.
ThiscodeisreturnedwhenworkingwiththeVerificationandFraud
PreventionServicesfeatures.Foranexampleofaresponsefrom
InstantID,see"iCheckVerification:UserPasses"onpage84.
(AssociatedwithUSverificationsonly.)
ilocate.match.summary
(iCheck,iAuth)
DetailsoftheiLocatematchsummaryprocess
Thiscodepresentsasummaryofthequalityofthematchasdetermined
bytheiLocateMatchSummaryfeature.Formoreinformationonthe
iLocateMatchSummaryfeature,see"iLocateMatchSummary"onpage
124.
ipatriot
(iCheck,iAuth)
Patriotcompliancestatus:
IftheusersnamedidnotmatchanentryontheSDNlistpublishedby
OFAC,theinformationcodereads:Theindividualwasnotfoundonthe
OFAClist.
IftheusersnamedidmatchanentryontheSDNlistpublishedbyOFAC,
theinformationcodereads:Theinformationprovidedisconsistentwith
anindividualfoundduringaPatriotActsearch.
ip_country_origin
(iCheck,iAuth)
IPaddresscountryoforigin:
ThiscodedisplaysthecountryoforiginfortheoriginatingIPaddress.
ip.flagging.warning
(iCheck,iAuth)
Warning:IPaddressofpersonhasbeenflaggedasatrisk
TheoriginatingIPaddressviolatedoneormoreoftheconfiguredrules
fortheclientaccount.Forexample,theIPAddressexhibitsanonymizing
behavior.
Code Description
FIN11016 July 2014
passed
VerificationSuccessful
Theuserhaspassedtheauthenticationprocess.
special.feature.request
SpecialFeature
Specialrequestsorfeaturesthatarenotgenerallyavailablemayreturn
thiscode.
special.feature.transaction
SpecialFeature
Specialrequestsorfeaturesthatarenotgenerallyavailablemayreturn
thiscode.
vcheck.amount
(iCheck,iAuth)
Totalamountfailurereason:
Theuserhasexceededtheallowedcumulativedollarlimitfor
transactionsfortheconfiguredperiodoftime.
vcheck.frequency
(iCheck,iAuth)
Frequencyviolationinformation:
vcheck.global.frequency
(iCheck,iAuth)
GlobalFrequencyTestViolationDetails
configuredperiodoftimeacrosstheIdentityVerificationclientbase.
vcheck.group.frequency
(iCheck,iAuth)
Warning:Groupfrequencytestwasexceeded
Theuserhasexceededtheallowedtransactionattemptlimitwithina
definedgroupofaccountsfortheconfiguredperiodoftime.
vcheck.group.iauthfailure
(iAuth)
Warning:GroupiAuthfailuretestwasexceeded
withintheconfiguredperiodoftimeacrossadefinedgroupofaccounts.
vcheck.iauthfailure
(iAuth)
PreviousiAuthfailurereason:
withintheconfiguredperiodoftime.
Code Description
Question Text | 233
FIN11016 July 2014
Appendi x B
Quest i on Text
I n Thi s Chapt er
QuestionText
Overview,page
234
US
Implementations,
page235
UK
Implementations,
page240
Question Text | 234
FIN11016 July 2014
Question Text Overview
Thisappendixlistsallthequestiontypesthatmaybepresentedtoauserduringauthenticationand
identif iesthecorrespondingquestiontext.Settingsinyouraccountparametersetdeterminewhich
questiontypescanbeused.
ThisappendixpresentsaseparatetableforUSandUKimplementations.Inthetables,theQuestion
Typecolumnidentif iesthequestiontypeasitislistedinaQuestionListorQuestionSummaryreport
thatyoucanruninNetview.Thefollowingf igureshowsanexampleofaQuestionListreport
generatedforaUSimplementation.
TheTextcolumnliststhequestiontextasitispresentedinthetextparameterofthequestiontype
datatypeinaTransactionResponsemessage.Forexample,thefollowinglinesfroma
TransactionResponseincludethetextforthecounty.lived.singlequestiontypepresentedwithaUS
implementation.
<questions>
<question>
For most question types, there is a
real and a fake version as denoted
by the suffix. Fake questions are not
based on facts and help to catch a user
guessing.
Question Text | 235
FIN11016 July 2014
<text>
<statement>Inwhichofthefollowingcountieshaveyou
everlivedorownedproperty?</statement>
</text>
US Implementations
ThefollowingtableliststhetextpresentedforeachquestiontypeavailablewithUSimplementations.
Thequestiontypesarelistedinalphabeticalorder.
Question Type Text
apollo.aircraft.association Whichofthefollowingaircrafthaveyouowned?
apollo.known.neighbors Whichofthefollowingpeoplehaveyouknown?
apollo.people.association Whichofthefollowingpeoplehaveyouknown?
apollo.ssn.state.issuance Inwhichofthefollowingstatesdidyoulivewhenyour
socialsecuritynumberwasissued?
apollo.watercraft.association Whichofthefollowingboatsorwatercraftshaveyou
owned?
apollo.year.livedin.city Duringwhichofthefollowingyearsdidyoulivein
%city%?
bank.account.atm.street.location
bank.account.atm.street.location is a
customized question type generated
using internal client data. To enable this
question type, contact your Technical
Solutions Consultant.
WhichofthefollowingATMlocationsdidyouuse
recently?
Question Text | 236
FIN11016 July 2014
bank.account.atm.withdrawal.amount
bank.account.atm.withdrawal.amount is
a customized question type generated
HowmuchwastheATMwithdrawalamounton
%day_of_week%%month%%day%%number_suffix%?
(Forexample,thewithdrawaldatecouldbeThursday
November1st.)
bank.account.cosigner.monthofbirth
bank.account.cosigner.monthofbirth is a
Inwhichofthefollowingmonthswasthecosignerof
youraccountborn?
bank.account.opening.city
bank.account.opening.city is a
Inwhichcityisthebranchwhereyouopenedyour
account?
bank.account.opening.year
bank.account.opening.year is a
Whichofthefollowingyearsisclosesttotheopening
dateofyouraccount?
college.association Whichofthefollowingcollegeshaveyouattended?
college.athletic.team Whichteamnicknameisassociatedwithacollegeyou
attended?
college.city Inwhichofthefollowingcitieshaveyouattended
college?
Question Type Text
Question Text | 237
FIN11016 July 2014
college.major Whichofthefollowingcollegemajorshaveyou
pursued?
corporate.association Whichofthefollowingcorporationshaveyouever
beenassociatedwith?
county.lived.single Inwhichofthefollowingcountieshaveyoueverlived
orownedproperty?
domainname.association Whichofthefollowingdomainnameshaveeverbeen
registeredinyourname?
driver.license.number Whichofthefollowingnumbersmatchyourcurrent
driverslicense?
email.association Whichofthefollowingemailshaveyoueverbeen
associatedwith?
individual.cityofbirth Inwhichcitywereyouborn?
individual.eyecolor Accordingtoyourdriver'slicense,whatcolorareyour
eyes?
individual.haircolor Accordingtoyourdriver'slicense,whatcolorisyour
hair?
individual.height Accordingtoyourdriver'slicense,approximatelyhow
tallareyou?
Individual.monthofbirth Whatmonthwereyoubornin?
individual.professional.license WhichofthefollowingProfessionalLicenseshaveyou
everheld?
individual.shoesize Whatsizeshoedoyoucommonlywear?
individual.zodiac Whatisyourzodiacsign?
Question Type Text
Question Text | 238
FIN11016 July 2014
livedat.current.address.how.long Howlonghaveyoulivedatyourcurrentresidencein
%city%?
livedat.subdivision Inwhichofthefollowinghousingcomplexesor
communitieshaveyoueverlivedorownedproperty?
nearby.hospital Whichofthefollowinghospitalsisnearbyyourcurrent
address?
nearby.school Whichofthefollowingschoolsisnearbyyourcurrent
address?
person.age Whichofthefollowingagerangesmostcloselymatch
theageof'%name%'?
person.city Inwhichofthefollowingcitiesdoes'%name%'
currentlyliveorownproperty?
person.known.single Whichofthefollowingpeoplehaveyouknown?
person.monthofbirth Whatmonthwas'%name%'bornin?
person.state Inwhichofthefollowingstatesdoes'%name%'
currentlyliveorownproperty?
petname.first Whatwasthenameofyourfirstpet?
phonenumber.old Whichofthefollowingphonenumbershaveyouever
beenassociatedwith?
property.association.single Whichofthefollowingaddresseshaveyoueverbeen
associatedwith?
property.city Basedonyourbackground,inwhatcityis'%street%'?
property.county Basedonyourbackground,inwhatcountyis
'%street%'?
Question Type Text
Question Text | 239
FIN11016 July 2014
property.fullbaths Howmanyfullbathroomsdidthepropertyat
'%street%'haveatthetimeofsaleorfinancingin
'%year%'?
property.purchasedfrom Fromwhomdidyoupurchasethepropertyat
'%street%'?
property.purchasedwhen Whendidyoupurchasethepropertyat'%street%'?
property.squarefeet Howmanysquarefeetdidthepropertyat'%street%'
haveatthetimeofsaleorfinancingin'%year%'?
property.street.in.city Whichofthefollowingstreetaddressesin'%city%'
haveyoueverlivedatorbeenassociatedwith?
ssn.first.two.digits Pleaseselectfromthefollowinglistthetwonumbers
thatmatchthefirsttwonumbersofyoursocialsecurity
number.
ssn.middle.two.digits Pleaseselectfromthefollowinglistthetwonumbers
thatmatchthetwonumbersinthemiddleofyour
socialsecuritynumber.
ssn.sum.first.two.digits Addingthefirsttwonumbersofyoursocialsecurity
numbertogetherequalswhichofthefollowing?
vehicle.association Whichofthefollowingvehicleshaveyourecently
owned,leasedorcosigned?
vehicle.color Whatcolorisyour'%year%%vehicle%'?
vehicle.historical.association Whichofthefollowingvehicleshaveyoueverowned
orleased?
Question Type Text
Question Text | 240
FIN11016 July 2014
UK Implementations
ThefollowingtableliststhetextpresentedforeachquestiontypeavailablewithUKimplementations.
Thequestiontypesarelistedinalphabeticalorder.
The question types followed by an asterisk (*) are passed directly from the data provider and may
vary slightly depending on the data.
vehicle.historical.color Whatcolorwasthe'%year%%vehicle%'thatyouhave
owned?
vehicle.plate.number Whatis,orwas,thelicenseplatenumberforyour
'%year%%vehicle%'?
vehicle.plate.style Whatkindof'%state%'licenseplateisorwasrecently
onyour'%year%%vehicle%'?
Question Type Text
ukkba.account.sortcode
ukkba.account.sortcode is a customized
question type based on the sort code. It
can only be used by integrated
customers using API version 6 as the
data must be passed directly to
LexisNexis.
Whatisthesortcodeonthefrontofthedebitcardyou
areusing?
ukkba.county.lived Inwhichofthefollowingcountieshaveyoueverlived
orownedproperty?
ukkba.credit.card.first.receive.date Whendidyoufirstreceivethecard?
Question Type Text
Question Text | 241
FIN11016 July 2014
ukkba.credit.card.last.statement.balance Whatwasyourbalanceatthetimeofyourlast
statement?
ukkba.credit.card.last.statement.credit.limit Whatwasyourcreditlimitatthetimeofyourlast
statement?
ukkba.credit.card.provider Whichofthefollowingcompaniesprovidesacredit
cardorstoreaccountcardtoyou?
ukkba.current.account.provider Whoisyouraccountprovider?
ukkba.district.lived Inwhichofthefollowingdistrictsorlocationshaveyou
everlived?
ukkba.finance.provider Whogaveyouthefinance?
ukkba.finance.regular.payment.amount Whatisyourregularpaymentamount?
ukkba.finance.when Whendidyoutakeoutthefinance?
ukkba.individual.phonenumber Whichofthefollowingphonenumbershaveyouever
beenassociatedwith?
ukkba.joint.current.account.joint.holder Whatisthefirstinitialandsurnameofthepersonyou
sharethisaccountwith?
ukkba.joint.current.account.provider Whoistheaccountprovider?
ukkba.knowsof.person.age Whichofthefollowingagerangesmostcloselymatch
theageof'%name%'?
ukkba.knowsof.person.byfullname Whichofthefollowingpeoplehaveyouknown?
ukkba.knowsof.person.byname Whichofthefollowing%surname%shaveyoushared
anaddresswith?
Question Type Text
Question Text | 242
FIN11016 July 2014
ukkba.knowsof.person.monthofbirth Whatmonthwas'%name%'bornin?
ukkba.land.registry.property.value Whatwastheoriginalpurchasepriceofthisproperty?
ukkba.land.registry.purchase.date Approximatelywhendidyoupurchasethisproperty?
ukkba.linked.address.previous.address Wheredidyouliveimmediatelypriortoyourcurrent
suppliedaddress?
ukkba.livedat.address Whichofthefollowingaddresseshaveyoueverbeen
associatedwith?
ukkba.livedat.current.address.how.long Howlonghaveyoulivedatyourcurrentresidencein
%city%?
ukkba.loan.length* Howlongwastheloanfor?
ukkba.loan.provider* Whogaveyoutheloan?
ukkba.mail.order.provider Whichoneofthefollowingcataloguesdoyouhave?
ukkba.mobile.phone.service.provider* Whichofthefollowingcompaniesprovidesyour
mobilephoneorcableservice?
ukkba.mobile.phone.service.start.date* Whendidyoustartusingthisservice?
ukkba.mortgage.amount* Howmuchwasthemortgagefor?
ukkba.mortgage.first.regular.payment.time* Whendidyoumakethefirstregularpaymentonyour
mortgage?
ukkba.mortgage.initial.term.length* Howlongwastheinitialterm?
ukkba.mortgage.provider* Whichofthefollowingcompaniesisyourmortgage
provider?
Question Type Text
Question Text | 243
FIN11016 July 2014
ukkba.nearby.hospital Whichofthefollowinghospitalsisnearbyyourcurrent
address?
ukkba.nearby.school Whichofthefollowingschoolsisnearbyyourcurrent
address?
ukkba.prior.resident Whichofthefollowingpeoplelivedat'%street%'prior
toyou?
ukkba.rental.provider Whodoyourentyourequipmentfrom?
ukkba.second.current.account.provider Whoisyouraccountprovider?
ukkba.year.lived.in.city Duringwhichofthefollowingyearsdidyoulivein
%city%?
ukkba.zodiac.sign Whatisyourzodiacsign?
Question Type Text
Sample Request and Response Messages | 244
FIN11016 July 2014
Appendi x C
Sampl e Request and
Response Messages
I n Thi s Chapt er
SampleRequest
andResponse
Messages
Overview,page
245
Workingwiththe
SampleMessages,
page245
FIN11016 July 2014
Sample Request and Response Messages Overview
ThisappendixdescribesthesampleSOAPrequestandresponsemessagesprovidedwiththisguide.
Thesamplemessagescorrespondto16examplesthatillustratedifferentiCheck,andiAuthtransaction
scenarios.
Forannotatedexamplesthatwalkyouthroughthemaincontentofseveralsamplemessages,see
"SOAPMessageExamples"onpage49.
Working with the Sample Messages
Thisbookisaccompaniedbyazipf ilecalledIdVToolkit.zipthatcontainsacollectionofsampleSOAP
messages(XMLf iles).
IfyoudonothavetheIdentityVerif icationtoolkit,contactyourdesignatedTechnicalSolutions
Consultant.
WhenyouunziptheIdVToolkit.zipf ile,youwillhaveanIdVSampleMessagesfolderthatcontainsa
subfolderforeachofthe16examples.
EachsubfoldercontainsacollectionofXMLf iles.Thef ilesarelogicallynamedtoindicatewhether
theyarearequest,continuation,orresponsemessage.Someexamplesincludemultipleresponsesand
continuationmessages.Forexample,Example11providesthemessagesforaniAuthverif icationthat
presentedquestionssequentiallyratherthaninaset.Therefore,thereisaresponsemessage(the
FIN11016 July 2014
question)andcontinuationmessage(theanswer)foreachofthequestions,plusanotherresponse
messageforthef inaltransactionstatus.
File Content
Foradescriptionofthetransactionscenariopresentedwitheachexample,see"IndexofExamples"on
page247.Witheachrequestmessagesample,personalizeddatavalueswerereplacedwithstring
placeholders.
FIN11016 July 2014
Index of Examples
Thefollowingtabledescribesthescenariosillustratedbyeachexample.
Example
Verification
Type
Countr
y
Transaction Type Description
1 iCheck US AccountVerification Riskscorereturned;InstantIDscores
returned;OFACcheckenabled;user
passes.
2 iCheck US AccountVerification Usercannotbelocated.
3 iCheck US Purchase Disambiguatingquestionpresented;
userpasses.
4 iCheck US Purchase Agethresholdof21enabled;FraudPoint
scoresreturned;userfails.
5 iCheck US AccountVerification Userfails;iLocateMatchSummary
enabled.
6 iCheck US AccountVerification Userunder18yearsofage;transaction
fails.
7 iCheck UK AccountVerification Velocitycheckenabled;userfails.
8 iCheck UK AccountVerification Usercannotbelocated;CallCenter
Assistenabled.
9 iAuth US AccountVerification Oneroundofquestionspresented;Flex
IDelementsreturned;userpasses.
10 iAuth UK AccountVerification Disambiguatingquestionpresented
followedbyoneroundofquestions;
userpasses.
FIN11016 July 2014
11 iAuth US AccountVerification Questionspresentedsequentially;user
passes.
12 iAuth US AccountVerification QuestionspresentedinSpanish;user
passes.
13 iAuth US AccountVerification Tworoundsofquestions;userfails.
14 iAuth US AccountVerification Continuationmessagenotreturnedin
allottedtime;transactionexpired.
Example
Verification
Type
Countr
y
Transaction Type Description
Request Message Quick Reference| 249
FIN11016 July 2014
Appendi x D
Request Message Qui ck
Ref erence
I n Thi s Chapt er
RequestMessage
QuickReference
Overview,page250
IdentityVerif ication
Message,page250
continuation
Message,page258
FIN11016 July 2014
Request Message Quick Reference Overview
Thisappendixprovidesaquickreferencetotheminimumsetofparametersthatshouldbeincludedin
IdentityVerif icationSOAPrequests.
InformationinthissectionispresentedinapseudoSOAPmessagelayoutwithindentationstoshow
nestedchildelements.Fordetaileddescriptionsofallparameters,see"APIReference"onpage154
IdentityVerification Message
AnIdentityVerif icationmessageisusedtoinitiateanIdentityVerif icationtransaction.Thissection
providesaquickreferencetotheminimumsetofparametersthatshouldbeincludedinan
IdentityVerif icationmessage.
Fordetaileddescriptionsofallparameters,see"IdentityVerif icationMessage"onpage250.
When the User is Living in the United States
transactionidentityverification
Toplevelcontainer(rootelement)fortheIdentityVerif icationmessage.Sometimesreferredtoasa
transactioninitiate.
settings
Containerelementthatprovidesaccountinformationandidentif iesthetypeofverif icationyouwant
IdentityVerif icationtoperform.Formoreinformation,see"settingstype"onpage205
accountname
Theclientsaccountname.ThisaccountnameisprovidedtoyoubyLexisNexis.
mode
Modeinwhichthetransactionshouldberun.
ValidValues:simulated,testing,pilot,live
FIN11016 July 2014
Ifthevalueissimulated,youshouldalsoincludethesimulatormodeparameter;ifyoudonotinclude
simulatormode,thesystemdefaultstoreturningrandomcannedresponsesforeachrequest.
ruleset
Referstoanamedsetofconf igurationsettings,knownasaparameterset,usedtogoverntheoperation
ofatransactionforeachIdentityVerif icationclient.ContactyourTechnicalSolutionsConsultantfor
thenameofyouraccountsparameterset.
task
Thetypeoftransaction.
ValidValues:icheck,iauth
/settings
person
Containerelementthatprovidesinformationabouttheuserbeingauthenticated.Formore
information,see"persontype"onpage192Notethatwiththepersonelement,themoreinformation
youprovideaboutauser,thegreaterthechancethatIdentityVerif icationwillbeabletolocatethat
usersidentityduringtheiLocateprocess.
namefirst
Theusersf irstname.
namelast
Theuserslastname.
email
(Recommended;notrequired.)Theusersemailaddress.Multipleemailaddressesareallowed.
ssn
(Notrequiredifaddressisprovided.)Theuserssocialsecuritynumber.
ssntype
(Onlyrequiredwhenssnisprovided.)Typeofsocialsecuritynumber.
FIN11016 July 2014
ValidValues:ssn4,ssn9,nossn
birthdate
(Requiredforverif icationswhenanagethresholdisenabled.)Specif iestheusersbirthdate.Theuser
mustbeatleast18yearsold.IdentityVerif icationcannotperformaverif icationonapersonwhoisless
than18yearsold.
year
Theyearoftheusersbirthdate.
ValidValues:Fourdigitinteger.Forexample:1970
month
Themonthoftheusersbirthdate.
ValidValues:Integerbetween1and12.Forexample:5forMay
day
Thedayoftheusersbirthdate.
ValidValues:Integerbetween1and31.
/birthdate
Closeselement.
address
(Notrequiredifssnisprovided.Notethatyoucanprovidebothssnandaddressifavailable.)Primary
addressassociatedwiththeuser.
Optionally,youcanincludemultipleaddresselementstoprovideadditionaladdressesassociatedwith
theuser(forexample:theusersbusinessaddress).
addressstreet1
Firstoronlylineofstreetaddress.
MaximumCharacters:150
addresscity
FIN11016 July 2014
Cityofaddress.
addressstate
Stateofaddress.
ValidValues:ValidtwoletterUSPSstatecode(Seehttp://www.usps.com/ncsc/lookups/
usps_abbreviations.html#states.)
addresszip
Zipcodeofaddress.
ValidValues:Astringoff ivenumericdigitsinNNNNNformat.
addresscontext
Thefunctionoftheaddressfortheuser.Specifyprimary.
ValidValues:primary,secondary,previous,vacation,business,other
/address
phonenumber
(Recommended;notrequired.)Containerelementspecifyingtheusersphonenumber.
phonenumber
Theusersphonenumberinxxxyyyzzzzformat.Forexample:1234567890.
phonenumbercontext
Thecontextinwhichthephonenumberisassociatedwiththeuser.
ValidValues:home,business,mobile,fax,pager,other
/person
transaction
FIN11016 July 2014
Containerelementthatprovidesinformationaboutthetransactionandidentif iesthattheverif ication
isneededforeitherapurchaseoranaccounttransaction.Formoreinformation,see"transactiontype"
onpage214.
accountverificationtype
Containerelementthatidentif iesthevenueanddateofthetransaction.
venue
Containerelementthatdescribesthetypeofenvironmentwherethetransactionistakingplace.
online
callcenter
pointofsale
customerservice
ivr
/venue
Closeselement.
Include one of these parameters in the venue element. For example: venue, callcenter, /callcenter, /
venue. These parameters do not need to include any of the optional, child elements.
activity-date
Thedateandtimeofthetransaction.
ValidValues:DatetimevalueinISO8601dateandtimeformat:
Example:
20100615T13:20:05.768Z
/account-verification-type
Closeselement.
/transaction
FIN11016 July 2014
Closeselement.
/transactionidentityverification
Closeselement.
When the User is Living in the United Kingdom
transactionidentityverification
Toplevelcontainer(rootelement)fortheIdentityVerif icationmessage.Sometimesreferredtoasa
transactioninitiate.
settings
IdentityVerif icationtoperform.Formoreinformation,see"settingstype"onpage205.
accountname
mode
Modeinwhichthetransactionshouldberun.
ValidValues:simulated,testing,pilot,live
ruleset
thenameofyouraccountsparameterset.
task
Thetypeoftransaction.
FIN11016 July 2014
ValidValues:icheck,iauth
/settings
person
Containerelementthatprovidesinformationabouttheuserbeingauthenticated.Formore
information,see"persontype"onpage192.Notethatwiththepersonelement,themoreinformation
youprovideaboutauser,thegreaterthechancethatIdentityVerif icationwillbeabletolocatethat
usersidentityduringtheiLocateprocess.
namefirst
Theusersforename.
namelast
Theuserssurname.
ukaddress
Primaryaddressassociatedwiththeuser.
street1
Firstoronlylineofstreetaddress(includinghousenumber).Optionally,youcanincludethehouse
numberinaseparatehousenumberparameter.
MaximumCharacters:Thisparameterplushousenumber(ifyouincludeitseparately)shouldnot
exceed32characters.
postcode
Validpostcodefortheaddress.
context
Thefunctionoftheaddressfortheuser.Mustbesettoprimary.
/ukaddress
FIN11016 July 2014
/person
Closeselement.
transaction
Containerelementthatprovidesinformationaboutthetransactionandidentif iesthattheverif ication
isneededforeitherapurchaseoranaccounttransaction.Formoreinformation,see"transactiontype"
onpage214.
accountverificationtype
Containerelementthatidentif iesthevenueanddateofthetransaction.
venue
Containerelementthatdescribesthetypeofenvironmentwherethetransactionistakingplace.
online
callcenter
pointofsale
customerservice
ivr
/venue
Closeselement.
activitydate
Thedateandtimeofthetransaction.
ValidValues:DatetimevalueinISO8601dateandtimeformat:
Example:
20100615T13:20:05.768Z
/accountverificationtype
FIN11016 July 2014
Closeselement.
/transaction
Closeselement.
/transactionidentityverification
Closeselement.
continuation Message
Thissectionprovidesaquickreferencetotheminimumsetofparametersthatshouldbeincludedina
continuationmessage.SendacontinuationmessagetorespondtoasetofquestionsduringaniAuth
authentication.
Fordetaileddescriptionsofallparameters,see"continuationMessage"onpage166.
transactioncontinue
Thetoplevelcontainer(rootelement)forthecontinuationmessage.
settings
IdentityVerif icationtoperform.Formoreinformation,see"settingstype"onpage205.
accountname
mode
Themodeinwhichthetransactionshouldberun.
ValidValues:simulated,testing,pilot,live.
FIN11016 July 2014
ruleset
thenameofyouraccountsparameterset.Formoreinformationonparametersets,see"Application
DesignProcess"onpage37.
transactionid
Specif iesthetransactionIDprovidedbyIdentityVerif icationinthetransactionResponsemessagethat
wassentinresponsetotheIdentityVerif icationmessage.
/settings
Closeselement.
answers
Containerelementthatincludestheanswersprovidedbytheuserinresponsetothesetofquestions
returnedinthetransactionResponsemessage.Formoreinformation,see"answerstype"onpage179.
questionsetid
TheIDforthesetofquestions,asprovidedinthetransactionResponsemessage.AsetIDisprovided
evenwhenquestionsarepresentedsequentially.
answer
Containerelementthatprovidestheusersanswertoaparticularquestion.Includeananswerelement
foreachquestionpresentedinthetransactionResponsemessage.
questionid
TheIDforaparticularquestion,asprovidedinthetransactionResponsemessage.
choices
ContainerelementthatprovidesoneormorechoiceIDsforaparticularquestion
choiceid
TheIDcorrespondingtotheanswerselectedbytheuser.Ifthequestionisamultipleanswerquestion,
youcanincludemultiplechoiceidparameterswithinthechoiceselement.
FIN11016 July 2014
/choices
Closeselement.
/answer
Closeselement.
/answers
Closeselement.
/transactioncontinue
Closeselement.
Glossary | 261
FIN11016 July 2014
Gl ossary
account
TheentitycreatedwithintheIdentityVerif icationdatabasetorepresentaLexisNexisclientthat
usesIdentityVerif icationtoauthenticatetheircustomers.Accountnames,asassignedby
LexisNexis,mustbeincludedinallSOAPrequestssenttotheIdentityVerif icationwebservice.
account veri f i cat i on
Oneoftwomaintransactiontypesforaverif ication(theotherisapurchase).Accountverif ication
transactionsareassociatedtoausersaccount.Theyincludeaccountorigination,account
maintenance,andaccountactivity(forexample,amoneytransfer)transactions.Anaccount
verif icationtransactionmayinvolveapurchasebyauserwhohasanaccountwiththeclient.
ANI ( Aut omat i c Number I dent i f i cat i on)
Aservicethatidentif iestothereceiverofatelephonecalltheBillingTelephoneNumber(BTN)or
directnumberfromwherethecallismade.ThereisadifferencebetweenCallerIDandANI:Caller
IDsometimesdisplaysthemainnumberofabusinessratherthanthedirectnumberfromwhich
thecallwasmade.
cal l cent er
ApossiblevenuewhereIdentityVerif icationisusedbyacallcenteragenttoauthenticatea
customerviatelephone.
chi l d account
Anaccountcreatedunderarootaccount.
cl i ent
TheLexisNexiscustomerwhoisusingIdentityVerif icationtoverifytheidentityofendusers.
CanalsorefertoaSOAPclient,whichistheapplicationthatisintegratedwiththeIdentity
Verif icationwebservice.ASOAPclientsendsSOAPrequeststoIdentityVerif icationandprocesses
SOAPresponses.
cl i ent cert i f i cat e
OneofthepossiblemethodsforauthenticatingaSOAPclienttoawebservice(theothermethodis
thebasicusername/passwordauthenticationscheme).Aclientcertif icateusesadigitalsignatureto
Glossary | 262
FIN11016 July 2014
bindapublickeywithinformationabouttheholderofthecertif icate.Whenyourapplication
attemptstoconnecttoIdentityVerif icationusingaclientcertif icate,theIdentityVerif icationweb
serververif iesthecertif icateisauthenticbeforeestablishingtheconnectionandallowingthe
transactiontocontinue.AlsoreferredtoasanSSLcertif icateoradigitalcertif icate.
di rect i nt egrat i on
OneoftwomethodsforimplementingIdentityVerif ication.Withadirectintegration,theclient
integratestheirconsumerfacingapplicationwithIdentityVerif icationviaawebservices
applicationprogramminginterface.TheotherimplementationmethodisusingtheNetviewWeb
PortaltocommunicatewithIdentityVerif ication.Manyclientsdevelopanauthenticationsolution
thatusesbothmethods.
di sambi guat i ng quest i on
Tohandlesituationswheretheuserisdiff iculttolocatebasedonthedataprovided,Identity
Verif icationcanbeconf iguredtopresentadisambiguatingquestion.Theanswertothe
disambiguatingquestionhelpsIdentityVerif icationselecttheappropriateindividualfrompossible
matches.
end poi nt
AURLthatindicatesaspecif iclocationforaccessingawebservice.Forexample,https://
netview.verid.com/carbon/wsistheendpointfortheIdentityVerif icationwebservicerunningon
theproductionserver.
end user
Thepersonwhoseidentitytheclientapplicationneedstoverify.Alsoreferredtoasuseror
consumer.
i Aut h
Thehighestlevelverif icationtypethatcanberequestedfromIdentityVerif ication.AniAuthf irst
conf irmsthattheusersidentityexistsandthenusesKBA(KnowledgebasedAuthentication),risk
assessment,andidentityfraudmonitoringtoauthenticatetheuser.
i Check
Averif icationtypethatconf irmsthattheusersidentityexistsbycheckingthattheprovideddata
(forexample:name,address,andphonenumber)matchesdatacollectedfrompublicrecordsand
otherdatasources.Inadditiontoconf irmingthatanidentityexists,aniCheckcanperformrisk
assessmentandidentityfraudmonitoringtoauthenticatetheuser.
Glossary | 263
FIN11016 July 2014
I dent i t y Ri sk Score
Anumericvalue,0to1000,basedonanassessmentoftheriskoffraudassociatedwithanidentity
duringaniAuth,oriChecktransaction.Thecloserthenumberisto1000,thegreatertherisk.
Knowl edge- Based Aut hent i cat i on ( KBA)
AnauthenticationprocessusedbyIdentityVerif icationduringaniAuthverif ication.WithKBA,
IdentityVerif icationscansbillionsofpublicrecordsandothercommerciallyavailabledatasources
tocompileaseriesofnonintrusive,topofmindquestionsrelevanttotheindividualwhoseidentity
youaretryingtoverify.Designedtologicallydevelopcorrectandincorrectanswers,Identity
Verif icationscorestheindividualsanswersanddeliversaconf irmationwithoutrequiringany
priorrelationshipwiththeindividual.
Net vi ew Web Portal
TheNetviewWebPortalistheIdentityVerif icationInternetapplicationforcallcenter
representativesandothercustomerliaisonstosubmitverif icationrequests.Netviewcanalsobe
usedtomanageNetviewuseraccountsandgeneratetransactionreports.
not i f i er
Atoolthatcanbeconf iguredtosendanotif icationemailtoalistofsubscribeduserswhena
transactionreachesafrequencythresholdorwhenthereisindicationofANI/CallerIDspoof ing.
OFAC l i st
OFACstandsforOff iceofForeignAssetControl.OFACpublishestheSDN(SpeciallyDesignated
Nationals)list,whichcontainsnamesofforeignindividualswhohavebeenidentif iedaspotential
threatstotheUSandareblockedfromtakingpartinf inancialactivitieswithintheUnitedStates,
includingopeningnewbankaccountsandbrokerageaccounts.TheUSPatriotActrequires
checkingindividualsagainsttheOFACSDNlistinordertocomplywithSection326.
onl i ne
ApossiblevenuewhereIdentityVerif icationisusedbyawebsiteapplicationtoverifytheidentity
ofanonlineuser,withoutinteractionwithacallcenterorserviceagent.
parameter set
Aclientscustomconf igurationofverif icationoptions.Parametersetsgovernmanydifferent
aspectsofsystembehavior,suchasthetypesofquestionsthatareaskedandhowthosequestions
arescored.Byadjustingparametersets,IdentityVerif icationcanbetailoredtomeetthechanging
needsofacompanysauthenticationprocess.Forexample,alargemerchantmayrequireastrict
Glossary | 264
FIN11016 July 2014
parametersettoprocesstransactionsinahighfraudareaandalessrestrictiveparametersetfor
anotherareaoftheirbusinessthatistypicallylowfraud.WhenyousendaSOAPrequesttoIdentity
Verif ication,youspecifywhichparametersettouseforthattransaction.Alsoreferredtoasarule
set.
purchase
Oneoftwomaintransactiontypesforaverif ication(theotherisanaccountverif ication).Witha
purchase,theverif icationisrequiredaspartofaretailpurchasetransaction.Purchasetransactions
mayrequireadditionalinformationsuchascreditcardnumber,checknumber,ortransaction
amount.
request
ASOAPrequestisanXMLdatastructuresenttoIdentityVerif icationintheformofadocument.
response
ASOAPresponseisthemessagereturnedfromIdentityVerif icationbasedontheresultsofthe
request.
t ransact i on
AtransactionencompassestheentireprocessofsubmittinginformationtoLexisNexisfor
authenticationandLexisNexisreturningtheappropriateresponse.
user
Thepersonwhoseidentitytheclientapplicationneedstoverify.Alsoreferredtoasenduseror
consumer.
venue
Theoriginatingsourceoftheverif icationrequesttoIdentityVerif ication.Commonvenuesinclude
acallcenteroranonlineecommercewebsite.
veri f i cat i on t ype
TheprocessthatIdentityVerif icationwillfollowtoverifytheidentityofauser.Therearefour
verif icationtypes:iAuthandiCheck,.
Glossary | 265
FIN11016 July 2014
web servi ce
Asoftwaresystemdesignedtosupportinteroperablemachinetomachineinteractionovera
network.AWSDL(WebServiceDef initionLanguage)isusedtodescribeawebservicesinterface.
SystemscaninterfacewithawebserviceusingSOAPmessagessentoveranHTTPorHTTPS
connection.(TheIdentityVerif icationservicesupportsanHTTPSconnection.)
WSDL ( Web Servi ce Def i ni t i on Language)
ProvidesanXMLgrammarthatdescribesalltheinformationneededtoinvokeawebservicefroma
clientapplication.
WS- I
Anopenindustryorganizationdesignedtopromotewebservicesinteroperabilityacrossplatforms,
operatingsystems,andprogramminglanguages.IdentityVerif icationisWSIBasicProf ileVersion
1.1compliant.
Index | 266
FIN11016 July 2014
I ndex
A
addresselement, 53
militarydesignations, 135,
136
agethresholdexample, 103
answerselement, 66
APIreference, 155
API,IdentityVerification, 26
applicationenvironmentset
up, 28
applicationprogramming
interface, 26
architecturalmodel, 18
authenticationcredentials, 28
authenticationschemes
clientcertificate, 30
usernameand
password, 29
B
bestpractices, 48,135
design, 41
binding, 160
C
CarbonWebService, 156
clientcertificate, 30
authenticatingwith, 47
expired, 31
client,SOAP, 21
codes, 234
error, 220
failure, 222
information, 228
connection, 28
webservice, 46
continuationmessage, 65
APIdetails, 166
conventions, 14
credentials, 28
D
datatypes,APIdetails, 168
designguidelines, 41
designprocess, 37
directintegration, 26
disambiguatingquestion
UK, 110
US, 97
E
envelope,SOAPmessage, 23
environmentsetup, 28
errorcodes, 220
F
failurecodes, 222
H
Helptext, 42
I
iAuth, 39
example, 51
iCheck, 38,40
example, 84,94
IdentityVerification
API, 26
architecturalmodel, 18
connectingto, 46
implementation
methods, 25
verificationtypes, 18
IdentityVerificationmessage
APIdetails, 164
example, 51
iLocateMatchSummary, 124
implementationmethods, 25
implementationprocess, 27
informationcodes, 228
informationelement, 59
integration
direct, 26
guidelines, 48,135
methods, 25
testing, 151
internationalization
example, 121
L
live(production)mode, 152
longdatatype, 137
Index | 267
FIN11016 July 2014
M
manual
organizationof, 13
messages
basicexchangeof, 21
reference, 162
militaryaddresses, 135,136
modes
live(production), 152
N
namespace, 156
NetviewWebPortal, 26
P
parameterset, 37
personelement, 52
requiredparameters, 132
porttype, 157
productionmode, 152
Q
questiontext
UKimplementations, 240
USimplementations, 235
questionselement, 57
R
reference,API, 155
requests,SOAP, 22
response,SOAP, 25
S
secureconnection, 28
servicedescription, 156
servicename, 156
settings, 51
SOAP
basicmessageexchange, 21
client, 21
messagebody, 23
messages
examples, 49
requests, 22
response, 25
server, 21
Spanishexample, 121
stringdatatype, 137
Submitbutton,disabling, 42
systemmessages, 220
T
targetnamespace, 156
testing, 151
transactionstatuselement, 55
transactionResponse
message, 55
APIdetails, 167
translatingquestions, 121
V
verificationtypes, 18,19
iAuth, 39
iCheck, 38,40
verificationworkflows,
designing, 37
W
workflows
designing, 37
iAuth, 39
iCheck, 38,40
WSDL
local, 48
location, 156
WSIcompliance, 18
X
X.509clientcertificate, 30
XMLlongdatavalues, 137
xslongdatatype, 137
xsstringdatatype, 137

DevelopersGuide InstantIDQA94

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

DevelopersGuide InstantIDQA94

Încărcat de

Drepturi de autor:

Formate disponibile

Lexi sNexi s

This is a note icon. It precedes helpful information.

The reference-id is returned in two parameters to maintain backward-compatibility with applications

is included in the main TransactionResponse message (see"External

is included in the main TransactionResponse

The name-first and name-last parameters are required.

In the source code above, <s0:port binding="s2:CarbonSoapBinding" name="CarbonSoapPort"> is

Risk data that you provide in this data

Risk data that you provide in this data

The WSDL supports any character string

Risk data that you provide in this data type

Do not use this parameter to specify any

For diagnostic purposes, you should store

The reference-id is returned in both this

S-ar putea să vă placă și