TXID Existence Verify Callback
Method
POST
Url
https://{YOUR_SERVICE_URL}/(TXID exists verify: 9)
This API endpoint is for verify tx id existence, initiator will send you tx id exists verify via GTR, and you have to use tx id + beneficiary address + tag + network to identify one tx id is exists, *The reason using beneficiary address in txId check, is because originator mostly using hot-wallet to make transfer, so that you as originator should using txid + beneficiary address to identify who is originator.
Authentication
No authentication
Path Parameters
No path parameters
Query Parameters
No query parameters
Request Body (Required)
- Schema
- Example
{
"requestId": "string",
"travelruleId": "string",
"ticker": "string",
"address": "string",
"tag": "string",
"txId": "string",
"network": "string",
"initiatorVasp": "string",
"addressType": 0
}
Responses
Status HTTP Status: 200, VerifyStatus: 100000
default response
JSON Content
- Schema
- Example
{
"verifyStatus": 100000,
"verifyMessage": "Verify Success"
}
Status HTTP Status: 200, VerifyStatus: 200007
TX ID Not found case
JSON Content
- Schema
- Example
{
"verifyStatus": 200007,
"verifyMessage": "TX ID Not Found"
}
You have to use tx_id + beneficiary_address + tag + network to identify one tx_id exists in your system or not.
The reason using beneficiary_address in txId check is because originator mostly using hot-wallet to make transfer, so that you as originator should use include beneficiary_address in the txId check.
Response Example 1: Success
HTTP Status: 200, VerifyStatus: 100000
This response indicates that this tx_id do exist in your VASP.
{"verifyStatus": 100000,"verifyMessage": "Verify Success"}
Response Example 2: TX ID Not Found
HTTP Status: 200, VerifyStatus: 200007
{"verifyStatus": 200007,"verifyMessage": "TX ID Not Found"}