Overview of MC portal:

MasterCard portal URL: www.mastercardconnect.com

MasterCard portal-> Data integrity online

Non-compliant edits are marked in red, while compliant edits are marked in green. The focus should be on addressing the non-compliant edits to ensure merchant compliance.

Select the corresponding ICA to identify the non-compliant edits and view the error description by clicking "Edit Name."

Select a report to view:

• Edit Summary Report: Provides an overall summary of entire edits. 
• Transaction Sample Report: Displays daily transaction details. 
• History Report: Tracks the history of all non-compliance edits.
• Top Error Report: Presents a monthly report.
• Daily Compliance Report: Lists daily compliance records.

Extensions: 

    If the edit is not resolved within the timeframe provided by Mastercard, this option can be used to request an extension. To proceed with the request, we must provide a valid reason for the extension and a detailed business plan outlining how the issue will be resolved. Mastercard will then review the request and determine whether to approve or decline it.

Steps to resolve the errors:

Review each edit description to determine whether the error needs to be addressed by the vendor, the processor, or our team.

• Vendor-Side Issue: Contact the relevant vendor and notify them to correct the issue.
• Processor-Side Issue: No action is required, as the processor will likely resolve the issue before the deadline.
• MI-Side Issue: Conduct a detailed review and make any necessary corrections, whether on the merchant or terminal side, or update to the latest firmware if required.

If the root cause is unclear, create a ticket in the TMS VAR sheet for further investigation. Based on the response from TMS VAR support (TSYS), determine whether the issue is related to the processor or another party, and take appropriate action.

Reaching out the vendors/agents:

Use the canned email templates available in Freshdesk to notify the relevant vendors or agents. Ensure that the sample transaction report and edit description are attached for reference.

History of the Errors:

1.CC_Missing_EMVtags_DE55(Chip issue):

Updating the device to the latest firmware will resolve this edit.

2.PDS error:

There appears to be a customer type mismatch, where the software/terminal is not providing the correct check-in/check-out dates. Please reach out to them and check if they can fix this issue.

If the software is not compatible, you have the following options to resolve the issue:

1. Switch the application and MCC code to retail.
2. Switch to a software/terminal that supports lodging.

3.Software MPOS: 

As confirmed with the processor (TSYS), the vendor will need to contact VAR support to open a ticket and address these issues. The error occurred because Sierra itself is compliant with the edit, provided all POS vendors are up to date with their certification.

We have reached out to all affected vendors (ISO Access Mobile Swiper, Charge Anywhere, Valor, Aloha, Tabit, and Touch Bistro) and have fixed the issue.

4.Merchant Country of Origin 0100 & 1240 :

It appears the country code is missing or invalid (only for government merchants). Please reach out to the agent and notify to correct it. 

5.AC_Inv_form_DE55:

According to Mastercard, a mobile number should not be entered in place of an address. As this requirement was recently updated, TSYS was mapped the correct details later. 

6. Edit 36- MPG ID 0100:

TSYS side issue and was resolved.

 Ongoing errors:

1. Edit 30- ECOM COF MIT CIT Ind 0100

2. Edit 17-AUTH_PREAUTH_0100

3. Edit 2- CC_Missing_EMVtags_DE55 

4. Edit 2- Merchant ID

5. Edit 38- Inavlid street