Re: VCES - Validate Endpoint with Documentation not in sync

kenmok
Regular Visitor

VCES - Validate Endpoint with Documentation not in sync

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-iFrame-API_/paths/~...

 

In the documentation a number of other fields are shown I cannot see in the service's response, for example aliasId, redemptionDetails, bin, lastFourDigits, etc. Is it possible to make all those fields shown in the documentation available in the response? How can I achieve that?

4 REPLIES 4
jenn_kh
Community Moderator

Re: VCES - Validate Endpoint with Documentation not in sync

Hi @kenmok, Thank you for reaching out. An agent will look into this and get back to you as soon as possible.

kenmok
Regular Visitor

Re: VCES - Validate Endpoint with Documentation not in sync

hi @jenn_kh , great! Thanks!

kenmok
Regular Visitor

Re: VCES - Validate Endpoint with Documentation not in sync

Hi @jenn_kh , I have received any feedback from agent, anyway I can contact with them? thanks.

API_Products
Visa Developer Support Specialist

Re: VCES - Validate Endpoint with Documentation not in sync

Hey @kenmok,

 

If you find inconsistencies between the documentation and the actual response from the Visa Card Eligibility Service (VCES) sandbox endpoint, there are a few steps you can take to address this issue:

 

Steps to Address Documentation and Endpoint Inconsistencies

1. Verify Documentation Version: Ensure that you are referring to the latest version of the API documentation. Sometimes, older versions might be cached or mistakenly referred to.

2. Check API Request Parameters: Ensure that your API request includes all necessary parameters and headers as specified in the documentation. Sometimes missing parameters may result in incomplete responses.

 

 




Thanks,

Diana H.



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