ZOLOZZOLOZDOCS

RealID Deeper Upgrade Guide

After purchasing the Deeper product, you can follow this guide to complete the Deeper upgrade operation in RealID.

Deeper Function Overview

Deeper is the end-to-cloud integrated AIGC detection capability offered by ZOLOZ. It combines multi-modal algorithms, terminal injection security detection capabilities, and a rich set of dynamic risk control strategies to identify AIGC risks in the identity verification process from multiple dimensions.

Deeper is not an independent product; rather, it enhances features in products like RealID, Face Capture, and Connect. For more information about Deeper, please refer to What is Deeper.

Deeper Upgrade Guide

  1. Purchase Deeper Products
  2. Upgrade Native SDK Version
  • From version 1.4 onwards, the Native SDK includes enhanced terminal control capabilities. To fully utilize the functionalities of Deeper, it is recommended to upgrade your Native SDK to version 1.4 or above. For specific version numbers, please refer to the Release Notes.
  • Note: SDK versions 1.4 and above do not require additional NearX dependencies. If you previously used NearX features, you must remove the NearX implementation lines after the upgrade to avoid execution conflicts. Refer to the App SDK-mode integration.
  1. Configure deeperMode Input Parameter:
    By enabling the Deeper functionality through deeperMode, the parameters serviceLevel and operationMode will become inactive, and the detailed product config parameters will take effect. The table below provides recommended standard configurations for detailed product config parameters. The suggested values are for reference only, and customers can set them according to their actual business needs. For more information, please refer to the initialize API.

Field name

Description

Example

docUiType

This parameter refers to methods for taking ID photos. The values are as follows:

  • 1: Self-capture. Users need to manually take ID photos, and it only has basic anti-spoofing capabilities.
  • 2: Deep-scan, only for Native SDK. ZOLOZ SDK automatically aligns and captures ID photos, and it has advanced anti-spoofing capabilities such as intercepting printed color images.
  • 3: Auto-scan, only for Web SDK. ZOLOZ SDK automatically aligns and captures ID photos, and it only has basic anti-spoofing capabilities. Auto-scan is recommended for WEB SDK because Auto-scan offers a better user experience and higher quality of document image compared to Self-scan.
  • 4: Trace-scan, only for Native SDK. ZOLOZ SDK automatically captures ID photos when the document is detected within the camera range. It can improve user experience, but it only has basic anti-spoofing capabilities.
  • 5: Multi-angle, only for HKID in Web SDK. Users need to take two document photos from different angles. For the first photo, make the camera directly face the ID document and captures its photo. For the second, incline the ID document 30° against the camera and capture its photo.

Note: The Deeper feature relies on two collection methods: Deep-scan and Auto-scan. When the Deeper feature is enabled, please select the appropriate collection method based on your actual application scenario to ensure optimal detection performance. Use Deep-scan for the Native SDK and Auto-scan for the Web SDK. The detection effect will be greatly impacted if these two modes are not selected.

  • Native：2
  • H5：3

spoofMode

This parameter refers to document anti-spoofing levels, defined as follows:

  • CLOSED: All algorithms are not applied. You can use this anti-spoofing detection mode in the test phase so that the algorithms and risk control rules do not affect the testing process.
  • STANDARD: A standard recommended level is applied.
  • LOOSE: Reserved value, not currently supported for use.
  • STRICT: Reserved value, not currently supported for use.

STANDARD

livenessMode

Specifies the liveness level for face liveness detection check. The following values are supported:

  • CLOSED: All algorithms are not applied. You can use this liveness detection mode in the test phase so that the algorithms and risk control rules do not affect the testing process.
  • STANDARD: A standard recommended level is applied.
  • LOOSE: A relatively looser level is applied. You can use this liveness detection mode in low-risk scenarios.
  • STRICT: A relatively stricter level is applied. You can use this liveness detection mode in high-risk scenarios.

STANDARD

actionCheckItems

User actions to be detected. For better user experience, it is not recommended to use two or more actions. The following values are supported:

  • FACEBLINK: Requires the user to blink their eyes.
  • MOUTHOPEN: Requires the user to open their mouth once.
  • HEADSHAKE: Requires the user to shake their head. Left or right headshake will be specified for the user to perform.
  • HEADLOWER: Requires the user to lower their head once.
  • HEADRAISE: Requires the user to raise their head once.

FACEBLINK+1 other action (for example, MOUTHOPEN, HEADSHAKE, HEADLOWER)

actionRandom

Specifies whether user actions specified in actionCheckItems are in random order to be detected. Valid values include:

  • Y: Random
  • N: Not random, action detection is performed following the order in actionCheckItems.

Y

actionFrame

This parameter refers to capturing other frame pictures, defined as follows:

  • EYECLOSE: Set this value to return closed-eye frames collected during the blink detection method.

EYECLOSE

riskMode

This parameter refers to multi-dimensional risk control rule verification in RealID. It is used to intercept suspicious transactions. The values are as follows:

  • CLOSED: All algorithms about risk detection are not applied. You can use this risk detection mode in the test phase so that the algorithms and risk control rules do not affect the testing process.
  • STANDARD: A standard recommended level is applied.
  • LOOSE: Reserved value, not currently supported for use.
  • STRICT: Reserved value, not currently supported for use.

STANDARD

  1. View the related results of Deeper.
    Check the business results corresponding to the Deeper feature in the checkresult API. The relevant output parameters include deeperFaceResult, deeperFaceResultDescription, deeperDocResult, deeperDocResultDescription, deeperRiskResult, and deeperRiskResultDescription. For more details, refer to the checkresult API.

Relationship Between antiInjectionMode and Deeper

In the RealID initialize API, the antiInjectionMode parameter served as a trial feature switch for detecting injection attacks. As of June 2024, this parameter is no longer effective. ZOLOZ has now launched the new Deeper product, which includes capabilities for both Deepfake detection and injection attack detection. To enable these features, you need to purchase the Deeper product and set the deeperMode parameter. Please refer to the Deeper Upgrade Guide.

Note:

  • For existing customers still using the antiInjectionMode, ZOLOZ will retain this parameter for a period to ensure API compatibility and a smooth transition.
  • If existing customers enable the ​deeperMode ​parameter, ZOLOZ will prioritize using ​deeperMode​, and ​antiInjectionMode ​will become invalid.