E00114 Invalid OTS Token

[mbruxvoort]

Our site stopped accepting payments through the Accept.JS interface. The system was working until today.

Please HELP, your customer support team offered NO help and asked me to come to the community forum. What can I do to have payments come through again?

Thanks,
Mike

[mbruxvoort]

The Accept.JS code appears to work if we put a debug breakpoint in our Javascript code. Is there a timing related issue with Accept.js?

Can someone PLEASE help?

[RichardH]

Hello @mbruxvoort

When you say it stopped working, do you know when you noticed the gateway returning E00114?

Also, when adding a breakpoint, are you suggesting that when a breakpoint is used that after the JavaScript continues you receive a nonce?

Where is your breakpoint?

Richard

[mbruxvoort]

@RichardH,

We know for sure that the code was working on July 13. 

In debugging we have added a breakpoint in our Javascript code in the response callback after the nonce is received. The nonce is there and if the pause is greater that a couple of seconds it seems to work. 

We have been doing further debug on the server side. Without any pause on the client side our .net server side code is receiving the nonce from the front end. When we submit that to the authorize.net api via the SDK Nuget Package version 1.9.0 it seems like the nonce has not made it to the right spot on your end. Therefore our assumption is that it is just returning invalid even though it is a nonce that we received from Accept.js.

This is on our production site and we are NOT using the sandbox mode of Authorize.net.

We have considered putting retry logic around the .net sdk submit code, but that feels very dirty. 

Do you have a direct line or anything that we could contact you at?

Thanks,
Mike

[RichardH]

Hello @mbruxvoort

I've escalated this to our product support specialist team.  Since this is for your production account, please open an eTicket so this is properly tracked.  If you can provide the ticket number, I'll update the support specialists for them to take ownership.

Richard

[RichardH]

Hello @mbruxvoort

I received word back from a support specialist that this is a known issue, if you attempt to use a nonce immediately after receipt AND there are other internal conditions present at Authorize.Net.  The most common cause is the data for the nonce has not completed replication between systems.

Our engineers are working on a solution, but in the mean time adding a short delay after receipt of the nonce before using it to create a transaction will improve success. 

Richard

[mbruxvoort]

How long is a short delay? 1 sec or more? This would be user blocking which is an Important factor.

Mike

[RichardH]

I asked but did not get any specific guidance, but I think 1 second should be sufficient for most cases.

[mbruxvoort]

Richard,

Any word from the team when the issue will be resolved on your end? This seems very odd that we need to add a 1 sec delay to a user facing payment process.

Thanks,
Mike

[RichardH]

@mbruxvoort  Unfortunately I don't have any details on a solution, but it does involve making changes across multiple systems to ensure each are operating at peak efficiency.  

Richard