topic Re: User authentication failed due to invalid authentication values. in Integration and Testing

User authentication failed due to invalid authentication values.

mwex501 — Thu, 19 Oct 2017 14:43:03 GMT

Hello:

I created an Accept hosted integartion. This integration works fine in sandbox mode, but fails in LIVE mode with the following error:

User authentication failed due to invalid authentication values.

I verified that my transactionKey and api_login_id are correct and that I am using the correct URL.

The settings on the auth.net account are set to LIVE.

What else could be the issue? I see banter about requiring a signature key also, but nothing in the docs.

Below is the code for the request:

<getHostedPaymentPageRequest xmlns="AnetApi/xml/v1/schema/AnetApiSchema.xsd">
<merchantAuthentication>
        <name>{hidden api_login_id}</name>
        <transactionKey>{hidden transaction key}</transactionKey>
</merchantAuthentication>
<transactionRequest>
        <transactionType>authCaptureTransaction</transactionType>
        <amount>7.94</amount>
<order>
<invoiceNumber>138437174</invoiceNumber>
</order>
        <billTo>
         <firstName>MARK</firstName>
         <lastName>WEXLER</lastName>
         <company>WHIRLWIND INC</company>
         <address>9811 ASHBURTON LANE</address>
         <city>BETHESDA</city>
         <state>MD</state>
         <zip>20817</zip>
         <country>US</country>
      </billTo>
      <shipTo>
         <firstName>MARK</firstName>
         <lastName>WEXLER</lastName>
         <company>WHIRLWIND INC</company>
         <address>9811 ASHBURTON LANE</address>
         <city>BETHESDA</city>
         <state>MD</state>
         <zip>20817</zip>
         <country>US</country>
      </shipTo>

</transactionRequest>
<hostedPaymentSettings>
        <setting>
                <settingName>hostedPaymentBillingAddressOptions</settingName>
                <settingValue>{"show": true, "required":true}</settingValue>
        </setting>
        <setting>
                <settingName>hostedPaymentButtonOptions</settingName>
                <settingValue>{"text": "Pay"}</settingValue>
        </setting>
        <setting>
                <settingName>hostedPaymentReturnOptions</settingName>
                <settingValue>{"showReceipt" : false, "url":"https://www.breyerhorses.com/plugins/authnet_iframe_communicator.html","urlText":"Continue","cancelUrl":"https://www.breyerhorses.com/plugins/authnet_response.php?action=cancel","cancelUrlText":"Cancel"}</settingValue>
        </setting>
        <setting>
         <settingName>hostedPaymentShippingAddressOptions</settingName>
         <settingValue>{"show": false, "required":false}</settingValue>
</setting>
        <setting>
                <settingName>hostedPaymentStyleOptions</settingName>
                <settingValue>{"bgColor":"#B00"}</settingValue>
        </setting>
        <setting>
                <settingName>hostedPaymentIFrameCommunicatorUrl</settingName>
                <settingValue>{"url": "https://www.breyerhorses.com/plugins/authnet_iframe_communicator.html"}</settingValue>
        </setting>
</hostedPaymentSettings>
</getHostedPaymentPageRequest>

Re: User authentication failed due to invalid authentication values.

daskjeeves — Fri, 06 Jul 2018 17:55:00 GMT

This is crazy. The lack of support from this company is seriously amazing. What could go wrong when you only have to change the login ID, transaction Key, and post URL? Apparently everything...

Re: User authentication failed due to invalid authentication values.

Anurag — Sat, 07 Jul 2018 04:12:01 GMT

Hi @daskjeeves

Can you provide more details on the issue faced by you ?

please do note to use the correct url for sandbox and prod env as

https://developer.authorize.net/api/reference/index.html#authentication

Thanks

Re: User authentication failed due to invalid authentication values.

daskjeeves — Mon, 09 Jul 2018 14:53:31 GMT

Anurag, I took your course a few weeks ago and learning more about PCI compliance was the reason we decided to switch over to Accept Hosted and your form so our backend code doesn't have to touch the data.

The test version works perfectly, everytime. The only thing I do to switch to live is switch the login ID, transaction key, and POST url. Where is the endpoint supposed to go, in a script tag at the bottom of the page? Because I have certainly tried that, and also tried it as the form POST, to no avail.

The documentation just seems to be lacking, and based on a lot of the stuff I am reading even on this forum, it has been for years.

Could you please list every step that needs to be taken to switch from the test version to the live version?

Re: User authentication failed due to invalid authentication values.

Anurag — Tue, 10 Jul 2018 05:43:20 GMT

Hi @daskjeeves

Thanks for joining the Webinar . We are going to do updates to Accept Hosted Documentation soon to make it clearer .

The urls to be used for step 1 for calling getHostedPaymentPageRequest

Sandbox API Endpoint: https://apitest.authorize.net/xml/v1/request.api

Production API Endpoint: https://api.authorize.net/xml/v1/request.api

For Step 2 where you need to post the hosted token , the urls are as below

FORM POST URLS:

Sandbox: https://test.authorize.net/payment/payment

Production: https://accept.authorize.net/payment/payment

if you still having issues please reach out to me on developer_feedback@authorize.net and we will look into it further .

Thanks

Anurag

Re: User authentication failed due to invalid authentication values.

daskjeeves — Tue, 10 Jul 2018 16:23:48 GMT

I have been trying for nearly a week and had live chats/phone calls with at least 8 authorize.net employees, and still no resolution. It shouldn't be this difficult, especially for the company providing the tool

Re: User authentication failed due to invalid authentication values.

lasertoast — Wed, 02 Jan 2019 12:25:32 GMT

I am having this same problem. Why does this thread end with no solution?

Re: User authentication failed due to invalid authentication values.

mrFreelancer201 — Sat, 13 Apr 2019 16:26:01 GMT

Has there still been no resolution? If anyone has found one pleas let me know.

I can't even use the sample merchant verification (PHP) script properly. It also throws a...

ERROR : Invalid response Response : E00007 User authentication failed due to invalid authentication values.

SOMEONE please respond? @administrator ?

Re: User authentication failed due to invalid authentication values.

RichardH — Sat, 13 Apr 2019 18:01:18 GMT

@mrFreelancer201 @lasertoast

An E00007 is only caused when the API Login, Transaction Key or corresponding endpoint are incorrect.

This may be simple, but let's walk through and confirm everything:

Sandbox:

Set your endpoint to https://apitest.authorize.net/xml/v1/request.api
Login to https://sandbox.authorize.net, confirm your API Login and obtain a new transactionKey; or use the sample credentials shown below
Send the following:

<authenticateTestRequest xmlns="AnetApi/xml/v1/schema/AnetApiSchema.xsd">
	<merchantAuthentication>
		<name>78BZ5Xprry</name>
		<transactionKey>8s2F95Q7brhHd7Tn</transactionKey>
	</merchantAuthentication>
</authenticateTestRequest>

If that is successful, then try production

Set your endpoint to https://api.authorize.net/xml/v1/request.api
Login to https://account.authorize.net, confirm your API Login and obtain a new transactionKey
Send the following:

<authenticateTestRequest xmlns="AnetApi/xml/v1/schema/AnetApiSchema.xsd">
	<merchantAuthentication>
		<name>*</name>
		<transactionKey>**</transactionKey>
	</merchantAuthentication>
</authenticateTestRequest>

Richard

Re: User authentication failed due to invalid authentication values.

mrFreelancer201 — Sun, 14 Apr 2019 04:28:30 GMT

So then what about a "E_WS_21" error? I'm honestly not concerned about the Merchant Verification Script but rather, the biggest issue I'm having is that error when attempting to fetch a token via Accept.js.

I'm using the hosted form and I'm 1000% sure I'm using proper API Login ID and Public Client Key. Infact, re-generated the client key just to be sure. I essentially lifted the sample codes as described here: https://developer.authorize.net/api/reference/features/acceptjs.html#Using_the_Hosted_Payment_Information_Form

However, it works perfectly fine in sandbox and I'm able to fetch a token, thus continue with Nonce.

Here's my exact code for obtaining a token...

<div class=\"authnetAcceptHostedWrapper\" data-open=\"0\">
<input type=\"hidden\" name=\"dataValue\" id=\"dataValue\" />
<input type=\"hidden\" name=\"dataDescriptor\" id=\"dataDescriptor\" />
<div type=\"button\" class=\"AcceptUI payByAcceptHostedSubmit\" data-progress=\"0\" data-default=\"Click Here to Pay by Credit Card\"
data-billingAddressOptions='{\"show\":true, \"required\":false}'
data-apiLoginID=\"{$apiLoginID}\"
data-clientKey=\"{$apiClientKey}\"
data-acceptUIFormBtnTxt=\"Continue\"
data-acceptUIFormHeaderTxt=\"Secured Payment Information\"
data-responseHandler=\"AuthnetAcceptHostedResponseHandler\">
Click Here to Enter Credit Card Details
</div>
<img class=\"authnetAcceptHostedCCEnteredIcon\" src=\"images/icon_checkmark_1.png\">

<script src=\"js/module_authorizenet_accept_hosted.js\"></script>
</div>
{$authnet[$this->mode]}

$authnet[$this->mode] points to "https://js.authorize.net/v3/AcceptUI.js"

That's as strait forward as it gets. Please tell me what I'm doing wrong for Live mode?

Re: User authentication failed due to invalid authentication values.

mjp1 — Tue, 10 Sep 2019 16:04:02 GMT

So not sure if anyone figured this out already, but I was running into this issue as well. I was using their example code/API. Everything worked fine in sandbox mode but would fail with a authentication error with the production keys. I had to dig through their SDK code and found out the reason it was failing is because their code defaults to using the sandbox url. I use node so it might be slightly different for everyone else, but I went into the authorizenet folder > apicontrollersbase.js then changed this line this._endpoint = constants.endpoint.sandbox; to this this._endpoint = constants.endpoint.production; and everything started working correctly.

It is really annoying that I have to go into their code and find that line and change it in order for it to work. It should just force me to put in the url that I want to use, or accept the url as a parameter and then defualt to the sandbox if it is not provided. Hope that helps anyone who stumbles across this.