Skip to main content
Search

Additional Callback APIs & Parameters

Receiver Callback API 7: End of Flow Notify

Where should I integrate​

Callback Behaviour​

In the before on chain scenario, if originator VASP decide not to transfer assets on chain, you will receive the end of flow status to get cancel notify.

The Request Payload from GTR:

{
  "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
        }
    }
}

Once you recieve this callback, you can use requestId to search the corresponding travel rule records and mark as the end travel rule stauts that are not transfer on chain.