Automate Mastercard Locations
HumDay reads Mastercard Locations’s own published API description and derives 7 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.
What Mastercard Locations is
The Locations API provides access to MasterCard's ATM and Merchant location database
API host: api.mastercard.com
What HumDay can read from Mastercard Locations
These are the operations a schedule or a trigger can watch.
- GETReturns countries that have Merchants offering the following services: accept contactless-enabled cards and devices, allow customers to add money to an eligible MasterCard or Maes…
/merchants/v1/country - GETReturns merchant location information for merchants offering the following services: accept contactless-enabled cards and devices, allow customers to add money to an eligible Mast…
/merchants/v1/merchant - GETReturns country subdivisions that have Merchants offering the following services: accept contactless-enabled cards and devices, allow customers to add money to an eligible MasterC…
/merchants/v1/countrysubdivision - GETReturns a list of all merchant categories for contactless and cash back merchants (example: Airline, Retail, etc.).
/merchants/v1/category - GETReturns detailed information about an ATM location.
/atms/v1/atm - GETReturns countries with valid ATM locations.
/atms/v1/country - GETReturns country subdivisions that have ATM locations.
/atms/v1/countrysubdivision
How automating Mastercard Locations works
- Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
- Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
- See it proven. The program runs and shows you the result before it is allowed near your live Mastercard Locations account.
- Grant access, then go live. You approve the specific Mastercard Locations operations it may use — and only those.
Automate Mastercard Locations with these
- MasterCard ABU1 operations
- Mastercard Bill Payment Validator1 operations
- MasterCard Bin Table Listing1 operations
- Mastercard for the Settlement Currency Rate converter3 operations
- Mastercard MATCH6 operations
- Mastercard MDES Customer15 operations
- Mastercard Merchant Identifier1 operations
- Mastercard Open Banking Payments initiation12 operations
- Mastercard Payment Account Reference Inquiry1 operations
- Mastercard Personalized Offers8 operations
- Mastercard rePower2 operations
- Mastercard Send Person to Merchant15 operations
Questions about Mastercard Locations automation
- Can HumDay connect to Mastercard Locations?
- Yes. HumDay reads Mastercard Locations's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 7 operations are documented.
- Do I need to write code to automate Mastercard Locations?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your Mastercard Locations account.
- What can HumDay do in Mastercard Locations?
- 0 of the 7 documented operations change something in Mastercard Locations, and 7 read from it. HumDay only ever uses the specific operations your approved contract needs.
- Is my Mastercard Locations account safe?
- Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to Mastercard Locations is held behind that approval.
Where this came from
The operations above are read from a published API description for Mastercard Locations at developer.mastercard.com/devzone/api/portal/swagger/locations. Descriptions are the provider’s own words, not ours. Last published 2020-08-24.