Skip to main content

Configuring Mastercard MATCH

Mastercard MATCH is a data provider you can use to run the Merchant fraud check.

How it works

This is the default behavior for a variant of the Merchant fraud check with Mastercard Alert to Control High-Risk Merchants system (MATCH).

The check is performed by screening a company's name and address, along with the names and addresses of one to five associates, who are individuals, on the company's verification list(s), against the MATCH database. This provides a list of matches to fraudulent merchant accounts that may belong to the company or associates.

Only associates with addresses will be used to run the check. If no associates have addresses, the check errors. If the company has more than five associates, who are individuals, on its verification list(s), the associates whose profiles were added first are used for the check. For example, if one associate is added to the Identify authorized persons list, then 10 associates are added to the Identify shareholders list, the authorized person and the 4 shareholders first added to the list will be used for the check.

If no potential matches are found for the company and associates, and there are no outstanding potential matches from earlier screening checks, the check is marked Completed.

If any potential matches are found, the check returns Unresolved events and the matches are displayed in the Potential matches list.

In either case, the Previous inquiries list displays any matches which others have inquired about in the MATCH database over the past 360 days. Note that these matches have not been reported or had their accounts terminated.

Click the name of any match, whether it's a potential, ignored, or a previous inquiry, to see a detailed portfolio that provides all available information from the data provider about the company data, associate data, and the reason the merchant is on the list. the reason the match's account was terminated and the contact details of the merchant that filed the report are also displayed.

This check is supported for all countries.

Ongoing monitoring

This check has ongoing monitoring enabled by default.

After the check is run, once a day, Passfort checks with MATCH for new results. If there are any new matches, they're displayed in the Potential matches list and the check becomes incomplete and the application (if it's approved) is put into review.

MATCH supports monitoring for up to 360 days. If you would like to ensure the check is re-run after that point, configure the task to expire after 360 days.

Configuration options

You can use the following configuration options:

  • Countries to search: When this option is selected, only results from the countries you specify will be returned.

  • Regions to search: When this option is selected, only results from the regions you specify will be returned. You can choose from the following regions: United States; Canada; Caribbean/Central America/Mexico/South America; Asia/Pacific; Europe; Middle East/Africa.

  • Minimum phonetic matches: When this option is selected, only results with the specified number of sound-alike matches you specify will be returned. For example, "easy" is a sound-alike match for "EZ". Choose between one to nine phonetic matches. When this option is deselected, the number of phonetic matches defaults to three.

The Search worldwide configuration option is deprecated. To learn more about how MATCH determines phonetic matches, see the MATCH User Manual or contact your Mastercard account manager.

What we'll need

Let us know that you'd like to add a variant of the Merchant fraud check with MATCH and which configuration options you'd like to use. We'll set it up for you.

To complete the configuration, we'll also need your MATCH:

  • Client certificate

  • Client consumer key

  • Client acquirer ID

For help getting this information, speak with your Mastercard account manager.

Testing the configuration

Once the check variant is configured, follow these steps in your demo environment to test whether it's working as expected.

  1. Does the check complete when no matches are returned from MATCH?

    To run the test, create any company profile, add at least one associate to a verification list, then run the check variant. If the check is marked Completed and the only new matches are returned in the Previous inquiries list, it's working as expected.

  2. Does the check display potential matches returned from MATCH?

    To run the test, create a company profile with FRAUD as part of the profile's name, add at least one associate to a verification list, then run the check variant. If the check status is Unresolved events and there are matches displayed in the Potential matches list, it's working as expected.

The test word is not case-sensitive.

Required profile fields

These are the required profile details of the company which are searched in MATCH:

Name

Description

Company name

(metadata.name)

The company's name.

Addresses

(metadata.addresses)

The company's address history.

These are the profile details of the individual which are searched in MATCH:

Name

Description

First name(s)

(personal_details.name.given_names)

The individual’s first and, if applicable, middle names.

Surname

(personal_details.name.family_name)

The individual’s last name.

Addresses

(address_history)

The individual’s address history.