AN213219 Q2 Core Rel An Snapshot

AN 2132—19.
Q2
Switching Release
Announcements—
Bundled Snapshot
5 February 2019
ANNC
Version History
Version History
The version history of this announcement is as follows.
Date Description of Change Where to Look

5 Feb 2019 This 19.Q2 Release bundled snapshot contains all 19.Q2 Throughout
Release announcements published through 5 February 2019.
Updated between Final Publication and Bundled Snapshot:
• AN 1807—New Global Interchange Program for Freight
Transactions and Business Service Arrangement for Future
Business-to-Business Programs
• AN 1812—Product Codes to Support Humanitarian
Organizations in Canada
• AN 2116—Introduction of Merchant Presented QR
Interchange for Selected Countries in Europe Region
• AN 2136—Introduction of Mastercard Cardless ATM
Program
8 Jan 2019 This 19.Q2 Release bundled snapshot contains all 19.Q2 Throughout
Release announcements published through 8 January 2019.
New with Bundled Snapshot:
Program
• AN 2148—Enhancement of Issuer Notification for
Installment Eligible E-Commerce Transactions
• AN 2149—Enhancements to the Mastercard Installment
Payment Service for Cross-Border Eligibility Check
©2018–2019Mastercard. Proprietary. All rights reserved.

AN 2132—19.Q2 Switching Release Announcements—Bundled Snapshot • 5 February 2019 2
Version History
Updated and FAQ Additions with Bundled Snapshot: Throughout

• AN 2114—Introduction of Mastercard ATM Cash Pick-Up
Identifier
• AN 2117—Introducing Cryptographic Key Block Changes
to Support Phase 2 of PCI Mandates
• AN 2118—Account Level Management Universal
Specification Enhancements
• AN 2120—U.S. Commercial Interchange Structure
Changes
• AN 2123—Identification of Tokenized Mastercard
Consumer Presented QR Transactions
• AN 2130—New Commercial Credit Product Codes and
U.S. Intraregional Interchange Program
• AN 2139—IIAS Real-time Substantiation for Vision
Enhancement
Added a new section dedicated to the Announcement Announcement

Summary Report. Summary Report
11 Dec 2018 This 19.Q2 Release bundled snapshot contains all 19.Q2 Throughout
Release announcements published through 11 December
2018.
• AN 2114—Introduction of Mastercard ATM Cash Pick Up
Identifier
• AN 2129—New Interchange Programs for Merchants in
the European Economic Area
• AN 2144—Transaction Integrity Class for Interchange
Rates-Reminder
• AN 2145—Clarification of Usage of Mastercard Digital
Enablement Service OBS Result Values and Redefinition
of Service Level Indicator Value
• AN 2147—Issuer Support for DE 48, Subelement 95

Version History
• AN 1810—New Product Codes for Platinum Mastercard

Prepaid Consumer General Spend
• AN 1811—New Product Code for Prepaid Gold Payroll
• AN 1813—Standardization of the 80-byte Financial
Institution Table File
• AN 2108—Switching Release 19.Q2—Related Bulletins
• AN 2111—Support of 8-Digit BIN Standard and Account
Range Specifications—Reminder
• AN 2113—Enhancements to AAV Validation for EMV 3-D
Secure
• AN 2115—Mastercard Clearing Optimizer Utility Upgrade
• AN 2121—Authorization of Purchase Returns
• AN 2122—Introduction of Mastercard Digital Transaction
Insights Service
• AN 2127—Expansion of Single Message System DE 127
(Processor Private Data) to 100 Characters
• AN 2134—Issuer-provided Format Error Responses
Removed references to MasterCom Administrator’s Manual Related Information

and MasterCom Reports Manual and added reference to
MasterCom User Guide.
1 Nov 2018 Removed AN 2128—Standardization of DE 42 to Reject All Throughout
Zeros, which was inadvertently published in this bundled
snapshot on 31 October 2018. AN 2128 is not included in
this 19.Q2 Release, and customers should ignore any prior
version of the 19.Q2 Release bundled snapshot that included
AN 2128.

Version History

31 Oct 2018 This 19.Q2 Release bundled snapshot contains all 19.Q2 Throughout
Release announcements published through 30 October 2018
and prior to the 19.Q2 Mastercard Customer Tech
Conferences.
Changes
• AN 2138—Mastercard Network—Secured Mastercard
Interface Processor (MIP) Customer Connectivity (TLS1.2)
Enhancement
Updated with Bundled Snapshot:
• AN 2133—Interchange Rate Program Timeliness Holidays
2019
Updated the summary section of the bundle to clarify its AN 2132—19.Q2

purpose and provide instructions on how to access the Switching Release
bundle PDF attachment. Announcements—
Bundled Snapshot
In the Release 19.Q2 Announcements section, revised the Release 19.Q2

introductory statement and note. Announcements
Updated the About Announcements section as follows: About

Announcements
• In the Understanding Publication Dates—About Ongoing
Updates subsection, removed the note and the sentence
that followed about the email notification. The removal
of this content is not marked by change bars.
• Revised the answer to the question, “How do I view a list
of only release announcements within a certain release?”
in the Simple Tips for Using the Technical Resource
Center subsection.
23 Oct 2018 Initial publication date

Contents
Contents
Version History..............................................................................................................2
Chapter 1: AN 2132—19.Q2 Switching Release Announcements

—Bundled Snapshot.................................................................................................24
AN 2132—19.Q2 Switching Release Announcements—Bundled Snapshot.......................25
Version History................................................................................................................. 25
At-A-Glance.....................................................................................................................29
Release 19.Q2 Announcements........................................................................................29
Release Milestones........................................................................................................... 31
Where to Find Release Announcements........................................................................... 31
Announcement Summary Report..................................................................................... 31
Release Testing.................................................................................................................32
About Announcements.................................................................................................... 32
Reminder of Change in GCMS Community Run Day of Week...........................................38
Mastercard Global Interchange Rates............................................................................... 38
Data Integrity Updates..................................................................................................... 38
Times Expressed in Documentation.................................................................................. 39
Related Information......................................................................................................... 40
Chapter 2: AN 1807—New Global Interchange Program for

Freight Transactions and Business Service Arrangement for
Future Business-to-Business Programs........................................................... 42
AN 1807—New Global Interchange Program for Freight Transactions and Business
Service Arrangement for Future Business-to-Business Programs........................................ 43
Version History................................................................................................................. 43
At-A-Glance.....................................................................................................................45
Overview..........................................................................................................................45
Customer Impact............................................................................................................. 46
Enhancements................................................................................................................. 47
Platform Impact............................................................................................................... 49
Authorization...................................................................................................................50
CIS Data Element Definitions....................................................................................... 50
DE 63—Network Data............................................................................................ 50
Alternate Processing.................................................................................................... 51
Authorization Transaction Investigator......................................................................... 51
Clearing........................................................................................................................... 51
IPM Data Element and Private Data Subelement Definitions......................................... 51
PDS 0002—GCMS Product Identifier.......................................................................51

Contents
IPM MPE......................................................................................................................51
Interchange Programs..................................................................................................51
IRD FF—Freight Program......................................................................................... 58
CAB Programs, Descriptions, and Associated MCCs..................................................... 60
New CAB Program, Descriptions, and Associated MCCs..........................................60
Edits............................................................................................................................ 61
Modified Edit—DE 25 (Message Reason Code)........................................................61
Error Numbers.........................................................................................................61
Pricing/Fees................................................................................................................. 62
Quarterly Mastercard Report (QMR)............................................................................. 62
Clearing Transaction Investigator................................................................................. 62
Frequently Asked Questions............................................................................................. 62
Chapter 3: AN 1810—New Product Codes for Platinum

Mastercard Prepaid Consumer General Spend........................................... 64
AN 1810—New Product Codes for Platinum Mastercard Prepaid Consumer General
Spend.............................................................................................................................. 65
Version History................................................................................................................. 65
At-A-Glance.....................................................................................................................66
Overview..........................................................................................................................67
Related Documentation....................................................................................................67
Customer Impact............................................................................................................. 68
Enhancements................................................................................................................. 68
Platform Impact............................................................................................................... 70
Authorization...................................................................................................................71
DE 63—Network Data............................................................................................ 71
Transaction Investigator............................................................................................... 72
Clearing........................................................................................................................... 72
IPM MPE......................................................................................................................72
Interchange................................................................................................................. 73
Interchange Programs............................................................................................. 73
Quarterly Mastercard Reporting................................................................................... 78
Single Message System.................................................................................................... 78
Single Message System Data Element Definitions......................................................... 78
DE 110—Additional Data-2.....................................................................................78
Single Message Transaction Manager...........................................................................79

Contents
Chapter 4: AN 1811—New Product Code for Prepaid Gold

Payroll..............................................................................................................................80
AN 1811—New Product Code for Prepaid Gold Payroll.................................................... 81
Version History................................................................................................................. 81
At-A-Glance.....................................................................................................................81
Overview..........................................................................................................................82
Related Documentation....................................................................................................83
Customer Impact............................................................................................................. 83
Enhancements................................................................................................................. 84
Platform Impact............................................................................................................... 85
Authorization...................................................................................................................87
DE 63—Network Data............................................................................................ 87
Clearing........................................................................................................................... 88
IPM MPE......................................................................................................................88
Interchange................................................................................................................. 89
Interchange Programs............................................................................................. 89
Quarterly Mastercard Reporting................................................................................... 93
Single Message System.................................................................................................... 93
Single Message System Data Element Definitions......................................................... 93
DE 110—Additional Data-2.....................................................................................93
Single Message Transaction Manager...........................................................................94
Chapter 5: AN 1812—Product Codes to Support Humanitarian

Organizations in Canada....................................................................................... 95
AN 1812—Product Codes to Support Humanitarian Organizations in Canada.................. 96
Version History................................................................................................................. 96
Chapter 6: AN 1813—Standardization of the 80-byte Financial

Institution Table File................................................................................................. 97
AN 1813—Standardization of the 80-byte Financial Institution Table File.......................... 98
Version History................................................................................................................. 98
At-A-Glance.....................................................................................................................99

Contents
Enhancements................................................................................................................. 99
Frequently Asked Questions........................................................................................... 102
Chapter 7: AN 2108—Switching Release 19.Q2—Related

Bulletins........................................................................................................................104
AN 2108—Switching Release 19.Q2—Related Bulletins..................................................105
Version History............................................................................................................... 105
Switching Release 19.Q2—Related Bulletins................................................................... 106
Chapter 8: AN 2111— Support of 8-Digit BIN Standard and

Account Range Specifications—Reminder.................................................. 108
AN 2111— Support of 8-Digit BIN Standard and Account Range Specifications—
Reminder....................................................................................................................... 109
Version History............................................................................................................... 109
At-A-Glance...................................................................................................................110
Overview........................................................................................................................111
Related Documentation..................................................................................................115
Customer Impact........................................................................................................... 116
Enhancements............................................................................................................... 117
Platform Impact............................................................................................................. 119
Authorization.................................................................................................................120
Reports......................................................................................................................120
Forms........................................................................................................................ 120
Clearing......................................................................................................................... 121
IPM Data Element and Private Data Subelement Definitions....................................... 121
DE 31—Acquirer Reference Data...........................................................................121
Edits.......................................................................................................................... 121
Reports......................................................................................................................121
Forms........................................................................................................................ 121
Single Message System.................................................................................................. 122
Reports......................................................................................................................122
Forms........................................................................................................................ 122
Chapter 9: AN 2113—Enhancements to AAV Validation for EMV

3-D Secure....................................................................................................................123
AN 2113—Enhancements to AAV Validation for EMV 3-D Secure.................................. 124
Version History............................................................................................................... 124
At-A-Glance...................................................................................................................125
Overview........................................................................................................................126

Contents
Customer Impact........................................................................................................... 127

Enhancements............................................................................................................... 128
Platform Impact............................................................................................................. 136
Authorization.................................................................................................................137
CIS Data Element Definitions..................................................................................... 137
DE 48—Additional Data—Private Use................................................................... 137
Clearing......................................................................................................................... 138
Edits.......................................................................................................................... 138
Modified Edit—PDS 0052 (Electronic Commerce Security Level Indicator),
Subfield 3 (UCAF Collection Indicator)...................................................................138
Error Numbers.......................................................................................................139
Single Message System Data Element Definitions....................................................... 139
DE 48—Additional Data........................................................................................139
Chapter 10: AN 2114—Introduction of Mastercard ATM Cash

Pick-Up Identifier..................................................................................................... 142
AN 2114—Introduction of Mastercard ATM Cash Pick-Up Identifier............................... 143
Version History............................................................................................................... 143
At-A-Glance...................................................................................................................143
Overview........................................................................................................................144
Customer Impact........................................................................................................... 146
Enhancements............................................................................................................... 147
Platform Impact............................................................................................................. 148
Authorization.................................................................................................................149
CIS Data Element Defintions...................................................................................... 149
Transaction Investigator............................................................................................. 149
Clearing......................................................................................................................... 149
PDS 0043—Program Registration ID......................................................................149
IPM MPE....................................................................................................................150
Edits.......................................................................................................................... 151

Contents
Chapter 11: AN 2115—Mastercard Clearing Optimizer Utility

Upgrade........................................................................................................................152
AN 2115—Mastercard Clearing Optimizer Utility Upgrade..............................................153
Version History............................................................................................................... 153
At-A-Glance...................................................................................................................153
Enhancements............................................................................................................... 154
Chapter 12: AN 2116—Introduction of Merchant Presented QR

Interchange for Selected Countries in Europe Region..........................155
AN 2116—Introduction of Merchant Presented QR Interchange for Selected Countries
in Europe Region............................................................................................................156
Version History............................................................................................................... 156
At-A-Glance...................................................................................................................157
Overview........................................................................................................................157
Customer Impact........................................................................................................... 160
Enhancements............................................................................................................... 161
Platform Impact............................................................................................................. 161
Clearing......................................................................................................................... 163
Interchange Programs................................................................................................163
IRD QR—Merchant Presented QR Payment (Europe Intracountry).......................... 163
IRD QR—Merchant Presented QR Funding (Europe Intracountry)........................... 165
IRD QS—Merchant Presented QR Payment (Europe Intracountry)...........................167
Interchange Rates................................................................................................. 168
Edits.......................................................................................................................... 168
New Edit—PDS 0004 (Funding Account Information), Subfield 2 (Sender
Account Number)................................................................................................. 168
Modified Edit—DE 26 (Card Acceptor Business Code [MCC])................................ 169
Modified Edit—PDS 0004 (Funding Account Information), Subfield 1 (Funding
Source)................................................................................................................. 169
Modified Edit—PDS 0004 (Funding Account Information), Subfield 2 (Sender
Account Number)................................................................................................. 170
Modified Edit—PDS 0004 (Funding Account Information), Subfield 2 (Sender
Account Number)................................................................................................. 170
Modified Edit—PDS 0043 (Program Registration ID).............................................. 170
Error Numbers.......................................................................................................171

Contents
Chapter 13: AN 2117—Introducing Cryptographic Key Block

Changes to Support Phase 2 of PCI Mandates..........................................174
AN 2117—Introducing Cryptographic Key Block Changes to Support Phase 2 of PCI
Mandates.......................................................................................................................175
Version History............................................................................................................... 175
At-A-Glance...................................................................................................................176
Overview........................................................................................................................176
Customer Impact........................................................................................................... 178
Enhancements............................................................................................................... 178
Implementation Scenarios..........................................................................................179
Platform Impact............................................................................................................. 181
Authorization.................................................................................................................182
DE 70—Network Management Information Code................................................. 182
DE 110—Additional Data–2.................................................................................. 183
DE 70—Network Management Information Code................................................. 186
DE 110—Additional Data–2.................................................................................. 187
Chapter 14: AN 2118—Account Level Management Universal

Specification Enhancements.............................................................................. 193
AN 2118—Account Level Management Universal Specification Enhancements............... 194
Version History............................................................................................................... 194
At-A-Glance...................................................................................................................194
Overview........................................................................................................................195
Customer Impact........................................................................................................... 197
Enhancements............................................................................................................... 197
Platform Impact............................................................................................................. 199
Authorization.................................................................................................................200
Reports......................................................................................................................200
Layouts......................................................................................................................200
Universal Specification Submission Layout............................................................. 200
Universal Specification Detail Response File Layout................................................ 201
World Shortfall (WLSF)—Summary Results, Final Layout........................................ 202
World Shortfall (WLSF)—Summary Results, Preliminary Layout...............................203
World Elite Shortfall (WESF)—Summary Results, Final Layout.................................204

Contents
World Elite Shortfall (WESF)—Summary Results, Preliminary Layout....................... 206

Bulk Files................................................................................................................... 207
Chapter 15: AN 2119—Enhancements to Batch Data File to

Support Mastercard Send Activity.................................................................. 208
AN 2119—Enhancements to Batch Data File to Support Mastercard Send Activity..........209
Version History............................................................................................................... 209
At-A-Glance...................................................................................................................209
Overview........................................................................................................................210
Customer Impact........................................................................................................... 211
Enhancements............................................................................................................... 212
Platform Impact............................................................................................................. 213
250-byte Batch Data File............................................................................................214
Chapter 16: AN 2120—U.S. Commercial Interchange Structure

Changes........................................................................................................................ 215
AN 2120—U.S. Commercial Interchange Structure Changes.......................................... 217
Version History............................................................................................................... 217
At-A-Glance...................................................................................................................218
Overview........................................................................................................................218
Customer Impact........................................................................................................... 219
Enhancements............................................................................................................... 220
Valid and Eliminated Product Codes and IRDs After Enhancements............................ 225
Platform Impact............................................................................................................. 234
Authorization.................................................................................................................235
DE 48—Additional Data—Private Use........................................................................ 235
Subelement 38—Account Category...................................................................... 235
DE 38—Authorization ID Response............................................................................235
Clearing......................................................................................................................... 236
DE 38—Approval Code......................................................................................... 236
IPM MPE Tables......................................................................................................... 236
Table IP0018T1: Mastercard Product Graduation Parameters................................. 236
Table IP0019T1: Account Level Management Participation and Enhanced Value
Parameters............................................................................................................236
Interchange............................................................................................................... 237
New Interchange Programs................................................................................... 237

Contents
IRD 5A—Business Level 5 Data Rate I.................................................................... 237

IRD 5B—Business Level 5 Data Rate II.................................................................... 240
IRD 5K—Business Level 5 Standard........................................................................243
IRD 5N—Business Level 5 T&E Rate....................................................................... 245
IRD 5R—Business Level 5 Utilities.......................................................................... 249
Modified Interchange Programs............................................................................ 251
IRD 62—Commercial Large Ticket......................................................................... 251
IRD E6—Mastercard Commercial Payments Account............................................. 251
CAB Code TE01.................................................................................................... 251
CAB Programs, Descriptions, and Associated MCCs................................................... 251
Life Cycled CAB Programs, Descriptions, and Associated MCCs.............................252
Edits.......................................................................................................................... 253
Modified Edit—DE 43 (Card Acceptor Name/Location), Subfield 5 (Card
Acceptor State/Province/Region Code)...................................................................253
Modified Edit—DE 63 (Transaction Life Cycle ID)................................................... 254
Modified Edit—PDS 0158 (Business Activity ), Subfield 4 (Interchange Rate
Designator)........................................................................................................... 255
Modified Edit—PDS 0158 (Business Activity ), subfield 4 (Interchange Rate
Designator)........................................................................................................... 256
Designator)........................................................................................................... 256
Designator)........................................................................................................... 257
Designator)........................................................................................................... 258
Designator)........................................................................................................... 259
Designator)........................................................................................................... 260
Designator)........................................................................................................... 261
Modified Edit—PDS 0173 (Legal Corporate Name)................................................ 262
Modified Edit—PDS 0505 (Passenger Name)......................................................... 262
Modified Edit—PDS 0505 (Passenger Name)......................................................... 263
Modified Edit—PDS 0520 (Travel Date)..................................................................264
Modified Edit—PDS 0520 (Travel Date)..................................................................265
Modified Edit—PDS 0544 (Rental Agreement Number)......................................... 266
Modified Edit—PDS 0552 (Customer Service Toll-Free [800] Number).................... 267
Modified Edit—PDS 0595 (Card Acceptor Type).....................................................267
Modified Edit—PDS 0595 (Card Acceptor Type).....................................................268
Modified Edit—PDS 0595 (Card Acceptor Type), subfield 1 (Business Type)............ 268

Contents
Modified Edit—PDS 0595 (Card Acceptor Type), subfield 5 (Business Type

Provided Code)..................................................................................................... 269
Provided Code)..................................................................................................... 269
Provided Code)..................................................................................................... 270
Modified Edit—PDS 0596 (Card Acceptor Tax ID), subfield 2 (Card Acceptor Tax
ID Provided Code)................................................................................................. 270
Modified Edit—PDS 0596 (Card Acceptor Tax ID), subfield 2 (Card Acceptor Tax
ID Provided Code)................................................................................................. 271
Modified Edit—PDS 0597 (Total Tax Amount)........................................................ 271
Modified Edit—PDS 0597 (Total Tax Amount), Subfield 1 (Total Tax Amount)......... 272
Modified Edit—PDS 0597 (Total Tax Amount), Subfield 1 (Total Tax Amount)......... 272
Quarterly Mastercard Reporting................................................................................. 273
Chapter 17: AN 2121—Authorization of Purchase Returns................274

AN 2121—Authorization of Purchase Returns................................................................ 275
Version History............................................................................................................... 275
At-A-Glance...................................................................................................................276
Overview........................................................................................................................276
Customer Impact........................................................................................................... 278
Enhancements............................................................................................................... 279
Platform Impact............................................................................................................. 280
DE 3—Processing Code.........................................................................................281
DE 3—Processing Code.........................................................................................281
Chapter 18: AN 2122—Introduction of Mastercard Digital

Transaction Insights Service............................................................................... 282
AN 2122—Introduction of Mastercard Digital Transaction Insights Service...................... 283
Version History............................................................................................................... 283
At-A-Glance...................................................................................................................283
Overview........................................................................................................................284
Customer Impact........................................................................................................... 286
Enhancements............................................................................................................... 290
Platform Impact............................................................................................................. 290
Authorization.................................................................................................................291

Contents

Chapter 19: AN 2123—Identification of Tokenized Mastercard

Consumer Presented QR Transactions...........................................................299
AN 2123—Identification of Tokenized Mastercard Consumer Presented QR
Transactions................................................................................................................... 300
Version History............................................................................................................... 300
At-A-Glance...................................................................................................................302
Overview........................................................................................................................302
Customer Impact........................................................................................................... 305
Enhancements............................................................................................................... 306
Platform Impact............................................................................................................. 308
Authorization.................................................................................................................309
Edits.......................................................................................................................... 310
Clearing......................................................................................................................... 312
PDS 0021—Transaction Type Indicator...................................................................312
IPM MPE....................................................................................................................312
Edits.......................................................................................................................... 313
New Edit—PDS 0021 (Transaction Type Indicator)..................................................313
Error Numbers.......................................................................................................314
Edits.......................................................................................................................... 317

Contents
Chapter 20: AN 2124—Revisions to Brazil 7–21 Installment

Payment Interchange Structure for Select Merchant Categories.... 320
AN 2124—Revisions to Brazil 7–21 Installment Payment Interchange Structure for
Select Merchant Categories............................................................................................321
Version History............................................................................................................... 321
At-A-Glance...................................................................................................................321
Overview........................................................................................................................322
Customer Impact........................................................................................................... 324
Enhancements............................................................................................................... 325
Platform Impact............................................................................................................. 325
Clearing......................................................................................................................... 327
Interchange............................................................................................................... 327
Interchange Programs........................................................................................... 327
Chapter 21: AN 2125—Enhancement for International Debit

Mastercard Single Message System Transactions................................... 328
AN 2125—Enhancement for International Debit Mastercard Single Message System
Transactions................................................................................................................... 329
Version History............................................................................................................... 329
At-A-Glance...................................................................................................................329
Enhancements............................................................................................................... 330
Chapter 22: AN 2127—Expansion of Single Message System DE

127 (Processor Private Data) to 100 Characters........................................331
AN 2127—Expansion of Single Message System DE 127 (Processor Private Data) to
100 Characters.............................................................................................................. 332
Version History............................................................................................................... 332
At-A-Glance...................................................................................................................332
Enhancements............................................................................................................... 333
250-Byte Batch Data File (BDF) Additional Processor Private Data Addendum (APPD)
—Optional Record..................................................................................................... 333
Additional Processor Private Data Addendum (APPD)—Optional............................333
Single Message System DE 127 (Processor Private Data)............................................. 334
DE 127—Processor Private Data............................................................................ 334

Contents
Chapter 23: AN 2129—New Interchange Programs for

Merchants in the European Economic Area............................................... 336
AN 2129—New Interchange Programs for Merchants in the European Economic Area... 337
Version History............................................................................................................... 337
At-A-Glance...................................................................................................................337
Overview........................................................................................................................338
Customer Impact........................................................................................................... 339
Enhancements............................................................................................................... 340
Platform Impact............................................................................................................. 342
Clearing......................................................................................................................... 343
Revised Interchange Rates..........................................................................................343
Frequently Asked Questions.......................................................................................343
Chapter 24: AN 2130—New Commercial Credit Product Codes

and U.S. Intraregional Interchange Program............................................. 344
AN 2130—New Commercial Credit Product Codes and U.S. Intraregional Interchange
Program......................................................................................................................... 346
Version History............................................................................................................... 346
At-A-Glance...................................................................................................................347
Overview........................................................................................................................347
Customer Impact........................................................................................................... 349
Enhancements............................................................................................................... 350
Platform Impact............................................................................................................. 351
Authorization.................................................................................................................352
DE 63—Network Data.......................................................................................... 352
Alternate Processing.................................................................................................. 354
Clearing......................................................................................................................... 354
PDS 0002—GCMS Product Identifier.....................................................................354
IPM MPE....................................................................................................................355
Interchange............................................................................................................... 355
IRD V5—Commercial VIP Standard........................................................................355
Edits.......................................................................................................................... 357
Modified Edit—DE 63 (Transaction Life Cycle ID)................................................... 357
Modified Edit—PDS 0023 (Terminal Type).............................................................. 358

Contents
Modified Edit—PDS 0173 (Legal Corporate Name)................................................ 358

Modified Edit—PDS 0595 (Card Acceptor Type), Subfield 1 (Business Type)............359
Modified Edit—PDS 0595 (Card Acceptor Type), Subfield 5 (Business Type
Provided Code)..................................................................................................... 359
Provided Code)..................................................................................................... 360
Provided Code)..................................................................................................... 360
Modified Edit—PDS 0596 (Card Acceptor Tax ID), Subfield 2 (Card Acceptor Tax
ID Provided Code)................................................................................................. 361
Modified Edit—PDS 0596 (Card Acceptor Tax ID), Subfield 2 (Card Acceptor Tax
ID Provided Code)................................................................................................. 361
Error Numbers.......................................................................................................362
Quarterly Mastercard Reporting................................................................................. 363
Chapter 25: AN 2133—Interchange Rate Program Timeliness

Holidays 2019............................................................................................................ 365
AN 2133—Interchange Rate Program Timeliness Holidays 2019..................................... 366
Version History............................................................................................................... 366
At-A-Glance...................................................................................................................366
Enhancement Description...............................................................................................367
Chapter 26: AN 2134—Issuer-provided Format Error Responses.....368

AN 2134—Issuer-provided Format Error Responses.........................................................369
Version History............................................................................................................... 369
At-A-Glance...................................................................................................................369
Enhancements............................................................................................................... 370
Chapter 27: AN 2136—Introduction of Mastercard Cardless ATM

Program........................................................................................................................ 372
AN 2136—Introduction of Mastercard Cardless ATM Program........................................374
Version History............................................................................................................... 374
At-A-Glance...................................................................................................................376
Overview........................................................................................................................377
Customer Impact........................................................................................................... 378
Enhancements............................................................................................................... 379
Platform Impact............................................................................................................. 387

Contents
Authorization.................................................................................................................388
CIS Data Element Defintions...................................................................................... 388
DE 61—Point-of-Service (POS) Data...................................................................... 389
Edits.......................................................................................................................... 390
Clearing......................................................................................................................... 394
DE 22—Point of Service (POS) Entry Mode............................................................ 394
PDS 0022—Additional Terminal Operating Environments...................................... 394
IPM MPE....................................................................................................................395
Edits.......................................................................................................................... 396
New Edit—PDS 0022 (Additional Terminal Operating Environments)......................396
New Edit—DE 22 (Point of Service [POS] Entry Mode), Subfield 7 (Card Entry
Mode)...................................................................................................................396
New Edit—DE 22 (Point of Service [POS] Entry Mode), subfield 4 (Terminal
Operating Environment)........................................................................................ 397
Modified Edit—DE 22 (POS Entry Mode), Subfield 4 (Terminal Operating
Environment)........................................................................................................ 398
Environment......................................................................................................... 399
Environment)........................................................................................................ 399
Environment)........................................................................................................ 400
Error Numbers.......................................................................................................400
DE 61—Point of Service (POS) Data....................................................................... 402
Edits.......................................................................................................................... 403
Chapter 28: AN 2137—New Edits for Japan Domestic

Transactions ...............................................................................................................409
AN 2137—New Edits for Japan Domestic Transactions .................................................. 410
Version History............................................................................................................... 410
At-A-Glance...................................................................................................................410
Overview........................................................................................................................411
Customer Impact........................................................................................................... 412

Contents
Enhancements............................................................................................................... 414
Platform Impact............................................................................................................. 415
Authorization.................................................................................................................416
DE 112—Additional Data (National Use)............................................................... 416
Clearing......................................................................................................................... 417
Edits.......................................................................................................................... 417
New Edit—PDS 0195 (Installment Data), Subfield 1 (Total Number of
Installments)......................................................................................................... 417
Error Numbers.......................................................................................................418
Chapter 29: AN 2138—Mastercard Network—Secured

Mastercard Interface Processor (MIP) Customer Connectivity
(TLS1.2)..........................................................................................................................419
AN 2138—Mastercard Network—Secured Mastercard Interface Processor (MIP)
Customer Connectivity (TLS1.2)......................................................................................420
Version History............................................................................................................... 420
At-A-Glance...................................................................................................................420
Enhancements............................................................................................................... 421
Chapter 30: AN 2139—IIAS Real-time Substantiation for Vision

Enhancement............................................................................................................. 423
AN 2139—IIAS Real-time Substantiation for Vision Enhancement...................................424
Version History............................................................................................................... 424
At-A-Glance...................................................................................................................424
Enhancements............................................................................................................... 425
Edits...............................................................................................................................426
Error Numbers........................................................................................................... 426
Chapter 31: AN 2140—2019 Switching Release Resources and

Frequently Asked Questions .............................................................................427
AN 2140—2019 Switching Release Resources and Frequently Asked Questions .............428
Version History............................................................................................................... 428
2019 Release Resources................................................................................................. 428
Preparing for the Switching Release........................................................................... 429
Requesting Help........................................................................................................ 431
Community Runs.......................................................................................................432
Freeze Dates.............................................................................................................. 432
Distribution of IPM MPE Files..................................................................................... 433

Contents
Interchange............................................................................................................... 435
IPM Clearing Optimizer and Utilities Software Global Rollout..................................... 435
MIP Initial Program Load............................................................................................ 435
Release Implementation.............................................................................................436
Testing.......................................................................................................................436
Timing (Sequence of Events)...................................................................................... 438
Chapter 32: AN 2144—Transaction Integrity Class for

Interchange Rates—Reminder...........................................................................443
AN 2144—Transaction Integrity Class for Interchange Rates—Reminder.........................444
Version History............................................................................................................... 444
At-A-Glance...................................................................................................................444
Overview........................................................................................................................445
Customer Impact........................................................................................................... 447
Enhancements............................................................................................................... 448
Platform Impact............................................................................................................. 448
Chapter 33: AN 2145—Clarification of Usage of Mastercard

Digital Enablement Service OBS Result Values and Redefinition
of Service Level Indicator Value....................................................................... 449
AN 2145—Clarification of Usage of Mastercard Digital Enablement Service OBS Result
Values and Redefinition of Service Level Indicator Value..................................................450
Version History............................................................................................................... 450
At-A-Glance...................................................................................................................450
Enhancements............................................................................................................... 451
Chapter 34: AN 2147—Issuer Support for DE 48, Subelement 95... 453

AN 2147—Issuer Support for DE 48, Subelement 95......................................................454
Version History............................................................................................................... 454
At-A-Glance...................................................................................................................454
Enhancements............................................................................................................... 455
Chapter 35: AN 2148—Enhancement of Issuer Notification for

Installment Eligible E-Commerce Transactions......................................... 457
AN 2148—Enhancement of Issuer Notification for Installment Eligible E-Commerce
Transactions................................................................................................................... 458
Version History............................................................................................................... 458
At-A-Glance...................................................................................................................458
Overview........................................................................................................................459

Contents
Customer Impact........................................................................................................... 460
Enhancements............................................................................................................... 461
Platform Impact............................................................................................................. 463
Chapter 36: AN 2149—Enhancements to the Mastercard

Installment Payment Service for Cross-Border Eligibility Check...... 464
AN 2149—Enhancements to the Mastercard Installment Payment Service for Cross-
Border Eligibility Check...................................................................................................465
Version History............................................................................................................... 465
At-A-Glance...................................................................................................................465
Overview........................................................................................................................466
Customer Impact........................................................................................................... 467
Enhancements............................................................................................................... 468
Platform Impact............................................................................................................. 469
Notices...........................................................................................................................470

AN 2132—19.Q2 Switching Release Announcements—Bundled Snapshot
Chapter 1 AN 2132—19.Q2 Switching Release

Announcements—Bundled Snapshot
Release announcements are published individually on the Technical Resource Center (TRC). On each
release publication milestone date, Mastercard provides this document to help customers more
easily view all release announcements together.
AN 2132—19.Q2 Switching Release Announcements—Bundled Snapshot....................................25

Version History..............................................................................................................................25
At-A-Glance..................................................................................................................................29
Release 19.Q2 Announcements.................................................................................................... 29
Release Milestones........................................................................................................................31
Where to Find Release Announcements........................................................................................ 31
Announcement Summary Report.................................................................................................. 31
Release Testing..............................................................................................................................32
About Announcements.................................................................................................................32
Reminder of Change in GCMS Community Run Day of Week....................................................... 38
Mastercard Global Interchange Rates............................................................................................ 38
Data Integrity Updates.................................................................................................................. 38
Times Expressed in Documentation............................................................................................... 39
Related Information...................................................................................................................... 40

AN 2132—19.Q2 Switching Release Announcements—Bundled

Snapshot
Release announcements are published individually on the Technical Resource Center (TRC). On
each release publication milestone date, Mastercard provides this document to help customers
more easily view all release announcements together.
To download the entire bundled snapshot, which includes all of the release
announcements, follow these steps:
1. Within this topic, select Attachments (in the upper right), and then select the filename.
2. When prompted, open or download and save the attachment.
NOTE: This document provides a snapshot. In computing, a snapshot is defined as a record of

contents at a given point in time. Announcements collected in this document are first
published as individual, stand-alone documents and may be updated from time to time. This
document may not be updated every time an announcement is updated, so customers must
refer to the individual announcements and use the version history in each announcement to
understand updates.
Version History

5 Feb 2019 This 19.Q2 Release bundled snapshot contains all 19.Q2 Throughout
Release announcements published through 5 February 2019.
Updated between Final Publication and Bundled Snapshot:
Program

Version History

8 Jan 2019 This 19.Q2 Release bundled snapshot contains all 19.Q2 Throughout
Release announcements published through 8 January 2019.
Program
• AN 2148—Enhancement of Issuer Notification for
Installment Eligible E-Commerce Transactions
• AN 2149—Enhancements to the Mastercard Installment
Payment Service for Cross-Border Eligibility Check

• AN 2114—Introduction of Mastercard ATM Cash Pick-Up
Identifier
• AN 2118—Account Level Management Universal
Specification Enhancements
Changes
• AN 2123—Identification of Tokenized Mastercard
Consumer Presented QR Transactions
Enhancement
Added a new section dedicated to the Announcement Announcement

Summary Report. Summary Report

Version History

11 Dec 2018 This 19.Q2 Release bundled snapshot contains all 19.Q2 Throughout
Release announcements published through 11 December
2018.
• AN 2114—Introduction of Mastercard ATM Cash Pick Up
Identifier
• AN 2129—New Interchange Programs for Merchants in
the European Economic Area
• AN 2144—Transaction Integrity Class for Interchange
Rates-Reminder
• AN 2145—Clarification of Usage of Mastercard Digital
Enablement Service OBS Result Values and Redefinition
of Service Level Indicator Value

• AN 1813—Standardization of the 80-byte Financial
• AN 2111—Support of 8-Digit BIN Standard and Account
Range Specifications—Reminder
• AN 2113—Enhancements to AAV Validation for EMV 3-D
Secure
• AN 2122—Introduction of Mastercard Digital Transaction
Insights Service
• AN 2127—Expansion of Single Message System DE 127
(Processor Private Data) to 100 Characters

Version History

Removed references to MasterCom Administrator’s Manual Related Information
and MasterCom Reports Manual and added reference to
MasterCom User Guide.
1 Nov 2018 Removed AN 2128—Standardization of DE 42 to Reject All Throughout
Zeros, which was inadvertently published in this bundled
snapshot on 31 October 2018. AN 2128 is not included in
this 19.Q2 Release, and customers should ignore any prior
version of the 19.Q2 Release bundled snapshot that included
AN 2128.
31 Oct 2018 This 19.Q2 Release bundled snapshot contains all 19.Q2 Throughout
Release announcements published through 30 October 2018
and prior to the 19.Q2 Mastercard Customer Tech
Conferences.
Changes
• AN 2138—Mastercard Network—Secured Mastercard
Interface Processor (MIP) Customer Connectivity (TLS1.2)
Enhancement
Updated with Bundled Snapshot:
• AN 2133—Interchange Rate Program Timeliness Holidays
2019
Updated the summary section of the bundle to clarify its AN 2132—19.Q2

purpose and provide instructions on how to access the Switching Release
bundle PDF attachment. Announcements—
Bundled Snapshot
In the Release 19.Q2 Announcements section, revised the Release 19.Q2

introductory statement and note. Announcements
Updated the About Announcements section as follows: About

Announcements
• In the Understanding Publication Dates—About Ongoing
Updates subsection, removed the note and the sentence
that followed about the email notification. The removal
of this content is not marked by change bars.
• Revised the answer to the question, “How do I view a list
of only release announcements within a certain release?”
in the Simple Tips for Using the Technical Resource
Center subsection.

At-A-Glance

At-A-Glance
The At-a-Glance table provides key information about the systems and groups affected by this
announcement, action indicators that specify the appropriate action, and the required
implementation date or dates.
Audience: Acquirer, Issuer, Processor

Each customer must determine the impact on its operations.
Brands: Mastercard®, Debit Mastercard®, Maestro®, Cirrus®
Release: 19.Q2
Region: All
System: Authorization, Clearing, Single Message System
Action Indicator:
Information only—Provides general information about release conventions
and the bundle.
Effective Date: Dual Message System (Authorization): 12 April 2019
Dual Message System (Clearing): 12 April 2019
Single Message System: 12 April 2019
Release 19.Q2 Announcements

The following announcements comprise the enhancements that will be included in this
release.
• AN 1807—New Global Interchange Program for Freight Transactions and Business Service
Arrangement for Future Business-to-Business Programs
• AN 1810—New Product Codes for Platinum Mastercard Prepaid Consumer General Spend
• AN 1812—Product Codes to Support Humanitarian Organizations in Canada
• AN 1813—Standardization of the 80-byte Financial Institution Table File
• AN 2111—Support of 8-Digit BIN Standard and Account Range Specifications—Reminder
• AN 2113—Enhancements to AAV Validation for EMV 3-D Secure

Release 19.Q2 Announcements
• AN 2114—Introduction of Mastercard ATM Cash Pick Up Identifier

• AN 2116—Introduction of Merchant Presented QR Interchange for Selected Countries in
Europe Region
• AN 2117—Introducing Cryptographic Key Block Changes to Support Phase 2 of PCI
Mandates
• AN 2118—Account Level Management Universal Specification Enhancements
• AN 2119—Enhancements to Batch Data File to Support Mastercard Send Activity
• AN 2120—U.S. Commercial Interchange Structure Changes
• AN 2122—Introduction of Mastercard Digital Transaction Insights Service
• AN 2123—Identification of Tokenized Mastercard Consumer Presented QR Transactions
• AN 2124—Revisions to Brazil 7–21 Installment Payment Interchange Structure for Select
Merchant Categories
• AN 2125—Enhancement for International Debit Mastercard Single Message System
Transactions
• AN 2127—Expansion of Single Message System DE 127 (Processor Private Data) to 100
Characters
• AN 2129—New Interchange Programs for Merchants in the European Economic Area
• AN 2130—New Commercial Credit Product Codes and U.S. Intraregional Interchange
Program
• AN 2133—Interchange Rate Program Timeliness Holidays 2019
• AN 2136—Introduction of Mastercard Cardless ATM Program
• AN 2137—New Edits for Japan Domestic Transactions
• AN 2138—Mastercard Network—Secured Mastercard Interface Processor (MIP) Customer
Connectivity (TLS1.2)
• AN 2139—IIAS Real-time Substantiation for Vision Enhancement
• AN 2140—2019 Switching Release Resources and Frequently Asked Questions
• AN 2144—Transaction Integrity Class for Interchange Rates-Reminder
• AN 2145—Clarification of Usage of Mastercard Digital Enablement Service OBS Result
Values and Redefinition of Service Level Indicator Value
• AN 2148—Enhancement of Issuer Notification for Installment Eligible E-Commerce
Transactions
• AN 2149—Enhancements to the Mastercard Installment Payment Service for Cross-Border
Eligibility Check

Release Milestones
NOTE: This document provides a snapshot. In computing, a snapshot is defined as a record of

contents at a given point in time. Announcements collected in this document are first
published as individual, stand-alone documents and may be updated from time-to-time. This
document may not be updated every time an announcement is updated, so customers must
refer to the individual announcements, and use the version history in each announcement to
understand updates.
Release Milestones
Milestones and dates for releases are available on the Mastercard Technical Resource Center.
TIP: From the Announcements results page, type “milestones” into the title search box at the
top right of the page. Announcements that include the word “milestones” in the title will
display.
Where to Find Release Announcements

Announcements are published on the Technical Resource Center on Mastercard Connect™. To
access Announcements on the Technical Resource Center, follow these steps:
1. Go to www.mastercardconnect.com.
2. Log on using the User ID and Security Information.
3. Click Support at the upper right, then click Technical Resource Center.
The Technical Resource Center home page will display. From the Technical Resource Center,
customers can access individual announcements or a bundled snapshot.
Announcement Summary Report

On 19 September 2018, Mastercard introduced the Announcement Summary Report, a
weekly report that summarizes all announcements published on the Technical Resource
Center.
Mastercard will provide the report each week, on Wednesdays. To locate the report, follow
these steps:
3. Click Support at the upper right, then click Technical Resource Center.
4. Look for the Featured Content panel on the Technical Resource Center home page,
where users will find a link to the Announcement Summary Report.
Each week, customers can access the report and download the complete list of
announcements published during the prior week.

Release Testing
The report lists all announcements that published in the current year and allows sorting and
filtering on particular values so customers can track all announcements collectively—those
labeled release announcement and those labeled bulletin announcement—in an easily
customizable Excel format. The data includes announcements published in the current month
through Tuesday prior to the Wednesday publishing date of the report.
The report includes links to each announcement, enabling customers to navigate quickly to
corresponding announcements available on the Technical Resource Center. To access
announcements using the links in the report, users must first login to Mastercard Connect to
view the content. Some organizations may limit this functionality.
For more information, refer to “AN 2169—New Announcement Summary Report on the
Technical Resource Center,” 19 September 2018.
Release Testing
Mastercard encourages customer testing as described in announcements. For more
information about customer testing, including release test cases, refer to the Testing Reference
Information Center on Mastercard Connect™ Support.
About Announcements
Release announcements communicate upcoming core system enhancements and other
changes. Announcements are numbered for reference, published on a particular schedule
with updates as necessary, and structured as consistently as possible.
Core Release Announcement Numbering
Mastercard assigns a unique number that displays in the title of each core release
announcement. The numbers are for reference only and do not imply impact to systems or
regions. Each announcement begins with AN, followed by a unique reference number. The AN
number (for example, AN 1000) is static and will not change throughout the lifecycle of the
announcement. There are no repeating numbers.
Understanding Publication Dates—About Ongoing Updates
Announcements may be updated and develop over time, and the publication date will always
reflect the last date on which that document was updated. To see when the announcement
was first published, look for the primary publication date in the version history. This indicates
when Mastercard first made the announcement.
Global release announcements publish as individual documents that are initially available on
the first publication date milestone, and then updated periodically, as needed.
Mastercard provides a bundled snapshot of the release announcements on each of the
Release publication milestone dates—First, Second, Final, and then a post-final version, 30
days after Final Publication.
Simple Tips for Using the Technical Resource Center

About Announcements
Refer to the following common questions to understand how to access release-related

information on the Technical Resource Center (TRC).
How do I view a list of only release Usually, you will want to display only release
announcements within a certain release? announcements for a particular release. To do so,
follow these steps:
1. On the TRC home page, click
Announcements, then click Filters.
2. From the filters, click Release, select the
particular release you want to view, then click
Apply.
To see only what has published in a particular
timeframe—in the last week, the last month, or
similar—click Limit Results by Date Range, and
type or select the appropriate dates.
How do I view a list of only release On the TRC home page, click Announcements.
announcements? Then, click Filters, click the drop down arrow on
Type, and select Release Announcements.
Core Release Announcement Structure

Mastercard structures announcements with an At-A-Glance section and action indicators to
help enable customers to quickly understand key information and impact.
At-A-Glance Information
Each core release announcement contains an At-A-Glance section. With its easy-to-read
format, this section provides key information, such as core systems and groups affected by an
announcement, action indicators that specify appropriate action, and the date or dates that
the announcement is effective.
Action indicators, which are provided in each announcement’s At-A-Glance section, help
customers more clearly identify their impact. They provide clarity about the applicability of a
change and actions to be taken. For example, the indicators will alert customers as to whether
a requirement applies to customers issuing or acquiring a Mastercard brand, using the
Mastercard Network, or opting to participate in a Mastercard product or service. The
indicators will also note whether customer action is critical, is required, or may be warranted.
Action Indicators
The following table identifies action indicators, along with their descriptions, that are in use.

About Announcements
Indicator Description Should be used for...
Brand Mandate Action required relating to • Any new or revised mandate

Mastercard-branded activity that impacts the brand rules
or a customer’s participation
with Mastercard at the
scheme level
• Any new or revised liability
shift
• Business rules; licensing
participation
• Requirements regardless of
which network is used to
process
Network Mandate Action required by participants in • Any new or revised message

Mastercard network switching format, data field, data value,
processing, and other services, indicator, or other coding
and their third-party service requirement
providers • Mandate associated with
transaction processing
through the Mastercard
Network
Program or service requirement Action required by participants in • Requirement relating to a

a Mastercard program or service new or existing Mastercard
offering product, program, or service
• Customer must take action to
support the requirement in
order to continue
participation
Critical action needed Failure to take action may pose a • Security-related

significant risk to payment announcements requiring
system integrity or result in timely action
noncompliance with law or • Notification of an obligation
regulatory requirements to take action to ensure
compliance with applicable
law or regulation
• May be used in conjunction
with “Brand Mandate” or in
place of “Attention
warranted (Brand-related),”
as appropriate

About Announcements
Attention-warranted (Brand- Action may be needed relating • Advance notice of a future

related) to Mastercard-branded activity mandate
• Brand level rule changes that
do not introduce or expand a
mandate
• Reminders of existing
mandates
Attention-warranted (Network- Action may be needed by • Reminder or advance notice

related) Mastercard network participants of a network requirement
and their third-party service • Network level rule changes
providers that do not introduce or
expand a mandate
• Network enhancements
requiring action to opt-in or
opt-out
• Introduction of a new card
product identifier or card
product-specific IRD (with
respect to acquirers that may
process transactions involving
use of the product)
Attention warranted (Program/ Action may be need by • Reminder or advance notice

service-related) participants in a Mastercard of a program or service
program or service offering launch, enhancement, or
requirement
• Program or service
enhancements requiring
action to opt-in or opt-out
(may be used in combination
with a registration and/or
testing indicator)
• Introduction of a new card
product identifier or card
product-specific IRD (with
respect to issuers that choose
to issue the product)

About Announcements
Information only No action is needed • Future date enhancement

announcements
• Training and education
offerings
• Release freeze or settlement
holiday schedule dates
Financial impact Fees or other pricing related to • Interchange and service fee
mandate compliance or amounts
program/service participation • Pricing for programs,
may apply products, and services
• Licensing and registration fee
amount
• Compliance, data integrity,
and variance fee amounts
Registration required Registration or enrollment is • Registration or enrollment is

required required to participate in a
Mastercard product,
program, service, training, or
other offering
• Registration is required in
accordance with brand or
network rules
Testing Testing is required or • Testing is required or

recommended recommended in connection
with a technical or other
implementation
• Certification requirements
apply to participants in a
product, program, or service
Scenarios Supporting Action Indicators

The following table illustrates different situations where customers can see how action
indicators are used.

About Announcements
Announcement
Description Acquirers Issuers Comments
Introduction of a new Network Mandate— Attention warranted In this example, the

product code for Acquirers globally MUST (Program/service- acquirer is not opting to
issuance in the Europe support this related) —Issuers in the participate. This is a
region only enhancement. Europe region that network data
choose to issue this new requirement from the
product code MUST acquirer’s perspective.
support this
Issuers can choose to
enhancement.
issue this new product
code being introduced.
Support of the product
code and interchange is
a product requirement.
Introduction of a new Network Mandate— Network Mandate— In this example, all

data element to the IPM Acquirers globally MUST Issuers globally MUST acquirers and issuers are
Clearing Format support this support this required to support this
enhancement. This new enhancement. This is a enhancement. Action is
data element is required “retain and return” field required by participants
on ALL Presentment/ that must be present on in the Mastercard
1240 messages. all Chargebacks/1442 Network switching,
messages. processing, and other
services.
Introduction of a new Program or service Network Mandate—All In this example,

value to the Mastercard requirement—Acquirers issuers must support the acquirers must take
Digital Enablement that process these enhancements. action to support the
Service transactions must requirement in order to
support the continue participation.
enhancements. ALL issuers must be able
to support the new
value to continue
transaction processing
through the Mastercard
network .
Technical Specifications
The technical details for Dual Message System (Authorization and Clearing) and the Single
Message System are provided within each core release announcement are described in the
Platform Impact section. The technical specifications contain new or changed technical
information. Technical information that is not changed may be presented as appropriate to
facilitate the understanding of the new or changed information.

Reminder of Change in GCMS Community Run Day of Week
Reminder of Change in GCMS Community Run Day of Week

Mastercard schedules GCMS Community Run testing dates to begin on Tuesdays after 08:00
(St. Louis, Missouri, USA Central time). This change was made in response to customer
requests.
The Community Run testing dates in the Clearing Release Milestones reflect the continuation
of this standard.
GCMS Community Runs encourage all clearing customers to participate on the same business
testing day. This all-on-the-same-business-day participation by the general clearing community
improves the likelihood that customers will receive and may systemically respond to a
significant variety of types of presentment transactions, as well as various life cycle
transactions.
Mastercard Global Interchange Rates

Changes to Mastercard Global and Regional Interchange rates are not included in release-
related announcements. Communications about upcoming changes to interchange rates will
be provided in a bulletin announcement.
NOTE: The technical specifications, including interchange information, contain only new or
changed technical information. All other technical information remain unchanged, and
customers may refer to the appropriate interchange manual for existing information.
Data Integrity Updates

Mastercard uses a number of primary edits to monitor compliance and to resolve issues that
account for more than 90 percent of all data integrity errors. These compliance issues
compromise the integrity of the acquirer’s message data.
The Data Integrity Monitoring Program helps acquirers reduce exception processing and,
through greater processing efficiency and accuracy.
Data Integrity Report Interface
For report monitoring, acquirers can access reports from the Data Integrity OnLine application
available through Mastercard Connect™. To access the reports, follow these steps:
3. On the My Items menu, click Data Integrity Online. The page will open on the Reporting
tab. From the list, select the type of appropriate report. If Data Integrity Online is not
available, continue to step 4.
4. On the Store menu, click Data Integrity Online, then click Order. Return to step 3.

Times Expressed in Documentation
Customers can refer to the Data Integrity Monitoring Program manual, available through
Publications on Mastercard Connect. This manual provides customers with detailed
information about the Data Integrity Online application and new and revised edit criteria.
New edits or updates for Data Integrity that are not addressed in release announcements will
be announced in a bulletin announcement.
For More Information
Customers with questions about the Data Integrity updates should contact Global Customer
Service or contact the Data Integrity Help Desk:
Phone: 1-636-722-6022
Times Expressed in Documentation

The following information indicates the way in which time is expressed in Mastercard
publications.
Mastercard is a global company with locations in many time zones around the world. The
Mastercard operations and business centers are in the United States. The operations center is
in St. Louis, Missouri, and the business center is in Purchase, New York. For operational
purposes, Mastercard refers to time frames in this document as either “St. Louis time” or
“New York time.” Coordinated Universal Time (UTC) is the basis for measuring time
throughout the world. You can use the following table to convert any time in this document
into the correct time in another zone.
Standard Time
First Sunday in November to second Sunday in March (For Central European Time, last Sunday
in October to last Sunday in March)
St. Louis, Missouri, USA Time Purchase, New York, USA

(UTC-6) Time (UTC-5) UTC
9:00 10:00 15:00
Daylight Saving Time

Second Sunday in March to first Sunday in November (For Central European Time, last Sunday
in March to last Sunday in October)

Related Information
St. Louis, Missouri, USA Time Purchase, New York, USA

(UTC-5) Time (UTC-4) UTC
9:00 10:00 14:00
Related Information
Mastercard updates the following information as needed, and it should be used in
conjunction with the release announcements to obtain a complete description of the release
enhancements.
Shared Resources
The following resources provide information common to both the Dual Message and Single
Message Systems related to subjects discussed in this document:
• Data Integrity Monitoring Program
• Interchange Information Center on Mastercard Connect™
• Technical Resource Center available on Mastercard Connect
• Testing Reference Information Center on Mastercard Connect
Dual Message System—Authorization

The following documents and resources provide authorization information related to the
subjects discussed in this document:
• Account Level Management User Manual
• Account Management System User Manual
• Authorization Manual
• Customer Interface Specification
• Data Communications Manual
• File Transfer Manual
Dual Message System—Clearing

The following documents and resources provide clearing information related to the subjects
discussed in this document:
• Chargeback Guide
• GCMS Parameter Table Layouts
• GCMS Reference Manual
• Interchange Manual
• IPM Clearing Formats
• IPM Clearing Format Error Numbers and Messages

Related Information
• IPM Pre-edit and Utilities—Mainframe

• IPM Pre-edit and Utilities Module List
• IPM Pre-edit and Utilities Global—Workstation Plus
• MasterCom User Guide
• Quick Reference Booklet
Single Message System

The following documents and resources provide Single Message System information related to
the subjects discussed in this document:
• Debit Mastercard for Single Message System Guide
• Single Message System Programs and Services
• Single Message System Settlement and Reports
• Single Message System Specifications
• Single Message Transaction Manager User Guide

AN 1807—New Global Interchange Program for Freight Transactions and Business Service Arrangement for
Future Business-to-Business Programs
Chapter 2 AN 1807—New Global Interchange Program for

Freight Transactions and Business Service Arrangement
for Future Business-to-Business Programs
Mastercard is introducing a new Global Interchange Program for the freight industry, a new
Business Service Arrangement (BSA), and a new product code for future Business-to-Business (B2B)
programs. Canada will be introduced in 19.Q4.
AN 1807—New Global Interchange Program for Freight Transactions and Business Service
Arrangement for Future Business-to-Business Programs.................................................................43
Version History..............................................................................................................................43
At-A-Glance..................................................................................................................................45
Overview...................................................................................................................................... 45
Customer Impact.......................................................................................................................... 46
Enhancements.............................................................................................................................. 47
Platform Impact............................................................................................................................ 49
Authorization................................................................................................................................50
CIS Data Element Definitions.................................................................................................... 50
DE 63—Network Data......................................................................................................... 50
Alternate Processing.................................................................................................................51
Authorization Transaction Investigator...................................................................................... 51
Clearing........................................................................................................................................51
IPM Data Element and Private Data Subelement Definitions......................................................51
PDS 0002—GCMS Product Identifier................................................................................... 51
IPM MPE.................................................................................................................................. 51
Interchange Programs...............................................................................................................51
IRD FF—Freight Program...................................................................................................... 58
CAB Programs, Descriptions, and Associated MCCs..................................................................60
New CAB Program, Descriptions, and Associated MCCs...................................................... 60
Edits.........................................................................................................................................61
Modified Edit—DE 25 (Message Reason Code).................................................................... 61
Error Numbers..................................................................................................................... 61
Pricing/Fees.............................................................................................................................. 62
Quarterly Mastercard Report (QMR)..........................................................................................62
Clearing Transaction Investigator.............................................................................................. 62
Frequently Asked Questions.......................................................................................................... 62

AN 1807—New Global Interchange Program for Freight Transactions

and Business Service Arrangement for Future Business-to-Business
Programs
Mastercard is introducing a new Global Interchange Program for the freight industry, a new
Business Service Arrangement (BSA), and a new product code for future Business-to-Business
(B2B) programs. Canada will be introduced in 19.Q4.
Version History

17 Jan 2019 Added, “Canada will be introduced in 19.Q4.” to short AN 1807—New
descriptions in the following locations: Global Interchange
Program for Freight
• Before Version History page
Transactions and
• Interchange Programs Business Service
Arrangement for
Future Business-to-
Business Programs
Added the following to At-A-Glance table: At-A-Glance
• “19.Q4 for customers in Canada.” to Release row.
• “18 October 2019 for customers in Canada” to Effective
Dates.
Added “(applicable to Canada from 19.Q4)”. Customer Impact

Added note above Interregional Interchange Programs table Interchange
and above Canada Region Intracountry Interchange Programs
Programs (BSA 4/124001) table: Product MES will be added
to Canada acquired interregional BSAs on 18 October 2019.
Added “Note: Interregional programs will be applicable for Interchange

Canada-acquired MES transactions from 19.Q4.” under Programs
Interregional Interchange Programs table.

Version History

8 Jan 2019 In Clearing, Interchange Programs, revised the lists of Interchange
interchange programs to which Mastercard will add new Programs
commercial credit product code MES (Mastercard Enterprise
Solutions) in the following tables:
• Interregional Interchange Programs
• Asia/Pacific Region Intraregional Interchange Programs
(BSA 2/040001)
• Asia/Pacific Region Intracountry Interchange Programs
• Europe Region Intraregional Interchange Programs (BSA
2/050001)
• Europe Region Intraregional Interchange Programs (BSA
2/050002)
• Europe Region Intercountry Interchange Programs
• Europe Region Intracountry Interchange Programs
• Latin America and the Caribbean Region Intraregional
Interchange Programs (BSA 2/030001)
• Latin America and the Caribbean Region Eastern
Caribbean Intercountry Interchange Programs (BSA
3/030021)
• Latin America and the Caribbean Region Intracountry
Interchange Programs
• Middle East/Africa Region Intraregional Interchange
Programs (BSA 2/060001)
• Middle East/Africa Region Intracountry Interchange
Programs
• United States Region Commercial Intraregional
Interchange Programs (BSA 2/010001)
Added a Frequently Asked Questions section. Frequently Asked

Questions
23 Oct 2018 In an effort to provide clear communication to our Throughout
customers, Mastercard has changed the format of Release
Announcements beginning with Release 19.Q1. The
following sections were reformatted after the initial
publication to align with the new layout:
• At-A-Glace
• Overview
• Customer Impact
• Enhancements
10 July 2018 Initial publication date

At-A-Glance
At-A-Glance
Type: Switching Release Announcement

Each customer must independently determine the impact on its operations.
Brands: Mastercard®
Release: 19.Q2; 19.Q4 for customers in Canada
Region: All
System: Authorization, Clearing
Action Indicator:
Network Mandate—Acquirers, Issuers
Program or service requirement—Acquirers
Testing recommended—Acquirers, Issuers
Effective Date: Dual Message System (Authorization): 12 April 2019; 18 October 2019 for
customers in Canada
Dual Message System (Clearing): 12 April 2019; 18 October 2019 for
customers in Canada
Overview
This Overview provides information about the current environment and any applicable
background information as it relates to this enhancement. This section also provides a brief
explanation of what Mastercard is going to do to address this opportunity and the business
drivers behind the enhancement.
What Mastercard Is Currently Doing

Currently, Mastercard does not have a way to introduce new B2B programs without creating a
new BSA or new product code every time a new program develops. There is not a specific B2B
product code or BSA that can be used for all B2B programs. Within the current structure,
Mastercard cannot differentiate between B2B programs.

Customer Impact
What Mastercard Is Going to Do

Mastercard is introducing a new Global Interchange Program for Freight Transactions, a new
CAB Program for Commercial Freight, a new Business Service Arrangement (BSA), and a new
commercial credit product code MES (Mastercard Enterprise Solutions) for future Business-to-
Business (B2B) programs.
This release announcement supports the following enhancements:
• New commercial B2B brand product code MES under the Mastercard® acceptance brand
• New Member-to-Member BSA: Global Wholesale Programs—8/000901
• New Global Interchange Program: IRD FF—Freight Program
• New CAB Program: CF01—Commercial Freight
Why Mastercard Is Implementing These Changes

The new Global Interchange Program for Freight Transactions is used to settle freight
transactions from anywhere in the world at any point in time, without restrictions to a
country-specific or regional view. The freight program provides differentiated operating
guidelines to more effectively compete in the payments market and to increase merchant
acceptance for payments currently captured by check and other forms of payment.
Customer Impact
This section provides high level information about customer impact. Refer to the
Enhancements section for more details.
Is Customer Action Required?

Network Mandate—Acquirers and issuers globally (applicable to Canada from 19.Q4) must
recognize new product code MES.
Program or service requirement—Acquirers should be aware that Mastercard will add them as
participants in the Global Wholesale Programs BSA.
Testing recommended—Mastercard recommends testing for acquirers and issuers to support
this announcement.
Transaction Message Flow Impacts

The manner in which a customer is connected to Mastercard determines the group of
message flows that apply and the transaction message types they send or receive within that
group. Customers can interface to the Mastercard Dual Message System, Single Message
System, or both, as applicable. The message flows that are affected by this announcement are
marked in the following table.

Enhancements
Acquirer to Mastercard Mastercard to Issuer Impacted
Dual Message Dual Message √
Dual Message Single Message
Single Message Single Message
Single Message Dual Message
The following are examples of message types within the Dual Message System and Single
Message System:
• Dual Message System—Authorization Request/0100 and First Presentment/1240 messages
• Single Message System—Financial Transaction Request/0200 and Financial Transaction
Advice/0220 messages
Enhancements
Mastercard will introduce the following changes to support this announcement.
Mastercard will create a new commercial B2B product code (MES), a new Member-to-Member
BSA (Global Wholesale Programs—8/000901), and a new IRD specific to the Freight Program
(IRD FF—Freight Program).
Dual Message System (Authorization)—Acquirers, Issuers

The Authorization Platform will support the new commercial credit product code MES as a
valid value in DE 63 (Network Data), subfield 1 (Financial Network Code).
• The Account Management System will support new product code MES and new product
class MES.
• Issuers that choose to issue the new product code MES must be prepared to receive it in DE
63 (Network Data), subfield 1 (Financial Network Code) of Authorization messages.
• Acquirers globally must be prepared to receive the new product code MES in DE 63
(Network Data), subfield 1 (Financial Network Code).
Dual Message System (Clearing)—Acquirers, Issuers

The Clearing Platform will support new product code MES in PDS 0002 (GCMS Product
Identifier) and PDS 0003 (Licensed Product Identifier).
• Product code MES will be added to the appropriate IPM MPE tables.
– Issuers must be prepared to receive and recognize the IRDs supporting product code
MES as described in this release announcement.
– Issuers that choose to issue the new product code MES must support its receipt in PDS
0002 (GCMS Product Identifier) and PDS 0003 (Licensed Product Identifier).

Enhancements
– Acquirers globally must be prepared to receive the new product code MES in PDS 0002
(GCMS Product Identifier) and PDS 0003 (Licensed Product Identifier).
• Product code MES will be available for use outside of transactions that qualify for the
Freight Program. Mastercard will add product code MES to all BSAs and IRDs where
product code MCP (Mastercard Purchasing Card) currently exists.
– Acquirers globally will be automatically enrolled to participate in the Global Wholesale
Programs BSA and must be able to identify participating freight transactions from their
merchants in order to qualify these transactions for program rate(s).
• Mastercard will modify a Clearing Edit to validate the chargeback message reason code in
DE 25 (message reason code) when PDS 0002 contains the new value MES and PDS 0158
contains the value FF.
– Acquirers globally will initiate clearing of freight transactions using the IRD FF (Freight
Program).
New Member-to-Member BSA for Global B2B Programs

• Global Wholesale Programs—8/000901
New Commercial Product Class and Product Code

• Mastercard Enterprise Solution (MES)
New Global Interchange Program

• IRD FF—Freight Program
New CAB Program

• CF01—Commercial Freight
– MCCs 3000-3350—Airlines, Air Carriers
– MCC 4011—Railroads, Freight
– MCC 4214—Motor Freight Carriers, Trucking—Long Distance, Moving and Storage
Companies, Local Delivery
– MCC 4215—Courier Services—Air and Ground, Freight Forwarders
– MCC 4511—Air Carriers, Airlines—Not Elsewhere Classified
– MCC 4789—Transportation Services—Not Elsewhere Classified
– MCC 4112—Passenger Railways
– MCC 4111—Transportation—Suburban and Local Commuter Passenger, Including
Ferries
– MCC 7299—Other Services Not Elsewhere Classified
– MCC 9311—Tax Payments
– MCC 9402—Postal Services—Government Only
– MCC 9399—Government Services Not Elsewhere Classified

Platform Impact
Platform Impact
The following table lists the impact of this announcement. For items that are marked √
(“Yes”), details are provided below.
Dual Message System
Single Message
Topic Authorization Clearing System
Message Flows
Message Layouts
Data Element Definitions √ √
IPM MPE √
Interchange √
CAB Programs, Descriptions,

√
and Associated MCCs
Edits √
Error Numbers √
Alternate Processing √
Interchange Compliance
Pricing/Fees √
Reports
Bulk Files
Forms
Quarterly Mastercard
√
Reporting
Transaction Investigator √ √
SAFE
Single Message Transaction

Manager
250-byte Batch Data File
80-byte Financial Institution

Table File

Authorization
Authorization
Mastercard will update the Authorization Platform as follows.
CIS Data Element Definitions

Mastercard will update the following data elements to support this announcement.
DE 63—Network Data
DE 63 (Network Data) is generated by the Authorization Platform for each originating
message routed through the network. The receiver must retain the data element and use it in
any response or acknowledgment message associated with the originating message.
Subfield 1—Financial Network Code
DE 63 (Network Data), subfield 1 (Financial Network Code) identifies the specific program or
service (for example, the financial network, financial program, or card program) with which
the transaction is associated. DE 63 will contain the graduated product when the issuer’s
cardholder account participates in the Product Graduation Account Level Management
service.
Code Description MC NP VI TE MS CI
MES Mastercard Enterprise Solution √

Clearing
Alternate Processing
New product code MES will be allowed for Stand-In and X-Code processing.
Authorization Transaction Investigator

The Authorization Transaction Investigator will be updated to support product code MES.
Clearing
Mastercard will update the Clearing Platform as follows.
IPM Data Element and Private Data Subelement Definitions

Mastercard will update the following data elements or private data subelement definitions to
support this announcement.
PDS 0002—GCMS Product Identifier

PDS 0002 (GCMS Product Identifier) identifies the product recognized by GCMS for the
combination of issuer account range (part of DE 2 [Primary Account Number (PAN)]) and Card
Program Identifier.
GCMS Product Licensed Product Licensed Product Product Class

Identifier (PDS 0002) Identifier (PDS 0003) Identifier Description Override Indicator
MES MES Mastercard Enterprise MES—Mastercard

Solution Enterprise Solution
IPM MPE
Mastercard will update these IPM MPE tables with new product class MES.
• IP0016T1—Brand Product
• IP0018T1—Mastercard Product Graduation Parameters
• IP0020T1—PAN Mapping Product Code Pairs
• IP0040T1—Issuer Account Range
• IP0052T1—Interchange Fee Group
• IP0057T1—Interchange Override Fee Group
Mastercard will add new commercial credit product code MES to the indicated interregional,
intraregional, and intracountry interchange programs where product code MCP (Mastercard

Clearing
Purchasing Card) exists and introduce new IRD FF (Freight Program). Interregional programs
will be applicable for Canada acquired MES transactions from 19.Q4.
Modified Interchange Programs
Criteria Requirement
GCMS Product ID Commercial Credit—added: MES
NOTE: Product MES will be added to Canada acquired interregional BSAs on 18 October 2019.
Interregional Interchange Programs
21, 2A, 62, 63, 67, EZ, QR
NOTE: Interregional programs will be applicable for Canada acquired MES transactions from
19.Q4.
Asia/Pacific Region Intraregional Interchange Programs (BSA 2/040001)
21, 2A, 62, 63, 67, 69, CS, CQ, SM, QR, NS, NQ
Southeast Asia Intercountry Interchange Programs (BSA 3/040041)
SA
Asia/Pacific Region Intracountry Interchange Programs
Australia (4/036001) 2A, 61, CH, LM
Bangladesh (4/050001) 21, 2A, 61, QR
Cambodia (4/116001) 2A, 46, 60, 61, QR
Hong Kong (4/344001) 2A, 46, 63, 71, 72, QR
India (4/356001) 21, 2A, 43, 61, ER, QR
Indonesia (4/360001) 2A, 60, 63, 6F, 6M, MP, SA, QR
Japan (4/392001) MD, 2A, 61

Clearing
Macao (4/446001) 2A, 46, 63, 71, 72, QR
Malaysia (4/458001) 2A, 60, 63, QR
Myanmar (4/104001) 2A, 60, 61, 6F, 6M, QR
New Zealand (4/554001) 2A, 61, 77, 78, 79, CH, ED, FL, SF, SM
Philippines (4/608001) 2A, 60, 75, 85, EM, EP, SA, QR
Singapore (4/702001) 2A, 61, SA, QR
Sri Lanka (4/144001) 2A, 63, QR
Thailand (4/764001) 2A, 46, 60, 61, SA, QR
Vietnam (4/704001) 21, 2A, 63, 6M, MP, SA, QR
NOTE: Product MES will be added to Canada intracountry BSA on 18 October 2019.
Canada Region Intracountry Interchange Programs (BSA 4/124001)
2A, 40, BQ, BR, BS, CC, EZ
Europe Region Intraregional Interchange Programs (BSA 2/050001)
ER, MS, P2, 2A, 21, 24, 26, 27, 50, 53, 75, 79, 84, 85, 88
Europe Region Intraregional Interchange Programs (BSA 2/050002)
AL, MT, 51, 56, 75, 85, 88
Europe Region Intercountry Interchange Programs
Intra EEA (3/050012) 21, 24, 26, 27, 2A, 50, 51, 53, 56, 75, 79, 84, 85, 88, AL, ER, MR,
MS, MT, P2, PW
Western Europe (3/050021) 21, 24, 26, 27, 2A, 50, 51, 53, 56, 75, 79, 84, 85, 88, AL, MS, MT,
P2

Clearing
Europe Region Intercountry Interchange Programs
Non-EEA Countries (3/050031) 21, 24, 26, 27, 2A, 50, 51, 53, 56, 75, 79, 84, 85, 88, AL, MS, MT,
P2
Europe Region Intracountry Interchange Programs
Albania (4/008001) 24, 2A, 51, 56, 75, 79, 84, 85, 88, AL, L1, L2, L3, L4, L5, MT, P2,
PC, PT, PV
Azerbaijan (4/031001) 24, 26, 27, 2A, 50, 51, 53, 56, 75, 79, 84, 85, 88, AL, MS, MT, P2,
PC
Belarus (4/112001) 21, 24, 26, 27, 2A, 50, 51, 53, 56, 75, 79, 84, 85, 88, AL, MS, MT,
P2, PC, PT
Bosnia (4/070001) 21, 24, 26, 27, 2A, 50, 51, 53, 56, 75, 79, 84, 85, 88, AL, L1, L2,
L3, L4, L5, MS, MT, P2, PC, PT, PV
Bulgaria (4/100001) 21, 24, 2A, 50, 51, 53, 56, 75, 79, 84, 85, 88, AL, MS, MT, P2, PT
Croatia (4/191001) 21, 24, 26, 27, 2A, 50, 51, 53, 56, 75, 79, 84, 85, 88, AL, L5, L7,
MS, MT
Czech Republic (4/203001) 24, 26, 27, 2A, 50, 51, 53, 56, 75, 79, 85, 88, AL, L7, MS, MT, P2,
P6, PC, PT, PV
Denmark (4/208001) 21, 24, 2A, 50, 51, 53, 56, 75, 79, 84, 85, 88, AL, MT, P2, PC, PT
Estonia (4/233001) 21, 24, 26, 27, 2A, 50, 51, 53, 56, 75, 79, 84, 85, 88, AL, MT, P2,
PC, PT
France (4/250001) 24, 26, 27, 2A, 51, 56, 75, 79, 84, 85, 88, AL, MT, P2, PW, T1
Germany (4/280001) 21, 24, 2A, 50, 51, 53, 56, 75, 79, 84, 85, 88, AL, MT, P2, PW
Greece (4/300001) 21, 24, 26, 27, 2A, 51, 56, 75, 79, 84, 85, 88, AL, L4, L5, MT, P2,
PC, PT, T1
Hungary (4/348001) 21, 24, 26, 27, 2A, 50, 51, 53, 56, 75, 79, 85, 88, AL, L5, L8, MS,
MT, P2, P6, PC, PK, PT, PV
Iceland (4/352001) 24, 26, 27, 2A, 50, 51, 53, 56, 75, 79, 84, 85, 88, AL, MT, P2
Italy (4/380001) 24, 26, 27, 2A, 51, 56, 75, 79, 84, 85, 88, AL, ER, MT, P2, T1
Kazakhstan (4/398001) 24, 26, 27, 2A,50, 51, 53, 56, 75, 79, 84, 85, 88, AL, MS, MT, P2,
PC, PT, PW
Kosovo (4/900001) 24, 2A, 51, 56, 75, 79, 84, 85, 88, AL, L1, L2, L3, L4, L5, MT, P2,
PC, PT, PV

Clearing
Europe Region Intracountry Interchange Programs
Lithuania (4/440001) 21, 24, 26, 27, 2A, 50, 51, 53, 56, 75, 79, 84, 85, 88, AL, L5, MT,
P2, PC, PT
Macedonia (4/807001) 24, 2A, 51, 56, 75, 79, 84, 85, 88, AL, L1, L2, L3, L4, L5, MT, P2,
PC, PT, PV
Malta (4/470001) 24, 26, 27, 2A, 51, 56, 75, 79, 84, 85, 88, AL, L4, L5, MS, MT, P2,
T1
Moldova (4/498001) 21, 24, 26, 27, 2A, 50, 51, 53, 56, 75, 79, 84, 85, 88, AL, L1, L2,
L3, MS, MT, P2,PC, PT, PV
Montenegro (4/499001) 24, 2A, 51, 56, 75, 79, 84, 85, 88, AL, L1, L2, L3, L4, L5, MT, P2,
PC, PT, PV
Poland (4/616001) 21, 24, 2A, 51, 56, 75, 79, 84, 85, 88, AL, ER, L1, L2, L3, L7, L9,
MS, MT
Romania (4/642001) 21, 24, 2A, 50, 51, 53, 56, 75, 79, 84, 85, 88, AL, L4, L7, L8, L9,
MT, P2, P6, PT
Russia (4/643001) 21, 24, 26, 27, 2A, 51, 56, 75, 79, 84, 85, 88, AL, L1, L2, L3, L5,
L7, L8, L9, MS, MT, PT, P2
Serbia (4/688001) 21, 24, 2A, 51, 56, 75, 79, 84, 85, 88, AL, L1, L2, L3, L4, L5, MS,
MT, P2, PC, PT, PV
Slovakia (4/703001) 24, 2A, 50, 51, 53, 56, 75, 79, 85, 88, AL, L7, L9, MS, MT, P2, PC,
PT
Slovenia (4/705001) 21, 24, 26, 27, 2A, 51, 56, 75, 79, 85, 88, AL, MS, MT, P2, PC, PT,
T1
Spain (4/724001) 2A, 51, 56, 75, 88, ER
Switzerland (4/756001) 21, 24, 26, 27, 2A, 50, 51, 53, 56, 75, 79, 84, 85, 88, AL, MT, P2,
PW
Ukraine (4/804001) 21, 24, 2A, 50, 51, 53, 56, 75, 79, 84, 85, 88, AL, MT, P2, PC, PT,
PW, QR
United Kingdom (4/826001) 21, 24, 26, 27, 2A, 5A, 5B, 51, 54, 75, 79, 84, 85, 88, 89, AL, C1,
ER, MR, MT, P2, PW, T1
Latin America and the Caribbean Region Intraregional Interchange Programs (BSA 2/030001)
21, 2A, 62, 63, 67, EZ, QR

Clearing
Latin America and the Caribbean Region Eastern Caribbean Intercountry Interchange
Programs (BSA 3/030021)
2A
Latin America and the Caribbean Region Intracountry Interchange Programs
Argentina (4/032001) 01, 02, 03, 04, 05, 2A, CH
Aruba (4/533001) 21, 2A, 61, MS
Bahamas (4/044001) 2A
Barbados (4/052001) 2A
Belize (4/084001) 2A, 01, 02, 03, 04, 05, 06, 07, 08, 09, 10, 15, MS
Brazil (4/076000) 08, 09, 10, 11, 22, 2A, 31, 58, 59, 60, CR, ER, KC, KD, KE, KF, KG,
KH, KI, KJ, KQ, KR, LA, LB, VQ, VR, VS
Cayman (4/136001) 21, 2A, 61, MS
Chile (4/152001) 01, 02, 03, 04, 05, 06, 07, 08, 09, 10, 11, 12, 13, 14, 2A, B5, CH,
D5, F5, G5, H5, J5, K5, MS
Colombia (4/170001) 01, 02, 03, 04, 05, 06, 07, 08, 09, 22, 2A, B1, B2, B3, B4, B5, B6,
B7, CI, C1, C2, C3, C4, C5, C6, C7, C8, C9, MS
Costa Rica (4/188001) 2A
Curaçao (4/531001) 21, 2A, 61, MS
Dominican Republic 2A, EZ

(4/214001)
Ecuador (4/218001) 2A
El Salvador (4/222001) 2A
Guatemala (4/320001) 2A
Haiti (4/332001) 2A, 61, MS
Honduras (4/340001) 2A
Jamaica (4/388001) 2A, EZ, 61
Mexico (4/484001) 2A
Nicaragua (4/558001) 2A
Panama (4/591001) 2A, 61

Clearing
Paraguay (4/600001) 2A
Peru (4/604001) 2A
Puerto Rico (4/630001) 2A, EZ, 30, 31, 40, 60, 61, 62, 63, 67, 70, 71, 72, 76
Trinidad and Tobago 11, 2A, EZ, MS

(4/780001)
Uruguay (4/858001) 02, 03, 04, 05, 06, 07, 08, 09, 10, 11, 12, 13, 15, 16, 2A
Venezuela (4/862001) 2A
Middle East/Africa Region Intraregional Interchange Programs (BSA 2/060001)
21, 2A, 62, 63, 67, QR
Middle East/Africa Region Intracountry Interchange Programs
Bahrain (4/048001) 62, 63, 67
Egypt (4/818001) 21, 2A, 62, 63, 67, QR
Jordan (4/400001) 21, 62, 63, 67, 6F, 6M
Kenya (4/404001) 62, 63, 67, QR
Kuwait (4/414001) 21, 62, 63, 67, 6F, 6M
Lebanon (4/422001) 21, 62, 63, 67
Mauritius (4/480001) 62, 63, 67, 75, 85
Oman (4/512001) 21, 62, 63, 67
Pakistan (4/586001) 62, 63, 67, QR
Qatar (4/634001) 21, 62, 63, 67, 6F, 6M
Saudi Arabia (4/682001) 21, 62, 63, 67
Sub-Saharan1 62, 63, 67, QR
United Arab Emirates 21, 2A, 62, 63, 67

(4/784001)
1 Sub-Saharan includes the following Middle/East Africa region countries:

Clearing
Benin (4/204001), Burkina Faso (4/854001), Burundi (4/108001), Cameroon (BSA 4/120001),
Chad (4/148001), Congo (4/178001), Cote d’Ivoire (4/384001), Ethiopia (4/230001), Gambia
(4/270001), Ghana (4/288001), Liberia (4/430001), Niger (4/562001), Rwanda (4/646001),
Senegal (4/686001), South Sudan (4/728001), Sierra Leone (4/694001), Tanzania (4/934001),
Togo (4/768001), Uganda (4/800001)
United States Region Commercial Intraregional Interchange Programs (BSA 2/010001)
21, 2A, 62, 65, 66, 67, 68, 69, CH, EZ, MC, MM
United States Region Refund Interchange Programs (BSA 2/010001)
39, 40, 41, 42
New Interchange Program

New IRD FF (Freight Program) will be added to the new BSA 8/000901 and it will include new
card acceptor business (CAB) code CF01 (Commercial Freight).
IRD FF—Freight Program

Transactions must meet requirements to qualify for this interchange program.
Card Program ID MCC
GCMS Product ID Commercial Credit—MES
Message Type ID • First and Second Presentments/1240

• First and Arbitration Chargebacks/1442
Processing Code • 00—Purchase (Goods and Services)

• 20—Credit (Purchase Return)
Card Acceptor CF01—Commercial Freight

Business (CAB)
For card acceptor business codes (MCCs) associated with CAB programs, refer to
Program
Chapter 3 in the Quick Reference Booklet.
Timeliness None
Approval Code Not required

Clearing
Magnetic stripe Not required

data from
authorization
message
Trace ID Not required

If present, the Banknet Date must contain a valid date in the format MMDD
Card Acceptor Required

Business Code
Must contain an MCC belonging to a card acceptor business (CAB) program
(MCC)
previously listed in this table
Amount Tolerance N/A
Card Acceptor ID Required

Code

Name
Card Acceptor Not required

Street Address
Card Acceptor City Required

Must be left-justified and cannot contain all spaces or all zeros

Postal (ZIP) Code

State, Province, or
Region Code

Country Code
Cannot contain spaces
Mastercard Not required

Assigned ID
Financial Detail None

Addendum/1644
Notes None
Interchange Rates
Mastercard will provide information about interchange rates in a future announcement.

Clearing
CAB Programs, Descriptions, and Associated MCCs

Mastercard is introducing new card acceptor business (CAB) programs to support this
announcement.
For a complete list of valid card acceptor business codes (MCCs), see the spreadsheet included
in the Comprehensive MCC Listing by Formatted File Type section in Chapter 3 of the Quick
Reference Booklet.
New CAB Program, Descriptions, and Associated MCCs

Mastercard is creating the following new card acceptor business (CAB) program to support
this announcement.
CF01—Commercial Freight
Card Acceptor Business Code (MCC) and Description
MCCs 3000–3350—Airlines, Air Carriers
MCC 4011—Railroads, Freight
MCC 4214—Motor Freight Carriers, Trucking—Long Distance, Moving and Storage Companies, Local
Delivery
MCC 4215—Courier Services—Air and Ground, Freight Forwarders
MCC 4511—Air Carriers, Airlines—Not Elsewhere Classified
MCC 4789—Transportation Services—Not Elsewhere Classified
MCC 4112—Passenger Railways
MCC 4111—Transportation—Suburban and Local Commuter Passenger, Including Ferries
MCC 7299—Other Services Not Elsewhere Classified
MCC 9311—Tax Payments
MCC 9402—Postal Services—Government Only
MCC 9399—Government Services Not Elsewhere Classified

Clearing
Edits
Mastercard will add new edits, modify existing edits, or remove existing edits to support this
announcement.
Modified Edit—DE 25 (Message Reason Code)

Mastercard will modify the following edit to include a new error condition for IRD FF, product
code MES, and new BSA 8/000901 (Global Wholesale Programs).
Error Number Current Requirement Modification for this Release

2665 The Clearing Platform will ensure • The Clearing Platform will
that DE 25 (Chargeback Reason ensure that for product codes
Code) contains only one of the MAP, MAQ, and MES, DE 25
following values: 4808, 4831, (Chargeback Reason Code)
4834, and 4846 contains only one of the
following values: 4808, 4831,
4834, and 4846
• This requirement applies to
product code MES only when
PDS 0158 contains:
– SF2 BSA Type Code 8
– SF3 BSA ID Code 000901
– SF4 IRD FF
This edit is performed in the Clearing Optimizer and at the Central Site for the following messages:
• First Chargeback/1442
• Arbitration Chargeback/1442
Collection Only messages are excluded from this edit.
Error Numbers
The error numbers and messages listed represent edits that are new, modified, or deleted to
support this release announcement.
Error Numbers in Modified Edits
Edit
Error Performed
Field/Subfield Number Error Message By…
DE 25 2665 DE025 MESSAGE REASON CODE MUST BE VALID FOR Both

THE BRAND PRODUCT.

Frequently Asked Questions
Pricing/Fees
Mastercard will announce billing and fee information in future Bulletin Announcements.
Quarterly Mastercard Report (QMR)

For Quarterly Mastercard Reporting, issuers that choose to issue cards with new product code
must report any activity associated with that product code with any Mastercard Credit activity
in the proper category.
Clearing Transaction Investigator

The Clearing Transaction Investigator will be updated to support product code MES.

These frequently asked questions are designed to provide a better understanding of this
announcement and may provide answers to some common questions.
Question Answer
1. How did Mastercard identify which MCCs When we selected the MCCs for this program,
were eligible for this program? Why were we realized that there are certain activities in
MCC 9399 (Government Services-not freight that are not reflected in any existing
elsewhere classified) and MCC 9311 (Tax MCCs; likely due to the lack of card payments in
Payments) included in the list? this vertical. Therefore, we chose MCCs that
would most closely represent these activities. For
example, there is no MCC for sea freight; as
such, we included MCC 4111 which references
“Transportation - Suburban and Local Commuter
Passenger, Including Ferries”.
Additionally, there are freight merchants that
currently accept card payments for passenger
transport services, so we foresee they will use
this MCC when accepting payments for freight
activities, especially in those cases when there is
no MCC for the freight activity they conduct.
With regards to MCCs 9399 and 9311, in freight
there is a large number of transactions relating to
custom payments. Like with other freight
activities, there is no MCC that captures custom
transactions, and these two MCCs most closely
resemble this type of activity.
2. Why are acquirers automatically enrolled and This is a global BSA that is expected to be used
required to support the new BSA? for future B2B programs globally, which is why all
acquirers are automatically enrolled.

Question Answer
3. Is there any impact to Smart Data CDF There are no changes to Smart Data as part of
reporting? this announcement. If you are a Smart Data
customer you will continue to manage
transactions as you do today.
4. Is this new product code MES a virtual Yes, MES is a virtual product code and will be
product code? used for virtual card numbers (VCNs), so this
product code could be used in non-face-to-face
transactions.
5. The announcement calls out specific Card acceptance in the freight industry is almost
chargeback reason codes; why are only these non-existent.
allowed?
Due to the nature of the business, sometimes
freight services get delayed or the transported
goods suffer damages during transit.
While it’s a common practice by merchants to
insure freight services and cargo, enabling
chargebacks will allow cardholders to dispute
their transactions when issues arise without
claiming through the insurance.
Since this can disrupt the way the freight industry
operates and cause a big impact on the
merchant of record and their cash flow, we
decided to limit the chargeback reason codes for
the launch of the product code. Also, we expect
that removing these risks at the beginning would
facilitate the card acceptance adoption by
merchants and acquirers.
Once card payments are more normalized in this
industry, we will review the existing chargeback
reasons and decide whether it would be
beneficial for the freight payment ecosystem to
expand them or not.
Any changes to chargeback processing would be
announced in a separate Operations Bulletin
announcement.
6. Should the interchange program FF be added The interchange program FF was created to be
to face-to-face transactions? used for VCN non-face-to-face transactions, so
there is no need to add it to face-to-face
transactions at this time.

AN 1810—New Product Codes for Platinum Mastercard Prepaid Consumer General Spend
Chapter 3 AN 1810—New Product Codes for Platinum

Mastercard Prepaid Consumer General Spend
Mastercard is introducing two new prepaid card product codes to be issued in the Asia/Pacific
region: MGS (Platinum Mastercard® Prepaid General Spend) under the Mastercard credit
acceptance brand and MRD (Platinum Debit Mastercard® Prepaid General Spend) under the Debit
Mastercard acceptance brand
AN 1810—New Product Codes for Platinum Mastercard Prepaid Consumer General Spend.......... 65
Version History..............................................................................................................................65
At-A-Glance..................................................................................................................................66
Overview...................................................................................................................................... 67
Related Documentation................................................................................................................ 67
Customer Impact.......................................................................................................................... 68
Enhancements.............................................................................................................................. 68
Platform Impact............................................................................................................................ 70
Authorization................................................................................................................................71
DE 63—Network Data......................................................................................................... 71
Transaction Investigator............................................................................................................ 72
Clearing........................................................................................................................................72
IPM MPE.................................................................................................................................. 72
Interchange..............................................................................................................................73
Interchange Programs.......................................................................................................... 73
Quarterly Mastercard Reporting................................................................................................78
Single Message System................................................................................................................. 78
Single Message System Data Element Definitions......................................................................78
DE 110—Additional Data-2................................................................................................. 78
Single Message Transaction Manager....................................................................................... 79

AN 1810—New Product Codes for Platinum Mastercard Prepaid

Consumer General Spend
Mastercard is introducing two new prepaid card product codes to be issued in the Asia/Pacific
region: MGS (Platinum Mastercard® Prepaid General Spend) under the Mastercard credit
acceptance brand and MRD (Platinum Debit Mastercard® Prepaid General Spend) under the
Debit Mastercard acceptance brand
Version History

11 Dec 2018 Added a note to the Interchange Programs section that Interchange
reads as follows: Programs
New product codes MGS and MRD will not be valid for
Australia intracountry BSA 4/036001 at this time.

Questions
30 Oct 2018 Revised the language in the Dual Message System (Clearing) Enhancements
—Acquirers, Issuers subsection of the Enhancements section
to indicate that—in addition to the interregional interchange
programs listed in the 16 July 2018 version of this
announcement—Mastercard will add new product codes
MGS and MRD to the appropriate intraregional, intercountry,
and intracountry interchange programs.
Updated the Interchange Programs section as follows: Interchange
Programs
• In the Modified Interchange Programs—Product Code
MGS subsection, updated the GCMS Product ID row to
indicate that new product code MGS is a Consumer
Credit product code rather than a Commercial Credit
product code.
• Added the affected Asia/Pacific region intraregional,
intercountry, and intracountry interchange programs to
the Interchange Programs section.

At-A-Glance

• At-A-Glance
• Overview
• Customer Impact
• Enhancements
16 Jul 2018 Initial publication date
At-A-Glance

Products & Services: Prepaid
Release: 19.Q2
Region: All
Action Indicator:
Network Mandate—Acquirer
Program or service required—Issuer
Testing recommended—Acquirer, Issuer

Overview
Overview
What Mastercard is Currently Doing

Mastercard does not currently offer a premium, general purpose reloadable prepaid program.
What Mastercard is Going to Do

Mastercard is introducing new consumer, general purpose reloadable prepaid products (MGS
and MRD) to leverage some of Mastercard’s other services and digital assets while also
allowing issuers to strengthen their offerings to cardholders.
Why Mastercard is Implementing These Enhancements

With these new, higher-tiered products, Mastercard is helping issuers deliver differentiated
propositions to their cardholders with premium service offerings not available with the
standard product, such as rewards, loyalty benefits, and preferred customer service.
Related Documentation
Information relevant to this release announcement can be found in the following documents
available on Mastercard Connect™.
Reference Manuals
Refer to these reference manuals for information about the current state of Mastercard
processing:
• Interchange Manual
NOTE: Manuals are updated with necessary changes after release implementation. Depending
on timing, information provided in this release announcement may not yet be reflected in the
manuals.

Customer Impact
Customer Impact

Network Mandate—Acquirers globally must support the new consumer prepaid product
codes MGS and MRD.
Program or service required—Issuers in the Asia/Pacific region that choose to issue cards under
these products must recognize and support the product codes as described in this release
announcement.
this announcement.

Dual Message Single Message √
Single Message Single Message √
Single Message Dual Message √
The following are examples of message types within the Dual Message System:
Enhancements
Mastercard will enhance the following systems to support this announcement.
Mastercard will introduce the product codes MGS and MRD with the product class override
indicators MGS and MRD, respectively.

Enhancements

Mastercard will add product codes MGS and MRD as valid values in DE 63 (Network Data),
subfield 1 (Financial Network Code).
New product codes MGS and MRD will be available to Stand-In (the default amount limit will
be set to zero) and will not be allowed for X-Code processing.
Acquirers globally must support the new consumer prepaid product codes MGS and MRD
issued in the Asia/Pacific region and identified in DE 63, subfield 1 in authorization messages.
Issuers in the Asia/Pacific region that choose to issue the new consumer prepaid products
MGS, MRD, or both, must be prepared to receive the product codes MGS or MRD in DE 63,
subfield 1 in authorization messages.
Mastercard will update the Authorization Transaction Investigator to support product codes
MGS and MRD.

Mastercard will add new product codes MGS and MRD as valid values in PDS 0002 (GCMS
Product Identifier) and PDS 0003 (Licensed Product Identifier).
Mastercard will add new product codes MGS and MRD to the appropriate IPM MPE tables.
Mastercard will add new product codes MGS and MRD to the appropriate interregional,
intraregional, intercountry, and intracountry interchange programs.
Acquirers globally must be prepared to recognize new product codes MGS and MRD in both
PDS 0002 and PDS 0003 when processing clearing transactions and to ensure that their
systems accurately qualify the product codes for the appropriate interchange programs
specified in this announcement.
Issuers in the Asia/Pacific region that choose to issue new consumer prepaid products MGS,
MRD, or both, must be prepared to receive new product codes MGS or MRD in both PDS
0002 and PDS 0003.
Mastercard will update Quarterly Mastercard Reporting with new product codes MGS and
MRD.
Mastercard will update the Clearing Transaction Investigator to support new product codes
MGS and MRD.
Single Message System—Acquirers, Issuers

Mastercard will add new product codes MGS and MRD as valid values in DE 110 (Additional
Data—2), subelement 8 (Product ID).
Mastercard will allow new product codes MGS and MRD for cash access, including ATMs.
Acquirers globally must be prepared to recognize and accept new product codes MGS and
MRD when processing transactions where DE 110, subelement 8 currently is supported and
displayed in the Single Message Transaction Manager.

Platform Impact
Issuers in the Asia/Pacific region that choose to issue new consumer prepaid products MGS,
MRD, or both, must be prepared to receive the new product codes MGS or MRD in
transactions where DE 110, subelement 8 are supported currently and displayed in the Single
Message Transaction Manager.
Mastercard will also update the Single Message Transaction Manager to support new product
codes MGS and MRD.
Platform Impact
The following table lists the impact of this announcement. For items that are marked √ (Yes),
details are provided below.
Dual Message
System Dual Message Single Message
Topic (Authorization) System (Clearing) System
Message Flows
Message Layouts
Data Element Definitions √ √ √
IPM MPE √
Interchange Programs √

and Associated MCCs
Edits
Error Numbers
Billing and Fees
Reports
Bulk Files
Forms
√
Reporting
SAFE

Authorization
Dual Message

√
Manager

Table File
Authorization

DE 63, subfield 1 (Financial Network Code) identifies the specific program or service (for
example, the financial network, financial program, or card program) with which the
transaction is associated. DE 63 will contain the graduated product when the issuer’s
service.
®
MGS Platinum Mastercard Prepaid General Spend √
®
MRD Platinum Debit Mastercard Prepaid General √
Spend

Clearing
Product codes MGS and MRD will be eligible for Stand-In processing, but will be defined with
zero amount default limits for the global TCC limit and accumulative limit tests. Product codes
MGS and MRD will not be allowed for X-Code processing.
Transaction Investigator
Mastercard will update the Authorization Transaction Investigator with new values MGS and
MRD to support this announcement.
Clearing


Program Identifier.
GCMS Licensed
Product Product
Identifier Identifier
(PDS (PDS
0002) 0003) Licensed Product Identifier Description Product Class Override Indicator
MGS MGS Platinum Mastercard® Prepaid General MGS—Platinum Mastercard® Prepaid
Spend General Spend
MRD MRD Platinum Debit Mastercard® Prepaid MRD—Platinum Debit Mastercard®
General Spend Prepaid General Spend
IPM MPE
Mastercard will update the following IPM MPE tables with new product codes MGS and MRD
in the Licensed Product ID field.
• IP0019T1—Account Level Management Participation and Enhanced Value Parameters
• IP0037T1—Selection Criteria Data

Clearing

• IP0097T1—Message Reason Code Restrictions for Card Program Identifier and Business
Service Arrangement
• IP0105T1—New Product Code Mapping
Interchange
Interchange information often includes new or updated interchange programs and rates.
Mastercard will add new consumer product code MGS (Platinum Mastercard Prepaid General
Spend) under MCC acceptance brand and consumer product code MRD (Platinum Debit
Mastercard Prepaid General Spend) under DMC acceptance brand to the indicated
interregional, intraregional, intercountry, and intracountry interchange programs.
NOTE: New product codes MGS and MRD will not be valid for Australia intracountry BSA
4/036001 at this time.
Modified Interchange Programs—Product Code MGS
20, 2A, EZ, MS, PE, PF, PM, PS, QR

Only for merchant activity in the U.S. and U.S. territories: LD, LF, LS, LT
Acquirer Region Issuer Region Card Program ID GCMS Product ID
• Canada Asia/Pacific MCC added: MGS

• Europe
• Latin America and
the Caribbean
• MEA
• U.S.
PA, PI

Clearing
MEA Asia/Pacific MCC added: MGS
51, 52, AS
Europe Asia/Pacific MCC added: MGS
GCMS Product ID Consumer Credit—added: MGS
Asia/Pacific Region Intraregional Interchange Programs (2/040001)
20, 2A, CS, EZ, MS, NS, PA, PE, PF, PI, PM, PS, QR, SM
SA
Bangladesh (4/050001) 20, 2A, EZ, MS, PA, PE, PF, PI, PM, PS
Cambodia (4/116001) 2A, 46, EZ, MS, PE, PS, QR
Hong Kong (4/344001) 2A, 46, 71, 72, EZ, MS, PA, PE, PF, PI, PM, PS
India (4/356001) 20, 2A, ER, EZ, MS, PA, PE, PF, PI, PM, PS, QR
Japan (4/392001) 2A, EZ, MD, PS

Clearing
Macao (4/446001) 2A, 46, 71, 72, EZ, MS, PA, PE, PF, PI, PM, PS
Malaysia (4/458001) 2A, EZ, MS, PE, PS, QR
Myanmar (4/104001) 2A, EZ, QR, PE, PF, PM, PS
New Zealand (4/554001) 77, 78, 79, CH, ED, EZ, FL, MS, PS, PY, SF, SM
Philippines (4/608001) 2A, 75, 83, 85, 90, 91, 92, 93, 94, EM, EP, EZ, MS, PE, QR, SA
Singapore (4/702001) 2A, EZ, MS, PE, PS, QR, SA
Sri Lanka (4/144001) 2A, EZ, MS, PA, PE, PF, PI, PM, PS, QR
Thailand (4/764001) 2A, 46, EZ, MS, PE, PF, PM, PS, QR, SA
Vietnam (4/704001) 20, 2A, EZ, MP, MS, PA, PE, PF, PI, PM, PS, QR, SA
Modified Interchange Programs—Product Code MRD
20, 2A, EZ, MS, PE, PF, PM, PS, QR

• Canada Asia/Pacific DMC added: MRD

• Europe
the Caribbean
• MEA
• U.S.
PA, PI

Clearing
MEA Asia/Pacific DMC added: MRD
51, 52, AS
Europe Asia/Pacific DMC added: MRD
GCMS Product ID Consumer Debit—added: MRD
Asia/Pacific Region Intraregional Interchange Programs (2/040001)
20, 2A, 74, CS, EZ, LD, LF, MS, NS, PA, PE, PF, PI, PM, PS, QR, SM
SA
NOTE: New product code MRD will not be valid for Myanmar intracountry BSA 4/104001.
Bangladesh (4/050001) 20, 2A, EZ, MS
Cambodia (4/116001) 2A, 46, EZ, MS, PE, PS, QR
Hong Kong (4/344001) 2A, 46, 71, 72, EZ, MS, PA, PE, PF, PI, PM, PS
India (4/356001) 20, 2A, ER, EZ, MS, PD, P2, QR

Clearing
Japan (4/392001) 2A, EZ, MD, PS
Macao (4/446001) 2A, 46, 71, 72, EZ, MS, PA, PE, PF, PI, PM, PS
Malaysia (4/458001) 2A, EZ, MS, PE, PS, QR
New Zealand (4/554001) 2A, 78, 79, CH, EZ, FL, PY, P2, SF, SM, Z7, ZP
Philippines (4/608001) 2A, 75, 85, EM, EP, EZ, MS, PE, QR, SA
Singapore (4/702001) 2A, EZ, MS, PE, PS, QR, SA
Sri Lanka (4/144001) 2A, EZ, MS, QR
Thailand (4/764001) 2A, 46, EZ, MS, PE, PF, PM, PS, QR, SA
Vietnam (4/704001) 20, 2A, EZ, MP, MS, PA, PE, PF, PI, PM, PS, QR, SA

Quarterly Mastercard Reporting

For Quarterly Mastercard Reporting, issuers that choose to issue cards with new product codes
MGS and MRD must report any activity associated with that product code with any
Mastercard Credit activity in the proper category.
Mastercard will update the Clearing Transaction Investigator with new values MGS and MRD
to support this announcement.

Mastercard will update the Single Message System as follows.
Single Message System Data Element Definitions

DE 110—Additional Data-2
DE 110 (Additional Data-2) is reserved for use based on product type.
Subelement 8—Product ID
DE 110, subelement 8 (Product ID) provides issuers additional information about Product ID,
also known as product code.
DE 110, Subelement 8, Product Identifier Values
Licensed Product
Identifier Licensed Product Identifier Description
®
MGS Platinum Mastercard Prepaid General Spend
®
MRD Platinum Debit Mastercard Prepaid General Spend

Single Message Transaction Manager

Mastercard will update the Single Message Transaction Manager to support new product
codes MGS and MRD.

Question Answer
1. Will new product codes MGS and MRD will be No, new product codes MGS and MRD will not
valid for Australia intracountry BSA be valid for Australia intracountry BSA 4/036001
4/036001? at this time.

AN 1811—New Product Code for Prepaid Gold Payroll
Chapter 4 AN 1811—New Product Code for Prepaid Gold

Payroll
Mastercard is introducing a prepaid card product code MGP (Mastercard® Prepaid Gold Payroll)
under the Mastercard credit acceptance brand to be issued in the Latin America and the Caribbean
and Middle East/Africa regions.
AN 1811—New Product Code for Prepaid Gold Payroll................................................................. 81

Version History..............................................................................................................................81
At-A-Glance..................................................................................................................................81
Overview...................................................................................................................................... 82
Related Documentation................................................................................................................ 83
Customer Impact.......................................................................................................................... 83
Enhancements.............................................................................................................................. 84
Platform Impact............................................................................................................................ 85
Authorization................................................................................................................................87
DE 63—Network Data......................................................................................................... 87
Clearing........................................................................................................................................88
IPM MPE.................................................................................................................................. 88
Interchange..............................................................................................................................89
Interchange Programs.......................................................................................................... 89
Quarterly Mastercard Reporting................................................................................................93
Single Message System................................................................................................................. 93
Single Message System Data Element Definitions......................................................................93
DE 110—Additional Data-2................................................................................................. 93
Single Message Transaction Manager....................................................................................... 94


Mastercard is introducing a prepaid card product code MGP (Mastercard® Prepaid Gold
Payroll) under the Mastercard credit acceptance brand to be issued in the Latin America and
the Caribbean and Middle East/Africa regions.
Version History

11 Dec 2018 In Clearing, Interchange Programs, removed the following Interchange
IRDs from the appropriate lists of interchange programs to Programs
which Mastercard will add new consumer product code
MGP (Mastercard Prepaid Gold Payroll):
• Jamaica intracountry IRD JP
• Middle East/Africa region intraregional IRD 88
These changes are not marked with change bars.

Questions
• At-A-Glance
• Overview
• Customer Impact
• Enhancements
At-A-Glance

Overview

Products & Services: Prepaid
Release: 19.Q2
Region: All
Action Indicator:
Program or service requirement—Issuer
Testing recommended—Acquirer and issuer
Overview

Mastercard does not currently offer a higher-tiered payroll prepaid program.

Mastercard is introducing a new prepaid Gold Payroll product (MGP).
Why Mastercard Is Implementing These Enhancements

Mastercard is introducing this new product to leverage other services and digital assets of
Mastercard while also allowing issuers and payroll program managers to educate and
empower payroll cardholders.
With this new, higher-tiered product, Mastercard is building upon the benefits of existing
Prepaid Payroll products (global acceptance, compliance with local regulations, and
replacement for check- and cash-based compensation).

Reference Manuals
processing:
• Interchange Manual—Latin America and the Caribbean Region
• Interchange Manual—MEA Region
manuals.
Customer Impact

Network Mandate—Acquirers globally must support the new consumer credit product code
MGP.
Program or service requirement—Issuers in the Latin America and Caribbean and Middle East/
Africa regions that choose to issue cards under this product must recognize and support the
product code as described in this release announcement.
this announcement.


Enhancements
Message System:
Enhancements
Mastercard will enhance the following systems to support this announcement.
Mastercard will introduce new product code MGP with the product class override indicator
MGP.

Mastercard will add new product code MGP as a valid value in DE 63 (Network Data), subfield
1 (Financial Network Code).
New product code MGP will be available to Stand-In (the default amount limit will be set to
zero) and will not be allowed for X-Code processing.
Acquirers globally must support the new consumer prepaid product code MGP issued in the
Latin America and Caribbean and Middle East/Africa regions and identified in DE 63, subfield
1 in authorization messages.
Issuers in the Latin America and Caribbean and Middle East/Africa regions that choose to issue
the new product must be prepared to receive new product code MGP in DE 63, subfield 1 in
authorization messages.
Mastercard will update the Authorization Transaction Investigator to support new product
code MGP.

Mastercard will add new product code MGP as a valid value in PDS 0002 (GCMS Product
Mastercard will add new product code MGP to the appropriate IPM MPE tables.

Platform Impact
Mastercard will add new product code MGP to the appropriate interregional, intraregional,
intercountry, and intracountry interchange programs.
Acquirers globally must be prepared to recognize new product code MGP in both PDS 0002
and PDS 0003 when processing clearing transactions and to ensure that their systems
accurately qualify the product code for the appropriate interchange programs specified in this
announcement.
the new product must support the receipt of new product code MGP in both PDS 0002 and
PDS 0003.
Mastercard will update Quarterly Mastercard Reporting with new product code MGP.
Mastercard will update the Clearing Transaction Investigator to support new product code
MGP.
Single Message System—Acquirers, Issuers

Mastercard will add new product code MGP as a valid value in DE 110 (Additional Data—2),
subelement 8 (Product ID).
Mastercard will allow new product code MGP for cash access, including ATMs.
Acquirers globally must be prepared to recognize and accept new product code MGP when
processing transactions where DE 110, subelement 8 currently is supported and displayed in
the Single Message Transaction Manager.
the new product must support the receipt of new product code MGP where DE 110,
subelement 8 are supported currently and displayed in the Single Message Transaction
Manager.
Mastercard will also update the Single Message Transaction Manager to support new product
code MGP.
Platform Impact
Dual Message System
Single Message
Message Flows
Message Layouts

Platform Impact
Dual Message System
Single Message
IPM MPE √

and Associated MCCs
Edits
Error Numbers
Billing and Fees
Reports
Bulk Files
Forms
√
Reporting
SAFE

√
Manager

Table File

Authorization
Authorization

service.
®
MGP Mastercard Prepaid Gold Payroll √

Clearing
Product code MGP will be eligible for Stand-In processing, but will be defined with zero
amount default limits for the global TCC limit and accumulative limit tests. Product code MGP
will not be allowed for X-Code processing.
Mastercard will update the Authorization Transaction Investigator with new value MGP to
Clearing


Program Identifier.
GCMS Licensed
Product Product
(PDS (PDS
MGP MGP Mastercard® Prepaid Gold Payroll MGP—Mastercard® Prepaid Gold Payroll
IPM MPE
Mastercard will update the following IPM MPE tables with new product code MGP in the
Licensed Product ID field.
• IP0019T1—Account Level Management Participation and Enhanced Value Parameters
• IP0037T1—Selection Criteria Data
• IP0097T1—Message Reason Code Restrictions for Card Program Identifier and Business
Service Arrangement

Clearing
• IP0105T1—New Product Code Mapping
Interchange
Mastercard will add new consumer product code MGP (Mastercard Prepaid Gold Payroll)
under MCC acceptance brand to the indicated interregional, intraregional, intercountry, and
intracountry interchange programs.
20, 24, 2A, 73, 75, 79, 83, 85, 95, EZ, MS, QR
• Asia/Pacific Latin America and MCC added: MGP

• Canada the Caribbean
• Europe
• MEA
• U.S.
• Asia/Pacific MEA MCC added: MGP

• Canada
• Europe
the Caribbean
• U.S.
51, 52, AS

Clearing
Europe Latin America and MCC added: MGP

the Caribbean
Europe MEA MCC added: MGP
Latin America and the Caribbean Region Intraregional Interchange Programs (BSA 2/030001)
20, 24, 2A, 33, 34, 73, 75, 79, 83, 85, 95, MS, QR
Latin America and the Caribbean Region Intercountry Interchange Programs
Eastern Caribbean (3/030021) 2A
Argentina (4/032001) 2A, MS
Aruba (4/533001) 20, 2A, 33, 34, 73, 75, 83, 85, 95, MS
Bahamas (4/044001) 2A
Barbados (4/052001) 2A
Belize (4/084001) 01, 02, 03, 04, 05, 06, 07, 08, 09, 10, 11, 12, 2A, MS
Brazil (4/076000) 2A, MS
Cayman Islands (4/136001) 2A, MS
Colombia (4/170001) 2A, MS
Costa Rica (4/188001) 2A
Curaçao (4/531001) 2A, MS
Dominican Republic 2A
(4/214001)
Ecuador (4/218001) 2A
El Salvador (4/222001) 2A
Guatemala (4/320001) 2A

Clearing
Haiti (4/332001) 2A, 73, 75, 83, 85, 95, MS
Honduras (4/340001) 2A
Jamaica (4/388001) 2A, MS
Mexico (4/484001) 2A
Nicaragua (4/558001) 2A
Panama (4/591001) 2A, MS
Paraguay (4/600001) 2A
Peru (4/604001) 2A
Puerto Rico (4/630001) 2A, MS
Trinidad and Tobago 01, 02, 03, 04, 05, 06, 07, 08, 2A, MS
(4/780001)
Uruguay (4/858001) 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 2A, 30, MS
Venezuela (4/862001) 2A, QR
GCMS Product ID Consumer Credit—added: MGP
Middle East/Africa Region Intraregional Interchange Programs (2/060001)
20, 24, 2A, 33, 34, 73, 75, 79, 83, 85, 95, MS, QR
Bahrain (4/048001) 24, 33, 34, 73, 75, 79, 83, 85, 95
Egypt (4/818001) 20, 24, 2A, 33, 34, 73, 75, 79, 83, 85, 95, MP, MS, QR
Kenya (4/404001) 20, 24, 2A, 33, 34, 73, 75, 79, 83, 85, 95, L5, MS, QR
Kuwait (4/414001) 20, 24, 2T, 3C, 73, 75, 79, 83, 85, 95, L3
Lebanon (4/422001) 20, 24, 2T, 3C, 73, 75, 79, 83, 85, 95, L3, MS
Mauritius (4/480001) 24, 34, 73, 75, 79, 83, 85

Clearing
Oman (4/512001) 20, 24, 2T, 3C, 73, 75, 79, 83, 85, 95, L3
Pakistan (4/586001) 24, 33, 34, 73, 75, 79, 83, 85, 95, L5, QR
Saudi Arabia (4/682001) 20, 24, 33, 34, 73, 75, 79, 83, 85, 95, MS
Sub-Saharan1 24, 33, 34, 73, 75, 79, 83, 85, 95, L5, QR
United Arab Emirates 20, 24, 2A, 33, 34, 73, 75, 79, 83, 85, 95, L5, MS
(4/784001)
1 Sub-Saharan includes the following Middle/East Africa region countries:

Benin (4/204001), Burkina Faso (4/854001), Burundi (4/108001), Cameroon (4/120001),
Central African Republic (4/140001), Chad (4/148001), Congo (4/178001), Côte D’Ivoire
(4/384001), Djibouti (4/262001), Equatorial Guinea (4/226001), Ethiopia (4/230001), Gabon
(4/266001), Gambia (4/270001), Ghana (4/288001), Guinea (4/324001), Guinea-Bissau
(4/624001), Liberia (4/430001), Mali (4/466001), Niger (4/562001), Rwanda (4/646001),
Senegal (4/686001), Sierra Leone (4/694001), Somalia (4/706001), South Sudan (4/728001),
Tanzania (4/834001), Togo (4/768001), Uganda (4/800001)


For Quarterly Mastercard Reporting, issuers that choose to issue cards with new product code
MGP must report any activity associated with that product code with any Mastercard Credit
activity in the proper category.
Mastercard will update the Clearing Transaction Investigator with new product code MGP to


DE 110—Additional Data-2
Subelement 8—Product ID
DE 110, subelement 8 (Product ID) provides issuers additional information about Product ID,
also known as product code.
DE 110, Subelement 8, Product Identifier Values
Licensed Product Licensed Product Identifier Description

Identifier
®
MGP Mastercard Prepaid Gold Payroll

Single Message Transaction Manager

Mastercard will update the Single Message Transaction Manager to support new product code
MGP.

Question Answer
1. Does the absence of an applicable IRD for a If a country is absent from a list of intracountry
given country indicate no issuer interest or interchange programs, cards under product code
maybe regulation restrictions? MGP—as in this case—will not be issued in that
country. If an IRD is missing from a country’s list
of interchange programs, that IRD is not valid for
use with product code MGP.
2. Acquirers are sometimes surprised when an Prior to allowing the issuance of cards against a
IRD is added to a country, unannounced. Is new IRD in any given country, the Mastercard
there a Mastercard process that would keep interchange teams require customer
such an addition without external customer communication in the form of an interchange
communication? bulletin announcement. Customers with
evidence to the contrary can contact the Global
Customer Support team using the contact
information provided on the Technical Resource
Center home page. Customers may request that
their announcement-related questions are routed
to CTC–TRC–SUPPORT–ONCALL.

AN 1812—Product Codes to Support Humanitarian Organizations in Canada
Chapter 5 AN 1812—Product Codes to Support

Humanitarian Organizations in Canada
Mastercard previously announced plans to introduce two existing Mastercard prepaid products in
the Canada region to help humanitarian aid organizations deliver financial assistance more cost
effectively and digitally with an effective date of 12 April 2019. Previously provided details intended
to support this change are now removed from this announcement and will be rescheduled to
Release 19.Q4. No action is currently required for customers.
AN 1812—Product Codes to Support Humanitarian Organizations in Canada............................... 96

Version History..............................................................................................................................96

AN 1812—Product Codes to Support Humanitarian Organizations in

Canada
Mastercard previously announced plans to introduce two existing Mastercard prepaid products
in the Canada region to help humanitarian aid organizations deliver financial assistance more
cost effectively and digitally with an effective date of 12 April 2019. Previously provided details
intended to support this change are now removed from this announcement and will be
rescheduled to Release 19.Q4. No action is currently required for customers.
Version History

17 Jan 2019 Mastercard previously announced plans to introduce two Throughout
existing Mastercard prepaid products in the Canada region
to help humanitarian aid organizations deliver financial
assistance more cost effectively and digitally with an
effective date of 12 April 2019. Previously provided details
intended to support this change are now removed from this
announcement and will be rescheduled to Release 19.Q4.
11 Dec 2018 Added a Frequently Asked Questions section. Frequently Asked
Questions
• At-A-Glance
• Overview
• Customer Impact
• Enhancements

AN 1813—Standardization of the 80-byte Financial Institution Table File
Chapter 6 AN 1813—Standardization of the 80-byte

Financial Institution Table File
Effective with Release 19.Q2, Mastercard will support only one 80-byte Financial Institution Table
(FIT) file routing format.
AN 1813—Standardization of the 80-byte Financial Institution Table File....................................... 98

Version History..............................................................................................................................98
At-A-Glance..................................................................................................................................99
Enhancements.............................................................................................................................. 99
Frequently Asked Questions........................................................................................................ 102

AN 1813—Standardization of the 80-byte Financial Institution Table

File
Effective with Release 19.Q2, Mastercard will support only one 80-byte Financial Institution
Table (FIT) file routing format.
Version History
NOTE:
This announcement format is customized to provide the appropriate level of detail for this
enhancement and may not include all of the sections usually provided in a standard release
announcement.

11 Dec 2018 Updated the Frequently Asked Question section with four Frequently Asked
additional questions and responses. Questions
23 Oct 2018 Removed the Category row from the At-A-Glance section as At-A-Glance
it is no longer needed.
Revised the Action Indicator from Attention warranted
(Network-related) to Attention warranted (Network-
Mandate).
Changed “Enhancements Description” section title to Enhancements

Enhancements.
Clarified note indicating additional information and time
frames for customers to request the one standard 80-byte
FIT file.
Added positions 54 and 55 to the note for the MS ATM and
MS POS flags.
Added Implementation Alert section.
Added table describing the different scenarios that
customers may encounter when the Maestro Flag (position
42) contains a value of “Y”, indicating the BIN does support
Maestro-branded transactions.
Added a Frequently Asked Questions section Frequently Asked

Questions

At-A-Glance

At-A-Glance

Audience: Acquirer, Processor
Brands: Mastercard®, Debit Mastercard®, Maestro®, Cirrus®, Visa®
Release: 19.Q2
Region: All
System: Single Message System
Action Indicator:
Attention warranted (Network-Mandate)—Single Message System-
connected acquirers must be aware that effective with release 19.Q2,
Mastercard will support only one 80-byte Financial Institution Table (FIT) file
routing format. All acquirers must prepare their systems to accept the
additional MS ATM and MS POS fields (positions 54 and 55) in the existing
FIT Data Record (FITD)—for Durbin Unaffiliated Network Compliance version
of the 80-byte FIT file.
Testing recommended—Mastercard recommends testing for acquirers to
Effective Date: Single Message System: 12 April 2019
Enhancements
Effective with release 19.Q2, Mastercard will support only one standard 80-byte Financial
Institution Table (FIT) file routing format.
NOTE: Mastercard communicated this 19.Q2 release announcement early to customers. This
update provides the additional information and time frames for customers to request to
receive the standard 80-byte FIT file that will be effective 12 April 2019.

Enhancements
The 80-byte FIT file is used by acquirers to make processing and network routing decisions.
Traditionally, when a BIN (or account range) was set up for Maestro, both POS and ATM
transactions were valid. With new government regulations, additional information may be
needed to make an accurate determination for transaction routing.
Effective with Release 19.Q2, Mastercard will only support one standard 80-byte FIT file
routing format by consolidating a legacy version where a BIN (or account range) that was set
up for Maestro allowed both POS and ATM transactions with a standard version that provides
additional information for determination of routing Maestro ATM and/or POS activity to the
Single Message System.
The Maestro Routing Indicator fields, MS ATM and MS POS, found in the standard version are
to be used in conjunction with the existing Maestro Brand Flag (values Y or N) and should be
used to identify if POS and/or ATM activity can be routed to the Single Message System.
Valid values for both MS ATM and MS POS in positions 54 and 55 are:
• D—The BIN is eligible for Maestro-branded POS/ATM transactions when acquired in the
U.S. region, in a U.S. territory, or on U.S. military bases.
• B—The BIN is eligible for Maestro-branded POS/ATM transactions when acquired in any
region.
• N—The BIN is ineligible for Maestro-branded POS/ATM transactions. Acquirers should
continue to use the other brand flags to determine non-Maestro ATM eligibility.
These fields are only applicable when the Maestro Flag (position 42 of the 80-byte FIT file) is Y.
When the Maestro Flag is N, these fields should contain a value of N. The fields can not be
blank.
Acquirers must prepare their systems to accept the additional MS ATM and MS POS fields
(positions 54 and 55) in the standard version of the 80-byte FIT file. These fields should be
used to determine which BINs (or account ranges) are eligible for routing Maestro ATM or
Maestro POS transactions to the Single Message System. With Release 19.Q2, the legacy
version of the 80-byte Financial Institution Table (FIT) data file without the MS ATM and MS
POS fields will be obsolete.
NOTE: Acquirers that are currently using the FIT routing format that contains the MS ATM and
MS POS flags (positions 54 and 55) do not need to take any action.
Implementation Alert
Customers not currently receiving the 80-byte Financial Institution Table File (FIT Data Record
[FITD]—for Durbin Unaffiliated Network Compliance) format, and request to receive it prior to
the 12 April 2019 deadline, can contact Global Customer Service (GCS) prior to that date.
Effective 13 April 2019, customers will automatically receive the 80-byte Financial Institution
Table File (FIT Data Record [FITD]—for Durbin Unaffiliated Network Compliance) format in the
first delivery of the standard FIT file.

Enhancements
Scenarios
For those customers that are currently receiving the legacy 80-byte FIT file (without positions
54 and 55), the following table intends to illustrate the different scenarios they may encounter
when the Maestro Flag (position 42) contains a value of “Y”, indicating the BIN does support
Maestro-branded transactions.
Customers must consider the values in Positions 54 and 55 before deciding whether to route
a transaction to an issuer with that particular BIN.
Maestro Flag (Position 42) MS ATM (Position 54) MS POS (Position 55)
N N = BIN is not eligible for N = BIN is not eligible for

Maestro-branded ATM Maestro-branded POS
transactions. transactions
Y D = BIN is eligible for Maestro N = BIN is not eligible for

ATM transactions when acquired Maestro-branded POS
in the U.S. region, U.S. territory transactions
or U.S. military base.
Y D = BIN is eligible for Maestro B = BIN is eligible for Maestro

ATM transactions when acquired POS acquired in any region
in the U.S. region, U.S. territory
or U.S. military base.
Y D = BIN is eligible for Maestro D = BIN is eligible for Maestro

ATM transactions when acquired POS transactions when acquired
in the U.S. region, U.S. territory in the U.S. region, U.S. territory
or U.S. military base. or U.S. military base
Y B = BIN is eligible for Maestro N = Bin is not eligible for

ATM acquired in any region Maestro-branded POS
transactions
Y B = BIN is eligible for Maestro B = BIN is eligible for Maestro

ATM acquired in any region POS acquired in any region
Y B = BIN is eligible for Maestro D = BIN is eligible for Maestro

ATM acquired in any region POS transactions when acquired
in the U.S. region, U.S. territory
or U.S. military base
Y N = BIN is not eligible for D = BIN is eligible for Maestro

Maestro-branded ATM POS transactions when acquired
transactions. in the U.S. region, U.S. territory
or U.S. military base

Maestro Flag (Position 42) MS ATM (Position 54) MS POS (Position 55)
Y N = BIN is not eligible for B = BIN is eligible for Maestro

Maestro-branded ATM POS acquired in any region
transactions.

Question Answer
1. How can I tell if I’m receiving the standard If the version you have contains data in positions
version or the legacy version? 54 and 55 then you have the standard format
and not the legacy format.
2. Why is Mastercard mandating this change? The 80-byte FIT file is used by acquirers to make
processing and network routing decisions.
Traditionally, when a BIN (or account range) was
set up for Maestro, both POS and ATM
transactions were valid. With new government
regulations, additional information may be
needed to make an accurate determination.
This change will simplify the customer decision
process for setting up delivery of the 80-byte FIT
file.
3. What will happen if I currently receive the If you’re receiving the legacy version of the 80-
legacy version and don’t prepare for this byte FIT File, you may see differences in BINs
change? enabled for Maestro, which may result in mis-
routing of transactions.
4. Why is the first delivery of the standard file on The file delivery on the 12th will happen before
13 April and not 12 April? system changes become effective on 12 April, so
the first delivery of the standard format will occur
on the 13th (for daily file delivery), or on 19 April
(for weekly file delivery).
5. Once Mastercard changes the structure and Both the 80-byte FIT and the IPM MPE are
we see the Maestro flag as "N", should we parameters that Mastercard provides to
decline the transaction or send to Mastercard customers to help them in their routing. We are
to decline? If we should decline, which not able to advise you on how to respond, but
response code should we use? are providing the additional information to
ensure acquirers can route the transaction
correctly.

Question Answer
6. Can I start using the new standard format Yes, customers can request to receive the new
that was available as of July 2018? standard format now, which will include the new
indicators in positions 54 and 55. Mastercard
communicated this a 19.Q2 release
announcement early to customers to provide
additional time to be prepared to receive the
new format.
7. When will the old version of the 80 Byte-FIT April 12 is the date that the old version of the
file be discontinued? Will there be a transition 80-Byte-Fit file will be discontinued, and that is
period? when Mastercard will start supporting only the
new standard version. The transition period
started from July 2018 (when it was first
published) to April 12, 2019.
8. Will bulk files be updated to support the new The current Production Bulk ID T458, and the
standard format and if so, which ones are Mastercard Test Bulk ID T459, are applicable.
applicable?

AN 2108—Switching Release 19.Q2—Related Bulletins
Chapter 7 AN 2108—Switching Release 19.Q2—Related

Bulletins
Use this document to locate bulletin announcements that may be related to the 19.Q2 Switching
Release.
AN 2108—Switching Release 19.Q2—Related Bulletins.............................................................. 105

Version History............................................................................................................................105
Switching Release 19.Q2—Related Bulletins................................................................................106


Use this document to locate global bulletin announcements that may be related to the 19.Q2
Switching Release.
A bulletin announcement is considered related to this release when the bulletin conveys:
• An effective date that coincides with the Switching Release implementation date.
• Business-related details for enhancements planned for this release. Examples include
pricing, rules/standards, or other types of content.
Mastercard makes every effort to include in this list all global bulletins that may be related to
this release. This list is provided as a convenience, and customers are responsible for reviewing
all available content and understanding the impact to their operations.
Version History
Announcements may be frequently updated on the Technical Resource Center. Refer to the
version history in each announcement to understand revisions.
11 Dec 2018 Clarified that the bulletin announcements provided herein Throughout
are global bulletin announcements.
Added the following bulletin announcement: Switching Release

19.Q2—Related
• AN 2259—Revised Standards—Merchant Category Code
Bulletins
9754

Switching Release 19.Q2—Related Bulletins

The following bulletin announcements are related to the 19.Q2 Switching Release. Bulletin
announcements provided here may have been updated since the date of their initial
publication.
Initial
Publication Related Bulletin Related Release
Date Announcement System Applies to Announcement Category
30 Oct 2018 AN 2259—Revised Authorization Acquirers Operations

Standards—
Merchant Category Clearing Issuers Rules/
Code 9754 Standards
Single Message
System
4 Sep 2018 AN 2042—Revised Authorization Acquirers Operations

Standards—Point-
of-Interaction Issuers POI
Currency Rules/
Conversion Standards
31 Aug AN 1430—Revised Authorization Acquirers Operations

2018 Standards—Online
Authorization of Single Message Issuers POI
Refund Transactions System Rules/
Standards
Security
30 Jul 2018 AN 2010—Revised Authorization Acquirers Operations

Standards—
Cardholder Clearing Issuers Rules/
Verification Method Standards
Limit Amounts in
Brunei
23 Jul 2018 AN 1943—Revised Authorization Acquirers Operations

Standards—
Cardholder Clearing Issuers Rules/
Verification Method Standards
Limit Amounts in
Bulgaria,
Montenegro, and
Serbia

Initial
Publication Related Bulletin Related Release
Date Announcement System Applies to Announcement Category
16 Jul 2018 AN 1663— Clearing Acquirers AN 1807 Interchange

Mastercard
Announces Issuers
Mastercard
Enterprise Solutions
—Freight Program
Interchange Rate
14 Jun 2018 AN 1528—M/Chip Authorization Issuers Operations

Advance
Requirement for
Issuance of Chip
Cards and Non-
Mobile Payment
Devices
15 May AN 1775—Revised Clearing Acquirers Operations

2018 Dispute Resolution
Forms Single Message Issuers
System
19 Mar AN 1674—Dispute Clearing Acquirers Operations

2018 Resolution Initiative
—Revised Dispute Single Message Issuers Rules/
Processing and System Standards
Chargeback Rules Security

AN 2111— Support of 8-Digit BIN Standard and Account Range Specifications—Reminder
Chapter 8 AN 2111— Support of 8-Digit BIN Standard and

Account Range Specifications—Reminder
Mastercard is reminding acquiring customers and their processors of the recent mandate to support
an 8-digit BIN standard and transaction processing using the first 11 digits of the primary account
number (PAN). Mastercard issuing customers and their processors are not required to make
changes associated with this enhancement, but they are encouraged to follow the new Mastercard
acquirer standards.
AN 2111— Support of 8-Digit BIN Standard and Account Range Specifications—Reminder........ 109
Version History............................................................................................................................109
At-A-Glance................................................................................................................................110
Overview.................................................................................................................................... 111
Related Documentation.............................................................................................................. 115
Customer Impact........................................................................................................................ 116
Enhancements............................................................................................................................ 117
Platform Impact.......................................................................................................................... 119
Authorization..............................................................................................................................120
Reports.................................................................................................................................. 120
Forms.....................................................................................................................................120
Clearing......................................................................................................................................121
IPM Data Element and Private Data Subelement Definitions....................................................121
DE 31—Acquirer Reference Data....................................................................................... 121
Edits.......................................................................................................................................121
Reports.................................................................................................................................. 121
Forms.....................................................................................................................................121
Single Message System............................................................................................................... 122
Reports.................................................................................................................................. 122
Forms.....................................................................................................................................122

AN 2111— Support of 8-Digit BIN Standard and Account Range

Specifications—Reminder
Mastercard is reminding acquiring customers and their processors of the recent mandate to
support an 8-digit BIN standard and transaction processing using the first 11 digits of the
primary account number (PAN). Mastercard issuing customers and their processors are not
required to make changes associated with this enhancement, but they are encouraged to
follow the new Mastercard acquirer standards.
Version History

11 Dec 2018 Under Overview, What Mastercard Is Going to Do, updated Overview
the following verbiage:
• “ISO announced a move to an 8-digit Institution
Identification Number (IIN) standard (IIN is the ISO term
for BIN) in 2016 (ISO/IEC 7812–1, ISO/IEC 7812–2) and
published the new standard in 2017. Mastercard will
conform to the new standard to better support
ecosystem-wide consistency for acquirers”.
Under Enhancements, Dual Message System (Authorization Enhancements

and Clearing) and Single Message System—Issuer, updated
the following verbiage:
• Issuers should recognize that DE 31 (Acquirer Reference
Data), subfield 2 (Acquirer Reference ID) will no longer be
referred to as Acquirer BIN. Instead, subfield 2 will
become Acquirer Reference ID, and will continue to be a
six-digit identifier assigned by Mastercard, but not
considered to be a BIN.
• Issuer service providers, including processors, are strongly
recommended to be:
– Able to support the full account range (up to 11
digits) and 8 digit BINs for all Mastercard, Maestro,
and Cirrus branded products (credit, debit, and
prepaid product types, both consumer and
commercial).
Under Authorization, Reports, added reference to Weekly Reports

(CAT) Authorization Summary Reports (SI458010-AA) and
Weekly Member Information (MIS) Authorization Summary
Report (AB505010-AA).

At-A-Glance

Under Clearing, Reports, added reference to Issuer Reports
Adjustment Summary Report (FC212010-AA).
At-A-Glance

Release: 19.Q2
Region: All
Action Indicator:
Attention warranted (Network-related)—Issuer
Testing required—Acquirer
Testing recommended—Issuer
Effective Date: Dual Message System (Authorization and Clearing) and Single Message
System:
• Testing Available Date: April 2019
• Implementation Date: April 2022 (Release 22.Q2)—Payment ecosystem
to support Mastercard 8-digit BINs and account ranges (up to 11 digits)
Dual Message System (Clearing):
• Implementation Date: April 2022 (Release 22.Q2)—Acquirer BIN change
to Acquirer Reference ID

Overview
Overview
Background
With Release 17.Q4, Mastercard introduced the 8-Digit BIN standard and account range
specifications.
BINs uniquely identify networks, issuers, and other important information across the
Mastercard payments ecosystem. BINs are a fundamental element of electronic payments, and
must be managed effectively. A continuous supply of BINs is necessary to help ensure a
sustainable, safe, and secure global payments ecosystem, enabling growth and innovation in
an increasingly digital world. Mastercard began a phased approach addressing BIN supply
challenges a number of years ago, and, in 2014, began addressing issues regarding increasing
BIN demand.

While the ability to process by account range is an existing Mastercard requirement and
processing capability, many acquirers and their service providers, including processors, do not
currently process on an account range level. Mastercard has allowed issuers to use specific
account ranges within BINs to segment programs and to provide other capabilities and
benefits. Today, a majority of issuer programs use entire BINs while some issuers split their BINs
into multiple account ranges using the same product type. Currently, BIN-level processing is
common as acquirers may be able to successfully authorize and to settle via BINs or account
ranges, but this is not sufficient. Inability to process at the account range level could cause
incorrect interchange application and transaction declines.

Increasing BIN demand across the electronic payments ecosystem has created the need for the
extension of BINs from the first 6 digits of a PAN to the first 8 digits of a PAN. Increasing the
length of the PAN will not occur. Emerging payment technologies, including tokenization,
have impacted BIN demand, as tokenization uses multiple PANs for a single account.
ISO announced a move to an 8-digit Institution Identification Number (IIN) standard (IIN is the
ISO term for BIN) in 2016 (ISO/IEC 7812–1, ISO/IEC 7812–2) and published the new standard
in 2017. Mastercard will confirm to the new standard to better support ecosystem-wide
consistency for acquirers.
In an effort to address BIN supply challenges, Mastercard began a phased approach using
several efficiency measures. For example, Mastercard launched a 2 series BIN range (222100–
272099), which increases the number of BINs available to customers. Mastercard is sharply

Overview
focused on 2 series BIN implementation across acquirers, issuers, processors, third party
providers, and merchants, and Mastercard has begun to assign 2 series BINs to customers.
Mastercard will further drive an emphasis on the efficient use of BINs through the use of
account ranges. Account ranges allow a customer to maximize the full potential of each
Mastercard BIN. Account ranges enable an issuer to use a single BIN to support many
programs of the same type. The use of account ranges allow an issuer to segment programs
in order to provide other capabilities and benefits. This strategy leverages existing
requirements for Mastercard customers to support 11-digit account ranges.
To help ensure ecosystem readiness, Mastercard is mandating that all acquirers and their
service providers, including processors, support 11-digit account ranges and the 8-digit BIN
standard by April 2022.
Mastercard will continue to send profile files to acquirers and their service providers, including
processors, at the account range level. These files include:
• Dual Message System (Authorization): BIN Table Resource File (TR52 [production]/TR54
[test] bulk file)
• Dual Message System (Clearing): Integrated Product Message Member Profile Extract (IPM
MPE) (T167 [production]/T168 [test])
• Single Message System: 80-byte Financial Institution Table (FIT)
NOTE: The 80-byte Financial Institution Table (FIT) contains BIN extensions. For additional
information, refer to the Single Message System chapter in the Account Range Management
User Manual.
In addition, Mastercard has BIN table resources available for all customers and their partners
upon request. Additional information is located on the Mastercard Developer site. The
Account Range Management User Manual serves as a central resource for customers to access
all information related to account range management and the adoption of any new digital
payment flows. For more information, refer to the “BIN Expansion Mandate and Best Practices
(8-Digit BINs and Account Ranges),” in Global Operations Bulletin No. 5, 1 May 2017.
• 2 Series BIN Mandate Reminder
The 2 series BIN was first introduced in 2014 and mandated in December 2015 as
described in “Global 585—Introduction of New 2 Series Mastercard BIN”, published in
Release 15.Q2. This mandate remains a priority, and Mastercard has already started to issue
2 series BINs in select markets. The 2 series BIN assignments to issuers will continue with
increased frequency.
Accordingly, acquirers and their processors are reminded that all merchants and acceptance
points of interaction were required to be 2 series BIN compliant by 14 October 2016 and
that the compliance program began 30 June 2017. Issuers are also reminded that issuers
were required to be 2 series BIN compliant by 14 October 2016. Mastercard has begun to
issue 2 series BINs to customers and issuers, and they may receive a 2 series BIN when
requesting a new BIN subject to Mastercard’s discretion.
• Account Ranges

Overview
Mastercard customers use account ranges to maximize efficient use of a BIN. Account
ranges are defined with unique processing attributes such as products, programs, regions,
and affiliates and are shared with Mastercard customers.
Currently, account ranges are considered to be up to the first 11 digits of a PAN, including
the 6-digit BIN.
In the future, account ranges will remain up to the first 11 digits of a PAN, including the 8-
digit BIN. Neither the account range length nor the overall PAN length will increase with
the introduction of 8-digit BINs.
Account ranges are up to 11 digits and inclusive of the BIN. If account range processing is
properly used, the transition from 6 to 8-digit BINs should be seamless. For example, card
5412 7512 3412 3456 has account range 5412 7512 341. Today, the BIN can be obtained
by parsing the first 6 digits: 5412 75. After April 2022, the BIN will be obtained by parsing
the first 8 digits. With both of these BIN standards, the account range is consistent.
Current 6-digit Mastercard BINs will be regarded as 8-digit BINs beginning April 2022. Each
6-digit BIN (for example, 541275) will encompass 100, 8-digit BINs as shown in the
following table.

Overview
BIN Length BIN Range Example
6-Digit BIN 541275
8-Digit BIN 541275–00 through 541275–99
Mastercard BIN requirements for product code classifications are currently defined by
region, and will remain intact for 6-digit BINs until April 2022, when these classifications
will then apply to 8-digit BINs. For example, consumer and commercial products must be
issued from unique BINs. Refer to updated guidelines and best practices for each region set
forth in the Related Information section of this announcement.
If the customer intends on using 8-digit BINs, refer to the example below on how to
account range.
Account Ranges for BIN 54127512
From Through Products
54127512 000 54127512 554 Consumer Credit Gold (555

ranges)
54127512 555 54127512 799 Consumer Credit Platinum (245

ranges)
54127512 800 54127512 999 Inactive/non-issued range (200

ranges)
• Mastercard BIN Expansion Information Center

The Mastercard BIN Expansion Information Center located on Publications via Mastercard
Connect™ is a centralized resource for 8-digit BIN expansion, 2 series BINs, and account
range processing. This information center will provide access to all information about the
Mastercard 8-digit BIN initiative, including announcements, related bulletins and release
information, testing, test cases, and Frequently Asked Questions.
Why Mastercard Is Implementting These Enhancements

These enhancements are aligned with the industry’s strategy to expand BIN supply to support
the future of payments.

Announcements
Refer to these previously published announcements for more information:
• “BIN Expansion Mandate and Best Practices (8-Digit BINs and Account Ranges),” Global
Operations Bulletin No. 5, 1 May 2017
• “Updated Mastercard Guidelines and Best Practices for BIN Management and Account
Ranges,” Middle East/Africa Region Operations Bulletin No. 2, 12 April 2017
• “Updated Mastercard Guidelines and Best Practices for BIN Management and Account
Ranges,” Asia Pacific Region Operations Bulletin No. 3, 17 March 2017
• “Updated Mastercard BIN Management Guidelines and Best Practices,” Europe Region
Operations Bulletin No. 12, 1 December 2016
• “Updated Mastercard BIN Management Guidelines and Best Practices,” Latin America and
Caribbean Region Operations Bulletin No. 7, 24 October 2016
• “Updated Mastercard BIN Management Guidelines and Best Practices,” Canada Region
Operations Alert No. 7, 29 August 2016
• “Updated Mastercard BIN Management Guidelines and Best Practices,” U. S. Region
Operations Bulletin No. 7, 9 June 2016
• “Requirement to Maintain Accurate BIN Tables,” Global Operations Bulletin No. 4, 1 April
2014
• “AN 1632—Support of 8-Digit BIN Standard and Account Range Specifications—
Reminder,” Release 18.Q4
• “AN 1094—Support of 8-Digit BIN Standard and Account Range Specifications—
Reminder,” Release 18.Q2
• “AN 1018—Support of 8-Digit BIN Standard and Account Range Specifications,” Release
17.Q4
• “Global 514—Introduction of New 2 Series Mastercard BIN Range—Update,” Release
16.Q4
Reference Manuals
processing:
• Account Range Management User Manual
• Customer Interface Specifications
• GCMS Reference Manual
• Interchange Manuals

Customer Impact

manuals.
Customer Impact

Network Mandate—Acquirers and their service providers, including processors, must support
the enhancements as described in this announcement. Acquirers not implementing the
enhancements in this announcement will risk mishandling of transactions and will not be in
compliance.
Attention warranted (Network-related)—Issuers and their service providers, including
processors, are strongly recommended to implement the enhancements as described in this
announcement. Issuers that opt not to implement the enhancements in this announcement
will not benefit from the cost effectiveness and operational efficiencies of account ranges.
Testing required—Mastercard requires testing for acquirers and their processors.
Testing recommended—Mastercard recommends testing for issuers and their service providers,
including processors.


Enhancements
Message System:
Enhancements
Dual Message System (Authorization and Clearing) and Single Message System—
Acquirer, Issuer
Mastercard will adopt an 8-digit BIN standard and has mandated account range-level
processing readiness for acquirers and their service providers, including processors, by April
2022. Mastercard will also strongly recommend account range usage for issuers in conjunction
with implementation of the 8-digit BIN standard.
Mastercard will make the following enhancements:
• Adoption of 8-digit BIN standards.
• Account range-level processing mandate for acquirers and their service providers, including
processors.
• Strong recommendation of account range usage for issuers and account range support for
their service providers, including processors.
• Renaming of Dual Message System (Clearing) DE 31 (Acquirer Reference Data), subfield 2
from Acquirer BIN to Acquirer Reference ID. Mastercard will no longer use an acquiring BIN
to identify an acquirer in this subfield.
Eight-digit BINs (in the 22210000–27209999 and 51000000–55999999 ranges) and
associated account ranges (up to 11 digits) will be processed in the same manner as the
222100–272099 and 510000–559999 series and 6-digit BINs on all Mastercard systems.
Acquirer
Acquirers and their service providers, including processors, will:
• Be able to support the full account range (up to 11 digits) and 8-digit BINs for all
Mastercard®, Maestro®, and Cirrus®-branded products (credit, debit, and prepaid types,
both consumer and commercial). Acquirers must determine the impact on their operations.
• Use full account range level data to avoid processing transactions incorrectly, which could
result in incorrect interchange rate application or transaction declines.
• Be aware that DE 31 (Acquirer Reference Data), subfield 2 (Acquirer Reference ID) on the
Dual Message System (Clearing) will no longer be referred to as Acquirer BIN. Instead,
subfield 2 will become Acquirer Reference ID, and will continue to be a 6-digit identifier
assigned by Mastercard, but not considered to be a BIN.

Enhancements
• Recognize that both card-present and card-not-present channels must be updated to

process full account ranges (up to 11 digits).
– Terminal configuration and software updates may be required to process full account
ranges (up to 11 digits).
– E-commerce transactions updates may be required for web interfaces to process full
account ranges (up to 11 digits).
• Be responsible for tracking implementation of all merchants that maintain a merchant
agreement for all card acceptance endpoints and all card input methods.
• Perform testing in support of the 8-digit BIN standard and account ranges (up to 11 digits).
• Be aware that the Single Message System will continue to use BIN extensions to represent
BIN and account range configurations. For additional information, refer to the Single
Message System chapter in the Account Range Management User Manual.
NOTE: Acquirers will be responsible for ensuring that their merchants, payment facilitators,
payment gateways, third party vendors, and all other service providers, including processors,
are ready to support account range processing and the 8-digit BIN standard by April 2022.
Issuer
Issuers will be recommended to:
• Maximize their BIN capacity through the use of account ranges. Account ranges allow for
multiple programs and/or products to be assigned under a single BIN, enhancing the usage
of Mastercard, Maestro, and Cirrus BIN assets.
• Analyze their current programs in order to determine if existing Mastercard BINs can be
used more efficiently with account ranges and return any unused BINs.
• Use an existing BIN when requesting a new program. Existing BINs can be split into
multiple products using account ranges—guided by local rules, regulations, and regional
practices.
• Activate only those account ranges for programs that will be issued in the near-term. This
can increase safety and security by helping ensure that transactions from PANs falling
outside an active account range are declined by Mastercard and will not be sent to the
issuer or approved during Stand-In processing.
• Be aware that the Single Message System will continue to use BIN extensions to represent
BIN and account range configurations. For additional information, refer to the Single
Message System chapter in the Account Range Management User Manual.
Issuers should recognize that DE 31 (Acquirer Reference Data), subfield 2 (Acquirer Reference
ID) on the Dual Message System (Clearing) will no longer be referred to as Acquirer BIN.
Instead, subfield 2 will become Acquirer Reference ID, and will continue to be a 6-digit
identifier assigned by Mastercard, but not considered to be a BIN.
Issuers that support account ranges will:
• Help ensure that their platforms are capable of handling account ranging before they
define programs at the account range level such as online banking and cardholder

Platform Impact
statements, host systems, fraud and dispute management, card design and
personalization, loyalty and rewards, and customer service.
• Be responsible for ensuring that their service providers, including processors, wallets, card
production suppliers, and software providers are ready to support account range
processing by April 2022.
Issuer service providers, including processors, are strongly recommended to be:
• Able to support the full account range (up to 11 digits) and 8-digit BINs for all Mastercard,
Maestro, and Cirrus-branded products (credit, debit, and prepaid, both consumer and
commercial).
Platform Impact
Dual Message
Message Flows
Message Layouts
Data Element Definitions √
IPM MPE
Interchange

and Associated MCCs
Edits √
Error Numbers
Pricing/Fees
Reports √ √ √
Bulk Files
Forms √ √ √
Reporting

Authorization
Dual Message
SAFE

Manager

Table File
Authorization
Reports
The Weekly (CAT) Authorization Summary Reports (SI458010-AA) and Weekly Member
Information (MIS) Authorization Summary Report (AB505010-AA) will be enhanced to support
account range level fields.
Forms
Forms that currently provide BIN level fields will be enhanced to support account range level
fields. The Acquirer BIN will be referred to as Acquirer Reference ID on all forms.
NOTE: Details of impacted forms will be provided in a future announcement.

Clearing
Clearing

DE 31—Acquirer Reference Data

DE 31 (Acquirer Reference Data) is data in which an acquirer supplies in an acquirer-originated
message that may be required for an issuer to return to the acquirer in a subsequent message.
DE 31 Subfields
The Acquirer Reference Data format consists of five subfields, including subfield 2 (Acquirer
Reference ID), which is specified in the following table.
Subfield 2 (Acquirer Reference ID)
Number Positions Name Attribute Justification
2 2–7 Contains the 6-digit Acquirer Reference n-6 right

ID
Edits
The Clearing Platform will continue to perform the same edits for transactions with primary
account numbers in account ranges (up to 11 digits) as performed today. DE 31 (Acquirer
Reference Data), subfield 2 (Acquirer Reference ID) will be referred to as Acquirer Reference ID
in all error messages.
Reports
The Issuer Adjustment Summary Report (FC212010-AA) will be enhanced to support account
range level fields.
Forms
Forms that currently provide BIN level fields will be enhanced to support account range level
fields. The Acquirer BIN will be referred to as Acquirer Reference ID on all forms.


Reports
Reports that currently provide BIN Number fields will continue to support BINs and BIN
extensions from 6-digits to 11-digits.
NOTE: Details of impacted reports will be provided in a future announcement.
Forms
Forms that currently provide BIN level fields will be enhanced to support account range or BIN
extension level fields.

AN 2113—Enhancements to AAV Validation for EMV 3-D Secure
Chapter 9 AN 2113—Enhancements to AAV Validation for

EMV 3-D Secure
Mastercard is introducing new Security Level Indicator (SLI) values and modifying the existing
Universal Cardholder Authentication Field (UCAF) downgrade logic applicable to transactions
authenticated using the Mastercard Identity Check/SecureCode service. These enhancements are
being made in support of Mastercard's use of the Secure Payment Application (SPA) algorithm
(SPA2) introduced by the EMV® 3-D Secure 2.0 authentication protocol.
AN 2113—Enhancements to AAV Validation for EMV 3-D Secure............................................... 124

Version History............................................................................................................................124
At-A-Glance................................................................................................................................125
Overview.................................................................................................................................... 126
Customer Impact........................................................................................................................ 127
Enhancements............................................................................................................................ 128
Platform Impact.......................................................................................................................... 136
Authorization..............................................................................................................................137
CIS Data Element Definitions.................................................................................................. 137
DE 48—Additional Data—Private Use................................................................................ 137
Clearing......................................................................................................................................138
Edits.......................................................................................................................................138
Modified Edit—PDS 0052 (Electronic Commerce Security Level Indicator), Subfield 3
(UCAF Collection Indicator)................................................................................................138
Error Numbers................................................................................................................... 139
Single Message System Data Element Definitions....................................................................139
DE 48—Additional Data.....................................................................................................139


Mastercard is introducing new Security Level Indicator (SLI) values and modifying the existing
Universal Cardholder Authentication Field (UCAF) downgrade logic applicable to transactions
authenticated using the Mastercard Identity Check/SecureCode service. These enhancements
are being made in support of Mastercard's use of the Secure Payment Application (SPA)
algorithm (SPA2) introduced by the EMV® 3-D Secure 2.0 authentication protocol.
Version History

11 Dec 2018 Updated the Overview to support the following changes: Overview
• Under What Mastercard Is Currently Doing, updated
verbiage to “Similarly, the current Mastercard Security
Level Indicator (SLI) downgrade functionality is able to
validate the SLI value and downgrade it as needed when
the AAV is generated using the SPA1 algorithm and SPA2
using the SHA1 key”.
• Under What Mastercard Is Going to Do, updated
verbiage to “ Mastercard will validate SPA2 AAVs using a
SHA 256 key against the SLI to determine the retention
of liability shift. In chance of a mismatch use case,
Mastercard will downgrade the transaction from
authenticated to non-authenticated, which does not
provide liability shift”.

At-A-Glance

Updated the Enhancements to support the following Enhancements
change:
• Under Dual Message System (Authorization) and Single
Message System—Acquirers, Issuers, updated verbiage to
“Issuers that are registered for OBS 05 or OBS 06
services, along with those issuers that self-validate, will:
– Receive appropriate new positions 1 and 2 control
byte values kA, kB, kC, kD, kE, kF, kN, kO, and kP and
existing position 1 control byte values h or j in
Authorization Request/0100, Authorization Advice/
0120—Acquirer-generated, Financial Transaction
Request/0200, and Financial Transaction Advice/0220
messages in DE 48, subelement 43.
– Support new SLI values 216 and 217 in DE 48,
subelement 42, subfield 1, position 1–3 for
Authorization Request Response/0110 and Financial
Transaction Request Response/0210 messages”.

Questions
At-A-Glance

Brands: Mastercard®, Debit Mastercard®, Maestro®
Release: 19.Q2
Region: All
Action Indicator:
Network Mandate—Acquirer, Issuer

Overview
Effective Date: Dual Message System (Authorization): 11 June 2019

Dual Message System (Clearing): 11 June 2019
Single Message System: 11 June 2019
Overview
Background
The SPA2 algorithm is designed to simplify Accountholder Authentication Value (AAV)
generation for the Access Control Server (ACS) while allowing Mastercard to better manage
the content and validation of the AAV to support Mastercard Identity Check.
Mastercard supports the EMV 3-D Secure 2.0 authentication protocol, which introduced the
SPA2 algorithm to generate AAV values as part of Mastercard Identity Check. The existing
AAV validation services, On-behalf Services (OBS) 05 (Mastercard® SecureCode AAV
Verification Service) and OBS 06 (Mastercard® SecureCode Dynamic AAV Verification in Stand-
In Processing), are being updated to validate new EMV 3-D Secure 2.0 use cases using the
SPA2 algorithm.

The OBS 05 and OBS 06 services are able to validate Mastercard Identity Check/SecureCode
transactions when the EMV 3-D Secure AAV is generated using SPA1 and SPA2 algorithms.
Similarly, the current Mastercard Security Level Indicator (SLI) downgrade functionality is able
to validate the SLI value and downgrade it as needed when the AAV is generated using the
SPA1 algorithm and SPA2 using the SHA1 key.

Mastercard will validate SPA2 AAVs using a SHA 256 key against the SLI to determine the
retention of liability shift. In chance of a mismatch use case, Mastercard will downgrade the
transaction from authenticated to non-authenticated, which does not provide liability shift.

By downgrading transactions, Mastercard is maintaining the integrity of the Mastercard
Identity Check program.

Announcements
• “AN 1085—AAV Validation for EMV 3-D Secure,” Release 18.Q2
Reference Manuals
processing:
• Mastercard Identity Check Program Guide
• SPA2 AAV for the Mastercard Identity Check Program
manuals.
Customer Impact

Network Mandate—Acquirers and issuers must support the enhancements as described in this
announcement. Acquirers not implementing the enhancements in this announcement will risk
issuer declines of valid transactions and liability shift and interchange errors. Issuers not
implementing the enhancements in this announcement may provide unsecured transactions
to customers and will not help to ensure the proper liability shift.
Testing recommended—Mastercard strongly recommends testing for acquirers and issuers.


Enhancements
Message System:
Enhancements
The OBS 05 and OBS 06 services will be modified to recognize the new AAV control byte
values which represent the new EMV 3-D Secure use cases. Refer to the Mastercard Identity
Check Program Guide and SPA2 AAV for the Mastercard Identity Check Program for additional
information.
Dual Message System (Authorization) and Single Message System—Acquirer, Issuer

Mastercard will:
• Introduce new positions 1 and 2 control byte values kA, kB, kC, kD, kE, kF, kN, kO, and kP
in DE 48 (Additional Data), subelement 43 (3–D Secure for Mastercard SecureCode) for the
SPA2 AAV validation in EMV 3-D Secure transactions. These values will be contained in the
SPA2 AAV.
• Enhance the SLI downgrade logic for SPA2 AAVs that will validate and, when necessary,
modify the SLI in DE 48, subelement 42 (Electronic Commerce Indicators), subfield 1
(Electronic Commerce Security Level Indicator and UCAF Collection Indicator), positions 1–3
in Authorization Request/0100 messages and Financial Transaction Request/0200
messages. Mastercard Identity Check/Mastercard SecureCode downgrade edits will be
updated to include these new positions 1 and 2 control byte values. Mastercard Identity
Check/Mastercard SecureCode transaction SLIs will be downgraded due to the presence of
these new positions 1 and 2 control byte values in DE 48, subelement 43.
• Introduce the following two new SLI values for Mastercard Identity Check:
216 (PDS2 Acquirer Exemption)
– Position 1 (Security protocol) = 2 (Channel)

Enhancements
– Position 2 (Cardholder authentication) = 1 (eCommerce/SecureCode)

– Position 3 (UCAF Collection Indicator) = 6 (Merchant Risk Based Decisioning)
217 (Split Shipment/Recurring Payment)
– Position 1 (Security protocol) = 2 (Channel)
– Position 2 (Cardholder authentication) = 1 (eCommerce/SecureCode)
– Position 3 (UCAF Collection Indicator) = 7 (Partial shipment or recurring payment)
• Send the correct SLI to the issuer in Authorization Request/0100 messages and Financial
Transaction Request/0200 messages.
• Notify acquirers when the SLI has been corrected in Authorization Request Response/0110
and Financial Transaction Request Response/0210 messages.
Acquirers will:
• Help to ensure SLIs associated with the transaction matches the appropriate new positions
1 and 2 control byte values kA, kB, kC, kD, kE, kF, kN, kO, and kP and existing position 1
control byte values h or j in Authorization Request/0100, Authorization Advice/0120—
Acquirer-generated, Financial Transaction Request/0200, and Financial Transaction Advice/
0220 messages in DE 48, subelement 43.
• Receive DE 48, subelement 42, subfield 1, positions 1–3 in Authorization Request
Response/0110 or Financial Transaction Request Response/0210 messages. When
Mastercard modifies DE 48, subelement 42, subfield 1, position 1–3 SLI values originally
provided by acquirers in Authorization Request/0100 or Financial Transaction Request/0200
messages, acquirers will receive the modified SLI in DE 48, subelement 42, subfield 1, the
original SLI in DE 48, subelement 42, subfield 2, and the reason for the modification in DE
48, subelement 42, subfield 3 in Authorization Request Response/0110 and Financial
Transaction Request Response/0210 messages.
• Receive SLI values 216 and 217 in DE 48, subelement 42, subfield 1, position 1–3 in
Authorization Request Response/0110 and Financial Transaction Request Response/0210
messages.
Issuers that are registered for OBS 05 or OBS 06 services, along with those issuers that self-
validate, will:
• Receive appropriate new positions 1 and 2 control byte values kA, kB, kC, kD, kE, kF, kN,
kO, and kP and existing position 1 control byte values h or j in Authorization Request/0100,
Authorization Advice/0120—Acquirer-generated, Financial Transaction Request/0200, and
Financial Transaction Advice/0220 messages in DE 48, subelement 43.
• Support new SLI values 216 and 217 in DE 48, subelement 42, subfield 1, position 1–3 for
Authorization Request Response/0110 and Financial Transaction Request Response/0210
messages.
NOTE: If determined to have been generated by the SPA1 algorithm, the transaction will
process as it does today for OBS 05 and OBS 06.
The first two characters of the UCAF string must be used to determine if the value was ACS
processed (authenticated), Attempts processing, Not Authenticated—Acquirer exemption, or
Authenticated—recurring/split shipment.

Enhancements
SPA1 Value SPA2 Value Indicates
j kA, kB ACS processed
j kC, kD ACS Stand-In processed
h kE, kF Attempts processing
h kN Not Authenticated—Acquirer
exemption
j kO Authenticated—recurring/split
shipment
j kP Authenticated—recurring/split
shipment
NOTE: Values h and j will continue to be used until all activity is transitioned from the existing
SPA1 algorithm.
The following table provides information on the use cases and types of processing performed
based upon the associated AAV control byte and SLI.
EMV 3-D Secure Use Case/AAV/SLI Summary Table

Enhancements
Type of
EMV 3-D Secure Processing DE 48, SE 43 AAV
Version Use Case Performed Control Bytes DE 48, SE 42 SLI
EMV 3-D Secure Transaction ACS processed kA 212

2.0 successfully
authenticated by
SPA2 value
the ACS without
(SHA 256) challenging the
cardholder
Transaction ACS processed kB 212

successfully
authenticated by
the ACS after
challenging the
cardholder
Transaction ACS Stand-in kC 212

successfully processed
authenticated by
Mastercard based
on risk based
assessment (RBA)
score
Future use only— ACS Stand-in kD 212

no current use processed
cases for Stand In
challenge
Transaction could Attempts kE 211

not be processing
authenticated by
either the ACS or
Mastercard RBA.
Future use only— Attempts kF 211

no current use processing
cases for Attempts
challenge

Enhancements
Type of
Transaction was Not kN 216

not authenticated Authenticated–
by ACS or Acquirer
Mastercard, based Exemption
on Acquirer
exemption from
strong customer
authentication
(SCA) under PSD2
Recurring Authenticated– kO 217

transaction and Frictionless
was successfully recurring payment/
authenticated by split shipment
either the ACS or
Mastercard RBA
Recurring Authenticated– kP 217

transaction is the challenge–First
first in a series and recurring payment
was successfully transaction
authenticated by
the ACS using SCA

Enhancements
Type of
EMV 3-D Secure Transaction ACS processed kG 212

2.0 successfully
authenticated by
SPA2 value
the ACS without
(SHA 1) challenging the
cardholder
Transaction ACS processed kH 212

successfully
authenticated by
the ACS after
challenging the
cardholder
Transaction ACS Stand-in kJ 212

successfully processed
authenticated by
Mastercard based
on RBA score
Future use only–no ACS Stand-in kK 212

current use cases processed
for Stand In
challenge
Transaction could Attempts kL 211

not be processing
authenticated by
either the ACS or
Mastercard RBA
Future use only–no Attempts kM 211

current use cases processing
for Attempts
challenge
EMV 3-D Secure Transaction ACS processed j 212

1.0.2 successfully
ACS Stand-in
authenticated by
SPA1 value processed
the ACS
Transaction could Attempts h 211

not be processing
authenticated

Enhancements
Security Level Indicator Validation or Modification

The following table provides the criteria for which the SLI value in DE 48, subelement 42,
subfield 1, position 1–3 will be validated or modified when not appropriate for Authorization
Request/0100 or Financial Transaction Request/0200 messages.
When... Then... If this condition is not met...
The Authorization Request/0100 DE 48, SE 43 must be present The SLI value will be
or Financial Transaction Request/ and contain valid Mastercard downgraded (modified) to 210
0200 message contains a DE 48, Identity Check/SecureCode AAV
SE 42 value indicating the data
transaction was processed via
Mastercard Identity Check/
SecureCode
The Authorization Request/0100 The AAV control bytes in the The SLI value will be
or Financial Transaction Request/ leading positions of DE 48, SE downgraded (modified) to 210
0200 message contains DE 48, 43 must contain h, kE, kF, kL or
SE 42, value 211 kM
0200 message contains DE 48, 43 must contain j, kA, kB, kC,
SE 42, value 212 kD, kG, kH, kJ, or kK
0200 message contains DE 48, 43 must contain j, kA, kB, kC,
SE 42, value 215 kD, kG, kH, kJ, or kK
0200 message contains DE 48, 43 must contain kN
SE 42, value 216
0200 message contains DE 48, 43 must contain kO or kP
SE 42, value 217
NOTE: Mastercard will modify the SLI value in Mastercard Digital Enablement Service (MDES)
transactions based on the AAV contained in DE 48, subelement 43. Therefore, acquirers and
issuers should expect to see Mastercard Identity Check/SecureCode SLI values in MDES
transactions.

Enhancements
Dual Message System (Clearing)—Acquirer, Issuer

Mastercard will modify a Dual Message System (Clearing) edit that will ensure the PDS 0052
(Electronic Commerce Security Level Indicator), subfield 3 (UCAF Collection Indicator), position
3 value in First Presentment/1240 messages matches the DE 48, subelement 42, subfield 1,
position 3 SLI value in the corresponding Authorization response message.
Acquirers will submit the SLI value received in Authorization Request Response/0110 messages
within First Presentment/1240 messages sent to the Clearing system. If the SLI in the First
Presentment/1240 message does not match the value previously provided back to the acquirer
in the Authorization Request Response/0110 message, then the clearing message will be
rejected by Mastercard using error message 2806 to indicate that the PDS 0052, subfield 3
value in the First Presentment/1240 message does not match the DE 48, subfield 42, subfield
1, position 3 SLI value from the corresponding Authorization response message.
As seen in the following tables, acquirers will have the option to resubmit First Presentment/
1240 messages with value 210 in PDS 0052.
Authorization
Message Type DE 48, SE 43 Value DE 48, SE 42,SF1 Description

Value
0100 kN 217
0110 kN 210 The platform

downgraded the
transaction to a non-
authenticated
transaction because DE
48, SE 43 leading
indicators must be
either a kO or kP when
DE 48, SE 42, SF1 is
value 217
Clearing
Message Type PDS 0052, SF 1, 2, 3 Value Description

Platform Impact
Clearing
1240 217 The platform rejects the

transaction based on the value in
PDS 0052, SF3 (which is 7) not
matching the value in DE 48, SE
42, SF1, position 3 of the
corresponding 0110 message
(which is 0)
Platform Impact
Dual Message
Message Flows
Message Layouts
IPM MPE
Interchange

and Associated MCCs
Edits √
Error Numbers √
Pricing/Fees
Reports
Bulk Files
Forms
Reporting

Authorization
Dual Message
SAFE

Manager

Table File
Authorization

DE 48—Additional Data—Private Use

DE 48 (Additional Data—Private Use) is reserved for private organizations to define data
unique to specific networks or specific programs and services. DE 48 provides other
supplemental data in a message when a specific ISO-designated data element is not available.
It is a free-format, variable-length data element that may be used for multiple purposes.
Subelement 43—3–D Secure for Mastercard SecureCode
DE 48, subelement 43 contains UCAF data and is described here for Mastercard
Implementation of 3–D Secure for Mastercard SecureCode.
Transaction specific. Position 1 of the Mastercard 3–D Secure SPA AAV is a control byte
indicating the Mastercard Identity Check/Mastercard SecureCode platform that created the
field contents.
SPA1 Value SPA2 Value
j kA, kB, kC, kD, kO, kP
h kE, kF, kN

Clearing
Clearing
Edits
announcement.
Modified Edit—PDS 0052 (Electronic Commerce Security Level Indicator), Subfield 3

(UCAF Collection Indicator)
The following existing edit will be modified to reject transactions if the value in DE 48
(Additional Data), subelement 42 (Electronic Commerce Indicators), subfield 3 (UCAF
Collection Indicator) of the corresponding authorization response does not match the value in
PDS 0052, subfield 3 (UCAF Collection Indicator).

2806 The Clearing Platform will ensure The Clearing Platform will
that PDS 0052 (Electronic recognize value 217 in addition to
Commerce Security Level values 211, 212, and 215 in PDS
Indicator), subfield 3 (UCAF 0052 (Electronic Commerce
Collection Indicator) matches the Security Level Indicator), subfield 3
value in DE 48 (Additional Data), (UCAF Collection Indicator) when
subelement 42 (Electronic performing the match to DE 48
Commerce Indicator), subfield 1 (Additional Data), subelement 42
(Electronic Commerce Security (Electronic Commerce Indicator),
Level Indicator and UCAF subfield 1 (Electronic Commerce
Collection Indicator), position 3 Security Level Indicator and UCAF
(UCAF Collection Indicator) of the Collection Indicator), position 3
corresponding authorization (UCAF Collection Indicator) of the
response. corresponding authorization
response.
This edit is performed in Central Site for the following messages:
• First Presentment Messages/1240
Collection Only and reversal messages are excluded from this edit. Additionally, this edit will not apply when
no corresponding authorization record is present.

Error Numbers
support this release item.
Edit
Error Performed
PDS 0052, s3 2806 <FLDNAME> UCAF COLLECTION INDICATOR INVALID, Central Site
MUST MATCH AUTHORIZATION RESPONSE.


DE 48—Additional Data
DE 48 (Additional Data) is reserved for use based on product type.
Subelement 43—3-D Secure for Mastercard SecureCode
Subelement 43 contains UCAF data and is described here for Mastercard Implementation of
3-D Secure for Mastercard® SecureCode™.
SPA1 Value SPA2 Value
j kA, kB, kC, kD, kO, kP

h kE, kF, kN


Question Answer
1. Are any new service result code values (DE 48, No. Mastercard will expand the transactional use
subelement 71, subfield 2) being added to cases supported by these services, but no new
either On-behalf services 05 or 06 as part of services result codes are required.
these enhancements?
2. Are any new Clearing Platform edits being SLI value 216 is not protected from fraud-related
created to prevent issuers from initiating a chargebacks. SLI 216 will be used in transactions
chargeback for any of the SLI values discussed when a PSD2 strong consumer authentication
in this announcement? (SCA) exemption has been granted. SLI values
215 and 217 are protected from fraud-related
chargebacks in the same way that SLI values 211
and 212 are protected. As part of the
enhancements, no new SLI-related chargebacks
edits are being created nor are any existing
chargeback edits being modified. However,
Mastercard will add SLI value 217 to existing First
Presentment edit 2806, in addition to 211, 212,
and 215, which are already accommodated by
the edit.
3. How are OBS 05 (Mastercard® SecureCode OBS 05 is a pre-validation service performed

AAV Verification Service) and OBS 06 before routing an authorization request to an
(Mastercard® SecureCode Dynamic AAV issuer when their host authorization system is
Verification in Stand-In Processing) signed into Mastercard. OBS 05 service results
transactions handled by Stand-In processing? are provided to the issuer in the request message
in DE 48, subelement 71. However, if a signed-in
issuer becomes unavailable and fails to respond
to an authorization request or responds late and
the issuer is enrolled in Mastercard’s Stand-In
processing service, the OBS 05 results will be
used in Stand-In processing. OBS 06 is a Stand-In
service that is used only when an issuer is not
signed into Mastercard. The service is performed
with the specific intention of using the result in
Stand-In processing.

Question Answer
4. Is the SLI always provided in an authorization Yes. In that case, the same SLI value provided by
response, even if it was correct in the request the acquirer in DE 48, subelement 42, subfield 1
and not changed by Mastercard? in the request message will be returned in the
same field in the response. On the other hand, if
the SLI value was corrected, the issuer and the
acquirer will both receive the corrected value in
DE 48, subelement 42, subfield 1. The acquirer
will also receive DE 48, subfield 2 containing the
original (incorrect) value and subfield 3 indicating
the nature of the issue in the response message.
5. How is the SLI value determined by the Using the EMV 3-D Secure protocol result
acquirer? information (that is, the SecureCode or Identity
Check authentication result information)
generated during a merchant’s authentication
request, the Mastercard SLI value must be
derived by the acquirer and included in DE 48,
subelement 41, subfield 1 of the Authorization
or Financial Request message. Subsequently, the
SLI value must also be included in the
corresponding clearing message (for Dual
Message System transactions) in PDS 0052. The
SLI value in the clearing message must always be
the value from DE 48, subelement 42, subfield 1
of the response message. This is important to
note in cases where the original SLI was deemed
inappropriate and modified before delivery to the
issuer and in the response back to the acquirer.
Mastercard compares the authorization and
clearing SLI value for each clearing message
containing PDS 0052. Match failures result in the
First Presentment clearing message being
rejected.

AN 2114—Introduction of Mastercard ATM Cash Pick-Up Identifier
Chapter 10 AN 2114—Introduction of Mastercard ATM

Cash Pick-Up Identifier
Mastercard is introducing a payment type identifier to uniquely identify ATM withdrawal
transactions initiated via the Mastercard ATM Cash Pick-Up service.
AN 2114—Introduction of Mastercard ATM Cash Pick-Up Identifier............................................ 143

Version History............................................................................................................................143
At-A-Glance................................................................................................................................143
Overview.................................................................................................................................... 144
Customer Impact........................................................................................................................ 146
Enhancements............................................................................................................................ 147
Platform Impact.......................................................................................................................... 148
Authorization..............................................................................................................................149
CIS Data Element Defintions...................................................................................................149
Transaction Investigator.......................................................................................................... 149
Clearing......................................................................................................................................149
PDS 0043—Program Registration ID.................................................................................. 149
IPM MPE................................................................................................................................ 150
Edits.......................................................................................................................................151


Mastercard is introducing a payment type identifier to uniquely identify ATM withdrawal
transactions initiated via the Mastercard ATM Cash Pick-Up service.
Version History

8 Jan 2019 Updated effective date to 12 April 2019. At-A-Glance
Removed the check from the Dual Message to Dual Message Customer Impact
transaction message flow entry.
The removal of this content is not marked by change bars.
Updated Enhancements to support the removal of the Enhancements

following:
• Acquirer-related content from the Dual Message System
(Authorization) and Dual Message System (Clearing)
sections.
• Financial Transaction Advice/0220 message and the
verbiage “Issuers are required to echo this subelement in
Financial Transaction Request Response/0210 messages”
from the Single Message System—Acquirers section.
• Retrieval Request/1644 message and chargeback and
adjustment verbiage from the Dual Message System
(Clearing)—Issuers section.
11 Dec 2018 Initial publication date
At-A-Glance


Overview
Brands: Mastercard®, Debit Mastercard®, Cirrus®

Release: 19.Q2
Region: All
Action Indicator:
Attention warranted (Program/service-related)—Acquirer
Registration required—Acquirer, Issuer
Overview

Mastercard is participating in a pilot program to offer the new Mastercard ATM Cash Pick-Up
service to customers. The service allows money to be sent to individual recipients who obtain
their funds from an ATM which has been upgraded with the ATM Cash Pick-Up software.
Recipients receive a code (for example, Short Message Service [SMS] text message) which they
enter into the ATM; therefore, they do not need a debit card or relationship with a bank to
receive funds.
The Mastercard ATM Cash Pick-Up service provides the following multiple use cases for
customers engaging in the service:
• Relief Fund Disbursement
• Emergency Cash Assistance
• Cash Rewards
• Person to Person Payments
• Small Insurance Claims
• Government Aid Payments/Social Benefits
• Compensation


Mastercard will provide customers with the ability to uniquely identify ATM withdrawal
transactions initiated via the Mastercard ATM Cash Pick-Up service using a new payment type
value P01 (ATM Cash Pick-Up Transaction) in DE 48 (Additional Data), subelement 77
(Funding/Payment Transaction Type Indicator) for the Dual Message System (Authorization)
and Single Message System and in PDS 0043 (Program Registration ID) for the Dual Message
System (Clearing).

To provide customers with the ability to uniquely identify ATM Cash Pick-Up transactions at an
enabled ATM using the standard withdrawal function, Mastercard will allow ATM acquirers to
provide specific ATM Cash Pick-Up identification information in Authorization, Clearing, and
Single Message System messages.
Reference Manuals
processing:
manuals.
Additional information on the Mastercard ATM Cash Pick-Up service is available on https://
www.mastercard.com/cashpickup.

Customer Impact
Customer Impact

Attention warranted (Program/service-related)—Mastercard strongly recommends that
acquirers participating in the Mastercard ATM Cash Pick-Up service be prepared to support the
enhancements as described in this announcement. Acquirers not participating in the
Mastercard ATM Cash Pick-Up service will not be impacted by this enhancement.
Program or service requirement—Issuers that receive and return messages through the Dual
Message System and participate in the Mastercard ATM Cash Pick-Up service must be
prepared to support the enhancements as described in this announcement. Issuers not
participating in the Mastercard ATM Cash Pick-Up service will not be impacted by this
enhancement.
Registration required—Acquirers and issuers must register to participate in the Mastercard
ATM Cash Pick-Up service. Acquirers and issuers must contact their Mastercard
Implementation Representative to participate.
Testing recommended—Mastercard recommends that acquirers and issuers that participate in
the Mastercard ATM Cash Pick-Up service perform testing.

Dual Message Dual Message
Message System:

Enhancements
• Single Message System—Financial Request/0200 and Financial Request Advice/0220

messages
Enhancements
Dual Message System (Authorization)—Issuers

Mastercard will introduce payment type value P01 (ATM Cash Pick-Up Transaction) in DE 48
(Additional Data—Private Use), subelement 77 (Funding/Payment Transaction Type Indicator)
to uniquely identify Mastercard ATM Cash Pick-Up transactions.
Issuers that participate in the Mastercard ATM Cash Pick-Up service must be prepared to
support payment type value P01 in DE 48, subelement 77 for Mastercard ATM Cash Pick-Up
transactions in the following message types:
• Authorization Request/0100
• Authorization Request Response/0110
• Reversal Request/0400
• Reversal Request Response/0410
Single Message System—Acquirers

Mastercard will introduce payment type value P01 (ATM Cash Pick-Up Transaction) in DE 48
(Additional Data), subelement 77 (Funding/Payment Transaction Type Indicator) to uniquely
identify Mastercard ATM Cash Pick-Up transactions.
Acquirers that participate in the Mastercard ATM Cash Pick-Up service must be prepared to
support payment type value P01 in DE 48, subelement 77 for Mastercard ATM Cash Pick-Up
transactions in the following message types:
• Financial Transaction Request/0200
• Acquirer Reversal Advice/0420—Acquirer Initiated
NOTE: For Funding/Payment Transactions, DE 48, sueblement 77 must be present in Financial

Dual Message System (Clearing)—Issuers

Mastercard will introduce payment type value P01 (ATM Cash Pick-Up Transaction) in PDS
0043 (Program Registration ID) to uniquely identify Mastercard ATM Cash Pick-Up
transactions.
Issuers that participate in the Mastercard ATM Cash Pick-Up service must be prepared to
support payment type value P01 in PDS 0043 in First Presentment/1240 messages.

Platform Impact
Platform Impact
Dual Message System
Single Message
Message Flows
Message Layouts
IPM MPE √
Interchange

and Associated MCCs
Edits √
Error Numbers
Pricing/Fees
Reports
Bulk Files
Forms
Reporting
SAFE

Manager

Table File

Authorization
Authorization
CIS Data Element Defintions


Subelement 77—Funding/Payment Transaction Type Indicator
DE 48, subelement 77 (Funding/Payment Transaction Type Indicator) indicates the type of
Funding/Payment Transaction taking place. NOTE: All MoneySend Funding and Payment
Transactions require the presence of this indicator.
Value
P01 = Mastercard ATM Cash Pick-Up Transaction
Mastercard will update the Authorization Transaction Investigator with new value P01
(Mastercard ATM Cash Pick-Up Transaction) in DE 48 (Additional Data), subelement 77
(Funding/Payment Transaction Type Indicator) to support this announcement.
Clearing

PDS 0043—Program Registration ID

PDS 0043 (Program Registration ID) monitors and tracks a participant’s activity in special
promotion programs (primarily U.S.-defined).
Values
PDS 0043 values are established and administered under the authority of brand-specific
program and service management and marketing personnel. Values are listed in the following
table.

Value Description
P01 Mastercard ATM Cash Pick-Up Transaction
IPM MPE
Mastercard will add PDS 0043 (Program Registration ID), new value P01 (Mastercard ATM
Cash Pick-Up Transaction) to IPM MPE Table IP3001T1 (Payment Transaction Type Codes) to
Mastercard will update the Clearing Transaction Investigator with new value P01 (Mastercard
ATM Cash Pick-Up Transaction) in PDS 0043 (Program Registration ID) to support this
announcement.


Subelement 77—Funding/Payment Transaction Type Indicator
DE 48, subelement 77 (Funding/Payment Transaction Type Indicator) indicates the type of
transaction taking place.
Value Description
P01 Mastercard ATM Cash Pick-Up Transaction

Edits
The Single Message System will perform the following system edits.
WHEN... THEN the Single Message System...
A Single Message System acquired point-of- Rejects the transaction

service (POS) transaction contains DE 48 Where:
(Additional Data), subelement 77 (Funding/
Payment Transaction Type Indicator), value P01 • DE 39 (Response Code) = 30 (Format error)
(Mastercard ATM Cash Pick-Up Transaction) • DE 44 (Additional Response Data) = 048077
(indicating the data element in error)

This frequently asked question is designed to provide a better understanding of this
announcement and may provide an answer to a common question.
Question Answer
1. Why is the Single Message Transaction Currently, DE 48, subelement 77 is not displayed
Manager section excluded from this within the user interface of the Single Message
announcement? Transaction Manager. Additional information
regarding DE 48, subelement 77 can be found in
applicable Single Message System reports.
2. Does this announcement affect Single Not at this time. Single Message System-
Message System-connected issuers? connected issuers will not be included in the
pilot.

AN 2115—Mastercard Clearing Optimizer Utility Upgrade
Chapter 11 AN 2115—Mastercard Clearing Optimizer

Utility Upgrade
Mastercard is upgrading Clearing Optimizer software to provide an additional service.
AN 2115—Mastercard Clearing Optimizer Utility Upgrade.......................................................... 153

Version History............................................................................................................................153
At-A-Glance................................................................................................................................153
Enhancements............................................................................................................................ 154


Mastercard is upgrading Clearing Optimizer software to provide an additional service.
Version History
NOTE: This announcement format is customized to provide the appropriate level of detail for
this enhancement and may not include all of the sections usually provided in a standard
release announcement.

Questions
At-A-Glance

Release: 19.Q2
Region: All
System: Clearing
Action Indicator:
Information only—Acquirers, Issuers
Effective Date: Dual Message System (Clearing): 12 April 2019

Enhancements
Enhancements
Mastercard will introduce a utility called “EBCDIC to ASCII” that will allow customers to
convert EBCDIC formatted Integrated Product Messages (IPM) files to ASCII formatted IPM
files in the Mastercard Clearing Optimizer software.
Currently, the Clearing Optimizer software offers an ASCII to EBCDIC format converter.
However, existing functionality (Clearing Optimizer WS+, Auto Edit, Clearing Optimizer
Mainframe) does not support converting EBCDIC formatted IPM files to ASCII formatted IPM
files in the Windows environment.
Customers that licensed Windows software (WS+ and Auto Edit) expressed interest in
additional functionality to convert back-end generated IPM files. The EBCDIC to ASCII utility
will be a value added feature, that will provide increased versatility for customers that use
Mastercard Clearing Optimizer software.
Mastercard will update the IPM Pre-edit and Utilities—Workstation Plus manual to reflect the
addition of the EBCDIC to ASCII utility. Mastercard will also update the compatibility of the
software with the Windows 10 operating system.

Question Answer
1. When a file is unblocked from Mastercard in The EBCDIC to ASCII utility allows a customer to
Workstation Plus, it is automatically converted convert internally stored EBCDIC files to ASCII,
to ASCII. How is the new converter utility allowing to seamlessly integrate their systems
useful? with the Clearing Optimizer Auto Edit and
Workstation Plus.

AN 2116—Introduction of Merchant Presented QR Interchange for Selected Countries in Europe Region
Chapter 12 AN 2116—Introduction of Merchant Presented

QR Interchange for Selected Countries in Europe Region
Mastercard is announcing the availability of IRD QR for Merchant Presented QR Payment and
Funding transactions in the Czech Republic, Kazakhstan, Romania, and Ukraine. Mastercard is also
introducing new IRD QS for Merchant Presented QR Payment in these same countries. The use of
IRD QR and QS in these countries is based on the Wallet Funding model.
AN 2116—Introduction of Merchant Presented QR Interchange for Selected Countries in

Europe Region............................................................................................................................ 156
Version History............................................................................................................................156
At-A-Glance................................................................................................................................157
Overview.................................................................................................................................... 157
Customer Impact........................................................................................................................ 160
Enhancements............................................................................................................................ 161
Platform Impact.......................................................................................................................... 161
Clearing......................................................................................................................................163
Interchange Programs.............................................................................................................163
IRD QR—Merchant Presented QR Payment (Europe Intracountry)....................................... 163
IRD QR—Merchant Presented QR Funding (Europe Intracountry)........................................ 165
IRD QS—Merchant Presented QR Payment (Europe Intracountry)....................................... 167
Interchange Rates.............................................................................................................. 168
Edits.......................................................................................................................................168
New Edit—PDS 0004 (Funding Account Information), Subfield 2 (Sender Account
Number)............................................................................................................................ 168
Modified Edit—DE 26 (Card Acceptor Business Code [MCC])............................................. 169
Modified Edit—PDS 0004 (Funding Account Information), Subfield 1 (Funding Source)...... 169
Modified Edit—PDS 0004 (Funding Account Information), Subfield 2 (Sender Account
Number)............................................................................................................................ 170
Number)............................................................................................................................ 170
Modified Edit—PDS 0043 (Program Registration ID)........................................................... 170
Error Numbers................................................................................................................... 171

AN 2116—Introduction of Merchant Presented QR Interchange for

Selected Countries in Europe Region
Mastercard is announcing the availability of IRD QR for Merchant Presented QR Payment and
Funding transactions in the Czech Republic, Kazakhstan, Romania, and Ukraine. Mastercard is
also introducing new IRD QS for Merchant Presented QR Payment in these same countries.
The use of IRD QR and QS in these countries is based on the Wallet Funding model.
Version History

29 Jan 2019 Corrected the text of the Error Message for PDS 0043, Error Error Numbers
Number 2436.
11 Dec 2018 Clarified the modification to the listed Clearing Edits for IRD Modified Edit—DE
QS and processing code 28 to read as follows: 26 (Card Acceptor
Business Code
This edit will be modified to include IRD QS for processing
[MCC])
code 28.
Modified Edit—PDS
0004 (Funding
Account
Information),
Subfield 1 (Funding
Source)
Modified Edit—PDS
0004 (Funding
Account
Information),
Subfield 2 (Sender
Account Number)
Modified Edit—PDS
0004 (Funding
Account
Information),
Subfield 2 (Sender
Account Number)
Modified Edit—PDS
0043 (Program
Registration ID)

Questions

At-A-Glance

At-A-Glance

Products & Services: Merchant Presented QR
Release: 19.Q2
Region: Europe
System: Clearing
Action Indicator:
Attention warranted (Program/service-related)—Acquirers, Issuers
Registration required—Acquirers, Issuers
Overview
Background
Mastercard Merchant Presented QR (MPQR) is a push payment acceptance model. The
consumer initiates a cashless payment using a smartphone to scan a QR code at any merchant
that accepts Mastercard Merchant Presented QR transactions.
Summarizing the characteristics of a Merchant Presented QR Payment transaction:

Overview
• Processing Code is 28 (Payment Transaction)

• Payment Type is C67 (Merchant Presented QR)
• DE 2 (Primary Account Number) contains the merchant’s card
• Sent by the Originating Institution (OI)—the bank operating in the technical capacity of an
acquirer in the MPQR cycle
• Sent to the Receiving Institution (RI)—the bank holding the merchant’s account—the bank
associated with the merchant’s card in DE 2
Summarizing the characteristics of a Merchant Presented QR Funding transaction:
• Processing Code is 00 (Purchase [Good and Services]))
• Payment Type is C67 (Merchant Presented QR)
• DE 2 contains the consumer’s PAN
• Sent by the OI
• Sent to the consumer bank—the bank issuing the consumer PAN in DE 2 (Primary Account
Number)
Characteristics of Issuer Wallet and Open Wallet Funding models in Merchant Presented QR
Transactions:
• An Issuer Wallet Funding model operates via an On-Us funding transaction where the OI is
the same as the issuer
• An Open Wallet Funding model operates via an Off-Us funding transaction where the OI is
not the same as the issuer
Merchant Presented QR supports both Issuer Wallet and Open Wallet Funding models based
on roles performed by the issuer, OI , and RI in a particular MPQR cycle. The Issuer Wallet
Funding model is invoked when the OI is the issuer of the funding card. The Open Wallet
Funding model is invoked when the OI is not the issuer of the funding card.
In the Open Wallet Funding model:
• The OI should use IRD QS to submit Merchant Presented QR Payment
• The OI should use IRD QR to submit corresponding Merchant Presented QR Funding
transactions
In the Issuer Wallet Funding model
• The OI should use IRD QR to submit Merchant Presented QR Payment
• The OI should use IRD QR to submit corresponding Merchant Presented QR Funding
transactions

Bulletin announcement, “AN 1710—Introducing Intracountry Interchange for Masterpass QR
Payments in Ukraine,” published 16 April 2018, announced the availability of IRD QR
(Merchant Presented QR Payment [Europe Intracountry]) for payment transactions in Ukraine.
IRD QR (Merchant Presented QR Payment [Europe Intracountry]) has not been announced for
the Czech Republic, Kazakhstan, or Romania.

For the Issuer Wallet Funding model, IRD QR is used for both Merchant Presented QR Payment
and Funding transactions.
IRD QR (Merchant Presented QR Funding [Europe Intracountry]) is not available in the Europe
region.

Mastercard is announcing the availability of existing IRD QR (Merchant Presented QR Payment
[Europe Intracountry]) to the Europe region countries Czech Republic, Kazakhstan, and
Romania. Mastercard is introducing IRD QR (Merchant Presented QR Funding [Europe
Intracountry]) in Czech Republic, Kazakhstan, Romania, and Ukraine. Mastercard is also
introducing IRD QS (Merchant Presented QR Payment [Europe Intracountry]) in these same
countries to support rate differentiation for the Open Wallet Funding model.

The introduction of IRD QR will allow Merchant Presented QR Payment and Funding
transactions in specified countries of the Europe region.
The introduction of IRD QS will allow these specified countries in the Europe region to meet
business and regulatory needs with a second interchange rate based on a funding model for
Merchant Presented QR payment transactions.
Announcements
• “AN 1710—Introducing Intracountry Interchange for Masterpass QR Payments in Ukraine,”
16 April 2018
• “AN 1618—Introduction of Merchant Presented QR Funding Transactions and
Enhancements to Merchant Presented QR Payments,” Release 18.Q4
• “AN 1025—Introduction of Masterpass QR,” Release 17.Q4
Reference Manuals
Refer to these manuals for information about the current state of Mastercard processing:
• Domestic Rules—Europe
• Interchange and Service Fees Manual—Europe Region
• Mastercard Merchant Presented QR Program Guide

Customer Impact
manuals.
Customer Impact

Attention warranted (Program/service-related)—Issuers, OIs, and RIs in the Europe region
countries Czech Republic, Kazakhstan, Romania, and Ukraine must support:
• Sending and receiving IRD QR—Merchant Presented QR Payment (Europe Intracountry)
• Sending and receiving IRD QR—Merchant Presented QR Funding (Europe Intracountry)
• Sending and receiving IRD QS—Merchant Presented QR Payment (Europe Intracountry)
• New and modified Clearing Edits
OIs not implementing the enhancements in this release announcement will not be able to
qualify Merchant Presented QR payment transaction and corresponding funding transactions
for the specific QR rates defined for Issuer Wallet Funding model and the Open Wallet
Funding model.
Registration required—OIs, and RIs in the specified Europe region countries must register to
participate in Merchant Presented QR through their Mastercard representative.
Testing recommended—Mastercard recommends Issuers, OIs, and RIs perform testing.


Enhancements
Message System:
Enhancements
Dual Message System (Clearing)—Issuers, OIs, RIs

The following interchange programs will be available for the Europe region countries Czech
Republic, Kazakhstan, Romania, and Ukraine to process Merchant Presented QR Payment and
Funding transactions:
• IRD QR—Merchant Presented QR Payment (Europe Intracountry)
• IRD QR—Merchant Presented QR Funding (Europe Intracountry)
• IRD QS—Merchant Presented QR Payment (Europe Intracountry)
IRD QR and IRD QS are only available for Europe intracountry transactions acquired on the
Dual Message System on accounts for issuers connected to the Dual Message System.
A new Clearing Edit will be introduced for PDS 0004 (Funding Account Information), subfield
2 (Sender Account Number)
Clearing Edits for PDS 0004 and PDS 0043 (Program Registration ID) will be modified to
include new IRD QS.
Platform Impact
Dual Message System
Single Message
Message Flows
Message Layouts
Data Element Definitions
IPM MPE

Platform Impact
Dual Message System
Single Message
Interchange √

and Associated MCCs
Edits √
Error Numbers √
Pricing/Fees
Reports
Bulk Files
Forms
Reporting
SAFE

Manager

Table File

Clearing
Clearing
Mastercard will introduce modifications to interchange programs to support this
announcement.
IRD QR—Merchant Presented QR Payment (Europe Intracountry)

This interchange rate designator (IRD) is not part of the standard intra-European interchange
tier structure. It is available for designated Europe region countries for intracountry
transactions. Transactions must meet IPM requirements to qualify for this IRD.
Business Requirements Technical Requirements

Valid for Mastercard and PDS 0158 (Business Activity), subfield 1 (Card Program Identifier):
Debit Mastercard cards.
MCC, DMC, MSI
PDS 0002 (GCMS Product Identifier):

Mastercard Consumer—MCC, MCE, MCG, MCS, MCW, MIU, MNW, MPL,
MRC, MRF, MRG, MRJ, MRO, MTP, MWE, MWF, SAG, SAP, SAS, SOS, SUR,
TCC, TCE, TCG, TCS, TCW, TNW, TPL, TWB, WBE
Debit Mastercard Consumer—ACS, DAG, DAP, DAS, DLG, DLH, DLP, DLS,
DOS, DWF, MBW, MDG, MDH, MDP, MDS, MDW, MPG, MPJ, MPP
Mastercard Commercial—MAP, MBE, MBS, MCB, MCF, MCO, MCP, MEB,
MEC, MEO, MLA, MNF, MPB, MRK, MRL, MRW, TBE, TCB, TCF, TCO, TCP, TEB,
TEC, TEO, TNF
Debit Mastercard Commercial—BPD, MBP, MDT
Maestro—MOC, MOG, MOP, MSA, MSB, MSF, MSG, MSI, MSJ, MSM, MSN,
MSO, MSQ, MSR, MST, MSV, MSW, MSX, MSY, MSZ, OLG, OLP, OLS, SAL
Valid for point-of-sale (POS) Message Type Identifier + DE 24 (Function Code):

transactions
• First Presentments/1240
DE 3 (Processing Code), subfield 1 (Cardholder Transaction Type):

• 28—Payment Transaction

Clearing

Card Acceptor Business CAB Program, derived from DE 26 (Card Acceptor Business Code
(CAB) Program and Card [MCC]):
Acceptor Business Code
• A001—Airline
(MCC) criteria. The MCC
cannot be a Payment • B001—Cruise/Steamship
Transaction MCC. • F001—Restaurant
• H001—Lodging
• M001—Mail Order/Telephone Order
• OTH1—Other
• P001—Beauty Salons
• R001—Railways
• S001—Supermarket
• T001—Telephone
• U001—Unique
• V001—Automobile/Vehicle Rental
• W001—Warehouse Club
Timeliness None
Transaction must be online DE 38 (Approval Code):
authorized
Required
Acquirers must be able to The acquirer must be registered as a certified “Merchant UCAF” acquirer.
receive UCAF data from
their merchants and to This requirement is not applicable to Digital Secure Remote Payment.
forward them to issuers, in
authorization messages
Notes PDS 0043 (Program Registration ID) is required and must contain value C67
(Merchant Presented QR).
PDS 0004 (Funding Account Information) is required for all Merchant
Presented QR payment transactions.
IRD QR is used by an Originating Institution (OI) on the Merchant Presented
QR payment transaction if the corresponding funding transaction was
performed on-us regardless of the processing entity for the funding
transaction.
IRD QR will support Issuer Wallet Funding model for Payment transactions.

Clearing
IRD QR—Merchant Presented QR Funding (Europe Intracountry)


MCC, DMC, MSI

TEC, TEO, TNF

transactions
• First and Second Presentments/1240

• 00—Purchase (Goods and Services)

Clearing

• A001—Airline
• H001—Lodging
• OTH1—Other
• R001—Railways
• U001—Unique
Timeliness None
authorized
Required
IRD QR will support Issuer Wallet and Open Wallet Funding models for both
Payment and Funding transactions.

Clearing
IRD QS—Merchant Presented QR Payment (Europe Intracountry)


MCC, DMC, MSI

TEC, TEO, TNF

transactions
• First Presentments/1240

• 28—Payment Transactions
• A001—Airline
• H001—Lodging
• OTH1—Other
• R001—Railways
• U001—Unique

Clearing

Timeliness None
authorized
Required
PDS 0004 (Funding Account Information) is required for all Merchant
Presented QR payment transactions.
IRD QS is used by an Originating Institution (OI) on the Merchant Presented QR
Payment transaction if the corresponding funding transaction was performed
off-us regardless of the processing entity for the funding transaction.
IRD QS is used to support Merchant Presented QR Payments transactions with
the Open Wallet Funding model when the OI is not the issuer of the funding
card.
Interchange Rates
Mastercard will provide information on rates for Merchant Presented QR transactions for the
Europe region countries Czech Republic, Kazakhstan, and Romania in future interchange
bulletin announcements.
Edits
announcement.
New Edit—PDS 0004 (Funding Account Information), Subfield 2 (Sender Account

Number)
For a Merchant Presented QR transaction in the Europe region that is associated with IRD QR
or with IRD QS, this edit will validate the interchange rate is found for the Brand associated
with the Funding PAN in PDS 0004, subfield 2 (Sender Account Number).
Error Number Requirement

2890 The Clearing Platform requires that interchange rates exists for
Mastercard Merchant Presented QR Europe Intracountry transactions
(Region D to Region D) when the Funding PAN contained in PDS 0004
(Funding Account Information), subfield 2 (Sender Account Number) is
associated with Card Program Identifier (DMC, MCC, or MSI), PDS
0043 (Program Registration ID) contains value C67 (Merchant
Presented QR) or C68 (Merchant Presented QR Refund), and PDS 0158
(Business Activity), subfield 4 (Interchange Rate Designator) contains QR
or QS.

Clearing

This edit is performed in Clearing Optimizer and at the Central Site for the following messages:
• First Presentment/1240
Modified Edit—DE 26 (Card Acceptor Business Code [MCC])

The following existing edit currently includes IRD QR and applies to processing code 00
(Purchase [Goods and Services]) . It will be modified to include IRD QS for processing code 28
(Payment) and to apply to additional message types for processing code 00.

161 The Clearing Platform must ensure that if PDS This edit will be modified to include
0043 (Program Registration ID) is present and IRD QS for processing code 28.
contains value C67 (Merchant Presented QR)
or C68 (Merchant Presented QR Refund), then When processing code is 00, this edit
DE 26 (Card Acceptor Business Code [MCC]) will be applied to the following
cannot contain MCCs 4829, 6010, 6011, additional message types:
6050, 6051, 6532, 6533, 6538, 6540, or • First Chargeback/1442
6555. • Arbitration Chargeback/1442
• Second Presentment/1240
• First Presentment/1240 Messages
Modified Edit—PDS 0004 (Funding Account Information), Subfield 1 (Funding Source)

The following existing edit currently includes IRD QR. It will be modified to include IRD QS
(Merchant Presented QR Payment [Europe Intracountry]) for processing code 28 (Payment).

2838 The Clearing Platform must ensure PDS 0004, This edit will be modified to include
subfield 1 (Funding Source) is present and IRD QS for processing code 28.
contains valid value 01, 02, 03, 04, 05, 06, or
07 for Merchant Presented QR interchange.

Clearing

Number)
The following existing edit currently includes IRD QR. It will be modified to include IRD QS
(Merchant Presented QR Payment [Europe Intracountry]) for processing code 28 (Payment).

2837 The Clearing Platform must ensure This edit will be modified to include IRD QS
the value in PDS 0004, subfield 2 for processing code 28.
(Sender Account Number) has a
minimum length of 1 position and
a maximum length of 20 positions.

Number)
The following currently includes IRD QR. It will be modified to include IRD QS—(Merchant
Presented QR Payment [Europe Intracountry]) for processing code 28 (Payment).

2839 The Clearing Platform must This edit will be modified to include IRD QS for
ensure PDS 0004, subfield 2 processing code 28.
(Sender Account Number) is
present and numeric contains a
non-zero numeric value for
Merchant Presented QR
interchange.
Modified Edit—PDS 0043 (Program Registration ID)

The following existing edit currently includes IRD QR and currently applies to First
Presentment/1240 messages. It will be modified to include IRD QS—(Merchant Presented QR

Clearing
Payment [Europe Intracountry]) for processing code 28 (Payment) and to apply to additional
message types.

2436 The Clearing Platform must ensure that PDS This edit will be modified to include
0043 (Program Registration ID) is present and IRD QS for processing code 28.
contains value C67 (Merchant Presented QR).
When processing code is 00, this edit
will be applied to the following
message types:
• First Presentment/1240 Messages
Error Numbers
Error Numbers in New Edits
Edit
Error Performed
PDS 0004, s2 2890 Interchange rate not found for MPQR Sender Account Both
Number (PDS 0004 subfield 2) Card Program Identifier.
Edit
Error Performed
DE 26 161 DE26 Invalid. Both
PDS 0004, s1 2838 PDS0004,S1 must be present and equal to <VALLIST>. Both

Edit
Error Performed
PDS 0004, s2 2837 PDS0004,S2 length must be 01–20. Both
PDS 0004, s2 2839 PDS0004,S2 must be present and numeric and cannot Both
contain all zeros.
PDS 0043 2436 Program Registration ID value invalid for the interchange Both
program.

Question Answer
1. How is a merchant identified in a Merchant There are a number of ways the merchant is
Presented QR transaction? identified.
A QR code is assigned to a participating
merchant. This QR code is linked to a card that is
included in the transaction (DE 2), along with the
typical indicators (Card Acceptor Location and ID
Code, DE 42 and DE 43).
The merchant displays their QR code at their
establishment. The customer will scan the code,
and that code is tied to the merchant for the
merchant to receive funds.
A full process flow can be viewed in the
Mastercard Merchant Presented QR Program
Guide.
2. When registering as an issuer for Merchant Registering for Merchant Presented QR must be
Presented QR must we support both open performed to support the service. The types of
and closed wallet funding sources? funding that the originator supports can be open
and closed wallet. Mastercard can support
indication of both types of funding during
testing and production operations.
It is not mandatory for an issuer to support both
open and closed wallet funding sources.
3. What guide provides information on the Information can be found in the Mastercard
transaction data needed to support Merchant Merchant Presented QR Program Guide.
Presented QR?

Question Answer
4. Does AN 2116 apply to domestic transactions With Release 19Q2, Merchant Presented QR will
only, or is cross-border supported? only be offered domestically, and only for the
four countries included in this announcement
(Czech Republic, Kazakhstan, Romania and
Ukraine).
5. If a consumer attempts to initiate an MPQR MPQR implementations can be facilitated
Payment transaction to a merchant via their through Open Wallet (a card issued by any
phone, would Mastercard prevent the Mastercard issuer can be loaded into the wallet)
payment to the merchant if the consumer’s and an Issuer Wallet (cards issued by the issuer of
financial institution does not participate? the wallet must only be loaded into the wallet)
programs. In both cases the financial institutions
operating the wallet that initiates the MPQR
payments must be registered for the service.
Mastercard would prevent the MPQR
transactions being processed on MC network if
the origination financial institution is not
registered for the service.
6. If a consumer attempts to initiate an MPQR If the financial institution does not participate in
Payment transaction to a merchant via their MPQR program, Mastercard would prevent the
phone, would Mastercard prevent the payment transaction as the receiver must be
payment to the merchant if the Merchant’s registered for the service.
financial institution does not participate?
7. How is the value determined for the Card PDS 0158, subfield 1 will continue to contain the
Program Identifier contained in PDS 0158 Card Program Identifier associated with DE 2
(Business Activity), subfield 1 (Card Program (Primary Account Number [PAN]).
Identifier) which is used to identify the card
program or financial network, for a
transaction?

AN 2117—Introducing Cryptographic Key Block Changes to Support Phase 2 of PCI Mandates
Chapter 13 AN 2117—Introducing Cryptographic Key

Block Changes to Support Phase 2 of PCI Mandates
Mastercard is introducing changes to key exchange information to support recent Payment Card
Industry (PCI) mandates.
AN 2117—Introducing Cryptographic Key Block Changes to Support Phase 2 of PCI Mandates.. 175
Version History............................................................................................................................175
At-A-Glance................................................................................................................................176
Overview.................................................................................................................................... 176
Customer Impact........................................................................................................................ 178
Enhancements............................................................................................................................ 178
Implementation Scenarios...................................................................................................... 179
Platform Impact.......................................................................................................................... 181
Authorization..............................................................................................................................182
DE 70—Network Management Information Code..............................................................182
DE 110—Additional Data–2...............................................................................................183
DE 70—Network Management Information Code..............................................................186
DE 110—Additional Data–2...............................................................................................187

AN 2117—Introducing Cryptographic Key Block Changes to Support

Phase 2 of PCI Mandates
Mastercard is introducing changes to key exchange information to support recent Payment
Card Industry (PCI) mandates.
Version History

8 Jan 2019 Changed the Effective Dates for both the Dual Message At-A-Glance
System (Authorization) and the Single Message System from
12 April 2019 to 11 June 2019. 11 June 2019 is the date
customers will be able to begin testing.
In addition, added a note after the revised effective dates
clarifying the difference between the network functionality
availability date and the PCI mandate final date.
Removed Attention Warranted from the “Is Customer Action Customer Impact
Required?” section prior to Network Mandate.
Clarified the starting and ending dates of when customers
can contact their Customer Implementation Support
representatives that they are prepared to receive the new PCI
PIN encryption key exchange information.
Added a note following the Testing required statement.
Clarified the starting date in Scenarios 2 and 3 to 11 June Implementation

2019, and in question 2 of Frequently Asked Questions. Scenarios
Clarified the starting date in question #2 of Frequently Frequently Asked
Asked Questions. Questions
11 Dec 2018 Added clarification and a note to the first two bullets of the Related
Reference Materials section. Documentation
Questions

At-A-Glance
At-A-Glance

Brands: Mastercard®, Debit Mastercard®, Maestro®, Cirrus®, Visa®, Mastercard
Electronic™, U.K. Domestic Maestro, Plus®, Pulse®, NYCE®, STAR®, Interlink®
Release: 19.Q2
Region: All
System: Authorization, Single Message System
Action Indicator:
Network Mandate—Acquirer, Issuer
Testing required—Acquirer, Issuer
NOTE: 11 June 2019 is the first point at which the Mastercard

network will support the use of the new TR-31 key block format in
the production environment. Customers will have from that date
until June 2021 to complete their migration to the new format,
following coordination and testing with the Mastercard Customer
Implementation Services team.
Overview
This overview provides information about the current environment and any applicable
The Payment Card Industry (PCI) Council mandated enforcement of new requirements
pertaining to the storing of keys for later retrieval, for example, key cryptograms. The new
restrictions stipulate customers must begin using structures called key blocks, which are
immune to specific types of attacks and also restrict further key usage, in order to enhance
security. The mandate stipulates customers must be fully compliant by June 2021.

Background
PCI PIN Security Requirements v2.0, published December 2014, introduced a new requirement
to increase security for encrypted keys. Implementation of key blocks—sometimes referred to
as “key bundling”—greatly improves the security of symmetric keys that are shared among
payment participants to protect PINs and other sensitive data.

Mastercard currently sends dynamic key exchange information to customers in DE 48
(Additional Data), subelement 11 (Key Exchange Data Block).

Mastercard is announcing changes to support the PCI mandate involving key exchange
information storage using key blocks. In Release 19.Q2, Mastercard is introducing new values
for DE 70 (Network Management Information Code) to allow customers to exchange keys for
the new key block structure. In addition, Mastercard will begin using DE 110 (Additional Data
-2) and two new subelements, 9 (ANSI X9 TR-31 Key Block Key) and 10 (Key Check Value) for
customers to receive the new key block format information.

These enhancements will assist customers to be compliant with the PCI Council mandate by
June 2021.
Reference Materials
processing:
• X9 TR-31 Interoperable Secure Key Exchange Key Block Specification for Symmetric
Algorithms, an industry standard, available from the ANSI Webstore
• Cryptographic Key Blocks, June 2017, an industry standard, available from the PCI Security
Standards Council
NOTE: The documents listed in the bullet list above are not Mastercard documents and are
not contained on the Mastercard Technical Resource Center. They are available from the
industry standards organizations mentioned.


Customer Impact
manuals.
Customer Impact

Network Mandate—Acquirers and issuers must support the new subelements and values in
the Network Management Request/0800—PEK Exchange, Network Management Response/
0810—PEK Exchange and Network Management Advice/0820 messages by June 2021.
Starting 11 June 2019 and until June 2021, customers must contact their Customer
Implementation Support representative when they are prepared to receive the new PCI PIN
encryption key exchange information in DE 110, subelements 9 and 10 before they can
submit a Network Management Request/0800—PEK Exchange in DE 70 containing a value
163 (Solicitation for Encryption Key Exchange - TR-31 Keyblock).
NOTE: Customers can continue receiving DE 48, subelement 11 (Key Exchange Data Block)
until June 2021. Beginning in June 2021, only DE 110, subelements 9 and 10 will be used for
PIN encryption key exchange processing.
Testing required—Mastercard requires that acquirers and issuers perform testing to support
the enhancements in this announcement.
NOTE: Once customers have successfully completed testing, they can implement in production
by contacting their Customer Implementation Support representative and requesting to
receive the TR-31 keyblock, or customers may send the Network Management Request/0800
message with DE 70 with value 163 to initiate the TR-31 keyblock exchange.

This announcement does not impact any transaction message flows.
Enhancements
Dual Message System (Authorization)—Acquirer, Issuer

Mastercard will make the following changes to support this mandate:

Enhancements
• DE 70 (Network Management Information Code)

– Add new value 163 (Solicitation for Encryption Key Exchange - TR-31 Keyblock) to the
Network Management Request/0800—PEK Exchange and the Network Management
Request Response/0810—PEK Exchange messages. Customers will use this value to
indicate they are prepared to receive the PCI Key Exchange information.
– Add new value 164 (Encryption Key Exchange Confirmation of Success) to the Network
Management Advice/0820—PEK Exchange message for confirmation of a successful
Key Exchange completion.
– Add new value 165 (Encryption Key Exchange Advice of Failure) to the Network
Management Advice/0820—PEK Exchange message for notification of a failed key
exchange attempt.
• Add and define DE 110 (Additional Data—2) which is currently reserved for ISO use,
with the following:
– Add subelement 9 (ANSI X9 TR-31 Key Block Key)
– Add subelement 10 (Key Check Value)
Single Message System—Acquirer, Issuer

Mastercard will make the following changes to support this mandate:
• DE 70 (Network Management Information Code)
– Add new value 163 (Solicitation for Encryption Key Exchange - TR-31 Keyblock) to the
Network Management Request/0800—PEK Exchange message and the Network
Management Request Response/0810—PEK Exchange messages. Issuers will use this
value to indicate they are prepared to receive the PCI Key Exchange information.
– Add new value 164 (Encryption Key Exchange Confirmation of Success) to the Network
Management Advice/0820—PEK Exchange message for confirmation of a successful
Key Exchange completion.
– Add new value 165 (Encryption Key Exchange Advice of Failure) to the Network
Management Advice/0820—PEK Exchange message for notification of a failed key
exchange attempt.
• Existing DE 110 (Additional Data—2)
– Expand DE 110 to the ISO Standard: ans...999; LLLVAR
– Add subelement 9 (ANSI X9 TR-31 Key Block Key)
– Add subelement 10 (Key Check Value)
Implementation Scenarios
The following scenarios describe the different time frames and criteria to implement the PCI
key exchange information mandate.
Implementation Scenarios
Three scenarios will be supported for this PCI mandate.
Scenario 1: Prior to Release 19.Q2:

Enhancements
• A customer can initiate the PIN encryption key exchange sequence by sending a Network
Management Request/0800 message where DE 70 (Network Management Information
Code) contains the value 162 (Solicitation for Encryption Key Exchange).
• Mastercard responds with a Network Management response/0810 message.
• Mastercard originates a Network Management Request/0800 message to initiate a PIN
encryption key (sometimes referred to as the “working key”) change with the customer.
The message contains the following data:
– DE 70 contains value 161 (Encryption Key Exchange)
– DE 48, subelement 11 (Key Exchange Data Block) contains the Key Exchange Data Block
• The customer responds with a Network Management Request Response/0810 message,
which contains the following data:
– DE 39 contains value 00 if the response is an approval (if there is a problem then DE 39
contains value 96 indicating a denial)
– DE 48 subelement 11 may be returned at customer’s discretion,
• Mastercard completes the sequence by sending a Network Management Advice/0820
message to the customer, indicating confirmation of the PIN encryption key change. This
message contains the following data:
– DE 70 contains value 161 (Encryption Key Exchange )
– DE 48 subelement 11 contains the first characters of the original subelement 11 up to
the beginning of the actual key.
NOTE: If the Network Management Request Response/0810 message indicated a denial, then
the Network Management Advice/0820 message will not contain DE 48 and DE 70.
Scenario 2: After 11 June 2019, but prior to June 2021:

• When the customer wants to initiate the PIN encryption key exchange sequence for the
new PCI Key Block Structure Exchange Information, the customer sends a Network
Management Request/0800 message where DE 70 (Network Management Information
Code) contains value 163 (Solicitation for Encryption Key Exchange - TR-31 Keyblock).
• Mastercard responds with a Network Management Response/0810 message.
• Mastercard originates a Network Management Request/0800 message to initiate the PIN
encryption key (this is sometimes referred to as the “working key”). The message contains
the following data:
– DE 110, subelement 9 (ANSI X9 TR-31 Key Block Key)
– DE 110, subelement 10 (Key Check Value)
• The customer responds with a Network Management Request Response/0810 message,
which contains the following data:
– DE 39 contains value 00 if the response is an approval (if there is a problem then DE 39
contains 96 indicating a denial).

Platform Impact
– DE 110, subelement 10 may be returned at the customer’s discretion

• Mastercard completes the sequence by sending a Network Management Advice/0820
message to the customer, indicating confirmation of the working key change. This message
contains the following data:
– DE 70 contains value 164 (Encryption Key Exchange Confirmation of Success) or value
165 (Encryption Key Exchange Advice of Failure)
– DE 110 subelement 10 (Key Check Value)
NOTE: Customers should begin using the new keys after they receive the Network
Management Advice/0820 message. However, if the Network Management Advice/0820
message contains DE 70 value 165 (Encryption Key Exchange Advice of Failure), the customer
must continue to use the current key.
Scenario 3: After 11 June 2019 and prior to June 2021 the customer can revert back to
receiving the key exchange information through DE 48, subelement 11 by sending a Network
Management Request/0800 where DE 70 (Network Management Information Code) contains
the value 162 (Solicitation for Encryption Key Exchange).
Refer to Scenario 1 for details on processing for scenario 3.
Platform Impact
Dual Message System
Single Message
Message Flows
Message Layouts
IPM MPE
Interchange

and Associated MCCs
Edits
Error Numbers

Authorization
Dual Message System
Single Message
Pricing/Fees
Reports
Bulk Files
Forms
Reporting
SAFE

Manager

Table File
Authorization

DE 70—Network Management Information Code

DE 70 (Network Management Information Code) identifies network status.
Network Management Request/0800—PEK Exchange and Network Management
Request
The following values apply to this message.
Code Financial Network MC NP VI TE MS CI

163 = Solicitation for Encryption Key Exchange √ √ √ √ √ √
- TR-31 Keyblock

Authorization
Network Management Request Response/0810—PEK Exchange and Network

Management Request Response

163 = Solicitation for Encryption Key Exchange √ √ √ √ √ √
- TR-31 Keyblock
Network Management Advice/0820—PEK Exchange


164 = Encryption Key Exchange Confirmation √ √ √ √ √ √
of Success
165 = Encryption Key Exchange Advice of √ √ √ √ √ √
Failure
DE 110—Additional Data–2
Attributes
Data Representation: ISO Standard: ans...999; LLLVAR

Mastercard Standard: ans...999; LLLVAR
Length Field: 3 positions, value =...999
Data Field: Contents of subelements 9-10
Subelements: 2
Justification: See “Subelements”
Usage
Following is the usage of DE 110 (whether it is mandatory, conditional, optional, system provided, or
not required) in applicable messages.

Authorization
Message Org Sys Dst
Network Management Request/0800—PEK Exchange and Network • M M

Management Request
Network Management Request Response/0810—PEK Exchange and O M •

Network Management Response
Network Management Advice/0820—PEK Exchange • M M
Application Notes
DE 110 provides supplemental data in a message when a specific ISO-designated data
element is not available. It is a free-format, variable-length alphanumeric data element that
may be used for multiple purposes. This data element’s content may vary by program and
service.
The following tables provide formats and descriptions for the subelements in DE 110.
Currently, there are two subelements but as subelements are added, the subelement sequence
will not have to be in the order of ID value.
Subelement 9—ANSI X9 TR-31 Key Block Key (128-bit Key Block Protection Key)
DE 110, subelement 9 (ANSI X9 TR-31 Key Block Key [128-bit Key Block Protection Key])
contains the attributes provided in a Network Management Request/0800 message.
Attribute Value
Subelement ID n–2 09
Subelement Length n–3 080
Data Representation an–80
Usage
Following is the usage of subelement 09 (whether it is mandatory, conditional, optional, or system

provided) in applicable messages.
Message Org Sys Dst
Network Management Request/0800 —PEK • M M

Exchange
Network Management Request Response/0810— O C •

PEK Exchange

Authorization
Usage
Network Management Request Advice/0820— • • •

PEK Exchange
Attribute Value
Usage

Message Org Sys Dst
Network Management Request/0800—PEK • M M

Exchange

PEK Exchange

PEK Exchange
Subelement 10—Key Check Value

DE 110, subelement 10 (Key Check Value) contains the attributes in a Network Management
Request/0800 message.
Attribute Value

Usage

Message Org Sys Dst

Exchange

PEK Exchange
Network Management Request Advice/0820— • M M

PEK Exchange


DE 70—Network Management Information Code

The Single Message System uses DE 70 (Network Management Information Code) to identify
network status. The Customer Processing System (CPS) may use Additional Data (DE 48) in
conjunction with DE 70 to provide network status or control information.
Usage
This data element indicates the specific classification and purpose of network management
(08xx) messages. It must be present in all network management (08xx) messages.
Following is the usage of DE 70 (whether it is mandatory, conditional, optional, system
provided, or not required) in applicable messages.
Message Org Sys Dst
Network Management Request/0800—PEK Exchange and Network M X •

Management Request
Network Management Request Response/0810—PEK Exchange and M X •


Message Org Sys Dst
Network Management Advice/0820—PEK Exchange • X C
Values
This table lists all Network Management Information Codes valid on the Single Message
System.
Network Management Information Codes
Code Description
163 Solicitation for Encryption Key Exchange - TR-31 Keyblock
164 Encryption Key Exchange Confirmation of Success
165 Encryption Key Exchange Advice of Failure
DE 110—Additional Data–2
Attributes

Length Field: 3 positions, value =...999
Data Field: Contents of subelements 1-10
Subelements: 10
Justification: See “Subelements”
Usage
Following is the usage of DE 110 (whether it is mandatory, conditional, optional, system provided, or
not required) in applicable messages.

Message Org Sys Dst
Network Management Request/0800—PEK Exchange and Network C • M

Management Request
Network Management Request Response/0810—PEK Exchange and C M M

Network Management Advice/0820—PEK Exchange C • M
Application Notes
DE 110 provides supplemental data in a message when a specific ISO-designated data
element is not available. It is a free-format, variable-length alphanumeric data element that
may be used for multiple purposes. This data element’s content may vary by program and
service.
The following tables provide formats and descriptions for the subelements in DE 110. There
are ten subelements but as subelements are added, the subelement sequence will not have to
be in the order of ID value.
Attribute Value
Usage

Message Org Sys Dst

Exchange

PEK Exchange

Usage

PEK Exchange
NOTE: For additional information customers should refer to the X9 TR-31 Interoperable Secure
Key Exchange Key Block Specification for Symmetric Algorithms specifications.
Attribute Value
Usage

Message Org Sys Dst

Exchange

PEK Exchange

PEK Exchange
Subelement 10—Key Check Value

DE 110, subelement 10 (Key Check Value) contains the attributes in a Network Management
Request/0800 message.
Attribute Value

Attribute Value
Usage

Message Org Sys Dst

Exchange

PEK Exchange
Network Management Request Advice/0820— • M M

PEK Exchange

Question Answer
1. Does Mastercard currently have plans to No. There are no plans to remove support for
eliminate the use of static PIN keys? static PIN keys at this time.
2. During the period starting 11 June 2019 until No. Mastercard will not send both DE 48,
June 2021, can the Network Management subelement 11 and DE 110 to a customer. We
Request/0800 message that Mastercard sends will only send the one that corresponds to the
to a customer contain both DE 48, method requested by the customer. Note that
subelement 11 and DE 110? during the period starting 11 June 2019 until
June 2021, customers can move between either
method until they are comfortable with the new
ANSI X9 TR-31 Key Block structure format.

Question Answer
3. Mastercard supports both automated and Customers are not being mandated to change
solicited/on-demand PIN encryption key their mode of PIN encryption key exchange.
exchanges. If a customer is currently using the Customers that currently initiate the process on-
solicited/on-demand method can they demand by sending Mastercard a Network
continue to use that method beyond June Management Request/0800 message containing
2021 or does this enhancement require DE 70 = 162 (Solicitation for Encryption Key
customers to migrate to only the automated Exchange) can continue to use this method, but
method? will use DE 70 value 163 (Solicitation for
Encryption Key Exchange - TR-31 Key block),
when appropriate.
4. Will customers that do not use the Network No. Customers that do not use the 0800
Management Request/0800 message to message method are not being mandated to do
perform a PIN encryption key exchange so at this time. While it is common for customers
method become required to do so with this in Europe to use an alternate (non-0800 message
enhancement? method) to perform the PIN encryption key
change with Mastercard, those customers that
use the 0800 message method must meet the
requirements defined in this announcement.
5. Does Mastercard have a recommendation of The 128 bit TR-31 key block is a double-length
which key length (128-bit vs 192-bit) that a TDEA (Triple DES Encryption Algorithm) key. The
customer should use? 192 bit TR-31 key block is a triple-length TDEA
key. Triple length keys are more secure than
double length keys. But Mastercard currently
allows both double and triple length set-ups.
Currently, either is acceptable. Which one to use
is a business decision that each customer must
make on their own.
If a customer has multiple connections to
Mastercard they need to consider whether
double or triple length keys make sense for a
given interface based on the infrastructure
involved with each, and then implement their
TR-31 key block support accordingly.
Note that migration to the TR-31 key block
format does not require reestablishment of
communication keys. Therefore it is acceptable
for customers to utilize the TR-31 length
appropriate for the key length they currently
support today

Question Answer
6. Where can we find the two documents These are not Mastercard produced documents
identified in the first two bullets of the and are not contained on the Technical Resource
Reference Materials in the Related Center. They can be obtained from the following
Documentation section? industry standards organizations.
• X9 TR-31 Interoperable Secure Key Exchange
Key Block Specification for Symmetric
Algorithms, an industry standard, available
from the ANSI Webstore
• Cryptographic Key Blocks, June 2017, an
industry standard, available from the PCI
Security Standards Council

AN 2118—Account Level Management Universal Specification Enhancements
Chapter 14 AN 2118—Account Level Management

Universal Specification Enhancements
Mastercard is streamlining Account Level Management by enhancing the Universal Specification
function, updating the Account File Management application on Mastercard Connect™, and
modifying reports, layouts, and bulk files.
AN 2118—Account Level Management Universal Specification Enhancements............................194

Version History............................................................................................................................194
At-A-Glance................................................................................................................................194
Overview.................................................................................................................................... 195
Customer Impact........................................................................................................................ 197
Enhancements............................................................................................................................ 197
Platform Impact.......................................................................................................................... 199
Authorization..............................................................................................................................200
Reports.................................................................................................................................. 200
Layouts.................................................................................................................................. 200
Universal Specification Submission Layout..........................................................................200
Universal Specification Detail Response File Layout.............................................................201
World Shortfall (WLSF)—Summary Results, Final Layout..................................................... 202
World Shortfall (WLSF)—Summary Results, Preliminary Layout........................................... 203
World Elite Shortfall (WESF)—Summary Results, Final Layout..............................................204
World Elite Shortfall (WESF)—Summary Results, Preliminary Layout....................................206
Bulk Files................................................................................................................................ 207

AN 2118—Account Level Management Universal Specification

Enhancements
Mastercard is streamlining Account Level Management by enhancing the Universal
Specification function, updating the Account File Management application on Mastercard
Connect™, and modifying reports, layouts, and bulk files.
Version History

18 Dec 2018 Updated the Universal Specification Detail Response File Universal
Layout section as follows: Specification Detail
Response File Layout
• Revised Account Level Management Service Code
“Positions” from 179–183 to 179–298 in Detail Response
File Layout (Fixed) table.
• Revised Accepted Action Codes “Positions” from 184–
423 to 299–538 in Detail Response File Layout (Fixed)
table.
• Revised Reject Codes “Positions” from 424–663 to 539–
778 in Detail Response File Layout (Fixed) table.
At-A-Glance

Audience: Issuer, Processor
Products & Services: Account Level Management
Release: 19.Q2
Region: All

Overview
System: Account Level Management

Action Indicator:
Registration required—Issuer
Effective Date: Account Level Management: 12 April 2019
Overview
Background
Account Level Management (ALM) is a technology that enables processing at the Primary
Account Number (PAN) level rather than traditional processing for all PANs within the same
Bank Identification Number (BIN), which is the first six or eight digits of the PAN, or Account
Range, which is up to the first 11 digits of the PAN.
Account Level Management occurs when Mastercard recognizes individual PANs as being
eligible for specific cardholder benefits, services and features, and processes transactions
uniquely at the PAN level. This differs from account range processing, in which all cardholder
accounts within a designated account range are subject to identical processing rules and
standards. ALM processing allows for further granularity and segmentation down to the PAN
level so that issuers can manage the value they offer their cardholders with the value they see
in return.
For ALM processing to be applied on transactions they must be authorized and cleared within
the Mastercard Network.

The Universal Specification function provides issuers with a process to manage their accounts
and account relationships within all Account Level Management services through a PAN
management system, including PAN-to-account validation, history management, and account
registration. Mastercard accepts the information from issuers via bulk file or through the
Account File Management application on Mastercard Connect™ in comma-separated values
(CSV) format, fixed format, or Excel. Currently the Universal Specification response file allows
for 10 Accepted Action Codes and 10 Reject Codes. Also, the PAN Status field in the Universal
Specification request and response files is a mandatory field. This can lead customers to

inadvertently change the PAN status when more than one source (for example, an issuer and a
processor) sends the PAN-level data with an incorrect PAN status.

Mastercard will:
• Increase the number of allowed Accepted Action Codes and Reject Codes to 30 each,
which helps ensure that all scenarios are displayed to the customer in the Universal
Specification response file reports and in the Account File Management application on
Mastercard Connect™.
• Change the PAN status to an optional field in the Universal Specification request and
response files, which is intended to reduce the risk of customers unintentionally changing
the PAN status when providing information about a PAN.
• Change the Universal Specification Detail Response File Layout to accommodate 30
occurrences of the Account Management Service Code. These are a one-to-one match
with the corresponding Accepted Action Codes.
• Improve data reconciliation by adding fields to the World Shortfall and World Elite Shortfall
reports.
• Update the World Shortfall and World Elite Shortfall report field descriptions for clarity.

Through this initiative, Mastercard is enabling easier data reconciliation, including card
participation status, for our customers by enhancing the Universal Specification, updating the
Account File Management application on Mastercard Connect, and modifying reports and
bulk files.
Announcements
• “AN 2211—Reminder of Mandatory Date to Support Universal File Format and Delivery
Process for Account Level Management Services,” 3 October 2018
• “AN 1010—Account Level Management Refresh,” Release 17.Q4
Reference Manuals
Refer to this reference manual for information about the current state of Mastercard
processing:
• Account Level Management Manual

Customer Impact
manuals.
Customer Impact

Program or service requirement—Issuers globally that participate in any Account Level
Management service must support updates to the Universal Specification. This announcement
affects issuers and their processors currently participating in any Account Level Management
services. Customers not implementing the enhancements in this release announcement will
not benefit from the improved Account Level Management service. Furthermore, Mastercard
has mandated that participating customers support the Universal Specification for the ability
to submit PANs into the various ALM services by 1 April 2019.
Registration required—Issuers that want to participate in the Account Level Management
services Enhanced Value and Product Graduation must register their selected PANs with
Mastercard and provide any necessary supporting documentation for proof of reward program
requirements.
Testing recommended—Mastercard strongly recommends testing for issuers to support this
Account Level Management Refresh—Reminder

Mastercard is reminding participating issuers that they must support the Universal
Specification as of 1 April 2019. For more details on the Universal Specification, refer to “AN
2211—Reminder of Mandatory Date to Support Universal File Format and Delivery Process for
Account Level Management Services,” 3 October 2018 and “AN 1010—Account Level
Management Refresh,” Release 17.Q4 on the Technical Resource Center through Mastercard
Connect™.
Enhancements
Account Level Management

Mastercard will update the Universal Specification as follows:
• Modify the request and response file layouts.
• Make the PAN status an optional field in the request and response file layouts.

Enhancements
• Increase the allowable Accepted Action Codes and Reject Codes to 30 each in the Detail
Response File Layout.
• Expand the allowable occurrences of the Account Management Service Codes to 30 in the
Detail Response File Layout.
Account File Management Application

Mastercard will enhance the Account File Management application on Mastercard Connect™
to display 30 Accepted Action Codes or 30 Reject Codes.
ALM Reports
Mastercard will enhance the following existing reports to improve reconciliation.
• World Shortfall (WLSF)—Summary Results, Final Bulk File
• World Shortfall (WLSF)—Summary Results, Preliminary Bulk Files
• World Elite Shortfall (WESF)—Summary Results, Final Bulk Files
• World Elite Shortfall (WESF)—World Shortfall Summary Results, Preliminary Bulk Files
The following new fields will be added to the World Shortfall (WLSF) and World Elite Shortfall
(WESF) summary final and preliminary reports:
• Total number of PANs in active accounts
• Total of actual spend on active accounts
• Total of prorated spend on redirected accounts with low spend amount
• Total of actual spend on redirected accounts with low spend amount
The following field descriptions will be updated on the World Shortfall (WLSF) and World Elite
Shortfall (WESF) summary final and preliminary reports:
• Active Accounts Individual PANs
• Active Accounts Linked
• Total Prorated Spend on Active Accounts
Mastercard will update the fixed bulk file length for the following reports:
• World Shortfall (WLSF)—Summary Results, Final Bulk File
NOTE: For customers that receive the reports via the fixed bulk file format, the length will
change.

Platform Impact
Platform Impact

Account Level System System Single Message
Topic Management (Authorization) (Clearing) System
Message Flows
Message Layouts
Data Element
Definitions
IPM MPE
Interchange
CAB Programs,
Descriptions, and
Associated MCCs
Edits
Error Numbers
Interchange
Compliance
Pricing/Fees
Reports √
Bulk Files √
Forms
Reporting
SAFE
Single Message
Transaction Manager
250-byte Batch Data

File

Authorization

Account Level System System Single Message
Topic Management (Authorization) (Clearing) System
80-byte Financial
Authorization
Reports
Mastercard is enhancing existing World Shortfall (WLSF) and World Elite Shortfall (WESF)
summary final and preliminary reports to improve reconciliation for ALM participants.
Layouts
This section provides the modification details for the ALM report layouts.
Universal Specification Submission Layout

Mastercard accepts CSV, fixed, and excel formats for this file. The update to the Detail Record
Layout (Fixed) is provided in this section.
Detail Record Layout (Fixed)
Mandatory/ Mandatory/ Optional Comments and

Field Name Positions Attribute Optional Values
Primary Account 20 a-1 O Denotes status of PAN. Valid values are:

Number (PAN)
• A—PAN Active
Status
• C—PAN Closed

Authorization
Universal Specification Detail Response File Layout

Mastercard accepts CSV, fixed, and excel formats for this file. The updates to the Detail
Response File Layout (Fixed) are provided in this section.
Detail Response File Layout (Fixed)
Mandatory/ Mandatory/ Optional Comments and

Field Name Positions Attribute Optional Values
Primary Account 20 a-1 O Mastercard will update the status based

Number (PAN) on the following:
Status
• If a value is provided, then the status
will be updated with the data from
the request file
• If no value is provided and there is no
PAN status in the history, then the
value will default to active
• If no value is provided and there is a
PAN status in the history, then the
value will default to the history value
Account Level 179–298 ans-120 O Account Level Management Service

Management Code is 4 positions with maximum 30
Service Code occurrences. Left-justified, space-filled.
Code and descriptions are:
• SBSC—Small Business Spend Credit
• WHVL—World High Value
• WLSF—Shortfall World
• WESF—Shortfall World Elite
• PRGR—Product Graduation
• ENVL—Enhanced Value
• HISP—High Spend
• PHSP—Premium High Spend
• NSRV—No Service
Accepted Action 299–538 ans-240 C Accepted Action Code; 8 Alphanumeric,

Codes with maximum 30 occurrences. Left-
justified, space-filled.
Reject Codes 539–778 ans-240 O Reject Code; 8 Alphanumeric, with

maximum 30 occurrences. Left-justified,
space-filled.

Authorization
World Shortfall (WLSF)—Summary Results, Final Layout

World Shortfall Summary Results, Final; Final summary results of World Shortfall spend
analysis. The updates to the World Shortfall (WLSF)—Summary Results, Final Layout are
provided in this section.
Field Attributes Description

Total of Prorated Spend on n-14 Total of prorated spend on
Redirected Accounts with Low redirected accounts with low
Spend Amount spend. The two right-most
positions represent the decimal
positions of this U.S. dollar
amount.
Total of Actual Spend on n-14 Total of actual spend on
Redirected Accounts redirected accounts with low
spend (current active World
cards and their supporting
product code and linked cards,
which may have other product
codes). The two right-most
positions with Low Spend
represent the decimal positions
of this U.S. dollar amount.
Total Number of Active Accounts n-9 Total number of active accounts
(denominator). (All active World
account individual and grouped.)
Total Number of PANs in Active n-9 Total number of PANs in Active
Accounts Accounts, individual and
grouped (only active World
PANs).
Active Accounts Individual PANs n-9 Number of active accounts
comprised of individual
accounts. (World active
accounts, not grouped.)
Active Accounts Linked n-9 Number of active linked
Accounts. (All active World
accounts, grouped.)
Total Prorated Spend on Active n-14 Total prorated spend on active
Accounts accounts (numerator). (Current
active World cards and their
supporting product codes and
linked cards which may have
other product codes.) The two
right-most positions represent
the decimal positions of this U.S.
dollar amount.

Authorization

Total of Actual Spend on Active n-14 Total of actual spend on active
Accounts accounts. (Current active World
product code and linked cards
codes.) The two right-most
amount.
World Shortfall (WLSF)—Summary Results, Preliminary Layout

World Shortfall Summary Results, Preliminary; Summary results of World Shortfall analysis. The
updates to the World Shortfall (WLSF)—Summary Results, Preliminary Layout are provided in
this section.

amount.
spend (current active World
product codes and linked cards
of this US dollar amount.
account, individual and
grouped.)
grouped (only active World
PANs).

Authorization

accounts. (World active
Accounts. (All active World
accounts grouped.)
active World cards and their
supporting product code and
dollar amount.
product code and linked card
amount.
World Elite Shortfall (WESF)—Summary Results, Final Layout

World Elite Shortfall Summary Results, Final; Final summary results of World Elite Shortfall
spend analysis. The updates to the World Elite Shortfall (WESF)—Summary Results, Final
Layout are provided in this section.

amount.

Authorization

spend. (Current active World
Elite cards and their supporting
Elite accounts, individual and
grouped.)
grouped. (Only active World Elite
PANs.)
accounts. (World Elite active
accounts. (All active World Elite
accounts grouped.)
active World Elite cards and their
linked card which may have
dollar amount.
amount.

Authorization
World Elite Shortfall (WESF)—Summary Results, Preliminary Layout

World Elite Shortfall Summary Preliminary, Summary preliminary results of World Elite Shortfall
spend analysis. The updates to the World Elite Shortfall (WESF)—Summary Results, Preliminary
Layout are provided in this section.

amount.
spend. (Current active World
Elite accounts, individual and
grouped.)
grouped. (Only active World Elite
PANs.)
Active Accounts Linked n-9 Number of active accounts
accounts, (not grouped).

Authorization

active World Elite cards and their
dollar amount.
codes.) The two right most
amount.
Bulk Files
Mastercard will update the file length for the following bulk files. ALM customers receiving
reports via the bulk file must be prepared to accept the new length.
• Account File Universal File Specification Detail Responses
• Universal Specification Detail Response
• World Shortfall (WLSF)—Summary Results, Final Bulk Files

AN 2119—Enhancements to Batch Data File to Support Mastercard Send Activity
Chapter 15 AN 2119—Enhancements to Batch Data File to

Support Mastercard Send Activity
Mastercard is modifying the Financial (FREC)/Non-financial (NREC) Records—Required and the
Financial/Non-financial Exception Record (EREC)—Required of the 250-byte Batch Data File to
advise acquirers when these files contain information on Mastercard Send transaction settlement.
AN 2119—Enhancements to Batch Data File to Support Mastercard Send Activity.......................209

Version History............................................................................................................................209
At-A-Glance................................................................................................................................209
Overview.................................................................................................................................... 210
Customer Impact........................................................................................................................ 211
Enhancements............................................................................................................................ 212
Platform Impact.......................................................................................................................... 213
250-byte Batch Data File........................................................................................................ 214

AN 2119—Enhancements to Batch Data File to Support Mastercard

Send Activity
Mastercard is modifying the Financial (FREC)/Non-financial (NREC) Records—Required and the
Financial/Non-financial Exception Record (EREC)—Required of the 250-byte Batch Data File to
advise acquirers when these files contain information on Mastercard Send transaction
settlement.
Version History

At-A-Glance

Products & Services: Mastercard Send
Release: 19.Q2
Region: All
Action Indicator:
Attention warranted (Program/service-related)—Acquirers
Registration required—Acquirers
Testing recommended—Acquirers

Overview
Overview
Background
The Mastercard Send Platform enables a variety of payment options to secure the safety of
electronic payments. Mastercard Send is designed to work with banks, businesses,
governments and others to help modernize the way they send, or push, money domestically
and cross-border.
The 250-byte Batch Data File for financial, non-financial, and addendum records is an optional
file available to Single Message System customers. Each record layout is populated with the
appropriate fields and corresponding attributes from the online transaction processing log file
used to create the records. The Valid Values column displays the values generated from the
online messages, unless otherwise indicated. The layouts for the Financial (FREC)/Non-financial
(NREC) Records reflect the core format of a Single Message System financial/non-financial
transaction that contains data elements of both the online ISO message and batch calculated
settlement. These data elements provide information that can be used by Single Message
System processors for reconciliation and reporting purposes. Financial/Non-financial Exception
Record (EREC) is created when a reversal adjustment, chargeback, or representment record is
received.

The FREC/NREC and EREC record layouts do not have a field indicating Mastercard Send
transactions.

Mastercard will add a new field, Recon Activity, to the FREC/NREC and EREC record layouts to
assist participating acquirers with the identification of Mastercard Send initiated transactions.

The addition of the Recon Activity field on the FREC/NREC and EREC layouts will assist
acquirers with their reconciliation of Mastercard Send initiated transactions.

Reference Manuals
processing:
• Mastercard Send Domestic Program Guide
manuals.
Customer Impact

Single Message System acquirers that do not participate in the Mastercard Send service will
not see any change to the FREC/NREC or EREC record layouts. Position 250 will continue to be
a Filler field defaulting to spaces.
Attention warranted (Program/service-related)—Acquirers that participate in Mastercard Send
service and have opted to receive the 250-byte Batch Data File, must be aware of the new
Recon Activity field on the FREC/NREC and EREC record layouts indicating Mastercard Send
activity.
Registration—Acquirers must register to participate in the Mastercard Send service by
contacting their Mastercard implementation representative. Acquirers not currently receiving
the 250-byte Batch Data File may opt-in to receive this file by contacting their Mastercard
implementation representative.
Testing recommended—Mastercard recommends that participating acquirers perform testing.
Implementation Alert—Participating acquirers should be aware the new Recon Activity field
on the Batch Data File records will be present with the Single Message System implementation
date 12 April, 2019. However, information will not be populated in this field retroactively.
Data will be populated after Mastercard Send transactions occur following the 12 April, 2019
implementation date.

Enhancements

Message System:
Enhancements

To advise participating acquirers of Mastercard Send transaction activity, Mastercard will add a
Recon Activity field to these files in the 250-byte Batch Data File:
• Financial (FREC)/Non-financial (NREC) Records—Required
• Financial/Non-financial Exception Record (EREC)—Required
The valid values of this field will be:
• S = Send activity/ Single Message settled
• D = Send activity/Dual Message settled
• BLANK = Not Applicable
Single Message System acquirers that do not participate in the Mastercard Send service will
not see any change to the FREC/NREC or EREC record layouts. Position 250 will continue to be
a Filler field defaulting to spaces.

Platform Impact
Platform Impact
Dual Message System
Single Message
Message Flows
Message Layouts
IPM MPE
Interchange

and Associated MCCs
Edits
Error Numbers
Pricing/Fees
Reports
Bulk Files
Forms
Reporting
SAFE

Manager
250-byte Batch Data File √

Table File



To support this announcement the Single Message System will modify the following records in
the 250-byte Batch Data File:
Financial (FREC)/Non-financial (NREC) Records—Required

Position 250 will default to spaces for all non-applicable activity.
ISO DE No./
Field Description Position Subfield Attribute Valid Values
Recon Activity 250 N/A ans-1 S = Send activity/

Single Message
settled
D = Send activity/
Dual Message
settled
BLANK = Not
Applicable
Financial/Non-financial Exception Record (EREC)—Required

Position 250 will default to spaces for all non-applicable activity.
ISO DE No./
Recon Activity 250 N/A ans-1 S = Send activity/

Single Message
settled
D = Send activity/
Dual Message
settled
BLANK = Not
Applicable

AN 2120—U.S. Commercial Interchange Structure Changes
Chapter 16 AN 2120—U.S. Commercial Interchange

Structure Changes
Mastercard is modifying the U.S. commercial credit and debit/prepaid interchange structures to
encourage widespread issuance and acceptance of Mastercard card products.
AN 2120—U.S. Commercial Interchange Structure Changes....................................................... 217

Version History............................................................................................................................217
At-A-Glance................................................................................................................................218
Overview.................................................................................................................................... 218
Customer Impact........................................................................................................................ 219
Enhancements............................................................................................................................ 220
Valid and Eliminated Product Codes and IRDs After Enhancements......................................... 225
Platform Impact.......................................................................................................................... 234
Authorization..............................................................................................................................235
DE 48—Additional Data—Private Use.....................................................................................235
Subelement 38—Account Category...................................................................................235
DE 38—Authorization ID Response.........................................................................................235
Clearing......................................................................................................................................236
DE 38—Approval Code......................................................................................................236
IPM MPE Tables...................................................................................................................... 236
Table IP0018T1: Mastercard Product Graduation Parameters.............................................. 236
Parameters........................................................................................................................ 236
Interchange............................................................................................................................237
New Interchange Programs................................................................................................ 237
IRD 5A—Business Level 5 Data Rate I................................................................................. 237
IRD 5B—Business Level 5 Data Rate II.................................................................................240
IRD 5K—Business Level 5 Standard.................................................................................... 243
IRD 5N—Business Level 5 T&E Rate.................................................................................... 245
IRD 5R—Business Level 5 Utilities....................................................................................... 249
Modified Interchange Programs......................................................................................... 251
IRD 62—Commercial Large Ticket......................................................................................251
IRD E6—Mastercard Commercial Payments Account.......................................................... 251

CAB Code TE01.................................................................................................................251

CAB Programs, Descriptions, and Associated MCCs................................................................251
Life Cycled CAB Programs, Descriptions, and Associated MCCs..........................................252
Edits.......................................................................................................................................253
Modified Edit—DE 43 (Card Acceptor Name/Location), Subfield 5 (Card Acceptor State/
Province/Region Code)....................................................................................................... 253
Modified Edit—DE 63 (Transaction Life Cycle ID)................................................................ 254
Modified Edit—PDS 0158 (Business Activity ), Subfield 4 (Interchange Rate Designator)..... 255
Modified Edit—PDS 0158 (Business Activity ), subfield 4 (Interchange Rate Designator)......256
Modified Edit—PDS 0173 (Legal Corporate Name).............................................................262
Modified Edit—PDS 0505 (Passenger Name)...................................................................... 262
Modified Edit—PDS 0505 (Passenger Name)...................................................................... 263
Modified Edit—PDS 0520 (Travel Date).............................................................................. 264
Modified Edit—PDS 0520 (Travel Date).............................................................................. 265
Modified Edit—PDS 0544 (Rental Agreement Number)...................................................... 266
Modified Edit—PDS 0552 (Customer Service Toll-Free [800] Number).................................267
Modified Edit—PDS 0595 (Card Acceptor Type)................................................................. 267
Modified Edit—PDS 0595 (Card Acceptor Type)................................................................. 268
Modified Edit—PDS 0595 (Card Acceptor Type), subfield 1 (Business Type).........................268
Modified Edit—PDS 0595 (Card Acceptor Type), subfield 5 (Business Type Provided Code). 269
Modified Edit—PDS 0596 (Card Acceptor Tax ID), subfield 2 (Card Acceptor Tax ID
Provided Code).................................................................................................................. 270
Provided Code).................................................................................................................. 271
Modified Edit—PDS 0597 (Total Tax Amount).....................................................................271
Modified Edit—PDS 0597 (Total Tax Amount), Subfield 1 (Total Tax Amount)......................272
Modified Edit—PDS 0597 (Total Tax Amount), Subfield 1 (Total Tax Amount)......................272
Quarterly Mastercard Reporting..............................................................................................273


Mastercard is modifying the U.S. commercial credit and debit/prepaid interchange structures
to encourage widespread issuance and acceptance of Mastercard card products.
Version History

8 Jan 2019 Added the following error numbers to modified Modified Edit—PDS
edit PDS 0595: 0595 (Card Acceptor
Type)
• Error number 1023
• Error number 2277
Added the following product codes under Enhancements

Interchange Programs:
• MDB—Debit BusinessCard is added under Life
Cycle Product Codes
• MBS—Mastercard® B2B Product is added
under Life Cycle Product Codes (Large Market)
• MNF—Mastercard® Public Sector Commercial
Card is added under Life Cycle Product Codes
(Large Market)
Added product codes MBS, MES, and MNF to Valid and Eliminated
“Valid Brand Product Code” in the product table. Product Codes and IRDs
After Enhancements
Removed IRD E1. New Interchange
Programs
The removal of this content is not marked by
change bars.
Added the following text to the program criteria- IRD 5A—Business Level
approval code section of IRDs 5A and 5B: 5 Data Rate I
This is an Account Level Management
IRD 5B—Business Level
interchange program. To qualify for this program,
5 Data Rate II
position 6 must contain the value Q or R with a
GCMS Product ID of MAB, MCB, MEB, or MWB
or MPC. For valid values and more information
about Account Level Management, refer to the
Account Level Management User Manual.

Questions

At-A-Glance

At-A-Glance

Brands: Mastercard®, Debit Mastercard®
Products & Services: Commercial Products
Release: 19.Q2
Region: United States
Action Indicator:
Attention warranted (Network-related)—Acquirer
Attention warranted (Program/service-related)—Issuer
Overview

The commercial interchange rate structures for the U.S. region are similar for all types of
Mastercard commercial card products (Corporate, Purchasing, Fleet, Small Business Credit,
Debit, and Prepaid).


Mastercard is modifying and removing some of the enhanced data interchange rates/IRDs in
all of the commercial interchange structures. The Large Market interchange structure will
maintain enhanced data addendum rates (Data Rate III and Large Ticket) for non-T&E
transactions while “portfolio” data incentives for T&E (T&E III) transactions will be removed.
The small business credit and debit/prepaid structures will no longer have enhanced data or
“portfolio” data incentive rates for T&E and non-T&E transactions, respectively.

Mastercard reviews U.S. region interchange rate programs and adjusts them, if necessary, to
encourage widespread issuance and acceptance of Mastercard card products and to remain
competitive in Small Business and Large Market commercial card products.
Reference Manuals
processing:
• Account Level Management Manual
• Customer Interface Specification Manual
• Interchange Manual—U.S. Region
• IPM Clearing Formats and Error Numbers Manual
• Parameter Table Layouts Manual
manuals.
Customer Impact

Attention warranted (Network-related)—Acquirers in the U.S. region must support the new
interchange structures and revised clearing edits as described in this announcement.

Enhancements
Attention warranted (Program/service-related)—Issuers in the U.S. region must be prepared to

receive transactions using the new interchange programs and card acceptor business (CAB)
programs as described in this announcement.
this announcement.

Message System:
Enhancements
Dual Message System (Authorization)

Mastercard will introduce the following changes to the Authorization Platform to support this
announcement.
Data Elements
• Mastercard will support the new values in DE 38 (Approval Code), position 6 and DE 48
(Additional Data—Private Use), subelement 38 (Account Category), adding:
– Q = Level 5 (Small Business Spend Processing)
– R = Level 5 (Small Business Spend Processing and Product Graduation)

Enhancements
Dual Message (Clearing)

Mastercard will make changes to the Clearing Platform to support this announcement.
Data Elements
• Mastercard will support the new values in IPM DE 38 (Approval Code), position 6 adding:
– Q = Level 5 (Small Business Spend Processing)
– R = Level 5 (Small Business Spend Processing and Product Graduation)
IPM MPE Tables

Mastercard will add value R level 5 Account Category Code to IPM MPE Table IP0018T1
(Mastercard Product Graduation Parameters) and values Q and R level 5 Account Category
Code to IPM MPE Table IP0019T1 (Account Level Management Participation and Enhanced
Value Parameters).
Life Cycle Product Codes

• Through Release 20.Q2, Mastercard will accept only life cycle transactions for the following
Small Business Spend Processing product codes from specific interchange programs:
– MAB—World Elite Mastercard Business
– MBD—Mastercard Professional Debit Business Card
– MCB—BusinessCard
– MDB—Debit BusinessCard
– MDL—Business Debit Other Embossed
– MDW—World Elite™ Debit Mastercard® (Mastercard Black™ Debit LAC region excluding
Mexico)
– MEB—Executive
– MPC—Mastercard Professional Card
– MPW—Mastercard Prepaid Workplace B2B
– MRW—Prepaid Mastercard BusinessCard Credit
– MWB—World Mastercard for Business
• The above product codes are life cycled from the following IRDs:
– IRD 66—Commercial Data Rate III
– IRD 62—Commercial Large Ticket I
– IRD 94—Commercial Large Ticket II
– IRD 99—Commercial Large Ticket III
– IRD E1—Commercial Large Ticket I MPG
– IRD 76, 86—Commercial T&E Rate I
– IRD 89—Commercial T&E Rate III

Enhancements
Life Cycle Product Codes (Large Market)

• Through Release 20.Q2, Mastercard will accept only life cycle transactions for the following
Small Business Spend Processing product codes from specific interchange programs:
• MAC—Mastercard®Corporate World Elite®
• MAP—Mastercard Commercial Payments Account
• MBS—Mastercard® B2B Product
• MCF—Mastercard Corporate Fleet Card®
• MCO—Mastercard Corporate
• MCP—Mastercard Corporate Purchasing Card®
• MEO—Mastercard Corporate Executive Card®
• MGF—Mastercard®Government Commercial Card
• MNF—Mastercard® Public Sector Commercial Card
• MPK—Prepaid Mastercard®Government Commercial Card
• MWO—Mastercard Corporate World
• The above product codes are life cycled from the following IRDs:
– IRD E1—Commercial Large Ticket I MPG
– IRD 76, 86—Commercial T&E Rate I
– IRD 89—Commercial T&E Rate III
Life Cycle of Interchange Programs

Through Release 20.Q2, Mastercard will accept only life cycle transactions for the following
interchange programs:
• IRD SC—Business Level 2 Data Rate III
• IRD 3C—Business Level 3 Data Rate III
• IRD 4C—Business Level 4 Data Rate III
• IRD SE—Business Level 2 Large Ticket I
• IRD SF—Business Level 2 Large Ticket II
• IRD SG—Business Level 2 Large Ticket III
• IRD 3E—Business Level 3 Large Ticket I
• IRD 3F—Business Level 3 Large Ticket II
• IRD 3G—Business Level 3 Large Ticket III
• IRD 4E—Business Level 4 Large Ticket I
• IRD 4F—Business Level 4 Large Ticket II
• IRD 4G—Business Level 4 Large Ticket III
• IRD SL—Business Level 2 T&E Rate I
• IRD SO—Business Level 2 T&E Rate III
• IRD 3L—Business Level 3 T&E Rate I
• IRD 3O—Business Level 3 T&E Rate III

Enhancements
• IRD 4L—Business Level 4 T&E Rate I

• IRD 4O—Business Level 4 T&E Rate III
Life Cycle Product Code MRW

Through Release 20.Q2, Mastercard will accept only life cycle transactions for any occurrences
of product code MRW (Mastercard Prepaid—Commercial) from all U.S. region commercial
interchange programs.
Modifications to Transaction Size Thresholds

Mastercard will increase the minimum threshold amount to USD 10,000 for the following
IRDs:
• IRD 62—Commercial Large Ticket I
• IRD E6—Mastercard Commercial Payments Account
New Account Category for New Small Business Level 5 Interchange Structure
Mastercard will create new Account Category Code values to represent the Level 5 spend:
• Q = Level 5 (Small Business Spend Processing)
• R = Level 5 (Small Business Spend Processing and Product Graduation)
• The default spend threshold for Level 5 is ≥ USD 250K
• Mastercard will modify the threshold for existing Level 4 from greater than USD 100K to
USD 100K – USD 250K.
New IRDs to Support New Small Business Level 5 Interchange Structure

Mastercard will create new IRDs to support Small Business Spend Processing (Level 5):
• Data Rate:
– IRD 5A—Business Level 5 Data Rate I
– IRD 5B—Business Level 5 Data Rate II
• Commercial Standard:
– IRD 5K—Business Level 5 Standard
• T&E:
– IRD 5N—Business Level 5 T&E Rate
• Utilities:
– IRD 5R—Business Level 5 Utilities
• The new IRDs will be valid for Card Program ID MCC and for the following GCMS Product
IDs: MAB, MCB, MEB, MPC, MWB.
Clearing Edits
Mastercard will modify clearing edits to support this release announcement.

Enhancements
Life Cycled CAB Programs, Descriptions, and Associated MCCs

• CAB program TE02 (Corporate T&E Rate II Card) will be accepted only for life cycle
transactions until Release 20.Q2 under the following IRDs:
– IRD 69—Commercial T&E Rate II
– IRD SN—Business Level 2 T&E Rate II
– IRD 3N—Business Level 3 T&E Rate II
• MCC H001 (Lodging) will be accepted only for life cycle transactions until Release 20.Q2
under the following IRDs:
– IRD 62—Commercial Large Ticket I
– IRD E6—Mastercard Commercial Payments Account
• The removal of CAB program TE02 (Corporate T&E Rate II Card) and addition of TE01
(Corporate T&E Rate I Card) enables MCC 5812 (Eating Places, Restaurants) to be enabled
for the following IRDs:
– IRD 69—Commercial T&E Rate II
– IRD SN—Business Level 2 T&E Rate II

Enhancements
Valid and Eliminated Product Codes and IRDs After Enhancements

The following tables display a listing of the product codes and IRDs that will be valid or
eliminated with these enhancements.

Enhancements
Valid and Eliminated Product Codes and IRDs After Enhancements
Interchange Rate Valid Brand Product

Structure Code IRDs Eliminated April 2019 Valid IRDs
Large Market MAC, MAP, MBS, IRD 94—Commercial Large IRD CH—Charities
MCF, MCO, MCP, Ticket II
MEO, MES, MGF,
IRD 99—Commercial Large IRD 68—Commercial Data
MNF, MPK, MWO
Ticket III Rate I
IRD E1—Commercial Large IRD 67—Commercial Data

Ticket I MPG Rate II
IRD 76, 86—Commercial T&E IRD 66—Commercial Data

Rate I Rate III
IRD 89—Commercial T&E Rate IRD 62—Commercial Large

III Ticket (formerly Commercial
Large Ticket I)
IRD 65—Commercial
Standard
IRD 69—Commercial T&E

Rate (formerly Commercial
T&E Rate II)
IRD 21—Commercial
Payment Transaction
IRD EZ—Commercial Rebate
IRD 39—Commercial
Refund Group 1
IRD 40—Commercial
Refund Group 2
IRD 41—Commercial
Refund Group 3
IRD 42—Commercial
Refund Group 4
IRD E6—Commercial
Payments Account (only
valid for MAP)
IRD MC—MPP
IRD MM—MPP

Enhancements

Level 1/Business Core MAB, MCB, MEB, IRD 66—Commercial Data Rate IRD CH—Charities
MPC, MWB III

Ticket I Rate I

Ticket II Rate II
IRD 99—Commercial Large IRD 65—Commercial

Ticket III Standard
IRD E1—Commercial Large IRD 69—Commercial T&E

Ticket I MPG Rate (formerly Commercial
T&E Rate II)
IRD 76, 86—Commercial T&E IRD CU—Commercial

Rate I Utilities
IRD 89—Commercial T&E Rate IRD 21—Commercial

III Payment Transaction
IRD 39—Commercial
Refund Group 1
IRD 40—Commercial
Refund Group 2
IRD 41—Commercial
Refund Group 3
IRD 42—Commercial
Refund Group 4
IRD MC—MPP
IRD MM—MPP

Enhancements

Level 2/Business World MAB, MCB, MEB, IRD SC—Business Level 2 Data IRD CH—Charities
MPC, MWB Rate III
IRD SE—Business Level 2 Large IRD SA—Commercial Data

Ticket I Rate I
IRD SF—Business Level 2 Large IRD SB—Commercial Data

Ticket II Rate II
IRD SG—Business Level 2 Large IRD SK—Commercial

Ticket III Standard
IRD SL—Business Level 2 T&E IRD SN—Commercial T&E

Rate I Rate (formerly Commercial
T&E Rate II)
IRD SO—Business Level 2 T&E IRD SR—Commercial

Rate III Utilities
IRD 21—Commercial
Payment Transaction
IRD 39—Commercial
Refund Group 1
IRD 40—Commercial
Refund Group 2
IRD 41—Commercial
Refund Group 3
IRD 42—Commercial
Refund Group 4
IRD MC—MPP
IRD MM—MPP

Enhancements

Level 3/Business World Elite MAB, MCB, MEB, IRD 3C—Business Level 3 Data IRD CH—Charities
MPC, MWB Rate III
IRD 3E—Business Level 3 Large IRD 3A—Commercial Data

Ticket I Rate I
IRD 3F—Business Level 3 Large IRD 3B—Commercial Data

Ticket II Rate II
IRD 3G—Business Level 3 Large IRD 3K—Commercial

Ticket III Standard
IRD 3L—Business Level 3 T&E IRD 3N—Commercial T&E

T&E Rate II)
IRD 3O—Business Level 3 T&E IRD 3R—Commercial

Rate III Utilities
IRD 21—Commercial
Payment Transaction
IRD 39—Commercial
Refund Group 1
IRD 40—Commercial
Refund Group 2
IRD 41—Commercial
Refund Group 3
IRD 42—Commercial
Refund Group 4
IRD MC—MPP
IRD MM—MPP

Enhancements

Level 4 MAB, MCB, MEB, IRD 4C—Business Level 4 Data IRD CH—Charities
MPC, MWB Rate III
IRD 4E—Business Level 4 Large IRD 4A—Commercial Data

Ticket I Rate I
IRD 4F—Business Level 4 Large IRD 4B—Commercial Data

Ticket II Rate II
IRD 4G—Business Level 4 Large IRD 4K—Commercial

Ticket III Standard
IRD 4L—Business Level 3 T&E IRD 4N—Commercial T&E

T&E Rate II)
IRD 4O—Business Level 3 T&E IRD 4R—Commercial

Rate III Utilities
IRD 21—Commercial
Payment Transaction
IRD 39—Commercial
Refund Group 1
IRD 40—Commercial
Refund Group 2
IRD 41—Commercial
Refund Group 3
IRD 42—Commercial
Refund Group 4
IRD MC—MPP
IRD MM—MPP

Enhancements

Level 5 (NEW) MAB, MCB, MEB, IRD CH—Charities

MPC, MWB
IRD 5A—Commercial Data
Rate I
IRD 5B—Commercial Data

Rate II
IRD 5K—Commercial
Standard
IRD 5N—Commercial T&E

Rate
IRD 5R—Commercial
Utilities
IRD 21—Commercial
Payment Transaction
IRD 39—Commercial
Refund Group 1
IRD 40—Commercial
Refund Group 2
IRD 41—Commercial
Refund Group 3
IRD 42—Commercial
Refund Group 4
IRD MC—MPP
IRD MM—MPP

Enhancements

Commercial Debit (NEW) MBD, MDB, MDL IRD 66—Commercial Data Rate IRD CH—Charities
III

Ticket I Rate I

Ticket II Rate II

Ticket III Standard

T&E Rate II)
IRD 76, 86—Commercial T&E IRD CU—Commercial

Rate I Utilities
IRD 89—Commercial T&E Rate IRD 21—Commercial

III Payment Transaction
IRD 39—Commercial
Refund Group 1
IRD 40—Commercial
Refund Group 2
IRD 41—Commercial
Refund Group 3
IRD 42—Commercial
Refund Group 4
IRD MC—MPP
IRD MM—MPP

Enhancements

Commercial Prepaid (NEW) MAQ, MPW IRD 66—Commercial Data Rate IRD CH—Charities
III

Ticket I Rate I

Ticket II Rate II

Ticket III Standard

T&E Rate II)
IRD 76, 86—Commercial T&E

Rate I
IRD 89—Commercial T&E Rate IRD CU—Commercial

III Utilities
IRD 21—Commercial
Payment Transaction
IRD 39—Commercial
Refund Group 1
IRD 40—Commercial
Refund Group 2
IRD 41—Commercial
Refund Group 3
IRD 42—Commercial
Refund Group 4
IRD E6—Commercial
Payments Account (only
valid for MAQ)
IRD MC—MPP
IRD MM—MPP

Platform Impact
Platform Impact
Dual Message System
Single Message
Message Flows
Message Layouts
IPM MPE √
Interchange √

√
and Associated MCCs
Edits √
Error Numbers
Pricing/Fees
Reports
Bulk Files
Forms
√ √
Reporting
Transaction Investigator √
SAFE

Manager

Table File

Authorization
Authorization

Subelement 38—Account Category

Subelement 38 (Account Category) supports Account Level Management.
Values
Q = Level 5 (Small Business Spend Processing)
R = Level 5 (Small Business Spend Processing and Product Graduation)
DE 38—Authorization ID Response
DE 38 (Authorization ID Response) is a transaction response ID code that the authorizing
institution assigns. DE 38 is used to transmit a card issuer’s “authorization code” for
Authorization transactions.
DE 38, position 6 may contain any of the following Account Level Management account
category codes when the account range is participating in an Account Level Management
service. Valid account category codes by program are:
• Q—Level 5 (Small Business Spend Processing)
• R—Level 5 (Small Business Spend Processing and Product Graduation)

Clearing
Mastercard will update the Authorization Transaction Invesitgator to include the new values Q
and R in DE 38, position 6.
Clearing

DE 38—Approval Code
DE 38 (Approval Code) is a code the authorizing institution assigns indicating approval.
DE 38, position 6 may contain any of the following Account Level Management account
category codes when the account range is participating in an Account Level Management
service. Valid account category codes by program are:
• Q—Level 5 (Small Business Spend Processing)
• R—Level 5 (Small Business Spend Processing and Product Graduation)
IPM MPE Tables

Mastercard will add value R level 5 Account Category Code to IPM MPE Table IP0018T1
(Mastercard Product Graduation Parameters) and values Q and R level 5 Account Category
Code to IPM MPE Table IP0019T1 (Account Level Management Participation and Enhanced
Value Parameters).
Table IP0018T1: Mastercard Product Graduation Parameters

This table contains the valid account category/licensed product ID/IRD combinations.
Field Name Positions Attribute Comments and Values
Account Category Code 20 an-1 The Account Category Code Valid

values:
R = Level 5 + Product Graduation

Parameters
This table identifies Account Level Management participation based on Card Program
Identifier and Business Service Arrangement Type and Business Service ID code combination. It

Clearing
also provides information related to the Business As Usual and Enhanced Value Platform
account categories.
Field Name Positions Attribute Comments and Values
Account Category Code 35 an-1 The Account Category Code

An account category code setup for the Business
Service and Acceptance Brand where the IRD,
shown as spaces, indicates the Account Level
Management programs that the Business Service
supports. If the Business Service participates in
Account Level Management and there is no
unique IRDs setup with the Account Category
Code, then incentive interchange is determined
by rate type 20 on the transaction.
Account Level Management participation valid
values:
Q = Level 5
R = Level 5 + Product Graduation
Interchange
New Interchange Programs

Mastercard will introduce the following new interchange programs to support this
announcement.
IRD 5A—Business Level 5 Data Rate I

Transactions must meet the following requirements to qualify for this U.S. region commercial
interchange program.
Card Program ID MCC
GCMS Product ID SBSP—MAB, MCB, MEB, MPC, MWB

• 18—Unique Transaction (requires unique MCC)

Clearing
Card Acceptor • B001—Cruise/Steamship
Business (CAB) • F002—Restaurant. All MCCs assigned to F001 except MCC 5812 (Eating
Program Places, Restaurants)
• OT36—U.S. Other
• U001—Unique
Timeliness GCMS—Three days

Interchange compliance—Four days
Non–face-to-face transactions are exempt from the timeliness test.
If the criteria in the following table are met, transactions submitted for all programs
in this category are exempt from the timeliness test.
Element Value
DE 22 (Point of Service Data Code), One of the following:
subfield 1 (Terminal Data: Card Data
Input Capability) • A—PAN auto-entry via contactless
magnetic stripe
• M—PAN auto-entry via contactless
M/Chip
DE 22, subfield 3 (Terminal Data: Card 0—No capture capability

Capture Capability)
DE 22, subfield 4 (Terminal Operating 2—On card acceptor premises;
Environment) unattended terminal
DE 22, subfield 5 (Cardholder Present 0—Cardholder present
Data)
DE 22, subfield 6 (Card Present Data) 1—Card present
DE 22, subfield 7 (Card Data: Input One of the following:
Mode)
• A—PAN auto-entry via contactless
magnetic stripe
M/Chip

Clearing
DE 26 (Card Acceptor Business Code • 4111—Transportation, Suburban and
[MCC]) Local Commuter Passenger, including
Ferries
• 4131—Bus Lines
• 4784—Bridge and Road Fees, Tolls
Approval Code Required

This is an Account Level Management interchange program. To qualify for this
program, position 6 must contain the value Q or R with a GCMS Product ID of
MAB, MCB, MEB, or MWB or MPC. For valid values and more information about
Account Level Management, refer to the Account Level Management User Manual.
Magnetic stripe data Not required

from authorization
message
Trace ID Required
Must contain a valid Banknet Reference Number, and the Banknet Date must
contain a valid date in the format MMDD

Business Code (MCC)
Must contain an MCC other than one of the following:
• MCC 3000–3299 or 4511—Airline
• MCC 3351–3500, 7512, 7513, or 7519—Automobile/Vehicle Rental
• MCC 3501–3999 or 7011—Hotel/Motel
• MCC 4112—Passenger Railways
• MCC 5812—Eating Places, Restaurants

Card Acceptor ID Code Required
Card Acceptor Name Required
Card Acceptor Street Required
Address
Card Acceptor Postal Required

(ZIP) Code

Clearing
Card Acceptor State, Required for transactions occurring in the United States
Province, or Region
When DE 43 (Card Acceptor Name/Location), subfield 6 (Card Acceptor Country
Code
Code) contains USA, this subfield must contain a valid state code.
Card Acceptor Country Required

Code
Mastercard Assigned Not required

ID
Financial Detail All MCCs require the following Financial Detail Addendum (Corporate Card
Addendum/1644 Common Data Requirements)/1644 data:
• PDS 0595 (Card Acceptor Type)
• PDS 0596 (Card Acceptor Tax ID)
Notes
IRD 5B—Business Level 5 Data Rate II

Card Program ID MCC

Card Acceptor • B001—Cruise/Steamship

Business (CAB) • F002—Restaurant. All MCCs assigned to F001 except MCC 5812 (Eating
Program Places, Restaurants)
• OT36—U.S. Other
• U001—Unique

Clearing
Timeliness GCMS—Three days
Interchange compliance—Four days
Non–face-to-face transactions are exempt from the timeliness test.
If the criteria in the following table are met, transactions submitted for all programs
in this category are exempt from the timeliness test.
Element Value
DE 22 (Point of Service Data Code), One of the following:
subfield 1 (Terminal Data: Card Data
Input Capability) • A—PAN auto-entry via contactless
magnetic stripe
M/Chip
DE 22, subfield 3 (Terminal Data: Card 0—No capture capability

Capture Capability)
DE 22, subfield 4 (Terminal Operating 2—On card acceptor premises;
Environment) unattended terminal
DE 22, subfield 5 (Cardholder Present 0—Cardholder present
Data)
DE 22, subfield 6 (Card Present Data) 1—Card present
DE 22, subfield 7 (Card Data: Input One of the following:
Mode)
• A—PAN auto-entry via contactless
magnetic stripe
M/Chip
DE 26 (Card Acceptor Business Code • 4111—Transportation, Suburban and

[MCC]) Local Commuter Passenger, including
Ferries
• 4131—Bus Lines
• 4784—Bridge and Road Fees, Tolls


from authorization
message

Clearing
Trace ID Required

Business Code (MCC)
Must contain an MCC other than one of the following:
• MCC 3000–3299 or 4511—Airline

Address

(ZIP) Code
Province, or Region
Code

Code

ID

Clearing
Financial Detail The following Financial Detail Addendum (Corporate Card Common Data
Addendum/1644 Requirements)/1644 data is required:
• PDS 0508 (Customer Code) (Must be sent if provided by the customer. Do not
send all spaces.)
• PDS 0597 (Total Tax Amount) (Not required for transactions involving
Mastercard Commercial Cards occurring at fuel locations [MCC 4468, 5541,
5542, 5499, 5983] or any of the following MCCs: 4111, 4131,4215, 4784,
8211, 8220, 8398, 8661, 9211, 9222, 9311, 9399, 9402. Additionally, PDS
0597 is not required for qualified Mastercard Payment Gateway [MPG]
transactions. Qualified MPG transactions are denoted by a value of 01 in PDS
0057 [Transaction Category Indicator].)
Notes
IRD 5K—Business Level 5 Standard

Card Program ID MCC


Clearing
Card Acceptor • A001—Airline
Business (CAB) • B001—Cruise/Steamship
Program
• F001—Restaurant
• H001—Lodging
• OTH1—Other
• R001—Railways
• U001—Unique
Timeliness None

from authorization
message
If present, must contain a valid Banknet Reference Number, and the Banknet Date
must contain a valid date in the format MMDD

Business Code (MCC)

Card Acceptor Street N/A
Address

Clearing
(ZIP) Code
Province, or Region
Code

Code
Cannot contain spaces for original First Presentment/ 1240 messages submitted
with DE 3 (Processing Code), subfield 1 (Cardholder Transaction Type), value other
than 20—Credit (Purchase Return). For all other messages, this field is required,
unless exempted by Corporation Standards.

ID
Notes
IRD 5N—Business Level 5 T&E Rate

Card Program ID MCC
Card Acceptor • TE01—Corporate T&E Rate I Card

Business (CAB)
Program For card acceptor business codes (MCCs) associated with CAB programs, refer to

Clearing
Timeliness GCMS— three days, except for airline transactions, for which the requirement is
nine days.
Interchange compliance—All transactions submitted for the commercial T&E rate
programs are exempt from the timeliness test.


from authorization
message
Trace ID Required

Business Code (MCC)
Must contain one of the following MCCs:
• MCC 3000–3299 or 4511—Airline
MCC 4722 (Travel Agencies and Tour Operations) is not permitted in the clearing
message.

Address

(ZIP) Code
Province, or Region
Code

Clearing
Code

ID

Clearing
Airline and Passenger Railways MCCs require the data listed in the following
messages:
• Financial Detail Addendum (Passenger Transport Detail—General Ticket
Information)/1644:
– PDS 0505 (Passenger Name)
– PDS 0506 (Ticket Number)
– PDS 0507 (Issuing Carrier)
• Financial Detail Addendum (Passenger Transport Detail—Trip Leg Data)/1644:
– PDS 0520 (Travel Date)
– PDS 0521 (Carrier Code)
– PDS 0522 (Service Class Code)
– PDS 0523 (City of Origin/Airport Code)
– PDS 0524 (City of Destination/Airport Code)
For Passenger Railways MCCs, the following Financial Detail Addendum (Passenger
Transport Detail—Rail Data)/1644 data may be provided in place of, or in addition
to, the Financial Detail Addendum (Passenger Transport Detail—Trip Leg Data)/
1644:
• PDS 0505 (Passenger Name)
• PDS 0520 (Travel Date)
• PDS 0664 (Start Station)
• PDS 0665 (Destination Station)
• PDS 0756 (Passenger Description)
Vehicle Rental MCCs require the following Financial Detail Addendum (Vehicle
Rental Detail)/1644 data:
• PDS 0544 (Rental Agreement Number)
• PDS 0545 (Renter Name)
• PDS 0546 (Rental Return City)
• PDS 0547 (Rental Return State/Province)
• PDS 0548 (Rental Return Country)
• PDS 0549 (Return Location ID)
• PDS 0550 (Rental Return Date)
• PDS 0551 (Rental Check-Out Date)
• PDS 0552 (Customer Service Toll-Free [800] Number)
Hotel/Motel MCCs require the following Financial Detail Addendum (Lodging
Summary)/1644 data:
• PDS 0552 (Customer Service Toll-Free [800] Number)

Clearing
• PDS 0574 (Arrival Date)

• PDS 0575 (Departure Date)
• PDS 0576 (Folio Number)
• PDS 0577 (Property Phone Number)
Notes
IRD 5R—Business Level 5 Utilities

Card Program ID MCC
Card Acceptor • UT01—Utilities

Business (CAB)
Program For card acceptor business codes (MCCs) associated with CAB programs, refer to
Timeliness GCMS—GCMS—Two days for all programs in this category

Interchange compliance—Three days for all programs in this category


from authorization
message
Trace ID Required

Clearing
Business Code (MCC)
Must contain MCC 4900 (Utilities—Electric, Gas, Oil, Sanitary, Water)
Amount Tolerance 10%

Some MCCs are exempt from all amount tolerance tests.

Address

(ZIP) Code
Province, or Region
Code

Code
Cannot contain spaces for original First Presentment/ 1240 messages submitted
with DE 3 (Processing Code), subfield 1 (Cardholder Transaction Type), value other
than 20—Credit (Purchase Return). For all other messages, this field is required,
unless exempted by Corporation Standards.

ID
Financial Detail The following Financial Detail Addendum/1644 criteria apply to the U.S. region
Addendum/1644 commercial Utilities interchange programs.
The following Financial Detail Addendum (Corporate Card Common Data
Requirements)/1644 data is required:
Notes In the First Presentment/1240, PDS 0173 (Legal Corporate Name) is required.

Clearing

Mastercard will modify the following interchange programs to support this announcement.
IRD 62—Commercial Large Ticket

Mastercard will increase the minimum threshold amount to support this release.
Notes The transaction amount must be a minimum of USD 10,000 or greater to submit with
this interchange program.
IRD E6—Mastercard Commercial Payments Account

Mastercard will increase the minimum threshold amount to support this release.
Interchange
Compliance
Failure
Criteria Requirement Adjustment
Notes There are five tiers for transaction amounts:
• USD 10,000–25,000
• USD 25,000.01–100,000
• USD 100,000.01–500,000
• USD 500,000.01–1,000,000
• Greater than USD 1,000,000
Interchange Rates
Mastercard will provide information about interchange rates in a future interchange
announcement.
CAB Code TE01

Mastercard is adding the following CAB Code to support this release.
Mastercard is adding CAB code TE01 to the following IRDs 69, SN, 3N, 4N, 5N.
CAB Programs, Descriptions, and Associated MCCs

Mastercard is life cycling card acceptor business (CAB) programs to support this
announcement.
For a complete list of valid card acceptor business codes (MCCs), see the spreadsheet included
in the Comprehensive MCC Listing by Formatted File Type section in Chapter 3 of the Quick
Reference Booklet.

Clearing

Mastercard is life cycling the following until Release 20.Q2 to support this release
announcement.
CAB program TE02 (Corporate T&E Rate II Card) will be accepted for life cycle transactions
until Release 20.Q2 under the following IRDs 69, SN, 3N, 4N, 5N.
MCC H001 (Lodging) will be accepted for life cycle transactions until Release 20.Q2 under
IRDs 62, 94, 99, E1, E6.

Clearing
Edits
announcement.
Modified Edit—DE 43 (Card Acceptor Name/Location), Subfield 5 (Card Acceptor

State/Province/Region Code)
This edit will be modified to add these IRDs: IRD 5A (Business Level 5 Data Rate I), IRD 5B
(Business Level 5 Data Rate II), IRD 5K (Business Level 5 Standard), IRD 5N (Business Level 5
T&E Rate), and IRD 5R (Business Level 5 Utilities).
Error Number Current Requirement Modifications this Release

0623 The Clearing Platform will ensure that: This edit will be modified to add IRDs
5A, 5B, 5K, 5N.
• DE 43 (Card Acceptor Name/Location),
subfield 5 (Card Acceptor State/Province/ • Process code 00 and 18
Region Code) must be present and cannot • Must be US
contain all spaces or non-printable, special
characters if the transaction is issued and
acquired in the U.S. Region, and
• PDS 0158 (Business Activity), subfield 4
(Interchange Rate Designator) is applicable,
and
• DE 43 (card Acceptor Name/Location ,
subfield 5 (Card Acceptor State/Province/
Region Code must also be present and
cannot contain all spaces or non-printable.
special characters if the transaction is an
international transaction (issued or
acquired outside the U.S. Region ) and
• PDS 0158 (Business Activity), subfield 4
(Interchange Rate Designator) is Corporate
Purchasing Data rate II.

Clearing
Modified Edit—DE 63 (Transaction Life Cycle ID)

Mastercard will modify this edit to exclude new IRD 5K (Business Level 5 Standard) for BSA
2/010001.

1100 The Clearing Platform must ensure that DE 63 This edit will be modified to exclude
(Network Data) is present for US acquired IRD 5K for BSA 2/010001.
incentive interchange programs.
The following are excluded from this edit:
• IRD 5K for BSA 2/010001

Clearing
Modified Edit—PDS 0158 (Business Activity ), Subfield 4 (Interchange Rate

Designator)
Mastercard will modify this edit to rename values Q and R from Reserve for Future Use to Q =
Level 5 and R = Level 5 and Product Graduation.
2422 The Clearing Platform must ensure that if the This edit will be modified to rename
transaction is submitted for a specific values Q and R.
interchange structure the value in the DE 38 • Q = Level 5
(Approval Code), position 6 equals the same • R = Level 5 and Product
interchange structure. Graduation.
Valid account category codes are:
• B = EV only
• C = Level 1
• D = Level 1 + Product Graduation
• E = Level 2
• F = Level 2 + Product Graduation
• G = Level 3
• H = Level 3 + Product Graduation
• J = Level 4
• K = Level 4 + Product Graduation
• M = Both EV and Product Graduation
• Q = Reserved for Future Use
• R = Reserved for Future Use
• S = High Value and Premium High Spend
• T = High Value/Product Graduated or
Premium High Spend/Product Graduation
• W = Spend Shortfall
• Y = Spend Shortfall and Product
Graduation
GCMS must ensure that the account supports
one of the following account category type
codes:
• 000 BAU
• 001 EVP or WHS/PHS
• 003 (EVP or PG) or (WHS/PHS and PG) or
(Spend Shortfall and PG) or (USSB and PG)
• 004 Spend Shortfall or USSB
This edit excludes collection only and reversal messages.

Clearing

Designator)
Mastercard will modify this edit to add values Q and R.
2431 The Clearing Platform must ensure that This edit will be modified to add
transactions that are not submitted with an values Q and R.
Enhanced IRD, World High Spend IRD, or Small • Q = Level 5
Business IRD when the Account Range does • R = Level 5 and Product
not participate in Account Level Management Graduation.
or DE 38 (Approval Code) is not present or DE
38 position 6 does not equal B, C, D, E, F, G,
H, J, K, M, Q, R, S, or T. Only one of the
conditions must be true.
This edit is performed at the Central Site for the following messages:

Designator)
Mastercard will modify this edit to add new IRD 5N (Business Level 5 T&E Rate).
1073 The Clearing Platform must ensure that if PDS This edit will be modified to add IRD
0158 (Business Activity ), subfield 4 5N.
(Interchange Rate Designator) contains a
• Process code 00
specified IRD, and DE 26 (Card Acceptor
Business Code [MCC]) in the associated First • Must be US
Presentment/1240 contains an Airline MCC • Must be MCC type A
(MCC group code of A), then PDS 0501
(Transaction Description), subfield 1 (Usage
Code), of an occurrence of transaction detail
data must contain value 01 (Passenger
Transport Detail) and PDS 0501 subfield 2
(Industry Record Number), Usage Code value
01 must contain value 000 (Passenger
Transport Detail—General Ticket Information).
This edit excludes Collection Only and Reversal messages.

Clearing

Designator)
• Process code 00
Presentment/1240 contains an Airline MCC • Must be MCC type A
(MCC group code of A), then PDS 0501
Transport Detail—Trip Leg Data).
The following messages are excluded from this edit:
• Collections Only
• Reversals

Clearing

Designator)
• Process code 00
Presentment/1240 contains a Railway MCC • Must be MCC type R
(MCC group code of R), then PDS 0501
Transport Detail—General Ticket Information).

Clearing

Designator)
• Process code 00
Presentment/1240 contains a Railway MCC • Must be MCC type R
(MCC group code of R), then PDS 0501
Transport Detail—Trip Leg Data) or 002
Passenger Transport Detail—Rail Data).

Clearing

Designator)
• Process code 00
Presentment/1240 contains a vehicle rental • Must be MCC type V
MCC (MCC group code of V), then PDS 0501
data must contain value 05 (Vehicle Rental
Detail) and PDS 0501 subfield 2 (Industry
Record Number), Usage Code value 01 must
contain value 000 (Passenger Transport Detail
—General Ticket Information).

Clearing

Designator)
• Process code 00
Presentment/1240 contains a lodging MCC • Must be MCC type H
(MCC group code of H), then PDS 0501
data must contain value 06 (Lodging
Summary) and PDS 0501 subfield 2 (Industry
Record Number), Usage Code value 01 must
contain value 000 (Passenger Transport Detail
—General Ticket Information).

Clearing
Modified Edit—PDS 0173 (Legal Corporate Name)

2/010001.

1023 The Clearing Platform must ensure This edit will be modified to
that PDS 0173 (Legal Corporate exclude IRD 5K for BSA 2/010001.
Name) must be present under the
following conditions: if the issuer
account range product type is a 2
for commercial, if DE 043 (Card
Acceptor Name/Location), subfield
6 (Card Acceptor Name/Location),
merchant country code is USA.
• Collection Only
• Reversals
Modified Edit—PDS 0505 (Passenger Name)


1036 The Clearing Platform must ensure This edit will be modified to add
that if DE 26 (Card Acceptor IRD 5N.
Business Code [MCC]) is Passenger
• Process code 00
Railway and PDS 0158 (Business
Activity ), subfield 4 (Interchange • Must be US
Rate Designator) is a specified • Must be MCC type R
interchange program, then PDS
0505 (Passenger Name), PDS 0506
(Ticket Number) and PDS 0507
(Issuing Carrier) must be present.
• Financial Detail Addendum/1644/696

Clearing
Modified Edit—PDS 0505 (Passenger Name)


Business Code [MCC]) is Airline
• Process code 00
and PDS 0158 (Business Activity ),
subfield 4 (Interchange Rate • Must be US
Designator) is a specified • Must be MCC type A
0505 (Passenger Name), PDS 0506
(Ticket Number) and PDS 0507
(Issuing Carrier) must be present.

Clearing
Modified Edit—PDS 0520 (Travel Date)


that if an addendum is provided IRD 5N.
where PDS 0501 (Transaction
• Process code 00
Description), subfield 1 (Usage
Code) contains value 01 • Must be US
(Passenger Transport Detail) and • Must be MCC type R
PDS 0501, subfield 2 (Industry
Record Number) contains either
value 001 (Trip Leg Data) or value
002 (Rail Data), then:
• If the Trip Leg Data, the
following fields must be
provided: PDS 0520 (Travel
Date), PDS 0521 (Carrier Code),
PDS 0522 (Service Class Code),
PDS 0523 (City of Origin/
Airport Code), PDS 0524 (City
of Destination/Airport Code)
• If Rail Data, the following fields
must be provided: PDS 0505
(Passenger Name), PDS 0520
(Travel Date), PDS 0664 (Start
Station), PDS 0665 (Destination
Station), PDS 0756 (Passenger
Description), subfield 3 (Class)
• Financial Detail Addendum/1644

Clearing
Modified Edit—PDS 0520 (Travel Date)


Business Code [MCC]) is Airline
• Process code 00
and PDS 0158 (Business Activity),
Designator) is a specified • Must be MCC type A
0520 (Travel Date), PDS 0521
(Carrier Code), PDS 0522 (Service
Class Code), PDS 0523 (City of
Origin/Airport Code), PDS 0524
(City of Destination/Airport Code)
must be present.

Clearing
Modified Edit—PDS 0544 (Rental Agreement Number)

This edit will be modified to add IRD 5N (Business Level 5 T&E Rate).

0928 The Clearing Platform must ensure that if DE This edit will be modified to add IRD
26 (Card Acceptor Business Code [MCC]) is a 5N.
vehicle rental MCC and PDS 0158 (Business
• Process code 00 and 18
Activity ), subfield 4 (Interchange Rate
Designator) contains a specified interchange • Must be US
program, then the following must be present: • Must be MCC type V
PDS 0544 (Rental Agreement Number)

PDS 0545 (Rental Name)
PDS 0546 (Rental Return City)
PDS 0547 (Rental Return State/Province)
PDS 0548 (Rental Return Country)
PDS 0549 (Rental Return Location)
PDS 0550 (Rental Return Date)
PDS 0551 (Rental Check-Out Date)
PDS 0552 (Customer Service Number)
Collection Only and Reversal messages are excluded from this edit.

Clearing
Modified Edit—PDS 0552 (Customer Service Toll-Free [800] Number)


Business Code [MCC]) is Lodging
• Process code 00
and PDS 0158 (Business Activity),
Designator) is a specified • Must be MCC type H
0552 (Customer Service Toll-Free
[800] Number), PDS 0574 (Arrival
Date), PDS 0575 (Departure Date),
PDS 0576 (Folio Number), and PDS
0577 (Property Telephone Number)
must be present.
Modified Edit—PDS 0595 (Card Acceptor Type)

Mastercard will modify this edit to exclude the edit for U.S. Region transactions submitted
with IRD E6 for BSA 2/010001.

1023 PDS 0595 (Card Acceptor Type) Exclude the edit for transactions
must be provided if the issuer submitted with IRD E6.
account range product type is
commercial and DE 043, subfield 6
(Merchant Category Code) is USA.
• Reversals
• IRD E6 for BSA 2/010001

Clearing
Modified Edit—PDS 0595 (Card Acceptor Type)

Mastercard will modify this edit to exclude the edit for U.S. Region transactions submitted
with IRD E6 for BSA 2/010001.

2277 When a Corporate Card Common Exclude the edit for U.S. Region
Addendum is present, then PDS transactions submitted with IRD
0595 (Card Acceptor Type) and E6.
PDS 0597 (Total Tax Amount) must
be present. Fleet transactions
(Product Code = MCF) at fuel
location (CAB Program FT01) are
excluded from this edit.
• Collection Only
• Reversals
• IRD E6 for BSA 2/010001
Modified Edit—PDS 0595 (Card Acceptor Type), subfield 1 (Business Type)

2/010001.

that PDS 0595 (Card Acceptor exclude IRD 5K for BSA 2/010001.
Type), subfield 1 (Business Type
Code) cannot be value 2 (Not
Known) if the issuer account range
product type is value 2 for
commercial and if DE 043 (Card

Clearing
Modified Edit—PDS 0595 (Card Acceptor Type), subfield 5 (Business Type Provided
Code)
Mastercard will modify this edit to include new IRD 5K (Business Level 5 Standard).

that if PDS 0595 (Card Acceptor include IRD 5K.
• Must be US
Provided Code) is present and
contains value R (Card acceptor
refused to provide business type),
then PDS 0595, subfield 1
(Business Type) must contain value
2 (Not known).
Code)

2436 The Clearing Platform must ensure his edit will be modified to include
that if PDS 0595 (Card Acceptor IRD 5K.
• Must be US
Provided Code) is present, it must
not contain value N (Business type
was not provided.).

Clearing
Code)
2/010001.

that if PDS 0595 (Card Acceptor exclude IRD 5K for BSA 2/010001.
Provided Code) is present it must
contain value Y (Business type is
provided) if the issuer account
range product type is value 2 for
commercial and if DE 043 (Card
Provided Code)

that if PDS 0596 (Card Acceptor include IRD 5K.
Tax ID), subfield 2 (Card Acceptor
• Must be US
Tax ID Provided Code) is present, it
must not contain value N (Business
type was not provided.).

Clearing
Provided Code)
2/010001.

that if PDS 0596 (Card Acceptor exclude IRD 5K for BSA 2/010001.
Tax ID), subfield 2 (Card Acceptor
Tax ID Provided Code) is present, it
must contain value Y (Card
Acceptor Tax ID provided) if the
issuer account range product type
is value 2 for commercial and if DE
043 (Card Acceptor Name/
Location), subfield 6 (Card
Acceptor Name/Location),
Modified Edit—PDS 0597 (Total Tax Amount)

This edit will be modified to add IRD 5B (Business Level 5 Data Rate I).

1137 The Clearing Platform will ensure that, if PDS This edit will be modified to add IRD
0158 (Business Activity), subfield 4 5B.
(Interchange Rate Designator) contains an
• Process code 00 and 18
applicable IRD, then PDS 0597 (Tax Amount)
must be present except if the transaction is a • Must be US
fuel location (MCC is equal to 4468, 5541,
5542, 5499, 5983, 7511, 9752, 4111, 4131,
4215, 4784, 8211, 8220, 8398, 8661, 9211,
9222, 9311, 9399, 9402) or MPG transaction.
• Collection Only
• Reversals

Clearing
Modified Edit—PDS 0597 (Total Tax Amount), Subfield 1 (Total Tax Amount)
This edit will be modified to include IRD 5B (Business Level 5 Data Rate I).

2456 The Clearing Platform will ensure that PDS This edit will be modified to add IRD
0597 (Total Tax Amount), subfield 1 (Total Tax 5B.
Amount) for Corporate Common Data
• Must be US
Addendums cannot be equal to zero.
• Collection Only
• Transactions for product codes TNF, MGF, MNF, MRK, MPK
Modified Edit—PDS 0597 (Total Tax Amount), Subfield 1 (Total Tax Amount)
This edit will be modified to add RD 5B (Business Level 5 Data Rate I).

2461 The Clearing Platform must ensure that the This edit will be modified to add IRD
Total Tax Amount (PDS 0597, subfield 1) must 5B.
be .1 Percent through 30 Percent of the value
• Must be US
in DE 4 (Amount, Transaction). This edit is not
to be performed if PDS 0686 (Tax Exempt
Indicator) is present. This edit is not to be
performed if the transaction is any Commercial
Product at a fuel location (MCC is equal to
4468, 5541, 5542, 5499, 5983, or 9752).
• Collection Only


For Quarterly Mastercard Reporting
Mastercard will update the Clearing Transaction Investigator to include the new values Q and
R in DE 38, position 6.

Question Answer
1. Does this enhancement indicate the Please refer to Life Cycled CAB Programs,
restaurant MCC 5812 is included for Travel & Descriptions, and Associated MCCs where it
Entertainment category? states that TE02 is being removed and TE01 is
being added. This adjustment in CAB codes will
add the restaurant MCC 5812 to T&E.
2. Where should we send additional questions If you have a customer support question, send to
about this announcement? customer support email address with Release
19Q2 in the subject line; this helps us route them
appropriately and analyze for patterns.
3. Any time you are introducing a new US Announcement 2053—U.S. Region Interchange
commercial interchange program, getting the Programs and Rates was published 1 November
actual rates themselves are crucial; if there is 2018.
any way that the rates could be available early
February or January we would appreciate that.

AN 2121—Authorization of Purchase Returns
Chapter 17 AN 2121—Authorization of Purchase Returns

In a future release Mastercard will introduce requirements to support authorization request
messages when initiated by a merchant during purchase return (or refund) transaction processing.
AN 2121—Authorization of Purchase Returns.............................................................................275

Version History............................................................................................................................275
At-A-Glance................................................................................................................................276
Overview.................................................................................................................................... 276
Customer Impact........................................................................................................................ 278
Enhancements............................................................................................................................ 279
Platform Impact.......................................................................................................................... 280
DE 3—Processing Code..................................................................................................... 281
DE 3—Processing Code..................................................................................................... 281


In a future release Mastercard will introduce requirements to support authorization request
messages when initiated by a merchant during purchase return (or refund) transaction
processing.
Version History

11 Dec 2018 Removed the Attention-warranted (Network-related)— At-A-Glance
Acquirer and Network Mandate—Issuer from the At-a-
Glance table as the AN 2121—Authorization of Purchase
Returns effort has been modified to be a testing effort only
for Release 19.Q2, with the planned implementation to be
announced in a future release.
Updated the Effective Dates for the Dual Message System At-A-Glance
(Authorization) and Single Message System to reflect that
the authorization of purchase return requirements will be
implemented in a future release.
Modified the Overview section to reflect that Mastercard will Overview
implement refund transaction authorization requirements in
a future release. However, for those customers that choose
to enhance their systems to support authorization for refund
transactions in advance, testing will be available in Release
19.Q2.
Updated the Customer Impact section to indicate that Customer Impact
testing is recommended so customers can prepare for the
future introduction of refund transaction authorization
requirements.
Modified the Enhancements section to indicate that Enhancements
customers are recommended to prepare for the future
introduction of refund transaction authorization
requirements.
Updated the Application notes for CIS DE 3 (Processing Subfield 1—
Code), subfield 1 (Cardholder Transaction Type Code) to Cardholder
indicate that value 20 (Purchase Return/Refund) will be Transaction Type
allowed for Visa gateway capabilities to support the Code
authorization of returns or refunds effective with Release
19.Q2.

At-A-Glance
At-A-Glance

Release: 19.Q2
Region: All
Action Indicator:
Effective Date: Dual Message System (Authorization): Future
Single Message System: Future
Important
Mastercard will introduce requirements to support authorization request messages when
initiated by a merchant during a purchase return transaction in a future release. For those
customers that choose to enhance their systems to support authorization for refund
transactions in advance, test scripts will be available in Release 19.Q2 for both acquirers and
issuers to confirm that they can submit and receive transactions with value 20 in DE 3
(Processing Code), subfield 1 (Cardholder Transaction Type Code).
Overview
Background
A refund transaction is initiated by a merchant to credit funds to a Mastercard, Debit
Mastercard, or Maestro cardholder’s account for returned products, canceled services, or a
price adjustment related to a prior purchase.


Refund transactions to a Mastercard, Debit Mastercard, or Maestro card do not require issuer
authorization, and such authorization requests are rarely submitted by merchants. Some
issuers do not support receipt of financial transaction request transactions with processing
code 20. Often, the issuer is not aware that a merchant has given a refund to a cardholder
until the issuer receives the First Presentment/1240 or Financial Transaction Advice/0220
message. In the meantime, cardholders may inquire with the merchant, the issuer, or both,
about the status of the expected refund, which can result in unnecessary “Credit Not
Processed” chargebacks.

For Release 19.Q2, Mastercard will make issuer and acquirer test scripts available so that
customers and their service providers may prepare for the future introduction of refund
transaction authorization requirements. Mastercard recommends that Dual Message System
(Authorization) and Single Message System acquirers prepare to send authorization request
messages and to pass the issuer responses to their merchants.
In a future release, Mastercard will require that refund transactions submitted for
authorization are identified in DE 3 (Processing Code), subfield 1 (Cardholder Transaction Type
Code) with a value as follows:
• 20 (Purchase Return/Refund) in the Dual Message System (Authorization)
• 20 (Refund/Correction) in the Single Message System
Mastercard also recommends that issuers prepare to accept authorization messages for refund
transactions involving a Mastercard, Debit Mastercard, or Maestro card, and provide a valid
approval or decline response code in DE 39 (Response Code) using business logic based on the
standing of the account in the issuer's card management system.
Why Mastercard is Implementing These Enhancements

In a future release, Mastercard will introduce refund authorization support to provide all
parties visibility to pending refund activity and reduce refund-related customer service burdens
on merchants, acquirers, and issuers.
Announcements
Refer to the previously published announcements for more information:
• “AN 1430—Revised Standards—Online Authorization of Refund Transactions”

Customer Impact
Reference Manuals
processing:
manuals.
Customer Impact
This announcement affects the indicated customers and platforms.

the future introduction of refund transaction processing requirements.

Message System:

Enhancements
Enhancements
Dual Message System (Authorization)—Acquirers

Mastercard recommends that acquirers prepare their systems and procedures to support any
payment card type for which a merchant initiates a refund transaction authorization request.
Refund transactions are identified in DE 3 (Processing Code), subfield 1 (Cardholder
Transaction Type Code) with a value of 20 (Purchase Return/Refund).
Mastercard recommends that acquirers identify Authorization Request/0100 messages for
refund transactions as final authorization by using:
• DE 61 (Point-of-Service [POS] Data), subfield 7 (POS Transaction Status) = 0 (Normal
Request)
• DE 48 (Additional Data), subelement 61 (POS Data, Extended Condition Codes), subfield 5
(Final Authorization Indicator) = 1 (Final Authorization)
Cryptography data is not mandatory for refund transactions with a processing code value of
20. However, Mastercard will validate the cryptography data if it is provided, including EMV
chip-related data and Mastercard Digital Enablement Service (MDES) tokens. Cryptography
data should only be present if the refund transaction has been initiated through the dip or tap
of a card or contactless-enabled access device at a POS terminal.

Issuers are recommended to prepare their systems and procedures to receive and respond to
Authorization Request/0100 messages for refund transactions.

Mastercard recommends that acquirers support any payment card type for which a merchant
initiates a refund transaction authorization request. Refund transactions are identified in DE 3
(Processing Code), subfield 1 (Cardholder Transaction Type Code) with a value of 20 (Refund/
Correction).
Single Message System—Issuers

Issuers are recommended to prepare their systems and procedures to receive and respond to
Financial Transaction Request/0200 messages for refund transactions.

Platform Impact
Platform Impact
Dual Message
Message Flows
Message Layouts
IPM MPE
Interchange

and Associated MCCs
Edits
Error Numbers
Pricing/Fees
Reports
Bulk Files
Forms
Reporting
SAFE

Manager

Table File

Platform Impact

DE 3—Processing Code
DE 3 (Processing Code) describes the effect of a transaction on the customer account and the
type of accounts affected.
Subfield 1—Cardholder Transaction Type Code
DE 3, subfield 1 (Cardholder Transaction Type Code) describes the specific transaction type.
Values
Cardholder Account MC NP VI TE MS CI
Credits
20 = Purchase Return/ √ √ √ √
Refund
Application Notes
Effective with Release 19.Q2, value 20 will be allowed for Visa gateway transactions to
support the authorization of returns or refunds.
The Dual Message System (Authorization) identifies refund transactions in DE 3, subfield 1
(Cardholder Transaction Type Code) with a value of 20 (Purchase Return/Refund). Mastercard
requires that issuers receive and respond to refund transactions involving a Mastercard, Debit
Mastercard, or Maestro card.

DE 3—Processing Code
DE 3 (Processing Code) is a series of digits used to describe the effect of a transaction on the
customer account and the type of accounts affected.
Subfield 1—Cardholder Transaction Type Code
DE 3, subfield 1 (Cardholder Transaction Type Code) describes the specific transaction being
performed.
Application Notes
The Single Message System identifies refund transactions in DE 3, subfield 1 (Cardholder
Transaction Type Code) with a value of 20 (Refund/Correction). Mastercard requires that
issuers receive and respond to refund transactions involving a Debit Mastercard or Maestro
card.

AN 2122—Introduction of Mastercard Digital Transaction Insights Service
Chapter 18 AN 2122—Introduction of Mastercard Digital

Transaction Insights Service
Mastercard is introducing Mastercard Digital Transaction Insights, a service that will replace the
existing Mastercard Assurance IQ service and provide issuers with improved data on card-not-
present transactions submitted by merchants participating in EMV 3-D Secure, the Mastercard
Identity Check Authentication Network.
AN 2122—Introduction of Mastercard Digital Transaction Insights Service................................... 283

Version History............................................................................................................................283
At-A-Glance................................................................................................................................283
Overview.................................................................................................................................... 284
Customer Impact........................................................................................................................ 286
Enhancements............................................................................................................................ 290
Platform Impact.......................................................................................................................... 290
Authorization..............................................................................................................................291

AN 2122—Introduction of Mastercard Digital Transaction Insights

Service
Mastercard is introducing Mastercard Digital Transaction Insights, a service that will replace the
existing Mastercard Assurance IQ service and provide issuers with improved data on card-not-
present transactions submitted by merchants participating in EMV 3-D Secure, the Mastercard
Identity Check Authentication Network.
Version History

Questions
At-A-Glance

Brands: Mastercard®, Debit Mastercard®, Maestro® (Europe only)
Release: 19.Q2
Region: All
Action Indicator:
Attention warranted (Network-related)—Issuer

Overview
Effective Date: Dual Message System (Authorization) and Single Message System: Varies by
Region
18 January 2019 (19.Q1)—Acquirers and issuers in the U.S. region
12 April 2019 (19.Q2)—Acquirers and issuers in Europe
January 2020—All other regions
Overview
Background
With the introduction of the Assurance IQ service (Global Operations Bulletin, No. 10, 1
October 2015) and the Decision Intelligence service (Global Operations Bulletin, No. 4, 1 April
2016), Mastercard introduced solutions that assisted issuers with their authorization decisions
of approving genuine transactions and declining fraudulent ones.
With the Digital Transaction Insights service, the original objectives introduced by Assurance IQ
and Decision Intelligence remain the same for both issuers and merchants—to increase
genuine approvals and reduce false declines. However, with the Digital Transaction Insights
service, merchants will pass consumer account, device, and other valuable information as part
of the EMV 3-D Secure standard, and who will no longer need to use a specific Mastercard
Application Program Interface (API).

Mastercard currently offers the Assurance IQ service which enables merchants to share
electronic commerce (e-commerce) data with issuers in card-not-present (CNP) environments.
Assurance IQ enables issuers to refine their authorization decisions with the goal of approving
genuine transactions and declining fraudulent ones.
What Mastercard Is Going To Do

Mastercard is introducing Digital Transaction Insights, a service that will enhance and replace
the existing Assurance IQ service and provide issuers with improved data on card not present
transactions submitted by merchants participating in the Mastercard Identity Check
Authentication Network. To minimize the processing impact with this new service, Mastercard
will use the existing data elements currently used with the Assurance IQ service.


Recent enhancements in technology, artificial intelligence and the EMV 3-D Secure standard
have enabled Mastercard to make enhancements to advances in the Decision Intelligence
product suite. Mastercard’s Digital Transaction Insights service can offer the issuer an improved
risk assessment, enabling issuers to make more advanced and intelligent risk-based
authorization decisions.
Mastercard Digital Transaction Insights integrates the authentication and authorization
platforms to help eliminate the differences that exist between card present and e-commerce
approval/fraud rates while facilitating a better customer experience. Digital Transaction
Insights is designed to enable Mastercard to provide additional information about a
transaction to help the issuer make an approval decision. Digital Transaction Insights leverages
the Mastercard Identity Check Program and EMV 3-D Secure standardization and technology
infrastructure to provide real-time intelligence to issuers. Mastercard develops insights and a
Risk Assessment with a proprietary 3-D Secure-enabled Risk Based Authentication (RBA)
model and delivers these to the issuer in authorization decision processing.
NOTE: Merchants will have to utilize the EMV 3D-Secure standard for Digital Transaction
Insights service to be available for issuers.
Announcements
• “Announcing MasterCard Decision Intelligence,” Global Operations Bulletin, No. 4 , 1 April
2016
• “Announcing Mastercard Assurance IQ,” Global Operations Bulletin, No. 10, 1 October
2015
• “AN 1630—AAV Verification Service Enhancement,” Release 18.Q2
Reference Manuals
processing:
• Mastercard Identity Check Program Guide

Customer Impact
manuals.
Customer Impact

Attention warranted (Network-related)—Merchants and acquirers will only need to submit
EMV 3DS transactions in order for Digital Transaction Insights service to be available for
issuers.
Acquirers will need to be enrolled in the Mastercard Identity Check Authentication Network to
send EMV 3DS transactions. For enrollment details, refer to the Mastercard Identity Check
Program Guide or the Mastercard Identity Check Onboarding Guide for 3-D Secure Acquirers,
Merchants, and Service Providers.
Attention warranted (Network-related)—Single Message debit Mastercard issuers must be
prepared to support the existing data elements and fields identified in the Enhancements
section of this announcement.
Mastercard will use existing data elements that already leverage the position, format and
structure of the existing Assurance IQ service for the new service. Consequently, since issuers
and processors were required to be able to receive these data elements as part of the 2016
Global Safety and Security Roadmap, additional development should not be required to
support this new service.
Insights are provided in Data Element 48, Subelement 56. Issuers may need to integrate these
values into their processing. Issuers that already receive Assurance IQ information may need to
update their systems to reflect changes to assessment and reason codes (see reason code
detail below).
Testing recommended—Mastercard recommends that issuers not participating in the
Assurance IQ service perform testing for the Digital Transaction Insights service.


Customer Impact
Message System:
Digital Transaction Insights Process Flow

The following diagrams provide an overview of the process flow of the Digital Transaction
Insights service from authentication into authorization messages.
Through the use of the “Data Only” message code, merchants may submit the EMV 3DS data
without requesting authentication. The Data Only process gets its name from the option for
merchants to submit the data via the EMV 3DS rails, but not request authentication.

Customer Impact
Mastercard will run all EMV 3DS transactions through the Mastercard Risk Based
Authentication (RBA) model.
Authorization requests for which an EMV 3DS transaction was submitted by the merchant will
include a risk assessment in existing security fields (DE 48, subelement 56, subfields 1–2). The
issuer may consider these insights during the authorization decision process.
The data will be passed in Digital Transaction Insights service data fields (formerly used for
Assurance IQ) and will have a similar structure and intent as follows:
• Risk level 0–9 represents the Mastercard Authentication Risk Model assessment, from 0 as
lowest to 9 as highest risk (contained in DE 48, subelement 56, subfield 2, position 1).
NOTE: Be aware of the change from Assurance IQ assessment where 9 represented the
greatest assurance or trust.
• Reason code 1 using values that reflect the key, anchor variables that drove the risk
assessment for the transaction (contained in DE 48, subelement 56, subfield 2, position 2).
• Reason code 2 being a pass-through merchant assessment (select merchants can supply
assessment) and contained in DE 48, subelement 56, subfield 2, position 3.
The risk assessment will be the reference for the issuer risk and fraud management
decisioning, and the reason code will offer a more specific view about the source of the
Mastercard risk analysis, with values from A–Z representing these reasons, with A as the
highest risk to Z as the greatest confidence. Refer to the following table for the current list of
Digital Transaction Insights reason codes (contained in subfield 2, position 2 in the above
example).
Code Reason Code Description
A Risk Event - Suspicious Account Activity
B Risk Event - Unknown Device/Account Relationship
C Risk Event - Device or Profile information associated with fraud

Customer Impact
Code Reason Code Description
D Risk Event - Recent High Risk change to Device or Profile information
E Risk Event - Recent change to Device or Profile Information
F Risk Event - PAN associated with fraud event
G New Account or Insufficient Data
H Merchant/Acquirer: Merchant (fraud) risk high (assessed by Mastercard)
I Merchant/Acquirer: Merchant (fraud) risk low (assessed by Mastercard)
J Environment: Good/Known IP
K Cardholder: Billing address - prior history established
L Cardholder: Email address - prior history established
M Cardholder: Phone Number - prior history established
N Cardholder: Shipping address - prior history established
O Cardholder: Card number (PAN) behavior established high trust in the current transaction
P Environment: Device known
Q Environment: Account established on Device
R Environment: Session - Trusted/normal/innocent session (no man in the middle attack/no

bot, not suspicious account activity)
S More than one Cardholder category established
T More than one Merchant/Acquirer category established
U More than one Environment category established
V Co-occurring established link between cardholder and Merchant/Acquirer
W Co-occurring established link between cardholder and Environment
X Co-occurring established link between Merchant/Acquirer and Environment
Y All three categories established
Z VIP, Known Customer (Merchant Submitted)
The above codes depict a potential list of reason codes and an appropriate ordering from
negative to positive. This list may be further refined. Reason codes A–H reflect riskier, or less
information while reason codes I–Z reflect positive information.
NOTE: Mastercard will communicate additional fields in future publications as necessary.

Enhancements
Enhancements
Dual Message System (Authorization) and Single Message System—Issuer

Mastercard will introduce the Digital Transaction Insights service to replace the existing
Assurance IQ service.
All issuers must be prepared to support the following existing fields and new values for the
Digital Transaction Insights service:
• DE 48, subelement 56 (Security Services Additional Data for Issuers)
– Subfield 1 (Security Services Indicator)
– Subfield 2 (Security Services Data)
• DE 48 (Additional Data—Private Use), subelement 71 (On-behalf Services), subfield 1 (On-
behalf Services) value 18C (Expert Monitoring Fraud Scoring Service was performed
successfully)
• DE 48, subelement 75 (Fraud Scoring Data),
– Subfield 1 (Fraud Score) default value 000.
– Subfield 2 (Score Reason Code) default value 00
– Subfield 3 (Rules Score)
– Subfield 4 (Rules Reason Code 1)
– Subfield 5 (Rules Reason Code 2)
NOTE: Merchants and acquirers will only need to submit EMV 3DS transactions in order for
Digital Transaction Insights service to be available for issuers.
Platform Impact
Dual Message
Message Flows
Message Layouts
IPM MPE

Authorization
Dual Message
Interchange

and Associated MCCs
Edits
Error Numbers
Pricing/Fees
Reports
Bulk Files
Forms
Reporting
SAFE

Manager

Table File
Authorization



Authorization
Subelement 56—Security Services Additional Data for Issuers
DE 48, subelement 56 (Security Services Additional Data for Issuers) supports Mastercard
embedded security services for issuers. Issuers can receive up to 16 instances of subelement
56. Each instance has the same format for each service. Issuers must code to receive the 16
instances that the service supports.
Subelement 56—Valid Subfield 1 and Subfield 2 Value Combinations
Following is the valid DE 48, subelement 56, subfield 1 (Security Services Indicator) and
subfield 2 (Security Services Data) value combinations.
Service Data Content for Decision Intelligence Service—Digital Transaction Insights

Feature
Following is the Service Data Content for the Digital Transaction Insights Feature of the
Decision Intelligence service.
Subfield 2 (an-3)
Subfield 1 (an-3) Position 1 Position 2 Position 3
Security Services
Indicator Risk Level Reason Code 1 Reason Code 2
AIQ (Digital 0–9 where higher The following codes apply to both Reason Code fields 1
Transaction Insights) values indicate and 2, where:
higher degree of risk.
• Position 2 = a Mastercard-determined reason code
• Position 3 = a merchant-determined reason code
NOTE: This information is subject to change.
Reason Description
Code
B Risk Event - Unknown Device/Account
Relationship
C Risk Event - Device or Profile information
associated with fraud
D Risk Event - Recent High Risk change to
Device or Profile information
E Risk Event - Recent change to Device or
Profile Information

Authorization
Subfield 2 (an-3)
Security Services
H Merchant/Acquirer: Merchant (fraud) risk
high (assessed by Mastercard)
I Merchant/Acquirer: Merchant (fraud) risk
low (assessed by Mastercard)
K Cardholder: Billing address - prior history
established
L Cardholder: Email address - prior history
established
M Cardholder: Phone Number - prior history
established
N Cardholder: Shipping address - prior history
established
O Cardholder: Card number (PAN) behavior
established high trust in the current
transaction
R Environment: Session - Trusted/normal/
innocent session (no man in the middle
attack/no bot, not suspicious account
activity)
S More than one Cardholder category
established
T More than one Merchant/Acquirer category
established
U More than one Environment category
established
V Co-occurring established link between
cardholder and Merchant/Acquirer
W Co-occurring established link between
cardholder and Environment

Subfield 2 (an-3)
Security Services
X Co-occurring established link between
Merchant/Acquirer and Environment
NOTE: The above codes depict a potential list of reason codes and an appropriate ordering
from negative to positive. This list may be further refined. Reason codes A–H reflect riskier, or
less information while reason codes I–Z reflect positive information.


Subelement 56—Security Services Additional Data for Issuers
DE 48, subelement 56 (Security Services Additional Data for Issuers) supports Mastercard
embedded security services for issuers. Issuers can receive up to 16 instances of subelement
56. Each instance has the same format for each service. Issuers must code to receive the 16
instances that the service supports.
Subelement 56—Valid Subfield 1 and Subfield 2 Value Combinations
Following is the valid DE 48, subelement 56, subfield 1 (Security Services Indicator) and
subfield 2 (Security Services Data) value combinations.
Service Data Content for Decision Intelligence Service—Digital Transaction Insights

Feature
Following is the Service Data Content for the Digital Transaction Insights Feature of the
Decision Intelligence service.

Subfield 2 (an-3)
Security Services
AIQ (Digital 0–9 where higher The following codes apply to both Reason Code fields 1
Transaction Insights) values indicate and 2, where:
higher degree of risk.
• Position 2 = a Mastercard-determined reason code
• Position 3 = a merchant-determined reason code
NOTE: This information is subject to change.
Reason Description
Code
B Risk Event - Unknown Device/Account
Relationship
C Risk Event - Device or Profile information
associated with fraud
D Risk Event - Recent High Risk change to
Device or Profile information
E Risk Event - Recent change to Device or
Profile Information
H Merchant/Acquirer: Merchant (fraud) risk
high (assessed by Mastercard)
I Merchant/Acquirer: Merchant (fraud) risk
low (assessed by Mastercard)
K Cardholder: Billing address - prior history
established
L Cardholder: Email address - prior history
established
M Cardholder: Phone Number - prior history
established

Subfield 2 (an-3)
Security Services
N Cardholder: Shipping address - prior history
established
O Cardholder: Card number (PAN) behavior
established high trust in the current
transaction
R Environment: Session - Trusted/normal/
innocent session (no man in the middle
attack/no bot, not suspicious account
activity)
S More than one Cardholder category
established
T More than one Merchant/Acquirer category
established
U More than one Environment category
established
V Co-occurring established link between
cardholder and Merchant/Acquirer
W Co-occurring established link between
cardholder and Environment
X Co-occurring established link between
Merchant/Acquirer and Environment
NOTE: The above codes depict a potential list of reason codes and an appropriate ordering
from negative to positive. This list may be further refined. Reason codes A–H reflect riskier, or
less information while reason codes I–Z reflect positive information.


Question Answer
1. This announcement uses the terms EMV 3DS Yes, this announcement only applies to the
and 3D-Secure, does this usage indicate this Mastercard Identity Check program and the EMV
only applies to the 3DS 2.0 format only? 3-D Secure format, and does not apply to Secure
Code nor the 3DS 1.0 format.
2. Mastercard currently allows up to 16 No. We support several elements that can occur
occurrences of DE 48, subelement 56 (Security multiple times to represent multiple results for
Services Additional Data for Issuers) within DE one or more services. DE 48, subelements 51 and
48. Are there any plans to combine this into 71 are two other examples. Variable length fields
one large fixed length element? that support “up to” a maximum number of
occurrences of data makes more efficient use of
message and data space by providing only the
data needed without extraneous filler area.
3. Will all occurrences of DE 48, subelement 56 Typically, occurrences of a recurring element are
be present in a request message sequentially, presented sequentially with no other elements
with no other element not grouped together? not grouped together. For example, if a
transaction contains 6 occurrences of DE 48,
subelement 56, all 6 will be grouped together.
However, it is technically possible for recurring
subelements to be not grouped together and
therefore message recipients must be capable of
supporting this data condition.
4. If an issuer chooses to make use of the Issuers do carry a level of risk when approving
information provided by the Digital any transaction regardless of the presence of
Transaction Insights service in DE 48, scoring information. Digital Transaction Insights
subelement 56, does the issuer still assume provides issuers with additional information to
transactional risk? assist in making better-educated authorization
decisions, by providing score information
generated using EMV 3-D Secure technology and
related data generated by merchants that
support Mastercard Identity Check. Issuers can
further reduce their card-not-present transaction
risk by enrolling in Mastercard Identity Check.

Question Answer
5. Does Digital Transaction Insights apply only to No. This is not dependent on EMV 3-D Secure
fully-authenticated EMV 3-D Secure authentication or any particular SLI values. For
transactions or only for transactions transactions initiated by a merchant that uses
containing certain Security level Indicator (SLI Mastercard Identity Check (regardless of an
values)? issuer’s participation in Identity Check or a
cardholder’s authentication by the service),
Digital Transaction Insights takes EMV 3-D Secure
data into account, scores it and then provides
score data to issuers to help in their authorization
decisioning. Digital Transaction Insights data is
simply incremental intelligence to give better
insight to consumer transaction activity.
6. Must a transaction originate from a merchant Yes. The Digital Transaction Insights service relies
that used Mastercard Identity Check in order on the EMV 3-D Secure data through the
for Digital Transaction Insights to provide Mastercard Identity Check service in a card-not-
score information to the issuer? present transaction in order to provide the Digital
Transaction Insights score data to the issuer.
7. Is any of the Digital Transaction Insights score No. At this time, score information is not sent
information sent back to the acquirer? back to the acquirer.
8. Are merchants being mandated to enroll in, or No. These Digital Transaction Insights
otherwise support Mastercard Identity Check enhancements do not mandate the use of
in Release 19.Q2? Are acquirers being SecureCode or Mastercard Identity Check by
mandated to offer or support Mastercard merchants, nor does this announcement
Identity Check in Release 19.Q2? mandate that acquirers support SecureCode or
Mastercard Identity Check. The new Digital
Transaction Insights service will simply perform
based on the presence of EMV 3-D Secure data
in a transaction when the merchant does support
Mastercard Identity Check.
9. Are any changes being made to DE 48 No. DE 48, subelement 55 contains scoring data
subelement 55 (Merchant Fraud Scoring related to merchants and is not related to Digital
Data)? Transaction Insights processing/scoring. DE 48,
subelement 55 is present only in authorization
and financial response messages to acquirers. It is
never included in request messages sent to
issuers. Conversely, DE 48, subelement 56
contains transaction-related scoring data and is
included only in request messages sent to issuers,
never in response messages sent back to
acquirers.
10. Will the Assurance IQ service continue to be No. The Assurance IQ service will eventually be
supported? decommissioned.

AN 2123—Identification of Tokenized Mastercard Consumer Presented QR Transactions
Chapter 19 AN 2123—Identification of Tokenized

Mastercard Consumer Presented QR Transactions
Mastercard will introduce enhancements to identify and allow the processing of tokenized
Mastercard Consumer Presented QR transactions performed on the Mastercard Network.
AN 2123—Identification of Tokenized Mastercard Consumer Presented QR Transactions.............300

Version History............................................................................................................................300
At-A-Glance................................................................................................................................302
Overview.................................................................................................................................... 302
Customer Impact........................................................................................................................ 305
Enhancements............................................................................................................................ 306
Platform Impact.......................................................................................................................... 308
Authorization..............................................................................................................................309
Edits.......................................................................................................................................310
Clearing......................................................................................................................................312
PDS 0021—Transaction Type Indicator............................................................................... 312
IPM MPE................................................................................................................................ 312
Edits.......................................................................................................................................313
New Edit—PDS 0021 (Transaction Type Indicator)...............................................................313
Error Numbers................................................................................................................... 314
Edits.......................................................................................................................................317

AN 2123—Identification of Tokenized Mastercard Consumer Presented

QR Transactions
Mastercard will introduce enhancements to identify and allow the processing of tokenized
Mastercard Consumer Presented QR transactions performed on the Mastercard Network.
Version History

8 Jan 2019 In Customer Impact, clarified the “Program or service Customer Impact
requirement” language to state that customers that choose
not to process tokenized Mastercard Consumer Presented
QR transactions—rather than customers that do not opt-in
to the processing of tokenized Mastercard Consumer
Presented QR transactions—will not benefit from offering
this emerging payment method.
In Authorization, Edits, made the following updates: Authorization Edits
• Corrected the note in the first edit to reflect that the
Authorization Platform will continue processing the
message if DE 48, subelement 21, subfield 2 is not
present rather than if subfield 2 contains no values.
• In the “When” column of the second edit, corrected the
second condition by removing the reference to MCC
6010 (Member Financial Institution—Manual Cash
Disbursements) and adding a reference to Transaction
Category Code value Z (ATM Cash Disbursement). As a
result, the second condition of the second edit reads as
follows: “DE 18 (Merchant Type) contains MCC 6011
(Member Financial Institution—Automated Cash
Disbursements) or DE 48 (Additional Data—Private Use),
TCC (Transaction Category Code), contains value Z (ATM
Cash Disbursement)”
• In the “When” column of the third edit, removed the
second condition that previously read as follows: “DE 18
(Merchant Type) does not contain MCC 6010 (Member
Financial Institution—Manual Cash Disbursements) or
MCC 6011 (Member Financial Institution—Automated
Cash Disbursements).” The removal of this content is not
marked by a change bar.

Version History

Revised the Data Representation of DE 48, subelement 21 DE 48—Additional
from “n-11; LLVAR” to “n...11; LLVAR” in the following Data
sections of Single Message System, Single Message System
Data Element Definitions, DE 48—Additional Data: Subelement 21—
Acceptance Data
• The “List of DE 48 Subelements” section
• The “Subelement 21—Acceptance Data” section
In Single Message System, Edits, made the following Single Message

updates: System Edits
• Corrected the note in the first edit to reflect that the
Single Message System (not the Authorization Platform)
will continue processing the message if DE 48,
subelement 21, subfield 2 is not present rather than if
subfield 2 contains no values.
• In the “When” column of the second edit, corrected the
second condition by removing the reference to MCC
6010 (Member Financial Institution—Manual Cash
Disbursements) and adding a reference to Transaction
Category Code value Z (ATM Cash Disbursement). As a
result, the second condition of the second edit reads as
follows: “DE 18 (Merchant Type) contains MCC 6011
Disbursements) or DE 48 (Additional Data—Private Use),
TCC (Transaction Category Code), contains value Z (ATM
Cash Disbursement)”
• In the “When” column of the third edit, removed the
second condition that previously read as follows: “DE 18
(Merchant Type) does not contain MCC 6010 (Member
Financial Institution—Manual Cash Disbursements) or
MCC 6011 (Member Financial Institution—Automated
Cash Disbursements).” The removal of this content is not
marked by a change bar.

Questions

At-A-Glance
At-A-Glance

Products & Services: Mastercard Digital Enablement Service
Release: 19.Q2
Region: All
Action Indicator:
Program or service requirement—Acquirer and issuer
Registration Required—Acquirer and issuer
Testing recommended—Acquirer and issuer
Overview
Background
A quick response (QR) code is a matrix barcode that can be used to store data and can be read
by an imaging device such as a camera.
The QR payment is a fast, convenient option for consumers. Consumer-presented QR
transactions originate when a consumer mobile wallet generates a QR code that can be
scanned by a merchant to receive payments.

Overview

Mastercard does not currently support tokenized consumer-presented QR payments.
Existing DE 22 (Point-of-Service [POS] Entry Mode), subfield 1 (POS Terminal PAN Entry Mode),
value 03 (PAN auto-entry via barcode reader) is used for transactions submitted with a
barcode reader.

Mastercard is implementing enhancements to allow customers to properly identify and
process tokenized Mastercard Consumer Presented QR transactions received on the
Mastercard Network. These transactions originate when a consumer mobile wallet generates a
QR code that can be scanned by a merchant to receive payment. Mastercard is implementing
these enhancements in accordance with the EMVCo specifications for Consumer Presented
QR codes.
These enhancements will include:
• Identification of Mastercard Consumer Presented QR transactions by the use of existing
value 03 in DE 22, subfield 1
• Identification of Mastercard Consumer Presented QR terminal capabilities through new
subfield 02 (Additional Terminal Capability Indicator) in DE 48 (Additional Data—Private
Use), subelement 21 (Acceptance Data)
NOTE: DE 48, subelement 21 was introduced with “AN 1626—Introduction of mPOS

Indicators for Software-based Terminals,” Release 18.Q4.
• Introduction of new PDS 0021 (Transaction Type Indicator).


With increasing consumer interest for QR-based payments in certain markets in the Asia/
Pacific region, Mastercard is integrating Consumer Presented QR capabilities into the
Mastercard Cloud-Based Payments (MCBP) product, in accordance with the EMVCo standards
for QR acceptance. These enhancements will help ensure that tokenized Mastercard
Consumer Presented QR transactions are properly identified and securely processed on the
Mastercard Network.
Announcements
• “AN 1626—Introduction of mPOS Indicators for Software-based Terminals,” Release 18.Q4
Reference Manuals
processing:
• Mastercard Digital Enablement Service (MDES) Information Center
• EMV QR Code Specification for Payment Systems (EMV QRCPS): Consumer-Presented Mode
manuals.

Customer Impact
Customer Impact

Program or service requirement—Acquirers and issuers that choose to submit or process
tokenized Mastercard Consumer Presented QR transactions must be prepared to support the
enhancements as described in this announcement. Customers that choose not to process
tokenized Mastercard Consumer Presented QR transactions will not benefit from offering this
emerging payment method.
Registration Required—Acquirers and issuers that choose to submit or process tokenized
Mastercard Consumer Presented QR transactions must contact their CIS or account
representatives.
Testing recommended—Mastercard recommends testing for acquirers and issuers that choose
to submit or process tokenized Mastercard Consumer Presented QR transactions to support
the enhancements described in this announcement.

Message System:

Enhancements
Enhancements
Mastercard is announcing the following enhancements to the Dual Message System
(Authorization and Clearing) and to the Single Message System. These enhancements support
the identification and processing of tokenized Mastercard Consumer Presented QR
transactions received on the Mastercard Network.
Dual Message System (Authorization) and Single Message System—Acquirers

Acquirers supporting merchants that choose to submit tokenized Mastercard Consumer
Presented QR transactions must support:
• The use of existing value 03 (PAN auto-entry via barcode reader) in DE 22 (Point-of-Service
[POS] Entry Mode), subfield 1 (POS Terminal PAN Entry Mode) in Authorization Request/
0100 and Financial Transaction Request/0200 messages.
• The use of Chip data in DE 55 (Integrated Circuit Card [ICC] System-Related Data) for
Mastercard Consumer Presented QR transactions.
• New subfield 02 (Additional Terminal Capability Indicator) in DE 48 (Additional Data—
Private Use), subelement 21 (Acceptance Data) to identify Mastercard Consumer Presented
QR and barcode terminal capabilities in Authorization Request/0100 and Financial
• The revision of the data representation of DE 48, subelement 21 from n...5; LLVAR to n...
11; LLVAR.
• The enablement of DE 22, subfield 1, value 03 for both of the following:
– Balance inquiries (DE 3 [Processing Code], subfield 1 [Cardholder Transaction Type
Code], value 30 [Balance Inquiry])
– Transactions containing chip data (DE 55 [ICC System-Related Data])
NOTE: Acquirers supporting tokenized Mastercard Consumer Presented QR transactions must

be prepared to receive the following, when applicable, in current messages: token-related
data, cryptography validation results, and Payment Account Reference (PAR) values
Dual Message System (Clearing)—Acquirers

Acquirers supporting merchants that choose to submit tokenized Mastercard Consumer
Presented QR transactions must support:
• The use of the existing value M (PAN auto-entry via contactless M/Chip) in DE 22, subfield
7 (Card Data: Input Mode) in First Presentment/1240 messages
• The use of Chip data in DE 55 (Integrated Circuit Card [ICC] System-Related Data) for
Mastercard Consumer Presented QR transactions
• New PDS 0021 (Transaction Type Indicator) in First Presentment/1240 messages
Stand-In and X-Code processing will not be available for Mastercard Consumer Presented QR
transactions. If submitted via Stand-In and X-Code processing, these transactions will be
declined to the acquirer with DE 39 (Response Code), value 05 (Do not honor).

Enhancements
Dual Message System (Authorization) and Single Message System—Issuers

Issuers that choose to process tokenized Mastercard Consumer Presented QR transactions
must support:
• The use of existing value 03 (PAN auto-entry via barcode reader) in DE 22 (Point-of-Service
[POS] Entry Mode), subfield 1 (POS Terminal PAN Entry Mode) in the messages in which it is
already defined.
• New subfield 02 (Additional Terminal Capability Indicator) in DE 48 (Additional Data—
Private Use), subelement 21 (Acceptance Data) to identify Mastercard Consumer Presented
QR and barcode terminal capabilities in the following messages:
– Authorization Request/0100
– Authorization Advice/0120
– Financial Transaction Request/0200
– Financial Transaction Advice/0220
• The revision of the data representation of DE 48, subelement 21 from n...5; LLVAR to n...
11; LLVAR.
NOTE: Issuers supporting tokenized Mastercard Consumer Presented QR transactions must be

prepared to receive the following, when applicable, in current messages: PAN mapped data,
cryptography validation results, and Payment Account Reference (PAR) values
Stand-In and X-Code processing will not be available for Mastercard Consumer Presented QR
transactions. If submitted via Stand-In and X-Code processing, these transactions will be
declined, though Mastercard will not send a decline advice message to issuers.

Issuers that choose to process tokenized Mastercard Consumer Presented QR transactions
must support:
• The use of the existing value M (PAN auto-entry via contactless M/Chip) in DE 22, subfield
7 (Card Data: Input Mode) in First Presentment/1240 messages
• The use of Chip data in DE 55 (Integrated Circuit Card [ICC] System-Related Data) for QR
Code transactions
• New PDS 0021 (Transaction Type Indicator) in First Presentment/1240 messages
– PDS 0021, value 1 (Mastercard Consumer Presented QR) will be present only for QR
Code transactions

Platform Impact
Platform Impact
Dual Message System
Single Message
Message Flows
Message Layouts
IPM MPE √
Interchange

and Associated MCCs
Edits √ √ √
Error Numbers √
Pricing/Fees
Reports
Bulk Files
Forms
Reporting
SAFE

Manager

Table File

Authorization
Authorization


List of DE 48 Subelements
DE 48 subelements are listed in numeric order. Subelements that are specific to a brand
service or program are clearly indicated in the subelement title or description or both.
Subelement ID and Name Data Representation
21 Acceptance Data n...11; LLVAR
Subelement 21—Acceptance Data

DE 48, subelement 21 (Acceptance Data) indicates the merchant terminal’s capability to
support specific programs and services.
Attribute Value
Data Representation n...11; LLVAR
Number of Subfields 2
NOTE: Refer to Release 18.Q4 announcement “AN 1626—Introduction of mPOS Indicators for
Software-based Terminals” for additional information on Usage and Application Notes for
subelement 21.
Subfield 2—Additional Terminal Capability Indicator

DE 48, subelement 21, subfield 2 (Additional Terminal Capability Indicator) identifies
Mastercard Consumer Presented QR and barcode terminal capabilities. This subfield is

Authorization
optional. Customers that have opted to submit or process tokenized Mastercard Consumer
Presented QR transactions are expected to support this subfield.
Attribute Value
Subfield ID n-2 02
Subfield Length n-2 02
Data Field Contents of positions 1–2
Justification N/A
Position 1 Mastercard Consumer Presented

QR Capability Support Indicator

Barcode Capability Support
Indicator
Values Description
0 Not Supported
1 Supported
Subfield 2—Valid Position 1 and Position 2 Value Combinations
Valid Combinations QR Capability Barcode Capability
00 Not supported Not supported
01 Not supported Supported
10 Supported Not supported
11 Supported Supported
Edits
The Authorization Platform will perform the following system edits.
Mastercard will add the following new edits to support this announcement.

Authorization
WHEN... THEN the Authorization Platform...
An Authorization Request/0100 or Authorization Rejects the message and sends the acquirer an
Advice/0120—Acquirer-generated message Authorization Request Response/0110 or
contains DE 22 (Point-of-Service [POS] Entry Authorization Advice Response/0130 message
Mode), subfield 1 (POS Terminal PAN Entry Mode), where:
value 03 (PAN auto-entry via barcode reader)
• DE 39 (Response Code) = 30 (Format error)
and • DE 44 (Additional Response Data) = 048021
DE 48 (Additional Data— Private Use), subelement (indicating the data element in error)
21 (Acceptance Data), subfield 2 (Additional
NOTE: If DE 48, subelement 21, subfield 2 is
Terminal Capability Indicator) is present and does
not present, the Authorization Platform will
not contain any of the valid value combinations of
continue processing the message.
00, 01, 10, or 11
An Authorization Request/0100 message contains Rejects the message and sends the acquirer an
DE 22 (Point-of-Service [POS] Entry Mode), Authorization Request Response/0110 message
subfield 1 (POS Terminal PAN Entry Mode), value where:
03 (PAN auto-entry via barcode reader)
• DE 39 (Response Code) = 58 (Transaction not
and permitted to acquirer/terminal)
DE 18 (Merchant Type) contains MCC 6011
Disbursements) or DE 48 (Additional Data—
Private Use), TCC (Transaction Category Code),
contains value Z (ATM Cash Disbursement)
An Authorization Request/0100 message contains Rejects the message and sends the acquirer an
both of the following: Authorization Request Response/0110 message
where:
• DE 22 (Point-of-Service [POS] Entry Mode),
subfield 1 (POS Terminal PAN Entry Mode), • DE 39 (Response Code) = 58 (Transaction not
value 03 (PAN auto-entry via barcode reader); permitted to acquirer/terminal)
and
• DE 52 (Personal ID Number [PIN] Data)

Clearing
Mastercard will update the Authorization Transaction Investigator tool to support new subfield
02 (Additional Terminal Capability Indicator) in DE 48 (Additional Data—Private Use),
subelement 21 (Acceptance Data).
Clearing

PDS 0021—Transaction Type Indicator

PDS 0021 provides information on the form factor of the terminal device that initiated the
transaction.
Attributes
Data Representation: ans-1; TAGLLL
Tag Field: 0021
Length Field: 3 positions, value = 001
Data Field: Fixed length, 1 position
Subfields: N/A
Justification: N/A
Values
Value Description
1 Mastercard Consumer Presented QR
IPM MPE
Mastercard will add and update IPM MPE tables to support this announcement.
Mastercard will:
• Introduce new IPM MPE Table IP2201T1, which will contain the valid values for new PDS
0021.
• Add new PDS 0021 to IPM MPE Table IP0008T1 (PDS Attribute).

Clearing
Mastercard will include these changes in the 19.Q2 GCMS Parameter Table Layouts.
Edits
announcement.
New Edit—PDS 0021 (Transaction Type Indicator)

This edit validates that, when present, PDS 0021 (Transaction Type Indicator) contains a valid
value.

2873 The Clearing Platform will ensure that PDS 0021 (Transaction Type
Indicator), if present, contains a valid value. Value/Range list table in
IPM MPE OneDay file is IP2201T1.
• Retrieval Request/1644
• Retrieval Request Acknowledgement/1644
• Fee Collection (Retrieval Fee Billing)/1740
• Fee Collection (Handling Fees)/1740
• Fee Collection (Other than Retrieval Fee Billing/Handling Fees)/1740

This edit validates that PDS 0021 (Transaction Type Indicator) is a fixed length of 1 byte.

2874 The Clearing Platform will ensure that PDS 0021 (Transaction Type
Indicator), if present, has a correct length of 001.

Clearing

• Retrieval Request/1644
• Retrieval Request Acknowledgement/1644
• Fee Collection (Retrieval Fee Billing)/1740
• Fee Collection (Handling Fees)/1740
• Fee Collection (Other than Retrieval Fee Billing/Handling Fees)/1740

This edit validates that PDS 0021 (Transaction Type Indicator) is present for a Mastercard
Consumer Presented QR transaction.

2875 If PDS 0021 (Transaction Type Indicator) is present, then the Clearing
Platform will ensure that:
• DE 22 (Point of Service Code), subfield 7 (Card Data: Input Mode)
contains value M (PAN auto-entry via contactless M/Chip); and
• DE 55 (Integrated Circuit Card [ICC] System-Related Data) is present.
Error Numbers
Edit
Error Performed
PDS 0021 2873 PDS0021 TRANSACTION TYPE INDICATOR INVALID, Both

MUST <VALLIST>.

Edit
Error Performed
PDS 0021 2874 PDS0021 TRANSACTION TYPE INDICATOR MUST BE A Both

FIXED LENGTH OF 001.
PDS 0021 2875 PDS0021 TRANSACTION TYPE INDICATOR WHEN Both

PRESENT, THEN DE22S7 MUST BE EQUAL TO “M” AND
DE55 MUST BE PRESENT.
Mastercard will update the Clearing Transaction Investigator tool to support new PDS 0021
(Transaction Type Indicator).


List of DE 48 Subelements
DE 48 subelements are listed in numeric order. Subelements specific to a brand service or
program are clearly indicated in the subelement title or description or both.
Subelement ID and Name Data Representation
21 Acceptance Data n...11; LLVAR
Subelement 21—Acceptance Data

DE 48, subelement 21 (Acceptance Data) indicates the merchant terminal’s capability to
support specific programs and services.
Attribute Value

Attribute Value
Number of Subfields 2
NOTE: Refer to Release 18.Q4 announcement “AN1626—Introduction of MPOS Indicator for

Software Based Terminals” for additional information on Usage and Application Notes for
subelement 21.
Subfield 2—Additional Terminal Capability Indicator

DE 48, subelement 21, subfield 2 (Additional Terminal Capability Indicator) identifies
Mastercard Consumer Presented QR and barcode terminal capabilities. This subfield is
optional. Customers that have opted to submit or process tokenized Mastercard Consumer
Presented QR transactions are expected to support this subfield.
Attribute Value
Subfield ID n-2 02
Subfield Length n-2 02
Data Representation n…2; LLVAR
Data Field Contents of positions 1–2
Justification N/A

QR Capability Support Indicator

Barcode Capability Support
Indicator
Values Description
0 Not Supported
1 Supported
Subfield 02—Valid Position 1 and Position 2 Value Combinations
00 Not supported Not supported

01 Not supported Supported
10 Supported Not supported
11 Supported Supported
Edits
Mastercard will add the following new edits to support this announcement.
A Financial Transaction Request/0200 message Rejects the message and sends the acquirer a
contains DE 22 (Point-of-Service [POS] Entry Financial Transaction Request Response/0210
Mode), subfield 1 (POS Terminal PAN Entry Mode), message where:
DE 48 (Additional Data— Private Use), subelement (indicating the data element in error)
21 (Acceptance Data), subfield 2 (Additional
NOTE: If DE 48, subelement 21, subfield 2 is
Terminal Capability Indicator) is present and does
not present, the Single Message System will
not contain any of the valid value combinations of
continue processing the message.
00, 01, 10, or 11
• DE 39 (Response Code) = 58 (Transaction not
and permitted to acquirer/terminal)
DE 18 (Merchant Type) contains MCC 6011
Disbursements) or DE 48 (Additional Data), TCC
(Transaction Category Code), contains value Z
(ATM Cash Disbursement)

contains both of the following: Financial Transaction Request Response/0210
message where:
• DE 22 (Point-of-Service [POS] Entry Mode),
subfield 1 (POS Terminal PAN Entry Mode), • DE 39 (Response Code) = 58 (Transaction not
value 03 (PAN auto-entry via barcode reader); permitted to acquirer/terminal)
and
• DE 52 (Personal ID Number [PIN] Data)

Question Answer
1. Does new PDS 0021 only need to be included Yes. Mastercard is introducing some Clearing
if a Mastercard Consumer Presented QR edits to help ensure the Mastercard Consumer
transaction contains DE 55? As in, if there is Presented QR transaction contains the correct
no chip data, the Clearing Platform would information (the presence of DE 55 data when
reject such Mastercard Consumer Presented PDS 0021 is present).
QR transactions?
2. From an issuer’s perspective, is this initiative This initiative revolves around the identification
simply about transaction-identification method that will be used by all the parties in the
methods, or are there any other expectations payment ecosystem. It is important to uniquely
for issuers? For example, will there be any identify these transactions so that fraud rules can
fraud rules? be applied to these transactions, as they are
becoming more prominent globally. With these
enhancements, we will—for example—be able
to identify if a transaction is coming from a
merchant that deploys a terminal capable of
these transactions.
3. Why is Mastercard using existing value M in Introducing a new value in DE 22, subfield 7
DE 22, subfield 7 to identify these new would impact all customers globally, and
Mastercard Consumer Presented QR Mastercard did not want to impact the whole
transactions in Clearing? Why not create and ecosystem to support these types of transactions.
support a new DE 22, subfield 7 value of 03? However, Mastercard may introduce a new value
in Clearing with a future release once it sees
more adoption and acceptance of Mastercard
Consumer Presented QR transactions.

Question Answer
4. If an issuer is EMV-ready but does not support It is not possible to perform a Mastercard
tokenization, will these Mastercard Consumer Consumer Presented QR transaction if the issuer
Presented QR transactions work? does not support tokenization.

AN 2124—Revisions to Brazil 7–21 Installment Payment Interchange Structure for Select Merchant Categories
Chapter 20 AN 2124—Revisions to Brazil 7–21 Installment

Payment Interchange Structure for Select Merchant
Categories
Mastercard is completing the modifications to the Brazil intracountry interchange structure for
select merchant categories with changes to the Brazil 7–21 Installment Payment interchange
programs.
AN 2124—Revisions to Brazil 7–21 Installment Payment Interchange Structure for Select

Merchant Categories.................................................................................................................. 321
Version History............................................................................................................................321
At-A-Glance................................................................................................................................321
Overview.................................................................................................................................... 322
Customer Impact........................................................................................................................ 324
Enhancements............................................................................................................................ 325
Platform Impact.......................................................................................................................... 325
Clearing......................................................................................................................................327
Interchange............................................................................................................................327
Interchange Programs........................................................................................................ 327

AN 2124—Revisions to Brazil 7–21 Installment Payment Interchange

Structure for Select Merchant Categories
Mastercard is completing the modifications to the Brazil intracountry interchange structure for
select merchant categories with changes to the Brazil 7–21 Installment Payment interchange
programs.
Version History

At-A-Glance
announcement, action indicators that specify the appropriate action, and the date or dates

Brands: Mastercard®, Maestro®
Release: 19.Q2
Region: Latin America/Caribbean
System: Clearing
Action Indicator:
Attention warranted (Program/service-related)—Acquirers and Issuers in
Brazil
Testing recommended—Acquirers and Issuers in Brazil

Overview
Overview
Background
Mastercard introduced in Release 17.Q3 modifications to interchange programs for non-
installments, new card acceptor business (CAB) programs, and modifications to clearing edits
effective 14 July 2017. Mastercard extended these modifications to include interchange
programs for 2–6 installment payments in Release 18.Q1 effective 19 January 2018.
Release 19.Q2 will be the final phase of this project modifying the interchange programs for
7–21 installment payments.

The CAB program modifications in the Release 17.Q3 announcement, “AN 1008—Revisions
to Brazil Intracountry Interchange Structure for Select Merchant Categories” included these
enhancements:
• Introduction of CAB program BR08 (Brazil Fast Transactions) in IRD KH (Brazil Intracountry
Fast Transactions—7–21 Installment Payments) for all acceptance brands
• Introduction of CAB program BR10 (Other All MCCs in BR07 except MCC 5192 [Books,
Periodicals, and Newspapers]) are present in the following interchange programs for 7–21
installment payments for all acceptance brands: K3, K6, KL, KN, KP, KR, KX, KZ, NC, NF, NI,
NL, and NO
Currently, existing CAB programs BR03 (Brazil Fast Transactions) and BR07 (Brazil Other) are
available for 7–21 installment payments interchange programs.

Mastercard will life cycle existing CAB program BR03 from IRD KH.
Mastercard will life cycle existing CAB program BR07 from these 7–21 Installment Payments
IRDs: K3, K6, KL, KN, KP, KR, KX, KZ, NC, NF, NI, NL, and NO.
As of Release 19Q2, CAB programs BR03 and BR07 are no longer valid for the Brazil
Intracountry BSA 4/076000.
When changes are made to CAB programs, life cycle activity processing is invoked. This allows
reversals and exception items such as chargebacks and retrievals to continue to be processed
until Release 20.Q2 with the original settings, while new activity (such as First Presentments) is
processed using the new settings.


Continuing to deploy the enhancements announced in Releases 17.Q3 and 18.Q1 offering
unique interchange rates for large retailers in Brazil and offering a separate IRD for public
transportation, Mastercard will apply these enhancements to the Brazil 7–21 installment
payments programs. The enhanced structure for installment payments and transportation will
encourage the issuance and acceptance of Mastercard payment products with the purpose of
providing an efficient and safe payment service to consumers and merchants, by increasing
the number of issuers, acquirers, and payment facilitators participating in Mastercard payment
network.
Announcements
• “Revised Brazil Intracountry Interchange Rates for Select Merchant Categories,” Brazil
Interchange Bulletin No. 4, 16 December 2016
• “AN 1052—Revisions to Brazil 2–6 Installment Payment Interchange Structure for Select
Merchant Categories,” Release 18.Q1
• “AN 1008—Revisions to Brazil Intracountry Interchange Structure for Select Merchant
Categories,” Release 17.Q3
Reference Manuals
processing:
• Interchange Manual Latin America and the Caribbean Region
manuals.

Customer Impact
Customer Impact

As described in the Release 17.Q3 announcement “AN 1008—Revisions to Brazil Intracountry
Interchange Structure for Select Merchant Categories”:
• CAB program BR08 (Fast Transactions) was added to IRD KH
• CAB program BR10 (Other. All MCCs in BR07 except MCC 5192 [Books, Periodicals, and
Newspapers]) was added to IRDs: K3, K6, KL, KN, KP, KR, KX, KZ, NC, NF, NI, NL, and NO
Attention warranted (Program/service-related)—Acquirers in Brazil that offer installment
payment services must use of CAB program BR08 in IRD KH and BR10 in Brazil 7–21
Installment Payment interchange programs.
Attention warranted (Program/service-related)—Issuers in Brazil:
• Must support the life cycle of CAB program BR03 from IRD KH
• Must support the life cycle of CAB program BR07 from Brazil 7–21 Installment Payment
interchange programs
Dual Message System acquirers and their processors must submit clearing transactions to
Mastercard in accordance with the interchange structure in place. Transactions that do not
meet the interchange criteria will be rejected.
Testing recommended—Mastercard recommends participating OIs and RIs perform testing in
the Mastercard Test Facility.


Enhancements
Message System:
Enhancements

BR03
Accept BR03 (Brazil Fast Transactions) for life cycle transactions until Release 20.Q2 under IRD
KH (Brazil Intracountry Fast Transactions—7–21 Installment Payments).
CAB program BR03 will remain active for installment and life cycle activity initiated prior to the
Release 19.Q2 implementation.
BR07
Accept BR07 (Brazil Other) for life cycle transactions until Release 20.Q2 under the following
IRDs: K3, K6, KL, KN, KP, KR, KX, KZ, NC, NF, NI, NL, and NO.
CAB program BR07 will remain active for installment and life cycle activity initiated prior to the
Release 19.Q2 implementation.
Platform Impact
Dual Message System
Single Message
Message Flows
Message Layouts

Platform Impact
Dual Message System
Single Message
IPM MPE
Interchange √

√
and Associated MCCs
Edits
Error Numbers
Pricing/Fees
Reports
Bulk Files
Forms
Reporting
SAFE

Manager

Table File

Clearing
Clearing
Interchange
Mastercard will introduce modifications to Card Acceptor Business (CAB) Program criteria for
the interchange programs as described in this announcement.
Mastercard will life cycle the following under BSA 4/076000 to support this release
announcement.
CAB program BR03 (Brazil Fast Transactions) will be accepted for life cycle transactions until
Release 20.Q2 under IRD KH (Brazil Intracountry Fast Transactions—7–21 Installment
Payments).
CAB program BR07 (Brazil Other) will be accepted for life cycle transactions until Release
20.Q2 under the following IRDs:
• IRD K3—Brazil Intracountry Consumer Gold—7–21 Installment Payments
• IRD K6—Brazil Intracountry Consumer Prepaid Standard—7–21 Installment Payments
• IRD KL—Brazil Intracountry Platinum—7–21 Installment Payments
• IRD KN—Brazil Intracountry World/Black—7–21 Installment Payments
• IRD KP—Brazil Intracountry Commercial Core—7–21 Installment Payments
• IRD KR—Brazil Intracountry Purchasing Card—7–21 Installment Payments
• IRD KX—Brazil Intracountry Other—7–21 Installment Payments
• IRD KZ—Brazil Intracountry Mastercard Benefits—7–21 Installment Payments
• IRD NC—Brazil Intracountry Commercial Small Business—7–21 Installment Payments
• IRD NF—Brazil Intracountry Commercial Small Business Premium—7–21 Installment
Payments
• IRD NI—Brazil Intracountry Commercial Corporate—7–21 Installment Payments
• IRD NL—Brazil Intracountry Commercial Travel Air—7–21 Installment Payments
• IRD NO—Brazil Intracountry Commercial Travel Land—7–21 Installment Payments
Interchange Rates
Mastercard published revisions to the interchange rates for the Clearing Platform and for the
Single Message System in “Revised Brazil Intracountry Interchange Rates for Select Merchant
Categories” Brazil Interchange Bulletin No. 4, 16 December 2016.

AN 2125—Enhancement for International Debit Mastercard Single Message System Transactions
Chapter 21 AN 2125—Enhancement for International

Debit Mastercard Single Message System Transactions
Mastercard will begin sending Financial Transaction Advice/0220 messages to Single Message
System issuers where DE 5 (Amount Settlement) may have a value of zero.
AN 2125—Enhancement for International Debit Mastercard Single Message System

Transactions................................................................................................................................ 329
Version History............................................................................................................................329
At-A-Glance................................................................................................................................329
Enhancements............................................................................................................................ 330

AN 2125—Enhancement for International Debit Mastercard Single

Message System Transactions
Mastercard will begin sending Financial Transaction Advice/0220 messages to Single Message
System issuers where DE 5 (Amount Settlement) may have a value of zero.
Version History

At-A-Glance

Brands: Debit Mastercard®
Release: 19.Q2
Region: All
Action Indicator:

Enhancements
Attention warranted (Network-related)—Single Message System-connected

issuers must be aware that effective with release 19.Q2, Mastercard will
support Debit Mastercard transactions with the value zero in DE 5 in the
Financial Transaction Advice/0220 message. All issuers must prepare their
systems to accept Financial Transaction Advice/0220 messages with zero in
DE 5. In addition, issuers must be prepared to receive the 250–byte Batch
Data File containing these types of transactions.
Testing recommended—Mastercard recommends testing for issuers to
Enhancements
Background
The Single Message System generates a Financial Transaction Advice/0220 force post message
to the issuer based on information from a Global Clearing Management System (GCMS) First
Presentment/1240 message and forwards the Financial Transaction Advice/0220 to the issuer
with DE 4 (Amount, Transaction) and DE 5. The amount in DE 5 is the DE 4 transaction
amount represented in the applicable settlement currency. In some cases, currency conversion
results in a calculated DE 5 value of zero. Currently, when DE 5 is zero, the Financial
Transaction Advice (System-initiated)/0220 message is not sent, even when a non-zero
interchange fee is present.
Single Message System—Issuers

Effective with Release 19.Q2, the Single Message System will generate a Financial Transaction
Advice/0220 force post message to the issuer when DE 5 amount is zero and the interchange
fee amount was non-zero.
Issuers must prepare their systems as follows for international Single Message System
transactions:
• Receive Financial Transaction Advice/0220 message with zero in DE 5 due to currency
conversion rates
• Accept the 250–byte Batch Data File containing these types of transactions. The Financial
Record (FREC) Interchange Fee field will contain the non-zero interchange amount.

AN 2127—Expansion of Single Message System DE 127 (Processor Private Data) to 100 Characters
Chapter 22 AN 2127—Expansion of Single Message

System DE 127 (Processor Private Data) to 100 Characters
Mastercard is expanding Single Message System DE 127 to support up to 100 characters.
AN 2127—Expansion of Single Message System DE 127 (Processor Private Data) to 100

Characters.................................................................................................................................. 332
Version History............................................................................................................................332
At-A-Glance................................................................................................................................332
Enhancements............................................................................................................................ 333
250-Byte Batch Data File (BDF) Additional Processor Private Data Addendum (APPD)—
Optional Record..................................................................................................................... 333
Additional Processor Private Data Addendum (APPD)—Optional.........................................333
Single Message System DE 127 (Processor Private Data)..........................................................334
DE 127—Processor Private Data......................................................................................... 334

AN 2127—Expansion of Single Message System DE 127 (Processor

Private Data) to 100 Characters
Mastercard is expanding Single Message System DE 127 to support up to 100 characters.
Version History

Questions
At-A-Glance

Release: 19.Q2
Region: All
Action Indicator:
Effective Date: 12 April 2019

Enhancements
Enhancements
Mastercard will expand Single Message System DE 127 to support up to 100 characters.
The Single Message System reserves DE 127 for the proprietary use of customer processing
systems (CPS) that connect directly to the Single Message System. Currently, this variable
length data element may contain private-use data up to a maximum length of 50 characters.
Data placed in this field is stored temporarily by the Single Message System and returned to
the message originator in any subsequent response or acknowledgment message. The data is
not passed through to the message receiver.
With this enhancement, Mastercard will expand DE 127 to support a maximum length of 100
characters. There will be no change to how DE 127 is used.
NOTE: DE 127 in the Dual Message System (Authorization) is currently defined with a length
of 100 characters and is not impacted by this enhancement.
250-Byte Batch Data File (BDF) Additional Processor Private Data Addendum
(APPD)—Optional Record
The expansion of DE 127 will impact the 250-Byte Batch Data File (BDF) Additional Processor
Private Data Addendum (APPD)—Optional record documented in the Single Message System
Settlement and Reports manual.
DE 127 is represented in this record as “Processor Private Data” currently in positions 17–66.
Following the expansion of DE 127, it will be expanded to positions 17–116. The existing filler
positions that follow Private Processor Data will be reduced and shifted accordingly, from
positions 67–250 to positions 117–250.
Additional Processor Private Data Addendum (APPD)—Optional

The APPD record contains transaction matching or queuing detail that can be accessed by the
message originator or message designator upon receipt of the corresponding response to the
originating request or advice message.
Additional Processor Private Data Addendum (APPD) Optional
ISO DE No./
Processor Private Data 17–116 127 an-100 Private-use data up to a maximum

length of 100 characters.
Filler 117–250 N/A an-134 Spaces

Enhancements
Single Message System DE 127 (Processor Private Data)

The expansion of DE 127 will impact the Single Message System Specifications manual.
Mastercard will update occurrences of “50” to “100” in Single Message System DE 127.
DE 127—Processor Private Data

The Single Message System reserves DE 127 (Processor Private Data) for the proprietary use of
customer processing systems (CPS) that connect directly to the Single Message System.
Attributes

Length Field: 3 positions, value = ...100
Data Field: Variable length, contents of positions 1–999

Variable length, contents of positions 1–100
NOTE: ISO Standards define this data element as ans...999; LLLVAR however the Single
Message System uses it as ans...100; LLLVAR.
Application Notes
Any message originator (for example, any CPS or INF facility communicating directly with the
Single Message System) may use this data element to contain private-use data up to a
maximum length of 100 characters. Data placed in this field is not passed through to the
message receiver, but is stored temporarily by the Single Message System and returned to the
message originator in any subsequent response or acknowledgment message.


Question Answer
1. Is it correct to say that when an acquirer sends That is correct. But more accurately, when any
information to Mastercard in DE 127 of a message originator (acquirer or issuer) includes
request message, it will not be forwarded to DE 127 in the initial message, DE 127 itself is
the issuer? removed by Mastercard and temporarily stored
before the message is forwarded to its final
destination. DE 127 is reinserted into the
response message before the message is
forwarded to the original requester.

AN 2129—New Interchange Programs for Merchants in the European Economic Area
Chapter 23 AN 2129—New Interchange Programs for

Merchants in the European Economic Area
Mastercard is introducing four new interchange programs to support its proposed commitments to
the European Commission with regard to EEA inbound cross-border consumer transactions.
AN 2129—New Interchange Programs for Merchants in the European Economic Area................ 337
Version History............................................................................................................................337
At-A-Glance................................................................................................................................337
Overview.................................................................................................................................... 338
Customer Impact........................................................................................................................ 339
Enhancements............................................................................................................................ 340
Platform Impact.......................................................................................................................... 342
Clearing......................................................................................................................................343
Revised Interchange Rates...................................................................................................... 343
Frequently Asked Questions................................................................................................... 343

AN 2129—New Interchange Programs for Merchants in the European

Economic Area
Mastercard is introducing four new interchange programs to support its proposed
commitments to the European Commission with regard to EEA inbound cross-border
consumer transactions.
NOTE: The commitments announced by the European Commission on 4 December 2018 are
subject to a period of industry consultation and as such are subject to change, however
Mastercard is committed to providing customers with sufficient notice to prepare for these
changes. This document outlines the proposed framework in advance of the conclusion of the
industry consultation.
Version History

At-A-Glance

Release: 19.Q2 (Information only)
Region: All
System: Clearing, Single Message System
Action Indicator:
Information Only—Acquirer, Issuer

Overview
Effective Date: Dual Message System (Clearing): Future (Third Quarter of 2019)
Single Message System: Future (Third Quarter of 2019)
NOTE: The effective dates will be subject to the completion of

industry consultation by European Commission.
Overview
This overview provides information about the current environment and any applicable
NOTE: These are early indications of our design and are subject to change.
Initially this document will only provide a high level proposal for how Mastercard seeks to
implement technical arrangement for its proposed commitments. Further detail will be
provided when industry consultation has concluded and the commitments are finalized and
agreed by the European Commission (expected in early 2019).
Mastercard is introducing four new interchange programs to support its proposed

commitments to the European Commission with regard to EEA inbound cross-border
transactions.
Background
Mastercard has defined the EEA subregion as follows for purposes of interchange and service
fees.
Mastercard European Economic Area (EEA) Subregion
• The 28 member states of the European Union: Austria, Belgium, Bulgaria, Croatia, Czech
Republic, Cyprus, Denmark, Estonia, Finland (including Aland Islands), France (including
French Guiana, Guadeloupe, Martinique, Réunion, Saint Martin [French Part], and
Mayotte), Germany, Greece, Hungary, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta,
Netherlands, Poland, Portugal (including Azores and Madeira), Romania, Slovakia, Slovenia,
Spain (including Canary Islands, Ceuta, Melilla), Sweden, and United Kingdom (including
Gibraltar)
• Iceland, Liechtenstein, Norway (including Svalbard and Jan Mayen)

Currently all purchase transactions acquired for merchants in the EEA subregion with
consumer cards issued outside of the EEA subregion qualify for the applicable interregional,
intra-European, or intra-Western rates.


Mastercard will introduce four new interchange programs that will support purchase
transactions for consumer cards when the merchant is located in one of the EEA countries and
the issuer is located outside of the EEA.

These changes are being introduced in-line with Mastercard's proposed commitments to the
European Commission regarding EEA inbound interchange fees for consumer transactions.
Reference Materials
processing:
• Interchange and Service Fees Manual—Europe Region
manuals.
Customer Impact

Information Only—Acquirers of merchants located in one of the European Economic Area
(EEA) countries must support the following new interchange programs:
• IRD EG—EEA Card Present Credit Restricted Rates
• IRD EB—EEA Card Present Debit Restricted Rates
• IRD EV—EEA Card Not Present Credit Restricted Rates
• IRD EW—EEA Card Not Present Debit Restricted Rates
Information Only—Issuers located outside of the EEA countries must be prepared to receive
transactions submitted with any of the four new interchange programs introduced in this
announcement.

Enhancements
Testing recommended—Mastercard recommends that acquirers and issuers perform testing to

support the enhancements in this announcement.
NOTE: Additional details about testing availability dates will be provided in a future update.

Message System:
Enhancements
Mastercard will introduce four new interchange programs that will support purchase
transactions for consumer cards when the merchant country is an EEA country and the issuer
country is not an EEA country.

Mastercard will introduce the following two new IRDs for card present transactions:
• IRD EG—EEA Card Present Credit Restricted Rates
• IRD EB—EEA Card Present Debit Restricted Rates
Mastercard will introduce the following two new IRDs for card not present transactions:
• IRD EV—EEA Card Not Present Credit Restricted Rates

Enhancements
• IRD EW—EEA Card Not Present Debit Restricted Rates

Mastercard will create new edits to support these new IRDs.
NOTE: When the Clearing Platform identifies the transaction as qualified under the specified
interchange programs, the Clearing Platform will truncate PDS 0146 (Amounts, Transaction
Fee) at two decimal positions without rounding, and, if applicable, PDS 0147 (Extended
Precision Amounts) at six decimal positions without rounding.
These IRDs will be assigned to the following Business Service Arrangement (BSA) Levels:
• 1—Interregional BSAs: 1-010501, 1-020501, 1-030501, 1-040501, 1-060501, 1-010201,
1-010301, 1-010401, 1-010601, 1-020101, 1-020301, 1-020401, 1-020601, 1-030101,
1-030201, 1-030401, 1-030601, 1-040101, 1-040201, 1-040301, 1-040601, 1-050101,
1-050201, 1-050301, 1-050401, 1-050601, 1-060101, 1-060201, 1-060301, 1-060401
• 2—Intraregional (Intra-European) BSAs: 2-050001 and 2-050002
• 3—Intercountry (Intra-Western) BSA: 3-050021
NOTE: The new cross border interchange rates and criteria will apply to all consumer purchase
transactions. Applicable processing codes for card present transactions are:
• 00—Purchase
• 09—Purchase with Cash back
• 18—Purchase (Unique MCC)
• 20—Credit
Purchase transactions at ATMs are also included.
Card Present Transactions

Criteria for card present transactions for this project will be provided in a future update to this
announcement or in a future announcement.
Card Not Present Transactions

Criteria for card not present transactions for this project will be provided in a future update to
this announcement or in a future announcement.
Single Message System—Acquirer, Issuer

There is no development required for customers connected to the Single Message System.
NOTE: Calculated interchange fee will be truncated at two decimal positions without
rounding.

Platform Impact
Platform Impact
Dual Message
Message Flows
Message Layouts
IPM MPE
Interchange √

and Associated MCCs
Edits
Error Numbers
Pricing/Fees
Reports
Bulk Files
Forms
Reporting
SAFE

Manager

Table File

Clearing
Clearing
Revised Interchange Rates

Interchange rates will be published in a future interchange announcement.

Question Answer
1. Why are four new interchange programs Despite the fact that by Mastercard rules it is
being added to BSAs that are not connected prohibited for acquirers registered in one region
to Europe (for example, 1-040101)? to work with merchants from another region,
occasionally such transactions happen (for
example an acquirer from Australia acquiring
transactions for a merchant in EEA). To make
sure all transactions are captured, Mastercard
adds new interchange programs across all cross-
border BSAs.

AN 2130—New Commercial Credit Product Codes and U.S. Intraregional Interchange Program
Chapter 24 AN 2130—New Commercial Credit Product

Codes and U.S. Intraregional Interchange Program
Mastercard is introducing commercial card product codes under the Mastercard credit acceptance
brand to be issued in the U.S. region.
AN 2130—New Commercial Credit Product Codes and U.S. Intraregional Interchange Program..346
Version History............................................................................................................................346
At-A-Glance................................................................................................................................347
Overview.................................................................................................................................... 347
Customer Impact........................................................................................................................ 349
Enhancements............................................................................................................................ 350
Platform Impact.......................................................................................................................... 351
Authorization..............................................................................................................................352
DE 63—Network Data....................................................................................................... 352
Alternate Processing...............................................................................................................354
Clearing......................................................................................................................................354
PDS 0002—GCMS Product Identifier................................................................................. 354
IPM MPE................................................................................................................................ 355
Interchange............................................................................................................................355
IRD V5—Commercial VIP Standard.....................................................................................355
Edits.......................................................................................................................................357
Modified Edit—DE 63 (Transaction Life Cycle ID)................................................................ 357
Modified Edit—PDS 0023 (Terminal Type)...........................................................................358
Modified Edit—PDS 0173 (Legal Corporate Name).............................................................358
Modified Edit—PDS 0595 (Card Acceptor Type), Subfield 1 (Business Type)........................ 359
Modified Edit—PDS 0595 (Card Acceptor Type), Subfield 5 (Business Type Provided Code). 359
Modified Edit—PDS 0596 (Card Acceptor Tax ID), Subfield 2 (Card Acceptor Tax ID
Provided Code).................................................................................................................. 361
Provided Code).................................................................................................................. 361

Error Numbers................................................................................................................... 362

Quarterly Mastercard Reporting..............................................................................................363

AN 2130—New Commercial Credit Product Codes and U.S.

Intraregional Interchange Program
Mastercard is introducing commercial card product codes under the Mastercard credit
acceptance brand to be issued in the U.S. region.
Version History

8 Jan 2019 Made the following updates in the “Is Customer Action Customer Impact
Required?” subsection of Customer Impact:
• Revised the “Network Mandate” as follows:
– Old language: Acquirers of domestic U.S. transactions
must support the new commercial card product
codes. If such acquirers do not support these
enhancements, these STP and VCN transactions will
be rejected by the Clearing Platform.
– New language: Acquirers of domestic U.S.
transactions must support the new commercial card
product codes. If such acquirers do not support these
enhancements, virtual card transactions leveraging
these products codes will be rejected by the Clearing
Platform.
• Removed the following language from the “Program or
service requirement:” Issuers that do not choose to issue
cards under these products will not be able to participate
in STP.
The removal of this content is not marked by a change
bar.

Questions

At-A-Glance
At-A-Glance

Products & Services: Commercial Products
Release: 19.Q2
Action Indicator:
Overview
Background
Mastercard offers virtual card products that facilitate single-use, virtual card numbers (VCNs)
used primarily to make highly secure, low-risk, business-to-business (B2B) purchases. A VCN is
a randomly generated, temporary card number that maps to the cardholder’s actual primary
account number (PAN), thus eliminating the need for a supplier to have the cardholder’s PAN
on record. This secure solution protects a cardholder’s card information from fraudulent
activity, while also making B2B transactions more secure.

As these virtual card products typically require the supplier to manually key enter the VCN,
Mastercard eliminated this step for suppliers by developing a straight-through processing (STP)
solution that routes the transaction directly to the acquirer.

With STP, the burden of enhanced-data interchange rate qualification is currently placed on
the issuer, which often does not have all the data required to ensure that the supplier qualifies
at the appropriate rate.

Mastercard is introducing 11 new commercial card product codes for use with virtual card
transactions acquired in the U.S. region. These new products are intended to offer a range of
new commercial rates (through variable interchange pricing [VIP]) that do not require the
supplier to provide enhanced data for rate qualification for STP. VIP is a program that ties
product codes to an interchange rate agreed upon by a corporate buyer and a supplier.

By introducing new commercial credit programs associated with account ranges from which a
corporate buyer may request a VCN, Mastercard will be able to:
• Simplify participating issuers’ role in the processing of virtual card transactions via STP.
• Eliminate suppliers’ need to manually enter VCNs.
• Offer a range of new commercial rates for specific situations (for example, STP) without the
need for data qualification.
These enhancements are all part of Mastercard’s ongoing effort to drive B2B transaction
acceptance.
Reference Manuals
processing:
• Interchange Manual—U.S. Region

Customer Impact
manuals.
Customer Impact

Network Mandate—Acquirers of domestic U.S. transactions must support the new
commercial card product codes. If such acquirers do not support these enhancements, virtual
card transactions leveraging these products codes will be rejected by the Clearing Platform.
Program or service requirement—Issuers in the U.S. region that choose to issue cards under
these products must recognize and support the product codes as described in this release
announcement.
Registration required—Issuers in the U.S. region that choose to issue cards under these
products must register account ranges in their bank identification numbers (BINs) for each
product code they want to use. To be eligible to register account ranges under these new
product codes, issuers must either have a minimum virtual card portfolio with Mastercard of
USD 10 billion or be signed up for Mastercard STP with a minimum five-year commitment of
USD 3 billion. Issuers in the U.S. region that do not issue cards under these products will need
to continue providing virtual card transaction data to suppliers.
Testing recommended—Mastercard recommends testing for acquirers of domestic U.S.
transactions and issuers in the U.S. region that choose to issue cards under these products to
support the enhancements as described in this announcement.


Enhancements
The following are examples of message types within the Dual Message System:
Enhancements
Mastercard will introduce 11 new commercial card product codes.
• MVA—Mastercard B2B VIP 1
• MVB—Mastercard B2B VIP 2
• MVC—Mastercard B2B VIP 3
• MVD—Mastercard B2B VIP 4
• MVE—Mastercard B2B VIP 5
• MVF—Mastercard B2B VIP 6
• MVG—Mastercard B2B VIP 7
• MVH—Mastercard B2B VIP 8
• MVI—Mastercard B2B VIP 9
• MVJ—Mastercard B2B VIP 10
• MVK—Mastercard B2B VIP 11
NOTE: These product codes will not be available for ATM or manual cash disbursement
transactions.

Mastercard will add these 11 new product codes as valid values in DE 63 (Network Data),
subfield 1 (Financial Network Code).
These new product codes will be available to Stand-In processing.
Acquirers of domestic U.S. transactions must support the new commercial card product codes
issued in the U.S. region and identified in DE 63, subfield 1 in authorization messages.
Issuers in the U.S. region that choose to issue cards under these products must be prepared to
receive these new commercial card product codes in DE 63, subfield 1 in authorization
messages.
Mastercard will update the Authorization Transaction Investigator to support these new
product codes.
Any account range set up for any of these new product codes will be local use only, and
acceptance will be restricted to merchants in the U.S. region.

Platform Impact

Mastercard will add these 11 new product codes as a valid value in PDS 0002 (GCMS Product
Mastercard will add these new product codes to the appropriate IPM MPE tables.
Mastercard will introduce a new interchange program under U.S. intraregional business
service arrangement (BSA) 2/010001.
Mastercard will add these new product codes to the new U.S. intraregional interchange
program.
Acquirers of domestic U.S. transactions must be prepared to recognize these new product
codes in both PDS 0002 and PDS 0003 when processing clearing transactions and to help
ensure that their systems accurately qualify the product codes for the interchange program
specified in this announcement.
Issuers in the U.S. region that choose to issue cards under these products must support receipt
of the new product codes in both PDS 0002 (GCMS Product Identifier) and PDS 0003
(Licensed Product Identifier).
Mastercard will update Quarterly Mastercard Reporting with these new product codes.
Mastercard will update the Clearing Transaction Investigator to support these new product
codes.
Platform Impact
Dual Message System
Single Message
Message Flows
Message Layouts
IPM MPE √

and Associated MCCs
Edits √

Authorization
Dual Message System
Single Message
Error Numbers √
Billing and Fees
Reports
Bulk Files
Forms
√
Reporting
SAFE

Manager

Table File
Authorization


Authorization

service.
®
MVA Mastercard B2B VIP 1 √
®
MVB Mastercard B2B VIP 2 √
®
MVC Mastercard B2B VIP 3 √
®
MVD Mastercard B2B VIP 4 √
®
MVE Mastercard B2B VIP 5 √
®
MVF Mastercard B2B VIP 6 √
®
MVG Mastercard B2B VIP 7 √
®
MVH Mastercard B2B VIP 8 √
®
MVI Mastercard B2B VIP 9 √
®
MVJ Mastercard B2B VIP 10 √
®
MVK Mastercard B2B VIP 11 √

Clearing
The 11 product codes introduced in this announcement will be eligible for Stand-In
processing.
Mastercard will update the Authorization Transaction Investigator with the 11 product codes
introduced in this announcement.
Clearing


Program Identifier.
GCMS Licensed
Product Product
(PDS (PDS
MVA MVA Mastercard® B2B VIP 1 MVA—Mastercard® B2B VIP 1
MVB MVB Mastercard® B2B VIP 2 MVB—Mastercard® B2B VIP 2
MVC MVC Mastercard® B2B VIP 3 MVC—Mastercard® B2B VIP 3
MVD MVD Mastercard® B2B VIP 4 MVD—Mastercard® B2B VIP 4
MVE MVE Mastercard® B2B VIP 5 MVE—Mastercard® B2B VIP 5
MVF MVF Mastercard® B2B VIP 6 MVF—Mastercard® B2B VIP 6
MVG MVG Mastercard® B2B VIP 7 MVG—Mastercard® B2B VIP 7
MVH MVH Mastercard® B2B VIP 8 MVH—Mastercard® B2B VIP 8
MVI MVI Mastercard® B2B VIP 9 MVI—Mastercard® B2B VIP 9
MVJ MVJ Mastercard® B2B VIP 10 MVJ—Mastercard® B2B VIP 10
MVK MVK Mastercard® B2B VIP 11 MVK—Mastercard® B2B VIP 11

Clearing
IPM MPE
Mastercard will update the following IPM MPE tables with the 11 product codes introduced in
this announcement in the Licensed Product ID field.
Interchange
IRD V5—Commercial VIP Standard

Transactions must meet requirements to qualify for this interchange program.
Card Program ID MCC
GCMS Product ID Commercial Credit—MVA, MVB, MVC, MVD, MVE, MVF, MVG, MVH, MVI, MVJ,
MVK


• 20—Credit (Purchase Return)
Card Acceptor • A001—Airline

Business (CAB) • B001—Cruise/Steamship
Program
• F001—Restaurant
• H001—Lodging
• OTH1—Other
• R001—Railways
• U001—Unique
Timeliness None

Clearing
Approval Code Not required
Magnetic stripe Not required
data from
authorization
message
If present, must contain a valid Banknet Reference Number, and the Banknet Date
must contain a valid date in the format MMDD.

Business Code
(MCC)

Card Acceptor ID Required
Code
Name
Street Address

Postal (ZIP) Code
Card Acceptor Required for transactions occurring in the United States.
State, Province, or
Region Code
Code) contains the value USA, this subfield must contain a valid state code.

Country Code
Mastercard Not required

Assigned ID
Financial Detail All MCCs require the following Financial Detail Addendum (Corporate Card Common
Addendum/1644 Data Requirements)/1644 data:
Notes Transactions submitted with this IRD are not subject to interchange compliance
processing.

Clearing
Interchange Rates
Mastercard will provide information about interchange rates in a future interchange
announcement.
Edits
announcement.
Modified Edit—DE 63 (Transaction Life Cycle ID)

This edit will be modified to exclude IRD V5 (Commercial VIP Standard).

1100 The Clearing Platform must ensure Mastercard will exclude IRD V5
that DE 63 is present for U.S.- (Commercial VIP Standard) from
acquired incentive interchange this edit for transactions submitted
programs. under the U.S. intraregional
business service arrangement
(BSA) 2/010001.
Collection Only messages and reversals are excluded from this edit.

Clearing
Modified Edit—PDS 0023 (Terminal Type)


0596 The Clearing Platform must ensure Mastercard will exclude IRD V5
that if PDS 0023 (Terminal Type) (Commercial VIP Standard) from
contains value CT4 (CAT level 4), this edit for transactions submitted
and DE 3 (Processing Code) under the U.S. intraregional
contains value 18 (Unique business service arrangement
Transaction) or 20 (Credit (BSA) 2/010001.
[Purchase Return]), then PDS 0158
(Business Activity), subfield 4
(Interchange Rate Designator)
must contain a valid value.
Modified Edit—PDS 0173 (Legal Corporate Name)


1023 If the Issuer Account Range Mastercard will exclude IRD V5
Product Type equals 2 (Commercial VIP Standard) from
(Commercial), and DE 43 (Card this edit for transactions submitted
Acceptor Name/Location), subfield under the U.S. intraregional
6 (Card Acceptor Country Code) business service arrangement
equals value USA, then the (BSA) 2/010001.
Clearing Platform must ensure that
PDS 0173 (Legal Corporate Name)
is present.

Clearing
Modified Edit—PDS 0595 (Card Acceptor Type), Subfield 1 (Business Type)


PDS 0595 (Card Acceptor Type),
subfield 1 (Business Type) does not
equal value 2 (Not known).
Modified Edit—PDS 0595 (Card Acceptor Type), Subfield 5 (Business Type Provided
Code)

PDS 0595 (Card Acceptor Type),
subfield 5 (Business Type Provided
Code) contains value Y (Business
type is provided).

Clearing
Code)
This edit will be modified to include IRD V5 (Commercial VIP Standard).

2436 The Clearing Platform must ensure Mastercard will include IRD V5
that PDS 0595 (Card Acceptor (Commercial VIP Standard) in this
Type), subfield 5 (Business Type edit for transactions submitted
Provided Code), if present, does under the U.S. intraregional
not contain value N (Business type business service arrangement
was not provided). (BSA) 2/010001.
Code)

that if PDS 0595 (Card Acceptor (Commercial VIP Standard) in this
Type), subfield 5 (Business Type edit for transactions submitted
Provided Code) is present and under the U.S. intraregional
contains value R (Card acceptor business service arrangement
refused to provide business type), (BSA) 2/010001.
then PDS 0595, subfield 1
(Business Type) must contain value
2 (Not known).

Clearing
Provided Code)

PDS 0596 (Card Acceptor Tax ID),
subfield 2 (Card Acceptor Tax ID
Provided Code) contains value Y.
Provided Code)

that PDS 0596 (Card Acceptor Tax (Commercial VIP Standard) in this
ID), subfield 2 (Card Acceptor Tax edit for transactions submitted
ID Provided Code), if present, does under the U.S. intraregional
not contain value N (Card business service arrangement
Acceptor Tax ID not provided). (BSA) 2/010001.

Clearing
Error Numbers
Edit
Error Performed
DE 63 1100 DE63 TRANSACTION LIFE CYCLE ID MUST BE PRESENT Both

FOR THE SUBMITTED INCENTIVE INTERCHANGE
PROGRAM.
PDS 0023 0596 PDS0052S3 UCAF COLLECTION INDICATOR/PDS0158S4 Both

INTERCHANGE RATE DESIGNATOR CONFLICT.
PDS 0173 1023 PDS0173 LEGAL CORPORATE NAME MUST BE PRESENT. Both
PDS 0595, s1 2367 PDS0595S1 BUSINESS TYPE INVALID FOR CORPORATE Both
CARD TRANSACTIONS CONDUCTED WITH A U.S.-
BASED MERCHANT.
PDS 0595, s5 2365 PDS0595S5 BUSINESS TYPE PROVIDED CODE INVALID. Both
THE BUSINESS TYPE PROVIDED CODE MUST BE Y FOR
CORPORATE CARD TRANSACTIONS CONDUCTED WITH
A U.S.-BASED MERCHANT
PDS 0595, s5 2436 PDS0595S5 BUSINESS TYPE PROVIDED CODE VALUE Both
INVALID FOR THE INTERCHANGE PROGRAM.
PDS 0595, s5 2466 IF PDS0595S5 BUSINESS TYPE PROVIDED CODE Both

CONTAINS THE VALUE OF R, THEN PDS0595S1 MUST BE
2.
PDS 0596, s2 2346 PDS0596S2 CARD ACCEPTOR TAX ID PROVIDED CODE Both
INVALID. THE CARD ACCEPTOR TAX ID MUST BE
PROVIDED FOR THE BUSINESS SERVICE, INTERCHANGE
PROGRAM COMBINATION.
PDS 0596, s2 2436 PDS0596S2 CARD ACCEPTOR TAX ID PROVIDED CODE Both
VALUE INVALID FOR THE INTERCHANGE PROGRAM.


For Quarterly Mastercard Reporting, issuers that choose to issue cards with the 11 product
codes introduced in this announcement must report any activity associated with that product
code with any Mastercard Credit activity in the proper category.
Mastercard will update the Clearing Transaction Investigator with the 11 product codes
introduced in this announcement.

Question Answer
1. These 11 new commercial card product codes The VIP BIN ranges will be set up as “local use
are for use in the domestic U.S. If a buyer tries only” in support of these domestic U.S. products.
to use a card issued under any of these 11 If a card issued under any of these 11 new VIP
new VIP product codes to initiate a product codes is used for a non-U.S. supplier, the
transaction with a Canadian supplier, will the Mastercard switch will reject the authorization.
transaction be declined?
2. Does “domestic U.S.” include U.S. territories? No. Only the 50 U.S. states apply.
3. How does the “variable interchange pricing” “Variable” refers to the buyer’s decision to
portion of the program work? choose a VCN from a VIP card product with a
corresponding interchange rate that fits the
supplier agreement for a particular invoice
payment.
This VIP program ties the 11 new product codes
to an interchange rate through the new U.S.
intraregional IRD V5.
To be eligible to register account ranges under
these new product codes, issuers must either
have a minimum virtual card portfolio with
Mastercard of USD 10 billion or be signed up for
Mastercard STP with a minimum five-year
commitment of USD 3 billion.
4. How would an acquirer know their merchant/ The issuer implementation guide for VIP will
supplier is participating in a VIP buyer require suppliers to contact their acquirer to
agreement? prepare for VIP interchange.
5. Will Mastercard update the Smart Data Global Yes. Mastercard has a process in place to
Data Repository (GDR) with the introduction internally communicate new product codes to all
of these new commercial product codes? divisions of Mastercard—including the Smart
Data product team.

Question Answer
6. How will acquirers support certain addenda Suppliers will be required to inform their acquirer
data (for example, tax ID) if they don't know of participation and provide any such necessary
their merchant participates? addenda data.

AN 2133—Interchange Rate Program Timeliness Holidays 2019
Chapter 25 AN 2133—Interchange Rate Program

Timeliness Holidays 2019
For U.S. region incentive interchange rate programs, Mastercard is excluding the holidays listed in
this announcement from interchange timeliness calculation and editing.
AN 2133—Interchange Rate Program Timeliness Holidays 2019..................................................366

Version History............................................................................................................................366
At-A-Glance................................................................................................................................366
Enhancement Description........................................................................................................... 367


For U.S. region incentive interchange rate programs, Mastercard is excluding the holidays
listed in this announcement from interchange timeliness calculation and editing.
Version History
Date Description of Change

30 Oct 2018 Corrected date for Thanksgiving Day.
At-A-Glance

Release: 19.Q2
System: Clearing
Action Indicator:
Testing recommended—Acquirer
Effective Date: Dual Message System (Clearing): 1 January 2019

Enhancement Description
Enhancement Description
GCMS, Clearing Optimizer and Utilities software, and interchange compliance will exclude the
holidays listed when calculating the last valid transaction date (LVTD) for First Presentment/
1240 messages submitted for any interchange rate program in which interchange timeliness
editing is applied.
The following table shows the 2019 Mastercard U.S. region interchange rate program
timeliness holidays.
MasterCard U.S. Region Interchange Rate Program Timeliness Holidays
Date to be excluded from

Holiday Day of the Week Timeliness Calculation
New Year’s Day Tuesday 1 January 2019
Memorial Day Monday 27 May 2019
Independence Day Thursday 4 July 2019
Labor Day Monday 2 September 2019
Thanksgiving Day Thursday 28 November 2019
Christmas Day Wednesday 25 December 2019
IPM MPE
The IPM MPE file itself is not affected. However, the net settlement holiday updates will be
reflected in IPM MPE Table IP0060T1 (Timeliness Holiday).

AN 2134—Issuer-provided Format Error Responses
Chapter 26 AN 2134—Issuer-provided Format Error

Responses
Mastercard is mandating that issuers indicate the data element in error when providing a format
error response in Authorization Request Response/0110 and Financial Transaction Request
Response/0210 messages.
AN 2134—Issuer-provided Format Error Responses..................................................................... 369

Version History............................................................................................................................369
At-A-Glance................................................................................................................................369
Enhancements............................................................................................................................ 370


Mastercard is mandating that issuers indicate the data element in error when providing a
format error response in Authorization Request Response/0110 and Financial Transaction
Request Response/0210 messages.
Version History

Questions
At-A-Glance

Release: 19.Q2
Region: All
Action Indicator:
Network Mandate—Issuers

Enhancements

Enhancements
Mastercard is committed to ensuring the quality of the data within the ecosystem and
providing the best customer experience at the point of interaction. To meet these
commitments, the Mastercard Network validates data to ensure it conforms with Dual
Message System (Authorization) and Single Message System specifications that are considered
to be essential to the authorization decision. Some less critical data may pass through to
issuers with less editing, allowing issuers to decide which data is critical to their needs. The
Data Integrity Monitoring Program manages these cases in order to not disrupt the transaction
process.
When Mastercard detects that data within an Authorization Request/0100 or Financial
Transaction Request/0200 message is not correctly formatted, it generates an Authorization
Request Response/0110 or Financial Transaction Request Response/0210 message to the
acquirer where DE 39 (Response Code) contains the value 30 (Format error). Mastercard also
includes DE 44 (Additional Response Data) with a numeric value indicating the data element
number where the format error occurred.
Examples:
• When one of the subelements of DE 48, DE 108, or DE 112 is in error, DE 44 will contain
the value of 048, 108, or 112 plus a three-position value representing subelement nn
(0nn), for a total of six positions; subfields are not included:
– Error on DE 48 subelement 42, subfield 1: 048042 (no subfield information is provided)
– Error on DE 48 subelement 61: 048061
• DE 48 TCC format error will be responded with DE 44 = 048000.
• For non-DE 48/DE 108/DE 112 format errors, DE 44 will only have data element
information and no subelement information. For example, the format error in DE 22 will
have DE 44 as 022.
When an issuer responds with a format error, they are indicating that the data in question
violates Mastercard specifications and is essential to make an authorization decision.
Mastercard will use this information when considering the creation of new data validation
requirements or modifying existing requirements supported by the network. Mastercard is
mandating that when issuers provide DE 39 (Response Code) value of 30 (Format error) in
Authorization Request Response/0110 or Financial Transaction Request Response/0210
messages, they must also provide a properly formatted DE 44 (Additional Response Data) to
indicate the data element in error. Mastercard forwards DE 44 to the acquirer in the
Authorization Request Response/0110 message. For Financial Transaction Request Response/
0210 messages, DE 44 from the issuer will be passed to the acquirer in a future release.

The availability of this additional response information will enable Mastercard to understand
the specific data that caused the issuer to decline with a format error so that Mastercard can
better identify the source of formatting issues and assist customers in their resolution.
Mastercard may implement an edit as part of the Data Integrity Monitoring Program in a
future release to monitor issuer compliance with this mandate.
NOTE: Mastercard will not reject an issuer format error response when DE 44 is missing.

Question Answer
1. What is the value to the payments ecosystem Mastercard has always sent DE 44 within format
if issuers and processors comply with this error switch responses as means for acquirers to
mandate? address data quality issues. Mastercard is now
asking issuers to follow suit for the same data
quality benefit.
2. When is the Data Integrity edit being No timelines have yet been established. A series
implemented to ensure compliance with the of audits are planned after the 19.Q2 Release
mandate? implements. The need for compliance edits will
be determined based on the audit results. It
should also be noted that Mastercard will not
reject issuer format error responses that are
submitted without DE 44.

AN 2136—Introduction of Mastercard Cardless ATM Program
Chapter 27 AN 2136—Introduction of Mastercard Cardless

ATM Program
Mastercard is announcing switching enhancements in conjunction with the launch of the
Mastercard Cardless ATM Program. This program provides cardholders with the ability to initiate
cash withdrawals using an issuer's mobile banking application (app) and to complete the
transaction at an enabled ATM without the use of their physical card.
AN 2136—Introduction of Mastercard Cardless ATM Program.................................................... 374

Version History............................................................................................................................374
At-A-Glance................................................................................................................................376
Overview.................................................................................................................................... 377
Customer Impact........................................................................................................................ 378
Enhancements............................................................................................................................ 379
Platform Impact.......................................................................................................................... 387
Authorization..............................................................................................................................388
CIS Data Element Defintions...................................................................................................388
DE 61—Point-of-Service (POS) Data................................................................................... 389
Edits.......................................................................................................................................390
Clearing......................................................................................................................................394
DE 22—Point of Service (POS) Entry Mode......................................................................... 394
PDS 0022—Additional Terminal Operating Environments................................................... 394
IPM MPE................................................................................................................................ 395
Edits.......................................................................................................................................396
New Edit—PDS 0022 (Additional Terminal Operating Environments).................................. 396
New Edit—DE 22 (Point of Service [POS] Entry Mode), Subfield 7 (Card Entry Mode)..........396
New Edit—DE 22 (Point of Service [POS] Entry Mode), subfield 4 (Terminal Operating
Environment)..................................................................................................................... 397
Modified Edit—DE 22 (POS Entry Mode), Subfield 4 (Terminal Operating Environment)...... 398
Modified Edit—DE 22 (POS Entry Mode), Subfield 4 (Terminal Operating Environment....... 399
Error Numbers................................................................................................................... 400


DE 61—Point of Service (POS) Data....................................................................................402
Edits.......................................................................................................................................403


Mastercard is announcing switching enhancements in conjunction with the launch of the
Mastercard Cardless ATM Program. This program provides cardholders with the ability to
initiate cash withdrawals using an issuer's mobile banking application (app) and to complete
the transaction at an enabled ATM without the use of their physical card.
Version History

29 Jan 2019 Updated DE 3 (Processing Code), subfield 1 (Cardholder Enhancements
Transaction Type Code), value 01 (Withdrawal) to DE 3
(Processing Code), subfield 1 (Cardholder Transaction Type
Code), value 01 (ATM Cash Withdrawal).
Added edit for DE 48 (Additional Data), subelement 28 Authorization: Edits
(Cardless ATM Order ID).
Updated Data Representation field to ans–1; TAGLLL. PDS 0022—
Additional Terminal
Operating
Environments

Version History

Removed the following statement: “Collection Only New Edit—PDS 0022
messages are excluded from this edit”. (Additional Terminal
Operating
Environments)
Modified Edit—DE
22 (POS Entry Mode),
Subfield 4 (Terminal
Operating
Environment)
Modified Edit—DE
Operating
Environment
Modified Edit—DE
Operating
Environment)
Modified Edit—DE
Operating
Environment)
Updated edit description to include DE 26 (Card Acceptor New Edit—DE 22

Business Code [MCC]), value 6011 (Member Financial (Point of Service
Institution—Automated Cash Disbursements). [POS] Entry Mode),
Subfield 7 (Card
Entry Mode)
Added reference to DE 3, subfield 1, value 01 in the New Edit—PDS 0022
Requirement description. (Additional Terminal
Operating
Environments)
In New Edit—DE 22 (Point of Service [POS] Entry Mode), New Edit—DE 22
subfield 4 (Terminal Operating Environment): (Point of Service
[POS] Entry Mode),
• Added reference to DE 3, subfield 1, value 01 in the
subfield 4 (Terminal
Requirement description.
Operating
• Updated edit exclusions to include IRD 51, 75, 85, or 88. Environment)

At-A-Glance

Updated Modification for this Release text for DE 22 (POS Modified Edit—DE
Entry Mode), Subfield 4 (Terminal Operating Environment). 22 (POS Entry Mode),
Operating
Environment)
Modified Edit—DE
Operating
Environment)
Updated edit for DE 48 (Additional Data), subelement 28 Single Message

(Cardless ATM Order ID) and DE 61 (Point-of-Service [POS] System: Edits
Data), subfield 3 (POS Terminal Location).
At-A-Glance

Release: 19.Q2
Region: All
Action Indicator:
Program or service requirement—Acquirer, Issuer
Registration required—Acquirer, Issuer
Testing required—Acquirer, Issuer
Dual Message System (Clearing): 11 June 2019

Overview
Overview

Mastercard is launching a pilot program to offer the Mastercard Cardless ATM as a new
program to issuers. The Mastercard Cardless ATM program is a digital solution that allows
cardholders to use an issuer’s mobile banking app to withdraw cash from their enabled ATM
without the need of a physical card.

Mastercard will enable an issuer and ATM operator to allow cardholders to view the fee of an
ATM cash withdrawal in advance of conducting the transaction from an enabled ATM using
their mobile banking app. Cardholders will initiate the withdrawal using their mobile banking
app after their arrival at the ATM or any time in advance of the withdrawal. At the ATM,
cardholders will scan a Quick Response Code (QR) code or manually enter a code displayed on
the ATM. After viewing any transaction fees in their mobile banking app, cardholders will
authenticate the withdrawal using their mobile device. Mastercard will pass the token and
details of the withdrawal to the ATM operator about the authorization request. If the
transaction is approved by the issuer, the ATM will dispense cash to cardholders.
The Mastercard Cardless ATM program will support cardless cash withdrawals initiated on the
Mastercard Network or those received from alternate networks via the Mastercard Shared
Service Platform (MSSP) or Alternative Network Routing Solution (ANRS) protocols.
Participation in the Cardless ATM program will be on an opt-in basis.
NOTE: Mastercard will not enable Visa tokenized accounts carrying a Mastercard ATM brand
with this enhancement.

The Mastercard Cardless ATM program is a digital ATM solution that provides improved
security, convenience, and transparency to consumers, drives engagement in the mobile
banking app, and reduces time and cost of teller service cash disbursements for issuers. For
ATM acquirers, the Mastercard Cardless ATM program allows them to meet the increased
security expectations of issuers and consumers and leverages the use of existing network
capabilities for authorization, settlement, and reconciliation.

Reference Manuals
processing:
• Cardless ATM Program Guide
• Digital Secure Remote Payment—Acquirer Implementation Guide
• IPM Clearing Formats Error Numbers and Messages
• Mastercard Shared Services Platform
• Mastercard Digital Enablement Service—Issuer Implementation Guide
• Mastercard Digital Enablement Service—Acquirer Implementation Guide
• Mastercard Digital Enablement Service—Technical Specifications for Dual and Single
Message Systems
• Single Message Transaction Manager
manuals.
Additional information on the Cardless ATM program is available on http://mastercard.com/

cardlessatm and on the Mastercard Developers site at https://developer.mastercard.com/
product/cardless-atm.
Customer Impact

Program or service requirement—Acquirers and issuers that participate in the Mastercard
Cardless ATM program must support the enhancements as described in this announcement.
Acquirers and issuers not participating in the Mastercard Cardless ATM program will not be
impacted by this enhancement.

Enhancements
Registration required—Acquirers and issuers must register to participate in the Mastercard

Cardless ATM program. Acquirers and issuers must contact their Mastercard Implementation
Representative to participate.
Testing required—Mastercard requires acquirers and issuers that participate in the Mastercard
Cardless ATM program to perform testing.

Message System:
messages
Enhancements
Mastercard is announcing the following enhancements to the Dual Message System
(Authorization and Clearing) and to the Single Message System. These enhancements support
the identification and processing of Mastercard Cardless ATM transactions received on the
Mastercard Network or from alternate networks via the MSSP or ANRS protocols.
Dual Message System (Authorization) and Single Message System—Acquirers

Acquirers of ATM operators that participate in the Mastercard Cardless ATM program must
support new and existing data as indicated in the following table.

Enhancements
DE Description Subfield Subelement Description Value Description
22 POS Entry 1 POS Terminal 09 PAN/Token

Mode PAN Entry entry via
Mode electronic
commerce
containing
DSRP
cryptogram in
DE 55
2 POS Terminal 1 Terminal has

PIN Entry PIN entry
Mode capability
8 Terminal has
PIN entry
capability but
PIN pad is not
currently
operative
48 Additional New 28 Cardless ATM

Data Order ID
New 29 Additional POS A Transaction

Terminal has been
Locations initiated
remotely and
completed at a
physical
terminal on
premises of
the card
acceptor
facility
B Transaction
has been
initiated
remotely and
completed at a
physical
terminal off
premises of
the card
acceptor
facility

Enhancements
55 Integrated
Circuit Card
(ICC) System-
Related Data
61 Point-of- 1 POS Terminal 1 Unattended

Service (POS) Attendance terminal
Data (cardholder-
activated
terminal [CAT],
home PC,
mobile phone,
PDA)
2 Reserved for 0 Zero-filled

Future Use
3 POS Terminal New 8 Additional POS

Location Terminal
Location
4 POS 5 Electronic
Cardholder order (home
Presence PC, Internet,
mobile phone,
PDA)
5 POS Card 1 Card not

Presence present
6 POS Card 0 Terminal/

Capture operator has
Capabilities no card
capture
capability
7 POS 0 Normal
Transaction request
Status (original
presentment)
8 POS 0 No security
Transaction concern
Security

Future Use

Enhancements
10 Cardholder- 6 Authorized
Activated Level 6 CAT:
Terminal Level Electronic
commerce
Acquirers that use the Dual Message System (Authorization) must be prepared to support
Cardless ATM transaction information in the following messages:
• Authorization Advice/0120—Acquirer-generated
• Authorization Advice Response/0130
Acquirers that use the Single Message System must be prepared to support Cardless ATM
transaction information in the following messages:
New Dual Message System (Authorization) and Single Message System edits will be
introduced for Cardless ATM transactions.
Dual Message System (Authorization) and Single Message System edits will be modified for
Cardless ATM transactions.
Dual Message System (Clearing)—Acquirers

Acquirers that participate in the Mastercard Cardless ATM program must support new and
existing information to identify such transactions:
• New and existing information to identify Mastercard Cardless ATM transactions:
– Existing DE 3 (Processing Code), subfield 1 (Cardholder Transaction Type Code), value 01
(ATM Cash Withdrawal)
– Existing DE 22 (POS Entry Mode):
– Subfield 4 (Terminal Operating Environment), new value 8 (Additional Terminal
Operating Environments)
– Subfield 7 (Card Entry Mode), value R (PAN entry via electronic commerce, including
remote chip)
– Existing DE 26 (Card Acceptor Business Code [MCC]), value 6011 (Member Financial
Institution—Automated Cash Disbursements)
– New PDS 0022 (Additional Terminal Operating Environments), value A (Transaction has
been initiated remotely and completed at a physical terminal on premises of the card

Enhancements
acceptor facility) and value B (Transaction has been initiated remotely and completed at
a physical terminal off premises of the card acceptor facility).
• Population of DE 22, subfield 4, value 8 in First Presentment/1240 messages when PDS
0022 is present.
• Population of PDS 0022 in First Presentment/1240 messages when DE 22, subfield 4, value
8 is present.
New clearing edits for Cardless ATM will be introduced for DE 22, subfield 4 and subfield 7
and PDS 0022.
Clearing edits for Cardless ATM will be modified for DE 22, subfield 4.

Issuers that participate in the Mastercard Cardless ATM program must support new and
existing data as indicated in the following table.
22 POS Entry 1 POS Terminal 09 PAN/Token

Mode PAN Entry entry via
Mode electronic
commerce
containing
DSRP
cryptogram in
DE 55
2 POS Terminal 1 Terminal has

PIN Entry PIN entry
Mode capability
8 Terminal has
PIN entry
capability but
PIN pad is not
currently
operative
48 Additional New 28 Cardless ATM

Data Order ID

Enhancements
New 29 Additional POS A Transaction

Terminal has been
Locations initiated
remotely and
completed at a
physical
terminal on
premises of
the card
acceptor
facility
B Transaction
has been
initiated
remotely and
completed at a
physical
terminal off
premises of
the card
acceptor
facility
55 Integrated
Circuit Card
(ICC) System-
Related Data
61 Point-of- 1 POS Terminal 1 Unattended

Service (POS) Attendance terminal
Data (cardholder-
activated
terminal [CAT],
home PC,
mobile phone,
PDA)

Future Use
3 POS Terminal New 8 Additional POS

Location Terminal
Location

Enhancements
4 POS 5 Electronic
Cardholder order (home
Presence PC, Internet,
mobile phone,
PDA)
5 POS Card 1 Card not

Presence present
6 POS Card 0 Terminal/

Capture operator has
Capabilities no card
capture
capability
7 POS 0 Normal
Transaction request
Status (original
presentment)
8 POS 0 No security
Transaction concern
Security

Future Use
10 Cardholder- 6 Authorized
Activated Level 6 CAT:
Terminal Level Electronic
commerce
Issuers that use the Dual Message System (Authorization) must be prepared to support
Cardless ATM transaction information in the following messages:
Issuers that use the Single Message System must be prepared to support Cardless ATM
transaction information in the following messages:

Enhancements
NOTE: Issuers will not receive DE 48, sueblements 28 and 29 in Acquirer Reversal Advice/0420
—Acquirer Initiated messages.
Single Message System chargebacks are not allowed for Mastercard Cardless ATM
transactions. If Mastercard receives chargebacks containing Cardless ATM transaction
information, Mastercard will reject the request in Issuer Reversal Advice/0422—Exception,
Issuer Initiated messages with the following reason codes:
• 0070 (Chargeback–Chip Liability Shift [POS and ATM])
• 0071 (Chargeback–Disputed Amount [POS only])
NOTE: Only reason code 17 (Cash Dispute-ATM Only) will be supported for the Single
Message System.
Cardless ATM transactions may or may not contain an online PIN. Mastercard will not reject
these transactions on the issuer’s behalf. The issuer will be responsible for responding
appropriately to these transaction requests.
Issuers supporting tokenized Cardless ATM transactions must be prepared to receive the
following, when applicable, in current messages:
• PAN mapping-related data
• Cryptography On-behalf service validation results
X-Code processing will not be available for Cardless ATM transactions. If processed via X-
Code, these transactions will be declined, though Mastercard will not send a decline advice
message to issuers.

Issuers that participate in the Mastercard Cardless ATM program must support new and
existing information to identify such transactions:
• New and existing information to identify Mastercard Cardless ATM transactions:
– Existing DE 3 (Processing Code), subfield 1 (Cardholder Transaction Type Code), value 01
(ATM Cash Withdrawal)
– Existing DE 22 (POS Entry Mode):
– Subfield 4 (Terminal Operating Environment), new value 8 (Additional Terminal
Operating Environments)
– Subfield 7 (Card Entry Mode), value R (PAN entry via electronic commerce, including
remote chip)
– Existing DE 26 (Card Acceptor Business Code [MCC]), value 6011 (Member Financial
Institution—Automated Cash Disbursements)
– New PDS 0022 (Additional Terminal Operating Environments), value A (Transaction has
acceptor facility) and value B (Transaction has been initiated remotely and completed at
a physical terminal off premises of the card acceptor facility).

Platform Impact
Some chargebacks are not allowed for Mastercard Cardless ATM transactions. If Mastercard
receives chargebacks containing Cardless ATM transaction information, Mastercard will reject
the request in First Chargeback/1442 and Arbitration Chargeback/1442 messages with the
following reason codes:
• 4837 (No Cardholder Authorization)
• 4863 (Cardholder Does Not Recognize—Potential Fraud)
• 4870 (Chip Liability Shift)
• 4871 (Chip Liability Shift—Lost/Stolen/Never Received Issue (NRI) Fraud)
Platform Impact
Dual Message System
Single Message
Message Flows
Message Layouts
IPM MPE √
Interchange

and Associated MCCs
Edits √ √ √
Error Numbers √
Pricing/Fees
Reports
Bulk Files
Forms
Reporting

Authorization
Dual Message System
Single Message
Transaction Investigator √
SAFE

Manager

Table File
Authorization
CIS Data Element Defintions


Subelement 28—Cardless ATM Order ID
Subelement 28 (Cardless ATM Order ID) is defined by the ATM operator, sent by the acquirer
participating in the Cardless ATM program and passed to the issuer participating in the
Cardless ATM program.
Attributes
Subelement ID: 28
Data Representation: an-10
Length Field: 2
Data Field: Fixed length, contents of positions 1–10
Subfields: N/A
Justification: N/A
Usage

Authorization
Following is the usage of subelement 28 (whether it is mandatory,

conditional, optional, system provided, or not required) in applicable
messages: Org Sys Dst
Authorization Request/0100 C X C
Values
Cannot contain all spaces or all zeros.
Subelement 29—Additional POS Terminal Locations

Subelement 29 is required when DE 61 (Point-of-Service [POS] Data), subfield 3 (POS Terminal
Location) is present with the value of 8 (Additional Terminal Operating Environments).
Attributes
Subelement ID: 29
Length Field: 01
Data Field: Contents of position 1
Subfields: N/A
Justification: N/A
Usage
Following is the usage of subelement 29 (whether it is mandatory,
conditional, optional, system provided, or not required) in applicable
messages: Org Sys Dst
Authorization Request/0100 C • C
Values
A = Transaction has been initiated remotely and completed at a physical terminal on
premises of the card acceptor facility.
B = Transaction has been initiated remotely and completed at a physical terminal off
DE 61—Point-of-Service (POS) Data

DE 61 (Point-of-Service [POS] Data) indicates the conditions that exist at the point of service at
the time of the transaction. Note that DE 61 supersedes and replaces the ISO-specified DE 25

Authorization
(Point-of-Service [POS] Condition Code) which is not used in the Customer Interface
Specification.
Subfield 3—POS Terminal Location
DE 61, subfield 3 (POS Terminal Location) indicates the terminal location.
Values
8 = Additional POS Terminal Locations
Edits
The Authorization Platform will perform the following system edits.
Modification to Existing System Edits
An Authorization Request/0100 message for a Rejects the message and sends the acquirer an
Cardless ATM transaction contains DE 48 Authorization Request Response/0110 message
(Additional Data), Transaction Category Code where:
(TCC), value Z (ATM)
DE 22 (Point-of-Service [POS] Entry Mode), (indicating the data element in error)
subfield 2 (POS Terminal PIN Entry Mode) value 1
(Terminal has PIN entry capability) is present, but
DE 22, subfield 1 (POS Terminal PAN Entry Mode)
contains a value other than 09 (PAN/Token entry
via electronic commerce containing DSRP
cryptogram in DE 55)
(Additional Data), Transaction Category Code where:
(TCC), value Z (ATM)
DE 22, subfield 1 (POS Terminal PAN Entry Mode) (indicating the data element in error)
is present and contains a value other than 09
(PAN/ Token entry via electronic commerce
containing DSRP cryptogram in DE 55), but DE 52
(Personal ID Number [PIN] Data) is not present
New System Edits

Authorization
Cardless ATM transaction does not contain DE 22 Authorization Request Response/0110 message
(Point-of-Service [POS] Entry Mode), subfield 2 where:
(POS Terminal PIN Entry Mode), value 1 (Terminal
has PIN entry capability) or value 8 (Terminal has
• DE 44 (Additional Response Data) = 022
PIN entry capability but PIN pad is not currently
operative)
(Additional Data), subelement 29 (Additional POS where:
Terminal Locations), value A (Transaction has been
initiated remotely and completed at a physical
terminal on premises of the card acceptor facility)
(indicating the data element and subelement
or value B (Transaction has been initiated remotely
in error)
and completed at a physical terminal off premises
of the card acceptor facility)
(Integrated Circuit Card [ICC] System-Related where:
Data])

Authorization
Cardless ATM transaction does not contain the Authorization Request Response/0110 message
following: where:
• DE 61 (Point-of-Service [POS] Data) • DE 39 (Response Code) = 30 (Format error)
– Subfield 1 (POS Terminal Attendance), value • DE 44 (Additional Response Data) = 061
1 (Unattended terminal [cardholder- (indicating the data element in error)
activated terminal (CAT), home PC, mobile
phone, PDA])
– Subfield 2 (Reserved for Future Use), value
0 (zero-filled)
– Subfield 3 (POS Terminal Location), value 8
(Additional POS Terminal Location)
– Subfield 4 (POS Cardholder Presence), value
5 (Electronic order [home PC, Internet,
mobile phone, PDA])
– Subfield 5 (POS Card Presence), value 1
(Card not present)
– Subfield 7 (POS Transaction Status), value 0
(Normal request [original presentment])
– Subfield 8 (POS Transaction Security), value
0 (No security concern)
0 (zero-filled)
– Subfield 10 (Cardholder-Activated Terminal
Level), value 6 (Authorized Level 6 CAT:
Electronic commerce)
Terminal Locations)
DE 61 (Point-of-Service [POS] Data), subfield 3 (indicating the data element and subelement
(POS Terminal Location) contains value 8 in error)
(Additional POS Terminal Locations)

Authorization
Terminal Locations)
(POS Terminal Location) contains a value other in error)
than 8 (Additional POS Terminal Locations)
Terminal Locations) with values other than A
(Transaction has been initiated remotely and
completed at a physical terminal on premises of
the card acceptor facility) or B (Transaction has
in error)
been initiated remotely and completed at a
physical terminal off premises of the card acceptor
facility)
Terminal Locations) and the length is not 01
in error)
(Additional Data), subelement 28 (Cardless ATM where:
Order ID) where the length is not 10 characters
and there are all spaces or all zeros
in error)

Clearing
(Additional Data), subelement 28 (Cardless ATM where:
Order ID)
in error)
A Cardless ATM transaction is submitted and is Rejects the message and sends the acquirer an
routed to X-Code for processing Authorization Request Response/0110 message
where:
• DE 39 (Response Code) = 05 (Do not honor)
Clearing

DE 22—Point of Service (POS) Entry Mode

DE 22 (Point of Service [POS] Entry Mode) is a series of codes that identify terminal capability,
terminal environment, and point-of-interaction (POI) security data.
Subfield 4—Terminal Operating Environment
DE 22 (Point of Service [POS] Entry Mode), subfield 4 indicates whether the card acceptor is
attending the terminal and the location of the terminal.
Values Description
8 Additional Terminal Operating Environments
PDS 0022—Additional Terminal Operating Environments

PDS 0022 (Additional Terminal Operating Environments) identifies a Cardless ATM transaction.
Attributes
Data Representation: ans–1; TAGLLL

Clearing
Tag Field: 0022
Length Field: 3 positions, value = 001
Data Field: Fixed length, 1 position
Subfields: None
Justification: N/A
Usage
The following table shows the usage of this PDS (whether it is mandatory, conditional,
optional, system-provided, or not required) in applicable messages.
Message Type Identifier Org Sys Dst
Presentment Message
First Presentment/1240 C • C
Values
Value Description
A Transaction has been initiated remotely and completed at a physical terminal on

B Transaction has been initiated remotely and completed at a physical terminal off
IPM MPE
The IPM Member Parameter Extract (MPE) contains all of the parameters that the IPM Pre-edit
uses to edit the customer’s Clearing files and to run the IPM utilities.
Mastercard will add IPM MPE table IP2203T1—Cardless ATM.
Mastercard will modify these IPM MPE tables:
• IP0008T1—PDS Attributes for new PDS 0022 (Additional Terminal Operating Environments)
• IP2004T1—DE 22 (Point of Service Data Code), subfield 4, (Terminal Operating
Environment) for new value 8 (Additional Terminal Operating Environments)
Mastercard will include these changes in the 19.Q2 GCMS Parameter Table Layouts.

Clearing
Edits
announcement.
New Edit—PDS 0022 (Additional Terminal Operating Environments)

This edit validates that PDS 0022 must contain a length value of 001.

0428 The Clearing Platform will ensure that if PDS 0022 is present, the
length must be 001.
New Edit—DE 22 (Point of Service [POS] Entry Mode), Subfield 7 (Card Entry Mode)
This edit validates that chargebacks with reason codes 4837 (No Cardholder Authorization),
4863 (Cardholder Does Not Recognize—Potential Fraud), 4870 (Chip Liability Shift), and 4871
(Chip Liability Shift—Lost/Stolen/Never Received Issue (NRI) Fraud) are not supported for
Cardless ATM (DE 22 [Point of Service (POS) Entry Mode], subfield 7 [Card Entry Mode], value
R [PAN entry via electronic commerce, including remote chip]) and DE 26 (Card Acceptor
Business Code [MCC]), value 6011 (Member Financial Institution—Automated Cash
Disbursements) transactions.

2267 The Clearing Platform will ensure that chargebacks with the following
reason codes are not supported for Cardless ATM (DE 22, subfield 7,
value R) and DE 26 (Card Acceptor Business Code [MCC] value 6011)
transactions: 4837, 4863, 4870, and 4871.

Clearing

This edit validates that PDS 0022 is present when DE 22 (Point of Service [POS] Entry Mode),
subfield 4 (Terminal Operating Environment) contains value 8 (Additional Terminal Operating
Environments).

2894 The Clearing Platform will ensure that PDS 0022 is present when DE
22, subfield 4 contains value 8.
This edit is performed in Clearing Optimizer and at the Central Site for the following message:

This edit validates that PDS 0022 contains value A (Transaction has been initiated remotely
and completed at a physical terminal on premises of the card acceptor facility) or B
(Transaction has been initiated remotely and completed at a physical terminal off premises of
the card acceptor facility) for a Cardless ATM transaction.

2895 The Clearing Platform will ensure that PDS 0022 contains value A or B
for a Cardless ATM transaction (DE 3, subfield 1, value 01).
New Edit—DE 22 (Point of Service [POS] Entry Mode), subfield 4 (Terminal Operating
Environment)
This edit validates that DE 22 (Point of Service [POS] Entry Mode), subfield 4 (Terminal
Operating Environment) contains value 8 (Additional Terminal Operating Environments) when
PDS 0022 (Additional Terminal Operating Environments) is present.

2896 The Clearing Platform will ensure that DE 22, subfield 4 contains value
8 when PDS 0022 is present for messages DE 3, subfield 1, value 01.

Clearing

• Collection Only messages
• IRD 51, 75, 85, or 88 for
– BS Level 4, BS ID 826001
– BS Level 8, all BS IDs
Modified Edit—DE 22 (POS Entry Mode), Subfield 4 (Terminal Operating Environment)

Mastercard will modify the following edit to include value 4 (Off card-acceptor premises;
unattended) or 8 (Additional Terminal Operating Environments) in DE 22, subfield 4 for
domestic U.K. ATM transactions for applicable IRDs.

that DE 22, subfield 4 contains include value 8 in addition to value
value 4 for domestic U.K. ATM 4 in DE 22, subfield 4.
Transactions for the applicable
IRDs.

Clearing
Modified Edit—DE 22 (POS Entry Mode), Subfield 4 (Terminal Operating Environment

Mastercard will modify the following edit to include value 8 in addition to value 4 in DE 22,
subfield 4 for domestic U.K. ATM transactions for IRD 89 or IRD 54.

that DE 22, subfield 4 contains include value 8 in addition to value
value 4 for domestic U.K. ATM 4 in DE 22, subfield 4. Additionally,
transactions with IRD 89 (Remote for domestic U.K. ATM
mag stripe) or IRD 54 (Remote transactions with IRD 89 or IRD 54.
combined chip EMV and mag This edit will be performed for
stripe). This edit is to be performed Region D to Region D Member to
for Region D to Region D Member Member business services if the
to Member business services if any country code for either the
of the country codes for the acquirer or the issuer is equal to
acquirer and the country code of Great Britain (GBR).
the issuer is equal to Great Britain
(GBR).

Mastercard will modify the following edit to not allow value 4 (Off card-acceptor premises;
unattended) or 8 (Additional Terminal Operating Environments) in DE 22, subfield 4 for
intracountry U.K. ATM transactions for applicable IRDs.

that DE 22, subfield 4 does not exclude value 8 when PDS 0022 =
contain value 4 for intracountry B in addition to value 4 in DE 22,
U.K. ATM Transactions for subfield 4. Additionally, for
applicable IRDs. intracountry U.K. ATM transactions
for applicable IRDs.

Clearing

Mastercard will modify the following edit to exclude value 4 (Off card-acceptor premises;
unattended) or 8 (Additional Terminal Operating Environments) in DE 22, subfield 4 for U.K.
ATM Member to Member transactions with IRDs 51, 75, 85, or 88.

that DE 22, subfield 4 does not exclude value 8 when PDS 00022
contain value 4 for U.K. ATM = B in addition to value 4 in DE 22,
Member to Member transactions subfield 4. Additionally, for for
with IRDs 51, 75, 85, or 88. This U.K. ATM Member to Member
edit is to be performed for Region transactions with IRDs 51, 75, 85,
D to D Member to Member or 88. This edit will be performed
business services if any of the for Region D to D Member to
country code for the acquirer and Member business services if any of
the country code of the issuer is the country code for the acquirer
equal to Great Britain (GBR). and the country code of the issuer
is equal to Great Britain (GBR).
Error Numbers
Edit
Error Performed
PDS 0022 0428 <FLDNAME> must be fixed length of 001. Both
DE 22, s7 2267 < FLDNAME> invalid for this <MSGETYPE>. Both
PDS 0022 2894 <FLDNAME> must be present when DE22,S4 is a value Both
of 8.
PDS 0022 2895 <FLDNAME> must be a value of A or B when DE22,S7 = Both

R.
DE 22, s4 2896 <FLDNAME> must have value of 8. Both

Edit
Error Performed
DE 22, s4 2134 <FLDNAME> must be 4 or 8. Both
DE 22, s4 2134 <FLDNAME> must be 4 or 8. Both
DE 22, s4 2423 <FLDNAME> must not be 4 or 8. Both
DE 22, s4 2424 <FLDNAME> must not be 4 or 8. Both
Mastercard will update the Clearing Transaction Investigator tool as follows to support this
announcement.
• New value 8 (Additional POS Terminal Locations) in DE 22 (Point of Service [POS] Entry
Mode), subfield 4 (Terminal Operating Environment).
• New PDS 0022 (Additional Terminal Operating Environments), values A (Transaction has
acceptor facility) and B (Transaction has been initiated remotely and completed at a
physical terminal off premises of the card acceptor facility).


Subelement 28—Cardless ATM Order ID
Subelement 28 (Cardless ATM Order ID) is defined by the ATM operator, sent by the acquirer
participating in the Cardless ATM program and passed to the issuer participating in the
Cardless ATM program.
Attributes
Subelement ID: 28
Length Field: 2

Data Field: Fixed length, contents of positions 1–10
Subfields: N/A
Justification: N/A
Values Description
Cannot contain all spaces or all zeros.
Subelement 29—Additional POS Terminal Locations

Subelement 29 is required when DE 61 (Point-of-Service [POS] Data), subfield 3 (POS Terminal
Location) is present with the value of 8 (Additional Terminal Operating Environments).
Attributes
Subelement ID: 29
Length Field: 01
Data Field: Contents of position 1
Subfields: N/A
Justification: N/A
Values Description
A Transaction has been initiated remotely and

the card acceptor facility.
B Transaction has been initiated remotely and

completed at a physical terminal off premises of
the card acceptor facility.
DE 61—Point of Service (POS) Data

DE 61 (Point-of-Service [POS] Data) indicates the conditions that exist at the point of service at
the time of the transaction. Note that DE 61 supersedes and replaces the ISO-specified DE 25

(Point-of-Service [POS] Condition Code) which is not used in the Single Message System
Specifications.
Subfield 3–POS Terminal Location
DE 61, subfield 3 (POS Terminal Location) indicates the terminal location.
Values Description
8 Additional POS Terminal Locations
Edits
Modification to Existing System Edits
Mode), subfield 1 (POS Terminal PAN Entry Mode) message where:
equal to value 09 (PAN/Token entry via electronic
commerce containing DSRP cryptogram in DE 55
(Integrated Circuit Card [ICC] System-Related
Data)
and
Is not a Cardless ATM transaction
and
DE 52 (Personal ID Number [PIN] Data) is not
present

value 09 (PAN/Token entry via electronic
Data)
and
DE 61 (Point-of-Service [POS] Data), subfield 3
(POS Terminal Location) contains values other than
2 (Off premises of card acceptor facility
[cardholder terminal including home PC, mobile
phone, PDA]), 4 (On premises of card acceptor
facility [cardholder terminal including home PC,
mobile phone, PDA], or 8 (Additional POS
Terminal Locations)
value 09 (PAN/Token entry via electronic
Data)
and
DE 52 (Personal ID Number [PIN] Data) is not
present or equal to spaces
except when
DE 18 (Merchant Type), value 6011 (Automated
Cash Disbursement)
and
DE 48 (Additional Data), Transaction Category
Code (TCC), value Z (ATM)
New System Edits

A Financial Transaction Request/0200 message for Rejects the message and sends the acquirer a
a Cardless ATM transaction does not contain DE Financial Transaction Request Response/0210
22 (Point-of-Service [POS] Entry Mode), subfield 2 message where:
(POS Terminal PIN Entry Mode), value 1 (Terminal
has PIN entry capability) or value 8 (Terminal has
PIN entry capability but PIN pad is not currently
operative)
in error)
48 (Additional Data), subelement 29 (Additional message where:
POS Terminal Locations), value A (Transaction has
physical terminal on premises of the card acceptor
facility) or value B (Transaction has been initiated
in error)
remotely and completed at a physical terminal off
premises of the card acceptor facility)
55 (Integrated Circuit Card [ICC] System-Related message where:
Data])

a Cardless ATM transaction does not contain the Financial Transaction Request Response/0210
following: message where:
• DE 61 (Point-of-Service [POS] Data) • DE 39 (Response Code) = 30 (Format error)
– Subfield 1 (POS Terminal Attendance), value • DE 44 (Additional Response Data) = 061
1 (Unattended terminal [cardholder- (indicating the data element in error)
activated terminal (CAT), home PC, mobile
phone, PDA])
0 (zero-filled)
– Subfield 3 (POS Terminal Location), value 8
(Additional POS Terminal Location)
– Subfield 4 (POS Cardholder Presence), value
5 (Electronic order [home PC, Internet,
mobile phone, PDA])
– Subfield 5 (POS Card Presence), value 1
(Card not present)
– Subfield 7 (POS Transaction Status), value 0
(Normal request [original presentment])
– Subfield 8 (POS Transaction Security), value
0 (No security concern)
0 (zero-filled)
– Subfield 10 (Cardholder-Activated Terminal
Level), value 6 (Authorized Level 6 CAT:
Electronic commerce)
48 (Additional Data), subelement 29 (Additional where:
POS Terminal Locations)
(POS Terminal Location) contains value 8 in error)
(Additional POS Terminal Locations)

a Cardless ATM transaction contains DE 48 Financial Transaction Request Response/0210
(Additional Data), subelement 29 (Additional POS message where:
Terminal Locations)
(POS Terminal Location) contains a value other in error)
than 8 (Additional POS Terminal Locations)
Terminal Locations) with values other than A
(Transaction has been initiated remotely and
the card acceptor facility) or B (Transaction has
in error)
physical terminal off premises of the card acceptor
facility)
Terminal Locations) and the length is not 01
in error)
(Additional Data), subelement 28 (Cardless ATM message where:
Order ID) where the length is not 10 characters
and there are all spaces or all zeros
in error)

48 (Additional Data), subelement 28 (Cardless message where:
ATM Order ID)
in error)

AN 2137—New Edits for Japan Domestic Transactions
Chapter 28 AN 2137—New Edits for Japan Domestic

Transactions
Mastercard is removing Japan National Data from DE 112 (Additional Data [National Use]) on all
authorization request and response messages for cross-border transactions. Mastercard is also
introducing a new clearing edit to validate the number of installments requested when the
installment payment option is selected.
AN 2137—New Edits for Japan Domestic Transactions ............................................................... 410

Version History............................................................................................................................410
At-A-Glance................................................................................................................................410
Overview.................................................................................................................................... 411
Customer Impact........................................................................................................................ 412
Enhancements............................................................................................................................ 414
Platform Impact.......................................................................................................................... 415
Authorization..............................................................................................................................416
DE 112—Additional Data (National Use)............................................................................ 416
Clearing......................................................................................................................................417
Edits.......................................................................................................................................417
New Edit—PDS 0195 (Installment Data), Subfield 1 (Total Number of Installments).............417
Error Numbers................................................................................................................... 418


Mastercard is removing Japan National Data from DE 112 (Additional Data [National Use]) on
all authorization request and response messages for cross-border transactions. Mastercard is
also introducing a new clearing edit to validate the number of installments requested when
the installment payment option is selected.
Version History

At-A-Glance

Release: 19.Q2
Region: Asia/Pacific
Action Indicator:
Attention warranted (Program/service-related)—Acquirers and issuers in
Japan
Testing recommended—Acquirers

Overview
Overview
Background
Japan Payment Options include various installment options, for example: payments options
based on cardholder salary bonus dates, settlement delayed concentrated on two dates per
year, and settlement split across two different settlement dates. For a Japan-issued card,
payment options are offered to the cardholder at point of sale. When the installment option is
selected, the cardholder designates the number of installments to be made. The payment
option information is included in both authorization and clearing messages.

DE 112 is used by acquirers in Japan to provide market specific data on Japan domestic
transactions.
There is no clearing edit available to prevent acquirers from submitting Japan Installment
transactions with value 000 or 001 in PDS 0195 (Installment Data), subfield 1 (Total Number
of Installments) when PDS 0195, subfield 2 (Payment Option Code) contains value 61
(Installments [Twice Pay/Three or more]).
For Japan domestic transactions, acquirers add national data to DE 112, subelement 030
(Japan Domestic POS Data) and subelement 032 (Japan Payment Options) in Authorization
Request/0100 and Reversal Request/0400 messages, while issuers may add subelement 031
(Japan Domestic Response Code) in Authorization Request Response/0110 and Reversal
Request Response/0410 messages. In a cross-border transaction (either the acquirer or the
issuer is not in Japan), Mastercard removes subelement 030 from the authorization message,
but, if present, subelements 031 and 032 are not removed. This data should not be included
in cross-border transactions as non-Japan issuers may not be prepared to process it.

If present, Mastercard will remove DE 112, subelement 032 from the Authorization Request/
0100 and Reversal Request/0400 messages of all cross-border transactions when the acquirer
or the issuer country code is not 392 (Japan).
If present, Mastercard will remove DE 112, subelements 031 and 032 from the Authorization
Request Response/0110 and Reversal Request Response/0410 messages of all cross border
transactions when the acquirer or the issuer country code is not 392 (Japan).
A new clearing edit will be introduced to prevent acquirers from submitting Japan Installment
transactions with value 000 or 001 in PDS 0195, subfield 1 when PDS 0195, subfield 2
contains value 61.


The new functionality for DE 112 Japan Payment Transactions subfields will prevent issuers
outside of Japan from receiving Japan National Data. Acquirers can populate these subfields
without concern if the authorization message is for a domestic or cross-border transaction.
The new clearing edit will prevent acquirers from sending an incorrect combination of values
related to installment payments to the issuer.
Issuers in Japan will be assured that DE 112, subfield 030 and subfield 032 will only be
present in the authorization message for domestic transactions and not present for cross-
border transactions.
Announcements
• “AP 123—Expansion of DE 112 to Support Japan National Data,” Release 17.Q1
• “AP 531—Japan Payment Options Enhancements,” Release 17.Q1
• “AP 110—DE 112 Update to Support Japan National Data,” Release 16.Q2
Reference Manuals
Refer to these manuals for information about the current state of Mastercard processing:
manuals.
Customer Impact

Attention warranted (Program/service-related)—Acquirers in Japan that submit Japan Payment
Transactions will not be required to remove DE 112, subelement 31 and subelement 32 from
cross-border transactions as Mastercard will perform this action.

Customer Impact
Acquirers in Japan that submit Japan Payment Transactions must comply with the new
clearing edit that validates an installment transaction submitted with the number of
installments contained in PDS 0195, subfield 1 is not 000 or 001 when PDS 0195, subfield 2
contains value 61.
Attention warranted (Program/service-related)—Issuers in Japan that receive Japan Payment
Transactions must be aware of the new clearing edit on installment transactions.
Testing recommended—Mastercard recommends that participating acquirers perform testing.
Implementation Alert—Acquirers and issuers in Japan must be aware of the dual effective
dates for this initiative.
• The Dual Message System (Authorization) enhancements as described in this
announcement will be effective on the MIP roll date–11 June 2019
If an acquirer sends DE 112, subelement 32 prior to 11 June 2019, the subelement will be
forwarded to the issuer.
• The Dual Message System (Clearing) enhancements as described in this announcement will
be effective on the Release 19.Q2 Implementation date—12 April 2019

Message System:

Enhancements
Enhancements
Dual Message System (Authorization)—Acquirers

• Mastercard currently removes DE 112 (Additional Data [National Use]), subelement 030
(Japan Domestic POS Data) from all cross-border Japan Payment Transactions. The
following will be added to the Application Notes of subelement 030 to document this
activity:
– If provided, Mastercard will remove subelement 030 from the Authorization Request/
0100, Authorization Request Response/0110, Reversal Request/0400, and Reversal
Request Response/0410 messages when the acquirer or the issuer country code is not
392 (Japan).
• The following Application Note will be added to DE 112, subelement 031 (Japan Domestic
Response Code):
– If present, Mastercard will remove subelement 031 from the Authorization Request
Response/0110 and Reversal Request Response/0410 messages when the acquirer or
the issuer country code is not 392 (Japan).
• This paragraph in the Application Notes of DE 112, subelement 032 (Japan Payment
Options) will be updated as follows:
– Mastercard provides subelement 032 to facilitate communication of data between the
acquirer and issuer. Mastercard does not enforce edits to check the presence of any
data. Transactions that do not include DE 112, subelement 032 data will not be
rejected. Mastercard will remove subelement 32 from the Authorization Request/0100,
Authorization Request Response/0110, Reversal Request/0400, and Reversal Request
Response/0410 messages when the acquirer or the issuer country code is not 392
(Japan).

Mastercard will introduce a new clearing edit, applicable only to BSA 4/392001, for PDS 0195
(Installment Data), subfield 1 (Total Number of Installments) to reject Japan domestic
installment activity when PDS 0195, subfield 2 (Payment Option Code) contains value 61 and
the value contained in PDS 0195, subfield 1 is not 000 or 001.

Platform Impact
Platform Impact
Dual Message System
Single Message
Message Flows
Message Layouts
Data Element Definitions √
IPM MPE
Interchange

and Associated MCCs
Edits √
Error Numbers √
Pricing/Fees
Reports
Bulk Files
Forms
Reporting
SAFE

Manager

Table File

Authorization
Authorization

DE 112—Additional Data (National Use)

DE 112 (Additional Data [National Use]) is reserved for national organizations to define data
It is a free-format, variable-length, alphanumeric data element used for information on
transactions between customers.
Subelement 030—Japan Domestic POS Data
Subelement 030 (Japan Domestic POS Data) is used in the Authorization Platform to provide
data required by acquirers and issuers in Japan for intracountry processing.
Application Notes
Because DE 112, subelement 030 contains unique data specific to acquirers and issuers in Japan,
Mastercard does not enforce the use of DE 112, subelement 030.
If provided, Mastercard does not validate the contents of DE 112, subelement 030.
If provided, Mastercard will remove subelement 030 from the Authorization Request/0100,
Authorization Request Response/0110, Reversal Request/0400, and Reversal Request Response/0410
messages when the acquirer or the issuer country code is not 392 (Japan).
Subelement 031—Japan Domestic Response Code

Subelement 031 (Japan Domestic Response Code) is used in the Authorization Platform to
provide data required by acquirers and issuers in Japan for intracountry processing.
Application Notes
If present, Mastercard will remove subelement 031 from the Authorization Request Response/0110
and Reversal Request Response/0410 messages when the acquirer or the issuer country code is not
392 (Japan).
Subelement 032—Japan Payment Options

Subelement 032 (Japan Payment Options) is used in the Authorization Platform to provide
data for domestic Japan installment payments. The term bonus used in this subelement and
related subfields refers to a salary bonus. In Japan, there can be one or two salary bonuses
paid per year.
Application Notes

Clearing
If subelement 032 is present then all subfields must also be present.

Mastercard provides subelement 032 to facilitate communication of data between the acquirer and
issuer. Mastercard does not enforce edits to check the presence of any data. Transactions that do not
include DE 112, subelement 032 data will not be rejected.
Mastercard will remove subelement 32 from the Authorization Request/0100, Authorization Request
Response/0110, Reversal Request/0400, and Reversal Request Response/0410 messages when the
acquirer or the issuer country code is not 392 (Japan).
Clearing
Edits
announcement.
New Edit—PDS 0195 (Installment Data), Subfield 1 (Total Number of Installments)

The edit performed on PDS 0195, subfield 1 will prevent Japan domestic installment
transactions from being submitted with the number of installments as 000 or 001 when the
Payment Option code indicates Twice Pay/Three or more. This edit is applicable only to BSA
4/392001.

2866 The Clearing Platform will ensure when PDS 0195 (Installment Data),
subfield 2 (Payment Option Code) contains value 61 (Installments
[Twice Pay/Three or more]), the number of installments indicated in PDS
0195, subfield 1 (Total Number of Installments) must not be value 000
or 001.

Clearing
Error Numbers
Edit
Error Performed
PDS0195, S1 2866 THE NUMBER OF INSTALLMENTS IN PDS0195S1 Both

CANNOT BE LESS THAN OR EQUAL TO 001.

AN 2138—Mastercard Network—Secured Mastercard Interface Processor (MIP) Customer Connectivity
(TLS1.2)
Chapter 29 AN 2138—Mastercard Network—Secured

Mastercard Interface Processor (MIP) Customer
Connectivity (TLS1.2)
Mastercard Network – MIP Connectivity for Customers is offering secured TCP/IP connectivity (aka
TLS connectivity) for customer hosts.
AN 2138—Mastercard Network—Secured Mastercard Interface Processor (MIP) Customer

Connectivity (TLS1.2).................................................................................................................. 420
Version History............................................................................................................................420
At-A-Glance................................................................................................................................420
Enhancements............................................................................................................................ 421

(TLS1.2)
(TLS1.2)
AN 2138—Mastercard Network—Secured Mastercard Interface

Processor (MIP) Customer Connectivity (TLS1.2)
Mastercard Network – MIP Connectivity for Customers is offering secured TCP/IP connectivity
(aka TLS connectivity) for customer hosts.
Version History

At-A-Glance

Release: 19.Q2
System: N/A
Region: All
Action Indicator:
Effective Date: 12 April 2019

(TLS1.2)
Enhancements
Enhancements
Mastercard Network – MIP Connectivity for Customers will offer secured TCP/IP connectivity
(aka TLS connectivity) for customer hosts.
The Mastercard Network is the primary communications facility that links all Mastercard
members and Mastercard processing centers including cloud based connectivity into a single,
worldwide, online payments network. It is designed for reliability, redundancy, and both peer-
to-peer and centralized transaction processing, both on customer premises and in the cloud.
Customers connect to the Mastercard network via MIP, which serves as a front-end
communications processor. The MIP is located on-site at the customer facility, Mastercard
Global Data Centers, or via Equinix Cloud Exchange (ECX) for cloud customers.
Mastercard uses various practices to ensure that customer communications carried through
the network are safe, including end-to-end encryption of data at rest and in transit once
inside the Mastercard network.
The MIP functions as a proxy server and restricts network traffic to authorized payments
network features and commands. The MIP prevents direct contact between the Mastercard
Network and the user network.
Customer host systems can connect to MIP services only through specified addresses and
specified ports. The MIP permits connections only from the member host IP addresses that
Mastercard has defined.
Mastercard disables IP Forwarding and offers no TCP or IP pass-through service on the MIP.
The MIP terminates all customer host connections so that TCP sockets on the customer side of
the MIP are separate from TCP sockets on the Mastercard side of the MIP. The MIP passes only
validated data messages between Mastercard systems and customer hosts.
Mastercard Network – MIP Connectivity for Customers now offers secured TCP/IP connectivity
(aka TLS connectivity) for customer hosts. To establish secured MIP Connectivity (TLS1.2), the
connection between Mastercard and the customer host must adhere to the high-level
requirements listed below.
• Mastercard and Customer Host IP addresses and ports must be identified and agreed upon
and may be separate from existing connections.
• All certificates will be issued by the Mastercard Certificate Authority (CA), which is regularly
audited and operates out of secured computing facilities.
• Mastercard will share a private Mastercard CA certification chain.
• The MIP will be configured as a TLS Server, and the Customer Host System must be
configured as a Client.
• The Customer Host must validate the certificate presented by the MIP against the
Mastercard CA certification chain to ensure authenticity and confidentiality.
• Once the TLS connection is established, the Customer Host can start sending data
messages to the MIP using an encrypted connection.

(TLS1.2)
Enhancements
Customers interested in participating, must complete the following to support this

announcement:
• Customers must request a Mastercard project manager from Customer Implementation
Services (CIS) team to request Secured Mastercard MIP Connectivity.
• Customers must provide the CIS team with the names of two Information Security Officers.
Phone numbers and email addresses will also be required to support a Mastercard
Certification.
NOTE: At this time, the secured TCP/IP connectivity is optional. If this changes, an update will
be published.

AN 2139—IIAS Real-time Substantiation for Vision Enhancement
Chapter 30 AN 2139—IIAS Real-time Substantiation for

Vision Enhancement
Mastercard is announcing the clearing edits that support IIAS Real-time Substantiation for Vision Rx
Eligibility Amounts will be available at Central Site and in Clearing Optimizer.
AN 2139—IIAS Real-time Substantiation for Vision Enhancement............................................... 424

Version History............................................................................................................................424
At-A-Glance................................................................................................................................424
Enhancements............................................................................................................................ 425
Edits........................................................................................................................................... 426
Error Numbers........................................................................................................................426


Mastercard is announcing the clearing edits that support IIAS Real-time Substantiation for
Vision Rx Eligibility Amounts will be available at Central Site and in Clearing Optimizer.
Version History
8 Jan 2019 Added Clearing Edit Error Number 2727 for DE 3, subfield 1 Error Numbers
to the listing of edits that will be available at Central Site and
in Clearing Optimizer.
At-A-Glance

Release: 19.Q2
Region: All
System: Clearing
Action Indicator:

Enhancements
Program or service requirement—Acquirers in the U.S. region must support

the enhancements as described in this announcement in preparation for
when the vision amount type is available.
Program or service requirement—Acquirers globally will see the
modifications as described in this announcement.
Program or service requirement—Issuers in the U.S. region must support the
enhancements as described in this announcement in preparation for when
the vision amount type is available.
Program or service requirement—Issuers globally will see the modifications
as described in this announcement.
Testing recommended—Mastercard recommends testing for this release

announcement for participating acquirers and issuers.
Enhancements
Mastercard will modify the Clearing Platform to support these changes.
Mastercard initiated a phased approach to the modification of the Real-time Substantiation
service to include the vision prescription (Rx) total amounts as a qualified healthcare expense.
As described in Release 18.Q4, “AN 1639—IIAS Real-time Substantiation for Vision
Enhancement,” specified clearing edits were restricted to Central Site processing only.
Mastercard is announcing these specified clearing edits will now be available at Central Site
and in Clearing Optimizer (previously referred to as Pre-Edit).
Related Announcements
Information relevant to this release announcement can be found in these previously published
announcements available on Mastercard Connect™.
• “AN 2103—IIAS Real-time Substantiation for Vision Enhancement for the U.S. Region,”
Release 19.Q1
• “AN 1639—IIAS Real-time Substantiation for Vision Enhancement,” Release 18.Q4

Edits
Edits
announcement.
Error Numbers
The edits represented by the error numbers listed below will be available at Central Site and in
Clearing Optimizer.
Field/Subfield Error Number Edit Performed By...
DE 3, s1 2716 Both
DE 3, s1 2727 Both
DE 4 2711 Both
DE 25 2324 Both
DE 54 2470 Both
DE 54, s2 2312 Both
DE 54, s2 2436 Both
DE 54, s2 2265 Both
DE 54, s3 2292 Both
DE 54, s3 2469 Both
DE 54, s3 0122 Both
DE 54, s4 2185 Both
DE 54, s4 2313 Both
DE 54, s5 2183 Both
DE 54, s5 2294 Both
DE 54, s5 2479 Both
DE 54, s5 2526 Both

AN 2140—2019 Switching Release Resources and Frequently Asked Questions
Chapter 31 AN 2140—2019 Switching Release Resources

and Frequently Asked Questions
Use this document to understand switching release resources and frequently asked questions
(FAQs).
AN 2140—2019 Switching Release Resources and Frequently Asked Questions ......................... 428
Version History............................................................................................................................428
2019 Release Resources.............................................................................................................. 428
Preparing for the Switching Release........................................................................................429
Requesting Help..................................................................................................................... 431
Community Runs....................................................................................................................432
Freeze Dates...........................................................................................................................432
Distribution of IPM MPE Files.................................................................................................. 433
Interchange............................................................................................................................435
IPM Clearing Optimizer and Utilities Software Global Rollout.................................................. 435
MIP Initial Program Load.........................................................................................................435
Release Implementation......................................................................................................... 436
Testing................................................................................................................................... 436
Timing (Sequence of Events)...................................................................................................438

AN 2140—2019 Switching Release Resources and Frequently Asked

Questions
Use this document to understand switching release resources and frequently asked questions
(FAQs).
Version History

2019 Release Resources

Mastercard communicates upcoming changes to systems, platforms, or products through
switching release announcements on the Technical Resource Center. Each enhancement is
detailed in its own announcement. For details about switching release enhancements, use
these resources.
Tracking Spreadsheet
The Announcement Summary Report is produced each Wednesday and posted on the
Technical Resource Center. The report allows sorting and filtering on particular values so
customers can track announcements in an easily customizable Excel format.
Using the summary report, customers may notice that announcement numbers are not
consecutive or sequential. Please note that announcement numbers serve only as quick
reference. The numbers do not denote any meaning.
Bundled Snapshots
Snapshots contain only those announcements that are handled as part of the switching
release. Because some announcements may not fit the criteria for handling as a release
announcement, a related bulletins announcement is included with each release and in each
bundled snapshot.
• AN 2132—19.Q2 Switching Release Announcements—Bundled Snapshot
• AN 2600—19.Q4 Switching Release Announcements—Bundled Snapshot (Future
Publication)

• AN 2601—Switching Release 19.Q3—Related Bulletins (Future Publication)

• AN 2602—Switching Release 19.Q4—Related Bulletins (Future Publication)
Milestones and Freeze Dates

These announcements apply more generally to the switching release overall:
• AN 1609—2019 Switching Release Customer Milestones By Quarter
• AN 1610—19.Q1 Switching Release Milestones
• AN 1367—Freeze Dates to Support Dual Message System and Single Message System
2019 Release Implementations

These frequently asked questions (FAQs) are designed to provide a better understanding about
switching releases and may provide answers to some common questions.
Preparing for the Switching Release

These questions and answers will assist customers in reviewing the Switching Release
documentation.
Q: Where can I find release documentation?

A: Switching release announcements are available on the Technical Resource Center (TRC). Refer to
the Release Resources section for specific details.
Q: When is release documentation available?

A: Switching release announcements are published according to AN 1609—2019 Switching Release
Customer Milestones By Quarter.
Q: What does AN mean?

A: AN is the acronym for Announcement Number (AN), which is an abbreviated method of quickly
referring to announcements. The numbers are not consecutive or sequential. The announcement
numbers serve only as quick reference and do not denote any meaning.

Q: How do I know if an announcement is a bulletin or a release announcement?

A: The first row of the At-A-Glance table will indicate the type of announcement. The choices are
Type: Bulletin or Type: Switching Release. Another option is to refer to the tags that display the
Type. Tags display on the announcements results page under the announcement title. Tags also
display in open announcements at the bottom of the page.
Q: How can I access all of the release announcements for a specific release?
A: To access the announcements individually, follow these steps:
™
1. Sign into Mastercard Connect
2. From the Technical Resource Center home page, click Announcements. The announcements
results page displays. This is a list of all announcements that you are entitled to see that have
been published, with the most recently published listed first.
3. Click Filter.
4. Under Release, choose the Release Number (for example, 19.Q2), and then click Apply. All
announcements tagged with 19.Q2 will display.
To access the announcements collectively, refer to the Bundled Snapshot. It is available under Quick
Links on the Technical Resource Center home page.
Q: How do I know when all the enhancements for a release have been announced? What is the
timing of announcements?
A: Mastercard makes every effort to include all release enhancements in the first publication, available
according to the publication milestone dates. The goal is to include only smaller efforts and minor
updates in the second publication, and few to no changes in any subsequent publications. Regulatory
or significant business requirements may necessitate exceptions.
Q: If I review only release announcements, am I seeing everything that I could possibly need to
prepare for this release?
A: Customers are responsible for reviewing all announcements and understanding impact on their
own business or operations. With each release, Mastercard includes an announcement (identified as
part of the Release) that links to related bulletin announcements. Consider using the Announcement
Summary Report, available on the Technical Resource Center under Quick Links, to filter on any of a
number of fields that may help you to better manage the volume and velocity of content.

Q: Why am I getting results that look like random topics when I try to filter for specific
announcements?
A: Follow these steps:
1. Check that you are filtering from the announcements results page. Go to the Technical Resource
Center home page, find the square that is labeled Announcements, and click it! The resulting
page is the announcement results page. This is a list of all announcements that you are entitled to
see that have been published, with the most recently published listed first.
2. Click Filters and choose from the options available.
Q: When will the manuals be updated with the information provided in these release
announcements?
A: The information provided in announcements on the Technical Resource Center is subsequently
incorporated into References (manuals and guides, for example) that are available through
Publications on Mastercard Connect. Mastercard makes every effort to update reference
documentation in the thirty to sixty days following release implementation. References reflect the
operating state of Mastercard systems as of the publication date on the document.
Requesting Help
These questions and answers will assist customers in seeking assistance with release
documentation.
Q: Who do I contact if I don’t understand a release announcement? How do I get help?

A: Contact the Global Customer Service team by emailing customer_support@mastercard.com.
To facilitate more efficient routing of inquiries related to switching release announcements (or bulletin
announcements clearly related to the release), include a subject line that references the
announcement number and the word Release, for example, “AN 0000 Release 19.Q1.”
TIP: Submit a single email for each release announcement. If you have questions about
multiple release announcements, submit them in separate emails.

Q: What if I don’t get a response in a timely manner? How do I escalate?

A: The goal is to answer release related inquiries in the least amount of time as possible, and our
current service level agreement is to answer 95% of submitted questions within 4 business days. If
your inquiry has been waiting beyond the SLA, send an email (and include the reference number) to
gcs_escalation@mastercard.com.
Community Runs
Q: How do I participate in or register for a Community Run?

A: No registration is required; however, all customers are encouraged to participate in the Community
Run processing, as communicated in the Release Milestones, by sending in clearing files containing
test transactions for processing.
For questions about Community Runs, contact your Customer Implementation Services representative.
Freeze Dates
Q: Why don’t the Dual Message System (Clearing) freeze dates align with the Dual Message System
(Authorization) and Single Message System freeze dates?
A: Mastercard does not allow changes to any of the core systems during the freeze dates. The Dual
Message (Authorization) and Single Message System freeze dates do not align with the Dual Message
System (Clearing) freeze dates due to the nature of when changes take effect in the respective
systems.
Changes made to the Dual Message System (Authorization) and Single Message System become
effective before the Clearing platform changes.
Changes made to the Clearing platform are effective with the Clearing processing date that occurs
the business day following the Dual Message System (Authorization) and Single Message System
changes.
Q: What are the peak season freeze dates?

A: Peak season freeze dates are no longer necessary, except for Christmas Day and New Year’s Day.

Q: Where are release freeze dates published?

A: Refer to AN 1367—Freeze Dates to Support Dual Message System and Single Message System
2019 Release Implementations.
Distribution of IPM MPE Files
Q: On what specific date will test files for IPM MPE (T168) and IPM Clearing Optimizer and Utilities
Software (T066) and Workstation Plus (T065) files be distributed? The release milestone dates indicate
a date range.
A: Mastercard provides a date range for file distribution to make sure customers are prepared to
receive files during that time frame. To allow flexibility in the distribution, Mastercard does not indicate
a specific date or time of day for the distribution of the files.
Q: When will I receive the Production IPM MPE Full File Replacement (T068)?
A: Mastercard generally distributes the Prod—IPM MPE Full File Replacement (T068) with global
releases (Q2 and Q4).
• For Asia/Pacific, Europe, and Middle East/Africa regions delivery of the Prod—IPM MPE Full File
Replacement (T068) for Dual Message System (Clearing) Release begins Thursday, 22:00 (St. Louis
time).
• For United States, Canada, Latin America and the Caribbean delivery of the Prod—IPM MPE Full
File Replacement (T068) for Dual Message System (Clearing) Release begins Friday, 04:00 (St. Louis
time).
Q: Why is the Production IPM MPE Full File (T068) Replacement distributed at different times?
A: Mastercard sends the Prod—IPM MPE Full File Replace file (T068) at different times to help balance
the transmission load.

Q: Will the Test MPE and Production MPE match?

A: No, the content will not match. There are internal test BINs and ICAs in the Test MPE that are not
included in Production MPE.
In addition, there are specific test parameter setups (internal or requested by customers) that will be
included in Test MPE that may not match production parameters.
• New Release Items—New release items will not be in Production MPE, until the release goes live.
• Interchange Rates—Interchange rates will be different in Production MPE until the release goes
live. Generally, interchange rates are included in Test MPE six months before they are included in
Production IPM and do not reflect actual rates until published.
• Delivery of Test—IPM MPE Full File Replace File (T168)—Delivery of T168 for a release
contains all known release content at the time of creation and all known structure changes.
Mastercard makes every effort to include all structure changes “up front” for a global rollout.
Q: Why doesn’t the first Test—IPM MPE Full File Replace file (T168) (which is delivered with First IPM
Clearing Optimizer and Utilities Software Global Rollout for a new release) contain all release changes
and requires Test account ranges?
A: The purpose of the First IPM Clearing Optimizer and Utilities Software Global Rollout is for
customers to install Clearing Optimizer on their host systems and to provide an MPE that will function
with the new release, containing as much as possible in the MPE at the time of the global rollout.
The Test—IPM MPE Full File Replace file (T168) is a pre-version file that provides customers with layout
changes and most release changes.
When the Mastercard Test Facility becomes available to support the new release, the actual T168 will
be delivered to customers for testing using the Mastercard Test Facility environment.
Q: Why can’t I find a Test account range in the MPE for a new product code for a specific country?
A: Mastercard will define Test account ranges on a regional basis to support testing of new product
codes and include additional ones if there is a specific country requirement.
Q: I didn’t receive my T065, T068 or T168 file, what do I do?

A: Send your ICA and Endpoint to cis_northamerica_support@mastercard.com and request that they
resend the file (for example, T168). Specify the release (for example, Release 19.Q2)

Interchange
Q: Where are interchange rates in the release announcements?

A: Interchange rates are not provided in release announcements. Instead, interchange rates are
published in a bulletin announcement, typically 60-90 days before release implementation.
IPM Clearing Optimizer and Utilities Software Global Rollout
Q: Will all planned release item updates be included in the First IPM Clearing Optimizer and Utilities
Software Global Rollout?
A: No. The purpose of the First IPM Clearing Optimizer and Utilities Software Global Rollout is for
customers to install Clearing Optimizer on their host systems and provide an MPE that will function
with the new release, containing as much as possible in the MPE at the time of the global rollout.
Release items that are published later or items that require changes due to late testing and community
runs will be in the Second IPM Clearing Optimizer and Utilities Software Global Rollout and the next
distribution of the Test—IPM MPE Full File Replace File (T168).
If you notice something was missed or have questions about details found in the First IPM Clearing
Optimizer and Utilities Software Global Rollout, contact the Global Customer Service team. If your
question involves a Community Run, contact your Customer Implementation Services representative.
MIP Initial Program Load
Q: What does the initial program load (IPL) entail?

A: The IPL downloads release software to your Mastercard interface processors (MIPs).
Q: How long does it take for an IPL to complete?

A: The IPL generally takes 20–30 minutes for each MIP.

Q: What is required for a customer to prepare for an IPL?

A: No preparation is required. The Mastercard Stand-In System will respond to any transactions sent
during the IPL. Customers with the capability to reroute traffic to another MIP may do so. Coordinate
reroutes with the Mastercard Operation Command Center (OCC).
Q: What does the customer need to do on the day/time that the IPL is scheduled?
A: No action is required from customers in preparation for the IPL, unless a customer wants to reroute
traffic.
Q: How will a customer know when an IPL is planned?

A: An IPL schedule email will be distributed to the customer.
Release Implementation
Q: Why does the effective date for the Dual Message System (Authorization) occur weeks after the
effective dates for Dual Message System (Clearing) and Single Message System implementation?
A: Some release enhancements require changes that impact the Mastercard interface processors
(MIPs). Because it takes time to roll out changes to all MIPs globally, these updates are rolled out to
the MIPs over a period of time. The code is activated after the end of the Global MIP Implementation
and Authorization changes are activated concurrent with the MIP implementation date.
In some cases, there are corresponding changes to the Dual Message System (Authorization) and Dual
Message System (Clearing). While changes may be introduced with an effective date for the Clearing
enhancements before the Authorization implementation, customers will not likely see any new
clearing data values until after the Authorization portion of the enhancement is implemented.
Testing
Q: What documentation provides customer testing information for new BINs and product codes?
A: Customers can find testing information about new BINs and product codes in the Test BINs and
SM
Card Data for Acquirers document located on the Publications page on Mastercard Connect or by
using the test BINs that are contained in the test IPM MPE bulk file.

Q: How do I determine which tables and test cases I should run using the Testing Reference
Information Center manuals to achieve my testing objective?
A: Customers should work with a Customer Implementation Services project manager to determine
their testing needs.
In addition, you can use the Customer NIV Test Case Table Search tool on the Testing Reference
Information Center.
Q: Who can I contact with questions about test cases and the Testing Reference Information Center
manuals?
A: For these types of questions, contact citr@mastercard.com.
Q: Why is the Mastercard Test Facility available for 4 weeks during most releases and on occasion
available for five weeks?
A: The Mastercard Test Facility is available for a minimum of four weeks for every release testing
period. The four-week time frame is standard for customers to test with Mastercard in the Mastercard
Test Facility. If the calendar allows, Mastercard will extend the time frame to five weeks.
The “Mastercard Test Facility Unavailable” and “Mastercard Test Facility Available” dates are provided
in the Release Milestones Refer to the Switching Release Milestone announcement for each release in
the Release Resources topic.
Q: Who do I contact to set up or change test parameters to perform testing (regression or with
Mastercard)?
A: Customers should contact their Customer Implementation Services representative.
Q: Will the Mastercard Test Facility and Production environments be in sync?

A: No, the Mastercard Test Facility and Production environments are not in sync. Refer to Distribution
of IPM MPE Files for more information.
If additional setup is needed for your specific test requirements to the internal test ICA setup, contact
your Customer Implementation Services representative.

Timing (Sequence of Events)

The following sequence of events occur under standard conditions and are subject to change
due to unforeseen events. The release implementation could be delayed or may take longer
than indicated. If release implementation is delayed, Mastercard will distribute an urgent
notification.
Q: Where can I find detailed information about release milestones?

A: Switching release announcements are published according to the release publication milestones
available in AN 1609—2019 Switching Release Customer Milestones By Quarter.
Q: What time will my MIP be updated on the Dual Message System (Authorization) release date?
A: Dual Message System (Authorization) release items always phase in gradually on the effective date
for a given enhancement. Because it takes time to roll out changes to all MIPs globally, this process
starts as early as Tuesday, 01:30 (St. Louis time) and is anticipated to end around 06:00 (St. Louis
time).
Acquirers should not send transactions with new values until 06:00 (St. Louis time) to ensure MIP edits
do not reject the transactions.
Q: When do changes to the Account Management System and Stand-In System become effective?
A: Generally, Account Management System and Stand-In System changes are implemented around
00:00 (midnight, St. Louis time) on Wednesday.
Q: When should I begin processing clearing messages with the new release software?
A: Customers must begin using the new release to submit transactions for Saturday clearing
processing date after the 08:00 (St. Louis time) cutoff for Friday’s transactions.
Customers using IPM Clearing Optimizer must use the new version of IPM Clearing Optimizer and
Utilities software for transactions submitted after Friday’s 08:00 (St. Louis time) cutoff.

Q: When do Single Message System changes, such as online, batch, and Single Message Transaction
Manager, become effective?
A: Generally, Single Message System changes, such as online, batch, and Single Message Transaction
Manager, are implemented as part of the Single Message System release.
The Single Message System implementation will begin as early as Thursday, 23:45 (St. Louis time) and
normally complete by Friday, 06:00 (St. Louis time).
Customers may begin seeing new values soon after 00:00 (midnight, St. Louis time), as soon as the
code is active.
Q: How do I know when events will occur in my time zone?

A: For operational purposes, Mastercard generally refers to time frames as either “St. Louis time” or
“New York time.” Coordinated Universal Time (UTC) is the basis for measuring time throughout the
world.
For more information about converting any time into the correct time in another zone, refer to Times
Expressed in Documentation, provided in the Bundled Snapshot.
Q: Will I be able to access Single Message Transaction Manager during the release implementation?
A: Single Message Transaction Manager users may experience access interruptions.

Q: When does Mastercard deliver the outbound Clearing files at release implementation?
A: Mastercard extends the planned outbound delivery of the files of cycles one and two by 1–3 hours
on release implementation dates only to accommodate additional release-related activities taking
place during this time period. The files from cycles three through six are delivered at the usual times.
Release implementation dates occur four times a year and occur on a Friday of the release
implementation month.
Although the files of cycles one and two are delivered on a different calendar day from cycles three
through six, Mastercard considers the delivery of all six cycles of files to occur in one “processing day.”
Acquirers and issuers should be aware that they will receive their cycle one and two files 1–3 hours
later than usual. Mastercard will notify customers if the delay runs greater than three hours.
The outbound files and reports that are expected to be delayed are listed below. For more information
about the files generated by Mastercard, refer to the GCMS Reference Manual.
NOTE: Cut-off times for clearing cycles remain the unchanged.
Expected Delay of Outbound Files and Reports
Bulk IDs: T057

File Name: Currency Conversion Rate File
File Name Details: The Currency Conversion Rate File provides customers with Mastercard-Issued USD
Rates and Mastercard-Issued Cross Rates, in effect for a given processing day.
Bulk IDs: T067 (Q1/Q3)

File Name: GCMS Parameter Extract File–Daily Updates
File Name Details: Customers receive the new and updated parameter values via distribution of this daily
IPM Mastercard Parameter Extract (IPM MPE) file.
Bulk IDs: T068 (Q2/Q4)

File Name: GCMS Parameter Extract File–Daily Updates
File Name Details: Customers receive a Full File replacement.
Bulk IDs: T112 and TY30 (Customers in Russia)

File Name: Clearing Outbounds
File Name Details: Production IPM data generated by Mastercard from Central Site.


File Name: Early Recon File
File Name Details: Early Reconciliation Message file generated by Mastercard: If the customer chooses to
receive this file, it provides early reconciliation and error message details after each logical file from a
member is processed.

File Name: Cycle End Reports File. Customers receive only those reports they signed up for.
File Name Details:
• IP727010-AA—Clearing Cycle Acknowledgment Report
• IP727020-AA—Clearing Cycle Notification Report
• IP728010-AA—Clearing Cycle Summary Report
• IP857010-AA—Error Detail Report
• IP857010-BB—Collection Only Error Detail Report
• IP142110-AA—IPM Messages Created On Behalf of a Member
• IP142520-AA—On-behalf Service Fee Collection Report
• IP170010-AA—Acquirer Funded Reward Presentments Created On Behalf of a Member
• IP184010-AA—Non-IIAS Certified Merchant Recap
• IP148320-AA—Miscellaneous Override Financial Adjustments
• IP854010-AA—Error Detail
Bulk ID: TN66

File Name: Raw Data to XML File. If customers opted for XML Conversion. Customers receive only those
reports they signed up for.
File Name Details: XML raw data files:
• IP775010-AA
• IP170010-AA
• IP142520-AA
• IP142110-AA

Bulk ID: TN70

File Name: Raw Data Report
File Name Details: Raw data files:
• IP142110-AA
• IP142520-AA
• IP170010-AA
• IP830010

AN 2144—Transaction Integrity Class for Interchange Rates—Reminder
Chapter 32 AN 2144—Transaction Integrity Class for

Interchange Rates—Reminder
In Release 17.Q4 “AN 1026—Transaction Integrity Class for Interchange Rates,” Mastercard
provided customers advance notification of the modifications to the interchange process that will
include the Transaction Integrity Class as a part of the interchange rate assignment. This
announcement is an additional reminder to acquirers and issuers of the requirements of the
Transaction Integrity Class initiative.
AN 2144—Transaction Integrity Class for Interchange Rates—Reminder......................................444

Version History............................................................................................................................444
At-A-Glance................................................................................................................................444
Overview.................................................................................................................................... 445
Customer Impact........................................................................................................................ 447
Enhancements............................................................................................................................ 448
Platform Impact.......................................................................................................................... 448


In Release 17.Q4 “AN 1026—Transaction Integrity Class for Interchange Rates,” Mastercard
provided customers advance notification of the modifications to the interchange process that
will include the Transaction Integrity Class as a part of the interchange rate assignment. This
announcement is an additional reminder to acquirers and issuers of the requirements of the
Transaction Integrity Class initiative.
Version History

At-A-Glance
announcement, action indicators that specify the appropriate action, and the date or dates

Release: 19.Q2
System: Clearing
Action Indicator:
Effective Date: Dual Message System (Clearing): Future

Overview
Overview
Background
The Transaction Integrity Class (TIC) is provided by Mastercard for point-of-sale (POS) purchase
and purchase with cash back transactions initiated on the Authorization Platform for all U.S.
acquirers and issuers of Mastercard® credit and Debit Mastercard® cards.
TIC, introduced in Release 16.Q2, encompasses the fundamental safety and security of a
transaction and includes the assessment of both the validity of the card and the cardholder.
Some transactions are inherently more secure than others. For example, EMV®1. chip cards are
more secure than magnetic stripe cards. There will be nuances across both the technology
used for the account and the Cardholder Verification Method (CVM), but the combination is
assessed across the spectrum to determine the overall integrity of each transaction.
TIC was implemented in Release 16.Q2 as optional. As Phase I and II are implemented, the TIC
value will be a required element in clearing messages as it will be a mandatory qualifying
criteria for U.S. region interchange rates (excluding Standard).
1. EMV is a registered trademark or a trademark of EMVCo LLC in the United States and other
countries.

PDS 0017 (Transaction Integrity Class) is a private data subelement optionally used by
acquirers in First Presentment/1240 messages. The Transaction Integrity Class is not used to
override the interchange rate.
The valid TIC values presented in PDS 0017 are as follows.
Classification
Card and Cardholder Present EMV/Token in a Secure, Trusted A1

Environment
Card and Cardholder Present EMV/Chip Equivalent B1
Card and Cardholder Present Mag Stripe C1
Card and Cardholder Present Key Entered E1
Card and Cardholder Present Unclassified U0
Card and/or Cardholder Not Present Digital Transactions A2

Overview
Classification
Card and/or Cardholder Not Present Authenticated Checkout B2
Card and/or Cardholder Not Present Transaction Validation C2
Card and/or Cardholder Not Present Enhanced Data D2
Card and/or Cardholder Not Present Generic Messaging E2
Card and/or Cardholder Not Present Unclassified U0

Mastercard is initiating a phased approach to the modification of the interchange process to
include the TIC as a part of the interchange rate assignment. The planned phases to
implement this modification are as follows:
• Phase I
– Transaction Integrity Class will be required for transactions with processing codes 00
(Purchase [Goods and Services]), 09 (Purchase [Goods and Services] with Cash Back [only
for use with Mastercard Debit Card Products]), and 18 (Unique Transaction [requires
unique MCC])
– New clearing edits will be introduced for existing PDS 0017 (Transaction Integrity Class)
to verify:
– When the TIC is present there is a valid combination of acceptance brands (AB), IRD,
and U.S. region BSA 2/010001
– When PDS 0017 is present, it must contain a valid combination of PDS 0158
(Business Activity), subfield 4 (Interchange Rate Designator) and the Transaction
Integrity Class in PDS 0017
– That PDS 0017 must be present for AB/BSA/IRD combinations when the Transaction
Integrity Class Mandatory indicator is value Y
• Phase II
– Addition of new subfield 15 (Transaction Integrity Class Override Indicator) in PDS 0158
(Business Activity) and modification of the Length Field for PDS 0158 to accommodate
the new subfield
– Addition of new subfield 15 in PDS 0358 (Reconciled, Business Activity) and
modification of the Length Field for PDS 0358 to accommodate the new subfield
– Mastercard will implement the ability to override the IRD based on the TIC.
Acquirers and issuers should be aware, as Mastercard develops this project additional technical
changes may be required. Complete details will be available in future release announcements.

With these changes implemented, Mastercard may differentiate different types of transactions
based on TIC values.

Announcements
• “AN 1808—Transaction Integrity Class for Interchange Rates—Reminder,” Release 18.Q4
• “AN 1026—Transaction Integrity Class for Interchange Rates,” Release 17.Q4 (Re-
published 17 October 2017)
• “Global 525—Introducing Transaction Integrity Classification,” Release 16.Q2
Customer Impact

Information only—Acquirers and issuers in the U.S. region should be aware Mastercard will
publish future release announcements providing the implementation schedule and description
of the technical enhancements based on the TIC value.

Message System:

Enhancements

Enhancements
Mastercard is not implementing any new or changed system functionality with Release 19.Q2.
Complete technical details will be available in future release announcements.
Platform Impact
Mastercard is not implementing any new or changed system functionality with Release 19.Q2.
Complete technical details will be available in future release announcements.

AN 2145—Clarification of Usage of Mastercard Digital Enablement Service OBS Result Values and
Redefinition of Service Level Indicator Value
Chapter 33 AN 2145—Clarification of Usage of Mastercard

Digital Enablement Service OBS Result Values and
Mastercard is clarifying the usage of select on-behalf service (OBS) result values for Mastercard
Digital Enablement Service (MDES) and updating the definition of a Security Level Indicator (SLI)
value.
AN 2145—Clarification of Usage of Mastercard Digital Enablement Service OBS Result Values

and Redefinition of Service Level Indicator Value......................................................................... 450
Version History............................................................................................................................450
At-A-Glance................................................................................................................................450
Enhancements............................................................................................................................ 451

AN 2145—Clarification of Usage of Mastercard Digital Enablement

Service OBS Result Values and Redefinition of Service Level Indicator
Value
Mastercard is clarifying the usage of select on-behalf service (OBS) result values for Mastercard
Digital Enablement Service (MDES) and updating the definition of a Security Level Indicator
(SLI) value.
Version History

At-A-Glance

Products & Services: Mastercard Digital Enablement Service
Release: 19.Q2
Region: All
Action Indicator:
Information only—MDES issuers should be aware that they may receive the
OBS result values identified in this release announcement.

Enhancements
Information only—MDES issuers should be aware of the revised description

of the SLI value identified in this release announcement.
Testing recommended—Mastercard recommends testing for issuers to
Enhancements
Mastercard will make the following enhancements to support this release announcement.

Clarification of Usage of Mastercard Digital Enablement Service OBS Result Values
Mastercard is clarifying that MDES issuers should be prepared to receive on-behalf service
(OBS) result values X (Security platform time out) or Z (Security platform system error) and
corresponding advice details code values 0038 (Reject: Security Platform Time Out) or 0040
(Reject: Security Platform System Error) in conjunction with any of the following MDES
cryptographic validation services:
• Mastercard Digital Enablement Service Chip Pre-Validation (OBS 51)
• Mastercard Digital Enablement Service CVC 3 Pre-Validation (OBS 52)
• Mastercard Digital Enablement Service Cloud-based Payments Chip Pre-Validation Service
(OBS 61)
• Mastercard Digital Enablement Service Cloud-based Payments Magnetic Stripe Pre-
Validation Service (OBS 62)
Mastercard provides OBS details to issuers in Authorization Request/0100 or Financial
Transaction Request/0200 messages and, when applicable, in system-generated Authorization
Advice/0120 or Financial Transaction Advice/0220 messages, in DE 48 (Additional Data—
Private Use), subelement 71 (On-behalf Services), subfield 1 (On-behalf [OB] Service) and
subfield 2 (On-behalf Result 1). Mastercard sends the corresponding values to issuers in
advices in DE 60 (Advice Reason Code), subfield 2 (Advice Detail Code).
NOTE: Issuers should be aware that the systemic conditions associated with these values
occur infrequently. Mastercard uses these values to uniquely identify the existence of such
conditions and simplify the resolution process without the need for extensive system
analysis.

Mastercard is also updating the description of existing value 4 in DE 48, subelement 42
(Electronic Commerce Indicators), subfield 1 (Electronic Commerce Security Level Indicator and

Enhancements
UCAF Collection Indicator), position 2 (Cardholder Authentication) from “Digital Secure

Remote Payment (DSRP) with UCAF data” to “Tokenized payment.”

AN 2147—Issuer Support for DE 48, Subelement 95
Chapter 34 AN 2147—Issuer Support for DE 48,

Subelement 95
Mastercard is reminding all issuers that it may introduce new DE 48 (Additional Data—Private Use)
subelements to facilitate special processing.
AN 2147—Issuer Support for DE 48, Subelement 95...................................................................454

Version History............................................................................................................................454
At-A-Glance................................................................................................................................454
Enhancements............................................................................................................................ 455


Mastercard is reminding all issuers that it may introduce new DE 48 (Additional Data—Private
Use) subelements to facilitate special processing.
Version History
Date Description of Change

At-A-Glance

Release: 19.Q2
Region: All
System: Authorization
Action Indicator:
Network Mandate—All issuers must support the enhancements as described
in this announcement.

Enhancements
Enhancements
Mastercard will enhance the following system to support this announcement.
Background
Effective with Release 18.Q4, Mastercard introduced enhancements to the Mastercard
Installment Payment Service as part of “AN 1633—Enhancements to the Mastercard
Installment Payment Service” to pass the installment promotion code in DE 48 (Additional
Data—Private Data), subelement 95 (Mastercard Promotion Code) sent by acquirers to issuers.
As some issuers were not prepared to receive DE 48, subelement 95, Mastercard deactivated
this enhancement and planned to reactivate it in Release 19.Q2.
NOTE: Mastercard may occasionally introduce new DE 48 subelements between releases to

facilitate special processing within a country, region, or among pilot participants. Mastercard
requires customers to be able to successfully process various online messages that may
contain new unannounced DE 48 subelements. This data element’s content may vary by
program and service.
Additional or supplemental information that may be required in a transaction message is
specified in Authorization Platform Edits for this data element. Refer to the Customer
Interface Specification manual for additional information.

Effective with Release 19.Q2, issuers must be prepared to receive DE 48, subelement 95 in
Authorization Request/0100 and Authorization Advice/0120—System-Generated messages
even if the transaction does not qualify for installment.
Announcements
Refer to this previously published announcement for more information:
• “AN 1633—Enhancements to the Mastercard Installment Payment Service,” Release 18.Q4
Reference Manuals
processing:

Enhancements
manuals.

AN 2148—Enhancement of Issuer Notification for Installment Eligible E-Commerce Transactions
Chapter 35 AN 2148—Enhancement of Issuer Notification

for Installment Eligible E-Commerce Transactions
Mastercard is enhancing the Mastercard Installment Payment Service to provide issuers with a new
option for the delivery of notifications for electronic commerce (e-commerce) transactions.
AN 2148—Enhancement of Issuer Notification for Installment Eligible E-Commerce

Transactions................................................................................................................................ 458
Version History............................................................................................................................458
At-A-Glance................................................................................................................................458
Overview.................................................................................................................................... 459
Customer Impact........................................................................................................................ 460
Enhancements............................................................................................................................ 461
Platform Impact.......................................................................................................................... 463

AN 2148—Enhancement of Issuer Notification for Installment Eligible

E-Commerce Transactions
Mastercard is enhancing the Mastercard Installment Payment Service to provide issuers with a
new option for the delivery of notifications for electronic commerce (e-commerce)
transactions.
Version History

8 Jan 2019 Initial publication date
At-A-Glance

Products & Services: Mastercard Installment Payment Service
Release: 19.Q2
Region: All
System: Installments
Action Indicator:
Effective Date: Installments: 12 April 2019

Overview
Overview
Background
In Release 16.Q2, Mastercard enhanced authorization and clearing processing to support
installment payment data globally. This functionality enabled enrolled issuers to offer
cardholders the choice to pay for a purchase through installment payments and to select the
installment payment data from options provided by the issuer.

Mastercard sends a notification message to the issuer for an installment eligible transaction
after authorization or clearing processing or both based upon issuer registration. The issuer
then sends the notification message through a Short Message Service (SMS)/push notification
to the cardholder about the availability of an installment offer for the transaction, regardless
of the origin of the transaction which may include:
• A point-of-service (POS) terminal which has not been upgraded to support installment
transactions
• A SMART terminal which has been upgraded with application programming interface (API)
technology
• An e-commerce website
However, prior to the cardholder receiving the installment offer notification directly from their
issuer, they first receive the notification from the merchant’s SMART terminal or e-commerce
website. Therefore, the issuer’s installment offer notification is a duplicate of the offer first
received via the merchant.

Mastercard will produce a new Send E-Commerce Notification option so that issuers can select
to receive or not to receive an updated notification for only e-commerce transactions using
the Mastercard Installment Payment Service application on Mastercard Connect™.
NOTE: Transactions from POS or SMART terminals will not benefit from this new option.

With these enhancements, Mastercard will allow issuers the flexibility to opt out of receiving
notification for an e-commerce transaction and to reduce the duplication of the installment
notification for this type of transaction.

Reference Manuals
processing:
• Mastercard Installment Payment Service—Application Programming Interface: Technical
Specifications Guide
Specifications Guide for Payment Service Providers
• Mastercard Installment Payment Service—Installment API: Implementation Guide
• Mastercard Installment Payment Service—Installment Calculation and Posting:
Implementation Guide
• Mastercard Installment Payment Service—Point-of-Interaction: Implementation Guide
• Mastercard Installment Payment Service User Guide
manuals.
Customer Impact

Attention warranted (Program/service-related)—Issuers that participate in the Mastercard
Installment Payment Service may modify the setting for the Send E-Commerce Notification
option using the Mastercard Installment Payment Service application on Mastercard Connect™
as described in this announcement.
Mastercard will apply the default setting for the Send E-Commerce Notification option when
issuers that are newly participating in the Mastercard Installment Payment Service do not
select a value for this option.
Registration required—To participate in the Mastercard Installment Payment Service, issuers
must contact Customer Implementation Services. This service is available to issuers that receive
and send messages through the Dual Message System.
Testing recommended—Mastercard recommends that issuers participating in the Mastercard
Installment Payment Service perform testing.

Enhancements

Message System:
messages
Enhancements
Installments—Issuers
Issuers that are currently participating in the Mastercard Installment Payment Service will
continue to receive notification for e-commerce transactions as the Send E-Commerce
Notification option will be set to Yes.
Mastercard will allow currently participating issuers to modify the Send E-Commerce
Notification option at the account range level for all installment-financed models (for example,
Issuer-Financed model and Issuer-Merchant Co-Financed model) and installment services
(Point-of-Interaction, Installment Calculation and Posting, and Installment API services) within
the Mastercard Installment Payment Service application on Mastercard Connect™.
Issuers that are newly participating in the Mastercard Installment Payment Service will be able
to modify the Send E-Commerce Notification option at the account range level. When issuers
do not provide a value for this option, Mastercard will apply the default value of No.
This option applies to all installment-financed models and installment services in the
Mastercard Installment Payment Service application on Mastercard Connect. Installment-
financed models include an Issuer-Financed model and an Issuer-Merchant Co-Finance model.

Enhancements
Installment services include Point-of-Interaction, Installment Calculation and Posting, and

Installment API services.
The following table shows the scenarios that occur based on the value selected by the issuer
for the Send E-Commerce Notification option.
Existing Field New Field

Scenarios for Installment
Plan Matching and Issuer Send E-Commerce Eligible e-Commerce
Notification via XML Gateway Notification Transaction Only
Authorization Yes Updated notification will be sent

to issuer after Authorization for
installment eligible e-commerce
transaction.
Authorization No No notification will be sent for

transaction.
Clearing Yes Updated notification will be sent

to issuer during Clearing for
transaction.
Clearing No No notification will be sent for

transaction.
Both Yes Updated notification will be sent

to issuer after Authorization and
during Clearing for installment
eligible e-commerce transaction.
Both No No notification will be sent for

transaction.
None No No notification will be sent.
NOTE: When the Plan Matching and Issuer Notification via XML Gateway option is set to
none, the Send E-Commerce Notification option will be unavailable in the Mastercard
Installment Payment Service application.
The Updated Notification will include an additional Java Script Object Notation (JSON) field
indicating whether the transaction is or is not e-commerce. The additional JSON field will be
in the notification message that is being sent to the issuer.

Platform Impact
Platform Impact
Mastercard is implementing new Mastercard Installment Payment Service functionality to
support this release announcement. Customers must determine the impact of this release
announcement on their own operations.

AN 2149—Enhancements to the Mastercard Installment Payment Service for Cross-Border Eligibility Check
Chapter 36 AN 2149—Enhancements to the Mastercard

Installment Payment Service for Cross-Border Eligibility
Check
Mastercard is enhancing the Mastercard Installment Payment Service to provide issuers with a new
option allowing issuers to configure whether they want to offer installment service for cross-border
transactions, domestic transactions, or both cross-border and domestic.
AN 2149—Enhancements to the Mastercard Installment Payment Service for Cross-Border

Eligibility Check...........................................................................................................................465
Version History............................................................................................................................465
At-A-Glance................................................................................................................................465
Overview.................................................................................................................................... 466
Customer Impact........................................................................................................................ 467
Enhancements............................................................................................................................ 468
Platform Impact.......................................................................................................................... 469

AN 2149—Enhancements to the Mastercard Installment Payment

Service for Cross-Border Eligibility Check
Mastercard is enhancing the Mastercard Installment Payment Service to provide issuers with a
new option allowing issuers to configure whether they want to offer installment service for
cross-border transactions, domestic transactions, or both cross-border and domestic.
Version History

8 Jan 2019 Initial publication date
At-A-Glance

Products & Services: Mastercard Installment Payment Service
Release: 19.Q2
Region: All
System: Installments
Action Indicator:
Effective Date: Installments: 12 April 2019

Overview
Overview
Background
In Release 16.Q2, Mastercard enhanced authorization and clearing processing to support
installment payment data globally. This functionality enabled enrolled issuers to offer
cardholders the choice to pay for a purchase through installment payments and to select the
installment payment data from options provided by the issuer.

The Mastercard Installment Payment Service determines whether or not a transaction is
eligible for installment processing based on the following criteria provided by the issuer:
• Account range and PAN eligibility through the inclusion or exclusion PAN list
• Card acceptor business codes (MCC) exclusions
• Transaction amount
Mastercard does not currently offer issuers an option for the service to determine the eligibility
of installment transactions as cross-border only, domestic only, or to allow both based on the
geographic scope.

Mastercard will provide the option allowing issuers to configure whether they want to offer
installment service for cross-border transactions, domestic transactions, or both cross-border
and domestic based on the geographic scope using the Mastercard Installment Payment
Service application on Mastercard Connect™.

With these enhancements, Mastercard will provide issuers with the flexibility to configure the
installment service to determine transaction eligibility based on its geographic scope: cross-
border only, domestic only, or to allow both.

Reference Manuals
processing:
Specifications Guide
Specifications Guide for Payment Service Providers
• Mastercard Installment Payment Service—Installment API: Implementation Guide
• Mastercard Installment Payment Service—Installment Calculation and Posting:
Implementation Guide
• Mastercard Installment Payment Service—Point-of-Interaction: Implementation Guide
• Mastercard Installment Payment Service User Guide
manuals.
Customer Impact

Attention warranted (Program/service-related)—Issuers that participate in the Mastercard
Installment Payment Service may modify the eligibility check option as described in this
announcement. Issuers that do not use this new option simply will not have the installment
service check for this criteria during eligibility qualification.
Registration required—To participate in the Mastercard Installment Payment Service, issuers
must contact Customer Implementation Services. This service is available to issuers that receive
and send messages through the Dual Message System.
Testing recommended—Mastercard recommends that issuers participating in the Mastercard
Installment Payment Service perform testing.

Enhancements

Message System:
messages
Enhancements
Installments—Issuer
Mastercard will allow participating issuers to set the eligibility check option for the Geographic
Scope field as cross-border only, domestic only, or allow both at the account range level for all
installment-financed models (for example, Issuer-Financed model and Issuer-Merchant Co-
Financed model) and installment services (Point-of-Interaction, Installment Calculation and
Posting, and Installment API services) within the Mastercard Installment Payment Service
application on Mastercard Connect™.
The default value of Both for the Geographic Scope does not restrict the installment
transaction as either cross-border or domestic. Issuers will be able to modify the default value
of Both choosing the cross-border only or domestic only options at the account range level.
The following table summarizes the Geographic Scope values.
Geographic Scope Value Result
Both (Default) no restriction on location

Platform Impact
Geographic Scope Value Result
Cross-border Installment services limited to cross-border

transactions
Domestic Installment services limited to domestic

transactions
No value selected Setting not allowed
Platform Impact
Mastercard is implementing new Mastercard Installment Payment Service functionality to
support this release announcement. Customers must determine the impact of this release
announcement on their own operations.

Notices
Notices
Following are policies pertaining to proprietary rights, trademarks, translations, and details
about the availability of additional information online.
Proprietary Rights
The information contained in this document is proprietary and confidential to Mastercard International
Incorporated, one or more of its affiliated entities (collectively “Mastercard”), or both.
This material may not be duplicated, published, or disclosed, in whole or in part, without the prior written
permission of Mastercard.
Trademarks
Trademark notices and symbols used in this document reflect the registration status of Mastercard
trademarks in the United States. Please consult with the Global Customer Service team or the Mastercard
Law Department for the registration status of particular product, program, or service names outside the
United States.
All third-party product and service names are trademarks or registered trademarks of their respective
owners.
Disclaimer
Mastercard makes no representations or warranties of any kind, express or implied, with respect to the
contents of this document. Without limitation, Mastercard specifically disclaims all representations and
warranties with respect to this document and any intellectual property rights subsisting therein or any part
thereof, including but not limited to any and all implied warranties of title, non-infringement, or suitability
for any purpose (whether or not Mastercard has been advised, has reason to know, or is otherwise in fact
aware of any information) or achievement of any particular result. Without limitation, Mastercard specifically
disclaims all representations and warranties that any practice or implementation of this document will not
infringe any third party patents, copyrights, trade secrets or other rights.
Translation
A translation of any Mastercard manual, bulletin, release, or other Mastercard document into a language
other than English is intended solely as a convenience to Mastercard customers. Mastercard provides any
translated document to its customers “AS IS” and makes no representations or warranties of any kind with
respect to the translated document, including, but not limited to, its accuracy or reliability. In no event shall
Mastercard be liable for any damages resulting from reliance on any translated document. The English
version of any Mastercard document will take precedence over any translated version in any legal
proceeding.
Information Available Online
Mastercard provides details about the standards used for this document—including times expressed,
language use, and contact information—on the Publications Support page available on Mastercard
Connect™. Go to Publications Support for centralized information.


AN213219 Q2 Core Rel An Snapshot

Uploaded by

Copyright:

Available Formats

You might also like

AN213219 Q2 Core Rel An Snapshot

Uploaded by

Document Information

Original Title

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

AN213219 Q2 Core Rel An Snapshot

Uploaded by

Copyright:

Available Formats

AN 2132—19.

Date Description of Change Where to Look

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

Date Description of Change Where to Look

Updated and FAQ Additions with Bundled Snapshot: Throughout

• AN 1807—New Global Interchange Program for Freight

Added a new section dedicated to the Announcement Announcement

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

Date Description of Change Where to Look

Updated and FAQ Additions with Bundled Snapshot: Throughout

• AN 1810—New Product Codes for Platinum Mastercard

Removed references to MasterCom Administrator’s Manual Related Information

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

Date Description of Change Where to Look

Updated the summary section of the bundle to clarify its AN 2132—19.Q2

In the Release 19.Q2 Announcements section, revised the Release 19.Q2

Updated the About Announcements section as follows: About

23 Oct 2018 Initial publication date

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

Chapter 1: AN 2132—19.Q2 Switching Release Announcements

Chapter 2: AN 1807—New Global Interchange Program for

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

Chapter 3: AN 1810—New Product Codes for Platinum

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

Chapter 4: AN 1811—New Product Code for Prepaid Gold

Chapter 5: AN 1812—Product Codes to Support Humanitarian

Chapter 6: AN 1813—Standardization of the 80-byte Financial

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

Chapter 7: AN 2108—Switching Release 19.Q2—Related

Chapter 8: AN 2111— Support of 8-Digit BIN Standard and

Chapter 9: AN 2113—Enhancements to AAV Validation for EMV

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

Customer Impact........................................................................................................... 127

Chapter 10: AN 2114—Introduction of Mastercard ATM Cash

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

Chapter 11: AN 2115—Mastercard Clearing Optimizer Utility

Chapter 12: AN 2116—Introduction of Merchant Presented QR

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

Chapter 13: AN 2117—Introducing Cryptographic Key Block

Chapter 14: AN 2118—Account Level Management Universal

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

World Elite Shortfall (WESF)—Summary Results, Preliminary Layout....................... 206

Chapter 15: AN 2119—Enhancements to Batch Data File to

Chapter 16: AN 2120—U.S. Commercial Interchange Structure

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

IRD 5A—Business Level 5 Data Rate I.................................................................... 237

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

Modified Edit—PDS 0595 (Card Acceptor Type), subfield 5 (Business Type

Chapter 17: AN 2121—Authorization of Purchase Returns................274

Chapter 18: AN 2122—Introduction of Mastercard Digital

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

CIS Data Element Definitions..................................................................................... 291

Chapter 19: AN 2123—Identification of Tokenized Mastercard

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

Chapter 20: AN 2124—Revisions to Brazil 7–21 Installment

Chapter 21: AN 2125—Enhancement for International Debit

Chapter 22: AN 2127—Expansion of Single Message System DE

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