The CrossCheck feature might have an additional cost, depending on your identity package. Please reach out to our support team before enabling it.

[email protected]

The CrossCheck feature verifies users' identities across various proprietary databases, by crossing two or more of the following parameters:

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

The more parameters that are submitted, the more accurate the results.

Submitting a CrossCheck job:

There are two main ways to submit a CrossCheck job:

1. CrossCheck as an add-on to IDV:

Using this method can be done by:

  • JS plugin - adding enableCrossCheck = true to the verification object;
  • Invite API - adding "enableCrossCheck" : true ; or
  • Ask Vouched team to turn it on to your account for any other integration methods.

The parameters can be submitted as follow:

  • Full name - extracted automatically from the ID picture.
  • Physical address - extracted automatically from the ID picture.
  • Phone number - submitting a phone parameter in the JS plugin or API request.
  • Email address - submitting an email parameter in the JS plugin or API request.
  • IP address - extracted automatically from the request.

2. Submitting a separate CrossCheck job:

By using our CrossCheck API.

The results

CrossCheck results include the following fields:

  • Identity Score - the main result parameter, a number between 0 to 1 that indicates the matching score for the candidate.
  • Activity Score - a number between 0 to 1 that is based on the number of times the data provided by the user has been observed in online transactions. More usage, the lesser the score.
  • Age range.
  • Gender.
  • Address: match, valid, warnings, and more.
  • Email: match, valid, days first seen, auto generated, disposable, warnings, and more.
  • Phone: match, valid, carrier, prepaid, warnings, and more.

The above results can be found:

1. In your Vouched dashboard, as the following picture:

  • When the identity score is below the threshold, the job will be marked with an orange warning symbol.

2. Via the Webhook response

The full result is under the result.crosscheck field, while the main identity score is under result.crosscheck.confidences.identity.
JSON example:

"crosscheck": {
                    "gender": {
                        "man": 3.271,
                        "woman": 0.012
                    "darkWeb": null,
                    "address": {
                        "errors": [],
                        "warnings": [],
                        "isMatch": true,
                        "isValid": true,
                        "name": "John W Smith",
                        "ageRange": null,
                        "type": "multi-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": "Mr. John W Smith",
                        "ageRange": null,
                        "carrier": "AT&T",
                        "type": "mobile",
                        "isPrepaid": false,
                        "isDisposable": false,
                        "isCommercial": true
                    "ageRange": {
                        "to": 50,
                        "from": 48
                    "confidences": {
                        "identity": 0.73,
                        "activity": 0.058,
                        "darkweb": null
  • When the identity score is below the threshold, the field result.warnings will be true.

CrossCheck then IDV

Decisioning logic involving Crosscheck and IDV is used to minimize user friction while assuring identity. Here are the steps:

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