ATMs Inquiry Status Codes

Highlighted
Regular Visitor

ATMs Inquiry Status Codes

Hi all,

me and my team are integrating the VISA atm locator in our backend systems. We're testing the service in sandbox with the following configurations:

- Endpoint: 

https://sandbox.api.visa.com/globalatmlocator/v1/localatms/atmsinquiry

 - Body as described in https://developer.visa.com/capabilities/atmlocator/reference#atmlocator__atmlocator

 

After various tests we noticed that the response's body usually assumes two common formats:

1 - Success, ATMs found with the specified parameters 

       "wsStatus": {

            "statusCode": "CDI000",

            "statusDesc": "Visa ATM Locator Svc-Success"

        }

        In this case we have two others scenarios:

              1.1 - The placename or the geocodes specified are invalid, so matchedLocations field in the response is empty                                          and founATMLocations is null

                     "matchedLocations": [ ],

                     "foundATMLocations": null

               1.2 - All the request's data are valid and locations are returned 

 

2 - Failure,  Visa ATM Locator Svc-Solr Execution Failure

          2.1 The specified placename is not included in the sandox's test data but location is matched, so matchedLocations is                            qualified but foundATMLocations is null because no data are available. The response in this case is:

            

  • "matchedLocations": [
    • {
      • "location": {
        • "placeName": "Via Castellanza 11, 20151, Milano, MI",
        • "coordinates": {
          • "latitude": 45.500834472387304,
          • "longitude": 9.109841521236055
          },
        • "score": 97.72,
        • "geocodeMethod": null,
        • "address": {
          • "city": "Milano",
          • "formattedAddress": "Via Castellanza 11, 20151, Milano, MI",
          • "street": "Via Castellanza 11",
          • "street2": "",
          • "postalCode": "20151",
          • "state": "Lombardia",
          • "country": "ITA"
          },
        • "typeName": "PointAddress",
        • "properties": null
        }
      }
    ],
  • "foundATMLocations": null,
  • ......
  • "wsStatus": {

    • --> "statusCode": "CDI082", <--
    • "statusDesc": "Visa ATM Locator Svc-Solr Execution Failure"

    }

             2.2 The specified placename exists in the sandox's test data but no atms are found for example because the distance field                       is set to 0 in the request. The status in this case is:

   "wsStatus": {

  •     --> "statusCode": "CDIS203", <--
  •     "statusDesc": "Visa ATM Locator Svc-Failure (Empty Response Received from GMR)"

    }     

 

The point is:

      - How can we interpret the various status codes to perform a consistent mapping between VISA status code              and our internal context manager? 

       - Are these codes different between production and testing environment?

       - Is there a more detailed documentation about this codes in the production environment?

 

We didn't find any reference in the developer center about this situations. Our worries are relative to the production environments in which the error mapping is essential to interpret the result.  

 

Thank you in advance!

 

 

 

 

1 REPLY 1
Highlighted
Visa Dev Moderator

Re: ATMs Inquiry Status Codes

Hey @grm27,

 

Those are some good questions, please see my inline answers to your questions below. 

 

- How can we interpret the various status codes to perform a consistent mapping between VISA status code and our internal context manager?

[Diana] We have very limited data to test in the sandbox for ATM Loc. Null response is not an error, this is expected due to lack of data. We find that there is data limitation in sandbox and that is why you are receiving the response "Visa ATM Locator Svc-Failure (Empty Response Received from GMR)". We have updated data in sandbox. However, it might not completely eliminate the possibility of having the same issue occur. Hence, we recommend that you try once more and let us know your findings.

 

Also, per the design, it is possible that foundATMLocations is null, in the case, there is no ATM data for the given input address/location.

 

- Are these codes different between production and testing environment?
[Diana] Yes, you can assume that the test data in sandbox is for testing purposes only, and it doesn’t reflect what the real data represents in the production environment.


- Is there a more detailed documentation about these codes in the production environment?

[Diana] We recommend you provide us with a signed contract and we will issue production access to completely resolve this issue.

 

 



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

Thanks,
Diana