VCES returning error "statusCode":"201","statusDescription":"

[lzepp81]

Hi,

I'm trying to perform test eligibility. Please make sure that I'm using the correct data from "Test Data" section and "Configuration"

1) Vendor-Id is taken from: Dashboard > Configuration > Visa Card Eligibility Service

2) Permanent Account number is taken from: Test Data > VCES > Validate (there are four accounts that can be used for tests)

Request:

{
"permanentAccountNumber": "4000000000000013",
"requestTimeStamp": "6/14/2020 10:28:00 AM",
"correlationId": "1234567890",
"vendorUniqueId": "10114_TstVDPPgm1"
}

HTTP Request Headers

Accept:application/json
Authorization:Basic UEZLNzI2RDJYU1gzVjlaQjBZMl....
Content-Type:application/json

 Respone:

{
    "statusCode": "201",
    "statusDescription": "Vendor Unique Id is invalid",
    "CorrelationId": "1234567890",
    "responseTimeStamp": "6/14/2020 10:32:07 AM",
    "eligibilityLevel": "0",
    "cardId": "0"
}

 HTTP Response Headers:

Server →nginx
Date →Sun, 14 Jun 2020 10:32:07 GMT
Content-Type →application/json;charset=utf-8
Content-Length →179
Connection →keep-alive
X-SERVED-BY →l73c018
X-CORRELATION-ID →1592130727_897_209025045_l73c018_VDP_WS
X-Backside-Transport →FAIL FAIL,FAIL FAIL
Cache-Control →no-cache, no-store ,no-cache, no-store, must-revalidate
Pragma →no-cache
Expires →-1
X-OPNET-Transaction-Trace →a2_f4991736-0f27-4d82-912c-35f094236d7c-4068-223
X-Powered-By →ASP.NET
X-Content-Type-Options →nosniff
X-Frame-Options →SAMEORIGIN
X-XSS-Protection →1; mode=block
Content-Security-Policy →default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline';
X-Global-Transaction-ID →1bedc9b25ee5fca7f807f4f5
X-APP-STATUS →400
Strict-Transport-Security →max-age=2592000;includeSubdomains
X-Cnection →close

I've timezone as GTM +04:00. When I send request and set timestamp as 4 hours back, otherwise I'm getting timestamp related error. It seems that something wrong with my vendor id on the server. 

As for certificate check, everything is ok here.  The Hello World project is working well! Also, I'm able to retrieve card information using card API (please find below)

Kindly help me to solve this issue. Thanks, 

[API_Products]

Hey @lzepp81,

I'm happy to help you resolve the issue. I'll take a look and get back to you soon. 

[lzepp81]

Hi Diana,

Do you have any update?

[API_Products]

Hey @lzepp81,

Can you please confirm the endpoint and the API that you are receiving an error on? Your Postman Endpoint (https://sandbox.api.visa.com/dcas/cardservices/v1/cards) is the Endpoint for DPS Card and Account Services API, however, it appears that the subject of your question is on a different API called Visa Card Eligibility Service (VCES). Please make sure to use the API product's Endpoint that is listed on the product's API Reference page for your sandbox testing or you will receive an error.

I've included links to both API products' API reference pages for you to review and confirm which API product you are testing and receiving an error on.

Visa Card Eligibility Service - https://developer.visa.com/capabilities/vces/reference

DPS Card and Account Services - https://developer.visa.com/capabilities/dps-card-and-account-services/reference

[lzepp81]

Hi Diana,

I think you got me wrong. If you look at the screen and description that I have shared, I have stated that card API working that is why I shared the screen, in order to show that my HTTP headers are correct. The error that related to vendor is returned for eligibility check service. What I’m saying is that I’m using right endpoints, please read my post once again more carefully please.

[API_Products]

Hey @lzepp81,

Thanks for the clarification. Can you please share with us the endpoint you are using for VCES?  

[lzepp81]

This is print-screen from Postman, URL is the VCES endpoint, below is the response with incorrect vendor id. 

Also, below HTTP Requests Headers:

Accept:application/json
Authorization:Basic UEZLNzI2RDJYU1gzVjlaQjBZMlUyMVJPMEJ2bmY2dFZHd0hMMHN2RVNKal9KVHNTRTpSZTQ4ZE1JMXhEazJvdmcxTzA2UE96UU9WU3YyMmY1NTAyMjJ4
Content-Type:application/json

And HTTP Response Headers:

Server →nginx

Date →Wed, 17 Jun 2020 19:27:49 GMT

Content-Type →application/json;charset=utf-8

Content-Length →178

Connection →keep-alive

X-SERVED-BY →l73c017

X-CORRELATION-ID →1592422069_546_1100355782_l73c017_VDP_WS

X-Backside-Transport →FAIL FAIL,FAIL FAIL

Cache-Control →no-cache, no-store ,no-cache, no-store, must-revalidate

Pragma →no-cache

Expires →-1

X-OPNET-Transaction-Trace →a2_702c146a-8acc-465d-a34c-299b205185f5-9356-97

X-Powered-By →ASP.NET

X-Content-Type-Options →nosniff

X-Frame-Options →SAMEORIGIN

X-XSS-Protection →1; mode=block

Content-Security-Policy →default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline';

X-Global-Transaction-ID →448482cb5eea6eb52cf821c5

X-APP-STATUS →400

Strict-Transport-Security →max-age=2592000;includeSubdomains

X-Cnection →close

[API_Products]

Hey @lzepp81,

Thanks for providing this information 🙂 After further investigation, this is a known issue and we are waiting for a software update that will provide a fix for this. The software update will go out soon with the 2006 release. The 2006 release is rolling out next week. Please let us know if there's anything else I can do to help or if you have additional questions.