VerifyVASP
  • Welcome
  • Change Log
  • Getting Started
    • Getting Started with VerifyVASP
    • Product Overview
    • Alliance Registration & API Key Creation
    • VASP API Functionality
    • Database
    • Enclave Installation & Execution
    • Security Guide
    • Robot VASP Utilization
    • Enclave Server API Utilization
    • Enclave Server Health Monitoring & Troubleshooting
  • Reference
    • Enclave API Reference
      • v1
        • VASP ID
        • VASP List
        • Screening API
          • Risk Assessment with Chainalysis Sanction API
          • Risk Assessment with Chainalysis KYT API
          • Risk Assessment with Refinitiv WCO API
        • User Account Verification
        • User Verification
        • Verification Result List
        • Verification Result by UUID
        • Transaction Result Report
        • Error Report
        • Transaction Status Query
    • VASP API Reference
      • User Account Verification
      • User Verification
      • Transaction Status Query
      • Callback API
      • Decrypting Database Encryption Key
    • IVMS101 Guide
      • About IVMS101 Standard
      • IVMS101 Message Format Guide
      • IVMS101 Personal Data Fields
    • Supplement
      • Network Field
      • Wallet address and transaction ID standards
    • Glossary
Powered by GitBook
On this page
  • Transaction Status Query API
  • Request Header
  • Request Body
  • Response Body
  1. Reference
  2. VASP API Reference

Transaction Status Query

Transaction Status Query API

POST VEGA_VERIFICATION_TRANSACTION_API_PATH

Enclave Environment Variable:

Enter the Transaction Status Query API endpoint in VEGA_VERIFICATION_TRANSACTION_API_PATH field.

VASPs can be both the beneficiary and originating VASP. Once an originating VASP verifies the beneficiary through VerifyVASP and sends virtual assets to the actual blockchain, it must send the transaction id (transaction hash) value to VerifyVASP. However, if this fails for whatever reason, the beneficiary VASP must be able to know which verification matches the deposit.

This API is called to the Originating VASP by the beneficiary VASP to enquire about the transaction status on the actual blockchain via VerifyVASP.

Response Time standard

This API must respond in 1 second.

Request Header

Field Name
Description

Authorization

Bearer <VEGA_VERIFICATION_AUTHORIZATION_TOKEN>

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"

Verification uuid to inquire transaction process status

Response Body

Response Body Examples
  • 200 OK

{
    "verificationUuid": "8557f2b2-985e-431f-8d52-75c2e5a01e46",
    "transactionStatus": "PROCESSING",
    "txHash": "8a54d58ca4100112a5430818776d74898f2232770bae03046862575cb851a042",
    "vout": "2"
}
Field Name
Data Type
Required
Example
Description

verificationUuid

string

true

"8557f2b2-985e-431f-8d52-75c2e5a01e46"

Verification uuid which inquired transaction process status

transactionStatus

string

true

"PROCESSING"

Transaction process status, refer to the explanation below.

txHash

string

false

"8a54d58ca4100112a5430818776d74898f2232770bae03046862575cb851a042"

Transaction id (transaction hash), return only when known.

vout

string

false

"2"

An index value indicating which transfer corresponds to within a single transaction, returned only if exist.

  • In the transactionStatus field can be included the values below.

    • 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.

PreviousUser VerificationNextCallback API

Last updated 1 year ago

Transaction Status Transition Diagram