Skip to main content
Search

Initiator API 2 - Report TX ID (Before On Chain)

Where should I integrate?​

To Use​

If you're the Originator as Initiator VASP and invoke the before On-Chain Travel Rule request, you must send the report TX ID API after the assets are on-chain. Whether the PII verify status is failed or not, all on-chain transactions should send the TX ID mapping to the counter-party VASP.

This API will not verify anything. It just sends the txId mapping along with requestId to the Beneficiary VASP so they can be notified which transaction has completed the Travel Rule beforehand.

Please submit the requestId that was used previously for the initiator one-step API. The same requestId with the on-chain txId can help the beneficiary VASP map the Travel Rule record that has been completed.

POST /api/verify/v2/notify_tx_id

For further details of the API, refer to the API documentation for /api/verify/v2/notify_tx_id.

Request cURL:

curl --silent --location --request POST "/api/verify/v2/notify_tx_id" \
    --cert-type P12 --cert ./certificate.p12:'[MY_PASSWORD_OF_CERT]' \
    --header 'Content-Type: application/json' \
    --header "Authorization: Bearer [YOUR LOGIN TOKEN]" \
    --header "Connection: keep-alive" \
    --data-raw "{
        \"requestId\": \"[REQUEST ID]\",
        \"txId\": \"[On chain TX ID]\"
    }"

Response Payload:

{
  "verifyMessage": "success!",
  "verifyStatus": 100000
}

You can ignore the response of notify_tx_id. GTR will asynchronously send the notification to the opposite VASP.