Data Integrity Monitoring

Program
9 May 2019

DIMP
 Summary of Changes, 1 May 2019

Summary of Changes, 1 May 2019

This summary reflects changes effective since the last update of this publication.

Field Description
Throughout Changes made to create consistent language and
formatting. No changes to technical content.

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 2
 Contents

Contents

Summary of Changes, 1 May 2019..................................................................... 2

Chapter 1: Data Integrity Monitoring............................................................... 5

Data Integrity Monitoring Overview....................................................................................6
Data Integrity Online Report Availability..............................................................................6
Data Integrity Support........................................................................................................6
Registering for Online Access............................................................................................. 7
MasterCard Connect Access.......................................................................................... 7
How to Order Data Integrity Online............................................................................... 8
Data Integrity Online Access.......................................................................................... 8
How to Enter Additional ICA numbers to your Data Integrity Online Profile....................9
Noncompliance Assessments............................................................................................10
New Billing Event Code............................................................................................... 10
Data Integrity Monitoring............................................................................................ 10
Assessment Extension Requests................................................................................... 11
Data Integrity Monitoring Tiers (Acquirers/Processors).......................................................12
Data Integrity Monitoring Threshold (Issuers).................................................................... 13
Data Integrity Online Reports (Acquirers/Issuers/Processors).............................................. 13
DI Edit Summary Report...............................................................................................14
Transaction Samples Report......................................................................................... 14
Transaction Sample Reports for Acquirers and Issuers.............................................. 14
Data Integrity History...................................................................................................18
Downloadable Compliance Report...............................................................................19
Accepted Cities Report................................................................................................ 20

Chapter 2: Data Integrity Edits List...................................................................21

Data Integrity Edits List Overview......................................................................................22
Acquirer Authorization Dual Message System Edits (0100)................................................22
Acquirer Clearing Dual Message System Edits (1240)........................................................43
Acquirer Authorization Chip Dual Message System Edits (0100)....................................... 58
Acquirer Clearing Chip Dual Message System Edits (1240)................................................69
Acquirer Debit Single Message System Edits (0200).......................................................... 73
Acquirer Debit Single Message System Chip Edits (0200).................................................. 86
Issuer Authorization Dual Message System Edits (0110)....................................................94
Issuer Debit Single Message System Edits (0210)............................................................ 110
Issuer Chargeback Program............................................................................................ 114
Global Collection Only Edits........................................................................................... 117
Mastercard Identity Check (AReq/ARes).......................................................................... 124

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 3
 Contents

Appendix A: Global Collection Only Program (GCO).............................128

Appendix B: Data Integrity Program Extension Policy and

Procedures................................................................................................................... 129
Data Integrity Noncompliance Extension.........................................................................129
Request Extension in Edit Tile......................................................................................... 130
No Forms to Attach and Send by Email...........................................................................130
Extension History............................................................................................................130
Submission Deadline...................................................................................................... 131
Data Integrity Support....................................................................................................131

Appendix C: Exclusions.........................................................................................132

Notices...........................................................................................................................133

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 4
 Data Integrity Monitoring

Chapter 1 Data Integrity Monitoring

This information provides data monitoring guidelines and explains the data integrity
process used by Mastercard to monitor transactions submitted by customers.

Data Integrity Monitoring Overview................................................................................................ 6

Data Integrity Online Report Availability.......................................................................................... 6
Data Integrity Support.....................................................................................................................6
Registering for Online Access.......................................................................................................... 7
MasterCard Connect Access.......................................................................................................7
How to Order Data Integrity Online............................................................................................ 8
Data Integrity Online Access....................................................................................................... 8
How to Enter Additional ICA numbers to your Data Integrity Online Profile.................................9
Noncompliance Assessments.........................................................................................................10
New Billing Event Code............................................................................................................ 10
Data Integrity Monitoring......................................................................................................... 10
Assessment Extension Requests................................................................................................ 11
Data Integrity Monitoring Tiers (Acquirers/Processors)................................................................... 12
Data Integrity Monitoring Threshold (Issuers).................................................................................13
Data Integrity Online Reports (Acquirers/Issuers/Processors)........................................................... 13
DI Edit Summary Report........................................................................................................... 14
Transaction Samples Report...................................................................................................... 14
Transaction Sample Reports for Acquirers and Issuers...........................................................14
Data Integrity History................................................................................................................18
Downloadable Compliance Report........................................................................................... 19
Accepted Cities Report............................................................................................................. 20

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 5
 Data Integrity Monitoring
Data Integrity Monitoring Overview

Data Integrity Monitoring Overview

Data integrity monitors Single and Dual message data submitted by acquirers/issuers/
processors.
Through select edits and edit criteria Mastercard Data Integrity may resolve inefficiencies that
could impact the integrity of acquirer/issuer/processor transaction data. The Data Integrity
Monitoring Program helps acquirers/issuers/processors reduce exception processing and
through greater processing efficiency and accuracy, may improve profitability.
The Mastercard Data Integrity online application can be accessed through Mastercard
Connect™, Applications, Data Integrity Online. This online application provides a convenient
way for acquirers/issuers/processors to run customized reporting and access additional Data
Integrity information.

Data Integrity Online Report Availability

Mastercard wants to ensure that acquirers/issuers/processors have enough opportunity to
identify and address data integrity issues.
Mastercard requires each ICA Number/Processor ID be licensed for Data Integrity Online to
review reports monthly. All acquirers/issuers/processors are required to designate a contact to
register for access to this application through Mastercard Connect. An email will be sent to all
noncompliant ICA Numbers/Processor IDs with access to Data Integrity Online to alert them of
monthly noncompliant issues. ICA Numbers/Processor IDs that do not gain access to Data
Integrity On-line will not receive the noncompliant email alert. The Data Integrity Online
application is a self- service tool that allows acquirers/issuers/processors to run their own
reports. The data for the reports will be available at the beginning of each month.
Guidelines:
• All noncompliant acquirers/issuers/processors must log into Data Integrity Online monthly
to review their noncompliant status on the data Integrity Dashboard.
• Acquirers/issuers/processors must correct errors by the date provided on the noncompliance
edit tile on the dashboard, and to avoid noncompliant assessments, must remain compliant
for two consecutive reporting months after corrections have been made.

Data Integrity Support

Data integrity online support is available by email and through local help desks.
For Data Integrity Online support, please contact:

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 6
 Data Integrity Monitoring
Registering for Online Access

Franchise Integrity

E-mail: [email protected]

For more information about the Data Integrity Online application, please contact your regional
Help Desk, or the Customer Technical Services team.
Conference calls and/or training is available upon request by sending an e-mail to
[email protected]

Registering for Online Access

Data integrity online access requires Mastercard Connect.
Customers must have access to Mastercard Connect to use the Data Integrity Online
application. Acquirers/issuers/processors must register online for each of the following
products.

MasterCard Connect Access

Complete the following steps to register for MasterCard Connect.

Procedure
1. To register for access to MasterCard Connect, navigate to www.mastercardconnect.com.

2. Click New User? Sign up.

3. Complete all the steps provided in the registration process.

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 7
 Data Integrity Monitoring
Registering for Online Access

How to Order Data Integrity Online

Perform these steps to order Data Integrity Online from Mastercard Connect.

Procedure
1. Navigate to www.mastercardconnect.com.
2. Log on using your user ID and security information.
3. Select Store.
4. Select Data Integrity Online.
5. Select Add to Cart.
6. Enter ICA number or Processor ID in the form, click Submit.

NOTE: You may be required to contact the security administrator for the ICA number or
Processor ID for approval prior to obtaining final approval by Mastercard.

Data Integrity Online Access

About this task

After successfully registering for Mastercard Connect and Data Integrity Online, follow these
steps to access the Data Integrity Online application.

Procedure
1. Navigate to www.mastercardconnect.com.
2. Log on using your User ID and Security Information.
3. Under Applications, select Data Integrity Online.

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 8
 Data Integrity Monitoring
Registering for Online Access

The Data Integrity Online application opens to the customer dashboard.

4. The Data Integrity Online application Home page appears.

How to Enter Additional ICA numbers to your Data Integrity Online Profile
Complete the following steps to update your data integrity online profile.

Procedure
1. From Mastercard Connect, click Store in the upper right corner of the main menu.
2. Click Data Integrity Online.
3. Click Manage Subscription.
4. On your profile, enter the additional ICA numbers.

NOTE: You will be requested to contact the security administrator at the ICA number or
Processor ID for approval prior to receiving final approval from Mastercard.

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 9
 Data Integrity Monitoring
Noncompliance Assessments

Noncompliance Assessments

New Billing Event Code

Beginning 01 October 2018, the billing event code associated to the Data Integrity Monitoring
Program will change from 2PN2123/TPN2123 to 2DC0100/TDC0100.
The billing event name will remain Data Integrity Monitoring Noncompliance. The details for
each billing event, including the edit for which the customer is noncompliant, will continue to
be provided within the billing invoice.
The Global Collection Only (GCO) and Issuer Monitoring Program* billing codes will also be
updated as indicated in the chart below.

Existing New Billing Billing Event Existing New Service New Service
Billing Event Event Name Service Code Code Name
2PN2123 2DC0100 Data Integrity PN DC Data
Monitoring Compliance
Program Fees
2PN1104 2DC0201 GCO Data PN DC Data
Collection and Compliance
Compliance Fees
2PN1105 2DC0200 GCO Program - PN DC Data
Data Quality Compliance
Assessment Fees
2SC2344 2DC0300 Issuer PN DC Data
Monitoring Compliance
Program* Fees
Noncompliance

*The Issuer Monitoring Program is referred to as the Issuer Chargeback Program elsewhere in
this manual.

Data Integrity Monitoring

Assessment Structure:
Effective 1 January 2018, Mastercard will update the Data Integrity Monitoring Program as
detailed below.
Mastercard will assess acquirers/issuers/processors that fall below the data integrity rating
thresholds established for each edit/program.
Any ICA number that is out of compliance with a Data Integrity Program edit will be assessed
a noncompliance fee for that edit.

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 10
 Data Integrity Monitoring
Noncompliance Assessments

The noncompliance assessments will begin to increase if the customer remains noncompliant
for a given edit nine months after the "comply by" date.
For example, if the ICA number has been noncompliant with Iss Auth Dual Msg (110) edit #2
ASI_APP_RT for ten (10) months, the customer will be assessed 5,000 USD or 17,000 BRL.
This assessment amount would remain the same up to the 18th month of noncompliance at
which time it would increase to the next level and so on. Indonesia is included in this new
assessment structure and will be assessed any applicable fees in RUPIAH.

Table 1: New Assessment Structure (Per Edit/Per Month)

Months noncompliant after comply by

date USD Reals
1 - 9 Months 2,500 8,500
10 - 18 Months 5,000 17,000
19 - 24 Months 10,000 34,000
2+ years 20,000 68,000

NOTE: This new assessment structure will not apply to the GCO reporting edit. It will continue
to bill at the current rates.

Assessment Extension Requests

Customers that want to request an extension should go to Data Integrity Online, click on
Extensions in the edit tile to open the options. Customers can then apply for an extension
per the current process by selecting Apply for Extension or they can view their history by
selecting Extension History.
Please review Appendix B for Data Integrity Extension Policy and Procedures.

NOTE: New Edits are given an initial six month grace period, unless otherwise specified in the
edit Announcement. No additional extensions will be approved for new edits.

NOTE: The MoneySend Variance Form is available on Data Integrity Online under the Help
tab. Please send completed Variance Request Forms to [email protected]

NOTE: No extensions are allowed on EMV_ARPC_0110 or EMV_ARPC_0210.

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 11
 Data Integrity Monitoring
Data Integrity Monitoring Tiers (Acquirers/Processors)

Data Integrity Monitoring Tiers (Acquirers/Processors)

Data Integrity Monitoring program noncompliance parameters include the following three
tiers only applicable to acquirers and processors.

NOTE: Not all edits participate in the tiered threshold approach. Please see each individual
edit description in Appendix A for varying thresholds.

The ICA number

If your monthly Dual Message System is determined to
(Authorization), Dual Message System (Clearing), be noncompliant
Chip Authorization, Chip Clearing or Chip volume if the data
per ICA number or Single Message System (Debit) integrity rating is
volume per processor ID total is… Tier Standards below…
More than 1 million Tier 1 standards 98%
149,000–1 million Tier 2 standards 97%
20,000–149,000 Tier 3 standards 97%

The table below illustrates an example of the noncompliance structure for Tier 1 (total first
presentments—4,040,980):

Number of Noncompliance
Clearing Edit Number Errors Data Integrity Rating Issues
1 (MCC) 118,526 97.1% Yes
2 (MERCHANT_ID) 51,469 98.7% No

The table below illustrates an example of the noncompliance structure for Tier 2 (total first
presentments—186,580):

Number of Noncompliance
Clearing Edit Number Errors Data Integrity Rating Issues
1 (MCC) 10,946 94.1% Yes
2 (MERCHANT_ID) 3,956 97.9% No

The table below illustrates an example of the noncompliance structure for Tier 3 (total
authorization—102,324):

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 12
 Data Integrity Monitoring
Data Integrity Monitoring Threshold (Issuers)

Number of Noncompliance
Edit Data Errors Data Integrity Rating Issues
1 (ADD_DATA) 243 99.82% No
6 (DE43) 6,476 93.67% Yes

Data Integrity Monitoring Threshold (Issuers)

The Data Integrity Monitoring program noncompliance thresholds for issuers are set at each
edit level and can be found within the Issuer edit descriptions.
Data Integrity Monitoring program noncompliance thresholds can be found in the Issuer edit
descriptions in Appendix A.

Data Integrity Online Reports (Acquirers/Issuers/Processors)

Data integrity reports inform customers of noncompliance issues.

NOTE: Due to space limitations, the Data Integrity online reports have not been completely
updated with all Mastercard standard industry terminology. Therefore, processing related to
Authorization or Clearing refers to the Dual Message System. Processing related to Debit,
refers to the Single Message System.

These data integrity reports inform customers of noncompliance issues, and can be found in
the Select Report to View drop down menu in each edit tile. Each report provides an export
option. Reports may be exported using Excel.
The reports found on the Select Report to View drop down menu on each edit tile include:
• DI Edit Summary Report
• Transaction Samples
• Data Integrity History

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 13
 Data Integrity Monitoring
Data Integrity Online Reports (Acquirers/Issuers/Processors)

DI Edit Summary Report

This report is a summary of a customers Data Integrity edit status (compliant or noncompliant)
by ICA Number/Processor ID for the period and program selected and provides a date by
which the acquirer’s/ processor’s system errors should be corrected.

Procedure
1. Click Select Report to View in edit tile.
2. When the report appears, examine the Compliance Issues column and look for
noncompliant edit number entries labeled Yes. As indicated in the following DI Edit
Summary report example, Edit Number 4, Edit Name, Date_Time is noncompliant.
3. Choose the Transaction Samples Report in the following section to view error samples
associated with the noncompliant edits listed on this DI Edit Summary Report.

Transaction Samples Report

This report is a detailed listing of noncompliant error transactions for the selected program,
ICA Number/Processor ID, and month that a customer can use along with the DI Edit
Summary Report to compare and correct noncompliant issues. These transaction reports also
include the option to mask the primary account number.

Transaction Sample Reports for Acquirers and Issuers

The transaction sample report provides a sample of errors for a specified date range.

About this task

Transaction Sample Reports can be run for a maximum of five consecutive days at a time,
(example: Date Range 09/07/18 to 09/11/18). This report is designed to provide a sample of
errors and is limited to 4,000 records. It may show all edit failures if there are less than 4,000
for the selected date range.

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 14
 Data Integrity Monitoring
Data Integrity Online Reports (Acquirers/Issuers/Processors)

Procedure
1. In the applicable edit title, use the Select Report To View drop-down list and select
Transaction Samples Report. The Report Parameter pop up will appear.
2. The Edit name should appear in the Select Edit(s) Row. Click Start Date Calendar and
End Date Calendar to select a maximum 5 day report range. The default is Masked
PAN; deselect to see the full PAN.
a. Click Show Report.

3. When the report appears, locate the Error Number and Error Description for the
noncompliant Edit Number and Edit Name that was found on the DI Edit Summary Report.
The following example shows, Error Number 4, Error Description, Date_Time.

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 15
 Data Integrity Monitoring
Data Integrity Online Reports (Acquirers/Issuers/Processors)

4. Refer to the Data Integrity Edits List in Appendix A to locate the Edit Number, Name, and
Edit Criteria that corresponds to the noncompliant edits found on the Transaction Samples
Report. For example, locate in the Acquirer Authorization Dual Message System Edits
(0100), Edit Number 4, Date_Time as shown in the following edit example.

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 16
 Data Integrity Monitoring
Data Integrity Online Reports (Acquirers/Issuers/Processors)

5. Review the detailed information related to the Transaction Samples Report to determine
your error. If you have questions, contact the Data Integrity Team.

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 17
 Data Integrity Monitoring
Data Integrity Online Reports (Acquirers/Issuers/Processors)

NOTE: Refer to the Data Integrity Edits List in Appendix A for a detailed description of all
edits.

Data Integrity History

The Data Integrity History report is a monthly history, by a selected program, of an ICA
Numbers/Processors compliance.
1. From the Dashboard View, click the program for which report is needed (for example, Acq
Auth Dual Msg [0100]).
2. Click the Select Report To View drop-down list in any edit tile and select History
Report.
This report displays the history of the previous 36 month’s compliant or noncompliant status
up to the current month for the particular program selected.

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 18
 Data Integrity Monitoring
Data Integrity Online Reports (Acquirers/Issuers/Processors)

Downloadable Compliance Report

The downloadable compliance report allows customers to export compliance data to Excel or
CSV.

About this task

This report allows customers to export compliance data for their registered ICA numbers to
Excel or CSV.

Procedure
1. From Dashboard View click Download Compliance.

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 19
 Data Integrity Monitoring
Data Integrity Online Reports (Acquirers/Issuers/Processors)

2. From the dialog box, select the applicable report Parameters. The default is ALL
Noncompliant Edits/ICA numbers and Excel.
3. Click Download.

Accepted Cities Report

The Accepted Cities Report can be found in the Reporting drop-down list in the upper right
corner of the screen.
The Accepted City Names Report allows a user to view a list of valid city names for a given
postal code.

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 20
 Data Integrity Edits List

Chapter 2 Data Integrity Edits List

This section provides a list of the Data Integrity Dual Message System, Single Message
System, and Chip edits.

Data Integrity Edits List Overview.................................................................................................. 22

Acquirer Authorization Dual Message System Edits (0100)............................................................ 22
Acquirer Clearing Dual Message System Edits (1240).................................................................... 43
Acquirer Authorization Chip Dual Message System Edits (0100).................................................... 58
Acquirer Clearing Chip Dual Message System Edits (1240)............................................................ 69
Acquirer Debit Single Message System Edits (0200).......................................................................73
Acquirer Debit Single Message System Chip Edits (0200)...............................................................86
Issuer Authorization Dual Message System Edits (0110).................................................................94
Issuer Debit Single Message System Edits (0210)......................................................................... 110
Issuer Chargeback Program.........................................................................................................114
Global Collection Only Edits........................................................................................................ 117
Mastercard Identity Check (AReq/ARes).......................................................................................124

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 21
 Data Integrity Edits List
Data Integrity Edits List Overview

Data Integrity Edits List Overview

In this section you will find detailed information on each edit monitored by Data Integrity. The
edits are grouped into programs based primarily on the type of transaction or data being
evaluated. The table below details how to read and interpret each edit.

Edit Number Numerical identifier within a program

Edit Title Unabbreviated title of edit
Name Name, as displayed on the Data Integrity Online application
Billing Code Identifier shown on billing statement. The same code may be used for many edits
within the Data Integrity Monitoring Program. Refer to the comments on the
billing statement for specific edit information.
Region(s) Geographical region or regions where this edit applies
Description Brief explanation of what is being monitored Ex: This edit monitors DE 43 (Card
Acceptor Name/Location) to ensure that all necessary values are present and
properly formatted.
Edit Criteria This section provides the detailed criteria that makes a transaction eligible for
monitoring (when applicable) as well as the criteria that causes a transaction to be
noncompliant.
Baseline/ Baseline: Number of transactions or failures required in a given month to be
Threshold eligible for monitoring
Threshold: Percentage or number of transactions that must pass the edit to be
considered compliant

Reference Documentation where additional information supporting this edit can be found

Acquirer Authorization Dual Message System Edits (0100)

The edits in this program focus on the data and product requirements monitored in the 0100/
Authorization Request message. In the Data Integrity Online application, the program name
appears in its abbreviated form, Acq Auth Dual Msg (0100).
Table of Contents:
• Edit 1 – ADD_DATA
• Edit 2 – AFD
• Edit 3 – Magstripe
• Edit 4 – Date_Time
• Edit 5 – Cntry 2
• Edit 6 – DE 43

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 22
 Data Integrity Edits List
Acquirer Authorization Dual Message System Edits (0100)

• Edit 7 – INV_STATE
• Edit 8 – TermPOS
• Edit 9 – POS Cnd
• Edit 10 – Ecom
• Edit 11 – A_PF_ID
• Edit 12 – Pure Magstripe ATM 0100
• Edit 13 – Pure Madstripe POS 0100
• Edit 14 – MERCHANT_AAV_UNIQUE (Retired from active monitoring)
• Edit 15 – INC_MAGSTRIPE_0100
• Edit 16 – AUTH_UNDEFINED_0100
• Edit 17 – AUTH_PREAUTH_0100
• Edit 18 – AFD_MAND_PRE_AUTH
• Edit 19 – INVALID_PRE_AUTH
• Edit 20 – ABU ACQ
• Edit 21 – Recurring COF Monitoring (0100)
• Edit 22 – Protocol Version Rate Edit
• Edit 23 – DS TRAN ID FOR AUTH TRAN

ADD_DATA

Edit Number 1
Edit Title DE 48 Additional Data
Name ADD_DATA
Billing Code 2DC0100
Region(s) Global
Description This edit monitors the values submitted in DE 48 (Additional Data – Private Use) to
ensure they are formatted correctly.
Edit Criteria A transaction is considered noncompliant if one or more of the following
subelements in DE 48 contain unrecognizable or improperly formatted values:
• Subelement 42 (Electronic Commerce Indicators)
• Subelement 43 (Universal Cardholder Authentication Field [UCAF])
• Subelement 61 (POS Data, Extended Condition Codes)
• Subelement 76 (Mastercard Electronic Acceptance Indicator)
• Subelement 82 (Address Verification Service Request)
• Subelement 90 (Lodging and Auto Rental Indicator)
• Subelement 95 (Mastercard Promotion Code)

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 23
 Data Integrity Edits List
Acquirer Authorization Dual Message System Edits (0100)

Edit Number 1
Baseline/ Baseline: 20,000 authorization requests
Threshold
Threshold: Customers with more than 1,000,000 authorization requests are
subject to a threshold of 98%.
Customers with 1,000,000 or fewer authorization requests are subject to a
threshold of 97%.

Reference Customer Interface Specification

AFD

Edit Number 2
Edit Title AFD
Name AFD
Billing Code 2DC0100
Region(s) Global (Some subedits apply to select countries.)
Description This edit monitors various standards associated with Automated Fuel Dispenser
(AFD) transactions.
Edit Criteria A customer is considered noncompliant if any of the following subedits apply:
a. A transaction is considered noncompliant if DE 18 (Merchant Type) is 5542 (AFD)
and DE 61, subfield 10 is not any of the following:
• 1 (Automated dispensing machine with PIN)
• 2 (Self-service terminal)
• 6 (Authorized Level 6 CAT: Electronic Commerce)

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 24
 Data Integrity Edits List
Acquirer Authorization Dual Message System Edits (0100)

Edit Number 2
b. In the US and Europe region only, a transaction is considered noncompliant if DE
18 is 5542 and no corresponding Authorization Advice/0120 or Reversal Request/
0400 is found on the same PAN.
Data used to match the Authorization Request/0100 with the Authorization
Advice/0120 includes:
• DE 2 (Primary Account Number [PAN])
• DE 7 (Transmission Date and Time)
• DE 11 (Systems Trace Audit Number [STAN])
• DE 32 (Acquiring Institution ID Code)
• DE 33 (Forwarding Institution ID Code)
Data used to match the Authorization Request/0100 with the Reversal Request/
0400 includes:
• DE 2
• DE 32
• DE 33
• DE 48 (Additional Data – Private Use), subelement 63 (Trace ID)

c. In the US only, a transaction is considered noncompliant if both of the following

are true:
• In the Authorization Request/0100, DE 18 is 5542
• In the Authorization Advice/0120, DE 60 ( Advice Reason Code), subfield 1
(Authorization Reason Code) is not 191 ( Acquirer Processing System [APS]
Completed Authorization Transaction )

d. In the US only, a transaction is considered noncompliant if within the

Authorization Advice/0120, the time submitted in DE 48 (Additional Data – Private
Use), subelement 15 (Authorization System Advice Date and Time) minus the time
submitted in DE 7 (0100 Authorization Transmission Date and Time) is greater than
60 minutes.
e. In the US only, a transaction is considered noncompliant if the time submitted in
DE 7 of the Reversal Request/0400 minus the time submitted in DE 7 of the
Authorization Request/0100 is greater than 24 hours.
Baseline/ Baseline: 1,000 AFD transactions
Threshold
Threshold: Customers with more than 1,000,000 authorization requests are
subject to a threshold of 98%.
Customers with 1,000,000 or fewer authorization requests are subject to a
threshold of 97%.

Reference Customer Interface Specification, Quick Reference Booklet

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 25
 Data Integrity Edits List
Acquirer Authorization Dual Message System Edits (0100)

Magstripe

Edit Number 3
Edit Title Magnetic Stripe Track Data (0100)
Name MAG_STRIPE
Billing Code 2DC0100
Region(s) Global
Description This edit monitors magnetic stripe data in DE 35 (Track 2 Data) and DE 45 (Track 1
Data) to validate that it corresponds appropriately to the Point of Service (POS)
Entry Mode and the Transaction Category Code (TCC).
Edit Criteria Magnetic stripe transactions are identified by one of the following values in DE 22
(POS Entry Mode) subfield 1 (POS Terminal PAN Entry Mode):
• 80 (Chip card at chip-capable terminal was unable to process transaction using
data on the chip; therefore, the terminal defaulted to the magnetic stripe-read
PAN)
• 90 (PAN auto-entry via magnetic stripe)
• 91 (PAN auto-entry via contactless magnetic stripe)
A transaction is considered noncompliant if any of the following subedits apply:

a. DE 22 is 80, 90, or 91 and neither DE 35 nor DE 45 is present

b. DE 22 is 80, 90, or 91 and DE 35 and DE 45 are both present
c. Both of the following are true:
• DE 22, subfield 1 is one of the following:
– 00 ( PAN entry mode unknown)
– 01 ( PAN manual entry)
– 03 ( PAN auto-entry via bar code reader)
– 04 ( PAN auto-entry via optical character reader [OCR])
– 79 (A hybrid terminal with an online connection to the acquirer failed in
sending a chip fallback transaction to the issuer)
– 81 (PAN/Token entry via electronic commerce with optional SecureCode -
AAV or DSRP cryptogram in UCAF)
• Either DE 35 or DE 45 is present

d. All of the following are true:

• DE 22 is 80, 90, or 91
• Either DE 35 or DE 45 is present
• DE 61 (POS Data), subfield 4 (POS Cardholder Presence) is not 0 (Cardholder
present)

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 26
 Data Integrity Edits List
Acquirer Authorization Dual Message System Edits (0100)

Edit Number 3
e. All of the following are true
• DE 22 is 80, 90, or 91
• Either DE 35 or DE 45 is present
• DE 61, subfield 5 (POS Card Presence) is 1 (Card not present)

f. All of the following are true:

• DE 22 is 80, 90, or 91
• Either DE 35 or DE 45 is present
• DE 48 (Additional Data – Private Use), character 1 (TCC) is T

Baseline/ Baseline: 20,000 authorization requests

Threshold
Threshold: Customers with more than 1,000,000 authorization requests are
subject to a threshold of 98%.
Customers with 1,000,000 or fewer authorization requests are subject to a
threshold of 97%.

Reference Customer Interface Specification

Date_Time

Edit Number 4
Edit Title Network Date and Time
Name DATE_TIME
Billing Code 2DC0100
Region(s) Global
Description This edit monitors the presence and accuracy of values in DE 7 (Transmission Date
and Time) which mark the date and time an authorization request is sent to
Mastercard.
Edit Criteria A transaction is considered noncompliant if the values in DE 7, subfield 1
(transmission date) and DE 7, subfield 2 (transmission time-UTC time zone) do not
match the Dual Message System date and time (+/- 3 minutes).
Note: Time must be submitted in UTC. Banknet time will be automatically
converted from St. Louis, Missouri time to UTC for comparison purposes. However,
the Transaction Sample report on Data Integrity Online will display values in St.
Louis, Missouri, USA time.

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 27
 Data Integrity Edits List
Acquirer Authorization Dual Message System Edits (0100)

Edit Number 4
Baseline/ Baseline: 20,000 authorization requests to be monitored
Threshold
Threshold: Customers with more than 1,000,000 authorization requests are
subject to a threshold of 98%.
Customers with 1,000,000 or fewer authorization requests are subject to a
threshold of 97%.

Reference Customer Interface Specification

Cntry 2

Edit Number 5
Edit Title Country Code or Postal Code Verification (0100)
Name CNTRY2
Billing Code 2DC0100
Region(s) This edit applies to the following countries: Argentina, Australia, Austria, Belgium,
Canada, Costa Rica, Czech Republic, Denmark, Finland, Germany, Greece,
Hungary, Israel, Korea, Kuwait, Malaysia, Netherlands, New Zealand, Norway,
Philippines, Puerto Rico , Singapore, Sweden, Switzerland, Taiwan, Thailand,
Turkey, USA, Venezuela
Description This edit monitors the postal code and/or country code submitted in DE 61 (POS
Data) to ensure values are present, valid, and correspond to the appropriate POS
location.
Edit Criteria A transaction is considered noncompliant if any of the following subedits apply:
a. DE 61, subfield 13 (POS Country Code) is blank or is not a valid country code
(Applies to all countries listed above)
b. DE 61, subfield 13 is 840 (USA) and DE 61, subfield 14 (POS Postal Code) is
blank or is not a valid US postal code
c. DE 43 (Card Acceptor Name/Location for All Transactions), subfield 5 (Card
Acceptor State or Country Code) is CAN and DE 61, subfield 14 is not a valid
postal code in Canada
d. DE 43, subfield 5 is AUS and DE 61, subfield 14 is not a valid postal code in
Australia
e. DE 43, subfield 5 is DEU and DE 61, subfield 14 is not a valid postal code in
Germany
f. DE 43, subfield 5 is ARG, FIN, MYS, KOR, AUT, NLD, SWE, BEL, GRC, NZL, CHE,
HUN, NOR, TWN, PHL, THA, ISR, TUR, CRI, PRI, CZE, DNK, KWT, SGP or VEN and
DE 61 subfield 14 contains “unknown” or is missing
Note: In DE 43, subfield 5 is the contents of positions 38-40.

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 28
 Data Integrity Edits List
Acquirer Authorization Dual Message System Edits (0100)

Edit Number 5
Baseline/ Baseline: 20,000 authorization requests
Threshold
Threshold: Customers with more than 1,000,000 authorization requests are
subject to a threshold of 98%.
Customers with 1,000,000 or fewer authorization requests are subject to a
threshold of 97%.

Reference Customer Interface Specification, Quick Reference Booklet

DE 43

Edit Number 6
Edit Title DE 43 - Card Acceptor Name and Location (0100)
Name DE 43
Billing Code 2DC0100
Region(s) Global
Description This edit monitors DE 43 (Card Acceptor Name/Location ) to ensure that all
necessary values are present and properly formatted.
Edit Criteria A transaction is considered noncompliant if any of the following subedits apply:
a. DE 43 is blank
b. DE 43, subfield 2 (Space) and/or subfield 4 (Space) contain anything other than
a space character
d. DE 61 ( POS Data) , subfield 13 (POS Country Code) is not 840 and DE 43,
subfield 5 ( Card Acceptor State or Country Code) is not a valid three-character
alphabetic country code
e. DE 43, subfield 1 (Card Acceptor Name) is all numeric, all one character, or all
sequential characters. e.g. ABCDEF
f. The following fields do not represent a valid combination:
• DE 61, subfield 4 (POS Cardholder Presence) is 0 (Cardholder present),
• DE 61, subfield 14 (POS Postal Code)
• DE 43, subfield 3 (Card Acceptor City)

Exclusions: Subedits d-f exclude transactions with the following MCCs related to
ATM and telephone services 6010, 6011, 6012, 4812, 4814, 4821.
Note: Subedit c has been removed from this edit.

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 29
 Data Integrity Edits List
Acquirer Authorization Dual Message System Edits (0100)

Edit Number 6
Edit Title DE 43 - Card Acceptor Name and Location (0100)
Baseline/ Baseline: 20,000 authorization requests to be monitored
Threshold
Threshold: Customers with more than 1,000,000 authorization requests are
subject to a threshold of 98%.
Customers with 1,000,000 or fewer authorization requests are subject to a
threshold of 97%.

Reference Customer Interface Specification, Quick Reference Booklet

INV_STATE

Edit Number 7
Edit Title Invalid State
Name INV_STATE
Billing Code 2DC0100
Region(s) USA and all US Territories
Description This edit monitors state submitted in DE 43 (Card Acceptor Name/Location) ,
subfield 5 (Card Acceptor State or Country Code [or Sub-Merchant Information, if
applicable]) to ensure that it is present, valid and corresponds to the country code
840 (US).
Edit Criteria A transaction is considered noncompliant if either of the following subedits apply:

a. DE 43, subfield 5 does not represent a valid state code, or the state code is not
present
b. DE 43, subfield 5 and DE 61 (POS Data) , subfield 14 (POS Postal Code) are both
present but do not represent a valid combination
Note: On non-ATM transactions the state code must be left justified.
Baseline/ Baseline: 20,000 authorization requests
Threshold
Threshold: Customers with more than 1,000,000 authorization requests are
subject to a threshold of 98%.
Customers with 1,000,000 or fewer authorization requests are subject to a
threshold of 97%.

Reference Customer Interface Specification

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 30
 Data Integrity Edits List
Acquirer Authorization Dual Message System Edits (0100)

TermPOS

Edit Number 8
Edit Title Terminal POS Processing Fields (0100)
Name TERM_POS
Billing Code 2DC0100
Region(s) Global
Description This edits monitors the values in DE 61 (POS Data) to ensure that the terminal
processing fields are valid and correspond appropriately to the data in DE 22 ( POS
Entry Mode).
Edit Criteria A transaction is considered noncompliant if any of the following subedits apply:
a. DE 61, subfield 1 (POS Terminal Attendance) is 2 ( No terminal used [voice/audio
response unit (ARU) authorization]; server) and DE 61, subfield 3 (POS Terminal
Location) is not 3 ( No terminal used [voice/ARU authorization]; server)
b. DE 61, subfield 3 is 3 and DE 61, subfield 1 is not 2
c. DE 61, subfield 1 is 1 (Unattended terminal [cardholder-activated terminal (CAT),
home PC, mobile phone, PDA]) and DE 61, subfield 10 (Cardholder-Activated
Terminal Level) is 0 ( Not a CAT transaction)
Exclusions: Subedit c excludes recurring payment transactions and transactions
with the following MCCs: 6011 (ATM), 4111 (Transportation – Suburban and Local
Commuter Passenger) , 4131 (Bus Lines), and 4784 (Bridge and Road Fees, Tolls)
d. DE 61, subfield 11 (POS Card Data Terminal Input Capability Indicator) is 1 ( No
terminal used [voice/ARU authorization]; server) and any of the following
conditions are true:
• DE 61, subfield 1 is not 2
• DE 61, subfield 3 is not 3
• DE 22, subfield 1 (POS Terminal PAN Entry Mode) is not one of the following
values:
– 00 (PAN entry mode unknown)
– 01 (PAN manual entry)
– 09 (PAN/Token entry via electronic commerce containing DSRP cryptogram
in DE 55)
– 10 COF
– 81 (PAN/Token entry via electronic commerce with optional SecureCode -
AAV or DSRP cryptogram in UCAF)
– 82 (PAN Auto Entry via Server)

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 31
 Data Integrity Edits List
Acquirer Authorization Dual Message System Edits (0100)

Edit Number 8
e. DE 22, subfield 1 is 00 and DE 61, subfield 11 is any of the following:
• 2 (Terminal supports magnetic stripe input only)
• 5 (Terminal supports EMV contact chip input and magnetic stripe input)
• 7 (Terminal supports magnetic stripe input and key entry input)
• 8 (Terminal supports EMV contact chip input, magnetic stripe input and key
entry input)

f. DE 61, subfield 11 is 6 (Terminal supports key entry input only) and DE 22,
subfield 1 is any of the following:
• 02 (PAN auto-entry via magnetic stripe—track data is not required)
• 90 (PAN auto-entry via magnetic stripe—the full track data has been read from
the data encoded on the card and transmitted within the authorization request
in DE 35 (Track 2 Data) or DE 45 (Track 1 Data) without alteration or truncation)
• 91 (PAN auto-entry via contactless magnetic stripe)

g. DE 61, subfield 5 (POS Card Presence) is 0 (Card Present) and DE 61, subfield 4
(POS Cardholder Presence) is any of the following:
• 1 (Cardholder not present, unspecified)
• 2 (Cardholder not present [mail/facsimile order])
• 3 (Cardholder not present [phone or ARU])
• 4 (Standing order/recurring transactions)
• 5 (Cardholder not present [Electronic order])

h. All of the following are true:

• DE 61, subfield 4 (Cardholder Presence) is 0 (Cardholder present)
• DE 61, subfield 5 is 1 (Card not present)
• DE 61, subfield 10 is not 7 (Authorized Level 7 CAT: Transponder transaction)

i. DE 61, subfield 5 is 1 and DE 22, subfield 1 is any of the following:

• 02
• 03 (PAN auto-entry via bar code reader)
• 04 (PAN auto-entry via optical character reader [OCR])
• 05 (PAN auto-entry via chip)
• 07 (PAN auto-entry via contactless M/Chip)
• 80 (Chip card at chip-capable terminal was unable to process transaction using
data on the chip; therefore, the terminal defaulted to the magnetic stripe-read
PAN)
• 90
• 91

j. DE 61, subfield 11 is 9 (Terminal supports EMV contact chip input only) and DE
22 subfield 1 is not 05

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 32
 Data Integrity Edits List
Acquirer Authorization Dual Message System Edits (0100)

Edit Number 8
Baseline/ Baseline: 20,000 authorization requests
Threshold
Threshold: Customers with more than 1,000,000 authorization requests are
subject to a threshold of 98%.
Customers with 1,000,000 or fewer authorization requests are subject to a
threshold of 97%.

Reference Customer Interface Specification

POS Cnd

Edit Number 9
Edit Title POS Condition Codes (0100)
Name POS_CND
Billing Code 2DC0100
Region(s) Global
Description This edit monitors DE 61 (POS Data) to ensure that all values submitted in subfields
1-11 are valid.
Edit Criteria A transaction is considered noncompliant if the values in any of the following
subfields in DE 61 are invalid:
• Subfield 1 (POS Terminal Attendance)
• Subfield 2 (Reserved)
• Subfield 3 (POS Terminal Location)
• Subfield 4 (POS Cardholder Presence)
• Subfield 5 (POS Card Presence)
• Subfield 6 (POS Card Capture Capabilities)
• Subfield 7 (POS Transaction Status)
• Subfield 8 (POS Transaction Security)
• Subfield 9 (Reserved)
• Subfield 10 (Cardholder-Activated Terminal Level)
• Subfield 11 (POS Card Data Terminal Input Capability)

Baseline/ Baseline: 20,000 authorization requests

Threshold
Threshold: Customers with more than 1,000,000 authorization requests are
subject to a threshold of 98%.
Customers with 1,000,000 or fewer authorization requests are subject to a
threshold of 97%.

Reference Customer Interface Specification

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 33
 Data Integrity Edits List
Acquirer Authorization Dual Message System Edits (0100)

Ecom

Edit Number 10
Edit Title Electronic Commerce Processing Fields
Name ECOM
Billing Code 2DC0100
Region(s) Global
Description This edit monitors electronic commerce processing fields to ensure they are
populated accurately.
Edit Criteria A transaction is considered noncompliant if any of the following subedits apply:
a. DE 22 (POS Entry Mode), subfield 1 (POS Terminal PAN Entry Mode) is not any of
the following:
• 09 (PAN/Token entry via electronic commerce containing DSRP cryptogram in
DE 55)
• 10 COF
• 81 (PAN/Token entry via electronic commerce with optional SecureCode -AAV
or DSRP cryptogram in UCAF)
• 82 (PAN Auto Entry via Server)
And one or both of the following conditions is true:
• DE 61 (POS Data), subfield 4 (Cardholder Presence) is 5 (Cardholder not present
[Electronic order])
• DE 61, subfield 10 (Cardholder-Activated Terminal Level) is 6 (Authorized Level
6 CAT: Electronic Commerce)

b. DE 48 (Additional Data), subelement 42 (Electronic Commerce Indicators) is not

present and any of the following conditions are true:
• DE 22 subfield 1 is 81 or 82
• DE 61 subfield 4 is 5
• DE 61 subfield 10 is 6

c. All of the following are true:

• DE 22, subfield 1 is 10 COF
• DE 61, subfield 4 is 5
• DE 61, subfield 10 is not 6

Baseline/ Baseline: 25 ecommerce transactions

Threshold
Threshold: Customers with more than 1,000,000 authorization requests are
subject to a threshold of 98%.
Customers with 1,000,000 or fewer authorization requests are subject to a
threshold of 97%.

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 34
 Data Integrity Edits List
Acquirer Authorization Dual Message System Edits (0100)

Edit Number 10
Reference Customer Interface Specification

A_PF_ID

Edit Number 11
Edit Title Authorization Payment Facilitator ID
Name A_PF_ID
Billing Code 2DC0100
Region(s) Global
Description This edit monitors the presence of the Payment Facilitator ID in DE 48 (Additional
Data – Private Use), subelement 37 (Additional Merchant Data) to ensure it is valid
and corresponds appropriately with other values in the authorization message.
Edit Criteria A transaction is considered noncompliant if any of the following subedits apply:
a. The Payment Facilitator is present in DE 48, subelement 37, subfield 1 (Payment
Facilitator) and the sub-merchant is not present in DE 48, subelement 37, subfield
3 (Sub-Merchant ID)
b. The Payment Facilitator ID is present DE 48, subelement 37, subfield 1 and DE
43 (Card Acceptor Name/Location), subfield 1 (Payment Facilitator & Sub-Merchant
Information) does not include an '*' separating Payment Facilitator name and sub-
merchant name
c. The value present in DE 48, subelement 37, subfield 1 is not a valid Payment
Facilitator ID
Baseline/ Baseline: 20,000 authorization requests
Threshold
Threshold: Customers with more than 1,000,000 authorization requests are
subject to a threshold of 98%.
Customers with 1,000,000 or fewer authorization requests are subject to a
threshold of 97%.

Reference Customer Interface Specification

Pure Magstripe ATM 0100

Edit Number 12
Edit Title Pure Magnetic Stripe – ATM (0100)
Name Pure Magstripe (Fallback) ATM 0100
Billing Code 2DC0100

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 35
 Data Integrity Edits List
Acquirer Authorization Dual Message System Edits (0100)

Edit Number 12
Region(s) Global
Description This edit monitors pure magnetic stripe ATM transactions that are submitted as
technical fallback.
Note: When an acquirer submits an ATM transaction as technical fallback for a
card that is only capable of magnetic stripe transactions, Mastercard will
automatically downgrade the transaction from technical fallback to magnetic
stripe. This change is indicated in DE 48 (Additional Data – Private Use),
subelement 74 (Additional Processing Information).

Edit Criteria A transaction is considered noncompliant when all of the following are true:
• DE 18 (Merchant Type) is 6011 (ATM)
• DE 48, subelement 74 is 90C (Chip Fallback Transaction Downgrade Process
Completed Successfully)

Baseline/ Baseline: N/A

Threshold
Europe Threshold: 20 failures
Non-Europe Threshold: 1,000 failures

Reference Customer Interface Specifications Manual, M/Chip Requirements for

Contact and Contactless

Pure Magstripe POS 0100

Edit Number 13
Edit Title Pure Magnetic Stripe – POS (0100)
Name Pure Magstripe (Fallback) POS 0100
Billing Code 2DC0100
Region(s) Global
Description This edit monitors pure magnetic stripe POS transactions that are submitted as
technical fallback.
Note: When an acquirer submits a POS transaction as technical fallback for a card
that is only capable of magnetic stripe transactions, Mastercard will automatically
downgrade the transaction from technical fallback to magnetic stripe. This change
is indicated in DE 48 (Additional Data – Private Use), subelement 74 (Additional
Processing Information).

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 36
 Data Integrity Edits List
Acquirer Authorization Dual Message System Edits (0100)

Edit Number 13
Edit Criteria A transaction is considered noncompliant when the all of the following are true:
• DE 18 (Merchant Type) is not 6011 (ATM), 4784 (Tolls), or 7523 (Automobile
Parking Lots and Garages)
• DE 48, subelement 74 is 90C ( Chip Fallback Transaction Downgrade Process
Completed Successfully)

Baseline/ Baseline: N/A

Threshold
Europe Threshold: 20 failures
Non-Europe Threshold: 1,000 failures

Reference Customer Interface Specifications Manual, M/Chip Requirements for

Contact and Contactless

INC_MAGSTRIPE_0100

Edit Number 15
Edit Title Inconsistent Magnetic Stripe (0100)
Name INC_MAGSTRIPE_0100
Billing Code 2DC0100
Region(s) Global
Description This edit monitors transactions performed with chip cards at chip capable terminals
that are submitted as magnetic stripe.
Edit Criteria A transaction is considered noncompliant if all of the following are true:
• DE 22 (POS Entry Mode), subfield 1 (POS Terminal PAN Entry Mode) is any of
the following:
– 02 (PAN auto-entry via magnetic stripe - track data is not required)
– 90 (PAN auto-entry via magnetic stripe – full track data)
• DE 35 (Track 2 Data) subfield 5 (Extended Service Code) begins with a value of
2 or 6, indicating a chip is present
• DE 61 (POS Data) subfield 11 (POS Card Data Terminal Input Capability
Indicator) is any of the following:
– 5 (Terminal supports EMV contact chip input and magnetic stripe input)
– 8 (Terminal supports EMV contact chip input, magnetic stripe input and key
entry input)
– 9 (Terminal supports EMV contact chip input only)
Exclusions: Transactions with MCCs 4784 (Tolls) and 7523 (Automobile Parking
Lots and Garages) are not monitored under this edit.

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 37
 Data Integrity Edits List
Acquirer Authorization Dual Message System Edits (0100)

Edit Number 15
Baseline/ Baseline: N/A
Threshold
Europe Threshold: 100 failures
Non-Europe Threshold: 1,000 failures

Reference Customer Interface Specifications, M/Chip Requirements for Contact and

Contactless

AUTH_UNDEFINED_0100

Edit Number 16
Edit Title Undefined Authorization Requests
Name AUTH_UNDEFINED_0100
Billing Code 2DC0100
Region(s) Canada, Latin America and the Caribbean, United States
Description This edit monitors approved purchase transactions that are submitted as
unidentified authorization requests.
Edit Criteria Transactions monitored under this edit are identified by the following criteria:
• DE 3 (Processing Code), subfield 1 (Cardholder Transaction Type Code) is 00
(Purchase)
• DE 39 (Issuer Response Code) is any of the following:
– 00 (Approved or completed successfully
– 08 (Honor with ID)
– 10 (Partial Approval)
– 87 (Purchase Amount Only, No Cash Back Allowed)
– DE 4 (Amount, Transaction) is greater than 0
A transaction is considered noncompliant if both of the following are true:
• DE 61 (POS Data) subfield 7 (POS Transaction Status) is 0 (Normal request -
original presentment)
• DE 48 (Additional Data – Private Use), subelement 61 (POS Data, Extended
Condition Codes), subfield 5 (Final Authorization Indicator) is 0 (Normal
Authorization/Undefined Finality) or is null

Baseline/ Baseline: 100,000 or more domestic transactions

Threshold
Threshold: 50%

Reference Customer Interface Specifications Manual

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 38
 Data Integrity Edits List
Acquirer Authorization Dual Message System Edits (0100)

AUTH_PREAUTH_0100

Edit Number 17
Edit Title Preauthorized Domestic Purchases
Name AUTH_PREAUTH_0100
Billing Code 2DC0100
Region(s) Canada, Latin America and the Caribbean, United States
Description The edit monitors approved domestic purchase transactions to determine what
percentage of the total volume was preauthorized.
Edit Criteria Transactions monitored under this edit are identified by the following criteria:
• DE 3 (Processing Code), subfield 1 (Cardholder Transaction Type Code) is 00
(Purchase)
– DE 4 (Amount, Transaction) is greater than 0
• DE 39 (Issuer Response Code) is any of the following:
– 00 (Approved or completed successfully)
– 08 ( Honor with ID)
– 10 (Partial Approval)
– 87 (Purchase Amount Only, No Cash Back Allowed)
• DE 61 (POS Data) subfield 7 (POS Transaction Status) is 4 (Preauthorized
Request)
Customers are considered noncompliant if preauthorized requests account for
25% or more of the all approved domestic purchase transactions.
Exclusions: This edit includes e-commerce transactions (POS entry mode of 81 in
DE 22, subfield 1). The following MCCs are excluded from this edit: 3000 – 3350,
3351 – 3500, 3501 – 3999, 4121, 4722, 4511, 5499, 5541, 5542, 5812, 5813,
5814, 5964, 5965, 5968, 5969, 7011, 7033, 7230, 7298, 7512, 7542, 7997

Baseline/ Baseline: 10,000 domestic authorization requests

Threshold
Threshold: 76% of domestic authorization requests are not preauthorized purchase
transactions

Reference Customer Interface Specifications

AFD_MAND_PRE_AUTH

Edit Number 18
Edit Title Preauthorized Maestro AFD
Name AFD_MAND_PRE_AUTH
Billing Code 2DC0100

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 39
 Data Integrity Edits List
Acquirer Authorization Dual Message System Edits (0100)

Edit Number 18
Region(s) Europe
Description This edit monitors Maestro AFD transactions to ensure that the authorization
request was preauthorized.
Edit Criteria A transaction is considered not compliant if DE 18 (Merchant Type) is 5542 (Fuel
Dispenser, Automated) and DE 61 (POS Data) subfield 7 (POS Transaction Status) is
not 4 (Preauthorized Request).
Baseline/ Baseline: 10 Maestro AFD transactions
Threshold
Threshold: 10 errors

Reference Customer Interface Specifications

INVALID_PRE_AUTH

Edit Number 19
Edit Title Invalid Preauthorization Request
Name INVALID_PRE_AUTH
Billing Code 2DC0100
Region(s) Europe
Description This edit monitors Maestro preauthorization transactions that are not associated
with unattended AFD, CNP, or Maestro contactless transit aggregated transactions.
Edit Criteria A transaction is considered noncompliant if DE 61 (POS Data), subfield 7 (POS
Transaction Status) is 4 (Preauthorized Request), and none of the following are
true:
• DE 18 (Merchant Type) is 5542 (Fuel Dispenser, Automated)
• DE 61, subfield 5 (POS Cardholder Presence) is 1 (Card not present)
• DE 48 (Additional Data – Private Use), subelement 64 (Transit Program), subfield
1 (Transit Transaction Type Indicator) is any of the following:
– 3 (Post-Authorized Aggregated)
– 4 (Authorized Aggregated Split Clearing)
– 6 (Post-authorized Aggregated Maestro)
– 7 (Debt Recovery)

Baseline/ Baseline: 50 Maestro preauthorized transactions

Threshold
Threshold: 50 errors

Reference Customer Interface Specifications

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 40
 Data Integrity Edits List
Acquirer Authorization Dual Message System Edits (0100)

ABU ACQ

Edit Number 20
Edit Title Automatic Billing Updater for Acquirers
Name ABU_ACQ
Billing Code 2DC0100
Region(s) LAC
Description This edit monitors the mandatory implementation of the Automatic Billing Updater
(ABU) by acquirers submitting Credential on File (COF) and recurring payment
transactions in Latin America and the Caribbean.
Edit Criteria Customers are monitored under this edit when they have on or more recurring
payment or COF transaction in a given month.
Customers are considered noncompliant when the following are true:
• Effective 1 January 2019, until 1 April 2019, the Latin America and Caribbean
acquirer has not initiated or completed implementation of an ABU project for
acquiring ICAs submitting COF and recurring payment transactions
• Effective 1 April 2019, Latin America and Caribbean acquirer has not
completed implementation of an ABU project for acquiring ICAs submitting
COF and recurring payment transactions
Note: All ICA numbers sharing a parent ICA number are considered compliant if
one child ICA number has implemented ABU.

Baseline/ Baseline: 1 recurring payment or COF transaction

Threshold
Threshold: N/A

Reference Transaction Processing Rules, section 5.7 “Use of Automatic Billing Updater”

Recurring COF Monitorying (0100)

Edit Number 21
Edit Title COF Indicator for Recurring Payments (0100)
Name COF Recurring Payments (0100)
Region(s) Global
Billing Code 2DC0100
Description This edit monitors the mandatory use of the COF indicator in recurring payment
transactions.

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 41
 Data Integrity Edits List
Acquirer Authorization Dual Message System Edits (0100)

Edit Number 21
Edit Criteria A transaction is considered noncompliant if both of the following are true:
• DE 61 (POS Data), subfield 4 (POS Cardholder Presence) is 4 (Standing order/
recurring transaction)
• DE 22 (POS Entry Mode), subfield 1 (POS Terminal PAN Entry Mode) is not 10
COF

Baseline/ Baseline: 1,000 COF transactions

Threshold
Threshold: 97%

Reference Customer Interface Specifications

Protocol Version Rate

Edit Number 22
Edit Title Protocol Version for Authenticated Transactions
Name Protocol Version Rate
Billing Code 2DC0100
Region(s) Global
Description This edit monitors transactions that were authenticated through 3DS 1.0 or EMV
3-DS to ensure that the program protocol is present.
Edit Criteria A transaction is considered noncompliant if both of the following are true:
• DE 48 (Additional Data – Private Use), subelement 42 (Electronic Commerce
Indicators) is a valid SLI (211, 212 or 215)
• DE 48, subelement 66 (Authentication Data), subfield 1 (Program Protocol) is
missing

Baseline/ Baseline: 1,000 3-DS transactions

Threshold
Threshold: 90%

Reference Customer Interface Specifications

DS TRAN ID FOR AUTH TRAN

Edit Number 23
Edit Title Directory Server Transaction ID For Authenticated Transactions
Name DS TRAN ID FOR AUTH TRAN
Billing Code 2DC0100

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 42
 Data Integrity Edits List
Acquirer Clearing Dual Message System Edits (1240)

Edit Number 23
Region(s) Global
Description This edit monitors transactions authenticated through EMV 3-D Secure to ensure
that the Directory Server (DS) Transaction ID is present.
Edit Criteria A transaction is considered noncompliant when all of the following are true:
• DE 48 (Additional Data – Private User), subelement 66 (Authentication Data),
subfield 1 (Program Protocol) is 2 (EMV 3–D Secure [3DS 2.0])
• DE 48, subelement 66, subfield 2 (Directory Server Transaction ID) is missing
Note: Transactions authenticated through 3DS 1.0 are not monitored under this
edit.

Baseline/ Baseline: 1,000 EMV 3-DS transactions

Threshold
Threshold: 90%

Reference Customer Interface Specifications

Acquirer Clearing Dual Message System Edits (1240)

The edits in this program focus on the data and product requirements monitored in the 1240/
First Presentment message. In the Data Integrity Online application, the program name
appears in its abbreviated form, Acq Clear Dual Msg (1240).
Edit 1 – MCC
Edit 2 – MERCHANT ID
Edit 3 – INV DE43
Edit 4 – CNTRY GEO
Edit 5 – INV_STREET
Edit 6 – INV ADDR
Edit 7 – TERM POS
Edit 8 – TRACE_ID
Edit 9 – POST_CD_MATCH
Edit 10 – POS_AUTH
Edit 11 – C_PF_ID
Edit 12 – POST_SLI_MATCH (Retired from active monitoring)
Edit 13 – MCC_MATCH
Edit 14 – MERCH_DBA_NAME_MATCH

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 43
 Data Integrity Edits List
Acquirer Clearing Dual Message System Edits (1240)

Edit 15 – MERCHANT_ID_MATCH (Retired from active monitoring)

Edit 16 – TERM_INPUT_MATCH
Edit 17 – AAV_RATE_CLEAR_TRAN

MCC

Edit Number 1
Edit Title Merchant Category Code
Name MCC
Billing Code 2DC0100
Region(s) Global
Description This edit monitors the invalid use of card acceptor business code/merchant
category code (MCC).
Edit Criteria A transaction is considered noncompliant if any of the following subedits apply:
a. The MCC in DE 26 (Card Acceptor Business Code [MCC]) falls between 3000–
3350 (Airlines and Air Carriers) and either of the following are true:
• DE 43 (Card Acceptor Name/Location), subfield 1(Card Acceptor Name [or
Payment Facilitator and Sub-Merchant Information, if applicable]), positions 1–9
do not match positions 1–9 of the abbreviated airline name
• DE 43, subfield 1, positions 1–9 do not match positions 1–9 of the MCC
Description

b. The MCC in DE 26 falls between 3351–3500 (Car Rental Agencies) and DE 43,
subfield 1, positions 1–9 do not match positions 1–9 of the MCC Description
c. The MCC in DE 26 falls between 3501–3999 and DE 43, subfield 1, positions 1–
9 do not match positions 1–9 of the MCC Description
d. The MCC in DE 26 is 4511 (Air Carriers, Airlines—Not Elsewhere Classified) and
DE 43, subfield 1, positions 1–9 match positions 1–9 of an abbreviated airline
name or DE 43, subfield 1, positions 1–9, match positions 1–9 of the 3xxx MCC
Description
e. The MCC in DE 26 is 7011 (Lodging – Hotels, Motels, Resorts – not elsewhere
classified) and DE 43, subfield 1, positions 1–13 match an MCC Description of
MCCs 3501–3999
f. The MCC in DE 26 is 7512 (Automobile Rental Agency – not elsewhere
classified) and DE 43, subfield 1, positions 1–11 match an MCC Description of
MCCs 3351–3441

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 44
 Data Integrity Edits List
Acquirer Clearing Dual Message System Edits (1240)

Edit Number 1
Baseline/ Baseline: 20,000 First Presentment/1240 transactions
Threshold
Threshold: Customers with more than 1,000,000 First Presentment/1240
transactions are subject to a threshold of 98%.
Customers with 1,000,000 or fewer First Presentment/1240 transactions are
subject to a threshold of 97%.

Reference IPM Clearing Formats, Quick Reference Booklet

MERCHANT ID

Edit Number 2
Edit Title Merchant ID
Name MERCHANT ID
Billing Code 2DC0100
Description This edit monitors the values in DE 42 (Card Acceptor ID Code) to ensure that each
Card Acceptor ID, or Merchant ID, has a unique address.
Region(s) Global
Edit Criteria Customers are considered noncompliant if the same Merchant ID value, found in
DE 42 (Card Acceptor ID Code) appears in multiple transactions but the following
values are not consistent:
• DE 43 (Card Acceptor Name/Location),subfield 2 (Card Acceptor Street Address)
• DE 43, subfield 3 (Card Acceptor City)
• DE 43, subfield 4 (Card Acceptor Postal Code)
• DE 43, subfield 5 (Card Acceptor State or Country Code)
NOTE: This edit only applies to face-to-face transactions

Baseline/ Baseline: 20,000 First Presentment/1240 transactions

Threshold
Threshold: Customers with more than 1,000,000 First Presentment/1240
transactions are subject to a threshold of 98%.
Customers with 1,000,000 or fewer First Presentment/1240 transactions are
subject to a threshold of 97%.

Reference GCMS Reference Manual, IPM Clearing Formats

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 45
 Data Integrity Edits List
Acquirer Clearing Dual Message System Edits (1240)

INV DE43

Edit Number 3
Edit Title Invalid Values DE 43
Name INV DE43
Billing Code 2DC0100
Region(s) Global
Description This edit monitors the values in DE 43 (Card Acceptor Name/Location) to ensure
they are valid and properly formatted.
Edit Criteria A transaction is considered noncompliant if any of the following subedits apply:
a. DE 43, subfield 1 is a street address
b. DE 43, subfield 1 is a telephone number and DE 26 (Card Acceptor Business
Code [MCC]) is not consistent with a telephone service
d. DE 43, subfield 1 is all numeric, all one character, or all sequential characters (for
example, ABCDEF)
Exclusions: Telephone Service MCCs

e. DE 43, subfield 1 does not contain the chain merchant name that is most
recognizable to the cardholder
Note: The Card Acceptor Name must contain the chain/franchise merchant name
at the beginning of this subfield. If a chain is listed in the 3000–3999 range of card
acceptor business codes (MCCs), use the exact chain name. If the merchant is part
of a chain/franchise and the cardholder would not recognize the chain/franchise
name, populate the recognizable name in DE 43, subfield 1, and provide PDS 0176
(Mastercard Assigned ID).

f. DE 43, subfield 1, positions 20-22 contains one of the following substrings:

“PAA”, “Rxx”, “Sxx”, “Wxx”, “PAY”
Baseline/ Baseline: 20,000 First Presentment/1240 transactions
Threshold
Threshold: Customers with more than 1,000,000 First Presentment/1240
transactions are subject to a threshold of 98%.
Customers with 1,000,000 or fewer First Presentment/1240 transactions are
subject to a threshold of 97%.

Reference GCMS Reference Manual, IPM Clearing Formats

CNTRY GEO

Edit Number 4
Edit Title Country Code or Postal Code Verification (1240)

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 46
 Data Integrity Edits List
Acquirer Clearing Dual Message System Edits (1240)

Edit Number 4
Name CNTRY GEO
Billing Code 2DC0100
Region(s) This edit applies to the following countries: Argentina, Australia, Austria, Belgium,
Canada, Costa Rica, Czech Republic, Denmark, Finland, Germany, Greece,
Hungary, Israel, Korea, Kuwait, Malaysia, Netherlands, New Zealand, Norway,
Philippines, Puerto Rico , Singapore, Sweden, Switzerland, Taiwan, Thailand,
Turkey, USA, Venezuela
Description This edit monitors the postal code and/or country code values submitted in DE 43
(Card Acceptor Name/Location) to ensure values are present, valid, and correspond
to the appropriate Point of Service (POS) location.
Edit Criteria A transaction is considered noncompliant if any of the following subedits apply:
a. DE 43 (Card Acceptor Name/Location) , subfield 6 (Card Acceptor Country
Code) is CAN and DE 43, subfield 4 (Card Acceptor Postal [ZIP] Code) is
“unknown” or is not a valid postal code in Canada
b. DE 43, subfield 6 is AUS and DE 43, subfield 4 is “unknown” or is not a valid
postal code in Australia
c. DE 43, subfield 6 is DEU and DE 43, subfield 4 is “unknown” or is not a valid
postal code in Germany
d. DE 43, subfield 6 is USA and DE 43, subfield 4 is not a valid US postal code
e. DE 43, subfield 6 is ARG, FIN, MYS, KOR, AUT, NLD, SWE, BEL, GRC, NZL, CHE,
HUN, NOR, TWN, PHL, THA, ISR, TUR, CRI, PRI, CZE, DNK, KWT, SGP or VEN and
DE 43, subfield 4 contains “unknown” or is not present
Baseline/ Baseline: 20,000 First Presentment/1240 transactions
Threshold
Threshold: Customers with more than 1,000,000 First Presentment/1240
transactions are subject to a threshold of 98%.
Customers with 1,000,000 or fewer First Presentment/1240 transactions are
subject to a threshold of 97%.

Reference IPM Clearing Formats

INV_STREET

Edit Number 5
Edit Title Invalid Street Address (1240)
Name INV_STREET
Billing Code 2DC0100

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 47
 Data Integrity Edits List
Acquirer Clearing Dual Message System Edits (1240)

Edit Number 5
Region(s) This edit applies to the following countries: United States, Canada, United
Kingdom, Australia, Italy, Germany, Brazil, China, France, India, Japan, Mexico,
Poland, Russian Federation, and Spain
Description This edit monitors the street address values in DE 43 (Card Acceptor Name/
Location), subfield 2 (Card Acceptor Street Address) to ensure they are valid and
properly formatted.
Edit Criteria A transaction is considered noncompliant if any of the following are true:
• DE 43, subfield 2 is null or all spaces
• DE 43, subfield 2 contains “unknown”
• DE 43, subfield 2 is all numeric
• DE 43, subfield 2 is less than three characters in length
• In the US only, DE 43, subfield 2 is missing the street number or street name
Exception: A value of “RR” is permitted in Canada

Baseline/ Baseline: 20,000 First Presentment/1240 transactions

Threshold
Threshold: Customers with more than 1,000,000 First Presentment/1240
transactions are subject to a threshold of 98%.
Customers with 1,000,000 or fewer First Presentment/1240 transactions are
subject to a threshold of 97%.

Reference IPM Clearing Formats

INV ADDR

Edit Number 6
Edit Title Invalid City/Address
Name INV ADDR
Billing Code 2DC0100
Region(s) Global (Some subedits apply to select countries.)
Description This edit monitors the values in DE 43 (Card Acceptor Name/Location) on face to
face transactions to ensure the city name is valid and corresponds appropriately to
the provided postal code.
Edit Criteria A transaction is considered noncompliant if any of the following subedits apply:
a. Globally, DE 43, subfield 3 (Card Acceptor City) contains invalid character sets
for the specified country code
b. In Canada, Germany, and Australia only, DE 43, subfield 4 (Card Acceptor Postal
[ZIP] Code) is invalid for the city populated in DE 43, subfield 3

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 48
 Data Integrity Edits List
Acquirer Clearing Dual Message System Edits (1240)

Edit Number 6
c. In the US only, either of the following are true:
• DE 43, subfield 3 is all spaces, all numeric, or null
– DE 43, subfield 3 and subfield 4 do not represent a valid combination

Baseline/ Baseline: 20,000 First Presentment/1240 transactions

Threshold
Threshold: Customers with more than 1,000,000 First Presentment/1240
transactions are subject to a threshold of 98%.
Customers with 1,000,000 or fewer First Presentment/1240 transactions are
subject to a threshold of 97%.

Reference IPM Clearing Formats

TERM POS

Edit Number 7
Edit Title Terminal POS Input Capability (1240)
Name TERM POS
Billing Code 2DC0100
Region(s) Global
Description This edit monitors the card data input capability in DE 22 (POS Entry Mode) to
ensure it corresponds appropriately to the terminal operating environment and
card data input mode.
Edit Criteria A transaction is considered noncompliant if any of the following subedits apply:
a. DE 22, subfield 1 (Terminal Data: Card Data Input Capability) is 1 (No POS
terminal used), and DE 22, subfield 7 (Card Data: Input Mode) is not any of the
following:
• 0 (PAN entry mode unknown)
• 1 (PAN manual entry; no terminal used)
• 7 COF
• S (PAN entry via electronic commerce)
• T ( PAN auto-entry via server)

b. DE 22, subfield 1 is 1, and DE 22, subfield 4 (Terminal Operating Environment) is

not 0 (No terminal used)
c. DE 22, subfield 5 (Cardholder Present Data) is 9 (Unknown; data unavailable)
d. DE 22, subfield 6 (Card Present Data) is 9 (Unknown; data unavailable)

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 49
 Data Integrity Edits List
Acquirer Clearing Dual Message System Edits (1240)

Edit Number 7
Baseline/ Baseline: 20,000 First Presentment/1240 transactions
Threshold
Threshold: Customers with more than 1,000,000 First Presentment/1240
transactions are subject to a threshold of 98%.
Customers with 1,000,000 or fewer First Presentment/1240 transactions are
subject to a threshold of 97%.

Reference IPM Clearing Formats

TRACE_ID

Edit Number 8
Edit Title Trace ID Match
Name TRACE_ID
Billing Code 2DC0100
Region(s) Global
Description This edit monitors the Trace ID value in the First Presentment/1240 to ensure it
corresponds accurately to the data in the Authorization Response/0110.
Edit Criteria A transaction is considered noncompliant if DE 63 (Transaction Life Cycle ID),
subfield 2 (Trace ID) does not match the data in DE 63 (Network Data) of the
authorization response.
Note: The Trace ID consists of the network reference number followed by the
network date.
Exclusions: Transactions that do not have online authorizations (these are
transactions that have a Dual Message System Clearing record but no Dual
Message System Authorization record).

Baseline/ Baseline: 20,000 First Presentment/1240 transactions

Threshold
Threshold: Customers with more than 1,000,000 First Presentment/1240
transactions are subject to a threshold of 98%.
Customers with 1,000,000 or fewer First Presentment/1240 transactions are
subject to a threshold of 97%.

Reference IPM Clearing Formats

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 50
 Data Integrity Edits List
Acquirer Clearing Dual Message System Edits (1240)

POST_CD_MATCH

Edit Number 9
Edit Title Postal Code Match
Name POST_CD_MATCH
Billing Code 2DC0100
Region(s) Global
Description This edit monitors the postal code value present in the First Presentment/1240
message to ensure that it matches the postal code value submitted in the
Authorization Request/0100.
Edit Criteria A transaction is considered noncompliant if DE 43 (Card Acceptor Name/Location),
subfield 4 (Card Acceptor Postal [ZIP] Code) of the First Presentment/1240 message
does not match DE 61 (POS Data) , subfield 14 (POS Postal Code) of the
Authorization/0100 message.
Exclusions: This edit only monitors face-to-face transactions.

Baseline/ Baseline: 20,000 First Presentment/1240 transactions

Threshold
Threshold: Customers with more than 1,000,000 First Presentment/1240
transactions are subject to a threshold of 98%.
Customers with 1,000,000 or fewer First Presentment/1240 transactions are
subject to a threshold of 97%.

Reference Customer Interface Specification, IPM Clearing Formats

POS_AUTH

Edit Number 10
Edit Title POS Authorization Values
Name POS_AUTH
Billing Code 2DC0100
Region(s) Global
Description This edit monitors the data in DE 22 (POS Entry Mode) of the First Presentment/
1240 to ensure that it corresponds appropriately to the data in DE 61 (Point of
Service Data) of the Authorization Request/0100.
Edit Criteria A transaction is considered noncompliant if any of the following subedits apply:

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 51
 Data Integrity Edits List
Acquirer Clearing Dual Message System Edits (1240)

Edit Number 10
e. Comparison of Clearing DE 22, subfield 5 (Cardholder Present Data) to
Authorization DE 61, subfield 4 (POS Cardholder Presence)
• Clearing DE 22, subfield 5 is 0 (Cardholder present) and Authorization DE 61,
subfield 4 is not 0 (Cardholder present)
• Clearing DE 22, subfield 5 is 1 (Cardholder not present - unspecified) and
Authorization DE 61, subfield 4 is not 1 (Cardholder not present-unspecified)
• Clearing DE 22, subfield 5 is 2 (Cardholder not present - mail/facsimile
transaction) and Authorization DE 61, subfield 4 is not 2 (Mail/facsimile order)
• Clearing DE 22, subfield 5 is 3 (Cardholder not present - phone order or from
Automated Response Unit [ARU]) and Authorization DE 61, subfield 4 is not 3
(Phone/Automated Response Unit [ARU] order).
• Clearing DE 22, subfield 5 is 4 (Cardholder not present – standing order/
recurring transactions) and Authorization DE 61, subfield 4 is not 4 (Standing
order/recurring transactions)
• Clearing DE 22, subfield 5 is 5 (Cardholder not present – electronic order: PC,
Internet, mobile phone or PDA) and Authorization DE 61, subfield 4 is not 5
(Electronic order)

f. Comparison of Clearing DE 22, subfield 6 (Card Present Data) to Authorization

DE 61, subfield 5 (POS Card Presence)
• Clearing DE 22, subfield 6 is 1 (Card present) and Authorization DE 61, subfield
5 is not 0 (Card present)
• Clearing DE 22, subfield 6 is 0 (Card not present) and Authorization DE 61,
subfield 5 is not 1 (Card not present)

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 52
 Data Integrity Edits List
Acquirer Clearing Dual Message System Edits (1240)

Edit Number 10
g. Comparison of Clearing DE 22, subfield 7 (Card Data: Input Mode) to
Authorization DE 22 (POS Entry Mode) , subfield 1 (POS Terminal PAN Entry Mode)
• Clearing DE 22, subfield 7 is 0 (PAN entry mode unknown) and Authorization
DE22, subfield 1 is not 00 (PAN entry mode unknown)
• Clearing DE 22, subfield 7 is 1 (PAN manual entry; no terminal used) and
Authorization DE 22, subfield 1 is not 01 (PAN manual entry)
• Clearing DE 22, subfield 7 is 2 (PAN auto-entry via magnetic stripe: track data is
not required within transaction) and Authorization DE 22, subfield 1 is not 02
(PAN auto-entry through magnetic stripe- track data not required)
• Clearing DE 22, subfield 7 is 0 (PAN entry mode unknown) and Authorization
DE 22, subfield 1 is not 03 (PAN auto-entry through bar code reader)
• Clearing DE 22, subfield 7 is 0 (PAN entry mode unknown) and Authorization
DE 22, subfield 1 is not 04 (PAN auto-entry through optical character reader)
• Clearing DE 22, subfield 7 is C (PAN auto-entry via Chip (Online authorized
transaction)) and Authorization DE 22, subfield 1 is not 05 (PAN auto-entry
through chip)
• Clearing DE 22, subfield 7 is M (PAN auto-entry through contactless M/Chip)
and Authorization DE 22, subfield 1 is not 07 (PAN auto-entry through
contactless M/Chip)
• Clearing DE 22, subfield 7 is R (PAN entry via electronic commerce containing
Digital Secure Remote Payment (DSRP) cryptogram within DE 55 (Integrated
Circuit Card [ICC]) and Authorization DE 22, subfield 1 is not 09 (PAN/Token
entry through electronic commerce containing DSRP cryptogram in DE 55)
• Clearing DE 22, subfield 7 is 6 (PAN manual entry using a terminal, or through
voice transaction after chip card read error or chip fallback transaction failure)
and Authorization DE 22, subfield 1 is not 79 (Hybrid terminal with an online
connection to the acquirer failed in sending a chip fallback transaction to the
issuer)
• Clearing DE 22, subfield 7 is B (PAN auto-entry via magnetic stripe: track data
provided unaltered within transaction (magnetic stripe entry may also be chip
fallback transaction)) and Authorization DE 22, subfield 1 is not 80 (Chip card
at chip-capable terminal was unable to process transaction using data on the
chip; therefore, terminal defaulted to the magnetic stripe-read PAN)
• Clearing DE 22, subfield 7 is S (PAN entry via electronic commerce) and
Authorization DE 22, subfield 1 is not 81 (PAN/Token entry through electronic
commerce with optional SecureCode-AAV or DSRP cryptogram in UCAF)
• Clearing DE 22, subfield 7 is T (PAN auto entry through server) and
Authorization DE 22, subfield 1 is not 82 (PAN auto-entry through Server)
• Clearing DE 22, subfield 7 is B (PAN auto-entry via magnetic stripe: track data
provided unaltered within transaction (magnetic stripe entry may also be chip
fallback transaction)) and Authorization DE 22, subfield 1 is not 90 (PAN auto-
entry through magnetic stripe)
• Clearing DE 22, subfield 7 is A (PAN auto-entry via contactless magnetic stripe:
track data provided unaltered within transaction) and Authorization DE 22,
subfield 1 is not 91 (PAN auto-entry through contactless magnetic stripe)

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 53
 Data Integrity Edits List
Acquirer Clearing Dual Message System Edits (1240)

Edit Number 10
• Clearing DE 22, subfield 7 is C (PAN auto-entry via Chip (Online authorized
transaction) and Authorization DE 22, subfield 1 is not 95 (Visa only. Chip card
with unreliable Card Verification Value [CVV] data)

Baseline/ Baseline: 20,000 First Presentment/1240 transactions

Threshold
Threshold: Customers with more than 1,000,000 First Presentment/1240
transactions are subject to a threshold of 98%.
Customers with 1,000,000 or fewer First Presentment/1240 transactions are
subject to a threshold of 97%.

Reference Customer Interface Specification, IPM Clearing Formats

C_PF_ID

Edit Number 11
Edit Title Clearing Payment Facilitator ID
Name C_PF_ID
Billing Code 2DC0100
Region(s) Global
Description This edit monitors the values in Private Data Subelement (PDS) 0208 (Additional
Merchant Data) to ensure that when a Payment Facilitator ID is present, a sub-
merchant ID is also present, and that all values submitted in the First Presentment/
1240 match the corresponding values in the Authorization Request/0100. This edit
also monitors proper formatting of the Payment Facilitator ID and sub-merchant ID.
Edit Criteria A transaction is considered noncompliant if any of the following subedits apply:
a. PDS 0208, subfield 1 (Payment Facilitator ID) is present and PDS 0208, subfield 2
(Sub-merchant ID) is missing
b. PDS 0208, subfield 1 of the First Presentment/1240 does not match DE 48
(Additional Data – Private Use), subelement 37 (Additional Merchant Data),
subfield 1 (Payment Facilitator ID) of the Authorization Request/0100
c. PDS 0208, subfield 1 of the First Presentment/1240 contains the Payment
Facilitator ID and DE 43 (Card Acceptor Name/Location for All Transactions),
subfield 1 ( Payment Facilitator & Sub-Merchant Information ) does not include an
'*' separating Payment Facilitator name and Sub-merchant name
d. PDS 0208, subfield 1 does not contain a valid Payment Facilitator ID

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 54
 Data Integrity Edits List
Acquirer Clearing Dual Message System Edits (1240)

Edit Number 11
Baseline/ Baseline: 20,000 First Presentment/1240 transactions
Threshold
Threshold: Customers with more than 1,000,000 First Presentment/1240
transactions are subject to a threshold of 98%.
Customers with 1,000,000 or fewer First Presentment/1240 transactions are
subject to a threshold of 97%.

Reference Customer Interface Specification, IPM Clearing Formats

MCC_MATCH

Edit Number 13
Edit Title Merchant Category Code Match
Name MCC_MATCH
Billing Code 2DC0100
Region(s) Global
Description This edit monitors the Merchant Category Code (MCC) in the First Presentment/
1240 to ensure it matches the MCC in the corresponding Authorization Request/
0100.
Edit Criteria A transaction is considered noncompliant if DE 26 (Card Acceptor Business Code
[MCC]) of the Frist Presentment/1240 and DE 18 (Merchant Type) of the
Authorization Request/0100 are not the same value.
Baseline/ Baseline: 20,000 First Presentment/1240 transactions
Threshold
Threshold: Customers with more than 1,000,000 First Presentment/1240
transactions are subject to a threshold of 98%.
Customers with 1,000,000 or fewer First Presentment/1240 transactions are
subject to a threshold of 97%.

Reference Customer Interface Specification, IPM Clearing Formats

MERCH_DBA_NAME_MATCH

Edit Number 14
Edit Title Merchant DBA Name Match
Name MERCH_DBA_NAME_MATCH
Billing Code 2DC0100
Region(s) Global

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 55
 Data Integrity Edits List
Acquirer Clearing Dual Message System Edits (1240)

Edit Number 14
Description This edit monitors the merchant Doing Business As (DBA) name in the First
Presentment/1240 to ensure it matches the DBA name in the corresponding
Authorization Request/0100.
Edit Criteria A transaction is considered noncompliant if DE 43 (Card Acceptor Name/Location) ,
subfield 1 (Card Acceptor Name) of the Frist Presentment/1240 and DE 43, subfield
1 of the Authorization Request/0100 are not the same value.
Baseline/ Baseline: 20,000 First Presentment/1240 transactions
Threshold
Threshold: Customers with more than 1,000,000 First Presentment/1240
transactions are subject to a threshold of 98%.
Customers with 1,000,000 or fewer First Presentment/1240 transactions are
subject to a threshold of 97%.

Reference Customer Interface Specification, IPM Clearing Formats

TERM_INPUT_MATCH

Edit Number 16
Edit Title Terminal Input Capability Indicator Match
Name TERM_INPUT_MATCH
Billing Code 2DC0100
Region(s) Global
Description This edit monitors the Terminal Input Capability Indicator in the First Presentment/
1240 to ensure it matches the Terminal Input Capability Indicator in the
corresponding Authorization Request/0100.

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 56
 Data Integrity Edits List
Acquirer Clearing Dual Message System Edits (1240)

Edit Number 16
Edit Criteria A transaction is considered noncompliant if any of the following criteria applies:
• Clearing DE 22 (POS Entry Mode), subfield 1 (Terminal Data: Card Data Input
Capability) is 0 (Input capability unknown or unspecified) and authorization DE
61 (POS Data), subfield 11 (POS Card Data Terminal Input Capability Indicator)
is not 0 (Input capability unknown or unspecified)
• Clearing DE 22, subfield 1 is 1 (No POS terminal used (e.g.; voice/ARU
authorization, MO/TO, electronic commerce, or other transactions originated
from a data server)) and authorization DE 61, subfield 11 is not 1 (no terminal
used; server)
• Clearing DE 22, subfield 1 is 2 (Terminal supports magnetic stripe input only)
and authorization DE 61, subfield 11 is not 2 (magnetic stripe input only)
• Clearing DE 22, subfield 1 is M (Contactless EMV/Chip (Proximity Chip)) and
authorization DE 61, subfield 11 is not 3 (Contactless EMV/Chip)
• Clearing DE 22, subfield 1 is A (Contactless Mag Stripe (Proximity Chip)) and
authorization DE 61, subfield 11 is not 4 (Contactless Mag Stripe)
• Clearing DE 22, subfield 1 is D (Terminal supports EMV contact chip input and
magnetic stripe input) and authorization DE 61, subfield 11 is not 5 (Terminal
supports EMV contact chip input and magnetic stripe input)
• Clearing DE 22, subfield 1 is 6 (Terminal supports key entry input only) and
authorization DE 61, subfield 11 is not 6 (Terminal supports key entry input
only)
• Clearing DE 22, subfield 1 is B (Terminal supports magnetic stripe input and key
entry input) and authorization DE 61, subfield 11 is not 7 (Terminal supports
magnetic stripe input and key entry input)
• Clearing DE 22, subfield 1 is C (Terminal supports EMV contact chip input,
magnetic stripe input and key entry input) and authorization DE 61, subfield 11
is not 8 (Terminal supports EMV contact chip input, magnetic stripe input, and
key entry input)
• Clearing DE 22, subfield 1 is 5 (Terminal supports EMV contact chip input only)
and authorization DE 61, subfield 11 is not 9 (Terminal supports EMV contact
chip input only)

Baseline/ Baseline: 20,000 First Presentment/1240 transactions

Threshold
Threshold: Customers with more than 1,000,000 First Presentment/1240
transactions are subject to a threshold of 98%.
Customers with 1,000,000 or fewer First Presentment/1240 transactions are
subject to a threshold of 97%.

Reference Customer Interface Specification, IPM Clearing Formats

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 57
 Data Integrity Edits List
Acquirer Authorization Chip Dual Message System Edits (0100)

AAV_RATE_CLEAR_TRAN

Edit Number 17
Edit Title Valid AAV for Authenticated Transactions (1240)
Name AAV_RATE_CLEAR_TRAN
Billing Code 2DC0100
Region(s) Global
Description This edit monitors the Accountholder Authentication Value (AAV) in transactions
that were authenticated through 3-DS 1.0 or EMV 3-DS to ensure it is valid and
corresponds appropriately to the security level indicator (SLI).
Edit Criteria A transaction is considered noncompliant when Private Data Subfield (PDS) 0052
(Electronic Commerce Security Level Indicator [SLI]) contains a valid SLI (211 or
212), but PDS 0185 (AAV) does not begin with j, k, or h.
Baseline/ Baseline: 1,000 3-DS transactions
Threshold
Threshold: 90%

Reference IPM Clearing Formats

Acquirer Authorization Chip Dual Message System Edits (0100)

The edits in this program focus on chip data and EMV requirements monitored in the 0100/
Authorization Request message. In the Data Integrity Online application, the program name
appears in its abbreviated form, Acq Auth Chip Dual Msg (0100).

NOTE: Before sending and/or receiving chip transactions, every customer is required to test
with Mastercard through a chip implementation project. Once the chip implementation
project is successfully completed, Customer Implementation Services activates the customer's
chip testing status flag to correspond to the profile that was implemented. Data Integrity
monitors specific fields to validate the status of the codes and ensure they remain accurately
aligned with the chip implementation plan.

Table of Contents:
Edit 1 – AC_Missing_DE12
Edit 2 – AC_Missing_DE13
Edit 3 – AC_Missing_DE35
Edit 4 – AC_Missing_DE37
Edit 5 – AC_Missing_DE41
Edit 6 – AC_Missing_DE55

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 58
 Data Integrity Edits List
Acquirer Authorization Chip Dual Message System Edits (0100)

Edit 7 – AC_Inv_form_DE55
Edit 8 – AC_Missing_EMVtags_DE55
Edit 9 – AC_Inv_length_DE55
Edit 10 – AC_Inv_DE61_SF11
Edit 11 – Fallback Rt ATM 0100
Edit 12 – Fallback Rt POS 0100
Edit 13 – AC INC Magstripe 0100 (Retired from active monitoring)
Edit 14 – AC_INV_EMVTAGS_DE55

AC_Missing_DE12

Edit Number 1
Edit Title Missing DE 12 (0100)
Name AC_Missing_DE12
Billing Code 2DC0100
Region(s) Global
Description This edit monitors dual message chip transactions to ensure that the local time is
populated.
Edit Criteria Chip transactions monitored under this edit are identified by one of the following
values in DE 22 (Point of Service [POS] Entry Mode) , subfield 1 (POS Terminal PAN
Entry Mode):
• 05 (PAN auto-entry via chip)
• 07 (PAN auto-entry via contactless M/Chip)
• 80 (Chip card at chip-capable terminal was unable to process transaction using
data on the chip; therefore, the terminal defaulted to the magnetic stripe-read
PAN)
A transaction is considered noncompliant if DE 12 (Time, Local Transaction) is
missing.

Baseline/ Baseline: 20,000 chip transactions

Threshold
Threshold: Customers with more than 1,000,000 chip authorization requests are
subject to a threshold of 98%.
Customers with 1,000,000 or fewer chip authorization requests are subject to a
threshold of 97%.
Effective 1 November 2019, the threshold will change to 99.85% for all customers
that meet the baseline of 20,000 chip transactions.

Reference Customer Interface Specifications

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 59
 Data Integrity Edits List
Acquirer Authorization Chip Dual Message System Edits (0100)

AC_Missing_DE13

Edit Number 2
Edit Title Missing DE 13 (0100)
Name AC_Missing_DE13
Billing Code 2DC0100
Region(s) Global
Description This edit monitors dual message chip transactions to ensure that the local date is
populated.
Edit Criteria Chip transactions monitored under this edit are identified by one of the following
values in DE 22 (POS Entry Mode) , subfield 1 (POS Terminal PAN Entry Mode):
• 05 (PAN auto-entry via chip)
• 07 (PAN auto-entry via contactless M/Chip)
• 80 (Chip card at chip-capable terminal was unable to process transaction using
data on the chip; therefore, the terminal defaulted to the magnetic stripe-read
PAN)
A transaction is considered noncompliant if DE 13 (Date, Local Transaction) is
missing.

Baseline/ Baseline: 20,000 chip transactions

Threshold
Threshold: Customers with more than 1,000,000 chip authorization requests are
subject to a threshold of 98%.
Customers with 1,000,000 or fewer chip authorization requests are subject to a
threshold of 97%.
Effective 1 November 2019, the threshold will change to 99.85% for all customers
that meet the baseline of 20,000 chip transactions.

Reference Customer Interface Specifications

AC_Missing_DE35

Edit Number 3
Edit Title Missing DE 35 (0100)
Name AC_Missing_DE35
Billing Code 2DC0100
Region(s) Global
Description This edit monitors dual message chip transactions to ensure that the Track 2 data is
populated.

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 60
 Data Integrity Edits List
Acquirer Authorization Chip Dual Message System Edits (0100)

Edit Number 3
Edit Criteria Chip transactions monitored under this edit are identified by one of the following
values in DE 22 (POS Entry Mode) , subfield 1 (POS Terminal PAN Entry Mode):
• 05 (PAN auto-entry via chip)
• 07 (PAN auto-entry via contactless M/Chip)
A transaction is considered noncompliant if DE 35 ( Track 2 Data) is missing.

Baseline/ Baseline: 20,000 chip transactions

Threshold
Threshold: Customers with more than 1,000,000 chip authorization requests are
subject to a threshold of 98%.
Customers with 1,000,000 or fewer chip authorization requests are subject to a
threshold of 97%.
Effective 1 November 2019, the threshold will change to 99.85% for all customers
that meet the baseline of 20,000 chip transactions.

Reference Customer Interface Specifications

AC_Missing_DE37

Edit Number 4
Edit Title Missing DE 37 (0100)
Name AC_Missing_DE37
Billing Code 2DC0100
Region(s) Global
Description This edit monitors dual message chip transactions to ensure that the retrieval
reference number is populated.
Edit Criteria Chip transactions monitored under this edit are identified by one of the following
values in DE 22 (POS Entry Mode) , subfield 1 (POS Terminal PAN Entry Mode):
• 05 (PAN auto-entry via chip)
• 07 (PAN auto-entry via contactless M/Chip)
• 80 (Chip card at chip-capable terminal was unable to process transaction using
data on the chip; therefore, the terminal defaulted to the magnetic stripe-read
PAN)
A transaction is considered noncompliant if DE 37 (Retrieval Reference Number) is
missing.

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 61
 Data Integrity Edits List
Acquirer Authorization Chip Dual Message System Edits (0100)

Edit Number 4
Baseline/ Baseline: 20,000 chip transactions
Threshold
Threshold: Customers with more than 1,000,000 chip authorization requests are
subject to a threshold of 98%.
Customers with 1,000,000 or fewer chip authorization requests are subject to a
threshold of 97%.
Effective 1 November 2019, the threshold will change to 99.85% for all customers
that meet the baseline of 20,000 chip transactions.

Reference Customer Interface Specifications

AC_Missing_DE41

Edit Number 5
Edit Title Missing DE 41 (0100)
Name AC_Missing_DE41
Billing Code 2DC0100
Region(s) Global
Description This edit monitors dual message chip transactions to ensure that the Terminal ID is
populated.
Edit Criteria Chip transactions monitored under this edit are identified by one of the following
values in DE 22 (POS Entry Mode) , subfield 1 (POS Terminal PAN Entry Mode):
• 05 (PAN auto-entry via chip)
• 07 (PAN auto-entry via contactless M/Chip)
• 80 (Chip card at chip-capable terminal was unable to process transaction using
data on the chip; therefore, the terminal defaulted to the magnetic stripe-read
PAN)
A transaction is considered noncompliant if DE 41 (Card Acceptor Terminal ID) is
missing.

Baseline/ Baseline: 20,000 chip transactions

Threshold
Threshold: Customers with more than 1,000,000 chip authorization requests are
subject to a threshold of 98%.
Customers with 1,000,000 or fewer chip authorization requests are subject to a
threshold of 97%.
Effective 1 November 2019, the threshold will change to 99.85% for all customers
that meet the baseline of 20,000 chip transactions.

Reference Customer Interface Specifications

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 62
 Data Integrity Edits List
Acquirer Authorization Chip Dual Message System Edits (0100)

AC_Missing_DE55

Edit Number 6
Edit Title Missing DE 55 (0100)
Name AC_Missing_DE55
Billing Code 2DC0100
Region(s) Global
Description This edit monitors dual message chip transactions to ensure that the Integrated
Circuit Card [ICC] System-Related Data is populated.
Edit Criteria Chip transactions monitored under this edit are identified by one of the following
values in DE 22 (POS Entry Mode) , subfield 1 (POS Terminal PAN Entry Mode):
• 05 (PAN auto-entry via chip)
• 07 (PAN auto-entry via contactless M/Chip)
A transaction is considered noncompliant if DE 55 (ICC System-Related Data) is
missing.

Baseline/ Baseline: 20,000 chip transactions

Threshold
Threshold: Customers with more than 1,000,000 chip authorization requests are
subject to a threshold of 98%.
Customers with 1,000,000 or fewer chip authorization requests are subject to a
threshold of 97%.
Effective 1 November 2019, the threshold will change to 99.85% for all customers
that meet the baseline of 20,000 chip transactions.

Reference Customer Interface Specifications

AC_Inv_form_DE55

Edit Number 7
Edit Title DE 55 Invalid Format (0100)
Name AC_Inv_form_DE55
Billing Code 2DC0100
Region(s) Global
Description This edit monitors dual message chip transactions to validate correct formatting of
tag, length, value (TLV) in DE 55 (Integrated Circuit Card [ICC] System Related
Data).

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 63
 Data Integrity Edits List
Acquirer Authorization Chip Dual Message System Edits (0100)

Edit Number 7
Edit Criteria Chip transactions monitored under this edit are identified by one of the following
values in DE 22 (POS Entry Mode) , subfield 1 (POS Terminal PAN Entry Mode):
• 05 (PAN auto-entry via chip)
• 07 (PAN auto-entry via contactless M/Chip)
A transaction is considered noncompliant if the TLV is not formatted in accordance
with specifications outlined in M/Chip Requirements for Contact and
Contactless.
Note: DE 55 is not parsable.

Baseline/ Baseline: 20,000 chip transactions

Threshold
Threshold: Customers with more than 1,000,000 chip authorization requests are
subject to a threshold of 98%.
Customers with 1,000,000 or fewer chip authorization requests are subject to a
threshold of 97%.
Effective 1 November 2019, the threshold will change to 99.85% for all customers
that meet the baseline of 20,000 chip transactions.

Reference Customer Interface Specifications, M/Chip Requirements for Contact and

Contactless

AC_Missing_EMVtags_DE55

Edit Number 8
Edit Title Missing EMV Tags (0100)
Name AC_Missing_EMVtags_DE55
Billing Code 2DC0100
Region(s) Global
Description This edit monitors dual message chip transactions to ensure that all the required
EMV tags are present.
Edit Criteria Chip transactions monitored under this edit are identified by one of the following
values in DE 22 (POS Entry Mode) , subfield 1 (POS Terminal PAN Entry Mode):
• 05 (PAN auto-entry via chip)
• 07 (PAN auto-entry via contactless M/Chip)
A transaction is considered noncompliant if DE55 (Integrated Circuit Card [ICC]
System Related Data) is missing one or more required EMV tags.

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 64
 Data Integrity Edits List
Acquirer Authorization Chip Dual Message System Edits (0100)

Edit Number 8
Baseline/ Baseline: 20,000 chip transactions
Threshold
Threshold: Customers with more than 1,000,000 chip authorization requests are
subject to a threshold of 98%.
Customers with 1,000,000 or fewer chip authorization requests are subject to a
threshold of 97%.
Effective 1 November 2019, the threshold will change to 99.85% for all customers
that meet the baseline of 20,000 chip transactions.

Reference Customer Interface Specifications, M/Chip Requirements for Contact and

Contactless

AC_Inv_length_DE55

Edit Number 9
Edit Title Invalid Length of EMV Tag (0100)
Name AC_Inv_length_DE55
Billing Code 2DC0100
Region(s) Global
Description This edit monitors dual message chip transactions to ensure that all EMV tags are
the correct length.
Edit Criteria Chip transactions monitored under this edit are identified by one of the following
values in DE 22 (POS Entry Mode), subfield 1 (POS Terminal PAN Entry Mode):
• 05 (PAN auto-entry via chip)
• 07 (PAN auto-entry via contactless M/Chip)

Baseline/ Baseline: 20,000 chip transactions

Threshold
Threshold: Customers with more than 1,000,000 chip authorization requests are
subject to a threshold of 98%.
Customers with 1,000,000 or fewer chip authorization requests are subject to a
threshold of 97%.
Effective 1 November 2019, the threshold will change to 99.85% for all customers
that meet the baseline of 20,000 chip transactions.

Reference Customer Interface Specifications, M/Chip Requirements for Contact and

Contactless

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 65
 Data Integrity Edits List
Acquirer Authorization Chip Dual Message System Edits (0100)

AC_Inv_DE61_SF11

Edit Number 10
Edit Title Invalid Terminal Input Capability (0100)
Name AC_Inv_DE61_SF11
Billing Code 2DC0100
Description This edit monitors the terminal input capability to ensure that it corresponds
appropriately to the (POS) POS entry mode for chip transactions.
Edit Criteria A transaction is considered noncompliant if any of the following subedits apply:
a. DE 22 (POS Entry Mode), subfield 1 (POS Terminal PAN Entry Mode) is 05 (PAN
auto-entry via chip), and DE 61 (POS Data) , subfield 11 (POS Card Data Terminal
Input Capability Indicator) is not any of the following:
• 3 (Contactless EMV/Chip [Proximity Chip])
• 4 (Contactless Mag Stripe [Proximity Chip])
• 5 (Terminal supports EMV contact chip input and magnetic stripe input)
• 8 (Terminal supports EMV contact chip input, magnetic stripe input and key
entry input)
• 9 (Terminal supports EMV contact chip input only)

b. DE 22, subfield 1 is 07 ( PAN auto-entry via contactless M/Chip) and DE 61,

subfield 11 is not 3
c. DE 22, subfield 1 is 91 ( PAN auto-entry via contactless magnetic stripe) and DE
61, subfield 11 is not 3 or 4
Baseline/ Baseline: 20,000 chip transactions
Threshold
Threshold: Customers with more than 1,000,000 chip authorization requests are
subject to a threshold of 98%.
Customers with 1,000,000 or fewer chip authorization requests are subject to a
threshold of 97%.
Effective 1 November 2019, the threshold will change to 99.85% for all customers
that meet the baseline of 20,000 chip transactions.

Reference Customer Interface Specifications, M/Chip Requirements for Contact and

Contactless

Fallback Rt ATM 0100

Edit Number 11
Edit Title Technical Fallback Rate – ATM Transactions (0100)
Name Fallback Rt ATM 0100

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 66
 Data Integrity Edits List
Acquirer Authorization Chip Dual Message System Edits (0100)

Edit Number 11
Billing Code 2DC0100
Region(s) Global
Description This edit monitors ATM transactions performed with chip cards on chip-capable
terminals that are sent as Technical Fallback to magnetic stripe.
Edit Criteria A transaction is considered noncompliant if DE 18 (Merchant Type) is 6011 (ATM)
and DE 22 (POS Entry Mode), subfield 1 (POS Terminal PAN Entry Mode) is (80 Chip
card at chip-capable terminal was unable to process transaction using data on the
chip).
Baseline/ Baseline: 1,000 failures
Threshold
Threshold: 99%

Reference Customer Interface Specifications Manual,M/Chip Requirements for Contact

and Contactless

Fallback Rt POS 0100

Edit Number 12
Edit Title Technical Fallback Rate – POS Transactions (0100)
Name Fallback Rt POS 0100
Region(s) Global
Billing Code 2DC0100
Description This edit monitors POS transactions performed with chip cards on chip-capable
terminals that are sent as Technical Fallback to magnetic stripe.
Edit Criteria A transaction is considered noncompliant if DE 18 (Merchant Type) is not 6011
(ATM) and DE 22 (POS Entry Mode), subfield 1 (POS Terminal PAN Entry Mode) is
80 (Chip card at chip-capable terminal was unable to process transaction using
data on the chip).
Exclusions: MCCs 4784 (Bridge and Road Fees, Tolls) and 7523 (Automobile
Parking Lots and Garages) are not monitored under this edit.

Baseline/ Baseline: 1,000 failures

Threshold
Threshold: Non-US acquirers – 99%
US Acquirers - Minimum compliance rating increases, refer to the dates and
thresholds below:
• 1 OCT 2018 – 96%
• 1 APR 2019 – 97%
• 1 OCT 2019 – 98%
• 1 APRL 2020 – 99%

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 67
 Data Integrity Edits List
Acquirer Authorization Chip Dual Message System Edits (0100)

Edit Number 12
Reference Customer Interface Specifications Manual,M/Chip Requirements for Contact
and Contactless

AC_INV_EMVTAGS_DE55

Edit Number 14
Edit Title Invalid EMV Tags (0100)
Name AC_INV_EMVTAGS_DE55
Billing Code 2DC0100
Region(s) Global
Description This edit monitors dual message chip transactions to determine if any EMV tag
data is present in DE 55 (Integrated Circuit Card [ICC] System-Related Data) is
invalid.
Edit Criteria A transaction is considered noncompliant if any of the following subedits apply:
a. Tag 9F27 (Cryptogram Information Data) is not any of the following:
• 00
• 40
• 80

b. Tag 5F2A (Transaction Currency Code) does not contain a valid currency code
c. Tag 9F1A (Terminal Country Code) does not contain a valid country code
d. Tag 9A (Transaction Date) is not a valid date or is not submitted in the correct
format (YYMMDD)
e. Any bit designated as Reserved for Future Use (RFU) in Tag 95 (Terminal
Verification Results [TVR]) is not set correctly
h. 9F34 (Cardholder Verification Method Results) is missing or is not a valid value
Note: Letters (f) Tag 82 Application Interchange Profile and (g) Tag 84 Dedicated
File were removed from this edit.
Baseline/ Baseline: 20,000 chip transactions
Threshold
Threshold: Customers with more than 1,000,000 chip authorization requests are
subject to a threshold of 98%.
Customers with 1,000,000 or fewer chip authorization requests are subject to a
threshold of 97%.
Effective 1 November 2019 the threshold will change to 99.85% for all customers
that meet the baseline of 20,000 chip transactions.

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 68
 Data Integrity Edits List
Acquirer Clearing Chip Dual Message System Edits (1240)

Edit Number 14
Reference Customer Interface Specifications Manual,M/Chip Requirements for Contact
and Contactless

Acquirer Clearing Chip Dual Message System Edits (1240)

The edits in this program focus on the chip data and EMV requirements monitored in the
1240/First Presentment message. In the Data Integrity Online application, the program name
appears in its abbreviated form, Acq Clear Chip Dual Msg (1240).
Edit 1 – CC_Missing_DE55
Edit 2 – CC_Missing_EMVtags_DE55
Edit 3 – CC_Inv_Length_DE55
Edit 4 – CC_Inv_EMVtags_DE55
Edit 5 – CC_Inv_form_DE55

CC_Missing_DE55

Edit Number 1
Edit Title Missing DE 55 (1240)
Name CC_Missing_DE55
Billing Code 2DC0100
Region(s) Global
Description This edit monitors First Presentment/1240 chip transactions to ensure that the
Integrated Circuit Card [ICC] System-Related Data is populated.
Edit Criteria Chip transactions monitored under this edit are identified by one of the following
values in DE 22 (Point of Service [POS] Entry Mode), subfield 7(Card Data: Input
Mode):
• C (PAN auto-entry via chip [online authorized transaction])
• F (PAN auto-entry via chip [offline chip-approved transaction])
• M (PAN auto-entry via contactless M/Chip)
A transaction is considered noncompliant if DE 55 (Integrated Circuit Card [ICC]
System Related Data) is missing.

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 69
 Data Integrity Edits List
Acquirer Clearing Chip Dual Message System Edits (1240)

Baseline/ Baseline: 20,000 chip transactions

Threshold
Threshold: Customers with more than 1,000,000 chip transactions are subject to a
threshold of 98%.
Customers with 1,000,000 or fewer chip transactions are subject to a threshold of
97%.
Effective 1 November 2019 the threshold will change to 99.85% for all customers
that meet the baseline of 20,000 chip transactions.

Reference IPM Clearing Formats, M/Chip Requirements for Contact and Contactless

CC_Missing_EMVtags_DE55

Edit Number 2
Edit Title Missing EMV Tags (1240)
Name CC_Missing_EMVtags_DE55
Billing Code 2DC0100
Region(s) Global
Description This edit monitors First Presentment/1240 chip transactions to ensure that all of the
mandatory EMV tags are present.
Edit Criteria Chip transactions monitored under this edit are identified by one of the following
values in DE 22 (POS Entry Mode) , subfield 7(Card Data: Input Mode):
• C (PAN auto-entry via chip [online authorized transaction])
• F (PAN auto-entry via chip [offline chip-approved transaction])
• M (PAN auto-entry via contactless M/Chip)
A transaction is considered noncompliant if any of the mandatory EMV tags are
missing from DE55 (Integrated Circuit Card [ICC] System Related Data).

Baseline/ Baseline: 20,000 chip transactions

Threshold
Threshold: Customers with more than 1,000,000 chip transactions are subject to a
threshold of 98%.
Customers with 1,000,000 or fewer chip transactions are subject to a threshold of
97%.
Effective 1 November 2019 the threshold will change to 99.85% for all customers
that meet the baseline of 20,000 chip transactions.

Reference IPM Clearing Formats, M/Chip Requirements for Contact and Contactless

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 70
 Data Integrity Edits List
Acquirer Clearing Chip Dual Message System Edits (1240)

CC_Inv_Length_DE55

Edit Number 3
Edit Title Invalid Length of EMV Tag (1240)
Name CC_Inv_Length_DE55
Billing Code 2DC0100
Region(s) Global
Description This edit monitors First Presentment/1240 chip transactions to ensure that all of the
mandatory EMV tags are submitted with the correct length.
Edit Criteria Chip transactions monitored under this edit are identified by one of the following
values in DE 22 (POS Entry Mode), subfield 7(Card Data: Input Mode):
• C (PAN auto-entry via chip [online authorized transaction])
• F (PAN auto-entry via chip [offline chip-approved transaction])
• M (PAN auto-entry via contactless M/Chip)
A transaction is considered noncompliant if any of the mandatory EMV tags in
DE55 (Integrated Circuit Card [ICC] System Related Data) are not submitted with
the correct length.

Baseline/ Baseline: 20,000 chip transactions

Threshold
Threshold: Customers with more than 1,000,000 chip transactions are subject to a
threshold of 98%.
Customers with 1,000,000 or fewer chip transactions are subject to a threshold of
97%.
Effective 1 November 2019 the threshold will change to 99.85% for all customers
that meet the baseline of 20,000 chip transactions.

Reference IPM Clearing Formats, M/Chip Requirements for Contact and Contactless

CC_Inv_EMVtags_DE55

Edit Number 4
Edit Title Invalid EMV Tags (1240)
Name CC_Inv_EMVtags_DE55
Billing Code 2DC0100
Region(s) Global
Description This edit monitors First Presentment/1240 chip transactions to ensure that all of the
mandatory EMV tags are submitted with the correct format.

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 71
 Data Integrity Edits List
Acquirer Clearing Chip Dual Message System Edits (1240)

Edit Criteria Chip transactions monitored under this edit are identified by one of the following
values in DE 22 (POS Entry Mode), subfield 7(Card Data: Input Mode):
• C (PAN auto-entry via chip [online authorized transaction])
• F (PAN auto-entry via chip [offline chip-approved transaction])
• M (PAN auto-entry via contactless M/Chip)
A transaction is considered noncompliant if any of the mandatory EMV tags in
DE55 (Integrated Circuit Card [ICC] System Related Data) are not submitted with
the correct format.

Baseline/ Baseline: 20,000 chip transactions

Threshold
Threshold: Customers with more than 1,000,000 chip transactions are subject to a
threshold of 98%.
Customers with 1,000,000 or fewer chip transactions are subject to a threshold of
97%.
Effective 1 November 2019 the threshold will change to 99.85% for all customers
that meet the baseline of 20,000 chip transactions.

Reference IPM Clearing Formats, M/Chip Requirements for Contact and Contactless

CC_Inv_form_DE55

Edit Number 5
Edit Title DE 55 Invalid Format (1240)
Name CC_Inv_form_DE55
Billing Code 2DC0100
Region(s) Global
Description This edit monitors First Presentment/1240 chip transactions to ensure that DE 55
(Integrated Circuit Card [ICC] System Related Data) is formatted correctly.
Edit Criteria Chip transactions monitored under this edit are identified by one of the following
values in DE 22 (POS Entry Mode), subfield 7(Card Data: Input Mode):
• C (PAN auto-entry via chip [online authorized transaction])
• F (PAN auto-entry via chip [offline chip-approved transaction])
• M (PAN auto-entry via contactless M/Chip)
A transaction is considered noncompliant if DE 55 (Integrated Circuit Card [ICC]
System Related Data) is not formatted properly according to the specifications in
M/Chip Requirements for Contact and Contactless.
Exclusions: Refund transactions

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 72
 Data Integrity Edits List
Acquirer Debit Single Message System Edits (0200)

Baseline/ Baseline: 20,000 chip transactions

Threshold
Threshold: Customers with more than 1,000,000 chip transactions are subject to a
threshold of 98%.
Customers with 1,000,000 or fewer chip transactions are subject to a threshold of
97%.
Effective 1 November 2019 the threshold will change to 99.85% for all customers
that meet the baseline of 20,000 chip transactions.

Reference IPM Clearing Formats, M/Chip Requirements for Contact and Contactless

Acquirer Debit Single Message System Edits (0200)

The edits in this program focus primarily on the data in 0200/Financial Transaction message.
Most edits look at Point of Service (POS) transactions only, but ATM transactions may be
monitored where specified. In the Data Integrity Online application, the program name
appears in its abbreviated form, Acq Debit Single Msg (0200).
Edit 1 – D_INVMCC (5542)
Edit 2 – D_MAGSTRIPE
Edit 3 – D_INVTYPE
Edit 4 – D_DE42
Edit 5 – D_DE43
Edit 6 – D_CARDACP (Retired from active monitoring)
Edit 7 – D_TERMPOS
Edit 8 – D_POSCND
Edit 9 – D_PF_ID
Edit 10 – D_Pure_Magstripe ATM
Edit 11 – D_Pure Magstripe POS
Edit 12 – D_INC_MAGSTRIPE_0200
Edit 13 – D_MISREPORTED ATM FEE
Edit 14 – Recurring CoF Monitorying (0200)
Edit 15 – D_MISREPORTED ATM FEE NON US

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 73
 Data Integrity Edits List
Acquirer Debit Single Message System Edits (0200)

D_INVMCC (5542)

Edit Number 1
Edit Title Invalid use of MCC 5542
Name D_INVMCC (5542)
Billing Code 2DC0100
Region(s) Global
Description This edit monitors Automated Fuel Dispenser (AFD) transactions to ensure that the
Merchant Category Code (MCC) corresponds appropriately to the values in DE 61
(POS Data), subfield 10 (Cardholder-Activated Terminal Level).
Edit Criteria A transaction is considered noncompliant if DE 18 (Merchant Type) is 5542
(Automated Fuel Dispenser (AFD)) and DE 61, subfield 10 is not any of the
following:
• 1 (Automated dispensing machine with PIN)
• 2 (Self-service terminal)
• 6 ( Authorized Level 6 CAT: Electronic Commerce)

Baseline/ Baseline: 20,000 financial transactions

Threshold
Threshold: Customers with more than 1,000,000 transactions are subject to a
threshold of 98%.
Customers with 1,000,000 or fewer transactions are subject to a threshold of
97%.

Reference Single Message System Specifications

D_MAGSTRIPE

Edit Number 2
Edit Title Magnetic Stripe (0200)
Name D_MAGSTRIPE
Billing Code 2DC0100
Region(s) Global
Description This edit monitors magnetic stripe transactions to ensure that DE 35 (Track 2 Data)
and DE 45 (Track 1 Data) are present when necessary and correspond appropriately
to the values in various other data elements.

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 74
 Data Integrity Edits List
Acquirer Debit Single Message System Edits (0200)

Edit Number 2
Edit Criteria Magnetic stripe transactions are identified by one of the following values in DE 22
(POS Entry Mode) subfield 1 (POS Terminal PAN Entry Mode):
• 80 ( Chip card at chip-capable terminal was unable to process transaction using
data on the chip; therefore, the terminal defaulted to the magnetic stripe-read
PAN)
• 90 (PAN auto-entry via magnetic stripe)
• 91 (PAN auto-entry via contactless magnetic stripe)
A transaction is considered noncompliant if any of the following subedits apply:

a. DE22, subfield 1 is 80, 90, or 91 and neither DE 35 nor DE 45 are present

b. DE 22, subfield 1 is 80, 90, or 91 and both DE 35 and DE 45 are both present
c. Both of the following are true:
• DE 22, subfield 1 is one of the following:
– 00 ( PAN entry mode unknown)
– 01 ( PAN manual entry)
– 03 ( PAN auto-entry via bar code reader)
– 04 ( PAN auto-entry via optical character reader (OCR)
– 79 (Chip card at chip-capable terminal was unable to process transaction
using data on the chip; therefore, the terminal defaulted to the magnetic
stripe-read PAN. The full track data has been read from the data encoded on
the card and transmitted within the Financial Transaction Request/0200
message in DE 45 (Track 1 Data) or DE 35 (Track 2 Data) without alteration
or truncation)
– 81 ( PAN/Token entry via e-commerce with optional SecureCode-AAV or
DSRP cryptogram in UCAF)
• DE 35 or DE 45 is present

d. DE 22, subfield 1 is either 80, 90, or 91 and DE 35 or DE 45 is present, and DE

61 (POS Data) , subfield 4 POS Cardholder Presence) is not 0 (Cardholder present)
e. DE 22, subfield 1 is either 80, 90, or 91 and DE 35 or DE 45 is present, and DE
61, subfield 5 (POS Card Presence) is 1 (Card not present)
f. DE 22, subfield 1 is either 80, 90, or 91 and DE 35 or DE 45 is present and DE 48
(Additional Data), position 1 (Transaction Category Code [TCC]) is T (All Other Non-
Face-to-Face Transactions)
Baseline/ Baseline: 20,000 financial transactions
Threshold
Threshold: Customers with more than 1,000,000 transactions are subject to a
threshold of 98%.
Customers with 1,000,000 or fewer transactions are subject to a threshold of
97%.

Reference Single Message System Specifications, Quick Reference Booklet

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 75
 Data Integrity Edits List
Acquirer Debit Single Message System Edits (0200)

D_INVTYPE

Edit Number 3
Edit Title MCC and TCC Combination for Quasi Cash
Name D_INVTYPE
Billing Code 2DC0100
Region(s) Global
Description This edit monitors the Merchant Type Code (also called Merchant Category Code
[MCC]) and the Transaction Category Code in Quasi Cash transactions to ensure
that they are a valid combination.
Edit Criteria A transaction is considered noncompliant if DE 18 (Merchant Type) is 6051 (Quasi
Cash) and DE 48 (Additional Data), position 1 (Transaction Category Code [TCC]) is
not U (Unique).
Baseline/ Baseline: 20,000 financial transactions
Threshold
Threshold: Customers with more than 1,000,000 transactions are subject to a
threshold of 98%.
Customers with 1,000,000 or fewer transactions are subject to a threshold of
97%.

Reference Single Message System Specifications, Quick Reference Booklet

D_DE42

Edit Number 4
Edit Title Debit DE 42
Name D_DE42
Billing Code 2DC0100
Region(s) Global
Description This edit monitors the values in DE 42 (Card Acceptor Identification Code) to
ensure that they are present and valid.
Edit Criteria A transaction is considered noncompliant if any of the following subedits apply:
a. DE 42 is the same value as DE 43 (Card Acceptor Name/Location) , subfield 1
(ATM Owner Name and/or Location, or POS Merchant Name [or Payment
Facilitator and Sub-Merchant Information, if applicable])
b. DE 42 contains spaces
c. DE 42 contains a Chain Merchant Name/Franchise Merchant Name

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 76
 Data Integrity Edits List
Acquirer Debit Single Message System Edits (0200)

Edit Number 4
Baseline/ Baseline: 20,000 financial transactions
Threshold
Threshold: Customers with more than 1,000,000 transactions are subject to a
threshold of 98%.
Customers with 1,000,000 or fewer transactions are subject to a threshold of
97%.

Reference Single Message System Specifications

D_DE43

Edit Number 5
Edit Title DE 43 - Card Acceptor Name and Location (0200)
Name D_DE43
Billing Code 2DC0100
Region(s) Global
Description This edit monitors DE 43 (Card Acceptor Name/Location ) to ensure that all
necessary values are present and properly formatted.
Edit Criteria At least one of the following edit criteria applies:
a. DE 43, subfield 1 (ATM Owner Name and/or Location, or POS Merchant Name)
is all numeric
b. DE 43, subfield 1 contains a chain merchant name that is not in the correct
format, or DE 48 (Additional Data), subelement 32 (Mastercard Assigned ID) is not
present
Note: Customers have the option to change the DBA name or request that a
Mastercard Assigned ID be established

c. DE 61 (POS Data) , subfield 13 (POS Country Code) is 840 (USA) and DE 43,
subfield 5 (Card Acceptor State [U.S.], Province Code [Canada and Canadian
territories]) is not a valid U.S. state code
d. DE 61, subfield 13 is 124 (CAN) and DE 43, subfield 5 is not a valid Canadian
province code
e. DE 61, subfield 13 is not 840 (USA) or 124 (CAN) and DE 43, subfield 5 is not a
valid three-character alphabetic country code
f. DE 61, subfield 13 is blank, or is 000

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 77
 Data Integrity Edits List
Acquirer Debit Single Message System Edits (0200)

Edit Number 5
Baseline/ Baseline: 20,000 financial transactions
Threshold
Threshold: Customers with more than 1,000,000 transactions are subject to a
threshold of 98%.
Customers with 1,000,000 or fewer transactions are subject to a threshold of
97%.

Reference Single Message System Specifications

D_TERMPOS

Edit Number 7
Edit Title Terminal POS Processing Fields (0200)
Name D_TERMPOS
Billing Code 2DC0100
Region(s) Global
Description This edits monitors the values in DE 61 (POS Data) to ensure that the terminal
processing fields are valid and correspond appropriately to the data in DE 22 ( POS
Entry Mode).
Edit Criteria One of the following edit criteria applies:
a. DE 61, subfield 1 (POS Terminal Attendance) is 2 ( No terminal used (voice/ARU
authorization]; server) and DE 61, subfield 3 (POS Terminal Location) is not 3 ( No
terminal used [voice/ARU authorization]; server)
b. DE 61, subfield 3 is 3 and DE 61, subfield 1 is not 2
c. DE 61, subfield 1 is 1 ( Unattended Terminal [CAT, home PC, mobile phone,
PDA]) and DE 61, subfield 10 (Cardholder-Activated Terminal [CAT] Level) is 0
Exclusions: Subedit c excludes recurring payment transactions and transactions
with the following MCCs: 6011 (ATM), 4111 (Transportation – Suburban and Local
Commuter Passenger) , 4131 (Bus Lines), and 4784 (Bridge and Road Fees, Tolls)
d. DE 61, subfield 11 (POS Card Data Terminal Input Capability) is 1 ( No terminal
used [voice/ARU authorization]; server) and all of the following conditions are true:
• DE 61, subfield 1 is not 2
• DE 61, subfield 3 is not 3
• DE 22, subfield 1 ( POS Terminal PAN Entry Mode) is not 00 ( PAN entry mode
unknown) or 01 ( PAN manual entry)

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 78
 Data Integrity Edits List
Acquirer Debit Single Message System Edits (0200)

Edit Number 7
e. DE 22, subfield 1 is 00 and DE 61, subfield 11 is any of the following:
• 2 ( Terminal supports magnetic stripe input only)
• 5 ( Terminal supports EMV contact chip input and magnetic stripe input)
• 7 ( Terminal supports magnetic stripe input and key entry input)
• 8 ( Terminal supports EMV contact chip input, magnetic stripe input and key
entry input)

f. DE 61, subfield 11 is 6 ( Terminal supports key entry input only) and DE 22,
subfield 1 is either of the following:
• 02 ( PAN auto-entry via magnetic stripe)
• 90 ( PAN auto-entry via magnetic stripe —the full track data has been read
from the data encoded on the card and transmitted within the authorization
request in DE 35 (Track 2 Data) or DE 45 (Track 1 Data) without alteration or
truncation)
• 91 (PAN auto-entry via contactless magnetic stripe—the full track data has been
transmitted by the acquirer within the authorization request in DE 35 (Track 2
Data) or DE 45 (Track 1 Data) and forwarded to the issuer without alteration or
truncation)

g. DE 61, subfield 5 is 0 and DE 61, subfield 4 (POS Cardholder Presence) is any of

the following:
• 1 ( Cardholder not present, unspecified)
• 2 ( Cardholder not present [mail/facsimile order])
• 3 ( Cardholder not present [phone or ARU])
• 4 ( Standing order/recurring transactions)
• 5 ( Cardholder not present [Electronic order])

h. All of the following are true:

• DE 61, subfield 4 is 0 (Cardholder present)
• DE 61, subfield 5 is 1 (Card not present)
• DE 61, subfield 10 (Cardholder-Activated Terminal Level) is not 7 (Authorized
Level 7 CAT: Transponder transaction)

i. DE 61, subfield 5 is 1 and DE 22, subfield 1 is any of the following:

• 02
• 05 (PAN auto-entry via chip)
• 80 (Chip card at chip-capable terminal was unable to process transaction using
data on the chip; therefore, the terminal defaulted to the magnetic stripe-read
PAN)
• 90
• 91

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 79
 Data Integrity Edits List
Acquirer Debit Single Message System Edits (0200)

Edit Number 7
Baseline/ Baseline: 20,000 financial transactions
Threshold
Threshold: Customers with more than 1,000,000 transactions are subject to a
threshold of 98%.
Customers with 1,000,000 or fewer transactions are subject to a threshold of
97%.

Reference Single Message System Specifications

D_POSCND

Edit Number 8
Edit Title POS Condition Codes (0200)
Name D_POSCND
Billing Code 2DC0100
Region(s) Global
Description This edit monitors DE 61 (POS Data) to ensure that all values submitted in subfields
1-8, 10 and 11 are valid.
Edit Criteria A transaction is considered noncompliant if the values in any of the following
subfields in DE 61 are invalid:
• Subfield 1 (POS Terminal Attendance)
• Subfield 2 (Reserved)
• Subfield 3 (POS Terminal Location)
• Subfield 4 (POS Cardholder Presence)
• Subfield 5 (POS Card Presence)
• Subfield 6 (POS Card Capture Capabilities)
• Subfield 7 (POS Transaction Status)
• Subfield 8 (POS Transaction Security)
• Subfield 9 (Reserved)
• Subfield 10 (Cardholder-Activated Terminal Level)
• Subfield 11 (POS Card Data Terminal Input Capability)

Baseline/ Baseline: 20,000 financial transactions

Threshold
Threshold: Customers with more than 1,000,000 transactions are subject to a
threshold of 98%.
Customers with 1,000,000 or fewer transactions are subject to a threshold of
97%.

Reference Single Message System Specifications

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 80
 Data Integrity Edits List
Acquirer Debit Single Message System Edits (0200)

D_PF_ID

Edit Number 9
Edit Title Payment Facilitator ID (0200)
Name D_PF_ID
Billing Code 2DC0100
Region(s) Global
Description This edit monitors the presence of the Payment Facilitator ID in DE 48 (Additional
Data), subelement 37 (Additional Merchant Data) to ensure it is valid and
corresponds appropriately with other values in the financial transaction.
Edit Criteria A transaction is considered noncompliant if any of the following subedits apply:
a. The Payment Facilitator ID is present in DE 48, subelement 37, subfield 1
(Payment Facilitator ID) and the sub-merchant is not present in DE 48, subelement
37, subfield 3 (Sub-Merchant ID)
b. The Payment Facilitator ID is present DE 48, subelement 37, subfield 1 and DE
43 (Card Acceptor Name/Location), subfield 1 (Payment Facilitator & Sub-Merchant
Information) does not include an '*' separating Payment Facilitator name and sub-
merchant name
c. The value in DE 48 subelement 37, subfield 1 is not a valid Payment Facilitator ID
Baseline/ Baseline: 20,000 financial transactions
Threshold
Threshold: Customers with more than 1,000,000 transactions are subject to a
threshold of 98%.
Customers with 1,000,000 or fewer transactions are subject to a threshold of
97%.

Reference IPM Clearing Formats, Single Message System Specifications

D_Pure_Magstripe ATM

Edit Number 10
Edit Title Pure Magnetic Stripe – ATM (0200)
Name D_Pure_Magstripe ATM
Billing Code 2DC0100
Region(s) Global
Description This edit monitors ATM transactions performed on magnetic stripe only cards that
are submitted as technical fallback.

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 81
 Data Integrity Edits List
Acquirer Debit Single Message System Edits (0200)

Edit Number 10
Edit Criteria A transaction is considered noncompliant if all of the following are true:
• DE 18 (Merchant Type Code) is 6011 (ATM)
• DE 22 (POS Entry Mode), subfield 1 (POS Terminal PAN Entry Mode )is 80
(Technical Fallback)
• DE 35 (Track 2 Data), subfield 5 (Extended Service Code) begins with 1 or 5
(Magstripe Only cards)

Baseline/ Baseline: N/A

Threshold
Europe Threshold: 20 failures
Non-Europe Threshold: 1,000 failures

Reference M/Chip Requirements for Contact and Contactless, Single Message System
Specifications

D_Pure Magstripe POS

Edit Number 11
Edit Title Pure Magnetic Stripe – POS (0200)
Name D_Pure Magstripe POS
Billing Code 2DC0100
Regions Global
Description This edit monitors POS transactions performed on magnetic stripe only cards that
are submitted as technical fallback.
Edit Criteria A transaction is considered noncompliant if all of the following are true:
• DE 18 (Merchant Type Code) is not 6011 (ATM)
• DE 22 (POS Entry Mode), subfield 1 (POS Terminal PAN Entry Mode )is 80
(Technical Fallback)
• DE 35 (Track 2 Data), subfield 5 (Extended Service Code) begins with 1 or 5
(Magstripe Only cards)

Baseline/ Baseline: N/A

Threshold
Europe Threshold: 20 failures
Non-Europe Threshold: 1,000 failures

Reference M/Chip Requirements for Contact and Contactless, Single Message System
Specifications

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 82
 Data Integrity Edits List
Acquirer Debit Single Message System Edits (0200)

D_INC_MAGSTRIPE_0200

Edit Number 12
Edit Title Inconsistent Magnetic Stripe (0200)
Name D_INC_MAGSTRIPE_0200
Billing Code 2DC0100
Region(s)
Description This edit monitors transactions performed with chip cards on chip-capable
terminals that are submitted as magnetic stripe.
Edit Criteria A transaction is considered noncompliant if all of the following are true:
• DE 22 (POS Entry Mode), subfield 1 (POS Terminal PAN Entry Mode) is 02 (PAN
auto-entry via magnetic stripe - track data is not required) 90 (PAN auto-entry
via magnetic stripe – full track data)
• DE 35 (Track 2 Data) subfield 5 (Extended Service Code) begins with a value of
2 or 6 indicating a chip is present
• DE 61 (POS Data) subfield 11 (POS Card Data Terminal Input Capability
Indicator) is any of the following:
– 5 (Terminal supports EMV contact chip input and magnetic stripe input)
– 8 (Terminal supports EMV contact chip input, magnetic stripe input and key
entry input)
– 9 (Terminal supports EMV contact chip input only)
Note: Merchant Category Codes 4784 (Tolls) and 7523 (Automobile Parking Lots
and Garages) are excluded from this edit.

Baseline/ Baseline: N/A

Threshold
Europe Threshold: 100 failures
Non-Europe Threshold: 1,000 failures

Reference M/Chip requirements for Contact and Contactless, Single Message System
Specifications

D_MISREPORTED ATM FEE

Edit Number 13
Edit Title US Misreported ATM Fee
Name D_MISREPORTED ATM FEE
Billing Code 2DC0100
Region(s) USA Only

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 83
 Data Integrity Edits List
Acquirer Debit Single Message System Edits (0200)

Edit Number 13
Description The edit monitors ATM transactions that are reported as non-surcharged, but a
surcharge is applied.
Edit Criteria Transactions monitored under this edit are identified by the following criteria:
• DE 3 (Processing Code, subfield 1 (Cardholder Transaction Type Code) is 01
(Withdrawal)
• DE 18 (MCC Code) is 6011 (ATM)
• DE 49 (Transaction Currency Code) is 840
• DE 61(POS Data), subfield 13 (POS Country Code) is 840
A transaction is considered noncompliant when both of the following are true:
• DE 28 (Amount of Transaction Fee) is 0 or Null
• DE 4 (Transaction Amount) is not divisible by 5[NK1] [NK2]
Note: Customers are required to report the lowest denomination dispensed by
their ATMs in the ATM Location Administration Tool (LAT). If not otherwise
reported, Mastercard will assume that five-dollar bills are the smallest bill
dispensed.

Baseline/ Baseline: 1 ATM transaction

Threshold
Threshold: 1 failure

Reference Single Message System Specifications

Recurring CoF Monitorying (0200)

Edit Number 14
Edit Title COF Indicator for Recurring Payments (0200)
Name Recurring CoF Monitoring(0200)
Region(s) Global
Billing Code 2DC0100
Description This edit monitors the mandatory use of the COF indicator in recurring payment
transactions.
Edit Criteria A transaction is considered noncompliant if both of the following are true:
• DE 61 (POS Data), subfield 4 (POS Cardholder Presence) is 4 (Standing order/
recurring transaction)
• DE 22 (POS Entry Mode), subfield 1 (POS Terminal PAN Entry Mode) is not 10
COF

Baseline/ Baseline: 1,000 COF transactions

Threshold
Threshold: 97%

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 84
 Data Integrity Edits List
Acquirer Debit Single Message System Edits (0200)

Edit Number 14
Reference Single Message System Specifications

D_MISREPORTED ATM FEE NON US

Edit Number 15
Edit Title Non-US Misreported ATM Fee (0200)
Name D_MISREPORTED ATM FEE NON US
Billing Code 2DC0100
Region(s) Asia Pacific
Description The edit monitors ATM transactions that are reported as non-surcharged, but a
surcharge is applied.
Edit Criteria Transactions monitored under this edit are identified by the following criteria:
• DE 3 (Processing Code, subfield 1 (Cardholder Transaction Type Code) is 01
(Withdrawal)
• DE 18 (MCC Code) is 6011 (ATM)
• DE 49 (Transaction Currency Code) is an ISO code for domestic currency
• DE 61, subfield 13 (POS Country Code) is an ISO country code is in the Asia
Pacific region
A transaction is considered noncompliant when both of the following are true:
• DE 28 (Amount of Transaction Fee) is 0 or Null
• DE 4 (Transaction Amount) is not evenly divisible by the minimum
denomination reported by the acquirer through the Mastercard ATM Location
Administration Tool (LAT)

Baseline/ Baseline: 1,000 ATM transactions

Threshold
Threshold: 85%

Reference Single Message System Specifications

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 85
 Data Integrity Edits List
Acquirer Debit Single Message System Chip Edits (0200)

Acquirer Debit Single Message System Chip Edits (0200)

The edits in this program focus on chip data and EMV requirements monitored in the 0200/
Financial Transaction message. In the Data Integrity Online application, the program name
appears in its abbreviated form, Acq Auth Chip Dual Msg (0200).

NOTE: Before sending and/or receiving chip transactions, every customer is required to test
with Mastercard through a chip implementation project. Once the chip implementation
project is successfully completed, Customer Implementation Services activates the customer's
chip testing status flag to correspond to the profile that was implemented. Data Integrity
monitors specific fields to validate the status of the codes and ensure they remain accurately
aligned with the chip implementation plan.

Edit 1 – DC_Missing_DE35
Edit 2 – DC_Missing_DE37
Edit 3 – DC_Missing_DE55
Edit 4 – DC_Inv_form_DE55
Edit 5 – DC_Missing_EMVtags_DE55
Edit 6 – DC_Inv_Length_DE55
Edit 7 – DC_Inv_DE61_SF11
Edit 8 – Fallback Rt ATM 0200
Edit 9 – Fallback Rt POS 0200
Edit 10 – DC_INC_Magstripe_0200 (Retired from active monitoring)
Edit 11 – DC_INV_EMVTAGS_DE55

DC_Missing_DE35

Edit Number 1
Edit Title Missing DE35 (0200)
Name DC_Missing_DE35
Billing Code 2DC0100
Region(s) Global
Description This edit monitors single message chip transactions to ensure that the Track 2 data
is populated.

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 86
 Data Integrity Edits List
Acquirer Debit Single Message System Chip Edits (0200)

Edit Number 1
Edit Criteria Chip transactions monitored under this edit are identified by one of the following
values in DE 22 (Point of Service [POS] Entry Mode) , subfield 1 (POS Terminal PAN
Entry Mode):
• 05 (PAN auto-entry via chip)
• 07 (PAN auto-entry via contactless M/Chip)
A transaction is considered noncompliant if DE 35 (Track 2 Data) is missing.

Baseline/ Baseline: 20,000 chip transactions

Threshold
Threshold: Customers with more than 1,000,000 chip transactions are subject to a
threshold of 98%.
Customers with 1,000,000 or fewer chip transactions are subject to a threshold of
97%.
Effective 1 November 2019, the threshold will change to 99.85% for all customers
that meet the baseline of 20,000 chip transactions.

Reference Single Message System Specifications

DC_Missing_DE37

Edit Number 2
Edit Title Missing DE 37 (0200)
Name DC_Missing_DE37
Billing Code 2DC0100
Region(s) Global
Description This edit monitors single message transactions to ensure that the retrieval reference
number is populated where required.
Edit Criteria Transactions monitored under this edit are identified by one of the following values
in DE 22 (POS Entry Mode), subfield 1 (POS Terminal PAN Entry Mode):[NK1]
• 05 (PAN auto-entry via chip)
• 07 (PAN auto-entry via contactless M/Chip)
• 80 (Chip card at chip-capable terminal was unable to process transaction using
data on the chip; therefore, the terminal defaulted to the magnetic stripe-read
PAN)
• 91 (PAN auto-entry via contactless magnetic stripe)
A transaction is considered noncompliant if DE 37 (Retrieval Reference Number) is
missing.

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 87
 Data Integrity Edits List
Acquirer Debit Single Message System Chip Edits (0200)

Edit Number 2
Baseline/ Baseline: 20,000 chip transactions
Threshold
Threshold: Customers with more than 1,000,000 chip transactions are subject to a
threshold of 98%.
Customers with 1,000,000 or fewer chip transactions are subject to a threshold of
97%.
Effective 1 November 2019, the threshold will change to 99.85% for all customers
that meet the baseline of 20,000 chip transactions.

Reference Single Message System Specifications

DC_Missing_DE55

Edit Number 3
Edit Title Missing DE 55 (0200)
Name DC_Missing_DE55
Billing Code 2DC0100
Region(s) Global
Description This edit monitors single message chip transactions to ensure that the Integrated
Circuit Card (ICC) System-Related Data is populated.
Edit Criteria Chip transactions monitored under this edit are identified by one of the following
values in DE 22 (POS Entry Mode) , subfield 1 (POS Terminal PAN Entry Mode):
• 05 (PAN auto-entry via chip)
• 07 (PAN auto-entry via contactless M/Chip)
A transaction is considered noncompliant if DE 55 (ICC System-Related Data) is
missing.

Baseline/ Baseline: 20,000 chip transactions

Threshold
Threshold: Customers with more than 1,000,000 chip transactions are subject to a
threshold of 98%.
Customers with 1,000,000 or fewer chip transactions are subject to a threshold of
97%.
Effective 1 November 2019, the threshold will change to 99.85% for all customers
that meet the baseline of 20,000 chip transactions.

Reference Single Message System Specifications

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 88
 Data Integrity Edits List
Acquirer Debit Single Message System Chip Edits (0200)

DC_Inv_form_DE55

Edit Number 4
Edit Title DE 55 Invalid Format (0200)
Name DC_Inv_form_DE55
Billing Code 2DC0100
Region(s) Global
Description This edit monitors single message chip transactions to validate correct formatting
of the tag, length, value (TLV) in DE 55 (Integrated Circuit Card [ICC] System
Related Data).
Edit Criteria Chip transactions monitored under this edit are identified by one of the following
values in DE 22 (POS Entry Mode) , subfield 1 (POS Terminal PAN Entry Mode):
• 05 (PAN auto-entry via chip)
• 07 (PAN auto-entry via contactless M/Chip)
A transaction is considered noncompliant if the TLV is not formatted in accordance
with specifications outlined in M/Chip Requirements for Contact and
Contactless.

Baseline/ Baseline: 20,000 chip transactions

Threshold
Threshold: Customers with more than 1,000,000 chip transactions are subject to a
threshold of 98%.
Customers with 1,000,000 or fewer chip transactions are subject to a threshold of
97%.
Effective 1 November 2019, the threshold will change to 99.85% for all customers
that meet the baseline of 20,000 chip transactions.

Reference M/Chip Requirements for Contact and Contactless, Single Message System
Specifications

DC_Missing_EMVtags_DE55

Edit Number 5
Edit Title Missing EMV Tags (0200)
Name DC_Missing_EMVtags_DE55
Billing Code 2DC0100
Region(s) Global
Description This edit monitors single message chip transactions to ensure that all the required
EMV tags are present.

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 89
 Data Integrity Edits List
Acquirer Debit Single Message System Chip Edits (0200)

Edit Number 5
Edit Criteria Chip transactions monitored under this edit are identified by one of the following
values in DE 22 (POS Entry Mode) , subfield 1 (POS Terminal PAN Entry Mode):
• 05 (PAN auto-entry via chip)
• 07 (PAN auto-entry via contactless M/Chip)
A transaction is considered noncompliant if DE55 (Integrated Circuit Card [ICC]
System Related Data) is missing one or more required EMV tags.

Baseline/ Baseline: 20,000 chip transactions

Threshold
Threshold: Customers with more than 1,000,000 chip transactions are subject to a
threshold of 98%.
Customers with 1,000,000 or fewer chip transactions are subject to a threshold of
97%.
Effective 1 November 2019, the threshold will change to 99.85% for all customers
that meet the baseline of 20,000 chip transactions.

Reference M/Chip Requirements for Contact and Contactless, Single Message System
Specifications

DC_Inv_Length_DE55

Edit Number 6
Edit Title Invalid Length of EMV Tag (0200)
Name DC_Inv_Length_DE55
Billing Code 2DC0100
Region(s) Global
Description This edit monitors single message chip transactions to ensure all EMV tags are the
correct length.
Edit Criteria A transaction is considered noncompliant if DE 55 (Integrated Circuit Card [ICC]
System Related Data) contains one or more EMV tags with an invalid length as
specified in M/Chip Requirements for Contact and Contactless.
Baseline/ Baseline: 20,000 chip transactions
Threshold
Threshold: Customers with more than 1,000,000 chip transactions are subject to a
threshold of 98%.
Customers with 1,000,000 or fewer chip transactions are subject to a threshold of
97%.
Effective 1 November 2019, the threshold will change to 99.85% for all customers
that meet the baseline of 20,000 chip transactions.

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 90
 Data Integrity Edits List
Acquirer Debit Single Message System Chip Edits (0200)

Edit Number 6
Reference M/Chip Requirements for Contact and Contactless, Single Message System
Specifications

DC_Inv_DE61_SF11

Edit Number 7
Edit Title Invalid Terminal Input Capability (0200)
Name DC_Inv_DE61_SF11
Billing Code 2DC0100
Description This edit monitors terminal input capability to ensure that it corresponds
appropriately to the (POS) POS entry mode for single message chip transactions.
Edit Criteria A transaction is considered noncompliant if any of the following subedits apply:
a. DE 22 (POS Entry Mode), subfield 1 (POS Terminal PAN Entry Mode) is 05 (PAN
auto-entry via chip), and DE 61 (POS Data) , subfield 11 (POS Card Data Terminal
Input Capability Indicator) is not any of the following:
• 3 (Contactless EMV/Chip [Proximity Chip])
• 4 (Contactless Mag Stripe [Proximity Chip])
• 5 (Terminal supports EMV contact chip input and magnetic stripe input)
• 8 (Terminal supports EMV contact chip input, magnetic stripe input and key
entry input)
• 9 (Terminal supports EMV contact chip input only)

b. DE 22, subfield 1 is 07 ( PAN auto-entry via contactless M/Chip) and DE 61,

subfield 11 is not 3
c. DE 22, subfield 1 is 91 ( PAN auto-entry via contactless magnetic stripe) and DE
61, subfield 11 is not 3 or 4
Baseline/ Baseline: 20,000 chip transactions
Threshold
Threshold: Customers with more than 1,000,000 chip transactions are subject to a
threshold of 98%.
Customers with 1,000,000 or fewer chip transactions are subject to a threshold of
97%.
Effective 1 November 2019 the threshold will change to 99.85% for all customers
that meet the baseline of 20,000 chip transactions.

Reference M/Chip Requirements for Contact and Contactless, Single Message System
Specifications

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 91
 Data Integrity Edits List
Acquirer Debit Single Message System Chip Edits (0200)

Fallback Rt ATM 0200

Edit Number 8
Edit Title Technical Fallback Rate – ATM Transactions (0200)
Name Fallback Rt ATM 0200
Billing Code 2DC0100
Region(s) Global
Description This edit monitors ATM transactions performed with chip cards on chip-capable
terminals that are sent as Technical Fallback to magnetic stripe.
Edit Criteria A transaction is considered noncompliant if DE 18 (Merchant Type) is 6011 (ATM)
and DE 22 (POS Entry Mode), subfield 1 (POS Terminal PAN Entry Mode) is 80.
Baseline/ Baseline: 1,000 failures
Threshold
Threshold: Non-US acquirers – 99%
US Acquirers - Minimum compliance rating increases, refer to the dates and
thresholds below:
• 1 OCT 2018 – 96%
• 1 APR 2019 – 97%
• 1 OCT 2019 – 98%
• 1 APRL 2020 – 99%

Reference M/Chip Requirements for Contact and Contactless, Single Message System
Specifications

Fallback Rt POS 0200

Edit Number 9
Edit Title Technical Fallback Rate – POS Transactions (0200)
Name Fallback Rt POS 0200
Region(s) Global
Billing Code 2DC0100
Description This edit monitors POS transactions performed with chip cards on chip-capable
terminals that are sent as Technical Fallback to magnetic stripe.
Edit Criteria A transaction is considered noncompliant if DE 18 (Merchant Type) is not 6011
(ATM) and DE 22 (POS Entry Mode), subfield 1 (POS Terminal PAN Entry Mode) is
80.
Exclusions: MCCs 4784 (Bridge and Road Fees, Tolls) and 7523 (Automobile
Parking Lots and Garages) are not monitored under this edit.

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 92
 Data Integrity Edits List
Acquirer Debit Single Message System Chip Edits (0200)

Edit Number 9
Baseline/ Baseline: 1,000 failures
Threshold
Threshold: Non-US acquirers – 99%
US Acquirers - Minimum compliance rating increases, refer to the dates and
thresholds below:
• 1 OCT 2018 – 96%
• 1 APR 2019 – 97%
• 1 OCT 2019 – 98%
• 1 APRL 2020 – 99%

Reference M/Chip Requirements for Contact and Contactless, Single Message System
Specifications

DC_INV_EMVTAGS_DE55

Edit Number 11
Edit Title Invalid EMV Tags (0200)
Name DC_INV_EMVTAGS_DE55
Billing Code 2DC0100
Description This edit monitors single message chip transactions to determine if any EMV tag
data is present in DE 55 (Integrated Circuit Card [ICC] System-Related Data) in
invalid.
Edit Criteria A transaction is considered noncompliant if any of the following subedits apply:
a. Tag 9F27 (Cryptogram Information Data) is not any of the following:
• 00
• 40
• 80

b. Tag 5F2A (Transaction Currency Code) does not contain a valid currency code
c. Tag 9F1A (Terminal Country Code) does not contain a valid country code
d. Tag 9A (Transaction Date) is not a valid date or is not submitted in the correct
format (YYMMDD)
e. Any bit designated as Reserved for Future Use (RFU) in Tag 95 (Terminal
Verification Results [TVR]) is not set correctly
h. 9F34 (Cardholder Verification Method Results) is missing or is not a valid value
Note: Letters (f) Tag 82 Application Interchange Profile and (g) Tag 84 Dedicated
File were removed from this edit.

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 93
 Data Integrity Edits List
Issuer Authorization Dual Message System Edits (0110)

Edit Number 11
Baseline/ Baseline: 20,000 chip transactions
Threshold Threshold: Customers with more than 1,000,000 transactions are subject to a
threshold of 98%.
Customers with 1,000,000 or fewer transactions are subject to a threshold of
97%.

Effective 1 November 2019, the threshold will change to 99.85% for all customers
that meet the baseline of 20,000 chip transactions.
Reference M/Chip Requirements for Contact and Contactless, Single Message System
Specifications

Issuer Authorization Dual Message System Edits (0110)

The edits in this program focus on the data and product requirements monitored in the 0110/
Authorization Response message. In the Data Integrity Online application, the program name
appears in its abbreviated form, Iss Auth Dual Msg (0110).
Edit 1 – MONEYSEND_AR_0110
Edit 2 – ASI_APP_RT
Edit 3 – ASI_INV_RC
Edit 4 – EMV_ARPC_0110
Edit 5 – CP_AFFL_APP_RT (LAC REGION ONLY)
Edit 6 – CP_GOLD_APP_RT (LAC REGION ONLY)
Edit 7 – CP_STND_APP_RT (LAC REGION ONLY)
Edit 8 – CNP_AFFL_APP_RT (LAC REGION ONLY)
Edit 9 – CNP_Gold_APP_RT (LAC REGION ONLY)
Edit 10 – CNP_STND_APP_RT (LAC REGION ONLY)
Edit 11 – ISS_ATTEMPTS_NOSOLUTION_DECLIN
Edit 12 – ISSUER_ATTEMPTS_AAV_DECLINE (Retired from active monitoring)
Edit 13 – NO_CVM_HIGH_DECLINE_PT
Edit 14 – NO_CVM_HIGH_DECLINE_VEND
Edit 15 – ISS_OFFLINE_CAM_0110
Edit 16 – AAV_Validation_Mandate (Retired from active monitoring)
Edit 17 – FULL_AUTH_APPR_RT

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 94
 Data Integrity Edits List
Issuer Authorization Dual Message System Edits (0110)

Edit 18 – Fallback Decline Rate 0110

Edit 19 – Issuer COF Monitoring (0100)

MONEYSEND_AR_0110

Edit Number 1
Edit Title MoneySend Approval Rate (0110)
Name MONEYSEND_AR_0110
Billing Code 2DC0100
Region(s) Global
Description This edit monitors the approval rate of dual message MoneySend transactions.
Edit Criteria Transactions monitored under this edit are identified by the following criteria:
• DE 3 (Processing Code), subfield 1 (Cardholder Transaction Type Code) is 28
(Payment Transaction)
• DE 18 (Merchant Type [MCC]) is 6536 (MoneySend Intracountry) or 6537
(MoneySend Intercountry)
A customer is considered noncompliant if the monthly approval rate for all
qualified transactions is below 75%. Approvals are identified by the following
values in DE 39 (Response Code):
• 00 (Approved or completed successfully)
• 08 (Honor with ID)
• 85 (Not Declined)
• 87 (Purchase Amount Only, No Cash Back Allowed)

Baseline/ Baseline: 50 declined MoneySend transactions

Threshold
Threshold: 75%

Reference Customer Interface Specification, MoneySend Program Guide

ASI_APP_RT

Edit Number 2
Edit Title Account Status Inquiry Approval Rate
Name ASI_APP_RT
Billing Code 2DC0100
Region(s) Global
Description This edit monitors the approval rate of Account Status Inquiry (ASI) transactions.

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 95
 Data Integrity Edits List
Issuer Authorization Dual Message System Edits (0110)

Edit Number 2
Edit Criteria Transactions monitored under this edit are identified by the following criteria:
• DE 61 (POS Data), subfield 7 (POS Transaction Status) is 8 (Account Status
Inquiry Service )
• DE 3 (Transaction Type), subfield 1 (Cardholder Transaction Type Code) is 00
(Purchase)
A customer is considered noncompliant if the monthly approval rate for all
qualified transactions is below 1%.
Approvals are identified by a value of 00 (Approved or completed successfully) or
85 (Not declined) in DE 39 (Response Code).
Exclusions: ASI payment transactions, identified by a value of 28 in DE 3, subfield
1, are not monitored under this edit.

Baseline/ Baseline: 50 ASI transactions

Threshold
Threshold: 1%

Reference Customer Interface Specification, Authorization Manual

ASI_INV_RC

Edit Number 3
Edit Title ASI Invalid Response Code
Name ASI_INV_RC
Billing Code 2DC0100
Region(s) Global
Description This edit monitors declined Account Status Inquiry (ASI) transactions to ensure that
issuers are using valid reason codes when declining.

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 96
 Data Integrity Edits List
Issuer Authorization Dual Message System Edits (0110)

Edit Number 3
Edit Criteria Transactions monitored under this edit are identified by the following criteria:
• DE 61 (Point of Service [POS] Data), subfield 7 (POS Transaction Status) is 8
(Account Status Inquiry Service )
• DE 3 (Transaction Type), subfield 1 (Cardholder Transaction Type Code) is 00
(Purchase)
A transaction is considered noncompliant if DE 39 (Response Code) is any of the
following values:
• 12 (Invalid transaction)
• 13 (Invalid amount)
• 30 (Format error)
• 51 (Insufficient funds/over credit limit)
• 57 (Transaction not permitted to issuer/cardholder)
• 58 (Transaction not permitted to acquire/terminal)
Exclusions: ASI payment transactions, identified by a value of 28 in DE 3, subfield
1, are not monitored under this edit.

Baseline/ Baseline: 50 ASI transactions

Threshold
Threshold: 50 failures

Reference Authorization Manual, Customer Interface Specification

EMV_ARPC_0110

Edit Number 4
Edit Title ARPC Presence (0110)
Name EMV_ARPC_0110
Billing Code 2DC0100
Region(s) Global
Description The edit monitors DE 55 (Integrated Circuit Card [ICC] System-Related Data) to
ensure the Authorization Response Cryptogram (ARPC) value is present in
approved chip transactions.

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 97
 Data Integrity Edits List
Issuer Authorization Dual Message System Edits (0110)

Edit Number 4
Edit Criteria Transactions are monitored under this edit when all of the following are true:
• DE 22 (POS Entry Mode), subfield 1 (POS Terminal PAN Entry Mode) is 05 (PAN
auto-entry via chip)
• DE 39 (Response code) is one of the following:
– 00 (Approved or completed successfully)
– 08 (Honor with ID)
– 10 (Partial Approval)
– 87 (Purchase Amount Only, No Cash Back Allowed)
• DE 55 is present in the originating 0100/Authorization Request with all
mandatory tags
A transaction is considered noncompliant if the ARPC value is missing from DE 55
(Integrated Circuit Card [ICC] System-Related Data), subelement 91 (Issuer
Authentication Data) .
Exclusions: Transactions originated from Mastercard Stand-In are not monitored
under this edit.
Note: This edit is not eligible for extensions.

Baseline/ Baseline: 500 chip transactions

Threshold
Threshold: 98%

Reference Authorization Manual, Customer Interface Specification, M/Chip

Requirements for Contact and Contactless

CP_AFFL_APP_RT (LAC REGION ONLY)

Edit Number 5
Edit Title Card Present Affluent Approval Rate
Name CP_AFFL_APP_RT (LAC REGION ONLY)
Billing Code 2DC0100
Region(s) LAC
Description This edit monitors the approval rate of card present, cross-border transactions on
cards designated as affluent brand products.

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 98
 Data Integrity Edits List
Issuer Authorization Dual Message System Edits (0110)

Edit Number 5
Edit Criteria Transactions monitored under this edit are identified by the following criteria:
• PAN brand product name contains “Black”, “Platinum”, “World”, or
“Titanium”
– Transaction is cross-border
– DE 22, subfield 1 is not any of the following:
– 00 (PAN entry mode unknown)
– 01 (PAN manual entry)
– 09 ( PAN/Token entry via electronic commerce containing DSRP
cryptogram in DE 55 (Integrated Circuit Card System-Related Data)
– 10 COF
– 81 ( PAN/Token entry via electronic commerce with optional SecureCode
-AAV or DSRP cryptogram in UCAF)
A customer is considered noncompliant if the monthly approval rate for all
qualified transactions is below 92%. Approvals are identified by the following
values in DE 39 (Response Code):
• 00 (Approved or completed successfully)
• 08 (Honor with ID)
• 10 (Partial Approval)
• 85 (Not Declined)
• 87 (Purchase Amount Only, No Cash Back Allowed)
Exclusions: Transactions declined by Stand-in, X-Code, or Safety Net are not
counted against issuer’s approval rate. Issuers in Venezuela are not monitored
under this edit.

Baseline/ Baseline: 1,000 transactions

Threshold
Threshold: 92%

Reference Customer Interface Specification

CP_GOLD_APP_RT (LAC REGION ONLY)

Edit Number 6
Edit Title Card Present Gold Approval Rate
Name CP_GOLD_APP_RT (LAC REGION ONLY)
Billing Code 2DC0100
Region(s) LAC
Description This edit monitors the approval rate of card present, cross-border transactions by
Gold cardholders.

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 99
 Data Integrity Edits List
Issuer Authorization Dual Message System Edits (0110)

Edit Number 6
Edit Criteria Transactions monitored under this edit are identified by the following criteria:
• PAN brand product name contains “Gold”
– Transaction is cross-border
– DE 22, subfield 1 is not any of the following:
– 00 (PAN entry mode unknown)
– 01 (PAN manual entry)
– 09 ( PAN/Token entry via electronic commerce containing DSRP
cryptogram in DE 55 (Integrated Circuit Card System-Related Data)
– 10 COF
– 81 ( PAN/Token entry via electronic commerce with optional SecureCode
-AAV or DSRP cryptogram in UCAF)
A customer is considered noncompliant if the monthly approval rate for all
qualified transactions is below 88%. Approvals are identified by the following
values in DE 39 (Response Code):
• 00 (Approved or completed successfully)
• 08 (Honor with ID)
• 10 (Partial Approval)
• 85 (Not Declined)
• 87 (Purchase Amount Only, No Cash Back Allowed)
Exclusions: Transactions declined by Stand-in, X-Code, or Safety Net are not
counted against issuer’s approval rate. Issuers in Venezuela are not monitored
under this edit.

Baseline/ Baseline: 1,000 transactions

Threshold
Threshold: 88%

Reference Customer Interface Specification

CP_STND_APP_RT (LAC REGION ONLY)

Edit Number 7
Edit Title Card Present Standard Approval Rate
Name CP_STND_APP_RT (LAC REGION ONLY)
Billing Code 2DC0100
Region(s) LAC
Description This edit monitors the approval rate of card present, cross-border transactions by
Standard cardholders.

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 100
 Data Integrity Edits List
Issuer Authorization Dual Message System Edits (0110)

Edit Number 7
Edit Criteria Transactions monitored under this edit are identified by the following criteria:
• PAN brand product name does not contain “Black”, “Platinum”, “World”,
“Titanium”, or “Gold”
– Transaction is cross-border
– DE 22, subfield 1 is not any of the following:
– 00 (PAN entry mode unknown)
– 01 (PAN manual entry)
– 09 ( PAN/Token entry via electronic commerce containing DSRP
cryptogram in DE 55 (Integrated Circuit Card System-Related Data)
– 10 COF
– 81 ( PAN/Token entry via electronic commerce with optional SecureCode
-AAV or DSRP cryptogram in UCAF)
A customer is considered noncompliant if the monthly approval rate for all
qualified transactions is below 84%. Approvals are identified by the following
values in DE 39 (Response Code):
• 00 (Approved or completed successfully)
• 08 (Honor with ID)
• 10 (Partial Approval)
• 85 (Not Declined)
• 87 (Purchase Amount Only, No Cash Back Allowed)
Exclusions: Transactions declined by Stand-in, X-Code, or Safety Net are not
counted against issuer’s approval rate. Issuers in Venezuela are not monitored
under this edit.

Baseline/ Baseline: 1,000 transactions

Threshold
Threshold: 84%

Reference Customer Interface Specification

CNP_AFFL_APP_RT (LAC REGION ONLY)

Edit Number 8
Edit Title Card Not Present (CNP) Affluent Approval Rate
Name CNP_AFFL_APP_RT (LAC REGION ONLY)
Billing Code 2DC0100
Region(s) LAC
Description This edit monitors the approval rate of card not present, cross-border transactions
on cards designated as affluent brand products.

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 101
 Data Integrity Edits List
Issuer Authorization Dual Message System Edits (0110)

Edit Number 8
Edit Criteria Transactions monitored under this edit are identified by the following criteria:
• PAN brand product name contains “Black”, “Platinum”, “World”, or
“Titanium”
• Transaction is cross-border
• DE 22, subfield 1 is any of the following:
– 00 (PAN entry mode unknown)
– 01 (PAN manual entry)
– 09 ( PAN/Token entry via electronic commerce containing DSRP cryptogram
in DE 55 (Integrated Circuit Card System-Related Data)
– 10 COF
– 81 ( PAN/Token entry via electronic commerce with optional SecureCode -
AAV or DSRP cryptogram in UCAF)
A customer is considered noncompliant if the monthly approval rate for all
qualified transactions is below 78%. Approvals are identified by the following
values in DE 39 (Response Code):
• 00 (Approved or completed successfully)
• 08 (Honor with ID)
• 10 (Partial Approval)
• 85 (Not Declined)
• 87 (Purchase Amount Only, No Cash Back Allowed)
Exclusions: Transactions declined by Stand-in, X-Code, or Safety Net are not
counted against issuer’s approval rate. Issuers in Venezuela are not monitored
under this edit.

Baseline/ Baseline: 1,000 transactions

Threshold
Threshold: 78%

Reference Customer Interface Specification

CNP_Gold_APP_RT (LAC REGION ONLY)

Edit Number 9
Edit Title Card Not Present Gold Approval Rate
Name CNP_Gold_APP_RT (LAC REGION ONLY)
Billing Code 2DC0100
Region(s) Latin America and the Caribbean
Description This edit monitors the approval rate of card not present, cross-border transactions
by Gold cardholders.

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 102
 Data Integrity Edits List
Issuer Authorization Dual Message System Edits (0110)

Edit Number 9
Edit Criteria Transactions monitored under this edit are identified by the following criteria:
• PAN brand product name contains “Gold”
– Transaction is cross-border
– DE 22, subfield 1 is any of the following:
– 00 (PAN entry mode unknown)
– 01 (PAN manual entry)
– 09 ( PAN/Token entry via electronic commerce containing DSRP
cryptogram in DE 55 (Integrated Circuit Card System-Related Data)
– 10 COF
– 81 ( PAN/Token entry via electronic commerce with optional SecureCode
-AAV or DSRP cryptogram in UCAF)
A customer is considered noncompliant if the monthly approval rate for all
qualified transactions is below 69%. Approvals are identified by the following
values in DE 39 (Response Code):
• 00 (Approved or completed successfully)
• 08 (Honor with ID)
• 10 (Partial Approval)
• 85 (Not Declined)
• 87 (Purchase Amount Only, No Cash Back Allowed)
Exclusions: Transactions declined by Stand-in, X-Code, or Safety Net are not
counted against issuer’s approval rate. Issuers in Venezuela are not monitored
under this edit.

Baseline/ Baseline: 1,000 transactions

Threshold
Threshold: 69%

Reference Customer Interface Specification

CNP_STND_APP_RT (LAC REGION ONLY)

Edit Number 10
Edit Title Card Not Present Standard Approval Rate
Name CNP_STND_APP_RT (LAC REGION ONLY)
Billing Code 2DC0100
Region(s) LAC
Description This edit monitors the approval rate of card not present, cross-border transactions
by Gold cardholders.

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 103
 Data Integrity Edits List
Issuer Authorization Dual Message System Edits (0110)

Edit Number 10
Edit Criteria Transactions monitored under this edit are identified by the following criteria:
• PAN brand product name does not contain “Black”, “Platinum”, “World”,
“Titanium”, or “Gold”
• Transaction is cross-border
• DE 22, subfield 1 is any of the following:
– 00 (PAN entry mode unknown)
– 01 (PAN manual entry)
– 09 ( PAN/Token entry via electronic commerce containing DSRP cryptogram
in DE 55 (Integrated Circuit Card System-Related Data)
– 10 COF
– 81 ( PAN/Token entry via electronic commerce with optional SecureCode -
AAV or DSRP cryptogram in UCAF)
A customer is considered noncompliant if the monthly approval rate for all
qualified transactions is below 69%. Approvals are identified by the following
values in DE 39 (Response Code):
• 00 (Approved or completed successfully)
• 08 (Honor with ID)
• 10 (Partial Approval)
• 85 (Not Declined)
• 87 (Purchase Amount Only, No Cash Back Allowed)
Exclusions: Transactions declined by Stand-in, X-Code, or Safety Net are not
counted against issuer’s approval rate. Issuers in Venezuela are not monitored
under this edit.

Baseline/ Baseline: 1,000 transactions

Threshold
Threshold: 67%

Reference Customer Interface Specification

ISS_ATTEMPTS_NOSOLUTION_DECLIN

Edit Number 11
Edit Title No Solution Decline
Name ISS_ATTEMPTS_NOSOLUTION_DECLIN
Billing Code 2DC0100
Region(s) Global
Description This edit monitors Merchant Only transactions to ensure that issuers are not
declining all transactions with a security level indicator (SLI) of 211 when issuers do
not offer an authentication solution to their cardholders.

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 104
 Data Integrity Edits List
Issuer Authorization Dual Message System Edits (0110)

Edit Number 11
Edit Criteria Customers are monitored under this edit when they do not have any approved
transactions in a given month where DE 48 (Additional Data - Private Use),
subelement 42 (Electronic Commerce Indicator, subfield 1 (Electronic Commerce
Security Level Indicator and UCAF Collection Indicator [SLI]) is 212 (Channel
encryption; cardholder certificate not used + UCAF data collection is supported by
the merchant).
Customers are considered noncompliant if the above condition is met and the
approval rate for transactions where DE 48, subelement 42, subfield 1 is 211
(Channel encryption; cardholder certificate not used + UCAF data collection is not
supported by the merchant) is less than 1%.
Approved transactions are identified by the following values in DE 39 (Response
Code):
• 00 (Approved or completed successfully)
• 08 (Honor with ID)
• 10 (Partial Approval)
• 87 (Purchase Amount Only, No Cash Back Allowed)

Baseline/ Baseline: 100 ecommerce transactions with an SLI of 211

Threshold
Threshold: 1%

Reference Customer Interface Specification

NO_CVM_HIGH_DECLINE_PT

Edit Number 13
Edit Title Decline Rate at Parking Lots and Tollways
Name NO_CVM_HIGH_DECLINE_PT
Billing Code 2DC0100
Region(s) Europe
Description This edit monitors the decline rate of Maestro transactions at parking lots and
tollways.

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 105
 Data Integrity Edits List
Issuer Authorization Dual Message System Edits (0110)

Edit Number 13
Edit Criteria Transactions monitored under this edit are identified by the following criteria:
• DE 4 (Amount, Transaction) is less than 50 euros
• DE 18 (Merchant Type) is 4784 (Tolls) or 7523 (Automobile Parking Lots and
Garages)
• DE 22 (POS Entry Mode), subfield 1 (POS Terminal PAN Entry Mode) is 05[NK1]
• DE 55 (Integrated Circuit Card [ICC] System-Related Data), subelement 95
(Terminal Verification Result [TVR]) shows that CVM failed
A customer is considered noncompliant if the monthly approval rate for all
qualified transactions is below 50%. Approvals are identified by the following
values in DE 39 (Response Code):
• 00 (Approved or completed successfully)
• 08 (Honor with ID)
• 10 (Partial Approval)
• 85 (Not Declined)
• 87 (Purchase Amount Only, No Cash Back Allowed)

Baseline/ Baseline: 10 declines

Threshold
Threshold: 50%

Reference Customer Interface Specification, M/Chip Requirements for Contact and

Contactless

NO_CVM_HIGH_DECLINE_VEND

Edit Number 14
Edit Title Decline Rate at Vending Machines
Name NO_CVM_HIGH_DECLINE_VEND
Billing Code 2DC0100
Region(s) Europe – Italy only
Description This edit monitors the decline rate of Maestro transactions at vending machines.

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 106
 Data Integrity Edits List
Issuer Authorization Dual Message System Edits (0110)

Edit Number 14
Edit Criteria Transactions monitored under this edit are identified by the following criteria:
• DE 4 (Amount, Transaction) is less than 50 euros
• DE 18 (Merchant Type) is 5499 (Miscellaneous Food Stores)
• DE 22 (POS Entry Mode), subfield 1 ({POS Terminal PAN Entry Mode) is 05[NK2]
• DE 43 (Card Acceptor Name/Location for All Transactions), subfield 5 (Card
Acceptor State or Country Code [or Sub-Merchant Information, if applicable]) is
ITA (Italy)
• DE 55 (Integrated Circuit Card [ICC] System-Related Data), subelement 95
( Terminal Verification Result [TVR]) shows that CVM failed
• DE 61 (POS Data), subfield 1 (POS Terminal Attendance) is 1 (Unattended
Terminal)
A customer is considered noncompliant if the monthly approval rate for all
qualified transactions is below 50%. Approvals are identified by the following
values in DE 39 (Response Code):
• 00 (Approved or completed successfully)
• 08 (Honor with ID)
• 10 (Partial Approval)
• 85 (Not Declined)
• 87 (Purchase Amount Only, No Cash Back Allowed)

Baseline/ Baseline: 10 declines

Threshold
Threshold: 50%

Reference Customer Interface Specification, M/Chip Requirements for Contact and

Contactless

ISS_OFFLINE_CAM_0110

Edit Number 15
Edit Title Issuer Offline CAM (0110)
Name ISS_OFFLINE_CAM_0110
Billing Code 2DC0100
Region(s) Global
Description This edit monitors the offline Cardholder Authentication Method (CAM) supported
on offline CAM-capable cards to ensure that customers migrate from Static Data
Authentication (SDA) and Dynamic Data Authentication (DDA) to Combined Data
Authentication (CDA).

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 107
 Data Integrity Edits List
Issuer Authorization Dual Message System Edits (0110)

Edit Number 15
Edit Criteria Transactions monitored under this edit are identified by the following criteria:
• Card is capable of offline authentication
• DE 22 (POS Entry Mode), subfield 1 (POS Terminal PAN Entry Mode) is 05 ( PAN
auto-entry via chip)
• DE 39 (Response code) is any of the following:
– 00 (Approved or completed successfully)
– 08 (Honor with ID)
– 10 (Partial Approval)
– 85 (Not Declined)
– 87 (Purchase Amount Only, No Cash Back Allowed)
An issuer is considered noncompliant if 0% of eligible transactions show that CDA
is supported in DE 55, subelement 82 (Application Interchange Profile [AIP]). CDA
is indicated in Byte 1, bit 1 of the AIP.

Baseline/ Baseline: 500 approved chip transactions on offline CAM-capable cards

Threshold
Threshold: Greater than 0%

Reference Customer Interface Specification, M/Chip Requirements for Contact and

Contactless

FULL_AUTH_APPR_RT

Edit Number 17
Edit Title Fully Authenticated Transaction Approval Rate
Name FULL_AUTH_APPR_RT
Billing Code 2DC0100
Region(s) Global - Select European countries excluded. (See excluded country list in Appendix
C.)
Description This edit monitors the approval rate of transactions that were authenticated
through 3-DS 1.0 or EMV 3-DS.

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 108
 Data Integrity Edits List
Issuer Authorization Dual Message System Edits (0110)

Edit Number 17
Edit Criteria Fully authenticated 3DS transactions are identified by the following criteria:
• The Security Level Indicator (SLI) in DE 48 (Additional Data – Private Use)
subelement 42 (Electronic Commerce Indicator) is 212 (UCAF data collection is
supported by the merchant, and UCAF data must be present)
• DE 48, subelement 43 (3DS 1.0 or EMV 3-DS) begins with a value of ‘k’ or ‘j’
A transaction is considered noncompliant if it is fully authenticated through 3DS
but was not approved with any of the following reason codes in DE 39 (Response
Code):
• 00 (Approved or completed successfully)
• 08 (Honor with ID)
• 10 (Partial Approval)
• 85 (Not Declined)

Baseline/ Baseline: 1,000 3-DS transactions

Threshold
Threshold: 85%

Reference Customer Interface Specifications

Fallback Decline Rate 0110

Edit Number 18
Edit Title Issuer Fallback Decline Rate (0110)
Name Fallback Decline Rate 0110
Billing Code 2DC0100
Region(s) Canada, Europe, Latin America and the Caribbean, Middle East and Africa
Description This edit monitors transactions submitted as technical fallback to ensure issuers are
declining them.
Edit Criteria A transaction is considered noncompliant when both of the following are true:
• DE 22 (POS Entry Mode), subfield 1 (POS Terminal PAN Entry Mode) is 80 (Chip
card at chip-capable terminal was unable to process transaction using data on
the chip)
• DE 39 (Response Code) is any of the following:
– 00 (Approved or completed successfully)
– 08 (Honor with ID)
– 10 (Partial Approval)
– 87 (Purchase Amount Only, No Cash Back Allowed)
Exclusions: Transactions taking place at merchant locations the USA and Asia
Pacific are not monitored under this edit.

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 109
 Data Integrity Edits List
Issuer Debit Single Message System Edits (0210)

Edit Number 18
Baseline/ Baseline: 50 fallback transactions
Threshold
Threshold: 99.85%

Reference Customer Interface Specification, M/Chip Requirements for Contact and

Contactless, Transaction Processing Rules

Issuer COF Monitoring (0100)

Edit Number 19
Edit Title Credential on File (COF) Approval Rate
Name Issuer COF Monitoring (0100)
Billing Code 2DC0100
Region(s) Global
Description This edit monitors the monthly approval rate of COF transactions.
Edit Criteria Transactions monitored under this edit are identified by a value of 10 COF in DE 22
(POS Entry Mode), subfield 1 (POS Terminal PAN Entry Mode).
Issuers are considered noncompliant when they have 50 or more COF transactions
in a given month, and 100% of those transactions are declined with a value of 05
(Do not honor) or 30 (Format Error) in DE 39 (Response Code).

Baseline/ Baseline: 50 COF transactions

Threshold
Threshold: Greater than 0%

Reference Customer Interface Specification

Issuer Debit Single Message System Edits (0210)

The edits in this program focus on the data and product requirements monitored in the 0210/
Financial Transaction message. In the Data Integrity Online application, the program name
appears in its abbreviated form, Iss Debit Single Msg (0210).
Edit 1 – MONEYSEND_AR_0210
Edit 2 – EMV_ARPC_0210
Edit 3 – ISS_OFFLINE_CAM_0210
Edit 4 – Fallback Decline Rate 0210

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 110
 Data Integrity Edits List
Issuer Debit Single Message System Edits (0210)

MONEYSEND_AR_0210

Edit Number 1
Edit Title MoneySend Approval Rate (0210)
Name MONEYSEND_AR_0210
Billing Code 2DC0100
Region(s) Global
Description This edit monitors the approval rate of single message MoneySend transactions.
Edit Criteria Transactions monitored under this edit are identified by the following criteria:
• DE 3 (Processing Code), subfield 1 (Cardholder Transaction Type Code) is 28
(Payment Transaction)
• DE 18 (Merchant Type [MCC]) is 6536 (MoneySend Intracountry) or 6537
(MoneySend Intercountry)
A customer is considered noncompliant if the monthly approval rate for all
qualified transactions is below 75%. Approvals are identified by the following
values in DE 39 (Response Code):
• 00 (Approved or completed successfully)
• 08 (Honor with ID)
• 85 (Not Declined)
• 87 (Purchase Amount Only, No Cash Back Allowed)

Baseline/ Baseline: 50 declined MoneySend transactions

Threshold
Threshold: 75%

Reference MoneySend Program Guide, Single Message Specifications

EMV_ARPC_0210

Edit Number 2
Edit Title ARPC Presence (0210)
Name EMV_ARPC_0210
Billing Code 2DC0100
Region(s) Global
Description The edit monitors DE 55 (Integrated Circuit Card [ICC] System-Related Data) to
ensure the Authorization Response Cryptogram (ARPC) value is present in
approved chip transactions.

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 111
 Data Integrity Edits List
Issuer Debit Single Message System Edits (0210)

Edit Number 2
Edit Criteria Transactions are monitored under this edit when all of the following are true:
• DE 22 (Point of Service [POS] Entry Mode), subfield 1 (POS Terminal PAN Entry
Mode) is 05 (PAN auto-entry via chip)
• DE 39 (Response code) is one of the following:
– 00 (Approved or completed successfully)
– 08 (Honor with ID)
– 10 (Partial Approval)
– 87 (Purchase Amount Only, No Cash Back Allowed)
• DE 55 is present in the originating 0100/Authorization Request with all
mandatory tags
A transaction is considered noncompliant if the ARPC value is missing from DE 55
(Integrated Circuit Card [ICC] System-Related Data), subelement 91 ( Issuer
Authentication Data) .
Exclusions: Transactions originated from Mastercard Stand-In are not monitored
under this edit.
Note: This edit is not eligible for extensions.

Baseline/ Baseline: 500 approved chip transactions

Threshold
Threshold: 98%

Reference M/Chip Requirements for Contact and Contactless, Single Message System
Specifications

ISS_OFFLINE_CAM_0210

Edit Number 3
Title Issuer Offline CAM (0210)
Name ISS_OFFLINE_CAM_0210
Billing Code 2DC0100
Region(s) Global
Description This edit monitors the offline Cardholder Authentication Method (CAM) supported
on offline CAM-capable cards to ensure that customers migrate from Static Data
Authentication (SDA) and Dynamic Data Authentication (DDA) to Combined Data
Authentication (CDA).

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 112
 Data Integrity Edits List
Issuer Debit Single Message System Edits (0210)

Edit Number 3
Edit Criteria Transactions monitored under this edit are identified by the following criteria:
• Card is capable of offline authentication
• DE 22 (POS Entry Mode), subfield 1 (POS Terminal PAN Entry Mode) is 05 ( PAN
auto-entry via chip)
• DE 39 (Response code) is any of the following:
– 00 (Approved or completed successfully)
– 08 (Honor with ID)
– 10 (Partial Approval)
– 85 (Not Declined)
– 87 (Purchase Amount Only, No Cash Back Allowed)
An issuer is considered noncompliant if 0% of eligible transactions show that CDA
is supported in DE 55, subelement 82 (Application Interchange Profile [AIP]). CDA
is indicated in Byte 1, bit 1 of the AIP.

Baseline/ Baseline: 500 approved chip transactions on offline CAM-capable cards

Threshold
Threshold: Greater than 0%

Reference M/Chip Requirements for Contact and Contactless, Single Message

Specifications

Fallback Decline Rater 0210

Edit Number 4
Edit Title Issuer Fallback Decline Rate (0210)
Name Fallback Decline Rate 0210
Billing Code 2DC0100
Region(s) Canada, Europe, Latin America and the Caribbean, Middle East and Africa
Description This edit monitors transactions submitted as technical fallback to ensure they are
being declined.

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 113
 Data Integrity Edits List
Issuer Chargeback Program

Edit Number 4
Edit Criteria A transaction is considered noncompliant when both of the following are true:
• DE 22 (POS Entry Mode), subfield 1 (POS Terminal PAN Entry Mode) is 80 ( Chip
card at chip-capable terminal was unable to process transaction using data on
the chip)
• DE 39 (Response Code) is any of the following:
– 00 (Approved or completed successfully)
– 08 (Honor with ID)
– 10 (Partial Approval)
– 87 (Purchase Amount Only, No Cash Back Allowed)
Exclusions: Transactions taking place at merchant locations the USA and Asia
Pacific are not monitored under this edit.

Baseline/ Baseline: 50 fallback transactions

Threshold
Threshold: 99.85%

Reference M/Chip Requirements for Contact and Contactless, Transaction Processing

Rules, Single Message Specifications

Issuer Chargeback Program

The edits in this program evaluate transactions in support of the Issuer Monitoring Program
(IMP), which establishes criteria for minimum standards of acceptable issuer chargeback
performance. Detailed information about the IMP can be found in chapter 8.5 of the Security
Rules and Procedures Manual.
Edit 1 – ISS_EXCESSIVE _CBS
Edit 2 – ISS_FNS
Edit 3 – ISS_Invalid_CLS

ISS_EXCESSIVE_CBS

Edit Number 1
Edit Title Issuer Excessive Chargebacks
Name ISS_EXCESSIVE _CBS
Billing Code 2DC0300
Regions Global
Description This edit monitors the number of chargebacks submitted on a single Primary
Account Number (PAN) each month.

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 114
 Data Integrity Edits List
Issuer Chargeback Program

Edit Number 1
Edit Criteria Transactions monitored under this edit are identified by the following criteria:
• MTI (Message Type Identifier) is 1442
• DE 24 (Function Code) is 450 (First Chargeback [Full])
• DE 25 (Message Reason Code) is not any of the following values:
– 4807 (Warning Bulletin File)
– 4808 (Authorization Related Chargeback)
– 4812 (Account number not on file)
– 4850 (Installments)
An issuer is considered noncompliant if 20 or more Chargebacks are submitted on
the same PAN for each of two consecutive months.
Note: This edit is not eligible for extensions.

Baseline/ Baseline: N/A

Threshold:
Threshold: Fewer than 20 errors

Reference IPM Clearing Formats, Security Rules and Procedures

ISS_FNS

Edit Number 2
Edit Title Issuer Fraud Notification Service
Name ISS_FNS
Billing Code 2DC0300
Regions Global
Description This edit monitors chargebacks to ensure that issuers are not circumventing the
Fraud Notification Service (FNS) block rule.

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 115
 Data Integrity Edits List
Issuer Chargeback Program

Edit Number 2
Edit Criteria Transactions monitored under this edit are identified by the following criteria:
• MTI (Message Type Identifier) is 1442
• DE 24 (Function Code) is 450 (First Chargeback [Full])
• DE 25 (Message Reason Code) is not any of the following values:
– 4807 (Warning Bulletin File)
– 4808 (Authorization Related Chargeback)
– 4812 (Account number not on file)
– 4850 (Installments)
– 4837 (No Cardholder Authorization)
A customer is considered noncompliant if a single PAN has 15 fraud chargebacks,
followed by five non-fraud chargebacks in a given month.
Note: This edit is not eligible for extensions.
Important: Data Integrity Online will display the number of non-fraud chargebacks
after the issuer has submitted 15 fraud chargebacks. So, a display of 5 errors or
more will indicate the customer is noncompliant.

Baseline/ Baseline: N/A

Threshold
Threshold: Fewer than 5 errors

Reference IPM Clearing Formats, Security Rules and Procedures

ISS_Invalid_CLS

Edit Number 3
Edit Title Issuer Invalid Chip Liability Shift
Name ISS_Invalid_CLS
Billing Code 2DC0300
Description This edit monitors issuers submitting Invalid Chip Liability Shift (CLS) chargebacks.

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 116
 Data Integrity Edits List
Global Collection Only Edits

Edit Number 3
Edit Criteria An issuer is considered noncompliant when 5 or more Primary Account Numbers
(PANs) have at least one invalid CLS chargeback in a single month.
Invalid CLS chargebacks occur when MTI (Message Type Identifier) is 1442 and DE
24 (Function Code) is 450, and either of the following are true:
1. DE 25 (Message Reason Code) is 4870 (Chip Liability Shift) on a valid Chip to
Chip transaction.
2. DE 25 (Message Reason Code) is either 4870 (Chip Liability Shift) or 4871
(Chip Liability Shift Lost/Stolen/ Never Received Issuer (NRI)/ Fraud) on any of
the following transaction types:
a. Proper Fallback from Chip (exclude POS entry mode 01)
b. Magnetic Stripe Card
c. E-commerce w/Chip Card
Note: This edit is not eligible for extensions.

Baseline/ Baseline: N/A

Threshold
Threshold: Fewer than 5 PANs with at least one error each

Reference IPM Clearing Formats, Security Rules and Procedures

Global Collection Only Edits

According to the Global Collection Only Handbook, Mastercard requires customers to submit
collection-only transaction records to Mastercard for all purchase, purchase with cash back,
unique/quasi-cash, ATM cash withdrawal, Payment Transactions, manual cash disbursement,
and refund/credit transactions enacted on the Mastercard family of brands (including
Mastercard®, Debit Mastercard®, Maestro®, or Cirrus® card issued under a Mastercard
assigned BIN) that have not been switched on the Mastercard Network.
This includes, but is not limited to, the following transactions:
• On-Us—Acquired and issued by the same customer.
• Intraprocessor—Acquired and issued by customers processing through the same processor.
• Bilateral Agreement—Separate issuer and acquirer using separate processors directly
connected to each other.
• Domestic Network—Separate issuer and acquirer using processors connected to each other
through a central switch.
• Other Transaction Scenarios—includes those transactions partially processed through the
Mastercard Network
The edits in this program monitor reporting of GCO volume as well as the data in the 1240/
First Presentment messages of collection-only transactions.
Edit 1 – GCO_Reporting

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 117
 Data Integrity Edits List
Global Collection Only Edits

Edit 2 – GCO INVALID MCC

Edit 3 – GCO INVALID MERCH ID
Edit 4 – GCO INVALID DE43
Edit 5 – GCO INVALID COUNTRY
Edit 6 – GCO INVALID STREET
Edit 7 – GCO INVALID CITY
Edit 8 – GCO INVALID TIME

GCO_Reporting

Edit Number 1
Edit Title GCO Reporting
Name GCO_Reporting
Billing Code 2DC0200
Region(s) Global
Description This edit monitors collection-only transactions to ensure that customers are
accurately reporting their Global Collection Only (GCO) volume.
Edit Criteria A Customer is out of compliance when the GCO Reporting percentage is below
80% of the previous month’s volume.
Baseline/ Baseline: Customers must have at least 25,000 eligible GCO transactions and 95%
Threshold or less of total transaction volume processed on the GCO network to be
monitored.
Threshold: 80%

Reference Global Collection Only Handbook

GCO INVALID MCC

Edit Number 2
Edit Title GCO Invalid MCC
Name GCO INVALID MCC
Billing Code 2DC0201
Region(s) Global
Description This edit monitors the card acceptor business code/merchant category code (MCC)
in collection-only transactions to ensure they are valid.

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 118
 Data Integrity Edits List
Global Collection Only Edits

Edit Number 2
Edit Criteria A merchant location is considered noncompliant if one or more transactions taking
place at that location meets any of the following criteria:

a. DE 26 (Card Acceptor Business Code [MCC]) is 3000–3350 (Airlines and Air

Carriers) and DE 43 (Card Acceptor Name/Location) , subfield 1 (Card Acceptor
Name), positions 1–9 do not match positions 1–9 of the abbreviated airline name
or DE 43, subfield 1, positions 1–9 do not match positions 1–9 of the MCC
Description.
b. DE 26 (MCC) is 3351–3500 (Car Rental Agencies) and DE 43, subfield 1,
positions 1–9 do not match positions 1–9 of the MCC Description
c. DE 26 (MCC) is 3501–3999 (Lodging—Hotels, Motels, Resorts) and DE 43,
subfield 1, positions 1–9 do not match positions 1–9 of the MCC Description
d. DE 26 (MCC) is 4511 (Air Carriers, Airlines—Not Elsewhere Classified) and DE
43, subfield 1, positions 1–9 match positions 1–9 of an abbreviated airline name or
DE 43, subfield 1, positions 1–9, match positions 1–9 of the MCC Description
e. DE 26 (MCC) is 7011 (Lodging – Hotels, Motels, Resorts – not elsewhere
classified) and DE 43, subfield 1, positions 1–13 match an MCC Description of
MCCs 3501–3999
f. DE 26 (MCC) is 7512 (Automobile Rental Agency – not elsewhere classified) and
DE 43, subfield 1, positions 1–11 match an MCC Description of MCCs 3351 and
3441
Baseline/ Baseline: 500 unique merchant locations
Threshold
Threshold: 98% of merchant locations

Reference Global Collection Only Handbook, IPM Clearing Formats, Quick Reference
Booklet

GCO INVALID MERCH ID

Edit Number 3
Edit Title GCO Invalid Merchant ID
Name GCO INVALID MERCH ID
Billing Code 2DC0201
Region(s) Global
Description This edit monitors the Card Acceptor ID (Merchant ID) in collection-only
transactions to ensure that each card acceptor location is uniquely identified.
Note: A Merchant ID can only be assigned to one location. Every transaction
containing a given Merchant ID must have the same corresponding address, city,
state, and postal code.

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 119
 Data Integrity Edits List
Global Collection Only Edits

Edit Number 3
Edit Criteria A merchant location is considered noncompliant if one or more transactions taking
place at that location contains the same Merchant ID value, found in DE 42 (Card
Acceptor ID Code) in multiple transactions but the following values are not
consistent:
• DE 43 (Card Acceptor Name/Location),subfield 2 (Card Acceptor Street Address)
• DE 43, subfield 3 (Card Acceptor City),
• DE 43, subfield 4 (Card Acceptor Postal Code),
• DE 43, subfield 5 (Card Acceptor State)

Baseline/ Baseline: 500 unique merchant locations

Threshold
Threshold: 98% of merchant locations

Reference IPM Clearing Formats

GCO INVALID DE43

Edit Number 4
Edit Title GCO Invalid DE 43
Name GCO INVALID DE43
Billing Code 2DC0201
Description This edit monitors the values in DE 43 (Card Acceptor Name/Location) in collection-
only transactions to ensure they are valid and properly formatted.
Edit Criteria A merchant location is considered noncompliant if one or more transactions taking
place at that location meets any of the following criteria:
• DE 43 (Card Acceptor Name/Location) , subfield 1 (Card Acceptor Name) is a
street address
• DE 43, subfield 1 is a telephone number and DE 26 (Card Acceptor Business
Code [MCC]) is an MCC that is not a telephone service
• DE 43, subfield 1 is all numeric, all one character or all sequential characters
(for example ABCDEF)
• DE 43, subfield 1, positions 20-22 contain the following substring “PAA”
• DE 43, subfield 1, positions 20-22 contain the following substring “Rxx”
• DE 43, subfield 1, positions 20-22 contain the following substring “Sxx”
• DE 43, subfield 1, positions 20-22 contain the following substring “Wxx”
• DE 43, subfield 1, positions 20-22 contain the following substring “PAY”

Baseline/ Baseline: 500 unique merchant locations

Threshold
Threshold: 98% of merchant locations

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 120
 Data Integrity Edits List
Global Collection Only Edits

Edit Number 4
Reference Global Collection Only Handbook, IPM Clearing Formats

GCO INVALID COUNTRY

Edit Number 5
Edit Title GCO Invalid Country
Name GCO INVALID COUNTRY
Billing Code 2DC0201
Region(s) This edit applies to the following countries: Argentina, Australia, Austria, Belgium,
Canada, Costa Rica, Czech Republic, Denmark, Finland, Germany, Greece,
Hungary, Israel, Korea, Kuwait, Malaysia, Netherlands, New Zealand, Norway,
Philippines, Puerto Rico , Singapore, Sweden, Switzerland, Taiwan, Thailand,
Turkey, USA, Venezuela
Description This edit monitors the postal code and/or country code value submitted in DE 43
(Card Acceptor Name/Location) in collection-only transactions to ensure values are
present, valid, and correspond to the appropriate POS location.
Edit Criteria A merchant location is considered noncompliant if one or more transactions taking
place at that location meets any of the following criteria:
• DE 43 (Card Acceptor Name/Location) , subfield 6 (Card Acceptor Country
Code) is CAN and DE 43, subfield 4 (Card Acceptor Postal [ZIP] Code) is
“unknown” or is not a valid postal code in Canada
• DE 43, subfield 6 is AUS and DE 43, subfield 4 is “unknown” or is not a valid
postal code in Australia
• DE 43, subfield 6 is DEU and DE 43, subfield 4 is “unknown” or is not a valid
postal code in Germany
• DE 43, subfield 6 is USA and DE 43, subfield 4 is “unknown” or is not a valid
postal code in the United States
• DE 43, subfield 6 is ARG, FIN, MYS, KOR, AUT, NLD, SWE, BEL, GRC, NZL, CHE,
HUN, NOR, TWN, PHL, THA, ISR, TUR, CRI, PRI, CZE, DNK, KWT, SGP or VEN
and DE 43, subfield 4 is “unknown” or is not present

Baseline/ Baseline: 500 unique merchant locations

Threshold
Threshold: 98% of merchant locations

Reference Global Collection Only Handbook, IPM Clearing Formats

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 121
 Data Integrity Edits List
Global Collection Only Edits

GCO INVALID STREET

Edit Number 6
Edit Title GCO Invalid Street Address
Name GCO INVALID STREET
Billing Code 2DC0201
Region(s) Global
Description This edit monitors DE 43 (Card Acceptor Name/Location), subfield 2 (Card
Acceptor Street Address) in collection-only transactions to ensure it is formatted
properly.
Edit Criteria A merchant location is considered noncompliant if one or more transactions taking
place at that location meets any of the following criteria:
• DE 43, subfield 2 is null or all spaces
• DE 43, subfield 2 contains “unknown”
• DE 43, subfield 2 is all numeric
• DE 43, subfield 2 is less than three characters in length
Exception: A value of “RR” is permitted in Canada

Baseline/ Baseline: 500 unique merchant locations

Threshold
Threshold: 98% of merchant locations

Reference IPM Clearing Formats

GCO INVALID CITY

Edit Number 7
Edit Title GCO Invalid City
Name GCO INVALID CITY
Billing Code 2DC0201
Region(s) Global
Description This edit monitors the values in DE 43 (Card Acceptor Name/Location) on face-to-
face collection-only transactions to ensure the city name is valid and corresponds
appropriately to the provided postal code.
Edit Criteria A merchant location is considered noncompliant if one or more transactions taking
place at that location meets any of the following criteria:

a. Globally, DE 43, subfield 3 (Card Acceptor City) contains invalid character sets
for the specified country code page

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 122
 Data Integrity Edits List
Global Collection Only Edits

Edit Number 7
b. DE 43, subfield 4 (Card Acceptor Postal [ZIP] Code) is invalid for the city given in
DE 43, subfield 3 when merchant country is CAN
c. DE 43, subfield 4 is invalid for the city given in DE 43, subfield 3 when merchant
country is DEU
d. DE 43, subfield 4 is invalid for the city given in DE 43, subfield 3 when merchant
country is AUS
e. DE 43, subfield 4 is invalid for the city given in DE 43, subfield 3 when merchant
country is USA
f. Globally, DE 43 subfield 3 is blank or null, all one character, all numeric, less than
3 characters, UNKNOWN
Exclusions: Subedit F excludes CAN, DEU, AUS and USA.
Baseline/ Baseline: 500 unique merchant locations
Threshold
Threshold: 98% of merchant locations

Reference Global Collection Only Handbook, IPM Clearing Formats

GCO INVALID TIME

Edit Number 8
Edit Title GCO Invalid Time
Name GCO INVALID TIME
Billing Code 2DC0201
Region(s) Global
Description This edit monitors collection-only transactions to ensure that no two transactions in
the same batch file have identical values for the local time and date.
Edit Criteria A merchant location is considered noncompliant if one or more transactions taking
place at that location have identical values in the following DE 12 (Date and Time,
Local Transaction) , subfield 1 (Date) and subfield 2 (Time).
Baseline/ Baseline: 500 unique merchant locations
Threshold
Threshold: 98% of merchant locations

Reference Global Collection Only Handbook, IPM Clearing Formats

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 123
 Data Integrity Edits List
Mastercard Identity Check (AReq/ARes)

Mastercard Identity Check (AReq/ARes)

The edits in this program monitor data in the various authentication messages used by the
EMV 3-D secure protocol. Transactions authentication through 3DS 1.0 are not monitored
under this program.
Table of Contents:
Edit 1 - Authentication Rate
Edit 2 - Authn Non-Static Method
Edit 3 - ACS Authn Error Rate
Edit 4 - 3DSS Authn Error Rate
Edit 5 - ACS Availability
Edit 6 - ACS Latency

Authentication Rate

Edit Number 1
Edit Title Issuer Authentication Rate (ARes)
Name Authentication Rate
Billing Code 2DC0100
Region(s) Global - Select European countries excluded. (See excluded country list in Appendix
C.)
Description This edit monitors the Authentication Response (ARes) messages to determine the
issuer’s overall authentication rate.
Edit Criteria Issuers are considered noncompliant if more than15% of authentication requests
are not authenticated.
Authenticated transactions are identified by the EMV® 3-DS Specification data
element definition of Transaction Status. A value of Y indicates that the transaction
was successfully authenticated.

Baseline/ Baseline: 1,000 EMV 3-DS transactions

Threshold
Threshold: 85%

Reference Mastercard Identity Check Program Guide

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 124
 Data Integrity Edits List
Mastercard Identity Check (AReq/ARes)

Authn Non-Static Method

Edit Number 2
Edit Title Issuer Authentication Non-Static Method (ARes)
Name Authn Non-Static Method
Billing Code 2DC0100
Region(s) Global - Select European countries excluded. (See excluded country list in Appendix
C.)
Description This edit monitors the method used by issuers to authenticate cardholders.
Edit Criteria Transactions are considered noncompliant when authentication is performed using
a static method.
Static method authentication is identified by the EMV® 3-DS Specification data
element definition of Authentication Type. A value of 01 indicates a static method
was used.

Baseline/ Baseline: 1,000 EMV 3-DS transactions

Threshold
Threshold: 99%

Reference Mastercard Identity Check Program Guide

ACS Authn Error Rate

Edit Number 3
Edit Title Issuer ACS Authentication Error Rate (ARes)
Name ACS Authn Error Rate
Billing Code 2DC0100
Region(s) Global
Description This edit monitors all authentication messages sent by the Access Control Server
(ACS) to determine the number of messages that result in an error response.
Edit Criteria Authentication messages from issuer’s ACS are considered noncompliant if they
result in an error message.
Baseline/ Baseline: 1,000 EMV 3-DS transactions
Threshold
Threshold: 99%

Reference Mastercard Identity Check Program Guide

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 125
 Data Integrity Edits List
Mastercard Identity Check (AReq/ARes)

3DSS Authn Error Rate

Edit Number 4
Edit Title Acquirer 3DSS Authentication Error Rate
Name 3DSS Authn Error Rate
Billing Code 2DC0100
Region(s) Global
Description This edit monitors all authentication messages sent by the 3DS Server (3DSS) to
determine the number of messages that result in an error response.
Edit Criteria Authentication messages from the Acquirer 3DSS are considered noncompliant if
they result in an error message.
Baseline/ Baseline: 1,000 EMV 3-DS transactions
Threshold
Threshold: 99%

Reference Mastercard Identity Check Program Guide

ACS Availability

Edit Number 5
Edit Title Issuer ACS Availability (ARes)
Name ACS Availability
Billing Code 2DC0100
Region(s) Global
Description This edit monitors the Access Control server (ACS) response rate to Authentication
Request (AReq) messages.
Edit Criteria Issuers are considered noncompliant if the ACS fails to respond to more than 1%
of AReq messages.
Baseline/ Baseline: 1,000 EMV 3-DS transactions
Threshold
Threshold: 99%

Reference Mastercard Identity Check Program Guide

ACS Latency

Edit Number 6
Edit Title Issuer ACS Latency (ARes)

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 126
 Data Integrity Edits List
Mastercard Identity Check (AReq/ARes)

Edit Number 6
Name ACS Latency
Billing Code 2DC0100
Region(s) Global
Description This edit monitors the issuer’s Access Control Server (ACS) response time to an
Authentication Request.
Edit Criteria An Authentication Response (ARes) message is considered noncompliant if it is not
received within 5 seconds of when Authentication Request (AReq) was sent by the
Directory Server (DS).
Baseline/ Baseline: 1,000 EMV 3-DS transactions
Threshold
Threshold: 95%

Reference Mastercard Identity Check Program Guide

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 127
 Global Collection Only Program (GCO)

Appendix A Global Collection Only Program (GCO)

A Collection Only transaction is described as
This includes, but is not limited to, the following transactions:
• On-Us—Acquired and issued by the same customer.
• Intraprocessor—Acquired and issued by customers processing through the same processor.
• Bilateral Agreement—Separate issuer and acquirer using separate processors directly connected
to each other.
• Domestic Network—Separate issuer and acquirer using processors connected to each other
through a central switch.
• Other Transaction Scenarios—Includes those transactions partially processed through the
Mastercard Network (for example, submitted for authorization but not for clearing and
settlement).
Customers are required to send Collection Only transaction information to Mastercard using the
Integrated Product Messages (IPM) format, which is based on the ISO 8583-1993 format. Further
details can be found in the GCMS Reference Manual.
Customers that do not report complete and accurate Collection Only information to Mastercard will
be notified via email of any Global Collection Only compliance errors and automatically assessed a
non-compliance fee on either a monthly or quarterly basis. Acquirers must register for Data
Integrity Online to receive their noncompliance email notification. The Global Collection Only
Program monitors customer's Collection Only reporting under the following categories.
• Customers that report less than 20% of their eligible Collection only transactions are considered
to be under reporting and may be assessed on a monthly basis.
Customers that need to find out about the quality and completeness of their Collection Only
reporting information status may do so by contacting their customer service representative or by
sending an email message to [email protected].
Customers that want to request an extension should click on Extensions in the edit tile to open
the options. Customers can then apply for an extension per the current process by selecting Apply
for Extension or they can view their history by selecting Extension History.

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 128
 Data Integrity Program Extension Policy and Procedures
Data Integrity Noncompliance Extension

Appendix B Data Integrity Program Extension Policy and

Procedures

Data Integrity Noncompliance Extension

Mastercard Data Integrity may grant short-term extensions to noncompliant ICA numbers or
Processor IDs on a case-by-case basis.
Only a customer may request an extension for the customer’s acquiring/issuing/owning ID/ICA
number. The request must be submitted by going to Data Integrity Online and clicking on
Apply For Extension in the edit tile.
If the customer claims to be prevented from fully complying with Mastercard specifications
because of law or regulation, the customer must provide a copy of the law or regulation and
if such law or regulation is in a language other than English, a complete English translation. As
a condition of granting an extension for that reason, Mastercard Worldwide may require the
customer to provide additional legal documentation.

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 129
 Data Integrity Program Extension Policy and Procedures
Request Extension in Edit Tile

Request Extension in Edit Tile

Customers wanting to request an Extension will click on Extensions in the edit tile to open
up options. Customer can Apply for Extension as currently done or view Extension
History.

No Forms to Attach and Send by Email

Clicking Apply for Extension will bring the user to a new online form.
Clicking SUBMIT once the form is completed will send a message to Mastercard Data Integrity
advising a new Extension Request has been submitted. The Data Integrity team will review the
request and will Approve, Decline or Return for more information.

Extension History
Clicking Extension History will allow Customers to see the full extension history for ICA
Number/Edit combination in the edit tile. This will show approved and declined requests.

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 130
 Data Integrity Program Extension Policy and Procedures
Submission Deadline

Submission Deadline
Customers must submit extensions no later than the Comply By date listed on the edit tile.
Extension requests may still be submitted after the Comply By date; however, they will not be
effective until the first day of the month following the submission.
For example, if the Comply By date is 1 May, then an extension request must be submitted
before 1 May in order to meet the May deadline. A request submitted on or after 1 May
would not be effective until 1 June, and the ICA number will be assessed a noncompliance fee
if the May compliance rate is below the required compliance threshold for the edit.
Maximum extension length will remain six months, except where noted in individual edit
descriptions.

Data Integrity Support

Data integrity online support is available by email and through local help desks.
For Data Integrity Online support, please contact:

Franchise Integrity

E-mail: [email protected]

For more information about the Data Integrity Online application, please contact your regional
Help Desk, or the Customer Technical Services team.
Conference calls and/or training is available upon request by sending an e-mail to
[email protected]

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 131
 Exclusions

Appendix C Exclusions
Issuers in the countries listed below are exempted from the following edits:
• Issuer Authentication Non-Static Method (ARes)
• Issuer Authentication Rate (ARes)
• Fully Authenticated Transaction Approval Rate (0110)

Albania, Andorra, Armenia, Austria, Azerbaijan, Belarus, Belgium, Bosnia and Herzegovina,
Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, France, Georgia, Germany,
Gibraltar, Greece, Hungary, Iceland, Ireland, Israel, Italy, Kazakhstan, Kosovo, Kyrgyzstan, Latvia,
Liechtenstein, Lithuania, Luxembourg, Macedonia, Malta, Moldova, Monaco, Montenegro,
Netherlands, Norway, Poland, Portugal, Romania, Russia, San Marino, Serbia, Slovakia, Slovenia,
Spain, Sweden, Switzerland, Tajikistan, Turkey, Turkmenistan, Ukraine, United Kingdom, Uzbekistan,
Vatican

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 132
 Notices

Notices
Following are policies pertaining to proprietary rights, trademarks, translations, and details
about the availability of additional information online.

Proprietary Rights
The information contained in this document is proprietary and confidential to Mastercard International
Incorporated, one or more of its affiliated entities (collectively “Mastercard”), or both.
This material may not be duplicated, published, or disclosed, in whole or in part, without the prior
written permission of Mastercard.

Trademarks
Trademark notices and symbols used in this document reflect the registration status of Mastercard
trademarks in the United States. Please consult with the Global Customer Service team or the
Mastercard Law Department for the registration status of particular product, program, or service
names outside the United States.
All third-party product and service names are trademarks or registered trademarks of their respective
owners.

Disclaimer
Mastercard makes no representations or warranties of any kind, express or implied, with respect to the
contents of this document. Without limitation, Mastercard specifically disclaims all representations and
warranties with respect to this document and any intellectual property rights subsisting therein or any
part thereof, including but not limited to any and all implied warranties of title, non-infringement, or
suitability for any purpose (whether or not Mastercard has been advised, has reason to know, or is
otherwise in fact aware of any information) or achievement of any particular result. Without
limitation, Mastercard specifically disclaims all representations and warranties that any practice or
implementation of this document will not infringe any third party patents, copyrights, trade secrets or
other rights.

Translation
A translation of any Mastercard manual, bulletin, release, or other Mastercard document into a
language other than English is intended solely as a convenience to Mastercard customers. Mastercard
provides any translated document to its customers “AS IS” and makes no representations or
warranties of any kind with respect to the translated document, including, but not limited to, its
accuracy or reliability. In no event shall Mastercard be liable for any damages resulting from reliance on
any translated document. The English version of any Mastercard document will take precedence over
any translated version in any legal proceeding.

Information Available Online

Mastercard provides details about the standards used for this document—including times expressed,
language use, and contact information—on the Publications Support page available on Mastercard
Connect™. Go to Publications Support for centralized information.

©2009–2019 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 9 May 2019 133