Mastercard

MATCH API

Helps acquirers identify potentially high-risk merchants before entering to a merchant agreement.

Other#openapi

Fork copies the collection into your workspace, without the publisher's secrets, so you can add your own key and send requests. Star saves it to your starred APIs (Account › Marketplace) and helps others find it.

Overview

Helps acquirers identify potentially high-risk merchants before entering to a merchant agreement.

Endpoints 6

Add Terminated Merchant

  • POSTUsed by Acquirers to add a terminated a merchant in the MATCH system. Merchant information, and up to five principal owners per merchant, can be provided by an acquiring bank as part of the listing./fraud/merchant/v3/add-merchantUsed by Acquirers to add a terminated a merchant in the MATCH system. Merchant information, and up to five principal owners per merchant, can be provided by…

Acquirer Contact Request

  • POSTReturns the contact information for the acquirer id requested. When MATCH returns a possible merchant match, this resource assists users by retrieving the contact information associated with the Acquirer ID/ICA that added the merchant to MATCH./fraud/merchant/v3/common/contact-detailsReturns the contact information for the acquirer id requested. When MATCH returns a possible merchant match, this resource assists users by retrieving the…

Retroactive Inquiry Details Request

  • 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. This MATCH resource assists acquirer's ability to consider the merchants terminated after the inquiry was made. If an initial inquiry does not result in a possible match, it is still possible that the merchant listing could appear sometime in the next 360 days. This may occur when another acquirer enters the merchant into the MATCH database. The system will automatically continue to search the MATCH system for 360 days. To view these notifications, acquirers must use the Retroactive Inquiry Summary service. This resource can be used to obtain detailed information, such as, if a Merchant or individual has been terminated by another acquirer after an inquiry was made, the reason for termination, and the history of fraudulent or risky business practices that led to that termination./fraud/merchant/v3/retro/retro-inquiry-details?AcquirerId=stringReturns detailed information about Merchants, URLs and up to five principal owners, that have been terminated by an acquiring bank after the inquiry was made.…

Retroactive Inquiry Request

  • POSTReturns the summary of Retro matches for the given Acquirer Id. This resource will return the summary of Retroactive Inquiry matches for the given Acquirer ID/ICA. If an initial inquiry does not result in a possible match, it is still possible that the merchant listing could appear sometime in the next 360 days. This may occur when another acquirer enters the merchant into the MATCH database. The system will automatically continue to search the MATCH system for 360 days. To view these notifications, acquirers must use the Retroactive Inquiry service./fraud/merchant/v3/retro/retro-listReturns the summary of Retro matches for the given Acquirer Id. This resource will return the summary of Retroactive Inquiry matches for the given Acquirer…

TerminationInquiryRequest

  • POSTReturns information on merchants that have been terminated and merchants that have inquired upon. Provides the acquiring bank with information, such as, if a Merchant or individual has been terminated by another acquirer already, the reason for termination, the history of fraudulent or risky business practices that led to that termination and the inquiry that was made already on the Merchant or individual by own or another acquiring bank (if opted)./fraud/merchant/v3/termination-inquiry?PageOffset=0&PageLength=10Returns information on merchants that have been terminated and merchants which have been inquired upon. MATCH can provide the acquiring bank with information,…

Termination Inquiry History Request

  • GETReturns information about Merchants, URLs and up to five principal owners, that have been terminated by an acquiring bank from a previous inquiry. The Inquiry History Results resource displays the inquiry with the option to view either; Possible Merchant Matches or Possible Inquiry Matches./fraud/merchant/v3/termination-inquiry/:IRN?PageOffset=0&PageLength=10&AcquirerId=1996Returns information about Merchants, URLs and up to five principal owners, that have been terminated by an acquiring bank from a previous inquiry. The Inquiry…

API details

Base URL
https://api.mastercard.com
Authentication
None declared in the description
Operations
6 operations on 6 pathsPOST 5GET 1
Main resources
Acquirer Contact Request 1Add Terminated Merchant 1Retroactive Inquiry Details Request 1Retroactive Inquiry Request 1Termination Inquiry History Request 1TerminationInquiryRequest 1
Response formats
application/json
Description format
Swagger 2.0, API version 1.0.0
Listed from
APIs.guru OpenAPI Directory (CC0-1.0)
Source updated

How to test the MATCH API in Swastik Codes

  1. Open the APISelect “Fork & run in Swastik Codes” on this page. Sign in or create a free account if asked.
  2. Fork it into your workspaceChoose a workspace. You get your own copy of the MATCH API collection, without the publisher's secrets.
  3. Add your credentialsOpen the collection's variables or an environment and enter your API key or token, if the API needs one.
  4. Send a requestPick an endpoint, for example “Used by Acquirers to add a terminated a merchant in the MATCH system. Merchant information, and up to five principal owners per merchant, can be provided by an acquiring bank as part of the listing.” (POST /fraud/merchant/v3/add-merchant), and press Send. Check the response, add tests and run the whole collection with the runner.

Frequently asked questions

What is the MATCH API?

Helps acquirers identify potentially high-risk merchants before entering to a merchant agreement. It is listed under Other and has 6 endpoints.

Who publishes the MATCH API?

It is listed from Mastercard's public API description (an OpenAPI document), not published by Mastercard on Swastik Codes. Anyone who controls mastercard.com can claim the profile by adding a DNS TXT record.

What is the base URL of the MATCH API?

Requests go to https://api.mastercard.com. Endpoint paths are added to this base URL.

How do I authenticate with the MATCH API?

Its OpenAPI description does not declare an authentication scheme. Some endpoints may be open; check the provider's documentation before relying on that.

How many endpoints does the MATCH API have?

6 operations on 6 paths (5 POST, 1 GET). The largest groups are Acquirer Contact Request, Add Terminated Merchant, Retroactive Inquiry Details Request, Retroactive Inquiry Request.

Is forking the MATCH API free?

Yes. Forking copies the collection into your workspace for free. It has been starred 0 times and forked 0 times.

Suggest an API

Tell us which public API is missing. We check it, then add it here with its endpoints when it has an OpenAPI (Swagger) description.