HumDay

Returns information about Merchants in Mastercard MATCH

A documented Mastercard MATCH operation that only reads, so it can watch for changes without altering anything. Describe what you want to happen and HumDay builds it.

Automate this

What this operation does

Returns information about Merchants, URLs and up to five principal owners, that have been terminated by an acquiring bank from a previous inquiry.

  • GETReads data · Termination Inquiry History Requestapi.mastercard.com/fraud/merchant/v3/termination-inquiry/{IRN}

How HumDay uses it

  1. You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
  2. 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.
  3. You approve access. Read-only access is still yours to grant, and still limited to what the contract needs.

Other Mastercard MATCH operations

All 6 Mastercard MATCH operations

Questions

Can HumDay returns information about merchants 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.
Does this change anything in my Mastercard MATCH account?
No. This is a read-only operation, so it can be used to watch for changes or fetch data without altering anything in Mastercard MATCH.
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.