PII Verify Fields
Sometimes, companies using GTR Solution must complete personal identity verification in advance. In order to meet the needs of due diligence, we additionally support optional fields called: Verify Fields.
For Travel Rule Request Initiator, they will bring out the fields expectVerifyFields they want to check for verification. And put the expectVerifyFields in request payload, for example: Initiator API 5: PII Verification, you can bring the parameter
*Travel Rule Request Initiator could be Originator VASP or Beneficiary VASP.
{
"requestId": "[YOUR REQUEST ID]",
"ticker": "ETC",
"address": "0x41ebF291D8BFb6481B4Ab1E26c412A96484b1454",
"tag": "",
"verifyType": 2,
"network": "xxxxxxxx",
"beneficiaryVasp": "xxxxxxx",
"encryptedPayload": "[YOUR PAYLOAD]",
"originatorPublicKey": "[YOUR PUBLIC KEY]",
"beneficiaryPublicKey": "[BENEFICIARY PUBLIC KEY]",
"fiatName": "USD",
"amount": "1000",
"fiatPrice": "6.66",
"lawThresholdEnabled": true,
"expectVerifyFields": [
"111001", // Beneficiary Legal Person Name
"110026" // Beneficiary Natural Person Name
]
}
For the Target VASP, they need to verify all the fields they can verify and bring out the results. And put the results into stage 3: receive PII results callback, for example: Receiver Callback API 3: PII Verification.
{
"verifyStatus": 100000,
"verifyMessage": "Success",
"data": {
"encryptedPayload": "....",
"verifyFields": [
{
"type": "110026", // Beneficiary Natural Person Name
"status": 1,
"message": "match"
}
]
//...
}
// ...
}
GTR will return based on the fields mentioned by Initiator instead of returning all the verification of the Beneficiary. In other words, the verification field result obtained by Initiator is an Intersection.
For the verifying fields, we provide the list that you could refer to, if the field is not in the list, you still can name it, please use UPPER snake case to name it.
Common Type Name:
| Name | FATF Name | JSON Path | GTR Enum |
|---|---|---|---|
| Beneficiary Legal Person Name | LegalPersonName | x.ivms101.Beneficiary.beneficiaryPersons[].legalPerson.name.nameIdentifier | 111001 |
| Beneficiary Natural Person Name | NaturalPersonNameID | x.ivms101.Beneficiary.beneficiaryPersons[].naturalPerson.name.nameIdentifier | 110026 |
| Beneficiary Natural Person Local Name | LocalNaturalPersonNameID | x.ivms101.Beneficiary.beneficiaryPersons[].naturalPerson.na Local Name is the non-english alphabet nameme.localNameIdentifier | 110027 |
| Beneficiary Natural Person Place of Birth | PlaceOfBirth | x.ivms101.Beneficiary.beneficiaryPersons[].naturalPerson.dateAndPlaceOfBirth.placeOfBirth | 110024 |
| Beneficiary Natural Person Date of Birth | DateOfBirth | x.ivms101.Beneficiary.beneficiaryPersons[].naturalPerson.dateAndPlaceOfBirth.dateOfBirth | 110025 |
| Beneficiary Natural Person Phonetic Name | LocalNaturalPersonNameID | x.ivms101.Beneficiary.beneficiaryPersons[].naturalPerson.name.phoneticNameIdentifier | 110028 |
| Beneficiary Natural Person Country Of Residence | CountryOfResidence | x.ivms101.Beneficiary.beneficiaryPersons[].naturalPerson.countryOfResidence | 110048 |
| Beneficiary Legal Person Country Of Registration | CountryOfRegistration | x.ivms101.Beneficiary.beneficiaryPersons[].legalPerson.countryOfRegistration | 111022 |
*Verify Fields code names are distinguished by Originator/Beneficiary and need to be used in different scenarios.
Status Enum Type:
| Status Enum Name | Status Enum Value (Integer) | Description |
|---|---|---|
| SKIP | 0 | GTR Response No Verify |
| MATCH / PASS | 1 | Full match Or Pass |
| MISMATCH | 2 | Not match |
| NOT_SUPPORT | 3 | Counter-Party VASP Response No Verify |
| REQUIRED_INFO_MISSING | 4 | Required Info missing (Required by the receiving VASP, but the field is missing) |
| REQUIRED_INFO_EXISTS | 5 | Received / Exists (Required by the receiving VASP; the field is present, but it cannot be verified because KYC/B does not support this field) |
The error message will also give the Travel Rule Initiator two forms of information, one is the verification result expected by the Initiator, and the other is the verification result expected by the Receiver.
In Travel Rule Request Initiator
Among them, SKIP, MATCH/PASS, MISMATCH, NOT_SUPPORT will only appear in the expectVerifyFields required by the Initiator. In other words, only the items listed by the Initiator will be returned in the result.
*Travel Rule Request Initiator could be Originator VASP or Beneficiary VASP.
In Travel Rule Request Receiver
Among them, INFO_MISSING and INFO_EXISTS will appear in the information returned by the Receiver. They represent the required information required by the other party's VASP. Regardless of whether the Initiator is included in expectVerifyFields, the results required by the fields will be returned to the Initiator.
*Travel Rule Request Receiver could be Originator VASP or Beneficiary VASP.
You can use the VASP Detail API to query which fields are required by the Receiver, which are presented in the requiredPiiFieldsAsBeneficiary field.
You can also check supportedVerifyFields to check which fields Receiver VASP can help you verify.
See: GET /api/common/v3/vasp/detail
Multiple National Identifications
IVMS101 carries one nationalIdentification object per person. Identity documents beyond that one are transmitted in specificNationalIdentifications, an object whose keys are a closed set of fixed slots named after the document type — ID_CCPT, ID_IDCD, ID_DRLC, and so on. See About Field - specificNationalIdentifications in the IVMS-101 Format Guidelines for the full structure and filling rules.
Why the documents are not sent as an array
This page is the reason. A Verify Field is a single numeric ID that has to resolve to exactly one value in the payload, on both sides: the Initiator puts the ID in expectVerifyFields, the Receiver returns a result carrying the same ID, and the exchange only means anything if that ID denotes the same JSON path for both VASPs. The mapping between a Verify Field ID and a JSON path must therefore be one-to-one and fixed before either side writes any code.
An array of identifications breaks that mapping:
- An array position is not stable. A document's index depends on how many documents happen to sit in front of it, so the same passport is
nationalIdentification[1]in one request andnationalIdentification[0]in the next, after an ID card is dropped from the customer's record. A Verify Field ID pinned to index1would address a different document every time. - Without a stable path the Receiver cannot tell which document the Initiator asked it to verify, and cannot report "passport matched, ID card did not" without ambiguity.
- Transmitted Content is affected in the same way: its manifest attaches
fieldIdto afieldPath, and a shifting array index changes the path of content that never changed.
A fixed slot key removes the moving part. ...specificNationalIdentifications.ID_CCPT.nationalIdentifier is the same path in every payload from every VASP, so each slot can hold a permanently assigned Verify Field ID: one slot ↔ one Verify Field ID ↔ one manifest entry. It is also why the key set is one slot per document type, fully enumerated, with no ordinals — every key in the set has to be assignable to an ID up front.
Slot to Verify Fields ID mapping
Interim design. Upstream IVMS101 has not yet released a standard way to carry more than one identity document per person, so both the slot structure and these IDs are provisional. If a later edition of IVMS101 publishes an official structure, GTR will follow the standard and notify integrating VASPs to migrate for interoperability. Keep the mapping between your KYC records and the slot keys in one place so that a change stays cheap.
Each ID addresses the nationalIdentifier value inside that slot. The document type needs no separate ID, because the slot key already fixes it.
Every slot has a distinct Verify Fields ID per direction and per entity type, so a single ID always resolves to exactly one JSON path. The full definition of each ID is in the PII Verify Fields Reference Table below.
Slot Key
nationalIdentifierType
Originator - Natural Person
Originator - Legal Person
Beneficiary - Natural Person
ID_ISO20022
ISO20022
100060
101049
110060
ID_ARNU
ARNU
100061
101050
110061
ID_CCPT
CCPT
100062
101051
110062
ID_RAID
RAID
100063
101052
110063
ID_DRLC
DRLC
100064
101053
110064
ID_FIIN
FIIN
100065
101054
110065
ID_TXID
TXID
100066
101055
110066
ID_SOCS
SOCS
100067
101056
110067
ID_IDCD
IDCD
100068
101057
110068
ID_LEIX
LEIX
100069
101058
110069
ID_MISC
MISC
100070
101059
110070
ID_RAIDandID_LEIXare for legal persons. IVMS101 defines RAID as body-corporate only and LEIX as legal-entity only. The Natural Person IDs on those two rows (100063,110063,100069,110069) exist in the global definition for completeness; do not fill those slots on anaturalPerson.
The optional dateOfIssue and dateOfExpiry extension fields inside a slot have no Verify Fields ID assigned. They are transmitted with the slot, but they cannot be listed in expectVerifyFields and no verification result is returned for them.
Notes:
- Slots are defined for the Originator and Beneficiary persons only. The
OriginatingVASPandBeneficiaryVASPentities keep using their existing single-identification fields (121002/121003,131002/131003). - The existing
nationalIdentificationfields (100044/100045,110044/110045, and the Legal Person equivalents) are unchanged and keep addressing the IVMS101nationalIdentificationobject. - A slot that the sender did not fill is absent from the payload. Requesting its ID returns the same result as any other absent field:
REQUIRED_INFO_MISSINGwhen the Receiver requires it, otherwise the Receiver's usual unverifiable status.
PII Verify Fields Reference Table
Update: 2026 Oct 02
VerifyFields
IVMS Name
Direction
Entity Type
Verify Rules ID
101006
Legal Person Customer Identification
Originator
Legal Person
101052
Legal Person National ID - Business registration number provided by the authority
Originator
Legal Person
101056
Legal Person National ID - Social Security Number or National Identification Number
Originator
Legal Person
101057
Legal Person National ID - Identity card number assigned by a state agency
Originator
Legal Person
101058
Legal Person National ID - Global legal entity identification number
Originator
Legal Person
100063
Natural Person National ID - Business registration number provided by the authority
Originator
Natural Person
100067
Natural Person National ID - Social Security Number or National Identification Number
Originator
Natural Person
100068
Natural Person National ID - Identity card number assigned by a state agency
Originator
Natural Person
100069
Natural Person National ID - Global legal entity identification number
Originator
Natural Person
100070
Natural Person National ID - ID card number from other countries
Originator
Natural Person
111006
Legal Person Customer Identification
Beneficiary
Legal Person
111052
Legal Person National ID - Business registration number provided by the authority
Beneficiary
Legal Person
111056
Legal Person National ID - Social Security Number or National Identification Number
Beneficiary
Legal Person
111057
Legal Person National ID - Identity card number assigned by a state agency
Beneficiary
Legal Person
111058
Legal Person National ID - Global legal entity identification number
Beneficiary
Legal Person
110063
Natural Person National ID - Business registration number provided by the authority
Beneficiary
Natural Person
110067
Natural Person National ID - Social Security Number or National Identification Number
Beneficiary
Natural Person
110068
Natural Person National ID - Identity card number assigned by a state agency
Beneficiary
Natural Person
110069
Natural Person National ID - Global legal entity identification number
Beneficiary
Natural Person
110070
Natural Person National ID - ID card number from other countries
Beneficiary
Natural Person
ISO20022 Document Example
Verify Fields 100060 and 110060 carry an ISO20022 document as the identifier value. The format is a pacs.008 message:
<?xml version="1.0" encoding="UTF-8"?>
<Document xmlns="urn:iso:std:iso:20022:tech:xsd:pacs.008.001.08">
<FIToFICstmrCdtTrf>
<!-- 1. Message Header Group (GrpHdr) -->
<GrpHdr>
<MsgId>MSG20261002-99812</MsgId>
<CreDtTm>2026-10-02T13:55:00Z</CreDtTm>
<NbOfTxs>1</NbOfTxs>
</GrpHdr>
<!-- 2. Core Transaction Details (CdtTrfTxInf) -->
<CdtTrfTxInf>
<PmtId>
<EndToEndId>E2E-987654321</EndToEndId>
</PmtId>
<!-- Amount and Currency ($5,000.00 USD) -->
<IntrBkSttlmAmt Ccy="USD">5000.00</IntrBkSttlmAmt>
<!-- 3. Debtor / Sender Info (Dbtr) -->
<Dbtr>
<Nm>John Doe</Nm>
<PstlAdr>
<StrtNm>Orchard Road</StrtNm>
<BldgNb>123</BldgNb>
<Ctry>SG</Ctry>
</PstlAdr>
</Dbtr>
<!-- Sender's Bank (DbtrAgt) using SWIFT Code (BIC) -->
<DbtrAgt>
<FinInstnId>
<BICFI>DBSSSGSGXxx</BICFI>
</FinInstnId>
</DbtrAgt>
<!-- 4. Creditor's Bank / Receiver's Bank (CdtrAgt) -->
<CdtrAgt>
<FinInstnId>
<BICFI>CHYBUS33Xxx</BICFI>
</FinInstnId>
</CdtrAgt>
<!-- 5. Creditor / Receiver Info (Cdtr) -->
<Cdtr>
<Nm>Alice Smith</Nm>
<PstlAdr>
<StrtNm>Fifth Avenue</StrtNm>
<BldgNb>456</BldgNb>
<Ctry>US</Ctry>
</PstlAdr>
</Cdtr>
</CdtTrfTxInf>
</FIToFICstmrCdtTrf>
</Document>