Phone Verification

What's the difference between this service and IDMatch?
In short, the main differences between this service and IDMatch are: 
The Goals - this service knows that your main objective is matching a phone number to a target. Therefore, this service will continue to search sources until that goal can either be confirmed or denied. 
​
The Required Inputs - this service only requires a first name, last name and phone number on input to process, but can accept all other target attributes and will attempt to match anything sent in the request. 
​
The Data Sources - this service uses additional phone number specific data sources to increase your success rate. 
Can I verify a user to their phone number outside of the United States? 
Yes. There are many countries outside of the US where Veratad has access to phone information. Please see the country coverage below: 
Data Coverage
Using this service coupled with PhoneMatch5.0.SMS and/or PhoneMatch5.0.Call is a great way to verify that the number belongs to your customer and that they have possession of the device to increase identity verification confidence. 
post
https://production.idresponse.com
/process/comprehensive/gateway
PhoneMatch5.0
Sample Request Body
{
      "user": "[email protected]",
      "pass": "PASSWORD",
      "service": "IDMatch5.0",
      "reference": "12345 {A UNIQUE ID}",
      "target":{
            "fn":"Barbara",
            "ln": "Miller",
            "phone": "2015106000",
            "test_key": "general_identity"
          }
  }
Service Testing
Use the test_key attribute to test the service. When the test_key is provided the system will dynamically drop the live data sources and use the testing database.
Test Cases
Action and Detail Responses
The following are all values that will be returned in the result object of the response.
Action
Detail
Description
FAIL
NO MATCH
No matching identity found in the data sources
FAIL
TARGET IS DECEASED
Target found as a deceased identity
REVIEW
TRANSACTION REQUIRES FURTHER ATTENTION
Target found and not deceased, but at least one identity attribute provided does not match. This will also populate the issuesobject with a list of the identity attributes that did not match. See full list below
PASS
ALL CHECKS PASSED
Target was found is not deceased and all submitted target attributes match
Issues Responses
When a transaction returns as REVIEW then there will be a list of issues. This list can include any of the below values.
Issue
Description
ADDRESS CHECK FAILED
The address provided does not match any on file
DOB CHECK FAILED
The Date of Birth provided does not match any on file
SSN CHECK FAILED
The SSN provided does not math any on file
PHONE CHECK FAILED
The phone number provided does not match any on file
EMAIL CHECK FAILED
The email address provided does not match any on file 
AGE CHECK FAILED
The age found does not meet the age submitted 
Rules
PhoneMatch will process with the default base ruleset. Which is as follows:
The base ruleset will return a PASS when:
A match is found
The target is not deceased
The target has provided all valid identity attributes
The base ruleset will return a REVIEW when:
A match is found
The target is not deceased
The target's identity attributes do not all match
This result will also return an array of issues to notify you of exactly which target attributes provided did not match. 
The base ruleset will return a FAIL when:
A match is not found or
The target is deceased

Smart 2FA

Phone Validation

Last modified 2yr ago

Copy link

Outline

What's the difference between this service and IDMatch?

Can I verify a user to their phone number outside of the United States?

Action and Detail Responses

Issues Responses

Rules