I PM Clearing Format

Return to Menu
Information about this Replacement
Replacement The May 2004 IPM Clearing Formats completely replaces your existing
manual.
What is in the new This new version reflects changes effective with the implementation of
version? GCMS Release 04.1 and changes identified after the October 2003
publication of the IPM Clearing Formats manual.
Please refer to:
• “Summary of Changes” for a comprehensive list of changes reflected in

this update.
• “Using this Manual” for a complete list of the contents of this manual.
Billing MasterCard will bill principal members for this document in printed format.
Please refer to the MasterCard Consolidated Billing System Manual for
billing-related information.
Questions? If you have questions about this manual, please contact the Customer
Operations Services team or your regional help desk. Please refer to
“Using this Manual” for more contact information.
MasterCard is Please take a moment to provide us with your feedback about the material
Listening… and usefulness of the IPM Clearing Formats using the following e-mail
address:
publications@mastercard.com
We continually strive to improve our publications. Your input will help us

accomplish our goal of providing you with the information you need.
Summary of Changes
IPM Clearing Formats, May 2004
Change Summary Description of Change Where to Look
Removed Comments Removed the “Comments” column from message Chapter 2

column layouts chapters (2–6). Information contained in the Chapter 3
Comments column was added to the appropriate data Chapter 4
element or private data subelement documentation. Chapter 5
Chapter 6
Removed references Removed references to Eurocard and intra-European Entire manual
to Eurocard and Clip Clip transactions throughout the manual.
Added information Added information to support enhanced business service Chapter 3
to support business processing. Chapter 8
service processing Appendix C
Changed name of Changed the name of the Financial Detail Addendum Entire manual
the Financial Detail (Lodging Detail)/1644 message to the Financial Detail
Addendum (Lodging Addendum (Lodging Summary)/1644 message.
Detail)/1644 message
Added two new Added the Financial Detail Addendum (Telephony Entire manual
addendums Billing Service)/1644 and the Financial Detail Addendum
(Electronic Invoices)/1644 message layouts and applicable
supporting PDSs.
Expanded Member Changed the minimum length requirement for all Entire manual
ID (ICA) Member ID data elements from 4 to 6 positions.
Added new tiered Added the new tiered interchange rate structure for Chapter 8
interchange rate Consumer credit and debit and new Debit interchange Chapter 9
structure. rate programs. Chapter 10
Eliminated references Removed any remaining references to the MasterPhone Entire manual
to MasterPhone Telephone Service interchange program.
Telephone Service
Page 1 of 2
Change Summary Description of Change Where to Look
Divided PDS Divided the Private Data Subelements (PDS) Chapter 8

definitions into definitions chapters into three chapters (previously Chapter 9
three chapters contained in two chapters): Chapter 10
Chapter 8—PDS Definitions–Part 1
Added PDSs. Added PDSs to support new or modified addendum Chapter 8
messages as well as other miscellaneous enhancements. Chapter 9
Chapter 10
Added many new Added error codes to support new or modified addendum Appendix C
error codes, and messages as well as other miscellaneous enhancements.
deleted several In addition, several obsolete error codes were removed.
obsolete error codes.
Removed Glossary Removed Glossary from this manual. To see a list of
approved MasterCard terminology and definitions, please
click the MasterCard Dictionary link in the Member
Publications product on MasterCard® OnLine.
Page 2 of 2
IPM Clearing
Formats
May 2004
Copyright The information contained in this manual is proprietary and
confidential to MasterCard International Incorporated (MasterCard)
and its members.
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 manual reflect the
registration status of MasterCard trademarks in the United States.
Please consult with the Customer Operations Services 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.
Media This document is available:

• On MasterCard OnLine®
• On the MasterCard Electronic Library (CD-ROM)
• In printed format
• Translated into Spanish
• Translated into Portuguese
MasterCard International Incorporated

2200 MasterCard Boulevard
O’Fallon MO 63366-7263
USA
1-636-722-6100
www.mastercard.com
© 2004 MasterCard International Incorporated

IPM Clearing Formats • May 2004 Publication Code: IP
Table of Contents
Using this Manual

Purpose ................................................................................................................... 1
Audience................................................................................................................. 1
Overview ................................................................................................................ 2
Excerpted Text ....................................................................................................... 3
Language Use ......................................................................................................... 3
Times Expressed..................................................................................................... 4
Functionality Not Initially Supported .................................................................... 4
Revisions ................................................................................................................. 5
Related Information................................................................................................ 5
Related MasterCard Technical Documents...................................................... 5
Related MasterCard Europe Technical Documents......................................... 6
Related ISO Documents................................................................................... 6
Support ................................................................................................................... 7
Member Relations Representative ................................................................... 7
Regional Representative................................................................................... 8
Chapter 1 Overview
Clearing Introduction ..........................................................................................1-1
Transaction Processing Flow Through the Clearing System .......................1-2
IPM Offline Message Structure............................................................................1-3
IPM Offline File Structure ...................................................................................1-8

Basic Clearing System Message Flow...........................................................1-9
Acquirer to Clearing System to Issuer ..........................................................1-9
Issuer to Clearing System to Acquirer ..........................................................1-9
Clearing System to Issuer or Acquirer........................................................1-10

IPM Clearing Formats • May 2004 i
Table of Contents
Chapter 2 File Header and Trailer Messages

Message Types and Associated Function Codes................................................2-1
File Header/1644 Messages.................................................................................2-1
File Trailer/1644 Messages ..................................................................................2-2
Member-Generated Files .....................................................................................2-2

Offline Files versus Offline Transmissions...................................................2-2
Structure of a Member-Generated Offline Transmission
Containing One Logical File .........................................................................2-3
Containing More than One Logical File .......................................................2-3
Member-Generated Offline File Structure ....................................................2-4
File ID............................................................................................................2-4
Processing Mode ...........................................................................................2-5
Trailer Total Reconciliation...........................................................................2-5
MasterCard-Generated Files ................................................................................2-5

Sequence of the MasterCard Generated Files ..............................................2-5
Sequence of the Early Reconciliation File....................................................2-8
Data Element Flow..............................................................................................2-9
Message Format Data Element Requirements ..................................................2-10
Data Element Usage in Messages .....................................................................2-11
Data Elements and PDSs Not Initially Supported ............................................2-11
Intra-European Transactions .............................................................................2-12
Maestro and Cirrus Transactions.......................................................................2-12
File Header (Member-Generated)/1644 ...........................................................2-13
File Header (MasterCard-Generated)/1644.......................................................2-14
File Trailer (Member-Generated)/1644.............................................................2-15
File Trailer (MasterCard-Generated)/1644 ........................................................2-16

ii May 2004 • IPM Clearing Formats
Table of Contents
Chapter 3 Presentment, Addendum, and Chargeback

Messages
First Presentment/1240 Messages .......................................................................3-1
Financial Detail Addendum/1644 Messages.......................................................3-1

Financial Detail Addendum (Passenger Transport Detail—
General Ticket Information)/1644................................................................3-2
Trip Leg Data)/1644 ......................................................................................3-2
Financial Detail Addendum (Vehicle Rental Detail)/1644...........................3-3
Financial Detail Addendum (Lodging Summary)/1644 ...............................3-3
Financial Detail Addendum (Temporary Services)/1644.............................3-4
Financial Detail Addendum (Shipping/Courier Services)/1644 ..................3-4
Financial Detail Addendum (Payment Transaction Detail)/1644................3-5
Financial Detail Addendum (Telephony Billing Services)/1644 .................3-5
Financial Detail Addendum (Electronic Invoices)/1644 ..............................3-6
Financial Detail Addendum (Corporate Card Common Data
Requirements)/1644 ......................................................................................3-7
Financial Detail Addendum (Corporate Fleet Transaction
Information)/1644 .........................................................................................3-8
Financial Detail Addendum (Corporate Line Item Detail)/1644 .................3-9
Financial Detail Addendum (Generic Detail)/1644 .....................................3-9
First Chargeback/1442 and Arbitration Chargeback/1442 Messages ..............3-10
Second Presentment/1240 Messages ................................................................3-10
Data Element Flow............................................................................................3-11
First Presentment/1240......................................................................................3-15

IPM Clearing Formats • May 2004 iii
Table of Contents

General Ticket Information)/1644 ....................................................................3-21

Trip Leg Data)/1644 ..........................................................................................3-26
Financial Detail Addendum (Vehicle Rental Detail)/1644...............................3-31
Financial Detail Addendum (Lodging Summary)/1644 ...................................3-37
Financial Detail Addendum (Temporary Services)/1644.................................3-46
Financial Detail Addendum (Shipping/Courier Services)/1644.......................3-51
Financial Detail Addendum (Payment Transaction Detail)/1644 ....................3-57
Financial Detail Addendum (Telephony Billing Service)/1644 .......................3-59

Use of Telephony Billing Addendum Messages with Other
Addendum Messages ..................................................................................3-60
Message Layout for Financial Detail Addendum (Telephony
Billing—Detail)/1644 Message....................................................................3-65
Financial Detail Addendum (Electronic Invoices)/1644 ..................................3-70

Use of the Electronic Invoice Addendum Messages with
Other Addendum Messages........................................................................3-72
Message Layout for Financial Detail Addendum (Electronic
Invoice—Party Information)/1644 Message ...............................................3-75

Requirements)/1644 ..........................................................................................3-78

Information)/1644 .............................................................................................3-84
Financial Detail Addendum (Corporate Line Item Detail)/1644 .....................3-89
Financial Detail Addendum (Generic Detail)/1644..........................................3-94
First Chargeback/1442 and Arbitration Chargeback/1442 ...............................3-96
Second Presentment/1240............................................................................... 3-103

iv May 2004 • IPM Clearing Formats
Table of Contents
Chapter 4 Retrieval and Fee Collection Messages

Retrieval Request/1644 Messages .......................................................................4-1
Retrieval Fee Billing Messages............................................................................4-1
Fee Collection Messages .....................................................................................4-2
Message Format Data Element Requirements ....................................................4-4
Data Element Usage in Messages .......................................................................4-5
Data Elements and PDSs Not Currently Supported ...........................................4-5
Intra-European Transactions ...............................................................................4-6
Maestro and Cirrus Transactions.........................................................................4-6
Retrieval Request/1644........................................................................................4-7
Fee Collection (Retrieval Fee Billing)/1740......................................................4-11
Fee Collection (Handling Fees)/1740 ...............................................................4-16
Fee Collection (Other than Retrieval Fee Billing/Handling Fees)/1740..........4-21
Chapter 5 Reconciliation Messages

Functionality Not Currently Supported ..............................................................5-1
Activity Types Accumulated................................................................................5-1
Function Codes Used ..........................................................................................5-2
Message Reason Codes Used..............................................................................5-2

IPM Clearing Formats • May 2004 v
Table of Contents
File Currency Summary/1644..............................................................................5-3

File Currency Summary/1644 Acknowledgement Messages .......................5-3
File Currency Summary/1644 Notification Messages...................................5-3
Financial Position Detail/1644 Messages............................................................5-3

Reconciliation Category Summary................................................................5-4
Reconciliation Category Definitions .............................................................5-5
Reconciliation Amount/Reconciliation Fee Totals .....................................5-11
Settlement Position Detail/1644........................................................................5-15

Reconciliation Categories............................................................................5-15
Reconciliation Totals ...................................................................................5-16
Settlement Position Total/1644 .........................................................................5-17

File Currency Summary/1644............................................................................5-21
Financial Position Detail/1644 ..........................................................................5-23
Chapter 6 Administrative Messages

Message Exception/1644 Messages ....................................................................6-1

Data Record (DE 72).....................................................................................6-3
File Reject/1644 Messages...................................................................................6-4

Data Record (DE 72).....................................................................................6-5
Text Message/1644 Messages .............................................................................6-5
Currency Update/1644 Messages........................................................................6-6

vi May 2004 • IPM Clearing Formats
Table of Contents
Message Exception and File Reject/1644 .........................................................6-10
Text Message/1644 ............................................................................................6-12
Currency Update/1644 ......................................................................................6-13
Chapter 7 Data Element Definitions

Presentation of Data Element Information.........................................................7-1
Data Element Listing (Numerical Order) ............................................................7-8
Data Element Listing (Alphabetical Order) ......................................................7-13
Message Type Identifier ....................................................................................7-18
Bit Map, Primary................................................................................................7-22
DE 1—Bit Map, Secondary ...............................................................................7-25
DE 2—Primary Account Number (PAN) ..........................................................7-28
DE 3—Processing Code ....................................................................................7-30
DE 4—Amount, Transaction .............................................................................7-35
DE 5—Amount, Reconciliation .........................................................................7-38
DE 6—Amount, Cardholder Billing ..................................................................7-41
DE 8—Amount, Cardholder Billing Fee ...........................................................7-43
DE 9—Conversion Rate, Reconciliation ...........................................................7-44

IPM Clearing Formats • May 2004 vii
Table of Contents
DE 10—Conversion Rate, Cardholder Billing ..................................................7-46
DE 12—Date and Time, Local Transaction ......................................................7-48
DE 14—Date, Expiration...................................................................................7-51
DE 22—Point of Service Data Code .................................................................7-52
DE 23—Card Sequence Number ......................................................................7-65
DE 24—Function Code .....................................................................................7-66
DE 25—Message Reason Code .........................................................................7-70
DE 26—Card Acceptor Business Code (MCC) .................................................7-99
DE 30—Amounts, Original ............................................................................. 7-101
DE 31—Acquirer Reference Data ................................................................... 7-104
DE 32—Acquiring Institution ID Code........................................................... 7-108
DE 33—Forwarding Institution ID Code ........................................................ 7-111
DE 37—Retrieval Reference Number ............................................................. 7-113
DE 38—Approval Code................................................................................... 7-115
DE 40 Service Code ....................................................................................... 7-117
DE 41—Card Acceptor Terminal ID ............................................................... 7-119
DE 42—Card Acceptor ID Code ..................................................................... 7-121
DE 43—Card Acceptor Name/Location.......................................................... 7-123
DE 48—Additional Data.................................................................................. 7-133
DE 49—Currency Code, Transaction.............................................................. 7-136
DE 50—Currency Code, Reconciliation.......................................................... 7-138
DE 51—Currency Code, Cardholder Billing................................................... 7-140
DE 55—Integrated Circuit Card (ICC) System-Related Data.......................... 7-142
DE 62—Additional Data 2............................................................................... 7-148

viii May 2004 • IPM Clearing Formats
Table of Contents
DE 63—Transaction Life Cycle ID .................................................................. 7-151
DE 71—Message Number ............................................................................... 7-163
DE 72—Data Record ....................................................................................... 7-166
DE 73—Date, Action ....................................................................................... 7-168
DE 93—Transaction Destination Institution ID Code .................................... 7-169
DE 94—Transaction Originator Institution ID Code...................................... 7-172
DE 95—Card Issuer Reference Data............................................................... 7-175
DE 100—Receiving Institution ID Code ......................................................... 7-177
DE 123—Additional Data 3............................................................................. 7-180
DE 127—Network Data................................................................................... 7-189
Chapter 8 PDS Definitions—Part 1

PDS Construction and Use..................................................................................8-1
PDS Listing (Numerical Order) ...........................................................................8-9
PDS Listing (Alphabetical Order)......................................................................8-21
PDS 0002—Product Identifier ...........................................................................8-35
PDS 0005—Message Error Indicator.................................................................8-38
PDS 0006—Applied Business Service Arrangement ........................................8-41
PDS 0020—Issuer Currency Conversion Rate (ICCR) Effective Date..............8-44
PDS 0021—Issuer Currency Conversion Rate (ICCR) Percentage...................8-45

IPM Clearing Formats • May 2004 ix
Table of Contents
PDS 0022—Recurring Payment Indicator .........................................................8-46
PDS 0023—Terminal Type................................................................................8-47
PDS 0025—Message Reversal Indicator ...........................................................8-50
PDS 0026—File Reversal Indicator ...................................................................8-53
PDS 0043—Program Registration ID ................................................................8-56
PDS 0052—Electronic Commerce Security Level Indicator .............................8-58
PDS 0105—File ID.............................................................................................8-61
PDS 0110—Transmission ID .............................................................................8-65
PDS 0122—Processing Mode ............................................................................8-68
PDS 0137—Fee Collection Control Number ....................................................8-69
PDS 0138—Source Message Number ID ..........................................................8-70
PDS 0146—Amounts, Transaction Fee .............................................................8-71
PDS 0148—Currency Exponents ......................................................................8-77
PDS 0149—Currency Codes, Amounts, Original .............................................8-81
PDS 0158—Business Activity ............................................................................8-83
PDS 0159—Settlement Data 1...........................................................................8-94
PDS 0161—Settlement Data 2......................................................................... 8-102
PDS 0164—Currency Cross Rates ................................................................... 8-109
PDS 0165—Settlement Indicator ..................................................................... 8-112
PDS 0170—Card Acceptor Inquiry Information............................................. 8-116
PDS 0171—Alternate Card Acceptor Description Data.................................. 8-120
PDS 0172—Sole Proprietor Name .................................................................. 8-123
PDS 0173—Legal Corporate Name ................................................................. 8-124
PDS 0174—Dun & Bradstreet Number........................................................... 8-125

x May 2004 • IPM Clearing Formats
Table of Contents
PDS 0175—Card Acceptor URL ...................................................................... 8-126
PDS 0189—Point-of-Interaction (POI) Phone Data ....................................... 8-127
PDS 0190—Partner ID Code ........................................................................... 8-132
PDS 0191—Originating Message Format........................................................ 8-134
PDS 0228—Retrieval Document Code............................................................ 8-137
PDS 0230—Fulfillment Document Code ........................................................ 8-138
PDS 0241—MasterCom Control Number........................................................ 8-139
PDS 0242—MasterCom Service Indicator....................................................... 8-141
PDS 0243—MasterCom Retrieval Response Data........................................... 8-142
PDS 0244—MasterCom Chargeback Support Documentation Dates ............ 8-148
PDS 0245—MasterCom Arbitration Chargeback Sender Processing Date .... 8-151
PDS 0246—MasterCom Sender Memo............................................................ 8-152
PDS 0247—MasterCom Receiver Memo ......................................................... 8-153
PDS 0248—MasterCom Image Review Memo................................................ 8-154
PDS 0249—MasterCom Record ID.................................................................. 8-155
PDS 0250—MasterCom Endpoints.................................................................. 8-156
PDS 0251—MasterCom Fulfillment Document Code..................................... 8-158
PDS 0252—MasterCom Image Metadata ........................................................ 8-159
PDS 0253—MasterCom System Enhanced Data............................................. 8-161
PDS 0254—MasterCom Member Enhanced Data........................................... 8-162
PDS 0255—MasterCom Message Type ........................................................... 8-163
PDS 0260—Edit Exclusion Indicator............................................................... 8-165
PDS 0261—Risk Management Approval Code............................................... 8-171
PDS 0262—Documentation Indicator............................................................. 8-172

IPM Clearing Formats • May 2004 xi
Table of Contents
PDS 0264—Original Retrieval Reason for Request ........................................ 8-174
PDS 0265—Initial Presentment/Fee Collection Data ..................................... 8-176
PDS 0266—First Chargeback/Fee Collection Return Data............................. 8-179
PDS 0267—Second Presentment/Fee Collection Resubmission Data ........... 8-185
PDS 0268—Amount, Partial Transaction ........................................................ 8-190
PDS 0280—Source File ID .............................................................................. 8-192
PDS 0298—Reconciled, Transmission ............................................................ 8-194
PDS 0300—Reconciled, File............................................................................ 8-196
PDS 0301—File Amount, Checksum .............................................................. 8-198
PDS 0302—Reconciled, Member Activity....................................................... 8-200
PDS 0306—File Message Counts .................................................................... 8-202
PDS 0358—Reconciled, Business Activity ...................................................... 8-203
PDS 0359—Reconciled, Settlement Activity ................................................... 8-206
PDS 0370—Reconciled, Account Range......................................................... 8-209
PDS 0371—Reconciled, Message Reason Code ............................................. 8-211
PDS 0372—Reconciled, Transaction Function ............................................... 8-212
PDS 0373—Reconciled, Card Acceptor ID ..................................................... 8-214
PDS 0374—Reconciled, Processing Code ...................................................... 8-215
PDS 0375—Member Reconciliation Indicator 1 ............................................. 8-216
PDS 0378—Original/Reversal Totals Indicator............................................... 8-220
PDS 0380—Debits, Transaction Amount In Transaction Currency ............... 8-222
PDS 0381—Credits, Transaction Amount in Transaction Currency .............. 8-224
PDS 0384—Amount, Net Transaction in Transaction Currency .................... 8-226

xii May 2004 • IPM Clearing Formats
Table of Contents
PDS 0390—Debits, Transaction Amount in Reconciliation Currency ........... 8-228
PDS 0391—Credits, Transaction Amount in Reconciliation Currency .......... 8-230
PDS 0392—Debits, Fee Amounts in Reconciliation Currency....................... 8-232
PDS 0393—Credits, Fee Amounts In Reconciliation Currency...................... 8-234
PDS 0394—Amount, Net Transaction in Reconciliation Currency ................ 8-236
PDS 0395—Amount, Net Fee in Reconciliation Currency ............................. 8-238
PDS 0396—Amount, Net Total in Reconciliation Currency........................... 8-240
PDS 0400—Debits, Transaction Number........................................................ 8-242
PDS 0401—Credits, Transaction Number....................................................... 8-243
PDS 0402—Total, Transaction Number.......................................................... 8-244

Overview .............................................................................................................9-1
PDS 0501—Transaction Description...................................................................9-2
PDS 0505—Passenger Name.............................................................................9-10
PDS 0506—Ticket Number ...............................................................................9-12
PDS 0507—Issuing Carrier ................................................................................9-14
PDS 0508—Customer Code ..............................................................................9-16
PDS 0509—Issue Date.......................................................................................9-18
PDS 0510—Travel Agency Code ......................................................................9-19
PDS 0511—Travel Agency Name .....................................................................9-20
PDS 0512—Total Fare .......................................................................................9-21
PDS 0513—Total Fees .......................................................................................9-22
PDS 0514—Total Taxes.....................................................................................9-23

IPM Clearing Formats • May 2004 xiii
Table of Contents
PDS 0515—Additional Card Acceptor Information..........................................9-24
PDS 0516—Austin-Tetra Number .....................................................................9-25
PDS 0517—NAICS Code ...................................................................................9-26
PDS 0518—Line Item Date ...............................................................................9-27
PDS 0519—Additional Fuel Location Information ...........................................9-28
PDS 0520—Travel Date.....................................................................................9-32
PDS 0521—Carrier Code ...................................................................................9-34
PDS 0522—Service Class Code .........................................................................9-36
PDS 0523—City of Origin/Airport Code...........................................................9-38
PDS 0524—City of Destination/Airport Code ..................................................9-40
PDS 0525—Stop Over Code .............................................................................9-42
PDS 0526—Conjunction Ticket.........................................................................9-44
PDS 0527—Exchange Ticket.............................................................................9-45
PDS 0528—Coupon Number ............................................................................9-46
PDS 0529—Fare Basis Code .............................................................................9-47
PDS 0530—Flight Number ................................................................................9-48
PDS 0531—Departure Time..............................................................................9-49
PDS 0532—Total Charges .................................................................................9-51
PDS 0533—Arrival Time....................................................................................9-53
PDS 0534—Total Non-Room Charges ..............................................................9-55
PDS 0535—Fare.................................................................................................9-57
PDS 0536—Fee ..................................................................................................9-58
PDS 0537—Taxes ..............................................................................................9-59
PDS 0538—Endorsements/Restrictions.............................................................9-60

xiv May 2004 • IPM Clearing Formats
Table of Contents
PDS 0539—Total Amount Charged on Card ....................................................9-61
PDS 0540—Room Service Charges ...................................................................9-63
PDS 0541—Lounge/Bar Charges ......................................................................9-65
PDS 0542—Transportation Charges..................................................................9-67
PDS 0543—Gratuity Charges ............................................................................9-69
PDS 0544—Rental Agreement Number ............................................................9-71
PDS 0545—Renter Name ..................................................................................9-72
PDS 0546—Rental Return City ..........................................................................9-74
PDS 0547—Rental Return State/Province .........................................................9-76
PDS 0548—Rental Return Country ...................................................................9-78
PDS 0549—Rental Return Location ID .............................................................9-80
PDS 0550—Rental Return Date.........................................................................9-81
PDS 0551—Rental Check-Out Date ..................................................................9-82
PDS 0552—Customer Service Toll-Free (800) Number ...................................9-83
PDS 0553—Rental Rate .....................................................................................9-85
PDS 0554—Conference Room Charges ............................................................9-87
PDS 0555—Rate Per Mile (or Per Kilometer)...................................................9-89
PDS 0556—Total Miles (or Kilometers)............................................................9-90
PDS 0557—Maximum Free Miles (or Kilometers) ...........................................9-91
PDS 0558—Miles/Kilometers Indicator ............................................................9-92
PDS 0559—Vehicle Insurance ..........................................................................9-93
PDS 0560—Audio Visual Charges ....................................................................9-95
PDS 0561—Adjusted Amount ...........................................................................9-97
PDS 0562—Banquet Charges............................................................................9-99

IPM Clearing Formats • May 2004 xv
Table of Contents
PDS 0563—Program Code .............................................................................. 9-101
PDS 0564—Rental Location City ..................................................................... 9-102
PDS 0565—Rental Location State/Province.................................................... 9-103
PDS 0566—Rental Location Country .............................................................. 9-104
PDS 0567—Rental Location ID ....................................................................... 9-105
PDS 0568—Rental Class ID............................................................................. 9-106
PDS 0569—Internet Access Charges............................................................... 9-109
PDS 0570—Early Departure Charges.............................................................. 9-111
PDS 0571—Guest Name.................................................................................. 9-113
PDS 0572—Guest Number.............................................................................. 9-114
PDS 0573—Invoice Number ........................................................................... 9-115
PDS 0574—Arrival Date .................................................................................. 9-116
PDS 0575—Departure Date ............................................................................ 9-117
PDS 0576—Folio Number ............................................................................... 9-118
PDS 0577—Property Phone Number.............................................................. 9-120
PDS 0578—Billing Adjustment........................................................................ 9-122
PDS 0579—Invoice Date................................................................................. 9-124
PDS 0580—Room Rate .................................................................................... 9-125
PDS 0581—Total Room Tax ........................................................................... 9-127
PDS 0582—Program Code .............................................................................. 9-129
PDS 0583—Phone Charges ............................................................................. 9-130
PDS 0584—Restaurant Charges ...................................................................... 9-132
PDS 0585—Mini-Bar Charges.......................................................................... 9-134
PDS 0586—Gift Shop Charges ........................................................................ 9-136

xvi May 2004 • IPM Clearing Formats
Table of Contents
PDS 0587—Laundry and Dry Cleaning Charges ............................................ 9-138
PDS 0588—Other Services .............................................................................. 9-140
PDS 0589—Invoice Creation Date/Time ........................................................ 9-142
PDS 0590—Party Identification....................................................................... 9-144
PDS 0591—Party Name................................................................................... 9-146
PDS 0592—Party Address ............................................................................... 9-148
PDS 0593—Party Postal Information .............................................................. 9-150
PDS 0594—Party Contact ................................................................................ 9-152
PDS 0595—Card Acceptor Type..................................................................... 9-154
PDS 0596—Card Acceptor Tax ID.................................................................. 9-160
PDS 0597—Total Tax Amount ........................................................................ 9-162
PDS 0598—Total Tax Collected Indicator ...................................................... 9-166
PDS 0599—Corporation VAT Number ........................................................... 9-168
PDS 0600—Card Acceptor Reference Number .............................................. 9-169

Overview ...........................................................................................................10-1
PDS 0601—Party Nature of Filing.....................................................................10-2
PDS 0602—Party Supplemental Data 1 ............................................................10-3
PDS 0604—Transaction Supplemental Data 1 .................................................10-7
PDS 0606—Freight Amount ............................................................................ 10-11
PDS 0607—Duty Amount................................................................................ 10-13

IPM Clearing Formats • May 2004 xvii
Table of Contents
PDS 0608—Destination Postal Code .............................................................. 10-15
PDS 0609—Destination State/Province Code................................................. 10-16
PDS 0610—Destination Country Code ........................................................... 10-17
PDS 0612—Ship Date...................................................................................... 10-18
PDS 0613—Ship-From Postal Code ................................................................ 10-19
PDS 0614—Order Date ................................................................................... 10-20
PDS 0615—Medical Services Ship to Health Industry Number..................... 10-21
PDS 0616—Contract Number.......................................................................... 10-22
PDS 0617—Medical Services Price Adjustment.............................................. 10-23
PDS 0618—Medical Services Product Number Qualifier............................... 10-24
PDS 0619—User Name.................................................................................... 10-25
PDS 0620—Oil Company Brand Name .......................................................... 10-26
PDS 0621—Purchase Time.............................................................................. 10-28
PDS 0622—Motor Fuel Service Type.............................................................. 10-30
PDS 0623—Motor Fuel Information ............................................................... 10-31
PDS 0624—User Account Number ................................................................. 10-34
PDS 0625—User Telephone Number ............................................................. 10-35
PDS 0626—Billing Statement Period .............................................................. 10-36
PDS 0627—Billing Event 1.............................................................................. 10-38
PDS 0629—Odometer Reading....................................................................... 10-42
PDS 0630—Vehicle Number ........................................................................... 10-44
PDS 0631—Driver Number/ID Number ......................................................... 10-46
PDS 0632—Product Type Code...................................................................... 10-48

xviii May 2004 • IPM Clearing Formats
Table of Contents
PDS 0633—Coupon/Discount Amount .......................................................... 10-50
PDS 0634—Tax Amount 1 .............................................................................. 10-51
PDS 0635—Tax Amount 2 .............................................................................. 10-52
PDS 0636—Call Date....................................................................................... 10-53
PDS 0637—Call Time ...................................................................................... 10-54
PDS 0638—Call To Information...................................................................... 10-55
PDS 0639—Call Duration ................................................................................ 10-58
PDS 0640—Call Time Period .......................................................................... 10-59
PDS 0641—Product Code ............................................................................... 10-61
PDS 0642—Item Description .......................................................................... 10-64
PDS 0643—Item Quantity ............................................................................... 10-65
PDS 0644—Call From Information ................................................................. 10-67
PDS 0645—Item Unit of Measure ................................................................... 10-70
PDS 0646—Unit Price...................................................................................... 10-71
PDS 0647—Extended Item Amount................................................................ 10-73
PDS 0648—Item Discount............................................................................... 10-75
PDS 0649—Call Usage Amount ...................................................................... 10-78
PDS 0654—Debit or Credit Indicator ............................................................. 10-80
PDS 0655—Call Long Distance Amount......................................................... 10-81
PDS 0658—Call Connect Amount................................................................... 10-83
PDS 0659—Other Description ........................................................................ 10-85
PDS 0663—Free-Form Description................................................................. 10-86
PDS 0670—Payer Name or User ID ............................................................... 10-87
PDS 0671—Date of Funds Requested ............................................................ 10-88

IPM Clearing Formats • May 2004 xix
Table of Contents
PDS 0672—Recipient Name (Seller) ............................................................... 10-89
PDS 0673—Date of Anticipated Receipt of Funds ......................................... 10-90
PDS 0674—Additional Trace/Reference Number Used by Card Acceptor ... 10-91
PDS 0675—Additional Transaction Description Data.................................... 10-92
PDS 0676—Card Acceptor VAT Number ....................................................... 10-93
PDS 0677—Customer VAT Number ............................................................... 10-94
PDS 0678—Unique Invoice Number .............................................................. 10-95
PDS 0679—Commodity Code ......................................................................... 10-96
PDS 0680—Authorized Contact Name ........................................................... 10-98
PDS 0681—Authorized Contact Phone .......................................................... 10-99
PDS 0682—Detail Tax Amount 1 ................................................................. 10-100
PDS 0685—Type of Supply .......................................................................... 10-124
PDS 0686—Tax Exempt Indicator ................................................................ 10-125
PDS 0687—Unique VAT Invoice Reference Number .................................. 10-127
PDS 0689—Corporate Identifier ................................................................... 10-128
PDS 0690—No Show Indicator..................................................................... 10-129
PDS 0691—Days Rented ............................................................................... 10-130
PDS 0692—Weekly Rental Amount.............................................................. 10-131
PDS 0693—Total Authorized Amount .......................................................... 10-132
PDS 0694—One Way Drop Off Charge ....................................................... 10-134
PDS 0695—Regular Mileage Charge............................................................. 10-135
PDS 0696—Extra Mileage Charge................................................................. 10-136

xx May 2004 • IPM Clearing Formats
Table of Contents
PDS 0697—Late Charge ................................................................................ 10-137
PDS 0698—Fuel Charge ................................................................................ 10-138
PDS 0699—Lodging Total Tax Amount........................................................ 10-139
PDS 0700—Towing Charges ......................................................................... 10-141
PDS 0701—Extra Charges ............................................................................. 10-142
PDS 0702—Other Charges ............................................................................ 10-143
PDS 0703—Total Room Nights ..................................................................... 10-144
PDS 0704—Prepaid Expenses....................................................................... 10-145
PDS 0705—Total Non-Room Tax Amount ................................................... 10-147
PDS 0706—Cash Advances ........................................................................... 10-149
PDS 0707—Valet Charges ............................................................................. 10-151
PDS 0708—Movie Charges ........................................................................... 10-153
PDS 0709—Business Center Charges ........................................................... 10-155
PDS 0710—Health Club Charges.................................................................. 10-157
PDS 0711—Fire Safety Act Indicator ............................................................ 10-159
PDS 0712—Net Fuel Price............................................................................. 10-160
PDS 0713—Restricted Ticket Indicator......................................................... 10-162
PDS 0714—Exchange Ticket Amount .......................................................... 10-163
PDS 0715—Exchange Fee Amount............................................................... 10-164
PDS 0716—Travel Authorization Code ........................................................ 10-165
PDS 0717—IATA Client Code ....................................................................... 10-166
PDS 0718—Employee/Temp Name/ID ........................................................ 10-167
PDS 0719—Employee Social Security Number or ID .................................. 10-168
PDS 0720—Job Description .......................................................................... 10-169

IPM Clearing Formats • May 2004 xxi
Table of Contents
PDS 0721—Job Code .................................................................................... 10-170
PDS 0722—Flat Rate Indicator...................................................................... 10-171
PDS 0723—Regular Hours Worked .............................................................. 10-172
PDS 0724—Regular Hours Rate .................................................................... 10-174
PDS 0725—Overtime Hours Worked ........................................................... 10-176
PDS 0726—Overtime Hours Rate ................................................................. 10-178
PDS 0727—Temp Start Date ......................................................................... 10-180
PDS 0728—Temp Week Ending ................................................................... 10-181
PDS 0729—Requestor Name or ID............................................................... 10-182
PDS 0730—Supervisor/Reports to ................................................................ 10-183
PDS 0731—Time Sheet Number ................................................................... 10-184
PDS 0732—Discount Amount ....................................................................... 10-185
PDS 0733—Subtotal Amount ........................................................................ 10-187
PDS 0734—Miscellaneous Expenses ............................................................ 10-189
PDS 0735—Service Descriptor Codes........................................................... 10-192
PDS 0736—Tracking Number or Pickup Number ....................................... 10-193
PDS 0737—Shipping Net Amounts............................................................... 10-194
PDS 0738—Incentive Amount ...................................................................... 10-196
PDS 0739—Pickup Date................................................................................ 10-198
PDS 0740—Delivery Date ............................................................................. 10-199
PDS 0741—Number of Packages.................................................................. 10-200
PDS 0742—Package Weight ......................................................................... 10-201
PDS 0743—Unit of Measure.......................................................................... 10-202
PDS 0744—Shipping Party Information ....................................................... 10-203

xxii May 2004 • IPM Clearing Formats
Table of Contents
PDS 0745—Shipping Party Address.............................................................. 10-205
PDS 0746—Shipping Party Postal Information ............................................ 10-207
PDS 0747—Shipping Party Contact .............................................................. 10-210
PDS 0748—Delivery Party Information ........................................................ 10-212
PDS 0749—Delivery Party Address Information .......................................... 10-214
PDS 0750—Delivery Party Postal Information ............................................. 10-216
PDS 0754—Delivery Party Contact ............................................................... 10-242
PDS 0755—Line Item Total Amount............................................................. 10-244
PDS 0799—Test Case Traceability Identifiers .............................................. 10-247
PDS 1000–1099—Member-to-Member Proprietary Data.............................. 10-251
Appendix A Institution ID Data Elements and PDSs

Financial or Business Institutions ...................................................................... A-1
Technical Institutions ......................................................................................... A-2
Additional Information ....................................................................................... A-3
Appendix B Printing Card Acceptor Information on Cardholder

Statements
Financial Transactions Used as Sources ............................................................ B-1
General Mapping Guidelines ............................................................................. B-2

U.S. Region Financial Transaction............................................................... B-2
Non-U.S. Region Financial Transaction....................................................... B-3
Transactions Acquired in Canada................................................................ B-4

IPM Clearing Formats • May 2004 xxiii
Table of Contents
Messages Involving Certain Transaction Types ................................................ B-5
Messages Involving Airline Transactions........................................................... B-6

U.S. Region Airlines ..................................................................................... B-6
Airlines Outside the U.S. Region ................................................................. B-8
Messages Involving QPS Transactions .............................................................. B-9
Messages Involving Supermarket Transactions............................................... B-11
Messages Involving Warehouse Club Transactions ........................................ B-12
Messages Involving Service Industries Transactions....................................... B-14
Messages Involving PH Transactions .............................................................. B-15
Messages Involving IFC Transactions.............................................................. B-17
Messages Involving Non–Face-To-Face Transactions..................................... B-18
Messages Involving Payment Transactions ..................................................... B-19
Appendix C Edit Error Numbers and Messages

Overview ............................................................................................................ C-1
Error Listing by Error Number ........................................................................... C-2
Error Listing by MTI/Function Code................................................................ C-79

File Header/1644-697................................................................................. C-79
First Presentments/1240-200 ...................................................................... C-82
Financial Detail Addendum/1644-696 ......................................................C-104
Retrieval Request/1644-603.......................................................................C-179
Fee Collection (Retrieval Fee Billing)/1740-700 ......................................C-191
First Chargebacks (Full)/1442-450 and (Partial)/1442-453 ......................C-205
Second Presentments (Full)/1240-205, and (Partial)/1240-282 ...............C-224
Arbitration Chargebacks (Full)/1442-451 and (Partial)/1442-454............C-243
Fee Collection (Other)/1740-700, 780, 781, and 782...............................C-263
File Trailer/1644-695 .................................................................................C-275

xxiv May 2004 • IPM Clearing Formats
Using this Manual
This chapter contains information that helps you understand and use this
document.
Purpose ................................................................................................................... 1
Audience................................................................................................................. 1
Overview ................................................................................................................ 2
Excerpted Text ....................................................................................................... 3
Language Use ......................................................................................................... 3
Times Expressed..................................................................................................... 4
Functionality Not Initially Supported .................................................................... 4
Revisions ................................................................................................................. 5
Related Information................................................................................................ 5
Related MasterCard Technical Documents...................................................... 5
Related MasterCard Europe Technical Documents......................................... 6
Related ISO Documents................................................................................... 6
Support ................................................................................................................... 7
Member Relations Representative ................................................................... 7
Regional Representative................................................................................... 8

IPM Clearing Formats • May 2004 i
Using this Manual
Purpose
Purpose
The MasterCard IPM Clearing Formats manual defines the message flow, data
elements, and message formats that customers and users need to clear
transactions in an offline environment. Offline in this context means sending
transaction information in a clearing file after a previous authorization.
The Integrated Product Messages (IPM) format includes messages for the
following MasterCard and MasterCard Europe brands:
• MasterCard®
• Cirrus®
• Maestro®
Audience
MasterCard provides this manual for use by customers and users. Specifically,
business operations and technical systems development staff who work with
MasterCard International and MasterCard Europe should find this manual
useful. Customers and users include:
• Member financial institutions

• Bankcard associations
• Third-party card processing organizations
• National and regional ATM and POS networks
• Contracted service organizations
• Approved member designated organizations
For operations staff, this document identifies the flow of transactions, defines
the associated messages, and discusses topics that have an impact on the
operational activities at customer installations.
For technical staff, this document defines the message formats and data
contents that the clearing system supports. It serves as a primary technical
reference document to be used by customers when considering the
development of an interface to the clearing system.

IPM Clearing Formats • May 2004 1
Using this Manual
Overview
Overview
The following table provides an overview of this manual:
Chapter Description
Table of Contents A list of the manual’s tabbed chapters and sections.
Each entry references a chapter and page number.
Using this Manual A description of the manual’s purpose and its contents.
1 Overview A description of each of the message types found in this
manual.
2 File Header and Provides an overview and data element requirements for
Trailer Messages File Header and File Trailer messages.
3 Presentment, An overview and data element requirements for
Addendum, and presentment, addendum, and chargeback messages.
Chargeback Messages
4 Retrieval and Fee An overview and data element requirements for Retrieval
Collection Messages and fee collection messages.
5 Reconciliation An overview and data element requirements for
Messages reconciliation messages.
6 Administrative An overview and data element requirements for
Messages administrative messages.
7 Data Element Definitions of International Organization for
Definitions Standardization (ISO) 8583–1993 data elements and
subelements that the clearing system uses, including
applicable usage and values.
8 PDS Definitions–Part 1 Definitions of private data subelements (PDSs) 001–500
and their PDS values that the clearing system uses.
9 PDS Definitions–Part 2 Definitions of PDSs 501–600 and their PDS values that
the clearing system uses.
10 PDS Definitions–Part 3 Definitions of PDSs 601–1099 and their PDS values that
the clearing system uses.
A Institution ID Data Relationship of the data elements and PDSs used to
Elements and PDSs identify financial or business institutions and technical
institutions.
B Printing Card Acceptor Detailed procedures on how to extract information from
Information on data elements and PDSs onto cardholder statements.
Cardholder Statements

2 May 2004 • IPM Clearing Formats
Using this Manual
Excerpted Text
Chapter Description
C Edit Error Numbers Error numbers and messages that GCMS, the IPM Pre-
and Messages edit software, or both generate during the edit process.
Excerpted Text
At times, this document may include text excerpted from another document. A
note before the repeated text always identifies the source document. In such
cases, we included the repeated text solely for the reader’s convenience. The
original text in the source document always takes legal precedence.
Language Use
The spelling of English words in this manual follows the convention used for
U.S. English as defined in Merriam–Webster’s Collegiate Dictionary.
MasterCard is incorporated in the United States and publishes in the United
States. Therefore, this publication uses U.S. English spelling and grammar
rules.
An exception to the above spelling rule concerns the spelling of proper nouns.
In this case, we use the local English spelling.

Using this Manual
Times Expressed
Times Expressed
MasterCard is a global company with locations in many time zones. 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 manual 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 used in this manual into the correct time in
another zone:
St. Louis, Purchase, New York

Missouri USA USA UTC
Central Time Eastern Time
Standard time 8:00 9:00 14:00
(last Sunday in October to the
first Sunday in April a)
Daylight saving time 8:00 9:00 13:00
(first Sunday in April to last
Sunday in October)
a For Central European Time, last Sunday in October to last Sunday in March.
Functionality Not Initially Supported

Some information in this manual may be shaded. Shading indicates IPM
functionality not currently supported by GCMS.

Using this Manual
Revisions
Revisions
MasterCard periodically will issue revisions to this document as we implement
enhancements and changes, or as corrections are required.
With each revision, we include a Summary of Changes describing how the text
changed. Revision markers (vertical lines in the right margin) indicate where
the text changed. The date of the revision appears in the footer of each page.
Occasionally, we may publish revisions or additions to this document in a

Global Operations Bulletin or other bulletin. Revisions announced in another
publication, such as a bulletin, are effective as of the date indicated in that
publication, regardless of when the changes are published in this manual.
Related Information
The following documents and resources provide information related to the
subjects discussed in this manual.
Related MasterCard Technical Documents

Refer to the Quick Reference Booklet for a description of the following
documents.
• Authorization System Manual
• Chargeback Guide
• Data Communications Manual
• File Transfer Manual
• GCMS Reference Manual
• MasterCom Administrator’s Manual
• Member Information Manual
• Settlement Manual

Using this Manual
Related Information
Members that use the Cirrus System, LLC service and logo or that process
online debit transactions should refer to the debit processing manuals
recommended by the Customer Operations Services team.
For definitions of key terms used in this document, please refer to the
MasterCard Dictionary on the Member Publications home page (on
MasterCard OnLine® and the MasterCard Electronic Library CD-ROM). You
also may access the MasterCard Dictionary from the main menu and bookmark
pane of most manuals.
To order MasterCard manuals, please use the Ordering Publications service on

MasterCard OnLine®, or contact the Customer Operations Services team.
Related MasterCard Europe Technical Documents

Direct MasterCard Europe (formerly Europay) inquiries to the following
address:
Business Information Department

MasterCard Europe
198A Chaussee de Tervuren
1410 Waterloo, Belgium
Related ISO Documents

The message format specifications contained in this manual are based on the
ISO 8583–1993: Bank Card Originated Messages—Interchange Message
Specifications—Content for Financial Transactions specification.
The following ISO standards documents were employed in the development of

this specification, and may be referenced in the text of the document. They
are listed here as a reference:
ISO 3166–1981: Codes for the Representation of Names of Countries
ISO 4217–1981: Codes for the Representation of Currencies and Funds

Using this Manual
Support
Support
Please address your questions to the Customer Operations Services team as
follows:
Phone: 1-800-999-0363 or 1-636-722-6176

1-636-722-6292 (Spanish Language support)
Fax: 1-636-722-7192
E-mail: Canada, Caribbean, and U.S. member_support@mastercard.com

Asia/Pacific Local office contact information
Europe css@mastercard.com
South Asia/Middle East/Africa emeaap@mastercard.com
Latin America (Spanish
Language support) lagroup@mastercard.com
Address: MasterCard International Incorporated

Customer Operations Services
2200 MasterCard Boulevard
O’Fallon MO 63366-7263
USA
Telex: 434800 answerback: 434800 ITAC UI
Member Relations Representative

Member Relations representatives assist U.S. members with marketing
inquiries. They interpret member requests and requirements, analyze them,
and if approved, monitor their progress through the various MasterCard
departments. This does not cover support for day-to-day operational
problems, which the Customer Operations Services team addresses.
To find out who your U.S. Member Relations representative is, contact your
local Member Relations office:
Atlanta 1-404-459-2400
Chicago 1-847-375-4000
Purchase 1-914-249-2000
San Francisco 1-925-866-7700

Using this Manual
Support
Regional Representative
The regional representatives work out of the regional offices. Their role is to
serve as intermediaries between the members and other departments in
MasterCard. Members can inquire and receive responses in their own
language and during their office’s hours of operation.
To find out the location of the regional office serving your area, call the
Customer Operations Services team at:
Phone: 1-800-999-0363 or 1-636-722-6176
1-636-722-6292 (Spanish Language support)

1 Overview
This chapter describes the structure of IPM offline messages and the flow of
these message types between acquirers and issuers.
Clearing Introduction ..........................................................................................1-1

Transaction Processing Flow Through the Clearing System .......................1-2
IPM Offline Message Structure............................................................................1-3
IPM Offline File Structure ...................................................................................1-8

Basic Clearing System Message Flow...........................................................1-9
Acquirer to Clearing System to Issuer ..........................................................1-9
Issuer to Clearing System to Acquirer ..........................................................1-9
Clearing System to Issuer or Acquirer........................................................1-10

IPM Clearing Formats • May 2004 1-i
Overview
Clearing Introduction
Clearing by means of the IPM format is the movement of transaction
information from the member to the clearing system or from the clearing
system to the member. “Offline clearing” is the practice of sending transaction
information in a clearing file after a previous authorization, if applicable. The
IPM format provides the vehicle for delivery of these messages. The sending
member places messages into a clearing file (see “Offline Message Structure”
later in this chapter), and sends this transaction data for clearing to the clearing
system seven days a week, 24 hours a day. The clearing system has
predetermined cutoff times throughout each day when it processes all files
received from members since the last cutoff. Refer to the GCMS Reference
Manual for processing times.
IPM messages are based on the variable-length specifications of the

International Organization for Standardization (ISO) 8583–1993 Financial
Transaction Card Originated Messages—Interchange Message Specifications.
Because the clearing system with IPM is offline, it supports only non-
interactive IPM messages (Notification/1x4x). ISO defines Notification/1x4x
with a 4 in the third position in the Message Type Identifier (MTI). Refer to
chapter 7 of this manual for more information on MTIs and data element
definitions.
In each IPM message there are institution identifiers—Transaction Destination

Institution ID Code (Data Element [DE] 93) and Transaction Originator
Institution ID Code (DE 94). Upon receipt of the files, the clearing system
performs edits, checks data for accuracy, and directs the messages to the
appropriate members based on the identifiers. (Refer to appendix A of this
manual for more information on institution ID data elements and PDSs.)
After the acquirer “presents” transaction data to the clearing system in a First
Presentment/1240, the issuer either accepts the data as is or disputes the data.
If the issuer accepts the First Presentment/1240, the transaction is posted to the
cardholder’s account and eventually presented for payment via the cardholder
statement. If the issuer disputes the data, members may exchange transaction
information through multiple processing (chargeback) cycles. In doing so, IPM
allows transaction history to be passed from one cycle to the next. The
following diagram depicts this information flow from a First Presentment/1240
through all possible chargeback cycles.
Members are not required to exhaust all chargeback cycles once they start the
chargeback process to achieve dispute resolution. Refer to the MasterCard
Chargeback Guide for more information.

IPM Clearing Formats • May 2004 1-1
Overview
Transaction Processing Flow Through the Clearing System

The following diagram depicts the transaction processing flow through the
clearing system starting with the cardholder:
First Presentment /1240 First Presentment /1240
Retrieval Request /1644 Retrieval Request /1644

Cardholder Card
Acceptor Fee Collection (Retrieval Fee Billing)/1740 Fee Collection (Retrieval Fee Billing)/1740
First Chargeback (Partial)/1442 First Chargeback (Partial) /1442

First Chargeback (Full)/1442 Clearing First Chargeback (Full) /1442
System
Acquirer Second Presentment (Partial)/1240 Second Presentment (Partial) /1240

Issuer
Second Presentment (Full)/1240 Second Presentment (Full) /1240
Arbitration Chargeback (Partial)/1442 Arbitration Chargeback (Partial) /1442

Arbitration Chargeback (Full /1442 Arbitration Chargeback (Full) /1442
The following diagram depicts the transaction processing flow for Fee
Collection transactions:
Fee Collection (Other)/1740 Fee Collection (Other)/1740
Fee Collection Return/1740 Fee Collection Return/1740

Sending Clearing Receiving
Member System Member
Fee Collection Resubmission/1740 Fee Collection Resubmission/1740
Fee Collection Arbitration Return/1740 Fee Collection Arbitration Return/1740
After collecting clearing data and routing it to the appropriate receiver,

settlement occurs, which is the process of exchanging funds among members.
Refer to the MasterCard Settlement Manual for settlement information.

1-2 May 2004 • IPM Clearing Formats
Overview
IPM Offline Message Structure

IPM is a variable-length format that facilitates the addition of new data
elements while allowing the message receiver to manage the recognition and
use of the new data through use of a bit map representation. It is based on
the ISO 8583–1993 specification.
Data elements constitute each IPM message. ISO dictates the presence of
certain data elements in each message type, while allowing individual
applications to optionally define others. Chapter 7, “Data Element Definitions,”
of this manual describes each data element the clearing system uses, detailing
the length (whether fixed or variable), content (alphabetic, numeric, and so
on), how the clearing system uses it, and possible corresponding values.
Data elements that require more than one data field contain subelements. ISO
defined subelements for certain data elements, are reflected in this manual.
However, ISO has allowed individual applications to define subelements for
certain data elements as repositories for additional data in messages. These
“private” data subelements (PDSs) are detailed in chapters 8 and 9. Refer to
DE 48 in chapter 7 and the beginning of chapter 8 for PDS encoding
information.
Clearing system requirements for data element and PDS usage in each message
are defined in chapters 2 through 6 of this manual. Each IPM message
contains the following data elements:
Message Type Identifier describes each message class and function. Its contents
are as follows: (Refer to “Message Type Identifier” in chapter 7 for a
comprehensive list of MTIs that the clearing system uses.)
General
Position Description Values Description Example
first ISO version 1 ISO 8583–1993 (The version 1644
on which the clearing system
IPM formats is based)
second message class 2 Financial (12xx) messages 1240
4 Chargeback (14xx) messages 1442
6 Administrative (16xx) 1644
messages
7 Fee Collection (17xx) 1740
messages

Overview
General
Position Description Values Description Example
third message 4 notification 1644
function
fourth transaction 0 acquirer a 1240
originator 2 issuer a 1442
4 other a 1644
a Fee Collection Messages can be sent by acquirer, issuer, or other. The IPM format
convention is that the fourth position of the MTI always contains a ‘0’ in all Fee Collection
messages.
• Primary Bit Map indicates the presence or absence of Secondary Bit Map,
(DE 1) through Message Authentication Code (MAC) (DE 64).
• Secondary Bit Map (DE 1) indicates the presence or absence of Reserved
(ISO) (DE 65) through Message Authentication Code (MAC) (DE 128).
• Function Code (DE 24) is a three-digit data element indicating the specific
purpose of a message in a message class. Refer to DE 24 in chapter 7 of
this manual for a complete list.
Most IPM messages also require Message Reason Code (DE 25). This is a
four-digit data element indicating the reason for sending a message. Refer to
DE 25 in chapter 7 for a complete list of DE 25 values.
The MTI and both bit maps are fixed-location data elements. The remaining
data elements in a message must be presented in ascending sequence by data
element number, and are not located in a certain fixed position. The location
of each of these data elements is dependent on the presence of the data
elements that precede it. For example, if Primary Account Number (DE 2),
Processing Code (DE 3), and Amount, Transaction (DE 4) are all present in a
message, then DE 4 may be located in positions 45–56. In another message,
DE 2 and DE 3 may not be present, and therefore DE 4 may be located in
positions 21–32. The following table depicts sample data element positioning
in a message:

Overview
Position(s) Description
1–4 MTI (always present)
5–12 Bit Map, Primary (always present)
13–20 Bit Map, Secondary (DE 1) (always present)
The following two fields are repeated until all the data elements in the bit maps are
presented:
21–xx field indicating length of first data element, in numeric order, in

message after DE 1, if corresponding data field is variable length
xx–yy field containing actual data in first data element after DE 1
As shown in the previous table, the data field of a variable-length data element
is preceded by a two- or three-digit length indicator field, represented
throughout this manual as the LL portion of LLVAR or LLL portion of LLLVAR.
(Refer to the beginning of chapter 7 for explanations of this and other labeling
conventions used throughout this manual.)
The indicator in the length field is right-justified with leading zeros, as follows:
Representation Data Field Length Length Field Contents

LLVAR two bytes 02
LLLVAR three bytes 002
The contents of fixed-length data elements are not preceded by a length field.

Overview
Assume a member wants to present the following data elements:
DE/
PDS Description Length Value
2 Primary Account Number 16 5412347890123456
(PAN)
3 Processing Code 6 000000
(retail purchase)
4 Amount, Transaction 12 000000025000
(USD 250.00)
12 Date and Time, Local 12 970228000000
Transaction (YYMMDDhhmmss)
p0148 Currency Exponents 4 8402
(currency code plus exponent
for USD)
49 Currency Code, Transaction 3 840
(represents USD)
71 Message Number 8 00000002
(correct sequential number)
94 Transaction Originator 6 005678
Institution ID Code (originated by ICA 5678)

Overview
DE 2, Currency Exponents (PDS 0148), and DE 94 are all variable-length fields.

The other data elements in this example are fixed length, and therefore do not
require a length indicator field. Following is the layout of the IPM message
that incorporates the data elements in the previous table:
Position(s) DE/PDS Description Value

1–4 - MTI 1240
5–12 - Bit Map, Primary a
13–20 1 Bit Map, Secondary a
21–22 length of DE 2 16
23–38 2 Primary Account Number (PAN) 5412347890123456
39–44 3 Processing Code 000000
45–56 4 Amount, Transaction 000000025000
57–68 12 Date and Time, Local Transaction 970228000000
72–75 48/p0148 tag for PDS 0148 0148
76–78 48/p0148 length of PDS 0148 004
79–82 48/p0148 contents of PDS 0148 8402
83–85 49 Currency Code, Transaction 840
86–93 71 Message Number 00000002
96–101 94 Transaction Originator Institution ID 005678
Code
a The actual values in this message are character representations of bit maps; in binary
format, each bit map is constructed of eight bytes, 64 bits. Refer to the following example
and the beginning of chapter 7 for more information.

Overview
IPM Offline File Structure
In binary format, the Primary Bit Map consists of the following arrangement of
bits in the previous example:
11110000 00010000 00000000 00000000 00000000 00000001 10000000 00000000

∧∧∧∧ ∧ ∧ ∧
Bit one indicates DE 1 is present, bit two indicates DE 2 is present, bit three indicates DE 3 is present, bit
four indicates DE 4 is present, bit 12 indicates DE 12 is present, bit 48 indicates DE 48 is present, and bit
49 indicates DE 49 is present.
In binary format, the Secondary Bit Map (DE 1) consists of the following
arrangement of bits in the previous example:
00000010 00000000 00000000 00000100 00000000 00000000 00000000 00000000

∧ ∧
Bit seven indicates DE 71 is present. (Because the second bit map indicates the presence of DE 65–DE
128, the seventh bit is equivalent to 64+7=71, therefore indicating the presence of DE 71.)
Bit 30 indicates DE 94 is present. (Calculated by adding 64+30=94.)

Offline clearing system messages are in files sent between members and
processed during clearing cycles. The message flows on the following pages
show issuer, clearing system, and acquirer requirements for processing or
actions and are based on conditions at the time of the transaction event. The
message flows assume that both the acquirer and issuer are using IPM offline
clearing formats.
Note that the exact placement of the messages in the diagrams are not
necessarily indicative of how they must appear in a file. Messages may appear
in any order in a clearing file with the following exceptions:
• A file must begin with a File Header/1644 and end with a File Trailer/1644.
• A Financial Detail Addendum/1644 must immediately follow the associated
Financial Presentment/1240.
• Message Exception/1644 messages are immediately followed by the
rejected message.
In addition, each message in a file must contain Message Number (DE 71) with
a unique value. The value in DE 71 for each message must be greater than the
value in the previous message. DE 71 must be reset to 00000001 in the File
Header/1644 of each logical file.
The file a member receives from the clearing system is delivered in a specific
sequence. See the GCMS Reference Manual for more information.

Overview
Basic Clearing System Message Flow

All offline clearing system messages are Notification (1x4x) messages. The
following diagram depicts a typical flow for this message type:
1x4x
1
Clearing 1x4x
Origination Destination
System 2
Acquirer to Clearing System to Issuer

The following flow depicts the possible offline messages that an acquirer may
send to the clearing system, and the clearing system forwards to the issuer:
File Header/1644 File Header/1644
First Presentment /1240 First Presentment /1240
Financial Detail Addendum/1644 Financial Detail Addendum/1644
Fee Collection (Retrieval Fee Billing)/1740 Fee Collection (Retrieval Fee Billing)/1740
Fee Collection (Other) /1740 Second Presentment (Full)/1240
Fee Collection Return/1740 Clearing Second Presentment (Partial)/1240
System
Fee Collection Resubmission /1740 Fee Collection (Other)/1740
Acquirer Issuer
Fee Collection Arbitration Return /1740 Fee Collection Return/1740
Second Presentment (Partial) /1240 Fee Collection Resubmission/1740
Second Presentment (Full) /1240 Fee Collection Arbitration Return/1740
File Trailer/1644 File Trailer/1644
Issuer to Clearing System to Acquirer

The following flow depicts the possible offline messages that an issuer may
send to the clearing system, and the clearing system forwards to the acquirer:
File Header/1644 File Header/1644
Fee Collection (Other)/1740 Retrieval Request/1644
Fee Collection Return/1740 First Chargeback (Full)/1442
Fee Collection Resubmission/1740 First Chargeback (Partial)/1442
Fee Collection Arbitration Return/1740 Arbitration Chargeback (Full)/1442
Retrieval Request /1644 Clearing Arbitration Chargeback (Partial)/1442
System
First Chargeback (Partial) /1442 Fee Collection (Other)/1740
Issuer Acquirer
First Chargeback (Full) /1442 Fee Collection Return /1740
Arbitration Chargeback (Partial) /1442 Fee Collection Resubmission/1740
Arbitration Chargeback (Full) /1442 Fee Collection Arbitration Return/1740
File Trailer/1644 File Trailer/1644

Overview
Clearing System to Issuer or Acquirer

The following flow depicts the possible offline messages that the clearing
system may send to the issuer or acquirer:
File Header/1644
Text Message/1644
Currency Update/1644 Issuer
Clearing Fee Collection (Clearing System-Generated)/1740
or
System Message Exception/1644
File Reject/1644
File Currency Summary /1644
Financial Position Detail /1644
Acquirer
File Trailer /1644

2 File Header and Trailer Messages
This chapter describes the formats for all file header and trailer messages that
the clearing system uses. The layouts on the following pages identify all
required, conditional, optional, or clearing system–provided data elements for
these messages.
File Header/1644 Messages.................................................................................2-1
File Trailer/1644 Messages ..................................................................................2-2
Member-Generated Files .....................................................................................2-2

Offline Files versus Offline Transmissions...................................................2-2
Containing One Logical File .........................................................................2-3
Containing More than One Logical File .......................................................2-3
Member-Generated Offline File Structure ....................................................2-4
File ID............................................................................................................2-4
Processing Mode ...........................................................................................2-5
Trailer Total Reconciliation...........................................................................2-5
MasterCard-Generated Files ................................................................................2-5

Sequence of the MasterCard Generated Files ..............................................2-5
Sequence of the Early Reconciliation File....................................................2-8
File Header (Member-Generated)/1644 ...........................................................2-13

File Header and Trailer Messages
File Header (MasterCard-Generated)/1644.......................................................2-14
File Trailer (Member-Generated)/1644.............................................................2-15
File Trailer (MasterCard-Generated)/1644 ........................................................2-16

2-ii May 2004 • IPM Clearing Formats
Message Types and Associated Function Codes

This chapter describes the formats for the messages listed below:
Message Type Function

Identifier Code Description
1644 697 File Header (Member-Generated)
697 File Header (MasterCard-Generated)
695 File Trailer (Member-Generated)
695 File Trailer (MasterCard-Generated)
This chapter also describes the structure of offline IPM clearing files and
transmissions.
File Header/1644 Messages

A File Header/1644 is each file’s first message. It provides information such as
the following:
• Originating member ID or processor ID
• File ID
• Transmission ID (optionally provided by members, processors, or both)
• File direction (incoming [MasterCard-generated] or outgoing [Member-
generated])
• Processing Mode (production or test)
• Reversal Indicator
• Originating Message Format
The message must contain 1644 in the Message Type Identifier (MTI) and 697
in Function Code (Data Element [DE] 24) to identify it as a File Header/1644.

File Trailer/1644 Messages
File Trailer/1644 Messages

A File Trailer/1644 is each file’s last message. It provides information such as
the following:
• The File ID that links the File Trailer/1644 with the File Header/1644
• Hash totals used to validate the file’s integrity
The message must contain 1644 in the MTI and 695 in DE 24 to identify it as a
File Trailer/1644.
Member-Generated Files
This manual distinguishes between “offline files” and “offline transmissions.”
Offline Files versus Offline Transmissions

An offline file (also referred to as a “logical file”) contains a single File
Header/1644, followed by various IPM clearing messages, followed by a single
File Trailer/1644. An offline file’s File ID (Private Data Subelement [PDS] 0105)
uniquely identifies each file.
An offline transmission (also referred to as a “physical file”) is a single dataset

or bulk file that contains one or more logical files. A File Header/1644 and a
File Trailer/1644 define each logical file. There are no “transmission header”
or “transmission trailer” messages to enclose an offline transmission. Instead,
the originator may link the logical files in the transmission by providing the
same value in Transmission ID (PDS 0110) in each logical file’s File
Header/1644. The clearing system does not provide PDS 0110 in files sent to
receiving members.
The transmission originator determines whether to submit a single logical file

or multiple logical files. There are no requirements related to the grouping of
IPM messages into logical files. For example, one originator may choose to
create a separate logical file for each different destination member. Another
originator may choose to create a separate logical file for Chargebacks and
Retrievals as opposed to Presentments.


Containing One Logical File
File Header/1644: File ID 1, Transmission ID 1
. (individual clearing messages)
File Trailer/1644: File ID 1

Containing More than One Logical File


File Header/1644–697: File ID 3, Transmission ID 1

Member-Generated Offline File Structure

Following are the file sequencing requirements for member-generated files:
• Each offline file (logical file) must begin with one File Header/1644 and
end with one File Trailer/1644.
• The File Header/1644 and File Trailer/1644 for each logical file must
contain the same value in PDS 0105.
• The file must contain at least one message in addition to the File
Header/1644 and File Trailer/1644.
• Multiple logical files may be present in a transmission (physical file). Each
logical file within a physical transmission is processed independently.
• Message Number (DE 71) must always contain 00000001 in the File
Header/1644. For each subsequent message in the logical file, the value in
DE 71 must be greater than the value in the previous message.
• All other clearing messages (such as First Presentment/1240, First
Chargeback/1442, and Retrieval Request/1644 messages) must follow the
File Header/1644 and precede the corresponding File Trailer/1644.
• Financial Detail Addendum/1644 messages must immediately follow their
related First Presentment/1240 messages.
• No other requirements exist for the sequencing of messages within a
logical file. Members may choose to submit messages from several
different sending member IDs in the same logical file.
File ID
File originators must create a unique PDS 0105 value for each logical file.
PDS 0105 includes:
• File Type—indicates whether the file is MasterCard- or member-generated.
This includes clearing files or MasterCard-generated Early Reconciliation
files.
• File Reference Date—indicates the date the originator processed or created
the file.
• Processor ID—for member-generated files, indicates the member ID of the
member or processor sending the file. For MasterCard-generated files, the
Processor ID indicates the member ID of the member or processor
receiving the file.

MasterCard-Generated Files
• File Sequence Number—a five-digit number the file originator assigns that
must be unique within each File Reference Date for each File Type and
Processor ID for files sent to MasterCard.
Processing Mode
File originators must indicate each logical file’s Processing Mode (PDS 0122)
value. PDS 0122 indicates the following:
• Production file
• Test file
The PDS 0122 value in the File Header/1644 applies to all transactions in the
logical file.
Trailer Total Reconciliation

Offline file receivers may verify that all non-financial and financial messages
the sender intended to include in a logical file were actually received by using
trailer totals.
Each File Trailer/1644 contains logical file totals as follows:

• File Amount, Checksum (PDS 0301) provides a hash total or checksum of
the Amount, Transaction (DE 4) for all messages in the file that contain
DE 4.
• File Message Counts (PDS 0306) in the File Trailer/1644 contains the total
number of messages (financial and non-financial) in the logical file,
including the File Header/1644 and File Trailer/1644.
Offline file receivers can accumulate a count and checksum as they process
each file. These accumulated totals can be used for reconciliation with the File
Trailer/1644 totals.
Sequence of the MasterCard Generated Files

GCMS has six clearing cutoffs per processing day. GCMS generates data for
members at each cutoff. Members and processors may choose to receive
clearing data four, five, or six times per day. If a member chooses to receive
data less than six times per day, this results in the merging of their clearing
activity across cycle boundaries.

The sequence of the individual messages in a merged clearing file remains

identical to the sequencing of messages in a file containing data from a single
clearing cycle.
Within a given MasterCard destination (a combination of endpoint and

Destination ID [DE 93]), GCMS sequences MasterCard-generated files as shown
in the following table.
Sequence of MasterCard-Generated Files
MTI-Function Code Message Type

1644-697 File Header
1644-693 Text Messages
1644-640 Currency Updates
1240-200 First Presentments
1644-696 Financial Detail Addendum (if required)
1644-603 Retrieval Requests
1740-700 Fee Collections (Retrieval Fee Billing)
1442-450, 1442-453 First Chargebacks, Full and Partial
1240-205, 1240-282 Second Presentments, Full and Partial
1442-451, 1442-454 Arbitration Chargebacks, Full and Partial
1740-700, 1740-780, Fee Collections (non–Retrieval Fee Billing)—Member
1740-781, 1740-782, generated, Returns, Resubmissions, Arbitration Returns,
1740-783 and MasterCard-Generated
1644-691, 1644-699 Message Exception and File Reject
1644-680, 1644-685 File Currency Summary and Financial Position Details
1644-695 File Trailer
When there are multiple message types (for example, multiple first
presentments) for multiple receiving member IDs, the clearing system
sequences them as follows:
• All message types except 1644-693 (Text Message) and 1644-640 (Currency
Update): first by receiving member ID and then by message type
• 1644-693 (Text Message) and 1644-640 (Currency Update) messages: once
per processor by the first occurring (lowest) member ID and then by
message type.

If a member or processor processes for multiple member IDs, GCMS constructs

the MasterCard-generated file as shown in the following table. For example,
suppose that member (processor) ID 004444, endpoint 1, processes for
member ID 002222 and member ID 003333. When processing for multiple
member IDs, GCMS would construct the receiver’s file as shown below:
Sequencing of MasterCard Generated Member or Processor Files
Endpoint 1, to
MTI-Function Code Description Member ID (ICA):
1644-697 File Header 004444
1644-693 Text Message 002222
1644-640 Currency Update 002222
1240-200 First Presentment 002222
1644-696 Financial Detail Addendum 002222
1240-282 Second Presentment (Partial) 002222
1644-685 Financial Position Detail 002222
1240-200 First Presentment 003333
1644-603 Retrieval Request 003333
1740-700 Fee Collection (Retrieval Fee 003333
Billing)
1442-450 First Chargeback—Full Amount 003333
1240-205 Second Presentment 003333
1442-451 Arbitration Chargeback—Full 003333
Amount
1740-700 Fee Collection (non–Retrieval Fee 003333
Billing)
1644-695 File Trailer 004444

Sequence of the Early Reconciliation File

Members electing to receive MasterCard-generated Early Reconciliation files
will receive one physical file for each physical file sent to MasterCard for
processing. If the member sends a physical file containing two logical files,
GCMS will return one Early Reconciliation file. The Acknowledgement
Reconciliation messages for the two logical files contained in the file sent to
MasterCard will be contained in two logical files within the single Early
Reconciliation physical file.
The sequence of an IPM MasterCard-generated Early Reconciliation physical

file is similar to the sequence in the following table. Suppose that member
(processor) ID 004444, endpoint 1, processes for member IDs 002222, 003333,
005555, and 006666. When processing for multiple member IDs, GCMS would
construct the receiver’s file as shown below:
Sequencing of MasterCard Generated Member or Processor Files—Early

Reconciliation
Endpoint 1, to
MTI-Function Code Description Member ID (ICA):
1644-697 File Header 004444
1644-680 File Currency Summary 002222
1644-691 Message Exception 005555
1644-691 Message Exception 006666
1644-695 File Trailer 004444
Note This example assumes that data for all members was received in two logical
files. Each logical file contains a file header, followed by various IPM clearing
messages, followed by a file trailer.
For additional information refer to the GCMS Reference Manual.

Data Element Flow
Data Element Flow

Several entities may insert or modify the data elements1 in an IPM message as
it flows from the message origin to the clearing system and from the clearing
system to the message destination. These entities typically include the
member or processor at the origin, the clearing system, and the member or
processor at the destination.
In the message format layouts, the following three columns provide

information to the originator, clearing system, and destination related to the
data element requirements:
Entity Description
Org Originator Requirements. The message originator must satisfy this data
element’s requirements before sending the message. Examples of
originators include a First Presentment/1240 acquirer or a First
Chargeback/1442 issuer.
Sys Clearing System Requirements. The clearing system may insert, correct,
modify, or echo this data element while, for example, routing a message
from the origin to the destination. The clearing system may overwrite the
data element and thereby overwrite any previous content.
Dst Destination Requirements. The message destination must expect this data
element (read it) and accept this data element (process it) if the originator
requirements are satisfied. Examples of destinations include a First
Presentment/1240 issuer or a First Chargeback/1442 acquirer.
1 In this and the following two tables, references to “data elements” include data elements,
PDSs (“p….” in the message layouts), and subfields (“s…” in the message layouts).

Message Format Data Element Requirements

The following notations describe the requirements for each data element.
These notations appear in the Org, Sys, and Dst columns.
Usage
Code Description
M Mandatory. The data element is required in the message.
C Conditional. The data element is required in the message if the conditions

described in the accompanying text are applicable.
O Optional. The data element is not required but may be included in the
message at the message originator’s option.
X Clearing System. The clearing system may (or will) insert or overwrite the
data element, depending on specific clearing system support services
provided for individual programs and services.
ME Mandatory Echo. The data element is required in an online response
message and must contain the same value (“echoed”) from the original
request or advice message.
CE Conditional Echo. The data element is required in an online response
message if it was present in the original request or advice message, and it
must contain the same value (“echoed”) from the original message.
XE Clearing System Echo. The data element must contain the value from the
original online request or advice (“echoed”), if present. Otherwise, the
clearing system supplies the values, if present.
Not Required or Not Applicable. The data element is not required or not
applicable, and the transaction originator should not include it if this
symbol is present in the “Org” column.

Data Element Usage in Messages

The layouts in this chapter describe how data elements are used in each
message. The following table shows all the possible usage combinations:
Usage
Org Sys Dst Description

M • M Mandatory; originator must provide the data element.
M X M Mandatory; originator must provide the data element; clearing
system adjusts/appends data.
C • C Conditionally required; conditions are described in Comments
column.
C X M Conditionally required; clearing system may adjust/append data and
always provides the data element.
C X C Conditionally required; clearing system adjusts/appends data.
• X C Clearing system provides the data element conditionally.
• X M Clearing system always provides the data element.
O • C Optional; originator may provide the data element.
O X C Optional; originator may provide the data element; clearing system
adjusts/appends data.
M • • Mandatory; originator must provide the data element; clearing
system does not forward data.
C • • Conditionally required; clearing system does not forward data.
O • • Optional; clearing system does not forward data.
• X • MasterCard internal use.
Data Elements and PDSs Not Initially Supported

Some data elements and PDSs in the message layouts may be shaded. Shading
indicates those data elements and PDSs not currently supported by GCMS.

Intra-European Transactions
Some data elements and PDSs are specified for intra-European use only. Intra-
European messages are those in which both the issuer and acquirer are in the
European region.
Maestro and Cirrus Transactions

During the next few years, the clearing system will be updated to
accommodate processing of offline Maestro and Cirrus transactions. These
transactions will migrate from the ECCSS system in Waterloo, Belgium to the
GCMS system in St. Louis. New elements and values have been added to this
manual to prepare for processing these transactions by GCMS.

File Header (Member-Generated)/1644
File Header (Member-Generated)/1644

No. Data Element Name Org Sys Dst
- Message Type Identifier M • •
- Bit Map, Primary M • •
1 Bit Map, Secondary M • •
24 Function Code M • •
48 Additional Data M • •
p0026 File Reversal Indicator C • •
s1 File Reversal Indicator C • •
s2 Central Site Processing Date of Original file C • •
p0105 File ID M • •
s1 File Type M • •
s2 File Reference Date M • •
s3 Processor ID M • •
s4 File Sequence Number M • •
p0110 Transmission ID O • •
s1 Transmission Type O • •
s2 Transmission Reference Date O • •
s3 Processor ID O • •
s4 Transmission Sequence Number O • •
p0122 Processing Mode M • •
p0191 Originating Message Format O • •
71 Message Number M • •

File Header (MasterCard-Generated)/1644
File Header (MasterCard-Generated)/1644

- Message Type Identifier • X M
- Bit Map, Primary • X M
1 Bit Map, Secondary • X M
24 Function Code • X M
48 Additional Data • X M
p0105 File ID • X M
s1 File Type • X M
s2 File Reference Date • X M
s3 Processor ID • X M
s4 File Sequence Number • X M
p0122 Processing Mode • X M
71 Message Number • X M

File Trailer (Member-Generated)/1644
File Trailer (Member-Generated)/1644

- Message Type Identifier M • •
- Bit Map, Primary M • •
1 Bit Map, Secondary M • •
24 Function Code M • •
48 Additional Data M • •
p0105 File ID M • •
p0191 Originating Message Format O • •
p0301 File Amount, Checksum M • •
p0306 File Message Counts M • •
71 Message Number M • •

File Trailer (MasterCard-Generated)/1644
File Trailer (MasterCard-Generated)/1644

p0105 File ID • X M
p0301 File Amount, Checksum • X C
p0306 File Message Counts • X M

3 Presentment, Addendum, and Chargeback
Messages
This chapter describes the formats for all presentment, addendum, and
chargeback messages that the clearing system uses. The layouts on the
following pages identify all required, conditional, optional, or clearing system–
provided data elements for these messages.
First Presentment/1240 Messages .......................................................................3-1
Financial Detail Addendum/1644 Messages.......................................................3-1

General Ticket Information)/1644................................................................3-2
Trip Leg Data)/1644 ......................................................................................3-2
Financial Detail Addendum (Vehicle Rental Detail)/1644...........................3-3
Financial Detail Addendum (Lodging Summary)/1644 ...............................3-3
Financial Detail Addendum (Temporary Services)/1644.............................3-4
Financial Detail Addendum (Shipping/Courier Services)/1644 ..................3-4
Financial Detail Addendum (Payment Transaction Detail)/1644................3-5
Financial Detail Addendum (Telephony Billing Services)/1644 .................3-5
Financial Detail Addendum (Electronic Invoices)/1644 ..............................3-6
Requirements)/1644 ......................................................................................3-7
Information)/1644 .........................................................................................3-8
Financial Detail Addendum (Corporate Line Item Detail)/1644 .................3-9
Financial Detail Addendum (Generic Detail)/1644 .....................................3-9
First Chargeback/1442 and Arbitration Chargeback/1442 Messages ..............3-10
Second Presentment/1240 Messages ................................................................3-10

Presentment, Addendum, and Chargeback Messages
First Presentment/1240......................................................................................3-15

General Ticket Information)/1644 ....................................................................3-21

Trip Leg Data)/1644 ..........................................................................................3-26
Financial Detail Addendum (Vehicle Rental Detail)/1644...............................3-31
Financial Detail Addendum (Lodging Summary)/1644 ...................................3-37
Financial Detail Addendum (Temporary Services)/1644.................................3-46
Financial Detail Addendum (Shipping/Courier Services)/1644.......................3-51
Financial Detail Addendum (Payment Transaction Detail)/1644 ....................3-57
Financial Detail Addendum (Telephony Billing Service)/1644 .......................3-59

Addendum Messages ..................................................................................3-60
Billing—Detail)/1644 Message....................................................................3-65
Financial Detail Addendum (Electronic Invoices)/1644 ..................................3-70

Use of the Electronic Invoice Addendum Messages with
Other Addendum Messages........................................................................3-72
Invoice—Party Information)/1644 Message ...............................................3-75

Requirements)/1644 ..........................................................................................3-78

Information)/1644 .............................................................................................3-84
Financial Detail Addendum (Corporate Line Item Detail)/1644 .....................3-89
Financial Detail Addendum (Generic Detail)/1644..........................................3-94

First Chargeback/1442 and Arbitration Chargeback/1442 ...............................3-96
Second Presentment/1240............................................................................... 3-103

IPM Clearing Formats • May 2004 3-iii


1240 200 First Presentment
1644 696 Financial Detail Addendum
1442 450 First Chargeback (Full)
451 Arbitration Chargeback (Full)
453 First Chargeback (Partial)
454 Arbitration Chargeback (Partial)
1240 205 Second Presentment (Full)
282 Second Presentment (Partial)
The Function Code (Data Element [DE] 24) in each message indicates the
transaction’s primary type or function, and the Message Reason Code (DE 25)
indicates the primary reason for the transaction.
First Presentment/1240 Messages

An acquirer may initiate a First Presentment/1240 to advise the issuer or its
agent that a financial transaction was completed on its behalf.
The message must contain 1240 in the Message Type Identifier (MTI) and 200
in DE 24 to identify it as a First Presentment/1240.
Financial Detail Addendum/1644 Messages

A Financial Detail Addendum/1644 provides additional program, service, or
industry data to supplement the First Presentment/1240. This message must
contain 1644 in the MTI and 696 in DE 24 to identify it as a Financial Detail
Addendum/1644.
The following are descriptions for each type of addendum message.


General Ticket Information)/1644
This message supports ticketing transactions for airline and railway transactions
to provide passenger ticket information for the cardholder. Acquirers may
submit one occurrence of this message for each airline or railway transaction
to provide general ticket information.
When using this message, the information in Transaction Description (Private

Data Subelement [PDS] 0501), subfields 1–3, must be the following values:
• Usage Code: 01
• Industry Record Number: 000
• Occurrence Indicator: 001
Acquirers should also submit one or more occurrences of the Financial Detail
Addendum (Passenger Transport Detail—Trip Leg Data)/1644 message (Usage
Code 01, Industry Record Number 001). Each trip leg message occurrence
provides detailed information regarding one trip leg associated with the ticket.
Financial Detail Addendum (Passenger Transport Detail—Trip

Leg Data)/1644
This message supports ticketing transactions for airline and railway transactions
to provide detailed itinerary information for the cardholder. Acquirers may
submit 1–98 occurrences of this message. Each occurrence provides detailed
itinerary data for one trip leg associated with an airline or railway transaction.
When using this message, the information in PDS 0501, subfields 1–3, must be
the following values:
• Usage Code: 01
• Occurrence Indicator: 002–099
If this addendum detail describes an airline itinerary, the “City of

Origin/Airport Code” and “City of Destination/Airport Code” for each trip leg
should contain an Airport Code from the OAG, which contains a list of
standard airport and airline service abbreviations.
Acquirers must provide a single occurrence of the Financial Detail Addendum

(Passenger Transport Detail—General Ticket Information)/1644 message
(Usage Code 01, Industry Record Number 000) before the first occurrence of
trip leg data for airline or railway transactions.

Financial Detail Addendum (Vehicle Rental Detail)/1644

This message provides detailed vehicle rental information for the cardholder.
One occurrence of this message provides rental agreement data reporting for a
single vehicle rental transaction.
• Usage Code: 05
This message may be provided in a single occurrence (such as, a single

transaction for a single vehicle rental) or in multiple occurrences (a single
transaction for the rental of multiple vehicles).
Financial Detail Addendum (Lodging Summary)/1644

This message provides detailed information on lodging accommodations and
related expenses for the cardholder. One occurrence of this message provides
lodging accommodation reporting for a single lodging folio, such as a single
“stay” at a lodging facility with one “check-in” and one “check-out.”
• Usage Code: 06
This message may be provided in a single occurrence (such as a single

transaction for a single room rental) or in multiple occurrences (a single
transaction for the rental of several rooms).

Financial Detail Addendum (Temporary Services)/1644

The Temporary Services detail addendum provides detailed information
regarding the billing for services rendered on a temporary or contract basis.
The message layout provides information such as the employee job performed,
timekeeping, and billing rates.
When using this message, the information in PDS 0501, Transaction

Description, subfields 1–4, must be the following values:
• Usage Code: 07
• Occurrence Indicator: 001–999 (incremented by 1 for each occurrence)
• Message Number: Message Number (DE 71) from the First
Presentment/1240 message.
This message is optional; however if this addendum is submitted with a First

Presentment/1240 message for an incentive interchange rate program, and the
addendum is rejected due to invalid data, the First Presentment/1240 message
also will be rejected.
Financial Detail Addendum (Shipping/Courier Services)/1644

The Shipping/Courier Service detail addendum provides detailed information
regarding delivery or courier services. The message layout supports the
shipping and delivery tracking information.
When using this message, the information in PDS 0501, Transaction

Description, subfields 1–4, must be the following values:
• Usage Code: 08
• Occurrence Indicator: 001–999 (incremented by 1 for each occurrence)
This message is optional; however if this addendum is submitted with a First

Presentment/1240 message for an incentive interchange rate program, and the
addendum is rejected due to invalid data, the First Presentment/1240 message
also will be rejected.

Financial Detail Addendum (Payment Transaction Detail)/1644

This message supports data related to a program permitting MasterCard
cardholders to receive payments from a money transfer agent or a financial
institution. Within this program the cardholder’s issuer posts the credit to the
cardholder’s MasterCard account.
When using this message, the information in PDS 0501, subfields 1–3 must be
• Usage code: 10
This message occurs only once per transaction. It is optional; however if this
addendum is submitted with a First Presentment/1240 message for an incentive
interchange rate program, and the addendum is rejected due to invalid data,
the First Presentment/1240 message also will be rejected.
Financial Detail Addendum (Telephony Billing Services)/1644

The Telephony Billing Service detail addendum is designed to carry telephony
billing data and to allow issuers to supply more transaction information to their
consumer and corporate clients. These new addendum messages are intended
to encourage companies to pay for telephony services using a MasterCard
Corporate Purchasing card.
The enhanced data in the new addendum messages will provide information
normally received on monthly statements generated by the service provider.
The information in Transaction Description, PDS 0501, subfields 1–4, must be

the following values for Telephony Billing—Summary:
• Usage Code: 11
• Message Number: Message Number (DE 71), from the First


the following values for Telephony Billing—Details:
• Usage Code: 11
There can be a combined total of 999 occurrences of the two telephony Billing
addendum messages for an associated First Presentment/1240 message.
This message is optional; however GCMS will reject both Financial Detail
Addendum (Telephony Billing—Summary and Telephony Billing—Detail)/1644
messages submitted with a First Presentment/1240 message for an incentive
interchange rate program if either addendum contains invalid data. The
associated First Presentment/1240 message also will be rejected unless it was
submitted with a Processing Code (DE 3, subfield 1) of 20 (Credit), as a
Reversal (PDS 0025, subfield 1 contains “R”), or as a Collection Only
transaction (PDS 0165, subfield 1 contains “C”).
Financial Detail Addendum (Electronic Invoices)/1644

The Electronic Invoice detail addendum messages are designed to carry
electronic invoice data that is not present in other addendum messages, and to
allow issuers to supply more transaction information to their corporate clients.
These new addendum messages provide additional information passed
between buyer and seller in business-to-business (“B2B”) and electronic-
business-to-business (“eB2B”) transactions.

the following values when submitted for Electronic Invoice—Transaction Data:
• Usage Code: 09
• Occurrence Indicator: 001–998 (The total number of occurrences for both
the Electronic Invoice—Transaction Data and the Electronic Invoice—Party
Information cannot be greater than 999)


the following values when submitted for Electronic Invoice—Party Information:
• Usage Code: 09
• Occurrence Indicator: 002–999 (The total number of occurrences for both
the Electronic Invoice—Transaction Data and the Electronic Invoice—Party
Information cannot be greater than 999. There is a minimum of one
occurrence and a maximum of six occurrences of Electronic Invoice—Party
Information.)
This message is optional; however GCMS will reject both Financial Detail
Addendum (Electronic Invoice—Transaction Data and Electronic Invoice—
Party Information)/1644 messages, and any other addendum messages,
submitted with a First Presentment/1240 message for an incentive interchange
rate program if any of the addenda contain invalid data. The associated First
Presentment/1240 message also will be rejected unless it was submitted with a
Processing Code (DE 3, subfield 1) value of 20 (Credit), as a Reversal
(PDS 0025, subfield 1 contains “R”), or as a Collection Only transaction
(PDS 0165, subfield 1 contains “C”).

Requirements)/1644
The Financial Detail Addendum (Corporate Card Common Data
Requirements)/1644 message (Usage Code 98, Industry Record Number 000)
may be provided with any transaction in which one of the corporate cards is
used.
If a MasterCard Corporate Purchasing Card™ or other corporate program or

service is used for airline, railway, lodging, or vehicle rental, those industry-
specific addendum messages may be submitted in addition to the Corporate
Card Common Data Requirements message.
If the transaction is a business-to-business purchase, members may provide up

to 998 occurrences of the Financial Detail Addendum (Corporate Line Item
Detail)/1644 message in addition to the Financial Detail Addendum (Corporate
Card Common Data Requirements)/1644 message.

The card acceptor location, state/province, postal code, and country code
should be provided in Card Acceptor Name/Location (DE 43) of the related
First Presentment/1240 message (not in this addendum message). In addition,
the card acceptor location phone number should be provided in subfield 1 of
Merchant Inquiry Information (PDS 0170) of the related First Presentment/1240
message instead of in this addendum message.
• Usage Code: 98
This message occurs only once per transaction, and includes information
relevant to any transaction involving a corporate card.

Information)/1644
When a MasterCard Corporate Fleet Card® is used at a fuel location, the
Corporate Fleet Transaction Information message (Usage Code 98, Industry
Record Number 002) may be submitted to provide information related to the
purchase as a whole, such as motor fuel service type, product code, unit of
measure, or quantity.
In addition to this message, members may provide line item detail related to
non-fuel products purchased using a MasterCard Corporate Fleet Card® at fuel
locations via 1–98 occurrences of the Corporate Program Line Item Detail
message (Usage Code 98, Industry Record Number 950). One “line item
detail” message is submitted for each occurrence of line item data in the
transaction.
• Usage Code: 98
This message occurs only once per transaction, and includes the “common”
information related to the total fuel purchase.

Financial Detail Addendum (Corporate Line Item Detail)/1644

When a corporate card (for example, MasterCard Corporate Purchasing Card™
or MasterCard Corporate Fleet Card®) is used in a business-to-business
purchase, any line item detail related to the purchase is presented via 1–998
occurrences of the Financial Detail Addendum (Corporate Line Item
Detail)/1644 message (Usage Code 98, Industry Record Number 950). One of
these messages is submitted for each occurrence of line item data in the
transaction.
• Usage Code: 98
This message supports a single corporate program transaction with multiple

line item details. It may be repeated from 001–998 times for each corporate
card transaction. Each occurrence represents a single line item for a corporate
card transaction, or a single non-fuel item purchased with a MasterCard Fleet
Card at a fuel location.
Financial Detail Addendum (Generic Detail)/1644

This message supports data related to new programs and services the
Corporation introduces that require the presence of data not available in First
Presentment/1240 messages.
This format allows the Corporation to respond to new business opportunities

without waiting for the clearing system’s next release.
• Usage code: 99
• Occurrence indicator: 001–999

First Chargeback/1442 and Arbitration Chargeback/1442 Messages
First Chargeback/1442 and Arbitration Chargeback/1442

Messages
An issuer initiates First Chargeback/1442 and Arbitration Chargeback/1442
messages to partially or completely return a previous First Presentment/1240.
Depending on program and service rules, an issuer may charge back a First
Presentment/1240, or a subsequent Second Presentment/1240 that the acquirer
submitted.
These messages must contain 1442 in the MTI and one of the following values
in DE 24:
• 450 to indicate that the message is a First Chargeback (Full)/1442 for the
full First Presentment/1240 amount
• 453 to indicate that the message is a First Chargeback (Partial)/1442 for
part of the First Presentment/1240 amount
• 451 to indicate that the message is an Arbitration Chargeback (Full)/1442
for the full First Presentment/1240 amount
• 454 to indicate that the message is an Arbitration Chargeback (Partial)/1442
for part of the First Presentment/1240 or Second Presentment/1240 amount
The specific reason for the First Chargeback/1442 or Arbitration

Chargeback/1442 is in the Message Reason Code (DE 25).
Second Presentment/1240 Messages

An acquirer initiates Second Presentment/1240 messages to remedy a previous
First Chargeback/1442. These messages must contain 1240 in the MTI and one
of the following values in DE 24:
• 205 to indicate that the Second Presentment (Full)/1240 is for the full First
Presentment/1240 amount
• 282 to indicate that the message is a Second Presentment (Partial)/1240 for
part of the First Presentment/1240 or First Chargeback/1442 amount
The specific reason for the Second Presentment/1240 is in DE 25.

Data Element Flow
Data Element Flow

it flows from the message origin to the clearing system, and from the clearing

Entity Description


Usage
Code Description

z Not Required or Not Applicable. The data element is not required or not
applicable, and the transaction originator should not include it if present in
the “Org” column.


Usage

column, and in the data element or private data subelement
definitions section.
Data Elements and PDSs Not Initially Supported


European region.

manual to prepare for processing these transactions by GCMS.

First Presentment/1240
First Presentment/1240 Message Layout
- Message Type Identifier M • M
- Bit Map, Primary M X M
1 Bit Map, Secondary M X M
2 Primary Account Number (PAN) M • M
3 Processing Code M • M
s1 Cardholder Transaction Type M • M
s2 Cardholder “From” Account Type Code M • M
s3 Cardholder “To” Account Type Code M • M
4 Amount, Transaction M • M
5 Amount, Reconciliation C X C
6 Amount, Cardholder Billing O X C
8 Amount, Cardholder Billing Fee • X C
9 Conversion Rate, Reconciliation • X C
10 Conversion Rate, Cardholder Billing • X C
12 Date and Time, Local Transaction C • C
s1 Date C • C
s2 Time C • C
14 Date, Expiration O • C
22 Point of Service Data Code C • C
s1 Card Data Input Capability C • C
s2 Cardholder Authentication Capability C • C
s3 Card Capture Capability C • C
s4 Terminal Operating Environment C • C
s5 Cardholder Present Data C • C
s6 Card Present Data C • C
s7 Card Data Input Mode C • C
s8 Cardholder Authentication Method C • C
s9 Cardholder Authentication Entity C • C


s10 Card Data Output Capability C • C
s11 Terminal Data Output Capability C • C
s12 PIN Capture Capability C • C
23 Card Sequence Number O • C
24 Function Code M • M
25 Message Reason Code O • C
26 Card Acceptor Business Code M • M
30 Amounts, Original O • C
s1 Original Amount, Transaction O • C
s2 Original Amount, Reconciliation O • C
31 Acquirer Reference Data M • M
s1 Interchange Rate Designator M • M
s2 Acquirer’s BIN M • M
s3 Julian Processing Date YDDD M • M
s4 Acquirer’s Sequence Number M • M
s5 Check Digit M • M
32 Acquiring Institution ID Code O • C
33 Forwarding Institution ID Code M • M
37 Retrieval Reference Number O • C
38 Approval Code C • C
40 Extended Service Code C • C
41 Card Acceptor Terminal ID C • C
42 Card Acceptor ID Code C • C
43 Card Acceptor Name/Location M • M
s1 Card Acceptor Name M • M
s2 Card Acceptor Street Address C • C
s3 Card Acceptor City C • C
s4 Card Acceptor Postal (ZIP) Code M • M
s5 Card Acceptor State /Province or Region M • M
Code


s6 Card Acceptor Country Code M • M
48 Additional Data M X M
p0002 Product Identifier • X M
p0020 Issuer Currency Conversion Rate (ICCR) • X C
Effective Date
p0021 Issuer Currency Conversion Rate (ICCR) • X C
Percentage
p0022 Recurring Payment Indicator C • C
p0023 Terminal Type C • C
p0025 Message Reversal Indicator C • C
s1 Message Reversal Indicator C • C
s2 Central Site Processing Date of Original C • C
Message
p0043 Program Registration ID C • C
p0052 Electronic Commerce Security Level Indicator C • C
s1 Security Protocol C • C
s2 Cardholder Authentication C • C
s3 UCAF Collection Indicator C • C
p0146 Amounts, Transaction Fee C X C
This PDS may contain from 1–12 occurrences
of transaction fee data. Each occurrence has
the following seven subfields:
s1 Fee Type Code C X C
s2 Fee Processing Code C X C
s3 Fee Settlement Indicator C X C
s4 Currency Code, Fee C X C
s5 Amount, Fee C X C
s6 Currency Code, Fee, Reconciliation C X C
s7 Amount, Fee, Reconciliation C X C


p0148 Currency Exponents M X M
This PDS may contain 1–15 occurrences of
exponent data. Each occurrence has the
following two subfields:
s1 Currency Code M X M
s2 Currency Exponent M X M
p0149 Currency Codes, Amounts, Original C • C
s1 Currency Code, Original Transaction C • C
Amount
s2 Currency Code, Original Reconciliation C • C
Amount
p0158 Business Activity C X M
s1 Card Program Identifier C X M
s2 Business Service Level Code C X M
s3 Business Service ID Code C X M
s4 Interchange Rate Designator C • M
s5 Business Date • X M
s6 Business Cycle • X M
s7 Card Acceptor Business Code (MCC) • X M
Override Indicator
s8 Product Override Indicator • X M
s9 Corporate Incentive Rates Apply Indicator • X M
s10 ATM Late Presentment Indicator • X M
p0159 Settlement Data 1 • X C
s1 Settlement Service Transfer Agent ID Code • X C
s2 Settlement Service Transfer Agent Account • X C
s3 Settlement Service Level Code • X C
s4 Settlement Service ID Code • X C
s5 Settlement Foreign Exchange Rate Class • X C
Code
s6 Reconciliation Date • X C
s7 Reconciliation Cycle • X C


s8 Settlement Date • X C
s9 Settlement Cycle • X C
s5 Settlement Foreign Exchange Rate Class • X C
Code
p0165 Settlement Indicator M • M
s1 Settlement Indicator M • M
s2 Settlement Information O • C
p0170 Card Acceptor Inquiry Information O • C
s1 Customer Service Phone Number O • C
s2 Card Acceptor Phone Number O • C
s3 Additional Contact Information O • C
p0171 Alternate Card Acceptor Description O • C
s1 Character Set Indicator O • C
s2 Card Acceptor Description Data O • C
p0172 Sole Proprietor Name O • C
p0173 Legal Corporate Name O • C
p0174 Dun & Bradstreet Number O • C
p0175 Card Acceptor URL O • C
p0189 Point-of-Interaction (POI) Phone Data O • C
s1 Format Number O • C
s2 Phone Data O • C


p0190 Partner ID Code O • C
p0191 Originating Message Format O X M
p0261 Risk Management Approval Code C X C
p0375 Member Reconciliation Indicator 1 O • •
p10XX Member-to-Member Proprietary Data (p1000 O • C
through p1099)
49 Currency Code, Transaction M • M
50 Currency Code, Reconciliation C X C
51 Currency Code, Cardholder Billing C X C
55 Integrated Circuit Card (ICC) System Related O • C
Data
62 Additional Data 2 C X C
63 Transaction Life Cycle ID C • C
s1 Life Cycle Support Indicator C • C
s2 Trace ID C • C
s3 Validation Code C • C
s4 Life Cycle Transaction Sequence Number O • C
s5 Life Cycle Transaction Total O • C
71 Message Number M X M
93 Transaction Destination Institution ID Code C X M
94 Transaction Originator Institution ID Code M • M
100 Receiving Institution ID Code • X M

Financial Detail Addendum (Passenger Transport Detail—General Ticket Information)/1644

At least one occurrence of this addendum message must be provided if the
associated First Presentment/1240 message contains an airline Card Acceptor
Business Code (MCC) or a Passenger Railway MCC and is submitted for one of
the following U.S. region incentive interchange rate programs:
IRD Incentive Interchange Rate Program

69 Corporate T&E Rate II
70 or 80 Merit III
76 or 86 Corporate T&E Rate I
78, 88, or 98 Merit I
89 Corporate T&E Rate III
93 Passenger Transport
96 World MasterCard T&E
This addendum message may only be provided if the associated First

Presentment/1240 contains an airline or railway MCC in DE 26, Card Acceptor
Business Code.
The clearing system will always reject this Financial Detail Addendum/1644
message if it contains invalid data. The associated First Presentment/1240
message also will be rejected if it is submitted for a U.S. region or international
interchange program, unless it is a Credit (DE 3, subfield 1 contains “20”), a
Reversal (PDS 0025, subfield 1 contains “R”), a Collection Only transaction
(PDS 0165, subfield 1 contains “C”), or a transaction submitted for a
MasterCard-defined Standard interchange program (U.S. and international
IRDs 61, 63, 65, 75, 85, or 95).
For information about the individual PDS requirements for this addendum and
for the specific incentive interchange programs listed above, please refer to
chapter 9 of this manual, or chapter 7 of the GCMS Reference Manual.


Message Layout
p0501 Transaction Description M • M
s1 Usage Code M • M
s2 Industry Record Number M • M
s3 Occurrence Indicator M • M
s4 Message Number M • M
p0505 Passenger Name C • C
p0506 Ticket Number C • C
p0507 Issuing Carrier C • C
p0508 Customer Code C • C
p0509 Issue Date O • C
p0510 Travel Agency Code O • C
p0511 Travel Agency Name O • C
p0512 Total Fare C • C
p0513 Total Fees O • C
p0514 Total Taxes O • C
p0597 Total Tax Amount O • C
s1 Total Tax Amount O • C
s2 Total Tax Amount Exponent O • C
s3 Total Tax Amount Sign O • C
p0598 Total Tax Collected Indicator O • C


Message Layout
p0679 Commodity Code O • C
p0682 Detail Tax Amount 1 O • C
s1 Detail Tax Amount Indicator 1 O • C
s2 Detail Tax Amount 1 O • C
s3 Detail Tax Rate 1 O • C
s4 Detail Tax Rate Exponent 1 O • C
s5 Detail Tax Type Applied 1 O • C
s6 Detail Tax Type Identifier 1 O • C
s7 Card Acceptor Tax ID 1 O • C
s8 Detail Tax Amount Sign 1 O • C


Message Layout
p0686 Tax Exempt Indicator O • C
p0713 Restricted Ticket Indicator O • C
p0714 Exchange Ticket Amount O • C
p0715 Exchange Fee Amount O • C
p0716 Travel Authorization Code O • C
p0717 IATA Client Code O • C


Message Layout
p10XX Member-to-Member Proprietary Data O • C
(p1000 through p1099)
s2 Trace ID C • C
s4 Life Cycle Transaction Sequence O • C
Number
93 Transaction Destination Institution ID Code • X M

Financial Detail Addendum (Passenger Transport Detail—Trip Leg Data)/1644

Trip Leg Data)/1644
associated First Presentment/1240 contains an airline card acceptor business
code (MCC) or a Passenger Railway MCC and is submitted for one of the
following U.S. region incentive interchange rate programs:
IRD Incentive Interchange Rate Program

70 or 80 Merit III

Presentment/1240 contains an airline or railway MCC in DE 26 Card Acceptor
Business Code.
IRDs 61, 63, 65, 75, 85, or 95).
chapter 9 of this manual or chapter 7 of the GCMS Reference Manual.

Financial Detail Addendum (Passenger Transport Detail—Trip Leg Data)/1644 Message Layout
p0520 Travel Date C • C
p0521 Carrier Code C • C
p0522 Service Class Code C • C
p0523 City of Origin/Airport Code C • C
p0524 City of Destination/Airport Code C • C
p0525 Stop Over Code C • C
p0526 Conjunction Ticket O • C
p0527 Exchange Ticket O • C
p0528 Coupon Number O • C
p0529 Fare Basis Code C • C
p0530 Flight Number C • C
p0531 Departure Time C • C
s1 Departure Time C • C
s2 Departure Time Segment C • C
p0533 Arrival Time O • C
s1 Arrival Time O • C
s2 Arrival Time Segment O • C

p0535 Fare O • C
p0536 Fee O • C
p0537 Taxes O • C
p0538 Endorsements/Restrictions O • C


s2 Trace ID C • C


associated First Presentment/1240 contains a Vehicle Rental card acceptor
business code (MCC) and is submitted for one of the following U.S. region
incentive interchange rate programs:
IRD Incentive Interchange Rate Programs

97 Travel Industries Premier Service

Presentment/1240 contains a vehicle MCC in Card Acceptor Business Code
(DE 26).
IRDs 61, 63, 65, 75, 85, or 95).
Financial Detail Addendum (Vehicle Rental Detail)/1644 Message Layout



p0544 Rental Agreement Number C • C
p0545 Renter Name C • C
p0546 Rental Return City C • C
p0547 Rental Return State/Province C • C
p0548 Rental Return Country C • C
p0549 Rental Return Location ID C • C
p0550 Rental Return Date C • C
p0551 Rental Checkout Date C • C
p0552 Customer Service Toll-Free (800) Number C • C
p0553 Rental Rate C • C
s1 Rental Rate Indicator C • C
s2 Rental Rate C • C
p0555 Rate per Mile (or Per Kilometer) O • C
p0556 Total Miles (or Kilometers) O • C
p0557 Maximum Free Miles (or Kilometers) O • C
p0558 Miles/Kilometer Indicator O • C
p0559 Vehicle Insurance O • C
s1 Insurance Indicator O • C
s2 Insurance Charges O • C
p0561 Adjusted Amount O • C
s1 Adjusted Amount Indicator O • C
s2 Adjusted Amount O • C


p0563 Program Code O • C
p0564 Rental Location City C • C
p0565 Rental Location State/Province C • C
p0566 Rental Location Country C • C
p0567 Rental Location ID O • C
p0568 Rental Class ID C • C


p0686 Tax Exempt Indicator C • C
p0689 Corporate Identifier O • C
p0690 No Show Indicator O • C
p0691 Days Rented C • C
p0692 Weekly Rental Amount O • C
p0693 Total Authorized Amount O • C
s1 Total Authorized Amount O • C
s2 Total Authorized Amount Exponent O • C
s3 Total Authorized Amount Sign O • C
p0694 One Way Drop Off Charge O • C
p0695 Regular Mileage Charge O • C
p0696 Extra Mileage Charge O • C
p0697 Late Charge O • C
p0698 Fuel Charge O • C
p0700 Towing Charges O • C
p0701 Extra Charges O • C
p0702 Other Charges O • C




p10XX Member-to-Member Proprietary Data (p1000 O • C
through p1099)
s2 Trace ID C • C


This message must be provided if the associated First Presentment/1240
contains a valid Lodging card acceptor business code (MCC) and is submitted
for one of the following U.S. region incentive interchange rate programs:


Presentment/1240 contains a lodging MCC in DE 26 Card Acceptor Business
Code.
The clearing system will always reject a Financial Detail Addendum (Lodging
Summary)/1644 message if it contains invalid data. The associated First
Presentment/1240 message also will be rejected if it is submitted for a U.S.
region or international interchange program, unless it is a Credit (DE 3,
subfield 1 contains “20”), a Reversal (PDS 0025, subfield 1 contains “R”), a
Collection Only transaction (PDS 0165, subfield 1 contains “C”), or a
transaction submitted for a MasterCard-defined Standard interchange program
(U.S. and international IRDs 61, 63, 65, 75, 85, or 95).
Whenever the Financial Detail Addendum (Lodging Summary)/1644 message is

present, and the transaction involves one of the MasterCard Corporate Cards,
the following addendum messages may optionally be provided:
• Corporate Card Common Data Requirement, usage code 98, industry
record number 000, and
• Corporate Card Line Item Detail, usage code 98, industry record number
950.

Financial Detail Addendum (Lodging Summary)/1644 Message Layout

p0521 Carrier Code O • C
p0530 Flight Number O • C
p0532 Total Charges O • C
s1 Total Charges Amount O • C
s2 Total Charges Exponent O • C
s3 Total Charges Sign O • C
p0534 Total Non–Room Charges O • C
s1 Total Non–Room Charges Amount O • C
s2 Total Non–Room Charges Exponent O • C
s3 Total Non–Room Charges Sign O • C


p0539 Total Amount Charged on Credit Card O • C
s1 Total Amount Charged on Credit Card Amount O • C
s2 Total Amount Charged on Credit Card O • C
Exponent
s3 Total Amount Charged on Credit Card Sign O • C
p0540 Room Service Charges O • C
s1 Room Service Charges Amount O • C
s2 Room Service Charges Exponent O • C
s3 Room Service Charges Sign O • C
p0541 Lounge/Bar Charges O • C
s1 Lounge/Bar Charges Amount O • C
s2 Lounge/Bar Charges Exponent O • C
s3 Lounge/Bar Charges Sign O • C
p0542 Transportation Charges O • C
s1 Transportation Charges Amount O • C
s2 Transportation Charges Exponent O • C
s3 Transportation Charges Sign O • C
p0543 Gratuity Charges O • C
s1 Gratuity Charges Amount O • C
s2 Gratuity Charges Exponent O • C
s3 Gratuity Charges Sign O • C
p0552 Customer Service Toll-Free (800) Number C • C
p0554 Conference Room Charges O • C
s1 Conference Room Charges Amount O • C
s2 Conference Room Charges Exponent O • C
s3 Conference Room Charges Sign O • C
p0560 Audio Visual Charges O • C
s1 Audio Visual Charges Amount O • C
s2 Audio Visual Charges Exponent O • C
s3 Audio Visual Charges Sign O • C


p0562 Banquet Charges O • C
s1 Banquet Charges Amount O • C
s2 Banquet Charges Exponent O • C
s3 Banquet Charges Sign O • C
p0569 Internet Access Charges O • C
s1 Internet Access Charges Amount O • C
s2 Internet Access Charges Exponent O • C
s3 Internet Access Charges Sign O • C
p0570 Early Departure Charges O • C
s1 Early Departure Charges Amount O • C
s2 Early Departure Charges Exponent O • C
s3 Early Departure Charges Sign O • C
p0571 Guest Name O • O
p0572 Guest Number O • C
p0574 Arrival Date C • C
p0575 Departure Date C • C
p0576 Folio Number C • C
p0577 Property Phone Number C • C
p0578 Billing Adjustment O • C
s1 Billing Adjustment Indicator O • C
s2 Billing Adjustment Amount O • C
s3 Billing Adjustment Exponent O • C
s4 Billing Adjustment Sign O • C
p0580 Room Rate C • C
s1 Room Rate Amount C • C
s2 Room Rate Exponent C • C


p0581 Total Room Tax C • C
s1 Total Room Tax Amount C • C
s2 Total Room Tax Exponent C • C
s3 Total Room Tax Sign C • C
p0582 Program Code O • C
p0583 Phone Charges O • C
s1 Phone Charges Amount O • C
s2 Phone Charges Exponent O • C
s3 Phone Charges Sign O • C
p0584 Restaurant Charges O • C
s1 Restaurant Charges Amount O • C
s2 Restaurant Charges Exponent O • C
s3 Restaurant Charges Sign O • C
p0585 Mini-Bar Charges O • C
s1 Mini-Bar Charges Amount O • C
s2 Mini-Bar Charges Exponent O • C
s3 Mini-Bar Charges Sign O • C
p0586 Gift Shop Charges O • C
s1 Gift Shop Charges Amount O • C
s2 Gift Shop Charges Exponent O • C
s3 Gift Shop Charges Sign O • C
p0587 Laundry and Dry Cleaning Charges O • C
s1 Laundry and Dry Cleaning Charges Amount O • C
s2 Laundry & Dry Cleaning Charges Exponent O • C
s3 Laundry & Dry Cleaning Charges Sign O • C
p0588 Other Services O • C
s1 Other Services Code O • C
s2 Other Services Amount O • C
s3 Other Services Exponent O • C
s4 Other Services Sign O • C




p0690 No Show Indicator O • C
p0693 Total Authorized Amount O • C
p0703 Total Room Nights C • C
p0704 Prepaid Expenses O • C
s1 Prepaid Expenses Amount O • C
s2 Prepaid Expenses Amount Exponent O • C
s3 Prepaid Expenses Amount Sign O • C
p0705 Total Non-Room Tax Amount O • C
s1 Non-Room Tax Amount O • C
s2 Non-Room Tax Exponent O • C
s3 Non-Room Tax Sign O • C
p0706 Cash Advances O • C
s1 Cash Advances Amount O • C
s2 Cash Advances Exponent O • C
s3 Cash Advances Sign O • C
p0707 Valet Charges O • C
s1 Valet Charges Amount O • C
s2 Valet Charges Exponent O • C
s3 Valet Charges Sign O • C


p0708 Movie Charges O • C
s1 Movie Charges Amount O • C
s2 Movie Charges Exponent O • C
s3 Movie Charges Sign O • C
p0709 Business Center Charges O • C
s1 Business Center Charges Amount O • C
s2 Business Center Charges Exponent O • C
s3 Business Center Charges Sign O • C
p0710 Health Club Charges O • C
s1 Health Club Charges Amount O • C
s2 Health Club Charges Exponent O • C
s3 Health Club Charges Sign O • C
p0711 Fire Safety Act Indicator C • C


s2 Trace ID C • C


The Financial Detail Addendum (Temporary Services Detail)/1644 message is
an optional addendum that may be submitted with any First Presentment/1240
message. It provides detailed information regarding the billing for services
rendered on a temporary or contract basis. The message layout provides
information such as the employee job performed, timekeeping, and billing
rates.
IRDs 61, 63, 65, 75, 85, or 95).
Financial Detail Addendum (Temporary Services)/1644 Message Layout

p0508 Customer Code O • C




p0718 Employee/Temp Name/ID O • C
p0719 Employee Social Security Number or ID O • C
p0720 Job Description O • C
p0721 Job Code O • C
p0722 Flat Rate Indicator O • C
p0723 Regular Hours Worked O • C
s1 Regular Hours Worked O • C
s2 Regular Hours Worked Exponent O • C
p0724 Regular Hours Rate O • C
s1 Regular Hours Rate O • C
s2 Regular Hours Rate Exponent O • C
p0725 Overtime Hours Worked O • C
s1 Overtime Hours Worked O • C
s2 Overtime Hours Worked Exponent O • C
p0726 Overtime Hours Rate O • C
s1 Overtime Hours Rate O • C
s2 Overtime Hours Rate Exponent O • C
p0727 Temp Start Date O • C
p0728 Temp Week Ending O • C
p0729 Requestor Name or ID O • C
p0730 Supervisor/Reports To O • C
p0731 Time Sheet Number O • C


p0732 Discount Amount O • C
s1 Discount Amount O • C
s2 Discount Amount Exponent O • C
s3 Discount Amount Sign O • C
s4 Discount Type O • C
p0733 Subtotal Amount O • C
s1 Subtotal Amount O • C
s2 Subtotal Amount Exponent O • C
s3 Subtotal Amount Sign O • C
p0734 Miscellaneous Expenses O • C
s1 Miscellaneous Expense Description O • C
s2 Miscellaneous Expense Amount O • C
s3 Miscellaneous Expense Exponent O • C
s4 Miscellaneous Expense Sign O • C


s2 Trace ID C • C



Financial Detail Addendum (Shipping/Courier

Services)/1644
The Financial Detail Addendum (Shipping/Courier Services)/1644 message is
an optional addendum that may be submitted with any First Presentment/1240
message. It provides detailed information regarding delivery or courier
services. The message layout supports the shipping and delivery tracking
information.
MasterCard-defined Standard interchange program (U.S. and international IRDs
61, 63, 65, 75, 85, or 95).
Financial Detail Addendum (Shipping/Courier Services)/1644 Message Layout





p0734 Miscellaneous Expenses O • C
s4 Miscellaneous Expense Sign O • C
p0735 Service Descriptor Code O • C
p0736 Tracking Number or Pickup Number O • C
p0737 Shipping Net Amount O • C
s1 Shipping Net Amount O • C
s2 Shipping Net Amount Exponent O • C
s3 Shipping Net Amount Sign O • C
p0738 Incentive Amount O • C
s1 Incentive Amount O • C
s2 Incentive Amount Exponent O • C
s3 Incentive Net Amount Sign O • C
p0739 Pickup Date O • C
p0740 Delivery Date O • C
p0741 Number of Packages O • C
p0742 Package Weight O • C
p0743 Unit of Measure O • C
p0744 Shipping Party Information O • C
s1 Shipping Party Name O • C
p0745 Shipping Party Address O • C
s1 Shipping Party Address O • C


p0746 Shipping Party Postal Information O • C
s1 Shipping Party City O • C
s2 Shipping Party State/Province Code O • C
s3 Shipping Party Country Code O • C
s4 Shipping Party Postal Code O • C
p0747 Shipping Party Contact O • C
s1 Shipping Party Descriptor O • C
s2 Shipping Party Contact Information O • C
p0748 Delivery Party Information O • C
s1 Delivery Party Name O • C
p0749 Delivery Party Address Information O • C
s1 Delivery Party Address O • C
p0750 Delivery Party Postal Information O • C
s1 Delivery Party City O • C
s2 Delivery Party State/Province Code O • C
s3 Delivery Party Country Code O • C
s4 Delivery Party Postal Code O • C


p0754 Delivery Party Contact O • C
s1 Delivery Party Descriptor O • C
s2 Delivery Party Contact Information O • C
s2 Trace ID C • C



Financial Detail Addendum (Payment Transaction

Detail)/1644
This addendum message can optionally be submitted with First
Presentment/1240 messages for Payment Transactions. The Payment
Transaction Detail addendum provides the issuer and cardholder with
enhanced data about the card acceptor, recipient of funds, and other
transaction details.
Reversal (PDS0025, subfield 1 contains “R”), a Collection Only transaction
(PDS0165, subfield 1 contains “C”), or a transaction submitted for a
IRDs 61, 63, 65, 75, 85, or 95).
Financial Detail Addendum (Payment Transaction Detail)/1644 Message Layout

Message Type Identifier M • M
p0670 Payer Name or User ID O • C
p0671 Date of Funds Requested O • C

Financial Detail Addendum (Payment Transaction Detail)/1644 Message Layout

p0672 Recipient Name (Seller) O • C
p0673 Date of Anticipated Receipt of Funds O • C
p0674 Additional Trace/Reference Number Used by O • C
Card Acceptor
p0675 Additional Transaction Description Data O • C
s2 Trace ID C • C

Financial Detail Addendum (Telephony Billing Service)/1644
Financial Detail Addendum (Telephony Billing

Service)/1644
This addendum message is designed to carry telephony billing data and allow
issuers the opportunity to supply more transaction information to their
consumer and corporate clients. This addendum message is intended to
encourage companies to pay for telephony services using a MasterCard
Corporate Purchasing Card®. The enhanced data in this addendum will
provide information normally received on monthly statements generated by the
service provider.
Telephony services include corporate conference call provider services and

usage as well as corporate mobile phone usage.
There can be a combined total of 999 occurrences of the two Telephony

Billing addendum messages for an associated First Presentment/1240 message.
The two Telephony Billing addendum messages are:

• Telephony Billing—Summary (one occurrence permitted; Occurrence
Indicator PDS 0501, subfield 3 is 001). Contains summary billing
information about the telephone customer and billing totals.
• Telephony Billing—Detail (1 to 998 occurrences permitted; Occurrence
Indicator, PDS 0501, subfield 3) is variable. If a Telephony Billing—Detail
addendum is present, the occurrence value may be 002–999). Contains
specific information about each telephone call. The Telephony Billing—
Detail is optional. If one or more Telephony Billing—Detail addendum
messages are present, they must follow the Telephony Billing—Summary
message.
GCMS will reject both Financial Detail Addendum (Telephony Billing—

Summary and Telephony Billing—Detail)/1644 messages submitted with a First
Presentment/1240 message for an incentive interchange rate program if either
addendum contains invalid data. The associated First Presentment/1240
message also will be rejected unless it was submitted with a Processing Code
(DE]3, subfield 1) value of 20 (Credit), as a Reversal (PDS 0025, subfield 1
contains “R”), or as a Collection Only transaction (PDS 0165, subfield 1
contains “C”).


Addendum Messages
Following are the rules for using the new Telephony Billing addendum
messages:
1. The Financial Detail Addendum (Telephony Billing—Summary)/1644 and
Financial Detail Addendum (Telephony Billing—Detail)/1644 messages
may optionally accompany any First Presentment/1240 message,
although they are intended for use in corporate transactions.
2. If one occurrence of the Financial Detail Addendum (Telephony
Billing—Summary)/1644 message is provided, then the following
messages also may optionally be provided.
− One or more occurrences of the Financial Detail Addendum
(Telephony Billing—Detail)/1644 message.
− The Financial Detail Addendum (Corporate Card Common Data
Requirements)/1644 message (in transactions involving a MasterCard
Corporate Card).
− One or more occurrences of the Financial Detail Addendum (Generic
Detail)/1644 message.
− One or more occurrences of the Financial Detail Addendum (Corporate
Card Line Item Detail)/1644 messages.
− Other industry-specific Financial Detail Addendum/1644 messages (if
they are appropriate for the transaction, such as Lodging Summary,
Vehicle Rental, Passenger Transport, Temporary Services, and
Shipping/Courier Services).

The table below provides the layout for the Financial Detail Addendum
(Telephony Billing—Summary)/1644 message. Shading indicates functionality
that will be available in a future release.
Financial Detail Addendum (Telephony Billing—Summary) /1644 Message Layout

No. Data Element Org Sys Dst
_ Message Type Identifier M • M
_ Bit Map Primary M X M
1 Bit Map Secondary M X M
32 Acquiring Institution Id O • C
s4 Associated First Presentment Message M • M
Number
p0619 User Name O • C
p0624 User Account Number O • C
p0625 User Telephone Number O • C
p0626 Billing Statement Period O • C
s1 Statement Start Date O • C
s2 Statement End Date O • C


p0627 Billing Event 1 O • C
s1 Billing Event Amount 1 O • C
s2 Billing Event Exponent 1 O • C
s3 Billing Event Sign 1 O • C
s4 Billing Event Description 1 O • C
p0628 Billing Event 2 O • C





p0755 Line Item Total Amount O • C
s1 Line Item Total Amount O • C
s2 Line Item Total Exponent O • C
s3 Line Item Total Amount Sign O • C
p10XX Member to Member Proprietary Data O • C

s2 Trace ID C • C


Billing—Detail)/1644 Message
The Telephony Billing—Detail addendum contains the call detail information
that is summarized in the Telephony Billing—Summary addendum message.
The Telephony Billing—Detail addendum message is optional and if sent must
follow the Telephony Billing—Summary addendum.
(Telephony Billing—Detail)/1644 message. Shading indicates functionality that
will be available in a future release.
Financial Detail Addendum (Telephony Billing—Detail) /1644 Message

PDS Data Element Org Sys Dst
s4 Associated First Presentment Message M • M
Number
p0636 Call Date O • C
p0637 Call Time O • C


p0638 Call To Information O • C
s1 Call To City O • C
s2 Call To State/Province O • C
s3 Call To Country O • C
s4 Call To Number O • C
s5 Call To Type O • C
p0639 Call Duration O • C
p0640 Call Time Period O • C
p0644 Call From Information O • C
s1 Call From City O • C
s2 Call From State/Province O • C
s3 Call From Country O • C
s4 Call From Number O • C
p0649 Call Usage Amount O • C
s1 Call Usage Amount O • C
s2 Call Usage Amount Exponent O • C
s3 Call Usage Amount Sign O • C
p0655 Call Long Distance Amount O • C
s1 Call Long Distance Amount O • C
s2 Call Long Distance Amount Exponent O • C
s3 Call Long Distance Amount Sign O • C
p0658 Call Connect Amount O • C
s1 Call Connect Amount O • C
s2 Call Connect Amount Exponent O • C
s3 Call Connect Amount Sign O • C
p0659 Other Description O • C




p0734 Miscellaneous Expense O • C
s4 Miscellaneous Expense Amount Sign O • C


p10XX Member to Member Proprietary Data (p1000 O • C

through p1099)
s2 Trace ID C • C


These addendum messages are designed to carry electronic invoice data that is
not present in other addendum messages, and to allow issuers to supply more
transaction information to their corporate clients. These new addendum
messages provide additional information passed between buyer and seller in
business-to-business (“B2B”) and electronic-business-to-business (“eB2B”)
transactions.
The new electronic invoice addendum messages are:

• Electronic Invoice—Transaction Data (multiple occurrences permitted)
• Electronic Invoice—Party Information (one to six occurrences permitted)
There can be a combined total of 999 occurrences of the two electronic

invoice addendum messages.
Following is general information about the new optional Financial Detail

Addendum (Electronic Invoice—Transaction Data and Electronic Invoice—
Party Information)/1644 messages:
• The new electronic invoice information is contained in two addendum
messages.
• The electronic invoice addendum messages must be sent with the Financial
Detail Addendum (Corporate Card Common Data Requirements)/1644
message to provide the tax information needed to comply with the various
tax reporting laws that exist in the global marketplace.
• The Financial Detail Addendum (Corporate Line Item Detail)/1644 message
may optionally be sent.
• Two addendum messages contain electronic invoice data.
− The Electronic Invoice—Transaction Data addendum message contains
detail about the items listed in the invoice. The Electronic Invoice—
Transaction Data addendum must precede the Electronic Invoice—
Party Information.
− The Electronic Invoice—Party Information addendum message contains
information about the buyer, the supplier, the invoice recipient, the
payee, the delivery party, and the “ship from” party. A minimum of
one occurrence of the Electronic Invoice—Party Information addendum
message must be present when the Electronic Invoice—Transaction
Data addendum message is present.

• There can be a combined total of 999 occurrences of the two Electronic

Invoice messages:
− The number of occurrences (provided in Occurrence Indicator
[PDS 0501, subfield 3]) of the Electronic Invoice—Transaction Data
addendum is variable.
− The number of occurrences (provided in Occurrence Indicator
[PDS 0501, subfield 3]) of the Electronic Invoice—Party Information
addendum is also variable. Electronic Invoice—Party Information
addendum must have a minimum occurrence of one and can have a
maximum occurrence of six.
− Each successive Occurrence Indicator (Occurrence Indicator [PDS 0501,
subfield 3]) with the same usage code must be greater than the
previous occurrence indicator. No edits are defined to validate the
value in Occurrence Indicator because both the Electronic Invoice—
Transaction Data addendum and the Electronic Invoice—Party
Information addendum may have variable occurrences.
• GCMS will reject both Financial Detail Addendum (Electronic Invoice—
Transaction Data and Electronic Invoice—Party Information)/1644
messages, and any other addendum messages, submitted with a First
Presentment/1240 message for an incentive interchange rate program if any
of the addenda contain invalid data. The associated First Presentment/1240
message also will be rejected unless it was submitted with a Processing
Code (DE 3, subfield 1) of 20 (Credit), as a Reversal (PDS 0025, subfield 1
contains “R”), or as a Collection Only transaction (PDS 0165, subfield 1
contains “C”).

Use of the Electronic Invoice Addendum Messages with Other

Addendum Messages
Following are the rules for using the new electronic invoice addendum
messages:
• The Financial Detail Addendum (Electronic Invoice—Transaction
Data)/1644 and Financial Detail Addendum (Electronic Invoice—Party
Information)/1644 messages optionally may accompany any First
Presentment/1240 message submitted with a MasterCard Corporate Card.
• If one or more occurrences of the Financial Detail Addendum (Electronic
Invoice—Transaction Data)/1644 message is provided, then:
− At least one occurrence of the Financial Detail Addendum (Electronic
Invoice—Party Information)/1644 message also must be provided, and
must follow the Electronic Invoice—Transaction Data addendum
messages.
− The Financial Detail Addendum (Corporate Card Common Data
Requirements)/1644 message also must be provided.
− One or more occurrences of the Financial Detail Addendum (Corporate
Card Line Item Detail)/1644 message optionally may be provided.
− One or more occurrences of the Financial Detail Addendum (Generic
Detail)/1644 message optionally may be provided.
− Other industry-specific Financial Detail Addendum/1644 messages may
be provided if they are appropriate for the transaction, such as Lodging
Summary, Vehicle Rental, Passenger Transport, Temporary Services,
and Shipping/Courier Services.

(Electronic Invoice—Transaction Data)/1644 message. Shading indicates
functionality that will be available in a future release.
Financial Detail Addendum (Electronic Invoice—Transaction Data)/1644 Message Layout

No. Description Org Sys Dst
32 Acquiring Institution ID O • C
p0573 Invoice Number O • C
p0579 Invoice Date O • C
p0589 Invoice Creation Date and Time O • C
s1 Invoice Creation Date O • C
s2 Invoice Creation Time O • C
p0604 Transaction Supplemental Data 1 O • C
s1 Transaction Supplemental Data O • C
Description 1
s2 Transaction Supplemental Data 1 O • C
s3 Transaction Supplemental Data Code 1 O • C


p0605 Transaction Supplemental Data 2 O • C
s1 Transaction Supplemental Data O • C
Description 2
through p1099)
s2 Trace ID C • C


Invoice—Party Information)/1644 Message
The Electronic Invoice—Party Information addendum provides information
about each entity, or party, involved in the transaction. PDS 0590 Party
Identification indicates the entity to which the information in the addendum
applies. There is a minimum of one occurrence and a maximum of six
occurrences of Electronic Invoice—Party Information. There is no specific
sequence in which the party information should be presented.
(Electronic Invoice—Party Information)/1644 message. Shading indicates
functionality that will be available in a future release.

p0590 Party Identification O • C
p0591 Party Name O • C


p0592 Party Address O • C
s1 Party Address Line O • C
p0593 Party Postal Information O • C
s1 City O • C
s2 State/Province Code O • C
s3 Country Code O • C
s4 Postal Code O • C
p0594 Party Contact O • C
s1 Party Contact Descriptor O • C
s2 Party Contact Information O • C
p0601 Party Nature of Filing O • C
p0602 Party Supplemental Data 1 O • C
s1 Party Supplemental Data Description 1 O • C
s2 Party Supplemental Data 1 O • C
s3 Party Supplemental Data Code 1 O • C
p0603 Party Supplemental Data 2 O • C
through p1099)
s2 Trace ID C • C



Financial Detail Addendum (Corporate Card Common Data Requirements)/1644

Requirements)/1644
This addendum message must be provided if the associated First
Presentment/1240 message is for a transaction that was:
• Completed with one of the MasterCard corporate cards except for
MasterCard Corporate Fleet Card transactions at fuel locations, and
• Submitted for one of the following incentive interchange rate programs:

60 U.S. region Corporate Face-to-Face
62 U.S. region Corporate Large Ticket
66 U.S. region Corporate Data Rate III
67 U.S. region Corporate Data Rate II
67 International Corporate Purchasing Data Rate II (except for MasterCard
Corporate Fleet Card transactions at fuel locations)
This addendum message may optionally be provided with the following

transactions:
• The associated First Presentment/1240 message is for a transaction that was
completed with a MasterCard Corporate Fleet Card at a fuel location.
• Any First Presentment/1240 transaction that was completed with one of the
MasterCard Corporate Cards.
• This addendum may optionally be provided when a Financial Detail/1240
message involves a Corporate Card and includes the Financial Detail
Addendum (Lodging Summary)/1644 message.

Presentment/1240 is for a transaction that was completed with one of the
MasterCard Corporate cards.
interchange program, unless it is a Credit (DE 3, subfield 1 contains “20“), a
(PDS 0165, subfield 1 contains “C“), or a transaction submitted for a
IRDs 61, 63, 65, 75, 85, or 95).

Financial Detail Addendum (Corporate Card Common Data Requirements)/1644 Message Layout
S2 Industry Record Number M • M
p0508 Customer Code C • C
p0515 Additional Card Acceptor Information O • C
p0516 Austin-Tetra Number O • C
p0517 NAICS Code O • C
p0595 Card Acceptor Type C • C
s1 Business Type C • C
s2 Business Owner Type C • C
s3 Business Certification Type C • C
s4 Business Racial/Ethnic Type C • C
s5 Business Type Provided C • C
s6 Business Owner Type Provided Code C • C
s7 Business Certification Type Provided Code C • C
s8 Business Racial/Ethnic Type Provided Code C • C

p0596 Card Acceptor Tax ID C • C
s1 Card Acceptor Tax ID C • C
s2 Card Acceptor Tax ID Provided Code C • C
p0597 Tax Amount C • C
s1 Total Tax Amount C • C
s2 Total Tax Exponent C • C
s3 Total Tax Sign C • C
p0598 Tax Collected Indicator O • C
p0599 Corporation VAT Number O • C
p0600 Card Acceptor Reference Number O • C
p0606 Freight Amount O • C
s1 Freight Amount O • C
s2 Freight Amount Exponent O • C
s3 Freight Amount Sign O • C
p0607 Duty Amount O • C
s1 Duty Amount O • C
s2 Duty Amount Exponent O • C
s3 Duty Amount Sign O • C
p0608 Destination Postal Code O • C
p0609 Destination State/Province Code O • C
p0610 Destination Country Code O • C
p0613 Ship-From Postal Code O • C
p0614 Order Date O • C
p0676 Card Acceptor VAT Number O • C
p0677 Customer VAT Number O • C
p0678 Unique Invoice Number O • C
p0680 Authorized Contact Name O • C
p0681 Authorized Contact Phone O • C


p0732 Discount Amount O • C

s2 Trace ID C • C

Financial Detail Addendum (Corporate Fleet Transaction Information)/1644

Information)/1644
This message must be provided if the associated First Presentment/1240
message is a MasterCard Corporate Fleet Card® transaction at a fuel location
and it is submitted for the following incentive interchange rate programs:

68 U.S. region Corporate Data Rate I

Presentment/1240 message is for a transaction that was completed with a
MasterCard Corporate Fleet Card at a fuel location.
IRDs 61, 63, 65, 75, 85, or 95).
for specific incentive interchange programs listed above, please refer to
chapter 9 of this manual, or chapter 7 of the GCMS Reference Manual.
Financial Detail Addendum (Corporate Fleet Transaction Information)/1644 Message Layout



p0519 Additional Fuel Location Information O • C
s1 Hours of Operation/24 Hours Available O • C
s2 18 Wheeler Access Available O • C
s3 Diesel Site Available O • C
s4 Interstate Access/Exit Number With Directions O • C
Available
s5 Convenience Store Available O • C
s6 Truck Stop Restaurant Available O • C
s7 Truck Stop Hotel Available O • C
s8 Truck Stop With Showers Available O • C
s9 Vehicle Maintenance/Repair Bays Available O • C
s10 Car Wash Available O • C
s11 Aviation Location Available O • C
s12 Marina Locations Available O • C
s13 Alternative Fuel Locations Available O • C
s14 Pay-At-Pump Available O • C
s2 Total Tax Exponent O • C
s3 Total Tax Sign O • C
p0620 Oil Company Brand Name C • C
p0621 Purchase Time C • C
p0622 Motor Fuel Service Type O • C


p0623 Motor Fuel Information C • C
s1 Motor Fuel Product Code C • C
s2 Motor Fuel Unit Price C • C
s3 Motor Fuel Unit of Measure C • C
s4 Motor Fuel Quantity C • C
s5 Motor Fuel Quantity Exponent C • C
s6 Motor Fuel Sale Amount C • C
p0629 Odometer Reading C • C
p0630 Vehicle Number C • C
p0631 Driver Number/ID Number C • C
p0632 Product Type Code C • C
p0633 Coupon/Discount Amount O • C
p0634 Tax Amount 1 O • C
p0635 Tax Amount 2 O • C


p0712 Net Fuel Price O • C
s1 Net Fuel Price O • C
s2 Net Fuel Price Exponent O • C


s2 Trace ID C • C

Financial Detail Addendum (Corporate Line Item

Detail)/1644
This message must be provided if the associated First Presentment/1240 is a:
• MasterCard Corporate Purchasing Card or MasterCard Corporate Fleet
Card® (at a non-fuel location) transaction and
• Is submitted for U.S. region Corporate Data Rate III (IRD 66) incentive
interchange rate program.

Presentment/1240 is for a transaction that was completed with one of the
MasterCard corporate cards.
IRDs 61, 63, 65, 75, 85, or 95).
for specific incentive interchange programs, please refer to chapter 9 of this
manual, or chapter 7 of the GCMS Reference Manual.
Financial Detail Addendum (Corporate Line Item Detail)/1644 Message Layout



p0518 Line Item Date C • C
p0612 Ship Date O • C
p0614 Order Date O • C
p0615 Medical Services Ship To Health Industry O • C
Number
p0616 Contract Number O • C
p0617 Medical Services Price Adjustment O • C
p0618 Medical Services Product Number Qualifier O • C
p0641 Product Code M • M
p0642 Item Description M • M
p0643 Item Quantity M • M
s1 Item Quantity M • M
s2 Item Quantity Exponent M • M
p0645 Item Unit of Measure M • M
p0646 Unit Price O • C
s1 Unit Price O • C
s2 Unit Price Exponent O • C


p0647 Extended Item Amount M • M
s1 Extended Item Amount M • M
s2 Extended Item Amount Exponent M • M
s3 Extended Item Amount Sign M • M
p0648 Item Discount O • C
s1 Discount Indicator O • C
s3 Item Discount Rate O • C
s4 Item Discount Rate Exponent O • C
s5 Item Discount Amount Sign O • C
p0654 Debit or Credit Indicator M • M


p0685 Type of Supply O • C
p0687 Unique VAT Invoice Reference Number O • C


s7 Card Acceptor TaxID 6 O • C
s2 Trace ID C • C


Financial Detail Addendum (Generic Detail)/1644 Message Layout
p0663 Free-Form Description M • M
s2 Trace ID C • C

Financial Detail Addendum (Generic Detail)/1644 Message Layout



First Chargeback/1442 and Arbitration Chargeback/1442 Message Layout
5 Amount, Reconciliation O X C
s1 Date C • C
s2 Time C • C


25 Message Reason Code M • M
30 Amounts, Original M • M
s1 Original Amount, Transaction M • M
s2 Original Amount, Reconciliation M • M
40 Extended Service Code O • C
41 Card Acceptor Terminal ID O • C
s2 Card Acceptor Street Address O • C
s5 Card Acceptor State/Province or Region Code M • M


p0020 Issuer Currency Conversion Rate (ICCR) Effective C • •
Date
s2 Central Site Processing Date of Original O • C
Message
p0043 Program Registration ID O • C
p0052 Electronic Commerce Security Level Indicator O • C
s1 Security Protocol O • C
s2 Cardholder Authentication O • C
s3 UCAF Collection Indicator O • C
p0146 Amounts, Transaction Fee O X C
transaction fee data. Each occurrence has the
following seven subfields:
s1 Fee Type Code O X C
s2 Fee Processing Code O X C
s3 Fee Settlement Indicator O X C
s4 Currency Code, Fee O X C
s5 Amount, Fee O X C
s6 Currency Code, Fee, Reconciliation O X C
s7 Amount, Fee, Reconciliation O X C
exponent data. Each occurrence has the following
two subfields:


p0149 Currency Codes, Amounts, Original M • M
s1 Currency Code, Original Transaction Amount M • M
s2 Currency Code, Original Reconciliation Amount M • M
s7 Card Acceptor Business Code (MCC) • X M
Override Indicator
s5 Settlement Foreign Exchange Rate Class Code • X C


p0241 MasterCom Control Number O • C
p0243 MasterCom Retrieval Response Data • X C
s1 MasterCom Issuer Retrieval Request Date • X C
s2 MasterCom Acquirer Retrieval Response Code • X C
s3 MasterCom Acquirer Retrieval Response Sent • X C
Date
s4 MasterCom Issuer Response Code • X C


s5 MasterCom Issuer Response Date • X C
s6 MasterCom Issuer Reject Reasons • X C
s7 MasterCom Image Review Decision • X C
s8 MasterCom Image Review Date • X C
p0244 MasterCom Chargeback Support Documentation • X C
Dates
s1 MasterCom Chargeback Support • X C
Documentation Sender Processing Date
(First Chargeback/1442)
s2 MasterCom Chargeback Support • X C
Documentation Sender Processing Date
(Second Presentment/1240)
p0260 Edit Exclusion Indicator C X C
s1 Exclusion Request Code C • C
s2 Exclusion Reason Code • X C
s3 Exclusion Results Code • X C
p0262 Documentation Indicator M • M
p0266 First Chargeback/Fee Collection Return Data • X C
s1 Message Reason Code • X C
s2 Date, First Return Business • X C
s3 Edit Exclusion Reason Code • X C
s4 Edit Exclusion Results Code • X C
s5 Amount, First Return • X C
s6 Currency Code, First Return • X C
s7 Data Record, First Return • X C
p0267 Second Presentment/Fee Collection Resubmission • X C
Data
s2 Date, Second Return Business • X C
s5 Amount, Second Return • X C


s6 Currency Code, Second Return • X C
s7 Data Record, Second Return • X C
p0268 Amount, Partial Transaction O • C
s1 Amount, Partial Transaction O • C
s2 Currency Code, Partial Transaction O • C
55 Integrated Circuit Card (ICC) System Related Data O • C
63 Transaction Life Cycle ID O • C
s2 Trace ID O • C
72 Data Record C • C
95 Card Issuer Reference Data M • M

Second Presentment/1240
Second Presentment/1240 Message Layout
6 Amount, Cardholder Billing O X C
10 Conversion Rate, Cardholder Billing • X C
s1 Date C • C
s2 Time C • C


40 Extended Service Code O • C
s5 Card Acceptor State/Province or Region Code M • M


s2 Central Site Processing Date of Original Message O • C
p0043 Program Registration ID O • C
p0052 Electronic Commerce Security Level Indicator O • C
p0146 Amounts, Transaction Fee O X C
transaction fee data. Each occurrence has the
following seven subfields:
This PDS may contain 1–15 occurrences of exponent
data. Each occurrence has the following two
subfields:
s2 Currency Code, Original Reconciliation M • M


s7 Card Acceptor Business Code (MCC) Override • X M
Indicator


p0243 MasterCom Retrieval Response Data • X C
s3 MasterCom Acquirer Retrieval Response Sent • X C
Date


p0244 MasterCom Chargeback Support Documentation • X C
Dates
s1 MasterCom Chargeback Support Documentation • X C
Sender Processing Date (First Chargeback/1442)
s2 MasterCom Chargeback Support Documentation • • •
Sender Processing Date (Second
Presentment/1240)
p0260 Edit Exclusion Indicator C X C
p0262 Documentation Indicator M • M
p0266 First Chargeback/Fee Collection Return Data • X C
p0268 Amount, Partial Transaction O • C
p10XX Member-to-Member Proprietary Data (p1000 through O • C
p1099)
51 Currency Code, Cardholder Billing C X C
55 Integrated Circuit Card (ICC) System Related Data O • C


s2 Trace ID O • C
95 Card Issuer Reference Data M • M

4 Retrieval and Fee Collection Messages
This chapter describes the formats for all retrieval and fee collection messages
that the clearing system uses. The layouts on the following pages identify all
required, conditional, optional, or clearing system–provided data elements for
these messages.
Retrieval Request/1644 Messages .......................................................................4-1
Retrieval Fee Billing Messages............................................................................4-1
Fee Collection Messages .....................................................................................4-2
Retrieval Request/1644........................................................................................4-7
Fee Collection (Retrieval Fee Billing)/1740......................................................4-11
Fee Collection (Handling Fees)/1740 ...............................................................4-16
Fee Collection (Other than Retrieval Fee Billing/Handling Fees)/1740..........4-21

Retrieval and Fee Collection Messages


1644 603 Retrieval Request
1740 700 Fee Collection (Member-Generated)
780 Fee Collection Return (Member-Generated)
781 Fee Collection Resubmission (Member-Generated)
782 Fee Collection Arbitration Return (Member-Generated)
783 Fee Collection (Clearing System-Generated)
Retrieval Request/1644 Messages

An issuer sends a Retrieval Request/1644 to an acquirer when it is determined
that the transaction information document needs to be examined before a
potential chargeback situation, or for other issuer or cardholder needs. The
message must contain 1644 in the Message Type Identifier (MTI) and 603 in
Function Code (Data Element [DE] 24) to identify it as a Retrieval
Request/1644.
Retrieval Fee Billing Messages

If the acquirer fulfills a Retrieval Request/1644 for a hardcopy document, the
acquirer should collect the appropriate hardcopy fulfillment fee by submitting
a Fee Collection (Retrieval Fee Billing)/1740 with the appropriate code
(190000) in DE 3, DE 24 = 700, and DE 25 = 7614. This credits the acquirer
and debits the issuer for the retrieval fulfillment fees.

Fee Collection Messages
Fee Collection Messages

Fee Collection messages are used for the collection or disbursement of fees
that require funds settlement between various clearing system participants.
Fee Collection messages may include fees generated between pairs of
members, and fees generated between the Corporation and members.
Following are some examples of Fee Collection messages:

• Member-to-member collection or disbursement of fees that brand, program,
and service rules permit
• MasterCard-to-member collection or disbursement of fees related to
processing services that the clearing system provides
• MasterCard-to-member collection or disbursement of such fees as
administrative fees, membership fees, and penalties, according to brand,
program, and service
• Member-to-member collection or disbursement of summary settlement
positions between members that participate in bilateral clearing
arrangements with clearing system summary settlement
These messages must contain 1740 in the MTI and one of the following values
in DE 24:
• 700 = Fee Collection (Member-Generated)
• 780 = Fee Collection Return (Member-Generated)
• 781 = Fee Collection Resubmission (Member-Generated)
• 782 = Fee Collection Arbitration Return (Member-Generated)
• 783 = Fee Collection (Clearing System-Generated)
Fee Collection (Clearing System-Generated)/1740 messages (DE 24 = 783)

cannot be returned. Therefore, Function Codes 780, 781, and 782 apply only
to Fee Collection (Member-Generated)/1740 messages (DE 24 = 700).

Data Element Flow
Data Element Flow


Entity Description


Usage
Code Description



Usage
column, or in the Data Elements, or Private Data Subelements
definitions sections.
Data Elements and PDSs Not Currently Supported

Some data elements and private data subelements (PDSs) in the message
layouts may be shaded. Shading indicates those data elements and PDSs not
currently supported by GCMS.

European region.

GCMS system in St. Louis. New elements and values have been introduced
into this manual to prepare for processing of these transactions by GCMS.

Retrieval Request/1644
Retrieval Request/1644 Message Layout
3 Processing Code O • C
s1 Cardholder Transaction Type O • C
s2 Cardholder “From” Account Type Code O • C
s3 Cardholder “To” Account Type Code O • C
12 Date and Time, Local Transaction O • C
s1 Date O • C
s2 Time O • C
26 Card Acceptor Business Code O • C


38 Approval Code O • C
42 Card Acceptor ID Code O • C
43 Card Acceptor Name/Location O • C
s1 Card Acceptor Name O • C
s3 Card Acceptor City O • C
s4 Card Acceptor Postal (ZIP) Code O • C
s5 Card Acceptor State/Province or Region Code O • C
s6 Card Acceptor Country Code O • C
p0148 Currency Exponents M • M
s1 Currency Code M • M
s2 Currency Exponent M • M
p0149 Currency Codes, Amounts Original M • M
p0158 Business Activity O X M
s1 Card Program Identifier O X M
s2 Business Service Level Code O X M
s3 Business Service ID Code O X M
s4 Interchange Rate Designator • X M


Indicator
p0228 Retrieval Document Code M • M
p0242 MasterCom Service Indicator • X C


s2 Trace ID O • C
95 Card Issuer Reference Data O • C

Fee Collection (Retrieval Fee Billing)/1740

Fee Collection (Retrieval Fee Billing)/1740 Message Layout
4 Amount, Transaction • X M


p0137 Fee Collection Control Number M • M
data. Each occurrence has the following two subfields:


Indicator


p0228 Retrieval Document Code O • C
p0230 Fulfillment Document Code M • M
p0262 Documentation Indicator O • C
p0264 Original Retrieval Reason for Request M • M
49 Currency Code, Transaction • X M
s2 Trace ID O • C
72 Data Record O • C
73 Date, Action M • M
93 Transaction Destination Institution ID Code M X M
95 Card Issuer Reference Data O • C



Fee Collection (Handling Fees)/1740

Fee Collection (Handling Fees)/1740 Message Layout


subfields:
s1 Currency Code, Original Transaction Amount C • C
s2 Currency Code, Original Reconciliation Amount C • C


Indicator


p0265 Initial Presentment/Fee Collection Data O • C
s1 Initial Message Reason Code O • C
s2 Date, Initial Presentment Business O • C
s3 Data Record, Initial O • C
p0266 First Chargeback/Fee Collection Return Data O • C
s1 Message Reason Code O • C
s2 Date, First Return Business O • C
s3 Edit Exclusion Reason Code O • C
s4 Edit Exclusion Results Code O • C
s5 Amount, First Return O • C
s6 Currency Code, First Return O • C
s7 Data Record, First Return O • C
p0267 Second Presentment/Fee Collection Resubmission O • C
Data
s2 Date, Second Return Business O • C
s5 Amount, Second Return O • C
s6 Currency Code, Second Return O • C
s7 Data Record, Second Return O • C


s2 Trace ID O • C
72 Data Record M • M
73 Date, Action M • M
93 Transaction Destination Institution ID Code M • M

Fee Collection (Other than Retrieval Fee Billing/Handling Fees)/1740
Fee Collection (Other than Retrieval Fee Billing/Handling

Fees)/1740
Fee Collection (Other than Retrieval Fee Billing/Handling Fees)/1740 Message Layout
2 Primary Account Number (PAN) O • C
31 Acquirer Reference Data O • C
s1 Interchange Rate Designator O • C
s2 Acquirer’s BIN O • C
s3 Julian Processing Date YDDD O • C
s4 Acquirer’s Sequence Number O • C
s5 Check Digit O • C

p0002 Product Identifier • X C
subfields:
s4 Interchange Rate Designator O X M

Indicator

p0265 Initial Presentment/Fee Collection Data O • C
p0266 First Chargeback/Fee Collection Return Data O • C
p0267 Second Presentment/Fee Collection Resubmission O • C
Data

s2 Trace ID O • C
73 Date, Action C • C
93 Transaction Destination Institution ID Code M • M

5 Reconciliation Messages
This chapter describes the formats for all reconciliation messages that the
clearing system uses. Members or member processors may use reconciliation
messages to assist in reconciling offline financial activity. The layouts on the
following pages identify all required, conditional, optional, or clearing system–
provided data elements for these messages.
Functionality Not Currently Supported ..............................................................5-1
Activity Types Accumulated................................................................................5-1
Function Codes Used ..........................................................................................5-2
Message Reason Codes Used..............................................................................5-2
File Currency Summary/1644..............................................................................5-3

File Currency Summary/1644 Acknowledgement Messages .......................5-3
File Currency Summary/1644 Notification Messages...................................5-3
Financial Position Detail/1644 Messages............................................................5-3

Reconciliation Category Summary................................................................5-4
Reconciliation Category Definitions .............................................................5-5
Transmission ID ......................................................................................5-5
File ID......................................................................................................5-5
Account Range ........................................................................................5-6
Acquiring Institution ID Code ................................................................5-6
Member Activity ......................................................................................5-7
Settlement Activity ..................................................................................5-7
Business Activity .....................................................................................5-8
Settlement Indicator ................................................................................5-8
Card Acceptor ID ....................................................................................5-8
Transaction Function ..............................................................................5-8
Message Reason Code ............................................................................5-9
Processing Code (Transaction Type) .....................................................5-9
Member-Specified Reconciliation Criteria ............................................5-10

Reconciliation Messages
Original/Reversal Totals .......................................................................5-10

Transaction Currency............................................................................5-11
Reconciliation Amount/Reconciliation Fee Totals .....................................5-11
Debit/Credit Totals................................................................................5-12


File Currency Summary/1644............................................................................5-21
Financial Position Detail/1644 ..........................................................................5-23



1644 680 File Currency Summary from the clearing system
685 Financial Position Detail from the clearing system
688 Settlement Position Detail from the settlement system
681 Settlement Position Total from the settlement system
Functionality Not Currently Supported

Some information in this chapter may be shaded. Shading indicates IPM
Activity Types Accumulated

Reconciliation messages accumulate only accepted financial activity. Financial
activity includes First Presentment/1240, First Chargeback/1442, Second
Presentment/1240, Arbitration Chargeback/1442, and Fee Collection/1740
messages.
Non-financial activity includes File Header/1644, File Trailer/1644, Text/1644,

Message Exception/1644, File Reject/1644, Retrieval Request/1644, Currency
Update/1644, and Financial Detail Addendum/1644 messages.
Rejected financial activity and all non-financial activity are accumulated and
reported elsewhere.

Function Codes Used
Function Codes Used

Each Reconciliation message type is identified by a unique Function Code
(Data Element [DE] 24) value as shown in the following table:
Function Code Reconciliation Message Type

680 File Currency Summary/1644 (Source currency totals)
685 Financial Position Detail/1644 (Expected settlement totals)
688 Settlement Position Detail/1644 (Actual settlement detail)
681 Settlement Position Total/1644 (Actual settlement totals)
Message Reason Codes Used

The Reconciliation message formats also include a Message Reason Code
(DE 25). The values in this data element allow for a mechanism to easily
segregate acknowledgement and notification Reconciliation messages delivered
in a single offline file, as shown in the following table:
Message Reason
Code Reconciliation Message Reason Code Description
Acknowledgement Reconciliation—the clearing system
6861 generates after processing member outbound activity
Notification Reconciliation—the clearing system generates
6862 for member inbound activity

File Currency Summary/1644

Members may use File Currency Summary/1644 messages to reconcile
transaction currency totals for each offline file. These messages contain debit
amount totals, credit amount totals, and net totals. One File Currency
Summary/1644 is created for each transaction currency that occurs in a file.
File Currency Summary/1644 messages may be provided as acknowledgement

messages (to reconcile a member’s previously submitted outgoing clearing
file), notification messages (to reconcile a member’s incoming clearing data),
or both. The Message Reason Code distinguishes notification and
acknowledgement messages that may be delivered in a common file.
File Currency Summary/1644 Acknowledgement Messages

The clearing system responds to a member-originated file by sending the
member File Currency Summary/1644 acknowledgement messages based on
member profile options. The acknowledgement messages contain the clearing
system-calculated totals by transaction currency for the related member
outbound file. The clearing system calculates totals only for accepted files and
accepted Financial messages.
File Currency Summary/1644 acknowledgement messages contain a 6861

DE 25 value.
File Currency Summary/1644 Notification Messages

The clearing system provides File Currency Summary/1644 notification
messages for each member inbound file based on member profile options.
The notification messages contain the clearing system-calculated totals by
transaction currency for the member’s inbound activity.
File Currency Summary/1644 notification messages contain a 6862 DE 25 value.
Financial Position Detail/1644 Messages

Financial Position Detail/1644 messages may be used to reconcile offline file
financial activity at a more detailed level than File Currency Summary/1644
messages allow. One Financial Position Detail/1644 message is generated for
each unique combination of values for member-selected reconciliation
categories that occur in a file, transmission, or both.

Reconciliation Category Summary

Financial Position Detail/1644 totals may include indicators for several
reconciliation categories to support a broad range of business requirements.
A Financial Position Detail/1644 is generated for each unique combination of
values for the selected reconciliation categories. The amount totals in the
Financial Position Detail/1644 always will be in the member’s reconciliation
currency (based on DE 5 of the original sender or the original receiver,
depending on whether the 1644-685 is going to the sender or receiver and
whether it is an acknowledgement or a notification). The totals also may be in
a transaction currency/reconciliation currency pair depending on whether the
member selects transaction currency as an option. These categories are in the
following table:
Category Acknowledgements Notifications

Reconciled, Transmission (PDS 0298) Y or N N/A
Reconciled, File (PDS 0300) Y or N Y or N
Reconciled, Account Range (PDS 0370) Y or N Y or N
Acquiring Institution ID Code (DE 32) Y or N Y or N
Reconciled, Member Activity (PDS 0302) Y or N Y or N
Reconciled, Settlement Activity (PDS 0359) Y or N Y or N
Reconciled, Business Activity (PDS 0358) Y or N Y or N
Settlement Indicator (PDS 0165) Y or N Y or N
Reconciled, Card Acceptor ID (PDS 0373) Y or N Y or N
Reconciled, Transaction Function Y or N Y or N
(PDS 0372)
Reconciled, Message Reason Code Y or N Y or N
(PDS 0371)
Reconciled, Processing Code (PDS 0374) Y or N Y or N
Member Specified Reconciliation Criteria: Y or N N/A
Member Reconciliation Indicator 1
(PDS 0375)
Member Reconciliation Indicator 2 Y or N N/A
(PDS 0376)
Original/Reversal Totals Indicator Y or N Y or N
(PDS 0378)
Currency Code, Transaction (DE 49) Y or N Y or N

Reconciliation Category Definitions

The following are reconciliation category definitions.
Transmission ID
The originator of a “stacked” transmission may include a common
Transmission ID (PDS 0110) in each File Header/1644 in the transmission. The
same PDS 0110 value should be in each File Header/1644 in the physical
transmission to link the logical files in the physical transmission, if the sender
chooses to receive reconciliation totals for all of these files.
Members/processors may use PDS 0110 to reconcile transmission totals. If
selected as a reconciliation category by the member/processor, Reconciled,
Transmission (PDS 0298) values are in Financial Position Detail/1644 and
Settlement Position Detail/1644 messages. This reconciliation category will be
available only for acknowledgement reconciliation totals. The member or
processor receives acknowledgement reconciliation totals at this level if it
initially provides PDS 0110 in its outgoing clearing files.
File ID
The file originator must create a unique File ID (PDS 0105) for each File
Header/1644 in and across transmissions. The file originator accomplishes this
by using unique values in PDS 0105 in each File Header/1644 and
corresponding File Trailer/1644. The File ID (PDS 0105) for which the totals
are presented is provided in Reconciled File, (PDS 0300) of the Reconciliation
message.
In acknowledgement reconciliation messages, PDS 0300 (Reconciled, File)

contains the File ID (PDS 0105) value submitted by the file originator in
member-generated files.
In notification reconciliation messages, Reconciled, File (PDS 0300) contains

the clearing cycle delivery file ID assigned by GCMS for MasterCard-generated
files.
Members will be able to use the reconciliation message PDS 0300 (Reconciled,
File) values to identify the corresponding File ID on their settlement
advisements as well as their reconciliation reports.

Account Range
Financial position detail totals also may be accumulated by issuing account
range activity for the reconciled member ID. If a member/processor selects
the account range level reconciliation category, Reconciled, Account Range
(PDS 0370) is provided in the Reconciliation messages. Only the member’s
issuing account range activity is provided; members will not receive account
range activity for other issuers’ account ranges. Members who select this
reconciliation option will receive issuing account range totals for all account
ranges they have established with the clearing system.
If the Reconciled, Account Range (PDS 0370) category is selected, the

Reconciled, Member Activity (PDS 0302) also must be selected to obtain
complete amount totals by issuing account range, acquiring activity
(member ID level), and fee collection activity (member ID levels).
Acquiring Institution ID Code

Financial position detail totals may be accumulated by Acquiring Institution ID
Code (DE 32). Members use this optional identifier to further segment their
portfolios. For example, members may use DE 32 to identify relationships
between principal members and their agent banks.
Only the member’s own Acquiring Institution ID Code activity is provided;

members will not receive these totals for other members’ Acquiring Institution
ID Code.
If the Acquiring Institution ID Code (DE 32) category is selected, the

Reconciled, Member Activity (PDS 0302) also must be selected to obtain
complete amount totals by issuing account range, acquiring activity
(member ID level), and fee collection activity (member ID levels).

Member Activity
Members may choose to receive separate financial position detail totals for
their acquiring activity, their issuing activity, and their fee collection activity.
The following table illustrates the clearing system’s classification of Financial
messages as “issuing,” “acquiring,” or “fee collection”:
Fee Collection
Acquiring Activity Issuing Activity for Activity for
Transaction Transaction for the Member the Member the Member
Description Function(s) Identified by Identified by Identified by
First Presentment 1240-200 DE 94 DE 93 n/a
First Chargeback 1442-450, 453 DE 93 DE 94 n/a
Second Presentment 1240-205, 282 DE 94 DE 93 n/a
Arbitration Chargeback 1442-451, 454 DE 93 DE 94 n/a
Fee Collection 1740-700, 780, 781, n/a n/a DE 94 and DE 93a
782, 783
a DE 94 indicates the transaction originator and DE 93 indicates the transaction receiver.
If selected, the Reconciled, Member Activity (PDS 0302) category provides

totals by issuing activity, acquiring activity, and fee collection activity at the
member ID level. If selected with the Account Range Category (PDS 0370),
the totals are by issuing account range, acquiring activity (member ID level),
and fee collections (member ID level).
Members cannot choose just to receive issuing activity, or just fee collection
activity. They will receive totals for whatever activity is processed.
Settlement Activity
Members may choose to receive financial position detail totals by Reconciled,
Settlement Activity (PDS 0359). This provides the settlement service ID and
level, transfer agent, transfer agent account, foreign exchange rate class,
reconciliation date and cycle, and settlement date and cycle being reconciled.
This information is fundamental in reconciling financial clearing activity with
settlement positions.

Business Activity
Members may choose to receive financial position detail totals by Reconciled,
Business Activity (PDS 0358). PDS 0358 includes the card program identifier,
business service ID and level, interchange rate indicator, business date and
business cycle. This allows members to reconcile interchange fees for financial
activity occurring in each business service group.
Settlement Indicator
The settlement indicator in each Financial Position Detail/1644 indicates
whether the totals are MasterCard settled totals, bilaterally settled totals, or
Collection Only totals.
MasterCard settled totals refer to member-to-member and member-to-

MasterCard financial activity for which settlement is completed using the
MasterCard settlement system as opposed to a bilateral arrangement. The
majority of offline clearing transactions are cleared and settled in this manner.
Bilateral totals refer to transactions submitted for clearing that are settled
directly between members by a mechanism other than the MasterCard clearing
system (MasterCard does not settle these transactions).
Collection Only totals refer to On-Us or intraprocessor transactions that were

cleared and settled outside the clearing system. They are sent to the clearing
system for reporting purposes only.
For bilateral and Collection Only totals, amounts will be provided in

transaction currency only, and only if the member has also selected Financial
Position Detail Reconciliation messages in transaction currency.
If members want to be able to reconcile MasterCard settled, bilateral, and

Collection Only activity separately, they should choose this category and the
transaction currency category.
Card Acceptor ID
Members may optionally choose to receive financial position detail totals based
on the original Card Acceptor ID Code (DE 42) provided in transactions. This
field uniquely identifies each financial transaction’s card acceptor (merchant).
Transaction Function
Members may optionally choose to receive reconciliation totals by transaction
function. Transaction function refers to a combination of MTI and DE 24 that
provides a method of uniquely identifying financial transaction categories.

Totals are provided for each unique transaction function supported in the
following transaction function subset:
Description MTI Function Code

Presentments and Second Presentments 1240 200, 205, 282
First Chargebacks and Arbitration Chargebacks 1442 450, 451, 453, 454
Retrieval Requests a 1644 603
Fee Collections 1740 700, 780, 781, 782, 783
a Members selecting this option and submitting 1644-603 (Retrieval Requests; non-financial
messages) will receive reconciliation messages with zero counts and amounts.
Message Reason Code

Members may optionally choose to receive financial position detail totals by
the original DE 25 provided in transactions.
Processing Code (Transaction Type)

Members will receive financial position detail totals by Processing Code
(DE 3). Each financial transaction a member submits and receives contains
one of the following Processing Codes:
Processing
Code Description
00 Purchase (Goods and Services) transaction
01 ATM Cash Withdrawal transaction
12 Cash Disbursement transaction
17 Convenience Checks (Collection Only)
18 Unique transaction
19 Fee Collection (Credit Originator)
20 Credit transaction
28 Payment Transaction
29 Fee Collection (Debit Originator)
50 Payment/Balance Transfers (Collection Only)
Members cannot choose to receive totals for specific DE 3 values. They will
receive totals for all DE 3 activity processed by the clearing system for which
they have activity.

Member-Specified Reconciliation Criteria

Financial message originators may choose to include one or two proprietary
member reconciliation indicators:
• Member Reconciliation Indicator 1 (PDS 0375)

• and Member Reconciliation Indicator 2 (PDS 0376).
These PDSs contain values the originator defined. If provided, the clearing
system generates reconciliation totals based on the originator’s defined values.
This reconciliation category is available for acknowledgement reconciliation
only.
Members can populate PDS 0375 in their member outgoing messages with any
proprietary value up to 50 positions in length.
For example, an acquirer may choose to assign a value for a specific merchant
chain and place this value into PDS 0375 in an outgoing member First
Presentment/1240 message related to the merchant chain. The acquirer can
then choose Member Reconciliation Indicator 1 (PDS 0375) as an
acknowledgement reconciliation message option, and receive
acknowledgement reconciliation messages from GCMS containing totals based
on this merchant chain identifier.
If the member has chosen this reconciliation category, but does not include
PDS 0375 in its member outgoing data, GCMS will create an acknowledgement
reconciliation message with a PDS 0375 value of “undefined.”
Original/Reversal Totals
If selected, the Original/Reversal Totals Indicator (PDS 0378) provides separate
totals for original amounts and reversal amounts.
Reversal transactions consist of all transactions the clearing system receives

with a Message Reversal Indicator (subfield 1 of Message Reversal Indicator
[PDS 0025]) value of R.
Original transactions include both original submissions (there is no PDS 0025

present) and resubmissions (subfield 1 of PDS 0025 contains a space and
subfield 2 contains a date).

Transaction Currency
Each Financial Position Detail/1644 and Settlement Position Detail/1644
messages will contain totals for one transaction and reconciliation currency
pair if the Transaction Currency reconciliation category is selected. All
Financial Position Detail message totals are automatically provided in the
receiving member’s reconciliation currencies.
Members who want to reconcile MasterCard settled, bilateral and Collection

Only activity separately should select this category and the Settlement
Indicator category.
Reconciliation Amount/Reconciliation Fee Totals

Reconciliation currency amounts in Financial Position Detail/1644 messages
provide expected settlement values. Reconciliation currency amounts in
Settlement Position Detail/1644 messages provide the actual settlement values
that appear on settlement advisements upon completion of settlement.
Financial Position Detail/1644 messages provide fee totals (Amounts,

Transaction Fee [PDS 0146]) separately from Amount, Reconciliation (DE 5)
totals. The fee totals are provided by fee type code.

The following table describes the process for accumulating fee totals. All fees
are in PDS 0146. PDS 0146 contains from one to 12 fee occurrences. Subfield
1, Fee Type Code identifies each fee. Each fee is accumulated as either a debit
or a credit based on subfield 2, Fee Processing Code.
Fee
Amount, Fee, Processing Originator Receiver
Reconciliation Code PDS Dr/Cr Dr/Cr
DE/PDS (subfield 7) (subfield 2) 0025 Indicator a Indicator b
PDS 0146 Amount, Fee, 19 - Cr Dr
Reconciliation
PDS 0146 Amount, Fee, 19 R Dr Cr
Reconciliation
PDS 0146 Amount, Fee, 29 - Dr Cr
Reconciliation
PDS 0146 Amount, Fee, 29 R Cr Dr
Reconciliation
a In reconciliation messages, if DE 25 contains 6861, the reconciliation message represents an
acknowledgement, which is an accumulation of a member’s previously submitted
outgoing clearing file. Therefore, when DE 25 is 6861, the reconciliation message is
generated for the originator.
b Further, if DE 25 contains 6862, the reconciliation message represents a notification, which
is an accumulation of a member’s new incoming clearing file. Therefore, when DE 25 is
6862, the reconciliation message is generated for the receiver.
Debit/Credit Totals
Reconciliation messages provide separate totals for debit and credit amounts.
DE 5 reconciliation debit and credit totals are determined for the transaction
originator and transaction destination by using the transaction function (MTI
and DE 24), DE 3, and PDS 0025. For activity other than bilaterally settled or
Collection Only, transaction and fee totals are designated as “debit” or “credit”
based on their settlement impact to each member. For example, an original
retail purchase is accumulated as a credit to the originator (the acquirer) and a
debit to the receiver (the issuer). The following tables detail this concept for
each financial message type.

An acquirer always originates and an issuer always receives the following

financial transactions:
Originator Receiver
Dr/Cr Dr/Cr
PDS Amount Indicator Indicator
MTI DE 24 DE 3 0025 DE/PDS (Acquirer) (Issuer)
1240 200 00–18, 50 - DE 5 Cr Dr
1240 200 00–18, 50 R DE 5 Dr Cr
1240 200 20, 28 - DE 5 Dr Cr
1240 200 20, 28 R DE 5 Cr Dr
1240 205 00–18, 50 - DE 5 Cr Dr
1240 205 00–18, 50 R DE 5 Dr Cr
1240 205 20, 28 - DE 5 Dr Cr
1240 205 20, 28 R DE 5 Cr Dr
1240 282 00–18, 50 - DE 5 Cr Dr
1240 282 00–18, 50 R DE 5 Dr Cr
1240 282 20, 28 - DE 5 Dr Cr
1240 282 20, 28 R DE 5 Cr Dr
An issuer always originates and the acquirer always receives the following
financial transactions:
Originator Receiver
Dr/Cr Dr/Cr
MTI DE 24 DE 3 0025 DE/PDS (Issuer) (Acquirer)
1442 450 00–18, 50 - DE 5 Cr Dr
1442 450 00–18, 50 R DE 5 Dr Cr
1442 450 20, 28 - DE 5 Dr Cr
1442 450 20, 28 R DE 5 Cr Dr
1442 451 00–18, 50 - DE 5 Cr Dr
1442 451 00–18, 50 R DE 5 Dr Cr
1442 451 20, 28 - DE 5 Dr Cr
1442 451 20, 28 R DE 5 Cr Dr
1442 453 00–18, 50 - DE 5 Cr Dr
1442 453 00–18, 50 R DE 5 Dr Cr

Originator Receiver
Dr/Cr Dr/Cr
MTI DE 24 DE 3 0025 DE/PDS (Issuer) (Acquirer)
1442 453 20, 28 - DE 5 Dr Cr
1442 453 20, 28 R DE 5 Cr Dr
1442 454 00–18, 50 - DE 5 Cr Dr
1442 454 00–18, 50 R DE 5 Dr Cr
1442 454 20, 28 - DE 5 Dr Cr
1442 454 20, 28 R DE 5 Cr Dr
The two tables above apply to Collection Only, non-Collection Only, and
bilateral activity.
Both acquirers and issuers may originate and receive Fee Collection messages.
The clearing system may also originate these messages:
Originator Receiver
PDS Amount Dr/Cr Dr/Cr
MTI DE 24 DE 3 0025 DE/PDS Indicator Indicator
1740 700 19 - DE 5 Cr Dr
1740 700 19 R DE 5 Dr Cr
1740 700 29 - DE 5 Dr Cr
1740 700 29 R DE 5 Cr Dr
1740 780 19 - DE 5 Cr Dr
1740 780 19 R DE 5 Dr Cr
1740 780 29 - DE 5 Dr Cr
1740 780 29 R DE 5 Cr Dr
1740 781 19 - DE 5 Cr Dr
1740 781 19 R DE 5 Dr Cr
1740 781 29 - DE 5 Dr Cr
1740 781 29 R DE 5 Cr Dr
1740 782 19 - DE 5 Cr Dr
1740 782 19 R DE 5 Dr Cr
1740 782 29 - DE 5 Dr Cr
1740 782 29 R DE 5 Cr Dr

Settlement Position Detail/1644
Originator Receiver
PDS Amount Dr/Cr Dr/Cr
MTI DE 24 DE 3 0025 DE/PDS Indicator Indicator
1740 783 19 - DE 5 Cr Dr
1740 783 19 R DE 5 Dr Cr
1740 783 29 - DE 5 Dr Cr
1740 783 29 R DE 5 Cr Dr

Settlement Position Detail/1644 messages may be used to reconcile financial
activity at the file or transmission level against settlement funds transfers.
These messages are generated after settlement cutoffs and provide totals for
each full and partial transmission or file processed in the cutoff.
Reconciliation Categories
Settlement Position Detail/1644 messages may include indicators for several
reconciliation categories. A Settlement Position Detail/1644 is generated for
each unique combination of values for the selected reconciliation categories.

Reconciled, Transmission (PDS 0298) Y or N N/A
Reconciled, File (PDS 0300) Y or N Y or N
Reconciled, Business Activity (PDS 0358) Y or N Y or N
Reconciled, Card Acceptor ID (PDS 0373) Y or N Y or N
Reconciled, Transaction Function (PDS 0372) Y or N Y or N
Reconciled, Message Reason Code Y or N Y or N
(PDS 0371) (fee collections only)
Reconciled, Processing Code (PDS 0374) Y or N Y or N


Member Specified Reconciliation Criteria:
Member Reconciliation Indicator 1 (PDS 0375) Y or N N/A
Member Reconciliation Indicator 2 (PDS 0376) Y or N N/A
Original/Reversal Totals Indicator (PDS 0378) Y or N Y or N
Currency Code, Transaction (DE 49) Y or N Y or N
Reconciliation Totals
The amount totals in the Settlement Position Detail/1644 always will be in the
member’s reconciliation currency.
Each Settlement Position Detail/1644 may contain totals for one transaction
and reconciliation currency pair. Source currencies include transaction
currencies and transaction fee currencies. Reconciliation currency amounts
indicate the actual settlement values that appear on settlement advisements
once settlement is completed.

Settlement Position Total/1644

Settlement Position Total/1644 messages provide a summary of reconciliation
currency totals for each settlement cutoff. These messages may be used to
reconcile financial positions against settlement funds transfers.
Reconciliation Categories
Settlement Position Total/1644 messages include indicators for several
reconciliation categories. A Settlement Position Total/1644 is generated for
each unique combination of values for the selected reconciliation categories.
These categories include the following:

Member Specified Reconciliation Criteria:
(PDS 0375)

(PDS 0376)
Reconciliation Totals
Each Settlement Position Total/1644 provides totals for one reconciliation
currency. The totals provided indicate “actual” settlement positions.

Data Element Flow
Data Element Flow


Entity Description


Usage
Code Description



Usage
column, or in the Data Element or Private Data Subelement
definitions sections.


File Currency Summary/1644 Message Layouts
25 Message Reason Code • X M
p0148 Currency Exponents • X M
This PDS contains the currency code and
exponent to which the totals pertain.
It has the following two subfields:
s1 Currency Code • X M
s2 Currency Exponent • X M
p0300 Reconciled, File • X M
p0380 Debits, Transaction Amount in Transaction • X M
Currency
s1 Debit/Credit Indicator • X M
s2 Amount, Transaction • X M
p0381 Credits, Transaction Amount in Transaction • X M
Currency
p0384 Amount, Net Transaction in Transaction Currency • X M
s2 Amount, Net • X M
p0400 Debits, Transaction Number • X M

File Currency Summary/1644 Message Layouts

p0401 Credits, Transaction Number • X M
p0402 Total, Transaction Number • X M
49 Currency Code, Transaction • X M
62 Additional Data 2 • X C

Financial Position Detail/1644

Financial Position Detail/1644 Message Layout
32 Acquiring Institution ID Code • X C
p0165 Settlement Indicator • X C
s1 Settlement Indicator • X C
p0298 Reconciled, Transmission • X C
s1 Transmission Type • X C
s2 Transmission Reference Date • X C
s3 Processor ID • X C
s4 Transmission Sequence Number • X C
p0300 Reconciled, File • X C
s1 File Type • X C
s2 File Reference Date • X C
s4 File Sequence Number • X C
p0302 Reconciled, Member Activity • X C
p0358 Reconciled, Business Activity • X C
s1 Card Program Identifier • X C
s2 Business Service Level Code • X C
s3 Business Service ID Code • X C


s4 Interchange Rate Designator • X C
s5 Business Date (YYMMDD) • X C
s6 Business Cycle • X C
s7 Card Acceptor Business Code (MCC) Override • X C
Indicator
s8 Product Override Indicator • X C
s9 Corporate Incentive Rates Apply Indicator • X C
s10 ATM Late Presentment Indicator • X C
p0359 Reconciled, Settlement Activity • X C
s7 Reconciliation Code • X C
p0370 Reconciled, Account Range • X C
s1 Beginning Account Range ID • X C
s2 Ending Account Range ID • X C
p0371 Reconciled, Message Reason Code • X C
p0372 Reconciled, Transaction Function • X C
s1 Message Type Identifier • X C
s2 Function Code • X C
p0373 Reconciled, Card Acceptor ID • X C
p0374 Reconciled, Processing Code • X C
p0375 Member Reconciliation Indicator 1 • X C
p0378 Original/Reversal Totals Indicator • X C


p0380 Debits, Transaction Amount in Transaction Currency • X C
s1 Debit/Credit Indicator • X C
s2 Amount, Transaction • X C
p0381 Credits, Transaction Amount in Transaction Currency • X C
p0384 Amount, Net Transaction in Transaction Currency • X C
s2 Amount, Net • X C
p0390 Debits, Transaction Amount in Reconciliation Currency • X M
p0391 Credits, Transaction Amount in Reconciliation Currency • X M
p0392 Debits, Fee Amount in Reconciliation Currency • X M
s1 Fee Type Code • X M
s3 Amount, Fee • X M
p0393 Credits, Fee Amount in Reconciliation Currency • X M
p0394 Amount, Net Transaction in Reconciliation Currency • X M
p0395 Amount, Net Fee in Reconciliation Currency • X M
s2 Amount, Net Fee • X M


p0396 Amount, Net Total in Reconciliation Currency • X M
s2 Amount, Net Total • X M
49 Currency Code, Transaction • X C
50 Currency Code, Reconciliation • X M


Settlement Position Detail/1644 Message Layout
p0298 Reconciled, Transmission • X C
p0300 Reconciled, File • X C
p0358 Reconciled, Business Activity • X C
s2 Business Service Level Code • X C


s7 Card Acceptor Business Code (MCC) Override • X C
Indicator
s8 Product Override Indicator • X C
s9 Corporate Incentive Rates Apply Indicator • X C
s10 ATM Late Presentment Indicator • X C
p0371 Reconciled, Message Reason Code • X C
p0372 Reconciled, Transaction Function • X C
p0373 Reconciled, Card Acceptor ID • X C
p0374 Reconciled, Processing Code • X C
p0378 Original/Reversal Totals Indicator • X C


p0380 Debits, Transaction Amount in Transaction Currency • X C
p0381 Credits, Transaction Amount in Transaction Currency • X C
p0384 Amount, Net Transaction in Transaction Currency • X C
s2 Amount, Net • X C
p0392 Debits, Fee Amounts in Reconciliation Currency • X M
p0395 Amount, Net Fee in Reconciliation Currency • X M


49 Currency Code, Transaction • X C


Settlement Position Total/1644 Message Layout
48 Additional Data (Private) • X M
This PDS will contain 1 occurrence of exponent data. It
has the following two subfields:


p0392 Debits, Fee Amount in Reconciliation Currency • X M
p0395 Amounts, Net Fee in Reconciliation Currency • X M



6 Administrative Messages
This chapter describes the formats for all administrative messages that the
clearing system uses. The layouts on the following pages identify all required,
conditional, optional, or clearing system–provided data elements for these
messages.
Message Exception/1644 Messages ....................................................................6-1

Data Record (DE 72).....................................................................................6-3
File Reject/1644 Messages...................................................................................6-4

Data Record (DE 72).....................................................................................6-5
Text Message/1644 Messages .............................................................................6-5
Currency Update/1644 Messages........................................................................6-6
Message Exception and File Reject/1644 .........................................................6-10
Text Message/1644 ............................................................................................6-12
Currency Update/1644 ......................................................................................6-13

Administrative Messages


1644 691 Message Exception
699 File Reject
693 Text Message
640 Currency Update
Message Exception/1644 Messages

The clearing system generates Message Exception/1644 messages when it
encounters an exception condition while processing an individual message.
The following chart summarizes the conditions and messages generated for the
various levels of severity (errors, adjustments, and warnings):
Level of What the

Severity Condition What the Originator Receives Destination Receives
Error Unparseable or Message Exception/1644 only Nothing
unrecognizable (rejected message is not returned)
message
Error Error in one or Message Exception/1644 Nothing
more supported Plus
elements
The rejected message itself. If generated by the
IPM Pre-edit utility, message number (Data
Element [DE] 71) in the rejected message is
modified to contain a value that is greater than
the DE 71 value of the preceding message in the
file. If generated by GCMS, DE 71 in the rejected
message is not modified.
Adjustment GCMS Message Exception/1644 The adjusted message
adjusts/modifies Plus (normal processing).
one or more
The adjusted message itself. If generated by the
supported
IPM Pre-edit utility, DE 71 message number in
elements.
the adjusted message is modified to contain a
value that is greater than the DE 71 value of the
preceding message in the file. If generated by
GCMS, DE 71 in the adjusted message is not
modified.

Level of What the

Warning Any Message Exception/ 1644 only The message (normal
(denoting a warning) processing)
The Message Exception/1644 message contains a code identifying the error,

adjustment or warning. It also contains the data element number(s) or private
data subelement (PDS) number(s) that caused the exception condition(s).
Other identifying information related to the message is presented if the

clearing system can parse the information. Following is a summary of the
critical data provided:
DE or PDS Contents
MTI 1644
DE 24 691
DE 72 1–10 data element and PDS numbers in error and their contents.
May also include additional explanatory text.
PDS 0005 Message error or adjustment code(s), severity code(s), and data
element and PDS number(s) in error
PDS 0025 Reversal Indicator of the exception message (if the clearing system
is able to parse)
PDS 0138 Message Number (DE 71) of the exception message (if the clearing
system is able to parse)
PDS 0165 Settlement Indicator of the exception message (if the clearing
system is able to parse)
PDS 0261 Risk Management Approval Code assigned to First Presentments
that exceeded the issuer and/or acquirer transaction amount limits.
PDS 0261 is not present in the Message Exception/1644 message.
Instead, GCMS inserts it into the First Presentment/1240 message
that follows the Message Exception/1644 message
PDS 0280 File ID (PDS 0105) of the file containing the exception message
(from the File Header/1644, if present, and the clearing system is
able to parse)

Data Record (DE 72)

In a Message Exception/1644, DE 72 contains 1–10 data element and PDS
numbers in error and their contents, if the clearing system can parse the
message. If a message rejects because the clearing system cannot parse it,
DE 72 contains the first 1–200 positions of the rejected message. DE 72 may
contain additional information as well, depending on the message reject
reason. Following are some examples of DE 72 contents in a Message
Exception/1644.
• If the clearing system rejects a message because the combination of MTI
and Function Code (DE 24) is invalid, DE 72 is formatted as follows:
D024\contents MTI^contents of DE24\\1–200 positions of the rejected
message
• If the clearing system rejects a message because a single element contains
an invalid value, DE 72 is formatted as follows:
DXXX (or PXXXX)\contents of DXXX (or PXXXX)\\
• If the clearing system rejects a message because more than one element or
subfield is in error, DE 72 is formatted as follows:
DXXX\contents\\PXXXX\contents\\PXXXX\contents\\
• If the clearing system rejects a Financial Detail Addendum/1644, DE 72 is
formatted as follows:
\USAGE=xx,IND REC NO=yyy, OCCUR=aaa^DExxx(or
PDSxxxx)\contents\\

File Reject/1644 Messages
File Reject/1644 Messages

The clearing system generates File Reject/1644 messages to indicate that it has
rejected an entire file. There are no warning or adjustment conditions in File
Reject/1644 messages, only errors as indicated in the following table:
Level of What the

Error Any File Reject/1644 and, if applicable, a Message Nothing
Exception/1644
(If all detail messages in a logical file reject, the
clearing system returns each detail message in a
Message Exception/ 1644-691 message. In addition,
it returns a File Reject/1644-699 message [since it did
not accept any of the individual messages]. The
clearing system returns individual error messages
with the Full File Reject Message.)
The File Reject/1644 contains the error code(s) that caused the file to reject,
plus 1–200 positions of the rejected file’s first message. In addition, if the
clearing system identifies any individual data element or PDS errors, the
erroneous data element or PDS and related error codes is presented. Other
identifying information related to the file is presented if the clearing system can
parse it.
The following table summarizes the critical data provided:
DE or PDS Contents
MTI 1644
DE 24 699
DE 72 1–200 positions of the rejected file’s first message, plus specific data
elements and PDSs and their values that are in error, if applicable
PDS 0005 File reject error code(s), severity code(s) indicating “fatal,” and
specific data elements and PDSs and their related error codes, if
applicable
PDS 0138 Message Number (DE 71) of the message that caused the file to
reject (if the clearing system is able to parse)
PDS 0280 File ID (PDS 0105) of the rejected file (from the File Header/1644, if
present, and the clearing system is able to parse)

Text Message/1644 Messages
Data Record (DE 72)

In a File Reject/1644, DE 72 always contains the first 1–200 positions of the
rejected file’s first message. DE 72 may contain additional information as well,
depending on the file reject reason. Following are some examples of DE 72
contents in a File Reject/1644:
• If the clearing system rejects a file because DE 71 in the File Header/1644
contains a value other than 00000001, DE 72 is formatted as follows:
DE71\contents of DE71\\1–200 positions of the rejected file’s first message
• If the clearing system rejects a file because DE 71 in the header message
contains a value other than 00000001 and PDS 0026 is present in the File
Header/1644, DE 72 is formatted as follows:
DE71\contents of DE71\\PDS0026\contents of PDS0026\\1–200 positions
of the rejected file’s first message
• If the clearing system rejects a file because PDS 0306 in the File
Trailer/1644 is not equal to the total number of messages in the logical file,
DE 72 is formatted as follows:
PDS0306\contents of PDS0306^SYSTEM CALCULATED
VALUE=XXXXXXXX\\1–200 positions of the rejected file’s first message
• If a file is rejected because it contains no messages, no recognizable
messages, no File Header/1644 messages, or all messages in the file
rejected, DE 72 is formatted as follows:
\1–200 positions of the rejected file’s first message
Text Message/1644 Messages

Text Message/1644 messages are used for the following function types:
• Transmit text messages from the clearing system to a member or processor
• Transmit “broadcast” messages from the clearing system to all
members/processors
This message will contain 1644 in Message Type Identifier (MTI) and 693 in
Function Code (DE 24) to identify it as a Text Message/1644. In a delivery file
containing more than one clearing cycle of data, one message will be present
per member, per file.

Currency Update/1644 Messages
Currency Update/1644 Messages

Currency Update/1644 messages provide conversion rates between MasterCard
Global Payment currency and all other MasterCard-supported payment
currencies. MasterCard supports buy, mid, and sell currency conversion rates.
Members may request Currency Update/1644 messages from MasterCard as
part of the clearing file.
The following are delivery options for Currency Update/1644 messages:

• Do not deliver Currency Update/1644 messages
• Deliver mid rate Currency Update/1644 messages
• Deliver buy and sell rate Currency Update/1644 messages only
• Deliver buy, mid, and sell rate Currency Update/1644 messages
Once these options are selected the member must also specify which clearing
cycles they have selected to receive the deliveries. The clearing cycles
indicated should coincide with a delivery cycle for that member or endpoint.
This message will contain 1644 in Message Type Identifier (MTI) and 640 in
Function Code (DE 24) to identify it as a Currency Update/1644 message.

Data Element Flow
Data Element Flow


Entity Description


Usage
Code Description



Usage
column, or from the Data Elements, or Private Data Subelements
definition sections.
Data Elements and PDSs Not Currently Supported


Message Exception and File Reject/1644

Message Exception and File Reject/1644 Message Layout
p0005 Message Error Indicator • X M
message exception data. Each reported exception
consists of the following three subfields:
s1 Data Element ID • X M
s2 Error Severity Code • X M
s3 Error Message Code • X M
s4 Subfield ID • X M
p0006 Applied Business Service Arrangement • X C
p0025 Message Reversal Indicator • X C
s1 Message Reversal Indicator • X C
s2 Central Site Processing Date of Original • X C
Message
p0026 File Reversal Indicator • X C
s1 File Reversal Indicator • X C
s2 Central Site Processing Date of Original File • X C
p0138 Source Message Number ID • X C
s2 Settlement Information • X C

Message Exception and File Reject/1644 Message Layout

p0280 Source File ID • X C
72 Data Record • X C
94 Transaction Originator Institution ID Code • X M

Text Message/1644
Text Message/1644
Text Message/1644 Message Layout
72 Data Record • X M

Currency Update/1644
Currency Update/1644
Currency Update/1644 Message Layout
– Message Type Identifier • X M
– Bit Map, Primary • X M
p0164 Currency Cross Rates • X M
conversion rate data. Each occurrence has the
following five subfields:
s2 Currency Conversion Rate • X M
s3 Currency Conversion Type • X M
s5 Clearing Cycle • X M
p0280 Source File ID • X C

7 Data Element Definitions
This chapter provides a detailed definition of all data elements used in IPM
format offline clearing messages.
Presentation of Data Element Information.........................................................7-1
Data Element Listing (Numerical Order) ............................................................7-8
Data Element Listing (Alphabetical Order) ......................................................7-13
Message Type Identifier ....................................................................................7-18
Bit Map, Primary................................................................................................7-22
DE 1—Bit Map, Secondary ...............................................................................7-25
DE 2—Primary Account Number (PAN) ..........................................................7-28
DE 3—Processing Code ....................................................................................7-30
DE 4—Amount, Transaction .............................................................................7-35
DE 5—Amount, Reconciliation .........................................................................7-38
DE 6—Amount, Cardholder Billing ..................................................................7-41
DE 8—Amount, Cardholder Billing Fee ...........................................................7-43
DE 9—Conversion Rate, Reconciliation ...........................................................7-44
DE 10—Conversion Rate, Cardholder Billing ..................................................7-46
DE 12—Date and Time, Local Transaction ......................................................7-48
DE 14—Date, Expiration...................................................................................7-51
DE 22—Point of Service Data Code .................................................................7-52
DE 23—Card Sequence Number ......................................................................7-65

Data Element Definitions
DE 24—Function Code .....................................................................................7-66
DE 25—Message Reason Code .........................................................................7-70
DE 26—Card Acceptor Business Code (MCC) .................................................7-99
DE 30—Amounts, Original ............................................................................. 7-101
DE 31—Acquirer Reference Data ................................................................... 7-104
DE 32—Acquiring Institution ID Code........................................................... 7-108
DE 33—Forwarding Institution ID Code ........................................................ 7-111
DE 37—Retrieval Reference Number ............................................................. 7-113
DE 38—Approval Code................................................................................... 7-115
DE 40—Service Code ..................................................................................... 7-117
DE 41—Card Acceptor Terminal ID ............................................................... 7-119
DE 42—Card Acceptor ID Code ..................................................................... 7-121
DE 43—Card Acceptor Name/Location.......................................................... 7-123
DE 48—Additional Data.................................................................................. 7-133
DE 49—Currency Code, Transaction.............................................................. 7-136
DE 50—Currency Code, Reconciliation.......................................................... 7-138
DE 51—Currency Code, Cardholder Billing................................................... 7-140
DE 55—Integrated Circuit Card (ICC) System-Related Data.......................... 7-142
DE 62—Additional Data 2............................................................................... 7-148
DE 63—Transaction Life Cycle ID .................................................................. 7-151
DE 71—Message Number ............................................................................... 7-163
DE 72—Data Record ....................................................................................... 7-166
DE 73—Date, Action ....................................................................................... 7-168
DE 93—Transaction Destination Institution ID Code .................................... 7-169

DE 94—Transaction Originator Institution ID Code...................................... 7-172
DE 95—Card Issuer Reference Data............................................................... 7-175
DE 100—Receiving Institution ID Code ......................................................... 7-177
DE 127—Network Data................................................................................... 7-189

Presentation of Data Element Information

This chapter provides a detailed definition of all ISO-defined data elements
used in IPM messages. Data element information is presented in the following
order:
• An explanation of the notation used throughout this chapter to describe all
data element attributes.
• A summary list of all data element names in the order of their ISO-assigned
bit (data element) numbers, followed by a list of these elements in data
element name alphabetic order. Included in both lists are each data
element’s attributes.
• A detailed definition of each data element, arranged in order of data
element number. For data elements that are not used, no definition is
provided. Each data element description includes the following
information:
− The original ISO definition, directly from the ISO 8583–1993
specification.
− Attributes, including data element length, data field formats,
justification, and processing restrictions.
− A detailed description of data element usage requirements by message
type.
− A detailed listing, if applicable, of specific values that may be used
within each data element, given by subfield, when applicable.
− A list of related required data elements and PDSs.
− Additional information that addresses any other rules and instructions.
Bit Mapped Message Encoding Technique

All messages are variable-length, with a bit map scheme used as the first data
element(s) of the message following the Message Type Identifier (MTI) to
indicate the presence or absence of additional data elements in the message.
Each bit map is a 64-bit string contained within an eight-byte data element.
The first bit in each bit map is 1 or 0 to indicate the presence or absence of
another (immediately following) bit map data element.

The clearing system uses a maximum of two bit maps: a “Primary” and a
“Secondary” Bit Map. Bits 1 or 0 in the Primary Bit Map indicate the presence
or absence of Primary Account Number (PAN) (Data Element [DE] 2) through
Message Authentication Code (MAC) (DE 64). Bits 1 or 0 in the Secondary Bit
Map indicate the presence or absence of Reserved (ISO) (DE 65) through
Message Authentication Code (MAC) (DE 128).
Note All bit positions are interpreted from left to right within each bit map; for
example, within the Primary Bit Map the leftmost bit is “bit number 1” and the
rightmost bit is “bit number 64.”
Bit number 1 in the Primary Bit Map and bit number 65 in the Secondary Bit
Map (that is, the first bit in each bit map) do not have corresponding data
elements; these bits indicate the presence or absence of additional bit map
data elements in the message. If bit number 1 is 1, it indicates that the
Secondary Bit Map is present and that selected data elements in the range
DE 65–DE 128 also are present in the message as indicated by bit positions in
the Secondary Bit Map.
Each message must contain the Primary Bit Map. The Secondary Bit Map must
be included in a message only when there are data elements in the range
DE 65–DE 128 present in the message.
Note As of the publication date of this document, all IPM messages require data
elements from both bit maps; therefore, both bit maps must be included in all
messages.

Annotation of Data Element Attributes

The following notation conventions are employed throughout this manual to
describe the attributes of all data elements:
Data Representation Attributes
Notation Description
a alphabetic characters A–Z and a–z
n numeric digits 0–9
as alphabetic characters A–Z and a–z, and space character
ns numeric digits 0–9 and special characters (including space)
an alphabetic and numeric characters
ans alphabetic, numeric, and special characters (including space)
b binary representation of data in eight-bit bytes
Date and Time Attributes
MM month (two digits; 01–12)
DD day (two digits; 01–31)
YY year (last two digits of calendar year; 00–99)
hh hour (two digits; 00–23)
mm minute (two digits; 00–59)
ss second (two digits; 00–59)

Data Length Attributes
-digit(s) Fixed length in number of positions.
Example: “n-3” indicates a three-position numeric data element.
Example: “an-10” indicates a 10-position alphanumeric data
element.
...digit(s) Variable length, with maximum number of positions specified.
Example: “n...11” indicates a variable-length numeric data element
of 1–11 digits.
Example: “an...25” indicates a variable-length alphanumeric data
element of 1–25 positions.
LLVAR Present with a variable-length data element attribute, indicates that
the data element contains two fields:
“LL” is the length field and represents the number of positions in the
variable-length data field that follows. The length field contains a
value in the range 01–99.
“VAR” is the variable-length data field.
Example: “an…25; LLVAR” represents a variable-length
alphanumeric data element with a length of 1–25 positions.
LLLVAR Present with a variable-length data element attribute, indicates that
“LLL” is the length field and represents the number of positions in
the variable-length data field that follows. The length field contains
a value in the range 001–999.
Example: “an..500; LLLVAR” indicates a variable-length
alphanumeric data element having a length of 1–500 positions.
Conventions for Data Representation

This specification is independent of the specific data encoding format (for
example, EBCDIC or ASCII).
The following data encoding conventions are standard for all messages.
• All message data elements are aligned on byte boundaries, for example, a
data element cannot begin with the low order “nibble“ or any bit other
than the high order bit of any byte.
• All binary (attribute “b”) data elements are constructed of bit-strings that
have lengths that are an integral number of eight-bit bytes. No binary data
element has a length of less than eight bits (one byte).

Note “b-8” indicates a fixed length binary field of eight characters (eight bytes, 64
bits).
• All track 2 or track 3 (attribute “ans”) data elements are encoded as

EBCDIC representations of the hexadecimal data specified in the ISO 7811
and 7812 specifications. (Refer to “Using this Manual” for a complete list
of IPM-related ISO specifications.) Thus, a hexadecimal “D” (binary 1101)
is encoded as an EBCDIC “D” character, and so forth. The “LL” or “LLL”
length specification associated with these data elements specifies the data
element length in number of bytes.
• All length fields are encoded as numeric, right-justified with leading zeros:
− Data elements with “LL” attributes have length fields with values in the
range 01–99.
− Data elements with “LLL” attributes have length fields with values in the
range 001–999.
Data Field and Subfield Justification

Right-justified data fields and subfields that do not contain a value that fills the
entire field must contain leading zeros. Most numeric (attribute “n”) data
elements are right-justified; for example, amounts always have this right
justification with leading zeros.
Left justified fields and subfields that do not use the entire field with a value
must have trailing spaces.
Justification of data elements and subfields are given under the “Attributes” and
“Subfields” headings throughout this chapter. A justification of not applicable
(n/a) indicates that the values contained within those fields or subfields take
up all positions allowed.
Maximum Lengths for Variable-Length Data Elements

There are two possible “maximum” lengths associated with each variable-
length data element:
• The ISO-defined maximum length
• The IPM-defined maximum length

Examples
Transaction Originator Institution ID Code (DE 94)—The ISO defined
maximum is 11 positions. The IPM format allows members to send 11
positions but edits and passes only six positions to the receiver.
Transaction Life Cycle ID (DE 63)—The ISO-defined maximum is 999

positions. The IPM format, however, currently supports only 16 positions.
In daily production files, the clearing system provides these data elements to
the receiving member with lengths less than or equal to the maximum lengths
currently supported. For example, the clearing system provides a six-position
value in DE 94 and a 16-position value in DE 63.
Subfield Presence Requirements

Data elements and PDSs may contain subfields. Some of these subfields are
mandatory and some are optional. For all fixed-length data elements and
PDSs, all subfields must be populated. For variable-length data elements and
PDSs, the following rules exist:
• All subfields that comprise the minimum length for the data element or
PDS must be populated. Subfields that are beyond the minimum length of
the element are optional and should not be populated unless the sender
has valid data to present. In other words, optional subfields must not be
populated with filler characters such as all spaces or all zeros.
• If any optional subfield is presented with valid data, all subfields preceding
that subfield must be populated. In this case, filler characters such as
spaces are acceptable. For example, if a PDS contains four subfields, and
the sender has valid data to present for subfields 1, 2, and 4, it must fill
subfield 3 with all spaces or all zeros so that all four subfields are
presented in the correct positions for the PDS.


European region.

accommodate processing of offline Maestro, and Cirrus transactions. These
manual to prepare for processing of these transactions by GCMS.

Data Element Listing (Numerical Order)

The following table is a listing of all the data elements in numerical order. The
lengths listed in the Attribute column are ISO-defined. Shaded rows indicate
data elements not currently used.
Number Name Attribute

- Message Type Identifier (MTI) n-4
- Bit Map, Primary b-8
1 Bit Map, Secondary b-8
2 Primary Account Number (PAN) n...19; LLVAR
3 Processing Code n-6
4 Amount, Transaction n-12
5 Amount, Reconciliation n-12
6 Amount, Cardholder Billing n-12
7 Date and Time, Transmission (not currently used) n-10;
MMDDhhmmss
8 Amount, Cardholder Billing Fee n-8
9 Conversion Rate, Reconciliation n-8
10 Conversion Rate, Cardholder Billing n-8
11 Systems Trace Audit Number(not currently used) n-6
12 Date and Time, Local Transaction n-12;
YYMMDDhhmmss
13 Date, Effective (not currently used) n-4; YYMM
14 Date, Expiration n-4; YYMM
15 Date, Settlement (not currently used) n-6; YYMMDD
16 Date, Conversion (not currently used) n-4; MMDD
17 Date, Capture (not currently used) n-4; MMDD
18 Merchant Type (not currently used) n-4
19 Country Code, Acquiring Institution n-3
(not currently used)
20 Country Code, Primary Account Number (PAN) n-3
21 Country Code, Forwarding Institution n-3


22 Point of Service Data Code an-12
23 Card Sequence Number n-3
24 Function Code n-3
25 Message Reason Code n-4
26 Card Acceptor Business Code (MCC) n-4
27 Approval Code Length (not currently used) n-1
28 Date, Reconciliation (not currently used) n-6; YYMMDD
29 Reconciliation Indicator (not currently used) n-3
30 Amounts, Original n-24
31 Acquirer Reference Data ans...99; LLVAR
32 Acquiring Institution ID Code n...11; LLVAR
33 Forwarding Institution ID Code n...11; LLVAR
34 Primary Account Number (PAN), Extended n...28; LLVAR
35 Track 2 Data (not currently used) ans…37: LLVAR
36 Track 3 Data (not currently used) ans...104; LLLVAR
37 Retrieval Reference Number ans-12
38 Approval Code ans-6
39 Action Code (not currently used) n-3
40 Service Code n-3
41 Card Acceptor Terminal ID ans-8
42 Card Acceptor ID Code ans-15
43 Card Acceptor Name/Location ans...99; LLVAR
44 Additional Response Data (not currently used) ans...99; LLVAR
45 Track 1 Data (not currently used) ans…76; LLVAR
46 Amounts, Fees (not currently used) ans...204; LLLVAR
47 Additional Data (National) (not currently used) ans...999; LLLVAR
48 Additional Data ans...999; LLLVAR
49 Currency Code, Transaction n-3
50 Currency Code, Reconciliation n-3
51 Currency Code, Cardholder Billing n-3


52 Personal ID Number (PIN) Data (not currently used) b-8
53 Security Related Control Information (not currently b...48; LLVAR
used)
54 Amounts, Additional (not currently used) ans...120; LLLVAR
55 Integrated Circuit Card (ICC) System Related Data b...255; LLLVAR
56 Original Data Elements (not currently used) n...35; LLVAR
57 Authorization Life Cycle (not currently used) n-3
58 Authorizing Agent Institution ID Code n...11; LLVAR
59 Transport Data (not currently used) ans...999; LLLVAR
60 Reserved (National) (not currently used) ans...999; LLLVAR
62 Additional Data 2 ans...999; LLLVAR
63 Transaction Life Cycle ID ans...999; LLLVAR
64 Message Authentication Code (MAC) b-8
65 Reserved (ISO) (not currently used) b-8
66 Amounts, Original Fees (not currently used) ans...204; LLLVAR
67 Extended Payment Data (not currently used) n-2
68 Country Code, Receiving Institution n-3
69 Country Code, Settlement Institution n-3
70 Country Code, Authorizing Agent Institution n-3
71 Message Number n-8
72 Data Record ans...999; LLLVAR
73 Date, Action n-6; YYMMDD
74 Credits, Number (not currently used) n-10
75 Credits, Reversal Number (not currently used) n-10
76 Debits, Number (not currently used) n-10
77 Debits, Reversal Number (not currently used) n-10
78 Transfers, Number (not currently used) n-10


79 Transfers, Reversal Number (not currently used) n-10
80 Inquiries, Number (not currently used) n-10
81 Authorizations, Number (not currently used) n-10
82 Inquiries, Reversal Number (not currently used) n-10
83 Payments, Number (not currently used) n-10
84 Payments, Reversal Number (not currently used) n-10
85 Fee Collections, Number (not currently used) n-10
86 Credits, Amount (not currently used) n-16
87 Credits, Reversal Amount (not currently used) n-16
88 Debits, Amount (not currently used) n-16
89 Debits, Reversal Amount (not currently used) n-16
90 Authorizations, Reversal Number n-10
91 Country Code, Transaction Destination Institution n-3
92 Country Code, Transaction Originator Institution n-3
93 Transaction Destination Institution ID Code n...11; LLVAR
94 Transaction Originator Institution ID Code n...11; LLVAR
95 Card Issuer Reference Data n-10; LLVAR
96 Key Management Data (not currently used) b...999; LLLVAR
97 Amount, Net Reconciliation (not currently used) ans-17
98 Payee (not currently used) ans-25
99 Settlement Institution ID Code (not currently used) n...11; LLVAR
100 Receiving Institution ID Code n...11; LLVAR
101 File Name (not currently used) ans...17; LLVAR
102 Account ID 1 (not currently used) ans...28; LLVAR
103 Account ID 2 (not currently used) ans...28; LLVAR
104 Transaction Description (not currently used) ans...100; LLLVAR
105 Credits, Chargeback Amount (not currently used) n-16
106 Debits, Chargeback Amount (not currently used) n-16
107 Credits, Chargeback Number (not currently used) n-10


108 Debits, Chargeback Number (not currently used) n-10
109 Credits, Fee Amounts (not currently used) ans...84; LLVAR
110 Debits, Fee Amounts (not currently used) ans...84; LLVAR
111 Reserved (ISO) (not currently used) ans...999; LLLVAR
126 Conversion Data (not currently used) ans...999; LLLVAR
127 Network Data (not currently used) ans...999; LLLVAR
128 Message Authentication Code (MAC) b-8

Data Element Listing (Alphabetical Order)

The following table lists the data elements in alphabetical order. The lengths
listed in the Attribute column are ISO-defined. Shaded rows indicate data
elements not currently used.
Name Number Attribute

Account ID 1 (not currently used) 102 ans...28; LLVAR
Account ID 2 (not currently used) 103 ans...28; LLVAR
Acquirer Reference Data 31 ans...99; LLVAR
Acquiring Institution ID Code 32 n...11; LLVAR
Action Code (not currently used) 39 n-3
Additional Data (National) (not currently used) 47 ans...999; LLLVAR
Additional Data 48 ans...999; LLLVAR
Additional Data 2 62 ans...999; LLLVAR
Additional Response Data (not currently used) 44 ans...99; LLVAR
Amount, Cardholder Billing 6 n-12
Amount, Cardholder Billing Fee 8 n-8
Amount, Net Reconciliation (not currently used) 97 ans-17
Amount, Reconciliation 5 n-12
Amount, Transaction 4 n-12
Amounts, Additional (not currently used) 54 ans...120; LLLVAR
Amounts, Fees (not currently used) 46 ans...204; LLLVAR
Amounts, Original 30 n-24
Amounts, Original Fees (not currently used) 66 ans...204; LLLVAR
Approval Code 38 ans-6
Approval Code Length (not currently used) 27 n-1
Authorization Life Cycle (not currently used) 57 n-3
Authorizations, Number (not currently used) 81 n-10


Authorizations, Reversal Number 90 n-10
Authorizing Agent Institution ID Code 58 n...11; LLVAR
Bit Map, Primary - b-8
Bit Map, Secondary 1 b-8
Card Acceptor Business Code (MCC) 26 n-4
Card Acceptor ID Code 42 ans-15
Card Acceptor Name/Location 43 ans...999; LLLVAR
Card Acceptor Terminal ID 41 ans-8
Card Issuer Reference Data 95 n-10
Card Sequence Number 23 n-3
Conversion Data (not currently used) 126 ans...999; LLLVAR
Conversion Rate, Cardholder Billing 10 n-8
Conversion Rate, Reconciliation 9 n-8
Country Code, Acquiring Institution 19 n-3
Country Code, Authorizing Agent Institution 70 n-3
Country Code, Forwarding Institution 21 n-3
Country Code, Primary Account Number (PAN) 20 n-3
Country Code, Receiving Institution 68 n-3
Country Code, Settlement Institution 69 n-3
Country Code, Transaction Destination Institution 91 n-3
Country Code, Transaction Originator Institution 92 n-3
Credits, Amount (not currently used) 86 n-16
Credits, Chargeback Amount (not currently used) 105 n-16
Credits, Chargeback Number (not currently used) 107 n-10


Credits, Fee Amounts (not currently used) 109 ans...84; LLVAR
Credits, Number (not currently used) 74 n-10
Credits, Reversal Amount (not currently used) 87 n-16
Credits, Reversal Number (not currently used) 75 n-10
Currency Code, Cardholder Billing 51 n-3
Currency Code, Reconciliation 50 n-3
Currency Code, Transaction 49 n-3
Data Record 72 ans...999; LLLVAR
Date and Time, Local Transaction 12 n-12; YMMDDhhmmss
Date and Time, Transmission (not currently used) 7 n-10; MMDDhhmmss
Date, Action 73 n-6; YYMMDD
Date, Capture (not currently used) 17 n-4; MMDD
Date, Conversion (not currently used) 16 n-4; MMDD
Date, Effective (not currently used) 13 n-4; YYMM
Date, Expiration 14 n-4; YYMM
Date, Reconciliation (not currently used) 28 n-6; YYMMDD
Date, Settlement (not currently used) 15 n-6; YYMMDD
Debits, Amount (not currently used) 88 n-16
Debits, Chargeback Amount (not currently used) 106 n-16
Debits, Chargeback Number (not currently used) 108 n-10
Debits, Fee Amounts (not currently used) 110 ans...84; LLVAR
Debits, Number (not currently used) 76 n-10
Debits, Reversal Amount (not currently used) 89 n-16
Debits, Reversal Number (not currently used) 77 n-10
Extended Payment Data (not currently used) 67 n-2
Fee Collections, Number (not currently used) 85 n-10
File Name (not currently used) 101 ans...17; LLVAR
Forwarding Institution ID 33 n...11; LLVAR
Function Code 24 n-3
Inquiries, Number (not currently used) 80 n-10
Inquiries, Reversal Number (not currently used) 82 n-10


Integrated Circuit Card (ICC) System Related Data 55 b...255; LLLVAR
Key Management Data (not currently used) 96 b...999; LLLVAR
Merchant Type (not currently used) 18 n-4
Message Authentication Code (MAC) 64 b-8
Message Authentication Code (MAC) 128 b-8
Message Number 71 n-8
Message Reason Code 25 n-4
Message Type Identifier (MTI) - n-4
Network Data 127 ans…999; LLLVAR
Original Data Elements (not currently used) 56 n...35; LLVAR
Payee (not currently used) 98 ans-25
Payments, Number (not currently used) 83 n-10
Payments, Reversal Number (not currently used) 84 n-10
Personal ID Number (PIN) Data 52 b-8
Point of Service Data Code 22 an-12
Primary Account Number (PAN) 2 n...19; LLVAR
Primary Account Number (PAN), Extended 34 ns...28; LLVAR
Processing Code 3 n-6
Receiving Institution ID Code 100 n...11; LLVAR
Reconciliation Indicator (not currently used) 29 n-3
Reserved (ISO) (not currently used) 65 b-8
Reserved (ISO) (not currently used) 111 ans...999; LLLVAR
Reserved (National) (not currently used) 60 ans...999; LLLVAR


Retrieval Reference Number 37 ans-12
Security Related Control Information 53 b...48; LLVAR
Service Code 40 n-3
Settlement Institution ID Code (not currently used) 99 n...11; LLVAR
Systems Trace Audit Number (not currently used) 11 n-6
Track 1 Data (not currently used) 45 ans…76; LLVAR
Track 2 Data (not currently used) 35 ans…37; LLVAR
Track 3 Data (not currently used) 36 ans...104; LLLVAR
Transaction Description (not currently used) 104 ans...100; LLLVAR
Transaction Destination Institution ID Code 93 n...11; LLVAR
Transaction Life Cycle ID 63 ans...999; LLLVAR
Transaction Originator Institution ID Code 94 n...11; LLVAR
Transfers, Number (not currently used) 78 n-10
Transfers, Reversal Number (not currently used) 79 n-10
Transport Data (not currently used) 59 ans...999; LLLVAR

Message Type Identifier

The Message Type Identifier (MTI) is a four-digit numeric field describing the
type of message being interchanged.
Attributes
n-4
Length Field: None

Data Field: fixed length 4 positions
Subfields: None
Justification: n/a
Usage
The following table shows the usage of this data element (whether it is
mandatory, conditional, optional, system provided, or not required) in
applicable messages:
Usage
Message Type Identifier Org Sys Dst
File Header (Member-Generated)/1644 M • •
File Header (Clearing System-Generated)/1644 • X M
File Trailer (Member-Generated)/1644 M • •
File Trailer (Clearing System-Generated)/1644 • X M
First Presentment/1240 M • M
Financial Detail Addendum (Passenger Transport Detail—General M • M
Ticket Information)/1644
Financial Detail Addendum (Passenger Transport Detail—Trip Leg M • M
Data)/1644
Financial Detail Addendum (Vehicle Rental Detail)/1644 M • M
Financial Detail Addendum (Lodging Summary)/1644 M • M
Financial Detail Addendum (Temporary Services)/1644 M • M

Usage
Financial Detail Addendum (Shipping/Courier Services)/1644 M • M
Financial Detail Addendum (Payment Transaction Detail)/1644 M • M
Financial Detail Addendum (Telephony Billing–Summary)/1644 M • M
Financial Detail Addendum (Telephony Billing–Detail)/1644 M • M
Financial Detail Addendum (Electronic Invoice–Transaction M • M
Data)/1644
Financial Detail Addendum (Electronic Invoice–Party M • M
Information)/1644
Financial Detail Addendum (Corporate Card Common Data M • M
Requirements)/1644
Financial Detail Addendum (Corporate Fleet Transaction M • M
Information)/1644
Financial Detail Addendum (Corporate Line Item Detail)/1644 M • M
Financial Detail Addendum (Generic Detail)/1644 M • M
First Chargeback/1442 and Arbitration Chargeback/1442 M • M
Second Presentment/1240 M • M
File Currency Summary/1644 • X M
Financial Position Detail/1644 • X M
Settlement Position Detail/1644 • X M
Settlement Position Total/1644 • X M
Retrieval Request/1644 M • M
Fee Collection (Retrieval Fee Billing)/1740 M • M
Fee Collection (Handling Fees)/1740 M • M
Fee Collection (Other than Retrieval Fee Billing/Handling Fees)/1740 M • M
Message Exception/1644 and File Reject/1644 • X M
Text Message/1644 • X M
Currency Update/1644 • X M

The MTI identifies the general classification of an ISO standard message. It

must be present as the first data field of every IPM message, preceding the ISO
bit map(s).
Values
The message types the clearing system currently supports are in the following
table:
MTI Description
1240 Presentment
1442 Chargeback
1644 Administrative
1740 Fee Collection
Relationship of MTI to Clearing System Transactions

The MTI does not identify a specific clearing system transaction function, only
the general ISO message type. The MTI together with Function Code (DE 24)
are required to determine the actual transaction function to be performed.
A summary list of all MTI and Function Code combinations the clearing system
supports is in the table below. Together, these two data elements define all
the clearing system transaction functions.
MTI Function Code Clearing System Transaction Function

1240 282 Second Presentment (Partial)
1442 451 Arbitration Chargeback (Full) a
1442 453 First Chargeback (Partial)

1442 454 Arbitration Chargeback (Partial) a
1644 603 Retrieval Request a
1644 640 Currency Update

1644 680 File Currency Summary
1644 681 Settlement Position Total


1644 685 Financial Position Detail
1644 688 Settlement Position Detail
1644 693 Text Message
1644 695 File Trailer
1644 697 File Header
1644 699 File Reject
1740 700 Fee Collection (Member-Generated) b
1740 780 Fee Collection Return

1740 781 Fee Collection Resubmission
1740 782 Fee Collection Arbitration Return
1740 783 Fee Collection (Clearing System-Generated)
a Not supported for ATM transactions (DE 3 = 010000).
b Fee Collection (Member-Generated)/1740 messages include manually-submitted (non-
MasterCom) retrieval fulfillments.

Bit Map, Primary
Bit Map, Primary

Bit Map, Primary is a series of 64 bits that identify the presence (denoted by 1)
or the absence (denoted by 0) of Bit Map, Secondary (DE 1) through Message
Authentication Code (MAC) (DE 64) in the message.
Attributes
b-8
Length Field: None

Data Field: fixed length 8 bytes (for each bit map)
Subfields: None
Justification: n/a
Usage
Usage
First Presentment/1240 M X M
Financial Detail Addendum (Passenger Transport Detail—General M X M
Financial Detail Addendum (Passenger Transport Detail—Trip Leg M X M
Data)/1644
Financial Detail Addendum (Vehicle Rental Detail)/1644 M X M
Financial Detail Addendum (Lodging Summary)/1644 M X M
Financial Detail Addendum (Temporary Services)/1644 M X M

Bit Map, Primary
Usage
Financial Detail Addendum (Shipping/Courier Services)/1644 M X M
Financial Detail Addendum (Payment Transaction Detail)/1644 M X M
Financial Detail Addendum (Telephony Billing–Summary)/1644 M X M
Financial Detail Addendum (Telephony Billing–Detail)/1644 M X M
Financial Detail Addendum (Electronic Invoice–Transaction M X M
Data)/1644
Financial Detail Addendum (Electronic Invoice–Party M X M
Information)/1644
Financial Detail Addendum (Corporate Card Common Data M X M
Requirements)/1644
Financial Detail Addendum (Corporate Fleet Transaction M X M
Information)/1644
Financial Detail Addendum (Corporate Line Item Detail)/1644 M X M
Financial Detail Addendum (Generic Detail)/1644 M X M
First Chargeback/1442 and Arbitration Chargeback/1442 M X M
Second Presentment/1240 M X M
Retrieval Request/1644 M X M
Fee Collection (Retrieval Fee Billing)/1740 M X M
Fee Collection (Handling Fees)/1740 M X M
Fee Collection (Other than Retrieval Fee Billing/Handling Fees)/1740 M X M

Bit Map, Primary
This data element must always be included in every IPM message as the
second data field immediately following the MTI. It indicates the presence or
absence of DE 1–DE 64 in the message.
The use of bit maps allows message originators to include only those data
elements in a message that are required for a specific function.
Related Required Data Element

DE 1 is also required in every IPM message to be used in conjunction with Bit
Map, Primary. DE 1 must be the third data field of every IPM message
following the MTI and Bit Map, Primary.
A total bit map mechanism of 128 bits comprises these two bit maps to select
any combination of the 128 standard ISO data elements within an IPM
message.
Note All MasterCard IPM messages have mandatory data elements from both the
Primary and Secondary Bit Maps. Therefore, both Primary and Secondary Bit
Maps are required in all IPM messages.

DE 1—Bit Map, Secondary

Bit Map, Secondary (DE 1) is a series of 64 bits that identify the presence
(denoted by 1) or the absence (denoted by 0) of Reserved (ISO) (DE 65)
through Message Authentication Code (MAC) (DE 128) in the message.
Attributes
b-8
Length Field: None

Data Field: fixed length 8 bytes (for each bit map)
Subfields: None
Justification: n/a
Usage
Usage
Data)/1644

Usage
Data)/1644
Information)/1644
Requirements)/1644
Information)/1644

This data element must always be in every IPM message as the third data field
immediately following the MTI and the Bit Map, Primary. It indicates the
presence or absence of DE 65–DE 128 in the message.
The use of bit maps allows message originators to include only those data
elements in a message that are required for a specific function.
Related Required Data Element

Bit Map, Primary is also required in every IPM message to be used with DE 1.
A total bit map mechanism of 128 bits comprises the two bit maps to select
any combination of the 128 standard ISO data elements in an IPM message.
Note All MasterCard IPM messages have mandatory data elements from both the
Primary and Secondary Bit Maps. Therefore, both Primary and Secondary Bit
Maps are required in all IPM messages.

DE 2—Primary Account Number (PAN)

Primary Account Number (PAN) (DE 2) is a series of digits that identify a
customer account or relationship.
Attributes
n...19; LLVAR
Length Field: 2 positions, value = 06–19
Data Field: variable length 6–19 positions
Subfields: None
Justification: None
Current Processing Restrictions

The clearing system accepts a DE 2 length of up to 19 positions.
The clearing system expects DE 2 to contain the appropriate number of

positions for the account number without any filler characters to the left or
right. For example, if a 16-digit account number is captured for a given
transaction, the length of DE 2 must be 16 and exactly 16 digits must be
provided beginning in position 1 of DE 2.
Usage
Usage

Usage
Fee Collection (Other than Retrieval Fee Billing/Handling Fees)/1740 O • C
This data element identifies the cardholder’s PAN. It contains an account

number of up to 19 digits that is encoded on magnetic stripe track 1 and track
2 of a bankcard, or embossed on a bankcard’s face.
This data element is required for bankcard-originated authorization, financial,

and related transactions.
The PAN used in a First Presentment/1240 must remain the same in all
subsequent life cycle messages related to it (such as subsequent Retrieval
Request/1644, Chargeback/1442, and Second Presentment/1240 messages).
If DE 2 is not provided in the Fee Collection/1740 message for the collection

of Handling Fees; the receiving member has the right to return the message.
Values
This data element is used for all numeric PANs up to 19 digits long.
Specific requirements for PAN composition are detailed in the ISO 7812 and
7813 specifications. All PANs used in messages must conform to the ISO PAN
encoding requirements as specified in these documents.
In addition, all transactions processed through the clearing system must

include PAN data that complies with MasterCard rules and policy publications.

DE 3—Processing Code
Processing Code (DE 3) is a series of digits that describe the effect of a
transaction on a customer account and the type of accounts affected.
Attributes
n-6
Length Field: None
Subfields: 3
Justification: see “Subfields”
Usage
Usage

Usage
Retrieval Request/1644 O • C
s1 Cardholder Transaction Type O • C
s2 Cardholder “From” Account Type Code O • C
s3 Cardholder “To” Account Type Code O • C
The Processing Code describes in First Presentment/1240 messages the

cardholder transaction type at the point of interaction. It also indicates
whether Amount, Transaction (DE 4) is to be applied as a credit or a debit to
the cardholder’s account.
It is also used in the following transaction life cycle messages related to a First
Presentment/1240 to properly identify the original cardholder transaction type
and ensure proper application of funds:
• Retrieval Request/1644
• First Chargeback/1442
• Second Presentment/1240
• Arbitration Chargeback/1442

For all life cycle messages related to a First Presentment/1240, the DE 3 value
must remain the same.
The Processing Code is also used in Fee Collection messages to indicate funds
movement direction.
Subfields
DE 3 comprises three subfields, as indicated in the following table:
Number Position(s) Name Attribute Justification

1 1–2 Cardholder Transaction Type n-2 n/a
2 3–4 Cardholder “From” Account n-2 n/a
Type Code
3 5–6 Cardholder “To” Account Type n-2 n/a
Code
Subfield 1 describes the specific cardholder transaction type.
Subfield 2 describes the cardholder account type affected for cardholder

“debit” and “inquiry” transactions and the “from” account type for cardholder
“transfer” transactions.
Subfield 3 describes the cardholder account type affected for cardholder

“credit” transactions and the “to” account type for cardholder “transfer”
transactions. This subfield is currently not used and must be populated with
00.
Subfield 1: Cardholder Transaction Type

The Cardholder Transaction Types the clearing system supports are in the
following tables:
For MasterCard-branded transactions:
Value Description
Cardholder Account Debits

00 Purchase (Goods and Services).
01 ATM Cash Withdrawal.
12 Cash Disbursement.
17 Convenience Check (Available Only in Collection Only Messages).

Value Description
18 Unique Transaction (Requires Unique MCC).
19 Fee Collection (Credit to Transaction Originator).
Cardholder Account Credits

20 Credit (Purchase Return)
29 Fee Collection (Debit to Transaction Originator)
Transfer Services
50 Payment/Balance Transfer (Available Only in Collection Only Messages).
Note Currently Convenience Checks and Payment/Balance Transfers are valid for
Collection Only transactions.
For Maestro transactions:
Value Description
00 Purchase (Goods and Services)
01 ATM Cash Withdrawal
12 Cash Disbursement
19 Fee Collection (Credit to Transaction Originator)
20 Credit (purchase return)
For Cirrus transactions:
Value Description
01 ATM Cash Withdrawal
12 Cash Disbursement
19 Fee Collection (Credit to Transaction Originator).

For chargebacks and second presentments, GCMS edits to ensure the

processing code value (DE 3, subfield 1) matches the value from the previous
cycle
Subfield 2: Cardholder “From” Account Type Code
For MasterCard-branded transactions:
Value Description
00 Default Account
For Maestro and Cirrus transactions:
Value Description
00 Default Account
10 Savings Account
20 Checking Account
30 Credit Card Account
Subfield 3: Cardholder “To” Account Type Code

The Cardholder “To” Account Type Code subfield must be 00 (default account)
in all clearing system messages.
Related Data Element

Refer to DE 26 later in this chapter for more Card Acceptor Business Code
information.

DE 4—Amount, Transaction
Amount, Transaction (DE 4) is the amount of funds the cardholder requested
in the currency appearing on the transaction information document (TID),
which may be the acquirer’s local currency or a currency acceptable to the
cardholder and card acceptor that the acquirer supports, exclusive of Amounts,
Transaction Fee (PDS 0146). If no currency is identified on the TID, the
transaction is deemed to have taken place in the currency that is legal tender
at the point of interaction.
Attributes
n-12
Length Field: None
Subfields: None
Justification: Right
Usage
Usage
Fee Collection (Retrieval Fee Billing)/1740 • X M

In First Presentment/1240 Messages

DE 4 is the cardholder transaction actual amount in the acquirer’s local
currency, or in a currency to which the card acceptor and cardholder agree
and that the acquirer supports. It is exclusive of any transaction fees
associated with the transaction. This may or may not be the same as the
original amount the card acceptor requested in a related authorization request.
In First Chargeback/1442 Messages

DE 4 is the First Chargeback/1442 amount in the First Chargeback/1442
currency, exclusive of any transaction fees.1 A First Chargeback/1442 is
classified as “partial” if it is for less than the First Presentment/1240 amount.
In Second Presentment/1240 Messages

DE 4 is the Second Presentment/1240 amount in the Second Presentment/1240
currency, exclusive of any transaction fees. A Second Presentment/1240 is
classified as “partial” if it is for less than the First Presentment/1240 amount.
In Arbitration Chargeback/1442 Messages

DE 4 is the Arbitration Chargeback/1442 amount in the Arbitration
Chargeback/1442 currency, exclusive of any transaction fees. An Arbitration
Chargeback/1442 is classified as “partial” if it is for less than the amount of the
First Presentment/1240.
In Fee Collection/1740 Messages

DE 4 is the Fee Collection /1740 transaction amount, exclusive of any
transaction fees.
In Fee Collection Return/1740 Messages

DE 4 is the Fee Collection Return/1740 transaction amount, exclusive of any
transaction fees.
1 For ATM First Chargeback/1442 messages destined for the non-intra-country MasterCard
Debit Switch (MDS) identifier, the issuer must add interchange fees to the chargeback
amount before sending the message.

In Fee Collection Resubmission/1740 Messages

DE 4 is the Fee Collection Resubmission/1740 transaction amount, exclusive of
any transaction fees.
In Fee Collection Arbitration Return/1740 Messages

DE 4 is the Fee Collection Arbitration Return/1740 transaction amount,
exclusive of any transaction fees.
Related Required Data Element and PDS

The following data element and PDS must be present in conjunction with DE 4
to identify the transaction’s currency and exponent:
• Currency Code, Transaction (DE 49)
• Currency Exponents (PDS 0148)
Values
In first chargebacks, second presentments, arbitration chargebacks, and fee
collection messages, if the transaction is not an intracurrency settlement service
level transaction, or an intra-European transaction, DE 4 must contain the U.S.
dollar equivalent of the original transaction amount.
If the account number is a MasterCard World card used at a World card T&E
MCC, and is submitted for IRD 75, 85, 95, or 96, then DE 4 must be greater
than the MasterCard World card chargeback minimum amount.
For all Consumer POS debit transactions submitted for U.S. Region Small Ticket
interchange program (IRD 25), DE 4 Amount, Transaction must contain a value
of USD 15.00 or less.
In all messages other than Fee Collection/1740 messages, DE 4 must be greater

than zero.
All currency amounts are expressed in the minor unit of currency without a
decimal separator in accordance with ISO standards for currency notation. For
example, a transaction amount of USD 212.50 is expressed as 000000021250.

DE 5—Amount, Reconciliation
Amount, Reconciliation (DE 5) is the Amount, Transaction (DE 4) value
converted to the member’s reconciliation (that is, the member’s payment or
settlement) currency.
This amount is exclusive of any fees that are provided in Amounts, Transaction
Fee (PDS 0146).
Attributes
n-12
Length Field: None

Subfields: None
Usage
Usage
First Presentment/1240 C X C
First Chargeback/1442 and Arbitration Chargeback/1442 O X C
Second Presentment/1240 O X C
Fee Collection (Retrieval Fee Billing)/1740 O X C
Fee Collection (Handling Fees)/1740 O X C
Fee Collection (Other than Retrieval Fee Billing/Handling Fees)/1740 O X C
For ATM transactions submitted by the MasterCard Debit Switch (MDS) this
element is mandatory.
For bilaterally settled transactions, this element is optional.
For all other transactions, the clearing system always provides this element.


DE 5 is DE 4 converted to the issuer’s reconciliation currency for the
transaction. The clearing system may use an adjusted conversion rate.
In First Chargeback/1442 Messages

DE 5 is DE 4 converted to the acquirer’s reconciliation currency for the
transaction.

DE 5 is DE 4 converted to the issuer’s reconciliation currency for the
transaction.
In Arbitration Chargeback/1442 Messages

DE 5 is DE 4 converted to the acquirer’s reconciliation currency for the
transaction.
In Fee Collection/1740 Messages, Fee Collection Return/1740

Messages, Fee Collection Resubmission/1740 Messages, or Fee
Collection Arbitration Return/1740 Messages
DE 5 is DE 4 converted to the transaction destination party’s reconciliation
currency for the transaction.
Note The preceding usage notes assume the transaction passes all system edits and
therefore DE 5 is calculated in the destination party’s reconciliation currency.
If a transaction is rejected and therefore returned to the originator, DE 5 is not
calculated or presented in the message.

Related Data Element and PDS

to identify the reconciliation (payment) currency and exponent:
• Currency Code, Reconciliation (DE 50)
Values
example, a reconciliation amount of USD 212.50 is expressed as 000000021250.

DE 6—Amount, Cardholder Billing

Amount, Cardholder Billing (DE 6) is Amount, Transaction (DE 4) converted to
the issuer’s designated cardholder billing currency.
This amount is exclusive of any fees that are provided in Amounts, Transaction
Fee (PDS 0146).
Attributes
n-12
Length Field: None
Subfields: None
Usage
Usage
First Presentment/1240 O X C
For bilaterally settled transactions, this element is optional.


DE 6 is DE 4 converted to the issuer’s cardholder billing currency. The
clearing system may use an adjusted conversion rate.

DE 6 is DE 4 converted to the issuer’s cardholder billing currency.

to identify the cardholder billing currency and exponent:
• Currency Code, Cardholder Billing (DE 51)
The clearing system determines the cardholder billing currency for transactions
based on data processing parameters issuers select in their member profile
database. Cardholder billing currency selection may be established on issuing
account range (PAN) data and other criteria.
The clearing system also optionally allows issuers to determine the cardholder
billing currency for a given transaction based on the account range and the
transaction currency in DE 49.
Values
example, a cardholder billing amount of USD 212.50 is expressed as
000000021250.

DE 8—Amount, Cardholder Billing Fee
DE 8—Amount, Cardholder Billing Fee

Amount, Cardholder Billing Fee (DE 8) is the currency conversion revenue the
card issuing institution is to receive from the Amount, Cardholder Billing
(DE 6).
Attributes
n-8
Length Field: None

Subfields: None
Usage
Usage
First Presentment/1240 • X C
This data element contains the calculated issuer currency conversion rate
adjustment amount. DE 6 represents the total amount to be posted to the
cardholder account for the transaction and is inclusive of this DE 8 amount.
The clearing system provides DE 8 when the transaction qualifies for an Issuer
Currency Conversion Rate (ICCR) adjustment and the issuer chose the option
to assess an additional currency conversion adjustment.
Note It is the issuer’s responsibility to interpret the legal disclosure obligation for this
fee based on the laws governing the issuer.

DE 9—Conversion Rate, Reconciliation

Conversion Rate, Reconciliation (DE 9) is the factor used in converting
transaction amount to reconciliation amount. After adjusting for the decimal
location, DE 9 is multiplied by Amount, Transaction (DE 4) to determine
Amount, Reconciliation (DE 5).
Attributes
n-8
Length Field: None
Subfields: None
Justification: n/a
Usage
Usage
First Chargeback/1442 and Arbitration Chargeback/1442 • X C
Second Presentment/1240 • X C
Fee Collection (Retrieval Fee Billing)/1740 • X C
Fee Collection (Handling Fees)/1740 • X C
Fee Collection (Other than Retrieval Fee Billing/Handling Fees)/1740 • X C
This data element is calculated by dividing DE 5 by DE 4. The result is

adjusted to fit within the last seven positions of DE 9, and the first position is
populated with the number of decimal places. DE 9 provides the “currency
conversion cross-rate” from DE 4 to DE 5.
DE 9 is present in a message whenever DE 4 and DE 5 are present.

Note This data element is simply a quotient of the two related “amount” data
elements, and may not reflect the actual currency conversion rate(s) or
algorithm(s) the clearing system uses to execute the currency conversion
service.
Values
The left-most digit denotes the number of positions that the decimal separator
shall be moved from the right. The left-most digit is in the range 0–9. For
example, a data value of 91234567 indicates a conversion rate of 0.001234567.
If DE 5 = DE 4, then DE 9 will contain a value of 61000000.

DE 10—Conversion Rate, Cardholder Billing

Conversion Rate, Cardholder Billing (DE 10) is the factor used in converting
transaction amount to cardholder billing amount. After adjusting for the
decimal location, DE 10 is multiplied by Amount, Transaction (DE 4) to
determine Amount, Cardholder Billing (DE 6).
Attributes
n-8
Length Field: None
Subfields: None
Justification: n/a
Usage
Usage
This data element is calculated by dividing DE 6 by DE 4. The result is

adjusted to fit within the last seven positions of DE 10, and the first position is
populated with the number of decimal places. DE 10 provides the “currency
conversion cross-rate” from DE 4 to DE 6.
DE 10 is present in a message whenever DE 4 and DE 6 are present.
Note This data element is simply a quotient of the two related “amount” data
elements, and may not reflect the actual currency conversion rate(s) or
algorithm(s) the clearing system uses to execute the currency conversion
service.

Values
The left-most digit denotes the number of positions that the decimal separator
shall be moved from the right. The left-most digit is in the range 0–9. For
example, a data value of 91234567 indicates a conversion rate of 0.001234567.
If DE 6 = DE 4, then DE 10 will contain a value of 61000000.

DE 12—Date and Time, Local Transaction

Date and Time, Local Transaction (DE 12) is the local year, month, day, and
time at which the transaction takes place at the card acceptor location.
Attributes
n-12; YYMMDDhhmmss
Length Field: None

Subfields: 2
Usage
Usage
First Presentment/1240 C • C
s1 Date C • C
s2 Time C • C
First Chargeback/1442 and Arbitration Chargeback/1442 C • C
s1 Date C • C
s2 Time C • C
Second Presentment/1240 C • C
s1 Date C • C
s2 Time C • C
s1 Date O • C
s2 Time O • C

For business transaction life cycle messages, DE 12 contains the actual

cardholder transaction local date and time at the point of interaction.
The DE 12 value submitted in the First Presentment/1240 should remain the

same in all subsequent Retrieval and Chargeback transactions.
Subfields
In First Presentment/1240 messages, this data element must contain a valid
date to qualify for most incentive interchange programs. The two subfields are
in the following table:

1 1–6 Date n-6; YYMMDD n/a
2 7–12 Time n-6; hhmmss n/a
The following are rules for the Date subfield:
The transaction date is the date on

For the following transactions… which...
Face-to-Face the goods or services are exchanged.
Non–Face-to-Face the merchandise is shipped.
vehicle rental the vehicle is returned, or, if applicable, the
prepayment date.
lodging checkout occurred, or if applicable, the
prepayment date.
no-show the cardholder was expected to arrive at the
hotel or motel and failed to appear.
airline/railway the ticket was issued.
cruise line the transportation documents are issued.
on-board cruise line the passenger disembarks.
credit the card acceptor grants a credit or price
adjustment.
all in-flight commerce transactions the flight departs from the originating city.
except in-flight commerce mailed The transaction date for in-flight commerce
purchases, mailed purchases is the shipment date unless
otherwise disclosed to the cardholder.

The following are requirements for the Date and Time subfields:
• If the transaction is a first presentment, the Date subfield must be present
and contain a valid date in the format YYMMDD, unless it is one of the
following:
− Standard interchange
− Credit
− Reversal
• The date cannot be greater than the file header date provided in subfield 2,
File Reference Date, of File ID (PDS 0105), unless the transaction is
Collection Only.
• In Retrieval Request transactions, if the day portion of the date subfield is
unknown or unavailable, it may be populated with zeros, if the transaction
does not qualify for an incentive interchange program.
• The time subfield must be in hhmmss format representing hours, minutes,
and seconds. The hours portion (hh) must contain a value in the range
00–23, and the minutes (mm), and seconds (ss) portion must contain a
• If the transaction time is unknown or unavailable, the time subfield should
be populated with zeros.

DE 14—Date, Expiration
DE 14—Date, Expiration
Date, Expiration (DE 14) specifies the year and month after which a card
expires.
Attributes
n-4; YYMM
Length Field: None
Subfields: None
Justification: n/a
Usage
Usage
First Presentment/1240 O • C
First Chargeback/1442 and Arbitration Chargeback/1442 O • C
Second Presentment/1240 O • C
Fee Collection (Retrieval Fee Billing)/1740 O • C
This data element may be used in messages to contain the date after which a
card “expires” and is no longer valid for cardholder use.
Values
This data element must consist of a year (YY) and a month (MM).

DE 22—Point of Service Data Code

Point of Service Data Code (DE 22) is a series of codes that identify terminal
capability, terminal environment, and point-of-interaction (POI) security data.
It indicates specific conditions that are (or were) present at the time a
transaction took place at the point of interaction.
Attributes
an-12
Length Field: None
Subfields: 12
Usage
Usage

Usage
This data element describes in First Presentment/1240 messages (and

subsequent related life cycle messages) the POI environment at the time that a
transaction took place.

Requirements
• DE 22 is required in intra-European transactions.
• DE 22 is required for offline Chip transactions when Approval Code (DE
38) is not available. In this situation, DE 22, subfield 7 must contain F to
identify the transaction as offline Chip.
• DE 22 is used in a clearing message to identify a message as a Clearing
Proximity Chip Online transaction. DE 22, subfields 1 and 7 contains A to
identify a Clearing Proximity Chip Online transaction.
• DE 22 is used in a clearing message to identify a message as a Clearing
Proximity Chip EMV transaction. DE 22, subfields 1 and 7 contains M to
identify a Clearing Proximity Chip EMV transaction.
• DE 22 is required when DE 55 is present. In this situation, DE 22, subfield
7 must contain F or C.
Subfields
This data element contains 12 subfields as specified in the following table:

1 1 Terminal Data: an-1 n/a
Card Data Input Capability
2 2 Terminal Data: Cardholder n-1 n/a
Authentication Capability
3 3 Terminal Data: n-1 n/a
Card Capture Capability
4 4 Terminal Operating Environment n-1 n/a
5 5 Cardholder Present Data an-1 n/a
6 6 Card Present Data n-1 n/a
7 7 Card Data: Input Mode an-1 n/a
8 8 Cardholder Authentication an-1 n/a
Method
9 9 Cardholder Authentication Entity n-1 n/a
10 10 Card Data Output Capability an-1 n/a
11 11 Terminal Data Output Capability n-1 n/a
12 12 PIN Capture Capability an-1 n/a

Each subfield consists of a one-character descriptor to document a specific

aspect of the POI environment. Valid codes for each of the 12 subfields are in
the following tables.
Note Whenever POI information is not available, acquirer processing systems must
use the appropriate “default” values to indicate that the data was not available
from the point of interaction.

Subfield 1: Terminal Data: Card Data Input Capability
Valid for
Valid for intra-European
intra-European MasterCard ATM,
MasterCard POS, Maestro ATM,
Maestro POS, and Maestro manual
Valid for MasterCard manual cash disbursement,
non–intra-European cash disbursement and Cirrus
Value Description messages messages messages
0 Unknown; data not available Yes Yes
1 Manual; no terminal Yes
2 Magnetic stripe reader Yes Yes Yes
capability
4 Optical character reader (OCR) Yes
capability
5 Integrated circuit card (ICC) Yes Yes Yes
capability
6 Key entry only capability Yes
A PAN auto-entry via contact Yes
less magnetic stripe
B Magnetic stripe reader and key Yes
entry capability
C Magnetic stripe reader, ICC, Yes
and key entry capability
D Magnetic stripe reader and ICC Yes
capability
E ICC and key entry capability Yes
M PAN auto-entry via contact Yes
less M/Chip
V Other capability Yes

Subfield 2: Terminal Data: Cardholder Authentication Capability
Valid for
0 No electronic authentication Yes
capability
1 PIN entry capability Yes Yes Yes
2 Electronic signature analysis Yes
capability
5 Electronic authentication Yes
capability is inoperative
6 Other Yes
Subfield 3: Terminal Data: Card Capture Capability
Valid for
0 No capture capability Yes
1 Card capture capability Yes Yes Yes
9 Unknown; data not available Yes Yes Yes

Subfield 4: Terminal Operating Environment
Valid for
0 No terminal used Yes
1 On card acceptor premises; Yes Yes Yes
attended terminal
2 On card acceptor premises; Yes Yes Yes
unattended terminal
3 Off card acceptor premises; Yes Yes
attended
4 Off card acceptor premises; Yes Yes Yes
unattended
5 On cardholder premises; Yes Yes
unattended
6 Off cardholder premises; Yes
unattended

Subfield 5: Cardholder Present Data
Valid for
0 Cardholder present Yes Yes Yes
1 Cardholder not present; Yes Yes
unspecified reason
2 Cardholder not present; mail Yes Yes
transaction
3 Cardholder not present; phone Yes Yes
transaction
standing (recurring)
transaction
electronic commerce

Subfield 6: Card Present Data
Valid for
0 Card not present Yes
1 Card present Yes Yes Yes
9 Unknown, data not available Yes Yes
Subfield 7: Card Data: Input Mode
Valid for
Maestro POS, and Maestro
MasterCard manual cash
Valid for manual cash disbursement,
non–intra-European disbursement and Cirrus
0 Unspecified; data not available Yes Yes
1 Manual input; no terminal Yes Yes
2 Magnetic stripe reader input Yes Yes Yes
6 Key entered input Yes Yes
A PAN auto-entry via contact less Yes
magnetic stripe
B Magnetic stripe reader input; Yes
track data captured and passed
unaltered
C Online Chip Yes Yes Yes
F Offline Chip Yes Yes Yes
M PAN auto-entry via contact less Yes
M/Chip

Valid for
S Electronic commerce, no Yes Yes
security, channel encrypted, or
SET without cardholder
certificate
T Electronic commerce, SET with Yes Yes
cardholder certificate
Subfield 8: Cardholder Authentication Method
Valid for
0 Not authenticated Yes
1 PIN Yes Yes Yes
2 Electronic signature analysis Yes
5 Manual signature verification Yes Yes
6 Other manual verification (such Yes
as a driver’s license number)
S Other systematic verification Yes

Subfield 9: Cardholder Authentication Entity
Valid for
MasterCard cash
0 Not authenticated Yes Yes
1 ICC Yes Yes Yes
2 Card acceptance device (CAD) Yes
3 Authorizing agent Yes Yes Yes
4 Merchant/card acceptor Yes Yes
5 Other Yes Yes
Subfield 10: Card Data Output Capability
Valid for
intra-European Valid for
MasterCard POS, intra-European
Maestro POS, and MasterCard ATM,
MasterCard Maestro ATM,
Valid for manual cash Maestro manual
non–intra-European disbursement cash disbursement,
Value Description messages messages and Cirrus messages
1 None Yes Yes
2 Magnetic stripe write Yes
3 ICC Yes Yes Yes
S Other Yes

Subfield 11: Terminal Data Output Capability
Valid for
intra-European
Valid for MasterCard ATM,
intra-European Maestro ATM,
MasterCard POS, Maestro manual
Maestro POS, and cash
Valid for MasterCard manual disbursement,
1 None Yes Yes
2 Printing capability only Yes Yes Yes
3 Display capability only Yes Yes Yes
4 Printing and display capability Yes Yes Yes
Subfield 12: PIN Capture Capability
Valid for
intra-European
0 No PIN capture capability Yes Yes
2 Reserved Yes
3 Reserved Yes
4 PIN capture capability four Yes Yes Yes
characters maximum
5 PIN capture capability five Yes Yes Yes
characters maximum
6 PIN capture capability six Yes Yes Yes
characters maximum
7 PIN capture capability seven Yes
characters maximum

Valid for
intra-European
8 PIN capture capability eight Yes
characters maximum
9 PIN capture capability nine Yes
characters maximum
A PIN capture capability 10 Yes
characters maximum
B PIN capture capability 11 Yes
characters maximum
C PIN capture capability 12 Yes
characters maximum

DE 23—Card Sequence Number
DE 23—Card Sequence Number

Card Sequence Number (DE 23) distinguishes among separate cards having the
same Primary Account Number (PAN) (DE 2).
Attributes
n-3
Length Field: None
Subfields: None
Usage
Usage
This data element is used to identify one of several cards issued under a single
PAN. Normally, when such cards are issued, the Card Sequence Number is
encoded on track 1 or track 2 of the card, and this information is automatically
captured during a magnetic stripe-read operation at a POI terminal.
Values
If present, DE 23 must contain a value in the 000–099 range.

DE 24—Function Code
Function Code (DE 24) indicates a message’s specific purpose.
Attributes
n-3
Length Field: None

Subfields: None
Usage
Usage
Data)/1644

Usage
Financial Detail Addendum (Payment Transactions)/1644 M • M
Data)/1644
Information)/1644
Requirements)/1644
Information)/1644

DE 24 is mandatory in all clearing system messages. Together with the MTI,

these data elements uniquely identify all transaction functions the clearing
system performs.
Values
The following table lists all Function Codes the clearing system supports. The
associated MTIs are also provided.

1240 282 Second Presentment (Partial)
1442 451 Arbitration Chargeback (Full) a
1442 453 First Chargeback (Partial)

1442 454 Arbitration Chargeback (Partial) a
1644 603 Retrieval Request a
1644 640 Currency Update

1644 680 File Currency Summary
1644 681 Settlement Position Total
1644 685 Financial Position Detail
1644 688 Settlement Position Detail
1644 693 Text Message
1644 695 File Trailer
1644 697 File Header
1644 699 File Reject
1740 700 Fee Collection (Member-Generated) b
1740 780 Fee Collection Return


1740 781 Fee Collection Resubmission
1740 782 Fee Collection Arbitration Return
1740 783 Fee Collection (Clearing System-Generated)
a Not supported for ATM transactions (DE 3 = 010000).
b Fee Collection (Member-Generated)/1740 messages includes manually submitted (non-
MasterCom) retrieval fulfillments..

DE 25—Message Reason Code

Message Reason Code (DE 25) provides the message receiver with the reason
that the message was sent.
Attributes
n-4
Length Field: None
Subfields: None
Usage
Usage

Usage
DE 25 identifies the specific reason that a transaction was initiated, such as the
reason for a Retrieval Request/1644, First Chargeback/1442, or Second
Presentment/1240.
Values
The tables on this and the following pages list all Message Reason Codes the
clearing system supports. The associated MTIs and Function Codes are also
provided to indicate the specific circumstances in which each Message Reason
Code is used.

First Presentment/1240 (Function Code = 200)
Valid for
non-intra-European Valid for
messages AND intra-European
MasterCard POS Valid for Maestro ATM,
Message and manual cash intra-European Maestro manual
Reason Message Reason disbursement Maestro POS cash disbursement,
Code Code Description messages messages and Cirrus messages
1400 Not previously authorized Yes Yes Yes
1401 Previously approved Yes Yes Yes
authorization—amount same
1402 Previously approved Yes Yes Yes
authorization—amount differs
Second Presentment (Full)/1240 (Function Code = 205) and Second Presentment (Partial)/1240
(Function Code = 282)
Valid for
2000 General; invalid chargeback. Yes Yes Yes
This Message Reason Code is
used when an ECCF record is
converted to IPM and the
message text format could not
determine the exact IPM Second
Presentment/1240 Message
Reason Code. This Message
Reason Code cannot be
submitted in IPM format.
2001 Invalid Acquirer Reference Data Yes Yes Yes
on chargeback; no
documentation required or
provided.
(ECCF S20 Documentation
Indicator field, value 2)

Valid for
2002 Non receipt of required Yes Yes Yes
documentation to support
chargeback.
2003 Correct transaction date provided. Yes Yes Yes
2004 Invalid Acquirer Reference Data Yes Yes Yes
on chargeback; documentation
was received.
2005 Correct card acceptor Yes Yes Yes
location/description provided.
2008 Issuer authorized transaction. Yes Yes Yes
2011 Credit previously issued. Yes Yes Yes
2700 Chargeback remedied—see Yes Yes Yes
corresponding documentation.
2701 Duplicate chargeback. Yes Yes Yes
2702 Past chargeback time limit. Yes Yes Yes
2703 Requested transaction document Yes Yes Yes
provided (requires hardship
variance).
2704 Invalid member message text. Yes Yes Yes
2705 Correct MCC provided. Yes Yes Yes
2706 Authorization advised suspicious. Yes Yes Yes
2707 No authorization request required Yes Yes Yes
nor attempted.
2708 Account was not listed on the Yes Yes Yes
applicable warning bulletin as of
the transaction date.

Valid for
2709 Documentation received was Yes Yes Yes
illegible.
2710 Documentation received was Yes Yes Yes
invalid/ incomplete.
2711 Missing documentation is being Yes* Yes* Yes*
supplied.
* Reserved for UK domestic use
(Corresponds to ECCF S20
Documentation Indicator,
value 5.)
2712 Other than required/requested Yes* Yes* Yes*
documentation provided.
value 6.)
2713 Invalid Chargeback Yes Yes Yes

First Chargeback (Full)/1442 (Function Code = 450) and First Chargeback (Partial)/1442 (Function
Code = 453)
Valid for
4515 Cardholder Denies Yes
4522 Authorization Declined Yes
4801 Requested transaction data was Yes Yes
not received.
4802 Requested information illegible or Yes Yes
missing.
4807 Warning bulletin. Yes
4808 Requested/required authorization Yes Yes
not obtained.
4809 Transaction Not Reconciled Yes Yes
(equates to ECCF DE 25 value
4753).
4812 Account number was not on file. Yes
4831 Transaction amount differs. Yes Yes
4834 Duplicate processing. Yes Yes Yes
4835 Card not valid or expired. Yes
4837 Fraudulent transaction; no Yes Yes
cardholder authorization.
4840 Fraudulent processing of Yes
transaction.
4841 Canceled recurring transaction. Yes
4842 Late presentment. Yes Yes Yes
4846 Correct transaction currency code Yes Yes
was not provided.
4847 Fraudulent transaction; exceeds Yes Yes
floor limit and not authorized.
4849 Questionable card acceptor Yes
activity.

Valid for
4850 Credit posted as purchase. Yes Yes
4853 Cardholder Dispute Defective/ Yes
Not as Described.
4854 Cardholder dispute not elsewhere Yes
classified (U.S. only).
4855 Non receipt of merchandise. Yes Yes
4857 Card-activated phone transaction Yes
4859 Services not rendered. Yes Yes
4860 Credit not processed. Yes Yes
4862 Counterfeit transaction; magnetic Yes
stripe POI fraud.
4863 Cardholder does not recognize– Yes* Yes* Yes*
Potential fraud
* Not valid for domestic UK
transactions.
4999 Domestic Chargeback Dispute Yes
Reserved for intra-European use

Arbitration Chargeback (Full)/1442 (Function Code = 451) and Arbitration Chargeback (Partial)/1442
Valid for
MasterCard POS Valid for Maestro ATM
4801 Requested transaction data was Yes N/A N/A
not received.
4802 Requested information illegible or Yes N/A N/A
missing.
4807 Warning bulletin. Yes N/A N/A
4808 Requested/required authorization Yes N/A N/A
not obtained.
4812 Account number was not on file. Yes N/A N/A
4831 Transaction amount differs. Yes N/A N/A
4834 Duplicate processing. Yes N/A N/A
4835 Card not valid or expired. Yes N/A N/A
4837 Fraudulent transaction; no Yes N/A N/A
cardholder authorization.
4840 Fraudulent processing of Yes N/A N/A
transaction.
4841 Canceled recurring transaction. Yes N/A N/A
4842 Late presentment. Yes N/A N/A
4846 Correct transaction currency code Yes N/A N/A
was not provided.
4847 Fraudulent transaction; exceeds Yes N/A N/A
floor limit and not authorized.
4849 Questionable card acceptor Yes N/A N/A
activity.
4850 Credit posted as purchase. Yes N/A N/A
4853 Cardholder Dispute Defective/Not Yes N/A N/A
as Described.
4854 Cardholder dispute not elsewhere Yes N/A N/A
classified (U.S. only).

Valid for
4855 Non-receipt of merchandise. Yes N/A N/A
4857 Card-activated phone transaction. Yes N/A N/A
4859 Services not rendered. Yes N/A N/A
4860 Credit not processed. Yes N/A N/A
4862 Counterfeit transaction; magnetic Yes N/A N/A
stripe POI fraud.
4863 Cardholder does not recognize– Yes * N/A N/A
Potential fraud
* Not valid for domestic UK
transactions.
4900 General; invalid Second Yes N/A N/A
Presentment/1240; Second
Presentment/1240 did not remedy
First Chargeback/1442; this
message reason code cannot be
submitted in IPM format.
4901 Required documentation not Yes N/A N/A
received to support prior Second
Presentment/1240.
(ECCF S20, Documentation
4902 Documentation received was Yes N/A N/A
illegible.
4903 Documentation received was Yes N/A N/A
invalid/ incomplete.
4905 Invalid Acquirer Reference Data Yes N/A N/A
in Second Presentment/1240;
documentation was received or
was not required.
ECCF S20, Documentation
4906 Missing documentation is being Yes* N/A N/A
supplied.

Valid for
value 5.)
4907 Other than required/requested Yes* N/A N/A
documentation provided.
* Reserved for UK domestic use.
Corresponds to ECCF S20
value 6.)
4908 Invalid Acquirer Reference Data Yes N/A N/A
in Second Presentment/1240;
documentation was received.
(ECCF S20, Documentation
4999 Domestic Chargeback Dispute Yes N/A N/A

Retrieval Request/1644 (Function Code = 603)
MTI Function Code Message Reason Code Message Reason Code Description
1644 603 6305 Cardholder does not agree with amount billed.
6321 Cardholder does not recognize transaction (for
example, does not recognize card acceptor
name, city, state, or date).
6322 Request Transaction Certificate for a chip
transaction.
6323 Cardholder needs information for personal
records (for example, for tax records or business
expense records).
6341 Fraud investigation.
6342 Potential chargeback or compliance
documentation is required.
Text Message/1644 (Function Code = 693)
1644 693 6801 Official MasterCard-to-member message.
6802 No data for this member and/or endpoint for this
delivery cycle.

Reconciliation Messages: File Currency Summary/1644 (Function Code = 680), Settlement Position
Total/1644 (Function Code = 681), Financial Position Detail/1644 (Function Code = 685), and
Settlement Position Detail/1644 (Function Code = 688)
1644 680, 681, 6861 File Acknowledgement—The clearing system
685, 688 generates after processing member outbound
activity.
1644 680, 681, 6862 File Notification—The clearing system generates
685, 688 to reconcile a member’s incoming activity.
1644 685 6863, 6864 Reserved for MasterCard internal use.
Fee Collection (Member-Generated)/1740 (Function Code = 700) and Fee Collection

Resubmission/1740 (Function Code = 781)
Valid for
non–intra- Valid for
European intra-European
messages AND Valid for Maestro ATM,
Message intra-European intra-European Maestro manual
Reason Message Reason MasterCard Maestro POS cash disbursement,
7600 Lost/stolen telex/phone fee; for Yes
collection of lost stolen report fee
and phone or telex costs incurred
for taking a lost or stolen card
report.
DE 3, s1 = 19, credit to sender
7601 Recovered card award fee; for Yes
collection of reward for a card
acceptor or financial institution
employee when a card has been
recovered.
7602 Emergency cash disbursement fee; Yes*
for collection of fees associated
with the handling of emergency
cash disbursements to cardholders.
*Not valid for intra-European
transactions

Valid for
7603 Compliance ruling settlement; for Yes Yes Yes
collection of a compliance ruling
settlement amount.
7604 Emergency card replacement fee; Yes*
with the Emergency Card
Replacement Service (ECR
Service).
transactions
7605 Warning bulletin handling fee— Yes
issuer originated; for settlement of
warning bulletin handling fees in
accordance with MasterCard
operating rules.
7606 Good faith acceptance settlement; Yes Yes Yes
for settlement of the amount of a
good faith acceptance.
DE 3, s1 = 29, debit to sender
7607 Collection letter handling fee; for Yes Yes Yes
settlement of the amount of a
collection letter acceptance.
7608 Telex authorization fee; for Yes
collection of fees associated with
an international telex
authorization.

Valid for
7610 Investigation fee; for fee collection Yes
when an investigation report has
been completed by an
investigating member on behalf of
the requesting member.
7611 Retrieval fee reversal; for issuer Yes Yes
use to reverse a retrieval request
fulfillment fee for documents
never received or invalid
documents.
DE 3, s1 = 19, credit to sender)
7612 Retrieval handling fee; for issuer Yes Yes
use to penalize an acquirer for
incorrect information verified by
the retrieval request document.
7614 Non-MasterCom fulfillment fee Yes Yes
settlement; for settlement of
retrieval request fulfillments not
processed through the MasterCom
system; credit to message
originator (acquirer).
This reason code is valid only for
Function Code 700 (acquirer to
issuer). An issuer that wants to
dispute these charges should
submit a 1740-780 Fee Collection
containing a DE 25 Message
Reason Code of either 7611 or
7612.

Valid for
acquirer originated; for settlement
of warning bulletin handling fees
in accordance with MasterCard
operating rules.
OR
Handling fee for second
presentment of reason codes 4812
and 4835 for chip transactions
where transaction certificate and
DE 55 are present in the clearing
message. Acquirer-originated.
7617 Adjustment for promotional Yes
transactions.
7618 Reversal of previously reimbursed Yes*
State Fuel Tax. Refer to the
MasterCard Government Card
Services Guide.
transactions
7619 Emergency card replacement Yes*
center, cash advance lockbox fee
* Not valid for intra-European
transactions.
7621 ATM Balance Inquiry Fee Yes Yes
(ECCF Message Reason Code field,
value 0701)

Valid for
7622 Handling Fee for Authorization Yes Yes Yes
Related Chargebacks (4807, 4808,
and 4847); for issuer use after
sending First Chargeback/1442 for
one of the specified authorization
related chargebacks.
and 4847); for acquirer use after
sending Second Presentment/1240,
which indicates that the
transaction was authorized.
sending Arbitration
Chargeback/1442
for one of the specified
authorization related chargebacks.
7625 PIN Management Service at ATM Yes Yes
“For intra-European use only”.
7626 Authorization reversal; for acquirer Yes
use to advise the issuer of an
authorization that needs to be
reversed.
DE 3, s1 = 19 (credit to sender)
7627 Failure to provide a merchant Yes
advice code in a progressive
handling fee.
DE 3 = 19 (credit to sender)

Valid for
7700 Intracurrency agreement Yes*
amounts in accordance with an
intracurrency agreement between
transaction originator and
transaction destination parties.
transactions
7750 Bilateral agreement settlement; for Yes Yes Yes
to settlement of amounts in
7779 accordance with a bilateral
agreement between transaction
originator and transaction
destination parties.
7780 Bilateral agreement settlement; for Yes Yes No
accordance with a bilateral
7781
7782 Bilateral agreement settlement; for Yes Yes Yes
7789

Valid for
7790 Bilateral agreement settlement; for Yes No No
7799

Fee Collection Return/1740 (Function Code = 780) and Fee Collection Arbitration Return/1740
Valid for Valid for

non-intra-European intra-European
Reason Message Reason Code MasterCard Maestro POS cash disbursement,
Code Description messages messages and Cirrus messages
7600 Lost/stolen telex/phone fee; for Yes
collection of lost stolen report fee
and phone or telex costs incurred
for taking a lost or stolen card
report.
7601 Recovered card award fee; for Yes
collection of reward for a card
acceptor or financial institution
employee when a card has been
recovered.
7602 Emergency cash disbursement Yes*
fee; for collection of fees
associated with the handling of
emergency cash disbursements to
cardholders.
transactions
7603 Compliance ruling settlement; for Yes Yes Yes
collection of a compliance ruling
settlement amount.
7604 Emergency card replacement fee; Yes*
with the Emergency Card
Replacement Service (ECR
Service).
transactions

Valid for Valid for

issuer originated; for settlement
operating rules.
7606 Good faith acceptance settlement; Yes Yes Yes
for settlement of the amount of a
good faith acceptance.
7607 Collection letter handling fee; for Yes Yes Yes
settlement of the amount of a
collection letter acceptance.
7608 Telex authorization fee; for Yes
collection of fees associated with
an international telex
authorization.
7610 Investigation fee; for fee Yes
collection when an investigation
report has been completed by an
investigating member on behalf
of the requesting member.
7611 Retrieval fee reversal; for issuer Yes Yes
use to reverse a retrieval request
fulfillment fee for documents
never received or invalid
documents.

Valid for Valid for

7612 Retrieval handling fee; for issuer Yes Yes
use to penalize an acquirer for
incorrect information verified by
the retrieval request document.
acquirer originated; for settlement
operating rules.
OR
Handling fee for second
presentment of reason codes
4812 and 4835 for chip
transactions where transaction
certificate and DE 55 are present
in the clearing message.
Acquirer-originated.
7617 Adjustment for promotional Yes
transactions.
7618 Reversal of previously reimbursed Yes*
State Fuel Tax. Refer to the
MasterCard Government Card
Services Guide.
transactions
7619 Emergency card replacement Yes*
center, cash advance lockbox fee
*Not valid for Intra-European
transactions.

Valid for Valid for

7621 ATM Balance Inquiry Fee Yes Yes
(ECCF Message Reason Code
field, value 0701)
sending First Chargeback/1442
for one of the specified
authorization related
chargebacks.
and 4847); for acquirer use after
sending Second Presentment
/1240, which indicates that the
transaction was authorized.
sending Arbitration Chargeback
/1442 for one of the specified
authorization related
chargebacks.
7625 PIN Management Service at ATM Yes Yes
DE 3, s1 = 19 credit to sender
” For Intra-European use only”.

Valid for Valid for

7626 Authorization reversal; for Yes
acquirer use to advise the issuer
of an authorization that needs to
be reversed.
7627 Failure to provide a merchant Yes
advice code in a progressive
handling fee.
7700 Intracurrency agreement Yes*
amounts in accordance with an
intracurrency agreement between
transaction originator and
transaction destination parties.
transactions
7750 Bilateral agreement settlement; Yes Yes Yes
to for settlement of amounts in
7780 Bilateral agreement settlement; Yes Yes No

Valid for Valid for

7782 Bilateral agreement settlement; Yes Yes Yes
7790 Bilateral agreement settlement; Yes No No
7950 Supporting documentation not Yes *
received.
transactions.
DE 3 = the same value as the
original Fee Collection.
7951 Missorted to the wrong member. Yes*
transactions.
7952 Missing message text. Yes*
transactions.

Valid for Valid for

7953 Fee charged exceeds amount Yes*
allowed.
transactions.
7954 Invalid fee amount. Yes*
transactions.
7955 Duplicate fee processing. Yes*
transactions.
7956 Unauthorized fee/charge; Yes*
receiving member did not
approve or agree to accept
fee/charge; applicable only if the
prior cycle Message Reason Code
was 7606 or 7607.
transactions.

Fee Collection (Clearing System-Generated)/1740 (Function Code = 783)
Valid for Valid for

messages AND/OR Valid for Maestro ATM,
7800 MCBS member settlement; for Yes*
collection or payment of such
things as member assessments,
processed through the
MasterCard Consolidated Billing
System (MCBS).
transactions
7801 MasterCard compliance case filing Yes Yes Yes
fee; for collection of a member
arbitration or compliance case
filing fee.
7802 Interchange compliance Yes
adjustment; for settlement of
financial amounts related to
interchange compliance.
7803 Interchange compliance Yes
adjustment reversal; for
settlement of financial amounts
related to the reversal of a
previous interchange compliance
adjustment.
7804 ATM transaction settlement; for Yes Yes Yes
settlement of daily ATM
transaction amounts.

Valid for Valid for

7805 ATM intracountry switch fee Yes*
settlement; for settlement of daily
ATM transaction intracountry
switch fees.
transactions
7806 ATM Network Information Yes*
Control System (NICS) switch fee
settlement; for settlement of MDS
NICS Switch Fees.
transactions
7807 ATM intracountry first chargeback Yes*
settlement; for settlement of daily
ATM transaction intracountry first
chargeback amounts
transactions
7811 Reimbursement of State Fuel Tax. Yes*
Refer to the MasterCard
Government Card Services Guide.
transactions
7812 Collection or return of collateral
for security arrangement. Yes*
transactions

Valid for Valid for

7813 Mexico IVA fees
Yes*
transactions
7814 Mexico IVA Fees
Yes*
transactions
7815 Mexico IVA Fees
Yes*
transactions
7820 Disaster Relief Fund
Yes*
transactions
7821 MCBS Emergency Borrowing
Collection Yes*
transactions
7822 Settlement Adjustment
Yes*
transactions

Valid for Valid for

7823 MDS Offline Debit Settlement
Yes*
transactions
MDS feed via Settlement Account
Management system (S.A.M.).
For MasterCard internal use only.

DE 26—Card Acceptor Business Code (MCC)

Card Acceptor Business Code (MCC) (DE 26) classifies the type of business
applicable to the card acceptor.
Attributes
n-4
Length Field: None
Subfields: None
Usage
Usage
Fee Collection (Handling Fees)/1740 O • C
This data element contains a four-digit card acceptor business code (MCC) that
identifies the card acceptor’s primary business.

Card acceptor business codes are required in MasterCard Financial transactions

to qualify transactions for specific interchange rates.
The four-position valid MasterCard card acceptor business code (MCC) that
most reasonably and fairly represents the card acceptor’s primary business
must be presented in DE 26. All MasterCard-recognized card acceptor
business codes (MCCs) are published in the Quick Reference Booklet. For
some transactions, MasterCard requires the use of a specific MCC. For
example, gaming transactions require the use of MCC 7995.
Values
Card Acceptor Business Codes comprise ISO standard business classification
codes, augmented with additional classification codes.
The codes for all MasterCard programs and services are in the MasterCard
Quick Reference Booklet, which is periodically updated and distributed to
member organizations.
Refer to the GCMS Reference Manual (chapter 7) for additional information

about MasterCard’s interchange programs and their requirements, including
valid DE 26 values for each interchange program, if applicable.

DE 30—Amounts, Original
Amounts, Original (DE 30) contains the “amount” data element values from the
First Presentment/1240 or Fee Collection (Member-Generated)/1740.
Attributes
n-24
Length Field: None
Subfields: 2
Usage
Usage

Usage
Fee Collection (Other than Retrieval Fee Billing/Handing Fees)/1740 O • C
DE 30 references the “amount” data elements (specifically, Amount,

Transaction [DE 4] and Amount, Reconciliation [DE 5]) of the First
Presentment/1240 or Fee Collection (Member-Generated)/1740.
DE 30 is required in Retrieval Request/1644, Retrieval Fulfillment (presented as

a Fee Collection message), First Chargeback/1442, Second Presentment/1240,
and Arbitration Chargeback/1442 messages to provide DE 4 of the First
Presentment/1240.
If present, DE 30 must be numeric.
In Fee Collection/1740 messages that are generated for reasons other than
retrieval fee billing, the sender may optionally provide DE 30 in a Fee
Collection Return/1740, Fee Collection Resubmission/1740, or Fee Collection
Arbitration Return/1740. In this case, DE 30 contains the DE 4 from the
original Fee Collection (Member-Generated)/1740.
Subfields
This data element consists of two subfields as indicated in the following table:

1 1–12 Original Amount, Transaction n-12 right
2 13–24 Original Amount, Reconciliation n-12 right

Subfield 1: Original Amount, Transaction

Subfield 1 must contain DE 4 from the First Presentment/1240 or Fee
Collection (Member-Generated)/1740.
Subfield 2: Original Amount, Reconciliation

Subfield 2 must contain all zeros.
Related PDSs
Whenever DE 30 is included in a message, the following PDSs must also be
included to identify the currency codes and exponents of the original amount
subfields:
• Currency Codes, Amounts, Original (PDS 0149)

DE 31—Acquirer Reference Data

Acquirer Reference Data (DE 31) is data an acquirer supplies in an acquirer-
originated message that may be required for an issuer to return to the acquirer
in a subsequent message.
Attributes
ans...99; LLVAR

Subfields: 5

The clearing system accepts a DE 31 length of up to 99 positions, but edits
only the first 23 positions. The clearing system forwards the entire contents of
DE 31.
Usage
Usage

Usage

Usage
s1 Interchange Rate Designator O • C
s2 Acquirer’s BIN O • C
s3 Julian Processing Date YDDD O • C
s4 Acquirer’s Sequence Number O • C
s5 Check Digit O • C
This data element contains the Acquirer Reference Data, which is mandatory in
all First Presentment/1240 and Second Presentment/1240 messages.
The issuer must return this data to the acquirer in subsequent related life cycle
messages, including Retrieval Request/1644, First Chargeback/1442, and
Arbitration Chargeback/1442 messages related to the First Presentment/1240.
DE 31 is also required in Fee Collection (Retrieval Fee Billing)/1740 messages.
If DE 31 is not provided in the Fee Collection/1740 message for the collection

of handling fees, the receiving member has the right to return the message.

Subfields
For MasterCard-branded, Cirrus, and Maestro transactions, DE 31 must be
formatted according to Corporation operating rules for Acquirer Reference
Data. The Acquirer Reference Data format consists of five subfields as
specified in the following table:

1 1–2 Interchange Rate Designator n-2 right
This field contains any numeric
value.
2 3–7 Acquirer’s BIN n-5 right
Must contain the acquirer’s
6-digit BIN with the BIN’s first
digit removed.
3 8–11 Julian Processing Date YDDD n-4 right
Contains the Julian processing
date the acquirer assigned to the
First Presentment/1240.
4 12–22 Acquirer’s Sequence Number n-11 right
Contains the sequence number
that the acquirer assigned to the
First Presentment/1240; numeric.
5 23 Check Digit n-1 right
Numeric; Luhn Formula
Modulus-10 algorithm
determines value on the
previous 22 positions.
Values
DE 31 cannot contain all low-values or all high-values.

DE 32—Acquiring Institution ID Code

Acquiring Institution ID Code (DE 32) identifies a transaction acquirer.
Attributes
n...11; LLVAR
Length Field: 2 positions value = 01–11

Data Field: variable length 1–11
Subfields: None
Usage
Usage
Financial Detail Addendum (Passenger Transport Detail—General O • C
Financial Detail Addendum (Passenger Transport Detail—Trip Leg O • C
Data)/1644
Financial Detail Addendum (Vehicle Rental Detail)/1644 O • C
Financial Detail Addendum (Lodging Summary)/1644 O • C
Financial Detail Addendum (Temporary Services)/1644 O • C
Financial Detail Addendum (Shipping/Courier Services)/1644 O • C
Financial Detail Addendum (Payment Transaction Detail)/1644 O • C
Financial Detail Addendum (Telephony Billing–Summary)/1644 O • C
Financial Detail Addendum (Telephony Billing–Detail)/1644 O • C
Financial Detail Addendum (Electronic Invoice–Transaction O • C
Data)/1644
Financial Detail Addendum (Electronic Invoice–Party O • C
Information)/1644

Usage
Financial Detail Addendum (Corporate Card Common Data O • C
Requirements)/1644
Financial Detail Addendum (Corporate Fleet Transaction O • C
Information)/1644
Financial Detail Addendum (Corporate Line Item Detail)/1644 O • C
Financial Detail Addendum (Generic Detail)/1644 O • C
Financial Position Detail/1644 • X C
Settlement Position Detail/1644 • X C
Settlement Position Total/1644 • X C
For clearing system transactions, this data element may identify the financial
institution that owns the merchant agreement.
DE 32 supplements the acquiring member ID (located in either Transaction

Originator Institution ID Code [DE 94] or Transaction Destination Institution ID
Code [DE 93]) by providing additional information about the agent bank
relationship. If the issuer returns DE 32 to the acquirer in subsequent
chargebacks, the acquirer may more easily determine the institution
responsible for the transaction.

Values
When present in clearing system messages, this data element contains a value
the acquirer assigns.
This value may be any proprietary numeric value as the acquirer determines.
When present, DE 32 must be numeric and cannot contain all zeros in First
Presentment/1240 or Financial Detail Addendum/1644 messages.
Additional Information
Refer to appendix A in this manual for more information about institution ID
codes and PDSs in clearing system messages.

DE 33—Forwarding Institution ID Code

Forwarding Institution ID Code (DE 33) identifies a message’s forwarding
institution. This is the institution in a transaction flow that sends a message
forward from the originating institution.
Attributes
n...11; LLVAR
Length Field: 2 positions value = 06–11

Subfields: None

The clearing system accepts a DE 33 length of 6–11 positions, but expects this
element to contain zeros in all but the last six positions. Only the last six
positions are passed along to the receiver of the message.
Usage
Usage
Data)/1644

Usage
Data)/1644
Information)/1644
Requirements)/1644
Information)/1644
DE 33 contains the clearing system member ID or Processor ID of the

processing facility that transmits a message.
Values
This data element must contain a valid member ID or Processor ID number.

DE 37—Retrieval Reference Number

Retrieval Reference Number (DE 37) is a transaction information document
reference number the card acceptor’s or designated agent’s system supplies.
DE 37 retains the transaction’s original source information. It assists in locating
that source information (or a copy).
Attributes
ans-12
Length Field: None
Subfields: None
Justification: None
Usage
Usage
This data element is for the exclusive use of card acceptor systems that retain
the original transaction source documentation such as electronic receipts,
paper receipts, imprinted tickets, and cardholder signature documents.
This data element’s primary purpose is to aid in retrieving original transaction

documentation if it is needed for some future action such as a retrieval request
or adjustment. For ATM or electronic POI terminal usage, DE 37 may contain
the transaction sequence number the terminal assigns.

Acquirer systems may assign a unique receipt or sales document identifier to

satisfy regulatory or legal requirements when the merchant performs source
document capture and truncation.
Values
If present, this element:
• Cannot contain all spaces or zeros in First Presentment/1240 messages.
• Cannot contain all spaces for all other messages (zeros are permitted in
non First Presentment/1240 messages.)

DE 38—Approval Code
Approval Code (DE 38) is a code the authorizing institution assigns indicating
approval.
Attributes
ans-6
Length Field: None
Subfields: None
Justification: Left
Usage
Usage
This data element transmits a card issuer’s “authorization code” for approved
transactions. The card acceptor may retain this code to verify that proper
authorization was received.
In First Presentment/1240 messages and related cardholder life cycle

transactions, this data element contains the actual approval response code the
issuer or its agent sends in response to an authorization request.

Values
This data element must contain an issuer’s authorization response code
formatted according to Corporation operating rules.
DE 38 is required to qualify for most incentive interchange rate programs.
If present, this data element must be left justified and cannot contain all
spaces, all low-values, or all high-values. In addition, it cannot contain
embedded spaces.
DE 38 must not be present if DE 22 is present and DE 22, subfield 7 = F,

indicating an offline chip transaction.

DE 40—Service Code
Service Code (DE 40) provides codes that increase issuers’ flexibility in
defining card acceptance parameters. These codes also provide acquirers with
the ability to interpret card acceptance preferences for all point-of-interaction
(POI) conditions.
The service code is a three digit value on the magnetic stripe (tracks 1 and 2)
and on the chip of a bankcard. The service code instructs the POI terminal
about conditions under which the card may be used.
Service codes contained on the magnetic stripe of a card must contain a 2 or 6

in the first position indicating a chip is present on the card. The service code
values of 2 or 6 can be used only on cards that are:
• MasterCard and Visa (EMV) compliant and
• cards in which the application on the magnetic stripe matches the
application on the chip.
Attributes
n-3
Length Field: none
Subfields: none
Justification: n/a
Usage
Usage

Values
DE 40 is required for the Asia/Pacific and South Asia/Middle East/Africa intra-
regional business service arrangements for transactions submitted for the Chip
Compliance interchange rate program (IRD 33 and 34).
If present, DE 40 must be numeric and contain a valid value for the IRD
submitted. When submitting DE 40, members must use the following
definitions and corresponding values to populate DE 40:
Definition Position 1 Position 2 Position 3

International Card 1
International Card—Integrated Circuit Card 2
National Use Only 5
National Use Only—Integrated Circuit Card 6
Private Label or Proprietary Card 7
Normal Authorization 0
Positive Online Authorization Required 2
PIN Required 0
Normal Cardholder Verification, No Restrictions 1
Normal Cardholder Verification—Goods and 2
services only at point of interaction (no cash
back)
ATM Only, PIN Required 3
PIN Required—Goods and services only at 5
point of interaction (no cash back)
Prompt for PIN if PIN Pad Present 6
Prompt for PIN if PIN Pad Present—Goods and 7
services only at point of service (no cash back)

DE 41—Card Acceptor Terminal ID

The Card Acceptor Terminal ID (DE 41) is a unique code identifying a terminal
at the card acceptor location.
Attributes
ans-8
Length Field: None
Subfields: None
Justification: Left
Usage
Usage

The Card Acceptor Terminal ID (DE 41) must contain a valid terminal ID, if
present. This data element contains the terminal ID that the card acceptor
assigns to a terminal device. Terminal IDs must be unique within each card
acceptor.
The terminal ID should be printed on all transaction receipts in ATM and POI
transactions in which the terminal is capable of generating customer receipts.
DE 41 is required in intra-European ATM First Presentment/1240 messages.
Values
Individual card acceptor, merchant, or acquirer clearing system organizations
assign terminal ID values.
If present, DE 41 must be left justified and cannot contain all low-values, all
high-values, all spaces or all zeros.

DE 42—Card Acceptor ID Code

Card Acceptor ID Code (DE 42) identifies the card acceptor.
Attributes
ans-15
Length Field: None
Subfields: None
Justification: Left
Usage
Usage
This data element uniquely identifies the card acceptor (merchant) for an
individual transaction.
DE 42 is required for all First Presentment/1240 transactions except reversal,

Collection Only, or ATM transactions.

DE 42 is required in First Chargeback/1442, Second Presentment/1240, and

Arbitration Chargeback/1442 transactions submitted for the U.S. region Merit I
or Convenience Purchases incentive interchange rate programs if DE 26 is
5542.
Values
The acquirer assigns DE 42 codes.
If present, DE 42 must be left justified and cannot contain all low-values, all
high-values, or all spaces or all zeros.

DE 43—Card Acceptor Name/Location

Card Acceptor Name/Location (DE 43) contains the card acceptor’s name and
location as known to the cardholder.
Attributes
ans...99; LLVAR
Subfields: 6

Subfield 1 of DE 43 must have a minimum length of 1 and a maximum length
of 22, excluding the backslash delimiter.
Subfield 3 of DE 43 must have a maximum length of 13, excluding the

backslash delimiter.
Usage
Usage
s2 Card Acceptor Street Address C • C
s5 Card Acceptor State, Province, or Region Code M • M

Usage
s5 Card Acceptor State, Province, or Region Code O • C

Usage
This data element provides the business name, street address, and other
location information about the card acceptor.
Subfields
DE 43 has six subfields. The first three are variable length, delimited by the
backslash (\) character. In the absence of data for any of the first three
subfields, the backslash is minimally required.
The last three subfields are fixed length. They must always be provided
whenever any DE 43 subfield is provided. At a minimum, spaces must be
provided in these last three subfields.

The following table shows the attribute and justification of each subfield:
Number Name Attribute Justification

1, 2, 3 Card Acceptor Name\Street Address\City\ ans...83 left
4 Card Acceptor Postal (ZIP) Code ans-10 left
5 Card Acceptor State, Province, or Region Code ans-3 left
6 Card Acceptor Country Code ans-3 left
Subfield 1: Card Acceptor Name

This field contains the card acceptor name, DBA name, or ATM owning
institution name.
The following are rules for this subfield:

• The Card Acceptor Name should contain the same name as imprinted or
printed on the transaction information document (TID)–the name most
recognizable to the cardholder.
• The Card Acceptor Name should contain the chain merchant name at the
beginning of this subfield. If a chain is listed in the 3000 range of card
acceptor business codes (MCCs), use the exact chain name. (A chain
merchant is one of multiple merchant outlets having the same ownership
and selling the same line of goods or services.)
• The Card Acceptor Name should contain a unique identifier at the end of
this subfield if the merchant has more than one property in a city.
• For airline transactions acquired outside the U.S. region, the abbreviated
carrier name and ticket number are required at the end of the Card
Acceptor Name subfield, if the member is provided with the airline/railway
ticket identifier.
• For lodging transactions, “No show” may be used at the end of the Card
Acceptor Name if appropriate.
• For in-flight commerce transactions, the service provider’s name and flight
identification must be provided in Card Acceptor Name. The flight
identification must be a recognizable identification of the airline. It is not
required to contain the airline’s alphabetic indicator as defined by the
International Air Transport Association (IATA).
• For telephone service transactions that are card-activated, the telephone
number dialed and duration of the telephone call must be provided in
Card Acceptor Name.

• In addition to the merchant’s DBA name, the following types of

transactions require the presence of the MasterCard-assigned ID code in
PDS 0043 Program Registration ID:
− Supermarket Base, Tier 1, Tier 2, and Tier 3
− Warehouse Club Base, Tier 1, Tier 2, and Tier 3
− Quick Payment Service (QPS)—may be provided in DE 43, subfield 1
instead of PDS 0043
− Service Industries
− Prestigious Hotel
− Payment Transaction
The following are requirements for this subfield:

• This subfield is mandatory and must contain data. It must end with a
backslash (\) delimiter and be left justified. It is variable-length 1–22
positions. It cannot contain all low-values, all high-values, or all spaces. It
cannot contain backslashes other than at the end of the subfield.
• For airline transactions acquired in the U.S. region, the abbreviated airline
name, not to exceed nine positions, must be provided in the Card Acceptor
Name for all First Presentment/1240, First Chargeback/1442, Second
Presentment/1240, and Arbitration Chargeback/1442 messages. If more
than nine positions are provided, anything after position 9 must be a space
up to the backslash delimiter. The ticket number and complete itinerary
data must be provided in the Financial Detail Addendum (Passenger
Transport Detail)/1644 messages.
Subfield 2: Card Acceptor Street Address

• The Card Acceptor Street Address is mandatory and cannot contain all
spaces for transactions submitted for the U.S. region Corporate Face-to-
Face (IRD 60), Corporate Large Ticket (IRD 62), Corporate Data Rate I (IRD
68), Corporate Data Rate II (IRD 67), Corporate Data Rate III (IRD 66),
Corporate T&E Rate I (IRD 76, 86), Corporate T&E Rate II (IRD 69), and
Corporate T&E Rate III (IRD 89) incentive interchange rate programs.
• This subfield is mandatory and cannot contain all spaces for non-remote
(face-to-face) transactions acquired in the Canada region and identified by:
− A value of 2 or 3 in Cardholder Present Data (DE 22, subfield 5), or
− A value of 5 in DE 22, subfield 5 and CT6 in Terminal Type (PDS 0023)

• If present, DE 43, subfield 2 must be left justified and cannot contain all
spaces, zeros, low-values, or high-values
• For all other transaction types, this subfield is optional.
• This subfield cannot contain backslashes other than at the end of the
subfield.
• Whether present or not, this subfield must end with a backslash (\)
delimiter.
Subfield 3: Card Acceptor City

The following are rules for this subfield:
• For vehicle rental transactions, Card Acceptor City should contain the
vehicle rental return location.
• For a card acceptor location that is not fixed (for example, aboard a train
or ship, a customer home, mail order, or telephone) a descriptive phrase
such as “sales ticket mailed” may be provided in Card Acceptor City in lieu
of the city.
• For non–face-to-face transactions originated and acquired in the United
States, a toll-free customer service phone number may be placed either in
the Card Acceptor City subfield or in PDS 0170 Card Acceptor Inquiry
Information.
• For in-flight commerce mailed purchases and gaming transactions, the
service provider’s customer service telephone number must be provided in
either Card Acceptor City or PDS 0170 Card Acceptor Inquiry Information.
It is not required to be a toll-free number. For other types of in-flight
commerce transactions, the customer service telephone number is optional.
• For electronic commerce transactions, either the card acceptor’s customer
service telephone number or Web site URL address must be provided. If
providing a Web site URL address, it should be placed in PDS 0175 Card
Acceptor URL. If providing a card acceptor’s customer service telephone
number, it may be placed in either DE 43, subfield 3 Card Acceptor City or
in PDS 0170 Card Acceptor Inquiry Information.
• For Payment transactions, processing code 28, the payment service
provider’s customer service telephone number or Web site URL address
should no longer be provided in DE 43, subfield 3. If providing Web site
URL address information, it should be submitted using PDS 0175, Card
Acceptor URL. If providing a card acceptor’s customer service telephone
number, it should be placed in PDS 0170 Card Acceptor Inquiry
Information, and should not be submitted in DE 43, subfield 3 Card
Acceptor City.


• The Card Acceptor City is optional for phone transactions. The phone
information for these transactions should be provided in Point-of-
Interaction (POI) Phone Data (PDS 0189), and may also optionally be
provided in DE 43, subfields 1 or 3.
• The Card Acceptor City is conditional for non–face-to-face and in-flight
commerce (IFC) transactions. The condition is that either this subfield or
Card Acceptor Inquiry Information (PDS 0170) must be present.
• For U.S. region corporate incentive interchange programs, this subfield
must be left justified and cannot contain all spaces or all zeros. This edit
applies to MasterCard settled original first presentment, original retail sale,
and unique transactions only.
• For all other transaction types, this subfield is mandatory and must contain
spaces or a valid state, province, or region code.
• This subfield cannot contain backslashes other than at the end of the
subfield.
• Whether present or not, this subfield must end with a backslash (\)
delimiter. It cannot contain all low-values or all high-values.
Subfield 4: Card Acceptor Postal (ZIP) Code

• This subfield is mandatory and cannot contain all spaces for non-remote
(face-to-face) transactions acquired in the Canada region and identified by:
− A value of 2 or 3 in Cardholder Present Data (DE 22, subfield 5), or
− A value of 5 in DE 22, subfield 5 and CT6 in Terminal Type (PDS 0023)
• This subfield must contain all spaces or a postal code and cannot contain
all low-values or all high-values.
• This subfield must be left justified and cannot contain all spaces, all zeros,
or all nines for transactions submitted for the U.S. region Corporate Face-
to-Face (IRD 60), Corporate Large Ticket (IRD 62), Corporate Data Rate I
(IRD 68), Corporate Data Rate II (IRD 67), Corporate Data Rate III (IRD
66), Corporate T&E Rate I (IRD 76, 86), Corporate T&E Rate II (IRD 69), or
Corporate T&E Rate III (IRD 89) incentive interchange rate programs.
• This subfield must be left justified and cannot contain all spaces for
transactions submitted for the International Corporate Purchasing Data Rate
II (IRD 67) incentive interchange rate program.

For U.S. card acceptors, acquirers should provide a five-digit or nine-digit ZIP
code. If the ZIP code is not available or not applicable, they should use
“space-fill” (not “zero-fill”).
Subfield 5: Card Acceptor State, Province, or Region Code

1. If DE 43, subfield 6 contains CAN, then subfield 5 must be present and
must always contain a valid Canadian Province code.
2. If DE 43, subfield 6 contains USA and the transaction is submitted for one
of the following U.S. region incentive interchange rate programs, then
subfield 5 must be present, must contain a valid U.S. State code, and
cannot contain all spaces, all zeros, or non-printable characters.
IRD Program Description

60 Corporate Face to Face
62 Corporate Large Ticket
68 Corporate Data Rate I
67 Corporate Data Rate II
76 and 86 Corporate T&E Rate I
66 Corporate Data Rate III
or
67 International Corporate Purchasing Data Rate II
3. If DE 43, subfield 6 contains a country code other than USA or CAN, and
the transaction is submitted for one of the interchange programs listed in
item 2 above, then subfield 5 must be present and cannot contain all
spaces. In this situation, members can populate subfield 5 with the same
country code as in DE 43, subfield 6. This scenario applies to any country
code other than USA or CAN, including the country codes of GUM, VIR, or
PRI.
4. If DE 43, subfield 6 contains USA and the transaction is submitted for an
interchange program that is not listed in item 2 above, then subfield 5 must
be present and must contain either all spaces or a valid U.S. State code.

5. If DE 43, subfield 6 contains a country code other than USA or CAN, and
the transaction is submitted for an interchange program that is not listed in
item 2 above, then subfield 5 must be present but its contents are not
edited. In this situation, members can populate subfield 5 with all spaces,
a province or region code, or the same three-position country code that is
in DE 43, subfield 6. This scenario applies to any country code other than
USA or CAN, including the country codes of GUM, VIR, or PRI.
6. When submitted for a First Presentment/1240 transaction, subfield 5 cannot
contain all low-values or high-values.
Subfield 6: Card Acceptor Country Code

This subfield cannot contain all spaces for original, non-credit First
Presentment/1240 messages. This subfield is required unless exempted by
Corporation rules.
This subfield must contain all spaces or a valid three-character ISO alphabetic
country code for the following:
• First Presentment/1240 (credits and reversals)
• First Chargebacks/1442 and Arbitration Chargebacks/1442
• Second Presentments/1240.
If the transaction took place within the United States, this subfield must
contain value “USA”.
If the transaction took place in the U.S. territories of Guam, Virgin Islands, or
Puerto Rico, this subfield must contain the appropriate three-position country
code of GUM, VIR, or PRI. It must not contain the value USA.
U.S. Acquired Airline Transaction Requirements

In MasterCard financial airline transactions that U.S. members acquire, the
following subfield restriction is required to ensure compatibility between the
clearing system and the IPM format: subfield 1 must be 1–22 positions long
with an abbreviated airline name in the first nine positions and spaces in any
remaining positions. The airline ticket number must not be provided in DE 43,
subfield 1 for U.S. acquired transactions.

Printing DE 43 Information on Cardholder Statements

Issuers may refer to appendix B in this manual for information regarding the
use of IPM data elements and PDSs for printing card acceptor description
information on statements.

DE 48—Additional Data
Additional Data (DE 48) contains one or more PDSs that may be required in a
message to provide additional clearing system-related, program-related, or
service data for which a specific ISO data element is not available.
Attributes
ans...999; LLLVAR

Subelements: see “Values”
Justification: Left
Usage
Usage
Data)/1644

Usage
Data)/1644
Information)/1644
Requirements)/1644
Information)/1644

This data element is a “carrier” data field for private data subelements (PDSs)
that supplement the original ISO 8583–1993 specification. These PDSs are
annotated with the prefix PDS (for example, PDS 0001 and PDS 0158) for
documentation purposes throughout this publication to distinguish them from
the ISO-standard data elements, which are simply numbered DE 1–DE 128.
Encoding of PDSs is always initiated in DE 48. If the resulting data space

required to contain all PDSs for a message exceeds the maximum length of
DE 48 (999 positions), the following data elements are employed, in sequential
order, to contain PDS data:
• DE 62 (Additional Data 2)
DE 62, DE 123, DE 124, and DE 125 each may contain a maximum of 999
positions each of encoded PDS information.
Values
This data element contains one or more PDSs in PDS-encoded format.
PDSs are formatted using a “tag-length-data” encoding procedure as follows:
Number Position(s) Description

1 1–4 First PDS tag (ID)
2 5–7 First PDS data length
3 8–999 First PDS data
Subfields 1–3 must be repeated as needed until all PDS data is presented or
the total length of subfields 1, 2, and 3 causes the total length of DE 48 to
exceed 999 positions.
Refer to the beginning of chapter 8 in this manual for additional information

about PDS definitions and an example.

DE 49—Currency Code, Transaction

Currency Code, Transaction (DE 49) defines the Amount, Transaction (DE 4)
currency.
Attributes
n-3
Length Field: None
Subfields: None
Justification: n/a
Usage
Usage

DE 49 is required in messages whenever DE 4 is present. It may also be used

in Reconciliation or Administrative messages to identify currencies referenced
in those messages.
ISO standard currency codes define the currency type, the country of origin,
and the implied decimal point location for the related amount data as defined
in the ISO 4217 specification.
Values
ISO standard numeric currency codes must be used.
This data element may contain the global base currency code in an
acknowledgement 1644–680 or 1644–685 reconciliation message if the
processed file contained only non-financial messages, depending on member
Reconciliation category options.

The following data element and PDS are required whenever DE 49 is present:
• DE 4

DE 50—Currency Code, Reconciliation

Currency Code, Reconciliation (DE 50) defines the Amount, Reconciliation
(DE 5) currency.
Attributes
n-3
Length Field: None
Subfields: None
Justification: n/a
Usage
Usage
First Chargeback/1442 and Arbitration Chargeback/1442 C X C
Second Presentment/1240 C X C
Fee Collection (Retrieval Fee Billing)/1740 C X C
Fee Collection (Handling Fees)/1740 C X C
Fee Collection (Other than Retrieval Fee Billing/Handling Fees)/1740 C X C

DE 50 is required in messages whenever DE 5 is present. If the transaction

originator provides DE 5, it also must provide DE 50. The transaction
originator should provide this only for a bilateral transaction, otherwise GCMS
will override. If the clearing system provides DE 5, it will provide DE 50. It
may also be used in Reconciliation or Administrative messages to identify
currencies referenced in those messages.
Values
This data element may contain the global base currency code in an
acknowledgement 1644–685 reconciliation message if the processed file
contained only non-financial messages.

The following data element and PDS are in a message whenever DE 50 is
present:
• DE 5

DE 51—Currency Code, Cardholder Billing

Currency Code, Cardholder Billing (DE 51) defines the Amount, Cardholder
Billing (DE 6) currency.
Attributes
n-3
Length Field: None
Subfields: None
Justification: n/a
Usage
Usage
DE 51 is required in messages whenever DE 6 is present. If the transaction

originator provides DE 6, it also must provide DE 51. The transaction
originator should provide this only for a bilateral transaction, otherwise GCMS
will override. If the clearing system provides DE 6, it will provide DE 51.

Values

The following data element and PDS are in a message whenever DE 51 is
present:
• DE 6

DE 55—Integrated Circuit Card (ICC) System-Related Data

Integrated Circuit Card (ICC) System Related Data (DE 55) contains data related
to ICC systems.
Attributes
b…255; LLLVAR
Subelements: see “Values”
Justification: n/a
Usage
Usage
If present, DE 55 cannot contain all spaces, all zeros, all low-values, or all
high-values.

Values
DE 55 contains chip data formatted in accordance with the Europay,
MasterCard, and Visa (EMV) chip specification.
If present, DE 55 cannot contain all spaces, zeros, low-values, or high-values.
DE 55 data is presented in binary format and contains the data used locally by
a card’s chip at a chip-capable terminal. In a First Presentment/1240, the
acquirer should not modify this data, but instead pass it unaltered to the issuer.
Chip data in DE 55 consists of a series of subfields in a “tag-length-data”

format, similar to the presentation of PDSs in Additional Data (DE 48). The
following table shows the layout:

1 1 or 1–2 First chip subelement tag (ID)
2 2 or 3 First chip subelement data length
3 3-xxx or 4–xxx First chip subelement data (variable length)
Subfields 1–3 must be repeated as needed until all chip subelements are
presented. The length of the “tag” subfield is either 1 or 2, depending on the
definition of the tag in EMV. The length of the “data length” subfield is always
one in DE 55.
Although DE 55 is currently optional in most IPM messages, if it is presented,

there are certain mandatory subelements. The following chart lists all the
possible subelements defined for DE 55, their lengths, and their requirements.
This subelement data may be presented in any order in DE 55, but they must
always be presented with their associated “tag” and “length.” The following
table shows the subelements and associated information:

Each Total
Subfield Subelement
Subelement Description Subfield Tag Value a Length b Length c
Application Cryptogram (AC) tag 9F26 2 11
length 1
data 8
Cryptogram Information Data tag 9F27 2 4
length 1
data 1
Issuer Application Data (IAD) tag 9F10 2 10–35
length 1
data 7–32
Unpredictable Number tag 9F37 2 7
length 1
data 4
Application Transaction tag 9F36 2 5
Counter length 1
data 2
Terminal Verification Result tag 95 1 7
(TVR) length 1
data 5
Transaction Date tag 9A 1 5
length 1
data 3
Transaction Type tag 9C 1 3
length 1
data 1
Transaction Amount tag 9F02 2 9
length 1
data 6
Transaction Currency Code tag 5F2A 2 5
length 1
data 2

Each Total
Subfield Subelement
Subelement Description Subfield Tag Value a Length b Length c
Application Interchange tag 82 1 4
Profile
length 1
data 2
Terminal Country Code tag 9F1A 2 5
length 1
data 2
Amount, Other tag 9F03 2 9
length 1
data 6
If the card populates the six bytes of data in Amount, Other, the acquirer must pass all
six bytes.
a The hexadecimal representation is given here. Every two positions of hexadecimal data is
one byte of binary data.
b Lengths are in binary format.
c “Total Subelement Length” is the sum of that subelement’s tag, length, and data subfields.
Optional Subelements
Members may send the following subelements:
Each Total
Subfield Subelement
Subelement Description Subfield Tag Value Length Length
Cardholder Verification tag 9F34 2 6
Method (CVM) Results length 1
data 3
Terminal Capabilities tag 9F33 2 6
length 1
data 3
Terminal Type tag 9F35 2 4
length 1
data 1

Each Total
Subfield Subelement
Interface Device (IFD) Serial tag 9F1E 2 11
Number length 1
data 8
Transaction Category Code tag 9F53 2 4
length 1
data 1
Dedicated File Name tag 84 1 7–18
length 1
data 5–16
Application Version Number tag 9F09 2 5
length 1
data 2
Transaction Sequence tag 9F41 2 5–7
Counter length 1
data 2–4
Data from Authorization Request Response/0110

The following subelement should be present in the clearing message if it was
present in the Authorization Request Response/0110 message:
Each Total
Subfield Subelement
Issuer Authentication Data tag 91 1 10–18
(Provides data to be length 1
transmitted to the card for
data 8–16
issuer authentication.)

Optional Subelements from an Authorization Request

Response/0110
Members may send the following subelements in the clearing message if they
were present in Authorization Request Response/0110 messages.
Each Total
Subfield Subelement
Issuer Script Template 1 and 2 tag 71 and 72 1 3–130
(Allows the issuer to provide a length 1
command for transmission to
data 1–128
the card; present if issuer sends
commands to ICC; acquirer
network must support a
minimum of 25 bytes and a
maximum of 130 bytes.)

DE 62—Additional Data 2
Additional Data 2 (DE 62) contains one or more PDSs that may be required in
a message to provide additional clearing system-related, program-related, or
service-related data for which a specific ISO data element is not available.
Attributes
ans...999; LLLVAR

Subelements: See “Values”
Justification: Left
Usage
Usage
Financial Detail Addendum (Passenger Transport Detail—General C X C
Financial Detail Addendum (Passenger Transport Detail—Trip Leg C X C
Data)/1644
Financial Detail Addendum (Vehicle Rental Detail)/1644 C X C
Financial Detail Addendum (Lodging Summary)/1644 C X C
Financial Detail Addendum (Temporary Services)/1644 C X C
Financial Detail Addendum (Shipping/Courier Services)/1644 C X C
Financial Detail Addendum (Payment Transaction Detail)/1644 C X C
Financial Detail Addendum (Telephony Billing–Summary)/1644 C X C
Financial Detail Addendum (Telephony Billing–Detail)/1644 C X C
Financial Detail Addendum (Electronic Invoice–Transaction C X C
Data)/1644

Usage
Financial Detail Addendum (Electronic Invoice–Party C X C
Information)/1644
Financial Detail Addendum (Corporate Card Common Data C X C
Requirements)/1644
Financial Detail Addendum (Corporate Fleet Transaction C X C
Information)/1644
Financial Detail Addendum (Corporate Line Item Detail)/1644 C X C
Financial Detail Addendum (Generic Detail)/1644 C X C
File Currency Summary/1644 • X C
Retrieval Request/1644 C X C
This data element is a “carrier” data field for PDSs that supplement the ISO
8583–1993 specification.
Encoding of PDSs is always initiated in Additional Data (DE 48). If the

resulting data length required to contain all PDSs exceeds the maximum length
of DE 48 (999 positions), the following ISO data elements are employed, in
sequential order, to contain the remaining PDS data:
• DE 62
• Additional Data 3 (DE 123)

DE 62, DE 123, DE 124, or DE 125 each may contain a maximum of 999

positions each of encoded PDS information.
DE 62 is present in an IPM message only if DE 48 cannot contain the full

length of encoded PDSs.
If both DE 48 and DE 62 are present in the message, DE 48 should contain as

many complete PDSs (tag+length+data) as fits into 999 bytes. The remaining
complete PDSs should be presented in DE 62, then DE 123, then DE 124, and
finally DE 125 as needed.
Members must not split a PDS between DE 48 and DE 62. If an entire PDS
coding scheme (tag-length-data) causes DE 48 to exceed 999 positions, the
entire PDS coding scheme (tag-length-data) must be presented in DE 62
instead. Therefore, the total length of DE 48 may be less than 999 positions,
with DE 62 containing additional PDS data.
Values
When present, this data element contains one or more PDSs in PDS-encoded
format.
PDS data is formatted using a “tag-length-data” encoding procedure as follows:



DE 63—Transaction Life Cycle ID

Transaction Life Cycle ID (DE 63) contains subfields that allow for transaction
life cycle control. All life cycle messages such as Authorizations, Financials,
Reversals, Retrievals, Fulfillments, and Chargebacks are linked with the Life
Cycle Support Indicator and Trace ID subfields.
Attributes
ans...999; LLLVAR
Subfields: 2

The clearing system accepts a DE 63 length of up to 999 positions, but edits
only the first 16 positions. The clearing system forwards the entire contents of
DE 63 to the receiver.
Note Members should enter data only in the first 16 positions of this data element.
Positions 17–24 are reserved for future use but will be edited if data is
provided, and may result in the transaction being rejected.
Usage

Usage
s2 Trace ID C • C
s4 Transaction Sequence Number O • C
s5 Transaction Total O • C
Financial Detail Addendum (Passenger Transport Detail—General C • C
s2 Trace ID C • C
Financial Detail Addendum (Passenger Transport Detail—Trip Leg C • C
Data)/1644
s2 Trace ID C • C
Financial Detail Addendum (Vehicle Rental Detail)/1644 C • C
s2 Trace ID C • C

Usage
Financial Detail Addendum (Lodging Summary)/1644 C • C
s2 Trace ID C • C
Financial Detail Addendum (Temporary Services)/1644 C • C
s2 Trace ID C • C
Financial Detail Addendum (Shipping/Courier Services)/1644 C • C
s2 Trace ID C • C
Financial Detail Addendum (Payment Transaction Detail)/1644 C • C
s2 Trace ID C • C

Usage
Financial Detail Addendum (Telephony Billing–Summary)/1644 C • C
s2 Trace ID C • C
Financial Detail Addendum (Telephony Billing–Detail)/1644 C • C
s2 Trace ID C • C
Financial Detail Addendum (Electronic Invoice–Transaction C • C
Data)/1644
s2 Trace ID C • C
Financial Detail Addendum (Electronic Invoice–Party C • C
Information)/1644
s2 Trace ID C • C

Usage
Financial Detail Addendum (Corporate Card Common Data C • C
Requirements)/1644
s2 Trace ID C • C
Financial Detail Addendum (Corporate Fleet Transaction C • C
Information)/1644
s2 Trace ID C • C
Financial Detail Addendum (Corporate Line Item Detail)/1644 C • C
s2 Trace ID C • C
Financial Detail Addendum (Generic Detail)/1644 C • C
s2 Trace ID C • C

Usage
s2 Trace ID O • C
s2 Trace ID O • C
s2 Trace ID O • C
s2 Trace ID O • C

Usage
s2 Trace ID O • C
s2 Trace ID O • C
DE 63 data may be assigned at the time that the first message in the transaction
life cycle is presented, usually at authorization. This data element currently
consists of two subfields. Three additional subfields will be defined in the
future. The subfields are as follows:
• Life Cycle Support Indicator

• Trace ID
• Validation Code
• Life Cycle Transaction Sequence Number
• Life Cycle Transaction Total
Life cycle messages such as Authorization, First Presentment/1240, Retrieval

Request/1644, First Chargeback/1442, Second Presentment/1240, and
Arbitration Chargeback/1442 messages are linked with a Life Cycle Support
Indicator and Trace ID.
For transactions in which a single authorization could result in multiple First

Presentment/1240 messages (such as airline and railway transactions), Life
Cycle Transaction Sequence Number and Life Cycle Transaction Total may also
be provided.

The Validation Code is not currently supported and must be space-filled if

subfields 4 and 5 are present.
DE 63 should be retained throughout all subsequent messages in the life cycle.
Subfields
DE 63 includes five subfields as specified in the following table:

1 1 Life Cycle Support Indicator ans-1 left
2 2–16 Trace ID ans-15 left
3 17–20 Validation Code an-4 left
4 21–22 Life Cycle Transaction Sequence an-2 left
Number
5 23–24 Life Cycle Transaction Total an-2 left
Subfield 1: Life Cycle Support Indicator

Currently, the Life Cycle Support Indicator subfield always contains a space.
The clearing system will, in the future assign Life Cycle Support Indicator
values. The values indicate the point in the transaction’s life cycle at which
the Trace ID was assigned.
If the Trace ID was assigned at authorization, the message originator may

provide a space in the Life Cycle Support Indicator subfield. In the future, if
the Trace ID was assigned to the First Presentment/1240 (or later), the clearing
system will populate the Life Cycle Support Indicator subfield with the
appropriate value.

Subfield 1 is required whenever Subfield 2 is present. Valid Life Cycle Support

Indicators are in the following table:
Value Description
space Trace ID assigned to Authorization message.
2 Trace ID assigned to First Presentment/1240.
3 Trace ID assigned to Retrieval Request/1644.
4 Trace ID assigned to First Chargeback/1442.
5 Trace ID assigned to Second Presentment/1240.
6 Trace ID assigned to Arbitration Chargeback/1442.
7 Trace ID assigned to Fee Collection (Member-Generated)/1740 and Fee
Collection (Clearing System-Generated)/1740.
8 Trace ID assigned to Fee Collection Return/1740.
A Trace ID assigned to Fee Collection Resubmission/1740.
B Trace ID assigned to Fee Collection Arbitration Return/1740.
R Trace ID assigned to a reversal transaction that was submitted without
the original Transaction Life Cycle Indicator.
Subfield 2: Trace ID
The Trace ID is intended to uniquely identify a transaction through its full life
cycle. Currently MasterCard assigns a Trace ID to any transaction authorized
via the Banknet® telecommunications network.
The Trace ID consists of the Banknet Reference Number (nine positions)

followed by the Banknet Date (four positions—MMDD), followed by two
spaces. In the future, the Trace ID will be required in all life cycle messages
following its assignment. (This does not apply to ATM transactions submitted
by or destined for the MasterCard Debit Switch [MDS]).
Subfield 2 is required if the associated First Presentment/1240 is submitted for

any U.S. region consumer or corporate incentive interchange rate programs,
unless the transaction is a credit, ATM cash disbursement, manual cash
disbursement, reversal, Collection Only, or bilaterally settled transaction.

It also is required for the following International incentive interchange rate

programs:
• U.S. acquired International Consumer IEI (73, 83)
• U.S. acquired International Merchant UCAF (24)
• U.S. acquired International Full UCAF (79)
• U.S. acquired International Corporate incentive interchange programs
Subfield 3: Validation Code

The clearing system calculates the Validation Code using an algorithm against
key transaction data elements that are common to Authorization and Financial
messages.
Subfields 4 and 5: Life Cycle Transaction Sequence Number and

Life Cycle Transaction Total
The Life Cycle Transaction Sequence Number will be used in the future to
uniquely identify transactions in those industries that permit multiple clearing
transactions to be generated from a single authorization. Specifically, the
airline and railway industries permit a ticket agent to obtain a single
authorization when a single card is used to pay for multiple tickets at the same
time. The acquirer then submits multiple First Presentment/1240 messages,
one for each ticket, all containing the same Trace ID as the authorization
system provides.
The Life Cycle Transaction Total will be used to indicate the total number of
airline or railway First Presentment/1240 messages that occur as the result of a
single authorization. For airline and railway transactions, both the Life Cycle
Transaction Sequence Number and the Life Cycle Transaction Total may be
greater than zero.
For transactions other than airline and railway, these two subfields should not
be presented.

To uniquely identify each airline or railway First Presentment/1240 message,

the acquirer may assign and provide both the Life Cycle Transaction Sequence
Number and Life Cycle Transaction Total. For example, if one authorization is
obtained for three airline tickets, the Life Cycle Support Indicator, Trace ID,
Life Cycle Transaction Sequence Number, and Life Cycle Transaction Total
contain the following:
First Life Cycle Life Cycle Life Cycle

Presentment/ Support Transaction Transaction
1240 Indicator Trace ID Sequence Number Total
First 1 MCC1234560930 01 03
Second 1 MCC1234560930 02 03
Third 1 MCC1234560930 03 03
For airline and railway transactions, The Life Cycle Transaction Sequence
Number and Life Cycle Transaction Total may each contain a value in the
range 00–99.
For industries other than airline and railway, the Life Cycle Transaction
Sequence Number and Life Cycle Transaction Total should not be present. If
they are present, they must contain zeros.
In Retrieval Request/1644 Messages, First Chargeback/1442 Messages,

Second Presentment/1240 Messages, and Arbitration Chargeback/1442
Messages
If a Trace ID was assigned in a previous message (such as the authorization),

the following subfields may be in DE 63 of the related Retrieval Request/1644,
Retrieval Fulfillment (presented via a Fee Collection message), First
Chargeback/1442, Second Presentment/1240, and/or Arbitration
Chargeback/1442:
• Trace ID
• Life Cycle Transaction Sequence Number and Life Cycle Transaction Total
(must contain zeros unless airline or railway transaction)
If a Trace ID was not assigned in a previous message, DE 63 should be

omitted from the current message.

In Fee Collections (Member-Generated)/1740 and Fee Collections

(Clearing System-Generated)/1740
If these original Fee Collection messages relate to a Financial message that

contains a Trace ID, the Fee Collection (Member-Generated)/1740 or Fee
Collection (Clearing System-Generated)/1740 may contain the Life Cycle
Support Indicator, Trace ID, and Life Cycle Transaction Sequence Number of
the related Financial message.
Otherwise, the Fee Collection (Member-Generated)/1740 or Fee Collection

(Clearing System-Generated)/1740 originator should omit DE 63 from the
message.
In Fee Collection Return/1740 Messages, Fee Collection

Resubmission/1740 Messages, and Fee Collection Arbitration Return/1740
Messages
These returned Fee Collection/1740 messages may contain DE 63 with the

following subfields:
• Trace ID
• These subfields should contain the values assigned to the original Fee
Collection (Member-Generated)/1740 or Fee Collection (Clearing System-
Generated)/1740.
Values
If present, DE 63 cannot contain all low-values, or all high-values.

DE 71—Message Number
The transaction originator assigns the Message Number (DE 71) to data
messages in a file. DE 71 monitors the integrity and continuity of the files
being exchanged.
Attributes
n-8
Length Field: None

Subfields: None
Usage
Usage
Data)/1644

Usage
Data)/1644
Information)/1644
Requirements)/1644
Information)/1644

This data element provides the recipient of a file with a readily available
means to verify it receives all data messages in the file.
Values
The first message in a data file (the File Header/1644) must have the Message
Number initialized to 00000001. For each subsequent message in the file, this
data element value must be greater than the value in the previously accepted
message.
When the clearing system returns a message because it was rejected, the
rejected message will immediately follow its related Message Exception/1644
or File Reject Message. If the IPM Pre-edit application rejects the message, it
modifies the DE 71 value of the rejected message so that it is in sequence with
the other messages in the file. If GCMS rejects the message, it retains the
DE 71 value that the sender originally provided.

DE 72—Data Record
DE 72—Data Record
Data Record (DE 72) contains message text data, file update data, or other
information as specified in individual IPM messages.
Attributes
ans...999; LLLVAR
Subfields: None
Justification: Left
Usage
Usage
Fee Collection (Other than Retrieval Fee Billing/Handling Fees)/1740 C • C
Message Exception/1644 and File Reject/1644 • X C

DE 72—Data Record
This data element is a variable-length data field that may be used for
transmitting file message data or character string data in various message types.
DE 72 must be a maximum of 100 positions in First Chargeback/1442, Second

Presentment/1442, Arbitration Chargeback/1442, and Fee Collection/1740
messages.
DE 72 may be up to 999 positions in Administrative messages that the clearing

system generates.
Values
For First Chargeback/1442, Second Presentment/1240, and Arbitration
Chargeback/1422 messages, refer to the MasterCard Chargeback Guide for
specific DE 72 requirements based on the value in Message Reason Code
(DE 25). The clearing system does not edit to require DE 72. However, if it is
not provided for a given Message Reason Code (DE 25) as specified in the
MasterCard Chargeback Guide, the receiving member has the right to return
the message. For Fee Collection Other/1740 messages, refer to the GCMS
Reference Manual for specific DE 72 requirements based on DE 25. The
clearing system does not edit for specific values in DE 72. However, if it is not
provided for a given DE 25 Message Reason Code as specified in the GCMS
Reference Manual, the receiving member has the right to return the message.
If present, DE 72 cannot contain all zeros, all spaces, all low-values, or all
high-values.

DE 73—Date, Action
DE 73—Date, Action
Date, Action (DE 73) specifies a future action date or a specific date such as a
transaction date.
Attributes
n-6; YYMMDD
Length Field: None
Subfields: None
Justification: n/a
Usage
Usage
Fee Collection (Other than Retrieval Fee Billing/Handling Fees)/1740 C • C
In Fee Collection messages, this data element identifies a reference date related
to the Fee Collection Message Reason Code.
For Fee Collection Other/1740 messages, refer to the GCMS Reference Manual
for specific DE 73 requirements based on DE25. The clearing system does not
edit to require DE 73. However, if it is not provided for a given DE 25
Message Reason Code as specified in the GCMS Reference Manual, the
receiving member has the right to return the message.
Values
The data in DE 73 must consist of all zeros or a valid year (YY), month (MM),
and day (DD). For Fee Collection (Retrieval Fee Billing)/1740 messages, the
DD portion may be zeros.

DE 93—Transaction Destination Institution ID Code

Transaction Destination Institution ID Code (DE 93) identifies the transaction
destination institution.
Attributes
n...11; LLVAR
Length Field: 2 positions, value 06–11
Subfields: None

The clearing system accepts a DE 93 length of 6-11 positions, but expects this
Usage
Usage
First Presentment/1240 C X M
Financial Detail Addendum (Passenger Transport Detail—General • X M
Financial Detail Addendum (Passenger Transport Detail—Trip Leg • X M
Data)/1644
Financial Detail Addendum (Vehicle Rental Detail)/1644 • X M
Financial Detail Addendum (Lodging Summary)/1644 • X M
Financial Detail Addendum (Temporary Services)/1644 • X M
Financial Detail Addendum (Shipping/Courier Services)/1644 • X M

Usage
Financial Detail Addendum (Payment Transaction Detail)/1644 • X M
Financial Detail Addendum (Telephony Billing–Summary)/1644 • X M
Financial Detail Addendum (Telephony Billing–Detail)/1644 • X M
Financial Detail Addendum (Electronic Invoice–Transaction • X M
Data)/1644
Financial Detail Addendum (Electronic Invoice–Party • X M
Information)/1644
Financial Detail Addendum (Corporate Card Common Data • X M
Requirements)/1644
Financial Detail Addendum (Corporate Fleet Transaction • X M
Information)/1644
Financial Detail Addendum (Corporate Line Item Detail)/1644 • X M
Financial Detail Addendum (Generic Detail)/1644 • X M
First Chargeback/1442 and Arbitration Chargeback/1442 C X M
Second Presentment/1240 C X M
Retrieval Request/1644 • X M

This data element identifies the transaction destination institution that has
financial responsibility and liability for the transaction.
For MasterCard transactions, this is the institution that has an agreement with
MasterCard as being a principal member and has the financial authority to
process MasterCard transactions as an acquirer or issuer.
This data element is required for ATM chargeback and second presentment
transactions (DE 3, s1 = 01) submitted by the MasterCard Debit Switch (MDS).
If the clearing system does not receive this data element from a member in an
originating message, it may perform automated routing services (based on
other data elements such as the Primary Account Number [PAN] [DE 2]) and
inserts and passes to the receiving institution the proper value for DE 93.
Values
When present in a message, this data element must contain a valid member
ID.

DE 94—Transaction Originator Institution ID Code

Transaction Originator Institution ID Code (DE 94) identifies the transaction
originator institution.
Attributes
n...11; LLVAR
Length Field: 2 positions, value 06–11
Subfields: None

The clearing system accepts a DE 94 length of 6-11 positions, but expects this
Usage
Usage
Data)/1644

Usage
Data)/1644
Information)/1644
Requirements)/1644
Information)/1644
This data element identifies the transaction originator institution that has
financial responsibility and liability for the transaction.
For MasterCard transactions, this is the institution that has an agreement with
MasterCard as being a principal member, and has the financial authority to
process MasterCard transactions as an acquirer or issuer.

If the clearing system does not receive this data element from a member in an
originating message, it rejects the message.
In First Presentment/1240, Second Presentment/1240, Financial Detail

Addendum/1644, and Fee Collection (Retrieval Fee Billing)/1740 messages, the
member ID cannot be designated as an issuer-only member ID.
In First Chargeback/1442 and Arbitration Chargeback/1442 messages, the

member ID cannot be designated as an acquirer-only member ID.
Values
When present in a message, this data element must contain a valid member
ID. The member ID must either be equal to the member processor ID in
subfield 3 of PDS 0105 File ID in the File Header/1644-697 message, or be
processed by that member/processor ID.
Refer to appendix A of this manual for more information about institution ID
codes in clearing system messages.

DE 95—Card Issuer Reference Data

The issuer provides Card Issuer Reference Data (DE 95) when processing
retrieval or chargeback messages. The acquirer is required to include the same
data in a subsequent fulfillment of the retrieval request. In the case of a
chargeback, this applies to both Second Presentment/1240 and Arbitration
Chargeback/1442 case filings.
Attributes
n-10; LLVAR
Length Field: 2 positions, value = 10

Subfields: None
Usage
Usage
This data element contains an “issuer’s reference number” for a specific

cardholder transaction. The acquirer may be required to retain and return
DE 95 in subsequent Retrieval Fulfillment (presented via a Fee Collection
message) or Second Presentment/1240 messages sent to the issuer.

The issuer may then use DE 95 as a common reference number to link related
Retrieval Request/1644 and Retrieval Fulfillment (presented via a Fee
Collection message) messages, or to link First Chargeback/1442, Second
Presentment/1240, and Arbitration Chargeback/1442 messages to the original
cardholder transaction.
Values
Issuers are responsible for assigning values for this data element.
For Retrieval Request/1644 messages and Retrieval Fulfillment messages

(presented via Fee Collection messages), DE 95, if present, should contain the
issuer’s control number.
For First Chargeback/1442, Second Presentment/1240, and Arbitration

Chargeback/1442 messages, DE 95 must contain the Chargeback Reference
Number. The issuer assigns the Chargeback Reference Number when the First
Chargeback/1442 is created, and this number must be unique. It is used to
track the chargeback throughout its life cycle.
If present, DE 95 must be numeric.

DE 100—Receiving Institution ID Code

The Receiving Institution ID Code (DE 100) identifies the receiving institution.
Attributes
n...11; LLVAR
Subfields: None
Usage
Usage
First Presentment/1240 • X M
Financial Detail Addendum (Passenger Transport Detail— • X M
Financial Detail Addendum (Passenger Transport Detail— • X M
Trip Leg Data)/1644
Financial Detail Addendum (Vehicle Rental Detail)/1644 • X M
Financial Detail Addendum (Lodging Summary)/1644 • X M
Financial Detail Addendum (Temporary Services)/1644 • X M
Financial Detail Addendum (Shipping/Courier Services)/1644 • X M
Financial Detail Addendum (Payment Transaction Detail)/1644 • X M
Financial Detail Addendum (Telephony Billing—Summary)/1644 • X M
Financial Detail Addendum (Telephony Billing—Detail)/1644 • X M
Financial Detail Addendum (Electronic Invoice—Transaction • X M
Data)/1644
Financial Detail Addendum (Electronic Invoice—Party • X M
Information)/1644

Usage
Financial Detail Addendum (Corporate Card Common Data • X M
Requirements)/1644
Financial Detail Addendum (Corporate Fleet Transaction • X M
Information)/1644
Financial Detail Addendum (Corporate Line Item Detail)/1644 • X M
Financial Detail Addendum (Generic Detail)/1644 • X M
First Chargeback/1442 and Arbitration Chargeback/1442 • X M
Second Presentment/1240 • X M
Fee Collection (Handling Fees)/1740 • X M
Fee Collection (Other than Retrieval Fee Billing/Handling Fees)/1740 • X M
DE 100 contains the member ID or Processor ID of the physically-connected

processing facility that receives a message.
Values
This data element must contain a valid member ID or Processor ID number.

Refer to appendix A in this manual for more information regarding the use of
institution ID codes and PDSs in clearing system messages.

Attributes
ans...999; LLLVAR

Justification: Left
Usage
Usage
Data)/1644

Usage
Data)/1644
Information)/1644
Requirements)/1644
Information)/1644


DE 62, DE 123, DE 124, and DE 125 may contain a maximum of 999 positions
each of encoded PDS information.
DE 123 is present in an IPM message only if DE 48 and DE 62 cannot together

contain the full length of encoded PDSs.
If there is a significant amount of PDS data in a message, DE 48 should contain

as many complete PDSs as fits into 999 bytes. Then DE 62 should contain as
complete PDSs must be presented in DE 123, DE 124, and DE 125 as needed.
Members must not split a PDS between DE 48 and DE 62, or between DE 62

and DE 123. If an entire PDS coding scheme (tag-length-data) causes DE 48 or
DE 62 to exceed 999 positions, the entire PDS coding scheme (tag-length-data)
must be presented in the next PDS carrier (DE 62 or DE 123) instead.
Therefore, the total length of DE 48 and DE 62 may be less than 999 positions
each, with DE 123 containing additional PDS data.
Values
format.

Refer to the beginning of chapter 8 of this manual for additional information


Attributes
ans...999; LLLVAR

Justification: Left
Usage
Usage
Data)/1644

Usage
Data)/1644
Information)/1644
Requirements)/1644
Information)/1644


DE 124 is present in an IPM message only if DE 48, DE 62, and DE 123 cannot
together contain the full length of encoded PDSs.
If there is a significant amount of PDS data in a message, DE 48 should contain

as many complete PDSs as fits into 999 bytes. Then DE 62 should contain as
complete PDSs must be presented in DE 123, DE 124, and DE 125 as needed.
Members must not split a PDS between DE 48 and DE 62, between DE 62 and
DE 123, or between DE 123 and DE 124. If an entire PDS coding scheme (tag-
length-data) causes DE 48 or DE 62 to exceed 999 positions, the entire PDS
coding scheme (tag-length-data) must be presented in the next PDS carrier
(DE 62 or DE 123) instead. Therefore, the total length of DE 48 and DE 62
may be less than 999 positions each, with DE 123 and DE 124 containing
additional PDS data.
Values
format.
PDSs are formatted using a “tag-length-data” encoding procedure as follows:

Refer to the beginning of chapter 8 for additional information about PDS

definitions and an example.

Attributes
ans...999; LLLVAR

Justification: Left
Usage
Usage
Data)/1644

Usage
Data)/1644
Information)/1644
Requirements)/1644
Information)/1644
Fee Collection (Other than Retrieval Fee Billing/handling Fees)/1740 C X C


DE 125 is present in an IPM message only if DE 48, DE 62, DE 123, and DE

124 cannot together contain the full length of encoded PDSs.
If there is a significant amount of PDS data in a message, DE 48, DE 62,

DE 123, and DE 124 should contain as many complete PDSs (tag+length+data)
as will fit into 999 bytes each. The remaining complete PDSs must be
presented in DE 125 if needed.
Members must not split a PDS between DE 48 and DE 62, between DE 62 and
DE 123, between DE 123 and DE 124, or between DE 124 and DE 125. If an
entire PDS coding scheme (tag-length-data) causes a PDS carrier to exceed 999
positions, the entire PDS coding scheme (tag-length-data) must be presented in
the next PDS carrier (DE 62, DE 123, DE 124, or DE 125) instead. Therefore,
the total length of DE 48, DE 62, DE 123, and DE 124 may be less than 999
positions each, with DE 125 containing the remaining PDS data.
Values
format.



DE 127—Network Data
DE 127—Network Data
Network Data (DE 127) is reserved for internal clearing system use.
Attributes
ans...999; LLLVAR

Subfields: See “Values”
Justification: Left
Usage
This data element is a “carrier” data field for internal clearing system PDSs that
supplement the ISO 8583-1993 specification. The transaction originator does
not provide this element. The clearing system populates DE 127 as needed
with temporary data and does not forward this element to the message
destination.

8 PDS Definitions—Part 1
This chapter provides a detailed definition of private data subelements (PDSs)
0001–0500 used in IPM format offline clearing messages
PDS Construction and Use..................................................................................8-1
PDS Listing (Numerical Order) ...........................................................................8-9
PDS Listing (Alphabetical Order)......................................................................8-21
PDS 0002—Product Identifier ...........................................................................8-35
PDS 0005—Message Error Indicator.................................................................8-38
PDS 0006—Applied Business Service Arrangement ........................................8-41
PDS 0020—Issuer Currency Conversion Rate (ICCR) Effective Date..............8-44
PDS 0021—Issuer Currency Conversion Rate (ICCR) Percentage...................8-45
PDS 0022—Recurring Payment Indicator .........................................................8-46
PDS 0023—Terminal Type................................................................................8-47
PDS 0025—Message Reversal Indicator ...........................................................8-50
PDS 0026—File Reversal Indicator ...................................................................8-53
PDS 0043—Program Registration ID ................................................................8-56
PDS 0052—Electronic Commerce Security Level Indicator .............................8-58
PDS 0105—File ID.............................................................................................8-61
PDS 0110—Transmission ID .............................................................................8-65
PDS 0122—Processing Mode ............................................................................8-68

PDS Definitions—Part 1
PDS 0137—Fee Collection Control Number ....................................................8-69
PDS 0138—Source Message Number ID ..........................................................8-70
PDS 0146—Amounts, Transaction Fee .............................................................8-71
PDS 0148—Currency Exponents ......................................................................8-77
PDS 0149—Currency Codes, Amounts, Original .............................................8-81
PDS 0158—Business Activity ............................................................................8-83
PDS 0159—Settlement Data 1...........................................................................8-94
PDS 0161—Settlement Data 2......................................................................... 8-102
PDS 0164—Currency Cross Rates ................................................................... 8-109
PDS 0165—Settlement Indicator ..................................................................... 8-112
PDS 0170—Card Acceptor Inquiry Information............................................. 8-116
PDS 0171—Alternate Card Acceptor Description Data.................................. 8-120
PDS 0172—Sole Proprietor Name .................................................................. 8-123
PDS 0173—Legal Corporate Name ................................................................. 8-124
PDS 0174—Dun & Bradstreet Number........................................................... 8-125
PDS 0175—Card Acceptor URL ...................................................................... 8-126
PDS 0189—Point-of-Interaction (POI) Phone Data ....................................... 8-127
PDS 0190—Partner ID Code ........................................................................... 8-132
PDS 0191—Originating Message Format........................................................ 8-134
PDS 0228—Retrieval Document Code............................................................ 8-137
PDS 0230—Fulfillment Document Code ........................................................ 8-138
PDS 0241—MasterCom Control Number........................................................ 8-139
PDS 0242—MasterCom Service Indicator....................................................... 8-141

PDS 0243—MasterCom Retrieval Response Data........................................... 8-142
PDS 0244—MasterCom Chargeback Support Documentation Dates ............ 8-148
PDS 0245—MasterCom Arbitration Chargeback Sender Processing Date .... 8-151
PDS 0246—MasterCom Sender Memo............................................................ 8-152
PDS 0247—MasterCom Receiver Memo ......................................................... 8-153
PDS 0248—MasterCom Image Review Memo................................................ 8-154
PDS 0249—MasterCom Record ID.................................................................. 8-155
PDS 0250—MasterCom Endpoints.................................................................. 8-156
PDS 0251—MasterCom Fulfillment Document Code..................................... 8-158
PDS 0252—MasterCom Image Metadata ........................................................ 8-159
PDS 0253—MasterCom System Enhanced Data............................................. 8-161
PDS 0254—MasterCom Member Enhanced Data........................................... 8-162
PDS 0255—MasterCom Message Type ........................................................... 8-163
PDS 0260—Edit Exclusion Indicator............................................................... 8-165
PDS 0261—Risk Management Approval Code............................................... 8-171
PDS 0262—Documentation Indicator............................................................. 8-172
PDS 0264—Original Retrieval Reason for Request ........................................ 8-174
PDS 0265—Initial Presentment/Fee Collection Data ..................................... 8-176
PDS 0266—First Chargeback/Fee Collection Return Data............................. 8-179
PDS 0267—Second Presentment/Fee Collection Resubmission Data ........... 8-185
PDS 0268—Amount, Partial Transaction ........................................................ 8-190
PDS 0280—Source File ID .............................................................................. 8-192
PDS 0298—Reconciled, Transmission ............................................................ 8-194

PDS 0300—Reconciled, File............................................................................ 8-196
PDS 0301—File Amount, Checksum .............................................................. 8-198
PDS 0302—Reconciled, Member Activity....................................................... 8-200
PDS 0306—File Message Counts .................................................................... 8-202
PDS 0358—Reconciled, Business Activity ...................................................... 8-203
PDS 0359—Reconciled, Settlement Activity ................................................... 8-206
PDS 0370—Reconciled, Account Range......................................................... 8-209
PDS 0371—Reconciled, Message Reason Code ............................................. 8-211
PDS 0372—Reconciled, Transaction Function ............................................... 8-212
PDS 0373—Reconciled, Card Acceptor ID ..................................................... 8-214
PDS 0374—Reconciled, Processing Code ...................................................... 8-215
PDS 0378—Original/Reversal Totals Indicator............................................... 8-220
PDS 0380—Debits, Transaction Amount In Transaction Currency ............... 8-222
PDS 0381—Credits, Transaction Amount in Transaction Currency .............. 8-224
PDS 0384—Amount, Net Transaction in Transaction Currency .................... 8-226
PDS 0390—Debits, Transaction Amount in Reconciliation Currency ........... 8-228
PDS 0391—Credits, Transaction Amount in Reconciliation Currency .......... 8-230
PDS 0392—Debits, Fee Amounts in Reconciliation Currency....................... 8-232
PDS 0393—Credits, Fee Amounts In Reconciliation Currency...................... 8-234
PDS 0394—Amount, Net Transaction in Reconciliation Currency ................ 8-236
PDS 0395—Amount, Net Fee in Reconciliation Currency ............................. 8-238

8-iv May 2004 • IPM Clearing Formats
PDS 0396—Amount, Net Total in Reconciliation Currency........................... 8-240
PDS 0400—Debits, Transaction Number........................................................ 8-242
PDS 0401—Credits, Transaction Number....................................................... 8-243
PDS 0402—Total, Transaction Number.......................................................... 8-244

IPM Clearing Formats • May 2004 8-v
PDS Construction and Use

This chapter defines private data subelements (PDSs) 0001–0500 used in this
specification. These subelements are defined for situations in which the
International Organization for Standardization (ISO) did not define standard
data elements in the ISO 8583-1993 specification or in situations in which the
ISO data elements are insufficient for operational requirements.
All PDSs are designed to be incorporated as subelements in ISO “private-use”

data elements. Private-use data elements are specifically designated in the ISO
8583-1993 specification for “private” organization use. As such, defined PDSs
enhance the overall functionality of the implementation of ISO 8583 entirely
within the ISO specification framework.
Several ISO standard private-use data elements are designated to be formatted

using a common PDS encoding procedure (described later in this chapter).
When present in a message, these ISO data elements are always formatted to
contain one or more PDSs in the ISO data element.
The following ISO private-use data elements are designated to contain PDS-
encoded data:
• Additional Data (Data Element [DE] 48)

PDSs in DE 48, DE 62, DE 123, DE 124, and DE 125 primarily support

individual program and service requirements. PDSs placed in these data
elements are considered a permanent part of this specification.
Originators must populate DE 48 first, then DE 62, then DE 123, then DE 124,
and finally DE 125.
If there is a significant amount of PDS data in a message, DE 48 must contain

as many complete PDSs as fits into 999 bytes. Then DE 62 must contain as
many complete PDSs as fits into 999 bytes. The remaining complete PDSs
must be in DE 123, DE 124, and DE 125 as needed.
Members must not split a PDS between DE 48 and DE 62. If an entire PDS
coding scheme (tag+length+data) causes DE 48 to exceed 999 positions, the
entire PDS coding scheme (tag+length+data) must be placed into the next PDS
carrier (DE 62) instead. Therefore, the total length of DE 48 may be less than
999 positions, with DE 62 containing additional PDS data. Similarly, members
must not split a PDS between DE 62 and DE 123, between DE 123 and
DE 124, or between DE 124 and DE 125.

The PDS Encoding Scheme

Each PDS consists of three components:
• PDS Tag Field—tag

• PDS Length Field—length
• PDS Data Field—data
The first four bytes of each PDS must contain the subelement tag ID, a
numeric value in the range 0001–9999, to uniquely identify the subelement.
The second three bytes of each PDS must contain the subelement length, a
numeric value in the range 001–992, to specify the total length (in bytes) of the
PDS data portion.
The remainder of the PDS consists of the actual data.
Because all PDSs have a common tag-length-data encoding format, new PDSs
may be added to messages at any time without impacting message processing
software resident on any member processing system. If a processor does not
recognize a PDS tag, it may simply use the length field to count past the PDS
data portion and continue parsing for any additional PDSs.
Note PDSs cannot be duplicated within an IPM message. The clearing system rejects
any message containing duplicate occurrences of a PDS tag field.
The following diagram illustrates the PDS encoding scheme in an ISO standard
data element:
LLL Tag Length Data .............. Tag Length Data ..............
1st PDS 2nd PDS
Tag Length Data ..............

Length field of the ISO data
element indicating the sum total
length of all PDSs contained in it
Nth PDS

Annotation of PDS Attributes

The following notation conventions are employed throughout this manual to
describe the attributes of all PDSs:
Data Representation Attributes
a alphabetic characters A–Z and a–z
n numeric digits 0–9
as alphabetic characters A–Z and a–z, and space character
ns numeric digits 0–9 and special characters (including space)
an alphabetic and numeric characters
ans alphabetic, numeric, and special characters (including space)
b binary representation of data in eight-bit bytes
Date and Time Attributes
MM month (two digits; 01–12)
DD day (two digits; 01–31)
YY year (last two digits of calendar year; 00–99)
hh hour (two digits; 00–23)
mm minute (two digits; 00–59)
ss second (two digits; 00–59)
Data Length Attributes
-digit(s) Fixed length in number of positions.
Example: “n-3” indicates a three-position numeric PDS.
Example: “an-10” indicates a 10-position alphanumeric PDS.

...digit(s) Variable length, with maximum number of positions specified.
Example: “n...11” indicates a variable-length numeric PDS of 1–11
digits.
Example: “an...25” indicates a variable-length alphanumeric PDS of
1–25 positions.
LLLVAR Present with a variable-length data element attribute, indicates that
“LLL” is the length field and represents the number of positions in the
variable-length data field that follows. The length field contains a
Example: “an..500; LLLVAR” indicates a variable-length
alphanumeric data element having a length of 1–500
positions.
Conventions for Data Representation

This specification is independent of the specific data encoding format (for
example, EBCDIC or ASCII).
The following data encoding conventions are standard for all messages.
• All message data elements are aligned on byte boundaries, for example, a
data element cannot begin with the low order “nibble” or any bit other
than the high order bit of any byte.
• All binary (attribute “b”) data elements are constructed of bit-strings that
have lengths that are an integral number of eight-bit bytes. No binary data
element has a length of less than eight bits (one byte).
Note “b-8” indicates a fixed length binary field of eight characters (eight bytes, 64
bits).
• All length fields are encoded as numeric, right-justified with leading zeros.
PDS length fields have values in the range 001–992.

Data Field and Subfield Justification

Right-justified data fields and subfields that do not contain a value that fills the
entire field must contain leading zeros. Most numeric (attribute “n”) data
elements are right-justified; for example, amounts always have this right
justification with leading zeros.
Left justified fields and subfields that do not use the entire field with a value
must have trailing spaces.
Justification of data elements and subfields are given under the “Attributes” and
“Subfields” headings throughout this chapter. A justification of not applicable
(n/a) indicates that the values contained within those fields or subfields take
up all positions allowed.
Note Members can send clearing files with PDSs in any sequence. In all clearing files
that members receive, the clearing system formats the PDS data in ascending
sequence by PDS tag number.
For example, assume a member wants to present the PDS data in the following
table:
PDS Number Description Length Value

0165 Settlement Indicator 1 M
0012 Cardholder Transaction Date and Time 14 19960930000000
0023 Terminal Type 3 CT2
0170 Card Acceptor Inquiry Information 14 1-800-555-1212

The member may construct DE 48 as in the following table:
Position(s) Value Description

1–4 0165 First PDS tag
5–7 001 First PDS length
8 M First PDS data
9–12 0012 Second PDS tag
13–15 014 Second PDS length
16–29 19960930000000 Second PDS data
30–33 0023 Third PDS tag
34–36 003 Third PDS length
37–39 CT2 Third PDS data
40–43 0170 Fourth PDS tag
44–46 014 Fourth PDS length
47–60 1-800-555-1212 Fourth PDS data
Subelement Tag Assignment

PDSs that one or more programs or services define for use are assigned tags in
ascending numeric order in the ranges 0001–0799 and 1000–9999. These PDSs
are considered a permanent part of this specification.
PDSs the clearing system reserves for internal use are assigned tags in
ascending numeric order in the range 0800–0899. These subelements are not
defined for member systems’ use and are not documented as part of this
general specification. The clearing system operations staff may use them for
special functions, such as unique interface requirements to external networks
(gateways) and other network support functions. These PDSs are never sent
to members.
PDSs used to support temporary program or service conversion and

enhancement activities are assigned identifiers in ascending numeric order in
the range 0900–0999. These PDSs are not considered a permanent part of this
specification, but will be used as necessary until the related
conversion/enhancement activity is completed. These PDS tags may then be
reused to support other conversion efforts or unique program and service
requirements. These PDSs are never sent to members.

The PDSs that are reserved for member proprietary use are in the range 1000–
1099. Members can use these PDSs to exchange data related to special
programs. The clearing system passes these PDSs unedited to the receivers.
These PDSs may be placed in any of the “Additional Data” data elements
(DE 48, DE 62, DE 123, DE 124, or DE 125). The total length of the tags,
lengths, and data for PDS 1000–1099 in a single IPM message cannot exceed
992 bytes.
PDSs are not restricted for use in a particular PDS carrier. For example,
PDS 0001–PDS 0099, or PDS 1000–1099, are not required to be in DE 48 as
opposed to DE 62, DE 123, DE 124, or DE 125.
Members/processors can present PDS data in any sequence, in any carrier,

provided that the PDS data is placed first in DE 48, then DE 62, then DE 123,
then DE 124, and finally DE 125.
Subfield Presence Requirements

Data elements and PDSs may contain subfields. Some of these subfields are
mandatory and some are optional. For all fixed-length data elements and
PDSs, all subfields must be populated. For variable-length data elements and
PDSs, the following rules exist:
• All subfields that comprise the minimum length for the data element or
PDS must be populated. Subfields that are beyond the minimum length of
the element are optional and should not be populated unless the sender
has valid data to present. In other words, optional subfields must not be
populated with filler characters such as all spaces or all zeros.
• If any optional subfield is presented with valid data, all subfields preceding
that subfield must be populated. In this case, filler characters such as
spaces are acceptable. For example, if a PDS contains four subfields, and
the sender has valid data to present for subfields 1, 2, and 4, it must fill
subfield 3 with all spaces or all zeros so that all four subfields are
presented in the correct positions for the PDS.


European region.

manual to prepare for processing of these transactions by GCMS.

PDS Listing (Numerical Order)

The following table is a listing of PDSs 0001–1099 in numerical order. .
Tag Length Name Attribute

0002 003 Product Identifier ans-3; TAGLLL
0005 Var… Message Error Indicator ans…140; TAGLLLVAR
0006 010 Applied Business Service Arrangement ans–10; TAGLLL
0020 006 Issuer Currency Conversion Rate (ICCR) n-6; TAGLLL
Effective Date
0021 007 Issuer Currency Conversion Rate (ICCR) n-7; TAGLLL
Percentage
0022 001 Recurring Payment Indicator n-1; TAGLLL
0023 003 Terminal Type ans-3; TAGLLL
0025 Var... Message Reversal Indicator an...7; TAGLLLVAR
0026 Var... File Reversal Indicator an...7; TAGLLLVAR
0043 003 Program Registration ID ans-3; TAGLLL
0052 003 Electronic Commerce Security Level n-3; TAGLLL
Indicator
0105 025 File ID n-25; TAGLLL
0110 025 Transmission ID n-25; TAGLLL
0122 001 Processing Mode ans-1; TAGLLL
0137 Var… Fee Collection Control Number n…20; TAGLLLVAR
0138 008 Source Message Number ID n-8; TAGLLL
0146 Var… Amounts, Transaction Fee n…336; TAGLLLVAR
0148 Var… Currency Exponents ans…60; TAGLLLVAR
0149 006 Currency Codes, Amounts, Original n-6; TAGLLL
0158 Var... Business Activity ans...20; TAGLLLVAR
ans...24; TAGLLLVAR
0159 Var... Settlement Data 1 ans...67; TAGLLLVAR
0161 Var... Settlement Data 2 ans...67; TAGLLLVAR
0164 Var... Currency Cross Rates ans...230; TAGLLLVAR
0165 Var... Settlement Indicator ans...30; TAGLLLVAR
0170 Var... Card Acceptor Inquiry Information ans...57; TAGLLLVAR


0171 Var... Alternate Card Acceptor Description Data ans...201; TAGLLLVAR
0172 Var... Sole Proprietor Name ans...30; TAGLLLVAR
0173 Var... Legal Corporate Name ans...30; TAGLLLVAR
0174 015 Dun & Bradstreet Number n-15; TAGLLL
0175 Var… Card Acceptor URL ans…255; TAGLLLVAR
0189 041 Point-of-Interaction (POI) Phone Data ans-41; TAGLLL
0190 Var... Partner ID Code ans...6; TAGLLLVAR
0191 001 Originating Message Format n-1; TAGLLL
0228 001 Retrieval Document Code n-1; TAGLLL
0230 001 Fulfillment Document Code n-1; TAGLLL
0241 Var... MasterCom Control Number ans...7; TAGLLLVAR
0242 001 MasterCom Service Indicator ans-1;TAGLLL
0243 Var... MasterCom Retrieval Response Data ans...38; TAGLLLVAR
0244 Var... MasterCom Chargeback Support ans...12; TAGLLLVAR
Documentation Dates
0245 006 MasterCom Arbitration Chargeback n-6; TAGLLL
Sender Processing Date
0246 Var… MasterCom Sender Memo ans…100; TAGLLLVAR
0247 Var… MasterCom Receiver Memo ans…100; TAGLLLVAR
0248 Var… MasterCom Image Review Memo ans…100: TAGLLLVAR
0249 Var… MasterCom Record ID n…10: TAGLLLVAR
0250 014 MasterCom Endpoints n-14: TAGLLL
0251 001 MasterCom Fulfillment Document Code n-1: TAGLLL
0252 Var… MasterCom Image Metadata ans…124: TAGLLVAR
0253 Var… MasterCom System Enhanced Data ans…999: TAGLLLVAR
0254 Var… MasterCom Member Enhanced Data ans…999: TAGLLLVAR
0255 Var… MasterCom Message Type ans…7, TAGLLLVAR
0260 Var... Edit Exclusion Indicator ans...4; TAGLLLVAR
0261 011 Risk Management Approval Code n-11; TAGLLL
0262 001 Documentation Indicator n-1; TAGLLL


0264 004 Original Retrieval Reason for Request n-4; TAGLLL
0265 Var... Initial Presentment/Fee Collection Data ans...110; TAGLLLVAR
0266 Var... First Chargeback/Fee Collection Return ans...127; TAGLLLVAR
Data
0267 Var... Second Presentment/Fee Collection ans...127; TAGLLLVAR
Resubmission Data
0268 015 Amount, Partial Transaction n-15; TAGLLL
0280 025 Source File ID n-25; TAGLLL
0298 025 Reconciled, Transmission n-25; TAGLLL
0300 025 Reconciled, File n-25; TAGLLL
0301 016 File Amount, Checksum n-16; TAGLLL
0302 001 Reconciled, Member Activity a-1; TAGLLL
0306 008 File Message Counts n-8; TAGLLL
0358 Var... Reconciled, Business Activity ans...20; TAGLLLVAR
ans...24; TAGLLLVAR
0359 Var... Reconciled, Settlement Activity ans...67; TAGLLLVAR
0370 Var... Reconciled, Account Range n...38; TAGLLLVAR
0371 004 Reconciled, Message Reason Code n-4; TAGLLL
0372 007 Reconciled, Transaction Function n-7; TAGLLL
0373 015 Reconciled, Card Acceptor ID ans-15; TAGLLL
0374 002 Reconciled, Processing Code n-2; TAGLLL
0375 Var... Member Reconciliation Indicator 1 ans...50; TAGLLLVAR
0376 Var... Member Reconciliation Indicator 2 ans...99; TAGLLLVAR
0378 001 Original/Reversal/Totals Indicator a-1; TAGLLL
0380 017 Debits, Transaction Amount in an-17; TAGLLL
0381 017 Credits, Transaction Amount in an-17; TAGLLL
0384 017 Amount, Net Transaction in an-17; TAGLLL
0390 017 Debits, Transaction Amount in an-17; TAGLLL
Reconciliation Currency


0391 017 Credits, Transaction Amount in an-17; TAGLLL
0392 Var... Debits, Fee Amounts in Reconciliation an...180; TAGLLLVAR
Currency
0393 Var... Credits, Fee Amounts in Reconciliation an...180; TAGLLLVAR
Currency
0394 017 Amount, Net Transaction in an-17; TAGLLL
0395 013 Amount, Net Fee in Reconciliation an-13; TAGLLL
Currency
0396 017 Amount, Net Total in Reconciliation an-17; TAGLLL
Currency
0400 010 Debits, Transaction Number n-10; TAGLLL
0401 010 Credits, Transaction Number n-10; TAGLLL
0402 010 Total, Transaction Number n-10; TAGLLL
0501 016 Transaction Description n-16; TAGLLL
0505 Var... Passenger Name ans…29; TAGLLLVAR
0506 015 Ticket Number ans-15; TAGLLL
0507 004 Issuing Carrier ans-4; TAGLLL
0508 Var... Customer Code ans…25; TAGLLLVAR
0509 006 Issue Date n-6; TAGLLL
0510 008 Travel Agency Code ans-8; TAGLLL
0511 Var... Travel Agency Name ans…25; TAGLLLVAR
0512 012 Total Fare n-12; TAGLLL
0513 012 Total Fees n-12; TAGLLL
0514 012 Total Taxes n-12; TAGLLL
0515 Var… Additional Card Acceptor Information ans…40; TAGLLLVAR
0516 015 Austin–Tetra Number ans-15; TAGLLL
0517 015 NAICS Code ans-15; TAGLLL
0518 006 Line Item Date n-6; TAGLLL
0519 014 Additional Fuel Location Information an-14; TAGLLL
0520 006 Travel Date n-6; TAGLLL


0521 002 Carrier Code ans-2; TAGLLL
0522 002 Service Class Code ans-2; TAGLLL
0523 005 City of Origin/Airport Code ans-5; TAGLLL
0524 005 City of Destination/Airport Code ans-5; TAGLLL
0525 001 Stop Over Code ans-1; TAGLLL
0526 015 Conjunction Ticket ans-15; TAGLLL
0527 015 Exchange Ticket ans-15; TAGLLL
0528 001 Coupon Number ans-1; TAGLLL
0529 Var... Fare Basis Code ans…15; TAGLLLVAR
0530 005 Flight Number ans-5; TAGLLL
0531 005 Departure Time ans-5; TAGLLL
0532 014 Total Charges ans-14; TAGLLL
0533 005 Arrival Time ans-5; TAGLLL
0534 014 Total Non-Room Charges ans-14; TAGLLL
0535 012 Fare n-12; TAGLLL
0536 012 Fee n-12; TAGLLL
0537 012 Taxes n-12; TAGLLL
0538 Var... Endorsements/Restrictions ans…20; TAGLLLVAR
0539 014 Total Amount Charged on Credit Card ans-14; TAGLLL
0540 014 Room Service Charges ans-14; TAGLLL
0541 014 Lounge/Bar Charges ans-14; TAGLLL
0542 014 Transportation Charges ans-14; TAGLLL
0543 014 Gratuity Charges ans-14; TAGLLL
0544 009 Rental Agreement Number ans-9; TAGLLL
0545 Var... Renter Name ans…40; TAGLLLVAR
0546 Var... Rental Return City ans…25; TAGLLLVAR
0547 003 Rental Return State/Province ans-3; TAGLLL
0548 003 Rental Return Country ans-3; TAGLLL
0549 010 Rental Return Location ID ans-10; TAGLLL
0550 006 Rental Return Date n-6; TAGLLL


0551 006 Rental Check-out Date n-6; TAGLLL
0552 017 Customer Service Toll-Free (800) Number ans-17; TAGLLL
0553 013 Rental Rate ans-13; TAGLLL
0554 014 Conference Room Charges ans-14; TAGLLL
0555 012 Rate per Mile (or per Kilometer) n-12; TAGLLL
0556 004 Total Miles (or Kilometers) n-4; TAGLLL
0557 004 Maximum Free Miles (or Kilometers) n-4; TAGLLL
0558 001 Miles/Kilometers Indicator as-1; TAGLLL
0559 013 Vehicle Insurance ans-13; TAGLLL
0560 014 Audio Visual Charges ans-14; TAGLLL
0561 013 Adjusted Amount ans-13; TAGLLL
0562 014 Banquet Charges ans-14; TAGLLL
0563 002 Program Code ans-2; TAGLLL
0564 Var... Rental Location City ans…25; TAGLLLVAR
0565 003 Rental Location State/Province ans-3; TAGLLL
0566 003 Rental Location Country as-3; TAGLLL
0567 010 Rental Location ID ans-10; TAGLLL
0568 004 Rental Class ID ans-4; TAGLLL
0569 014 Internet Access Charges ans-14; TAGLLL
0570 014 Early Departure Charges ans-14; TAGLLL
0571 Var… Guest Name ans…40; TAGLLLVAR
0572 025 Guest Number ans-25; TAGLLL
0573 Var… Invoice Number ans…25; TAGLLLVAR
0574 006 Arrival Date n-6; TAGLLL
0575 006 Departure Date n-6; TAGLLL
0576 Var… Folio Number ans…25; TAGLLLVAR
0577 017 Property Phone Number ans-17; TAGLLL
0578 015 Billing Adjustment ans-15; TAGLLL
0579 006 Invoice Date n-6; TAGLLL
0580 013 Room Rate n-13; TAGLLL


0581 014 Total Room Tax ans-14; TAGLLL
0582 002 Program Code ans-2; TAGLLL
0583 014 Phone Charges ans-14; TAGLLL
0584 014 Restaurant Charges ans-14; TAGLLL
0585 014 Mini-Bar Charges ans-14; TAGLLL
0586 014 Gift Shop Charges ans-14; TAGLLL
0587 014 Laundry and Dry Cleaning Charges ans-14; TAGLLL
0588 102 Other Services ans-102; TAGLLL
0589 012 Invoice Creation Date/Time n-12; TAGLLL
0590 002 Party Identification an-2; TAGLLL
0591 Var… Party Name ans…120; TAGLLLVAR
0592 Var… Party Address ans…240; TAGLLLVAR
0593 Var… Party Postal Information ans…46; TAGLLLVAR
0594 Var… Party Contact ans…305; TAGLLLVAR
0595 008 Card Acceptor Type ans-8; TAGLLL
0596 Var... Card Acceptor Tax ID ans…21; TAGLLLVAR
0597 014 Total Tax Amount ans-14; TAGLLL
0598 001 Total Tax Collected Indicator ans-1; TAGLLL
0599 020 Corporation VAT Number ans-20; TAGLLL
0600 Var... Card Acceptor Reference Number ans…25; TAGLLLVAR
0601 001 Party Nature of Filing a-1; TAGLLL
0602 Var… Party Supplemental Data 1 ans…672; TAGLLLVAR
0603 Var… Party Supplemental Data 2 ans...672; TAGLLLVAR
0604 Var… Transaction Supplemental Data 1 ans…672; TAGLLLVAR
0605 Var… Transaction Supplemental Data 2 ans…672; TAGLLLVAR
0606 014 Freight Amount ans-14; TAGLLL
0607 014 Duty Amount ans-14; TAGLLL
0608 010 Destination Postal Code ans-10; TAGLLL
0609 003 Destination State/Province Code ans-3; TAGLLL
0610 003 Destination Country Code ans-3; TAGLLL


0612 006 Ship Date n-6; TAGLLL
0613 010 Ship-From Postal Code ans-10; TAGLLL
0614 006 Order Date n-6; TAGLLL
0615 Var… Medical Services Ship to Health ans…40; TAGLLLVAR
Industry Number
0616 Var… Contract Number ans…40; TAGLLLVAR
0617 001 Medical Services Price Adjustment a-1; TAGLLL
0618 002 Medical Services Product Number an-2; TAGLLL
Qualifier
0619 Var… User Name ans…40; TAGLLLVAR
0620 004 Oil Company Brand Name n-4; TAGLLL
0621 004 Purchase Time n-4; TAGLLL
0622 001 Motor Fuel Service Type ans-1; TAGLLL
0623 035 Motor Fuel Information ns-35; TAGLLL
0624 Var… User Account Number ans…40; TAGLLLVAR
0625 Var… User Telephone Number ans…25; TAGLLLVAR
0626 012 Billing Statement Period n-12; TAGLLL
0627 Var… Billing Event 1 ans…540; TAGLLLVAR
0628 Var… Billing Event 2 ans…540; TAGLLLVAR
0629 Var... Odometer Reading ans…7; TAGLLLVAR
0630 Var... Vehicle Number ans…17; TAGLLLVAR
0631 Var... Driver Number/ID Number ans…17; TAGLLLVAR
0632 001 Product Type Code n-1; TAGLLL
0633 012 Coupon/Discount Amount n-12; TAGLLL
0634 006 Tax Amount 1 n-6; TAGLLL
0635 006 Tax Amount 2 n-6; TAGLLL
0636 006 Call Date n-6; TAGLLL
0637 006 Call Time n-6; TAGLLL
0638 146 Call To Information ans-146; TAGLLL
0639 006 Call Duration n-6; TAGLLL


0640 002 Call Time Period an-2; TAGLLL
0641 Var... Product Code ans…15; TAGLLLVAR
0642 Var... Item Description ans…35; TAGLLLVAR
0643 013 Item Quantity n-13; TAGLLL
0644 145 Call From Information ans-145; TAGLLL
0645 Var... Item Unit of Measure ans…12; TAGLLLVAR
0646 013 Unit Price n-13; TAGLLL
0647 014 Extended Item Amount ans-14; TAGLLL
0648 020 Item Discount ans-20; TAGLLL
0649 014 Call Usage Amount ans-14; TAGLLL
0654 001 Debit or Credit Indicator as-1; TAGLLL
0655 014 Call Long Distance Amount ans-14; TAGLLL
0658 014 Call Connect Amount ans-14; TAGLLL
0659 Var… Other Description ans…60; TAGLLLVAR
0663 Var… Free-Form Description ans…992; TAGLLLVAR
0670 Var… Payer Name or User ID ans…24; TAGLLLVAR
0671 006 Date of Funds Requested n–6; TAGLLL
0672 Var… Recipient Name (Seller) ans…24; TAGLLLVAR
0673 006 Date of Anticipated Receipt of Funds n-6; TAGLLL
0674 Var… Additional Trace/Reference Number ans…15; TAGLLLVAR
Used by Card Acceptor
0675 Var… Additional Transaction Description Data ans…15; TAGLLLVAR
0676 Var… Card Acceptor VAT Number ans…20; TAGLLLVAR
0677 Var… Customer VAT Number ans…20; TAGLLLVAR
0678 Var… Unique Invoice Number ans…17; TAGLLLVAR
0679 Var… Commodity Code ans…15; TAGLLLVAR
0680 Var… Authorized Contact Name ans…36; TAGLLLVAR
0681 Var… Authorized Contact Phone ans…17; TAGLLLVAR
0682 Var… Detail Tax Amount 1 ans…46; TAGLLLVAR


0685 002 Type of Supply an-2; TAGLLL
0686 001 Tax Exempt Indicator an-1; TAGLLL
0687 Var… Unique VAT Invoice Reference Number ans…17; TAGLLLVAR
0689 Var… Corporate Identifier ans…12; TAGLLLVAR
0690 001 No Show Indicator an-1; TAGLLL
0691 004 Days Rented n-4; TAGLLL
0692 012 Weekly Rental Amount n-12; TAGLLL
0693 014 Total Authorized Amount n-14; TAGLLL
0694 012 One Way Drop Off Charge n-12; TAGLLL
0695 012 Regular Mileage Charge n-12; TAGLLL
0696 012 Extra Mileage Charge n-12; TAGLLL
0697 012 Late Charge n-12; TAGLLL
0698 012 Fuel Charge n-12; TAGLLL
0699 014 Lodging Total Tax Amount n-14; TAGLLL
0700 012 Towing Charges n-12; TAGLLL
0701 012 Extra Charges n-12; TAGLLL
0702 012 Other Charges n-12; TAGLLL
0703 004 Total Room Nights n-4; TAGLLL
0704 014 Prepaid Expenses n-14; TAGLLL
0705 014 Total Non-Room Tax Amount n-14; TAGLLL
0706 014 Cash Advances n-14; TAGLLL
0707 014 Valet Charges ans-14; TAGLLL
0708 014 Movie Charges n-14; TAGLLL
0709 014 Business Center Charges n-14; TAGLLL
0710 014 Health Club Charges n-14; TAGLLL
0711 001 Fire Safety Act Indicator an-1; TAGLLL
0712 013 Net Fuel Price n-13; TAGLLL
0713 001 Restricted Ticket Indicator an-1; TAGLLL
0714 012 Exchange Ticket Amount n-12; TAGLLL


0715 012 Exchange Fee Amount n-12; TAGLLL
0716 Var… Travel Authorization Code ans…64; TAGLLLVAR
0717 Var… IATA Client Code ans…17; TAGLLLVAR
0718 Var… Employee/Temp Name/ID ans…40; TAGLLLVAR
0719 Var… Employee Social Security Number or ID ans…30; TAGLLLVAR
0720 Var… Job Description ans…40; TAGLLLVAR
0721 Var… Job Code ans…20; TAGLLLVAR
0722 001 Flat Rate Indicator ans-1; TAGLLL
0723 007 Regular Hours Worked n-7; TAGLLL
0724 007 Regular Hours Rate n-7; TAGLLL
0725 007 Overtime Hours Worked n-7; TAGLLL
0726 007 Overtime Hours Rate n-7; TAGLLL
0727 006 Temp Start Date n-6; TAGLLL
0728 006 Temp Week Ending n-6; TAGLLL
0729 Var… Requestor Name or ID ans…40; TAGLLLVAR
0730 Var… Supervisor/Reports To ans…40; TAGLLLVAR
0731 Var… Time Sheet Number ans…20; TAGLLLVAR
0732 018 Discount Amount ans-18; TAGLLL
0733 014 Subtotal Amount ans-14; TAGLLL
0734 Var… Miscellaneous Expenses ans…216; TAGLLLVAR
0735 Var… Service Descriptor Code ans…40; TAGLLLVAR
0736 Var… Tracking Number or Pickup Number ans…40; TAGLLLVAR
0737 014 Shipping Net Amount ans-14; TAGLLL
0738 014 Incentive Amount ans-14; TAGLLL
0739 006 Pickup Date n-6; TAGLLL
0740 006 Delivery Date n-6; TAGLLL
0741 006 Number of Packages n-6; TAGLLL
0742 012 Package Weight n-12; TAGLLL
0743 Var… Unit of Measure ans…3; TAGLLLVAR
0744 Var… Shipping Party Information ans…150; TAGLLLVAR


0745 Var… Shipping Party Address ans…300; TAGLLLVAR
0746 Var… Shipping Party Postal Information ans…41; TAGLLLVAR
0747 Var… Shipping Party Contact ans…305; TAGLLLVAR
0748 Var… Delivery Party Information ans…150; TAGLLLVAR
0749 Var… Delivery Party Address Information ans…300; TAGLLLVAR
0750 Var… Delivery Party Postal Information ans…41; TAGLLLVAR
0754 Var… Delivery Party Contact ans…305; TAGLLLVAR
0755 014 Line Item Total Amount ans-14; TAGLLL
0799 Var… Test Case Traceability Identifiers ans…165; TAGLLLVAR
1000– Var… Member-to-Member Proprietary Data ans…992; TAGLLLVAR
1099

PDS Listing (Alphabetical Order)

The following table is a listing of PDSs 0001–1099 in alphabetical order.
Name Tag Length Attribute

Additional Card Acceptor Information 0515 Var… ans…40;
TAGLLLVAR
Additional Fuel Location Information 0519 014 an-14; TAGLLL
Additional Trace/Reference Number Used by 0674 Var… ans…15;
Card Acceptor TAGLLLVAR
Additional Transaction Description Data 0675 Var… ans…15;
TAGLLLVAR
Adjusted Amount 0561 013 ans-13; TAGLLL
Alternate Card Acceptor Description Data 0171 Var... ans...201;
TAGLLLVAR
Amount, Net Fee in Reconciliation Currency 0395 013 an-13; TAGLLL
Amount, Net Total in Reconciliation Currency 0396 017 an-17; TAGLLL
Amount, Net Transaction in Reconciliation 0394 017 an-17; TAGLLL
Currency
Amount, Net Transaction in Transaction 0384 017 an-17; TAGLLL
Currency
Amount, Partial Transaction 0268 015 n-15; TAGLLL
Amounts, Transaction Fee 0146 Var… n…336;
TAGLLLVAR
Applied Business Service Arrangement 0006 010 ans–10; TAGLLL
Arrival Date 0574 006 n-6; TAGLLL
Arrival Time 0533 005 ans-5; TAGLLL
Audio Visual Charges 0560 014 ans-14; TAGLLL
Austin–Tetra Number 0516 015 ans-15; TAGLLL
Authorized Contact Name 0680 Var… ans…36;
TAGLLLVAR
Authorized Contact Phone 0681 Var… ans…17;
TAGLLLVAR
Banquet Charges 0562 014 ans-14; TAGLLL
Billing Adjustment 0578 015 ans-15; TAGLLL


Billing Event 1 0627 Var… ans…540;
TAGLLLVAR
Billing Event 2 0628 Var… ans…540;
TAGLLLVAR
Billing Statement Period 0626 012 n-12; TAGLLL
Business Activity 0158 Var... ans...20;
TAGLLLVAR
ans...24;
TAGLLLVAR
Business Center Charges 0709 014 ans-14; TAGLLL
Call Connect Amount 0658 014 ans-14; TAGLLL
Call Date 0636 006 n-6; TAGLLL
Call Duration 0639 006 n-6; TAGLLL
Call From Information 0644 145 ans-145;
TAGLLL
Call Long Distance Amount 0655 014 ans-14; TAGLLL
Call Time 0637 006 n-6; TAGLLL
Call Time Period 0640 002 an-2; TAGLLL
Call To Information 0638 146 ans-146;
TAGLLL
Call Usage Amount 0649 014 ans-14; TAGLLL
Card Acceptor Inquiry Information 0170 Var… ans…57;
TAGLLLVAR
Card Acceptor Reference Number 0600 Var… ans…25;
TAGLLLVAR
Card Acceptor Tax ID 0596 Var… ans…21;
TAGLLLVAR
Card Acceptor Type 0595 008 ans-8; TAGLLL
Card Acceptor URL 0175 Var… ans…255;
TAGLLVAR
Card Acceptor VAT Number 0676 Var… ans…20;
TAGLLLVAR
Carrier Code 0521 002 ans-2; TAGLLL
Cash Advances 0706 014 ans-14; TAGLLL


City of Destination/Airport Code 0524 005 ans-5; TAGLLL
City of Origin/Airport Code 0523 005 ans-5; TAGLLL
Commodity Code 0679 Var… ans…15;
TAGLLLVAR
Conference Room Charges 0554 014 ans-14; TAGLLL
Conjunction Ticket 0526 015 ans-15; TAGLLL
Contract Number 0616 Var… ans…40;
TAGLLLVAR
Corporate Identifier 0689 Var… ans…12;
TAGLLLVAR
Corporation VAT Number 0599 020 ans-20; TAGLLL
Coupon Number 0528 001 ans-1; TAGLLL
Coupon/Discount Amount 0633 012 n-12; TAGLLL
Credits, Fee Amounts in Reconciliation 0393 Var... an...180;
Currency TAGLLLVAR
Credits, Transaction Amount in Reconciliation 0391 017 an-17; TAGLLL
Currency
Credits, Transaction Amount in Transaction 0381 017 an-17; TAGLLL
Currency
Credits, Transaction Number 0401 010 n-10; TAGLLL
Currency Codes, Amounts, Original 0149 006 n-6; TAGLLL
Currency Cross Rates 0164 Var... ans...230;
TAGLLLVAR
Currency Exponents 0148 Var... ans…60;
TAGLLLVAR
Customer Code 0508 Var... ans…25;
TAGLLLVAR
Customer Service Toll-Free (800) Number 0552 017 ans-17; TAGLLL
Customer VAT Number 0677 Var… ans…20;
TAGLLLVAR
Date of Anticipated Receipt of Funds 0673 006 n–6; TAGLLL
Date of Funds Requested 0671 006 n–6; TAGLLL
Days Rented 0691 004 n-4; TAGLLL


Debit or Credit Indicator 0654 001 as-1; TAGLLL
Debits, Fee Amounts in Reconciliation 0392 Var... an...180;
Currency TAGLLLVAR
Debits, Transaction Amount in Reconciliation 0390 017 an-17; TAGLLL
Currency
Debits, Transaction Amount in Transaction 0380 017 an-17; TAGLLL
Currency
Debits, Transaction Number 0400 010 n-10; TAGLLL
Delivery Date 0740 006 n-6; TAGLLL
Delivery Party Address Information 0749 Var… ans…300;
TAGLLLVAR
Delivery Party Contact 0754 Var… ans…305;
TAGLLLVAR
Delivery Party Information 0748 Var… ans…150;
TAGLLLVAR
Delivery Party Postal Information 0750 Var… ans…41;
TAGLLLVAR
Departure Date 0575 006 n-6; TAGLLL
Departure Time 0531 005 ans-5; TAGLLL
Destination Country Code 0610 003 ans-3; TAGLLL
Destination Postal Code 0608 010 ans-10; TAGLLL
Destination State/Province Code 0609 003 ans-3; TAGLLL
Detail Tax Amount 1 0682 Var… ans…46;
TAGLLLVAR
TAGLLLVAR
TAGLLLVAR
TAGLLLVAR
TAGLLLVAR
Detail Tax Amount 6 0753 Var… ans…46
TAGLLLVAR
Discount Amount 0732 018 ans-18; TAGLLL


Documentation Indicator 0262 001 n-1; TAGLLL
Driver Number/ID Number 0631 Var... ans..17;
TAGLLLVAR
Dun & Bradstreet Number 0174 015 n-15; TAGLLL
Duty Amount 0607 014 ans-14; TAGLLL
Early Departure Charges 0570 014 ans-14; TAGLLL
Edit Exclusion Indicator 0260 Var... ans...4;
TAGLLLVAR
Electronic Commerce Security Level Indicator 0052 003 n--3; TAGLLL
Employee/Temp Name/ID 0718 Var… ans…40;
TAGLLLVAR
Employee Social Security Number or ID 0719 Var… ans…30;
TAGLLLVAR
Endorsements/Restrictions 0538 Var… ans…20;
TAGLLLVAR
Exchange Fee Amount 0715 012 n-12; TAGLLL
Exchange Ticket 0527 015 ans-15; TAGLLL
Exchange Ticket Amount 0714 012 n-12; TAGLLL
Extended Item Amount 0647 014 ans-14; TAGLLL
Extra Charges 0701 012 n-12; TAGLLL
Extra Mileage Charge 0696 012 n-12; TAGLLL
Fare 0535 012 n-12; TAGLLL
Fare Basis Code 0529 Var… ans…15;
TAGLLLVAR
Fee 0536 012 n-12; TAGLLL
Fee Collection Control Number 0137 Var… n…20;
TAGLLLVAR
File Amount, Checksum 0301 16 n-16; TAGLLL
File ID 0105 025 n-25; TAGLLL
File Message Counts 0306 008 n-8; TAGLLL
File Reversal Indicator 0026 Var... an...7;
TAGLLLVAR
Fire Safety Act Indicator 0711 001 an-1; TAGLLL


First Chargeback/Fee Collection Return Data 0266 Var... ans...127;
TAGLLLVAR
Flat Rate Indicator 0722 001 ans-1; TAGLLL
Flight Number 0530 005 ans-5; TAGLLL
Folio Number 0576 Var… ans…25;
TAGLLLVAR
Free-Form Description 0663 Var… ans…992;
TAGLLLVAR
Freight Amount 0606 014 ans-14; TAGLLL
Fuel Charge 0698 012 n-12; TAGLLL
Fulfillment Document Code 0230 001 n-1; TAGLLL
Gift Shop Charges 0586 014 ans-14; TAGLLL
Gratuity Charges 0543 014 ans-14; TAGLLL
Guest Name 0571 Var… ans…40;
TAGLLLVAR
Guest Number 0572 025 ans-25; TAGLLL
Health Club Charges 0710 014 ans-14; TAGLLL
IATA Client Code 0717 Var… ans…17;
TAGLLLVAR
Incentive Amount 0738 014 ans-14; TAGLLL
Initial Presentment/Fee Collection Data 0265 Var... ans...110;
TAGLLLVAR
Internet Access Charges 0569 014 ans-14; TAGLLL
Invoice Creation Date/Time 0589 012 n-12; TAGLLL
Invoice Date 0579 006 n-6; TAGLLL
Invoice Number 0573 Var… ans…25;
TAGLLLVAR
Issue Date 0509 006 n-6; TAGLLL
Issuer Currency Conversion Rate (ICCR) 0020 006 n-6; TAGLLL
Effective Date
Issuer Currency Conversion Rate (ICCR) 0021 007 n-7; TAGLLL
Percentage
Issuing Carrier 0507 004 ans-4; TAGLLL


Item Description 0642 Var... ans…35;
TAGLLLVAR
Item Discount 0648 020 ans-20; TAGLLL
Item Quantity 0643 013 n-13; TAGLLL
Item Unit of Measure 0645 Var… ans…12;
TAGLLLVAR
Job Code 0721 Var… ans…20;
TAGLLLVAR
Job Description 0720 Var… ans…40;
TAGLLLVAR
Late Charge 0697 012 n-12; TAGLLL
Laundry and Dry Cleaning Charges 0587 014 ans-14; TAGLLL
Legal Corporate Name 0173 Var... ans...30;
TAGLLLVAR
Line Item Date 0518 006 n-6; TAGLLL
Line Item Total Amount 0755 014 ans-14; TAGLLL
Lodging Total Tax Amount 0699 014 n-14; TAGLLL
Lounge/Bar Charges 0541 014 ans-14; TAGLLL
MasterCom Arbitration Chargeback Sender 0245 006 n-6; TAGLLL
Processing Date
MasterCom Chargeback Support 0244 Var... ans...12;
Documentation Dates TAGLLLVAR
MasterCom Control Number 0241 Var... ans...7;
TAGLLLVAR
MasterCom Endpoints 0250 014 n-14; TAGLLL
MasterCom Fulfillment Document Code 0251 001 n-1; TAGLLL
MasterCom Image Metadata 0252 Var… ans…124;
TAGLLLVAR
MasterCom Image Review Memo 0248 Var… ans…100;
TAGLLLVAR
MasterCom Member Enhanced Data 0254 Var… ans…999;
TAGLLLVAR
MasterCom Message Type 0255 Var… ans…7,
TAGLLLVAR


MasterCom Receiver Memo 0247 Var… ans…100;
TAGLLLVAR
MasterCom Record ID 0249 Var… n…10;
TAGLLLVAR
MasterCom Retrieval Response Data 0243 Var... ans...38;
TAGLLLVAR
MasterCom Sender Memo 0246 Var… ans…100;
TAGLLLVAR
MasterCom Service Indicator 0242 001 ans-1; TAGLLL
MasterCom System Enhanced Data 0253 Var… ans…999;
TAGLLLVAR
Maximum Free Miles (or Kilometers) 0557 004 n-4; TAGLLL
Medical Services Price Adjustment 0617 001 a-1; TAGLLL
Medical Services Product Number Qualifier 0618 002 an-2; TAGLLL
Medical Services Ship to Health Industry 0615 Var… ans…40;
Number TAGLLLVAR
Member Reconciliation Indicator 1 0375 Var... ans...50;
TAGLLLVAR
Member Reconciliation Indicator 2 0376 Var... ans...99;
TAGLLLVAR
Member-to-Member Proprietary Data 1000-1099 Var… ans…992;
TAGLLLVAR
Message Error Indicator 0005 Var… ans…110;
TAGLLLVAR
Message Reversal Indicator 0025 Var... an...7;
TAGLLLVAR
Miles/Kilometers Indicator 0558 001 as-1; TAGLLL
Mini-Bar Charges 0585 012 ans-12; TAGLLL
Miscellaneous Expenses 0734 Var… ans…248;
TAGLLLVAR
Motor Fuel Information 0623 035 ns-35; TAGLLL
Motor Fuel Service Type 0622 001 ans-1; TAGLLL
Movie Charges 0708 014 ans-142;
TAGLLL


NAICS Code 0517 015 ans-15; TAGLLL
Net Fuel Price 0712 013 n-13; TAGLLL
No Show Indicator 0690 001 an-1; TAGLLL
Number of Packages 0741 006 n-6; TAGLLL
Odometer Reading 0629 Var… ans…7;
TAGLLLVAR
Oil Company Brand Name 0620 004 n-4; TAGLLL
One Way Drop Off Charge 0694 012 n-12; TAGLLL
Order Date 0614 006 n-6; TAGLLL
Original Retrieval Reason for Request 0264 004 n-4; TAGLLL
Original/Reversal/Totals Indicator 0378 001 a-1; TAGLLL
Originating Message Format 0191 001 n-1; TAGLLL
Other Charges 0702 012 n-12; TAGLLL
Other Description 0659 Var… ans…60;
TAGLLLVAR
Other Services 0588 102 ans-102;
TAGLLL
Overtime Hours Rate 0726 007 n-7; TAGLLL
Overtime Hours Worked 0725 007 n-7; TAGLLL
Package Weight 0742 012 n-12; TAGLLL
Partner ID Code 0190 Var... ans...6;
TAGLLLVAR
Party Address 0592 Var… ans…240;
TAGLLLVAR
Party Contact 0594 Var… ans…305;
TAGLLLVAR
Party Identification 0590 002 an-2; TAGLLL
Party Name 0591 Var… ans…120;
TAGLLLVAR
Party Nature of Filing 0601 001 a-1; TAGLLL
Party Postal Information 0593 Var… Ans…46;
TAGLLLVAR


Party Supplemental Data 1 0602 Var… ans…672;
TAGLLLVAR
Party Supplemental Data 2 0603 Var… ans…672;
TAGLLLVAR
Passenger Name 0505 Var… ans…29;
TAGLLLVAR
Payer Name or User ID 0670 Var… ans…24;
TAGLLLVAR
Phone Charges 0583 014 ans-14; TAGLLL
Pickup Date 0739 006 n-6; TAGLLL
Point-of-Interaction (POI) Phone Data 0189 041 ans-41; TAGLLL
Prepaid Expenses 0704 014 ans-14; TAGLLL
Processing Mode 0122 001 ans-1; TAGLLL
Product Code 0641 Var… ans…15;
TAGLLLVAR
Product Identifier 0002 003 ans-3; TAGLLL
Product Type Code 0632 001 n-1; TAGLLL
Program Code 0563 002 ans-2; TAGLLL
Program Code 0582 002 ans-2; TAGLLL
Program Registration ID 0043 003 ans-3; TAGLLL
Property Phone Number 0577 017 ans-17; TAGLLL
Purchase Time 0621 004 n-4; TAGLLL
Rate per Mile (or per Kilometer) 0555 012 n-12; TAGLLL
Recipient Name (Seller) 0672 Var… ans…24;
TAGLLLVAR
Reconciled, Account Range 0370 Var... n...38;
TAGLLLVAR
Reconciled, Business Activity 0358 Var... ans...20;
TAGLLLVAR
ans...24;
TAGLLLVAR
Reconciled, Card Acceptor ID 0373 015 ans-15; TAGLLL
Reconciled, File 0300 025 n-25; TAGLLL


Reconciled, Member Activity 0302 001 a-1; TAGLLL
Reconciled, Message Reason Code 0371 004 n-4; TAGLLL
Reconciled, Processing Code 0374 002 n-2; TAGLLL
Reconciled, Settlement Activity 0359 Var... ans...67;
TAGLLLVAR
Reconciled, Transaction Function 0372 007 n-7; TAGLLL
Reconciled, Transmission 0298 025 n-25; TAGLLL
Recurring Payment Indicator 0022 001 n-1; TAGLLL
Regular Hours Rate 0724 007 n-7; TAGLLL
Regular Hours Worked 0723 007 n-7; TAGLLL
Regular Mileage Charge 0695 012 n-12; TAGLLL
Rental Agreement Number 0544 009 ans-9; TAGLLL
Rental Check-out Date 0551 006 n-6; TAGLLL
Rental Class ID 0568 004 ans-4; TAGLLL
Rental Location City 0564 Var… ans…25;
TAGLLLVAR
Rental Location Country 0566 003 as-3; TAGLLL
Rental Location ID 0567 010 ans-10; TAGLLL
Rental Location State/Province 0565 003 ans-3; TAGLLL
Rental Rate 0553 013 ans-13; TAGLLL
Rental Return City 0546 Var… ans…25;
TAGLLLVAR
Rental Return Country 0548 003 ans-3; TAGLLL
Rental Return Date 0550 006 n-6; TAGLLL
Rental Return Location ID 0549 010 ans-10; TAGLLL
Rental Return State/Province 0547 003 ans-3; TAGLLL
Renter Name 0545 Var… ans…40;
TAGLLLVAR
Requestor Name or ID 0729 Var… ans…40;
TAGLLLVAR
Restaurant Charges 0584 014 ans-14; TAGLLL
Restricted Ticket Indicator 0713 001 an-1; TAGLLL


Retrieval Document Code 0228 001 n-1; TAGLLL
Risk Management Approval Code 0261 011 n-11; TAGLLL
Room Rate 0580 013 n-13; TAGLLL
Room Service Charges 0540 014 ans-14; TAGLLL
Second Presentment/Fee Collection 0267 Var... ans...127;
Resubmission Data TAGLLLVAR
Service Class Code 0522 002 ans-2; TAGLLL
Service Descriptor 0735 Var… ans…40;
TAGLLLVAR
Settlement Data 1 0159 Var... ans...67;
TAGLLLVAR
Settlement Data 2 0161 Var... ans...67;
TAGLLLVAR
Settlement Indicator 0165 Var... ans...30;
TAGLLLVAR
Ship Date 0612 006 n-6; TAGLLL
Ship-From Postal Code 0613 010 ans-10; TAGLLL
Shipping Net Amount 0737 014 ans-14; TAGLLL
Shipping Party Address 0745 Var… ans…300;
TAGLLLVAR
Shipping Party Contact 0747 Var… ans…305;
TAGLLLVAR
Shipping Party Information 0744 Var… ans…150;
TAGLLLVAR
Shipping Party Postal Information 0746 Var… ans…41;
TAGLLLVAR
Sole Proprietor Name 0172 Var... ans...30;
TAGLLLVAR
Source File ID 0280 025 n-25; TAGLLL
Source Message Number ID 0138 008 n-8; TAGLLL
Stop Over Code 0525 001 ans-1; TAGLLL
Subtotal Amount 0733 014 ans-14; TAGLLL
Supervisor/Reports To 0730 Var… ans…40;
TAGLLLVAR


Tax Amount 1 0634 006 n-6; TAGLLL
Tax Amount 2 0635 006 n-6; TAGLLL
Tax Exempt Indicator 0686 001 an-1; TAGLLL
Taxes 0537 012 n-12; TAGLLL
Temp Start Date 0727 006 n-6; TAGLLL
Temp Week Ending 0728 006 n-6; TAGLLL
Terminal Type 0023 003 ans-3; TAGLLL
Test Case Traceability Identifiers 0799 Var… ans…165;
TAGLLLVAR
Ticket Number 0506 015 ans-15;TAGLLL
Time Sheet Number 0731 Var… ans…20;
TAGLLLVAR
Total Amount Charged on Credit Card 0539 014 ans-14; TAGLLL
Total Authorized Amount 0693 014 ans-14; TAGLLL
Total Charges 0532 014 ans-14; TAGLLL
Total Fare 0512 012 n-12; TAGLLL
Total Fees 0513 012 n-12; TAGLLL
Total Miles (or Kilometers) 0556 004 n-4; TAGLLL
Total Non-Room Charges 0534 014 ans-14: TAGLLL
Total Non-Room Tax Amount 0705 014 ans-14; TAGLLL
Total Room Nights 0703 004 n-4; TAGLLL
Total Room Tax 0581 014 ans-14; TAGLLL
Total Tax Amount 0597 012 ans-12; TAGLLL
Total Tax Collected Indicator 0598 001 ans-1; TAGLLL
Total Taxes 0514 012 n-12; TAGLLL
Total, Transaction Number 0402 010 n-10; TAGLLL
Towing Charges 0700 012 n-12; TAGLLL
Tracking Number or Pickup Number 0736 Var… ans…40;
TAGLLLVAR
Transaction Description 0501 016 n-16; TAGLLL


Transaction Supplemental Data 1 0604 Var… ans…672;
TAGLLLVAR
Transaction Supplemental Data 2 0605 Var… ans…672;
TAGLLLVAR
Transmission ID 0110 025 n-25; TAGLLL
Transportation Charges 0542 014 ans-14; TAGLLL
Travel Agency Code 0510 008 ans-8; TAGLLL
Travel Agency Name 0511 Var... ans…25;
TAGLLLVAR
Travel Authorization Code 0716 Var… ans…64;
TAGLLLVAR
Travel Date 0520 006 n-6; TAGLLL
Type of Supply 0685 002 an-2; TAGLLL
Unit of Measure 0743 Var… ans…3;
TAGLLLVAR
Unit Price 0646 013 n-13; TAGLLL
Unique Invoice Number 0678 Var… ans…17;
TAGLLLVAR
Unique VAT Invoice Reference Number 0687 Var… ans…17;
TAGLLLVAR
User Account Number 0624 Var… ans…40;
TAGLLLVAR
User Name 0619 Var… ans…40;
TAGLLLVAR
User Telephone Number 0625 Var… ans…25;
TAGLLLVAR
Valet Charges 0707 014 ans-14; TAGLLL
Vehicle Insurance 0559 013 ans-13; TAGLLL
Vehicle Number 0630 Var... ans…17;
TAGLLLVAR
Weekly Rental Amount 0692 012 n-12; TAGLLL

PDS 0002—Product Identifier

Product Identifier (PDS 0002) identifies the product code assigned to the
transaction. The product code is associated with the DE 2 Primary Account
Number (PAN).
Note This PDS is not currently supported in GCMS.
Attributes
ans-3; TAGLLL
Tag Field: 0002

Subfields: none
Justification: left
Usage
The following table shows the usage of this PDS (whether it is mandatory,
conditional, optional, system provided, or not required) in applicable
messages:
Usage
First Presentment/1240 • X M
First Chargeback/1442 and Arbitration Chargeback/1442 • X M
Second Presentment/1240 • X M
Fee Collection (Handling Fees)/1740 • X M

The clearing system provides PDS 0002 to indicate the product code assigned
to the transaction. Some examples of current credit and debit product codes
are:
Product Code Card Type

MCC MasterCard Card
MasterCard Credit (mixed BIN)
MPL Platinum MasterCard
MCB MasterCard BusinessCard Card
MasterCard Certified Corporate Card
MasterCard Executive BusinessCard Card
MasterCard Executive Corporate Card
MasterCard World BusinessCard Card
MasterCard World Corporate Card
MCE MasterCard Electronic
MCF MasterCard Fleet Card
MCG MasterCard Gold Card
MCP MasterCard Purchasing Card
MCS MasterCard Standard Card
MCW MasterCard World Card
MCD MasterCard Debit
MDG Debit Gold MasterCard®
MDO Debit Other
MDP Debit Platinum
MDR Debit Brokerage a
MDS Debit MasterCard® card

MPP Pre-Paid
.a Brokerage accounts will not be defined as debit if the account is swept in 14 or more days.
Brokerage accounts swept under 14 days are considered debit accounts.
Note Some product codes include multiple card types such as MCC and MCB in the
table above.

The product codes in the above table are representative of the credit and debit
product codes recognized by the clearing system. Therefore, the card type
itself may have a different description, and differing associated product types,
but the clearing system recognizes the same product type identifier. For
example, only MCB is recognized by GCMS and applies to seven different card
types, where each of those card types has its own product type within other
MasterCard applications.

PDS 0005—Message Error Indicator

Message Error Indicator (PDS 0005) identifies the location, severity, and
general description of data element errors in a message.
Attributes
ans...140; TAGLLLVAR
Tag Field: 0005
Data Field: variable length 14–140 positions in increments of 14
Subfields: 4 fixed-length subfields for each error occurrence
Occurrences: 1–10
Usage
messages:
Usage
s1 Data Element ID • X M
s2 Error Severity Code • X M
s3 Error Message Code • X M
s4 Subfield ID • X M
The clearing system provides PDS 0005 in Message Exception/1644 and File
Reject/1644 messages to indicate the location of fatal or non-fatal errors,
warnings, or adjustments in messages that it processed.
The clearing system may report up to a maximum of 10 exception conditions

detected in a message.

Subfields
The clearing system reports each exception condition using three subfields,
formatted as indicated in the following table:

1 1–5 Data Element ID an-5 left
2 6–7 Error Severity Code n-2 n/a
3 8–11 Error Message Code an-4 n/a
4 12–14 Subfield ID n-3 n/a
The clearing system repeats the subfield format described in the previous table
from one to 10 times in PDS 0005 to report a maximum of 10 error conditions
in a single message.
Subfield 1: Data Element ID

The Data Element ID identifies the ISO data element or PDS where the error
occurred. ISO data elements are identified with the prefix D. This is followed
by the data element number right-justified with leading zeros so that the
number fills four positions. For example, D0003 indicates DE 3, D0100
indicates DE 100, and so on.
PDSs are identified with the prefix P followed by the four-digit tag ID. For
example, P0002 indicates PDS 0002, P0146 indicates PDS 0146, and so on.
This subfield may contain spaces if the error is a “general” error not related to
a specific data element or PDS.
Subfield 2: Error Severity Code

The Error Severity Code indicates the severity of the error the clearing system
detects. Some errors may affect the clearing system or destination processor’s
ability to process a message successfully (fatal error), while other errors may
be relatively minor in nature and are reported as “warning” conditions to alert
members to potential problems or invalid data fields.
Message data element errors are listed in PDS 0005 in severity order. All fatal
errors are presented first, followed by adjustments, then warning errors.

Values for this subfield are listed in the following table:
Value Description
00 Fatal Error; invalid or incomplete data was encountered that prevented the
clearing system from processing the transaction.
01 Adjustment; this is a non-fatal error; the message may be processed
normally, however the clearing system has corrected, adjusted, or over-
written the data element or PDS original value.
02 Warning; this is a non-fatal error; the clearing system detected invalid data
in a data element or PDS; the message was processed normally, but
processing (such as interchange rate calculation) may have been impacted
by invalid, missing, or incomplete data.
Subfield 3: Error Message Code

The Error Message Code is a four-digit value that refers to a specific edit error
message to identify the error condition.
Refer to appendix C of this manual or the following manuals for a complete

list of error codes and error messages:
• IPM Pre-edit and Utilities Guide—Mainframe Version
• IPM Pre-edit and Utilities Guide—Windows® NT 4.0 Version
Subfield 4: Subfield ID
The three-position subfield ID of the element in error. This subfield will
contain zeros if the element in error is not defined with subfields.

PDS 0006—Applied Business Service Arrangement

Applied Business Service Arrangement (PDS 0006) identifies, for a rejected
message, the card program identifier and business service arrangement for
which the transaction was being evaluated at the time of the reject.
This PDS is included in a Message Exception/1644 message when a message

fails an edit not related to the selection of the acceptance brand and business
service arrangement information.
Attributes
ans-10; TAGLLL
Tag Field: 0006

Subfields: 3
Justification: left
Usage
messages:
Usage
Message Exception/1644 • X C
s2 Business Service Arrangement Type • X C

Subfields
This PDS consists of three subfields as defined in the following table:

1 1–3 Card Program Identifier ans-3 left
2 4 Business Service Arrangement ans-1 left
Type Code
3 5–10 Business Service ID Code ans-6 left
Subfield 1: Card Program Identifier

The Card Program Identifier is a three-character code that identifies the card
program or financial network to which a transaction belongs.
Value Description
CIR Cirrus
DMC Debit MasterCard®
MCC MasterCard® Credit
MSI Maestro
PRO Sweden domestic brand
PVL Private label
SOL U.K. domestic Solo brand
SWI U.K. domestic Switch brand

Subfield 2: Business Service Arrangement Type Code

The Business Service Arrangement Type Code is a one-position numeric value
that identifies the interchange relationship between the transaction’s
participants. Business service arrangement type codes supported by the
clearing system are:
Value Description
1 Interregional
2 Intraregional
3 Intercountry
4 Intracountry
8 Member-to-member
Subfield 3: Business Service ID Code

The Business Service ID Code is a six-position value that identifies the
business service assigned to the transaction for rulings and reconciliation. See
PDS 0158, subfield 3 for Business Service ID code format and values.

PDS 0020—Issuer Currency Conversion Rate (ICCR) Effective Date
PDS 0020—Issuer Currency Conversion Rate (ICCR)

Effective Date
Issuer Currency Conversion Rate (ICCR) Effective Date (PDS 0020) identifies
the date the ICCR became effective in the clearing system.
Attributes
n-6; TAGLLL
Tag Field: 0020
Subfields: None
Justification: n/a
Usage
messages:
Usage
First Chargeback/1442 C • •
This PDS contains the date (in YYMMDD format) that the percentage rate used
in the ICCR adjustment calculation became effective in the clearing system.
The clearing system provides this PDS for First Presentment/1240 messages in
which ICCR was applied. Issuers are to retain and return this PDS in a First
Chargeback/1442 if it was present in the First Presentment/1240.
In First Chargeback/1442 messages, the clearing system uses PDS 0020 and
historical rate information to remove ICCR from the chargeback amount in
Amount, Transaction (DE 4) before sending the message to the acquirer. The
clearing system also removes PDS 0020 from the chargeback message before
forwarding the message to the acquirer.

PDS 0021—Issuer Currency Conversion Rate (ICCR) Percentage
PDS 0021—Issuer Currency Conversion Rate (ICCR)

Percentage
Issuer Currency Conversion Rate (ICCR) Percentage (PDS 0021) identifies the
percentage rate used to calculate the ICCR amount.
Attributes
n-7; TAGLLL
Tag Field: 0021
Subfields: None
Justification: n/a
Usage
messages:
Usage
This PDS contains the percentage rate that was applied in the ICCR adjustment
calculation.
The clearing system provides this PDS for First Presentment/1240 messages in
which ICCR was applied.
The element contains three numbers to the left of the decimal and four
numbers to the right of the decimal. For example, a 1.5% ICCR percentage is
expressed as a value of 0015000.

PDS 0022—Recurring Payment Indicator
PDS 0022—Recurring Payment Indicator

Recurring Payment Indicator (PDS 0022) identifies that the transaction is a
recurring payment transaction.
Attributes
n-1; TAGLLL
Tag Field: 0022
Data Field: fixed length 1 position
Subfields: None
Usage
messages:
Usage
A recurring payment transaction refers to a transaction such as monthly

Internet service or insurance payments that are automatically posted to the
cardholder account on a regular basis. A value of 4 is the only valid value for
this PDS.

PDS 0023—Terminal Type

Terminal Type (PDS 0023) identifies the type of terminal used at the point of
interaction.
Attributes
ans-3; TAGLLL
Tag Field: 0023
Subfields: None
Justification: Left
Usage
messages:
Usage
Terminal Type (PDS 0023) is required in non-reversal First Presentment/1240,

First Chargeback/1442, Second Presentment/1240, and Arbitration
Chargeback/1442 messages.
Transactions submitted in the U.S. region with the following terminal types
may not have an Interchange Rate Designator (subfield 4 of Business Activity
[PDS 0158]) value of 60 (Corporate Face-to-Face) or 92 (Key-Entered):
• CT1, Automated Dispensing Machine, (Cardholder Activated Terminal
[CAT] Level 1)
• CT2, Self-Service Terminal (CAT Level 2)
• CT3, Limited Amount Terminal (CAT Level 3)
• CT4, In-Flight Commerce Terminal (CAT Level 4)

Transactions submitted with a PDS 0023 value of CT1 (Automated Dispensing

Machine) or CT2 (Self-Service Terminal) and a Card Acceptor Business Code
(DE 26) value of 5542, qualify for the U.S. region Convenience Purchases
Interchange Program (IRD 23).
First Presentment/1240 transactions submitted for the International Merchant

Universal Card Authentication Field (UCAF) Interchange Program (IRD 24) or
the International Full UCAF Interchange Program (IRD 79) must have a value
of CT6 (electronic commerce transaction) in PDS 0023.
In-flight Commerce Gaming Transactions

Transactions submitted with a PDS 0023 value of CT4 (In-flight Commerce
Terminal) that contain a Cardholder Transaction Type (subfield 1
of Processing Code [DE 3]) of 18 (Unique Transaction) or 20 (Credit) are
considered in-flight commerce gaming transactions. If DE 3s1=18, they are
gaming losses. If DE 3s1=20, they are gaming wins.
Gaming wins and gaming losses must contain one of the following values in
subfield 4 of PDS 0158:
• 61, International Corporate Standard
• 63, International Corporate Purchase Standard
• 65, U.S. Corporate Standard
• 68, U.S. Corporate Data Rate I
• 75, 85, and 95, U.S. Consumer Standard and International Standard
Interchange
• 78, 88, and 98, Merit I
Gaming wins and gaming losses must contain a DE 2 PAN that is not blocked
from participating in in-flight gaming.
The DE 4 transaction amount for gaming wins is limited to USD 3500. The
transaction amount for gaming losses is limited to USD 350.

Values
Terminal Type codes for point-of-interaction (POI) terminal devices are in the
following table:
Value Description
ATM ATM terminal
CT1 CAT level 1 (automated dispensing machine).
CT2 CAT level 2 (self-service terminal).
CT3 CAT level 3 (limited amount terminal).
CT4 CAT level 4 (in-flight commerce terminal).
CT6 CAT level 6 (electronic commerce transaction).
CT7 CAT level 7 (transponders).
MAN Manual, no terminal.
NA Terminal type data unknown or not available. (The third position of this
value is a space.)
POI POI terminal.
If present, PDS 0023 must be left justified and cannot contain all low-values,
all high-values, or all spaces.

PDS 0025—Message Reversal Indicator

Message Reversal Indicator (PDS 0025) identifies a message as a reversal of a
previous message.
Attributes
an...7; TAGLLLVAR
Tag Field: 0025
Subfields: 2
Usage
messages:
Usage
s1 Message Reversal Indicator C X C
s2 Central Site Processing Date of Original Message C X C
s2 Central Site Processing Date of Original Message O X C

Usage
s1 Message Reversal Indicator • X C
s2 Central Site Processing Date of Original Message • X C
PDS 0025 in an advice or notification message indicates that a previously-

transmitted message was transmitted in error and should be ignored or
reversed.
The value in PDS 0025 in a Message Exception/1644 message is taken from the
actual rejected message. This PDS is not provided in a File Reject/1644
message. PDS 0026 is provided in File Reject/1644 message if it was present in
the File Header/1644 message of the rejected file.
All other data elements in the message remain unchanged from the original
message to provide sufficient information for that message to be nullified or
reversed.
Note An R in subfield 1 reverses the original funds flow.

Subfields
This PDS should not be present unless a message is to be reversed. The
subfield formats are in the following table:

1 1 Message Reversal Indicator a-1; R or space n/a
2 2–7 Central Site Processing Date n-6; YYMMDD n/a
of Original Message
Subfield 1: Message Reversal Indicator

If a message is not a reversal, members/processors should not provide
PDS 0025.
If a member/processor does provide PDS 0025 in a clearing message, then

subfield 1 is always required and must contain an R or space.
The clearing system may provide PDS 0025 in a message if it is part of a “full
file reversal” that the original message sender requested. If this is the case,
then subfield 1 of PDS 0025 contains an R if this message is a reversal of a
previous message in which PDS 0025 was not present. Subfield 1 contains a
space if this message is a reversal of a previous message in which PDS 0025
subfield 1 contained an “R”. Refer to PDS 0026 in this chapter for additional
information on full file reversals.
Subfield 2: Central Site Processing Date of Original Message

Subfield 2 is required only when PDS 0025 is present in First Presentment/1240
messages. Subfield 2 must contain a valid date in the format YYMMDD.
Subfield 2, if present, must contain a date that is less than or equal to the
clearing system processing date.
When PDS 0025 is present in First Presentment/1240 messages, the clearing

system uses subfield 2 of PDS 0025 to obtain the correct foreign exchange
rates from the currency conversion rate history file.
When PDS 0025 is present in First Chargeback/1442, Second

Presentment/1240, or Arbitration Chargeback/1442 messages, the clearing
system uses the current business processing date for currency conversion.

PDS 0026—File Reversal Indicator

File Reversal Indicator (PDS 0026) identifies the entire file as a reversal of a
previous file.
Attributes
an...7; TAGLLLVAR
Tag Field: 0026
Subfields: 2
Usage
messages:
Usage
File Header (Member-Generated)/1644 C • •
s1 File Reversal Indicator C • •
s2 Central Site Processing Date of Original File C • •
Message Exception and File Reject/1644 • X C
s1 File Reversal Indicator • X C
s2 Central Site Processing Date of Original File • X C
The presence of PDS 0026 in a File Header (Member-Generated)/1644

indicates that the clearing system should reverse all messages contained in the
logical file. The clearing system manages this process by inserting or revising
Message Reversal Indicator (PDS 0025) in each message.
Note An R in subfield 1 reverses the original funds flow.

When PDS 0026 is present in the File Header (Member-Generated)/1644 and

the individual transaction message:
• Does not contain PDS 0025, the clearing system builds PDS 0025 using the
values submitted in PDS 0026 in the File Header (Member-
Generated)/1644.
• Already contains PDS 0025, the value of subfield 1 is changed from R to a
space or a space to R.
The value in subfield 2 of PDS 0025 remains unchanged.
Example 1
If… Then…
• PDS 0026 subfield 1 is R and The clearing system:
subfield 2 is 991013 in the File • Changes R to space in PDS 0025
Header (Member-Generated)/1644, subfield 1 of the First Presentment/1240,
and and
• One of the First Presentment/1240 • Retains the value of 991012 in PDS 0025
messages contains PDS 0025 with subfield 2 using the currency conversion
an R in subfield 1 and a date of rates of 991012 to settle the transaction.
991012 in subfield 2,
Example 2
If… Then…
• PDS 0026 subfield 1 is R and The clearing system:
subfield 2 is 991013 in the File • Changes space to an R in PDS 0025,
Header (Member-Generated)/1644, subfield 1 of the First Presentment/1240,
and and
• One of the First Presentment/1240 • Retains the value of 991011 in PDS 0025
messages contains PDS 0025 subfield 2 using the currency conversion
with a space in subfield 1 and rates of 991011 to settle the transaction.
a date of 991011 in subfield 2,

Subfields
This PDS should not be present unless the entire file is to be reversed. The
subfield formats are in the following table:

1 1 File Reversal Indicator a-1; R n/a
2 2–7 Central Site Processing Date n-6; n/a
of Original File YYMMDD
Subfield 1: File Reversal Indicator

If PDS 0026 is present, subfield 1 is always required and must contain an R.
Subfield 2: Central Site Processing Date of Original File

If PDS 0026 is present, subfield 2 is always required and must contain a valid
date equal to or less than the current business processing date.

PDS 0043—Program Registration ID

The Program Registration ID (PDS 0043) monitors and tracks a participant’s
activity in special promotion programs, such as Quick Payment Services (QPS),
Supermarket, Service Industries, Payment Transactions, and Warehouse Club
programs.
Attributes
ans-3; TAGLLL
Tag Field: 0043
Subfields: None
Justification: Left
Usage
messages:
Usage

The transaction originator (the merchant or the acquirer) supplies the

information in this PDS. The value in PDS 0043 indicates that the acquirer or
merchant is certified to participate in a program such as Supermarket,
Warehouse Club, Service Industries, or QPS. It contains the program
registration identifier. PDS 0043 must be present in First Presentment/1240
transactions submitted for the following U.S. region interchange programs,
unless the transaction is a credit, reversal, or Collection Only transaction:
IRD Description
71, 81 Supermarket Base
13, 14, 15 Supermarket Tier 1, 2, or 3
91 Warehouse Club Base
16, 17, 18 Warehouse Club Tier 1, 2, or 3
23 Service Industries
Values
PDS 0043 values are established and administered under the authority of
brand-specific program and service management and marketing personnel.
Values are in the following table:
Value Description
PAA Prestigious Hotel (PH) transaction.
Qxx a QPS transaction.
Rxx Service Industries transaction.
Sxx Supermarket transaction.
Wxx Warehouse Club transaction.
PAY Payment Transaction.
a The xx is a MasterCard-assigned alphanumeric ID unique to each participant.
PDS 0043 Program Registration ID cannot contain all spaces or all zeros.
Printing PDS 0043 Information on Cardholder Statements


PDS 0052—Electronic Commerce Security Level Indicator

The Electronic Commerce Security Level Indicator (PDS 0052) provides
information about the Universal Cardholder Authentication Field (UCAF)
security protocol for international MasterCard card Internet transactions.
Attributes
n–3; TAGLLL
Tag Field: 0052

Length Field: 3 positions
Subfields: 3
Justification: see “subfields”
Usage
messages:
Usage
s1 Security Protocol C • C
s2 Cardholder Authentication C • C
s3 UCAF Collection Indicator C • C

Subfields
Number Position Name Attribute Justification

1 1 Security Protocol n-1 n/a
2 2 Cardholder Authentication n-1 n/a
3 3 UCAF Collection Indicator n-1 n/a
Subfield 1: Security Protocol

Security Protocol indicates the presence and type of security protocol present
in the authorization process. Subfield 1 is populated from the Authorization
Request/0100 message, Electronic Commerce Security Level Indicator/Security
Protocol (DE 48, subfield 42, position 1).
GCMS does not edit this subfield.
Subfield 2: Cardholder Authentication

Cardholder Authentication indicates the type of Cardholder Authentication
used in the authorization process. Subfield 2 is populated from the
Authorization Request/0100 message, Electronic Commerce Security Level
Indicator/Cardholder Authentication (DE 48, subfield 42, position 2).

Subfield 3: UCAF Collection Indicator

UCAF Collection Indicator identifies the level of UCAF supported in the
authorization process. Subfield 3 is populated from the Authorization
Request/0100 message, Electronic Commerce Security Level Indicator/UCAF
Status (DE 48, subfield 42, position 3). Valid values include the following:
Value Description
0 Not supported at the merchant’s Web site
Supported by the merchant, but UCAF data was not present in the
1 Authorization Request/0100 message
Both merchant and issuer are UCAF enabled, as indicated in the
Authorization Request/0100 and Authorization Request
2 Response/0110 messages.
Values
A value of 0 in UCAF Collection Indicator (PDS 0052, subfield 3) is not edited
in the clearing system.
First Presentment/1240 transactions submitted with a value of 24 (Merchant

UCAF) in Business Activity/Interchange Rate Designator (PDS 0158, subfield 4),
must include Electronic Commerce Security Level Indicator (PDS 0052). The
value in UCAF Collection Indicator (PDS 0052, subfield 3) must be a 1.
First Presentment/1240 transactions submitted with a value of 79 (Full UCAF)

in Business Activity/Interchange Rate Designator (PDS 0158, subfield 4), must
include Electronic Commerce Security Level Indicator (PDS 0052). The value
in UCAF Collection Indicator (PDS 0052), subfield 3) must be a 2.

PDS 0105—File ID
PDS 0105—File ID
File ID (PDS 0105) uniquely identifies a logical data file to be exchanged
between a member or processor and the clearing system.
Attributes
n-25; TAGLLL
Tag Field: 0105
Subfields: 4
Usage
messages:
Usage

PDS 0105—File ID
Usage
This PDS comprises four subfields that indicate the file type, the file processing
date, the ID of the member or processor associated with the file, and a file
sequence number to uniquely identify the file and delivery cycle (1–6). The
combination of these four subfields must together form a value that uniquely
identifies all logical files to or from a member processing center.
For member-generated files, the clearing system retains 180 days of file ID
history for each member or processor and uses this information to edit
duplicate file IDs. A clearing file rejects in its entirety if it contains a duplicate
File ID. A file ID is considered a duplicate if subfields 2, 3, and 4 of PDS 0105
plus subfield 1 of File Reversal Indicator (PDS 0026) match an entry in the file
ID history file.
Subfields
This PDS consists of four subfields as defined in the following table:

1 1–3 File Type n-3 n/a
2 4–9 File Reference Date n-6 n/a
3 10–20 Processor ID n-11 right
4 21–25 File Sequence Number n-5 right

PDS 0105—File ID
Subfield 1: File Type

The File Type is a three-digit code that indicates the type of logical data file
being transmitted. Values are in the following table:
Value Description
001 Clearing file: MasterCard-generated.
002 Clearing file: Member-generated.
003 Early Reconciliation File: MasterCard-generated.
Subfield 2: File Reference Date

For member-generated logical files, the File Reference Date is the date that the
transmitting member or processor processed or submitted the file. It must be
less than or equal to the clearing system’s business processing date. The
required date format is YYMMDD.
For MasterCard-generated logical files this subfield will contain the clearing
system’s business processing date.
Subfield 3: Processor ID
For member-generated logical files this subfield contains the member ID of the
member or processor submitting the file.
For MasterCard-generated logical files this subfield contains the member ID of

the member or processor receiving the file.
Subfield 4: File Sequence Number

The File Sequence Number is a five-digit value that the member or processor
submitting the file assigns. It must be unique for each Processor ID and File
Reference Date combination.

PDS 0105—File ID
For member-generated logical files this subfield must be numeric. Members

that submit clearing files from multiple locations each day may choose to
assign specific ranges of sequence numbers to each location to ensure that file
IDs are not duplicated.
For MasterCard-generated logical files this subfield contains the two-position

clearing cycle indicator, followed by a one-position delivery cycle and two-
position sequential number that is incremented for each processing file, and
clearing cycle, throughout a clearing processing day.
PDS 0105 Subfield 4 in MasterCard-generated files
Position(s) Name Attribute Justification

1–2 Clearing Cycle n-2 right
Note: This will be 99 if the
member receives clearing files
containing data from two or
more clearings.
3 Delivery Cycle (Values = 1–6)
4–5 Sequence Number right

PDS 0110—Transmission ID
Transmission ID (PDS 0110) uniquely identifies a physical transmission or
grouping of logical files to be exchanged between a member or processor and
the clearing system. Each transmission may contain multiple logical files that
File ID (PDS 0105) identifies.
Attributes
n-25; TAGLLL
Tag Field: 0110
Subfields: 4
Usage
messages:
Usage
File Header (Member-Generated)/1644 O • •
s1 Transmission Type O • •
s2 Transmission Reference Date O • •
s3 Processor ID O • •
s4 Transmission Sequence Number O • •

Usage
Members that “stack” multiple logical files in a physical transmission may use
this optional PDS. Members may provide it in File Header/1644 messages to
tie together all logical files in the physical transmission.
If present, the same PDS 0110 value should be placed into PDS 0110 in each
File Header/1644 in the physical transmission. This causes the clearing system
to generate reconciliation information that accumulates data at both the
transmission level and the individual file level. This reconciliation information
is available only at the acknowledgement level.
If not present, the clearing system generates reconciliation information that

accumulates data at the individual logical file level. Transmission-level totals
are not provided.
Subfields

1 1–3 Transmission Type n-3 n/a
2 4–9 Transmission Reference Date n-6 n/a
4 21–25 Transmission Sequence Number n-5 right
The combination of these four subfields must together form a value that
uniquely identifies each transmission or grouping of logical files within a
business day from a member processing center.

Subfield 1: Transmission Type

The Transmission Type is a three-digit code that indicates the transmission
type as follows:
Value Description
002 Clearing transmission: member-generated.
Subfield 2: Transmission Reference Date

The Transmission Reference Date is the date that the originating member or
processor processed or submitted the transmission. It must be less than or
equal to the clearing system’s business processing date. The required date
format is YYMMDD.
Subfield 3: Processor ID
For member-generated transmissions, this subfield contains the member ID of
the member or processor submitting the transmission.
Subfield 4: Transmission Sequence Number

The Transmission Sequence Number is a five-digit number the transmission
originator assigns. It should be unique for each combination of Transmission
Type, Transmission Reference Date, and Processor ID. GCMS does not edit for
duplicate transmission IDs.

PDS 0122—Processing Mode
PDS 0122—Processing Mode

Processing Mode (PDS 0122) indicates the type of processing to be performed
on transaction messages.
Attributes
ans-1;TAGLLL
Tag Field: 0122
Subfields: None
Justification: n/a
Usage
messages:
Usage
PDS 0122 indicates the type of processing (such as production or test) to be

applied to an entire data file of transaction messages.
Values
Processing Mode values are in the following table:
Value Description
P Production.
T Test.

PDS 0137—Fee Collection Control Number
PDS 0137—Fee Collection Control Number

Fee Collection Control Number (PDS 0137) contains a financial control number
(“reference number”) a Fee Collection message originator assigns.
Attributes
n…20; TAGLLLVAR
Tag Field: 0137
Subfields: None
Usage
messages:
Usage
The PDS assists members in referencing and reconciling various posted

miscellaneous fees and billings using the Fee Collection message.
A member institution may assign PDS 0137 as a documentation reference for

member-generated Fee Collection messages sent to another member.
Members must submit a minimum of 17 positions, and a maximum of 20

positions for PDS 0137. The information must be numeric and right justified.
The clearing system also uses this PDS to provide control numbers on Fee
Collection (Clearing System-Generated)/1740 messages.
In all Fee Collection/1740 messages, PDS 0137 is required and must be the
same on the initial Fee Collection and all subsequent returns.

PDS 0138—Source Message Number ID
PDS 0138—Source Message Number ID

Source Message Number ID (PDS 0138) contains the message sequence
number from a previously-submitted file’s message.
Attributes
n-8; TAGLLL
Tag Field: 0138
Subfields: None
Usage
messages:
Usage
This PDS identifies in Message Exception/1644 messages the message

sequence number of a rejected message from a previously-transmitted data file.
It contains the value from Message Number (DE 71) from the rejected message.
This PDS is present if the clearing system can parse the rejected message.

PDS 0146—Amounts, Transaction Fee

Amounts, Transaction Fee (PDS 0146) presents all fee amounts associated with
a transaction. This PDS may accommodate a total of one to 12 different fee
types.
Attributes
n...336; TAGLLLVAR
Tag Field: 0146

Length Field: 3 positions, value = 028–336 in increments of 28
Subfields: 7 subfields for each transaction fee occurrence
Occurrences: 1–12
Usage
messages:
Usage
s1 Fee Type Code C X C
s2 Fee Processing Code C X C
s3 Fee Settlement Indicator C X C
s4 Currency Code, Fee C X C
s5 Amount, Fee C X C
s6 Currency Code, Fee, Reconciliation C X C
s7 Amount, Fee, Reconciliation C X C

Usage
First Chargeback/1442 and Arbitration Chargeback/1442 O X C
For ATM transactions submitted by the MasterCard Debit Switch (MDS), this
element is mandatory.
For bilaterally settled and Collection Only transactions, this element is optional.
Fees are assessed in an appropriate currency according to card program

identifier, program, or service rules. For example, a fee assessed to the
acquirer, such as a variable transaction interchange fee, may be assessed in the
transaction currency; a regional clearing system processing fee might be
assessed in the preferred currency of the country in which the clearing system
is operated.

If the transaction is classified as bilateral settlement (indicated by a B in

subfield 1 of Settlement Indicator [PDS 0165]), or a Collection Only (indicated
by a value of C in subfield 1 of Settlement Indicator [PDS 0165]), the message
originator may populate PDS 0146 with “expected” fees and the clearing
system passes them to the receiving member without recalculating them. If the
originator of a bilaterally settled or Collection Only transaction does not
provide PDS 0146, it will not be present at all in the message.
Subfields
This PDS may contain one to 12 occurrences of transaction fees. Each
transaction fee consists of seven subfields as defined in the following table.
Each fee requires 28 positions; the length of this PDS must be a multiple of 28,
with a maximum length of 336 positions.

1 1–2 Fee Type Code n-2 n/a
A code in the range 00–99 to
indicate the fee type.
2 3–4 Fee Processing Code n-2 n/a
A code that indicates the entity
to be debited and the entity to
be credited for this fee amount.
3 5–6 Fee Settlement Indicator n-2 n/a
Identifies the PDS location of the
settlement service information
applicable to this fee.
4 7–9 Currency Code, Fee n-3 n/a
The ISO numeric currency code
for the Amount, Fee (subfield 5).
5 10–17 Amount, Fee n-8 n/a
The transaction fee amount in
the calculated currency of the
fee.
6 18–20 Currency Code, Fee, n-3 n/a
Reconciliation
The ISO numeric currency code
for the Amount, Fee,
Reconciliation (subfield 7).
7 21–28 Amount, Fee, Reconciliation n-8 n/a
Fee amount in the reconciliation
currency (payment currency).

All subfields are present for each fee occurrence. If the fee reconciliation
(payment) currency is the same as the fee calculation currency, fee subfields 6
and 7 contain the same values as subfields 4 and 5.
When the transaction originator provides PDS 0146, subfield 3 may contain
zeros.
The values to be used for each fee subfield are described in the following text.
Subfield 1: Fee Type Code

Fee Type Codes the clearing system assigns are in the following table.
Member processing systems must be able to accommodate new fee types that
may be added at any time.
Value Description
00 Transaction interchange fee (fixed plus variable fee amount).
Subfield 2: Fee Processing Code

The Fee Processing Code identifies the entity to be debited and the entity to
be credited for the fee amount.
Valid values are in the following table:
Value Description
19 Debit transaction destination.
29 Credit transaction destination
00 Not applicable – May be used if member provides PDS 0146.
Subfield 3: Fee Settlement Indicator

The Fee Settlement Indicator identifies the settlement service PDS to which the
fee is associated for the purpose of financial reconciliation and settlement.

Value Description
00 Settlement services do not apply to this fee; fee settlement or fee billing
occurs as a separate activity and is not included in this transaction’s
reconciliation and settlement (usually applies when bilateral settlement
occurs).
01 Settlement data 1; this settlement service is identified in Settlement Data 1
(PDS 0159).
02 Settlement data 2; this settlement service is identified in Settlement Data 2
(PDS 0161).
Subfield 4: Currency Code, Fee

The Currency Code, Fee identifies the currency of Amount, Fee. This is the
currency in which the fee is calculated by the clearing system. For example, if
the fee is listed in MasterCard publications as a U.S. dollar fee, then subfields 4
and 5 will contain the fee in U.S. dollars.
The fee is defined in the calculated fee currency, and may include a fixed
amount, a percentage of the transaction amount, or both.
This subfield must contain a valid ISO numeric currency code.
Subfield 5: Amount, Fee

The Amount, Fee is the fee amount in the currency in which the fee is
calculated by the clearing system. In First Presentment/1240 messages, the
total interchange fees assessed must not be greater than the transaction
amount.
Subfield 6: Currency Code, Fee, Reconciliation

The Currency Code, Fee, Reconciliation identifies this fee’s reconciliation
(payment) currency.
Standard ISO numeric currency codes are used.
Subfield 7: Amount, Fee, Reconciliation

The Amount, Fee, Reconciliation is the Amount, Fee converted to the
reconciliation (payment) currency for the message recipient.

Related Required PDS

Currency Exponents (PDS 0148) must be present with PDS 0146 to identify the
transaction’s exponent.
Values
example, a transaction amount of USD 212.50 is expressed as 000000021250.

PDS 0148—Currency Exponents

Currency Exponents (PDS 0148) explicitly identifies the implicit decimal point
locations associated with each ISO standard currency code used in a message.
Attributes
ans...60; TAGLLLVAR
Tag Field: 0148
2 subfields for each currency exponent data
Subfields: occurrence
Occurrences: 1–15
Usage
messages:
Usage

Usage
Retrieval Request/1644 C • C
s1 Currency Code C • C
s2 Currency Exponent C • C
Fee Collection (Retrieval Fee Billing)/1740 C X M
s1 Currency Code C X M
s2 Currency Exponent C X M

This PDS identifies the decimal point location for all currency amounts in a
message.
Message originators must populate PDS 0148 with the currency exponents that
apply to any amount and currency code data elements, such as Amount,
Transaction (DE 4), Currency Code, Transaction (DE 49), and Amounts,
Original (DE 30) that they provide in a message.
The clearing system populates PDS 0148 with the currency exponents that
apply to any clearing system-provided amount and currency code data
elements, such as Amount Reconciliation (DE 5) and Currency Code,
Reconciliation (DE 50); Amount, Cardholder Billing (DE 6) and Currency Code,
Cardholder Billing (DE 51); or Amounts, Transaction Fee (PDS 0146).
Each currency code in the message should be presented only once in

PDS 0148, along with the corresponding currency exponent.
The clearing system validates the currency exponents in subfield 2 of PDS 0148
to ensure they are valid for the currency codes in subfield 1. If they are not
valid, the clearing system rejects the transaction.
For example, assume that a transaction occurs between Canadian members in

U.S. dollars (currency code 840, exponent 2). The clearing system assesses
fees in Canadian dollars (currency code 124, exponent 2):
• The acquirer submits a First Presentment/1240 in which DE 49 contains
840. PDS 0148 also must be present, and must contain a single value of
8402, representing currency code 840 and currency exponent 2.
• The clearing system then calculates fees and presents them in PDS 0146.
Because the fees are in a currency that is not yet present in PDS 0148, the
clearing system adds a second occurrence to PDS 0148, containing a value
of 1242 to indicate currency code 124 and currency exponent 2.
• The clearing system then calculates DE 5 and DE 6 in Canadian dollars
(currency code 124) and adds them to the message, along with their
related currency codes of DE 50 and DE 51. Because currency code 124 is
already present in PDS 0148, the clearing system does not add any more
values to PDS 0148.
• The issuer receives the First Presentment/1240 containing all of the amount
and currency data elements and PDSs previously described (DE 4 and
DE 49; DE 5 and DE 50; DE 6 and DE 51; PDS 0146; and PDS 0148).
PDS 0148 contains two data occurrences with values of 8402 and 1242,
respectively.

Subfields
This PDS may contain from one to 15 occurrences of currency exponent
information. Each occurrence consists of two subfields as defined in the
following table. Each occurrence requires four positions; the length of this
PDS must be a multiple of four, with a maximum length of 60 positions.

1 1–3 Currency Code n-3 n/a
2 4 Currency Exponent an-1 n/a
Subfield 1: Currency Code

Currency Code is an ISO-standard currency code that identifies the currency
type.
Subfield 2: Currency Exponent

Currency Exponent explicitly identifies the implied decimal position applicable
to the ISO standard currency code.
A 0 indicates that the decimal point immediately follows the least significant
digit of the related “amount” data.
Values in the range 1–5 indicate that the decimal point is located 1–5 positions
to the left of the least significant digit of the related “amount” data.
Values in the range A–E indicate that the decimal point is located 1–5 positions
to the right of the least significant digit of the related “amount” data. (Values
A–E are not currently supported.)
Currently, only numeric currency exponents (values 1–5) are supported. ISO
defined values A–E for future use.
Refer to the MasterCard Quick Reference Booklet for a complete list of ISO
currency codes and related implied currency exponent values.
Values
If present, PDS 0148 cannot contain all low-values or all high-values.

PDS 0149—Currency Codes, Amounts, Original

Currency Codes, Amounts, Original (PDS 0149) defines the Amounts, Original
(DE 30) currencies.
Attributes
n-6; TAGLLL
Tag Field: 0149
Subfields: 2
Usage
messages:
Usage

Usage
Fee Collection (Handling Fees)/1740 C • C
Fee Collection (Other than Retrieval Fee Billing/handling Fees)/1740 C • C
This PDS is required when Amounts, Original (DE 30) is in the message.
Currency Exponents, PDS 0148 must also be present in a message when
Currency Codes, Amounts, Original PDS 0149 is present.
Subfields
This PDS contains two subfields as specified in the following table:

1 1–3 Currency Code, Original n-3 n/a
Transaction Amount
2 4–6 Currency Code, Original n-3 n/a
Reconciliation Amount
Values
Subfield 1 must contain valid ISO numeric currency codes. There must be an
occurrence of PDS 0149, subfield 1 Currency Code, Original Transaction
Amount (along with its corresponding currency exponent) in PDS 0148
Currency Exponents.
Subfield 2 must contain all zeros.

PDS 0158—Business Activity

Business Activity (PDS 0158) identifies the business arrangement applied to
this transaction. This includes information about the applicable card program
identifier for a transaction, the business relationship between the acquirer and
issuer (or the transaction originator and destination members), the interchange
rules governing all participants in the transaction, and the clearing system
business date and processing cycle for reconciliation purposes.
Current Attributes
ans...20; TAGLLLVAR
Tag Field: 0158
Subfields: 6
Future Attributes
ans…24; TAGLLLVAR
Tag Field: 0158
Subfields: 10
Usage
messages:
Usage
First Presentment/1240 C X M
s2 Business Service Arrangement Type Code C X M

Usage
s4 Interchange Rate Designator C X M
s7 Card Acceptor Business Code (MCC) Override Indicator • X M
First Chargeback/1442 and Arbitration Chargeback/1442 C X M
Second Presentment/1240 C X M

Usage
Retrieval Request/1644 O X M
s2 Business Service Arrangement Type Code O X M
Fee Collection (Retrieval Fee Billing)/1740 O X M
Fee Collection (Handling Fees)/1740 O X M

Usage
Fee Collection (Other than Retrieval Fee Billing/Handling Fees)/1740 O X M
PDS 0158 Business Activity must be a minimum length of 003 and a maximum
length of 020.
The clearing system determines and/or validates PDS 0158. If the business
service requires an IRD for a given message type, the message originator must
submit all spaces or valid values in subfields 1, 2, and 3, and a valid
interchange rate designator in subfield 4. For example, PDS 0158 is required
to be present for all U.S. region and international MasterCard-branded
transactions, except for the following:
• ATM (DE 3, subfield 1 = 01)
• Cash Disbursement (DE 3, subfield 1 = 12)
• Retrieval Requests and Fee Collections
The clearing system honors the request if the submitted information matches
the information the clearing system assigns. Otherwise, the clearing system
rejects the transaction.

PDS 0158 is important to reconciliation processing because it identifies the

card program identifier, the business service, the interchange rate designator,
and the business date and processing cycle to which the transaction is
assigned for reconciliation purposes.
Refer to the GCMS Reference Manual for a complete listing of U.S. region,
Canada region, and interregional interchange programs.
Subfields
This PDS consists of six subfields (with an additional four being added in the
future) as defined in the following table. The clearing system provides
subfields 1, 2, 3, 5, 6, 7, 8, 9, and 10. However, the message originator must
provide spaces or valid values in subfields 1, 2, and 3 whenever subfield 4 is
provided.

1 1–3 Card Program Identifier ans-3 left
2 4 Business Service Arrangement ans-1 left
Type Code
3 5–10 Business Service ID Code ans-6 left
4 11–12 Interchange Rate Designator ans-2 left
5 13–18 Business Date n-6; right
YYMMDD
6 19–20 Business Cycle n-2 right
7 21 Card Acceptor Business Code a-1 n/a
(MCC) Override Indicator
8 22 Product Override Indicator a-1 n/a
9 23 Corporate Incentive Rates Apply a-1 n/a
Indicator
10 24 ATM Late Presentment Indicator a-1 n/a

Subfield 1: Card Program Identifier

The Card Program Identifier is a three-character code that identifies the card
program or financial network to which a transaction belongs. Valid card
program identifiers for programs and services the clearing system supports are
Value Description
CIR Cirrus
DMC Debit MasterCard®
MCC MasterCard® Credit
MSI Maestro
PRO Sweden domestic brand
PVL Private label
SOL U.K. domestic Solo brand
SWI U.K. domestic Switch brand
spaces Recommended: Members can submit all spaces in this subfield to indicate
that the clearing system should assign the correct value.
Subfield 2: Business Service Arrangement Type Code

The Business Service Arrangement Type Code is a one-position numeric value
that identifies the business relationship between the transaction’s participants.
When a business service arrangement ID Code is submitted in subfield 3, this
subfield must contain the business service arrangement type code, and cannot
contain all spaces.

Business service arrangement type codes the clearing system supports are in
the following table:
Value Description
1 Interregional
2 Intraregional
3 Intercountry
4 Intracountry
8 Member-to-member
spaces Recommended: Members can submit all spaces in this subfield (and in
subfield 3) to indicate that the clearing system should assign the correct
value.
Subfield 3: Business Service ID Code

The Business Service ID Code is a six-position value that identifies the
business service to which the transaction is assigned for reconciliation and
rules basis.
When a business service arrangement type code is submitted in subfield 2, this

subfield must contain a valid Business Service ID code and cannot contain all
spaces.
The following table provides further information:
Type
Type Code Description ID Code ID Code Description
1 Interregional FFTTnn FF = “from” acquiring region
TT = “to” issuing region
nn = unique number assigned to each
interregional business service
2 Intraregional RRnnnn RR = business region
nnnn = unique number assigned to each
intraregional business service
3 Intercountry nnnnnn nnnnnn = unique ID assigned to each
intercountry business service
4 Intracountry CCCnnn CCC = ISO numeric country code
nnn = unique number assigned to each I
ntracountry business service

Type
Type Code Description ID Code ID Code Description
8 Member-to- Nnnnnn Nnnnnn = unique number assigned to
member each member-to-member
business service
space Recommended: Members can submit all
spaces in this subfield (and in subfield 2)
to indicate that the clearing system should
assign the correct value.
The MasterCard billing and clearing codes, Account Management System (AMS)
region codes, and corresponding descriptions are in the following table. The
two-digit billing and clearing codes are used in subfield 3 in the previous
table, denoted with FF, TT, and RR.
Billing/
Clearing AMS
Code Region Code Description
01 1 United States
02 A Canada
03 B Caribbean, Central America, Mexico, South America
04 C Asia/Pacific
05 D Europe
06 E South Asia/Middle East/Africa
Note All business service IDs are provided on the IPM MPE.
Subfield 4: Interchange Rate Designator

The Interchange Rate Designator is a two-position code that indicates the
interchange rate and editing rules applied to the transaction.
A valid two-position IRD is required for all MasterCard-branded U.S. region

and international First Presentment/1240 messages, and chargeback cycle
messages, except for ATM (DE 3, subfield 1 = 01), and manual cash
disbursement (DE 3, subfield 1 = 12) transactions. It also is required in
messages submitted for a business service that requires an IRD to be present in
the given message type.

If business need dictates, MasterCard may introduce new business service

arrangements, interchange rate designators, or both outside of the typical
release schedule.
Subfield 5: Business Date

The Business Date identifies the official business processing date when the
business service reconciles a transaction.
The Business Date format is YYMMDD. For all business transactions, the
clearing system determines the Business Date and inserts it into the
transaction.
The Business Date is the clearing system’s processing date expressed in the
local time zone of the clearing system’s processing center.
Subfield 6: Business Cycle

The Business Cycle is a two-digit numeric subfield (such as 01, 02, or 03) that
identifies a reconciliation period in a Business Date. The Business Cycle is
adjusted at each business service’s processing cycle cutover. At cycle cutover
time, the Business Cycle is incremented by one unless Business Date is also
being cut over to the next time period; in this case, the Business Date is
incremented to the next available business day for the business service, and
the Business Cycle is reset to 01.
For all business transactions, the clearing system determines the Business Cycle
and inserts it into the transaction.
Subfield 7: Card Acceptor Business Code (MCC) Override Indicator

The clearing system populates this subfield with a value of Y or N to indicate
whether card acceptor business code (MCC) override interchange rates were
used in the interchange fee amount designated in PDS 0146 Amount,
Transaction Fees. Initially this subfield will contain N for most transactions,
because card acceptor business code (MCC) overrides will apply only to intra-
European Business Services.
Subfield 8: Product Override Indicator

whether product override interchange rates were used in the interchange fee
amount designated in PDS 0146 Amount, Transaction Fees. Initially, this
subfield will contain N for most transactions, because product overrides will
apply only to intra-European Business Services.

Subfield 9: Corporate Incentive Rates Apply Indicator

whether corporate incentive rates were used in the interchange fee amount
designated in PDS 0146 Amount, Transaction Fees. Initially this subfield will
contain N for most transactions, because the application of corporate incentive
rates will apply only to intra-European Business Services.
Subfield 10: ATM Late Presentment Indicator

whether an ATM Late Presentment fee was included in the interchange fee
amount designated in PDS 0146 Amount, Transaction Fees. Initially this
subfield will contain N for most transactions, because ATM Late Presentment
fees will apply only to intra-European Business Services.
Business Service Selection General Information

The transaction business relationship (referred to as the “business service”) is
described collectively by the Card Program Identifier, the Business Service
Level Code, and the Business Service ID Code subfields. The business service
defines the transaction interchange rule basis together with the interchange
rate designator submitted by the originator of the message.
A business service is an arrangement among a defined group of members (for

example, acquirers and issuers) that share a common level of interchange
participation for a specific card program identifier such as the MasterCard
brand. Business services may involve, but are not limited to the following:
• Two or more members (member-to-member)
• Members in a single country (intracountry)
• Members in two or more countries or regions (intercountry)
• Members within a business region (intraregional)
• Members between business regions (interregional)
Each business service may have its own criteria, interchange rates, transaction
life cycle procedures, business date calendar, and other features.

When the clearing system receives a business transaction for processing, it

evaluates the following types of information to determine the applicable card
program and business service:
• The country of the acquirer
• The country to which the issuing account range is assigned
• The card program(s) associated with the acquirer
• The card program(s) associated with the issuing account range
• The Processing Code (DE 3)
• The business services in which the transaction originator participates, and
for which the message qualifies
• The business services in which the transaction receiver participates, and for
which the message qualifies
• The interchange rate designator submitted in the message.
Both the origination and destination members of a transaction (for example,

the acquirer and issuer) must be licensed for a selected card program and must
participate in a common business service; otherwise, the clearing system
rejects the transaction because there are no business rules to govern its
completion. The clearing system selects the appropriate business service from
those in common between the issuer and acquirer in the following order of
priority:
• Member-to-member
• Intracountry
• Intercountry
• Intraregional
• Interregional
After the business service is determined, the clearing system evaluates financial
transactions with respect to the interchange criteria defined for the business
service and submitted interchange rate designator to determine the correct
interchange rate. The clearing system validates any data the message
originator submits in PDS 0158, calculates interchange fees, and forwards the
transaction to the receiver. This information is made available to the
transaction originating processor through reconciliation processing options.
Values
If present, PDS 0158 must be a minimum length of three positions, and cannot
contain all low-values or all high-values.

PDS 0159—Settlement Data 1

Settlement Data 1 (PDS 0159) with Settlement Data 2
(PDS 0161), provides reconciliation and settlement information for each
clearing system transaction that has settlement impact.
Attributes
ans...67; TAGLLLVAR
Tag Field: 0159

Subfields: 9
Usage
messages:
Usage

Usage
Fee Collection (Retrieval Fee Billing)/1740 • X C

Usage
The clearing system inserts PDS 0159 and PDS 0161 into all transactions with
settlement impact for which the clearing system is responsible for managing
funds settlement.
A transaction has settlement impact if it causes funds to be moved between

members or between the member and the Association when the transaction is
successfully completed.
Amount, Reconciliation (DE 5) always is assigned to PDS 0159 for

reconciliation.

In Amounts, Transaction Fee (PDS 0146), each occurrence of a transaction fee

(Amount, Fee, Reconciliation subfield 7) is assigned to either PDS 0159 or
PDS 0161 for reconciliation, as indicated by the Fee Settlement Indicator
subfield associated with each fee.
Subfields
Settlement Data 1 consists of nine subfields as defined in the following table:

1 1–11 Settlement Service Transfer ans-11 right
Agent ID Code
2 12–39 Settlement Service Transfer ans-28 left
Agent Account
3 40 Settlement Service Level Code n-1 n/a
4 41–50 Settlement Service ID Code ans-10 left
5 51 Settlement Foreign Exchange an-1 n/a
Rate Class Code
6 52–57 Reconciliation Date n-6; n/a
YYMMDD
7 58–59 Reconciliation Cycle n-2 n/a
8 60–65 Settlement Date n-6; n/a
YYMMDD
9 66–67 Settlement Cycle n-2 n/a
Subfield 1: Settlement Service Transfer Agent ID Code

Currently, this subfield is space-filled.
The Settlement Service Transfer Agent ID Code identifies the transfer agent
associated with the settlement service identified in subfield 4. The agent
established one or more accounts with at least one bank approved to effect
settlement with the Association. The agent’s accounts are used for settling
activity with the Association for itself, a member or group of members, or
both.
The clearing system always determines this subfield’s data value.

Subfield 2: Settlement Service Transfer Agent Account

This subfield contains the agent’s bank account number associated with the
settlement service identified in subfield 4.
The clearing system always determines this subfield’s value.
Subfield 3: Settlement Service Level Code

The Settlement Service Level Code is a one-digit code that identifies the
settlement level of the settlement service.
The clearing system always determines this subfield’s data value. Supported
values are listed in the following table:
Value Description
1 Regional.
2 Intercurrency
3 Intracurrency
Subfield 4: Settlement Service ID Code

The Settlement Service ID Code contains a 10-position value that uniquely

identifies the settlement service.
Subfield 5: Settlement Foreign Exchange Rate Class Code

The Settlement Foreign Exchange Rate Class Code identifies the classification
of foreign exchange rates used to compute payment amounts for this
settlement service.

values are in the following table:
Value Description
0 Not applicable; intracurrency settlement.
1 Actual rate (not currently supported).
2 Guaranteed rate.
Subfield 6: Reconciliation Date

Currently, this subfield is zero-filled.
The Reconciliation Date is a six-digit subfield in the format YYMMDD that

identifies the clearing system’s processing date expressed in the local time
zone of the clearing system’s processing center. Clearing reconciliation cutoffs
may occur every day. The clearing system may process a transaction on a
Sunday but the transaction may not be settled until Monday if the settlement
bank is not open on Sundays. If this occurs, the clearing system assigns the
Sunday date to subfield 6 (Reconciliation Date) and assigns the Monday date
to subfield 8 (Settlement Date).
The clearing system always determines this subfield’s data value. The clearing
system inserts Reconciliation Date into any transaction to which it has assigned
a Settlement Service Level Code and Settlement Service ID Code.
This subfield contains the same value as Business Date (PDS 0158, subfield 5).
Subfield 7: Reconciliation Cycle

The Reconciliation Cycle is a two-digit subfield that identifies a reconciliation

period in a Reconciliation Date. The Reconciliation Cycle is adjusted at each
clearing reconciliation cutoff. At cutoff, the Reconciliation Cycle is
incremented by one unless the last cycle in the Reconciliation Date is being
cutoff. In this case, the Reconciliation Date is incremented to the next
available business day for the settlement service, and the Reconciliation Cycle
is 01. The Reconciliation Cycles in the following table are assigned:

Value Description
00 Cycle data not applicable.
01 Cycle 1
02 Cycle 2
03 Cycle 3
04 Cycle 4
05 Cycle 5
06 Cycle 6
system inserts Reconciliation Cycle into any transaction to which it assigned a
Settlement Service Level Code and Settlement Service ID Code.
Senders and receivers of clearing file activity should anticipate that additional
Reconciliation Cycle cutoffs are added over time to support regional and local
needs. All processors should be prepared to receive and reconcile against
multiple Reconciliation Cycles.
This subfield contains the same value as Business Cycle (PDS 0158, subfield 6)
Subfield 8: Settlement Date

The Settlement Date is a six-digit subfield in the format YYMMDD that
identifies the date that the settlement service initiates settlement for the
message, such as the settlement advisement date, which is based on the
clearing date, settlement service cutoff cycle, and calendar for the settlement
service. Settlement service settlement cutoffs occur only on banking business
days the settlement service specifically identifies. The clearing system may
process a transaction on a Sunday but may not settle it until Monday if the
settlement bank is not open on Sundays. If this occurs, the clearing system
assigns the Sunday date to subfield 6 (Reconciliation Date) and assigns the
Monday date to subfield 8 (Settlement Date).
system inserts Settlement Date in any transaction to which it assigned a

Subfield 9: Settlement Cycle

The Settlement Cycle is a two-digit subfield that identifies a settlement period

in a settlement date. The settlement cycle is adjusted at each settlement
service reconciliation cutoff. The settlement cycles in the following table are
assigned:
Value Description
01 Cycle 1
Clearing file activity senders and receivers should anticipate that additional
Settlement Cycle cutoffs will be added over time to support regional and local
needs. All members and processors should be prepared to receive and
reconcile against multiple settlement cycles.


Settlement Data 2 (PDS 0161), with Settlement Data 1 (PDS 0159), provides
reconciliation and settlement information for each clearing system transaction
that has settlement impact.
Note This PDS is not currently supported in GCMS.
Attributes
ans...67; TAGLLLVAR
Tag Field: 0161

Subfields: 9
Usage
messages:
Usage

Usage
s5 Settlement FX Rate Class Code • X C

Usage
s5 Settlement FX Rate Class Code • X C
The clearing system inserts PDS 0159 and PDS 0161 into all transactions with
settlement impact for which the clearing system is responsible for managing
funds settlement.
A transaction has settlement impact if it causes funds to be moved between

members or between the member and the Association when the transaction is
successfully completed.
Note Amount, Reconciliation (DE 5) is always assigned to PDS 0159 for reconciliation.
Individual fees are assigned to either PDS 0159 or PDS 0161.
In Amounts, Transaction Fee (PDS 0146), each occurrence of a transaction fee

(Amount, Fee, Reconciliation subfield) is assigned to either PDS 0159 or
PDS 0161 for reconciliation, as indicated by each fee’s Fee Settlement Indicator
subfield.

Subfields
Settlement Data 2 consists of nine subfields as defined in the following table:

1 1–11 Settlement Service Transfer ans-11 right
Agent ID Code
Agent Account
3 40 Settlement Service Level Code n-1 n/a
Rate Class Code
6 52–57 Reconciliation Date (YYMMDD) n-6 n/a
8 60–65 Settlement Date (YYMMDD) n-6 n/a
Subfield 1: Settlement Service Transfer Agent ID Code

The Settlement Service Transfer Agent ID Code identifies the transfer agent
associated with the settlement service identified in subfield 4. The agent
established one or more accounts with at least one bank approved to effect
settlement with the Association. The agent’s accounts are used for settling
activity with the Association for itself, a member or group of members, or
both.
Subfield 2: Settlement Service Transfer Agent Account

The clearing system will provide this subfield in a future enhancement. It will
contain the agent’s bank account number associated with the settlement
service identified in subfield 4.

Subfield 3: Settlement Service Level Code

The Settlement Service Level Code is a one-digit code that identifies the
settlement level of the settlement service.
Value Description
1 Regional
2 Intracurrency
3 Subregional
Subfield 4: Settlement Service ID Code

The Settlement Service ID Code contains a 10-position value that uniquely
identifies the settlement service.
Subfield 5: Settlement Foreign Rate Class Code

The Settlement Foreign Rate Class Code identifies the classification of foreign
exchange rates used to compute payment amounts for this settlement service.
Value Description
0 Not applicable; intracurrency settlement.
1 Actual rate (not currently supported).
2 Guaranteed rate.

Subfield 6: Reconciliation Date

The Reconciliation Date is a six-digit subfield in the format YYMMDD that
identifies the date when the settlement service financially reconciles the
message. The time basis for the Reconciliation Date is based on the local time
zone and calendar for the settlement service. Settlement service reconciliation
cutoffs may occur every day or only on business days the settlement service
identifies. The clearing system may process a transaction on a Sunday but the
transaction may not be settled until Monday if the settlement bank is not open
on Sundays. If this occurs, the clearing system assigns the Sunday date to
subfield 6 (Reconciliation Date) and assigns the Monday date to subfield 8
(Settlement Date).
system inserts Reconciliation Date into any transaction to which it has assigned
a Settlement Service Level Code and Settlement Service ID Code.
Subfield 7: Reconciliation Cycle

The Reconciliation Cycle is a two-digit subfield that identifies a reconciliation
period in a Reconciliation Date. The Reconciliation Cycle is adjusted at each
settlement service reconciliation cutoff. At cutoff, the Reconciliation Cycle is
incremented by one unless the last cycle in the Reconciliation Date is being cut
off. In this case, the Reconciliation Date is incremented to the next available
business day for the settlement service, and the Reconciliation Cycle is 01. The
Reconciliation Cycles in the following tables are assigned:
Value Description
01 Cycle 1 (default value if multiple cycles are not supported).
02 Cycle 2 (if second cycle is supported).
03 Cycle 3 (if third cycle is supported).
system inserts Reconciliation Cycle into any transaction to which it assigned a
Reconciliation Cycle cutoffs are added over time to support regional and local
needs. All processors should be prepared to receive and reconcile against
multiple Reconciliation Cycles.

Subfield 8: Settlement Date

The Settlement Date is a six-digit subfield in the format YYMMDD that
identifies the date that the settlement service initiates settlement for the
message. The time basis for the Settlement Date is based on the local time
zone and calendar for the settlement service. Settlement service settlement
cutoffs occur only on banking business days the settlement service specifically
identifies. The clearing system may process a transaction on a Sunday but may
not settle it until Monday if the settlement bank is not open on Sundays. If
this occurs, the clearing system assigns the Sunday date to subfield 6
(Reconciliation Date) and assigns the Monday date to subfield 8 (Settlement
Date).
system inserts Settlement Date into any transaction to which it assigned a
Subfield 9: Settlement Cycle

The Settlement Cycle is a two-digit subfield that identifies a settlement period
in a Settlement Date. The Settlement Cycle is adjusted at each settlement
service reconciliation cutoff. At cutoff, the Settlement Cycle is incremented by
one unless the last cycle in Settlement Date is being cut off. In this case, the
Settlement Date is incremented to the next available business day for the
Settlement Service, and the Settlement Cycle is 01. The Settlement Cycles in
the following table are assigned:
Value Settlement Cycle

01 Cycle 1 (default value if multiple cycles are not supported).
02 Cycle 2 (if second cycle is supported).
03 Cycle 3 (if third cycle is supported).
system inserts Settlement Cycle into any transaction to which it has assigned a
Settlement Cycle cutoffs are added over time to support regional and local
needs. All members and processors should be prepared to receive and
reconcile against multiple Settlement Cycles.

PDS 0164—Currency Cross Rates

Currency Cross Rates (PDS 0164) in Currency Update/1644 messages provides
members with cross-rates between global base currency (currently U.S.
dollars), and other standard currencies. These rates are expressed as indirect
rates. That is, they contain the inverted rates of conversion between a given
currency and global base currency (currently U.S. dollars).
Attributes
Tag Field: 0164

Subfields: 5 subfields for each currency data occurrence
Occurrences 1–10
Usage
messages:
Usage
s2 Currency Conversion Rate • X M
s3 Currency Conversion Type • X M
s5 Delivery Cycle • X M
This PDS contains one to 10 occurrences of currency conversion data. The

clearing system may provide multiple Currency Update/1644 messages to
members (each with up to 10 rates per message) to provide information on
currency conversion rates used in processing Financial messages.

Subfields
One to 10 occurrences of currency cross rate data may be in this PDS. Each
occurrence of currency update information consists of five subfields as defined

1 1–3 Currency Code n-3 n/a
2 4–14 Currency Conversion Rate n-11 right
3 15 Currency Conversion Type a-1 n/a
4 16–21 Business Date n-6; n/a
YYMMDD
5 22–23 Delivery Cycle n-2 right
Subfield 1: Currency Code

The Currency Code is the ISO numeric currency code of the currency for
which conversion rate information is being provided.
Subfield 2: Currency Conversion Rate

The Currency Conversion Rate is the conversion rate between Currency Code,
Reconciliation (DE 50) and the Currency Code in subfield 1.
This subfield’s first position indicates the decimal point position of the
conversion rate data.
For example, a subfield value of 90001234567 indicates a conversion rate of

0.001234567.
Example
Assume that currency XYZ has a direct ratio to U.S. dollars (USD) of 3:1. The
indirect rate is 1/3, or 0.33333. The clearing system inserts a 9 in the first
position of subfield 2 to indicate the location of the decimal and the resulting
value in PDS 0164 subfield 2 is 90333333333. The receiver interprets this as
0.333333333.
The receiver multiplies this rate by the non-U.S. dollar amount to determine
the U.S. dollar equivalent, or divides the U.S. dollar amount by this rate to
determine the non-U.S. dollar amount.

To illustrate:
100 XYZ *(times) 0.333333333 = 33.33 USD
100 USD /(divided by) 0.333333333 = 300 XYZ
Subfield 3: Currency Conversion Type

The Currency Conversion Type indicates the type of rate represented in
subfields 1 and 2. There are three rate types the member uses to calculate
settlement (buy, mid, or sell). The values for subfield are in the following
table:
Value Description
B Buy rate
M Mid rate
S Sell rate
Subfield 4: Business Date

This subfield indicates the business date that the currency conversion rates are
effective. The format is YYMMDD.
Subfield 5: Delivery Cycle

This subfield contains the delivery cycle in which the currency conversion
rates are being distributed.

PDS 0165—Settlement Indicator

The Settlement Indicator (PDS 0165) indicates the settlement impact of
amounts in an IPM message.
Attributes
ans...30; TAGLLLVAR
Tag Field: 0165
Subfields: 2; subfield 1 is mandatory; subfield 2 is optional
Usage
messages:
Usage
s2 Settlement Agreement Information O • C
s2 Settlement Agreement Information • X C

Usage
The transaction originator must provide this PDS. It must indicate normal,
bilateral, or collection-only processing.

MasterCard Clearing and Net Settlement Processing

A value of M in subfield 1 signifies that normal MasterCard clearing and net
settlement processes must be performed for the transaction.
Bilateral Processing
A value of B in subfield 1 signifies bilateral settlement. When included in
transactions where the members are participating in a bilateral settlement
agreement process, PDS 0165 signifies that the participating members assume
responsibility for settlement processing according to an agreement on file with
the Association. Therefore the transaction is cleared but not settled.
Subfield 2 may optionally include any supplemental information that may be

required under the bilateral agreement terms.
Collection-Only Processing
This PDS also identifies transactions forwarded to the clearing system “for
Collection Only.” These are On-Us or intraprocessor transactions that were
cleared and settled outside the clearing system. These transactions may be
required for the system to process for fee billing and collection and audit
control purposes. A value of C in subfield 1 signifies Collection Only.
Payment/Balance Transfer (Processing Code [DE 3], subfield 1 is 50) and

Convenience Check (DE 3, subfield 1 is 17) transactions are valid only as
collection-only transactions.
When PDS 0165 indicates bilateral settlement, the clearing system does not
assign a settlement service or recalculate the Amount, Reconciliation (DE 5) or
Amounts, Transaction Fee (PDS 0146).
When present in Reconciliation/1644 messages, PDS 0165 indicates that the

totals presented in the message reflect MasterCard clearing and net settlement
activity, bilateral settlement activity, or collection-only activity.

Subfields
This PDS consists of two subfields as defined in the following table:

1 1 Settlement Indicator an-1 n/a
2 2–30 Settlement Agreement Information ans...29 left
Subfield 1: Settlement Indicator

The Settlement Indicator identifies the type of clearing and settlement
processing to be performed for a transaction. Values are in the following
table:
Value Description
B Bilateral settlement agreement applies; the clearing system clears the
transaction but does not settle it.
C Collection Only; the transaction is On-Us or intraprocessor and was
cleared and settled outside the clearing system; it is submitted to the
clearing system according to rules governing “collection-only” transactions.
M MasterCard clearing and net settlement; the clearing system should clear
and settle the transaction.
Subfield 2: Settlement Information

The message originator may provide Settlement Information. This optional
variable-length subfield (up to 29 characters long) may contain additional
information related to a bilateral settlement agreement.
It is assumed that the information conveyed has proprietary meaning between

the participants; therefore, the clearing system does not perform any editing on
this subfield.
If a bilateral settlement agreement does not require additional information, this

subfield should be omitted, and PDS 0165 should be truncated at the end of
the first subfield.
Values
If present, PDS 0165 cannot contain all low-values, or all high-values.

PDS 0170—Card Acceptor Inquiry Information

Card Acceptor Inquiry Information (PDS 0170) provides card acceptor contact
data for cardholder, acquirer, or issuer use if there are questions or disputes
concerning a transaction.
Attributes
ans...57; TAGLLLVAR
Tag Field: 0170

Subfields: 3
Usage
messages:
Usage

Usage
This PDS is available for use in First Presentment/1240 messages and

subsequent cardholder life cycle transactions.
Issuers may print the contents of PDS 0170, subfield 1 on cardholder

statements in addition to any card acceptor data in Card Acceptor
Name/Location (DE 43).
This information may be especially valuable to cardholders for transactions

initiated through non–face–to–face procedures, or for those transactions that
are part of a pre-approved billing program (such as monthly or annual dues or
monthly payment programs).
PDS 0170 subfield 1 should be provided for in-flight commerce transactions

(PDS 0023 contains a value of CT4), and also should be provided in any other
transaction in which a phone number would be submitted instead of a card
acceptor city.
An acquirer can choose to put the customer service phone number either in
DE 43, subfield 3, or in PDS 0170 (or in both). For a telephone transaction,
the acquirer can choose to put the telephone detail either in DE 43, subfields 1
and 3, or in PDS 0189 (or in both).
PDS 0170 must not contain all spaces or all zeros.

Subfields

1 1–16 Customer Service Phone Number ans-16 left
Optional subfield for this PDS.
2 17–32 Card Acceptor Phone Number ans-16 left
3 33–57 Additional Contact Information ans...25 left
Subfield 1: Customer Service Phone Number

This subfield contains the primary card acceptor organization customer service
phone number that the cardholder may use for inquiries on the transaction.
Where applicable, this should contain the card acceptor’s customer service or
accounting department’s toll free (800) phone number.
If present, Card Acceptor Inquiry Information, Customer Service Phone

Number (PDS 0170, subfield 1) cannot contain all zeros or any of the
following:
• 000-000-0000
• (000) 000-0000
• 000 000 0000
For original, non-credit First Presentment/1240 transactions acquired in the U.S.

or Canada regions, Customer Service Phone Number (PDS 0170, subfield 1), if
present, must contain a 10-position phone number, and must be left justified
with trailing spaces. The first three positions must be numeric.
Subfield 2: Card Acceptor Phone Number

This subfield contains the card acceptor’s business phone number if it is
different than the value in Customer Service Phone Number (subfield 1).

If present, Card Acceptor Inquiry Information, Card Acceptor Phone Number

(PDS 0170, subfield) cannot contain all zeros, or any of the following:
• 000-000-0000
• (000) 000-0000
• 000 000 0000

or Canada region, Card Acceptor Phone Number (PDS 0170, subfield 2), if
present, must contain a 10-position phone number, and must be left justified
Subfield 3: Additional Contact Information

This subfield may contain additional card acceptor contact information, such as
secondary phone numbers, customer service operation hours, and contact
name.
If present, Card Acceptor Inquiry Information, Additional Contact Information

(PDS 0170, subfield 3) cannot contain all zeros.
Issuers may print this information on cardholder statements in addition to any

card acceptor data that is in DE 43.

Values
If present, Card Acceptor Inquiry Information (PDS 0170)cannot contain all
low-values, all high-values, all spaces, or all zeros.

PDS 0171—Alternate Card Acceptor Description Data

Alternate Card Acceptor Description Data (PDS 0171) may provide a local
language version of the data in Card Acceptor Name/Location (DE 43) using a
non-standard character set.
Attributes
Tag Field: 0171

Subfields: 2
Usage
messages:
Usage

Usage
This PDS is optional in First Presentment/1240 messages and subsequent

cardholder life cycle transactions.
Subfields

1 1–3 Character Set Indicator an-3 n/a
2 4–201 Card Acceptor Description Data ans...198 left
Subfield 1: Character Set Indicator

The Character Set Indicator identifies the character set in which the alternate
card acceptor description is provided. Values are in the following table:
Value Description
ARA Arabic
CHS Chinese (simplified)
CHT Chinese (traditional)
CYR Cyrillic
GRK Greek
HEB Hebrew
HIR Hiragana
HAN Hangul
KAN Kanji

Value Description
KAT Katakana
ROM Roman
THI Thai
VIE Vietnamese
Subfield 2: Card Acceptor Description Data

The Card Acceptor Description Data consists of a free-format text describing
the card acceptor name and/or location, provided in the character set as
indicated in subfield 1.
This data is variable length, with a maximum length of 198 positions. This
subfield is not edited.
Values

PDS 0172—Sole Proprietor Name
PDS 0172—Sole Proprietor Name

Sole Proprietor Name (PDS 0172) provides the card acceptor’s proprietor
name.
Attributes
ans...30; TAGLLLVAR
Tag Field: 0172
Subfields: None
Justification: Left
Usage
messages:
Usage

cardholder life cycle transactions. If present, it must be left justified and
cannot contain all spaces.

PDS 0173—Legal Corporate Name
PDS 0173—Legal Corporate Name

Legal Corporate Name (PDS 0173) provides the card acceptor’s legal
corporation name.
Attributes
ans...30; TAGLLLVAR
Tag Field: 0173
Subfields: None
Justification: Left
Usage
messages:
Usage

cardholder life cycle transactions. If present, it must be left justified and
cannot contain all spaces.

PDS 0174—Dun & Bradstreet Number
PDS 0174—Dun & Bradstreet Number

Dun & Bradstreet Number (PDS 0174) provides the card acceptor’s Dun &
Bradstreet assigned number.
Attributes
n-15; TAGLLL
Tag Field: 0174
Data Field: Fixed length 15 positions
Subfields: None
Justification: Left
Usage
messages:
Usage

cardholder life cycle transactions. If present, it must be numeric and cannot
contain all zeros.

PDS 0175—Card Acceptor URL
PDS 0175—Card Acceptor URL

Card Acceptor URL (PDS 0175) is used to capture the URL (Uniform Resource
Locator)/Web site address.
Attributes
ans…255; TAGLLLVAR
Tag Field: 0175
Data Field: Variable length 1–255 positions
Subfields: None
Justification: Left
Usage
messages:
Usage
Fee Collection (other than Retrieval Fee Billing/Handling Fees)/1740 O • C

cardholder life cycle transactions. It should be provided for all electronic
commerce transactions. If present, PDS 0175 must be left justified and cannot
contain all spaces or all zeros.

PDS 0189—Point-of-Interaction (POI) Phone Data

Point-of-Interaction (POI) Phone Data (PDS 0189) identifies the number dialed
in a POI phone call transaction.
Attributes
ans–41; TAGLLL
Tag Field: 0189
Subfields: 2
Usage
messages:
Usage

Usage
This PDS is supplemental to the information in Card Acceptor Name/Location

(DE 43). It provides call detail record reporting for the cardholder.
Subfields

1 1 Format Number an-1 n/a
2 2–41 Phone Data ans-40 left
Subfield 1: Format Number

The Format Number identifies the format of the data in subfield 2, Phone Data.
Value Description
1 Card-activated phone transactions (U.S. and Canadian call detail format).
2 Card-activated phone transactions (non-U.S. and non-Canadian format).
Subfield 2: Phone Data

The Phone Data provides the phone number dialed, the call duration, and
other related information. It is formatted to fit in 40 bytes. This allows the
issuer the option of printing this subfield’s contents directly on the cardholder’s
statement. The formats are in the following tables.
If present, Phone Data (PDS 0189, subfield 2) cannot contain all zeros or all
spaces.


or Canada regions, Phone Data (PDS 0189, subfield 2), if present, must contain
a 10-position phone number, and must be left justified with trailing spaces.
The first three positions must be numeric.
Note The following layouts are guidelines only. The clearing system does not
perform edits to ensure that these layouts are followed.

Format 1: Card-Activated Phone Transactions (U.S. and Canadian Call

Detail Format)

1 1–3 Abbreviation TEL a-3 n/a
2 4 Delimiter (space) a-1 n/a
3 5–7 Area Code n-3 n/a
U.S./Canadian area code.
5 9–11 Local Exchange n-3 n/a
Phone number; first three digits.
7 13–16 Local Number n-4 n/a
Phone number; last four digits.
9 18–20 Abbreviation MIN a-3 n/a
10 21–22 Call Duration in Minutes an-2 right
12 24–36 Card Acceptor City ans-13 left
14 38–40 Call Origin State/Country Code a-3 left
May be space-filled; otherwise,
may be a three-position
alphabetic country code from ISO
3166 table or a two-position U.S.
state code if merchant is in the
U.S. region. See the Quick
Reference Booklet for valid state
and country codes.

Format 2: Card-Activated Phone Transactions (Non-U.S. and Non-

Canadian Format)

1 1–2 Abbreviation TL a-2 n/a
2 3–17 Full Phone Number Dialed ans-15 right
Includes country code, city code,
and local number dialed.
3 18–19 Abbreviation MN a-2 n/a
4 20–22 Call Duration in Minutes an-3 right
5 23 Delimiter (spaces) a-1 n/a
6 24–36 Card Acceptor City ans-13 left
7 37 Delimiter (spaces) a-1 n/a
8 38–40 Call Origin State/Country Code a-3 left
May be space-filled; otherwise,
may be a three-position
alphabetic country code from ISO
3166 table or a two-position U.S.
state code if merchant is in the
U.S. region. See the Quick
Reference Booklet for valid state
and country codes.

Values

PDS 0190—Partner ID Code

Partner ID Code (PDS 0190) identifies a specific partnership agreement,
generally between specific card acceptors and issuers.
Attributes
ans...6; TAGLLLVAR
Tag Field: 0190
Subfields: None
Justification: Left
Usage
messages:
Usage
This PDS may be used for transactions on accounts issued under co-branding
agreements when one of the co-branding partners originates the transaction. It
may also be used when the agreement is between the card acceptor and the
clearing system, such as in certain promotional discounts.

Values
Card acceptors and issuers establish Partner ID Codes.
If present, PDS 0190 cannot contain all low-values, all high-values, all zeros, or
all spaces.

PDS 0191—Originating Message Format

Originating Message Format (PDS 0191) provides the message format in which
the clearing system received a message.
Attributes
n-1; TAGLLL
Tag Field: 0191
Subfields: None
Justification: n/a
Usage
messages:
Usage
File Header and Trailer Message
File Trailer (Member-Generated)/1644 O • •
First Presentment/1240 O X M
Financial Detail Addendum (Passenger Transport Detail—General O X M
Financial Detail Addendum (Passenger Transport Detail—Trip Leg O X M
Data)/1644
Financial Detail Addendum (Vehicle Rental Detail)/1644 O X M
Financial Detail Addendum (Lodging Summary)/1644 O X M
Financial Detail Addendum (Temporary Services)/1644 O X M
Financial Detail Addendum (Shipping/Courier Services)/1644 O X M
Financial Detail Addendum (Payment Transaction Detail)/1644 O X M
Financial Detail Addendum (Telephony Billing—Summary)/1644 O X M

Usage
Financial Detail Addendum (Telephony Billing—Detail)/1644 O X M
Financial Detail Addendum (Electronic Invoice—Transaction O X M
Data)/1644
Financial Detail Addendum (Electronic Invoice—Party O X M
Information)/1644
Financial Detail Addendum (Corporate Card Common Data O X M
Requirements)/1644
Financial Detail Addendum (Corporate Fleet Transaction O X M
Information)/1644
Financial Detail Addendum (Corporate Line Item Detail)/1644 O X M
Financial Detail Addendum (Generic Detail)/1644 O X M
First Chargeback/1442 and Arbitration Chargeback/1442 O X M
Second Presentment/1240 O X M
Retrieval Request/1644 O X M
Fee Collection (Retrieval Fee Billing)/1740 O X M
Fee Collection (Handling Fees)/1740 O X M
Fee Collection (Other than Retrieval Fee Billing/Handling Fees)/1740 O X M
Originators may optionally provide this PDS. If this information is not present,
the clearing system will provide this PDS in member-submitted messages. It
assists the receiving member in anticipating the presence or absence of various
IPM data elements and PDSs in an IPM message. If a message originated in
the ECCF format and was translated into the IPM format for the receiving
member, those IPM data elements and PDSs that do not have a corresponding
value in the ECCF format are not present in the IPM message.

Values
PDS 0191 values are in the following table:
Value Description
1 Clearing system received message in the ECCF format.
2 Clearing system received message in the IPM format.

PDS 0228—Retrieval Document Code
PDS 0228—Retrieval Document Code

Retrieval Document Code (PDS 0228) indicates the document type requested
to be provided in a Retrieval Request/1644.
Attributes
n-1; TAGLLL
Tag Field: 0228
Subfields: None
Justification: n/a
Usage
messages:
Usage
This PDS is used in Retrieval Request/1644 and Retrieval Fulfillment (presented

via a Fee Collection) messages to identify the specific type of retrieval
document an issuer or processor requests.
Values
Data values are in the following table:
Value Description
1 Hard copy original document.
2 Copy or image (xerox, microfilm, fax) of original document.
4 Substitute draft.

PDS 0230—Fulfillment Document Code
PDS 0230—Fulfillment Document Code

Fulfillment Document Code (PDS 0230) indicates the document type the
acquirer provided to the issuer in response to a Retrieval Request/1644.
Attributes
n-1; TAGLLL
Tag Field: 0230
Subfields: None
Justification: Left
Usage
messages:
Usage
This PDS is used in a retrieval fulfillment, which is presented via Fee

Collection message. PDS 0230 identifies the specific type of retrieval
document that the acquirer was able to supply in response to a previous
Retrieval Request/1644.
Values
Value Description
1 Hard copy original document.

PDS 0241—MasterCom Control Number

MasterCom Control Number (PDS 0241) contains the MasterCom PC Endpoint
Number used in routing chargeback and retrieval documentation.
Attributes
ans...7; TAGLLLVAR
Tag Field: 0241
Length Field: 3 positions, value = 002 or 007
Data Field: variable length 2 or 7 positions
Subfields: None
Justification: Left

In First Chargeback/1442, Second Presentment/1240, and Arbitration
Chargeback/1442 messages, if PDS 0241 is present it must be a length of 002
and contain a MasterCom endpoint suffix.
In Retrieval Requests/1644 and Fee Collection (Retrieval Fees)/1740 messages,

if PDS 0241 is present it can contain either a MasterCom endpoint suffix or a
full MasterCom endpoint. If it contains a MasterCom endpoint suffix, the
length must be 002. If it contains a full MasterCom endpoint, the length must
be 007.
Usage
conditional, optional, system provided, or not required) in applicable messages
Usage

This PDS contains the MasterCom PC Endpoint Control Number or Suffix to

identify the MasterCom PC associated with a retrieval request or response
action, or with CSD. It is used to notify the MasterCom system that a retrieval
fulfillment or CSD will be provided from a specific MasterCom PC endpoint.
If the originator does not provide the MasterCom PC Endpoint Control Number
or Suffix in the clearing message, this PDS is not present in the receiver’s
message, and the MasterCom system uses the member’s default endpoint
number.
Values
This PDS must contain a seven-digit MasterCom PC Endpoint Number or a
two-digit MasterCom PC Endpoint Suffix.
If present, PDS 0241 MasterCom Control Number cannot contain all zeros or all
spaces.

PDS 0242—MasterCom Service Indicator
PDS 0242—MasterCom Service Indicator

The MasterCom Service Indicator (PDS 0242) identifies the service level the
MasterCom system provides in support of a Retrieval Request/1644.
Attributes
ans-1; TAGLLL
Tag Field: 0242
Subfields: none
Justification: n/a
Usage
messages:
Usage
Retrieval Request/1644 • X C
The clearing system provides this PDS for MasterCom-supported Retrieval

Request/1644 messages. If the transaction involves a non-MasterCom
participant, PDS 0242 is not in the message.
Values
Value Description
E MasterCom service is supported for issuer and acquirer.
S MasterCom service is supported for issuer and acquirer Central Site
Assistance Facility (CSAF).

PDS 0243—MasterCom Retrieval Response Data

The MasterCom Processing System provides retrieval request, response, and
MasterCom image review information to the clearing system. New information
is provided each day, 7 days per week. The clearing system maintains this
information for 120 days from the last update in a retrieval history record for
each transaction.
Each transaction is identified in history by the Primary Account Number

(DE 2) and the Acquirer Reference Data (DE 31). Whenever possible, the
clearing system will supplement a chargeback message with information from
the retrieval history file related to the issuer’s Retrieval Request/1644, the
acquirer’s response, and any subsequent decisions by the issuer, MasterCom,
or both.
Attributes
ans…38; TAGLLLVAR
Tag Field: 0243
Subfields: 8
Note If the clearing system is unable to locate history for the transaction, or more
than one occurrence of history is detected, this information will not be provided
in the message.

Usage
messages:
Usage
s3 MasterCom Acquirer Retrieval Response Sent Date • X C
s3 MasterCom Acquirer Retrieval Response Sent Date • X C
The clearing system provides this PDS using information from the MasterCom
system.

Subfields
This PDS consists of eight subfields as indicated in the following table:

1 1–6 MasterCom Issuer Retrieval n-6; n/a
Request Date YYMMDD
2 7 MasterCom Acquirer Retrieval ans-1 n/a
Response Code
3 8–13 MasterCom Acquirer Retrieval n-6; n/a
Response Sent Date YYMMDD
4 14–15 MasterCom Issuer Response ans-2 n/a
Code
5 16–21 MasterCom Issuer Response n-6; n/a
Date YYMMDD
6 22–31 MasterCom Issuer Reject Reasons ans-10 left
7 32 MasterCom Image Review a-1 n/a
Decision
8 33–38 MasterCom Image Review Date n-6; n/a
YYMMDD
Subfield 1: MasterCom Issuer Retrieval Request Date

Subfield 1 is the clearing system processing date of the issuer’s Retrieval
Request/1644. This is the date that begins the time frame edits related to the
validity of a chargeback for non-receipt of requested documentation.
The subfield 1 format is YYMMDD.

Subfield 2: MasterCom Acquirer Retrieval Response Code

Subfield 2 is the code the acquirer returns in response to the issuer’s Retrieval
Request/1644. Valid codes and their descriptions are in the following table:
Value Description
A Retrieval request not fulfilled; invalid reference number.
B Retrieval request not fulfilled; reference number and cardholder account
number combination is incompatible.
C Retrieval request not fulfilled; request is for a below floor limit QPS
transaction for which documentation was not available.
D Retrieval request was fulfilled.
E Retrieval request was not fulfilled; required or requested documentation is
not available.
Subfield 3: MasterCom Acquirer Retrieval Response Sent Date

Subfield 3 is the date that the acquirer responded to the issuer’s Retrieval
Request/1644. This date determines whether the acquirer responded to the
issuer’s request in the appropriate time frames. It is also used in retrieval
fulfillment fee billing to indicate the number of days that the acquirer took to
respond.
Subfield 4: MasterCom Issuer Response Code

Subfield 4 is the code the issuer returns after reviewing the acquirer’s response
to the Retrieval Request/1644. It indicates whether the issuer accepts or rejects
the acquirer’s response. Valid codes and their descriptions are in the following
table:
Value Description
01 Image accepted.
02 Image rejected.
03 The acquirer responded with “invalid request” (Acquirer’s Response
Codes A, B, or C); the issuer accepted this response.
04 The acquirer responded with “invalid request” (Acquirer’s Response
Codes A, B, or C); the issuer rejected this response.
05 The acquirer responded with “documentation not available”
(Acquirer’s Response Code E); the issuer accepted this response.

Value Description
06 The acquirer responded with code A, B, C, or D; the issuer neither
accepted nor rejected the response in the appropriate time frame; the
MasterCom system automatically accepted the response on the issuer’s
behalf.
07 The acquirer responded with code E; the issuer neither accepted nor
rejected the response in the appropriate time frame; the MasterCom
system automatically rejected the response on the issuer’s behalf.
Subfield 5: MasterCom Issuer Response Date

Subfield 5 is the date that the issuer response code was provided. It
determines whether an issuer responded in the time frame allowed and is
therefore eligible (if it rejects the acquirer’s fulfillment and MasterCom Image
Review supports it) to charge back a transaction for Message Reason Code
4802—requested information illegible or missing, or 4801—requested
transaction data not received.
Subfield 6: MasterCom Issuer Reject Reason

Subfield 6 contains the reason(s) that the issuer rejected the acquirer’s
response. Up to 10 one-position reject codes can be provided. A Y in a
particular position indicates that the issuer rejected the response for the reason
associated with that position. For example, a Y in positions 2 and 4 of this
subfield indicates that the issuer rejected the document the acquirer provided
because of the transaction date and the expiration date. The reject reason
associated with each position is in the following table:
Position(s) Description
1 Reject for cardholder number.
2 Reject for transaction date.
3 Reject for transaction amount.
4 Reject for expiration date.
5 Reject for card acceptor name.
6 Reject for incorrect documentation.
7 Reject for other reason.
8–10 Reserved for future use.

Subfield 7: MasterCom Image Review Decision

Subfield 7 contains the Image Review decision. Whenever an issuer rejects an
acquirer’s response, the case is referred to Image Review for a ruling. Issuers
are only permitted to charge back for Message Reason Code 4802, requested
item illegible or missing if Image Review has ruled in their favor. Subfield
Value Description
A Image Review ruled in favor of the acquirer.
I Image Review ruled in favor of the issuer.
Subfield 8: MasterCom Image Review Date

Subfield 8 contains the date the Image Review decision was made. The format
is YYMMDD.
Values
Only those subfields for which the MasterCom system has stored the
information are present. PDS 0243 is truncated after the last available subfield.
For example, if the issuer received the acquirer’s image but has not yet
accepted or rejected it, only subfields 1, 2, and 3 of PDS 0243 are present, with
a corresponding length of 13.

PDS 0244—MasterCom Chargeback Support Documentation Dates
PDS 0244—MasterCom Chargeback Support

Documentation Dates
The MasterCom Processing System provides chargeback support
documentation (CSD) information to the clearing system. New information is
provided each day, seven days per week. The clearing system maintains this
information for 120 days from the last update in a chargeback history record
for each transaction.
Each transaction is identified in history by the Chargeback Reference Number

(DE 95) and the first six digits of the Primary Account Number (DE 2).
Whenever possible, the clearing system will supplement the chargeback
message with the information from the chargeback history file related to the
dates that CSD was sent via the MasterCom system.
Attributes
ans…12; TAGLLLVAR
Tag Field: 0244
Subfields: 2
Note If the clearing system is unable to locate history for the transaction, this
information will not be provided in the message.

Usage
messages:
Usage
Arbitration Chargeback/1442 • X C
s1 MasterCom Chargeback Support Documentation Sender • X C
Processing Date (First Chargeback)
Processing Date (Second Presentment)
Processing Date (First Chargeback)
s2 MasterCom Chargeback Support Documentation Sender • • •
Processing Date (Second Presentment)
The clearing system provides this PDS using information from the MasterCom
system. If available, PDS 0244 is included in Second Presentment/1240 and
Arbitration Chargeback/1442 messages. It indicates whether members
provided CSD via the MasterCom system in the appropriate time frames.
Subfields
This PDS consists of two subfields as indicated in the following table:

1 1–6 MasterCom Chargeback Support n-6; n/a
Documentation Sender YYMMDD
Processing Date (First
Chargeback/1442)
2 7–12 MasterCom Chargeback Support n-6; n/a
Documentation Sender YYMMDD
Processing Date (Second
Presentment/1240)

Subfield 1: MasterCom Chargeback Documentation Sender

Processing Date (First Chargeback/1442)
Subfield 1 is the date that the issuer provided CSD applicable to the First
Chargeback/1442. This date determines whether the issuer provided the
documentation in the appropriate time frames.
The subfield 1 format is YYMMDD. This subfield may contain zeros when
present in Arbitration Chargeback/1442 messages if the First Chargeback/1442
did not have documentation but the Second Presentment/1240 did.
Subfield 2: MasterCom Chargeback Documentation Sender

Processing Date (Second Presentment/1240)
Subfield 2 is the date that the acquirer provided CSD applicable to the Second
Presentment/1240. This date that determines whether the acquirer provided
the documentation in the appropriate time frames.
Values
Only those subfields for which the MasterCom system has stored the
information are present. PDS 0244 is truncated after the last available subfield.
For example, if PDS 0244 is present in an Arbitration Chargeback/1442
message, and documentation was sent only for the First Chargeback/1442, then
PDS 0244 contains only subfield 1, with a corresponding length of 6.

PDS 0245—MasterCom Arbitration Chargeback Sender Processing Date
PDS 0245—MasterCom Arbitration Chargeback Sender

Processing Date
MasterCom Arbitration Chargeback Sender Processing Date (PDS 0245)
contains the date on which the issuer submits supporting documentation for
an arbitration chargeback. This information is included only in the MasterCom
notification files.
Attributes
n-6; TAGLLL
Tag Field: 0245
Subfields: None
Justification: n/a
Usage
messages:
Usage
Arbitration Chargeback/1442 in the MasterCom notification files • X C
The MasterCom system provides this PDS in Arbitration Chargeback messages

within the MasterCom notification files. It indicates whether members
provided CSD via the MasterCom system in the appropriate time frames.
Values
This PDS contains a date in the format YYMMDD.

PDS 0246—MasterCom Sender Memo
PDS 0246—MasterCom Sender Memo

MasterCom Sender Memo (PDS 0246) conveys a message from the sender to
the receiver. This information is included only in the MasterCom Image
Interface data header and MasterCom notification files.
Attributes
Tag Field: 0246

Subfields: None
Justification: Left
Usage
For First Chargeback/1442 and Arbitration Chargeback/1442 messages, the
sender is always the issuer.
For Second Presentment/1240 messages and the fulfillment of Retrieval

Request/1644 messages, the sender is always the acquirer.
Usage
Second Presentment/1240 in the MasterCom Image Interface O • C
data header and MasterCom notification files
First Chargeback/1442 and Arbitration Chargeback/1442 in the O • C
MasterCom Image Interface data header and MasterCom
notification files
Retrieval Request/1644 in the MasterCom Image Interface O • C

PDS 0247—MasterCom Receiver Memo
PDS 0247—MasterCom Receiver Memo

MasterCom Receiver Memo (PDS 0247) conveys a message from the receiver to
the sender, or relays a message that the receiver originally sent to the sender.
This information is included only in the MasterCom Image Interface data
header and MasterCom notification files.
Attributes
Tag Field: 0247
Subfields: None
Justification: Left
Usage
For First Chargeback/1442, and Arbitration Chargeback/1442 message, the
receiver is always the acquirer.
For Second Presentment/1240 and the fulfillment of Retrieval Request/1644

messages, the receiver is always the issuer.
Usage
notification files

PDS 0248—MasterCom Image Review Memo
PDS 0248—MasterCom Image Review Memo

MasterCom Image Review Memo (PDS 0248) conveys a message from the
Image Review board to the requester of the review, or to all parties. This
information is included only in the MasterCom Image Interface data header
and MasterCom notification files.
Attributes
Tag Field: 0248
Subfields: None
Justification: Left
Usage
Accompanies MasterCom Image Review Decision (PDS 0243, subfield 7) and
MasterCom Image Review Date (PDS 0243, subfield 8).
Usage

PDS 0249—MasterCom Record ID
PDS 0249—MasterCom Record ID

MasterCom Record ID (PDS 0249) stores a unique identifier that relates the
record described in the IPM message to a specific record in the MasterCom
database. This information is included only in the MasterCom Image Interface
data header and MasterCom notification files.
Attributes
n...10; TAGLLLVAR
Tag Field: 0249
Subfields: None
Justification: n/a
Usage
Usage
notification files

PDS 0250—MasterCom Endpoints

MasterCom Endpoints (PDS 0250) contains two subfields that represent the
pair of endpoints used in the MasterCom transaction. This information is
included only in the MasterCom Image Interface data header and MasterCom
notification files.
Attributes
n-14; TAGLLL
Tag Field: 0250
Subfields: 2
Justification: n/a

Both endpoints must appear in their respective subfields; if one is present, the
other also must be present.
Usage
messages:
Usage
notification files

This PDS contains the MasterCom Endpoints that are associated with a retrieval
request fulfillment or response action, or with CSD files. It is used to identify
to the MasterCom system that a retrieval or CSD fulfillment will be provided
from and to a specific MasterCom endpoint.
This field is only present in MasterCom-generated notification files and

MasterCom Image Interface data headers.
Subfields
This PDS consists of two subfields as indicated in the following table:

1 1–7 MasterCom Sender Endpoint n-7 n/a
Number
2 8–14 MasterCom Receiver Endpoint n-7 n/a
Number
Subfield 1 is a number that identifies the endpoint that acts as the sender of a
MasterCom transaction (for both chargebacks and retrievals); subfield 2
identifies the endpoint that acts as the receiver of the same transaction.
Values
This PDS must contain two seven-digit MasterCom Endpoints: respectively,
sender and receiver.

PDS 0251—MasterCom Fulfillment Document Code
PDS 0251—MasterCom Fulfillment Document Code

MasterCom Fulfillment Document Code (PDS 0251) indicates the retrieval
document type supplied by the MasterCom application. This field is present
only in the MasterCom–generated notification files and MasterCom Image
Interface data headers.
Attributes
n-1; TAGLLL
Tag Field: 0251
Subfields: None
Justification: n/a
Usage
This PDS is used in MasterCom ASI/1644 header files to identify the specific
type of retrieval document sent by the MasterCom application.
Values
Value Description
2 Image (scanned or faxed) of original document.
4 Substitute draft.

PDS 0252—MasterCom Image Metadata

MasterCom Image Metadata (PDS 0252) provides data specific to an image
attached to the same message file. Currently only one image and one message
appear in a single file. This information is included only in the MasterCom
Image Interface fulfillment file.
Attributes
Tag Field: 0252
Subfields: 4
Usage
Images used by the MasterCom system are Group 3/Group 4 Tagged Image
File Format (TIFF) files, and may bear multiple pages of images within a single
TIFF file. The members provide this PDS to the MasterCom system when they
send an image file with the message. Each of the first three fields is expressed
as an eight-position, right-justified hexadecimal number. Leading zeros need
to be added where applicable. The fourth field is a variable-length filename.
MasterCom provides this data to the member within the Image Interface
fulfillment files that are delivered to the member’s imaging system.

Subfields
This PDS consists of four subfields as indicated in the following table:

1 1–8 MasterCom TIFF Image Data an-8 (hex) right
Length (expressed in
hexadecimal)
2 9–16 MasterCom TIFF Image Data an-8 (hex) right
Offset (expressed in
hexadecimal)
3 17–24 MasterCom TIFF Image CRC-32 an-8 (hex) right
(expressed in hexadecimal)
4 25–124 MasterCom TIFF Image Filename an..100 n/a
Subfield 1: MasterCom TIFF Image Data Length

Subfield 1 contains the 4-byte size of the TIFF image file, expressed in
hexadecimal and right-justified with leading zeros.
Subfield 2: MasterCom TIFF Image Data Offset

Subfield 2 contains the 4-byte value that corresponds to the offset byte within
the message file that is the first byte of the TIFF image file. This value is also
expressed in hexadecimal, and is right-justified with leading zeros.
Subfield 3: MasterCom TIFF Image CRC32

Subfield 3 contains the 32-bit CRC-32 (cyclic redundancy check) value that
verifies the integrity of the transmitted image file. This value is also expressed
in hexadecimal, and is right-justified with leading zeros where necessary.
Subfield 4: MasterCom TIFF Image Filename

Subfield 4 contains the variable-length filename of the TIFF image. It may
have a maximum length of 100 characters and, since it is variable-length, there
is no need for justification.
Values
If no image is present, this PDS will not appear in the message. If an image is
present, all four of these fields are required to have values.

PDS 0253—MasterCom System Enhanced Data
PDS 0253—MasterCom System Enhanced Data

MasterCom System Enhanced Data (PDS 0253) provides proprietary data from
the MasterCom system. This information is included only in the MasterCom
Image Interface files from the Image interface application.
Attributes
Tag Field: 0253

Subfields: None
Justification: n/a
Usage
messages:
Usage
MasterCom Image Interface files
Second Presentment/1240 in the MasterCom Image Interface files O • C
Retrieval Message
Retrieval Request/1644 in the MasterCom Image Interface files O • C

PDS 0254—MasterCom Member Enhanced Data
PDS 0254—MasterCom Member Enhanced Data

MasterCom Member Enhanced Data (PDS 0254) provides proprietary data from
the member. This information is included only in the MasterCom Image
Interface files for processing by the MasterCom system.
Attributes
Tag Field: 0254

Subfields: None
Justification: n/a
Usage
Reserved.
Usage
MasterCom Image Interface files
Second Presentment/1240 in the MasterCom Image Interface files O • C
Retrieval Message
Retrieval Request/1644 in the MasterCom Image Interface files O • C

PDS 0255—MasterCom Message Type

The MasterCom Message Type (PDS 0255) identifies non–MasterCard-branded
records processed in the MasterCom system.
This private date subelement is submitted by members that participate in the

program to process non–MasterCard-branded retrieval and chargeback
fulfillments via MasterCom. MasterCom returns this information only to that
member in its MasterCom Image Interface data headers and MasterCom
Notification files. Members can use this PDS to identify non–MasterCard-
branded fulfillment record information. Members will send or receive this
information directly to and from the MasterCom system, not within GCMS
clearing processing.
Attributes
ans…7; TAGLLLVAR
Tag Field: 0255
Subfields: None
Justification: Left
Usage
messages:
Usage
First Chargeback/1442 and Arbitration Chargeback/1442 (in O • C
MasterCom notification files)
Second Presentment/1240 (in MasterCom notification files) O • C
Retrieval Request/1644 (in MasterCom notification files) O • C

Values
Members processing non–MasterCard-branded retrieval or CSD transactions in
the MasterCom system can supply their own codes.

PDS 0260—Edit Exclusion Indicator

Edit Exclusion Indicator (PDS 0260) requests or grants de-activation of
transaction life cycle editing functions the clearing system normally performs
for chargebacks.
Attributes
ans...4; TAGLLLVAR
Tag Field: 0260

Data Field: variable length 2–4 positions on
Subfields: 3
Usage
messages:
Usage

This PDS may be used in clearing system messages to suspend life cycle
editing procedures on First Chargeback/1442, Second Presentment/1240, and
Arbitration Chargeback/1442 messages whose life cycle status changed as a
result of an ICA or BIN transfer, or for other life cycle-related exception
conditions that normally cause the clearing system to reject a message.
The transaction originator should present PDS 0260 only if edit exclusion
processing is requested for the transaction. The clearing system provides
PDS 0260 whenever edit exclusion approval is granted.
Subfields

1 1–2 Exclusion Request Code ans-2 left
2 3 Exclusion Reason Code an-1 n/a
3 4 Exclusion Results Code an-1 n/a
Subfield 1: Exclusion Request Code

The transaction originator provides this subfield. This subfield identifies the
clearing system edits that the originator requests to be bypassed during
clearing system processing of the IPM message in which PDS 0260 is present.
Subfield 1 values are in the following table:
Value Description
Y Conversion exclusion; exempts all chargeback cycles from timeliness,
cycle appropriateness, retrieval, and documentation history edits because
a recent ICA or BIN transfer caused an on-us or intraprocessor transaction
to become an inter-member transaction; conversion is validated against
clearing system files; exemptions are permitted for 60 days after the
conversion occurs.
B0–B9 Special conditions exclusion (chargeback and retrieval history); exempts
or chargebacks from timeliness, cycle appropriateness, retrieval history, and
documentation history edits when extenuating circumstances exist; the
BA–BZ
exclusion request code must match the exemption code the Association
granted in advance.
spaces Business service agreement exclusion; exempts chargebacks assigned to a
particular business service from timeliness, cycle appropriateness, retrieval
history, and documentation history edits; exemption automatically occurs
if the exclusion is profiled for the business service.

Value Description
spaces Hardship variance exclusion; exempts first chargebacks, second
presentments, and arbitration chargebacks from time frame edits when an
event such as flood or earthquake prevents timely responses; the
Association must grant hardship variance in advance; this exemption will
occur automatically if the hardship variance is in effect.
spaces ATM exclusion; ATM transactions (DE 3 Processing Code,
subfield 1 = 01) are automatically exempted from chargeback timeliness,
cycle appropriateness, and documentation history edits.
spaces Bilateral settlement and collection-only exclusion; exempts chargebacks
from timeliness, cycle appropriateness, retrieval history, and
documentation history edits if subfield 1 of Settlement Indicator (PDS
0165) contains a B; or if subfield 1 of PDS 0165 (Settlement Indicator)
contains a C, and a member has not chosen to have MasterCard perform
these edits on collection-only transactions.
L Single item life cycle exclusion—future enhancement; exempts a single
chargeback from timeliness, cycle appropriateness, retrieval history, and
documentation history edits when circumstances warrant an exclusion for
a particular transaction; request is validated against the clearing system’s
database of single-item exclusions, stored by transaction life cycle ID, card
account number, and acquirer’s reference number.
spaces Intraprocessor exclusion—future enhancement; allows chargebacks and
or P retrievals to be submitted without a life cycle ID when the account range
and acquiring BIN are assigned to the same third-party processor; other
chargeback edits, such as timeliness, are still enforced; a life cycle ID is
assigned when the chargeback or retrieval is processed the first time;
allows members to process chargebacks and retrievals for On-Us activity
through the clearing system for the protection of the rules and consistency
of edits.
spaces Special conditions exclusion—future enhancement; allows chargebacks for
or W “warning bulletin” when only the account range is listed on the Warning
Notice or the Electronic Warning Bulletin file; intended for use when
circumstances warrant a listing of an entire account range on the Warning
Notice or the Electronic Warning Bulletin file to prevent card utilization in
that account range; exemption automatically occurs if the exclusion is
profiled for the issuer’s account range; other chargeback edits, such as
timeliness, are still enforced.
spaces Interchange timeliness extension—future enhancement; extends the
interchange time frames for presentments by a certain number of days;
extension is automatically granted if the number of additional days is
profiled for the sending member; other presentment edits are still
enforced.

Value Description
spaces Transaction time frame extension—future enhancement; extends the time
frames for chargebacks by a certain number of days; includes time frames
between cycles, such as the time period that a member must wait for
chargeback documentation before submitting the next cycle; extension is
automatically granted if the number of additional days is profiled for the
sending member; other transaction edits are still enforced.
Subfield 2: Exclusion Reason Code

The clearing system provides this subfield. It contains a code the clearing
system assigns to indicate approval of and the reason for the edit exclusion.
Value Description
X Conversion exclusion; exclusion granted due to a recent ICA or BIN
or Y transfer caused an On-Us or intraprocessor transaction to become an inter-
member transaction; values are as follows:
or Z
X = recent issuer conversion
Y = recent acquirer conversion
Z = recent issuer and acquirer conversion
B Special conditions exclusion (chargeback and retrieval history); retrieval
history and chargeback exclusion granted because of extenuating
circumstances.
A Business service agreement exclusion; exclusion requested and granted for
chargebacks assigned to the specified business service.
H Hardship variance exclusion; exclusion requested and granted because of
an event such as flood or earthquake.
M ATM exclusion; ATM transactions (DE 3 Processing Code,
subfield 1 = 01) are automatically exempted from chargeback timeliness,
cycle appropriateness, and documentation history edits.
S Bilateral settlement and collection-only exclusion; exclusion automatically
granted if subfield 1 of Settlement Indicator (PDS 0165) contains a B; or if
subfield 1 of PDS 0165 (Settlement Indicator) contain a C, and a member
has not chosen to have MasterCard perform these edits on collection-only
transactions.
L Single item life cycle exclusion—future enhancement; exclusion requested
and granted for a single transaction based on life cycle ID, card account
number, and ARN.
P Intraprocessor exclusion—future enhancement; allows chargebacks and
retrievals to be submitted without a life cycle ID when the account range
and acquiring BIN are assigned to the same third-party processor.

Value Description
W Special conditions exclusion—future enhancement; allows chargebacks for
“warning bulletin” when only the account range is listed on the Warning
Notice or the Electronic Warning Bulletin file; because of circumstances
that warrant a listing of an entire account range on the CWB to prevent
card utilization in that account range.
I Interchange timeliness extension—future enhancement; extension
requested and granted for presentment interchange time frames.
F Transaction time frame extension—future enhancement; extension
requested and granted for various chargeback time frame edits.
T Interchange and transaction time frame extensions—future enhancement;
extension requested and granted for both presentment and chargeback
time frame edits.
Subfield 3: Exclusion Results Code

The clearing system provides this subfield. It contains a code the clearing
system assigns to indicate the edit set(s) actually bypassed when this
transaction was processed.
Value Description
H Bypass timeliness edits; allow second presentment for “non-receipt”
chargebacks.
C Bypass timeliness edits, cycle appropriateness edits, and documentation
history edits.
R Bypass retrieval history edits.
A Bypass timeliness edits, cycle appropriateness edits, documentation history
edits, and retrieval history edits; allow chargebacks and retrievals to be
submitted without a life cycle ID (future enhancement).
W Allow chargebacks for “warning bulletin” when only the account range is
listed on the Warning Notice or the Electronic Bulletin file (future
enhancement).
P Allow chargebacks and retrievals to be submitted without a life cycle ID
(future enhancement).
I Bypass interchange timeliness edits only (future enhancement).
F Bypass timeliness edits only (future enhancement).
T Bypass interchange timeliness edits only (future enhancement); bypass
timeliness edits only (future enhancement).

Values

PDS 0261—Risk Management Approval Code
PDS 0261—Risk Management Approval Code

The Risk Management Approval Code (PDS 0261) contains the approval code
provided by MasterCard in a rejected First Presentment/1240 message with
error code 2202 or error code 2203. Acquirers resubmit the First
Presentment/1240 message with the approval code once MasterCard confirms
that the approval code has been activated.
Attributes
n-11; TAGLLL
Tag Field: 0261

Subfields: None
Justification: n/a
Usage
messages:
Usage
First Presentment/1240 – rejected by MasterCard • X C
First Presentment/1240 – re-submitted by member after validation C • •
Values
If present, PDS 0261 must be numeric and cannot contain all zeros.
If a First Presentment rejects due to exceeding the MasterCard-defined risk

parameter limits, and there is no matching authorization on file, the clearing
system provides the PDS back to the acquirer in the First Presentment message
that accompanies the Message Exception/1644 message.
If the acquirer resubmits the transaction following MasterCard activation of the

risk management approval code, this PDS must be present. This PDS is not
forwarded to the issuer.

PDS 0262—Documentation Indicator

Documentation Indicator (PDS 0262) indicates whether supporting
documentation will be provided for the current chargeback or fee collection
cycle.
Attributes
n-1; TAGLLL
Tag Field: 0262

Subfields: None
Justification: n/a
Usage
messages:
Usage
This PDS indicates in First Chargeback/1442, Second Presentment/1240,

Arbitration Chargeback/1442, and Fee Collection/1740 messages whether the
message originator will provide supporting documentation.

Values
Value Description
0 Supporting documentation is not required.
1 Supporting documentation will follow.

PDS 0264—Original Retrieval Reason for Request

Original Retrieval Reason for Request (PDS 0264) contains the “reason for
request” from a previous Retrieval Request/1644.
Attributes
n-4; TAGLLL
Tag Field: 0264
Subfields: None
Justification: n/a
Usage
messages:
Usage
This PDS provides in Retrieval Fulfillment (presented as a Fee Collection)

messages the “reason for request” in Message Reason Code (DE 25) of a
related Retrieval Request/1644.

Values
Value Description
6305 Cardholder does not agree with amount billed.
6321 Cardholder does not recognize transaction.
6322 Request transaction certificate for a chip transaction.
6323 Cardholder needs information for personal records.
6341 Fraud investigation.
6342 Potential chargeback or compliance documentation is required.

PDS 0265—Initial Presentment/Fee Collection Data

Initial Presentment/Fee Collection Data (PDS 0265) contains dates, reasons,
and other information from a First Presentment/1240 or Fee Collection
(Member-Generated)/1740.
Attributes
Tag Field: 0265

Subfields: 3

The PDS 0265 maximum length must be 110 positions.
Usage
messages:
Usage

This PDS provides information from the First Presentment/1240 or Fee

This PDS may optionally be provided in Fee Collection Return/1740, Fee

Collection Resubmission/1740, and Fee Collection Arbitration Return/1740
messages to give information from the Fee Collection (Member-
Generated)/1740.
Subfields
This PDS consists of three subfields as indicated in the following table:

1 1–4 Initial Message Reason Code n-4 n/a
2 5–10 Date, Initial Presentment n-6; n/a
Business YYMMDD
3 11–110 Data Record, Initial ans...100 left
Subfield 1: Initial Message Reason Code

Subfield 1 contains the initial transaction’s Message Reason Code. It is
obtained from Message Reason Code (DE 25) in the First Presentment/1240 or
Fee Collection (Member-Generated)/1740.
Subfield 1 is optional in Fee Collection Return/1740, Fee Collection

Resubmission/1740, and Fee Collection Arbitration Return/1740 messages. If
present, it may contain either zeros or the DE 25 value of the related Fee
Refer to DE 25 in chapter 7 in this manual for a list of valid message reason

codes.
Subfield 2: Date, Initial Presentment Business

Subfield 2 contains the initial transaction’s business processing date. It is
obtained from the Business Date subfield of Business Activity (PDS 0158) in
the First Presentment/1240 or Fee Collection (Member-Generated)/1740.
Subfield 2 is optional in all messages containing PDS 0265. It should be

populated with all zeros if the information is not available.

Subfield 3: Data Record, Initial

Subfield 3 contains the message text data of the initial Fee Collection
transaction. It is obtained from Data Record (DE 72) in the Fee Collection
(Member-Generated)/1740.
Subfield 3 is optional in Fee Collection Return/1740, Fee Collection

Resubmission/1740, and Fee Collection Arbitration Return/1740 messages. It
identifies the Data Record (DE 72) of the related Fee Collection (Member-
Generated)/1740.
If present, subfield 3, Data Record, Initial cannot contain all zeros or all spaces.
Values
PDS 0265 may be truncated after the last subfield. For example, if used in a
Fee Collection Return/1740, PDS 0265 may contain only subfields 1 and 2, with
a corresponding length of 10.

PDS 0266—First Chargeback/Fee Collection Return Data

First Chargeback/Fee Collection Return Data (PDS 0266) contains dates,
amounts, reasons, and other information from a First Chargeback/1442 or a
Fee Collection Return/1740.
Attributes
Tag Field: 0266

Subfields: 7

Usage
messages:
Usage

Usage
The clearing system provides this PDS in Second Presentment/1240 and

Arbitration Chargeback/1442 messages to supply information from the First
Chargeback/1442, if the information is available.
The transaction originator may optionally provide this PDS in Fee Collection
Resubmission/1740 and Fee Collection Arbitration Return/1740 messages to
supply information from the Fee Collection Return/1740.

Subfields
This PDS consists of seven subfields as indicated in the following table:

1 1–4 Message Reason Code n-4 n/a
2 5–10 Date, First Return Business n-6; n/a
YYMMDD
3 11 Edit Exclusion Reason Code an-1 n/a
4 12 Edit Exclusion Results Code an-1 n/a
5 13–24 Amount, First Return n-12 right
6 25–27 Currency Code, First Return n-3 n/a
7 28–127 Data Record, First Return ans…100 left
Subfield 1: Message Reason Code

Subfield 1 contains the first return transaction’s Message Reason Code. It is
obtained from Message Reason Code (DE 25) in the First Chargeback/1442 or
the Fee Collection Return/1740.
The clearing system provides subfield 1 in Second Presentment/1240 and

Arbitration Chargeback/1442 messages to identify DE 25 of the related First
Chargeback/1442.
Subfield 1 may optionally be presented in Fee Collection Resubmission/1740

and Fee Collection Arbitration Return/1740 messages to identify DE 25 of the
related Fee Collection Return/1740. If present, it must contain all zeros or a
valid message reason code.
Refer to DE 25 in chapter 7 of this manual for a list of valid Message Reason

Codes.
Subfield 2: Date, First Return Business

Subfield 2 contains the first return transaction’s business processing date. It is
obtained from the Business Date subfield of Business Activity (PDS 0158) in
the First Chargeback/1442 or Fee Collection Return/1740.
The clearing system provides subfield 2 with a valid date when used in Second
Presentment/1240 and Arbitration Chargeback/1442 messages.

The transaction originator may optionally provide subfield 2 in Fee Collection

Resubmission/1740 and Fee Collection Arbitration Return/1740 messages.
Subfield 3: Edit Exclusion Reason Code

Subfield 3 contains the Edit Exclusion Reason Code, if the clearing system
supplies it, for the first return transaction. It is obtained from the Edit
Exclusion Reason Code subfield of Edit Exclusion Indicator (PDS 0260) in the
First Chargeback/1442 or Fee Collection Return/1740.

Arbitration Chargeback/1442 messages. It contains a valid Edit Exclusion
Reason Code or a space if no exclusion was granted.
Subfield 3 should contain spaces when used in Fee Collection

Resubmission/1740 and Fee Collection Arbitration Return/1740 messages if
subfields 5, 6, or 7 are present.
Subfield 4: Edit Exclusion Results Code

Subfield 4 contains the Edit Exclusion Results Code, if the clearing system
supplies it, for the first return transaction. It is obtained from the Edit
Exclusion Results Code subfield of Edit Exclusion Indicator (PDS 0260) in the
First Chargeback/1442 or Fee Collection Return/1740.

Arbitration Chargeback/1442 messages. It contains a valid Edit Exclusion
Results Code or a space if no exclusion was granted.
Subfield 4 should contain spaces when used in Fee Collection

Resubmission/1740 and Fee Collection Arbitration Return/1740 messages if
subfields 5, 6, or 7 are present.

Subfield 5: Amount, First Return

Subfield 5 contains the first return transaction’s submitted amount. It is
obtained from Amount, Transaction (DE 4) in the First Chargeback/1442 or Fee
Collection Return/1740.

Chargeback/1442.

identify DE 4 of the related Fee Collection Return/1740.
Subfield 6: Currency Code, First Return

Subfield 6 contains the first return transaction’s submitted currency code. It is
obtained from DE 49 in the First Chargeback/1442 or Fee Collection
Return/1740.

Chargeback/1442.

identify DE 49 of the related Fee Collection Return/1740.
Subfield 7: Data Record, First Return

Subfield 7 contains the first return transaction’s message text data. It is
obtained from Data Record (DE 72) in the First Chargeback/1442 or the Fee
Collection Return/1740.

Chargeback/1442..

identify DE 72 of the related Fee Collection Return/1740. If present, subfield 7
cannot contain all zeros or all spaces.


When PDS 0266 is included in a message, and subfield 6, Currency Code, First
Return, is present and contains a valid nonzero ISO currency code, then
Currency Exponents (PDS 0148) also is required to identify the currency
exponent of the First Chargeback/1442 or Fee Collection Return/1740.
Values

PDS 0267—Second Presentment/Fee Collection Resubmission Data
PDS 0267—Second Presentment/Fee Collection

Resubmission Data
Second Presentment/Fee Collection Resubmission Data (PDS 0267) contains
dates, amounts, reasons, and other information from a Second
Presentment/1240 or a Fee Collection Resubmission/1740.
Attributes
Tag Field: 0267
Subfields: 7
Justification:

Usage
messages:
Usage
s2 Date, Second Return Business • X C
s5 Amount, Second Return • X C
s6 Currency Code, Second Return • X C
s7 Data Record, Second Return • X C

Usage
The clearing system provides this PDS in Arbitration Chargeback/1442

messages to supply information from the Second Presentment/1240, if
available.
The transaction originator optionally may provide this PDS in Fee Collection
Arbitration Return/1740 messages to supply information from the Fee
Collection Resubmission/1740.

Subfields
This PDS consists of seven subfields as indicated in the following table:

1 1–4 Message Reason Code n-4 n/a
2 5–10 Date, Second Return Business n-6; n/a
YYMMDD
3 11 Edit Exclusion Reason Code an-1 n/a
4 12 Edit Exclusion Results Code an-1 n/a
5 13–24 Amount, Second Return n-12 right
6 25–27 Currency Code, Second Return n-3 n/a
7 28–127 Data Record, Second Return ans…100 left
Subfield 1: Message Reason Code

Subfield 1 contains the second return transaction’s Message Reason Code. It is
obtained from Message Reason Code (DE 25) in the Second Presentment/1240
or Fee Collection Resubmission/1740.
The clearing system provides subfield 1 in Arbitration Chargeback/1442

messages to identify DE 25 of the related Second Presentment/1240.
The transaction originator optionally may provide subfield 1 in Fee Collection

Arbitration Return/1740 messages to identify DE 25 of the related Fee
Collection Resubmission/1740. If present, it must contain all zeros or a valid
message reason code.
Refer to DE 25 in chapter 7 in this manual for a list of valid message reason

codes.
Subfield 2: Date, Second Return Business

Subfield 2 contains the second return transaction’s business processing date. It
is obtained from the Business Date subfield of Business Activity (PDS 0158) in
the Second Presentment/1240 or Fee Collection Resubmission/1740.
The clearing system provides subfield 2 with a valid date when used in
Arbitration Chargeback/1442 messages.

Arbitration Return/1740 messages.

Subfield 3: Edit Exclusion Reason Code

Subfield 3 contains the Edit Exclusion Reason Code for the second return
transaction. It is obtained from the Edit Exclusion Reason Code subfield of
Edit Exclusion Indicator (PDS 0260) in the Second Presentment/1240 or Fee

messages. It contains a valid Edit Exclusion Reason Code or a space if no
exclusion was granted.
Subfield 3 should contain a space when used in Fee Collection Arbitration

Return/1740 messages if subfields 5, 6, or 7 are present. GCMS does not edit
this subfield.
Subfield 4: Edit Exclusion Results Code

Subfield 4 contains the Edit Exclusion Results Code for the second return
transaction. It is obtained from the Edit Exclusion Results Code subfield of
Edit Exclusion Indicator (PDS 0260) in the Second Presentment/1240 or Fee

messages. It contains a valid Edit Exclusion Results Code or a space if no
exclusion was granted.
Subfield 4 must contain a space when used in Fee Collection Arbitration

Return/1740 messages if subfields 5, 6, or 7 are present. The clearing system
currently does not perform life cycle edits on these transactions. GCMS does
not edit this subfield.
Subfield 5: Amount, Second Return

Subfield 5 contains the second return transaction’s submitted amount. It is
obtained from Amount, Transaction (DE 4) in the Second Presentment/1240 or
Fee Collection Resubmission/1740.


Arbitration Return/1740 messages to identify DE 4 of the related Fee Collection
Resubmission/1740.

Subfield 6: Currency Code, Second Return

Subfield 6 contains the second return transaction’s submitted currency code. It
is obtained from Currency Code, Transaction (DE 49) in the Second
Presentment/1240 or Fee Collection Resubmission/1740.


Subfield 7: Data Record, Second Return

Subfield 7 contains the second return transaction’s message text data. It is
obtained from Data Record (DE 72) in the Second Presentment/1240 or Fee


Collection Resubmission/1740. If present, subfield 7 cannot contain all zeros
or all spaces.

When PDS 0267 is in a message, and subfield 6, Currency Code, Second
Return, is present and contains a valid nonzero ISO currency code, then
Currency Exponents (PDS 0148) is also required to identify the currency
exponent of the Second Presentment/1240 or Fee Collection
Resubmission/1740.
Values

PDS 0268—Amount, Partial Transaction

Amount, Partial Transaction (PDS 0268) provides the partial transaction amount
in the First Presentment/1240 currency.
Attributes
n-15; TAGLLL
Tag Field: 0268
Subfields: 2
Usage
messages:
Usage

The transaction originator provides this PDS. It may be provided in partial

Chargeback/1442, partial Second Presentment/1240, and partial Arbitration
Chargeback/1442 messages to provide the partial amount in the First
Presentment/1240 transaction currency. The currency is obtained from
Currency Code, Transaction (DE 49) of the First Presentment/1240.
For example, assume an acquirer submits a First Presentment/1240 for 200

Canadian dollars, which represents two days’ lodging at 100 Canadian dollars
per day. Assume also that the cardholder disputes one day’s lodging and the
issuer presents chargebacks in U.S. dollars. The issuer submits a partial First
Chargeback (Partial)/1442 containing a value of 100 Canadian dollars in this
PDS and the U.S. dollar equivalent to it in Amount, Transaction (DE 4).
Subfields

1 1–12 Amount, Partial Transaction n-12 right
2 13–15 Currency Code, Partial Transaction n-3 n/a
Subfield 1: Amount, Partial Transaction

Subfield 1 contains the partial transaction amount in the First Presentment/1240
currency.
Subfield 2: Currency Code, Partial Transaction

Subfield 2 contains the currency code associated with subfield 1. It should be
the same as the First Presentment/1240 currency code.
Related PDSs
Whenever PDS 0268 is included in a message, Currency Exponents (PDS 0148)
must also be included to identify the currency exponent of subfield 2.

PDS 0280—Source File ID

Source File ID (PDS 0280) provides the File ID of a referenced data file.
Attributes
n-25; TAGLLL
Tag Field: 0280

Subfields: 4
Usage
messages:
Usage
Currency Update/1644 • X C
This PDS identifies in File Reject/1644 and Message Exception/1644 messages

the file that contains errors.

This PDS comprises four subfields to indicate the file type; the file processing
date; the ID of the member or processor associated with the file; and a file
sequence number to uniquely identify the file. The combination of these four
subfields together form a value that uniquely identifies all files to or from a
member processing facility.
Subfields

Clearing Cycle (positions 21–22)
Note: This will be 99 if the member
receives clearing files containing data
from two or more clearings.
Delivery Cycle (position 23,
values 1–6)
Sequence Number (positions 24–25)
Refer to PDS 0105 in this chapter for descriptions of these subfields.

PDS 0298—Reconciled, Transmission

Reconciled, Transmission (PDS 0298) identifies in Reconciliation messages the
physical transmission to which the reconciliation totals pertain.
Note This PDS is not currently supported by GCMS.
Attributes
n-25; TAGLLL
Tag Field: 0298

Subfields: 4
Usage
messages:
Usage

This PDS reflects in Reconciliation acknowledgement messages the

Transmission ID (PDS 0110) of the offline clearing transmission to which the
reconciliation totals apply.
Each physical transmission may contain multiple data files (logical files).
These are identified in the offline clearing transmission File Header/1644 by
File ID (PDS 0105). In Reconciliation messages, Reconciled, File (PDS 0300)
presents and identifies reconciliation totals at the logical file level.
Reconciliation totals at the Transmission Identifier level are automatically

provided for acknowledgement message totals if the member supplies
PDS 0110 in its member-generated file.
Subfields

1 1–3 Transmission Type n-3 right
2 4–9 Transmission Reference Date n-6 right
4 21–25 Transmission Sequence Number n-5 right

PDS 0300—Reconciled, File

Reconciled, File (PDS 0300) identifies in Reconciliation messages the logical
file to which the reconciliation totals pertain.
Attributes
n-25; TAGLLL
Tag Field: 0300
Subfields: 4
Usage
messages:
Usage

Usage
In Reconciliation messages, this PDS contains the File ID (PDS 0105) of the
offline clearing logical file to which the reconciliation totals apply.
Multiple logical files may be present in a physical clearing transmission. In

Reconciliation messages, Reconciled, Transmission (PDS 0298) presents and
identifies reconciliation totals at the physical transmission level.
Subfields
For members requesting the Early Reconciliation file, this category is always
provided. This PDS contains four subfields as defined in the following table:

Clearing Cycle (positions 21–22)
Note: This will be 99 if the member
receives clearing files containing data
from two or more clearings.
Delivery Cycle (position 23,
values 1–6)
Sequence Number (positions 24–25)

PDS 0301—File Amount, Checksum

File Amount, Checksum (PDS 0301) provides a preliminary “quick check” for
the file recipient to indicate or to determine that it received all messages in a
file.
Attributes
n-16; TAGLLL
Tag Field: 0301
Subfields: none
Justification: right
Usage
messages:
Usage
File Trailer (Clearing System-Generated)/1644 • X C
This PDS contains the sum amount of all amounts from each occurrence of
Amount, Transaction (DE 4) in a logical file.
This sum is a hash total only, and ignores the currency code and currency
exponent associated with DE 4 in all cases.
This hash total includes only data from DE 4 when present in a message. This
PDS is not present in early Reconciliation messages. It does not include any
fee amounts.
Originators may provide all zeros in this field. If PDS 0301 contains a value
other than all zeros, the clearing system validates PDS 0301 against the sum of
all amounts in each occurrence of DE 4 within the logical file. The entire
logical file rejects if the values do not match.

Values
This PDS has no financial value.
The checksum amount is always initialized to zero before processing

messages. If no messages in the file contain DE 4, the checksum amount
remains all zeros.

PDS 0302—Reconciled, Member Activity

Reconciled, Member Activity (PDS 0302) indicates in Reconciliation messages
whether the related reconciliation totals represent acquiring activity, issuing
activity or fee collection activity.
Attributes
a-1; TAGLLL
Tag Field: 0302

Subfields: none
Justification: n/a
Usage
messages:
Usage
This PDS indicates in Reconciliation messages whether the related

reconciliation totals represent acquiring activity, issuing activity, or fee
collection activity. Refer to the beginning of chapter 5 in this manual for
additional information about classifying activity into one of these categories.

Values
Value Description
A Acquiring activity.
I Issuing activity.
F Fee collection activity.

PDS 0306—File Message Counts
PDS 0306—File Message Counts

File Message Counts (PDS 0306) provides a preliminary “quick check” for the
file recipient to indicate that all records in a file have been received. It
contains the total number of messages in the file.
Attributes
n-8; TAGLLL
Tag Field: 0306

Subfields: none
Usage
messages:
Usage
This PDS contains the total count of messages occurring in a logical file,
including the File Header (Member-Generated or Clearing System-
Generated)/1644 and File Trailer (Member-Generated or Clearing System-
Generated)/1644. This PDS is provided in File Trailer (Member-
Generated)/1644 and File Trailer (Clearing System-Generated)/1644 messages.
Originators may provide all zeros in this field. If PDS 0306 contains a value
other than all zeros, the clearing system validates PDS 0306 against the total of
all messages in the logical file, including the File Header/1644 and File
Trailer/1644. The entire logical file rejects if the counts do not match.

PDS 0358—Reconciled, Business Activity

Reconciled, Business Activity (PDS 0358) identifies in Reconciliation messages
the business activity to which the reconciliation totals pertain.
Current Attributes
ans…20; TAGLLLVAR
Tag Field: 0358
Subfields: 6
Future Attributes
ans….24; TAGLLLVAR
Tag Field: 0358
Subfields: 10
Usage
messages:
Usage
s2 Business Service Arrangement Type Code • X C

Usage
s2 Business Service Arrangement Type Code • X C
This PDS reflects in Reconciliation messages, the Business Activity (PDS 0158)
to which the related reconciliation totals apply.

Subfields
This PDS currently consists of six subfields as defined in the following table:

1 1–3 Card Program Identifier an-3 n/a
2 4 Business Service Arrangement n-1 n/a
Type Code
3 5–10 Business Service ID Code an-6 left
4 11–12 Interchange Rate Designator an-2 n/a
5 13–18 Business Date (YYMMDD) n-6 n/a
6 19–20 Business Cycle n-2 n/a
7 21 Card Acceptor Business Code a-1 n/a
(MCC) Override Indicator
8 22 Product Override Indicator a-1 n/a
9 23 Corporate Incentive Rates Apply a-1 n/a
Indicator
10 24 ATM Late Presentment Indicator a-1 n/a

PDS 0359—Reconciled, Settlement Activity

Reconciled, Settlement Activity (PDS 0359) identifies in Reconciliation
messages the settlement activity to which the reconciliation totals pertain.
Note This PDS currently is not supported in GCMS.
Attributes
ans…67; TAGLLLVAR
Tag Field: 0359
Subfields: 9
Usage
messages:
Usage

Usage
This PDS reflects in Reconciliation messages, the settlement activity (Settlement

Data 1 [PDS 0159] and Settlement Data 2 [PDS 0161]) to which the related

Subfields
This PDS consists of nine subfields as defined in the following table:

Agent ID Code
Agent Account
3 40 Settlement Service Level Code n-1 right
Rate Class Code
6 52-57 Reconciliation Date n-6; n/a
YYMMDD
8 60–65 Settlement Date n-6; n/a
YYMMDD
Refer to PDS 0159 or PDS 0161 in this chapter for descriptions of these
subfields.

PDS 0370—Reconciled, Account Range

Reconciled, Account Range (PDS 0370) identifies in Reconciliation messages
the specific member issuing account range to which the reconciliation totals
pertain.
Attributes
n…38; TAGLLLVAR
Tag Field: 0370

Subfields: 2
Usage
messages:
Usage

This PDS reflects in Reconciliation messages, the specific member account

range (obtained from the account range portion of Primary Account Number
[PAN] [DE 2]) to which the related reconciliation totals apply. Members
selecting this reconciliation category will receive totals only for their own
issuing account ranges that have been established at MasterCard.
If the Reconciled, Account Range reconciliation category is selected, the

Reconciled Member Activity reconciliation category also must be selected to
ensure that the member receives totals by issuing account range, acquiring
activity, and fee collection activity to provide complete reconciliation
information.
Subfields

1 1–19 Beginning Account Range ID n-19 n/a
2 20–38 Ending Account Range ID n-19 n/a
Account ranges are profiled for each issuer member ID.

PDS 0371—Reconciled, Message Reason Code
PDS 0371—Reconciled, Message Reason Code

Reconciled, Message Reason Code (PDS 0371) identifies in Reconciliation
messages the Message Reason Code (DE 25) value to which the reconciliation
totals pertain.
Attributes
n-4; TAGLLL
Tag Field: 0371

Subfields: none
Usage
messages:
Usage
Refer to DE 25 in chapter 7 in this manual for a complete list of message

reason codes.

PDS 0372—Reconciled, Transaction Function

Reconciled, Transaction Function (PDS 0372) identifies in Reconciliation
messages the transaction function to which the reconciliation totals pertain.
Attributes
n-7; TAGLLL
Tag Field: 0372
Subfields: 2
Usage
messages:
Usage
This PDS reflects in Reconciliation messages, the transaction function to which

the related reconciliation totals apply. A transaction function consists of MTI
and Function Code (DE 24).

Subfields

1 1–4 Message Type Identifier n-4 right
2 5–7 Function Code n-3 right
Values
Refer to DE 24 in chapter 7 in this manual for a list of valid transaction
function codes.

PDS 0373—Reconciled, Card Acceptor ID
PDS 0373—Reconciled, Card Acceptor ID

Reconciled, Card Acceptor ID (PDS 0373) identifies in Reconciliation messages
the card acceptor (merchant) to which the reconciliation totals pertain.
Attributes
ans-15; TAGLLL
Tag Field: 0373
Subfields: none
Justification: left
Usage
messages:
Usage
This PDS reflects in Reconciliation messages, the Card Acceptor ID (DE 42) to
which the related reconciliation totals apply.
Values
The acquirer assigns Card acceptor ID values.

PDS 0374—Reconciled, Processing Code
PDS 0374—Reconciled, Processing Code

Reconciled, Processing Code (PDS 0374) identifies in Reconciliation messages
the Processing Code, or transaction type, to which the reconciliation totals
pertain.
Attributes
n-2; TAGLLL
Tag Field: 0374

Subfields: none
Justification: n/a
Usage
messages:
Usage
This PDS reflects in Reconciliation messages, subfield 1, Cardholder

Transaction Type, of Processing Code (DE 3) to which the related
Values
Refer to DE 3, subfield 1, in chapter 7 of this manual for a list of values.

PDS 0375—Member Reconciliation Indicator 1

Member Reconciliation Indicator 1 (PDS 0375) contains a proprietary value a
transaction originator defines that may be assigned to its outgoing financial
messages.
Attributes
ans…50; TAGLLLVAR
Tag Field: 0375

Subfields: none
Justification: left
Usage
messages:
Usage
First Presentment/1240 O • •
First Chargeback/1442 and Arbitration Chargeback/1442 O • •
Second Presentment/1240 O • •
Retrieval Request/1644 O • •
Fee Collection (Retrieval Fee Billing)/1740 O • •
Fee Collection (Handling Fees)/1740 O • •
Fee Collection (Other than Retrieval Fee Billing/Handling Fees)/1740 O • •

Members can assign a proprietary value to PDS 0375 and include it in any
financial message. If an originating member provides PDS 0375 in financial
messages, and chooses to receive Reconciliation messages at this level, the
clearing system provides reconciliation totals based on the unique values
present.
For any First Presentment/1240, Retrieval Request/1644, or Fee Collection/1740

Messages that does not contain PDS 0375, the clearing system will create an
acknowledgement message with a Member Reconciliation indicator 1 value of
“Undefined.” This will ensure that the Acknowledgement reconciliation
provided represents 100% of the accepted financial activity of the member for
that file. The value in PDS 0300 will also be “Undefined.”
For example, an acquirer that wants to receive reconciliation totals for a

specific card acceptor chain could populate this PDS with the chain descriptor.
Then the clearing system would accumulate totals based on this value in
addition to the other reconciliation options the acquirer selects.
This PDS is available only for Acknowledgement Reconciliation messages.
Values
The transaction originator assigns PDS 0375 values. If present, PDS 0375 must
be left justified and cannot contain all spaces, all zeros, low-values, or high-
values.


Member Reconciliation Indicator 2 (PDS 0376) contains a proprietary value a
transaction originator defines that may be assigned to its outgoing Financial
messages.
Attributes
ans…99; TAGLLLVAR
Tag Field: 0376

Subfields: none
Justification: n/a
Usage
messages:
Usage
First Presentment/1240 O • •
First Chargeback/1442 and Arbitration Chargeback/1442 O • •
Second Presentment/1240 O • •

Usage
Fee Collection (Retrieval Fee Billing)/1740 O • •
Fee Collection (Handling Fees)/1740 O • •
Fee Collection (Other than Retrieval Fee Billing/Handling Fees)/1740 O • •
Members can assign a proprietary value to PDS 0376 and include it in any
financial message. If an originating member provides PDS 0376 in financial
messages, and chooses to receive Reconciliation messages at this level, the
clearing system provides reconciliation totals based on the unique values
present.
For example, an acquirer who wishes to receive reconciliation totals for a

specific card acceptor chain could populate this PDS with the chain descriptor.
Then the clearing system would accumulate totals based on this value in
addition to the other reconciliation options the acquirer selects.
This PDS is only available for Acknowledgement Reconciliation messages.
Values
The transaction originator assigns PDS 0376 values.

PDS 0378—Original/Reversal Totals Indicator

Original/Reversal Totals Indicator (PDS 0378) indicates in Reconciliation
messages whether the related reconciliation totals represent original
transactions or reversal transactions.
Attributes
a-1; TAGLLL
Tag Field: 0378

Subfields: none
Justification: n/a
Usage
messages:
Usage
This PDS indicates in Reconciliation messages whether the related

reconciliation totals represent original activity or reversal activity. Amounts are
accumulated as “original” activity if Reversal Indicator (PDS 0025) is not
present in the message or if the transaction is a resubmission (subfield 1 of
PDS 0025 contains a space and subfield 2 contains a date). Amounts are
accumulated as “reversal” activity if PDS 0025 is present in the message and
subfield 1 contains an R.

Values
The following values may be provided in this PDS.
Value Description
O Original message amounts.
R Reversal message amounts.

PDS 0380—Debits, Transaction Amount In Transaction Currency
PDS 0380—Debits, Transaction Amount In Transaction

Currency
Debits, Transaction Amount in Transaction Currency (PDS 0380) provides in
Reconciliation messages the total of transaction amounts that have a debit
impact on processing. The total is in the transaction currency.
Attributes
an-17; TAGLLL
Tag Field: 0380
Subfields: 2
Usage
messages:
Usage

PDS 0380—Debits, Transaction Amount In Transaction Currency
This PDS provides in Reconciliation messages, totals in the transaction

currency of transaction amounts with a debit impact to processing. To do this,
the clearing system accumulates Amount, Transaction (DE 4) for each message
in which Processing Code (DE 3) indicates a debit impact on processing to the
appropriate member. Refer to the beginning of chapter 5 in this manual for
additional information on classifying activity as “debit impact” versus “credit
impact.”
Subfields

1 1 Debit/Credit Indicator a-1; n/a
constant—D
2 2–17 Amount, Transaction n-16 right
Values
This PDS may contain zeros if the processed file contained only non-financial
messages and DE 25 = 6861 (Acknowledgement).

PDS 0381—Credits, Transaction Amount in Transaction Currency
PDS 0381—Credits, Transaction Amount in Transaction

Currency
Credits, Transaction Amount in Transaction Currency (PDS 0381) provides in
Reconciliation messages the total of transaction amounts that have a credit
impact on processing. The total is in the transaction currency.
Attributes
an-17; TAGLLL
Tag Field: 0381
Subfields: 2
Usage
messages:
Usage

PDS 0381—Credits, Transaction Amount in Transaction Currency
This PDS provides in Reconciliation/1644 messages, totals in the transaction

currency of transaction amounts with a credit impact to processing. To do
this, the clearing system accumulates Amount, Transaction (DE 4) for each
message in which Processing Code (DE 3) indicates a credit impact on
processing to the appropriate member. Refer to the beginning of chapter 5 in
this manual for additional information on classifying activity as “debit impact”
versus “credit impact.”
Subfields

constant—C
Values

PDS 0384—Amount, Net Transaction in Transaction Currency
PDS 0384—Amount, Net Transaction in Transaction

Currency
Amount, Net Transaction in Transaction Currency (PDS 0384) provides in
Reconciliation messages the net total of transaction amounts that have a debit
impact on processing and those that have a credit impact on processing. The
net total is in the transaction currency.
Attributes
an-17; TAGLLL
Tag Field: 0384
Subfields: 2
Usage
messages:
Usage
s2 Amount, Net (unsigned) • X M
s2 Amount, Net (unsigned) • X C
s2 Amount, Net (unsigned) • X C

PDS 0384—Amount, Net Transaction in Transaction Currency
This PDS provides in Reconciliation messages, net totals in the transaction

currency of transaction amounts with a debit impact to settlement and those
with a credit impact to settlement.
If the amount in Debits, Transaction Amount in Transaction Currency

(PDS 0380) is greater than the amount in Credits, Transaction Amount in
Transaction Currency (PDS 0381), the clearing system inserts a D in subfield 1
of PDS 0384 and inserts the excess amount in subfield 2 of PDS 0384.
If the amount in PDS 0381 is greater than the amount in PDS 0380, the clearing
system inserts a C in subfield 1 of PDS 0384 and inserts the excess amount in
subfield 2 of PDS 0384.
Subfields

value D or C
2 2–17 Amount, Net n-16 right
Values

PDS 0390—Debits, Transaction Amount in Reconciliation Currency
PDS 0390—Debits, Transaction Amount in Reconciliation

Currency
Debits, Transaction Amount in Reconciliation Currency (PDS 0390) provides in
Reconciliation messages the total of transaction amounts that have a debit
impact on processing. The total is in the message receiver’s reconciliation
currency.
Attributes
an-17; TAGLLL
Tag Field: 0390
Subfields: 2
Usage
messages:
Usage

PDS 0390—Debits, Transaction Amount in Reconciliation Currency
This PDS provides in Reconciliation/1644 messages, totals in the reconciliation

currency of transaction amounts with a debit impact to processing. To do this,
the clearing system accumulates Amount, Reconciliation (DE 5) for each
message in which Processing Code (DE 3) indicates a debit impact on
The Financial Position Detail/1644, the Settlement Position Detail/1644, and the
Settlement Position Total/1644 messages all will contain totals in the receiving
Subfields

1 1 Debit/Credit Indicator a-1; value D n/a
Values
This PDS may contain zeros in the acknowledgement reconciliation messages
if the processed file contained only non-financial messages and DE 25 = 6861
(Acknowledgement).
This element contains the sum of DE 5 by currency identified in DE 50 and

other reconciliation options in effect. Reconciliation messages that reflect
totals for bilateral and Collection only activity will contain zeros in this PDS.

PDS 0391—Credits, Transaction Amount in Reconciliation Currency
PDS 0391—Credits, Transaction Amount in Reconciliation

Currency
Credits, Transaction Amount in Reconciliation Currency (PDS 0391) provides in
Reconciliation messages the total of transaction amounts that have a credit
impact on processing. The total is in the reconciliation currency.
Attributes
an-17; TAGLLL
Tag Field: 0391
Subfields: 2
Usage
messages:
Usage

PDS 0391—Credits, Transaction Amount in Reconciliation Currency

currency of transaction amounts with a credit impact to processing. To do
this, the clearing system accumulates Amount, Reconciliation (DE 5) for each
message in which Processing Code (DE 3) indicates a credit impact on
Subfields

1 1 Debit/Credit Indicator a-1; constant—C n/a
Values
(Acknowledgement).

totals for bilateral and Collection Only activity will contain zeros in this PDS.

PDS 0392—Debits, Fee Amounts in Reconciliation Currency

Debits, Fee Amounts in Reconciliation Currency (PDS 0392) provides in
Reconciliation messages the total of fee amounts that have a debit impact on
processing. The total is in the reconciliation currency.
Attributes
an…180; TAGLLLVAR
Tag Field: 0392

Subfields: 3
Occurrences: 1–12
Usage
messages:
Usage

Usage

currency of fee amounts with a debit impact to processing. To do this, the
clearing system accumulates all occurrences of subfield 7, Amount, Fee,
Reconciliation, of Amounts, Transaction Fee (PDS 0146) for each message in
which subfield 2, Fee Processing Code, of PDS 0146 indicates a debit impact
on processing to the appropriate member. Refer to the beginning of chapter 5
in this manual for additional information on classifying activity as “debit
impact” versus “credit impact.”
Subfields

constant—D
Values
(Acknowledgement).
This element contains the sum of PDS 0146 by currency identified in DE 50

and other reconciliation options in effect. Reconciliation messages that reflect

PDS 0393—Credits, Fee Amounts In Reconciliation Currency
PDS 0393—Credits, Fee Amounts In Reconciliation

Currency
Credits, Fee Amounts in Reconciliation Currency (PDS 0393) provides in
Reconciliation messages the total of fee amounts that have a credit impact on
processing. The total is in the reconciliation currency.
Attributes
an…180; TAGLLLVAR
Tag Field: 0393
Subfields: 3
Occurrences: 1–12
Usage
messages:
Usage

PDS 0393—Credits, Fee Amounts In Reconciliation Currency
Usage

currency of fee amounts with a credit impact to processing. To do this, the
clearing system accumulates all occurrences of subfield 7, Amount, Fee,
Reconciliation, of Amounts, Transaction Fee (PDS 0146) for each message in
which subfield 2, Fee Processing Code, of PDS 0146 indicates a credit impact
on processing to the appropriate member. Refer to the beginning of chapter 5
in this manual for additional information on classifying activity as “debit
impact” versus “credit impact.”
Subfields

constant—C
Values
This PDS may contain zeros in the Acknowledgement Reconciliation messages
(Acknowledgement).


PDS 0394—Amount, Net Transaction in Reconciliation Currency
PDS 0394—Amount, Net Transaction in Reconciliation

Currency
Amount, Net Transaction in Reconciliation Currency (PDS 0394) provides in
Reconciliation messages the net total of the transaction amounts that have a
debit impact on processing and those that have a credit impact on processing.
The net total is in the reconciliation currency.
Attributes
an-17; TAGLLL
Tag Field: 0394
Subfields: 2
Usage
messages:
Usage

PDS 0394—Amount, Net Transaction in Reconciliation Currency
This PDS provides in Reconciliation/1644 messages, net totals in the

reconciliation currency of transaction amounts with a debit impact to
processing and those with a credit impact to processing.
If the amount in Debits, Transaction Amount in Reconciliation Currency (PDS

0390) is greater than the amount in Credits, Transaction Amount in
Reconciliation Currency (PDS 0391), the clearing system inserts a D in subfield
1 of PDS 0394 and inserts the excess amount in subfield 2 of PDS 0394.
If the amount in PDS 0391 is greater than the amount in PDS 0390, the clearing
system inserts a C in subfield 1 of PDS 0394 and inserts the excess amount in
subfield 2 of PDS 0394.
Subfields

value D or C
2 2–17 Amount, Net n-16 right
Values
(Acknowledgement).


PDS 0395—Amount, Net Fee in Reconciliation Currency

Amount, Net Fee in Reconciliation Currency (PDS 0395) provides in
Reconciliation messages the net total of fee amounts that have a debit impact
on processing and those that have a credit impact on processing. The net total
is in the reconciliation currency.
Attributes
an-13; TAGLLL
Tag Field: 0395
Subfields: 2
Usage
messages:
Usage
s2 Amount, Net Fee (unsigned) • X M


reconciliation currency of fee amounts with a debit impact to processing and
those with a credit impact to processing.
If the sum of all amounts in Debits, Fee Amounts in Reconciliation Currency

(PDS 0392) is greater than the sum of all amounts in Credits, Fee Amounts in
Reconciliation Currency (PDS 0393), the clearing system inserts a D in subfield
1 of PDS 0395 and inserts the excess amount in subfield 2 of PDS 0395.
If the sum of all amounts in PDS 0393 is greater than the sum of all amounts in
PDS 0392, the clearing system inserts a C in subfield 1 of PDS 0395 and inserts
the excess amount in subfield 2 of PDS 0395.
Subfields

value D or C
2 2–13 Amount, Net Fee n-12 right
Values
(Acknowledgement).


PDS 0396—Amount, Net Total in Reconciliation Currency

Amount, Net Total in Reconciliation Currency (PDS 0396) provides in
Reconciliation messages the net total of transaction and fee amounts. The net
total is in the reconciliation currency.
Attributes
an-17; TAGLLL
Tag Field: 0396

Subfields: 2
Usage
messages:
Usage
s2 Amount, Net Total (unsigned) • X M


reconciliation currency of transaction amounts and fee amounts. The values
used in calculating PDS 0396 are from Amount, Net Transaction in
Reconciliation Currency (PDS 0394) and Amount, Net Fee in Reconciliation
Currency (PDS 0395).
If subfield 1, Debit/Credit Indicator, of both PDS 0394 and PDS 0395 contains a
D, the system inserts a D in subfield 1 of PDS 0396 and inserts the total of the
“amount” subfields from PDS 0394 and PDS 0395 in subfield 2 of PDS 0396.
If subfield 1, Debit/Credit Indicator, of both PDS 0394 and PDS 0395 contains a
C, the clearing system inserts a C in subfield 1 of PDS 0396 and inserts the total
of the “amount” subfields from PDS 0394 and PDS 0395 in subfield 2 of
PDS 0396.
If PDS 0394 and PDS 0395 contain two different values in subfield 1, the
clearing system selects the Debit/Credit Indicator associated with the larger of
the two “amount” subfields and inserts it in subfield 1 of PDS 0396. The
clearing system then calculates the difference between the two “amount”
subfields and inserts the result in subfield 2 of PDS 0396.
Subfields

value D or C
2 2–17 Amount, Net Total n-16 right
Values
(Acknowledgement). Reconciliation messages that reflect totals for bilateral
and Collection Only activity will contain zeros in this PDS.

PDS 0400—Debits, Transaction Number
PDS 0400—Debits, Transaction Number

Debits, Transaction Number (PDS 0400) provides in Reconciliation messages
the number of transactions whose transaction amounts have a debit impact on
processing.
Attributes
n-10; TAGLLL
Tag Field: 0400

Subfields: none
Usage
messages:
Usage
This PDS provides in Reconciliation/1644 messages, the total number of

transactions whose transaction amounts have a debit impact to processing. To
do this, the clearing system accumulates the number of messages for which
Processing Code (DE 3) indicates a debit impact on processing to the
impact.”
Values
messages.

PDS 0401—Credits, Transaction Number
PDS 0401—Credits, Transaction Number

Credits, Transaction Number (PDS 0401) provides in Reconciliation messages
the number of transactions whose transaction amounts have a credit impact on
processing.
Attributes
n-10; TAGLLL
Tag Field: 0401

Subfields: none
Usage
messages:
Usage

transactions whose transaction amounts have a credit impact to processing. To
do this, the clearing system accumulates the number of messages for which
Processing Code (DE 3) indicates a credit impact on processing to the
impact.”
Values
messages.

PDS 0402—Total, Transaction Number
PDS 0402—Total, Transaction Number

Total, Transaction Number (PDS 0402) provides in Reconciliation messages the
number of transactions whose transaction amounts have either a debit or a
credit impact on processing.
Attributes
n-10; TAGLLL
Tag Field: 0402

Subfields: none
Usage
messages:
Usage

transactions whose transaction amounts have either a debit or a credit impact
to processing. To do this, the clearing system accumulates Debits, Transaction
Number (PDS 0400) and Credits, Transaction Number (PDS 0401) and inserts
the result in PDS 0402.
Values
messages.

0501–0600 used in IPM format offline clearing messages.
Overview .............................................................................................................9-1
PDS 0501—Transaction Description...................................................................9-2
PDS 0505—Passenger Name.............................................................................9-10
PDS 0506—Ticket Number ...............................................................................9-12
PDS 0507—Issuing Carrier ................................................................................9-14
PDS 0508—Customer Code ..............................................................................9-16
PDS 0509—Issue Date.......................................................................................9-18
PDS 0510—Travel Agency Code ......................................................................9-19
PDS 0511—Travel Agency Name .....................................................................9-20
PDS 0512—Total Fare .......................................................................................9-21
PDS 0513—Total Fees .......................................................................................9-22
PDS 0514—Total Taxes.....................................................................................9-23
PDS 0515—Additional Card Acceptor Information..........................................9-24
PDS 0516—Austin-Tetra Number .....................................................................9-25
PDS 0517—NAICS Code ...................................................................................9-26
PDS 0518—Line Item Date ...............................................................................9-27
PDS 0519—Additional Fuel Location Information ...........................................9-28
PDS 0520—Travel Date.....................................................................................9-32

PDS 0521—Carrier Code ...................................................................................9-34
PDS 0522—Service Class Code .........................................................................9-36
PDS 0523—City of Origin/Airport Code...........................................................9-38
PDS 0524—City of Destination/Airport Code ..................................................9-40
PDS 0525—Stop Over Code .............................................................................9-42
PDS 0526—Conjunction Ticket.........................................................................9-44
PDS 0527—Exchange Ticket.............................................................................9-45
PDS 0528—Coupon Number ............................................................................9-46
PDS 0529—Fare Basis Code .............................................................................9-47
PDS 0530—Flight Number ................................................................................9-48
PDS 0531—Departure Time..............................................................................9-49
PDS 0532—Total Charges .................................................................................9-51
PDS 0533—Arrival Time....................................................................................9-53
PDS 0534—Total Non-Room Charges ..............................................................9-55
PDS 0535—Fare.................................................................................................9-57
PDS 0536—Fee ..................................................................................................9-58
PDS 0537—Taxes ..............................................................................................9-59
PDS 0538—Endorsements/Restrictions.............................................................9-60
PDS 0539—Total Amount Charged on Card ....................................................9-61
PDS 0540—Room Service Charges ...................................................................9-63
PDS 0541—Lounge/Bar Charges ......................................................................9-65
PDS 0542—Transportation Charges..................................................................9-67

PDS 0543—Gratuity Charges ............................................................................9-69
PDS 0544—Rental Agreement Number ............................................................9-71
PDS 0545—Renter Name ..................................................................................9-72
PDS 0546—Rental Return City ..........................................................................9-74
PDS 0547—Rental Return State/Province .........................................................9-76
PDS 0548—Rental Return Country ...................................................................9-78
PDS 0549—Rental Return Location ID .............................................................9-80
PDS 0550—Rental Return Date.........................................................................9-81
PDS 0551—Rental Check-Out Date ..................................................................9-82
PDS 0552—Customer Service Toll-Free (800) Number ...................................9-83
PDS 0553—Rental Rate .....................................................................................9-85
PDS 0554—Conference Room Charges ............................................................9-87
PDS 0555—Rate Per Mile (or Per Kilometer)...................................................9-89
PDS 0556—Total Miles (or Kilometers)............................................................9-90
PDS 0557—Maximum Free Miles (or Kilometers) ...........................................9-91
PDS 0558—Miles/Kilometers Indicator ............................................................9-92
PDS 0559—Vehicle Insurance ..........................................................................9-93
PDS 0560—Audio Visual Charges ....................................................................9-95
PDS 0561—Adjusted Amount ...........................................................................9-97
PDS 0562—Banquet Charges............................................................................9-99
PDS 0563—Program Code .............................................................................. 9-101
PDS 0564—Rental Location City ..................................................................... 9-102

PDS 0565—Rental Location State/Province.................................................... 9-103
PDS 0566—Rental Location Country .............................................................. 9-104
PDS 0567—Rental Location ID ....................................................................... 9-105
PDS 0568—Rental Class ID............................................................................. 9-106
PDS 0569—Internet Access Charges............................................................... 9-109
PDS 0570—Early Departure Charges.............................................................. 9-111
PDS 0571—Guest Name.................................................................................. 9-113
PDS 0572—Guest Number.............................................................................. 9-114
PDS 0573—Invoice Number ........................................................................... 9-115
PDS 0574—Arrival Date .................................................................................. 9-116
PDS 0575—Departure Date ............................................................................ 9-117
PDS 0576—Folio Number ............................................................................... 9-118
PDS 0577—Property Phone Number.............................................................. 9-120
PDS 0578—Billing Adjustment........................................................................ 9-122
PDS 0579—Invoice Date................................................................................. 9-124
PDS 0580—Room Rate .................................................................................... 9-125
PDS 0581—Total Room Tax ........................................................................... 9-127
PDS 0582—Program Code .............................................................................. 9-129
PDS 0583—Phone Charges ............................................................................. 9-130
PDS 0584—Restaurant Charges ...................................................................... 9-132
PDS 0585—Mini-Bar Charges.......................................................................... 9-134
PDS 0586—Gift Shop Charges ........................................................................ 9-136

PDS 0587—Laundry and Dry Cleaning Charges ............................................ 9-138
PDS 0588—Other Services .............................................................................. 9-140
PDS 0589—Invoice Creation Date/Time ........................................................ 9-142
PDS 0590—Party Identification....................................................................... 9-144
PDS 0591—Party Name................................................................................... 9-146
PDS 0592—Party Address ............................................................................... 9-148
PDS 0593—Party Postal Information .............................................................. 9-150
PDS 0594—Party Contact ................................................................................ 9-152
PDS 0595—Card Acceptor Type..................................................................... 9-154
PDS 0596—Card Acceptor Tax ID.................................................................. 9-160
PDS 0597—Total Tax Amount ........................................................................ 9-162
PDS 0598—Total Tax Collected Indicator ...................................................... 9-166
PDS 0599—Corporation VAT Number ........................................................... 9-168
PDS 0600—Card Acceptor Reference Number .............................................. 9-169

Overview
Overview
This chapter provides detailed definitions for private data subelements (PDSs)
0501–0600. For specific information about PDS construction and use, intra-
European, Maestro®, and Cirrus® transactions, and for numerical and
alphabetical PDS listings see the beginning of chapter 8 in this manual.
Note Some information in this chapter may be shaded. Shading indicates IPM

PDS 0501—Transaction Description

Transaction Description (PDS 0501) contains information describing the type of
addendum data being presented.
Attributes
n-16; TAGLLL
Tag Field: 0501
Subfields: 4
Usage
messages:
Usage
Data)/1644

Usage

Usage
Financial Detail Addendum (Electronic Invoice—Transaction M • M
Data)/1644
Financial Detail Addendum (Electronic Invoice—Party M • M
Information)/1644
Financial Detail Addendum (Telephony Billing—Summary)/1644 M • M
Financial Detail Addendum (Telephony Billing—Detail)/1644 M • M
Requirements)/1644

Usage
Information)/1644
This PDS provides the information necessary to identify the type of addendum
information in a Financial Detail Addendum/1644. The PDS also contains a
sequence number to associate the addendum message with the related First
Presentment/1240.
PDS 0501 subfields are formatted as described in the following table:

1 1–2 Usage Code n-2 n/a
2 3–5 Industry Record Number n-3 right
3 6–8 Occurrence Indicator n-3 right
4 9–16 Associated First Presentment n-8 right
Number

Subfield 1: Usage Code

Usage Code indicates the type of addendum data to be provided. The Usage
Codes supporting various industries or programs are in the following table:
Usage Transaction Detail Supported Card Acceptor Category,

Code Description Industry, or Programs
01 Passenger Transport Detail Airline, railway.
05 Vehicle Rental Detail Vehicle rental agencies.
06 Lodging Summary Hotel, motel, and related lodging facilities.
07 Temporary Services New business opportunities for the
temporary services sector.
08 Shipping/Courier Services New business opportunities for the
shipping/courier services sector.
09 Electronic Invoice— New business opportunities to allow issuers
Transaction Data/Party to supply more transaction information to
Information their corporate clients.
10 Payment Transaction Detail Payments from money transfer agents or
financial institutions.
11 Telephony Billing— New business opportunities for companies
Detail/Summary to pay for telephony services using a
MasterCard Corporate Purchasing Card®.
98 Corporate Detail New business opportunities unique to the
corporate environment
99 Generic Detail Other new business opportunities
New Usage Codes are added periodically as required to support various

industry and card acceptor organizations. The clearing system validates the
Usage Code and rejects a message if it contains an invalid Usage Code.

Subfield 2: Industry Record Number

The Usage Code and Industry Record Number are used in conjunction to
uniquely identify the addendum data format (layout) as shown in the following
table:
Industry
Record
Usage Code Number Description
01 000 Passenger Transport Detail—General Ticket Information
01 001 Passenger Transport Detail—Trip Leg Data
05 000 Vehicle Rental Detail
06 000 Lodging Summary
07 000 Temporary Services
08 000 Shipping/Courier Services
09 000 Electronic Invoice—Transaction Data
09 001 Electronic Invoice—Party Information
10 000 Payment Transaction Detail
11 000 Telephony Billing—Summary
11 001 Telephony Billing—Detail
98 000 Corporate Detail—Corporate Card Common Data
Requirements
98 002 Corporate Detail—Corporate Fleet Transaction
Information
98 950 Corporate Detail—Corporate Line Item Detail
99 000 Generic Detail
New Industry Record Numbers are added periodically as required to support

various industry and card acceptor organizations. Members should prepare
their systems to accept new Industry Record Numbers. The clearing system
does not reject a message containing an unrecognized Industry Record
Number if it contains a valid Usage Code. Instead, the clearing system passes
the unedited contents of the addendum data to the receiving member. This
policy allows the timely assignment of new Industry Record Numbers in
response to specific needs, without waiting for corresponding updates to the
clearing system.

Subfield 3: Occurrence Indicator

The Occurrence Indicator identifies the specific occurrence number of each
addendum data in a particular usage code. Specific rules for Occurrence
Indicator (PDS 0501, subfield 3) are:
• For Financial Detail Addendum (Passenger Transport—General Ticket
Information)/1644 messages, (PDS 0501, subfield 1 Usage Code 01 and
PDS 0501, subfield 2 Industry Record Number 000) the value of PDS 0501,
subfield 3 Occurrence Indicator must be 001.
• For Financial Detail Addendum (Passenger Transport—Trip Leg Data)/1644
messages, (PDS 0501, subfield 1 Usage Code 01 and PDS 0501, subfield 2
Industry Record Number 001) the value of PDS 0501, subfield 3
Occurrence Indicator must be within the range of 002–999.
• For Financial Detail Addendum (Vehicle Rental Detail)/1644 messages,
(PDS 0501, subfield 1 Usage Code 05 and PDS 0501, subfield 2 Industry
Record Number 000) the value of PDS 0501, subfield 3 Occurrence
Indicator must be within the range of 001–999.
• For Financial Detail Addendum (Lodging Summary)/1644 messages,
• For Financial Detail Addendum (Temporary Services)/1644 messages,
• For Financial Detail Addendum (Shipping/Courier Services)/1644 messages,
• For Financial Detail Addendum (Electronic Invoice—Transaction Data)
/1644 messages, (PDS 0501, subfield 1 Usage Code 09 and PDS 0501,
subfield 2 Industry Record Number 000) the value of PDS 0501, subfield 3
• For Financial Detail Addendum (Electronic Invoice—Party
Information)/1644 messages, (PDS 0501, subfield 1 Usage Code 09 and
subfield 3 Occurrence Indicator must be within the range of 002–999.

• For Financial Detail Addendum (Payment Transaction Detail)/1644

Occurrence Indicator must be 001.
• For Financial Detail Addendum (Telephony Billing—Summary)/1644
Occurrence Indicator must 001.
• For Financial Detail Addendum (Telephony Billing—Detail)/1644
• For Financial Detail Addendum (Corporate Card Common Data
Requirements)/1644 messages, (PDS 0501, subfield 1 Usage Code 98 and
subfield 3 Occurrence Indicator must be 001.
• For Financial Detail Addendum (Corporate Fleet Transaction Information)
/1644 messages, (PDS 0501, subfield 1 Usage Code 98 and PDS 0501,
subfield 2 Industry Record Number 002) the value of PDS 0501, subfield 3
Occurrence Indicator must be 001.
• For Financial Detail Addendum (Corporate Line Item Detail)/1644
Occurrence Indicator must be within the range 002-999.
• For Financial Detail Addendum (Generic Detail)/1644 messages,
Subfield 4: Associated First Presentment Number

The number in this subfield is copied from DE 71 of the associated First
Presentment/1240. The associated first presentment number is placed in this
subfield to tie the addendum message back to the related First
Presentment/1240.

PDS 0505—Passenger Name

Passenger Name (PDS 0505) contains the name of the passenger to whom the
ticket was issued.
Attributes
ans…29; TAGLLLVAR
Tag Field: 0505
Subfields: none
Justification: left
Usage
messages:
Usage
This PDS is required if the associated First Presentment/1240 contains an

airline card acceptor business code (MCC) or railway MCC and is submitted for
one of the following U.S. region incentive interchange rate programs.
IRD Description
10 Merit III Tier 1
11 Merit III Tier 2
12 Merit III Tier 3
78, 88, 98 Merit I
70, 80 Merit III Base

IRD Description
This PDS may optionally be provided for airline or railway transactions

submitted for any other interchange program.
Values
If present, PDS 0505 must be left justified and cannot contain all low-values, all
high-values, all spaces, or all zeros.

PDS 0506—Ticket Number

Ticket Number (PDS 0506) contains the number on the ticket.
Attributes
ans-15; TAGLLL
Tag Field: 0506

Subfields: none
Justification: left
Usage
messages:
Usage

IRD Description
10 Merit III Tier 1
11 Merit III Tier 2
12 Merit III Tier 3
78, 88, 98 Merit I

IRD Description

Values
If present, PDS 0506 must contain the ticket number, and be left justified and
cannot contain all low-values, all high-values, all spaces, or all zeros. If
multiple tickets are purchased using a single transaction, the primary ticket
number should be provided.

PDS 0507—Issuing Carrier

Issuing Carrier (PDS 0507) contains the standard abbreviation for the airline or
railway carrier issuing the ticket.
Attributes
ans-4; TAGLLL
Tag Field: 0507
Subfields: none
Justification: left
Usage
messages:
Usage

IRD Description
10 Merit III Tier 1
11 Merit III Tier 2
12 Merit III Tier 3
78, 88, 98 Merit I

IRD Description

Values
high-values, all spaces or all zeros. It may be populated with the carrier code
for the appropriate trip leg. For airline transactions, the carrier code is
obtained from the OAG or its equivalent.

PDS 0508—Customer Code

Customer Code (PDS 0508) contains the code that the cardholder supplied to
the card acceptor.
Attributes
ans…25; TAGLLLVAR
Tag Field: 0508
Subfields: none
Justification: left
Usage
messages:
Usage
Requirements)/1644

If the customer provides the customer code, then this PDS must be submitted
to qualify the transaction for the following U.S. region and international
incentive interchange rate program.
IRD Description
60 Corporate Face-to-Face
62 Corporate Large Ticket
67 Corporate Data Rate II
66 Corporate Data Rate III
Values
If present, PDS 0508 must be left justified and cannot contain all spaces.

PDS 0509—Issue Date
PDS 0509—Issue Date

Issue Date (PDS 0509) is the date the ticket was issued to the customer.
Attributes
n-6; TAGLLL
Tag Field: 0509

Subfields: none
Justification: n/a
Usage
messages:
Usage
Financial Detail Addendum (Passenger Transport Detail— O • C
Values
If present, PDS 0509 must contain a valid date in the format YYMMDD.

PDS 0510—Travel Agency Code
PDS 0510—Travel Agency Code

Travel Agency Code (PDS 0510) is a code assigned to the travel agency.
Attributes
ans-8; TAGLLL
Tag Field: 0510

Subfields: none
Justification: left
Usage
messages:
Usage
Values

PDS 0511—Travel Agency Name
PDS 0511—Travel Agency Name

Travel Agency Name (PDS 0511) is the name of the travel agency issuing the
ticket.
Attributes
ans…25; TAGLLLVAR
Tag Field: 0511
Subfields: none
Justification: left
Usage
messages:
Usage
Values

PDS 0512—Total Fare
PDS 0512—Total Fare

Total Fare (PDS 0512) is the total amount of the ticket and should equal the
amount of the transaction.
Attributes
n-12; TAGLLL
Tag Field: 0512

Subfields: none
Usage
messages:
Usage
Financial Detail Addendum (Passenger Transport Detail— C • C

the U.S. region Corporate T&E Rate III (89) incentive interchange rate program.
This PDS optionally may be provided for airline or railway transactions

Values
If present, PDS 0512 can contain all zeros. It cannot contain all spaces.

PDS 0513—Total Fees
PDS 0513—Total Fees

Total Fees (PDS 0513) is the amount of the fees associated with the ticket.
Attributes
n-12; TAGLLL
Tag Field: 0513

Subfields: none
Usage
messages:
Usage
Values
If present, PDS 0513 can contain all zeros.

PDS 0514—Total Taxes
PDS 0514—Total Taxes

Total Taxes (PDS 0514) is the amount of all the taxes associated with the
ticket.
Attributes
n-12; TAGLLL
Tag Field: 0514

Subfields: none
Usage
messages:
Usage
Values

PDS 0515—Additional Card Acceptor Information
PDS 0515—Additional Card Acceptor Information

Additional Card Acceptor Information (PDS 0515) contains information
pertaining to the card acceptor.
Attributes
ans…40; TAGLLLVAR
Tag Field: 0515

Subfields: none
Justification: left
Usage
messages:
Usage
Requirements)/1644
Values

PDS 0516—Austin-Tetra Number
PDS 0516—Austin-Tetra Number

Austin-Tetra Number (PDS 0516) contains the Austin-Tetra Number assigned to
the card acceptor.
Attributes
ans-15; TAGLLL
Tag Field: 0516

Subfields: none
Justification: left
Usage
messages:
Usage
Requirements)/1644
Values
If present, PDS 0516 cannot contain all low-values, all high-values, all spaces,
or all zeros.

PDS 0517—NAICS Code
PDS 0517—NAICS Code

NAICS Code (PDS 0517) contains the North American Industry Classification
System (NAICS) code assigned to the card acceptor.
Attributes
ans-15; TAGLLL
Tag Field: 0517

Subfields: none
Justification: left
Usage
messages:
Usage

Requirements)/1644
Values
If present, PDS 0517 cannot contain all low-values, all high-values, all spaces,
or all zeros.

PDS 0518—Line Item Date
PDS 0518—Line Item Date

Line Item Date (PDS 0518) contains the purchase date of the line item
referenced in the associated Corporate Card Line Item Detail.
Attributes
n-6; TAGLLL
Tag Field: 0518

Subfields: none
Justification: n/a
Usage
messages:
Usage
Financial Detail Addendum (Corporate Line Item Detail)/1644 C • C
Values
If present, PDS 0518 must contain a valid date in the format YYMMDD. This
field is required to be present in the Financial Detail Addendum (Corporate
Line Item Detail)/1644 message when a Financial Detail Addendum (Lodging
Summary)/1644 message is presented with the transaction.

PDS 0519—Additional Fuel Location Information

Additional Fuel Location Information (PDS 0519) contains additional
information about the fuel location, such as hours of operation and Interstate
Access/Exit Number.
Attributes
an-14; TAGLLL
Tag Field: 0519

Subfields: 14
Usage
messages:
Usage
Information)/1644
s1 Hours of Operation/24 hour Available O • C
s2 18 Wheeler Access Available O • C
s3 Diesel Sites Available O • C
s4 Interstate Access/Exit Number with Directions Available O • C
s5 Convenience Store Available O • C
s6 Truck Stop Restaurant Available O • C
s7 Truck Stop Hotel Available O • C
s8 Truck Stop with Showers Available O • C
s9 Vehicle Maintenance/Repair Bays Available O • C
s10 Car Wash Available O • C
s11 Aviation Locations Available O • C

Usage
s12 Marina Locations Available O • C
s13 Alternative Fuel Locations Available O • C
s14 Pay-At-Pump Available O • C
Subfields
This PDS consists of fourteen subfields as defined in the following table:

1 1 Hours of Operation/24 Hours a-1 n/a
Available
2 2 18 Wheeler Access Available a-1 n/a
3 3 Diesel Sites Available a-1 n/a
4 4 Interstate Access/Exit Number with a-1 n/a
Directions Available
5 5 Convenience Store Available a-1 n/a
6 6 Truck Stop Restaurant Available a-1 n/a
7 7 Truck Stop Hotel Available a-1 n/a
8 8 Truck Stop with Showers Available a-1 n/a
9 9 Vehicle Maintenance/Repair Bays a-1 n/a
Available
10 10 Car Wash Available a-1 n/a
11 11 Aviation Locations Available a-1 n/a
12 12 Marina Locations Available a-1 n/a
13 13 Alternative Fuel Locations Available a-1 n/a
14 14 Pay-At-Pump Available a-1 n/a

Subfield 1: Hours of Operation/24 Hours Available

Hours of Operation/24 Hours Available (PDS 0519, subfield 1) must have a
valid value of Y or N.
Subfield 2: 18 Wheeler Access Available

18 Wheeler Access Available (PDS 0519, subfield 2) must have a valid value of
Y or N.
Subfield 3: Diesel Sites Available

Diesel Sites Available (PDS 0519, subfield 3) must have a valid value of Y or N.
Subfield 4: Interstate Access/Exit Number with Directions

Available
Interstate Access/Exit Number with Directions Available (PDS 0519, subfield 4)
must have a valid value of Y or N.
Subfield 5: Convenience Store Available

Convenience Store Available (PDS 0519, subfield 5) must have a valid value of
Y or N.
Subfield 6: Truck Stop Restaurant Available

Truck Stop Restaurant Available (PDS 0519, subfield 6) must have a valid value
of Y or N
Subfield 7: Truck Stop Hotel Available

Truck Stop Hotel Available (PDS 0519, subfield 7) must have a valid value of Y
or N.
Subfield 8: Truck Stop with Showers Available

Truck Stop with Showers Available (PDS 0519, subfield 8) must have a valid
value of Y or N.
Subfield 9: Vehicle Maintenance/Repair Bays Available

Vehicle Maintenance/ Repair Bays Available (PDS 0519, subfield 9) must have
a valid value of Y or N.

Subfield 10: Car Wash Available

Car Wash Available (PDS 0519, subfield 10) must have a valid value of Y or N.
Subfield 11: Aviation Locations Available

Aviation Locations Available (PDS 0519, subfield 11) must have a valid value of
Y or N.
Subfield 12: Marina Locations Available

Marina Locations Available (PDS 0519, subfield 12) must have a valid value of
Y or N.
Subfield 13: Alternative Fuel Locations Available

Alternative Fuel Locations Available (PDS 0519, subfield 13) must have a valid
value of Y or N.
Subfield 14: Pay-At-Pump Available

Pay-at-Pump Available (PDS 0519, subfield 14) must have a valid value of
Y or N.
Values
If present, PDS 0519 must be a fixed length of 14, and each of the 14 subfields
subfield must contain a value of Y or N. If unknown, a value of N should be
provided.

PDS 0520—Travel Date

Travel Date (PDS 0520) is the effective ticket date, previously referred to as
departure date.
Attributes
n-6; TAGLLL
Tag Field: 0520
Subfields: none
Justification: n/a
Usage
messages:
Usage
Trip Leg Data)/1644


one of the following U.S. region incentive interchange rate programs:
IRD Description
10 Merit III Tier 1
11 Merit III Tier 2
12 Merit III Tier 3
Values
If present, PDS 0520 must be a valid date in the format YYMMDD. Members
must use the ticket purchase date for “open tickets.”

PDS 0521—Carrier Code

Carrier Code (PDS 0521) is the standard abbreviation for the airline or railway
carrier.
Attributes
ans-2; TAGLLL
Tag Field: 0521
Subfields: none
Justification: left
Usage
messages:
Usage
Trip Leg Data)/1644


IRD Description
10 Merit III Tier 1
11 Merit III Tier 2
12 Merit III Tier 3
Values
PDS 0521 is the Carrier Code obtained from the OAG or its equivalent.
If present, it must be left justified and cannot contain all low-values, all high-
values, all spaces, or all zeros.

PDS 0522—Service Class Code

Service Class Code (PDS 0522) is the service type (for example, coach or first
class).
Attributes
ans-2; TAGLLL
Tag Field: 0522
Subfields: none
Justification: left
Usage
messages:
Usage
Trip Leg Data)/1644


IRD Description
10 Merit III Tier 1
11 Merit III Tier 2
12 Merit III Tier 3
Values
PDS 0522 is the Service Class Code obtained from the OAG or its equivalent.
If present, it must be left justified and cannot contain all low-values, all high-

PDS 0523—City of Origin/Airport Code

City of Origin/Airport Code (PDS 0523) is the originating airport or railway
name’s standard abbreviation.
Attributes
ans-5; TAGLLL
Tag Field: 0523
Subfields: None
Justification: Left
Usage
messages:
Usage
Trip Leg Data)/1644


IRD Description
10 Merit III Tier 1
11 Merit III Tier 2
12 Merit III Tier 3
Values
PDS 0523 is the City of Origin/Airport Code obtained from the OAG or its
equivalent. If present, it must be left justified and cannot contain all low-
values, all high-values, all spaces, or all zeros.

PDS 0524—City of Destination/Airport Code

City of Destination/Airport Code (PDS 0524) is the destination airport or
railway name’s standard abbreviation.
Attributes
ans-5; TAGLLL
Tag Field: 0524
Subfields: None
Justification: Left
Usage
messages:
Usage
Trip Leg Data)/1644


IRD Description
10 Merit III Tier 1
11 Merit III Tier 2
12 Merit III Tier 3
Values
PDS 0524 is the City of Destination/Airport Code obtained from the OAG or
its equivalent. If present, it must be left justified and cannot contain all low-

PDS 0525—Stop Over Code

Stop Over Code (PDS 0525) contains a code indicating whether there was a
direct or a non-direct flight or route on the same ticket number.
Attributes
ans-1; TAGLLL
Tag Field: 0525

Subfields: none
Justification: n/a
Usage
messages:
Usage
Trip Leg Data)/1644

the U.S. region Corporate T&E III (IRD 89) incentive interchange rate program.


Values
PDS 0525 is the Stop Over Code obtained from the OAG or its equivalent. If
present, PDS 0525 may contain a space, but cannot contain all low-values or
all high-values. If present, a value of a space indicates a direct flight (for
example, no stopover). A value other than a space indicates a non-direct flight
(includes stopover).
Valid values for PDS 0525 are 0–9, A–Z, or space.

PDS 0526—Conjunction Ticket
PDS 0526—Conjunction Ticket

Conjunction Ticket (PDS 0526) is the ticket that contains additional coupons
on an itinerary that is more than four segments.
Attributes
ans-15; TAGLLL
Tag Field: 0526
Subfields: none
Justification: left
Usage
messages:
Usage
Data)/1644
Values
If present, PDS 0526 must be left justified and cannot contain all spaces, all
zeros, all low-values, or all high-values.

PDS 0527—Exchange Ticket
PDS 0527—Exchange Ticket

Exchange Ticket (PDS 0527) is the original ticket number replaced by a new
ticket number.
Attributes
ans-15; TAGLLL
Tag Field: 0527
Subfields: None
Justification: Left
Usage
messages:
Usage
Trip Leg Data)/1644
Values
If present, PDS 0527 must be left justified and cannot contain all spaces, all
zeros, all low-values, or all high-values.

PDS 0528—Coupon Number
PDS 0528—Coupon Number

Coupon Number (PDS 0528) contains information for each leg of travel for a
purchased ticket. A ticket can contain several legs of travel and each leg of
travel requires a separate coupon within the series identified by a coupon
number.
Attributes
ans-1; TAGLLL
Tag Field: 0528

Subfields: None
Justification: n/a
Usage
messages:
Usage
Trip Leg Data)/1644
Values
If present, PDS 0528 may contain a space but cannot contain all low-values, all

PDS 0529—Fare Basis Code
PDS 0529—Fare Basis Code

Fare Basis Code (PDS 0529) contains a code that carriers assign to a particular
ticket type, such as business class or discounted/nonrefundable.
Attributes
ans…15; TAGLLLVAR
Tag Field: 0529
Subfields: none
Justification: n/a
Usage
messages:
Usage
Trip Leg Data)/1644

the U.S. region Corporate T&E Rate III (IRD 89) incentive interchange rate
program.

Values
If present, PDS 0529 cannot contain all low-values, all high-values, all spaces
or all zeros.

PDS 0530—Flight Number
PDS 0530—Flight Number

Flight Number (PDS 0530) is the number that the operating or marketing
carrier assigned.
Attributes
ans-5; TAGLLL
Tag Field: 0530
Subfields: None
Justification: Left
Usage
messages:
Usage
Trip Leg Data)/1644


Values

PDS 0531—Departure Time

Departure Time (PDS 0531) is the time of departure provided by the airline
or railway, per trip leg.
Attributes
ans-5; TAGLLL
Tag Field: 0531
Subfields: 2
Usage
messages:
Usage
Trip Leg Data)/1644
s1 Departure Time C • C
s2 Departure Time Segment C • C



Subfields

1 1–4 Departure Time n-4 right
2 5 Departure Time Segment ans-1 n/a
Subfield 1: Departure Time

Departure Time consists of hours and minutes (hhmm), with an implied colon.
The hours (hh) must be 00–23 and the minutes (mm) must be 00–59.
Note Midnight is provided as 0000.
Subfield 2: Departure Time Segment

Departure Time Segment must contain one of the values in the following table:
Value Description
A 00:00 (midnight) to 11:59.
P 12:00 (noon) to 23:59.
space Unknown or not available.

PDS 0532—Total Charges

Total Charges (PDS 0532) contains the total amount of the room charges.
Attributes
ans-14; TAGLLL
Tag Field: 0532

Subfields: 3
Usage
messages:
Usage
s1 Total Charges Amount O • C
s2 Total Charges Exponent O • C
s3 Total Charges Sign O • C
Subfields

1 1–12 Total Charges Amount n-12 Right
2 13 Total Charges Exponent n-1 n/a
3 14 Total Charges Sign a-1 n/a

Subfield 1: Total Charges Amount

If PDS 0532 is present, subfield 1 must contain the amount of the charges, and
may be all zeros.
Subfield 2: Total Charges Exponent

If PDS 0532 is present, subfield 2 must contain a value of 0–5.
Subfield 3: Total Charges Sign

If PDS 0532 is present, subfield 3 must contain a value of D or C.
Value Description
D Total charges amount is a debit
C Total charges amount is a credit
Values
PDS 0532 Total Charges must be a fixed length of 14.

PDS 0533—Arrival Time

Arrival Time (PDS 0533) is the arrival time provided by the airline or railway,
per trip leg.
Attributes
ans-5; TAGLLL
Tag Field: 0533
Subfields: 2
Usage
messages:
Usage
Trip Leg Data)/1644
s1 Arrival Time O • C
s2 Arrival Time Segment O • C

Subfields

1 1–4 Arrival Time n-4 right
2 5 Arrival Time Segment ans-1 n/a
Subfield 1: Arrival Time

Arrival Time consists of hours and minutes (hhmm), with an implied colon.
The hours (hh) must be 00–23 and the minutes (mm) must be 00-–59.
Subfield 2: Arrival Time Segment

Arrival Time Segment must contain one of the values in the following table:
Value Description
A 00:00 (midnight) to 11:59.
P 12:00 (noon) to 11:59.
space Unknown or not available.

PDS 0534—Total Non-Room Charges

Total Non-Room Charges (PDS 0534) contains the total amount of the non-
room charges.
Attributes
ans-14; TAGLLL
Tag Field: 0534

Subfields: 3
Usage
messages:
Usage

s1 Total Non-Room Charges Amount O • C
s2 Total Non-Room Charges Exponent O • C
s3 Total Non-Room Charges Sign O • C

Subfields

1 1–12 Total Non-Room Charges n-12 Right
Amount
2 13 Total Non-Room Charges n-1 n/a
Exponent
3 14 Total Non-Room Charges Sign a-1 n/a
Subfield 1: Total Non-Room Charges Amount

If PDS 0534 is present, subfield 1 must contain the amount of the non-room
charges, and may be all zeros.
Subfield 2: Total Non-Room Charges Exponent

If PDS 0534 is present, subfield 2 must contain a value of 0–5.
Subfield 3: Total Non-Room Charges Sign

Value Description
D Total non-room charges amount is a debit
C Total non-room charges amount is a credit
Values
PDS 0534 Total Non-Room Charges must be a fixed length of 14.

PDS 0535—Fare
PDS 0535—Fare
Fare (PDS 0535) is the total amount of the trip leg ticket.
Attributes
n-12; TAGLLL
Tag Field: 0535

Subfields: None
Usage
messages:
Usage
Trip Leg Data)/1644
Values

PDS 0536—Fee
PDS 0536—Fee
Fee (PDS 0536) is the total fee amount, per trip leg, associated with the ticket.
Attributes
n-12; TAGLLL
Tag Field: 0536

Subfields: None
Usage
messages:
Usage
Trip Leg Data)/1644
Values

PDS 0537—Taxes
PDS 0537—Taxes
Taxes (PDS 0537) is the amount of the total taxes, per trip leg, associated with
the ticket.
Attributes
n-12; TAGLLL
Tag Field: 0537
Subfields: none
Usage
messages:
Usage
Trip Leg Data)/1644
Values

PDS 0538—Endorsements/Restrictions
PDS 0538—Endorsements/Restrictions
Endorsements can be agency-added notations, and in some cases, mandatory
government required notations, such as VAT. Restrictions are limitations set
on a ticket based on the type of fare, such as nonrefundable or three-day
minimum stay. This information is contained in Endorsements/Restrictions
(PDS 0538).
Attributes
ans…20; TAGLLLVAR
Tag Field: 0537

Subfields: none
Justification: left
Usage
messages:
Usage
Trip Leg Data)/1644
Values

PDS 0539—Total Amount Charged on Card

Total Amount Charged on Card (PDS 0539) contains the total amount of the
room charges, charged to this account.
Attributes
ans-14; TAGLLL
Tag Field: 0539

Subfields: 3
Usage
messages:
Usage
s1 Total Amount Charged on Card Amount O • C
s2 Total Amount Charged on Card Exponent O • C
s3 Total Amount Charged on Card Sign O • C

Subfields

1 1–12 Total Amount Charged on Card n-12 Right
Amount
2 13 Total Amount Charged on Card n-1 n/a
Exponent
3 14 Total Amount Charged on Card Sign a-1 n/a
Subfield 1: Total Amount Charged on Card Amount

If PDS 0539 is present, subfield 1 must be numeric and contain the amount
charged on this account, and may be all zeros.
Subfield 2: Total Amount Charged on Card Exponent

If PDS 0539 is present, subfield 2 must be numeric and contain a value of 0–5.
Subfield 3: Total Amount Charged on Card Sign

Value Description
D Total amount charged on this account is a debit
C Total amount charged on this account is a credit
Values
PDS 0539 Total Amount Charged on Card must be a fixed length of 14.

PDS 0540—Room Service Charges

Room Service Charges (PDS 0540) contains the amount of the room service
charges.
Attributes
ans-14; TAGLLL
Tag Field: 0540

Subfields: 3
Usage
messages:
Usage
s1 Room Services Charges Amount O • C
s2 Room Service Charges Exponent O • C
s3 Room Service Charges Sign O • C

Subfields

1 1–12 Room Service Charges Amount n-12 Right
2 13 Room Service Charges Exponent n-1 n/a
3 14 Room Service Charges Sign a-1 n/a
Subfield 1: Room Services Charges Amount

If PDS 0540 is present, subfield 1 must be numeric and contain the amount of
the room service charges, and may be all zeros.
Subfield 2: Room Service Charges Exponent

Subfield 3: Room Services Charges Sign

Value Description
D Room service charges amount is a debit
C Room service charges amount is a credit
Values
PDS 0540 Room Service Charges must be a fixed length of 14.

PDS 0541—Lounge/Bar Charges

Lounge/Bar Charges (PDS 0541) contains the amount of the Lounge or Bar
charges.
Attributes
ans-14; TAGLLL
Tag Field: 0541

Subfields: 3
Usage
messages:
Usage
s1 Lounge/Bar Charges Amount O • C
s2 Lounge/Bar Charges Exponent O • C
s3 Lounge/Bar Charges Sign O • C

Subfields

1 1–12 Lounge/Bar Charges Amount n-12 Right
2 13 Lounge/Bar Charges Exponent n-1 n/a
3 14 Lounge/Bar Charges Sign a-1 n/a
Subfield 1: Lounge/Bar Charges Amount

the Lounge or Bar charges, and may be all zeros.
Subfield 2: Lounge/Bar Charges Exponent

Subfield 3: Lounge/Bar Charges Sign

Value Description
D Lounge/Bar charges amount is a debit
C Lounge/Bar charges amount is a credit
Values
PDS 0541 Lounge/Bar Charges must be a fixed length of 14.

PDS 0542—Transportation Charges

Transportation Charges (PDS 0542) contains the amount of the transportation
charges.
Attributes
ans-14; TAGLLL
Tag Field: 0542

Subfields: 3
Usage
messages:
Usage
s1 Transportation Charges Amount O • C
s2 Transportation Charges Exponent O • C
s3 Transportation Charges Sign O • C

Subfields

1 1–12 Transportation Charges Amount n-12 Right
2 13 Transportation Charges Exponent n-1 n/a
3 14 Transportation Charges Sign a-1 n/a
Subfield 1: Transportation Charges Amount

the transportation charges, and may be all zeros.
Subfield 2: Transportation Charges Exponent

Subfield 3: Transportation Charges Sign

Value Description
D Transportation charges amount is a debit
C Transportation charges amount is a credit
Values
PDS 0542 Transportation Charges must be a fixed length of 14.

PDS 0543—Gratuity Charges

Gratuity Charges (PDS 0543) contains the amount of the gratuity charges.
Attributes
ans-14; TAGLLL
Tag Field: 0543

Subfields: 3
Usage
messages:
Usage
s1 Gratuity Charges Amount O • C
s2 Gratuity Charges Exponent O • C
s3 Gratuity Charges Sign O • C
Subfields

1 1–12 Gratuity Charges Amount n-12 Right
2 13 Gratuity Charges Exponent n-1 n/a
3 14 Gratuity Charges Sign a-1 n/a

Subfield 1: Gratuity Charges Amount

If PDS 0543 is present, subfield 1 must be numeric and may be all zeros.
Subfield 2: Gratuity Charges Exponent

Subfield 3: Gratuity Charges Sign

Value Description
D Gratuity charges amount is a debit
C Gratuity charges amount is a credit
Values
PDS 0543 Gratuity Charges must be a fixed length of 14.

PDS 0544—Rental Agreement Number
PDS 0544—Rental Agreement Number

Rental Agreement Number (PDS 0544) contains the original vehicle rental
agreement invoice number.
Attributes
ans-9; TAGLLL
Tag Field: 0544
Subfields: None
Justification: Left
Usage
messages:
Usage
This PDS is required if the associated First Presentment/1240 contains a vehicle

rental card acceptor business code (MCC) and is submitted for one of the
following incentive interchange rate programs:
IRD Description
69 U.S. region Corporate T&E Rate II
89 U.S. region Corporate T&E Rate III
97 U.S. region Travel Industries Premier Service
Values
If the actual rental agreement number contains more than nine digits, members
should populate PDS 0544 with the agreement number’s rightmost nine digits.

PDS 0545—Renter Name

Renter Name (PDS 0545) is the name of the individual making the vehicle
rental agreement.
Attributes
ans…40; TAGLLLVAR
Tag Field: 0545
Subfields: None
Justification: Left
Usage
messages:
Usage

IRD Description
96 U.S. region World MasterCard T&E

Values
PDS 0545 Renter Name must be a minimum length of 1 and a maximum length
of 040.

PDS 0546—Rental Return City

Rental Return City (PDS 0546) is the city where the vehicle was returned to the
rental agency.
Attributes
ans…25; TAGLLLVAR
Tag Field: 0546
Subfields: none
Justification: left
Usage
messages:
Usage

IRD Description

Values
PDS 0546 Rental Return City must be a minimum length of 1 and a maximum
length of 025.

PDS 0547—Rental Return State/Province

Rental Return State/Province (PDS 0547) is the state or province where the
vehicle was returned to the rental agency.
Attributes
ans-3; TAGLLL
Tag Field: 0547
Subfields: none
Justification: left
Usage
messages:
Usage

IRD Description

Values
high-values, all spaces or all zeros. It must contain a valid U.S. state code
when Rental Return Country (PDS 0548) contains USA.
If the rental return occurs in a U.S. territory (Guam, Puerto Rico, or Virgin
Islands), members should provide the three-position country code (GUM, PRI,
or VIR) in both PDS 0547 and PDS 0548.
If rental return occurs outside the U.S. region, this field is not edited.

PDS 0548—Rental Return Country

Rental Return Country (PDS 0548) is the country where the vehicle was
returned to the rental agency.
Attributes
ans-3; TAGLLL
Tag Field: 0548
Subfields: none
Justification: left
Usage
messages:
Usage

IRD Description

Values
If present, PDS 0548 must be left justified and contain a valid alphabetic ISO
country code. It cannot contain all spaces.
If the rental return occurs in a U.S. territory (Guam, Puerto Rico, or Virgin

PDS 0549—Rental Return Location ID
PDS 0549—Rental Return Location ID

Rental Return Location ID (PDS 0549) contains the agency code, phone
number, or address abbreviation used to identify the vehicle rental return
location.
Attributes
ans-10; TAGLLL
Tag Field: 0549

Subfields: none
Justification: left
Usage
messages:
Usage

IRD Description
97 Travel Industries Premier Services
Values

PDS 0550—Rental Return Date
PDS 0550—Rental Return Date

Rental Return Date (PDS 0550) indicates the date when the vehicle was
returned to the rental agency.
Attributes
n-6; TAGLLL
Tag Field: 0550
Subfields: none
Justification: n/a
Usage
messages:
Usage

IRD Description
Values

PDS 0551—Rental Check-Out Date
PDS 0551—Rental Check-Out Date

Rental Check-Out Date (PDS 0551) is the date when the vehicle was originally
rented.
Attributes
n-6; TAGLLL
Tag Field: 0551
Subfields: none
Justification: n/a
Usage
messages:
Usage

IRD Description
Values

PDS 0552—Customer Service Toll-Free (800) Number

Customer Service Toll-Free (800) Number (PDS 0552) contains the customer
service phone number used to resolve cardholder questions and disputes.
Attributes
ans-17; TAGLLL
Tag Field: 0552
Subfields: none
Justification: left
Usage
messages:
Usage
This PDS is required if the associated First Presentment/1240 contains a

lodging card acceptor business code (MCC) and is submitted for the U.S.
region Travel Industries Premier Service (97) incentive interchange rate
program.


rental MCC and is submitted for one of the following U.S. region incentive
interchange rate programs:
IRD Description
Either this PDS or Property Phone Number (PDS 0577) is required if the
associated First Presentment/1240 contains a lodging MCC and is submitted for
one of the following incentive interchange rate programs:
IRD Description
For transactions acquired in the U.S. or Canada region, Customer Service Toll-
Free (800) Number (PDS 0552), if present must contain a 10-position phone
number, left justified with trailing spaces. The first three positions must be
numeric.
Values
If present, PDS 0552 cannot contain all zeros, all spaces, all low-values, or all
high-values.

PDS 0553—Rental Rate

Rental Rate (PDS 0553) contains the rental rate charged for the vehicle and
indicates whether it is a daily, weekly, or monthly rate.
Attributes
ans-13; TAGLLL
Tag Field: 0553
Subfields: 2
Usage
messages:
Usage
s1 Rental Rate Indicator O • C
s2 Rental Rate O • C

Subfields

1 1 Rental Rate Indicator as-1 n/a
2 2–13 Rental Rate n-12 right
Subfield 1: Rental Rate Indicator

If PDS 0553 is present, subfield 1 must contain one of the following values:
Value Description
D Daily rate.
W Weekly rate.
M Monthly rate.
space Unknown or unreported.
Subfield 2: Rental Rate

If PDS 0553 is present, subfield 2 must be numeric and may contain all zeros.

PDS 0554—Conference Room Charges

Conference Room Charges (PDS 0554) contains the amount of the charges
associated to conference room use.
Attributes
ans-14; TAGLLL
Tag Field: 0554

Subfields: 3
Usage
messages:
Usage
s1 Conference Room Charges Amount O • C
s2 Conference Room Charges Exponent O • C
s3 Conference Room Charges Sign O • C

Subfields

1 1–12 Conference Room Charges Amount n-12 Right
2 13 Conference Room Charges Exponent n-1 n/a
3 14 Conference Room Charges Sign a1 n/a
Subfield 1: Conference Room Charges Amount

If PDS 0554 is present, subfield 1 must be numeric and may be all zeros.
Subfield 2: Conference Room Charges Exponent

Subfield 3: Conference Room Charges Sign

Value Description
D Conference room charges amount is a debit
C Conference room charges amount is a credit
Values
PDS 0554 Conference Room Charges must be a fixed length of 14.

PDS 0555—Rate Per Mile (or Per Kilometer)
PDS 0555—Rate Per Mile (or Per Kilometer)

Rate Per Mile (or Per Kilometer) (PDS 0555) contains the rate charged for each
mile or kilometer. It may be a daily, weekly, or monthly rate.
Attributes
n-12; TAGLLL
Tag Field: 0555
Subfields: none
Usage
messages:
Usage
Values
If present, PDS 0555 must be numeric and may contain all zeros.

PDS 0556—Total Miles (or Kilometers)
PDS 0556—Total Miles (or Kilometers)

Total Miles (or Kilometers) (PDS 0556) contains the total miles or kilometers
that the customer drove.
Attributes
n-4; TAGLLL
Tag Field: 0556
Subfields: none
Usage
messages:
Usage
Values
If present, PDS 0556 must be numeric and cannot contain all zeros.

PDS 0557—Maximum Free Miles (or Kilometers)
PDS 0557—Maximum Free Miles (or Kilometers)

Maximum Free Miles (or Kilometers) (PDS 0557) contains the free miles or
kilometers allowed to a customer for the duration of the vehicle rental
agreement.
Attributes
n-4; TAGLLL
Tag Field: 0557

Subfields: none
Usage
messages:
Usage
Values
If present, PDS 0557 must be numeric and may contain all zeros.

PDS 0558—Miles/Kilometers Indicator
PDS 0558—Miles/Kilometers Indicator

Miles/Kilometers Indicator (PDS 0558) shows whether the “miles” fields are
expressed in miles or kilometers.
Attributes
ans-1; TAGLLL
Tag Field: 0558
Subfields: none
Justification: n/a
Usage
messages:
Usage
Values
If present, PDS 0558 must contain one of the following values:
Value Description
K Kilometers.
M Miles.
space Unknown or unreported.

PDS 0559—Vehicle Insurance

Vehicle Insurance (PDS 0559) contains an indicator of whether the customer
purchased insurance and the insurance amount.
Attributes
ans-13; TAGLLL
Tag Field: 0559
Subfields: 2
Usage
messages:
Usage
s1 Insurance Indicator O • C
s2 Insurance Charges O • C
Subfields

1 1 Insurance Indicator as-1 n/a
2 2–13 Insurance Charges ans-12 right

Subfield 1: Insurance Indicator

Value Description
Y Yes (insurance was purchased).
N No (insurance was not purchased).
spaces Unknown or unreported.
Subfield 2: Insurance Charges

If PDS 0559, subfield 1 is Y, then PDS 0559, subfield 2 cannot contain all
spaces or all zeros.

PDS 0560—Audio Visual Charges

Audio Visual Charges (PDS 0560) contains the amount of the audio visual
equipment charges.
Attributes
ans-14; TAGLLL
Tag Field: 0560

Subfields: 3
Usage
messages:
Usage
s1 Audio Visual Charges Amount O • C
s2 Audio Visual Charges Exponent O • C
s3 Audio Visual Charges Sign O • C

Subfields

1 1–12 Audio Visual Charges Amount n-12 Right
2 13 Audio Visual Charges Exponent n-1 n/a
3 14 Audio Visual Charges Sign a-1 n/a
Subfield 1: Audio Visual Charges Amount

the audio visual equipment charges, and may be all zeros.
Subfield 2: Audio Visual Charges Exponent

Subfield 3: Audio Visual Charges Sign

Value Description
D Audio visual charges amount is a debit
C Audio visual charges amount is a credit
Values
PDS 0560 Audio Visual Charges must be a fixed length of 14.

PDS 0561—Adjusted Amount

Adjusted Amount (PDS 0561) indicates whether any miscellaneous charges
were incurred after the vehicle was returned. PDS 0561 should only be
provided when additional charges have been identified.
Attributes
ans-13; TAGLLL
Tag Field: 0561
Subfields: 2
Usage
messages:
Usage
s1 Adjusted Amount Indicator O • C
s2 Adjusted Amount O • C

Subfields

1 1 Adjusted Amount Indicator as-1 n/a
2 2–13 Adjusted Amount n-12 right
Subfield 1: Adjusted Amount Indicator

Value Description
A Drop-off charges.
B Delivery charges.
C Parking expenses.
D Extra hours.
E Violations.
X Multiple charges of the above type(s).
space Unknown or no additional charges.
Subfield 2: Adjusted Amount

If subfield 1 does not contain a space, then subfield 2 must be numeric and
greater than zero.

PDS 0562—Banquet Charges

Banquet Charges (PDS 0562) contains the amount of the banquet charges.
Attributes
ans-14; TAGLLL
Tag Field: 0562

Subfields: 3
Usage
messages:
Usage
s1 Banquet Charges Amount O • C
s2 Banquet Charges Exponent O • C
s3 Banquet Charges Sign O • C
Subfields

1 1–12 Banquet Charges Amount n-12 Right
2 13 Banquet Charges Exponent n-1 n/a
3 14 Banquet Charges Sign a-1 n/a

Subfield 1: Banquet Charges Amount

the banquet charges, and may be all zeros.
Subfield 2: Banquet Charges Exponent

Subfield 3: Banquet Charges Sign

Value Description
D Banquet charges amount is a debit
C Banquet charges amount is a credit
Values
PDS 0562 Banquet Charges must be a fixed length of 14.

PDS 0563—Program Code

Program Code (PDS 0563) identifies special circumstances, such as “frequent
renter.”
Attributes
ans-2; TAGLLL
Tag Field: 0563
Subfields: none
Justification: left
Usage
messages:
Usage
Values
If present, PDS 0563 Program Code must be left justified and cannot be all

PDS 0564—Rental Location City
PDS 0564—Rental Location City

Rental Location City (PDS 0564) indicates where the vehicle was rented.
Attributes
ans…25; TAGLLLVAR
Tag Field: 0564

Subfields: none
Justification: left
Usage
messages:
Usage

rental card acceptor business code (MCC) and is submitted for the U.S. region
Corporate T&E Rate III (IRD 89) incentive interchange rate program.
Values
PDS 0564, Rental Location City must be a minimum length of 001 and a
maximum length of 025.
If present, PDS 0564 must be left justified and cannot be all low-values, all

PDS 0565—Rental Location State/Province
PDS 0565—Rental Location State/Province

Rental Location State/Province (PDS 0565) indicates the state or province
where the vehicle was rented.
Attributes
ans-3; TAGLLL
Tag Field: 0565
Subfields: none
Justification: left
Usage
messages:
Usage

Values
high-values, all spaces, or all zeros. It must contain a valid U.S. state code if
Rental Location Country (PDS 0566) contains USA.
If the rental location occurs in a U.S. territory (Guam, Puerto Rico, or Virgin

PDS 0566—Rental Location Country
PDS 0566—Rental Location Country

Rental Location Country (PDS 0566) indicates the country where the vehicle
was rented.
Attributes
as-3; TAGLLL
Tag Field: 0566
Subfields: none
Justification: left
Usage
messages:
Usage

Values
If present, PDS 0566 must be left justified and be a valid alphabetic ISO
country code. It cannot contain all spaces.
If the rental location occurs in a U.S. territory (Guam, Puerto Rico, or Virgin

PDS 0567—Rental Location ID
PDS 0567—Rental Location ID

Rental Location ID (PDS 0567) contains the agency code, phone number, or
address abbreviation used to identify the rental location.
Attributes
ans-10; TAGLLL
Tag Field: 0567
Subfields: none
Justification: left
Usage
messages:
Usage
Values

PDS 0568—Rental Class ID

Rental Class ID (PDS 0568) contains the classification, such as midsize or
luxury, of the vehicle rented.
Attributes
ans-4; TAGLLL
Tag Field: 0568
Subfields: none
Justification: left
Usage
messages:
Usage


Values
If present, PDS 0568 must be left justified and cannot contain all low-values,
high-values, all spaces, or all zeros. Otherwise, the clearing system does not
edit PDS 0568. Suggested values are in the following table:
Value Description
0001 Mini
0002 Subcompact
0003 Economy
0004 Compact
0005 Midsize
0006 Intermediate
0007 Standard
0008 Full size
0009 Luxury
0010 Premium
0011 Minivan
0012 12 passenger van
0013 Moving van
0014 15 passenger van
0015 Cargo van
0016 12 foot truck
0017 20 foot truck
0018 24 foot truck
0019 26 foot truck
0020 Moped
0021 Stretch
0022 Regular
0023 Unique
0024 Exotic
0025 Small/medium truck

Value Description
0026 Large truck
0027 Small SUV
0028 Medium SUV
0029 Large SUV
0030 Exotic SUV
9999 Miscellaneous

PDS 0569—Internet Access Charges

Internet Access Charges (PDS 0569) contains the amount of the internet access
charges.
Attributes
ans-14; TAGLLL
Tag Field: 0569

Subfields: 3
Usage
messages:
Usage
s1 Internet Access Charges for Access Amount O • C
s2 Internet Access Charges for Internet Access Exponent O • C
s3 Internet Access Charges for Internet Access Sign O • C

Subfields

1 1–12 Internet Access Charges Amount n-12 Right
2 13 Internet Access Charges Exponent n-1 n/a
3 14 Internet Access Charges Sign a-1 n/a
Subfield 1: Internet Access Charges Amount

the internet access charges, and may be all zeros.
Subfield 2: Internet Access Charges Exponent

Subfield 3: Internet Access Charges Sign

Value Description
D Internet Access Charges amount is a debit
C Internet Access Charges amount is a credit
Values
PDS 0569 Internal access charges must be a fixed length of 14.

PDS 0570—Early Departure Charges

Early Departure Charges (PDS 0570) contains the amount charged due to early
departure.
Attributes
ans-14; TAGLLL
Tag Field: 0570

Subfields: 3
Usage
messages:
Usage
s1 Early Departure Charges Amount O • C
s2 Early Departure Charges Exponent O • C
s3 Early Departure Charges Sign O • C

Subfields

1 1–12 Early Departure Charges Amount n-12 Right
2 13 Early Departure Charges Exponent n-1 n/a
3 14 Early Departure Charges Sign a-1 n/a
Subfield 1: Early Departure Charges Amount

the early departure charges, and may be all zeros.
Subfield 2: Early Departure Charges Exponent

Subfield 3: Early Departure Charges Sign

Value Description
D Early departure charges amount is a debit
C Early departure charges amount is a credit
Values
PDS 0570 Early departure charges must be a fixed length of 14.

PDS 0571—Guest Name
PDS 0571—Guest Name

Guest Name (PDS 0571) contains the name of the lodging patron.
Attributes
ans…40; TAGLLLVAR
Tag Field: 0571

Length Field: 3 positions, value = 001-040
Data Field: variable length 001-040 positions
Subfields: none
Justification: left
Usage
messages:
Usage
Values
PDS 0571 must be a minimum length of 001 and a maximum length of 040. If
present, PDS 0571 must be left justified and cannot contain all low-values,

PDS 0572—Guest Number
PDS 0572—Guest Number

Guest Number (PDS 0572) contains the number assigned to the lodging
patron.
Attributes
ans-25; TAGLLL
Tag Field: 0572

Subfields: none
Justification: left
Usage
messages:
Usage
Values
PDS 0572 must be a fixed length of 025. If present, PDS 0572 must be left
justified and cannot contain all low-values, high-values, all spaces, or all zeros.

PDS 0573—Invoice Number
PDS 0573—Invoice Number

Invoice Number (PDS 0573) contains the number of the electronic invoice.
Attributes
ans…25; TAGLLLVAR
Tag Field: 0573

Subfields: none
Justification: left
Usage
messages:
Usage
Financial Detail Addendum (Electronic Invoice-Transaction O • C
Data)/1644
Values
PDS 0573 must be a minimum length of 001 and a maximum length of 025. If
present, PDS 0573 must be left justified and cannot contain all low-values,

PDS 0574—Arrival Date
PDS 0574—Arrival Date

Arrival Date (PDS 0574) contains the cardholder check-in date.
Attributes
n-6; TAGLLL
Tag Field: 0574

Subfields: none
Justification: n/a
Usage
messages:
Usage

lodging card acceptor business code (MCC) and is submitted for one of the
IRD Description
Values

PDS 0575—Departure Date
PDS 0575—Departure Date

Departure Date (PDS 0575) contains the cardholder check-out date.
Attributes
n-6; TAGLLL
Tag Field: 0575

Subfields: none
Justification: n/a
Usage
messages:
Usage

IRD Description
Values

PDS 0576—Folio Number

Folio Number (PDS 0576) contains the card acceptor’s internal invoice or
billing ID reference number.
Attributes
ans…25; TAGLLLVAR
Tag Field: 0576
Subfields: none
Justification: left
Usage
messages:
Usage

IRD Description

Values
PDS 0576, Folio Number must be a minimum length of 001 and a maximum
length of 025.

PDS 0577—Property Phone Number

Property Phone Number (PDS 0577) identifies specific lodging property
location by its local phone number.
Attributes
ans-17; TAGLLL
Tag Field: 0577
Subfields: none
Justification: left
Usage
messages:
Usage

region Travel Industries Premier Service (97) incentive interchange rate
program.
Either this PDS or Customer Service Toll-Free (800) Number (PDS 0552) is
required if the associated First Presentment/1240 contains a lodging MCC and
is submitted for one of the following incentive interchange rate programs:
IRD Description

For transactions acquired in the U.S. or Canada region, Property Phone

Number (PDS 0577 ), if present, must contain a 10-position phone number,
left justified with trailing spaces. The first three positions must be numeric.
Values
If present, PDS 0577 cannot contain all low-values, all high-values, all zeros or
all spaces.

PDS 0578—Billing Adjustment

Billing Adjustment (PDS 0578) indicates whether any additional charges were
incurred after the cardholder’s departure.
Attributes
ans-15; TAGLLL
Tag Field: 0578
Subfields: 4
Usage
messages:
Usage
s1 Billing Adjustment Indicator O • C
s2 Billing Adjusted Amount O • C
s3 Billing Adjusted Exponent O • C
s4 Billing Adjusted Sign O • C

Subfields

1 1 Billing Adjustment Indicator as-1 n/a
2 2–13 Billing Adjustment Amount n-12 Right
3 14 Billing Adjustment Exponent n–1 n/a
4 15 Billing Adjustment Sign a–1 n/a
Subfield 1: Billing Adjustment Indicator

If PDS 0578 is present, subfield 1 should contain one of the following values:
Value Description
Y Yes (additional charges were added).
N No (no additional charges were added).
space No additional charges or unknown.
Subfield 2: Billing Adjustment Amount

This subfield contains the total amount of the charges added after the
departure. If subfield 1 contains a Y, then subfield 2 must be numeric and
greater than zero.
Subfield 3: Billing Adjustment Exponent

Subfield 3 must be numeric and contain a value of 0–5.
Subfield 4: Billing Adjustment Sign

Subfield 4 must contain a value of D or C.
Value Description
D Billing Adjustment amount is a debit
C Billing Adjustment amount is a credit

PDS 0579—Invoice Date
PDS 0579—Invoice Date

Invoice Date (PDS 0579) contains the date of the electronic invoice.
Attributes
n-6; TAGLLL
Tag Field: 0579

Subfields: none
Justification: n/a
Usage
messages:
Usage
Data)/1644
Values
PDS 0579 Invoice Date must be numeric and must be a fixed length of 006. If
present, PDS 0579 must contain a valid date in the format YYMMDD.

PDS 0580—Room Rate

Room Rate (PDS 0580) contains the daily room charges exclusive of taxes and
fees.
Attributes
n-13; TAGLLL
Tag Field: 0580
Subfields: 2
Justification: See “Subfields”
Usage
messages:
Usage
s1 Room Rate Amount C • C
s2 Room Rate Exponent C • C

region Corporate T&E Rate III (IRD 89) incentive interchange rate program.

Subfields

1 1–12 Room Rate Amount n–12 right
2 13 Room Rate Exponent n-1 n/a
Subfield 1: Room Rate Amount

This subfield contains the daily room charges exclusive of taxes and fees. If
PDS 0580 is present, subfield 1 must be numeric.
Subfield 2: Room Rate Exponent

Subfield 2 must be numeric and contain a value of 0-5.
Values
If various room rates apply for the same stay (folio), the room rate for the
majority of number of days should be listed.
If present, PDS 0580 must be a fixed length of 13 and may contain all zeros.

PDS 0581—Total Room Tax

Total Room Tax (PDS 0581) contains tax amount information such as the daily
room tax, occupancy tax, energy tax, and tourist tax amounts.
Attributes
ans-14; TAGLLL
Tag Field: 0581

Subfields: 3
Usage
messages:
Usage
s1 Total Room Tax Amount C • C
s2 Total Room Tax Exponent C • C
s3 Total Room Tax Sign C • C


Subfields

1 1–12 Total Room Tax Amount n–12 right
2 13 Total Room Tax Exponent n-1 n/a
3 14 Total Room Tax Sign a–1 n/a
Subfield 1: Total Room Tax Amount

This subfield contains the total amount of the charges for Total Room Tax. If
PDS 0581 is present, subfield 1 must be numeric.
Subfield 2: Total Room Tax Exponent

Subfield 3: Total Room Tax Sign

Value Description
D Total room tax amount is a debit
C Total room tax amount is a credit
Values
If present, PDS 0581 must be fixed length of 14.


Program Code (PDS 0582) indicates special circumstances such as “no show”
situations.
Attributes
ans-2; TAGLLL
Tag Field: 0582
Subfields: none
Justification: left
Usage
messages:
Usage
Values
high values, all spaces or all zeros.

PDS 0583—Phone Charges

Phone Charges (PDS 0583) contains the total amount of charges for all phone
calls.
Attributes
ans-14; TAGLLL
Tag Field: 0583
Subfields: 3
Usage
messages:
Usage
s1 Phone Charges Amount O • C
s2 Phone Charges Exponent O • C
s3 Phone Charges Sign O • C

Subfields

1 1–12 Phone Charges Amount n–12 right
2 13 Phone Charges Exponent n-1 n/a
3 14 Phone Charges Sign a–1 n/a
Subfield 1: Phone Charges Amount

This subfield contains the total amount of charges for all phone calls. If
PDS 0583 is present, subfield 1 must be numeric
Subfield 2: Phone Charges Exponent

Subfield 3: Phone Charges Sign

Value Description
D Phone charges amount is a debit
C Phone charges amount is a credit
Values
If present, PDS 0583 must be a fixed length of 14.

PDS 0584—Restaurant Charges

Restaurant Charges (PDS 0584) contains the total amount of all restaurant
charges.
Attributes
ans-14; TAGLLL
Tag Field: 0584
Subfields: 3
Justification: lefts “Subfields”
Usage
messages:
Usage
s1 Restaurant Charges Amount O • C
s2 Restaurant Charges Exponent O • C
s3 Restaurant Charges Sign O • C
Subfields

1 1–12 Restaurant Charges Amount n–12 right
2 13 Restaurant Charges Exponent n-1 n/a
3 14 Restaurant Charges Sign a–1 n/a

Subfield 1: Restaurant Charges Amount

If PDS 0584 is present, subfield 1 must be numeric and contain the restaurant
charges amount.
Subfield 2: Restaurant Charges Exponent

Subfield 3: Restaurant Charges Sign

Value Description
D Restaurant charges amount is a debit
C Restaurant charges amount is a credit
Values

PDS 0585—Mini-Bar Charges

Mini-Bar Charges (PDS 0585) contains the total amount of in-room “mini-bar”
service charges.
Attributes
ans-14; TAGLLL
Tag Field: 0585
Subfields: 3
Usage
messages:
Usage
s1 Mini-Bar Charges Amount O • C
s2 Mini-Bar Charges Exponent O • C
s3 Mini-Bar Charges Sign O • C
Subfields

1 1–12 Mini-Bar Charges Amount n–12 right
2 13 Mini-Bar Charges Exponent n-1 n/a
3 14 Mini-Bar Charges Sign a–1 n/a

Subfield 1: Mini-Bar Charges Amount

If PDS 0585 is present, subfield 1 must be numeric and contain the mini-bar
charges amount.
Subfield 2: Mini-Bar Charges Exponent

Subfield 3: Mini-Bar Charges Sign

Value Description
D Mini Bar charges amount is a debit
C Mini Bar charges amount is a credit
Values

PDS 0586—Gift Shop Charges

Gift Shop Charges (PDS 0586) contains the total amount of all gift shop and
specialty shop charges.
Attributes
ans-14; TAGLLL
Tag Field: 0586
Subfields: 3
Usage
messages:
Usage
s1 Gift Shop Charges Amount O • C
s2 Gift Shop Charges Exponent O • C
s3 Gift Shop Charges Sign O • C
Subfields

1 1–12 Gift Shop Charges Amount n–12 right
2 13 Gift Shop Charges Exponent n-1 n/a
3 14 Gift Shop Charges Sign a–1 n/a

Subfield 1: Gift Shop Charges Amount

This subfield contains the total amount of all gift shop and specialty shop
charges. If PDS 0586 is present, subfield 1 must be numeric..
Subfield 2: Gift Shop Charges Exponent

Subfield 3: Gift Shop Charges Sign

Value Description
D Gift Shop charges amount is a debit
C Gift Shop charges amount is a credit
Values

PDS 0587—Laundry and Dry Cleaning Charges

Laundry and Dry Cleaning Charges (PDS 0587) contains the total amount of
cleaning charges.
Attributes
ans-14; TAGLLL
Tag Field: 0587
Subfields: 3
Usage
messages:
Usage
s1 Laundry and Dry Cleaning Charges Amount O • C
s2 Laundry and Dry Cleaning Charges Exponent O • C
s3 Laundry and Dry Cleaning Charges Sign O • C

Subfields

1 1–12 Laundry and Dry Cleaning Charges n–12 right
Amount
2 13 Laundry and Dry Cleaning Charges n-1 n/a
Exponent
3 14 Laundry and Dry Cleaning Charges a–1 n/a
Sign
Subfield 1: Laundry and Dry Cleaning Charges Amount

This subfield contains the total amount of all laundry and dry cleaning charges.
If PDS 0587 is present, subfield 1 must be numeric.
Subfield 2: Laundry and Dry Cleaning Charges Exponent

Subfield 3: Laundry and Dry Cleaning Charges Sign

Value Description
D Laundry and Dry Cleaning charges amount is a debit
C Laundry and Dry Cleaning charges amount is a credit
Values

PDS 0588—Other Services

Other Services (PDS 0588) contains the total amount of “other” service charges,
not elsewhere classified.
Attributes
ans-102; TAGLLLVAR
Tag Field: 0588

Data Field: fixed length 17–102 positions
Subfields: 4
Occurrences 1–6
Usage
messages:
Usage
s1 Other Services Code O • C
s2 Other Services Amount O • C
s3 Other Services Exponent O • C
s4 Other Services Sign O • C
PDS 0588 Other Services must be a minimum length of 017 and a maximum
length of 102, and must be divisible by a minimum occurrence length of 017.

Subfields

1 1–3 Other Services Code ans-3 left
2 4–15 Other Services Amount n-12 right
3 16 Other Services Exponent n–1 n/a
4 17 Other Services Sign a–1 n/a
Subfield 1: Other Services Code

The code indicating the type of services provided. If present, PDS 0588,
subfield 1 Other Services Code must be left justified and cannot be all low-
Subfield 2: Other Services Amount

PDS 0588, subfield 2 Other Services Amount must be numeric.
Subfield 3: Other Services Exponent

If PDS 0588 is present, subfield 3 must be numeric and must contain a value of
0–5.
Subfield 4: Other Services Sign

If PDS 0588 is present, subfield 4 must contain a valid value of D or C.
Value Description
D Other Services charges amount is a debit
C Other Services charges amount is a credit

PDS 0589—Invoice Creation Date/Time

Invoice Creation Date/Time (PDS 0589) contains the date and time the
electronic invoice was created.
Attributes
n-12; TAGLLL
Tag Field: 0589

Subfields: two
Usage
messages:
Usage
Data)/1644
s1 Invoice Creation Date O • C
s2 Invoice Creation Time O • C
Subfields

1 1–6 Invoice Creation Date n-6 right
2 7–12 Invoice Creation Time n-6 right

Subfield 1: Invoice Creation Date

If PDS 0589 is present, subfield 1 must be numeric and must contain a valid
date in the format YYMMDD.
Subfield 2: Invoice Creation Time

If PDS 0589 is present, subfield 2 must be numeric and must contain a valid
time in the format HHMMSS.
Values
PDS 0589 Invoice Creation Date/Time must be a fixed length of 12.

PDS 0590—Party Identification

Party Identification (PDS 0590) contains a code that identifies the various
parties on an invoice.
Attributes
an-2; TAGLLL
Tag Field: 0590

Subfields: none
Justification: n/a
Usage
messages:
Usage
Financial Detail Addendum (Electronic Invoice-Party O • C
Information)/1644

Values
If present, PDS 0590 must be a fixed length of 02 and contain one of the
following values:
Value Description
BY Buyer, or company buying the goods or services (Corporate)
SU Supplier, or the provider of the goods or services (Merchant)
IV The party to whom the invoice is addressed
PE Payee, or the party that will receive payment
DP Delivery party, or the party that will receive the goods
SF Ship from party, or the company from which the goods or services will be
shipped

PDS 0591—Party Name

Party Name (PDS 0591) contains name of the party identified on the invoice.
Attributes
Tag Field: 0591

Data Field: variable length 120 positions
Subfields: one
Occurrences: 1–3
Justification: left
Usage
messages:
Usage
Information)/1644
s1 Party Name O • C
Subfields
This PDS contains from one to three occurrences of Party Name information.
Each occurrence requires 40 positions; the length of this PDS must be a
multiple of 40, with a maximum length of 120 positions.

1 1-40 Party Name ans-40 left

Subfield 1–Party Name

If present, PDS 0591, subfield 1 Party Name must be left justified and cannot
contain all low-values, high-values, spaces, or zeros.

PDS 0592—Party Address

Party Address (PDS 0592) contains address of the party identified on the
invoice.
Attributes
Tag Field: 0592

Subfields: one
Occurrences: 1–6
Justification: Left
Usage
messages:
Usage
Information)/1644
s1 Party Address Line O • C

Subfields
This PDS contains from 1-6 occurrences of Party Address information. Each
occurrence requires 40 positions; the length of this PDS must be a multiple of
40, with a maximum length of 240 positions.

1 1–40 Party Address Line ans-40 left
Subfield 1: Party Address Line

Values
PDS 0592, Party Address contains from 1-6 occurrences of Party Address
information. The PDS must be a minimum length of 040 and a maximum
length of 240 and must be divisible by minimum occurrence length of 040.

PDS 0593—Party Postal Information

Party Postal Information (PDS 0593) contains the city, state/province, country
code, and postal code of the party identified on the invoice.
Attributes
ans…46; TAGLLLVAR
Tag Field: 0593

Subfields: 4
Usage
messages:
Usage
Information)/1644
s1 City O • C
s2 State/Province Code O • C
s3 Country Code O • C
s4 Postal Code O • C

Subfields
PDS 0593 consists of four subfields as defined in the following table:

1 1–25 City ans-25 left
2 26–28 State/Province Code ans-3 left
3 29–31 Country Code ans-3 left
4 32–46 Postal Code ans-15 left
Subfield 1: City
When PDS 0593 is present, subfield 1 City is required to be present, must be
25 positions, and must contain the city of the party identified on the invoice.
This subfield must be left justified and cannot contain all low-values, all high-
Subfield 2: State/Province Code

This subfield contains the state or province code of the party identified on the
invoice. This subfield must be a fixed length of 003, and must be left justified.
It cannot contain all low-values, all high-values, all spaces, or all zeros.
Subfield 3: Country Code

This subfield contains the country code of the party identified on the invoice.
This subfield must be a fixed length of 003 and must be left justified. It cannot
contain all low-values, all high-values, all spaces, or all zeros.
Subfield 4: Postal Code

This subfield contains the postal code of the party identified on the invoice.
This subfield must be a fixed length of 015 and must be left justified. It cannot
Values
PDS 0593, Party Postal Information must be a minimum length of 025 and a

PDS 0594—Party Contact

Party Contact (PDS 0594) contains a contact descriptor and party information
for the party identified on the invoice.
Attributes
Tag Field: 0594

Subfields: two
Occurrences: 5
Usage
messages:
Usage
Information)/1644
s1 Party Contact Descriptor O • C
s2 Party Contact Information O • C

Subfields
PDS 0594 consists of two subfields as defined in the following table:

1 1 Party Contact Descriptor n-1 n/a
2 2–61 Party Contact Information ans-60 left
Subfield 1: Party Contact Descriptor

This subfield contains a code that identifies the type of party information being
provided. If present, this subfield must numeric and must be left justified. It
cannot contain all low-values, all high-values, all spaces, or all zeros, and must
contain one of the following values:
Value Description
1 Name
2 Title
3 Telephone
4 E-mail address
5 Function
Subfield 2: Party Contact Information

This subfield contains the contact information of the party. This subfield must
be left justified and cannot contain all low-values, all high-values, all spaces, or
all zeros.
Values
PDS 0594, Party Contact must be a minimum length of 061 and a maximum
length of 305 and must be divisible by minimum occurrence length of 061.

PDS 0595—Card Acceptor Type

Card Acceptor Type (PDS 0595) contains various classifications of business
ownership characteristics.
Attributes
ans-8; TAGLLL
Tag Field: 0595
Subfields: 8
Usage
messages:
Usage
Requirements)/1644
s1 Business Type C • C
s2 Business Owner Type C • C
s3 Business Certification Type C • C
s4 Business Racial/Ethnic Type C • C
s5 Business Type Provided Code C • C
s6 Business Owner Type Provided Code C • C
s7 Business Certification Type Provided Code C • C
s8 Business Racial/Ethnic Type Provided Code C • C

This PDS is required if the associated First Presentment/1240 is other than a

MasterCard Corporate Fleet Card® transaction at a fuel location and is
submitted for one of the following incentive interchange rate programs:
IRD Description
Subfield Layout
PDS 0595 consists of eight subfields as defined in the following table:

1 1 Business Type ans–1 n/a
2 2 Business Owner Type ans–1 n/a
3 3 Business Certification Type ans–1 n/a
4 4 Business Racial/Ethnic Type ans–1 n/a
5 5 Business Type Provided Code ans–1 n/a
6 6 Business Owner Type Provided Code ans–1 n/a
7 7 Business Certification Type Provided ans–1 n/a
Code
8 8 Business Racial/Ethnic Type ans–1 n/a
Provided Code

Subfield 1: Business Type

If PDS 0595 is present, subfield 1 contains a code to identify the specific
classification or type of business. PDS 0595 subfield 1 cannot contain all low-
values or all high-values. The following values should be used in this subfield:
Value Description
1 Corporation
2 Not known
3 Individual/Sole Proprietorship
4 Partnership
5 Association/Estate/Trust
6 Tax Exempt Organizations (501C)
7 International Organization
8 Limited Liability Company (LLC)
Subfield 2: Business Owner Type

Subfield 2 contains a code to identify specific characteristics about the business
owner. PDS 0595, subfield 2 cannot contain all low-values or all high-values.
Valid values are:
Value Description
1 No application classification
2 Female business owner
3 Physically handicapped female business owner
4 Physically handicapped male business owner
0 Unknown

Subfield 3: Business Certification Type

Subfield 3 contains a code to identify specific characteristics about the business
certification type, such as small business, disadvantaged or other certification
type. PDS 0595, subfield 3 cannot contain all low-values, or all high-values.
Valid values
Value Description
1 Not certified
2 Small Business Administration (SBA) certification small business
3 SBA certification as small disadvantaged business
4 Other government or agency-recognized certification (such as Minority
Supplier Development Council)
5 Self-certified small business
6 SBA certification as small and other government or agency-recognized
certification
7 SBA certification as small disadvantaged business and other government or
agency-recognized certification
8 Other government or agency-recognized certification and self-certified small
business
A SBA certification as 8(a)
B Self-certified small disadvantaged business (SDB)
C SBA certification as HUBZone
0 Unknown

Subfield 4: Business Racial/Ethnic Type

A code identifying the racial or ethnic type of the majority owner of the
business. PDS 0595, subfield 4 cannot contain all low-values or all high-
values. Valid values are:
Value Description
1 African American
2 Asian Pacific American
3 Subcontinent Asian American
4 Hispanic American
5 Native American Indian
6 Native Hawaiian
7 Native Alaskan
8 Caucasian
9 Other
0 Unknown
Subfield 5: Business Type Provided Code

Valid values for this subfield are:
Value Description
Y Business type provided
N Business type was not provided
R Card acceptor refused to provide business type.
Subfield 6: Business Owner Type Provided Code

Value Description
Y Business owner type provided
N Business owner type was not provided

Subfield 7: Business Certification Type Provided Code

Valid values for this subfield are:.
Value Description
Y Business certification type provided
N Business certification type was not provided
Subfield 8: Business Racial/Ethnic Type Provided Code

Value Description
Y Business racial/ethnic type provided
N Business racial/ethnic type was not provided
R Card acceptor refused to provide business racial/ethnic type.
Values

PDS 0596—Card Acceptor Tax ID

Card Acceptor Tax ID (PDS 0596) contains a U.S. federal tax ID number or
value added tax (VAT) ID.
Attributes
ans-21 TAGLLLVAR
Tag Field: 0596
Data Field: Fixed length 1–21 positions
Subfields: 2
Usage
messages:
Usage
Requirements)/1644
s1 Card Acceptor Tax ID C • C
s2 Card Acceptor Tax ID Provided Code C • C
This PDS is required if the associated First Presentment/1240 is other than a

MasterCard Corporate Fleet Card® transaction at a fuel location and is
submitted for one of the following incentive interchange rate programs:
IRD Description

Subfields

1 1–20 Card Acceptor Tax ID ans-20 n/a
2 21 Card Acceptor Tax ID Provided Code ans-1 right
Subfield 1—Card Acceptor Tax ID

PDS 0596, subfield 1 cannot contain a known invalid Tax ID.
For transactions acquired in the U.S. region, if present, subfield 1 must contain
nine numeric characters, and be left justified with trailing spaces. It cannot
contain all zeros or all spaces, or any known invalid tax ID value.
For transactions acquired outside the U.S. region, if present, subfield 1 cannot
contain all spaces if the associated First Presentment/1240 is submitted for the
International Corporate Purchasing Data Rate II (IRD 67) incentive interchange
rate program.
Subfield 2—Card Acceptor Tax ID Provided Code

Value Description
Y Card Acceptor Tax ID provided
N Card Acceptor Tax ID not provided
R Refused to provide Card Acceptor Tax ID
Values
If present, PDS 0596 must be fixed length of 21. The Card Acceptor Tax ID
cannot be on the GCMS defined list of invalid tax IDs, or contain a known
invalid value such as all low-values, all high-values, all spaces, all zeros, or all
nines.

PDS 0597—Total Tax Amount

Total Tax Amount (PDS 0597) contains the total amount of sales tax or value
added tax (VAT) on the total purchase amount.
Attributes
ans-14; TAGLLL
Tag Field: 0597
Subfields: 3
Usage
messages:
Usage
Data)/1644

Usage
Financial Detail Addendum (Telephony Billing—Summary)/1644 O • C
Financial Detail Addendum (Telephony Billing—Detail)/1644 O • C
Requirements)/1644
s1 Total Tax Amount C • C
s2 Total Tax Exponent C • C
s3 Total Tax Sign C • C
Financial Detail Addendum (Corporate Card Fleet Transaction O • C
Information)/1644

Usage
This PDS is required in a Corporate Card Common Data Requirements message

if the associated First Presentment/1240 is other than a MasterCard Corporate
Fleet Card® transaction at a fuel location and is submitted for one of the
IRD Description
Indicators in PDS 0682, subfield 1, PDS 0683, subfield 1, PDS 0684,

subfield 1, PDS 0751, subfield 1, PDS 0752, subfield 1, and PDS 0753,
subfield 1, are used to reflect the collection of the individual tax amounts that
are summarized in PDS 0597 Tax Amount.
PDS 0682, PDS 0683, PDS 0684, PDS 0751, PDS 0752, and PDS 0753 are used
to categorize the individual tax amounts such as state, local, and municipal
taxes that are summarized in PDS 0597 Tax Amount.

Subfields

1 1–12 Total Tax Amount n–12 right
2 13 Total Tax Exponent n-1 n/a
3 14 Total Tax Sign a–1 n/a
Subfield 1: Total Tax Amount

If PDS 0597 is present, subfield 1 must be numeric and contain the tax amount
and may contain all zeros.
Subfield 2: Total Tax Exponent

Subfield 3: Total Tax Sign

Value Description
D Total tax amount is a debit
C Total tax amount is a credit
Values

PDS 0598—Total Tax Collected Indicator

Total Tax Collected Indicator (PDS 0598) reflects total sales tax capture and
reporting information such as whether sales tax was included in the purchase
amount, or if goods and services were not taxable.
Attributes
ans-1; TAGLLL
Tag Field: 0598
Subfields: none
Justification: N/A
Usage
messages:
Usage
Trip Leg Data)/1644
Requirements)/1644
Financial Detail Addendum (Corporate Card Fleet Transaction O • C
Information)/1644

Values
If present, this PDS cannot contain all low-values, or high-values. It must
contain one of the following values:
Value Description
Y Sales tax included in total purchase amount.
N or zero Card acceptor has the ability to provide tax amount, but
goods/services were not taxable.
space Information is unknown.

PDS 0599—Corporation VAT Number
PDS 0599—Corporation VAT Number

Corporation VAT Number (PDS 0599) contains a corporation’s value added tax
(VAT) number.
Attributes
ans…20; TAGLLL
Tag Field: 0599

Data Field: variable length 1–20 position
Subfields: none
Justification: left
Usage
messages:
Usage
Requirements)/1644
Values
high-values, all spaces, or all zeros. It must be a minimum length of 001 and a

PDS 0600—Card Acceptor Reference Number
PDS 0600—Card Acceptor Reference Number

Card Acceptor Reference Number (PDS 0600) contains a code that facilitates
card acceptor/corporation communication and record keeping.
Attributes
ans…25; TAGLLLVAR
Tag Field: 0600
Subfields: none
Justification: n/a
Usage
messages:
Usage
Requirements)/1644
Values
If present, PDS 0600 Card Acceptor Reference Number must be left justified
and cannot contain all low-values, high-values, all spaces, or all zeros.

0601–1099 used in IPM format offline clearing messages.
Overview ...........................................................................................................10-1
PDS 0601—Party Nature of Filing.....................................................................10-2
PDS 0606—Freight Amount ............................................................................ 10-11
PDS 0607—Duty Amount................................................................................ 10-13
PDS 0608—Destination Postal Code .............................................................. 10-15
PDS 0609—Destination State/Province Code................................................. 10-16
PDS 0610—Destination Country Code ........................................................... 10-17
PDS 0612—Ship Date...................................................................................... 10-18
PDS 0613—Ship-From Postal Code ................................................................ 10-19
PDS 0614—Order Date ................................................................................... 10-20
PDS 0615—Medical Services Ship to Health Industry Number..................... 10-21
PDS 0616—Contract Number.......................................................................... 10-22
PDS 0617—Medical Services Price Adjustment.............................................. 10-23
PDS 0618—Medical Services Product Number Qualifier............................... 10-24
PDS 0619—User Name.................................................................................... 10-25

PDS 0620—Oil Company Brand Name .......................................................... 10-26
PDS 0621—Purchase Time.............................................................................. 10-28
PDS 0622—Motor Fuel Service Type.............................................................. 10-30
PDS 0623—Motor Fuel Information ............................................................... 10-31
PDS 0624—User Account Number ................................................................. 10-34
PDS 0625—User Telephone Number ............................................................. 10-35
PDS 0626—Billing Statement Period .............................................................. 10-36
PDS 0629—Odometer Reading....................................................................... 10-42
PDS 0630—Vehicle Number ........................................................................... 10-44
PDS 0631—Driver Number/ID Number ......................................................... 10-46
PDS 0632—Product Type Code...................................................................... 10-48
PDS 0633—Coupon/Discount Amount .......................................................... 10-50
PDS 0634—Tax Amount 1 .............................................................................. 10-51
PDS 0635—Tax Amount 2 .............................................................................. 10-52
PDS 0636—Call Date....................................................................................... 10-53
PDS 0637—Call Time ...................................................................................... 10-54
PDS 0638—Call To Information...................................................................... 10-55
PDS 0639—Call Duration ................................................................................ 10-58
PDS 0640—Call Time Period .......................................................................... 10-59
PDS 0641—Product Code ............................................................................... 10-61
PDS 0642—Item Description .......................................................................... 10-64

PDS 0643—Item Quantity ............................................................................... 10-65
PDS 0644—Call From Information ................................................................. 10-67
PDS 0645—Item Unit of Measure ................................................................... 10-70
PDS 0646—Unit Price...................................................................................... 10-71
PDS 0647—Extended Item Amount................................................................ 10-73
PDS 0648—Item Discount............................................................................... 10-75
PDS 0649—Call Usage Amount ...................................................................... 10-78
PDS 0654—Debit or Credit Indicator ............................................................. 10-80
PDS 0655—Call Long Distance Amount......................................................... 10-81
PDS 0658—Call Connect Amount................................................................... 10-83
PDS 0659—Other Description ........................................................................ 10-85
PDS 0663—Free-Form Description................................................................. 10-86
PDS 0670—Payer Name or User ID ............................................................... 10-87
PDS 0671—Date of Funds Requested ............................................................ 10-88
PDS 0672—Recipient Name (Seller) ............................................................... 10-89
PDS 0673—Date of Anticipated Receipt of Funds ......................................... 10-90
PDS 0674—Additional Trace/Reference Number Used by Card Acceptor ... 10-91
PDS 0675—Additional Transaction Description Data.................................... 10-92
PDS 0676—Card Acceptor VAT Number ....................................................... 10-93
PDS 0677—Customer VAT Number ............................................................... 10-94
PDS 0678—Unique Invoice Number .............................................................. 10-95
PDS 0679—Commodity Code ......................................................................... 10-96
PDS 0680—Authorized Contact Name ........................................................... 10-98

PDS 0681—Authorized Contact Phone .......................................................... 10-99
PDS 0685—Type of Supply .......................................................................... 10-124
PDS 0686—Tax Exempt Indicator ................................................................ 10-125
PDS 0687—Unique VAT Invoice Reference Number .................................. 10-127
PDS 0689—Corporate Identifier ................................................................... 10-128
PDS 0690—No Show Indicator..................................................................... 10-129
PDS 0691—Days Rented ............................................................................... 10-130
PDS 0692—Weekly Rental Amount.............................................................. 10-131
PDS 0693—Total Authorized Amount .......................................................... 10-132
PDS 0694—One Way Drop Off Charge ....................................................... 10-134
PDS 0695—Regular Mileage Charge............................................................. 10-135
PDS 0696—Extra Mileage Charge................................................................. 10-136
PDS 0697—Late Charge ................................................................................ 10-137
PDS 0698—Fuel Charge ................................................................................ 10-138
PDS 0699—Lodging Total Tax Amount........................................................ 10-139
PDS 0700—Towing Charges ......................................................................... 10-141
PDS 0701—Extra Charges ............................................................................. 10-142
PDS 0702—Other Charges ............................................................................ 10-143
PDS 0703—Total Room Nights ..................................................................... 10-144
PDS 0704—Prepaid Expenses....................................................................... 10-145

PDS 0705—Total Non-Room Tax Amount ................................................... 10-147
PDS 0706—Cash Advances ........................................................................... 10-149
PDS 0707—Valet Charges ............................................................................. 10-151
PDS 0708—Movie Charges ........................................................................... 10-153
PDS 0709—Business Center Charges ........................................................... 10-155
PDS 0710—Health Club Charges.................................................................. 10-157
PDS 0711—Fire Safety Act Indicator ............................................................ 10-159
PDS 0712—Net Fuel Price............................................................................. 10-160
PDS 0713—Restricted Ticket Indicator......................................................... 10-162
PDS 0714—Exchange Ticket Amount .......................................................... 10-163
PDS 0715—Exchange Fee Amount............................................................... 10-164
PDS 0716—Travel Authorization Code ........................................................ 10-165
PDS 0717—IATA Client Code ....................................................................... 10-166
PDS 0718—Employee/Temp Name/ID ........................................................ 10-167
PDS 0719—Employee Social Security Number or ID .................................. 10-168
PDS 0720—Job Description .......................................................................... 10-169
PDS 0721—Job Code .................................................................................... 10-170
PDS 0722—Flat Rate Indicator...................................................................... 10-171
PDS 0723—Regular Hours Worked .............................................................. 10-172
PDS 0724—Regular Hours Rate .................................................................... 10-174
PDS 0725—Overtime Hours Worked ........................................................... 10-176
PDS 0726—Overtime Hours Rate ................................................................. 10-178
PDS 0727—Temp Start Date ......................................................................... 10-180

PDS 0728—Temp Week Ending ................................................................... 10-181
PDS 0729—Requestor Name or ID............................................................... 10-182
PDS 0730—Supervisor/Reports to ................................................................ 10-183
PDS 0731—Time Sheet Number ................................................................... 10-184
PDS 0732—Discount Amount ....................................................................... 10-185
PDS 0733—Subtotal Amount ........................................................................ 10-187
PDS 0734—Miscellaneous Expenses ............................................................ 10-189
PDS 0735—Service Descriptor Codes........................................................... 10-192
PDS 0736—Tracking Number or Pickup Number ....................................... 10-193
PDS 0737—Shipping Net Amounts............................................................... 10-194
PDS 0738—Incentive Amount ...................................................................... 10-196
PDS 0739—Pickup Date................................................................................ 10-198
PDS 0740—Delivery Date ............................................................................. 10-199
PDS 0741—Number of Packages.................................................................. 10-200
PDS 0742—Package Weight ......................................................................... 10-201
PDS 0743—Unit of Measure.......................................................................... 10-202
PDS 0744—Shipping Party Information ....................................................... 10-203
PDS 0745—Shipping Party Address.............................................................. 10-205
PDS 0746—Shipping Party Postal Information ............................................ 10-207
PDS 0747—Shipping Party Contact .............................................................. 10-210
PDS 0748—Delivery Party Information ........................................................ 10-212
PDS 0749—Delivery Party Address Information .......................................... 10-214
PDS 0750—Delivery Party Postal Information ............................................. 10-216

10-vi May 2004 • IPM Clearing Formats
PDS 0754—Delivery Party Contact ............................................................... 10-242
PDS 0755—Line Item Total Amount............................................................. 10-244
PDS 0799—Test Case Traceability Identifiers .............................................. 10-247
PDS 1000–1099—Member-to-Member Proprietary Data.............................. 10-251

IPM Clearing Formats • May 2004 10-vii
Overview
Overview
This chapter provides detailed definitions for private data subelements (PDSs)
0601–1099. For specific information about PDS construction and use, intra-
European, Maestro®, and Cirrus® transactions, and numerical and alphabetical
PDS listings see the beginning of chapter 8 in this manual.
Note Some information in this chapter may be shaded. Shading indicates IPM

PDS 0601—Party Nature of Filing
PDS 0601—Party Nature of Filing

Party Nature of Filing (PDS 0601) contains a code that identifies the disposition
of the electronic invoice.
Attributes
a-1; TAGLLL
Tag Field: 0601

Subfields: none
Justification: n/a
Usage
The following table shows the usage of PDS 0601 (whether it is mandatory,
messages:
Usage
Information)/1644
Values
If present, PDS 0601 must be a fixed length of 001 and contain one of the
following values:
Value Description
P Invoice printed and given to purchaser, and then used for tax reclaim.
S Printed, but invoice is treated as supplemental invoice because electronic
copy is used for tax reclaim.
E Printed invoice suppressed because electronic master version is used for
tax reclaim.
N Not applicable to Party Identification.

PDS 0602—Party Supplemental Data 1

Party Supplemental Data 1 (PDS 0602) contains information about the invoice
party.
Attributes
Tag Field: 0602

Subfields: 3
Occurrences: 1–8
Usage
messages:
Usage
Information)/1644

Subfields
PDS 0602 consists of three subfields as defined in the following table:

1 1–40 Party Supplemental Data ans-40 left
Description 1
2 41–80 Party Supplemental Data 1 ans-40 left
3 81–84 Party Supplemental Data Code 1 ans-4 Left
Subfield 1: Party Supplemental Data Description 1

PDS 0602, subfield 1 Party Supplemental Data Description 1 must be left
justified and cannot contain all low-values, high-values, all spaces or all zeros.
Subfield 2: Party Supplemental Data 1

PDS 0602, subfield 2 Party Supplemental Data 1 must be left justified and
cannot contain all low-values, all high-values, all spaces, or all zeros.
Subfield 3: Party Supplemental Data Code 1

PDS 0602, subfield 3 Party Supplemental Data Code 1 must be left justified and
Values
PDS 0602, Party Supplemental Data 1 must be a minimum length of 084 and a
maximum length of 672 and must be divisible by minimum occurrence length
of 084.


Party Supplemental Data 2 (PDS 0603) contains information about the invoice
party.
Attributes
Tag Field: 0603

Subfields: 3
Occurrences: 1–8
Usage
messages:
Usage
Information)/1644

Subfields
This PDS may contain from one to eight occurrences of Party Supplemental
Data. Each occurrence consists of three subfields as defined in the following
table. Each occurrence requires 84 positions; the length of this PDS must be a

1 1–40 Party Supplemental Data ans-40 left
Description 2
2 41–80 Party Supplemental Data 2 ans-40 left
3 81–84 Party Supplemental Data Code 2 ans-4 left
Subfield 1: Party Supplemental Data Description 2

PDS 0603, subfield 1 Party Supplemental Data Description 2 must be left
justified and cannot contain all low-values, all high-values, all spaces, or all
zeros.
Subfield 2: Party Supplemental Data 2

PDS 0603, subfield 2 Party Supplemental Data 2 must be left justified and
Subfield 3: Party Supplemental Data Code 2

PDS 0603, subfield 3 Party Supplemental Data Code 2 must be left justified and
Values
PDS 0603, Party Supplemental Data 2 must be a minimum length of 084 and a
maximum length of 672 and must be divisible by minimum occurrence length
of 084

PDS 0604—Transaction Supplemental Data 1

Transaction Supplemental Data 1 (PDS 0604) contains information about the
transaction.
Attributes
Tag Field: 0604

Subfields: 3
Occurrences: 1–8
Usage
messages:
Usage
Information)/1644
s1 Transaction Supplemental Data Description 1 O • C

Subfields
This PDS may contain from one to eight occurrences of Transaction
Supplemental Data. Each occurrence consists of three subfields as defined in
the following table. Each occurrence requires 84 positions; the length of this
PDS must be a multiple of 84, with a maximum length of 672 positions

1 1–40 Transaction Supplemental Data ans-40 left
Description 1
2 41–80 Transaction Supplemental Data 1 ans-40 left
Code 1
Subfield 1: Transaction Supplemental Data Description 1

PDS 0604, subfield 1 Transaction Supplemental Data Description 1 must be left
zeros.
Subfield 2: Transaction Supplemental Data 1

PDS 0604, subfield 2 Transaction Supplemental Data 1 must be left justified
and cannot contain all low-values, all high-values, all spaces, or all zeros.
Subfield 3: Transaction Supplemental Data Code 1

PDS 0604, subfield 3 Transaction Supplemental Data Code 1 must be left
zeros.
Values
PDS 0604 Transaction Supplemental Data 1 may contain from one to eight
occurrences of Transaction Supplemental Data. Each occurrence consists of
three subfields as defined in the following table. Each occurrence must be a
minimum length of 084 and a maximum length of 672 and must be divisible by
minimum occurrence length of 084


Transaction Supplemental Data 2 (PDS 0605) contains information about the
transaction.
Attributes
Tag Field: 0605

Subfields: 3
Occurrences: 1–8
Usage
messages:
Usage
Information)/1644
s1 Transaction Supplemental Data Description 2 O • C

Subfields
PDS 0605 Transaction Supplemental Data 2 may contain from one to eight
occurrences of transaction supplemental data. Each occurrence consists of
three subfields as defined in the following table. Each occurrence must be a
minimum length of 084 and a maximum length of 672 and must be divisible by
minimum occurrence length of 084.

Description 2
2 41–80 Transaction Supplemental Data 2 ans-40 left
Code 2
Subfield 1: Transaction Supplemental Data Description 2

PDS 0605, subfield 1 Transaction Supplemental Data Description 2 must be left
zeros.
Subfield 2: Transaction Supplemental Data 2

PDS 0605, subfield 2 Transaction Supplemental Data 2 must be left justified
Subfield 3: Transaction Supplemental Data Code 2

PDS 0605, subfield 3 Transaction Supplemental Data Code 2 must be left
zeros.

PDS 0606—Freight Amount

Freight Amount (PDS 0606) contains the freight charges on total purchases.
Attributes
ans-14; TAGLLL
Tag Field: 0606

Subfields: 3
Usage
messages:
Usage
Requirements)/1644
s1 Freight Amount O • C
s2 Freight Amount Exponent O • C
s3 Freight Amount Sign O • C
Subfields

1 1–12 Freight Amount n-12 right
2 13 Freight Amount Exponent n-1 n/a
3 14 Freight Amount Sign a-1 n/a

Subfield 1: Freight Amount

PDS 0606, subfield 1 contains the freight charges on the total purchase. If
present, subfield 1 Freight Amount must be numeric and may contain all zeros.
Subfield 2: Freight Amount Exponent

If present, subfield 2 must be numeric and contain a value of 0–5.
Subfield 3: Freight Amount Sign

If present, subfield 3 must contain a value of D or C.
Value Description
D Freight amount is a debit
C Freight amount is a credit

PDS 0607—Duty Amount

Duty Amount (PDS 0607) is the duty on the total purchase amount.
Attributes
ans-14; TAGLLL
Tag Field: 0607

Subfields: 3
Usage
messages:
Usage
Requirements)/1644
s1 Duty Amount O • C
s2 Duty Amount Exponent O • C
s3 Duty Amount Sign O • C

Subfield Layout

1 1–12 Duty Amount n-12 right
2 13 Duty Amount Exponent n-1 n/a
3 14 Duty Amount Sign a-1 n/a
Subfield 1: Duty Amount

PDS 0607, subfield 1 contains the duty amount on the total charges. If present,
subfield 1 Duty Amount must be numeric and may contain all zeros.
Subfield 2: Duty Amount Exponent

If present, subfield 2 must be numeric and contain a value of 0-5.
Subfield 3: Duty Amount Sign

If present, subfield 3 must contain a value of D or C.
Value Description
D Duty amount is a debit
C Duty amount is a credit
Values
If present, PDS 0607 Duty Amount must be a fixed length of 014.

PDS 0608—Destination Postal Code
PDS 0608—Destination Postal Code

Destination Postal Code (PDS 0608) contains the ZIP code or other postal code
where the purchased goods will be delivered.
Attributes
ans-10; TAGLLL
Tag Field: 0608
Subfields: none
Justification: left
Usage
messages:
Usage
Requirements)/1644
For transactions acquired in the U.S. region, if present, Destination Postal Code
(PDS 0608) must contain either five numeric characters, left justified, spaced
filled, or the “ZIP+four” nine numeric characters with a hyphen between the
fifth and sixth numeric character.
Values
If present, PDS 0608, must be left justified and cannot contain all low-values,
all high-values, all spaces, or all zeros.

PDS 0609—Destination State/Province Code
PDS 0609—Destination State/Province Code

Destination State/Province Code (PDS 0609) indicates the state or province of
the country where the purchased goods will be delivered.
Attributes
ans-3; TAGLLL
Tag Field: 0609
Subfields: none
Justification: left
Usage
messages:
Usage
Requirements)/1644
Values
If present, PDS 0609 must contain a valid U.S. state code if Destination Country
Code (PDS 0610) contains USA.
If the destination is a U.S. territory (Guam, Puerto Rico, or Virgin Islands),

members should provide the three-position country code (GUM, PRI, or VIR)
in both PDS 0609 and PDS 0610.

PDS 0610—Destination Country Code
PDS 0610—Destination Country Code

Destination Country Code (PDS 0610) contains the code of the country where
the purchased goods will be delivered.
Attributes
ans-3; TAGLLL
Tag Field: 0610
Subfields: none
Justification: left
Usage
messages:
Usage
Requirements)/1644
Values
If present, PDS 0610 must contain a valid alphabetic ISO country code.
If the destination is a U.S. territory (Guam, Puerto Rico, or Virgin Islands),

members should provide the three-position country code (GUM, PRI, or VIR)
in both PDS 0609 and PDS 0610.

PDS 0612—Ship Date
PDS 0612—Ship Date

Ship Date (PDS 0612) contains the date the merchandise was shipped to the
destination.
Attributes
n-6; TAGLLL
Tag Field: 0612

Subfields: none
Justification: n/a
Usage
messages:
Usage
Values
If present, PDS 0612 must be a valid date in the format YYMMDD. PDS 0612
Ship Date must be numeric and be a fixed length of 006.

PDS 0613—Ship-From Postal Code
PDS 0613—Ship-From Postal Code

Ship-From Postal Code (PDS 0613) contains the ZIP code or other postal code
from which items were shipped.
Attributes
ans-10; TAGLLL
Tag Field: 0613
Subfields: none
Justification: left
Usage
messages:
Usage
Requirements)/1644
For transactions acquired in the U.S. region, if present, Ship From Postal Code
(PDS 0613) must contain either five numeric characters, be left justified, spaced
filled, or the “ZIP+4” 9 numeric characters with a hyphen between the fifth and
sixth numeric character.
Values
If present, PDS 0613 Ship–From Postal Code must be left justified, and cannot

PDS 0614—Order Date
PDS 0614—Order Date

Order Date (PDS 0614) contains the date the item was ordered.
Attributes
n-6; TAGLLL
Tag Field: 0614

Subfields: none
Justification: n/a
Usage
messages:
Usage
Requirements)/1644
Values

PDS 0615—Medical Services Ship to Health Industry Number
PDS 0615—Medical Services Ship to Health Industry

Number
Medical Services Ship to Health Industry Number (PDS 0615) contains the
health industry number to where the medical services are being shipped.
Attributes
ans…40; TAGLLLVAR
Tag Field: 0615

Subfields: none
Justification: n/a
Usage
messages:
Usage
Values
PDS 0615, Medical Services Ship to Health Industry Number must be a
minimum length of 001 and a maximum length of 040. If present, PDS 0615
must be left justified and cannot contain all low-values, all high-values, all
spaces, or all zeros.

PDS 0616—Contract Number
PDS 0616—Contract Number

Contract Number (PDS 0616) contains the corporate contract number.
Attributes
ans…40; TAGLLLVAR
Tag Field: 0616

Subfields: none
Justification: left
Usage
messages:
Usage
Values
PDS 0616, Contract Number must be a minimum length of 001 and a maximum
length of 040. If present, PDS 0616 must be left justified and cannot contain
all low-values, all high-values, all spaces, or all zeros.

PDS 0617—Medical Services Price Adjustment
PDS 0617—Medical Services Price Adjustment

Medical Services Price Adjustment (PDS 0617) contains a code that identifies
the type of price adjustment related the medical services provided.
Attributes
a-1; TAGLLL
Tag Field: 0617

Subfields: none
Justification: left
Usage
messages:
Usage
Values
If present, PDS 0617 Medical Services Price Adjustment must be a fixed length
of 001 and contain one of the following values:
Value Description
A Price Adjustment
B Original
C Credit
D Re-bill

PDS 0618—Medical Services Product Number Qualifier
PDS 0618—Medical Services Product Number Qualifier

Medical Services Product Number Qualifier (PDS 0618) contains a code that
identifies the product number qualifier of the medical services.
Attributes
an-2; TAGLLL
Tag Field: 0618

Subfields: none
Justification: n/a
Usage
messages:
Usage
Values
If present, PDS 0618 Medical Services Product Number Qualifier must be a
fixed length of 002 and contain one of the following values:
Value Description
01 HIBCC (Health Industry Business Communication Council)
02 UCC (Uniform Code Council)
03 Other

PDS 0619—User Name
PDS 0619—User Name

User Name (PDS 0619) contains the user name related to the Telephony Billing
information.
Attributes
ans…40; TAGLLLVAR
Tag Field: 0619

Subfields: none
Justification: left
Usage
messages:
Usage
Financial Detail Addendum (Telephony Billing Summary)/1644 O • C
Values
PDS 0619, User Name must be a minimum length of 001 and a maximum
length of 040. If present, PDS 0619 must be left justified and cannot contain

PDS 0620—Oil Company Brand Name

Oil Company Brand Name (PDS 0620) contains a four-digit code that indicates
the card acceptor oil company brand name.
Attributes
n-4; TAGLLL
Tag Field: 0620
Subfields: none
Usage
messages:
Usage
Information)/1644
This PDS is required if the associated First Presentment/1240 is a MasterCard

Corporate Fleet Card® transaction at a fuel location and is submitted for one of
the following incentive interchange rate programs:
IRD Description

Values
If present, and submitted for an incentive interchange rate program, PDS 0620
cannot contain all zeros (zeros are allowed for Standard transactions).

PDS 0621—Purchase Time

Purchase Time (PDS 0621) contains the time of day the purchase was made.
Attributes
n-4; TAGLLL
Tag Field: 0621

Subfields: none
Justification: n/a
Usage
messages:
Usage
Information)/1644

IRD Description

Values
If present, PDS 0621 should be in the format hhmm, with hours in the range
00–23 and minutes in the range 00–59.

PDS 0622—Motor Fuel Service Type
PDS 0622—Motor Fuel Service Type

Motor Fuel Service Type (PDS 0622) contains the type of service received at
the card acceptor site.
Attributes
ans-1; TAGLLL
Tag Field: 0622

Subfields: none
Justification: n/a
Usage
messages:
Usage
Information)/1644
Values
GCMS does not edit this subfield. If present, this PDS must contain a value
from the following table:
Value Description
0 or space Undefined
1 Self service.
2 Full service.
3 Only non-fuel products being purchased.

PDS 0623—Motor Fuel Information

Motor Fuel Information (PDS 0623) contains the acquirer’s motor fuel product
code translated from the information the attendant entered.
Attributes
ns-35; TAGLLL
Tag Field: 0623
Subfields: 6
Usage
messages:
Usage
Information)/1644
s1 Motor Fuel Product Code C • C
s2 Motor Fuel Unit Price C • C
s3 Motor Fuel Unit of Measure C • C
s4 Motor Fuel Quantity C • C
s5 Motor Fuel Quantity Exponent C • C
s6 Motor Fuel Sale Amount C • C

This PDS is required if the following occurs:

• Motor Fuel Service Type (PDS 0622) is present and contains a value other
than 3
• The associated First Presentment/1240 is a MasterCard Corporate Fleet
Card® transaction at a fuel location and is submitted for one of the
IRD Description
Subfields
PDS 0623 subfields are in the following table:

1 1–3 Motor Fuel Product Code n-3 right
2 4–15 Motor Fuel Unit Price n-12 right
3 16 Motor Fuel Unit of Measure ns-1 n/a
4 17–22 Motor Fuel Quantity n-6 right
5 23 Motor Fuel Quantity Exponent n-1 n/a
6 24–35 Motor Fuel Sale Amount n-12 right
Subfield 1: Motor Fuel Product Code

If PDS 0623 is present, Motor Fuel Product Code must be in the range 001–029
or 100–299.
Subfield 2: Motor Fuel Unit Price

If PDS 0623 is present, Motor Fuel Unit Price must be numeric and non-zero.

Subfield 3: Motor Fuel Unit of Measure

If PDS 0623 is present, Motor Fuel Unit of Measure must be a space or in the
range 1–5 as in the following table:
Value Description
1 Gallons.
2 Liters.
3 Pounds.
4 Kilos.
5 Imperial gallons.
space Not applicable.
Subfield 4: Motor Fuel Quantity

If PDS 0623 is present, Motor Fuel Quantity must be numeric and greater than
zero.
Subfield 5: Motor Fuel Quantity Exponent

If PDS 0623 is present, Motor Fuel Quantity Exponent must be in the range
0–5.
Subfield 6: Motor Fuel Sale Amount

If PDS 0623 is present, Motor Fuel Sale Amount must be greater than zero and
the same currency as the First Presentment/1240.
Values
If present, PDS 0623 Motor Fuel Information must be a fixed length of 35.

PDS 0624—User Account Number
PDS 0624—User Account Number

User Account Number (PDS 0624) contains the user’s account number related
to the Telephony Billing information.
Attributes
ans…40; TAGLLLVAR
Tag Field: 0624

Subfields: none
Justification: left
Usage
messages:
Usage
Values
PDS 0624, User Account Number must be a minimum length of 001 and a
maximum length of 040. If present, PDS 0624 must be left justified and cannot

PDS 0625—User Telephone Number
PDS 0625—User Telephone Number

User Telephone Number (PDS 0625) contains the user’s telephone number
related to the Telephony Billing information.
Attributes
ans…25; TAGLLLVAR
Tag Field: 0625

Subfields: none
Justification: left
Usage
messages:
Usage
Values
PDS 0625, User Telephone Number must be a minimum length of 001 and a
maximum length of 025. If present, PDS 0625 must be left justified and cannot

PDS 0626—Billing Statement Period

Billing Statement Period (PDS 0626) contains the billing start and end dates.
Attributes
n-12; TAGLLL
Tag Field: 0626

Subfields: 2
Usage
messages:
Usage
s1 Statement Start Date O • C
s2 Statement End Date O • C
Subfields

1 1–6 Statement Start Date n-6 n/a
2 7–12 Statement End Date n-6 n/a

Subfield 1: Statement Start Date

If present, PDS 0626, subfield 1 Statement Start Date must be numeric and
must be a valid date in the format YYMMDD.
Subfield 2: Statement End Date

If present, PDS 0626, subfield 2 Statement End Date must be numeric and must
be a valid date in the format YYMMDD.
Values
PDS 0626, Billing Statement Period must be a fixed length of 012.

PDS 0627—Billing Event 1

Billing Event 1 (PDS 0627) contains information pertaining to the Telephony
Billing Event.
Attributes
Tag Field: 0627

Subfields: 4
Occurrences: 1–10
Usage
messages:
Usage

Subfields

1 1–12 Billing Event Amount 1 n-12 right
2 13 Billing Event Exponent 1 n-1 n/a
3 14 Billing Event Sign 1 a-1 n/a
4 15–54 Billing Event Description ans-40 left
Subfield 1: Billing Event Amount 1

the billing event, and may be all zeros.
Subfield 2: Billing Event Exponent 1

PDS 0627, subfield 2 Billing Event Exponent 1 must be numeric and must be a
value within the range of 0–5.
Subfield 3: Billing Event Sign 1

If PDS 0627 is present, subfield 3 contains debit/credit indicator.
Value Description
D Billing Event amount 2 is a debit
C Billing Event amount 2 is a credit
Subfield 4: Billing Event Description 1

If PDS 0627 is present, subfield 4 contains the description of the billing event.
It must be a fixed length of 40 positions, be left justified and cannot contain all
Values
PDS 0627, Billing Event 1 must be a minimum length of 54 and a maximum


Billing Event 2 (PDS 0628) contains information pertaining to the Telephony
Billing Event.
Attributes
Tag Field: 0628

Subfields: 4
Occurrences: 1–10
Usage
messages:
Usage

Subfields

1 1–12 Billing Event Amount 2 n-12 right
2 13 Billing Event Exponent 2 n-1 n/a
3 14 Billing Event Sign 2 a-1 n/a
4 15–54 Billing Event Description 2 ans-40 left
Subfield 1: Billing Event Amount 2

the billing event, and may be all zeros.
Subfield 2: Billing Event Exponent 2

PDS 0628, subfield 2 Billing Event Exponent 2 must be numeric and must be a
value within the range of 0–5.
Subfield 3: Billing Event Sign 2

If PDS 0628 is present, subfield 3 contains debit/credit indicator.
Value Description
D Billing event amount 2 is a debit
C Billing event amount 2 is a credit
Subfield 4: Billing Event Description 2

If PDS 0628 is present, subfield 4 contains the description of the billing event.
It must be a fixed length of 40 positions, be left justified and cannot contain all
Values
PDS 0628, Billing Event 2 must be a minimum length of 54 and a maximum

PDS 0629—Odometer Reading

Odometer Reading (PDS 0629) contains the vehicle odometer reading the
purchaser entered.
Attributes
ans…7; TAGLLLVAR
Tag Field: 0629
Subfields: none
Justification: left
Usage
messages:
Usage
Information)/1644

• Product Type Code (PDS 0632) contains a value in the range 1–4
IRD Description

Values
If present, PDS 0629 Odometer Reading must be left-justified and cannot

PDS 0630—Vehicle Number

Vehicle Number (PDS 0630) is the number assigned to the vehicle by the
business using the MasterCard Corporate Fleet Card® and entered by the
cardholder at the point of interaction.
Attributes
ans…17; TAGLLLVAR
Tag Field: 0630

Subfields: none
Justification: left
Usage
messages:
Usage

Information)/1644

• No data is present in Driver Number/ID Number (PDS 0631)
• Product Type Code (PDS 0632) contains a 2
IRD Description

Values
If present, PDS 0630 Vehicle Number must be left-justified, and cannot contain

PDS 0631—Driver Number/ID Number

Driver Number/ID Number (PDS 0631) contains the number assigned to the
driver by the business using the MasterCard Corporate Fleet Card® and
entered by the cardholder at the point of interaction.
Attributes
ans…17; TAGLLLVAR
Tag Field: 0631

Subfields: none
Justification: left
Usage
messages:
Usage
Information)/1644

• Product Type Code (PDS 0632) contains a 1 or 3
IRD Description

Values
If present, PDS 0631 must be left-justified, and cannot contain all low-values,
all high-values, all spaces, or all zeros. In addition, the first position of
PDS 0631 must contain a numeric value.

PDS 0632—Product Type Code

Product Type Code (PDS 0632) contains a code read from a card magnetic
stripe that indicates prompts that occur at the point of interaction.
Attributes
n-1; TAGLLL
Tag Field: 0632
Subfields: none
Justification: n/a
Usage
messages:
Usage
Information)/1644

IRD Description

Values
If present, PDS 0632 must contain a value in the range 1–5 as shown in the
following table:
Value Description
1 Prompts for ID number and odometer reading.
2 Prompts for vehicle number and odometer reading.
3 Prompts for driver number and odometer reading.
4 Prompts for odometer reading only.
5 No prompts issued.
Values 1–4 are used in the editing process for MasterCard Corporate Fleet card
transactions conducted at fuel locations that are submitted for the following
interchange rate programs:
IRD Description
Related Required PDS Information

The following PDS’s are required to be present when PDS 0632 is present,
based on the value submitted.
If PDS 0632 contains a… Then the following is also required

Driver Number/ID Number (PDS 0631) and
1 Odometer Reading (PDS 0629)
Vehicle Number (PDS 0630) and
Driver Number/ID Number (PDS 0631) and

PDS 0633—Coupon/Discount Amount
PDS 0633—Coupon/Discount Amount

Coupon/Discount Amount (PDS 0633) contains the coupon or discount dollar
amount.
Attributes
n-12; TAGLLL
Tag Field: 0633
Subfields: none
Usage
messages:
Usage
Information)/1644
Values
If present, PDS 0633 must contain a numeric value.

PDS 0634—Tax Amount 1

Tax Amount 1 (PDS 0634) contains the tax amount for tax exempt fleets.
Attributes
n-6; TAGLLL
Tag Field: 0634

Subfields: none
Justification: n/a
Usage
messages:
Usage
Information)/1644
Values
If present, PDS 0634 Tax Amount 1 must be numeric and may contain all
zeros.


Tax Amount 2 (PDS 0635) contains the tax amount for tax exempt fleets.
Attributes
n-6; TAGLLL
Tag Field: 0635

Subfields: none
Justification: n/a
Usage
messages:
Usage
Information)/1644
Values
If present, PDS 0635 Tax Amount 2 must be numeric and may contain all
zeros.

PDS 0636—Call Date
PDS 0636—Call Date

Call Date (PDS 0636) contains the date of the call related to the Telephony
Billing Detail.
Attributes
n-6; TAGLLL
Tag Field: 0636

Subfields: none
Justification: n/a
Usage
messages:
Usage
Financial Detail Addendum (Telephony Billing Detail)/1644 O • C
Values
PDS 0636, Call Date must be a fixed length of 006. If present, PDS 0636 must
be numeric and a valid date in the format YYMMDD.

PDS 0637—Call Time
PDS 0637—Call Time

Call Time (PDS 0637) contains the time of the call related to the Telephony
Billing Detail.
Attributes
n-6; TAGLLL
Tag Field: 0637

Subfields: none
Justification: n/a
Usage
messages:
Usage
Values
PDS 0637, Call Time must be a fixed length of 006. If present, PDS 0637 must
be numeric and a valid time in the format HHMMSS.

PDS 0638—Call To Information

Call To Information (PDS 0638) contains the call location information and the
phone number called pertaining to the Telephony Billing Event.
Attributes
ans-146; TAGLLL
Tag Field: 0638

Subfields: 5
Usage
messages:
Usage
s1 Call To City O • C
s2 Call To State/Province O • C
s3 Call To Country O • C
s4 Call To Number O • C
s5 Call To Type O • C

Subfields
This PDS consists of five subfields as defined in the following table:

1 1–40 Call To City ans-40 left
2 41–80 Call To State/Province ans-40 left
3 81–120 Call To Country ans-40 left
4 121–145 Call To Number ans-25 left
5 146 Call To Type an-1 n/a
Subfield 1: Call To City

If PDS 0638 is present, subfield 1 must contain the city to which the call was
made. It must be left justified with trailing spaces, and cannot contain all low-
Subfield 2: Call To State/Province

If PDS 0638 is present, subfield 2 must contain the state/province to which the
call was made. It must be left justified with trailing spaces, and cannot contain
Subfield 3: Call To Country

If PDS 0638 is present, subfield 3 must contain the country to which the call
was made. It must be left justified with trailing spaces, and cannot contain all
Subfield 4: Call To Number

If PDS 0638 is present, subfield 4 must contain the phone number called. It
must be left justified with trailing spaces, and cannot contain all low-values, all
For transactions acquired in the U.S. or Canada region, Call To Number

(PDS 0638, subfield 4), must contain a 10-position phone number, left-justified

Subfield 5: Call To Type

Value Description
C Outgoing Call
I Incoming Call
V Voice Mail
P Page
O Other
F Toll-Free Call
Values
PDS 0638, Call To Information must be a fixed length of 146.

PDS 0639—Call Duration
PDS 0639—Call Duration

Call Duration (PDS 0639) contains the duration of the call related to the
Telephony Billing Detail.
Attributes
n-6; TAGLLL
Tag Field: 0639

Subfields: none
Justification: n/a
Usage
messages:
Usage
Values
PDS 0639, Call Duration must be a fixed length of 006. If present, PDS 0639
must be numeric and should be in the format HHMMSS.

PDS 0640—Call Time Period

Call Time Period (PDS 0640) describes the period (for example, Peak, Off
Peak) of the call related to the Telephony Billing Detail.
Attributes
an-2; TAGLLL
Tag Field: 0640

Subfields: none
Justification: n/a
Usage
messages:
Usage
Values
If present, PDS 0640 must contain one of the following values:
Value Description
PP Peak Period
OP Off Peak Period
MP Multiple Period
OT Other

Values
PDS 0640, Call Time Period must be a fixed length of 002.

PDS 0641—Product Code

Product Code (PDS 0641) contains the non-fuel related product code of the
individual item purchased.
Attributes
ans…15; TAGLLLVAR
Tag Field: 0641
Subfields: none
Justification: left
Usage
messages:
Usage
Values
If the Corporate Line Item Detail Addendum/1644 message is provided,
PDS 0641 is mandatory.
When a Financial Detail Addendum (Corporate Line Item Detail)/1644 is

submitted in conjunction with non-fuel purchases conducted with a
MasterCard Corporate Fleet Card® at a fuel location, PDS 0641 must be
provided and contain a three-position non-fuel product code in the range
030–099 or 300–999.

submitted in conjunction with a Financial Detail Addendum (Temporary
Services)/1644 message, PDS 0641 should contain a value of Temporary–01.


submitted in conjunction with a Financial Detail Addendum (Shipping/Courier
Services)/1644 message, PDS 0641 should contain a value of Shipping–01.
When a Financial Detail Addendum (Corporate Line Item Detail)/1644 message

is submitted in conjunction with a lodging MCC, Product Code (PDS 0641)
must be one of the following values:
Value Description
L-1000 Room Rate
L-1020 Room Tax
L-1021 Non-Room Tax
L-1100 Room Service Charges
L-1101 Restaurant Charges
L-1102 Tray Charges
L-1103 Gratuities
L-1104 Prepaid Expenses
L-1105 Telephone Charges
L-1106 Movie Charges
L-1107 Dry Cleaning Charges
L-1108 Laundry Charges
L-1109 Health Club Charges
L-1110 Valet Charges
L-1111 Gift Shop Charges
L-1112 Cash Disbursements
L-1113 Business Center Charges
L-1114 Lounge Charges
L-1115 Bar Charges
L-1116 Mini Bar Charges
L-1117 Audiovisual Charges
L-1118 Banquet Charges
L-1119 Conference Room Charges
L-1120 Early Departure Charges

Value Description
L-1121 Transportation Charges
L-1122 Internet Access Charges
L-9999 Miscellaneous Charges
In all other situations, PDS 0641 must be left justified and cannot contain all
zeros or all spaces.

PDS 0642—Item Description
PDS 0642—Item Description

Item Description (PDS 0642) contains the description of the individual item
purchased.
Attributes
ans…35; TAGLLLVAR
Tag Field: 0642
Subfields: none
Justification: left
Usage
messages:
Usage
If the Financial Detail Addendum (Corporate Line Item Detail)/1644 message is

provided, PDS 0642 is mandatory.

Services)/1644 message, PDS 0642 should contain “Temporary Services”.

Services)/1644 message, PDS 0642 should contain ”Shipping Services”.
Values
PDS 0642 must be left justified and cannot contain all spaces, all zeros, all low-
values, or all high-values.

PDS 0643—Item Quantity

Item Quantity (PDS 0643) indicates the quantity of the item purchased and the
associated decimal point location.
Attributes
n-13; TAGLLL
Tag Field: 0643
Subfields: 2
Usage
messages:
Usage
s1 Item Quantity M • M
s2 Item Quantity Exponent M • M


Services)/1644 message, PDS 0643 should contain a value of 1.


Subfields
PDS 0643 subfields are listed in the following table:

1 1–12 Item Quantity n-12 right
2 13 Item Quantity Exponent n-1 n/a
Subfield 1: Item Quantity

If present, Item Quantity (PDS 0643, subfield 1) must be numeric and be
greater than zero.
Subfield 2: Item Quantity Exponent

If present, Item Quantity Exponent (PDS 0643, subfield 2) must be numeric.

PDS 0644—Call From Information

Call From Information (PDS 0644) contains the location description for the
originator of the telephone call and the number from which the call was made.
Attributes
ans-145; TAGLLL
Tag Field: 0644

Subfields: 4
Usage
messages:
Usage
s1 Call From City O • C
s2 Call From State/Province O • C
s3 Call From Country O • C
S4 Call From Number O • C

Subfields

1 1–40 Call From City ans-40 left
2 41–80 Call From State/Province ans-40 left
3 81–120 Call From Country ans-40 left
4 121–145 Call From Number ans-25 left
Subfield 1: Call From City

If PDS 0644 is present, subfield 1 must contain the city from which the call was
originated. It must be left justified with trailing spaces, and cannot contain all
Subfield 2: Call From State/Province

Subfield 2 must contain the state/province from which the call was originated.
It must be left justified with trailing spaces, and cannot contain all low-values,
Subfield 3: Call From Country

Subfield 3 must contain the country from which the call was originated. It
must be left justified with trailing spaces, and cannot contain all low-values, all
Subfield 4: Call From Number

Subfield 4 must contain the phone number from which the call was originated.
It must be left justified with trailing spaces, and cannot contain all low-values,
For transactions acquired in the U.S. or Canada region, Call From Number
(PDS 0644, subfield 4), must contain a 10-position phone number, be left
justified with trailing spaces. The first three positions must be numeric.

Values
PDS 0644, Call From Information must be a fixed length of 145.

PDS 0645—Item Unit of Measure
PDS 0645—Item Unit of Measure

Item Unit of Measure (PDS 0645) contains the line item unit of measurement
code.
Attributes
ans…12; TAGLLLVAR
Tag Field: 0645
Subfields: none
Justification: n/a
Usage
messages:
Usage


Services)/1644 message, PDS 0645 should contain a value of “Unit”.

Services)/1644 message, PDS 0645 should contain a value of “Unit”. Values
Values

PDS 0646—Unit Price

Unit Price (PDS 0646) is the price for one unit of the product.
Attributes
n-13; TAGLLL
Tag Field: 0646

Subfields: see “Subfields”
Justification: left
Usage
messages:
Usage
s1 Unit Price O • C
s2 Unit Price Exponent O • C
This PDS is part of the “line item detail” when a MasterCard Corporate
Purchasing Card™ or MasterCard Corporate Fleet Card® is used in a business-
to-business purchase.



Subfields
PDS 0646 subfields are listed in the following table:

s1 1–12 Unit Price n-12 right
s2 13 Unit Price Exponent n-1 n/a
Subfield 1 Unit Price

PDS 0646 subfield 1 Unit Price must be numeric.
Subfield 2 Unit Price Exponent

PDS 0646 subfield 2 Unit Price Exponent must be between 0-5.
Values
If present, PDS 0646, subfield 1 Unit Price must be numeric. PDS 0646,
subfield 2 Unit Price Exponent must contain a value in the range 0-5.

PDS 0647—Extended Item Amount

Extended Item Amount (PDS 0647) contains the individual item amount that is
normally calculated as price multiplied by quantity.
Attributes
ans-14; TAGLLL
Tag Field: 0647
Subfields: 3
Usage
messages:
Usage
s1 Extended Item Amount M • M
s2 Extended Item Amount Exponent M • M
s3 Extended Item Amount Sign M • M


Services)/1644 message, PDS 0647 should equal the Transaction Amount.

Services)/1644 message, PDS 0647 should equal the Transaction Amount.

Subfields

1 1–12 Extended Item Amount n–12 right
2 13 Extended Item Amount Exponent n-1 n/a
3 14 Extended Item Amount Sign a–1 n/a
Subfield 1: Extended Item Amount

If PDS 0647 is present, subfield 1 contain the amount and be numeric and
greater than zero.
Subfield 2: Extended Item Amount Exponent

Subfield 3: Extended Item Amount Sign

Value Description
D Extended item amount is a debit
C Extended item amount is a credit
Values
If present, PDS 0647 Extended Item Amount must be a fixed length of 014.

PDS 0648—Item Discount

Item Discount (PDS 0648) contains the item discount indicator and amount.
Attributes
ans-20; TAGLLL
Tag Field: 0648
Subfields: 5
Usage
messages:
Usage
s1 Item Discount Indicator O • C
s2 Item Discount Amount O • C
s3 Item Discount Rate O • C
s4 Item Discount Rate Exponent O • C
s5 Item Discount Amount Sign O • C
This PDS is part of the “line item detail” when a MasterCard Corporate
Purchasing Card™ or MasterCard Corporate Fleet Card® is used in a business-
to-business purchase.
If subfields 1 and 2 are provided, then the member must also provide subfields
3, 4, and 5.

Subfields
This PDS consists of five subfields as defined in the following table:

1 1 Discount Indicator as-1 n/a
2 2–13 Discount Amount ans-12 right
3 14–18 Item Discount Rate n-5 right
4 19 Item Discount Rate Exponent n-1 n/a
5 20 Item Discount Amount Sign a–1 n/a
Subfield 1: Discount Indicator

Value Description
Y Amount is discounted.
N Amount is not discounted.
space Not supported.
Subfield 2: Discount Amount

If PDS 0648 is present, subfield 2 must be numeric and cannot be all zeros if
subfield 1 is Y.
Subfield 3: Item Discount Rate

This subfield is the discount rate applicable to the amount. If PDS 0648 is
present, subfield 3 must contain a five-digit numeric value.
Subfield 4: Item Discount Rate Exponent

If PDS 0648 is present, subfield 4 must contain a value in the range 0–5.

Subfield 5: Item Discount Amount Sign

Value Description
D Item discount amount is a debit
C Item discount amount is a credit
Values
PDS 0648 Item Discount Amount must be a fixed length of 20.

PDS 0649—Call Usage Amount

Call Usage Amount (PDS 0649) contains the call usage amount information
pertaining to the Telephony Billing Event.
Attributes
ans-14; TAGLLL
Tag Field: 0649

Subfields: 3
Usage
messages:
Usage
s1 Call Usage Amount O • C
s2 Call Usage Amount Exponent O • C
s3 Call Usage Amount Sign O • C

Subfields

1 1–12 Call Usage Amount n-12 right
2 13 Call Usage Amount Exponent n-1 n/a
3 14 Call Usage Amount Sign a-1 n/a
Subfield 1: Call Usage Amount

If PDS 0649 is present, subfield 1 must be numeric and contain the usage
amount of the call, and may be all zeros.
Subfield 2: Call Usage Amount Exponent

If PDS 0649 is present, subfield 2 must be numeric and contain a value of 0–5
Subfield 3: Call Usage Amount Sign

Value Description
D Call Usage Amount is a debit
C Call Usage Amount is a credit
Values
PDS 0649, Call Usage Amount must be a fixed length of 14.

PDS 0654—Debit or Credit Indicator
PDS 0654—Debit or Credit Indicator

Debit or Credit Indicator (PDS 0654) indicates whether the net of extended
item amount, net of discount, taxes, and price, is a debit or credit.
Attributes
as-1; TAGLLL
Tag Field: 0654
Subfields: none
Justification: n/a
Usage
messages:
Usage

Values
PDS 0654 must contain one of the following values:
Value Description
D Extended item amount is a debit.
C Extended item amount is a credit.

PDS 0655—Call Long Distance Amount

Call Long Distance Amount (PDS 0655) contains the Long Distance amount
information pertaining to the Telephony Billing Event.
Attributes
ans-14; TAGLLL
Tag Field: 0655

Subfields: 3
Usage
messages:
Usage
s1 Call Long Distance Amount O • C
s2 Call Long Distance Amount Exponent O • C
s3 Call Long Distance Amount Sign O • C

Subfields

1 1–12 Call Long Distance Amount n-12 right
2 13 Call Long Distance Amount Exponent n-1 n/a
3 14 Call Long Distance Amount Sign a-1 n/a
Subfield 1: Call Long Distance Amount

If PDS 0655 is present, subfield 1 must be numeric and contain the long
distance amount of the call, and may be all zeros.
Subfield 2: Call Long Distance Amount Exponent

Subfield 3: Call Long Distance Amount Sign

Value Description
D Call long distance amount is a debit
C Call long distance amount is a credit
Values
PDS 0655, Call Long Distance Amount must be a fixed length of 14.

PDS 0658—Call Connect Amount

Call Connect Amount (PDS 0658) contains the call connect amount information
pertaining to the Telephony Billing Event.
Attributes
ans-14; TAGLLL
Tag Field: 0658

Subfields: 3
Usage
messages:
Usage
s1 Call Connect Amount O • C
s2 Call Connect Amount Exponent O • C
s3 Call Connect Amount Sign O • C

Subfields

1 1–12 Call Connect Amount n-12 right
2 13 Call Connect Amount Exponent n-1 n/a
3 14 Call Connect Amount Sign a-1 n/a
Subfield 1: Call Connect Amount

If PDS 0658 is present, subfield 1 must be numeric and contain the connect
amount of the call, and may be all zeros.
Subfield 2: Call Connect Amount Exponent

Subfield 3: Call Connect Amount Sign

Value Description
D Call connect amount is a debit
C Call connect amount is a credit
Values
PDS 0658, Call Connect Amount must be a fixed length of 14.

PDS 0659—Other Description
PDS 0659—Other Description

Other Description (PDS 0659) contains additional descriptive information
related to the Telephony Billing information.
Attributes
ans…60; TAGLLLVAR
Tag Field: 0659

Subfields: none
Justification: n/a
Usage
messages:
Usage
Values
PDS 0659, Other Description must be a minimum length of 001 and a
maximum length of 060 if present. If present, PDS 0659 must be left justified

PDS 0663—Free-Form Description
PDS 0663—Free-Form Description

Free-Form Description (PDS 0663) is free-form description information the
Association assigns as needed.
Attributes
Tag Field: 0663
Subfields: none
Justification: left
Usage
messages:
Usage
This PDS supports data related to new programs and services the Corporation
introduces that involve corporate cards and require the presence of data not
available in the First Presentment/1240.
Values
If present, PDS 0663 Free-Form Description must be left-justified, and cannot

PDS 0670—Payer Name or User ID
PDS 0670—Payer Name or User ID

Payer Name or User ID (PDS 0670) provides the full last name, first name, and
middle initial of the payer (buyer of goods).
Attributes
ans…24; TAGLLLVAR
Tag Field: 0670
Subfields: none
Justification: left
Usage
messages:
Usage
Values
If present, PDS 0670 must be left justified and cannot be all spaces.

PDS 0671—Date of Funds Requested
PDS 0671—Date of Funds Requested

Date of Funds Requested (PDS 0671) provides the date the recipient (seller of
goods) requested receipt of funds.
Attributes
n-6; TAGLLL
Tag Field: 0671
Subfields: none
Justification: n/a
Usage
messages:
Usage
Values

PDS 0672—Recipient Name (Seller)
PDS 0672—Recipient Name (Seller)

Recipient Name (Seller) (PDS 0672) provides the name of the recipient of the
funds (seller).
Attributes
ans…24 TAGLLLVAR
Tag Field: 0672
Subfields: none
Justification: left
Usage
messages:
Usage
Values

PDS 0673—Date of Anticipated Receipt of Funds
PDS 0673—Date of Anticipated Receipt of Funds

Date of Anticipated Receipt of Funds (PDS 0673) provides the date of the
anticipated receipt of funds by the recipient (Seller).
Attributes
n–6; TAGLLL
Tag Field: 0673
Subfields: none
Justification: n/a
Usage
messages:
Usage
Values

PDS 0674—Additional Trace/Reference Number Used by Card Acceptor
PDS 0674—Additional Trace/Reference Number Used by

Card Acceptor
Additional Trace/Reference Number Used by Card Acceptor (PDS 0674)
provides additional trace and/or reference number information supplied by the
card acceptor (merchant).
Attributes
ans…15; TAGLLLVAR
Tag Field: 0674
Subfields: none
Justification: left
Usage
messages:
Usage
Values

PDS 0675—Additional Transaction Description Data
PDS 0675—Additional Transaction Description Data

Additional Transaction Description Data (PDS 0675) provides additional data
that the card acceptor might want to provide.
Attributes
ans…15; TAGLLLVAR
Tag Field: 0675
Subfields: none
Justification: left
Usage
messages:
Usage
Values

PDS 0676—Card Acceptor VAT Number
PDS 0676—Card Acceptor VAT Number

Card Acceptor VAT Number (PDS 0676) provides the value-added tax (VAT)
number for the card acceptor location used to identify the card acceptor when
collecting and reporting taxes.
Attributes
ans…20; TAGLLLVAR
Tag Field: 0676

Subfields: none
Justification: left
Usage
messages:
Usage
Requirements)/1644
Values

PDS 0677—Customer VAT Number
PDS 0677—Customer VAT Number

Customer VAT Number (PDS 0677) provides the value-added tax (VAT)
number for the customer used to identify the customer when purchasing
goods and services from a card acceptor.
Attributes
ans…20; TAGLLLVAR
Tag Field: 0677

Subfields: none
Justification: left
Usage
messages:
Usage
Requirements)/1644
Values

PDS 0678—Unique Invoice Number
PDS 0678—Unique Invoice Number

Unique Invoice Number (PDS 0678) provides the unique number associated
with the individual transaction provided by the card acceptor.
Attributes
ans…17; TAGLLLVAR
Tag Field: 0678
Subfields: none
Justification: left
Usage
messages:
Usage
Requirements)/1644
Values

PDS 0679—Commodity Code

Commodity Code (PDS 0679) provides the identifier assigned by the card
acceptor that best categorizes the items being purchased in a standardized
commodity group.
Attributes
ans…15; TAGLLLVAR
Tag Field: 0679

Subfields: none
Justification: left
Usage
messages:
Usage
Requirements)/1644
Information)/1644

Values

PDS 0680—Authorized Contact Name
PDS 0680—Authorized Contact Name

Authorized Contact Name (PDS 0680) provides the name of an individual or
company contacted for company authorized purchases.
Attributes
ans…36; TAGLLLVAR
Tag Field: 0680
Subfields: none
Justification: left
Usage
messages:
Usage
Requirements)/1644
Values

PDS 0681—Authorized Contact Phone
PDS 0681—Authorized Contact Phone

Authorized Contact Phone (PDS 0681) provides the phone number of an
individual or company contacted for company authorized purchases.
Attributes
ans…17; TAGLLLVAR
Tag Field: 0681
Subfields: none
Justification: left
Usage
messages:
Usage
Requirements)/1644
Values

PDS 0682—Detail Tax Amount 1

Detail Tax Amount 1 (PDS 0682) provides additional tax information such as
tax rate, tax amounts, and tax type.
Attributes
ans…46; TAGLLLVAR
Tag Field: 0682
Subfields: 8
Usage
messages:
Usage
Financial Detail Addendum (Passenger Transport Detail—General
Financial Detail Addendum (Passenger Transport Detail—Trip Leg
Data)/1644

Usage

Usage
Financial Detail Addendum (Telephony Billing—Summary)/1644
Financial Detail Addendum (Telephony Billing—Detail)/1644

Usage
Requirements)/1644
Information)/1644

Usage
Subfields
This PDS consists of eight subfields as defined in the following table:

1 1 Detail Tax Amount Indicator 1 ans-1 n/a
2 2–13 Detail Tax Amount 1 n-12 right
3 14–18 Detail Tax Rate 1 n-5 right
4 19 Detail Tax Rate Exponent 1 n-1 n/a
5 20–23 Detail Tax Type Applied 1 ans-4 left
6 24–25 Detail Tax Type Identifier 1 ans-2 left
7 26–45 Card Acceptor Tax ID 1 ans–20 left
8 46 Detail Tax Amount Sign 1 a–1 n/a
Subfield 1 Detail Tax Amount Indicator 1

This subfield is the indicator used to reflect additional tax capture and
reporting. Must be one of the following values:
Value Description
Y Tax included in total purchase amount
N Tax not included in total purchase amount
spaces Not supported
Subfield 2 Detail Tax Amount 1

This subfield indicates the detailed tax amount on the purchased goods or
services. This subfield must be numeric and may contain all zeros.
Subfield 3 Detail Tax Rate 1

This subfield indicates the detailed tax rate applied in relationship to a specific
tax amount. This subfield must be numeric and may contain all zeros.

Subfield 4 Detail Tax Rate Exponent 1

This subfield indicates the decimal location for the Detail Tax Rate in subfield
3. It must contain a value in the range of 0–5.
For a tax rate less than 100%, the exponent must indicate that the value is less
than 1. For example:
Subfield 3 Tax Rate Subfield 4 Tax Rate Exponent Interpretation

09000 5 0.09000 (9% tax rate)
00009 2 0.09 (9% tax rate)
09000 3 9.000 (900% tax rate)
00009 1 0.9 (90% tax rate)
00009 3 0.009 (0.9% tax rate)
Subfield 5 Detail Tax Type Applied 1

This subfield provides an indicator that is used to further define tax categories
applicable to specific domestic processing arrangements in certain locations.

Subfield 6 Detail Tax Type Identifier 1

This subfield indicates the type of tax collected in relationship to a specific tax
amount. Must be one of the following values:
Value Description
00 Unknown
01 Federal/National Sales Tax
02 State Sales Tax
03 City Sales Tax
04 Local Sales Tax
05 Municipal Sales Tax
06 Other Tax
10 Value Added Tax (VAT)
11 Goods and Services Tax (GST)
12 Provincial Sales Tax (PST)
20 Room Tax
21 Occupancy Tax
22 Energy Tax
space Not supported
Subfield 7 Card Acceptor Tax ID 1

This subfield provides an identification number used by the card acceptor with
the tax authority in relationship to a specific tax amount.
If present, this subfield must be 20 positions, be left justified and cannot

contain all low-values, all high-values, or all spaces. In addition, if this
subfield is present and the related First Presentment is a U.S. acquired
transaction, this subfield must consist of 9 numeric characters followed by
eleven spaces.

Subfield 8: Detail Tax Amount Sign 1

Value Description
D Detail tax amount is a debit
C Detail tax amount is a credit


Attributes
ans…46; TAGLLLVAR
Tag Field: 0683
Subfields: 8
Usage
messages:
Usage
Data)/1644

Usage
s1 Tax Amount Indicator 2 O • C
s2 Tax Amount 2 O • C
s3 Tax Rate 2 O • C
s4 Tax Rate Exponent 2 O • C
s5 Tax Type Applied 2 O • C
s6 Tax Type Identifier 2 O • C
s1 Tax Amount Indicator 2 O • C
s2 Tax Amount 2 O • C
s3 Tax Rate 2 O • C
s4 Tax Rate Exponent 2 O • C
s5 Tax Type Applied 2 O • C
s6 Tax Type Identifier 2 O • C

Usage

Usage
Requirements)/1644
Information)/1644

Usage
Subfields

8 46 Detail Tax Amount Sign 2 a-1 n/a

Value Description
space Not supported


This subfield indicates the tax rate applied in relationship to a specific tax
amount. This subfield must be numeric and may contain all zeros.


This subfield indicates the decimal location for the Tax Rate 4 subfield. It must
contain a value in the range of 0–5.

09000 5 0.09000 (9% tax rate)
00009 2 0.09 (9% tax rate)
09000 3 9.000 (900% tax rate)
00009 1 0.9 (90% tax rate)
00009 3 0.009 (0.9% tax rate)



Value Description
00 Unknown
02 State Sales Tax
03 City Sales Tax
04 Local Sales Tax
06 Other Tax
20 Room Tax
21 Occupancy Tax
22 Energy Tax
space Not supported

If present, PDS 0683, subfield 7 must be 20 positions, be left justified and

cannot contain all low-values, all high-values, or all spaces.
In addition, if this subfield is present and the related First Presentment is a U.S.
acquired transaction, this subfield must consist of 9 numeric characters
followed by eleven spaces.

Subfield 8 Detail Tax Amount Sign 2

Value Description
D Detail tax amount sign is a debit
C Detail tax amount sign is a credit


Attributes
ans…46; TAGLLLVAR
Tag Field: 0684
Subfields: 8
Usage
messages:
Usage
Data)/1644

Usage

Usage

Usage
Requirements)/1644
Information)/1644

Usage
Subfields


Value Description
spaces Not supported

This subfield indicates the tax amount on the purchased goods or services.
This subfield must be numeric and may contain all zeros.




09000 5 0.09000 (9% tax rate)
00009 2 0.09 (9% tax rate)
09000 3 9.000 (900% tax rate)
00009 1 0.9 (90% tax rate)
00009 3 0.009 (0.9% tax rate)



Value Description
00 Unknown
02 State Sales Tax
03 City Sales Tax
04 Local Sales Tax
06 Other Tax
20 Room Tax
21 Occupancy Tax
22 Energy Tax
space Not supported

If present, PDS 0684, subfield 7 must be 20 positions, be left justified and

cannot contain all low-values, all high-values, or all spaces.


Value Description
D Detail tax amount sign 3 is a debit
C Detail tax amount sign 3 is a credit

PDS 0685—Type of Supply
PDS 0685—Type of Supply

Type of Supply (PDS 0685) provides the indicator noting whether the purchase
is categorized as goods or services.
Attributes
an-2; TAGLLL
Tag Field: 0685
Subfields: none
Justification: left
Usage
messages:
Usage
Values
If present, this PDS must be one of the following values:
Value Description
00 Goods
01 Services

PDS 0686—Tax Exempt Indicator

Tax Exempt Indicator (PDS 0686) provides the indicator noting whether the
goods or services were tax exempt.
Attributes
an-1; TAGLLL
Tag Field: 0686
Subfields: none
Justification: none
Usage
messages:
Usage
Financial Detail Addendum (Passenger Transport Detail–General O • C
Requirements)/1644
Information)/1644


Values
If present, this PDS must be one of the following values:
Value Description
0 Not applicable
1 Tax Exempt

PDS 0687—Unique VAT Invoice Reference Number
PDS 0687—Unique VAT Invoice Reference Number

Unique VAT Invoice Reference Number (PDS 0687) provides an additional
subelement that is used to identify the value-added tax (VAT) invoice or tax
receipt.
Attributes
ans…17; TAGLLLVAR
Tag Field: 0687

Subfields: none
Justification: left
Usage
messages:
Usage
Values
If present, this PDS must be left justified and cannot contain all spaces.

PDS 0689—Corporate Identifier
PDS 0689—Corporate Identifier

Corporate Identifier (PDS 0689) provides the unique identifier of the
corporation or entity renting the vehicle.
Attributes
ans…12; TAGLLLVAR
Tag Field: 0689
Subfields: none
Justification: left
Usage
messages:
Usage

PDS 0690—No Show Indicator
PDS 0690—No Show Indicator

No Show Indicator (PDS 0690) provides an indicator noting that the individual
did not show up after making a reservation for a vehicle or lodging.
Attributes
an-1; TAGLLL
Tag Field: 0690
Subfields: none
Justification: none
Usage
messages:
Usage
Values
If present, this PDS must contain one of the following values:
Value Description
0 Not applicable
1 No-Show transaction amount due

PDS 0691—Days Rented
PDS 0691—Days Rented

Days Rented (PDS 0691) provides the number of days that, the vehicle was
rented.
Attributes
n-4; TAGLLL
Tag Field: 0691
Subfields: none
Usage
messages:
Usage

Values
If present, this PDS must be numeric and may contain all zeros.

PDS 0692—Weekly Rental Amount
PDS 0692—Weekly Rental Amount

Weekly Rental Amount (PDS 0692) provides the amount charged for a
seven-day rental period.
Attributes
n-12; TAGLLL
Tag Field: 0692
Subfields: none
Usage
messages:
Usage
Values

PDS 0693—Total Authorized Amount

Total Authorized Amount (PDS 0693) provides the amount reserved on a credit
card to cover the anticipated charges associated with the rental of a vehicle or
lodging stay.
Attributes
ans-14; TAGLLL
Tag Field: 0693

Subfields: 3
Usage
messages:
Usage

Subfields

1 1–12 Total Authorized Amount n–12 right
2 13 Total Authorized Amount Exponent n-1 n/a
3 14 Total Authorized Amount Sign a–1 n/a
Subfield 1: Total Authorized Amount

If PDS 0693 is present, subfield 1 must be numeric and contain the total
authorized amount reserved on the card. May contain all zeros.
Subfield 2: Total Authorized Amount Exponent

Subfield 3: Total Authorized Amount Sign

Value Description
D Total authorized amount is a debit
C Total authorized amount Sign is a credit
Values
If present, PDS 0693 Total Authorized Amount must be a fixed length of 014.

PDS 0694—One Way Drop Off Charge
PDS 0694—One Way Drop Off Charge

One Way Drop Off Charge (PDS 0694) provides a charge associated with not
returning a vehicle to the original rental location.
Attributes
n-12; TAGLLL
Tag Field: 0694
Subfields: none
Usage
messages:
Usage
Values

PDS 0695—Regular Mileage Charge
PDS 0695—Regular Mileage Charge

Regular Mileage Charge (PDS 0695) provides the amount charged for regular
miles traveled during vehicle rental.
Attributes
n-12; TAGLLL
Tag Field: 0695
Subfields: none
Usage
messages:
Usage
Values

PDS 0696—Extra Mileage Charge
PDS 0696—Extra Mileage Charge

Extra Mileage Charge (PDS 0696) provides the amount charged for miles
exceeding maximum allowed miles traveled during vehicle rental.
Attributes
n-12; TAGLLL
Tag Field: 0696
Subfields: none
Usage
messages:
Usage
Values

PDS 0697—Late Charge
PDS 0697—Late Charge

Late Charge (PDS 0697) provides the amount charged for returning a vehicle
after its anticipated date of return.
Attributes
n-12; TAGLLL
Tag Field: 0697
Subfields: none
Usage
messages:
Usage
Values

PDS 0698—Fuel Charge
PDS 0698—Fuel Charge

Fuel Charge (PDS 0698) provides the amount charged for fuel used during
vehicle rental.
Attributes
n-12; TAGLLL
Tag Field: 0698
Subfields: none
Usage
messages:
Usage
Values

PDS 0699—Lodging Total Tax Amount

Lodging Total Tax Amount (PDS 0699) provides the total taxes paid during a
lodging stay.
Attributes
ans-14; TAGLLL
Tag Field: 0699
Subfields: 3
Usage
messages:
Usage
s1 Lodging Total Tax Amount O • C
s2 Lodging Total Tax Amount Exponent O • C
s3 Lodging Total Tax Amount Sign O • C
Subfields

1 1–12 Lodging Total Tax Amount n–12 right
2 13 Lodging Total Tax Amount Exponent n-1 n/a
3 14 Lodging Total Tax Amount Sign a–1 n/a

Subfield 1: Lodging Total Tax Amount

amount of taxes related to the lodging stay. May contain all zeros.
Subfield 2: Lodging Total Tax Amount Exponent

Subfield 3: Lodging Total Tax Amount Sign

Value Description
D Lodging total tax amount is a debit
C Lodging total tax amount is a credit
Values
If present, PDS 0699, Lodging Total Tax Amount must be a fixed length of 014.

PDS 0700—Towing Charges
PDS 0700—Towing Charges

Towing Charges (PDS 0700) provides the amount charged to tow the rental
vehicle.
Attributes
n-12; TAGLLL
Tag Field: 0700
Subfields: none
Usage
messages:
Usage
Values

PDS 0701—Extra Charges
PDS 0701—Extra Charges

Extra Charges (PDS 0701) provides the extra charges associated with the
vehicle rental.
Attributes
n-12; TAGLLL
Tag Field: 0701
Subfields: none
Usage
messages:
Usage
Values

PDS 0702—Other Charges
PDS 0702—Other Charges

Other Charges (PDS 0702) provides the other charges associated with the
vehicle rental.
Attributes
n-12; TAGLLL
Tag Field: 0702
Subfields: none
Usage
messages:
Usage
Values

PDS 0703—Total Room Nights
PDS 0703—Total Room Nights

Total Room Nights (PDS 0703) provides the total number of nights for which a
room was contracted during a lodging stay.
Attributes
n-4; TAGLLL
Tag Field: 0703
Subfields: none
Usage
messages:
Usage

Values

PDS 0704—Prepaid Expenses

Prepaid Expenses (PDS 0704) provides the amount of deposit or other prepaid
amounts for the lodging stay.
Attributes
ans-14; TAGLLL
Tag Field: 0704
Subfields: 3
Usage
messages:
Usage
s1 Prepaid Expenses Amount O • C
s2 Prepaid Expenses Amount Exponent O • C
s3 Prepaid Expenses Amount Sign O • C
Subfields

1 1–12 Prepaid Expenses Amount n–12 right
2 13 Prepaid Expenses Amount Exponent n-1 n/a
3 14 Prepaid Expenses Amount Sign a–1 n/a

Subfield 1: Prepaid Expenses Amount

amount of the deposit or other prepaid expenses. May contain all zeros.
Subfield 2: Prepaid Expenses Amount Exponent

Subfield 3: Prepaid Expenses Amount Sign

Value Description
D Prepaid expenses amount is a debit
C Prepaid expenses amount is a credit
Values
If present, PDS 0704 Prepaid Expenses must be a fixed length of 014.

PDS 0705—Total Non-Room Tax Amount

Total Non-Room Tax Amount (PDS 0705) provides the total amount of taxes
for all items not specifically associated with the room rental during the lodging
stay.
Attributes
ans-14; TAGLLL
Tag Field: 0705

Subfields: 3
Usage
messages:
Usage
s1 Total Non-Room Tax Amount O • C
s2 Total Non-Room Tax Amount Exponent O • C
s3 Total Non-Room Tax Amount Sign O • C

Subfields

1 1–12 Total Non-Room Tax Amount n–12 right
2 13 Total Non-Room Tax Amount n-1 n/a
Exponent
3 14 Total Non-Room Tax Amount Sign a–1 n/a
Subfield 1: Total Non-Room Tax Amount

charges for total non-room tax. May contain all zeros.
Subfield 2: Total Non-Room Tax Amount Exponent

Subfield 3: Total Non-Room Tax Amount Sign

Value Description
D Total non-room tax amount is a debit
C Total non-room tax amount is a credit
Values
If present, PDS 0705, Total Non-Room Tax Amount must be a fixed length of
014.

PDS 0706—Cash Advances

Cash Advances (PDS 0706) provides the amount of cash received during the
lodging stay.
Attributes
ans-14; TAGLLL
Tag Field: 0706
Subfields: 3
Usage
messages:
Usage
s1 Cash Advance Amount O • C
s2 Cash Advance Exponent O • C
s3 Cash Advance Sign O • C
Subfields

1 1–12 Cash Advance Amount n–12 right
2 13 Cash Advance Exponent n-1 n/a
3 14 Cash Advance Sign a–1 n/a

Subfield 1: Cash Advance Amount

amount of the cash advance. May contain all zeros.
Subfield 2: Cash Advance Exponent

Subfield 3: Cash Advance Sign

Value Description
D Cash advance amount is a debit
C Cash advance amount is a credit
Values
If present, PDS 0706, Cash Advances must be a fixed length of 014.

PDS 0707—Valet Charges

Valet Charges (PDS 0707) provides the charges associated with the use of valet
services.
Attributes
ans-14; TAGLLL
Tag Field: 0707
Subfields: 3
Usage
messages:
Usage
s1 Valet Charges Amount O • C
s2 Valet Charges Exponent O • C
s3 Valet Charges Sign O • C
Subfields

1 1–12 Valet Charges Amount n–12 right
2 13 Valet Charges Exponent n-1 n/a
3 14 Valet Charges Sign a–1 n/a

Subfield 1: Valet Charges Amount

amount of the valet charges. May contain all zeros.
Subfield 2: Valet Charges Exponent

Subfield 3: Valet Charges Sign

Value Description
D Valet charges amount is a debit
C Valet charges amount is a credit
Values
If present, PDS 0707, Valet Charges must be a fixed length of 014.

PDS 0708—Movie Charges

Movie Charges (PDS 0708) provides the amount charged for in-room movies.
Attributes
ans-14; TAGLLL
Tag Field: 0708

Subfields: 3
Usage
messages:
Usage
s1 Movie Charges Amount O • C
s2 Movie Charges Exponent O • C
s3 Movie Charges Sign O • C
Subfields

1 1–12 Movie Charges Amount n–12 right
2 13 Movie Charges Exponent n-1 n/a
3 14 Movie Charges Sign a–1 n/a

Subfield 1: Movie Charges Amount

amount of the movie charges. May contain all zeros.
Subfield 2: Movie Charges Exponent

Subfield 3: Movie Charges Sign

Value Description
D Movie charges amount is a debit
C Movie charges amount is a credit
Values
If present, PDS 0708, Movie Charges must be a fixed length of 014.

PDS 0709—Business Center Charges

Business Center Charges (PDS 0709) provides the amount charged for business
center use and supplies.
Attributes
ans-14; TAGLLL
Tag Field: 0709
Subfields: 3
Justification: see “Subfield”
Usage
messages:
Usage
s1 Business Center Charges Amount O • C
s2 Business Center Charges Exponent O • C
s3 Business Center Charges Sign O • C
Subfields

1 1–12 Business Center Charges Amount n–12 right
2 13 Business Center Charges Exponent n-1 n/a
3 14 Business Center Charges Sign a–1 n/a

Subfield 1: Business Center Charges Amount

amount of the business center charges. May contain all zeros.
Subfield 2: Business Center Charges Exponent

Subfield 3: Business Center Charges Sign

Value Description
D Business center charges amount is a debit
C Business center charges amount is a credit
Values
If present, PDS 0709, Business Center Charges must be a fixed length of 014.

PDS 0710—Health Club Charges

Health Club Charges (PDS 0710) provides the amount charged for health club
use and supplies.
Attributes
ans-14; TAGLLL
Tag Field: 0710
Subfields: 3
Usage
messages:
Usage
s1 Health Club Charges Amount O • C
s2 Health Club Charges Exponent O • C
s3 Health Club Charges Sign O • C

Subfields

1 1–12 Health Club Charges Amount n–12 right
2 13 Health Club Charges Exponent n-1 n/a
3 14 Health Club Charges Sign a–1 n/a
Subfield 1: Health Club Charges Amount

amount of the health club charges. May contain all zeros.
Subfield 2: Health Club Charges Exponent

Subfield 3: Health Club Charges Sign

Value Description
D Health club charges amount is a debit
C Health club charges amount is a credit
Values
If present, PDS 0710, Health Club Charges must be a fixed length of 014.

PDS 0711—Fire Safety Act Indicator
PDS 0711—Fire Safety Act Indicator

Fire Safety Act Indicator (PDS 0711) identifies that the facility is in compliance
with the Hotel and Motel Fire Safety Act of 1990 (PL101-391), or similar
legislation.
Attributes
an-1; TAGLLL
Tag Field: 0711

Subfields: none
Justification: none
Usage
messages:
Usage

Values
If present, this PDS must contain one of the following values.
Value Description
Y In compliance with Fire Safety Act
N Not in compliance with Fire Safety Act

PDS 0712—Net Fuel Price

Net Fuel Price (PDS 0712) indicates the price of fuel net of any taxes.
Attributes
n-13; TAGLLL
Tag Field: 0712

Subfields: 2
Usage
messages:
Usage
Information)/1644
s1 Net Fuel Price O • C
s2 Net Fuel Price Exponent O • C
Subfields

1 1–12 Net Fuel Price n-12 right
2 13 Net Fuel Price Exponent n-1 n/a

Subfield 1 Net Fuel Price

This subfield provides the price of fuel net of any taxes. May contain all zeros.
Subfield 2 Net Fuel Price Exponent

This subfield indicates the decimal location for the Net Fuel Price subfield.
The Net Fuel Price Exponent must be a value in the range of 0–5.

PDS 0713—Restricted Ticket Indicator
PDS 0713—Restricted Ticket Indicator

Restricted Ticket Indicator (PDS 0713) provides the identifier noting that the
ticket purchased has some restriction associated with its use.
Attributes
an-1; TAGLLL
Tag Field: 0713
Subfields: none
Justification: none
Usage
messages:
Usage
Values
If present, this PDS must contain one of the following values.
Value Description
0 No restriction
1 Restricted ticket (non-refundable)

PDS 0714—Exchange Ticket Amount
PDS 0714—Exchange Ticket Amount

Exchange Ticket Amount (PDS 0714) provides the amount of the new ticket
purchase on an exchanged ticket.
Attributes
n-12; TAGLLL
Tag Field: 0714
Subfields: none
Usage
messages:
Usage
Values

PDS 0715—Exchange Fee Amount
PDS 0715—Exchange Fee Amount

Exchange Fee Amount (PDS 0715) indicates the fee paid to exchange the
ticket.
Attributes
n-12; TAGLLL
Tag Field: 0715
Subfields: none
Usage
messages:
Usage
Values

PDS 0716—Travel Authorization Code
PDS 0716—Travel Authorization Code

Travel Authorization Code (PDS 0716) indicates the code provided by the
company to a travel agent authorizing ticket issuance. Identified as Customer
File Reference Number in Airline Reporting Corporation (ARC) specifications.
Attributes
ans…64; TAGLLLVAR
Tag Field: 0716

Subfields: none
Justification: left
Usage
messages:
Usage
Values
If present, this PDS must be left-justified and cannot contain all spaces.

PDS 0717—IATA Client Code
PDS 0717—IATA Client Code

IATA Client Code (PDS 0717) provides the International Air Transport
Association (IATA) code identifying the company that purchased the ticket.
Attributes
ans…17; TAGLLLVAR
Tag Field: 0717
Subfields: none
Justification: left
Usage
messages:
Usage
Values
If present, this PDS must be left justified and cannot contain all spaces.

PDS 0718—Employee/Temp Name/ID
PDS 0718—Employee/Temp Name/ID

Employee/Temp Name/ID (PDS 0718) provides the name or ID associated
with the individual working in a temporary capacity..
Attributes
ans…40; TAGLLLVAR
Tag Field: 0718
Subfields: none
Justification: left
Usage
messages:
Usage
Values
If present, this PDS must be left justified and cannot contain all spaces or all
zeros.

PDS 0719—Employee Social Security Number or ID
PDS 0719—Employee Social Security Number or ID

Employee Social Security Number or ID (PDS 0719) contains the identifier
associated with the individual working in a temporary capacity.
Attributes
ans…30; TAGLLLVAR
Tag Field: 0719
Subfields: none
Justification: left
Usage
messages:
Usage
Values
zeros.

PDS 0720—Job Description
PDS 0720—Job Description

Job Description (PDS 0720) contains the description of the job or task of the
individual working in a temporary capacity..
Attributes
ans…40; TAGLLLVAR
Tag Field: 0720
Subfields: none
Justification: left
Usage
messages:
Usage
Values
zeros.

PDS 0721—Job Code
PDS 0721—Job Code

Job Code (PDS 0721) contains an indicator identifying the job or task of the
individual working in a temporary capacity.
Attributes
ans…20; TAGLLLVAR
Tag Field: 0721
Subfields: none
Justification: left
Usage
messages:
Usage
Values
zeros.

PDS 0722—Flat Rate Indicator
PDS 0722—Flat Rate Indicator

Flat Rate Indicator (PDS 0722) contains an indicator noting that the fee for the
individual working in a temporary capacity is a flat rate.
Attributes
ans-1; TAGLLL
Tag Field: 0722
Subfields: none
Justification: n/a
Usage
messages:
Usage
Values
If present, this PDS will show if the flat rate is applied. Valid value is Y or N.

PDS 0723—Regular Hours Worked

Regular Hours Worked (PDS 0723) contains the amount of time worked during
a normal operation for the task or job.
Attributes
n-7; TAGLLL
Tag Field: 0723
Subfields: 2
Usage
messages:
Usage
s1 Regular Hours Worked O • C
s2 Regular Hours Worked Exponent O • C
Subfields

1 1–6 Regular Hours Worked n-6 right
2 7 Regular Hours Worked Exponent n-1 right, valid
values 0–5

Subfield 1 Regular Hours Worked

This subfield provides the number of regular hours worked.
Subfield 2 Regular Hours Worked Exponent

This subfield indicates the decimal location for the Regular Hours Worked
subfield. The Regular Hours Worked Exponent must be a value in the range
of 0–5.
Values

PDS 0724—Regular Hours Rate

Regular Hours Rate (PDS 0724) contains the amount paid per regular hours
worked.
Attributes
n-7; TAGLLL
Tag Field: 0724
Subfields: 2
Usage
messages:
Usage
s1 Regular Hours Rate O • C
s2 Regular Hours Rate Exponent O • C
Subfields

1 1–6 Regular Hours Rate n-6 right
2 7 Regular Hours Rate Exponent n-1 right, valid
values 0–5

Subfield 1 Regular Hours Rate

This subfield provides the rate for the regular hours worked.
Subfield 2 Regular Hours Rate Exponent

This subfield indicates the decimal location for the Regular Hours Rate
subfield. The Regular Hours Rate Exponent must be a value in the range of
0–5.
Values

PDS 0725—Overtime Hours Worked

Overtime Hours Worked (PDS 0725) contains the number of hours worked in
excess of regular hours.
Attributes
n-7; TAGLLL
Tag Field: 0725
Subfields: 2
Usage
messages:
Usage
s1 Overtime Hours Worked O • C
s2 Overtime Hours Worked Exponent O • C
Subfields

1 1–6 Overtime Hours Worked n-6 right
2 7 Overtime Hours Worked Exponent n-1 right, valid
values 0–5

Subfield 1 Overtime Hours Worked

This subfield provides the number of overtime hours worked.
Subfield 2 Overtime Hours Worked Exponent

This subfield indicates the decimal location for the Overtime Hours Worked
subfield. The Overtime Hours Worked Exponent must be a value in the range
of 0–5.
Values

PDS 0726—Overtime Hours Rate

Overtime Hours Rate (PDS 0726) contains the amount paid per Overtime Hour
worked.
Attributes
n-7; TAGLLL
Tag Field: 0726
Subfields: 2
Usage
messages:
Usage
s1 Overtime Hours Rate O • C
s2 Overtime Hours Rate Exponent O • C
Subfields

1 1–6 Overtime Hours Rate n-6 right
2 7 Overtime Hours Rate Exponent n-1 right, valid
values 0–5

Subfield 1 Overtime Hours Rate

This subfield provides the rate for the overtime hours worked.
Subfield 2 Overtime Hours Rate Exponent

This subfield indicates the decimal location for the Overtime Hours Rate
subfield. The Overtime Hours Rate Exponent must be a value in the range of
0–5.
Values

PDS 0727—Temp Start Date
PDS 0727—Temp Start Date

Temp Start Date (PDS 0727) contains the date for the beginning of the pay
period.
Attributes
n-6; TAGLLL
Tag Field: 0727
Subfields: None
Usage
messages:
Usage
Values
If present, this PDS must be a valid date in the format YYMMDD.

PDS 0728—Temp Week Ending
PDS 0728—Temp Week Ending

Temp Week Ending (PDS 0728) contains the date of the end of the billing
cycle.
Attributes
n-6; TAGLLL
Tag Field: 0728
Subfields: none
Usage
messages:
Usage
Values
If present, this PDS must contain a valid date in the format YYMMDD.

PDS 0729—Requestor Name or ID
PDS 0729—Requestor Name or ID

Requestor Name or ID (PDS 0729) contains the name of the individual
requesting temporary services.
Attributes
ans…40; TAGLLLVAR
Tag Field: 0729
Subfields: none
Justification: left
Usage
messages:
Usage
Values
zeros.

PDS 0730—Supervisor/Reports to
PDS 0730—Supervisor/Reports to
Supervisor/Reports to (PDS 0730) contains the name of the individual
supervising the temporary staff.
Attributes
ans…40; TAGLLLVAR
Tag Field: 0730
Subfields: None
Justification: Left
Usage
messages:
Usage
Values
zeros.

PDS 0731—Time Sheet Number
PDS 0731—Time Sheet Number

Time Sheet Number (PDS 0731) contains the identification of the time sheet.
Attributes
ans…20; TAGLLLVAR
Tag Field: 0731
Subfields: None
Justification: Left
Usage
messages:
Usage
Values
zeros.

PDS 0732—Discount Amount

Discount Amount (PDS 0732) contains the amount and type of discount.
Attributes
ans-18; TAGLLL
Tag Field: 0732
Subfields: 4
Usage
messages:
Usage
Requirements)/1644

Subfields

1 1–12 Discount Amount n–12 right
2 13 Discount Amount Exponent n-1 n/a
3 14 Discount Amount Sign a–1 n/a
4 15–18 Discount Type ans–4 left
Subfield 1: Discount Amount

If PDS 0732 is present, subfield 1 must be numeric and contain the discount
amount. May contain all zeros.
Subfield 2: Discount Amount Exponent

Subfield 3: Discount Amount Sign

Value Description
D Discount amount is a debit
C Discount amount is a credit
Subfield 4: Discount Type

If PDS 0732 is present, subfield 4 contains the type of discount. If present, it
must be left-justified and cannot contain all low-values, all high-values, all
spaces, or all zeros.
Values
If present, PDS 0732, Discount Amount must be a fixed length of 018.

PDS 0733—Subtotal Amount

Subtotal Amount (PDS 0733) provides a subtotal of amounts associated with
the services.
Attributes
ans-14; TAGLLL
Tag Field: 0733
Subfields: 3
Usage
messages:
Usage
s1 Subtotal Amount O • C
s2 Subtotal Amount Exponent O • C
s3 Subtotal Amount Sign O • C

Subfields

1 1–12 Subtotal Amount n–12 right
2 13 Subtotal Amount Exponent n-1 n/a
3 14 Subtotal Amount Sign a–1 n/a
Subfield 1: Subtotal Amount

If PDS 0733 is present, subfield 1 must be numeric and may contain all zeros.
Subfield 2: Subtotal Amount Exponent

Subfield 3: Subtotal Amount Sign

Value Description
D Subtotal amount is a debit
C Subtotal amount is a credit
Values
If present, PDS 0733, Subtotal Amount must be a fixed length of 014.

PDS 0734—Miscellaneous Expenses

Miscellaneous Expenses (PDS 0734) provides a description and an amount for
miscellaneous expenses.
Attributes
Tag Field: 0734
Subfields: 4 subfields for each Miscellaneous Expenses
Occurrences: 1–4
Usage
messages:
Usage
s1 Miscellaneous Expenses Description O • C
s2 Miscellaneous Expenses Amount O • C
s3 Miscellaneous Expenses Amount Exponent O • C
s4 Miscellaneous Expenses Amount Sign O • C

Usage
Financial Detail Addendum (Telephony Billing–Detail)/1644 O • C
This PDS allows the sender to provide 1–4 different miscellaneous expenses.
For each different miscellaneous expense provided, subfields 1 and 2 must be
present. These subfields provide the description and amount of each
miscellaneous expense.
Subfields
This PDS may contain from one to four occurrences of Miscellaneous Expense
data. Each occurrence consists of four subfields as defined in the following
table. Each occurrence requires 54 positions; the length of this PDS must be a

1 1–40 Miscellaneous Expense Description ans-40 left
2 41–52 Miscellaneous Expense Amount n-12 right
3 53 Miscellaneous Expenses Amount n–1 n/a
Exponent
4 54 Miscellaneous Expenses Amount a–1 n/a
Sign
Subfield 1 Miscellaneous Expense Description

This subfield provides the description for any miscellaneous expenses. If
present, this PDS must be 40 positions, be left justified with trailing spaces, and
cannot contain all spaces or all zeros.

Subfield 2 Miscellaneous Expense Amount

This subfield indicates the amount of any miscellaneous expenses. If present,
it must contain numeric data. May contain all zeros.
Subfield 3 Miscellaneous Expense Amount Exponent

If present, this subfield must be numeric and contain a value of 0–5.
Subfield 4 Miscellaneous Expense Amount Sign

Value Description
D Miscellaneous expense amount is a debit
C Miscellaneous expense amount is a credit
Values
If present, PDS 0734 Miscellaneous Expenses must be within a minimum
length of 054 and a maximum length of 216, and must be divisible by a
minimum occurrence length of 054.

PDS 0735—Service Descriptor Codes
PDS 0735—Service Descriptor Codes

Service Descriptor Codes (PDS 0735) contains a card acceptor designated code
for the shipping service provided.
Attributes
ans…40; TAGLLLVAR
Tag Field: 0735
Subfields: none
Justification: left
Usage
messages:
Usage
Values
zeros.

PDS 0736—Tracking Number or Pickup Number
PDS 0736—Tracking Number or Pickup Number

Tracking Number or Pickup Number (PDS 0736) contains the identification
number for the package(s) being shipped for tracking and billing purposes.
Attributes
ans…40; TAGLLLVAR
Tag Field: 0736
Subfields: none
Justification: left
Usage
messages:
Usage
Values
zeros.

PDS 0737—Shipping Net Amounts

Shipping Net Amount (PDS 0737) provides the net amount of the shipping
costs.
Attributes
ans-14; TAGLLL
Tag Field: 0737
Subfields: 3
Usage
messages:
Usage
s1 Shipping Net Amount O • C
s2 Shipping Net Amount Exponent O • C
s3 Shipping Net Amount Sign O • C

Subfields

1 1–12 Shipping Net Amount n–12 right
2 13 Shipping Net Amount Exponent n-1 n/a
3 14 Shipping Net Amount Sign a–1 n/a
Subfield 1: Shipping Net Amount

If PDS 0737 is present, subfield 1 must be numeric and contains the total
shipping net amount. May contain all zeros.
Subfield 2: Shipping Net Amount Exponent

Subfield 3: Shipping Net Amount Sign

Value Description
D Shipping net amount is a debit
C Shipping net amount is a credit
Values
If present, PDS 0737, Shipping Net Amount must be a fixed length of 014.

PDS 0738—Incentive Amount

Incentive Amount (PDS 0738) provides the amount of the incentive.
Attributes
ans-14; TAGLLL
Tag Field: 0738
Subfields: 3
Usage
messages:
Usage
s1 Incentive Amount O • C
s2 Incentive Amount Exponent O • C
s3 Incentive Amount Sign O • C

Subfields

1 1–12 Incentive Amount n–12 right
2 13 Incentive Amount Exponent n-1 n/a
3 14 Incentive Amount Sign a–1 n/a
Subfield 1: Incentive Amount

If PDS 0738 is present, subfield 1 must be numeric and contains the total
incentive amount. May contain all zeros.
Subfield 2: Incentive Amount Exponent

Subfield 3: Incentive Amount Sign

Value Description
D Incentive amount is a debit
C Incentive amount is a credit
Values
If present, PDS 0738, Incentive Amount must be a fixed length of 014.

PDS 0739—Pickup Date
PDS 0739—Pickup Date

Pickup Date (PDS 0739) contains the date the package being shipped or sent
by courier is picked up.
Attributes
n-6; TAGLLL
Tag Field: 0739
Subfields: none
Usage
messages:
Usage
Values

PDS 0740—Delivery Date
PDS 0740—Delivery Date

Delivery Date (PDS 0740) contains the date of delivery for the packages being
shipped or sent by courier.
Attributes
n-6; TAGLLL
Tag Field: 0740
Subfields: none
Usage
messages:
Usage
Values

PDS 0741—Number of Packages
PDS 0741—Number of Packages

Number of Packages (PDS 0741) contains the total number of packages being
Attributes
n-6; TAGLLL
Tag Field: 0741
Subfields: none
Usage
messages:
Usage
Values

PDS 0742—Package Weight
PDS 0742—Package Weight

Package Weight (PDS 0742) contains the weight of each package being
Attributes
n-12; TAGLLL
Tag Field: 0742
Subfields: none
Usage
messages:
Usage
Values

PDS 0743—Unit of Measure
PDS 0743—Unit of Measure

Unit of Measure (PDS 0743) contains the identification associated with the type
of item being shipped.
Attributes
ans…3; TAGLLLVAR
Tag Field: 0743
Subfields: none
Justification: left
Usage
messages:
Usage
Values
zeros.

PDS 0744—Shipping Party Information

Shipping Party Information (PDS 0744) contains all of the address information
associated with the shipping party.
Attributes
Tag Field: 0744
1 subfield for each shipping party information
Occurrences 1–3
Usage
messages:
Usage
s1 Shipping Party Name O • C
This PDS allows the sender to provide 1–3 different shipping party names.

Subfields
This PDS consists of one subfield as defined in the following table:

1 1–50 Shipping Party Name ans-50 left
Subfield 1 Shipping Party Name

This subfield provides the name of the shipping party.
Values
zeros.

PDS 0745—Shipping Party Address

Shipping Party Address (PDS 0745) contains the address of the location from
where the package is being shipped or sent by courier.
Attributes
Tag Field: 0745
1 subfield for each shipping party address
Occurrence 1–6
Usage
messages:
Usage
s1 Shipping Party Address O • C
This PDS allows the sender to provide 1–6 different shipping party address
lines.

Subfields
This PDS consists of one subfield as defined in the following table:

1 1–50 Shipping Party Address ans-50 left
Subfield 1 Shipping Party Address

This subfield provides the address of the shipping party.
Values
zeros.

PDS 0746—Shipping Party Postal Information

Shipping Party Postal Information (PDS 0746) contains the postal information
of the party shipping or sending the package by courier.
Attributes
ans…41; TAGLLLVAR
Tag Field: 0746
Subfields: 4
Usage
messages:
Usage
s1 Shipping Party City O • C
s2 Shipping Party State/Province Code O • C
s3 Shipping Party Country Code O • C
s4 Shipping Party Postal Code O • C

Subfields

1 1–25 Shipping Party City ans-25 left
2 26–28 Shipping Party State/Province Code ans-3 left
3 29–31 Shipping Party Country Code ans–3 left
4 32–41 Shipping Party Postal Code ans–10 left
Subfield 1 Shipping Party City

This subfield identifies the city from where the package is shipped or sent by
courier. If present, must be left-justified and cannot contain all spaces or all
zeros.
Subfield 2 Shipping Party State/Province Code

This subfield identifies the state or province from where the package is
shipped or sent by courier. If present, must be left-justified and cannot
Subfield 3 Shipping Party Country Code

This subfield identifies the country from where the package is shipped or sent
by courier. If present, must be left-justified and cannot contain all spaces or all
zeros.
Subfield 4 Shipping Party Postal Code

This subfield contains the postal code from where the package is shipped or
sent by courier. If present, must be left-justified and cannot contain all spaces
or all zeros.
For transactions acquired in the U.S. region, Shipping Party Postal Code
(PDS 0746, subfield 4) must contain either five numeric characters, be left
justified, space filled, or the “ZIP+4” nine numeric characters with a hyphen
between the 5th and 6th numeric characters.

Values
zeros.

PDS 0747—Shipping Party Contact

Shipping Party Contact (PDS 0747) provides information about the
individual(s) identified as the shipping party. This information is typically not
address information.
Attributes
Tag Field: 0747
2 subfields for each shipping party contact
Occurrence 1–5
Usage
messages:
Usage
s1 Shipping Party Descriptor O • C
s2 Shipping Party Contact Information O • C
This PDS allows the sender to provide 1–5 different pieces of information
related to the shipping party contact. For each different piece of shipping
contact information provided, subfields 1 and 2 must be present. These
subfields describe the type of information and the actual data.

Subfields

1 1 Shipping Party Descriptor ans-1
2 2–61 Shipping Party Contact Information ans-60 left
Subfield 1 Shipping Party Descriptor

This subfield can occur 1–5 times and contains the following valid values:
Value Description
1 Name
2 Title
3 Telephone
4 e-mail address
5 Function
Subfield 2 Shipping Party Contact Information

This subfield can occur 1–5 times and contains the contact information about
the party shipping or sending a package by courier. It must be left-justified,
and cannot contain all spaces, or all zeros.
Values
If present, PDS 0747 must be a minimum length of 061 (one occurrence) or a
maximum length of 305 (five occurrences) and be divisible by the minimum
occurrence length of 61.

PDS 0748—Delivery Party Information

Delivery Party Information (PDS 0748) provides information about the party
receiving the package.
Attributes
Tag Field: 0748
1 subfield for each delivery party information
Occurrences 1–3
Usage
messages:
Usage
s1 Delivery Party Name O • C
This PDS allows the sender to provide 1–3 different delivery party names.

Subfields
This PDS consists of the following subfield defined in the following table:

1 1–50 Delivery Party Name ans-50 left
Subfield 1 Delivery Party Name

This subfield can occur 1–3 times. If subfield 1 is present, must be left-justified
and cannot contain all spaces or all zeros.
Values
zeros.

PDS 0749—Delivery Party Address Information

Delivery Party Address Information (PDS 0749) contains the address of the
location to which the package is being shipped to, or sent to, by courier.
Attributes
Tag Field: 0749
1 subfield for each Delivery Party Address
Occurrences 1–6
Usage
messages:
Usage
s1 Delivery Party Address O • C
This PDS allows the sender to provide 1–6 different delivery party address
lines.

Subfields
This PDS consists of the following subfield as defined in the following table:

1 1–50 Delivery Party Address ans-50 left
Subfield 1 Delivery Party Address

This subfield can occur 1–6 times. If present, must be left-justified and cannot
Values
zeros.

PDS 0750—Delivery Party Postal Information

Delivery Party Postal Information (PDS 0750) contains specific postal
information about the delivery destination.
Attributes
ans…41; TAGLLLVAR
Tag Field: 0750
Subfields: 4
Usage
messages:
Usage
s1 Delivery Party City O • C
s2 Delivery Party State/Province Code O • C
s3 Delivery Party Country Code O • C
s4 Delivery Party Postal Code O • C

Subfields
This PDS consists of the following four subfields as defined in the following
table:

1 1–25 Delivery Party City ans-25 left
2 26–28 Delivery Party State/Province Code ans–3 left
3 29–31 Delivery Party Country Code ans–3 Left
4 32–41 Delivery Party Postal Code ans–10 left
Subfield 1 Delivery Party City

This subfield identifies the city where the package is to be delivered.
Subfield 2 Delivery Party State/Province Code

This subfield identifies the state or province where the package is being
delivered.
Subfield 3 Delivery Party Country Code

This subfield identifies the country where the package is being delivered.
Subfield 4 Delivery Party Postal Code

This subfield contains the postal code where the package is being delivered.
For transactions acquired in the U.S. region, Delivery Party Postal Code
(PDS 0750, subfield 4) must contain either five numeric characters, be left
justified, space filled, or the “ZIP+4” 9 numeric characters with a hyphen
between the fifth and sixth numeric characters.
Values
If present, this PDS and each of its four subfields must be left justified and
cannot contain all spaces or all zeros.


Detail Tax Amount 4 (PDS 0751) contains the tax amount, tax rate, tax type
applied, and card acceptor tax ID.
Attributes
ans…46; TAGLLLVAR
Tag Field: 0751
Subfields: 8
Usage
messages:
Usage
Data)/1644

Usage

Usage

Usage
Requirements)/1644
Information)/1644

Usage
Subfields
This PDS consists of the following eight subfields as defined in the following
table:

2 2–13 Detail Tax Amount 4 n–12 right
3 14–18 Detail Tax Rate 4 n–5 right
4 19 Detail Tax Rate Exponent 4 n–1 n/a
5 20–23 Detail Tax Type Applied 4 ans–4 left
6 24–25 Detail Tax Type Identifier 4 ans–2 left

This subfield must contain one of the following values:
Value Description
Space Not supported


This subfield indicates the detailed amount on the purchased goods or

This subfield indicates the detailed tax rate applied in relationship to a specific
tax amount. This subfield must be numeric and may contain all zeros.

This subfield indicates the decimal location for the Detail Tax Rate 3 subfield.
It must contain a value in the range of 0–5.

09000 5 0.09000 (9% tax rate)
00009 2 0.09 (9% tax rate)
09000 3 9.000 (900% tax rate)
00009 1 0.9 (90% tax rate)
00009 3 0.009 (0.9% tax rate)



Value Description
00 Unknown
02 State Sales Tax
03 City Sales Tax
04 Local Sales Tax
06 Other Tax
11 Goods and Services (GST)
20 Room Tax
21 Occupancy Tax
22 Energy Tax
Space Not supported

If present, PDS 0751, subfield 7 must be a fixed length of 20. It must be left
justified, and cannot contain all low-values, all high-values, or all spaces.


If present, this subfield must have a valid value of D or C.
Value Description


Attributes
ans…46; TAGLLLVAR
Tag Field: 0752
Subfields: 8
Usage
messages:
Usage
Data)/1644

Usage

Usage

Usage
Requirements)/1644
Information)/1644

Usage
Subfields
table:



Value Description
Space Not supported




09000 5 0.09000 (9% tax rate)
00009 2 0.09 (9% tax rate)
09000 3 9.000 (900% tax rate)
00009 1 0.9 (90% tax rate)
00009 3 0.009 (0.9% tax rate)



Value Description
00 Unknown
02 State Sales Tax
03 City Sales Tax
04 Local Sales Tax
06 Other Tax
20 Room Tax
21 Occupancy Tax
22 Energy Tax
Space Not supported



Value Description


Attributes
ans…46; TAGLLLVAR
Tag Field: 0753
Subfields: 8
Usage
messages:
Usage

Usage
Data)/1644

Usage

Usage
Requirements)/1644
Information)/1644

Usage
Subfields
table:

8 46 Detail Tax Amount 6 a–1 n/a


Value Description
Space Not supported

This subfield indicates the tax amount on the purchased goods or services.
This subfield must be numeric and may contain all zeros.



09000 5 0.09000 (9% tax rate)
00009 2 0.09 (9% tax rate)
09000 3 9.000 (900% tax rate)
00009 1 0.9 (90% tax rate)
00009 3 0.009 (0.9% tax rate)



Value Description
00 Unknown
02 State Sales Tax
03 City Sales Tax
04 Local Sales Tax
06 Other Tax
20 Room Tax
21 Occupancy Tax
22 Energy Tax
Space Not supported



Value Description

PDS 0754—Delivery Party Contact

Delivery Party Contact (PDS 0754) contains information about the individual(s)
identified as the delivery party. This information is typically not address
information.
Attributes
Tag Field: 0754
2 subfields for each Delivery Party Contact
Occurrences 1–5
Usage
messages:
Usage
s1 Delivery Party Descriptor O • C
s2 Delivery Party Contact Information O • C
This PDS allows the sender to provide 1–5 different pieces of information
related to the delivery party contact. For each different piece of delivery
information provided, subfields 1 and 2 must be present. These subfields
describe the type of information and the actual data.

Subfields

1 1 Delivery Party Descriptor ans-1
2 2–61 Delivery Party Contact ans-60 left
Information
Subfield 1 Delivery Party Descriptor

This subfield can occur 1–5 times and contains the following valid values:
Value Description
1 Name
2 Title
3 Telephone
4 e-mail address
5 Function
Subfield 2 Delivery Party Contact Information

This subfield can occur 1–5 times, and contains the contact information about
the party delivering the package. It must be left-justified and cannot contain
all spaces or all zeros.
Values
If present, PDS 0754 must be a minimum length of 061 (one occurrence) or a
maximum length of 305 (five occurrences) and be divisible by the minimum
occurrence length of 61.

PDS 0755—Line Item Total Amount

Line Item Total Amount (PDS 0755) provides the total amount presented in the
line item detail message.
Attributes
ans-14; TAGLLL
Tag Field: 0755
Subfields: 3
Usage
messages:
Usage
s2 Line Item Total Amount Exponent O • C

Subfields

1 1–12 Line Item Total Amount n–12 right
2 13 Line Item Total Amount Exponent n-1 n/a
3 14 Line Item Total Amount Sign a–1 n/a
Subfield 1: Line Item Total Amount

If PDS 0755 is present, subfield 1 must be numeric and cannot contain all
zeros. It contains the line item total amount.
Subfield 2: Line Item Total Amount Exponent

Subfield 3: Line Item Total Amount Sign

Value Description
D Line item total amount is a debit
C Line item total amount is a credit
Values
When used in a Corporate Line Item Detail addendum message, PDS 0755
represents the sum of PDS 0647 Extended Item Amount, and PDS 0597 Total
Tax Amount.
When used in a Telephony Billing Summary message, PDS 0755 represents the
sum of PDS 0627, subfield 1 Billing Event Amount (occurs 1 to 10 times),
PDS 0628, subfield 1 Billing Event Amount 2 (occurs 1 to 10 times) and PDS
0597, subfield 1 Total Tax Amount (which is the sum of all six of the tax-
related PDSs).

When used in a Telephony Billing Detail addendum message, PDS 0755

represents the sum of PDS 0649, subfield 1 Call Usage Amount, PDS 0655,
subfield 1 Call Long Distance Amount, PDS 0658, subfield 1 Call Collect
Amount, PDS 0734, subfield 2 Miscellaneous Expense Amount and PDS 0597,
subfield 1 Total Tax Amount (which is the sum of all six of the tax-related
PDSs).

PDS 0799—Test Case Traceability Identifiers

Test Case Traceability Identifiers (PDS 0799) provides an audit trail for various
messages within a specified test transaction. This PDS is used for internal
MasterCard testing, as well as member testing.
Attributes
Tag Field: 0799

Subfields: 2 subfields for each Test Case occurrence
Occurrences: 1–5
Usage
messages:
Usage
s1 Auxiliary Field 1 O • •
File Trailer (Member-Generated)/1644 O • •
s1 Auxiliary Field 1 O • C

Usage
Data)/1644
Financial Detail Addendum (Electronic Invoice—Transaction O • C
Data)/1644
Financial Detail Addendum (Electronic Invoice—Party O • C
Information)/1644

Usage
Requirements)/1644
Information)/1644
Fee Collection (Other than Retrieval Fee Billing)/1740 O • C

This PDS contains 1–5 test case numbers. The transaction originator may
optionally provide it. Its purpose is to trace the associated message to 1-5
internal MasterCard or member test cases. This may assist the transaction
originator in evaluating test results. The IPM Pre-edit application retains this
PDS throughout its processing. GCMS removes this PDS from the message
before sending the message to the receiving member.
Subfields
This PDS may contain one to five test case traceability identifiers. Each
traceability identifier consists of two subfields as defined in the following table.
Each traceability identifier requires 33 positions; the maximum length of this
PDS is 165 positions. None of these subfields is optional, that is, all 33
positions must be provided for each occurrence.

1 1–8 Auxiliary Field 1 ans–8 left
An identifier for internal
MasterCard testing or member
testing
2 9–33 Auxiliary Field 2 ans–25 left
An identifier for internal
MasterCard testing or member
testing
Values
The transaction originator assigns PDS 0799 values.
If present, PDS 0799 Test Case Traceability Identifiers must be left justified and

PDS 1000–1099—Member-to-Member Proprietary Data

Member-to-Member Proprietary Data (PDS 10XX) contains 100 private data
subelements (1000–1099) used exclusively for reporting member-to-member
proprietary data. Members can use these PDSs to exchange information that is
not defined and captured in other elements, with other participating members.
These PDSs are reserved for member-to-member proprietary data. Members

that want to exchange data that is not defined in another data element or PDS
may agree to define the data between themselves and present it in one or
multiple PDSs in the 1000–1099 range.
Attributes
Tag Field: 10XX (1000-1099)
Subfields: none
Justification: none
Usage
messages:
Usage
O • C
Financial Detail Addendum (Passenger Transport Detail—Trip
O • C
Leg Data)/1644

Usage
O • C
Requirements)/1644
O • C
Information)/1644
Fee Collection (Other than Retrieval Fee Billing)/1740 O • C
Values
Members may choose one of two options in presenting member-to-member
proprietary data in their messages.
• Members that want to send or receive proprietary data, but would rather
use their own parsing routines to parse their data, may opt to use a single
PDS within the range of 1000–1099 and provide one string of up to 992
characters of data. With this option, members would provide a single PDS
tag (ID) and one length definition, followed by the data string. The
clearing system parsers will leave this member data intact.
• Members that want to send or receive proprietary data, but would like
MasterCard to parse the data, may opt to use up to 100 individual PDSs
within the range of 1000–1099 to define their data. Under this option,
members will need to use the normal “tag-length-data” PDS encoding
structure to define as many PDSs as they choose to use. This will provide
the clearing system parsers with the appropriate information to parse the
data for inbound and outbound messages. Members may provide up to an
overall total of 999 positions (including tags, lengths, and data for all PDSs
assigned within the range) per message.

Member-to-Member data in PDSs 1000–1099 may be presented in all messages

originated by members and may be included in any of the “Additional Data”
data elements (DE 48, DE 62, DE 123, DE 124, and DE 125).
The contents of a single or of multiple PDSs in the 1000–1099 range must be in

display format. The clearing system does not accommodate binary data in
these subelements.
PDS 1000-1099 Member-to-Member Proprietary Data cannot be all low-values

or all high-values.

A Institution ID Data Elements and PDSs
There are multiple institution ID data elements and private data subelements
(PDSs) defined in IPM messages and each has a specific function. They are
classified into financial or business institutions and technical institutions. This
appendix describes the relationship of these data elements and PDSs.
Financial or Business Institutions ...................................................................... A-1
Technical Institutions ......................................................................................... A-2
Additional Information ....................................................................................... A-3

IPM Clearing Formats • May 2004 A-i
Institution ID Data Elements and PDSs
Financial or Business Institutions
Financial or Business Institutions

These institutions have a financial relationship, business relationship, or both
with the card acceptor, cardholder, or with MasterCard. They do not
necessarily send and receive data. They consist of Acquiring Institution ID
Code (Data Element [DE] 32), Transaction Originator Institution ID Code
(DE 94), and Transaction Destination Institution ID Code (DE 93).
• DE 32—Acquirers assign DE 32 contents and the contents are not validated
against the clearing system member ID database. DE 32 is optional.
An acquirer may use DE 32 to subdivide its portfolio within its member ID
number. For example, one acquirer may assign a different DE 32 value to
each of its affiliate or agent institutions. Another acquirer may assign
DE 32 values based on geographic location.
The following diagram illustrates the relationship between the acquirer and
DE 32:
Acquiring
Member ID
(DE 93 or
DE 94)
DE 32 DE 32 DE 32
• DE 94—This institution has financial responsibility as the transaction

originator. It must be a principal member. DE 94 must contain a valid
member ID, such as an ICA number.
• DE 93—This institution has financial responsibility as the transaction
receiver. It must be a principal member. DE 93 must contain a valid
member ID, such as an ICA number.
Note If submitted, DE 93, and DE 94 must be a minimum of 6 digits long and a

maximum of 11 digits long. GCMS will reject clearing messages submitted with
a member ID less than six positions long.

IPM Clearing Formats • May 2004 A-1
Technical Institutions
The following diagram depicts the roles of institutions identified in DE 93 and

DE 94:
Institution Institution
Identified MasterCard Identified
in DE 94 in DE 93
Technical Institutions
These institutions are physically connected to the card acceptor, cardholder
data center, or with MasterCard. Their primary function is to send data,
receive data, or both. They do not necessarily have financial responsibility for
a transaction. They consist of Forwarding Institution ID Code (DE 33), and
Receiving Institution ID Code (DE 100).
• DE 33—This institution is physically connected to the clearing system. It is
usually a processor. The message originator populates DE 33 with the
member ID assigned to the member or processor that is physically
connected to the clearing system.
• DE 100—This institution is also physically connected to the clearing system.
Like DE 33, it is usually a processor. The clearing system populates
DE 100. It contains either the member ID of the institution that receives
transactions on the acquirer’s behalf (as the account range in positions 3–7
of the acquirer reference data [ARD] identifies), or the issuer’s behalf (as
the account range in the card account number identifies), whichever is
appropriate to the transaction.
Note If submitted, DE 33, and DE 100 must be a minimum of 6 digits long and a
maximum of 11 digits long. GCMS will reject clearing messages submitted with
a member ID less than six positions long.

A-2 May 2004 • IPM Clearing Formats
The following diagram further illustrates the technical relationship among these
data elements and PDSs:
Institution Institution
Identified MasterCard Identified
in DE 33 in DE 100
Card
Acceptor
Several of these data elements and PDSs may contain the same value. For
example, an acquirer that submits transactions directly to the clearing system
(as opposed to submitting them through a processor) may place the same
identifier in DE 32, DE 94, and DE 33.

IPM Clearing Formats • May 2004 A-3
B Printing Card Acceptor Information on
Cardholder Statements
This appendix describes the location of card acceptor information in various
financial messages. Issuers may use this information on cardholder statements.
Financial Transactions Used as Sources ............................................................ B-1
General Mapping Guidelines ............................................................................. B-2

U.S. Region Financial Transaction............................................................... B-2
Non-U.S. Region Financial Transaction....................................................... B-3
Transactions Acquired in Canada................................................................ B-4
Messages Involving Certain Transaction Types ................................................ B-5
Messages Involving Airline Transactions........................................................... B-6

U.S. Region Airlines ..................................................................................... B-6
Airlines Outside the U.S. Region ................................................................. B-8
Messages Involving QPS Transactions .............................................................. B-9
Messages Involving Supermarket Transactions............................................... B-11
Messages Involving Warehouse Club Transactions ........................................ B-12
Messages Involving Service Industries Transactions....................................... B-14
Messages Involving PH Transactions .............................................................. B-15
Messages Involving IFC Transactions.............................................................. B-17
Messages Involving Non–Face-To-Face Transactions..................................... B-18
Messages Involving Payment Transactions ..................................................... B-19

IPM Clearing Formats • May 2004 B-i
Printing Card Acceptor Information on Cardholder Statements
Financial Transactions Used as Sources
Financial Transactions Used as Sources

An issuer who wants to print a 40-position card acceptor description on the
cardholder statement must construct the description from several IPM data
elements and private data subelements (PDSs). When creating chargebacks,
the issuer must reverse this process to populate the appropriate IPM data
elements and PDSs, or return the original contents of DE 43 from the First
Presentment.
The guidelines in this appendix are recommendations on how to construct a

40-position card acceptor description from the following financial transactions
in the IPM format:
• Messages not involving credit card activated phone, Airline, Supermarket,
Service Industries, Quick Payment Service (QPS), Prestigious Hotels (PH),
In-flight Commerce (IFC), Non–Face-to-Face, transactions, or Payment
Transactions.
• Credit card activated phone transactions from cards issued outside the U.S.
region.
• Airline transactions
• QPS transactions
• Supermarket transactions
• Warehouse Club transactions
• Service Industries transactions
• PH transactions
• IFC transactions
• Non–Face-to-Face transactions
• Payment Transactions
If an issuer wants to exceed the 40-position length, it may append other card
acceptor description information provided in the IPM message at its discretion.
Note Web sites listed in this appendix are for example only and should not be
considered valid sites.

IPM Clearing Formats • May 2004 B-1
General Mapping Guidelines

Information in this subsection does not apply to the following transaction
types:
• Credit card-activated phone
• Airline
• Supermarket
• Warehouse Club
• Service Industries
• QPS
• PH
• IFC
• Non–Face-to-Face
The full card acceptor name/location information in Card Acceptor Name/

Location (Data Element [DE] 43), if provided, is available to issuers that choose
to use it. Issuers that choose not to use the full content of DE 43 may extract
the mandatory subfields from DE 43 and print them directly on the cardholder
statement. In this case, no truncation of subfields is necessary. Issuers must
construct cardholder statements as shown in the following examples when
extracting the 40-position card acceptor description from DE 43.
U.S. Region Financial Transaction

Assume an issuer wants to print a 40-position card acceptor description on the
cardholder statement. It is a U.S. region financial transaction. This issuer
receives a message with the following DE 43 contents:
subfield 1 2 3 4 5 6
ABC Electronics\123 Main Street\AnyCity\00000-0000NE USA

B-2 May 2004 • IPM Clearing Formats
From the contents the issuer extracts card acceptor description data for
placement on the cardholder statement as follows:

1–15 ABC Electronics Subfield 1—Card Acceptor Name—from DE 43, up
to the first backslash (\).
16–22 spaces Issuer inserts if Card Acceptor Name is less than
22 positions.
23 delimiter space Issuer inserts.
24–30 Any City Subfield 3—Card Acceptor City—from DE 43,
between the second and third backslash (\).
31–36 spaces Issuer inserts if Card Acceptor City is less than 13
positions.
38–40 NE Subfield 5—State, Province, or Region Code—from
DE 43, starting in the 11th position after the third
backslash (\) for three positions.
The following appears on the cardholder statement:
ABC Electronics AnyCity NE
Non-U.S. Region Financial Transaction

cardholder statement. It is a non-U.S. region financial transaction. The
following is all the data in DE 43:
ABC Electronics\123 Main Road\Mexico City\00000-0000OB MEX

From the contents, the issuer extracts card acceptor description data for
placement on the cardholder statement as follows:

1–15 ABC Electronics Subfield 1—Card Acceptor Name—from DE 43, up
16–22 spaces Issuer inserts if Card Acceptor Name is less than
22 positions.
24–34 Mexico City Subfield 3—Card Acceptor City—from DE 43,
35–36 spaces Issuer inserts if Card Acceptor City is less than 13
positions.
38–40 MEX Subfield 6—Country Code—from DE 43, starting
in the 14th position after the third backslash (\)
for three positions.
ABC Electronics Mexico City MEX
Transactions Acquired in Canada

Canada region acquirers are required to provide the following information for
all non-remote transactions.
• Street Address submitted in DE 43, subfield 2 Card Acceptor Street Address
• Postal Code submitted in DE 43, subfield 4 Card Acceptor Postal (ZIP)
Code

Messages Involving Certain Transaction Types
MasterCard recommends that issuers processing transactions acquired in the

Canada region follow the recommended standards for Canadian Postal Code
when printing on cardholder statements:
M5X_1B1___ (_ = space)
Messages Involving Certain Transaction Types

Information in this subsection applies to credit card-activated phone
transaction types from cards issued outside the U.S. region.
The card acceptor description data for credit card-activated phone transactions
is in Point-of-Interaction (POI) Phone Data (PDS 0189). If there is a credit
card-activated phone merchant category code (MCC) in Card Acceptor
Business Code (DE 26), and PDS 0189 Point-of-Interaction Phone Data is
present, the issuer must move the entire contents of PDS 0189,
subfield 2, Phone Data, to the cardholder statement.
Assume an issuer wants to print up to a 40-position card acceptor description

on the cardholder statement. The telephone call occurred on a card issued in
region B and originated from the U.S., and has an associated MCC of 4814.
The following is all data in PDS 0189:
MCC 4814 indicates that this is a credit card activated telephone financial
transaction, so the issuer extracts the entire contents of PDS 0189 and prints it
on the cardholder statement as follows:
TL 011 59521 123415_ASUNCION_USA

Messages Involving Airline Transactions

1–2 TL Abbreviation for TEL.
3–17 Phone Number Full phone number dialed; includes country code,
city code, and local number.
18–19 Duration of call Number of minutes—duration of call.
in minutes
21–33 Card Acceptor Issuer inserts
City
35–37 USA Call origin state/country code.
If PDS 0189 is not present in the message, the issuer extracts the data from
DE 43 subfields 1, 3, and 5 as described in the preceding subsection labeled
“U.S. Region Financial Transaction.”

The card acceptor description data for airline transactions is in DE 43 and
Ticket Number (PDS 0506). If the MCC in DE 26 is an airline MCC, then the
issuer must complete the following when extracting a 40-position card
acceptor description.
U.S. Region Airlines

Assume a financial transaction has an associated MCC of 3000, United Airlines,
an airline in the U.S. region. The following is the Ticket Number in PDS 0506:
0123456789012
The following is all data in DE 43 of a First Presentment/1240:
United\123 Main Street\AnyCity\00000-0000IL USA

From the contents of DE 43 and PDS 0506, the issuer extracts card acceptor
description data for placement on the cardholder statement as follows:

1–6 United Subfield 1—Card Acceptor Name—from DE 43, up
to the first backslash (\). The Card Acceptor
Name (airline name) is abbreviated in an airline
transaction. This subfield cannot exceed nine-
positions.
7–9 spaces Issuer inserts.
10–22 0123456789012 Ticket Number, excluding check digit, from
PDS 0506.
31–36 spaces Issuer inserts if DE 43, subfield 3 is less than 13
positions.
38–40 IL Subfield 5—State, Province, or Region Code—from
The following is on the cardholder statement:
United 0123456789012 AnyCity IL

Airlines Outside the U.S. Region

Another example assumes a member wants to print a 40-position card acceptor
description on the cardholder statement. The Financial transaction has an
associated MCC of 3151, Air Zaire, an airline outside the U.S. region. The
following is all data in DE 43 of a First Presentment/1240:
AirZaire 0123456789012\123 Pen Lane\AnyCity\00000-0000OD ZAR
From the contents of DE 43 the issuer extracts card acceptor description data
for placement on the cardholder statement as follows:

1–22 AirZaire Subfield 1—Card Acceptor Name—from DE 43,
0123456789012 up to the first backslash (\). The Card Acceptor
Name (airline name) is abbreviated in an airline
transaction. For airlines outside the U.S., the
ticket number is included in the Card Acceptor
Name subfield.
positions.
38–40 ZAR Subfield 6—Country Code—from DE 43, starting
in the 14th position after the third backslash (\)
for three positions.
AirZaire 0123456789012 AnyCity ZAR

Messages Involving QPS Transactions

The card acceptor description data for Quick Payment Service (QPS)
transactions is in DE 43 and Program Registration ID (PDS 0043). If PDS 0043
is present, and contains a “Q” followed by a two-position code, the issuer must
complete the following when extracting a 40-position card acceptor
description.

cardholder statement. It is a U.S. region financial transaction submitted with
an MCC of 5814, Quick Payment Service—Fast-Food Restaurant. The clearing
system verified that PDS 0043 is a valid QPS indicator registered to the member
that submitted the transaction. The following is all data in DE 43 of a First
Presentment/1240:
A1 Food Inc\123 Elm Street\AnyCity\00000-0000TX USA
positions 1 2 3
Q01

From the DE 43 and PDS 0043 contents, the issuer extracts card acceptor

1–11 A1 Food Inc Subfield 1—Card Acceptor Name—from DE 43, up
to the first backslash (\). The Card Acceptor
Name is limited to 19 positions in QPS
transactions if PDS 0043 is present.
positions.
20–22 Q01 From PDS 0043, positions 1–3; or DE 43
subfield 1, positions 20–22.
positions.
38–40 TX Subfield 5—State, Province, or Region Code—from
A1 Food Inc Q01 AnyCity TX

Messages Involving Supermarket Transactions
Messages Involving Supermarket Transactions

The card acceptor description data for Supermarket transactions is in DE 43
and PDS 0043. If PDS 0043 is present, the issuer must complete the following
when extracting the 40-position card acceptor description.

cardholder statement. It is a U.S. region financial transaction submitted at the
Supermarket interchange level (an Interchange Rate Designator of 71 or 81.
The clearing system has verified that PDS 0043 is a valid Supermarket indicator
registered to the member that submitted the transaction. The following is all
data in DE 43 of a First Presentment/1240:
ABC Grocery\123 Elm Street\AnyCity\00000-0000TX USA
positions 1 2 3
S01

1–11 ABC Grocery Subfield 1—Card Acceptor Name—from DE 43, up
to the first backslash (\). Card Acceptor Name is
limited to 19 positions in Supermarket program
positions.
20–22 S01 From PDS 0043, positions 1–3; or DE 43
positions.

Messages Involving Warehouse Club Transactions

38–40 TX Subfield 5—State, Province, or Region Code—from
ABC Grocery S01 AnyCity TX

The card acceptor description data for Warehouse Club transactions is in
DE 43 and PDS 0043. If there is a Warehouse Club MCC in DE 26 and if
PDS 0043 is present, the issuer must complete the following when extracting a
40-position card acceptor description.

cardholder statement. It is a U.S. region financial transaction submitted with
an MCC of 5300, Wholesale Clubs. The clearing system has verified that
PDS 0043 is a valid Warehouse Club indicator registered to the member that
submitted the transaction. The following is all data in DE 43 of a First
Presentment/1240:
Pat’s Club\123 High Street\AnyCity\00000-0000MO USA
positions 1 2 3
W01

Position(s) Value Definition

1–10 Pat’s Club Subfield 1—Card Acceptor Name—from DE 43, up
limited to 19 positions in Warehouse Club
20–22 W01 From PDS 0043, positions 1–3; or DE 43
positions.
38–40 MO Subfield 5—State, Province, or Region Code—from
Pat's Club W01 AnyCity MO

Messages Involving Service Industries Transactions
Messages Involving Service Industries Transactions

The card acceptor description data for Service Industries transactions is in
DE 43 and PDS 0043. If PDS 0043 is present, and contains an “R” followed by
a two-position code, the issuer must complete the following when extracting a

cardholder statement. It is a U.S. region financial transaction submitted with a
Service Industries MCC. The clearing system has verified that PDS 0043 is a
valid Service Industries indicator registered to the member that submitted the
transaction. The following is all data in DE 43 of a First Presentment/1240:
Al’s Place\123 High Street\AnyCity\00000-0000AL USA
positions 1 2 3
R01

1–10 Al’s Place Subfield 1—Card Acceptor Name—from DE 43, up
limited to 19 positions in Service Industries
20–22 R01 From PDS 0043, positions 1–3; or DE 43
24-30 Any City Subfield 3—Card Acceptor City—from DE 43,
positions.

Messages Involving PH Transactions

38–40 AL Subfield 5—State, Province, or Region Code—from
Al's Place R01 AnyCity AL

The card acceptor description data for Prestigious Hotels (PH) transactions is in
DE 43 and PDS 0043. If PDS 0043 is present, the issuer must complete the
following when extracting the 40-position card acceptor description.
Assume an issuer wants to print a 40 position card acceptor description on the

cardholder statement. The acquirer submitted the financial transaction with a
value of PAA in PDS 0043 indicating that it is a PH transaction. The following
is all data in DE 43 of a First Presentment/1240:
ABC Hotel\123 Same Street\AnyCity\00000-0000MN USA
positions 1 2 3
PAA


1–9 ABC Hotel Subfield 1—Card Acceptor Name—from DE 43, up
limited to 19 positions in PH transactions if
PDS 0043 is present.
positions.
20–22 PAA From PDS 0043, positions 1–3; or DE 43
positions.
38–40 MN Subfield 5—State, Province, or Region Code—from
ABC Hotel PAA AnyCity MN

Messages Involving IFC Transactions
Messages Involving IFC Transactions

The card acceptor description data for In-flight Commerce (IFC) transactions is
in DE 43 and Card Acceptor Inquiry Information (PDS 0170). If the value in
Terminal Type (PDS 0023) is CT4⎯Cardholder Activated Terminal Level 4
(IFC Terminal)—the issuer must complete the following when extracting the

cardholder statement. The acquirer submitted the financial transaction with a
value of CT4 in PDS 0023, indicating that this is an IFC transaction. The
following is all data in DE 43 of a First Presentment/1240:
ABC Service Provider\12 Elm Road\AnyCity\00000-0000OB MEX
positions 1 2 3
CT4

1–20 ABC Service Subfield 1—Card Acceptor Name—from DE 43,
Provider up to the first backslash (\).
positions.
24–38 800-123-4567 Subfield 1—Customer Service Telephone
Number—from PDS 0170 or DE 43 subfield 3.
(Customer Service Telephone Numbers are left-
justified, space-filled.)
39–40 delimiter spaces Issuer inserts.

Messages Involving Non–Face-To-Face Transactions
ABC Service Provider 800-123-4567
Messages Involving Non–Face-To-Face Transactions

The card acceptor description data for Non–Face-To-Face transactions is in DE
43 and PDS 0170. If the MCC in DE 26 indicates a Non–Face-to-Face
transaction, the issuer must complete the following when extracting the 40-
position card acceptor description.

cardholder statement. The acquirer submitted the financial transaction with an
MCC of 5964—Catalog Merchants—indicating that this is a Non–Face-To-Face
transaction. The following is all data in DE 43 of a First Presentment/1240:
Outdoor Wear\123 Same Street\AnyCity\00000-0000SD

USA

1–12 Outdoor Wear Subfield 1—Card Acceptor Name—from DE 43, up
positions.
24–38 TEL8001234567 Subfield 1—Customer Service Telephone
Number—from PDS 0170 or DE 43 subfield 3.
(Customer Service Telephone Numbers are left-
justified, space-filled.) The system extracts only
the first 13 positions of subfield 1.
39–40 delimiter space Issuer inserts.

Messages Involving Payment Transactions
Outdoor Wear TEL8001234567

The card acceptor description data for Payment Transactions is in DE 43,
subfield 1 Card Acceptor Name, in PDS 0170, subfield 1 Customer Service
Phone Number, and in PDS 0175 Card Acceptor URL.

cardholder statement. The acquirer submitted the financial transaction as a
payment transaction, as indicated by a value of 28 in DE 3, Processing Code,
subfield 1 Cardholder Transaction Type. The following is data in DE 43,
PDS 0170, and PDS 0175 of a First Presentment/1240:
DE 43, s1 PDS 0170, s1 PDS 0175
ABC PayPro 8001234567 www.abc_paypro.com
Form the contents of in DE 43, subfield 1, PDS 0170, subfield 1, and in

PDS 0175, the issuer extracts card acceptor description data for placement on
the cardholder statement as follows:

1–10 ABC PayPro From DE 43, subfield 1—Card Acceptor
Name—Name of the service provider that
processed the Payment Transaction.
12–21 8001234567 From PDS 0170, subfield 1, Customer Service
Phone Number—the phone number of the
service provider.
23–30 www.abc_paypro.com From PDS 0175—Card Acceptor URL–URL
(Uniform Resource Locator)/web site address
information.

ABC PayPro 8001234567 www.abc_paypro.com

C Edit Error Numbers and Messages
This chapter provides error numbers and messages that the IPM Pre-edit
software, GCMS, or both generate during the edit process.
Overview ............................................................................................................ C-1
Error Listing by Error Number ........................................................................... C-2
Error Listing by MTI/Function Code................................................................ C-79

File Header/1644-697................................................................................. C-79
First Presentments/1240-200 ...................................................................... C-82
Financial Detail Addendum/1644-696 ......................................................C-104
Retrieval Request/1644-603.......................................................................C-179
Fee Collection (Retrieval Fee Billing)/1740-700 ......................................C-191
First Chargebacks (Full)/1442-450 and (Partial)/1442-453 ......................C-205
Second Presentments (Full)/1240-205, and (Partial)/1240-282 ...............C-224
Arbitration Chargebacks (Full)/1442-451 and (Partial)/1442-454............C-243
Fee Collection (Other)/1740-700, 780, 781, and 782...............................C-263
File Trailer/1644-695 .................................................................................C-275

IPM Clearing Formats • May 2004 C-i
Edit Error Numbers and Messages
Overview
Overview
The IPM Pre-edit software and GCMS generate error numbers and messages
during the edit process.
This appendix presents these error numbers and messages in two ways:
• By IPM error number
• By Field and Subfield and Message Type Identifier (MTI/Function Code)
Some error messages contain a variable field. IPM Pre-edit software or GCMS
replaces the variable field with the specific element, list of values, message
type, or occurrence number of the field in error when it generates the error
message. The replacement with the actual value appears in the IPM Pre-edit
and GCMS Error Detail reports
The table of error numbers and messages contains a column titled “Edit
Performed By…” This column indicates whether the edit is performed by:
• The IPM Pre-edit software only
• GCMS only
• Both the IPM Pre-edit software and GCMS

IPM Clearing Formats • May 2004 C-1
Error Listing by Error Number

Error Edit Performed
Number Error Message By…
UNPARSEABLE MESSAGE Both
Refer to the beginning of chapter 6 of this manual for further information.
0006 MESSAGE TYPE INDICATOR (MTI) NON-NUMERIC. Both
0008 PDS0052S3 UCAF COLLECTION INDICATOR MUST BE 1. Both
0009 DE2 PRIMARY ACCOUNT NUMBER (PAN) MUST BE NUMERIC. Both
0010 DE2 PRIMARY ACCOUNT NUMBER (PAN) LENGTH MUST BE 6-19. Both
0011 DE2 PRIMARY ACCOUNT NUMBER (PAN) ACCOUNT RANGE INVALID. Both
0012 DE3 PROCESSING CODE MUST BE NUMERIC. Both
0013 DE3S1 CARDHOLDER TRANSACTION TYPE INVALID. MUST BE 00, 01, Both
12, 17, 18, 20, 28, OR 50.
0014 DE3S2 CARDHOLDER FROM - ACCOUNT MUST BE 00. Both
0015 DE3S3 CARDHOLDER TO - ACCOUNT MUST BE 00. Both
0016 DE3S1 CARDHOLDER TRANSACTION TYPE INVALID FOR ATM CASH Both
WITHDRAWAL CARD ACCEPTOR BUSINESS CODE (MCC) 6011.
0017 DE3S1 CARDHOLDER TRANSACTION TYPE INVALID FOR CASH Both
ADVANCE CARD ACCEPTOR BUSINESS CODE (MCC) 6010.
0018 DE3S1 CARDHOLDER TRANSACTION TYPE INVALID FOR UNIQUE Both
TRANSACTION CARD ACCEPTOR BUSINESS CODE (MCC). MUST BE
EQUAL TO 18.
0019 PDS0052S3 UCAF COLLECTION INDICATOR MUST BE 2. Both
0020 DE4 AMOUNT, TRANSACTION MUST BE NUMERIC AND GREATER Both
THAN ZERO.
0022 PDS0023 TERMINAL TYPE/PDS0158S4 INTERCHANGE RATE Both
DESIGNATOR CONFLICT.
0023 DE4 AMOUNT, TRANSACTION MUST BE PRESENT WHEN DE49 Both
CURRENCY CODE, TRANSACTION IS PROVIDED.
0024 PDS0148 CURRENCY EXPONENTS MISSING. MUST BE PRESENT IN A Both
MESSAGE WHEN DE4 AMOUNT, TRANSACTION IS PROVIDED.
0025 DE5 AMOUNT, RECONCILIATION MUST BE NUMERIC. Both
0027 DE5 AMOUNT, RECONCILIATION MISSING. MUST BE PRESENT IN A Both
MESSAGE WHEN DE50 CURRENCY CODE, RECONCILIATION IS
PROVIDED.

C-2 May 2004 • IPM Clearing Formats

0028 PDS0148 CURRENCY EXPONENTS MUST BE PRESENT IN A MESSAGE Both
WHEN DE5 AMOUNT, RECONCILIATION IS PROVIDED.
0029 DE5 AMOUNT, RECONCILIATION MISSING. MUST BE PRESENT IN AN Both
ATM CASH WITHDRAWAL MESSAGE.
0034 DE6 AMOUNT, CARDHOLDER BILLING MUST BE NUMERIC. Both
0036 DE6 AMOUNT, CARDHOLDER BILLING MUST BE PRESENT IN A Both
MESSAGE WHEN DE51 CURRENCY CODE, CARDHOLDER BILLING IS
PROVIDED.
MESSAGE WHEN DE6 AMOUNT, CARDHOLDER BILLING IS PROVIDED.
0039 DE12S1 DATE, LOCAL TRANSACTION IN DE12 DATE AND TIME, LOCAL Both
TRANSACTION INVALID. DATE MUST BE IN THE FORMAT 000000,
YYMMDD, OR YYMM00.
0040 DE12S2 TIME, LOCAL TRANSACTION HOURS MUST BE IN THE RANGE Both
00-23.
0042 DE12S2 TIME, LOCAL TRANSACTION INVALID. MINUTES AND Both
SECONDS MUST BE IN RANGE 00-59.
0043 DE12S1 DATE, LOCAL TRANSACTION CANNOT BE GREATER THAN Both
THE DATE IN PDS0105S2 FILE REFERENCE DATE.
0044 DE94 TRANSACTION ORIGINATOR INSTITUTION ID CODE INVALID Both
FOR SUPERMARKET INTERCHANGE PROGRAM.
0045 DE14 EXPIRATION DATE MUST BE NUMERIC AND HAVE A VALID Both
DATE IN THE FORMAT YYMM.
0047 DE22S1 TERMINAL DATA: CARD DATA INPUT CAPABILITY INVALID. Both
MUST BE 0, 1, 2, 4, 5, 6, A, B, C, D, E, M, OR V.
0048 DE22S2 CARDHOLDER AUTHENTICATION CAPABILITY INVALID. Both
MUST BE 0, 1, 2, 5, 6, OR 9.
0049 DE22S3 CARD CAPTURE CAPABILITY INVALID. MUST BE 0, 1, OR 9. Both
0050 DE22S4 TERMINAL OPERATING ENVIRONMENT INVALID. MUST BE 0, Both
1, 2, 3, 4, 5, 6, OR 9.
0051 DE22S5 CARDHOLDER PRESENT DATA INVALID. MUST BE 0, 1, 2, 3, 4, Both
5, 6, OR 9.
0052 DE22S6 CARD PRESENT DATA INVALID. MUST BE 0, 1, OR 9. Both


0053 DE22S7 CARD DATA INPUT MODE INVALID. MUST BE 0, 1, 2, 6, A, B, Both
S, OR T.
DE22S1 CARD DATA INPUT CAPABILITY INVALID. MUST BE 0, 1, 2, 4, Both
6, A, B, OR V.
DE22S1 CARD DATA INPUT CAPABILITY INVALID. MUST BE 5, C, D, E, Both
OR M.
DE22S4 TERMINAL OPERATING ENVIRONMENT INVALID. MUST BE 1 Both
OR 3.
DE22S5 CARDHOLDER PRESENT DATA INVALID. MUST BE ZERO. Both
DE22S6 CARD PRESENT DATA INVALID. MUST BE 1. Both
DE22S7 CARD DATA INPUT MODE INVALID. MUST BE 0, 1, 2, 6, A, B, Both
C, F, M, S, OR T.
DE22S10 CARD DATA OUTPUT CAPABILITY INVALID. MUST BE 3. Both
DE22S10 CARD DATA OUTPUT CAPABILITY INVALID. MUST BE 0, 1, 2, Both
OR S.
DE40 EXTENDED SERVICE CODE INVALID. MUST BE 200, 201, 202, Both
203, 205, 206, 207, 220, 221, 222, 223, 225, 226, 227, 600, 601, 602, 603,
605, 606, 607, 620, 621, 622, 623, 625, 626 OR 627.
DE40 EXTENDED SERVICE CODE INVALID. MUST BE 100, 101, 102, Both
103, 105, 106, 107, 120, 121, 122, 123, 125, 126, 127, 500, 501, 502, 503,
505, 506, 507, 520, 521, 522, 523, 525, 526, 527, 700, 701, 702, 703, 705,
706, 707, 720, 721, 722, 723, 725, 726, 727.
0054 DE22S8 CARDHOLDER AUTHENTICATION METHOD INVALID. MUST Both
BE 0, 1, 2, 5, 6, 9, OR S.
0055 DE22S9 CADHOLDER AUTHENTICATION ENTITY INVALID. MUST BE 0, Both
1, 2, 3, 4, 5, 6 OR 9.
0056 DE22S10 CARD DATA OUTPUT CAPABILITY INVALID. MUST BE 0, 1, 2, Both
3, OR S.
0057 DE22S11 TERMINAL DATA OUTPUT CAPABILITY INVALID. MUST BE 0, Both
1, 2, 3, OR 4.
0058 DE22S12 PIN CAPTURE CAPABILITY INVALID. MUST BE 0, 1, 2, 3, 4, 5, Both
6, 7, 8, 9, A, B, OR C.
0059 DE23 CARD SEQUENCE NUMBER MUST BE NUMERIC. Both
0061 DE24 FUNCTION CODE MUST BE NUMERIC. Both
0062 MESSAGE TYPE INDICATOR (MTI)/DE24 FUNCTION CODE Both
COMBINATION INVALID.


0064 DE25 MESSAGE REASON CODE MUST BE NUMERIC. Both
0067 PDS0522 SERVICE CLASS CODE MUST BE LEFT JUSTIFIED AND Both
CANNOT CONTAIN ALL SPACES.
0069 PDS0043 PROGRAM REGISTRATION ID IS REQUIRED AND MUST Both
CONTAIN A VALID VALUE.
0070 DE71 MESSAGE NUMBER MUST BE NUMERIC. Both
0076 DE30S2 AMOUNTS ORIGINAL, RECONCILIATION MUST BE ZERO- Both
FILLED.
0077 PDS0149 CURRENCY CODES, AMOUNTS, ORIGINAL MUST BE PRESENT Both
IN A MESSAGE WHEN DE30 AMOUNTS, ORIGINAL IS PROVIDED.
0078 PDS0148 CURRENCY EXPONENTS MUST BE PRESENT IN A MESSAGE Both
WHEN DE30 AMOUNTS, ORIGINAL IS PROVIDED.
0079 DE31 ACQUIRER REFERENCE DATA CANNOT BE ALL LOW-VALUES OR Both
ALL HIGH-VALUES.
0080 DE31S1 INTERCHANGE RATE DESIGNATOR MUST BE NUMERIC. Both
0081 DE31S2 ACQUIRER’S BIN MUST BE NUMERIC. Both
0083 DE31S4 ACQUIRER’S SEQUENCE NUMBER MUST BE NUMERIC. Both
0085 DE31S5 CHECK DIGIT MUST BE NUMERIC. Both
0086 DE31S3 JULIAN PROCESSING DATE YDDD OF DE31 ACQUIRER Both
REFERENCE DATA MUST BE A VALID DATE IN THE FORMAT YDDD.
0087 DE31S5 CHECK DIGIT DOES NOT MOD-CHECK. Both
0089 DE32 ACQUIRING INSTITUTION ID CODE MUST BE NUMERIC. Both
0090 DE32 ACQUIRING INSTITUTION ID CODE LENGTH FIELD MUST BE A Both
VALUE OF 001-011.
0091 DE37 RETRIEVAL REFERENCE NUMBER CANNOT BE ALL LOW-VALUES Both
OR ALL HIGH-VALUES.
0092 DE37 RETRIEVAL REFERENCE NUMBER CANNOT CONTAIN ALL Both
SPACES.
0093 DE38 APPROVAL CODE CANNOT BE ALL LOW-VALUES OR ALL HIGH- Both
VALUES.
0094 DE38 APPROVAL CODE CONTAINS EMBEDDED SPACES. Both
0095 DE38 APPROVAL CODE MUST BE LEFT JUSTIFIED AND CANNOT Both
CONTAIN ALL SPACES.
0096 DE41 CARD ACCEPTOR TERMINAL ID CANNOT BE ALL LOW-VALUES Both
OR ALL HIGH-VALUES.


0097 DE41 CARD ACCEPTOR TERMINAL ID MUST BE LEFT JUSTIFIED AND Both
0098 DE42 CARD ACCEPTOR ID CANNOT BE ALL LOW-VALUES OR ALL Both
HIGH-VALUES.
0099 DE42 CARD ACCEPTOR ID MUST BE LEFT JUSTIFIED AND CANNOT Both
CONTAIN ALL SPACES.
0100 DE43 CARD ACCEPTOR NAME/LOCATION CANNOT BE ALL LOW- Both
VALUES OR ALL HIGH-VALUES.
0101 DE43 CARD ACCEPTOR NAME/LOCATION MUST BE 20-99. Both
0102 DE43S1 CARD ACCEPTOR NAME CANNOT BE ALL LOW-VALUES OR ALL Both
HIGH-VALUES.
0103 DE43S1 CARD ACCEPTOR NAME LENGTH MUST BE 1-22. Both
0104 DE43S3 CARD ACCEPTOR CITY CANNOT BE ALL LOW-VALUES OR ALL Both
HIGH-VALUES.
0105 DE43S3 CARD ACCEPTOR CITY LENGTH CANNOT EXCEED 13. Both
0107 WITHIN DE43 CARD ACCEPTOR NAME/LOCATION, 3 BACKSLASH Both
CHARACTERS ARE REQUIRED TO DELIMIT NAME\STREET
ADDRESS\CITY.
0108 DE43S1 CARD ACCEPTOR NAME MUST BE LEFT JUSTIFIED AND Both
0109 DE43S4 CARD ACCEPTOR POSTAL (ZIP) CODE NOT LEFT JUSTIFIED. Both
0112 DE43S6 CARD ACCEPTOR COUNTRY CODE MUST CONTAIN A VALID Both
ISO STANDARD COUNTRY CODE.
0114 DE48 ADDITIONAL DATA CANNOT BE ALL LOW-VALUES OR ALL Both
HIGH-VALUES.
0115 DE48 ADDITIONAL DATA LENGTH MUST BE 008-999. Both
0117 INCORRECT PDS ENCODING SCHEME WITHIN DE48 ADDITIONAL Both
DATA. PDS TAG + LENGTH + DATA MUST FIT ENTIRELY INTO DE48
OR BE MOVED TO DE62.
0119 DE49 CURRENCY CODE, TRANSACTION MUST CONTAIN A VALID ISO Both
STANDARD NUMERIC CURRENCY CODE.
0120 DE49 CURRENCY CODE, TRANSACTION MUST BE PRESENT WHEN DE4 Both
AMOUNT, TRANSACTION IS PROVIDED.
0122 PDS0148S1 CURRENCY CODE OCCURRENCE FOR DE49 CURRENCY Both
CODE, TRANSACTION, MUST BE PROVIDED.
0123 DE50 CURRENCY CODE, RECONCILIATION MUST BE NUMERIC. Both


0124 DE50 CURRENCY CODE MISSING. MUST BE PRESENT IN A MESSAGE Both
WHEN DE5 AMOUNT, RECONCILIATION IS PROVIDED.
CODE, RECONCILIATION MUST BE PROVIDED.
0129 DE50 CURRENCY CODE, RECONCILIATION MUST CONTAIN A VALID Both
ISO STANDARD NUMERIC CURRENCY CODE.
0133 DE51 CURRENCY CODE, CARDHOLDER BILLING MUST BE NUMERIC. Both
0134 DE51 CURRENCY CODE, CARDHOLDER BILLING MUST BE PRESENT IN Both
A MESSAGE WHEN DE6 AMOUNT, CARDHOLDER BILLING IS
PROVIDED.
CODE, CARDHOLDER BILLING MUST BE PROVIDED.
0137 DE63 TRANSACTION LIFE CYCLE ID CANNOT BE ALL LOW-VALUES OR Both
ALL HIGH-VALUES.
0138 DE63 TRANSACTION LIFE CYCLE ID LENGTH FIELD MUST BE 016-999. Both
0139 DE63S1 LIFE CYCLE SUPPORT INDICATOR MUST BE A SPACE. Both
0141 DE63S2 TRACE ID POSITIONS 10-13 MUST BE A VALID DATE IN THE Both
FORMAT MMDD.
0142 THE FIRST NINE POSITIONS OF DE63S2 TRACE ID CANNOT CONTAIN Both
EMBEDDED SPACES.
0148 DE25 MESSAGE REASON CODE INVALID FOR THIS FIRST GCMS
CHARGEBACK (FULL), FIRST CHARGEBACK (PARTIAL) MESSAGES.
0149 DE71 MESSAGE NUMBER MUST BE GREATER THAN THE DE71 Both
MESSAGE NUMBER VALUE IN THE PREVIOUS MESSAGE.
0151 DE72 DATA RECORD CANNOT BE ALL LOW-VALUES OR ALL HIGH- Both
VALUES.
0154 REQUEST NOT ON FILE. GCMS
0155 DE93 TRANSACTION DESTINATION INSTITUTION ID CODE MUST BE Both
NUMERIC.
0157 DE93 TRANSACTION DESTINATION INSTITUTION ID CODE INVALID. Both
0159 DE94 TRANSACTION ORIGINATOR INSTITUTION ID CODE MUST BE Both
NUMERIC.
0161 DE94 TRANSACTION ORIGINATOR INSTITUTION ID CODE INVALID. Both
0165 DE62 ADDITIONAL DATA 2 CANNOT BE ALL LOW-VALUES OR ALL Both
HIGH-VALUES.


0166 DE62 ADDITIONAL DATA 2 LENGTH MUST BE 008-999. Both
DATA 2.
0169 DE62 ADDITIONAL DATA 2 CAN BE PRESENT ONLY IF DE48 Both
ADDITIONAL DATA IS PRESENT.
HIGH-VALUES.
DATA 3. PDS TAG + LENGTH + DATA MUST FIT ENTIRELY INTO
DE123 OR BE MOVED TO DE124.
ADDITIONAL DATA AND DE62 ADDITIONAL DATA 2 ARE PRESENT.
HIGH-VALUES.
DE125 OR IT CANNOT BE ADDED.
ADDITIONAL DATA, DE62 ADDITIONAL DATA 2, AND DE123
ADDITIONAL DATA 3 ARE PRESENT.
0181 PDS0023 TERMINAL TYPE CANNOT BE ALL LOW-VALUES OR ALL Both
HIGH-VALUES.
0182 PDS0023 TERMINAL TYPE MUST BE A FIXED LENGTH OF 003. Both
0183 PDS0023 TERMINAL TYPE NOT LEFT JUSTIFIED. Both
0184 PDS0023 TERMINAL TYPE MUST CONTAIN A VALID VALUE OF ATM, Both
CT1, CT2, CT3, CT4, CT6, CT7, MAN, NA_, OR POI.
0185 PDS0025S1 MESSAGE REVERSAL INDICATOR MUST BE EQUAL TO R OR Both
A SPACE IF PRESENT.
0186 PDS0025S2 CENTRAL SITE PROCESSING DATE OF ORIGINAL MESSAGE Both
MUST BE NUMERIC AND A VALID DATE IN THE FORMAT YYMMDD.
0187 PDS0025 MESSAGE REVERSAL INDICATOR LENGTH FIELD MUST BE A Both
VALUE OF 001-007.


INVALID. CANNOT BE GREATER THAN THE SYSTEM PROCESSING
DATE.
0194 PDS0043 PROGRAM REGISTRATION ID MUST BE A FIXED LENGTH OF Both
003.
0206 PDS0512 TOTAL FARE MUST BE NUMERIC AND RIGHT-JUSTIFIED. Both
0207 PDS0509 ISSUE DATE MUST BE A VALID DATE IN THE FORMAT Both
YYMMDD.
0208 PDS0501S1 USAGE CODE INVALID. MUST BE 01, 05, 06, 07, 08, 10, 98, Both
OR 99.
0211 INVALID PASSENGER TRANSPORT ADDENDUM. PASSENGER Both
TRANSPORT ADDENDUM CAN ONLY BE USED WITH A PASSENGER
TRANSPORT CARD ACCEPTOR BUSINESS CODE (MCC).
0212 INVALID VEHICLE RENTAL ADDENDUM. VEHICLE RENTAL Both
ADDENDUM CAN ONLY BE USED WITH A VEHICLE RENTAL CARD
ACCEPTOR BUSINESS CODE (MCC).
0213 INVALID LODGING ADDENDUM. LODGING ADDENDUM CAN ONLY Both
BE USED WITH A LODGING CARD ACCEPTOR BUSINESS CODE (MCC).
0214 INVALID CORPORATE FLEET ADDENDUM. CORPORATE FLEET Both
TRANSACTION DETAIL INFORMATION ADDENDUM CAN ONLY BE
USED WITH A FUEL CARD ACCEPTOR BUSINESS CODE (MCC) AND A
FLEET ACCOUNT RANGE.
0215 PDS0501S2 INDUSTRY RECORD NUMBER MUST BE NUMERIC. Both
0217 PDS0501S3 OCCURRENCE INDICATOR MUST BE NUMERIC. Both
0219 PDS0513 TOTAL FEES MUST BE NUMERIC AND RIGHT-JUSTIFIED. Both
0220 PDS0514 TOTAL TAXES MUST BE NUMERIC AND RIGHT-JUSTIFIED. Both
0222 PDS0505 PASSENGER NAME MUST BE LEFT JUSTIFIED AND CANNOT Both
CONTAIN ALL SPACES.
0223 PDS0520 TRAVEL DATE MUST BE A VALID DATE IN THE FORMAT Both
YYMMDD.
0226 PDS0510 TRAVEL AGENCY CODE CANNOT BE ALL LOW-VALUES OR Both
ALL HIGH-VALUES.
0227 PDS0511 TRAVEL AGENCY NAME CANNOT BE ALL LOW-VALUES OR Both
ALL HIGH-VALUES.
0228 PDS0523 CITY OF ORGIN/AIRPORT CODE CANNOT BE ALL LOW- Both


0229 PDS0523 CITY OF ORGIN/AIRPORT CODE MUST BE LEFT JUSTIFIED Both
AND CANNOT CONTAIN ALL SPACES.
0232 PDS0530 FLIGHT NUMBER MUST BE LEFT JUSTIFIED AND CANNOT Both
CONTAIN ALL SPACES.
0234 PDS0522 SERVICE CLASS CODE CANNOT BE ALL LOW-VALUES OR ALL Both
HIGH-VALUES.
0235 PDS0525 STOP OVER CODE CANNOT BE ALL LOW-VALUES OR ALL Both
HIGH-VALUES.
0236 PDS0524 CITY OF DESTINATION/AIRPORT CODE CANNOT BE ALL Both
LOW-VALUES OR ALL HIGH-VALUES.
0237 PDS0524 CITY OF DESTINATION/AIRPORT CODE MUST BE LEFT Both
JUSTIFIED AND CANNOT CONTAIN ALL SPACES.
0239 PDS0529 FARE BASIS CODE CANNOT BE ALL LOW-VALUES OR ALL Both
HIGH-VALUES.
0258 PDS0506 TICKET NUMBER CANNOT BE ALL LOW-VALUES OR ALL Both
HIGH-VALUES.
0259 PDS0521 CARRIER CODE MUST BE LEFT JUSTIFIED AND CANNOT Both
CONTAIN ALL SPACES.
0268 PDS0266 FIRST CHARGEBACK/FEE COLLECTION RETURN DATA Both
CANNOT BE ALL LOW-VALUES OR ALL HIGH-VALUES.
0269 PDS0267S1 MESSAGE REASON CODE MUST BE A VALID MESSAGE Both
REASON CODE OR ZEROS.
0270 PDS0508 CUSTOMER CODE MUST BE LEFT JUSTIFIED AND CANNOT Both
CONTAIN ALL SPACES.
0277 PDS0598 TOTAL TAX COLLECTED INDICATOR MUST BE Y, N, 0, OR A Both
SPACE.
0279 PDS0607 DUTY AMOUNT INVALID. MUST BE NUMERIC. Both
0280 PDS0608 DESTINATION POSTAL CODE MUST BE LEFT JUSTIFIED AND Both
0283 PDS0614 ORDER DATE MUST BE A VALID DATE IN THE FORMAT Both
YYMMDD.
0285 PDS0641 PRODUCT CODE MUST CONTAIN A VALUE IN THE RANGE Both
030-099 OR 300-999 IF TRANSACTION IS A FLEET CARD AT A FUEL
LOCATION SUBMITTED FOR THE U.S. REGION CORPORATE DATA
RATE III INTERCHANGE PROGRAM.
0286 PDS0642 ITEM DESCRIPTION MUST BE LEFT JUSTIFIED AND CANNOT Both
CONTAIN ALL SPACES.


0288 PDS0643S2 ITEM QUANTITY EXPONENT MUST BE NUMERIC. Both
0289 DE31 ACQUIRER REFERENCE DATA LENGTH MUST BE 01-99. Both
0292 PDS0648S1 DISCOUNT INDICATOR MUST BE Y OR N OR A SPACE. Both
0293 PDS0648S2 ITEM DISCOUNT MUST BE NUMERIC. Both
0294 PDS0650 NET/GROSS INDICATOR FOR EXTENDED ITEM AMOUNT Both
MUST BE Y OR N OR A SPACE.
0295 PDS0654 DEBIT OR CREDIT INDICATOR MUST BE D OR C. Both
0296 PDS0654 DEBIT OR CREDIT INDICATOR MUST BE ‘C’ OR ‘D’ IF PDS0647 Both
EXTENDED ITEM AMOUNT IS GREATER THAN ZERO.
0302 PDS0547 RENTAL RETURN STATE/PROVINCE INVALID. Both
0304 PDS0548 RENTAL RETURN COUNTRY MUST CONTAIN A VALID ISO Both
STANDARD COUNTRY CODE.
0305 PDS0548 RENTAL RETURN COUNTRY MUST BE LEFT JUSTIFIED AND Both
0307 PDS0550 RENTAL RETURN DATE MUST BE A VALID DATE IN THE Both
FORMAT YYMMDD.
0308 PDS0551 RENTAL CHECKOUT DATE MUST BE A VALID DATE IN THE Both
FORMAT YYMMDD.
0310 PDS0558 MILES/KILOMETER INDICATOR MUST BE K, M OR A SPACE. Both
0312 PDS0555 RATE PER MILE (OR PER KILOMETER) INVALID.MUST BE Both
NUMERIC.
0313 PDS0556 TOTAL MILES (OR PER KILOMETERS) INVALID. MUST BE Both
NUMERIC.
0314 PDS0557 MAXIMUM FREE MILES (OR KILOMETERS) INVALID. MUST BE Both
NUMERIC.
0316 PDS0559S1 INSURANCE INDICATOR MUST BE Y, N OR A SPACE. Both
0318 PDS0561S1 ADJUSTED AMOUNT INDICATOR MUST BE A SPACE, A, B, Both
C, D, E OR X.
0321 PDS0574 ARRIVAL DATE MUST BE A VALID DATE IN THE FORMAT Both
YYMMDD.
0326 PDS0578S1 BILLING ADJUSTMENT INDICATOR MUST BE Y, N OR A Both
SPACE.
0327 PDS0578S2 BILLING ADJUSTMENT AMOUNT INVALID. MUST BE Both
NUMERIC.


0328 PDS0578S2 BILLING ADJUSTED AMOUNT CANNOT EQUAL ALL ZEROS Both
IF BILLING ADJUSTMENT INDICATOR IS EQUAL TO "Y.”
0329 PDS0620 OIL COMPANY BRAND NAME MUST BE NUMERIC. Both
0330 PDS0621 PURCHASE TIME INVALID. MUST BE IN THE FORMAT HHMM. Both
HOURS MUST BE 00-23 AND MINUTES MUST BE 00-59.
0332 PDS0623S1 MOTOR FUEL PRODUCT CODE MUST BE NUMERIC. Both
0333 PDS0623S1 MOTOR FUEL PRODUCT CODE INVALID. MUST BE 001-029 Both
OR 100-299.
0336 PDS0623S5 MOTOR FUEL QUANTITY EXPONENT MUST BE 0-5. Both
0337 PDS0623S3 MOTOR FUEL UNIT OF MEASURE MUST CONTAIN A SPACE Both
OR 1-5.
0339 PDS0623S2 MOTOR FUEL UNIT PRICE MUST BE NUMERIC. Both
0340 DE43 CARD ACCEPTOR NAME/LOCATION MUST BE PRESENT. Both
0341 PDS0623S6 MOTOR FUEL SALE AMOUNT MUST BE NUMERIC AND Both
GREATER THAN ZERO.
0343 PDS0629 ODOMETER READING MUST BE NUMERIC IF PDS0632 IS 1–4 Both
AND IT IS FLEET AT FUEL SUBMITTED FOR U.S. REGION CORP. LARGE
TICKET OR DATA RATE II.
0345 PDS0630 VEHICLE NUMBER MUST BE PRESENT IF PDS0632 IS ‘2’, Both
PDS 0631 IS NOT PRESENT, AND IT IS FLEET AT FUEL SUBMITTED FOR
INTERCHANGE 62 OR 67.
0347 PDS0631 DRIVER NUMBER/ID NUMBER MUST BE NUMERIC IF PDS0632 Both
IS ‘1’ OR ‘3’ AND IT IS FLEET AT FUEL SUBMITTED FOR U.S. REGION
CORP. LARGE TICKET OR DATA RATE II.
0348 PDS0620 OIL COMPANY BRAND NAME AND PDS0621 PURCHASE TIME Both
REQUIRED FOR FLEET CARD AT FUEL LOCATION TRANSACTIONS
SUBMITTED FOR THE U.S. REGION CORPORATE DATA RATE I
INTERCHANGE PROGRAM.
0349 PDS0633 COUPON/DISCOUNT AMOUNT MUST BE NUMERIC. Both
0351 PDS0105 FILE ID MUST BE A FIXED LENGTH OF 025. Both
0355 PDS0105S3 PROCESSOR ID MUST BE NUMERIC. Both
0356 PDS0105S4 FILE SEQUENCE NUMBER MUST BE NUMERIC. Both
0358 INVALID PDS0105S1 FILE TYPE. MUST BE 002. Both
0359 PDS0105S2 FILE REFERENCE DATE MUST BE A VALID DATE IN THE Both
FORMAT YYMMDD.


0360 PDS0105S2 FILE REFERENCE DATE INVALID. CANNOT BE GREATER Both
THAN THE SYSTEM PROCESSING DATE.
0361 PDS0110S3 PROCESSOR ID INVALID. MUST CONTAIN A VALID Both
MEMBER ID OR PROCESSOR ID.
0362 DUPLICATE PDS0105 FILE ID. Both
0364 PDS0110 TRANSMISSION ID MUST BE A FIXED LENGTH OF 025. Both
0369 PDS0110S4 TRANSMISSION SEQUENCE NUMBER MUST BE NUMERIC. Both
0371 PDS0110S1 TRANSMISSION TYPE INVALID. MUST BE 002. Both
0372 PDS0110S2 TRANSMISSION REFERENCE DATE INVALID. MUST BE A Both
VALID DATE IN THE FORMAT YYMMDD.
0373 PDS0110S2 TRANSMISSION REFERENCE DATE INVALID. CANNOT BE Both
GREATER THAN THE SYSTEM PROCESSING DATE.
0375 PDS0137 FEE COLLECTION CONTROL NUMBER MUST BE NUMERIC. Both
0377 PDS0174 DUN & BRADSTREET NUMBER LENGTH MUST BE 001–030. Both
0378 PDS0170 CARD ACCEPTOR INQUIRY INFORMATION CANNOT BE ALL Both
0381 PDS0146 AMOUNTS, TRANSACTION FEE LENGTH MUST BE 028-336 Both
AND MUST BE DIVISIBLE BY MINIMUM OCCURRENCE LENGTH OF 28.
0384 PDS0146S4 CURRENCY CODE, FEE NOT NUMERIC. OCCURRENCE
<XX>. Both
On Production Reports, the field occurrence number with the data in error
will replace the “XX”.
0385 PDS0146S5 AMOUNT, FEE NOT NUMERIC. OCCURRENCE <XX>. Both

0386 PDS0146S1 FEE TYPE CODE MUST BE 00-99. OCCURRENCE Both

INDICATOR <XX>.
0387 PDS0146S2 FEE PROCESSING CODE MUST BE 00, 19, OR 29. Both
OCCURRENCE INDICATOR <XX>.
0393 PDS0148 CURRENCY EXPONENTS CANNOT BE ALL LOW-VALUES OR Both

ALL HIGH-VALUES.


0394 PDS0148 CURRENCY EXPONENTS LENGTH MUST BE 04-60 AND MUST Both
BE DIVISIBLE BY MINIMUM OCCURRENCE LENGTH OF 04.
0395 PDS0148S1 CURRENCY CODE MUST CONTAIN A VALID NUMERIC ISO- Both
STANDARD CURRENCY CODE. OCCURRENCE <XX>.
0396 PDS0148S2 CURRENCY EXPONENT MUST BE VALID FOR THE Both

CORRESPONDING CURRENCY CODE IN SUBFIELD 1. OCCURRENCE
<XX>.
0398 PDS0149 CURRENCY CODES, AMOUNTS, ORIGINAL MUST BE Both

NUMERIC.
0399 PDS0149 CURRENCY CODES, AMOUNTS, ORIGINAL MUST BE A FIXED Both
LENGTH OF 006.
0400 PDS0149S1 CURRENCY CODE, ORIGINAL TRANSACTION AMOUNT Both
MUST CONTAIN A VALID ISO STANDARD NUMERIC CURRENCY CODE.
0401 PDS0149S2 CURRENCY CODE, ORIGINAL RECONCILIATION AMOUNT Both
MUST BE ALL ZEROS.
0402 PDS0149 CURRENCY CODES, AMOUNTS, ORIGINAL IS PRESENT BUT Both
PDS0148 CURRENCY EXPONENTS IS NOT PRESENT.
0403 PDS0148 CURRENCY EXPONENTS OCCURRENCE FOR PDS0149 Both
CURRENCY CODES, AMOUNTS, ORIGINAL MISSING. MUST BE
PROVIDED.
0404 PDS0149 CURRENCY CODES AMOUNT, ORIGINAL IS PRESENT BUT Both
DE30 AMOUNT, ORIGINAL IS NOT PRESENT.
0405 INVALID TRANSACTION FOR THE COUNTRY/REGION. Both
0406 PDS0508 CUSTOMER CODE LENGTH MUST BE 001–025. Both
0407 PDS0158 BUSINESS ACTIVITY CANNOT BE ALL LOW-VALUES OR ALL Both
HIGH-VALUES.
0408 PDS0158 BUSINESS ACTIVITY LENGTH MUST BE 003-020. Both
0412 PDS0165 SETTLEMENT INDICATOR CANNOT BE ALL LOW-VALUES OR Both
ALL HIGH-VALUES.
0414 PDS0165S1 SETTLEMENT INDICATOR MUST BE M, B, OR C. Both


0416 NO BILATERAL SETTLEMENT AGREEMENT ON FILE FOR <DE93> AND Both
<DE94>.
On Production Reports, the Destination & Origination Member ID will
replace “<DE93>” and “<DE94>” respectively.
0419 PDS0171 ALTERNATE CARD ACCEPTOR DESCRIPTION CANNOT BE ALL Both

0420 PDS0171 ALTERNATE CARD ACCEPTOR DESCRIPTION LENGTH MUST Both
BE 4-201.
0421 PDS0171S1 CHARACTER SET INDICATOR INVALID. MUST BE ARA, CHS, Both
CHT, CYR, GRK, HEB, HIR, HAN, KAN, KAT, ROM, THI, OR VIE.
0422 PDS0189 POINT-OF-INTERACTION (POI) PHONE DATA CANNOT BE Both
ALL LOW-VALUES OR ALL HIGH-VALUES.
0423 PDS0189 POINT-OF-INTERACTION (POI) PHONE DATA LENGTH MUST Both
BE A FIXED LENGTH OF 41.
0424 PDS0189S1 FORMAT NUMBER MUST BE 0, 1, 2, 3, OR 4. Both
0425 PDS0190 PARTNER ID CODE CANNOT BE ALL LOW-VALUES OR ALL Both
HIGH-VALUES.
0426 PDS0190 PARTNER ID CODE LENGTH MUST BE 1-6. Both
0428 PDS0228 RETRIEVAL DOCUMENT CODE MUST BE A FIXED LENGTH OF Both
001.
0429 PDS0228 RETRIEVAL DOCUMENT CODE MUST BE 1. Both
0431 PDS0230 FULFILLMENT DOCUMENT CODE MUST BE A FIXED LENGTH Both
OF 001.
0432 PDS0230 FULFILLMENT DOCUMENT CODE MUST BE 1. Both
0433 PDS0170 CARD ACCEPTOR INQUIRY INFORMATION LENGTH MUST BE Both
16-57.
0435 PDS0260 EDIT EXCLUSION INDICATOR CANNOT BE ALL LOW-VALUES Both
OR ALL HIGH-VALUES.
0436 PDS0260 EDIT EXCLUSION INDICATOR LENGTH MUST BE 2-4. Both
0437 DE23 CARD SEQUENCE NUMBER CONTAINS A VALUE IN THE RANGE Both
OF 000-099.
PDS0260S1 EXCLUSION REQUEST CODE INVALID. MUST BE Y, B0 - B9, Both
BA - BZ OR SPACES.
0441 PDS0262 DOCUMENTATION INDICATOR MUST BE A FIXED LENGTH Both
OF 001.
0442 PDS0262 DOCUMENTATION INDICATOR MUST BE 0 OR 1. Both


0444 INVALID ORIGINAL RETRIEVAL REASON FOR REQUEST LENGTH. Both
MUST BE A FIXED LENGTH OF 4.
0445 INVALID VALUE IN ORIGINAL RETRIEVAL REASON FOR REQUEST. Both
MUST BE 6305, 6321, 6322, 6323, 6341, OR 6342.
0446 PDS0265 INITIAL PRESENTMENT/FEE COLLECTION DATA CANNOT BE Both
0447 PDS0265 INITIAL PRESENTMENT/FEE COLLECTION DATA LENGTH Both
MUST BE 004-110.
0448 PDS0265S1 INITIAL MESSAGE REASON CODE MUST BE A VALID Both
MESSAGE REASON CODE.
0449 PDS0265S2 DATE, INITIAL PRESENTMENT BUSINESS MUST BE VALID Both
YYMMDD OR ZEROS IN FEE COLLECTION (RETRIEVAL FEE BILLING)
OR FEE COLLECTION (OTHER) MESSAGES.
0451 PDS0268S2 CURRENCY CODE, PARTIAL TRANSACTION MUST CONTAIN Both
A VALID ISO STANDARD NUMERIC CURRENCY CODE.
0453 PDS0306 FILE MESSAGE COUNTS MUST BE NUMERIC. Both
0454 PDS0306 FILE MESSAGE COUNTS LENGTH MUST BE A FIXED LENGTH Both
OF 8.
0456 PDS0306 FILE MESSAGE COUNTS IS NOT ZEROS, AND DOES NOT Both
EQUAL THE TOTAL NUMBER OF MESSAGES (INCLUDING FILE HEADER
AND FILE TRAILER) IN THE LOGICAL FILE.
0468 PDS0267 SECOND PRESENTMENT/FEE COLLECTION RESUBMISSION Both
DATA CANNOT BE ALL LOW-VALUES OR ALL HIGH-VALUES.
0469 PDS0267 SECOND PRESENTMENT/FEE COLLECTION RESUBMISSION Both
DATA MUST BE 004–127.
0476 PDS0146S7 AMOUNT, FEE, RECONCILIATION INVALID. MUST BE GCMS
NUMERIC AND CANNOT BE GREATER THAN DE5 AMOUNT,
RECONCILIATION.
0482 AMOUNT, PARTIAL TRANSACTION MUST BE NUMERIC AND GREATER Both
THAN ZEROS.
0483 PDS0506 TICKET NUMBER LENGTH MUST BE A FIXED LENGTH OF 15. Both
MESSAGE WHEN PDS0268 AMOUNT, PARTIAL TRANSACTION IS
PROVIDED.
0488 PDS0148 CURRENCY EXPONENT OCCURRENCE FOR PDS0268S2 Both
CURRENCY CODE, PARTIAL TRANSACTION MISSING. MUST BE
PROVIDED.


0489 PDS0301 FILE AMOUNT, CHECKSUM MUST BE NUMERIC. Both
0490 PDS0301 FILE AMOUNT, CHECKSUM LENGTH MUST BE A FIXED Both
LENGTH OF 16.
0491 PDS0552 CUSTOMER SERVICE TOLL-FREE (800) NUMBER, PDS0574 Both
ARRIVAL DATE, PDS0575 DEPARTURE DATE, PDS0576 FOLIO NUMBER,
AND PDS0577 PROPERTY PHONE NUMBER REQUIRED FOR LODGING
TRANS. SUBMITTED FOR U.S. REGION TRAVEL INDUSTRIES PREMIER
SERVICE INTERCHANGE PROGRAM.
0496 PDS0565 RENTAL LOCATION STATE/PROVINCE MUST BE LEFT Both
0497 IPM FILE HEADER/1644-697 MUST BE FIRST MESSAGE IN A PHYSICAL Both
TRANSMISSION.
0498 IPM FILE HEADER/1644-697 MESSAGE MISSING. MUST FOLLOW A FILE Both
TRAILER/1644-695.
0502 DE71 MESSAGE NUMBER IN FILE HEADER MUST BE 00000001. Both
0503 PDS0025 MESSAGE REVERSAL INDICATOR NOT ALLOWED IN FILE Both
TRAILER.
0505 PDS0266S1 MESSAGE REASON CODE MUST BE A VALID MESSAGE Both
REASON CODE OR ZEROS.
0507 IPM FILE TRAILER/1644-695 MESSAGE MUST BE THE LAST MESSAGE IN Both
A PHYSICAL TRANSMISSION.
0508 IPM FILE TRAILER/1644-695 MESSAGE MISSING. Both
0510 FILE TRAILER REJECTED BECAUSE ALL DETAILS IN FILE REJECTED. Both
0511 NO DETAILS PRESENT IN THE LOGICAL FILE. ONLY FILE HEADER Both
AND FILE TRAILER PRESENT.
0515 PDS0122 PROCESSING MODE MUST BE P FOR PRODUCTION GCMS
ENVIRONMENT; P OR T FOR TEST ENVIRONMENT.
0517 INVALID PDS0105 FILE ID IN FILE TRAILER. SHOULD BE THE SAME AS Both
THAT IN THE FILE HEADER.
0519 PDS0301 FILE AMOUNT, CHECKSUM IS NOT ZEROS, AND DOES NOT Both
EQUAL THE TOTAL OF AMOUNT, TRANSACTION (DE4) FROM EACH
DETAIL MESSAGE.
0521 ASSOCIATED FINANCIAL DETAIL ADDENDUM/1644 REJECTED. Both
0523 ACQUIRER NOT CERTIFIED BY MASTERCARD TO PROCESS ATM CASH Both
WITHDRAWAL TRANSACTIONS.
0528 PDS0191 ORIGINATING MESSAGE FORMAT INVALID. MUST BE 1 OR 2. Both


0531 DE26 CARD ACCEPTOR BUSINESS CODE (MCC) INVALID OR Both
OBSOLETE.
0539 DE43S3 CARD ACCEPTOR CITY MUST BE PRESENT. Both
0544 DE93 TRANSACTION DESTINATION INSTITUTION ID CODE IS Both
DESIGNATED FOR INTERNAL USE BY MASTERCARD.
0546 DE94 TRANSACTION ORIGINATOR INSTITUTION ID CODE/ACQUIRER Both
BIN (DE31S2) COMBINATION INVALID.
0547 DE94 TRANSACTION ORIGINATOR INSTITUTION ID CODE /DE2 Both
PRIMARY ACCOUNT NUMBER (PAN) COMBINATION INVALID.
0550 DE94 TRANSACTION ORIGINATOR INSTITUTION ID CODE IS Both
DESIGNATED AS AN ISSUER ONLY BY MASTERCARD.
0553 GAMING NOT ALLOWED. GCMS
0554 GAMING LOSS EXCEEDED. GCMS
0555 GAMING WIN EXCEEDED. GCMS
MUST BE PRESENT WHEN MESSAGE REVERSAL INDICATOR IS PRESENT
IN FIRST PRESENTMENT MESSAGE.
0564 INVALID FINANCIAL DETAIL ADDENDUM. Both
0565 PDS0501S4 MESSAGE NUMBER MUST CONTAIN THE SAME VALUE AS Both
DE71 IN THE ASSOCIATED FIRST PRESENTMENT.
0566 ASSOCIATED FIRST PRESENTMENT REJECTED. Both
0575 ISSUER HAS ACCEPTED THE ACQUIRER’S RESPONSE. GCMS
0577 DE63 TRANSACTION LIFE CYCLE ID MUST BE THE SAME IDENTIFIER Both
AS PROVIDED IN THE RELATED FIRST PRESENTMENT/1240.
0578 INVALID FINANCIAL DETAIL ADDENDUM/1644. ONLY 999 Both
OCCURRENCES FOR TRANSACTION DESCRIPTION DETAIL FOR EACH
COMBINATION OF USAGE CODE AND INDUSTRY RECORD NUMBER
ARE PERMITTED.
0580 FINANCIAL DETAIL ADDENDUM/1644 OUT OF SEQUENCE. Both
0586 DE43S4 CARD ACCEPTOR POSTAL CODE REQUIRED. Both
0588 DE25 MESSAGE REASON CODE INVALID FOR ATM CASH Both
WITHDRAWAL TRANSACTION. MUST BE SUBMITTED FOR DUPLICATE
PROCESSING (4834) OR SERVICES NOT RENDERED (4859).
0589 DE43S6 CARD ACCEPTOR COUNTRY CODE MUST BE COMPATIBLE Both
WITH DE43S5 STATE/PROVINCE/REGION CODE.


0591 PDS0172 SOLE PROPRIETOR NAME LENGTH MUST BE 001-015 Both
0592 DOCUMENTATION ALWAYS REQUIRED FOR THIS DE25 MESSAGE Both
REASON CODE.
0593 DE25 MESSAGE REASON CODE/TERMINAL TYPE COMBINATION Both
INVALID.
0595 DE25 MESSAGE REASON CODE NOT ALLOWED IF FIRST CHARGEBACK GCMS
WAS FOR REQUESTED TRANSACTION INFORMATION NOT RECEIVED.
0596 PDS0023 TERMINAL TYPE/PDS0158S4 INTERCHANGE RATE Both
DESIGNATOR CONFLICT.
0598 PDS0158S4 INTERCHANGE RATE DESIGNATOR INVALID FOR Both
CORPORATE PRODUCT.
0603 DE72 DATA RECORD LENGTH CANNOT EXCEED 999. Both
0609 DE94 TRANSACTION ORIGINATOR INSTITUTION ID CODE IS Both
DESIGNATED AS AN ACQUIRER ONLY BY MASTERCARD.
0612 PDS0262 DOCUMENTATION INDICATOR 0 ON PREVIOUS CYCLE. GCMS
0623 DE43S5 CARD ACCEPTOR STATE/PROVINCE/REGION CODE Both
REQUIRED.
0625 DE43S2 CARD ACCEPTOR STREET ADDRESS REQUIRED. Both
0630 DE25 MESSAGE REASON CODE INVALID. MESSAGE REASON CODE Both
RESERVED FOR SECOND PRESENTMENT (FULL), SECOND
PRESENTMENT (PARTIAL), ARBITRATION CHARGEBACKS (FULL),
ARBITRATION CHARGEBACKS (PARTIAL) MESSAGES ORIGINATING IN
THE INET FORMAT.
0631 PDS0158S4 INTERCHANGE RATE DESIGNATOR AND PROCESSING Both
CODE/REVERSAL INDICATOR COMBINATION INVALID FOR BUSINESS
SERVICE ARRANGEMENT <BUSINESS SERVICE ID & TYPE> AND
ACCEPTANCE BRAND ID CODE <AB>.
0638 ISSUER CANNOT CHARGEBACK FOR DE25 MESSAGE REASON CODE GCMS
4801 OR 4802.
0649 DUPLICATE DE95 CARD ISSUER REFERENCE DATA. GCMS
0650 PDS0595 CARD ACCEPTOR TYPE MUST BE LEFT JUSTIFIED AND Both
0660 PDS0158S4 INTERCHANGE RATE DESIGNATOR INVALID FOR T&E Both
CARD ACCEPTOR BUSINESS CODE.
0667 DE31S1 INTERCHANGE RATE DESIGNATOR MUST BE EQUAL TO GCMS
PDS0158 SUBFIELD 4 INTERCHANGE RATE DESIGNATOR.


0670 TIMELINESS ERROR. Both
FOR SERVICE INDUSTRY INTERCHANGE PROGRAM.
0676 PDS0538 ENDORSEMENTS/RESTRICTIONS LENGTH MUST BE 1-20. Both
0677 DE25 MESSAGE REASON CODE SHOULD HAVE BEEN 4802. GCMS
0686 EXCEEDS MAXIMUM TIMELINESS OF <NNN> DAYS. GCMS
The actual maximum number of days will replace <NNN> in the exception
message that members receive.
0687 DE24 FUNCTION CODE AND PDS0025 REVERSAL INDICATOR GCMS

0699 PDS0173 LEGAL CORPORATE NAME LENGTH MUST BE 1-30. Both
FOR INTERNATIONAL ELECTRONIC INTERCHANGE PROGRAM.
0702 PDS0158S4 INTERCHANGE RATE DESIGNATOR INVALID FOR WORLD Both
MASTERCARD INTERCHANGE RATE PROGRAM.
0703 LESS THAN THE MINIMUM TIMELINESS OF <NNN> DAYS. GCMS
The actual minimum number of days will replace <NNN> in the exception
0704 IMAGE REVIEW STILL PENDING GCMS

0711 SUPPORT DOCUMENTATION NOT REQUIRED. GCMS
FOR WAREHOUSE INTERCHANGE PROGRAM.
0720 EXCEEDS MAXIMUM TIMELINESS OF <NNN> DAYS. GCMS
The actual maximum number of days will replace <NNN> in the exception
0726 PREVIOUS CYCLE NOT ON FILE. GCMS

0733 TIMELINESS ERROR (AIRLINE). Both
0735 DE2 PRIMARY ACCOUNT NUMBER (PAN) MUST BE PRESENT IN FIRST Both
PRESENTMENT, FIRST CHARGEBACK (FULL), FIRST CHARGEBACK
(PARTIAL), SECOND PRESENTMENT (FULL), SECOND PRESENTMENT
(PARTIAL), ARBITRATION CHARGEBACK (FULL), ARBITRATION
CHARGEBACK (PARTIAL), RETRIEVAL REQUEST, OR FEE COLLECTION
(RETRIEVAL FEE BILLING) MESSAGES.


0735 DE3 PROCESSING CODE MUST BE PRESENT IN FIRST PRESENTMENT, Both
FIRST CHARGEBACK (FULL), FIRST CHARGEBACK (PARTIAL), SECOND
PRESENTMENT (FULL), SECOND PRESENTMENT (PARTIAL),
ARBITRATION CHARGEBACK (FULL), ARBITRATION CHARGEBACK
(PARTIAL), RETRIEVAL REQUEST, FEE COLLECTION (RETRIEVAL FEE
BILLING), OR FEE COLLECTION (OTHER) MESSAGES.
DE4 AMOUNT, TRANSACTION MUST BE PRESENT IN FIRST Both
CHARGEBACK (PARTIAL), FEE COLLECTION (OTHER) MESSAGES.
DE24 FUNCTION CODE MUST BE PRESENT IN FIRST PRESENTMENT, Both
BILLING), FEE COLLECTION (OTHER), FILE HEADER, FILE TRAILER, OR
FINANCIAL DETAIL ADDENDUM MESSAGES.
DE25 MESSAGE REASON CODE MUST BE PRESENT IN FIRST Both
CHARGEBACK (PARTIAL), RETRIEVAL REQUEST, FEE COLLECTION
(RETRIEVAL FEE BILLING), OR FEE COLLECTION (OTHER) MESSAGES.
DE26 CARD ACCEPTOR BUSINESS CODE (MCC) MUST BE PRESENT IN Both
FIRST PRESENTMENT, FIRST CHARGEBACK (FULL), FIRST
CHARGEBACK (PARTIAL), SECOND PRESENTMENT (FULL), SECOND
PRESENTMENT (PARTIAL), ARBITRATION CHARGEBACK (FULL), OR
ARBITRATION CHARGEBACK (PARTIAL) MESSAGES.
DE30 AMOUNTS, ORIGINAL MUST BE PRESENT IN FIRST CHARGEBACK Both
(FULL), FIRST CHARGEBACK (PARTIAL), SECOND PRESENTMENT
(FULL), SECOND PRESENTMENT (PARTIAL), ARBITRATION
CHARGEBACK (FULL), ARBITRATION CHARGEBACK (PARTIAL),
RETRIEVAL REQUEST, OR FEE COLLECTION (RETRIEVAL FEE BILLING)
MESSAGES.
DE30 AMOUNTS, ORIGINAL MUST BE PRESENT. Both
DE31 ACQUIRER REFERENCE DATA MUST BE PRESENT IN FIRST Both


0735 DE33 FORWARDING INSTITUTION ID CODE MUST BE PRESENT IN Both
FIRST PRESENTMENT, FIRST CHARGEBACK (FULL), FIRST
PRESENTMENT (PARTIAL), ARBITRATION CHARGEBACK (FULL),
ARBITRATION CHARGEBACK (PARTIAL), RETRIEVAL REQUEST, FEE
COLLECTION (RETRIEVAL FEE BILLING), FEE COLLECTION (OTHER),
OR FINANCIAL DETAIL ADDENDUM MESSAGES.
DE41 CARD ACCEPTOR TERMINAL ID MUST BE PRESENT. Both
DE43S1 CARD ACCEPTOR NAME MUST BE PRESENT IN FIRST Both
(PARTIAL), ARBITRATION CHARGEBACK (FULL), OR ARBITRATION
CHARGEBACK (PARTIAL) MESSAGES.
DE48 ADDITIONAL DATA MUST BE PRESENT IN FIRST PRESENTMENT, Both
DE49 CURRENCY CODE, TRANSACTION MUST BE PRESENT IN FIRST Both
CHARGEBACK (PARTIAL), OR FEE COLLECTION (OTHER) MESSAGES.
DE71 MESSAGE NUMBER MUST BE PRESENT IN FIRST PRESENTMENT, Both
DE73 DATE, ACTION MUST BE PRESENT IN FEE COLLECTION Both
DE93 TRANSACTION DESTINATION INSTITUTION ID CODE MUST BE Both
PRESENT IN FEE COLLECTION (RETRIEVAL FEE BILLING), OR FEE
COLLECTION (OTHER) MESSAGES.


0735 DE94 TRANSACTION ORIGINATOR INSTITUTION ID CODE MUST BE Both
PRESENT IN FIRST PRESENTMENT, FIRST CHARGEBACK (FULL), FIRST
ARBITRATION CHARGEBACK (PARTIAL), RETRIEVAL REQUEST, FEE
COLLECTION (RETRIEVAL FEE BILLING), OR FEE COLLECTION
(OTHER) MESSAGES.
DE95 CARD ISSUER REFERENCE DATA MUST BE PRESENT IN FIRST Both
CHARGEBACK (FULL), FIRST CHARGEBACK (PARTIAL), SECOND
ARBITRATION CHARGEBACK (FULL), OR ARBITRATION CHARGEBACK
(PARTIAL) MESSAGES.
PDS0105 FILE ID MISSING. MUST BE PRESENT IN FILE HEADER AND Both
FILE TRAILER MESSAGES.
PDS0137 FEE COLLECTION MUST BE PRESENT IN FEE COLLECTION Both
(OTHER) MESSAGES.
PDS0137 FEE COLLECTION CONTROL NUMBER MUST BE PRESENT. Both
PDS0148 CURRENCY EXPONENTS MUST BE PRESENT IN FIRST Both
(OTHER) MESSAGES.
PDS0149 CURRENCY CODES, AMOUNTS, ORIGINAL MUST BE PRESENT. Both
PDS0149 CURRENCY CODES, AMOUNTS, ORIGINAL MISSING MUST BE Both
PRESENT IN FIRST CHARGEBACK (FULL), FIRST CHARGEBACK
PDS0158 BUSINESS ACTIVITY MUST BE PRESENT IN FIRST Both
PDS0165 SETTLEMENT INDICATOR MUST BE PRESENT IN FIRST Both
CHARGEBACK (PARTIAL), RETRIEVAL REQUEST, FEE COLLECTION
(RETRIEVAL FEE BILLING), OR FEE COLLECTION (OTHER) MESSAGES.


0735 PDS0230 FULFILLMENT DOCUMENT CODE MUST BE PRESENT IN FEE Both
COLLECTION (RETRIEVAL FEE BILLING) MESSAGES.
PDS0262 DOCUMENTATION INDICATOR MUST BE PRESENT IN FIRST Both
CHARGEBACK (FULL), FIRST CHARGEBACK (PARTIAL), SECOND
ARBITRATION CHARGEBACK (FULL), OR ARBITRATION CHARGEBACK
(PARTIAL) MESSAGES.
PDS0264 ORIGINAL RETRIEVAL REASON FOR REQUEST MUST BE Both
PRESENT IN FEE COLLECTION (RETRIEVAL FEE BILLING) MESSAGES.
PDS0301 FILE AMOUNT, CHECKSUM MUST BE PRESENT IN FILE Both
TRAILER MESSAGES.
PDS0306 FILE MESSAGE COUNTS MUST BE PRESENT IN FILE TRAILER Both
MESSAGES.
PDS0501 TRANSACTION DESCRIPTION MUST BE PRESENT IN Both
0738 DE4 AMOUNT, TRANSACTION EXCEEDS MAXIMUM AMOUNT GCMS
SPECIFIED FOR THE GIVEN DE25 MESSAGE REASON CODE.
0741 THE ISSUER HAS NOT ACCEPTED/REJECTED THE FULFILLMENT. GCMS
0747 INVALID DATE, ACTION. MUST BE VALID YYMMDD, YYMM00, OR ALL Both
ZEROS.
0753 REQUIRED SUPPORT DOCUMENTATION PROVIDED. GCMS
0756 PDS0137 FEE COLLECTION CONTROL NUMBER LENGTH MUST BE Both
17–20.
0766 DE42 CARD ACCEPTOR ID CODE MUST BE PRESENT. Both
0769 PDS0158S4 INTERCHANGE RATE DESIGNATOR INVALID FOR FLEET Both
TRANSACTION AT FUEL LOCATION.
0780 DE38 APPROVAL CODE MUST BE PRESENT. Both
0781 PDS0526 CONJUNCTION TICKET MUST BE LEFT JUSTIFIED AND Both
0782 PDS0527 EXCHANGE TICKET MUST BE LEFT JUSTIFIED AND CANNOT Both
CONTAIN ALL SPACES.
0783 PDS0528 COUPON NUMBER CANNOT BE ALL LOW-VALUES OR ALL Both
HIGH-VALUES.
0784 PDS0530 FLIGHT NUMBER CANNOT BE ALL LOW-VALUES OR ALL Both
HIGH-VALUES.


0785 PDS0531S1 DEPARTURE TIME INVALID. MUST BE IN THE FORMAT Both
HHMM. HOURS MUST BE 00-23 AND MINUTES MUST BE 00-59.
0786 PDS0531S2 DEPARTURE TIME SEGMENT INVALID. MUST BE A, P, OR A Both
SPACE.
0789 PDS0561S2 ADJUSTED AMOUNT CANNOT EQUAL ALL SPACES OR ALL Both
ZEROS IF PDS0561S1 ADJUSTED AMOUNT INDICATOR IS EQUAL TO A,
B, C, D, E OR X.
0790 INVALID DE33 FORWARDING INSTITUTION ID CODE FOR FIRST Both
PRESENTMENT, SECOND PRESENTMENT, FIRST CHARGEBACK (FULL),
FIRST CHARGEBACK (PARTIAL), ARBITRATION CHARGEBACK (FULL),
ARBITRATION CHARGEBACK (PARTIAL), RETRIEVAL REQUESTS,
FINANCIAL DETAIL ADDENDUM, FEE COLLECTION (RETURN FEE
BILLING), AND FEE COLLECTION (OTHER) MESSAGES.
0792 PDS0538 ENDORSEMENTS/RESTRICTIONS MUST BE LEFT JUSTIFIED Both
0808 DE33 FORWARDING INSTITUTION ID CODE MUST BE NUMERIC. Both
0823 PDS0191 ORIGINATING MESSAGE FORMAT LENGTH MUST BE A FIXED Both
LENGTH OF 001.
0825 PDS0241 MASTERCOM CONTROL NUMBER LENGTH MUST BE 002 OR Both
007.
0826 PDS0266 FIRST CHARGEBACK/FEE COLLECTION RETURN DATA MUST Both
BE 004–127.
0827 PDS0501 TRANSACTION DESCRIPTION LENGTH MUST BE A FIXED Both
LENGTH OF 016.
0828 PDS0505 PASSENGER NAME LENGTH MUST BE 1-29. Both
0829 PDS0507 ISSUING CARRIER MUST BE A FIXED LENGTH OF 004. Both
0830 PDS0509 ISSUE DATE MUST BE A FIXED LENGTH OF 006. Both
0831 PDS0510 TRAVEL AGENCY CODE MUST BE A FIXED LENGTH OF 008. Both
0832 PDS0512 TOTAL FARE MUST BE A FIXED LENGTH OF 012. Both
0833 PDS0513 TOTAL FEES MUST BE A FIXED LENGTH OF 012. Both
0834 PDS0514 TOTAL TAXES MUST BE A FIXED LENGTH OF 012. Both
0835 PDS0520 TRAVEL DATE MUST BE A FIXED LENGTH OF 006. Both
0837 PDS0522 SERVICE CLASS CODE MUST BE A FIXED LENGTH OF 002. Both
0838 PDS0523 CITY OF ORIGIN/AIRPORT CODE MUST BE A FIXED LENGTH Both
OF 005.


0839 PDS0524 CITY OF DESTINATION/AIRPORT CODE MUST BE A FIXED Both
LENGTH OF 005.
0840 PDS0525 STOP OVER CODE MUST BE A FIXED LENGTH OF 001. Both
0841 PDS0526 CONJUNCTION TICKET MUST BE A FIXED LENGTH OF 015. Both
0842 PDS0527 EXCHANGE TICKET MUST BE A FIXED LENGTH OF 015. Both
0843 PDS0528 COUPON NUMBER MUST BE A FIXED LENGTH OF 001. Both
0844 PDS0530 FLIGHT NUMBER MUST BE A FIXED LENGTH OF 005. Both
0845 PDS0531 DEPARTURE TIME MUST BE A FIXED LENGTH OF 005. Both
0846 PDS0533 ARRIVAL TIME MUST BE A FIXED LENGTH OF 005. Both
0847 PDS0535 FARE MUST BE A FIXED LENGTH OF 012. Both
0848 PDS0536 FEE MUST BE A FIXED LENGTH OF 012. Both
0849 PDS0537 TAXES MUST BE A FIXED LENGTH OF 012. Both
0850 PDS0544 RENTAL AGREEMENT NUMBER MUST BE A FIXED LENGTH OF Both
009.
0851 PDS0547 RENTAL RETURN STATE/PROVINCE MUST BE A FIXED Both
LENGTH OF 003.
0852 PDS0548 RENTAL RETURN COUNTRY MUST BE A FIXED LENGTH OF Both
003.
0853 PDS0549 RENTAL RETURN LOCATION ID MUST BE A FIXED LENGTH Both
OF 010.
0854 PDS0550 RENTAL RETURN DATE MUST BE A FIXED LENGTH OF 006. Both
0855 PDS0551 RENTAL CHECKOUT DATE MUST BE A FIXED LENGTH OF Both
006.
0857 PDS0553 RENTAL RATE MUST BE A FIXED LENGTH OF 013. Both
0858 PDS0555 RATE PER MILE (OR PER KILOMETER) MUST BE A FIXED Both
LENGTH OF 012.
0859 PDS0556 TOTAL MILES (OR KILOMETERS) MUST BE A FIXED LENGTH Both
OF 004.
0860 PDS0557 MAXIMUM FREE MILES (OR KILOMETERS) MUST BE A FIXED Both
LENGTH OF 004.
0861 PDS0558 MILES/KILOMETER INDICATOR MUST BE A FIXED LENGTH Both
OF 001.
0862 PDS0559 VEHICLE INSURANCE MUST BE A FIXED LENGTH OF 013. Both


0863 PDS0561 ADJUSTED AMOUNT MUST BE A FIXED LENGTH OF 013. Both
0865 PDS0563 PROGRAM CODE MUST BE A FIXED LENGTH OF 002. Both
0866 PDS0565 RENTAL LOCATION STATE/PROVINCE MUST BE A FIXED Both
LENGTH OF 003.
0867 PDS0565 RENTAL LOCATION STATE/PROVINCE MUST CONTAIN A Both
VALID U.S. STATE/PROVINCE CODE IF PDS0566 RENTAL LOCATION
COUNTRY CONTAINS “USA”.
0868 PDS0574 ARRIVAL DATE MUST BE A FIXED LENGTH OF 006. Both
0869 PDS0575 DEPARTURE DATE MUST BE A FIXED LENGTH OF 006. Both
0875 PDS0582 PROGRAM CODE MUST BE A FIXED LENGTH OF 002. Both
0883 PDS0598 TOTAL TAX COLLECTED INDICATOR MUST BE A FIXED Both
LENGTH OF 001.
0886 PDS0608 DESTINATION POSTAL CODE MUST BE A FIXED LENGTH OF Both
010.
0887 PDS0609 DESTINATION STATE/PROVINCE CODE MUST BE A FIXED Both
LENGTH OF 003.
0888 PDS0609 DESTINATION STATE/PROVINCE CODE INVALID. MUST Both
CONTAIN A VALID U.S. STATE CODE.
0889 PDS0610 DESTINATION COUNTRY CODE MUST BE A FIXED LENGTH Both
OF 003.
0890 PDS0610 DESTINATION COUNTRY CODE INVALID. MUST CONTAIN A Both
VALID COUNTRY CODE.
0893 PDS0613 SHIP-FROM POSTAL CODE MUST BE A FIXED LENGTH OF Both
010.
0894 PDS0614 ORDER DATE LENGTH MUST BE A FIXED LENGTH OF 006. Both
0895 PDS0620 OIL COMPANY BRAND NAME MUST BE A FIXED LENGTH OF Both
004.
0896 PDS0621 PURCHASE TIME MUST BE A FIXED LENGTH OF 004. Both
0897 PDS0622 MOTOR FUEL SERVICE TYPE MUST BE A FIXED LENGTH OF Both
001.
0903 PDS0632 PRODUCT TYPE CODE MUST BE A FIXED LENGTH OF 001. Both
0904 PDS0633 COUPON/DISCOUNT AMOUNT MUST BE A FIXED LENGTH Both
OF 012.
0905 PDS0634 TAX AMOUNT 1 MUST BE A FIXED LENGTH OF 006. Both


0906 PDS0635 TAX AMOUNT 2 MUST BE A FIXED LENGTH OF 006. Both
0907 PDS0643 ITEM QUANTITY MUST BE A FIXED LENGTH OF 013. Both
0908 PDS0646 UNIT PRICE MUST BE A FIXED LENGTH OF 013. Both
0911 PDS0650 NET/GROSS INDICATOR FOR EXTENDED ITEM AMOUNT Both
0912 PDS0651 TAX RATE APPLIED MUST BE A FIXED LENGTH OF 005. Both
0913 PDS0652 TAX TYPE APPLIED MUST BE A FIXED LENGTH OF 004. Both
0914 PDS0653 TAX AMOUNT MUST BE A FIXED LENGTH OF 012. Both
0915 PDS0656 ALTERNATE TAX ID MUST BE A FIXED LENGTH OF 015. Both
0916 PDS0657 ITEM DISCOUNT RATE MUST BE A FIXED LENGTH OF 005. Both
0917 PDS0505 PASSENGER NAME, PDS0506 TICKET NUMBER, AND PDS0507 Both
ISSUING CARRIER REQUIRED FOR AIRLINE TRANSACTIONS
SUBMITTED FOR MERIT I, WORLD CARD T&E, PASSENGER TRANSPORT
OR CORP. T&E II INTERCHANGE PROGRAMS.
0920 PDS0520 TRAVEL DATE, PDS0521 CARRIER CODE, PDS0522 SERVICE Both
CLASS CODE, PDS0523 CITY OF ORIGIN/AIRPORT CODE, AND PDS0524
CITY OF DESTINATION/AIRPORT CODE REQUIRED FOR AIRLINE
TRANSACTIONS SUBMITTED FOR U.S. MERIT III, WORLD T&E,
PASSENGER TRANSPORT OR CORPORATE T&E II INTERCHANGE
PROGRAMS.
0925 PDS0529 FARE BASIS CODE LENGTH MUST BE 1-15. Both
0927 PDS0533S2 ARRIVAL TIME SEGMENT INVALID. MUST BE A, P, OR A Both
SPACE.
0928 PDS0544 RENTAL AGREEMENT NUMBER, PDS0545 RENTER NAME, Both
PDS0546 RENTAL RETURN CITY, PDS0547 RENTAL RETURN
STATE/PROVINCE, PDS0548 RENTAL RETURN COUNTRY, PDS0549
RENTAL RETURN LOCATION ID, PDS0550 RENTAL RETURN DATE,
PDS0551 RENTAL CHECK-OUT DATE, AND PDS0552 CUSTOMER
SERVICE TOLL-FREE NUMBER REQUIRED FOR U.S. REGION TRAVEL
INDUSTRIES PREMIER SERVICE OR CORPORATE T&E RATE II
0930 PDS0545 RENTER NAME, PDS0546 RENTAL RETURN CITY, PDS0547 Both
RENTAL RETURN STATE/PROVINCE, PDS0548 RENTAL RETURN
COUNTRY, PDS0550 RENTAL RETURN DATE, PDS0551 RENTAL CHECK-
OUT DATE, AND PDS0552 CUSTOMER SERVICE TOLL-FREE NUMBER
REQUIRED FOR WORLD MASTERCARD T&E INTERCHANGE PROGRAM.
0939 PDS0553S2 RENTAL RATE INVALID. MUST BE NUMERIC. Both


0940 PDS0553S1 RENTAL RATE INDICATOR MUST BE D, W, OR M. Both
0941 PDS0559S2 INSURANCE CHARGES CANNOT EQUAL ALL SPACES OR ALL Both
ZEROS IF INSURANCE INDICATOR IS EQUAL TO "Y".
0947 PDS0595 CARD ACCEPTOR TYPE AND PDS0596 MERCHANT TAX ID Both
REQUIRED FOR U.S. REGION CORPORATE LARGE TICKET, FACE TO
FACE, DATA RATE II, OR DATA RATE III INTERCHANGE PROGRAMS.
0948 PDS0596 CARD ACCEPTOR TAX ID AND PDS0597 TAX AMOUNT Both
REQUIRED FOR THE INTERNATIONAL CORPORATE PURCHASING
DATA RATE II INTERCHANGE PROGRAMS.
0951 PDS0600 CARD ACCEPTOR REFERENCE NUMBER LENGTH MUST BE Both
001–025.
0953 PDS0620 OIL COMPANY BRAND NAME, PDS0621 PURCHASE TIME, AND Both
PDS0632 PRODUCT TYPE CODE REQUIRED FOR FLEET CARD AT FUEL
LOCATION TRANSACTIONS SUBMITTED FOR THE U.S. REGION
CORPORATE LARGE TICKET OR DATA RATE II INTERCHANGE
PROGRAMS.
0960 PDS0629 ODOMETER READING LENGTH MUST BE 1-7. Both
0961 PDS0630 VEHICLE NUMBER LENGTH MUST BE 1-17. Both
0962 PDS0631 DRIVER NUMBER/ID NUMBER LENGTH MUST BE 1-17. Both
0963 PDS0641 PRODUCT CODE LENGTH MUST BE 1-15. Both
0964 PDS0642 ITEM DESCRIPTION LENGTH MUST BE 1-35. Both
0965 PDS0645 ITEM UNIT OF MEASURE LENGTH MUST BE 1-12. Both
0966 PDS0648S2 DISCOUNT AMOUNT CANNOT EQUAL ALL ZEROS IF Both
PDS0648S1 DISCOUNT INDICATOR IS EQUAL TO “Y”.
0967 PDS0663 FREE-FORM DESCRIPTION LENGTH MUST BE 001-992. Both
0971 PDS0501S3 OCCURRENCE INDICATOR INVALID. MUST BE EQUAL TO Both
“001” FOR USAGE CODE “01” AND INDUSTRY RECORD NUMBER “000”.
0972 PDS0501S3 OCCURRENCE INDICATOR INVALID. MUST BE IN THE Both
RANGE OF “002-099” FOR USAGE CODE 01 AND INDUSTRY RECORD
NUMBER “001”.
“001” FOR USAGE CODE “98” AND INDUSTRY RECORD NUMBER “000”.
“001” FOR USAGE CODE 98 AND INDUSTRY RECORD NUMBER “002”.


0976 PDS0501S3 OCCURRENCE INDICATOR MUST BE IN THE RANGE OF Both
“002-999” FOR USAGE CODE 98 AND INDUSTRY RECORD NUMBER
“950”.
0978 DE/PDS TAG INVALID. MUST BE A VALID, NUMERIC DE/PDS ID. Both
0982 PDS0511 TRAVEL AGENCY NAME LENGTH MUST BE 1-25. Both
0983 PDS0663 FREE-FORM DESCRIPTION CANNOT BE ALL SPACES. Both
0984 PDS0521 CARRIER CODE MUST BE A FIXED LENGTH OF 002. Both
0985 LENGTH FIELD INVALID. MUST BE NUMERIC. Both
0986 DE26 CARD ACCEPTOR BUSINESS CODE (MCC) INVALID. MUST BE Both
6011 AUTOMATED CASH DISBURSEMENT FOR DE3 SUBFIELD 1,
PROCESSING CODE 01.
0987 DUPLICATE OCCURRENCE OF PDSXXX IN A SINGLE MESSAGE. Both
DESIGNATED AS UNIQUE FOR DE3 SUBFIELD 1, PROCESSING CODE
18.
0990 UNPARSEABLE MESSAGE. TOO MANY TAGS TO TAG TABLE. Both
0991 UNPARSEABLE MESSAGE. NO PDS DEFINED WITH THIS NUMBER. Both
0992 UNPARSEABLE MESSAGE. NO \ AT END OF SUBFIELD. Both
0993 MISSING SECOND BITMAP. Both

0994 NON-NUMERIC PDS ID. Both
0997 NON-NUMERIC LENGTH FIELD. Both
1012 THRESHOLDS EXCEEDED. FILE REJECTED. Pre-edit
1013 RERUN FILE ID NOT PRESENT ON FILE ID HISTORY FILE. Pre-edit
1014 DE3S1 CARDHOLDER TRANSACTION TYPE INVALID. MUST BE EQUAL Both
TO 19 FOR FEE COLLECTION (RETRIEVAL FEE BILLING) MESSAGES.
1015 DE3S1 CARDHOLDER TRANSACTION TYPE INVALID. MUST BE EQUAL Both
TO 19 OR 29 FOR FEE COLLECTION (OTHER) MESSAGES.
1016 DE30 AMOUNTS, ORIGINAL MUST BE PRESENT AND NON-ZERO IN Both
RETRIEVAL REQUEST, FEE COLLECTION (RETRIEVAL FEE BILLING),
ARBITRATION CHARGEBACK (FULL), AND ARBITRATION


1016 DE30S2 AMOUNTS ORIGINAL MUST BE PRESENT AND NONZERO IN Both
FIRST PRESENTMENT MESSAGES.
1017 DE12S1 DATE LOCAL TRANSACTION IN DATE AND TIME, LOCAL Both
TRANSACTION INVALID. MUST BE VALID YYMMDD IN FIRST
PRESENTMENT MESSAGES IF TIMELINESS EDITS ARE PERFORMED.
1019 DE30 AMOUNTS, ORIGINAL MUST BE NUMERIC. Both
1022 PDS0105S3 PROCESSOR ID INVALID. Both
1023 PDS0146 AMOUNTS, TRANSACTION FEE MUST BE PRESENT. Both
1024 PDS0507 ISSUING CARRIER MUST BE LEFT JUSTIFIED AND CANNOT Both
CONTAIN ALL SPACES.
1027 PDS0538 ENDORSEMENTS/RESTRICTIONS CANNOT BE ALL LOW- Both
1031 INVALID CORPORATE ADDENDUM. CORPORATE ADDENDUM Both
INFORMATION CAN ONLY BE USED WITH A CORPORATE ACCOUNT
RANGE.
1032 PDS0566 RENTAL LOCATION COUNTRY MUST CONTAIN A VALID ISO Both
STANDARD COUNTRY CODE.
1034 PDS0623 MOTOR FUEL INFORMATION REQUIRED FOR FLEET CARD AT Both
FUEL LOCATION TRANS. SUBMITTED FOR THE U.S.REGION CORP.
LARGE TICKET, DATA RATE I OR II INTERCHANGE PROGRAMS IN
WHICH PDS622 CONTAINS A VALUE OTHER THAN 3.
1036 PDS0505 PASSENGER NAME, PDS0506 TICKET NUMBER, AND PDS0507 Both
ISSUING CARRIER REQUIRED FOR PASSENGER RAILWAY
TRANSACTIONS SUBMITTED FOR CORP. T&E RATE I & II, WORLD
CARD T&E, MERIT I OR PASSENGER TRANSPORT INTERCHANGE
PROGRAMS.
1037 PDS0529 FARE BASIS CODE CANNOT CONTAIN ALL SPACES. Both
1038 PDS0533S1 ARRIVAL TIME INVALID. MUST BE IN THE FORMAT HHMM. Both
HOURS MUST BE 00-23 AND MINUTES MUST BE 00-59.
1042 PDS0549 RENTAL RETURN LOCATION ID MUST BE LEFT JUSTIFIED Both
1043 PDS0552 CUSTOMER SERVICE TOLL-FREE (800) NUMBER CANNOT BE Both
ALL ZEROS OR ALL SPACES.
1044 PDS0566 RENTAL LOCATION COUNTRY MUST BE LEFT JUSTIFIED AND Both
1045 PDS0576 FOLIO NUMBER MUST BE LEFT JUSTIFIED AND CANNOT Both
CONTAIN ALL SPACES.


1046 PDS0577 PROPERTY PHONE NUMBER CANNOT BE ALL ZEROS OR ALL Both
SPACES.
1048 PDS 0501S1 USAGE CODE MUST BE NUMERIC. Both
1051 PDS0520 TRAVEL DATE, PDS0521 CARRIER CODE, PDS0522 SERVICE Both
CLASS CODE, PDS0523 CITY OF ORIGIN/AIRPORT CODE, AND PDS0524
CITY OF DESTINATION/AIRPORT CODE REQUIRED FOR PASSENGER
RAILWAY TRANSACTIONS SUBMITTED FOR U.S. REGION MERIT III,
CORPORATE T&E RATE II, WORLD CARD T&E OR PASSENGER
TRANSPORT INTERCHANGE PROGRAMS.
1053 DE4 AMOUNT, TRANSACTION LESS THAN OR EQUAL TO WORLD Both
CARD CHARGEBACK MINIMUM AMOUNT.
1054 PDS0623S4 MOTOR FUEL QUANTITY MUST BE NUMERIC AND Both
GREATER THAN ZERO.
1057 DE 55 INTEGRATED CIRCUIT CARD (ICC) SYSTEM-RELATED DATA Both
LENGTH MUST BE 1-255.
1059 PDS0146S4 CURRENCY CODE, FEE MUST CONTAIN A VALID NUMERIC Both
ISO-STANDARD CURRENCY CODE. OCCURRENCE <XX>.
1065 PDS0020 ISSUER CURRENCY CONVERSION RATE (ICCR) EFFECTIVE Both

DATE MUST BE A VALID DATE IN THE FORMAT YYMMDD.
1066 DE3 PROCESSING CODE AND PDS0165S1 SETTLEMENT INDICATOR Both
6012 MERCHANDISE & SERVICES FOR DE3 SUBFIELD 1, PROCESSING
CODE 17 OR 50.
1073 PASSENGER TRANSPORT DETAIL-GENERAL TICKET INFORMATION Both
ADDENDUM REQUIRED FOR INTERCHANGE PROGRAM.
1074 PASSENGER TRANSPORT DETAIL-TRIP LEG DATA ADDENDUM Both
REQUIRED FOR INTERCHANGE PROGRAM.
1075 VEHICLE RENTAL DETAIL ADDENDUM REQUIRED FOR INTERCHANGE Both
PROGRAM.
1076 LODGING DETAIL ADDENDUM REQUIRED FOR INTERCHANGE Both
PROGRAM.
1077 CORPORATE CARD COMMON DATA REQUIRED FOR INTERCHANGE Both
RATE PROGRAM.


1078 CORPORATE DETAIL-CORPORATE FLEET TRANSACTION Both
INFORMATION ADDENDUM REQUIRED FOR INTERCHANGE
PROGRAM.
1079 CORPORATE LINE ITEM DETAIL REQUIRED FOR INTERCHANGE Both
PROGRAM.
1080 PDS0020 ISSUER CURRENCY CONVERSION RATE (ICCR) EFFECTIVE Both
DATE LENGTH MUST BE A FIXED LENGTH OF 006.
1081 PDS0599 CORPORATION VAT NUMBER MUST BE LEFT JUSTIFIED AND Both
1083 PDS0567 RENTAL LOCATION ID MUST BE LEFT JUSTIFIED AND Both
1084 PDS0241 MASTERCOM CONTROL NUMBER MUST BE A FIXED LENGTH Both
OF 002.
1086 DE49 CURRENCY CODE FOR FIRST CHARGEBACK (FULL), FIRST GCMS
ARBITRATION CHARGEBACK (PARTIAL), AND FEE COLLECTION
(OTHER) MESSAGES MUST CONTAIN A VALUE OF 840 OR THE INTRA-
CURRENCY AGREEMENT SETTLEMENT CURRENCY CODE.
1087 DE31S2 ACQUIRER’S BIN NOT A VALID ACQUIRER BIN. Both
1088 PDS0596S1 CARD ACCEPTOR TAX ID CANNOT CONTAIN ALL SPACES Both
FOR INTERNATIONAL CORPORATE PURCHASING DATA RATE II
INTERCHANGE PROGRAMS.
1089 PDS0632 PRODUCT TYPE CODE INVALID. SHOULD BE 1-5. Both
1090 PDS0596S1 CARD ACCEPTOR TAX ID CANNOT CONTAIN ALL ZEROS, Both
ALL NINES, OR ALL SPACES FOR U.S. REGION CORP. LARGE TICKET,
FACE-TO-FACE, DATA RATE II OR DATA RATE III INTERCHANGE.
1092 PDS0023 TERMINAL TYPE MISSING. MUST BE PRESENT IN NON- Both
REVERSAL FIRST PRESENTMENT, FIRST CHARGEBACK (FULL), FIRST
PRESENTMENT (PARTIAL), ARBITRATION CHARGEBACK (FULL), OR
ARBITRATION CHARGEBACK (PARTIAL) MESSAGES.
1093 PDS0022 RECURRING PAYMENT INDICATOR INVALID. MUST BE 4. Both
1100 DE63 TRANSACTION LIFE CYCLE ID MUST BE PRESENT FOR US Both
ACQUIRED INCENTIVE INTERCHANGE PROGRAM.
1102 PDS0146S3 FEE SETTLEMENT INDICATOR MUST BE 00 OR 01. Both
1105 DE26 CARD ACCEPTOR BUSINESS CODE INVALID FOR PAYMENT Both
TRANSACTION INTERCHANGE RATE PROGRAM.


1106 PAYMENT TRANSACTION NOT ALLOWED. GCMS
1120 PDS0026S1 FILE REVERSAL INDICATOR MUST BE EQUAL TO R IF Both
PRESENT.
1121 PDS0026S2 CENTRAL SITE PROCESSING DATE OF ORIGINAL FILE MUST Both
BE NUMERIC AND A VALID DATE IN THE FORMAT YYMMDD.
1122 PDS0026S2 CENTRAL SITE PROCESSING DATE OF ORIGINAL FILE Both
INVALID. CANNOT BE GREATER THAN THE SYSTEM PROCESSING
DATE.
1123 PDS0535 FARE MUST BE NUMERIC AND RIGHT-JUSTIFIED. Both
1124 PDS0536 FEE MUST BE NUMERIC AND RIGHT-JUSTIFIED. Both
1125 PDS0537 TAXES MUST BE NUMERIC AND RIGHT-JUSTIFIED. Both
1126 PDS0575 DEPARTURE DATE MUST BE A VALID DATE IN THE FORMAT Both
YYMMDD.
1127 PDS0507 ISSUING CARRIER CANNOT BE ALL LOW-VALUES OR ALL Both
HIGH-VALUES.
1128 PDS0521 CARRIER CODE CANNOT BE ALL LOW-VALUES OR ALL HIGH- Both
VALUES.
1129 PDS0510 TRAVEL AGENCY CODE MUST BE LEFT JUSTIFIED AND Both
1130 PDS0511 TRAVEL AGENCY NAME MUST BE LEFT JUSTIFIED AND Both
1132 PDS0268 AMOUNT, PARTIAL TRANSACTION LENGTH MUST BE A FIXED Both
LENGTH OF 15.
1133 PDS0566 RENTAL LOCATION COUNTRY MUST BE A FIXED LENGTH OF Both
003.
1134 PDS0567 RENTAL LOCATION ID MUST BE A FIXED LENGTH OF 010. Both
1135 PDS0568 RENTAL CLASS ID MUST BE A FIXED LENGTH OF 004. Both
1137 PDS0597 TOTAL TAX AMOUNT REQUIRED FOR U.S. REGION Both
CORPORATE LARGE TICKET, FACE TO FACE, DATA RATE II, OR DATA
RATE III INTERCHANGE PROGRAMS.
6010 MANUAL CASH DISBURSEMENT FOR DE3 SUBFIELD 1,
PROCESSING CODE 12.
1140 ATM CHARGEBACKS MUST BE SENT TO ATM ACQUIRERS. Both


1142 ISSUER CURRENCY CONVERSION RATE (ICCR) EFFECTIVE DATE NOT GCMS
ON FILE.
1151 PDS 0172 SOLE PROPRIETOR NAME MUST BE LEFT JUSTIFIED AND Both
1152 PDS0173 LEGAL CORPORATE NAME MUST BE LEFT JUSTIFIED AND Both
1154 DE93 TRANSACTION DESTINATION INSTITUTION ID CODE MUST BE GCMS
AN ATM ISSUER IF THE TRANSACTION IS AN ATM CASH
WITHDRAWAL.
1155 DE93 TRANSACTION DESTINATION INSTITUTION ID CODE CANNOT GCMS
BE FLAGGED FOR INTERNAL USE ONLY.
1156 ATM RETRIEVAL REQUESTS MUST BE SENT TO ATM ACQUIRERS. GCMS
1157 DE93 TRANSACTION DESTINATION INSTITUTION ID CODE MUST BE A GCMS
SUPERMARKET ACQUIRER IF THE TRANSACTION IS SUBMITTED FOR
THE U.S. REGION SUPERMARKET INTERCHANGE PROGRAM.
1158 DE93 TRANSACTION DESTINATION INSTITUTION ID CODE IS GCMS
DESIGNATED AS AN ACQUIRER ONLY BY MASTERCARD.
1159 DE93 TRANSACTION DESTINATION INSTITUTION ID CODE IS GCMS
DESIGNATED AS AN ISSUER ONLY BY MASTERCARD.
1160 DE3S1 CARDHOLDER TRANSACTION TYPE MUST BE 01 IF THE GCMS
RECEIVER IS AN ATM ACQUIRER.
1162 DE93 TRANSACTION DESTINATION INSTITUTION ID CODE MUST BE A GCMS
WAREHOUSE ACQUIRER IF THE TRANSACTION IS SUBMITTED FOR
THE U.S. REGION WAREHOUSE INTERCHANGE PROGRAM.
1163 PDS 0174 DUN & BRADSTREET NUMBER MUST BE NUMERIC. Both
1164 PDS0574 ARRIVAL DATE, PDS0575 DEPARTURE DATE, PDS0576 FOLIO Both
NUMBER, AND EITHER PDS0577 PROPERTY PHONE NUMBER OR
PDS0552 CUSTOMER SERVICE TOLL-FREE NUMBER ARE REQUIRED FOR
LODGING TRANS. SUBMITTED FOR U.S.REGION WORLD MASTERCARD
T&E OR CORP. T&E RATE II INTERCHANGE PROGRAMS.
1174 TRANSACTION AMOUNT EXCEEDS RESTRICTED THRESHOLD GCMS
1175 DE94 TRANSACTION ORIGINATOR INSTITUTION ID CODE INVALID GCMS
FOR SENDING PROCESSOR ID IN PARAMETER MASTER.


1177 DE95 CARD ISSUER REFERENCE DATA MUST BE NUMERIC. Both
2007 ACCEPTANCE BRAND ID CODE SUBMITTED IS NOT VALID FOR THE Both
MEMBER PAIR.
2009 NO BUSINESS SERVICE ARRANGEMENT EXISTS FOR THE MEMBER Both
PAIR.
2010 BUSINESS SERVICE ID CODE SUBMITTED IS NOT VALID FOR THE Both
MEMBER PAIR.
2024 PDS0670 PAYER NAME OR USER ID MUST BE LEFT JUSTIFIED AND Both
2025 PDS0670 PAYER NAME OR USER ID LENGTH MUST BE 1–24. Both
2026 PDS0671 DATE OF FUNDS REQUESTED MUST BE A VALID DATE IN Both
THE FORMAT YYMMDD.
2027 PDS0671 DATE OF FUNDS REQUESTED MUST BE A FIXED LENGTH OF Both
006.
2028 PDS0672 RECIPIENT NAME (SELLER) MUST BE LEFT JUSTIFIED AND Both
2029 PDS0672 RECIPIENT NAME (SELLER) LENGTH MUST BE 1–24. Both
2030 PDS0673 DATE OF ANTICIPATED RECEIPT OF FUNDS MUST BE A Both
2031 PDS0673 DATE OF ANTICIPATED RECEIPT OF FUNDS MUST BE A Both
FIXED LENGTH OF 006.
2032 PDS0674 ADDITIONAL TRACE/REFERENCE NUMBER USED BY CARD Both
ACCEPTOR MUST BE LEFT JUSTIFIED AND CANNOT CONTAIN ALL
SPACES.
2033 PDS0674 ADDITIONAL TRACE/REFERENCE NUMBER USED BY CARD Both
ACCEPTOR LENGTH MUST BE 1–15.
2034 PDS0675 ADDITIONAL TRANSACTION DESCRIPTION DATA MUST BE Both
LEFT JUSTIFIED AND CANNOT CONTAIN ALL SPACES.
2035 PDS0676 CARD ACCEPTOR VAT NUMBER LENGTH MUST BE 1–20. Both
2036 PDS0676 CARD ACCEPTOR VAT NUMBER MUST BE LEFT JUSTIFIED Both
2037 PDS0677 CUSTOMER VAT NUMBER LENGTH MUST BE 1–20. Both
2038 PDS0677 CUSTOMER VAT NUMBER MUST BE LEFT JUSTIFIED AND Both
2039 PDS0678 UNIQUE INVOICE NUMBER LENGTH MUST BE 1–17. Both


2040 PDS0678 UNIQUE INVOICE NUMBER MUST BE LEFT JUSTIFIED AND Both
2041 PDS0679 COMMODITY CODE LENGTH MUST BE 1–15. Both
2042 PDS0679 COMMODITY CODE MUST BE LEFT JUSTIFIED AND CANNOT Both
CONTAIN ALL SPACES.
2043 PDS0680 AUTHORIZED CONTACT NAME LENGTH MUST BE 1–36. Both
2044 PDS0680 AUTHORIZED CONTACT NAME MUST BE LEFT JUSTIFIED Both
2045 PDS0681 AUTHORIZED CONTACT PHONE LENGTH MUST BE 1–17. Both
2046 PDS0681 AUTHORIZED CONTACT PHONE MUST BE LEFT JUSTIFIED Both
2048 PDS0682S1 DETAIL TAX AMOUNT INDICATOR 1 MUST BE Y, N, OR Both
SPACE.
2049 PDS0682S2 DETAIL TAX AMOUNT 1 INVALID. MUST BE NUMERIC. Both
2050 PDS0682S3 DETAIL TAX RATE 1 INVALID. MUST BE NUMERIC. Both
2051 PDS0682S4 DETAIL TAX RATE EXPONENT 1 MUST BE 0–5. Both
2052 PDS0682S6 DETAIL TAX TYPE IDENTIFIER 1 MUST BE 00, 01, 02, 03, 04, Both
05, 06, 10, 11, 12, 20, 21, 22, OR SPACE.
SPACE.
05, 06, 10, 11, 12, 20, 21, 22, OR SPACE.
SPACE.
05, 06, 10, 11, 12, 20, 21, 22, OR SPACE.
2065 PDS0685 TYPE OF SUPPLY MUST BE A FIXED LENGTH OF 002. Both
2066 PDS0685 TYPE OF SUPPLY MUST BE 00 OR 01. Both


2067 PDS0686 TAX EXEMPT INDICATOR MUST BE A FIXED LENGTH OF 001. Both
2068 PDS0686 TAX EXEMPT INDICATOR MUST BE 0 OR 1. Both
2069 PDS0687 UNIQUE VAT INVOICE REFERENCE NUMBER LENGTH MUST Both
BE 1–17.
2070 PDS0687 UNIQUE VAT INVOICE REFERENCE NUMBER MUST BE LEFT Both
2073 PDS0689 CORPORATE IDENTIFIER LENGTH MUST BE 1–12. Both
2074 PDS0690 NO SHOW INDICATOR MUST BE A FIXED LENGTH OF 001. Both
2075 PDS0690 NO SHOW INDICATOR MUST BE 0 OR 1. Both
2076 PDS0691 DAYS RENTED MUST BE A FIXED LENGTH OF 004. Both
2077 PDS0691 DAYS RENTED MUST BE NUMERIC. Both
2078 PDS0692 WEEKLY RENTAL AMOUNT MUST BE A FIXED LENGTH OF Both
012.
2079 PDS0692 WEEKLY RENTAL AMOUNT MUST BE NUMERIC. Both
2082 PDS0694 ONE WAY DROP OFF CHARGE MUST BE A FIXED LENGTH OF Both
012.
2083 PDS0694 ONE WAY DROP OFF CHARGE MUST BE NUMERIC. Both
2084 PDS0695 REGULAR MILEAGE CHARGE MUST BE A FIXED LENGTH OF Both
012.
2085 PDS0695 REGULAR MILEAGE CHARGE MUST BE NUMERIC. Both
2086 PDS0696 EXTRA MILEAGE CHARGE MUST BE A FIXED LENGTH OF 012. Both
2087 PDS0696 EXTRA MILEAGE CHARGE MUST BE NUMERIC. Both
2088 PDS0697 LATE CHARGE MUST BE A FIXED LENGTH OF 012. Both
2089 PDS0697 LATE CHARGE MUST BE NUMERIC. Both
2090 PDS0698 FUEL CHARGE MUST BE A FIXED LENGTH OF 012. Both
2091 PDS0698 FUEL CHARGE MUST BE NUMERIC. Both
2094 PDS0700 TOWING CHARGES MUST BE A FIXED LENGTH OF 012. Both
2095 PDS0700 TOWING CHARGES MUST BE NUMERIC. Both
2096 PDS0701 EXTRA CHARGES MUST BE A FIXED LENGTH OF 012. Both
2097 PDS0701 EXTRA CHARGES MUST BE NUMERIC. Both


2098 PDS0702 OTHER CHARGES MUST BE A FIXED LENGTH OF 012. Both
2099 PDS0702 OTHER CHARGES MUST BE NUMERIC. Both
2100 PDS0703 TOTAL ROOM NIGHTS MUST BE A FIXED LENGTH OF 004. Both
2101 PDS0703 TOTAL ROOM NIGHTS MUST BE NUMERIC. Both
2103 PDS0704 PREPAID EXPENSES MUST BE NUMERIC. Both
2116 PDS0711 FIRE SAFETY ACT INDICATOR MUST BE A FIXED LENGTH OF Both
001.
2117 PDS0711 FIRE SAFETY ACT INDICATOR MUST BE Y OR N. Both
2118 PDS0712 NET FUEL PRICE MUST BE A FIXED LENGTH OF 013. Both
2119 PDS0712S1 NET FUEL PRICE MUST BE NUMERIC. Both
2120 PDS0712S2 NET FUEL PRICE EXPONENT MUST BE 0–5. Both
2121 PDS0713 RESTRICTED TICKET INDICATOR MUST BE A FIXED LENGTH Both
OF 001.
2122 PDS0713 RESTRICTED TICKET INDICATOR MUST BE 0 OR 1. Both
2123 PDS0714 EXCHANGE TICKET AMOUNT MUST BE A FIXED LENGTH OF Both
012.
2124 PDS0714 EXCHANGE TICKET AMOUNT MUST BE NUMERIC. Both
2125 PDS0715 EXCHANGE FEE AMOUNT MUST BE A FIXED LENGTH OF 012. Both
2126 PDS0715 EXCHANGE FEE AMOUNT MUST BE NUMERIC. Both
2127 PDS0716 TRAVEL AUTHORIZATION CODE LENGTH MUST BE 1–64. Both
2128 PDS0716 TRAVEL AUTHORIZATION CODE MUST BE LEFT JUSTIFIED Both
2129 PDS0717 IATA CLIENT CODE LENGTH MUST BE 1–17. Both
2130 PDS0717 IATA CLIENT CODE MUST BE LEFT JUSTIFIED AND CANNOT Both
CONTAIN ALL SPACES.
2151 DE124 CANNOT BE ALL LOW-VALUES OR ALL HIGH-VALUES. Both
2152 DE124 ADDITIONAL DATA 4 LENGTH MUST BE 008–999. Both
DE124 OR BE MOVED TO DE125.
ADDITIONAL DATA, DE62 ADDITIONAL DATA 2, DE123 ADDITIONAL
DATA 3, AND DE124 ADDITIONAL DATA 4 ARE PRESENT.


2156 PDS 10XX MEMBER-TO-MEMBER PROPRIETARY DATA CANNOT BE ALL Both
2159 MEMBER-TO-MEMBER PROPRIETARY DATA CANNOT EXCEED 999 Both
BYTES.
2160 PDS0175 CARD ACCEPTOR URL MUST BE LEFT JUSTIFIED AND Both
2163 PDS0675 ADDITIONAL TRANSACTION DESCRIPTION DATA LENGTH Both
MUST BE 1–15.
2165 PDS0175 CARD ACCEPTOR URL LENGTH MUST BE 1–255. Both
2167 DE43S5 CARD ACCEPTOR STATE/PROVINCE/REGION CODE Both
REQUIRED.
2175 DE93 TRANSACTION DESTINATION INSTITUTION ID CODE MISSING. GCMS
MUST BE PRESENT IN FIRST AND SECOND PRESENTMENT.
This error message applies to ATM Cash Disbursement only.
DE93 TRANSACTION DESTINATION INSTITUTION ID CODE MISSING. Both

MUST BE PRESENT IN FIRST CHARGEBACK MESSAGES.
DE93 TRANSACTION DESTINATION INSTITUTION ID CODE MISSING. Both
MUST BE PRESENT IN ARBITRATION CHARGEBACK MESSAGES.
2176 DE4 AMOUNT, TRANSACTION MUST BE NUMERIC. Both
2177 DE95 CARD ISSUER REFERENCE DATA MUST BE A FIXED LENGTH OF Both
010.
2180 DE33 FORWARDING INSTITUTION ID CODE LENGTH MUST BE 006- Both
011.
DE72 DATA RECORD LENGTH MUST BE 001-100. Both
DE93 TRANSACTION DESTINATION INSTITUTION ID CODE LENGTH Both
MUST BE 006-011.
DE94 TRANSACTION ORIGINATOR INSTITUTION ID CODE LENGTH Both
MUST BE 006-011.
DE100 FORWARDING INSTITUTION ID CODE LENGTH MUST BE Both
006-011.
PDS0165 SETTLEMENT INDICATOR LENGTH MUST BE 001-030. Both
PDS0375 MEMBER RECONCILIATION INDICATOR 1 LENGTH MUST BE Both
001–050.
PDS0515 ADDITIONAL CARD ACCEPTOR INFORMATION LENGTH Both
MUST BE 001–040.
PDS0545 RENTER NAME LENGTH MUST BE 001-040. Both


2180 PDS0546 RENTAL RETURN CITY LENGTH MUST BE 001-025. Both
PDS0564 RENTAL LOCATION CITY LENGTH MUST BE 001-025. Both
PDS0567 FOLIO NUMBER LENGTH MUST BE 001-025. Both
PDS0571 GUEST NAME LENGTH MUST BE 001-040. Both
PDS0573 INVOICE NUMBER LENGTH MUST BE 001-025. Both
PDS0576 FOLIO NUMBER LENGTH MUST BE 001-025. Both
PDS0593 PARTY POSTAL INFORMATION LENGTH MUST BE 025-046. Both
PDS0599 CORPORATION VAT NUMBER LENGTH MUST BE 001–020. Both
PDS0615 MEDICAL SERVICES SHIP TO HEALTH INDUSTRY NUMBER Both
LENGTH MUST BE 001 TO 040.
PDS0616 CONTRACT NUMBER LENGTH MUST BE 001 TO 040. Both
PDS0619 USER NAME LENGTH MUST BE 001-040. Both
PDS0624 USER ACCOUNT NUMBER LENGTH MUST BE 001-040. Both
PDS0625 USER TELEPHONE NUMBER LENGTH MUST BE 001-025. Both
PDS0659 OTHER DESCRIPTION LENGTH MUST BE 001-060. Both
PDS0682 DETAIL TAX AMOUNT 1 LENGTH MUST BE 001-046. Both
PDS0718 EMPLOYEE TEMP NAME/ID LENGTH MUST BE 001–040. Both
PDS0719 EMPLOYEE SOCIAL SECURITY NUMBER OR ID LENGTH MUST Both
BE 001–030.
PDS0720 JOB DESCRIPTION LENGTH MUST BE 001–040. Both
PDS0721 JOB CODE LENGTH MUST BE 001–020. Both
PDS0729 REQUESTOR NAME OR ID LENGTH MUST BE 001–040. Both
PDS0730 SUPERVISOR/REPORTS TO LENGTH MUST BE 001–040. Both
PDS0731 TIME SHEET NUMBER LENGTH MUST BE 001–020. Both
PDS0735 SERVICE DESCRIPTOR CODE LENGTH MUST BE 001–040. Both
PDS0736 TRACKING NUMBER LENGTH MUST BE 001–040. Both
PDS0743 UNIT OF MEASURE LENGTH MUST BE 001–003. Both
PDS0746 SHIPPING PARTY POSTAL INFORMATION LENGTH MUST BE Both
025–041.


2180 PDS0750 DELIVERY PARTY POSTAL INFORMATION LENGTH MUST BE Both
025–041.
PDS0751 DETAIL TAX AMOUNT 4 LENGTH MUST BE 001–046. Both
2181 PDS0261 RISK MANAGEMENT APPROVAL CODE MUST BE A FIXED Both
LENGTH OF 011.
PDS0516 AUSTIN-TETRA NUMBER MUST BE A FIXED LENGTH OF 15. Both
PDS0517 NAICS CODE MUST BE A FIXED LENGTH OF 15. Both
PDS0518 LINE ITEM DATE MUST BE A FIXED LENGTH OF 006. Both
PDS0519 ADDITIONAL FUEL LOCATION INFORMATION MUST BE A Both
PDS0532 TOTAL CHARGES MUST BE A FIXED LENGTH OF 014. Both
PDS0534 TOTAL NON-ROOM CHARGES MUST BE A FIXED LENGTH OF Both
014.
PDS0539 TOTAL AMOUNT CHARGED ON CREDIT CARD MUST BE A Both
PDS0540 ROOM SERVICE CHARGES MUST BE A FIXED LENGTH OF 014. Both
PDS0541 LOUNGE/BAR CHARGES MUST BE A FIXED LENGTH OF 014. Both
PDS0542 TRANSPORTATION CHARGES MUST BE A FIXED LENGTH OF Both
014.
PDS0543 GRATUITY CHARGES MUST BE A FIXED LENGTH OF 014. Both
PDS0552 CUSTOMER SERVICE TOLL-FREE (800) NUMBER MUST BE A Both
PDS0554 CONFERENCE ROOM CHARGES MUST BE A FIXED LENGTH Both
OF 014.
PDS0560 AUDIO VISUAL CHARGES MUST BE A FIXED LENGTH OF 014. Both
PDS0562 BANQUET CHARGES MUST BE A FIXED LENGTH OF 014. Both
PDS0569 INTERNET ACCESS MUST BE A FIXED LENGTH OF 014. Both
PDS0570 EARLY DEPARTURE CHARGES MUST BE A FIXED LENGTH OF Both
014.
PDS0572 GUEST NUMBER MUST BE A FIXED LENGTH OF 025. Both
PDS0577 PROPERTY NUMER MUST BE A FIXED LENGTH OF 017. Both


2181 PDS0578 BILLING ADJUSTMENT LENGTH MUST BE A FIXED LENGTH Both
OF 015.
PDS0579 INVOICE DATE MUST BE A FIXED LENGTH OF 006. Both
PDS0580 ROOM RATE MUST BE A FIXED LENGTH OF 013. Both
PDS0581 TOTAL ROOM TAX AMOUNT MUST BE A FIXED LENGTH OF Both
014.
PDS0583 PHONE CHARGES AMOUNT MUST BE FIXED LENGTH OF 014. Both
PDS0584 RESTAURANT CHARGES AMOUNT MUST BE A FIXED LENGTH Both
OF 014.
PDS0585 MINI-BAR CHARGES AMOUNT MUST BE A FIXED LENGTH OF Both
014.
PDS0586 GIFT SHOP CHARGES AMOUNT MUST BE A FIXED LENGTH Both
OF 014.
PDS0587 LAUNDRY & DRY CLEANING CHARGES MUST BE FIXED Both
LENGTH OF 014.
PDS0589 INVOICE CREATION DATE/TIME MUST BE A FIXED LENGTH Both
OF 012.
PDS0590 PARTY IDENTIFICATION MUST BE A FIXED LENGTH OF 002. Both
PDS0593S1 CITY MUST BE A FIXED LENGTH OF 025. Both
PDS0593S2 STATE/PROVINCE CODE MUST BE FIXED LENGTH OF 003. Both
PDS0593S3 COUNTRY CODE MUST BE FIXED LENGTH OF 003. Both
PDS0593S4 POSTAL CODE MUST BE FIXED LENGTH OF 015. Both
PDS0595 CARD ACCEPTOR TYPE MUST BE A FIXED LENGTH OF 008. Both
PDS0596 CARD ACCEPTOR TAX ID MUST BE A FIXED LENGTH OF 021. Both
PDS0597 TOTAL TAX AMOUNT MUST BE A FIXED LENGTH OF 014. Both
PDS0601 PARTY NATURE OF FILING MUST BE A FIXED LENGTH 001. Both
PDS0606 FREIGHT AMOUNT MUST BE A FIXED LENGTH OF 014. Both
PDS0607 DUTY AMOUNT MUST BE A FIXED LENGTH OF 014. Both
PDS0612 SHIP DATE MUST BE A FIXED LENGTH OF 006. Both
PDS0617 MEDICAL SERVICES PRICE ADJUSTMENT MUST BE A FIXED Both
LENGTH OF 001.
PDS0618 MEDICAL SERVICES PRODUCT NUMBER QUALIFIER MUST BE Both
A FIXED LENGTH OF 002.


2181 PDS0623 MOTOR FUEL INFORMATION MUST BE A FIXED LENGTH OF Both
035.
PDS0626 BILLING STATEMENT PERIOD MUST BE A FIXED LENGTH OF Both
012.
PDS0636 CALL DATE MUST BE A FIXED LENGTH OF 006. Both
PDS0637 CALL TIME MUST BE A FIXED LENGTH OF 006. Both
PDS0638 CALL TO INFORMATION MUST BE A FIXED LENGTH OF 146. Both
PDS0639 CALL DURATION MUST BE A FIXED LENGTH OF 006. Both
PDS0640 CALL TIME PERIOD MUST BE A FIXED LENGTH OF 002. Both
PDS0644 CALL FROM INFORMATION MUST BE A FIXED LENGTH OF Both
146.
PDS0647 EXTENDED ITEM AMOUNT MUST BE A FIXED LENGTH OF Both
014.
PDS0648 ITEM DISCOUNT MUST BE A FIXED LENGTH OF 020. Both
PDS0649 CALL USAGE AMOUNT MUST BE A FIXED LENGTH OF 014. Both
PDS0655 CALL LONG DISTANCE AMOUNT MUST BE A FIXED LENGTH Both
OF 014.
PDS0658 CALL CONNECT AMOUNT MUST BE A FIXED LENGTH OF 014. Both
PDS0682S7 CARD ACCEPTOR TAX ID 1 MUST BE A FIXED LENGTH OF Both
020.
020.
020.
PDS0693 TOTAL AUTHORIZED AMOUNT MUST BE A FIXED LENGTH Both
OF 014.
PDS0699 LODGING TOTAL TAX AMOUNT MUST BE A FIXED LENGTH Both
OF 014.
PDS0704 PREPAID EXPENSES MUST BE A FIXED LENGTH OF 014. Both
PDS0705 TOTAL NON-ROOM TAX AMOUNT MUST BE A FIXED LENGTH Both
OF 014.
PDS0706 CASH ADVANCES MUST BE A FIXED LENGTH OF 014. Both
PDS0707 VALET CHARGES MUST BE A FIXED LENGTH OF 014. Both
PDS0708 MOVIE CHARGES MUST BE A FIXED LENGTH OF 014. Both


2181 PDS0709 BUSINESS CENTER CHARGES MUST BE A FIXED LENGTH OF Both
014.
PDS0710 HEALTH CLUB CHARGES MUST BE A FIXED LENGTH OF 014. Both
PDS0722 FLAT RATE INDICATOR MUST BE A FIXED LENGTH OF 001. Both
PDS0723 REGULAR HOURS WORKED MUST BE A FIXED LENGTH OF Both
007.
PDS0724 REGULAR HOURS RATE MUST BE A FIXED LENGTH OF 007. Both
PDS0725 OVERTIME HOURS WORKED MUST BE A FIXED LENGTH OF Both
007.
PDS0726 OVERTIME HOURS RATE MUST BE A FIXED LENGTH OF 007. Both
PDS0727 TEMP START DATE MUST BE A FIXED LENGTH OF 006. Both
PDS0728 TEMP WEEK ENDING MUST BE A FIXED LENGTH OF 006. Both
PDS0732 DISCOUNT AMOUNT MUST BE A FIXED LENGTH OF 018. Both
PDS0733 SUBTOTAL AMOUNT MUST BE A FIXED LENGTH OF 014. Both
PDS0737 SHIPPING NET AMOUNT MUST BE A FIXED LENGTH OF 014. Both
PDS0738 INCENTIVE AMOUNT MUST BE A FIXED LENGTH OF 014. Both
PDS0739 PICKUP DATE MUST BE A FIXED LENGTH OF 006. Both
PDS0740 DELIVERY DATE MUST BE A FIXED LENGTH OF 006. Both
PDS0741 NUMBER OF PACKAGES MUST BE A FIXED LENGTH OF 006. Both
PDS0742 PACKAGE WEIGHT MUST BE A FIXED LENGTH OF 012. Both
020.
020.
020.
PDS0755 LINE ITEM TOTAL AMOUNT MUST BE A FIXED LENGTH OF Both
014.


2182 DE41 CARD ACCEPTOR TERMINAL ID MUST BE LEFT JUSTIFIED AND Both
CANNOT CONTAIN ALL SPACES OR ALL ZEROS.
DE42 CARD ACCEPTOR ID CODE MUST BE LEFT JUSTIFIED AND Both
DE 43S2 CARD ACCEPTOR STREET ADDRESS MUST BE LEFT JUSTIFIED Both
AND CANNOT CONTAIN ALL SPACES OR ALL ZEROS.
DE43S3 CARD ACCEPTOR CITY MUST BE LEFT JUSTIFIED AND Both
PDS0175 CARD ACCEPTOR URL MUST BE LEFT JUSTIFIED AND Both
PDS0505 PASSENGER NAME MUST BE LEFT JUSTIFIED AND CANNOT Both
CONTAIN ALL SPACES OR ALL ZEROS.
PDS0506 TICKET NUMBER MUST BE LEFT JUSTIFIED AND CANNOT Both
PDS0507 ISSUING CARRIER MUST BE LEFT JUSTIFIED AND CANNOT Both
PDS0510 TRAVEL AGENCY CODE MUST BE LEFT JUSTIFIED AND Both
PDS0511 TRAVEL AGENCY NAME MUST BE LEFT JUSTIFIED AND Both
PDS0515 ADDITIONAL CARD ACCEPTOR INFORMATION MUST BE LEFT Both
JUSTIFIED AND CANNOT CONTAIN ALL SPACES OR ALL ZEROS.
PDS0516 AUSTIN-TETRA NUMBER MUST BE LEFT JUSTIFIED AND Both
PDS0517 NAICS CODE MUST BE LEFT JUSTIFIED AND CANNOT Both
PDS0521 CARRIER CODE MUST BE LEFT JUSTIFIED AND CANNOT Both
PDS0522 SERVICE CLASS CODE MUST BE LEFT JUSTIFIED AND Both
PDS0523 CITY OF ORIGIN/AIRPORT CODE MUST BE LEFT JUSTIFIED Both
PDS0524 CITY OF DESTINATION/AIRPORT CODE MUST BE LEFT Both
PDS0526 CONJUNCTION TICKET MUST BE LEFT JUSTIFIED AND Both


2182 PDS0527 EXCHANGE TICKET MUST BE LEFT JUSTIFIED AND CANNOT Both
PDS0530 FLIGHT NUMBER MUST BE LEFT JUSTIFIED AND CANNOT Both
PDS0538 ENDORSEMENT/RESTRICTIONS MUST BE LEFT JUSTIFIED Both
PDS0544 RENTAL AGREEMENT NUMBER MUST BE LEFT JUSTIFIED AND Both
PDS0545 RENTER NAME MUST BE LEFT JUSTIFIED AND CANNOT Both
PDS0546 RENTAL RETURN CITY MUST BE LEFT JUSTIFIED AND Both
PDS0547 RENTAL RETURN STATE/PROVINCE MUST BE LEFT JUSTIFIED Both
PDS0563 PROGRAM CODE MUST BE LEFT JUSTIFIED AND CANNOT Both
PDS0564 RENTAL LOCATION CITY MUST BE LEFT JUSTIFIED AND Both
PDS0565 RENTAL LOCATION STATE/PROVINCE MUST BE LEFT Both
PDS0567 RENTAL LOCATION ID MUST BE LEFT JUSTIFIED AND Both
CANNOT CONTAIN ALL SPACES OR ALL ZEROS
PDS0568 RENTAL CLASS ID MUST BE LEFT JUSTIFIED AND CANNOT Both
PDS0571 GUEST NAME MUST BE LEFT JUSTIFIED AND CANNOT Both
PDS0572 GUEST NUMBER MUST BE LEFT JUSTIFIED AND CANNOT Both
PDS0573 INVOICE NUMBER MUST BE LEFT JUSTIFIED AND CANNOT Both
PDS0576 FOLIO NUMBER MUST BE LEFT JUSTIFIED AND CANNOT Both
PDS0577 PROPERTY PHONE NUMBER MUST BE LEFT JUSTIFIED AND Both
PDS0582 PROGRAM CODE MUST BE LEFT JUSTIFIED AND CANNOT Both


2182 PDS0588S1 OTHER SERVICES CODE MUST BE LEFT JUSTIFIED AND Both
PDS0591 PARTY NAME MUST BE LEFT JUSTIFIED AND CANNOT Both
PDS0592S1 PARTY ADDRESS MUST BE LEFT JUSTIFIED AND CANNOT Both
PDS0593S1 CITY MUST BE LEFT JUSTIFIED AND CANNOT CONTAIN Both
ALL SPACES OR ALL ZEROS.
PDS0593S2 STATE/PROVINCE CODE MUST BE LEFT JUSTIFIED AND Both
PDS0593S3 COUNTRY CODE MUST BE LEFT JUSTIFIED AND CANNOT Both
PDS0593S4 POSTAL CODE MUST BE LEFT JUSTIFIED AND CANNOT Both
PDS0594S2 PARTY CONTACT INFORMATION MUST BE LEFT JUSTIFIED Both
PDS0599 CORPORATION VAT NUMER MUST BE LEFT JUSTIFIED AND Both
PDS0600 CARD ACCEPTOR REFERENCE NUMBER MUST BE LEFT Both
PDS0602S1 PARTY SUPPLEMENTAL DATA DESCRIPTION 1 MUST BE Both
LEFT JUSTIFIED AND CANNOT CONTAIN ALL SPACES OR ALL ZEROS.
PDS0602S2 PARTY SUPPLEMENTAL DATA 1 MUST BE LEFT JUSTIFIED Both
PDS0602S3 PARTY SUPPLEMENTAL DATA CODE 1 MUST BE LEFT Both
PDS0603S1 PARTY SUPPLEMENTAL DATA DESCRIPTION 2 MUST BE Both
PDS0603S2 PARTY SUPPLEMENTAL DATA 2 MUST BE LEFT JUSTIFIED Both
PDS0603S3 PARTY SUPPLEMENTAL DATA CODE 2 MUST BE LEFT Both
PDS0604S1 TRANSACTION SUPPLEMENTAL DATA DESCRIPTION 1 Both
MUST BE LEFT JUSTIFIED AND CANNOT CONTAIN ALL SPACES OR ALL
ZEROS.


2182 PDS0604S2 TRANSACTION SUPPLEMENTAL DATA 1 MUST BE LEFT Both
PDS0604S3 TRANSACTION SUPPLEMENTAL DATA CODE 1 MUST BE Both
ZEROS.
PDS0605S2 TRANSACTION SUPPLEMENTAL DATA 2 MUST BE LEFT Both
PDS0605S3 TRANSACTION SUPPLEMENTAL DATA CODE 2 MUST BE Both
PDS0608 DESTINATION POSTAL CODE MUST BE LEFT JUSTIFIED AND Both
PDS0609 DESTINATION STATE/PROVINCE MUST BE LEFT JUSTIFIED Both
PDS0613 SHIP-FROM POSTAL CODE MUST BE LEFT JUSTIFIED AND Both
ZEROS.
PDS0616 CONTRACT NUMBER MUST BE LEFT JUSTIFIED AND CANNOT Both
PDS0619 USER NAME MUST BE LEFT JUSTIFIED AND CANNOT Both
PDS0624 USER ACCOUNT NUMBER MUST BE LEFT JUSTIFIED AND Both
PDS0625 USER TELEPHONE NUMBER MUST BE LEFT JUSTIFIED AND Both
PDS0627S4 BILLING EVENT DESCRIPTION 1 MUST BE LEFT JUSTIFIED Both
PDS0628S4 BILLING EVENT DESCRIPTION 2 MUST BE LEFT JUSTIFIED Both
PDS0629 ODOMETER READING MUST BE LEFT JUSTIFIED AND Both
PDS0630 VEHICLE NUMBER MUST BE LEFT JUSTIFIED AND CANNOT Both


2182 PDS0631 DRIVER NUMBER/ID NUMBER MUST BE LEFT JUSTIFIED AND Both
PDS0638S1CALL TO CITY MUST BE LEFT JUSTIFIED AND CANNOT Both
PDS0638S2 CALL TO STATE/PROVINCE MUST BE LEFT JUSTIFIED AND Both
PDS0638S3 CALL TO COUNTRY MUST BE LEFT JUSTIFIED AND Both
PDS0638S4 CALL TO NUMBER MUST BE LEFT JUSTIFIED AND CANNOT Both
PDS0644S1 CALL FROM CITY MUST BE LEFT JUSTIFIED AND CANNOT Both
PDS0644S2 CALL FROM STATE/PROVINCE MUST BE LEFT JUSTIFIED Both
PDS0644S3 CALL FROM COUNTRY MUST BE LEFT JUSTIFIED AND Both
PDS0644S4 CALL FROM NUMBER MUST BE LEFT JUSTIFIED AND Both
PDS0659 OTHER DESCRIPTION MUST BE LEFT JUSTIFIED AND Both
PDS0663 FREE-FORM DESCRIPTION MUST BE LEFT JUSTIFIED AND Both
PDS0718 EMPLOYEE TEMP NAME/ID MUST BE LEFT JUSTIFIED AND Both
PDS0719 EMPLOYEE SOCIAL SECURITY NUMBER OR ID MUST BE LEFT Both
PDS0720 JOB DESCRIPTION MUST BE LEFT JUSTIFIED AND CANNOT Both
PDS0721 JOB CODE MUST BE LEFT JUSTIFIED AND CANNOT CONTAIN Both
PDS0729 REQUESTOR NAME OR ID MUST BE LEFT JUSTIFIED AND Both
CANNOT CONTAIN SPACES OR ALL ZEROS.
PDS0730 SUPERVISOR/REPORTS TO MUST BE LEFT JUSTIFIED AND Both
PDS0731 TIME SHEET NUMBER MUST BE LEFT JUSTIFIED AND Both


2182 PDS0732S4 DISCOUNT TYPE MUST BE LEFT JUSTIFIED AND CANNOT Both
PDS0734S1 MISCELLANEOUS EXPENSES DESCRIPTION MUST BE LEFT Both
PDS0735 SERVICE DESCRIPTOR CODE MUST BE LEFT JUSTIFIED AND Both
PDS0736 TRACKING NUMBER OR PICKUP NUMBER MUST BE LEFT Both
PDS0743 UNIT OF MEASURE MUST BE LEFT JUSTIFIED AND CANNOT Both
PDS0744S1 SHIPPING PARTY NAME MUST BE LEFT JUSTIFIED AND Both
PDS0745S1 SHIPPING PARTY ADDRESS MUST BE LEFT JUSTIFIED AND Both
PDS0746 SHIPPING PARTY POSTAL INFORMATION MUST BE LEFT Both
PDS0746S1 SHIPPING PARTY CITY MUST BE LEFT JUSTIFIED AND Both
PDS0746S2 SHIPPING PARTY STATE/PROVINCE MUST BE LEFT Both
PDS0746S3 SHIPPING PARTY COUNTRY CODE MUST BE LEFT Both
PDS0746S4 SHIPPING PARTY POSTAL CODE MUST BE LEFT JUSTIFIED Both
PDS0747S2 SHIPPING PARTY CONTACT INFORMATION MUST BE LEFT Both
PDS0748S1 DELIVERY PARTY NAME MUST BE LEFT JUSTIFIED AND Both
PDS0749S1 DELIVERY PARTY ADDRESS MUST BE LEFT JUSTIFIED AND Both
PDS0750 DELIVERY PARTY POSTAL INFORMATION MUST BE LEFT Both
PDS0750S1 DELIVERY PARTY CITY MUST BE LEFT JUSTIFIED AND Both
PDS0750S2 DELIVERY PARTY STATE/PROVINCE MUST BE LEFT Both


2182 PDS0750S3 DELIVERY PARTY COUNTRY CODE MUST BE LEFT Both
PDS0750S4 DELIVERY PARTY POSTAL CODE MUST BE LEFT JUSTIFIED Both
PDS0754S2 DELIVERY PARTY CONTACT INFORMATION MUST BE LEFT Both
PDS0799 TEST CASE TRACABILITY 1 MUST BE LEFT JUSTIFIED AND Both
2183 DE40 EXTENDED SERVICE CODE MUST BE NUMERIC. Both
PDS0518 LINE ITEM DATE MUST BE NUMERIC. Both
PDS0532S1 TOTAL CHARGES AMOUNT MUST BE NUMERIC. Both
PDS0532S2 TOTAL CHARGES EXPONENT MUST BE NUMERIC. Both
PDS0534S1 TOTAL NON-ROOM CHARGES AMOUNT MUST BE Both
NUMERIC.
PDS0534S2 TOTAL NON-ROOM CHARGES EXPONENT MUST BE Both
NUMERIC.
PDS0539S1 TOTAL AMOUNT CHARGED ON CREDIT CARD AMOUNT Both
MUST BE NUMERIC.
PDS0539S2 TOTAL AMOUNT CHARGED ON CREDIT CARD EXPONENT Both
MUST BE NUMERIC.
PDS0540S1 ROOM SERVICE CHARGES AMOUNT MUST BE NUMERIC. Both
PDS0540S2 ROOM SERVICE CHARGES EXPONENT MUST BE NUMERIC. Both
PDS0541S1 LOUNGE/BAR CHARGES AMOUNT MUST BE NUMERIC. Both
PDS 541S2 LOUNGE/BAR CHARGES EXPONENT MUST BE NUMERIC. Both
PDS 542S1 TRANSPORTATION CHARGES AMOUNT MUST BE NUMERIC. Both
PDS0542S2 TRANSPORTATION CHARGES EXPONENT MUST BE Both
NUMERIC.
PDS0543S1 GRATUITY CHARGES AMOUNT MUST BE NUMERIC. Both
PDS 543S2 GRATUITY CHARGES EXPONENT MUST BE NUMERIC. Both
PDS0553S2 RENTAL RATE MUST BE NUMERIC. Both
PDS0554S1 CONFERENCE ROOM CHARGES AMOUNT MUST BE Both
NUMERIC.


2183 PDS0554S2 CONFERENCE ROOM CHARGES EXPONENT MUST BE Both
NUMERIC.
PDS0560S1 AUDIO VISUAL CHARGES AMOUNT MUST BE NUMERIC. Both
PDS0560S2 AUDIO VISUAL CHARGES EXPONENT MUST BE NUMERIC. Both
PDS0562S1 BANQUET CHARGES AMOUNT MUST BE NUMERIC. Both
PDS0562S2 BANQUET CHARGES EXPONENT MUST BE NUMERIC. Both
PDS 569S1 INTERNET ACCESS AMOUNT MUST BE NUMERIC. Both
PDS 569S2 INTERNET ACCESS EXPONENT MUST BE NUMERIC. Both
PDS0570S1 EARLY DEPARTURE CHARGES AMOUNT MUST BE Both
NUMERIC.
PDS0570S2 EARLY DEPARTURE CHARGES EXPONENT MUST BE Both
NUMERIC.
PDS0578S3 BILLING ADJUSTMENT EXPONENT MUST BE NUMERIC. Both
PDS0579 INVOICE DATE MUST BE NUMERIC. Both
PDS0580S1 ROOM RATE AMOUNT MUST BE NUMERIC. Both
PDS0580S2 ROOM RATE EXPONENT MUST BE NUMERIC. Both
PDS0581S1 TOTAL ROOM TAX AMOUNT MUST BE NUMERIC. Both
PDS0581S2 TOTAL ROOM TAX EXPONENT MUST BE NUMERIC. Both
PDS0583S1 PHONE CHARGES AMOUNT MUST BE NUMERIC. Both
PDS0583S2 PHONE CHARGES EXPONENT MUST BE NUMERIC. Both
PDS0584S1 RESTAURANT CHARGES AMOUNT MUST BE NUMERIC. Both
PDS0584S2 RESTAURANT CHARGES EXPONENT MUST BE NUMERIC. Both
PDS0585S1 MINI-BAR CHARGES AMOUNT MUST BE NUMERIC. Both
PDS0585S2 MINI-BAR CHARGES EXPONENT MUST BE NUMERIC. Both
PDS0586S1 GIFT SHOP CHARGES AMOUNT MUST BE NUMERIC. Both
PDS0586S2 GIFT SHOP CHARGES EXPONENT MUST BE NUMERIC. Both
PDS0587S1 LAUNDRY AND DRY CLEANING CHARGES AMOUNT MUST Both
BE NUMERIC.
PDS0587S2 LAUNDRY AND DRY CLEANING CHARGES EXPONENT Both
MUST BE NUMERIC.
PDS0588S2 OTHER SERVICE AMOUNT MUST BE NUMERIC. Both


2183 PDS0588S3 OTHER SERVICES EXPONENT MUST BE NUMERIC. Both
PDS0589S1 INVOICE CREATION DATE MUST BE NUMERIC. Both
PDS0589S2 INVOICE CREATION TIME MUST BE NUMERIC. Both
PDS0594S1 PARTY CONTACT DESCRIPTOR MUST BE NUMERIC. Both
PDS0597S1 TOTAL TAX AMOUNT MUST BE NUMERIC. Both
PDS0597S2 TOTAL TAX AMOUNT EXPONENT MUST BE NUMERIC. Both
PDS0606S1 FREIGHT AMOUNT MUST BE NUMERIC. Both
PDS0606S2 FREIGHT AMOUNT EXPONENT MUST BE NUMERIC. Both
PDS0607S1 DUTY AMOUNT MUST NUMERIC. Both
PDS0607S2 DUTY AMOUNT EXPONENT MUST BE NUMERIC. Both
PDS0612 SHIP DATE MUST BE NUMERIC. Both
PDS0626S1 STATEMENT START DATE MUST BE NUMERIC. Both
PDS0626S2 STATEMENT END DATE MUST BE NUMERIC. Both
PDS0627S1 BILLING EVENT 1 AMOUNT MUST BE NUMERIC. Both
PDS0627S2 BILLING EVENT EXPONENT 1 MUST BE NUMERIC. Both
PDS0628S1 BILLING EVENT AMOUNT 2 MUST BE NUMERIC. Both
PDS0628S2 BILLING EVENT EXPONENT 2 MUST BE NUMERIC. Both
PDS0634 TAX AMOUNT 1 MUST BE NUMERIC Both
PDS0635 TAX AMOUNT 2 MUST BE NUMERIC. Both
PDS0636 CALL DATE MUST BE NUMERIC Both
PDS0637 CALL TIME MUST BE NUMERIC Both
PDS0639 CALL DURATION MUST BE NUMERIC Both
PDS0646S1 UNIT PRICE MUST BE NUMERIC. Both
PDS0647S1 EXTENDED ITEM AMOUNT EXPONENT MUST BE NUMERIC. Both
PDS0648S3 ITEM DISCOUNT RATE MUST BE NUMERIC. Both
PDS0648S4 ITEM DISCOUNT RATE EXPONENT MUST BE NUMERIC. Both
PDS0649S1 CALL USAGE AMOUNT MUST BE NUMERIC. Both
PDS0649S2 CALL USAGE AMOUNT EXPONENT MUST BE NUMERIC. Both
PDS0655S1 CALL LONG DISTANCE AMOUNT MUST BE NUMERIC. Both


2183 PDS0655S2 CALL LONG DISTANCE AMOUNT EXPONENT MUST BE Both
NUMERIC.
PDS0658S1CALL CONNECT AMOUNT MUST BE NUMERIC. Both
PDS0658S2 CALL CONNECT AMOUNT EXPONENT MUST BE NUMERIC. Both
PDS0693S1 TOTAL AUTHORIZED AMOUNT MUST BE NUMERIC. Both
PDS0693S2 TOTAL AUTHORIZED AMOUNT EXPONENT MUST BE Both
NUMERIC.
PDS0699S1 LODGING TOTAL TAX AMOUNT MUST BE NUMERIC. Both
PDS0699S2 LODGING TOTAL TAX AMOUNT EXPONENT MUST BE Both
NUMERIC.
PDS0704S1 PREPAID EXPENSES AMOUNT MUST BE NUMERIC. Both
PDS0704S2 PREPAID EXPENSES AMOUNT EXPONENT MUST BE Both
NUMERIC.
PDS0705S1 TOTAL NON-ROOM TAX AMOUNT MUST BE NUMERIC. Both
PDS0705S2 TOTAL NON-ROOM TAX AMOUNT EXPONENT MUST BE Both
NUMERIC.
PDS0706S1 CASH ADVANCE AMOUNT MUST BE NUMERIC. Both
PDS0706S2 CASH ADVANCE EXPONENT MUST BE NUMERIC. Both
PDS0707S1 VALET CHARGES AMOUNT MUST BE NUMERIC. Both
PDS0707S2 VALET CHARGES EXPONENT MUST BE NUMERIC. Both
PDS0708S1 MOVIE CHARGES AMOUNT MUST BE NUMERIC. Both
PDS0708S2 MOVIE CHARGES EXPONENT MUST BE NUMERIC. Both
PDS0709S1 BUSINESS CENTER CHARGES AMOUNT MUST BE NUMERIC. Both
PDS0709S2 BUSINESS CENTER CHARGES EXPONENT MUST BE Both
NUMERIC.
PDS0710S1 HEALTH CLUB CHARGES AMOUNT MUST BE NUMERIC. Both
PDS0710S2 HEALTH CLUB CHARGES EXPONENT MUST BE NUMERIC. Both
PDS0723 REGULAR HOURS WORKED MUST BE NUMERIC. Both
PDS0724 REGULAR HOURS RATE MUST BE NUMERIC. Both
PDS0725 OVERTIME HOURS WORKED MUST BE NUMERIC. Both
PDS0726 OVERTIME HOURS RATE MUST BE NUMERIC. Both
PDS0732 DISCOUNT AMOUNT MUST BE NUMERIC. Both


2183 PDS0732S1 DISCOUNT AMOUNT MUST BE NUMERIC. Both
PDS0732S2 DISCOUNT AMOUNT EXPONENT MUST BE NUMERIC. Both
PDS0733 SUBTOTAL AMOUNT MUST BE NUMERIC. Both
PDS0733S1 SUBTOTAL AMOUNT MUST BE NUMERIC. Both
PDS0733S2 SUBTOTAL AMOUNT EXPONENT MUST BE NUMERIC. Both
PDS0734S2 MISCELLANEOUS EXPENSE AMOUNT MUST BE NUMERIC. Both
PDS0734S3 MISCELLANEOUS EXPENSES EXPONENT MUST BE NUMERIC. Both
PDS0737 SHIPPING NET AMOUNT MUST BE NUMERIC. Both
PDS0737S1 SHIPPING NET AMOUNT MUST BE NUMERIC. Both
PDS0737S2 SHIPPING NET AMOUNT EXPONENT MUST BE NUMERIC. Both
PDS0738 INCENTIVE AMOUNT MUST BE NUMERIC. Both
PDS0738S1 INCENTIVE AMOUNT MUST BE NUMERIC. Both
PDS0738S2 INCENTIVE AMOUNT EXPONENT MUST BE NUMERIC. Both
PDS0741 NUMBER OF PACKAGES MUST BE NUMERIC. Both
PDS0742 PACKAGE WEIGHT MUST BE NUMERIC. Both
PDS0751S2 DETAIL TAX AMOUNT 4 MUST BE NUMERIC. Both
PDS0751S3 TAX RATE 4 MUST BE NUMERIC. Both
PDS0752S3 DETAIL TAX RATE 5 MUST BE NUMERIC. Both
PDS0753S3 DETAIL TAX RATE 6 MUST BE NUMERIC. Both
PDS0755S2 LINE ITEM TOTAL AMOUNT EXPONENT MUST BE Both
NUMERIC.
2184 DE43S2 CARD ACCEPTOR STREET ADDRESS CANNOT BE ALL LOW- Both
DE43S4 CARD ACCEPTOR POSTAL (ZIP) CODE CANNOT CONTAIN ALL Both
DE43S5 CARD ACCEPTOR STATE, PROVINCE, OR REGION CODE Both
DE55 INTEGRATED CIRCUIT CARD (ICC) SYSTEM RELATED DATA Both
CANNOT BE ALL LOW-VALUES, ALL HIGH-VALUES.


2184 PDS0375 MEMBER RECONCILIATION INDICATOR 1 CANNOT BE ALL Both
PDS0505 PASSENGER NAME CANNOT BE ALL LOW-VALUES OR HIGH- Both
VALUES.
PDS0515 ADDITIONAL CARD ACCEPTOR INFORMATION CANNOT BE Both
PDS0516 AUSTIN-TETRA NUMBER CANNOT BE ALL LOW-VALUES OR Both
ALL HIGH-VALUES.
PDS0517 NAICS CODE CANNOT BE ALL LOW-VALUES OR ALL HIGH- Both
VALUES.
PDS0526 CONJUNCTION TICKET CANNOT BE ALL LOW-VALUES OR Both
ALL HIGH-VALUES.
PDS0527 EXCHANGE TICKET CANNOT BE ALL LOW-VALUES OR ALL Both
HIGH-VALUES.
PDS0544 RENTAL AGREEMENT NUMBER CANNOT BE ALL LOW-VALUES Both
OR ALL HIGH-VALUES.
PDS0545 RENTER NAME CANNOT BE ALL LOW-VALUES OR ALL HIGH- Both
VALUES.
PDS0546 RENTAL RETURN CITY CANNOT BE ALL LOW-VALUES OR ALL Both
HIGH-VALUES.
PDS0547 RENTAL RETURN STATE/PROVINCE CANNOT BE ALL LOW- Both
PDS0552 CUSTOMER SERVICE TOLL-FREE (800) NUMBER CANNOT BE Both
PDS0563 PROGRAM CODE CANNOT BE ALL LOW-VALUES OR ALL Both
HIGH-VALUES.
PDS0564 RENTAL LOCATION CITY CANNOT BE ALL LOW-VALUES OR Both
ALL HIGH-VALUES.
PDS0565 RENTAL LOCATION STATE/PROVINCE CANNOT BE ALL LOW- Both
PDS0567 RENTAL LOCATION ID CANNOT BE ALL LOW-VALUES OR ALL Both
HIGH-VALUES.
PDS0568 RENTAL CLASS ID CANNOT BE ALL LOW-VALUES OR ALL Both
HIGH-VALUES.
PDS0571 GUEST NAME CANNOT BE ALL LOW-VALUES OR ALL HIGH- Both
VALUES.


2184 PDS0572 GUEST NUMBER CANNOT BE ALL LOW-VALUES OR ALL Both
HIGH-VALUES.
PDS0573 INVOICE NUMBER CANNOT BE ALL LOW-VALUES OR ALL Both
HIGH-VALUES.
PDS0576 FOLIO NUMER CANNOT BE ALL LOW-VALUES OR ALL HIGH- Both
VALUES.
PDS0577 PROPERTY PHONE NUMBER CANNOT BE ALL LOW-VALUES Both
OR ALL HIGH-VALUES.
PDS0582 PROGRAM CODE CANNOT BE ALL LOW-VALUES OR ALL Both
HIGH-VALUES.
PDS0588S1 OTHER SERVICES CODE CANNOT BE ALL LOW-VALUES OR Both
HIGH-VALUES.
PDS0591S1 PARTY NAME CANNOT BE ALL LOW-VALUES OR ALL HIGH- Both
VALUES.
PDS0592S1 PARTY ADDRESS LINE CANNOT BE ALL LOW-VALUES OR Both
ALL HIGH-VALUES.
PDS0593S1 CITY CANNOT BE ALL LOW-VALUES OR ALL HIGH-VALUES. Both
PDS0593S2 STATE/PROVINCE CANNOT BE ALL LOW-VALUES OR ALL Both
HIGH-VALUES.
PDS0593S3 COUNTRY CODE CANNOT BE ALL LOW-VALUES OR ALL Both
HIGH-VALUES.
PDS0593S4 POSTAL CODE CANNOT BE ALL LOW-VALUES OR ALL Both
HIGH-VALUES.
PDS0594S2 PARTY CONTACT INFORMATION CANNOT BE ALL LOW- Both
PDS0595S1 BUSINESS TYPE CANNOT BE ALL LOW-VALUES OR ALL Both
HIGH-VALUES.
PDS0595S2 BUSINESS OWNER TYPE CANNOT BE ALL LOW-VALUES OR Both
ALL HIGH-VALUES.
PDS0595S3 BUSINESS CERTIFICATION TYPE CANNOT BE ALL LOW- Both
PDS0595S4 BUSINESS RACIAL/ETHNIC TYPE CANNOT BE ALL LOW- Both
PDS0598 TOTAL TAX COLLECTED INDICATOR CANNOT BE ALL LOW- Both


2184 PDS0599 CORPORATION VAT NUMBER CANNOT BE ALL LOW-VALUES Both
OR ALL HIGH-VALUES.
PDS0600 CARD REFERENCE NUMBER CANNOT BE ALL LOW-VALUES Both
OR ALL HIGH-VALUES.
PDS0602S1 PARTY SUPPLEMENTAL DATA DESCRIPTION 1 CANNOT BE Both
PDS0602S2 PARTY SUPPLEMENTAL DATA 1 CANNOT BE ALL LOW- Both
PDS0602S3 PARTY SUPPLEMENTAL DATA CODE 1 CANNOT BE ALL Both
PDS0603S1 PARTY SUPPLEMENTAL DATA DESCRIPTION 2 CANNOT BE Both
PDS0603S2 PARTY SUPPLEMENTAL DATA 2 CANNOT BE ALL LOW- Both
PDS0603S3 PARTY SUPPLEMENTAL DATA CODE 2 CANNOT BE ALL Both
PDS0604S2 TRANSACTION SUPPLEMENTAL DATA 1 CANNOT BE ALL Both
PDS0604S3 TRANSACTION SUUPLEMENTAL DATA CODE 1 CANNOT BE Both
PDS0605S2 TRANSACTION SUPPLEMENTAL DATA 2 CANNOT BE ALL Both
PDS0605S3 TRANSACTION SUPPLEMENTAL DATA CODE 2 CANNOT BE Both
PDS0608 DESTINATION POSTAL CODE CANNOT BE ALL LOW-VALUES Both
OR ALL HIGH-VALUES.
PDS0609 DESTINATION STATE/PROVINCE CANNOT BE ALL LOW- Both
PDS0613 SHIP-FROM POSTAL CODE CANNOT BE ALL LOW-VALUES OR Both
ALL HIGH-VALUES.


2184 PDS0616 CONTRACT NUMBER CANNOT BE ALL LOW-VALUES OR ALL Both
HIGH-VALUES.
PDS0619 USER NAME CANNOT BE ALL LOW-VALUES OR ALL HIGH- Both
VALUES.
PDS0624 USER ACCOUNT NUMBER CANNOT BE ALL LOW-VALUES OR Both
ALL HIGH-VALUES.
PDS0625 USER TELEPHONE NUMBER CANNOT BE ALL LOW-VALUES Both
OR ALL HIGH-VALUES.
PDS0627S4 BILLING EVENT DESCRIPTION 1 CANNOT BE ALL LOW- Both
PDS0628S4 BILLING EVENT DESCRIPTION 2 CANNOT BE ALL LOW- Both
PDS0629 ODOMETER READING CANNOT BE ALL LOW-VALUES OR ALL Both
HIGH-VALUES.
PDS0630 VEHICLE NUMER CANNOT BE ALL LOW-VALUES OR ALL Both
HIGH-VALUES.
PDS0631 DRIVER NUMBER/ID NUMBER CANNOT BE ALL LOW-VALUES Both
OR ALL HIGH-VALUES.
PDS0638S1 CALL TO CITY CANNOT BE ALL LOW-VALUES OR ALL Both
HIGH-VALUES.
PDS0638S2 CALL TO STATE/PROVINCE CANNOT BE ALL LOW-VALUES Both
OR ALL HIGH-VALUES.
PDS0638S3 CALL TO COUNTRY CANNOT BE ALL LOW-VALUES OR ALL Both
HIGH-VALUES.
PDS0638S4 CALL TO NUMBER CANNOT BE ALL LOW-VALUES OR ALL Both
HIGH-VALUES
PDS0642 ITEM DESCRIPTION CANNOT BE ALL LOW-VALUES OR ALL Both
HIGH-VALUES.
PDS0644S1 CALL FROM CITY CANNOT BE ALL LOW-VALUES OR ALL Both
HIGH-VALUES.
PDS0644S2 CALL FROM STATE/PROVINCE CANNOT BE ALL LOW- Both
PDS0644S3 CALL FROM COUNTRY CANNOT BE ALL LOW-VALUES OR Both
ALL HIGH-VALUES.
PDS0644S4 CALL FROM NUMBER CANNOT BE ALL LOW-VALUES OR Both
ALL HIGH-VALUES.


2184 PDS0645 ITEM UNIT OF MEASURE CANNOT BE ALL LOW-VALUES OR Both
ALL HIGH-VALUES.
PDS0659 OTHER DESCRIPTION MUST BE LEFT JUSTIFIED AND Both
PDS0663 FREE-FORM DESCRIPTION CANNOT BE ALL LOW-VALUES OR Both
ALL HIGH-VALUES.
PDS0682S7 CARD ACCEPTOR TAX ID 1 CANNOT BE ALL LOW-VALUES Both
OR ALL HIGH-VALUES.
OR ALL HIGH-VALUES.
OR ALL HIGH-VALUES.
PDS0732S4 DISCOUNT TYPE CANNOT BE ALL LOW-VALUES OR ALL Both
HIGH-VALUES.
OR ALL HIGH-VALUES.
OR ALL HIGH-VALUES.
OR ALL HIGH-VALUES.
PDS0799 TEST CASE TRACABILITY IDENTIFIERS CANNOT BE ALL LOW- Both
2185 PDS0519S1 HOURS OF OPERATION/24 HOUR AVAILABLE MUST BE A Both
VALUE OF Y OR N.
PDS0519S2 18 WHEELER ACCESS AVAILABLE MUST BE A VALUE OF Y Both
OR N.
PDS0519S3 DIESEL SITES AVAILABLE MUST BE A VALUE OF Y OR N. Both
PDS0519S4 INTERSTATE ACCESS/EXIT NUMBER WITH DIRECTIONS Both
AVAILABLE MUST BE A VALUE OF Y OR N.
PDS0519S5 CONVENIENCE STORE AVAILABLE MUST BE A VALUE OF Y Both
OR N.
PDS0519S6 TRUCK STOP RESTAURANT AVAILABLE MUST BE A VALUE Both
OF Y OR N.
PDS0519S7 TRUCK STOP HOTEL AVAILABLE MUST BE A VALUE OF Y Both
OR N.


2185 PDS0519S8 TRUCK STOP WITH SHOWERS AVAILABLE MUST BE A Both
VALUE OF Y OR N.
PDS0519S9 VEHICLE MAINTENANCE/REPAIR BAYS AVAILABLE MUST Both
BE A VALUE OF Y OR N.
PDS0519S10 CAR WASH AVAILABLE MUST BE A VALUE OF Y OR N. Both
PDS0519S11 AVIATION LOCATIONS AVAILABLE MUST BE A VALUE OF Both
Y OR N.
PDS0519S12 MARINA LOCATIONS AVAILABLE MUST BE A VALUE OF Y Both
OR N.
PDS0519S13 ALTERNATIVE FUEL LOCATIONS AVAILABLE MUST BE A Both
VALUE OF Y OR N.
PDS0519S14 PAY-AT-PUMP AVAILABLE MUST BE A VALUE OF Y OR N. Both
PDS0534S3 TOTAL NON-ROOM CHARGES SIGN MUST BE D OR C. Both
PDS0539S3 TOTAL AMOUNT CHARGED ON CREDIT CARD SIGN MUST Both
BE D OR C.
PDS0540S3 ROOM SERVICE CHARGES SIGN MUST BE D OR C. Both
PDS0541S3 LOUNGE/BAR CHARGES SIGN MUST BE D OR C. Both
PDS0542S3 TRANSPORTATION CHARGES SIGN MUST BE D OR C. Both
PDS0543S3 GRATUITY CHARGES SIGN MUST BE D OR C. Both
PDS0554S3 CONFERENCE ROOM CHARGES SIGN MUST BE D OR C. Both
PDS0560S3 AUDIO VISUAL CHARGES SIGN MUST BE D OR C. Both
PDS0562S3 BANQUET CHARGES SIGN MUST BE D OR C. Both
PDS0569S3 INTERNET ACCESS CHARGES SIGN MUST BE D OR C. Both
PDS0570S3 EARLY DEPARTURE CHARGES SIGN MUST BE D OR C. Both
PDS0578S4 BILLING ADJUSTMENT SIGN MUST BE D OR C. Both
PDS0581S3 TOTAL ROOM TAX SIGN MUST BE D OR C. Both
PDS0583S3 PHONE CHARGES SIGN MUST BE D OR C. Both
PDS0584S3 RESTAURANT CHARGES SIGN MUST BE D OR C. Both
PDS0585S3 MINI-BAR CHARGES SIGN MUST BE D OR C. Both
PDS0586S3 GIFT SHOP CHARGES SIGN MUST BE D OR C. Both
PDS0587S3 LAUNDRY & DRY CLEANING CHARGES SIGN MUST BE D Both
OR C.


2185 PDS0588S4 OTHER SERVICES SIGN MUST BE D OR C. Both
PDS0590 PARTY IDENTIFICATION MUST BE BY, SU, IV, PE, DP, OR SF. Both
PDS0594S1 PARTY CONTACT DESCRIPTOR MUST BE 1, 2, 3, 4, OR 5. Both
PDS0595S5 BUSINESS TYPE PROVIDED MUST BE 7, N OR R. Both
PDS0595S6 BUSINESS OWNER TYPE PROVIDED MUST BE Y, N, OR R. Both
PDS0595S7 BUSINESS CERTIFICATION TYPE PROVIDED MUST BE Y, N, Both
OR R.
PDS0595S8 BUSINESS RACIAL/ETHNIC TYPE MUST BE Y, N, OR R. Both
PDS0596S2 CARD ACCEPTOR TAX ID MUST BE Y, N, OR R. Both
PDS0597S3 TOTAL TAX AMOUNT SIGN MUST BE D OR C. Both
PDS0601 PARTY NATURE OF FILING MUST BE P, S, E, OR N. Both
PDS0606S3 FREIGHT AMOUNT SIGN MUST BE D OR C. Both
PDS0607S3 DUTY AMOUNT SIGN MUST BE D OR C. Both
PDS0617 MEDICAL SERVICES PRICE ADJUSTMENT MUST BE A, B, C, Both
OR D.
PDS0618 MEDICAL SERVICES PRODUCT NUMBER QUALIFIER MUST BE Both
01, 02, OR 03.
PDS0627S3 BILLING EVENT SIGN 1 MUST BE D OR C. Both
PDS0628S3 BILLING EVENT SIGN 2 MUST BE D OR C. Both
PDS0638S5 CALL TO TYPE MUST BE C, I, V, P, O, OR F. Both
PDS0640 CALL TIME PERIOD MUST BE PP, OP, MP OR OT. Both
PDS0641 PRODUCT CODE MUST BE L-1000, L-1020, L-1021, L-1100, Both
L-1101, L-1102, L-1103, L-1104, L-1105, L-1106, L-1107, L-1108, L-1109,
L-1110, L-1111, L-1112, L-1113, L-1114, L-1115, L-1116, L-1117, L-1118,
1-1119, L-1120, L-1121, L-1122, L-9999.
PDS0647S3 EXTENDED ITEM AMOUNT SIGN MUST BE D OR C. Both
PDS0648S5 ITEM DISCOUNT AMOUNT SIGN MUST BE D OR C. Both
PDS0649S3 CALL USAGE AMOUNT SIGN MUST BE D OR C. Both
PDS0655S3 CALL LONG DISTANCE AMOUNT SIGN MUST BE D OR C. Both
PDS0658S3 CALL CONNECT AMOUNT SIGN MUST BE D OR C. Both
PDS0682S8 DETAIL TAX AMOUNT SIGN 1 MUST BE D OR C. Both


2185 PDS0683S8 DETAIL TAX AMOUNT SIGN2 MUST BE D OR C. Both
PDS0693S3 TOTAL AUTHORIZED AMOUNT SIGN MUST BE D OR C. Both
PDS0699S3 LODGING TOTAL AMOUNT SIGN MUST BE D OR C. Both
PDS0704S3 PREPAID EXPENSE AMOUNT SIGN MUST BE D OR C. Both
PDS0705S3 TOTAL NON-ROOM TAX AMOUNT SIGN MUST BE D OR C. Both
PDS0706S3 CASH ADVANCE SIGN MUST BE D OR C. Both
PDS0707S3 VALET CHARGES SIGN MUST BE D OR C. Both
PDS0708S3 MOVIE CHARGES SIGN MUST BE D OR C. Both
PDS0709S3 BUSINESS CENTER CHARGES SIGN MUST BE D OR C. Both
PDS0710S3 HEALTH CLUB CHARGES SIGN MUST BE D OR C. Both
PDS0722 FLAT RATE INDICATOR MUST BE Y OR N. Both
PDS 732S3 DISCOUNT AMOUNT SIGN MUST BE D OR C. Both
PDS0733S3 SUBTOTAL AMOUNT SIGN MUST BE D OR C. Both
PDS0734S4 MISCELLANEOUS EXPENSES AMOUNT SIGN MUST BE D Both
OR C.
PDS0737S3 SHIPPING NET AMOUNT SIGN MUST BE D OR C. Both
PDS0738S3 INCENTIVE AMOUNT SIGN MUST BE D OR C. Both
PDS0747S1 SHIPPING PARTY DESCRIPTOR MUST BE 1, 2, 3, 4, OR 5. Both
PDS0751S1 DETAIL TAX AMOUNT INDICATOR 4 MUST BE Y, N, OR Both
SPACE.
PDS0751S6 DETAIL TAX TYPE IDENTIFIER 4 MUST BE 00, 01, 02, 03, 04, Both
05, 06, 10, 11, 12, 20, 21, 22, OR SPACES.
SPACE.
PDS0752S6 DETAIL TAX TYPE IDENTIFIER 5 MUST BE 00, 01, 02, 03, 04, Both
05, 06, 10, 11, 12, 20, 21, 22 OR SPACES.
SPACE.


05, 06, 10, 11, 12, 20, 21, 22, OR SPACES.
PDS0754S1 DELIVERY PARTY DESCRIPTOR MUST BE 1, 2, 3, 4, OR 5. Both
PDS0755S3 LINE ITEM TOTAL AMOUNT SIGN MUST BE D OR C. Both
2186 PDS0518 LINE ITEM DATE MUST BE A VALID DATE IN THE FORMAT Both
YYMMDD.
PDS0579 INVOICE DATE MUST BE A VALID DATE IN THE FORMAT Both
YYMMDD.
PDS0589S1 INVOICE CREATION DATE MUST BE A VALID DATE IN THE Both
FORMAT YYMMDD.
PDS0612 SHIP DATE MUST BE A VALID DATE IN THE FORMAT Both
YYMMDD.
PDS0626S1 STATEMENT START DATE MUST BE A VALID DATE IN THE Both
FORMAT YYMMDD.
PDS0626S2 STATEMENT END DATE MUST BE A VALID DATE IN THE Both
FORMAT YYMMDD.
PDS0636 CALL DATE MUST BE A VALID DATE IN THE FORMAT Both
YYMMDD.
PDS0727 TEMP START DATE MUST BE A VALID DATE IN THE FORMAT Both
YYMMDD.
PDS0728 TEMP WEEK ENDING MUST BE A VALID DATE IN THE Both
FORMAT YYMMDD.
PDS0739 PICKUP DATE MUST BE A VALID DATE IN THE FORMAT Both
YYMMDD.
PDS0740 DELIVERY DATE MUST BE A VALID DATE IN THE FORMAT Both
YYMMDD.
2187 PDS0505 PASSENGER NAME REQUIRED FOR AIRLINE TRANSACTIONS Both
SUBMITTED FOR T&E III.
PDS0506 TICKET NUMBER REQUIRED FOR AIRLINE TRANSACTIONS Both
PDS0507 ISSUING CARRIER REQUIRED FOR AIRLINE TRANSACTIONS Both
PDS0512 TOTAL FARE REQUIRED FOR AIRLINE TRANSACTIONS Both


2187 PDS0520 TRAVEL DATE REQUIRED FOR AIRLINE TRANSACTIONS Both
PDS0521 CARRIER CODE REQUIRED FOR AIRLINE TRANSACTIONS Both
PDS0522 SERVICE CLASS CODE REQUIRED FOR AIRLINE Both
TRANSACTIONS SUBMITTED FOR T&E III.
PDS0523 CITY OF ORIGIN/AIRPORT CODE REQUIRED FOR AIRLINE Both
PDS0524 CITY OF DESTINATION/AIRPORT CODE REQUIRED FOR Both
AIRLINE TRANSACTIONS SUBMITTED FOR T&E III.
PDS0525 STOP OVER CODE REQUIRED FOR AIRLINE TRANSACTIONS Both
PDS0529 FARE BASIS CODE REQUIRED FOR AIRLINE TRANSACTIONS Both
PDS0530 FLIGHT NUMBER REQUIRED FOR AIRLINE TRANSACTIONS Both
PDS0531 DEPARTURE TIME REQUIRED FOR AIRLINE TRANSACTIONS Both
2188 PDS0505 PASSENGER NAME REQUIRED FOR PASSENGER RAILWAY Both
PDS0506 TICKET NUMBER REQUIRED FOR PASSENGER RAILWAY Both
PDS0507 ISSUING CARRIER REQUIRED FOR PASSENGER RAILWAY Both
PDS0512 TOTAL FARE REQUIRED FOR PASSENGER RAILWAY Both
PDS0520 TRAVEL DATE REQUIRED FOR PASSENGER RAILWAY Both
PDS0521 CARRIER CODE REQUIRED FOR PASSENGER RAILWAY Both
PDS0522 SERVICE CLASS CODE REQUIRED FOR PASSENGER RAILWAY Both
PDS0523 CITY OF ORIGIN/AIRPORT CODE REQUIRED FOR PASSENGER Both
RAILWAY TRANSACTIONS SUBMITTED FOR T&E III.
PDS0524 CITY OF DESTINATION/AIRPORT CODE REQUIRED FOR Both
PASSENGER RAILWAY TRANSACTIONS SUBMITTED FOR T&E III.


2188 PDS0525 STOP OVER CODE REQUIRED FOR PASSENGER RAILWAY Both
PDS0529 FARE BASIS CODE REQUIRED FOR PASSENGER RAILWAY Both
PDS0530 FLIGHT NUMBER REQUIRED FOR PASSENGER RAILWAY Both
PDS0531 DEPARTURE TIME REQUIRED FOR PASSENGER RAILWAY Both
2189 PDS0544 RENTAL AGREEMENT NUMBER REQUIRED FOR VEHICLE Both
RENTAL TRANSACTIONS SUBMITTED FOR T&E III.
PDS0545 RENTER NAME REQUIRED FOR VEHICLE RENTAL Both
PDS0546 RENTAL RETURN CITY REQUIRED FOR VEHICLE RENTAL Both
PDS0547 RENTAL RETURN STATE/PROVINCE REQUIRED FOR VEHICLE Both
PDS0548 RENTAL RETURN COUNTRY REQUIRED FOR VEHICLE RENTAL Both
PDS0549 RENTAL RETURN LOCATION ID REQUIRED FOR VEHICLE Both
PDS0550 RENTAL RETURN DATE REQUIRED FOR VEHICLE RENTAL Both
PDS0551 RENTAL CHECK-OUT DATE REQUIRED FOR VEHICLE RENTAL Both
PDS0552 CUSTOMER SERVICE TOLL-FREE NUMBER REQUIRED FOR Both
VEHICLE RENTAL TRANSACTIONS SUBMITTED FOR T&E III.
PDS0564 RENTAL LOCATION CITY REQUIRED FOR VEHICLE RENTAL Both
PDS0565 RENTAL LOCATION STATE/PROVINCE REQUIRED FOR Both
VEHICLE RENTAL TRANSACTIONS SUBMITTED FOR T&E III.
PDS0566 RENTAL LOCATION COUNTRY REQUIRED FOR VEHICLE Both
PDS0568 RENTAL CLASS IDENTIFIER REQUIRED FOR VEHICLE RENTAL Both
PDS0686 TAX EXEMPT INDICATOR REQUIRED FOR VEHICLE RENTAL Both


2189 PDS0691 DAYS RENTED REQUIRED FOR VEHICLE RENTAL Both
2190 PDS0552 CUSTOMER SERVICE TOLL-FREE NUMBER REQUIRED FOR Both
LODGING TRANSACTIONS SUBMITTED FOR T&E III.
PDS0574 ARRIVAL DATE REQUIRED FOR LODGING TRANSACTIONS Both
PDS0575 DEPARTURE DATE REQUIRED FOR LODGING TRANSACTIONS Both
PDS0576 FOLIO NUMBER REQUIRED FOR LODGING TRANSACTIONS Both
PDS0577 PROPERTY PHONE NUMBER REQUIRED FOR LODGING Both
PDS0580 ROOM RATE REQUIRED FOR LODGING TRANSACTIONS Both
PDS0581 ROOM TAX REQUIRED FOR LODGING TRANSACTIONS Both
PDS0703 TOTAL ROOM NIGHTS REQUIRED FOR LODGING Both
PDS0711 FIRE SAFETY ACT INDICATOR REQUIRED FOR LODGING Both
2191 PDS0744 SHIPPING PARTY INFORMATION LENGTH MUST BE 050–150 Both
PDS0748 DELIVERY PARTY INFORMATION LENGTH MUST BE 050–150 Both
2192 PDS0745 SHIPPING PARTY ADDRESS LENGTH MUST BE 050–300 AND Both
MUST BE DIVISIBLE BY MINIMUM OCCURRENCE LENGTH OF 50.
PDS0749 DELIVERY PARTY ADDRESS INFORMATION LENGTH MUST BE Both
050–300 AND MUST BE DIVISIBLE BY MINIMUM OCCURRENCE
LENGTH OF 50.
2193 PDS0747 SHIPPING PARTY CONTACT LENGTH MUST BE 061–305 AND Both
PDS0754 DELIVERY PARTY CONTACT LENGTH MUST BE 061–305 AND Both
2194 PDS0734 MISCELLANEOUS EXPENSES LENGTH MUST BE 054-216 AND Both


2195 PDS0641 PRODUCT CODE MUST BE PRESENT IN A LINE ITEM DETAIL Both
ADDENDUM MESSAGE.
PDS0642 ITEM DESCRIPTION MUST BE PRESENT IN A LINE ITEM Both
DETAIL ADDENDUM MESSAGE.
PDS0643 ITEM QUANTITY MUST BE PRESENT IN A LINE ITEM DETAIL Both
ADDENDUM MESSAGE.
PDS0645 ITEM UNIT OF MEASURE MUST BE PRESENT IN A LINE ITEM Both
DETAIL ADDENDUM MESSAGE.
PDS0647 EXTENDED ITEM AMOUNT MUST BE PRESENT IN A LINE Both
ITEM DETAIL ADDENDUM MESSAGE.
PDS0654 DEBIT OR CREDIT INDICATOR MUST BE PRESENT IN A LINE Both
ITEM DETAIL ADDENDUM MESSAGE.
2196 DE32 AQUIRING INSTITUTION IDENTIFICATION CODE MUST BE Both
NUMERIC AND CANNOT BE ALL ZEROS.
PDS0174 DUN & BRADSTREET NUMBER MUST BE NUMERIC AND Both
CANNOT BE ALL ZEROS.
PDS0261 RISK MANAGEMENT APPROVAL CODE MUST BE NUMERIC Both
AND CANNOT BE ALL ZEROS.
PDS0556 TOTAL MILES (OR KILOMETERS) MUST BE NUMERIC AND Both
PDS0755 LINE ITEM TOTAL AMOUNT IF PRESENT MUST BE NUMERIC Both
AND CANNOT BE ALL ZEROS.
PDS0755S1 LINE ITEM TOTAL AMOUNT MUST BE NUMERIC AND Both
2197 WHEN DE55 INTEGRATED CIRCUIT CARD (ICC) SYSTEM RELATED Both
DATA IS PRESENT DE22 MUST BE PRESENT AND DE22S7 CARD DATA
INPUT MODE MUST BE AN F, C, M, S, OR T.
2198 DE38 APPROVAL CODE CANNOT BE PRESENT WHEN DE022S7 CARD Both
DATA INPUT MODE CONTAINS AN F.
2199 PDS0375 MEMBER RECONCILIATION INDICATOR 1 NOT LEFT Both
JUSTIFIED.
2200 DE55 INTEGRATED CIRCUIT CARD (ICC) SYSTEM RELATED DATA GCMS
CANNOT BE ALL ZEROS OR ALL SPACES.
PDS0641 PRODUCT CODE CANNOT BE ALL ZEROS OR ALL SPACES. Both
PDS0642 ITEM DESCRIPTION CANNOT BE ALL ZEROS OR ALL SPACES. Both


2202 DE4 AMOUNT, TRANSACTION EXCEEDS THE MASTERCARD DEFINED GCMS
ACQUIRER LIMIT.
2203 DE4 AMOUNT, TRANSACTION EXCEEDS THE MASTERCARD DEFINED GCMS
ISSUER LIMIT.
2204 PDS0261 RISK MANAGEMENT APPROVAL CODE INVALID. GCMS
2205 DE 25 MESSAGE REASON CODE AND DE 3 PROCESSING CODE Both
2206 PDS0261-RISK MANAGEMENT APPROVAL CODE HAS EXPIRED. GCMS
2207 THE VALUE IN PDS0596 CARD ACCEPTOR TAX ID IS CONTAINED IN A GCMS
LIST OF INVALID VALUES FOR THIS ELEMENT.
THE VALUE IN PDS0596S1 CARD ACCEPTOR TAX ID IS CONTAINED IN
A LIST OF INVALID VALUES FOR THIS ELEMENT.
2208 DE37 RETRIEVAL REFERENCE NUMBER CANNOT BE ALL ZEROS OR ALL Both
SPACES
DE72 DATA RECORD CANNOT BE ALL ZEROS OR ALL SPACES. Both
PDS0043 PROGRAM REGISTRATION ID CANNOT BE ALL ZEROS OR ALL Both
SPACES.
PDS0170 MERCHANT INQUIRY INFORMATION CANNOT BE ZEROS OR Both
ALL SPACES.
PDS0189S2 POINT OF INTERACTION (POI) PHONE DATA CANNOT BE Both
PDS0190 PARTNER ID CODE CANNOT BE ALL ZEROS OR ALL SPACES. Both
PDS0241 MASTERCOM CONTROL NUMBER CANNOT BE ALL ZEROS OR Both
ALL SPACES.
PDS0265S3 DATA RECORD CANNOT BE ALL ZEROS OR ALL SPACES. Both
PDS0266S7 DATA RECORD FIRST RETURN CANNOT BE ALL ZEROS OR Both
ALL SPACES.
PDS0267S7 SECOND PRESENTMENT/FEE COLLECTION RESUBMISSION Both
DATA SECOND RETURN CANNOT BE ALL ZEROS OR ALL SPACES.
PDS0375 MEMBER RECONCILIATION INDICATOR 1 CANNOT BE ALL Both
ZEROS OR ALL SPACES.
PDS0528 COUPON NUMBER CANNOT CONTAIN ALL ZEROS OR ALL Both
SPACES.
PDS0529 FARE BASIS CODE CANNOT CONTAIN ALL ZEROS OR ALL Both
SPACES.


2208 PDS0643S1 ITEM QUANTITY CANNOT BE ALL ZEROS OR ALL SPACES. GCMS
PDS0645 ITEM UNIT OF MEASURE CANNOT BE ALL ZEROS OR ALL Both
SPACES.
PDS0647 EXTENDED ITEM AMOUNT CANNOT BE ALL ZEROS OR ALL Both
SPACES.
001–999 FOR USAGE CODE 05 AND INDUSTRY RECORD NUMBER 000.
2215 PDS0525 STOP OVER CODE MUST CONTAIN A VALUE WITHIN THE Both
RANGE OF 0–9, A-Z, OR SPACE.
PDS0532S2 TOTAL CHARGES EXPONENT MUST CONTAIN A VALUE Both
WITHIN THE RANGE OF 0–5.
PDS0534S2 TOTAL NON-ROOM CHARGES EXPONENT MUST CONTAIN Both
A VALUE WITHIN THE RANGE OF 0–5.
PDS0539S2 TOTAL NON-ROOM CHARGES EXPONENT MUST CONTAIN Both
PDS0540S2 ROOM SERVICE CHARGES EXPONENT MUST CONTAIN A Both
VALUE WITHIN THE RANGE OF 0–5.
PDS0541S2 LOUNGE/BAR CHARGES EXPONENT MUST CONTAIN A Both
PDS0542S2 TRANSPORTATION CHARGES EXPONENT MUST CONTAIN A Both
PDS0543S2 GRATUITY CHARGES EXPONENT MUST CONTAIN A VALUE Both
PDS0554S2 CONFERENCE ROOM CHARGES EXPONENT MUST CONTAIN Both


2215 PDS0560S2 AUDIO VISUAL CHARGES EXPONENT MUST CONTAIN A Both
PDS0562S2 BANQUET CHARGES EXPONENT MUST CONTAIN A VALUE Both
PDS0569S2 INTERNET ACCESS CHARGES EXPONENT MUST CONTAIN A Both
PDS0570S2 EARLY DEPARTURE CHARGES EXPONENT MUST CONTAIN Both
PDS0578S3 BILLING ADJUSTMENT EXPONENT MUST CONTAIN A Both
PDS0580S2 ROOM RATE EXPONENT MUST CONTAIN A VALUE WITHIN Both
THE RANGE OF 0–5.
PDS0581S2 TOTAL ROOM TAX EXPONENT MUST CONTAIN A VALUE Both
WITHIN THE RANGE 0–5.
PDS0583S2 PHONE CHARGES EXPONENT MUST CONTAIN A VALUE Both
PDS0584S2 RESTAURANT CHARGES EXPONENT MUST CONTAIN A Both
VALUE WITHIN THE RANGE 0–5.
PDS0585S2 MINI BAR CHARGES EXPONENT MUST CONTAIN A VALUE Both
PDS0586S2 GIFT SHOP CHARGES EXPONENT MUST CONTAIN A VALUE Both
PDS0587S2 LAUNDRY AND DRY CLEANING CHARGES EXPONENT Both
MUST CONTAIN A VALUE WITHIN THE RANGE 0–5.
PDS0588S3 OTHER SERVICES EXPONENT MUST CONTAIN A VALUE Both
PDS0597S2 TOTAL TAX AMOUNT EXPONENT MUST CONTAIN A VALUE Both
PDS0606S2 FREIGHT AMOUNT EXPONENT MUST CONTAIN A VALUE Both
PDS607S2 DUTY AMOUNT EXPONENT MUST CONTAIN A VALUE Both
PDS0627S2 BILLING EVENT EXPONENT 1 MUST CONTAIN A VALUE Both
PDS0628S2 BILLING EVENT EXPONENT 2 MUST CONTAIN A VALUE Both


2215 PDS0643S2 ITEM QUANTITY EXPONENT MUST CONTAIN A VALUE Both
PDS0646S2 UNIT PRICE EXPONENT MUST CONTAIN A VALUE WITHIN Both
THE RANGE OF 0–5.
PDS0647S2 EXTENDED ITEM AMOUNT EXPONENT MUST CONTAIN A Both
PDS0648S4 ITEM DISCOUNT RATE EXPONENT MUST CONTAIN A Both
PDS0649S2 CALL USAGE AMOUNT EXPONENT Both
PDS0655S2 CALL LONG DISTANCE AMOUNT EXPONENT MUST Both
CONTAIN A VALUE WITHIN THE RANGE OF 0–5.
PDS0658S2 CALL CONNECT AMOUNT EXPONENT MUST CONTAIN A Both
PDS0693S2 TOTAL AUTHORIZED AMOUNT EXPONENT MUST CONTAIN Both
PDS0699S2 LODGING TOTAL TAX AMOUNT EXPONENT MUST Both
PDS07042S2 PREPAID EXPENSES AMOUNT EXPONENT MUST CONTAIN Both
PDS0705S2TOTAL NON-ROOM TAX AMOUNT EXPONENT MUST Both
CONTAIN A VALUE WITHIN THE RANGE 0–5.
PDS0706S2 CASH ADVANCE EXPONENT MUST CONTAIN A VALUE Both
PDS0707S2 VALET CHARGES EXPONENT MUST CONTAIN A VALUE Both
PDS0708S2 MOVIE CHARGES EXPONENT MUST CONTAIN A VALUE Both
PDS0709S2 BUSINESS CENTER CHARGES EXPONENT MUST CONTAIN A Both
PDS0710S2 HEALTH CLUB CHARGES EXPONENT MUST CONTAIN A Both
PDS0723S2 REGULAR HOURS WORKED EXPONENT MUST CONTAIN A Both
PDS0724S2 REGULAR HOURS RATE EXPONENT MUST CONTAIN A Both


2215 PDS0725S2 OVERTIME HOURS WORKED EXPONENT MUST CONTAIN A Both
PDS0726S2 OVERTIME HOURS RATE EXPONENT MUST CONTAIN A Both
PDS0732S2 DISCOUNT AMOUNT EXPONENT MUST CONTAIN A VALUE Both
PDS0733S2 SUBTOTAL AMOUNT EXPONENT MUST CONTAIN A VALUE Both
PDS0734S3 MISCELLANEOUS EXPENSES AMOUNT EXPONENT MUST Both
CONTAIN A VALUE WITH THE RANGE OF 0–5.
PDS0737S2 SHIPPING NET AMOUNT EXPONENT MUST CONTAIN A Both
PDS0738S2 INCENTIVE AMOUNT EXPONENT MUST CONTAIN A VALUE Both
PDS0751S4 DETAIL TAX RATE EXPONENT 4 MUST CONTAIN A VALUE Both
PDS0755S2 LINE ITEM TOTAL AMOUNT EXPONENT MUST CONTAIN A Both
2217 PDS0158S3 BUSINESS SERVICE ID CODE MUST BE PRESENT AND VALID Both
WHEN PDS0158S2 BUSINESS SERVICE ARRANGEMENT TYPE CODE IS
PRESENT.
2218 PDS0158S2 BUSINESS SERVICE ARRANGEMENT TYPE CODE MUST BE Both
PRESENT AND VALID WHEN PDS0158S3 BUSINESS SERVICE ID CODE IS
PRESENT.
2219 DE25 MESSAGE REASON CODE INVALID FOR BUSINESS SERVICE Both
ARRANGEMENT <BSID&TYPE> AND ACCEPTANCE BRAND ID CODE
<AB>.
2220 DE3 PROCESSING CODE INVALID FOR BUSINESS SERVICE Both
ARRANGEMENT <BSID & TYPE> AND ACCEPTANCE BRAND ID CODE
<AB>.
2221 PDS0158S4 INTERCHANGE RATE DESIGNATOR MISSING FOR BUSINESS Both
SERVICE ARRANGEMENT <BSID & TYPE> AND ACCEPTANCE BRAND
ID CODE <AB>


2223 DE26 CARD ACCEPTOR BUSINESS CODE (MCC) INVALID FOR Both
BUSINESS SERVICE ARRANGEMENT <BSID &TYPE> AND ACCEPTANCE
BRAND ID CODE <AB>.
2224 DE26 CARD ACCEPTOR BUSINESS CODE (MCC) INVALID FOR Both
BUSINESS SERVICE ARRANGEMENT <BSID&TYPE> AND ACCEPTANCE
BRAND ID CODE <AB> FOR INTERCHANGE PROGRAM.
2225 BRAND PRODUCT <DERIVED FROM DE 2> INVALID FOR BUSINESS Both
SERVICE ARRANGEMENT <BSID & TYPE> AND ACCEPTANCE BRAND
ID CODE <AB>.
2226 BRAND PRODUCT <DERIVED FROM DE 2> INVALID FOR BUSINESS Both
SERVICE ARRANGEMENT <BSID&TYPE> AND ACCEPTANCE BRAND ID
CODE <AB> FOR INTERCHANGE PROGRAM.
2227 PDS0158S1 INVALID. MUST BE <VALLIST>. Both
2228 PDS0170S3 MERCHANT INQUIRY INFORMATION ADDITIONAL Both
INFORMATION CANNOT CONTAIN ALL ZEROS.
2229 DE43S1 INVALID, MUST CONTAIN ABBREVIATED AIRLINE NAME Both
FOLLOWED BY DELIMETER OR SPACE AND DELIMETER.
2232 PDS0561S2 ADJUSTED AMOUNT MUST BE NUMERIC AND GREATER Both
THAN ZERO.
PDS0643S1 ITEM QUANTITY MUST BE NUMERIC AND GREATER THAN Both
ZERO.
PDS0647S1 EXTENDED ITEM AMOUNT MUST BE NUMERIC AND Both
GREATER THAN ZERO.
2233 PDS0682S7 CARD ACCEPTOR TAX ID 1 MUST BE LEFT JUSTIFIED AND Both
PDS0683S7 CARD ACCEPTOR TAX ID 2 MUST BE LEFT JUSTIFIED AND Both


2235 PDS0518 LINE ITEM DATE MUST BE PRESENT AND A VALID DATE Both
WHEN LODGING SUMMARY IS PRESENT.
2236 PDS0591 PARTY NAME LENGTH MUST BE 040–120 AND MUST BE Both
DIVISIBLE BY MINIMUM OCCURRENCE LENGTH OF 040.
PDS0592 PARTY ADDRESS LENGTH MUST BE 040–240 AND MUST BE Both
PDS0594 PARTY CONTACT LENGTH MUST BE 061–305 AND MUST BE Both
PDS0602 PARTY SUPPLEMENTAL DATA 1 LENGTH MUST BE 084-672 Both
PDS0603 PARTY SUPPLEMENTAL DATA 2 LENGTH MUST BE 084-672 Both
PDS0604 TRANSACTION SUPPLEMENTAL DATA 1 LENGTH MUST BE Both
084-672 AND MUST BE DIVISIBLE BY MINIMUM OCCURRENCE LENGTH
OF 084.
PDS0605 TRANSACTION SUPPLEMENTAL DATA 2 LENGTH MUST BE Both
084-672 AND MUST BE DIVISIBLE BY MINIMUM OCCURRENCE LENGTH
OF 084.
PDS0627 BILLING EVENT 1 LENGTH MUST BE 54-540 AND MUST BE Both
PDS0628 BILLING EVENT 2 LENGTH MUST BE 54-540 AND MUST BE Both
PDS0734 OTHER SERVICES LENGTH MUST BE 017-102 AND MUST BE Both
2238 PDS0589S2 INVOICE CREATION TIME MUST BE A VALID TIME IN THE Both
FORMAT HHMMSS.
PDS0637 CALL TIME MUST BE A VALID TIME IN THE FORMAT Both
HHMMSS.
2244 PDS0170S1 CUSTOMER SERVICE PHONE NUMBER CANNOT CONTAIN Both
ALL ZEROS OR 000–000–0000 OR (000) 000–0000 OR 000 000 0000.
PDS0170S2 CARD ACCEPTOR PHONE NUMBER CANNOT CONTAIN ALL Both
ZEROS OR 000–000–0000 OR (000) 000–0000 OR 000 000 0000.
2246 THE CORPORATE CARD COMMON DATA REQUIREMENT ADDENDUM Both
MESSAGE MUST BE PRESENT WITH AN ELECTRONIC INVOICE-
TRANSACTION DATA.


2247 THE ELECTRONIC INVOICE-TRANSACTION DATA MUST PRECEDE THE Both
ELECTRONIC INVOICE-PARTY INFORMATION.
2248 ONE OCCURRENCE OF ELECTRONIC INVOICE-PARTY INFORMATION Both
REQUIRED WITH ELECTRONIC INVOICE-TRANSACTION
INFORMATION.
2249 THE TELEPHONY BILLING DETAIL MUST FOLLOW THE TELPEPHONY Both
BILLING SUMMARY.
2250 PDS0501S3 OCCURRENCE INDICATOR MUST 001 FOR USAGE CODE 11 Both
AND INDUSTRY RECORD NUMBER 000.
2254 PDS0501S3 OCCURRENCE INDICATOR MUST BE 002-999 FOR USAGE Both
CODE 11 AND INDUSTRY RECORD NUMBER 001.
2256 PARSED MSG LENGTH NOT EQUAL TO RECORD LENGTH Both
2257 PDS0596 CARD ACCEPTOR TAX ID MUST BE LEFT JUSTIFIED, NON- Both
ZERO AND CONTAIN 9 NUMERIC CHARACTERS
PDS0682S7 TAX AMOUNT 1, TAX ID MUST BE LEFT JUSTIFIED, NON- Both
2258 PDS59354 DESTINATION POSTAL CODE MUST BE EITHER 5 NUMERIC Both
CHARACTERS OR 9 NUMERIC CHARACTERS WITH A HYPHEN
BETWEEN THE 5TH AND 6TH NUMERIC CHARACTER WITH TRAILING
SPACES
PDS0608 DESTINATION POSTAL CODE MUST BE EITHER 5 NUMERIC Both
SPACES
PDS0613 SHIP FROM POSTAL CODE MUST BE EITHER 5 NUMERIC Both
SPACES


2258 PDS0746S4 SHIPPING PARTY POSTAL CODE MUST BE EITHER 5 Both
NUMERIC CHARACTERS OR 9 NUMERIC CHARACTERS WITH A HYPHEN
SPACES
PDS0750S4 DELIVERY PARTY POSTAL CODE MUST BE EITHER 5 Both
NUMERIC CHARACTERS OR 9 NUMERIC CHARACTERS WITH A HYPHEN
SPACES
2259 PDS0170S1 CUSTOMER SERVICE PHONE NUMBER MUST CONTAIN 10 Both
CHARACTERS FOLLOWED BY TRAILING SPACES. THE FIRST THREE
POSITIONS MUST BE NUMERIC.
PDS0170S2 CARD ACCEPTOR PHONE NUMBER MUST CONTAIN 10 Both
CHARACTERS FOLLOWED BY TRAILING SPACES. THE FIRST THREE
POSITIONS MUST BE NUMERIC.
PDS0189S2 PHONE DATA MUST CONTAIN 10 CHARACTERS FOLLOWED Both
BY TRAILING SPACES. THE FIRST THREE POSITIONS MUST BE
NUMERIC.
PDS0552 CUSTOMER SERVICE TOLL FREE (800) NUMBER MUST Both
CONTAIN 10 CHARACTERS FOLLOWED BY TRAILING SPACES. THE
FIRST THREE POSITIONS MUST BE NUMERIC.
PDS0577 PROPERTY PHONE NUMBER MUST CONTAIN 10 CHARACTERS Both
FOLLOWED BY TRAILING SPACES. THE FIRST THREE POSITIONS
MUST BE NUMERIC.
PDS0638S4 CALL TO NUMBER MUST CONTAIN 10 CHARACTERS Both
MUST BE NUMERIC.
PDS0644S4 CALL FROM NUMBER MUST CONTAIN 10 CHARACTERS Both
MUST BE NUMERIC.
2264 FREE FORM DESCRIPTION (P0663) MUST BE PRESENT IN GENERIC Both
DETAIL ADDENDUM MESSAGE (P0501 S1 = 99 and P0501 S2 = 000).
2268 SENDING PROCESSOR ID IN PDS105, INVALID FOR SENDING Both
ENDPOINT.
2285 DE3S1 PROCESSING CODE MUST MATCH THE PROCESSING CODE GCMS
FROM THE PREVIOUS CYCLE.

Error Listing by MTI/Function Code
File Header/1644-697
The following table shows the error numbers and message texts by field and
subfield for File Header (member generated and MasterCard-generated)
1644-697 messages.
MTI/Function: File Header/1644-697

Field/Subfield Number Error Message By…
DE 1 0990 UNPARSEABLE MESSAGE. TOO MANY TAGS TO TAG Both
TABLE.
0993 MISSING SECOND BITMAP. Both
DE 24 0061 DE24 FUNCTION CODE MUST BE NUMERIC. Both
0735 DE24 FUNCTION CODE MUST BE PRESENT IN FILE Both
HEADER MESSAGES.
DE 48 0114 DE48 ADDITIONAL DATA CANNOT BE ALL LOW- Both
0117 INCORRECT PDS ENCODING SCHEME WITHIN DE48 Both
ADDITIONAL DATA. PDS TAG + LENGTH + DATA
MUST FIT ENTIRELY INTO DE48 OR BE MOVED TO
DE62.
0735 DE48 ADDITIONAL DATA MUST BE PRESENT IN FILE Both
HEADER MESSAGES.
0987 DUPLICATE OCCURRENCE OF PDSXXX IN A SINGLE Both
MESSAGE.
0991 UNPARSEABLE MESSAGE. NO PDS DEFINED WITH THIS Both
NUMBER.
0994 NON-NUMERIC PDS ID. Both
0997 NON-NUMERIC LENGTH FIELD. Both
DE 71 0070 DE71 MESSAGE NUMBER MUST BE NUMERIC. Both
0149 DE71 MESSAGE NUMBER MUST BE GREATER THAN THE Both
DE71 MESSAGE NUMBER VALUE IN THE PREVIOUS
MESSAGE.
0502 DE71 MESSAGE NUMBER IN FILE HEADER MUST BE Both
00000001.


DE 71 0735 DE71 MESSAGE NUMBER MUST BE PRESENT IN FILE Both
HEADER MESSAGES
PDS 0026, s1 1120 PDS0026S1 FILE REVERSAL INDICATOR MUST BE EQUAL Both
TO R IF PRESENT.
PDS 0026, s2 1121 PDS0026S2 CENTRAL SITE PROCESSING DATE OF Both
ORIGINAL FILE MUST BE NUMERIC AND A VALID DATE
IN THE FORMAT YYMMDD.
1122 PDS0026S2 CENTRAL SITE PROCESSING DATE OF Both
ORIGINAL FILE INVALID. CANNOT BE GREATER THAN
THE SYSTEM PROCESSING DATE.
PDS 0105 0351 PDS0105 FILE ID MUST BE A FIXED LENGTH OF 025. Both
0362 DUPLICATE PDS0105 FILE ID. Both
0497 IPM FILE HEADER/1644-697 MUST BE FIRST MESSAGE IN Both
A PHYSICAL TRANSMISSION.
0498 IPM FILE HEADER/1644-697 MESSAGE MISSING. MUST Both
FOLLOW A FILE TRAILER/1644-695.
0511 NO DETAILS PRESENT IN THE LOGICAL FILE. ONLY Both
FILE HEADER AND FILE TRAILER PRESENT.
0735 PDS0105 FILE ID MISSING. MUST BE PRESENT IN FILE Both
HEADER MESSAGES.
PDS 0105, s1 0358 INVALID PDS0105S1 FILE TYPE. MUST BE 002. Both
PDS 0105, s2 0359 PDS0105S2 FILE REFERENCE DATE MUST BE A VALID Both
DATE IN THE FORMAT YYMMDD.
0360 PDS0105S2 FILE REFERENCE DATE INVALID. CANNOT Both
BE GREATER THAN THE SYSTEM PROCESSING DATE.
PDS 0105, s3 0355 PDS0105S3 PROCESSOR ID MUST BE NUMERIC. Both
1022 PDS0105S3 PROCESSOR ID INVALID. Both
PDS 0105, s4 0356 PDS0105S4 FILE SEQUENCE NUMBER MUST BE Both
NUMERIC.
PDS 0110 0364 PDS0110 TRANSMISSION ID MUST BE A FIXED LENGTH Both
OF 025.
PDS 0110, s1 0371 PDS0110S1 TRANSMISSION TYPE INVALID. MUST BE Both
002.


PDS 0110, s2 0372 PDS0110S2 TRANSMISSION REFERENCE DATE INVALID. Both
MUST BE A VALID DATE IN THE FORMAT YYMMDD.
0373 PDS0110S2 TRANSMISSION REFERENCE DATE INVALID. Both
CANNOT BE GREATER THAN THE SYSTEM PROCESSING
DATE.
PDS 0110, s3 0361 PDS0110S3 PROCESSOR ID INVALID. MUST CONTAIN A Both
VALID MEMBER ID OR PROCESSOR ID.
PDS 0110, s4 0369 PDS0110S4 TRANSMISSION SEQUENCE NUMBER MUST Both
BE NUMERIC.
PDS 0122 0515 PDS0122 PROCESSING MODE MUST BE P FOR GCMS
PRODUCTION ENVIRONMENT; P OR T FOR TEST
ENVIRONMENT.
PDS 1000 2156 PDS 10XX MEMBER-TO-MEMBER PROPRIETARY DATA Both
2159 MEMBER-TO-MEMBER PROPRIETARY DATA CANNOT Both
EXCEED 999 BYTES.

First Presentments/1240-200
subfield for First Presentments/1240-200 messages.
MTI/Function Code: First Presentment/1240-200

DE 2 0011 DE2 PRIMARY ACCOUNT NUMBER (PAN) ACCOUNT Both
RANGE INVALID.
0405 INVALID TRANSACTION FOR THE COUNTRY/REGION. Both
0735 DE2 PRIMARY ACCOUNT NUMBER (PAN) MUST BE Both
PRESENT IN FIRST PRESENTMENT MESSAGES.
1106 PAYMENT TRANSACTION NOT ALLOWED. GCMS
2225 BRAND PRODUCT <DERIVED FROM DE 2> INVALID Both
FOR BUSINESS SERVICE ARRANGEMENT <BSID &
TYPE> AND ACCEPTANCE BRAND ID CODE <AB>
FOR BUSINESS SERVICE ARRANGEMENT <BSID&TYPE>
AND ACCEPTANCE BRAND ID CODE <AB> FOR
DE 3 0012 DE3 PROCESSING CODE MUST BE NUMERIC. Both
0735 DE3 PROCESSING CODE MUST BE PRESENT IN FIRST Both
PRESENTMENT MESSAGES.
2220 DE3 PROCESSING CODE INVALID FOR BUSINESS Both
SERVICE ARRANGEMENT <BSID & TYPE> AND
DE 3, s1 0013 DE3S1 CARDHOLDER TRANSACTION TYPE INVALID. Both
MUST BE 00, 01, 12, 17, 18, 20, 28, OR 50.
0016 DE3S1 CARDHOLDER TRANSACTION TYPE INVALID Both
FOR ATM CASH WITHDRAWAL CARD ACCEPTOR
BUSINESS CODE (MCC) 6011.
FOR CASH ADVANCE CARD ACCEPTOR BUSINESS
CODE (MCC) 6010.
FOR UNIQUE TRANSACTION CARD ACCEPTOR
BUSINESS CODE (MCC). MUST BE EQUAL TO 18.
0523 ACQUIRER NOT CERTIFIED BY MASTERCARD TO Both
PROCESS ATM CASH WITHDRAWAL TRANSACTIONS.


DE 3, s1 1103 DE3S1 CARDHOLDER TRANSACTION TYPE INVALID Both
FOR PAYMENT TRANSACTION CARD ACCEPTOR
BUSINESS CODE.
DE 3, s2 0014 DE3S2 CARDHOLDER FROM - ACCOUNT MUST BE 00. Both
DE 3, s3 0015 DE3S3 CARDHOLDER TO - ACCOUNT MUST BE 00. Both
DE 4 0020 DE4 AMOUNT, TRANSACTION MUST BE NUMERIC. Both
0023 DE4 AMOUNT, TRANSACTION MUST BE PRESENT Both
WHEN DE49 CURRENCY CODE, TRANSACTION IS
PROVIDED.
0024 PDS0148 CURRENCY EXPONENTS MISSING. MUST BE Both
PRESENT IN A MESSAGE WHEN DE4 AMOUNT,
TRANSACTION IS PROVIDED.
0735 DE4 AMOUNT, TRANSACTION MUST BE PRESENT IN Both
1174 TRANSACTION AMOUNT EXCEEDS RESTRICTED GCMS
THRESHOLD.
2202 DE4 AMOUNT, TRANSACTION EXCEEDS MASTERCARD GCMS
DEFINED ACQUIRER LIMIT
2203 DE4 AMOUNT, TRANSACTION EXCEEDS MASTERCARD GCMS
DEFINED ISSUER LIMIT
DE 5 0025 DE5 AMOUNT, RECONCILIATION MUST BE NUMERIC. Both
0027 DE5 AMOUNT, RECONCILIATION MISSING. MUST BE Both
PRESENT IN A MESSAGE WHEN DE50 CURRENCY
CODE, RECONCILIATION IS PROVIDED.
0028 PDS0148 CURRENCY EXPONENTS MUST BE PRESENT Both
IN A MESSAGE WHEN DE5 AMOUNT,
RECONCILIATION IS PROVIDED.
PRESENT IN AN ATM CASH WITHDRAWAL MESSAGE.
DE 6 0034 DE6 AMOUNT, CARDHOLDER BILLING MUST BE Both
NUMERIC.
0036 DE6 AMOUNT, CARDHOLDER BILLING MUST BE Both
CODE, CARDHOLDER BILLING IS PROVIDED.


DE 6 0037 PDS0148 CURRENCY EXPONENTS MISSING. MUST BE Both
CARDHOLDER BILLING IS PROVIDED.
DE 12, s1 0039 DE12S1 DATE, LOCAL TRANSACTION IN DE12 DATE Both
AND TIME, LOCAL TRANSACTION INVALID. DATE
MUST BE IN THE FORMAT 000000, YYMMDD, OR
YYMM00.
0043 DE12S1 DATE, LOCAL TRANSACTION CANNOT BE Both
GREATER THAN THE DATE IN PDS0105S2 FILE
REFERENCE DATE.
1017 DE12S1 DATE, LOCAL TRANSACTION IN DE12 DATE Both
AND TIME, LOCAL TRANSACTION INVALID. MUST BE
VALID YYMMDD IN FIRST PRESENTMENT MESSAGES IF
TIMELINESS EDITS ARE PERFORMED FOR THE
RELATED INTERCHANGE PROGRAM.
DE 12, s2 0040 DE12S2 TIME, LOCAL TRANSACTION HOURS MUST BE Both
IN THE RANGE 00-23.
0042 DE12S2 TIME, LOCAL TRANSACTION INVALID. Both
MINUTES AND SECONDS MUST BE IN RANGE 00-59.
DE 14 0045 DE14 EXPIRATION DATE MUST BE NUMERIC AND Both
HAVE A VALID DATE IN THE FORMAT YYMM.
DE 22, s1 0047 DE22S1 TERMINAL DATA:CARD DATA INPUT Both
CAPABILITY INVALID. MUST BE 0, 1, 2, 4, 5, 6, A, B, C,
D, E, M OR V.
0053 DE22S1 CARD DATA INPUT CAPABILITY INVALID. Both
MUST BE 0, 1, 2, 4, 6, A, B, OR V.
0053 DE22S1 CARD DATA INPUT CAPABILITY INVALID. Both
MUST BE 5, C, D, E, OR M.
DE 22, s2 0048 DE22S2 CARDHOLDER AUTHENTICATION CAPABILITY Both
INVALID. MUST BE 0, 1, 2, 5, 6 OR 9.
DE 22, s3 0049 DE22S3 CARD CAPTURE CAPABILITY INVALID. MUST Both
BE 0, 1, OR 9.
DE 22, s4 0050 DE22S4 TERMINAL OPERATING ENVIRONMENT Both
INVALID. MUST BE 0, 1, 2, 3, 4, 5, 6 OR 9.
0053 DE22S4 TERMINAL OPERATING ENVIRONMENT Both
INVALID. MUST BE 1 OR 3.


DE 22, s5 0051 DE22S5 CARDHOLDER PRESENT DATA INVALID. Both
MUST BE 0, 1, 2, 3, 4, 5, 6 OR 9.
0053 DE22S5 CARDHOLDER PRESENT DATA INVALID. Both
MUST BE ZERO.
DE 22, s6 0052 DE22S6 CARD PRESENT DATA INVALID. MUST BE 0, 1, Both
OR 9.
0053 DE22S6 CARD PRESENT DATA INVALID. MUST BE 1. Both
DE 22, s7 0053 DE22S7 CARD DATA INPUT MODE INVALID. MUST BE Both
0, 1, 2, 6, A, B, S, OR T.
0053 DE22S7 CARD DATA INPUT MODE INVALID. MUST BE Both
0, 1, 2, 6, A, B, C, F, S, OR T.
0053 DE22S7 CARD DATA INPUT MODE INVALID. MUST BE Both
0, 1, 2, 6, A, B, C, F, M, S, OR T.
2197 WHEN DE055 INTEGRATED CIRCUIT CARD (ICC) Both
SYSTEM RELATED DATA IS PRESENT DE022 MUST BE
PRESENT AND DE022S7 CARD DATA INPUT MODE
MUST CONTAIN AN F , C, M, S, OR T.
DE 22, s8 0054 DE22S8 CARDHOLDER AUTHENTICATION METHOD Both
INVALID. MUST BE 0, 1, 2, 5, 6, 9, OR S.
DE 22, s9 0055 DE22S9 CADHOLDER AUTHENTICATION ENTITY Both
DE 22, s10 0053 DE22S10 CARD DATA OUTPUT CAPABILITY INVALID. Both
MUST BE 3.
0053 DE22S10 CARD DATA OUTPUT CAPABILITY INVALID. Both
MUST BE 0, 1, 2, OR S.
0056 DE22S10 CARD DATA OUTPUT CAPABILITY INVALID. Both
MUST BE 0, 1, 2, 3, OR S.
DE 22, s11 0057 DE22S11 TERMINAL DATA OUTPUT CAPABILITY Both
INVALID. MUST BE 0, 1, 2, 3, OR 4.
DE 22, s12 0058 DE22S12 PIN CAPTURE CAPABILITY INVALID. MUST BE Both
0, 1, 2, 3, 4, 5, 6, 7, 8, 9, A, B, OR C.
DE 23 0059 DE23 CARD SEQUENCE NUMBER MUST BE NUMERIC. Both
0437 DE23 CARD SEQUENCE NUMBER CONTAINS A VALUE Both
IN THE RANGE OF 000-099.


DE 24 0735 DE24 FUNCTION CODE MUST BE PRESENT IN FIRST Both
DE 25 0064 DE25 MESSAGE REASON CODE MUST BE NUMERIC. Both
0735 DE25 MESSAGE REASON CODE MUST BE PRESENT IN Both
2219 DE25 MESSAGE REASON CODE INVALID FOR Both
BUSINESS SERVICE ARRANGEMENT <BSID&TYPE>
AND ACCEPTANCE BRAND ID CODE <AB>.
DE 26 0531 DE26 CARD ACCEPTOR BUSINESS CODE (MCC) Both
INVALID OR OBSOLETE.
0735 DE26 CARD ACCEPTOR BUSINESS CODE (MCC) MUST Both
BE PRESENT IN FIRST PRESENTMENT MESSAGES.
0986 DE26 CARD ACCEPTOR BUSINESS CODE (MCC) Both
INVALID. MUST BE 6011 AUTOMATED CASH
DISBURSEMENT FOR DE3 SUBFIELD 1, PROCESSING
CODE 01.
INVALID. MUST BE DESIGNATED AS UNIQUE FOR
DE3 SUBFIELD 1, PROCESSING CODE 18.
INVALID. MUST BE 6012 MERCHANDISE & SERVICES
FOR DE3 SUBFIELD 1, PROCESSING CODE 17 OR 50.
INVALID FOR PAYMENT TRANSACTION INTERCHANGE
RATE PROGRAM.
INVALID. MUST BE 6010 MANUAL CASH
CODE 12.
INVALID FOR BUSINESS SERVICE ARRANGEMENT
<BSID &TYPE> AND ACCEPTANCE BRAND ID CODE
<AB>.
<BSID&TYPE> AND ACCEPTANCE BRAND ID CODE
<AB> FOR INTERCHANGE PROGRAM.


DE 30 0077 PDS0149 CURRENCY CODES, AMOUNTS, ORIGINAL Both
MUST BE PRESENT IN A MESSAGE WHEN DE30
AMOUNTS, ORIGINAL IS PROVIDED.
IN A MESSAGE WHEN DE30 AMOUNTS, ORIGINAL IS
PROVIDED.
0735 DE30 AMOUNTS, ORIGINAL MUST BE PRESENT IN Both
FIRST PRESENTMENT MESSAGES. (Intra-European
transactions only)
DE 30, s2 0076 DE30S2 ORIGINAL AMOUNT, RECONCILIATION MUST Both
BE ZERO-FILLED.
DE 31 0079 DE31 ACQUIRER REFERENCE DATA CANNOT BE ALL Both
0289 DE31 ACQUIRER REFERENCE DATA LENGTH MUST BE Both
01-99.
0735 DE31 ACQUIRER REFERENCE DATA MUST BE PRESENT Both
IN FIRST PRESENTMENT MESSAGES.
DE 31, s1 0080 DE31S1 INTERCHANGE RATE DESIGNATOR MUST BE Both
NUMERIC.
DE 31, s2 0081 DE31S2 ACQUIRER’S BIN MUST BE NUMERIC. Both
DE 31, s3 0086 DE31S3 JULIAN PROCESSING DATE YDDD OF DE31 Both
ACQUIRER REFERENCE DATA MUST BE A VALID DATE
IN THE FORMAT YDDD.
DE 31, s4 0083 DE31S4 ACQUIRER’S SEQUENCE NUMBER MUST BE Both
NUMERIC.
DE 31, s5 0085 DE31S5 CHECK DIGIT MUST BE NUMERIC. Both


DE 32 0089 DE32 ACQUIRING INSTITUTION ID CODE MUST BE Both
NUMERIC.
0090 DE32 ACQUIRING INSTITUTION ID CODE LENGTH Both
FIELD MUST BE A VALUE OF 001-011.
2196 DE32 AQUIRING INSTITUTION IDENTIFICATION CODE Both
MUST BE NUMERIC AND CANNOT BE ALL ZEROS.
DE 33 0735 DE33 FORWARDING INSTITUTION ID CODE MUST BE Both
0790 INVALID DE33 FORWARDING INSTITUTION ID CODE Both
FOR FIRST PRESENTMENT MESSAGES.
0808 DE33 FORWARDING INSTITUTION ID CODE MUST BE Both
NUMERIC.
2180 DE33 FORWARDING INSTITUTION ID CODE LENGTH Both
MUST BE 006-011.
DE 37 0091 DE37 RETRIEVAL REFERENCE NUMBER CANNOT BE Both
2208 DE37 RETRIEVAL REFERENCE NUMBER CANNOT BE Both
ALL ZEROS OR ALL SPACES
DE 38 0093 DE38 APPROVAL CODE CANNOT BE ALL LOW-VALUES Both
OR ALL HIGH-VALUES.
0094 DE38 APPROVAL CODE CONTAINS EMBEDDED Both
SPACES.
0095 DE38 APPROVAL CODE MUST BE LEFT JUSTIFIED. Both
2198 DE38 APPROVAL CODE CANNOT BE PRESENT WHEN Both
DE022S7 CARD DATA INPUT MODE CONTAINS AN F.
DE 40 0053 DE40 EXTENDED SERVICE CODE INVALID. MUST BE Both
200, 201, 202, 203, 205, 206, 207, 220, 221, 222, 223, 225,
226, 227, 600, 601, 602, 603, 605, 606, 607, 620, 621, 622,
623, 625, 626 OR 627.
0053 DE40 EXTENDED SERVICE CODE INVALID. MUST BE Both
100, 101, 102, 103, 105, 106, 107, 120, 121, 122, 123, 125,
126, 127, 500, 501, 502, 503, 505, 506, 507, 520, 521, 522,
523, 525, 526, 527, 700, 701, 702, 703, 705, 706, 707, 720,
721, 722, 723, 725, 726, 727.
2183 DE40 EXTENDED SERVICE CODE MUST BE NUMERIC. Both


DE 41 0096 CARD ACCEPTOR TERMINAL ID CANNOT BE ALL LOW- Both
0097 CARD ACCEPTOR TERMINAL ID MUST BE LEFT Both
0735 DE41 CARD ACCEPTOR TERMINAL ID MUST BE Both
PRESENT.
2182 DE41 CARD ACCEPTOR TERMINAL ID MUST BE LEFT Both
JUSTIFIED AND CANNOT CONTAIN ALL SPACES OR
ALL ZEROS.
DE 42 0098 DE42 CARD ACCEPTOR ID CANNOT BE ALL LOW- Both
0099 DE42 CARD ACCEPTOR ID MUST BE LEFT JUSTIFIED Both
2182 DE42 CARD ACCEPTOR ID CODE MUST BE LEFT Both
ALL ZEROS.
DE 43 0100 DE43 CARD ACCEPTOR NAME/LOCATION CANNOT BE Both
0101 DE43 CARD ACCEPTOR NAME/LOCATION MUST BE 20- Both
99.
0107 WITHIN DE43 CARD ACCEPTOR NAME/LOCATION, 3 Both
BACKSLASH CHARACTERS ARE REQUIRED TO DELIMIT
NAME\STREET ADDRESS\CITY\.
0992 UNPARSEABLE MESSAGE. NO \ AT END OF SUBFIELD. Both
DE 43, s1 0102 DE43S1 CARD ACCEPTOR NAME CANNOT BE ALL Both
0103 DE43S1 CARD ACCEPTOR NAME LENGTH MUST BE 1- Both
22.
0108 DE43S1 CARD ACCEPTOR NAME MUST BE LEFT Both
0735 DE43S1 CARD ACCEPTOR NAME MUST BE PRESENT IN Both
2229 DE43S1 CARD ACCEPTOR NAME INVALID. MUST Both
CONTAIN ABBREVIATED AIRLINE NAME FOLLOWED
BY DELIMITER, OR SPACES AND DELIMITER.


DE 43, s2 0625 DE43S2 CARD ACCEPTOR STREET ADDRESS Both
REQUIRED.
2182 DE 43S2 CARD ACCEPTOR STREET ADDRESS MUST BE Both
LEFT JUSTIFIED AND CANNOT CONTAIN ALL SPACES
OR ALL ZEROS.
2184 DE43S2 CARD ACCEPTOR STREET ADDRESS CANNOT Both
BE ALL LOW-VALUES OR ALL HIGH-VALUES.
DE 43, s3 0104 DE43S3 CARD ACCEPTOR CITY CANNOT BE ALL LOW- Both
0105 DE43S3 CARD ACCEPTOR CITY LENGTH CANNOT Both
EXCEED 13.
2182 DE43S3 CARD ACCEPTOR CITY MUST BE LEFT Both
ALL ZEROS.
DE 43, s4 0109 DE43S4 CARD ACCEPTOR POSTAL (ZIP) CODE NOT Both
LEFT JUSTIFIED.
0586 DE43S4 CARD ACCEPTOR POSTAL (ZIP) CODE Both
REQUIRED.
2184 DE43S4 CARD ACCEPTOR POSTAL (ZIP) CODE Both
CANNOT CONTAIN ALL LOW-VALUES OR ALL HIGH-
VALUES.
DE 43, s5 0623 DE43S5 CARD ACCEPTOR STATE/PROVINCE/REGION Both
CODE REQUIRED.
2167 DE43S5 CARD ACCEPTOR STATE/PROVINCE/REGION Both
CODE REQUIRED.
2184 DE43S5 CARD ACCEPTOR STATE, PROVINCE, OR Both
REGION CODE CANNOT BE ALL LOW-VALUES OR ALL
HIGH-VALUES.
DE 43, s6 0112 DE43S6 CARD ACCEPTOR COUNTRY CODE MUST Both
CONTAIN A VALID ISO STANDARD COUNTRY CODE.
0589 DE43S6 CARD ACCEPTOR COUNTRY CODE MUST BE Both
COMPATIBLE WITH DE43S5 STATE/PROVINCE/REGION
CODE.


DE62.
0735 DE48 ADDITIONAL DATA MUST BE PRESENT IN FIRST Both
DE 49 0023 DE4 AMOUNT, TRANSACTION MUST BE PRESENT Both
PROVIDED.
0119 DE49 CURRENCY CODE, TRANSACTION MUST Both
CONTAIN A VALID ISO STANDARD NUMERIC
CURRENCY CODE.
0120 DE49 CURRENCY CODE, TRANSACTION MUST BE Both
PRESENT WHEN DE4 AMOUNT, TRANSACTION IS
PROVIDED.
0122 PDS0148S1 CURRENCY CODE OCCURRENCE FOR DE49 Both
CURRENCY CODE, TRANSACTION, MUST BE
PROVIDED.
DE 50 0123 DE50 CURRENCY CODE, RECONCILIATION MUST BE Both
NUMERIC.
0124 DE50 CURRENCY CODE MISSING. MUST BE PRESENT Both
IN A MESSAGE WHEN DE5 AMOUNT, RECONCILIATION
IS PROVIDED.
CURRENCY CODE, RECONCILIATION MUST BE
PROVIDED.
0129 DE50 CURRENCY CODE, RECONCILIATION MUST Both
CURRENCY CODE.


DE 51 0133 DE51 CURRENCY CODE, CARDHOLDER BILLING MUST Both
BE NUMERIC.
0134 DE51 CURRENCY CODE, CARDHOLDER BILLING MUST Both
BE PRESENT IN A MESSAGE WHEN DE6 AMOUNT,
CURRENCY CODE, CARDHOLDER BILLING MUST BE
PROVIDED.
DE 55 1057 DE 55 INTEGRATED CIRCUIT CARD (ICC) SYSTEM- Both
RELATED DATA LENGTH MUST BE 1-255.
2184 DE55 INTEGRATED CIRCUIT CARD (ICC) SYSTEM Both
RELATED DATA CANNOT BE ALL LOW-VALUES, ALL
HIGH-VALUES
2200 DE55 INTEGRATED CIRCUIT CARD (ICC) SYSTEM GCMS
RELATED DATA CANNOT BE ALL ZEROS OR ALL
SPACES.
DE 62 0165 DE62 ADDITIONAL DATA 2 CANNOT BE ALL LOW- Both
0168 INCORRECT PDS ENCODING SCHEME WITH DE62 Both
ADDITIONAL DATA 2.
0169 DE62 ADDITIONAL DATA 2 CAN BE PRESENT ONLY IF Both
DE48 ADDITIONAL DATA IS PRESENT.
DE 63 0137 DE63 TRANSACTION LIFE CYCLE ID CANNOT BE ALL Both
0138 DE63 TRANSACTION LIFE CYCLE ID LENGTH FIELD Both
MUST BE 016-999.
1100 DE63 TRANSACTION LIFE CYCLE ID MUST BE PRESENT Both
FOR US ACQUIRED INCENTIVE INTERCHANGE
PROGRAM.
DE 63, s1 0139 DE63S1 LIFE CYCLE SUPPORT INDICATOR MUST BE A Both
SPACE.
DE 63, s2 0141 DE63S2 TRACE ID POSITIONS 10-13 MUST BE A VALID Both
DATE IN THE FORMAT MMDD.
0142 THE FIRST NINE POSITIONS OF DE63S2 TRACE ID Both
CANNOT CONTAIN EMBEDDED SPACES.


0149 DE71 MESSAGE NUMBER MUST BE GREATER THAN Both
THE DE 71 VALUE FROM THE PREVIOUS MESSAGE.
0735 DE71 MESSAGE NUMBER MUST BE PRESENT IN FIRST Both
DE 93 0155 DE93 TRANSACTION DESTINATION INSTITUTION ID Both
CODE MUST BE NUMERIC.
0157 DE93 TRANSACTION DESTINATION INSTITUTION ID Both
CODE INVALID.
1154 DE93 TRANSACTION DESTINATION INSTITUTION ID GCMS
CODE MUST BE AN ATM ISSUER IF THE TRANSACTION
IS AN ATM CASH WITHDRAWAL.
This error message applies to ATM Cash Disbursement
only.

CODE CANNOT BE FLAGGED FOR INTERNAL USE
ONLY.
CODE IS DESIGNATED AS AN ACQUIRER ONLY BY
MASTERCARD.
CODE MISSING. MUST BE PRESENT IN FIRST AND
SECOND PRESENTMENT.
only.

CODE LENGTH MUST BE 006-011.
DE 94 0044 DE94 TRANSACTION ORIGINATOR INSTITUTION ID Both
CODE INVALID FOR SUPERMARKET INTERCHANGE
PROGRAM.
0159 DE94 TRANSACTION ORIGINATOR INSTITUTION ID Both
CODE INVALID.
CODE/ACQUIRER BIN (DE31s2) COMBINATION
INVALID.


CODE IS DESIGNATED AS AN ISSUER ONLY BY
MASTERCARD.
CODE INVALID FOR SERVICE INDUSTRY
CODE INVALID FOR INTERNATIONAL ELECTRONIC
CODE INVALID FOR WAREHOUSE INTERCHANGE
PROGRAM.
CODE MUST BE PRESENT IN FIRST PRESENTMENT
MESSAGES.
0171 DE123 ADDITIONAL DATA 3 LENGTH MUST BE 008- Both
999.
ADDITIONAL DATA 3. PDS TAG + LENGTH + DATA
DE124.
0174 DE123 ADDITIONAL DATA 3 CAN BE PRESENT ONLY Both
IF DE48 ADDITIONAL DATA AND DE62 ADDITIONAL
DATA 2 ARE PRESENT.
DE 124 0179 DE124 ADDITIONAL DATA 4 CAN BE PRESENT ONLY Both
IF DE48 ADDITIONAL DATA, DE62 ADDITIONAL DATA
2, AND DE123 ADDITIONAL DATA 3 ARE PRESENT.
2151 DE 124 CANNOT BE ALL LOW-VALUES OR ALL HIGH- Both
VALUES.
2152 DE124 ADDITIONAL DATA 4 LENGTH MUST BE 008– Both
999.


DE 124 2154 INCORRECT PDS ENCODING SCHEME WITHIN DE124 Both
DE125.
999.
MUST FIT ENTIRELY INTO DE125 OR IT CANNOT BE
ADDED.
2, DE123 ADDITIONAL DATA 3, AND DE124
PDS 0022 1093 PDS0022 RECURRING PAYMENT INDICATOR INVALID. Both
MUST BE 4.
PDS 0023 0022 PDS0023 TERMINAL TYPE/PDS0158S4 INTERCHANGE Both
RATE DESIGNATOR CONFLICT.
0181 PDS0023 TERMINAL TYPE CANNOT BE ALL LOW- Both
0182 PDS0023 TERMINAL TYPE MUST BE A FIXED LENGTH Both
OF 003.
0184 PDS0023 TERMINAL TYPE MUST CONTAIN A VALID Both
VALUE OF ATM, CT1, CT2, CT3, CT4, CT6, CT7, MAN,
NA_, OR POI.
0553 GAMING NOT ALLOWED. GCMS
0554 GAMING LOSS EXCEEDED. GCMS
0555 GAMING WIN EXCEEDED. GCMS
0596 PDS0023 TERMINAL TYPE/PDS0158S4 INTERCHANGE Both


PDS 0023 1092 PDS0023 TERMINAL TYPE MISSING. MUST BE PRESENT Both
IN NON-REVERSAL FIRST PRESENTMENT, FIRST
CHARGEBACK (FULL), FIRST CHARGEBACK (PARTIAL),
SECOND PRESENTMENT (FULL), SECOND
PRESENTMENT (PARTIAL), ARBITRATION
CHARGEBACK (FULL), OR ARBITRATION
PDS 0025 0187 PDS0025 MESSAGE REVERSAL INDICATOR LENGTH Both
PDS 0025, s1 0185 PDS0025S1 MESSAGE REVERSAL INDICATOR MUST BE Both
EQUAL TO R OR A SPACE IF PRESENT.
ORIGINAL MESSAGE MUST BE NUMERIC AND A VALID
ORIGINAL MESSAGE INVALID. CANNOT BE GREATER
ORIGINAL MESSAGE MUST BE PRESENT WHEN
MESSAGE REVERSAL INDICATOR IS PRESENT IN FIRST
PRESENTMENT MESSAGE.
PDS 0043 0069 PDS0043 PROGRAM REGISTRATION ID IS REQUIRED Both
AND MUST CONTAIN A VALID VALUE.
0194 PDS0043 PROGRAM REGISTRATION ID MUST BE A Both
2208 PDS0043 PROGRAM REGISTRATION ID CANNOT BE Both
PDS 0052, s3 0008 UCAF COLLECTION INDICATOR MUST BE 1. Both
0019 UCAF COLLECTION INDICATOR MUST BE 2. Both
PDS 0146 0381 PDS0146 AMOUNTS, TRANSACTION FEE LENGTH MUST Both
BE 028-336 AND MUST BE DIVISIBLE BY MINIMUM
OCCURRENCE LENGTH OF 28.
1023 PDS0146 AMOUNTS, TRANSACTION FEE MUST BE Both
PRESENT.


PDS 0146, s1 0386 PDS0146S1 FEE TYPE CODE MUST BE 00-99. Both
On Production Reports, the field occurrence number with
the data in error will replace the “XX”.
PDS 0146, s2 0387 PDS0146S2 FEE PROCESSING CODE MUST BE 00, 19, Both
OR 29. OCCURRENCE INDICATOR <XX>.
PDS 0146, s3 1102 PDS0146S3 FEE SETTLEMENT INDICATOR MUST BE 00 Both

OR 01.
PDS 0146, s4 0384 PDS0146S4 CURRENCY CODE, FEE NOT NUMERIC. Both
OCCURRENCE <XX>.
1059 PDS0146S4 CURRENCY CODE, FEE MUST CONTAIN A Both

VALID NUMERIC ISO-STANDARD CURRENCY CODE.
OCCURRENCE <XX>.
PDS 0146, s5 0385 PDS0146S5 AMOUNT, FEE NOT NUMERIC. Both

OCCURRENCE <XX>.
0476 PDS0146S5 AMOUNT, FEE INVALID. MUST BE GCMS

NUMERIC AND CANNOT BE GREATER THAN DE4
AMOUNT, TRANSACTION.
PDS 0148 0393 PDS0148 CURRENCY EXPONENTS CANNOT BE ALL Both
0394 PDS0148 CURRENCY EXPONENTS LENGTH MUST BE Both
04-60 AND MUST BE DIVISIBLE BY MINIMUM


PDS 0148, s1 0395 PDS0148S1 CURRENCY CODE MUST CONTAIN A VALID Both
NUMERIC ISO-STANDARD CURRENCY CODE.
OCCURRENCE <XX>.
PDS 0148, s2 0396 PDS0148S2 CURRENCY EXPONENT MUST BE VALID Both

FOR THE CORRESPONDING CURRENCY CODE IN
SUBFIELD 1. OCCURRENCE <XX>.
PDS 0149 0398 PDS0149 CURRENCY CODE, AMOUNTS, ORIGINAL Both

MUST BE NUMERIC.
0399 PDS0149 CURRENCY CODE, AMOUNTS, ORIGINAL Both
LENGTH MUST BE A FIXED LENGTH OF 006.
0402 PDS0149 CURRENCY CODES, AMOUNTS, ORIGINAL IS Both
PRESENT BUT PDS0148 CURRENCY EXPONENTS IS
NOT PRESENT.
PRESENT BUT DE30 AMOUNT, ORIGINAL IS NOT
PRESENT.
PDS 0149, s1 0400 PDS0149S1 CURRENCY CODE, ORIGINAL Both
TRANSACTION AMOUNT MUST CONTAIN A VALID ISO
0403 PDS0148 CURRENCY EXPONENT OCCURRENCE FOR Both
PDS0149S1 CURRENCY CODE, ORIGINAL
TRANSACTION AMOUNT MISSING. MUST BE
PROVIDED.
RECONCILIATION AMOUNT MUST BE ALL ZEROS.
PDS 0158 0407 PDS0158 BUSINESS ACTIVITY CANNOT BE ALL LOW- Both
0408 PDS0158 BUSINESS ACTIVITY LENGTH MUST BE 003- Both
020.
0735 PDS0158 BUSINESS ACTIVITY MUST BE PRESENT IN Both


PDS 0158, s1 2007 ACCEPTANCE BRAND ID CODE SUBMITTED IS NOT Both
VALID FOR THE MEMBER PAIR.
PDS 0158, s2 2009 NO BUSINESS SERVICE ARRANGEMENT EXISTS FOR Both
THE MEMBER PAIR.
2010 BUSINESS SERVICE ID CODE SUBMITTED IS NOT Both
THE MEMBER PAIR.
2217 PDS0158S3 BUSINESS SERVICE ID CODE MUST BE Both
PRESENT AND VALID WHEN PDS0158s2 BUSINESS
SERVICE ARRANGEMENT TYPE CODE IS PRESENT.
2218 PDS0158S2 BUSINESS SERVICE ARRANGEMENT TYPE Both
CODE MUST BE PRESENT AND VALID WHEN
PDS0158s3 BUSINESS SERVICE ID CODE IS PRESENT.
PDS 0158, s4 0521 ASSOCIATED FINANCIAL DETAIL ADDENDUM/1644 Both
REJECTED.
0598 PDS0158S4 INTERCHANGE RATE DESIGNATOR Both
INVALID FOR CORPORATE PRODUCT.
0631 PDS0158S4 INTERCHANGE RATE DESIGNATOR AND Both
PROCESSING CODE/REVERSAL INDICATOR
COMBINATION INVALID FOR BUSINESS SERVICE
ARRANGEMENT <BUSINESS SERVICE ID & TYPE> AND
INVALID FOR SPECIFIED INTERCHANGE PROGRAM.
INVALID FOR T&E CARD ACCEPTOR BUSINESS CODE.
0670 TIMELINESS ERROR. Both
INVALID FOR WORLD MASTERCARD INTERCHANGE
RATE PROGRAM.
0733 TIMELINESS ERROR (AIRLINE). Both


PDS 0158, s4 0769 PDS0158S4 INTERCHANGE RATE DESIGNATOR Both
INVALID FOR FLEET TRANSACTION AT FUEL
LOCATION.
1073 PASSENGER TRANSPORT DETAIL-GENERAL TICKET Both
INFORMATION ADDENDUM REQUIRED FOR
1074 PASSENGER TRANSPORT DETAIL -TRIP LEG DATA Both
ADDENDUM REQUIRED FOR INTERCHANGE
PROGRAM.
1075 VEHICLE RENTAL DETAIL ADDENDUM REQUIRED FOR Both
1076 LODGING DETAIL ADDENDUM REQUIRED FOR Both
1077 CORPORATE CARD COMMON DATA REQUIRED FOR Both
INTERCHANGE RATE PROGRAM.
1078 CORPORATE DETAIL-CORPORATE FLEET Both
TRANSACTION INFORMATION ADDENDUM REQUIRED
FOR INTERCHANGE PROGRAM.
1079 CORPORATE LINE ITEM DETAIL REQUIRED FOR Both
MISSING FOR BUSINESS SERVICE ARRANGEMENT
<BSID & TYPE> AND ACCEPTANCE BRAND ID CODE
<AB>
PDS 0165 0412 PDS0165 SETTLEMENT INDICATOR CANNOT BE ALL Both
0735 PDS0165 SETTLEMENT INDICATOR MUST BE PRESENT Both
2180 PDS0165 SETTLEMENT INDICATOR LENGTH MUST BE Both
001-030.
PDS 0165, s1 0414 PDS0165S1 SETTLEMENT INDICATOR MUST BE M, B OR Both
C.
0416 NO BILATERAL SETTLEMENT AGREEMENT ON FILE Both
FOR <DE93> AND <DE94>.
On Production Reports, the Destination & Originator
Member ID will replace “<DE93>” and “<DE94>”
respectively.


PDS 0165, s1 1066 DE3 PROCESSING CODE AND PDS0165S1 SETTLEMENT Both
INDICATOR COMBINATION INVALID.
PDS 0170 0378 PDS0170 CARD ACCEPTOR INQUIRY INFORMATION Both
0433 PDS0170 CARD ACCEPTOR INQUIRY INFORMATION Both
2208 PDS0170 MERCHANT INQUIRY INFORMATION Both
CANNOT BE ZEROS OR ALL SPACES.
PDS 0170, s1 2244 PDS0170S1 CUSTOMER SERVICE PHONE NUMBER Both
CANNOT CONTAIN ALL ZEROS OR 000–000–0000 OR
(000) 000–0000 OR 000 000 0000.
2259 PDS0170S1 CUSTOMER SERVICE PHONE NUMBER Both
MUST CONTAIN 10 CHARACTERS FOLLOWED BY
TRAILING SPACES. THE FIRST THREE POSITIONS
MUST BE NUMERIC.
PDS 0170, s2 2244 PDS0170S2 CARD ACCEPTOR PHONE NUMBER Both
(000) 000–0000 OR 000 000 0000.
2259 PDS0170S2 CARD ACCEPTOR PHONE NUMBER MUST Both
CONTAIN 10 CHARACTERS FOLLOWED BY TRAILING
SPACES. THE FIRST THREE POSITIONS MUST BE
NUMERIC.
PDS 0170, s3 2228 PDS0170S3 MERCHANT INQUIRY INFORMATION Both
ADDITIONAL INFORMATION CANNOT CONTAIN ALL
ZEROS.
PDS 0171 0419 PDS0171 ALTERNATE CARD ACCEPTOR DESCRIPTION Both
0420 PDS0171 ALTERNATE CARD ACCEPTOR DESCRIPTION Both
PDS 0171, s1 0421 PDS0171S1 CHARACTER SET INDICATOR INVALID. Both
MUST BE ARA, CHS, CHT, CYR, GRK, HEB, HIR, HAN,
KAN, KAT, ROM, THI, OR VIE.
PDS 0172 0591 PDS0172 SOLE PROPRIETOR NAME LENGTH MUST BE Both
1-15.
1151 PDS0172 SOLE PROPRIETOR NAME MUST BE LEFT Both


PDS 0173 0699 PDS0173 LEGAL CORPORATE NAME LENGTH MUST BE Both
1-15.
1152 PDS0173 LEGAL CORPORATE NAME MUST BE LEFT Both
PDS 0174 0377 PDS0174 DUN & BRADSTREET NUMBER LENGTH MUST Both
BE 1–15.
1163 PDS0174 DUN & BRADSTREET NUMBER MUST BE Both
NUMERIC.
PDS 0175 2165 PDS0175 CARD ACCEPTOR URL LENGTH MUST BE 1– Both
255.
2182 PDS0175 CARD ACCEPTOR URL MUST BE LEFT Both
ALL ZEROS.
PDS 0189 0422 PDS0189 POINT-OF-INTERACTION (POI) PHONE DATA Both
0423 PDS0189 POINT-OF-INTERACTION (POI) PHONE DATA Both
PDS 0189, s1 0424 PDS0189S1 FORMAT NUMBER MUST BE 0, 1, 2, 3, OR 4. Both
PDS 0189, s2 2208 PDS0189S2 POINT OF INTERACTION (POI) PHONE Both
DATA CANNOT BE ALL ZEROS OR ALL SPACES.
2259 PDS0189S2 PHONE DATA MUST CONTAIN 10 Both
CHARACTERS FOLLOWED BY TRAILING SPACES. THE
PDS 0190 0425 PDS0190 PARTNER ID CODE CANNOT BE ALL LOW- Both
2208 PDS0190 PARTNER ID CODE CANNOT BE ALL ZEROS Both
OR ALL SPACES.
PDS 0191 0528 PDS0191 ORIGINATING MESSAGE FORMAT MUST BE 1 GCMS
OR 2.
0823 PDS0191 ORIGINATING MESSAGE FORMAT LENGTH Both


PDS 0261 2181 PDS0261 RISK MANAGEMENT APPROVAL CODE MUST Both
2196 PDS0261 RISK MANAGEMENT APPROVAL CODE MUST Both
BE NUMERIC AND CANNOT BE ALL ZEROS.
2204 PDS0261 RISK MANAGEMENT APPROVAL CODE GCMS
INVALID.
2206 PDS0261 RISK MANAGEMENT APPROVAL CODE HAS GCMS
EXPIRED.
PDS 0375 2180 PDS0375 MEMBER RECONCILIATION INDICATOR 1 Both
LENGTH MUST BE 001–050.
2184 PDS0375 MEMBER RECONCILIATION INDICATOR 1 Both
NOT LEFT JUSTIFIED.
EXCEED 999 BYTES.

Financial Detail Addendum/1644-696

subfield for Financial Detail Addendum/1644-696 messages.
MTI/Function Code: Financial Detail Addendum/1644-696

0735 DE24 FUNCTION CODE MUST BE PRESENT IN Both
NUMERIC.
2196 DE32 AQUIRING INSTITUTION IDENTIFICATION CODE Both
PRESENT IN FINANCIAL DETAIL ADDENDUM
MESSAGES.
FOR FINANCIAL DETAIL ADDENDUM MESSAGES.
NUMERIC.
MUST BE 006-011.
DE62.
0735 DE48 ADDITIONAL DATA MUST BE PRESENT IN Both


ADDITIONAL DATA 2.
MUST BE 016-999.
0577 DE63 TRANSACTION LIFE CYCLE ID MUST BE THE Both
SAME IDENTIFIER AS PROVIDED IN THE RELATED
FIRST PRESENTMENT/1240.
SPACE.
0735 DE71 MESSAGE NUMBER MUST BE PRESENT IN
0160 DE94 TRANSACTION ORIGINATION INSTITUTION ID Both
CODE LENGTH FIELD MUST BE A VALUE OF 001-011.
CODE INVALID.
MASTERCARD.
1175 TRANSACTION ORIGINATOR INSTITUTION ID CODE GCMS
INVALID FOR SENDING PROCESSOR ID IN
PARAMETER MASTER.


DE124.
DATA 2 ARE PRESENT.
DE 124 2151 DE 124 CANNOT BE ALL LOW-VALUES OR ALL HIGH- Both
VALUES.
DE125.
ADDED.
PDS 0175 2160 PDS0175 CARD ACCEPTOR URL MUST BE LEFT Both
2165 PDS0175 CARD ACCEPTOR URL LENGTH MUST BE Both
1-255.
PDS 0191 0528 PDS0191 ORIGINATING MESSAGE FORMAT MUST BE GCMS
1 OR 2.
PDS 0501 0521 ASSOCIATED FINANCIAL DETAIL ADDENDUM/1644 Both
REJECTED.
0564 INVALID FINANCIAL DETAIL ADDENDUM. Both
0566 ASSOCIATED FIRST PRESENTMENT REJECTED. Both


PDS 0501 0735 PDS0501 TRANSACTION DESCRIPTION MUST BE Both
PRESENT IN FINANCIAL DETAIL ADDENDUM
MESSAGES.
0827 PDS0501 TRANSACTION DESCRIPTION LENGTH MUST Both
1048 PDS 0501S1 USAGE CODE MUST BE NUMERIC Both
2246 THE CORPORATE CARD COMMON DATA Both
REQUIREMENT ADDENDUM MESSAGE MUST BE
PRESENT WITH AN ELECTRONIC INVOICE-
TRANSACTION DATA.
2247 THE ELECTRONIC INVOICE-TRANSACTION DATA Both
MUST PRECEDE THE ELECTRONIC INVOICE-PARTY
INFORMATION.
2248 ONE OCCURRENCE OF ELECTRONIC INVOICE-PARTY Both
INFORMATION REQUIRED WITH ELECTRONIC
INVOICE-TRANSACTION INFORMATION.
2249 THE TELEPHONY BILLING DETAIL MUST FOLLOW THE Both
TELPEPHONY BILLING SUMMARY.
PDS 0501, s1 0208 PDS0501S1 USAGE CODE INVALID. MUST BE 01, 05, Both
06, 07, 08, 09, 10, 11, 98 OR 99.
0211 INVALID PASSENGER TRANSPORT ADDENDUM. Both
PASSENGER TRANSPORT ADDENDUM CAN ONLY BE
USED WITH A PASSENGER TRANSPORT CARD
ACCEPTOR BUSINESS CODE (MCC).
0212 INVALID VEHICLE RENTAL ADDENDUM. VEHICLE Both
RENTAL ADDENDUM CAN ONLY BE USED WITH A
VEHICLE RENTAL CARD ACCEPTOR BUSINESS CODE
(MCC).
0213 INVALID LODGING ADDENDUM. LODGING Both
ADDENDUM CAN ONLY BE USED WITH A LODGING
CARD ACCEPTOR BUSINESS CODE (MCC).
0214 INVALID CORPORATE FLEET ADDENDUM. Both
CORPORATE FLEET TRANSACTION DETAIL
INFORMATION ADDENDUM CAN ONLY BE USED
WITH A FUEL CARD ACCEPTOR BUSINESS CODE
(MCC) AND A FLEET ACCOUNT RANGE.


PDS 0501, s1 1031 INVALID CORPORATE ADDENDUM. CORPORATE Both
ADDENDUM INFORMATION CAN ONLY BE USED
WITH A CORPORATE ACCOUNT RANGE.
1048 PDS0501S1 USAGE CODE MUST BE NUMERIC. Both
PDS 0501, s2 0215 PDS0501S2 INDUSTRY RECORD NUMBER MUST BE Both
NUMERIC.
PDS 0501, s3 0217 PDS0501S3 OCCURRENCE INDICATOR MUST BE Both
NUMERIC.
0580 FINANCIAL DETAIL ADDENDUM/1644 OUT OF Both
SEQUENCE.
0971 PDS0501S3 OCCURRENCE INDICATOR INVALID. MUST Both
BE EQUAL TO “001” FOR USAGE CODE “01” AND
INDUSTRY RECORD NUMBER “000”.
BE IN THE RANGE OF “002-999” FOR USAGE CODE 01
AND INDUSTRY RECORD NUMBER “001”.
BE EQUAL TO “001” FOR USAGE CODE “98” AND
BE EQUAL TO “001” FOR USAGE CODE 98 AND
0976 PDS0501S3 OCCURRENCE INDICATOR MUST BE IN Both
THE RANGE OF “002-999” FOR USAGE CODE 98 AND
THE RANGE OF 001–999 FOR USAGE CODE 05 AND
INDUSTRY RECORD NUMBER 000.


PDS 0501, s3 2213 PDS0501S3 OCCURRENCE INDICATOR MUST BE IN Both
2250 PDS0501S3 OCCURRENCE INDICATOR MUST 001 FOR Both
USAGE CODE 11 AND INDUSTRY RECORD NUMBER
000.
2254 PDS0501S3 OCCURRENCE INDICATOR MUST BE 002- Both
999 FOR USAGE CODE 11 AND INDUSTRY RECORD
NUMBER 001.
PDS 0501, s4 0565 PDS0501S4 MESSAGE NUMBER MUST CONTAIN THE Both
SAME VALUE AS DE71 IN THE ASSOCIATED FIRST
PRESENTMENT.
PDS 0505 0222 PDS0505 PASSENGER NAME MUST BE LEFT JUSTIFIED Both
0828 PDS0505 PASSENGER NAME LENGTH MUST BE 1-29. Both
0917 PDS0505 PASSENGER NAME, PDS0506 TICKET Both
NUMBER, AND PDS0507 ISSUING CARRIER REQUIRED
FOR AIRLINE TRANSACTIONS SUBMITTED FOR MERIT
I, WORLD CARD T&E, PASSENGER TRANSPORT OR
CORP. T&E II INTERCHANGE PROGRAMS.
FOR PASSENGER RAILWAY TRANSACTIONS
SUBMITTED FOR CORP. T&E RATE I & II, WORLD
CARD T&E, MERIT I OR PASSENGER TRANSPORT
2182 PDS0505 PASSENGER NAME MUST BE LEFT JUSTIFIED Both
2184 PDS0505 PASSENGER NAME CANNOT BE ALL LOW- Both
VALUES OR HIGH-VALUES.
2187 PDS0505 PASSENGER NAME REQUIRED FOR AIRLINE Both
2188 PDS0505 PASSENGER NAME REQUIRED FOR Both
PASSENGER RAILWAY TRANSACTIONS SUBMITTED
FOR T&E III.


PDS 0506 0258 PDS0506 TICKET NUMBER CANNOT BE ALL LOW- Both
0483 PDS0506 TICKET NUMBER LENGTH MUST BE A FIXED Both
LENGTH OF 15.
2182 PDS0506 TICKET NUMBER MUST BE LEFT JUSTIFIED Both
2187 PDS0506 TICKET NUMBER REQUIRED FOR AIRLINE Both
2188 PDS0506 TICKET NUMBER REQUIRED FOR PASSENGER Both
PDS 0507 0829 PDS0507 ISSUING CARRIER MUST BE A FIXED LENGTH Both
OF 004.
1024 PDS0507 ISSUING CARRIER MUST BE LEFT JUSTIFIED Both
1127 PDS0507 ISSUING CARRIER CANNOT BE ALL LOW- Both


PDS 0507 2182 PDS0507 ISSUING CARRIER MUST BE LEFT JUSTIFIED Both
2187 PDS0507 ISSUING CARRIER REQUIRED FOR AIRLINE Both
2188 PDS0507 ISSUING CARRIER REQUIRED FOR Both
FOR T&E III.
PDS 0508 0270 PDS0508 CUSTOMER CODE MUST BE LEFT JUSTIFIED Both
0406 PDS0508 CUSTOMER CODE LENGTH MUST BE 001-025. Both
PDS 0509 0207 PDS0509 ISSUE DATE MUST BE A VALID DATE IN THE Both
FORMAT YYMMDD.
0830 PDS0509 ISSUE DATE MUST BE A FIXED LENGTH OF Both
006.
PDS0510 0226 PDS0510 TRAVEL AGENCY CODE CANNOT BE ALL Both
0831 PDS0510 TRAVEL AGENCY CODE MUST BE A FIXED Both
LENGTH OF 008.
1129 PDS0510 TRAVEL AGENCY CODE MUST BE LEFT Both
2182 PDS0510 TRAVEL AGENCY CODE MUST BE LEFT Both
ALL ZEROS.
PDS 0511 0227 PDS0511 TRAVEL AGENCY NAME CANNOT BE ALL Both
0982 PDS0511 TRAVEL AGENCY NAME LENGTH MUST BE Both
1-25.
1130 PDS0511 TRAVEL AGENCY NAME MUST BE LEFT Both
2182 PDS0511 TRAVEL AGENCY NAME MUST BE LEFT Both
ALL ZEROS.


PDS 0512 0206 PDS0512 TOTAL FARE MUST BE NUMERIC AND RIGHT- Both
JUSTIFIED.
0832 PDS0512 TOTAL FARE MUST BE A FIXED LENGTH OF Both
012.
2187 PDS0512 TOTAL FARE REQUIRED FOR AIRLINE Both
2188 PDS0512 TOTAL FARE REQUIRED FOR PASSENGER Both
PDS 0513 0219 PDS0513 TOTAL FEES MUST BE NUMERIC AND RIGHT- Both
JUSTIFIED.
0833 PDS0513 TOTAL FEES MUST BE A FIXED LENGTH OF Both
012.
PDS 0514 0220 PDS0514 TOTAL TAXES MUST BE NUMERIC AND Both
RIGHT-JUSTIFIED.
0834 PDS0514 TOTAL TAXES MUST BE A FIXED LENGTH OF Both
012.
PDS 0515 2180 PDS0515 ADDITIONAL CARD ACCEPTOR Both
INFORMATION LENGTH MUST BE 001–040.
2182 PDS0515 ADDITIONAL CARD ACCEPTOR Both
INFORMATION MUST BE LEFT JUSTIFIED AND
2184 PDS0515 ADDITIONAL CARD ACCEPTOR Both
INFORMATION CANNOT BE ALL LOW-VALUES OR ALL
HIGH-VALUES.
PDS 0516 2181 PDS0516 AUSTIN-TETRA NUMBER MUST BE A FIXED Both
LENGTH OF 15.
2182 PDS0516 AUSTIN-TETRA NUMBER MUST BE LEFT Both
ALL ZEROS.
2184 PDS0516 AUSTIN-TETRA NUMBER CANNOT BE ALL Both
PDS 0517 2181 PDS0517 NAICS CODE MUST BE A FIXED LENGTH OF Both
15.
2182 PDS0517 NAICS CODE MUST BE LEFT JUSTIFIED AND Both


PDS 0517 2184 PDS0517 NAICS CODE CANNOT BE ALL LOW-VALUES Both
OR ALL HIGH-VALUES.
PDS 0518 2181 PDS0518 LINE ITEM DATE MUST BE A FIXED LENGTH Both
OF 006.
2183 PDS0518 LINE ITEM DATE MUST BE NUMERIC. Both
2186 PDS0518 LINE ITEM DATE MUST BE A VALID DATE IN Both
THE FORMAT YYMMDD.
2235 PDS0518 LINE ITEM DATE MUST BE PRESENT AND A Both
VALID DATE WHEN LODGING SUMMARY IS PRESENT.
PDS 0519 2181 PDS0519 ADDITIONAL FUEL LOCATION Both
INFORMATION MUST BE A FIXED LENGTH OF 014.
PDS 0519, s1 2185 PDS0519S1 HOURS OF OPERATION/24 HOUR Both
PDS 0519, s2 2185 PDS0519S2 18 WHEELER ACCESS AVAILABLE MUST BE Both
A VALUE OF Y OR N.
PDS 0519, s3 2185 PDS0519S3 DIESEL SITES AVAILABLE MUST BE A Both
VALUE OF Y OR N.
PDS 0519, s4 2185 PDS0519S4 INTERSTATE ACCESS/EXIT NUMBER WITH Both
DIRECTIONS AVAILABLE MUST BE A VALUE OF Y OR
N.
PDS 0519, s5 2185 PDS0519S5 CONVENIENCE STORE AVAILABLE MUST Both
PDS 0519, s6 2185 PDS0519S6 TRUCK STOP RESTAURANT AVAILABLE Both
MUST BE A VALUE OF Y OR N.
PDS 0519, s7 2185 PDS0519S7 TRUCK STOP HOTEL AVAILABLE MUST BE Both
A VALUE OF Y OR N.
PDS 0519, s8 2185 PDS0519S8 TRUCK STOP WITH SHOWERS AVAILABLE Both
MUST BE A VALUE OF Y OR N.
PDS 0519, s9 2185 PDS0519S9 VEHICLE MAINTENANCE/REPAIR BAYS Both
PDS 0519, s10 2185 PDS0519S10 CAR WASH AVAILABLE MUST BE A VALUE Both
OF Y OR N.
PDS 0519, s11 2185 PDS0519S11 AVIATION LOCATIONS AVAILABLE MUST Both


PDS 0519, s12 2185 PDS0519S12 MARINA LOCATIONS AVAILABLE MUST BE Both
A VALUE OF Y OR N.
PDS 0519, s13 2185 PDS0519S13 ALTERNATIVE FUEL LOCATIONS Both
PDS 0519, s14 2185 PDS0519S14 PAY-AT-PUMP AVAILABLE MUST BE A Both
VALUE OF Y OR N.
PDS 0520 0223 PDS0520 TRAVEL DATE MUST BE A VALID DATE IN Both
THE FORMAT YYMMDD.
0835 PDS0520 TRAVEL DATE MUST BE A FIXED LENGTH OF Both
006.
0920 PDS0520 TRAVEL DATE, PDS0521 CARRIER CODE, Both
PDS0522 SERVICE CLASS CODE, PDS0523 CITY OF
ORIGIN/AIRPORT CODE, AND PDS0524 CITY OF
DESTINATION/AIRPORT CODE REQUIRED FOR
AIRLINE TRANSACTIONS SUBMITTED FOR U.S. MERIT
III, WORLD T&E, PASSENGER TRANSPORT OR
CORPORATE T&E II INTERCHANGE PROGRAMS.
FOR U.S. REGION MERIT III, CORPORATE T&E RATE II,
WORLD CARD T&E OR PASSENGER TRANSPORT
2187 PDS0520 TRAVEL DATE REQUIRED FOR AIRLINE Both
2188 PDS0520 TRAVEL DATE REQUIRED FOR PASSENGER Both
PDS 0521 0259 PDS0521 CARRIER CODE MUST BE LEFT JUSTIFIED Both
III, WORLD T&E, PASSENGER TRANSPORT, OR


PDS 0521 0984 PDS0521 CARRIER CODE MUST BE A FIXED LENGTH Both
OF 002.
WORLD CARD T&E, OR PASSENGER TRANSPORT
1128 PDS0521 CARRIER CODE CANNOT BE ALL LOW- Both
2182 PDS0521 CARRIER CODE MUST BE LEFT JUSTIFIED Both
2187 PDS0521 CARRIER CODE REQUIRED FOR AIRLINE Both
2188 PDS0521 CARRIER CODE REQUIRED FOR PASSENGER Both
PDS 0522 0067 PDS0522 SERVICE CLASS CODE MUST BE LEFT Both
0234 PDS0522 SERVICE CLASS CODE CANNOT BE ALL LOW- Both
0837 PDS0522 SERVICE CLASS CODE MUST BE A FIXED Both
LENGTH OF 002.


PDS 0522 2182 PDS0522 SERVICE CLASS CODE MUST BE LEFT Both
ALL ZEROS.
2187 PDS0522 SERVICE CLASS CODE REQUIRED FOR Both
AIRLINE TRANSACTIONS SUBMITTED FOR T&E III.
2188 PDS0522 SERVICE CLASS CODE REQUIRED FOR Both
FOR T&E III.
PDS 0523 0228 PDS0523 CITY OF ORIGIN/AIRPORT CODE CANNOT Both
0229 PDS0523 CITY OF ORIGIN/AIRPORT CODE MUST BE Both
0838 PDS0523 CITY OF ORIGIN/AIRPORT CODE MUST BE A Both
2182 PDS0523 CITY OF ORIGIN/AIRPORT CODE MUST BE Both
OR ALL ZEROS.
2187 PDS0523 CITY OF ORIGIN/AIRPORT CODE REQUIRED Both
FOR AIRLINE TRANSACTIONS SUBMITTED FOR T&E III.
2188 PDS0523 CITY OF ORIGIN/AIRPORT CODE REQUIRED Both


PDS 0524 0236 PDS0524 CITY OF DESTINATION/AIRPORT CODE Both
0237 PDS0524 CITY OF DESTINATION/AIRPORT CODE Both
MUST BE LEFT JUSTIFIED AND CANNOT CONTAIN ALL
SPACES.
SPACES OR ALL ZEROS.
REQUIRED FOR AIRLINE TRANSACTIONS SUBMITTED
FOR T&E III.
REQUIRED FOR PASSENGER RAILWAY TRANSACTIONS
PDS 0525 0235 PDS0525 STOP OVER CODE CANNOT BE ALL LOW- Both
0840 PDS0525 STOP OVER CODE MUST BE A FIXED Both
LENGTH OF 001.
2187 PDS0525 STOP OVER CODE REQUIRED FOR AIRLINE Both


PDS 0525 2188 PDS0525 STOP OVER CODE REQUIRED FOR Both
FOR T&E III.
2215 PDS0525 STOP OVER CODE MUST CONTAIN A VALUE Both
WITHIN THE RANGE OF 0–9, A-Z, OR SPACE.
PDS 0526 0781 PDS0526 CONJUNCTION TICKET MUST BE LEFT Both
0841 PDS0526 CONJUNCTION TICKET MUST BE A FIXED Both
LENGTH OF 015.
2182 PDS0526 CONJUNCTION TICKET MUST BE LEFT Both
ALL ZEROS.
2184 PDS0526 CONJUNCTION TICKET CANNOT BE ALL Both
PDS 0527 0782 PDS0527 EXCHANGE TICKET MUST BE LEFT JUSTIFIED Both
0842 PDS0527 EXCHANGE TICKET MUST BE A FIXED Both
LENGTH OF 015.
2182 PDS0527 EXCHANGE TICKET MUST BE LEFT JUSTIFIED Both
2184 PDS0527 EXCHANGE TICKET CANNOT BE ALL LOW- Both
PDS 0528 0783 PDS0528 COUPON NUMBER CANNOT BE ALL LOW- Both
0843 PDS0528 COUPON NUMBER MUST BE A FIXED Both
LENGTH OF 001.
2208 PDS0528 COUPON NUMBER CANNOT CONTAIN ALL Both
PDS 0529 0239 PDS0529 FARE BASIS CODE CANNOT BE ALL LOW- Both
0925 PDS0529 FARE BASIS CODE LENGTH MUST BE 1-15. Both
1037 PDS0529 FARE BASIS CODE CANNOT CONTAIN ALL Both
SPACES.
2187 PDS0529 FARE BASIS CODE REQUIRED FOR AIRLINE Both


PDS 0529 2188 PDS0529 FARE BASIS CODE REQUIRED FOR Both
FOR T&E III.
2208 PDS0529 FARE BASIS CODE CANNOT CONTAIN ALL Both
PDS 0530 0232 PDS0530 FLIGHT NUMBER MUST BE LEFT JUSTIFIED Both
0784 PDS0530 FLIGHT NUMBER CANNOT BE ALL LOW- Both
0844 PDS0530 FLIGHT NUMBER MUST BE A FIXED LENGTH Both
OF 005.
2182 PDS0530 FLIGHT NUMBER MUST BE LEFT JUSTIFIED Both
2187 PDS0530 FLIGHT NUMBER REQUIRED FOR AIRLINE Both
2188 PDS0530 FLIGHT NUMBER REQUIRED FOR PASSENGER Both
PDS 0531 0845 PDS0531 DEPARTURE TIME MUST BE A FIXED LENGTH Both
OF 005.
2187 PDS0531 DEPARTURE TIME REQUIRED FOR AIRLINE Both
2188 PDS0531 DEPARTURE TIME REQUIRED FOR Both
FOR T&E III.
PDS 0531, s1 0785 PDS0531S1 DEPARTURE TIME INVALID. MUST BE IN Both
THE FORMAT HHMM. HOURS MUST BE 00-23 AND
MINUTES MUST BE 00-59.
PDS 0531, s2 0786 PDS0531S2 DEPARTURE TIME SEGMENT INVALID. Both
MUST BE A, P OR A SPACE.
PDS 0532 2181 PDS0532 TOTAL CHARGES MUST BE A FIXED LENGTH Both
OF 014.
PDS 0532, s1 2183 PDS0532S1 TOTAL CHARGES AMOUNT MUST BE Both
NUMERIC.


PDS 0532, s2 2183 PDS0532S2 TOTAL CHARGES EXPONENT MUST BE Both
NUMERIC.
2215 PDS0532S2 TOTAL CHARGES EXPONENT MUST Both
PDS 0532, s3 2185 PDS0532S3 TOTAL CHARGES SIGN MUST BE D OR C. Both
PDS 0533 0846 PDS0533 ARRIVAL TIME MUST BE A FIXED LENGTH OF Both
005.
PDS 0533, s1 1038 PDS0533S1 ARRIVAL TIME INVALID. MUST BE IN THE Both
FORMAT HHMM. HOURS MUST BE 00-23 AND
PDS 0533, s2 0927 PDS0533S2 ARRIVAL TIME SEGMENT INVALID. MUST Both
BE A, P OR A SPACE.
PDS 0534 2181 PDS0534 TOTAL NON-ROOM CHARGES MUST BE A Both
PDS 0534, s1 2183 PDS 534S1 TOTAL NON-ROOM CHARGES AMOUNT Both
MUST BE NUMERIC.
PDS 0534, s2 2183 PDS0534S2 TOTAL NON-ROOM CHARGES EXPONENT Both
MUST BE NUMERIC.
2215 PDS0534S2 TOTAL NON-ROOM CHARGES EXPONENT Both
MUST CONTAIN A VALUE WITHIN THE RANGE OF 0–
5.
PDS 0534, s3 2185 PDS0534S3 TOTAL NON-ROOM CHARGES SIGN MUST Both
BE D OR C.
PDS 0535 0847 PDS0535 FARE MUST BE A FIXED LENGTH OF 012. Both
1123 PDS0535 FARE MUST BE NUMERIC AND RIGHT- Both
JUSTIFIED.
PDS 0536 0848 PDS0536 FEE MUST BE A FIXED LENGTH OF 012. Both
1124 PDS0536 FEE MUST BE NUMERIC AND RIGHT- Both
JUSTIFIED.
PDS 0537 0849 PDS0537 TAXES MUST BE A FIXED LENGTH OF 012. Both
1125 PDS0537 TAXES MUST BE NUMERIC AND RIGHT- Both
JUSTIFIED.


PDS 0538 0676 PDS0538 ENDORSEMENTS/RESTRICTIONS LENGTH Both
MUST BE 1-20.
0792 PDS0538 ENDORSEMENTS/RESTRICTIONS MUST BE Both
1027 PDS0538 ENDORSEMENTS/RESTRICTIONS CANNOT BE Both
2182 PDS0538 ENDORSEMENT/RESTRICTIONS MUST BE Both
LEFT JUSTIFIED AND CANNOT CONATIN ALL SPACES
OR ALL ZEROS.
PDS 0539 2181 PDS0539 TOTAL AMOUNT CHARGED ON CREDIT Both
CARD MUST BE A FIXED LENGTH OF 014.
PDS 0539, s1 2183 PDS0539S1 TOTAL AMOUNT CHARGED ON CREDIT Both
CARD AMOUNT MUST BE NUMERIC.
CARD EXPONENT MUST BE NUMERIC.
2215 PDS0539S2 TOTAL NON-ROOM CHARGES EXPONENT Both
5.
CARD SIGN MUST BE D OR C.
PDS 0540 2181 PDS0540 ROOM SERVICE CHARGES MUST BE A FIXED Both
LENGTH OF 014.
PDS 0540, s1 2183 PDS0540S1 ROOM SERVICE CHARGES AMOUNT MUST Both
BE NUMERIC.
PDS 0540, s2 2183 PDS0540S2 ROOM SERVICE CHARGES EXPONENT Both
MUST BE NUMERIC.
2215 PDS0540S2 ROOM SERVICE CHARGES EXPONENT Both
MUST CONTAIN A VALUE WITHIN THE RANGE OF
0–5.
PDS 0540, s3 2185 PDS0540S3 ROOM SERVICE CHARGES SIGN MUST BE D Both
OR C.
PDS 0541 2181 PDS0541 LOUNGE/BAR CHARGES MUST BE A FIXED Both
LENGTH OF 014.
PDS 0541, s1 2183 PDS0541S1 LOUNGE/BAR CHARGES AMOUNT MUST Both
BE NUMERIC.


PDS 0541, s2 2183 PDS0541S2 LOUNGE/BAR CHARGES EXPONENT MUST Both
BE NUMERIC.
2215 PDS0541S2 LOUNGE/BAR CHARGES EXPONENT MUST Both
PDS 0541, s3 2185 PDS0541S3 LOUNGE/BAR CHARGES SIGN MUST BE D Both
OR C.
PDS 0542 2181 PDS0542 TRANSPORTATION CHARGES MUST BE A Both
PDS 0542, s1 2183 PDS0542S1 TRANSPORTATION CHARGES AMOUNT Both
MUST BE NUMERIC.
PDS 0542, s2 2183 PDS0542S2 TRANSPORTATION CHARGES EXPONENT Both
MUST BE NUMERIC.
2215 PDS0542S2 TRANSPORTATION CHARGES EXPONENT Both
5.
PDS 0542, s3 2185 PDS0542S3 TRANSPORTATION CHARGES SIGN MUST Both
BE D OR C.
PDS 0543 2181 PDS0543 GRATUITY CHARGES MUST BE A FIXED Both
LENGTH OF 014.
PDS 0543, s1 2183 PDS0543S1 GRATUITY CHARGES AMOUNT MUST BE Both
NUMERIC.
PDS 0543, s2 2183 PDS0543S2 GRATUITY CHARGES EXPONENT MUST BE Both
NUMERIC.
2215 PDS0543S2 GRATUITY CHARGES EXPONENT MUST Both
PDS 0543, s3 2185 PDS0543S3 GRATUITY CHARGES SIGN MUST BE D OR Both
C.
PDS 0544 0850 PDS0544 RENTAL AGREEMENT NUMBER MUST BE A Both


PDS 0544 0928 PDS0544 RENTAL AGREEMENT NUMBER, PDS0545 Both
RENTER NAME, PDS0546 RENTAL RETURN CITY,
PDS0547 RENTAL RETURN STATE/PROVINCE, PDS0548
RENTAL RETURN COUNTRY, PDS0549 RENTAL RETURN
LOCATION ID, PDS0550 RENTAL RETURN DATE,
PDS0551 RENTAL CHECK-OUT DATE, AND PDS0552
CUSTOMER SERVICE TOLL-FREE NUMBER REQUIRED
FOR U.S. REGION TRAVEL INDUSTRIES PREMIER
SERVICE OR CORPORATE T&E RATE II INTERCHANGE
PROGRAM.
1039 PDS0544 RENTAL AGREEMENT NUMBER MUST BE LEFT Both
JUSTIFIED AND CANNOT CONTAN ALL SPACES.
2182 PDS0544 RENTAL AGREEMENT NUMBER MUST BE LEFT Both
ALL ZEROS.
2184 PDS0544 RENTAL AGREEMENT NUMBER CANNOT BE Both
2189 PDS0544 RENTAL AGREEMENT NUMBER REQUIRED Both
FOR VEHICLE RENTAL TRANSACTIONS SUBMITTED
FOR T&E III.
PROGRAM.
0930 PDS0545 RENTER NAME, PDS0546 RENTAL RETURN Both
CITY, PDS0547 RENTAL RETURN STATE/PROVINCE,
PDS0548 RENTAL RETURN COUNTRY, PDS0550 RENTAL
RETURN DATE, PDS0551 RENTAL CHECK-OUT DATE,
AND PDS0552 CUSTOMER SERVICE TOLL-FREE
NUMBER REQUIRED FOR WORLD MASTERCARD T&E


PDS 0545 2180 PDS0545 RENTER NAME LENGTH MUST BE 001-040. Both
2182 PDS0545 RENTER NAME MUST BE LEFT JUSTIFIED AND Both
2184 PDS0545 RENTER NAME CANNOT BE ALL LOW-VALUES Both
OR ALL HIGH-VALUES.
2189 PDS0545 RENTER NAME REQUIRED FOR VEHICLE Both
PROGRAM.
2180 PDS0546 RENTAL RETURN CITY LENGTH MUST BE 001- Both
025.
2182 PDS0546 RENTAL RETURN CITY MUST BE LEFT Both
ALL ZEROS.
2184 PDS0546 RENTAL RETURN CITY CANNOT BE ALL LOW- Both
2189 PDS0546 RENTAL RETURN CITY REQUIRED FOR Both
VEHICLE RENTAL TRANSACTIONS SUBMITTED FOR
T&E III.


PDS 0547 0302 PDS0547 RENTAL RETURN STATE/PROVINCE INVALID. Both
0851 PDS0547 RENTAL RETURN STATE/PROVINCE MUST BE Both
0928 PDS0544 RENTAL AGREEMENT NUMBER, PDS0545 Both
PROGRAM.
2182 PDS0547 RENTAL RETURN STATE/PROVINCE MUST BE Both
OR ALL ZEROS.
2184 PDS0547 RENTAL RETURN STATE/PROVINCE CANNOT Both
2189 PDS0547 RENTAL RETURN STATE/PROVINCE Both
REQUIRED FOR VEHICLE RENTAL TRANSACTIONS
PDS 0548 0304 PDS0548 RENTAL RETURN COUNTRY MUST CONTAIN Both
A VALID ISO STANDARD COUNTRY CODE.
0305 PDS0548 RENTAL RETURN COUNTRY MUST BE LEFT Both
0852 PDS0548 RENTAL RETURN COUNTRY MUST BE A Both


PROGRAM.
2189 PDS0548 RENTAL RETURN COUNTRY REQUIRED FOR Both
T&E III
PDS 0549 0853 PDS0549 RENTAL RETURN LOCATION ID MUST BE A Both
PROGRAM.
1042 PDS0549 RENTAL RETURN LOCATION ID MUST BE Both
2189 PDS0549 RENTAL RETURN LOCATION ID REQUIRED Both
FOR T&E III.


PDS 0550 0307 PDS0550 RENTAL RETURN DATE MUST BE A VALID Both
0854 PDS0550 RENTAL RETURN DATE MUST BE A FIXED Both
LENGTH OF 006.
PROGRAM.
2189 PDS0550 RENTAL RETURN DATE REQUIRED FOR Both
T&E III.
PDS 0551 0308 PDS0551 RENTAL CHECKOUT DATE MUST BE A VALID Both
0855 PDS0551 RENTAL CHECKOUT DATE MUST BE A FIXED Both
LENGTH OF 006.
PROGRAM.


PDS 0551 0930 PDS0545 RENTER NAME, PDS0546 RENTAL RETURN Both
‘ 2189 PDS0551 RENTAL CHECK-OUT DATE REQUIRED FOR Both
T&E III.
PDS 0552 0491 PDS0552 CUSTOMER SERVICE TOLL-FREE (800) Both
NUMBER, PDS0574 ARRIVAL DATE, PDS0575
DEPARTURE DATE, PDS0576 FOLIO NUMBER, AND
PDS0577 PROPERTY PHONE NUMBER REQUIRED FOR
LODGING TRANS. SUBMITTED FOR U.S. REGION
TRAVEL INDUSTRIES PREMIER SERVICE INTERCHANGE
PROGRAM.
PROGRAM.
1043 PDS0552 CUSTOMER SERVICE TOLL-FREE (800) Both
NUMBER CANNOT BE ALL ZEROS OR ALL SPACES.


PDS 0552 1164 PDS0574 ARRIVAL DATE, PDS0575 DEPARTURE DATE, Both
PDS0576 FOLIO NUMBER, AND EITHER PDS0577
PROPERTY PHONE NUMBER OR PDS0552 CUSTOMER
SERVICE TOLL-FREE NUMBER ARE REQUIRED FOR
LODGING TRANS. SUBMITTED FOR U.S.REGION
WORLD MASTERCARD T&E OR CORP. T&E RATE II
NUMBER MUST BE A FIXED LENGTH OF 017.
NUMBER CANNOT BE ALL LOW-VALUES OR ALL
HIGH-VALUES.
2189 PDS0552 CUSTOMER SERVICE TOLL-FREE NUMBER Both
2190 PDS0552 CUSTOMER SERVICE TOLL-FREE NUMBER Both
REQUIRED FOR LODGING TRANSACTIONS
SUBMITTED FOR T&E II.
2259 PDS0552 CUSTOMER SERVICE TOLL FREE (800) Both
NUMBER MUST CONTAIN 10 CHARACTERS FOLLOWED
BY TRAILING SPACES. THE FIRST THREE POSITIONS
MUST BE NUMERIC.
PDS 0553 0857 PDS0553 RENTAL RATE MUST BE A FIXED LENGTH OF Both
013.
PDS 0553, s1 0940 PDS0553S1 RENTAL RATE INDICATOR MUST BE D, W Both
OR M.
PDS 0553, s2 0939 PDS0553S2 RENTAL RATE INVALID. MUST BE Both
NUMERIC.
PDS 0554 2181 PDS0554 CONFERENCE ROOM CHARGES MUST BE A Both
PDS 0554, s1 2183 PDS0554S1 CONFERENCE ROOM CHARGES AMOUNT Both
MUST BE NUMERIC.
PDS 0554, s2 2183 PDS0554S2 CONFERENCE ROOM CHARGES EXPONENT Both
MUST BE NUMERIC.
2215 PDS 554S2 CONFERENCE ROOM CHARGES EXPONENT Both
0–5.


PDS 0554, s3 2185 PDS0554S3 CONFERENCE ROOM CHARGES SIGN MUST Both
BE D OR C.
PDS 0555 0312 PDS0555 RATE PER MILE (OR PER KILOMETER) Both
INVALID.MUST BE NUMERIC.
0858 PDS0555 RATE PER MILE (OR PER KILOMETER) MUST Both
PDS 0556 0859 PDS0556 TOTAL MILES (OR KILOMETERS) MUST BE A Both
2196 PDS0556 TOTAL MILES (OR KILOMETERS) MUST BE Both
PDS 0557 0314 PDS0557 MAXIMUM FREE MILES (OR KILOMETERS) Both
INVALID. MUST BE NUMERIC.
0860 PDS0557 MAXIMUM FREE MILES (OR KILOMETERS) Both
PDS 0558 0310 PDS0558 MILES/KILOMETER INDICATOR MUST BE K, M Both
OR A SPACE.
0861 PDS0558 MILES/KILOMETER INDICATOR MUST BE A Both
PDS 0559 0862 PDS0559 VEHICLE INSURANCE MUST BE A FIXED Both
LENGTH OF 013.
PDS 0559, s1 0316 PDS0559S1 INSURANCE INDICATOR MUST BE Y, N OR Both
A SPACE.
PDS 0559, s2 0941 PDS0559S2 INSURANCE CHARGES CANNOT EQUAL ALL Both
SPACES OR ALL ZEROS IF INSURANCE INDICATOR IS
EQUAL TO "Y".
PDS 0560 2181 PDS0560 AUDIO VISUAL CHARGES MUST BE A FIXED Both
LENGTH OF 014.
PDS 0560, s1 2183 PDS0560S1 AUDIO VISUAL CHARGES AMOUNT MUST Both
BE NUMERIC.
PDS 0560, s2 2183 PDS0560S2 AUDIO VISUAL CHARGES EXPONENT MUST Both
BE NUMERIC.
2215 PDS0560S2 AUDIO VISUAL CHARGES EXPONENT MUST Both
PDS 0560, s3 2185 PDS0560S3 AUDIO VISUAL CHARGES SIGN MUST BE D Both
OR C.


PDS 0561 0863 PDS0561 ADJUSTED AMOUNT MUST BE A FIXED Both
LENGTH OF 013.
PDS0561, s1 0318 PDS0561S1 ADJUSTED AMOUNT INDICATOR MUST BE Both
A SPACE, A, B, C, D, E OR X.
PDS 0561, s2 0789 PDS0561S2 ADJUSTED AMOUNT CANNOT EQUAL ALL Both
SPACES OR ALL ZEROS IF PDS0561S1 ADJUSTED
AMOUNT INDICATOR IS EQUAL TO A, B, C, D, E or X.
2232 PDS0561S2 ADJUSTED AMOUNT MUST BE NUMERIC Both
AND GREATER THAN ZERO.
PDS 0562 2181 PDS0562 BANQUET CHARGES MUST BE A FIXED Both
LENGTH OF 014.
PDS 0562, s1 2183 PDS0562S1 BANQUET CHARGES AMOUNT MUST BE Both
NUMERIC.
PDS 0562, s2 2183 PDS0562S2 BANQUET CHARGES EXPONENT MUST BE Both
NUMERIC.
2215 PDS0562S2 BANQUET CHARGES EXPONENT MUST Both
PDS 0562, s3 2185 PDS0562S3 BANQUET CHARGES SIGN MUST BE D OR Both
C.
PDS 0563 0865 PDS0563 PROGRAM CODE MUST BE A FIXED LENGTH Both
OF 002.
2182 PDS0563 PROGRAM CODE MUST BE LEFT JUSTIFIED Both
2184 PDS0563 PROGRAM CODE CANNOT BE ALL LOW- Both
2189 PDS0564 RENTAL LOCATION CITY REQUIRED FOR Both
T&E III.
PDS 0564 2180 PDS0564 RENTAL LOCATION CITY LENGTH MUST BE Both
001-025.
2182 PDS0564 RENTAL LOCATION CITY MUST BE LEFT Both
ALL ZEROS.
2184 PDS0564 RENTAL LOCATION CITY CANNOT BE ALL Both


PDS 0565 0496 PDS0565 RENTAL LOCATION STATE/PROVINCE MUST Both
BE LEFT JUSTIFIED AND CANNOT CONTAIN ALL
SPACES.
0866 PDS0565 RENTAL LOCATION STATE/PROVINCE MUST Both
CONTAIN A VALID U.S. STATE/PROVINCE CODE IF
PDS0566 RENTAL LOCATION COUNTRY CONTAINS
“USA”.
2184 PDS0565 RENTAL LOCATION STATE/PROVINCE Both
2189 PDS0565 RENTAL LOCATION STATE/PROVINCE Both
PDS 0566 1032 PDS0566 RENTAL LOCATION COUNTRY MUST Both
1044 PDS0566 RENTAL LOCATION COUNTRY MUST BE LEFT Both
1133 PDS0566 RENTAL LOCATION COUNTRY MUST BE A Both
2189 PDS0566 RENTAL LOCATION COUNTRY REQUIRED Both
FOR T&E III.
PDS 0567 1083 PDS0567 RENTAL LOCATION ID MUST BE LEFT Both
1134 PDS0567 RENTAL LOCATION ID MUST BE A FIXED Both
LENGTH OF 010.
2182 PDS0567 RENTAL LOCATION ID MUST BE LEFT Both
ALL ZEROS
2184 PDS0567 RENTAL LOCATION ID CANNOT BE ALL LOW- Both


PDS 0568 1135 PDS0568 RENTAL CLASS ID MUST BE A FIXED LENGTH Both
OF 004.
2182 PDS0568 RENTAL CLASS ID MUST BE LEFT JUSTIFIED Both
2184 PDS0568 RENTAL CLASS ID CANNOT BE ALL LOW- Both
2189 PDS0568 RENTAL CLASS IDENTIFIER REQUIRED FOR Both
T&E III.
PDS 0569 2181 PDS0569 INTERNET ACCESS MUST BE A FIXED Both
LENGTH OF 014.
PDS 0569, s1 2183 PDS0569S1 INTERNET ACCESS AMOUNT MUST BE Both
NUMERIC.
PDS 0569, s2 2183 PDS0569S2 INTERNET ACCESS EXPONENT MUST BE Both
NUMERIC.
2215 PDS0569S2 INTERNET ACCESS CHARGES EXPONENT Both
5.
PDS 0569, s3 2185 PDS0569S3 INTERNET ACCESS CHARGES SIGN MUST Both
BE D OR C.
PDS 0570 2181 PDS0570 EARLY DEPARTURE CHARGES MUST BE A Both
PDS 0570, s1 2183 PDS0570S1 EARLY DEPARTURE CHARGES AMOUNT Both
MUST BE NUMERIC.
PDS 0570, s2 2183 PDS0570S2 EARLY DEPARTURE CHARGES EXPONENT Both
MUST BE NUMERIC.
2215 PDS0570S2 EARLY DEPARTURE CHARGES EXPONENT Both
0–5.
PDS 0570, s3 2185 PDS0570S3 EARLY DEPARTURE CHARGES SIGN MUST Both
BE D OR C.
PDS 0571 2180 PDS0571 GUEST NAME LENGTH MUST BE 001-040. Both
2182 PDS0571 GUEST NAME MUST BE LEFT JUSTIFIED AND Both
2184 PDS0571 GUEST NAME CANNOT BE ALL LOW-VALUES Both
OR ALL HIGH-VALUES.


PDS 0572 2181 PDS0572 GUEST NUMBER MUST BE A FIXED LENGTH Both
OF 025.
2182 PDS0572 GUEST NUMBER MUST BE LEFT JUSTIFIED Both
2184 PDS0572 GUEST NUMBER CANNOT BE ALL LOW- Both
PDS 0573 2180 PDS0573 INVOICE NUMBER LENGTH MUST BE 001-025. Both
2182 PDS0573 INVOICE NUMBER MUST BE LEFT JUSTIFIED Both
PDS 0573 2184 PDS0573 INVOICE NUMBER CANNOT BE ALL LOW- Both
PDS 0574 0321 PDS0574 ARRIVAL DATE MUST BE A VALID DATE IN Both
THE FORMAT YYMMDD.
PROGRAM.
0868 PDS0574 ARRIVAL DATE MUST BE A FIXED LENGTH Both
OF 006.
1164 PDS0574 ARRIVAL DATE, PDS0575 DEPARTURE DATE, Both
2190 PDS0574 ARRIVAL DATE REQUIRED FOR LODGING Both
PROGRAM.


PDS 0575 0869 PDS0575 DEPARTURE DATE MUST BE A FIXED Both
LENGTH OF 006.
1126 PDS0575 DEPARTURE DATE MUST BE A VALID DATE Both
2190 PDS0575 DEPARTURE DATE REQUIRED FOR LODGING Both
PROGRAM.
1045 PDS0576 FOLIO NUMBER MUST BE LEFT JUSTIFIED Both
2180 PDS0576 FOLIO NUMBER LENGTH MUST BE 001-025. Both
2182 PDS0576 FOLIO NUMBER MUST BE LEFT JUSTIFIED Both
2184 PDS0576 FOLIO NUMER CANNOT BE ALL LOW-VALUES Both
OR ALL HIGH-VALUES.
2190 PDS0576 FOLIO NUMBER REQUIRED FOR LODGING Both


PROGRAM.
1046 PDS0577 PROPERTY PHONE NUMBER CANNOT BE ALL Both
2181 PDS0577 PROPERTY NUMER MUST BE A FIXED Both
LENGTH OF 017.
2184 PDS0577 PROPERTY PHONE NUMBER CANNOT BE ALL Both
2190 PDS0577 PROPERTY PHONE NUMBER REQUIRED FOR Both
2259 PDS0577 PROPERTY PHONE NUMBER MUST CONTAIN Both
10 CHARACTERS FOLLOWED BY TRAILING SPACES.
THE FIRST THREE POSITIONS MUST BE NUMERIC.
PDS 0578 2181 PDS0578 BILLING ADJUSTMENT LENGTH MUST BE A Both
PDS 0578, s1 0326 PDS0578S1 BILLING ADJUSTMENT INDICATOR MUST Both
BE Y, N OR A SPACE.
PDS 0578, s2 0327 PDS0578S2 BILLING ADJUSTMENT AMOUNT INVALID. Both
MUST BE NUMERIC.
0328 PDS0578S2 BILLING ADJUSTED AMOUNT CANNOT Both
EQUAL ALL ZEROS IF BILLING ADJUSTMENT
INDICATOR IS EQUAL TO "Y".


PDS 0578, s3 2183 PDS0578S3 BILING ADJUSTMENT EXPONENT MUST BE Both
NUMERIC.
2215 PDS0578S3 BILLING ADJUSTMENT EXPONENT MUST Both
PDS 0578, s4 2185 PDS0578S4 BILLING ADJUSTMENT SIGN MUST BE D Both
OR C.
PDS 0579 2181 PDS0579 INVOICE DATE MUST BE A FIXED LENGTH Both
OF 006.
2183 PDS0579 INVOICE DATE MUST BE NUMERIC. Both
2186 PDS0579 INVOICE DATE MUST BE A VALID DATE IN Both
THE FORMAT YYMMDD.
PDS 0580 2181 PDS0580 ROOM RATE MUST BE A FIXED LENGTH OF Both
013.
2190 PDS0580 ROOM RATE REQUIRED FOR LODGING Both
PDS 0580, s1 2183 PDS0580S1 ROOM RATE AMOUNT MUST BE NUMERIC. Both
PDS 0580, s2 2183 PDS0580S2 ROOM RATE EXPONENT MUST BE Both
NUMERIC.
2215 PDS0580S2 ROOM RATE EXPONENT MUST CONTAIN A Both
PDS 0581 2181 PDS0581 TOTAL ROOM TAX AMOUNT MUST BE A Both
2190 PDS0581 ROOM TAX REQUIRED FOR LODGING Both
PDS 0581, s1 2183 PDS0581S1 TOTAL ROOM TAX AMOUNT MUST BE Both
NUMERIC.
PDS 0581, s2 2183 PDS0581S2 TOTAL ROOM TAX EXPONENT MUST BE Both
NUMERIC.
2215 PDS0581S2 TOTAL ROOM TAX EXPONENT MUST Both
PDS 0581, s3 2185 PDS0581S3 TOTAL ROOM TAX SIGN MUST BE D OR C. Both


PDS 0582 0875 PDS0582 PROGRAM CODE MUST BE A FIXED LENGTH Both
OF 002.
2182 PDS0582 PROGRAM CODE MUST BE LEFT JUSTIFIED Both
2184 PDS0582 PROGRAM CODE CANNOT BE ALL LOW- Both
PDS 0583 2181 PDS0583 PHONE CHARGES AMOUNT MUST BE FIXED Both
LENGTH OF 014.
PDS 0583, s1 2183 PDS0583S1 PHONE CHARGES AMOUNT MUST BE Both
NUMERIC.
PDS 0583, s2 2183 PDS0583S2 PHONE CHARGES EXPONENT MUST BE Both
NUMERIC.
2215 PDS0583S2 PHONE CHARGES EXPONENT MUST Both
PDS 0583, s3 2185 PDS0583S3 PHONE CHARGES SIGN MUST BE D OR C. Both
PDS 0584 2181 PDS0584 RESTAURANT CHARGES AMOUNT MUST BE A Both
PDS 0584, s1 2183 PDS0584S1 RESTAURANT CHARGES AMOUNT MUST BE Both
NUMERIC.
PDS 0584, s2 2183 PDS0584S2 RESTAURANT CHARGES EXPONENT MUST Both
BE NUMERIC.
2215 PDS0584S2 RESTAURANT CHARGES EXPONENT MUST Both
PDS 0584, s3 2185 PDS0584S3 RESTAURANT CHARGES SIGN MUST BE D Both
OR C.
PDS 0585 2181 PDS0585 MINI-BAR CHARGES AMOUNT MUST BE A Both
PDS 0585, s1 2183 PDS0585S1 MINI-BAR CHARGES AMOUNT MUST BE Both
NUMERIC.
PDS 0585, s2 2183 PDS0585S2 MINI-BAR CHARGES EXPONENT MUST BE Both
NUMERIC.
2215 PDS0585S2 MINI BAR CHARGES EXPONENT MUST Both


PDS 0585, s3 2185 PDS0585S3 MINI-BAR CHARGES SIGN MUST BE D OR Both
C.
PDS 0586 2181 PDS0586 GIFT SHOP CHARGES AMOUNT MUST BE A Both
PDS 0586, s1 2183 PDS0586S1 GIFT SHOP CHARGES AMOUNT MUST BE Both
NUMERIC.
PDS 0586, s2 2183 PDS0586S2 GIFT SHOP CHARGES EXPONENT MUST BE Both
NUMERIC.
2215 PDS0586S2 GIFT SHOP CHARGES EXPONENT MUST Both
PDS 0586, s3 2185 PDS0586S3 GIFT SHOP CHARGES SIGN MUST BE D OR Both
C.
PDS 0587 2181 PDS0587 LAUNDRY & DRY CLEANING CHARGES MUST Both
BE FIXED LENGTH OF 014.
PDS 0587, s1 2183 PDS0587S1 LAUNDRY AND DRY CLEANING CHARGES Both
AMOUNT MUST BE NUMERIC.
PDS 0587, s2 2183 PDS0587S2 LAUNDRY AND DRY CLEANING CHARGES Both
EXPONENT MUST BE NUMERIC.
2215 PDS0587S2 LAUNDRY AND DRY CLEANING CHARGES Both
EXPONENT MUST CONTAIN A VALUE WITHIN THE
RANGE 0–5.
PDS 0587, s3 2185 PDS0587S3 LAUNDRY & DRY CLEANING CHARGES Both
SIGN MUST BE D OR C.
PDS 0588 2236 PDS0588 OTHER SERVICES LENGTH MUST BE 017-102 Both
AND MUST BE DIVISIBLE BY MINIMUM OCCURRENCE
LENGTH OF 17.
PDS 0588, s1 2182 PDS0588S1 OTHER SERVICES CODE MUST BE LEFT Both
ALL ZEROS.
2184 PDS0588S1 OTHER SERVICES CODE CANNOT BE ALL Both
LOW-VALUES OR HIGH-VALUES.
PDS 0588, s2 2183 PDS0588S2 OTHER SERVICE AMOUNT MUST BE Both
NUMERIC.
PDS 0588, s3 2183 PDS0588S3 OTHER SERVICES EXPONENT MUST BE Both
NUMERIC.


PDS 0588, s3 2215 PDS0588S3 OTHER SERVICES EXPONENT MUST Both
PDS 0588, s4 2185 PDS0588S4 OTHER SERVICES SIGN MUST BE D OR C. Both
PDS 0589 2181 PDS0589 INVOICE CREATION DATE/TIME MUST BE A Both
PDS 0589, s1 2183 PDS0589S1 INVOICE CREATION DATE MUST BE Both
NUMERIC.
2186 PDS0589S1 INVOICE CREATION DATE MUST BE A Both
PDS 0589, s2 2183 PDS0589S2 INVOICE CREATION TIME MUST BE Both
NUMERIC.
2238 PDS0589S2 INVOICE CREATION TIME MUST BE A Both
VALID TIME IN THE FORMAT HHMMSS.
PDS 0590 2181 PDS0590 PARTY IDENTIFICATION MUST BE A FIXED Both
LENGTH OF 002.
2185 PDS0590 PARTY IDENTIFICATION MUST BE BY, SU, IV, Both
PE, DP, OR SF.
PDS 0591 2236 PDS0591 PARTY NAME LENGTH MUST BE 040–120 Both
LENGTH OF 040.
PDS 0591,s1 2182 PDS0591 PARTY NAME MUST BE LEFT JUSTIFIED AND Both
2184 PDS0591S1 PARTY NAME CANNOT BE ALL LOW- Both
PDS 0592 2236 PDS0592 PARTY ADDRESS LENGTH MUST BE 040–240 Both
LENGTH OF 040.
PDS 0592, s1 2182 PDS0592S1 PARTY ADDRESS MUST BE LEFT JUSTIFIED Both
2184 PDS0592S1 PARTY ADDRESS LINE CANNOT BE ALL Both


PDS 0593 2180 PDS0593 PARTY POSTAL INFORMATION LENGTH Both
MUST BE 025-046.
PDS 0593, s1 2181 PDS0593S1 CITY MUST BE A FIXED LENGTH OF 025. Both
2182 PDS0593S1 CITY MUST BE LEFT JUSTIFIED AND Both
2184 PDS0593S1 CITY CANNOT BE ALL LOW-VALUES OR Both
ALL HIGH-VALUES.
PDS 0593, s2 2181 PDS0593S2 STATE/PROVINCE CODE MUST BE FIXED Both
LENGTH OF 003.
2182 PDS0593S2 STATE/PROVINCE CODE MUST BE LEFT Both
ALL ZEROS.
2184 PDS0593S2 STATE/PROVINCE CANNOT BE ALL LOW- Both
PDS 0593, s3 2181 PDS0593S3 COUNTRY CODE MUST BE FIXED LENGTH Both
OF 003.
2182 PDS0593S3 COUNTRY CODE MUST BE LEFT JUSTIFIED Both
2184 PDS0593S3 COUNTRY CODE CANNOT BE ALL LOW- Both
PDS 0593, s4 2181 PDS0593S4 POSTAL CODE MUST BE FIXED LENGTH Both
OF 015.
2182 PDS0593S4 POSTAL CODE MUST BE LEFT JUSTIFIED Both
2184 PDS0593S4 POSTAL CODE CANNOT BE ALL LOW- Both
PDS 0594 2236 PDS0594 PARTY CONTACT LENGTH MUST BE 061–305 Both
LENGTH OF 61.
PDS 0594, s1 2183 PDS0594S1 PARTY CONTACT DESCRIPTOR MUST BE Both
NUMERIC.
2185 PDS0594S1 PARTY CONTACT DESCRIPTOR MUST BE 1, Both
2, 3, 4, OR 5.


PDS 0594, s2 2182 PDS0594S2 PARTY CONTACT INFORMATION MUST BE Both
OR ALL ZEROS.
2184 PDS0594S2 PARTY CONTACT INFORMATION CANNOT Both
PDS 0595 0650 PDS0595 CARD ACCEPTOR TYPE MUST BE LEFT Both
0947 PDS0595 CARD ACCEPTOR TYPE AND PDS0596 Both
MERCHANT TAX ID REQUIRED FOR U.S. REGION
CORPORATE LARGE TICKET, FACE TO FACE, DATA
RATE II, OR DATA RATE III INTERCHANGE
PROGRAMS.
0947 PDS0595 CARD ACCEPTOR TYPE AND PDS0596 Both
MERCHANT TAX ID REQUIRED FOR U.S. REGION
CORPORATE LARGE TICKET, FACE TO FACE, DATA
RATE II, OR DATA RATE III INTERCHANGE
PROGRAMS.
2181 PDS0595 CARD ACCEPTOR TYPE MUST BE A FIXED Both
LENGTH OF 008.
PDS 0595, S1 2184 PDS0595S1 BUSINESS TYPE CANNOT BE ALL LOW- Both
PDS 0595, S2 2184 PDS0595S2 BUSINESS OWNER TYPE CANNOT BE ALL Both
PDS 0595, S3 2184 PDS0595S3 BUSINESS CERTIFICATION TYPE CANNOT Both
PDS 0595, S4 2184 PDS0595S4 BUSINESS RACIAL/ETHNIC TYPE CANNOT Both
PDS 0595, S5 2185 PDS0595S5 BUSINESS TYPE PROVIDED MUST BE 7, N Both
OR R.
PDS 0595, S6 2185 PDS0595S6 BUSINESS OWNER TYPE PROVIDED MUST Both
BE Y, N, OR R.
PDS 0595, S7 2185 PDS0595S7 BUSINESS CERTIFICATION TYPE PROVIDED Both
MUST BE Y, N, OR R.
PDS 0595, S8 2185 PDS0595S8 BUSINESS RACIAL/ETHNIC TYPE MUST BE Both
Y, N, OR R.


PDS 0596 0948 PDS0596 CARD ACCEPTOR TAX ID AND PDS0597 TAX Both
AMOUNT REQUIRED FOR THE INTERNATIONAL
CORPORATE PURCHASING DATA RATE II
1088 PDS0596 CARD ACCEPTOR TAX ID CANNOT CONTAIN Both
ALL SPACES FOR INTERNATIONAL CORPORATE
PURCHASING DATA RATE II INTERCHANGE
PROGRAMS.
1090 PDS0596 CARD ACCEPTOR TAX ID CANNOT CONTAIN Both
ALL ZEROS, ALL NINES, OR ALL SPACES FOR U.S.
REGION CORP. LARGE TICKET, FACE-TO-FACE, DATA
RATE II OR DATA RATE III INTERCHANGE PROGRAMS.
2181 PDS0596 CARD ACCEPTOR TAX ID MUST BE A FIXED Both
LENGTH OF 021.
2207 THE VALUE IN PDS0596 CARD ACCEPTOR TAX ID IS Both
CONTAINED IN A LIST OF INVALID VALUES FOR THIS
ELEMENT.
PDS 0596, s1 1088 PDS0596S1 CARD ACCEPTOR TAX ID CANNOT Both
CONTAIN ALL SPACES FOR INTERNATIONAL
1090 PDS0596S1 CARD ACCEPTOR TAX ID CANNOT Both
CONTAIN ALL ZEROS, ALL NINES, OR ALL SPACES FOR
U.S. REGION CORP. LARGE TICKET, FACE-TO-FACE,
DATA RATE II OR DATA RATE III INTERCHANGE.
2207 THE VALUE IN PDS 0595, S1 CARD ACCEPTOR TAX ID Both
IS CONTAINED IN A LIST OF INVALID VALUES FOR
THIS ELEMENT.
2257 PDS0596S1 CARD ACCEPTOR TAX ID MUST BE LEFT Both
JUSTIFIED, NON- ZERO AND CONTAIN 9 NUMERIC
CHARACTERS
PDS 0596, s2 2185 PDS0596S2 CARD ACCEPTOR TAX ID MUST BE Y, N, Both
OR R.


PDS 0597 0948 PDS0596 CARD ACCEPTOR TAX ID AND PDS0597 TAX Both
AMOUNT REQUIRED FOR THE INTERNATIONAL
1137 PDS0597 TOTAL TAX AMOUNT REQUIRED FOR U.S. Both
REGION CORPORATE LARGE TICKET, FACE TO FACE,
DATA RATE II, OR DATA RATE III INTERCHANGE
PROGRAMS.
2181 PDS0597 TOTAL TAX AMOUNT MUST BE A FIXED Both
LENGTH OF 014.
PDS 0597, s1 2183 PDS0597S1 TOTAL TAX AMOUNT MUST BE NUMERIC. Both
PDS 0597, s2 2183 PDS0597S2 TOTAL TAX AMOUNT EXPONENT MUST BE Both
NUMERIC.
2215 PDS0597S2 TOTAL TAX AMOUNT EXPONENT MUST Both
PDS 0597, s3 2185 PDS0597S3 TOTAL TAX AMOUNT SIGN MUST BE D OR Both
C.
PDS 0598 0277 PDS0598 TOTAL TAX COLLECTED INDICATOR MUST Both
BE Y, N, 0, OR A SPACE.
0883 PDS0598 TOTAL TAX COLLECTED INDICATOR MUST Both
2184 PDS0598 TOTAL TAX COLLECTED INDICATOR Both
PDS 0599 1081 PDS0599 CORPORATION VAT NUMBER MUST BE LEFT Both
2180 PDS0599 CORPORATION VAT NUMBER LENGTH MUST Both
BE 001–020.
2182 PDS0599 CORPORATION VAT NUMER MUST BE LEFT Both
ALL ZEROS.
2184 PDS0599 CORPORATION VAT NUMBER CANNOT BE Both


PDS 0600 0951 PDS0600 CARD ACCEPTOR REFERENCE NUMBER Both
2182 PDS0600 CARD ACCEPTOR REFERENCE NUMBER MUST Both
2184 PDS0600 CARD REFERENCE NUMBER CANNOT BE ALL Both
PDS 0601 2181 PDS0601 PARTY NATURE OF FILING MUST BE A FIXED Both
LENGTH 001.
2185 PDS0601 PARTY NATURE OF FILING MUST BE P, S, E, Both
OR N.
PDS 0602 2236 PDS0602 PARTY SUPPLEMENTAL DATA 1 LENGTH Both
MUST BE 084-672 AND MUST BE DIVISIBLE BY
MINIMUM OCCURRENCE LENGTH OF 084.
PDS 0602, s1 2182 PDS0602S1 PARTY SUPPLEMENTAL DATA Both
DESCRIPTION 1 MUST BE LEFT JUSTIFIED AND
2184 PDS0602S1 PARTY SUPPLEMENTAL DATA Both
DESCRIPTION 1 CANNOT BE ALL LOW-VALUES OR ALL
HIGH-VALUES.
PDS 0602, s2 2182 PDS0602S2 PARTY SUPPLEMENTAL DATA 1 MUST BE Both
OR ALL ZEROS.
2184 PDS0602S2 PARTY SUPPLEMENTAL DATA 1 CANNOT Both
PDS 0602, s3 2182 PDS0602S3 PARTY SUPPLEMENTAL DATA CODE 1 Both
2184 PDS0602S3 PARTY SUPPLEMENTAL DATA CODE 1 Both
PDS 0603 2236 PDS0603 PARTY SUPPLEMENTAL DATA 2 LENGTH Both


HIGH-VALUES.
PDS 0603, s2 2182 PDS0603S2 PARTY SUPPLEMENTAL DATA 2 MUST BE Both
OR ALL ZEROS.
2184 PDS0603S2 PARTY SUPPLEMENTAL DATA 2 CANNOT Both
PDS 0603, s3 2182 PDS0603S3 PARTY SUPPLEMENTAL DATA CODE 2 Both
2184 PDS0603S3 PARTY SUPPLEMENTAL DATA CODE 2 Both
PDS 0604 2236 PDS0604 TRANSACTION SUPPLEMENTAL DATA 1 Both
LENGTH MUST BE 084-672 AND MUST BE DIVISIBLE
BY MINIMUM OCCURRENCE LENGTH OF 084.
PDS 0604, s1 2182 PDS0604S1 TRANSACTION SUPPLEMENTAL DATA Both
2184 PDS0604S1 TRANSACTION SUPPLEMENTAL DATA Both
HIGH-VALUES.
PDS 0604, s2 2182 PDS0604S2 TRANSACTION SUPPLEMENTAL DATA 1 Both
2184 PDS0604S2 TRANSACTION SUPPLEMENTAL DATA 1 Both
CODE 1 MUST BE LEFT JUSTIFIED AND CANNOT
2184 PDS0604S3 TRANSACTION SUUPLEMENTAL DATA Both
CODE 1 CANNOT BE ALL LOW-VALUES OR ALL HIGH-
VALUES.
PDS 0605 2236 PDS0605 TRANSACTION SUPPLEMENTAL DATA 2 Both
LENGTH MUST BE 084-672 AND MUST BE DIVISIBLE
BY MINIMUM OCCURRENCE LENGTH OF 084.


HIGH-VALUES.
PDS 0605, s2 2182 PDS0605S2 TRANSACTION SUPPLEMENTAL DATA 2 Both
2184 PDS0605S2 TRANSACTION SUPPLEMENTAL DATA 2 Both
CODE 2 MUST BE LEFT JUSTIFIED AND CANNOT
CODE 2 CANNOT BE ALL LOW-VALUES OR ALL HIGH-
VALUES.
PDS 0606 2181 PDS0606 FREIGHT AMOUNT MUST BE A FIXED Both
LENGTH OF 014.
PDS 0606, s1 2183 PDS0606S1 FREIGHT AMOUNT MUST BE NUMERIC. Both
PDS 0606, s2 2183 PDS0606S2 FREIGHT AMOUNT EXPONENT MUST BE Both
NUMERIC.
2215 PDS0606S2 FREIGHT AMOUNT EXPONENT MUST Both
PDS 0606, s3 2185 PDS0606S3 FREIGHT AMOUNT SIGN MUST BE D OR C. Both
PDS 0607 0279 PDS0607 DUTY AMOUNT INVALID. MUST BE Both
NUMERIC.
2181 PDS0607 DUTY AMOUNT MUST BE A FIXED LENGTH Both
OF 014.
PDS 0607, s1 2183 PDS0607S1 DUTY AMOUNT MUST NUMERIC. Both
PDS 0607, s2 2183 PDS0607S2 DUTY AMOUNT EXPONENT MUST BE Both
NUMERIC.
2215 PDS607S2 DUTY AMOUNT EXPONENT MUST CONTAIN Both


PDS 0607, s3 2185 PDS0607S3 DUTY AMOUNT SIGN MUST BE D OR C. Both
PDS 0608 0280 PDS0608 DESTINATION POSTAL CODE MUST BE LEFT Both
0886 PDS0608 DESTINATION POSTAL CODE MUST BE A Both
2182 PDS0608 DESTINATION POSTAL CODE MUST BE LEFT Both
ALL ZEROS.
2184 PDS0608 DESTINATION POSTAL CODE CANNOT BE Both
2258 PDS0608 DESTINATION POSTAL CODE MUST BE Both
EITHER 5 NUMERIC CHARACTERS OR 9 NUMERIC
CHARACTERS WITH A HYPHEN BETWEEN THE 5TH
AND 6TH NUMERIC CHARACTER WITH TRAILING
SPACES
PDS 0609 0887 PDS0609 DESTINATION STATE/PROVINCE CODE MUST Both
0888 PDS0609 DESTINATION STATE/PROVINCE CODE Both
INVALID. MUST CONTAIN A VALID U.S. STATE CODE.
2182 PDS0609 DESTINATION STATE/PROVINCE MUST BE Both
OR ALL ZEROS.
2184 PDS0609 DESTINATION STATE/PROVINCE CANNOT BE Both
PDS 0610 0889 PDS0610 DESTINATION COUNTRY CODE MUST BE A Both
0890 DESTINATION COUNTRY CODE INVALID. MUST Both
CONTAIN A VALID COUNTRY CODE.
PDS 0612 2181 PDS0612 SHIP DATE MUST BE A FIXED LENGTH OF Both
006.
2183 PDS0612 SHIP DATE MUST BE NUMERIC. Both
2186 PDS0612 SHIP DATE MUST BE A VALID DATE IN THE Both
FORMAT YYMMDD.


PDS 0613 0893 PDS0613 SHIP-FROM POSTAL CODE MUST BE A FIXED Both
LENGTH OF 010.
2182 PDS0613 SHIP-FROM POSTAL CODE MUST BE LEFT Both
ALL ZEROS.
2184 PDS0613 SHIP-FROM POSTAL CODE CANNOT BE ALL Both
2258 PDS0613 SHIP FROM POSTAL CODE MUST BE IN THE Both
FORMAT OF EITHER NNNNN OR NNNNN-NNNN.
PDS 0614 0283 PDS0614 ORDER DATE MUST BE A VALID DATE IN Both
THE FORMAT YYMMDD.
0894 PDS0614 ORDER DATE LENGTH MUST BE A FIXED Both
LENGTH OF 6.
PDS 0615 2180 PDS0615 MEDICAL SERVICES SHIP TO HEALTH Both
INDUSTRY NUMBER LENGTH MUST BE 001 TO 040.
2182 PDS0615 MEDICAL SERVICES SHIP TO HEALTH Both
INDUSTRY NUMBER MUST BE LEFT JUSTIFIED AND
2184 PDS0615 MEDICAL SERVICES SHIP TO HEALTH Both
INDUSTRY NUMBER CANNOT BE ALL LOW-VALUES OR
ALL HIGH-VALUES.
PDS 0616 2180 PDS0616 CONTRACT NUMBER LENGTH MUST BE 001 Both
TO 040.
2182 PDS0616 CONTRACT NUMBER MUST BE LEFT Both
ALL ZEROS.
2184 PDS0616 CONTRACT NUMBER CANNOT BE ALL LOW- Both
PDS 0617 2181 PDS0617 MEDICAL SERVICES PRICE ADJUSTMENT Both
2185 PDS0617 MEDICAL SERVICES PRICE ADJUSTMENT Both
MUST BE A, B, C, OR D.


PDS 0618 2181 PDS0618 MEDICAL SERVICES PRODUCT NUMBER Both
QUALIFIER MUST BE A FIXED LENGTH OF 002.
2185 PDS0618 MEDICAL SERVICES PRODUCT NUMBER Both
QUALIFIER MUST BE 01, 02, OR 03.
PDS 0619 2180 PDS0619 USER NAME LENGTH MUST BE 001-040. Both
2182 PDS0619 USER NAME MUST BE LEFT JUSTIFIED AND Both
2184 PDS0619 USER NAME CANNOT BE ALL LOW-VALUES Both
OR ALL HIGH-VALUES.
PDS 0620 0329 PDS0620 OIL COMPANY BRAND NAME MUST BE Both
NUMERIC.
0348 PDS0620 OIL COMPANY BRAND NAME AND PDS0621 Both
PURCHASE TIME REQUIRED FOR FLEET CARD AT FUEL
LOCATION TRANSACTIONS SUBMITTED FOR THE U.S.
REGION CORPORATE DATA RATE I INTERCHANGE
PROGRAM.
0895 PDS0620 OIL COMPANY BRAND NAME MUST BE A Both
0953 PDS0620 OIL COMPANY BRAND NAME, PDS0621 Both
PURCHASE TIME, AND PDS0632 PRODUCT TYPE CODE
REQUIRED FOR FLEET CARD AT FUEL LOCATION
TRANSACTIONS SUBMITTED FOR THE U.S. REGION
CORPORATE LARGE TICKET OR DATA RATE II
PDS 0621 0330 PDS0621 PURCHASE TIME INVALID. MUST BE IN THE Both
FORMAT HHMM. HOURS MUST BE 00-23 AND
0896 PDS0621 PURCHASE TIME MUST BE A FIXED LENGTH Both
OF 004.
PDS 0622 0897 PDS0622 MOTOR FUEL SERVICE TYPE MUST BE A Both
PDS 0623 1034 PDS0623 MOTOR FUEL INFORMATION REQUIRED FOR Both
FLEET CARD AT FUEL LOCATION TRANS. SUBMITTED
FOR THE U.S.REGION CORP. LARGE TICKET, DATA
RATE I OR II INTERCHANGE PROGRAMS IN WHICH
PDS622 CONTAINS A VALUE OTHER THAN 3.


PDS 0623 2181 PDS0623 MOTOR FUEL INFORMATION MUST BE A Both
PDS 0623, s1 0332 PDS0623S1 MOTOR FUEL PRODUCT CODE MUST BE Both
NUMERIC.
0333 PDS0623S1 MOTOR FUEL PRODUCT CODE INVALID. Both
MUST BE 001-029 OR 100-299.
PDS 0623, s2 0339 PDS0623S2 MOTOR FUEL UNIT PRICE MUST BE Both
NUMERIC.
PDS 0623, s3 0337 PDS0623S3 MOTOR FUEL UNIT OF MEASURE MUST Both
CONTAIN A SPACE OR 1-5.
PDS 0623, s4 1054 PDS0623S4 MOTOR FUEL QUANTITY MUST BE Both
NUMERIC AND GREATER THAN ZERO.
PDS 0623, s5 0336 PDS0623S5 MOTOR FUEL QUANTITY EXPONENT MUST Both
BE 0-5.
PDS 0623, s6 0341 PDS0623S6 MOTOR FUEL SALE AMOUNT MUST BE Both
PDS 0624 2180 PDS0624 USER ACCOUNT NUMBER LENGTH MUST BE Both
001-040.
2182 PDS0624 USER ACCOUNT NUMBER MUST BE LEFT Both
ALL ZEROS.
2184 PDS0624 USER ACCOUNT NUMBER CANNOT BE ALL Both
PDS 0625 2180 PDS0625 USER TELEPHONE NUMBER LENGTH MUST Both
BE 001-025.
2182 PDS0625 USER TELEPHONE NUMBER MUST BE LEFT Both
ALL ZEROS.
2184 PDS0625 USER TELEPHONE NUMBER CANNOT BE ALL Both
PDS 0626 2181 PDS0626 BILLING STATEMENT PERIOD MUST BE A Both
PDS 0626, s1 2183 PDS0626S1 STATEMENT START DATE MUST BE Both
NUMERIC.
2186 PDS0626S1 STATEMENT START DATE MUST BE A Both


PDS 0626, s2 2183 PDS0626S2 STATEMENT END DATE MUST BE Both
NUMERIC.
2186 PDS0626S2 STATEMENT END DATE MUST BE A VALID Both
PDS 0627 2236 PDS0627 BILLING EVENT 1 LENGTH MUST BE 54-540 Both
LENGTH OF 054.
PDS 0627, s1 2183 PDS0627S1 BILLING EVENT 1 AMOUNT MUST BE Both
NUMERIC.
PDS 0627, s2 2183 PDS0627S2 BILLING EVENT EXPONENT 1 MUST BE Both
NUMERIC.
2215 PDS0627S2 BILLING EVENT EXPONENT 1 MUST Both
PDS 0627, s3 2185 PDS0627S3 BILLING EVENT SIGN 1 MUST BE D OR C. Both
PDS 0627, s4 2182 PDS0627S4 BILLING EVENT DESCRIPTION 1 MUST BE Both
OR ALL ZEROS.
2184 PDS 627S4 BILLING EVENT DESCRIPTION 1 CANNOT Both
PDS 0628 2236 PDS0628 BILLING EVENT 2 LENGTH MUST BE 54-540 Both
LENGTH OF 054.
PDS 0628, s1 2183 PDS0628S1 BILLING EVENT AMOUNT 2 MUST BE Both
NUMERIC.
PDS 0628, s2 2183 PDS0628S2 BILLING EVENT EXPONENT 2 MUST BE Both
NUMERIC.
2215 PDS0628S2 BILLING EVENT EXPONENT 2 MUST Both
PDS 0628, s3 2185 PDS0628S3 BILLING EVENT SIGN 2 MUST BE D OR C. Both
PDS 0628, s4 2182 PDS0628S4 BILLING EVENT DESCRIPTION 2 MUST BE Both
OR ALL ZEROS.
2184 PDS0628S4 BILLING EVENT DESCRIPTION 2 CANNOT Both


PDS 0629 0343 PDS0629 ODOMETER READING MUST BE NUMERIC IF Both
PDS0632 IS 1–4 AND IT IS FLEET AT FUEL SUBMITTED
FOR U.S. REGION CORP. LARGE TICKET OR DATA
RATE II.
0960 PDS0629 ODOMETER READING LENGTH MUST BE 1-7. Both
2182 PDS0629 ODOMETER READING MUST BE LEFT Both
ALL ZEROS.
2184 PDS0629 ODOMETER READING CANNOT BE ALL LOW- Both
PDS 0630 0345 PDS0630 VEHICLE NUMBER MUST BE PRESENT IF Both
PDS0632 IS ‘2’, PDS 0631 IS NOT PRESENT, AND IT IS
FLEET AT FUEL SUBMITTED FOR INTERCHANGE 62 OR
67.
0961 PDS0630 VEHICLE NUMBER LENGTH MUST BE 1-17. Both
2182 PDS0630 VEHICLE NUMBER MUST BE LEFT JUSTIFIED Both
2184 PDS0630 VEHICLE NUMER CANNOT BE ALL LOW- Both
PDS 0631 0347 PDS0631 DRIVER NUMBER/ID NUMBER MUST BE Both
NUMERIC IF PDS0632 IS ‘1’ OR ‘3’ AND IT IS FLEET AT
FUEL SUBMITTED FOR U.S. REGION CORP. LARGE
TICKET OR DATA RATE II.
0962 PDS0631 DRIVER NUMBER/ID NUMBER LENGTH MUST Both
BE 1-17.
2182 PDS0631 DRIVER NUMBER/ID NUMBER MUST BE LEFT Both
ALL ZEROS.
2184 PDS0631 DRIVER NUMBER/ID NUMBER CANNOT BE Both
PDS 0632 0903 PDS0632 PRODUCT TYPE CODE MUST BE A FIXED Both
LENGTH OF 001.
1089 PDS0632 PRODUCT TYPE CODE INVALID. SHOULD BE Both
1-5.


PDS 0633 0349 PDS0633 COUPON/DISCOUNT AMOUNT MUST BE Both
NUMERIC.
0904 PDS0633 COUPON/DISCOUNT AMOUNT MUST BE A Both
PDS 0634 0905 PDS0634 TAX AMOUNT 1 MUST BE A FIXED LENGTH Both
OF 006.
2183 PDS0634 TAX AMOUNT 1 MUST BE NUMERIC Both
PDS 0635 0906 PDS0635 TAX AMOUNT 2 MUST BE A FIXED LENGTH Both
OF 006.
2183 PDS0635 TAX AMOUNT 2 MUST BE NUMERIC. Both
PDS 0636 2181 PDS0636 CALL DATE MUST BE A FIXED LENGTH OF Both
006.
2183 PDS0636 CALL DATE MUST BE NUMERIC Both
2186 PDS0636 CALL DATE MUST BE A VALID DATE IN THE Both
FORMAT YYMMDD.
PDS 0637 2181 PDS0637 CALL TIME MUST BE A FIXED LENGTH OF Both
006.
2183 PDS0637 CALL TIME MUST BE NUMERIC Both
2238 PDS0637 CALL TIME MUST BE A VALID TIME IN THE Both
FORMAT HHMMSS.
PDS 0638 2181 PDS0638 CALL TO INFORMATION MUST BE A FIXED Both
LENGTH OF 146.
PDS 0638, s1 2182 PDS0638S1CALL TO CITY MUST BE LEFT JUSTIFIED Both
2184 PDS 638S1 CALL TO CITY CANNOT BE ALL LOW- Both
PDS 0638, s2 2182 PDS0638S2 CALL TO STATE/PROVINCE MUST BE LEFT Both
ALL ZEROS.
2184 PDS0638S2 CALL TO STATE/PROVINCE CANNOT BE Both
PDS 0638, s3 2182 PDS0638S3 CALL TO COUNTRY MUST BE LEFT Both
ALL ZEROS.


PDS 0638, s3 2184 PDS0638S3 CALL TO COUNTRY CANNOT BE ALL LOW- Both
PDS 0638, s4 2182 PDS0638S4 CALL TO NUMBER MUST BE LEFT Both
ALL ZEROS.
2184 PDS0638S4 CALL TO NUMBER CANNOT BE ALL LOW- Both
VALUES OR ALL HIGH-VALUES
2259 PDS0638S4 CALL TO NUMBER MUST CONTAIN 10 Both
PDS 0638, s5 2185 PDS0638S5 CALL TO TYPE MUST BE C, I, V, P, O, OR F. Both
PDS 0639 2181 PDS0639 CALL DURATION MUST BE A FIXED LENGTH Both
OF 006.
2183 PDS0639 CALL DURATION MUST BE NUMERIC Both
PDS 0640 2181 PDS0640 CALL TIME PERIOD MUST BE A FIXED Both
LENGTH OF 002.
2185 PDS0640 CALL TIME PERIOD MUST BE PP, OP, MP OR Both
OT.
PDS 0641 0285 PDS0641 PRODUCT CODE MUST CONTAIN A VALUE IN Both
THE RANGE 030-099 OR 300-999 IF TRANSACTION IS A
FLEET CARD AT A FUEL LOCATION SUBMITTED FOR
THE U.S. REGION CORPORATE DATA RATE III
0963 PDS0641 PRODUCT CODE LENGTH MUST BE 1-15. Both
2185 PDS0641 PRODUCT CODE MUST BE L-1000, L-1020, Both
L-1021, L-1100, L-1101, L-1102, L-1103, L-1104, L-1105,
L-1106, L-1107, L-1108, L-1109, L-1110, L-1111, L-1112,
L-1113, L-1114, L-1115, L-1116, L-1117, L-1118, 1-1119,
L-1120, L-1121, L-1122, L-9999.
2195 PDS0641 PRODUCT CODE MUST BE PRESENT IN A Both
LINE ITEM DETAIL ADDENDUM MESSAGE.
2200 PDS0641 PRODUCT CODE CANNOT BE ALL ZEROS OR Both
ALL SPACES.


PDS 0642 0286 PDS0642 ITEM DESCRIPTION MUST BE LEFT JUSTIFIED Both
0964 PDS0642 ITEM DESCRIPTION LENGTH MUST BE 1-35. Both
2184 PDS0642 ITEM DESCRIPTION CANNOT BE ALL LOW- Both
2195 PDS0642 ITEM DESCRIPTION MUST BE PRESENT IN A Both
2200 PDS0642 ITEM DESCRIPTION CANNOT BE ALL ZEROS Both
OR ALL SPACES.
PDS 0643 0907 PDS0643 ITEM QUANTITY MUST BE A FIXED LENGTH Both
OF 013.
2195 PDS0643 ITEM QUANTITY MUST BE PRESENT IN A Both
PDS 0643, s1 2208 PDS0643S1 ITEM QUANTITY CANNOT CONTAIN ALL Both
2232 PDS0643S1 ITEM QUANITY MUST BE NUMERIC AND Both
GREATER THAN ZERO.
PDS 0643, s2 0288 PDS0643S2 ITEM QUANTITY EXPONENT MUST BE Both
NUMERIC.
2215 PDS0643S2 ITEM QUANTITY EXPONENT MUST Both
CONTAIN A VALUE WITHIN THE RANGE OF 0-5.
PDS 0644 2181 PDS0644 CALL FROM INFORMATION MUST BE A FIXED Both
LENGTH OF 145.
PDS 0644, s1 2182 PDS0644S1 CALL FROM CITY MUST BE LEFT JUSTIFIED Both
2184 PDS0644S1 CALL FROM CITY CANNOT BE ALL LOW- Both
PDS 0644, s2 2182 PDS0644S2 CALL FROM STATE/PROVINCE MUST BE Both
OR ALL ZEROS.
2184 PDS0644S2 CALL FROM STATE/PROVINCE CANNOT BE Both


PDS 0644, s3 2182 PDS0644S3 CALL FROM COUNTRY MUST BE LEFT Both
ALL ZEROS.
2184 PDS0644S3 CALL FROM COUNTRY CANNOT BE ALL Both
PDS 0644, s4 2182 PDS0644S4 CALL FROM NUMBER MUST BE LEFT Both
ALL ZEROS.
2184 PDS0644S4 CALL FROM NUMBER CANNOT BE ALL Both
2259 PDS0644S4 CALL FROM NUMBER MUST CONTAIN 10 Both
PDS 0645 0965 PDS0645 ITEM UNIT OF MEASURE LENGTH MUST BE Both
1-12.
2184 PDS0645 ITEM UNIT OF MEASURE CANNOT BE ALL Both
2195 PDS0645 ITEM UNIT OF MEASURE MUST BE PRESENT Both
IN A LINE ITEM DETAIL ADDENDUM MESSAGE.
2208 PDS0645 ITEM UNIT OF MEASURE CANNOT BE ALL Both
PDS 0646 0908 PDS0646 UNIT PRICE MUST BE A FIXED LENGTH OF Both
013.
PDS 0646, s1 2183 PDS0646S1 UNIT PRICE MUST BE NUMERIC. Both
PDS 0646, s2 2215 PDS0646S2 UNIT PRICE EXPONENT MUST CONTAIN A Both
VALUE WITHIN THE RANGE OF 0-5.
PDS 0647 2181 PDS0647 EXTENDED ITEM AMOUNT MUST BE A FIXED Both
LENGTH OF 014.
2195 PDS0647 EXTENDED ITEM AMOUNT MUST BE Both
PRESENT IN A LINE ITEM DETAIL ADDENDUM
MESSAGE.
2208 PDS0647 EXTENDED ITEM AMOUNT CANNOT BE ALL Both


PDS 0647, s1 2232 PDS0647S1 EXTENDED ITEM AMOUNT MUST BE Both
PDS 0647, s2 2183 PDS0647S2 EXTENDED ITEM AMOUNT EXPONENT Both
MUST BE NUMERIC.
2215 PDS0647S2 EXTENDED ITEM AMOUNT EXPONENT Both
5.
PDS 0647, s3 2185 PDS0647S3 EXTENDED ITEM AMOUNT SIGN MUST BE Both
D OR C.
PDS 0648 2181 PDS0648 ITEM DISCOUNT MUST BE A FIXED LENGTH Both
OF 020.
PDS 0648, s1 0292 PDS0648S1 DISCOUNT INDICATOR MUST BE Y OR N Both
OR A SPACE.
PDS 0648, s2 0293 PDS0648S2 ITEM DISCOUNT MUST BE NUMERIC. Both
0966 PDS0648S2 DISCOUNT AMOUNT CANNOT EQUAL ALL Both
ZEROS IF PDS0648S1 DISCOUNT INDICATOR IS EQUAL
TO “Y”.
PDS 0648, s3 2183 PDS0648S3 ITEM DISCOUNT RATE MUST BE NUMERIC. Both
PDS 0648, s4 2183 PDS0648S4 ITEM DISCOUNT RATE EXPONENT MUST Both
BE NUMERIC.
2215 PDS0648S4 ITEM DISCOUNT RATE EXPONENT MUST Both
PDS 0648, s5 2185 PDS0648S5 ITEM DISCOUNT AMOUNT SIGN MUST BE Both
D OR C.
PDS 0649 2181 PDS0649 CALL USAGE AMOUNT MUST BE A FIXED Both
LENGTH OF 014.
PDS 0649, s1 2183 PDS0649S1 CALL USAGE AMOUNT MUST BE NUMERIC. Both
PDS 0649, s2 2183 PDS0649S2 CALL USAGE AMOUNT EXPONENT MUST Both
BE NUMERIC.
2215 PDS0649S2 CALL USAGE AMOUNT EXPONENT MUST Both
PDS 0649, s3 2185 PDS0649S3 CALL USAGE AMOUNT SIGN MUST BE D Both
OR C.


PDS 0654 0295 PDS0654 DEBIT OR CREDIT INDICATOR MUST BE D Both
OR C.
0296 PDS0654 DEBIT OR CREDIT INDICATOR MUST BE ‘C’ Both
OR ‘D’ IF PDS0647 EXTENDED ITEM AMOUNT IS
GREATER THAN ZERO.
2195 PDS0654 DEBIT OR CREDIT INDICATOR MUST BE Both
PRESENT IN A LINE ITEM DETAIL ADDENDUM
MESSAGE.
PDS 0655 2181 PDS0655 CALL LONG DISTANCE AMOUNT MUST BE A Both
PDS 0655, s1 2183 PDS0655S1 CALL LONG DISTANCE AMOUNT MUST BE Both
NUMERIC.
PDS 0655, s2 2183 PDS0655S2 CALL LONG DISTANCE AMOUNT Both
2215 PDS0655S2 CALL LONG DISTANCE AMOUNT Both
RANGE OF 0–5.
PDS 0655, s3 2185 PDS0655S3 CALL LONG DISTANCE AMOUNT SIGN Both
MUST BE D OR C.
PDS 0658 2181 PDS0658 CALL CONNECT AMOUNT MUST BE A FIXED Both
LENGTH OF 014.
PDS 0658, s1 2183 PDS0658S1CALL CONNECT AMOUNT MUST BE Both
NUMERIC.
PDS 0658, s2 2183 PDS0658S2 CALL CONNECT AMOUNT EXPONENT Both
MUST BE NUMERIC.
2215 PDS0658S2 CALL CONNECT AMOUNT EXPONENT Both
0–5.
PDS 0658, s3 2185 PDS0658S3 CALL CONNECT AMOUNT SIGN MUST BE D Both
OR C.
PDS 0659 2180 PDS0659 OTHER DESCRIPTION LENGTH MUST BE 001- Both
060.
2182 PDS0659 OTHER DESCRIPTION MUST BE LEFT Both
ALL ZEROS.


PDS 0659 2184 PDS0659 OTHER DESCRIPTION MUST BE LEFT Both
JUSTIFIED AND CANNOT BE ALL LOW-VALUES OR ALL
HIGH-VALUES.
PDS 0663 0967 PDS0663 FREE-FORM DESCRIPTION LENGTH MUST BE Both
001-992.
0983 PDS0663 FREE-FORM DESCRIPTION CANNOT BE ALL Both
SPACES.
2182 PDS0663 FREE-FORM DESCRIPTION MUST BE LEFT Both
ALL ZEROS.
2184 PDS0663 FREE-FORM DESCRIPTION CANNOT BE ALL Both
2264 PDS0663 FREE-FORM DESCRIPTION MUST BE PRESENT Both
PDS 0670 2024 PDS0670 PAYER NAME OR USER ID MUST BE LEFT Both
2025 PDS0670 PAYER NAME OR USER ID LENGTH MUST BE Both
1–24.
PDS 0671 2026 PDS0671 DATE OF FUNDS REQUESTED MUST BE A Both
2027 PDS0671 DATE OF FUNDS REQUESTED MUST BE A Both
PDS 0672 2028 PDS0672 RECIPIENT NAME (SELLER) MUST BE LEFT Both
2029 PDS0672 RECIPIENT NAME (SELLER) LENGTH MUST BE Both
1–24.
PDS 0673 2030 PDS0673 DATE OF ANTICIPATED RECEIPT OF FUNDS Both
MUST BE A VALID DATE IN THE FORMAT YYMMDD.
2031 PDS0673 DATE OF ANTICIPATED RECEIPT OF FUNDS Both
PDS 0674 2032 PDS0674 ADDITIONAL TRACE/REFERENCE NUMBER Both
USED BY CARD ACCEPTOR MUST BE LEFT JUSTIFIED
2033 PDS0674 ADDITIONAL TRACE/REFERENCE NUMBER Both
USED BY CARD ACCEPTOR LENGTH MUST BE 1–15.


PDS 0675 2034 PDS0675 ADDITIONAL TRANSACTION DESCRIPTION Both
DATA MUST BE LEFT JUSTIFIED AND CANNOT
CONTAIN ALL SPACES.
2163 PDS0675 ADDITIONAL TRANSACTION DESCRIPTION Both
DATA LENGTH MUST BE 1–15.
PDS 0676 2035 PDS0676 CARD ACCEPTOR VAT NUMBER LENGTH Both
MUST BE 1–20.
2036 PDS0676 CARD ACCEPTOR VAT NUMBER MUST BE Both
PDS 0677 2037 PDS0677 CUSTOMER VAT NUMBER LENGTH MUST BE Both
1–20.
2038 PDS0677 CUSTOMER VAT NUMBER MUST BE LEFT Both
PDS 0678 2039 PDS0678 UNIQUE INVOICE NUMBER LENGTH MUST Both
BE 1–17.
2040 PDS0678 UNIQUE INVOICE NUMBER MUST BE LEFT Both
PDS 0679 2041 PDS0679 COMMODITY CODE LENGTH MUST BE 1–15. Both
2042 PDS0679 COMMODITY CODE MUST BE LEFT Both
PDS 0680 2043 PDS0680 AUTHORIZED CONTACT NAME LENGTH Both
MUST BE 1–36.
2044 PDS0680 AUTHORIZED CONTACT NAME MUST BE Both
PDS 0681 2045 PDS0681 AUTHORIZED CONTACT PHONE LENGTH Both
MUST BE 1–17.
2046 PDS0681 AUTHORIZED CONTACT PHONE MUST BE Both
PDS 0682 2180 PDS0682 DETAIL TAX AMOUNT 1 LENGTH MUST BE Both
001-046.
PDS 0682, s1 2048 PDS0682S1 DETAIL TAX AMOUNT INDICATOR 1 MUST Both
BE Y, N, OR SPACE.
PDS 0682, s2 2049 PDS0682S2 DETAIL TAX AMOUNT 1 INVALID. MUST BE Both
NUMERIC.


PDS 0682, s3 2050 PDS0682S3 DETAIL TAX RATE 1 INVALID. MUST BE Both
NUMERIC.
PDS 0682, s4 2051 PDS0682S4 DETAIL TAX RATE EXPONENT 1 MUST BE Both
0–5.
PDS 0682, s6 2052 PDS0682S6 DETAIL TAX TYPE IDENTIFIER 1 MUST BE Both
00, 01, 02, 03, 04, 05, 06, 10, 11, 12, 20, 21, 22, OR
SPACES.
PDS 0682, s7 2181 PDS0682S7 CARD ACCEPTOR TAX ID 1 MUST BE A Both
2184 PDS0682S7 CARD ACCEPTOR TAX ID 1 CANNOT BE Both
2257 PDS0682S7 TAX AMOUNT 1, TAX ID MUST BE LEFT Both
CHARACTERS
PDS 0682, s8 2185 PDS0682S8 DETAIL TAX AMOUNT SIGN 1 MUST BE D Both
OR C.
001-046.
BE Y, N, OR SPACE.
PDS 0683, s2 2055 PDS0683S2 DETAIL TAX AMOUNT 2 INVALID. MUST Both
BE NUMERIC.
NUMERIC.
0–5.
00, 01, 02, 03, 04, 05, 06, 10, 11, 12, 20, 21, 22, OR
SPACES.


CHARACTERS
PDS 0683, s8 2185 PDS0683S8 DETAIL TAX AMOUNT SIGN2 MUST BE D Both
OR C.
001-046.
BE Y, N, OR SPACE.
PDS 0684, s2 2061 PDS0684S2 DETAIL TAX AMOUNT 3 INVALID. MUST Both
BE NUMERIC.
NUMERIC.
0–5.
00, 01, 02, 03, 04, 05, 06, 10, 11, 12, 20, 21, 22, OR
SPACES.
CHARACTERS
OR C.


PDS 0685 2065 PDS0685 TYPE OF SUPPLY MUST BE A FIXED LENGTH Both
OF 002.
2066 PDS0685 TYPE OF SUPPLY MUST BE 00 OR 01. Both
PDS 0686 2067 PDS0686 TAX EXEMPT INDICATOR MUST BE A FIXED Both
LENGTH OF 001.
2068 PDS0686 TAX EXEMPT INDICATOR MUST BE 0 OR 1. Both
2189 PDS0686 TAX EXEMPT INDICATOR REQUIRED FOR Both
T&E III.
PDS 0687 2069 PDS0687 UNIQUE VAT INVOICE REFERENCE NUMBER Both
2070 PDS0687 UNIQUE VAT INVOICE REFERENCE NUMBER Both
SPACES.
PDS 0689 2073 PDS0689 CORPORATE IDENTIFIER LENGTH MUST BE Both
1–12.
PDS 0690 2074 PDS0690 NO SHOW INDICATOR MUST BE A FIXED Both
LENGTH OF 001.
2075 PDS0690 NO SHOW INDICATOR MUST BE 0 OR 1. Both
PDS 0691 2076 PDS0691 DAYS RENTED MUST BE A FIXED LENGTH OF Both
004.
2077 PDS0691 DAYS RENTED MUST BE NUMERIC. Both
2189 PDS0691 DAYS RENTED REQUIRED FOR VEHICLE Both
PDS 0692 2078 PDS0692 WEEKLY RENTAL AMOUNT MUST BE A FIXED Both
LENGTH OF 012.
2079 PDS0692 WEEKLY RENTAL AMOUNT MUST BE Both
NUMERIC.
PDS 0693 2181 PDS0693 TOTAL AUTHORIZED AMOUNT MUST BE A Both
PDS 0693, s1 2183 PDS0693S1 TOTAL AUTHORIZED AMOUNT MUST BE Both
NUMERIC.


PDS 0693, s2 2183 PDS0693S2 TOTAL AUTHORIZED AMOUNT EXPONENT Both
MUST BE NUMERIC.
2215 PDS0693S2 TOTAL AUTHORIZED AMOUNT EXPONENT Both
0–5.
PDS 0693, s3 2185 PDS0693S3 TOTAL AUTHORIZED AMOUNT SIGN MUST Both
BE D OR C.
PDS 0694 2082 PDS0694 ONE WAY DROP OFF CHARGE MUST BE A Both
2083 PDS0694 ONE WAY DROP OFF CHARGE MUST BE Both
NUMERIC.
PDS 0695 2084 PDS0695 REGULAR MILEAGE CHARGE MUST BE A Both
2085 PDS0695 REGULAR MILEAGE CHARGE MUST BE Both
NUMERIC.
PDS 0696 2086 PDS0696 EXTRA MILEAGE CHARGE MUST BE A FIXED Both
LENGTH OF 012.
2087 PDS0696 EXTRA MILEAGE CHARGE MUST BE Both
NUMERIC.
PDS 0697 2088 PDS0697 LATE CHARGE MUST BE A FIXED LENGTH OF Both
012.
2089 PDS0697 LATE CHARGE MUST BE NUMERIC. Both
PDS 0698 2090 PDS0698 FUEL CHARGE MUST BE A FIXED LENGTH OF Both
012.
2091 PDS0698 FUEL CHARGE MUST BE NUMERIC. Both
PDS 0699 2181 PDS0699 LODGING TOTAL TAX AMOUNT MUST BE A Both
PDS 0699, s1 2183 PDS0699S1 LODGING TOTAL TAX AMOUNT MUST BE Both
NUMERIC.
PDS 0699, s2 2183 PDS0699S2 LODGING TOTAL TAX AMOUNT Both
2215 PDS0699S2 LODGING TOTAL TAX AMOUNT Both
RANGE OF 0–5.


PDS 0699, s3 2185 PDS0699S3 LODGING TOTAL AMOUNT SIGN MUST BE Both
D OR C.
PDS 0700 2094 PDS0700 TOWING CHARGES MUST BE A FIXED Both
LENGTH OF 012.
2095 PDS0700 TOWING CHARGES MUST BE NUMERIC. Both
PDS 0701 2096 PDS0701 EXTRA CHARGES MUST BE A FIXED LENGTH Both
OF 012.
2097 PDS0701 EXTRA CHARGES MUST BE NUMERIC. Both
PDS 0702 2098 PDS0702 OTHER CHARGES MUST BE A FIXED LENGTH Both
OF 012.
2099 PDS0702 OTHER CHARGES MUST BE NUMERIC. Both
PDS 0703 2100 PDS0703 TOTAL ROOM NIGHTS MUST BE A FIXED Both
LENGTH OF 004.
2101 PDS0703 TOTAL ROOM NIGHTS MUST BE NUMERIC. Both
2190 PDS0703 TOTAL ROOM NIGHTS REQUIRED FOR Both
PDS 0704 2103 PDS0704 PREPAID EXPENSES MUST BE NUMERIC. Both
2181 PDS0704 PREPAID EXPENSES MUST BE A FIXED Both
LENGTH OF 014.
PDS 0704, s1 2183 PDS0704S1 PREPAID EXPENSES AMOUNT MUST BE Both
NUMERIC.
PDS 0704, s2 2183 PDS0704S2 PREPAID EXPENSES AMOUNT EXPONENT Both
MUST BE NUMERIC.
2215 PDS07042S2 PREPAID EXPENSES AMOUNT EXPONENT Both
5.
PDS 0704, s3 2185 PDS0704S3 PREPAID EXPENSE AMOUNT SIGN MUST Both
BE D OR C.
PDS 0705 2181 PDS0705 TOTAL NON-ROOM TAX AMOUNT MUST BE Both
A FIXED LENGTH
OF 014.
PDS 0705, s1 2183 PDS0705S1 TOTAL NON-ROOM TAX AMOUNT MUST Both
BE NUMERIC.
PDS 0705, s2 2183 PDS0705S2 TOTAL NON-ROOM TAX AMOUNT Both


PDS 0705, s2 2215 PDS0705S2TOTAL NON-ROOM TAX AMOUNT Both
RANGE 0–5.
PDS 0705, s3 2185 PDS0705S3 TOTAL NON-ROOM TAX AMOUNT SIGN Both
MUST BE D OR C.
PDS 0706 2181 PDS0706 CASH ADVANCES MUST BE A FIXED LENGTH Both
OF 014.
PDS 0706, s1 2183 PDS0706S1 CASH ADVANCE AMOUNT MUST BE Both
NUMERIC.
PDS 0706, s2 2183 PDS0706S2 CASH ADVANCE EXPONENT MUST BE Both
NUMERIC.
2215 PDS0706S2 CASH ADVANCE EXPONENT MUST Both
PDS 0706, s3 2185 PDS0706S3 CASH ADVANCE SIGN MUST BE D OR C. Both
PDS 0707 2181 PDS0707 VALET CHARGES MUST BE A FIXED LENGTH Both
OF 014.
PDS 0707, s1 2183 PDS0707S1 VALET CHARGES AMOUNT MUST BE Both
NUMERIC.
PDS 0707, s2 2183 PDS0707S2 VALET CHARGES EXPONENT MUST BE Both
NUMERIC.
2215 PDS0707S2 VALET CHARGES EXPONENT MUST Both
PDS 0707, s3 2185 PDS0707S3 VALET CHARGES SIGN MUST BE D OR C. Both
PDS 0708 2181 PDS0708 MOVIE CHARGES MUST BE A FIXED LENGTH Both
OF 014.
PDS 0708, s1 2183 PDS0708S1 MOVIE CHARGES AMOUNT MUST BE Both
NUMERIC.
PDS 0708, s2 2183 PDS0708S2 MOVIE CHARGES EXPONENT MUST BE Both
NUMERIC.
2215 PDS0708S2 MOVIE CHARGES EXPONENT MUST Both
PDS 0708, s3 2185 PDS0708S3 MOVIE CHARGES SIGN MUST BE D OR C. Both


PDS 0709 2181 PDS0709 BUSINESS CENTER CHARGES MUST BE A Both
PDS 0709, s1 2183 PDS0709S1 BUSINESS CENTER CHARGES AMOUNT Both
MUST BE NUMERIC.
PDS 0709, s2 2183 PDS0709S2 BUSINESS CENTER CHARGES EXPONENT Both
MUST BE NUMERIC.
2215 PDS0709S2 BUSINESS CENTER CHARGES EXPONENT Both
MUST CONTAIN A VALUE WITHIN THE RANGE 0–5.
PDS 0709, s3 2185 PDS0709S3 BUSINESS CENTER CHARGES SIGN MUST Both
BE D OR C.
PDS 0710 2181 PDS0710 HEALTH CLUB CHARGES MUST BE A FIXED Both
LENGTH OF 014.
PDS 0710, s1 2183 PDS0710S1 HEALTH CLUB CHARGES AMOUNT MUST Both
BE NUMERIC.
PDS 0710, s2 2183 PDS0710S2 HEALTH CLUB CHARGES EXPONENT MUST Both
BE NUMERIC.
2215 PDS0710S2 HEALTH CLUB CHARGES EXPONENT MUST Both
PDS 0710, s3 2185 PDS0710S3 HEALTH CLUB CHARGES SIGN MUST BE D Both
OR C.
PDS 0711 2116 PDS0711 FIRE SAFETY ACT INDICATOR MUST BE A Both
2117 PDS0711 FIRE SAFETY ACT INDICATOR MUST BE Y OR Both
N.
2190 PDS0711 FIRE SAFETY ACT INDICATOR REQUIRED Both
FOR LODGING TRANSACTIONS SUBMITTED FOR T&E
III.
PDS 0712 2118 PDS0712 NET FUEL PRICE MUST BE A FIXED LENGTH Both
OF 013.
PDS 0712, s1 2119 PDS0712S1 NET FUEL PRICE MUST BE NUMERIC. Both
PDS 0712, s2 2120 PDS0712S2 NET FUEL PRICE EXPONENT MUST BE 0–5. Both
PDS 0713 2121 PDS0713 RESTRICTED TICKET INDICATOR MUST BE A Both
2122 PDS0713 RESTRICTED TICKET INDICATOR MUST BE 0 Both
OR 1.


PDS 0714 2123 PDS0714 EXCHANGE TICKET AMOUNT MUST BE A Both
2124 PDS0714 EXCHANGE TICKET AMOUNT MUST BE Both
NUMERIC.
PDS 0715 2125 PDS0715 EXCHANGE FEE AMOUNT MUST BE A FIXED Both
LENGTH OF 012.
2126 PDS0715 EXCHANGE FEE AMOUNT MUST BE Both
NUMERIC.
PDS 0716 2127 PDS0716 TRAVEL AUTHORIZATION CODE LENGTH Both
MUST BE 1–64.
2128 PDS0716 TRAVEL AUTHORIZATION CODE MUST BE Both
PDS 0717 2129 PDS0717 IATA CLIENT CODE LENGTH MUST BE 1–17. Both
2130 PDS0717 IATA CLIENT CODE MUST BE LEFT JUSTIFIED Both
PDS 0718 2180 PDS 0718 EMPLOYEE TEMP NAME/ID LENGTH MUST Both
BE 001-040.
2182 PDS 0718 EMPLOYEE TEMP NAME/ID MUST BE LEFT Both
ALL ZEROS.
PDS 0719 2180 PDS0719 EMPLOYEE SOCIAL SECURITY NUMBER OR Both
ID LENGTH MUST BE 001-030.
2182 PDS0719 EMPLOYEE SOCIAL SECURITY NUMBER OR Both
ID MUST BE LEFT JUSTIFIED AND CANNOT CONTAIN
PDS 0720 2180 PDS0720 JOB DESCRIPTION LENGTH MUST BE 001-040. Both
2182 PDS0720 JOB DESCRIPTION MUST BE LEFT JUSTIFIED Both
PDS 0721 2180 PDS0721 JOB CODE LENGTH MUST BE 001-020. Both
2182 PDS0721 JOB CODE MUST BE LEFT JUSTIFIED AND Both
PDS 0722 2181 PDS0722 FLAT RATE INDICATOR MUST BE A FIXED Both
LENGTH OF 001.
2185 PDS0722 FLAT RATE INDICATOR MUST BE Y OR N. Both


PDS 0723 2181 PDS0723 REGULAR HOURS WORKED MUST BE A Both
2183 PDS0723 REGULAR HOURS WORKED MUST BE Both
NUMERIC.
PDS 0723, s2 2215 PDS0723S2 REGULAR HOURS WORKED EXPONENT Both
MUST CONTAIN A VALUE WITHIN THE RANGE OF 0–5.
PDS 0724 2181 PDS0724 REGULAR HOURS RATE MUST BE A FIXED Both
LENGTH OF 007.
2183 PDS0724 REGULAR HOURS RATE MUST BE NUMERIC. Both
PDS 0724, s2 2215 PDS0724S2 REGULAR HOURS RATE EXPONENT MUST Both
PDS 0725 2181 PDS0725 OVERTIME HOURS WORKED MUST BE FIXED Both
LENGTH OF 007.
2183 PDS0725 OVERTIME HOURS WORKED MUST BE Both
NUMERIC.
PDS 0725, s2 2215 PDS0725S2 OVERTIME HOURS WORKED EXPONENT Both
MUST CONTAIN A VALUE WITHIN THE RANGE OF 0–5.
PDS 0726 2181 PDS0726 OVERTIME HOURS RATE MUST BE A FIXED Both
LENGTH OF 007.
2183 PDS0726 OVERTIME HOURS RATE MUST BE NUMERIC. Both
PDS 0726, s2 2215 PDS0726S2 OVERTIME HOURS RATE EXPONENT MUST Both
PDS 0727 2181 PDS0727 TEMP START DATE MUST BE A FIXED Both
LENGTH OF 006.
2186 PDS0727 TEMP START DATE MUST BE A VALID DATE Both
PDS 0728 2181 PDS0728 TEMP WEEK ENDING MUST BE A FIXED Both
LENGTH OF 006.
2186 PDS0728 TEMP WEEK ENDING MUST BE A VALID Both
PDS 0729 2180 PDS0729 REQUESTOR NAME OR ID LENGTH MUST BE Both
001–040.
2182 PDS0729 REQUESTOR NAME OR ID MUST BE LEFT Both
ALL ZEROS.


PDS0730 2180 PDS0730 SUPERVISOR/REPORTS TO LENGTH MUST BE Both
001–040.
2182 PDS0730 SUPERVISOR/REPORTS TO MUST BE LEFT Both
ALL ZEROS.
PDS 0731 2180 PDS0731 TIME SHEET NUMBER LENGTH MUST BE 001– Both
020.
2182 PDS0731 TIME SHEET NUMBER MUST BE LEFT Both
ALL ZEROS.
PDS 0732 2181 PDS0732 DISCOUNT AMOUNT MUST BE A FIXED Both
LENGTH OF 018.
2183 PDS0732 DISCOUNT AMOUNT MUST BE NUMERIC. Both
PDS 0732, s1 2183 PDS0732S1 DISCOUNT AMOUNT MUST BE NUMERIC. Both
PDS 0732, s2 2183 PDS0732S2 DISCOUNT AMOUNT EXPONENT MUST BE Both
NUMERIC.
2215 PDS0732S2 DISCOUNT AMOUNT EXPONENT MUST Both
PDS 0732, s3 2185 PDS 732S3 DISCOUNT AMOUNT SIGN MUST BE D OR Both
C.
PDS 0732, s4 2182 PDS0732S4 DISCOUNT TYPE MUST BE LEFT JUSTIFIED Both
2184 PDS0732S4 DISCOUNT TYPE CANNOT BE ALL LOW- Both
PDS 0733 2181 PDS0733 SUBTOTAL AMOUNT MUST BE A FIXED Both
LENGTH OF 014.
2183 PDS0733 SUBTOTAL AMOUNT MUST BE NUMERIC. Both
PDS 0733, s1 2183 PDS0733S1 SUBTOTAL AMOUNT MUST BE NUMERIC. Both
PDS 0733, s2 2183 PDS0733S2 SUBTOTAL AMOUNT EXPONENT MUST BE Both
NUMERIC.
2215 PDS0733S2 SUBTOTAL AMOUNT EXPONENT MUST Both
PDS 0733, s3 2185 PDS0733S3 SUBTOTAL AMOUNT SIGN MUST BE D Both
OR C.


PDS 0734 2194 PDS0734 MISCELLANEOUS EXPENSES LENGTH MUST Both
PDS 0734, s1 2182 PDS0734S1 MISCELLANEOUS EXPENSE DESCRIPTION Both
(each MUST BE LEFT JUSTIFIED AND CANNOT CONTAIN ALL
occurrence) SPACES OR ALL ZEROS.
PDS 0734, s2 2183 PDS0734S2 MISCELLANEOUS EXPENSE AMOUNT MUST Both
(each BE NUMERIC.
occurrence)
PDS 0734, s3 2183 PDS0734S3 MISCELLANEOUS EXPENSES EXPONENT Both
MUST BE NUMERIC.
2215 PDS0734S3 MISCELLANEOUS EXPENSES AMOUNT Both
EXPONENT MUST CONTAIN A VALUE WITH THE
RANGE OF 0–5.
PDS 0734, s4 2185 PDS0734S4 MISCELLANEOUS EXPENSES AMOUNT SIGN Both
MUST BE D OR C.
PDS 0735 2180 PDS0735 SERVICE DESCRIPTOR CODE LENGTH MUST Both
BE 001–040.
2182 PDS0735 SERVICE DESCRIPTOR CODE MUST BE LEFT Both
ALL ZEROS.
PDS 0736 2180 PDS0736 TRACKING NUMBER OR PICKUP NUMBER Both
2182 PDS0736 TRACKING NUMBER OR PICKUP NUMBER Both
LENGTH MUST BE LEFT JUSTIFIED AND CANNOT
PDS 0737 2181 PDS0737 SHIPPING NET AMOUNT MUST BE A FIXED Both
LENGTH OF 014.
2183 PDS0737 SHIPPING NET AMOUNT MUST BE NUMERIC. Both
PDS 0737, s1 2183 PDS0737S1 SHIPPING NET AMOUNT MUST BE Both
NUMERIC.
PDS 0737, s2 2183 PDS0737S2 SHIPPING NET AMOUNT EXPONENT MUST Both
BE NUMERIC.
2215 PDS0737S2 SHIPPING NET AMOUNT EXPONENT MUST Both


PDS 0737, s3 2185 PDS0737S3 SHIPPING NET AMOUNT SIGN MUST BE D Both
OR C.
PDS 0738 2181 PDS0738 INCENTIVE AMOUNT MUST BE A FIXED Both
LENGTH OF 014.
2183 PDS0738 INCENTIVE AMOUNT MUST BE NUMERIC. Both
PDS 0738, s1 2183 PDS0738S1 INCENTIVE AMOUNT MUST BE NUMERIC. Both
PDS 0738, s2 2183 PDS0738S2 INCENTIVE AMOUNT EXPONENT MUST BE Both
NUMERIC.
2215 PDS0738S2 INCENTIVE AMOUNT EXPONENT MUST Both
PDS 0738, s3 2185 PDS0738S3 INCENTIVE AMOUNT SIGN MUST BE D OR Both
C.
PDS 0739 2181 PDS0739 PICKUP DATE MUST BE A FIXED LENGTH OF Both
006.
2186 PDS0739 PICKUP DATE MUST BE A VALID DATE IN Both
THE FORMAT YYMMDD.
PDS 0740 2181 PDS0740 DELIVERY DATE MUST BE A FIXED LENGTH Both
OF 006.
2186 PDS0740 DELIVERY DATE MUST BE A VALID DATE IN Both
THE FORMAT YYMMDD.
PDS 0741 2181 PDS0741 NUMBER OF PACKAGES MUST BE A FIXED Both
LENGTH OF 006.
2183 PDS0741 NUMBER OF PACKAGES MUST BE NUMERIC. Both
PDS 0742 2181 PDS0742 PACKAGE WEIGHT MUST BE A FIXED Both
LENGTH OF 012.
2183 PDS0742 PACKAGE WEIGHT MUST BE NUMERIC. Both
PDS 0743 2180 PDS0743 UNIT OF MEASURE LENGTH MUST BE 1–3. Both
2182 PDS0743 UNIT OF MEASURE MUST BE LEFT JUSTIFIED Both
PDS 0744 2191 PDS0744 SHIPPING PARTY INFORMATION LENGTH Both
MUST BE 050–150 AND MUST BE DIVISIBLE BY


PDS 0744, s1 2182 PDS0744S1 SHIPPING PARTY NAME MUST BE LEFT Both
ALL ZEROS.
PDS 0745 2192 PDS0745 SHIPPING PARTY ADDRESS LENGTH MUST Both
BE 050–300 AND MUST BE DIVISIBLE BY MINIMUM
PDS 0745, s1 2182 PDS 0745S1 SHIPPING PARTY ADDRESS MUST BE LEFT Both
(each JUSTIFIED AND CANNOT CONTAIN ALL SPACES OR
occurrence) ALL ZEROS.
PDS 0746 2180 PDS0746 SHIPPING PARTY POSTAL INFORMATION Both
2182 PDS0746 SHIPPING PARTY POSTAL INFORMATION Both
PDS 0746, s1 2182 PDS0746S1 SHIPPING PARTY CITY MUST BE LEFT Both
ALL ZEROS.
PDS 0746, s2 2182 PDS0746S2 SHIPPING PARTY STATE/PROVINCE MUST Both
PDS 0746, s3 2182 PDS0746S3 SHIPPING PARTY COUNTRY CODE MUST Both
PDS 0746, s4 2182 PDS0746S4 SHIPPING PARTY POSTAL CODE MUST BE Both
OR ALL ZEROS.
2258 PDS0746S4 SHIPPING PARTY POSTAL CODE MUST BE Both
SPACES
PDS 0747 2193 PDS0747 SHIPPING PARTY CONTACT LENGTH MUST Both
PDS 0747, s1 2185 PDS0747S1 SHIPPING PARTY DESCRIPTOR MUST BE 1, Both
2, 3, 4, OR 5.


PDS 0747, s2 2182 PDS0747S2 SHIPPING PARTY CONTACT INFORMATION Both
PDS 0748 2191 PDS0748 DELIVERY PARTY INFORMATION LENGTH Both
(each MUST BE 050–150 AND MUST BE DIVISIBLE BY
occurrence) MINIMUM OCCURRENCE LENGTH OF 050.
PDS 0748, s1 2182 PDS0748S1 DELIVERY PARTY NAME MUST BE LEFT Both
ALL ZEROS.
PDS 0749 2192 PDS0749 DELIVERY PARTY ADDRESS INFORMATION Both
(each LENGTH MUST BE 050–300 AND MUST BE DIVISIBLE
occurrence) BY MINIMUM OCCURRENCE LENGTH OF 050.
PDS 0749, s1 2182 PDS0749S1 DELIVERY PARTY ADDRESS MUST BE LEFT Both
ALL ZEROS.
PDS 0750 2180 PDS0750 DELIVERY PARTY POSTAL INFORMATION Both
2182 PDS0750 DELIVERY PARTY POSTAL INFORMATION Both
PDS 0750, s1 2182 PDS0750S1 DELIVERY PARTY CITY MUST BE LEFT Both
ALL ZEROS.
PDS 0750, s2 2182 PDS0750S2 DELIVERY PARTY STATE/PROVINCE CODE Both
PDS 0750,s3 2182 PDS0750S3 DELIVERY PARTY COUNTRY CODE MUST Both
PDS 0750, s4 2182 PDS0750S4 DELIVERY PARTY POSTAL CODE MUST BE Both
OR ALL ZEROS.
2258 PDS0750S4 DELIVERY PARTY POSTAL CODE MUST BE Both
SPACES


001–046
BE Y, N, OR SPACE.
PDS 0751, s2 2183 PDS0751S2 DETAIL TAX AMOUNT 4 MUST BE Both
NUMERIC.
PDS 0751, s3 2183 PDS0751S3 DETAIL TAX RATE 4 MUST BE NUMERIC. Both
PDS 0751, s4 2215 PDS0751S4 DETAIL TAX RATE EXPONENT 4 MUST Both
00, 01, 02, 03, 04, 05, 06, 10, 11, 12, 20, 21, 22, OR
SPACES.
CHARACTERS
OR C.
001–046.
BE Y, N, OR SPACES.
NUMERIC.
00, 01, 02, 03, 04, 05, 06, 10, 11, 12, 20, 21, 22, OR
SPACES.


CHARACTERS
OR C.
PDS 0753 2180 PDS0753 TAX AMOUNT 6 LENGTH MUST BE 001–046. Both
BE Y, N, OR SPACE.
NUMERIC.
00, 01, 02, 03, 04, 05, 06, 10, 11, 12, 20, 21, 22 OR
SPACES.
CHARACTERS
OR C.


PDS 0754 2193 PDS0754 DELIVERY PARTY CONTACT LENGTH MUST Both
PDS 0754, s1 2185 PDS0754S1 DELIVERY PARTY DESCRIPTOR MUST BE 1, Both
2, 3, 4, OR 5.
PDS 0754, s2 2182 PDS0754S2 DELIVERY PARTY CONTACT INFORMATION Both
PDS 0755 2181 PDS0755 LINE ITEM TOTAL AMOUNT MUST BE A Both
2196 PDS0755 LINE ITEM TOTAL AMOUNT IF PRESENT Both
PDS 0755, s1 2196 PDS0755S1 LINE ITEM TOTAL AMOUNT MUST BE Both
PDS 0755, s2 2183 PDS0755S2 LINE ITEM TOTAL AMOUNT EXPONENT Both
MUST BE NUMERIC.
2215 PDS0755S2 LINE ITEM TOTAL AMOUNT EXPONENT Both
5.
PDS 0755, s3 2185 PDS0755S3 LINE ITEM TOTAL AMOUNT SIGN MUST BE Both
D OR C.
PDS 0799 2182 PDS0799 TEST CASE TRACABILITY 1 MUST BE LEFT Both
ALL ZEROS.
2184 PDS0799 TEST CASE TRACEABILITY IDENTIFIERS Both
EXCEED 999 BYTES.

Retrieval Request/1644-603
subfield, for Retrieval Request/1644-603 messages.
MTI/Function Code: Retrieval Request/1644-603

DE 2 0009 DE2 PRIMARY ACCOUNT NUMBER (PAN) MUST BE Both
NUMERIC.
0010 DE2 PRIMARY ACCOUNT NUMBER (PAN) LENGTH Both
MUST BE 6-19.
0011 DE2 PRIMARY ACCOUNT NUMBER (PAN) ACCOUNT Both
RANGE INVALID.
PRESENT IN RETRIEVAL REQUEST MESSAGES.
MUST BE 00, 01, 12, 17, 18, 20, 28, OR 50.
0033 RERIEVAL REQ TO ATM ACQUIRER. Both
YYMM00.


REFERENCE DATE.
IN THE RANGE 00-23.
DE 14 0045 DE14 DATE, EXPIRATION MUST BE NUMERIC AND Both
RETRIEVAL REQUEST MESSAGES.
2219 DE25 MESSAGE REASON CODE INVALID FOR BUSINESS Both
SERVICE ARRANGEMENT <BSID&TYPE> AND
<AB>.
PROVIDED.


DE 30 0735 DE30 AMOUNTS, ORIGINAL MUST BE PRESENT IN Both
1016 DE30 AMOUNTS, ORIGINAL MUST BE PRESENT AND Both
NONZERO IN RETRIEVAL REQUEST MESSAGES.
BE ZERO-FILLED.
01-99.
IN RETRIEVAL REQUEST MESSAGES.
NUMERIC.
IN THE FORMAT YDDD.
NUMERIC.
NUMERIC.
FOR RETRIEVAL REQUEST MESSAGES.
NUMERIC.


DE 33 2180 DE33 FORWARDING INSTITUTION ID CODE LENGTH Both
MUST BE 006-011.
0092 DE37 RETRIEVAL REFERENCE NUMBER CANNOT Both
CONTAIN ALL SPACES.
OR ALL HIGH-VALUES.
SPACES.
0095 DE38 APPROVAL CODE MUST BE LEFT JUSTIFIED AND Both
99.
22.


EXCEED 13.
LEFT JUSTIFIED.
CODE.
DE62.
DE 49 0735 DE49 CURRENCY CODE, TRANSACTION MUST BE Both
ADDITIONAL DATA 2.
MUST BE 016-999.
SPACE.


THE DE71 MESSAGE NUMBERVALUE IN THE PREVIOUS
MESSAGE.
0735 DE71 MESSAGE NUMBER MUST BE PRESENT IN Both
CODE INVALID.
ONLY.
1156 ATM RETRIEVAL REQUESTS MUST BE SENT TO ATM GCMS
ACQUIRERS.
MASTERCARD.
CODE MISSING. MUST BE PRESENT IN ARBITRATION
CHARGEBACK MESSAGES (ATM TRANSACTIONS
ONLY).
CODE INVALID.
CODE /DE2 PRIMARY ACCOUNT NUMBER (PAN)
MASTERCARD.


CODE MUST BE PRESENT IN RETRIEVAL REQUEST
MESSAGES.
1175 TRANSACTION ORIGINATOR INSTITUTION ID CODE Both
INVALID FOR SENDING PROCESSOR ID IN PARAMETER
MASTER.
DE 95 1177 DE95 CARD ISSUER REFERENCE DATA MUST BE Both
NUMERIC.
2177 DE95 CARD ISSUER REFERENCE DATA MUST BE A Both
DE124.
DATA 2 ARE PRESENT.
VALUES.
DE125.
ADDED.


OCCURRENCE <XX>.



MUST BE NUMERIC.
NOT PRESENT.
PRESENT.
0735 PDS0149 CURRENCY CODES, AMOUNTS, ORIGINAL Both
MUST BE PRESENT.
PROVIDED.
020.
THE MEMBER PAIR.


PDS 0158, s3 2218 PDS0158S2 BUSINESS SERVICE ARRANGEMENT TYPE Both
PDS 0158, s4 0631 PDS0158S4 INTERCHANGE RATE DESIGNATOR AND Both
ARRANGEMENT <BSID&TYPE> AND ACCEPTANCE
BRAND <AB>.
<AB>
001-030.
C.
On Production Reports, the Destination & Origination
respectively.
1066 DE3 PROCESSING CODE AND PDS0165S1 SETTLEMENT Both

(000) 000–0000 OR 000 000 0000.


PDS 0171, s1 0421 PDS0171S1 CHARACTER SET INVALID. MUST BE ARA, Both
CHS, CHT, CYR, GRK, HEB, HIR, HAN, KAN, KAT, ROM,
THI, OR VIE.
1-15.
1151 PDS0172 SOLE PROPRIETOR NAME MUST BE LEFT Both
1-15.
1152 PDS0173 LEGAL CORPORATE NAME MUST BE LEFT Both
PDS 0174 0377 PDS0174 DUN & BRADTSREET NUMBER LENGTH MUST Both
BE 1–15.
NUMERIC.
2165 PDS0175 CARD ACCEPTOR URL LENGTH MUST BE 1– Both
255.
PDS 0189 0422 PD0189 POINT-OF-INTERACTION (POI) PHONE DATA Both
0423 PD0189 POINT-OF-INTERACTION (POI) PHONE DATA Both
PDS 0189, s1 0424 PDS0189S1 FORMAT NUMBER MUST BE 0, 1, 2, 3 OR 4. Both
PDS 0191 0528 PDS0191 ORIGINATING MESSAGE FORMAT MUST BE 1 Both
OR 2.


PDS 0228 0428 PDS0228 RETRIEVAL DOCUMENT CODE MUST BE A Both
0429 PDS0228 RETRIEVAL DOCUMENT CODE MUST BE 1. Both
PDS 0241 0825 PDS0241 MASTERCOM CONTROL NUMBER LENGTH Both
MUST BE 002 or 007.
2208 PDS0241 MASTERCOM CONTROL NUMBER CANNOT BE Both
EXCEED 999 BYTES.

Fee Collection (Retrieval Fee Billing)/1740-700

subfield, for Fee Collection (Retrieval Fee Billing)/1740-700 messages.
MTI/Function Code: Fee Collection (Retrieval Fee Billing)/1740-700

NUMERIC.
RANGE INVALID.
PRESENT IN FEE COLLECTION (RETRIEVAL FEE
BILLING) MESSAGES.
0735 DE3 PROCESSING CODE MUST BE PRESENT IN FEE Both
MUST BE EQUAL TO 19 FOR FEE COLLECTION
PROVIDED.
2176 DE 4 AMOUNT, TRANSACTION MUST BE NUMERIC. Both


IS PROVIDED.
0735 DE24 FUNCTION CODE MUST BE PRESENT IN FEE Both
FEE COLLECTION (RETRIEVAL FEE BILLING)
MESSAGES.
2205 DE 25 MESSAGE REASON CODE AND DE 3 Both
PROCESSING CODE COMBINATION INVALID.
<AB>.


PROVIDED.
0735 DE30 AMOUNTS, ORIGINAL MUST BE PRESENT IN FEE Both
NONZERO IN FEE COLLECTION (RETRIEVAL FEE
BILLING) MESSAGES.
BE ZERO-FILLED.
01-99.
IN FEE COLLECTION (RETRIEVAL FEE BILLING)
MESSAGES.
NUMERIC.
IN THE FORMAT YDDD.
NUMERIC.


BILLING) MESSAGES.
FOR FEE COLLECTION (RETRIEVAL FEE BILLING)
MESSAGES.
NUMERIC.
MUST BE 006-011.
CONTAIN ALL SPACES.
OR ALL HIGH-VALUES.
SPACES.
99.


22.
EXCEED 13.
LEFT JUSTIFIED.
CODE.
DE62.
0735 DE48 ADDITIONAL DATA MUST BE PRESENT IN FEE Both
DE 49 0119 DE49 CURRENCY CODE, TRANSACTION MUST Both
CURRENCY CODE.
PROVIDED.
PROVIDED.


NUMERIC.
IS PROVIDED.
PROVIDED.
CURRENCY CODE.
ADDITIONAL DATA 2.
MUST BE 016-999.
SPACE.
THE DE 71 MESSAGE NUMBER OF THE PREVIOUS
MESSAGE.
0735 DE71 MESSAGE NUMBER MUST BE PRESENT IN FEE Both


DE 72 0151 DE72 DATA RECORD CANNOT BE ALL LOW-VALUES Both
OR ALL HIGH-VALUES.
2180 DE72 DATA RECORD LENGTH MUST BE 001-100. Both
2208 DE72 DATA RECORD CANNOT BE ALL ZEROS OR ALL Both
SPACES.
DE 73 0747 INVALID DATE, ACTION. MUST BE VALID YYMMDD, Both
YYMM00, OR ALL ZEROS.
0735 DE73 DATE, ACTION MUST BE PRESENT IN FEE Both
CODE INVALID.
CODE IS DESIGNATED FOR INTERNAL USE BY
MASTERCARD.
CODE MUST BE PRESENT IN FEE COLLECTION
MASTERCARD.
CODE INVALID.
INVALID.
MASTERCARD.


CODE MUST BE PRESENT IN FEE COLLECTION
MASTER.
DE 95 1177 DE95 CARD ISSUER REFERENCE DATA MUST BE Both
NUMERIC.
DE124.
DATA 2 ARE PRESENT.
VALUES.
DE125.


ADDED.
PDS 0137 0375 PDS0137 FEE COLLECTION CONTROL NUMBER MUST Both
BE NUMERIC.
0735 PDS0137 FEE COLLECTION CONTROL NUMBER MUST Both
BE PRESENT.
0756 PDS0137 FEE COLLECTION CONTROL NUMBER Both
IN FEE COLLECTION (RETRIEVAL FEE BILLING).


OCCURRENCE <XX>.


MUST BE NUMERIC.
NOT PRESENT.
PRESENT.
MUST BE PRESENT.
PROVIDED.
020.


THE MEMBER PAIR.
ARRANGEMENT <BSID&TYPE> AND ACCEPTANCE
BRAND <AB>.
<AB>
IN FEE COLLECTION (RETRIEVAL FEE BILLING)
MESSAGES.
001-030.
C.
respectively.


(000) 000–0000 OR 000 000 0000.
1-15.
1151 PDS 0172 SOLE PROPRIETOR NAME MUST BE LEFT Both
1-15.
1152 PDS 0173 LEGAL CORPORATE NAME MUST BE LEFT Both
BE 1–15.
1163 PDS 0174 DUN & BRADSTREET NUMBER MUST BE Both
NUMERIC.
255.


PDS 0191 0528 PDS0191 ORIGINATING MESSAGE FORMAT MUST BE Both
1OR 2.
PDS 0228 0428 PDS0228 RETRIEVAL DOCUMENT CODE MUST BE A Both
0429 PDS0228 RETRIEVAL DOCUMENT CODE MUST BE 1, 2, Both
OR 4.
PDS 0230 0431 PDS0230 FULFILLMENT DOCUMENT CODE MUST BE A Both
0432 PDS0230 FULFILLMENT DOCUMENT CODE MUST BE 1. Both
0735 PDS0230 FULFILLMENT DOCUMENT CODE MUST BE Both
BILLING) MESSAGES.
PDS 0241 0825 PDS0241 MASTERCOM CONTROL NUMBER LENGTH Both
MUST BE 002 or 007.
PDS 0262 0441 PDS0262 DOCUMENTATION INDICATOR MUST BE A Both
0442 PDS0262 DOCUMENTATION INDICATOR MUST BE 0 Both
OR 1.
PDS 264 0444 INVALID ORIGINAL RETRIEVAL REASON FOR REQUEST Both
LENGTH. MUST BE A FIXED LENGTH OF 4.
0445 INVALID VALUE IN ORIGINAL RETRIEVAL REASON FOR Both
REQUEST. MUST BE 6305, 6321, 6322, 6323, 6341, 6342.
0735 PDS0264 ORIGINAL RETRIEVAL REASON FOR REQUEST Both
MUST BE PRESENT IN FEE COLLECTION (RETRIEVAL
FEE BILLING) MESSAGES.


PDS 0265 0446 PDS0265 INITIAL PRESENTMENT/FEE COLLECTION Both
DATA CANNOT BE LOW-VALUES OR HIGH-VALUES.
0447 PDS0265 INITIAL PRESENTMENT/FEE COLLECTION Both
DATA LENGTH MUST BE 004-110.
PDS 0265, s1 0448 PDS0265S1 INITIAL MESSAGE REASON CODE MUST BE Both
A VALID MESSAGE REASON CODE.
PDS 0265, s2 0449 PDS0265S2 DATE, INITIAL PRESENTMENT BUSINESS Both
MUST BE VALID YYMMDD OR ZEROS IN FEE
PDS 0266 0268 PDS0266 FIRST CHARGEBACK/FEE COLLECTION Both
RETURN DATA CANNOT BE ALL LOW-VALUES OR ALL
HIGH-VALUES.
0826 PDS0266 FIRST CHARGEBACK/FEE COLLECTION Both
RETURN DATA MUST BE 004-127.
PDS 0266, s1 0505 PDS0266S1 MESSAGE REASON CODE MUST BE A VALID Both
MESSAGE REASON CODE OR ZEROS.
PDS 0267 0468 PDS0267 SECOND PRESENTMENT/FEE COLLECTION Both
RESUBMISSION DATA CANNOT BE ALL LOW-VALUES
OR ALL HIGH-VALUES.
0469 PDS0267 SECOND PRESENTMENT/FEE COLLECTION Both
RESUBMISSION DATA MUST BE 004-127.
NOT LEFT JUSTIFIED.
EXCEED 999 BYTES.

First Chargebacks (Full)/1442-450 and (Partial)/1442-453

The following tables show the error numbers and message texts by field and
subfield, for First Chargebacks (Full)/1442-450 and (Partial)/1442-453
messages.
MTI/Function Code: First Chargebacks (Full)/1442-450 and (Partial)/1442-453

NUMERIC.
MUST BE 6-19.
RANGE INVALID.
PRESENT IN FIRST CHARGEBACK (FULL AND PARTIAL)
MESSAGES.
DE 3 0012 DE3 PROCESSING CODE MUST BE NUMERIC Both
0735 DE3 PROCESSING CODE MUST BE PRESENT IN FIRST Both
CHARGEBACK (FULL AND PARTIAL) MESSAGES.
MUST BE 00, 01, 12, 17, 18, 20, 28, OR 50.
1140 ATM CHARGEBACKS MUST BE SENT TO ATM Both
ACQUIRERS.
1160 DE3S1 CARDHOLDER TRANSACTION TYPE MUST BE 01 GCMS
IF THE RECEIVER IS AN ATM ACQUIRER.


PROVIDED.
FIRST CHARGEBACK (FULL AND PARTIAL) MESSAGES.
1053 DE4 AMOUNT, TRANSACTION LESS THAN OR EQUAL Both
TO WORLD CARD CHARGEBACK MINIMUM AMOUNT.
THRESHOLD.
IS PROVIDED.
YYMM00.
REFERENCE DATE.
IN THE RANGE 00-23.


DE 22, s1 0047 DE22S1 TERMINAL DATA: CARD DATA INPUT Both
D, E, M, OR V.
INVALID. MUST BE 0, 1, 2, 5, 6, OR 9.
BE 0, 1, OR 9.
INVALID. MUST BE 0, 1, 2, 3, 4, 5, 6, OR 9.
DE 22, s5 0051 DE22S5 CARDHOLDER PRESENT DATA INVALID. MUST Both
BE 0, 1, 2, 3, 4, 5, 6, OR 9.
OR 9.
0, 1, 2, 6, A, B, C, F, S, OR T.
MUST CONTAIN AN “F”, “C” OR “M”.
MUST BE 0, 1, 2, 3, OR S.
0, 1, 2, 3, 4, 5, 6, 7, 8, 9, A, B, OR C.
0687 DE24 FUNCTION CODE AND PDS0025 REVERSAL GCMS


DE 24 0735 DE24 FUNCTION CODE MUST BE PRESENT IN FIRST Both
0148 DE25 MESSAGE REASON CODE INVALID FOR THIS GCMS
FIRST CHARGEBACK (FULL) MESSAGES.
0154 REQUEST NOT ON FILE. GCMS
0575 ISSUER HAS ACCEPTED THE ACQUIRER’S RESPONSE. GCMS
0588 DE25 MESSAGE REASON CODE INVALID FOR ATM Both
CASH WITHDRAWAL TRANSACTION. MUST BE
SUBMITTED FOR DUPLICATE PROCESSING (4834) OR
SERVICES NOT RENDERED (4859).
0592 DOCUMENTATION ALWAYS REQUIRED FOR THIS Both
DE25 MESSAGE REASON CODE.
0593 DE25 MESSAGE REASON CODE/TERMINAL TYPE Both
0638 ISSUER CANNOT CHARGEBACK FOR DE25 MESSAGE GCMS
REASON CODE 4801 OR 4802.
0677 DE25 MESSAGE REASON CODE SHOULD HAVE BEEN GCMS
4802.
0704 IMAGE REVIEW STILL PENDING. GCMS
ARBITRATION CHARGEBACK (FULL AND PARTIAL)
MESSAGES.
0741 THE ISSUER HAS NOT ACCEPTED/REJECTED THE GCMS
FULFILLMENT.
2267 DE25 MESSAGE REASON CODE INVALID FOR FIRST Both
CHARGEBACK MESSAGES.


DE 26 0735 DE26 CARD ACCEPTOR BUSINESS CODE (MCC) MUST Both
BE PRESENT IN FIRST CHARGEBACK (FULL AND
PARTIAL) MESSAGES.
<AB>.
PROVIDED.
NONZERO IN FIRST CHARGEBACK (FULL) OR FIRST
BE ZERO-FILLED.
01-99.
IN FIRST CHARGEBACK (FULL AND PARTIAL)
MESSAGES.


NUMERIC.
IN THE FORMAT YDDD.
NUMERIC.
NUMERIC.
PRESENT IN FIRST CHARGEBACK (FULL AND PARTIAL),
MESSAGES.
FOR FIRST CHARGEBACK (FULL) MESSAGES.
NUMERIC.
MUST BE 006-011.
CONTAIN ALL SPACES.
OR ALL HIGH-VALUES.
SPACES.


DE 38 2198 DE38 APPROVAL CODE CANNOT BE PRESENT WHEN Both
DE 40 2183 DE40 EXTENDED SERVICE CODE MUST BE NUMERIC. Both
0101 DE43 CARD ACCEPTOR NAME/LOCATION MUST BE Both
20-99.
NAME\STREET ADDRESS\CITY.
22.
EXCEED 13.


LEFT JUSTIFIED.
CODE.
DE62.
0735 DE48 ADDITIONAL DATA MUST BE PRESENT IN FIRST Both
CURRENCY CODE.
PROVIDED.
PROVIDED.
MESSAGES.
NUMERIC.
IS PROVIDED.
PROVIDED.
CURRENCY CODE.


HIGH-VALUES.
SPACES.
ADDITIONAL DATA 2.
MUST BE 016-999.
SPACE.
THE DE 71 MESSAGE NUMBER OF THE PREVIOUS
MESSAGE.
0735 DE71 MESSAGE NUMBER MUST BE PRESENT IN FIRST Both


OR ALL HIGH-VALUES.
SPACES.
CODE INVALID.
ONLY.
CODE MUST BE A SUPERMARKET ACQUIRER IF THE
TRANSACTION IS SUBMITTED FOR THE U.S. REGION
SUPERMARKET INTERCHANGE PROGRAM.
MASTERCARD.
CODE MUST BE A WAREHOUSE ACQUIRER IF THE
WAREHOUSE INTERCHANGE PROGRAM.
CODE MISSING. MUST BE PRESENT IN FIRST
CHARGEBACK (ATM) MESSAGES.
CODE LENGTH MUST BE 006-011
CODE INVALID.


MASTERCARD.
CODE MUST BE PRESENT IN FIRST CHARGEBACK
(FULL AND PARTIAL) MESSAGES.
MASTER.
DE 95 0649 DUPLICATE DE95 CARD ISSUER REFERENCE DATA. GCMS
0735 DE95 CARD ISSUER REFERENCE DATA MUST BE Both
MESSAGES.
NUMERIC.
2177 DE 95 CARD ISSUER REFERENCE DATA MUST BE A Both
FIXED LENGTH OF 10.
DE124.
DATA 2 ARE PRESENT.
VALUES.
2152 DE 124 ADDITIONAL DATA AND LENGTH MUST BE Both
008-999.


DE 124 2154 INCORRECT PDS ENCODING SCHEME WITHIN DE124 Both
DE125.
ADDED.
PDS 0020 1065 PDS0020 ISSUER CURRENCY CONVERSION RATE (ICCR) Both
EFFECTIVE DATE MUST BE A VALID DATE IN THE
FORMAT YYMMDD.
1080 PDS0020 ISSUER CURRENCY CONVERSION RATE (ICCR) Both
EFFECTIVE DATE LENGTH MUST BE A FIXED LENGTH
OF 6.
1142 ISSUER CURRENCY CONVERSION RATE (ICCR) GCMS
EFFECTIVE DATE NOT ON FILE.
PDS 0023 0181 PDS0023 TERMINAL TYPE CANNOT BE ALL LOW- Both
OF 003.
NA_, OR POI.
1092 PDS0023 TERMINAL TYPE MISSING. MUST BE PRESENT Both
IN NON-REVERSAL FIRST CHARGEBACK (FULL)
MESSAGES.


PDS 0043 0194 PDS0043 PROGRAM REGISTRATION ID MUST BE A Both

OR 01.
OCCURRENCE <XX>.

OCCURRENCE <XX>.


OCCURRENCE <XX>.

MESSAGES.
OCCURRENCE <XX>.


MUST BE NUMERIC.
NOT PRESENT.
PRESENT.
MUST BE PRESENT.


PROVIDED.
020.
THE MEMBER PAIR.
LOCATION.


<AB>
PDS 0158, s5 0686 EXCEEDS MAXIMUM TIMELINESS OF <NNN> DAYS. GCMS
The actual maximum number of days will replace <NNN>
in the exception message that members receive.

MESSAGES.
001-030.
C.
respectively.

(000) 000–0000 OR 000 000 0000.


1-15.
1-15.
BE 1–15.
NUMERIC.
255.
OR 2.


PDS 0241 1084 PDS0241 MASTERCOM CONTROL NUMBER MUST BE A Both
PDS 0260 0435 PDS0260 EDIT EXCLUSION INDICATOR CANNOT BE Both
0436 PDS0260 EDIT EXCLUSION INDICATOR LENGTH MUST Both
BE 2-4.
PDS 0260, s1 0437 PDS0260S1 EXCLUSION REQUEST CODE INVALID. Both
MUST BE Y, B0 - B9, BA – BZ, OR SPACES.
OR 1.
0735 PDS0262 DOCUMENTATION INDICATOR MUST BE Both
MESSAGES.
PDS 0268 0487 PDS0148 CURRENCY EXPONENTS MISSING. MUST BE Both
PRESENT IN A MESSAGE WHEN PDS0268 AMOUNT,
PARTIAL TRANSACTION IS PROVIDED.
This error code applies only to First Chargebacks
(Partial)/1442-453.
1132 PDS0268 AMOUNT, PARTIAL TRANSACTION LENGTH Both

(Partial)/1442-453.
PDS 0268, s1 0482 AMOUNT, PARTIAL TRANSACTION MUST BE NUMERIC Both

AND GREATER THAN ZEROS.
(Partial)/1442-453.
PDS 0268, s2 0451 PDS0268S2 CURRENCY CODE, PARTIAL TRANSACTION Both

MUST CONTAIN A VALID ISO STANDARD NUMERIC
CURRENCY CODE.
(Partial)/1442-453.


PDS 0268, s2 0488 PDS0148 CURRENCY EXPONENT OCCURRENCE FOR Both
PDS0268S2 CURRENCY CODE, PARTIAL TRANSACTION
MISSING. MUST BE PROVIDED.
(Partial)/1442-453.

LENGTH MUST BE 001–050
NOT LEFT JUSTIFIED.
EXCEED 999 BYTES.

Second Presentments (Full)/1240-205, and (Partial)/1240-282

subfield, for Second Presentment (Full)/1240-205, and (Partial)/1240-282
messages.
MTI/Function Code: Second Presentment (Full)/1240-205 and (Partial)/1240-282

PRESENT SECOND PRESENTMENT (FULL AND
PARTIAL) MESSAGES.
MASTERCARD.
FOR BUSINESS SERVICE ARRANGEMENT
0735 DE3 PROCESSING CODE MUST BE PRESENT IN Both
SECOND PRESENTMENT (FULL AND PARTIAL)
MESSAGES.
MUST BE 00, 01, 12, 17, 18, 20, 28, OR 50.
2285 DE3S1 PROCESSING CODE MUST MATCH THE GCMS
PROCESSING CODE FROM THE PREVIOUS CYCLE.
DE 3, s2 0014 DE3S2 CARDHOLDER FROM – ACCOUNT MUST BE 00 Both
DE 3, S3 0015 DE3S3 CARDHOLDER TO – ACCOUNT MUST BE 00. Both


PROVIDED.
0024 PDS0148 CURRENCY EXPONENTS MISSING. MUST Both
MESSAGES.
THRESHOLD
DE 5 0025 DE5 AMOUNT, RECONCILIATION MUST BE Both
NUMERIC.
IN A MESSAGE WHEN DE5 AMOUNT,
DE 6 0034 DE6 AMOUNT, CARDHOLDER BILLING MUST BE Both
NUMERIC.
0036 DE6 AMOUNT, CARDHOLDER BILLING MUST BE Both
CODE, CARDHOLDER BILLING IS PROVIDED.
0037 PDS 0148 CURRENCY EXPONENTS MISSING. MUST Both
YYMM00.
REFERENCE DATE.


DE 12, s2 0040 DE12S2 TIME, LOCAL TRANSACTION HOURS MUST Both
BE IN THE RANGE 00–23
MINUTES AND SECONDS MUST BE IN RANGE 00–59,
HAVE A VALID DATE IN THE FORMAT YYMM
DE 22, s1 0047 DE22S1 TERMINAL DATA:CARD DATA INPUT Both
CAPABILITY INVALID. MUST BE 0, 1, 2, 4, 5, 6, A, B,
C, D, E, M OR V.
DE 22, s2 0048 DE22S2 CARDHOLDER AUTHENTICATION Both
CAPABILITY INVALID. MUST BE 0, 1, 2, 5, 6 OR 9.
DE 22, s3 0049 DE22S3 CARD CAPTURE CAPABILITY INVALID. Both
MUST BE 0, 1, OR 9.
DE 22, s5 0051 DE22S5 CARDHOLDER PRESENT DATA INVALID. Both
MUST BE 0, 1, 2, 3, 4, 5, 6 OR 9.
DE 22, s6 0052 DE22S6 CARD PRESENT DATA INVALID. MUST BE 0, Both
1, OR 9.
DE 22, s7 0053 DE22S7 CARD DATA INPUT MODE INVALID. MUST Both
BE 0, 1, 2, 6, A, B, C, F, S, OR T.
MUST CONTAIN AN “F”, “C”, OR “M”..
MUST BE 0, 1, 2, 3, OR S.
DE 22, s12 0058 DE22S12 PIN CAPTURE CAPABILITY INVALID. MUST Both
BE 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, A, B, OR C.


0437 DE23 CARD SEQUENCE NUMBER CONTAINS A Both
VALUE IN THE RANGE OF 000-099.
DE 24 0735 DE24 FUNCTION CODE MUST BE PRESENT IN Both
MESSAGES.
0595 DE25 MESSAGE REASON CODE NOT ALLOWED IF GCMS
FIRST CHARGEBACK WAS FOR REQUESTED
TRANSACTION INFRMATION NOT RECEIVED.
0630 DE25 MESSAGE REASON CODE INVALID. MESSAGE Both
REASON CODE RESERVED FOR SECOND
PRESENTMENT (FULL), OR SECOND PRESENTMENT
(PARTIAL) MESSAGES ORIGINATING IN THE INET
FORMAT.
MESSAGES.
2219 DE25 MESSAGE REASON CODE INVALID FOR Both
BUSINESS SERVICE ARRANGEMENT <BSID&TYPE>
BE PRESENT IN SECOND PRESENTMENT (FULL AND
PARTIAL) MESSAGES.
INVALID. MUST BE 6011 AUTOMATED CASH
CODE 01.
<AB>.


PROVIDED.
MESSAGES.
NONZERO IN SECOND PRESENTMENT (FULL AND
PARTIAL) MESSAGES.
DE 30, S2 0076 DE30S2 AMOUNTS ORIGINAL RECONCILIATION
MUST BE ZERO-FILLED.
LOW-VALUES OR ALL HIGH-VALUES.-
0289 DE31 ACQUIRER REFERENCE DATA LENGTH MUST Both
BE 01-99.
0735 DE31 ACQUIRER REFERENCE DATA MUST BE Both
PRESENT IN SECOND PRESENTMENT (FULL AND
PARTIAL) MESSAGES.
NUMERIC.


DE 31, s2 0081 DE31S2 ACQUIRERS BIN MUST BE NUMERIC. Both
1087 DE31S2 ACQUIRER’S BIN NOT A VALID ACQUIRER Both
BIN.
ACQUIRER REFERENCE DATA MUST BE A VALID
DATE IN THE FORMAT YDDD.
DE 31, s4 0083 DE31S4 ACQUIRERS SEQUENCE NUMBER MUST BE Both
NUMERIC.
NUMERIC.
FIELD MUST BE A VALUE OF 001-011
DE 33 0735 DE33 FORWARDING INSTITUTION ID CODE MUST Both
BE PRESENT IN SECOND PRESENTMENT (FULL AND
PARTIAL) MESSAGES.
FOR SECOND PRESENTMENT (FULL) OR SECOND
PRESENTMENT (PARTIAL) MESSAGES.
0808 DE33 FORWARDING INSTITUTION ID CODE MUST Both
BE NUMERIC.
MUST BE 006-011.
CONTAIN ALL SPACES.
DE 38 0093 DE38 APPROVAL CODE CANNOT BE ALL LOW- Both
SPACES.


DE 38 2198 DE38 APPROVAL CODE CANNOT BE PRESENT WHEN Both
DE 41 0096 CARD ACCEPTOR TERMINAL ID CANNOT BE ALL Both
DE 43 0100 DE43 CARD ACCEPTOR NAME/LOCATION CANNOT Both
0101 DE43 CARD ACCEPTOR NAME/LOCATION MUST BE Both
20-99.
BACKSLASH CHARACTESR ARE REQUIRED TO
DELIMIT NAME\STREET\ADDRESS\CITY.
0103 DE43S1 CAD ACCEPTOR NAME LENGTH MUST BE 1- Both
22
JUSTIFIED AND CANNOT CONTAIN ALL SPACES
DE 43, s1 0735 DE43S1 CARD ACCEPTOR NAME MUST BE PRESENT Both
IN SECOND PRESENTMENT (FULL AND PARTIAL)
MESSAGES.


DE 43, s3 0104 DE43S3 CARD ACCEPTOR CITY CANNOT BE ALL Both
EXCEED 13.
LEFT JUSTIFIED.
0405 INVALID TRANSACTION FOR THE Both
COUNTRY/REGION.
COMPATIBLE WITH DE43S5
STATE/PROVINCE/REGION CODE.
DE 48 0114 DE 48 ADDITIONAL DATA CANNOT BE ALL LOW- Both
DE62.
MESSAGES.
CURRENCY CODE.
PROVIDED.
0122 PDS0148S1 CURRENCY CODE OCCURRENCE FOR Both
DE49 CURRENCY CODE, TRANSACTION MUST BE
PROVIDED.
PARTIAL) MESSAGES.


NUMERIC.
0124 DE50 CURRENCY CODE MISSING. MUST BE Both
DE50 CURRENCY CODE, RECONCILIATION MUST BE
PROVIDED.
CURRENCY CODE.
DE 51 0133 DE51 CURRENCY CODE, CARDHOLDER BILLING Both
MUST BE NUMERIC.
0134 DE51 CURRENCY CODE, CARDHOLDER BILLING Both
AMOUNT, CARDHOLDER BILLING IS PROVIDED.
DE51 CURRENCY CODE, CARDHOLDER BILLING
MUST BE PROVIDED.
HIGH-VALUES.
SPACES.
0168 INCORRECT PDS ENCODING SCHEME WITH DE62 Both
ADDITIONAL DATA 2.
IF DE48 ADDITIONAL DATA IS PRESENT.


DE 63, s1 0139 DE63S1 LIFE CYCLE SUPPORT INDICATOR MUST BE Both
A SPACE.
DE 63, s2 0141 DE63S2 TRACE ID POSITIONS 10-13 MUST BE A Both
VALID DATE IN THE FORMAT MMDD.
THE DE 71 VALUE FROM THE PREVIOUS MESSAGE.
MESSAGES.
OR ALL HIGH-VALUES.
SPACES.
CODE INVALID.
ONLY.
MASTERCARD.
CODE MISSING. MUST BE PRESENT IN FIRST AND
SECOND PRESENTMENT.
only.



CODE INVALID.
INVALID.
MASTERCARD.
CODE MUST BE PRESENT IN SECOND PRESENTMENT
(FULL AND PARTIAL) MESSAGES.
CODE INVALID FOR SENDING PROCESSOR ID IN
PARAMETER MASTER.
DE 95 0726 PREVIOUS CYCLE NOT ON FILE. Both
PARTIAL) MESSAGES.
NUMERIC.
DE 123 0170 DE123 ADDITIONAL DATA 3 CANNOT BE ALL LOW-
0173 INCORRECT PDS ENCODING SCHEME WITHIN DE123
DE124.
0174 DE123 ADDITIONAL DATA 3 CAN BE PRESENT ONLY
DATA 2 ARE PRESENT.


IF DE48 ADDITIONAL DATA, DE62 ADDITIONAL
DATA 2, AND DE123 ADDITIONAL DATA 3 ARE
PRESENT.
VALUES.
DE125.
ADDED.
IF DE48 ADDITIONAL DATA, DE62 ADDITIONAL
DATA 2, DE123 ADDITIONAL DATA 3, AND DE124
OF 003.
NA_, OR POI.
1092 PDS0023 TERMINAL TYPE MISSING. MUST BE Both
PRESENT IN NON-REVERSAL SECOND PRESENTMENT
(FULL) OR SECOND PRESENTMENT (PARTIAL)
MESSAGES.


PDS 0025, s1 0185 PDS0025S1 MESSAGE REVERSAL INDICATOR MUST Both
BE EQUAL TO R OR A SPACE IF PRESENT.
ORIGINAL MESSAGE MUST BE NUMERIC AND A
ORIGINAL MESSAGE INVALID. CANNOT BE
GREATER THAN THE SYSTEM PROCESSING DATE.
PDS 0043 2208 PDS0043 PROGRAM REGISTRATION ID CANNOT BE Both
PDS 0146 0381 PDS0146 AMOUNTS, TRANSACTION FEE LENGTH Both
On Production Reports, the field occurrence number
with the data in error will replace the “XX”.
PDS 0146, s3 1102 PDS0146S3 FEE SETTLEMENT INDICATOR MUST BE Both

00 OR 01.
OCCURRENCE <XX>.

OCCURRENCE <XX>.


PDS 0146, s5 0385 PDS0146 AMOUNTS, TRANSACTION FEE LENGTH Both
IN SECOND PRESENTMENT (FULL AND PARTIAL)
MESSAGES.
PDS 0148, s1 0395 PDS0148S1 CURRENCY CODE MUST CONTAIN A Both
OCCURRENCE <XX>.


MUST BE NUMERIC.
IS PRESENT BUT PDS0148 CURRENCY EXPONENTS IS
NOT PRESENT.
IS PRESENT BUT DE30 AMOUNT, ORIGINAL IS NOT
PRESENT.
MUST BE PRESENT.
TRANSACTION AMOUNT MUST CONTAIN A VALID
ISO STANDARD NUMERIC CURRENCY CODE.


PDS 0149, s1 0403 PDS0148 CURRENCY EXPONENT OCCURRENCE FOR Both
PROVIDED.
020.
MESSAGES.
THE MEMBER PAIR.
THE MEMBER PAIR.
ARRANGEMENT <BUSINESS SERVICE ID & TYPE>


LOCATION.
<AB>

0735 PDS0165 SETTLEMENT INDICATOR MUST BE Both
PARTIAL) MESSAGES.
001-030.
PDS 0165, s1 0414 PDS0165S1 SETTLEMENT INDICATOR MUST BE M, B Both
OR C.
On Production Report, the Destination & Origination
respectively.
1066 DE3 PROCESSING CODE AND PDS0165S1 Both

SETTLEMENT INDICATOR COMBINATION INVALID.
CANNOT BE ALL LOW-VALUES OR ALL HIGH-
VALUES.


(000) 000–0000 OR 000 000 0000.
PDS 0171 0419 PDS0171 ALTERNATE CARD ACCEPTOR Both
DESCRIPTION CANNOT BE ALL LOW-VALUES OR ALL
HIGH-VALUES.
0420 PDS0171 ALTERNATE CARD ACCEPTOR Both
DESCRIPTION LENGTH MUST BE 4-201.
PDS 0172 0591 PDS0172 SOLE PROPRIETOR NAME LENGTH MUST Both
BE 1-15.
PDS 0173 0699 PDS0173 LEGAL CORPORATE NAME LENGTH MUST Both
BE 1-15.
PDS 0174 0377 PDS0174 DUN & BRADSTREET NUMBER LENGTH Both
MUST BE 1–15.
NUMERIC.
PDS 0189 0422 PDS0189 POINT-OF-INTERACTION (POI) PHONE Both
DATA CANNOT BE ALL LOW-VALUES OR ALL HIGH-
VALUES.
0423 PDS0189 POINT-OF-INTERACTION (POI) PHONE Both
DATA LENGTH MUST BE A FIXED LENGTH OF 41.
PDS 0189, s1 0424 PDS0189S1 FORMAT NUMBER MUST BE 0, 1, 2, 3, OR Both
4.


PDS 0191 0528 PDS0191 ORIGINATING MESSAGE FORMAT MUST BE Both
1 OR 2.
PDS 0241 1084 PDS0241 MASTERCOM CONTROL NUMBER MUST BE Both
2208 PDS0241 MASTERCOM CONTROL NUMBER CANNOT Both
BE ALL ZEROS OR ALL SPACES.
0436 PDS0260 EDIT EXCLUSION INDICATOR LENGTH Both
MUST BE 2-4.
MUST BE Y, B0 - B9, BA – BZ, OR SPACES.
OR 1.
PARTIAL) MESSAGES.
This error code applies only to Second Presentments
(Partial)/1240-282.

(Partial)/1240-282.
PDS 0268, s1 0482 PDS0268S1 AMOUNT, PARTIAL TRANSACTION MUST Both

BE NUMERIC AND GREATER THAN ZEROS.
(Partial)/1240-282.


PDS 0268, s2 0451 PDS0268S2 CURRENCY CODE, PARTIAL Both
TRANSACTION MUST CONTAIN A VALID ISO
(Partial)/1240-282.

PDS0268S2 CURRENCY CODE, PARTIAL
TRANSACTION MISSING. MUST BE PROVIDED.
(Partial)/1240-282.

CANNOT BE ALL LOW-VALUES OR ALL HIGH-
VALUES.
NOT LEFT JUSTIFIED.

Arbitration Chargebacks (Full)/1442-451 and (Partial)/1442-454

The following tables show the error numbers and message texts by field and
subfield, for Arbitration Chargebacks (Full)/1442-451 and (Partial)/1442-454
messages.
MTI/Function Code: Arbitration Chargebacks (Full)/1442-451 and (Partial)/1442-454

NUMERIC.
MUST BE 6-19.
RANGE INVALID.
PRESENT IN ARBITRATION CHARGEBACK (FULL AND
PARTIAL) MESSAGES.
1160 DE3S1 CARDHOLDER TRANSACTION TYPE MUST BE 01 GCMS
IF THE RECEIVER IS AN ATM ACQUIRER.
0735 DE3 PROCESSING CODE MUST BE PRESENT IN Both
MESSAGES.
MUST BE 00, 01, 12, 17, 18, 20, 28, OR 50.


DE 3, s1 1140 ATM CHARGEBACKS MUST BE SENT TO ATM Both
ACQUIRERS.
2285 DE3S1 PROCESSING CODE MUST MATCH THE GCMS
PROCESSING CODE FROM THE PREVIOUS CYCLE.
DE 4 0020 DE4 AMOUNT, TRANSACTION MUST BE NUMERIC AND Both
GREATER THAN ZERO.
PROVIDED.
MESSAGES.
1053 DE4 AMOUNT, TRANSACTION LESS THAN OR EQUAL Both
TO WORLD CARD CHARGEBACK MINIMUM AMOUNT.
THRESHOLD.
IS PROVIDED.
YYMM00.
REFERENCE DATE.


IN THE RANGE 00-23.
DE 22, s1 0047 DE22S1 TERMINAL DATA: CARD DATA INPUT Both
D, E, M, OR V.
INVALID. MUST BE 0, 1, 2, 5, 6, OR 9.
BE 0, 1, OR 9.
DE 22, s5 0051 DE22S5 CARDHOLDER PRESENT DATA INVALID. MUST Both
BE 0, 1, 2, 3, 4, 5, 6, OR 9.
OR 9.
0, 1, 2, 6, A, B, C, F, S, OR T.
MUST CONTAIN AN “F”, “C”, OR “M”..
MUST BE 0, 1, 2, 3, OR S.
0, 1, 2, 3, 4, 5, 6, 7, 8, 9, A, B, OR C.


0687 DE24 FUNCTION CODE AND PDS0025 REVERSAL GCMS
MESSAGES.
0588 DE25 MESSAGE REASON CODE INVALID FOR ATM Both
CASH WITHDRAWAL TRANSACTION. MUST BE
SUBMITTED FOR DUPLICATE PROCESSING (4834) OR
SERVICES NOT RENDERED (4859).
0612 PDS0262 DOCUMENTATION INDICATOR 0 ON GCMS
PREVIOUS CYCLE.
0630 DE25 MESSAGE REASON CODE INVALID. MESSAGE Both
REASON CODE RESERVED FOR ARBITRATION
CHARGEBACKS (FULL) MESSAGES ORIGINATING IN
THE INET FORMAT.
MESSAGES.
2267 DE25 MESSAGE REASON CODE INVALID FOR FIRST Both
CHARGEBACK MESSAGES.
BE PRESENT IN ARBITRATION CHARGEBACK (FULL
AND PARTIAL) MESSAGES.


<AB>.
PROVIDED.
MESSAGES.
NONZERO IN ARBITRATION CHARGEBACK (FULL)
MESSAGES.
BE ZERO-FILLED.
01-99.
IN ARBITRATION CHARGEBACK (FULL AND PARTIAL)
MESSAGES.
NUMERIC.


IN THE FORMAT YDDD.
NUMERIC.
NUMERIC.
PARTIAL) MESSAGES.
FOR ARBITRATION CHARGEBACK (FULL) MESSAGES.
NUMERIC.
MUST BE 006-011.
CONTAIN ALL SPACES.
OR ALL HIGH-VALUES.
SPACES.
2198 DE38 APPROVAL CODE CANNOT BE PRESENT WHEN Both


99.
22.
MESSAGES.
DE43, s3 0104 DE43S3 CARD ACCEPTOR CITY CANNOT BE ALL LOW- Both
EXCEED 13.


LEFT JUSTIFIED.
CODE.
DE62.
MESSAGES.
CURRENCY CODE.
PROVIDED.
PROVIDED.
PARTIAL) MESSAGES.
1086 DE49 CURRENCY CODE FOR ARBITRATION GCMS
CHARGEBACK (FULL) MESSAGES MUST CONTAIN A
VALUE OF 840 OR THE INTRA-CURRENCY AGREEMENT
SETTLEMENT CURRENCY CODE.


NUMERIC.
IS PROVIDED.
PROVIDED.
CURRENCY CODE.
HIGH-VALUES.
SPACES.
ADDITIONAL DATA 2.
MUST BE 016-999.
SPACE.


THE DE71 MESSAGE NUMBER VALUE IN THE
PREVIOUS MESSAGE.
MESSAGES.
OR ALL HIGH-VALUES.
SPACES.
CODE INVALID.
ONLY.
CODE MUST BE A SUPERMARKET ACQUIRER IF THE
SUPERMARKET INTERCHANGE PROGRAM.
MASTERCARD.
CODE MUST BE A WAREHOUSE ACQUIRER IF THE
WAREHOUSE INTERCHANGE PROGRAM.
CODE MISSING. MUST BE PRESENT IN ARBITRATION
CHARGEBACK (ATM) MESSAGES.


CODE LENGTH MUST BE 006–011
CODE INVALID.
MASTERCARD.
CODE MUST BE PRESENT IN ARBITRATION
MASTER.
DE 95 0649 DUPLICATE DE95 CARD ISSUER REFERENCE DATA. GCMS
PARTIAL) MESSAGES.
NUMERIC.
2177 DE 95 CARD ISSUER REFERENCE DATA MUST BE A Both
FIXED LENGTH OF 10.


DE124.
DATA 2 ARE PRESENT.
VALUES.
DE125.
ADDED.
OF 003.
NA_, OR POI.


PDS 0023 0596 PDS0023 TERMINAL TYPE/PDS0158S4 INTERCHANGE Both
1092 PDS0023 TERMINAL TYPE MISSING. MUST BE PRESENT Both
IN NON-REVERSAL ARBITRATION CHARGEBACK (FULL)
MESSAGES.

OR 01.


OCCURRENCE <XX>.

OCCURRENCE <XX>.

OCCURRENCE <XX>.

MESSAGES.
OCCURRENCE <XX>.



MUST BE NUMERIC.
NOT PRESENT.
PRESENT.
MUST BE PRESENT.
0735 PDS0149 CURRENCY CODES, AMOUNTS MUST BE Both
PRESENT IN ARBITRATION CHARGEBACKS (FULL AND
PARTIAL) ORIGINATING IN THE IPM FORMAT.
PROVIDED.
020.
MESSAGES.


THE MEMBER PAIR.
THE MEMBER PAIR.
LOCATION.
<AB>


MESSAGES.
001-030.
C.
0416 NO BILATERAL SETTLEMENT AGREEMENT ON FILE FOR Both
<DE93> AND <DE94>.
respectively.

(000) 000–0000 OR 000 000 0000.
1-15.


1-30.
BE 1–15.
NUMERIC.
255.
OR 2.
PDS 0241 1084 PDS0241 MASTERCOM CONTROL NUMBER MUST BE A Both
0436 PDS0260 EDIT EXCLUSION INDICATOR LENGTH MUST Both
BE 2-4.


MUST BE Y, B0 - B9, BA - BZ OR SPACES.
OR 1.
PARTIAL) MESSAGES.
This error code applies only to Arbitration Chargebacks
(Partial)/1442-454.

(Partial)/1442-454.
PDS 0268, s1 0482 AMOUNT, PARTIAL TRANSACTION MUST BE NUMERIC Both

AND GREATER THAN ZEROS.
(Partial)/1442-454.
PDS 0268, s2 0451 PDS0268S2 CURRENCY CODE, PARTIAL TRANSACTION Both

MUST CONTAIN A VALID ISO STANDARD NUMERIC
CURRENCY CODE.
(Partial)/1442-454.

PDS0268S2 CURRENCY CODE, PARTIAL TRANSACTION
MISSING. MUST BE PROVIDED.
(Partial)/1442-454.


NOT LEFT JUSTIFIED.
EXCEED 999 BYTES.

Fee Collection (Other)/1740-700, 780, 781, and 782

subfield, for Fee Collection (Other)/1740-700, 780, 781, and 782 messages.
MTI/Function Code: Fee Collection (Other)/1740-700, 780, 781, and 782

NUMERIC.
MUST BE 6-19.
RANGE INVALID.
0735 DE3 PROCESSING CODE MISSING. MUST BE PRESENT Both
IN FEE COLLECTION (OTHER) MESSAGES.
MUST BE EQUAL TO 19 OR 29 FOR FEE COLLECTION
(OTHER) MESSAGES.
DE 3, s2 0014 DE3S2 CARDHOLDER FROM – ACCOUNT MUST BE 00. Both
PROVIDED.
0735 DE4 AMOUNT TRANSACTION MISSING. MUST BE Both
PRESENT IN FEE COLLECTION (OTHER) MESSAGES.


DE 4 0738 DE4 AMOUNT, TRANSACTION EXCEEDS MAXIMUM GCMS
AMOUNT SPECIFIED FOR THE GIVEN DE25 MESSAGE
REASON CODE.
2176 DE 4 AMOUNT, TRANSACTION MUST BE NUMERIC. Both
IS PROVIDED.
0735 DE24 FUNCTION CODE MISSING. MUST BE PRESENT Both
0735 DE25 MESSAGE REASON CODE MISSING. MUST BE Both
2205 DE 25 MESSAGE REASON CODE AND DE 3 Both
PROCESSING CODE COMBINATION INVALID.
<AB>.


PROVIDED.
BE ZERO-FILLED.
01-99.
NUMERIC.
IN THE FORMAT YDDD.
NUMERIC.
DE 33 0735 DE33 FORWARDING INSTITUTION ID CODE MISSING. Both
MUST BE PRESENT IN FEE COLLECTION (OTHER)
MESSAGES.
FOR FEE COLLECTION (OTHER) MESSAGES.
NUMERIC.
MUST BE 006-011.


OR ALL HIGH-VALUES.
SPACES.
99.
22.
EXCEED 13.
LEFT JUSTIFIED.


CODE.
DE62.
0735 DE48 ADDITIONAL DATA MUST BE PRESENT IN FEE Both
CURRENCY CODE.
PROVIDED.
PROVIDED.
0735 DE49 CUURENCY CODE, TRANSACTION MISSING. Both
MUST BE PRESENT IN FEE COLLECTION (OTHER)
MESSAGES.
NUMERIC.
IS PROVIDED.
PROVIDED.
CURRENCY CODE.


ADDITIONAL DATA 2.
MUST BE 016-999.
SPACE.
THE DE71 MESSAGE NUMBER VALUE IN THE
PREVIOUS MESSAGE.
0735 DE71 MESSAGE NUMBER MISSING. MUST BE PRESENT Both
OR ALL HIGH-VALUES.
SPACES.
DE 73 0747 INVALID DATE, ACTION. MUST BE VALID YYMMDD, Both
YYMM00, OR ALL ZEROS.


CODE INVALID.
CODE IS DESIGNATED FOR INTERNAL USE BY
MASTERCARD.
CODE MISSING. MUST BE PRESENT IN FEE
CODE LENGTH MUST BE 006–011.
CODE INVALID.
MISSING. MUST BE PRESENT IN FEE COLLECTION
(OTHER) MESSAGES.
MASTER.
999.
DE124.
DATA 2 ARE PRESENT.


VALUES.
999.
DE125.
999.
ADDED.
PDS 0137 0375 PDS0137 FEE COLLECTION CONTROL NUMBER MUST Both
BE NUMERIC.
BE PRESENT.


PDS 0137 0756 PDS0137 FEE COLLECTION CONTROL NUMBER Both
BE PRESENT.
OCCURRENCE <XX>.


MUST BE NUMERIC.
NOT PRESENT.
PRESENT.
PROVIDED.


PDS 0158, s1 2227 PDS0158S1 INVALID. MUST BE <VALLIST>. Both
THE MEMBER PAIR.
<AB>
1-15.
0735 PDS0165 SETTLEMENT INDICATOR MISSING. MUST BE Both
C.
0416 NO BILATERAL SETTLEMENT AGREEMENT ON FILE FOR Both
<DE93> AND <DE94>.
respectively.


OR 2.
OR 1.
PDS 0265 0446 PDS0265 INITIAL PRESENTMENT/FEE COLLECTION Both
DATA CANNOT BE ALL LOW-VALUES OR ALL HIGH-
VALUES.
0447 PDS0265 INITIAL PRESENTMENT/FEE COLLECTION Both
DATA LENGTH MUST BE 004-110.
PDS 0265, s1 0448 PDS0265S1 INITIAL MESSAGE REASON CODE MUST BE Both
A VALID MESSAGE REASON CODE.
PDS 0265, s2 0449 PDS0265S2 DATE, INITIAL PRESENTMENT BUSINESS Both
MUST BE VALID YYMMDD OR ZEROS IN FEE
PDS 0265, s3 2208 PDS0265S3 DATA RECORD CANNOT BE ALL ZEROS OR Both
ALL SPACES.
PDS 0266 0268 PDS0266 FIRST CHARGEBACK/FEE COLLECTION Both
RETURN DATA CANNOT BE ALL LOW-VALUES OR ALL
HIGH-VALUES.
0826 PDS0266 FIRST CHARGEBACK/FEE COLLECTION Both
RETURN DATA MUST BE 004 - 127.
PDS 0266, s7 2208 PDS0266S7 DATA RECORD FIRST RETURN CANNOT BE Both
PDS 0267 0468 PDS0267 SECOND PRESENTMENT/FEE COLLECTION Both
RESUBMISSION DATA CANNOT BE ALL LOW-VALUES
OR ALL HIGH-VALUES.
0469 PDS0267 SECOND PRESENTMENT/FEE COLLECTION Both
RESUBMISSION DATA MUST BE 004 - 127.


PDS 0267, s7 2208 PDS0267S7 SECOND PRESENTMENT/FEE COLLECTION Both
RESUBMISSION DATA SECOND RETURN CANNOT BE
NOT LEFT JUSTIFIED.
EXCEED 999 BYTES.

File Trailer/1644-695
subfield, for File Trailer (member generated and MasterCard-generated/
1644-695 messages.
MTI/Function: File Trailer/1644-695

DE 24 0061 DE24 FUNCTION CODE MUST BE NUMERIC Both
0735 DE24 FUNCTION CODE MUST BE PRESENT IN FILE Both
TRAILER MESSAGES.
DE62.
0735 DE48 ADDITIONAL DATA MUST BE PRESENT IN FILE Both
TRAILER MESSAGES.
DE 71 0070 DE71 MESSAGE NUMBER MUST BE NUMERIC Both
0149 DE71 MESSAGE NUMBER MUST BE GREATER THAN THE Both
DE71 MESSAGE NUMBER VALUE IN THE PREVIOUS
MESSAGE.
0735 DE71 MESSAGE NUMBER MUST BE PRESENT IN FEE Both
PDS 0025 0503 PDS0025 MESSAGE REVERSAL INDICATOR NOT Both
ALLOWED IN FILE TRAILER.
PDS 0105 0351 PDS0105 FILE ID MUST BE A FIXED LENGTH OF 025. Both
0507 IPM FILE TRAILER/1644-695 MESSAGE MUST BE THE Both
LAST MESSAGE IN A PHYSICAL TRANSMISSION.
0508 IPM FILE TRAILER/1644-695 MESSAGE MISSING. Both
0510 FILE TRAILER REJECTED BECAUSE ALL DETAILS IN FILE Both
REJECTED.
0517 INVALID PDS0105 FILE ID IN FILE TRAILER/1644-695. Both
SHOULD BE THE SAME AS THAT IN THE FILE HEADER.
0735 PDS0105 FILE ID MISSING. MUST BE PRESENT IN FILE Both
TRAILER MESSAGES.

MTI/Function: File Trailer/1644-695

PDS 0301 0489 PDS0301 FILE AMOUNT, CHECKSUM MUST BE Both
NUMERIC.
0490 PDS0301 FILE AMOUNT, CHECKSUM LENGTH MUST BE Both
0519 PDS0301 FILE AMOUNT, CHECKSUM IS NOT ZEROS, Both
AND DOES NOT EQUAL THE TOTAL OF AMOUNT,
TRANSACTION (DE4) FROM EACH DETAIL MESSAGE.
0735 PDS0301 FILE AMOUNT, CHECKSUM MUST BE PRESENT Both
IN FILE TRAILER MESSAGES.
PDS 0306 0453 PDS0306 FILE MESSAGE COUNTS MUST BE NUMERIC. Both
0454 PDS0306 FILE MESSAGE COUNTS LENGTH MUST BE A Both
FIXED LENGTH OF 8.
0456 PDS0306 FILE MESSAGE COUNTS IS NOT ZEROS, AND Both
DOES NOT EQUAL THE TOTAL NUMBER OF MESSAGES
(INCLUDING FILE HEADER AND FILE TRAILER) IN THE
LOGICAL FILE.
0735 PDS0306 FILE MESSAGE COUNTS MUST BE PRESENT IN Both
FILE TRAILER MESSAGES.
EXCEED 999 BYTES.


I PM Clearing Format

Uploaded by

Document Information

Original Description:

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

I PM Clearing Format

Uploaded by

Copyright:

Available Formats

Return to Menu

Information about this Replacement

Please refer to:

• “Summary of Changes” for a comprehensive list of changes reflected in

We continually strive to improve our publications. Your input will help us

IPM Clearing Formats, May 2004

Change Summary Description of Change Where to Look

Removed Comments Removed the “Comments” column from message Chapter 2

Divided PDS Divided the Private Data Subelements (PDS) Chapter 8

This material may not be duplicated, published, or disclosed, in

All third-party product and service names are trademarks or

Media This document is available:

MasterCard International Incorporated

© 2004 MasterCard International Incorporated

Using this Manual

Excerpted Text ....................................................................................................... 3

Language Use ......................................................................................................... 3

Functionality Not Initially Supported .................................................................... 4

IPM Offline Message Structure............................................................................1-3

IPM Offline File Structure ...................................................................................1-8

© 2004 MasterCard International Incorporated

Chapter 2 File Header and Trailer Messages

File Header/1644 Messages.................................................................................2-1

File Trailer/1644 Messages ..................................................................................2-2

Member-Generated Files .....................................................................................2-2

MasterCard-Generated Files ................................................................................2-5

Data Element Flow..............................................................................................2-9

Message Format Data Element Requirements ..................................................2-10

Data Element Usage in Messages .....................................................................2-11

Data Elements and PDSs Not Initially Supported ............................................2-11

Intra-European Transactions .............................................................................2-12

Maestro and Cirrus Transactions.......................................................................2-12

File Header (Member-Generated)/1644 ...........................................................2-13

File Header (MasterCard-Generated)/1644.......................................................2-14

File Trailer (Member-Generated)/1644.............................................................2-15

File Trailer (MasterCard-Generated)/1644 ........................................................2-16

© 2004 MasterCard International Incorporated

Chapter 3 Presentment, Addendum, and Chargeback

First Presentment/1240 Messages .......................................................................3-1

Financial Detail Addendum/1644 Messages.......................................................3-1

First Chargeback/1442 and Arbitration Chargeback/1442 Messages ..............3-10

Second Presentment/1240 Messages ................................................................3-10

Data Element Flow............................................................................................3-11

Message Format Data Element Requirements ..................................................3-12

Data Element Usage in Messages .....................................................................3-13

Data Elements and PDSs Not Initially Supported ............................................3-13

Intra-European Transactions .............................................................................3-14

Maestro and Cirrus Transactions.......................................................................3-14

© 2004 MasterCard International Incorporated

Financial Detail Addendum (Passenger Transport Detail—

Financial Detail Addendum (Passenger Transport Detail—

Financial Detail Addendum (Vehicle Rental Detail)/1644...............................3-31

Financial Detail Addendum (Lodging Summary)/1644 ...................................3-37

Financial Detail Addendum (Temporary Services)/1644.................................3-46

Financial Detail Addendum (Shipping/Courier Services)/1644.......................3-51

Financial Detail Addendum (Payment Transaction Detail)/1644 ....................3-57

Financial Detail Addendum (Telephony Billing Service)/1644 .......................3-59

Financial Detail Addendum (Electronic Invoices)/1644 ..................................3-70

Financial Detail Addendum (Corporate Card Common Data

Financial Detail Addendum (Corporate Fleet Transaction

Financial Detail Addendum (Corporate Line Item Detail)/1644 .....................3-89

Financial Detail Addendum (Generic Detail)/1644..........................................3-94