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

endpoint
`POST` {{baseUrl}}/api/v1/server/encrypt_ivms
body
"public_key": "0x0409e8d4a705e9dff75c5d082b601a8326b77c61b763df76ec242f24b85abd070fcada35335033ec0bfe8308dfcf0ea551b0193836219bbb535f059ade08140772"
"ivms_json": "{"originator":"test kyc data 0x96ee37"}"
The ivms_json above is simplified for demonstration & testing purposes.
response (200 OK)
{
    "data": "BGqavksg9ZzUjsAr8AcgxQQ3BCNqBdijdk5kv4YJzDVkb7l5386Z59VGGLJbjwX4oxmrAVk4FILLdtwXczFVk/Lz5jgseoidTxubmIyZ5XN6xGFBgRvYim68G0WQarY/GEOTlMIfyWaFIofLtG3rAHkRIn5aIJnxbGT4wTrwZM6gNcXiS07rHWlDJmlIL+XOm/n1WU8D3oA="
}