Returns information on merchants that have been terminated in Mastercard MATCH
A documented Mastercard MATCH operation that changes something in your account. Describe the outcome you want in plain words — HumDay writes the program, proves it, and runs it.
What this operation does
Returns information on merchants that have been terminated and merchants that have inquired upon.
- POSTChanges data · TerminationInquiryRequest
api.mastercard.com/fraud/merchant/v3/termination-inquiry
How HumDay uses it
- You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
- The contract names it. Before anything is built, you see exactly which Mastercard MATCH operations the program may use, and this is one of them.
- You approve access. Because this one changes data, it cannot run until you have explicitly granted it.
Other Mastercard MATCH operations
- Used by Acquirers to add a terminated a merchant in the MATCH systemPOST · changes data
- Returns the summary of Retro matches for the given Acquirer IdPOST · changes data
- Returns the contact information for the acquirer id requestedPOST · changes data
- Returns detailed information about MerchantsPOST · changes data
- Returns information about MerchantsGET · reads data
Questions
- Can HumDay returns information on merchants that have been terminated in Mastercard MATCH?
- Yes. This operation is published in Mastercard MATCH's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
- Will this change my Mastercard MATCH data?
- Yes — this is a POST operation, so it changes something in Mastercard MATCH. HumDay holds anything that writes behind an approval you grant explicitly, and the contract you approve says what it may touch.
- Do I need to write code?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your Mastercard MATCH account.
Where this came from
Read from a published API description for Mastercard MATCH at developer.mastercard.com/devzone/api/portal/swagger/match. The description above is the provider’s own wording, not ours. Last published 2020-08-24.