ATM Locator Returns Error "Visa ATM Locator Svc-Solr Execution Failure"
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ATM Locator Returns Error "Visa ATM Locator Svc-Solr Execution Failure"
Hi,
I'm currently building an app using Xcode, and I'm trying to use the ATM Locator API (ATMs Inquiry, v1; Find Nearby ATMs, v3 ), but it doesn't seem to work. I've been trying to test it Postman, and it keeps on returning the following errors for v1 and v3:
v1:
"wsRequestHeaderV2": {
"requestTs": "2015-08-11T01:49:53.887Z",
"requestMessageId": "test1234567801",
"userBid": "10000108",
"correlationId": "909420141104053819418",
"applicationId": "VATMLOC",
"userId": "CDISIUserID"
},
"requestData": {
"distanceUnit": "mi",
"distance": "60",
"culture": "en-US",
"options": {
"findFilters": [
{
"filterValue": "",
"filterName": "PLACE_NAME"
},
{
"filterValue": "",
"filterName": "CARD_ACCEPT"
},
{
"filterValue": "",
"filterName": "OPER_HRS"
},
{
"filterValue": "",
"filterName": "AIRPORT_CD"
},
{
"filterValue": "",
"filterName": "WHEELCHAIR"
},
{
"filterValue": "",
"filterName": "BRAILLE_AUDIO"
},
{
"filterValue": "",
"filterName": "BALANCE_INQUIRY"
},
{
"filterValue": "",
"filterName": "CHIP_CAPABLE"
},
{
"filterValue": "",
"filterName": "PIN_CHANGE"
},
{
"filterValue": "",
"filterName": "RESTRICTED"
},
{
"filterValue": "",
"filterName": "PLUS_ALLIANCE_NO_SURCHARGE_FEE"
},
{
"filterValue": "",
"filterName": "ACCEPTS_PLUS_SHARED_DEPOSIT"
},
{
"filterValue": "",
"filterName": "V_PAY_CAPABLE"
},
{
"filterValue": "",
"filterName": "READY_LINK"
},
{
"filterValue": "",
"filterName": "ACPT_INTL_CRD_IND"
},
{
"filterValue": "",
"filterName": "NO_ATM_ACCS_FEE_IND"
},
{
"filterValue": "",
"filterName": "BONUS_OFFER"
},
{
"filterValue": "",
"filterName": "PREFERRED_ATM"
},
{
"filterValue": "",
"filterName": "VISA_EVERYWHERE_ACCESS"
}
],
"range": {
"count": 10,
"start": 0
},
"operationName": "and",
"sort": {
"primary": "distance",
"direction": "asc"
},
"useFirstAmbiguous": true
},
"location": {
"address": null,
"geocodes": {
"latitude": 38.28352,
"longitude": -75.4169
},
"placeName": ""
},
"metaDataOptions": 0
}
}
"requestData": {
"culture": "en-US",
"options": {
"sort": {
"primary": "distance",
"direction": "asc"
},
"range": {
"count": 10,
"start": 0
},
"findFilters": [
{
"filterName": "string",
"filterVaule": "string"
}
],
"operationName": "or",
"useFirstAmbiguous": true
},
"distance": 20,
"location": {
"address": {},
"geocodes": {
"latitude": "30.26759000000004",
"longitude": "-97.74298999999996"
},
"placeName": "Austin"
},
"distanceUnit": "mi",
"metaDataOptions": 0
},
"wsRequestHeaderV2": {
"userId": "CDISIUserID",
"userBid": "10000108",
"requestTs": "2021-04-14T20:28:16.000Z",
"applicationId": "VATMLOC",
"correlationId": "909420141104053819420",
"requestMessageId": "rohuang-001"
}
}
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ATM Locator Returns Error "Visa ATM Locator Svc-Solr Execution Failure"
Hi @alesyabondareva,Thank you for reaching out. One of our agents will look into this and get back to you soon. In the meantime, if any community member knows a solution, feel free to reply to this thread.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ATM Locator Returns Error "Visa ATM Locator Svc-Solr Execution Failure"
These are the errors I keep on getting for "ATMs Inquiry" (for the record "Find Geocodes" works well):
v3:
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ATM Locator Returns Error "Visa ATM Locator Svc-Solr Execution Failure"
Hi @alesyabondareva,
We have very limited data to test in the sandbox for ATM Locator. Null response is not an error because this is expected due to lack of data. We find that there's data limitation in sandbox and that is why you're 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. Once you're in the Production environment you won't get this error.