All Products
Search
Document Center

ID Verification:CheckResult

Last Updated:Oct 23, 2026

This topic describes how to call the CheckResult API to retrieve the verification results for the ID_OCR_PRO solution.

API

  • API name: CheckResult

  • Request method: HTTPS POST

  • Description: When the server-side receives a callback indicating that authentication is complete, call this API to retrieve the corresponding authentication status and information. This callback is sent when the client result code is 1001 or 1002. For more information, see Native SDK client result codes and sub-codes.

    Important

    The ID Verification service stores verification results for 30 days by default. Please retrieve them within this period, as they are automatically deleted afterward.

  • QPS limit: Each API has its own QPS limit. For more information, see QPS limits of ID Verification server-side APIs.

  • Service endpoints

    Note
    • Benefits of internal network access: An internal network is a private communication network connecting Alibaba Cloud products within the same region. If your application server is deployed in the same region, use the internal endpoint to access the ID Verification service for enhanced security and stability.

    • Optimizing overseas access: Overseas network environments can be complex. Refer to Optimize server network latency to tune your integration and reduce network latency and request failures.

    Asia Pacific SE 1 (Singapore)

    • Public endpoint: cloudauth-intl.ap-southeast-1.aliyuncs.com

    • Internal endpoint: cloudauth-intl-vpc.ap-southeast-1.aliyuncs.com

    Asia Pacific SE 5 (Jakarta)

    • Public endpoint: cloudauth-intl.ap-southeast-5.aliyuncs.com

    • Internal endpoint: cloudauth-intl-vpc.ap-southeast-5.aliyuncs.com

    China (Hong Kong)

    • Public endpoint: cloudauth-intl.cn-hongkong.aliyuncs.com

    • Internal endpoint: cloudauth-intl-vpc.cn-hongkong.aliyuncs.com

    Asia Pacific SE 3 (Kuala Lumpur)

    • Public endpoint: cloudauth-intl.ap-southeast-3.aliyuncs.com

    • Internal endpoint: cloudauth-intl-vpc.ap-southeast-3.aliyuncs.com

Online debugging and integration

Note

Before debugging and integration, read the Use OpenAPI document to learn how to call APIs on the OpenAPI platform and obtain the SDK.

You can use OpenAPI Explorer to directly call this API for debugging and generate SDK code examples.

Usage notes

  1. Transaction ID storage: The TransactionId is the only trusted identifier for a server-side verification record. You must bind it to a business ID and store it persistently on your server.

  2. Log retention and compliance: Verification result logs are stored for 30 days by default and are automatically deleted afterward. You must query the results within this period and store the relevant data according to your compliance requirements.

  3. Conditions for returning the authentication image: The authentication image is returned only if IsReturnImage=Y and the face scan is successful. Because the Base64 content is large, keep the default value N if you do not need to display or store the image.

  4. Logic for determining the authentication result: Code=Success only indicates that the API call was successful. The final authentication result is determined by the Result.Passed and Result.SubCode fields.

  5. Fault tolerance for OCR field parsing: The OCR fields, number of document pages, and face attributes may vary based on the document type, regional capabilities, and SDK configuration. Your client must handle missing or newly added fields during parsing.

Field distribution

The CheckResult main return structure, liveness result, and OCR result fields are the same for both App SDK and Web SDK integrations.

Category

Field

Description

Common output

General response, authentication result, ExtIdInfo and its sub-fields

These fields can be returned in both integration modes, depending on the verification flow and InitializeV2 configuration.

Web SDK-specific

procedurePriority

Returns the actual fallback policy when a compatibility fallback occurs during verification.

App-specific

None

None

Request parameters

Parameter

Type

Required

Description

Example

MerchantBizId

String

Yes

A unique business identifier for the merchant, consisting of 32 letters and digits. This value must be the same as the one used in the InitializeV2 request.

e0c34a77f5ac40a5aa5e6ed20c35****

TransactionId

String

Yes

The unique authentication identifier returned by a successful init API call. To prevent tampering, always retrieve this value from your server-side storage and do not trust the value sent from the client-side.

hksb7ba1b28130d24e015d6********

IsReturnImage

String

No

Specifies whether to return verification image data (including document photos):

  • Y: Return

  • N: Do not return (Default)

Y

Response parameters

Parameter

Type

Description

Example

HTTP Status Code

Integer

The HTTP status code.

200

HTTP Body

RequestId

String

The request ID, used for troubleshooting.

130A2C10-B9EE-4D84-88E3-5384FF039795

Code

String

The server-side response code. For more information, see Server-side HTTP Status Codes.

Success

Message

String

A detailed description of the response code.

success

Result.Passed

String

The final verification result:

  • Y: Passed

  • N: Not Passed

Y

Result.SubCode

String

A detailed code for the verification result. For more information, see Result.SubCode Subcodes.

200

Result.ExtIdInfo

String

Document OCR and anti-spoofing results. For more information, see Result.ExtIdInfo.

{
  "ocrIdInfoData": {
    "01": {
      "ocrIdInfo": {
        "id_number": "083****767",
        "full_name": "MAC *** NG",
        "nationality": "Việt Nam",
        "date_of_expiry": "",
        "date_of_birth": "10/10/1999",
        "sex": "Nam"
      },
      "ocrIdPassed": "Y",
      "spoofInfo": {
        "spoofResult": "N"
      }
    },
    "02": {
      "ocrIdInfo": {
        "date_of_issue": "10/10/2022",
        "personal_identification": "Sẹo **** phải"
      },
      "ocrIdPassed": "Y",
      "spoofInfo": {
        "spoofResult": "N"
      }
    }
  },
  "ocrIdPassed": "Y"
}

Result.ExtInfo

String

Other verification information, which mainly includes the actual fallback method for mobile H5 verification. For more information, see Result.ExtInfo.

{
  "procedurePriority": "keep"
}

Result.ExtIdInfo

Parameter

Type

Description

Example

ocrIdPassed

String

The final result of the document OCR stage:

  • Y: Passed

  • N: Not Passed

N

ocrDocType

String

Returned only when the DocType parameter in InitializeV2 is set to a specified country/region or a specified country/region and document category. It serves as the precise document code automatically identified by the system in auto-classification mode.

CHN01001

ocrIdInfoData

Map<String,Object>

Detailed results for each page of the document. The key is the page number, and the value is described in ocrIdInfoData.{page} single-page fields.

The numbers 01 and 02 represent the front and back (or secondary page) of the document, respectively.

{
  "01": {
    "ocrIdPassed": "Y",
    "idImage": "Base64_placeholder",
    "ocrIdInfo": {
      "expiryDate": "2030.01.01",
      "englishName": "SUN, xxx",
      "originOfIssue": "National Immigration Administration of the People's Republic of China",
      "placeOfIssue": "Beijing",
      "sex": "Male",
      "name": "Sun x",
      "idNumber": "CGxxxxxxxx",
      "issueDate": "2024.12.01",
      "birthDate": "1992.12.01"
    },
    "spoofInfo": {
      "spoofResult": "N",
      "spoofType": []
    }
  }
}

ocrIdEditInfo

String

This field contains the document OCR field information that the user submitted after editing it on the OCR result page. This field is returned when the client is configured to enable the OCR result editing page (ShowOcrResult).

{
  "expiryDate": "2026-01-02",
  "originOfIssue": "Exit-Entry Administration of the Ministry of Public Security",
  "englishName": "ZHANG SAN",
  "sex": "Male",
  "name": "Zhang San",
  "idNumber": "H11111115",
  "issueDate": "2013-01-02",
  "birthDate": "1990-02-21"
}

ocrStandardData

String

Standardized document OCR field information.

Note

Returned only if this ID type is supported and OcrValueStandard is set to 1.

{
    "given_name_s": "HYUNEUI",
    "surname_s": "MUN",
    "date_of_expiry_s": "2028-02-08",
    "date_of_birth_s": "1988-10-26",
    "sex_s": "M"
}

ocrIdInfoData.{page} single-page fields

Parameter

Type

Description

Example

idImage

String

The OCR-processed image of the ID document in Base64 format. This is returned only when IsReturnImage=Y and the OCR operation succeeds.

Base64 format

ocrIdPassed

String

The OCR result for the current document page:

  • Y: Passed

  • N: Not Passed

N

ocrIdInfo

String

The OCR field information for the current document page. This field is empty if OCR fails. The specific fields vary by document type.

For a list of fields, see Document OCR Fields.

{
  "expiryDate": "2030.01.01",
  "englishName": "SUN, xxx",
  "originOfIssue": "National Immigration Administration of the People's Republic of China",
  "placeOfIssue": "Beijing",
  "sex": "Male",
  "name": "Sun x",
  "idNumber": "CGxxxxxxxx",
  "issueDate": "2024.12.01",
  "birthDate": "1992.12.01"
}

spoofInfo

String

The result of spoof detection, including the risk decision and risk types:

Note

Card spoofing detection is enabled only when IdSpoof = Y in the Initialize request.

Otherwise, spoofResult sets to N, and spoofType is empty.

  • spoofResult:

    • Y: Risk detected

    • N: Normal

  • spoofType:

    • SCREEN_REMARK: screen recapture

    • PHOTO_COPY: photocopy

    • TAMPER: tampering

    • SHORTCUT: screenshot

{
 "spoofResult": "Y",
 "spoofType": ["SCREEN_REMARK"]
}

Result.ExtInfo

Parameter

Type

Description

procedurePriority

String

The actual fallback method used for mobile H5 verification:

  • keep: No fallback was triggered.

  • url: A fallback to a URL occurred.

Result.SubCode subcodes

Subcode

Charged

Description

200

Yes

Verification passed.

212

Yes

[Document solution] A risk was detected during the document anti-spoofing check. This can be caused by high-risk activities such as a screen recapture, digital tampering, or using a photocopy.