I'm currently investigating the VCO issue your experiencing and I'll get back to you soon.
Can you please confirm if you have used the new API key that we have created for your account? When you use the new API key, this should be able to resolve your issue.
Please let us know if you have resolved the issue is resolved yet?
See the below note that I have previously sent you, following is the API key you can try.
We currently have a bug associated with the API key creation API from the VDP portal (which is a merchant created self API Key). Therefore, as a temporary solution we have created a new API key for you.
Following is the key- 3T8ORAVKLGY1XEEH8ZOI21DQp0jMdt9o6VaxQK9IsdD61N3dM
Also, please use HMAC(XV2) signature type.
No, Still facing the same issue even with the new key. Is there a timeline for the general fix for the bug ?
Thanks for letting us know. We're working to help resolve your issue and I'll get back to you with the next step soon. Also, regarding the timeline for the bug fix, I'll take a look and get back to you soon on that, as well.
Thanks for the x-correlation-id.
I wanted to provide you with a quick update on this issue.
1. Our backend team has identified the fix and they are going to do the code fix in the October release.
2. Meanwhile, we have made some temporary changes on the account settings specially for API Key Segregation level. We have tested and validated this temporary solution and it works for now.
SO please use the API key- 3T8ORAVKLGY1XEEH8ZOI21DQp0jMdt9o6VaxQK9IsdD61N3dM
Also, after you use this API key, please share your results with us and let us know if your issue is resolved. Thanks!