Step 11) oVASP decrypts KYC/IVMS data with oUser’s private key

endpoint
`POST` {{baseUrl}}/api/v1/server/decrypt_ivms
params
"private_key": "0xbc454d37a96647a26aafdf15fc6a0eb81b7874c510d1b8b201ad2b5d785978cf"
"kyc_data": "BBrdMJb2anTBqL+nOyV+cB4Tla8RUUW22E58rECT+PNm7xral2xZRZVQXDa487Eqt2ptVH43EXck+c6KcqKHVs5QtC1J0s9XqZZIMqduY1PY4+SLjWxNGkRWxgYTkuA1PrjxjsfPnSM2O710+bJOOfyqLOF0+BSOAPYbD6Qha4lCCUrOmi3E3lAeROWoBsFD6bMLO7lDAGI="
private_key must begin with 0x
response (200 OK)
"{\"beneficiary\":\"beneficiary user kyc\"}"