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 result reporting API
  • Request Body
  • Response Body
  • Success case
  • Error Codes
  1. Reference
  2. Enclave API Reference
  3. v1

Transaction Result Report

PreviousVerification Result by UUIDNextError Report

Last updated 1 year ago

Transaction result reporting API

POST http://<enclave-endpoint>/v1/verifications/tx

This is an API that allows the Originating VASP to report the txHash value of the actual virtual asset transaction on the blockchain after confirming the Beneficiary through VerifyVASP.

Policy

  • The Originating VASP must report the transaction ID or TX hash of the actual virtual asset transaction to VerifyVASP through this API as soon as it is detected.

  • This allows the Beneficiary VASP to immediately identify which User Verification corresponds to the transaction.

Request Body

Request Body Examples
{
    "txHash": "8a54d58ca4100112a5430818776d74898f2232770bae03046862575cb851a042",
    "vout": "2",
    "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 a transaction to the blockchain.

txHash

string

true

"8a54d58ca4100112a5430818776d74898f2232770bae03046862575cb851a042"

Eigenvalue that can recognize VA transaction corresponding to the verification.

vout

string

false

"2"

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

  • The txHash value must follow the Blockchain Node Output format. For more information about the txHash format, please refer to the .

Response Body

Success case

Response Body Examples
  • 200 OK

{
  "result": true
}
Field Name
Data Type
Required
Description

result

boolean

true

The result of Transaction Hash value report request. Meaning: true=Success, false=Fail

Error Codes

Missing mandatory parameter

Response Body Examples
  • 400 Bad Request

{
  "code": "MISSING-VERIFICATION-UUID",
  "message": "`verificationUuid` is required."
}

The input of invalid verification UUID.

Response Body Examples
  • 400 Bad Request

{
  "code": "VERIFICATION-NOT-FOUND",
  "message": "Verification(9faab87c-54a6-4145-baa9-7a3a42d7410c) is not found"
}
Wallet address and transaction ID standards