Case Search

After connecting to ZOLOZ, you can search for cases using one or more fields on the case search page as well as export your case search results. At the same time, you can view the details of specified case results to help you better understand the product uses. 

Introducing case search function

Case search

You can search for product records using the search filters: Transaction ID, BizId, User ID, Product Type, Time, ID Number, TransactionId Suffix, Doc Type, Deleted Remark, and Result fields.

Picture 3.png

Field name

Description

transactionId

A unique transaction ID that is generated by the ZOLOZ server.

bizId

A unique business ID for tracing purpose. For example, the sequence ID from the merchant's business-related database.

Note: The ZOLOZ server does not perform uniqueness check on the value of this field. For better tracking, it is strongly recommended to enable the merchant server to guarantee the uniqueness of the business ID.

userId

Merchant user ID, or other identifiers that can be used to identify a specific user, for example, mobile phone number, email address and so on. It is strongly recommended to pre-desensitize the value of the userId field, for example, by hashing the value.

Product Type

Product type, including Real ID, ID recognition, Face capture, Face compare, etc.

Time

The time the case was searched.

ID Number

The ID number. 

TransactionId Suffix

The suffix tied to the transactionId.

Doc Type

The type of ID. 

Deleted Remark

Whether private data has been deleted. 

Result

Product Results: 

  •  ALL: The sum of all product results, including the following seven results below. 
  • Success: Authentication succeeded.
  • Failure: Authentication failed. This may be due to a failed ID or face verification, or risk control processing. 
  • Pending: Authentication is pending. 
    Note: This is a final response, and you are encouraged to view the application manually and then decide if the transaction should pass or not. If you encounter any issues during your review, please contact ZOLOZ's technical support. 
  • InProcess: Authentication is in progress. There is a certain delay during this state, and InProcess will change to VoidTimeout after a certain period of time. 
  • VoidTimeout: Authentication timeout. 
  • VoidCancelled: Authentication cancelled. 
  • Incomplete: This result is no longer in use, please ignore. 

Export Results

Support exporting case search results to meet your personalized data analysis needs. You can export up to 20,000 records. 

Case search result details

In the case search result list, click View Detail on the right of the specified case to view the product’s specific result content. This article introduces the product result detail page of Real ID as an example, and includes the following five major elements:

Basic Information

Picture 4.png

Displays the basic information for a record, including the following:

  • User ID: userId. Merchant user ID, or other identifiers that can be used to identify a specific user.
  • Business ID: bizId. A unique business ID for tracing purpose. For example, the sequence ID from the merchant's business-related database.
  • Transaction ID: transactionId. A unique transaction ID that is generated by the ZOLOZ server.
  • Creation Time: The time when the transaction was created
  • Completion Time: Time of completion
  • Deleted Remark: Whether private data has been deleted
  • Device ID: Device identification number
  • OS: The system type of the user's device (if any)
  • Model: Phone brand information (if any)

Total Result

Display the overall business results of Real ID product and the results of each sub-module.

Picture 5.png

The ZOLOZ server compares and verifies the submitted ID photo and face selfie, and then returns the final result to the user in the form of Success, Pending and Fail.

  • Success: Authentication passed. Both the ID and face are authentic, and the comparison is consistent. 
  • Fail: Authentication failed. There is a high risk present in this authentication e.g. the ID photo and face self are not of the same person; or the live face detection does not pass.
  • Pending: There are certain risks associated with this authentication and a second manual audit is required. The reasons for Pending include the document anti-counterfeit detection not passing; or that the face and document comparison score is not high enough and only approaches the threshold.

Document Verification Result
Displays sub-result details of the document module in Real ID. This includes document image display, document quality and classification test results, anti-counterfeit test results, and user-specific anti-counterfeit test results, document type, and document OCR recognition results. Please see checkresult for the relevant field descriptions.

Face Verification Result
Displays sub-result details of the face module in Real ID. This includes face image display, live face detection result, face image quality detection result, and face authentication comparison result. Please see checkresult for the relevant field descriptions.

Risk Control Result
Displays sub-result details of the risk policy module in Real ID. Contains the specific type of risk policy for the current transaction. When the ID Network or blacklist risk module is hit, the specific details of the hit will be displayed. Please see checkresult for the relevant field descriptions.