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.
ImportantThe 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
NoteBenefits 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.comInternal endpoint:
cloudauth-intl-vpc.ap-southeast-1.aliyuncs.com
Asia Pacific SE 5 (Jakarta)
Public endpoint:
cloudauth-intl.ap-southeast-5.aliyuncs.comInternal endpoint:
cloudauth-intl-vpc.ap-southeast-5.aliyuncs.com
China (Hong Kong)
Public endpoint:
cloudauth-intl.cn-hongkong.aliyuncs.comInternal endpoint:
cloudauth-intl-vpc.cn-hongkong.aliyuncs.com
Asia Pacific SE 3 (Kuala Lumpur)
Public endpoint:
cloudauth-intl.ap-southeast-3.aliyuncs.comInternal endpoint:
cloudauth-intl-vpc.ap-southeast-3.aliyuncs.com
Online debugging and integration
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
Transaction ID storage: The
TransactionIdis 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.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.
Conditions for returning the authentication image: The authentication image is returned only if
IsReturnImage=Yand the face scan is successful. Because the Base64 content is large, keep the default valueNif you do not need to display or store the image.Logic for determining the authentication result:
Code=Successonly indicates that the API call was successful. The final authentication result is determined by theResult.PassedandResult.SubCodefields.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, | These fields can be returned in both integration modes, depending on the verification flow and InitializeV2 configuration. |
Web SDK-specific |
| 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 |
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 | |
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. | | |
Result.ExtInfo | String | Other verification information, which mainly includes the actual fallback method for mobile H5 verification. For more information, see Result.ExtInfo. | | |
Result.ExtIdInfo
Parameter | Type | Description | Example |
ocrIdPassed | String | The final result of the document OCR stage:
| N |
ocrDocType | String | Returned only when the | 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 | |
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). | |
ocrStandardData | String | Standardized document OCR field information. Note Returned only if this ID type is supported and | |
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 | Base64 format |
ocrIdPassed | String | The OCR result for the current document page:
| 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. | |
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.
| |
Result.ExtInfo
Parameter | Type | Description |
procedurePriority | String | The actual fallback method used for mobile H5 verification:
|
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. |