Identity Verify - Advance

introduction the identity verify api (“identity verify”) enables you to verify an individual consumer’s identity using a phone first approach that validates consumer provided personal identifying information (pii) and confirms ownership of their phone number using authoritative data, including device and phone number tenure data this is a critical step in ensuring your important consumer interactions are with the phone number owner and information, helping eliminate bad actors and prevent fraudulent accounts signzy performs ownership verifications without ever storing your consumers' pii ownership verification goes beyond just matching a person's name and address; inputs that can be included for matching in the api request are name, address, full ssn (or last four digits of ssn), date of birth (dob), and driver's license number and state the api's verified flag and matching details can help with customer onboarding (acquisitions, originations, registrations, etc ) and servicing (e g , your customer adds a new phone number to their profile) and enhances user experience `` by utilizing this api, you can ensure the integrity of the user's identity information and make informed decisions based on the verification results features phone number ownership verification identity verify provides phone ownership verification using the phone number status + the name & address information, or ssn, to then determine a verified status of true or false you start by querying the phone number, locating the relevant information associated with the identity recognized behind the phone number, and then matching appropriate fields against your consumer's submitted data api details you must first login before sending the request the authorization header in the request must include the access token obtained from the login api call sample curl curl location 'https //api signzy us/api/v3/us kyc/idv advance' \\ \ header 'content type application/json' \\ \ header 'authorization \<auth token>' \\ \ data '{ "consentstatus" "optedin", "phonenumber" "19177253169", "ssn" "602410869", "firstname" "hanson", "lastname" "kerner", "address" "761 shasta place", "city" "fort lauderdale", "region" "il" "postalcode" "33355", "countrycode" "us", "dob" "1990 02 21", "emailaddress" "abc\@gmail com", "driverslicensenumber" "123abc", "driverslicensestate" "il" "details" "true" }'curl location 'https //api preproduction signzy us/api/v3/us kyc/idv advance' \\ \ header 'content type application/json' \\ \ header 'authorization \<auth token>' \\ \ data '{ "consentstatus" "optedin", "phonenumber" "19177253169", "ssn" "602410869", "firstname" "hanson", "lastname" "kerner", "address" "761 shasta place", "city" "fort lauderdale", "region" "il" "postalcode" "33355", "countrycode" "us", "dob" "1990 02 21", "emailaddress" "abc\@gmail com", "driverslicensenumber" "123abc", "driverslicensestate" "il" "details" "true" }' request body parameters true 165,165,165,166 unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type consumer input parameters regardless of whether details are returned or not, a match score is generated for the following pii data elements name (first name, last name, name score) address (street number, street, city, region, postal code, distance, address score) boolean values can be generated for the following pii data elements identifiers (last4 of ssn, full ssn, date of birth, driver's license number, and state) the fields you implement for your identity verify calls should reflect the typical personal information you request from your consumers at minimum , however, the request needs to include the phone number either to return a successful response; otherwise, an error is returned however, the more fields included for name, address, and ssn, the more reliable the verification result when the api request is sent, if signzy finds no data for the person, verified returns false, and a reason code of nc is returned, indicating no name and address information associated with the phone number the consumer should then be put through your organization's step up procedure if data is found for the person, the data matching process is enabled and performed for the available fields as outlined in the scoring and matching framework section below score and matching framework signzy checks the information submitted through the identity verify api, only matching information submitted using our proprietary logic you're able to see the details of the resulting matching and scores in your responses by including the details parameter as true in the request name and address matching match results for the name and address fields are calculated with weighted algorithms to generate a score for each; the weight applied is influenced by how much variance was found between submitted data and queried data (e g , which fields returned true/false, etc ) these calculations then return a unique total score for the name matching and (if the information is submitted) a unique total score for the address matching; each can fall between 0–100 these scores contribute to the verification of the end user with the following logic either a namescore greater than or equal to 70 or an addressscore equal to 100 contributes to verified returing true both name and address scores failing the above thresholds contribute to verified returning false name and address matching notes name matching takes into account nicknames first/last name transposition name contained within those with changed last name due to marriage mother and father's name concatenated or split within middle and last name fields fuzzy match logic extended address data can be submitted to support the many address forms with additional lines for apartment numbers, etc , but this data is not factored into address matching logic reason codes are returned when these matching elements come into play ssn and last4 matching if a ssn (or last4) was submitted, but neither name field was submitted, the name and address matching is not enabled, and matching is performed only using the ssn/last 4 with the following logic if the ssn/last4 submitted matches the data found, verified returns true if the ssn/last4 submitted information does not match the data found, verified returns false see the identity verify flows section for diagrams of each situation the rest of the request and response parameters (date of birth, driver's license, etc ) are simply informational, returning true or false (if details is set to true, see the detailed response section) to help you confirm submitted data and not contribute to the verified response identity verify flows response body parameters true 220,220,221 unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type if a death indicator was found in the matching data for the person submitted, verified returns false, and a di reason code is returned in the response as well see the reason codes section for more information on identity verify reason codes detailed response there is a critical query parameter to explain first details it's set by default to false, but if you determine you want to receive the matching outcome for the various pii inputs of your consumer, it should be set to true the api response then includes a field level breakdown of the matching and score results, which can add visibility to the verification decision when left to false, you only receive the overall verified result sample response (details = true) { "result" { "requestid" "6466555fa90017ffa26ebba0", "status" 0, "description" "success ", "response" { "verified" true, "transactionid" "12225155440", "payfonealias" "60a37e2c4vkrkkx4d3fd70cee16c05afa0mek1a51jd9p396647cb4c454f4dc26a7202ba66e04e2f9f6g30f557a4cd71d054fb417ee475b03404d02bf", "phonenumber" "19177253169", "linetype" "mobile", "carrier" "t mobile usa", "countrycode" "us", "name" { "firstname" 100, "lastname" 100, "namescore" 100 }, "address" { "streetnumber" 100, "street" false, "city" true, "postalcode" true, "distance" 0, "addressscore" 100 }, "identifiers" { "ssn" true }, "identifiers" { "dob" true }, "reasoncodes" \[ "ou", "p5", "pt", "rm", "uv" ] } } } sample response (details = false) { "result" { "requestid" "6466555fa90017ffa26ebba0", "status" 0, "description" "success ", "response" { "verified" true, "transactionid" "12225155440", "payfonealias" "60a37e2c4vkrkkx4d3fd70cee16c05afa0mek1a51jd9p396647cb4c454f4dc26a7202ba66e04e2f9f6g30f557a4cd71d054fb417ee475b03404d02bf", "phonenumber" "19177253169", "linetype" "mobile", "carrier" "t mobile usa", "countrycode" "us", "dob" "1990 02 21", "reasoncodes" \[ "ou", "p5", "pt", "rm", "uv" ] } } only parameters submitted in the request return in a detailed response for example, if city was not included in the address fields for the request, there is no matching performed for that field, and that field is excluded from the response reason codes along with the scores, signzy supplies reason code(s) in the response that gives further insight into why a particular score was returned or indicates the risk associated with the identity this is to assist you in making informed decisions for managing your risk the following reason codes can be returned for all versions of the identity verify api true 330,331 unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type sample error { "error" { "name" "error", "message" " message ", "status" 400, "reason" "badrequest", "type" "ok", "statuscode" 200 } } error response parameters 283,520 true left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type unhandled content type left unhandled content type unhandled content type left unhandled content type left unhandled content type left unhandled content type unhandled content type left unhandled content type left unhandled content type left unhandled content type unhandled content type getting help please feel free to contact us if you have any questions, require clarification, or have ideas for how to make the documents or any of our services better you can reach out to us at we strive to provide prompt and reliable assistance, ensuring your queries are addressed effectively we value your feedback and are committed to making your experience smooth and enjoyable our team is dedicated to assisting you with any needs you may have thank you for choosing our services we look forward to helping you!