Hello,
Solved! Go to Solution
Hi,
Thanks for posting your inquiry. Can you please describe the error you are receiving? The cause of the issue could be that the key pair is ending up getting mismatched, when you are using the test environment, while your colleague uses the production environment. Or it might be that you are not copying the full key. After generating other keys, have you stuck with the original shared secret key, and changed API keys?
Thank you,
Diana
Visa Developer Team
Hello Diana, I'm having a similar problem, I've put my project into production, using the production URLs of both the button and the SDK, but using the Key API I get an error {"code": 401, "message": "Invalid API Key "} and if I use the Shared Secret I do not receive any error, but the button does not work and the API Frame is not launched.
thanks, David Fortoul
regards
Hi @fuerzaenti and @David,
Are you still experiencing an error? To resolve the 401 Invalid Api Key issue, we need to identify if this is a credential issue. Follow the steps in the API Key – Shared Secret (x-pay-token) for Visa Checkout guide using this link - https://developer.visa.com/pages/apikey_visacheckout, and test whether your credentials are good.
If the issue persists, please provide the following information:
1. End Point
2. Request Header
3. Request Body
4. Response Header (include the x-correlation-id)
5. Response Body
Using SoapUI, you can find the x-correlation-id in the Raw Tab of the response header.
I'm having that error too.
Please if you had rid of it let me know what you did or how you solved.