Address Routing Verify Callback
Method
POST
Url
https://{YOUR_SERVICE_URL}/(address routing verify: 10)
This callback API endpoint served two purpose in the same endpoint: 1. address ownership verification, 2. txId existence verification. If your VASP has different local entity in different region, this endpoint could be implemented for purpose of VASP routing.
Authentication
No authentication
Path Parameters
No path parameters
Query Parameters
No query parameters
Request Body (Optional)
- Schema
- Example
{
"initiatorVasp": "string",
"requestId": "string",
"verifyTargetType": 0,
"travelruleId": "string",
"beneficiaryAddress": {
"address": "string",
"addressType": 0,
"tag": "string"
},
"transactionInfo": {
"blockId": "string",
"blockHash": "string",
"ticker": "string",
"txIdType": 0,
"txId": "string",
"vin": "string",
"network": "string",
"vout": "string"
}
}
Responses
Status 200
OK
JSON Content
- Schema
- Example
{
"data": {
"redirectVaspCode": "string"
},
"verifyStatus": 0,
"verifyMessage": "string"
}
Status HTTP Status: 200, VerifyStatus: 100000
JSON Content
- Schema
- Example
{
"data": {},
"verifyStatus": 0,
"verifyMessage": "string"
}
verifyTargetType= 1 is to verifybeneficiary_address+network+tagbelongs to your VASP or not.verifyTargetType= 2 is to verifytx id+beneficiary_address+network+tagbelongs to your VASP or not.
For the Address Routing feature, if the beneficiary_address in the request belongs to another entity of your brand, you can return the vasp_code of that entity.
This is a tactic to help reduce the ratio of Address Not Found.