Validate Travel Rule Transaction
Validate Travel Rule transactions. Checks what beneficiary VASP details are required by your jurisdiction and the beneficiary’s jurisdiction. Deprecation Notice This endpoint will be deprecated soon in favor of the validate full endpoint. Please update your integrations to use the validate full endpoint to ensure compatibility with future releases. Checks what beneficiary VASP details are required by your jurisdiction and the beneficiary’s jurisdiction. Learn more about Fireblocks Travel Rule management in the following guide.
Endpoint Permission: Admin, Non-Signing Admin, Signer, Approver, Editor, Viewer.
Headers
Query Parameters
Specifies the notation of the transaction. Possible values are: - notabene: Uses Notabene notation (default behavior). - fireblocks: Uses Fireblocks notation, with automatic translation of asset tickers and amounts. - <none>: Defaults to notabene for backward compatibility.
Note: The default value for the notation parameter will change from notabene to fireblocks Update your integrations accordingly.
fireblocks, notabene Body
Response
Transaction validated successfully
"isValid" will tell you if you have collected all the information needed for the travel rule data transfer. Once this field = "true", you can move on to the next step which is to transfer the front-end information to your back-end and perform Travel Rule Transaction create
true
"type" will tell you if the virtual asset value converted to FIAT value of the withdrawal request is above (=TRAVELRULE) or below (=BELOW_THRESHOLD) the threshold in your jurisdiction. If it is to an unhosted wallet which does not require travel rule information to be sent and only collected, it will say NON_CUSTODIAL.
"TRAVELRULE"