VerifyVASP
Search…
Welcome
Change Log
Getting Started
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
Getting Started with VerifyVASP
Reference
Enclave API Reference
VASP API Reference
IVMS101 Guide
Glossary
Powered By GitBook
Change Log
​

Version 1.4.1

Enclave Bugfix

  • Fixed: low probability that user verification result not stored properly in the enclave DB.

Version 1.4.0

Major change

  • Modified to allow interoperability with CODE.

Enclave

  • VASPs using CODE protocol are also displayed in the list when the list lookup API is called.
  • ​VASP List API CountryCode and protocol items have been added in the return value..
  • ​VASP List API Added new vaspStatus value (INTEROPERATED) in return value.

Version 1.3.9

Enclave Bugfix

  • Fixed a bug in the logic to remove information from the enclave when the user-verified VASP API returned information that was not in requiredBeneficiaryInfo .

Version 1.3.6

Enclave Bugfix

  • The verification failure issue with UNDEFINED-ERROR code on user verification VASP API request without ivms101 data fields has been resolved.

Version 1.3.4

Enclave Bugfix

  • An error occurrence from commands table on the Oracle database has been removed.

Version 1.3.2

Enclave Bugfix

  • The problem has been fixed that the authorization header value is misconfigured when VEGA_VERIFICATION_AUTHORIZATION_TOKEN variable is not configured.
  • The type mismatch issue on the count(returned in string type) value in response payload of Verification Result List API has been fixed.

Version 1.3.0

Major changes
  • The user address verification API was expanded to a user 'account' verification API.
    • Now it supports a selective name matching verification in addition to the existing wallet address check.
    • See User Account Verification API for more details.
  • Utilize a robot VASP for more test cases coverage
    • Now you can experience more various error case handling when you test the withdrawal verification with the robot VASP.
    • See Robot VASP page for more details.

Enclave API

  • API policy of Transaction Result Report API has been updated.
    • It requires to call this API as soon as the VASP finds the transaction ID (txHash) now, in contrast to the former version of the guide that required calling it after the transaction finality check.
  • Error code specifications have been provided for each API.

VASP API

  • ​User Verification API implementation policy has been updated.
    • Only required beneficiary information fields need to be filled out.
  • verificationUuid field is newly added to the request payload of User Verification API.
  • ​Callback API implementation policy regarding the idempotent has been added.
  • ​User Account Verification API was updated to verify the beneficiary name in case of the transaction amount exceeds the legal baseline.

Enclave

  • The name of an environmental variable has been changed as User Address Verification API is changed to User Account Verification API.
    • AS-IS: VEGA_VERIFICATION_ADDRESS_API_PATH
    • TO-BE: VEGA_VERIFICATION_ACCOUNT_API_PATH
  • A new environment variable for VASP API Authorization Token header setup has been added.
  • The index definition of commands table updated.
    • A new column created_at is added to the index.
    • See Database page for more details.

Version 1.2.0

Major changes

  • Some enclave APIs were changed to work asynchronously.
    • Data that was delivered with synchronous API response is now delivered through the callback VASP API.
Why did VerifyVASP introduce asynchronous processes?
  • Specific personal data specification requirements now can be designated in the request phase to VASP.
    • Refer to the newly added code specification to designate the data requirements.
Background of using personal data field code
  • VASP API implementation policy updated.
VASP API policies
  • Now VerifyVASP supports a transaction in a single VASP, meaning a VASP can be both the originating VASP and beneficiary VASP of the transaction.
Supporting transaction inside a VASP

Enclave API

VASP API

  • Callback API is newly added.
    • The API is for getting notifications of the processing result asynchronously.
    • Strongly recommended implementing the callback API: Polling way of implementation for all the processing transaction results without enough care might be a burden to both VASP itself and the VerifyVASP network.
  • Implementation policies for each VASP API were updated.
  • Error codes from the user verification API are now provided.

Enclave

  • The database table definition was updated.
    • Added: commands table
    • Modified: verifications table
      • message column is added
  • An environmental variable was added
    • VEGA_VERIFICATION_CALLBACK_API_PATH: A variable for callback API endpoint setup

IVMS101

  • IVMS101 Message Format Guide was updated.
    • Address field expansion to support multiple addresses in addition to the parent address (e.g. XPR, EOS)
    • The geographic address policy now requires corporations to fill out both headquarters address and branches.

Bugfix and minor updates

  • The problem in setting database port number adjustment has been fixed.
  • The endpoint scanning process during enclave boot now checks the endpoints of transaction status checking API and address verification API too.
  • A diagram describing the transaction state transition has been added to the transaction status check API page.
  • Parameter names have been changed.
    • The query parameters for Verification Result List API are modified as follows. - fromAccount --> originatorAccountNumber - toAccount --> beneficiaryAccountNumber

Version 1.1.0

Consol Site

  • The Korean Site is open.
    • Only the staging environment and site are open; the production environment and site are to open soon.
  • The address of the Korean VerifyVASP console site updated (https://kr.verifyvasp.xyz).
  • Korean VASPs need to register to the Korean console site newly.

Central Server

  • The central server endpoint for the Korea region was added.

Enclave Server

  • Enclave server - version updated (VerifyVASP/enclave:v1.1.0)
  • Enclave database - table definition updated.
    • verifications
  • Enclave database - new tables
    • counter_party_keys
    • own_keys
  • Enclave database applies encryption to some columns
  • Environment variables added
    • VEGA_ENCLAVE_PUBLIC_ENDPOINT
    • VEGA_VERIFICATION_ADDRESSES_API_PATH
    • VEGA_VERIFICATION_TRANSACTION_API_PATH
    • VEGA_VERIFICATION_AUTHORIZATION_TOKEN
    • VEGA_ENCRYPTION_KEY_BASE64
    • VEGA_DECRYPT_API_ENDPOINT
    • VEGA_PUBLIC_KEY_TTL
    • VEGA_LOG_LEVEL

VASP API

  • VASP side need-to-implement APIs were added
    • User address verification API (mandatory)
    • Transaction status checking API (mandatory)
    • Decrypting database encryption key API (recommended)
  • Specification update for user verification API
    • symbol, amount fields moved into assetInfo object

Enclave API

  • API version information was added to all API paths.
  • Updated APIs
    • VASP List API
      • The list is changed to include VerifyVASP members only by default.
      • includesAll query parameter is now supported.
      • The response provides more detailed information including VASP health status.
    • User verification API
      • request body modified
  • New APIs are now supported.
    • Address verification API
    • Error report API
    • Transaction status check API

기타

  • A security guide page was added.
  • IVMS101 standard guiding page was added.
  • IVMS101 message format guide page was added.
Previous
Welcome
Next - Getting Started
Product Overview
Last modified 2mo ago
Copy link
On this page
Version 1.4.1
Version 1.4.0
Version 1.3.9
Version 1.3.6
Version 1.3.4
Version 1.3.2
Version 1.3.0
Version 1.2.0
Version 1.1.0