cancel
Showing results for 
Search instead for 
Did you mean: 

error: E00114 testing on sandbox

I'm working on an accept.js integration with my sandbox account.

 

I got the web side to return the transaction code. At this point, the response is literally from the sample code provided.

 

function useOpaqueData(responseData) {
    // This is where you would set the data descriptor & data value to be posted back to your server
    console.log(responseData.dataDescriptor);
    console.log(responseData.dataValue);
    alert(responseData.dataValue);
}

 

 

While I was working on the backend card charge routines I used the 'dataValue' and got an E00114 error.

 

The posted json:

 

{
	"createTransactionRequest": {
		"merchantAuthentication": {
			"name": "name",
			"transactionKey": "Key"
		},
		"transactionRequest": {
			"transactionType": "authCaptureTransaction",
			"amount": 5,
			"payment": {
				"opaqueData": {
					"dataDescriptor": "COMMON.ACCEPT.INAPP.PAYMENT",
					"dataValue": "mynoncehere"
				}
			}
		}
	}
}

The error response

 

{"transactionResponse":{},"messages":{"resultCode":"Error","message":[{"code":"E00114","text":"Invalid OTS Token."}]}}

 

 

When i reran the web side to get a new nonce, I got the same dataValue back. Repeatedly, even if I changed the credit card number.

 

That doesn't seem right.

 

So, a) is there anyway to get more info about what's wrong wtih the OTS Token.

       b) why do I keep getting the same nonce back?

 

Thanks!

leehinde
Contributor
Contributor
2 REPLIES 2

Hello @leehinde

 

Are you still experiencing this issue?  

 

Richard

RichardH
Administrator Administrator
Administrator

Hi,

 

It's working now. Thanks.

 

When it wasn't working the response was quick. Now that it is working, I'm back to 30-40 second response times. This is on the 2nd step, the post of the sale data with the nonce.

 

I understand this delay is apparentlhy unique to my setup somehow.