Callback - PII Verification Result Notify

✍️ If your VASP doesn't support Travel Rule Pending Solution, you can skip this implementation guide.

This callback API notifies the Travel Rule Initiator VASP of the PII Verification result.

GTR will forward the verification result with callType=15 to your service once the Travel Rule Receiver VASP has completed the PII Verification.

Type	Pre-transaction Travel Rule	Post-transaction Travel Rule
Your Role in Travel Rule	Travel Rule Initiator VASP	Travel Rule Initiator VASP
Your Counterparty in Travel Rule	Travel Rule Receiver VASP	Travel Rule Receiver VASP
Your Role in Transfer	Originator VASP	Beneficiary VASP
Your Counterparty Role in Transfer	Beneficiary VASP	Originator VASP
Your Counterparty's Responsibility	Confirmed correctness of Beneficiary PII	Confirmed correctness of Originator PII

Request

Once your Travel Rule Receiver VASP responds with the PII Verification result, you shall receive this callback request with callType=15.

✍️ You can focus on the matching result of the fields you specified in the expectVerifyFields in the original One-Step request and ignore the others.

This should help you to meet your minimum compliance requirement.

For more detail of verifyFields, you can visit Expect Verify Fields & Verify Fields

{
  "callbackType": 15,
  "invokeVaspCode": "0xQKGsNzOq2Er-xh6ReiL",
  "originatorVasp": "0xQKGsNzOq2Er-xh6ReiL",
  "requestId": "[REQUEST-ID]",
  "beneficiaryVasp": "gdummy",
  "callbackData": {
    "notifyResult": {
      "verifyMessage": "PII Verification Success",
      "verifyStatus": 100006
    },
    "piiSecuredInfo": {
      "initiatorKeyInfo": {
        "publicKey": ""
      },
      "piiSecretFormatType": "FULL_JSON_OBJECT_ENCRYPT",
      "piiSpecVersion": "ivms101-2020",
      "receiverKeyInfo": {
        "publicKey": ""
      },
      "secretAlgorithm": "ed25519_curve25519",
      "securedPayload": "PII"
    },
    "piiVerifyResult": {
      "verifiedFields": [
        {}
      ]
    },
    "preflightCheckResult": {
      "preflightCheckMessage": "",
      "preflightCheckStatus": "REJECTED"
    },
    "travelruleInfo": {
      "beneficiaryVaspCode": "gdummy",
      "initiatorVaspCode": "0xQKGsNzOq2Er-xh6ReiL",
      "invokeVaspCode": "gdummy",
      "originatorVaspCode": "0xQKGsNzOq2Er-xh6ReiL",
      "receiverVaspCode": "gdummy",
      "requestId": "[REQUEST-ID]",
      "verificationDirection": 2
    }
  }
}

💡 GTR Implementation Recommendations

Once you receive this callback, you can update your in-house Travel Rule records to the PII Verify stage and status accordingly.

Callback - PII Verification Result Notify

Request​

Request