VTS error 9159 Token validation failed

[Manievw]

Hi.

I'm trying to do a Get Transaction History to VTS but getting the following error back to our MAP.

Response from VTS code:401 message:{"responseStatus":{"status":401,"code":"9159","severity":"ERROR","message":"Token validation failed","info":""}}

All the research I've done points to the x-pay token in the header not being correct.

I've validated the process and can't find an issue. Any other suggestions?

[DianaTran]

Hi @Manievw,

I'll take a look and get back to you soon!

[DianaTran]

Hi @Manievw,

Please submit this query to developer@visa.com so that the issue can be investigated more thoroughly. VTS is a restricted product. You, as the merchant, should have previously provided information about the business in order to be provided with VTS product and content access. It is possible that you have not been provided access at this time.

[DianaTran]

Hey @Manievw - I haven’t received an update via email. Did you still need our help here? Were you able to figure it out? Let me know!

[dinc3b]

Yeah, You are right.

[DianaTran]

Hi @Manievw,

Just checking in to see if your questions were answered and if you need help with anything else?

If you are still experiencing an issue, please provide the following information:

1. End Point
2. Request Header
3. Request Body
4. Response Header (include the x-correlation-id)
5. Response Body

Using SoapUI, you can find the x-correlation-id in the Raw Tab of the response header.

[bhaikosalam]

Just started to have an issue with PXE booting machines can no longer download the operating system package during OSD Have stood up a new DP, same issue Regenerated boot images Recreated boot images Redistributed content Created new task sequences Re-enrolled in new IIS & DP certs From the basic glance, the MP cannot get the auth token from the DP. We use HTTPS in our environment and not NAAs. This had been working....obviously something changed, but I'm at a loss.

[DianaTran]

Hey @bhaikosalam,

Are you experiencing a Visa Token Service issue? 

To further investigate, please provide the following information:

1. End Point
2. Request Header
3. Request Body
4. Response Header (include the x-correlation-id)
5. Response Body

Using SoapUI, you can find the x-correlation-id in the Raw Tab of the response header.