topic Re: Accept.js Example showing Transaction Unsuccessful in Integration and Testing

Accept.js Example showing Transaction Unsuccessful

highnoon — Sun, 21 Aug 2016 15:22:32 GMT

Hello World,

I am trying out the new Accept.js integration. Everything is installed. and the foodie demo page is loading.

I cannot seem to get a transaction to return as Successful though.

In my browser debug console (using Firefox 47.01 on Redhat) I see the following:

OPTIONS
XHR
https://apitest.authorize.net/xml/v1/request.api [HTTP/1.1 200 OK 342ms]
POST
XHR
https://apitest.authorize.net/xml/v1/request.api [HTTP/1.1 200 OK 608ms]
COMMON.ACCEPT.INAPP.PAYMENT acceptJSCaller.js:75:3
9471792038153068005001 acceptJSCaller.js:76:3
POST
XHR
https://devc1.bountifulbaskets.org/anettest/accept-sample-app/transactionCaller.php [HTTP/1.1 200 OK 723ms]
Success acceptJSCaller.js:53:3
{"messages":{"resultCode":"Error","message":{"code":"E00116","text":"OTS Token access violation"}},"transactionResponse":{}}

I have also tested the adding of a shipping address in the demo script and that seemed to work without a hitch so I am confident the API/TRANSACTION bits are working.

Any ideas what the "OTS Token access violation" error means? Is there some additional sandbox config I need to set for this to work?

Thanks,

Highnoon

Re: Accept.js Example showing Transaction Unsuccessful

Joy — Mon, 22 Aug 2016 14:56:36 GMT

Hi,

The error E00116 for OTS Token access violation, this error generally indicates that a token is being used by a different merchant than the one that created. One possible reasons is if you generated a token on production and tried to use it on sandbox.

Thanks,

Joy

Re: Accept.js Example showing Transaction Unsuccessful

highnoon — Mon, 29 Aug 2016 17:53:48 GMT

Thank you for the response Joy.

I managed to get things working. I determined that the example code was not quite as "drop-in" as expected. After changing the transaction ID and Agent ID information in the scripts, things started working.

Best,

Highnoon