Glossary

The following is a description of technical terms frequently shown in “Behavior Verification” products.

captcha_id

Verify public key. A 32-bit string, a unique identification of a captcha, visible to the public and used to distinguish verification modules on different pages. ID is created and obtained on the GeeTest dashboard. Please deploy different captcha IDs in each verification scenario.

captcha_key

Verify private key. A 32-bit string that uniquely corresponds to the public key of the captcha. This private key will be used for data encryption in the verification service to ensure safe verification. After creating an ID in the captcha background, the corresponding KEY will be generated. Please keep the registered private key properly.

lot_number

Serial number of verification events, which is the unique identification of a single verification event, and is used to ensure the uniqueness of a single verification event and prevent playback. This serial number is obtained by dynamic registration from the GeeTest server through the deployed SDK, and each serial number is valid for about 10 minutes.

sign_token

User signature, users need to use serial number and key to sign during the second validation. The validation process will not begin until the secondary validation interface confirms that the signature is correct.

Secondary validation

When the user passes the captcha in the front-end interface, a batch of parameters related to the captcha will be generated, and the user’s business request will bring these parameters, and the background business interface will upload these parameters to the GeeTest secondary verification interface to confirm the validity of the user’s verification this time.

Offline mode

When the service is abnormal, the front-end will load a local verification form that passes at one point to ensure that the front-end will not block the normal interactive process of the page. In the secondary validation of the server, the customer needs to deal with the abnormality of the service (request timeout, request rejection, non-200 status code) to ensure that the secondary validation will not block the business process.