AnsweredAssumed Answered

Authorization API request | Token not found

Question asked by satishweb on Apr 10, 2019
Latest reply on Apr 12, 2019 by daniperea
  • Comment • 1

Hi,

 

I'm a Software Engineer with Skillz. I wish to know the pre-live url/conditions to accept/process eProtect requests.

Right now with every request to litle I'm getting a response code - 822 / Token not found. However, Test cases 14 and 15 in Table 2-9 in the integration guide send the correct response codes. For example here's the response that I get for the failure: 

 

failed an auth with order ID 1520190410235644, response code 822, message Token was not found, and json {"response":"822","message":"Token was not found","authCode":null,"avsResult":"34","cardValidationResult":null,"litleTxnId":83013463953900025,"orderId":"1520190410235644","postDate":"2019-04-10T00:00:00Z"}

 

With  "paypage_registration_id": "cnhJN241WWM1cFBoUXU3TkF0S3haYTNkc3VyZmc3OERkM2U1T1dKN1NRekovWXc3d1Avck9lRGIyRkxLak54aQ=="

 

Also, the url we send this request to is: 'https://transact.vantivpostlive.com/vap/communicator/online'

It'll be great to step into the right direction and resolve/understand the issue. 

 

Please let me know.

 

Thanks!

daniperea
daniperea Apr 12, 2019 2:26 PM
Correct Answer

Hi Satish,

In prelive, you can't use the default PayPage ID value for eProtect with your unique prelive test account. You can contact your RM (I think yours should be Alicia Volker) and ask for eProtect to be set up on your prelive account. Then you can use your own PayPage ID and the tests will work.

 

Many thanks!

See the reply in context
No one else had this question

Outcomes