Automate Mastercard MATCH
HumDay reads Mastercard MATCH’s own published API description and derives 6 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 MATCH is
Helps acquirers identify potentially high-risk merchants before entering to a merchant agreement.
API host: api.mastercard.com
What HumDay can do in Mastercard MATCH
5 documented operations change something in Mastercard MATCH.
- POSTUsed by Acquirers to add a terminated a merchant in the MATCH system.
/fraud/merchant/v3/add-merchant - POSTReturns the summary of Retro matches for the given Acquirer Id.
/fraud/merchant/v3/retro/retro-list - POSTReturns the contact information for the acquirer id requested.
/fraud/merchant/v3/common/contact-details - POSTReturns information on merchants that have been terminated and merchants that have inquired upon.
/fraud/merchant/v3/termination-inquiry - POSTReturns detailed information about Merchants, URLs and up to five principal owners, that have been terminated by an acquiring bank after the inquiry was made.
/fraud/merchant/v3/retro/retro-inquiry-details
What HumDay can read from Mastercard MATCH
These are the operations a schedule or a trigger can watch.
- GETReturns information about Merchants, URLs and up to five principal owners, that have been terminated by an acquiring bank from a previous inquiry.
/fraud/merchant/v3/termination-inquiry/{IRN}
How automating Mastercard MATCH 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 MATCH account.
- Grant access, then go live. You approve the specific Mastercard MATCH operations it may use — and only those.
Automate Mastercard MATCH with these
- MasterCard ABU1 operations
- Mastercard Bill Payment Validator1 operations
- MasterCard Bin Table Listing1 operations
- Mastercard for the Settlement Currency Rate converter3 operations
- Mastercard Locations7 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 MATCH automation
- Can HumDay connect to Mastercard MATCH?
- Yes. HumDay reads Mastercard MATCH's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 6 operations are documented.
- Do I need to write code to automate Mastercard MATCH?
- 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 MATCH account.
- What can HumDay do in Mastercard MATCH?
- 5 of the 6 documented operations change something in Mastercard MATCH, and 1 read from it. HumDay only ever uses the specific operations your approved contract needs.
- Is my Mastercard MATCH 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 MATCH is held behind that approval.
Where this came from
The operations above are read from a published API description for Mastercard MATCH at developer.mastercard.com/devzone/api/portal/swagger/match. Descriptions are the provider’s own words, not ours. Last published 2020-08-24.