Skip to main content
Search

Update Address Verification Result

✍️ If your VASP doesn't support Travel Rule Pending Solution, you can skip this implementation guide.

This POST /api/verify/v2/manual/verify_address API allows VASPs to perform Address Verification in a separate async process and notify GTR via this endpoint once verification is completed. GTR will forward the Address Verification result to the corresponding Travel Rule Initiator VASP.

This is a follow-up API for Travel Rule Receiver VASP which previously responded to an Address Verification callback request with a PENDING result.

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

Request​

To use this API,

  • The requestId must already exist beforehand.
  • This request must be at the Address Verification stage with a status 100002 which is PENDING.

Once you call this API, GTR will forward your Address Verification result to your Travel Rule Initiator VASP.

Request A: Address Exists​

If you confirm the address does belong to your VASP, you can call this API with verifyStatus=100000.

{
    "requestId": "[REQUEST-ID]",
    "result": {
        "verifyStatus": 100000,
        "verifyMessage": "verify success"
    }
}

Request B: Address Not Found​

If the address does not belong to your VASP, you can call this API with verifyStatus=200001.

{
    "requestId": "[REQUEST-ID]",
    "result": {
        "verifyStatus": 200001,
        "verifyMessage": "address not found"
    }
}