VerifyVASP
Search
⌃K

Transaction Status Query

post
http://<enclave-endpoint>
/v1/verifications/tx/inquiry
Transaction status query API
A VASP can check a transaction status if it has not received a transaction ID (txHash) report from an originating VASP in a duration.
Policy
  • When the beneficiary VASP detects a deposit transaction, the VASP can do txHash filtering to find candidates and call the verification result checking API to find a matched verification history.
  • If there is no exact matching txHash found in filtering, the VASP can wait for the transaction result report from the originating VASP.
  • When there is no report in a while, the beneficiary VASP can call the verification result checking API to filter out the candidates.
    • Setting the originator account number to 'from address' and beneficiary account number to 'to address' can narrow down the candidates.
    • Comparison of the transaction amounts is also helpful for filtering out.
  • You can find the final candidate of verification history by checking the transaction status for each of the candidates.

Request Body

Request Body Examples
{
"verificationUuid": "8557f2b2-985e-431f-8d52-75c2e5a01e46"
}
Field Name
Data Type
Required
Example
Description
verificationUuid
string
true
“8557f2b2-985e-431f-8d52-75c2e5a01e46”
UUID of completed verification. UUID which was used as a key during /verification process before sending Transaction to the blockchain.

Response Body

Success case

Response Body Examples
  • 200 OK
{
"verificationUuid": "8557f2b2-985e-431f-8d52-75c2e5a01e46",
"transactionStatus": "PROCESSING",
"txHash": ""
}
  • 200 OK
{
"verificationUuid": "8557f2b2-985e-431f-8d52-75c2e5a01e46",
"transactionStatus": "CONFIRMED",
"txHash": "0xaaa042c0632f4d44c7cea978f22cd02e751a410e"
}
Field Name
Data Type
Example
Required
Description
verificationUuid
string
"8557f2b2-985e-431f-8d52-75c2e5a01e46"
true
UUID of completed verification.
transactionStatus
string
"PROCESSING"
true
Transaction Status.
txHash
string
"0xb966123f0f7fc226f93688f77cfa4993d675ac9847049ad2d8bc56d64eaf06d5”
false
TxHash (Transaction ID), Returned only in available.
  • transactionStatus field specification is as follows.
    • PENDING: Blockchain transaction transmission is blocked for some reason.
    • PROCESSING: Waiting to be mined after transaction transmission.
    • WAIT-CONFIRM: The transaction is mined to block but not finalized yet.
    • CONFIRMED: The finality of the transaction is confirmed after being mined to block.
    • CANCELED: Blockchain transaction is canceled with or without starting transmission.
Transaction state transition diagram

Error Codes

Mandatory parameter missing

Response Body Examples
  • 400 Bad Request
{
"code": "MISSING-VERIFICATION-UUID",
"message": "`verificationUuid` is required."
}

Invalid verification UUID input

Response Body Examples
  • 400 Bad Request
{
"code": "VERIFICATION-NOT-FOUND",
"message": "Verification(9faab87c-54a6-4145-baa9-7a3a42d7410c) is not found"
}

A mismatch of the caller VASP with the beneficiary VASP

Response Body Examples
  • 400 Bad Request
{
"code": "VASP-NOT-MATCHED",
"message": "You are not the beneficiary VASP for the verification"
}