MC IPMClearingFormats
MC IPMClearingFormats
16 April 2024
IP
Contents
Contents
Use of the Electronic Invoice addendum messages with other addendum messages...94
Message layout for Financial Detail Addendum (Electronic Invoice, Transaction
Data)/1644................................................................................................................................. 95
Message layout for Financial Detail Addendum (Electronic Invoice, Party
Information)/1644..................................................................................................................... 96
Financial Detail Addendum (Payment Transaction Detail)/1644...........................................97
Financial Detail Addendum (Telephony Billing Services)/1644................................................99
Message Layout for Financial Detail Addendum (Telephony Billing, Detail)/1644...... 102
Financial Detail Addendum (Travel Agency Detail)/1644......................................................104
Financial Detail Addendum (Lodged Account Detail)/1644..................................................106
Financial Detail Addendum (Private Label Common Data)/1644....................................... 107
Financial Detail Addendum (Private Label Line Item Detail)/1644..................................... 109
Financial Detail Addendum (Healthcare)/1644.......................................................................112
Financial Detail Addendum (Corporate Card Common Data Requirements)/1644.........114
Financial Detail Addendum (Corporate Fleet Transaction Information)/1644..................118
Financial Detail Addendum (Corporate Line Item Detail)/1644.......................................... 121
Financial Detail Addendum (Generic Detail)/1644................................................................. 126
First Chargeback/1442 and Arbitration Chargeback/1442 messages.................................... 127
Second Presentment/1240 messages............................................................................................133
DE 71 (Message Number)..................................................................................................................380
DE 72 (Data Record).......................................................................................................................... 383
DE 73 (Date, Action).......................................................................................................................... 384
DE 93 (Transaction Destination Institution ID Code)...................................................................385
DE 94 (Transaction Originator Institution ID Code)..................................................................... 388
DE 95 (Card Issuer Reference Data)................................................................................................391
DE 100 (Receiving Institution ID Code)...........................................................................................392
DE 105 (Multi-Use Transaction Identification Data)....................................................................395
Subelement 001 (Transaction Link ID [TLID]).......................................................................... 396
DE 111 (Amount, Currency Conversion Assessment).................................................................. 397
DE 123 (Additional Data 3)...............................................................................................................398
DE 124 (Additional Data 4)...............................................................................................................401
DE 125 (Additional Data 5)...............................................................................................................404
DE 127 (Network Data).....................................................................................................................407
Notices..................................................................................................................................................1304
Summary of Changes
Revised values in PDS 0052, and PDS 0185 and Subfield 1 (Security Protocol)
PDS 0186 Subfield 2 (Cardholder Authentication)
Subfield 3 (UCAF Collection Indicator)
PDS 0185 (Accountholder Authentication Value)
PDS 0186 (Program Protocol)
PDS 0052 and DE 22s7 revised for clarity. PDS 0052 (Electronic Commerce Security Level
Indicator)
Clearing introduction............................................................................................................................................29
Transaction processing flow through the clearing system.......................................................................30
IPM offline message structure............................................................................................................................34
IPM offline file structure......................................................................................................................................39
Basic clearing system message flow............................................................................................................41
IPM data element information........................................................................................................................... 42
IPM data element flow...................................................................................................................................42
Message format data element requirements............................................................................................ 42
Data element usage in messages.................................................................................................................43
Clearing introduction
Clearing by means of the Integrated Product Messages (IPM) format is the movement of
transaction information from the customer to the clearing system or from the clearing system
to the customer.
Offline clearing
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 customer places messages into a clearing file 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
customers since the last cutoff. For more information on offline message structure, see IPM
offline message structure. Refer to the GCMS Reference Manual for processing times.
Transaction histories
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 is eventually
presented for payment via the cardholder statement. If the issuer disputes the data, customers
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.
Chargeback cycles
Customers are not required to exhaust all chargeback cycles once they start the chargeback
process to achieve dispute resolution. Refer to the Chargeback Guide for more information on
chargebacks.
This diagram depicts the transaction processing flow for fee collection transactions.
After collecting clearing data and routing it to the appropriate receiver, settlement occurs, which
is the process of exchanging funds among customers. Refer to the Settlement Manual for
settlement information.
Data elements
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. For more information on data elements, see Data element definitions.
Subelements
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. For PDS encoding information, refer to DE 48 (Additional Data), in
Data element definitions.
IPM messages
Each IPM message contains these data elements.
• Primary Bit Map: indicates the presence or absence of DE 1 (Secondary Bit Map) through DE
64 (Message Authentication Code [MAC]).
• DE 1 (Secondary Bit Map): indicates the presence or absence of DE 65 (Reserved [ISO])
through Clearing DE 128 (Message Authentication Code [MAC]).
• DE 24 (Function Code): is a three-digit data element that indicates the specific purpose of a
message in a message class.
• Message Type Identifier: describes each message class and function.
Positions Description
1–4 MTI (always present)
1 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.
Positions Description
21–xx Field indicating length of first data element, in
numeric order, in message after DE 1, if
corresponding data field is variable length
The two fields in this table are repeated until all the data elements in the bit maps are
presented.
Length fields
The indicator in the length field is right-justified with leading zeros, as shown in this table.
21–22 length of DE 2 16
2 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.
94–95 length of DE 94 06
Bitmaps
Set in binary format, the Primary Bit Map consists of this arrangement of bits from the previous
example.
Figure 1: Bitmap 1
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.
Set in binary format, DE 1 (Secondary Bit Map) consists of this arrangement of bits in the
previous example.
Figure 2: Bitmap 2
Bit seven indicates that 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 that DE 94 is present. (Calculated by adding 64+30=94.)
NOTE: References to data elements include data elements, PDSs (“p….” in the message layouts), and
subfields (“s…” in the message layouts).
In the message format layouts, 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, or modify
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.
The usage code for each of the subfields is the same as that of its parent data element or
private data subelement unless specified differently in the table.
Message type identifiers and associated function codes of File Header and Trailer messages............. 46
Customer-generated files................................................................................................................................... 46
Files generated by Mastercard...........................................................................................................................49
Mastercard-generated file sequence...........................................................................................................49
Early reconciliation file sequence..................................................................................................................51
File Header/1644 messages............................................................................................................................... 52
File Trailer/1644 messages................................................................................................................................. 53
This section also describes the structure of offline IPM clearing files and transmissions.
Customer-generated files
This section distinguishes between offline files and offline transmissions.
Offline files
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 Private
Data Subelement (PDS) 0105 (File ID) uniquely identifies each file.
Offline transmissions
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 PDS 0110 (Transmission ID) in each logical file’s File Header/1644. The
clearing system does not provide PDS 0110 in files sent to receiving customers.
Transmission originators
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 customer. Another originator may choose to create a separate logical file for
Chargebacks and Retrievals as opposed to Presentments.
exceeded, then customers will be impacted by not receiving early reconciliation for the physical
file and could miss the desired settlement cycle.
• 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.
• DE 71 (Message Number) 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, Retrieval Request Acknowledgment/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. Customers
may choose to submit messages from several different sending customer IDs in the same
logical file.
File IDs
File originators must create a unique PDS 0105 (File ID) value for each logical file. PDS 0105
includes these items:
• File type: Indicates whether Mastercard or the customers generate the file. This includes
clearing files or Early Reconciliation files generated by Mastercard.
• File reference date: Indicates the date the originator processed or created the file.
• Processor ID: For customer-generated files, indicates the customer ID of the customer or
processor sending the file. For files generated by Mastercard, the Processor ID indicates the
customer ID of the customer or processor receiving the file.
• 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 modes
File originators must indicate each logical file’s PDS 0122 (Processing Mode) value. PDS 0122
indicates:
• Production file or
• Test file.
The PDS 0122 value in the File Header/1644 applies to all transactions in the logical file.
GCMS generates data for customers at each of the six clearing cutoffs. Customers and
processors may choose to receive clearing data four, five, or six times per day. However, the
choice to receive data fewer than six times per day results in the customer’s clearing activity
being merged 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 files generated by Mastercard as shown in this table.
When there are multiple message types (for example, multiple first presentments) for multiple
receiving customer IDs, the clearing system sequences them as follows:
• All message types except 1644-693 (Text Message) and 1644-640 (Currency Update): first
by receiving customer ID and then by message type
• 1644-693 (Text Message) and 1644-640 (Currency Update) messages: once per processor by
the first occurring (lowest) customer ID and then by message type
If a customer or processor processes for multiple customer IDs, GCMS constructs the file
generated by Mastercard. For example, suppose that customer (processor) ID 004444, endpoint
1, processes for customer ID 002222 and customer ID 003333. When processing for multiple
customer IDs, GCMS would construct the receiver’s file as shown in this table.
Endpoint 1, to Customer ID
MTI-function code Description (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
Endpoint 1, to Customer ID
MTI-function code Description (ICA)
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-685 Financial Position Detail 003333
1644-695 File Trailer 004444
Reconciliation files
If the customer sends a physical file containing two logical files, GCMS will return one early
reconciliation file. The acknowledgment 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.
Endpoint 1, to Customer ID
MTI-function code Description (ICA)
1644-697 File Header 004444
1644-680 File Currency Summary 002222
Endpoint 1, to Customer ID
MTI-function code Description (ICA)
1644-685 Financial Position Detail 003333
1644-691 Message Exception 005555
1644-685 Financial Position Detail 005555
1644-691 Message Exception 006666
1644-685 Financial Position Detail 006666
1644-695 File Trailer 004444
NOTE: This example assumes that data for all customers 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.
Message type identifiers and associated function codes of presentment, addendum, and
chargeback messages..........................................................................................................................................56
First Presentment/1240 messages...................................................................................................................56
Financial Detail Addendum/1644 messages...................................................................................................63
Financial Detail Addendum/1644 messages listed by usage code........................................................ 63
Financial Detail Addendum (Passenger Transport Detail, General Ticket Information)/1644......... 64
Financial Detail Addendum (Passenger Transport Detail, Rail Data)/1644........................................ 69
Financial Detail Addendum (Passenger Transport Detail, Trip Leg Data)/1644.................................73
Financial Detail Addendum (Vehicle Rental Detail)/1644....................................................................... 78
Financial Detail Addendum (Lodging Summary)/1644...........................................................................82
Financial Detail Addendum (Temporary Services)/1644.........................................................................87
Financial Detail Addendum (Shipping/Courier Services)/1644..............................................................89
Financial Detail Addendum (Electronic Invoices)/1644............................................................................92
Use of the Electronic Invoice addendum messages with other addendum messages.................. 94
Message layout for Financial Detail Addendum (Electronic Invoice, Transaction Data)/1644... 95
Message layout for Financial Detail Addendum (Electronic Invoice, Party Information)/1644.. 96
Financial Detail Addendum (Payment Transaction Detail)/1644.......................................................... 97
Financial Detail Addendum (Telephony Billing Services)/1644...............................................................99
Message Layout for Financial Detail Addendum (Telephony Billing, Detail)/1644..................... 102
Financial Detail Addendum (Travel Agency Detail)/1644..................................................................... 104
Financial Detail Addendum (Lodged Account Detail)/1644.................................................................106
Financial Detail Addendum (Private Label Common Data)/1644...................................................... 107
Financial Detail Addendum (Private Label Line Item Detail)/1644.....................................................109
Financial Detail Addendum (Healthcare)/1644...................................................................................... 112
Financial Detail Addendum (Corporate Card Common Data Requirements)/1644........................114
Financial Detail Addendum (Corporate Fleet Transaction Information)/1644.................................118
Financial Detail Addendum (Corporate Line Item Detail)/1644..........................................................121
Financial Detail Addendum (Generic Detail)/1644................................................................................ 126
First Chargeback/1442 and Arbitration Chargeback/1442 messages................................................... 127
Second Presentment/1240 messages........................................................................................................... 133
The Data Element (DE) 24 (Function Code) in each message indicates the transaction’s primary
type or function, and the DE 25 (Message Reason Code) indicates the primary reason for the
transaction.
One occurrence of this addendum message may be provided if the associated First
Presentment/1240 message contains a travel agency MCC and is submitted for one of the U.S.
region incentive interchange rate programs listed in this table.
Financial Detail Addendum (Passenger Transport Detail, General Ticket Information)/1644, cont.
This addendum message may be provided only if the associated First Presentment/1240
contains an airline, railway, or travel agency MCC in DE 26 (Acceptor Business Code).
If the First Presentment/1240 message associated with this addendum is submitted for an
incentive interchange program that requires only this addendum, and the associated First
Presentment/1240 message is submitted for a railway or travel agent MCC in DE 26, the
Financial Detail Addendum (Passenger Transport Detail, Rail Data)/1644 message can be used
in addition to this addendum message.
For specific corporate transactions occurring in the U.S. region, Corporate Card Common Data
is also required.
The clearing system always will 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 submitted as:
• Credit: DE 3 (Processing Code), subfield 1 = 20
• Reversal: PDS 0025 (Message Reversal Indicator), subfield 1 = R
• Collection Only transaction: PDS 0165 (Settlement Indicator), subfield 1 = C, or
• A transaction submitted for Standard interchange program (U.S. region and international
IRDs 01, 61, 63, 65, 75, 85, 95, RU, or WA) as defined by Mastercard.
For information about the individual PDS requirements for this addendum and for the specific
incentive interchange programs, please refer to Private data subelement definitions or to the
applicable sections of the Interchange Manual.
Financial Detail Addendum (Passenger Transport Detail, General Ticket Information)/1644 message
layout
This new message supports rail transaction information. Acquirers may submit 1–999
occurrences of this message. Each occurrence provides detailed data for one trip leg of the
associated rail transaction.
When using this message, the information in PDS 0501, subfields 1–3, must be these values:
• Usage Code: 01
• Industry Record Number: 002
• Occurrence Indicator: 001–999
This addendum message may be provided only if the associated First Presentment/1240
contains a rail or travel agency MCC in DE 26 (Acceptor Business Code).
The submission of this addendum is optional. Acquirers may provide a Financial Detail
Addendum (Passenger Transport Detail, Rail Data)/1644 message (Usage Code 01, Industry
Record Number 002,) under these circumstances:
• For U.S. region incentive interchange rate programs that require a Financial Detail
Addendum (Passenger Transport Detail, General Ticket Information)/1644 and a Financial
Detail Addendum (Passenger Transport Detail, Trip Leg Data)/1644, the acquirer may
submit the Rail Data addendum in place of the Trip Leg Data addendum.
This table lists U.S. region interchange programs requiring a General Ticket addendum and Trip
Leg Data or Rail Data addendum.
U.S. region Interchange Programs requiring a General Ticket addendum and Trip Leg Data or Rail Data
addendum
For other incentive interchange rate programs that do not require an addendum, the Rail Data
addendum may be submitted by itself, or in addition to any other applicable addendum.
When the Financial Detail Addendum (Passenger Transport Detail, General Ticket Information)
is provided, the occurrence indicator (PDS 0501, subfield 3) submitted for the first Rail Data
addendum should equal 002. Otherwise, it should equal 001.
For specific corporate transactions occurring in the U.S. region, Corporate Card Common Data
is also required.
Financial Detail Addendum (Passenger Transport Detail, Rail Data)/1644 Message Layout
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 International
Air Transport Association (IATA) which contains a list of standard airport and airline service
abbreviations.
Acquirers must include all trip legs of a transaction in the Financial Detail Addendum (Passenger
Transport Detail, General Ticket Information)/1644 message (Usage Code 01, Industry Record
Number 000) if they include at least one trip leg.
For railway transactions, acquirers may submit a Financial Detail Addendum (Passenger
Transport Detail, Rail Data)/1644 message in addition to or in place of the Financial Detail
Addendum (Passenger Transport Detail, Trip Leg Data)/1644 message. One occurrence of this
addendum message must be provided if the associated First Presentment/1240 message
contains an airline or railway MCC and is submitted for one of the U.S. region incentive
interchange rate programs listed in this table. Rail Data addendum message may be used
instead of or in addition to the Trip Leg data when a rail MCC is submitted.
One occurrence of this addendum message may be provided if the associated First
Presentment/1240 message contains a travel agency MCC and is submitted for one of the U.S.
region incentive interchange rate programs listed in this table.
Financial Detail Addendum (Passenger Transport Detail, Trip Leg Data)/1644, cont.
This addendum message may be provided only if the associated First Presentment/1240
contains an airline, railway, or travel agency MCC in DE 26 (Acceptor Business Code).
If the U.S. region or international First Presentment/1240 message associated with the
addendum contains a railway or travel agent MCC in DE 26, the Financial Detail Addendum
(Passenger Transport Detail, Rail Data)/1644 message can be used in place of or in addition to
this addendum.
For specific corporate transactions occurring in the U.S. region, Corporate Card Common Data
is also required.
The clearing system always rejects this Financial Detail Addendum/1644 message if it contains
invalid data. The associated First Presentment/1240 message is also rejected if it is submitted
for a U.S. region or international interchange program, unless it is submitted as one of these:
• Credit: DE 3 (Processing Code), subfield 1= 20
• Reversal: PDS 0025 (Message Reversal Indicator), subfield 1 = R
• Collection Only transaction: PDS 0165 (Settlement Indicator),subfield 1 = C
• A transaction submitted for a Standard interchange program (U.S. region and international
IRDs 01, 61, 63, 65, 75, 85, 95, RU, or WA) as defined by Mastercard.
For information about the individual PDS requirements for this addendum and for the specific
incentive interchange programs listed above, please refer to Private data subelement definitions
or to the applicable sections of the Interchange Manual.
Financial Detail Addendum (Passenger Transport Detail, Trip Leg Data)/1644 Message Layout, cont.
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).
At least one occurrence of this addendum message must be provided if the associated First
Presentment/1240 contains a Vehicle Rental acceptor business code (MCC) and is submitted
for one of the U.S. region incentive interchange rate programs listed in this table.
This addendum message may be provided only if the associated First Presentment/1240
contains a vehicle MCC in DE 26 (Acceptor Business Code).
For specific corporate transactions occurring in the U.S. region, Corporate Card Common Data
is also required.
The clearing system always rejects this Financial Detail Addendum/1644 message if it contains
invalid data. The associated First Presentment/1240 message is also rejected if it is submitted
for a U.S. region or international interchange program, unless it is submitted as one of these:
• Credit: DE 3 (Processing Code), subfield 1 = 20
• Reversal: PDS 0025 (Message Reversal Indicator), subfield 1 = R
• Collection Only transaction: PDS 0165 ((Settlement Indicator), subfield 1 = C
• A transaction submitted for a Standard interchange program (U.S. region and international
IRDs 01, 61, 63, 65, 75, 85, 95, or RU, or WA) as defined by Mastercard
For information about the individual PDS requirements for this addendum and for the specific
incentive interchange programs listed above, refer to Private data subelement definitions or to
the applicable chapters of the Interchange Manual.
• Usage Code: 06
• Industry Record Number: 000
• Occurrence Indicator: 001–999
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).
This message must be provided if the associated First Presentment/1240 contains a valid
Lodging acceptor business code (MCC) and is submitted for one of the U.S. Region incentive
interchange rate programs listed in this table.
This addendum message may be provided only if the associated First Presentment/1240
contains a lodging MCC in DE 26 (Acceptor Business Code). The clearing system always rejects a
Financial Detail Addendum (Lodging Summary)/1644 message if it contains invalid data.
The associated First Presentment/1240 message is also rejected if it is submitted for a U.S.
region or international interchange program, unless it is submitted as:
• Credit: DE 3 (Processing Code), subfield 1 = 20
• Reversal: PDS 0025 (Message Reversal Indicator), subfield 1 = R
• Collection Only transaction: PDS 0165 (Settlement Indicator), subfield 1 = C
• A transaction submitted for a Standard interchange program (U.S. region and international
IRDs 01, 61, 63, 65, 75, 85, 95, RU, or WA) as defined by Mastercard
Whenever the Financial Detail Addendum (Lodging Summary)/1644 message is present, and
the transaction involves one of the Mastercard Corporate Cards, these optional addendum
messages may be provided:
• Corporate Card Common Data Requirement, usage code 98, industry record number 000, or
• Corporate Card Line Item Detail, usage code 98, industry record number 950.
For specific corporate transactions occurring in the United States, Corporate Card Common
Data is also required.
For information about the individual PDS requirements for this addendum and for the specific
incentive interchange programs listed, refer to Private data element definitions or to the
applicable sections of the Interchange Manual.
For specific corporate transactions occurring in the U.S. region, Corporate Card Common Data
is also required.
than 999. There is a minimum of one occurrence and a maximum of six occurrences of
Electronic Invoice (Party Information).
• Message Number: DE 71 from the First Presentment/1240 message
This message is optional; however, GCMS rejects 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 is also rejected unless it was submitted in one
of these ways:
• Credit: DE 3 (Processing Code), subfield 1 = 20
• Reversal: PDS 0025 (Message Reversal Indicator), subfield 1 = R
• Collection Only transaction: PDS 0165 (Settlement Indicator), subfield 1 = C
These addendum messages are designed to carry electronic invoice data that is not present in
other addendum messages, and to enable issuers to supply more transaction information to
their corporate clients. These addendum messages provide additional information passed
between buyer and seller in business-to-business (B2B) and electronic-business-to-business
(eB2B) transactions.
These are the electronic invoice addendum messages:
• 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.
Here is general information about the 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 optionally may
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 PDS 0501 [Transaction Indicator], subfield 3
[Occurrence Indicator]) of the Electronic Invoice (Transaction Data) addendum is variable.
– The number of occurrences (provided in 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 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 rejects messages that contain invalid data. The associated First Presentment/1240
message is also rejected unless it was submitted as:
– Credit: DE 3 ( Processing Code), subfield 1 = 20
– Reversal: PDS 0025 (Message Reversal Indicator), subfield 1 = R
– Collection Only transaction: PDS 0165 (Settlement Indicator), subfield 1 = C
– A transaction submitted for a Standard interchange program (U.S. region and
international 01, 61, 63, 65, 75, 85, 95, RU, or WA) as defined by Mastercard
Use of the Electronic Invoice addendum messages with other addendum messages
These are the rules for using the electronic invoice addendum messages with other 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.
Message layout for Financial Detail Addendum (Electronic Invoice, Transaction Data)/1644
The Electronic Invoice (Transaction Data) addendum provides information about each
transaction.
This table shows the message layout.
Message layout for Financial Detail Addendum (Electronic Invoice, Party Information)/1644
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.
This table provides the layout for the Financial Detail Addendum (Electronic Invoice, Party
Information)/1644 message.
Message layout for Financial Detail Addendum (Electronic Invoice, Party Information)/1644
C59, or C65. All acquirers of payment transactions are required to submit PDS 0670 (Payer/
User Information), PDS 0671 (Date of Funds Requested), and PDS 0674 (Additional Trace/
Reference Number used by Acceptor).
The clearing system rejects this Financial Detail Addendum/1644 message if it contains invalid
data. The associated First Presentment/1240 message is also rejected if it is submitted for a
U.S. region or international interchange program, unless it is submitted as:
• Credit: DE 3 ( Processing Code), subfield 1 = 20
• Reversal: PDS 0025 (Message Reversal Indicator), subfield 1 = R
• Collection Only transaction: PDS 0165 (Settlement Indicator), subfield 1 = C
• A transaction submitted for a Standard interchange program (U.S. region and international
IRDs 01, 61, 63, 65, 75, 85, 95, RU, or WA) as defined by Mastercard
This table shows the message layout.
The clearing system rejects this Financial Detail Addendum/1644 message if it contains invalid
data. If this addendum message is rejected for invalid data, the First Presentment/1240
message is not rejected.
This table provides the layout for the Financial Detail Addendum (Private Label Common Data)/
1644 message.
used. It includes information relevant to private label transactions for participants in the
Mastercard Private Label Program.
When this message is used, the information in PDS 0501 (Transaction Description), subfields 1–
3, must be these values:
• Usage code: 14
• Industry Record Number: 001
• Occurrence Indicator: 002–999
This addendum message supports a single private label card transaction with multiple line item
details. This message may be repeated from 1 to 998 times for each private label card
transaction. Each occurrence represents a single line item for a private label card transaction.
This addendum message is optional. However, submission of the Private Label Line Item Detail
addendum message requires the submission of the Financial Detail Addendum (Private Label
Common Data)/1644 message. The Private Label Common Data addendum must precede the
Private Label Line Item Detail addendum.
The clearing system rejects this Financial Detail Addendum/1644 message if it contains invalid
data. If this addendum message is rejected for invalid data, the First Presentment/1240
message is not rejected.
This table provides the layout for the Financial Detail Addendum (Private Label Line Item
Detail)/1644 message.
Financial Detail Addendum (Private Label Line Item Detail)/1644 message layout
United States acquired Mastercard Commercial Fleet Card transactions occurring at fuel
locations.
Acquirers should provide the Financial Detail Addendum (Corporate Card Common Data
Requirements)/1644 message containing PDS 0608 (Destination Postal Code), PDS 0609
(Destination State/Province Code), PDS 0610 (Destination Country Code), and PDS 0613
(Ship-From Postal Code) from U.S. acceptors for all commercial card transactions in which
goods were shipped. All goods in a transaction must be shipped from one location and received
at one location.
This table provides the message layout.
Financial Detail Addendum (Corporate Card Common Data Requirements)/1644 message layout
Inter-regional transactions
This addendum message must be provided if the associated First Presentment/1240 message
is for a transaction that meets these conditions:
• It is a Mastercard Corporate Card.
• The transaction is submitted for one of the incentive interchange rate programs listed in this
table.
Inter-regional transactions
Incentive Interchange Rate Programs for Mastercard Corporate Fleet Card transactions
This addendum message may be provided only if the associated First Presentment/1240
message is for a transaction that was completed with a Mastercard Corporate Fleet Card at a
fuel location.
The clearing system rejects this Financial Detail Addendum/1644 message if it contains invalid
data. The associated First Presentment/1240 message is also rejected if it is submitted for a
U.S. region or international interchange program, unless it is submitted as:
• Credit: DE 3 (Processing Code), subfield 1 = 20
• Reversal: PDS 0025 (Message Reversal Indicator), subfield 1 = R
• Collection Only transaction: PDS 0165 (Settlement Indicator), subfield 1 = C
• A transaction submitted for a Standard interchange program (U.S. region and international
IRDs 61, 63, or 65) as defined by Mastercard
For U.S. region acceptors, the submission of this addendum requires the submission of a
Financial Detail Addendum (Corporate Card Common Data)/1644 message.
This table provides the message layout.
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.
When this message is used, the information in PDS 0501, subfields 1–3, must be these values:
• Usage Code: 98
• Industry Record Number: 950
• Occurrence Indicator: 002–999
This message supports a single corporate program transaction with multiple line item details. It
may be repeated from 001 to 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.
This message must be provided if any of these conditions are met:
• The associated First Presentment/1240 is submitted for one of the above interchange
programs, and it contains a shipping/courier MCC in DE 26 (Acceptor Business Code), in
which case the acquirer must provide either the Financial Detail Addendum (Shipping/
Courier Services)/1644 message or the Financial Detail Addendum (Corporate Line Item
Detail)/1644 message.
• The associated First Presentment/1240 is submitted for one of the above interchange
programs, and it contains a temporary services MCC in DE 26, in which case the acquirer
must provide the Financial Detail Addendum (Temporary Services)/1644 message. The
Financial Detail Addendum (Corporate Line Item Detail)/1644 message is not required.
• The associated First Presentment/1240 is a Mastercard Corporate Purchasing Card,
Mastercard Business Card, Mastercard Corporate Card, or Mastercard Corporate Fleet Card
(at a non-fuel location) transaction and is submitted for one of the interchange programs
listed in this table unless the transaction is a shipping/courier or temporary services
transaction.
This message must be provided if the associated First Presentment/1240 meets all of this
criteria:
• The Product Code is MCP or MCF at a non-fuel location.
• The Business Service is equal to one of the items in this table.
Financial Detail Addendum (Corporate Line Item Detail)/1644, Business Service information
NOTE:
This applies to additional domestic arrangements within the Europe region.
The IRD submitted in the associated First Presentment/1240 is one of the items listed in this
table.
IRD Description
26 Purchasing Large Ticket Level 1 Interchange
27 Purchasing Large Ticket Level 2 Interchange
This addendum message may be provided only if the associated First Presentment/1240 is for a
transaction that was completed with one of the Mastercard Corporate Cards.
The submission of this addendum requires the submission of a Financial Detail Addendum
(Corporate Card Common Data)/1644 message.
The clearing system rejects this Financial Detail Addendum/1644 message if it contains invalid
data. The associated First Presentment/1240 message is also rejected if it is submitted for a
U.S. region or international interchange program, unless it is submitted as:
• Credit: DE 3 (Processing Code), subfield 1 = 20
• Reversal: PDS 0025 (Message Reversal Indicator), subfield 1 = R
• Collection Only transaction: PDS 0165 (Settlement Indicator), subfield 1 = C
• A transaction submitted for a Standard interchange program (U.S. region and international
IRDs 61, 63, or 65) as defined by Mastercard
This table provides the message layout.
Message Type Identifiers and Associated Function Codes of Retrieval and Fee Collection
messages............................................................................................................................................................. 141
Retrieval Request/1644 messages..................................................................................................................141
Retrieval Request Acknowledgment/1644 messages................................................................................. 145
Fee Collection messages...................................................................................................................................149
Fee Collection (Retrieval Fee Billing)/1740.............................................................................................. 150
Fee Collection (Handling Fees)/1740........................................................................................................153
Fee Collection (Other than Retrieval Fee Billing/Handling Fees)/1740..............................................157
Message Type Identifiers and Associated Function Codes of Retrieval and Fee Collection messages
Fee Collection (Other than Retrieval Fee Billing/Handling Fees)/1740 message layout
Message Type Identifiers and Associated Function Codes of reconciliation messages......................... 162
Activity types accumulated by reconciliation messages..............................................................................162
Function Codes used..........................................................................................................................................162
Message Reason Codes used............................................................................................................................163
Reconciliation messages....................................................................................................................................163
Acknowledgment messages........................................................................................................................163
Notification messages..................................................................................................................................164
Reconciliation message totals.................................................................................................................... 164
Reconciliation Amount/Reconciliation Fee totals....................................................................................165
Debit/Credit totals..................................................................................................................................166
Reconciliation category summary..............................................................................................................169
Reconciliation category definitions............................................................................................................171
File Currency Summary/1644 messages....................................................................................................... 177
Financial Position Detail/1644 messages......................................................................................................179
Settlement Position Detail/1644 messages................................................................................................. 181
DEFINITION:
Acknowledgment is a type of IPM reconciliation message confirming activity that the customer sent to
GCMS.
Notification is a type of IPM reconciliation message confirming activity that the customer received
from GCMS.
Reconciliation messages
These sections describe the reconciliation messages.
Acknowledgment messages
The acknowledgment messages contain the clearing system-calculated totals for the related
customer outbound file.
The clearing system responds to a customer-originated file by sending the customer
acknowledgment messages based on customer profile options. The clearing system calculates
totals only for accepted files and accepted financial messages.
Acknowledgment messages contain a DE 25 (Message Reason Code) value of 6861.
Notification messages
The notification messages contain the clearing system-calculated totals for the customer’s
inbound activity.
The clearing system provides notification messages for each customer inbound file based on the
customer profile options.
Notification messages contain a DE 25 value of 6862.
Value Description
M Mandatory. The data element always is present in the message.
C Conditional. The data element is present in the message if the
conditions described in the accompanying text are applicable.
N/A Not applicable
Amount, Fee,
Reconciliation Fee Processing PDS Originator Dr/Cr Receiver Dr/Cr
DE/PDS (subfield 7) Code (subfield 2) 0025 Indicator3 Indicator4
PDS Amount, Fee, 19 - Cr Dr
0146 Reconciliation
PDS Amount, Fee, 19 R Dr Cr
0146 Reconciliation
PDS Amount, Fee, 29 - Dr Cr
0146 Reconciliation
PDS Amount, Fee, 29 R Cr Dr
0146 Reconciliation
In the Financial Position Detail/1644 and the Settlement Position Detail/1644 messages, debit
fee totals are provided in reconciliation currency in PDS 0392 (Debit, Fee Amounts), credit fee
totals are provided in reconciliation currency in PDS 0393 (Credits, Fee Amounts), and the net
totals are provided in reconciliation currency in PDS 0395 (Amount, Net Fee).
Debit/Credit totals
Reconciliation messages provide separate totals for debit and credit amounts.
DE 5 (Amount, Reconciliation) reconciliation debit and credit totals are determined for the
transaction originator and transaction destination by using the transaction function (MTI and
DE 24 [Function code]), DE 3 Processing Code), and PDS 0025 (Message Reversal Indicator). For
activity other than bilaterally settled or Collection Only, transaction and fee totals are
designated as debit or credit according to the settlement impact to each customer. For
example, an original retail purchase is accumulated as a credit to the originator (the acquirer)
and a debit to the receiver (the issuer).
An acquirer always originates and an issuer always receives the financial transactions listed in
this table.
Originator Receiver
Dr/Cr Dr/Cr
Amount Indicator Indicator
MTI DE 24 DE 3 PDS 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 financial transactions listed in
this table.
Originator Receiver
Dr/Cr Dr/Cr
Amount Indicator Indicator
MTI DE 24 DE 3 PDS 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
Originator Receiver
Dr/Cr Dr/Cr
Amount Indicator Indicator
MTI DE 24 DE 3 PDS 0025 DE/PDS (Issuer) (Acquirer)
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
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 previous tables 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. The transactions are listed in this table.
Originator Receiver
Amount Dr/Cr Dr/Cr
MTI DE 24 DE 3 PDS 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
Originator Receiver
Amount Dr/Cr Dr/Cr
MTI DE 24 DE 3 PDS 0025 DE/PDS Indicator Indicator
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
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
1644-688 Settlement
1644-685 Financial 1644-685 Financial Position Detail
Position Detail Position Detail
Acknowledgment/
Category Acknowledgment Notification Notification
Reconciled, File (PDS Y or N Y or N Default
0300)
Reconciled, Account Y or N Y or N Y or N
Range (PDS 0370)
Reconciled, Member Y or N Y or N Conditional
Activity (PDS 0302)
1644-688 Settlement
1644-685 Financial 1644-685 Financial Position Detail
Position Detail Position Detail
Acknowledgment/
Category Acknowledgment Notification Notification
Reconciled, Business Y or N Y or N N/A
Activity (PDS 0358)
Settlement Indicator Y or N Y or N N/A
(PDS 0165)
Reconciled, Transaction Y or N Y or N N/A
Function (PDS 0372)
Reconciled, Processing Y or N Y or N N/A
Code (PDS 0374)
Member specified Y or N N/A N/A
Reconciliation Criteria:
Member Reconciliation
Indicator 1 (PDS 0375)
Original/Reversal Totals Y or N Y or N N/A
Indicator (PDS 0378)
Currency Code, Y or N Y or N Y or N
Transaction (DE 49)
Settlement Activity N/A N/A Default
(PDS 0359)
Card Program Identifier N/A N/A Y or N
(PDS 0367)
Transaction Function N/A N/A Y or N
Group Code (PDS 0368)
Acquirer’s BIN (PDS N/A N/A Y or N
0369)
To ensure that customers receive a complete representation of their Mastercard settled activity,
when either the account range or the Acquirer’s BIN category (or both) is selected, GCMS
automatically accumulates the totals, in PDS 0302, Reconciled, Member Activity, on the basis of
one or more of these values:
• Issuing activity
• Acquiring activity, or
• Fee collection activity.
NOTE: Customers electing to receive Settlement Position Detail messages always receive both
acknowledgment and notification messages for each settlement reconciliation category.
PDS 0105 (File ID) and PDS 0300 (Reconciled, File ID)
The file originator must create a unique File ID 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 for which the totals are
presented is provided in PDS 0300 (Reconciled, File) of the Reconciliation message.
In acknowledgment reconciliation messages, PDS 0300 contains the PDS 0105 value submitted
by the file originator in customer-generated files.
In notification reconciliation messages, PDS 0300 contains the clearing cycle delivery file ID
assigned by GCMS for files generated by Mastercard.
PDS 0300 is a default category for Settlement Position Detail/1644 messages, and an optional
category for Financial Position Detail/1644 messages. Customers who elect to receive the
reconciliation messages and choose this category receive either the Financial Position Detail/
1644 or Settlement Position Detail/1644-688 messages, or both, as selected by the customer,
grouped by this category. The File ID for which the totals are presented is provided in PDS 0300
of the reconciliation message. Customers can use these values in PDS 0300 to identify the
corresponding File ID for reconciliation to the Settlement Advisement line item totals as well as
their reconciliation reports.
Fee Collection
Acquiring Activity Issuing Activity for Activity for the
Transaction Transaction for the Customer the Customer Customer
Description Functions 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 1240–205, 282 DE 94 DE 93 N/A
Presentment
Arbitration 1442–451, 454 DE 93 DE 94 N/A
Chargeback
Fee Collection 1740–700, 780, N/A N/A DE 94 and DE 936
781, 782, 783,
7905
If selected for Financial Position Detail/1644 messages, the PDS 0302 (Reconciled, Member
Activity) category provides totals by issuing activity, acquiring activity, and fee collection activity
at the customer ID level. If selected with PDS 0370 (Account Range Category), the totals are by
issuing account range, acquiring activity (customer ID level), and fee collections (customer ID
level).
Customers cannot choose just to receive issuing activity or just fee collection activity. They
receive totals for whatever activity is processed.
This category is not offered as a settlement reconciliation category; however, GCMS
automatically generates totals for this type of activity for customers that elect reconciliation by
issuing account range, acquirers BIN, or both.
This table lists the category and related totals.
5 Transaction function 1740-790 is valid only in the IPM Pre-edit system for U.K. domestic Maestro® transactions.
6 DE 94 (Transaction Originator Institution ID Code) indicates the transaction originator, and DE 93 (Transaction
Destination ID Code) indicates the transaction receiver.
DE 3 (Processing Code) and PDS 0374 (Reconciled, Processing Code) transaction type
7 Customers selecting this option and submitting 1644-603 (Retrieval Requests; non-financial messages) will receive
reconciliation messages with zero counts and amounts.
8 Transaction function 1740-790 is valid only in the IPM Pre-edit system for UK domestic Maestro transactions.
Customers cannot choose to receive totals for specific DE 3 values. They receive totals for all DE
3 activity processed by the clearing system for which they have activity.
NOTE: The Settlement Position Detail/1644 message is delivered along with the customer's normal
activity at the end of each clearing cycle (Bulk Type T112) and will not be distributed within the IPM
Early Reconciliation File (Bulk Type T113).
Level of Destination
severity Condition Originator receives receives
Error Unparseable or unrecognizable Message Exception/1644 only Nothing
message (The rejected message is not
returned.)
Error Error in one or more supported Message Exception/1644 and the Nothing
elements rejected message itself. If
generated by the IPM Pre-edit
utility, Data Element (DE) 71
(Message Number) 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.
The Message Exception/1644 message contains a code identifying the error. It also contains the
data element numbers or private data subelement (PDS) numbers that caused the exception
conditions.
Other identifying information related to the message is presented if the clearing system can
parse the information.
For Mexico Domestic transactions, under certain condition the message is flagged for error but
it is cleared and settled. Syntax condition is not rejected. In this case, the error is indicated by
PDS 0005 and is present in the presentment, chargeback, retrieval request, and retrieval
request acknowledgment messages. Refer to the GCMS Reference Manualfor details on the
syntax error Messages.
This table provides the message contents.
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 codes, severity codes, and data element and PDS
numbers in error
PDS 0025 Reversal Indicator of the exception message (if the clearing system
can parse)
PDS 0138 DE 71 (Message Number) of the exception message (if the clearing
system can parse)
PDS 0165 Settlement Indicator of the exception message (if the clearing
system can 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 PDS 0105 (File ID) of the file containing the exception message
(from the File Header/1644, if present and if the clearing system can
parse)
DE 72 (Data Record)
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 (Data Record) contains
the first 1–200 positions of the rejected message. DE 72 may also contain additional
information, depending on the message reject reason.
This list is some examples of DE 72 contents in a Message Exception/1644:
• If the clearing system rejects a message because the combination of MTI and DE 24
(Function Code) is invalid, DE 72 is formatted as:
DE24\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:
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:
DXXX\contents\\PXXXX\contents\\PXXXX\contents\\.
• If the clearing system rejects a Financial Detail Addendum/1644, DE 72 is formatted as:
\USAGE=xx,IND REC NO=yyy, OCCUR=aaa^DExxx(or PDSxxxx)\contents\\.
Destination
Level of severity Condition Originator receives receives
Error Any File Reject/1644 message and, if Nothing
applicable, a Message Exception/1644.
If all detail messages in a logical file are
rejected, the clearing system returns
each detail message in a Message
Exception/ 1644 (Function Code 691)
message. In addition, it returns a File
Reject/1644 (Function Code 699)
message because 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 message contains the error codes that caused the file to be rejected, 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 are presented. Other identifying information related to the file is presented if the clearing
system can parse it.
This 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 codes, severity codes indicating fatal, and specific
data elements and PDSs and their related error codes, if applicable
PDS 0138 DE 71 (Message Number) of the message that caused the file to be
rejected (if the clearing system can parse)
PDS 0280 PDS 0105 (File ID) of the rejected file (from the File Header/1644, if
present and the clearing system can parse)
DE 72 (Data Record)
In a File Reject/1644 message, DE 72 always contains the first 1–200 positions of the rejected
file’s first message.
DE 72 may also contain additional information, depending on the file reject reason.
This list is some examples of DE 72 contents in a File Reject/1644 message:
• If the clearing system rejects a file because DE 71 in the File Header/1644 message contains
a value other than 00000001, DE 72 is formatted as:
DE71\contents of DE71\\1–200 positions of the rejected file’s first message.
• If the clearing system rejects a file because DE 71 (Message Number) in the header message
contains a value other than 00000001 and PDS 0026 (File Reversal Indicator) is present in
the File Header/1644, DE 72 is formatted as:
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 (File Message Counts) in the File
Trailer/1644 is not equal to the total number of messages in the logical file, DE 72 is
formatted as:
DE 72 (Data Record)..........................................................................................................................................383
DE 73 (Date, Action)..........................................................................................................................................384
DE 93 (Transaction Destination Institution ID Code).................................................................................. 385
DE 94 (Transaction Originator Institution ID Code).....................................................................................388
DE 95 (Card Issuer Reference Data)...............................................................................................................391
DE 100 (Receiving Institution ID Code).......................................................................................................... 392
DE 105 (Multi-Use Transaction Identification Data)................................................................................... 395
Subelement 001 (Transaction Link ID [TLID])......................................................................................... 396
DE 111 (Amount, Currency Conversion Assessment)..................................................................................397
DE 123 (Additional Data 3)..............................................................................................................................398
DE 124 (Additional Data 4)..............................................................................................................................401
DE 125 (Additional Data 5)..............................................................................................................................404
DE 127 (Network Data)....................................................................................................................................407
NOTE: All bit positions are interpreted from left to right within each bit map; for example, within the
Primary Bit Map the left-most bit is bit number 1 and the right-most 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) have no 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 data elements in the range DE 65–DE 128 are present in the 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.
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 (A–Z and a–z) and numeric characters
ans alphabetic (A–Z and a–z), numeric, and special characters (including
space)
b binary representation of data in eight-bit bytes
Notation Description
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)
Notation Description
-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.
• 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).
• 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. 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.
NOTE: The notation b-8 indicates a fixed-length binary field of eight characters (eight bytes, 64 bits).
Examples
DE 94 (Transaction Originator Institution ID Code): The ISO-defined maximum is 11 positions.
The IPM format allows customers to send 11 positions but edits and passes only 6 positions to
the receiver.
DE 63 (Transaction Life Cycle ID): 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
customer with lengths less than or equal to the maximum lengths currently supported. For
example, the clearing system provides a 6-position value in DE 94 and a 16-position value in DE
63.
Attributes
Usage
This table shows the usage of this data element (whether it is mandatory, conditional, optional,
system-provided, or not required) in applicable messages.
Usage
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 maps.
Values
This table shows the message types the clearing system currently supports.
MTI Description
1240 Presentment
1442 Chargeback
1644 Administrative
MTI Description
1740 Fee Collection
Attributes
This table shows the message attributes.
Attributes
Justification: N/A
Usage
This table shows the usage of this data element (whether it is mandatory, conditional, optional,
system-provided, or not required) in applicable messages.
Usage
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.
Attributes
Usage
Use of this data element is mandatory, conditional, optional, system provided, or not required in
applicable messages.
Usage
This data element always must 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 enables message originators to include only those data elements in a
message that are required for a specific function.
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.
Message requirements
Attributes
This table shows the data element attributes.
Attributes
Usage
Use of this data element is mandatory, conditional, optional, system provided, or not required in
applicable messages.
Usage
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 payment card or embossed on
a bankcard’s face.
This data element is required for payment card-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 customer 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 standards and policy publications.
DE 3 (Processing Code)
DE 3 (Processing Code) is a series of digits that describe the effect of a transaction on a
customer account and the type of accounts affected.
Attributes
Usage
Use of this data element is mandatory, conditional, optional, system provided, or not required in
applicable messages.
Usage
The Processing Code describes in First Presentment/1240 messages the cardholder transaction
type at the point of interaction. It also indicates whether DE 4 (Amount, Transaction) 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 message to properly identify the original cardholder transaction type and ensure proper
application of funds:
• Retrieval Request/1644
• Retrieval Request Acknowledgment/1644
• First Chargeback/1442
• Second Presentment/1240
• Arbitration Chargeback/1442
For all life cycle messages related to a First Presentment/1240 message, the DE 3 value must
remain the same.
The Processing Code is also used in Fee Collection messages to indicate funds movement
direction.
DE 3 subfields
DE 3 is comprised of three subfields.
This table describes the subfield formats for DE 3.
DE 3 subfields
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.
Value Description
00 Purchase (Goods and Services)
01 ATM Cash Withdrawal
09 Purchase (Goods and Services) with Cash Back (available only in
designated countries)
12 Cash Disbursement
17 Convenience Check (available only in Collection Only messages)
18 Unique Transaction (requires unique MCC)
19 Fee Collection (Credit to Transaction Originator)
Value Description
20 Credit (Purchase Return)
28 Payment Transaction
29 Fee Collection (Debit to Transaction Originator)
Value Description
30 Balance Inquiry11
Value Description
91 PIN Unblock3
92 PIN Change3
Transfer services
Value Description
50 Payment/Balance Transfer (Available Only in Collection Only
Messages)
Value Description
00 Purchase (Goods and Services)
01 ATM Cash Withdrawal
09 Purchase (Goods and Services) with Cash Back
12 Cash Disbursement
17 Convenience Check (available only in Collection Only messages)
18 Unique Transaction (requires unique MCC)
19 Fee Collection (Credit to Transaction Originator)
Value Description
20 Credit (Purchase Return)
28 Payment Transaction
29 Fee Collection (Debit to Transaction Originator)
Value Description
30 Balance Inquiry3
Value Description
91 PIN Unblock3
92 PIN Change3
Transfer services
Value Description
50 Payment/Balance Transfer (available only in Collection Only
messages)
Value Description
00 Purchase (Goods and Services)
01 ATM Cash Withdrawal
09 Purchase (Goods and Services) with Cash Back
12 Cash Disbursement
19 Fee Collection (Credit to Transaction Originator)
20 Credit (purchase return)
28 Payment Transaction
9 Fee Collection (Debit to Transaction Originator)
Value Description
01 ATM Cash Withdrawal
Value Description
12 Cash Disbursement
19 Fee Collection (Credit to Transaction Originator)
29 Fee Collection (Debit to Transaction Originator)
Value Description
00 Purchase
18 Unique Transaction (requires unique MCC)
20 Credit (Purchase Return)
28 Payment Transaction
Value Description
00 Default Account
10 Savings Account
20 Checking Account
30 Credit Account
39 Commercial Credit Account
60 Stored Value Account
Value Description
00 Default Account
10 Savings Account
20 Checking Account
30 Credit Card Account
39 Corporate Credit Account
Value Description
60 Stored Value Account
NOTE: The Mastercard Parameter Extract (MPE) retains only the masked values for the cardholder
from account type code.
DE 4 (Amount, Transaction)
DE 4 (Amount, Transaction) 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 acceptor that the acquirer supports,
exclusive of PDS 0146 (Amounts, Transaction Fee).
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
Usage
Use of this data element is mandatory, conditional, optional, system provided, or not required in
applicable messages.
Usage
12 For ATM First Chargeback/1442 messages involving non-European Primary Account Numbers (PANs) and destined
for the non-European, non-intracountry Mastercard Network identifier, the issuer must add interchange fees to the
chargeback amount before sending the message.
Values
In first chargebacks, second presentments, arbitration chargebacks, and fee collection (Retrieval
Fee Billing/Handling Fees) 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 transaction amount if submitted by a customer unless the transaction came
from the Single Message System. For fee collection messages, if the transaction is an
intracurrency settlement service transaction it must be submitted in the currency of the
intracurrency settlement agreement.
Chargebacks are restricted based on the MCC, the product code, and amount. Refer to the
Chargeback Guide, for more information.
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)
DE 5 (Amount, Reconciliation) is the DE 4 (Amount, Transaction) value converted to the
customer’s reconciliation payment or settlement currency.
This amount is exclusive of any fees that are provided in PDS 0146 (Amounts, Transaction Fee).
Attributes
Justification: Right
Usage
Use of this data element will be mandatory, conditional, optional, system provided, or not
required in applicable messages.
Usage
For ATM transactions submitted by the Mastercard Network, this element is mandatory.
For ATM transactions submitted by the acquirers, DE5 is mandatory when the ATM indicator is
1 or 4.
For all transactions, the clearing system always provides this element.
If a Currency Conversion Assessment (DE 111) was applied, DE 5 will contain this amount.
NOTE: These 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.
Values
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 reconciliation amount of
USD 212.50 is expressed as 000000021250.
Attributes
Usage
Use of this data element will be mandatory, conditional, optional, system provided, or not
required in applicable messages.
Usage
Values
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 cardholder billing amount
of USD 212.50 is expressed as 000000021250.
Attributes
Usage
Use of this data element will be mandatory, conditional, optional, system provided, or not
required in applicable messages.
Usage
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.
NOTE: This data element is simply a quotient of the two related amount data elements and may not
reflect the actual currency conversion rates or algorithms 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, DE 9 will contain a value of 61000000.
Attributes
Usage
Use of this data element will be mandatory, conditional, optional, system provided, or not
required in applicable messages.
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.
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, DE 10 will contain a value of 61000000.
Attributes
Usage
This table shows the usage of this data element (whether it is mandatory, conditional, optional,
system-provided, or not required) in applicable messages.
Usage
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.
DE 12 is required in the life cycle transactions if it was provided on the First Presentment. This is
critical if the transaction qualifies for Account Level Management/Spend Shortfall processing.
Please refer to the Account Level Management User Manual for details regarding which
transactions qualify for Account Level Management.
The date and time should always be retained and returned through all subsequent messages in
the life cycle.
Subfield 1 (Date)
DE 12 (Date and Time, Local Transaction), subfield 1 (Date) describes the date on which a
transaction takes place at the acceptor location.
Attributes
Requirements
• DE 12, subfield 1 must be present and contain a valid date in the format YYMMDD in all First
Presentment/1240 transactions. GCMS rejects the transaction if DE 12, subfield 1 is not
present.
• In First Presentment/1240 messages, DE 12 must contain a valid date to qualify for most
incentive interchange programs.
• The date cannot be greater than the file header date provided in subfield 2, File Reference
Date, of PDS 0105 (File ID), unless the transaction is Collection Only.
• If the transaction is a retrieval request and DE 12 is present, this subfield must contain a
valid date in the format YYMMDD.
• This table describes the rules for the date subfield based on the transaction type.
Subfield 2 (Time)
DE 12 (Date and Time, Local Transaction), subfield 2 (Time) describes the time at which a
transaction takes place at the acceptor location.
Attributes
Requirements
• This 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 value in the range 00–59.
• If the transaction time is unknown or unavailable, the time subfield should be populated with
zeros.
DE 14 (Date, Expiration)
DE 14 (Date, Expiration) specifies the year and month after which a card expires.
Attributes
This table shows the usage of this data element (whether it is mandatory, conditional, optional,
system-provided, or not required) in applicable messages.
Usage
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).
Attributes
Usage
Use of this data element will be mandatory, conditional, optional, system provided, or not
required in applicable messages.
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 occurred. Credit (Purchase
Return) messages should submit point-of-interaction (POI) data based on the refund
environment, not the environment of the original transaction.
If the acquirer fails to provide DE 22 (Point of Service Data Code) in the First Presentment of an
electronic commerce transaction, regardless of the IRD submitted, the transaction will be
rejected.
Requirements
This list describes the requirements for DE 22.
• DE 22 is required in First Presentment/1240, First Chargebacks/1442, Second
Presentments/1240, and Arbitration Chargebacks/1442 transactions.
If DE 22 is not present in the First Presentment/1240 message, GCMS rejects the
transaction.
• DE 22 data sent in the First and Arbitration Chargeback/1442 and Second Presentment/
1240 messages should be the same value as that which was sent in DE 22 in the First
Presentment/1240 message.
• DE 22 is required in Retrieval Request/1644 and Retrieval Request Acknowledgment/1644
messages whenever it was included in the associated First Presentment/1240. GCMS and
IPM Pre-edit and Utilities software currently have no edits to support this business
requirement.
• DE 22 is required when DE 55 is present. In this situation, DE 22, subfield 7 must contain
values F, M, R, S, or C.
• DE 22 is used in a clearing message to identify a message as a Clearing contactless magnetic
stripe transaction. For this transaction type, DE 22, subfield 1 contains values A or M, and
subfield 7 contains value A.
• DE 22 is used in a clearing message to identify a message as a Clearing contactless M/Chip
transaction. For this transaction type, DE 22, subfields 1 and 7 contain value M.
• For offline chip transactions when DE 38 (Approval Code) is not available, DE 22, subfield 7
must contain value F to identify the transaction as offline chip.
• DE 22, subfield 4 must contain value 2 or 4 when DE 22, subfield 7 contains value R.
• DE 22, subfield 5 must contain values 4 or 5 when DE 22, subfield 7 contains value S.
• Transactions identified as contactless PAN-mapped or Mastercard Digital Enablement
Service PAN-mapped, contactless transactions sent to the issuer, will have the value sent by
the acquirer (A or M) in DE 22, subfield 7, changed by Mastercard to value M.
• Transactions identified as contactless PAN-mapped or Mastercard Digital Enablement
Service PAN-mapped, contactless transactions sent to the acquirer, will have the DE 22,
subfield 7 value sent by the issuer (M) changed by Mastercard to the original value sent in by
the acquirer.
• Transactions identified as Mastercard Digital Enablement Service PAN-mapped Digital
Secure Remote Payment transactions sent to the issuer will have value R sent by the acquirer
in DE 22, subfield 7, changed by Mastercard to value O.
• Transactions identified as Mastercard Digital Enablement Service PAN-mapped Digital
Secure Remote Payment transactions sent to the acquirer will have value O sent by the
issuer and changed by Mastercard to the original value sent in by the acquirer.
NOTE: Refer to the Data Integrity Monitoring Program manual for specific edit information.
This table details the mapping between the authorization and clearing data elements.
Attributes
Values Description
0 Input capability unknown or unspecified.
1 No POS terminal used (for example, voice/ARU authorization or
other transactions that originated from a data server).
2 Terminal supports magnetic stripe input only.
4 Optical character reader (OCR) capability
5 Terminal supports EMV contact chip input only.
6 Terminal supports key entry input only.
Values Description
A Contactless Magnetic Stripe (Proximity Chip)
V Other capability
Attributes
Values Description
0 Terminal does not have PIN entry capability
1 Terminal has PIN entry capability
2 Electronic signature analysis capability
3 POS software-based PIN entry capability
Values Description
5 Terminal has PIN entry capability but PIN pad is not currently
operative
6 Other
9 Unknown; data unavailable
Attributes
Values Description
0 Terminal/operator does not have card capture capability
1 Terminal/operator has card capture capability
9 Unknown; data unavailable
Attributes
Values Description
0 No terminal used
Values Description
1 On acceptor premises; attended terminal
2 On acceptor premises; unattended terminal
3 Off acceptor premises; attended
4 Off acceptor premises; unattended
5 On cardholder premises; unattended
6 Off cardholder premises; unattended
7 Private use (Future use)
8 Additional Terminal Operating Environments
9 Unknown; data unavailable
Attributes
Values Description
0 Cardholder present
1 Cardholder not present (unspecified)
2 Cardholder not present (mail/facsimile transaction)
3 Cardholder not present (phone order or from automated response
unit [ARU])
4 Cardholder not present (standing order/recurring transactions)
5 Cardholder not present (electronic order [PC, Internet, mobile phone,
or PDA])
9 Unknown; data unavailable
Attributes
Values Description
0 Card not present*
1 Card present*
9 Unknown; data unavailable
*
Attributes
NOTE: Issuers are allowed to use values N, O, or V for Chargeback/1442 messages and Retrieval
Request/1644 messages if the First Presentment/1240 message contained values N, O, or V.
Values Description
0 PAN entry mode unknown
Values Description
1 PAN manual entry; no terminal used
2 PAN auto-entry via magnetic strip: track data is not required within
transaction
6 PAN manual entry using a terminal, or through voice transaction
after chip card read error or chip fallback transaction failure
7 Credential on File (effective June 12, 2018)
A PAN auto-entry via contactless magnetic stripe: track data provided
unaltered within transaction
B PAN auto-entry via magnetic stripe: track data provided unaltered
within transaction (magnetic stripe entry may also be chip fallback
transaction).
C PAN auto-entry via chip (online authorized transaction)
F PAN auto-entry via chip (offline chip-approved transaction)
M PAN auto-entry via contactless M/Chip
R PAN entry via electronic commerce containing Digital Secure Remote
Payment (DSRP) cryptogram within DE 55 (Integrated Circuit Card
[ICC])
S PAN entry via electronic commerce
T PAN auto-entry via server (issuer, acquirer, or third party vendor
system)
Attributes
Values Description
0 Not authenticated
1 PIN
Values Description
2 Electronic signature analysis
5 Manual signature verification
6 Other manual verification (such as a driver’s license number)
9 Unknown; data unavailable
S Other systematic verification
Attributes
Values Description
0 Not authenticated
1 ICC, Offline PIN
2 Card acceptance device (CAD)
3 Authorizing agent, Online PIN
4 Merchant/acceptor, signature
5 Other
9 Unknown; data unavailable
Application notes
For chip transactions, the Cardholder Verification Method (CVM) used for that transaction is
specified via the combination of values for DE 22, subfields 8 (Cardholder Authentication
Method) and 9 shown in this table.
Attributes
Values Description
0 Unknown; data unavailable
1 None
2 Write data to card at magnetic stripe level
3 Write data to card at ICC chip level
S Other
Attributes
Values Description
0 Unknown; data unavailable
1 None
2 Printing capability only
3 Display capability only
4 Printing and display capability
Attributes
Values Description
0 No PIN capture capability
1 Unknown; data unavailable
2 Reserved
3 Reserved
4 PIN capture capability 4 characters maximum
5 PIN capture capability 5 characters maximum
6 PIN capture capability 6 characters maximum
7 PIN capture capability 7 characters maximum
8 PIN capture capability 8 characters maximum
9 PIN capture capability 9 characters maximum
A PIN capture capability 10 characters maximum
B PIN capture capability 11 characters maximum
C PIN capture capability 12 characters maximum
Attributes
Usage
Use of this data element will be mandatory, conditional, optional, system provided, or not
required in applicable messages.
Usage
DE 23 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.
For chip transactions that include EMV-compliant ICC system-related data (DE 55), DE 23 must
be present and contain the Application PAN Sequence Number (tag 5F34) if provided by the IC
card to the terminal.
If the account range is registered for the Authentication Indicator Type 1 Service, then DE 23
must be present.
Values
If present, DE 23 contains the Card Sequence Number in the range 000–099, right-justified and
left-padded with zeros.
In the context of chip transactions, the Application PAN Sequence Number (EMV tag 5F34) is
defined as a one-byte numeric value. The acquirer software shall therefore convert this one-byte
numeric value to a three-byte value in DE 23, with leading zeros. For example, if the value of
5F34 is 2, the value of DE 23 will be 002.
Application notes
For Europe-acquired, Brazil-issued chip combination cards; acquirers in the Europe region may
optionally recognize the Brazil-issued chip combination card acceptance brand selection that is
determined by a unique PSN value in DE 23.
• 0x1 (Credit/Mastercard®), where x is the sequence number 0 to 9: the transaction is
processed a credit transaction.
• 0x2 (Debit/Mastercard®), where x is the sequence number 0 to 9: the transaction is
processed as a debit transaction.
• If neither 0x1 or 0x2 is present, the transaction is processed as a credit transaction.
DE 24 (Function Code)
DE 24 (Function Code) indicates the specific purpose for a message.
Attributes
Usage
Use of this data element will be mandatory, conditional, optional, system provided, or not
required in applicable messages.
Usage
DE 24 is mandatory in all Fee Collection/1740 clearing system messages. Together with the
MTI, the function code uniquely identifies all Fee Collection/1740 transaction functions the
clearing system performs.
Values
This table lists all Function Codes the clearing system supports. The associated MTIs are also
provided.
Values
Attributes
Usage
Use of this data element will be mandatory, conditional, optional, system provided, or not
required in applicable messages.
Usage
Values
These tables list Message Reason Codes the clearing system supports for Fee Collection/1740
messages. The associated MTIs and Function Codes are also provided to indicate the specific
circumstances in which each Message Reason Code is used.
Second Presentment (Full)/1240 (Function Code = 205) and Second Presentment (Partial)/1240
(Function Code = 282)
15 MEA countries participating in the Interregional Chip Liability Shift program include: Bahrain, Kuwait, Mauritius,
Morocco, Qatar, South Africa, Tunisia, United Arab Emirates
16 AP countries participating in interregional chip liability shift include: Hong Kong, Indonesia, Malaysia, New Zealand,
Philippines, Singapore, Taiwan, Thailand
First Chargeback (Full)/1442 (Function Code = 450) and First Chargeback (Partial)/1442 (Function
Code = 453)
Arbitration Chargeback (Full)/1442 (Function Code = 451) and Arbitration Chargeback (Partial)/1442
(Function Code = 454)
6343 Real-time
Substantiation Audit
Request
Reconciliation Messages: File Currency Summary/1644 (Function Code = 680), Financial Position
Detail/1644 (Function Code = 685), and Settlement Position Detail (Function Code = 688)
Fee Collection (Customer-generated)/1740 (Function Code = 700) and Fee Collection Return/1740
(Function Code = 780)
Fee Collection (Customer-generated)/1740 (Function Code = 700) and Fee Collection Resubmission/
1740 (Function Code = 781)
Difference in Yes
Negotiated
Interchange
(amounts/rates)
Fee Collection Return/1740 (Function Code = 780) and Fee Collection Arbitration Return/1740
(Function Code = 782)
7701 Mastercard
member
settlement of
fulfillment fees
processed by
MasterCom
DE 3, s1 = 19,
credit to sender
DE 3, s1 = 29, debit
to sender
DE 3, s1 = 29, debit
to sender
Fee Collection Funds Transfer/1740 (Function Code = 790) and Fee Collection Funds Backout/1740
(Function Code = 791)
Attributes
Usage
This table shows the usage of this data element (whether it is mandatory, conditional, optional,
system-provided, or not required) in applicable messages.
Usage
This data element contains a four-digit acceptor business code (MCC) that identifies the
acceptor’s primary business.
Acceptor business codes are required in Mastercard Financial transactions to qualify
transactions for specific interchange rates.
DE 26 is mandatory in Retrieval Request/1644 and Retrieval Request Acknowledgment/1644
messages.
If PDS 0358 (Reconciled, Business Activity), subfield 7 ( Acceptor Business Code [MCC] Override
Indicator) contains 0, DE 26 will also be present in the Financial Position Detail/1644 message,
to provide totals based on the value in DE 26.
The four-position valid Mastercard Acceptor Business Code (MCC) that most reasonably and
fairly represents the acceptor’s primary business, must be presented in DE 26. For example, if a
large Internet retailer sells an item on behalf of a toy store, DE 26 should contain the MCC
associated with the toy store. All acceptor business codes (MCCs) recognized by Mastercard are
published in the Quick Reference Booklet. For some transactions, Mastercard requires the use of
a specific MCC. For example, gambling transactions require the use of MCC 7995.
Values
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 Quick Reference Booklet, which is
periodically updated and made available to customer organizations.
Refer to Publications for additional information about Mastercard interchange programs and
their requirements, including valid DE 26 values for each interchange program, if applicable.
DE 30 (Amounts, Original)
DE 30 (Amounts, Original) contains the amount data element values from the First
Presentment/1240 or Fee Collection (Customer-generated)/1740 messages.
Attributes
Usage
Use of this data element will be mandatory, conditional, optional, system provided, or not
required in applicable messages.
Usage
Related PDSs
Whenever DE 30 is included in a message, PDS 0148 (Currency Exponents) and PDS 0149
(Currency Codes, Amounts, Original) must be included to identify the currency codes and
exponents of the original amount subfields.
DE 30 subfields
This data element consists of two subfields.
DE 30 Subfields
Attributes
Usage
Use of this data element will be mandatory, conditional, optional, system provided, or not
required in applicable messages.
Usage
This data element contains the acquirer reference data, which is mandatory in all First
Presentment/1240, Second Presentment/1240, First Chargeback/1442, and Arbitration
Chargeback/1442 messages. The acquirer reference data in a Second Presentment/1240
message must be the same as the acquirer reference data in the First Presentment/1240 and
Chargeback/1442 messages.
The issuer must return this data to the acquirer in subsequent related life cycle messages,
including Retrieval Request/1644, Retrieval Request Acknowledgment/1644, First Chargeback/
1442, Second Presentment/1240, and Arbitration Chargeback/1442 messages related to the
First Presentment/1240.
GCMS requires the six-digit acquiring BIN in DE 31, positions 2–7, for all applicable transactions.
If DE 31 is not provided in the Fee Collection/1740 message for the collection of handling fees,
the receiving customer has the right to return the message.
Values
DE 31 must be numeric.
DE 31 subfields
DE 31 consists of five subfields.
Attributes
Usage
Use of this data element will be mandatory, conditional, optional, system provided, or not
required in applicable messages.
Usage
For clearing system transactions, this data element may identify the financial institution that
owns the merchant agreement.
DE 32 supplements the acquiring customer ID (located in either DE 94 [Transaction Originator
Institution ID Code] or DE 93 [Transaction Destination Institution ID Code]) 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.
Additional information
Refer to Institution ID data elements and PDSs for more information about institution ID codes
and PDSs in clearing system messages.
Attributes
Usage
Use of this data element will be mandatory, conditional, optional, system provided, or not
required in applicable messages.
Usage
DE 33 contains the clearing system customer ID or Processor ID of the processing facility that
transmits a message.
Values
This data element must contain a valid customer ID or Processor ID number.
Additional information
Refer to Institution ID data elements and PDSs for more information about institution ID codes
and PDSs in clearing system messages.
Attributes
Usage
Use of this data element will be mandatory, conditional, optional, system provided, or not
required in applicable messages.
Usage
This data element is for the exclusive use of 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.
DE 37 should be supplied on European-acquired debit activity. The Single Message System uses
this field and some additional fields for matching the clearing message to information provided
in the authorization response message. An unsuccessful match may result in Mastercard
Network-generated chargebacks to the acquirer.
Values
If present, this element cannot contain all spaces or zeros.
DE 38 (Approval Code)
DE 38 (Approval Code) is a code the authorizing institution assigns indicating approval.
Attributes
Usage
Use of this data element will be mandatory, conditional, optional, system provided, or not
required in applicable messages.
Usage
This data element transmits a card issuer’s authorization code for approved transactions. The
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.
For each transaction authorized via the Mastercard Network (“online-authorized transactions”),
DE 38 of the First Presentment/1240 message must be populated with the same value
contained in DE 38 of the related Authorization Request Response/0110 message, or for
automated fuel dispenser (MCC 5542 and CAT level 2) transactions occurring in the U.S. or
Canada regions, the related Authorization Advice Response/0130 message.
This requirement does not apply to transactions where online authorization is not requested or
required, such as offline-authorized chip-read transactions, credit (purchase return)
transactions, and Collection Only transactions.
DE 38 must be present for all Mastercard Account Level Management transactions. DE 38
should be retained and returned through all subsequent messages in the lifecycle. Transactions
that qualify for Account Level Management processing (Enhanced Value, Product Graduation,
High Value, Small Business Spend Processing, Consumer Product Monitoring Service, or a
combination of Account Level Management Services) require this data element for correct
processing. Spend Shortfall clearing processing follows the same logic as Account Level
Management. For more information about Account Level Management services refer to the
GCMS Reference Manual.
Transactions for the accounts participating in the Co-Brand Proprietary Transaction
Management require this data element for correct processing.
DE 38 must be present for all Mastercard® MoneySend™ transactions where (a) PDS 0043
(Transaction Type Identifier) equals C07, C52, C53, C54, C55, C56, C57, C58, C59, or C65 and
(b) DE 3 (Processing Code), subfield 1 (Cardholder Transaction Type) equals 28 (Payment
Transaction).
Values
This data element must contain an issuer’s authorization response code formatted according to
Corporation operating rules.
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 (Point of Service Data Code) is present and DE 22, subfield
7 = F, indicating an offline chip transaction. (This does not apply to intracountry business service
arrangements.)
DE 38 is required for all U.S., Canada, Moldova, and Ukraine First Presentment/1240 messages
being submitted for incentive interchange. (This excludes transactions submitted for standard
IRD, credits, and reversals.)
If DE 38 is present in a First Presentment/1240 message, DE 38 should be provided on all
subsequent cycles (First Chargeback, Second Presentment, and so on).
For transactions authorized via the network, the sixth position of DE 38 could contain an
identifier indicating that the cardholder is a participant in Account Level Management, World
Elite Spend Shortfall, or World Mastercard Spend Shortfall. Please refer to the Account Level
Management Manual for more information.
DE 38, position 6 may contain any of the account category codes when the account range is
participating in an account level management service. This table describes the code values.
Value Description
B Enhanced Value
M Enhanced Value and Product Graduation Plus
B High Spend
S Premium High Spend
P Product Graduation Plus
E Consumer Product Monitoring Service: World Qualified
G Consumer Product Monitoring Service: Name for GCMS Product ID
MPE Qualified
J Consumer Product Monitoring Service: World Elite Qualified
Q Consumer Product Monitoring Service: Muse Mastercard Qualified
A Consumer Product Monitoring Service: Muse Mastercard Requalified
X Consumer Product Monitoring Service: World Elite Requalified
Y Affluent Shortfall World Mastercard and Product Graduation Plus
W Affluent Shortfall World Mastercard
W Affluent Shortfall World Elite Mastercard
Y Affluent Shortfall World Elite Mastercard and Product Graduation
Plus
C Small Business Spend Level 1
E Small Business Spend Level 2
G Small Business Spend Level 3
J Small Business Spend Level 4
Q Small Business Spend Level 5
H Small Business Spend Level 3 and Product Graduation Plus
K Small Business Spend Level 4 and Product Graduation Plus
D Small Business Spend Level 1 and Product Graduation Plus
F Small Business Spend Level 2 and Product Graduation Plus
R Small Business Spend Level 5 and Product Graduation Plus
S World High Value
Value Description
T World High Value and Product Graduation Plus
Z No Service: PAN not registered for ALM Activate Account Range
Value Description
W Spend Shortfall
Y Spend Shortfall and Product Graduation
DE 40 (Service Code)
DE 40 (Service Code) provides codes that increase flexibility in issuer-defined 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 an issuer-defined, 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.
The service code first-digit value of 2 or 6 can only be defined on chip cards:
• That comply with both Mastercard and Visa (EMV chip).
• In which the application on the magnetic stripe matches the application on the chip.
Attributes
Usage
Use of this data element will be mandatory, conditional, optional, system provided, or not
required in applicable messages.
Usage
Values
DE 40 is required to validate eligibility for some interchange programs. In such cases, acquirers
must populate DE 40 with the service code value available on the card. Refer to the Interchange
Manual for details.
Issuers may find more information about the physical and magnetic characteristics of chip cards
in International Organization for Standardization (ISO) 7813.
Attributes
Usage
Use of this data element will be mandatory, conditional, optional, system provided, or not
required in applicable messages.
Usage
Values
If present, DE 41 must be left-justified and cannot contain all low values, all high values, all
spaces, or all zeros.
Processing rules
The Acceptor Terminal ID must be present in all transactions.
Acceptor Terminal ID must uniquely identify each point-of-sale terminal and ATM terminal at
the acceptor location. For electronic commerce, phone/mail order, or other card-not-present
environments, the value must uniquely identify each payment gateway or other device used to
capture account data to effect a transaction at the acceptor location.
DE 42 (Acceptor ID)
This data element contains the identifier assigned by the acquirer to the acceptor and its
location, or to the payment facilitator.
Attributes
Subfields: None
Justification: Left
Usage
Use of this data element will be mandatory, conditional, optional, system provided, or not
required in applicable messages.
Usage
DE 42 is required for all First Presentment/1240 transactions and will be edited except for ATM
transactions.
DE 42 is required in First Chargeback/1442, Second Presentment/1240, and Arbitration
Chargeback/1442 transactions submitted for the following U.S.-to-U.S. interchange programs
when DE 26 is equal to 5542 (Automated Fuel Dispenser).
DE 42 is required for all Fee Collection (Other than Retrieval Fee Billing/handling Fees)/
1740-790 and 791 Funds Transfer messages generated by Mastercard on behalf of the
customer. This requirement does not apply to U.K. Domestic Maestro activity. Please refer to the
Interchange Manual for specific IRD details.
This table lists the IRD codes and descriptions.
IRD Description
02 World Merit 1
IRD Description
27 Petroleum CAT/AFD
45 World Petroleum Base
61 Petroleum Base
78/88/98 Merit 1
HB World High Value Merit
HX World High Value Petroleum Base
RP Enhanced Merit II
RW - Enhanced Petroleum Base
WB World Elite Merit I
WX World Elite Petroleum Base
Values
The acquirer assigns DE 42 values. The values assigned must be unique for each acceptor name/
location identified in DE 43 (Acceptor Name/Location) within the acquiring BIN ID. Mastercard
recommends that DE 42 values not be reassigned to a different Acceptor Name/Location until
the values have been inactive for a minimum of three years. This practice helps to avoid
ambiguity and erroneous tracking in fraud data analysis and reporting.
If present, DE 42 must be left-justified and cannot contain all low values, all high values, all
spaces, or all zeros.
Processing rules
The Acceptor ID must be present in all transactions and must uniquely identify each acceptor
and its location.
Payment facilitator-enabled transactions must uniquely identify the payment facilitator. The
Acceptor ID of the sponsored merchant must be provided in the sponsored merchant ID data
element.
Attributes
Usage
Use of this data element will be mandatory, conditional, optional, system provided, or not
required in applicable messages.
Usage
This data element provides the business name, street address, and other location information
about the acceptor.
For DE 43, Mastercard will support only the International Organization for Standardization
(ISO)/IEC 8859-1:1998 (Latin Alphabet No. 1) character set usage in all subfields. This
character set can be identified in several ways:
• In COBOL compiler options, the term would be Code Page 1140.
• In MVS Operating System information, the term CCSID 37 (EBCDIC Latin + 1, USA) is used.
• In ISO, it is identified as ISO8859-1.
All other standards must not be submitted in DE 43 but instead may be submitted in PDS 0171
(Alternate Acceptor Description Data) or PDS 0178 (Alternate Acceptor Description Data 2).
Attribute Value
Subfield ID n-2 01
Subfield Length n-2 22
Data Representation ans...22
Justification Left
Subfield requirements
This subfield is mandatory and must contain data in First Presentments/1240, Second
Presentments/1240, First Chargebacks/1442, and Arbitration Chargebacks/1442 messages. 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.
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.
The airline ticket number must not be provided in the Acceptor Name. For airline transactions
acquired outside the U.S. region, the abbreviated carrier name must be provided in positions 1–
9, followed by the ticket number in the Acceptor Name subfield, if the customer is provided with
the airline/railway ticket identifier.
Processing rules
The Acceptor Name must be present for all transactions and contain a valid merchant/ATM
owner/entity name that is most recognizable to the cardholder.
Unique identifiers, invoice numbers, or additional descriptors must be placed after the
merchant/ATM owner/entity name.
When a merchant is a part of a chain or franchise, the name most recognizable to the
cardholder must be provided at the beginning of the field, followed by a store number or other
unique identifier for each location. For a chain or franchise that has been issued a Mastercard
Assigned ID, all submitted transactions must contain the Mastercard Assigned ID data element.
For any MCC in the 3000-3350 range (Airlines), the Abbreviated Airline listed in Chapter 3 of
the Quick Reference Booklet must be provided in positions 1-9 of the field followed by the Airline
Ticket Number.
For any MCC in the 3351-3500 range (Automobile/Vehicle Rentals), the first nine characters of
the Description listed in Chapter 3 of the Quick Reference Booklet must be provided in positions
1-9 of the field and then followed by a unique identifier for each location.
For any MCC in the 3501-3999 range (Hotels and Motels), the first nine characters of the
Description listed in Chapter 3 of the Quick Reference Booklet must be provided in positions 1-9
of the field and then followed by a unique identifier for each location.
The (ISO)/IEC 8859-1:1998 (Latin Alphabet No. 1) character set must be used.
Program rules
Payment facilitator-enabled transactions: The sponsored merchant name must be provided. The
Payment Facilitator Name or abbreviated name must be provided, followed by an asterisk "*"
and the sponsored merchant name. All submitted transactions must contain the Payment
Facilitator ID submitted in the Payment Facilitator ID data element.
Staged digital wallet operator: The staged digital wallet operator name must be provided. If
issuer authorization for the transaction is occurring at the time of the consumer’s purchase of
products or services, then the staged digital wallet operator name must be provided, followed
by an asterisk “*” and the retailer name. If the retailer is identified with an MCC in the
3000-3999 range, then the appropriate industry MCC value, rather than individual retailer MCC,
if assigned, must be provided.
Mastercard® rePower™ transactions must have the value “MC repower” following the
merchant/ATM owner/entity name providing the service.
Payment Transactions must contain the name of the payment provider. Payee information must
be provided in the Additional Transaction Reference Data and MoneySend Receiver Data data
elements.
Country rules
Mexico-acquired transactions must contain only
• uppercase alpha characters (A-Z) (cannot contain accent characters)
• numeric characters (0–9)
• ampersand (&)
• asterisk (*) and,
• space (cannot be the first character or contain more than one space between words).
Attribute Value
Subfield ID: n-2 02
Subfield Length: n-2 48
Data Representation: ans...48
Justification Left
Subfield requirements
• For First Presentment/1240 messages, an acceptor address is mandatory for all non-ATM
transactions. Please refer to the appropriate regional Interchange Manual to determine the
IRDs which require the presence of this subfield.
• A valid acceptor street address is required for First Presentment/1240, Second
Presentment/1240, and First and Arbitration Chargeback/1442 transactions submitted for
the appropriate Canada region interchange rate programs. For more information, refer to
the Interchange Manual: Canada Region.
• For First Presentment/1240 messages, DE 43, subfield 2 must be present for Commercial
Card transactions in and between participating countries where value-added tax (VAT)
applies. The edit validates that DE 43, subfield 6 (Acceptor Country Code) and the country
code associated with the issuer account range in DE 2 (Primary Account Number) are on the
list of participating countries. Participating VAT countries will be announced via the
Operations Bulletin and identified via the VAT Indicator in Table IP0028T1 (Country Codes) of
the Mastercard Parameter Extract (MPE).
• If present, DE 43, subfield 2 must be left-justified and cannot contain all spaces, zeros, low
values, or high values.
• This subfield cannot contain backslashes other than at the end of the subfield.
• Whether populated or not, this subfield must end with a backslash (\) delimiter.
Values
Acceptor Street Address must contain all Address Line 1 and Address Line 2 information,
including
• the name of the street or throughfare
• the locality or community
• the building or house number; and
• any apartment, unit, suite, or floor number, if applicable.
This information must be populated and formatted as defined by country postal standards.
Processing rules
The Acceptor Street Address must be present for all transactions and contain a valid location
for the acceptor. The location of the acceptor will generally be the physical location where the
transaction occurred or business location for transactions that occur virtually.
If the information for Acceptor Street Address does not exist per country postal standards, then
the value of “Unavailable” must be provided.
Program rules
Payment facilitator-enabled transactions: The sponsored merchant street address must be
provided.
Attribute Value
Subfield ID: n-2 03
Subfield Length: n-2 13
Data Representation: ans…13
Justification Left
Subfield requirements
• The Acceptor City is mandatory on all transaction types except Payment Transactions and
ATM Transactions.
• This subfield must contain only the Acceptor City and must not contain other information
such as Acceptor Customer Service Phone Number, Acceptor URL Address, or other
descriptors.
• For First and Second Presentment/1240 and Chargeback/1442 messages, the Acceptor City
must be left justified and cannot contain all spaces or all zeros unless the transaction is an
ATM or Payment Transaction.
• This subfield cannot contain backslashes other than at the end of the subfield.
• Whether populated or not, this subfield must end with a backslash (\) delimiter. It cannot
contain all low values or all high values.
• This subfield must contain only the Acceptor City and must not contain other information
such as Acceptor Customer Service Phone Number, Acceptor URL Address, or other
descriptors.
Values
Acceptor City Name must contain the name of the city, town, or village as defined by country
postal standards.
For U.S. region transactions, Acceptor City Name must match the U.S. Postal Service list of
acceptable cities and spellings by postal code.
Processing rules
The Acceptor City Name must be present for all transactions and contain a valid location for the
acceptor. The location of the acceptor will generally be the physical location where the
transaction occurred or the business/operations location for transactions that occur virtually.
Program rules
Payment facilitator-enabled transactions: The sponsored merchant city name must be provided.
Attributes
Subfield rules
Subfield requirements
• For U.S. region acceptors, acquirers must provide a five-digit or nine-digit ZIP Code.
• This subfield must be present and must contain a postal code or all spaces. This subfield
cannot contain all low values or all high values.
Processing rules
The Acceptor Postal Code must be present for all transactions and contain a valid code for
countries that utilize postal codes. This information must be populated and formatted as
defined by country postal standards.
Program rules
Payment facilitator-enabled transactions: The sponsored merchant postal code must be
provided.
Attributes
Subfield requirements
• For Presentments/1240, Chargebacks/1442, Retrievals/1644, and Fee Collections/1740, if
DE 43, subfield 6 contains USA or CAN, subfield 5 must contain a valid country subdivision
code for the country identified.
• When submitted for a First Presentment/1240 transaction, subfield 5 cannot contain all low
values or high values.
• Mastercard will allow and populate DE 43, subfield 5 to contain text other than valid country
subdivision code (for example: “com”) when PDS 0158 (Business Activity), subfield 4
(Interchange Rate Designator) contains value EZ for a U.S. Intra-regional or Canada intra-
country Easy Savings transaction. Mastercard initiates these rebate transactions, which do
not impact acquiring transactions.
• The U.S. Postal Service has established three state codes that, when combined with a five-
digit ZIP Code from a specific range, will identify the Air/Army Post Office (APO) or Fleet
Post Office (FPO) of a U.S. military unit. The U.S. military state codes are available for use in
all authorization and clearing messages. The U.S. military state codes are listed in this table.
Values
Acceptor Country Subdivision Code must contain a valid code as defined in Chapter 2 of the
Quick Reference Booklet.
Processing rules
The Acceptor Country Subdivision Code must be present for all transactions when defined in
Chapter 2 of the Quick Reference Booklet.
Program rules
Payment facilitator-enabled transactions: The sponsored merchant country subdivision code
must be provided.
Attributes
Subfield requirements
• This subfield must contain a valid three-character ISO alphabetic country code in these
messages:
– First Presentment/1240
– First Chargebacks/1442 and Arbitration Chargebacks/1442
– Second Presentments/1240
– Retrieval Request/1644
– Retrieval Request Acknowledgment/1644
– Fee Collection (Retrieval Fee Billing)/1740
– Fee Collection (Handling Fees)/1740
– Fee Collection (Other than Retrieval Fee Billing/Handling Fees)/1740
Values
Acceptor Country Code must contain a valid three-character alphabetic code as defined in
Chapter 2 of the Quick Reference Booklet. When territories have a defined country code in the
Quick Reference Booklet, that country code must be used.
Processing rules
The Acceptor Country Code must be present for all transactions.
Program rules
Payment facilitator-enabled transactions: The sponsored merchant country code must be
provided.
DE 48 (Additional Data)
DE 48 (Additional Data) 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 unavailable.
Attributes
Usage
Use of this data element will be mandatory, conditional, optional, system provided, or not
required in applicable messages.
Usage
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), these data
elements are employed, in sequential order, to contain PDS data:
• DE 62 (Additional Data 2)
• DE 123 (Additional Data 3)
• DE 124 (Additional Data 4)
• DE 125 (Additional Data 5)
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, shown in this table.
Values
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.
Attributes
Usage
Use of this data element will be mandatory, conditional, optional, system provided, or not
required in applicable messages.
Usage
NOTE: For more information on currency conversion, refer to the GCMS Reference Manual.
Values
ISO standard numeric currency codes must be used.
This data element may contain the global base currency code in an acknowledgment 1644–680
or 1644–685 reconciliation message if the processed file contained only non-financial messages,
depending on customer-reconciliation category options.
Attributes
Usage
Use of this data element will be mandatory, conditional, optional, system provided, or not
required in applicable messages.
Usage
Values
ISO standard numeric currency codes must be used.
This data element may contain the global base currency code in an acknowledgment 1644–685
reconciliation message if the processed file contained only non-financial messages.
Attributes
Usage
Use of this data element will be mandatory, conditional, optional, system provided, or not
required in applicable messages.
Values
ISO standard numeric currency codes must be used.
DE 54 (Amounts, Additional)
DE 54 (Amounts, Additional) are additional amounts and related account data for which
specific data elements have not been defined.
Attributes
Usage
Use of this data element will be mandatory, conditional, optional, system provided, or not
required in applicable messages.
Usage
Transactions with surcharges (DE 54, subfield 2 = 42) are systemically permitted for all
processing codes in DE 3 (Processing Code). However, customers should refer to the Mastercard
Rules for standards pertaining to the areas in which they process.
DE 54 is required in Purchase with Cash Back transactions (Cardholder Transaction Type, DE 3,
subfield 1 = 09) to indicate the cash back amount of the transaction.
The following describes usage expectations for transactions containing one or more of the
following Amount Types: cash back amount, surcharge amount, or POI Amount.
• If DE 54 is present in a First Presentment/1240 message and indicates surcharging,
customers:
– Should not provide DE 54 in First Chargeback (Partial)/1442 or subsequent life cycle
messages;
– Should provide DE 54 in First Chargeback (Full)/1442 and subsequent life cycle messages;
– Must provide the total amount of the Brand-Level Surcharge or Product-Level Surcharge
amount in DE 54 in the First Chargeback/1442 message regardless of whether the
chargeback is for the partial or full amount of the transaction and subsequent life cycle
messages.
– The first DE 54 occurrence will represent either the cash back amount information (DE
54, subfield 2 = 40) or the surcharging information (DE 54, subfield 2 = 42).
– The second DE 54 occurrence will represent the original transaction amount and
transaction currency, including either cash back amount or the surcharge amount.
• If DE 54 is present in a First Presentment/1240 message and indicates that a POI currency
conversion service (also known as dynamic currency conversion [DCC]) was used by the
cardholder, then the updated amount and currency are located in DE 4 (Amount,
Transaction) and DE 49 (Currency Code, Transaction), respectively. DE 54 contains the
original transaction amount and currency information.
• DE 54 will occur multiple times if Purchase with Cash Back (DE 3, subfield 1 [Cardholder
Transaction Type] = 09) or surcharging occurs, and the POI currency conversion service (DCC)
updated DE 4 (Amount, Transaction) and DE 49 (Currency Code, Transaction).
• Occurrences are described as follows:
– The first DE 54 occurrence will represent either the cash back amount information (DE
54, subfield 2 = 40) or the surcharging information (DE 54, subfield 2 = 42).
– The second DE 54 occurrence will represent the original transaction amount and
transaction currency, including either cash back amount or the surcharge amount.
NOTE: For information about the Brand-Level Surcharge or Product-Level Surcharge, refer to
the Mastercard Rules manual, Chapter 10, “Asia/Pacific Region Rules,” Rule 5.11.2, “Charges to
Cardholders,”; Chapter 13, “Latin America and the Caribbean Region Rules,” Rule 5.11.2,
“Charges to Cardholders,”; and Chapter 15, “United States Region Rules,” Rule 5.11.2, “Charges
to Cardholders.”
– Each DE 54 occurrence within a transaction must have a unique DE 54, subfield 2
(Additional Amount, Amount Type) value.
– The sum of all DE 54, subfield 5 occurrences should be equal to or less than DE 4
(Amount, Transaction). Occurrences with Amount, Surcharge (DE 54, subfield 2 = 42) and
POI Amount (DE 54, subfield 2 = 58) are excluded from the sum.
In support of local government regulations, the Clearing system will determine whether
interchange should be applied to transactions containing a surcharge. Interchange may be
applied to surcharged transactions when:
• The combination of Card Program Identifier, Business Service Level and Business Service ID
permits interchange with surcharging OR
• The Acceptor Country Code (DE 43, subfield 6) and the issuing account range (derived from
PAN [DE 2]) country code are the same and the country permits interchange in combination
with surcharging.
NOTE: Although this edit will not produce an error, it will identify transactions qualifying for ATM
surcharging.
• DE 54, subfield 3 must contain the same currency as DE 49 (Currency Code, Transaction)
• DE 54, subfield 4 must be D (Debit)
• DE 54, subfield 5 must contain the cash back amount. This subfield may contain all zeros if
the issuer has declined the cash back portion of the transaction. This amount must be less
than the DE 4 (Amount, Transaction) amount.19
For First Presentment/1240 messages in which a surcharge is included:
• DE 54, subfield 2 must be 42 (Amount, Surcharge)
• DE 54, subfield 3 must contain the same currency as DE 49 (Currency Code, Transaction)
• DE 54, subfield 4 must be D (Debit).
• DE 54, subfield 5 must contain the surcharge amount.
• For processing codes 30, 91, or 92, this amount must be equal to the DE 4 (Amount,
Transaction) amount.
• For processing codes other than 30, 91 or 92, this amount must be less than the DE 4
(Amount, Transaction) amount.
For First Presentment/1240 messages when POI currency conversion (also known as dynamic
currency conversion [DCC]) is performed, DE 54 must be present and:
• DE 54, subfield 2 must be 58 (Amount, POI Amount)
• DE 54, subfield 3 must contain the pre-conversion currency of the purchase or withdrawal,
which must be a different currency from DE 49 (Currency Code, Transaction).
DE 54 subfields
DE 54 may contain one to 12 occurrences of additional amounts.
Each additional amount consists of five subfields as defined in this table. Each field requires 20
positions; the length of this data element must be a multiple of 20, with a maximum length of
240 positions.
DE 54 subfields
19 For intracountry India activity, the cash back amount can be equal to the DE 4 (Amount, Transaction) amount.
Value Description
10 Healthcare Eligibility Amount
11 Prescription Eligibility Amount
12 Vision Rx Eligibility Amount
17 Prepaid Online Bill Pay Fee Amount
40 Amount, Cash Back
42 Amount, Surcharge
44 Amount Gratuity
58 Amount, POI Amount
must be D. For all other amount types, the sign is from the issuer’s perspective on the First
Presentment/1240 message and will not change in subsequent life cycle or reversal messages.
Attributes
Usage
Use of this data element will be mandatory, conditional, optional, system provided, or not
required in applicable messages.
Usage
DE 55 must be provided for all chip transactions except for refund transactions.
If present, DE 55 cannot contain all spaces, all zeros, all low values, or all high values.
If present and maximum length (255), DE 55 must be left justified and zero (low value hex 00)
filled.
If DE 55 is present and is greater than 255 characters in length, then the Clearing Platform will
reject the transaction with a format error:
• DE 39 (Response Code) value of 30 (Format Error)
• DE 44 (Additional Response Data) includes DE 55 as a data element with a format error.
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 components in a “tag-length-data” format, similar to
the presentation of PDSs in DE 48 (Additional Data). This table shows the layout.
DE 55 layout
Components 1–3 must be repeated as needed until all chip subelements are presented. The
length of the tag component is either 1 or 2, depending on the definition of the tag in EMV chip.
The length of the data length component is always one in DE 55.
Each Total
Tag Componen Componen Subelemen
Subelement Description Value20 Format t t Length21 t Length22
Application Cryptogram 9F26 b8 tag 2 11
(AC)
length 1
data 8
Cryptogram Information 9F27 b1 tag 2 4
Data
length 1
data 1
Issuer Application Data 9F10 b1..32, VAR tag 2 4–35
(IAD) (Must be provided
by the acquirer if the
corresponding data
object is provided by the
ICC to the terminal)
length 1
data 1–32
Cardholder Verification 9F34 b3 tag 2 6
Method (CVM) Results
length 1
data 3
Terminal Capabilities 9F33 b3 tag 2 6
length 1
data 3
Unpredictable Number 9F37 b4 tag 2 7
length 1
20 The hexadecimal representation is given here. Every two positions of hexadecimal data is one byte of binary data.
21 Lengths are in binary format.
22 “Total Subelement Length” is the sum of that subelement’s tag, length, and data components.
Each Total
Tag Componen Componen Subelemen
Subelement Description Value20 Format t t Length21 t Length22
data 4
Application Transaction 9F36 b2 tag 2 5
Counter
length 1
data 2
Terminal Verification 95 b5 tag 1 7
Result
length 1
data 5
Transaction Date 9A b3 (n6) tag 1 5
length 1
data 3
Transaction Type 9C b1 (n2) tag 1 3
length 1
data 1
Amount Authorized 9F02 b6 (n12) tag 2 9
(numeric)
length 1
data 6
Transaction Currency 5F2A b2 (n3) tag 2 5
Code
length 1
data 2
Application Interchange 82 b2 tag 1 4
Profile
length 1
data 2
Terminal Country Code 9F1A b2 (n3) tag 2 5
length 1
20 The hexadecimal representation is given here. Every two positions of hexadecimal data is one byte of binary data.
21 Lengths are in binary format.
22 “Total Subelement Length” is the sum of that subelement’s tag, length, and data components.
Each Total
Tag Componen Componen Subelemen
Subelement Description Value20 Format t t Length21 t Length22
data 2
Dedicated File Name 84 b5...16 tag 1
length 1
data 5–16
Amount, Other 9F03 b6 (n12) tag 2 9
(numeric)
length 1
data 6
When cash back is not
allowed by product rules,
9F03 can only either be
absent or present with a
zero value. If cash back is
allowed by product rules,
• If there is a cash back
amount, 9F03 carries
the cashback
amount, and this
data element is
mandatory.
• If there is no cash
back amount, the
value of 9F03 will be
zero, in which case
9F03 can either be
absent or present
with a zero value.
Optional subelements
Customers may send the optional subelements listed in this table.
20 The hexadecimal representation is given here. Every two positions of hexadecimal data is one byte of binary data.
21 Lengths are in binary format.
22 “Total Subelement Length” is the sum of that subelement’s tag, length, and data components.
Optional subelements
Each Total
Tag Componen Componen Subelemen
Subelement Description Value23 Format t t Length24 t Length25
Terminal Type 9F35 b1 (n2) tag 2 4
length 1
data 1
Interface Device Serial 9F1E b8 (an 8) tag 2 11
Number
length 1
data 8
Transaction Category 9F53 b1 (an 1) tag 2 4
Code
length 1
data 1
Terminal Application 9F09 b2 tag 2 5
version Number
length 1
data 2
Transaction Sequence 9F41 b2 (n..8) tag 2 5–7
Counter
length 1
data 2–4
Authenticated 9F60 b tag 2 4-130
Application Data
length 1
data var-127
Kernel Identifier- 96 b tag 1 10
Terminal
length 1
23 The hexadecimal representation is given here. Every two positions of hexadecimal data is one byte of binary data.
24 Lengths are in binary format.
25 “Total Subelement Length” is the sum of that subelement’s tag, length, and data components.
Each Total
Tag Componen Componen Subelemen
Subelement Description Value23 Format t t Length24 t Length25
data 8
This subelement may be present in the clearing message if it was present in the Authorization
Request Response/0110 message.
Each Total
Component Subelement
Subelement description Tag Value Format Component Length Length
Issuer Authentication Data 91 b8..16 tag 1 10–18
(Provides data to be
transmitted to the card for
issuer authentication)
length 1
data 8–16
DE 62 (Additional Data 2)
DE 62 (Additional Data 2) 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 unavailable.
Attributes
23 The hexadecimal representation is given here. Every two positions of hexadecimal data is one byte of binary data.
24 Lengths are in binary format.
25 “Total Subelement Length” is the sum of that subelement’s tag, length, and data components.
Usage
Use of this data element will be mandatory, conditional, optional, system provided, or not
required in applicable messages.
Usage
This data element is a carrier data field for PDSs that supplement the ISO 8583–1993
specification.
Encoding of PDSs is always initiated in DE 48 (Additional Data). If the resulting data length
required to contain all PDSs exceeds the maximum length of DE 48 (999 positions), these ISO
data elements are employed, in sequential order, to contain the remaining PDS data:
• DE 62
• Additional Data 3 (DE 123)
• Additional Data 4 (DE 124), and
• Additional Data 5 (DE 125).
DE 62, DE 123, DE 124, or DE 125 each may contain a maximum of 999 positions 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, and then DE 123, DE 124, and finally DE 125, as needed.
Customers 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-
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, shown in this table.
Values
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 62 to exceed 999 positions.
Attributes
Usage
This table shows the usage of this data element (whether it is mandatory, conditional, optional,
system-provided, or not required) in applicable messages.
Usage
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 consists of two subfields:
• Life Cycle Support Indicator
• Trace ID
DE 63 must be present in the First Presentment/1240 message for all transactions authorized
via the Mastercard Network (“online-authorized transactions”). This requirement does not apply
to transactions where online authorization is not requested or required, such as offline-
authorized chip-read transactions, credit (purchase return) transactions, and Collection Only
transactions.
Life cycle messages such as Authorization Request/0100, First Presentment/1240, Retrieval
Request/1644, Retrieval Request Acknowledgment/1644, First Chargeback/1442, Second
Presentment/1240, and Arbitration Chargeback/1442 messages are linked with this data
element.
DE 63 should always be retained and returned throughout all subsequent messages in the life
cycle.
DE 63 is required for European acquired activity destined for processing through the network
unless DE 22 (Point of Service Data Code), subfield 7 (Card Data: Input Mode) = F (Offline
Chip). This activity can be identified via one of the these situations:
• First presentment interregional ATM transactions
• First presentment PIN-based Maestro or Cirrus manual cash disbursement transactions
• First presentment interregional Maestro retail transactions
• First presentment European intraregional ATM or retail Enhanced Gateway transactions
Credit (Purchase Return) transactions are exempt from this requirement.
NOTE: Enhanced Gateway transactions are defined as those from a Europe region acquirer for which
the ATM Indicator is equal to 5 and for which the ATM Indicator of the issuer is equal to 4.
Alternate Automated Fuel Dispenser Clearing Processing: Mastercard recommends that the
Trace ID (DE 15 [Settlement Date] and DE 63 [Network Data]) of the Automated Fuel
Dispenser (AFD) completion advice response be used within the clearing presentment. The Trace
ID of the original preauthorization may be used for clearing presentment if that same Trace ID is
included in the AFD completion advice message within DE 48, subelement 63 (Additional Data,
Trace ID).
Values
If present, DE 63 cannot contain all low values or all high values.
DE 63 subfields
DE 63 includes two subfields.
DE 63 subfields
Value Description
space Trace ID assigned to Authorization message.
This requirement does not apply to transactions where online authorization is not requested or
required, such as offline-authorized chip-read transactions, credit (purchase return)
transactions, and Collection Only transactions.
For each Authorization Request Response/0110 message transmitted via the network (“online-
authorized transactions”), subfield 2 of the First Presentment/1240 message must be
populated with the values contained in DE 15, DE 63 subfield 1, and DE 63 subfield 2. For
automated fuel dispenser (MCC 5542) transactions where an Authorization Request/0100
message is followed by an Authorization Advice/0120 message containing the final transaction
amount, these values should come from the same fields of the related Authorization Advice
Response/0130 message.
Subfield 2 is required if the associated First Presentment/1240 is submitted for any U.S. region
consumer or corporate credit or consumer debit incentive interchange rate programs, unless the
transaction is a credit, ATM cash disbursement, manual cash disbursement, reversal, Collection
Only, or bilaterally settled transaction.
Mastercard recommends that the Trace ID (DE 15 [Date, Settlement] and DE 63 [Network
Data]) of the completion advice response be used within the clearing presentment. (Refer to the
Alternate AFD Clearing Processing in the following section.)
The Trace ID of the original pre-authorization may be used for Clearing presentment if that
same Trace ID is included in the Automated Fuel Dispenser (AFD) completion advice message
within CIS DE 48 (Additional Data, Private Use), subelement 63 (Trace ID).
GCMS requires the presence of DE 63 for all U.S. acquired transactions submitted for incentive
interchange programs. For transactions containing 14-digit Enabled International Cards
beginning with the digits 36, U.S. acquirers should populate Trace ID (DE 63, subfield 2) with the
correct Network Reference Number and Network Date.
GCMS requires the presence of DE 63 for all Canada acquired transactions submitted for
incentive interchange programs.
When Trace ID (DE 63) is present, edits will be applied against the network Reference Number
(DE 63, subfield 2) to confirm the format of the information.
The edit checks are:
• Position 1–3: Must contain a valid Mastercard product code
• Position 4–9: Must contain six alphanumeric characters, no embedded spaces, low values, or
high values.
This table represents mapping of values from DE 63 in the Authorization CIS message to the
Clearing IPM message.
DE 71 (Message Number)
The transaction originator assigns the DE 71 (Message Number) to data messages in a file.
DE 71 monitors the integrity and continuity of the files being exchanged.
Attributes
Usage
Use of this data element will be mandatory, conditional, optional, system provided, or not
required in applicable messages.
Usage
This data element provides the recipient of a file with a readily available means to verify that 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) contains message text data, file update data, or other information as
specified in individual IPM messages.
Attributes
Usage
Use of this data element will be mandatory, conditional, optional, system provided, or not
required in applicable messages.
Usage
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/
1240, 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 Chargeback Guide for specific DE 72 requirements based on the value in
DE 25 (Message Reason Code). 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 Chargeback Guide,
the receiving customer 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 message reason code as specified in the GCMS Reference Manual, the receiving
customer 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) specifies a future action date or a specific date such as a transaction date.
Attributes
Usage
Use of this data element will be mandatory, conditional, optional, system provided, or not
required in applicable messages.
Usage
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 DE 25 (Message Reason Code). The clearing system does not edit to
require DE 73. However, if it is not provided for a given Message Reason Code as specified in the
GCMS Reference Manual, the receiving customer 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.
Attributes
Usage
Use of this data element will be mandatory, conditional, optional, system provided, or not
required in applicable messages.
Usage
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 in all Fee Collection (Other) and Fee Collection (Handling Fees)
transactions.
If the clearing system does not receive this data element from a customer in an originating
message, it may perform automated routing services (based on other data elements such as DE
2 (Primary Account Number [PAN]) 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 customer ID.
For lifecycle transactions initiated by issuers, DE 93 may contain the ICA number as provided in
DE 94 (Transaction Originator Institution ID Code) from the First Presentment/1240 message.
If the ICA number present in DE 93 represents a Single Message System acquirer, the ICA
number may not be present in the IPM MPE data as supplied by Mastercard. If the DE 93 value
is provided, Mastercard recommends that it be the ICA number related to the bank
identification number (BIN) in DE 31 (Acquirer Reference Data), subfield 2 (Acquirer’s BIN must
contain the six-digit acquirer’s BIN).
Additional information
Refer to Institution ID data elements and PDSs for more information about institution ID codes
and PDSs in clearing system messages.
Attributes
Usage
Use of this data element will be mandatory, conditional, optional, system provided, or not
required in applicable messages.
Usage
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 that 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 customer 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 customer ID cannot be designated as
an issuer-only customer ID.
In First Chargeback/1442 and Arbitration Chargeback/1442 messages, the customer ID cannot
be designated as an acquirer-only customer ID.
Values
When present in a message, this data element must contain a valid customer ID. The customer
ID must either be equal to the customer processor ID in subfield 3 of PDS 0105 File ID in the File
Header/1644-697 message or be processed by that customer/processor ID.
For collection only activity, DE 94 must be compatible with the Acquirer Reference ID in DE 31
(Acquirer Reference Data), subfield 2 (Acquirer’s BIN).
For outbound files to customers, DE 94 may contain an ICA number associated with a Single
Message System customer. In such cases, the ICA number may not be included in the IPM MPE
data provided by Mastercard and is intended for informational purposes.
Application notes
For bridged transactions, issuers will now receive the ICA number that identifies the transaction
originator institution having financial responsibility for the transaction in DE 94 of the First and
Second Presentment/1240 messages, instead of a Mastercard-assigned internal ICA.
NOTE: Transactions that have passed between platforms (Single Message System to Dual Message
System, Dual Message System to Single Message System) are referred to as bridged transactions.
Additional information
Refer to Institution ID data elements and PDSs for more information about institution ID codes
in clearing system messages.
Attributes
Usage
Use of this data element will be mandatory, conditional, optional, system provided, or not
required in applicable messages.
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, Retrieval Request Acknowledgment/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, Retrieval Request Acknowledgment/1644, 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 within BIN. It is used to track the chargeback throughout its life cycle.
If present, DE 95 must be numeric.
Attributes
Usage
Use of this data element will be mandatory, conditional, optional, system provided, or not
required in applicable messages.
Usage
DE 100 contains the customer ID or Processor ID of the physically connected processing facility
that receives a message.
Values
This data element must contain a valid customer ID or Processor ID number.
Additional information
Refer to Institution ID data elements and PDSs for more information regarding the use of
institution ID codes and PDSs in clearing system messages.
Attributes
Attribute Description
Data representation ans…999, LLLVAR
Length field 3 positions, value = 001-999
Data field Variable length, 1-999 positions
Subelements 1, see "Values"
Justification N/A
Usage
Following is the usage of DE 105 (whether it is mandatory, conditional, optional, system
provided, or not required) in applicable messages.
Values
Data in DE 105 consists of a series of repeatable components in a tag-length-data format,
similar to the presentation of the subelements in DE 55 (Integrated Circuit Card [ICC] System-
Related Data).
Components 1-3 may be repeated, as needed, until all subelements are presented.
The subelement sequence does not have to be in the order of the ID value. For example,
subelement 001 does not have to precede all the other subelements. If a new subelement 017 is
defined in the future, it could be presented before subelement 001. Systems must be prepared
to read and parse the contents of DE 105 to determine which tags (subelements) are present
and which are necessary for their own internal processing.
Attributes
Attribute Description
Subelement ID 001
Subelement length 3
Data representation ans-22
Data field N/A
Subfields N/A
Justification N/A
Usage
Whether the data element is mandatory, conditional, optional, system-provided, or not required
is noted for each applicable message.
Attributes
ISO defines DE 111 as a variable-length field. Therefore, the DE 111 data is preceded by a
three-position length field. In the IPM format, customers still must precede the DE 111 data
with a three-position length field. This length field always will contain the value 012, and the
data that follows always must be exactly 12 positions long.
Usage
Use of this data element will be mandatory, conditional, optional, system provided, or not
required in applicable messages.
Usage
This data element contains the calculated Currency Conversion Assessment adjustment
amount. The clearing system provides DE 111 when the transaction qualifies for a Currency
Conversion Assessment conversion adjustment.
Values
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 cardholder billing amount
of USD 212.50 is expressed as 000000021250.
Attributes
Usage
Use of this data element will be mandatory, conditional, optional, system provided, or not
required in applicable messages.
Usage
This data element is a “carrier” data field for PDSs that supplement the ISO 8583–1993
specification.
Encoding of PDSs is always initiated in DE 48 (Additional Data). If the resulting data length
required to contain all PDSs exceeds the maximum length of DE 48 (999 positions), these ISO
data elements are employed, in sequential order, to contain the remaining PDS data:
• DE 62 (Additional Data 2)
• DE 123 (Additional Data 3)
• DE 124 (Additional Data 4)
• DE 125 (Additional Data 5)
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 a significant amount of PDS data is in a message, DE 48 should contain as many complete
PDSs as will fit into 999 bytes. Then DE 62 should contain as many complete PDSs (tag+length
+data) as will fit into 999 bytes. The remaining complete PDSs must be presented in DE 123,
DE 124, and DE 125, as needed.
Customers 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
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, shown in this table.
Values
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 123 to exceed 999 positions.
Refer to the beginning of Chapter 8 of this manual for additional information about PDS
definitions and an example.
Attributes
Usage
Use of this data element will be mandatory, conditional, optional, system provided, or not
required in applicable messages.
Usage
This data element is a “carrier” data field for PDSs that supplement the ISO 8583–1993
specification.
Encoding of PDSs is always initiated in DE 48 (Additional Data). 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 2)
• DE 123 (Additional Data 3)
• DE 124 (Additional Data 4)
• DE 125 (Additional Data 5)
DE 62, DE 123, DE 124, and DE 125 may contain a maximum of 999 positions, each, of encoded
PDS information.
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 a significant amount of PDS data is in a message, DE 48 should contain as many complete
PDSs as will fit into 999 bytes. Then DE 62 should contain as many complete PDSs (tag+length
+data) as will fit into 999 bytes. The remaining complete PDSs must be presented in DE 123,
DE 124, and DE 125, as needed.
Customers 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
When present, this data element contains one or more PDSs in PDS-encoded format.
PDSs are formatted using a “tag-length-data” encoding procedure, shown in this table.
Values
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 124 to exceed 999 positions.
Refer to the beginning of Chapter 8 for additional information about PDS definitions and an
example.
Attributes
Usage
Use of this data element will be mandatory, conditional, optional, system provided, or not
required in applicable messages.
Usage
This data element is a “carrier” data field for PDSs that supplement the ISO 8583–1993
specification.
Encoding of PDSs is always initiated in DE 48 (Additional Data). If the resulting data length
required to contain all PDSs exceeds the maximum length of DE 48 (999 positions), these ISO
data elements are employed, in sequential order, to contain the remaining PDS data:
• DE 62 (Additional Data 2)
• DE 123 (Additional Data 3)
• DE 124 (Additional Data 4)
• DE 125 (Additional Data 5)
DE 62, DE 123, DE 124, and DE 125 may contain a maximum of 999 positions, each, of encoded
PDS information.
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 a significant amount of PDS data is 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.
Customers 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
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, shown in this table.
Values
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 125 to exceed 999 positions.
Refer to the beginning of Chapter 8 in this manual for additional information about PDS
definitions and an example.
Attributes
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.
PDS 0222 (Mexico Domestic Dispute Resolution Documentation Image-Related Data).................... 690
PDS 0222 subfields...................................................................................................................................... 691
PDS 0225 (Syntax Return, Original Message Reason Code)......................................................................693
PDS 0228 (Retrieval Document Code)...........................................................................................................694
PDS 0230 (Fulfillment Document Code)....................................................................................................... 696
PDS 0235 (Mastercard Assigned Incentive Identifier).................................................................................697
PDS 0241 (MasterCom Control Number)..................................................................................................... 697
PDS 0243 (MasterCom Retrieval Response Data)...................................................................................... 699
Subfield 1 (MasterCom Issuer Retrieval Request Date)........................................................................ 700
Subfield 2 (MasterCom Acquirer Retrieval Response Code)................................................................. 700
Subfield 3 (MasterCom Acquirer Retrieval Response Sent Date)........................................................701
Subfield 4 (MasterCom Issuer Response Code)...................................................................................... 701
Subfield 5 (MasterCom Issuer Response Date).......................................................................................702
Subfield 6 (MasterCom Issuer Reject Reasons).......................................................................................703
Subfield 7 (MasterCom Image Review Decision).................................................................................... 703
Subfield 8 (MasterCom Image Review Date).......................................................................................... 704
PDS 0244 (MasterCom Chargeback Support Documentation Dates)....................................................704
PDS 0244 subfields...................................................................................................................................... 706
PDS 0245 (MasterCom Arbitration Chargeback Sender Processing Date)............................................ 706
PDS 0246 (MasterCom Sender Memo)......................................................................................................... 707
PDS 0247 (MasterCom Receiver Memo)....................................................................................................... 708
PDS 0248 (MasterCom Image Review Memo)............................................................................................. 709
PDS 0249 (MasterCom Record ID).................................................................................................................710
PDS 0250 (MasterCom Endpoints)................................................................................................................ 711
PDS 0250 subfields...................................................................................................................................... 712
PDS 0251 (MasterCom Fulfillment Document Code).................................................................................713
PDS 0252 (MasterCom Image Metadata)....................................................................................................714
PDS 0252 subfields...................................................................................................................................... 715
PDS 0253 (MasterCom System Enhanced Data)........................................................................................716
PDS 0254 (MasterCom Member Enhanced Data)...................................................................................... 716
PDS 0255 (MasterCom Message Type)......................................................................................................... 717
PDS 0260 (Edit Exclusion Indicator)............................................................................................................... 718
PDS 0260 subfields...................................................................................................................................... 720
PDS 0261 (Risk Management Approval Code)............................................................................................. 722
PDS 0262 (Documentation Indicator)............................................................................................................723
PDS 0264 (Original Retrieval Reason for Request)......................................................................................725
PDS 0265 (Initial Presentment/Fee Collection Data).................................................................................726
PDS 0265 subfields...................................................................................................................................... 727
PDS 0266 (First Chargeback/Fee Collection Return Data)....................................................................... 728
NOTE: PDSs cannot be duplicated within an IPM message. The clearing system rejects any message
containing duplicate occurrences of a PDS tag field.
This diagram illustrates the PDS encoding scheme in an ISO standard data element.
Figure 7: PDS encoding scheme
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 (A–Z and a–z) and numeric characters
Notation Description
ans alphabetic (A–Z and a–z), numeric, and special characters (including space)
b binary representation of data in eight-bit bytes
Notation Description
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)
Notation Description
-digits Fixed length in number of positions
Example: “n-3” indicates a three-position numeric PDS.
Example: “an-10” indicates a 10-position alphanumeric PDS.
LLLVAR Present with a variable-length data element attribute, indicates that the data
element contains two fields:
“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–
992.
“VAR” is the variable-length data field.
Example: “an..500; LLLVAR” indicates a variable-length alphanumeric data element
having a length of 1–500 positions.
NOTE: The notation“b-8” indicates a fixed-length binary field of eight characters (eight bytes, 64 bits).
NOTE: Customers can send clearing files with PDSs in any sequence. In all clearing files that customers
receive, the clearing system formats the PDS data in ascending sequence by PDS tag number.
For example, assume a customer wants to present the PDS data in this table.
DE 48 example
“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 PDSs 1000–1099 in a single IPM message cannot exceed 992
bytes.
PDS listing
This table is a listing of PDSs 0001–1099 in numerical order.
PDS Listing
Attributes
Subfields: 2 subfields
Justification: N/A
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
The clearing system provides PDS 0001 to the issuer whenever it performs the mapping service.
This service maps a virtual card number or token to a real card number or a real card number to
a virtual card number or token. PDS 0001 is provided to the acquirer only when a PAN Mapping
Service has been performed.
Attribute Value
Subfield ID: n-2 01
Subfield Length: n-2 02
Data Representation: ans-2
Justification: Left
Values Description
C Space Subfield 2 contains the Mastercard Digital Enablement Service secure element
device token used at the point of sale. The account range is owned by an issuer.
Mapping was based on the authorization log.
CC Subfield 2 contains the Mastercard Digital Enablement Service secure element
device token used at the point of sale. The account range is owned by an issuer.
Mapping was based on a source other than the authorization log.
H space Subfield 2 contains the Mastercard Digital Enablement Service Cloud-Based
Payments device token used at the point of sale. The account range is owned by an
issuer. Mapping was based on the authorization log.
HC Subfield 2 contains the Mastercard Digital Enablement Service Cloud-Based
Payments device token used at the point of sale. The account range is owned by an
issuer. Mapping was based on a source other than the authorization log.
O Space Subfield 2 contains the Mastercard Digital Enablement Service Card on File token
submitted by the acquirer. The account range is owned by Mastercard. Mapping
was based on the authorization log.
OC Subfield 2 contains the Mastercard Digital Enablement Service Card on File token
submitted by the acquirer. The account range is owned by Mastercard. Mapping
was based on a source other than the authorization log.
Values Description
TC Subfield 2 contains a primary account number. Mapping was based on a source
other than the authorization logs.
1 Subfield 2 contains a contactless account number owned by an issuer, and the
issuer is actively participating in the PayPass® Mapping Service. Every transaction
containing this account range is to be mapped. Mapping was based on the
authorization logs.
1C Subfield 2 contains a contactless account number owned by an issuer, and the
issuer is actively participating in the PayPass® Mapping Service. Every transaction
containing this account range is to be mapped. Mapping was based on a source
other than the authorization logs.
2 Subfield 2 contains a contactless account number owned by an issuer, and the
issuer is actively participating in the PayPass® Mapping Service. Not all
transactions in this issuer account range are mapped, because the issuer is phasing
in the PayPass® Mapping Service. Mapping was based on the authorization logs.
2C Subfield 2 contains a contactless account number owned by an issuer, and the
issuer is actively participating in the PayPass® Mapping Service. Not all
transactions in this issuer account range are mapped, because the issuer is phasing
in the PayPass® Mapping Service. Mapping was based on a source other than the
authorization logs.
3 Subfield 2 contains a contactless account number provided by Mastercard and is
assigned to an issuer that is actively participating in the PayPass® Mapping
Service. Mapping was based on the authorizations logs.
3C Subfield 2 contains a contactless account number provided by Mastercard and is
assigned to an issuer that is actively participating in the PayPass® Mapping
Service. Mapping was based on a source other than the authorization logs.
4 Subfield 2 contains a contactless account number provided by Mastercard and is
assigned to an issuer that is passively participating in the PayPass® Mapping
Service by permitting its cardholders to request a contactless card or device via
that website. Mapping was based on the authorization logs.
4C Subfield 2 contains a contactless account number provided by Mastercard and is
assigned to an issuer that is passively participating in the PayPass® Mapping
Service by permitting its cardholders to request a contactless card or device via the
website. Mapping was based on a source other than the authorization logs.
5 Subfield 2 contains a contactless account number provided by Mastercard and is
assigned to a merchant that sponsors the contactless card or device. The issuer is
passively participating in the PayPass® Mapping Service. Mapping was based on
the authorization logs.
5C Subfield 2 contains a contactless account number provided by Mastercard and is
assigned to a merchant that sponsors the contactless card or device. The issuer is
passively participating in the PayPass® Mapping Service. Mapping was based on a
source other than the authorization logs.
Values Description
6 Subfield 2 contains a contactless account number provided by Mastercard, and
Mastercard sponsors the contactless card or device. The issuer is passively
participating in the PayPass® Mapping Service. Mapping was based on the
authorization logs.
6C Subfield 2 contains a contactless account number provided by Mastercard, and
Mastercard sponsors the contactless card or device. The issuer is passively
participating in the PayPass® Mapping Service. Mapping was based on a source
other than the authorization logs.
8 Subfield 2 contains a Mastercard In Control account number. Mapping was based
on the authorization logs.
8C Subfield 2 contains a Mastercard In Control account number. Mapping was based
on a source other than the authorization logs.
9 Subfield 2 contains the VCN used at the point of sale. Mapping was based on the
authorization log.
9C Subfield 2 contains the VCN used at the point of sale. Mapping was based on a
source other than the authorization log.
Attribute Value
Subfield ID n-2 02
Subfield Length n-2 06–19
Data Representation n...19
Justification Left
• When issuers receive PDS 0001, this subfield always contains a virtual account number/
token.
• When acquirers receive PDS 0001, this subfield always contains a real card number.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Licensed Product Identifier is provided in Fee Collection (Other)/1740 and Fee Collection
(Handling Fees)/1740 if DE 2 (Primary Account Number [PAN]) is present and the issuer
account range associated with the PAN contains a brand/product assignment that is
compatible with the brand and business service arrangement assigned to the transaction by
clearing.
The product codes in this table are representative of the credit and debit product codes
recognized by the clearing system. This table identifies the product identifier used by GCMS
(PDS 0002) as well as the Licensed Product Identifier (PDS 0003). Each Licensed Product
Identifier has a different description, although multiple Licensed Product Identifier values may
be associated with a common GCMS Product Identifier.
The Product Class Override Indicator is populated by GCMS in PDS 0158 Subfield 8. The
clearing system populates subfield 8 (Product Class Override Indicator) with a Product Class
value indicating whether product class override interchange rates were used in the interchange
fee amount designated in PDS 0146 (Amount, Transaction Fees).
NOTE: Immediate Debit products begin with “T” in the GCMS Product Identifier and have “immediate”
in the description.
Licensed
GCMS Product Product
Identifier (PDS Identifier (PDS Licensed Product Identifier
0002) 0003) Description Product Class Override Indicator
ACS ACS Digital Debit ACS, Digital Debit
BPC BPC Bill Pay Commercial BPC, Bill Pay Commercial
BPD BPD Business Premium Debit BPD, Business Premium Debit
BPL BPL Mastercard® Business Credit Plus BPL,Mastercard® Business Credit
Plus
CIR CIR Cirrus® N/A
Licensed
GCMS Product Product
Identifier (PDS Identifier (PDS Licensed Product Identifier
0002) 0003) Description Product Class Override Indicator
ETH ETH Prepaid Installment Payments A ETH: Prepaid Installment
Payments A
ETI ETI Prepaid Installment Payments B ETI: Prepaid Installment
Payments B
ETJ ETJ Prepaid Installment Payments C ETJ: Prepaid Installment
Payments C
ETK ETK Prepaid Installment Payments D ETK: Prepaid Installment
Payments D
ETL ETL Prepaid Installment Payments E ETL: Prepaid Installment
Payments E
ETM ETM Prepaid Installment Payments F ETM: Prepaid Installment
Payments F
ETN ETN Prepaid Installment Payments G ETN: Prepaid Installment
Payments G
FIA FIA Mastercard® B2B VIP 27 FIA: Mastercard ®B2B VIP 27
FIB FIB Mastercard® B2B VIP 28 FIB: Mastercard ®B2B VIP 28
FIC FIC Mastercard® B2B VIP 29 FIC: Mastercard ®B2B VIP 29
FID FID Mastercard® B2B VIP 30 FID: Mastercard ®B2B VIP 30
FIE FIE Mastercard® B2B VIP 31 FIE:Mastercard®B2B VIP 31
FIF FIF Mastercard® B2B VIP 32 FIF: Mastercard ®B2B VIP 32
FIG FIG Mastercard® B2B VIP 33 FIG: Mastercard ®B2B VIP 33
FIH FIH Mastercard® B2B VIP 34 FIH: Mastercard ®B2B VIP 34
GCP GCP Mastercard Installments Card GCP, Mastercard Installments
Premium Card Premium
GCS GCS Mastercard Installments Card GCS, Mastercard Installments
Standard Card Standard
GPP GPP Mastercard Prepaid Installments GPP, Mastercard Prepaid
Card Premium Installments Card Premium
MAB MAB World Elite™ Mastercard® for MAB, Business World Elite
Business Card
MAC MAC Mastercard® World Elite™ MAC, Corporate World Elite
Corporate Card
MAP MAP MAP, Mastercard Commercial MAP, Mastercard Commercial
Payments Account Payments Account
Licensed
GCMS Product Product
Identifier (PDS Identifier (PDS Licensed Product Identifier
0002) 0003) Description Product Class Override Indicator
MAQ MAQ Mastercard® Prepaid Commercial MAQ, Mastercard® Prepaid
Payments Account Commercial Payments Account
MBA MBA Mastercard® B2B Product 2 MBA, Mastercard® B2B Product 2
MBB MBB Mastercard Prepaid Consumer MBB, Mastercard Prepaid
Consumer
MBC MBC Mastercard Prepaid Voucher MBC, Mastercard Prepaid
Voucher
MBD MBD Mastercard® Professional Debit MDB, Commercial Debit
BusinessCard Card
MBE MBE Mastercard® Electronic™ Business MCB, Corporate
Card
MBE MRB Mastercard® Prepaid Electronic™ MCB, Corporate
Business Card (Non-U.S.)
MBG MBG Mastercard® B2B Product 3 MBG, Mastercard® B2B Product 3
MBH MBH Mastercard® B2B Product 4 MBH, Mastercard® B2B Product 4
MBI MBI Mastercard® B2B Product 5 MBI, Mastercard® B2B Product 5
MBJ MBJ Mastercard® B2B Product 6 MBJ, Mastercard® B2B Product 6
MBK MBK Mastercard Black® Card MBK, Mastercard Black
MBP MBP Mastercard Corporate Prepaid MBP, Mastercard Corporate
Prepaid
MBS MBS Mastercard® B2B Product 1 MBS, Mastercard® B2B Product 1
MBW MBW World Mastercard® Black Edition, MBW, World Mastercard® Black
Debit Edition, Debit
MCB MCB Mastercard® BusinessCard Card MCB, Corporate
MCB MLC Mastercard® Micro-Business Card MCB, Corporate
MCB MPC Mastercard® Professional Card MCB, Corporate
MCB MXB Debit Card X Code MCB, Corporate
MCC MCC Mastercard® Credit Card (mixed MCC, Consumer
BIN)
MCC MHC Mastercard® Healthcare Credit MCC, Consumer
Non-Substantiated
MCC MNS Mastercard® Non Standard MCC, Consumer
MCE MCE Mastercard Electronic Card
® ™
MCC, Consumer
Licensed
GCMS Product Product
Identifier (PDS Identifier (PDS Licensed Product Identifier
0002) 0003) Description Product Class Override Indicator
MCE MED Debit Mastercard® Electronic MCC, Consumer
Card (Non-U.S.)
MCE MIB Mastercard® Electronic™ Student MCC, Consumer
Card
MCE MIH Debit Mastercard® Electronic™ MCC, Consumer
Student Card
MCE MRL Prepaid Mastercard Electronic MCC, Consumer
Commercial Card (Non-U.S.)
MCF MCF Mastercard® Fleet Card MCF, Fleet
MCF MDM Middle Market Fleet Card MCF, Fleet
MCG MCG Gold Mastercard Card
®
MCG, Consumer
MCI MCI MCI, Mastercard Select Debit MCI, Mastercard Select Debit
MCO MCO Mastercard® Corporate Card MCO, Global Certified Corporate
MCO MDQ Middle Market Corporate Card MCO, Global Certified Corporate
MCP MCP Mastercard Purchasing Card
® ®
MCP, Mastercard Purchasing
Card
MCP MDN Middle Market Purchasing Card MCP, Mastercard Purchasing
Card
MCS MCS Standard Mastercard® Card MCC, Consumer
MCS MCU Unembossed Mastercard® Card MCC, Consumer
MCS MIC Mastercard Student Card
®
MCC, Consumer
MCS MIG Unembossed Mastercard® MCC, Consumer
Student Card
MCS MIJ Debit Mastercard® Unembossed MCC, Consumer
Non-U.S. Student Card
MCS MIU Debit Mastercard® Unembossed MCC, Consumer
(Non-U.S.)
MCS MSD Mastercard Deferred Debit MCC, Consumer
Consumer
MCT MCT Titanium Mastercard® Card MCT, Titanium
MCW MCW World Mastercard® Card MCW, World
MCW MWP Mastercard® World Prepaid MCW, Mastercard® World
MCW WMR World Mastercard® Rewards MCW, World
Licensed
GCMS Product Product
Identifier (PDS Identifier (PDS Licensed Product Identifier
0002) 0003) Description Product Class Override Indicator
MDB MDB Debit Mastercard® BusinessCard MDB, Commercial Debit
Card
MDG MDG Gold Debit Mastercard® Card MDG, Debit Mastercard Gold
MDG MXG Gold Debit Mastercard Card
®
MDG, Debit Mastercard Gold
MDH MDH Debit Other Embossed MDH, Debit World
Mastercard® Card
MDH WDR World Debit Mastercard® MDH, World Debit
Rewards
MDJ MDJ Debit Mastercard® (Enhanced) MDJ, Debit Mastercard®
(Enhanced)
MDO MDO Debit Other DMC, Debit Mastercard
MDO MXO Debit Card Other DMC, Debit Mastercard
MDP MDP Platinum Debit Mastercard® Card MDP, Debit Mastercard Platinum
MDP MEP Premium Debit Mastercard® Card MDP, Debit Mastercard Platinum
MDP MUP Premium Debit Unembossed MDP, Debit Mastercard Platinum
Mastercard® Card
MDP MXP Platinum Debit Mastercard® Card MDP, Debit Mastercard Platinum
MDR MXR Debit Card Brokerage DMC, Debit Mastercard
MDS MDS Debit Mastercard® Card DMC, Debit Mastercard
MDS MDU Debit Unembossed Mastercard ®
DMC, Debit Mastercard
Card
MDS MID Debit Unembossed Mastercard® DMC, Debit Mastercard
Student Card
MDS MIS Debit Mastercard® Student Card DMC, Debit Mastercard
MDS MPQ Mastercard® Prepaid Debit DMC, Debit Mastercard
Standard, Government Disaster
Relief
MDS MXS Standard Debit Mastercard® DMC, Debit Mastercard
Card
MDT MDT Commercial Debit Mastercard® MDT, Business Debit
Card
MDW MDW MDW, (World Elite™ Debit MDW, (World Elite™ Debit
Mastercard®) Mastercard®)
Licensed
GCMS Product Product
Identifier (PDS Identifier (PDS Licensed Product Identifier
0002) 0003) Description Product Class Override Indicator
MDW MDW MDW, (World Black™ Debit [LAC MDW, (World Black™ Debit [LAC
region excluding Mexico]) region excluding Mexico])
MEB MEB Mastercard® Executive MEB, Corporate
BusinessCard Card
MEO MEO Mastercard® Corporate Executive MEO, Corporate
Card
MES MES Mastercard Enterprise Solution MES, Mastercard Enterprise
Solution
MET MET Titanium Debit Mastercard® Card MET, Titanium Debit Mastercard®
Card
MGF MGF Mastercard® Government MCF, Fleet
Commercial Card
MGP MGP Mastercard® Prepaid Gold Payroll MGP, Mastercard®Prepaid Gold
Payroll
MGS MGS Platinum Mastercard®Prepaid MGS, Platinum Mastercard
General Spend Prepaid General Spend
MHA MHA Mastercard® Healthcare Prepaid MPM, Prepaid Mastercard
Non-Tax Consumer
MHB MHB Mastercard® HSA Substantiated MPM, Prepaid Mastercard
Consumer
MHH MHH Mastercard® HSA Non- MPM, Prepaid Mastercard
Substantiated Consumer
MIO MIO Mastercard Pay & Split MIO, Mastercard Pay & Split
MIP MIP Mastercard® Prepaid Student MPG, Debit Mastercard Prepaid
Card
MIU MIU Debit Mastercard® Unembossed MIU, Debit Mastercard
(Non-U.S.) Unembossed (Non-U.S.)
MKA MKA Digital Gold Debit MKA, Digital Gold Debit
MKB MKB Digital Platinum Debit MKB, Digital Platinum Debit
MKC MKC Digital World Debit MKC, Digital World Debit
MKD MKD Digital World Elite Debit MKD, Digital World Elite Debit
MKE MKE Digital Platinum MKE, Digital Platinum
MKF MKF Digital World MKF, Digital World
MKG MKG Digital World Elite MKG, Digital World Elite
Licensed
GCMS Product Product
Identifier (PDS Identifier (PDS Licensed Product Identifier
0002) 0003) Description Product Class Override Indicator
MKH MKH Digital World Elite Exclusive MKH, Digital World Elite Exclusive
MLA MLA Mastercard® Central Travel MLA, Mastercard® Central Travel
Solutions Air Card Solutions Air Card
MLB MLB MLB, Mastercard Brazil Benefit MLB, Mastercard Brazil Benefit
for Home Improvement for Home Improvement
MLD MLD Mastercard Distribution Card MLD, Mastercard Distribution
Card
MLE MLE MLE, Mastercard Brazil General MLE, Mastercard Brazil General
Benefits Benefits
MLF MLF MLF, (Mastercard Agro) MLF, Mastercard Agro
MLL MLL Mastercard Central Travel
®
MLL, Mastercard® Central Travel
Solutions Land Card Solutions Land Card
MNF MNF Mastercard® Public Sector MCF, Fleet
Commercial Card
MNW MNW Mastercard® World Card MNW, new World
MOC MOC Standard Maestro® Social MOC, Standard Maestro® Social
MPA MPA Mastercard® Prepaid Debit MPM, Prepaid Mastercard
Standard, Payroll Consumer
MPB MPB Mastercard® Preferred Business MCO, Global Certified Corporate
Card
MPD MPD Mastercard® Flex Prepaid MPD, Mastercard Flex Prepaid
MPE MPE Name for GCMS Product ID MPE MPE, Name for GCMS Product ID
MPE
MPF MPF Mastercard® Prepaid Debit MPM, Prepaid Mastercard
Standard, Gift Consumer
MPG MPG Debit Mastercard® Standard MPG, Debit Mastercard Prepaid
Prepaid, General Spend
MPG MUS Prepaid Unembossed MPG, Debit Mastercard Prepaid
Mastercard® Card
MPJ MPJ Mastercard Debit Prepaid Meal MPJ, Mastercard Debit Prepaid
Vouchers Meal Vouchers
MPL MPL Platinum Mastercard® Card MPL, Consumer
MPM MPM Mastercard® Prepaid Debit MPM, Prepaid Mastercard
Standard, Consumer Incentive Consumer
Licensed
GCMS Product Product
Identifier (PDS Identifier (PDS Licensed Product Identifier
0002) 0003) Description Product Class Override Indicator
MPN MPN Mastercard® Prepaid Debit MPM, Prepaid Mastercard
Standard, Insurance Consumer
MPO MPO Mastercard® Prepaid Debit MPM, Prepaid Mastercard
Standard, Other Consumer
MPP MFR Mastercard® Commercial Reward MPG, Debit Mastercard Prepaid
Funding
MPP MPP Mastercard® Prepaid Card MPG, Debit Mastercard Prepaid
MPR MPR Mastercard® Prepaid Debit MPM, Prepaid Mastercard
Standard, Travel Consumer
MPT MPT Mastercard® Prepaid Debit MPM, Prepaid Mastercard
Standard, Teen Consumer
MPV MPV Mastercard® Prepaid Debit MPM, Prepaid Mastercard
Standard, Government Consumer
MPW MPW Debit Mastercard® BusinessCard MPW, Mastercard Prepaid
Prepaid Workplace Business to Commercial
Business
MPX MPX Mastercard® Prepaid Debit MPM, Prepaid Mastercard
Standard, Flex Benefit Consumer
MPY MPY Mastercard® Prepaid Debit MPM, Prepaid Mastercard
Standard, Employee Incentive Consumer
MRC MIK Mastercard® Electronic™ Prepaid MRG, Mastercard Prepaid,
Student Card Consumer
MRC MRC Prepaid Mastercard® Electronic™ MRG, Mastercard Prepaid,
Card (Non-U.S.) Consumer
MRD MRD Platinum Debit Mastercard® MRD, Platinum Debit Mastercard
Prepaid General Spend Prepaid General Spend
MRF MRF European Regulated Individual MRF, European Regulated
Pay Individual Pay
MRG MIL Prepaid Unembossed MRG, Mastercard Prepaid,
Mastercard® Student Card (Non- Consumer
U.S.)
MRG MRG Mastercard® Prepaid Card (Non- MRG, Mastercard Prepaid,
U.S.) Consumer
MRG MRS Prepaid Mastercard® Student MRG, Mastercard Prepaid,
Card Consumer
Licensed
GCMS Product Product
Identifier (PDS Identifier (PDS Licensed Product Identifier
0002) 0003) Description Product Class Override Indicator
MRH MRH Mastercard® Platinum Prepaid MRH, Mastercard Platinum
Travel Card Prepaid Travel Card
MRJ MRJ Mastercard Prepaid Meal MRJ, Mastercard Prepaid Meal
Vouchers Vouchers
MRK MRK Prepaid Mastercard® Public MRW, Mastercard Prepaid,
Sector Commercial Card Commercial
MRL MRL Mastercard Prepaid Business MRL, Mastercard Prepaid
Preferred Business Preferred
MRO MRO Mastercard® Rewards Only MRO, Mastercard Rewards Only
MRW MRW Prepaid Mastercard® Business MRW, Mastercard Prepaid,
Card (Non-U.S.) Commercial
MSB MSB Maestro® Small Business Card MSB, Maestro Small Business
MSG MSG Prepaid Maestro® Consumer MSO, Maestro Prepaid,
Reloadable Card Consumer
MSG OLR Prepaid Maestro® Consumer MSG, Prepaid Maestro®
Reloadable Card Consumer Reloadable Card
MSI MSI Maestro® Card MSI, Maestro
MSI MSS Maestro Student Card
®
MSI, Maestro
MSJ MSJ Maestro Prepaid Meal Vouchers MSJ, Maestro Prepaid Meal
Vouchers
MSM MSM Maestro® Prepaid Consumer MSO, Maestro Prepaid,
Promotion Card Consumer
MSO MSO Maestro® Prepaid Other Card MSO, Maestro Prepaid,
Consumer
MSP MSP Muse Mastercard™ MSP, Muse Mastercard™
MSW MSW Prepaid Maestro® Corporate MSW, Maestro Prepaid,
Card Commercial
MTA MTA Mastercard® B2B Product 7 MTA: Mastercard® B2B Product 7
MTB MTB Mastercard® B2B Product 8 MTB: Mastercard® B2B Product 8
MTC MTC Mastercard® B2B Product 9 MTC: Mastercard® B2B Product
9
MTD MTD Mastercard® B2B Product 10 MTD: Mastercard® B2B Product
10
Licensed
GCMS Product Product
Identifier (PDS Identifier (PDS Licensed Product Identifier
0002) 0003) Description Product Class Override Indicator
MTE MTE Mastercard® B2B Product 11 MTE: Mastercard® B2B Product
11
MTF MTF Mastercard® B2B Product 12 MTF: Mastercard® B2B Product
12
MTG MTG Mastercard® B2B Product 13 MTG: Mastercard® B2B Product
13
MTH MTH Mastercard® B2B Product 14 MTH: Mastercard® B2B Product
14
MTI MTI Mastercard® B2B Product 15 MTI: Mastercard® B2B Product
15
MTJ MTJ Mastercard® B2B Product 16 MTJ: Mastercard® B2B Product
16
MTK MTK Mastercard® B2B Product 17 MTK: Mastercard® B2B Product
17
MTL MTL Mastercard® B2B Product 18 MTL: Mastercard® B2B Product
18
MTM MTM Mastercard® B2B Product 19 MTM: Mastercard® B2B Product
19
MTN MTN Mastercard® B2B Product 20 MTN: Mastercard® B2B Product
20
MTO MTO Mastercard® B2B Product 21 MTO: Mastercard® B2B Product
21
MTP MTP Mastercard® Platinum Prepaid MTP, Mastercard Platinum
Travel Card Prepaid Travel Card
MTQ MTQ Mastercard® B2B Product 22 MTQ: Mastercard® B2B Product
22
MTR MTR Mastercard® B2B Product 23 MTR: Mastercard® B2B Product
23
MTS MTS Mastercard® B2B Product 24 MTS: Mastercard® B2B Product
24
MTT MTT Mastercard® B2B Product 25 MTT: Mastercard® B2B Product
25
MTU MTU Mastercard® B2B Product 26 MTU: Mastercard® B2B Product
26
Licensed
GCMS Product Product
Identifier (PDS Identifier (PDS Licensed Product Identifier
0002) 0003) Description Product Class Override Indicator
MTV MTV Mastercard® B2B Product 27 MTV: Mastercard® B2B Product
27
MVA MVA Mastercard® B2B VIP 1 MVA, Mastercard® B2B VIP 1
MVB MVB Mastercard® B2B VIP 2 MVB, Mastercard® B2B VIP 2
MVC MVC Mastercard® B2B VIP 3 MVC, Mastercard® B2B VIP 3
MVD MVD Mastercard® B2B VIP 4 MVD, Mastercard® B2B VIP 4
MVE MVE Mastercard® B2B VIP 5 MVE, Mastercard® B2B VIP 5
MVF MVF Mastercard® B2B VIP 6 MVF, Mastercard® B2B VIP 6
MVG MVG Mastercard® B2B VIP 7 MVG, Mastercard® B2B VIP 7
MVH MVH Mastercard® B2B VIP 8 MVH, Mastercard® B2B VIP 8
MVI MVI Mastercard® B2B VIP 9 MVI, Mastercard® B2B VIP 9
MVJ MVJ Mastercard® B2B VIP 10 MVJ, Mastercard® B2B VIP 10
MVK MVK Mastercard® B2B VIP 11 MVK, Mastercard® B2B VIP 11
MVL MVL Mastercard® B2B VIP 12 MVL, Mastercard® B2B VIP 12
MVM MVM Mastercard® B2B VIP 13 MVM, Mastercard® B2B VIP 13
MVN MVN Mastercard® B2B VIP 14 MVN, Mastercard® B2B VIP 14
MVO MVO Mastercard® B2B VIP 15 MVO: Mastercard ®B2B VIP 15
MVP MVP Mastercard® B2B VIP 16 MVP: Mastercard ®B2B VIP 16
MVQ MVQ Mastercard® B2B VIP 17 MVQ: Mastercard ®B2B VIP 17
MVR MVR Mastercard® B2B VIP 18 MVR: Mastercard ®B2B VIP 18
MVS MVS Mastercard® B2B VIP 19 MVS: Mastercard ®B2B VIP 19
MVT MVT Mastercard® B2B VIP 20 MVT: Mastercard ®B2B VIP 20
MVU MVU Mastercard® B2B VIP 21 MVU: Mastercard ®B2B VIP 21
MVV MVV Mastercard® B2B VIP 22 MVV: Mastercard ®B2B VIP 22
MVW MVW Mastercard® B2B VIP 23 MVW: Mastercard ®B2B VIP 23
MVX MVX Mastercard® B2B VIP 24 MVX: Mastercard ®B2B VIP 24
MVY MVY Mastercard® B2B VIP 25 MVY: Mastercard ®B2B VIP 25
MVZ MVZ Mastercard® B2B VIP 26 MVZ: Mastercard ®B2B VIP 26
MWB MWB World Mastercard® for Business MWB, Business World
Card
Licensed
GCMS Product Product
Identifier (PDS Identifier (PDS Licensed Product Identifier
0002) 0003) Description Product Class Override Indicator
MWE MWE World Elite Mastercard® Card MWE, World Elite
Mastercard®Card
MWF MWF Mastercard® Humanitarian MWF, Mastercard® Humanitarian
Prepaid Prepaid
MWO MWO Mastercard® Corporate World MWO, Corporate World
Card
MWP MWP Mastercard World Prepaid MWP, Mastercard World Prepaid
OLB OLB Maestro® Small Business, OLB, Maestro Small Business,
Delayed Debit Delayed Debit
OLS OLS Maestro®, Delayed Debit OLS, Maestro Delayed Debit
PMC PMC Proprietary Credit Card (Sweden PMC, Proprietary Credit
domestic)
PMD PMD Proprietary Debit Card (Sweden PMD, Proprietary Card Debit
domestic)
PSC PSC Common Proprietary Swedish PSC, Common Proprietary Credit
Credit Card
PSD PSD Common Proprietary Swedish PSD, Common Proprietary Debit
Debit Card
PVA PVA Private Label A PVA, Private Label A
PVB PVB Private Label B PVB, Private Label B
PVC PVC Private Label C PVC, Private Label C
PVD PVD Private Label D PVD, Private Label D
PVE PVE Private Label E PVE, Private Label E
PVF PVF Private Label F PVF, Private Label F
PVG PVG Private Label G PVG, Private Label G
PVH PVH Private Label H PVH, Private Label H
PVI PVI Private Label I PVI, Private Label I
PVJ PVJ Private Label J PVJ, Private Label J
PVL PVL Private Label L PVL, Private Label L
SAP SAP Platinum Mastercard® Salary– SAP, Platinum Mastercard®
Immediate Debit Salary: Immediate Debit
SAS SAS Standard Mastercard® Salary– SAS, Standard Mastercard®
Immediate Debit Salary: Immediate Debit
Licensed
GCMS Product Product
Identifier (PDS Identifier (PDS Licensed Product Identifier
0002) 0003) Description Product Class Override Indicator
SBJ SBJ Prepaid Installment Payments H SBJ: Prepaid Installment
Payments H
SBK SBK Prepaid Installment Payments I SBK: Prepaid Installment
Payments I
SBP SBP Small Business Prepaid SBP, Small Business Prepaid
SPP SPP Mastercard Installment SPP: Mastercard Installment
Payments P Payments P
SPS SPS Mastercard Installment SPS: Mastercard Installment
Payments S Payments S
SUR SUR Prepaid Unembossed MRG, Mastercard Prepaid,
Mastercard® Card (Non-U.S.) Consumer
TCB TCB Mastercard® Executive Business TCB, Mastercard Corporate,
Card, Immediate Debit Immediate Debit
TCB TPC Mastercard® Professional Card, TCB, Mastercard Corporate,
Immediate Debit Immediate Debit
TCC TCC Mastercard® (mixed BIN), TCC, Mastercard Consumer,
Immediate Debit Immediate Debit
TCE TCE Mastercard® Electronic™, TCC, Mastercard Consumer,
Immediate Debit Immediate Debit
TCE TIB Mastercard® Electronic™ Student TCC, Mastercard Consumer,
Card, Immediate Debit Immediate Debit
TCG TCG Gold Mastercard® Card, TCC, Mastercard Consumer,
Immediate Debit Immediate Debit
TCO TCO Mastercard® Corporate, TCO, Global Certified Corporate,
Immediate Debit Immediate Debit
TCO TLA Mastercard® Central Travel TCO, Global Certified Corporate,
Solutions Air, Immediate Debit Immediate Debit
TCS TCS Mastercard® Standard Card, TCC, Mastercard Consumer,
Immediate Debit Immediate Debit
TCS TIC Mastercard® Student Card, TCC, Mastercard Consumer,
Immediate Debit Immediate Debit
TCS TIU Mastercard® Unembossed, TCC, Mastercard Consumer,
Immediate Debit Immediate Debit
TCW TCW World Signia Mastercard® Card, TCW, Mastercard World Signia,
Immediate Debit Immediate Debit
Licensed
GCMS Product Product
Identifier (PDS Identifier (PDS Licensed Product Identifier
0002) 0003) Description Product Class Override Indicator
TEB TEB Mastercard® Executive TEB, Mastercard Corporate,
BusinessCard Card Immediate Debit
TNW TNW Mastercard® New World, TNW, Mastercard New World,
Immediate Debit Immediate Debit
TPB TPB Mastercard® Preferred Business TCO, Global Certified Corporate,
Card, Immediate Debit Immediate Debit
TPL TPL Platinum Mastercard®, TCC, Mastercard Consumer,
Immediate Debit Immediate Debit
TWB TWB World Mastercard® Black Edition, TWB, World Mastercard® Black
Immediate Debit Edition, Immediate Debit
WBE WBE World Mastercard® Black Edition WBE, World Mastercard® Black
Edition
WPD WPD Mastercard® World Prepaid Debit WPD, World Prepaid Debit
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Issuers that participate in the Mastercard Product Graduation program, should refer to the
Account Level Management Manual for details on how PDS 0003 will be populated.
For issuers that participate in the Mastercard Product Graduation program, PDS 0003 will be
populated on the basis of whether the transactions are qualified or non-qualified, as follows.
For qualified transactions authorized via the Mastercard Network, this field will reflect the
product identifier associated with the graduated account number. For a transaction to qualify,
all the conditions in this list must be met:
• Transaction qualifies for the U.S. intraregional business service arrangement (2/010001).
• Transaction type must be equal to:
– DE 3 (Processing Code), subfield 1 (Cardholder Transaction Type) = 00 (Purchase [Goods
and Services])
– DE 3, subfield 1 = 09 (Purchase [Goods and Services] with Cash Back)
– DE 3, subfield 1 = 18 (Unique Transaction)
For non-qualified transactions, this field identifies the Licensed Product Identifier according to
the licensed product associated with the issuer account range. Non-qualified transactions are
defined as follows:
• Transactions not authorized through the Mastercard Network
• Transactions that do not meet all of the conditions defined for qualified transactions
For issuers that participate in the Canada Consumer Product Monitoring service, PDS 0003 is
populated as follows:
• For qualified transactions authorized using the Mastercard Network, this field reflects the
product code of the registered PAN.
• For non-qualified transactions, this field identifies the Licensed Product Identifier according
to the licensed product associated with the issuer account range. Non-qualified transactions
are listed as follows:
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Requirements
PDS 0004 must be present on Payment Transactions (Processing code = 28) when Transaction
Type Identifier (PDS 0043) has a value C67 and the Interchange Rate Designator is a
Mastercard Merchant Presented (MPQR) (PDS 0158, subfield 4 is value QR).
Attributes
Subfield ID n-2 01
Subfield Length n-2 02
Data Representation n-2
Justification N/A
Subfield 1 must be present and contain one of the valid values listed in this table.
Values
Values Description
01 Credit
02 Debit
03 Prepaid
04 Deposit Account
05 Mobile Money Account
06 Cash
07 Other
In the Asia/Pacific region, funding sources are limited to Mastercard® cards. In subfield 1, values
04, 05, 06, and 07 are not applicable.
Attribute Value
Subfield ID n-2 02
Subfield Length 34
Data Representation an...34
Justification Left
Subfield 2 must be present, numeric, cannot contain all zeros, and cannot exceed a length of 20.
Subfield 2 is a variable length field with a length value 01 - 34, however, the maximum length
will be restricted to 20.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
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 in messages that it processed.
The clearing system may report up to a maximum of 10 exception conditions detected in a
message.
Justificati
Number Positions Name Attribute on
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 from 1 to 10 times in PDS 0005 to report a
maximum of 10 error conditions in a single message.
Value Description
00 Fatal Error; invalid or incomplete data was encountered that
prevented the clearing system from processing the transaction.
01–25 Local domestic reason codes
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Justificati
Number Positions Name Attribute on
1 1–3 Card Program Identifier ans-3 left
2 4 Business Service Arrangement Type Code ans-1 left
3 5–10 Business Service ID Code ans-6 left
Value Description
1 Interregional
2 Intraregional
3 Intercountry
4 Intracountry
8 Member-to-member
Attributes
Usage
Application notes
The Clearing system provides PDS 0010 to the issuer if the account range participates in the
Currency Rate service and the transaction qualifies for the service.
Attributes
Justification N/A
Values
Value Description
Y (Yes) The issuer is registered for the currency rate service
and Clearing applied the service to this transaction.
N (No) The issuer is registered for the currency rate service
but Clearing did not apply the service to this
transaction.
Attributes
Values
Value Description
Date field YYMMDD format
Attributes
Usage
Application notes
The Clearing system provides PDS 0011 to the issuer whenever it performs the mapping for a
token that has an associated virtual card number.
Attributes
Attribute Value
Subfield ID n-2 01
Subfield length n-2 02
Data representation ans-2
Justification Left
Values
Values Description
8C Subfield 02 contains a Mastercard In Control
virtual card number. Mapping was based on a
source other than the authorization logs.
Attributes
Attribute Value
Subfield ID n-2 02
Subfield length n-2 06-19
Data representation n...19
Justification Left
When issuers receive PDS 0011, this subfield always contains a virtual card number.
Attributes
Usage
This table shows the usage of this data element (whether it is mandatory, conditional, optional,
system-provided, or not required) in applicable messages.
Usage
Attributes
Usage
This table shows the usage of this data element (whether it is mandatory, conditional, optional,
system-provided, or not required) in applicable messages.
Usage
Attributes
Attributes
Attribute Value
Subfield ID n-2 02
Subfield Length n-2 01
Data Representation an-1
Justification N/A
Values
Value Description
0 Transaction not eligible for use of the currency conversion rate effective at the
time of authorization processing hence GCMS Central site processing date
rates applied for currency conversion.
1 Authorization processing date rates applied for currency conversion rates
applied for currency conversion.
2 GCMS Central site processing date rates applied for currency conversion.
Attributes
Attribute Description
Data Representation AN-10; TAGLLLVAR
Length Field 10 positions, value=010
Data Field Fixed length
Attribute Description
Subfields Subfield 1 (Digital Service Provider ID 1)
Subfield 2 (Digital Service Provider ID 2)
Justification Left
Usage
Whether the usage is mandatory, conditional, optional, system-provided, or not required is as
noted for each applicable message.
Application notes
The clearing system populates values in PDS 0016 in First Presentment/1240 messages only
when the issuer has opted for the service to receive it.
Attributes
Attribute Value
Data representation an-5
Data field Contents of position 5
Justification Left
Values
Attributes
Attribute Value
Data representation an-5
Data field Contents of position 5
Justification Left
Values
Attributes
Usage
This table shows the usage of this data element (whether it is mandatory, conditional, optional,
system-provided, or not required) in applicable messages.
Usage
Values
This table describes the classification descriptions and values.
Values
Application notes
The transaction integrity classification is provided to all issuers in the U.S. Region of Mastercard®
credit and Debit Mastercard® cards.
Attributes
Usage
This table shows the usage of this data element (whether it is mandatory, conditional, optional,
system-provided, or not required) in applicable messages.
Usage
Attributes
Values
Values Description
0 Dedicated mPOS Terminal with PCI complaint Dongle (with or without
keypad)
1 Off the Shelf Mobile Device
2-9 Reserved for Future Use
Attributes
Attribute Description
Data representation ans...57; LLVAR
Length Field: 2 positions, value = 57
Data field Contents of subfields 01–04
Subfields 4
Justification See Subfields
Usage
Whether the usage is mandatory, conditional, optional, system-provided, or not required is as
noted for each applicable message.
Subfield values
Attributes
Attribute Description
Data representation n-1
Data field Contents of position 1
Justification Left
Values
Value Description
1 Mastercard
2 Acquirer
Value Description
3 Issuer
4-9 Reserved for future use
Attributes
Attribute Description
Data representation n-1
Data field Contents of position 1
Justification Left
Values
Value Description
1 SQR
2 Click to Pay
3 Biometrics Checkout Program
4 Next Gen Point-of-Interaction
5-9 Reserved for future use
Attributes
Attribute Description
Data representation ans...15
Data field Contents of position 15
Attribute Description
Justification N/A
Attributes
Attribute Description
Data representation ans...40
Data field Contents of position 40
Justification N/A
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
Additional terminal operating environment values are listed in this table.
Values
Value Description
A Transaction has been initiated remotely and completed at a physical terminal
on premises of the acceptor facility.
B Transaction has been initiated remotely and completed at a physical terminal
off premises of the acceptor facility.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Transactions submitted in the U.S. region with the following terminal types may not have an
Interchange Rate Designator (subfield 4 of PDS 0158 [Business Activity]) value of 60
(Commercial 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 DE 26 (Acceptor Business Code [MCC]) 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.
Values
Terminal Type codes for point-of-interaction (POI) terminal devices are listed in this table.
Values
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)
CT8 Reserved for Future Use
CT9 MPOS Acceptance Device
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 0023 must contain a value of CT6 when DE 22, Subfield 7 is populated with a value of S.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
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.
Justificati
Number Positions Name Attribute on
1 1 Message Reversal Indicator a-1; R or N/A
space
2 2–7 Central Site Processing Date of Original Message n-6; N/A
YYMMDD
NOTE: Chargeback reversals cannot be processed in the same file as the original chargeback.
When PDS 0025 is present in First Presentment/1240 messages, the clearing system compares
that to original first presentment message and if it is within 7 days from the date of original
first presentment processing, it applies the foreign exchange rate of original first presentment
transaction. In all other instances, the clearing system uses current business processing date for
currency conversion.
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.
Attributes
Usage
This table shows the usage of this PDS (mandatory, conditional, optional, system-provided, or
not required) in applicable messages.
Usage
The presence of PDS 0026 in a File Header (Customer-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 PDS 0025 (Message Reversal Indicator) in each
message.
When PDS 0026 is present in the File Header (Customer-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 (Customer-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
Example 2
Justificati
Number Positions Name Attribute on
1 1 File Reversal Indicator a-1; R N/A
2 2–7 Central Site Processing Date of Original File n-6; N/A
YYMMDD
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, or
system-provided) in applicable messages.
Usage
NOTE: If acquirers or issuers do not submit PDS 0027 for Brazil Flex Cards domestic transactions, the
clearing system will not reject the associated messages.
Attributes
Subfields: None
Justification: Left
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Attributes
Usage
This 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: Not available. Edit if presented. Reject transaction if edit fails.
Forward message to destination if edit validates.
• Second Presentment/1240: Not available. Edit if presented. Reject transaction if edit fails.
Forward message to destination if edit validates.
• First Chargeback/1442 and Arbitration Chargeback/1442: Not available. Edit if presented.
Reject transaction if edit fails. Forward message to destination if edit validates.
Funding transaction usage:
• First Presentment/1240: Optional. If present, edit must validate. Forward message to
destination if edit validates.
• Second Presentment/1240: Optional. If present, edit must validate. Forward message to
destination if edit validates.
• First Chargeback/1442 and Arbitration Chargeback/1442: Optional. If present, edit must
validate. Forward message to destination if edit validates.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
The acquirer populates PDS 0042 to identify e-commerce transactions that are initiated at a
Masterpass merchant, but the cardholder did not use Masterpass to facilitate the transaction.
Values
This table lists the valid values.
Values
Value Description
A Masterpass Enabled Merchant
Requirements
These are requirements for PDS 0042.
• When PDS 0042 is provided, value A is the only character permitted; a space is not allowed.
• PDS 0042 is required for e-commerce transactions submitted for the Masterpass enabled
merchant incentive. If the acquirer fails to provide PDS 0042 in the First Presentment
message, the transaction will not qualify for the incentive.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable 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 Gaming. It contains the Transaction Type Identifier.
PDS 0043 must be present in First Presentment/1240 transactions submitted for the U.S.
region interchange programs, as defined in the Interchange Manual, unless the transaction is a
credit, reversal, or Collection Only transaction.
PDS 0043 is required for all Payment Transactions (DE 3 [Processing Code] subfield 1 = 28).
PDS 0043 is required for all MoneySend™ Funding Transactions (DE 3, subfield 1 = 00 and DE 26
[Acceptor Business Code (MCC)] = 6538, 4829 or 6540).
PDS 0043 is required for all MoneySend Payment Transactions (DE 3, subfield 1 = 28 and DE 26
= 6536 or 6537).
PDS 0043 is required for all MoneySend payment transactions (DE 3, subfield 1 = 28 [Payment
Transaction]). PDS 0043 will contain one of the following values.
Values
PDS 0043 values are established and administered under the authority of brand-specific
program and service management and marketing personnel. The values are listed in this table.
Values
Value Description
C02 Mastercard rebate
C03 rePower Load Value
Value Description
C04 Gaming Re-pay
C06 Payment of a credit card balance with cash or check
C07 General Person-to-Person Transfer
C51 MoneySend Additional Funding/Payment Indicator (Reserved for
Future Use)
C52 General Transfer to Own Account
C53 Agent Cash Out
C54 Payment of Own Credit Card Bill
C55 Business Disbursement
C56 Government/Non-profit Disbursement
C57 Rapid Merchant Settlement
C58 Cash in at ATM
C59 Cash in at Point of Sale
C60 MoneySend Additional Funding/Payment Indicator (Reserved for
Future Use)
C61 MoneySend Additional Funding/Payment Indicator (Reserved for
Future Use)
C62 MoneySend Additional Funding/Payment Indicator (Reserved for
Future Use)
C63 MoneySend Additional Funding/Payment Indicator (Reserved for
Future Use)
C64 MoneySend Additional Funding/Payment Indicator (Reserved for
Future Use)
C65 General Business to Business Transfer
C66 MoneySend Additional Funding/Payment Indicator (Reserved for
Future Use)
C67 Mastercard Merchant Presented (MPQR)
C68 Mastercard Merchant Presented (MPQR) Refund
C91 Utility Payments, Brazil domestic transactions
C92 Government Services, Brazil domestic transactions
C93 Mobile phone top-ups, Brazil domestic transactions
C94 Coupon Booklet Payments (CARNE), Brazil domestic transactions
F07 General Person-to-Person Transfer
Value Description
F08 Person-to-Person Transfer to Card Account
F52 General Transfer to Own Account
F53 Agent Cash Out
F54 Payment of Own Credit Card Bill
F55 Business Disbursement
F61 Transfer to Own Staged Digital Wallet Account
F64 Transfer to Own Debit or Prepaid Card Account
F65 General Business-to-Business Transfer
P01 Mastercard ATM Cash Pick-Up Transaction
P10 Purchase repayment
P70 Cryptocurrency
P71 High-risk Securities
PDS 0043 (Transaction Type Identifier) cannot contain all spaces or all zeros.
The Payment Transaction Types of C03–C07, C52–C59, and C92–C94 are valid for Clearing, via
specific business service arrangements.
For payment transactions: transactions submitted with a Cardholder Transaction Type of 28
(Payment Transaction) require a value of C04, C07, C52, C53, C54, C55, C56, C57, C58, C59,
and C65.
For funding transactions: transactions submitted with a Cardholder Transaction Type of 00
(Purchase Goods and Services) require a value of C07, C52, C53, C54, C55, C56, C57, C65 for
MCC 6538 (MoneySend Funding) and F07, F08, F52, F53, F54, F55, F61, F64, and F65 for MCC
4829 (Money Transfer) or MCC 6540 (POI Funding Transactions).
For funding Refund transactions: transactions submitted with a Cardholder Transaction Type of
20 (Purchase Return) require a value of C07, C52, C53, C54, C55, C56, C57, C65 for MCC 6538
(MoneySend Funding) and F07, F08 F52, F53, F54, F55, F61, F64, and F65 for MCC 4829
(Money Transfer) or MCC 6540 (Funding Transactions).
Values C07, C52, C53, C54, C55, C56, C57, C58, C59, and C65 indicate that the payment
transaction is associated with Mastercard® MoneySend and MCC 6536 (MoneySend
Intracountry) or MCC 6537 (MoneySend Intercountry). MoneySend payment transactions
require the submission of the Financial Detail Addendum, Payment Transaction Detail/1644.
Values C07, C52, C53, C54, C55, C56, C57, C58, C59, and C65 indicate that the Payment
Transaction is associated with Mastercard® MoneySend and MCC 6536 or 6537. In the MEA
region, the value C04 indicates that the Gaming Payment Transaction is associated with MCC
7995. Values C07, C52, C53, C54, C55, C56, C57, C58, C59, and C65 indicate that the Payment
Transaction is associated with Mastercard® MoneySend and MCC 6536 or 6537.
MoneySend Payment Transactions and Gaming Payment Transactions require the submission of
the Financial Detail Addendum, Payment Transaction Detail/1644.
The value C04 indicates that the Gaming Payment Transaction is associated with:
• In the Europe region, Intra-European and inter-European IRDs 20 and 23, and MCC 7995; or
• In the U.S. region
– MCC 7800 (Government Owned Lottery [U.S. Region Only])
– MCC 7801 (Internet Gambling [U.S. Region Only])
– MCC 7802 (Government Licensed Horse/Dog Racing [U.S. Region Only])
– MCC 7994 (Video Game Arcades/Establishments)
Attributes
Usage
This table shows the usage of this data element (whether it is mandatory, conditional, optional,
system-provided, or not required) in applicable messages.
Usage
Attributes
Values
This table lists the valid values.
Values
Values Description
C The transaction qualifies for the CVC 2 Validation Program. GCMS
populates this PDS.
Attributes
Values
This table lists the valid values.
Values
Values Description
I Value for PayPass transaction is ineligible for chargeback for reason
code 4837 based upon the Cardholder Verification Method (CVM)
limit in effect on the day of the transaction. This field is populated by
GCMS on Presentment/1240 messages. The value I indicates that
chargeback is not allowed for above mentioned chargeback reason
codes if the transaction amount is less than or equal to the CVM
limit as defined on IPM MPE IP0058T1. Refer to the Chargeback
Guide for details about processing PayPass transactions.
(space) Transaction is eligible for chargeback.
Attributes
Subfields: None
Justification: N/A
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Mastercard will populate PDS 0045 to identify and process installment transactions.
Values
This table lists the valid values.
Values
Value Description
A Transaction approved for installment processing.
C Credit transaction to reverse the purchase transaction
E Transaction eligible for Installment Processing
M Approved for installment processing and Mastercard generated
installment payment data
P Purchase transaction of each split installment transaction
Y Transaction qualifies for the installment processing
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
If PDS 0046 is submitted in a First Presentment/1240 message, acquirers must also submit it in
the Second Presentment/1240 message. Similarly, issuers that receive the PDS 0046 in first
presentment must retain it and provide it in the subsequent First Chargeback/1442 and
Arbitration Chargeback/1442 messages.
PDS 0046 is only available for Japan intracountry transactions.
If present, Mastercard will remove PDS 0046 from any Presentment message submitted by a
non-Japan acquirer. The transaction will not be rejected.
Attributes
Usage
PDS 0052 must be present in First Presentment/1240 transactions related to transactions
authorized with a static accountholder authentication value assigned by Mastercard®.
All Mastercard® e-commerce/Identity Check acquirers and acquirers supporting MDES
transactions are expected to send the Mastercard validated/modified Electronic Commerce
Security Level indicator value from the Authorization Request Response/0110 message in the
first presentment for clearing.
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
If the acquirer fails to provide PDS 0052 in the First Presentment of a UCAF transaction,
regardless of the IRD submitted, the authorization will not qualify for liability shift.
Mastercard® considers the inclusion of PDS 0052 in these messages to be an electronic
commerce (e-commerce) clearing requirement associated with UCAF processing. Adherence to
Values
A value of 0 in PDS 0052, subfield 3 (UCAF Collection Indicator) 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 [Business Activity], subfield 4), must
include PDS 0052. The value in PDS 0052, subfield 3 (UCAF Collection Indicator) must be a 1.
First Presentment/1240 transactions submitted with a value of PF (Premium Full UCAF) in PDS
0158 subfield 4 (Business Activity/Interchange Rate Designator) must include Electronic
Commerce Security Level Indicator (PDS 0052). The value in PDS 0052, subfield 3 (UCAF
Collection Indicator) must be a 2 or 3. If PDS 0052 subfield 3 contains a value 3 (indicating
MARP transaction) then PDS 0176 must be submitted.
For details about the Maestro® Utility Payment Program (MUPP), intracountry recurring
payment programs (Europe Region), and static Accountholder Authentication Values (AAVs),
refer to these documents:
• Transaction Processing Rules
• “Modifications to e-Commerce Authentication Programs,” Europe Region Operations Bulletin
No. 2, 3 February 2014
PDS 0052, if present must be numeric and a fixed length of 3.
8–9 Reserved for future use 8–9 Reserved for future use
Attributes
Values
This table lists the valid values.
Values
Values Description
0 Reserved for existing Mastercard Europe/Visa definitions
1 Reserved for future use
2 Channel
3–8 Reserved for future use
9 Reserved for future use
Attributes
Values
This table lists the valid values.
Values
Values Description
0 Reserved for future use
1 E-commerce/Identity Check Program
2 Processed through MasterPass®
3 Reserved for future use
4 Tokenized payment
5–9 Reserved for future use
Attributes
Values
This table lists the valid values.
Values
Values Description
0 Non-authenticated payment, Identity Check transaction with failed
authentication, or Tokenized Payment with Dynamic Token
Verification Code (DTVC).
1 UCAF data collection is supported by the merchant, and UCAF data
must be present (DE 48, subelement 43 must be present and contain
an attempt AAV for Mastercard® Identity Check).
2 UCAF data collection is supported by the merchant, and UCAF data
must be present (DE 48, subelement 43 must contain a fully
authenticated AAV). This includes cardholder-initiated transactions
(CIT) for authentication.
3 UCAF data collection is supported by the merchant, and UCAF
(Mastercard assigned Static Accountholder Authentication Value)
data must be present.
Value Description
210 Present in unauthenticated transactions, or in transactions where an Identity Check
™
merchant has chosen not to undertake Identity Check™, or where Identity Check™
failed authentication and the merchant desires to proceed with the transaction. Also
present in transactions with a DTVC
211 Mastercard® Identity Check™ transaction. UCAF data contains either an Attempts
AAV or a Non-Low Risk AAV for Mastercard® Identity Check™
Value Description
212 Mastercard® Identity Check™transaction. UCAF data contains either a Fully
Authenticated AAV or a Low Risk AAV for Mastercard® Identity Check™
214 Mastercard® Identity Check™where merchant has chosen to share data to generate
insights within the authorization (used in Identity Check™ Insights transactions).
Insights provided to the Issuer in DE 48, subelement 56
216 Mastercard® Identity Check™transaction. Merchant Risk Based Decisioning
217 Mastercard® Identity Check™Merchant Initiated Transactions
242 Authenticated tokenized transaction with DSRP cryptogram. Transaction is not
eligible for fraud-related chargeback by the issuer
246 Tokenized transaction with DSRP cryptogram
247 Tokenized Merchant Initiated Transaction
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
The clearing system populates values in PDS 0056 in First Presentment/1240 messages for all
Mastercard Electronic™ products. This value indicates to the issuer whether the acquirer and
their merchant participate in the Mastercard Electronic™ program.
Values
The Mastercard Electronic™ indicator values are listed in this table.
Values
Value Description
C Participant in Mastercard® only (considered not a Mastercard
Electronic™ participant)
E Acquirer and its merchants both participate in Mastercard
Electronic™ (considered a Mastercard Electronic™ participant).
U Unidentified acquirer. It is unknown whether the acquirer is a
Mastercard Electronic™ participant.
Attributes
Justification: N/A
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, PDS 0057 must contain a valid value. The values are shown in this table.
Values
Value Description
01 The transaction is a Mastercard® commercial card transaction
initiated via the Payment Gateway (a Payable Account transaction).
This value was introduced with GCMS Release 06.2 to support future
business opportunities.
02 This transaction is from an acceptor terminal that is exempt from
having an IIAS because it has met the IRSs 90 percent qualification
rule.
03 The transaction is from an acceptor terminal that verified qualified
healthcare expenses against an Inventory Information Approval
System (IIAS) during the authorization process.
04 The transaction is submitted as a healthcare transaction but from a
non–IIAS-certified merchant.
Customers may only submit values of 1, 2, or 3. The value of 4 may only be populated by GCMS.
GCMS updates the value of PDS 0057 from a value of 03 to a value of 04 if one of these occurs:
• A transaction is submitted with PDS 0057 value of 03, but PDS 0176 (Mastercard Assigned
ID) is not present.
• GCMS was unable to validate that PDS 0176 was inventory information approval system
(IIAS)-certified.
Use CIS DE 48
(Additional
Data),
subelement 61
(POS Data,
Extended
Condition
To map to PDS Codes),
0057 subfield 3
(Transaction (Real-time
Category Substantiation
Indicator), Indicator),
value Description value Description
01 Transaction is a Mastercard® 0 Merchant terminal did not verify
commercial card transaction the purchased items against the
initiated via the Payment IIAS.
Gateway (a Payable Account
transaction).
03 Transaction is from an acceptor 01 Merchant terminal verified the
terminal that verified qualified purchased items against an IIAS.
healthcare expenses against an
Inventory Information Approval
System (IIAS) during the
authorization process.
02 Transaction is from an acceptor 02 Merchant claims exemption from
terminal that is exempt from using an IIAS, based on the IRS
having an IIAS because it has met 90 percent rule.
the IRSs 90 percent qualification
rule.
Use CIS DE 48
(Additional
Data),
subelement 61
(POS Data,
Extended
Condition
To map to PDS Codes),
0057 subfield 3
(Transaction (Real-time
Category Substantiation
Indicator), Indicator),
value Description value Description
04 Transaction is submitted as a 04 Transaction was submitted as
Healthcare transaction but from real-time substantiated but from
a non–IIAS certified merchant. a non-IIAS certified merchant.
Mastercard® uses this value to
notify the issuer that the
merchant could not be
substantiated. Acquirers may not
use this value.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Attributes
Attribute Value
Subfield ID: n-2 01
Data Representation: ans...064; LLLVAR
Subfield Length: n-2 02
Data Field: n-2
Justification N/A
Values
The financial account identifier value is a minimum of 9 characters and a maximum of 64
characters.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Attributes
Data Representation: an–2
Data Field: Contents of positions 1–2
Justification: Left-justified
Values: 01 = Chip to Magnetic Stripe Conversion Service
Attributes
Data Representation: an–1
Attributes
Data Field: Contents of positions 3
Justification: N/A
Values: C= Conversion of the M/Chip transaction to a
magnetic stripe transaction was complete
Attributes
Data Representation: ans–1
Data Field: Contents of positions 4
Justification: N/A
Values: Space
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
This table lists the valid values.
Values
Value Description
1 Transaction qualified for Authentication Service Type 1
2 Transaction qualified for Authentication Service Type 2
Attributes
Attribute Value
Data representation ans…63; TAGLLLVAR
Tag field 0073
Length field 63 positions
Data field Variable length, 003-063 positions
Subfields 3
Occurrences 1-3
Justification Left
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Subfield details
This PDS contains 3 subfields.
Data
Subfield ID Subfield length representation Data field Justification
Subfield 1 n-2, 01 n-3, 003 a-3 3 positions Left
(Taxpayer
Country Code)
Subfield 2 n-2, 02 n-3, 030 ans-030 30 positions Left
(Taxpayer
Identification
Code)
Subfield 3 (Tax n-2, 03 n-3, 030 ans-030 30 positions Left
Registration
Code)
Attributes
Justification: N/A
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, PDS 0080 must be alphanumeric and represents the tax amount calculated from the
Amount, Transaction (DE 4) or the Amount, Transaction Fee (PDS 0146) on Presentment/1240
and Chargeback/1442 messages, and from the Amount, Transaction (DE 4) on Fee Collection/
1740 messages.
For applicable intracountry Mexico transactions, the clearing system supplies the tax amount,
except on ATM activity.
For applicable intracountry Mexico 1740 transactions, PDS 0080 should be submitted by
customers where the Fee Processing Impact Switch is set to N on IP0097T1 for the message
reason code.
The Mastercard® Network supplies the tax amount in PDS 0080, when applicable.
Subfields
Value Description
010 Value Added Tax (VAT)
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS comprises four subfields that indicate the file type, the file processing date, the ID of
the customer 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 customer processing center.
For customer-generated files, the clearing system retains 180 days of file ID history for each
customer 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 PDS 0026 (File Reversal Indicator) match an entry in the
file ID history file.
Value Description
001 Clearing file: Generated by Mastercard®
002 Clearing file: Member-generated
003 Early Reconciliation file: Generated by Mastercard®
011 Clearing file: Generated by LPRUS
013 Early Reconciliation file: Generated by LPRUS
021 Clearing file: Generated by NSPK
023 Early Reconciliation file: Generated by NSPK
031 Clearing file: Generated by LPIDN
033 Early Reconciliation file: Generated by LPIDN
901 Generated by Mastercard®, MasterCom System
902 Generated by Mastercard®, Rewards System
903 Generated by Mastercard®, EPSNet System
904 Generated by Mastercard® Network
Value Description
905 Clearing file: Generated by Mastercard® SEND
906 Clearing file: Generated by Mastercard® CBK
907–999 Clearing file: Generated by Mastercard® on behalf of member
Attributes
Usage
This table shows the usage of this data element (whether it is mandatory, conditional, optional,
system-provided, or not required) in applicable messages.
Usage
Subfields
Values
Values Description
1 Mainframe
2 Auto-Edit
3 Workstation Plus
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Customers that stack multiple logical files in a physical transmission may use this optional PDS.
Customers 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 may be placed into PDS 0110 in each File Header/1644 in
the physical transmission.
The clearing system generates reconciliation information that accumulates data at the
individual logical file level. Transmission-level totals are not provided.
Subfields
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 customer processing
center.
Value Description
002 Clearing transmission: member-generated
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable 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 listed in this table.
Values
Value Description
P Production
T Test
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS assists customers in referencing and reconciling various posted miscellaneous fees and
billings using the fee collection message.
A customer may assign PDS 0137 as a documentation reference for customer-generated fee
collection messages sent to another customer.
Customers 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.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable 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 DE 71
(Message Number) from the rejected message.
This PDS is present if the clearing system can parse the rejected message.
NOTE: Both subfields of PDS 0140 are always USD, Currency Code 840, with a currency exponent of
two.
Attributes
Usage
This table shows the usage of this data element (whether it is mandatory, conditional, optional,
system-provided, or not required) in applicable messages.
Usage
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Attributes
Values
The seven left-most digits denote the values that appear to the left of the decimal of the
customer currency conversion rate, and the six right-most digits denote the values that appear
after the decimal of the customer currency conversion rate. For example, a data value of
0000002350000 indicates a conversion rate of 0000002.350000.
Attributes
Values
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 customer currency
conversion amount of BRL 212.50 is expressed as 000000021250.
Attributes
Attribute Description
Data Representation: ans-15; TAGLLL
Tag Field: 0142
Length Field: 3 positions, value = 015
Data Field: Fixed length, 15 positions
Subfields: 3
Attribute Description
Justification: See subfields
Usage
The following table shows the usage of this PDS (whether it is mandatory, conditional, optional,
system-provided, or not required) in applicable messages.
Values
Issuers will receive these subfields if they have opted in for any of the supported services and if
those services were performed on the given transaction.
If present, PDS 0142 must be a fixed length of 15 and will represent European Issuer Foreign
exchange reference rate and any percentage difference between the Mastercard Foreign
Exchange rate.
PDS 0142 subfield 01 provides the “currency conversion cross-rate” from DE 4 (Amount,
Transaction) to DE 6 (Amount, Cardholder Billing).
The first position or the leftmost digit is populated with the number of decimal places and
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 percent.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Fees are assessed in an appropriate currency according to card program identifier, program, or
service rules. For example, a fee assessed to the customer, 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. This field is used by Mexico Domestic Business Service 4/484001.
Values
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.
Notes
PDS 0148 (Currency Exponents) must be present with PDS 0145 to identify the transaction’s
exponent.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
For ATM transactions submitted by the Mastercard® Network, 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 B in subfield 1 of PDS 0165
[Settlement Indicator]), and the business service assigned to the transaction does not specify
that fees should be calculated:
• If the message originator populates PDS 0146 with expected fees, the clearing system
passes them to the receiving customer.
• If the message originator does not provide PDS 0146, PDS 0146 will not be present at all in
the message sent to the receiving customer.
In all other conditions, the clearing system calculates the fees and provides them to the receiving
customer in PDS 0146.
Values
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.
NOTE: This field remains unchanged from the original message when processing a reversal of a
previous message.
Subfields
Each transaction fee consists of seven subfields as defined in this table. Each fee requires 36
positions; the length of this PDS must be a multiple of 36, with a maximum length of 432
positions.
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.
Value Description
00 Transaction interchange fee (fixed plus variable fee amount)
Value Description
19 Debit transaction destination
29 Credit transaction destination
00 Not applicable: May be used if member provides PDS 0146
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 This settlement service is identified in PDS 0159 (Settlement Data).
Attributes
Usage
For all transactions where extended decimal precision is active, the clearing system provides this
field. This table shows the usage of this PDS (whether it is mandatory, conditional, optional,
system-provided, or not required) in applicable messages.
Usage
Values
All currency amounts are expressed to 6 decimals without a decimal separator in accordance
with ISO standards for currency notation. For example, an Interchange Fee amount of
USD .000123 is expressed as 000000000000000123.
NOTE: This field remains unchanged from the original message when processing a reversal of a
previous message.
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.
Value Description
00 Transaction interchange fee (fixed plus variable fee amount).
Value Description
19 Debit transaction destination.
29 Credit transaction destination.
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; this settlement service is identified as PDS 0159
(Settlement Data).
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
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 DE 4 (Amount, Transaction), DE 49 (Currency
Code, Transaction), and DE 30 (Amounts, Original) 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 DE 5 (Amount
Reconciliation) and DE 50 (Currency Code, Reconciliation); DE 6 (Amount, Cardholder Billing)
and DE 51 (Currency Code, Cardholder Billing); or PDS 0146 (Amounts, Transaction Fee).
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 Canada region customers 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.
Values
If present, PDS 0148 cannot contain all low values or all high values.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
Subfield 1 (Currency Code, Original Transaction Amount) 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.
Subfield 2 (Currency Code, Original Reconciliation Amount) must contain all zeros.
Attributes
Attribute Value
Data representation ans-26; TAGLLL
Tag field 0150
Length field 3 positions, value = 026
Data field Fixed length, 26 positions
Subfields 7
Justification Left
Values
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Application notes
Mastercard is not enforcing edits to check the presence or content of any data.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, PDS 0157 must contain a valid value of ALTC to indicate Alternate Processor Cross-
border transaction.
If PDS 0157 Alternate Processor Indicator is present, PDS 0165 subfield 1 (Settlement
Indicator) must contain a value of C.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, PDS 0158 must be a length of three positions and cannot contain all low values or all
high values.
Attribute Value
Subfield ID n-2 01
Attribute Value
Subfield Length n-2 03
Data Representation ans-3
Justification Left
Values
Valid card program identifiers for programs and services the clearing system supports are listed
in this table.
Values
Values Description
CIR Cirrus®
DMC Debit Mastercard®
MCC Mastercard® Credit
MSI Maestro®
PRO Sweden domestic brand
PVL Private label
spaces Customers must submit all spaces in this subfield unless specifically
directed otherwise by Mastercard®. The clearing system will then
determine the correct value and populate this subfield before
sending the message to the receiver.
Attribute Value
Subfield ID n-2 02
Subfield Length n-2 01
Data Representation ans-1
Attribute Value
Justification Left
Values
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. The values
are shown in this table.
Values
Values Description
1 Interregional
2 Intraregional
3 Intercountry
4 Intracountry
8 Member-to-member
spaces Customers must submit all spaces in this subfield unless specifically
directed otherwise by Mastercard®. The clearing system will then
determine the correct value and populate this subfield before
sending the message to the receiver.
Attribute Value
Subfield ID n-2 03
Subfield Length n-2 06
Data Representation ans-6
Justification Left
The Mastercard® billing and clearing codes, Account Management System (AMS) region codes,
and corresponding descriptions are listed in this table. The two-digit billing and clearing codes
are used in subfield 3, denoted with FF, TT, and RR.
Attribute Value
Subfield ID n-2 04
Subfield Length n-2 02
Data Representation ans-2
Justification Left
Attribute Value
Subfield ID n-2 05
Subfield Length n-2 06
Data Representation n-6; YYMMDD
Attribute Value
Justification Right
Attribute Value
Subfield ID n-2 06
Subfield Length n-2 02
Data Representation n-2
Justification Right
Attribute Value
Subfield ID n-2 07
Subfield Length n-2 01
Data Representation ans-1
Justification N/A
Values
This table lists the values.
Values
Value Description
Space No acceptor classification override was applied.
0 Acceptor Business Code (MCC) Override was applied.
1 AB Type “Other” Override was applied.
A AB Type “Passenger Transport: Airline” Override was applied.
B AB Type “Cruise Line/Steamship” Override was applied.
C AB Type “Cash Disbursement” Override was applied.
D AB Type “Payment Transaction” Override was applied.
F AB Type “Restaurant” Override was applied.
H AB Type “Lodging” Override was applied.
M AB Type “Mail Order/Telephone Order” Override was applied.
P AB Type “Beauty Salon” Override was applied.
R AB Type “Passenger Transport: Railway” Override was applied.
S AB Type “Supermarket” Override was applied.
T AB Type “Telephone” Override was applied.
U AB Type “Unique” Override was applied.
V AB Type “Automobile/Vehicle Rental” Override was applied.
W AB Type “Warehouse Club” Override was applied.
Z AB Type “ATM” Override was applied.
interchange rates were used in the interchange fee amount designated in PDS 0146 (Amount,
Transaction Fees).
Attribute Value
Subfield ID n-2 08
Subfield Length n-2 03
Data Representation ans-3
Justification N/A
Values
NOTE: Refer to PDS 0002 (GCMS Product Identifier) for the full value list.
Values
Attribute Value
Subfield ID n-2 09
Subfield Length n-2 01
Data Representation ans-1
Justification N/A
Values
This table lists the values.
Values
Value Description
N No corporate incentive interchange was applied.
V UK summary VAT level corporate incentive rates were applied, meaning that the
UK acquirer:
• Met all non-addendum business requirements for the specified interchange
program, and
• Did not provide addendum data required by first-level incentive interchange
conditions, but instead
• Provided the data mandated for UK VAT summary in the relevant Financial
Detail Addendum/1644 messages.
1 First-level corporate card incentive interchange was applied, meaning that the
acquirer:
• Met all non-addendum business requirements for the specified interchange
program, and
• Provided the mandated data in the relevant Financial Detail Addendum/1644
messages.
2 Second-level corporate card incentive interchange was applied, meaning that the
acquirer:
• Met all non-addendum business requirements for the specified interchange
program, and
• Did not provide addendum data required by first-level incentive interchange
conditions OR was a UK acquirer that did not provide the information needed to
qualify for the UK summary VAT Level incentive interchange, but instead
• Provided PDS 0502 (Custom Identifier) in the First Presentment/1240
message with a value that allows Mastercard® to match the First
Presentment/1240 with addendum data obtained from third-party T&E
vendors.
Attribute Value
Subfield ID n-2 10
Subfield Length n-2 01
Data Representation ans-1
Justification N/A
Values
This table lists the values
Values
Value Description
N Neither Late Presentment nor ATM Surcharge adjustment
Y Late Presentment adjustment only
2 ATM Surcharge adjustment only
3 Both Late Presentment and ATM Surcharge adjustment
Attribute Value
Subfield ID n-2 11
Subfield Length n-2 01
Attribute Value
Data Representation ans-1
Justification N/A
Attribute Value
Subfield ID n-2 12
Subfield Length n-2 01
Data Representation ans-1
Justification N/A
Values
PDS 0158, subfield 12 contains a value for account level management when unique IRDs are not
defined. Customers in the Europe Region use this subfield. Customers in the U.S. and Canada
Regions do not use subfield 12 to identify the transaction processed as account level
management.
GCMS populates PDS 0158, subfield 12 when:
• An account in the Europe region associated with the transaction is participating in Enhanced
Value where an incremental incentive is included in the transaction’s interchange amount.
• An account in the Europe region associated with the transaction is participating in Product
Graduation.
• An account in the Europe region associated with the transaction is participating in a both
Enhanced Value and Product Graduation where an incremental incentive is included in the
transaction’s interchange amount.
This subfield will be populated by GCMS as part of the qualification process for account level
management transactions.
Values
Value Description
N (default) For markets that use a rate adjustment for incentive interchange
and unique IRDs are not defined for account level management, such
as Europe, value N indicates a rate adjustment was not applied. For
markets that use unique IRDs for account level management
incentive interchange or markets that do not participate in account
level management services, value N represents the default value.
B Enhanced Value
M Product Graduation and Enhanced Value
P Product Graduation
Attribute Value
Subfield ID n-2 13
Subfield Length n-2 01
Data Representation ans-1
Justification N/A
Values
This table lists the values.
Values
Value Description
B Base
C MPP Regulated Rate 1
E The transaction qualified for the Europe Cross Border Acquiring Regulated Rate.
The clearing system adjusted the interchange fee since the original interchange fee
was greater than the maximum allowed interchange fee.
Value Description
F The transaction qualified for Europe Cross Border Acquiring Regulated Rate. The
clearing system did not adjust the interchange fee since the original interchange
fee was less than or equal to the maximum allowed interchange fee.
P MPP Regulated Rate 2
1 Base plus Fraud Adjustment
N Non-regulated
S Regulated Small Ticket Base
T Regulated Small Ticket Tier 1
Attributes
Attribute Value
Subfield ID n-2 14
Subfield Length n-2 01
Data Representation an-1
Justification N/A
Values
This table lists the values.
Values
Value Description
Y The transaction did receive the incentive interchange.
N The transaction did not receive the incentive interchange.
Attributes
Attribute Value
Subfield ID n-2 15
Subfield Length n-2 01
Data Representation an-1
Justification N/A
Values
This table lists the values.
Values
Value Description
Y Digital wallet interchange override was applied.
N Digital wallet interchange override was not applied.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
The clearing system inserts PDS 0159 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 customers or
between the customer and Mastercard when the transaction is successfully completed.
Amount, Reconciliation (DE 5) always is assigned to PDS 0159 for reconciliation.
In PDS 0146 (Amounts, Transaction Fee), each occurrence of a transaction fee (subfield 7
[Amount, Fee, Reconciliation]) is assigned to PDS 0159 for reconciliation, as indicated by the Fee
Settlement Indicator subfield associated with each fee.
Value Description
1 Regional
3 Intracurrency
Value Description
F Fixed; indicates that a fixed rate class was used to convert from
transaction currency to receiver’s payment currency.
M Market; indicates that a market rate was used to convert from base
currency to the receiver’s payment currency.
N Not applicable; no conversion occurred.
business day for the settlement service, and the reconciliation cycle is 01. The reconciliation
cycles in this table are assigned.
Value Description
01 Cycle 1
02 Cycle 2
03 Cycle 3
04 Cycle 4
05 Cycle 5
06 Cycle 6
The clearing system always determines this subfield’s data value. The clearing system inserts
reconciliation cycle into any transaction to which it assigned a settlement service level code and
settlement service ID code.
This subfield contains the same value as PDS 0158, subfield 6 (Business Cycle).
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 customers and
processors should be prepared to receive and reconcile against multiple settlement cycles.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
The clearing system inserts PDS 0160 into all First Presentment messages and subsequent
cardholder life cycle transactions with settlement impact for which the clearing system is
responsible for managing installment payment funds settlement.
A transaction with a payment option is identified by the presence of PDS 0195 (Installment
Data).
If PDS 0195, subfield 2 (Payment Option Code) is present and indicates a specific payment
option, PDS 0159 (Settlement Data), subfield 8 (Settlement Date) will contain all nines to alert
the customer to look at PDS 0160 for the settlement dates and settlement amounts.
If PDS 0195, subfield 2 contains value 61 (Installments [Twice Pay/Three or More]), and subfield
1 (Total Number of Installments) is value 2, and it is a First Presentment, PDS 0160 will contain
two sets of settlement dates as the twice pay payments of a First Presentment will be settled
in two parts.
For Japan domestic transactions, if PDS 0195, subfield 2 contains value 61, and subfield 1 is 2
in First Presentment/1240, the clearing system inserts PDS 0160 into the message. However,
the clearing system does not insert PDS 0160 into First Chargeback/1442, Arbitration
Chargeback/1442, or Second Presentment/1240 even when PDS 0195, subfield 2 contains
value 61, and subfield 1 is value 2.
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 the banking business days that the settlement service specifically identifies.
The clearing system always determines this subfield’s data value if the transaction is identified
as having a specific installment payment option in PDS 0195 (Installment Data), subfield 2
(Payment Option Code).
The settlement date is adjusted for each settlement service level and settlement service ID.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS contains one to 10 occurrences of currency conversion data. The clearing system may
provide multiple Currency Update/1644 messages to customers (each with up to 10 rates per
message) to provide information on currency conversion rates used in processing Financial
messages.
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 this example:
• 100 XYZ * (multiplied by) 0.333333333 = 33.33 USD
• 100 USD / (divided by) 0.333333333 = 300 XYZ
Value Description
B Buy rate
M Mid rate
S Sell rate
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
The transaction originator must provide this PDS. It must indicate normal, bilateral, or collection
only processing.
Values
If present, PDS 0165 cannot contain all low values or all high values.
Application note
Europe region issuers that participate in a meal voucher program must ensure that PDS 0165,
subfield 1, contains value B for any transaction the issuer will settle directly with the
participating merchant. Issuers that act as meal voucher service providers indicate their
intention to settle a transaction directly with a merchant by using the Prepaid Voucher format
of Authorization System DE 124 in the Authorization Request Response/0110 message for such
transactions. The requirements for this format are defined in the Customer Interface
Specification manual.
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.
Value Description
M Mastercard® clearing and net settlement; the clearing system should
clear and settle the transaction.
Value Description
X followed by a 25 byte Input Single Message System has settled the transaction; for the clearing
Source Reference ID system to clear the message and not settle the transaction the 25
byte Input Source Reference ID indicates a unique value to assist
with reconciliation.
NOTE: When PDS 0165 has the value X in subfield 2, position 1, the Input Source Reference IDs in
position 2 through position 26 will be used as the identifier assigned to PDS 0300 (Reconciled, File) to
create a new logical file for 1644/688 Settlement Reconciliation Notification Messages.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
For U.S. and Canada-acquired First Presentment/1240 transactions, PDS 0170 subfield 1
(Customer Service Phone Number) must be present when DE 22 (Point of Service Data Code),
subfield 5 (Cardholder Present Data) is equal to 2 (cardholder not present, mail transaction), 3
(cardholder not present, phone transaction), or 4 (cardholder not present, standing [recurring]
transaction).
Values
If present, PDS 0170 cannot contain all low values, all high values, all spaces, or all zeros.
Subfield 1 values
Acceptor Customer Service Phone Number must contain a valid value defined and formatted as
per local telecom or the ITU Telecommunication Standardization Sector (ITU-T) standards.
For U.S. region and Canada transactions, if present, Acceptor Customer Service Phone Number
must be 10 positions with the beginning three positions numeric.
For these transactions acquired in the U.S. or Canada regions, the 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.
• First Presentment/1240
• Second Presentment/1240
• First Chargeback/1442
• Arbitration Chargebacks/1442
• Retrieval Requests/1644
• Fee Collection (Retrieval Fee Billing)/1740
The first three positions must be numeric.
For U.S. and Canada-acquired First Presentment/1240 transactions, PDS 0170 subfield 1
(Customer Service Phone Number) must be present when DE 22 (Point of Service Data Code),
subfield 5 (Cardholder Present Data) is equal to 2 (cardholder not present, mail transaction), 3
(cardholder not present, phone transaction), or 4 (cardholder not present, standing [recurring]
transaction), unless the transaction is collection only or a reversal.
Subfield 2 values
Acceptor Phone Number must contain a valid value defined and formatted as per local telecom
or the ITU Telecommunication Standardization Sector (ITU-T) standards.
For U.S region and Canada transactions, if present, Acceptor Phone Number must be 10
positions with the beginning three positions numeric.
Attributes
NOTE: Subfield 2 includes binary data. Converting this data to other formats may cause data loss.
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS is optional in First Presentment/1240 messages and subsequent cardholder life cycle
transactions.
Values
If present, PDS 0171 cannot contain all low values or all high values.
Value Description
ARA Arabic
CHS Chinese (simplified)
CHT Chinese (traditional)
CYR Cyrillic
Value Description
GRK Greek
HEB Hebrew
HIR Hiragana
HAN Hangul
KAN Kanji
KAT Katakana
ROM Roman
THI Thai
VIE Vietnamese
NOTE: Subfield 2 includes binary data. Converting this data to other formats may cause data loss.
Subfield 2 (Acceptor Description Data) consists of a free-format text describing the acceptor
name or location (or both), 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.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
This PDS is optional in First Presentment/1240 messages and subsequent cardholder life cycle
transactions. If present, it must be left-justified and cannot contain all spaces.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS is conditional in First Presentment/1240 messages and subsequent cardholder life
cycle transactions. If present, it must be left-justified and cannot contain all spaces.
Values
This PDS must be present in the associated First Presentment/1240 messages submitted with
this criteria:
• DE 43 (Acceptor Name/Location), subfield 6 (Acceptor Country Code) equals USA.
• DE 3 (Processing Code), subfield 1 (Cardholder Transaction Type) equals 00 Purchase (Goods
and services) or 18 Unique.
• The transaction must be processed with a Mastercard® commercial card.
• The transaction is submitted for a U.S.-acquired Commercial Interchange Rate program.
Transactions submitted for U.S. Commercial Standard, International Commercial Standard, and
International Commercial Purchasing Standard interchange are excluded from submitting PDS
0173 in the associated First Presentment/1240 messages, unless PDS 0596 (Acceptor Tax ID),
subfield 2 (Acceptor Tax ID Provided Code) equals Y.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
This PDS is optional in First Presentment/1240 messages and subsequent cardholder life cycle
transactions. If present, it must be numeric and cannot contain all zeros.
Attributes
Justification: Left
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, PDS 0175 must be left-justified and cannot contain all spaces or all zeros.
Processing rules
The Acceptor URL Address must be present for all electronic commerce transactions and
contain a valid website address. For all other transactions, it must be provided unless a
customer service phone is provided for contact.
Program rules
Payment facilitator-enabled transaction: The sponsored merchant acceptor URL should be
provided.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
If PDS 0176 is present and valid in a First Presentment/1240 message, GCMS will forward it to
the issuer. The issuer must retain PDS 0176 and provide it in subsequent First Chargeback/1442
and Arbitration Chargeback/1442 messages. Similarly, acquirers that receive PDS 0176 in a
First Chargeback/1442 message must retain it and provide it in subsequent Second
Presentment/1240 messages. This is needed for GCMS to apply the same interchange rate to
the life cycle transaction it applied to the First Presentment/1240 transaction.
Editing rules
PDS 0176 is not a required field for IIAS transactions. It may be sent with IIAS transactions;
however, if it is sent, it will be checked for validity. If the ID is not valid, the transaction will be
rejected.
If present, PDS 0176 (Mastercard Assigned ID) must be valid and must be used only for
transactions that are authorized to use this ID. If received in First Presentments, it must be
returned in First Chargebacks, Second Presentments, and Arbitration Chargebacks.
If PDS 0057 (Transaction Category Indicator) has the value 3 (The transaction is from an
acceptor terminal that verified qualified healthcare expenses against an inventory information
approval system [IIAS] during the authorization process), the Mastercard Assigned ID is
required.
For the following interchange programs defined in the U.S. region intracountry BSA 2/010001,
GCMS will require and validate PDS 0176 if these conditions have been met:
• The acquirer has submitted PDS 0176 for the transaction
• DE 3 (Processing Code), subfield 1 is Purchase: Goods and Services (00), Unique Transaction:
Requires Unique MCC (18), or Credit: Purchase Return (20).
Interchange programs
IRD Description
05 World Merit III Tier 1
08 World Supermarket Tier 1
09 Warehouse Base
10 Merit III Tier I
11 Merit III Tier 2
12 Merit III Tier 3
13 Supermarket Tier 1
14 Supermarket Tier 2
15 Supermarket Tier 3
16 World Small Ticket Card Present
17 Warehouse Tier 2
18 Warehouse Tier 3
19 World Merit III Tier 2
30 World Merit III Tier 3
54 World Warehouse Tier 1
77 World Supermarket Tier 2
91 Warehouse Base
BP Mastercard® Prepaid Online Bill Pay
RB Enhanced Merit III Tier 1
IRD Description
RC Enhanced Merit III Tier 2
RD Enhanced Merit III Tier 3
RF Enhanced Supermarket Tier I
RG Enhanced Supermarket Tier II
RH Enhanced Supermarket Tier III
RI Enhanced Warehouse Base
RJ Enhanced Warehouse Club I
ST Small Ticket Tier 1
WM World Elite Warehouse Base
If the transaction meets this mentioned criteria, the Mastercard Assigned ID and IRD
combination is edited against the valid Mastercard Assigned ID and IRD list maintained at
Mastercard®.
For the interchange programs defined in the intracountry Business Service Arrangement
4/124001, GCMS will require and validate PDS 0176 (Mastercard Assigned ID) if these
conditions have been met:
• The acquirer has submitted PDS 0176 for the transaction.
• DE 3 (Processing Code), subfield 1 (Cardholder Transaction Type) is 00 (Purchase [Goods and
Services]), 09 (Purchase [Goods and Services] with Cash Back [only for use with Debit
Mastercard® card products]), or 20 (Credit [Purchase Return]).
• The acquirer has submitted the transaction for a tiered interchange program and the IRD is
listed in this table.
Interchange programs
IRD Description
61 Canada Intracountry Consumer Rate A
62 Canada Intracountry Consumer Rate B
63 Canada Intracountry Consumer High Spend Rate A
64 Canada Intracountry Consumer High Spend Rate B
65 Canada Intracountry Consumer Premium High Spend Rate A
66 Canada Intracountry Consumer Premium High Spend Rate B
74 Canada Intracountry Consumer Supermarket [High Volume]
75 Canada Intracountry Consumer Petroleum [High Volume]
IRD Description
84 Canada Intracountry Consumer High Spend Supermarket [High
Volume]
85 Canada Intracountry Consumer High Spend Petroleum [High
Volume]
94 Canada Intracountry Consumer Premium High Spend Supermarket
[High Volume]
95 Canada Intracountry Consumer Premium High Spend Petroleum
[High Volume]
For the interchange programs defined in the Canada intracountry BSA 4/124001, GCMS will
require and validate PDS 0176 if these conditions have been met:
• The acquirer has submitted PDS 0176 for the transaction.
• DE 3 (Processing Code), subfield 1 is Purchase: Goods and Services (00), Unique Transaction:
Requires Unique MCC (18), or Credit: Purchase Return (20).
The IRD codes are listed in this table.
Interchange programs
IRD Description
42 Supermarket Tier 1
43 Supermarket Tier 2
45 Big Box Stores Tier 1
46 Big Box Stores Tier 2
48 Petroleum Tier 1
49 Petroleum Tier 2
51 Specialty Clothing Tier 1
52 Specialty Clothing Tier 2
56 Other Tier 1
58 Other Tier 2
If the transaction meets this criteria, the Mastercard Assigned ID and IRD combination is edited
against the valid Mastercard Assigned ID and IRD list maintained at Mastercard®.
For the interchange programs defined in intracountry BSAs of Eurozone countries, GCMS will
require and validate PDS 0176 if these conditions have been met:
• The acquirer has submitted PDS 0176 for the transaction.
• For IRDs S3 and T2, DE 3 (Processing Code), subfield 1 is 00 (Purchase), 09 (Purchase with
Cash Back), or 20 (Credit).
• For IRD P3, DE 3 (Processing Code), subfield 1 is 00 (Purchase).
The IRD codes are listed in this table.
Interchange programs
IRD Description
S3 Maestro® POS Large Merchant
P3 Maestro® PayPass® Large Merchant
T2 Debit Mastercard POS Large Merchant
If the transaction meets the above criteria, the Mastercard Assigned ID and IRD combination is
edited against the valid Mastercard Assigned ID and IRD list maintained at Mastercard®.
Acquirers impact
Acquirers should note the following:
• For First Presentment/1240 non-collection messages, if the IRD submitted is a specified
U.S.-to-U.S. IRD listed above, then PDS 0176 must be present.
• For First Presentment/1240 non-collection messages, if PDS 0176 is submitted and the IRD
submitted is a U.S.-to-U.S. IRD listed above, the message will be subject to the Mastercard
Assigned ID interchange edit.
• Acquirers must be able retain PDS 0176 and provide it in any subsequent transactions.
• For all acceptors that have been issued a Mastercard Assigned ID, all submitted First
Presentment transactions should contain the Mastercard Assigned ID in PDS 0176, including
credits and reversals.
Issuers impact
Issuers should note these items:
• Mastercard® will forward PDS 0176 in First Presentment/1240 messages to the issuers.
• Issuers continue to receive the tiered interchange IRDs in PDS 0158 (Business Activity),
subfield 4 (Interchange Rate Designator) if submitted by the acquirer.
• Issuers must be able retain PDS 0176 and provide it in any subsequent Chargeback
transactions.
Values
The Mastercard Assigned Merchant ID in this PDS should always be a value assigned by
Mastercard®.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
The clearing system populates values in PDS 0177. Customer-generated messages should not
contain PDS 0177. Transactions processed by the Mastercard® network and then submitted to
the clearing system will contain PDS 0177.
Value Description
Y Qualifies as a cross-border transaction.
N Does not qualify as a cross-border transaction.
Value Description
Space Does not qualify as a cross-border transaction.
Y Transaction submitted in the local currency of the merchant.
N Transaction not submitted in the local currency of the merchant.
Attributes
NOTE: Subfield 2 includes binary data. Converting this data to other formats may cause data loss.
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS is optional in First Presentment/1240 and subsequent cardholder life cycle
transactions.
Values
If present, PDS 0178 cannot contain all low values or all high values.
Value Description
ARA Arabic
CHS Chinese (simplified)
CHT Chinese (traditional)
CYR Cyrillic
GRK Greek
HEB Hebrew
HIR Hiragana
HAN Hangul
KAN Kanji
KAT Katakana
ROM Roman
THI Thai
VIE Vietnamese
NOTE: Subfield 2 includes binary data. Converting this data to other formats may cause data loss.
Subfield 2 (Acceptor Description Data 2) consists of free-format text describing the acceptor
name or location (or both), 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.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, PDS 0179 must contain a valid value. The values are shown in this table.
Values
Value Description
1 Healthcare Long Running Transaction (LRT)
Attributes
Usage
This table shows the usage of this data element (whether it is mandatory, conditional, optional,
system-provided, or not required) in applicable messages.
Usage
For transactions qualifying for this business service arrangement, PDS 0180 must be present
for first presentment non-cash transactions.
For customers in Croatia, acquirers in Croatia must support PDS 0180 in First Presentment/
1240 messages for installment payment transactions.PDS 0180 must be present in the First
Presentment/1240 message containing Processing Code (DE 3, subfield 1), value 00 (Purchase
[Good and Services]), 09 (Purchase [Goods and Services] with Cash Back), 18 (Unique
Transaction [Requires Unique MCC]), 20 (Credit [Purchase Return]), or 28 (Payment
Transaction). Collection Only messages are excluded.For customers in Croatia, acquirers in
Croatia must support PDS 0180 in First Presentment/1240 messages for installment payment
transactions.
Values
PDS 0180 must be left-justified and cannot contain all low values, all high values, all spaces, or
all zeros.
For non-Mexico domestic transactions, if present, PDS 0180 must be a minimum length of 1
and a maximum length of 20.
For this business service arrangement, if present, PDS 0180 must be a minimum length of 13
and maximum length of 14, unless it is Collection Only.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system
provided, or not required) in applicable messages.
Usage
All of the amount subfields are based on the cardholder billing currency and exponent values
found in DE 51 (Currency Code, Cardholder Billing) and PDS 0148 (Currency Exponents).
Attributes
Attribute Value
Subfield ID n-2 01
Subfield Length n-2 02
Data Representation n-2
Justification Right
Values
NOTE: Values 20, 21, and 22 are valid for all regions. Only value 21 is valid for the Philippines.
Values
Values Description
20 Issuer-financed
21 Merchant-financed
22 Acquirer-financed
23 Co-branded Merchant Financed
24 Issuer Merchant Co-Financed
Attribute Value
Subfield ID n-2 02
Subfield Length n-2 02
Data Representation n-2
Justification Right
Attribute Value
Subfield ID n-2 03
Subfield Length n-2 05
Data Representation ns-5
Justification Right
Attribute Value
Subfield ID n-2 04
Subfield Length n-2 12
Attribute Value
Data Representation ns-12
Justification Right
Attribute Value
Subfield ID n-2 05
Subfield Length n-2 12
Data Representation ns-12
Justification Right
Attribute Value
Subfield ID n-2 06
Subfield Length n-2 05
Data Representation ns-5
Justification Right
Attribute Value
Subfield ID n-2 07
Subfield Length n-2 12
Data Representation ns-12
Justification Right
Attribute Value
Subfield ID n-2 08
Subfield Length n-2 05
Data Representation ns-5
Justification Right with leading zeros
Attributes
Attribute Value
Subfield ID n-2 09
Subfield Length n-2 01
Data Representation ans-1
Attribute Value
Justification N/A
Values
This table lists the valid values.
Values
Values Description
C Credit to Issuer and Debit to Acquirer
D Debit to Issuer and Credit to Acquirer
Attribute Value
Subfield ID n-2 10
Subfield Length n-2 12
Data Representation ns-12
Justification Right with leading zeros
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
All the amount subfields are based on the cardholder billing currency and exponent, as provided
in DE 51 (Currency Code, Cardholder Billing) and PDS 0148 (Currency Exponents).
Attributes
Values
This table lists the valid values.
Values
Values Description
02-99 The total number of installments selected by the cardholder.
Attributes
Values
This table lists the valid values.
Values
Values Description
01–99 The current installment number of the installment split transaction
Attributes
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.
Attributes
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.
Attributes
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.
Attributes
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.
Attributes
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.
Attributes
Subfield 9 (APR)
PDS 0182, subfield 9 (APR) contains the annual percentage rate (XXX.XX %) that the issuer
charges the cardholder for the installment payments. The default rate is spaces.
Attributes
Attributes
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.
Attributes
Values
This table lists the valid values.
Values
Values Description
Y Canceled Installment
N Ongoing Installment
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
NOTE: The Post-Dated Payment service and this subfield will be available to customers in Brazil on 13
June 2017.
Attributes
Justification N/A
Values
This table lists the valid values.
Values
Values Description
30 Post-Dated with Guarantee
31 Post-Dated without Guarantee
NOTE: The Post-Dated Payment service and this subfield will be available to customers in Brazil on 13
June 2017.
Attributes
NOTE: The Post-Dated Payment service and this subfield will be available to customers in Brazil on 13
June 2017.
Subfield 3 (Guarantee)
PDS 0183 (Brazil Post-Dated Transaction Data), subfield 3 indicates whether or not there is a
guarantee to be settled for the post-dated transaction.
Attributes
Values
This table lists the valid values.
Values
Values Description
Y Yes
N No
NOTE: The Post-Dated Payment service and this subfield will be available to customers in Brazil on 13
June 2017.
Attributes
If PDS 0183, subfield 1 contains value 31 (Post-Dated without Guarantee), subfield 4 must
equal 00000000.
NOTE: The Post-Dated Payment service and this subfield will be available to customers in Brazil on 13
June 2017.
Attributes
NOTE: The Post-Dated Payment service and this subfield will be available to customers in Brazil on 13
June 2017.
Attributes
NOTE: The Post-Dated Payment service and this subfield will be available to customers in Brazil on 13
June 2017.
Attributes
NOTE: The Post-Dated Payment service and this subfield will be available to customers in Brazil on 13
June 2017.
Attributes
NOTE: The Post-Dated Payment service and this subfield will be available to customers in Brazil on 13
June 2017.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If PDS 0184 (Directory Server Transaction ID) is present, it should contain values as in this
example. The Directory Server Transaction ID is a unique ID.
Example: f38e6948-5388-41a6-bca4-b49723c19437
Application notes
This is a conditional field and must be provided by the acquirers part of the First Presentment/
1240 messages if they are participating and have previously authenticated using the
Mastercard® e-commerce/Identity Check program. This field will not be edited to ensure that
the Directory Server Transaction ID was provided on the transaction. If provided by the acquirer
or processor, it must meet the specifications defined.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
The Accountholder Authentication Value (AAV) is transaction specific. The AAV is unique to each
transaction, but will start with a leading indicator as defined in this table.
Values
NOTE: Values i, l, m, and n are reserved for future use. Refer to SPA2 AAV for Mastercard® e-commerce/
Identity Check for more details on Accountholder Authentication Value changes.
Application notes
This is a conditional field and must be provided by the acquirers part of the First Presentment/
1240 messages if they are participating and have previously authenticated using the
Mastercard® e-commerce/Identity Check program. This field will not be edited to ensure that
the AAV Value was provided on the transaction. If provided by the acquirer or processor, it must
meet the specifications defined.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If PDS 0186 (Program Protocol) is present, customers indicate the correct Program Protocol by
sending one of these values:
Value Description
1 EMV 3-D Secure Version 2.1
2 EMV 3-D Secure Version 2.2
3 EMV 3-D Secure Version 2.3
4 EMV 3-D Secure Version 2.4
5 EMV 3-D Secure Version 2.5
6 EMV 3-D Secure Version 2.6
Value Description
7 EMV 3-D Secure Version 2.7
8 EMV 3-D Secure Version 2.8
9 EMV 3-D Secure Version 2.9
Application notes
This is a conditional field and must be provided by the acquirers part of the First Presentment/
1240 messages if they are participating and have previously authenticated using the
Mastercard® e-commerce/Identity Check program. This field will not be edited to ensure that
the Program Protocol was provided on the transaction. If provided by the acquirer or processor,
it must meet the specifications defined.
Attributes
Usage
This table shows the usage of this data element (whether it is mandatory, conditional, optional,
system-provided, or not required) in applicable messages.
Values
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, PDS 0189 cannot contain all low values or all high values.
Subfields
Value Description
1 Card-activated phone transactions (U.S. and Canada call detail
format)
2 Card-activated phone transactions (non-U.S. and non-Canada
format)
NOTE: These formats 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)
Attributes
27 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.
28 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. Refer to the Quick Reference Booklet for valid state and
country codes.
Justification: Left
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable 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 also may be used when the
agreement is between the acceptor and the clearing system, such as in certain promotional
discounts.
Values
Acceptors and issuers establish Partner ID Codes. If present, PDS 0190 cannot contain all low
values, all high values, all zeros, or all spaces.
Attributes
Subfields: None
Justification: N/A
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Originators optionally may provide this PDS. If this information is not present, the clearing
system provides this PDS in customer-submitted messages. The information assists the
receiving customer in anticipating the presence or absence of various IPM data elements and
PDSs in an IPM message.
Values
The PDS 0191 values are listed in this table.
Values
Value Description
0 Clearing system received original message in Mexico Domestic
Format
2 Clearing system received message in the IPM format.
6 Clearing system received message in Japan Domestic Format
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Values
The value associated with PDS 0192 is MCW, Mastercard Worldwide.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system
provided, or not required) in applicable messages.
Usage
Values
The PDS 0194 values are listed in this table.
Value Description
1 Issuer domain
2 Acquirer domain
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system
provided, or not required) in applicable messages.
Usage
Attributes
When PDS 0195 is present, subfield 1 is required for transactions submitted for Japan
Intracountry BSA 4/392001:
• Subfield must be numeric.
• Subfield must contain the three position value that identifies the total number of
installments.
When PDS 0195, Subfield 2 (Payment Option Code) Contains value 61, subfield 1 must contain
the number of installments (a value between 002 and 999). If PDS 0195, subfield 2 contains
values other than 31, 34, or 61, subfield 1 should be zero-filled.
If PDS 0195, subfield 2 contains 61 and the number of installments is 2, the transaction will be
settled following the Twice Pay method:
• 50 percent of the transaction amount will be settled following normal settlement process.
• 50 percent of the transaction amount will be settled following a delay of 30 days from the
clearing date.
The actual settlement date will be adjusted following the settlement calendar of selected
settlement service.
Attributes
When PDS 0195 is present, subfield 2 is required for transactions submitted for Japan
Intracountry BSA 4/392001.
Values
This table lists the valid values.
Values
Values Description
10 Single Payment
21 Bonus Pay
31 Installment Payment with Bonus Pay Simplified
Values Description
34 Installment Payment with Bonus Pay Detailed
61 Installments (Twice Pay/Three or More)
80 Revolving
Attributes
This subfield is not applicable for Japan. For transactions submitted for Japan Intracountry BSA
4/392001, subfield 3 should be populated with zeros.
As an example, acquirers submitting multiple installment transactions indicate that this is the
first of three installment transactions if subfield 1 (Total Number of Installments) contains the
value 003 and subfield 3 contains the value 001.
Attributes
For transactions submitted for Japan Intracountry BSA 4/392001, subfield 4 must be provided
when subfield 2 (Payment Option Code) contains value 21 (Bonus Pay). This subfield identifies
whether a transaction must be settled utilizing the delayed settlement method.
Values
This table lists the valid values.
Values
Values Description
0 Settlement will be delayed.
If the clearing date is 21 July to 20 December, then the settlement
date will be 20 December.
If the clearing date is 21 December to 20 July, then the settlement
date will be 20 July.
1 No settlement delay
Attributes
For transactions submitted for Japan Intracountry BSA 4/392001, subfield 5 must be provided
when subfield 2 (Payment Option Code) is value 34 (Installment Payment with Bonus Pay
Detailed). The combination of a code in subfield 5 and a value in subfield 6 (Number of Bonus
Payments Per Year) identifies the bonus payment month(s). For specific combination details,
refer to the tables included under subfield 6.
NOTE: When the value <space> is used, it indicates the amount in subfield 7 (Bonus Amount) can be a
zero amount even when subfield 2 is value 34 (Installment Payment with Bonus Pay Detailed). The
value <space> does not change the presence rule for other subfields.
Values
This table lists the valid values.
Values
Values Description
1 January
Values Description
2 February
3 March
4 April
5 May
6 June
7 July
8 August
9 September
A October
B November
C December
<space> Undefined
Attributes
For transactions submitted for Japan Intracountry BSA 4/392001, subfield 6 must be provided
when subfield 2 (Payment Option Code) contains value 34 (Installment Payment with Bonus
Pay Detailed). The combinations of a code in subfield 5 (Bonus Month Code) and a value in
subfield 6 identifies the bonus payment month(s).
Values
This table lists the valid values.
Values
Values Description
1 Number of Bonus Payments is once per year
Values Description
2 Number of Bonus Payments is twice per year
Indicates the bonus month(s) when once per year bonus payments will be settled.
Indicates the bonus month(s) when twice per year bonus payments will be settled.
Attributes
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 bonus amount of USD
4500.29 is expressed as 000000450029.
For transactions submitted for Japan Intracountry BSA 4/392001, subfield 7 must be provided
when subfield 2 (Payment Option Code) is value 34 (Installment Payment with Bonus Pay
Detailed). When provided, the amount must be greater than zero except when subfield 5 (Bonus
Month Code) contains <space>. For example, a bonus amount of JPY 45000 is expressed as
000000045000.
Attributes
For transactions submitted for Japan Intracountry BSA 4/392001, subfield 8 is a four-digit
subfield in the format YYMM that identifies the first month of bonus payment. This subfield
must be provided when subfield 2 (Payment Option Code) contains value 34 (Installment
Payment with Bonus Pay Detailed).
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system
provided, or not required) in applicable messages.
Usage
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS can be used to present tax amounts, a tax percentage, and a tax base amount for
intracountry transactions in various markets. The subfield names are very general in nature, to
allow different usage definitions for different countries.
Values
If present, each of the subfields 1, 2, 4, and 5 within PDS 0197 must be right-justified with
leading zeros.
Attributes
Usage
This table shows the usage of this data element (whether it is mandatory, conditional, optional,
system-provided, or not required) in applicable messages.
Usage
Values
NOTE: As removable secure elements may be moved from a mobile phone to a tablet or e-book by the
consumer, values 01, 08, 10, and 12 represent the initial intended use of this secure element by the
issuer. There is no requirement to change these four values after initial personalization has taken place.
Values
Value Description
00 Card
01 Mobile Phone or Smartphone with Mobile Network Operator (MNO)
controlled removable secure element (SIM or UICC) personalized for
use with a Mobile Phone or Smartphone29
29 As a removable secure element (SE) may be moved from a mobile phone to a tablet or e-book by the consumer this
value represents the initial intended use of this SE only.
Value Description
02 Key Fob
03 Watch using a contactless chip or a fixed (non-removable) secure
element not controlled by the MNO
04 Mobile Tag
05 Wristband
06 Mobile Phone Case or Sleeve
07 Mobile phone or smartphone with a fixed (non-removable) secure
element controlled by the MNO, for example, code division multiple
access (CDMA)
08 Mobile Phone or Smartphone with removable secure element not
controlled by the MNO, for example, SD Card personalized for use
with a Mobile Phone or Smartphone30
09 Mobile phone or smartphone with a fixed (non-removable) secure
element not controlled by the MNO
10 Tablet or e-Reader with an MNO-controlled removable secure
element (SIM or UICC) personalized for used with a Tablet or
Reader31
11 Tablet or e-book with a fixed (non-removable) secure element
controlled by the MNO
12 Removable secure element not controlled by the MNO, for example,
memory card personalized for use with a tablet or e-book
13 Tablet or e-book with fixed (non-removable) secure element not
controlled by the MNO
14 Mobile Phone or Smartphone with a payment application running in
a host processor
15 Tablet or e-Reader with a payment application running in a host
processor
16 Mobile Phone or Smartphone with a payment application running in
the TEE of a host processor
17 Tablet or E-Book with a payment application running in the TEE of a
host processor
18 Watch with a payment application running in the TEE of a host
processor
19 Watch with a payment application running in a host processor
30 As a removable secure element (SE) may be moved from a mobile phone to a tablet or e-book by the consumer this
value represents the initial intended use of this SE only.
31 As a removable secure element (SE) may be moved from a mobile phone to a tablet or e-book by the consumer this
value represents the initial intended use of this SE only.
Value Description
20 Card
21 Phone
22 Tablet/e-reader
23 Watch/Wristband
24 Sticker
25 PC
26 Device Peripheral
27 Tag
28 Jewelry
29 Fashion Accessory
30 Garment
31 Domestic Appliance
32 Vehicle
33 Media/Gaming Device
34–99 Reserved for Future Use
Attributes
This table shows the usage of this data element (whether it is mandatory, conditional, optional,
system-provided, or not required) in applicable messages.
Usage
Values
If present, PDS 0199 must contain the information that can be included on the cardholder
statement as a result of a domestic funding transaction at an ATM initiated by a cardholder to
pay a bill. Specific formatting of PDS 0199 can be found in the Domestic Processing Guide for
the country provided by the Mastercard® regional office. Specific formatting of PDS 0199 is
defined for each country where the funding transaction at an ATM is implemented. Contact
your regional office for information regarding the implementation of the funding transaction at
the ATM for your local market.
Attributes
PDS 0200 is populated and provided to the acquirer starting with the second fraud-related
chargeback for the account, and continues with each successive fraud-related chargeback on
the account.
When a first or second chargeback is received from the issuers with the fraud-related
chargeback reason codes (4837, 4840, 4849, 4863, 4870, and 4871), Fraud Notification Service
(FNS) Blocking is applied on each chargeback that exceeds the FNS criteria (FNS Date and FNS
counter) set in the system. Chargeback is blocked if either or both of these condition matches:
• The original transaction settlement date is greater than FNS Date from FNS Service reply
(IPM Clearing Format error number error code 2801).
• The FNS Service reply for FNS Count is greater than FNS counter criteria (of 35 counts) in
aggregate for the aforementioned qualifying, fraud-related chargeback reason codes (IPM
Clearing Format error number error code 2802).
Accepting or rejecting a reversal chargeback depends on the corresponding original chargeback
status. If the original chargeback was accepted, then the corresponding reversal chargeback will
also be accepted without validating FNS counter and FNS date criteria. If the original
chargeback was rejected, then corresponding reversal chargeback will also be rejected without
validating FNS counter and FNS date criteria. The FNS date and counter is updated for all
transactions regardless of the reject/accept due to the edit.
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, PDS 0200, subfield 1 (Fraud Notification Service Date) contains the date of the
second fraud chargeback on the account.
If present, PDS 0200, subfield 1 (Fraud Notification Service Date) must contain a valid date in
the YYMMDD format.
Application notes
The FNS reply for Fraud Notification Service Chargeback Counter is greater than the Fraud
Notification Service Chargeback Counter limit of 35 in aggregate for the previously mentioned,
fraud-related chargeback reason codes will result in error number 2802 (INELIGIBLE
CHARGEBACK REJECT REASON CODES ‘FNS COUNTER EXCEEDED').
Attributes
account number is captured for a given transaction, the length of PDS 0202 must be 16, and
exactly 16 digits must be provided beginning in position 1 of PDs 0202.
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
PDS 0202 contains the same structure as DE 2 (Primary Account Number [PAN]), but the value
can be alphanumeric.
For more information on the usage and values of PDS 0202, see DE 2.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
PDS 0204 contains the same structure as DE 4 (Amount, Transaction), but the value can be
alphanumeric.
For more information on the usage and values of PDS 0204, see DE 4 (Amount, Transaction).
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Value Description
01–25 Local domestic reason codes.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Attributes
Attributes
Usage
Application notes
For MasterPass®, Mastercard® passes the Wallet Identifier as sent in by the acquirer or issuer.
The submission of PDS 0207 is always required on MasterPass® Wallet transactions or other
Staged/Pass-through wallets. This data is received from the MasterPass® Wallet and can vary
from transaction to transaction.
Usage
Application notes
For MDES, Mastercard® inserts the Wallet Identifier that is in the system, when available.
The submission of PDS 0207 is always required on MasterPass® Wallet transactions or other
Staged/Pass-through wallets. This data is received from the MasterPass® Wallet and can vary
from transaction to transaction.
Values
Value Description
101 Wallet Remote
102 Wallet Remote NFC Payment
PDS 0207 cannot contain all zeros, spaces, or special characters. PDS 0207 has no specific
format and may contain any combination of numeric or alphanumeric values.
Mastercard® does not publish the new wallet ID values. The acquirer and processor systems
should pass whatever value is provided by MasterPass® Wallet unaltered in the transaction
record.
Values
Value Description
103 Apple Pay
216 Android Pay
217 Samsung Pay
327 Merchant tokenization program
PDS 0207 cannot contain all zeros, spaces, or special characters. PDS 0207 has no specific
format and may contain any combination of numeric or alphanumeric values.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Attributes
Application notes
This value should be provided by the acquirer when a registered payment facilitator is involved in
a transaction and should be right justified with leading zeros. For example, if the company ID is
123456, PDS 0208, subfield 1 should be 00000123456.
PDS 0208 (Additional Merchant Data), subfield 1 must match DE 48 (Additional Data, Private
Use), subelement 37 (Additional Merchant Data), subfield 1 (Payment Facilitator ID) in
authorization.
Subfield 1 (Payment Facilitator ID) must be alphanumeric and must not contain all zeros or all
spaces.
Attributes
Processing rules
The sponsored merchant ID must be present for all payment facilitator-acquired transactions
and must uniquely identify each sponsored merchant and its location.
Application notes
This value, which is assigned by the payment facilitator or their acquirer, should be provided by
the acquirer whenever the payment facilitator ID is provided in PDS 0208 (Additional Merchant
Data), subfield 1 (Payment Facilitator ID).
Subfield 2 (Sponsored Merchant ID) must be alphanumeric and must not contain all zeros or all
spaces.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Values
The independent sales organization ID must always be a value assigned by Mastercard® and is
the same value in both the authorization and clearing platforms. This ID is the company ID that
is assigned during the time of registration via Mastercard Connect® of a service provider as an
independent sales organization.
This value must be provided by the acquirer when a registered independent sales organization is
involved in a transaction and should be right justified with leading zeros. For example, if the
company ID is 123456, PDS 0209 should be 00000123456.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system
provided, or not required) in applicable messages.
Usage
Acquirers should not populate the subfields in this PDS with values other than those defined by
Mastercard®. The values should be populated only on transit activity for transactions that have
transit-related MCCs and not on transactions with any other MCC.
NOTE: The values 03 and 04 defined for subfield 1 (Transit Transaction Type Indicator) must only be
populated by acquirers working with Transit agencies and supporting Mastercard aggregated transit
transaction models.
Issuers should not reject or limit processing of these transactions solely because acquirers
populate the subfields in this PDS with values that are not defined by Mastercard®.
NOTE: The value of 07 (Debt Recovery) must not be used where the original transit transaction was 01
(Pre-Funded) or 02 (Real-Time Authorized). The value of 07 should only be used where the original
transit transactions was 03 (Post-Authorized Aggregated), or 04 (Authorized Aggregated Split
Clearing) or 05 (Other) where the transaction model implements a delayed authorization.
Value Description
01 Pre-Funded
02 Real-time Authorized
03 Post-Authorized Aggregated
04 Authorized Aggregated Split Clearing
05 Other
06 Post-authorized Aggregated Maestro®
07 Debt Recovery
08 First Ride Risk Claim
09–99 Reserved for Future Use
Value Description
00 Unknown
01 Urban Bus
02 Interurban Bus
03 Light Train Mass Transit (Underground Metro, LTR)
04 Train
05 Commuter Train
06 Water Borne Vehicle
07 Toll
08 Parking
09 Taxi
10 High Speed Train
11 Rural Bus
12 Express Commuter Train
13 Para Transit
14 Self Drive Vehicle
15 Coach
16 Locomotive
17 Powered Motor Vehicle
18 Trailer
19 Regional Train
20 Inter City
21 Funicular Train
22 Cable Car
23–99 Reserved for Future Use
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system
provided, or not required) in applicable messages.
Usage
Acquirers should not populate the subfields in this PDS with values other than those defined by
Mastercard®. These values should be populated only on card-present POS transactions acquired
in India.
Values
Values Description
1 Not Certified
2 Certified
Values
Value Description
1 Not Certified
2 Certified
Attributes
If present, PDS 0213 must contain a valid numeric ISO country code. When territories have a defined
country code in Chapter 2 of the Quick Reference Booklet, that country code must be used.
For example, embassies are physically located in countries that are not their “home country” (that is, the
embassy of Mexico may be physically located in Singapore; however, the “home country” is Mexico).
Requirements
PDS 0213 must contain the location information of the government entity, not the location of the
merchant.
When PDS 0213 is provided, this field must contain a valid three byte ISO numeric country code in First
Presentment/1240 messages.
The following table shows the usage of this PDS (whether it is mandatory, conditional, optional,
system provided, or not required) in applicable messages.
Usage
Attributes
Usage
Usage
Attributes
Attribute Value
Subfield ID n-2 01
Subfield length n-2 13
Data representation ans-13
Justification Left with trailing spaces
Values
Service Location City Name must contain the name of the city, town, or village as defined by
country postal standards.
Processing rules
Service Location City Name must be present for all transactions when different from the
location identified in the Acceptor City Name.
For the U.S. region, this field must match the U.S. Postal Service list of acceptable cities and
spellings.
Attributes
Attribute Value
Subfield ID n-2 02
Subfield length n-2 03
Data representation ans-3
Justification Left with trailing spaces
Values
Service Location Country Subdivision Code must contain a valid code as defined in Chapter 2 of
the Quick Reference Booklet.
Processing rules
The Service Location Subdivision Code must be present for all transactions when different from
the location identified in the Acceptor Subdivision Code.
Attributes
Attribute Value
Subfield ID n-2 03
Subfield length n-2 03
Data representation ans-3
Justification Left
Values
Acceptor Country Code must contain a valid three-character alphabetic code as defined in
Chapter 2 of the Quick Reference Booklet. When territories have a defined country code in the
Quick Reference Booklet, that country code must be used.
Processing rules
The Service Location Country Code must be present for all transactions when different from the
location identified in the Acceptor Country Code.
Attributes
Attribute Value
Subfield ID n-2 04
Subfield length n-2 10
Data representation ans-10
Justification Left with trailing spaces
Values
Service Location Postal Code must contain a valid code as defined by country postal standards.
Processing rules
The Service Location Postal Code must be present for all transactions when different from the
Acceptor Postal Code and contain a valid code for countries that utilize postal codes. This
information must be populated and formatted as defined by country postal standards.
Attributes
Subfields: 2
Justification: N/A
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Attributes
Justificati
Number Positions Name Attribute on
1 1-2 CIT/MIT Category an-2 Right
2 3-4 CIT/MIT Sub-category Code n-2 Right
Subfield 1
Subfield 1 (CIT/MIT Category) contains the CIT and MIT categories.
Values
Values Description
C1, M1, M2 CIT and MIT categories
Subfield 2
Subfield 2 (CIT/MIT Sub-category) contains the CIT and MIT sub-categories.
Values
Values Description
00 to 99 CIT and MIT sub-categories
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Attributes
Application notes
This field is required when purchase, purchase with cash back, and refund transactions are
submitted by acquirers for merchants in Chile and Paraguay.
Usage
This table shows the usage of this data element (whether it is mandatory, conditional, optional,
system-provided, or not required) in applicable messages.
Usage
For transactions qualifying for the business service arrangement listed in this table, PDS 0221
must be present for first presentment purchase transactions.
PDS 0221 must be present in the First Presentment/1240 message containing Processing Code
(DE 3, subfield 1), value 00 (Purchase [Good and Services]), 09 (Purchase [Goods and Services]
with Cash Back), 18 (Unique Transaction [Requires Unique MCC]), 20 (Credit [Purchase
Return]).
If present, will vary in length from 8 or 11 characters based on the registered tax regime.
PDS 0221 must be numeric and right justified and must not contain all spaces or all zeros.
For cross-border, non-domestic transactions, PDS 0221 must not be present. If present, the
Global Clearing Management System (GCMS) will remove this PDS before sending the message
to the issuers.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This data is used to associate a clearing message with the corresponding dispute-resolution-
related image file that was routed through the Mexico domestic image interchange system and
available for review in the Mastercard® domestic dispute resolution system.
Attributes Value
Subfield ID: n-2 01
Subfield Length: n-3 004
Data Representation: ans-4
Data Field: Fixed length, 4 positions
Justification: Left
A static value of MXDS (Mexico Domestic Switching) in uppercase characters present in this
field indicates the PDS content applies specifically to Mexico-domestic dispute resolution
processing.
Subfield 2 (Unique Image Number (Single Issuer Folio Field in CATB Format))
PDS 0222 (Mexico Domestic Dispute Resolution Documentation Image-Related Data), subfield
2 (Unique Image Number [Single Issuer Folio Field in CATB Format]) contains the unique image
number assigned to the image by the domestic network participant that created the image file.
Subfield 2 (Unique Image Number (Single Issuer Folio Field in CATB Format))
Attributes Value
Subfield ID: n-2 02
Subfield Length: n-3 013
Data Representation: ans-013
Data Field: Fixed length, 13 positions
Justification: Left
Subfield 2 values
Value Description
pos 1-3 Institution ID number (001 – 999; identifies a specific Mexican
network participant)
pos 4 Institution Type (A [Acquirer] or E [Issuer])
Value Description
pos 5-8 Julian Date (1 position year + Julian day 001-366, for example 17
Jan 2025 = 5017)
pos 9-13 Consecutive Sequence Number (00000 – 99999; incremental value
that uniquely identifies each image record)
Attributes Value
Subfield ID: n-2 04
Subfield Length: n-3 032
Data Representation: ans-32
Data Field: Fixed length, 32 positions
Justification: Left
The hash value is calculated via 128bit MD5 hashing algorithm which generates a 32-byte
character string. For example: “d41d8cd98f00b204e9800998ecf8427e”.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
PDS 0225 contains the same structure as DE 25 (Message Reason Code).
For more information on the usage and values of PDS 0225, see DE 25 (Message Reason Code).
Attributes
Subfields: None
Justification: N/A
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
Data values are listed in this table.
Values
Value Description
1 Hard copy original document
2 Copy or image (photocopy, microfilm, fax) of original document
4 Substitute draft
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable 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 and in Retrieval Request Acknowledgment/1644.
Values
Data values are listed in this table.
Values
Value Description
1 Hard copy original document
Attributes
Usage
Refer to the usage table, which notes if this data element is mandatory, conditional, optional, or
system provided in applicable messages.
Attributes
Subfields: None
Justification: Left
Usage
This table shows the usage of this PDS (whether it is mandatory, 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 customer’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.
Attributes
NOTE: If the clearing system cannot locate history for the transaction, or more than one occurrence of
history is detected, this information is not provided in the message.
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
The clearing system provides this PDS using information from the MasterCom system.
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.
Attributes
Attributes
Values
Values 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 qualified limit
transaction for which documentation was not available.
D Retrieval request was fulfilled.
Values Description
E Retrieval request was not fulfilled; required or requested
documentation is not available.
F Inventory Information Approval System (IIAS) information cannot be
provided because the merchant is exempt from using an IIAS.
G The retrieval information provided was not complete or was
inaccurate.
H The retrieval request has been fulfilled.
Attributes
Attributes
Values
This table lists the values.
Values
Values 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.
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.
Attributes
Attributes
Values
This table lists the valid values.
Values
Values Description
1 Reject for cardholder number
2 Reject for transaction date
3 Reject for transaction amount
4 Reject for expiration date
5 Reject for acceptor name
6 Reject for incorrect documentation
7 Reject for other reason
8–10 Reserved for future use
Attributes
Values
This table lists the valid values.
Values
Values Description
A Image Review ruled in favor of the acquirer.
I Image Review ruled in favor of the issuer.
Attributes
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
NOTE: If the clearing system cannot locate history for the transaction, this information is not provided
in the message.
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
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 customers provided CSD via the MasterCom system 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, PDS 0244 contains only subfield 1, with a corresponding length of 6.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
The MasterCom system provides this PDS in Arbitration Chargeback messages within the
MasterCom notification files. It indicates whether customers provided CSD via the MasterCom
system in the appropriate time frames.
Values
This PDS contains a date in the format YYMMDD.
Attributes
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
Attributes
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
Attributes
Usage
PDS 0248 accompanies PDS 0243 (MasterCom Retrieval Response Data), subfield 7
(MasterCom Image Review Decision) and subfield 8 (MasterCom Image Review Date).
Usage
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
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 present only in notification files generated by MasterCom and in MasterCom Image
Interface data headers.
Values
This PDS must contain two seven-digit MasterCom Endpoints: sender and receiver, respectively.
Subfield 1 (MasterCom Sender Endpoint Number) is a number that identifies the endpoint that
acts as the sender of a MasterCom transaction (for both chargebacks and retrievals).
Subfield 2 (MasterCom Receiver Endpoint Number) identifies the endpoint that acts as the
receiver of the same transaction.
Attributes
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
The values are listed in this table.
Values
Value Description
2 Image (scanned or faxed) of original document
4 Substitute draft
Attributes
Usage
Images used by the MasterCom system are Group 3/Group 4 Tagged Image File Format (TIFF)
files, and they may bear multiple pages of images within a single TIFF file. The customers
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 customer within the image interface fulfillment files that
are delivered to the customer’s imaging system.
Values
If no image is present, this PDS does appear in the message. If an image is present, all four of
these fields are required to have values.
Attributes
Usage
NOTE: This element is available in MasterCom image interface files, not IPM clearing files.
Usage
Attributes
Usage
NOTE: This element is available in MasterCom image interface files, not IPM Clearing files.
Usage
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
Customers processing retrieval or CSD transactions of brands other than Mastercard® in the
MasterCom system can supply their own codes.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable 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 because of an ICA number 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.
Values
If present, PDS 0260 cannot contain all low values or all high values.
Value Description
Y Conversion exclusion; exempts all chargeback cycles from timeliness,
cycle appropriateness, retrieval, and documentation history edits
because a recent ICA number or BIN transfer caused an on-us or
intraprocessor transaction to become an intercustomer transaction;
conversion is validated against clearing system files; exemptions are
permitted for 60 days after the conversion occurs.
B0–B9 or BA–BZ Special conditions exclusion (chargeback and retrieval history);
exempts chargebacks from timeliness, cycle appropriateness,
retrieval history, and documentation history edits when extenuating
circumstances exist; the exclusion request code must match the
exemption code Mastercard 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; Mastercard 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 PDS 0165
(Settlement Indicator) contains a B; or if subfield 1 of PDS 0165
(Settlement Indicator) contains a C and a customer has not chosen
to have Mastercard perform these edits on collection-only
transactions.
Value Description
X, Y , or Z Conversion exclusion; exclusion granted because a recent ICA or BIN
transfer caused an On-Us or intraprocessor transaction to become
an intercustomer transaction. These are the value descriptions.
• X = recent issuer conversion
• Y = recent acquirer conversion
• Z = recent issuer and acquirer conversion
Value Description
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 PDS 0165 (Settlement
Indicator) contains a B; or if subfield 1 of PDS 0165 contains a C and
a customer has not chosen to have Mastercard® perform these edits
on collection-only transactions.
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.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, PDS 0261 must be numeric and cannot contain all zeros.
If a First Presentment rejects because the risk parameter limits defined by Mastercard have
been exceeded, and no matching authorization is 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.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
The data values are listed in this table.
Values
Value Description
0 Supporting documentation is not required.
1 Supporting documentation will follow.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS provides in Retrieval Fulfillment (presented as a Fee Collection) messages the reason
for request in DE 25 (Message Reason Code) of a related Retrieval Request/1644.
Values
The data values are listed in this table.
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
Value Description
6323 Cardholder needs information for personal records.
6341 Fraud investigation
6342 Potential chargeback or compliance documentation is required.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
This PDS provides information from the First Presentment/1240 or Fee Collection (Customer-
generated)/1740.
This PDS optionally may 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 (Customer-generated)/1740.
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.
If present, PDS 0265 cannot contain all low values or all high values.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
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 optionally may provide this PDS in Fee Collection Resubmission/1740
and Fee Collection Arbitration Return/1740 messages to supply information from the Fee
Collection Return/1740.
Values
If present, PDS 0266 cannot contain all low values or all high values.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
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.
Values
If present, PDS 0267 cannot contain all low values or all high values.
The clearing system provides subfield 2 with a valid date when used in Arbitration Chargeback/
1442 messages.
The transaction originator optionally may provide subfield 2 in Fee Collection Arbitration
Return/1740 messages.
The subfield 2 format is YYMMDD.
GCMS does not edit this subfield.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable 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 DE 49 (Currency Code, Transaction) of the First Presentment/1240.
For example, assume an acquirer submits a First Presentment/1240 for 200 Canadian dollars,
which represents two days of lodging at 100 Canadian dollars per day. Assume also that the
cardholder disputes one day of 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 DE 4 (Amount, Transaction).
Related PDSs
Whenever PDS 0268 is included in a message, PDS 0148 (Currency Exponents) must also be
included to identify the currency exponent of subfield 2.
Attributes
Attribute Value
Data representation ans…91; TAGLLLVAR
Tag field 0270
Length field 3 positions, value = 001–091
Data field Variable length, 32-91 positions
Subfields 6
Justification See subfield details.
Usage
C (conditional) indicates the field only applies to EFI program transactions.
Attributes
Attribute Value
Subfield ID n-2 01
Subfield length n-2 01
Data representation a-1
Justification N/A
Values
Value Description
N Negotiated rates were applied to the transaction
D Market-specific rates were applied to the
transaction
Attributes
Attribute Value
Subfield ID n-2 02
Subfield length n-2 06
Data representation ans-6
Justification Right justified with leading zeros,
when numeric
Values
Interchange Percentage will be populated with spaces when interchange percentage is not
provided in the negotiated rates or when market-specific interchange percentage was not
applied to the transaction. When an interchange percentage is provided, it will be represented
as n(3) v n(3). For example, an Interchange Percentage of 1.234% is represented with PDS
0270 subfield 2 value 001234.
Attributes
Attribute Value
Subfield ID n-2 03
Subfield length n-2 12
Data representation ans-12
Justification Right justified with leading zeros,
when numeric
Values
Unit fee amount will be populated with spaces when unit fee amount is not provided in the
negotiated rates or when market-specific unit fee amount was not applied to the transaction.
Attributes
Attribute Value
Subfield ID n-2 04
Subfield length n-2 12
Data representation ans-12
Justification Right justified with leading zeros,
when numeric
Values
Flat interchange amount will be populated with spaces when flat interchange amount is not
provided in the negotiated rates or when market-specific flat interchange amount was not
applied to the transaction.
Attributes
Attribute Value
Subfield ID n-2 05
Subfield length n-2 01
Data representation ans-1
Justification N/A
Values
Value Description
A Acquirer Pays interchange
I Issuer Pays interchange
Space Not provided within the Authorization message
Attributes
Attribute Value
Subfield ID n-2 06
Subfield length n-2 00-59
Data representation ans...59
Justification N/A
Values
Supplemental Interchange Data will only be populated when Supplemental Interchange Data is
provided with the negotiated rates on the Authorization message.
Attributes
Usage
The following table shows the usage of this PDS (whether it is mandatory, conditional, optional,
system-provided, or not required) in applicable messages.
Application notes
The following subfields will be populated when applicable to the ALM program and service
indicated within Subfield 1 (ALM Service Code). Subfields that are not applicable will be ’XXX’
filled. The absence of PDS 0275 for opt-in customers means the PAN account range does not
participate in ALM.
• Subfield 2 ALM Product Graduation Plus or Registered Product Code
• Subfield 3 ALM Product Class
• Subfield 4 ALM Rate Type
• Subfield 5 ALM Data Source
The following IPM DE 24 Function Codes apply:
• MTI 1240 Presentment: 200 First Presentment, 205 Second Presentment (Full), 282 Second
Presentment (Partial)
• MTI 1442 Chargeback: 450 First Chargeback (Full), and 453 First Chargeback (Partial)
Refer to the Account Level Management User Manual for additional information.
populated in the applicable authorization messages to ensure ALM processing is applied during
transaction processing for the PAN.
When the ALM Service Code is present with one of the following, ALM processing was not
applied with Clearing.
• 99726 = ALM Service not processed in Clearing
– When the Clearing System cannot complete ALM processing for a specific transaction
• 99826 or 99926 = ALM Service Unavailable
– When the Clearing System can’t connect to the Account Level Management Platform for
PAN registration validation, the customer will receive an ALM Service Unavailable service
code
• 00126 = PAN not registered for ALM, but Issuers Account Range participates, transaction
will process business as usual
– When the Issuers Account Range participates in Account Level Management, identified as
having at least one PAN actively registered in ALM for the Account Range of the PAN
within the authorization message, but the PAN is not actively registered in ALM
All other values provided will represent an individual ALM Service or ALM Service Combinations
based on the PANs active registration
Mastercard reserves the right to add new valid values for ALM Service Code at any time and
customers must be able to accept, and process any valid values. In the event new valid values
are added, refer to the Account Level Management Manual.
Values
Values
ALM
Graduate
d or
Registere
d Product
Code:
Card
Program
Identifier:
Valid Card
Values Program
List Description Country of Issuance
Moldov Thailan
Australia Belarus Brazil Canada a d Ukraine US
ACS DIGITAL X
DEBIT
BPL Mastercard® X
Business
Credit Plus
DBK *Digital X
Mastercard
Black
DCG *Digital Gold X
Mastercard
Card
DCS *Digital X
Standard
Mastercard
Card
DPL *Digital X
Platinum
Mastercard
Card
MAB World Elite X
Mastercard®
for
BusinessCar
d
MAC Mastercard X
World Elite™
Corporate
Card
ALM
Graduate
d or
Registere
d Product
Code:
Card
Program
Identifier:
Valid Card
Values Program
List Description Country of Issuance
Moldov Thailan
Australia Belarus Brazil Canada a d Ukraine US
MBK Mastercard® X
Black
MCB Mastercard X
BusinessCar
d® Card
MCC Mixed X X X
Mastercard®
Card
MCD Debit X
Mastercard®
Card
MCG Gold X X X X X X
Mastercard®
Card
MCO Mastercard® X
Corporate
Card
MCS Standard X X X X X X
Mastercard®
Card
MCT Titanium X X X
Mastercard®
Card
MCU Mastercard® X X X
Unembossed
MCW World X X X X X X
Mastercard®
Card
ALM
Graduate
d or
Registere
d Product
Code:
Card
Program
Identifier:
Valid Card
Values Program
List Description Country of Issuance
Moldov Thailan
Australia Belarus Brazil Canada a d Ukraine US
MDG Gold Debit X X X X X
Mastercard®
Card
MDH WORLD X X X
DEBIT
EMBOSSED
MDI Debit Other X
Unembossed
MDJ Debit X
Rewards
MDK Debit Other X
2
Unembossed
MDO Debit Other X
MDP Platinum X X X
Debit
Mastercard®
Card
MDQ Middle X
Market
Corporate
Card
MDR Debit X
Brokerage
MDS Debit X X X X X
Mastercard®
Card
ALM
Graduate
d or
Registere
d Product
Code:
Card
Program
Identifier:
Valid Card
Values Program
List Description Country of Issuance
Moldov Thailan
Australia Belarus Brazil Canada a d Ukraine US
MDU Debit X X X X
Unembossed
Mastercard®
Card
MEB Mastercard X
Executive
BusinessCar
d® Card
MEO Mastercard X
Corporate
Executive
Card® Card
MEP Premium X
Debit
Mastercard®
Card
MPC Mastercard X
Professional
Card® card
MPE Mastercard® X
branding to
be
announced
MPL Platinum X X X X X X X
Mastercard®
Card
MSP Muse X
Mastercard®
Card
ALM
Graduate
d or
Registere
d Product
Code:
Card
Program
Identifier:
Valid Card
Values Program
List Description Country of Issuance
Moldov Thailan
Australia Belarus Brazil Canada a d Ukraine US
MUP Premium X
Debit
Unembossed
Mastercard®
Card
MWB World X
Mastercard®
for Business
Corporate
Executive
Card
MWE World Elite™ X X X X
Mastercard®
Card
MWO Mastercard® X
Corporate
World
MXO Debit Card X
Other
MXR Debit Card X
Brokerage
MXS Debit Card X
Standard
SAP Platinum X
Mastercard®
Salary–
Immediate
Debit
ALM
Graduate
d or
Registere
d Product
Code:
Card
Program
Identifier:
Valid Card
Values Program
List Description Country of Issuance
Moldov Thailan
Australia Belarus Brazil Canada a d Ukraine US
TPL Platinum X
MasterCard-
Immediate
Debit
TWB World X
Mastercard®
Black Edition
—Immediate
Debit
WBE World X
Mastercard®
Black Edition
WDR World Debit X
Mastercard®
Rewards
XXX PAN is not
registered in
Product
Graduation
Plus or
Consumer
Product
Monitoring
Service
NOTE: *Brazil Digital Product Codes were introduced for domestic acquiring and issuing only, and are
not supported for global acquirer acceptance ALM Product Graduation Plus will be enhanced in a
future release to be compatible with Digital Product Codes.
Values
Values
NOTE: *Consumer Product Monitoring Service, will process using Rate Types associated with a
Registered Product Code in Subfield 2 (ALM Product Code).
Values
Attributes
Usage
The following table shows the usage of this PDS (whether it is mandatory, conditional, optional,
system-provided, or not required) in applicable messages.
Amount values
All currency amounts are expressed in the minor unit of currency without a decimal separator in
accordance with ISO standards for currency notation. All amounts support the optional
Extended Decimal Precision (EDP) service. For example, a transaction amount of USD 212.55 is
expressed as 000000000000021255 and 2 decimal positions without the EDP service (see PDS
0147), and will be expressed as 000000000212550000 and 6 decimal positions with EDP
(when PDS 0147 is present).
Application notes
Fee Amount occurrence examples include: Base amount, Override replacement amount, Base +
Rate Type adjustment(s), Override + Rate Type adjustment(s).
ALM-processed transactions where no ALM interchange was applied ('PAN not registered' or
ALM service errors) will show a Base amount only. PDS 0276 Fee Amount and Direction
subfields are shown from the acquirer/receiver view.
NOTE: This field will remain unchanged from the original message when processing a reversal of a
previous message.
All subfields are present for each fee occurrence. The values to be used for each fee subfield are
described in the following text.
NOTE: Refer to the Fee Assignment section of the GCMS Reference Manual, Chapter 11 Business
Service for the list of Override criteria descriptions and the hierarchical order of selection.
Attributes
Usage
This table shows the usage of PDS 0280 (whether it is mandatory, conditional, optional,
system-provided, or not required) in applicable messages.
Usage
This PDS identifies in File Reject/1644 and Message Exception/1644 messages the file that
contains errors.
This PDS is comprised of four subfields to indicate the file type, the file processing date, the ID
of the customer or processor associated with the file, and a file sequence number to identify the
file uniquely. The combination of these four subfields together forms a value that uniquely
identifies all files to or from a customer processing facility.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
In reconciliation messages, this PDS contains PDS 0105 (File ID) 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, PDS 0298 (Reconciled, Transmission) presents and identifies reconciliation totals at
the physical transmission level.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS contains the sum amount of all amounts from each occurrence of DE 4 (Amount,
Transaction) 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.
Attributes
Justification: N/A
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS indicates in reconciliation messages whether the related reconciliation totals represent
acquiring activity, issuing activity, or fee collection activity. Refer to Reconciliation messages for
additional information about classifying activity into one of these categories.
For Settlement Position Detail/1644 messages, PDS 0302 is provided automatically if the
customer selects the acquirer BIN or issuer account range settlement reconciliation categories.
Values
The data values are listed in this table.
Values
Value Description
A Acquiring activity
I Issuing activity
F Fee collection activity
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS contains the total count of messages occurring in a logical file, including the File
Header (Customer-generated or Clearing System-generated)/1644 and File Trailer (Customer-
generated or Clearing System-generated)/1644. This PDS is provided in File Trailer (Customer-
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.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS reflects in Reconciliation messages, the PDS 0158 (Business Activity) to which the
related reconciliation totals apply.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
In reconciliation messages, this PDS reflects the settlement activity (PDS 0159 [Settlement
Data 1]) to which the related reconciliation totals apply.
Attributes
Usage
The following table shows the usage of this PDS (whether it is mandatory, conditional, optional,
system-provided, or not required) in applicable messages.
NOTE: New PDS 0360 will be present only if a split amount is required.
New PDS 0360 indicates that there has been a split in the reconciliation total reported in
reconciliation messages. The subfields indicate the sequence and the total number of message
splits.
For example, assume that GCMS calculates a reconciliation amount of 19,999,999,999,999,999
(17 digits).
The current GCMS functionality will truncate (drop) the leftmost digit when placing this amount
into PDS 0396 (Amount, Net Total in Reconciliation Currency). The resulting amount of
9,999,999,999,999,999 (16 digits) will present in a single 1644-685 message.
Continuing with the example above, the new GCMS functionality will split that single
reconciliation amount into multiple amounts (in this case, specifically three amounts) and
include each amount in three separate 1644-685 reconciliation messages. The sum total of
those three amounts will equal the total reconciliation amount.
Additionally, to simplify customer reconciliation processing, GCMS will insert new PDS 0360 into
each of those reconciliation messages to provide the sequence number of each related message
and the total number of messages pertaining to given split amount, as follows:
1. PDS 0360 subfield 1 = 00001, PDS 0360 subfield 2 = 00003 and PDS 0396 =
9999999999999999 (16 positions)
2. PDS 0360 subfield 1 = 00002, PDS 0360 subfield 2 = 00003 and PDS 0396 =
9999999999999999 (16 positions)
3. PDS 0360 subfield 1 = 00003, PDS 0360 subfield 2 = 00003 and PDS 0396 =
0000000000000001 (16 positions)
The total reconciliation amount can then be calculated as: 9,999,999,999,999,999 +
9,999,999,999,999,999 + 0000000000000001 = 19,999,999,999,999,999
All of the related 1644-685 messages for a given split will always be sent in the proper order
and always sent together sequentially. Mastercard will never intermix 1644-685 messages from
unrelated splits, nor will Mastercard ever separate the messages belonging to a split with a
single message that is not related to any split whatsoever.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
Refer to PDS 0158, Subfield 1 (Card Program Identifier) for a list of valid values.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
In reconciliation messages, this PDS reflects the specific transaction function group code to
which the related reconciliation totals apply. Transaction function group code refers to a
combination of MTI and DE 24 (Function Code) that provides a method of uniquely identifying
financial transaction categories.
Values
This table lists the transaction functions that are supported in each transaction function group
code.
Values
Transaction
Transaction Function Group Function Group IPM DE 24 Function (includes both
Description and MTI Code originals and reversals)
First Presentment/1240 FP 200
Second Presentment/1240 SP 205 Full and 282 Partial
First Chargeback/1442 FC 450 Full and 453 Partial
Arbitration Chargeback/1442 AC 451 Full and 454 Partial
Fee Collections/1740 FE 700, 780, 781, 782, and 783
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
In reconciliation messages, this PDS reflects the specific customer BIN (obtained from DE 31
[Acquirer’s Reference Data], positions 2–7) that apply to the related reconciliation totals.
Customers selecting this reconciliation category will receive totals only for their own acquiring
BINs that have been established at Mastercard.
If the Reconciled, Acquirer’s BIN reconciliation category is selected, the Reconciled, Member
Activity reconciliation category will be automatically provided to ensure that the customer
receives totals by acquiring BIN, issuing activity, and fee collection activity to provide complete
reconciliation information.
Values
PDS 0369 contains the acquirer’s BIN from DE 31, positions 2–7.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS reflects in reconciliation messages, the specific customer account range (obtained
from the account range portion of DE 2 [Primary Account Number {PAN}]) to which the related
reconciliation totals apply. Customers selecting this reconciliation category receive totals only
for their own issuing account ranges that have been established at Mastercard®.
If the Reconciled, Account Range reconciliation category is selected as a clearing reconciliation
category, GCMS automatically will accumulate totals for the Reconciled, Member Activity
category . This ensures that the customer also receives totals for their acquiring activity and fee
collection activity to provide complete reconciliation information.
Attributes
Subfields: 2
Justification: See “Subfields”
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable 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 DE 24 (Function Code).
Values
Refer to DE 24 (Function Code) for a list of valid transaction function codes.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
Refer to DE 3 (Processing Code), subfield 1, for a list of values.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Customers can assign a proprietary value to PDS 0375 and include it in any financial message. If
an originating customer 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 Business Service Arrangements that qualify for the Extended
Precision Decimal Service, acquirers are allowed to submit PDS 0375, however, it will have the
value Undefined applied to it. This ensures that the acknowledgment reconciliation provided
represents all of the accepted financial activity to the customer for that file.
For any First Presentment/1240, Retrieval Request/1644, Retrieval Request Acknowledgment/
1644, or Fee Collection/1740 Messages that do not contain PDS 0375, the clearing system will
create an acknowledgment message with a Member Reconciliation indicator 1 value of
Undefined. This will ensure that the Acknowledgment reconciliation provided represents 100
percent of the accepted financial activity of the customer for that file. The value in PDS 0300
(Reconciled, File) will also be Undefined.
For example, an acquirer that wants to receive reconciliation totals for a specific 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 Acknowledgment 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, all low values, or all high values.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable 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 PDS 0025
(Reversal Indicator) is not present in the message or if the transaction is a re-submission
(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
This table shows the values that may be provided in this PDS.
Values
Value Description
O Original message amounts
R Reversal message amounts
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS provides, in reconciliation messages, totals in the transaction currency of transaction
amounts with a debit impact to processing. The clearing system accumulates DE 4 (Amount,
Transaction) values for each message in which DE 3 (Processing Code) indicates a debit impact
Values
This PDS may contain zeros if the processed file contained only non-financial messages and the
value of DE 25 (Message Reason Code) = 6861 (Acknowledgment).
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS provides, in reconciliation messages, totals in the transaction currency of transaction
amounts with a credit impact to processing. The clearing system accumulates DE 4 (Amount,
Transaction) values for each message in which DE 3 (Processing Code) indicates a credit impact
on processing to the appropriate customer. Refer to Reconciliation messages for additional
information on classifying activity as debit impact versus credit impact.
Values
This PDS may contain zeros if the processed file contained only non-financial messages and DE
25 (Message Reason Code) = 6861 (Acknowledgment).
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
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 PDS 0380 (Debits, Transaction Amount in Transaction Currency) is greater
than the amount in PDS 0381 (Credits, Transaction Amount in Transaction Currency), 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.
Values
This PDS may contain zeros if the processed file contained only non-financial messages and DE
25 (Message Reason Code) = 6861 (Acknowledgment).
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
This PDS may contain zeros in the acknowledgment reconciliation messages if the processed file
contained only non-financial messages and DE 25 (Message Reason Code) = 6861
(Acknowledgment).
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
This PDS may contain zeros in the acknowledgment reconciliation messages if the processed file
contained only non-financial messages and DE 25 (Message Reason Code) = 6861
(Acknowledgment).
This element contains the sum of DE 5 by currency identified in DE 50 (Currency code,
Reconciliation) and other reconciliation options in effect. Reconciliation messages that reflect
totals for bilateral and collection only activity will contain zeros in this PDS.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS provides, in Reconciliation/1644 messages, totals in the reconciliation currency of fee
amounts with a debit impact to processing. The clearing system accumulates all occurrences of
subfield 7, Amount, Fee, Reconciliation, of PDS 0146 (Amounts, Transaction Fee) for each
message in which subfield 2, Fee Processing Code, of PDS 0146 indicates a debit impact on
processing to the appropriate customer. Refer to Reconciliation messages for additional
information on classifying activity as debit impact versus credit impact.
The Financial Position Detail/1644 and the Settlement Position Detail/1644 messages both will
contain totals in the receiving customer’s reconciliation currency.
Values
This PDS may contain zeros in the acknowledgment reconciliation messages if the processed file
contained only non-financial messages and DE 25 (Message Reason Code) = 6861
(Acknowledgment).
This element contains the sum of PDS 0146 by currency identified in DE 50 (Currency Code,
Reconciliation) and other reconciliation options in effect. Reconciliation messages that reflect
totals for bilateral and collection only activity will contain zeros in this PDS.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS provides, in Reconciliation/1644 messages, totals in the reconciliation currency of fee
amounts with a credit impact to processing. The clearing system accumulates all occurrences of
subfield 7, Amount, Fee, Reconciliation, of PDS 0146 (Amounts, Transaction Fee) for each
message in which subfield 2, Fee Processing Code, of PDS 0146 indicates a credit impact on
processing to the appropriate customer. Refer to Reconciliation messages for additional
information on classifying activity as debit impact versus credit impact.
The Financial Position Detail/1644 message and Settlement Position Detail/1644 message will
contain totals in the receiving customer’s reconciliation currency.
Values
This PDS may contain zeros in the Acknowledgment Reconciliation messages if the processed
file contained only non-financial messages and DE 25 (Message Reason Code) = 6861
(Acknowledgment).
This element contains the sum of PDS 0146 by currency identified in DE 50 (Currency Code,
Reconciliation) and other reconciliation options in effect. Reconciliation messages that reflect
totals for bilateral and collection only activity will contain zeros in this PDS.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
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 PDS 0390 (Debits, Transaction Amount in Reconciliation Currency) is greater
than the amount in PDS 0391 (Credits, Transaction Amount in Reconciliation Currency), 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.
The Financial Position Detail/1644 message and Settlement Position Detail/1644 message will
contain totals in the receiving customer’s reconciliation currency.
Values
This PDS may contain zeros in the Acknowledgment Reconciliation messages if the processed
file contained only non-financial messages and DE 25 (Message Reason Code) = 6861
(Acknowledgment).
This element contains the sum of DE 5 (Amount, Reconciliation) by currency identified in DE 50
(Currency Code, Reconciliation) and other reconciliation options in effect. Reconciliation
messages that reflect totals for bilateral and collection only activity will contain zeros in this
PDS.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS provides, in Reconciliation/1644 messages, net totals in the 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 PDS 0392 (Debits, Fee Amounts in Reconciliation Currency) is
greater than the sum of all amounts in PDS 0393 (Credits, Fee Amounts in Reconciliation
Currency), 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.
The Financial Position Detail/1644 message and Settlement Position Detail/1644 message will
contain totals in the receiving customer’s reconciliation currency.
Values
This PDS may contain zeros in the Acknowledgment Reconciliation messages if the processed
file contained only non-financial messages and DE 25 (Message Reason Code) = 6861
(Acknowledgment).
This element contains the sum of PDS 0146 (Amounts, Transaction Fee) by currency identified in
DE 50 (Currency Code, Reconciliation) and other reconciliation options in effect. Reconciliation
messages that reflect totals for bilateral and Collection Only activity will contain zeros in this
PDS.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS provides, in Reconciliation/1644 messages, net totals in the reconciliation currency of
transaction amounts and fee amounts. The values used in calculating PDS 0396 are from PDS
0394 (Amount, Net Transaction in Reconciliation Currency) and PDS 0395 (Amount, Net Fee in
Reconciliation Currency).
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.
The Financial Position Detail/1644 message and Settlement Position Detail/1644 message will
contain totals in the receiving customer’s reconciliation currency.
Values
This PDS may contain zeros in the acknowledgment reconciliation messages if the processed file
contained only non-financial messages and DE 25 (Message Reason Code) = 6861
(Acknowledgment). Reconciliation messages that reflect totals for bilateral and collection only
activity will contain zeros in this PDS.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS provides, in reconciliation messages (1644-685, 1644-688), totals in the reconciliation
currency of extended precision amounts with a debit impact to processing. The clearing system
accumulates all occurrences of subfield 7 (Interchange Amount, Fee, Reconciliation) of PDS
0147 (Extended Precision Amount) for each message in which subfield 2 (Fee Processing Code)
of PDS 0147 indicates a debit impact on processing to the appropriate customer. The Financial
Position Detail-1644-685 message and the Settlement Position Detail-1644-688 messages
both contain totals in the receiving customer’s reconciliation currency.
Values
All currency amounts are expressed to 6 decimals without a decimal separator in accordance
with ISO standards for currency notation. For example, an interchange fee amount of
USD .000123 is expressed as 000000000000000123.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS provides, in reconciliation messages (1644-685, 1644-688), totals in the reconciliation
currency of extended precision amounts with a credit impact to processing. The clearing
Values
All currency amounts are expressed to six decimals without a decimal separator in accordance
with ISO standards for currency notation. For example, an interchange fee amount of
USD .000123 is expressed as 000000000000000123.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS provides, in reconciliation messages (1644-685, 1644-688), net totals in the
reconciliation currency of Extended Precision amounts with a debit impact to processing and
those with a credit impact to processing. If the sum of all amounts in PDS 0397 (Debits,
Extended Precision Amounts in Reconciliation Currency) is greater than the sum of all amounts
in PDS 0398 (Credits, Extended Precision Amounts in Reconciliation Currency), the GCMS
inserts a D in PDS 0399, subfield 1 and inserts the excess amount in PDS 0399, subfield 2. If the
sum of all amounts in PDS 0397 is greater than the sum of all amounts in PDS 0398, the GCMS
inserts a C in subfield 1 of PDS 0399 and inserts the excess amount in PDS 0399, subfield 2. The
Financial Position Detail/1644 message and Settlement Position Detail/1644 message will
contain totals in the receiving customer’s reconciliation currency.
Values
All currency amounts are expressed to six decimals without a decimal separator in accordance
with ISO standards for currency notation. For example, an interchange fee amount of
USD .000123 is expressed as 000000000000000123.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS provides in Reconciliation/1644 messages the total number of transactions whose
transaction amounts have a debit impact to processing. The clearing system accumulates the
number of messages for which DE 3 (Processing Code) indicates a debit impact on processing
to the appropriate customer. Refer to Reconciliation messages for additional information on
classifying activity as debit impact versus credit impact.
Values
This PDS may contain zeros if the processed file contained only non-financial messages.
Attributes
Usage
This table shows the usage of this PDS (mandatory, conditional, optional, system-provided, or
not required) in applicable messages.
Usage
This PDS provides in Reconciliation/1644 messages, the total number of transactions whose
transaction amounts have a credit impact to processing. To do this, the clearing system
accumulates the number of messages for which DE 3 (Processing Code) indicates a credit
impact on processing to the appropriate customer.
Values
This PDS may contain zeros if the processed file contained only non-financial messages.
This PDS is populated based on final fund direction of the customer. If the customer’s net
position is a debit then the PDS contains the accumulated counts.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS provides in Reconciliation/1644 messages the total number of transactions whose
transaction amounts have either a debit or a credit impact to processing. To do this, the clearing
system accumulates PDS 0400 (Debits, Transaction Number) and PDS 0401 (Credits,
Transaction Number) and inserts the result in PDS 0402.
Values
This PDS may contain zeros if the processed file contained only non-financial messages.
This PDS is populated based on the final fund direction of the customer. If the customer’s net
position is a credit then this PDS contains the accumulated counts.
Attributes
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.
Values
If present, PDS 0444 must be numeric and cannot contain all zeros.
If a First Presentment message rejects because the transaction has been identified as a
potential duplicate by Mastercard, the clearing system provides this PDS to the acquirer in the
First Presentment message that accompanies the Message Exception/1644 message.
If the acquirer resubmits the transaction following validation, this PDS must be present and
contain the same value received in the Message Exception/1644 message. This PDS is not
forwarded to the issuer.
Attributes
Attribute Description
Data Representation: ans...992; TAGLLLVAR
Tag Field: 0445
Length Field: 3 positions, value = 011–992
Data Field: Variable length, 11–992 positions
Subfields: None
Justification: Left
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Values
PDS 0445 is a free-form text field in the following format and can accommodate any DE and
PDS values that are replaced and substituted from its original value. This position
representation illustrates multiple DEs or PDSs being changed during processing:
• Position 1 (Tag type) which can have value of either 2 representing DE or a value of 3 PDS.
• Position 2 (Tag number) which is a format of nnnn (numeric 4 bytes) representing the actual
DE or PDS number.
• Position 6 (Tag subfield number) which is a format of nn (numeric 2 bytes) representing the
DE or PDS subfield number. It is “00” if the DE or PDS does not have any subfields.
• Position 8 (Tag length) which is a format of nnn (numeric 3 bytes) representing the DE or
PDS length.
• Position 11 represents its original DE or PDS value.
Requirements
PDS 0445 can accommodate any number of DEs and PDSs, up to a maximum of 999
characters in length, with what GCMS replaced it with during the time of processing.
Attributes
Usage
This element is created when PDS 0146, subfield 5 (Amount, Fee) was flagged for a syntax
error.
Values
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.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
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.
New usage codes are added periodically as required to support various industry and acceptor
organizations. The clearing system validates the usage code and rejects a message if it contains
an invalid usage code.
Industry Record
Usage Code Number Description
01 000 Passenger Transport Detail, General Ticket
Information
01 001 Passenger Transport Detail, Trip Leg Data
01 002 Passenger Transport Detail, Rail 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
12 000 Travel Agency Detail
13 000 Lodged Account Detail
14 000 Private Label Common Data
14 001 Private Label Line Item Detail
15 000 Healthcare-IIAS 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
acceptor organizations. Customers 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 customer. 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.
• For Financial Detail Addendum (Lodged Account, Detail)/1644 messages (PDS 0501,
subfield 1 Usage Code 13 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 to 999.
• For Financial Detail Addendum (Telephony Billing, Detail)/1644 messages (PDS 0501,
subfield 1 Usage Code 11 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 to 999.
• For Financial Detail Addendum (Corporate Card Common Data Requirements)/1644
messages (PDS 0501, subfield 1 Usage Code 98 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 (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 between 001 and 003.
• For Financial Detail Addendum (Corporate Line Item Detail)/1644 messages (PDS 0501,
subfield 1 Usage Code 98 and PDS 0501, subfield 2 Industry Record Number 950), the value
of PDS 0501, subfield 3 Occurrence Indicator must be within the range of 002 to 999.
• For Financial Detail Addendum (Generic Detail)/1644 messages (PDS 0501, subfield 1
Usage Code 99 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 to 999.
• For Financial Detail Addendum (Healthcare)/1644 messages (PDS 0501, subfield 1 Usage
Code 15 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 (Private Label Common Data)/1644 messages (PDS 0501,
subfield 1 Usage Code 14 and PDS 0501, subfield 2 Industry Record Number 000), the value
of PDS 0501, subfield 3 Occurrence Indicator must be the value of 001.
• For Financial Detail Addendum (Private Label Line Item Detail)/1644 messages (PDS 0501,
subfield 1 Usage Code 14 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 to 999.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS is required in First Presentment/1240, Financial Detail Addendum (Travel Agency
Detail)/1644, or Financial Detail Addendum (Lodged Account Detail)/1644 messages for
transactions submitted for the interchange rate programs with Brand Product MEF in this
table.
IRD Description
67 Commercial Data Rate II
82 Electronic Payment Account
Values
If PDS 0502 is present, both subfield 1 and subfield 2 must be present.
PDS 0502 is required in First Presentment/1240 messages to qualify for corporate incentives
within some intra-European and inter-European interchange programs.
For Mastercard In Control® First Presentment/1240 messages:
• If PDS 0502 is present in the message then the values will be overlaid with the value OTHER1
in subfield 1 (Custom Identifier Type) and the Virtual Account Number in subfield 2 (Custom
Identifier Detail).
• If PDS 0502 is not present in the First Presentment/1240 then PDS 0502 is added to the
message and sent to the issuer. The values are OTHER1 in subfield 1 (Custom Identifier Type)
and the Virtual Account Number in subfield 2 (Custom Identifier Detail).
PDS 0502 (Custom Identifier), subfield 1 (Custom Identifier Type) is required and must contain
the value PMTREF along with the data in subfield 2 (Customer Identifier Detail) for U.S. region
(2/010001) transactions submitted for IRD 67 (Commercial Data Rate II) when the account
number represents the MEF product.
PDS 0502 (Custom Identifier), subfield 1 (Custom Identifier Type) is required and must contain
the value PMTREF along with the data in subfield 2 (Customer Identifier Detail) for U.S. region
(2/010001) transactions submitted for IRD 82 (Commercial Electronic Payment Account).
Value Description
CUSORD Customer Order
CUSTPO Customer Purchase Order
FOLNUM Folio Number
INVACT Invoice or Account Number for Bill Payments
OTHER1 Other
PMTREF Payment Reference Number
PRCHID Purchase Identification
Value Description
RECLOC Record Locator
RESNUM Reservation Number
RNTAGR Rental Agreement
SUPINV Supplier Invoice
SUPORD Supplier Order
TKTNUM Ticket Number
TRANID Transaction Identification
TRKNUM Tracking Number
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, this PDS must be left-justified and cannot contain all zeros, all spaces, all high values,
or all low values.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
NOTE: Financial Detail Addendum/1644 messages that contain amounts and amount exponents
should utilize the same currency and exponent of the Amount, Transaction in the associated First
Presentment/1240 message.
Value Description
D Travel Agency Fee Amount is a debit.
C Travel Agency Fee Amount is a credit.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS is required if the associated First Presentment/1240 contains an airline acceptor
business code (MCC) or railway MCC and is submitted for one of the U.S. region incentive
interchange rate programs listed in this table.
IRD Description
10 Merit III Tier 1
11 Merit III Tier 2
12 Merit III Tier 3
24 Merchant UCAF
69 Commercial T&E Rate II
70, 80 Merit III Base
76, 86 Commercial T&E Rate I
78, 88, 98 Merit I
79 Full UCAF
89 Commercial T&E Rate III
93 Passenger Transport
96 World T&E
RA Enhanced Merit III Base
RB Enhanced Merit III Tier 1
RC Enhanced Merit III Tier 2
RD Enhanced Merit III Tier 3
RN Enhanced Merchant UCAF
RO Enhanced Full UCAF
RR Enhanced Passenger Transport
SL Business Level 2 T&E Rate I
SN Business Level 2 T&E Rate II
SO Business Level 2 T&E Rate III
3L Business Level 3 T&E Rate I
3N Business Level 3 T&E Rate II
3O Business Level 3 T&E Rate III
4L Business Level 4 T&E Rate I
4N Business Level 4 T&E Rate II
4O Business Level 4 T&E Rate III
This PDS is required if a Passenger Transport Detail, Rail Data Addendum message is submitted
and the associated First Presentment/1240 contains a Rail or Travel Agency MCC and is
submitted for one of the interchange programs listed in this table.
IRD Description
10 Merit III Tier I
11 Merit III Tier 2
12 Merit III Tier 3
22 Public Sector
24 Merchant UCAF
29 Emerging Markets, Consumer Core Value
56 World Public Sector
69 Commercial T&E Rate II
70/80 Merit III Base
79 Full UCAF
89 Commercial T&E Rate III
93 Passenger Transport
96 World T&E
HP World High Value Public Sector
RA Enhanced Merit III Base
RB Enhanced Merit III Tier 1
RC Enhanced Merit III Tier 2
RD Enhanced Merit III Tier 3
RK Enhanced Public Sector
RN Enhanced Merchant UCAF
RO Enhanced Full UCAF
RP Enhanced Merit I
RR Enhanced Passenger Transport
SL Business Level 2 T&E Rate I
SN Business Level 2 T&E Rate II
SO Business Level 2 T&E Rate III
IRD Description
WP World Elite Public Sector
WZ World Elite T&E Large Ticket
3L Business Level 3 T&E Rate I
3N Business Level 3 T&E Rate II
3O Business Level 3 T&E Rate III
4L Business Level 4 T&E Rate I
4N Business Level 4 T&E Rate II
4O Business Level 4 T&E Rate III
This PDS optionally may be provided for airline, railway, or travel agency 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.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS is required if the associated First Presentment/1240 contains an airline acceptor
business code (MCC) or railway MCC and is submitted for the U.S. region incentive interchange
rate programs listed in this table.
IRD Description
10 Merit III Tier 1
11 Merit III Tier 2
12 Merit III Tier 3
22 Public Sector
24 Merchant UCAF
29 Emerging Markets: Consumer Core Value
56 World Public Sector
69 Commercial T&E Rate II
70/80 Merit III Base
76/86 Commercial T&E Rate I
78/88/98 Merit I
79 Full UCAF
89 Commercial T&E Rate III
93 Passenger Transport
96 World T&E
HP World High Value Public Sector
RA Enhanced Merit III Base
RB Enhanced Merit III Tier 1
RC Enhanced Merit III Tier 2
IRD Description
RD Enhanced Merit III Tier 3
RK Enhanced Public Sector
RN Enhanced Merchant UCAF
RR Enhanced Passenger Transport
SL Business Level 2 T&E Rate I
SN Business Level 2 T&E Rate II
SO Business Level 2 T&E Rate III
WP World Elite Public Sector
3L Business Level 3 T&E Rate I
3N Business Level 3 T&E Rate II
3O Business Level 3 T&E Rate III
4L Business Level 4 T&E Rate I
4N Business Level 4 T&E Rate II
4O Business Level 4 T&E Rate III
This PDS is required if a Passenger Transport Detail, Rail Data Addendum message is submitted
and the associated First Presentment/1240 contains a rail or travel agency MCC and is
submitted for IRD 89, Commercial T&E Rate III.
This PDS optionally may be provided for airline, railway, or travel agency transactions submitted
for any other interchange program.
When an occurrence of the Financial Detail Addendum (Passenger Transport Detail, General
Ticket Information)/1644 or Financial Detail Addendum (Passenger Transport Detail, Rail
Data)/1644 addendum message is submitted in association with a First Presentment/1240
message, it must include PDS 0506 (Ticket Number) and cannot contain null values.
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.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS is required if the associated First Presentment/1240 contains an airline acceptor
business code (MCC) or railway MCC and is submitted for 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
22 Public Sector
IRD Description
24 Merchant UCAF
29 Emerging Markets, Consumer Core Value
56 World Public Sector
69 Commercial T&E Rate II
70/80 Merit III Base
76/86 Commercial T&E Rate I
78/88/98 Merit I
79 Full UCAF
89 Commercial T&E Rate III
93 Passenger Transport
96 World T&E
HP World High Value Public Sector
RA Enhanced Merit III Base
RB Enhanced Merit III Tier 1
RC Enhanced Merit III Tier 2
RD Enhanced Merit III Tier 3
RK Enhanced Public Sector
RN Enhanced Merchant UCAF
RO Enhanced Full UCAF
RR Enhanced Passenger Transport
SL Business Level 2 T&E Rate I
SN Business Level 2 T&E Rate II
SO Business Level 2 T&E Rate III
WP World Elite Public Sector
3L Business Level 3 T&E Rate I
3N Business Level 3 T&E Rate II
3O Business Level 3 T&E Rate III
4L Business Level 4 T&E Rate I
4N Business Level 4 T&E Rate II
4O Business Level 4 T&E Rate III
This PDS optionally may be provided for airline or railway transactions submitted for any other
interchange program.
When an occurrence of the Financial Detail Addendum (Passenger Transport Detail, General
Ticket Information)/1644 addendum message is submitted in association with a First
Presentment/1240 message, it must include PDS 0507 (Issuing Carrier) and cannot contain null
values.
Values
If present, PDS 0507 must be left-justified and cannot contain all low values, all high values, all
spaces, or all zeros.
PDS 0507 must contain a valid International Air Transport Association (IATA) two character
Airline code.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS is required in Financial Detail Addendum (Shipping/Courier) and Financial Detail
Addendum (Temporary Services) messages for transactions submitted for the interchange rate
programs listed in this table, if provided by the customer.
IRD Description
60 Commercial Face-to-Face
62 Commercial Large Ticket I
66 Commercial Data Rate III
67 Interregional Commercial Purchasing Data Rate II
67 Commercial Data Rate II
94 Commercial Large Ticket II
99 Commercial Large Ticket III
E1 Commercial Large Ticket Rate 1 MPG
E2 Commercial Large Ticket Rate 2 MPG
E3 Commercial Large Ticket Rate 3 MPG
This PDS is required in Financial Detail Addendum (Corporate Card Common Data
Requirements) messages for transactions submitted with interchange rate program GCMS
Product Code MEF 82 (Commercial Electronic Payment Account).
PDS 0508 must be present in a Financial Detail Addendum (Corporate Card Common Data
Requirements)/1644 when all of these conditions exist:
The IRD submitted in the associated First Presentment/1240 is one of the values listed in this
table.
IRD descriptions
IRD Description
26 Purchasing Large Ticket Level 1 Interchange
27 Purchasing Large Ticket Level 2 Interchange
If the customer provides the customer code, this PDS must be submitted to qualify the
transaction for the U.S. region and international incentive interchange rate programs listed in
this table.
IRD descriptions
IRD Description
60 Commercial Face-to-Face
62 Commercial Large Ticket I
66 Commercial Data Rate III
67 Commercial Data Rate II
67 Inter-regional Commercial Purchasing Data Rate II
94 Commercial Large Ticket II
IRD Description
99 Commercial Large Ticket III
F1 Commercial Fleet Data Rate I
F2 Commercial Fleet Data Rate II
F3 Commercial Fleet Data Rate III
FL Commercial Fleet Large Ticket
If the customer provides the customer code, PDS 0508 must be submitted to qualify the
transaction for these Canada incentive interchange rate programs:
• BQ: Canada Intracountry Commercial Data Rate I (only for transactions at non-fuel and non-
maintenance locations)
• BR: Canada Intracountry Commercial Data Rate II, and
• BS: Canada Intracountry Commercial Large Ticket.
Values
If present, PDS 0508 must be left-justified and cannot contain all spaces.
Attributes
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
When an occurrence of the Financial Detail Addendum (Passenger Transport Detail, General
Ticket Information)/1644 addendum message is submitted in association with a First
Presentment/1240 message, it must include PDS 0509 (Issue Date) and cannot contain null
values
Values
If present, PDS 0509 must contain a valid date in the format YYMMDD.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, PDS 0510 must be left-justified and cannot contain all low values, all high values, all
spaces, or all zeros.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, PDS 0511 must be left-justified and cannot contain all low values, all high values, all
spaces, or all zeros.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS is required if the associated First Presentment/1240 contains an airline acceptor
business code (MCC) or railway MCC and is submitted for any of these interchange rate
programs:
• IRD 89: Commercial T&E Rate III
• IRD SO: Business Level 2 T&E Rate III
• IRD 3O: Business Level 3 T&E Rate III, or
• IRD 4O: Business Level 4 T&E Rate III.
This PDS optionally may be provided for airline or railway transactions submitted for any other
interchange program.
Values
If present, PDS 0512 can contain all zeros. It cannot contain all spaces.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, PDS 0513 can contain all zeros.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, PDS 0514 can contain all zeros.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, PDS 0515 must be left-justified and cannot contain all low values, all high values, all
spaces, or all zeros.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, PDS 0516 cannot contain all low values, all high values, all spaces, or all zeros.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, PDS 0517 cannot contain all low values, all high values, all spaces, or all zeros.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
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.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, PDS 0519 must be a fixed length of 14, and each of the 14 subfields must contain a
value of Y or N. If unknown, a value of N should be provided.
Values
Each subfield must have a valid value of Y or N. If the information is unknown, a value of N
should be provided.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS is required if the associated First Presentment/1240 contains an airline acceptor
business code (MCC) or railway MCC and is submitted for one of the U.S. region incentive
interchange rate programs listed in this table.
IRD Description
10 Merit III Tier 1
11 Merit III Tier 2
12 Merit III Tier 3
22 Public Sector
IRD Description
24 Merchant UCAF
29 Emerging Markets, Consumer Core Value
56 World Public Sector
69 Commercial T&E Rate II
70/80 Merit III Base
79 Full UCAF
89 Commercial T&E Rate III
93 Passenger Transport
96 World T&E
HP World High Value Public Sector
RA Enhanced Merit III Base
RB Enhanced Merit III Tier 1
RC Enhanced Merit III Tier 2
RD Enhanced Merit III Tier 3
RK Enhanced Public Sector
RN Enhanced Merchant UCAF
RO Enhanced Full UCAF
RR Enhanced Passenger Transport
WP World Elite Public Sector
When an occurrence of the Financial Detail Addendum (Passenger Transport Detail, Rail Data)/
1644 or Financial Detail Addendum (Passenger Transport Detail, Trip Leg Data)/1644
addendum message is submitted in association with a First Presentment/1240 message, it
must include PDS 0520 (Travel Date) and cannot contain null values.
Values
If present, PDS 0520 must be a valid date in the format YYMMDD. Customers must use the
ticket purchase date for open tickets.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
IRD Description
10 Merit III Tier 1
11 Merit III Tier 2
12 Merit III Tier 3
22 Public Sector
24 Merchant UCAF
29 Emerging Markets, Consumer Core Value
56 World Public Sector
69 Commercial T&E Rate II
70/80 Merit III Base
79 Full UCAF
89 Commercial T&E Rate III
93 Passenger Transport
96 World T&E
HP World High Value Public Sector
RA Enhanced Merit III Base
RB Enhanced Merit III Tier 1
RC Enhanced Merit III Tier 2
RD Enhanced Merit III Tier 3
RK Enhanced Public Sector
RN Enhanced Merchant UCAF
RO Enhanced Full UCAF
RR Enhanced Passenger Transport
WP World Elite Public Sector
When an occurrence of the Financial Detail Addendum (Passenger Transport Detail, Trip Leg
Data)/1644 addendum message is submitted in association with a First Presentment/1240
message, it must include PDS 0521 (Carrier Code) and cannot contain null values.
Values
PDS 0521 must contain a valid International Air Transport Association (IATA) two character
Airline code.
If present, it must be left-justified and cannot contain all low values, all high values, all spaces, or
all zeros.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
IRD Description
10 Merit III Tier 1
11 Merit III Tier 2
12 Merit III Tier 3
22 Public Sector
29 Emerging Markets, Consumer Core Value
56 World Public Sector
69 Commercial T&E Rate II
70, 80 Merit III Base
89 Commercial T&E Rate III
93 Passenger Transport
96 World T&E
HP World High Value Public Sector
RA Enhanced Merit III Base
RB Enhanced Merit III Tier 1
RC Enhanced Merit III Tier 2
RD Enhanced Merit III Tier 3
RK Enhanced Public Sector
RN Enhanced Merchant UCAF
RO Enhanced Full UCAF
RR Enhanced Passenger Transport
WP World Elite Public Sector
When an occurrence of the Financial Detail Addendum (Passenger Transport Detail, Trip Leg
Data)/1644 addendum message is submitted in association with a First Presentment/1240
message, it must include PDS 0522 (Service Class Code) and cannot contain null values.
Values
PDS 0522 is the service class code obtained from the IATA or its equivalent. If present, it must
be left-justified and cannot contain all low values, all high values, all spaces, or all zeros.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
IRD Description
10 Merit III Tier 1
IRD Description
11 Merit III Tier 2
12 Merit III Tier 3
22 Public Sector
24 Merchant UCAF
29 Emerging Markets, Consumer Core Value
56 World Public Sector
69 Commercial T&E Rate II
70/80 Merit III Base
79 Full UCAF
89 Commercial T&E Rate III
93 Passenger Transport
96 World T&E
HP World High Value Public Sector
RA Enhanced Merit III Base
RB Enhanced Merit III Tier 1
RC Enhanced Merit III Tier 2
RD Enhanced Merit III Tier 3
RK Enhanced Public Sector
RN Enhanced Merchant UCAF
RO Enhanced Full UCAF
RR Enhanced Passenger Transport
WP World Elite Public Sector
When an occurrence of the Financial Detail Addendum (Passenger Transport Detail, Trip Leg
Data)/1644 addendum message is submitted in association with a First Presentment/1240
message, it must include PDS 0523 (City of Origin/Airport Code) and cannot contain null values.
Values
PDS 0523 must contain a valid International Air Transport Association (IATA) three letter
Location Identifier (Airport Code) or Mastercard defined non-travel code.
Code Description
XUP Upgrade
XAF Club fee
XCA Cargo
XOT Tour order
XDF Duty free
XAE Baggage charge
XAO Prepaid ticket
XAA Miscellaneous charge
XTD Delivery
XPC Pet carrier
XPE Ticket reissue
If present, this PDS must be left-justified and cannot contain these values or formats:
• Low values
• High values
• All spaces
• All zeros, or
• Only one character.
Attributes
Justification: Left
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
IRD Description
10 Merit III Tier 1
11 Merit III Tier 2
12 Merit III Tier 3
22 Public Sector
24 Merchant UCAF
29 Emerging Markets, Consumer Core Value
56 World Public Sector
69 Commercial T&E Rate II
70, 80 Merit III Base
79 Full UCAF
89 Commercial T&E Rate III
IRD Description
93 Passenger Transport
96 World T&E
HP World High Value Public Sector
RK Enhanced Public Sector
WP World Elite Public Sector
When an occurrence of the Financial Detail Addendum (Passenger Transport Detail, Trip Leg
Data)/1644 addendum message is submitted in association with a First Presentment/1240
message, it must include PDS 0524 (City of Destination/Airport Code) and cannot contain null
values.
Values
PDS 0524 must contain a valid International Air Transport Association (IATA) three letter
Location Identifier (Airport Code) or Mastercard defined non-travel code.
Code Description
XUP Upgrade
XAF Club fee
XCA Cargo
XOT Tour order
XDF Duty free
XAE Baggage charge
XAO Prepaid ticket
XAA Miscellaneous charge
XTD Delivery
XPC Pet carrier
XPE Ticket reissue
If present, this PDS must be left-justified and cannot contain these values or formats:
• Low values
• High values
• All spaces
• All zeros, or
• Only one character.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS is required if the associated First Presentment/1240 contains an airline acceptor
business code (MCC) or railway MCC and is submitted for the U.S. region Commercial T&E III
(IRD 89) incentive interchange rate program and the acquirer submits a Financial Detail
Addendum (Passenger Transport Detail, Trip Leg Data)/1644 message.
This PDS optionally may be provided for airline or railway transactions submitted for any other
interchange program.
Values
PDS 0525 is the stop over code obtained from the IATA 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 (that is, 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.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, PDS 0526 must be left-justified and cannot contain all spaces, all zeros, all low
values, or all high values.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, PDS 0527 must be left-justified and cannot contain all spaces, all zeros, all low
values, or all high values.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, PDS 0528 can not contain a space, low value, high value, zero.
Attributes
Justification: N/A
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS is required if the associated First Presentment/1240 contains an airline acceptor
business code (MCC) or railway MCC and is submitted for the U.S. region Commercial T&E Rate
III (IRD 89) incentive interchange rate program and the acquirer submits a Financial Detail
Addendum (Passenger Transport Detail, Trip Leg Data)/1644 message.
This PDS optionally may be provided for airline or railway transactions submitted for any other
interchange program.
Values
If present, PDS 0529 cannot contain all low values, all high values, all spaces, or all zeros.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS is required if the associated First Presentment/1240 contains an airline acceptor
business code (MCC) or railway MCC, the transaction is submitted for the U.S. region
Commercial T&E III (IRD 89) incentive interchange rate program, and the acquirer submits a
Financial Detail Addendum (Passenger Transport Detail, Trip Leg Data)/1644 message.
This PDS optionally may be provided for airline or railway transactions submitted for any other
interchange program.
When an occurrence of the Financial Detail Addendum (Passenger Transport Detail, Trip Leg
Data)/1644 addendum message is submitted in association with a First Presentment/1240
message, it must include PDS 0530 (Flight Number) and cannot contain null values.
Values
PDS 530 must contain the numerical operating or marketing carrier assigned flight number. It
should not include the leading IATA two character carrier code.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS is required if the associated First Presentment/1240 contains an airline acceptor
business code (MCC) or railway MCC, the transaction is submitted for the U.S. region
Commercial T&E III (IRD 89) incentive interchange rate program and the acquirer submits a
Financial Detail Addendum (Passenger Transport Detail, Trip Leg Data)/1644 message.
This PDS optionally may be provided for airline or railway transactions submitted for any other
interchange program.
Value Description
A 00:00 (midnight) to 11:59
P 12:00 (noon) to 23:59
space Unknown or not available
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
PDS 0532 (Total Charges) must be a fixed length of 14.
NOTE: Financial Detail Addendum/1644 messages that contain amounts and amount exponents
should utilize the same currency and exponent of the Amount, Transaction in the associated First
Presentment/1240 message.
Value Description
D Total charges amount is a debit.
C Total charges amount is a credit.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Value Description
A 00:00 (midnight) to 11:59
P 12:00 (noon) to 11:59
space Unknown or not available
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
PDS 0534 must be a fixed length of 14.
NOTE: Financial Detail Addendum/1644 messages that contain amounts and amount exponents
should utilize the same currency and exponent of the Amount, Transaction in the associated First
Presentment/1240 message.
Value Description
D Total non-room charges amount is a debit.
C Total non-room charges amount is a credit.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, PDS 0535 can contain all zeros.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, PDS 0536 can contain all zeros.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, PDS 0537 can contain all zeros.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, PDS 0538 must be left-justified and cannot contain all low values, all high values, all
spaces, or all zeros.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
PDS 0539 must be a fixed length of 14.
NOTE: Financial Detail Addendum/1644 messages that contain amounts and amount exponents
should utilize the same currency and exponent of the Amount, Transaction in the associated First
Presentment/1240 message.
Value Description
D Total amount charged on this account is a debit.
C Total amount charged on this account is a credit.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
PDS 0540 must be a fixed length of 14.
NOTE: Financial Detail Addendum/1644 messages that contain amounts and amount exponents
should utilize the same currency and exponent of the Amount, Transaction in the associated First
Presentment/1240 message.
Value Description
D Room service charges amount is a debit.
C Room service charges amount is a credit.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
PDS 0541 must be a fixed length of 14.
NOTE: Financial Detail Addendum/1644 messages that contain amounts and amount exponents
should utilize the same currency and exponent of the Amount, Transaction in the associated First
Presentment/1240 message.
Value Description
D Lounge/Bar charges amount is a debit.
C Lounge/Bar charges amount is a credit.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
PDS 0542 must be a fixed length of 14.
NOTE: Financial Detail Addendum/1644 messages that contain amounts and amount exponents
should utilize the same currency and exponent of the Amount, Transaction in the associated First
Presentment/1240 message.
Value Description
D Transportation charges amount is a debit.
C Transportation charges amount is a credit.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Values
PDS 0543 must be a fixed length of 14.
NOTE: Financial Detail Addendum/1644 messages that contain amounts and amount exponents
should utilize the same currency and exponent of the Amount, Transaction in the associated First
Presentment/1240 message.
Value Description
D Gratuity charges amount is a debit.
C Gratuity charges amount is a credit.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS is required if the associated First Presentment/1240 contains a vehicle rental acceptor
business code (MCC) and is submitted for one of the U.S. region incentive interchange rate
programs listed in this table.
IRD Description
24 Merchant UCAF
69 Commercial T&E Rate II
79 Full UCAF
89 Commercial T&E Rate III
97 Lodging and Auto Rental
RN Enhanced Merchant UCAF
RO Enhanced Full UCAF
RS Enhanced Lodging and Auto Rental
When an occurrence of the Financial Detail Addendum (Vehicle Rental Detail)/1644 addendum
message is submitted in association with a First Presentment/1240 message, it must include
PDS 0544 (Rental Agreement Number) and cannot contain null values.
Values
If the actual rental agreement number contains more than nine digits, customers should
populate PDS 0544 with the agreement number’s right-most nine digits. If present, PDS 0544
must be left-justified and cannot contain all low values, all high values, all spaces, or all zeros.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS is required if the associated First Presentment/1240 contains a vehicle rental acceptor
business code (MCC) and is submitted for one of the U.S. region incentive interchange rate
programs listed in this table.
IRD Description
24 Merchant UCAF
69 Commercial T&E Rate II
79 Full UCAF
89 Commercial T&E Rate III
96 World T&E
97 Lodging and Auto Rental
IRD Description
RN Enhanced Merchant UCAF
RO Enhanced Full UCAF
RS Enhanced Lodging and Auto Rental
When an occurrence of the Financial Detail Addendum (Vehicle Rental Detail)/1644 addendum
message is submitted in association with a First Presentment/1240 message, it must include
PDS 0545 (Renter Name) and cannot contain null values.
Values
PDS 0545 must be a length of 1–040.
If present, PDS 0545 must be left-justified and cannot contain all low values, all high values, all
spaces, or all zeros.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS is required if the associated First Presentment/1240 contains a vehicle rental acceptor
business code (MCC) and is submitted for one of the U.S. region incentive interchange rate
programs listed in this table.
IRD Description
24 Merchant UCAF
69 Commercial T&E Rate II
79 Full UCAF
89 Commercial T&E Rate III
96 World T&E
97 Lodging and Auto Rental
RN Enhanced Merchant UCAF
RO Enhanced Full UCAF
RS Enhanced Lodging and Auto Rental
When an occurrence of the Financial Detail Addendum (Vehicle Rental Detail)/1644 addendum
message is submitted in association with a First Presentment/1240 message, it must include
PDS 0546 (Rental Return City) and cannot contain null values.
Values
PDS 0546 must be a length of 001–025.
If present, PDS 0546 must be left-justified and cannot contain all low values, all high values, all
spaces, or all zeros.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS is required if the associated First Presentment/1240 contains a vehicle rental acceptor
business code (MCC) and is submitted for one of the U.S. region incentive interchange rate
programs listed in this table.
IRD Description
24 Merchant UCAF
69 Commercial T&E Rate II
79 Full UCAF
89 Commercial T&E Rate III
96 World T&E
97 Lodging and Auto Rental
RN Enhanced Merchant UCAF
RO Enhanced Full UCAF
RS Enhanced Lodging and Auto Rental
When an occurrence of the Financial Detail Addendum (Vehicle Rental Detail)/1644 addendum
message is submitted in association with a First Presentment/1240 message, it must include
PDS 0547 (Rental Return State/Province) and cannot contain null values.
Values
If present, PDS 0547 must be left-justified and cannot contain all low values, all high values, all
spaces, or all zeros. It must contain a valid U.S. state code when PDS 0548 (Rental Return
Country) contains USA.
If the rental return occurs in a U.S. territory (Guam, Puerto Rico, or Virgin Islands), customers
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.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS is required if the associated First Presentment/1240 contains a vehicle rental acceptor
business code (MCC) and is submitted for one of the U.S. region incentive interchange rate
programs listed in this table.
IRD Description
24 Merchant UCAF
69 Commercial T&E Rate II
79 Full UCAF
89 Commercial T&E Rate III
96 World T&E
97 Lodging and Auto Rental
RN Enhanced Merchant UCAF
RO Enhanced Full UCAF
RS Enhanced Lodging and Auto Rental
When an occurrence of the Financial Detail Addendum (Vehicle Rental Detail)/1644 addendum
message is submitted in association with a First Presentment/1240 message, it must include
PDS 0548 (Rental Return Country) and cannot contain null values.
Values
If present, PDS 0548 must be left-justified and contain a valid alphabetic ISO country code. It
cannot contain all spaces.
When territories have a defined country code in Chapter 2 of the Quick Reference Booklet, that
country code must be used.
Attributes
Justification: Left
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS is required if the associated First Presentment/1240 contains a vehicle rental acceptor
business code (MCC) and is submitted for one of the U.S. region incentive interchange rate
programs listed in this table.
IRD Description
24 Merchant UCAF
69 Commercial T&E Rate II
79 Full UCAF
89 Commercial T&E Rate III
97 Lodging and Auto Rentals
RN Enhanced Merchant UCAF
RO Enhanced Full UCAF
RS Enhanced Lodging and Auto Rental
When an occurrence of the Financial Detail Addendum (Vehicle Rental Detail)/1644 addendum
message is submitted in association with a First Presentment/1240 message, it must include
PDS 0549 (Rental Return Location ID) and cannot contain null values.
Values
If present, PDS 0549 must be left-justified and cannot contain all spaces.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS is required if the associated First Presentment/1240 contains a vehicle rental acceptor
business code (MCC) and is submitted for one of the U.S. region incentive interchange rate
programs listed in this table.
When an occurrence of the Financial Detail Addendum (Vehicle Rental Detail)/1644 addendum
message is submitted in association with a First Presentment/1240 message, it must include
PDS 0550 (Rental Return Date) and cannot contain null values.
IRD Description
24 Merchant UCAF
69 Commercial T&E Rate II
79 Full UCAF
IRD Description
89 Commercial T&E Rate III
96 World T&E
97 Lodging and Auto Rental
RN Enhanced Merchant UCAF
RO Enhanced Full UCAF
RS Enhanced Lodging and Auto Rental
When an occurrence of the Financial Detail Addendum (Vehicle Rental Detail)/1644 addendum
message is submitted in association with a First Presentment/1240 message, it must include
PDS 0550 (Rental Return Date) and cannot contain null values.
Values
If present, PDS 0550 must contain a valid date in the format YYMMDD.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS is required if the associated First Presentment/1240 contains a vehicle rental acceptor
business code (MCC) and is submitted for one of the U.S. region incentive interchange rate
programs listed in this table.
IRD Description
24 Merchant UCAF
69 Commercial T&E Rate II
79 Full UCAF
89 Commercial T&E Rate III
96 World T&E
97 Lodging and Auto Rental
RN Enhanced Merchant UCAF
RO Enhanced Full UCAF
RS Enhanced Lodging and Auto Rental
When an occurrence of the Financial Detail Addendum (Vehicle Rental Detail)/1644 addendum
message is submitted in association with a First Presentment/1240 message, it must include
PDS 0551 (Rental Checkout Date) and cannot contain null values.
Values
If present, PDS 0551 must contain a valid date in the format YYMMDD.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS is required if the associated First Presentment/1240 contains a lodging acceptor
business code (MCC) and is submitted for the U.S. region Lodging and Auto Rental (IRD 97)
incentive interchange rate program.
This PDS is required if the associated First Presentment/1240 contains a vehicle rental MCC
and is submitted for one of the U.S. region incentive interchange rate programs listed in this
table.
IRD Description
24 Merchant UCAF
69 Commercial T&E Rate II
IRD Description
79 Full UCAF
89 Commercial T&E Rate III
96 World T&E
97 Lodging and Auto Rental
RN Enhanced Merchant UCAF
RO Enhanced Full UCAF
RS Enhanced Lodging and Auto Rental
This PDS is required if the associated First Presentment/1240 contains a lodging MCC and is
submitted for one of the U.S. region incentive interchange rate programs listed in this table.
IRD Description
69 Commercial T&E Rate II
89 Commercial T&E Rate III
96 World T&E
For transactions acquired in the U.S. region or Canada region, PDS 0552, if present, must
contain a 10-position phone number and be 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.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
When an occurrence of the Financial Detail Addendum (Vehicle Rental Detail)/1644 addendum
message is submitted in association with a First Presentment/1240 message, it must include
PDS 0553 (Rental Rate) and cannot contain null values.
Requirements
This PDS is required if the associated First Presentment/1240 contains a fleet card MCC and is
submitted for U.S. region incentive interchange rate program 66 (Commercial Data Rate III).
Value Description
D Daily rate
W Weekly rate
M Monthly rate
space Unknown or unreported
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
PDS 0554 must be a fixed length of 14.
NOTE: Financial Detail Addendum/1644 messages that contain amounts and amount exponents
should utilize the same currency and exponent of the Amount, Transaction in the associated First
Presentment/1240 message.
Value Description
D Conference room charges amount is a debit.
C Conference room charges amount is a credit.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, PDS 0555 must be numeric and may contain all zeros.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, PDS 0556 must be numeric and cannot contain all zeros.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, PDS 0557 must be numeric and may contain all zeros.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, PDS 0558 must contain one of the values listed in this table.
Value Description
K Kilometers
M Miles
space Unknown or unreported
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Value Description
Y Yes (insurance was purchased)
N No (insurance was not purchased)
spaces Unknown or unreported
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
PDS 0560 must be a fixed length of 14.
NOTE: Financial Detail Addendum/1644 messages that contain amounts and amount exponents
should utilize the same currency and exponent of the Amount, Transaction in the associated First
Presentment/1240 message.
Value Description
D Audio visual charges amount is a debit.
C Audio visual charges amount is a credit.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Value Description
A Drop-off charges
B Delivery charges
C Parking expenses
D Extra hours
E Violations
X Multiple charges of the above types
space Unknown or no additional charges
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
PDS 0562 must be a fixed length of 14.
NOTE: Financial Detail Addendum/1644 messages that contain amounts and amount exponents
should utilize the same currency and exponent of the Amount, Transaction in the associated First
Presentment/1240 message.
Value Description
D Banquet charges amount is a debit.
C Banquet charges amount is a credit.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, PDS 0563 must be left-justified and cannot be all low values, all high values, all
spaces, or all zeros.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS is required if the associated First Presentment/1240 contains a vehicle rental acceptor
business code (MCC) and is submitted for the U.S. region Commercial T&E Rate III (IRD 89)
incentive interchange rate program.
Values
PDS 0564, Rental Location City must be a length of 001–025.
If present, PDS 0564 must be left-justified and cannot be all low values, all high values, all
spaces, or all zeros.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS is required if the associated First Presentment/1240 contains a vehicle rental acceptor
business code (MCC) and is submitted for the U.S. region Commercial T&E Rate III (IRD 89)
incentive interchange rate program.
Values
If present, PDS 0565 must be left-justified and cannot contain all low values, all high values, all
spaces, or all zeros. It must contain a valid U.S. state code if PDS 0566 (Rental Location
Country) contains USA.
If the rental location occurs in a U.S. territory (Guam, Puerto Rico, or Virgin Islands), customers
should provide the three-position country code (GUM, PRI, or VIR) in both PDS 0565 and PDS
0566 (Rental Location Country).
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS is required if the associated First Presentment/1240 contains a vehicle rental acceptor
business code (MCC) and is submitted for the U.S. region Commercial T&E Rate III (IRD 89)
incentive interchange rate program.
Values
If present, PDS 0566 must be left-justified and be a valid alphabetic ISO country code. It cannot
contain all spaces.
When territories have a defined country code in Chapter 2 of the Quick Reference Booklet, that
country code must be used.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values)
If present, PDS 0567 must be left-justified and cannot contain all low values, all high values, all
spaces, or all zeros.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS is required if the associated First Presentment/1240 contains a vehicle rental acceptor
business code (MCC) and is submitted for the U.S. region Commercial T&E Rate III (IRD 89)
incentive interchange rate program.
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 listed in this table.
Value Description
0001 Mini
0002 Subcompact
0003 Economy
0004 Compact
0005 Midsize
0006 Intermediate
0007 Standard
0008 Full size
Value Description
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
0026 Large truck
0027 Small SUV
0028 Medium SUV
0029 Large SUV
0030 Exotic SUV
9999 Miscellaneous
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
PDS 0569 must be a fixed length of 14.
NOTE: Financial Detail Addendum/1644 messages that contain amounts and amount exponents
should utilize the same currency and exponent of the Amount, Transaction in the associated First
Presentment/1240 message.
Value Description
D Internet Access Charges amount is a debit.
C Internet Access Charges amount is a credit.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
PDS 0570 must be a fixed length of 14.
NOTE: Financial Detail Addendum/1644 messages that contain amounts and amount exponents
should utilize the same currency and exponent of the Amount, Transaction in the associated First
Presentment/1240 message.
Value Description
D Early departure charges amount is a debit.
C Early departure charges amount is a credit.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
PDS 0571 must be a length of 001–040. If present, PDS 0571 must be left-justified and cannot
contain all low values, high values, all spaces, or all zeros.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable 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.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
PDS 0573 must be present in a Financial Addendum (Electronic Invoice, Transaction Data)/
1644 when the transaction is for one of these Mastercard Payment Gateway Interchange
Programs:
• E1 Commercial Large Ticket Rate 1 MPG
• E2 Commercial Large Ticket Rate 2 MPG, or
• E3 Commercial Large Ticket Rate 3 MPG.
Values
PDS 0573 must be a length of 001–025. If present, PDS 0573 must be left-justified and cannot
contain all low values, high values, all spaces, or all zeros.
Attributes
Justification: N/A
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS is required if the associated First Presentment/1240 contains a lodging acceptor
business code (MCC) and is submitted for one of the U.S. region incentive interchange rate
programs listed in this table.
IRD Description
24 Merchant UCAF
69 Commercial T&E Rate II
79 Full UCAF
89 Commercial T&E Rate III
96 World T&E
97 Lodging and Auto Rental
RN Enhanced Merchant UCAF
RO Enhanced Full UCAF
RS Enhanced Lodging and Auto Rental
Values
If present, PDS 0574 must contain a valid date in the format YYMMDD.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS is required if the associated First Presentment/1240 contains a lodging acceptor
business code (MCC) and is submitted for one of the U.S. region incentive interchange rate
programs listed in this table.
When an occurrence of the Financial Detail Addendum (Lodging Summary)/1644 addendum
message is submitted in association with a First Presentment/1240 message, it must include
PDS 0575 (Departure Date) and cannot contain null values.
IRD Description
24 Merchant UCAF
69 Commercial T&E Rate II
79 Full UCAF
IRD Description
89 Commercial T&E Rate III
96 World T&E
97 Lodging and Auto Rental
RN Enhanced Merchant UCAF
RO Enhanced Full UCAF
RS Enhanced Lodging and Auto Rental
Values
If present, PDS 0575 must contain a valid date in the format YYMMDD.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS is required if the associated First Presentment/1240 contains a lodging acceptor
business code (MCC) and is submitted for one of the following U.S. region incentive interchange
rate programs.
IRD Description
24 Merchant UCAF
69 Commercial T&E Rate II
79 Full UCAF
89 Commercial T&E Rate III
96 World T&E
97 Lodging and Auto Rental
RN Enhanced Merchant UCAF
RO Enhanced Full UCAF
RS Enhanced Lodging and Auto Rental
Values
PDS 0576, Folio Number must be a length of 001–025.
If present, PDS 0576 must be left-justified and cannot contain all low values, all high values, all
spaces, or all zeros.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS is required if the associated First Presentment/1240 contains a lodging acceptor
business code (MCC) and is submitted for the U.S. region Lodging and Auto Rental (IRD 97)
incentive interchange rate program.
Either this PDS or PDS 0552 (Customer Service Toll-Free [800] Number) is required if the
associated First Presentment/1240 contains a lodging MCC and is submitted for one of the U.S.
region incentive interchange rate programs listed in this table.
IRD Description
24 Merchant UCAF
69 Commercial T&E Rate II
79 Full UCAF
IRD Description
89 Commercial T&E Rate III
96 World T&E
RN Enhanced Merchant UCAF
RO Enhanced Full UCAF
For transactions acquired in the U.S. or Canada region, PDS 0577, if present, must contain a 10-
position phone number, left-justified with trailing spaces. The first three positions must be
numeric.
Values
If present, PDS 0577 cannot contain all low values, all high values, all zeros, or all spaces.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Value Description
Y Yes (additional charges were added)
N No (no additional charges were added)
space No additional charges or unknown
NOTE: Financial Detail Addendum/1644 messages that contain amounts and amount exponents
should utilize the same currency and exponent of the Amount, Transaction in the associated First
Presentment/1240 message.
Value Description
D Billing Adjustment amount is a debit.
C Billing Adjustment amount is a credit.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
PDS 0579 must be numeric and must be a fixed length of 006. If present, PDS 0579 must
contain a valid date in the format YYMMDD.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS is required if the associated First Presentment/1240 contains a lodging acceptor
business code (MCC) and is submitted for the U.S. region Commercial T&E Rate III (IRD 89)
incentive interchange rate program.
When an occurrence of the Financial Detail Addendum (Lodging Summary)/1644 addendum
message is submitted in association with a First Presentment/1240 message, it must include
PDS 0580 (Room Rate) and cannot contain null values.
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.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS is required if the associated First Presentment/1240 contains a lodging acceptor
business code (MCC) and is submitted for the U.S. region Commercial T&E Rate III (IRD 89)
incentive interchange rate program.
Values
If present, must be a fixed length of 14.
NOTE:
Financial Detail Addendum/1644 messages that contain amounts and amount exponents should
utilize the same currency and exponent of the Amount, Transaction in the associated First
Presentment/1240 message.
Value Description
D Total room tax amount is a debit.
C Total room tax amount is a credit.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, PDS 0582 must be left-justified and cannot contain all low values, all high values, all
spaces, or all zeros.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, PDS 0583 must be a fixed length of 14.
NOTE: Financial Detail Addendum/1644 messages that contain amounts and amount exponents
should utilize the same currency and exponent of the Amount, Transaction in the associated First
Presentment/1240 message.
Value Description
D Phone charges amount is a debit.
C Phone charges amount is a credit.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, PDS 0584 must be a fixed length of 14.
NOTE: Financial Detail Addendum/1644 messages that contain amounts and amount exponents
should utilize the same currency and exponent of the Amount, Transaction in the associated First
Presentment/1240 message.
Value Description
D Restaurant charges amount is a debit.
C Restaurant charges amount is a credit.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, PDS 0585 must be a fixed length of 14.
NOTE: Financial Detail Addendum/1644 messages that contain amounts and amount exponents
should utilize the same currency and exponent of the Amount, Transaction in the associated First
Presentment/1240 message.
Value Description
D Mini-Bar charges amount is a debit.
C Mini-Bar charges amount is a credit.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, PDS 0586 must be a fixed length of 14.
NOTE: Financial Detail Addendum/1644 messages that contain amounts and amount exponents
should utilize the same currency and exponent of the Amount, Transaction in the associated First
Presentment/1240 message.
Value Description
D Gift Shop charges amount is a debit.
C Gift Shop charges amount is a credit.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, PDS 0587 must be a fixed length of 14.
NOTE: Financial Detail Addendum/1644 messages that contain amounts and amount exponents
should utilize the same currency and exponent of the Amount, Transaction in the associated First
Presentment/1240 message.
Value Description
D Laundry and Dry Cleaning charges amount is a debit.
C Laundry and Dry Cleaning charges amount is a credit.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
PDS 0588 must be a length of 017–102, and it must be divisible by a minimum occurrence
length of 017.
NOTE: Financial Detail Addendum/1644 messages that contain amounts and amount exponents
should utilize the same currency and exponent of the Amount, Transaction in the associated First
Presentment/1240 message.
Value Description
D Other Services charges amount is a debit.
Value Description
C Other Services charges amount is a credit.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
PDS 0589 must be a fixed length of 12.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, PDS 0590 must be a fixed length of 02 and contain one of the values listed in this
table.
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
Attributes
Justification: Left
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
PDS 0592 contains from one to six occurrences of party address information. The PDS must be
a length of 040–240 and must be divisible by minimum occurrence length of 040.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
PDS 0593 must be a length of 025–046.
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 values, all spaces, or all zeros.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
PDS 0594 must be a length of 061–305 and must be divisible by minimum occurrence length of
061.
Value Description
1 Name
2 Title
Value Description
3 Telephone
4 E-mail address
5 Function
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS must be present in the associated Financial Detail Addendum (Corporate Card
Common Data Requirements)/1644 message for First Presentment/1240 transactions
submitted with this criteria:
• DE 43 (Acceptor Name/Location), subfield 6 (Acceptor Country Code) equals USA.
• DE 3 (Processing Code), subfield 1 (Cardholder Transaction Type) equals 00 (Purchase
[Goods and Services]) or 18 (Unique).
• The GCMS Product ID associated with DE 2 (Primary Account Number) is a corporate
product.
Requirements
This requirement applies to corporate card transactions conducted with a U.S.-based merchant
or acceptor.
PDS 0595, subfield 5, value of R (Acceptor refused to provide business type), is only valid with
transactions submitted for the interchange programs listed in this table.
IRD Description
Interregional Interchange Programs
61 Interregional Commercial Standard
63 Interregional Commercial Purchasing Standard
IP Interregional Commercial Premium Standard
LD Interregional Regulated POS Debit
LF Interregional Regulated POS Debit with Fraud Adjustment
LS Interregional Regulated POS Debit Small Ticket
LT Interregional Regulated POS Debit Small Ticket with Fraud
Adjustment
U.S. region Consumer Interchange Programs
LD Regulated POS Debit
LF Regulated POS Debit with Fraud Adjustment
LS Regulated POS Debit Small Ticket
LT Regulated POS Debit Small Ticket with Fraud Adjustment
U.S. region Commercial Interchange Programs
65 Commercial Standard
SK Business Level 2 Standard
3K Business Level 3 Standard
IRD Description
4K Business Level 4 Standard
Values
If present, PDS 0595 must be a fixed length of 8.
Value of 2 (Not known), in Subfield 1 is not permitted for commercial card transactions
conducted with a U.S.-based acceptor, unless submitted for a Standard interchange program.
Value R (Acceptor refused to provide business type) is permitted in Subfield 5 for commercial
card transactions conducted with a U.S.-based acceptor, only when submitted for a Standard
interchange program.
If Subfield 5 contains the value R (Acceptor refused to provide business type), Subfield 1 must
contain the value 2 (Not known) for commercial card transactions conducted with a U.S.-based
acceptor, when submitted for a standard interchange program.
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)
9 Government Agency
Value Description
1 No application classification
2 Female business owner
3 Physically handicapped female business owner
4 Physically handicapped male business owner
0 Unknown
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
Value Description
1 African American
2 Asian Pacific American
3 Subcontinent Asian American
4 Hispanic American
5 Native American Indian
6 Native Hawaiian
Value Description
7 Native Alaskan
8 Caucasian
9 Other
0 Unknown
Value Description
Y Business type is provided.
N Business type was not provided.
R Acceptor refused to provide business type.
Value Description
Y Business owner type is provided.
N Business owner type was not provided.
R Acceptor refused to provide business type.
Value Description
Y Business certification type is provided.
Value Description
N Business certification type was not provided.
R Acceptor refused to provide business type.
Value Description
Y Business racial/ethnic type is provided.
N Business racial/ethnic type was not provided.
R Acceptor refused to provide business racial/ethnic type.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
PDS 0596 must be present in a Financial Detail Addendum (Corporate Common Card Data)/
1644 when all of these conditions exist.
• The product code is any corporate product code.
• The Acceptor Country Code (DE 43 subfield 6) equals USA.
• Financial Detail Addendum (Corporate Card Common DataThe Processing Code (DE 3,
subfield 1) is equal to 00 (Purchase [Goods and Services]), 09 (Purchase [Goods and
Services]) with Cash Back, or 18 (Unique]), 09 (Purchase [Goods and Services]) with Cash
Back, or 18 (Unique Transaction). Transaction).
• The transaction is not a reversal.
For transactions acquired outside the U.S. region, PDS 0596 must be present if the associated
First Presentment/1240 is submitted for IRD 67: Interregional Commercial Purchasing Data
Rate II.
PDS 0596 must be present in a Financial Detail Addendum (Corporate Common Card Data)/
1644 when all these conditions exist.
• The product code is MCP or MCF at a non-fuel location.
• The business service is equal to one of the values in this table.
IRD Description
26 Purchasing Large Ticket Level 1 Interchange
27 Purchasing Large Ticket Level 2 Interchange
Values
If present, PDS 0596 must be a fixed length of 21.
– 123456780–123456789
– 222222220–222222229
– 333333330–333333339
– 444444440–444444449
– 555555550–555555559
– 666666660–666666669
– 777777770–777777779
– 888888880–888888889
– 999999990–999999999
PDS 0596, subfield 1 can be spaces when one of these conditions exist.
• The transaction is submitted for the U.S. region Commercial or Interregional Commercial
standard interchange programs and PDS 0596, subfield 2 is equal to R (Refused to Provide
Acceptor Tax ID).
• PDS 0596, subfield 2 is equal to N or R.
For First Presentment/1240 messages, PDS 0596, subfield 1 must be present and cannot
contain all zeros, all nines, all spaces, all low values, or all high values for Commercial Card
transactions in and between participating countries where value-added tax (VAT) applies. The
edit validates that DE 43, subfield 6 (Acceptor Country Code) and the country code associated
with the issuer account range in DE 2 (Primary Account Number) are on the list of participating
countries. Participating VAT countries will be announced via the Operations Bulletin and
identified via the VAT Indicator in Table IP0028T1 (Country Codes) of the Mastercard Parameter
Extract (MPE).
Value Description
Y Acceptor Tax ID provided
N Acceptor Tax ID not provided
R Refused to provide Acceptor Tax ID
PDS 0596, subfield 2 must contain a value of Y when all of these conditions exist.
• The product code is any corporate product code.
• The Acceptor Country Code (DE 43 subfield 6) equals USA.
IRD Description
61 Interregional Commercial Standard
63 Interregional Commercial Purchasing Standard
IP Interregional Commercial Premium Standard
LD Interregional Regulated POS Debit
LF Interregional Regulated POS Debit with Fraud Adjustment
LS Interregional Regulated POS Debit Small Ticket
LT Interregional Regulated POS Debit Small Ticket with Fraud
Adjustment
IRD Description
LD Regulated POS Debit
LF Regulated POS Debit with Fraud Adjustment
LS Regulated POS Debit Small Ticket
LT Regulated POS Debit Small Ticket with Fraud Adjustment
IRD Description
65 U.S. region Commercial Standard
SK Business Level 2 Standard
3K Business Level 3 Standard
4K Business Level 4 Standard
For First Presentment/1240 messages, PDS 0596, subfield 2 must be present for Commercial
Card transactions in and between participating countries where value-added tax (VAT) applies.
The edit validates that DE 43, subfield 6 (Acceptor Country Code) and the country code
associated with the issuer account range in DE 2 (Primary Account Number) are on the list of
participating countries. Participating VAT countries will be announced via the Operations
Bulletin and identified via the VAT Indicator in Table IP0028T1 (Country Codes) of the MPE.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS is allowed on First Presentment messages for Maestro® (MSI) transactions only. This
field will not be submitted to the transaction receiver if provided on a First Presentment/1240
for transactions other than Maestro.
This PDS is required for the Financial Detail Addendum (Shipping/Courier Services)/1644 when
the following occurs.
• The transaction is submitted for Commercial Data Rate III (IRD66), Commercial Large Ticket
I (IRD 62), Commercial Large Ticket II (IRD 94), or Commercial Large Ticket III (IRD 99).
• One of these MCCs is present in DE 26 (Acceptor Business Code [MCC]).
– 4214 Motor Freight Carriers, Trucking-Local/Long Distance, Moving and Storage
Companies, Local Delivery
– 4215 Courier Services: Air and Ground, Freight Forwards.
• The Financial Detail Addendum (Corporate Line Item Detail)/1644 message is not present.
This PDS is required in a Financial Detail Addendum (Corporate Card Common Data
Requirements)/1644 message if the associated First Presentment/1240 message 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
BQ Canada Intracountry Commercial Data Rate I
IRD Description
BR Canada Intracountry Commercial Data Rate II
BS Canada Intracountry Commercial Large Ticket
IRD Description
3B Business Level 3 Data Rate II
3D Business Level 3 Face-to-face
4B Business Level 4 Data Rate II
4D Business Level 4 Face-to-face
60 Commercial Face-to-Face
62 Commercial Large Ticket I
66 Commercial Data Rate III
67 Commercial Data Rate II
67 Interregional Commercial Purchasing Data Rate II
82 Electronic Payment Account
94 Commercial Large Ticket II
99 Commercial Large Ticket III
E1 Commercial Large Ticket Rate 1 MPG
E2 Commercial Large Ticket Rate 2 MPG
E3 Commercial Large Ticket Rate 3 MPG
F2 Commercial Fleet Data Rate II
F3 Commercial Fleet Data Rate III
FL Commercial Fleet Large Ticket
SB Business Level 2 Data Rate II
SD Business Level 2 Face-to-face
PDS 0597 must be present in a Financial Detail Addendum (Corporate Common Card Data)/
1644 when all the following conditions exist:
• The product code is MCP or MCF at a non-fuel location.
• The Business Service is equal to one of the values in this table.
Business services
The IRD submitted in the associated First Presentment/1240 is one of the values in this table.
IRD Description
26 Purchasing Large Ticket Level 1 Interchange
27 Purchasing Large Ticket Level 2 Interchange
Indicators in subfield 1 of these PDSs are used to reflect the collection of the individual tax
amounts that are summarized in PDS 0597:
• PDS 0682 (Detail Tax Amount 1)
• PDS 0683 (Detail Tax Amount 2)
• PDS 0684 (Detail Tax Amount 3)
• PDS 0751 (Detail Tax Amount 4)
• PDS 0752 (Detail Tax Amount 5), and
• PDS 0753 (Detail Tax Amount 6).
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.
PDS 0597 is submitted when PDS 0682, PDS 0683, PDS 0684, PDS 0751, PDS 0752, or PDS
0753 are submitted in the transaction.
Values
If present, PDS 0597 must be a fixed length of 014.
IRD Description
3B Business Level 3 Data Rate II
3D Business Level 3 Face-to-face
4B Business Level 4 Data Rate II
4D Business Level 4 Face-to-face
60 U.S. region Commercial Face-to-Face
67 U.S. region Commercial Data Rate II
F2 Commercial Fleet Data Rate II
SB Business Level 2 Data Rate II
SD Business Level 2 Face-to-face
• For the interchange programs listed in this table, the value must be 0.1 percent to 30 percent
of the value in DE 4 unless PDS 0686 is present.
IRD Description
BQ Canada Intracountry Commercial Data Rate I
BR Canada Intracountry Commercial Data Rate II
BS Canada Intracountry Commercial Large Ticket
NOTE: Financial Detail Addendum/1644 messages that contain amounts and amount exponents
should utilize the same currency and exponent of the Amount, Transaction in the associated First
Presentment/1240 message.
Value Description
D Total tax amount is a debit.
C Total tax amount is a credit.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, this PDS cannot contain all low values or high values. It must contain one of the
values listed in this table.
Value Description
Y Sales tax is included in the total purchase amount.
N or zero The acceptor has the ability to provide tax amount, but goods/
services were not taxable.
space The information is unknown.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, PDS 0599 must be left-justified and cannot contain all low values, all high values, all
spaces, or all zeros. It must be a length of 001–020.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
PDS 0600 must be present in a Financial Detail Addendum (Corporate Common Card Data)/
1644 when all these conditions exist.
• The product code is MCP or MCF at a non-fuel location.
• The Business Service is equal to one of the values in this table.
The IRD submitted in the associated First Presentment/1240 is one of the values in this table.
IRD Description
26 Purchasing Large Ticket Level 1 Interchange
27 Purchasing Large Ticket Level 2 Interchange
Values
If present, PDS 0600 must be left-justified and cannot contain all low values, high values, all
spaces, or all zeros.
Attributes
Subfields: None
Justification: N/A
Usage
This table shows the usage of PDS 0601 (whether it is mandatory, conditional, optional,
system-provided, or not required) in applicable messages.
Usage
Values
If present, PDS 0601 must be a fixed length of 001 and contain one of the values listed in this
table.
Value Description
P Invoice printed and given to purchaser and then used for tax reclaim
S Invoice printed but treated as supplemental 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
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
PDS 0602 must be a length of 084–672 and must be divisible by minimum occurrence length of
084.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
PDS 0603 must be a length of 084–672 and must be divisible by minimum occurrence length of
084.
Attributes
Occurrences: 1–8
Justification: See “Subfields”
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
PDS 0604 may contain from one to eight occurrences of Transaction Supplemental Data. Each
occurrence consists of three subfields. Each occurrence must be a length of 084–672 and must
be divisible by minimum occurrence length of 084.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Value Description
D Freight amount is a debit.
C Freight amount is a credit.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, PDS 0607 must be a fixed length of 014.
Value Description
D Duty amount is a debit.
C Duty amount is a credit.
Attributes
Subfields: None
Justification: Left
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
PDS 0608 should be provided by U.S. acceptors for all commercial card transactions in which
goods were shipped. All goods in a transaction must be shipped to one location.
Values
If present, PDS 0608 must be left-justified and cannot contain all low values, all high values, all
spaces, or all zeros.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS should be provided by U.S. acceptors for all commercial card transactions in which
goods were shipped. When this PDS is used, all goods in a transaction must be shipped to one
location.
Values
If present, PDS 0609 must contain a valid U.S. state code if PDS 0610 (Destination Country
Code) contains USA.
If the destination is a U.S. territory (Guam, Puerto Rico, or Virgin Islands), customers should
provide the three-position country code (GUM, PRI, or VIR) in both PDS 0609 and PDS 0610.
If present, PDS 0609 must be left-justified and cannot contain all low values, all high values, all
spaces, or all zeros.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS should be provided by U.S. acceptors for all commercial card transactions in which
goods were shipped. When this PDS is used, all goods in a transaction must be shipped to one
location.
Values
If present, PDS 0610 must contain a valid alphabetic ISO country code.
When territories have a defined country code in Chapter 2 of the Quick Reference Booklet, that
country code must be used.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, this PDS must be left-justified and cannot contain all zeros, all spaces, all high values,
or all low values.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, PDS 0612 must be a valid date in the format YYMMDD. PDS 0612 must be numeric
and be a fixed length of 006.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
For transactions acquired in the U.S. region, PDS 0613, if present, must contain either five
numeric characters and be left-justified and spaced filled, or the ZIP+four nine numeric
characters with a hyphen between the fifth and sixth numeric character.
This PDS should be provided by U.S. acceptors for all commercial card transactions in which
goods were shipped. When this PDS is used, all goods in a transaction must be shipped from one
location.
Values
If present, PDS 0613 must be left-justified and cannot contain all low values, all high values, all
spaces, or all zeros.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, PDS 0614 must contain a valid date in the format YYMMDD.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
PDS 0615 must be a length of 001–040. If present, PDS 0615 must be left-justified and cannot
contain all low values, all high values, all spaces, or all zeros.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
PDS 0616 must be a length of 001–040. If present, PDS 0616 must be left-justified and cannot
contain all low values, all high values, all spaces, or all zeros.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, PDS 0617 must be a fixed length of 001 and contain one of the values listed in this
table.
Values
Value Description
A Price Adjustment
B Original
C Credit
D Rebill
Attributes
Justification: N/A
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, PDS 0618 must be a fixed length of 002 and contain one of the values listed in this
table.
Values
Value Description
01 HIBCC (Health Industry Business Communication Council)
02 UCC (Uniform Code Council)
03 Other
Attributes
Justification: Left
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
PDS 0619 must be a length of 001–040. If present, PDS 0619 must be left-justified and cannot
contain all low values, all high values, all spaces, or all zeros.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
IRD Description
16 Warehouse Tier I
62 Commercial Large Ticket I
67 Commercial Data Rate II
68 Commercial Data Rate I
91 Warehouse Base
94 Commercial Large Ticket II
99 Commercial Large Ticket III
F1 Commercial Fleet Data Rate I
F2 Commercial Fleet Data Rate II
FL Commercial Fleet Large Ticket
Values
If present, PDS 0620 must contain a valid value.
Oil company brand name codes are added periodically in support of the Mastercard Corporate
Fleet Card® program. New oil company brand name codes are announced and listed in a Global
Operations Bulletin. All oil company brand name codes are documented in the Fleet
Implementation Guide.
If the AB Code (MCC) is 5552 (Electric Vehicle Charging) then acquirers should populate PDS
0620 with 9999 (Unbranded/Unassigned) unless there is a valid Oil Company Brand Name that
can be associated with the transaction.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
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 IRD BQ: Canada Intracountry
Commercial Data Rate I or one of the following incentive interchange rate programs
IRD Description
16 Warehouse Tier I
62 Commercial Large Ticket I
67 Commercial Data Rate II
68 Commercial Data Rate I
91 Warehouse Base
IRD Description
94 Commercial Large Ticket II
99 Commercial Large Ticket III
F1 Commercial Fleet Data Rate I
F2 Commercial Fleet Data Rate II
FL Commercial Fleet Large Ticket
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.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
The motor fuel service type must be present and contain a valid value in the Financial Detail
Addendum (Corporate Fleet Transaction Information)/1644 message when it is a Mastercard
Corporate Fleet Card® (MCF, MNF, MGF) when these transactions are submitted with a fuel
MCC (4468, 5541, 5499, 5552 or 5983) for any U.S.-acquired commercial interchange rate
program.
IRD Description
16 Warehouse Tier I
62 Commercial Large Ticket I
67 Commercial Data Rate II
68 Commercial Data Rate I
91 Warehouse Base
94 Commercial Large Ticket II
99 Commercial Large Ticket III
F1 Commercial Fleet Data Rate I
F2 Commercial Fleet Data Rate II
FL Commercial Fleet Large Ticket
If the Motor Fuel Service (PDS 0622) type equals 3 (only non-fuel items being purchased) on the
Fleet Transaction Information Addendum, these PDSs are required on the Financial Detail
Addendum (Corporate Line Item Detail)/1644 messages when the purchase is with a
Mastercard Corporate Fleet Card® (MCF, MPK, MGF, MNF) at fuel locations (MCC 4468, 5541,
5499, and 5983) and the transaction is submitted with one of the following U.S. region
incentive interchange rate programs.
• PDS 0641 (Product Code)
• PDS 0642 (Item Description)
• PDS 0643 (Item Quantity)
• PDS 0645 (Item Unit of Measure)
IRD Description
16 Warehouse Tier I
62 Commercial Large Ticket I
67 Commercial Data Rate II
68 Commercial Data Rate I
91 Warehouse Base
94 Commercial Large Ticket II
99 Commercial Large Ticket III
If PDS 0622 (Motor Fuel Service Type) equals 3 (only non-fuel items being purchased) on the
Fleet Transaction Information Addendum, these PDSs are required on the Financial Detail
Addendum (Corporate Line Item Detail)/1644 messages when the purchase is with a
Mastercard Corporate Fleet Card (MCF and MGF) at fuel locations (MCC 4468, 5541, 5499,
5552, and 5983) and the transaction is submitted with one of the following U.S. region
incentive interchange rate programs.
• PDS 0783 (Fleet Product Code)
• PDS 0784 (Fleet Item Description)
• PDS 0785 (Fleet Item Quantity)
• PDS 0786 (Fleet Item Unit of Measure)
• PDS 0787 (Fleet Extended Item Amount)
IRD Description
F1 Commercial Fleet Data Rate I
F2 Commercial Fleet Data Rate II
Fl Commercial Fleet Large Ticket
purchased), these PDSs are required in Financial Detail Addendum (Corporate Line Item Detail)/
1644 messages:
• PDS 0641 (Product Code)
• PDS 0642 (Item Description)
• PDS 0643 (Item Quantity)
• PDS 0645 (Item Unit of Measure)
• PDS 0646 (Unit Price)
• PDS 0647 (Extended Item Amount), and
• PDS 0654 (Debit or Credit Indicator).
Values
GCMS does not edit this subfield. If present, this PDS must contain a value listed in this table.
Value Description
0 or space Undefined
1 Self-service
2 Full service
3 Only non-fuel products being purchased
PDS 622 must contain a value of 1 or 2 when submitted with fleet card transactions submitted
with an acceptor business code (MCC) equal to 5542.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
IRD Description
16 Warehouse Tier I
62 Commercial Large Ticket I
67 Commercial Data Rate II
68 Commercial Data Rate I
91 Warehouse Base
94 Commercial Large Ticket II
99 Commercial Large Ticket III
Values
If present, PDS 0623 Motor Fuel Information must be a fixed length of 35.
Requirements
These are the requirements regulating the use of PDS 0623:
• PDS 0623 (Motor Fuel Information) must be present when these conditions are met:
– DE 2 Primary Account Number in the associated First Presentment/1240 message
contains a Fleet account range.
– DE 26 Acceptor Business Code (MCC) in the associated First Presentment/1240 is 5541
or 5542.
– PDS 0622 Motor Fuel Service Type is present and contains a value of 1 (Self-service) or 2
(Full service).
– PDS 0158s4 Interchange Rate Designator is applicable.
• PDS 0623 (Motor Fuel Information) is allowed on First Presentment/1240 messages for
Mastercard Credit (MCC), Maestro® (MSI) and Private Label (PVL) transactions only. This
field will not be submitted to the transaction receiver if provided on a First Presentment/
1240 for transactions other than Mastercard Credit, Maestro® or Private Label.
• For Mastercard Corporate Fleet Card® transactions, PDS 0623, subfield 6 (Motor Fuel Sale
Amount) must equal the product of the value of PDS 0623, subfield 2 (Motor Fuel Unit Price)
multiplied by the value in PDS 0623, subfield 4 (Motor Fuel Quantity). A tolerance of five
percent is permitted to address rounding issues. The tolerance is applied on PDS 0623,
subfield 6 (Sale Amount) and not on the calculated value (PDS 0623, subfield 2 multiplied by
PDS 0623, subfield 4). Also, this edit does not round the calculated amount and low/high
tolerance amounts to the transaction currency exponent, and keeps six decimal positions on
these values.
Value Description
001 Unleaded Regular (86 or 87 octane)
002 Unleaded Mid Grade (88 or 89 octane)
003 Unleaded Premium (90 or 91 octane)
004 Unleaded Super (92–94 octane)
005 Methanol Unleaded Regular (86 or 87 octane)
006 Methanol Unleaded Mid Grade (88 or 89 octane)
007 Methanol Unleaded Premium (90 or 91 octane)
008 Methanol Unleaded Super (92–94 octane)
009 Methanol Regular Leaded
011 Regular Leaded Gasoline
012 Diesel
013 Diesel Premium
014 Kerosene
015 LPG
016 Compressed Natural Gas
017 M85 (Methanol 85 percent)
018 E85 (Ethanol 85 percent)
019 Ethanol Unleaded Regular (86 or 87 octane)
020 Ethanol Unleaded Mid Grade (88 or 89 octane)
021 Ethanol Unleaded Premium (90 or 91 octane)
022 Ethanol Unleaded Super (92–94 octane)
023 Ethanol Regular Leaded
024 Unleaded Reformulated (86 or 87 octane)
025 Unleaded Mid Grade Reformulated (88 or 89 octane)
026 Dyed Diesel
027 Gasohol
028 Biodiesel
029 Ultra Low Sulfur Diesel (ULSD)
100 Aviation 100 Octane
Value Description
101 Jet Fuel
102 Aviation Fuel
150 Marine Fuel
200 Miscellaneous Fuel
201 Liquid Natural Gas
202 White Gas
203 Racing Fuel
204 Electric Vehicle Charge Level 1: 110v
205 Electric Vehicle Charge Level 2: 240v
206 Electric Vehicle Charge Level 3: 480v
207 Biodiesel (Non-Taxable)
208 Diesel (Non-Taxable)
209 Diesel Exhaust Fluid: Dispensed
Value Description
1 Gallons
2 Liters
3 Pounds
4 Kilos
5 Imperial gallons
6 Kilowatt hour
Value Description
7 Minutes
8 Hours
space Not applicable
Attributes
Justification: Left
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
PDS 0624 must be a length of 001–040. If present, PDS 0624 must be left-justified and cannot
contain all low values, all high values, all spaces, or all zeros.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
PDS 0625 must be a length of 001–025. If present, PDS 0625 must be left-justified and cannot
contain all low values, all high values, all spaces, or all zeros.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
PDS 0626 must be a fixed length of 012.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
PDS 0627 must be a length of 54–540, and it must be divisible by a minimum occurrence length
of 54.
Value Description
D Billing Event amount 2 is a debit.
C Billing Event amount 2 is a credit.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
PDS 0628 must be a length of 54–540, and it must be divisible by a minimum occurrence length
of 54.
Value Description
D Billing event amount 2 is a debit.
C Billing event amount 2 is a credit.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS is allowed on First Presentment messages for Maestro® (MSI) transactions only. This
field will not be submitted to the transaction receiver if provided on a First Presentment/1240
for transactions other than Maestro®.
This PDS is required if these conditions occur:
• PDS 0632 (Product Type Code) contains a value in the range 1–4.
• The associated First Presentment/1240 is a Mastercard Corporate Fleet Card® transaction
at a fuel location and is submitted for IRD BQ: Canada Intracountry Commercial Data Rate I.
IRD Description
16 Warehouse Tier I
62 Commercial Large Ticket 1
67 Commercial Data Rate II
91 Warehouse Base
94 Commercial Large Ticket II
99 Commercial Large Ticket III
Values
If present, PDS 0629 must be left-justified and cannot contain all low values, all high values, all
spaces, or all zeros.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
IRD Description
16 Warehouse Tier I
62 Commercial Large Ticket 1
67 Commercial Data Rate II
91 Warehouse Base
94 Commercial Large Ticket II
99 Commercial Large Ticket III
When the transaction is a Mastercard Corporate Fleet Card® (MCF, MPK, MNF, or MGF)
transaction at a fuel location MCC (4468, 5541, 5542, 5499, or 5983), and was submitted for
one of the above interchange programs (BQ, 16, 62, 67, 91, 94, and 99), PDS 0632 (Product
Type Code) is present and contains one of these values:
• 1 (Prompts for ID number and odometer reading)
• 2 (Prompts for vehicle number and odometer reading), or
• 3 (Prompts for driver number and odometer reading).
The data in the Authorization Request/0100 message matches this data in the Corporate Fleet
Transaction Information Addendum/1644:
• Driver ID: CIS DE 48 (Additional Data, Private Use), subelement 98 (Mastercard Corporate
Fleet Card ID/ Driver Number) and IPM PDS 0631 (Driver Number/ID Number)
• Driver Number: CIS DE 48, subelement 98 (Mastercard Corporate Fleet Card ID/Driver
Number) and IPM PDS 0631 (Driver Number/ID Number)
• Vehicle Number: CIS DE 48, subelement 99 (Mastercard Corporate Fleet Card Vehicle
Number) and IPM PDS 0630 (Vehicle Number).
When the data requirements are not met, the transaction is downgraded to IRD 68 (Business
Core Value Data Rate 1) through Mastercard® Interchange Compliance.
Values
If present, PDS 0630 must be left-justified and cannot contain all low values, all high values, all
spaces, or all zeros.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
IRD Description
16 Warehouse Tier I
62 Commercial Large Ticket 1
67 Commercial Data Rate II
91 Warehouse Base
94 Commercial Large Ticket II
99 Commercial Large Ticket III
When the transaction is a Mastercard Corporate Fleet Card® (MCF, MPK, MNF, or MGF)
transaction at a fuel location MCC (4468, 5541, 5542, 5499, or 5983), and was submitted for
one of the above interchange programs (BQ, 16, 62, 67, 91, 94, and 99), PDS 0632 (Product
Type Code) is present and contains one of these values.
• 1 (Prompts for ID number and odometer reading)
• 2 (Prompts for vehicle number and odometer reading)
• 3 (Prompts for driver number and odometer reading)
The data in the Authorization Request/0100 message matches the data in the Corporate Fleet
Transaction Information Addendum/1644 message as follows.
• Driver ID: CIS DE 48 (Additional Data, Private Use), subelement 98 (Mastercard Corporate
Fleet Card ID/ Driver Number) and IPM PDS 0631 (Driver Number/ID Number)
• Driver Number: CIS DE 48, subelement 98 (Mastercard Corporate Fleet Card ID/Driver
Number) and IPM PDS 0631 (Driver Number/ID Number)
• Vehicle Number: CIS DE 48, subelement 99 (Mastercard Corporate Fleet Card Vehicle
Number) and IPM PDS 0630 (Vehicle Number).
When the data requirements are not met, the transaction will be downgraded to IRD 68
(Business Core Value Data Rate 1) through Mastercard® Interchange Compliance.
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.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
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 IRD BQ: Canada Intracountry
Commercial Data Rate I.
IRD Description
16 World Small Ticket Card Present
62 Commercial Large Ticket I
67 Commercial Data Rate II
91 Warehouse Base
IRD Description
94 Commercial Large Ticket II
99 Commercial Large Ticket III
When the transaction is a Mastercard Corporate Fleet Card® (MCF, MPK, MNF, or MGF)
transaction at a fuel location MCC (4468, 5541, 5542, 5499, or 5983), and was submitted for
one of the above interchange programs (BQ, 16, 62, 67, 91, 94, and 99), PDS 0632 (Product
Type Code) is present and contains one of these values:
• 1 (Prompts for ID number and odometer reading)
• 2 (Prompts for vehicle number and odometer reading), or
• 3 (Prompts for driver number and odometer reading).
The data in the Authorization Request/0100 message matches the data in the Corporate Fleet
Transaction Information Addendum/1644 message as follows.
• Driver ID: CIS DE 48 (Additional Data, Private Use), subelement 98 (Mastercard Corporate
Fleet Card ID/ Driver Number) and IPM PDS 0631 (Driver Number/ID Number)
• Driver Number: CIS DE 48, subelement 98 (Mastercard Corporate Fleet Card ID/Driver
Number) and IPM PDS 0631 (Driver Number/ID Number)
• Vehicle Number: CIS DE 48, subelement 99 (Mastercard Corporate Fleet Card Vehicle
Number) and IPM PDS 0630 (Vehicle Number).
When the data requirements are not met, the transaction will be downgraded to IRD 68
(Business Core Value Data Rate 1) through Mastercard® Interchange Compliance.
Values
If present, PDS 0632 must contain a value in the range 1–5 as shown in this table.
Values
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 IRD BQ: Canada Intracountry Commercial
Data Rate I.
IRD Description
16 World Small Ticket Card Present
62 Commercial Large Ticket I
67 Commercial Data Rate II
91 Warehouse Base
94 Commercial Large Ticket II
99 Commercial Large Ticket III
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, PDS 0633 must contain a numeric value.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, PDS 0634 must be numeric and may contain all zeros.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, PDS 0635 must be numeric and may contain all zeros.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
PDS 0636 must be a fixed length of 006. If present, PDS 0636 must be numeric and a valid date
in the format YYMMDD.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
PDS 0637 must be a fixed length of 006. If present, PDS 0637 must be numeric and a valid time
in the format HHMMSS.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
PDS 0638 must be a fixed length of 146.
Value Description
C Outgoing Call
I Incoming Call
V Voice Mail
P Page
O Other
F Toll-Free Call
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
PDS 0639 must be a fixed length of 006. If present, PDS 0639 must be numeric and should be
in the format HHMMSS.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, PDS 0640 must contain one of the values listed in this table.
Values
Value Description
PP Peak Period
OP Off-Peak Period
MP Multiple Period
OT Other
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
PDS 0641 (Product Code) must be present in the Financial Detail Addendum (Corporate Line
Item Detail)/1644 message when one of these conditions occur:
• PDS 0622 (Motor Fuel Service Type) is present with a value of 3 (Only non-fuel items being
purchased) in the Financial Detail Addendum (Corporate Fleet Transaction Information)/
1644 message.
• The associated First Presentment/1240 message is a Mastercard Corporate Fleet Card®
transaction at a fuel location MCC and is submitted for IRD BQ: Canada Intracountry
Commercial Data Rate I and PDS0622 contains value 3.
• The associated First Presentment/1240 message is a Mastercard Corporate Fleet Card®
transaction at a maintenance location MCC and is submitted for IRD BQ: Canada
Intracountry Commercial Data Rate I.
• The associated First Presentment/1240 message is a not Shipping/Courier MCC or
Temporary Services MCC and is submitted for IRD BR: Canada Intracountry Commercial
Data Rate II or IRD BS: Canada Intracountry Commercial Large Ticket.
The business service arrangement is U.S.-to-U.S. where PDS 0158, subfield 2 is equal to 2 and
PDS 0158, subfield 3 is equal to 010001.
Associated First Presentment/1240 messages should contain a fuel MCC in DE 26 (Acceptor
Business). The applicable IRDs for the First Presentment/1240 messages are listed in this table.
IRD Description
16 Commercial Warehouse Tier I
62 Commercial Large Ticket I
67 Commercial Data Rate II
68 Commercial Data Rate I
91 Commercial Warehouse Base
94 Commercial Large Ticket II
99 Commercial Large Ticket III
SC Business Level 2 Data Rate III
SE Business Level 2 Large Ticket I
SF Business Level 2 Large Ticket II
SG Business Level 2 Large Ticket III
3C Business Level 3 Data Rate III
3E Business Level 3 Large Ticket I
3F Business Level 3 Large Ticket II
3G Business Level 3 Large Ticket III
4C Business Level 4 Data Rate III
4E Business Level 4 Large Ticket I
4F Business Level 4 Large Ticket II
4G Business Level 4 Large Ticket III
PDS 0641 must be present in a Financial Detail Addendum (Corporate Line Item Detail)/1644
message when PDS 0642 (Item Description) is not present and when all of these conditions
exist:
The business service is equal to one of the values listed in this table.
Business service
The Product Code should be provided for Mastercard Corporate Fleet Card® transactions
occurring at fuel locations, when PDS 0622 (Motor Fuel Service Type) is 3 and the transactions
are submitted for any U.S.-acquired Commercial interchange rate program for which Fleet
transactions at fuel locations are valid.
PDS 0641 must be present when these conditions exist:
• The Business Service is U.S.-to-U.S. (PDS 0158, subfield 2 is equal to 2 and PDS 0158,
subfield 3 is equal to 010001).
• The associated First Presentment/1240 contains a shipping/courier MCC in DE 26 (Acceptor
Business Code [MCC]), and a Financial Detail Addendum (Shipping/Courier Services)/1644
message is not provided
• The associated First Presentment/1240 does not contain a temporary services MCC in DE
26.
• The IRD submitted in the associated First Presentment/1240 is one of the values in this
table.
IRD Description
26 Purchasing Large Ticket Level 1 Interchange
27 Purchasing Large Ticket Level 2 Interchange
62 Commercial Large Ticket I
66 Commercial Data Rate III
94 Commercial Large Ticket II
99 Commercial Large Ticket III
IRD Description
26 Purchasing Large Ticket Level 1 Interchange
27 Purchasing Large Ticket Level 2 Interchange
62 Commercial Large Ticket I
66 Commercial Data Rate III
94 Commercial Large Ticket II
99 Commercial Large Ticket III
SC Business Level 2 Data Rate III
SE Business Level 2 Large Ticket I
SF Business Level 2 Large Ticket II
SG Business Level 2 Large Ticket III
3C Business Level 3 Data Rate III
3E Business Level 3 Large Ticket I
3F Business Level 3 Large Ticket II
3G Business Level 3 Large Ticket III
4C Business Level 4 Data Rate III
4E Business Level 4 Large Ticket I
4F Business Level 4 Large Ticket II
4G Business Level 4 Large Ticket III
Field Description
PDS 0641 Product Code
PDS 0642 Item Description
PDS 0643 Item Quantity
Field Description
PDS 0645 Item Unit of Measure
PDS 0647 Extended Item Amount
PDS 0654 Debit or Credit Indicator
Values
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 should be provided and must contain a three-position non-fuel product
code in the range 030–099 or 300–999.
Values
Value Description
030 Motor Oil
031 Oil Change
032 Engine Service
033 Transmission Service
034 Brake Service
035 Solvent
036 Brake Fluid
037 Miscellaneous Parts
038 Miscellaneous Labor
039 Miscellaneous Repairs
040 TBA (tire, batteries, accessories)
041 Tires
042 Batteries
043 Automotive Accessories
044 Automotive Glass
045 Car Wash
046 Towing
047 Diesel Exhaust Fluid
070 Cigarettes/Tobacco
Value Description
078 Health/Beauty Aid
079 Miscellaneous Food/Grocery
080 Soda
081 Beer/Wine
082 Milk/Juice
083 Restaurant
089 Miscellaneous Beverage
099 Miscellaneous Other
300 Aviation Maintenance
301 De-icing
302 APU or Aircraft Jump Start
303 Aviation Catering
304 Tiedown or Hangar
305 Landing Fee
306 Ramp Fee
307 Call Out Fee
308 Plane Rental
309 Instruction Fee
310 Miscellaneous Aviation
311 Flight Planning/Weather Fees
312 Charter Fees
313 Ground Handling
314 Communications Fees
315 Aircraft Cleaning
316 Cargo Handling
317 Aviation Accessories
350 Boat Service
Product codes
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.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
PDS 0642 (Item Description) must be present in the Financial Detail Addendum (Corporate Line
Item Detail)/1644 message when one of these conditions occur:
• PDS 0622 (Motor Fuel Service Type) is present with a value of 3 (Only non-fuel items being
purchased) in the Financial Detail Addendum (Corporate Fleet Transaction Information)/
1644 message.
• The associated First Presentment/1240 message is a Mastercard Corporate Fleet Card®
transaction at a fuel location MCC and is submitted for IRD BQ: Canada Intracountry
Commercial Data Rate I and PDS0622 contains value 3.
• The associated First Presentment/1240 message is a Mastercard Corporate Fleet Card®
transaction at a maintenance location MCC and is submitted for IRD BQ: Canada
Intracountry Commercial Data Rate I.
• The associated First Presentment/1240 message is a not Shipping/Courier MCC or
Temporary Services MCC and is submitted for IRD BR: Canada Intracountry Commercial
Data Rate II or IRD BS: Canada Intracountry Commercial Large Ticket.
The business service arrangement is U.S.-to-U.S. where PDS 0158, subfield 2 is equal to 2 and
PDS 0158, subfield 3 is equal to 010001.
Associated First Presentment/1240 messages should contain a fuel MCC in DE 26 (Acceptor
Business). The applicable IRDs for the First Presentment/1240 messages are listed in this table.
IRD Description
16 Commercial Warehouse Tier I
62 Commercial Large Ticket I
67 Commercial Data Rate II
68 Commercial Data Rate I
91 Commercial Warehouse Base
94 Commercial Large Ticket II
99 Commercial Large Ticket III
SC Business Level 2 Data Rate III
SE Business Level 2 Large Ticket I
SF Business Level 2 Large Ticket II
SG Business Level 2 Large Ticket III
3C Business Level 3 Data Rate III
3E Business Level 3 Large Ticket I
3F Business Level 3 Large Ticket II
3G Business Level 3 Large Ticket III
4C Business Level 4 Data Rate III
IRD Description
4E Business Level 4 Large Ticket I
4F Business Level 4 Large Ticket II
4G Business Level 4 Large Ticket III
The IRD submitted in the associated First Presentment/1240 is one of the values listed in this
table.
IRD Description
26 Purchasing Large Ticket Level 1 Interchange
IRD Description
27 Purchasing Large Ticket Level 2 Interchange
IRD Description
62 Commercial Large Ticket I
66 Commercial Data Rate III
94 Commercial Large Ticket II
99 Commercial Large Ticket III
IRD Description
62 Commercial Large Ticket I
66 Commercial Data Rate III
94 Commercial Large Ticket II
99 Commercial Large Ticket III
Field Description
PDS 0641 Product Code
PDS 0642 Item Description
PDS 0643 Item Quantity
PDS 0645 Item Unit of Measure
PDS 0647 Extended Item Amount
PDS 0654 Debit or Credit Indicator
Values
PDS 0642 must be left-justified and cannot contain all spaces, all zeros, all low values, or all high
values.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
PDS 0643 (Item Quantity) must be present in the Financial Detail Addendum (Corporate Line
Item Detail)/1644 message when one of these conditions occur:
• PDS 0622 (Motor Fuel Service Type) is present with a value of 3 (Only non-fuel items being
purchased) in the Financial Detail Addendum (Corporate Fleet Transaction Information)/
1644 message.
• The associated First Presentment/1240 message is a Mastercard Corporate Fleet Card®
transaction at a fuel location MCC and is submitted for IRD BQ: Canada Intracountry
Commercial Data Rate I and PDS0622 contains value 3.
• The associated First Presentment/1240 message is a Mastercard Corporate Fleet Card®
transaction at a maintenance location MCC and is submitted for IRD BQ: Canada
Intracountry Commercial Data Rate I.
• The associated First Presentment/1240 message is a not Shipping/Courier MCC or
Temporary Services MCC and is submitted for IRD BR: Canada Intracountry Commercial
Data Rate II or IRD BS: Canada Intracountry Commercial Large Ticket.
The business service arrangement is U.S.-to-U.S. where PDS 0158, subfield 2 is equal to 2 and
PDS 0158, subfield 3 is equal to 010001.
Associated First Presentment/1240 messages should contain a fuel MCC in DE 26 (Acceptor
Business Code). The applicable IRDs for the First Presentment/1240 messages are listed in this
table.
IRD Description
16 Commercial Warehouse Tier I
62 Commercial Large Ticket I
67 Commercial Data Rate II
68 Commercial Data Rate I
91 Commercial Warehouse Base
IRD Description
94 Commercial Large Ticket II
99 Commercial Large Ticket III
SC Business Level 2 Data Rate III
SE Business Level 2 Large Ticket I
SF Business Level 2 Large Ticket II
SG Business Level 2 Large Ticket III
3C Business Level 3 Data Rate III
3E Business Level 3 Large Ticket I
3F Business Level 3 Large Ticket II
3G Business Level 3 Large Ticket III
4C Business Level 4 Data Rate III
4E Business Level 4 Large Ticket I
4F Business Level 4 Large Ticket II
4G Business Level 4 Large Ticket III
PDS 0643 must be present in a Financial Detail Addendum (Corporate Line Item Detail)/1644
message when all these conditions exist:
• The product code is MCP or MCF at a non-fuel location.
• The business service is equal to one of the values listed in this table.
The IRD submitted in the associated First Presentment/1240 is one of the values listed in this
table.
IRD Description
26 Purchasing Large Ticket Level 1 Interchange
27 Purchasing Large Ticket Level 2 Interchange
IRD Description
62 Commercial Large Ticket I
66 Commercial Data Rate III
94 Commercial Large Ticket II
99 Commercial Large Ticket III
IRD Description
62 Commercial Large Ticket I
66 Commercial Data Rate III
IRD Description
94 Commercial Large Ticket II
99 Commercial Large Ticket III
Field Description
PDS 0641 Product Code
PDS 0642 Item Description
PDS 0643 Item Quantity
PDS 0645 Item Unit of Measure
PDS 0647 Extended Item Amount
PDS 0654 Debit or Credit Indicator
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
PDS 0644 must be a fixed length of 145.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
PDS 0645 (Item Unit of Measure) must be present in the Financial Detail Addendum (Corporate
Line Item Detail)/1644 message when one of these conditions occur:
• PDS 0622 (Motor Fuel Service Type) is present with a value of 3 (Only non-fuel items being
purchased) in the Financial Detail Addendum (Corporate Fleet Transaction Information)/
1644 message.
• The associated First Presentment/1240 message is a Mastercard Corporate Fleet Card®
transaction at a fuel location MCC and is submitted for IRD BQ: Canada Intracountry
Commercial Data Rate I and PDS0622 contains value 3.
IRD Description
16 Commercial Warehouse Tier I
62 Commercial Large Ticket I
67 Commercial Data Rate II
68 Commercial Data Rate I
91 Commercial Warehouse Base
94 Commercial Large Ticket II
99 Commercial Large Ticket III
SC Business Level 2 Data Rate III
SE Business Level 2 Large Ticket I
SF Business Level 2 Large Ticket II
SG Business Level 2 Large Ticket III
3C Business Level 3 Data Rate III
3E Business Level 3 Large Ticket I
3F Business Level 3 Large Ticket II
3G Business Level 3 Large Ticket III
4C Business Level 4 Data Rate III
4E Business Level 4 Large Ticket I
4F Business Level 4 Large Ticket II
4G Business Level 4 Large Ticket III
IRD Description
62 Commercial Large Ticket I
66 Commercial Data Rate III
94 Commercial Large Ticket II
99 Commercial Large Ticket III
IRD Description
62 Commercial Large Ticket I
66 Commercial Data Rate III
94 Commercial Large Ticket II
99 Commercial Large Ticket III
Field Description
PDS 0641 Product Code
PDS 0642 Item Description
PDS 0643 Item Quantity
PDS 0645 Item Unit of Measure
PDS 0647 Extended Item Amount
PDS 0654 Debit or Credit Indicator
Values
If present, PDS 0645 cannot contain all low values, all high values, all zeros, or all spaces.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
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.
When a Financial Detail Addendum (Corporate Line Item Detail)/1644 is submitted in
conjunction with a Financial Detail Addendum (Temporary Services)/1644 message, PDS 0646
should contain a value of 1.
When a Financial Detail Addendum (Corporate Line Item Detail)/1644 is submitted in
conjunction with a Financial Detail Addendum (Shipping/Courier Services)/1644 message, PDS
0646 should contain a value of 1.
PDS 0646 must be present in the Financial Detail Addendum (Corporate Line Item Detail)/1644
message when one of these conditions occur:
• The associated First Presentment/1240 message is a Mastercard Corporate Fleet Card®
transaction at a fuel location MCC and is submitted for IRD BQ: Canada Intracountry
Commercial Data Rate I and PDS0622 contains value 3.
• The associated First Presentment/1240 message is a Mastercard Corporate Fleet Card®
transaction at a maintenance location MCC and is submitted for IRD BQ: Canada
Intracountry Commercial Data Rate I.
• The associated First Presentment/1240 message is a not Shipping/Courier MCC or
Temporary Services MCC and is submitted for IRD BR: Canada Intracountry Commercial
Data Rate II or IRD BS: Canada Intracountry Commercial Large Ticket.
• The product code is MCP or MCF at a non-fuel location.
• The Business Service is equal to one of the values in this table.
The IRD submitted in the associated First Presentment/1240 is one of the values listed in this
table.
IRD Description
26 Purchasing Large Ticket Level 1 Interchange
27 Purchasing Large Ticket Level 2 Interchange
Values
If present, subfield 1 must be numeric. Subfield 2 must contain a value in the range 0–5.
NOTE: Financial Detail Addendum/1644 messages that contain amounts and amount exponents
should utilize the same currency and exponent of the Amount, Transaction in the associated First
Presentment/1240 message.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
PDS 0647 must be present in the Financial Detail Addendum (Corporate Line Item Detail)/1644
message when PDS 0622 (Motor Fuel Service Type) is present with a value of 3 (Only non-fuel
items being purchased) in the Financial Detail Addendum (Corporate Fleet Transaction
Information)/1644 message.
The business service arrangement is U.S.-to-U.S. where PDS 0158, subfield 2 is equal to 2 and
PDS 0158, subfield 3 is equal to 010001.
IRD Description
BQ Canada Intracountry Commercial Data Rate I
BR Canada Intracountry Commercial Data Rate II
BS Canada Intracountry Commercial Large Ticket
IRD Description
16 Commercial Warehouse Tier I
62 Commercial Large Ticket I
67 Commercial Data Rate II
68 Commercial Data Rate I
91 Commercial Warehouse Base
94 Commercial Large Ticket II
99 Commercial Large Ticket III
SC Business Level 2 Data Rate III
SE Business Level 2 Large Ticket I
SF Business Level 2 Large Ticket II
SG Business Level 2 Large Ticket III
3C Business Level 3 Data Rate III
3E Business Level 3 Large Ticket I
3F Business Level 3 Large Ticket II
3G Business Level 3 Large Ticket III
4C Business Level 4 Data Rate III
4E Business Level 4 Large Ticket I
4F Business Level 4 Large Ticket II
4G Business Level 4 Large Ticket III
IRD Description
62 Commercial Large Ticket I
66 Commercial Data Rate III
94 Commercial Large Ticket II
99 Commercial Large Ticket III
IRD Description
62 Commercial Large Ticket I
66 Commercial Data Rate III
94 Commercial Large Ticket II
IRD Description
99 Commercial Large Ticket III
Required fields
Field Description
PDS 0641 Product Code
PDS 0642 Item Description
PDS 0643 Item Quantity
PDS 0645 Item Unit of Measure
PDS 0647 Extended Item Amount
PDS 0654 Debit or Credit Indicator
Values
If present, PDS 0647 must be a fixed length of 014.
To allow for situations in which the item is zero cost to the customer, PDS 0650 (Zero Cost to
Customer) must also be present in the Corporate Card Line Item Detail Addendum message,
and equal to Y. PDS 0647, subfield 1 may contain zero in this circumstance.
NOTE: Financial Detail Addendum/1644 messages that contain amounts and amount exponents
should utilize the same currency and exponent of the Amount, Transaction in the associated First
Presentment/1240 message.
Value Description
D Extended item amount is a debit.
C Extended item amount is a credit.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
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, the customer must also provide subfields 3, 4, and 5.
PDS 0648 must be present in a Financial Detail Addendum (Corporate Line Item Detail)/1644
message when all these conditions exist:
• The product code is MCP or MCF at a non-fuel location.
• The business service is equal to one of the values in this table.
The IRD submitted in the associated First Presentment/1240 is one of the values in this table.
IRD Description
26 Purchasing Large Ticket Level 1 Interchange
27 Purchasing Large Ticket Level 2 Interchange
Values
PDS 0648 must be a fixed length of 20.
Value Description
Y Amount is discounted.
N Amount is not discounted.
space Not supported
Value Description
C Item discount amount is a credit.
D Item discount amount is a debit.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
PDS 0649 must be a fixed length of 14.
Value Description
D Call Usage Amount is a debit.
C Call Usage Amount is a credit.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
PDS 0650 must contain one of the values listed in this table.
Value Description
Y The line item is at zero cost to the customer. PDS 0647 (Extended
Item Amount) and PDS 0787 (Fleet Extended Item Amount) may be
equal to zero.
N The line item is not at zero cost to the customer.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, this PDS must be left-justified and cannot contain all zeros, all spaces, all high values,
or all low values.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, PDS 0652 must not contain all high values or all low values.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
NOTE: Financial Detail Addendum/1644 messages that contain amounts and amount exponents
should utilize the same currency and exponent of the Amount, Transaction in the associated First
Presentment/1240 message.
Value Description
D Fee Amount is a debit
Value Description
C Fee Amount is a credit
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
If the Financial Detail Addendum (Corporate Line Item Detail)/1644 message is provided, PDS
0654 is mandatory.
PDS 0654 must be present in the Financial Detail Addendum (Corporate Line Item Detail)/1644
message when PDS 0622 (Motor Fuel Service Type) is present with a value of 3 (Only non-fuel
items being purchased) in the Financial Detail Addendum (Corporate Fleet Transaction
Information)/1644 message.
The business service arrangement is U.S.-to-U.S. where PDS 0158, subfield 2 is equal to 2 and
PDS 0158, subfield 3 is equal to 010001.
IRD Description
BQ Canada Intracountry Commercial Data Rate I
BR Canada Intracountry Commercial Data Rate II
BS Canada Intracountry Commercial Large Ticket
IRD Description
16 Commercial Warehouse Tier I
62 Commercial Large Ticket I
67 Commercial Data Rate II
68 Commercial Data Rate I
91 Commercial Warehouse Base
94 Commercial Large Ticket II
99 Commercial Large Ticket III
SC Business Level 2 Data Rate III
SE Business Level 2 Large Ticket I
SF Business Level 2 Large Ticket II
SG Business Level 2 Large Ticket III
3C Business Level 3 Data Rate III
3E Business Level 3 Large Ticket I
3F Business Level 3 Large Ticket II
3G Business Level 3 Large Ticket III
4C Business Level 4 Data Rate III
4E Business Level 4 Large Ticket I
4F Business Level 4 Large Ticket II
4G Business Level 4 Large Ticket III
Values
PDS 0654 must contain one of the values listed in this table.
Values
Value Description
D Extended item amount is a debit.
C Extended item amount is a credit.
IRD Description
62 Commercial Large Ticket I
66 Commercial Data Rate III
94 Commercial Large Ticket II
99 Commercial Large Ticket III
IRD Description
62 Commercial Large Ticket I
66 Commercial Data Rate III
94 Commercial Large Ticket II
99 Commercial Large Ticket III
Required fields
Field Description
PDS 0641 Product Code
PDS 0642 Item Description
PDS 0643 Item Quantity
PDS 0645 Item Unit of Measure
PDS 0647 Extended Item Amount
PDS 0654 Debit or Credit Indicator
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
PDS 0655 must be a fixed length of 14.
Value Description
D Call long distance amount is a debit.
C Call long distance amount is a credit.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
NOTE: Financial Detail Addendum/1644 messages that contain amounts and amount exponents
should utilize the same currency and exponent of the Amount, Transaction in the associated First
Presentment/1240 message.
Value Description
D Full VAT Gross Amount is a debit.
C Full VAT Gross Amount is a credit.
NOTE: Financial Detail Addendum/1644 messages that contain amounts and amount exponents
should utilize the same currency and exponent of the Amount, Transaction in the associated First
Presentment/1240 message.
Value Description
D Full VAT Tax Amount is a debit.
C Full VAT Tax Amount is a credit.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
NOTE: Financial Detail Addendum/1644 messages that contain amounts and amount exponents
should utilize the same currency and exponent of the Amount, Transaction in the associated First
Presentment/1240 message.
Value Description
D Half VAT Gross Amount is a debit.
C Half VAT Gross Amount is a credit.
NOTE: Financial Detail Addendum/1644 messages that contain amounts and amount exponents
should utilize the same currency and exponent of the Amount, Transaction in the associated First
Presentment/1240 message.
Value Description
D Half VAT Tax Amount is a debit.
C Half VAT Tax Amount is a credit.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
PDS 0658 must be a fixed length of 14.
Value Description
D Call connect amount is a debit.
C Call connect amount is a credit.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, PDS 0659 must be a length of 001–060. PDS 0659 must be left-justified, and cannot
contain all low values, all high values, all spaces, or all zeros.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, this PDS must be numeric.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, this PDS must be numeric and cannot be all zeros.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
PDS 0663 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 message. This PDS can also be used to exchange data for transactions involving consumer
cards.
Acquirers of Brazil intracountry transactions must ensure that required installment payment
data is provided in PDS 0663 of Financial Detail Addendum/1644 messages for installment
transactions. For more information, refer to the Interchange Manual: Latin America and the
Caribbean Region.
Values
If present, PDS 0663 must be left-justified and cannot contain all low values, all high values, all
spaces, or all zeros.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS is required if the associated First Presentment/1240 contains a railway MCC and is
submitted for one of the U.S. region incentive interchange rate programs listed in this table.
IRD Description
10 Merit III Tier 1
11 Merit III Tier 2
12 Merit III Tier 3
22 Public Sector
24 Merchant UCAF
29 Emerging Markets: Consumer Core Value
56 World Public Sector
69 Commercial T&E Rate II
70/80 Merit III Base
79 Full UCAF
89 Commercial T&E Rate III
93 Passenger Transport
96 World T&E
HP World High Value Public Sector
RA Enhanced Merit III Base
RB Enhanced Merit III Tier 1
RC Enhanced Merit III Tier 2
RD Enhanced Merit III Tier 3
RK Enhanced Public Sector
RN Enhanced Merchant UCAF
RO Enhanced Full UCAF
RR Enhanced Passenger Transport
SO Business Level 2 T&E Rate III
WP World Elite Public Sector
3O Business Level 3 T&E Rate III
4O Business Level 4 T&E Rate III
When an occurrence of the Financial Detail Addendum (Passenger Transport Detail, Rail Data)/
1644 addendum message is submitted in association with a First Presentment/1240 message,
it must include PDS 0664 (Start Station) and cannot contain null values.
Values
If present, this PDS must be left-justified and cannot contain all zeros, all spaces, all high values,
or all low values.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS is required if the associated First Presentment/1240 contains a railway MCC and is
submitted for one of the U.S. region incentive interchange rate programs lisyed in this table.
IRD Description
10 Merit III Tier 1
11 Merit III Tier 2
12 Merit III Tier 3
22 Public Sector
24 Merchant UCAF
29 Emerging Markets: Consumer Core Value
56 World Public Sector
69 Commercial T&E Rate II
70/80 Merit III Base
79 Full UCAF
89 Commercial T&E Rate III
93 Passenger Transport
96 World T&E
HP World High Value Public Sector
RA Enhanced Merit III Base
RB Enhanced Merit III Tier 1
RC Enhanced Merit III Tier 2
RD Enhanced Merit III Tier 3
RK Enhanced Public Sector
RN Enhanced Merchant UCAF
RO Enhanced Full UCAF
RR Enhanced Passenger Transport
SO Business Level 2 T&E Rate III
WP World Elite Public Sector
3O Business Level 3 T&E Rate III
4O Business Level 4 T&E Rate III
When an occurrence of the Financial Detail Addendum (Passenger Transport Detail, Rail Data)/
1644 addendum message is submitted in association with a First Presentment/1240 message,
it must include PDS 0665 (Destination Station) and cannot contain null values.
Values
If present, this PDS must be left-justified and cannot contain all zeros, all spaces, all high values,
or all low values.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, this PDS must be numeric.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
PDS 0670 must be present in a Financial Detail Addendum (Payment Transaction Detail)/1644
message when Payment Transactions (identified by DE 3 [Processing Code], subfield 1
[Cardholder Transaction Type] value of 28) contains PDS 0043 (Transaction Type Identifier) with
a value of C04, C06, C07, C52, C53, C54, C55, C56, C57, C58, C59, and C65.
Values
If present, each PDS 0670 subfield must be left-justified and cannot contain all low values or all
high values. Subfields 1, 2, 3, 5, and 6 cannot contain all spaces or all zeros. Subfield 7 is an
optional field.
PDS 0670, subfields 1, 2, 3, 4, and 5 must be present when DE 3 (Processing Code), subfield 1
(Cardholder Transaction Type) contains value 28 and PDS 0043 (Transaction Type Identifier)
contains value C04, C07, C52, C53, C54, C55, C56, C57, C58, C59, and C65.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
PDS 0671 must be present in a Financial Detail Addendum (Payment Transaction Detail)/1644
message when Payment Transactions (identified by DE 3 [Processing Code], subfield 1
[Cardholder Transaction Type] value of 28) contains PDS 0043 (Transaction Type Identifier) with
a value of C07, C52, C53, C54, C55, C56, C57, C58, C59, or C65.
NOTE:
For a Mastercard® MoneySend™ payment transaction, this is the date the sender requested the
payment or transfer of funds to the recipient.
Values
If present, PDS 0671 must contain a valid date in the format YYMMDD.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, PDS 0673 must contain a valid date in the format YYMMDD.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
NOTE: For a Mastercard® MoneySend™ payment transaction and a Mastercard Merchant Presented
(MPQR) funding transaction, the acceptor is the originating institution.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, PDS 0675 must be left-justified and cannot contain all spaces.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, PDS 0676 must be left-justified and cannot contain all spaces.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, PDS 0677 must be left-justified and cannot contain all spaces.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS is required in Financial Detail Addendum (Corporate Common Card Data) messages
for transactions submitted for the interchange rate programs listed in this table with Brand
Product MEF.
IRD Description
67 Commercial Data Rate II
82 Electronic Payment Account
Values
If present, PDS 0678 must be left-justified and cannot contain all spaces.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, PDS 0679 must be left-justified and cannot contain all spaces.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, PDS 0680 must be left-justified and cannot contain all spaces.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, PDS 0681 must be left-justified and cannot contain all spaces.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
PDS 0682 must be present in a Financial Detail Addendum (Corporate Line Item Detail)/1644
message when all these conditions exist:
• The product code is MCP or MCF at a non-fuel location.
• The business service is equal to one of the values listed in this table.
The IRD submitted in the associated First Presentment/1240 is one of the values in this table.
IRD Description
26 Purchasing Large Ticket Level 1 Interchange
27 Purchasing Large Ticket Level 2 Interchange
IRD Description
BQ Canada Intracountry Commercial Data Rate IPDS 0682 (including all
subfields) must be present in a Financial Detail Addendum
(Corporate Card Common Data Requirements)/1644 message,
except when PDS 0686 (Tax Exempt Indicator) is present, for
transactions with the associated First Presentment/1240 submitted
for one of the interchange programs listed in this table.
BR PDS 0682 (including all subfields) must be present in a
FinancialCanada Intracountry Commercial Data Rate II
IRD Description
BS Canada Intracountry Commercial Large Ticket
Value Description
Y Tax included in total purchase amount
N Tax not included in total purchase amount
spaces Not supported
Subfield 4 example
Value Description
00 Unknown
01 Federal/National Sales Tax
02 State Sales Tax
Value Description
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)
13 Harmonized Sales Tax (HST)
14 Quebec Sales Tax (QST)
20 Room Tax
21 Occupancy Tax
22 Energy Tax
space Not supported
Value Description
D Detail tax amount is a debit.
Value Description
C Detail tax amount is a credit.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
When a second Canada provincial tax is applicable, PDS 0683 (including all subfields) must be
present in a Financial Detail Addendum (Corporate Card Common Data Requirements)/1644
message, except when PDS 0686 (Tax Exempt Indicator) is present, for transactions with the
associated First Presentment/1240 submitted for one the interchange programs listed in this
table.
IRD Description
BQ Canada Intracountry Commercial Data Rate I
BR Canada Intracountry Commercial Data Rate II
BS Canada Intracountry Commercial Large Ticket
Value Description
Y Tax included in total purchase amount
N Tax not included in total purchase amount
space Not supported
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)
13 Harmonized Sales Tax (HST)
14 Quebec Sales Tax (QST)
20 Room Tax
21 Occupancy Tax
Value Description
22 Energy Tax
space Not supported
Value Description
D Detail tax amount sign is a debit.
C Detail tax amount sign is a credit.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Value Description
Y Tax included in total purchase amount
N Tax not included in total purchase amount
spaces Not supported
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)
Value Description
11 Goods and Services Tax (GST)
12 Provincial Sales Tax (PST)
13 Harmonized Sales Tax (HST)
14 Quebec Sales Tax (QST)
20 Room Tax
21 Occupancy Tax
22 Energy Tax
space Not supported
Value Description
D Detail tax amount sign 3 is a debit.
C Detail tax amount sign 3 is a credit.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
If present, this PDS must be one of the values listed in this table.
Values
Value Description
00 Goods
01 Services
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS is required if the associated First Presentment/1240 contains a vehicle rental acceptor
business code (MCC) and is submitted for the U.S. region Commercial T&E Rate III (IRD 89)
incentive interchange rate program.
If present, this PDS must be one of the values listed in this table.
Values
Value Description
0 No Tax Collected
1 Tax Exempt
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, this PDS must be left-justified and cannot contain all spaces.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages:
Usage
Values
If present, PDS 0688 must be left-justified and cannot contain all low values, all high values, all
spaces, or all zeros. It must be a length of 006–060.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Attributes
Subfields: None
Justification: None
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
If present, this PDS must contain one of the values listed in this table.
Values
Value Description
0 Not applicable
1 No-Show transaction amount due
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS is required if the associated First Presentment/1240 contains a vehicle rental acceptor
business code (MCC) and is submitted for the U.S. region Commercial T&E Rate III (IRD 89)
incentive interchange rate program.
When an occurrence of the Financial Detail Addendum (Vehicle Rental Detail)/1644 addendum
message is submitted in association with a First Presentment/1240 message, it must include
PDS 0691 (Days Rented) and cannot contain null values.
Values
If present, this PDS must be numeric and may contain all zeros.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, this PDS must be numeric and may contain all zeros.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, PDS 0693 must be a fixed length of 014.
NOTE: Financial Detail Addendum/1644 messages that contain amounts and amount exponents
should utilize the same currency and exponent of the Amount, Transaction in the associated First
Presentment/1240 message.
Value Description
D Total authorized amount is a debit.
C Total authorized amount sign is a credit.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, this PDS must be numeric and may contain all zeros.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, this PDS must be numeric and may contain all zeros.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, this PDS must be numeric and may contain all zeros.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, this PDS must be numeric and may contain all zeros.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, this PDS must be numeric and may contain all zeros.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, PDS 0699 must be a fixed length of 014.
NOTE: Financial Detail Addendum/1644 messages that contain amounts and amount exponents
should utilize the same currency and exponent of the Amount, Transaction in the associated First
Presentment/1240 message.
Value Description
D Lodging total tax amount is a debit.
C Lodging total tax amount is a credit.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, this PDS must be numeric and may contain all zeros.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, this PDS must be numeric and may contain all zeros.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, this PDS must be numeric and may contain all zeros.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS is required if the associated First Presentment/1240 contains a lodging acceptor
business code (MCC) and is submitted for the U.S. region Commercial T&E Rate III (IRD 89)
incentive interchange rate program.
When an occurrence of the Financial Detail Addendum (Lodging Summary)/1644 addendum
message is submitted in association with a First Presentment/1240 message, it must include
PDS 0703 (Total Room Nights) and cannot contain null values.
Values
If present, this PDS must be numeric and may contain all zeros.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, PDS 0704 must be a fixed length of 014.
NOTE: Financial Detail Addendum/1644 messages that contain amounts and amount exponents
should utilize the same currency and exponent of the Amount, Transaction in the associated First
Presentment/1240 message.
Value Description
D Prepaid expenses amount is a debit.
C Prepaid expenses amount is a credit.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, PDS 0705 must be a fixed length of 014.
NOTE: Financial Detail Addendum/1644 messages that contain amounts and amount exponents
should utilize the same currency and exponent of the Amount, Transaction in the associated First
Presentment/1240 message.
Value Description
D Total non-room tax amount is a debit.
C Total non-room tax amount is a credit.
NOTE: Mastercard® merchants are prohibited from performing cash advances. For transactions in
which the Cardholder Transaction Type (DE 3, subfield 1) is purchase with cash back (value 09), the
acquirer must provide the amount of cash back in DE 54.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, PDS 0706 must be a fixed length of 014.
Mastercard® merchants are prohibited from performing cash advances. For transactions in
which the Cardholder Transaction Type (DE 3, subfield 1) is purchase with cash back (value 09),
the acquirer must provide the amount of cash back in DE 54. For more information on cash
advances, refer to the Mastercard Manual Cash Disbursement Transactions section of the
Transaction Processing Rules manual.
NOTE: Financial Detail Addendum/1644 messages that contain amounts and amount exponents
should utilize the same currency and exponent of the Amount, Transaction in the associated First
Presentment/1240 message.
Value Description
D Cash advance amount is a debit.
C Cash advance amount is a credit.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, PDS 0707 must be a fixed length of 014.
NOTE: Financial Detail Addendum/1644 messages that contain amounts and amount exponents
should utilize the same currency and exponent of the Amount, Transaction in the associated First
Presentment/1240 message.
Value Description
D Valet charges amount is a debit.
C Valet charges amount is a credit.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, PDS 0708 must be a fixed length of 014.
NOTE: Financial Detail Addendum/1644 messages that contain amounts and amount exponents
should utilize the same currency and exponent of the Amount, Transaction in the associated First
Presentment/1240 message.
Value Description
D Movie charges amount is a debit.
C Movie charges amount is a credit.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, PDS 0709 must be a fixed length of 014.
NOTE: Financial Detail Addendum/1644 messages that contain amounts and amount exponents
should utilize the same currency and exponent of the Amount, Transaction in the associated First
Presentment/1240 message.
Value Description
D Business center charges amount is a debit.
C Business center charges amount is a credit.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, PDS 0710 must be a fixed length of 014.
NOTE: Financial Detail Addendum/1644 messages that contain amounts and amount exponents
should utilize the same currency and exponent of the Amount, Transaction in the associated First
Presentment/1240 message.
Value Description
D Health club charges amount is a debit.
C Health club charges amount is a credit.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS is required if the associated First Presentment/1240 contains a lodging acceptor
business code (MCC) and is submitted for the U.S. region Commercial T&E Rate III (IRD 89)
incentive interchange rate program.
Values
If present, this PDS must contain one of the values listed in this table.
Value Description
Y In compliance with Fire Safety Act
N Not in compliance with Fire Safety Act
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
If present, this PDS must contain one of the values listed in this table.
Value Description
0 No restriction
1 Restricted ticket (non-refundable)
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, this PDS must be numeric and may contain all zeros.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
PDS 0715 must be present in a Financial Detail Addendum (Passenger Transport Detail,
General Ticket Information)/1644 message when the ancillary service charge data is provided
by the acceptor with an MCC of Airline, Railway, or Travel Agency.
When the ancillary service charge data is present for transactions with an MCC of Airline,
Railway, or Travel Agency then the issuer must disclose the description of the ancillary service
charges by making it visible in cardholder billing statements, online account tools, mobile apps,
or other methods designed to inform cardholders of their purchases.
Values
If present, PDS 0715 must be a length of 14-84, and divisible by a minimum occurrence length
of 14.
Value Description
BF Bundled Service
BG Baggage Fee
CF Change Fee
CG Cargo
CO Carbon Offset
FF Frequent Flyer
GF Gift Card
GT Ground Transport
IE In-Flight Entertainment
LG Lounge
MD Medical
ML Meal/Beverage
OT Other
PA Passenger Assist Fee
PT Pets
SA Seat Fees
SB Standby
SF Service Fee
ST Store
TS Travel Service
UN Unaccompanied Travel
UP Upgrades
WI Wi-Fi
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, an ancillary fee amount of
USD 212.50 is expressed as 000000021250.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, this PDS must be left-justified and cannot contain all spaces.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, this PDS must be left-justified and cannot contain all spaces.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
PDS 0718 is required for the Financial Detail Addendum (Temporary Services)/1644 message
when both of these conditions apply:
• DE 26 (Acceptor Business Code [MCC]) contains a value of 7361 (Employment Agencies,
Temporary Services)
• The associated First Presentment/1240 message is submitted for one of the interchange
programs listed in this table.
IRD Description
BR Canada Intracountry Commercial Data Rate II
BS Canada Intracountry Commercial Large Ticket
IRD Description
62 Commercial Large Ticket 1
66 Commercial Data Rate III
94 Commercial Large Ticket II
99 Commercial Large Ticket III
IRD Description
SC Business Level 2 Data Rate III
SE Business Level 2 Large Ticket I
3C Business Level 3 Data Rate III
4C Business Level 4 Data Rate III
Values
If present, this PDS must be left-justified and cannot contain all spaces or all zeros.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, this PDS must be left-justified and cannot contain all spaces or all zeros.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
PDS 0720 is required for the Financial Detail Addendum (Temporary Services)/1644 message
when both of these conditions apply:
• DE 26 (Acceptor Business Code [MCC]) contains a value of 7361 (Employment Agencies,
Temporary Services), and
• The associated First Presentment/1240 message is submitted for one of the interchange
programs listed in this table.
IRD Description
BR Canada Intracountry Commercial Data Rate II
IRD Description
BS Canada Intracountry Commercial Large Ticket
IRD Description
62 Commercial Large Ticket 1
66 Commercial Data Rate III
94 Commercial Large Ticket II
99 Commercial Large Ticket III
SC Business Level 2 Data Rate III
SE Business Level 2 Large Ticket I
SF Business Level 2 Large Ticket II
SG Business Level 2 Large Ticket III
3C Business Level 3 Data Rate III
3E Business Level 3 Large Ticket I
3F Business Level 3 Large Ticket II
3G Business Level 3 Large Ticket III
4C Business Level 4 Data Rate III
4E Business Level 4 Large Ticket I
4F Business Level 4 Large Ticket II
4G Business Level 4 Large Ticket III
Values
If present, this PDS must be left-justified and cannot contain all spaces or all zeros.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, this PDS must be left-justified and cannot contain all spaces or all zeros.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, this PDS shows whether the flat rate is applied. The valid value is Y or N.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
At least one of these fields is required for the Financial Detail Addendum (Temporary Services)/
1644 message when the transaction is submitted for any of the interchange programs listed in
this table and the MCC in DE 26 (Acceptor Business Code [MCC]) contains MCC 7361:
Employment Agencies, Temporary Services:
• PDS 0723 (Regular Hours Worked)
• PDS 0725 (Overtime Hours Worked), or
• PDS 0734 (Miscellaneous Expenses).
IRD Description
BR Canada Intracountry Commercial Data Rate II
BS Canada Intracountry Commercial Large Ticket
IRD Description
62 Commercial Large Ticket 1
66 Commercial Data Rate III
94 Commercial Large Ticket II
99 Commercial Large Ticket III
SC Business Level 2 Data Rate III
SE Business Level 2 Large Ticket I
SF Business Level 2 Large Ticket II
SG Business Level 2 Large Ticket III
3C Business Level 3 Data Rate III
3E Business Level 3 Large Ticket I
3F Business Level 3 Large Ticket II
3G Business Level 3 Large Ticket III
IRD Description
4C Business Level 4 Data Rate III
4E Business Level 4 Large Ticket I
4F Business Level 4 Large Ticket II
4G Business Level 4 Large Ticket III
Values
If present, this PDS must be numeric and may contain all zeros.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
PDS 0724 is mandatory for the Financial Detail Addendum (Temporary Services)/1644
message when all of these conditions apply:
• MCC is 7361: Employment Agencies and Temporary Services is in DE 26 (Acceptor Business
Code [MCC]).
• PDS 0723 (Regular Hours Worked) is present.
• The associated First Presentment/1240 message is submitted for any of the interchange
programs listed in these tables.
IRD Description
BR Canada Intracountry Commercial Data Rate II
BS Canada Intracountry Commercial Large Ticket
4F Business Level 4 Large Ticket II
4G Business Level 4 Large Ticket III
IRD Description
62 Commercial Large Ticket 1
66 Commercial Data Rate III
94 Commercial Large Ticket II
IRD Description
99 Commercial Large Ticket III
SC Business Level 2 Data Rate III
SE Business Level 2 Large Ticket I
SF Business Level 2 Large Ticket II
SG Business Level 2 Large Ticket III
3C Business Level 3 Data Rate III
3E Business Level 3 Large Ticket I
3F Business Level 3 Large Ticket II
3G Business Level 3 Large Ticket III
4C Business Level 4 Data Rate III
4E Business Level 4 Large Ticket I
4F Business Level 4 Large Ticket II
4G Business Level 4 Large Ticket III
Values
If present, this PDS must be numeric and may contain all zeros.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
At least one of these fields is required for the Financial Detail Addendum (Temporary Services)/
1644 message when the transaction is submitted for any of the interchange programs listed in
these table and the MCC in DE 26 (Acceptor Business Code [MCC]) contains MCC 7361:
Employment Agencies, Temporary Services:
• PDS 0723 (Regular Hours Worked)
• PDS 0725 (Overtime Hours Worked), or
• PDS 0734 (Miscellaneous Expenses).
IRD Description
BR Canada Intracountry Commercial Data Rate II
IRD Description
BS Canada Intracountry Commercial Large Ticket
IRD Description
62 Commercial Large Ticket 1
66 Commercial Data Rate III
94 Commercial Large Ticket II
99 Commercial Large Ticket III
SC Business Level 2 Data Rate III
SE Business Level 2 Large Ticket I
SF Business Level 2 Large Ticket II
SG Business Level 2 Large Ticket III
3C Business Level 3 Data Rate III
3E Business Level 3 Large Ticket I
3F Business Level 3 Large Ticket II
3G Business Level 3 Large Ticket III
4C Business Level 4 Data Rate III
4E Business Level 4 Large Ticket I
4F Business Level 4 Large Ticket II
4G Business Level 4 Large Ticket III
Values
If present, this PDS must be numeric and may contain all zeros.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS is mandatory for the Financial Detail Addendum (Temporary Services)/1644 message
when all of these conditions apply:
• The associated First Presentment/1240 message is submitted for any of the interchange
programs listed in these tables.
• MCC is 7361: Employment Agencies and Temporary Services in DE 26 (Acceptor Business
Code [MCC]).
• PDS 0725 (Overtime Hours Worked) is present.
IRD Description
BR Canada Intracountry Commercial Data Rate II
BS Canada Intracountry Commercial Large Ticket
IRD Description
62 Commercial Large Ticket 1
66 Commercial Data Rate III
94 Commercial Large Ticket II
99 Commercial Large Ticket III
SC Business Level 2 Data Rate III
SE Business Level 2 Large Ticket I
3C Business Level 3 Data Rate III
4C Business Level 4 Data Rate III
Values
If present, this PDS must be numeric and may contain all zeros.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
PDS 0727 is required for the Financial Detail Addendum (Temporary Services)/1644 message
when both of these conditions apply:
IRD Description
BR Canada Intracountry Commercial Data Rate II
BS Canada Intracountry Commercial Large Ticket
IRD Description
62 Commercial Large Ticket 1
66 Commercial Data Rate III
94 Commercial Large Ticket II
99 Commercial Large Ticket III
SC Business Level 2 Data Rate III
SE Business Level 2 Large Ticket I
SF Business Level 2 Large Ticket II
SG Business Level 2 Large Ticket III
3C Business Level 3 Data Rate III
3E Business Level 3 Large Ticket I
3F Business Level 3 Large Ticket II
3G Business Level 3 Large Ticket III
4C Business Level 4 Data Rate III
4E Business Level 4 Large Ticket I
4F Business Level 4 Large Ticket II
4G Business Level 4 Large Ticket III
Values
If present, this PDS must be a valid date in the format YYMMDD.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
PDS 0728 is required for the Financial Detail Addendum (Temporary Services)/1644 message
when both of these conditions apply:
• DE 26 (Acceptor Business Code [MCC]) contains a value of 7361 (Employment Agencies,
Temporary Services), and
• The associated First Presentment/1240 message is submitted for one of the interchange
programs listed in these tables.
IRD Description
BR Canada Intracountry Commercial Data Rate II
BS Canada Intracountry Commercial Large Ticket
IRD Description
62 Commercial Large Ticket 1
66 Commercial Data Rate III
94 Commercial Large Ticket II
99 Commercial Large Ticket III
SC Business Level 2 Data Rate III
SE Business Level 2 Large Ticket I
3C Business Level 3 Data Rate III
4C Business Level 4 Data Rate III
Values
If present, this PDS must contain a valid date in the format YYMMDD.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS is required for the Financial Detail Addendum (Temporary Services)/1644 message
when both of these conditions apply:
• DE 26 (Acceptor Business Code [MCC]) contains a value of 7361 (Employment Agencies,
Temporary Services), and
• The associated First Presentment/1240 message is submitted for one of the interchange
programs listed in these tables.
IRD Description
BR Canada Intracountry Commercial Data Rate II
BS Canada Intracountry Commercial Large Ticket
IRD Description
62 Commercial Large Ticket 1
66 Commercial Data Rate III
94 Commercial Large Ticket II
99 Commercial Large Ticket III
SC Business Level 2 Data Rate III
SE Business Level 2 Large Ticket I
SF Business Level 2 Large Ticket II
SG Business Level 2 Large Ticket III
3C Business Level 3 Data Rate III
3E Business Level 3 Large Ticket I
3F Business Level 3 Large Ticket II
3G Business Level 3 Large Ticket III
4C Business Level 4 Data Rate III
IRD Description
4E Business Level 4 Large Ticket I
4F Business Level 4 Large Ticket II
4G Business Level 4 Large Ticket III
Values
If present, this PDS must be left-justified and cannot contain all spaces or all zeros.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, this PDS must be left-justified and cannot contain all spaces or all zeros.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, this PDS must be left-justified and cannot contain all spaces or all zeros.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, PDS 0732 must be a fixed length of 018.
Value Description
D Discount amount is a debit.
C Discount amount is a credit.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, PDS 0733 must be a fixed length of 014.
Value Description
D Subtotal amount is a debit.
C Subtotal amount is a credit.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS enables 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.
At least one of these fields is required for the Financial Detail Addendum (Temporary Services)/
1644 message when the transaction is submitted for any of the interchange programs listed in
these tables and the MCC in DE 26 (Acceptor Business Code [MCC]) is 7361: Employment
Agencies, Temporary Services:
• PDS 0723 (Regular Hours Worked)
IRD Description
BR Canada Intracountry Commercial Data Rate II
BS Canada Intracountry Commercial Large Ticket
IRD Description
62 Commercial Large Ticket 1
66 Commercial Data Rate III
94 Commercial Large Ticket II
99 Commercial Large Ticket III
Values
If present, PDS 0734 must be within a minimum length of 054–216 and must be divisible by a
minimum occurrence length of 054.
Value Description
D Miscellaneous expense amount is a debit.
C Miscellaneous expense amount is a credit.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS is required for the Financial Detail Addendum (Shipping/Courier Services)/1644
message when these conditions apply:
• One of these MCCs is present in DE 26 (Acceptor Business Code [MCC]):
– 4214: Motor Freight Carriers, Trucking; Local/Long Distance, Moving and Storage
Companies, Local Delivery
– 4215: Courier Services; Air and Ground, Freight Forwards
• The Financial Detail Addendum (Corporate Line Item Detail)/1644 message is not present.
• The transaction is submitted for the any of the interchange programs listed in these tables.
IRD Description
BR Canada Intracountry Commercial Data Rate II
BS Canada Intracountry Commercial Large Ticket
IRD Description
62 Commercial Large Ticket 1
66 Commercial Data Rate III
IRD Description
94 Commercial Large Ticket II
99 Commercial Large Ticket III
SC Business Level 2 Data Rate III
SE Business Level 2 Large Ticket I
SF Business Level 2 Large Ticket II
SG Business Level 2 Large Ticket III
3C Business Level 3 Data Rate III
3E Business Level 3 Large Ticket I
3F Business Level 3 Large Ticket II
3G Business Level 3 Large Ticket III
4C Business Level 4 Data Rate III
4E Business Level 4 Large Ticket I
4F Business Level 4 Large Ticket II
4G Business Level 4 Large Ticket III
Values
If present, this PDS must be left-justified and cannot contain all spaces or all zeros.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS is required for the Financial Detail Addendum (Shipping/Courier Services)/1644
message when these conditions apply:
• One of the following MCCs is present in DE 26 (Acceptor Business Code [MCC]):
– 4214: Motor Freight carriers, Trucking; Local/Long Distance, Moving and Storage
Companies, Local Delivery
– 4215: Courier Services; Air and Ground, Freight Forwards
• The Financial Detail Addendum (Corporate Line Item Detail)/1644 message is not present.
• The transaction is submitted for any of the interchange programs listed in these tables.
IRD Description
BR Canada Intracountry Commercial Data Rate II
BS Canada Intracountry Commercial Large Ticket
IRD Description
62 Commercial Large Ticket 1
66 Commercial Data Rate III
94 Commercial Large Ticket II
99 Commercial Large Ticket III
SC Business Level 2 Data Rate III
SE Business Level 2 Large Ticket I
SF Business Level 2 Large Ticket II
SG Business Level 2 Large Ticket III
IRD Description
3C Business Level 3 Data Rate III
3E Business Level 3 Large Ticket I
3F Business Level 3 Large Ticket II
3G Business Level 3 Large Ticket III
4C Business Level 4 Data Rate III
4E Business Level 4 Large Ticket I
4F Business Level 4 Large Ticket II
4G Business Level 4 Large Ticket III
Values
If present, this PDS must be left-justified and cannot contain all spaces or all zeros.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS is required for the Financial Detail Addendum (Shipping/Courier Services)/1644
message when these conditions apply:
• One of these MCCs is present in DE 26 (Acceptor Business Code [MCC]):
– 4214: Motor Freight Carriers, Trucking; Local/Long Distance, Moving and Storage
Companies, Local Delivery
– 4215: Courier Services; Air and Ground, Freight Forwards
• The Financial Detail Addendum (Corporate Line Item Detail)/1644 message is not present.
• The transaction is submitted for any of the interchange programs listed in these tables.
IRD Description
BR Canada Intracountry Commercial Data Rate II
BS Canada Intracountry Commercial Large Ticket
IRD Description
62 Commercial Large Ticket 1
66 Commercial Data Rate III
94 Commercial Large Ticket II
99 Commercial Large Ticket III
SC Business Level 2 Data Rate III
SE Business Level 2 Large Ticket I
SF Business Level 2 Large Ticket II
SG Business Level 2 Large Ticket III
3C Business Level 3 Data Rate III
IRD Description
3E Business Level 3 Large Ticket I
3F Business Level 3 Large Ticket II
3G Business Level 3 Large Ticket III
4C Business Level 4 Data Rate III
4E Business Level 4 Large Ticket I
4F Business Level 4 Large Ticket II
4G Business Level 4 Large Ticket III
Values
If present, PDS 0737 must be a fixed length of 014.
Value Description
D Shipping net amount is a debit.
C Shipping net amount is a credit.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, PDS 0738 must be a fixed length of 014.
Value Description
D Incentive amount is a debit.
C Incentive amount is a credit.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS is required for the Financial Detail Addendum (Shipping/Courier Services)/1644
message when these conditions apply:
• One of these MCCs is present in DE 26 (Acceptor Business Code [MCC]):
– 4214: Motor Freight Carriers, Trucking; Local/Long Distance, Moving and Storage
Companies, Local Delivery
– 4215: Courier Services; Air and Ground, Freight Forwards
• The Financial Detail Addendum (Corporate Line Item Detail)/1644 message is not present.
• The transaction is submitted for the interchange programs listed in these tables.
IRD Description
BR Canada Intracountry Commercial Data Rate II
BS Canada Intracountry Commercial Large Ticket
IRD Description
62 Commercial Large Ticket 1
IRD Description
66 Commercial Data Rate III
94 Commercial Large Ticket II
99 Commercial Large Ticket III
SC Business Level 2 Data Rate III
SE Business Level 2 Large Ticket I
SF Business Level 2 Large Ticket II
SG Business Level 2 Large Ticket III
3C Business Level 3 Data Rate III
3E Business Level 3 Large Ticket I
3F Business Level 3 Large Ticket II
3G Business Level 3 Large Ticket III
4C Business Level 4 Data Rate III
4E Business Level 4 Large Ticket I
4F Business Level 4 Large Ticket II
4G Business Level 4 Large Ticket III
Values
If present, this PDS must be a valid date in the format YYMMDD.
Attributes
Justification: Right
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, this PDS must be a valid date in the format YYMMDD.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS is required for the Financial Detail Addendum (Shipping/Courier Services)/1644
message when:
• One of these MCCs is present in DE 26, Acceptor Business Code (MCC),
– 4214: Motor Freight Carriers, Trucking; Local/Long Distance, Moving and Storage
Companies, Local Delivery
– 4215: Courier Services; Air and Ground, Freight Forwards
• The Financial Detail Addendum (Corporate Line Item Detail)/1644 message is not present.
• The transaction is submitted for one of the interchange programs listed in these tables.
IRD Description
BR Canada Intracountry Commercial Data Rate II
BS Canada Intracountry Commercial Large Ticket
IRD Description
62 Commercial Large Ticket 1
66 Commercial Data Rate III
94 Commercial Large Ticket II
99 Commercial Large Ticket III
SC Business Level 2 Data Rate III
SE Business Level 2 Large Ticket I
SF Business Level 2 Large Ticket II
SG Business Level 2 Large Ticket III
3C Business Level 3 Data Rate III
IRD Description
3E Business Level 3 Large Ticket I
3F Business Level 3 Large Ticket II
3G Business Level 3 Large Ticket III
4C Business Level 4 Data Rate III
4E Business Level 4 Large Ticket I
4F Business Level 4 Large Ticket II
4G Business Level 4 Large Ticket III
Values
If present, this PDS must be numeric and may contain all zeros.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS is required for the Financial Detail Addendum (Shipping/Courier Services)/1644
message when these conditions apply:
• One of these MCCs is present in DE 26 (Acceptor Business Code [MCC]):
– 4214: Motor Freight Carriers, Trucking; Local/Long Distance, Moving and Storage
Companies, Local Delivery
– 4215: Courier Services; Air and Ground, Freight Forwards
• The Financial Detail Addendum (Corporate Line Item Detail)/1644 message is not present.
• The transaction is submitted for any of the interchange programs listed in these tables.
IRD Description
BR Canada Intracountry Commercial Data Rate II
BS Canada Intracountry Commercial Large Ticket
IRD Description
62 Commercial Large Ticket 1
66 Commercial Data Rate III
94 Commercial Large Ticket II
99 Commercial Large Ticket III
SC Business Level 2 Data Rate III
SE Business Level 2 Large Ticket I
SF Business Level 2 Large Ticket II
SG Business Level 2 Large Ticket III
3C Business Level 3 Data Rate III
IRD Description
3E Business Level 3 Large Ticket I
3F Business Level 3 Large Ticket II
3G Business Level 3 Large Ticket III
4C Business Level 4 Data Rate III
4E Business Level 4 Large Ticket I
4F Business Level 4 Large Ticket II
4G Business Level 4 Large Ticket III
Values
If present, this PDS must be left-justified and cannot contain all spaces, all low values, or all high
values.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS is required for the Financial Detail Addendum (Shipping/Courier Services)/1644
message when these conditions apply:
• One of the following MCCs is present in DE 26 (Acceptor Business Code [MCC]):
– 4214: Motor Freight Carriers, Trucking; Local/Long Distance, Moving and Storage
Companies, Local Delivery
– 4215: Courier Services; Air and Ground, Freight Forwards
• The Financial Detail Addendum (Corporate Line Item Detail)/1644 message is not present.
• The transaction is submitted for any of the interchange programs listed in these tables.
IRD Description
BR Canada Intracountry Commercial Data Rate II
BS Canada Intracountry Commercial Large Ticket
IRD Description
62 Commercial Large Ticket 1
66 Commercial Data Rate III
94 Commercial Large Ticket II
99 Commercial Large Ticket III
SC Business Level 2 Data Rate III
SE Business Level 2 Large Ticket I
SF Business Level 2 Large Ticket II
SG Business Level 2 Large Ticket III
3C Business Level 3 Data Rate III
IRD Description
3E Business Level 3 Large Ticket I
3F Business Level 3 Large Ticket II
3G Business Level 3 Large Ticket III
4C Business Level 4 Data Rate III
4E Business Level 4 Large Ticket I
4F Business Level 4 Large Ticket II
4G Business Level 4 Large Ticket III
Values
If present, this PDS must be left-justified and cannot contain all spaces or all zeros.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS enables the sender to provide 1–3 different shipping party names.
This PDS is required for the Financial Detail Addendum (Shipping/Courier Services)/1644
message when these conditions apply:
• One of these MCCs is present in DE 26 (Acceptor Business Code [MCC]):
– 4214: Motor Freight Carriers, Trucking; Local/Long Distance, Moving and Storage
Companies, Local Delivery
– 4215: Courier Services; Air and Ground, Freight Forwards
• The Financial Detail Addendum (Corporate Line Item Detail)/1644 message is not present.
• The transaction is submitted for any of the interchange programs listed in these tables.
IRD Description
BR Canada Intracountry Commercial Data Rate II
BS Canada Intracountry Commercial Large Ticket
IRD Description
62 Commercial Large Ticket 1
66 Commercial Data Rate III
94 Commercial Large Ticket II
99 Commercial Large Ticket III
SC Business Level 2 Data Rate III
SE Business Level 2 Large Ticket I
SF Business Level 2 Large Ticket II
SG Business Level 2 Large Ticket III
3C Business Level 3 Data Rate III
IRD Description
3E Business Level 3 Large Ticket I
3F Business Level 3 Large Ticket II
3G Business Level 3 Large Ticket III
4C Business Level 4 Data Rate III
4E Business Level 4 Large Ticket I
4F Business Level 4 Large Ticket II
4G Business Level 4 Large Ticket III
Values
If present, this PDS must be left-justified and cannot contain all spaces or all zeros.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS enables the sender to provide 1–6 different shipping party address lines.
This PDS is required for the Financial Detail Addendum (Shipping/Courier Services)/1644
message when these conditions apply:
• One of these MCCs is present in DE 26 (Acceptor Business Code [MCC]):
– 4214: Motor Freight Carriers, Trucking; Local/Long Distance, Moving and Storage
Companies, Local Delivery
– 4215: Courier Services; Air and Ground, Freight Forwards
• The Financial Detail Addendum (Corporate Line Item Detail)/1644 message is not present.
• The transaction is submitted for any of the interchange programs listed in these tables.
IRD Description
BR Canada Intracountry Commercial Data Rate II
BS Canada Intracountry Commercial Large Ticket
IRD Description
62 Commercial Large Ticket 1
66 Commercial Data Rate III
IRD Description
94 Commercial Large Ticket II
99 Commercial Large Ticket III
SC Business Level 2 Data Rate III
SE Business Level 2 Large Ticket I
SF Business Level 2 Large Ticket II
SG Business Level 2 Large Ticket III
3C Business Level 3 Data Rate III
3E Business Level 3 Large Ticket I
3F Business Level 3 Large Ticket II
3G Business Level 3 Large Ticket III
4C Business Level 4 Data Rate III
4E Business Level 4 Large Ticket I
4F Business Level 4 Large Ticket II
4G Business Level 4 Large Ticket III
Values
If present, this PDS must be left-justified and cannot contain all spaces or all zeros.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS is required for the Financial Detail Addendum (Shipping/Courier Services)/1644
message when these conditions apply:
• One of these MCCs is present in DE 26 (Acceptor Business Code [MCC]):
– 4214: Motor Freight Carriers, Trucking; Local/Long Distance, Moving and Storage
Companies, Local Delivery
– 4215: Courier Services; Air and Ground, Freight Forwards
• The Financial Detail Addendum (Corporate Line Item Detail)/1644 message is not present.
• The transaction is submitted for any of the interchange programs listed in these tables.
IRD Description
BR Canada Intracountry Commercial Data Rate II
BS Canada Intracountry Commercial Large Ticket
IRD Description
62 Commercial Large Ticket 1
66 Commercial Data Rate III
94 Commercial Large Ticket II
99 Commercial Large Ticket III
SC Business Level 2 Data Rate III
SE Business Level 2 Large Ticket I
SF Business Level 2 Large Ticket II
SG Business Level 2 Large Ticket III
3C Business Level 3 Data Rate III
3E Business Level 3 Large Ticket I
3F Business Level 3 Large Ticket II
3G Business Level 3 Large Ticket III
4C Business Level 4 Data Rate III
4E Business Level 4 Large Ticket I
4F Business Level 4 Large Ticket II
4G Business Level 4 Large Ticket III
Values
If present, this PDS must be left-justified and cannot contain all spaces or all zeros.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS enables 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.
This PDS is required for the Financial Detail Addendum (Shipping/Courier Services)/1644
message when these conditions apply:
• One of these MCCs is present in DE 26 (Acceptor Business Code [MCC]):
– 4214: Motor Freight Carriers, Trucking; Local/Long Distance, Moving and Storage
Companies, Local Delivery
– 4215: Courier Services; Air and Ground, Freight Forwards
• The Financial Detail Addendum (Corporate Line Item Detail)/1644 message is not present.
• The transaction is submitted for any of the interchange programs listed in these tables.
IRD Description
BR Canada Intracountry Commercial Data Rate II
BS Canada Intracountry Commercial Large Ticket
IRD Description
62 Commercial Large Ticket 1
66 Commercial Data Rate III
94 Commercial Large Ticket II
99 Commercial Large Ticket III
SC Business Level 2 Data Rate III
SE Business Level 2 Large Ticket I
SF Business Level 2 Large Ticket II
SG Business Level 2 Large Ticket III
3C Business Level 3 Data Rate III
3E Business Level 3 Large Ticket I
3F Business Level 3 Large Ticket II
3G Business Level 3 Large Ticket III
4C Business Level 4 Data Rate III
4E Business Level 4 Large Ticket I
4F Business Level 4 Large Ticket II
4G Business Level 4 Large Ticket III
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.
Value Description
1 Name
2 Title
3 Telephone
4 E-mail address
5 Function
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS allows the sender to provide 1–3 different delivery party names.
This PDS is required for the Financial Detail Addendum (Shipping/Courier Services)/1644
message when these conditions apply:
• One of these MCCs is present in DE 26 (Acceptor Business Code [MCC]):
– 4214: Motor Freight Carriers, Trucking; Local/Long Distance, Moving and Storage
Companies, Local Delivery
– 4215: Courier Services; Air and Ground, Freight Forwards
• The Financial Detail Addendum (Corporate Line Item Detail)/1644 message is not present.
• The transaction is submitted for any of the interchange programs listed in these tables.
IRD Description
BR Canada Intracountry Commercial Data Rate II
BS Canada Intracountry Commercial Large Ticket
IRD Description
62 Commercial Large Ticket 1
66 Commercial Data Rate III
94 Commercial Large Ticket II
99 Commercial Large Ticket III
SC Business Level 2 Data Rate III
SE Business Level 2 Large Ticket I
SF Business Level 2 Large Ticket II
SG Business Level 2 Large Ticket III
3C Business Level 3 Data Rate III
3E Business Level 3 Large Ticket I
3F Business Level 3 Large Ticket II
3G Business Level 3 Large Ticket III
4C Business Level 4 Data Rate III
4E Business Level 4 Large Ticket I
4F Business Level 4 Large Ticket II
4G Business Level 4 Large Ticket III
Values
If present, this PDS must be left-justified and cannot contain all spaces or all zeros.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS enables the sender to provide 1–6 different delivery party address lines.
This PDS is required for the Financial Detail Addendum (Shipping/Courier Services)/1644
message when these conditions apply:
• One of these MCCs is present in DE 26 (Acceptor Business Code [MCC]):
– 4214: Motor Freight Carriers, Trucking; Local/Long Distance, Moving and Storage
Companies, Local Delivery
– 4215: Courier Services; Air and Ground, Freight Forwards
• The Financial Detail Addendum (Corporate Line Item Detail)/1644 message is not present.
• The transaction is submitted for any of the interchange programs listed in these tables.
IRD Description
BR Canada Intracountry Commercial Data Rate II
BS Canada Intracountry Commercial Large Ticket
IRD Description
62 Commercial Large Ticket 1
66 Commercial Data Rate III
94 Commercial Large Ticket II
99 Commercial Large Ticket III
SC Business Level 2 Data Rate III
SE Business Level 2 Large Ticket I
SF Business Level 2 Large Ticket II
SG Business Level 2 Large Ticket III
IRD Description
3C Business Level 3 Data Rate III
3E Business Level 3 Large Ticket I
3F Business Level 3 Large Ticket II
3G Business Level 3 Large Ticket III
4C Business Level 4 Data Rate III
4E Business Level 4 Large Ticket I
4F Business Level 4 Large Ticket II
4G Business Level 4 Large Ticket III
Values
If present, this PDS must be left-justified and cannot contain all spaces or all zeros.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS is required for the Financial Detail Addendum (Shipping/Courier Services)/1644
message when these conditions apply:
• One of these MCCs is present in DE 26 (Acceptor Business Code [MCC]):
– 4214: Motor Freight Carriers, Trucking; Local/Long Distance, Moving and Storage
Companies, Local Delivery
– 4215: Courier Services; Air and Ground, Freight Forwards
• The Financial Detail Addendum (Corporate Line Item Detail)/1644 message is not present.
• The transaction is submitted for any of the interchange programs listed in these tables.
IRD Description
BR Canada Intracountry Commercial Data Rate II
BS Canada Intracountry Commercial Large Ticket
IRD Description
62 Commercial Large Ticket 1
66 Commercial Data Rate III
IRD Description
94 Commercial Large Ticket II
99 Commercial Large Ticket III
SC Business Level 2 Data Rate III
SE Business Level 2 Large Ticket I
SF Business Level 2 Large Ticket II
SG Business Level 2 Large Ticket III
3C Business Level 3 Data Rate III
3E Business Level 3 Large Ticket I
3F Business Level 3 Large Ticket II
3G Business Level 3 Large Ticket III
4C Business Level 4 Data Rate III
4E Business Level 4 Large Ticket I
4F Business Level 4 Large Ticket II
4G Business Level 4 Large Ticket III
Values
If present, this PDS and each of its four subfields must be left-justified and cannot contain all
spaces or all zeros.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Value Description
Y Tax included in total purchase amount
N Tax not included in total purchase amount
Space Not supported
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 (GST)
12 Provincial Sales Tax (PST)
13 Harmonized Sales Tax (HST)
14 Quebec Sales Tax (QST)
20 Room Tax
21 Occupancy Tax
22 Energy Tax
Value Description
Space Not supported
Value Description
D Detail tax amount is a debit.
C Detail tax amount is a credit.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Value Description
Y Tax included in total purchase amount
N Tax not included in total purchase amount
Space Not supported
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)
Value Description
11 Goods and Services (GST)
12 Provincial Sales Tax (PST)
13 Harmonized Sales Tax (HST)
14 Quebec Sales Tax (QST)
20 Room Tax
21 Occupancy Tax
22 Energy Tax
Space Not supported
Value Description
D Detail tax amount is a debit.
C Detail tax amount is a credit.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Value Description
Y Tax included in total purchase amount
N Tax not included in total purchase amount
Value Description
Space Not supported
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 (GST)
12 Provincial Sales Tax (PST)
13 Harmonized Sales Tax (HST)
14 Quebec Sales Tax (QST)
20 Room Tax
21 Occupancy Tax
22 Energy Tax
Space Not supported
Value Description
D Detail tax amount is a debit.
C Detail tax amount is a credit.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS enables 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.
This PDS is required for the Financial Detail Addendum (Shipping/Courier Services)/1644
message when the conditions apply:
• One of these MCCs is present in DE 26 (Acceptor Business Code [MCC]):
– 4214: Motor Freight Carriers, Trucking; Local/Long Distance, Moving and Storage
Companies, Local Delivery
– 4215: Courier Services; Air and Ground, Freight Forwards
• The Financial Detail Addendum (Corporate Line Item Detail)/1644 message is not present.
• The transaction is submitted for any of the interchange programs listed in these tables.
IRD Description
BR Canada Intracountry Commercial Data Rate II
BS Canada Intracountry Commercial Large Ticket
IRD Description
62 Commercial Large Ticket 1
66 Commercial Data Rate III
94 Commercial Large Ticket II
99 Commercial Large Ticket III
SC Business Level 2 Data Rate III
SE Business Level 2 Large Ticket I
SF Business Level 2 Large Ticket II
SG Business Level 2 Large Ticket III
3C Business Level 3 Data Rate III
3E Business Level 3 Large Ticket I
3F Business Level 3 Large Ticket II
3G Business Level 3 Large Ticket III
4C Business Level 4 Data Rate III
4E Business Level 4 Large Ticket I
4F Business Level 4 Large Ticket II
4G Business Level 4 Large Ticket III
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.
Value Description
1 Name
2 Title
3 Telephone
4 E-mail address
5 Function
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
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 these
subfields:
• PDS 0627 (Billing Event 1), subfield 1 (Billing Event Amount) (occurs 1 to 10 times)
• PDS 0628 (Billing Event 2), subfield 1 (Billing Event Amount 2) (occurs 1 to 10 times), and
• PDS 0597 (Total Tax Amount), 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
these subfields:
• PDS 0649 (Call Usage Amount), subfield 1 (Call Usage Amount)
• PDS 0655 (Call Long Distance Amount), subfield 1 (Call Long Distance Amount)
• PDS 0658 (Call Connect Amount), subfield 1 (Call Collect Amount)
• PDS 0734 (Miscellaneous Expenses), subfield 2 (Miscellaneous Expense Amount), and
• PDS 0597 (Total Tax Amount), subfield 1 (Total Tax Amount) (which is the sum of all six of
the tax-related PDSs).
NOTE: Financial Detail Addendum/1644 messages that contain amounts and amount exponents
should utilize the same currency and exponent of the Amount, Transaction in the associated First
Presentment/1240 message.
Value Description
D Line item total amount is a debit.
C Line item total amount is a credit.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS is required if the associated First Presentment/1240 contains an airline acceptor
business code (MCC) or railway MCC and is submitted for the U.S. region incentive interchange
rate programs listed in this table.
IRD Description
22 Public Sector
29 Emerging Markets, Consumer Core Value
56 World Public Sector
HP World High Value Public Sector
RK Enhanced Public Sector
WP World Elite Public Sector
Subfield 3 (Class)
If PDS 0756 is present, subfield 3 must be provided. This PDS is required if the associated First
Presentment/1240 contains a railway MCC and is submitted for one of the U.S. region incentive
interchange rate programs listed in this table.
IRD Description
10 Merit III Tier 1
11 Merit III Tier 2
12 Merit III Tier 3
24 Merchant UCAF
69 Commercial T&E Rate II
70/80 Merit III Base
79 Full UCAF
89 Commercial T&E Rate III
93 Passenger Transport
96 World T&E
RA Enhanced Merit III Base
RB Enhanced Merit III Tier 1
RC Enhanced Merit III Tier 2
RD Enhanced Merit III Tier 3
RN Enhanced Merchant UCAF
RO Enhanced Full UCAF
RR Enhanced Passenger Transport
SO Business Level 2 T&E Rate III
3O Business Level 3 T&E Rate III
4O Business Level 4 T&E Rate III
If present, this PDS cannot contain all high values or all low values.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, this PDS must be left-justified and cannot contain all zeros, all spaces, all high values,
or all low values.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, this PDS must be left-justified and cannot contain all zeros, all spaces, all high values,
or all low values.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, this PDS must be left-justified and cannot contain all zeros, all spaces, all high values,
or all low values.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, this PDS must be left-justified and cannot contain all zeros, all spaces, all high values,
or all low values.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, this PDS must be left-justified and cannot contain all zeros, all spaces, all high values,
or all low values.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, this PDS must contain one of the valid values listed in this table.
Valid Values
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
If present, this PDS must be left-justified, cannot contain all zeros, all spaces, all high values, or
all low values. The common values are DR (Deutsches Reisebüro) or ST (ST Art Amadeus).
Attributes
Usage
This table shows the usage of this data element (whether it is mandatory, conditional, optional,
system-provided, or not required) in applicable messages.
Usage
Values
This PDS must contain a valid value listed in this table.
Values
Value Description
0 Non-qualified healthcare item
1 Qualified healthcare item
Attributes
Usage
This table shows the usage of this data element (whether it is mandatory, conditional, optional,
system-provided, or not required) in applicable messages.
Usage
PDS 0765 subfields 01 and 02 must be present in a Financial Detail Addendum (Payment
Transaction Detail)/1644 message when Payment Transactions (identified by DE 3 [Processing
Code], subfield 01 [Cardholder Transaction Type] value of 28) contains PDS 0043 (Program
Registration ID) with a value of C04, C07, C52, C53, C54, C55, C56, C57 C58, C59, or C65 and
the transaction qualifies as a crossborder Moneysend payment transaction.
Values
If present, each PDS 0765 subfield must be left-justified and cannot contain all low values or all
high values. Subfields 01 and 02 cannot contain all spaces or all zeros. Subfield 3, 4, 5, 6, 7, 8,
and 9 are optional fields.
Attributes
Attribute Value
Subfield ID n-2 01
Subfield Length n-2 35
Data Representation ans-35
Justification Left
Attributes
Attribute Value
Subfield ID n-2 02
Subfield Length n-2 35
Data Representation ans-35
Justification Left
Attributes
Attribute Value
Subfield ID n-2 03
Subfield Length n-2 30
Data Representation ans-30
Justification Left
Attributes
Attribute Value
Subfield ID n-2 04
Subfield Length n-2 25
Data Representation ans-25
Justification Left
Attribute Value
Subfield ID n-2 05
Subfield Length n-2 03
Data Representation ans-3
Justification Left
Attributes
Attribute Value
Subfield ID n-2 06
Subfield Length n-2 03
Data Representation ans-3
Justification Left
Attributes
Attribute Value
Subfield ID n-2 07
Subfield Length n-2 10
Data Representation ans-10
Justification Left
Attributes
Attribute Value
Subfield ID n-2 08
Subfield Length n-2 08
Attribute Value
Data Representation n-8
Justification Left
Attributes
Attribute Value
Subfield ID: n-2 09
Subfield Length: n-2 20
Data Representation: ans-20
Justification: Left
Attributes
Usage
This table shows the usage of this data element (whether it is mandatory, conditional, optional,
system-provided, or not required) in applicable messages.
Usage
Values
If present, PDS 0770 cannot contain all low values, all high values, all spaces, or all zeros and
must be a length of 025–073.
Attributes
Usage
Application notes
The Clearing system provides PDS 0010 to the issuer if the account range participates in the
Currency Rate service and the transaction qualifies for the service.
Attributes
Usage
This table shows the usage of this data element (whether it is mandatory, conditional, optional,
system-provided, or not required) in applicable messages.
Usage
Values
If present, PDS 0771 must be a length of 18–36.
Attributes
Subfields: 2
Justification: See “Subfields”
Usage
This table shows the usage of this data element (whether it is mandatory, conditional, optional,
system-provided, or not required) in applicable messages.
Usage
Values
If present, PDS 0772 must be a length of 15–18.
If present, subfield 2 must be left-justified and cannot contain all low values, all high values, all
spaces, or all zeros.
Attributes
Usage
This table shows the usage of this data element (whether it is mandatory, conditional, optional,
system-provided, or not required) in applicable messages.
Usage
Values
If present, PDS 0772 must be a length of 14–140, and divisible by a minimum occurrence length
of 14.
Value Description
01 Credit Card
02 Debit Card
03 Gift Card
04 Cash
05 Check
06 Coupon
07 Other
Attributes
Usage
This table shows the usage of this data element (whether it is mandatory, conditional, optional,
system-provided, or not required) in applicable messages.
Usage
Values
If present, PDS 0774 must be left-justified and cannot contain all low values, all high values, all
spaces, or all zeros and must be a length of 1–200.
Attributes
Usage
This table shows the usage of this data element (whether it is mandatory, conditional, optional,
system-provided, or not required) in applicable messages.
Usage
Values
If present, PDS 0775 must be left-justified and cannot contain all low values, all high values, all
spaces, or all zeros and must be a length of 1–8.
Attributes
Usage
This table shows the usage of this data element (whether it is mandatory, conditional, optional,
system-provided, or not required) in applicable messages.
Usage
Values
If PDS 0776 is present, both subfield 1 and subfield 2 must be present in each occurrence of
Alternate Custom Identifier, and the PDS must be a length of 82–410 and divisible by a
minimum occurrence length of 82.
Value Description
CUSORD Customer Order
CUSTPO Customer Purchase Order
FOLNUM Folio Number
INVACT Invoice or Account Number
OTHER1 Other
OTHER2 Other
PRCHID Purchase Identification
RECLOC Record Locator
RESNUM Reservation Number
RNTAGR Rental Agreement
SUPINV Supplier Invoice
SUPORD Supplier Order
TKTNUM Ticket Number
TRANID Transaction Identification
TRKNUM Tracking Number
Attributes
Usage
This table shows the usage of this data element (whether it is mandatory, conditional, optional,
system-provided, or not required) in applicable messages.
Usage
Values
If present, PDS 0777 must be left-justified and cannot contain all low values, all high values, all
spaces, or all zeros and must be a length of 1–6.
Values
Values Description
ARGCTA Installment payment transaction within Argentina
AGROF1 Mastercard Agro Card
BNDES1 Brazil intracountry transactions using the Mastercard BNDES Card
COLCTA Installment payment transaction within Colombia
GREECE Installment payment transaction within Greece
HGMINS Installment payment transaction for Croatia, Czech Republic,
Georgia, Hungary, Romania, Serbia, Slovakia, Slovenia, and Ukraine
MCGARS Identifies Global Automated Service (GARS) Stand-In activity
MCINST Mastercard Installment Payment
MEXCTA Installment payment transaction within Mexico
PARCEL Installment payment transaction within Brazil
Values Description
PERCTA Installment payment transaction within Peru
PHINST Installment payment transaction within Philippines
PRYCTA Installment payment transaction within Paraguay
URYCTA Installment payment transaction within Uruguay
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
PDS 0781 is used to inform issuers of the purchase restrictions enforced by the merchant point
of sale. PDS 0781 should contain the Conexxus Purchase Restriction Tag information value
found in tag DF32 read from the EMV chip.
Usage of PDS 0781 is required only for EMV chip cards personalized using the IFSF/Conexxus
specification for retrieving supplemental data from acceptors and cardholders.
Alternate flow
In scenarios where the merchant supports the Dual Message Authorization field DE 106,
subelement 02 Merchant Fleet Spend Control Override Capability and the issuer provides a
response value in Dual Message Authorization field DE 106, subelement 3 (Fleet Spend Control
Override Items) in the Authorization Request Response/0110 message, which is enforced by the
merchant at the point of sale, then that spend control data will be populated in PDS 0781.
PDS 0781 should be formatted as read from the EMV chip or provided in authorization in DE
106, subelement 03 (Fleet Spend Control Override Items) which is formatted according to
Conexxus standards.
Values
If present, PDS 0781 must be a fixed length of 16 and cannot contain all zeros or all spaces.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Usage of PDS 0782 is required only for EMV chip cards personalized using the IFSF/Conexxus
specification for retrieving supplemental data from acceptors and cardholders.
This PDS must be present in the Financial Detail Addendum (Corporate Fleet Transaction
Information)/1644 message when PDS 0622 (Motor Fuel Service Type) is present and contains
a value other than 3 for the following U.S.-acquired commercial interchange rate programs.
IRD Description
F1 Commercial Fleet Data Rate I
F2 Commercial Fleet Data Rate II
FL Commercial Fleet Large Ticket
Values
If present, PDS 0782 Fleet Fuel Information must be a fixed length of 35.
Requirements
These are the requirements regulating the use of PDS 0782.
For Mastercard Corporate Fleet Card or Mastercard Government Commercial Card
transactions, PDS 0782, subfield 6 (Fleet Fuel Sale Amount) must equal the product of the
value of PDS 0782, subfield 2 (Fleet Fuel Unit Price) multiplied by the value in PDS 0782,
subfield 4 (Fleet Fuel Quantity). A tolerance of five percent is permitted to address rounding
issues. The tolerance is applied on PDS 0782, subfield 6 (Sale Amount) and not on the
calculated value (PDS 0782, subfield 2 multiplied by PDS 0782, subfield 4). Also, this edit does
not round the calculated amount and low/high tolerance amounts to the transaction currency
exponent, and keeps six decimal positions on these values.
Subfields
PDS 0782 contains six subfields.
Value Description
001 Regular
002 Mid/Plus
003 Premium/Super
004 Mid/Plus 2
005 Premium/Super 2
011 <Deprecated> Ethanol (5.7% blend)
012 <Deprecated> Mid/Plus Ethanol (5.7% blend)
013 <Deprecated> Premium/Super Ethanol (5.7%
blend)
014 <Deprecated> Ethanol (7.7% blend)
015 <Deprecated> Mid/Plus Ethanol (7.7% blend)
016 Green Gasoline Regular (Plant based not petroleum
based)
Value Description
017 Green Gasoline Mid/Plus (Plant based not
petroleum based)
018 Green Gasoline Premium/Super (Plant based not
petroleum based)
019 Regular Diesel #2
020 Premium Diesel #2
021 Regular Diesel #1
022 Compressed Natural Gas
023 Liquid Propane Gas
024 Liquid Natural Gas
026 E-85
027 Reformulated 1
028 Reformulated 2
029 Reformulated 3
030 Reformulated 4
031 Reformulated 5
032 Diesel Off-Road (#1 and #2 Non-Taxable)
033 Diesel Off-Road (Non-Taxable)
034 Biodiesel Blend Off-Road (Non-Taxable)
035 Undefined Fuel - Reserved for Conexxus Future
036 Racing Fuel
037 Mid/Plus 2 (10% Blend)
038 Premium/Super 2 (10% Blend)
039 Mid/Plus Ethanol 2 (15% Blend)
040 Premium/Super Ethanol 2 (15% Blend)
041 <Deprecated> Premium/Super Ethanol (7.7%
Blend)
042 Regular Ethanol (10% Blend)
043 Mid/Plus Ethanol (10% Blend)
044 Premium/Super Ethanol (10% Blend)
045 B2 Diesel Blend 2% Biodiesel
046 B5 Diesel Blend 5% Biodiesel
Value Description
047 B10 Diesel Blend 10% Biodiesel
048 B11 Diesel Blend 11% Biodiesel
049 B15 Diesel Blend 15% Biodiesel
050 B20 Diesel Blend 20% Biodiesel
051 B100 Diesel Blend 100% Biodiesel
052 B1 Diesel Blend 1% Biodiesel
053 Additized Diesel #2
054 Additized Diesel #3
060 Renewable Diesel (>=R95) (meets ASTM D975 in
US / EN 590 in Europe)
061 Renewable Diesel (Biodiesel 6%-20%) (meets
ASTM D7467 in US)
062 DEF (Diesel Exhaust Fluid)
063 Premium Diesel #1
064 Regular Ethanol (15% Blend)
065 Mid/Plus Ethanol (15% Blend)
066 Premium/Super Ethanol (15% Blend)
067 Premium Diesel Blend <20% Biodiesel
068 Premium Diesel Blend >= 20% Biodiesel
069 B75 Diesel Blend 75% Biodiesel
070 B99 Diesel Blend 99% Biodiesel
099 Miscellaneous Fuel
150 Jet Fuel
151 Aviation Fuel Regular
152 Aviation Fuel Premium
153 Aviation Fuel JP8
154 Aviation Fuel 4
155 Aviation Fuel 5
156 Biojet (Diesel)
157 Aviation Biofuel (Gasoline)
174 Miscellaneous Aviation Fuel
Value Description
225 Marine Fuel 1
226 Marine Fuel 2
227 Marine Fuel 3
228 Marine Fuel 4
229 Marine Fuel 5
230 Marine - Other
231 Marine Diesel
249 Miscellaneous Marine Fuel
300 Kerosene – Low Sulfur
301 White Gas
302 Heating Oil
304 Other Fuel (Non-Taxable)
305 Kerosene – Ultra Low Sulfur
306 Kerosene – Low Sulfur (Non-Taxable)
307 Kerosene – Ultra Low Sulfur (Non-Taxable)
308 EVC-1 – Level 1 charge = 110v 15 amp
309 EVC-2 – Level 2 charge = 240v 15-40 amp
310 EVC-3 – Level 3 charge = 480v 3 phase charge
311 Biodiesel Blend 2% Off-Road (Non-Taxable)
312 Biodiesel Blend 5% Off-Road (Non-Taxable)
313 Biodiesel Blend 10% Off-Road (Non-Taxable)
314 Biodiesel Blend 11% Off-Road (Non-Taxable)
315 Biodiesel Blend 15% Off-Road (Non-Taxable)
316 Biodiesel Blend 20% Off-Road (Non-Taxable)
317 Diesel #1 Off-Road (Non-Taxable)
318 Diesel #2 Off-Road (Non-Taxable)
319 Diesel #1 Premium Off-Road (Non-Taxable)
320 Diesel #2 Premium Off-Road (Non-Taxable)
321 Additive Dosage
322 Ethanol Blends E16-E84
323 Low Octane UNL
Value Description
324 Blended Diesel (#1 and #2)
325 Off-Road Regular (Non-Taxable)
326 Off-Road Mid/Plus (Non-Taxable)
327 Off-Road Premium/Super (Non-Taxable)
328 Off-Road Mid/Plus 2 (Non-Taxable)
329 Off-Road Premium/Super 2 (Non-Taxable)
330 Recreational Fuel (90 Octane)
331 Hydrogen H35
332 Hydrogen H70
333 Renewable Diesel (>=R95) Off-Road (Non-Taxable)
(meets ASTM D975 in US / EN 590 in Europe)
334 Biodiesel Blend 1% Off-Road (Non-Taxable)
335 Biodiesel Blend 75% Off-Road (Non-Taxable)
336 Biodiesel Blend 99% Off-Road (Non-Taxable)
337 Biodiesel Blend 100% Off-Road (Non-Taxable)
338 Renewable Diesel (Biodiesel 6%-20%) Off-Road
(Non-taxable) (meets ASTM D7467 in US)
399 Miscellaneous Other Fuel
Value Description
1 Gallons
2 Liters
3 Pounds
Value Description
4 Kilos
5 Imperial gallons
6 Kilowatt hour
7 Minutes
8 Hours
Space Not Applicable
Attributes
Justification: Left
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
The Fleet Product Code should be provided for Fleet card transactions occurring at fuel
locations, when PDS 0622 (Motor Fuel Service Type) is a value of 3.
Usage of PDS 0783 is required only for EMV chip cards personalized using the IFSF/Conexxus
specification for retrieving supplemental data from acceptors and cardholders.
PDS 0783 (Fleet Product Code) must be present in the Financial Detail Addendum (Corporate
Line Item Detail)/1644 message for Fleet Card product MCF and MGF transactions when all
these conditions occur.
• DE 26 (Acceptor Business Code [MCC]) contains one of the following Fleet non-fuel
maintenance location MCCs: 5013, 5511, 5531, 5532, 5533, 5599, 7531, 7534, 7535, 7538,
7542, 7549, 7692, or 7699
• Transaction qualifies for the U.S. Region business service arrangement 2/010001 where PDS
0158, subfield 2 is equal to 2 and PDS 0158, subfield 3 is equal to 010001.
• First Presentment/1240 is submitted with one of the IRDs listed in this table.
IRD Description
F3 Commercial Fleet Data Rate III
FL Commercial Fleet Large Ticket
PDS 0783 (Fleet Product Code) must be present in the Financial Detail Addendum (Corporate
Line Item Detail)/1644 message for Fleet Card product MCF and MGF transactions when all
these conditions occur:
• DE 26 (Acceptor Business Code [MCC]) contains one of the following Fleet fuel location
MCCs: 4468, 5499, 5541, 5552, or 5983
• PDS 0622 (Motor Fuel Service Type) is present with a value of 3 (Only non-fuel items being
purchased) in the Financial Detail Addendum (Corporate Fleet Transaction Information)/
1644 message.
• Transaction qualifies for the U.S. Region business service arrangement 2/010001 where PDS
0158, subfield 2 is equal to 2 and PDS 0158, subfield 3 is equal to 010001.
• First Presentment/1240 is submitted with one of the IRDs listed in this table.
IRD Description
F1 Commercial Fleet Data Rate I
F2 Commercial Fleet Data Rate II
FL Commercial Fleet Large Ticket
Values
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 or
Mastercard Government Commercial Card at a non-fuel location, PDS 0783 should be provided
and must contain a three-position non-fuel product code listed in this table.
The following list of product code values is based on the Conexxus Payment System Product
Codes version 4.1.
Value Description
100 General Automotive Merchandise
101 Motor Oil
102 Car Wash
103 Oil Change
104 Oil Filter
105 Work Order
106 Anti-Freeze
107 Washer Fluid
108 Brake Fluid
109 Tires
110 Federal Excise Tax (Tires)
111 Tire Rotation
Value Description
112 Batteries
113 Lube
114 Inspection
115 Labor
116 Towing
117 Road Service
118 Vehicle Accessories
119 Vehicle Parts
120 Preventative Maintenance
121 Air Conditioning Service
122 Engine Service
123 Transmission Service
124 Brake Service
125 Exhaust Service
126 Body Work
127 Vehicle Glass
128 Synthetic Oil
129 Lamps
130 Wipers
131 Hoses
132 Tire-related (Wheel Balance, Valve Stem)
133 Repairs
134 Service Package
135 Vehicle Parking
136 Truck Tank Cleaning
137 Other Lubricants
138 Vehicle Fuel Additives/Treatment (Injected)
139 Vehicle Rental
140 Air Filter
141 Vehicle Prep
142 Fuel System
Value Description
149 Miscellaneous Vehicle Products / Services
175 Storage
176 Aircraft Ground Handling
177 Aircraft Ground Power Unit
178 Aircraft Labor
179 Aircraft Work Order
180 Aircraft Maintenance
181 Aircraft Service
182 Transportation
183 De-icing
184 Ramp Fees
185 Catering
186 Hangar Fee
187 Landing Fee
188 Call Out Fee
189 Aircraft Rental
190 Instruction Fee
191 Flight Plans / Weather Brief
192 Charter Fee
193 Communication Fee
194 Aircraft Cleaning
195 Cargo Handling
196 Aircraft Accessories
197 Pilot Supplies
198 Aircraft Parking Fees
199 Aircraft Tie Down Fees
200 Aircraft Sanitation Fees
201 Aircraft Fuel Additive
202 AC Parts
203 Oxygen
204 De-fuel
Value Description
205 Re-service
206 Static Dissipater Additive
207 Corrosion Inhibitor
208 Airport Fees
209 Overtime Fees
210 IT/Bladder
211 Ground Equipment Service Fees
212 Secure Fees
213 Flow Fee
224 Miscellaneous Aviation Products/Services
250 Marine Service
251 Marine Labor
252 Marine Work Order
253 Launch Fee
254 Slip Rental
400 General Merchandise
401 General Ice
410 General Tobacco
411 Cigarettes
412 Tobacco - Other
420 General Packaged Beverage
421 Packaged Beverages (non-alcoholic)
422 Packaged Juice
423 Other Packaged Beverages
430 General Dispensed Beverage
431 Hot Dispensed Beverages
432 Cold Dispensed Beverages
433 Frozen Dispensed Beverages
434 Other Dispensed Beverages
440 General Snacks
441 Salty Snacks
Value Description
442 Alternative Snacks
443 Sweet Snacks - Packaged
450 General Candy
460 General Dairy
461 Fluid Milk Products
462 Packaged Ice Cream/Novelties
463 Other Dairy
470 General Grocery
471 Groceries - Edible
472 Groceries - Non-Edible
473 Groceries - Perishable
474 Bread - Packaged
475 Frozen Foods
480 General Alcohol
481 Beer - Alcoholic
482 Beer - Non-Alcoholic
483 Wine
484 Liquor
490 General Deli
491 Packaged Sandwiches/Deli Products
492 Prepared Foods
493 Deli Items
500 General Food service
510 General Lottery
511 Lottery - Instant
512 Lottery - Online
513 Lottery - Other
520 General Money Order
521 Money Order - Vendor Payment
522 Money Order - Payroll Check
523 Money Order - Gift Certificate
Value Description
524 Money Order - Refund Check
525 Money Order - Official Check
526 Money Order - Rebate Check
527 Money Order - Dividend Check
528 Money Order - Utility Check
530 General Store Service
531 Home Delivery
532 Prepaid Cards - Purchase
533 Prepaid Cards - Activation/Recharge
534 Membership/Loyalty
540 General Health & Beauty Care
550 General Publications
560 PIN Activate Prepaid Card
561 PIN Return Prepaid Card
562 Enable Device/Handset Unlock
563 Disable Device/Handset Lock
564 3rd Party Prepaid Card Activate
565 3rd Party Prepaid Card Reload
566 Financial Prepaid Card Activate
567 Financial Prepaid Card Reload
568 Proprietary Prepaid Card Activate
569 Proprietary Prepaid Card Reload
570 General Purpose Activate
571 General Purpose Reload
572 Real Time Recharge
573 Wireless Real Time Recharge
574 Single Payee Bill Pay
575 Multiple Payee Bill Pay
600 Packaged DEF (Diesel Exhaust Fluid)
601 Packaged B99
602 Packaged B100
Value Description
603 Packaged Additive
604 Packaged Kerosene
605 Packaged Propane
624 Miscellaneous Packaged Fuels
650 Scales
651 Shower
652 Tire Repair
653 Lodging
654 Wash Out
655 Trailer Wash
656 RV Dump Fee
657 EV Charging Fee
658 EV Battery Exchanges
659 Toll Payments
700 Cannabidiol (CBD)
900 Discount 1
901 Discount 2
902 Discount 3
903 Discount 4
904 Discount 5
905 Coupon 1
906 Coupon 2
907 Coupon 3
908 Coupon 4
909 Coupon 5
910 Lottery Pay Out - Instant
911 Lottery Pay Out - Online
912 Lottery Pay Out - Other
913 Split Tender
914 Tax Discount/Forgiven
915 Local Discount 1
Value Description
916 Local Discount 2
917 Local Discount 3
918 Local Discount 4
919 Local Discount 5
920 POS/Loyalty Reserved Discount 1
921 POS/Loyalty Reserved Discount 2
922 POS/Loyalty Reserved Discount 3
923 POS/Loyalty Reserved Discount 4
924 POS/Loyalty Reserved Discount 5
949 Miscellaneous Negative Administrative
950 Tax 1
951 Tax 2
952 Tax 3
953 Tax 4
954 Tax 5
955 Cash Back
956 Cash Back Fee
957 Fee 1
958 Fee 2
959 Fee 3
960 Fee 4
961 Fee 5
962 Miscellaneous Aviation Tax
963 GST/HST (Canadian)/VAT 1
964 PST/QST (Canadian) VAT 2
965 SWT Rate (Canadian)
966 Tax 6
967 Tax 7
968 Tax 8
969 Jet Federal Excise Tax
970 AvGas Federal Excise Tax
Value Description
971 Charity
972 Gratuity
999 Miscellaneous Administrative
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
PDS 0784 (Fleet Item Description) should be present in the Financial Detail Addendum
(Corporate Line-Item Detail)/1644 message when PDS 0622 (Motor Fuel Service Type) is
present with a value of 3 (Only non-fuel items being purchased) in the Financial Detail
Addendum (Corporate Fleet Transaction Information)/1644 message.
Usage of PDS 0784 is required only for EMV chip cards personalized using the IFSF/Conexxus
specification for retrieving supplemental data from acceptors and cardholders.
PDS 0784 (Fleet Item Description) must be present in the Financial Detail Addendum
(Corporate Line Item Detail)/1644 message for Fleet Card product MCF and MGF transactions
when all these conditions occur.
• DE 26 (Acceptor Business Code [MCC]) contains one of the following Fleet non-fuel
maintenance location MCCs: 5013, 5511, 5531, 5532, 5533, 5599, 7531, 7534, 7535, 7538,
7542, 7549, 7692, or 7699
• Transaction qualifies for the U.S. Region business service arrangement 2/010001 where PDS
0158, subfield 2 is equal to 2 and PDS 0158, subfield 3 is equal to 010001.
• First Presentment/1240 is submitted with one of the IRDs listed in this table.
IRD Description
F3 Commercial Fleet Data Rate III
FL Commercial Fleet Large Ticket
PDS 0784 (Fleet Item Description) must be present in the Financial Detail Addendum
(Corporate Line Item Detail)/1644 message for Fleet Card product MCF and MGF transactions
when all these conditions occur.
• DE 26 (Acceptor Business Code [MCC]) contains one of the following Fleet fuel location
MCCs: 4468, 5499, 5541, 5552, or 5983.
• PDS 0622 (Motor Fuel Service Type) is present with a value of 3 (Only non-fuel items being
purchased) in the Financial Detail Addendum (Corporate Fleet Transaction Information)/
1644 message.
• Transaction qualifies for the U.S. Region business service arrangement 2/010001 where PDS
0158, subfield 2 is equal to 2 and PDS 0158, subfield 3 is equal to 010001.
• First Presentment/1240 is submitted with one of the IRDs listed in this table.
IRD Description
F1 Commercial Fleet Data Rate I
F2 Commercial Fleet Data Rate II
FL Commercial Fleet Large Ticket
Values
PDS 0784 must be left justified, cannot contain all spaces, and a minimum length of 1 and a
maximum length of 35.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
PDS 0785 (Fleet Item Quantity) should be present in the Financial Detail Addendum (Corporate
Line-Item Detail)/1644 message when PDS 0622 (Motor Fuel Service Type) is present with a
value of 3 (Only non-fuel items being purchased) in the Financial Detail Addendum (Corporate
Fleet Transaction Information)/1644 message.
Usage of PDS 0785 is required only for EMV chip cards personalized using the IFSF/Conexxus
specification for retrieving supplemental data from acceptors and cardholders.
PDS 0785 (Fleet Item Quantity) must be present in the Financial Detail Addendum (Corporate
Line Item Detail)/1644 message for Fleet Card product MCF and MGF transactions when all
these conditions occur.
• DE 26 (Acceptor Business Code [MCC]) contains one of the following Fleet non-fuel
maintenance location MCCs: 5013, 5511, 5531, 5532, 5533, 5599, 7531, 7534, 7535, 7538,
7542, 7549, 7692, or 7699.
• Transaction qualifies for the U.S. Region business service arrangement 2/010001 where PDS
0158, subfield 2 is equal to 2 and PDS 0158, subfield 3 is equal to 010001.
• First Presentment/1240 is submitted with one of the IRDs listed in this table.
IRD Description
F3 Commercial Fleet Data Rate III
FL Commercial Fleet Large Ticket
PDS 0785 (Fleet Item Quantity) must be present in the Financial Detail Addendum (Corporate
Line Item Detail)/1644 message for Fleet Card product MCF and MGF transactions when all
these conditions occur.
• DE 26 (Acceptor Business Code [MCC]) contains one of the following Fleet fuel location
MCCs: 4468, 5499, 5541, 5552, or 5983.
• PDS 0622 (Motor Fuel Service Type) is present with a value of 3 (Only non-fuel items being
purchased) in the Financial Detail Addendum (Corporate Fleet Transaction Information)/
1644 message.
• Transaction qualifies for the U.S. Region business service arrangement 2/010001 where PDS
0158, subfield 2 is equal to 2 and PDS 0158, subfield 3 is equal to 010001.
• First Presentment/1240 is submitted with one of the IRDs listed in this table.
IRD Description
F1 Commercial Fleet Data Rate I
F2 Commercial Fleet Data Rate II
FL Commercial Fleet Large Ticket
Values
PDS 0785 must be a fixed length of 13.
Subfields
PDS 0785 consists of two subfields. PDS 0785 subfields are listed in this table.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
PDS 0786 (Fleet Item Unit of Measure) should be present in the Financial Detail Addendum
(Corporate Line-Item Detail)/1644 message when PDS 0622 (Motor Fuel Service Type) is
present with a value of 3 (Only non-fuel items being purchased) in the Financial Detail
Addendum (Corporate Fleet Transaction Information)/1644 message.
Usage of PDS 0786 is required only for EMV chip cards personalized using the IFSF/Conexxus
specification for retrieving supplemental data from acceptors and cardholders.
PDS 0786 (Fleet Item Unit of Measure) must be present in the Financial Detail Addendum
(Corporate Line Item Detail)/1644 message for Fleet Card product MCF and MGF transactions
when all these conditions occur.
• DE 26 (Acceptor Business Code [MCC]) contains one of the following Fleet non-fuel
maintenance location MCCs: 5013, 5511, 5531, 5532, 5533, 5599, 7531, 7534, 7535, 7538,
7542, 7549, 7692, or 7699.
• Transaction qualifies for the U.S. Region business service arrangement 2/010001 where PDS
0158, subfield 2 is equal to 2 and PDS 0158, subfield 3 is equal to 010001.
• First Presentment/1240 is submitted with one of the IRDs listed in this table.
IRD Description
F3 Commercial Fleet Data Rate III
FL Commercial Fleet Large Ticket
PDS 0786 (Fleet Item Unit of Measure) must be present in the Financial Detail Addendum
(Corporate Line Item Detail)/1644 message for Fleet Card product MCF and MGF transactions
when all these conditions occur.
• DE 26 (Acceptor Business Code [MCC]) contains one of the following Fleet fuel location
MCCs: 4468, 5499, 5541, 5552, or 5983.
• PDS 0622 (Motor Fuel Service Type) is present with a value of 3 (Only non-fuel items being
purchased) in the Financial Detail Addendum (Corporate Fleet Transaction Information)/
1644 message.
• Transaction qualifies for the U.S. Region business service arrangement 2/010001 where PDS
0158, subfield 2 is equal to 2 and PDS 0158, subfield 3 is equal to 010001.
• First Presentment/1240 is submitted with one of the IRDs listed in this table.
IRD Description
F1 Commercial Fleet Data Rate I
F2 Commercial Fleet Data Rate II
FL Commercial Fleet Large Ticket
Values
If present, PDS 0786 cannot contain all zeros, all spaces and must be a minimum length of 1
and a maximum length of 12.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
PDS 0787 (Fleet Item Quantity) should be present in the Financial Detail Addendum (Corporate
Line-Item Detail)/1644 message when PDS 0622 (Motor Fuel Service Type) is present with a
value of 3 (Only non-fuel items being purchased) in the Financial Detail Addendum (Corporate
Fleet Transaction Information)/1644 message.
Usage of PDS 0787 is required only for EMV chip cards personalized using the IFSF/Conexxus
specification for retrieving supplemental data from acceptors and cardholders.
PDS 0787 (Fleet Extended Item Amount) must be present in the Financial Detail Addendum
(Corporate Line Item Detail)/1644 message for Fleet Card product MCF and MGF transactions
when all these conditions occur.
• DE 26 (Acceptor Business Code [MCC]) contains one of the following Fleet non-fuel
maintenance location MCCs: 5013, 5511, 5531, 5532, 5533, 5599, 7531, 7534, 7535, 7538,
7542, 7549, 7692, or 7699.
• Transaction qualifies for the U.S. Region business service arrangement 2/010001 where PDS
0158, subfield 2 is equal to 2 and PDS 0158, subfield 3 is equal to 010001.
• First Presentment/1240 is submitted with one of the IRDs listed in this table.
IRD Description
F3 Commercial Fleet Data Rate III
FL Commercial Fleet Large Ticket
PDS 0787 (Fleet Extended Item Amount) must be present in the Financial Detail Addendum
(Corporate Line Item Detail)/1644 message for Fleet Card product MCF and MGF transactions
when all these conditions occur.
• DE 26 (Acceptor Business Code [MCC]) contains one of the following Fleet fuel location
MCCs: 4468, 5499, 5541, 5552, or 5983.
• PDS 0622 (Motor Fuel Service Type) is present with a value of 3 (Only non-fuel items being
purchased) in the Financial Detail Addendum (Corporate Fleet Transaction Information)/
1644 message.
• Transaction qualifies for the U.S. Region business service arrangement 2/010001 where PDS
0158, subfield 2 is equal to 2 and PDS 0158, subfield 3 is equal to 010001.
• First Presentment/1240 is submitted with one of the IRDs listed in this table.
IRD Description
F1 Commercial Fleet Data Rate I
F2 Commercial Fleet Data Rate II
FL Commercial Fleet Large Ticket
Values
If present, PDS 0787 must be a fixed length of 014.
To allow for situations in which the item is zero cost to the customer, PDS 0650 (Zero Cost to
Customer) must also be present in the Corporate Line Item Detail Addendum message, and
equal to Y. PDS 0787 subfield 1 may contain zero in this circumstance.
Subfields
PDS 0787 consists of three subfields. PDS 0787 subfields are listed in this table.
NOTE: Financial Detail Addendum/1644 messages that contain amounts and amounts exponents
should use the same currency and exponent of the Amount, Transaction in the associated First
Presentment/1240 message.
Value Description
D Extended item amount is a debit.
C Extended item amount is a credit.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Usage of PDS 0790 is required only for EMV chip cards personalized using the IFSF/Conexxus
specification for retrieving supplemental data from acceptors and cardholders.
PDS 0790 (Fleet Prompted Data 1) must be present in the Financial Detail Addendum
(Corporate Fleet Transaction Information)/1644 message for Fleet Card product MCF and MGF
transactions when all these conditions occur.
• DE 26 (Acceptor Business Code [MCC]) contains one of the following Fleet fuel location
MCCs: 4468, 5499, 5541, 5542, or 5983.
• Transaction qualifies for the U.S. Region business service arrangement 2/010001 where PDS
0158, subfield 2 is equal to 2 and PDS 0158, subfield 3 is equal to 010001.
• First Presentment/1240 is submitted with one of the IRDs listed in this table.
IRD Description
F2 Commercial Fleet Data Rate II
FL Commercial Fleet Large Ticket
Values
If present, PDS 0790 must be variable length of 4-38 positions.
Subfields
PDS 0790 consists of two subfields. PDS 0790 subfields are listed in this table.
Value Description
001 User ID
002 Vehicle Number
003 Vehicle Tag
004 Driver ID
005 Odometer
009 Work Order / P.O. Number
010 Invoice Number
011 Trip Number
012 Unit Number
013 Reefer Hours
015 ZIP Code / Postal Code
016 Replacement Car
017 Entered Data Num
018 Web Portal Data
019 Entered Data Alpha
021 Job Number
022 Maintenance ID
023 Department Number
024 Trailer Number
025 Delivery Ticket Number
026 Hubometer
033 Sub Fleet Number
035 Transaction Number
036 Control Number
Value Description
038 Reefer Temperature
040 Driver or Vehicle Card
041 Customer Number
042 Additional Card Data
043 Additional Vehicle Data
044 Engine Hours
045 Tank Level Start
046 Fuel Gauge Level
047 Battery Voltage
048 Coolant Temperature
049 Check Engine Status
050 Fuel Economy
051 Engine RPM
052 Engine Load
053 Engine Oil Temperature
054 Engine Time Total
055 Hard Breaking
056 Hard Acceleration
058 Idle Time
065 Total Idle Time
067 Engine Oil Pressure
068 Engine Oil Life
069 Billing ID
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Usage of PDS 0791 is required only for EMV chip cards personalized using the IFSF/Conexxus
specification for retrieving supplemental data from acceptors and cardholders.
If PDS 0791 (Fleet Prompted Data 2) is present in the Financial Detail Addendum (Corporate
Fleet Transaction Information)/1644 message for Fleet Card product MCF and MGF
transactions when all these conditions occur, then PDS 0790 (Fleet Prompted Data 1) must also
be present.
• DE 26 (Acceptor Business Code [MCC]) contains one of the following Fleet fuel location
MCCs: 4468, 5499, 5541, 5542, or 5983.
• Transaction qualifies for the U.S. Region business service arrangement 2/010001 where PDS
0158, subfield 2 is equal to 2 and PDS 0158, subfield 3 is equal to 010001.
• First Presentment/1240 is submitted with one of the IRDs listed in this table.
IRD Description
F2 Commercial Fleet Data Rate II
FL Commercial Fleet Large Ticket
Values
If present, PDS 0791 must be variable length of 4-38 positions.
Subfields
PDS 0791 consists of two subfields. PDS 0791 subfields are listed in this table.
Value Description
001 User ID
002 Vehicle Number
003 Vehicle Tag
004 Driver ID
005 Odometer
009 Work Order / P.O. Number
010 Invoice Number
011 Trip Number
Value Description
012 Unit Number
013 Reefer Hours
015 ZIP Code / Postal Code
016 Replacement Car
017 Entered Data Num
018 Web Portal Data
019 Entered Data Alpha
021 Job Number
022 Maintenance ID
023 Department Number
024 Trailer Number
025 Delivery Ticket Number
026 Hubometer
033 Sub Fleet Number
035 Transaction Number
036 Control Number
038 Reefer Temperature
040 Driver or Vehicle Card
041 Customer Number
042 Additional Card Data
043 Additional Vehicle Data
044 Engine Hours
045 Tank Level Start
046 Fuel Gauge Level
047 Battery Voltage
048 Coolant Temperature
049 Check Engine Status
050 Fuel Economy
051 Engine RPM
052 Engine Load
053 Engine Oil Temperature
Value Description
054 Engine Time Total
055 Hard Breaking
056 Hard Acceleration
058 Idle Time
065 Total Idle Time
067 Engine Oil Pressure
068 Engine Oil Life
069 Billing ID
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage of PDS 0792 is required only for EMV chip cards personalized using the IFSF/Conexxus
specification for retrieving supplemental data from acceptors and cardholders.
If PDS 0792 (Fleet Prompted Data 3) is present in the Financial Detail Addendum (Corporate
Fleet Transaction Information)/1644 message for Fleet Card product MCF and MGF
transactions when all these conditions occur, then PDS 0790 (Fleet Prompted Data 1) and PDS
0791 (Fleet Prompted Data 2) must also be present.
• DE 26 (Acceptor Business Code [MCC]) contains one of the following Fleet fuel location
MCCs: 4468, 5499, 5541, 5542, or 5983.
• Transaction qualifies for the U.S. Region business service arrangement 2/010001 where PDS
0158, subfield 2 is equal to 2 and PDS 0158, subfield 3 is equal to 010001.
• First Presentment/1240 is submitted with one of the IRDs listed in this table.
IRD Description
F2 Commercial Fleet Data Rate II
FL Commercial Fleet Large Ticket
Values
If present, PDS 0792 must be variable length of 4-38 positions.
Subfields
PDS 0792 consists of two subfields. PDS 0792 subfields are listed in this table.
Values Description
001 User ID
002 Vehicle Number
003 Vehicle Tag
004 Driver ID
005 Odometer
009 Work Order / P.O. Number
010 Invoice Number
011 Trip Number
012 Unit Number
013 Reefer Hours
015 ZIP Code / Postal Code
016 Replacement Car
017 Entered Data Num
018 Web Portal Data
019 Entered Data Alpha
021 Job Number
022 Maintenance ID
023 Department Number
024 Trailer Number
025 Delivery Ticket Number
026 Hubometer
033 Sub Fleet Number
035 Transaction Number
036 Control Number
Values Description
038 Reefer Temperature
040 Driver or Vehicle Card
041 Customer Number
042 Additional Card Data
043 Additional Vehicle Data
044 Engine Hours
045 Tank Level Start
046 Fuel Gauge Level
047 Battery Voltage
048 Coolant Temperature
049 Check Engine Status
050 Fuel Economy
051 Engine RPM
052 Engine Load
053 Engine Oil Temperature
054 Engine Time Total
055 Hard Breaking
056 Hard Acceleration
058 Idle Time
065 Total Idle Time
067 Engine Oil Pressure
068 Engine Oil Life
069 Billing ID
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Usage of PDS 0793 is required only for EMV chip cards personalized using the IFSF/Conexxus
specification for retrieving supplemental data from acceptors and cardholders.
If PDS 0793 (Fleet Prompted Data 4) is present in the Financial Detail Addendum (Corporate
Fleet Transaction Information)/1644 message for Fleet Card product MCF and MGF
transactions when all these conditions occur, then PDS 0790 (Fleet Prompted Data 1), PDS
0791 (Fleet Prompted Data 2), and PDS 0792 (Fleet Prompted Data 3) must also be present.
• DE 26 (Acceptor Business Code [MCC]) contains one of the following Fleet fuel location
MCCs: 4468, 5499, 5541, 5542, or 5983.
• Transaction qualifies for the U.S. Region business service arrangement 2/010001 where PDS
0158, subfield 2 is equal to 2 and PDS 0158, subfield 3 is equal to 010001.
• First Presentment/1240 is submitted with one of the IRDs listed in this table.
IRD Description
F2 Commercial Fleet Data Rate II
FL Commercial Fleet Large Ticket
Values
If present, PDS 0793 must be variable length of 4-38 positions.
Subfields
PDS 0793 consists of two subfields. PDS 0793 subfields are listed in this table.
Value Description
001 User ID
002 Vehicle Number
003 Vehicle Tag
004 Driver ID
005 Odometer
009 Work Order / P.O. Number
010 Invoice Number
011 Trip Number
Value Description
012 Unit Number
013 Reefer Hours
015 ZIP Code / Postal Code
016 Replacement Car
017 Entered Data Num
018 Web Portal Data
019 Entered Data Alpha
021 Job Number
022 Maintenance ID
023 Department Number
024 Trailer Number
025 Delivery Ticket Number
026 Hubometer
033 Sub Fleet Number
035 Transaction Number
036 Control Number
038 Reefer Temperature
040 Driver or Vehicle Card
041 Customer Number
042 Additional Card Data
043 Additional Vehicle Data
044 Engine Hours
045 Tank Level Start
046 Fuel Gauge Level
047 Battery Voltage
048 Coolant Temperature
049 Check Engine Status
050 Fuel Economy
051 Engine RPM
052 Engine Load
053 Engine Oil Temperature
Value Description
054 Engine Time Total
055 Hard Breaking
056 Hard Acceleration
058 Idle Time
065 Total Idle Time
067 Engine Oil Pressure
068 Engine Oil Life
069 Billing ID
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Usage of PDS 0794 is required only for EMV chip cards personalized using the IFSF/Conexxus
specification for retrieving supplemental data from acceptors and cardholders.
If PDS 0794 (Fleet Prompted Data 5) is present in the Financial Detail Addendum (Corporate
Fleet Transaction Information)/1644 message for Fleet Card product MCF and MGF
transactions when all these conditions occur, then PDS 0790 (Fleet Prompted Data 1), PDS
0791 (Fleet Prompted Data 2), PDS 0792 (Fleet Prompted Data 3), and PDS 0793 (Fleet
Prompted Data 4) must also be present.
• DE 26 (Acceptor Business Code [MCC]) contains one of the following Fleet fuel location
MCCs: 4468, 5499, 5541, 5542, or 5983.
• Transaction qualifies for the U.S. Region business service arrangement 2/010001 where PDS
0158, subfield 2 is equal to 2 and PDS 0158, subfield 3 is equal to 010001.
• First Presentment/1240 is submitted with one of the IRDs listed in this table.
IRD descriptions
IRD Description
F2 Commercial Fleet Data Rate II
FL Commercial Fleet Large Ticket
Values
If present, PDS 0794 must be variable length of 4-38 positions.
Subfields
PDS 0794 consists of two subfields. PDS 0794 subfields are listed in this table.
Value Description
001 User ID
002 Vehicle Number
003 Vehicle Tag
004 Driver ID
005 Odometer
009 Work Order / P.O. Number
010 Invoice Number
011 Trip Number
012 Unit Number
013 Reefer Hours
015 ZIP Code / Postal Code
016 Replacement Car
017 Entered Data Num
018 Web Portal Data
019 Entered Data Alpha
021 Job Number
022 Maintenance ID
023 Department Number
024 Trailer Number
025 Delivery Ticket Number
Value Description
026 Hubometer
033 Sub Fleet Number
035 Transaction Number
036 Control Number
038 Reefer Temperature
040 Driver or Vehicle Card
041 Customer Number
042 Additional Card Data
043 Additional Vehicle Data
044 Engine Hours
045 Tank Level Start
046 Fuel Gauge Level
047 Battery Voltage
048 Coolant Temperature
049 Check Engine Status
050 Fuel Economy
051 Engine RPM
052 Engine Load
053 Engine Oil Temperature
054 Engine Time Total
055 Hard Breaking
056 Hard Acceleration
058 Idle Time
065 Total Idle Time
067 Engine Oil Pressure
068 Engine Oil Life
069 Billing ID
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
This PDS contains 1–5 test case numbers. The transaction originator optionally may provide it.
Its purpose is to trace the associated message to 1 to 5 internal Mastercard® or customer 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 customer.
Values
The transaction originator assigns PDS 0799 values.
If present, PDS 0799 must be left-justified and cannot contain all low values, all high values, all
spaces, or all zeros.
Attributes
Usage
This table shows the usage of this PDS (whether it is mandatory, conditional, optional, system-
provided, or not required) in applicable messages.
Usage
Values
Customers may choose one of two options in presenting member-to-member proprietary data
in their messages.
• Customers 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 to
1099 and provide one string of up to 992 characters of data. With this option, customers
would provide a single PDS tag (ID) and one length definition, followed by the data string.
The clearing system parsers will leave this customer data intact.
• Customers 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 to 1099 to
define their data. Under this option, customers 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. Customers 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 through 1099 may be presented in all messages
originated by customers 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.
PDS 1000 (Member-to-Member Proprietary Data) designates new commercial product type
MLF issued in Brazil only. The values listed in this table are used with the Brazil Agro Program.
Values
32 For 12.6, the 12 represents numeric values in front of the decimal point and the 6 represents values behind the
decimal point.
33 For 12.6, the 12 represents numeric values in front of the decimal point and the 6 represents values behind the
decimal point.
This diagram illustrates the relationship between the acquirer and DE 32.
Figure 8: Acquirer and DE 32 relationship
Technical institutions
These institutions are physically connected to the 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 DE 33 (Forwarding Institution ID Code)
and DE 100 (Receiving Institution ID Code).
• DE 33 - This institution is physically connected to the clearing system. It is usually a processor.
The message originator populates DE 33 with the customer ID assigned to the customer 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 customer 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 positions long and a maximum of 11
positions long. GCMS will reject clearing messages submitted with a customer ID less than six
positions long.
This diagram further illustrates the technical relationship among these data elements and
PDSs.
Figure 10: DE and PDS relationships
Notices
Following are policies pertaining to proprietary rights, trademarks, translations, and details
about the availability of additional information online.
Proprietary Rights
The information contained in this document is proprietary and confidential to Mastercard
International Incorporated, one or more of its affiliated entities (collectively “Mastercard”), or
both.
This material may not be duplicated, published, or disclosed, in whole or in part, without the
prior written permission of Mastercard.
Trademarks
Trademark notices and symbols used in this document reflect the registration status of
Mastercard trademarks in the United States. Consult with the Global Customer Service team or
the Mastercard Law Department for the registration status of particular product, program, or
service names outside the United States.
All third-party product and service names are trademarks or registered trademarks of their
respective owners.
EMV® is a registered trademark of EMVCo LLC in the United States and other countries. For
more information, see http://www.emvco.com.
Disclaimer
Mastercard makes no representations or warranties of any kind, express or implied, with respect
to the contents of this document. Without limitation, Mastercard specifically disclaims all
representations and warranties with respect to this document and any intellectual property
rights subsisting therein or any part thereof, including but not limited to any and all implied
warranties of title, non-infringement, or suitability for any purpose (whether or not Mastercard
has been advised, has reason to know, or is otherwise in fact aware of any information) or
achievement of any particular result.
Translation
A translation of any Mastercard manual, bulletin, release, or other Mastercard document into a
language other than English is intended solely as a convenience to Mastercard customers.
Mastercard provides any translated document to its customers “AS IS” and makes no
representations or warranties of any kind with respect to the translated document, including,
but not limited to, its accuracy or reliability. In no event shall Mastercard be liable for any
damages resulting from reliance on any translated document. The English version of any
Mastercard document will take precedence over any translated version in any legal proceeding.