Encrypted IVMS State Machine

[ivms_status]

Tracks the state of encrypted KYC/IVMS data sent between peers. These can be sent multiple times and in any sequence. Note: If an ivms_state_code is included in the KYC template, no new KYC/IVMS webhook event is triggered. It is thus recommended to send the final version of your KYC/IVMS before accepting or rejecting a transfer.

To view the states in the Veriscope web-app, go to the Backoffice > KYC Templates section, choose a template and scroll down to the 4th table.

oVASP Veriscope Statuses

State Description

START

…​

BE_ENC_SENT

Beneficiary encrypted KYC/IVMS data has been sent to oVASP

BE_ENC_RECEIVED

Beneficiary encrypted KYC/IVMS data has been received by oVASP (based on 200 OK response from oVASP backend)

BE_ENC_FAILED

Beneficiary encrypted KYC/IVMS data has not been received by oVASP
ivms state

bVASP Veriscope Statuses

State Description

START

…​

OR_ENC_SENT

Originator encrypted KYC/IVMS data has been sent to bVASP

OR_ENC_RECEIVED

Originator encrypted KYC/IVMS data has been received by bVASP (based on 200 OK response from bVASP backend)

OR_ENC_FAILED

Originator encrypted KYC/IVMS data has not been received by bVASP
ivms state