Skip to main content
Search

04-Address Correction (Pre-Transaction)

  • This API automatically corrects user-selected VASP when incorrect selection is detected. Correction is only available when VASPs belong to the same corporate group('brand') and the counterparty supports address routing.
  • The API may return the same VASP code as in the request body (if correct) or a corrected VASP code if available. Refer to the Address Routing Detection Documentation for detailed response scenarios.
  • Note: This API is NOT for address verification or VASP discovery purposes.

Expected Request (VASP → GTR)

  • Method: POST
  • Base URL: https://uat-platform.globaltravelrule.com
  • Endpoint: /api/verify/v2/auto_address_vasp_detection
  • 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:
{
"vaspCode": "[VASP_CODE]",
"address": "[BENEFICIARY_ADDRESS]",
"tag": "[ADDRESS_TAG]",
"network": "[NETWORK]",
"txId": null
}
set -e

export CURL_SSL_BACKEND="openssl"

curl -v --silent --location --request POST 'https://uat-platform.globaltravelrule.com/api/verify/v2/auto_address_vasp_detection' \
-k --cert ./certificate.pem --key ./privateKey.pem \
--header 'Content-Type: application/json' \
--header 'ignore-detect: true' \
# Please use one of Authorization or X-Authorization
--header 'Authorization: Bearer [JWT_TOKEN]' \
--header 'X-Authorization: [APP_TOKEN]' \
--data-raw "{
\"vaspCode\": \"[VASP_CODE]\",
\"address\": \"[BENEFICIARY_ADDRESS]\",
\"tag\": \"[ADDRESS_TAG]\",
\"network\": \"[NETWORK]\",
\"txId\": null
}"

Hint:

  • [VASP_CODE] is the VASP code selected by user from VASP list
  • [BENEFICIARY_ADDRESS] is the destination wallet address
  • [ADDRESS_TAG] is optional address tag/memo if applicable
  • [NETWORK] specifies the blockchain network (e.g., BTC, ETH, XRP)
  • txId should be null for Pre-Transaction scenarios
  • This API provides correction only when VASPs are in the same corporate group
  • Important: This API is NOT for address verification purposes

Materials:


Expected Response (GTR → VASP)

  • Confirm you receive a valid response with verifyStatus: 100000
  • Always use the returned vaspCode for subsequent Travel Rule API calls.
{
"data": {
"vaspCode": "[VASP_CODE]"
},
"verifyMessage": "success",
"verifyStatus": 100000
}