Visa Checkout API Key Issue

[mz]

Hello,

Integrating with Visa Checkout and a payments processor does not work if I use my API KEY.

If I just replace my API KEY with the Visa Checkout API KEY used by another developer, it works fine.

I went to the Visa Digital Solutions Profile and created a couple of other keys to try them, but they also failed. I created a new profile, and set it as a default. I filled in some information about my company, but that didn't seem to help. Not sure if any fields are mandatory or affect how things work.

Thank you!

Can anyone kindly shed some light on what I need to do to have this fixed? How can I figure this out?

[API_Products · Accepted 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

[David]

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

[API_Products]

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.

[fuerzaenti]

I'm having that error too.

Please if you had rid of it let me know what you did or how you solved.