Receiver Callback API 2 - TX Verification
Where should I integrate
Callback Behaviour
This callback is to verify the txId is exists in your system.
For further details of request structure, see: RegularizeCallbackVerifyTransactionRequest
When the initiator requests to verify whether the transaction exists in your service, you will receive the callback request, and the callback type will be 9.
Request Payload From GTR:
{
"requestId": "IGicRINHYF4N",
"invokeVaspCode": "[Invoker VASP Code]",
"originatorVasp": "[Originator VASP Code]",
"beneficiaryVasp": "[Beneficiary VASP Code]",
"callbackType": 9,
"callbackData": {
"requestId": "IGicRINHYF4N",
"ticker": "ETC",
"address": "0x41ebF291D8BFb6481B4Ab1E26c412A96484b1454",
"tag": "",
"txId": "1fcd10006f252d2cca3a4803d0dcb84b0ee10ef73d1055f0fe23ce4ead0f6e75",
"network": "Sepolia",
"initiatorVasp": "[Initiator VASP Code]"
}
}
Please identify callback type 9 and use the info fields: ticker, network, and txId to search for the target transaction.
First, scan txId from your blockchain scan database, if match any records, then filter the to_address by the address (optional: with tag if required) from callback parameter.
*The address format of txId+vout is currently not supported. If a transfer is initiated with multiple recipients, the response should be "tx id and address not found", and the reason for the multiple possible addresses should be described in the response.
And provide the result as shown below:
If transaction exists
Response from your service if exists:
{
"verifyMessage": "success",
"verifyStatus": 100000
}
If transaction not exists
Response from your service if not exists:
{
"verifyMessage": "txId and address/tag not found",
"verifyStatus": 200007
}
If transaction with target address get multiple records
Response from your service if not exists:
{
"verifyMessage": "Too many records founded",
"verifyStatus": 200007
}
The timing of block been scanned could be different between two system, we will suggest the API Initiator to wait 30sec and initiate the request.
*The Timeout of this API response should be < 2 sec.