Chinese Documents

Supported Chinese Documents

The FrankieOne KYC v2 API supports the following Chinese documents:

Chinese National ID Card (身份证)

Chinese National ID Cards (身份证) are official identification documents issued by the Chinese government that confirm an individual’s identity and citizenship. They include personal details such as the individual’s name, date of birth, ID card number, and expiration date.

Required Fields

Name Handling Guidelines:

1
{
2
  "familyName": "ZHANG",     // Family name in uppercase Pinyin
3
  "givenName": "WEIMING"     // Given name (and middle name, if any) in uppercase Pinyin
4
}

1
{
2
  "supplementaryData": {
3
    "homeCountryFullName": "张伟明" // Full name in Chinese characters
4
  }
5
}

Chinese Name Transliteration Check (Name Validation)

For enhanced identity verification, FrankieOne offers a name transliteration check. This feature verifies that an applicant’s English/Pinyin name (e.g., “Wei Wang”) is the correct transliteration of their name written in Chinese characters (e.g., “王伟”). This check, historically known as namev in v1, uses a specialized third-party service to ensure the two name versions are a plausible match, helping to reduce identity fraud.

How It Works & Configuration

The transliteration check is not enabled by default. It must be configured in your workflow by the FrankieOne team as a distinct step called NAME_VALIDATION.

1. The anglicized name is taken from the primary individual.name object (givenName and familyName).
2. The native script name is taken from the document.supplementaryData.homeCountryFullName field for the Chinese NATIONAL_ID.
3. The NAME_VALIDATION step in the workflow sends these two names to the transliteration service.
4. If the native script name (homeCountryFullName) is not provided, the step will be skipped and the result will be SKIPPED.

To enable this feature, please contact your FrankieOne representative and request the NAME_VALIDATION step be added to your KYC workflow.

Example Result

When the NAME_VALIDATION step is executed, a workflowStepResult is added to the API response. The outcome is detailed within the processResult object, which will have a result of MATCH or NO_MATCH.

1
{
2
  "workflowStepResults": [
3
    {
4
      "stepName": "NAME_VALIDATION",
5
      "result": "SUCCESS",
6
      "processResults": [
7
        {
8
          "provider": "AsiaConnector",
9
          "objectType": "NAME",
10
          "class": "KYC",
11
          "result": "MATCH",
12
          "checkDate": "2025-10-15T07:40:57.000Z",
13
          "data": {
14
            "reference": "av-ref-12345",
15
            "message": "Name transliteration check passed."
16
          }
17
        }
18
      ]
19
    }
20
  ]
21
}

Example Document Structure

1
{
2
  "document": {
3
    "class": "IDENTITY",
4
    "documentId": "92de15f64-5717-4562-b3fc-2c963f6665a7",
5
    "primaryIdentifier": "110105199003077341",
6
    "type": "NATIONAL_ID",
7
    "country": "CHN"
8
  },
9
  "supplementaryData": {
10
    "type": "NATIONAL_ID",
11
    "homeCountryFullName": "张伟明"
12
  }
13
}