All Products
Search
Document Center

ID Verification:eKYC_MIN.

Last Updated:Jul 10, 2026

This topic describes how to integrate ID Verification using server-side API calls.

API information

  • API operation: EkycVerifyV2

  • Request method: HTTPS POST

  • Operation description: You can call this operation and specify information such as an image to perform an electronic KYC (eKYC) verification.

  • QPS limit: Each API has a dedicated QPS limit. For details, see QPS limits of ID Verification server-side APIs.

  • Service endpoints:

    Note
    • Benefits of internal network access: An internal network enables private communication between Alibaba Cloud services in the same region. If your application server is also in the same region, use the internal network endpoint to access the ID Verification service for a more secure and stable connection. 

    • Optimization for overseas access: Network conditions outside the Chinese mainland can be complex. To reduce latency and minimize request failures, optimize your integration by following the best practices in Server-side Network Latency Analysis and Optimization.

    China (Hong Kong)

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

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

Online debugging and integration

Note

Before you debug or integrate, read the Use OpenAPI guide to understand how to call APIs on the OpenAPI platform and how to obtain the SDK.

In OpenAPI Explorer, you can directly run this API for debugging and generate an SDK code example.

Image requirements

  • Supported image formats: JPG, JPEG, and PNG.

  • Image size: Recommended 50–100 KB; maximum 1 MB.

  • Image resolution: Must be at least 640 x 480 pixels (height x width) and no more than 1920 x 1080 pixels. For optimal results, we recommend scaling the shorter side to 720 pixels and using a compression ratio greater than 0.9. Images must be in portrait orientation (height greater than width), as landscape images may reduce detection accuracy.

    Note

    Converting an image to base64 format typically increases its data size. If you pass the image as a base64-encoded string, ensure the original image is no larger than 0.6 MB to stay within the 1 MB data transfer limit.

  • Image quality recommendations:

    • The face must be complete, clear, and unobstructed. The subject should be facing the camera directly. We recommend using images from a front-facing camera.

    • The face must occupy more than 60% of the total image area. Smaller faces may reduce detection accuracy.

    • If an image contains multiple faces, the algorithm processes the largest one by default. For best results, avoid images with multiple faces.

Request parameters

Parameter

Type

Required

Description

Example

ProductCode

String

Yes

The solution that you want to use. Set the value to eKYC_MIN.

eKYC_MIN

SceneCode

String

No

A custom ID for the verification scenario, used to query related records in the ID Verification console. The ID can be up to 10 characters long and can contain letters, digits, and underscores (_).

1234567890

MerchantBizId

String

Yes

The unique identifier of your business, which is used for troubleshooting. You can specify a custom value that is 32 characters in length and contains letters and digits. Make sure that the value is unique.

e0c34a77f5ac40a5aa5e6ed20c35****

MerchantUserId

String

Yes

The ID of a customer. You can specify a custom value, such as a mobile phone number or an email address. Before you specify a custom value, we recommend that you perform data masking. For example, you can perform hashing.

Y

DocType

String

Yes

The document type. You can specify an 8-digit value to uniquely identify a document type. For more information, see Document types.

01000000

DocName

String

No

The real name of the customer.

Note

When Authorize=T and the document type is Mainland China Resident ID Card, you must provide at least one of the following two parameter groups: 

  • DocName and DocNo); 

  • IdOcrPictureBase64 or IdOcrPictureUrl.

If the preceding conditions are met, the following logic applies. If you provide only DocName and DocNo (without uploading a document image), the system performs only an identity information consistency check and does not verify the authenticity of the face image. If a document image is provided, the system uses algorithms to detect basic presentation attacks, such as screen recapture, on the document and face images. This process is suitable for low-risk business scenarios.

Alice

DocNo

String

No

The ID card number of the customer.

Note

When Authorize=T and the document type is Mainland China Resident ID Card, you must provide at least one of the following two parameter groups: 

  • DocName and DocNo); 

  • IdOcrPictureBase64 or IdOcrPictureUrl.

If the preceding conditions are met, the following logic applies. If you provide only DocName and DocNo (without uploading a document image), the system performs only an identity information consistency check and does not verify the authenticity of the face image. If a document image is provided, the system uses algorithms to detect basic presentation attacks, such as screen recapture, on the document and face images. This process is suitable for low-risk business scenarios.

411xxxxxxxxxxx0001

IdOcrPictureBase64

String

No

Note

You can choose any one of the three upload methods.

The Base64-encoded document image.

Note

If you upload an image by using the IdOcrPictureBase64 parameter, check the size of the image. Do not specify an image whose size is excessively large.

Base64-encoded content

IdOcrPictureUrl

String

The URL of the document image. The URL can be an HTTP or HTTPS URL that can be accessed over the Internet.

https://***

IdOcrPictureFile

InputStream

ID document image file stream.

For specific integration methods, see File uploads with the Advance interface.

FacePictureBase64

String

No

Note

You can choose any one of the three upload methods.

The Base64-encoded face image.

Note

If you upload an image by using the FacePictureBase64 parameter, check the size of the image. Do not specify an image whose size is excessively large.

Base64-encoded content

FacePictureUrl

String

The URL of the face image. The URL can be an HTTP or HTTPS URL that can be accessed over the Internet.

https://***

FacePictureFile

InputStream

File stream of the portrait image.

For specific integration methods, see File uploads with the Advance interface.

Crop

String

No

Specifies whether to crop the face from the image:

  • T: Allows cropping.

  • F: Disallows cropping (Default)

F

Authorize

String

No

Specifies whether to enable verification against an official database:

  • T: Enables verification.

  • F: Disables verification (Default)

Note

This parameter supports only second-generation ID cards for residents in the Chinese mainland.

F

IdThreshold

String

No

Sets the mode for the OCR quality check. Valid values are:

  • 1: strict mode

  • 2: loose mode

  • 3 (default): Disables the quality check.

3

Document types

DocType

Document

01000000

Passports (global)

00000006

ID cards (Hong Kong (China)) (2003 version)

00000008

ID cards (Hong Kong (China)) (2018 version)

00000007

Exit-entry Permit for Travelling to and from Hong Kong and Macao

00000009

Mainland Travel Permit for Hong Kong and Macao Residents

000000011

ID cards (Macao (China))

000000012

Mainland Travel Permit for Taiwan Residents

00000001

Second-generation ID cards for residents in the Chinese mainland

Response parameters

Parameter

Type

Description

Example

HTTP Status Code

Integer

The HTTP status code.

200

HTTP Body

RequestId

String

The request ID.

130A2C10-B9EE-4D84-88E3-5384FF0****

Code

String

Return code: For more information, see Server-side HTTP status codes.

Success

Message

String

A detailed description of the returned error code.

success

Result.Passed

String

The final verification result. Valid values:

  • Y: Passed

  • N: Failed

Y

Result.SubCode

String

A description of the verification result. For more information, see ResultObject.SubCode error codes.

200

Result.ExtFaceInfo

String

The result of face liveness verification. The value is in the JSON format. For more information, see ExtFaceInfo.

{
  "faceAttack": "N",
  "faceComparisonScore": 52.57,
  "facePassed": "N",
  "authorityComparisonScore": 80.39
}

Result.ExtIdInfo

String

The result of document verification.

The value is in the JSON format. For more information, see ExtIdInfo.

{
  "ocrIdInfo": {
    "expiryDate": "",
    "originOfIssue": "National Immigration Administration",
    "englishName": "LI SI",
    "sex": "Male",
    "name": "LI SI",
    "idNumber": "H11111112",
    "issueDate": "2013-01-02",
    "birthDate": "1990-02-21"
  },
  "ocrIdPassed": "N",
  "spoofInfo": {
    "spoofResult": "Y",
    "spoofType": [
      "SCREEN_REMARK"
    ]
  }
}

Codes of ResultObject.SubCode

Code

Billed

Description and cause

200

Yes

The customer passed the verification.

201

Yes

The name does not match the ID card in the official database. The information about the customer is incorrect or fake. The customer can check the information and perform the verification again.

Note

This error code is returned only when the certificate type verified by the product is a Chinese ID card and the authoritative verification feature is enabled.

202

Yes

The information about the customer cannot be queried in the official database. We recommend that you reserve an entry point to manual review.

Note

This error code is returned only when the certificate type verified by the product is a Chinese ID card and the authoritative verification feature is enabled.

203

Yes

No image is queried or the image is unavailable. Possible cause: No library image is saved in the authoritative comparison source. We recommend that you reserve an entry point to manual review.

204

Yes

The document face does not match the live face. A possible reason is that the faces belong to different live persons or the quality of the live face is poor.

205

Yes

The results of liveness detection show risks.

207

Yes

The uploaded face does not match the face in the official database. This could mean the faces belong to different people or the quality of the submitted face image is poor.

Note

This error code is returned only when the certificate type verified by the product is a Chinese ID card and the authoritative verification feature is enabled.

209

Yes

An exception occurs in the authoritative comparison source.

Note

This error code is returned only when the certificate type verified by the product is a Chinese ID card and the authoritative verification feature is enabled.

212

Yes

The results of anti-counterfeiting detection on documents show risks, such as photos and copies of documents and documents that are tampered with.

ExtFaceInfo

Parameter

Type

Description

Example

facePassed

String

Indicates whether the customer passed the face liveness verification. Valid values:

  • Y: Passed

  • N: Failed

Y

faceComparisonScore

Double

The score of comparison between the collected face and document face. Valid values: 0 to 100.

99.99

faceAttack

String

Indicates if a liveness attack was detected on the submitted face:

  • Y: An attack was detected.

  • N: No attack was detected.

N

authorityComparisonScore

Double

The comparison score between the collected face and the authoritative comparison source. Valid values: 0 to 100.

99.99

ExtIdInfo

Parameter

Type

Description

Example

idPassed

String

Indicates whether the customer passes the document verification. Document verification also refers to document optical character recognition (OCR). Valid values:

  • Y: Passed

  • N: Failed

N

ocrIdInfo

String

The fields that are returned by document verification.

Note

If the document verification failed, this parameter is empty.

{
  "expiryDate": "",
  "originOfIssue": "National Immigration Administration",
  "englishName": "LI SI",
  "sex": "Male",
  "name": "LI SI",
  "idNumber": "H11111112",
  "issueDate": "2013-01-02",
  "birthDate": "1990-02-21"
}

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 defaults 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"]
}