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