# MATCH Pro
source: https://developer.mastercard.com/match/documentation/index.md

Alert: MATCH Pro Migration Required: Per GLB 12773.1, all customers must migrate to MATCH Pro API and bulk files by March 31, 2026. Customers who do not migrate will be classified as Category C Noncompliant, triggering standard compliance program assessments.

## Overview {#overview}

The Mastercard Alert To Control High-risk Merchants (MATCH™) Pro system provides an Authorized User (as defined in this section) the opportunity to develop, assess, and review enhanced or incremental risk information prior to entering into a Merchant Agreement or Sponsored Merchant Agreement with a prospective MATCH Merchant.

MATCH Pro is a mandatory system for Mastercard Acquirers. The MATCH Pro database includes Authorized User-reported information about certain MATCH Merchants (and their owners) that an Authorized User has terminated.

When an Authorized User considers onboarding a Merchant, MATCH Pro can assist the
Authorized User to make an independent risk determination prior to onboarding the Merchant and commencing submission of Transactions conducted by the Merchant to the Interchange System.

The MATCH Pro APIs provides Authorized Users with the ability to develop an automated system-to-system method to access MATCH Pro and to receive a real-time response.

To learn more about MATCH Pro, please refer to the MATCH Pro User Manual and the Mastercard Security Rules and Procedures in Technical Resource Center.

## Mastercard offers another useful application to analyse Merchant Risk, called Onboarding Risk Check. {#mastercard-offers-another-useful-application-to-analyse-merchant-risk-called-onboarding-risk-check}

Cyber vulnerabilities can expose your merchants to potential breaches and Data ransom attacks, which can lead to stolen card, fraudulent transactions, large fines and reputation based damage. Onboard Risk Check (ORC) can help you identify which merchants are most vulnerable with our Cyber Risk, Sanctions Screening and Business Identity Verification functionalities. Please see AN6202 with instructions on how to request access to ORC.

Get ORC Today: [Click here](https://www.mastercardconnect.com/jct_ssc_content/fraudcenter/cyber-secure)

Learn More about ORC: [Click here](https://www.riskrecon.com/solutions/mastercard-onboard-risk-check)

## How it works {#how-it-works}

#### Inquire for terminated merchants {#inquire-for-terminated-merchants}

###### Step 1 {#step-1}

Prior to executing the merchant agreement, the Acquirers submits an inquiry to the MATCH Pro API that includes information on a merchant and the associated principal owner(s).

###### Step 2 {#step-2}

MATCH Pro searches the database for possible matches between the merchant information provided in the inquiry and information related to merchants added to MATCH Pro by other Acquirers during the past five years.

###### Step 3 {#step-3}

MATCH Pro returns details of possible merchants found listed in MATCH Pro; the response indicates if each search result is based on an exact possible match or phonetic possible match to each of the data elements provided by the acquirer.

#### Adding a terminated merchants {#adding-a-terminated-merchants}

###### Step 1 {#step-1}

Within 5 days of the decision to terminate a merchant that meets one of the MATCH Pro reasons codes, the Acquirer submits an addition record to the MATCH Pro API that includes information on the merchant and associated principal owner(s), and the applicable reason code.

###### Step 2 {#step-2}

The record is added to MATCH Pro and made available to all other acquirers in real time.

###### Step 3 {#step-3}

MATCH Pro returns a confirmation to the acquirer that the merchant was successfully added and provides a MATCH Pro Reference Number.

#### Retro active inquiry {#retro-active-inquiry}

###### Step 1 {#step-1}

An Acquirer submits an inquiry information of a merchant to the MATCH Pro, and MATCH Pro could not find any possible matches.

###### Step 2 {#step-2}

Another Acquirer submits an addition record to the MATCH Pro that includes information on the merchant and associated principal owner(s), and the applicable reason code.

###### Step 3 {#step-3}

When the newly terminated merchant is a possible match to an Inquiry executed by an Acquirer, MATCH Pro will send out an email communication to alert the Inquirer about a possible match.

## Why use MATCH Pro API's? {#why-use-match-pro-apis}

![Why use MATCH Pro 1](https://static.developer.mastercard.com/content/match/uploads/why1.svg) The MATCH Pro API service provides customers with the ability to develop an automated system-to-system method to access MATCH Pro. ![Why use MATCH Pro 2](https://static.developer.mastercard.com/content/match/uploads/why2.svg) MATCH Pro API integration reduces time associated with MATCH Pro activity during due diligence and post termination from one day to real-time responses.

## Getting Started {#getting-started}

#### Before You Start {#before-you-start}

1.Review [API Basics.](https://developer.mastercard.com/match/documentation/api-basics/index.md)   

2.Review [use cases](https://developer.mastercard.com/match/documentation/use-cases/index.md) to establish the sequence of calls needed to evaluate the risk of onboarding a new merchant.  

3.Try the [reference app](https://developer.mastercard.com/match/documentation/reference-app/index.md) to integrate with MATCH Pro API.  

4.Follow the [onboarding guide](https://developer.mastercard.com/match/documentation/tutorial-structure/index.md#onboarding/) to begin onboarding.  

5.Refer [API reference](https://developer.mastercard.com/match/documentation/api-reference/index.md) for in-depth details about services.