All Products
Search
Document Center

ID Verification:Credential fraud detection

Last Updated:Jun 02, 2026

Analyze credential images to detect forgery, tampering, screen captures, and recaptures using the CredentialVerifyIntl API.

API description

  • Operation name: CredentialVerifyIntl

  • Description: Analyzes credential images to detect forgery, tampering, screen captures, and recaptures.

  • Request method: POST

  • Transport protocol: HTTPS

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

  • 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.

    Singapore

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

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

Note
  1. Credential detection is AI-based with approximately 90% accuracy on internal test data. Actual accuracy varies by scenario.

  2. Detection is more effective on native camera photos than on digitally synthesized images.

  3. Do not rely solely on detection results to verify credential authenticity. Use them to supplement or accelerate manual reviews.

  4. Common use cases include finance, payment acquiring, and e-commerce merchant onboarding. For other scenarios, contact your account manager.

Online debugging and integration

Note

Before you debug or integrate, read the Debug and integrate server-side APIs with OpenAPI guide to understand how to call APIs on the OpenAPI platform and how to obtain the SDK.

You can debug this operation directly in OpenAPI Explorer. You can also generate SDK sample code for this operation.

Request parameters

The image specified by the ImageUrl or ImageFileObject parameter must meet the following requirements:

  • Image format: PNG, JPG, JPEG, BMP, and WebP.

  • Image dimensions: Height and width must be greater than 15 px and less than 8192 px. Aspect ratio must be less than 50.

    Note

    For best results, use images with height and width both greater than 500 pixels.

  • Image size: URL images cannot exceed 10 MB. ImageFileObject images cannot exceed 3 MB.

    Note

    Large images increase response time. Keep images under 3 MB.

Name

Type

Required

Description

Example

CredType

String

Yes

Credential type:

  • 03: Business qualification

  • 04: Transactional credential

03

CredName

String

Yes

Credential name (use the numeric code):

  • Starts with 03, business qualification:

    • 0301: Business license of the Chinese mainland

  • Starts with 04, transactional credential:

    • 0401: Bank statement

    • 0402: Payslip

    • 0403: Utility bill

    • 0405: Credit card bill

    • 0499: Other

Note

To support more credential types, contact your account manager.

0301

ProductCode

String

Yes

Call mode:

  • ANTI_FAKE_CHECK: Image quality and tampering detection.

ANTI_FAKE_CHECK

ImageUrl

String

Yes

Important

Specify either imageUrl or ImageFileObject.

The URL of the image.

https://example.com/test.jpg

ImageFileObject

InputStream

The image file stream.

To upload an image this way, you must call the Advance API and pass a valid InputStream object. For more information, see Special scenario: Configure the Advance API for file uploads.

The InputStream object of the image

Response parameters

Name

Type

Description

Example

RequestId

String

The request ID.

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

Code

String

Return code.

Important
  • Indicates whether the API call succeeded. Return code definitions are listed in the return codes section below.

  • For the business verification result, check the fields in ResultObject.

Success

Message

String

A detailed description of the return code.

success

ResultObject

Result

String

  • 0: Low risk

  • 1: High risk

  • 2: Suspicious

1

RiskTag

String

Risk tags, comma-separated. Valid values:

  • PS: Photoshopped image

  • SCREEN_PHOTO: screen capture

  • SCREENSHOT: Screen capture

  • ORIGINAL_PHOTO: Non-original image

PS

RiskScore

Map<String,String>

Risk score for each detected tag. Ranges from 0 (no risk) to 1 (risk detected).

{
  "PS": "0.0211",
  "SCREEN_PHOTO": "0.0101",
  "SCREENSHOT": "0.0521",
  "ORIGINAL_PHOTO": "0.0861"
}

MaterialInfo

String

Other information. This is a reserved field.

Return codes

HTTP status code

Code

Description

200

Success

Success.

400

MissingParameter

A required parameter is missing.

400

Forbidden.ExceptionRepeatedInvoke

Duplicate request detected.

401

InvalidParameter

The parameter is invalid.

401

UnqualifiedPhoto

The provided image is not usable.

401

ToolargeImage

The provided image is too large.

401

DataDuplication

The data is duplicate.

403

Forbidden.AccountAccessDenied

Make sure that you have activated ID Verification and your account has no overdue payments.

403

Forbidden.RAMUserAccessDenied

RAM user requires AliyunAntCloudAuthFullAccess permission.

500

Forbidden.ExceptionDataSource

Authoritative data source service error.

500

InternalError

Internal system error. Contact support for troubleshooting.