# Support source: https://developer.mastercard.com/match/documentation/support/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. ## MATCH PRO FAQ {#match-pro-faq} MATCH Pro is a mandated program for all acquirers and acquiring partners. Acquirers are required to: * Have access to MATCH Pro under live, acquiring ICAs * Add terminated merchants to MATCH Pro that meet the specified criteria * Inquire to MATCH Pro about a merchant prior to signing an agreement and/or prior to Mastercard acceptance being enabled While usage of the MATCH Pro application is mandated for all acquirers, the MATCH Pro API is considered an optional service intended to enable acquirers to develop an automated process to perform MATCH Pro inquiries and receive a real time response. For more information on other ways to access the MATCH Pro application, refer to "What are the other ways to access MATCH Pro besides the API service?" The MATCH Pro API will now adhere to the new Mastercard API Governance and Standards. New APIs to retrieve City and Country are being introduced with the launch of MATCH Pro. For more information, please see the MATCH Pro API specifications. In addition to the API, there are three methods acquirers can use to access MATCH Pro. * The first method is the submission of a single entry via MATCH Pro Online. * The second method is the electronic submission of bulk files via the batch process. * The third method is the submission of bulk files through the import function. Create a MATCH Pro API sandbox project on the Mastercard Developers Zone. There are three environments: sandbox, MTF, and production. Yes. MATCH Pro API is available in our Member Testing Facility (MTF) environment. You will first need to create a MATCH Pro API Sandbox project before onboarding into MTF. Please refer to the MATCH Pro MTF User Guide for more information. Requests should be submitted as json. Xml requests will no longer be supported, in accordance with the Mastercard API Gold Standards. Customers can submit up to 10 inquiries or merchant additions per second. The API supports up to 864,000 records per ICA in a 24-hour period. To ensure consistent data, users are now required to retrieve the city/state/country using the respective API prior to submitting a request that contains City, State, or Country fields. If a city does not return in the City API, you can use "isOtherCity": "Y" and proceed with entering the value in the "City". The MATCH Pro API will indicate which fields in your response match your query using the following codes: * M00: No Match * M01: Exact Match * M02: Phonetic Match No, the search is only global by default, and results will include all countries. Yes, the date format for all MATCH Pro APIs is YYYY-MM-DD. Yes. 1-5 Principals are supported in a single request. Mastercard provides details about the standards used for MATCH Pro on the Technical Resource Center (TRC). Refer to the MATCH Pro User Manual, available in the Mastercard Connect Technical Resource Center for more information about: * The use of MATCH Pro, including how to access and navigate the MATCH Pro system. * How to make inquiries, and add, modify, or delete MATCH Merchant information. * MATCH Pro reports. * MATCH Pro system features and standards. ## Legacy API FAQ {#legacy-api-faq} No, There is no change in authentication mechanism, you can use same client id which you were using for v3 api. Refer [API Basics](https://developer.mastercard.com/match/documentation/api-basics) for more details. Yes, You can use existing credentials to access MATCH v3 API's as well MATCH Pro API's. No, There is no need to update your p12 file if your credentials are valid and not expired. Yes, there is still an option for global, regional, or country-level searches. To perform a global search, you must enter "SearchAll: Y". To perform a regional/country level search, you must enter "SearchAll: N". Please note that results from the country that your ICA is registered under in My Company Manager will always return in the results. Use Cases for v3 API version are similar to [MATCH Pro API's Use Cases](https://developer.mastercard.com/match/documentation/use-cases). MATCH API v3 use cases can be found as below * Termination Inquiry Request * Termination Inquiry History Request * Add Terminated Merchant * Acquirer Contact Request * Retroactive Inquiry Request * Retroactive Inquiry Details Request MATCH API v3 spec file can be found here [match-v3.yaml](https://static.developer.mastercard.com/content/match/swagger/match-v3.yaml) (46KB) MATCH API v3 reference application can be found here [match-ref-app.zip](https://static.developer.mastercard.com/content/match/uploads/match-ref-app.zip) (185KB) MATCH API v3 Postman Collection can be found here Run in Postman Please drop a mail with your questions to [Contact Us](mailto:MATCHBusinessOwner@mastercard.com) ## Release history {#release-history} #### Summary of Release History {#summary-of-release-history} This section will be used to log updates to this documentation site, with dates and a description of what changed. | Date | OAS Version | Application | Description | |--------------|-------------|--------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Mar 18, 2026 | 3.0.14 | Match Pro | Remove nullable property from all the required fields. Current OAS file [match-pro.yaml](https://static.developer.mastercard.com/content/match/swagger/match-pro.yaml) (85KB) | | Feb 27, 2026 | 3.0.13 | Match Pro | Updated Legacy Decommissioning Banner. Revised isOtherCity description. Updated Pattern for the following fields - Merchant Name, Doing business as, Address Line 1 and Line 2, Principal First and Last Name. Previous OAS file [match-pro-3.0.13.yaml](https://static.developer.mastercard.com/content/match/swagger-versioning/match-pro-3.0.13.yaml) (85KB) | | Dec 23, 2025 | 3.0.12 | Match Pro | Revised nationalId description. Previous OAS file [match-pro-3.0.12.yaml](https://static.developer.mastercard.com/content/match/swagger-versioning/match-pro-3.0.12.yaml) (85KB) | | Nov 14, 2025 | 3.0.11 | Match Pro | Revised domain from api.mastercard.com to apiedge.mastercard.com across all environments. Previous OAS file [match-pro-3.0.11.yaml](https://static.developer.mastercard.com/content/match/swagger-versioning/match-pro-3.0.11.yaml) (85KB) | | Aug 18, 2025 | 3.0.10 | Match Pro | Request and response schemas have been updated to follow the latest field patterns and descriptions, and are now separated to prevent unnecessary elements from appearing in each model. In the response schema, some fields are both mandatory (required: true) and nullable. This means the field must always be present in the response payload, but its value may either contain valid data or be null. Previous OAS file [match-pro-3.0.10.yaml](https://static.developer.mastercard.com/content/match/swagger-versioning/match-pro-3.0.10.yaml) (85KB) | | Jul 30, 2025 | 3.0.9 | Match Pro | Request and response schemas have been revised to reflect the latest field patterns and descriptions. The default flag has been removed from specific fields where applicable. Previous OAS file [match-pro-3.0.9.yaml](https://static.developer.mastercard.com/content/match/swagger-versioning/match-pro-3.0.9.yaml) (74KB) | | Jul 08, 2025 | 3.0.8 | Match Pro | Mandatory fields have been marked as nullable to prevent primitive type errors during JSON conversion. For empty values, null will be displayed in the example responses of all APIs. Previous OAS file [match-pro-3.0.8.yaml](https://static.developer.mastercard.com/content/match/swagger-versioning/match-pro-3.0.8.yaml) (73KB) | | Jun 17, 2025 | 3.0.7 | Match Pro | Removed the transaction reference number from the termination inquiry response, as it was an unused and unnecessary field, and marked the email and dob fields as nullable. Previous OAS file [match-pro-3.0.7.yaml](https://static.developer.mastercard.com/content/match/swagger-versioning/match-pro-3.0.7.yaml) (63KB) | | May 30, 2025 | 3.0.6 | Match Pro | Unnecessary URL's field were removed from the inquiry responses. The missing field acquirerId was added to the retro details response. The reasonCode field's maxLength in the terminated merchant schema was updated. Accordingly the match-pro-ref-app YAML was updated to reflect these changes. current OAS file [match-pro-3.0.6.yaml](https://static.developer.mastercard.com/content/match/swagger-versioning/match-pro-3.0.6.yaml) (63KB) | | May 21, 2025 | 3.0.5 | Match Pro | Updated field validations including corrected maxLength and minLength constraints, enhanced description fields for better clarity, and refined pattern validations to ensure stricter input adherence. Previous OAS file [match-pro-3.0.5.yaml](https://static.developer.mastercard.com/content/match/swagger-versioning/match-pro-3.0.5.yaml) (63KB) | | May 21, 2025 | 3.0.3 | Match Legacy | Refine field validations: corrected the maxLength values, updated URL length limit. current OAS file [match-v3.yaml](https://static.developer.mastercard.com/content/match/swagger/match-v3.yaml) (46KB) | | May 09, 2025 | 3.0.4 | Match Pro | Corrected maxlength and description. Previous OAS file [match-pro-3.0.4.yaml](https://static.developer.mastercard.com/content/match/swagger-versioning/match-pro-3.0.4.yaml) (62KB) | | May 08, 2025 | 3.0.3 | Match Pro | Previous OAS file [match-pro-3.0.3.yaml](https://static.developer.mastercard.com/content/match/swagger-versioning/match-pro-3.0.3.yaml) (61KB) | | May 09, 2025 | 3.0.2 | Match Legacy | Corrected maxlength,description and removed unused properties. Previous OAS file [match-v3.0.2.yaml](https://static.developer.mastercard.com/content/match/swagger-versioning/match-v3.0.2.yaml) (47KB) | | May 08, 2025 | 3.0.1 | Match Legacy | Previous OAS file [match-v3.0.1.yaml](https://static.developer.mastercard.com/content/match/swagger-versioning/match-v3.0.1.yaml) (46KB) | ## Get Help {#get-help} ### Contact us for technical support. {#contact-us-for-technical-support}