Skip to main content
Search

Address Routing Detection

The background of this POST /api/verify/v2/auto_address_vasp_detection endpoint is that the vaspCode your customer selected may have different local entities.

For example: your customer select Axchange Japan by mistake and your true counterparty should be Axchange USA. This endpoint is to help you route to the correct counterparty and get their VASP Code and Public Key before initiating Travel Rule request.

Thus, before initiating a Travel Rule request, you need to check the correct target VASP code using this API. The vaspCode is still necessary, along with address, network, and tag to detect the correct VASP code.

For further details of this API, see API Reference: /api/verify/v2/auto_address_vasp_detection

Routing Logic​

By providing address or tx_id in the request body, you will receive the correct VASP Code and Public Key from this API. This is the VASP Code and Public Key that you should use to initiate a request.

This API is not for address verification. This is just to tell you who is your exact counterparty VASP.

Your input in the request:

  • VASP: Axchange Japan
  • Address: Address123

Case A: your selected VASP is correct​

This API will return the Axchange Japan.

Case B: Address not found​

This means the address Address123 may not belong to Axchange Japan or any other Axchange entities. Since this API doesn't serve the purpose of Address Verification, it will return you the result as your input.

So, this API will return the Axchange Japan by default.

Case C: Address found, but wrong VASP​

Since Axchange Japan and Axchange USA are in the same brand, this API will return the Axchange USA.

Request & Response​

Address Routing Detection: Pre-transaction Travel Rule​

In the Pre-transaction travel rule case, the txId is null and address is the Beneficiary Address your customer provided.

curl --silent --location --request POST "/api/verify/v2/auto_address_vasp_detection" \
    --cert-type P12 --cert ./certificate.p12:'[MY_PASSWORD_OF_CERT]' \
    --header 'Content-Type: application/json' \
    --header "Authorization: Bearer [YOUR LOGIN TOKEN]" \
    --header "Connection: keep-alive"
    --data-raw "{
        \"vaspCode\": \"[VASP Code]\",
        \"address\": \"[Beneficiary Address]\",
        \"tag\": \"[Tag]\",
        \"network\": \"[Network]\",
        \"txId\": null
    }"

You can expect to get following response:

{
  "data": {
    "vaspCode": "[VASP Code]"
  },
  "verifyMessage": "success",
  "verifyStatus": 100000
}

Address Routing Detection: Post-transaction Travel Rule​

In the Post-transaction travel rule case, the txId is required and address is also the Beneficiary address of this crypto transfer.

curl --silent --location --request POST "/api/verify/v2/auto_address_vasp_detection" \
    --cert-type P12 --cert ./certificate.p12:'[MY_PASSWORD_OF_CERT]' \
    --header 'Content-Type: application/json' \
    --header "Authorization: Bearer [YOUR LOGIN TOKEN]" \
    --header "Connection: keep-alive"
    --data-raw "{
        \"vaspCode\": \"[VASP Code]\",
        \"address\": \"[Beneficiary Address]\",
        \"tag\": \"[Tag]\",
        \"network\": \"[Network]\",
        \"txId\": \"[txId]\"
    }"

You can expect to get following response:

{
  "data": {
    "vaspCode": "[VASP Code]"
  },
  "verifyMessage": "success",
  "verifyStatus": 100000
}