Skip to main content
Search

Callback - Receive Travel Rule End Notify

In the Pre-Transaction Travel Rule scenario, if the Travel Rule Initiator VASP (also the Originator VASP) decides not to transfer crypto assets onto blockchain, your service will receive this Travel Rule termination notification callback with callbackType=17.

Request​

You can expect to receive below request payload from GTR with callbackType=17:

{
  "requestId": "[REQUEST-ID]",
  "invokeVaspCode": "YOUR_VASP_CODE",
  "originatorVasp": "ORIGINATOR_VASP_CODE",
  "beneficiaryVasp": "BENEFICIARY_VASP_CODE",
  "callbackType": 17,
  "callbackData": {
        "notifyResult": {
            "verifyMessage": "travel rule canceled",
            "verifyStatus": 100028
        },
        "finalStateInfo": {
            "reasonType": "REJECTED",
            "reason": "rejected"
        },
        "basicMessage": {
            "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 use requestId to search your in-house Travel Rule records and update the status as End or Cancel.