13-Wrong TXID Verification
- Post-Transaction Approval - TXID Verification Failed.
- This test case intentionally submits an incorrect or non-existent TXID to verify that your system can properly handle TXID verification failures.
Expected Request (VASP → GTR)
- Method:
POST - Base URL:
https://uat-platform.globaltravelrule.com - Endpoint:
/api/verify/v2/one_step - 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:
{
"requestId": "[YOUR_REQUEST_ID]",
"network": "[NETWORK_NAME]",
"address": "[ORIGINATOR_ADDRESS]",
"tag": "[TAG]",
"txId": "[INCORRECT_OR_NONEXISTENT_TX_ID]",
"verifyDirection": 1,
"targetVaspCode": "[TARGET_VASP_CODE]",
"ticker": "[TICKER_NAME]",
"amount": "[CRYPTO_TRANSFER_AMOUNT]",
"fiatName": "USD",
"fiatPrice": "[FIAT_RATIO_PRICE]",
"sourceVaspCode": "",
"expectVerifyFields": [
"100026",
"100025",
"100045"
],
"piiSecuredInfo": {
"initiatorKeyInfo": {
"publicKey": "[YOUR_PUBLIC_KEY]"
},
"piiSecretFormatType": "FULL_JSON_OBJECT_ENCRYPT",
"piiSpecVersion": "ivms101-2020",
"receiverKeyInfo": {
"publicKey": "[THEIR_PUBLIC_KEY]"
},
"secretAlgorithm": "ed25519_curve25519",
"securedPayload": "[PII_ENCRYPTED_PAYLOAD]"
}
}
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/one_step' \
-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\",
\"network\": \"[NETWORK_NAME]\",
\"address\": \"[ORIGINATOR_ADDRESS]\",
\"tag\": \"[TAG]\",
\"txId\": \"[INCORRECT_OR_NONEXISTENT_TX_ID]\",
\"verifyDirection\": 1,
\"targetVaspCode\": \"[TARGET_VASP_CODE]\",
\"ticker\": \"[TICKER_NAME]\",
\"amount\": \"[CRYPTO_TRANSFER_AMOUNT]\",
\"fiatName\": \"USD\",
\"fiatPrice\": \"[FIAT_RATIO_PRICE]\",
\"sourceVaspCode\": \"\",
\"expectVerifyFields\": [
\"100026\",
\"100025\",
\"100045\"
],
\"piiSecuredInfo\": {
\"initiatorKeyInfo\": {
\"publicKey\": \"[YOUR_PUBLIC_KEY]\"
},
\"piiSecretFormatType\": \"FULL_JSON_OBJECT_ENCRYPT\",
\"piiSpecVersion\": \"ivms101-2020\",
\"receiverKeyInfo\": {
\"publicKey\": \"[THEIR_PUBLIC_KEY]\"
},
\"secretAlgorithm\": \"ed25519_curve25519\",
\"securedPayload\": \"[PII_ENCRYPTED_PAYLOAD]\"
}
}"
Hint:
verifyDirectionmust be set to 1 for Post-Transaction ApprovaltxIdis required for Post-Transaction Travel Rule and should be an invalid/non-existent transaction hash for this testaddressis the originator address (FROM address) in Post-Transaction scenariosexpectVerifyFieldsuses Originator codes (100xxx series) as this is Post-Transaction Travel Rule100026: Originator Natural Person Name100025: Originator Natural Person Date of Birth100045: Originator Natural Person National ID
Materials:
Expected Response (GTR → VASP)
When the TXID does not exist or cannot be verified by the target VASP, you will receive:
- HTTP Status Code: 200
verifyStatus: 200007 (TXID Not Found)verifyStage: TRANSACTION_VERIFICATION- No PII verification will be performed (first stage failure).
{
"verifyMessage": "TX ID Not Found" or "Transaction verification failed",
"verifyStatus": 200007,
"verifyStage": "TRANSACTION_VERIFICATION"
}