Re: VCES - Validate Endpoint with Documentation not in sync

Solved! Go to solution
tibalogh
Helper

VCES - Validate Endpoint with Documentation not in sync

Dear Team,

 

I might have found some inconsistencies between the documentation (see the link below), and the functionality of sandbox service endpoint.

Link to the documentation: https://developer.visa.com/capabilities/vces/reference#tag/Visa-Card-Eligibility-Service/operation/V...

Sandbox service endpoint: https://sandbox.api.visa.com/visacardeligibilityservices/v1/cardeligibility/validate

 

  • requestTimeStamp format: regarding to the documentation, the timestamp should be in this format: "mm/dd/yyyy hh:mm:ss a", but it responds "Vendor RequestTimeStamp format error" status description, statusCode: "103".

    request example: 

 

{
    "permanentAccountNumber": "4000000000000013",
    "vendorUniqueId": "14096_TstVDPPgm1",
    "numberOfAdditionalRedemptions": 2,
    "requestTimeStamp": "5/4/2022 5:04:50 PM",
    "correlationId": "7a9d1ed7-78cf-4de5-bafd-0dc59fce742d",
    "extendedData": "asddd"
}​

Response: 

{
    "statusCode": "103",
    "statusDescription": "Vendor RequestTimeStamp format error",
    "CorrelationId": "1651e4cb-440b-456b-9e3f-01b3c1e34fd7",
    "responseTimeStamp": "5/4/2022 3:08:01 PM",
    "eligibilityLevel": "0",
    "cardId": "0"
}​

 

X-CORRELATION-ID:1651676691_006_553997613_-74979967j5_VDP_WS


Using ISO format in the responseTimeStamp, the response was successful:
Request: 

{
    "permanentAccountNumber": "4000000000000013",
    "vendorUniqueId": "14096_TstVDPPgm1",
    "numberOfAdditionalRedemptions": 2,
    "requestTimeStamp": "2022-05-04T15:14:13.630Z",
    "correlationId": "9badec7e-afa0-47dd-940e-28dd2ca161d9",
    "extendedData": "asddd"
}​

 

Response: 

 

{
    "statusCode": "000",
    "statusDescription": "Success",
    "CorrelationId": "9badec7e-afa0-47dd-940e-28dd2ca161d9",
    "responseTimeStamp": "5/4/2022 3:14:14 PM",
    "eligibilityLevel": "0",
    "isEligible": "True",
    "cardId": "311"
}​

 

Which format should I use in production? Can you please clarify this?

 

  • In the documentation a number of other fields are shown I cannot see in the service's response, for example cardBenefits, productSubType, redemptionDetails, etc. 
    Is it possible to make all those fields shown in the documentation available in the response?
    How can I achieve that?
  • According to the documentation, the response message field name "CorrelationId" should start with lowercase letter: "correlationId".
  • Can you please provide test data, where eligibility level is "1" or "2" as well?

Thank you in advance,

Tibor  

 

 
7 REPLIES 7
jenn_kh
Community Moderator

Re: VCES - Validate Endpoint with Documentation not in sync

We appreciate you bringing this to our attention, @tibalogh. We have let our team know and an agent will follow up with any information as soon as possible. -Jenn

API_Managers
Visa Developer Support Specialist

Re: VCES - Validate Endpoint with Documentation not in sync

Hi @tibalogh,

 

I've logged incident INC13514536 for our engineering team to investigate the issue. I'll provide an update once I hear back from them. 




Thanks,

Diana



Was your question answered? Don't forget to click on "Accept as Solution" to help other devs find the answer to the same question.

tibalogh
Helper

Re: VCES - Validate Endpoint with Documentation not in sync

Thank you Diana

I've made further tests, and found, that the first bulletpoint with the requestTimeStamp format is not a problem anymore. When I first tried the given format, I used my local time, which was in GMT+2 timezone. Now I have tried using UTC time, and the format was accepted by the service. Maybe it would be worth mentioning it in the documentation, that the request timestamp should be in UTC.

API_Managers
Visa Developer Support Specialist

Re: VCES - Validate Endpoint with Documentation not in sync

Hi @tibalogh,

 

Thanks for letting me know the issue is fixed. I've communicated your request to have our documentation updated to our engineering team. 




Thanks,

Diana



Was your question answered? Don't forget to click on "Accept as Solution" to help other devs find the answer to the same question.

tibalogh
Helper

Re: VCES - Validate Endpoint with Documentation not in sync

Hi @API_Managers , thank you for your message.

I only wanted to let you know that the first question is no more an issue, but there were others in my original question. Should I ask them in a different thread? They were: 

  • In the documentation a number of other fields are shown I cannot see in the service's response, for example cardBenefits, productSubType, redemptionDetails, etc. 
    Is it possible to make all those fields shown in the documentation available in the response?
    How can I achieve that?
  • According to the documentation example response, the response message field name "CorrelationId" should start with lowercase letter: "correlationId".
  • Can you please provide test data, where eligibility level is "1" or "2" as well?

 

API_Managers
Visa Developer Support Specialist

Re: VCES - Validate Endpoint with Documentation not in sync

Hi @tibalogh,

 

The VCES product team is most likely going to postpone any API documentation update until the future. Regarding documentation on cardBenefits, productSubType, redemptionDetails, etc., that will not be provided in the near future unless you (the client) establishes a formal business relationship with Visa. 




Thanks,

Diana



Was your question answered? Don't forget to click on "Accept as Solution" to help other devs find the answer to the same question.

API_Managers
Visa Developer Support Specialist

Re: VCES - Validate Endpoint with Documentation not in sync

Hi @tibalogh,

 

Our engineering team has received information from the VCES team that the Sandbox is very limited in terms of testing scope. If you wish to pursue additional information about VCES, you should contact your regional product office. We have opened up a ticket to have the documentation corrected for some of the VCES case issues.




Thanks,

Diana



Was your question answered? Don't forget to click on "Accept as Solution" to help other devs find the answer to the same question.