Reply
Member
Posts: 1
Registered: ‎12-23-2016

Accept.js E_WC_17:User authentication failed due to invalid authentication values.

I'm having a little trouble interpreting an error message i'm recieving while trying to implement Accept.js to replace our current Direct Post functionality on a Magento store.

 

E_WC_17:User authentication failed due to invalid authentication values.

 

Looking up this error on https://developer.authorize.net/api/reference/features/acceptjs.html

 

E_WC_17Please provide valid card holder name.

 

I've tried implementing the optional fields according to:

 

Property Type Description

cardNumberStringMust be a valid 13-16 digit card number. Required.
monthString2-digit month. Required.
yearString2-digit year. Required.
cardCodeString3 or 4-digit card validation value (CVV). Optional.
zipString20-character alphanumeric postal code. Optional.
fullNameString64-character alphanumeric cardholder name. Optional.

 

Still no luck, i've verified the Client Key, generated a new one as well. The API Login is correct as well. I'm also using the testing JS "https://jstest.authorize.net/v1/Accept.js"

 

Any idea what this error really means?

 

Thanks!

Administrator
Posts: 296
Registered: ‎11-03-2016

Re: Accept.js E_WC_17:User authentication failed due to invalid authentication values.

Hi @amazedchili,

 

In my experience, the E_WC_17 error is always because of a problem with the authorization credentials (the API Login ID or the Public Client Key). I don't know why the error codes in that documentation would steer you so wrong, but I'll look into that ASAP.

 

For further troubleshooting, re-verify the Public Client Key and the API Login ID. I know you said you've already reissued the client key, but double or triple-check everything to be sure.

 

The other common gotcha is to make sure that you're using your test credentials if you're calling the test script. Since you're calling the test script that runs in the sandbox environment, you have to have a sandbox account with it's own credentials. Live credentials won't work on sandbox or vice versa. When you're managing or reissuing the public client key, make sure you're logged in to https://sandbox.authorize.net.

 

Let us know how that goes!

-Aaron

Aaron Wright
Developer Evangelist - Authorize.Net

Follow Authorize.Net developer news on Twitter!
Member
Posts: 9
Registered: ‎10-08-2014

Re: Accept.js E_WC_17:User authentication failed due to invalid authentication values.

I'm having the same exact problem. The error message I'm seeing is 

 

E_WC_17:User authentication failed due to invalid authentication values.

 

The code, E_WC_17, as the documentation claims, is for "Please provide valid card holder name." but the message that accompanies it is related to authentication. 

 

I've also tried regenerating my sandbox transaction key, with no change in response.

 

I wonder, do we need to be setting some client-side equivilent of x_test_request to test in order to use the sandbox accounts?

Administrator
Posts: 296
Registered: ‎11-03-2016

Re: Accept.js E_WC_17:User authentication failed due to invalid authentication values.

Hi @jenlampton,

 

There are some known issues with getting the right code at the right time for some of the error reporting in Accept.js, but those should be fixed soon. In the meantime, if the text you're receiving states an authentication error, it's likely that your issue is indeed related to authentication.

 

There's no test transaction flag that needs to be sent to use Accept.js in the sandbox. The only thing you need to do is load the script from the test location (https://jstest.authorize.net/v1/Accept.js).

 

The important thing to remember, though, is that you're not using your regular sandbox transaction key to use Accept.js. If that's what you're trying with Accept.js, that would explain the error.

 

Any credentials you use for Accept.js will be exposed in the browser, so we have you use a special client key that's only for Accept. That way, someone taking your credentials out of the browser would only be able to use them to generate card tokens, not for any transaction processing or anything like that.

 

We call his special client key the "public client key". If you haven't already, go back to the documentation and read through the section "Obtaining a Public Client Key". That will walk you through the steps of generating a public client key to use with Accept.js.

 

Hope that helps!

-Aaron

Aaron Wright
Developer Evangelist - Authorize.Net

Follow Authorize.Net developer news on Twitter!
Member
Posts: 9
Registered: ‎10-08-2014

Re: Accept.js E_WC_17:User authentication failed due to invalid authentication values.

Thanks Aaron, I think that was it! For some reason I had assumed the public client key and the transaction key were the same thing, but the documentation is very clear. I've generated a new public client key for the sandbox account and I'm not getting the error anymore. Thank you!

Administrator
Posts: 296
Registered: ‎11-03-2016

Re: Accept.js E_WC_17:User authentication failed due to invalid authentication values.

No problem @jenlampton. The documentation is clear, but only if you already know those are two different things. A few people are still getting caught by that, though, so I'm trying to find ways to make it even more clear.

 

Thanks for the feedback!

-Aaron

Aaron Wright
Developer Evangelist - Authorize.Net

Follow Authorize.Net developer news on Twitter!