Standard for PII Verification Methods

About Information

GTR has constituted the standards for verifying PII, based on strict regulations and considering user experience. Please make sure you use this standard to improve verification accuracy.

We can distinguish two types of validation entities: 1. Legal Person (Company/Entity/Enterprise), 2. Natural Person (Individual/Citizen).

They have different verification methods and applicable conditions. Please mind the following attributes and parameters of each verification standard.

Name / Local Name Verification

[Natural Person]

The name of a natural person will have three parameters: Last Name, Middle Name, First Name. Name verification takes into account the possibility of various languages, if you can distinguish whether they are local languages, then the name should be filled in the "Local Name Identifier" in the IVMS101 standard.

1. Use the English name field on KYC

We recommend that you use fields in the KYC system that only have English characters. We know each company's KYC method could be different, and they may use non-English names to fill into the KYC system. However, we still recommend using English fields as much as possible when using GTR verification. The most recommended document is a passport.

English refers to the A-Z of the regular expression. You can refer to the MRZ identification zone at the bottom of the passport. It uses the Doc 9303 standard and can only use 26 English letters to represent a person.

2. Convert to lower case

Convert all names to lowercase.

For example (KYC):

• LastName: Maynard → maynard
• MiddleName: Victor P. → victor p.
• FirstName: Ausburn → ausburn

For example (IVMS101):

• primaryIdentifier: Maynard Victor P. → maynard victor p.
• secondaryIdentifier: Ausburn → ausburn

3. Replace with regular expressions

Each field should use regular rules to remove special characters, please refer to this pattern, remove whitespace and some special characters.

[-,\.\s&%#^?!@{}\[\]()><*"'~\/;:$\\\|\/_=+-]

For example the name "maynard victor p. ausburn" will replace to be: "maynardvictorpausburn" after applying the pattern.

Regex101

4. If the field is empty, leave empty letters

If the field name is empty, please use an empty string instead. Do not use padding with special characters, such as "-", which are bad.

For example (KYC):

• LastName: null → ""
• MiddleName: null → ""
• FirstName: null → ""

For example (IVMS101):

• primaryIdentifier: null → ""
• secondaryIdentifier: null → ""

After replacement, please use the Heap’s algorithm, it generates all possible permutations of n objects, 1: LastName, 2: MiddleName, 3: FirstName:

1 2 3
2 1 3
3 1 2
1 3 2
2 3 1
3 2 1

You will get 6 combinations of name combinations, Please merge them directly during verification and use APIs such as join to complete the combination.

["123", "213", "312", "132", "231", "321"]

Since IVMS 101 only has two fields, primaryIdentifier and secondaryIdentifier should be merged directly and compared.

When you need to fill in the name into an IVMS 101 field with only two Identifiers, you can refer to the following method.

If there are only FirstName and LastName

{
  "primaryIdentifier": "[LastName]",
  "secondaryIdentifier": "[FirstName]"
}

If there is Middle Name

{
  "primaryIdentifier": "[LastName] [MiddleName]",
  "secondaryIdentifier": "[FirstName]"
}

If it is impossible to distinguish, you can fill them all in PrimaryIdentifier

{
  "primaryIdentifier": "[FullName]",
  "secondaryIdentifier": ""
}

Please note that if this is the case where your KYC system cannot distinguish between FirstName and LastName positions, that is, the full name is filled in FirstName or LastName, we recommend that you ask the customer to re-do KYC verification.

Birthday Verification

[Natural Person]

The birthday validation format should be "YYYY-MM-DD" and compared directly.

Place Of Birth Verification

[Natural Person]

The placeOfBirth definition in standard of InterVASP states:

Definition: The town and/or the city and/or the suburb and/or the country subdivision and/or the country where the person was born.

We recommend using one representative name, not to combine multiple types of place, Please refer to the order of adoption.

• If there is a Province/State field, please use it first. such as the United States (New Mexico, Florida…etc), China (Guangdong, Shanghai…etc), Germany (Baden-Württemberg, Berlin…etc), India (Rajasthan, Himachal Pradesh…etc).
• City
• Town

The matching rules are determined by different regulatory units.

Resident Country Verification

[Natural Person]

Please use code 2 national characters.

Country of Registration Verification

[Legal Person]

Please use code 2 national characters.

Legal Name Verification

[Legal Person]

The verification of the company name only has one parameter: the company's full name. Since the company name may contain various special characters, such as . , - , we should refer to two possible comparison methods:

1. Matching only remove whitespace from all special words, convert to lowercase

[\s]

Happy Company Co., Ltd → happycompanyco.,ltd

2. Matching the rule of retaining only the word letters (remove all special character), and convert to lowercase

[-,\.\s&%#^?!@{}\[\]()><*"'~\/;:$\\\|\/_=+-]

Happy Company Co., Ltd → happycompanycoltd

Please use these two possibilities directly for verification.