Data Integrity Monitoring Program

Data Integrity Monitoring
Program
24 January 2023
DIMP
Contents
Contents
Summary of Changes, 24 January 2023.....................................................................8
Chapter 1: Data Integrity monitoring........................................................................10

Data Integrity Monitoring Program................................................................................................... 11
Data Integrity programs list overview............................................................................................... 12
Edit life cycle...........................................................................................................................................14
Data Integrity extensions.....................................................................................................................15
Data Integrity assessment structure.................................................................................................18
Billing event codes................................................................................................................................. 18
Data Integrity Online............................................................................................................................ 20
Register for Data Integrity Online.................................................................................................20
Access the application.....................................................................................................................21
View your institution’s data............................................................................................................21
Add new customers to your Data Integrity Online profile........................................................ 22
Data Integrity Online edit reports...................................................................................................... 23
Data Integrity Online Reporting..........................................................................................................24
Data Integrity Online manuals and guides........................................................................................24
Contact us...............................................................................................................................................25
Chapter 2: Acquirer Authorization Dual Message System Edits (0100)... 26

Retired edits............................................................................................................................................27
Edit 1 ADD_DATA...................................................................................................................................27
Edit 2 AFD...............................................................................................................................................28
Edit 3 Magstripe.................................................................................................................................... 29
Edit 4 Date_Time...................................................................................................................................31
Edit 5 Cntry 2......................................................................................................................................... 31
Edit 6 DE 43............................................................................................................................................33
Edit 7 INV_STATE...................................................................................................................................34
Edit 8 TermPOS......................................................................................................................................35
Edit 9 POS Cnd...................................................................................................................................... 38
Edit 10 Ecom.......................................................................................................................................... 38
Edit 11 A_PF_ID..................................................................................................................................... 40
Edit 12 Pure Magstripe ATM 0100..................................................................................................... 41
Edit 13 Pure Magstripe POS 0100..................................................................................................... 42
Edit 15 INC_MAGSTRIPE_0100...........................................................................................................42
Edit 16 AUTH_UNDEFINED_0100......................................................................................................43
Edit 17 AUTH_PREAUTH_0100...........................................................................................................44
Edit 18 AFD_MAND_PRE_AUTH......................................................................................................... 45
©2009–2023 Mastercard. Proprietary. All rights reserved.

Data Integrity Monitoring Program • 24 January 2023 2
Contents
Edit 20 ABU ACQ...................................................................................................................................46

Edit 23 DS TRAN ID FOR AUTH TRAN...............................................................................................47
Edit 24 Contactless Terminal...............................................................................................................48
Edit 25 ACQ_SKIP_EXEMPT_FLAG.................................................................................................... 49
Edit 27 DSRP Cryptogram Placement_0100................................................................................... 51
Edit 28 TTI Monitoring 0100................................................................................................................52
Edit 29 Funding Transactions 0100....................................................................................................53
Edit 31 MIT Recurring Trace ID Usage................................................................................................54
Edit 32 Gambling Authorization 0100...............................................................................................55
Edit 33 Software MPOS 0100............................................................................................................ 56
Chapter 3: Acquirer Authorization Chip Dual Message System Edits

(0100)....................................................................................................................................... 58
Retired edits............................................................................................................................................59
Chip testing requirement..................................................................................................................... 59
Edit 1 AC_Missing_DE12...................................................................................................................... 59
Edit 7 AC_Inv_form_DE55....................................................................................................................64
Edit 8 AC_Missing_EMVtags_DE55....................................................................................................64
Edit 9 AC_Inv_length_DE55................................................................................................................. 65
Edit 10 AC_Inv_DE61_SF11.................................................................................................................66
Edit 11 Fallback Rt ATM 0100.............................................................................................................67
Edit 12 Fallback Rt POS 0100.............................................................................................................68
Edit 14 AC_INV_EMVTAGS_DE55.......................................................................................................69
Edit 15 Contactless CVM Limits 0100...............................................................................................70
Chapter 4: Acquirer Clearing Dual Message System Edits (1240)............... 73

Retired edits............................................................................................................................................74
Edit 1 MCC..............................................................................................................................................74
Edit 2 MERCHANT ID............................................................................................................................75
Edit 3 INV DE43.....................................................................................................................................76
Edit 4 CNTRY GEO................................................................................................................................ 77
Edit 5 INV_STREET................................................................................................................................79
Edit 6 INV ADDR.................................................................................................................................... 80
Edit 7 TERM POS...................................................................................................................................81
Edit 8 TRACE_ID.....................................................................................................................................82
Edit 9 POST_CD_MATCH..................................................................................................................... 83

Contents
Edit 10 POS_AUTH................................................................................................................................84
Edit 11 C_PF_ID..................................................................................................................................... 86
Edit 13 MCC_MATCH............................................................................................................................87
Edit 14 MERCH_DBA_NAME_MATCH................................................................................................88
Edit 16 TERM_INPUT_MATCH.............................................................................................................89
Edit 17 AAV_RATE_CLEAR_TRAN.......................................................................................................91
Edit 18 DS_TRAN_ID_CLEAR_TRANS................................................................................................ 91
Edit 20 Cross Border TC28 Force Post 1240....................................................................................92
Edit 21 High Risk MCC Mismatch.......................................................................................................93
Edit 22 POI Currency Conversion 1240............................................................................................. 94
Chapter 5: Acquirer Clearing Chip Dual Message System Edits (1240).... 96

Edit 1 CC_Missing_DE55......................................................................................................................97
Edit 2 CC_Missing_EMVtags_DE55....................................................................................................97
Edit 3 CC_Inv_Length_DE55................................................................................................................98
Edit 4 CC_Inv_EMVtags_DE55............................................................................................................99
Edit 5 CC_Inv_form_DE55................................................................................................................. 100
Chapter 6: Acquirer Debit Single Message System Edits (0200)................102

Retired edits......................................................................................................................................... 103
Edit 1 D_INVMCC (5542)...................................................................................................................103
Edit 2 D_MAGSTRIPE..........................................................................................................................104
Edit 3 D_INVTYPE............................................................................................................................... 105
Edit 4 D_DE42......................................................................................................................................106
Edit 5 D_DE43......................................................................................................................................107
Edit 7 D_TERMPOS.............................................................................................................................108
Edit 8 D_POSCND...............................................................................................................................110
Edit 9 D_PF_ID.....................................................................................................................................111
Edit 10 D_Pure_Magstripe ATM........................................................................................................112
Edit 11 D_Pure Magstripe POS.........................................................................................................113
Edit 12 D_INC_MAGSTRIPE_0200................................................................................................... 114
Edit 16 DSRP Cryptogram Placement_0200.................................................................................115
Edit 17 TTI Monitoring 0200............................................................................................................. 116
Edit 18 POI Currency Conversion 0200...........................................................................................117
Edit 19 Funding Transactions 0200................................................................................................. 118
Edit 21 Software MPOS 0200..........................................................................................................119
Chapter 7: Acquirer Debit Single Message System Chip Edits (0200)..... 121
Retired edits......................................................................................................................................... 122
Chip testing requirement...................................................................................................................122
Edit 1 DC_Missing_DE35....................................................................................................................122

Contents
Edit 4 DC_Inv_form_DE55................................................................................................................. 124
Edit 5 DC_Missing_EMVtags_DE55................................................................................................. 125
Edit 6 DC_Inv_Length_DE55............................................................................................................. 126
Edit 7 DC_Inv_DE61_SF11................................................................................................................ 127
Edit 8 Fallback Rt ATM 0200.............................................................................................................128
Edit 9 Fallback Rt POS 0200.............................................................................................................128
Edit 11 DC_INV_EMVTAGS_DE55....................................................................................................129
Edit 12 Contactless CVM Limits 0200............................................................................................ 130
Chapter 8: Acquirer Chargeback Monitoring Program.................................... 133

About edits........................................................................................................................................... 134
Edit 1 Excessive Fraud Merchant......................................................................................................134
Edit 2 Excessive Chargeback Merchant...........................................................................................137
Acquirer Chargeback Monitoring Program regulated/non-regulated countries......................139
Chapter 9: Issuer Authorization Dual Message System Edits (0110)...... 143

Retired edits......................................................................................................................................... 144
Edit 4 EMV_ARPC_0110.................................................................................................................... 144
Edit 13 NO_CVM_HIGH_DECLINE_PT.............................................................................................145
Edit 14 NO_CVM_HIGH_DECLINE_VEND.......................................................................................146
Edit 15 ISS_OFFLINE_CAM_0110....................................................................................................147
Edit 18 Fallback Decline Rate 0110.................................................................................................148
Edit 19 Issuer COF Monitoring (0110)............................................................................................ 149
Edit 20 ABU Penetration Rate.......................................................................................................... 150
Edit 21 ABU for Issuers.......................................................................................................................151
Edit 22 Invalid AVS Value (0110)......................................................................................................152
Edit 23 SDA Capable Cards (0110).................................................................................................153
Edit 26 EMV3DS_Non_Low_Risk_Appr_Rt......................................................................................154
Edit 27 EMV3DS_Full_Authent_Appr_Rt.........................................................................................155
Edit 28 Contactless Issuer................................................................................................................. 157
Edit 29 Do Not Honor 05 Declines 0110.........................................................................................158
Edit 30 Auth Refund Inv Declines 0110...........................................................................................159
Edit 31 Auth Refund Appr Rt 0110..................................................................................................160
Chapter 10: Issuer Debit Single Message System Edits (0210).................. 162
Retired edits......................................................................................................................................... 163
Edit 2 EMV_ARPC_0210.................................................................................................................... 163
Edit 3 ISS_OFFLINE_CAM_0210...................................................................................................... 164
Edit 4 Fallback Decline Rate 0210....................................................................................................165

Contents
Edit 5 SDA Capable Cards 0210...................................................................................................... 166

Edit 6 Do Not Honor 05 Declines 0210........................................................................................... 167
Chapter 11: Issuer Chargeback Program............................................................... 169

Edit 1 ISS_EXCESSIVE_CBS..............................................................................................................170
Edit 2 ISS_FNS.....................................................................................................................................170
Edit 3 ISS_Invalid_CLS........................................................................................................................171
Chapter 12: Digital Standards Program ................................................................173

About Digital Standards Program................................................................................................... 174
Edit 1 CNP APP RT CREDIT 0110.................................................................................................... 175
Edit 2 CNP APP RT DEBIT 0110....................................................................................................... 177
Edit 3 CNP APP RT CR WORLD 0110............................................................................................. 180
Edit 4 CNP APP RT PREPAID 0110.................................................................................................. 183
Chapter 13: Global Collection Only Edits...............................................................186

About Global Collection Only edits...................................................................................................187
Edit 1 GCO_Reporting........................................................................................................................187
Edit 2 GCO INVALID MCC..................................................................................................................188
Edit 3 GCO INVALID MERCH ID........................................................................................................189
Edit 4 GCO INVALID DE43................................................................................................................ 190
Edit 5 GCO INVALID COUNTRY........................................................................................................191
Edit 6 GCO INVALID STREET............................................................................................................192
Edit 7 GCO INVALID CITY..................................................................................................................193
Edit 8 GCO INVALID TIME................................................................................................................. 194
Edit 9 GCO Quarterly Reporting.......................................................................................................195
Chapter 14: Mastercard Identity Check (AReq/ARes).....................................196

Retired edits......................................................................................................................................... 197
Mastercard Identity Check (AReq/ARes) exclusions......................................................................197
Edit 1 Authentication Rate................................................................................................................198
Edit 2 Authn Non-Static Method......................................................................................................199
Edit 3 ACS Authn Error Rate.............................................................................................................199
Edit 4 3DSS Authn Error Rate...........................................................................................................200
Edit 5 ACS Availability........................................................................................................................201
Edit 7 3RI_AUTH_TRANS_DECLINE................................................................................................. 201
Edit 8 ACS_AUTHEN_ABANDON_RATE..........................................................................................202
Edit 9 CHALLENGE_FLOW_3DS......................................................................................................202
Edit 11 ISS_AUTH_SCA_EXEMP.......................................................................................................203
Edit 12 BIOMETRIC_AUTH_RATE..................................................................................................... 204

Contents
Chapter 15: Fraud Reporting Performance Program........................................206

Edit 1 Rejects....................................................................................................................................... 207
Edit 2 Suspends Suspicious Amount................................................................................................207
Edit 3 Suspends Amount Difference................................................................................................208
Edit 4 Deletes.......................................................................................................................................209
Chapter 16: Addendum Data Performance Program....................................... 211

Edit 1 PDS 0507 Issuing Carrier....................................................................................................... 212
Edit 2 PDS 0509 Issue Date..............................................................................................................212
Edit 3 PDS 0520 Travel Date............................................................................................................ 213
Edit 4 PDS 0574 Arrival Date........................................................................................................... 214
Edit 5 PDS 0577 Property Phone Number..................................................................................... 215
Notices................................................................................................................................... 216

Summary of Changes, 24 January 2023

This summary reflects changes effective since the 11 October 2022 update of this
publication.
Description of Change Where to Look

Minor editorial, grammar, or formatting Throughout
changes
Chapter 2 Acquirer Authorization Dual Message System Edits (0100)
Updated Edit 1 ADD_DATA Edit 1 ADD_DATA
Updated Edit 6 DE 43 Edit 6 DE 43
Updated Edit 8 TermPOS Edit 8 TermPOS
Updated Edit 10 Ecom Edit 10 Ecom
Updated Edit 17 AUTH_PREAUTH_0100 Edit 17 AUTH_PREAUTH_0100
Updated Edit 20 ABU ACQ Edit 20 ABU ACQ
Updated Edit 24 Contactless Terminal Edit 24 Contactless Terminal
Updated Edit 25 ACQ_SKIP_EXEMPT_FLAG Edit 25 ACQ_SKIP_EXEMPT_FLAG
Added Edit 31 MIT Recurring Trace ID Usage Edit 31 MIT Recurring Trace ID Usage
Added Edit 32 Gambling Authorization 0100 Edit 32 Gambling Authorization 0100
Added Edit 33 Software MPOS 0100 Edit 33 Software MPOS 0100
Chapter 4 Acquirer Clearing Dual Message System Edits (1240)
Updated Edit 2 MERCHANT ID Edit 2 MERCHANT ID
Updated Edit 10 POS_AUTH Edit 10 POS_AUTH
Updated Edit 13 MCC_MATCH Edit 13 MCC_MATCH
Updated Edit 21 High Risk MCC Mismatch Edit 21 High Risk MCC Mismatch
Chapter 6 Acquirer Dept Single Message System Edits (0200)
Updated Edit 2 D_MAGSTRIPE Edit 2 D_MAGSTRIPE
Added Edit 21 Software MPOS 0200 Edit 21 Software MPOS 0200
Chapter 8 Acquirer Chargeback Monitoring Program
Updated Edit 1 Excessive Fraud Merchant Edit 1 Excessive Fraud Merchant
Chapter 9 Issuer Authorization Dual Message System Edits (0110)
Updated Edit 20 ABU Penetration Rate Edit 20 ABU Penetration Rate
Updated Edit 21 ABU for Issuers Edit 21 ABU for Issuers

Description of Change Where to Look

Updated Edit 26 EMV3DS_Non_Low_Risk Edit 26 EMV3DS_Non_Low_Risk_Appr_Rt
Appr_Rt
Updated Edit 27 Edit 27 EMV3DS_Full_Authent_Appr_Rt
EMV3DS_Full_Authent_Appr_Rt
Updated Edit 28 Contactless Issuer Edit 28 Contactless Issuer
Updated Edit 30 Auth Refund Inv Declines Edit 30 Auth Refund Inv Declines 0110
0110
Chapter 12 Digital Standards Program
Updated About Digital Standards Program About Digital Standards Program
Updated Edit 1 CNP APP RT CREDIT 0110 Edit 1 CNP APP RT CREDIT 0110
Updated Edit 2 CNP APP RT DEBIT 0110 Edit 2 CNP APP RT DEBIT 0110
Updated Edit 3 CNP APP RT CR WORLD Edit 3 CNP APP RT CR WORLD 0110
0110
Updated Edit 4 CNP APP RT PREPAID 0110 Edit 4 CNP APP RT PREPAID 0110
Chapter 14 Mastercard Identity Check (AReq/ARes)
Updated Edit 1 Authentication Rate Edit 1 Authentication Rate

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 Program...................................................................................................................11

Data Integrity programs list overview.............................................................................................................. 12
Edit life cycle.......................................................................................................................................................... 14
Data Integrity extensions....................................................................................................................................15
Data Integrity assessment structure................................................................................................................ 18
Billing event codes.................................................................................................................................................18
Data Integrity Online............................................................................................................................................20
Register for Data Integrity Online................................................................................................................20
Access the application.................................................................................................................................... 21
View your institution’s data...........................................................................................................................21
Add new customers to your Data Integrity Online profile....................................................................... 22
Data Integrity Online edit reports......................................................................................................................23
Data Integrity Online Reporting.........................................................................................................................24
Data Integrity Online manuals and guides.......................................................................................................24
Contact us..............................................................................................................................................................25

Data Integrity Monitoring Program
Data Integrity Monitoring Program

The Data Integrity Monitoring Program is a performance program that exists to
promote data quality and processing efficiency on the Mastercard Network.
Systematic validation, or edits, help ensure that customers:
• Process data according to Mastercard rules, standards, specifications, and
mandates
• Adhere to product and service mandates as applicable
What is an edit? An edit is a set of criteria that focuses on a specific component of
a transaction, authentication message, or a program requirement. An edit may
check to see if
• a certain data element is present in a transaction,
• a value is properly formatted,
• or if a mandated product is implemented.
Data Integrity edits do not block, decline, or downgrade transactions. Instead,
transactions flow through the network, and data is evaluated after the fact
against the edit criteria.
Most Data Integrity edits are evaluated over the period of one month to examine
holistic data trends, and to ensure that customers are not penalized for marginal
errors or exceptions.
Each edit has a baseline and a threshold.
The baseline indicates the number or type of transactions needed to be included in
the edit.
The threshold indicates the percentage or number of transactions that a customer
must meet to determine performance status for the edit.
What is the scope of Data Integrity? The range of our performance program
evolves with the industry. Currently, data in single and dual message systems,
cardholder authentication messages, Quarterly Mastercard Reporting (QMR), the
Fraud and Loss Database (FLD), and customer configurations are examined for
Mastercard products1.
However, Data Integrity continues to expand its scope accordingly as new payment
channels, industry regulations, and network requirements arise.
What happens if a customer is under performing with an edit? When an ICA
number or processor ID is determined to be under performing with an edit, all
registered users of Data Integrity Online (for that ICA number or processor ID)
receive an email notification.
1 Mastercard products include Mastercard®, Debit Mastercard®, Maestro®, or Cirrus® Card. Private
Label (PVL) products are excluded from monitoring in all Data Integrity edits and programs.

Data Integrity programs list overview
Customers are directed to log in to Data Integrity Online to view their complete
status, access reports, and learn more about how to meet the edit requirement.
Data Integrity provides a grace period and establishes a 'Comply by' date by which
the customer is expected to meet the edit requirements.
Acquirers, issuers, and processors must correct errors by the date provided on the
dashboard edit tile. To avoid Data Integrity assessments, customers must remain
at or above the threshold for two consecutive reporting months (unless otherwise
noted in the edit description) after corrections have been made.
After the Comply by Date, ICA numbers and processor IDs that remain under
performing are subject to assessments. For additional information, refer to the
“Data Integrity assessment structure” section of this program guide for additional
information.

This document provides detailed information on each edit monitored by Data
Integrity. Edits are grouped into programs based primarily on the type of
transaction or data being evaluated.
Table 1: Edit table legend details how to read and interpret each edit.
Table 1: Edit table legend
Term Description
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. For example, 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 nonperforming.

Term Description
Baseline/ Baseline: Number or type of transactions required in a given month to be
Threshold included in the edit.
Threshold: Percentage or number of transactions required to determine
performance status for the edit.
Reference Documentation where additional information supporting this edit can be

found

Edit life cycle
Edit life cycle

The Life cycle figure details the Data Integrity performance process from a
customer’s perspective from the time a monthly edit is first announced to the time
that assessments are applied.
Figure 1: Life cycle

Data Integrity extensions

Mastercard Data Integrity may grant short-term extensions to under performing
ICA numbers or processor IDs on a case-by-case basis.
Many edits are eligible for an extension of up to six months with a valid business
justification. If an edit is not eligible for an extension, this is noted in the edit tile in
Data Integrity Online.
In order to apply for an extension, customers must log in to Data Integrity Online.
Once there, customers must navigate to the edit tile for which the extension is
being requested, and choose Apply for Extension from the tile drop-down menu.
Extension history is also available through a link on the edit tile.
NOTE: Some edits do not become eligible for an extension until two months prior to the
Comply by Date. In this case, no option appears in the tile to request an extension.
When Apply for Extension is selected, a prepopulated extension request form

opens. Customers must verify the information and fill in all required fields denoted

with an asterisk. Once complete, click Submit to send the extension request to the
Data Integrity team for review. A confirmation email is sent to the requestor with
an Extension ID for reference.
A response to the extension request is provided within five business days. Data
Integrity staff can approve an extension request for up to six months. After the six
month extension expires, no further extension is granted and assessments may be
applicable for future nonperformance. With any extensions granted, Mastercard
applies back billing2 should the customer remain below the threshold at the
conclusion of the extension. Customers can email Data Integrity with any
questions or concerns at ps_data_integrity@mastercard.com.
Submission deadline
Extension requests submitted after the Comply by Date are not effective until the
first day of the following month.
2 If an ICA number or processor ID is granted an extension, and at the conclusion of the extension
period that ICA number or processor ID remains underperforming, Mastercard will back bill that ICA
number or processor ID to collect an amount equal to the total number of months that they were
underperforming during the extension period multiplied by each of the individual month’s then current
incremental monthly assessment rate.

For example, if the Comply by Date is 1 May, an extension request must be

submitted on or before 30 April. An approved request submitted in May on or after
1 May would not become effective until 1 June, and the ICA number or processor
ID is subject to a Data Integrity fee for the month of May.
Local laws or regulations

If local laws or regulations prevent a customer from complying with Mastercard
rules, mandates, or specifications, the customer may be entitled to an exemption
from a Data Integrity edit or program. A copy of the law or regulation must be
provided to Mastercard, along with an English translation if written in any other
language. Mastercard can require the customer to provide additional legal
documentation upon request.

Data Integrity assessment structure
Data Integrity assessment structure

Mastercard assesses acquirers, issuers, and processors that fall below the
threshold for any relevant edit, as indicated in Table 2: Data Integrity assessment
structure (by edit/by month).
Customers are assessed for each nonperforming edit at the ICA number or
processor ID level. The billing event appears on the customer’s statement the
month after an ICA number or processor ID is deemed nonperforming for a given
edit.
Assessments increase incrementally when the customer remains nonperforming
for an extended period of time past the comply by date.
Important: When an extension is granted, assessments are deferred, but
Mastercard continues to count the number of months a customer is
nonperforming. When the extension expires, customers that have not met the
threshold are assessed based on the number of months that have passed since the
original comply by date.
Table 2: Data Integrity assessment structure (by edit/by month)
Months
nonperforming
after comply by
date USD Reals Rupiah Euro
1 - 9 Months 2,500 8,500 33355000 2,500
10 - 18 Months 5,000 17,000 66710000 5,000
19 - 24 Months 10,000 34,000 133420000 10,000
2+ years 20,000 68,000 266840000 20,000
Billing event codes

Each edit lists the actual billing event code used when assessing Data Integrity
fees.
The billing event codes for the Data Integrity assessment structure are:

Billing event codes
Table 3: Data Integrity assessment structure billing event codes
Billing event code Billing event name Service code Service name
2DC0100 Data Integrity DC Non-Compliance
Monitoring Program Fees
2DC0200 GCO Program Data DC Non-Compliance
Quality Assessment Fees
The Data Integrity assessment structure does not apply to the GCO_Reporting
edit, any of the Acquirer Chargeback Monitoring Program edits, Issuer Chargeback
Program edits, or Digital Standards Program edits.
The billing event codes listed in Table 4 are for the GCO_Reporting edit, the Issuer
Do Not Honor edits, the Acquirer Chargeback Monitoring Program edits, the Issuer
Chargeback Program edits, and the Digital Standards Program edits. Go to
https://www.mastercardconnect.com/ > Pricing Billing and Resource Center3 for
the assessment structures associated with these program edits.
Table 4: Billing event codes
2DC0101 Data Integrity DC Non-Compliance
Monitoring Program Fees
2DC0201 GCO Data Collection DC Non-Compliance
and Compliance Fees
2DC0202 GCO Data Collection DC Non-Compliance
and Compliance Fees
2DC0300 Issuer Monitoring DC Non-Compliance
Program Fees
Noncompliance
2DC0400 Excessive Fraud DC Non-Compliance
Merchant Violation Fees
Assessment
3 For new Pricing and Billing Resource Center users, sign in to Mastercard Connect™ with your user ID
and password or passcode. Select Store from the upper ribbon on the home page, look up the Pricing
and Billing Resource Center application by searching for keyword Pricing and click Request at the
bottom right corner of the Pricing and Billing Resource Center application tile. For existing Pricing and
Billing Resource Center application users sign in to Mastercard Connect with your user ID and
password or passcode. Select My Items from the upper ribbon on the home page. Under All Items,
look up the Pricing and Billing Resource Center application.

Data Integrity Online
2DC0401 Excessive DC Non-Compliance
Chargeback Fees
Merchant Violation
Assessment
2DC0402 High Excessive DC Non-Compliance
Chargeback Fees
Merchant Violation
Assessment
2DC04034 Excessive DC Non-Compliance
Chargeback Fees
Merchant Issuer
Recovery Assessment
2DC0500 Digital Minimum DC Non-Compliance
Standards Program Fees
Data Integrity Online

Data Integrity Online is a user-friendly dashboard where customers can view their
comprehensive performance status, access our suite of reports, manage extension
requests, and more. The application is available free of charge on Mastercard
Connect.
While there is no limit to the number of users a customer can register for the tool,
it is mandatory that at least one user is registered for each ICA number or
processor ID operating on the Mastercard Network. Registered users receive
important Data Integrity communications, including notifications of
nonperformance.
Register for Data Integrity Online
Procedure
1. Navigate to www.mastercardconnect.com.
2. Log in using your user ID and security information.
3. Select Store.
4. Select Data Integrity Online.
5. Select Add to Cart.
4 MIDs identified in High Excessive Chargeback Merchant (HECM) month four or greater are assessed
an additional issuer recovery fee at EUR/USD 5 for each chargeback for all chargebacks over 300
during the violation month. The issuer recovery fee is credited to the impacted issuers, on a prorated
basis.

Access the application
6. Enter ICA number or processor ID in the form, click Submit.

Users may be required to contact the security administrator for the ICA
number or processor ID for approval prior to obtaining final approval by
Mastercard.
NOTE: Notifications are sent to the System Administrator for ICA numbers and
processor IDs that do not have a registered user in Data Integrity Online.
Access the application

Once your access has been approved, Data Integrity Online appears on the
Mastercard Connect home screen under My Items.
Figure 2: My Items
View your institution’s data
Procedure
1. Select your ICA number or processor ID from the list to view programs relevant
to your institution.
A green check mark indicates that the ICA number/processor ID is at or above
the threshold with all edits under the program. A red exclamation point
indicates at least one instance of nonperformance. Click the program tile to
view the details for each edit.

Add new customers to your Data Integrity Online profile
By default, only the tiles for nonperforming edits appear on your dashboard.
2. Click Show all Edits for a complete view.
Each edit tile displays basic information about the edit, such as the threshold,
the comply by date (if below the threshold), and your ICA number’s and
processor ID’s current status. Additionally, you can run reports or manage
extension requests directly from the tile. For more information on requesting an
extension, see the “Data Integrity extensions” section.
Add new customers to your Data Integrity Online profile
Procedure
1. Navigate to www.mastercardconnect.com.
2. Log in using your user ID and security information.
3. Click Store.
4. Click Data Integrity Online.
5. Click Manage Subscription.
6. In your profile, enter the additional ICA numbers or processor IDs.
NOTE: Contact the security administrator at the ICA number or processor ID for
approval prior to receiving final approval from Mastercard.

Data Integrity Online edit reports
Data Integrity Online edit reports

From the edit tile, Select Report to View, select a report from the list of the
available reports for the edit. Reports can be exported as needed.
History Report: This report provides a complete history of how an ICA number or
processor ID has performed within a given Data Integrity program (for example,
Acquiring Authorization Dual Message). Data is provided for each edit in the
program over the past three years.
Edit Summary Report: This report provides a snapshot view of an ICA number's or
processor ID's status for all edits within a given program. Data is displayed for the
most recent month and includes the following categories:
• Total Errors
• Edited Count (number of edited transactions)
• DI Rate % (Compliance Rate)
• Billing Event Number
• Compliance Issues (Yes/No)
• Comply By Date
Transaction Samples Report: This report provides customers access to the data
element, subelement, and subfield levels to better understand where errors are
occurring in a transaction. Samples can be provided for a period of up to five days
and as many as 4,000 transactions. If a customer has more than 4,000 errors in the
selected period, this report provides a sampling of the data. It is important to note
that this report does not display real-time information. There is typically a 3-5 day
delay from when a transaction is on the Mastercard Network before it is available
on the transaction samples report.
Top Error Report: This report is exclusive to acquirers and provides a list of top
merchants where the most errors occurred in the last week of the prior month.
Daily Compliance Report: This report provides the daily compliance for a given edit
up to 36 days. Using this report, customers see near immediate impact to any
changes or adjustments they make. Data includes the following categories:
• Processing Day and Date
• Edit Name
• Transaction Count
• Error Count
• Daily Compliance % (Compliance Rate)
Click view samples from the Daily Compliance Report to see transaction samples
for a particular day or period without having to return to the edit tile to choose a
new report.

Data Integrity Online Reporting
Data Integrity Online Reporting
From the dashboard, select the Reporting tab in the upper right section of the
screen. Some additional edit reports and online tools can be accessed from this
section.
Full Month Top Error Report: This report is exclusive to acquirers and provides a list
of top merchants where the most errors occurred during a given month.
Once selected, the Full Month Top Error Report offers parameters for data
selection. For best results, select only one ICA number, one program, and one edit
to decrease the report creation time.
Accepted City Names: The Accepted City Names tool allows the user to select a
country and enter a postal code to determine accepted values for the city name.
Data Integrity Online manuals and guides

Reference material for Data Integrity, as well as other useful documents that
pertain to data and transaction types that are monitored by Data Integrity can be
accessed directly from the Data Integrity Online application as needed.
From the Help option, select Manuals and Guides from the list. Manuals and
Guides opens on the Data Integrity Online™ dashboard.

Contact us
Figure 3: Manuals and Guides
This information is also available on Mastercard Connect > Technical Resource

Center (TRC) .
Contact us
For questions or comments about the Data Integrity Monitoring Program, send an
email to ps_data_integrity@mastercard.com.

Acquirer Authorization Dual Message System Edits (0100)
Chapter 2 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).
Retired edits...........................................................................................................................................................27
Edit 1 ADD_DATA..................................................................................................................................................27
Edit 2 AFD..............................................................................................................................................................28
Edit 3 Magstripe....................................................................................................................................................29
Edit 4 Date_Time.................................................................................................................................................. 31
Edit 5 Cntry 2........................................................................................................................................................ 31
Edit 6 DE 43...........................................................................................................................................................33
Edit 7 INV_STATE..................................................................................................................................................34
Edit 8 TermPOS.....................................................................................................................................................35
Edit 9 POS Cnd......................................................................................................................................................38
Edit 10 Ecom..........................................................................................................................................................38
Edit 11 A_PF_ID.....................................................................................................................................................40
Edit 12 Pure Magstripe ATM 0100.....................................................................................................................41
Edit 13 Pure Magstripe POS 0100.....................................................................................................................42
Edit 15 INC_MAGSTRIPE_0100..........................................................................................................................42
Edit 16 AUTH_UNDEFINED_0100..................................................................................................................... 43
Edit 17 AUTH_PREAUTH_0100.......................................................................................................................... 44
Edit 18 AFD_MAND_PRE_AUTH.........................................................................................................................45
Edit 20 ABU ACQ.................................................................................................................................................. 46
Edit 23 DS TRAN ID FOR AUTH TRAN.............................................................................................................. 47
Edit 24 Contactless Terminal..............................................................................................................................48
Edit 25 ACQ_SKIP_EXEMPT_FLAG....................................................................................................................49
Edit 27 DSRP Cryptogram Placement_0100...................................................................................................51
Edit 28 TTI Monitoring 0100...............................................................................................................................52
Edit 29 Funding Transactions 0100...................................................................................................................53
Edit 31 MIT Recurring Trace ID Usage...............................................................................................................54
Edit 32 Gambling Authorization 0100..............................................................................................................55
Edit 33 Software MPOS 0100............................................................................................................................56

Retired edits
Retired edits
Edit 14 MERCHANT_AAV_UNIQUE (Retired from active monitoring)

Edit 19 INVALID_PRE_AUTH (Retired from active monitoring)
Edit 21 Recurring COF Monitoring (0100)
Edit 22 Protocol Version Rate Edit (Retired from active monitoring)
Edit 26 (Open)
Edit 1 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 nonperforming when 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 82 (Address Verification Service Request)
• Subelement 90 (Lodging and Auto Rental Indicator)
• Subelement 95 (Mastercard Promotion Code)
Monitoring start date: Prior to 1 December 2006

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

Edit 2 AFD
Edit 2 AFD
Edit Number 2
Edit Title AFD
Name AFD
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 transaction is considered nonperforming when any of the following
subedits apply:
a. 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)
b. In the U.S. and Europe Regions only, when 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 U.S. only, when both of the following are true:

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

Edit 3 Magstripe
Edit Number 2
d. In the U.S. only, when 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 in the
Authorization/Advice/0120.
e. In the U.S. only, when 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.
Exclusions: Transactions with DE 61, subfield 7 (POS Transaction Status)
equal to 8 (Account Status Inquiry Service [ASI]) are not monitored
under this edit.

Baseline/ Europe and United States Baseline: 1,000 AFD transactions
Threshold Asia/Pacific, Canada, Latin America and the Caribbean, Middle East/
Africa Baseline: 100 AFD transactions
Threshold: Customers with more than 1,000,000 authorization requests
Customers with 20,000 to 1,000,000 authorization requests are subject
to a threshold of 97%.
Reference Customer Interface Specification, Quick Reference Booklet
Edit 3 Magstripe
Edit Number 3
Edit Title Magnetic Stripe Track Data (0100)
Name MAG_STRIPE
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 3 Magstripe
Edit Number 3
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 nonperforming when 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
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)
e. All of the following are true:

• DE 22 is 80, 90, or 91
• 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
• DE 48 (Additional Data – Private Use), character 1 (TCC) is T

a threshold of 97%.

Edit 4 Date_Time
Edit 4 Date_Time
Edit Number 4
Edit Title Network Date and Time
Name DATE_TIME
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 nonperforming when 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).
Time must be submitted in UTC. Banknet time is automatically converted
from St. Louis, Missouri time to UTC for comparison purposes. However,
the Transaction Sample report on Data Integrity Online displays values in
St. Louis, Missouri, USA time.
Monitoring start date: 1 October 2011

a threshold of 97%.
Edit 5 Cntry 2
Edit Number 5
Edit Title Country Code or Postal Code Verification (0100)
Name CNTRY2
Region(s) Global

Edit 5 Cntry 2
Edit Number 5
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.
subedits apply:
a. DE 61, subfield 13 (POS Country Code) is not present or is not a valid
country code (Global)
b. DE 61, subfield 13 is 840 (USA) and DE 61, subfield 14 (POS Postal
Code) is not present or is not a valid U.S. 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 CHE, CRI, DNK, ISR, KOR, KWT, NOR, NZL, PHL,
PRI, THA, TUR, TWN or VEN and DE 61 subfield 14 contains “unknown” or
is not present
g. DE 43, subfield 5 is AFG, ALB, ARG, AUT, BEL, BRA, CHE, COL, CZE,
FIN, FRA, GBR, GRC, HRV, HUN, IND, ITA, JPN, MYS, NLD, POL, RUS,
SGP, SWE, UKR or ZAF and DE 61, subfield 14 contains “unknown” or is
not present or is not in the correct format. Exclusions: Airline
transactions MCC in DE 18 is 3000-3350 or 4511 and 6011 (ATM)
Exclusions: All subedits exclude transactions with MCC 4784 (Bridge and
road fees, tolls)
NOTE: In DE 43, subfield 5 is the contents of positions 38-40.
Monitoring start date: Prior to 1 December 2006, 1 February 2021 for

new countries in subedits f and g
a threshold of 97%.
Reference Customer Interface Specification, Quick Reference Booklet, AN 4589 Data

Integrity Monitoring Program: Updates to Existing Edits for Global Address
Standardization

Edit 6 DE 43
Edit 6 DE 43
Edit Number 6
Edit Title DE 43 - Card Acceptor Name and Location (0100)
Name DE 43
Region(s) Global
Description This edit monitors DE 43 (Card Acceptor Name/Location ) to ensure that
all necessary values are present and properly formatted.
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. Such as, ABCDEF
f. The following fields do not represent a valid combination for USA:
• 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:
• All subedits exclude transactions with MCC 4784 (Bridge and road
fees, tolls)
• 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.

Edit 7 INV_STATE
Edit Number 6
Baseline/ Baseline: 20,000 authorization requests to be monitored
a threshold of 97%.
Reference Customer Interface Specification, Quick Reference Booklet
Edit 7 INV_STATE
Edit Number 7
Edit Title Invalid State
Name INV_STATE
Region(s) United States and all 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 (USA).
Edit Criteria A transaction is considered nonperforming when 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
road fees, tolls)
NOTE: On non-ATM transactions the state code must be left justified.

a threshold of 97%.

Edit 8 TermPOS
Edit Number 7
Edit 8 TermPOS
Edit Number 8
Edit Title Terminal POS Processing Fields (0100)
Name TermPOS
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).
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 MCCs 6011 (ATM), 4111 (Transportation – Suburban
and Local Commuter Passenger), 4131 (Bus Lines), and 4784 (Bridge and
road fees, tolls)

Edit 8 TermPOS
Edit Number 8
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 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
Identity Check-AAV or DSRP cryptogram in UCAF)
– 82 (PAN Auto Entry via Server)
Exclusions: Subedit d excludes transactions with MCC 5542 (Fuel
Dispenser, Automated)
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®5 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)
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])
• 5 (Cardholder not present [Electronic order])
5 EMV is a registered trademark or trademark of EMVCo LLC in the United States and other countries.
For more information visit: www.emvco.com.

Edit 8 TermPOS
Edit Number 8
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)
• DE 61, subfield 10 is 0 (Not a CAT Transaction), and DE22, subfield 1
is not 10 (credential on file)
i. DE 61, subfield 5 is 1 and DE 22, subfield 1 is any of the following:

• 02 (PAN auto-entry via magnetic stripe-track data is not required OR
the acquirer is not qualified to submit magnetic stripe transactions, so
Mastercard replaced value 90 or 91 with value 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)
• 90 (PAN auto-entry via magnetic stripe the full track data has been
• 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)
j. DE 61, subfield 11 is 9 (Terminal supports EMV contact chip input only)

and DE 22 subfield 1 is not 05
a threshold of 97%.

Edit 9 POS Cnd
Edit 9 POS Cnd
Edit Number 9
Edit Title POS Condition Codes (0100)
Name POS_CND
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 nonperforming when 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 10 (Cardholder-Activated Terminal Level)
• Subfield 11 (POS Card Data Terminal Input Capability)

a threshold of 97%.
Edit 10 Ecom
Edit Number 10
Edit Title Electronic Commerce Processing Fields

Edit 10 Ecom
Edit Number 10
Name ECOM
Region(s) Global
Description This edit monitors electronic commerce processing fields to ensure they
are populated accurately.
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 Identity
Check-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
Exclusions: Transactions where DE 48, subelement 77 (Transaction Type
Identifier) values are populated with C67 (Mastercard Merchant
Presented QR) or C68 (Mastercard Merchant Presented QR Refund) are
excluded from all subedits listed above.
Monitoring start date: Prior to 1 December 2006, 1 January 2019 for

subedit C

Edit 11 A_PF_ID
Edit Number 10
Baseline/ Baseline: 25 e-commerce transactions
a threshold of 97%.
Reference Customer Interface Specification, AN 2288 Data Integrity Monitoring

Program - New Edits to Monitor Use and Acceptance of Credential-On-File
Indicator
Edit 11 A_PF_ID
Edit Number 11
Edit Title Authorization Payment Facilitator ID
Name A_PF_ID
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.
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
Monitoring start date: 1 May 2015

Edit 12 Pure Magstripe ATM 0100
Edit Number 11
a threshold of 97%.
Edit 12 Pure Magstripe ATM 0100
Edit Number 12
Edit Title Pure Magnetic Stripe – ATM (0100)
Name Pure Magstripe (Fallback) ATM 0100
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 nonperforming 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)
Monitoring start date: 1 January 2016

Baseline/ Baseline: 1 ATM transaction
Threshold Europe Threshold: 20 failures
Non-Europe Threshold: 1,000 failures
Reference Customer Interface Specification, M/Chip Requirements for Contact and

Contactless

Edit 13 Pure Magstripe POS 0100
Edit 13 Pure Magstripe POS 0100
Edit Number 13
Edit Title Pure Magnetic Stripe – POS (0100)
Name Pure Magstripe (Fallback) POS 0100
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).
true:
• DE 18 (Merchant Type) is not 6011 (ATM), 4784 (Bridge and road fees,
tolls), or 7523 (Automobile Parking Lots and Garages)
• DE 48, subelement 74 is 90C (Chip Fallback Transaction Downgrade
Process Completed Successfully)

Baseline/ Baseline: 1 POS transaction

Contactless
Edit 15 INC_MAGSTRIPE_0100
Edit Number 15
Edit Title Inconsistent Magnetic Stripe (0100)
Name INC_MAGSTRIPE_0100

Edit 16 AUTH_UNDEFINED_0100
Edit Number 15
Region(s) Global
Description This edit monitors transactions performed with chip cards at chip
capable terminals that are submitted as magnetic stripe.
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
– 9 (Terminal supports EMV contact chip input only)
Exclusions: Transactions with MCCs 4784 (Bridge and road fees, tolls)
and 7523 (Automobile Parking Lots and Garages) are not monitored
under this edit.

Baseline/ Baseline: 1 magnetic stripe transaction
Threshold United States Threshold: 15,000 failures
Non-United States Threshold: 1,000 failures

Contactless
Edit 16 AUTH_UNDEFINED_0100
Edit Number 16
Edit Title Undefined Authorization Requests
Name AUTH_UNDEFINED_0100

Edit 17 AUTH_PREAUTH_0100
Edit Number 16
Region(s) Asia/Pacific, 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 nonperforming when 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
Monitoring start date: 1 June 2017

Baseline/ Baseline: 100,000 or more domestic transactions
Threshold Threshold: 50%
Edit 17 AUTH_PREAUTH_0100
Edit Number 17
Edit Title Preauthorized Domestic Purchases
Name AUTH_PREAUTH_0100
Region(s) Asia/Pacific, 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 18 AFD_MAND_PRE_AUTH
Edit Number 17
criteria:
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)
• DE 61 (POS Data) subfield 7 (POS Transaction Status) is 4
(Preauthorized Request)
Customers are considered nonperforming when preauthorized requests
account for 25% or more of all approved domestic purchase
transactions.
Exclusions: This edit excludes e-commerce transactions (POS entry mode
of 81 in DE 22, subfield 1). Additionally, transactions are excluded when
both DE 22, subfield 1 = 10 (COF) and DE 61, subfield 10 = 6 (Authorized
Level 6 CAT: Electronic commerce). The following MCCs are excluded
from this edit: 3000 – 3350, 3351 – 3500, 3501 – 3999, 4121, 4511, 4722,
5499, 5541, 5542, 5552, 5812, 5813, 5814, 5943, 5964, 5965, 5968, 5969,
5983, 6513, 7011, 7033, 7230, 7297, 7298, 7394, 7512, 7513, 7542, 7997

Baseline/ Baseline: 10,000 domestic authorization requests
Threshold Threshold: 76% of domestic authorization requests are not preauthorized
purchase transactions
Edit 18 AFD_MAND_PRE_AUTH
Edit Number 18
Edit Title Preauthorized Maestro AFD
Name AFD_MAND_PRE_AUTH
Region(s) Europe

Edit 20 ABU ACQ
Edit Number 18
Description This edit monitors Maestro Automated Fuel Dispenser (AFD)
transactions to ensure that the authorization request was preauthorized.
Edit Criteria A transaction is considered nonperforming when DE 18 (Merchant Type)
is 5542 (Fuel Dispenser, Automated) and DE 61 (POS Data) subfield 7
(POS Transaction Status) is not 4 (Preauthorized Request).
Exclusions: Transactions with DE 61, subfield 7 (POS Transaction Status)
equal to 8 (Account Status Inquiry Service [ASI]) are not monitored
under this edit.
Monitoring start date: 1 April 2017

Baseline/ Baseline: 10 Maestro AFD transactions
Threshold Threshold: 10 errors
Edit 20 ABU ACQ
Edit Number 20
Edit Title Automatic Billing Updater for Acquirers
Name ABU_ACQ
Region(s) Latin America and the Caribbean, Select Countries in Europe (Armenia,
Azerbaijan, Belarus, Belgium, Georgia, Germany, Gibraltar, Ireland, Italy,
Kazakhstan, Kyrgyzstan, Liechtenstein, Luxembourg, Netherlands,
Portugal, Russian Federation, San Marino, Switzerland, Tajikistan,
Turkmenistan, United Kingdom, and Uzbekistan), Middle East/Africa
Description This edit monitors the mandatory implementation of the Automatic
Billing Updater (ABU) by acquirers submitting Credential on File (COF)
and recurring payment transactions.
Edit Criteria Customers are monitored under this edit when they have one or more
recurring payment or COF transaction in a given month.
An acquirer is considered nonperforming when ABU is not implemented
for ICA numbers submitting COF or recurring payment transactions.
NOTE: All ICA numbers sharing a parent ICA number are considered
compliant if any ICA number in the family has implemented ABU.

Edit 23 DS TRAN ID FOR AUTH TRAN
Edit Number 20
Monitoring start date: 1 October 2018 for Latin America and the
Caribbean, 1 August 2019 for Armenia, Azerbaijan, Belarus, Belgium,
Georgia, Italy, Kazakhstan, Kyrgyzstan, Luxembourg, Netherlands,
Russian Federation, San Marino, Tajikistan, Turkmenistan, and
Uzbekistan, 1 May 2020 for Andorra, Germany, Gibraltar, Ireland,
Liechtenstein, Portugal, Switzerland, and United Kingdom, and 1
November 2020 for Middle East/Africa
Baseline/ Baseline: 1 recurring payment or COF transaction
Threshold
Reference Automatic Billing Updater Reference Guide, Transaction Processing Rules,
AN 2171—Data Integrity Monitoring Program—New Edit for the Latin,
America and the Caribbean Region, AN 2712—Data Integrity Monitoring
Program—Select Europe Region Countries to be Monitored for Compliance
with Acquirer ABU Mandate, AN 3888—Data Integrity Monitoring Program
—Acquirers and Issuers in Select Europe Region Countries to be Monitored
for Compliance with the ABU Mandate, AN 4310 Data Integrity Monitoring
Program, Middle East/Africa Region Acquirers to be Monitored for
Compliance with ABU Mandate
Edit 23 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
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 24 Contactless Terminal
Edit Number 23
true:
• DE 48 (Additional Data – Private Use), subelement 42 (Electronic
Commerce Indicators) subfield 1 (Electronic Commerce Security Level
Indicator and UCAF Collection Indicator) is 211, 212, 216 or 217
• DE 48, subelement 43 (3-D Secure SPA Accountholder Authentication
Value [AAV]) has a leading indicator of ‘k’ (SPA 2)
• 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.
Exclusions: Prepaid Product Codes

Baseline/ Baseline: 1,000 EMV 3DS transactions
Edit 24 Contactless Terminal
Edit Number 24
Edit Title Contactless Terminal
Name Contactless Terminal
Region(s) Asia/Pacific (excluding Japan), Middle East/Africa
Description This edit monitors the percentage of merchant terminals under an
acquiring ICA number identified as contactless capable.

Edit 25 ACQ_SKIP_EXEMPT_FLAG
Edit Number 24
Edit Criteria An acquirer is considered nonperforming when the percentage of
merchant terminals identified as contactless capable do not meet the
thresholds for that acquirer’s region.
Contactless capability is identified by a value of 3 (Contactless EMV/Chip
[Proximity Chip]) in DE 61 (POS Data), subfield 11 (Terminal Input
Capability Indicator).
Exclusions: ATM Terminals
NOTE: This edit is not eligible for extensions.

Baseline/ Baseline: 1,000 face-to-face transactions
Threshold Threshold:
Asia/Pacific:
• Effective 1 October 2022: 40%
Middle East/Africa:

Program New Edit to Monitor Compliance in the Asia/Pacific and Middle
East/Africa Regions with the Contactless Terminal Mandate
Edit Number 25
Edit Title Acquirer Skipping Exemption Flag in Auth
Name ACQ_SKIP_EXEMPT_FLAG

Edit Number 25
Region(s) Select countries in Europe (Aland Islands, Austria, Belgium, Bulgaria,
Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, France,
French Guiana, Germany, Gibraltar, Greece, Guadeloupe, Hungary,
Iceland, Ireland, Italy, Svalbard and Jan Mayen, Latvia, Liechtenstein,
Lithuania, Luxembourg, Malta, Martinique, Mayotte, Netherlands,
Norway, Poland, Portugal, Reunion, Romania, Slovakia, Slovenia, Spain,
Sweden, and United Kingdom)
Description This edit monitors European PSD2 acquirers that are skipping 3DS and
not utilizing the exemption flag in authorization DE 48, subelement 22
(Multi-Purpose Merchant Indicator), subfield 01 (Low-Risk Merchant
Indicator) for e-commerce purchase and recurring transactions
monitored under PSD2 regulation.
criteria:
• DE 61 (Point-of-Service [POS] Data), subfield 4 (POS Cardholder
Presence) has a value of 5 (electronic order) and DE 61, subfield 10
(Cardholder-Activated Terminal [CAT] Level) has a value of 6
(Authorized Level 6 CAT: Electronic Commerce) or DE 61, subfield 4
has a value of 4 (Standing Order/ Recurring Transactions).
• DE 48, subelement 42 (Electronic Commerce Indicators), subfield 1
(Electronic Commerce Security Level Indicator and UCAF Collection
Indicator) has a value of 210, or 213, or 214, or 216, or 217.
• Both issuer and acquirer are in one of the listed countries.
A transaction is considered nonperforming when the following is true:
• DE 48, subelement 22 (Multi-Purpose Merchant Indicator), subfield 1
(Low- Risk Merchant Indicator) is not present.
Exclusions:
• Prepaid product codes
• DE 61, subfield 7 (POS Transaction Status) equal to 8 (Account
Status Inquiry Service [ASI])

Baseline/ Baseline: 1,000 e-commerce/recurring transactions
Reference Authentication Guide for Europe, Mastercard Rules, AN 4309 Data

Integrity Monitoring Program, New Edits for Mastercard Identity Check,
AN 7157 Revised Criteria for Data Integrity Monitoring Program Acquirer
Skipping Exemption Flag in Auth Edit for Select Countries in the Europe
Region

Edit 27 DSRP Cryptogram Placement_0100
Edit Number 27
Edit Title DSRP Cryptogram Placement_0100
Name DSRP Cryptogram Placement_0100
Region(s) Global
Description This edit monitors the presence of the Digital Secure Remote Payment
(DSRP) Cryptogram in DE 104 (Digital Payment Data) subelement 001
(Digital Payment Cryptogram) by the acquirer for MDES and third party
tokenized electronic commerce transactions in Authorization Request/
0100 messages.
criteria:
• DE 22 (Point-of-Service [POS] Entry Mode), subfield 1 (POS Terminal
PAN Entry Mode) is any of the following:
– 10 (Credential on File)
– 82 (PAN Auto Entry via Server [issuer, acquirer, or third- party
vendor system])
A transaction is considered nonperforming when all of the following
criteria are met:
• DE 104 (Digital Payment Data) subelement 001 (Digital Payment
Cryptogram) is not present
• DE 48, subelement 43 (UCAF) is not empty and the value does not
have a Mastercard Identity Check AAV (leading indicator Mastercard
Identity Check AAV begins with j, h, or k)
Monitoring start date: 1 March 2021 and 1 December 2022 for third
party tokenized electronic commerce transactions
Baseline/ Baseline: 100 DSRP transactions
Reference Customer Interface Specification, AN 4670 New Data Integrity Monitoring

Program Edits for Digital Secure Remote Payment Cryptogram

Edit 28 TTI Monitoring 0100
Edit Number 28
Edit Title Transaction Type Identifier Monitoring 0100
Name TTI Monitoring 0100
Region(s) Global
Description This edit monitors the Transaction Type Identifier (TTI) in purchase,
purchase return, and payment transactions to help ensure acquirers
discontinue inappropriate use of TTIs and use of invalid TTIs.
Edit Criteria Transactions monitored under this edit are identified by one of the
following values in DE 3 (Processing Code), subfield 1 (Cardholder
Transaction Type Code):
• 00 (Purchase)
• 20 (Purchase Return/Refund)
• 28 (Payment Transaction)
A transaction is considered nonperforming when DE 48 (Additional Data
—Private Use), subelement 77 (Transaction Type Identifiers [TTI]) is any
of the following:
• C01 (Person-to-Person)
• C02 (Mastercard rebate)
• C05 (Payment Transaction for a reason other than those defined in
values C01-C04) or
• the value in DE 48, SE 77 is not a valid TTI per the Customer Interface
Specification manual
NOTE: The TTI value of C02 (Mastercard Rebate) is for Mastercard use
only as stated in AN 4462 Revised Standards for the Sunset of Several
Legacy Transaction Type Identifiers.
Monitoring start date: 1 July 2021

Baseline/ Baseline: 1 dual message (0100) purchase, purchase return, or payment
Threshold transaction
Threshold: 100 errors

Program: New Edits for Transaction Type Identification

Edit 29 Funding Transactions 0100
Edit Number 29
Edit Title Funding Transactions 0100
Name Funding Transactions 0100
Region(s) Global
Description This edit monitors acquirer funding transactions to ensure that acquirers
are sending appropriate MCC and transaction type identifier (TTI)
values, and that the funding transaction includes key required reference
data in DE 108 (Additional Transaction Reference Data) of Authorization
Request/0100 messages.
criteria:
Code) is 00 (Purchase) and
• DE 18 (Merchant Type [MCC]) is any of the following
– 4829 (Money Transfer)
– 6538 (Funding Transactions for MoneySend)
– 6540 (Funding Transactions)
Transactions are considered nonperforming when either of the following

subedits are true:
a. DE 48 (Additional Data—Private Use), subfield 77 (Transaction Type
Identifier) is blank or null
b. DE 48, subfield 77 is not blank or null and DE 108 (Additional
Transaction Reference Data), subelement 1 (Receiver/Recipient Data),
subfield 1 (Receiver/Recipient First Name) and subfield 3 (Receiver/
Recipient Last Name) are not populated
Exclusions:
• DE 61 (Point-of-Service [POS] Data), subfield 7 (POS Transaction
Status), value 8 (Account Status Inquiry Service [ASI])
Monitoring start date: 1 November 2022

Baseline/ Baseline: 1 funding transaction
Reference Customer Interface Specification, Mastercard MoneySend and Funding

Transactions Program Standards, AN 6410 New Data Integrity Monitoring
Program Edits for Funding Transactions

Edit 31 MIT Recurring Trace ID Usage
Edit 31 MIT Recurring Trace ID Usage
Edit Number 31
Edit Title MIT Recurring Trace ID Usage Europe
Name MIT Recurring Trace ID Usage
Region(s) Select countries in Europe (Austria, Belgium, Bulgaria, Croatia, Cyprus,
Czech Republic, Denmark, Estonia, Finland, France, Germany, Gibraltar,
Greece, Hungary, Iceland, Ireland, Italy, Latvia, Liechtenstein, Lithuania,
Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania,
San Marino, Slovakia, Slovenia, Spain, Sweden, and United Kingdom.)
Description This edit monitors for the presence of a valid Trace ID value in recurring
payment and Merchant Initiated Transactions (MIT) in the authorization
message.
criteria:
• Both acquirer and issuer need to be in one of the listed countries
• DE 48 (Additional Data—Private Use), sub-element 22 (Multi-Purpose
Merchant Indicator), subfield 01 (Low-Risk Merchant Indicator) is
– 01 (Merchant Initiated Transaction) or
– 03 (Recurring Payment)
Transactions are considered nonperforming when any of the following
are true:
• DE 61 (Point-of-Service [POS] Data), subfield 4 (POS Cardholder
Presence) is not equal to 4 (Standing order/recurring transactions) or
• DE 61, subfield 4 is equal to 4 and DE 48, subelement 63 (Trace ID)
not present or
• DE 61, subfield 4 is equal to 4 and DE 48, subelement 63 is present but
the length is less than 13 bytes, contains all zeros, or non-uppercase
alpha/numeric combinations
Monitoring start date: 1 March 2023

Baseline/ Baseline: 100 MIT or RP transactions

Edit 32 Gambling Authorization 0100
Edit 32 Gambling Authorization 0100
Edit Number 32
Edit Title Gambling Authorization 0100
Name Gambling Authorization 0100
Region(s) Global
Description This edit monitors the presence of the card validation code 2 (CVC2)
value or EMV 3-D Secure (EMV 3DS) authentication by the acquirer for
online gambling transactions in Authorization Request/0100 messages.
criteria:
Code) value is 00 (Purchase)
• DE 18 (Merchant Type) values are any of the following:
– MCC 7995 (Gambling Transactions)
– MCC 7800 (Government Owned Lottery [U.S. Region Only])
– MCC 7801 (Internet Gambling [U.S. Region Only])
– MCC 7802 (Government Licensed Horse/Dog Racing [U.S. Region
Only])
– MCC 9406 (Government Owned Lottery [global, excluding U.S.
region])
PAN Entry Mode) values are any of the following:
cryptogram in DE 55 (Integrated Circuit Card [ICC] System-
Related Data))
– 82 (PAN Auto Entry via Server [issuer, acquirer, or third-party
vendor system])

Edit 33 Software MPOS 0100
Edit Number 32
Transactions are considered nonperforming when:
• DE 48 (Additional Data: Private Use), subelement 92 (CVC 2) is not
present, and
– DE 48, subelement 42 (Electronic Commerce Indicators) subfield 1
(Electronic Commerce Security Level Indicator [SLI] UCAF
Collection Indicator) does not have a value of 212, or
– DE 61 (POS Cardholder Presence Indicator), subfield 4 (POS
Cardholder Presence) value is 4 (Recurring Payment) and DE 48,
subelement 42, subfield 1 does not have a value of 214 or 217.
Excluded countries:
Aland Islands, Albania, Andorra, Antarctica, Austria, Belgium, Bosnia and
Herzegovina, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark,
Estonia, Falkland Islands (Malvinas), Faroe Islands, Finland, France,
French Guiana, Germany, Gibraltar, Greece, Greenland, Guadeloupe,
Guernsey, Hungary, Iceland, Ireland, Isle of Man, Italy, Jersey, Kosovo,
Latvia, Liechtenstein, Lithuania, Luxembourg, Macedonia, Malta,
Martinique, Mayotte, Moldova, Monaco, Montenegro, Netherlands,
Norway, Poland, Portugal, Reunion, Romania, Saint Helena, Ascension
and Tristan Da Cunha, Saint Barthélemy, Saint Martin (French part), San
Marino, Serbia, Slovakia, Slovenia, South Georgia and the South
Sandwich Islands, Spain, Svalbard and Jan Mayen, Sweden, Switzerland,
Ukraine, United Kingdom, and Vatican City State
Monitoring start date: 1 February 2023

Baseline/ Baseline: 10 online gambling authorization transactions
Reference Customer Interface Specification, Mastercard Identity Check Program

Guide, Mastercard Rules, AN 6856 New Data Integrity Monitoring Program
Edit for Online Gambling Authorization
Edit Number 33
Edit Title Software MPOS 0100
Name Software MPOS 0100
Region(s) Global

Edit Number 33
Description This edit monitors the software mobile point-of-sale (mPOS) indicator in
Data Element (DE) 61 (Point-of-Service [POS] Data), subfield 10
(Cardholder-Activated Terminal Level) in the acquirer Authorization
Request/0100 messages to ensure proper identification is occurring.
criteria:
• DE 61, subfield 10 is 9 (mPOS Acceptance Device)
PIN Entry Mode) is not one of the following values:
– 2 (Terminal does not have PIN entry capability)
– 3 (mPOS Software-based PIN Entry Capability), or
• DE 22, subfield 2 is 2 and DE 48 (Additional Data-Private Use),
subelement 21 (Acceptance Data), subfield 01 (mPOS Acceptance
Device Type) is not 1 (Off the Shelf Mobile Device), or
• DE 22, subfield 2 is 3 (MPOS Software-based PIN Entry Capability)
and DE 48, subelement 21, subfield 01 is not one of the following
values:
– 0 (Dedicated mPOS terminal with PCI compliant dongle [with or
without keypad])
– 1
Exclusions:
• DE 22, subfield 2 is 1 (Terminal has PIN entry capability) and DE 48,
subelement 21, subfield 01 is 0
• DE 22, subfield 2 is 2 and DE 48, subelement 21, subfield 01 is 0
• DE 22, subfield 2 is 8 (Terminal has PIN entry capability but PIN pad is
not currently operative) and DE 48, subelement 21, subfield 01 is 0
• DE 61, subfield 11 (POS Card Data Terminal Input Capability
Indicator) is 9 (Terminal supports EMV contact chip input only)

Baseline/ Baseline: 300 software mPOS transactions

Contactless, AN 7011 New Data Integrity Monitoring Program Edits for
Software Mobile Point-of-Sale Indicators

Acquirer Authorization Chip Dual Message System Edits (0100)
Chapter 3 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).
Retired edits...........................................................................................................................................................59
Chip testing requirement.....................................................................................................................................59
Edit 1 AC_Missing_DE12......................................................................................................................................59
Edit 7 AC_Inv_form_DE55................................................................................................................................... 64
Edit 8 AC_Missing_EMVtags_DE55................................................................................................................... 64
Edit 9 AC_Inv_length_DE55.................................................................................................................................65
Edit 10 AC_Inv_DE61_SF11................................................................................................................................66
Edit 11 Fallback Rt ATM 0100............................................................................................................................67
Edit 12 Fallback Rt POS 0100............................................................................................................................68
Edit 14 AC_INV_EMVTAGS_DE55......................................................................................................................69
Edit 15 Contactless CVM Limits 0100..............................................................................................................70

Retired edits
Retired edits
Edit 13 AC INC Magstripe 0100 (Retired from active monitoring)
Chip testing requirement
Before sending and 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 AC_Missing_DE12
Edit Number 1
Edit Title Missing DE 12 (0100)
Name AC_Missing_DE12
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):
A transaction is considered nonperforming when DE 12 (Time, Local
Transaction) is missing.
Monitoring start date: 1 December 2014

Edit Number 1
Baseline/ Baseline: 20,000 chip transactions
Threshold Threshold: 99.85%
Reference Customer Interface Specification, AN 2301—Data Integrity Monitoring

Program—Updated Threshold on Chip Edits
Edit Number 2
Region(s) Global
local date is populated.
following values in DE 22 (POS Entry Mode), subfield 1 (POS Terminal
PAN Entry Mode):
A transaction is considered nonperforming when DE 13 (Date, Local
Transaction) is missing.



Edit Number 3
Region(s) Global
Track 2 data is populated.
following values in DE 22 (POS Entry Mode) , subfield 1 (POS Terminal
PAN Entry Mode):
A transaction is considered nonperforming when DE 35 ( Track 2 Data) is
missing.


Edit Number 4
Region(s) Global
retrieval reference number is populated.

Edit Number 4
PAN Entry Mode):
A transaction is considered nonperforming when DE 37 (Retrieval
Reference Number) is missing.


Edit Number 5
Region(s) Global
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):
transaction using data on the chip; therefore, the terminal
defaulted to the magnetic stripe-read PAN)
A transaction is considered nonperforming when DE 41 (Card
Acceptor Terminal ID) is missing.

Edit Number 5

Edit Number 6
Region(s) Global
Integrated Circuit Card [ICC] System-Related Data is
populated.Baseline/Threshold
PAN Entry Mode):
A transaction is considered nonperforming when DE 55 (ICC System-
Related Data) is missing.
Exclusions: Refund transactions



Edit 7 AC_Inv_form_DE55
Edit 7 AC_Inv_form_DE55
Edit Number 7
Edit Title DE 55 Invalid Format (0100)
Name AC_Inv_form_DE55
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).
PAN Entry Mode):
A transaction is considered nonperforming when the TLV is not
formatted in accordance with specifications outlined in M/Chip
Requirements for Contact and Contactless.
NOTE: DE 55 is not parsable.


Contactless, AN 2301—Data Integrity Monitoring Program—Updated
Threshold on Chip Edits
Edit 8 AC_Missing_EMVtags_DE55
Edit Number 8
Edit Title Missing EMV Tags (0100)
Name AC_Missing_EMVtags_DE55

Edit 9 AC_Inv_length_DE55
Edit Number 8
Region(s) Global
Description This edit monitors dual message chip transactions to ensure that all the
required EMV tags are present.
PAN Entry Mode):
A transaction is considered nonperforming when DE55 (Integrated
Circuit Card [ICC] System Related Data) is missing one or more required
EMV tags.


Edit 9 AC_Inv_length_DE55
Edit Number 9
Edit Title Invalid Length of EMV Tag (0100)
Name AC_Inv_length_DE55
Region(s) Global
Description This edit monitors dual message chip transactions to ensure that all EMV
tags are the correct length.

Edit 10 AC_Inv_DE61_SF11
Edit Number 9
PAN Entry Mode):
A transaction is considered nonperforming when 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.


Edit 10 AC_Inv_DE61_SF11
Edit Number 10
Edit Title Invalid Terminal Input Capability (0100)
Name AC_Inv_DE61_SF11
Region(s) Global
Description This edit monitors the terminal input capability to ensure that it
corresponds appropriately to the POS entry mode for chip transactions.
subedits apply:

Edit 11 Fallback Rt ATM 0100
Edit Number 10
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)
• 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

Edit Number 11
Edit Title Technical Fallback Rate – ATM Transactions (0100)
Name Fallback Rt ATM 0100
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 12 Fallback Rt POS 0100
Edit Number 11
criteria:
is
– 05 (PAN auto-entry via chip)
– 80 (Chip card at chip-capable terminal was unable to process
transaction using data on the chip)
• DE 22, subfield 1 equals 80
Exclusions: Product code MPV

Monitoring start date: 1 September 2017
Baseline/ Baseline: 1,000 failures

Contactless
Edit Number 12
Edit Title Technical Fallback Rate – POS Transactions (0100)
Name Fallback Rt POS 0100
Region(s) Global
Description This edit monitors POS transactions performed with chip cards on chip-

Edit 14 AC_INV_EMVTAGS_DE55
Edit Number 12
criteria:
• DE 18 (Merchant Type) is not 6011 (ATM)
is
Transactions are considered nonperforming when DE 22, subfield 1
equals 80.
Exclusions:
• MCCs 4784 (Bridge and road fees, tolls) and 7523 (Automobile
parking lots and garages)
• Product code MPV


Contactless
Edit 14 AC_INV_EMVTAGS_DE55
Edit Number 14
Edit Title Invalid EMV Tags (0100)
Name AC_INV_EMVTAGS_DE55
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.
subedits apply:

Edit 15 Contactless CVM Limits 0100
Edit Number 14
a. Tag 9F27 (Cryptogram Information Data) is not any of the following:
• 0x
• 4x
• 8x
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.


Edit Number 15
Edit Title Contactless Cardholder Verification Method Limits 0100
Name Contactless CVM Limits 0100

Edit Number 15
Region(s) Asia/Pacific, Latin America and the Caribbean, and select countries in
Middle East/Africa (Angola, Bahrain, Botswana, Egypt, Ghana, Jordan,
Kenya, Kuwait, Lebanon, Lesotho, Malawi, Mauritius, Morocco,
Mozambique, Namibia, Nigeria, Oman, Qatar, Saudi Arabia, Seychelles,
South Africa, Swaziland, Tanzania, Uganda, United Arab Emirates, and
Zambia)
Description This edit monitors merchant terminals to ensure that they are accurately
setting the CVM limits to Mastercard published values.
criteria:
• Message Type Identifier is 0100 (Authorization Request)
• DE 22 (Point of Service [POS] Entry Mode), subfield 1 (POS Terminal
PAN Entry Mode) value is 07 (PAN auto-entry via contactless M/Chip)
• DE 55 (Integrated Circuit Card [ICC] System-Related Data) tag value
is 9F1A (Terminal Country Code)

subedits are true:
a. Transaction amount in DE 4 (Amount, Transaction) is less than or
equal to the CVM limit per country, and DE 55 is present and tag 9F34
(Cardholder Verification Method [CVM] Results) values do not start with
00011111 or 00111111; or
b. Transaction amount in DE 4 (or DE 54, subfield 4 for DCC) is greater
than the CVM limit per country, and DE 55 is present and tag 9F34
values start with 00011111 or 00111111
NOTE: DCC is determined when DE 54 (Additional Amounts), subfield 2

(Account Type) value is 58 (POI Amount (also known as Dynamic
Currency Conversion [DCC])
Exclusions:
• DE 3 (Processing Code), Subfield 1 Cardholder Transaction Type Code
value 09 (Purchase with Cash Back)
• DE 18 (Merchant Type [MCC]) values 4784, 4829, 5542, 6010, 6011,
6050, 6051, 6540, 7802, 7995, and 9405

Edit Number 15
Baseline/ Baseline: 1,000 contactless POS transactions
The performance rating percentage is not exclusive per subedit (a or b)
and if customer fails a or b on a transaction it is counted as a failure and
adds up against total failures.
Reference Chargeback Guide, M/Chip Requirements for Contact and Contactless

(RA486.20), Transaction Processing Rules, section 3.4 (Mastercard
Cardholder Verification Requirements) and section 4.4 (Contactless
Transactions at POS Terminals), AN 5957 Data Integrity Monitoring
Program: New Edits for Cardholder Verification Method Limits for Select
Regions

Acquirer Clearing Dual Message System Edits (1240)
Chapter 4 Acquirer Clearing Dual Message System Edits

(1240)
1240/First Presentment message. In the Data Integrity Online application, the program
name appears in its abbreviated form, Acq Clear Dual Msg (1240).
Retired edits...........................................................................................................................................................74
Edit 1 MCC.............................................................................................................................................................74
Edit 2 MERCHANT ID...........................................................................................................................................75
Edit 3 INV DE43.................................................................................................................................................... 76
Edit 4 CNTRY GEO................................................................................................................................................77
Edit 5 INV_STREET............................................................................................................................................... 79
Edit 6 INV ADDR....................................................................................................................................................80
Edit 7 TERM POS.................................................................................................................................................. 81
Edit 8 TRACE_ID....................................................................................................................................................82
Edit 9 POST_CD_MATCH.....................................................................................................................................83
Edit 10 POS_AUTH............................................................................................................................................... 84
Edit 11 C_PF_ID.....................................................................................................................................................86
Edit 13 MCC_MATCH........................................................................................................................................... 87
Edit 14 MERCH_DBA_NAME_MATCH...............................................................................................................88
Edit 16 TERM_INPUT_MATCH............................................................................................................................ 89
Edit 17 AAV_RATE_CLEAR_TRAN...................................................................................................................... 91
Edit 18 DS_TRAN_ID_CLEAR_TRANS............................................................................................................... 91
Edit 20 Cross Border TC28 Force Post 1240................................................................................................... 92
Edit 21 High Risk MCC Mismatch...................................................................................................................... 93
Edit 22 POI Currency Conversion 1240.............................................................................................................94

Retired edits
Retired edits
Edit 12 POST_SLI_MATCH (Retired from active monitoring)

Edit 15 MERCHANT_ID_MATCH (Retired from active monitoring)
Edit 19 (Open)
Edit 1 MCC
Edit Number 1
Edit Title Merchant Category Code
Name MCC
Region(s) Global
Description This edit monitors the invalid use of card acceptor business code/
merchant category code (MCC).
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

Edit 2 MERCHANT ID
Edit Number 1
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
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
Reference IPM Clearing Formats, Quick Reference Booklet
Edit 2 MERCHANT ID
Edit Number 2
Edit Title Merchant ID
Name MERCHANT ID
Region(s) Global
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.

Edit 3 INV DE43
Edit Number 2
Edit Criteria Customers are considered nonperforming when 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)
Exclusions:
• Transactions with PDS 0208 (Additional Merchant Data), subfield 1
(Payment Facilitator ID) populated.
NOTE: This edit only applies to face-to-face transactions.

Reference Global Clearing Management System Reference Manual, IPM Clearing

Formats
Edit 3 INV DE43
Edit Number 3
Edit Title Invalid Values DE 43
Name INV DE43
Region(s) Global
Description This edit monitors the values in DE 43 (Card Acceptor Name/Location) to
ensure they are valid and properly formatted.
subedits apply:
a. DE 43, subfield 1 is a street address

Edit 4 CNTRY GEO
Edit Number 3
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”
Exclusions:
• Transactions with MCC 5511 (Automobile and Truck Dealers—Sales,
Service, Repairs, Parts, and Leasing) are excluded from subedit e.
• Transactions with MCC 4784 (Bridge and road fees, tolls) are excluded
from all subedits.

Reference Global Clearing Management System Reference Manual, IPM Clearing

Formats
Edit 4 CNTRY GEO
Edit Number 4
Edit Title Country Code or Postal Code Verification (1240)
Name CNTRY GEO

Edit 4 CNTRY GEO
Edit Number 4
Region(s) This edit applies to the following countries: Afghanistan, Albania,
Argentina, Australia, Austria, Belgium, Brazil, Canada, Colombia, Costa
Rica, Croatia, Czech Republic, Denmark, Finland, France, Germany,
Greece, Hungary, India, Israel, Italy, Japan, Korea, Kuwait, Malaysia,
Netherlands, New Zealand, Norway, Philippines, Poland, Puerto Rico,
Russian Federation, Singapore, South Africa, Sweden, Switzerland,
Taiwan, Thailand, Turkey, Ukraine, United Kingdom, United States,
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.
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 CHE, CRI, DNK, ISR, KOR, KWT, NOR, NZL, PHL,
PRI, THA, TUR, TWN, or VEN
f. DE 43, subfield 6 is AFG, ALB, ARG, AUT, BEL, BRA, CHE, COL, CZE,
transactions MCC in DE 26 is 3000-3350 or 4511
road fees, tolls)
Monitoring start date: 1 January 2005, 1 February 2021 for new
countries in subedits e and f

Edit 5 INV_STREET
Edit Number 4
Reference IPM Clearing Formats, AN 4589 Data Integrity Monitoring Program:
Updates to Existing Edits for Global Address Standardization
Edit 5 INV_STREET
Edit Number 5
Edit Title Invalid Street Address (1240)
Name INV_STREET
Region(s) Global
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.
subedits apply:
a. 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 U.S. only, DE 43, subfield 2 is missing the street number or
street name
Exception: A value of “RR” is permitted in Canada.
Subedit a. applies only to the following countries: Australia, Brazil,
Canada, China, France, Germany, India, Italy, Japan, Mexico, Poland,
Russian Federation, Spain, United Kingdom and United States.
b. DE 43, subfield 1 matches DE 43, subfield 2 (Spaces, character case

and special characters are removed prior to matching.)
road fees, tolls)
Monitoring start date: 1 February 2010, 1 February 2021 for subedit b

Edit 6 INV ADDR
Edit Number 5
Reference IPM Clearing Formats, AN 4589 Data Integrity Monitoring Program:

Updates to Existing Edits for Global Address Standardization
Edit 6 INV ADDR
Edit Number 6
Edit Title Invalid City/Address
Name INV ADDR
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.
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
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
road fees, tolls)

Edit 7 TERM POS
Edit Number 6
Reference IPM Clearing Formats
Edit 7 TERM POS
Edit Number 7
Edit Title Terminal POS Input Capability (1240)
Name TERM POS
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.
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)

Edit 8 TRACE_ID
Edit Number 7
Edit 8 TRACE_ID
Edit Number 8
Edit Title Trace ID Match
Name TRACE_ID
Region(s) Global
Description This edit monitors the Trace ID value in the First Presentment/1240 to
ensure it is populated with the same values contained in the related the
Authorization Request Response/0110 message.
Edit Criteria A transaction is considered nonperforming when DE 63 (Transaction Life
Cycle ID), subfield 2 (Trace ID) does not match the data in DE 63
(Network Data) and DE 15 (Settlement Date) of the authorization
response.
NOTE: The Trace ID consists of the network reference number followed by

the network date. For each transaction authorized via the network
(“online-authorized transactions”), IPM DE 63 subfield 2 (Trace ID) of the
First Presentment/1240 message must be populated with the same
values contained in the related authorization message.
Exclusions: Transactions where online authorization is not requested or

required, such as offline-authorized chip-read transactions, credit
(purchase return) transactions, payment transactions, and Collection
Only transactions.

Edit 9 POST_CD_MATCH
Edit Number 8
Edit 9 POST_CD_MATCH
Edit Number 9
Edit Title Postal Code Match
Name POST_CD_MATCH
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 nonperforming when 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.

Reference Customer Interface Specification, IPM Clearing Formats

Edit 10 POS_AUTH
Edit 10 POS_AUTH
Edit Number 10
Edit Title POS Authorization Values
Name POS_AUTH
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.
subedits apply:
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)

Edit 10 POS_AUTH
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)
Authorization DE 22, subfield 1 is not 03 (PAN auto-entry through bar
code
Authorization DE 22, subfield 1 is not 04 (PAN auto-entry through
optical character reader)
• 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 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 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 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)

Edit 11 C_PF_ID
Edit Number 10
• 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 Identify Check-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)
• 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)
• Clearing DE 22, subfield 7 is 7 (Credential on File) and Authorization
DE 22, subfield 1 is not 10 (Credential on File)

Reference Customer Interface Specification, IPM Clearing Formats, AN 1411—Data

Integrity Monitoring Program—New Edits and Updates to Existing Edit, AN
2232—Data Integrity Monitoring Program—Mapping of Authorization and
Clearing Values
Edit 11 C_PF_ID
Edit Number 11
Edit Title Clearing Payment Facilitator ID
Name C_PF_ID

Edit 13 MCC_MATCH
Edit Number 11
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.
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
Reference Customer Interface Specification, IPM Clearing Formats
Edit 13 MCC_MATCH
Edit Number 13
Edit Title Merchant Category Code Match
Name MCC_MATCH

Edit 14 MERCH_DBA_NAME_MATCH
Edit Number 13
Region(s) Global
Description This edit monitors the Merchant Category Code (MCC) in the clearing
message to ensure it matches the MCC in the corresponding
authorization request.
Edit Criteria Transactions monitored under this edit are identified by the Clearing
First Presentment/1240 DE 26 (Card Acceptor Business Code [MCC]).
A transaction is considered nonperforming when the value in the Clearing
First Presentment/1240 DE 26 does not match the value in DE 18
(Merchant Type) of the corresponding Authorization Request/0100
record.
Exclusions: MCC’s between 3000 and 3350, 4112, 4511, 4722, 7800, 7801,
7802, 7995 and 9406

Effective 1 March 2023

Baseline: All customers with 5,000 First Presentment/1240 transactions
Threshold: 98.85%.
Reference Customer Interface Specification, IPM Clearing Formats, AN 4669

Announcing New and Updated Edits for the Data Integrity Monitoring
Program, AN 1411—Data Integrity Monitoring Program—New Edits and
Updates to Existing Edit, AN 6961 Data Integrity Monitoring Program
Update for Card Acceptor Business Code Edits
Edit 14 MERCH_DBA_NAME_MATCH
Edit Number 14
Edit Title Merchant DBA Name Match
Name MERCH_DBA_NAME_MATCH
Region(s) Global

Edit 16 TERM_INPUT_MATCH
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 nonperforming when 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.

Integrity Monitoring Program—New Edits and Updates to Existing Edit
Edit Number 16
Edit Title Terminal Input Capability Indicator Match
Name TERM_INPUT_MATCH
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.

Edit Number 16
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 [for example,
voice/ARU authorization or other transactions that 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)


Edit 17 AAV_RATE_CLEAR_TRAN
Edit Number 16
Integrity Monitoring Program—New Edits and Updates to Existing Edit, AN
2232—Data Integrity Monitoring Program—Mapping of Authorization and
Clearing Values
Edit 17 AAV_RATE_CLEAR_TRAN
Edit Number 17
Edit Title Valid AAV for Authenticated Transactions (1240)
Name AAV_RATE_CLEAR_TRAN
Region(s) Global
Description This edit monitors the Accountholder Authentication Value (AAV) in
transactions that were authenticated through 3DS 1.0 or EMV 3DS to
ensure it is valid and corresponds appropriately to the security level
indicator (SLI).
Edit Criteria A transaction is considered nonperforming when Private Data
Subelement (PDS) 0052 (Electronic Commerce Security Level Indicator
[SLI]) contains a valid SLI (211, 212 or 215), but PDS 0185 (AAV) does
not begin with j, k, or h.
Baseline/ Baseline: 1,000 3DS transactions
Edit 18 DS_TRAN_ID_CLEAR_TRANS
Edit Number 18
Edit Title Directory Server Transaction ID (1240)
Name DS_TRAN_ID_CLEAR_TRANS

Edit 20 Cross Border TC28 Force Post 1240
Edit Number 18
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.
true:
• Private data subelement (PDS) 0052 (Electronic Commerce Security
Level Indicator) is 211, 212, 216, or 217
• PDS 0185 (Accountholder Authentication Value) has a leading
indicator of “k” indicating the transaction was authenticated through
EMV 3DS
• PDS 0184 (Directory Server Transaction ID) is missing

Threshold
Threshold: 90%
Reference IPM Clearing Formats, Mastercard Identity Check Program Guide, AN

2853 Data Integrity Monitoring Program Updates to Existing Programs
and New Edits to Monitor 3DS Activity
Edit 20 Cross Border TC28 Force Post 1240
Edit Number 20
Edit Title Cross Border TC28 Force Post 1240
Name Cross Border_TC28_Force Post
Region(s) Global
Description This edit monitors the values in DE 63 (Transaction Life Cycle ID),
subfield 2 (Trace ID) and DE 2 (Primary Account Number [PAN]) to help
ensure that when a First Presentment/1240 Cross-Border Payment
Transaction is present an authorization request is also present.

Edit 21 High Risk MCC Mismatch
Edit Number 20
Edit Criteria A transaction is considered nonperforming when the First Presentment/
1240 Cross-Border Payment Transaction does not have a matching
authorization request within the 30 the days before the Clearing record
submission.
A Cross-Border transaction is identified when the DE 43 (Card Acceptor
Name/Location), subfield 6 (Card Acceptor Country Code) is not equal to
the Issuer Country.
A Payment Transaction is identified when the DE 3 (Processing Code),
subfield 1 (Cardholder Transaction Type), value is 28.
Exclusions: Intra-EEA, United Kingdom and Gibraltar, Cross Border
Transactions, Collection Only Transactions, Reversals, and Rebates.
Rebates are identified when the private data subelement (PDS) 0043
(Program Registration ID), value is C02 (Mastercard rebate), and when
the card acceptor business code (MCC) value is 6555 (MA Initiated
Rewards/Rebate) in DE 18 (Merchant Type).

Baseline/ Baseline: 1 First Presentment/1240 Cross-Border Payment Transaction
Threshold Threshold: Zero (A single First Presentment/1240 Cross Border Payment
Force-posted Transaction is considered nonperforming)
Reference IPM Clearing Formats, Transaction Processing Rules, AN 4089 Data

Integrity Monitoring Program: New Acquirer Edit to Monitor Force Post
Cross-Border Payment Transactions
Edit 21 High Risk MCC Mismatch
Edit Number 21
Edit Title High Risk MCC Mismatch
Name High Risk MCC Mismatch
Region(s) Global
Description This edit monitors the Merchant Category Code (MCC) in the clearing
message to ensure it matches the MCC value in the corresponding
authorization request for high risk MCCs.

Edit 22 POI Currency Conversion 1240
Edit Number 21
Edit Criteria High risk transactions monitored under this edit are identified by one of
the following values in the Clearing First Presentment/1240 DE 26 (Card
Acceptor Business Code [MCC]):
• 7800 Government Owned Lottery (U.S. Region Only)
• 7801 Internet Gambling (U.S. Region Only)
• 7802 Government Licensed Horse/Dog Racing (U.S. Region Only)
• 7995 Gambling Transactions
• 9406 Government-owned Lottery (Specific Countries)
A transaction is considered nonperforming when the value in the Clearing
First Presentment/1240 DE 26 does not match the value in DE 18
(Merchant Type) of the corresponding Authorization Request/0100
record.

Baseline/ Baseline: 10 high risk transactions
• Effective 1 March 2021: 10 mismatched transactions
• Effective 1 March 2023: 1 mismatched transation
Reference Customer Interface Specification, IPM Clearing Formats, Quick Reference

Guide, AN 4669 Announcing New and Updated Edits for the Data Integrity
Monitoring Program, AN 6961 Data Integrity Monitoring Program Update
for Card Acceptor Business Code Edits
Edit Number 22
Edit Title POI Currency Conversion 1240
Name POI Currency Conversion 1240
Region(s) Global
Description This edit monitors point-of-interaction (POI) currency conversion (also
known as dynamic currency conversion [DCC]) card-present/cardholder-
present POS and ATM transactions to ensure that when DCC is applied,
it is not applied to accounts that issuers or Mastercard designate as not
allowing DCC.

Edit Number 22
criteria:
• DE 22, subfield 5 (Cardholder Present Data) is 0 (Cardholder present)
• DE 22, subfield 6 (Card Present Data) is 1 (Card present)
• Declared DCC: In any occurrence of DE 54, subfield 2 (Additional
Amount, Amount Type) is 58 (Amount, POI Amount)

• the account is within an account range identified in the MPE, FIT, or
BIN table resource files as prohibiting DCC – Cardholder Currency
Indicator value of T (for prepaid travel and debit multicurrency cards,
as well as the new MWP exclusion) or C (corporate client opt-out).

Baseline/ Baseline: 100 DCC transactions
Reference IPM Clearing Formats, Transaction Processing Rules, section 3.8 (POI
Currency Conversion), AN 5913 Data Integrity Monitoring Program: New
Edits for Point-of-Interaction Currency Conversion

Acquirer Clearing Chip Dual Message System Edits (1240)
Chapter 5 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..................................................................................................................................... 97
Edit 2 CC_Missing_EMVtags_DE55...................................................................................................................97
Edit 3 CC_Inv_Length_DE55...............................................................................................................................98
Edit 4 CC_Inv_EMVtags_DE55........................................................................................................................... 99
Edit 5 CC_Inv_form_DE55.................................................................................................................................100

Edit 1 CC_Missing_DE55
Edit 1 CC_Missing_DE55
Edit Number 1
Name CC_Missing_DE55
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.
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)
Circuit Card [ICC] System Related Data) is missing.

Reference IPM Clearing Formats, M/Chip Requirements for Contact and Contactless,
AN 2301—Data Integrity Monitoring Program—Updated Threshold on Chip
Edits
Edit 2 CC_Missing_EMVtags_DE55
Edit Number 2
Name CC_Missing_EMVtags_DE55
Region(s) Global

Edit 3 CC_Inv_Length_DE55
Edit Number 2
that all of the mandatory EMV tags are present.
following values in DE 22 (POS Entry Mode) , subfield 7(Card Data: Input
Mode):
A transaction is considered nonperforming when any of the mandatory
EMV tags are missing from DE55 (Integrated Circuit Card [ICC] System
Related Data).

Edits
Edit 3 CC_Inv_Length_DE55
Edit Number 3
Name CC_Inv_Length_DE55
Region(s) Global
that all of the mandatory EMV tags are submitted with the correct
length.

Edit 4 CC_Inv_EMVtags_DE55
Edit Number 3
following values in DE 22 (POS Entry Mode), subfield 7(Card Data: Input
Mode):
EMV tags in DE55 (Integrated Circuit Card [ICC] System Related Data)
are not submitted with the correct length.

Edits
Edit 4 CC_Inv_EMVtags_DE55
Edit Number 4
Name CC_Inv_EMVtags_DE55
Region(s) Global
that all of the mandatory EMV tags are submitted with the correct
format.
Mode):
EMV tags in DE55 (Integrated Circuit Card [ICC] System Related Data)
are not submitted with the correct format.

Edit 5 CC_Inv_form_DE55
Edit Number 4
Edits
Edit Number 5
Name CC_Inv_form_DE55
Region(s) Global
that DE 55 (Integrated Circuit Card [ICC] System Related Data) is
formatted correctly.
Mode):
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


Edit Number 5
Edits

Acquirer Debit Single Message System Edits (0200)
Chapter 6 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 can be monitored where specified. In the Data Integrity Online application,
the program name appears in its abbreviated form, Acq Debit Single Msg (0200).
Retired edits.........................................................................................................................................................103
Edit 1 D_INVMCC (5542)..................................................................................................................................103
Edit 2 D_MAGSTRIPE.........................................................................................................................................104
Edit 3 D_INVTYPE...............................................................................................................................................105
Edit 4 D_DE42.....................................................................................................................................................106
Edit 5 D_DE43.....................................................................................................................................................107
Edit 7 D_TERMPOS............................................................................................................................................108
Edit 8 D_POSCND..............................................................................................................................................110
Edit 9 D_PF_ID.................................................................................................................................................... 111
Edit 10 D_Pure_Magstripe ATM.......................................................................................................................112
Edit 11 D_Pure Magstripe POS........................................................................................................................113
Edit 12 D_INC_MAGSTRIPE_0200...................................................................................................................114
Edit 16 DSRP Cryptogram Placement_0200................................................................................................ 115
Edit 17 TTI Monitoring 0200.............................................................................................................................116
Edit 18 POI Currency Conversion 0200.......................................................................................................... 117
Edit 19 Funding Transactions 0200................................................................................................................ 118
Edit 21 Software MPOS 0200......................................................................................................................... 119

Retired edits
Retired edits
Edit 6 D_CARDACP (Retired from active monitoring)

Edit 13 D_MISREPORTED ATM FEE (Retired from active monitoring)
Edit 14 Recurring CoF Monitoring (0200)
Edit 15 D_MISREPORTED ATM FEE NON US (Retired from active monitoring)
Edit 1 D_INVMCC (5542)
Edit Number 1
Edit Title Invalid use of MCC 5542
Name D_INVMCC (5542)
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).
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
Customers with 1,000,000 or fewer transactions are subject to a
threshold of 97%.
Reference Single Message System Specifications

Edit 2 D_MAGSTRIPE
Edit 2 D_MAGSTRIPE
Edit Number 2
Edit Title Magnetic Stripe (0200)
Name D_MAGSTRIPE
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.
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
• 90 (PAN auto-entry via magnetic stripe)
A transaction is considered nonperforming when 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)
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 Identity Check-
AAV or DSRP cryptogram in UCAF)
• DE 35 or DE 45 is present

Edit 3 D_INVTYPE
Edit Number 2
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)
threshold of 97%.
Reference Single Message System Specifications, Quick Reference Booklet
Edit 3 D_INVTYPE
Edit Number 3
Edit Title MCC and TCC Combination for Quasi Cash
Name D_INVTYPE
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.
is 6051 (Quasi Cash) and DE 48 (Additional Data), position 1
(Transaction Category Code [TCC]) is not U (Unique).

Edit 4 D_DE42
Edit Number 3
threshold of 97%.
Reference Single Message System Specifications, Quick Reference Booklet
Edit 4 D_DE42
Edit Number 4
Edit Title Debit DE 42
Name D_DE42
Region(s) Global
Description This edit monitors the values in DE 42 (Card Acceptor Identification
Code) to ensure that they are present and valid.
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
threshold of 97%.

Edit 5 D_DE43
Edit 5 D_DE43
Edit Number 5
Edit Title DE 43 - Card Acceptor Name and Location (0200)
Name D_DE43
Region(s) Global
Description This edit monitors DE 43 (Card Acceptor Name/Location) to ensure that
all necessary values are present and properly formatted.
subedits apply:
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
g. DE 43, subfield 5 is AFG, ALB, ARG, AUT, BEL, BRA, CHE, COL, CZE,
transactions MCC in DE 18 is 3000-3350 or 4511 and 6011 (ATM)
road fees, tolls)
Monitoring start date: 1 October 2011, 1 February 2021 for subedit g

Edit 7 D_TERMPOS
Edit Number 5
threshold of 97%.
Reference Single Message System Specifications, AN 4589 Data Integrity Monitoring

Program: Updates to Existing Edits for Global Address Standardization
Edit 7 D_TERMPOS
Edit Number 7
Edit Title Terminal POS Processing Fields (0200)
Name D_TERMPOS
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).
subedits apply:
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)

Edit 7 D_TERMPOS
Edit Number 7
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 22, subfield 1 (POS Terminal PAN Entry Mode) is not 00 (PAN
entry mode unknown) or 01 (PAN manual entry)
e. DE 22, subfield 1 is 00 and DE 61, subfield 11 is any of the following:

• 2 (Terminal supports magnetic stripe input only)
input)
• 7 (Terminal supports 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
• 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)

Edit 8 D_POSCND
Edit Number 7
i. DE 61, subfield 5 is 1 and DE 22, subfield 1 is any of the following:
• 02 (Data is not required OR the acquirer is not qualified to submit
magnetic stripe transactions, so Mastercard replaced value 90 or 91
with value 02)
• 90 (PAN auto-entry via magnetic stripe—the full track data has been
• 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)

threshold of 97%.
Edit 8 D_POSCND
Edit Number 8
Edit Title POS Condition Codes (0200)
Name D_POSCND
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 9 D_PF_ID
Edit Number 8
Edit Criteria A transaction is considered nonperforming when the values in any of the
following subfields in DE 61 are invalid:
• Subfield 1 (POS Terminal Attendance)
• 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 10 (Cardholder-Activated Terminal Level)
• Subfield 11 (POS Card Data Terminal Input Capability)

threshold of 97%.
Edit 9 D_PF_ID
Edit Number 9
Edit Title Payment Facilitator ID (0200)
Name D_PF_ID
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.
subedits apply:

Edit 10 D_Pure_Magstripe ATM
Edit Number 9
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
threshold of 97%.
Reference IPM Clearing Formats, Single Message System Specifications
Edit 10 D_Pure_Magstripe ATM
Edit Number 10
Edit Title Pure Magnetic Stripe – ATM (0200)
Name D_Pure_Magstripe ATM
Region(s) Global
Description This edit monitors ATM transactions performed on magnetic stripe only
cards that are submitted as technical fallback.
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)

Edit 11 D_Pure Magstripe POS
Edit Number 10
Baseline/ Baseline: 1 ATM transaction
Reference M/Chip Requirements for Contact and Contactless, Single Message

System Specifications
Edit 11 D_Pure Magstripe POS
Edit Number 11
Edit Title Pure Magnetic Stripe – POS (0200)
Name D_Pure Magstripe POS
Regions Global
Description This edit monitors POS transactions performed on magnetic stripe only
cards that are submitted as technical fallback.
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: 1 POS transaction


Edit 12 D_INC_MAGSTRIPE_0200
Edit 12 D_INC_MAGSTRIPE_0200
Edit Number 12
Edit Title Inconsistent Magnetic Stripe (0200)
Name D_INC_MAGSTRIPE_0200
Region(s) Global
Description This edit monitors transactions performed with chip cards on chip-
capable terminals that are submitted as magnetic stripe.
true:
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
– 9 (Terminal supports EMV contact chip input only)
NOTE: Merchant Category Codes 4784 (Bridge and road fees, tolls) and
7523 (Automobile Parking Lots and Garages) are excluded from this edit.

Baseline/ Baseline: 1 magnetic stripe transaction
Threshold USA Threshold: 15,000 failures
Non-USA Threshold: 1,000 failures
Reference M/Chip requirements for Contact and Contactless, Single Message System
Specifications

Edit Number 16
Edit Title DSRP Cryptogram Placement_0200
Name DSRP Cryptogram Placement_0200
Region(s) Global
Description This edit monitors the presence of the Digital Secure Remote Payment
(DSRP) Cryptogram in DE 104 (Digital Payment Data) subelement 001
(Digital Payment Cryptogram) by the acquirer for MDES and third party
tokenized electronic commerce transactions in Financial Transaction
Request/0200 messages.
criteria:
– 82 (PAN Auto Entry via Server [issuer, acquirer, or third- party
vendor system])
A transaction is considered nonperforming when all of the following
criteria are met:
• DE 104 (Digital Payment Data) subelement 001 (Digital Payment
Cryptogram) is not present
• DE 48 (Additional Data), subelement 43 (UCAF) is not empty and the
value does not have a Mastercard Identity Check AAV (leading
indicator Mastercard Identity Check AAV begins with j, h or k)
Monitoring start date: 1 March 2021 and 1 December 2022 for third
party tokenized electronic commerce transactions
Baseline/ Baseline: 100 DSRP transactions
Reference Single Message System Specifications, AN 4670 New Data Integrity

Monitoring Program Edits for Digital Secure Remote Payment Cryptogram

Edit Number 17
Edit Title Transaction Type Identifier Monitoring 0200
Name TTI Monitoring 0200
Region(s) Global
Description This edit monitors the Transaction Type Identifier (TTI) in purchase,
refund, and payment transactions to help ensure acquirers discontinue
inappropriate use of TTIs and use of invalid TTIs.
following values in DE 3 (Processing Code), subfield 1 (Cardholder
Transaction Type Code):
• 00 (Purchase)
• 20 (Refund/Correction)
• 28 (Payment Transaction)
A transaction is considered nonperforming when DE 48 (Additional Data
—Private Use), subelement 77 (Transaction Type Identifiers [TTI]) is any
of the following:
• C01 (Person-to-Person)
• C02 (Mastercard Rebate)
• C05 (Other payment reason) or
• the value in DE 48, SE 77 is not a valid TTI per the Single Message
System Specifications manual
NOTE: The TTI value of C02 (Mastercard Rebate) is for Mastercard use
only as stated in AN 4462 Revised Standards for the Sunset of Several
Legacy Transaction Type Identifiers.
Monitoring start date: 1 July 2021

Baseline/ Baseline: 1 single message (0200) purchase, refund, or payment
Threshold transaction
Threshold: 100 errors

Program: New Edits for Transaction Type Identification

Edit Number 18
Edit Title POI Currency Conversion 0200
Name POI Currency Conversion 0200
Region(s) Global
Description This edit monitors point-of-interaction (POI) currency conversion (also
known as dynamic currency conversion [DCC]) card-present/cardholder-
present POS and ATM transactions to ensure that when DCC is applied,
it is not applied to accounts that issuers or Mastercard designate as not
allowing DCC.
criteria:
• DE 61, subfield 4 (Cardholder Presence) is 0 (Cardholder present)
• DE 61, subfield 5 (POS Card Presence) is 0 (Card present)
• Declared DCC: In any occurrence of DE 54, subfield 2 (Additional
Amounts, Amount Type) is 58 (POI Amount)

• the account is within an account range identified in the MPE, FIT, or
BIN table resource files as prohibiting DCC – Cardholder Currency
Indicator value of T (for prepaid travel and debit multicurrency cards,
as well as the new MWP exclusion) or C (corporate client opt-out).

Baseline/ Baseline: 100 DCC transactions
Reference Single Message System Specifications, Single Message System Settlement

and Reports, (80-byte Financial Institution Table File, FIT Optional
Addendum Record [FIT1]), Transaction Processing Rules, section 3.8 (POI
Currency Conversion), AN 5913 Data Integrity Monitoring Program: New
Edits for Point-of-Interaction Currency Conversion

Edit Number 19
Edit Title Funding Transactions 0200
Name Funding Transactions 0200
Region(s) Global
Description This edit monitors acquirer funding transactions to ensure that acquirers
are sending appropriate MCC and transaction type identifier (TTI)
values, and that the funding transaction includes key required reference
data in DE 108 (Additional Transaction Reference Data) of Financial
Transaction Request/0200 messages.
criteria:
Code) is 00 (Purchase) and
• DE 18 (Merchant Type [MCC]) is any of the following
– 4829 (Money Transfer)
– 6538 (Funding Transactions for MoneySend)
– 6540 (Funding Transactions)

subedits are true:
a. DE 48 (Additional Data—Private Use), subfield 77 (Transaction Type

Identifier) is blank or null
b. DE 48, subfield 77 is not blank or null and DE 108 (Additional
Transaction Reference Data), subelement 1 (Receiver/Recipient Data),
subfield 1 (Receiver/Recipient First Name) and subfield 3 (Receiver/
Recipient Last Name) are not populated
Exclusions:
Monitoring start date: 1 November 2022

Baseline/ Baseline: 1 funding transaction

Edit Number 19
Reference Mastercard MoneySend and Funding Transactions Program Standards,
Single Message System Specifications, AN 6410 New Data Integrity
Monitoring Program Edits for Funding Transactions
Edit Number 21
Edit Title Software MPOS 0200
Name Software MPOS 0200
Region(s) Global
Description This edit monitors the software mobile point-of-sale (mPOS) indicator in
Data Element (DE) 61 (Point-of-Service [POS] Data), subfield 10
(Cardholder-Activated Terminal Level) in the acquirer Financial
Transaction Request/0200 messages to ensure proper identification is
occurring.

Edit Number 21
criteria:
• DE 61, subfield 10 is 9 (mPOS Acceptance Device)
PIN Entry Mode) is not one of the following values:
– 2 (Terminal does not have PIN entry capability)
– 3 (mPOS Software-based PIN Entry Capability), or
• DE 22, subfield 2 is 2 and DE 48 (Additional Data-Private Use),
subelement 21 (Acceptance Data), subfield 01 (mPOS Acceptance
Device Type) is not 1 (Off the Shelf Mobile Device), or
• DE 22, subfield 2 is 3 (MPOS Software-based PIN Entry Capability)
and DE 48, subelement 21, subfield 01 is not one of the following
values:
– 0 (Dedicated mPOS terminal with PCI compliant dongle [with or
without keypad])
– 1
Exclusions:
• DE 22, subfield 2 is 1 (Terminal has PIN entry capability) and DE 48,
subelement 21, subfield 01 is 0
• DE 22, subfield 2 is 2 and DE 48, subelement 21, subfield 01 is 0
• DE 22, subfield 2 is 8 (Terminal has PIN entry capability but PIN pad is
not currently operative) and DE 48, subelement 21, subfield 01 is 0
• DE 61, subfield 11 (POS Card Data Terminal Input Capability
Indicator) is 9 (Terminal supports EMV contact chip input only)

Baseline/ Baseline: 300 software mPOS transactions

System Specifications, AN 7011 New Data Integrity Monitoring Program
Edits for Software Mobile Point-of-Sale Indicators

Acquirer Debit Single Message System Chip Edits (0200)
Chapter 7 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 Chip Single Msg (0200).
Retired edits.........................................................................................................................................................122
Chip testing requirement.................................................................................................................................. 122
Edit 1 DC_Missing_DE35...................................................................................................................................122
Edit 4 DC_Inv_form_DE55................................................................................................................................ 124
Edit 5 DC_Missing_EMVtags_DE55................................................................................................................ 125
Edit 6 DC_Inv_Length_DE55.............................................................................................................................126
Edit 7 DC_Inv_DE61_SF11................................................................................................................................127
Edit 8 Fallback Rt ATM 0200............................................................................................................................128
Edit 9 Fallback Rt POS 0200............................................................................................................................128
Edit 11 DC_INV_EMVTAGS_DE55...................................................................................................................129
Edit 12 Contactless CVM Limits 0200........................................................................................................... 130

Retired edits
Retired edits
Edit 10 – DC_INC_Magstripe_0200 (Retired from active monitoring)
Chip testing requirement
Before sending and 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 Number 1
Edit Title Missing DE35 (0200)
Name DC_Missing_DE35
Region(s) Global
Description This edit monitors single message chip transactions to ensure that the
Track 2 data is populated.
following values in DE 22 (Point of Service [POS] Entry Mode) , subfield 1
(POS Terminal PAN Entry Mode):
A transaction is considered nonperforming when DE 35 (Track 2 Data) is
missing.


Edit Number 1
Reference Single Message System Specifications, AN 2301—Data Integrity
Monitoring Program—Updated Threshold on Chip Edits
Edit Number 2
Region(s) Global
Description This edit monitors single message transactions to ensure that the
retrieval reference number is populated where required.
PAN Entry Mode):
A transaction is considered nonperforming when DE 37 (Retrieval
Reference Number) is missing.



Edit Number 3
Region(s) Global
Description This edit monitors single message chip transactions to ensure that the
Integrated Circuit Card (ICC) System-Related Data is populated.
PAN Entry Mode):
A transaction is considered nonperforming when DE 55 (ICC System-
Related Data) is missing.


Edit 4 DC_Inv_form_DE55
Edit Number 4
Name DC_Inv_form_DE55
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 5 DC_Missing_EMVtags_DE55
Edit Number 4
PAN Entry Mode):
A transaction is considered nonperforming when the TLV is not
formatted in accordance with specifications outlined in M/Chip
Requirements for Contact and Contactless.


System Specifications, AN 2301—Data Integrity Monitoring Program—
Updated Threshold on Chip Edits
Edit 5 DC_Missing_EMVtags_DE55
Edit Number 5
Name DC_Missing_EMVtags_DE55
Region(s) Global
Description This edit monitors single message chip transactions to ensure that all the
required EMV tags are present.
PAN Entry Mode):
A transaction is considered nonperforming when DE55 (Integrated
Circuit Card [ICC] System Related Data) is missing one or more required
EMV tags.

Edit 6 DC_Inv_Length_DE55
Edit Number 5

Edit 6 DC_Inv_Length_DE55
Edit Number 6
Name DC_Inv_Length_DE55
Region(s) Global
Description This edit monitors single message chip transactions to ensure all EMV
tags are the correct length.
PAN Entry Mode):
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.



Edit 7 DC_Inv_DE61_SF11
Edit 7 DC_Inv_DE61_SF11
Edit Number 7
Edit Title Invalid Terminal Input Capability (0200)
Name DC_Inv_DE61_SF11
Regions(s) Global
Description This edit monitors terminal input capability to ensure that it corresponds
appropriately to the POS entry mode for single message chip
transactions.
subedits apply:
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])
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
Threshold
Threshold: 99.85%


Edit Number 8
Edit Title Technical Fallback Rate – ATM Transactions (0200)
Name Fallback Rt ATM 0200
Region(s) Global
Description This edit monitors ATM transactions performed with chip cards on chip-
Edit Criteria Transactions are considered nonperforming when DE 22, subfield 1
equals 80.
Transactions monitored under this edit are identified by the following
criteria:
is
Exclusions: Product code MPV

Threshold
Threshold: 99%

Edit Number 9
Edit Title Technical Fallback Rate – POS Transactions (0200)
Name Fallback Rt POS 0200

Edit 11 DC_INV_EMVTAGS_DE55
Edit Number 9
Region(s) Global
Description This edit monitors POS transactions performed with chip cards on chip-
criteria:
• DE 18 (Merchant Type) is not 6011 (ATM)
is
• DE 22, subfield 1 equals 80
Exclusions:

Threshold
Threshold: 99%

Edit 11 DC_INV_EMVTAGS_DE55
Edit Number 11
Name DC_INV_EMVTAGS_DE55
Regoin(s) Global
Description This edit monitors single message chip transactions to determine if any
EMV tag data present in DE 55 (Integrated Circuit Card [ICC] System-
Related Data) is invalid.

Edit Number 11
subedits apply:
a. Tag 9F27 (Cryptogram Information Data) is not any of the following:
• 0x
• 4x
• 8x
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.

Edit Number 12
Edit Title Contactless Cardholder Verification Method Limits 0200
Name Contactless CVM Limits 0200

Edit Number 12
Regoin(s) Asia/Pacific, Latin America and the Caribbean, and select countries in
Middle East/Africa (Angola, Bahrain, Botswana, Egypt, Ghana, Jordan,
Kenya, Kuwait, Lebanon, Lesotho, Malawi, Mauritius, Morocco,
Mozambique, Namibia, Nigeria, Oman, Qatar, Saudi Arabia, Seychelles,
South Africa, Swaziland, Tanzania, Uganda, United Arab Emirates, and
Zambia)
Description This edit monitors merchant terminals to ensure that they are accurately
setting the CVM limits to Mastercard published values.
criteria:
• Message Type Identifier is 0200 (Financial Transaction Request)
PAN Entry Mode) value is 07 (PAN auto-entry via contactless M/Chip)
• DE 55 (Integrated Circuit Card [ICC] System-Related Data) tag value
is 9F1A (Terminal Country Code)

subedits are true:
a. Transaction amount in DE 4 (Amount, Transaction is less than or equal
to the CVM limit per country, and DE 55 is present and tag 9F34
(Cardholder Verification Method [CVM] Results) values do not start with
00011111 or 00111111; or
b. Transaction amount in DE 4 (or DE 54, subfield 5 for DCC) is greater
than the CVM limit per country, and DE 55 is present and tag 9F34
values start with 00011111 or 00111111
NOTE: DCC is determined when DE 54 (Additional Amounts), subfield 2

(Account Type) value is 58 (POI Amount (also known as Dynamic
Currency Conversion [DCC]))
Exclusions:
• DE 3 (Processing Code), Subfield 1—Cardholder Transaction Type
Code value 09 (Purchase with Cash Back)
• DE 18 (Merchant Type [MCC]) values 4784, 4829, 5542, 6010, 6011,
6050, 6051, 6540, 7802, 7995, and 9405

Edit Number 12
Baseline/ Baseline: 1,000 contactless POS transactions
The performance rating percentage is not exclusive per subedit (a or b)
and if customer fails a or b on a transaction it is counted as a failure and
adds up against total failures.
Reference Chargeback Guide, M/Chip Requirements for Contact and Contactless

(RA486.20), Transaction Processing Rules, section 3.4 (Mastercard
Cardholder Verification Requirements), and section 4.4 (Contactless
Transactions at POS Terminals), AN 5957 Data Integrity Monitoring
Program: New Edits for Cardholder Verification Method Limits for Select
Regions

Acquirer Chargeback Monitoring Program
Chapter 8 Acquirer Chargeback Monitoring Program

The edits in this program evaluate transactions in support of the Acquirer Chargeback
Monitoring Program (ACMP) to encourage each acquirer to closely monitor, on an
ongoing basis, its fraud and chargeback performance at the merchant level and to
promptly determine when a Mastercard merchant has exceeded or is likely to exceed
monthly thresholds.
About edits.......................................................................................................................................................... 134

Edit 1 Excessive Fraud Merchant.....................................................................................................................134
Edit 2 Excessive Chargeback Merchant..........................................................................................................137
Acquirer Chargeback Monitoring Program regulated/non-regulated countries..................................... 139

About edits
About edits
The Acquirer Chargeback Monitoring Program includes two edits: Excessive Fraud
Merchant and Excessive Chargeback Merchant (also known as the Excessive
Chargeback Program [ECP]).
Detailed information about the ECP can be found in section 8.3 of the Security
Rules and Procedures manual. Once a merchant ID reaches month 12 of being
identified under either Edit 1 Excessive Fraud Merchant or Edit 2 Excessive
Chargeback Merchant, and is identified under both in the same month, the higher
assessment amount (whether for Edit 1 or Edit 2) takes priority for billing
purposes.
Edit 1 Excessive Fraud Merchant
Edit Number 1
Edit Title Excessive Fraud Merchant
Name Excessive Fraud Merchant
Region(s) Global
Description This edit monitors the total amount of fraud occurring at a given e-
commerce merchant as well as the number of transactions
authenticated through EMV 3-D Secure (3DS) or Digital Secure Remote
Payment (DSRP).

Edit Number 1
Edit Criteria Merchants are considered nonperforming when all of the following
conditions are met in a given month:
1. The total dollar amount (or local currency equivalent) of fraud-
related chargebacks is greater than or equal to EUR/USD 50,000
(USD 15,000 for Australia)
2. The total number of fraud chargeback basis points (BPS) is greater
than or equal to 50 (20 for Australia)
3. The percentage of monthly clearing volume processed using 3DS
(including Identity Check Insights [IDCI] transactions) or DSRP is less
than 10 percent in nonregulated countries, or less than 50 percent in
regulated countries
NOTE: Monthly fraud-related chargebacks are defined as those first

presentment chargebacks processed within a calendar month under the
4837 (No cardholder authorization) message reason code.
3DS transactions are identified in clearing in private data subelement

(PDS) 0052 (Security Level Indicators) with a value of 211, 212, 214, 216,
or 217.
DSRP transactions are identified in clearing in PDS 0052 with a value of
242 (Issuer Fully Authenticated) or 246 (Merchant Risk Based
Decisioning).
IDCI (previously called Data Only) refers to non-3DS transactions in
which Mastercard performs risk scoring and injects Digital Transaction
Insights to the authorization request message.
The term non-regulated refers to those countries without a legal or
regulatory requirement for strong cardholder authentication. The term
regulated refers to those countries with a legal or regulatory requirement
for strong cardholder authentication. See Acquirer Chargeback
Monitoring Program Regulated/Non-regulated Countries tables for full
list.
Exclusions: This program does not apply to merchants in Germany, India,
Liechtenstein, Saint Helena, Ascension and Tristan Da Cunha and
Switzerland.

Edit Number 1
Effective 1 January 2023: This program does not apply to merchants in
Aland Islands, Albania, Andorra, Antarctica, Austria, Belgium, Bosnia and
Herzegovina, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark,
Estonia, Falkland Islands (Malvinas), Faroe Islands, Finland, France,
French Guiana, Gibraltar, Greece, Greenland, Guadeloupe, Guernsey,
Hungary, Iceland, Ireland, Isle of Man, Italy, Jersey, Kosovo, Latvia,
Lithuania, Luxembourg, Macedonia, Malta, Martinique, Mayotte,
Moldova, Monaco, Montenegro, Netherlands (the), Norway, Poland,
Portugal, Réunion, Romania, Saint Barthélemy, Saint Helena, Ascension
and Tristan da Cunha, Saint Martin (French part), San Marino, Serbia,
Slovakia, Slovenia, South Georgia and the South Sandwich Islands, Spain,
Svalbard and Jan Mayen, Sweden, Ukraine, United Kingdom and Vatican
City
Monitoring start date: 1 October 2019, 1 May 2022 for Australia updates
Baseline/ Baseline: 1,000 e-commerce transactions (by MID) in Clearing
Threshold Threshold: By MID (see edit description)
Reference Chargeback Guide, AN 2530-U.S. Assurance Framework, AN 2819-Canada

Assurance Framework, AN 2852 Revised Standards-Excessive Fraud
Merchant Compliance Program, AN 2968 Revised Standards - Data
Integrity Monitoring Program - Introducing the Acquiring Chargeback
Program, AN 5879 Data Integrity Monitoring Program, Update to the
Excessive Fraud Merchant Edit in Australia
The acquirer may be subject to the following assessments if noncompliant.
Table 5: EFM assessment structure
Number of months above EFM thresholds EFM violation assessment amount

Violation assessment
1 EUR/USD 0
2 EUR/USD 500
3 EUR/USD 1,000
4 to 6 EUR/USD 5,000
7 to 11 EUR/USD 25,500
12 to 18 EUR/USD 50,000
19+ EUR/USD 100,000

Edit 2 Excessive Chargeback Merchant
Edit Number 2
Edit Title Excessive Chargeback Merchant
Name Excessive Chargeback Merchant
Billing Code 2DC0401 and 2DC0402
Region(s) Global
Description This edit monitors chargeback performance at the merchant ID (MID)
level to determine if a merchant has exceeded monthly chargeback
thresholds.
Edit Criteria Merchants are evaluated under two categories, Excessive Chargeback
Merchant (ECM) and High ECM (HECM).
Merchants are considered noncompliant in the ECM category when both
of the following are true:
• The total number of chargebacks is greater than or equal to 100
• The total number of chargeback bps is greater than or equal to 150
Merchants are considered noncompliant in the High ECM category when
both of the following are true:
• The total number of chargebacks is greater than or equal to 300
• The total number of chargeback bps is greater than or equal to 300
A merchant identified as noncompliant for Edit 1—Excessive Fraud
Merchant will not be assessed for Edit 2—Excessive Chargeback
Merchant.
Once a merchant ID is identified in the ECM edit, the merchant ID will
continue to be monitored until there are three consecutive months below
the ECM thresholds, at which time the ECM status resets.
Monthly chargebacks are defined as all first presentment chargebacks
with a processed date within the violation month. Bps are the number of
chargebacks received by the acquirer for a merchant ID in a calendar
month divided by the number of Mastercard transactions processed for
the merchant ID in the preceding month, and then multiplied by 10,000.
Monitoring start date: 1 October 2019, 1 March 2022 for additional

baseline of 25 or more cleared transactions.
Baseline/ Baseline: 1 chargeback and 25 or more cleared transactions for each MID
Threshold Threshold: By MID (see edit description)

Edit Number 2
Reference Security Rules and Procedures, AN 2968 Revised Standards - Data
Integrity Monitoring Program - Introducing the Acquiring Chargeback
Program, AN 5588 Revised Standards for the Acquirer Chargeback
Monitoring Program
Table 6: ECP assessment structure
ECM violation
assessment amount
Number of months (100–299
chargebacks and– HECM violation assessment amount
above ECP
thresholds 299 Basis Points) (> 300 chargebacks and > 300 Basis Points)
Issuer recovery
Violation assessment Violation assessment assessment
1 EUR/USD 0 EUR/USD 0 No
2 EUR/USD 1,000 EUR/USD 1,000 No
3 EUR/USD 1,000 EUR/USD 2,000 No
4 to 6 EUR/USD 5,000 EUR/USD 10,000 Yes6
19+ EUR/USD 100,000 EUR/USD 200,000 Yes6
A merchant's status in the Acquirer Chargeback Monitoring Program does not reset as
compliant, until the merchant ID has achieved three consecutive months below the
program thresholds.
Table 7: Example of ECM/HECM status reset
Month ECP status Assessment amount

January ECM (month 1) 0
February No Violation 0
March ECM (month 2) EUR/USD 1,000
April HECM (month 3) EUR/USD 2,000
6 Issuer recovery assessment applies at EUR/USD 5 for each chargeback over 300 chargebacks. For
example, a merchant with 500 chargebacks would be assessed EUR/USD 1,000 in issuer recovery
(500-300 = 200 x EUR/USD 5 = EUR/USD 1,000)

Acquirer Chargeback Monitoring Program regulated/non-regulated countries
Month ECP status Assessment amount

May No Violation 0
June No Violation 0
July No Violation—Audit Closed 0
Acquirer Chargeback Monitoring Program regulated/non-regulated

countries
The following tables list the countries identified as regulated or non-regulated.
Asia/Pacific region
The countries in the following table are regulated countries.
Table 8: Regulated countries
Bangladesh Malaysia Singapore
The countries in the following table are non-regulated countries.
Table 9: Non-regulated countries
American Samoa Korea, Republic of Philippines

Australia Lao People's Democratic Pitcairn
Republic
Bhutan Macao Samoa
Brunei Darussalam Maldives Solomon Islands
Cambodia Marshall Islands Sri Lanka
China Micronesia, Federated Taiwan
States of
Christmas Island Mongolia Thailand
Cocos (Keeling Islands) Myanmar Timor-Leste
Cook Islands Nauru Tokelau
Fiji Nepal Tonga
French Polynesia New Caledonia Tuvalu

Guam New Zealand U.S. Minor Outlying Islands

Heard and McDonald Islands Niue Vanuatu
Hong Kong Norfolk Island Viet Nam
Indonesia Northern Mariana Islands Wallis and Futuna
Japan Palau
Kiribati Papua New Guinea
Canada region
Canada is a non-regulated country.
Europe region
The countries in the following table are regulated countries.
Table 10: Regulated countries
Austria Gibraltar Netherlands

Belgium Greece Norway
Bulgaria Hungary Poland
Croatia Iceland Portugal
Cyprus Ireland Romania
Czech Republic Italy Slovakia
Denmark Latvia Slovenia
Estonia Lithuania Spain
Finland Luxembourg Sweden
France Malta United Kingdom
Albania Israel Serbia

Andorra Kazakhstan Tajikistan
Armenia Kosovo Turkey

Azerbaijan Kyrgyzstan Turkmenistan

Belarus Macedonia Ukraine
Bosnia and Herzegovina Moldova Uzbekistan
Channel Islands Montenegro Vatican City
Georgia Russian Federation
Isle of Man San Marino
Latin America and the Caribbean region

All countries in the Latin America and the Caribbean Region are non-regulated
countries.
Middle East/Africa region

Nigeria is a regulated country.
Afghanistan Gabon Palestine

Algeria Gambia Qatar
Angola Ghana Reunion
Bahrain Guinea Rwanda
Benin Guinea-Bissau Sao Tome and Principe
Botswana Iraq Saudi Arabia
Bouvet Island Jordan Senegal
British Indian Ocean Kenya Seychelles
Territory
Burkina Faso Kuwait Sierra Leone
Burundi Lebanon Somalia
Cameroon Lesotho South Africa
Cape Verde Liberia South Sudan
Central African Republic Libyan Arab Jamahiriya Swaziland
Chad Madagascar Syrian Arab Republic
Comoros Malawi Tanzania

Congo Mali Togo

Cote D'Ivoire Mauritania Tunisia
Democratic Republic of Mauritius Uganda
Congo
Djibouti Morocco United Arab Emirates
Egypt Mozambique Western Sahara
Equatorial Guinea Namibia Yemen
Eritrea Niger Zambia
Ethiopia Oman Zimbabwe
French Southern Territories Pakistan
United States region

The United States is a non-regulated country.

Issuer Authorization Dual Message System Edits (0110)
Chapter 9 Issuer Authorization Dual Message System

Edits (0110)
0110/Authorization Response message. In the Data Integrity Online application, the
program name appears in its abbreviated form, Iss Auth Dual Msg (0110).
Retired edits.........................................................................................................................................................144
Edit 4 EMV_ARPC_0110....................................................................................................................................144
Edit 13 NO_CVM_HIGH_DECLINE_PT............................................................................................................145
Edit 14 NO_CVM_HIGH_DECLINE_VEND......................................................................................................146
Edit 15 ISS_OFFLINE_CAM_0110................................................................................................................... 147
Edit 18 Fallback Decline Rate 0110................................................................................................................ 148
Edit 19 Issuer COF Monitoring (0110)............................................................................................................149
Edit 20 ABU Penetration Rate......................................................................................................................... 150
Edit 21 ABU for Issuers......................................................................................................................................151
Edit 22 Invalid AVS Value (0110).....................................................................................................................152
Edit 23 SDA Capable Cards (0110)................................................................................................................ 153
Edit 26 EMV3DS_Non_Low_Risk_Appr_Rt.....................................................................................................154
Edit 27 EMV3DS_Full_Authent_Appr_Rt........................................................................................................155
Edit 28 Contactless Issuer................................................................................................................................ 157
Edit 29 Do Not Honor 05 Declines 0110........................................................................................................ 158
Edit 30 Auth Refund Inv Declines 0110.......................................................................................................... 159
Edit 31 Auth Refund Appr Rt 0110................................................................................................................. 160

Retired edits
Retired edits
Edit 1 MONEYSEND_AR_0110
Edit 2 ASI_APP_RT (Retired from active monitoring)
Edit 3 ASI_INV_RC (Retired from active monitoring)
Edit 5 CP_AFFL_APP_RT (Retired from active monitoring)
Edit 6 CP_GOLD_APP_RT (Retired from active monitoring)
Edit 7 CP_STND_APP_RT (Retired from active monitoring)
Edit 8 CNP_AFFL_APP_RT (Retired from active monitoring)
Edit 9 CNP_GOLD_APP_RT (Retired from active monitoring)
Edit 10 CNP_STND_APP_RT (Retired from active monitoring)
Edit 11 ISS_ATTEMPTS_NOSOLUTION_DECLIN (Retired from active monitoring)
Edit 12 ISSUER_ATTEMPTS_AAV_DECLINE (Retired from active monitoring)
Edit 16 AAV_Validation_Mandate (Retired from active monitoring)
Edit 17 FULL_AUTH_APPR_RT (Retired from active monitoring)
Edit 24 (Open)
Edit 25 ISS_AUTH_RESP_CODE_65
Edit 4 EMV_ARPC_0110
Edit Number 4
Edit Title ARPC Presence (0110)
Name EMV_ARPC_0110
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.

Edit 13 NO_CVM_HIGH_DECLINE_PT
Edit Number 4
Edit Criteria Transactions are monitored under this edit when all of the following are
true:
is 05 (PAN auto-entry via chip)
• DE 39 (Response code) is one of the following:
• DE 55 is present in the originating 0100/Authorization Request with
all mandatory tags
A transaction is considered nonperforming when 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.

Baseline/ Baseline: 500 chip transactions
Reference Authorization Manual, Customer Interface Specification, M/Chip

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

Edit 14 NO_CVM_HIGH_DECLINE_VEND
Edit Number 13
criteria:
• DE 4 (Amount, Transaction) is less than 50 euros
• DE 18 (Merchant Type) is 4784 (Bridge and road fees, tolls) or 7523
(Automobile Parking Lots and Garages)
is 05
• DE 55 (Integrated Circuit Card [ICC] System-Related Data),
subelement 95 (Terminal Verification Result [TVR]) shows that CVM
failed
A customer is considered nonperforming when 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

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

Edit 15 ISS_OFFLINE_CAM_0110
Edit Number 14
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
• 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 nonperforming when the monthly approval rate
for all qualified transactions is below 50%. Approvals are identified by
the following values in DE 39 (Response Code):

Baseline/ Baseline: 10 declines

Contactless
Edit Number 15
Edit Title Issuer Offline CAM (0110)
Name ISS_OFFLINE_CAM_0110
Region(s) Global

Edit 18 Fallback Decline Rate 0110
Edit Number 15
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).
criteria:
• Card is capable of offline authentication
is 05 ( PAN auto-entry via chip)
• DE 39 (Response code) is any of the following:
– 85 (Not Declined)
An issuer is considered nonperforming when less than the current annual
threshold percent of eligible transactions show that CDA is supported in
DE 55, subelement 82 (Application Interchange Profile [AIP]) (Byte 1, bit
1).

Baseline/ Baseline: 500 offline CAM-capable card chip transactions
Threshold
Threshold: Adjusts annually.
• Effective 1 January 2022, 50%

Contactless, AN 2871—Updates to EMV Offline CAM Requirements and
Associated Data Integrity Edits
Edit Number 18
Edit Title Issuer Fallback Decline Rate (0110)
Name Fallback Decline Rate 0110
Region(s) Canada, Europe, Latin America and the Caribbean, Middle East/Africa

Edit 19 Issuer COF Monitoring (0110)
Edit Number 18
Description This edit monitors transactions submitted as technical fallback to ensure
issuers are declining them.
Edit Criteria A transaction is considered nonperforming when both of the following
are true:
is 80 (Chip card at chip-capable terminal was unable to process
• DE 39 (Response Code) is any of the following:
Exclusions:
Code) equal to 20 (Purchase Return/Refund)
Transactions taking place at merchant locations in the United States and

Asia/Pacific are not monitored under this edit.

Baseline/ Baseline: 50 fallback transactions

Contactless, Transaction Processing Rules, AN 2237—Data Integrity
Monitoring Program—New Edits to Monitor Issuer Fallback Transaction
Approvals
Edit 19 Issuer COF Monitoring (0110)
Edit Number 19
Edit Title Credential on File (COF) Approval Rate
Name Issuer COF Monitoring (0110)
Region(s) Global

Edit 20 ABU Penetration Rate
Edit Number 19
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 nonperforming 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%

Program New Edits to Monitor Use and Acceptance of Credential-On-File
Indicator
Edit 20 ABU Penetration Rate
Edit Number 20
Edit Title ABU Penetration Rate
Name ABU Penetration Rate
Region(s) Asia/Pacific (excluding China, India, and Taiwan), Middle East/Africa,
United States, Puerto Rico and Virgin Islands, U.S.
Description This edit monitors the account range cardholder penetration rate of the
ABU.

Edit 21 ABU for Issuers
Edit Number 20
Edit Criteria The cardholder penetration rate is determined by the total number of
unique primary account numbers (PANs) registered for ABU within a
given account range and the number of unique PANs active on the
Mastercard Network in the last 12 months.
An ICA number is considered nonperforming when any account range
under that ICA number does not maintain a cardholder penetration rate
of 95%.
NOTE: Assessments for this edit is applied at the parent ICA number
level. A parent ICA number is assessed according to the standard Data
Integrity assessment structure as long as any ICA number in the family
has at least one nonperforming account range. A parent ICA number isl
not assessed more than one time for each month, even if multiple child
ICA numbers are considered nonperforming.
Exclusions: Prepaid product codes

Baseline/ Baseline: 15,000 approved authorizations on unique PANs in the past 12
Threshold months
Threshold: 95% of active cards in every account range
Reference Automatic Billing Updater Reference, Transaction Processing Rules
Edit 21 ABU for Issuers
Edit Number 21
Edit Title ABU for Issuers
Name ABU for Issuers
Region(s) Select Countries in Europe (Armenia, Azerbaijan, Belarus, Belgium,
Georgia, Germany, Gibraltar, Ireland, Italy, Kazakhstan, Kyrgyzstan,
Liechtenstein, Luxembourg, Netherlands, Portugal, Russian Federation,
San Marino, Switzerland, Tajikistan, Turkmenistan, United Kingdom,
Uzbekistan)
Description This edit monitors the implementation of ABU by issuers in countries
where it is mandated.

Edit 22 Invalid AVS Value (0110)
Edit Number 21
Edit Criteria A parent ICA number is considered nonperforming when any ICA number
in the family has not implemented ABU.
NOTE: Assessments for this edit is applied at the parent ICA number
level. A parent ICA number will be assessed according to the standard
Data Integrity assessment structure until every ICA number in the family
has implemented ABU. A parent ICA number is not assessed more than
one time for each month, even if multiple child ICA numbers are
considered nonperforming.
Exclusions: See the issuer requirements table in Rule 5.7.1 of the

Transaction Processing Rules.

Baseline/ Baseline: 500 approved recurring payment or credential-on-file
Threshold transactions
Reference Automatic Billing Updater Reference Guide, Transaction Processing Rules
Edit 22 Invalid AVS Value (0110)
Edit Number 22
Edit Title Invalid AVS Value (0110)
Name Invalid AVS Value (0110)
Region(s) Canada, United States
Description This edit monitors issuer support of address verification service (AVS)
response.

Edit 23 SDA Capable Cards (0110)
Edit Number 22
Edit Criteria A transaction is considered nonperforming when DE 48 (Additional Data
– Private Use), subelement 83 (AVS Response), contains a value of S
(AVS currently not supported).
NOTE: Issuers are required to populate DE 48, subelement 83, of the

Authorization Response/0110 message any time the acquirer requests
address verification in DE 48, subelement 82, of the Authorization
Request/0100 message.
AVS response code U (No response from issuer/authorization platform)

can be used where there is a decline authorization and the issuer cannot
disclose the address verification service (AVS) response.
Exclusions: This edit excludes transactions performed on prepaid
anonymous cards within the following brand product codes:
• MPF—Mastercard Prepaid Gift
• MPM—Mastercard Prepaid Consumer Incentive
• MPY—Mastercard Prepaid Employee Incentive

Baseline/ Baseline: 1,000 AVS transactions
Reference Authorization Manual, Customer Interface Specification
Edit 23 SDA Capable Cards (0110)
Edit Number 23
Edit Title SDA Capable Cards (0110)
Name SDA Capable Cards (0110)
Region(s) Global
Description This edit monitors the offline Card Authentication Method (CAM)
supported on offline CAM-capable cards to ensure that no cards with
Static Data Authentication (SDA) remain in circulation.

Edit 26 EMV3DS_Non_Low_Risk_Appr_Rt
Edit Number 23
Edit Criteria A transaction is considered nonperforming when SDA is present in DE 55,
subelement 82 (Application Interchange Profile [AIP]).
criteria:
Card supports offline CAM
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 any of the following:
• 82 (Application Interchange Profile [AIP])

Baseline/ Baseline: 500 eligible transactions

Contactless, AN 2871—Updates to EMV Offline CAM Requirements and
Associated Data Integrity Edits
Edit 26 EMV3DS_Non_Low_Risk_Appr_Rt
Edit Number 26
Edit Title Non Low Risk Transaction Approval Rate
Name EMV3DS_Non_Low_Risk_Appr_Rt
Region(s) Global, Select Asia/Pacific and Europe region countries excluded
Description This edit monitors issuers approval rates on authorizations for
Mastercard Identity Check EMV 3DS non-low risk authenticated
transactions. A transaction is considered not performing to Standards if
it is non-low risk via EMV 3DS and systematically declined by issuer.

Edit 27 EMV3DS_Full_Authent_Appr_Rt
Edit Number 26
Edit Criteria A nonperforming transaction is identified by the following criteria:
• DE 39 (Response Code) is not equal to 00, 08, 10 or 85
• DE 48, subelement 42 (Electronic Commerce Indicators) subfield 1
Indicator) has a value of 211
• DE 48, subelement 43 (Universal Cardholder Authentication Field
[UCAF]) starts with kE
Exclusions:
• DE 39 (Response Code) has a value of 51 (Insufficient funds/over
credit limit) or 61 (Exceeds withdrawal amount limits)
Countries excluded: Aland Islands, Andorra, Bangladesh, Belgium,
Denmark, Estonia, Falkland Islands (Malvinas), Faroe Islands, Germany,
Finland, France, French Guiana, Gibraltar, Greenland, Guadeloupe,
Guernsey, Iceland, India, Ireland, Isle of Man, Italy, Jersey, Kazakhstan,
Latvia, Liechtenstein, Lithuania, Luxembourg, Malaysia, Martinique,
Mayotte, Monaco, Netherlands, Nigeria, Norway, Portugal, Qatar,
Reunion, Russian Federation, Saint Barthelemy, Saint Helena, Ascension
and Tristan Da Cunha, Saint Martin, San Marino, Singapore, South
Georgia and South Sandwich Islands, Spain, Svalbard and Jan Mayen,
Sweden, Switzerland, and United Kingdom.
Countries excluded 1 May 2022: Albania, Austria, Bosnia and

Herzegovina, Bulgaria, Croatia, Cyprus, Czech Republic, Greece, Hungary,
Kosovo, Macedonia, Malta, Moldova, Montenegro, Poland, Romania,
Serbia, Slovakia, Slovenia, Ukraine, and Vatican City.
Countries excluded 1 November 2022: Nigeria and Qatar
Baseline/ Baseline: 1,000 e-commerce transactions with SLI 211

Guide, AN 4309 Data Integrity Monitoring Program, New Edits for
Mastercard Identity Check
Edit Number 27
Edit Title Fully Authenticated Transaction Approval Rate

Edit Number 27
Name EMV3DS_Full_Authent_Appr_Rt
Region(s) Global, Select European countries excluded
Description This edit monitors issuers approval rates on authorizations for
Mastercard Identity Check EMV 3DS fully authenticated transactions. A
transaction is considered not performing to Standards if it is fully
authenticated through EMV 3DS and declined by issuer.
Edit Criteria A nonperforming transaction is identified by the following criteria:
• DE 39 (Response Code) is not equal to 00, 08, 10 or 85
• DE 48, subelement 42 (Electronic Commerce Indicators) subfield 1
Indicator) has a value of 212 or 217
• DE 48, subelement 43 (UCAF) begins with a value of “k”
Exclusions:
• DE 39 (Response Code) has a value of 51 (Insufficient funds/over
credit limit) or 61 (Exceeds withdrawal amount limits)
• DE 48, subelement 43 has a leading indicator of kA, kC, or kO and DE
48, subelement 56, subfield 1 (Security Services Indicator) is AIQ
(Digital Transaction Insights) and the value in DE 48, subelement 56,
subfield 2 (Security Services Data) position 1 is 8 or higher.
• DE 48, subelement 71 (On-behalf [OB] Services), subfield 1 (OB
Service) value 05 (Mastercard Identity Check AAV Verification Service)
and subfield 2 (OB Result 1) value combinations:
– 05D (DS Transaction ID does not match with PAN and SPA2 AAV
within the authentication record).
– 05I (Invalid AAV).
– 05M (Monetary Currency mismatch between authorization and
authentication).

Edit 28 Contactless Issuer
Edit Number 27
• DE 48, subelement 87 (Card Validation Code Result) values:
– N (Invalid CVC 2 [non-match])
– P (CVC 2 not processed [issuer temporarily unavailable])
– U (CVC 2 Unverified—Mastercard Use Only)
• Systematic declines from Mastercard Safety Net.
Countries excluded: Germany, Kazakhstan, Liechtenstein, Switzerland,
and Russian Federation
Countries excluded 1 May 2022: Aland Islands, Albania, Andorra,
Antarctica, Austria, Belgium, Bosnia and Herzegovina, Bulgaria, Croatia,
Cyprus, Czech Republic, Denmark, Estonia, Falkland Islands (Malvinas),
Faroe Islands, Finland, France, French Guiana, French Polynesia,
Gibraltar, Greece, Greenland, Guadeloupe, Guernsey, Hungary, Iceland,
Ireland, Isle of Man, Italy, Jersey, Kosovo, Latvia, Lithuania, Luxembourg,
Macedonia, Malta, Martinique, Mayotte, Moldova, Montenegro,
Netherlands, Norway, Poland, Portugal, Reunion, Romania, Saint
Barthelemy, Saint Helena, Ascension and Tristan Da Cunha, Saint Martin,
San Marino, Serbia, Slovakia, Slovenia, South Georgia and the South
Sandwich Islands, Spain, Svalbard and Jan Mayen, Sweden, Ukraine,
United Kingdom and Vatican City.

Baseline/ Baseline: 1,000 e-commerce transactions with SLI 212 or 217

Guide, AN 4309 Data Integrity Monitoring Program, New Edits for
Mastercard Identity Check, AN 6378 Revised Criteria for Data Integrity
Monitoring Program Fully Authenticated Transaction Approval Rate Edit
Edit 28 Contactless Issuer
Edit Number 28
Edit Title Contactless Issuer
Name Contactless Issuer
Region(s) Asia/Pacific (excluding Japan), Europe, Middle East/Africa
Description This edit monitors that the percentage of cards under a given primary
issuer ICA number reported as contactless capable meet the thresholds
for that issuer’s region.

Edit 29 Do Not Honor 05 Declines 0110
Edit Number 28
Edit Criteria An issuer is considered nonperforming when the percentage of issuer
cards reported as contactless capable (compared to the overall number
of cards issued) does not meet the threshold for that issuer’s region.
Issuers will be monitored to help ensure that an increasing percentage of
their cards are contactless capable by the dates outlined in the Baseline/
Threshold for this edit.
The number of contactless capable cards (under a given issuer ICA
number) are determined by cards reported in the Quarterly Mastercard
Report (QMR) database by ICA number and region.

Baseline/ Baseline: 1,000 cards issued
Asia/Pacific and Europe:
Middle East/Africa:
Reference AN 1474 Revised Standards for EMV and Contactless Roadmap
Edit Number 29
Edit Title Do Not Honor 05 Decline Response 0110
Name Do Not Honor 05 Declines 0110
Region(s) Asia/Pacific (excluding India), Canada, Latin America and the Caribbean,
and United States
Description This edit monitors issuer usage of the decline reason code 05 (Do Not
Honor [DNH]) response for card-not-present (CNP) transactions in the
authorization response message.

Edit 30 Auth Refund Inv Declines 0110
Edit Number 29
criteria:
• Message Type Identifier is 0110 (Authorization Request Response)
• DE 61 (Point-of-Service [POS] Data), subfield 5 (POS Card Presence)
is 1 (CNP)
Transactions are considered nonperforming when more than 5% of an
ICA number or processor IDs decline responses are:
• DE 39 (Response code) value of 05 (Do Not Honor)
Decline responses are defined as any transaction whose response
contains a DE 39 value that is not equal to 00, 08, 10, 85, or 87
Exclusions:
• DE 48, Subelement 84 (Merchant Advice Codes) value of 21 (Payment
Cancellation)
• Mastercard generated declines (or on-behalf service declines)
• MDES provisioning request declines
• Stand-In services
• Systematic declines from Mastercard Safety Net
• Token provisioning request responses

Baseline/ Baseline: 20,000 Mastercard and Maestro CNP decline responses

Program: New Edits for Issuer Do Not Honor Declines for Select Regions
Edit 30 Auth Refund Inv Declines 0110
Edit Number 30
Edit Title Auth Refund Invalid Declines 0110
Name Auth Refund Inv Declines 0110
Region(s) Global
Description This edit monitors the validity of the issuer decline reason code for
purchase refund transactions in Authorization Request Response/0110
messages.

Edit 31 Auth Refund Appr Rt 0110
Edit Number 30
criteria:
Code) is 20 (Purchase Return/Refund)
• DE 39 (Response Code) in one of the following:
– 51 (Insufficient funds/over credit limit) or
• DE 39 value is 57 (Transaction not permitted to issuer/cardholder) and
the account is not flagged as non-reloadable prepaid
Exclusions:
PAN Entry Mode) value 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.)

Baseline/ Baseline: 1,000 purchase refund transactions
Reference Customer Interface Specification, GCMS Reference Manual, AN 6409 New

Data Integrity Monitoring Program Edits for Purchase Refund
Authorizations
Edit Number 31
Edit Title Auth Refund Approval Rate 0110
Name Auth Refund Appr Rt 0110
Region(s) Global
Description This edit monitors the monthly approval rate of purchase refund
transactions in Authorization Request Response/0110 messages.

Edit Number 31
criteria:
Code) is 20 (Purchase Return/Refund)
Issuers are considered nonperforming when they have 100 or more
purchase refund transactions in a given month, with 100% decline rates,
or 0% approval rates.
Excludes prepaid account ranges flagged with the non-reloadable
indicator in the Authorization BIN Resource file (TR52) or Financial
Institution Table (FIT) Optional Addendum Record (FIT1).

Baseline/ Baseline: 100 purchase refund transactions
Threshold Threshold: Greater than 0% approved
Reference Customer Interface Specification, GCMS Reference Manual, AN 6409 New

Data Integrity Monitoring Program Edits for Purchase Refund
Authorizations

Issuer Debit Single Message System Edits (0210)
Chapter 10 Issuer Debit Single Message System Edits

(0210)
0210/Financial Transaction message. In the Data Integrity Online application, the
program name appears in its abbreviated form, Iss Debit Single Msg (0210).
Retired edits.........................................................................................................................................................163
Edit 2 EMV_ARPC_0210....................................................................................................................................163
Edit 3 ISS_OFFLINE_CAM_0210......................................................................................................................164
Edit 4 Fallback Decline Rate 0210...................................................................................................................165
Edit 5 SDA Capable Cards 0210......................................................................................................................166
Edit 6 Do Not Honor 05 Declines 0210...........................................................................................................167

Retired edits
Retired edits
Edit 1 MoneySend Approval Rate (0210)
Edit 2 EMV_ARPC_0210
Edit Number 2
Edit Title ARPC Presence (0210)
Name EMV_ARPC_0210
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.
Edit Criteria Transactions are monitored under this edit when all of the following are
true:
• DE 39 (Response code) is one of the following:
• DE 55 is present in the originating 0100/Authorization Request with
all mandatory tags
A transaction is considered nonperforming when 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.

Baseline/ Baseline: 500 approved chip transactions
Threshold
Threshold: 98%

Edit Number 2
Edit Number 3
Title Issuer Offline CAM (0210)
Name ISS_OFFLINE_CAM_0210
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).
criteria:
• Card is capable of offline authentication
is 05 ( PAN auto-entry via chip)
• DE 39 (Response code) is any of the following:
– 85 (Not Declined)
An issuer is considered nonperforming when less than the current annual
threshold percent of eligible transactions show that CDA is supported in
DE 55, subelement 82 (Application Interchange Profile [AIP]) (Byte 1, bit
1).

Baseline/ Baseline: 500 offline CAM-capable card chip transactions
Threshold Threshold: Adjusts annually.

Edit Number 3
System Specifications, AN 2871—Updates to EMV Offline CAM
Requirements and Associated Data Integrity Edits
Edit Number 4
Edit Title Issuer Fallback Decline Rate (0210)
Name Fallback Decline Rate 0210
Region(s) Canada, Europe, Latin America and the Caribbean, Middle East/Africa
Description This edit monitors transactions submitted as technical fallback to ensure
they are being declined.
Edit Criteria A transaction is considered nonperforming when both of the following
are true:
is 80 ( Chip card at chip-capable terminal was unable to process
• DE 39 (Response Code) is any of the following:
Exclusions: Transactions with DE 3 (Processing Code), subfield 1
(Cardholder Transaction Type Code) equal to 20 (Refund/Correction) are
not monitored under this edit.
Transactions taking place at merchant locations in the United States and
Asia/Pacific are not monitored under this edit.

Baseline/ Baseline: 50 fallback transactions
Threshold
Threshold: 97%

Edit 5 SDA Capable Cards 0210
Edit Number 4
System Specifications, Transaction Processing Rules, AN 2237—Data
Integrity Monitoring Program—New Edits to Monitor Issuer Fallback
Transaction Approvals
Edit 5 SDA Capable Cards 0210
Edit Number 5
Edit Title SDA Capable Cards 0210
Name SDA Capable Cards 0210
Region(s) Global
Description This edit monitors the offline Card Authentication Method (CAM)
supported on offline CAM-capable cards to ensure that no cards with
Static Data Authentication (SDA) remain in circulation.
Edit Criteria A transaction is considered nonperforming when SDA is present in DE 55,
subelement 82 (Application Interchange Profile [AIP]).
criteria:
Card supports offline CAM
DE 22 (Point-of-Service [POS] Entry Mode), subfield 1 (POS Terminal
DE 39 (Response code) is any of the following:
• 82 (Application Interchange Profile [AIP])

Baseline/ Baseline: 500 eligible transactions

Edit Number 5
System Specifications, AN 2871—Updates to EMV Offline CAM
Requirements and Associated Data Integrity Edits
Edit Number 6
Edit Title Do Not Honor 05 Decline Response 0210
Name Do Not Honor 05 Declines 0210
Region(s) Asia/Pacific (excluding India), Canada, Latin America and the Caribbean,
and United States
Description This edit monitors issuer usage of the decline reason code 05 (Do Not
Honor [DNH]) response for card-not-present (CNP) transactions in the
Financial Transaction Request Response message.
criteria:
• MTI (Message Type Identifier) is 0210 (Financial Transaction Request
Response)
is 1 (CNP)
Transactions are considered nonperforming when more than 5% of an
ICA number or processor IDs decline responses are:
• DE 39 (Response code) value of 05 (Do Not Honor)
Decline responses are defined as any transaction whose response
contains a DE 39 value that is not equal to 00, 08, 10, 85, or 87
Exclusions:
• DE 48, Subelement 84 (Merchant Advice Codes) value of 21 (Payment
Cancellation)
• Mastercard generated declines (or on-behalf service declines)
• MDES provisioning request declines
• Stand-In services
• Systematic declines from Mastercard Safety Net
• Token provisioning request responses

Edit Number 6
Baseline/ Baseline: 20,000 Mastercard and Maestro CNP decline responses

Program: New Edits for Issuer Do Not Honor Declines for Select Regions

Issuer Chargeback Program
Chapter 11 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.............................................................................................................................170
Edit 2 ISS_FNS....................................................................................................................................................170
Edit 3 ISS_Invalid_CLS.......................................................................................................................................171

Edit 1 ISS_EXCESSIVE_CBS
Edit 1 ISS_EXCESSIVE_CBS
Edit Number 1
Edit Title Issuer Excessive Chargebacks
Name ISS_EXCESSIVE _CBS
Regions Global
Description This edit monitors the number of chargebacks submitted on a single
Primary Account Number (PAN) each month.
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 nonperforming when 20 or more chargebacks are
submitted on the same PAN for each of two consecutive months.

Baseline/ Baseline: 1 chargeback
Threshold:
Threshold: Fewer than 20 errors for each PAN
Reference IPM Clearing Formats, Security Rules and Procedures, AN 2170 Data
Integrity Monitoring Program - New Edits to Monitor Issuer Chargebacks
Edit 2 ISS_FNS
Edit Number 2
Edit Title Issuer Fraud Notification Service
Name ISS_FNS

Edit 3 ISS_Invalid_CLS
Edit Number 2
Regions Global
Description This edit monitors chargebacks to ensure that issuers are not
circumventing the Fraud Notification Service (FNS) block rule.
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 nonperforming when a single PAN has 15 fraud
chargebacks, followed by five non-fraud chargebacks in a given month.
Important: Data Integrity Online displays the number of non-fraud

chargebacks after the issuer has submitted 15 fraud chargebacks. So, a
display of 5 errors or more indicates the customer is nonperforming.

Threshold
Threshold: Fewer than 5 errors for each PAN
Edit Number 3
Edit Title Issuer Invalid Chip Liability Shift
Name ISS_Invalid_CLS
Region(s) Global

Edit Number 3
Description This edit monitors issuers submitting Invalid Chip Liability Shift (CLS)
chargebacks.
Edit Criteria An issuer is considered nonperforming 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
Exclusions: Reversals

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

Digital Standards Program
Chapter 12 Digital Standards Program

The edits in this program evaluate transactions in support of the Digital Standards
Program to help issuers to improve card-not-present (CNP) approval rates across
consumer debit, mass credit, affluent credit and prepaid reloadable card products.
About Digital Standards Program...................................................................................................................174

Edit 1 CNP APP RT CREDIT 0110....................................................................................................................175
Edit 2 CNP APP RT DEBIT 0110...................................................................................................................... 177
Edit 3 CNP APP RT CR WORLD 0110.............................................................................................................180
Edit 4 CNP APP RT PREPAID 0110................................................................................................................. 183

About Digital Standards Program
About Digital Standards Program

The Digital Standards Program (DSP) applies to issuer portfolios that meet the
baseline number of transactions by country or market, by year for each edit.
Every quarter, issuer performance will be assessed against the annual benchmark
with assessments calculated at the transaction level.
Performance will be based on Mastercard processed data and will include domestic
and cross-border CNP transactions, excluding Mastercard®, MoneySend™ (funding
and payments), and EMV® 3-D Secure (3DS) transactions. All issuer responded
decline reason codes will be considered with the exception of credit related declines
(DE 39 Response Code 51)7. Approval rate performance will be calculated based
on approval rate count data with declined transaction duplicates removed.
The edits monitor issuers in all countries in the Latin America and Caribbean (LAC)
region, excluding Mexico, Puerto Rico and the Virgin Islands, U.S. Additionally the
edits monitor issuers in the following Eastern Europe and Middle East/Africa
countries: Azerbaijan, Bahrain, Egypt, Ghana, Iraq, Kazakhstan, Kenya, Kuwait,
Lebanon, Morocco, Oman, Pakistan, Qatar, Saudi Arabia, South Africa, Turkey, and
United Arab Emirates.
For LAC, the DSP will monitor domestic and cross-border CNP transactions,
except where there are regulatory restrictions; Argentina will only include domestic
transactions. The covered markets will be individual countries in the case of Brazil
and clusters of countries for the remainder of the LAC region based on adjacent
markets with similar performances as listed in Table 13: Country markets.
Table 13: Country markets
Market Countries included

Argentina and Argentina (ARG), Uruguay (URY)
Uruguay
Brazil Brazil (BRA)
Caribbean Anguilla (AIA), Antigua and Barbuda (ATG), Aruba (ABW), Bahamas
(BHS), Barbados (BRB), Belize (BLZ), Bermuda (BMU), Bonaire Saint
Eustatius & Saba (BES), Cayman Islands (CYM), Cuba (CUB), Curacao
(CUW), Dominica (DMA), Dominican Republic (DOM), Grenada (GRD),
Haiti (HTI), Jamaica (JAM), Montserrat (MSR), Saint Kitts and Nevis
(KNA), Saint Lucia (LCA), Saint Maarten (SXM), St. Vincent and The
Grenadines (VCT), Trinidad and Tobago (TTO), Turks and Caicos Islands
(TCA), Virgin Islands British (VGB)
7 Cryptocurrency-related CNP transactions (DE 48, subelement 77 Transaction Type Identifier P70) are
excluded from monitoring for all of Eastern Europe and Middle East/Africa countries.

Edit 1 CNP APP RT CREDIT 0110
Market Countries included

Central Costa Rica (CRI), El Salvador (SLV), Guatemala (GTM), Honduras (HND),
America Nicaragua (NIC), Panama (PAN)
Chile and Chile (CHL), Paraguay (PRY)
Paraguay
Colombia and Colombia (COL), Ecuador (ECU)
Ecuador
Peru and Bolivia (BOL), Peru (PER)
Bolivia
Venezuela, Guyana (GUY), Suriname (SUR), Venezuela (VEN)
Guyana and
Suriname
For Eastern Europe and the Middle/East Africa region, the DSP will monitor
domestic and cross-border CNP transactions except where there are regulatory
restrictions: Azerbaijan, Kazakhstan, Morocco, and Turkey will only include cross-
border transactions.
Edit Number 1
Edit Title Card Not Present Consumer Credit Approval Rate 0110
Name CNP APP RT CREDIT 0110
Region(s) Latin America and the Caribbean, excluding Mexico, Puerto Rico and the
Virgin Islands, U.S., select Europe countries (Azerbaijan, Kazakhstan, and
Turkey) and select Middle East/Africa Countries (Bahrain, Egypt, Ghana,
Iraq, Kenya, Kuwait, Lebanon, Morocco, Oman, Pakistan, Qatar, Saudi
Arabia, South Africa, and United Arab Emirates)
Description This edit monitors issuer’s minimum approval rate for domestic and
cross-border card not present (CNP) consumer credit transactions.

Edit Number 1
Edit Criteria An issuer is considered nonperforming when the quarterly approval rate
for all qualified transactions is below Market (target) Threshold percent
and there is not greater than one percent quarter over quarter
improvement over the issuer’s prior year approval rate.
Eligible transactions monitored under this edit are identified by the
following criteria:
is 1 (Card not present)
• DE 48, subelement 33, subfield 4 (product code)
– for LAC is MCA, MCC, MCE, MCG, MCS, MCU, MCV, MHC, MHG,
MHP, MHS, MIB, MIC, MIG, MNS, MRF, MRO, or MRP
– for MEA is MCA, MCC, MCE, MCG, MCH, MCS, MCT, MCU, MCV,
MCX, MFD, MFL, MHC, MHG, MHP, MHS, MIB, MIC, MIG, MKE,
MNS, MPL, MRF, MRO, or MRP
cryptogram in DE 55 (Integrated Circuit Card System-Related
Data)
Eligible transactions are considered noncompliant if the DE 39 (Response
code) is not any of the following:

Edit 2 CNP APP RT DEBIT 0110
Edit Number 1
NOTE:
• Argentina is monitored on domestic transactions only.
• Azerbaijan, Kazakhstan, Morocco, and Turkey are monitored on cross-
border transactions only.
– Cross-border is identified when the value in DE 20 (Primary
Account Number [PAN] Country Code) does not match the value in
DE 43 (Card Acceptor Name/Location for All Transactions),
subfield 5 (Card Acceptor Country Code)
• An issuer of accounts in Turkey may have their minimum average
approval rate adjusted by 4 percent for cross-border CNP transactions
for a covered consumer product type.
Monitoring start date:

• 1 January 2021 for Bahrain, Kuwait, Oman, Qatar, Saudi Arabia, and
United Arab Emirates
• 1 January 2022 for LAC countries
• 1 January 2023 for Azerbaijan, Egypt, Ghana, Iraq, Kazakhstan,
Kenya, Lebanon, Morocco, Pakistan, South Africa, and Turkey
Baseline/ Baseline 300,000 prior year CNP consumer credit transactions

Threshold
Target Threshold: Annual average market/product approval rate
Issuer Threshold: Prior year issuer/market/product approval rate

Program: New Digital Standards Program and Edits for Select Countries in
the Middle East/Africa Region, AN 5602 Data Integrity Monitoring
Program: New Digital Standards Program and Edits in the Latin America
and Caribbean Region, AN 7210 Revision to the Data Integrity Monitoring
Program Digital Standards Program Edits for Select Countries in the
Europe and Middle East/Africa Regions
Edit Number 2
Edit Title Card Not Present Consumer Debit Approval Rate 0110
Name CNP APP RT DEBIT 0110

Edit Number 2
Region(s) Latin America and the Caribbean excluding Mexico, Puerto Rico and the
cross-border card not present (CNP) consumer debit transactions.

Edit Number 2
following criteria:
• DE 48, subelement 33, subfield 4 (product code) for LAC and MEA is
ACS, DAG, DAP, DAS, DDG, DDS, DLG, DLH, DLI, DLP, DLS, DLU,
DOS, MCD, MCI, MDE, MDG, MDI, MDJ, MDK, MDO, MDP, MDR, MDS,
MDU, MED, MEP, MET, MHD, MHL, MHM, MHN, MID, MIH, MIJ, MIS,
MIU, MKA, MKB, MOC, MPJ, MSD, MUP, MXG, MXO, MXP, MXR, MXS,
SAG, SAP, SAS, SOS, TCC, TCE, TCG, TCS, TIB, TIC, TIU, or TPL
Data)
Eligible transactions are considered nonperforming when the DE 39
(Response code) is not any of the following:

Edit 3 CNP APP RT CR WORLD 0110
Edit Number 2
NOTE:

Baseline/ Baseline: 300,000 prior year CNP consumer debit transactions

Threshold

Edit Number 3
Edit Title Card Not Present Consumer World and World Elite Approval Rate 0110
Name CNP APP RT CR WORLD 0110

Edit Number 3
Description This edit monitors issuer's minimum approval rate for domestic and
cross-border card not present (CNP) consumer credit World and World
Elite transactions.
following criteria:
• DE 48, subelement 33, subfield 4 (product code)
– for LAC is MBK, MCH, MCT, MCW, MFB, MFD, MFE, MFH, MFL,
MFW, MHW, MNW, MPL, MUW, MWD, MWE, MWR, WBE, or WMR
– for MEA is MFB, MFE, MKG, MKH, MWE, MBK, MCW, MFH, MFW,
MHW, MKF, MNW, MUW, MWD, MWR, WBE, or WMR
Data)

Edit Number 3
NOTE:

Baseline/ Baseline: 300,000 prior year CNP consumer credit World and World Elite
Threshold transactions

Program New Digital Standards Program and Edits in the Latin America

Edit 4 CNP APP RT PREPAID 0110
Edit Number 4
Edit Title Card Not Present Consumer Prepaid Approval Rate 0110
Name CNP APP RT PREPAID 0110
cross-border card not present (CNP) consumer prepaid transactions.

Edit Number 4
following criteria:
• DE 48, subelement 33, subfield 4 (product code) for LAC and MEA is
DWF, MBB, MGP, MGS, MHA, MHB, MHH, MIA, MIK, MIL, MIP, MPA,
MPD, MPF, MPG, MPH, MPM, MPN, MPO, MPP, MPQ, MPR, MPT, MPV,
MPX, MPY, MPZ, MRC, MRD, MRG, MRH, MRJ, MRS, MTP, MUS, MWF,
MWP, or SUR
Data)
NOTE:

Edit Number 4
Baseline/ Baseline: 300,000 prior year CNP consumer prepaid transactions

Threshold Target Threshold: Annual average market/product approval rate

the Middle East/Africa Region, AN 5602 Data Integrity Monitoring,

Global Collection Only Edits
Chapter 13 Global Collection Only Edits

The edits in this program monitor reporting of Global Collection Only Edits (GCO) volume
as well as the data quality in the 1240/First Presentment messages of collection-only
transactions.
About Global Collection Only edits..................................................................................................................187

Edit 1 GCO_Reporting....................................................................................................................................... 187
Edit 2 GCO INVALID MCC.................................................................................................................................188
Edit 3 GCO INVALID MERCH ID.......................................................................................................................189
Edit 4 GCO INVALID DE43................................................................................................................................190
Edit 5 GCO INVALID COUNTRY.......................................................................................................................191
Edit 6 GCO INVALID STREET........................................................................................................................... 192
Edit 7 GCO INVALID CITY................................................................................................................................. 193
Edit 8 GCO INVALID TIME.................................................................................................................................194
Edit 9 GCO Quarterly Reporting......................................................................................................................195

About Global Collection Only edits
About Global Collection Only edits
According to the Global Collection Only Program 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
Edit 1 GCO_Reporting
Edit Number 1
Edit Title GCO Reporting
Name GCO_Reporting
Region(s) Europe
Description This edit monitors collection-only transactions to ensure that customers
are accurately reporting their Global Collection Only (GCO) volume.
Edit Criteria Customers are considered nonperforming 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
Threshold and 95% or less of total transaction volume processed on the GCO
network to be monitored.
Threshold: 80%

Edit 2 GCO INVALID MCC
Edit Number 1
Reference Global Collection Only Program Handbook
Edit 2 GCO INVALID MCC
Edit Number 2
Edit Title GCO Invalid MCC
Name GCO INVALID MCC
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.
Edit Criteria A merchant location is considered nonperforming when 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

Edit 3 GCO INVALID MERCH ID
Edit Number 2
Baseline/ Baseline: 500 unique merchant locations
Threshold
Threshold: 98% of merchant locations
Reference Global Collection Only Program Handbook, IPM Clearing Formats, Quick
Reference Booklet, AN 1397 Data Integrity - New Edits- Global Collection
Only Data Quality Edits
Edit 3 GCO INVALID MERCH ID
Edit Number 3
Edit Title GCO Invalid Merchant ID
Name GCO INVALID MERCH ID
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.

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)

Threshold

Edit 4 GCO INVALID DE43
Edit Number 3
Reference IPM Clearing Formats, AN 1397 Data Integrity - New Edits- Global
Collection Only Data Quality Edits
Edit 4 GCO INVALID DE43
Edit Number 4
Edit Title GCO Invalid DE 43
Name GCO INVALID DE43
Region(s) Global
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.
criteria:
a. DE 43 (Card Acceptor Name/Location) , subfield 1 (Card Acceptor
Name) is a street address
b. 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
c. DE 43, subfield 1 is all numeric, all one character or all sequential
characters (for example ABCDEF)
d. DE 43, subfield 1, positions 20-22 contain the following substring
“PAA”
e. DE 43, subfield 1, positions 20-22 contain the following substring “Rxx”
f. DE 43, subfield 1, positions 20-22 contain the following substring “Sxx”
g. DE 43, subfield 1, positions 20-22 contain the following substring
“Wxx”
h. DE 43, subfield 1, positions 20-22 contain the following substring “PAY”
Exclusions: Transactions with MCC 4784 (Bridge and road fees, tolls)
Threshold Threshold: 98% of merchant locations

Edit 5 GCO INVALID COUNTRY
Edit Number 4
Reference Global Collection Only Program Handbook, IPM Clearing Formats, AN
1397 Data Integrity - New Edits- Global Collection Only Data Quality Edits
Edit 5 GCO INVALID COUNTRY
Edit Number 5
Edit Title GCO Invalid Country
Name GCO INVALID COUNTRY
Region(s) This edit applies to the following countries: Afghanistan, Albania,
Argentina, Australia, Austria, Belgium, Brazil, Canada, Colombia, Costa
Rica, Croatia, Czech Republic, Denmark, Finland, France, Germany,
Greece, Hungary, India, Israel, Italy, Japan, Korea, Kuwait, Malaysia,
Netherlands, New Zealand, Norway, Philippines, Poland, Puerto Rico,
Russian Federation, Singapore, South Africa, Sweden, Switzerland,
Taiwan, Thailand, Turkey, Ukraine, United Kingdom, United States,
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 6 GCO INVALID STREET
Edit Number 5
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 CHE, CRI, DNK, ISR, KOR, KWT, NOR, NZL, PHL,
PRI, THA, TUR, TWN, or VEN and DE 43, subfield 4 is “unknown” or is
not present
• DE 43, subfield 6 is AFG, ALB, ARG, AUT, BEL, BRA, CHE, COL, CZE,
SGP, SWE, UKR or ZAF and DE 43, subfield 4 is “unknown” or is not
present or is not in the correct format. Exclusions: Airline transactions
MCC in DE 26 is 3000-3350 or 4511
Exclusions: Transactions with MCC 4784 (Bridge and road fees, tolls)
Monitoring start date: 1 January 2018 and 1 February 2021 for new
countries in last two bullets

1397 Data Integrity - New Edits- Global Collection Only Data Quality
Edits, AN 4589 Data Integrity Monitoring Program: Updates to Existing
Edits for Global Address Standardization
Edit 6 GCO INVALID STREET
Edit Number 6
Edit Title GCO Invalid Street Address
Name GCO INVALID STREET
Region(s) Global

Edit 7 GCO INVALID CITY
Edit Number 6
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 transaction is considered nonperforming when either of the following
subedits apply:
a. 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
Exception: A value of “RR” is permitted in Canada
c.
• DE 43, subfield 1 matches DE 43, subfield 2 (Spaces, character case
and special characters are removed prior to matching.)
road fees, tolls)
Monitoring start date: 1 January 2018 for subedit a. 1 February 2021 for
subedit c.
Reference IPM Clearing Formats, AN 1397 Data Integrity - New Edits- Global
Collection Only Data Quality Edits, AN 4589 Data Integrity Monitoring
Program: Updates to Existing Edits for Global Address Standardization
Edit 7 GCO INVALID CITY
Edit Number 7
Edit Title GCO Invalid City
Name GCO INVALID CITY
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 8 GCO INVALID TIME
Edit Number 7
criteria:
a. Globally, DE 43, subfield 3 (Card Acceptor City) contains invalid

character sets for the specified country code page
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.
road fees, tolls)


Edit 8 GCO INVALID TIME
Edit Number 8
Edit Title GCO Invalid Time
Name GCO INVALID TIME
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 9 GCO Quarterly Reporting
Edit Number 8
transactions taking place at that location have identical values in DE 12
(Date and Time, Local Transaction), subfield 1 (Date) and subfield 2
(Time).

Threshold

Edit 9 GCO Quarterly Reporting
Edit Number 9
Edit Title GCO Quarterly Reporting
Name GCO Quarterly Reporting
Region(s) Asia/Pacific, Latin America and the Caribbean, and Middle East/Africa
Description This edit monitors collection-only transactions to ensure that customers
are accurately reporting their Global Collection Only (GCO) volume.
Edit Criteria Customers are considered nonperforming when the GCO Reporting
percentage is below 90% of the same quarter's Reported volume.
NOTE: Europe will be monitored on Edit 1: GCO Reporting

Baseline/ Baseline: Customers must have at least 25,000 eligible GCO transactions
Threshold and 5% or more of GCO activity on total transaction volume to be
monitored.
Threshold: 90%
Reference Global Collection Only Program Handbook

Mastercard Identity Check (AReq/ARes)
Chapter 14 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 authenticated through 3DS 1.0 are not
monitored under this program.
Retired edits.........................................................................................................................................................197
Mastercard Identity Check (AReq/ARes) exclusions.....................................................................................197
Edit 1 Authentication Rate............................................................................................................................... 198
Edit 2 Authn Non-Static Method.....................................................................................................................199
Edit 3 ACS Authn Error Rate............................................................................................................................ 199
Edit 4 3DSS Authn Error Rate..........................................................................................................................200
Edit 5 ACS Availability....................................................................................................................................... 201
Edit 7 3RI_AUTH_TRANS_DECLINE................................................................................................................ 201
Edit 8 ACS_AUTHEN_ABANDON_RATE......................................................................................................... 202
Edit 9 CHALLENGE_FLOW_3DS.....................................................................................................................202
Edit 11 ISS_AUTH_SCA_EXEMP......................................................................................................................203
Edit 12 BIOMETRIC_AUTH_RATE.................................................................................................................... 204

Retired edits
Retired edits
Edit 6 ACS Latency (Retired from active monitoring)

Edit 10 SPA2_ALGRTHM_ADOPTION (Retired from active monitoring)
Mastercard Identity Check (AReq/ARes) exclusions

Issuers in the countries listed in Table14: Mastercard Identity Check excluded
countries are exempted from the following edits.
• Issuer Authentication Non-Static Method (ARes)
• Issuer Authentication Rate (ARes)
• Issuer Authentication Abandonment Rate (RReq)
Table 14: Mastercard Identity Check excluded countries
Country
Albania France Lithuania Slovakia
Andorra Georgia Luxembourg Slovenia
Armenia Germany Macedonia Spain
Austria Gibraltar Malta Sweden
Azerbaijan Greece Moldova Switzerland
Belarus Hungary Monaco Tajikistan
Belgium Iceland Montenegro Turkey
Bosnia and Ireland Netherlands Turkmenistan
Herzegovina
Bulgaria Israel Norway Ukraine
Croatia Italy Poland United Kingdom
Cyprus Kazakhstan Portugal Uzbekistan
Czech Republic Kosovo Romania Vatican City
Denmark Kyrgyzstan Russian Federation
Estonia Latvia San Marino
Finland Liechtenstein Serbia

Edit 1 Authentication Rate
Edit 1 Authentication Rate
Edit Number 1
Edit Title Issuer Authentication Rate (ARes)
Name Authentication Rate
Region(s) Global
Description This edit monitors the Authentication Response (ARes) messages to
determine the issuer’s overall authentication rate.
Edit Criteria Issuers are considered nonperforming when more than 15% of
authentication requests are not authenticated.
Authenticated transactions are identified by the EMV 3DS Specification
data element definition of Transaction Status. A value of Y indicates that
the transaction was successfully authenticated.
Exclusions: Authentications that use a cardholder challenge
Countries excluded: 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, Russian Federation, San Marino, Serbia,
Slovakia, Slovenia, Spain, Sweden, Switzerland, Tajikistan, Turkey,
Turkmenistan, Ukraine, United Kingdom, Uzbekistan, and Vatican City
Countries excluded 1 November 2022: Nigeria and Qatar
Countries excluded after 31 December 2022: Aland Islands, Antarctica,
Falkland Islands (Malvinas), Faroe Islands, French Guiana, Greenland,
Guernsey, Isle of Man, Jersey, Liechtenstein, Martinique, Mayotte,
Reunion, Saint Barthelemy, Saint Helena, Ascension and Tristan Da
Cunha, Saint Martin, South Georgia and the South Sandwich Islands,
and Svalbard and Jan Mayen

Reference Mastercard Identity Check Program Guide, AN 2401 Data Integrity

Monitoring Program New Edits for EMV 3-D Secure and New Alerts and
Notifications Feature, AN 2853 Data Integrity Monitoring Program
Updates to Existing Programs and New Edits to Monitor 3DS Activity

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


Edit 3 ACS Authn Error Rate
Edit Number 3
Edit Title Issuer ACS Authentication Error Rate (ARes)
Name ACS Authn Error Rate
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 4 3DSS Authn Error Rate
Edit Number 3
Edit Criteria Authentication messages from issuer’s ACS are considered
nonperforming when they result in an error message.

Edit 4 3DSS Authn Error Rate
Edit Number 4
Edit Title Acquirer 3DSS Authentication Error Rate
Name 3DSS Authn Error Rate
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
nonperforming when they result in an error message.


Edit 5 ACS Availability
Edit 5 ACS Availability
Edit Number 5
Edit Title Issuer ACS Availability (ARes)
Name ACS Availability
Region(s) Global
Description This edit monitors the Access Control server (ACS) response rate to
Authentication Request (AReq) messages.
Edit Criteria Issuers are considered nonperforming when the ACS fails to respond to
more than 1% of AReq messages.

Edit 7 3RI_AUTH_TRANS_DECLINE
Edit Number 7
Edit Title 3DS Requestor Initiated (ARes)
Name 3RI_AUTH_TRANS_DECLINE
Region(s) Global
Description This edit monitors 3DS Requestor Initiated (3RI) transactions to ensure
issuers are able to support the 3RI flow.
Edit Criteria Issuers are considered nonperforming when they respond to all 3RI
requests with a value of N, R, or U in the ARes, indicating they are unable
to support 3RI transactions.

Edit 8 ACS_AUTHEN_ABANDON_RATE
Edit Number 7
Baseline/ Baseline: 100 3RI transactions

Monitoring Program Updates to Existing Programs and New Edits to
Monitor 3DS Activity
Edit 8 ACS_AUTHEN_ABANDON_RATE
Edit Number 8
Edit Title Issuer Authentication Abandonment Rate (RReq)
Name ACS_AUTHEN_ABANDON_RATE
Region(s) Global - Select European countries excluded. (See excluded country list in
Exclusions.)
Description This edit monitors challenge responses sent by the issuer Access Control
Server (ACS) to the Directory Server (DS) to ensure that issuers are
executing the challenge flow as required.
Edit Criteria Issuers are considered nonperforming when more than 10% of challenge
responses contain the cancellation indicator.

Edit 9 CHALLENGE_FLOW_3DS
Edit Number 9
Edit Title Acquirer Challenge Flow Execution Rate (ARes/RReq)
Name CHALLENGE_FLOW_3DS

Edit 11 ISS_AUTH_SCA_EXEMP
Edit Number 9
Region(s) Global
Description This edit monitors the ARes and RReq messages to ensure merchants
execute the challenge flow when they receive a challenge response from
an issuer ACS.
Edit Criteria An acquirer is considered nonperforming when more than 10% of
challenge responses are abandoned by the merchant.
Monitoring start date : 1 September 2019

Edit 11 ISS_AUTH_SCA_EXEMP
Edit Number 11
Edit Title 3DS Issuer Authentication Rate for SCA Exemption
Name ISS_AUTH_SCA_EXEMP
Sweden and United Kingdom).
Description This edit monitors European PSD2 issuers who are not allowing Strong
Consumer Authentication (SCA) delegation or acquirer exemptions when
requested.

Edit 12 BIOMETRIC_AUTH_RATE
Edit Number 11
Edit Criteria A transaction is considered nonperforming when:
• Both issuer and acquirer are in one of the listed countries.
• The authentication request contains a request for acquirer exemption
or SCA delegation (sca Exemption = 05 or 07 in v2.1, Challenge
Indicator = 05 or 07 in V2.2) and the issuer Access Control Server
(ACS) does not respond with an:
– ARes = N with Reason Code 81 and with Electronic Commerce
Indicator (ECI) 06 in v2.1, or
– ARes = I with ECI 06 in v2.2, or
– ARes = Y with ECI 02

Baseline/ Baseline: 1,000 EMV 3DS Transactions
Reference Authentication Guide for Europe, AN 4517 Data Integrity Monitoring

Program: New Edits for Mastercard Identity Check
Edit Number 12
Edit Title Biometric Authentication Rate
Name BIOMETRIC_AUTH_RATE
Sweden and United Kingdom).
Description This edit identifies European issuers who have not implemented a
biometric authentication solution in accordance with the Mastercard
Identity Check program rule.

Edit Number 12
Edit Criteria A transaction is considered nonperforming when:
• Both issuer and acquirer are in one of the listed countries
• The issuers Access Control Server (ACS) challenges the cardholder but
does not perform Strong Consumer Authentication (SCA) via
biometric authentication (Authentication Method = 07 in RReq)

Baseline/ Baseline: 1,000 EMV 3DS Transactions
Reference Authentication Guide for Europe, Mastercard Biometric Authentication–

Europe Region, AN 4517 Data Integrity Monitoring Program: New Edits for
Mastercard Identity Check

Fraud Reporting Performance Program
Chapter 15 Fraud Reporting Performance Program

The edits in this program monitor issuers' performance with the Fraud and Loss
Database (FLD) to help ensure issuers are submitting and managing fraudulent
transactions according to the new FLD fraud reporting requirements and that issuers
report all fraud data using the appropriate FLD functionality to record fraudulent events
accurately and in a timely manner.
Edit 1 Rejects.......................................................................................................................................................207
Edit 2 Suspends Suspicious Amount...............................................................................................................207
Edit 3 Suspends Amount Difference...............................................................................................................208
Edit 4 Deletes......................................................................................................................................................209

Edit 1 Rejects
Edit 1 Rejects
Edit Number 1
Edit Title Rejects
Name Rejects
Region(s) Global
Description This edit monitors the number of resubmitted rejected transactions in
relation to the total number of rejected transactions an issuer submits to
the Fraud and Loss Database (FLD) in a given month.
Edit Criteria An issuer is considered nonperforming when 10 percent or more of
rejected transactions are not resubmitted into FLD within 30 days of the
original submission date.
Baseline/ Baseline: 50 rejected transactions
Threshold
Threshold: 90%
Reference Fraud & Loss Database Guide, Security Rules and Procedures, Chapter 12
Fraud Reporting Standards, AN 5660 Data Integrity Monitoring Program:
New Fraud Reporting Performance Program Edits
Edit 2 Suspends Suspicious Amount
Edit Number 2
Edit Title Suspends Suspicious Amount
Name Suspends Suspicious Amount
Region(s) Global
Description This edit monitors when issuers either confirm, modify, or delete
suspended transactions within the required time frame.
Transactions can be suspended as a suspicious amount.

Edit 3 Suspends Amount Difference
Edit Number 2
Edit Criteria A transaction is considered nonperforming when a suspended
transaction previously submitted into the Fraud and Loss Database
(FLD) is not confirmed, modified, or deleted within 30 days of the original
submission.
A suspended transaction is identified by:
• Error Code 24800 (transaction amount is greater than USD 25,000)
An issuer is considered nonperforming when they have a single
transaction with Error Code 24800 (suspended transaction).
NOTE: If issuer is nonperforming on either of the Suspends Suspicious

Amount or Suspends Amount Difference they are charged only once for
the highest tier count.

Baseline/ Baseline: 1 suspended transaction
Threshold Threshold: 1 suspended transaction with Error Code 24800
Reference Fraud & Loss Database Guide, Security Rules and Procedures, Chapter 12
Fraud Reporting Standards, AN 5660 Data Integrity Monitoring Program:
New Fraud Reporting Performance Program Edits
Edit 3 Suspends Amount Difference
Edit Number 3
Edit Title Suspends Amount Difference
Name Suspends Amount Difference
Region(s) Global
Description This edit monitors if issuers either confirm, modify, or delete suspended
transactions with an amount difference within 30 days of the original
submission date.

Edit 4 Deletes
Edit Number 3
Edit Criteria A transaction is considered nonperforming when a suspended
transaction previously submitted into the Fraud and Loss Database
(FLD) is not confirmed, modified, or deleted within 30 days of the original
submission.
A suspended transaction is identified by:
• Error Code 24511 (where the transaction amount and the cardholder
billing amount differ by more than 25 percent when converted to
USD)
An issuer is considered nonperforming when they have 20 or more
outstanding suspended transactions with Error Code 24511.
NOTE: If issuer is nonperforming on either of the Suspends Suspicious

Amount or Suspends Amount Difference they are charged only once for
the highest tier count.

Baseline/ Baseline: 1 suspended transaction
Reference Fraud and Loss Database Guide, Security Rules and Procedures, Chapter
12 Fraud Reporting Standards, AN 5660 Data Integrity Monitoring
Program: New Fraud Reporting Performance Program Edits
Edit 4 Deletes
Edit Number 4
Edit Title Deletes
Name Deletes
Region(s) Global
Description This edit monitors the number of deleted transactions in relation to the
total number of successful fraudulent transactions an issuer submits to
the Fraud and Loss Database (FLD) in a given month.
Edit Criteria An issuer is considered nonperforming when the total number of deleted
transactions are 8 percent or more of the total number of successful
fraudulent transactions an issuer submits to FLD in a given month.

Edit 4 Deletes
Edit Number 4
Baseline/ Baseline: 100 fraud transactions
Threshold
Threshold: 92%
Reference Fraud and Loss Database Guide, Security Rules and Procedures, Chapter
12 Fraud Reporting Standards, AN 5660 Data Integrity Monitoring
Program: New Fraud Reporting Performance Program Edits

Addendum Data Performance Program
Chapter 16 Addendum Data Performance Program

The edits in this program monitor financial detail addendum transactions to help ensure
that acquirers processing financial detail addendum messages are sending complete,
verified, and accurate information as set forth in the Mastercard Rules.
Edit 1 PDS 0507 Issuing Carrier...................................................................................................................... 212

Edit 2 PDS 0509 Issue Date............................................................................................................................. 212
Edit 3 PDS 0520 Travel Date............................................................................................................................213
Edit 4 PDS 0574 Arrival Date...........................................................................................................................214
Edit 5 PDS 0577 Property Phone Number.....................................................................................................215

Edit 1 PDS 0507 Issuing Carrier
Edit 1 PDS 0507 Issuing Carrier
Edit Number 1
Edit Title PDS 0507 Issuing Carrier
Name PDS 0507 Issuing Carrier
Region(s) Global
Description This edit monitors financial detail addendum messages for the presence
and validity of values in PDS 0507 (Issuing Carrier), which contains the
standard abbreviation for the airline or railway carrier issuing the ticket.
Edit Criteria When PDS 0507 is populated, the value in the field will be considered
nonperforming when:
• PDS 0507 is not left-justified and contains all low values, all high
values, all spaces, or all zeros or
• an invalid IATA (International Air Transport Association) is provided
NOTE: For airline transactions, the carrier code is obtained from the
Official Airline Guide (OAG) or its equivalent.

Baseline/ Baseline: 500 addendum transactions
Threshold
Threshold: 98%
Reference IPM Clearing Formats, Mastercard Rules, AN 6743 New Data Integrity
Monitoring Program Edits for Addendum Data
Edit 2 PDS 0509 Issue Date
Edit Number 2
Edit Title PDS 0509 Issue Date
Name PDS 0509 Issue Date
Region(s) Global

Edit 3 PDS 0520 Travel Date
Edit Number 2
Description The edit monitors financial detail addendum messages for the presence
and formatting of the values in PDS 0509 (Issue Date), which contains
the date the ticket was issued to the customer.
nonperforming when:
• PDS 0509 is not a valid date or is not in the form of YYMMDD.
– YY must be plus or minus 3 years from current date
– MM must be between 01 to 12
– DD must be between 01 to 31

Threshold
Threshold: 98%
Edit 3 PDS 0520 Travel Date
Edit Number 3
Edit Title PDS 0520 Travel Date
Name PDS 0520 Travel Date
Region(s) Global
and formatting of the values in PDS 0520 (Travel Date), which contains
the effective ticket date, previously referred to as departure date.
nonperforming when:
• PDS 0520 date is less than (prior to) PDS 0509 (Issue Date)

Edit 4 PDS 0574 Arrival Date
Edit Number 3
Threshold
Threshold: 98%
Edit 4 PDS 0574 Arrival Date
Edit Number 4
Edit Title PDS 0574 Arrival Date
Name PDS 0574 Arrival Date
Region(s) Global
and accuracy of the values in PDS 0574 (Arrival Date), which contains
the cardholder check-in date.
nonperforming when:
• PDS 0574 date is greater than (after/later than) PDS 0575
(Departure Date)

Threshold
Threshold: 98%

Edit 5 PDS 0577 Property Phone Number
Edit 5 PDS 0577 Property Phone Number
Edit Number 5
Edit Title PDS 0577 Property Phone Number
Name PDS 0577 Property Phone Number
Region(s) Global
and formatting of the values in PDS 0577 (Property Phone Number),
which identifies specific lodging property location by its local phone
number.
nonperforming when:
• PDS 0577 contains all low values, all high values, all zeros, or all
spaces.
NOTE: For transactions acquired in the U.S. or Canada region, PDS 0577,
if present, must contain a 10-position phone number, left-justified with
trailing spaces. The first three positions must be numeric.

Threshold
Threshold: 98%

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. 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.
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.

Notices
Information Available Online

Mastercard provides details about the standards used for this document, including
times expressed, language use, and contact information, on the Technical Resource
Center (TRC). Go to the Rules collection of the References section for centralized
information.


Data Integrity Monitoring Program

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Data Integrity Monitoring Program

Uploaded by

Copyright:

Available Formats

Data Integrity Monitoring

Summary of Changes, 24 January 2023.....................................................................8

Chapter 1: Data Integrity monitoring........................................................................10

Chapter 2: Acquirer Authorization Dual Message System Edits (0100)... 26

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

Edit 20 ABU ACQ...................................................................................................................................46

Chapter 3: Acquirer Authorization Chip Dual Message System Edits

Chapter 4: Acquirer Clearing Dual Message System Edits (1240)............... 73

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

Chapter 5: Acquirer Clearing Chip Dual Message System Edits (1240).... 96

Chapter 6: Acquirer Debit Single Message System Edits (0200)................102

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

Chapter 8: Acquirer Chargeback Monitoring Program.................................... 133

Chapter 9: Issuer Authorization Dual Message System Edits (0110)...... 143

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

Edit 5 SDA Capable Cards 0210...................................................................................................... 166

Chapter 11: Issuer Chargeback Program............................................................... 169

Chapter 12: Digital Standards Program ................................................................173

Chapter 13: Global Collection Only Edits...............................................................186

Chapter 14: Mastercard Identity Check (AReq/ARes).....................................196

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

Chapter 15: Fraud Reporting Performance Program........................................206

Chapter 16: Addendum Data Performance Program....................................... 211

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

Summary of Changes, 24 January 2023

Description of Change Where to Look

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

Description of Change Where to Look

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

Chapter 1 Data Integrity monitoring