Intermittent Invalid OTS Token Errors (E00114)

[DoomHamster]

We have started to get intermittent "Invalid OTS Token" errors today when creating a new user profile.  Most of our attempts to create a user profile work fine and, prior to today, we recieved an occaisional error every couple of weeks.  We have found that if a customer gets this error (nine so far today) and they refresh the checkout page to initiate a new transaction, their next attempt works fine.

Is anyone else seeing an uptick in these errors today?  Any good way to mitigate?  

[RichardH]

@samablews

Do you know when approximately this problem started with your production account?  Also, if you can provide the case #, we can escalate your issue.

Richard

[dbroome]

This has begun again this morning at 7:41 central.  I have gotten this issue periodically with one or two errors here or there.  Today it has been consistent, happening 23 times in the last hour.

I will be calling support, though as always I suspect that will be a waste of time on this issue.

[willimus]

We too have seen a significant increase in "E00114 Invalid OTS Token" errors this morning. I'm now submitting a support ticket about this. We've received over 150 instances in the past 12 hours.

Did the "1 second delay" workaround outlined in this older post solve this issue for anyone?
https://community.developer.authorize.net/t5/Integration-and-Testing/E00114-Invalid-OTS-Token/td-p/5...

[DoomHamster]

Looks we had a few between 0646 and 0700 MDT but none since then.

[oakleydokley]

When you call support please make sure you press option 4 to get an integration specialist. Not all reps are trained in integration. 

[oakleydokley]

When you call support please make sure you press option 4 to get an integration specialist

[oakleydokley]

CODE: E00114

EXPLANATION: Invalid OTS Token.

DESCRIPTION: The specified OTS Token is invalid.

INTEGRATION SUGGESTIONS: E00114 is returned when the payment token is not found on our server, usually because the token has already been submitted once. The payment token is a one-time use token.

OTHER SUGGESTIONS: Try searching for the transaction in the sandbox Merchant Interface or the live Merchant Interface depending on whether the error was triggered by a test transaction or a live transaction. If the transaction exists, it was probably sent twice. When the token was submitted the first time, the token was valid and the transaction was processed. The second time the transaction was submitted, the token was no longer found because it had already been used. 

If the above doesn't describe your situation, it is possible that there is a problem retrieving the token from the token service. Please contact Merchant Support for assistance.
*PRESS OPTION 4 FOR INTEGRATION*