Step 5) oVASP encrypts KYC/IVMS data with bUser’s public key

endpoint
`POST` {{baseUrl}}/api/v1/server/encrypt_ivms
params
"public_key": "0x04b3549cd59d458cbcdd0572ea15560ca8aefca8b383361076454464d0f24f9434bbbd331d0b75958b6ee99054a51708abe673f3f63ab2c049e61bcc2434cd7752"
"ivms_json": "{"originator":"originator user kyc"}"
The ivms_json above is simplified for demonstration & testing purposes.
response (200 OK)
{
    "data": "BD1jCMLjET4BWFm/t2oA1lR4KTuG1Zc6LCK3Li130VLKNYWTqV2tbpDnBTB9/B1c+FJvNBJZ+qgrcpLkWP4YrI2Q8cKJzNdpCUWuvr7dCkFXyGiXwPHkq6KorL/yoJFfqyNwBRGjkigPxKbMUQBvIEufG0901NKjm7bCtM0unEaC"
}