Skip to main content
Search

Receiver Update API 2 - Transaction ID Verify Result Update

Where should I integrate?​

Receiver Update API 2 - Transaction Verification​

This API is for Receiver VASPs who will respond with a pending state to the Travel Rule. It allows you to perform the verification step manually in a separate process.

*If you don't have a pending flow, you can skip this implementation.

To Use​

To use this API, the requestId must exist beforehand because someone (Initiator VASP) has initiated the request and is at the TX ID verification stage: callbackType=9. You replied as pending (verifyStatus: 100002), and when you finish the manual verification, reply with the status via this API. GTR will help notify the Initiator VASP.

API Request​

POST /api/verify/v2/manual/verify_tx_id

Request Payload - Transaction ID Exists

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

Request Payload - Transaction ID Not Found:

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