iClear: XVerify Email Lookup
Support At Phonexa avatar
Written by Support At Phonexa
Updated over a week ago

The XVerify Email Lookup service allows you to perform real-time validation of the lead email address through XVerify third-party service and reject leads based on the service response.

To enable this service, go to the Fraud Detector > iClear section and select a Product from the drop-down list.

Once you select the Product, you’ll be automatically redirected to the Lead Processing Rules (iClear) sub-tab. You may also navigate here by selecting the System Management > Products section on the left-hand menu and clicking on the “Settings” button for the corresponding product (Lead Processing Rules (iClear) sub-tab).

To configure this service, click the “Add Service” button in the Global Rules block. Fill in the following fields:

  • Select Third Party Service: Select the “XVerify Email Lookup” option.

  • XVerify API Key: Fill in your XVerify API key.

  • XVerify Allowed Domain: Fill in the domain you have configured in your Xverify settings under which this query should be processed.

  • Select a field to retrieve the email: Select which field the system will retrieve the email address from. Example: email.

  • Execution Type:

    • Select the "Synchronous" option to wait for the XVerify email lookup outcome before processing a lead. This execution type is recommended for real-time filtration of a lead based on the lookup status. Before processing a lead, the system makes a request to the XVerify email lookup service. If the email is valid, the system will process the lead according to the lookup status.

    • Select the "Asynchronous" option to make a simultaneous request and process a lead without waiting for the lookup outcome. This execution type is recommended for analytical purposes and not for real-time filtration of a lead based on the lookup status. While processing a lead, the system makes a request to the XVerify email lookup service. The lead will be processed as usual, but it could be added to the DNPL based on the result of the lookup status.

  • % of leads to lookup: Set the percentage of leads to be checked through this service.

  • Use Cache Data Not Older Than (days): Enter the maximum period (in days )for cache data usage.

  • Reject the lead if XVerify returns this status(es): Select what leads you would like to filter out if you receive the chosen status. The status description is provided on the XVerify side.

The “Add to Do and Do Not Present lists” configuration block allows you to use the service to add more filters to your existing DNPLs. Read more about Present and Do Not Present lists in the Knowledge Base article. Fill in the following fields to configure:

  • Status: Select the XVerify statuses to be added to the chosen PL/DNPLs configuration.

  • Do and Don Not Present Lists: Select one or more available PL/DNPLs from the list.

The “Advanced Settings” configuration block allows you to customize the lookup and timeout settings of the service according to the selected Execution Type.

  • Lookup only in local DB (Synchronous Execution only): Select “Yes” for the service to lookup only in the local database. Select “No” for the service to lookup both in the local database and API.

  • If local lookup failed - perform Async run (Synchronous Execution only): Select “Yes” to perform the Asynchronous run in case the local database lookup is unsuccessful. Select “No” to disable the lookup override.

  • API Timeout (Synchronous Execution): Fill in the service response timeout (from one to five seconds). The field is active only if the “Lookup only in local DB” option is disabled.

  • API Timeout (Asynchronous Execution): Fill in the service response timeout (from one to five seconds).

  • After timeout run as Async (Synchronous Execution only): Select “Yes” to perform the Asynchronous execution if the timeout runs out. Select “No” to disable the Asynchronous run override.

Click the “Add” button to confirm.

Read more about the Global Rules and Advanced Rules configuration in this Knowledge Base article.

Did this answer your question?