Skip to main content
Search

Update TXID 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_tx_id API allows VASPs to perform TXID Verification in a separate async process and notify GTR via this endpoint once verification is completed. GTR will forward the TXID 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 TXID Verification callback request with a PENDING result.

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

Request​

To use this API,

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

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

Request A: Transaction ID Exists​

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

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

Request B: Transaction ID Not Found​

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

{
    "requestId": "[REQUEST-ID]",
    "result": {
        "verifyStatus": 200007,
        "verifyMessage": "tx id not found"
    }
}