Skip to main content
Search

Callback Structure Explain

About​

GTR uses the same API Endpoint (from your service) to process the Travel Rule verification. Please log in to the GTR dashboard to configure the Callback URL.

The outer payload will be like:

{
  "requestId": "[REQUEST-ID]",
  "invokeVaspCode": "[Invoker VASP Code]",
  "originatorVasp": "[Originator VASP Code]",
  "beneficiaryVasp": "[Beneficiary VASP Code]",
  "callbackType": 0,
  "callbackData": {
    
  }
}

Parameter explanations are as follows:

  • requestId: the requestId from Initiator VASP. The same Travel Rule will use the same request ID. If you see any parameter named requestId, it refers to the same thing. We include it in the callback data for convenience.
  • invokeVaspCode: who will receive this callback. This is useful if you have many local exchanges sharing the same API endpoint for management. You can recognize the invokeVaspCode to route traffic to the correct VASP logic.
  • originatorVasp is the originator of the assets transfer direction
  • beneficiaryVasp is the beneficiary of the assets transfer direction
  • callbackType is the stage representation as a numeric ID
  • callbackData is the dynamic structure that depends on the different callbackType