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.

Query Params
notation
array of strings

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.

notation
Body Params
string
required

Transaction asset symbol (BTC,ETH)

string
required

Transaction destination address

string
required

Transaction amount in the transaction asset

number

Number of decimals in the transaction asset. This is used to convert the transaction amount to the smallest unit of the asset

string
required

This is the identifier assigned to your VASP

boolean
required

"True" if the originator and beneficiary is the same person and you therefore do not need to collect any information. "False" if it is a third-party transfer.

boolean

This will also check if the transaction is a TRAVEL_RULE in the beneficiary VASP's jurisdiction

string

This is the identifier assigned to the VASP the funds are being sent to

string

Beneficiary VASP name

string

Beneficiary name

string

Beneficiary name

beneficiaryAddress
object
Headers
string

A unique identifier for the request. If the request is sent multiple times with the same idempotency key, the server will return the same response as the first request. The idempotency key is valid for 24 hours.

Responses

Language
URL
LoadingLoading…
Response
Choose an example:
application/json