Skip to main content
Search

Address Routing Verify Callback

Version: 3.0.0

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)

PropertyTypeRequiredDescription
beneficiaryAddress
ObjectNo
PropertyTypeDescription
address
String
addressType
Integer
tag
String
initiatorVasp
StringNo
requestId
StringNo
transactionInfo
ObjectNo
PropertyTypeDescription
blockHash
String
blockId
String
network
String
ticker
String
txId
String
txIdType
Integer
vin
String
vout
String
travelruleId
StringNo
verifyTargetType
IntegerNo

Responses

Status 200

OK

JSON Content

PropertyTypeDescription
data
Object
PropertyTypeDescription
redirectVaspCode
String
verifyMessage
String
verifyStatus
Integer

Status HTTP Status: 200, VerifyStatus: 100000

JSON Content

PropertyTypeDescription
data
Object
PropertyTypeDescription
No properties
verifyMessage
String
verifyStatus
Integer
  • verifyTargetType = 1 is to verify beneficiary_address + network + tag belongs to your VASP or not.
  • verifyTargetType = 2 is to verify tx id + beneficiary_address + network + tag belongs 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.