Skip to main content
Search

10-Update TX ID (Pre-Transaction)

  • Pre-Transaction Approval - TX ID notification after executing asset transfer on the blockchain.
  • After completing a Pre-Transaction Approval request with successful address verification and reaching the PII Verification stage (regardless of PII verification success or failure), and after executing the asset transfer on the blockchain, this API allows you to submit the actual transaction ID to notify GTR and the counterparty VASP.
  • By calling this API, your counterparty VASP shall have knowledge of the mapping between the Travel Rule request and the blockchain transaction.
  • This is a required step for a completed Pre-Transaction Travel Rule request when the asset transfer is successfully executed on the blockchain.

Expected Request (VASP → GTR)​

  • Method: POST
  • Base URL: https://uat-platform.globaltravelrule.com
  • Endpoint: /api/verify/v2/notify_tx_id
  • Authentication:
    • mTLS (Mutual Transport Layer Security) when sending the API
    • JWT Bearer Token or App Token authentication via Authorization header
  • Header:
    • Content-Type: application/json
    • Authorization: Bearer [JWT_TOKEN] or X-Authorization: [APP_TOKEN]
  • Body:
{
    "requestId": "[ORIGINAL_REQUEST_ID]",
    "txId": "[BLOCKCHAIN_TX_ID]"
}
set -e

export CURL_SSL_BACKEND="openssl"
randomRequestId="test-"$(openssl rand -base64 48 | tr -dc 'a-zA-Z0-9' | head -c "12")"-"$(date '+%Y%m%d%H%M%S')

curl -v --silent --location --request POST 'https://uat-platform.globaltravelrule.com/api/verify/v2/notify_tx_id' \
    -k --cert ./certificate.pem --key ./privateKey.pem \
    --header 'Content-Type: application/json' \
    # Please use one of Authorization or X-Authorization
    --header 'Authorization: Bearer [JWT_TOKEN]' \
    --header 'X-Authorization: [APP_TOKEN]' \
    --data-raw "{
        \"requestId\": \"$randomRequestId\",
        \"txId\": \"[BLOCKCHAIN_TX_ID]\"
    }"

Hint:

  • requestId must be the exact same request ID used in the original /api/verify/v2/one_step call
  • txId is the actual transaction hash/ID from the blockchain after executing the asset transfer
  • Prerequisites: You must have successfully completed a Pre-Transaction Approval request (/api/verify/v2/one_step) with successful address verification that reached PII Verification stage
  • Blockchain transaction must be executed: Only call this API AFTER you have actually executed the asset transfer on the blockchain
  • The counterparty VASP can use this mapping to identify incoming deposits and their associated Travel Rule compliance status
  • If you decide not to execute the blockchain transaction, use /api/verify/v2/end instead to cancel the Travel Rule request

Materials:

Expected Response (GTR → VASP)​

When the TX ID is successfully submitted, the system returns:

  • HTTP Status Code: 200
  • verifyStatus: 100000 (success)
{
    "verifyMessage": "success",
    "verifyStatus": 100000
}