12-Address Correction (Post-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.
- Post-Transaction Scenario:
txIdis required as the transaction has already been executed on the blockchain.
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/jsonAuthorization: Bearer [JWT_TOKEN]orX-Authorization: [APP_TOKEN]
- Body:
{
"vaspCode": "[USER_SELECTED_VASP_CODE]",
"address": "[BENEFICIARY_ADDRESS]",
"tag": "[TAG]",
"network": "[NETWORK_NAME]",
"txId": "[BLOCKCHAIN_TX_ID]"
}
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' \
# Please use one of Authorization or X-Authorization
--header 'Authorization: Bearer [JWT_TOKEN]' \
--header 'X-Authorization: [APP_TOKEN]' \
--data-raw "{
\"vaspCode\": \"[USER_SELECTED_VASP_CODE]\",
\"address\": \"[BENEFICIARY_ADDRESS]\",
\"tag\": \"[TAG]\",
\"network\": \"[NETWORK_NAME]\",
\"txId\": \"[BLOCKCHAIN_TX_ID]\"
}"
Hint:
vaspCodeis the VASP code initially selected by the user (which may be incorrect)addressis the beneficiary address from the blockchain transactiontxIdis required for Post-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
vaspCodefor subsequent Travel Rule API calls.
{
"data": {
"vaspCode": "[VASP_CODE]"
},
"verifyMessage": "success",
"verifyStatus": 100000
}