KYC China

KYC verification services for Chinese citizens.

Verify identity, look up mobile number info, and assess risk using government and telecom records.

Endpoints

Endpoint	Description
POST /kyc/cn/identity	Verify a person's identity (document-based or mobile-based)
POST /kyc/cn/mobile	Mobile number lookups — carrier info and geolocation
POST /kyc/cn/risk	Risk assessment — anti-fraud scoring and police blacklist

Verify Identity

post

Verify a person's identity using government records and/or telecom registration data.

All verification types return a consistent pass/fail result (consistent boolean).

Document-based (name + ID number):

• two-factor: Basic — verify name matches ID number

• four-factor: Enhanced — also verify ID card validity dates

• image: Biometric — also compare a facial photo

Mobile-based (mobile number + identity):

• name-mobile: Verify mobile number is registered to this name

• id-mobile: Verify mobile number is registered to this ID number

• three-factor: Verify mobile, name, and ID number all match

Authorizations

ClientID & ClientSecret

x-client-idstringRequired

Client ID in x-client-id header.

x-client-secretstringRequired

Client Secret in x-client-secret header.

Body

application/json

typestring · enumRequired

The verification method to use:

• two-factor: Verify name matches ID number
• four-factor: Verify name, ID number, and ID card validity dates
• image: Verify name, ID number, and compare facial photo
• name-mobile: Verify mobile number is registered to this name
• id-mobile: Verify mobile number is registered to this ID number
• three-factor: Verify mobile, name, and ID number all match

Example: two-factorPossible values:

namestringOptional

Full legal name in Chinese characters. Required for two-factor, four-factor, image, name-mobile, three-factor.

Example: 李明

idNostringOptional

18-digit Chinese Resident Identity Card number. Required for two-factor, four-factor, image, id-mobile, three-factor.

Example: 110101199003076515Pattern: ^[0-9]{17}[0-9Xx]$

mobilestringOptional

11-digit Chinese mobile phone number. Required for name-mobile, id-mobile, three-factor.

Example: 13912345678Pattern: ^1[3-9][0-9]{9}$

frDatestringOptional

ID card issue date in YYYYMMDD format. Required when type is four-factor.

Example: 20200315Pattern: ^[0-9]{8}$

toDatestringOptional

ID card expiry date in YYYYMMDD format, or "长期" for permanent validity. Required when type is four-factor.

Example: 20400315

imgstringOptional

Base64-encoded facial photograph for biometric comparison. Required when type is image. Supported formats: JPEG, PNG. Recommended size: 300x400 pixels minimum.

Responses

200

Identity verification completed

application/json

successbooleanRequired

Whether the verification request was processed successfully

Example: true

consistentboolean · nullableOptional

Whether the provided information matches records.

• true: Information matches
• false: Information does not match
• null: Unable to verify (no records found)

Example: true

checkResultstringOptional

Raw verification result code ("1" = match, "-1" = no match)

Example: 1

messagestringRequired

Human-readable description of the verification result

Example: Identity information matches

400

Invalid request parameters

502

Upstream verification service error

post

/kyc/cn/identity

HTTPcURLJavaScriptPython

POST /kyc/cn/identity HTTP/1.1
Host: sandbox.staging-api.fill-easy.com
x-client-id: YOUR_API_KEY
x-client-secret: YOUR_API_KEY
Content-Type: application/json
Accept: */*
Content-Length: 65

{
  "type": "two-factor",
  "name": "李明",
  "idNo": "110101199003076515"
}

Two-Factor (name + ID)Four-Factor (name + ID + dates)Photo (name + ID + face)Name-Mobile (mobile + name)ID-Mobile (mobile + ID)Three-Factor (mobile + name + ID)

{
  "success": true,
  "consistent": true,
  "checkResult": "1",
  "message": "Identity information matches"
}

Mobile Number Lookup

post

Non-identity lookups keyed on a mobile phone number — carrier info and geolocation.

Types:

• attribution: Get the carrier, province, and city for a mobile number

• location-verify: Check the distance between a mobile user's location and a specified address

• location-query: Retrieve the city where the mobile user has been active

Location Types (for location-verify and location-query):

• 1: Common location — area with highest mobile activity (location-verify only)

• 2: Work location — activity during 7:00-19:00 on weekdays

• 3: Residential location — activity during 21:00-07:00

Authorizations

ClientID & ClientSecret

x-client-idstringRequired

Client ID in x-client-id header.

x-client-secretstringRequired

Client Secret in x-client-secret header.

Body

application/json

typestring · enumRequired

Lookup type:

• attribution: Look up carrier and location info
• location-verify: Check distance between mobile location and an address
• location-query: Get the city where the user is located

Example: attributionPossible values:

mobilestringRequired

11-digit Chinese mobile phone number

Example: 13912345678Pattern: ^1[3-9][0-9]{9}$

locationTypestring · enumOptional

Location category. Required for location-verify and location-query.

• 1: Common location (highest activity) — location-verify only
• 2: Work location (7:00-19:00 weekdays)
• 3: Residential location (21:00-07:00)

Example: 2Possible values:

citystringOptional

City name in Chinese. Required for location-verify.

Example: 北京

addressstringOptional

Full street address in Chinese. Required for location-verify.

Example: 朝阳区建国路88号

Responses

200

Mobile lookup completed

application/json

or

or

400

Invalid request parameters

502

Upstream verification service error

post

/kyc/cn/mobile

HTTPcURLJavaScriptPython

POST /kyc/cn/mobile HTTP/1.1
Host: sandbox.staging-api.fill-easy.com
x-client-id: YOUR_API_KEY
x-client-secret: YOUR_API_KEY
Content-Type: application/json
Accept: */*
Content-Length: 45

{
  "type": "attribution",
  "mobile": "13912345678"
}

Carrier AttributionVerify Work LocationQuery Residential City

{
  "success": true,
  "province": "广东",
  "city": "广州",
  "operator": "中国移动",
  "message": "Mobile number belongs to 中国移动 in 广州, 广东"
}

Risk Assessment

post

Compliance and blacklist checks — anti-fraud scoring and police records.

Types:

• anti-fraud: Assess fraud and gambling risk based on mobile number or ID number

• police: Check if a person is on the public security blacklist

Anti-Fraud Risk Levels: 0 None, 1 Low, 2 Medium, 3 High

Anti-Fraud Risk Types: 1 Fraud, 2 Gambling House, 4 Gambling Player, 8 Money Mule

Authorizations

ClientID & ClientSecret

x-client-idstringRequired

Client ID in x-client-id header.

x-client-secretstringRequired

Client Secret in x-client-secret header.

Body

application/json

typestring · enumRequired

Risk check type:

• anti-fraud: Fraud/gambling risk score (requires mobile and/or idNo)
• police: Police blacklist check (requires name and idNo)

Example: anti-fraudPossible values:

mobilestringOptional

11-digit Chinese mobile phone number. Used by anti-fraud. At least one of mobile or idNo required.

Example: 13912345678Pattern: ^1[3-9][0-9]{9}$

idNostringOptional

18-digit Chinese Resident Identity Card number. Required for police. Optional for anti-fraud.

Example: 110101199003076515Pattern: ^[0-9]{17}[0-9Xx]$

namestringOptional

Full legal name in Chinese characters. Required for police.

Example: 李明

Responses

200

Risk check completed

application/json

or

400

Invalid request parameters

502

Upstream verification service error

post

/kyc/cn/risk

HTTPcURLJavaScriptPython

POST /kyc/cn/risk HTTP/1.1
Host: sandbox.staging-api.fill-easy.com
x-client-id: YOUR_API_KEY
x-client-secret: YOUR_API_KEY
Content-Type: application/json
Accept: */*
Content-Length: 44

{
  "type": "anti-fraud",
  "mobile": "13912345678"
}

Anti-Fraud by MobileAnti-Fraud by IDPolice Blacklist

{
  "success": true,
  "message": "Anti-fraud check completed",
  "risks": []
}