# Support source: https://developer.mastercard.com/locations/documentation/support/index.md ## FAQ {#faq} #### General {#general} The ATM Locations API provides programmatic access to Mastercard's global ATM location dataset, covering over 2 million Mastercard-accepting ATM terminals. It allows developers to search by geographic coordinates, address, country to retrieve merchant attributes such as accessibility features, supported languages, cash withdrawal limits, sponsor bank details, and 24-hour availability. Explore [Overview page](https://developer.mastercard.com/locations/documentation/index.md) to understand core capabilities Global, all countries where Mastercard-accepting ATMs are reported. Country and country-subdivision lookup endpoints are available to discover supported regions. Refer [API reference page](https://developer.mastercard.com/locations/documentation/api-reference/index.md) to know more about the API specific information The API supports below mentioned scenarios across ATM discovery, lookup, and feedback- * [ATM Search By GeoCode](https://developer.mastercard.com/locations/documentation/use-cases/atm-network-optimization/index.md) * [ATM Search By Address](https://developer.mastercard.com/locations/documentation/use-cases/intelligent-atm-discovery/index.md) * [Country Search](https://developer.mastercard.com/locations/documentation/use-cases/country-code/index.md) * [Country Subdivision Search](https://developer.mastercard.com/locations/documentation/use-cases/country-subdivision-code/index.md) * [Customer Feedbacks](https://developer.mastercard.com/locations/documentation/use-cases/customer-feedback/index.md) The API is designed for four primary audiences: * Card Issuers- embed ATM finders in mobile/web banking apps * Digital Banking Apps- power location-based banking features * ATM Locator Applications- build standalone ATM discovery tools * Developers integrating map services- enrich map apps with authoritative Mastercard ATM data Unlike consumer POI APIs, Mastercard's ATM Locations API is powered by authoritative data submitted directly by sponsor banks and acquirers into Mastercard's global ATM database. This provides unique attributes that competitors cannot offer: * Sponsor/owner bank details and Mastercard-assigned IDs * Real-time accessibility features (wheelchair access, audio support) * Payment feature flags (contactless, cardless withdrawal) Each ATM record includes location details (address, geo-coordinates), sponsor information (bank name, ICA), operational attributes (24-hour availability, max withdrawal limit, primary currency), accessibility features (handicap accessible, audio support), payment features (EMV, contactless, cardless withdrawal), and fee information (access fees, surcharge-free alliance membership). Refer to [Data Elements](https://developer.mastercard.com/locations/documentation/tutorials-and-guides/data-elements/index.md) to know more about API response fields Yes, Mastercard Issuers and ATM Acquirers that report their ATMs into Mastercard's Location Administration Tool (LAT) are entitled to up to 100k requests at no cost. Please specify this when you sign up for the service to ensure you get the promotion. #### Onboarding {#onboarding} Access to the ATM Locations API begins with a Mastercard Developers account using enterprise mail id. Once registered, you can create a project, select the Locations API, and immediately receive sandbox credentials for evaluation. Follow steps below, or check [Quick Start Guide](https://developer.mastercard.com/locations/documentation/quick-start-guide/index.md) for detailed step by step guide- 1. Go to developer.mastercard.com/account/sign-up 2. Register with your work email and verify your account 3. Create a new project in your dashboard 4. Add the "Locations API" to your project 5. Download your .p12 keystore file and note your Consumer Key 6. Set up OAuth 1.0a signing using the Mastercard OAuth SDK Sandbox and Production URL details are available on [API Basics Page](https://developer.mastercard.com/locations/documentation/api-basics/index.md). * Sandbox ```Sandbox https://sandbox.api.mastercard.com/locations/atms ``` * Production ```Production https://api.mastercard.com//locations/atms ``` The fastest path to a successful first call is to use the POST/searches endpoint with a sample descriptor. This takes under 5 minutes end-to-end using an OAuth SDK. Prerequisites checklist: * Mastercard Developers account * Project created and MID API added * Sandbox credentials (Consumer Key, .p12 keystore, key alias, keystore password) * OAuth1 SDK installed for your language
Follow detailed steps on [Quick Start Guide](https://developer.mastercard.com/locations/documentation/quick-start-guide/index.md) ATM Locations API uses OAuth 1.0a signed with RSA (SHA-256) for authentication. Each request must include a signed authorization header generated using your private key from the developer portal. Learn more → [Authentication Guide](https://developer.mastercard.com/platform/documentation/authentication/using-oauth-1a-to-access-mastercard-apis/) Sandbox access is included with every Mastercard Developers account. There is no separate free-trial application required, sandbox credentials are issued immediately when you create a project and add the ATM Locations API. Check [Quick Start Guide](https://developer.mastercard.com/locations/documentation/quick-start-guide/index.md) to know more about sandbox account access To cancel a monthly subscription, go to My Projects, select the project and select Delete project. Once your project which is using Locations API has been deleted, recurring charges for this service will end. #### Data and Coverage {#data-and-coverage} Use the POST `/customer-feedbacks` endpoint. Retrieve valid problem codes first from GET `/feedback-problems`. This creates a data-quality loop back to the Places / ATM product team. If you are interested in a region which is not listed, please contact us at `lat_admin@mastercard.com`. We are constantly expanding into new countries and will be happy to work with you to determine when your country will be available. ATM Location data is reported by acquirers, processors and sponsors via the Location Administration Tool (LAT). For governance details, please consult section 5.1.4.1 of the Mastercard Rules Geocoding is the process of assigning latitude and longitude coordinates for a given location. * **Rooftop geocoding** - Location is specified down to the rooftop of a particular address. Currently offered in the United States only. * **Street Segment geocoding** - Address is matched to a street and specific segment (such as a city block). Currently offered in 135 countries as listed in regional availability. * **City Center level geocoding** - Countries not listed in the regional availability section are geocoded to the center of the city. It is not recommended to display these locations on a map. Yes, the Data Leasing option is available. Data Leasing provides access to the full data set (regional or global), allowing customers to store the dataset locally with greater flexibility on analytics needs. Price is based on geography, field bundles, vintage and delivery frequency #### Integration and Troubleshooting {#integration-and-troubleshooting} The API returns structured error codes indicating exactly what went wrong and where. Refer [Codes and Formats](https://developer.mastercard.com/locations/documentation/code-and-formats/index.md) for Resolution Tips table linking each error to endpoints and step-by-step fixes. To test the Locations API in a sandbox environment you create a project, generate sandbox keys and use our test data. Refer to our [Getting Started](https://developer.mastercard.com/locations/documentation/quick-start-guide/index.md) guide for details. We return up to twenty-five records per request. Due to the large volume of records that could potentially be returned for a location, we currently limit record returns to twenty-five per call. Additional calls may be made to retrieve subsequent records using the Offset parameter. See the documentation for details [here](https://developer.mastercard.com/locations/documentation/api-reference/index.md) You can find detailed information on the Locations API [here](https://developer.mastercard.com/locations/documentation/api-reference/index.md) For general or pricing questions about the Locations API, send an e-mail to `lat_admin@mastercard.com`. For development related or technical questions, please visit our [support page](https://developer.mastercard.com/support) and submit your inquiry. ## How to get help {#how-to-get-help} Use the [**Get Help**](https://developer.mastercard.com/locations/documentation/support/index.md#get-help) button at the bottom of this page to raise a support case for anything technical --- integration issues, unexpected responses, or documentation feedback (add `ATM Locations docs feedback` to the subject line). The self-service options below resolve most issues immediately. | Need | Where to go | Response target | |-----------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------|-----------------| | Technical, integration or documentation issue | [**Get Help**](https://developer.mastercard.com/locations/documentation/support/index.md#get-help) button below | 1 business day | | Commercial, licensing or pricing | Your Account Manager or [Contact Sales](https://developer.mastercard.com/contact-us) | 2 business days | | Authentication or gateway errors | [Gateway Error Codes](https://developer.mastercard.com/platform/documentation/security-and-authentication/gateway-error-codes) | Self-service | | API-specific error codes | [Codes and Formats](https://developer.mastercard.com/locations/documentation/code-and-formats/index.md) | Self-service | | Service availability or outage | [API Status Page](https://developer.mastercard.com/api-status?environment=production&service=Locations%20Intelligence%20-%20Places) | Live | ## Before you contact support {#before-you-contact-support} To help us resolve your issue on the first response, include the following details in your request: | Detail | Example | |----------------------------------------|---------------------------| | Endpoint and HTTP method | `POST /atm/searches` | | HTTP status and error code | `400 INVALID_INPUT_VALUE` | | Environment | Sandbox or Production | | Timestamp of the failing call (UTC) | `2026-08-11T14:32:05Z` | | Consumer key (first 8 characters only) | `9aF2kL7q...` | Warning: Never share your `.p12` keystore, keystore password, or full `Authorization` header in a support case or email. See [API Basics](https://developer.mastercard.com/locations/documentation/api-basics/index.md) for key-management guidance. ## Get Help {#get-help} ### Contact us for technical support. {#contact-us-for-technical-support}