GCMSReference Manual
GCMSReference Manual
Management System
Reference Manual
15 October 2019
TA
Summary of Changes, 15 October 2019
Contents
NOTE: For more information about settlement, refer to the Settlement Manual.
Clearing Basics
To understand clearing through Global Clearing Management System, customers should
understand clearing basics.
• When clearing can occur
• When settlement occurs
• The Integrated Product Messages (IPM) format (the clearing message format)
• Clearing message types
• Means of transferring clearing data
• Processing cycles
NOTE: In addition to the six primary clearing cycles, a seventh clearing cycle exists exclusively
for Mexico domestic switching transactions.
These four cycles are also the default delivery cycles for all endpoints, unless otherwise
specified. Processing customers will automatically receive clearing files at these default times,
unless they contact Mastercard to request different times. Processing customers may request
any combination of daily cycles that include four, five, or six cycles per day, adhering to the
requirements listed above. Processing customers that want to change their clearing cycle
cutoff times should complete section 4 of the Global Clearing Management System Parameter
Worksheet (Form 600).
The following table shows the daily schedule for the six primary clearing cycles and the
seventh clearing cycle designated for Mexico domestic switching transactions.
Business
Day Clearing 1 Clearing 2 Clearing 3 Clearing 4 Clearing 5 Clearing 6
Sunday No No No No No No
processing processing processing processing processing processing
The following table shows the daily schedule for the seventh clearing cycle designated for
Mexico domestic switching transactions.
Refer to the Clearing Processing Details chapter of the Global Clearing Management System
Reference Manual for clearing file delivery options.
Settlement Times
Mastercard settles with most customers Monday through Friday following the sixth clearing
cycle cutoff. However, for intracurrency settlement participants, the option to settle after any
clearing cycle is available.
Customers receive settlement advisements from the Mastercard Settlement Account
Management (S.A.M.) system.
The deadline for U.S. dollar funds transfer is 14:00 St. Louis, Missouri, U.S.A. time.
Transactions processed in the Saturday clearing cycles are included in the Monday net
settlement totals. Advisements that customers receive on Monday report both Saturday and
Monday settlement totals. Settlement can occur only after clearing has already occurred.
NOTE: For more information about settlement, refer to the Settlement Manual.
• Two bit-maps: A series of binary digits (bits) that indicate the presence or absence of data
elements.
• Data elements: Message elements, defined within the ISO 8583-1993 specification that
may contain data.
• Private data subelements: Message elements that Mastercard defined to support data not
defined within the ISO 8583-1993 specification.
MTI Description
1240 Presentment
1442 Chargeback
1644 Administrative
NOTE: For more information about the construction of the IPM message, refer to the IPM
Clearing Formats manual and the Clearing Processing Details chapter of the Global Clearing
Management System Reference Manual.
• Mastercard File Express: Transfer through dial-up access between remote personal
computers and a Central Site–based mainframe using modems and communications
software developed and licensed by Mastercard. The Mastercard File Express Client Users’
Guide contains more information about this transmission method.
• CONNECT:Direct: Mastercard mainframe to customer mainframe using dedicated network
communication facilities. This facility supports all bulk data types.
The acquirer may return the transaction with additional information as a second
presentment. The acquirer may return the second presentment to correct the original
defect or to indicate a disagreement with the issuer’s chargeback.
5. Arbitration Chargeback
If the issuer continues to dispute the item, it returns the transaction to the acquirer for the
second time as an arbitration chargeback. This cycle is not supported for ATM, Maestro, or
Cirrus transactions.
Arbitration
The final phase in the chargeback process is arbitration. A customer may petition Mastercard
to determine responsibility for a transaction after unsuccessful dispute resolution through the
chargeback process outlined above.
Compliance
The customers request that Mastercard resolve a rules violation or a dispute between the
customers when no remedy exists through the chargeback life cycle.
NOTE: For more information about the distributed software, refer to either the Clearing
Optimizer—Mainframe manual or the Clearing Optimizer—Workstation Plus manual.
In addition to the distributed software described above, Mastercard will deliver Member Host
Preparation Facility (MHPF) communication software upon request. The purpose of the
software is to assist in the management of data transfers through a Mastercard Interface
Processor (MIP). The MHPF communication software performs the following functions:
• Transmits files through the TCP/IP transmission protocol.
• Provides modules to perform some very basic file structure edits on non-clearing files.
• Provides MIP Bulk File Advisement software to perform queries and reporting of bulk files
received and available for unloading from their MIP.
Bulk File Advisement Module (module not specific to clearing format files)
Module Description
MH410010 MIP Bulk File Advisement
NOTE: For more information about the MHPF software, refer to the File Transfer Manual and
the Data Communications Manual.
NOTE: Mastercard will deliver modules MH590010 and MH700010 solely to support the
existing compile and link edit processes for the driver routines that contain them. Customers
no longer will run the modules themselves.
NOTE: The daily net settlement advisement is the definitive authority about funds movement.
Differences between the Global Clearing Management System reconciliation messages and
reports and the settlement advisement may occur from time to time because of risk
management edits present in the settlement system.
NOTE: For more information about net settlement procedures, refer to the Settlement
Manual.
• Determines the net amount for each customer’s daily incoming and outgoing work. Global
Clearing Management System produces a net settlement figure in reconciliation currency
that it sends to the Mastercard Settlement Account Management (S.A.M.) system.
• Verifies and adjusts fee calculations when necessary.
• Rejects individual messages or entire files and then notifies the sending customer of the
rejection.
• Updates accepted file information for each customer sending files.
• Produces and sends clearing files to participating customers.
• Provides currency conversion rates to customers at their option.
NOTE: For a sample of the worksheet, refer to the Global Clearing Management System
Parameter Worksheet (Form 600).
• Mastercard Rules
• Quick Reference Booklet
• Security Rules and Procedures
• Transaction Processing Rules
Element
Element Number Description
Message Type Identifier (MTI) ---- Describes the message class.
Primary Bit Map ---- A series of binary digits (bits) that indicate the
presence or absence of DE 1–DE 64.
Secondary Bit Map DE 1 A series of binary digits (bits) that indicate the
presence or absence of DE 65–DE 128.
The IPM Clearing Formats manual documents the specifications for each data element and
private data subelement.
message, in which case Global Clearing Management System returns the message to the
customer with the original DE 71 value).
NOTE: Customers must not populate an element with all high values, such as hexadecimal FF,
or all low values, such as hexadecimal 00, within clearing messages. Global Clearing
Management System edits for all low and high values and will reject messages that contain
them.
IPM Structure
The structure of an IPM message has several identifying components.
subelements, nor any data elements not supported for specific message type identifier (MTI)
and DE 24 (Function Code) combinations. This includes elements and subelements that
Mastercard will support in the future.
For example, the IPM Clearing Formats manual defines DE 17 (Capture Date) as an element
that Mastercard does not currently support and does not plan to support in the future. Global
Clearing Management System does not edit DE 17 or include it in any accepted message to
the transaction destination.
In addition to the above examples, some data elements are not valid for specific MTI and DE
24 combinations. For example, DE 55 (Integrated Circuit Card System Related Data) is a valid
data element for first presentment, second presentment, first chargeback, and arbitration
chargeback messages. However, it is not a valid data element for financial detail addendum
messages. Therefore, Global Clearing Management System would not forward it to the
transaction destination if it were included in a financial detail addendum message by the
sender of the message.
Mastercard follows the IPM Clearing Formats manual data element and private data
subelement specifications.
As shown in the following figure, Global Clearing Management System drops an unsupported
data element or private data subelement if Global Clearing Management System accepts the
message. An accepted message is one that Global Clearing Management System processes
because it does not fail format, syntax, content, or context edits.
Global Clearing Management System accepts a particular data element or private data
subelement if the element is all of the following:
• Parseable
• Identified as a recognized element for the transaction function (message type identifier
(MTI) and DE 24 [Function Code]), regardless of whether the field is mandatory, optional,
or conditional
• Valid
Valid means that the data element or private data subelement passes any format, syntax,
content, or context edits applied during the edit process. For example, a private data
subelement that the IPM Clearing Formats manual defines as containing only numeric digits
must contain only numeric digits to be considered valid. Chapters 7, 8, 9, and 10 of the IPM
Clearing Formats manual document the specifications for each data element and private data
subelement.
For example, within a first presentment, the IPM Clearing Formats manual defines:
• PDS 0165 (Settlement Indicator) as a mandatory field for a first presentment.
• PDS 0171 (Alternate Card Acceptor Description Data) as optional (that is, the transaction
originator may or may not include it) in a first presentment.
Both fields described above Any field is invalid Reject the message and return
both fields.
of non-binary data (including tags, lengths, and data for all PDS in the 1000–1099 range)
within a single IPM message.
To accommodate varying global business requirements, customers have two options for
presenting their data:
• Customers who want to use their own parsing routines to parse the proprietary data may
provide one string of up to 992 characters of data within a single private data subelement
in the 1000–1099 range. With this option, customers would provide a single private data
subelement tag (ID) and one length definition, followed by the desired data string. Global
Clearing Management System will leave this customer data intact.
• Customers who would like Mastercard to parse the proprietary data may use up to 100
individual private data subelement in the 1000–1099 range to define their data. With this
option, customers must use the normal tag-length-data private data subelement encoding
structure to define as many private data subelements as they choose to use. Customers
may provide up to 999 positions total (including tags, lengths, and data for all private data
subelements within the range) per message.
Customers may present proprietary data in private data subelements 1000–1099 in any of the
IPM message types for which the customer is the originator. They may include the customer-
to-customer proprietary private data subelements in any of the Additional Data DEs (DE 48,
DE 62, DE 123, DE 124, and DE 125), which are the carrier data elements for private data
subelements. Customers also should be prepared to receive private data subelements 1000–
1099 in any of the carrier data elements.
The contents of PDSs 1000–1099 must be in display format. The Global Clearing
Management System does not accommodate binary data in the private data subelements
dedicated for customer-to-customer proprietary data.
Customers must treat the data in the Customer-to-Customer Proprietary private data
subelements as confidential. Customers may disregard unsolicited Customer-to-Customer
Proprietary private data subelement data, and may discard it, provided this is done in a
manner, which preserves the confidentiality of the data.
Mastercard actions to split the logical files between multiple physical files, not receiving
reconciliation as expected, and could miss the preferred settlement cycle.
Offline
As used above, offline refers to an operating mode in which current active files are not being
viewed during the time the transaction is conducted.
Global Clearing Management System processes each logical file within a physical file
independently. The transmission originator determines whether to submit a single logical file
or multiple logical files within a physical file.
Logical Files within a Physical File
There are no requirements related to the grouping of IPM messages into logical files. For
example, one transmission originator may choose to create a separate logical file for each
ending customer ID. Another transmission originator may choose to create one logical file for
chargebacks and retrievals and another for presentments.
The following table specifies the contents of a possible clearing file that customer 004444 could send.
Location Requirements
U.S. region and Canada region • Must receive a clearing file after cycle 1.
customers • Must receive a clearing file after cycle 6.
• Must choose to receive clearing files after two or more of
the following cycles: cycle 2, cycle 3, cycle 4, or cycle 5.
Customers outside the U.S. and Canada • Must receive a clearing file after cycle 6.
regions • Must choose to receive clearing files after three or more
of the following cycles: cycle 1, cycle 2, cycle 3, cycle 4,
or cycle 5.
Customers processing Mexico Domestic • Must receive a clearing file after cycle 6.
transactions and participating in the • Must choose to receive clearing files after three or more
seventh clearing of the following cycles: cycle 1, cycle 2, cycle 3, cycle 4,
or cycle 5.
• Must receive a clearing file after cycle 7.
Mastercard has established the initial default delivery cycles for all processor customers as
cycles one, two, four, and six. These four cycles are also the default delivery cycles for all
endpoints unless otherwise specified.
Default Delivery Cycles
Customers automatically receive clearing files at these default times, unless they contact
Mastercard to request different times. Customersmay request any combination of daily cycles
that include four, five, or six cycles per day, adhering to the requirements listed above.
NOTE: The outbound delivery of the files of cycles one and two is extended by 1–3 hours on
release implementation dates only. The files from cycles three through six will be delivered at
the usual times. Release implementation dates occur four times a year and occur on a Friday
of the release implementation month. Although the files of cycles one and two are delivered
on a different calendar day from cycles three through six, Mastercard considers the delivery
of all six cycles of files to occur in one processing day.
The following table provides examples of the relationship between clearing cycle cutoff and
the receipt of clearing data.
Customers that want to change their clearing cycle cutoff times should complete section 2 of
the Global Clearing Management System Parameter Worksheet (Form 600).
Customer ID Endpoint
001234 0000001
005678 0000002
002222 0000001
In this example, Global Clearing Management System will create one file for endpoint
0000001 and one file for endpoint 0000002 after each specified clearing cycle cutoff.
The file created for endpoint 0000001 will contain transactions destined for customer IDs
001234 and 002222. The file created for endpoint 0000002 will contain transactions destined
for customer ID 005678.
A processor might choose to use this arrangement to group its customers into different files.
Option 2: Acquirer BIN
With this option, a customer can specify different endpoints according to acquirer bank
identification number (BIN). The following table is an example.
543333 0000002
In this example, Global Clearing Management System will create one file for endpoint
0000001 and one file for endpoint 0000002 after each specified clearing cycle cutoff.
The file created for endpoint 0000001 will contain transactions destined for acquirer BIN
541234. The file created for endpoint 0000002 will contain transactions destined for acquirer
BIN 543333.
Option 3: Acquirer BIN plus Card Program Identifier
With this option, a customer can specify different endpoints according to the combination of
acquirer BIN plus card program identifier. The following table is an example.
In this example, Global Clearing Management System will create one file for endpoint
0000001 and one file for endpoint 0000002 after each specified clearing cycle cutoff.
The file created for endpoint 0000001 will contain Maestro transactions destined for acquirer
BIN 544444. The file created for endpoint 0000002 will contain Mastercard transactions
destined for acquirer BIN 544444.
An acquirer might choose to use this arrangement to separate debit and credit activity.
Option 4: Issuer Account Range
With this option, a customer can specify different endpoints according to issuer account
range. The following table is an example.
542222 0000002
In this example, Global Clearing Management System will create one file for endpoint
0000001 and one file for endpoint 0000002 after each specified clearing cycle cutoff.
The file created for endpoint 0000001 will contain transactions destined for issuer account
range 541111. The file created for endpoint 0000002 will contain Mastercard transactions
destined for issuer account range 542222.
An issuer might choose to use this arrangement to separate consumer and corporate activity,
by assigning consumer account ranges to one endpoint and corporate account ranges to
another endpoint.
An issuer might also choose to use this arrangement to separate debit and credit activity, by
assigning one endpoint to Maestro or Cirrus account ranges and another endpoint to
Mastercard account ranges.
Option 5: Issuer Account Range plus Card Program Identifier
With this option, a customer can specify different endpoints based on the combination of
issuer account range plus card program identifier. The following table is an example.
In this example, Global Clearing Management System will create one file for endpoint
0000001 and one file for endpoint 0000002 after each specified clearing cycle cutoff.
The file created for endpoint 0000001 will contain Cirrus transactions destined for issuer
account range 545555. The file created for endpoint 0000002 will contain Mastercard
transactions destined for issuer account range 545555.
An issuer might choose to use this arrangement to separate Cirrus and Mastercard activity for
each account range.
Option 6: Issuer Account Range plus Card Program Identifier plus ATM versus POS
With this option, a customer can specify different endpoints according to the combination of
issuer account range, card program identifier, and whether the transaction is an ATM
transaction. The following table is an example.
Card Program
Issuer Account Range Identifier ATM/POS Endpoint
545555 Cirrus (CIR) ATM 0000001
In this example, Global Clearing Management System will create one file for endpoint
0000001, one file for endpoint 0000002, and one file for endpoint 0000003 after each
specified clearing cycle cutoff.
The file created for endpoint 0000001 will contain Maestro and Cirrus ATM transactions
destined for issuer account ranges 545555 and 547777. The file created for endpoint
0000002 will contain all Mastercard transactions destined for issuer account range 545555.
The file created for endpoint 0000003 will contain Maestro point-of-sale (POS) transactions
destined for issuer account range 547777.
An issuer could use this option to simulate the processing class concept by assigning one
endpoint to Maestro and Cirrus ATM transactions, one endpoint to Maestro POS transactions,
and one endpoint to Mastercard transactions, for each issuing account range.
When there are multiple message types (for example, multiple first presentments) for multiple
receiving customer IDs, the Global Clearing Management 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, Global Clearing Management
System constructs files generated by Mastercard as shown in the following table. For example,
suppose that customer ID 004444, endpoint 1, processes for customer ID 002222 and
customer ID 003333. When processing for multiple customer IDs, Global Clearing
Management System would construct the receiver’s inbound file as shown in the following
table.
Example of Sequencing of Files Generated by Mastercard
Endpoint 1, to Customer ID
MTI-Function Code Description (ICA)
1644-697 File Header 004444
NOTE: In addition to the six primary clearing cycles, a seventh clearing cycle exists exclusively
for Mexico domestic switching transactions.
NOTE: Within the MTI-Function Code category, data will not necessarily be in ascending
clearing cycle sequence. For example, cycle 5 First Presentments might precede cycle 4 First
Presentments.
The individual messages in a specific MTI-Function Code will continue to be sequenced as they
are today.
NOTE: In addition to the six primary clearing cycles, a seventh clearing cycle exists exclusively
for Mexico domestic switching transactions.
Customers and processors that elect to receive early reconciliation files may receive
information after all six cycles. For example, if a customer chooses to receive clearing files after
cycles 1, 2, 4, and 6, and to send files to Mastercard during cycles 3 and 5, the customer will
receive clearing files in all six cycles.
Customers and processors that choose to not receive early reconciliation will receive all of their
reconciliation messages, error messages, and messages from Mastercard to customers after
the next available delivery cycle they have chosen.
Global Clearing Management System will not recalculate or merge totals of reconciliation
messages that are held until the next available delivery cycle.
For example, if a customer or processor has selected cycles 1, 3, 4, and 6 as its delivery cycles
and has elected to not receive early reconciliation files, the following will apply:
• Reconciliation and error messages, if any, from cycle 1 will be delivered after cycle 1
processing.
• Reconciliation and error messages generated in clearing cycle 2 will be held, combined
with any reconciliation and error messages reconciliation and error messages generated
during cycle 3, and delivered after cycle 3 processing.
• Reconciliation and error messages generated in clearing cycle 4 will be delivered after cycle
4 processing.
• Reconciliation and error messages generated in clearing cycle 5 will be held, combined
with any generated during cycle 6, and delivered after cycle 6 processing.
The following table illustrates the differences of selecting receipt of early reconciliation
messages when both processors have chosen cycles 1, 3, 4, and 6 as their delivery cycles.
Early Reconciliation Customer and Non–Early Reconciliation Processor Example
a physical file containing two logical files, Global Clearing Management System will return
one early reconciliation Message file. The acknowledgement reconciliation messages for the
two logical files contained in the file sent to Mastercard will be contained in the single early
reconciliation message physical file.
For example, if the customer sends two logical files within a physical file, Global Clearing
Management System will send the acknowledgement reconciliation messages for the two
logical files within one physical file. Refer to the following figure for an illustration of this
example.
Number of Early Reconciliation Files Returned
The sequence number returned by Global Clearing Management System in the T113 early
reconciliation bulk file generated by Mastercard will match the sequence number sent by the
customer in the corresponding customer-generated R111 Global Clearing Management
System Data bulk file for those customers electing receipt of the early reconciliation files.
Mexico Domestic transactions for the seventh clearing is sent by customers under bulk type
RSP1 and Global Clearing Management System will use the sequence number from the RSP1
bulk file for early reconciliation and sent under the Bulk File T113 bulk to customers.
The sequence of an IPM early reconciliation message physical file generated by Mastercard is
similar to the sequence in the following table. Suppose that customer ID 004444, endpoint 1,
processes for customer IDs 002222, 003333, 005555, and 006666. When processing for
multiple customer IDs, Global Clearing Management System would construct the receiver’s
inbound file as shown in the following table.
For customers that participate in GCMS Early Reconciliation, a GCMS limitation requires that
the number of logical files within a phsyical file must not exceed 999. If the allowed limit is
exceeded, then customers will be impacted by not receiving early reconciliation for the
physical file amd could miss the preferred settlement cycle.
Sequencing of Files Generated by Mastercard Early Reconciliation
Endpoint 1, to Customer ID
MTI-Function Code Description (ICA)
1644-697 File Header 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.
Customers can match the physical file sent to Mastercard with the early reconciliation file
shown below by the T113 Global Clearing Management System early reconciliation file. The
following table identifies the pairing of the early reconciliation files with the file sent by the
customer.
T121 Test—Global Clearing Management R119 (or RSP3 for Mexico Domestico transactions
System Early Reconciliation File received from under the seventh clearing cycle) Test—Global Clearing
Mastercard Management System Data sent by the customer.
This message type contains 1644 in the MTI and 693 in DE 24 (Function Code) to identify it as
a text message.
NOTE: Mastercard recommends that customers using CONNECT:Direct choose to receive the
No Data file.
Clearing Times
The sending customer can submit transaction data for clearing to the St. Louis Operations
Center (Central Site) seven days a week, 24 hours a day.
Mastercard processes the data during one of six clearing periods Monday through Saturday.
The six cutoff times per processing day are 18:00 (16:00 on Sunday) and 21:00 the day before
the processing day, and 00:00, 03:00, 06:00, and 08:00 of the processing day (All times
shown are expressed as St.Louis time).
Customers may create and send clearing files as frequently as they want. Sending clearing files
earlier allows customers to have more transactions processed in earlier clearing cycle cutoffs,
thus ensuring the next available settlement of their accepted transactions.
NOTE: Mastercard does not recommend that customers send multiple single-record logical
files on a physical file. For alternative options, contact Global Customer Service. Sending in
multiple single-record logical files could cause processing of files to be significantly delayed.
Julian date refers to the day of the year expressed as a three-position number, with a range of
001 through 366 (for example, 001 on 1 January).
The file sequence subfield within PDS 0105 (File ID), a five-position file sequence number,
supports the frequent submission of files. It allows customers to have up to 99,999 files per
unique combination of PDS 0105, subfields one through three. PDS 0105 in the IPM format
consists of the subfields shown in the following table.
File ID Format for PDS 0105
3 Processor ID n-11
NOTE: For additional information about customer delivery cycle options, refer to the Files
Generated by Mastercard section.
T121 Test bulk ID for the Early Reconciliation Message file generated by T
Mastercard
T167 Test IPM MPE generated by MasterCard from Central Site (daily
T
updates)
T168 Test IPM MPE generated by MasterCard from Central Site (full file
T
replacement)
Date created 16–23 n-8 Date the IPM MPE Daily Update
file was generated.
Format: YYYYMMDD.
Time created 24–27 n-4 Time the IPM MPE Daily Update
file was generated.
Format: HHMM.
Date created 46–54 an-9 Date the IPM MPE Full File
Replacement was generated.
Format: MM DD YY followed by
one space.
Time created 62–69 an-8 Time the IPM MPE Full File
Replacement was generated.
Format: HH:MM:SS
CONNECT:Direct
The Record Descriptor Word (RDW) does not affect customers that send or receive IPM
clearing files, the IPM MPE file, or both through CONNECT:Direct.
Does not use Mastercard Must delete then insert the RDW at the
MHPF communications beginning of each IPM clearing message
software before loading the IPM clearing file to
the MIP for delivery to Mastercard.
Does not use Mastercard Must remove the RDW from the
MHPF communications beginning of each IPM clearing
software message, as the file is unloaded from
the MIP.
Processing Cards That have Converted from Cirrus to the Visa/PLUS ATM Network
Once cards are converted from Cirrus® to the Visa/PLUS ATM Network, customers must be
aware of the processing changes that occur.
In instances where an issuing account range has been converted from Cirrus to the Visa/PLUS
ATM Network, new transactions occurring after the conversion must be authorized and
processed by the Visa/PLUS ATM Network, not by the Single Message System. However,
transactions that were authorized by the Single Message System before the conversion to the
Visa/PLUS ATM Network must be cleared and settled by both Global Clearing Management
System and the Single Message System.
To accommodate customers that use the IPM MPE file for both authorization routing decisions
and clearing processing, when an issuer account range converts to the Visa/PLUS ATM
Network, Mastercard removes the account range from table IP0040T1 (Issuer Account Range)
in the IPM MPE file sent to customers, but still retains it in table IP0040T1 in the IPM MPE file
used by Global Clearing Management System. This procedure allows acquirers to stop sending
new authorization requests for the issuer account range to the Single Message System, but
still process clearing messages for previously authorized transactions by sending them to
Global Clearing Management System.
Acquirers that use the Clearing Optimizer software to process production clearing messages
before sending their files to Global Clearing Management System may receive error messages
from the Clearing Optimizer software for these transactions, even though they are accepted
when processed by Global Clearing Management System. To account for this condition,
Mastercard enhanced the Clearing Optimizer software to prevent customers from receiving
error messages when processing clearing messages for transactions authorized before an
issuer account range is converted from Cirrus to the Visa/PLUS ATM Network. This
enhancement consisted of adding the issuer account ranges that had been converted from
Cirrus to the Visa/PLUS ATM Network, to a Mastercard private use IPM MPE table IP9000T1.
The Clearing Optimizer software will use this table in its optimized table processing, to allow
Clearing Optimizer to accept clearing transactions involving these converted account ranges.
The following table describes distinctions between the two versions of the IPM MPE file in this context.
File Change
IPM MPE file sent to customers • Mastercard private use table IP9000T1—contains
issuer account ranges that have converted from
Cirrus to the Visa/PLUS ATM Network
• Table IP0090T1 (Issuer Account Range Card Program
Identifier and Business Service Arrangement
Participation)—contains issuer account ranges that
have converted from Cirrus to the Visa/PLUS ATM
Network.
• Table IP0040T1 (Issuer Account Range)—omits issuer
account ranges that have converted from Cirrus to
the Visa/PLUS ATM Network, so that acquirers can
continue to understand that new authorizations for
these account ranges must be authorized and
processed through the Visa/PLUS ATM Network, and
not by Single Message System.
Optimized version of the IPM MPE (created • Table IP0090T1 (optimized version)—contains issuer
by the Clearing Optimizer software) account ranges that have converted from Cirrus to
the Visa/PLUS ATM Network.
• Table IP0040T1 (optimized version)—contains issuer
account ranges that have converted from Cirrus to
the Visa/PLUS ATM Network so that the Clearing
Optimizer software will no longer reject clearing
transactions for these issuer account ranges.
These changes are provided here to customers as a courtesy reminder of this feature;
therefore, no action is required.
Guiding Principles
Unless otherwise specified, these are suggested best practices for AFD processing and are not
mandatory.
• AFD transactions often clear for an amount that is different from the authorized amount.
Mastercard recommends (required in the Europe region) that AFD transactions be
submitted as preauthorizations (DE 61, subfield 7, [POS Transaction Status = 4]).
Mastercard recommends (required in the Canada, Europe, and U.S. regions) that acquirers
submit an AFD completion advice message to the issuer with the final transaction amount
after fueling is completed, regardless of the method used (1.00 AFD or maximum amount)
—even when the final purchase equals the authorized amount.
• If DE 38 (Approval Code) is contained in Authorization Request Response/0110 or
Authorization Advice Response/0130 message, the Mastercard also recommends that the
Trace ID (DE 15 [Settlement Date] and DE 63 [Network Data]) of the completion advice
response be used within the clearing presentment (Refer to the Automated Fuel Dispenser
Clearing Processing in the following section).
As an alternative, the Trace ID (DE 15 [Settlement Date] and DE 63 [Network Data]) 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 (Trace ID).
Value Description
1403 Previously approved authorization—partial amount, multi-clearing
1404 Previously approved authorization—partial amount, final clearing
Guiding Principles
• Multi-clearing is intended for improved open-to-buy (OTB) management of e-commerce
split shipments, but not limited to card-not-present merchants. Issuers should manage OTB
holds using the new multi-clearing reason codes and their own balance management
policies.
• Multi-clearing must include proper authorization matching data (DE 38 Approval Code, DE
63 Trace ID) or the presentment will be rejected. If the split shipment sequence is not
deterministic, e-commerce processors may not be able to identify which presentment is
final.
• Multi-presentment airline ticket and installment purchases are unaffected and will process
business as usual. Multi-clearing only applies to Mastercard credit and Debit Mastercard
transactions.
NOTE: Global Clearing Management System will reject the message if edits reveal that
required information is missing. In most cases, Global Clearing Management System will also
reject a message if an element contains all low values, all high values, all spaces, or all zeros.
Refer to the IPM Clearing Formats manual for specific exceptions to this policy. One such
exception is for Mexico Domestic transactions where, under certain conditions, the transaction
is not rejected but flagged for error and the transaction settles. This is referred to as syntax
error condition.
NOTE: For information about the edits that apply to individual IPM messages, refer to the IPM
Clearing Formats manual.
When Global Clearing Management System encounters exception conditions at the single
message or file level, it generates appropriate error messages. Global Clearing Management
System creates the following types of IPM error messages:
• Full file rejection messages
• Single message rejection messages
NOTE: IPM reject messages contain no warning or adjustment conditions, only reject
conditions.
Global Clearing Management System can reject both a first presentment message and its
associated financial detail addendum messages, or it can reject just the associated financial
detail addendum messages, as follows:
• If Global Clearing Management System rejects an IPM first presentment message, it also
rejects and returns to the transaction originator all associated financial detail addendum
messages.
• If Global Clearing Management System rejects financial detail addendum messages, it does
not necessarily reject the associated first presentment message.
NOTE: Global Clearing Management System does not return the IPM file reject message if the
header message of the rejected file is unparseable, nor if PDS 0105 (File ID), subfield 3
(Processor ID) is invalid. In these cases, Global Clearing Management System cannot
determine the receiver of the file reject message and therefore cannot notify the appropriate
customer of the file reject.
Example 1
Suppose that the transaction originator omits IPM messages between the file header and file
trailer messages. Because Global Clearing Management System requires data between the file
header and file trailer messages in a customer-submitted logical file, the absence of data
results in a file reject. The Global Clearing Management System would return a file reject
message to the transaction originator indicating the following:
Example 2
Suppose that the transaction originator includes a file ID in the file trailer message that does
not match the file ID in the file header message. The Global Clearing Management System
would return a file reject message to the transaction originator indicating the following:
• The file ID of the rejected file
• The field in error, with the appropriate error code
• Up to 200 positions of the first message in the rejected file
The Global Clearing Management System would not forward any of the messages to the
intended transaction destinations because it rejected the entire file.
Example 3
Suppose that the transaction originator includes PDS 0105 on a file header message that has
a duplicate file ID—that is, the file ID duplicates the ID of another clearing file submitted
within the previous 180 days. The Global Clearing Management System would return a file
reject message to the transaction originator indicating the following:
• The file ID of the rejected file
• The field in error, with the appropriate error code
• Up to 200 positions of the rejected file’s first message
The Global Clearing Management System would not forward any of the messages to the
intended transaction destinations because it rejected the entire file.
If a customer processes for multiple customer IDs, Global Clearing Management System sends
a single file reject for that customer processor surrounded by a file header and a file trailer. For
example, if customer 004444, endpoint 1:
• Processes for customer IDs 001111, 002222, and 003333
• Sends a file with transactions for customer IDs 001111, 002222, and 003333, which
Global Clearing Management System rejects with a full file reject, and
• Receives the Early Reconciliation File
Global Clearing Management System would construct the file generated by Mastercard as
follows.
The Clearing Optimizer application The Clearing Optimizer application provides the entire
original message, unaltered except for DE 71 (Message
Number) (Refer to the following information).
The Clearing Optimizer application assigns a new DE 71 value to the rejected original message
when returning it to the sending customer, although Global Clearing Management System
retains the DE 71 value from the original message. Customers also may use PDS 0138 (Source
Message Number ID) of the message exception message to identify the input source message
number. PDS 0138 will not be present if the original message is unparseable and Global
Clearing Management System cannot determine the DE 71 value from the original message.
If all detail messages in a logical file are rejected, the Global Clearing Management System
generates a Message Exception/1644-691 for each rejected detail message. Additionally, the
Global Clearing Management System generates a File Reject/1644-699 because none of the
individual messages were accepted.
If a customer processes for multiple customer IDs, Global Clearing Management System sends
all the message rejects for that customer surrounded by a file header and a file trailer. For
example, if customer 4444, endpoint 1, processes for customer IDs 1111 and 2222 and
receives the Early Reconciliation File, Global Clearing Management System would construct
the file generated by Mastercard as follows.
Transactions that are flagged only with syntax errors are not rejected, but will be cleared and
settled business as usual. However, transactions that are flagged with syntax errors and also
have other errors resulting from Clearing Platform edits will be rejected.
NOTE: Interchange and fees will be reversed on syntax error return messages. The receiver of
the returned syntax error can return the message and collect funds using a Miscellaneous Fee
Collection/1740 message, if applicable.
Error Detail—Input Sequence Report and Global Collection Only Error Detail—
Input Sequence Report
Global Clearing Management System reports rejected transaction data through the Error
Detail—Input Sequence report and the Global Collection Only Error Detail—Input Sequence
report. These reports provide all data elements of a rejected message, including data that fails
edits and data that passes edits, highlighting the data elements in error.
These reports include rejected transaction details at the following levels:
• Logical file to Mastercard
• Processing Mode (Test or Production)
• Source Message Number
• Source Currency
• Source Amount
• Transaction Function
• Global Collection Only separated from non–Global Collection Only rejected transactions
These reports are billable at USD 0.01 per line and are billed through the Mastercard
Consolidated Billing System (MCBS). The billing event numbers are as follows.
The Error Detail—Input Sequence reports are optional. The Global Clearing Management
System transmits this report using bulk type T140 for production and bulk type T150 for test
reports.
NOTE: Customers that request these reports will receive them after each clearing cycle,
regardless of the customer’s file delivery options. For example, if data from clearing cycles 3
and 4 are merged for data delivery, Global Clearing Management System will produce a
report after clearing cycle 3 and a separate report after clearing cycle 4.
Field Description
Run Date The date on which this report was produced.
File ID The logical file ID of the customer-generated file to which the data in
this report pertains.
Figure: Error Detail—Input Sequence Report (IP857010-AA), File Level Reject, page 2
Error Detail—Input Sequence Report (IP857010-AA), File Level Reject, page 2 Field
Descriptions
Field Description
Run Date The date on which this report was produced.
File ID The logical file ID of the customer-generated file to which the data in
this report pertains.
Error Code A unique code (established by Mastercard) that identifies the type of
error encountered. Refer to the IPM Clearing Format Error Numbers
and Messages manual for a list of the error codes established by
Mastercard and their corresponding descriptions.
Source Message Number Number of the original message that contains the error, from DE 71
(Message Number).
Element ID The number of the data element or private data subelement causing
the error condition.
File Information If parseable, contains up to the first 200 positions of data in a reject
of an entire file (This information prints only for file-level rejects).
Field Description
Run Date The date on which this report was produced.
Field Description
File ID The logical file ID of the customer-generated file to which the data in
this report pertains.
Source Message Number Number of the original message that contains the error, from DE 71
(Message Number).
Source Amount Monetary amount of the rejected message. For messages without a
DE 4 (Amount, Transaction) value (for example, retrieval fee billing or
financial detail addendum messages), the field will be zero.
MTI-Function Code The Message Type Identifier and the DE 24 (Function Code) value
associated with the rejected message.
Source Currency The alphabetic currency code associated with the monetary amount.
Error Code A unique code (established by Mastercard) that identifies the type of
error encountered. Refer to the IPM Clearing Format Error Numbers
and Messages manual for a list of the error codes established by
Mastercard and their corresponding descriptions.
Source Message Number Number of the original message that contains the error, from DE 71
(Message Number).
Element ID The number of the data element or private data subelement causing
the error condition.
Invalid Data Listing of the contents of the data element or private data subelement
in error, within the rejected message (This information prints only for
message level rejects).
Field Description
Run Date The date on which this report was produced.
File ID The logical file ID of the customer-generated file to which the data in
this report pertains.
Error Code A unique code (established by Mastercard) that identifies the type of
error encountered. Refer to the IPM Clearing Format Error Numbers
and Messages manual for a list of the error codes established by
Mastercard and their corresponding descriptions.
Source Message Number Number of the original message that contains the error, from DE 71
(Message Number).
Element ID The number of the data element or private data subelement causing
the error condition.
Invalid Data Listing of the contents of the data element or private data subelement
in error, within the rejected message (This information prints only for
message level rejects).
Message Unparseable Contains up to the first 200 positions of the rejected message when
Global Clearing Management System cannot parse the message into
elements.
Field Description
Run Date The date on which this report was produced.
Field Description
Page The page number within the report.
File ID The logical file ID of the customer-generated file to which the data in
this report pertains.
Message Type Identifies whether the message has a settlement indicator of settled
by Mastercard, bilateral (not settled by Mastercard), or Global
Collection Only.
Amount The net total of the source monetary amount of the messages.
Messages that do not include a DE 4 (Amount, Transaction) value are
not included in this field.
Field Description
Run Date The date on which this report was produced.
File ID The logical file ID of the customer-generated file to which the data in
this report pertains.
Field Description
Run Date The date on which this report was produced.
Field Description
File ID The logical file ID of the customer-generated file to which the data in
this report pertains.
Source Message Number Number of the original message that contains the error, from DE 71
(Message Number).
Source Amount Monetary amount of the rejected message. For messages without a
DE 4 (Amount, Transaction) value (for example, retrieval fee billing or
financial detail addendum messages), the field will be zero.
MTI—Function Code The Message Type Identifier and the Function Code associated with
the rejected message.
Source Currency The alphabetic currency code associated with the monetary amount.
Error Code A unique code (established by Mastercard) that identifies the type of
error encountered. Refer to the IPM Clearing Format Error Numbers
and Messages manual for a list of the error codes established by
Mastercard and their corresponding descriptions.
Source Message Number Number of the original message that contains the error, from DE 71
(Message Number).
Source Element ID Identifies the element for which Global Clearing Management System
encountered the reject condition.
Invalid Data Listing of the contents of the element within the rejected message.
Field Description
Run Date The date on which this report was produced.
Field Description
Page The page number within the report.
File ID The logical file ID of the customer-generated file to which the data in
this report pertains.
Error Code A unique code (established by Mastercard) that identifies the type of
error encountered. Refer to the IPM Clearing Format Error Numbers
and Messages manual for a list of the error codes established by
Mastercard and their corresponding descriptions.
Source Message Number Number of the original message that contains the error, from DE 71
(Message Number).
Element ID The number of the data element or private data subelement causing
the error condition.
Invalid Data Listing of the contents of the data element or private data subelement
in error, within the rejected message.
Message Unparseable Contains up to the first 200 positions of the rejected message when
Global Clearing Management System cannot parse the message into
elements.
Field Description
Run Date The date on which this report was produced.
Field Description
Page The page number within the report.
File ID The logical file ID of the customer-generated file to which the data in
this report pertains.
Message Type Identifies whether the message has a settlement indicator of settled
by Mastercard, bilateral (not settled by Mastercard), or Global
Collection Only.
Amount The net total of the source monetary amount of the messages.
Messages that do not include a DE 4 (Amount, Transaction) value are
not included in this field.
Global Clearing Management System Transaction and Chargeback Analysis Reports................... 111
items, maintain an audit trail for the life cycle of the chargeback, and retain subsequent
chargeback and second presentment rights.
NOTE: For information about the message procedures for presentment of transactions, refer
to the IPM Clearing Formats manual.
The acquirer must present all cash disbursements, purchases, credits, unique, and Payment
Transactions for the full amount of the original transaction currency as agreed to by the
cardholder. The amount may not be increased (or reduced in the case of a credit or a Payment
Transaction) unless specifically authorized within this manual. Acquirers must promptly present
these transactions to issuers.
NOTE: For more information about currency conversions, refer to the Currency Conversion
chapter.
• When the transaction was completed with electronically recorded card information
(whether card-read or key-entered), the acquirer has a maximum of seven calendar days
after the transaction date to present the transaction to the issuer.
• When the transaction was completed with manually recorded card information (whether
imprinted or handwritten), the acquirer has a maximum of 30 calendar days after the
transaction date to present the transaction to the issuer.
• For transactions effected at a U.S. region merchant with a card issued in the U.S. region,
when the transaction was completed with manually recorded card information (whether
imprinted or handwritten), the acquirer has a maximum of 14 calendar days after the
transaction date to present the transaction to the issuer.
• A payment transaction must be presented in clearing within one business day of the
authorization date.
• A contactless transit aggregated transaction must be presented in clearing within 14
calendar days of the authorization date.
Notwithstanding these time frames, the acquirer has a maximum of 30 calendar days (14
calendar days for intra-United States transactions) after the transaction date to present a
transaction when the acquirer must delay presentment:
• Because of the merchant’s delay in submitting the transaction, as permitted under Chapter
3, Transaction Records of Transaction Processing Rules;
• A national bank holiday of at least four consecutive days occurred, which prevented the
acquirer from presenting a card-read or key-entered transaction within the applicable
seven-calendar-day time frame.
An issuer must still accept transactions submitted beyond the applicable time frame if the
cardholder account is in good standing or the transaction can be otherwise honored and
posted.
If the message has no transaction date when processed through Global Clearing Management
System, the date 15 days before the date in PDS 0105 (File ID), subfield 2 (File Reference Date)
will be presumed (for rules administration) to be the transaction date, subject to subsequent
establishment of the actual date by support documentation.
these error numbers, acquirers must contact the Global Customer Service team to request a
risk-management approval code.
NOTE: Refer to the MasterCom manuals for more information about retrieval requests and
fulfillments, including information about processing time frames and processing procedures.
Sequence of
Information Positions Name Attribute Justification
1 1–16 Fulfillment Fax Number ans-16 left
Sequence of
Information Positions Name Attribute Justification
2 17–46 Contact Name ans-30 left
NOTE: Because this format is only a recommendation and uses existing customer-to-customer
proprietary data fields within the IPM format, it is not documented in the IPM Clearing
Formats manual.
Chargeback Processing
The chargeback process begins when an issuer determines that, for a valid chargeback reason
specified in the Chargeback Guide, the transaction may be charged back to the acquirer for
possible remedy. The chargeback life cycle includes the first chargeback and, if necessary, a
second presentment, arbitration chargeback, if applicable, and arbitration case filing.
The required time frames applicable to each cycle are described below.
In cases that involve… Mastercard calculates the period of 120 days from…
Delayed delivery of goods or The latest anticipated date that the card acceptor was to provide the
performance of services that goods or services.
the cardholder asserts the card
acceptor never provided
NOTE: For more information about chargeback life cycle support and the time frame
associated with each chargeback reason, refer to the Chargeback Guide.
Central Site processing date in PDS 0158, Chargeback History File business date in PDS 0158,
subfield 5 subfield 5
Central Site processing date in PDS 0158, Date in retrieval history in DE 31 (Acquirer Reference
subfield 5 Data), subfield 3 (Julian Processing Date YDDD)
Retrieval history in PDS 0243, subfield 1 Date in retrieval history in DE 31, subfield 3
Examples
Compare the following examples to understand the effect of the submission date and time on
chargeback processing. In both examples, the customer submits the second presentment with
a message reason code of 2008, which has the requirement of submission within 45 days
after the first chargeback.
The customer submits the second Saturday, 18 August after the Saturday, 18 August before
presentment with a message reason sixth clearing. The file header the sixth clearing. The file
code of 2008. date is Saturday, 18 August. header date is Saturday, 18
August.
Code]) and also find that the exclusion indicator is invalid. In this case, Global Clearing
Management System will provide the IPM error code 2006 (INVALID EXCLUSION INDICATOR)
in addition to the other applicable error codes in the IPM error message that the system
returns to the sender of the transaction.
DE 24 (Function
MTI Code) Description
1442 450 First Chargeback (Full)/1442 for the full First Presentment/1240 amount.
Initiated by the issuer.
1240 205 Second Presentment (Full)/1240 for the full First Presentment/1240
amount. Initiated by the acquirer.
DE 24 (Function
MTI Code) Description
1442 451 Arbitration Chargeback (Full)/1442 for the full First Presentment/1240
amount. Initiated by the issuer.
An issuer may exercise one first chargeback per presented transaction within the applicable
time frame limit specified in the Chargeback Guide.
An acquirer may process a second presentment if it can provide additional information, as
specified in the Chargeback Guide, to correct the original defect that led to the chargeback.
An issuer may process an arbitration chargeback if it is determined that a transaction was
improperly presented for a second time or if the issuer does not receive supporting
documentation required with the second presentment.
Submitting the Transaction Amount for First Chargebacks, Second Presentments, and
Arbitration
Customers must submit three elements for first chargebacks, second presentments, and
arbitration.
For first chargebacks, second presentments, and arbitration chargebacks, the sender submits
the following:
• DE 4 (Amount, Transaction), which provides the amount of the current chargeback in
either U.S. dollars or the customer’s intracurrency settlement currency.
• DE 30 (Amount, Original), which provides the original amount from the first presentment,
in the original transaction currency.
• PDS 0149 (Currency Codes, Amounts, Original), which provides the currency code
associated with the original transaction amount in DE 30.
If the message is for a partial amount, the sender also may submit PDS 0268 (Amount, Partial
Transaction), which provides the partial amount being submitted as a chargeback or second
presentment, in the original transaction currency.
The following table identifies the message element criteria for processing chargebacks on
purchases with cash back transactions.
DE 30 (Amounts, Original) Should contain the original transaction amount of the First
Presentment/1240
DE 30 (Amounts, Original) Should contain the original transaction amount of the First
Presentment/1240
DE 54 (Amounts, Additional) Should contain the cash back portion of the purchase with cash
back transaction
DE 25 (Message
Reason Code) Description
4853 Cardholder Dispute—Defective Merchandise/Not as Described
DE 25 (Message
Reason Code) Description
4854 Cardholder Dispute—Not Elsewhere Classified (U.S. region only)
If initiating a chargeback for the purchase amount or a portion thereof, the issuer should
submit a First Chargeback (Partial)/1442 or Arbitration Chargeback (Partial)/1442.
DE 95 (card issuer reference data)
DE 95 (card issuer reference data) is a control value of 10 positions that the issuer assigns with
its original chargeback and is used to track the chargeback throughout its life cycle.
The issuer may, at its option, include its customer ID number when defining the value for this
element. The card issuer reference data may be used to identify the originator, and in turn, the
originator may determine and direct the chargeback to the department or affiliate customer
that initiated the original chargeback.
The issuer provides DE 95 when processing retrieval or chargeback messages. The acquirer is
required to include the same data in a subsequent fulfillment of the retrieval request or
acquirer advisement. In the case of a chargeback, this applies to both Second Presentment/
1240 and Arbitration Chargeback/1442 case filings.
The unique card issuer reference data provides an audit trail of a chargeback’s processing life
cycle. It allows customers to locate the source documentation needed to rebill a cardholder or
recharge a card acceptor.
The issuer must not use the card issuer reference data number more than once in a 12-month
period. Global Clearing Management System edits validate all incoming chargebacks against
the chargeback history file to ensure that the incoming chargebacks do not contain a card
issuer reference data used previously with the same BIN. Acquirers must not modify the card
issuer reference data when second presenting a chargeback. Global Clearing Management
System will reject the chargeback or second presentment if it contains an invalid card issuer
reference data. Customers should always submit DE 95 in all chargeback life cycle
transactions, even though Global Clearing Management System does not perform the
validation edits for ATM chargeback life cycle transactions (DE 3 [Processing Code], subfield 1
[Cardholder Transaction Type], value of 01).
Global Clearing Management System will edit this private data subelement for all First
Chargeback/1442, Second Presentment/1240, and Arbitration Chargeback/1442 messages
and will reject the message if the indicator is not a 0 or a 1.
DE 72 (Data Record)
DE 72 (Data Record) is used during the different chargeback processing cycles to provide the
receiving customer with specific information about the item.
NOTE: For specific message text requirements for each type of message, refer to the
Chargeback Guide.
– Subfield 3—Edit exclusion reason code (from PDS 260, subfield 2 of the first
chargeback or second presentment)
– Subfield 4—Edit exclusion results code (from PDS 260, subfield 3 of the first
chargeback or second presentment)
– Subfield 5—First return amount (from DE 4 [Amount, Transaction] of the first
chargeback or second presentment)
– Subfield 6—First return currency code (from DE 49 [Currency Code, Transaction] of
the first chargeback or second presentment)
– Subfield 7—First return data record (from DE 72 [Data Record] of the first chargeback
or second presentment)
NOTE: For more information about compliance procedures, refer to the Chargeback Guide.
sale entry mode, cardholder present information, merchant advice code, and message type
identifier (MTI).
• If the transaction is over 180 days, customers can submit a request using the Authorization
Research Request (Form 074). The Global Customer Service team will perform the research
for you. The team provides information about authorization transactions, duplicate reports,
microfiche re-creation, currency conversion rates, BIN and ICA numbers, and conversions.
Initial access to Mastercard Connect requires only your user ID and password, which are
created during the enrollment process. A SecurID token is assigned, if required for a
Mastercard Connect product that requires higher security level access.
For any assistance with Masterc ard Connect enrollment or product registration, contact
Global Customer Service Support at [email protected].
Procedure
1. Log on to Mastercard Connect at www.mastercardconnect.com.
2. Enter your User ID and Password.
3. Click Store on the main menu (located in the upper-right corner) on the Mastercard
Connect home page.
4. Scroll or search for Transaction Investigator.
5. Click Add to Shopping. A confirmation message appears.
6. Click Cart to display the cart, and then click Checkout to display the Order Details
window.
7. Under Order Details, click Review Order, and then click Place Order.
Once the Security Administrator approves the request, Transaction Investigator will appear
under the Applications menu on the Mastercard Connect home page.
For any assistance with Mastercard Connect enrollment or product registration, contact
Global Customer Service Support at [email protected].
Procedure
1. Log on to Mastercard Connect using your Mastercard Connect user ID and PIN/SecurID.
2. From the Applications menu, click Transaction Investigator.
On selecting Transaction Investigator, a new browser window opens and displays the
Transaction Investigator home page.
Searches can be performed from this screen using an account number and dates
combination, Auth Only data or click Advanced Search for additional search criteria.
3. Click Advanced Search and select the Clearing View on the left pane.
Clearing Summary
A summary of clearing information is displayed here based on the criteria entered in the
search. The information displayed may contain several records. Clicking a record in the
grid will automatically highlight and display the corresponding data at the top of the other
open panel—Clearing Detail. Data elements that do not contain any data are indicated in
the display with the words No Data.
You can customize the data display using the sort feature on any column in the Clearing
Summary. By clicking the column heading, the sort direction can be toggled. The default
sort is by transaction date.
Clearing Detail
The clearing data detail is displayed here for the record selected in the Clearing Summary
grid.
To expand the data elements that contain subfield data, click the corresponding plus sign.
The subfield data is highlighted for the expanded data element.
When the Global Collection Only option is selected, the query searches for GCO
transactions from the GCO data store. The Clearing summary and details grids will display
the GCO transaction records.
Procedure
1. Click the Customize box, from the panel tool bar.
2. From the Customize window, select the data elements that you want to hide from view.
3. Click the Move Left arrow to move the selected data elements to the Hidden from View
panel. Use the Move Right arrow to move selected data elements to the My View panel.
4. Select the desired data element in the My View panel and click either the Up or Down
arrow to change the display order of the data elements.
5. Click Save.
6. Click Restore Default to reset the display to show all data elements.
7. Clicking on Search after entering the Cardholder account number and the date range, the
results may look similar to the following illustration. The Clearing Detail will display the
details corresponding to the highlighted transaction in the Clearing Summary grid.
-BB Issuer
Because the layouts are the same, the following shows only the -AA version.
These reports are available in the following media types:
• Mastercard Network/Bulk
• Mastercard File Express
• CONNECT:Direct
To request these reports, please contact the Global Customer Service team or refer to and
complete the Global Clearing Management System Parameter Worksheet (Form 600).
Figure: Global Clearing Management System Transaction/Chargeback Analysis Report
(IP776010-AA)
Field Description
Report Name Constant; Value is always Mastercard Global Clearing Management System
Transaction/Chargeback Analysis..
Customer ID Received from Global Clearing Management System customer master file.
Customer Name Name of the customer associated with the above member ID.
Page Incremental number starting at 1 for each new ICA number/customer ID.
Period From The specific beginning and end dates of the reporting month.
Year-to-date Calendar year to date beginning with January through the current reporting
month.
First Chargeback Total number of First Chargebacks/1442-450 (full) and 1442-453 (partial).
Received
Chargeback Dollars Total U.S. dollar amount of 1442-450 (full) and 1442-453 (partial) messages.
PCNT FNCL Value of the first Chargeback Received, Chargeback Dollars, and Retrieval
Reqst Recd fields as a percentage of the total First Presentments/1240-200
messages sent/received by the customer.
PCNT Global Clearing Value of fields 1 and 5 for the customer as compared with the total volume of
Management System corresponding activity processed by Global Clearing Management System for
all customers (IP776010-CC report).
Retrieval Volume
Retrieval Volume
Fulfillments Sent Total number of fulfillments processed for MasterCom and manual (non-
MasterCom) fulfillment activity.
Field Description
Retrieval Volume
Reason Code Total number of First Chargeback/1442-450 and 1442-453 messages. Both
MasterCom and manual (non-MasterCom) activity is reported.
Retrieval Volume
Retrvls Recd vs Fin Total number of Retr. Rqst. Rcd. (Retrieval Request/1644-603 messages) as a
Sent percentage of Financial Detail Sent (First Presentment/1240-200 messages) for
MasterCom and manual (non-MasterCom) activity.
1st Cgbk Number of 45-day, 120-day, and total First Chargeback/1442-450 (Full) and
1442-453 (Partial) messages for all message reason codes received (by
acquirer) or sent (by issuer).
2nd Pres Number of 45-day, 120-day, and Second Presentment/1240-205 (Full) for all
message reason codes received (by issuer) or sent and 1240-282 (Partial)
messages (by acquirer).
Total Volume Number of all first chargeback, second presentment, and arbitration
chargeback messages.
Average Ticket Total chargeback dollars divided by total chargeback volume. Total U.S. dollars
can be derived by adding the net U.S. dollar amount for chargebacks and
second presentments shown on the corresponding IP776030 Dollar Volume
Summary report.
Field Description
Report Name Constant; Value is always Mastercard Global Clearing Management
System Transaction/Chargeback Analysis..
Customer Name Name of the customer associated with the above customer ID.
Period From The specific beginning and end dates of the reporting month.
Reason Code All activity on this report is sorted by message reason code. Message
reason codes 4834 and 4859 include both ATM and non-ATM activity.
For a chargeback reason code, both MasterCom and manual (non-
MasterCom) activity is reported.
Percent of Cgbk Percentage of Total Chargeback Volume (for message reason code
specified) to the grand total of total chargeback volume processed.
Total Cgbk Volume Total number of first chargebacks, second presentments, and
arbitration chargebacks by message reason code.
Total Cgbk DollarAmount Total dollar amount of first chargebacks, second presentments, and
arbitration chargebacks by message reason code.
Grand Total Grand totals for all chargeback, second presentment, and arbitration
chargeback activity.
Field Description
Report Name Constant; Value is always Mastercard Global Clearing Management
System Transaction/Chargeback Analysis.
Period From The specific beginning and end dates of the reporting month.
Financial Detail Debits Total number and associated dollar volume of First Presentment/
1240-200 non-reversal debit messages.
Financial Detail Debit Reversals Total number and associated dollar volume of First Presentment/
1240-200 reversal debit messages.
Financial Detail Credits Total number and associated dollar volume of First Presentment/
1240-200 non-reversal credit messages.
Financial Detail Credit Total number and associated dollar volume of First Presentment/
Reversals 1240-200 credit reversal messages.
* Net Total (Dollar Volume) Debits - credits - debit reversals + credit reversals.
Chargeback Debits Total number and associated dollar volume of non-reversal debit First
Chargeback/1442-450 (Full) and 1442-453 (Partial) and Arbitration
Chargeback/1442–451 (Full) and 1442-454 (Partial) messages.
Chargeback Debit Reversals Total number and associated dollar volume of reversal debit First
Chargeback/1442-450 (Full) and 1442-453 (Partial), and Arbitration
Chargeback/1442-451 (Full) and 1442-454 (Partial) messages.
Field Description
Chargeback Credits Total number and associated dollar volume of non-reversal credit First
Chargeback/1442-450 (Full) and 1442-453 (Partial) and Arbitration
Chargeback/1442-451 (Full) and 1442-454 (Partial) messages.
Chargeback Credit Reversals Total number and associated dollar volume of credit reversal First
Chargeback/1442-450 (Full) and 1442-453 (Partial) and Arbitration
Chargeback/1442-451 (Full) and 1442-454 (Partial) messages.
Representment Debits Total number and associated dollar volume of non-reversal debit
Second Presentment/1240-205 (Full) and 1240-282 (Partial) messages.
Representment Debit Reversals Total number and associated dollar volume of reversal debit Second
Presentment/1240-205 (Full) and 1240-282 (Partial) messages.
Representment Credits Total number and associated dollar volume of non-reversal credit
Second Presentment/1240-205 (Full) and 1240-282 (Partial) messages.
Representment Credit Total number and associated dollar volume of reversal credit Second
Reversals Presentment/1240–205 (Full) and 1240–282 (Partial) messages.
Retrieval Requests Total number and associated dollar volume of non-reversal Retrieval
Request/1644-603 messages.
Retrieval Request Reversals Total number and associated dollar volume of reversal Second
presentment/1240-205 (Full) and 1240-282 (Partial) messages.
Retrieval Request Fulfillments Total number and associated dollar volume of non-reversal
MasterCom and manual (non-MasterCom) fulfillment activity.
Retrieval Request Fulfillment Total number and associated dollar volume of reversal MasterCom
Reversals and manual (non-MasterCom) fulfillment activity.
minimal impact. Mastercard contactless account numbers eligible for the service may belong
to a Mastercard issuer.
Through the Mastercard PAN Mapping Service, Mastercard can provide Mastercard contactless
issuance and processing services as described in this chapter.
2. The Mastercard contactless terminal passes the Mastercard contactless account number
and other authorization information to the acquirer.
3. The acquirer initiates an authorization message containing the Mastercard contactless
account number and sends it to the Mastercard Network.
4. The Mastercard Network maps the Mastercard contactless account number to the
cardholder’s PAN before sending the transaction to the issuer.
5. The issuer responds with an authorization response message containing the PAN.
6. The Mastercard Network maps the cardholder’s PAN back to the Mastercard contactless
account number and sends the response message on to the acquirer.
7. The acquirer forwards the Mastercard contactless account number and other authorization
response information to the Mastercard contactless terminal.
8. The Mastercard Network logs all authorizations for which it performed the Mastercard
PAN Mapping Service and makes this information available to Global Clearing
Management System.
9. The acquirer sends to Global Clearing Management System the corresponding clearing
message, containing the Mastercard contactless account number.
10. Global Clearing Management System maps the Mastercard contactless account number to
the PAN using either the authorization logs or the Mastercard PAN Mapping Service
database before sending the clearing message to the issuer for posting.
11. Issuers can send to Global Clearing Management System subsequent retrieval and
chargeback messages containing the cardholder’s PAN, and Global Clearing Management
System maps the cardholder’s PAN to the Mastercard contactless account number before
sending the message to the acquirer.
Refer to the Authorization Manual for detailed information about using this service for
authorization processing.
Using the MPE to Identify Issuer Account Ranges Participating in the Contactless
Mapping Service
The IPM MPE table IP0040T1—Issuer Account Range contains the Mapping Service Indicator
field. This field identifies issuer account ranges that require the Mastercard PAN Mapping
Service.
This field contains one of the following values for each issuer account range.
Value Description
space The issuer account range does not participate in the Mastercard PAN Mapping
Service.
1 The issuer account range consists of PAN account numbers owned by an issuer, in
which the issuer actively participates in the PAN Mapping Service. Every transaction
containing this account range is to be mapped.
Value Description
2 The issuer account range consists of PAN account numbers owned by an issuer, in
which the issuer actively participates in the PAN Mapping Service. Not all transactions
containing this account range are to be mapped because the issuer is phasing in the
PAN Mapping Service.
4 The issuer account range consists of PAN account numbers provided by Mastercard,
assigned to an issuer that participates in the Processing and Issuance of Non-card
Form Factor option of the contactless Mapping Service by permitting its cardholders
to request a contactless card or non-card form factor through the website.
Before distributing contactless non-card form factors to consumers, Mastercard adds to the
IPM MPE file issuer account ranges that consist of contactless account numbers. The IPM MPE
file contains valid Global Clearing Management System Product IDs, country codes, and other
fields necessary for processing for these issuer account ranges. They are assigned to
participate in all the default interregional, intraregional, and intracountry business services that
are relevant to their assigned country codes.
NOTE: If an issuer account range contains a value of 1-6 in this new field in the IPM MPE,
acquirers must send ALL transactions involving this issuer account range to Mastercard for
authorization and clearing because only the Mastercard systems contain the data needed to
map a contactless account number to a PAN. Transactions processed in an On-Us or
intraprocessor mode will not have access to this mapping data.
not retain and return PDS 0001 in future life cycle messages, although customers may choose
to store and use it within their internal systems to help resolve processing questions that may
occur.
PDS 0001 contains the following two subfields.
Value Description
TC Subfield 2 contains a PAN. 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 PAN Mapping Service. Every transaction containing this
account range is to be mapped. Mapping was based on the authorization logs.
Value Description
1C Subfield 2 contains a contactless account number owned by an issuer, and the issuer is
actively participating in the PAN 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 PAN Mapping Service. Not all transactions in this issuer
account range are mapped, because the issuer is phasing in the PAN 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 PAN Mapping Service. Not all transactions in this issuer
account range are mapped, because the issuer is phasing in the PAN Mapping Service.
Mapping was based on a source other than the authorization logs.
Contents of DE 22 (Point of Service Data Code), Subfield 7 (Card Data input Mode)
Currently, issuers only receive values A or M when sent by the acquirer.
For the mapping of contactless M/Chip and Contact M/Chip transactions in the PAN Mapping
Service, Mastercard will pass through the values (C and M) as provided by the acquirer.
The issuer must send the same values (either the C or M value), which are the original values
sent by the acquirer, in any subsequent First Chargeback/1442 or Arbitration Chargeback/
1442 messages.
3. If Global Clearing Management System cannot match the First Presentment/1240 message
to either the Mastercard PAN Mapping Service authorization log or the Mastercard PAN
Mapping Service database, Global Clearing Management System rejects the transaction.
After successfully mapping the Mastercard contactless account number to a PAN, Global
Clearing Management System uses the PAN in its processing. For example, it uses business
services in which the issuer of the PAN participates, and it delivers the transaction to the
endpoint associated with the issuer of the PAN, as opposed to the Mastercard contactless
account number. If the transaction contains no errors, Global Clearing Management System
modifies the data as follows before sending the First Presentment/1240 to the issuer:
• Moves the Mastercard contactless account number from DE 2 to PDS 0001 (Mastercard
Mapping Service Account Number), subfield 2 (Account Number).
• Populates DE 2 with the PAN
• Passes through the value received from the acquirer in DE 22, subfield 7.
Global Clearing Management System also logs the mapped transaction to a Mastercard PAN
Mapping Service First Presentment history file. Any acknowledgement reconciliation messages
or reporting created for the acquirer is based on the Mastercard contactless account number.
Any notification reconciliation messages or reporting created for the issuer is based on the
PAN.
If the transaction is rejected for any existing Global Clearing Management System error, Global
Clearing Management System sends the rejected transaction back to the acquirer with the
acquirer’s originally submitted values in DE 2.
Issuers will be allowed to use value A (for Contactless Magnetic Stripe transactions), M (for
Contactless M/Chip transactions), R (for Digital Secure Remote Payment containing EMV data
transactions), S (for Digital Secure Remote Payment containing UCAF data transactions or
Card on File, Electronic Commerce tokenization) or T (for Card on File tokenization) for
chargebacks and retrieval requests.
If the chargeback message does not contain DE 22, subfield 7 with a value of A, C or M,
Global Clearing Management System assumes that it did not perform the Mastercard PAN
Mapping Service at the time of the First Presentment/1240. Global Clearing Management
System continues processing the Retrieval Request/1644, First Chargeback/1442, or
Arbitration Chargeback/1442 as it normally does and delivers the message to the acquirer
with the PAN in DE 2 and the issuer’s submitted values in DE 22. If, upon receipt, the acquirer
does not recognize the transaction because the First Presentment/1240 had actually been
submitted with a Mastercard contactless account number, the acquirer must follow existing
dispute resolution rules and procedures that apply when the PAN is not recognized.
If Global Clearing Management System does successfully match the message to the
Mastercard PAN Mapping Service First Presentment history file, and the message is a First
Chargeback/1442, Global Clearing Management System validates that the chargeback
amount is greater than the regional limit for reason code 4837.
If the mapped retrieval or chargeback transaction contains no errors, Global Clearing
Management System modifies the data as follows before sending the message to the
acquirer:
• Move the PAN from DE 2 to PDS 0001, subfield 2
• Populate DE 2 with the contactless account number
• Populate DE 94 (Transaction Originator Institution ID Code) and DE 33 (Forwarding
Institution ID Code) with customer ID information related to the contactless account
number
• Move the value originally submitted by the acquirer in the First Presentment/1240 message
to DE 22, subfield 7 if the issuer provided the other DE 22 subfields in the retrieval or
chargeback
When Global Clearing Management System logs the Retrieval Request/1644, First
Chargeback/1442, or Arbitration Chargeback/1442 message to its existing Retrieval or
Chargeback history files, it logs both the PAN and the Mastercard contactless account number.
Any acknowledgement reconciliation messages or reports created for the issuer are based on
the PAN. Any notification reconciliation messages or reports created for the acquirer are based
on the Mastercard contactless account number.
If Global Clearing Management System cannot match the Fee Collection (Retrieval Fee Billing)/
1740 message to the Mastercard PAN Mapping Service First Presentment history file, Global
Clearing Management System rejects the transaction.
After successfully mapping the Mastercard contactless account number to a PAN, Global
Clearing Management System uses the PAN in its processing. For example, it uses business
services in which the issuer of the PAN participates, and it delivers the transaction to the
endpoint associated with the issuer of the PAN, as opposed to the Mastercard contactless
account number. If the transaction contains no errors, Global Clearing Management System
modifies the data as follows before sending the message to the issuer:
• Move the Mastercard contactless account number from DE 2 to private data subelement
(PDS) 0001 (Mastercard Mapping Service Account Number), subfield 2 (Account Number)
• Populate DE 2 with the PAN
Any acknowledgement reconciliation messages or reports created for the acquirer are based
on the Mastercard contactless account number. Any notification reconciliation messages or
reports created for the issuer are based on the PAN.
MasterCom Processing
All customers have been assigned a MasterCom endpoint to help with the routing of retrieval
and chargeback documentation through the MasterCom system.
The MasterCom system is PC-based and electronically transmits a copy of the requested TID
through the MasterCom server. The result is a clear copy that the issuer and the cardholder
can read, and proof for the acquirer that it fulfilled the request. Once again, Mastercard
strongly recommends that customers use the MasterCom system to ensure timely delivery of
items and to retain subsequent chargeback and presentment rights.
22 (POS Entry Mode), subfield 1 (POS Terminal PAN Entry Mode) with one of the following
values:
– 07 (PAN auto-entry via contactless M/Chip)
– 09 (PAN/Token entry via electronic commerce containing DSRP cryptogram in DE 55
[Integrated Circuit Card System-Related Data])
– 10 (Credential on File)
– 81 (PAN/Token entry via electronic commerce with optional AAV or DSRP cryptogram in
UCAF)
– 90 (PAN auto-entry via magentic stripe)—The full track data has been read from the
data encoded on the card and transmitted within the authorization request in DE 35
(Track 2 Data) or DE 45 (Track 1 Data) without alteration or truncation.
– 91 (PAN auto-entry via contactless magnetic stripe)—The full track data has been
transmitted by the acquirer within the authorization request in DE 35 or DE 45 and
forwarded to the issuer without alteration or truncation.
For electronic commerce (e-commerce) transactions using static tokens, the acquirer will
initiate an authorization request containing the token and DE 22, subfield 1 with one of
the following values:
– 81
– 82 (PAN auto-entry via server [issuer, acquirer, or third party vendor system])
NOTE: For static tokens, cryptography data will not be present in transactions.
3. For secure element and Mastercard Cloud-Based Payment tokens, the Authorization
Platform performs either chip or dynamic CVC 3 data pre-validation, and maps the token
to the primary account number. For static tokens, the Authorization Platform maps the
token to the PAN.
4. If the cryptography validation and PAN mapping are successful, the Authorization Platform
then sends the issuer the authorization request.
5. The issuer responds with an authorization response message, and the Authorization
Platform maps the PAN back to the token and provides the response to the acquirer.
6. The acquirer forwards the token and other authorization response information to the
contactless terminal or merchant payment gateway.
7. The Authorization Platform logs all authorizations for which it performed MDES services
and makes this information available to the Clearing Platform.
8. The acquirer sends the first presentment message to the Clearing Platform containing the
token in DE 2 (Primary Account Number). The acquirer provides DE 22, subfield 7 (Card
Data: Input Mode) with one of the following values:
– A (PAN auto-entry via contactless magnetic stripe)
– B (Magnetic stripe reader inout; track data captured and passed unaltered)
– M (PAN auto-entry via contactless M/Chip)
– R (PAN entry via electronic commerce, including remote chip)
– S (Electronic commerce)
For static tokens, the acquirer provides DE 22, subfield 7 with one of the following values:
– 7 (Credential on file)
– S (Electronic commerce)
– T (PAN auto-entry via server [issuer, acquirer, or third party vendor system])
9. The Clearing Platform maps the token to the PAN using either the authorization logs or
the PAN mapping database and sends the first presentment to the issuer containing:
– DE 2 with the cardholder’s PAN
– DE 14 (Data, Expiration)—If provided on a presentment from the acquirer, DE 14 will
not be present in the presentment message to the issuer when MDES has been applied.
– DE 22, subfield 7 with the value provided by the acquirer.
The Clearing Platform no longer converts values, but passes through these values.
– PDS 0001 (Mastercard Mapping Service Account Number), subfield 1 (Account Number
Type) with one of the following values:
– C (C followed by a space), indicating that subfield 2 (Account Number) contains the
MDES 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 (value CC), indicating that subfield 2 contains the MDES 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 (value H followed by a space), indicating that subfield 2 contains the MDES
Cloud-Based Payments token device account number used at the point of sale. The
account range is owned by an issuer. Mapping was based on the authorization log.
– HC (value HC), indicating that subfield 2 contains the MDES Cloud-Based Payments
token device account number 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.
PDS 0001, subfield 2 (Account Number) contains the token.
For static tokens, PDS 0001, subfield 1 will be the following:
– O (O followed by a space), indicating that subfield 2 contains the MDES Card on File
token submitted by the acquirer. The account range is owned by Mastercard.
Mapping was based on the authorization log.
– OC, indicating that subfield 2 conatins the MDES 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.
PDS 0001, subfield 2 contains the token.
– PDS 0058 (Token Assurance Level) (if applicable)
– PDS 0059 (Token Requestor ID)
– PDS 0207 (Wallet Identifier) (if applicable)
On a first presentment, if there is no match on the authorization logs or PAN mapping
database for the token, the Clearing Platform will reject the first presentment with existing
error number 2358 (DE2 PRIMARY ACCOUNT NUMBER [PAN] INVALID. THE PAN
MAPPING SERVICE CANNOT MAP DE2 TO ANOTHER ACCOUNT NUMBER).
10. Issuers send subsequent retrieval and chargeback messages containing the cardholder’s
PAN in DE 2. For all Retrieval Request/1644 messages, the Clearing Platform attempts to
match the PAN in DE 2 to the MDES First Presentment history file. For First Chargeback/
1442 and Arbitration Chargeback/1442 messages, the Clearing Platform attempts to
match the PAN in DE 2 to the MDES First Presentment history file. If a match is found, the
Clearing Platform will map the cardholder’s PAN to the token before sending the message
to the acquirer. Acquirers will receive retrieval requests or chargeback messages that have
had MDES performed with the following:
– DE 2 with the token
– DE 22, subfield 7 with the original value provided by the acquirer in the first
presentment
– PDS 0001, subfield 1, value TC (Subfield 2 contains a PAN. Mapping was based on a
source other than the authorization logs.); PDS 0001, subfield 2 containing the
cardholder’s PAN
– PDS 0058 (Token Assurance Level) (if applicable)
– PDS 0059 (Token Requestor ID)
– PDS 0207 (Wallet Identifier) (if applicable)
If DE 2 in the Retrieval Request/1644 message or First Chargeback/1442 message cannot
be matched to a First Presentment/1240 message in the MDES First Presentment History
File, the Clearing Platform assumes that it did not perform MDES at the time of the First
Presentment/1240 message. The Clearing Platform continues processing the Retrieval
Request/1644 message, First Chargeback/1442 message, or Arbitration Chargeback/1442
message and delivers the message to the acquirer with the PAN in DE 2. If, upon receipt,
the acquirer does not recognize the transaction because the First Presentment/1240
message had actually been submitted with an MDES token, the acquirer must follow
existing dispute resolution rules and procedures that apply when the PAN is not
recognized.
11. Within second presentments, the acquirer provides the token in DE 2. The Clearing
Platform attempts to match all Second Presentment/1240 messages to the existing
Chargeback history file. If the Clearing Platform is unable to match the message to the
Chargeback history file, it rejects the Second Presentment/1240 message. If the Clearing
Platform successfully matches the Second Presentment/1240 message to the Chargeback
history file, and the Chargeback history file indicates that DE 2 contains an MDES token,
the Clearing Platform maps it to the PAN and uses the PAN in its processing. The Clearing
Platform sends the Second Presentment/1240 message to the issuer containing:
– DE 2 with the cardholder’s PAN
– DE 22, subfield 7 with the value provided by the acquirer
– PDS 0001, subfield 1 with one of the following values:
– C (followed by a space)
– CC
– H (H followed by a space)
– HC
– O (O followed by a space)
– OC
– PDS 0058 (if applicable)
– PDS 0059
– PDS 0207 (if applicable)
NOTE: If an issuer account range contains a value of C in the Mapping Service Indicator field
in the IPM MPE, acquirers must send ALL transactions involving this issuer account range to
Mastercard for authorization and clearing because only the Mastercard systems contain the
data needed to map an MDES token to a PAN. Transactions processed in an On-Us or
intraprocessor mode will not have access to this mapping data.
Value Description
C Space Subfield 2 contains the MDES token used at the point of sale. The account range is
owned by an issuer. Mapping was based on the authorization log.
Value Description
CC Subfield 2 contains the MDES 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 MDES token used at the point of sale. The account range is
owned by an issuer. Mapping was based on the authorization log.
TC Subfield 2 contains a PAN. Mapping was based on a source other than the
authorization logs.
O Subfield 2 contains the MDES 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 MDES 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.
4. The Clearing Platform will validate and when incorrect, reject the First Presentment/1240
message containing PDS 0052 (Electronic Commerce Security Level Indicator), subfield 1
(Security Protocol), subfield 2 (Cardholder Authentication), and subfield 3 (UCAF
Collection Indicator) values if they do not match the correct security level indicator (SLI)
value determined during Authorization processign.
After successfully mapping the MDES token to the PAN, the Clearing Platform uses the PAN in
its processing. For example, it uses business services in which the issuer of the PAN
participates, and it delivers the transaction to the endpoint associated with the issuer of the
PAN, as opposed to the MDES token. If the transaction contains no errors, the Clearing
Platform modifies the data as follows before sending the First Presentment/1240 to the issuer:
• Moves the MDES token from DE 2 to PDS 0001 (Mastercard Mapping Service Account
Number), subfield 2 (Account Number).
• Populates DE 2 with the PAN.
• Passes through the value received from the acquirer in DE 22 (POS Entry Mode), subfield 7
(Card Data: Input Mode).
The Clearing Platform also logs the mapped transaction to a MDES First Presentment history
file. Any acknowledgement reconciliation messages or reporting created for the acquirer is
based on the MDES token. Any notification reconciliation messages or reporting created for
the issuer is based on the PAN.
If the transaction is rejected for any existing Clearing Platform error, the Clearing Platform
sends the rejected transaction back to the acquirer with the acquirer’s originally submitted
values in DE 2 and DE 22.
The Clearing Platform attempts to match this To this combination of fields in the MDES
combination of fields in the retrieval request First Presentment history file
or chargeback message...
DE 2 (Primary Account Number) PAN
DE 31 (Acquirer Reference Data) DE 31
DE 30 (Amounts, Original) subfield 1 (Original DE 4 (Amount, Transaction)
Amount, Transaction)
PDS 0149 (Currency Codes, Amounts, Original), DE 49 (Currency Code, Transaction)
subfield 1 (Currency Code, Original Transaction
Amount)
DE 12 (Date and Time, Local Transaction), subfield DE 12, subfield 1
1 (Date)
If the mapped retrieval or chargeback transaction contains no errors, the Clearing Platform
modifies the data as follows before sending the message to the acquirer:
• Move the PAN from DE 2 to PDS 0001 (Mastercard Mapping Service Account Number),
subfield 2 (Account Number)
• Populate DE 2 with the MDES token
• Populate DE 94 (Transaction Originator Institution ID Code) and DE 33 (Forwarding
Institution ID Code) with customer ID information related to the MDES token
When the Clearing Platform logs the Retrieval Request/1644, First Chargeback/1442, or
Arbitration Chargeback/1442 message to its existing Retrieval or Chargeback history files, it
logs both the primary account number and the MDES token. Any acknowledgement
reconciliation messages or reports created for the issuer are based on the PAN. Any
notification reconciliation messages or reports created for the acquirer are based on the MDES
token.
If DE 2 in the Retrieval Request/1644 message or First Chargeback/1442 message cannot be
matched to a First Presentment/1240 message in the MDES First Presentment history file, the
Clearing Platfrom assumes that it did not perfrom MDES at the time of the Fist Presentment/
1240 message. The Clearing Platform continues processing the Retrieval Request/1644
message, First Chargeback/1442 message, or Arbitration Chargebaxk/1442 message and
delivers the message to the acquirer with the PAN in DE 2. If, upon receipt, the acquirer does
not recognize the trasnaction because the First Presentment/1240 message had actually been
submitted with an MDES token, the acquirer must follow existing dispute resolution rules and
procedures that apply when the PAN is not recognized.
• Move the MDES token from DE 2 to PDS 0001 (Mastercard Mapping Service Account
Number), subfield 2 (Account Number)
• Populate DE 2 with the PAN
Any acknowledgement reconciliation messages or reports created for the acquirer are based
on the MDES token. Any notification reconciliation messages or reports created for the issuer
are based on the PAN.
Fee Collection 1740/messages initiated with the PAN: The issuer populates DE 2 with the PAN
in the Fee Collection/1740 message. The Clearing Platform attempts to match the PAN in DE 2
to the MDES First Presentment history file. If a match found, the Clearing Platform will map
the cardholder’s PAN to the MDES token before sending the message to the acquirer. If the
Clearing Platform cannot match the Fee Collection/1740 message to the First Presentment
history file, the Clearing Platform will continue processing the Fee Collection/1740 message as
a non-PAN mapped transaction. DE 2 in the Fee Collection/1740 message to the acquirer will
contain the PAN.
MasterCom Processing
All customers have been assigned a MasterCom endpoint to help with the routing of retrieval
and chargeback documentation through the MasterCom system.
The MasterCom system is PC-based and electronically transmits a copy of the requested TID
through the MasterCom server. The result is a clear copy that the issuer and the cardholder
can read, and proof for the acquirer that it fulfilled the request. Once again, Mastercard
strongly recommends that customers use the MasterCom system to ensure timely delivery of
items and to retain subsequent chargeback and presentment rights.
Stage Description
1. The VCN is sent to the Global Clearing Management System.
2. The Global Clearing Management System maps the VCN to the cardholder PAN.
The PAN is used during the clearing process.
1. The first attempt to match to the mapping service authorization log according to the
combination of VCN, Banknet Reference Number, and Banknet Date.
– VCN is in DE 2 (Primary Account Number [PAN])
– The Banknet Reference Number and Date are present in DE 63 (Transaction Life
Cycle ID), subfield 2 (Trace ID) in First Presentment/1240 messages.
2. If Global Clearing Management System does not find a match in the mapping service
authorization log, or if DE 63 is not present in the First Presentment/1240 message,
Global Clearing Management System attempts to match to the mapping service
database using the VCN and registration flag.
3. If Global Clearing Management System cannot match the First Presentment/1240
message, Global Clearing Management System rejects the transaction.
3. The issuer receives the cardholder’s PAN in DE 2 (Primary Account Number [PAN]) and the
VCN in PDS 0001 (Mastercard Mapping Service Account Number).
Stage Description
1. The RCN is sent in DE 2.
This DE 2 account number is used during the clearing process.
NOTE: The acquirer only receives the masked RCN in PDS 0001 (Mastercard
Mapping Service Account Number) for retrieval and chargeback requests.
NOTE: Transactions that contain the VCN in DE 2 and which cannot be mapped are rejected
back to the sender.
When acquirers receive PDS 0001, the subfield 2 (Account Number) always contains a real,
masked card number. The real card number (RCN) will be masked according to PCI guidelines
as follows:
• Display the first six digits
• Fill the remaining digits of the real card number with zeros
• Display the final four digits (for example: 1234560000001234 for a 16-digit PAN or
1234560000000001234 for a 19-digit PAN)
NOTE: Clearing and Authorization System On-behalf Services must be requested individually.
The following lists the actions for the chip to Magnetic Stripe Conversion service.
If Chip to Magnetic Stripe Conversion is Y for Then the Global Clearing Management
clearing issuer account range… System will…
DE 55 Remove DE 55
NOTE: The Chip to Magnetic Stripe Conversion service affects issuers only. Acquirers are not
affected by this service.
Sender Receiver
Interchange Interchange
Sender Fee Amount, Receiver Amount,
Amount in Fee, in Fee Amount Fee, in
Recon Recon in Recon Recon
Currency Currency Currency Currency
(PDS 0146, (PDS 0147, (PDS 0146, (PDS 0147,
Transaction Sender Receiver SF 7) SF 7) SF 7) SF 7)
1 Acquirer 1 Issuer 1 -5.00 -5.003987 5.00 5.003987
2 Acquirer 1 Issuer 1 -10.00 -10.001234 10.00 10.001234
3 Acquirer 1 Issuer 1 -20.00 -20.005841 20.00 20.005841
4 Acquirer 2 Issuer 2 -6.00 -6.001223 6.00 6.001223
5 Acquirer 2 Issuer 2 -7.00 -7.003589 7.00 7.003589
6 Acquirer 3 Issuer 1 -8.00 -8.001899 8.00 8.001899
7 Acquirer 2 Issuer 1 -11.00 -11.002651 11.00 11.002651
8 Acquirer 2 Issuer 1 -30.00 -30.003877 30.00 30.003877
9 Acquirer 2 Issuer 1 -40.00 -40.002445 40.00 40.002445
10 Acquirer 4 Issuer 3 -50.00 -50.008511 50.00 50.008511
11 Acquirer 4 Issuer 3 -20.00 -20.007688 20.00 20.007688
EDP Calculation: PDS 0146, subfield 7 and PDS 0147, subfield 7 summed by Sender/Receiver
pairs:
Receiver Receiver
Sender Sender Net Sender Net Receiver Net Net
Net Fee Interchange Adjustment Net Fee Interchange Adjustment
Amount Amount, in Recon Amount Amount, in Recon
in Recon Fee, in Currency in Recon Fee, in Currency
Currency Recon (PDS 0147, Currency Recon (PDS 0147,
(PDS Currency SF 7 minus (PDS Currency SF 7 minus
0146, SF (PDS 0147, PDS 0146, 0146, SF (PDS 0147, PDS 0146,
Sender Receiver 7) SF 7) SF 7) 7) SF 7) SF 7)
Acquirer Issuer 1 -35.00 -35.011062 -0.011062 35.00 35.011062 0.011062
1
Acquirer Issuer 2 -13.00 -13.004812 -0.004812 13.00 13.004812 0.004812
2
Receiver Receiver
Sender Sender Net Sender Net Receiver Net Net
Net Fee Interchange Adjustment Net Fee Interchange Adjustment
Amount Amount, in Recon Amount Amount, in Recon
in Recon Fee, in Currency in Recon Fee, in Currency
Currency Recon (PDS 0147, Currency Recon (PDS 0147,
(PDS Currency SF 7 minus (PDS Currency SF 7 minus
0146, SF (PDS 0147, PDS 0146, 0146, SF (PDS 0147, PDS 0146,
Sender Receiver 7) SF 7) SF 7) 7) SF 7) SF 7)
Acquirer Issuer 1 -8.00 -8.001899 -0.001899 8.00 8.001899 0.001899
3
Acquirer Issuer 1 -81.00 -81.008973 -0.008973 81.00 81.008973 0.008973
2
Acquirer Issuer 3 -70.00 -70.016199 -0.016199 70.00 70.016199 0.016199
4
DE 3 (Processing
DE 93 (Transaction Code), SF 1
Destination (Cardholder DE 4 (Amount, DE 49 (Currency Code,
Institution ID Code) Transaction Type) Transaction) Transaction)
Acquirer 1 19 000000000001 840
Acquirer 2 19 000000000001 840
Acquirer 4 19 000000000002 840
Issuer 1 29 000000000002 840
Issuer 3 29 000000000002 840
NOTE: Most major changes, such as changes that affect all customers globally or all customers
within a specific region, will continue to be implemented in a standard release schedule.
NOTE: For more information about processing cycles, time frames, and thresholds for clearing
transactions, refer to the Processing Cycles and Regulations chapter of the Global Clearing
Management System Reference Manual.
Business service arrangements are established in accordance with local laws and regulations.
For questions about participation in, or the hierarchy of business arrangement qualification,
please contact your Mastercard representative.
NOTE: The definition of the rules for all customer defined arrangements must be consistent
with Mastercard standards (or the standards of the other applicable brands) and established
in accordance with the Mastercard Rules.
depending on the country that is defined for the customers’ issuing account ranges, acquiring
BINs, or both.
Interregional arrangements consist of the International interchange programs and rates
defined by Mastercard (such as International Electronic Interchange [IEI] and Corporate
Purchasing Data Rate II).
The geographic designation for Interregional arrangements consists of a from region and a to
region.
• The from region is defined as the region associated to the value in DE 31 (Acquirer
Reference Data), subfield 2 (Acquirer Reference ID), or in the absence of DE 31, the value in
DE 94 (Transaction Originator Institution ID Code) of the message.
• The to region is defined as the region associated to the value in the DE 2 (Primary Account
Number [PAN]), or in the absence of DE 2 the value in DE 93 (Transaction Destination
Institution ID Code) of the message.
Additionally, IRDs are defined within the arrangement, each with its own unique set of qualification
criteria and corresponding interchange fee structure. The criteria available for customization within an
arrangement are described in the following table.
Global Clearing The set of clearing product codes in PDS 0002 (Global Clearing
Management System Product Management System Product Identifier), derived from DE 2 (Primary
Identifier Account Number [PAN]) that are valid for the card program identifier
within the business service arrangement.
Transaction Function The set of transaction functions (Message Type Identifier plus DE 24
[Function Code]) that are valid for the card program identifier within
the business service arrangement.
Cardholder From Account ID The set of Cardholder From Account ID codes in DE 3 (Processing
Code), subfield 2 (Cardholder From Account Type Code) that are valid
for each transaction function established for the card program
identifier within the business service arrangement.
Message Reason Codes/ The set of Message Reason Codes in DE 25 (Message Reason Code)
Reversal Indicator that are valid for each card program identifier within the business
service arrangement. Defines whether reversals are permitted for the
message reason code.
Geography The valid geographical usage for the brand, expressed as a set of valid
regions, country codes, or a combination of both.
NOTE: When two or more conditions occur on the same day (for example, Sunday = excluded
date, and Processing Date = not excluded), exclusions take precedence and the day will not be
counted in the timeliness calculation.
accommodation fee to the acquirer for transactions involving a manual (non-ATM) cash
disbursement.
Customer-defined manual cash disbursement fees may be calculated as a percentage of the
transaction amount, a unit fee in local currency or U.S. dollars, a minimum cash disbursement
accommodation fee, or any combination thereof.
NOTE: Customers that require additional assistance to support unique local requirements
should contact the appropriate regional office.
When sending transactions to Global Clearing Management System, customers must submit
an interchange rate designator in subfield 4 and may populate subfields 1, 2, and 3 with
either spaces or the appropriate business service data. Global Clearing Management System
will reject any transaction that contains invalid data in PDS 0158, subfields 1 through 4. For all
other valid transactions, Global Clearing Management System will populate subfields 1, 2, and
3 with the system-selected information, and will also populate subfields 5 through 12 of PDS
0158 before forwarding the transaction to the receiving customer.
Global Clearing Management System derives the information according to evaluation of the
message contents against the qualification criteria for business service arrangements in
common between the issuer and acquirer. If Global Clearing Management System cannot find
a business service in which to process the transaction, the Global Clearing Management
System will reject the transaction.
2 Refer to PDS 0158—Business Activity in the IPM Clearing Formats manual for format exceptions to subfield 4.
edits, which use the BIN in the Acquirer Reference Data (ARD) to obtain and validate the card
program.
2 Intraregional
3 Intercountry
4 Intracountry
TT = to issuing region
Global Clearing
Management System Code
and MCBS (billing) Code AMS Region Code Description
01 1 United States
02 A Canada
04 C Asia/Pacific
05 D Europe
06 E Middle East/Africa
Intraregional ID Codes
This table lists and describes the intraregional ID codes found in PDS 0158, subfield 3
(Business Service ID Code).
Interregional ID Codes
This table lists and describes the interregional ID codes found in PDS 0158, subfield 3
(Business Service ID Code).
NOTE: The IPM MPE contains a complete list of business service arrangements.
NOTE: If PDS 0158, subfield 4 is CS, and the merchant or acquirer country is not China (CHN),
or the issuer country is China (CHN), the Clearing Platform will reject the chargeback message
with error number 2709 (PDS0158S4 INTERCHANGE RATE DESIGNATOR INVALID WHEN
MERCHANT OR ACQUIRER COUNTRY IS NOT CHINA OR ISSUER COUNTRY IS CHINA).
PDS 0158, subfield 5—Business Date (Global Clearing Management System provides this field)
PDS 0158, subfield 6—Business Cycle (Global Clearing Management System provides this field)
PDS 0158, subfield 12—Future Use Account Level Management Account Category Code
Management System either selects the card program identifier, if not submitted by the
customer, or validates the customer-submitted card program identifier value in PDS 0158,
subfield 1. If the submitted information in PDS 0158, subfield 2 and PDS 0158, subfield 3 is
not valid for the message or for the Global Clearing Management System-selected or
customer-submitted card program identifier in PDS 0158, subfield 1, Global Clearing
Management System rejects the message.
Using the MPE to Select the Card Program Identifier and Business
Service Information
Global Clearing Management System can select or validate the business activity (PDS 0158,
subfields 1–4) for all financial transactions. The following outlines the steps that Global
Clearing Management System follows to select the business activity for financial transactions
using the IPM Mastercard Parameter Extract (MPE). This includes selection or validation of the
card program identifier, selection or validation of the business service arrangement, and
validation of the interchange rate designator (IRD), if applicable.
Step Action
Data and Message Content Validation
1a. Validate format requirements of the elements used in the selection process
1b. Validate syntax and attributes of elements used in the selection process
3 Card Program Identifier (PDS 0158, subfield 1) may be spaces or may contain a card program identifier value when
submitting business service information in PDS 0158, subfield 2 and PDS 0158, subfield 3.
Step Action
2. Determine whether the transaction requires business service processing
3b. Retrieve and Validate Issuer Card Program Identifier and Business Service Arrangement
Participation (Central Acquiring Process)
Global Clearing Management System determines whether Central Acquiring logic applies to
an intra-European or inter-European transaction by comparing the acquiring BIN country
code (found in table IP0041T1) with the merchant country code (found in DE 43 [Card
Acceptor Name/Location], subfield 6 [Card Acceptor Country Code] of the transaction). If
these country codes are the same, the Standard Process (defined in Step 3a above) applies. If
the country codes are not the same, the Central Acquiring Process applies, as defined in this
subsection.
IRD Validation
7. Validate MTI/Function Code/Processing Code/Reversal Indicator combination for the IRD
11. Determine whether the issuer account range is exempt from Central Acquiring
IRD Validation
validate the qualification criteria for card program identifiers and business service
arrangements.
The format requirements, syntax/attribute definitions, and content of these critical elements
are defined by Mastercard.
If one of the elements shown in the previous figure is mandatory for a message but not
present, Global Clearing Management System rejects the message with the following error
message (where <fldname> represents the name of the missing element):
735 - <fldname> MUST BE PRESENT
The IP2nnnT1 series tables contain valid values based on card program identifier/business
service arrangement combination. They contain some entries for which the Card Program
Identifier field contains all spaces and the Business Service Arrangement Type and Business
Service ID fields contain all zeros. These entries represent the default valid values. At this stage
of validation, when Global Clearing Management System is trying to ensure that all of the
mandatory fields are present and contain valid values, Global Clearing Management System
uses these default valid values.
Later, after Global Clearing Management System assigns a specific card program identifier/
business service arrangement combination, Global Clearing Management System may
perform edits that require a specific subset of valid values depending on the business service.
For these types of edits, Global Clearing Management System uses the IP2nnnT1 table entries
that contain specific values in the Card Program Identifier, Business Service Arrangement Type,
and Business Service ID fields.
5 The table includes card acceptor business codes that are active and life cycled. If the CAB code provided by the
customer is in life cycle status, First Presentment/1240 non-reversal messages will be rejected.
Y for the transaction function, Global Clearing Management System performs business service
processing.
Mastercard defines the following as the specific transaction functions that are eligible.
Step 3a (Standard Process): Retrieve and Match Card Program Identifier and Business
Service Arrangement Participation
Global Clearing Management System retrieves the card program identifier and business
service arrangement participation information for both customers in the message.
Using the tables listed above, Global Clearing Management System finds all card program
identifier/business service arrangement combinations in common between the two customers.
If none are in common, Global Clearing Management System rejects the transaction.
If the two customers have one or more card program identifier/business service arrangement
combinations in common, Global Clearing Management System evaluates each card program
identifier/business service arrangement combination that is in common between the
customers against the characteristics of the transaction. This process begins with Step 4 as
described in the Business Service Arrangement Validation subsection later in this section. If
one arrangement fails the validation, Global Clearing Management System returns to Step 3a
to evaluate the next higher priority issuer card program identifier/business service arrangement
combination.
Step 3b (Central Acquiring Process): Retrieve and Validate Issuer Card Program
Identifier and Business Service Arrangement Participation
Currently, Central Acquiring logic applies only to presentments and chargebacks for which the
issuer, the acquirer, and the card acceptor are in the Europe region. Central Acquiring logic
does not apply to ATM or manual cash advance transactions.
For Central Acquiring, the acquiring bank identification numbers (BINs) do not show all the
relevant intracountry business service arrangements in table IP0091T1. Such an approach
would be too restrictive for acquirers as they would need to wait until they were set up in
table IP0091T1 for a new intracountry arrangement before they could successfully submit
transactions in that market. Therefore, for Central Acquiring situations, Global Clearing
Management System considers only the issuing account range participation as defined in table
IP0090T1.
Global Clearing Management System determines whether Central Acquiring logic applies to
an intra-European transaction by comparing the acquiring BIN country code (found in table
IP0041T1) with the merchant country code (found in DE 43 [Card Acceptor Name/Location],
subfield 6 [Card Acceptor Country Code] of the transaction). If these country codes are the
same, the Standard Process (defined in Step 3a above) applies. If the country codes are not
the same, the Central Acquiring Process applies, as defined in this subsection.
For the Central Acquiring process, Global Clearing Management System retrieves the card
program identifier and business service arrangement participation information for the issuer
only.
Global Clearing Management System then evaluates each card program identifier/business
service arrangement combination in which the issuer participates, in the sequence in which
they are provided in table IP0090T1, to determine whether the acquirer accepts the card
program identifier, and whether the geography and Central Acquiring permission are
appropriate.
To determine whether the acquirer accepts the card program identifier of the card program
identifier/business service arrangement combination being evaluated, Global Clearing
Management System checks all the table IP0041T1 entries for the acquiring BIN. If the
contents of the Card Program Identifier field in any of the acquiring BIN table IP0041T1 entries
match the card program identifier of the card program identifier/business service arrangement
combination being evaluated, Global Clearing Management System considers the
arrangement eligible for further processing. Otherwise, Global Clearing Management System
discards the current arrangement and returns to Step 3b to evaluate the next higher priority
issuer card program identifier/business service arrangement combination.
NOTE: Table 94 is called only when the business service level equals 4 Intra or 3 Inter. It is not
called for M2M.
To validate the geography of the arrangement, Global Clearing Management System looks up
the issuer’s card program identifier/business service arrangement combination in table
IP0094T1 Geographic Restrictions. Table IP0094T1 restricts business service arrangements at
either the country code level or the region level.
If table IP0094T1 has no entry for the card program identifier/business service arrangement
combination, Global Clearing Management System considers the card program identifier/
business service arrangement combination to have no geographic restrictions and, therefore,
it is eligible for further processing.
If table IP0094T1 has at least one entry for the card program identifier/business service
arrangement combination, the business service arrangement combination has at least one
geographic restriction. Global Clearing Management System evaluates each of these entries to
ensure that the transaction meets at least one of the table IP0094T1 geographic restrictions as
follows:
• If the table IP0094T1 entry contains a country code in the Country field, Global Clearing
Management System compares the merchant country code (found in DE 43, subfield 6 of
the transaction) with the Country field in table IP0094T1.
• If the table IP0094T1 entry contains a region code on the Region field, Global Clearing
Management System determines the region associated with the merchant country code of
the transaction and compares it with the Region field in table IP0094T1.
• If the merchant country or region matches the table IP0094T1 country or region, Global
Clearing Management System considers the card program identifier/business service
arrangement combination eligible for further processing.
• If none of the table IP0094T1 entries for the business service arrangement matches the
merchant country/region of the transaction, Global Clearing Management System discards
the current arrangement and returns to Step 3b to evaluate the next higher priority issuer
card program identifier/business service arrangement combination.
If the issuer arrangement being evaluated is not a Customer-to-Customer arrangement,
Global Clearing Management System evaluates the issuer card program identifier/business
service arrangement combination against the characteristics of the transaction. This process
begins with Step 4 as described in the Business Service Arrangement Validation subsection
later in this section.
If the arrangement fails the validation, Global Clearing Management System returns to Step
3b to evaluate the next higher priority issuer card program identifier/business service
arrangement combination. If the issuer arrangement being evaluated is a Customer-to-
Customer arrangement, Global Clearing Management System continues its Central Acquiring
process by validating acquirer participation in this customer-to-customer business service
arrangement. Global Clearing Management System does this by looking up the combination
of acquirer BIN, Customer-to-Customer business service arrangement, and card program
identifier in table IP0091T1.
If no matching entry is in table IP0091T1, the acquirer does not participate in the Customer-
to-Customer business service arrangement; therefore, it cannot be used. Global Clearing
Management System discards the current Customer-to-Customer business service
arrangement and returns to Step 3b to evaluate the next higher priority issuer card program
identifier/business service arrangement combination. If a matching entry is in table IP0091T1
for the Customer-to-Customer business service arrangement, Global Clearing Management
System continues its Central Acquiring process by validating Central Acquiring permission. To
do this, Global Clearing Management System looks up the issuer’s Customer-to-Customer
business service arrangement in table IP0089T1 Business Service Switches.
• If the table IP0089T1 entry contains a Y in the Central Acquired Switch field, the Customer-
to-Customer business service arrangement cannot be used, because an appropriate
intracountry business service arrangement should be used instead for the centrally acquired
transactions. Therefore, Global Clearing Management System discards the current
NOTE: Global Clearing Management System evaluates all original and reversal financial
transactions, with the exception of Global Collection Only transactions, against the
qualification parameters for all eligible card program identifiers and business service
arrangements unless otherwise noted.
NOTE: Global Collection Only transactions bypass all qualification criteria except for Message
Reason Code validation. Selection of the card program identifier and business service
arrangement for Global Collection Only transactions is based only on issuing Account Range
and Acquirer BIN (or sending and receiving customer ID) participation and priority, and
Message Reason Code validation.
When Global Clearing Management System is unable to select an arrangement for the
message or to validate the customer-submitted arrangement information in PDS 0158, Global
Clearing Management System rejects the message. Global Clearing Management System
generates a Message Exception/1644 message with an error code indicating the fields in error
and the reason for the error. Global Clearing Management System generates one Message
Exception/1644 message with one error code for each card program identifier and business
service arrangement combination evaluated (Or if IRD validation is required for the message,
Global Clearing Management System generates one Message Exception/1644 message with
an error code for each card program identifier/business service arrangement/IRD combination
evaluated).
Step 4: Validate the Message Reason Code and Reversal Indicator for the Card
Program Identifier/Business Service Arrangement Combination
In some messages, such as First Presentment/1240 messages, DE 25 (Message Reason Code) is
an optional field. If DE 25 is not present in the message, Global Clearing Management System
performs this step using spaces for the message reason code.
Global Clearing Management System first looks up the combination of Card Program
Identifier, Business Service Arrangement Type, and Business Service ID in table IP0088T1 to
determine whether it is masked to another business service arrangement.
• If table IP0088T1 has no entry that matches all of these values, the business service
arrangement is not masked and Global Clearing Management System will perform all table
lookups using the actual card program identifier and business service arrangement values.
• If table IP0088T1 has an entry that matches all of these values, Global Clearing
Management System obtains the related Masked Card Program Identifier, Masked Business
Service Arrangement Type, and Masked Business Service ID and will perform table
IP0097T1 and IP0098T1 lookups using these masked values instead of the actual card
program identifier and business service arrangement values.
Global Clearing Management System then looks up the combination of message type
identifier (MTI), Function Code, Message Reason Code, Card Program Identifier, Business
Service Arrangement Type, and Business Service ID, in table IP0097T1. When performing this
lookup, Global Clearing Management System uses the masked card program identifier and
business service arrangement values if table IP0088T1 indicates that the business service
arrangement is masked.
If table IP0097T1 has no entry that matches all of these values, Global Clearing Management
System discards the current arrangement and returns to Step 3 to select the next card
program identifier/business service arrangement combination.
If table IP0097T1 has an entry that matches all of these values, Global Clearing Management
System obtains the value in the table IP0097T1 Reversal Indicator field.
• If this value is B, the table IP0097T1 entry is valid for both reversal and non-reversal
transactions, and Global Clearing Management System continues processing with Step 5.
• If this value is R, the table IP0097T1 entry is valid only for reversal transactions. If the
transaction is a reversal, indicated by PDS 0025 (Message Reversal Indicator), subfield 1
(Message Reversal Indicator) being present in the transaction and containing a value of R,
Global Clearing Management System continues processing with Step 5. If the transaction is
not a reversal, Global Clearing Management System discards the current arrangement and
returns to Step 3 to select the next card program identifier/business service arrangement
combination.
• If this value is N, the table IP0097T1 entry is valid only for non-reversal transactions. If the
transaction does not contain PDS 0025, subfield 1 with a value of R, it is not a reversal and
Global Clearing Management System continues processing with Step 5. Otherwise, Global
Clearing Management System discards the current arrangement and returns to Step 3 to
select the next card program identifier/business service arrangement combination.
Step 5: Validate the Processing Code and Reversal Indicator for the Card Program
Identifier/Business Service Arrangement Combination
Global Clearing Management System first looks up the value in DE 3 (Processing Code),
subfield 2 (Cardholder From Account Type Code) of the transaction in table IP2054T1 and
obtains its related masked value. The masked value is located immediately following the actual
value. Global Clearing Management System will perform table IP0098T1 and IP0052T1
lookups using the masked DE 3, subfield 2 value in place of the actual DE 3, subfield 2 value.
Global Clearing Management System then looks up the combination of message type
identifier (MTI), Function Code, Processing Code, Card Program Identifier, Business Service
Arrangement Type, and Business Service ID, in table IP0098T1. Global Clearing Management
System uses the masked DE 3 and masked business service arrangement values where
appropriate.
If table IP0098T1 has no entry that matches all of these values, Global Clearing Management
System discards the current arrangement and returns to Step 3 to select the next card
program identifier/business service arrangement combination.
If table IP0098T1 has an entry that matches all of these values, Global Clearing Management
System obtains the value in the table IP0098T1 Reversal Indicator field.
• If this value is B, the table IP0098T1 entry is valid for both reversal and non-reversal
transactions, and Global Clearing Management System continues processing with Step 6.
• If this value is R, the table IP0098T1 entry is valid only for reversal transactions. If the
transaction is a reversal, indicated by PDS 0025 (Message Reversal Indicator), subfield 1
(Message Reversal Indicator) being present in the transaction and containing a value of R,
Global Clearing Management System continues processing with Step 6. If the transaction is
not a reversal, Global Clearing Management System discards the current arrangement and
returns to Step 3 to select the next card program identifier/business service arrangement
combination.
• If this value is N, the table IP0098T1 entry is valid only for non-reversal transactions. If the
transaction does not contain PDS 0025, subfield 1 with a value of R, it is not a reversal and
Global Clearing Management System continues processing with Step 6. Otherwise, Global
Clearing Management System discards the current arrangement and returns to Step 3 to
select the next card program identifier/business service arrangement combination.
submitted in PDS 0158 (Business Activity), subfield 4 (Interchange Rate Designator) of the
transaction.
• If this field contains N, Global Clearing Management System performs IRD validation
(beginning with Step 8) and determines the correct interchange fee using an IRD value of
spaces.
Step 7: Validate the Processing Code and Reversal Indicator for the IRD
If IRD validation is not required for the transaction, Global Clearing Management System
omits Step 7 and continues processing with Step 8.
Otherwise, Global Clearing Management System looks up the combination of message type
identifier (MTI), Function Code, Processing Code, Card Program Identifier, Business Service
Arrangement Type, Business Service ID, and interchange rate desigator (IRD), in table
IP0052T1. To perform this lookup, Global Clearing Management System uses:
• The masked value for DE 3 (Processing Code), subfield 2 (Cardholder From Account Type
Code), as described in Step 5.
• The actual (unmasked) values for the card program identifier/business service arrangement
combination.
• The actual interchange rate designator in the IRD field.
If table IP0052T1 has no entry that matches all of these values, Global Clearing Management
System discards the current arrangement and returns to Step 3 to select the next card
program identifier and business service arrangement combination.
If table IP0052T1 has an entry that matches all of these values, Global Clearing Management
System obtains the value in the table IP0052T1 Reversal Indicator field.
• If this value is B, the table IP0052T1 entry is valid for both reversal and non-reversal
transactions, and Global Clearing Management System continues processing with Step 8.
• If this value is R, the table IP0052T1 entry is valid only for reversal transactions. If the
transaction is a reversal, indicated by PDS 0025 (Message Reversal Indicator), subfield 1
(Message Reversal Indicator) being present in the transaction and containing a value of R,
Global Clearing Management System continues processing with Step 8. If the transaction is
not a reversal, Global Clearing Management System discards the current arrangement and
returns to Step 3 to select the next card program identifier/business service arrangement
combination.
• If this value is N, the table IP0052T1 entry is valid only for non-reversal transactions. If the
transaction does not contain PDS 0025, subfield 1 with a value of R, it is not a reversal and
Global Clearing Management System continues processing with Step 8. Otherwise, Global
Clearing Management System discards the current arrangement and returns to Step 3 to
select the next card program identifier/business service arrangement combination.
NOTE: Product code validation process is bypassed when the message is a life cycle
transaction and the Product reassignment switch on table IP0040T1 is set to Y or the message
is a first presentment and the first presentment reassignment switch on table IP0040T1 is Y.
Global Clearing Management System looks up the value in DE 2 (Primary Account Number) of
the transaction in table IP0040T1 by finding the table entries for which the DE 2 PAN falls
within the Issuer Account Range—Low and Issuer Account Range—High values in table
IP0040T1. There may be more than one entry in table IP0040T1 for the issuer account range.
Global Clearing Management System chooses the table IP0040T1 entry for which the Card
Program Identifier matches the card program identifier of the card program identifier/business
service arrangement combination being evaluated. From this table IP0040T1 entry, Global
Clearing Management System obtains the related Global Clearing Management System
Product ID for use in table IP0096T1.
The Product Class feature provides the ability to vary interchange rates by product grouping,
while maintaining common interchange structures. The Product Class Override Indicator is
used in the interchange product override functionality. Override of interchange rates by
product code is accomplished by assigning a Product Class Override Indicator to one or more
product codes that would be associated with a given interchange rate value.
An example would be Product Class Override Indicator MCC (Consumer) being used to
indicate a specific rate for a given IRD and Product Class Override Indicator. This Product Class
Override Indicator MCC would be used for product codes MDS, MDH, MCE, MCC, MCG,
MPL, and MDP, thereby avoiding the repetition of each of these product code rates in the
appropriate tables in the member profile extract (MPE). This helps Mastercard to limit the
number of entries in the MPE tables, reducing the delivery time to our customers.
Please refer to the IPM Clearing Formats manual to learn about the Product Class Override
Indicator associated with each product code.
Global Clearing Management System looks up the combination of Card Program Identifier,
Business Service Arrangement Type, Business Service ID, IRD, and Global Clearing
Management System Product ID, in table IP0096T1. To perform this lookup, Global Clearing
Management System uses:
• The actual (unmasked) values for the card program identifier/business service arrangement
combination or use masked values, if found
• The interchange rate designator in the IRD field (if IRD validation is required), or a space in
the IRD field (if IRD validation is not required), as described in Step 6
• The Global Clearing Management System Product ID from table IP0040T1 in the product ID
field
IF… THEN…
There is no entry in table IP0096T1 that matches Global Clearing Management System discards the
all the values mentioned in the previous bullet list current business service arrangement and returns
to Step 3 to select the next card program
identifier/business service arrangement
combination.
There is an entry in table IP0096T1 that matches Global Clearing Management System proceeds to
all the values mentioned in the previous bullet list Step 9 to continue validating the IRD.
There is an entry in table IP0096T1 that matches Global Clearing Management System discards the
all the values mentioned in the previous bullet list, current business service arrangement and returns
and to Step 3 to select the next Card Program
Identifier/Business Service Arrangement
• the Card Program Identifier associated with
combination. This is because ATM transactions
this entry is other than CIR,
involving Mastercard Electronic cards must qualify
• the transaction is an ATM transaction (DE 3 for a business service that supports Cirrus.
[Processing Code], subfield 1 [Cardholder
Transaction Type], value of 1), and
• at least one entry for this account range in
table IP0040T1 contains a Global Clearing
Management System Product ID of MCE, MEC,
or MBE (denoting a Mastercard Electronic
account range).
(IRD), and Card Acceptor Business (CAB) Program, in table IP0095T1. As with Step 8 (Validate
Product Codes for the IRD), GCMS searches for a masked value in table IP0087T1. If found,
Global Clearing Management System uses Masked Card Program Identifier, Masked Business
Service Arrangement Type, Masked Business Service ID, and Masked Interchange Rate
Designator if found in step 8. Spaces are used in the IRD field for look up when IRD validation
is not required as described in Step 6.
If there is no entry in table IP0087T1 that matches all of these values, the Business Service
Arrangement is not masked, and the Global Clearing Management System performs table
IP0095T1 look-up using the actual Card Program Identifier, Business Service Arrangement
Type, Business Service ID, IRD, and Card Acceptor Business (CAB) Program values.
If table IP0095T1 has an entry that matches all of these values, Global Clearing Management
System proceeds to Step 10 to continue validating the business service.
Otherwise, Global Clearing Management System returns to table IP0075T1 and obtains the
next table IP0075T1 entry for the DE 26 value and looks up its Card Acceptor Business (CAB)
Program and business service/IRD information in table IP0095T1.
If Global Clearing Management System does not find an entry in table IP0095T1 that matches
the business service arrangement/IRD and any one of the Card Acceptor Business (CAB)
Programs in the relevant table IP0075T1 entries, Global Clearing Management System discards
the current business service arrangement and returns to Step 3 to select the next card
program identifier/business service arrangement combination.
Service Arrangement) must be submitted for an interchange program that is valid for that
intracountry Business Service Arrangement.
If Global Clearing Management System processes a First Presentment/1240 transaction
occurring between an acquirer and an issuer, and it is submitted with an IRD that does not
qualify for the intracountry Business Service Arrangement but qualifies for a less restrictive
business service such as the regional business Service Arrangement, Global Clearing
Management System will reject the transaction with the following error codes:
• 2425—PDS 0158 (Business Activity), subfield 4 (Interchange Rate Designator) is not valid
for enforced Business Service Arrangement and Acceptance Brand ID code.
• 2451—Submitted Business Service Arrangement is not valid. Must be submitted for
enforced Business Service Arrangement.
First Chargeback/1442, Second Presentment/1240, or Arbitration Chargeback/1442
transactions that contain an IRD that applies to the respective regional Business Service
Arrangement will still be permitted.
The Business Service Selection Enforcement Code does not apply to the following
transactions:
• Fee Collection/1740 messages. Existing functionality as it pertains to Fee Collection/1740
messages remains unchanged.
• Global Collection Only (On-Us and intraprocessor) transactions
• Transactions qualifying for an intracountry Business Service Arrangement submitted with an
airline card acceptor business code (MCC in the range of 3000 to 3299)
Countries with established Business Service Arrangements fall into one of two Business Service
Arrangement categories. Default or Non-Default.
A Life Cycle Indicator is associated with specific qualification parameters, which Global
Clearing Management System uses to determine the valid messages (MTI/Function Code/
Processing Code/Reversal Indicator combinations) for a given parameter. The Life Cycle
Indicator codes associated with each parameter are as follows.
Code Description
A All transaction types are valid.
A Life Cycle Indicator parameter exists in the following IPM MPE tables and associated
parameters.
IP0090T1 Issuer Account Range Card For combination of card program identifier/
Program Identifier and Business business service arrangement type/business service
Service Arrangement Participation arrangement ID/issuer account range-low/issuer
account range-high
IP0091T1 Acquiring BIN Card Program For combination of card program identifier/
Identifier and Business Service business service arrangement type/business service
Arrangement Participation arrangement ID/acquiring BIN
IP0095T1 Card Acceptor Business Program Card Acceptor Business (CAB) Program
Restrictions (new)
For combination of card program identifier/
business service arrangement type/business service
arrangement ID/interchange rate designator
When a parameter has a life cycle indicator of L, only life cycle transactions, as defined by
Mastercard, are valid for the parameter value.
Example
A business service arrangement has the following setup for CAB programs:
CAB Program Setup for Business Service Arrangement 4/123456
In the above example, the CAB Program value for A001 has a Life Cycle Indicator value of L-
Life Cycle Only. In this instance, Global Clearing Management System will accept transactions
that are defined as life cycle transactions only if the card acceptor business code in DE 26 is
assigned to the A001 CAB program.
The following table indicates the transaction types that are defined by Mastercard as life cycle
transactions:
Global Clearing Management System Edits, Fee Assignments, and Fee Calculation
This section describes Global Clearing Management System edits, fee assignments, and fee
calculation.
Edits
The IP2nnT1 series tables contain valid values based on card program identifier/business
service arrangement combination. After Global Clearing Management System assigns a
specific card program identifier/business service arrangement combination, Global Clearing
Management System may perform edits that require specific valid values depending on the
business service. For these types of edits, Global Clearing Management System uses the
IP2nnnT1 table entries that contain specific values in the Card Program Identifier, Business
Service Arrangement Type, and Business Service ID fields. Valid-value edits that are not specific
to a business service arrangement are performed using the default values of spaces and zeros
in the card program identifier/business service arrangement combination fields.
Global Clearing Management System also performs other edits, depending on the business
service assigned, and does not use the IPM MPE for these edits.
If the transaction fails any edits, Global Clearing Management System rejects the transaction.
Otherwise, Global Clearing Management System continues processing and determines the
fees applicable to the transaction.
Fee Assignment
Global Clearing Management System looks up the transaction and business service
information in table IP0052T1. Table IP0052T1 contains pointers to tables IP0053T1 and
IP0057T1. Table IP0053T1 contains the fee groups that are assigned to the transaction. Table
IP0057T1 contains override pointers to table IP0053T1.
Global Clearing Management System already looked up the Card Program Identifier, Business
Service Arrangement Type, Business Service ID, IRD, message type identifier (MTI), Function
Code, and Processing Code information in table IP0052T1, in step 7 of this process. Global
Clearing Management System now looks at the fee code pointer information in the table
IP0052T1 entry.
If the IP0052T1 field Product Class—Card Acceptor Override Pointer contains all zeros, Global
Clearing Management System disregards it and instead looks up the value from table
IP0052T1 Fee Code Pointer in the Fee Code Pointer field in table IP0053T1. Global Clearing
Management System then calculates the fees as described in the Fee Calculation section of
this article.
If the IP0052T1 field Product Class—Card Acceptor Override Pointer contains a non-zero
value, it indicates that an override may exist for the interchange rate and represents a pointer
to table IP0057T1.
Global Clearing Management System searches table IP0057T1 in accordance with the pointer
obtained from table IP0052T1. Each pointer may have multiple entries. The multiple entries
represent a number of different override rates that can be applied. On the basis of a
predetermined hierarchy, Global Clearing Management System searches until the first
matching entry is found. If no match is found, no override applies.
The criteria combinations are listed below in hierarchical order of selection:
1. The Mastercard Assigned ID, in combination with the product class and MCC
2. The Mastercard Assigned ID, in combination with the product class and card acceptor
business type
3. The Mastercard Assigned ID, in combination with the product class
4. The Mastercard Assigned ID, in combination with MCC
5. The Mastercard Assigned ID, in combination with the card acceptor business type
6. The Mastercard Assigned ID
7. The product class, in combination with MCC
8. The product class, in combination with the card acceptor business type
9. MCC
10. The card acceptor business type
11. The product class
If Global Clearing Management System finds an entry in table IP0057T1 that matches the
combination of one of the criteria listed in the hierarchy above, Global Clearing Management
System then looks up the value from that table IP0057T1 entry’s Fee Code Pointer in the Fee
Code Pointer field in table IP0053T1. Global Clearing Management System then applies the
appropriate rate types and calculates the fees as described in the Fee Calculation section of
this manual.
If Global Clearing Management System does not find an entry in table IP0057T1 that matches
the combination of one of the criteria listed in the hierarchy above, Global Clearing
Management System uses the base rate. Global Clearing Management System then calculates
the fees as described in the Fee Calculation section of this manual.
Fee Calculation
Table IP0053T1 contains multiple entries for the same Fee Code Pointer. Each entry contains
the Payment Party (issuer, acquirer, or internal entity), the interchange rate (if applicable) and
rate direction, the interchange unit fee (if applicable) and its direction, the currency code and
exponent for the unit fee (if applicable), and any minimum or maximum fee limits and
direction.
NOTE:
The IPM MPE file does not provide the rates and fees for Customer-to-Customer business
service arrangements, because this information is proprietary. The Customer-to-Customer
business service arrangement and IRD parameters are stored in the IPM MPE file, but the Fee
Code Pointer and Product Class—Card Acceptor Override Pointer fields in table IP0052T1 that
normally point to the correct fee entries in tables IP0057T1, IP0053T1, or both, contain all
zeros for Customer-to-Customer arrangements.
The table IP0053T1 entries are grouped by Rate Type. For example, Rate Type 001 is the
interchange fee and Rate Type 014 is the first-level corporate incentive discount (currently
applies only to intra-European and inter-European transactions). For Rate Types other than
001, Global Clearing Management System determines whether to apply the fees according to
internal programming logic. For example, Global Clearing Management System applies the
Rate Type 014 first-level corporate incentive discount only if the transaction is accompanied by
the required addendum elements. Participating customers understand the conditions in which
the various Rate Types apply to business service arrangements in which they participate.
The Rate Types are as follows:
• 000—Cash Advance Fee (applies to manual cash disbursement transactions)
• 001—Interchange Fee
• 002—Merchant Investment Fee
• 010—IVA on interchange fee (specific to Mexico processing)
• 013—ATM Late Presentment Fee (Currently specific to Europe processing. Applies to non-
reversal First Presentment ATM transactions for which the transaction date is older than 45
days.
• 014—First-level Corporate incentive discount (applies when one corporate IRD can have
different rates, depending on the presence of valid addendum data. Currently specific to
Europe processing)
• 015—Purchase with Cash Back (applies only to the cash back portion of a purchase with
cash back transaction)
• 016—Rewards Program
• 017—Second-level Corporate Incentive discount (applies when the transaction qualifies for
neither the First-level Corporate incentive discount nor the U.K. Summary VAT Incentive
discount, but the acquirer provides information in PDS 0502 [Custom Identifier]. Currently
specific to Europe processing)
• 018—New UK Summary VAT Incentive Interchange (applies when the transaction does not
qualify for the First-level Corporate Incentive discount, but the acquirer submits the data
needed for Mastercard to generate the U.K. Summary VAT Invoice on behalf of the
merchant. Required data is:
– PDS 0508 [Customer Code]
– PDS 0596 [Card Acceptor Tax ID], in which subfield 1 [Card Acceptor Tax ID] contains
the correct tax ID and subfield 2 [Card Acceptor Tax ID Provided Code] contains value Y
– PDS 0597 [Total Tax Amount]
– PDS 0600 [Card Acceptor Reference Number]
– PDS 0641 [Product Code]
– PDS 0642 [Item Description]
– PDS 0647 [Extended Item Amount], with a non-zero value
– PDS 0682 [Detail Tax Amount 1])
• 019—Merchant Interchange
• 020—Europe Enhanced Value
their participation in specific settlement services; however, all customers are required to
participate in at least one regional settlement service. Clearing activity between two customers
usually is settled at the lowest possible common settlement service level. If a customer pair
does not settle in a common settlement service, the customers settle at their respective
regional settlement service accounts. The defined regional default service for the customer will
be used if no other settlement service can be applied to the transaction.
Global Clearing Management System supports the settlement service levels listed in the
following table.
Settlement
Service Level Description
Bilateral Customers participating in a bilateral agreement instruct Mastercard to clear their
transactions through Global Clearing Management System applying all
appropriate business rules. The customers settle these transactions directly rather
than through the Mastercard Settlement Account Management (S.A.M.) system.
Settlement
Service Level Description
Regional A settlement agreement involving customers that may settle in different currencies
and that may use different settlement banks. This is the default agreement; that is,
transactions settled by Mastercard that do not qualify for intracurrency settlement
are automatically settled in a regional settlement service. Transactions that qualify
for regional settlement are settled in U.S. dollars or a local currency approved by
Mastercard, at a settlement bank defined by Mastercard.
Each customer ID must participate in at least one regional settlement service. If a
customer participates in more than one regional settlement service, it must
designate one regional settlement service as the default service, with no selection
criteria. For the other regional settlement services, the customer must define
specific settlement service selection criteria to indicate the circumstances in which
Global Clearing Management System should select each of the other regional
services.
Base currency is the currency that Mastercard uses as the basis for settlement calculations. All
transaction currencies are converted against this currency when determining the customer
reconciliation amount in the reconciliation currency. Summing all reconciliation amounts in
base reconciliation currency will net to zero.
Customers may specify more than one account within each settlement service to segregate
settlement activity according to criteria within the transaction, such as card program, account
range, or BIN. However, each account must be in the currency supported by the agreement.
NOTE: The Global Settlement Services department must approve all settlement arrangements
requested by a customer.
To illustrate the settlement service selection process, assume that the following customers
participate in settlement service agreements, with no additional criteria specified, as shown in
the following table.
005678 X X
009876 X
Assume that customers 001234 and 005678 participate in the same intracurrency settlement
agreement.
According to the information above, the following settlement services would be selected:
Transactions from 001234 to/from 005678⇛ Intracurrency settlement
Transactions from 005678 to/from 009876⇛ Regional settlement
Transactions from 009876 to/from 001234⇛ Regional settlement
NOTE: Global Clearing Management System does not perform settlement service selection for
Global Collection Only transactions because these transactions are submitted for reporting
purposes only.
Account Range Derived from DE 2 If selected by the customer, this may be used for
(Primary Account the settlement service/TAA selection.
Number [PAN])
This element identifies the account range
associated with the cardholder account number
of the transaction.
Acquiring BIN DE 31 (Acquirer If selected by the customer, this may be used for
Reference Data), settlement service/TAA selection.
subfield 2 (Acquirer
This element identifies the acquiring BIN
Reference ID)
associated with the acquirer of the transaction.
Issuing/Acquiring/Both Transaction Function If selected by the customer, this may be used for
Activity (MTI plus DE 24 settlement service/TAA selection.
[Function Code])
The transaction function is used to classify a
transaction as issuing and acquiring activity.
Fee collection messages are considered an
acquirer transaction for the sending ICA when
this option is used.
NOTE: The customer’s transfer agent (TA) may be the customer or a separate entity that the
customer authorizes to settle with Mastercard on its behalf.
A TAA is a combination of the customer’s transfer agent (TA) and the customer bank account
number.
The following is an example of the settlement service selection process. Assume both
customers participate in an intracurrency service using Canada Dollars (CAD) as the
reconciliation currency. Customer ID 001234 is both an issuer and an acquirer. This customer
has criteria established for the Intracurrency 1 settlement service. The customer chooses to
settle only its issuing activity submitted with an assigned card program identifier of Mastercard
Credit (MCC). Customer ID 005678 is an issuer only and has not specified criteria in order for
transactions to qualify in this service.
The transaction is a First Presentment/1240 message and assigned a card program identifier of
MCC. The transaction is sent by customer ID 001234 and received by customer ID 005678.
Settlement Iss/Acq
Customer Service CPI Acct Rg Acq BIN Act TAA Txn Qualify
001234 Intracurrency 1 MCC — — Issuing 11111 No
CAD
selection process. For example, by using the selection criteria, customers determine when they
can submit chargeback transactions in their local currency as opposed to U.S. dollars.
Settlement
Customer Service ID CPI Acct Rg Acq BIN Iss/Acq Act Effective Date
001234 Intracurrency 1 Not Not Not Not Specified 1 Dec 2003
Specified Specified Specified
Settlement
Customer Service ID CPI Acct Rg Acq BIN Iss/Acq Act Effective Date
Intracurrency 2 MCC Not Not Not Specified 15 May 2004
Specified Specified
Transactions submitted between customer 001234 and customer 005678 with an assigned
card program identifier of MCC and processed on or after May 15th 2004, will be qualified
for the Intracurrency 2 settlement agreement. These transactions could be qualified for either
the Intracurrency 1 or the Intracurrency 2 settlement service agreement. However, the
Intracurrency 2 agreement specifying all transactions with an assigned card program identifier
of MCC contains more specific criteria, and is thus the selected settlement service agreement.
Transactions submitted between customer 001234 and customer 005678 with an assigned
card program identifier other than MCC will be qualified for the Intracurrency 1 settlement
agreement.
Transactions submitted between customer 001234 and customer 009012 do not have an
intracurrency settlement agreement in common and, therefore, would use the regional
settlement service selection.
Example 2
Customer 001234 and customer 005678 both participate in intracurrency settlement
agreements with the specified criteria in the following table.
Settlement Iss/Acq
Customer Service ID CPI Acct Rg Acq BIN Act Effective Date
001234 Intracurrency 1 Not Not Not Not 1 Dec 2003
Specified Specified Specified Specified
Transactions submitted between customer 001234 and customer 005678 on or after 15 May
2004 could be qualified for either the Intracurrency 1 or the Intracurrency 2 settlement
agreement. There are no criteria for either service to help the system decide. Therefore, the
selection process will use the most recent effective date and qualify transactions between
these customers in the Intracurrency 2 service.
The above example (Example 2) is included to explain Global Clearing Management System
functionality. In reality, customers would add specific criteria to one of these settlement service
selection setups, or delete one, instead of defining two settlement services with no selection
criteria.
Step 2—Settlement Service and TAA Selection
For each payment party (the sender and the receiver), identify all transfer agent assignments
that meet each customer’s criteria specified within the common settlement services identified
in Step 1.
Step 2a—Settlement Service and Issuer TAA Selection
Settlement service is assigned according to one of the following:
• If there is only one intracurrency settlement service in common and only one TAA for each
payment party that matches the transaction data, Global Clearing Management System
assigns that settlement service and TAA combination to the transaction for each payment
party.
• If there are multiple settlement services and/or TAA combinations with customized
assignment criteria that match the transaction data, the issuing customer’s assignment that
has the most specific criteria matching the transaction is used to determine the service and
the issuing customer TAA.
• If there are multiple TAA assignments for the issuing customer that match the transaction
data, the assignment with the most recent effective date is used.
Step 2b—Acquirer TAA Selection
Once the settlement service and TAA are assigned for the issuing customer, the acquiring
customer’s TAA is selected from those identified within the selected settlement service that
match the transaction criteria:
• If there is only one TAA for the acquirer within the selected settlement service, that
assignment is used for the acquirer’s settlement.
• If there are multiple TAA combinations with customized assignment criteria that match the
transaction data, the assignment that has the most specific criteria matching the
transaction is used to determine the acquiring customer’s TAA.
• If there are multiple TAA assignments for the acquiring customer that match the
transaction data, the assignment with the most recent effective date is used.
Example
To illustrate the TAA selection process, assume that both customers participate in the
Intracurrency 1 service and that customer 001234 is the issuing customer with the specified
criteria shown in the following table.
Transactions submitted with a transaction currency of HKD that are assigned a card program
identifier of MCC will be assigned the settlement service ID Intracurrency 2 for both
customers, and TAA of ZZZ for customer 001234 because it is the assignment with the most
recent effective date. Because the transaction meets both of the acquirer’s TAA criteria for the
Intracurrency 2 agreement, the TAA of BBBB would be chosen because it has the acquirer’s
most specific criteria that match the transaction.
Step 3—Transaction Amount and Fee Calculation
The transaction amount is converted to the intracurrency account currency (reconciliation
currency), if necessary. Additionally, the interchange fees are calculated in the intracurrency
account currency (reconciliation currency).
The settlement service selection process described in the previous section does not apply to
transactions processed at the regional settlement service level. Regional level services are
qualified independently for the sender and receiver against the customer’s specified criteria, as
follows:
• If only one regional settlement service and TAA combination is established for a payment
party that matches the transaction data, Global Clearing Management System assigns that
TAA and account currency to the transaction.
• If multiple settlement services and/or TAAs are established with customized assignment
criteria for a payment party that matches the transaction data, Global Clearing
Management System assigns the settlement service and TAA combination with the most
specific criteria. If more than one settlement service and TAA combination have the same
level of specificity, the TAA with the most recent effective date is selected.
• The default settlement service and TAA are selected when no selection criteria are defined
that match the transaction.
Example 1
To illustrate the service selection process, assume that a customer participates in settlement
service agreements with the specified selection criteria shown in the following table.
001234 Regional 2 YYYY, CAD MCC Not Not Specified Not Specified
Specified
Transactions submitted with an assigned card program identifier of MCC will be assigned the
settlement service ID Regional 2 and account YYYY because it has the most specific criteria
that match the transaction. Transactions submitted with an assigned card program identifier
other than MCC would be assigned to the settlement service ID Regional 1 and account
XXXX.
Example 2
To illustrate the settlement service TAA account selection process, assume that a customer
participates in the regional settlement service agreements as specified in the following table.
The optional settlement service selection criteria defined above can have multiple occurrences
per customer and are used to determine or restrict settlement account selection. Each unique
grouping represents the criteria used to select a specific customer ID, TA, and TAA
combination. The more specific the criteria defined by the customer, the more combinations
of customer ID, TA, and TAA will exist.
Customer 005678 is an issuer or acquirer. In this example, all issuing transactions with a card
program identifier of MCC or DMC and a transaction currency of USD will be settled in USD
through the Regional 1 service. However, transactions with a card program identifier of MCC
will be settled using VVVV and transactions with DMC will be settled using account XXXX. All
acquiring transactions will be settled in CAD through the Regional 2 service in account YYYY
before 15 Jan 2004 and will be settled in account ZZZZ on or after 15 Jan 2004. All other
issuing transactions will settle in USD through the Regional 3 Service in account AAAA.
Step 2—Transaction Amount and Fee Calculation
The transaction amount is converted through U.S. dollars to the TAA account currency
(reconciliation currency). Interchange fees are calculated in U.S. dollars and converted to each
TAA account currency.
NOTE: In addition to the six primary clearing cycles, a seventh clearing cycle exists for Mexico
domestic switching transactions. For more information on the seven clearing cycles, refer to
the Daily Clearing Cycle Schedule section.
Settlement
Service Level Fee Calculation Method
Intracurrency • Transaction amounts and fixed fees are converted to the reconciliation currency
(if necessary).
• Fees are calculated in the reconciliation currency.
• Fees are converted to U.S. dollars for reporting purposes.
Settlement
Service Level Fee Calculation Method
Regional • Transaction amounts and fixed fees are converted to U.S. dollars (if necessary).
• Fees are calculated in U.S. dollars.
• Transaction amounts and calculated fees are converted to each customer’s
reconciliation currency and remain in U.S. dollars for reporting purposes.
Settlement Service Transfer Agent Populated according to the Transfer Agent Assignment bank
Account account number for the receiving customer
3 = Intracurrency
Settlement Foreign Exchange Rate Class Populated according to the currency conversion rate type
Code used:
Settlement Date Populated with the date on which net settlement positions
are determined. This date matches the date of the
corresponding Settlement Advisement generated from the
Mastercard Settlement Account Management (S.A.M.)
system.
If Global Clearing Management System assigns a settlement
service in which the customer does not provide the
settlement date, this field contains the appropriate
settlement service date, as calculated by Global Clearing
Management System for the receiving customer.
If Global Clearing Management System assigns a settlement
service in which the customer is required to provide the
settlement date, this field contains the customer submitted
settlement date.
This date is adjusted for each settlement service level and
settlement service ID.
customer a method to ensure that appropriate funds are in place to effect settlement or
notifies the customer about funds that will be available.
NOTE: For more information about settlement advisements and the Net Settlement
Information Form (NSIF), refer to the Settlement Manual.
Term Description
Base Amount Transaction amount converted to U.S.
dollars.
Computed Cross Rates An exchange rate between two non-
U.S. dollar currencies computed by
reference to the U.S. dollar.
Mastercard-Issued Cross Rates Buy, mid, and sell rates for certain non-
U.S. dollar currency pairs set by
Mastercard (Applies to regional
settlement service only).
Mastercard-Issued USD Rates Buy, mid, and sell rates against the U.S.
dollar set by Mastercard.
Reference Currency Reference currency is quoted as one
unit per a certain amount of foreign
currency.
NOTE: Currency conversion and foreign exchange are used interchangeably in the context of
the information presented in this chapter.
Reconciliation and settlement are used interchangeably in the context of the information
presented in this chapter.
NOTE: There may be other arrangements defined for those customers participating in
bilateral agreements. For more information about participation in bilateral agreements, refer
to the Settlement Manual.
• Total Interchange Amount: Fixed Interchange Amount and Variable Interchange Amount in
acquirer reconciliation currency are added to calculate Total Interchange Amount in
acquirer reconciliation currency.
• Acquirer Net Reconciliation Amount: Total Interchange Amount is subtracted/added from
Total Acquirer Reconciliation Amount to calculate Acquirer Net Reconciliation Amount in
acquirer reconciliation currency.
NOTE: Mastercard provides the T057 Currency Conversion Rate File, the Acquirer Currency
Conversion Files (TQQ4—Regional First Presentments, TQQ8—Regional Second Presentments,
and TQX2—Intracurrency Presentments), and the Clearing Detail File (IP755120-AA) to
facilitate acquirer reconciliation. The Acquirer Currency Conversion Rate File provides the
effective currency conversion rate of all possible ISO currency codes between the transaction
currency code and the acquirer reconciliation currency code and is available at the same time
as the T057 file. The Clearing Detail File provides transaction-level details for the acquirer
after each clearing cycle. Details regarding all the data elements provided in these files and
how customers can register for them are provided at the end of this chapter.
All above mentioned data elements are shown in the Clearing Detail File (IP755120-AA) as
follows.
Total Interchange Amount in acquirer PDS 0146 (Amounts, Transaction Fee), subfield 7
reconciliation currency (Amount, Fee, Reconciliation)
Currency Conversion Rate: Transaction Amount to DE 9 (Conversion Rate, Reconciliation)
Acquirer Reconciliation Amount
The following are examples showing currency conversion on the acquirer side of transactions
with each using Mastercard-Issued USD Rates and Mastercard-Issued Cross Rates.
NOTE: For simplicity, all examples are presented with rounding to the second decimal point.
To see precise rounding conventions and calculations of the system, refer to the Rounding of
Global Clearing Management System Currency Conversion section of this manual.
Assumptions
• Transaction Amount: CAD 50.00
• Acquirer Reconciliation Currency: CAD
• Fixed Interchange Amount: CAD 0.10
• Mastercard-Issued USD Rate (USD-CAD): 1 USD = 1.25 CAD; Reference Currency: USD
• Interchange Rate = 1.00%
DE 5 CAD 50.00
1. Locate the record in the Acquirer Currency Conversion Rate File where the Transaction
Currency matches the currency in field 2 and the Acquirer Reconciliation Currency
matches the currency in field 3 and extract the corresponding Conversion Rate in field 5.
Conversion Rate (field 5) = 1.00
2. Determine the total acquirer reconciliation amount (DE 5) by multiplying the transaction
amount (DE 4) by the conversion rate (field 5)
Total Acquirer Reconciliation Amount (DE 5) = Transaction Amount (DE 4) x Conversion
Rate (field 5)
CAD 50.00 x 1.0000 = CAD 50.00
NOTE: Since transaction currency and acquirer reconciliation currency are the same, Total
Acquirer Reconciliation Amount and Transaction Amount are equal.
NOTE: Since transaction currency and acquirer reconciliation currency are the same,
Variable Interchange Amount in acquirer reconciliation currency is same as the amount in
transaction currency.
NOTE: Since fixed interchange amount currency and acquirer reconciliation currency are
the same, Fixed Interchange Amount in acquirer reconciliation currency is same as the
amount in fixed interchange amount currency.
Assumptions
• Transaction Amount: GBP 30.00
• Acquirer Reconciliation Currency: AUD
• Mastercard-Issued Cross Rate (GBP-AUD): GBP 1 = AUD 2.0000; Reference Currency GBP
• Interchange Rate = 1.20%
• Fixed Interchange Amount = AUD 0.10
1. Locate the record in the Acquirer Currency Conversion Rate File where the Transaction
Currency (GBP) matches the currency in field 2 and the Acquirer Reconciliation Currency
(AUD) matches the currency in field 3 and extract the corresponding Conversion Rate in
field 5.
Conversion Rate (field 5) = 2.00
2. Determine Total Acquirer Reconciliation Amount (DE 5) by multiplying Transaction Amount
(DE 4) by Conversion Rate (field 5)
Total Acquirer Reconciliation Amount (DE 5) = Transaction Amount (DE 4) x Conversion
Rate (field 5)
GBP 30.00 x 2.0000 = AUD 60.00
NOTE: Since fixed interchange amount currency and acquirer reconciliation currency are
the same, Fixed Interchange Amount in acquirer reconciliation currency is same as the
amount in fixed interchange amount currency.
the same period as the T057 file and in DE 9 for the transaction as presented in the Clearing
Detail File once the transaction is processed.
Assumptions
• Transaction Amount: JPY 3,500
• Acquirer Reconciliation Currency: USD
• Mastercard-Issued Cross Rate (USD-JPY): USD 1 = JPY 108.3300; Reference Currency USD
• Interchange Rate = 1.20%
• Fixed Interchange Amount = USD 0.15
DE 5 USD 32.31
1. Locate the record in the Acquirer Currency Conversion Rate File where the Transaction
Currency (JPY) matches the currency in field 2 and the Acquirer Reconciliation Currency
(USD) matches the currency in field 3 and extract the corresponding Conversion Rate in
field 5.
Conversion Rate (field 5) = 0.009231
NOTE: Since fixed interchange amount currency and acquirer reconciliation currency are
the same, Fixed Interchange Amount in acquirer reconciliation currency is same as the
amount in fixed interchange amount currency.
Clearing system will perform currency conversion by going through the U.S. dollar and using
two Mastercard-Issued Rates to calculate a cross rate (computed cross rate).
First, the system will calculate a cross rate by dividing the currency conversion rate for the
reconciliation currency as published in field 7 of the T057 file by the currency conversion rate
for the transaction currency published in field 8. Then, this computed cross rate will be used
to multiply the transaction amount to obtain the reconciliation amount in the reconciliation
currency. Similarly, the computed cross rate will be used to convert the variable interchange
from the transaction currency to the reconciliation currency. The computed cross rate is also
provided in the Acquirer Currency Conversion Rate File. In addition, the Clearing Detail File
provides the computed cross rate for each transaction in DE 9 and can be used for
reconciliation.
Regarding fixed interchange, any time the fixed interchange currency is different from the
acquirer reconciliation currency, the currency conversion process will follow the same process
as described in the examples above where the fixed interchange amount will be converted as
any other transaction amount.
• Total Interchange Amount: Fixed Interchange Amount and Variable Interchange Amount in
issuer reconciliation currency are added to calculate Total Interchange Amount in issuer
reconciliation currency.
• Issuer Net Reconciliation Amount: Total Interchange Amount in issuer reconciliation
currency is subtracted/added from Total Issuer Reconciliation Amount to calculate Issuer
Net Reconciliation Amount in issuer reconciliation currency.
The above-mentioned data elements are shown in the IPM File as follows.
Data Element/Private
Description Data Subelement Notes
Transaction Amount DE 4
Data Element/Private
Description Data Subelement Notes
Total Cardholder Billing DE 6 Inclusive of Issuer Currency Conversion Rate
Amount (ICCR) Amount or Cross Border Fee Manager
Amount if applicable
Currency Conversion DE 9 (Conversion Rate, Effective conversion rate (inclusive of CCA if
Rate: Transaction Reconciliation) applicable)
Amount to Issuer
Reconciliation Amount
Currency Conversion DE 10 (Conversion Rate, Effective conversion rate (Inclusive of Issuer
Rate: Transaction Cardholder Billing) Currency Conversion Rate [ICCR] Amount or Cross
Amount to Cardholder Border Fee Manager Amount if applicable)
Billing Amount
Currency Conversion DE 111 (Amount,
Assessment in issuer Currency Conversion
cardholder billing Assessment)
currency
Total Interchange PDS 0146, subfield 7
Amount in issuer
reconciliation currency
The following are examples that illustrate how interchange, CCA, and ICCR or Cross Border
Fee Manager Rates are calculated throughout the transaction flow. For the specific currency
conversion rates for any transaction scenario, issuers can use the transaction IPM message, in
particular DE 9 and DE 10 as described above. The currency conversion rates in these data
elements will be the same, or derived from, the rates in the T057 file, which are wholesale
market rates.
Assumptions
• Transaction Amount: MXN 180.00
• Cardholder Billing Currency: USD
• Issuer Reconciliation Currency: USD
• Mastercard-Issued USD Rate (USD-MXN): USD 1 = MXN 18.0000
• CCA Rate = 0.20%
• ICCR or Cross Border Fee Manager Rate = 0%
Data Element/Private
Data Subelement Value Notes
DE 4 MXN 180.00
Operational Method
1. Obtain DE 4, DE 9 and DE 10 from the outbound IPM file.
2. Determine Total Cardholder Billing Amount (DE 6) by multiplying DE 4 and DE 10.
Total Cardholder Billing Amount (DE 6) = Transaction Amount (DE 4) x Conversion Rate
(DE 10)
MXN 180.00 x 0.055556 = USD 10.00 (Inclusive of Issuer Currency Conversion Rate
[ICCR] Amount or Cross Border Fee Manager Amount if applicable)
3. Determine Total Issuer Reconciliation Amount (DE 5) by multiplying DE 4 and DE 9.
Total Issuer Reconciliation Amount (DE 5) = Transaction Amount (DE 4) x Conversion Rate
(DE 9)
MXN 180.00 x 0.055667 = USD 10.02006, rounded to USD 10.02 (inclusive of CCA if
applicable)
NOTE: Since fixed interchange amount currency and issuer reconciliation currency are the
same, Fixed Interchange Amount in issuer reconciliation currency is same as the amount in
fixed interchange amount currency.
NOTE: Since cardholder billing currency and issuer reconciliation currency are the same,
Initial Issuer Reconciliation Amount in issuer reconciliation currency is same as Initial
Cardholder Billing Amount in cardholder billing currency.
NOTE: Since cardholder billing currency and issuer reconciliation currency are the same,
Currency Conversion Assessment in issuer reconciliation currency is same as Currency
Conversion Assessment in cardholder billing currency.
Assumptions
• Transaction Amount: PLN 600.00
• Cardholder Billing Currency: EUR
• Issuer Reconciliation Currency: EUR
• Mastercard-Issued Cross Rate (EUR-PLN): EUR 1 = PLN 5.0000; Reference Currency is EUR
• ICCR or Cross Border Fee Manager Rate = 3.00%
• CCA Rate = 0.20%
• Interchange Rate = 1.20%
• Fixed Interchange Amount = EUR 0.10
The following table contains the transaction level details through Mastercard’s outbound IPM
file.
Data Element/Private
Data Subelement Value Notes
DE 4 PLN 600.00
Data Element/Private
Data Subelement Value Notes
DE 6 EUR 123.60 Inclusive of Issuer Currency Conversion Rate
(ICCR) Amount or Cross Border Fee Manager
Amount if applicable
DE 9 0.20040 Effective conversion rate (inclusive of CCA if
applicable)
DE 10 0.20600 Effective conversion rate (Inclusive of Issuer
Currency Conversion Rate [ICCR] Amount or Cross
Border Fee Manager Amount if applicable)
DE 111 EUR 0.24
PDS 0146, subfield 7 EUR 1.54
Operational Method
1. Obtain DE 4, DE 9, and DE 10 from the outbound IPM file.
2. Determine Total Cardholder Billing Amount (DE 6) by multiplying DE 4 and DE 10.
Total Cardholder Billing Amount (DE 6) = Transaction Amount (DE 4) x Conversion Rate
(DE 10)
PLN 600.00 x 0.20600 = EUR 123.60 (Inclusive of Issuer Currency Conversion Rate [ICCR]
Amount or Cross Border Fee Manager Amount if applicable)
3. Determine Total Issuer Reconciliation Amount (DE 5) by multiplying DE 4 and DE 9.
Total Issuer Reconciliation Amount (DE 5) = Transaction Amount (DE 4) x Conversion Rate
(DE 9)
PLN 600.00 x 0.20040 = EUR 120.24 (inclusive of CCA if applicable)
NOTE: Since fixed interchange amount currency and issuer reconciliation currency are the
same, Fixed Interchange Amount in issuer reconciliation currency is same as the amount in
fixed interchange amount currency.
NOTE: Since cardholder billing currency and issuer reconciliation currency are the same,
Initial Issuer Reconciliation Amount in issuer reconciliation currency is same as Initial
Cardholder Billing Amount in cardholder billing currency.
NOTE: Since cardholder billing currency and issuer reconciliation currency are the same,
Currency Conversion Assessment in issuer reconciliation currency is same as Currency
Conversion Assessment in cardholder billing currency.
Issuer Net Reconciliation Amount = Total Issuer Reconciliation Amount – Total Interchange
Amount in issuer reconciliation currency
EUR 120.24 – EUR 1.54 = EUR 118.70
• If the number in the low order position is equal to or greater than 5, the number in the
minor currency position is increased by a value of 1 to round the amount. For example,
17.559048 results in 17.56.
• If the number in the low order position is less than 5, the low order positions are truncated
without rounding the amount. For example, 17.530011 results in 17.53.
Global Clearing Management System only rounds amounts to the number of positions to the
right of the decimal point specified by the currency exponent, once they are calculated in the
final (issuer/acquirer reconciliation currency, cardholder billing currency) currency, as shown
below:
• After Global Clearing Management System calculates the currency conversion assessment
in cardholder billing currency.
• After Global Clearing Management System completes the calculation of the total
cardholder billing amount (Inclusive of Issuer Currency Conversion Rate [ICCR] Amount or
Cross Border Fee Manager Amount if applicable).
• After Global Clearing Management System completes the calculation of acquirer and issuer
reconciliation amounts in acquirer/issuer reconciliation currency.
• After Global Clearing Management System completes the calculation of an interchange fee
in reconciliation currency.
Customer Requirements for Charging Back a Purchase with Cash Back Transaction
A Purchase with Cash Back transaction is a Debit Mastercard® transaction in which a purchase
was conducted, and cash was dispensed by the card acceptor at the point of interaction.
In the First Presentment/1240 messages, the total amount of the transaction (purchase plus
cash) must be submitted in DE 4 (Amount, Transaction). The cash back portion of the
transaction must be identified in DE 54 (Amounts, Additional), subfield 5 (Additional Amount,
Amount) in the same currency as the transaction amount contained in DE 4.
Customers should follow the chargeback procedures for Purchase with Cash Back transactions
described in, Processing Chargeback Messages. To chargeback all or part of the purchase
amount but not the cash back amount of a Purchase with Cash Back transaction, the
customer must subtract the cash back portion from the cardholder billing amount. If the
currency of the cash back portion differs from the currency of the cardholder billing amount,
the customer must perform the following calculation:
• Remove any assessments or fees added to the cardholder billing amount.
• Use the process described in the Currency Conversion Calculations section to convert the
cash back portion in DE 54 to the cardholder billing currency, applying the same exchange
rates used by Global Clearing Management System.
• Subtract the converted DE 54 amount from the DE 4 amount of the First Presentment/1240
message to obtain the purchase amount.
• The revised DE 4 will now contain the purchase amount only.
When charging back all or a part of the purchase portion but not the cash back portion of a
Purchase with Cash Back transaction, the customer must submit a First Chargeback/1442
message containing DE 24 (Function Code), value 453.
The chargeback amount submitted in DE 4 should not exceed the transaction amount
previously provided to the issuer in DE 4 of the First Presentment/1240 message.
For partial chargebacks, the chargeback amount submitted in DE 4 of the chargeback
message should be less than the transaction amount previously provided to the issuer in DE 4
of the first presentment. If an issuer submits multiple partial chargebacks for one first
presentment, the total of the partial chargebacks must not exceed the transaction amount
previously provided to the issuer in DE 4 of the first
Currency Conversion for Customers Outside the U.S. Region Processing a Chargeback
Message
An issuer not in the U.S. region processing a chargeback message will determine the currency
of the chargeback amount as follows.
For intra-European and inter-European transactions only, issuers may process a chargeback for
the same or lesser amount of the original presentment received from the acquirer either:
NOTE: Customers must use Mastercard published rates when pre-converting chargeback
amounts.
Chargeback
Submitted for Global
Clearing Management
System Processing FX Rate File Received Currency Update/1644 Messages Received in
Day Calendar Day Clearing Transmission with Processing Day
Monday Saturday Saturday
Tuesday Monday Monday
Wednesday Tuesday Tuesday
Thursday Wednesday Wednesday
Friday Thursday Thursday
Saturday Friday Friday
multiplies the resulting U.S. dollar amount by the mid rate associated with the intracurrency
reconciliation currency.
NOTE: The chargeback amount presented by the issuer to Mastercard in U.S. dollars should
include amounts resulting from a Currency Conversion Assessment, if applicable.
An arbitration chargeback may not be for an amount in excess of the acquirer’s second
presentment, but it may be for a lesser amount. The issuer notifies the acquirer that the
arbitration chargeback is for less than the full amount of the second presentment by providing
value 454 in DE 24 (Function Code) of the Arbitration Chargeback/1442 message.
If the acquirer has initiated the second presentment for an amount less than the original
chargeback amount, and DE 24 contains value 282 in the Second Presentment/1240 message,
then the issuer should identify the subsequent Arbitration Chargeback/1442 message as
partial by providing value 454 in DE 24, if applicable.
Acquirers submitting first presentment reversal messages are required to provide the original
Global Clearing Management System processing date in:
• PDS 0025 (Message Reversal Indicator), subfield 2 (Central Site Processing Date of Original
Message) (if reversing an individual message), or
• PDS 0026 (File Reversal Indicator), subfield 2 (Central Site Processing Date of Original File)
(if reversing an entire file)
If this original Global Clearing Management System processing date is within 60 days of the
current Global Clearing Management System processing date, Global Clearing Management
System will use the historical currency conversion rates from that date when calculating the
settlement value of the reversal.
If the original Global Clearing Management System processing date is more than 60 days from
the current Global Clearing Management System processing date, Global Clearing
Management System will use the currency conversion rates from the 60th day, the oldest
currency conversion rates in the historical rate file, when calculating the settlement value of
the reversal.
For chargeback and fee collection reversals, Global Clearing Management System uses the
current processing day’s currency conversion rates when calculating the settlement value of
the reversal.
NOTE: Global Clearing Management System sends the Currency Update/1644-640 messages
once per processor endpoint to the lowest (first) occurring customer ID in the logical file.
Global Clearing Management System does not provide a set of these messages for each
customer ID associated with the same processor. Only one set will be provided in a delivery
file. For example, if the customer elects to have clearing cycles 3 and 4 delivered as one file
after the fourth clearing, only one set of rate messages will be sent, not one each from 3 and
4.
The following are delivery options for the Currency Update/1644-640 messages:
• Do not deliver Currency Update/1644-640 messages.
• Deliver mid rate Currency Update/1644-640 messages.
• Deliver buy and sell rate Currency Update/1644-640 messages only.
• Deliver buy, sell, and mid rate Currency Update/1644-640 messages.
The customer or processor will receive the Currency Update/1644-640 messages in the
delivery cycles for which the customer or processor has elected to receive the rates. The
Clearing system will not generate Currency Update/1644-640 messages for customers when
there is no financial activity for that customer for a processing day.
NOTE: Calendar days and times are expressed in Central Standard Time in the table above.
Customers interested in receiving the currency conversion rate file should contact the Global
Customer Service team for additional information.
The Currency Conversion Rate File Detail Record provides the Rate Class in field 5. The values
for Rate Class are defined in the following table.
F = Master-Issued Cross Rate Buy, mid, and sell rates against The cross rates will reside in all
non-U.S. dollar currencies three rate type fields.
• Field 7 will contain the BUY
Currency Conversion Rate.
• Field 8 will contain the MID
Currency Conversion Rate.
• Field 9 will contain the SELL
Currency Conversion Rate.
NOTE: The Acquirer Currency Conversion Rate File is applicable only to determine the acquirer
reconciliation amount from the transaction currency. This file does not replace the existing
T057 Currency Conversion Rate File. Customers will continue to receive T057 rate files the
same as before.
The Originating Institution Payment Transaction Currency Conversion Rate File gives customers
the ability to determine the funding amount needed to reconcile with Mastercard specifically
for cross-border payment transactions. To assist customers in reconciling their payment
transactions (DE 3, Processing Code, subfield 1, Cardholder Transaction Type Code, value 28),
this rate file contains all possible currency conversion rates from the transaction currency to
the Originating Institution’s reconciliation currency code for regional First Presentment
payment transactions.
Customers may use the following methods to receive this new file:
• Mastercard Interface Processor (MIP) (production bulk files TS40, and test bulk files TS42)
• CONNECT:Direct
• Mastercard File Express
NOTE: The Originating Institution Payment Transaction Currency Conversion Rate File is
applicable only for determining the Originating Institution’s reconciliation amount to support
cross-border payment transactions. This file will not replace the existing T057 Currency
Conversion Rate File. Customers will continue to receive T057 rate files.
Receiving institutions that reconcile must continue reconciling using currency conversion rate
information provided in the First Presentment message and must not use the Originating
Institution Payment Transaction Currency Conversion Rate File.
Refer to the Acquirer Clearing Detail Reporting chapter for the layout of a Clearing Detail File.
ICCR Enrollment
All issuers in the Europe region that choose to enroll in the ICCR service must submit the
correct enrollment form.
The ICCR Service Enrollment Form, available on Mastercard Connect™, must be completed and
submitted before issuers can participate in the ICCR service.
Forms should be submitted to the issuer’s local customer delivery manager.
ICCR Reports
Issuers can choose to receive daily audit report files that align with each clearing cycle from
Global Clearing Management System.
This audit report will be available for the clearing transactions for which the ICCR calculation
was performed.
Bulk File TN70 On Request Report Data File Transfer Raw Format
Header Record
Detail Record
Trailer Record
1st Presentment Field 1st Chargeback (Full and Partial) Position Length Forma
Description Field Description t
MTI MTI 1 4 an
DW_PROCESS_DATE DW_PROCESS_DATE 8 8 an
DE2_CARD_NBR DE2_CARD_NBR 16 19 an
DE3_CARDHOLDER_TXN_TYPE DE3_CARDHOLDER_TXN_TYPE 35 2 an
DE93_ISSUER_ID DE94_SEND_ICA 37 11 an
PDS25_REVERSAL_IND PDS25_REVERSAL_IND 48 1 an
FILLER_REV_IND_MDS FILLER_REV_IND_MDS 49 3 an
DE12_TXN_DATE DE12_TXN_DATE 52 6 an
1st Presentment Field 1st Chargeback (Full and Partial) Position Length Forma
Description Field Description t
DE12_TXN_TIME 58 4 an
DE43_MERCH_COUNTRY_CD DE43_MERCH_COUNTRY_CD 62 3 an
DE63_BANKNET_REF_NBR DE63_BANKNET_REF_NBR 65 9 an
DE4_TXN_AMT DE4_TXN_AMT 74 12 n
DE49_TXN_CURR_CD DE49_TXN_CURR_CD 86 3 an
PDS148_TXN_CURR_EXP DE49_TXN_CURR_EXP 89 1 an
DE5_SETTLEMENT_AMT DE5_SETTLEMENT_AMT 90 12 n
DE6_CARDHOLDER_BILLING_AMT 106 12 n
DE51_CH_BILLING_CURR_CD 118 3 an
PDS148_ISSUER_CURR_EXP 121 1 an
Chapter 15 Reconciliation
This section describes the Global Clearing Management System messages and reports and how
they can be used in the reconciliation process.
Available for:
Clearing financial Settlement financial
transactions transactions
Reconciliation Messages Yes Yes
For more information about the Reconciliation Utility, refer to the Clearing Optimizer—
Mainframe manual.
If the files that Mastercard receives from the customer contain financial activity, Global
Clearing Management System may create clearing acknowledgement messages, settlement
acknowledgement messages, or both for each customer’s logical files. If no financial activity is
received, no settlement acknowledgement messages are created.
Notification Messages
Mastercard generates notification messages only when there is notification data to transmit.
6 C = Conditional—The data element is present in the message if the conditions described in the
accompanying text are applicable. M = Mandatory—The data element is always present in the message.
Available for:
1644-685 1644-688
Fin Pos Smt Pos
Reconciliation Provides Totals of Additional Information Dtl Dtl
Message Reconciliation about this Reconciliation
Category Amounts by: Category Ack Not Ack/Not
1 PDS 0300 PDS 0105 (Sending The file originator must create a R R D
(Reconciled, File File ID) unique File ID for each File
ID) Header/1644-697 message in
and across transmissions. The
file originator accomplishes this
by using unique values in the
File ID in each File Header/
1644-697 message and
corresponding File Trailer/
1644-695 message. This value
appears in PDS 0300 of the
reconciliation message.
The value provided in the
customer acknowledgement
messages identifies the File ID in
PDS 0105 submitted by the
customer.
The value provided in the
customer notification messages
identifies the clearing cycle and
the delivery cycle within the File
ID in PDS 0105 sent to the
customer.
These values can be used for
reconciliation to the Settlement
Advisement totals.
7 D = Default—If the customer elects to receive reconciliation messages, this category will be provided
automatically. O = Optional—The category is not required but may be included at the customer’s option.
R = Recommended—Unless the customer specifies otherwise, this category will be provided.
8 Customers sending a full file reversal using the same file ID, within the same clearing, may receive reconciliation
messages with amount totals that net to zero as a result of the original file and the reversal file processing in the
same clearing.
Available for:
1644-685 1644-688
Fin Pos Smt Pos
Reconciliation Provides Totals of Additional Information Dtl Dtl
Message Reconciliation about this Reconciliation
Category Amounts by: Category Ack Not Ack/Not
2 PDS 0165 • Transactions Each reconciliation message R R N/A
(Settlement cleared and contains totals only for a single
Indicator) settled by settlement indicator, not a
Mastercard combined total for transactions
• Bilateral settled by Mastercard, Bilateral
transactions transactions, and Global
• Global Collection Only transactions.
Collection Only Global Clearing Management
transactions System reports Bilateral and
Global Collection Only
transactions only in transaction
currency because they are not
settled through Mastercard.
Global Clearing Management
System reports only transactions
settled through Mastercard in
reconciliation currency, and
additionally may report them in
transaction currency or
transaction counts depending
on the reconciliation message
type.
7 D = Default—If the customer elects to receive reconciliation messages, this category will be provided
automatically. O = Optional—The category is not required but may be included at the customer’s option.
R = Recommended—Unless the customer specifies otherwise, this category will be provided.
Available for:
1644-685 1644-688
Fin Pos Smt Pos
Reconciliation Provides Totals of Additional Information Dtl Dtl
Message Reconciliation about this Reconciliation
Category Amounts by: Category Ack Not Ack/Not
4 PDS 0374 Processing Code Processing Code describes the R R N/A
(Reconciled effect of a transaction on a
Processing customer account and the type
Code) of account affected.
Customers that receive this
reconciliation category will
receive amount totals for all
processing codes for which
there is activity. Customers
cannot specify amount totals for
only certain processing codes.
Currently supported processing
codes are:
00 = Purchase (goods
and services)
transaction
01 = ATM transaction
12 = Cash disbursement
transaction
17 = Convenience check
(Global Collection
Only specific)
18 = Unique transaction
19 = Fee collection
(credit originator)
20 = Credit transaction
28 = Payment
transaction
7 D = Default—If the customer elects to receive reconciliation messages, this category will be provided
automatically. O = Optional—The category is not required but may be included at the customer’s option.
R = Recommended—Unless the customer specifies otherwise, this category will be provided.
Available for:
1644-685 1644-688
Fin Pos Smt Pos
Reconciliation Provides Totals of Additional Information Dtl Dtl
Message Reconciliation about this Reconciliation
Category Amounts by: Category Ack Not Ack/Not
29 = Fee collection
(debit originator)
30 = Balance Inquiry
50 = Payment/balance
transfer (Global
Collection Only
specific)
91 = PIN Unblock4
92 = PIN Change4
7 D = Default—If the customer elects to receive reconciliation messages, this category will be provided
automatically. O = Optional—The category is not required but may be included at the customer’s option.
R = Recommended—Unless the customer specifies otherwise, this category will be provided.
9 Although these transactions are traditionally considered to be non-financial with respect to the processing code,
they are classified as financial transactions when they are originated containing an Access Fee collected by the ATM
provider.
Available for:
1644-685 1644-688
Fin Pos Smt Pos
Reconciliation Provides Totals of Additional Information Dtl Dtl
Message Reconciliation about this Reconciliation
Category Amounts by: Category Ack Not Ack/Not
When this category is selected,
the issuer will receive messages
for each account range
established for its member ID
that had activity in the
applicable file, clearing cycle, or
both.
Additional information on this
reconciliation category is located
in the following section titled
Account Range Reconciliation
Category.
7 D = Default—If the customer elects to receive reconciliation messages, this category will be provided
automatically. O = Optional—The category is not required but may be included at the customer’s option.
R = Recommended—Unless the customer specifies otherwise, this category will be provided.
Available for:
1644-685 1644-688
Fin Pos Smt Pos
Reconciliation Provides Totals of Additional Information Dtl Dtl
Message Reconciliation about this Reconciliation
Category Amounts by: Category Ack Not Ack/Not
8 PDS 0358 All of the Customers that receive this O O N/A
(Reconciled following: reconciliation category will
Business receive amount totals for all
• Card Program
Activity) business activity categories for
Identifier
which there is activity.
• Business service Customers cannot specify to
level receive amount totals for only
• Business service certain Business Activity
ID categories.
• Interchange
rate designator The Global Clearing
Management System takes this
• Business Date
data from the Business Activity
• Business Cycle element of the original
• Card Acceptor transaction.
Classification
Override For customers processing
Indicator transactions such as product
• Product Class class overrides or special
Override conditions, if Business Activity is
Indicator one of the reconciliation
message categories being
• Corporate
received, amount totals are
Incentive Rates
based on the product class and
Apply Indicator
special conditions being
• Special received.
Conditions
Indicator
• Mastercard
Assigned ID
Override
Indicator
7 D = Default—If the customer elects to receive reconciliation messages, this category will be provided
automatically. O = Optional—The category is not required but may be included at the customer’s option.
R = Recommended—Unless the customer specifies otherwise, this category will be provided.
Available for:
1644-685 1644-688
Fin Pos Smt Pos
Reconciliation Provides Totals of Additional Information Dtl Dtl
Message Reconciliation about this Reconciliation
Category Amounts by: Category Ack Not Ack/Not
9 PDS 0359 • Settlement Customers that elect to receive N/A N/A D
(Reconciled, service level the settlement reconciliation
Settlement • Settlement messages will always receive
Activity) Service ID Settlement Position Detail/
• Transfer agent 1644-688 messages grouped by
• Transfer agent this category. Customers will
account receive settlement position
detail totals based on the
• Foreign
information that Global
exchange rate
Clearing Management System
class
populates in PDS 0159
• Reconciliation (Settlement Activity) of each
date and cycle transaction settled by
• Settlement date Mastercard.
and cycle
7 D = Default—If the customer elects to receive reconciliation messages, this category will be provided
automatically. O = Optional—The category is not required but may be included at the customer’s option.
R = Recommended—Unless the customer specifies otherwise, this category will be provided.
Available for:
1644-685 1644-688
Fin Pos Smt Pos
Reconciliation Provides Totals of Additional Information Dtl Dtl
Message Reconciliation about this Reconciliation
Category Amounts by: Category Ack Not Ack/Not
11 PDS 0375 Customers that Customers can populate PDS O N/A N/A
(Member select this as an 0375 in their customer
Reconciliation acknowledgement outgoing messages with any
Indicator 1) reconciliation proprietary value up to 50
option, and positions in length. When using
populate PDS 0375 this option, all financial records
in outgoing that do not contain PDS 0375
messages, will upon submission, will be
receive totals based accumulated and returned in
on the contents of acknowledgement reconciliation
PDS 0375 in messages in which PDS 0375
Acknowledgement contains the value undefined.
Financial Position
Business service arrangements
Detail/1644
that qualify for the Extended
messages.
Decimal Precision service will
have PDS 0375 populated with
the value undefined. Additional
information on this
reconciliation category is located
in the following section titled
Member Reconciliation Indicator
1.
12 PDS 0367 Card Program Customers that select this as a N/A N/A O
(Reconciled Identifier settlement reconciliation option
Card Program will receive totals based on the
Identifier) contents of PDS 0367 in
Acknowledgement Settlement
Position/1644 message. Global
Clearing Management System
will populate PDS 0367 based
on PDS 0158 (Business Activity),
subfield 1 (Card Program
Identifier).
7 D = Default—If the customer elects to receive reconciliation messages, this category will be provided
automatically. O = Optional—The category is not required but may be included at the customer’s option.
R = Recommended—Unless the customer specifies otherwise, this category will be provided.
Available for:
1644-685 1644-688
Fin Pos Smt Pos
Reconciliation Provides Totals of Additional Information Dtl Dtl
Message Reconciliation about this Reconciliation
Category Amounts by: Category Ack Not Ack/Not
13 PDS 0368 Totals are provided Customers that select this as a N/A N/A O
(Reconciled for each unique settlement reconciliation option
Transaction Transaction will receive totals based on the
Function Group Function group. contents of PDS 0368 in
Code) Acknowledgement Settlement
Position/1644 message.
14 PDS 0369 Acquirer’s BINs Customers may receive amount N/A N/A O
(Reconciled totals only for their own
Acquirer’s BIN) acquirer BINs as established by
Mastercard.
Customers that select this as a
settlement reconciliation
category will receive complete
reconciliation information for
their:
• Acquirer BINs
• Issuing activity (at the
customer ID level), and
• Fee collection activity (at the
customer ID level)
7 D = Default—If the customer elects to receive reconciliation messages, this category will be provided
automatically. O = Optional—The category is not required but may be included at the customer’s option.
R = Recommended—Unless the customer specifies otherwise, this category will be provided.
10 Note: For customers using this Financial Reconciliation option, the totals within a business service arrangement
subject to the Extended Decimal Precision Service will be accumulated and returned in acknowledgement
reconciliation messages where PDS 0375 contains the value “undefined.” Use of PDS 0375 in other business
services arrangements is not affected. Refer to the Extended Decimal Precision Service section for more
information.
Global Clearing Management System, Clearing Optimizer, IPM Utilities, and IPM MPE will
construct Customer ID and issuer account range as follows:
Customer ID 009999 or 00000009999
NOTE: The IPM MPE contains the 11-position representation. The IPM format supports a
variable representation from six positions to 11 positions.
The account ranges initially allow specification by 11-position ranges; however, this field
supports 19 positions for future use. The positions 12–19 in the Issuing Account Range
reconciliation category element are zero-filled for the beginning account range and nine-filled
for the ending account range.
Transaction Function Reconciliation Category
The transaction functions currently supported for reconciliation messages are listed in the
Currently Supported Transaction Functions table.
NOTE: If the customer chooses to receive reconciliation messages for transaction functions,
Mastercard will provide reconciliation detail only for the transaction functions for which
financial detail activity has occurred.
Message Type
Identifier Function Code Transaction Function
1240 200 First Presentment
Message Type
Identifier Function Code Transaction Function
1740 700 Fee Collection (customer-generated)
11 Customers selecting this option and submitting only 1644-603 (Retrieval Requests; non-financial messages) will
receive reconciliation messages with zero counts and amounts.
All other transactions The customer’s reconciliation currency and, if the customer selects
it, also in transaction currency.
When the reconciliation amounts are for bilateral totals, Global Collection Only totals, or both,
the message elements related to reconciliation currency amounts will be present in the
reconciliation message, but zero-filled. However, elements related to transaction counts
always contain totals for those settled by Mastercard, bilateral, and Global Collection Only
count when there is activity for those transaction types.
The IPM format does not require customers to provide expected reconciliation totals.
Customers optionally may provide hash totals for counts and amounts in PDS 0301 and PDS
0306 in their outbound File Trailer/1644-695 messages to activate file integrity checks.
However, the Global Clearing Management System does not use this data in PDS 0301 and
PDS 0306 as part of the reconciliation process.
Reconciliation messages accumulate only accepted financial activity. Financial activity currently
includes the transaction functions shown in the table Currently Supported Transaction
Functions.
The reconciliation messages do not provide amount or count totals for the following non-
financial message types:
• File Headers
• File Trailers
• Retrieval Requests
• Financial Detail Addenda
NOTE: For more information about transaction functions, as identified by MTI and Function
Code (DE 24), that qualify as financial activity, refer to the IPM Clearing Formats manual.
NOTE: The reconciliation messages report only accepted (not rejected) transaction message
totals.
The Global Clearing Management System automatically provides all message amount totals
for the Financial Position Detail/1644-685 in the customer’s reconciliation currency. If a
customer selects the Transaction Currency reconciliation category, the message will contain
amount totals for each unique pair of transaction currency and reconciliation currency for
which there was clearing activity.
Acknowledgement or
Notification Reconciliation Category
Notification Customer Activity
Acknowledgement File ID
Acknowledgement or
Notification Reconciliation Category
Acknowledgement Original/Reversal Transactions
For each combination of category, the Global Clearing Management System generates a
unique notification or acknowledgement Financial Position Detail/1644-685 message. For
example, one Financial Position Detail/1644-685 reconciliation message would contain totals
for the combination of one account range plus settlement indicator, another for a second
account range plus settlement indicator, and so forth.
Within the reconciliation categories for account range, customer activity, settlement indicator,
and processing code are multiple possible values. This can result in additional reconciliation
category combinations, generating additional Financial Position Detail/1644-685 messages.
This applies to all reconciliation categories.
For example, suppose that customer 001234 has selected the following reconciliation
categories for acknowledgement and notification messages and has clearing data as shown.
For each combination of categories, Global Clearing Management System generates a unique
notification or acknowledgement Financial Position Detail/1644-685 message.
In addition, within the reconciliation categories for business activity, settlement indicator,
original/reversal, and processing code are multiple possible values. These values can result in
additional reconciliation category combinations, generating additional Financial Position
Detail/1644-685 messages.
Using the selected reconciliation categories and specified values shown in the previous table,
Global Clearing Management System generates the following Financial Position Detail/
1644-685 messages.
In the above example, when the customer does not select the business activity reconciliation
category, Global Clearing Management System will combine the reconciliation totals for
consumer credit transactions and point-of-sale (POS) consumer debit transactions. Global
Clearing Management System also combines the interchange fee amount totals for those
transactions. Conversely, when the business activity reconciliation category is selected, Global
Clearing Management System specifies the interchange fee amount totals with the associated
credit or POS debit transaction amount totals in the reconciliation messages.
Customers may receive IPM acknowledgement and notification reconciliation messages for
POS debit and credit activity within the same logical file. Customers selecting the Early
Reconciliation file option also may see acknowledgement messages for both POS debit and
credit activity in the same Early Reconciliation file from Global Clearing Management System.
NOTE: The Settlement Position Detail/1644-688 Message will be delivered along with the
customers’ 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).
Reconciliation Category
Account Range:
54XXXXXXXXXXXXXXXXX – 54XXXXXXXXXXXXXXXXX
NOTE: Initially, account ranges will allow specification by 11-position ranges, however this
field supports 19 positions for future use. Refer to previous table titled Account Range
Building for additional information about building account ranges.
For each combination of category, the Global Clearing Management System generates a
unique notification or acknowledgement Settlement Position Detail/1644-688 message. For
example, one Settlement Position Detail/1644-688 reconciliation message would contain
totals for the combination of one account range, one file ID, and settlement activity, another
for a second account range, file ID, and settlement activity, and so forth.
Customers may receive IPM acknowledgement and notification settlement reconciliation
messages for point-of-sale (POS) debit and credit activity within the same logical file.
NOTE:
Customers that request these reports will receive them after each clearing cycle, regardless of
the customer’s file delivery options. For example, if data from clearing cycles 3 and 4 are
merged for data delivery, Global Clearing Management System will produce a report after
clearing cycle 3 and a separate report after clearing cycle 4.
4 Interchange Rate The ID assigned to the specific interchange program within the business
Designator agreement identified.
9 Reconciliation Reconciliation Currency alpha and numeric codes. These totals will
Currency/Code reflect only Mastercard settled transactions. Bilateral and Global
Collection Only totals are not provided in reconciliation currency.
11 Logical File ID Customer outbound logical file ID or customer inbound logical file ID.
The reconciliation reports are available for distribution to the customers upon request.
Customers can contact the Global Customer Service team or their Regional Office to request
these reports, detailed in the Global Clearing Management System Reconciliation Reports
table and in the report samples that follow.
If the customer chooses the option to receive reconciliation reports, detail IPM clearing reports
and a summary report will be generated for each of the six clearing cycles. These reports
supplement the IPM reconciliation messages and will facilitate reconciliation and balancing for
the customers.
A seventh clearing cycle exists exclusively for Mexico domestic switching transactions. For
more information on the seven clearing cycles, refer to the Daily Clearing Cycle Schedule
section.
Global Clearing Management System Reconciliation Reports
Customers may select report options using the Global Clearing Management System
Parameter Worksheet (Form 600).
This report is billable at USD 0.01 per line and is billed through the Mastercard Consolidated
Billing System (MCBS). The billing event number is as follows.
Customers may select report options using the Global Clearing Management System
Parameter Worksheet (Form 600).
NOTE: For each of the report samples that follows, field descriptions applicable to all of the
report pages follow the Summary page.
Clearing Cycle Acknowledgement Report (IP727010-AA), page 10: Global Collection Only
Transactions
Field Description
Run Date The date on which this report was produced.
Acceptance Brand (Card The code for the Mastercard or proprietary service marks under whose
Program Identifier) umbrella transactions are processed. As an example, MCC
(Mastercard Card) is a card program.
Business Service Level Identifies the interchange relationship for the business arrangement.
Examples are intracountry, intraregional, and interregional.
Business Service ID A unique code that identifies the specific interchange agreement
assigned to the transaction.
File ID The logical file ID to which the data in this report pertains.
Member ID The identifier that the association assigns to a customer (also referred
to as ICA number).
Trans. Func. (Transaction The IPM Message Type Identifier and Function Code combination that
Function) defines the transaction. Examples of transaction functions are first
presentment, first chargeback, and second presentment.
Proc. Code (Processing Code) Describes the effect of a transaction on a customer account and the
type of account affected. Examples are purchase, credit, and ATM
cash withdrawal. All transactions are defined as either an original or a
reversal.
IRD The interchange rate desigator defines the interchange program for
which the transactions were presented.
Recon. Amount The total net amount (with fees applied) of the transactions in
(Reconciliation Amount) reconciliation currency for the applicable processing code.
NOTE: Global Collection Only and Bilateral transactions are not
settled by Mastercard; therefore, the field contains a zero.
Recon. Currency Code The numeric and alpha ISO currency code associated with the
reconciliation currency (Always 840-USD for Global Collection Only
and Bilateral).
Field Description
Trans. Fee (Transaction Fee) The total of the transaction fees applicable to the transactions for the
processing code.
NOTE: Global Collection Only and Bilateral transactions are not
settled by Mastercard; therefore, the field contains a zero.
Fee Curr. Code (Fee Currency The numeric and alpha ISO currency code associated with the fee
Code) currency (Always 840-USD for Global Collection Only and Bilateral).
Total The total count and net amount (with fees applied) of the
transactions and reconciliation currency for the applicable transaction
function.
NOTE: This report is not available for customers submitting only Global Collection Only
transaction data.
Field Description
Run Date The date on which this report was produced.
Acceptance Brand (Card The code for the Mastercard or proprietary service marks under whose
Program Identifier) umbrella transactions are processed. As an example, MCC
(Mastercard Card) is a card program.
Business Service Level Identifies the interchange relationship for the business arrangement.
Examples are intracountry, intraregional, and interregional.
Business Service ID A unique code that identifies the specific interchange agreement
assigned to the transaction.
File ID The logical file ID to which the data in this report pertains.
Member ID The identifier that the association assigns to a customer (also referred
to as ICA number).
Trans. Func. (Transaction The IPM Message Type Identifier and Function Code combination that
Function) defines the transaction. Examples of transaction functions are first
presentment, first chargeback, and second presentment.
Proc. Code (Processing Code) Describes the effect of a transaction on a customer account and the
type of account affected. Examples are purchase, payment credit, and
ATM cash withdrawal. All transactions are defined as either an
original or a reversal.
IRD The interchange rate desigator defines the interchange program for
which the transactions were presented.
Recon. Amount The total net amount (with fees applied) of the transactions in
(Reconciliation Amount) reconciliation currency for the applicable processing code.
NOTE: Mastercard does not settle Global Collection Only and
Bilateral transactions; therefore, the field contains a zero.
Field Description
Recon. Currency Code The numeric and alpha ISO currency code associated with the
(Reconciliation Currency Code) reconciliation currency (Always 840-USD for Global Collection Only
and Bilateral).
Trans. Fee (Transaction Fee) The total of the transaction fees applicable to the transactions for the
processing code.
NOTE: Bilateral transactions are not settled by Mastercard;
therefore, the field contains a zero.
Fee Curr. Code (Fee Currency The numeric and alpha ISO currency code associated with the fee
Code) currency (Always 840-USD for Bilateral).
Total The total count and net amount (with fees applied) of the
transactions in reconciliation currency for the applicable transaction
function.
NOTE: This report is not available for customers submitting only Global Collection Only
transaction data.
Field Description
Run Date The date on which this report was produced.
Acceptance Brand (Card The code for the Mastercard or proprietary service marks under whose
Program Identifier) umbrella transactions are processed. As an example, MCC
(Mastercard Card) is a card program.
Business Service Level Identifies the interchange relationship for the business arrangement.
Examples are intracountry, intraregional, and regional.
Business Service ID A unique code that identifies the specific interchange agreement
assigned to the transaction.
Member ID The identifier that the association assigns to a customer (also referred
to as ICA number).
Cycle Activity The clearing cycle in which the file was processed by Global Clearing
Management System.
File ID To Mastercard The logical file ID of the file sent by the customer to Mastercard to
which the net amounts apply.
File ID From Mastercard The logical file ID of the file sent by Mastercard to the customer to
which the net amounts apply.
Net Reconciliation Currency The total net amount (with fees applied) of the transactions in
Amount reconciliation currency for the applicable logical file ID.
Reconciliation Currency Code The numeric and alpha ISO currency code associated with the
reconciliation currency.
Clearing Day Total As Of The grand total net amount (with fees applied) for the specified
Clearing (001–006) clearing day as of clearing cycle NNN.
Global Clearing Management System report IP142110-AA (IPM Clearing Messages Created
On Behalf of a Customer) has two additional receipt options:
• Text file available in raw data, variable length version. The bulk types are TN70 (Production)
and TN72 (Test) for outbound file delivery.
• XML data file available in variable length version. The bulk types are TN66 (Production) and
TN68 (Test) for outbound file delivery.
The data files are created and distributed after each clearing cycle. The data files do not
include summary totals. If no data is available, the customer will receive a header and trailer
only, with record count 0.
When multiple customer IDs are packaged in a single file to the same endpoint, the data is
sequenced by customer ID. A header and trailer will be provided for each customer ID (as
shown for three customers in the following example).
Both of the data files contain the same fields that are currently on the IP142110-AA report. In
addition, the data files contain the following fields. (These fields will not be added to the
IP142110–AA print report.
Name Description
Central Site Processing Date of Contains the value in PDS 0025 (Message Reversal Indicator),
Original Message subfield 2 (Central Site Processing Date of Original Message). If PDS
0025, subfield 2 is present because the transaction is being reversed,
the original message date is displayed.
File ID For the IP142110–AA report and data files, the File ID is the
Mastercard Source File ID. The File ID is found in PDS 0105 (File ID).
Record
Type Field Name Field Format Field Value Justification
Header Record Type PIC X(1) H Left
Record
Type Field Name Field Format Field Value Justification
Data Record Type PIC X(1) D Left
Record
Type Field Name Field Format Field Value Justification
Trailer Record Type PIC X(01) T Left
Record
Type Field Name Field Format Field Value Justification
Header Record Type PIC X(01) H Left
Record
Type Field Name Field Format Field Value Justification
Data Record Type PIC X(01) D Left
Record
Type Field Name Field Format Field Value Justification
Trailer Record Type PIC X(01) T Left
Field Description
Run Date The date on which this report was produced.
Member ID The identifier that the association assigns to a customer (also referred
to as ICA number). DE 94 (Transaction Originator Institution ID Code).
Currency The numeric ISO currency code associated with the transaction
currency. DE 49 (Currency Code, Transaction).
Credit Debit Indicator Indicates the amount credit or debit for the customer.
Currency The numeric ISO currency code associated with the reconciliation
currency. DE 50 (Currency Code, Reconciliation).
Fee Collection Control PDS 0137 (Fee Collection Control Number)/PDS 0241 (MasterCom
Number/MasterCom Control Control Number).
Number
Card Program Identifier/PAN PDS 0158 (Business Activity), subfield 1 (Card Program Identifier)/DE 2
(Primary Account Number [PAN]).
Field Description
Transaction Amounts The net total amount of the transaction in transaction currency for the
applicable logical ID file.
Reconciliation Amounts The net total amount of the transaction in transaction currency for the
applicable logical ID file.
Currency Code The numeric ISO currency code associated with the reconciliation
currency. DE 50 (Currency Code, Reconciliation).
Implementation Services team or registering through the Global Clearing Management System
Parameter Worksheet (Form 600).
Clearing system report Miscellaneous Override Financial Adjustments report (IP148320-AA)
has two additional receipt options:
• Text file is available in raw data, variable length version. The bulk type is TN70 (Production).
• XML data file is available in variable length version. The bulk type is TN66 (Production).
The data files are created and distributed after each processing day. The data files do not
include summary totals. If no data is available, the customer receives a header and trailer only,
with record count 0.
When multiple customer IDs are packaged in a single file to the same endpoint, the data is
sequenced by customer ID. A header and trailer is provided for each customer ID (as shown
for three customers in the following example).
The XML file version of the report will contain the data shown in the following layout.
XML Data File Distribution
Record
Type Field Name Field Format Field Value Justification
Header Record Type PIC X(01) H Left
Record
Type Field Name Field Format Field Value Justification
Trailer Record Type PIC X(01) T Left
The Raw Data version of the report will contain the data shown in the following layout.
Raw Data File Distribution
Record
Type Field Name Field Format Field Value Justification
Header Record Type PIC X(01) H Left
Record
Type Field Name Field Format Field Value Justification
Detail Record Type PIC X(01) D Left
NOTE:
Customers that request an XML data file version of a report will receive the same data as
above but in XML format.
For customers that elect to receive the text file, when no data is present, the file will consist
of a header and trailer record with zero (0) for the record count.
• The customer may choose to receive the IPM reconciliation message totals at the account
range level. Global Clearing Management System reconciliation reports provide totals at
the customer level but not at the account range level. Choosing the message totals at the
account range level provides the customer with a more detailed breakdown by customer
activity than Global Clearing Management System reports will provide.
• Global Clearing Management System reports provide count totals for non-financial
transactions, in addition to financial transactions. The IPM reconciliation messages do not
provide non-financial transaction detail. Thus, customers may request the IPM clearing
reports to obtain non-financial transaction count information to supplement the financial
count and totals information in the IPM reconciliation messages.
• Global Clearing Management System reports provide amount totals in the customer’s
reconciliation currency. The IPM reconciliation messages provide amount totals in the
customer’s reconciliation currency and optionally in the transaction currency. Customers
receiving both the Global Clearing Management System reports and the IPM reconciliation
messages can thus receive their amount totals in these currencies: transaction,
reconciliation.
• The rejected transaction reports can provide customers with rejected transaction
information that accounts for the difference between the customer clearing data totals and
the accepted clearing data totals as reported by Mastercard. For example, suppose that
customer A submits financial transactions totaling USD 3,000.00. Customer A receives
acknowledgement reconciliation messages, which show processing of USD 2,500.00
financial activity. Customer A can refer not only to the rejected transaction reports but also
to the customer inbound error messages to verify the source of the USD 500.00 difference.
NOTE: All of the reports referenced in the list above are available per clearing cycle and are
not available within the IPM Early Reconciliation File. Reconciliation messages are delivered
according to the customer’s elected file delivery schedule.
NOTE: Customers and processors will need to accumulate reconciliation messages to derive a
grand total, by processor, for any of the reconciliation categories for the customers for which
they process.
For example, suppose that customer or processor 001111 processes for customer ID 002222,
customer ID 003333, and customer ID 004444 and that Mastercard has set up the customers’
selected categories for notification messages as follows:
• Customer ID 002222: Set up to receive reconciliation totals by processing code and
settlement indicator
• Customer ID 004444: Set up to receive reconciliation totals by processing code and
settlement indicator
Although it is unlikely that a customer or processor would establish such a diverse set of
categories for each customer ID, this example illustrates the process for accumulating any set
of reconciliation totals.
Processor
001111
Receives Settlement Originals/ Transaction
Member ID Record… Processing Code Indicator Reversals Function
002222 1 Purchase—USD 100.00 Settled by
Mastercard
To derive a total at the customer or processor level for any of the above reconciliation
categories, the customer or processor will need to accumulate and total each applicable
customer ID’s reconciliation category.
For example, to derive the notification totals by processing code of purchase for processor
001111, the processor must accumulate the notification totals by processing code for
customer ID 002222 and customer ID 004444.
NOTE: The Settlement Position Detail/1644-688 message will be 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).
NOTE: The Global Clearing Management System does not duplicate the messages provided in
the early reconciliation files when it creates the customer inbound clearing files at cycle cutoff
times. The customer will receive the messages only once.The Early Reconciliation file is
transmitted using bulk type T113. This differs from the normal clearing cycle cutoff file bulk
types, to clearly distinguish the Early Reconciliation file from all other clearing files.
NOTE: For more information about sending files for processing by the Global Clearing
Management System, refer to the section titled, Early Reconciliation Message File in the
Clearing Processing Details section.
Customers may select the Early Reconciliation file option using the Global Clearing
Management System Parameter Worksheet (Form 600). Refer to the Global Clearing
Management System Parameter Worksheet (Form 600).
NOTE: The Cross-Border Flex Method does not apply to intra-European transactions where the
country codes of the merchant and the account range are both in the extended Eurozone
(Euro countries plus Sweden) and the transaction currency is euros (EUR).
By participating in either of the methods (Currency Conversion Method and Cross-Border Flex
Method), issuers have the option to use a combination of the following parameters at an
account range level, which can be applied to the total cardholder billing amount:
• Account range for Mastercard, Debit Mastercard, Maestro, and Cirrus acceptance brands
• Region differentiation
• Processing groups (for example, point-of-sale [POS], ATM, card-present, card-not-present,
and so on)
• Transaction currency
• Region identifier
For both of these methods, issuers can apply different fees for intraregional and interregional
identifiers.
Cross-Border Fee Manager Self-Service Application
Issuers that participate in the service have the capability to change their Cross-Border Fee
Manager markup rates at the account range level within an existing service setup, using a self-
service application on Mastercard Connect™. To expedite rate changes, issuers can view their
current rates and change markup rates up to two decimal positions and set zero rates for
account ranges that are already enrolled in the Cross-Border Fee Manager Service.
NOTE: Rate changes become effective within 48 hours after the rate changes are made in the
self-service application.
Conversion Method, Cross-Border Flex Method, or both as part of the Cross-Border Fee
Manager service.
This form should be submitted to the issuer’s local customer delivery manager.
NOTE: Issuers may only participate in the Currency Conversion Method and the Cross-Border
Flex Method where permitted by local regulations.
Bulk File TN70 On Request Report Data File Transfer Raw Format
Header Record
Detail Record
Mastercard does not calculate a rate or amount if DE 22 (Point of Service [POS] Entry Mode]),
subfield 6 (Card Present Data) contains value 9 (Unknown; data unavailable), but the
transaction is included in report IP830020. This assists issuers with identification of why the
markup was not applied.
Trailer Record
NOTE: Mastercard does not provide or validate history for fee collection messages, although
the sender may optionally provide it.
Fee Collection Messages for Purposes Other Than Retrieval Fee Billing
Customers must settle all miscellaneous fees and charges by use of the IPM Fee Collection/
1740 message. The fee collection message is used for a number of diverse applications, and it
contains the information required for customers to process the miscellaneous fees and
charges identified in DE 25 (Message Reason Code).
Within the IPM Fee Collection/1740 message, DE 25 indicates the reason for, or type of, fee
collection. DE 3 (Processing Code), subfield 1 (Cardholder Transaction Type) indicates the
direction of funds movement, such as debit to message originator or credit to message
originator.
NOTE: Transaction amount maximum can be set in currencies other than U.S. dollar. All Fee
Collection/1740 message with function code 700 transaction amount maximum settings can
be viewed in the IPM MPE Table IP0097T1: Message Reason Code Restrictions for Card
Program Identifier and Business Service Arrangement.
1. The receiving customer may return a fee collection within 45 calendar days after receipt of
the message for any of the following reasons. This is handled by sending a Fee Collection/
1740 with the same data originally received, except that DE 24 must contain a value of
780 to indicate a return.
– Supporting documentation not received. The receiving customer must wait 21 calendar
days from the date the message is received before returning for this reason.
– Missorted to wrong member.
– The message text was not provided or was incomplete.
– Fee charged exceeds amount allowed.
– Fee inaccurate because of entry error.
– Charged twice for same fee.
– Past applicable time frame.
– An erroneous or inappropriate progressive handling fee was received.
– Unauthorized fee/charge—receiving member did not approve or agree to accept fee/
charge. Applicable only to reason codes for good-faith acceptance (DE 25 = 7606) and
for collection letters (DE 25=7607).
2. If a fee collection is returned for any of the previously-mentioned reasons, the receiving
customer may resubmit it within 45 calendar days of receipt of the message but only if the
reason for return has been corrected (For example, the receiving customer has supplied
the missing documentation or the correct amount). To resubmit the fee collection, the
NOTE: For case filings initiated for a violation of this subsection, the good-faith
correspondence is not required. For more information about filing procedure, refer the
Chargeback Guide.
The sending customer must reverse any Fee Collection/1740 message that is duplicated in
error. The customer handles this by processing a duplicate of the message originally processed,
except that the customer enters the letter R in PDS 0025 (Message Reversal Indicator), subfield
1 (Message Reversal Indicator). This denotes a reversal transaction.
NOTE: For more information about reversals, refer to the Reversals chapter of the Global
Clearing Management System Reference Manual.
NOTE: When Global Clearing Management System converts the transaction amount in
transaction currency to the (euro) issuer/acquirer payment currency, Global Clearing
Management System first converts the amount to the base currency (USD), and carries six
positions to the right of the decimal (no rounding). Then Global Clearing Management
System converts the USD base amount to the euro, and rounds to the euro currency
exponent.
Global Clearing Management System only rounds amounts to the number of positions to the
right of the decimal point specified by the currency exponent, once they are calculated in the
final (issuer/acquirer payment currency, cardholder billing currency) currency, as shown in the
following table.
IF Global Clearing THEN Global Clearing Management System rounding to the nearest
Management System currency exponent...
has…
Calculated interchange Occurs after Global Clearing Management System has completed
fees in payment calculation of the interchange fee in acquirer/issuer currency.
currencies
Calculated an Acquirer/ Occurs after Global Clearing Management System has completed
Issuer payment calculation of the acquirer/issuer payment amount.
NOTE: Transaction amount maximum can be set in currencies other than U.S. dollar. All Fee
Collection/1740 message transaction amount maximum settings can be viewed in the IPM
MPE Table IP0097T1: Message Reason Code Restrictions for Card Program Identifier and
Business Service Arrangement. For example, the maximum amount for MRC 7601 for Europe
intraregional business services for MCC and DMC acceptance brand is EUR 115.
DE 25 7600
Lost/stolen telex/phone fee; for collection of lost stolen report fee and phone or telex costs
incurred for taking a lost or stolen card report.
Maximum USD 65
Amount
33 1 Space
34–100 67 When the cardholder number is absent, the cardholder name and
address should be placed in this field.
DE 25 7601
Recovered card award fee; for collection of reward for a card acceptor or financial
institution employee when a card has been recovered.
1 = Mastercard® Card
2 1 Space
3–6 4 Valid MCC; refer to the Quick Reference Booklet for a current listing.
Valid MCC; refer to the Quick Reference Booklet for a current listing.
7 1 Space
2 = authorization response
4 = code
5 = authenticator
6 = non-hologram
0 = other
9 1 Space
32 1 Space
46 1 Space
47–49 3 Alphabetic; U.S. state or country code if outside the U.S. region; left-
justified with trailing spaces
50 1 Space
DE 25 7602
Emergency cash disbursement fee; for collection of fees associated with the handling of
emergency cash disbursements to cardholders.
Reason
Code Fee Description
2–100 99 Spaces
DE 25 7603
Compliance ruling settlement; for collection of a compliance ruling settlement amount.
12 1 Space
DE 25 7604
Emergency card replacement fee; for collection of fees associated with the Emergency
Card Replacement Service (ECR Service).
1 1 Reason Code:
L = survey statistics
2–100 99 Spaces
DE 25 7605
Warning bulletin handling fee—issuer originated; for settlement of warning bulletin
handling fees in accordance with Mastercard operating rules.
Maximum USD 25
Amount
1 1 Reason Code:
C = combination of A and B
2 1 Space
26 1 Space
37–100 64 Spaces
DE 25 7606
Good-faith acceptance settlement; for settlement of the amount of a good-faith
acceptance.
1–31 31 Reference number and the name of the person who gave acceptance
32 1 Space
DE 73 Good-faith date
DE 25 7607
Collection letter handling fee; for settlement of the amount of a collection letter
acceptance.
12 1 Space
DE 25 7608
Telex authorization fee; for collection of fees associated with an international telex
authorization.
Maximum USD 20
Amount
34–100 67 Spaces
DE 25 7610
Investigation fee; for fee collection when an investigation report has been completed by
an investigating member on behalf of the requesting member.
20–100 81 Spaces
DE 25 7611
Retrieval fee reversal; issuer-originated; acquirer may return. For acquirer use when
returning an invalid or incorrect retrieval fee reversal; applicable only if the previous cycle
message reason code was 7611, or
For issuer use when returning an invalid or incorrect non-MasterCom fulfillment fee
settlement; applicable only if the previous cycle message reason code was 7614.
Maximum USD 15
Amount
1 1 Reason Code:
A = nonreceipt of document
B = illegible document
2 1 Space
3–25 23 ARD
26 1 Space
37–100 64 Spaces
DE 73 PDS 0105 (File ID), subfield 2 (File Reference Date) of the Central Site processed Retrieval
Fee Billing/1740-700 message.
DE 25 7612
Retrieval handling fee; issuer-originated; acquirer may return. For acquirer use when
returning an invalid or incorrect retrieval handling fee; applicable only if the previous cycle
message reason code was 7612, or
For issuer use when returning an invalid or incorrect non-MasterCom fulfillment fee
settlement; applicable only if the previous cycle message reason code was 7614, or for
issuer use to assess the acquirer for incorrect information verified by the retrieval request
document or a TID sent as chargeback documentation.
For issuer use to charge the acquirer for incorrect information verified by the retrieval
request document or a TID sent as chargeback documentation.
Maximum USD 25
Amount
1 1 Reason Code:
2 1 Space
3–25 23 ARD
26 1 Space
37 1 Space
60 1 Space
83–100 18 Spaces
37 1 Space
60 1 Space
83–100 18 Spaces
DE 73 PDS 0105 (File ID), subfield 2 (File Reference Date) of the Central Site processed Retrieval
Fee Billing/1740-700 or Second Presentment/1240-205 or 1240-282
DE 25 7616
Handling fee for second presentment of reason codes 12 and 35 for chip transactions
where transaction certificate and DE 55 (Integrated Circuit Card [ICC] System-Related
Data) are present in the clearing message. Acquirer-originated.
Maximum USD 25
Amount
1 1 Reason Code:
2 1 Space
3–25 23 ARD
26 1 Space
37–100 45 Spaces
DE 73 PDS 0105 (File ID), subfield 2 (File Reference Date) of the member-submitted Second
Presentment/1240-205 or 1240-282
DE 25 7617
Adjustment for promotional transactions.
Maximum None
Amount
39–100 62 Spaces
DE 73 PDS 0105 (File ID), subfield 2 (File Reference Date) of the File Header/1644
DE 25 7618
Reversal of previously reimbursed State Fuel Tax.
Maximum None
Amount
87–100 14 Spaces
DE 25 7619
Emergency card replacement center, cash advance lockbox fee.
Maximum USD 50
Amount
1 1 Reason
Code Fee Description
2–100 99 Spaces
DE 25 7621
ATM Balance Inquiry Fee—Reserved for intra-European and inter-European use.
Maximum USD 50
Amount
1-100 100
DE 25 7622
Handling fee for Authorization Related Chargebacks (4807 and 4808). This fee is sent by
the issuer after sending a First Chargeback/1442–450 or 1442–453 for one of the
chargeback reasons identified above.
Maximum USD 50
Amount
3 1 Constant Space
5 1 Constant Space
7 1 Constant Space
18 1 Constant Space
25 1 Constant Space
29 1 Constant Space
30–49 20 PDS 0137 (Fee Collection Control Number) assigned by the issuer.
Right justified, leading zeros.
DE 73 Date of the chargeback cycle with which the handling fee is associated
DE 25 7623
Handling fee for Authorization Related Chargebacks (4807 and 4808). This fee is sent by
the acquirer after sending a Second Presentment/1240-205 or 1240-282 for one of the
chargeback reasons identified above.
1–2 2 Values 07, 08, or 47 correspond to the IPM Message Reason Code (DE
25) 4807 and 4808 of the related First Chargeback/1442
3 1 Constant Space
5 1 Constant Space
7 1 Constant Space
29 1 Constant Space
30–49 20 PDS 0137 (Fee Collection Control Number) assigned by the issuer in
the (IPM Fee Collection/1740-700 message with a DE 25 (Message
Reason Code) of 7622, or spaces, if the issuer did not send a Fee
Collection/1740-700 message. Right justified, leading zeros.
50 1 Constant Space
57 1 Constant Space
DE 73 Date of the chargeback cycle with which the handling fee is associated
DE 25 7624
Handling fee for Authorization Related Chargebacks (4807 and 4808). This fee is sent by
the issuer after sending an Arbitration Chargeback/1442-451 or 1442-454 for one of the
chargeback reasons identified above.
3 1 Constant Space
5 1 Constant Space
7 1 Constant Space
18 1 Constant Space
25 1 Constant Space
29 1 Constant Space
30–49 20 Original PDS 0137 (Fee Collection Control Number) assigned by the
acquirer in the IPM Fee Collection/1740-700 message with a DE 25
(Message Reason Code) of 7623, or spaces, if the acquirer did not
send a Fee Collection/1740-700 message.
DE 73 Date of the chargeback cycle with which the handling fee is associated
DE 25 7625
PIN Management Service at ATM. (Intra-European and inter-European use only).
Maximum USD 5
Amount
1–100 100 PIN CHANGE xxxx xxxx xxxx xxxx (where xxxx xxxx xxxx xxxx represents
the cardholder number) OR PIN TRY COUNTER RESET xxxx xxxx xxxx
xxxx (where xxxx xxxx xxxx xxxx represents the cardholder number)
DE 25 7626
Private Label Merchant Fee for Private Label fee collection messages. This fee collection
message reason code is available for business service arrangements level 1 (interregional),
level 2 (intraregional), level 3 (intercountry) and level 4 (intracountry) where Private Label
exists.
Maximum None
Amount
DE 25 7627
Fees related to the issuer’s failure to provide a Merchant Advice Code; for acquirer use
only.
3 1 Constant Space
5 1 Constant Space
7 1 Constant Space
18 1 Constant Space
25 1 Constant Space
29 1 Constant Space
30–49 20 PDS 0137 (Fee Collection Control Number) assigned by the issuer.
Right justified, leading zeros.
DE 73 Date of the chargeback cycle with which the handling fee is associated
DE 25 7628
Reclaim surcharge—Reserved for intra-European, inter-European, and European
transaction related services.
1-100 100
DE 25 7700
Intracurrency settlement agreement; for settlement of amounts in accordance with an
intracountry agreement between transaction originator and transaction destination
parties.
Maximum
Amount USD 40,000
1–100 100
DE 25 7704
Bank Card Interchange fee, reverse interchange for ATM transactions (Mexico Domestic).
Maximum None
Amount
DE 25 7705
Transactions below to threshold published (Mexico Domestic). Customer calculates VAT
(Value Added Tax).
Maximum None
Amount
DE 25 7706
Difference in interchange amount between member calculated and Mastercard calculated
(Mexico Domestic). Member calculates VAT (Value Added Tax).
Maximum None
Amount
DE 25 7707
Interest for late settlements (Mexico Domestic). Customer calculates VAT (Value Added
Tax).
Maximum None
Amount
DE 25 7708
Non fullfiled documentation penalties (Mexico Domestic). Customer calculates VAT (Value
Added Tax).
Maximum None
Amount
DE 25 7709
Penalties on code 102 miscellaneous (Mexico Domestic). Customer calculates VAT (Value
Added Tax).
Maximum None
Amount
DE 25 7710
Miscellaneous (Mexico Domestic).
Maximum None
Amount
DE 25 7711
Pre-fund amount, offset for others (Mexico Domestic).
Maximum None
Amount
DE 25 7712
Bank Card Interchange fee, balance inquiry interchange. Customer calculates VAT (Value
Added Tax).
Maximum None
Amount
DE 25 7750–7799
Bilateral agreement settlement; for settlement of amounts in accordance with a bilateral
agreement between transaction originator and transaction destination parties.
1–100 100
DE 73 Charge date
DE 25 7800
MCBS customer settlement; for collection or payment of such things as customer
assessments, processed through the Mastercard Consolidated Billing System (MCBS).
Maximum None
Amount
5 1 Space
7 1 Space
15–16 2 Spaces
19 1 Space
21 1 Space
44–45 2 Spaces
49–50 2 Spaces
65–67 3 Spaces
86 1 Space
88 1 Space
92 1 Space
96 1 Space
NOTE: Transaction amount maximum can be set in currencies other than U.S. dollar. All Fee
Collection/1740 message transaction amount maximum settings can be viewed in the IPM
MPE Table IP0097T1: Message Reason Code Restrictions for Card Program Identifier and
Business Service Arrangement. For example, the maximum amount for MRC 7601 for Europe
intraregional business services for MCC and DMC acceptance brand is EUR 115.
DE 25 7621
ATM Balance Inquiry Fee—Reserved for intra-European use
DE 25 7625
PIN Management Service at ATM—Reserved for intra-European use
DE 25 7629
Interregional non-financial ATM interchange for collection of interchange due on a non-
financial ATM transaction (Single Message System-originated.
Maximum USD 5
Amount
45–64 20 DE 127 (Private Data) from the authorization message. This value
contains the first 20 positions of Acquirer Private Data. It is left
justified with trailing spaces.
DE 25 7702
Domestic ATM VAT Fees/Services—Used for the Mexico Domestic Fee Collection/1740
message on the VAT amount on ATM transactions. Mastercard calculates the VAT when
submitted with this message reason code.
DE 25 7800
MCBS customer settlement; for collection or payment of such things as customer
assessments, processed through the Mastercard Consolidated Billing System (MCBS).
Maximum None
Amount
5 1 Space
7 1 Space
15–16 2 Spaces
19 1 Space
21 1 Space
44–45 2 Spaces
49–50 2 Spaces
65–67 3 Spaces
86 1 Space
88 1 Space
92 1 Space
96 1 Space
DE 25 7802
Maximum None
Amount
DE 73 PDS 0105 (File ID), subfield 2 (File Reference Date) of the File Header/1644
34–100 67 Spaces
DE 25 7803
Interchange compliance adjustment reversal; for settlement of financial amounts related
to the reversal of a previous interchange compliance adjustment.
Maximum None
Amount
DE 73 PDS 0105 (File ID), subfield 2 (File Reference Date) of the File Header/1644
42–100 59 Spaces
DE 25 7804
ATM transaction settlement; for settlement of daily ATM transaction amounts.
Maximum None
Amount
1–7 7 “NET AMT” = transaction amount field equals the net dollar value of
all ATM withdrawals transacted by an issuer’s cardholders.
8–100 93 Spaces
5–100 96 Spaces
6–100 95 Spaces
5–100 96 Spaces
6-100 95 Spaces
6–100 95 Spaces
DE 25 7805
ATM intracountry switch fee settlement; for settlement of daily ATM transaction
intracountry switch fees.
Maximum None
Amount
6–100 95 Spaces
DE 25 7806
ATM Single Message Transaction Manager switch fee settlement; for settlement of MDS
Single Message Transaction Manager Switch Fees.
Maximum None
Amount
1–100 100
DE 25 7807
ATM intracountry first chargeback settlement; for settlement of daily ATM transaction
intracountry first chargeback amounts.
Maximum None
Amount
6–100 95 Spaces
DE 25 7808
Miscellaneous Override Financial Adjustment.
Maximum None
Amount
38–38 1 Blank (only when the fee collection is for the issuer)
39–76 78 Account Range (only when the fee collection is for the issuer)
DE 25 7811
Reimbursement of State Fuel Tax.
Maximum None
Amount
1–80 80 “TAX REIMBURSE DEBIT FROM JURISDICTION SSSS VIA OIL AAA TO
AGENCY NNN PERIOD YYMM”
81–100 20 Spaces
1–81 81 “TAX REIMBURSE CREDIT FROM JURISDICTION SSSS VIA OIL AAA TO
AGENCY NNN PERIOD YYMM”
82–100 19 Spaces
DE 25 7812
Collection or return of collateral for security arrangement.
Maximum None
Amount
50–100 51 Spaces
47–100 54 Spaces
DE 25 7813
IVA fees
Maximum None
Amount
DE 73 PDS 0105 (File ID), subfield 2 (File Reference Date) of the File Header/1644
16–100 85 Spaces
DE 25 7820
Disaster Relief Fund (credit to sender).
Maximum None
Amount
DE 73 PDS 0105 (File ID), subfield 2 (File Reference Date) of the File Header/1644
1–100 100
DE 25 7821
MCBS Credit Emergency.
Maximum None
Amount
1–100 100
DE 25 7822
Settlement Adjustment
Maximum None
Amount
22–100 79 Spaces
DE 25 7823
Single Message System Offline Debit Settlement (Mastercard Internal Use Only).
Maximum None
Amount
DE 25 7824
Collection of Reward Amount as agreed upon between the customers.
Maximum None
Amount
28–100 73 Spaces
DE 25 7827
EDP Adjustment Amount (Used only by the Mastercard Network for the EDP Service).
Chapter 20 Reversals
This section describes how to create reversals and how Global Clearing Management System will
process them.
When a Single Message System to Dual Message System (Authorization) transaction (that is,
bridged transaction) has been reversed due to an ATM Withdrawal failure, a reversal message
is generated by Mastercard for the original 1240/Presentment message. The Global Clearing
Management System would directly deduct the non-financial fee into the reversal message
and no longer generate a Fee Collection (Retrieval Fee Billing)/1740 message non-financial
fee.
Procedure
1. The customer realizes that it needs to reverse an individual message.
2. The customer extracts the message to be reversed. For example, if a customer wants to
reverse a message containing a specific cardholder account number, the customer can use
the IPM Message Selection Criteria utility to select and extract the message containing
that cardholder account number.
3. The customer adds PDS 0025 (Message Reversal Indicator) to the message, with the value
R in subfield 1 (Message Reversal Indicator) and the original Global Clearing Management
System processing date in subfield 2.
4. The customer adds the reversal message to one of its outgoing clearing files.
5. If the customer’s original message needs to be resent because it contained incorrect data,
the customer corrects the data in the original message and resubmits it.
Global Clearing Management System will recognize and process individual reversal
messages submitted in a file. There is no requirement to isolate reversal messages or to
send them in separate files.
Procedure
1. The customer realizes that it needs to reverse an entire file.
2. The customer sends a full file reversal using the same file ID or a new file ID. The customer
adds PDS 0026 (File Reversal Indicator) to the file header message with the value R in
subfield 1 (File Reversal Indicator) and the original Global Clearing Management System
processing date in subfield 2 (Central Site Processing Date of Original File).
Because PDS 0026 is present in the File Header message, Global Clearing Management
System recognizes the file as a full file reversal. Global Clearing Management System
inserts PDS 0025 (Message Reversal Indicator) into each individual message in the file and
processes and distributes each message as a single-item reversal.
3. If the customer’s original file needs to be resent because it contained incorrect data, the
customer corrects the data in the original file and resubmits it using a different file ID.
Example
For example, suppose that customer 001234 sends file ID 0020406150000000123400001
on 15 June 2004.
1. The customer realizes that the data is incorrect and that the customer needs to reverse
the file and resubmit the data.
2. Customer 001234 sends a full file reversal using the same file ID
0020406150000000123400001, on 16 June 2004 to reverse the incorrect data. The
customer adds PDS 0026 to the File Header message of this file before sending it. The
date provided in PDS 0026, subfield 2 must be the 15 June 2004 date. This is the
original file processing date. Global Clearing Management System processes each
individual message in the file as a reversal; however, if an individual message is already
a reversal transaction, it will be processed as an original transaction.
3. Customer 001234 then corrects the data in the original file and resubmits it using a
different file ID, such as 0020406150000000123400002.
If customer 001234 submits the corrected data using file ID
0020406150000000123400001 again, Global Clearing Management System will reject
this third file because it contains a duplicate file ID. Global Clearing Management System
allows one original file and one reversal file for each file ID.
Allowing customers to reverse files using the same file ID simplifies the creation of reversal
files. Customers only need to populate PDS 0026 in the File Header message with an R to
indicate that the entire file is being reversed.
NOTE: Customers will not receive an entire file that is a full file reversal file (that is, PDS
0026 will not be present in the customer inbound file header). In the receiving customer’s
clearing file, reversal messages will be mixed with non-reversal messages.
Procedure
1. Extract the messages to be reversed into a new file. For example, if a customer wants to
reverse all of the first chargebacks from a file, the customer can extract all first
chargebacks from the original file.
2. Create a file header message with a value of R in PDS 0026 (File Reversal Indicator).
3. Create a file trailer containing zeros in PDS 0301 (File Amount, Checksum) and PDS 0306
(File Message Counts).
4. Submit the file for processing.
Customers should not combine messages from more than one processing date to be
reversed. This is because the date in subfield 2 (Central Site Processing Date of Original
File) of PDS 0026 will allow specification of only one original processing date for the
currency conversion rate history. The Global Clearing Management System uses that date’s
currency conversion rate (if necessary) to apply to the reversal transactions.
NOTE: Customers submitting a full or partial reversal file (indicated by the presence of
PDS 0026 in the File Header) are not required to use a File ID that has already been
processed. For example, customers creating a partial reversal file may choose to assign a
new File ID instead of using the original File ID.
NOTE: If multiple partial reversals are required before clearing a transaction, each reversal
should always reference the original transaction data. For example, within DE 48
(Additional Data—Private Use), subelement 63 (Trace ID), DE 90 (Original Data Elements)
and DE 4 (Amount, Transaction) of the Reversal Request/0400 message, the amount value
should be the authorized amount from the original transaction to support issuer matching
(do not use the adjusted amount from DE 95 (Replacement Amounts) within a previous
reversal, nor the requested amount if a partial approval applies). If an incremental
authorization has been submitted, a reversal should reference original transaction data
and DE 4 should be the sum of the original authorized amount plus any incremental
amounts.
NOTE: For more information about the IPM Message Selection Criteria, refer to either the
Clearing Optimizer—Mainframe guide or the Clearing Optimizer—Workstation Plus guide.
Mastercard recommends that customers establish controls to prevent and detect these and
other errors to help prevent duplicate files and postings.
Collection-only Transactions
A collection-only transaction is a transaction that is reported to Mastercard by means of the
Global Clearing Management System, but which has not been cleared nor settled through the
Mastercard Network. A customer must identify each collection-only transaction by populating
PDS 0165 (Settlement Indicator), subfield 1 (Settlement Indicator), value C (Collection Only).
A customer may combine collection-only transactions with other transactions in the same file,
or provide collection-only transactions in a separate file.
Collection-only Transactions that are Not Permitted for Global Collection Only
These sections describe requirements for the reporting of collection-only transactions,
including such reporting performed pursuant to the GCO Data Collection Program.
The following types of transactions should not be submitted as collection-only:
• Retrieval Request/1644
• First Chargeback/1442
• Second Presentment/1240
• Arbitration Chargeback/1442
• Fee Collection (Retrieval Fee Billing)/1740
• Fee Collection (Other)/1740
• Fee Collection (Handling Fees)/1740
NOTE: For instructions for reversing a single message or an entire file (applicable to both
collection-only and non-collection-only activity), refer to Bilateral Settlement Activity.
Data Element
Data Element M— Guiding Data Element Name—Single
Data Element Name—IPM Mandatory / Comments or No.—Single Message
—IPM 1240 1240 O—Optional Maps to Value Message 0200 System 0200
- Message Type M 1240
Identifier
- Bit Map, M
Primary
1 Bit Map, M
Secondary
2 PAN M 2 PAN
3 Processing M 3 Processing
Code Code
4 Amount, M 4 Amount,
Transaction Transaction
5 Amount, O 5 Amount,
Reconciliation Settlement
6 Amount, O 6 Amount,
Cardholder Cardholder
Billing Billing
12 Date and Time, M 13 Date, Local
Local Transaction
Transaction
14 Date, O 14 Date,
Expiration Expiration
22 Point of Service M 22 Point-of-Service
Data Code Entry Mode
- s7 Card Data: M 22/1 Point-of-Service
Input Mode Entry Mode
23 Card Sequence O 23 Card Sequence
Number Number
24 Function Code M 200
25 Message O
Reason Code
26 Card Acceptor M 18 Merchant Type
Business Code (MCC)
Data Element
Data Element M— Guiding Data Element Name—Single
Data Element Name—IPM Mandatory / Comments or No.—Single Message
—IPM 1240 1240 O—Optional Maps to Value Message 0200 System 0200
30 Amounts, O 4 Amount,
Original Transaction
5
Amount,
Settlement
Data Element
Data Element M— Guiding Data Element Name—Single
Data Element Name—IPM Mandatory / Comments or No.—Single Message
—IPM 1240 1240 O—Optional Maps to Value Message 0200 System 0200
p0052 Electronic O 48/42 Additional Data
Commerce
Security Level
Indicator
p0057 Transaction O 48/61 Additional Data
Category
Indicator
p0058 Token O
Assurance Level
p0059 Token O
Requestor ID
p0080 Amount, Tax O
p0145 Amount, O
Alternate
Transaction Fee
p0146 Amounts, O 28 Amount,
Transaction Fee Transaction Fee
p0148 Currency M ISO Currency
Exponents Exponent from
the FIT file or
Member
Parameter
Extract (MPE)
for each
currency code
used in the
transaction
p0149 Currency O 49 Currency Code,
Codes, 50 Original
Amounts, Transaction
Original Amount
Currency Code,
Original
Reconciliation
Amount
p0157 Alternate O
Processor
Indicator
Data Element
Data Element M— Guiding Data Element Name—Single
Data Element Name—IPM Mandatory / Comments or No.—Single Message
—IPM 1240 1240 O—Optional Maps to Value Message 0200 System 0200
p0158 Business O 110 Additional Data
Activity -2
p0159 Settlement O 110/7 Additional Data
Data -2
p0165 Settlement M C
Indicator
p0170 Card Acceptor O
Inquiry
Information
p0171 Alternate Card O
Acceptor
Description
p0172 Sole Proprietor O
Name
p0173 Legal O
Corporate
Name
p0174 Dun & O
Bradstreet
Number
p0175 Card Acceptor O
URL
p0176 Mastercard O 48/32 Additional Data
Assigned ID
p0177 Cross-border O 126 Switch Private
Data
p0178 Alternate Card O
Acceptor
Description
Data 2
p0179 Long Running O
Transaction
(LRT) Indicator
p0180 Domestic Card O
Acceptor Tax ID
p0181 Installment O
Payment Data
Data Element
Data Element M— Guiding Data Element Name—Single
Data Element Name—IPM Mandatory / Comments or No.—Single Message
—IPM 1240 1240 O—Optional Maps to Value Message 0200 System 0200
p0189 Point-of- O
Interaction
(POI) Phone
Data
p0190 Partner ID O
Code
p0191 Originating O
Message
Format
p0193 Subscriber O
Reference Data
p0194 Remote O
Payment
Program Date
p0195 Installment O
Data
p0196 Mobile Phone O
Reload Data
p0197 National Use O
Tax Data
p0198 Device Type O
p0199 Funding O
Transaction
Information
p0202 PAN Syntax O
Error
p0204 Amount, O
Syntax Error
p0205 Syntax Return, O
Message Error
Indicator
p0207 Wallet Identifier O
p0208 Additional O
Merchant Data
p0209 Independent O
Sales
Organization ID
Data Element
Data Element M— Guiding Data Element Name—Single
Data Element Name—IPM Mandatory / Comments or No.—Single Message
—IPM 1240 1240 O—Optional Maps to Value Message 0200 System 0200
p0210 Transit Program O
p0211 Terminal O
Compliant
Indicator
p0220 Brazil Merchant O
Tax ID
p0225 Syntax Return, O
Original
Message
Reason Code
p0261 Risk O
Management
Approval Code
(Rejected by
Mastercard)
p0375 Member O
Reconciliation
Indicator 1
p0446 Transaction Fee O
Amount,
Syntax Error
p0502 Custom O
Identifier
p0596 Card Acceptor O
Tax ID
p0597 Total Tax O
Amount
p0623 Motor Fuel O
Information
p0629 Odometer O
Reading
p0799 Test Case O
Traceability
Identifiers
Data Element
Data Element M— Guiding Data Element Name—Single
Data Element Name—IPM Mandatory / Comments or No.—Single Message
—IPM 1240 1240 O—Optional Maps to Value Message 0200 System 0200
p10XX Member-to- O
Member
Proprietary
Data (p1000
through p1099)
49 Currency Code, M 49 Currency Code,
Transaction Transaction
50 Currency Code, O 50 Currency Code,
Reconciliation Settlement
51 Currency Code, O 51 Currency Code,
Cardholder Cardholder
Billing Billing
54 Amounts, O 54 Additional
Additional Amounts
55 Integrated O 55 Integrated
Circuit Card Circuit Card
(ICC) System (ICC) System-
Related Data Related Data
62 Additional Data O 62 INF Data
2
63 Transaction Life O 63 Network Data
Cycle ID
71 Message M Per definition in
Number IPM Manual
94 Transaction M 32 Acquiring
Originator Institution
Institution ID Identification
Code Code
123 Additional Data O
3
124 Additional Data O
4
125 Additional Data O
5
Interchange Fees
Global Clearing Management System offers several options related to interchange fees for
bilaterally settled transactions:
• If the Business Service assigned to a bilaterally settled transaction indicates that Global
Clearing Management System should calculate interchange fees, Global Clearing
Management System will calculate the interchange fees, convert them to the receiving
customer’s reconciliation currency, and populate PDS 0146 (Amounts, Transaction Fees),
subfield 4 (Currency Code, Fee), subfield 5 (Amount, Fee), subfield 6 (Currency Code, Fee,
Reconciliation), and subfield 7 (Amount, Fee, Reconciliation) PDS 0147 (Extended Precision
Amounts), subfield 4 (Currency Code, Fee), subfield 5 (Amount, Fee), subfield 6 (Currency
Code, Fee, Reconciliation), and subfield 7 (Amount, Fee, Reconciliation) with the correct
interchange fees and associated currency codes before forwarding the message to the
receiver.
• If the Business Service assigned to a bilaterally settled transaction indicates that Global
Clearing Management System should not calculate interchange fees, the sending customer
may optionally populate PDS 0146, subfields 4 and 5 with the relevant interchange fees.
Global Clearing Management System will forward PDS 0146, subfields 4 and 5 to the
receiving customer without altering the data. In addition, Global Clearing Management
System will convert the fees that were provided in PDS 0146, subfields 4 and 5 to the
receiving customer’s reconciliation currency and place this amount and currency into PDS
0146, subfields 6 and 7 before forwarding the message to the receiver.
• If the Business Service assigned to a bilaterally settled transaction indicates that Global
Clearing Management System should not calculate interchange fees, and the sending
customer does not provide fees in PDS 0146, Global Clearing Management System will
process the transaction with no interchange fees. PDS 0146 will not be present in the
message sent to the receiver.
Electronic Commerce
Electronic commerce (e-commerce) transactions are non–face-to-face, online transactions that
use electronic media over any public network such as the Internet, or private network such as
an extranet. E-commerce processing allows transactions to be initiated from a cardholder-
controlled device, such as a PC or mobile phone, for purchasing goods and services on the
Internet.
Customer Requirements
To process e-commerce transactions:
• All issuers must be able to receive and process all e-commerce data present in the
Authorization Request/0100 messages.
• All acquirers must properly identify e-commerce messages within the Authorization
Request/0100 message. They must be able to receive and to process e-commerce
Authorization Request Response/0110 messages.
For detailed transaction flows and requirements associated with participation in the
Mastercard® SecureCode/Identity Check program, refer to the SecureCode Member
Enrollment and Implementation Guide and Mastercard Identity Check Program Guide. For
details about data requirements and transaction processing specifications, refer to the
Customer Interface Specification manual.
1. The cardholder accesses a merchant’s Web site through the Internet and requests to make
a purchase.
2. The merchant submits the cardholder’s information to the acquirer.
3. The acquirer sends an Authorization Request/0100 message through the Mastercard
Network to the issuer.
4. The issuer makes the authorization decision and replies using an Authorization Request
Response/0110 message.
5. The acquirer responds to the merchant.
6. The merchant completes the transaction according to the authorization response returned.
NOTE: Without UCAF data present, a re-authorized transaction must be presented within
clearing for non-UCAF interchange (as applicable by region).
For more information about SecureCode/Identity Check, including detailed transaction flows
and participation requirements, refer to the SecureCode Issuer Implementation Guide,
SecureCode Merchant Implementation Guide, SecureCode Acquirer Implementation Guide, or
Mastercard Identity Check Program Guide.
the merchant for placement in the authorization request upon successful authentication of
the cardholder.
UCAF is used to transmit the AAV from the merchant to the issuer for authentication purposes
during the authorization process.
Customers must perform AAV validation during the Authorization Request/0100 messages,
either through their own self-validation process or through the Mastercard SecureCode AAV
Verification service.
All customers must participate in Mastercard SecureCode Dynamic AAV Verification in Stand-
In Processing.
To implement the Mastercard SecureCode AAV Verification service, complete the Key
Validation Service Specification Form (Form 735).
NOTE: All issuers globally that participate in Stand-In processing must have SecureCode
Dynamic AAV verification in Stand-In performed during Stand-In processing.
Effective on or before 1 April 2017 based on region specific effective dates per Global
Operations Bulletin No. 4, 1 April 2016, Revised Standards for Validation Services During
Stand-In Processing, all issuers globally that participate in Stand-In processing must have
Dynamic CVC 3 Validation in Stand-In performed during Stand-In processing.
DE 22 (Point of Service Data Code), Subfield 1 (Terminal Data: Card Data Input
Capability)
The description for DE 22 (Point of Service Data Code), subfield 1 (Terminal Data: Card Data
Input Capability), value 1 reads Manual; no terminal; server. This definition indicates the ability
to capture the PAN entry through server.
Issuers participating in the Mastercard Merchant Data Cleansing Plus service receive cleansed
merchant data in the following data fields on First and Second Presentment/1240 messages:
• DE 43 (Card Acceptor Name/Location), subfield 1 (Card Acceptor Name)
• DE 43, subfield 2 (Card Acceptor Street Address)
• DE 43, subfield 3 (Card Acceptor City)
• DE 43, subfield 4 (Card Acceptor Postal [ZIP] Code)
• DE 43, subfield 5 (Card Acceptor State, Province, or Region Code)
• DE 43, subfield 6 (Card Acceptor Country Code)
• PDS 0170 (Card Acceptor Inquiry Information), subfield 2 (Card Acceptor Phone Number)
First and Second Presentment/1240 messages are not enriched with cleansed merchant data if
the country code, as submitted by the acquirer in DE 43, subfield 6 is different than the
cleansed merchant data country code maintained by Mastercard. However, if participating in
Mastercard Merchant Data Cleansing Plus, the following additional data fields are provided in
First and Second Presentment/1240 messages:
• PDS 0214 (Merchant Data Cleansing Plus), subfield 1 (Cleansed Legal Corporate Name)
• PDS 0214, subfield 2 (Sales Channel—Percentage Brick)
• PDS 0214, subfield 3 (Sales Channel—Percentage Online)
• PDS 0214, subfield 4 (Sales Channel—Percentage Other)
• PDS 0214, subfield 5 (Cleansed Merchant URL)
NOTE: For First Chargeback and Arbitration Chargeback/1442 messages, the issuer is not
required to retain and return the PDS 0212, PDS 0213, PDS 0214, or PDS 0215 data.
Issuers must return the same data values in DE 43 and PDS 0170, subfield 2 as was received in
the associated First and Second Presentment/1240 messages.
Viewing Data Fields of Merchant Data Services in the Transaction Research Tool
Issuers participating in any of the Mastercard Merchant Data services may view all of the
applicable data fields in the Transaction Investigator Tool.
Starting
Field Name DE PDS Subfield Length Position
D (Detail static value 1 1
Record)
Acquirer ICA 11 2
Message Type MTI 4 13
Indicator
PAN 2 19 17
Processing 3 1, 2, 3 6 36
Code (includes
all subfields)
Amount, 4 12 42
Transaction
Reconciliation 5 12 54
Amount
Date and Time, 12 12 66
Local
Transaction
Starting
Field Name DE PDS Subfield Length Position
Point of Service 22 1–12 12 78
Data Code
Function Code 24 3 90
Message 25 4 93
Reason Code
Card Acceptor 26 4 97
Business Code
Acquirer 31 23 101
Reference Data
Approval Code 38 6 124
Service Code 40 3 130
Card Acceptor 41 8 133
Terminal ID
Card Acceptor 42 15 141
ID Code
Card Acceptor 43 1, 2, 3 83 156
Name and
Location
Card Acceptor 43 4 10 239
Post Code
Global Clearing 2 3 249
Management
System Product
Identifier
Licensed 3 3 252
Product
Identifier
Terminal Type 23 3 255
Message 25 1 1 258
Reversal
Indicator
Electronic 52 1,2,3 3 259
Commerce
Security Level
Indicator
File ID—File 105 2 6 262
Reference Date
Starting
Field Name DE PDS Subfield Length Position
Fee Type Code 146 1 2 268
Fee Processing 146 2 2 270
Code
Fee Settlement 146 3 2 272
Indicator
Currency Code 146 4 3 274
Amounts, 146 5 12 277
Transaction Fee
Currency Code 146 6 3 289
Fee
Reconciliation
Amount Fee 146 7 12 292
Reconciliation
Extended—Fee 147 1 2 304
Type Code
Extended—Fee 147 2 2 306
Processing
Code
Extended—Fee 147 3 2 308
Settlement
indicator
Extended— 147 4 3 310
Currency Code,
Fee
Extended— 147 5 18 313
Interchange
Amount, Fee
Extended— 147 6 3 331
Currency Code,
Fee, Recon.
Extended— 147 7 18 334
Interchange
Amount, Fee,
Recon.
Currency 148 1, 2 4 352
Exponents
Card Program 158 1 3 356
Identifier
Starting
Field Name DE PDS Subfield Length Position
Business Service 158 2 1 359
Arrangement
Type Code
Business Service 158 3 6 360
ID Code
Interchange 158 4 2 366
Rate Designator
Central Site 158 5 6 368
Business Date
Business Cycle 158 6 2 374
Card Acceptor 158 7 1 376
Classification
Override Ind.
Product Class 158 8 3 377
Override
Indicator
Corporate 158 9 1 380
Incentive Rates
Apply Indicator
Special 158 10 1 381
Conditions
Indicator
Mastercard 158 11 1 382
Assigned ID
Override
Indicator
ALM Account 158 12 1 383
Category Code
Rate Indicator 158 13 1 384
MasterPass 158 14 1 385
Incentive
Indicator
Settlement 159 1 11 386
Service Transfer
Agent ID
Settlement 159 2 28 397
Service Transfer
Agent Account
Starting
Field Name DE PDS Subfield Length Position
Settlement 159 3 1 425
Service Level
Code
Settlement 159 4 10 426
Service ID Code
Settlement 159 5 1 436
Foreign
Exchange Rate
Class Code
Reconciliation 159 6 6 437
Date
Reconciliation 159 7 2 443
Cycle
Settlement 159 8 6 445
Date
Settlement 159 9 2 451
Cycle
Transaction 49 3 453
Currency Code
Reconciliation 50 3 456
Currency Code
Additional 54 20 459
Amount
Trace ID 63 2 15 479
Trailer Record
NOTE: The Interchange Detail Report will not include Collection-Only messages.
It will be sent to acquirers through Global File Transfer using Bulk File TN70. Acquirers can use
bulk file TN72 for testing.
Acquirers will be able to choose between 2 versions:
• Version 1—Acquirer only activity
– 1st Presentments and reversals
– 2nd Presentments and reversals
• Version 2—Acquirer and Issuer activity
– 1st Presentments and reversals
– 2nd Presentments and reversals
Detail Record
Trailer Record
Mastercard sends the Clearing Detail File at the end of each clearing cycle for all activity in
that clearing cycle.
NOTE: If the Clearing Detail File Record does not contain data for the customer, then the
customer receives only the header and trailer for the Clearing detail file.
Table 7: Acquirer Currency Conversion Rate File Header Record (Regional First
Presentments)
Field Number
and
Comments and
Name Position Length Format Values
1 Header 1 1 an Constant—H
Description
2 Date 2-9 8 n File creation date.
YYYYMMDD
3 Time 10-15 6 n The time the file
was created.
Coordinated
Universal time
(UTC); six digits in
military format
HHMMSS. For
example, 3:30:30
p.m. would show
as 153030.
4 Rate File Format 16 1 an This field identifies
Version the file format
version. The initial
version will be 2
and will be
incremented each
time the file
format changes.
5 Filler 17-60 44 an Spaces
Table 8: Acquirer Currency Conversion Rate File Detail Record (Regional First
Presentments)
Field Number
and
Comments and
Name Position Length Format Values
1 Detail 1 1 an Constant—R
Description
2 Transaction 2-4 3 n Represents
Currency Code transaction
currency code.
3 Acquirer Recon 5-7 3 n Represents
Currency Code acquirer
reconciliation
currency code.
4 Rate Class 8 1 an • M=
Mastercard-
issued U.S.
dollar rates
• F = Mastercard-
issued cross
rates
• X = Calculated
cross rates
Table 9: Acquirer Currency Conversion Rate File Trailer Record (Regional First
Presentments)
Field Number
and
Comments and
Name Position Length Format Values
1 Trailer 1 1 an Constant—T
Description
Field Number
and
Comments and
Name Position Length Format Values
2 Count 2-11 10 n Total number of
detail records. This
count does not
include the header
or trailer records.
3 Filler 12-60 49 an Spaces
Table 10: Acquirer Currency Conversion Rate File Header Record (Regional Second
Presentments)
Field Number
and
Comments and
Name Position Length Format Values
1 Header 1 1 an Constant—H
Description
2 Date 2-9 8 n File creation date.
YYYYMMDD
3 Time 10-15 6 n The time the file
was created.
Coordinated
Universal time
(UTC); six digits in
military format
HHMMSS. For
example, 3:30:30
p.m. would show
as 153030.
4 Rate File Format 16 1 an This field identifies
Version the file format
version. The initial
version will be 3
and will be
incremented each
time the file
format changes.
5 Filler 17-60 44 an Spaces
Table 11: Acquirer Currency Conversion Rate File Detail Record (Regional Second
Presentments)
Field Number
and
Comments and
Name Position Length Format Values
1 Detail 1 1 an Constant—I
Description
2 Transaction 2-4 3 n Represents
Currency Code transaction
currency code.
3 Acquirer Recon 5-7 3 n Represents
Currency Code acquirer
reconciliation
currency code.
4 Rate Class 8 1 an • M=
Mastercard-
issued U.S.
dollar rates
• F = Mastercard-
issued cross
rates
• X = Calculated
cross rates
Table 12: Acquirer Currency Conversion Rate File Trailer Record (Regional Second
Presentments)
Field Number
and
Comments and
Name Position Length Format Values
1 Trailer 1 1 an Constant—T
Description
Field Number
and
Comments and
Name Position Length Format Values
2 Count 2-11 10 n Total number of
detail records. This
count does not
include the header
or trailer records.
3 Filler 12-60 49 an Spaces
Table 13: Acquirer Currency Conversion Rate File Header Record (Intracurrency
Presentments)
Field Number
and
Comments and
Name Position Length Format Values
1 Header 1 1 an Constant—H
Description
2 Date 2-9 8 n File creation date.
YYYYMMDD
3 Time 10-15 6 n The time the file
was created.
Coordinated
Universal time
(UTC); six digits in
military format
HHMMSS. For
example, 3:30:30
p.m. would show
as 153030.
4 Rate File Format 16 1 an This field identifies
Version the file format
version. The initial
version will be 4
and will be
incremented each
time the file
format changes.
5 Filler 17-60 44 an Spaces
Table 14: Acquirer Currency Conversion Rate File Detail Record (Intracurrency
Presentments)
Field Number
and
Comments and
Name Position Length Format Values
1 Detail 1 1 an Constant—S
Description
2 Transaction 2-4 3 n Represents
Currency Code transaction
currency code.
3 Acquirer Recon 5-7 3 n Represents
Currency Code acquirer
reconciliation
currency code.
4 Rate Class 8 1 an • M=
Mastercard-
issued U.S.
dollar rates
• X = Calculated
cross rates
Table 15: Acquirer Currency Conversion Rate File Trailer Record (Intracurrency
Presentments)
Field Number
and
Comments and
Name Position Length Format Values
1 Trailer 1 1 an Constant—T
Description
Field Number
and
Comments and
Name Position Length Format Values
2 Count 2-11 10 n Total number of
detail records. This
count does not
include the header
or trailer records.
3 Filler 12-60 49 an Spaces
Originating Institution Payment Transaction Currency Conversion Rate File Format...................... 468
Table 16: Originating Institution Payment Transaction Currency Conversion Rate File
Header
Field Number
and
Comments and
Name Position Length Format Values
1 Header 1 1 an Constant–H
Description
2 Date 2-9 8 n File creation date.
YYYYMMDD
3 Time 10-15 6 n The time the file
was created.
Coordinated
Universal time
(UTC); six digits in
military format
HHMMSS. For
example, 3:30:29
p.m. would show
as 153029.
4 Rate File Format 16 1 an This file identifies
Version the file format
version. The initial
version will be 2
and will be
incremented each
time the file
format changes.
5 Filler 17-60 44 an Spaces
Table 17: Originating Institution Payment Transaction Currency Conversion Rate File
Detail Record
Field Number
and
Comments and
Name Position Length Format Values
1 Detail 1 1 an Constant—R
Description
2 Transaction Type 2-4 3 an Transaction Type
Identifier Identifier. Valid
value is:
• CXX (default
value)
Field Number
and
Comments and
Name Position Length Format Values
6 Effective 12-26 15 n Conversion rate
Currency (Assumed decimal
Conversion Rate after position 19).
Eight positions to
the left of the
decimal, seven
positions to the
right of the
decimal.
7 Filler 27-60 34 an Spaces
Table 18: Originating Institution Payment Transaction Currency Conversion Rate File
Trailer Record
Field Number
and
Comments and
Name Position Length Format Values
1 Trailer 1 1 an Constant—T
Description
2 Record Count 2-11 10 n Total number of
detail records. This
count does not
include the header
or trailer records.
3 Filler 12-60 49 an Spaces
The following steps explain how originating institutions can determine the reconciliation
amount using the Originating Institution Payment Transaction Currency Conversion Rate File.
1. Locate the record in the Originating Institution Payment Transaction Currency Conversion
Rate File where the Transaction Type Identifier matches the value in field 2, the transaction
currency matches the currency in field 3, and the Originating Institution reconciliation
currency matches the currency in field 4. If there is no match in field 2, then use the
default value of CXX (as the Transaction Type Identifier) to match.
2. Multiply the effective currency conversion rate in field 6 by the transaction amount to
determine the originating institution’s reconciliation amount.