CrossCheck

CrossCheck verifies a user's identity by cross-referencing two or more of the following parameters against proprietary databases:

• Full name
• Physical address
• Phone number
• Email address
• IP address

In addition to Full Name, either a phone number or an email address (or both) is required to return results. Submitting more parameters improves the accuracy of the results.

CrossCheck may carry an additional cost depending on your identity package. Contact the Vouched team before enabling it.

Submitting a CrossCheck Job

There are two ways to submit a CrossCheck job.

1. As an add-on to IDV

• JS Plugin: add enableCrossCheck: true to the verification object.
• Invite API: add "enableCrossCheck": true.
• For any other integration method, contact the Vouched team to enable it on your account.

When submitted this way, parameters are populated as follows:

• Full name and physical address are extracted automatically from the ID photo.
• Phone number and email address are submitted as phone and email parameters in the JS Plugin or API request.
• IP address is extracted automatically from the request.

2. As a standalone job

Submit a CrossCheck job directly using the CrossCheck API.

POST https://verify.vouched.id/api/identity/crosscheck

Request parameters

Address object

Example request

{
    "firstName": "John",
    "lastName": "Bao",
    "email": "[email protected]",
    "phone": "000-111-2222",
    "ipAddress": "73.19.102.110",
    "address": {
        "unit": "",
        "streetAddress": "123 Elmo Avenue",
        "city": "Seattle",
        "state": "WA",
        "postalCode": "98109",
        "country": "US"
    }
}

The Result

Results appear in the Vouched dashboard and in the webhook response. The full result is under result.crosscheck, and the identity score is under result.crosscheck.confidences.identity.

A standalone CrossCheck response returns the request ID, an echo of the submitted request, and the result.

Confidences

Address

Email

Phone

Gender

IP

ip reports on the submitted IP address relative to the submitted address.

ipAddress returns the full inspection of the IP address and is available on standalone CrossCheck requests.

Errors and warnings

Each entry in an errors or warnings array contains the following fields.

JSON example

"crosscheck": {
    "gender": {
        "man": 3.271,
        "woman": 0.012
    },
    "address": {
        "errors": [],
        "warnings": [],
        "isMatch": true,
        "isValid": true,
        "name": null,
        "ageRange": null,
        "type": "single-unit",
        "isForwarder": false,
        "isCommercial": false
    },
    "email": {
        "errors": [
            {
                "type": "NameMatchError",
                "message": "Name match score is below the threshold (0.9)"
            }
        ],
        "warnings": [],
        "isMatch": false,
        "isValid": true,
        "name": null,
        "ageRange": null,
        "isAutoGenerated": false,
        "isDisposable": false,
        "daysFirstSeen": 992
    },
    "phone": {
        "errors": [],
        "warnings": [],
        "isMatch": true,
        "isValid": true,
        "name": null,
        "ageRange": null,
        "carrier": "AT&T",
        "type": "mobile",
        "isPrepaid": false,
        "isDisposable": false,
        "isCommercial": false
    },
    "ageRange": null,
    "ip": {
        "isValid": true,
        "distance": 12.4
    },
    "model": "fraud",
    "confidences": {
        "identity": 0.73,
        "originalIdentity": 0.68,
        "activity": null
    },
}

If the identity score falls below the threshold, result.warnings is set to true and the job is marked in orange in the dashboard.

If neither a phone number nor an email address is submitted, the following error is returned:

{
    "type": "InvalidRequestError",
    "message": "Phone number and/or email address is required"
}

Response codes

CrossCheck then IDV

This decisioning logic combines CrossCheck and IDV to minimize user friction while still confirming identity:

1. Perform CrossCheck verification with the user's information.
2. If CrossCheck's confidences.identity passes the required threshold, continue with the post-verification process.
3. If CrossCheck fails, or other criteria such as gender do not match, move the user to IDV.