This topic has 3 replies, 2 voices, and was last updated 1 years, 6 months ago ago by Tony Rodriguez
Hi, I am using X Store child theme 1.0. I just installed a plugin to use Authorize.net. That’s my client’s gateway and apparently woocommerce doesn’t come set up for Authroize.net. I’ve got it in test mode and I enter my billing details and use Auth.net’s suggested credit card number: 4111 1111 1111 1111 with a vaild future expiry date and any 3-digit CVV number. When I try to process the credit card there is an error in red at the top of the page which reads:
User authentication failed due to invalid authentication values.
I don’t know if this is something to do with the theme or my plugin or woocommerce in general.Just looking for some help.
By the way, I did install Storefront theme and got the same error.
Well, I think I solved it. Not only did I not have a Public Client Key from Authorize.net (which I now do), but I found that my password manager (Dashlane) was replacing the Authorize.net keys with something else. Once I prevented Dashlane from autofilling these fields and with the correct info in them I was able to process a transaction.
Hello, @michaelmilauskas,
Great job on solving the issue! It sounds like you identified two important factors that were causing the problem. First, obtaining the Public Client Key from Authorize.net was crucial, and it’s great that you have it now. Additionally, you discovered that your password manager, Dashlane, was replacing the Authorize.net keys with incorrect information. By preventing Dashlane from auto-filling those fields and inputting the correct information, you were able to successfully process a transaction.
Your resourcefulness and attention to detail in troubleshooting the problem are commendable. If you have any further questions or need assistance with anything else, feel free to let me know.
Best Regards,
8Theme’s Team
Tagged: authentication, error, transaction, woocommerce, wordpress
The issue related to '‘Transaction fails, get “authentication values” error’' has been successfully resolved, and the topic is now closed for further responses