File Transfer Manual

File Transfer Manual
Version 1.1
22 June 2020
Contents
Contents
Summary of Changes, 22 June 2020............................................................... 6
Chapter 1: File Transfer Overview.................................................................... 7

About File Transfer...............................................................................................................8
File Transfer Reference Information.................................................................................9
Maintenance.......................................................................................................................... 9
Chapter 2: File Transfer Mechanisms........................................................... 10

About File Transfer Mechanisms.....................................................................................11
Mastercard File Express Client........................................................................................12
Mastercard File Express Scheduler................................................................................ 13
Mastercard Interface Processor......................................................................................14
IBM – Sterling Connect:Direct.........................................................................................15
Mastercard Data Exchange............................................................................................. 16
Third Party SFTP Client.................................................................................................... 17
Secure Delivery File Push (SD File Push).......................................................................18
Chapter 3: Getting Started................................................................................ 20

About File Transfer Options ............................................................................................21
File Transfer Option Selection.........................................................................................21
About Bulk File Types....................................................................................................21
File Transfer System Implementation........................................................................... 22
Chapter 4: Proprietary Mastercard Bulk File Transfer

Mechanisms................................................................................................................. 25
Mastercard File Express Client........................................................................................27
Registering for File Express.........................................................................................28
Mastercard File Express Scheduler................................................................................ 28
Mastercard Data Exchange............................................................................................. 30
Mastercard Interface Processors....................................................................................31
Generic File Naming on the MIP.................................................................................32
Mastercard Network and Bulk File Transfer on the MIP.......................................33
Connectivity...............................................................................................................33
File Transfers from Mastercard to Customer............................................... 33
File Transfers to Mastercard............................................................................. 34
Bulk File Identifiers and Types.................................................................................... 35
Member Host to MIP to Mastercard Translation Dialogs.................................... 36
©2020 Mastercard. Proprietary. All rights reserved.

File Transfer Manual—Version 1.1 • 22 June 2020 2
Contents
Successful Transfer Dialog..................................................................................... 36

Duplicate Transfer Refused Dialog....................................................................... 38
Error During Transmission Dialog......................................................................... 38
Block Count Discrepancy Dialog........................................................................... 39
Data Fails Edit Dialog............................................................................................. 41
Too Much Data in Last Block Dialog.................................................................... 42
Member MIP to Member Host from Mastercard Transaction Dialogs..............44
Successful Transfer Dialog..................................................................................... 44
Error During Transmission Dialog......................................................................... 46
Block Count Discrepancy Dialog........................................................................... 47
About Record Types Used in Bulk File Transfer Protocol...................................... 49
Record Types Used in Bulk File Transfer To Mastercard...................................49
Record Types Used in Bulk File Transfer From Mastercard............................. 51
Bulk File Advisements...................................................................................................54
201—Bulk File Advisement Solicit Message........................................................ 55
202—Bulk File Advisement Response Message..................................................56
198—Data Acknowledgement Message.............................................................. 59
298—Trailer Message................................................................................................59
Exception Handling....................................................................................................... 60
Operator Console Messages.......................................................................................61
COBOL Template.......................................................................................................... 62
Bulk Data Test Plan.......................................................................................................65
Chapter 5: Third-Party File Transfer Mechanisms and

Solutions........................................................................................................................66
File Transfers by Third Party Solutions..........................................................................67
IBM – Sterling Connect:Direct ........................................................................................67
Is Sterling Connect:Direct Right for Your Business?.............................................. 67
Getting Started with Sterling Connect:Direct....................................................... 68
Sterling Connect:Direct Security Profile.................................................................. 68
Sterling Connect:Direct Configuration.....................................................................69
Secure Shell File Transfer Protocol (SFTP)...................................................................69
Chapter 6: Global File Transfer Endpoint and Bulk File Naming

Convention................................................................................................................... 71
EndPoints............................................................................................................................. 72
Bulk Types and Bulk Files..................................................................................................72
File Naming Convention in the Mastercard Repository.............................................74

Contents
Chapter 7: Mastercard Processing Environments................................. 77

Production Environment...................................................................................................78
Mastercard Test Facility................................................................................................... 78
Appendix A: Recovery and Resumption of Service................................ 79

Disruption and Business Resumption Service..............................................................80
GCMS/Non-GCMS Recovery...........................................................................................80
Business Recovery Options...............................................................................................80
Business Resumption Testing Process........................................................................... 80
Appendix B: Member Host Preparation Facility..................................... 82

About Member Host Preparation Facility.....................................................................83
Compile/Assemble and Link MHPF Programs.............................................................83
OS—Compiling COBOL Modules................................................................................83
OS—Assembler Programs............................................................................................85
Required Order of Compilation and Assembly....................................................... 86
Compile and Link Edit of Specific Source Modules................................................86
CR99XXXX..................................................................................................................86
CR992050 Codes..................................................................................................87
CR992070 Codes..................................................................................................90
IE7400010...................................................................................................................93
MH410010..................................................................................................................93
MH545010..................................................................................................................94
MH550010..................................................................................................................94
MH580010..................................................................................................................95
MH590010..................................................................................................................95
MH560010..................................................................................................................96
MH600010..................................................................................................................96
MH500010..................................................................................................................97
Member Profile Extract File.............................................................................................98
Daily Member Profile Extract Upload Job............................................................... 98
Member Profile Extract File Record Types...............................................................98
Member Profile 5—Currency Conversion Values, ISO Code, ISO Rate,
and Rate Exponent...................................................................................................99
Member Profile 6—Bulk Type............................................................................... 100
Member Profile 8—MHPF Current Program Version Numbers.................... 102
JCL Setup.......................................................................................................................... 104
SMH1002R....................................................................................................................104
SMH1003R....................................................................................................................107
SMH2001R....................................................................................................................110

Contents
SMH2003R....................................................................................................................114
Appendix C: MIP Bulk File Advisement...................................................... 118

About MIP Bulk File Advisement Program................................................................. 119
Current Environment.......................................................................................................119
How It Works.....................................................................................................................119
Customer Internal System Enhancement Options.................................................. 120
Customer-Defined Parameters.................................................................................... 120
Parameter Control Card File Queries.....................................................................121
JCL Setup (SMR4001R)..................................................................................................123
Parameter Control Card File (MH410010).................................................................124
MIP Bulk File Advisement File Layout (MH410010)................................................. 125
Bulk File Advisement Report (MH410010-AA).......................................................... 127
MH410 Console Messages............................................................................................. 130
Appendix D: Testing Procedures.................................................................... 132

About Testing Procedures.............................................................................................. 133
Priority of Testing Activities...........................................................................................133
Installing MHPF................................................................................................................ 134
Testing Procedures for MIP/MHPF Customers......................................................... 135
Pended Transmissions.....................................................................................................136
Testing Procedure for Third Party File SFTP Client..................................................136
Production.....................................................................................................................137
Testing the domain name service for attended or unattended
production URL....................................................................................................... 137
Testing SFTP Connection.................................................................................137
MTF.................................................................................................................................138
Testing the domain name service for attended or unattended MTF URL.138
Testing SFTP Connection.................................................................................138
Contact and Support........................................................................................... 140
Notices......................................................................................................................... 141

Summary of Changes, 22 June 2020
Summary of Changes, 22 June 2020

This document reflects the following changes that are effective 22 June 2020.
Description of Change Where to look at

Updated Mastercard supported File Throughout the document
Transfer Protocols and Software versions

File Transfer Overview
Chapter 1 File Transfer Overview

This section provides an overview of the basics of bulk file transfer and why it is important
to your business. File transfer references and maintenance window information are also
included.
About File Transfer............................................................................................................................ 8

File Transfer Reference Information.............................................................................................. 9
Maintenance........................................................................................................................................9

About File Transfer
About File Transfer

File Transfer is the process of exchanging one or more files over a computer
network, using a predetermined protocol (formal set of rules, conventions, and
data structures).
The Mastercard Global File Transfer System (GFT) is the name given to the
Mastercard infrastructure that manages the exchange of files between
Mastercard and its customers (acquirers, issuers, processors, business partners,
and vendors).
The following diagram displays the GFT routes files bi-directionally (sending and
receiving) between customers and Mastercard’s many services and applications.
There are many methods and software applications that customers can use to
exchange bulk files. When considering bulk file transfer options for their
businesses, customers should compare several hardware and software choices to
determine the best solution. This document may help customers to build and to
maintain a reliable file transfer network.
Most Mastercard customers and business partners exchange at least one kind of
bulk file with Mastercard. If customers send Mastercard bulk files for processing,
they may receive bulk files back from Mastercard. This return of information may
be in the form of confirmations, reports, or processed bulk files. Some customers
also exchange bulk files with other acquirers, clearing banks, business partners, and
support vendors.
Mastercard supports several different options for bulk file exchange. Mastercard
has developed some of these options, and some of these options are solutions
from third-party vendors. These file transfer mechanisms offer a wide range of
functions for a wide range of associated costs.
Mastercard does not recommend any specific file transfer method. Customers
must determine which solution best meets their budget and business model. The
information provided in this manual is presented as an objective evaluation to help
customers make informed decisions.
The Global File Transfer System provides:
• Support for multiple File Transfer methods
• Centralized management of file exchange–customers need only connect to one
point to exchange files with all Mastercard applications

File Transfer Reference Information
• Endpoints–destination points for customer files (similar in concept to mailbox

addresses)
• In most cases, customers can send files using their own naming conventions
• Transmission status reporting (success/failure)
• Secure transmission of data
File Transfer Reference Information

The File Transfer Manual is a comprehensive reference manual for file transfer and
file transfer mechanisms.
This manual includes information about Mastercard Interface Processors (MIPs),
Connect Direct, Mastercard File Express Client, Mastercard File Express Scheduler,
Third Party SFTP Client, Mastercard Data Exchange, and Secure Delivery File Push.
Customers who choose a third-party software solution should use the third-party
vendor’s user manuals and documentation for detailed product information.
Because this manual is the primary source of information about Mastercard
proprietary file transfer mechanisms but not for third-party solutions, it contains
detailed information about the proprietary solutions and general information for
third-party solutions.
Maintenance
From time to time, Mastercard performs maintenance on the File Transfer
Architecture. The following information outlines the outage windows when
customers can expect to experience a temporary lapse in File Exchange services.
Mastercard File Express Products

The maintenance window for Mastercard File Express products is Saturday from
22:00 (St. Louis time) to Sunday at 06:00 (St. Louis time). During this period,
customers can expect to experience file exchange issues.
Mastercard File Express Products (Customer-initiated Push and Pull) include the
following:
• Mastercard File Express Client
• Mastercard Express Scheduler
• Mastercard Data Exchange
• Third Party SFTP Client

File Transfer Mechanisms
Chapter 2 File Transfer Mechanisms

This section provides an overview of various file transfer mechanism software packages.
About File Transfer Mechanisms.................................................................................................. 11

Mastercard File Express Client..................................................................................................... 12
Mastercard File Express Scheduler..............................................................................................13
Mastercard Interface Processor................................................................................................... 14
IBM – Sterling Connect:Direct...................................................................................................... 15
Mastercard Data Exchange...........................................................................................................16
Third Party SFTP Client..................................................................................................................17
Secure Delivery File Push (SD File Push).................................................................................... 18

About File Transfer Mechanisms
About File Transfer Mechanisms

Mastercard supports several approved file transfer mechanism software packages.
Mastercard has developed proprietary file transfer methods that interface with
Mastercard business systems (Mastercard interface processor [MIPs], Mastercard
File Express Client, Mastercard File Express Scheduler, and Mastercard Data
Exchange). Additionally, Mastercard supports the use of several third-party file
exchange software packages.
Mastercard does not recommend any specific file transfer method. Customers
must determine which solution best meets their budget and business model. This
information is provided to help customers make informed decisions.
Mastercard Network
Many file transfer mechanisms move data using the Mastercard Network. The
Mastercard Network is the primary “data transport” communications facility that
links all Mastercard customers and Mastercard data. Customers looking for a
solution that bypasses the Mastercard Network should consider using file transfer
mechanisms that support Internet or dial-up connectivity, including third-party
SFTP or File Express.

Mastercard supports several file transfer mechanisms.
• Mastercard File Express Client
• Mastercard File Express Scheduler
• Mastercard interface processor (MIP)
• Connect:Direct
• Mastercard Data Exchange
• Secure Delivery File Push
• Third Party SFTP Client

Mastercard File Express Client

File Express Client provides a reliable, secure way for customers to upload files to
Mastercard and download files from Mastercard in an attended mode.
System Requirements
• Windows® XP (32 bit); Windows® 7 (32 and 64 bit); Windows Server 2003 (32
bit); Windows 2008 R2 (64 bit)
• Java® Runtime Environment (JRE).
JRE is a component of Mastercard File Express Software Package that will be
installed in a custom location. File Express Client is coded to always use the
specific JRE version from that custom location. Alternatively, Customers may
also use an upgraded JRE Version after checking with Support team if the
version they intend to use is supported for the Client or not.
• Registered with Mastercard Connect™ and have a SecurID® token.
Features
Using File Express Client, you can:
• Exchange (download and upload) production and test files between Mastercard
and your host.
• Retrieve archived files. Archived files are those files that have been previously
downloaded from Mastercard successfully. Archived files are available for
retrieval for 30 calendar days which may be overridden to align to regulatory
reasons like On Soil requirements

Mastercard File Express Scheduler
• Display and print a file transmission report for information regarding successful
or unsuccessful file transfers that occurred during the current transfer session.
• Display and print an audit report for a selected file transfer session. The audit
report contains the specific file exchanged, date and time of the exchange, file
size, and overall transfer session status.
• Display and print a transfer log containing a report for every file transfer
attempted with the Mastercard File Express server on a specific day. The
transfer log report includes the transfer date and time, if the transfer was
successful or unsuccessful, the endpoint of the file transferred, bulk type, and
source file.
NOTE:
• If using the Client program, implementation time is typically 2-3 weeks.
• If using the Scheduler program, implementation time is typically 3-4 weeks.
For more information, see the File Express Client User Guide.

File Express Scheduler provides a secure, reliable way for customers to upload files
to Mastercard and download files from Mastercard in an unattended mode.
System Requirements
installed in a custom location. File Express Scheduler is coded to always use the
specific JRE version from that custom location. Alternatively, Customers may
also use an upgraded JRE Version after checking with Support team if the
version they intend to use is supported for the Scheduler or not.
Features
Using File Express Scheduler, you can:
• Define, maintain, and control a custom file exchange schedule. Files are
transferred with Mastercard on this schedule, with no required user intervention
to initiate each exchange.
• View a list of bulk types by endpoint, the bulk type staging directory, next
transfer time, and last transfer status.
• Specify a staging directory for each bulk type.
• Define a file transfer schedule for each bulk type you exchange with Mastercard
through a given endpoint.

Mastercard Interface Processor
• Specify the schedule for a given bulk type using periodic intervals or a set of
specific times.
• Display and print an audit report for a selected file transfer session. The audit
report contains specific file names exchanged, date and time of the exchange,
file size, and overall transfer session status.
• Display and print a transfer log containing a report for every file transfer
attempted with the Mastercard File Express server on a specific day. The
transfer log report includes the transfer date and time, if the transfer was
successful or unsuccessful, the endpoint of the file transferred, bulk type, and
source file.
• MFE version 7.1 authenticates Scheduler (unattended) sessions with
Mastercard by using SSH (Secure Shell) keys. SSH keys use encrypted network
protocol that allows secure remote logins over an unsecured network. This level
of encryption secures the file transfer path.
• If using the Client program, implementation time is typically 2-3 weeks. While
for the Scheduler program, implementation time is typically 3-4 weeks.
For more information, see the File Express Scheduler User Guide.
Mastercard Interface Processor

Customers and business partners that exchange files with Mastercard use their
MIP for bulk file transfer at a minimal cost per transaction.
The MIP is a server customized to link with customer internal business systems and
becomes a gateway between the customer’s business and Mastercard. The MIP
can serve many business functions, including authorization.
How It Works
When a customer uses a MIP for bulk file transfer, the following process occurs:
1. The MIP relays the customer’s bulk files to Mastercard.
2. Mastercard retrieves the files sent from the MIP.
3. Mastercard processes the files.
4. Mastercard returns the response bulk files and reports to the MIP.
5. The customer retrieves the response bulk files and reports from the MIP.
Features
With the MIP bulk file transfer, no hardware or installation fees may be necessary
to upgrade an existing MIP (currently used for authorization or other functions) to
perform bulk file transfer, depending on the rate structure set by a customer’s
regional office.
• A MIP is a Mastercard server installed on the customer’s site to provide access
to the Mastercard Network.

IBM – Sterling Connect:Direct
• It is important to note that MFTS file transfer requires that customers have a
MIP, and that it is reliant on the accessibility of that MIP.
• Mastercard stages the files on the MIP, and the customer connects to the MIP
to retrieve them.
• The encryption used with MFTS Bulk File Transfer Protocol encrypts the data
only from the point of the customer’s MIP, to Mastercard.
• The file transfer between Mastercard MIP and Customer mainframe host, uses
a proprietary protocol which requires customer software development.
For more information about MIP bulk file transfer, see the Data Communications
Manual.

IBM® Sterling Connect:Direct® supports a wide range of platforms, ranging from
mainframe enterprise servers to PCs. Supported operating systems include z/OS,
AS/400, Windows NT, UNIX/Linux, and HP/NonStop.
Connect:Direct, an industry standard in file exchange for over 25 years, uses
TCP/IP (and other) protocols to establish secure peer-to-peer connections and
exchange with other Connect:Direct business partners. Although less expensive
options are available, Connect:Direct’s specialty is moving volumes of data securely
and efficiently. The Connect:Direct solution may offer more functionality than
needed for some customers that exchange only a limited number of files on a daily
basis.
Connect:Direct is a flexible solution with configuration options that allow
customers to customize connections to suit the type of data the customer is
moving.
Network Connectivity
Connect:Direct requires the use of a virtual private network similar to the
Mastercard Network. It also requires the use of either a security router or MIP.
Security Considerations
Connect:Direct uses the Mastercard Network. It can navigate files easily and
securely through a corporate firewall. It works in conjunction with all of a
customer’s existing security solutions and firewall configurations.
Similar to proprietary Mastercard file transfer mechanisms, Connect:Direct checks
the node ID associated with incoming files against a list of known node IDs to aid
in user authentication.

Mastercard Data Exchange
Features
Connect:Direct has an encryption mechanism which is a add on feature called
Secure Plus. Secure Plus requires certificates and support TLS1.2 transport
security. Connect:Direct provides the following features:
• Moves large volumes of data efficiently
• Restarts file transfer without resending the entire job in event of failure.
Checkpoint establishes a point of failure and resends from that point.
• Ensures delivery
• Automates:
– Runs in an unattended environment 24 hours a day, 7 days a week
– Schedules transfers to be performed individually or on a recurring basis
– Provides event and emergency alert notifications
• Supports data compression
• Provides flexible setup options to easily integrate existing networks and
applications
• Creates portability across mainframes, mid-ranges, desktops, and LAN-based
workstations
• Supports many operating systems and platforms
• The Connect:Direct application will be configured to save files received from
Mastercard applications to a specified directory path on the customer’s server.
• The Connect:Direct method offers options for users to perform translations (for
example, ASCII to EBCDIC).
• Connect:Direct allows automation on the receiving side following successful
transfers.
NOTE: Connect:Direct customers wanting transport encryption must order the

Connect:Direct Secure Plus product, which requires certificates for authentication.
Mastercard’s Complex-to-Complex(CTC) Admin Group will initiate the certificate exchange
between the customer and Mastercard Key Management Services (KMS). As
Connect:Direct is a third party product, Mastercard will not be able to provide technical
support for it. Support for the product is provided by the third-party vendor.
For more information, visit the IBM– Sterling Connect:Direct Web site.

Data Exchange, a browser-based product, provides customers with an easy, safe,
and secure way to exchange files to and from Mastercard.
Data Exchange is an ideal solution for those users that prefer to perform their file
transfers manually and have a relatively small number of daily files to transfer.
With Mastercard Data Exchange, there is no software to install—all you need is a
Web browser.

Third Party SFTP Client
System Requirements
Data Exchange users must be registered with Mastercard Connect™ and have a
SecurID® token. In addition, Mastercard recommends the following browsers for
optimum performance and optional browser plug-ins. Mastecard Data Exchange
works with all browsers that are supported by MC Connect.
Features
Data Exchange provides the following features:
• Exchange (downloads and uploads) production and test files between
Mastercard and your host.
• Retrieve archived files
• View a list of files uploaded (sent to Mastercard) during the current session
• Confirm that files were uploaded
The endpoint concept is particularly relevant to MDE users as they must manually
select the endpoint associated with the files they want to upload or download.
MDE provides an Endpoint Summary Page that provides summary information
about bulk file types, as well as types of files a customer can upload or download.
RSA SecurID® is a method of two-factor (two source) authentication.
For more information about using Data Exchange, see the Mastercard Data
Exchange User Guide.
Third Party SFTP Client

SSH File Transfer Protocol (SFTP) is a safe, secure, and easy-to-use file transfer
option for customers and business partners.
SFTP runs over the SSH protocol and supports the full security and authentication
functionality of SSH. It protects against password sniffing and man-in-the-middle
attacks, and also the integrity of the data using encryption and cryptographic
hash functions, and authenticates both the server and the user.
Authentication Methods
Two types of authentication methods are supported:
• Attended—RSA Token Based Authentication
• Unattended—SSH Key Pair Based Authentication
Connection Details
URL for connection and exchanging files:
• Production Environment URL (For exchanging production files):
– Attended URL—files.mastercard.com
– Attended URL Port—15022

Secure Delivery File Push (SD File Push)
– Unattended URL—files.mastercard.com
– Unattended URL Port—16022
• Test environment URL (For exchanging test files):
– Attended URL—mtf.files.mastercard.com
– Attended URL Port—15022
– Unattended URL—mtf.files.mastercard.com
– Unattended URL Port —16022
NOTE:
• Customers are recommended to use single user session at a time. If user tries to create
an additional session with an active user ID, the last session would be hijacked causing
the current session to fail.
• Implementing attended mode typically takes 2-3 weeks; unattended mode, 3-4 weeks.
• Secure Shell (SSH) is an encrypted network protocol that allows secure remote logins
over an unsecured network. This level of encryption secures the file transfer path.
• As SFTP software is a third-party product, Mastercard will not be able to provide
technical support for it. Support for the product is provided by the third-party vendor.

Secure Delivery File Push provides capability to push files from Mastercard to
customer's host machine over the Internet.
SD File Push is one of the file transfer mechanism that does not require customer
to initiate the file exchange. This is Mastercard initiated file push.
System Requirement
• For SD File Push file transfer products, a customer may choose to provide a
remote directory, URL or IP address and port to identify their target server.
• Automated connection where Mastercard pushes outbound files to the
customer’s server as they are available.
• For SFTP key-based file push, Mastercard shares SSH Public with customers to
add to their system. For SFTP password based file push, customer needs to
provide UserID and password.
• During onboarding, customer need to inform Mastercard Implementation team
if they want file to be PGP or ZIP transformed.
• For payload encryption, customer needs to share public part of PGP key with
the Mastercard using which file will be encrypted.
Features
• Support for SFTP with password/SSH Key based authentication.

• Support for SCP with password/SSH Key based authentication.

• Inline PGP or ZIP transformation (Optional).
Comparison of File Transfer Methods

Now that we have presented all of the available file transfer options, here is a
comparison of all methods and some of the important file transfer characteristics
to consider.
NOTE:
• For file transfer methods using the Mastercard Network, additional time will be needed
if customer connectivity to the Network has not yet been established.
• If the Secure Plus encryption product (for Connect:Direct) is used, certificates will be
needed for authentication.

Getting Started
Chapter 3 Getting Started

This section provides the basics for initiating, changing, or evaluating a new file transfer
mechanism.
About File Transfer Options ......................................................................................................... 21

File Transfer Option Selection.......................................................................................................21
About Bulk File Types................................................................................................................. 21
File Transfer System Implementation.........................................................................................22

Getting Started
About File Transfer Options
About File Transfer Options

Customers should consider these guidelines when selecting the best file transfer
option for their business.
Customers should contact the Mastercard Customer Operations Services team
when:
• Considering using a proprietary Mastercard file transfer system or investing in
third-party file transfer software
• Changing file transfer methods
• Requesting help to choose the best file transfer option for their business
• Making a final decision after thoroughly researching file transfer options
File Transfer Option Selection

Selecting the best file transfer option for a customer’s business is the customer’s
responsibility.
Mastercard has no financial interest in whether customers use a proprietary
Mastercard solution or a third-party solution. The interest of Mastercard is to
assist customers in choosing the appropriate file transfer option that meets their
business needs.
Customers should contact Mastercard before finalizing a file transfer option.
Mastercard experience and expertise with all of the file transfer mechanisms may
benefit customers by saving time and money. Mastercard is a trusted business
partner with all the companies whose products it supports. The relationship
between Mastercard and these solution providers may help customers create
positive customer relationships with software vendors.
About Bulk File Types

The bulk file types are subject to change as Mastercard adds or phases out
features in response to new business and technological conditions. The most
current listing of the bulk file types appears daily in the Member Profile Extract
(T007) file.
For questions about bulk file types, contact the Customer Operations Services
team.

Getting Started
File Transfer System Implementation

To implement your file transfer system, follow these steps.
Step 1—Contact the Customer Operations Services Team

As with any file transfer mechanism that customers initiate or change, customers
should begin the process of implementing file transfer by calling the Customer
Operations Services team.
Mastercard Customer Services Help Desk
1-800-999-0363 or 1-636-722-6176
1-636-722-6292 (Spanish language support)
U.S. Regional Customer Relations Offices
Atlanta: 1-678-459-9000
Chicago: 1-847-375-4000
Purchase: 1-914-249-2000
San Francisco: 1-925-866-7700
Customers should provide the name and phone number of two contacts with their
organization:
• A specialist in the customer’s physical network architecture
• A file transfer specialist
Step 2—Assemble Your Project Support Team

The Customer Operations Services team will put customer representatives in
touch with a Mastercard Network Architect, a member of the Complex-to-
Complex (CTC) Administration team, and a Customer Implementation Services
specialist. Usually this contact is accomplished in a single conference call.
If a customer is uncertain about the compatibility of their system with a given file
transfer solution, ask questions and solicit answers and advice.
If a customer finalizes a decision to change or start with a file transfer mechanism,
the support team begins processing a series of authorization forms through
Mastercard. The Mastercard support team calls the network and file transfer
contact points whom customers have designated for the information needed to
complete the various Mastercard department authorizations.
Step 3—Prepare Your Network Architecture and Bulk File Naming Strategy
After the paperwork on the file transfer method begins, implementation falls into
two separate tracks.

Getting Started
Track One—Network Architecture

The first track establishes the secured network circuit with Mastercard via the
customer’s chosen connection option.
If the customer’s connection option includes the Mastercard Network (a private
network), Mastercard may ship and install proprietary routers if necessary.
Establishing a network circuit with Mastercard also may involve getting your
business on the Mastercard Network.
Even if you manage or subscribe to another VPN, Mastercard may require you to
participate in the Mastercard private network as well. Mastercard assumes the risk
and responsibility for file transfer over its private network. Mastercard cannot
accommodate secure file transfer through an external VPN, no matter how robust
or secure it may be. The connection must always be double-matted—one end
within the Mastercard firewall and one end within the customer’s firewall.
For certain file transfer mechanisms, Internet or dial-up connectivity is available.
Track Two—Bulk File Naming Conventions
The second track prepares the customer’s bulk file naming structure to be
compatible with Mastercard file naming conventions. Depending on the file
transfer mechanism being used, bulk file naming conventions may vary. For some
file transfer mechanisms, Mastercard will provide customers with a spreadsheet of
how each customer’s file name should be named to accommodate the Mastercard
standard file naming convention. Mastercard works with customers to gather and
enter the customer’s file name structure and other critical data, such as the
maximum file size limits that the customer’s system can receive in the Mastercard
database.
NOTE: Some file transfer methods rename customer files before sending them to
Mastercard; some file transfer methods leave the renaming duties to Mastercard systems.
Depending on which file transfer product the customer uses, remapping bulk file names on
the customer’s end of the network before they are sent to Mastercard may be necessary.
Manage Both Project Tracks Simultaneously

Both project paths should receive prompt, simultaneous attention after
commitment to the network configuration phase begins.
Before the network changes are complete, customers must send test files with the
proper file naming structures. Waiting until the network issues are resolved before
focusing on file naming issues will delay the implementation of the new file
transfer mechanism. This delay may increase the amount of time customers spend
duplicating efforts or may leave customers without a file transfer option for a
short time.

Getting Started
Step 4—Establish Parameters

Throughout implementation, much of the communication for starting or changing
a file exchange relationship between Mastercard and a customer is driven by a
parameters spreadsheet. This spreadsheet is passed back and forth between
Mastercard and the customer to exchange critical network parameters for the
network solution in use.
Mastercard support departments operate under a directive to act on incoming
customer parameters immediately. Mastercard encourages customers to complete
their parameter requests in a timely manner. Mutual attention to the parameters
spreadsheet ensures the successful and timely completion of customer network
changes or upgrades.

Proprietary Mastercard Bulk File Transfer Mechanisms
Chapter 4 Proprietary Mastercard Bulk File Transfer

Mechanisms
This section contains additional information about the proprietary Mastercard File
Express Client, File Express Scheduler, and Data Exchange file transfer mechanisms.
Detailed operational information about using a Mastercard interface processor for bulk
file transfer also is provided.
Mastercard File Express Client..................................................................................................... 27

Registering for File Express...................................................................................................... 28
Mastercard File Express Scheduler..............................................................................................28
Mastercard Data Exchange...........................................................................................................30
Mastercard Interface Processors................................................................................................. 31
Generic File Naming on the MIP.............................................................................................. 32
Mastercard Network and Bulk File Transfer on the MIP.................................................... 33
Connectivity.............................................................................................................................33
File Transfers from Mastercard to Customer............................................................. 33
File Transfers to Mastercard...........................................................................................34
Bulk File Identifiers and Types..................................................................................................35
Member Host to MIP to Mastercard Translation Dialogs..................................................36
Successful Transfer Dialog...................................................................................................36
Duplicate Transfer Refused Dialog.....................................................................................38
Error During Transmission Dialog.......................................................................................38
Block Count Discrepancy Dialog.........................................................................................39
Data Fails Edit Dialog...........................................................................................................41
Too Much Data in Last Block Dialog..................................................................................42
Member MIP to Member Host from Mastercard Transaction Dialogs........................... 44
Successful Transfer Dialog...................................................................................................44
Error During Transmission Dialog.......................................................................................46
Block Count Discrepancy Dialog.........................................................................................47
About Record Types Used in Bulk File Transfer Protocol....................................................49
Record Types Used in Bulk File Transfer To Mastercard................................................ 49
Record Types Used in Bulk File Transfer From Mastercard...........................................51
Bulk File Advisements................................................................................................................ 54
201—Bulk File Advisement Solicit Message......................................................................55
202—Bulk File Advisement Response Message................................................................56
198—Data Acknowledgement Message............................................................................59
298—Trailer Message............................................................................................................. 59

Exception Handling.....................................................................................................................60
Operator Console Messages.................................................................................................... 61
COBOL Template........................................................................................................................62
Bulk Data Test Plan.................................................................................................................... 65


File Express Client is a proprietary bulk file transfer application developed by
Mastercard.
Is File Express Client Right for Your Business?

File Express Client is a Java®-based file transfer application with a user-friendly
graphical interface that provides a reliable, secure way for customers to upload
files to Mastercard and download files from Mastercard in an attended mode. File
transfers are secured using Hypertext Transfer Protocol over Secure Sockets Layer
(https) with 128-bit encryption. The Mastercard File Express software package is
provided by Mastercard and must be installed on a customer’s hardware platform.
Getting Started
1-800-999-0363 or 1-636-722-6176
Atlanta: 1-678-459-9000
Chicago: 1-847-375-4000
Purchase: 1-914-249-2000
System Requirements
File Express users must, at a minimum, have the following system requirements to
transfer files.
installed in a custom location. File Express Client and File Express Scheduler are
coded to always use this specific JRE version from that custom location.
Alternatively, Customers may also use an upgraded JRE Version after checking

Registering for File Express
with Support team, if the version they intend to use is supported for the Client
or not.
For More Information

For more information about installing and using File Express Client, see the File
Express Client User Guide.
Registering for File Express

After you have successfully registered for Mastercard Connect or if you are an
existing Mastercard Connect user, follow these steps to order the Mastercard File
Express software.
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 to or search for Mastercard File Express Software.
5. Click Add to Cart.
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.
After the appropriate Security Administrator approves the order, it is routed to
Mastercard for processing. The user will have access to File Express Software
after Mastercard approves the order. Once the order is approved, Mastercard
File Express Software will appear as an entry in the Applications menu on the
Mastercard Connect home page. Users must have a SecurID® to use File
Express Client. If you do not have a SecurID prior to ordering Mastercard File
Express Software, one will be issued as part of the access approval and product
fulfillment process.

File Express Scheduler is a reliable, secure way for customers to exchange files with
Mastercard in an unattended (scheduled) mode.
Is File Express Scheduler Right for Your Business?

File Express Scheduler is a Java®-based application with a user-friendly graphical
interface that allows you to define, maintain, and control a custom file exchange

schedule. Files are transferred with Mastercard on this schedule, with no required
user intervention to initiate each exchange.
Getting Started
1-800-999-0363 or 1-636-722-6176
Atlanta: 1-678-459-9000
Chicago: 1-847-375-4000
Purchase: 1-914-249-2000
System Requirements
File Express users must, at a minimum, have the following system requirements to
transfer files.
installed in a custom location. File Express Client and File Express Scheduler are
coded to always use this specific JRE version from that custom location.
Alternatively, Customers may also use an upgraded JRE Version after checking
with Support team if the version they intend to use is supported for the
Scheduler or not.

For more information about installing and using File Express Scheduler, see the File
Express Scheduler User Guide.


Data Exchange, a browser-based product, provides customers with an easy, safe,
and secure way to exchange files to and from Mastercard.
Is Mastercard Data Exchange Right for Your Business?

Data Exchange is an ideal solution for those customers that prefer to perform
their file transfers manually and have a relatively small number of daily files to
transfer. With Data Exchange, there is no software to install—all you need is a Web
browser.
Getting Started
1-800-999-0363 or 1-636-722-6176
Atlanta: 1-678-459-9000
Chicago: 1-847-375-4000
Purchase: 1-914-249-2000
System Requirements
Data Exchange users must be registered with Mastercard Connect™ and have a
SecurID® token. In addition, Mastercard recommends the following browsers for
optimum performance and optional browser plug-ins.
• Recommended browsers:
– Internet Explorer (version 7, 8, 9, or 10)
– Firefox (version 3.6+)
• Optional browser plug-ins:
– Adobe Flash® 9 or higher
– Adobe Reader® 8 or higher
These plug-ins may be needed when viewing videos or downloading manuals on
Mastercard Connect.

Mastercard Interface Processors

For more information about installing and using the Data Exchange, see the
Mastercard Data Exchange User Guide.
Mastercard Interface Processors

The Mastercard interface processor (MIP) is a hardware bridge between a
customer’s internal business systems and Mastercard systems. The MIP has many
functions—bulk file exchange is one of these functions.
Is a MIP Right for Your Business?

Getting a MIP and Mastercard Network (Mastercard private network) connection
established can be a substantial undertaking. The Data Communications Manual is
an excellent resource for evaluating the resources needed to connect a customer
network with a MIP. This manual contains a checklist of items a customer should
consider before requesting a MIP, including the space requirements needed for the
unit.
If a customer already uses a MIP for authorization or any other function, using it to
send bulk files to Mastercard is an easier process than if the customer is installing
a MIP specifically for this purpose, and will require a much smaller resource
commitment.
Getting Started
1-800-999-0363 or 1-636-722-6176
Atlanta: 1-678-459-9000
Chicago: 1-847-375-4000
Purchase: 1-914-249-2000
The Customer Operations Services team or a designee at the customer’s regional
office will start the paperwork process by initiating a Banknet Service Request
(BSR).

Generic File Naming on the MIP
Mastercard Network Architecture and the Customer Implementation Services

group will work with customers to implement two separate but equally important
tracks:
• Network Architecture handles the customer’s physical circuit connection and
hardware design.
• Customer Implementation Services manages the customer’s internal business
system modifications and related testing.
Before and during a customer’s MIP conversion, the Data Communications Manual
describes the steps and resources required to use a MIP to transfer bulk files.
Security
There are several aspects to the security of MIP file transfer.
Mastercard Network
Using a MIP for file transfer requires customers to subscribe to the Mastercard
Network. Even if customers maintain or participate in another VPN, they must
subscribe to the Mastercard Network. Mastercard Network Architecture supervises
the establishment of a secure circuit with the customer business.
Encryption
The security of the Mastercard private network supersedes the need to send
encrypted data.
Features and Benefits

The file transfer application:
• Identifies the most common types of errors and allows the customer host to
correct and resubmit the data. This process is called “minimum acceptance
editing” and is performed at the point the data is loaded into the MIP.
• Bypasses this process on the MIP if the Member Host Preparation Facility
(MHPF) edited the file, as indicated by the transmission header request.
Generic File Naming on the MIP

Mastercard uses the generic endpoint format to name generic inbound file types.
Bulk Type Endpoint Julian Day Seq #

R y y y E E E E E J J J Q Q
In the example of a generic bulk ID R1119999936501:

• R111 is GCMS IPM Inbound.
• 99999 is a unique endpoint provided by the MIP for the customer’s connection.

Mastercard Network and Bulk File Transfer on the MIP
• 365 is the MIP Julian day.

• 01 is the customer-provided sequence number.
Mastercard Network and Bulk File Transfer on the MIP

The transfer of bulk files on the Mastercard Network links the Mastercard
processing center to customer processing systems and customers to each other
through their Mastercard interface processors (MIPs).
The MIPs store the data that the customer sends and makes the information
available to the customer’s processing system or to Mastercard.
The MIP acts as a staging area for potential multiple transmissions from both the
member host and Central Site. This capability provides flexibility in the retrieval,
delivery, and retransmission of data without operator intervention.
Mastercard can transfer bulk files to (outbound) all customers, a customer group,
or a specific customer. Customers also can send information to Mastercard
(inbound).
Mastercard or a vendor designated by Mastercard installs the MIP components.
NOTE: All bulk file transfer activity must use the TCP/IP protocol between the customer’s
processing system and the MIP.
Connectivity
There are two basic types of file transfers.
• From Mastercard—Bulk files that Mastercard transfers from Mastercard
(outbound) to one or more customers (Type—T)
• To Mastercard—Bulk files that Mastercard transfers from a customer to
Mastercard (inbound) (Type—R)
File Transfers from Mastercard to Customer
This flow describes the connectivity for file transfers from Mastercard to a
customer.

File Transfers to Mastercard
1. The MIP File Transfer System (MFTS) sends a pending file transfer to a single
customer or multiple customers.
2. The Mastercard Network transfers the file to MFTS for scheduling and
transferring to the customer.
3. When the necessary system and network resources are available, the MFTS
transfers the file through the Mastercard Network to the designated member
MIP of group or member MIPs.
4. The member MIP receives the file and the Mastercard Network writes the file to
a MIP storage device.
5. The member host, at its discretion, solicits the file from its attached MIP.
File Transfers to Mastercard
This flow describes the connectivity for file transfers to Mastercard.
1. The member host identifies a file that it wants to send to Mastercard and
sends that file to the Mastercard interface processor (MIP) at the customer’s
site.
2. The member MIP receives the file from the customer’s host and writes the file
to a MIP storage device.
3. The member MIP notifies the MIP File Transfer System (MFTS) at Mastercard
that it has a file it wants to transfer.
4. The MFTS receives the request from the remote member MIP and determines if
necessary system and network resources are available for the requested file
transfer. When adequate resources are available, the MFTS notifies the
member MIP to transfer the file.
5. Upon receiving the request to proceed with the transfer, the member MIP
transfers the file to the MFTS. The MFTS writes the file to a storage device to
await a future processing request.

Bulk File Identifiers and Types
6. Mastercard, at its discretion, solicits the file from the MFTS and the MFTS
transfers the file to the host for processing. This solicitation is based normally
on scheduled processing cycles associated with specific bulk file types.
Bulk File Identifiers and Types

Customers can identify the type of bulk file transfer using these guidelines.
• Size and format of the associated Transaction Identifier field. Mastercard files
usually have 14–byte bulk transaction identifier.
• The first letter of the file name:
– T—Files transferred from Mastercard to customers
– R—Files transferred to Mastercard from customers
• The bulk type is in the first four positions (1–4)
• Zeros are in the next eight positions (5–12)
• A sequence number is in the last two positions (13–14)
• This sequence number (starting at 01) must be incremented for every submittal
that occurs within a 24-hour period (midnight to midnight) local time.
• The MIP will override positions 5–12 with the appropriate values.
The following illustrations show the format of the two different transaction
identifiers.
14–Byte Bulk File Transaction Identifier (From Mastercard—Type T)

T 1 1 2 0 0 1 5 7 1 7 2 0 1
14-Byte Bulk File Transaction Identifier (To Mastercard—Type R)

R 1 1 1 9 9 9 9 9 1 7 2 0 1
The following illustrations show the message and data flow between the MIP and
the member host during various file transfer scenarios. In each example, the
following conventions are used.
When you see... Description

Here is a R11112210651 file. This normal text font contains a description of what this
step means.

Member Host to MIP to Mastercard Translation Dialogs
When you see... Description

004 File Header (1) Text in italic shows the protocol record types that are sent.
The number in parentheses (in this example, 1) identifies
the record type.
Line driver to line driver This underlined text shows that a communications event
acknowledgement takes place at the data link level.
File Status = F This icon and the accompanying text show the status of
(In-Progress the file displayed in the file system utility described in the
from Host) Mastercard Interface Processor Manual.
ID 05/28/97 This icon and the accompanying text show the operator
05:49:33 9272I message that displays on the MIP console. The fields in the
FtFrmMbr FILE operator message are: MIP ID (in this example, ID), date
STARTED FOR and time, message number and severity code (9272I), the
R11112210651 program that originated the operator message
Q447 (FtFrmMbr), and the text of the message.
Member Host to MIP to Mastercard Translation Dialogs

There are several file transfer scenarios that illustrate the message and data flow
between the member host to MIP to Mastercard.
Successful Transfer Dialog

This illustration shows a member host to MIP to Mastercard successful transfer
dialog.
Member Host MIP

Here is a R11112210651 file.
004 “To Mastercard” File Header (1)
[Do I have room?]

[Is it a duplicate?]
[Is this member host edited?]
Yes, member, I can take your

R11112210651 file.
998 Header Acknowledgement (2A)
File Status = F (In-Progress

from Host)
ID 05/28/97 05:49:33 9272I

FtFrmMbr FILE STARTED
FOR R11112210651 Q447

Member Host MIP

Here comes some data.
Data Record (3) #1

Thank you. Do you have more data?
Line driver to line driver
acknowledgement
Yes, I do. Here it is.

Data Record (3) #2

acknowledgement

Data Record (3) #3

acknowledgement
No more data. Did you receive 4 blocks?

Note: The three data records and a 998
trailer are included in the count.
998 Trailer (4)
Yes, I received 4 blocks.

998 Trailer Acknowledgement (5A)
File Status = S (Staged)
ID 05/28/97 05:50:32 9271I

FtFrmMbr FILE STAGED
FOR R11112210651 Q447
[Notify Mastercard Scheduler
R11112210651 is available for
transfer.]

Duplicate Transfer Refused Dialog
Duplicate Transfer Refused Dialog

This illustration shows a member host to MIP to Mastercard duplicate transfer
refused dialog.
Member Host MIP

[Do I have room?]

No, member, I can NOT take your

R11112210651 file.
998 Refusal (2B)
ID 05/28/97 05:50:32
9288W FtFrmMbr
DUPLICATE FT FILE
NAME R11112210651
Error During Transmission Dialog

This illustration shows a member host to MIP to Mastercard error during
transmission dialog.
Member Host MIP

[Do I have room?]


R11112210651 file.

from Host)
ID 05/28/97 05:49:33 9272I

FOR R11112210651 Q447

Block Count Discrepancy Dialog
Member Host MIP

Data Record (3) #1

acknowledgement

Data Record (3) #2

acknowledgement

Data Record (3) #3
Error condition detected. Abort the

transfer.
998 Transfer Abort (2B) with the first
message mentioned below
A message describing the

error, plus:
ID 05/28/97 05:49:33 9264I
FtFrmMbr FILE FAILED FOR
R11112210651 Q447

This illustration shows a member host to MIP to Mastercard block count
discrepancy dialog.
Member Host MIP

[Do I have room?]


Member Host MIP

R11112210651 file.

from Host)
ID 05/28/97 05:49:33 9272I

FOR R11112210651 Q447
Data Record (3) #1

acknowledgement

Data Record (3) #2

acknowledgement

Data Record (3) #3

acknowledgement

998 Trailer (4)
No, I received 3 blocks.

998 Trailer Error (5B)
File deleted

Data Fails Edit Dialog
Member Host MIP

ID 05/28/97 05:49:33 9656F
FtFrmMbr TRAILER 4 NE
RECEIVED 3
Data Fails Edit Dialog

This illustration shows a member host to MIP to Mastercard data fails edit dialog.
Member Host MIP

[Do I have room?]


R11112210651 file.

from Host)
ID 05/28/97 05:49:33 9272I

FOR R11112210651 Q447
Data Record (3) #1

acknowledgement

Data Record (3) #2
[Edit error detected within this block

of data.]
acknowledgement

Too Much Data in Last Block Dialog
Member Host MIP

Data Record (3) #3

acknowledgement

998 Trailer
Yes, I received 4 blocks.

998 Trailer Acknowledgement (5B)
File Status = E (Edit Pended)

problem, for example:
ID 05/28/97 05:49:33 9657I
FtFrmMbr SEQ/INVAL
TRANSACTION ERROR
R11112210651
plus
ID 05/28/97 05:49:33 9270I
FtFrmMbr STATUS SET TO
PENDED R11112210651

This illustration shows a member host to MIP to Mastercard dialog when there is
too much data in the last block.
Member Host MIP

[Do I have room?]


Member Host MIP

R11112210651 file.

from Host)
ID 05/28/97 05:49:33 9272I

FOR R11112210651 Q447
Data Record (3) #1

acknowledgement

Data Record (3) #2

acknowledgement

Data Record (3) #3, where Data Record
#3 contains an IPM trailer (691) not
followed by a 601 IPM header or with
data after the end of file data records.
998 Trailer Acknowledgement (5B)
File Status = E (Edit Pended)

Member MIP to Member Host from Mastercard Transaction Dialogs
Member Host MIP

problem, for example:
ID 05/28/97 05:49:33 9604F
FtFrmMbr 601 HEADER REC
NOT FOUND IN
R11112210651
plus
ID 05/28/97 05:49:33 9264I
FtFrmMbr FILE FAILED FOR
R11112210651 Q 447
Member MIP to Member Host from Mastercard Transaction Dialogs

There are several file transfer scenarios that illustrate the message and data flow
between the customer’s MIP (member MIP) to member host from Mastercard.

This illustration shows a member MIP to member host from Mastercard successful
transfer dialog.
Member Host MIP

Do you have a T112 file for me?
101 File Request Header (1)
[Do I have a file that fulfills the

request?]
[Is this endpoint authorized on this
connection?]
Here is a T1120015712203 file. It is 3

blocks in size.
004 “From Mastercard” File Header (2)
File Status = T (In-Progress

to Host)
ID 05/28/97 05:49:33 9272I

FtToMbr FILE STARTED FOR
T1120015712203 Q447

Member Host MIP

Data Record (3) #1

acknowledgement

Data Record (3) #2

acknowledgement

Data Record (3) #3

acknowledgement
No more data. Did you receive 4

blocks?
Note: The three data records and a
998 trailer are included in the count.
998 Trailer (4A)
Yes, I received 4 blocks. You can delete

the file.
999 File Purge Request (5)
File Status = P (Purgeable)
ID 05/28/97 05:50:32 9271I

FtFrmMbr FILE STAGED
FOR R11112210651 Q447
O.K., the file is marked for deletion.
998 Purge Acknowledgement (6A)


This illustration shows a member MIP to member host from Mastercard error
during transmission dialog.
Member Host MIP


request?]
connection?]

blocks in size.

to Host)
ID 05/28/97 05:49:33 9272I

T1120015712203 Q447
Data Record (3) #1

acknowledgement

Data Record (3) #2
Error condition detected. Abort the

transfer.
998 Error Trailer (4B)

Member Host MIP

A message showing what
went wrong on the MIP (the
message is included in the
plus
ID 05/28/97 05:50:01 9264I
FtToMbr FILE FAILED FOR
T1120015712203 Q447

This illustration shows a member MIP to member host from Mastercard block
count discrepancy dialog.
Member Host MIP


request?]
connection?]

blocks in size.

to Host)
ID 05/28/97 05:49:33 9272I

T1120015712203 Q447
Data Record (3) #1

acknowledgement

Member Host MIP

Data Record (3) #2

acknowledgement

Data Record (3) #3

acknowledgement
No more data. Did you receive 4

blocks?
Note: The three data records and a
998 trailer are included in the count.
998 Trailer (4A)
No, I received 3 blocks.

ID 05/28/97 05:49:33 9263I

FtToMbr FILE DENIED FOR
T1120015712203
Note: The MIP does not
know why the member host
is denying the file (there
could also have been an
internal error on the host),
and so this message is
different from the message
generated when the MIP
detects a block count
discrepancy.

About Record Types Used in Bulk File Transfer Protocol
About Record Types Used in Bulk File Transfer Protocol

There are specific file transfer protocols for record types used in bulk file transfers.
Record Types Used in Bulk File Transfer To Mastercard

The following record types are used for bulk file transfers to Mastercard from the
member host to the MIP.
Host-to-MIP—004 ”To Mastercard” File Header (1)
Field Name Position Length Format Comments and Values

Request Code 1–3 3 AN Constant—004
(Send “To Mastercard” data
to the MIP)
Record Type 4–5 2 AN Constant—01

(Unless the file is
compressed)
MIP File Name at Unique

Mastercard
Transmission 6 1 A Constant—R
Type Prefix
Transmission 7–9 3 AN Note: Valid Transmission
Type Types have been defined
earlier in this chapter.
Varies 10–19 10 AN Note: Transmission Types
depending on details have been defined
Transmission earlier in this chapter.
Type
Filler 20–36 17 AN
Reserved for future 37–40 4 B Constant—Zeros
use
Future capability to send file
size to the MIP
Reserved for future 41–44 4 B Constant—Zeros

use
Sequence number for future
restart capability

Record Types Used in Bulk File Transfer To Mastercard
MIP-to-Host—998 Header Acknowledgement (2A)

Request Type 4–5 2 AN Constant—01 (Unless compressed)
Return Code 6–7 2 AN Constant—00 (Good)
Error Message 8–11 160 B Constant—Zero
MIP-to-Host—998 Error Record (Refusal or Transfer Abort) (2B)

Return Code 6–7 2 AN Constant—01 (Error)
Error Message 8–(n+7) 160 AN Same as message displayed on
member MIP console
Host-to-MIP—Data Record (3)

Direction 1 1 A Constant—R
Indicator
Bulk File Data 2–(n+1) n B Maximum of 1014 bytes
Host-to-MIP—998 Trailer (4)

Return Code 6–7 2 AN Constant—00
Number of 8–11 4 B Value is in most significant bit to least
Blocks significant bit order and represents the
number of data record blocks sent to
the MIP, plus this trailer.

Record Types Used in Bulk File Transfer From Mastercard
MIP-to-Host—998 Trailer Acknowledgement (5A)

Error Message 8–11 160 B Constant—Zero
MIP-to-Host—998 Trailer Error Record (5B)

member MIP console

The following record types are used for bulk file transfers from Mastercard from
the member host to the MIP.
Host-to-MIP—101 File Request Header (1)

(Request “From Mastercard” file)

(Unless compressed)
Transmission ID


MIP File 6–9 4 AN Position 1 Constant—T
Name at
Positions 2–4 Transmission Type
Mastercard
These four bytes are required. A
generic request can be made by
supplying these four bytes and
filling the rest of the Transmission
ID with blanks (hex 40) or nulls (hex
00).
End Point 10–14 5 AN

Number
Julian Day 15–17 3 AN DDD format
Sequence 18–19 2 AN
Number
MIP-to-Host—004 “From Mastercard” File Header (2)

(Specific file detail header)

(Unless compressed)
MIP file name Unique for the data staged

Transmissi 6 1 A Constant—T
on Type
Prefix
Transmissi 7–9 3 AN The current bulk file list is available
on Type in the Member Profile Extract
(T007) file.
End Point 10–14 5 AN
Number
Julian Day 15–17 3 AN DDD format
Sequence 18–19 2 AN
Number
Reserved for 20–36 17 B Constant—Zero
future use


Number of 37–40 4 B Size of the file as staged on the
Blocks MIP. The size value is in most
significant bit to least significant
bit order.
MIP-to-Host—Data Record (3)

Direction 1 1 A Constant—T
Indicator
MIP Data String 2–(n+1) n B Maximum of 1014 bytes
MIP to Host—998 Trailer (4A)

Number of 8–11 4 B Value is in most significant bit to
Blocks least significant bit order and
represents the number of data
record blocks sent to the MIP, plus
this trailer.
MIP-to-Host—998 Error Trailer (Used for Transfer Abort) (4B)

member MIP printer

Bulk File Advisements
Host-to-MIP—999 File Purge (5A)

Transmission ID 8–21 14 AN
Host-to-MIP—998 Error Trailer (Used for Transfer Abort) (5B)

MIP-to-Host—998 Purge Acknowledgement (6A)

Error Message 8–(n+7) 160 AN Blank (No message)
Bulk File Advisements

Member host processing schedules rely on the timely delivery of bulk files from the
member MIP; therefore, an automated process is needed for the host to know that
bulk files have arrived at the MIP and are ready for delivery to the host.
Mastercard Bulk File Advisement routines satisfy this requirement. The Bulk File
Advisement routines enable software on the host to query the attached MIP for
the presence of bulk files. A host query to the MIP will return a list of bulk files
currently available on the MIP along with size and file status information. From
this list, the host software can make decisions about scheduling and processing
bulk files found on this list.

201—Bulk File Advisement Solicit Message
Advisement Protocol, Messages, and Data Structure

The following diagram illustrates the messages used to establish and maintain
communication between the member host and its MIP during a bulk file
advisement process.
The following information provides more details about each message, purpose, and
format:
• 201—Bulk File Advisement Solicit Message
• 202—Bulk File Advisement Response Message
• 198—Data Acknowledgement Message
• 298—Trailer Message
201—Bulk File Advisement Solicit Message

The following table provides the details about the 201—Bulk File Advisement Solicit
message.
Sent by: Member host

Sent to: MIP
Purpose: The host requests that the MIP begin processing a bulk file advisement
request
Data sent: None
201—Field Name Position Length Format Comments and Values

Transaction Code 1–3 3 AN Constant—201
Identifier
Process Code Identifier 4–5 2 AN Constant—00

202—Bulk File Advisement Response Message

Status 6 1 AN Specific File Status to
participate in advisement
process. (Blank indicates
all statuses.)
Bulk ID 7–38 32 AN Specific Bulk ID to
participate in advisement
process. (Blank indicates
all bulk IDs.)

The following table provides the details about the 202—Bulk File Advisement
Response message.
Sent by: MIP

Sent to: Member host
Purpose: Presents a bulk file advisement to the member host
Data sent: Bulk file advisement packet

Identifier
Process Code 4–5 2 AN Constant—00
Identifier
Reference 6–11 6 AN Bulk advisement session number.
Number This number should be used in the
associated 198 and 298 messages.
Bulk ID 12–43 32 AN
File Status 44 1 AN Bulk File Status:
A = File is being read to update
MIP database
D = File is complete to
destination, delivered
E = File is pending with edit
errors
F = File in progress from host
I = Database session initiated


L = Log file in progress
N = File in progress through
network
P = File use complete; can
delete (purgeable)
S = File is staged and available
T = File in progress to host
U = File transfer interrupted
X = File being processed by
engine
W= File is being written for log
Destination 45–51 7 AN File destination endpoint
Endpoint
Destination Box 52–54 3 AN Destination MIP ID
ID
Origination 55–61 7 AN File origination endpoint
Endpoint
Origination Box 62–64 3 AN Originating MIP ID
ID
Source of this 65 1 AN H = Origin of file was member
File host
N = Origin of file was network
D = Origin of file was a
database
L = Origin of file was a logger
I = Origin of file was a PCI
C = Origin of file was a PCC
S = Origin of file was a MIP
Current Owner of 66 1 AN L = Filed owner by logger
File
M = Member side file transfer
N = Network side file transfer
S = File being processed after
receipt
File Dimensions All values are in most significant
for Sender bit to least significant bit order


Origination 67–70 4 B Number of blocks
Blocks
Origination 71–74 4 B Number of records
Records
Origination 75–78 4 B Number of bytes
Bytes
Origination 79–80 2 B Block size
Block Size
Origination 81–82 2 B Record size
Record Size
File Dimensions for Receiver
Destination 83–86 4 B Number of blocks
Blocks
Destination 87–90 4 B Number of records
Records
Destination 91–94 4 B Number of bytes
Bytes
Destination 95–96 2 B Block size
Block Size
Destination 97–98 2 B Record size
Record Size
Blocking Flag 99 1 AN Record blocking format flag
N = No blocking
F = Fixed blocking
T = Table lookup blocking
G = General blocking (IP)
H = General blocking (HPF)
Deblocking Flag 100 1 AN Record deblocking format flag
N = No blocking
F = Fixed blocking
T = Table lookup blocking
G = General blocking (IP)
H = General blocking (HPF)
Date/Time Stamps

198—Data Acknowledgement Message

Creation Day 101–103 3 AN DDD (Julian day file was created)
Expire Year 104–107 4 AN YYYY (Year this file expires)
Expire Day 108–110 3 AN DDD (Julian day this file expires)
Receive Day 111–113 3 AN DDD (Julian day this file was
received from customer or
network)
Receive Time 114–119 6 AN HHMMSS (Time file was received)
Send Day 120–122 3 AN DDD (Julian day file was sent to
customer or network)
Send Time 123–128 6 AN HHMMSS (Time file was sent)
198—Data Acknowledgement Message

The following table provides the details about the 198—Data Acknowledgement
message.
Sent by: Member host

Sent to: MIP
Purpose: Acknowledges receipt of data
Data sent: None. This is a flow control transaction. The Reference Number field
contains the same session reference number that was passed with the 202
data packet.

Identifier
Return Code (set by 6-7 2 AN 00 = OK11 = Failure
sender)
Reference Number 8-13 6 AN Session reference number
from 202 packet
298—Trailer Message
The following table provides the details about the 298—Trailer message.
Sent by: MIP

Exception Handling
Sent to: Member host

Purpose: Notifies the sender or receiver that the session is complete and no more data
will follow.
Data sent: If the message is sent by the MIP to the host, it will contain the count of bulk
file advisements sent to the host. If the message is sent by the host to the
MIP, it will contain the number of bulk file advisements received. This
message may also be sent by the host to the MIP to terminate a bulk file
advisement session before all the data has been sent by the MIP.

Identifier
Return Code (set by 6–7 2 AN 00 = OK11 = Failure
sender)
Reference Number 8–13 6 AN Session reference number
from 202 packet
Bulk File Advisements 14–17 4 B Number of bulk file
Sent advisements sent
Exception Handling
The Bulk File Advisement function must be capable of recognizing and handling
any exceptions in a consistent manner and report them to the member host.
The following table illustrates exceptional conditions that must be recognized by
the MIP software.
Exception Condition MIP Response

201 message is corrupt (for example, message No session established.
header information is missing or invalid, data
length is invalid).
No bulk files located which the request 298 message presented to member host,
specified in the 201. which contains a file count of zero.
Internal error occurs in bulk file advisement Session is dismantled. (2980001 message
process. sent to host indicating transmission
error.)
Communications between member host and Session is dismantled. No response sent
MIP are lost, as indicated by session clear to member host.
message sent by member session manager.

Operator Console Messages
Exception Condition MIP Response

298 end of transmission sent by member host Session is dismantled. No response sent
in response to data packet. to member host.
Unknown or corrupted message arrives. Message arrival is announced on operator
console, and message is discarded. No
existing sessions are interrupted or
dismantled.
Operator Console Messages

Bulk file advisement process provides an activity log on the member MIP operator
console.
Normal messages displayed are:
• 283I BULK ADVISEMENT STARTED
• 284I BULK ADVISEMENT DONE [nn] FILES ADVISED
where “nn” is equal to the number of files sent during the bulk file advisement.

COBOL Template
COBOL Template
The following COBOL template provides the data mapping of the bulk advisement
processing messages.

COBOL Template

COBOL Template

Bulk Data Test Plan
Bulk Data Test Plan

Mastercard has a test procedure to determine if a customer has in place the
proper procedures for bulk file transfers.
The Mastercard Customer Implementation Services specialist contacts each
customer to set up testing schedules. The test includes tasks that range from
operational testing of the member MIP to production cutover.
NOTE: Successful completion of this test is required before a customer can be certified for
production processing.
For more information about test procedures, contact your Customer

Implementation Services specialist.

Third-Party File Transfer Mechanisms and Solutions
Chapter 5 Third-Party File Transfer Mechanisms and

Solutions
Mastercard supports several bulk file transfer solutions sold by third-party vendors. A
third-party vendor may represent the best file transfer option for a customer’s business
model.
File Transfers by Third Party Solutions....................................................................................... 67

IBM – Sterling Connect:Direct ..................................................................................................... 67
Is Sterling Connect:Direct Right for Your Business?............................................................67
Getting Started with Sterling Connect:Direct.....................................................................68
Sterling Connect:Direct Security Profile................................................................................68
Sterling Connect:Direct Configuration.................................................................................. 69
Secure Shell File Transfer Protocol (SFTP)................................................................................ 69

File Transfers by Third Party Solutions
File Transfers by Third Party Solutions

The Mastercard interface processor (MIP) relies on a multi-layered secure business
network designed and maintained end-to-end by Mastercard. Mastercard Data
Exchange leverages the security of a customer’s Mastercard Connect connection
to exchange files with Mastercard, while Mastercard File Express Client and
Mastercard File Express Scheduler have their own connection (gateway).
The third-party solutions described in this chapter may use one or more of the
following connection types for file exchange:
• Mastercard Network:
– Security router (proprietary secure router)
– Mastercard interface processor (proprietary secure hardware)
• Internet
• Dial-up
Mastercard Network
The Mastercard Network is the telecommunications and data transport
mechanism that facilitates the routing and processing of financial transactions.
The network links all Mastercard customers and data processing centers into a
single online financial network.

IBM® Sterling Connect:Direct® is the industry standard for business-to-business file
exchange.
Is Sterling Connect:Direct Right for Your Business?

Mastercard supports the use of the Sterling Connect:Direct file transfer
mechanism for the transfer of bulk files for processing.
Sterling Connect:Direct is a complete file exchange and electronic commerce
solution that will empower a customer’s business to leverage virtually all of the
electronic advices currently in use. Sterling Connect:Direct also is a solution that
requires a modest level of expertise and commitment from its users. As with any
software package designed for power users, if a member chooses Sterling
Connect:Direct, it will have to designate and train specialists to integrate the
solution into business systems and manage day-to-day usage issues.
Sterling Commerce offers product support services for its customers, as well as a
host of invaluable consulting, training, and educational opportunities.
Mastercard specialists will work closely with customers to establish a secure file
exchange connection between customers and Mastercard. Several levels of support
teams will be available to get the customer’s Sterling Connect:Direct server

Getting Started with Sterling Connect:Direct
running smoothly. However, after six months in production bulk file exchange,
Mastercard expects the following of its customers:
• Customers have cultivated internal troubleshooting specialists with Sterling
Connect:Direct knowledge and expertise.
• Customers must identify these specialists to Mastercard as primary points-of-
contact.
• Customers should use Sterling Commerce as the first stop for support issues
that do not directly affect member file exchange with Mastercard.
Getting Started with Sterling Connect:Direct

If a decision is made to use Sterling Connect:Direct as your third-party file transfer
mechanism, follow these guidelines.
If a member decides to purchase Sterling Connect:Direct, or if a member
organization is already using Sterling Connect:Direct for communication with
business partners and would like to switch the file transfer mechanism for one or
more member endpoints to Sterling Connect:Direct, the member should first call
the Customer Operations Services team.
There is system configuration work that should be done up front by Mastercard
and the customer’s system administrator. The Customer Operations Services team
will initiate any Mastercard paperwork and assemble a Mastercard support team.
A Mastercard CTC Administration team member will contact the customer’s
system administrator and work closely with the member and Sterling Commerce
to ensure a successful transition to Sterling Connect:Direct.
The customer’s network architecture management and designated Sterling
Connect:Direct specialist are expected to participate in a conference call with
representatives from various Mastercard departments who will guide member
representatives through all of the required setup and testing.
Customers must provide Mastercard with a naming convention for the bulk file
types to be exchanged. Mastercard will return a spreadsheet cross-referencing the
customer’s file naming schema with the file names required by Mastercard. The
customer’s Sterling Connect:Direct configuration names the files to Mastercard
file naming standards before sending files to Mastercard.
Following the initial effort required to get the Sterling Connect:Direct file transfer
mechanism exchanging files with Mastercard, these connections tend to be
trouble-free, low maintenance, and reliable.
Sterling Connect:Direct Security Profile

There are many aspects to the security profile of Sterling Connect:Direct.
Mastercard Network
Use of Sterling Connect:Direct requires most customers to subscribe to the
Mastercard Network. Even if customers maintain or participate in another VPN,

Sterling Connect:Direct Configuration
they will need to subscribe to the Mastercard Network. The CTC Administration
team will supervise the establishment of a secure circuit between customers’
businesses and Mastercard.
Encryption
The security of the Mastercard Network supersedes the need to send encrypted
data.
User ID Authentication
Mastercard validates and authenticates a user using one of two methods:
• When sending files to Mastercard, the required method is to use the Secure
Point-of-Entry option within Sterling Connect:Direct. Using this method,
customers provide Mastercard with user IDs of their choice. Mastercard then
cross-references the user IDs against the specific Sterling Connect:Direct node
used by the customer. This prevents any portability of the access privileges
outside of the customer’s Sterling Connect:Direct environment and minimizes
the security risk for both Mastercard and customers.
• When sending files to customers, Mastercard can support either Secure Point-
of-Entry or the user ID and password method (using ACF2). As customers
upgrade and change their systems, Mastercard will help them migrate to the
Secure Point-of-Entry method.
The Mastercard CTC Administration team will help customers set up the most
secure user ID authentication method available for their business models.
Sterling Connect:Direct Configuration

A Sterling Connect:Direct interface (player) only communicates and exchanges
files with another Sterling Connect:Direct player. Although the network schematic
for Sterling Connect:Direct is a simple one, configuring a customer’s business
system to interact with their Sterling Connect:Direct player requires expertise.
Secure Shell File Transfer Protocol (SFTP)

Secure Shell (SSH) File Transfer Protocol (SFTP) is a safe, secure, and easy-to-use
file transfer option for customers and business partners. SFTP is supported over
Internet as well as over Mastercard Network.
SFTP runs over the SSH protocol and supports the full security and authentication
functionality of SSH. It protects against password sniffing and man-in-the-middle
attacks, and also the integrity of the data using encryption and cryptographic
hash functions, and authenticates both the server and the user.
NOTE: Secure Shell Protocol (see RFC 4251, RFC 4252, RFC 4253 and RFC 4254).

Secure Shell File Transfer Protocol (SFTP)
SFTP Client Softwares

Mastercard does not endorse or certify compatibility with specific software clients.
Customers must research available options and procure client software that
provides the operational features required for their environment.

Global File Transfer Endpoint and Bulk File Naming Convention
Chapter 6 Global File Transfer Endpoint and Bulk File

Naming Convention
This section provides information about where and how file transfer mechanisms rename
files to the Global File Transfer standard naming convention used by Mastercard.
EndPoints...........................................................................................................................................72
Bulk Types and Bulk Files................................................................................................................72
File Naming Convention in the Mastercard Repository.......................................................... 74

EndPoints
EndPoints
An endpoint is a value that represents a logical address. All Mastercard customers
using file transfer are assigned at least one endpoint.
On the Mastercard side, the endpoint will be linked to the customer’s Endpoint File
Profile; this contains all the details needed by Mastercard to help ensure that the
correct files are delivered successfully to the intended location via the chosen file
transfer method.
All file transfer methods use endpoints; however, the Sterling Connect:Direct also
use additional identifiers: nodes and site names respectively. These are references
to the servers at the customer’s site and at Mastercard.
• Endpoints are comprised of seven digits.
• In conversations with the customer, the endpoint E0023456 is referred to as
endpoint 23456. As we will see later, the full endpoint reference is used when
naming files.
• Customers must provide their chosen file transfer method and ICA (Interbank
Card Association) number (if assigned) when requesting new endpoint setups.
• Customers may request multiple endpoints for a variety of reasons (for
example, for use with different file transfer methods, or to distribute files to
different locations).
• An endpoint cannot be linked to more than one customer.
Bulk Types and Bulk Files

A bulk type is the term used by Mastercard to describe file types (files with similar
data content supporting a product or service).
Mastercard must keep track of all incoming files from more than 40,000 customers
and business partners. To ensure the guaranteed delivery and timely processing of
so many files, Mastercard must have a mechanism in place that uniquely identifies
to Mastercard where files originate, what kind of bulk file type they represent, and
which file transfer method was used to get them to Mastercard.
Mastercard requires that every incoming file follow a certain naming convention,
which may differ slightly between file transfer mechanisms, but it must maintain a
certain standard of uniqueness. For inbound files to Mastercard, the concept of
bulk type (file type) is the same for all file transfer mechanisms, and it is critical for
Mastercard to process files appropriately.
A bulk file refers to a file type that belongs to a particular application. Mastercard
has thousands of bulk types supporting multiple programs and services, named
according to the following convention:

Bulk Types and Bulk Files
• A three-digit code identifies the bulk type

• The letter R or T, indicating if the file is inbound, being received (R) by
Mastercard, or outbound, being transmitted (T) by Mastercard. Examples:
R111-Clearing Inbound Data (Received), T112-Clearing Outbound Data
(Transmitted).
The following diagram shows examples of different bulk types flowing between the
customer and Mastercard. This is just a small subset of the many bulk types used.
There are over 20 bulk types associated with the Clearing system alone.
Your Mastercard Implementation Manager provides customers with the most

current information on bulk types and bulk files, and will help identify the types
needed to support your processing.
Features
• There is no “one size fits all” list of bulk types that is used by Mastercard
customers; only the bulk files that support their individual processing needs are
assigned.
• Customers may need new bulk types if they are adding a new product or service.
Bulk types may also change due to Mastercard product upgrades or service
enhancements. Mastercard communicates these additions and changes to
customers via bulletins and release documentation.
• A system or service (for example, Clearing) can have more than one bulk type.
• Separate bulk types are created for test and production files; the same format
is used for both.
• The Member Profile Extract (contained in bulk type T007) has the current listing
of all bulk types.For customers wanting more information on bulk files
supporting specific products and services, consult the related manual. A few
examples are provided a:.
– Clearing: GCMS Reference Manual
– MATCH: MATCH User Manual
– SAFE: SAFE Products User Guide
About Bulk File Types:

File Naming Convention in the Mastercard Repository
The bulk file types are subject to change as Mastercard adds or phases out
features in response to new business and technological conditions. The most
current listing of the bulk file types appears daily in the Member Profile Extract
(T007) file.
For questions about bulk file types, contact the Customer Operations Services
team

A standard file naming convention is used for file processing by Mastercard Global
File Transfer System (GFT). This standard makes it very clear what is being
transmitted, and also assists with troubleshooting.
The file name is made up of various components, each providing information about
the file that is being transmitted, as shown below:
Files received (R) by Mastercard

Customers sending files to Mastercard using Sterling Connect:Direct file transfer
method must use the file naming convention shown above. In general, Mastercard
recommends that customers do not include spaces or special characters in the
names of files they send to Mastercard. It also suggests that customers include
the following values in the names of files they send to Mastercard, which will help
when troubleshooting: file creation date, ICA number (if assigned), bulk type, and
endpoint.
The Mastercard Global File Transfer Management System has an established bulk
file naming convention.
When retrieving files from Mastercard, you will see this naming convention. The
following table identifies the parts of the file name and provides a brief description
of each part.

Files transmitted (T) by Mastercard

Customers receiving files from Mastercard via Sterling Connect:Direct file transfer
method can expect that by default, the files will reflect the naming convention
displayed above. However, if Sterling Connect:Direct customers prefer to receive a
different file name, they can indicate that to Mastercard.
The GFT Management System has an established bulk file naming convention.
When retrieving files from Mastercard, you will see this naming convention. The
following table identifies the parts of the file name and provides a brief description
of each part. Here is an example:
MCI.AR.T112.M.E0090000.D040928.T095115.A001
Part Description
MCI High-level qualifier.
• MCI—Designation for the Mastercard production environment, which
some test files may use
• YTF—Designation for the Mastercard test facility environment
AR A two-character constant that identifies the Mastercard Global File

Transfer Management System.
T112 Bulk type. Bulk types (sometimes referred to as bulk file types or file
types) allow Mastercard to process files appropriately.
The first position of the bulk type indicates the direction that the file is
moving (from a Mastercard perspective), for example:
• R indicates that the file is being Received from the Customer into
Mastercard.
• T indicates that the file is being Transmitted to the Customer from
Mastercard.
The last three positions identify a specific bulk type. These three
positions can be any combination of the alphanumeric values 0–9 and
A–Z. The number 112, in this example, indicates a Global Clearing
Management System data file.
M File transfer mechanism. In this example, M indicates Mastercard File

Express.
E0090000 Endpoint number. An E (constant) followed by seven numeric digits.
Within the Mastercard Global File Transfer Management System, the
endpoint represents a destination (address) in routing bulk files.
D040928 Date the file was created. A D (constant), followed by the year, month,
and day the file was created—DYYMMDD.
T095115 Time the file was created. A T (constant), followed by the time of day in
24-hour format. Time—HHMMSS.

Part Description
A001 Sequence number. The sequence number is used to ensure unique file
names.
Bulk type, endpoint, date, and time are relevant file name elements for the user.
The date and time is when the data file was created in the Mastercard Global File
Transfer Management System.

Mastercard Processing Environments
Chapter 7 Mastercard Processing Environments

This section provides a high-level explanation of the various production and test
environments involved in Mastercard file exchange.
Production Environment.................................................................................................................78
Mastercard Test Facility.................................................................................................................78

Mastercard Processing Environments
Production Environment
Production Environment
The production environment allows you to exchange production files or retrieve
archived files from Mastercard.
The file profiles established for your user ID determine which production files are
available to you. Your file profiles are set up to include the endpoints and bulk
types you need to access. After your file profiles have been established by
Mastercard, you can exchange files with Mastercard production applications, such
as the Account Management and clearing systems, and Stand-In processing.
Bulk files that begin with “MCI” are designated for the Mastercard production
environment. Mastercard guarantees that all incoming bulk files with a file name
beginning with MCI will get prompt delivery to the business area and systems
noted within the file name. Only bulk files with active, legitimate processing needs
should be sent to the production environment.
Mastercard Test Facility

The Mastercard Test Facility is the high-level test environment for use by all
customers.
The test environment allows you to exchange test files or retrieve archived test
files from the Mastercard test facility. The file profiles established for your user ID
determine which test files are available to you. The test environment allows you to
test new application software releases in coordination with a Member
Implementation group.
NOTE: YTF is the designation for the Mastercard Test Facility environment. Customers
using Connect:Direct will need to specify the YTF environment qualifier on bulk file names
destined for the Mastercard Test Facility.

Recovery and Resumption of Service
Appendix A Recovery and Resumption of Service

This section explains the business process for resuming file transfers in case of MIP failure
or a service outage in your central data center.
Disruption and Business Resumption Service............................................................................80

GCMS/Non-GCMS Recovery........................................................................................................ 80
Business Recovery Options............................................................................................................ 80
Business Resumption Testing Process.........................................................................................80

Disruption and Business Resumption Service
Disruption and Business Resumption Service

There are two possible scenarios that can explain a disruption of service.
• The Mastercard interface processor (MIP) could fail or a customer’s connection
to the Mastercard Network could go down.
• The customer’s data center could fail. In this case, customers should transfer
their credit and debit card processing to another location, either a service
provider or their own hot backup sites. Business Resumption Services addresses
the re-establishment of connectivity to the Mastercard Network after the
member has relocated its processing operations.
GCMS/Non-GCMS Recovery
Settlement and clearing backup is available online if disaster recovery operations
are expected to continue for an extended period from an alternate site that has a
Mastercard disaster recovery processing configuration in place.
Business Recovery Options

Customers that use tape media as part of their disaster recovery exercise are
required to use an alternate business recovery method.
Mastercard no longer uses magnetic tape as a media type for data output when
distributing files to customers and business partners. If magnetic tape is part of
your institution’s disaster recovery plan, you will need to determine an alternate
type of media, and then contact your Customer Implementation Services specialist
to request testing and implementation. In addition, Mastercard discourages
customers from sending magnetic tape as a method of file transfer.
For Connect:Direct users, you should manage your file transfers from your
alternate site or specific node.
Business Resumption Testing Process

The Business Resumption testing process consists of two phases of testing.
Customers must complete two phases of testing after choosing to participate in
the Business Resumption Service:
• Phase 1—The Business Resumption Service is tested after the initial installation
• Phase 2—The member should retest yearly to ensure disaster recovery support is
still operable.

Business Resumption Testing Process
Initial Testing—Phase 1
The first phase of testing varies depending on the type of testing. For information
about the business resumption testing process, contact Customer Implementation
Services.
For information about:
• Sending batch file maintenance requests via bulk file or Mastercard File Express,
see the Account Management System User Manual.
• Sending SAFE—Monthly Data R847 bulk files, see the Security Rules and
Procedures manual for specifications.
• Sending R311 bulk files via Mastercard File Express, see the Mastercard File
Express Client User Guide.
Testing Complete—Phase 2
After the completion of successful testing, Mastercard issues a letter to the
member indicating that Mastercard Business Resumption Service testing has been
completed for GCMS procedures to the satisfaction of the member and the
Customer Implementation Services specialist.

Member Host Preparation Facility
Appendix B Member Host Preparation Facility

This section details the Member Host Preparation Facility software, including the
programs that compile and assemble, the Member Profile Extract file, and JCL setup.
About Member Host Preparation Facility.................................................................................. 83

Compile/Assemble and Link MHPF Programs.......................................................................... 83
OS—Compiling COBOL Modules............................................................................................. 83
OS—Assembler Programs......................................................................................................... 85
Required Order of Compilation and Assembly.....................................................................86
Compile and Link Edit of Specific Source Modules............................................................. 86
CR99XXXX............................................................................................................................... 86
CR992050 Codes............................................................................................................... 87
CR992070 Codes............................................................................................................... 90
IE7400010................................................................................................................................ 93
MH410010................................................................................................................................93
MH545010................................................................................................................................94
MH550010................................................................................................................................94
MH580010................................................................................................................................95
MH590010................................................................................................................................95
MH560010................................................................................................................................96
MH600010................................................................................................................................96
MH500010................................................................................................................................97
Member Profile Extract File...........................................................................................................98
Daily Member Profile Extract Upload Job.............................................................................98
Member Profile Extract File Record Types............................................................................ 98
Member Profile 5—Currency Conversion Values, ISO Code, ISO Rate, and Rate
Exponent.................................................................................................................................. 99
Member Profile 6—Bulk Type.............................................................................................100
Member Profile 8—MHPF Current Program Version Numbers..................................102
JCL Setup........................................................................................................................................104
SMH1002R..................................................................................................................................104
SMH1003R..................................................................................................................................107
SMH2001R..................................................................................................................................110
SMH2003R..................................................................................................................................114

About Member Host Preparation Facility
About Member Host Preparation Facility

The Member Host Preparation Facility (MHPF) software resides on the member
host mainframe.
MHPF is designed for IBM™ or IBM-compatible host mainframes. MHPF is
provided, by request, to institutions wanting to interrogate programs written to
support the MHPF function. All types of bulk data transmissions that run on the
host use of the MHPF software utilities. Clearing transmissions are identified as
clearing data.
NOTE: MHPF cannot support record lengths greater than 1012.
Compile/Assemble and Link MHPF Programs

To support the MHPF software, the following information explains procedures for
compiling and linking MHPF COBOL programs in the current COBOL compiler
supported by IBM, procedures for assembling and linking Assembler modules, and
sample programs in required compilation sequence (OS samples are included).
Mastercard implements MHPF conversion release updates twice each year. With
each release, Mastercard distributes updated testing and implementation
information, which supersedes the following information.
OS—Compiling COBOL Modules

The term COBOL includes COBOL compilers supported by IBM on the MHPF
release date. This does not include any compiler removed from marketing or
support by IBM on the MHPF release date.
The following job stream illustrates OS JCL for compile/link edit of the supplied
COBOL modules.
Some COBOL modules call other modules. When compiling, this situation may
result in “Unresolved External References.” In this case, the entry point name of the
CR99XXXX module, MCIMIPIO, is usually listed here. These warning messages are
resolved when the group (main) module is compiled and linked. MH410010 and
MH500010 are the MHPF group (main) modules. After all single module compiles
are complete, the group modules are compiled and linked with the other modules.
*************************************************************************************************
****************************
--------------- OS JCL FOR COMPILE AND LINK EDIT -----------------
//COMPLINK JOB (TEST),'COBOL OS/390 COMPILE-LINK', CLASS=T
//COBOL EXEC PGM=IGYCRCTL,REGION=512K

OS—Compiling COBOL Modules
//SYSPRINT DD SYSOUT=*
//SYSLIN DD DSN=&OBJ,SPACE=(3040,(40,40),,,ROUND),UNIT=SYSDA,
// DCB=(BLKSIZE=3040,LRECL=80,RECFM=FBS,BUFNO=1),
// DISP=(MOD,PASS)
//SYSUT1 DD SPACE=(1024,(120,120),,,ROUND),UNIT=SYSDA
//SYSIN DD DDNAME=CSYSIN (SEE BELOW)
//LKED EXEC PGM=IEWL,COND=(5,LT,COB),PARM='LIST,XREF,LET,MAP,AMODE=(31)'
//SYSLIB DD DSN=MCI.TS.COBLIB,DISP=SHR
//SYSLMOD DD DSN=MCI.AD.TEST.PGMLIB,DISP=SHR
//SYSUT1 DD SPACE=(1024,(120,120),,,ROUND),UNIT=SYSDA,DCB=BUFNO=1
//SYSLIN DD DSN=&OBJ,DISP=(OLD,DELETE)
// DD DDNAME=LSYSIN
*************************************************************************************************
*****************************
*************************************************************************************************
*****************************
//CSYSIN For information on the data sets assigned to the input DD names (CSYSIN
and LSYSIN) for each compilation, see Compile and Link Edit of Specific
//LSYSIN
Source Modules.,
*************************************************************************************************
*****************************
Default Parameters to Compile the MHPF Modules

The following table provides a reference for the Member Host Compile options.
MHPF COBOL Options

NOADATA ADV APOST
ARITH(EXTEND) AWO BUFSIZE(27998)
NOCICS CODEPAGE(1140) NOCOMPILE(E)

OS—Assembler Programs
MHPF COBOL Options

NOCURRENCY DATA(24) NODATEPROC
NODBCS NODECK DIAGTRUNC
NODLL NODUMP NODYNAM
NOEXIT NOEXPORTALL FASTSRT
FLAG(I,W) NOFLAGSTD INTDATE(LILIAN)
LANGUAGE(EN) LIB LINECOUNT(60)
LIST MAP NONAME
NSYMBOL(DBCS) NONUMBER NUMPROC(NOPFD)
OBJECT NOOFFSET OPTIMIZE(FULL)
OUTDD(SYSOUT) PGMNAME(COMPAT) NORENT
RMODE(ANY) NOSEQUENCE
SIZE(MAX) SOURCE SPACE(1)
NOSQL NOSSRANGE TERM
NOTEST NOTHREAD TRUNC(OPT)
NOVBREF NOWORD XREF(FULL)
YEARWINDOW(1900) ZWB
OS—Assembler Programs
The following job stream illustrates the OS JCL for assembly and link of the
Mastercard supplied Assembler source modules, CR99XXXX, and IE740010.
*************************************************************************************************
****************************
------------- OS JCL FOR ASSEMBLE AND LINK EDIT -------------------
//ASMLINK JOB (TEST),'ASSEMBLE-LINK',CLASS=T
//ASM EXEC PGM=ASMA90,
// PARM=(OBJ,NODECK)
//SYSLIB DD DSN=MCI.AD.PROD.MACLIB,DISP=SHR
// DD DSN=SYS1.MACLIB,DISP=SHR

Required Order of Compilation and Assembly
//SYSGO DD DSN=&&OBJSET,UNIT=SYSDA,SPACE=(80,(200,50)),
// DISP=(MOD,PASS)
//SYSIN DD DDNAME=ASYSIN (SEE BELOW)
//LKED EXEC PGM=IEWL,PARM=(LIST,XREF,LET,NCAL),
// REGION=128K,COND=(4,LT,ASM)
//SYSLIB DD DSN=MCI.TS.COBLIB,DISP=SHR
//SYSLMOD DD DSN=MCI.AD.TEST.PGMLIB,DISP=SHR
//SYSUT1 DD SPACE=(1024,(120,120),,,ROUND),UNIT=SYSDA,
// DCB=BUFNO=1
//SYSLIN DD DSN=&OBJSET,DISP=(OLD,DELETE)
// DD DDNAME=LSYSIN (See following data sets.)
Required Order of Compilation and Assembly

Customers must build the load modules in a specified sequence.
Build the load modules in the following sequence:
1. CR99XXXX (for example, CR992050 or CR992070, as applicable)
2. IE740010
3. MH410010
4. MH545010
5. MH550010
6. MH580010
7. MH590010
8. MH560010
9. MH600010
10. MH500010
Compile and Link Edit of Specific Source Modules

The following information explains the compile and link edit of specific source
modules. Information about the data sets assigned to the input DD names
(CSYSIN and LSYSIN) for each compilation is provided.
CR99XXXX
The CR99XXXX module does not apply to customers that transmit and receive files
with a tape unit attached to a Mastercard interface processor (MIP).
Two versions of the “CR99XXXX” module are provided; one using the IBM TCP/IP
stack and one using the Interlink TCP/IP stack. Only one of the two “CR99XXXX”

CR992050 Codes
Assembler modules should be chosen for assembly and link-editing with the
necessary COBOL programs. Each module performs the same logical functions
and has the entry point name “MCIMIPIO.” MCIMIPIO is not a separate module,
but exclusively an entry point.
The criteria for choosing the correct module depend on the communications
protocol used between the member host and the MIP for bulk data delivery. The
criteria are as follows:
• CR992050—TCP/IP Module for use with InterLink IP stack, version 3.1 or later
• CR992070—TCP/IP module for use with IBM IP Stack
*************************************************************************************************
*****************************
----------- ASSEMBLE AND LINK EDIT CR99XXXX ---------------------
//ASYSIN DD ((((((( SOURCE MODULE(CR99XXXX) )))))))
//LSYSIN DD *
NAME CR99XXXX(R)
ENTRY MCIMIPIO
/*
*************************************************************************************************
*****************************
NOTE: All customers must migrate from existing legacy protocol connections between their
hosts and MIPs to Transmission Control Protocol (TCP)/Internet Protocol (IP).
CR992050 Codes
MHPF module CR992050 is compatible with INTERLINK IP Stack, version 3.1 or
later. Customers that use IP stacks from vendors other than Interlink or IBM may
still use CR992050 as a template for file transfer. However, customers must
replace the CR992050 INTERLINK TCP/IP application programming interface (API)
calls with the TCP/IP API calls supported by their preferred vendor.
The following parameters and error codes are associated with the CR99 routine
necessary to support the TCP/IP MIP interface.
Inputs
The calling application routine places all inputs in memory.
1. MIOREQST—request code
1 = Open

CR992050 Codes
2 = Close
3 = Send
4 = Receive
2. MIOIODDN—DNR host MIP name
3. MIOIOAPL—TCP/IP SUBSYS name
4. MIORECD—Record for SEND or buffer for RECEIVE
Outputs
The calling application routine places all outputs in memory or in General Purpose
Register 15.
1. R15 and MIORETRN—return code

0 = Good return code
4 = Invalid request
7 = Open APCB
8 = Open local endpoint or receive timeout
9 = Bind local endpoint
10 = Connect remote endpoint
12 = TCHECK failed
16 = TRECEIVE failed
20 = MIOLL invalid, TSEND failed
24 = Invalid length
2. MIOERRFN—error function code

1 = OPEN
2 = CLOSE
3 = SEND
4 = RECEIVE
11 = RECEIVE two byte header
13 = RECEIVE data
14 = SEND header

CR992050 Codes
15 = SEND data
3. MIOERRRT—error return code

R15 = Macro return code
21 = Data waiting
22 = Unknown request
4. MIOERRSN—RO
5. MIORECD—record for RECEIVE
In the following tables:

• MIO is not included in the labels.
• REQST and ERRFN have values as described earlier.
• n/a indicates that the value is not applicable.
Normal Completion
REQST Condition RETRN ERRFN ERRRT ERRSN

1,2,3,4 Normal completion 0 n/a n/a n/a
Error Conditions

1 Invalid request 4 1
1 OPEN APCB 7 1 R15 R0
1 OPEN local endpoint 8 1 R15 R0
1 BIND local endpoint 9 1 R15 R0
1 Connect remote endpoint 10 1 R15 R0
2 Invalid request 4 2 n/a n/a
2 TCHECK failed 12 15 R15 R0
3 Invalid request 4 3 21 n/a
3 TSEND failed 20 14 R15 R0

CR992070 Codes

4 RECEIVE timeout 8 11 n/a n/a
4 TRECEIVE failed 16 11 R15 R0
4 MIOLL invalid 20 11
4 Invalid length 24 13
1,2,3,4 Invalid request 4 22
CR992070 Codes
MHPF module CR992070 is compatible with IBM’s IP Stack. Customers that use IP
stacks from vendors other than IBM may still use CR992070 as a template for file
transfer. However, customers must replace the CR992070 IBM TCP/IP application
programming interface (API) calls with the TCP/IP API calls supported by their
preferred vendor.
The parameters and error codes are associated with the CR992070 routine
necessary to support the TCP/IP MIP interface.
In the Normal Completion and Error Condition tables:
• MIO is left off the labels.
• REQST and ERRFN have values as described in Inputs and Outputs tables.
• n/a indicates that the value is not applicable.
Inputs
The calling application routine places all inputs in memory.
1 = Open
2 = Close
3 = Send

CR992070 Codes
4 = Receive
Outputs
The calling application routine places all outputs in memory or in General Purpose
Register 15.
1. R15 and MIORETRN—return code

0 = Good return code
4 = Invalid request
7 = Open APCB
8 = Open local endpoint or receive time out
9 = Bind local endpoint
10 = Connect remote endpoint
12 = TCHECK failed
16 = TRECEIVE failed
20 = MIOLL invalid, TSEND failed
24 = Invalid length
2. MIOERRFN—error function code

1 = OPEN
2 = CLOSE
3 = SEND
4 = RECEIVE
11 = RECEIVE two byte header
13 = RECEIVE data
14 = SEND header
15 = SEND data

CR992070 Codes
3. MIOERRRT—error return code

4. MIOERRSN—RO
5. MIORECD—record for RECEIVE
R15 = Macro return code
21 = Data waiting
22 = Unknown request
Normal Completion

1,2,3,4 Normal completion 0 n/a n/a n/a
Error Conditions

1 Invalid request 4 1
1 OPEN APCB 7 1 R15 R0
1 OPEN local endpoint 8 1 R15 R0
1 BIND local endpoint 9 1 R15 R0
1 Connect remote endpoint 10 1 R15 R0
3 Invalid request 4 3 21 n/a

IE7400010

4 MIOLL invalid 20 11
4 Invalid length 24 13
1,2,3,4 Invalid request 4 22
IE7400010
The following sample displays the load module IE7400010.
*************************************************************************************************
*****************************
---------------- ASSEMBLE AND LINK EDIT IE740010 -----------
//ASYSIN DD ((((((( SOURCE MODULE(IE740010) )))))))
//LSYSIN DD *
NAME IE740010(R)
/*
*************************************************************************************************
*****************************
MH410010
The following sample displays the load module MH410010.
*************************************************************************************************
*****************************
------------- COMPILE AND LINK EDIT MH410010 ---------------
//CSYSIN DD ((((((( SOURCE MODULE (MH410010) )))))))
//LSYSIN DD
INCLUDE SYSLMOD(CR99XXXX)
NAME MH410010(R)
/*
*************************************************************************************************
*****************************

MH545010
MH545010
*************************************************************************************************
*****************************
------------------ COMPILE AND LINK EDIT MH545010 -----------------
//LSYSIN DD *
NAME MH545010(R)
/*
*************************************************************************************************
*****************************
MH550010
*************************************************************************************************
*****************************
----------------- COMPILE AND LINK EDIT MH550010 ------------------
// DD ((((((( SOURCE MODULE (MH550010) )))))))

CSYSIN
// DD *
LSYSIN
NAME MH550010(R)
/*
Note: As a programming reference, the following programs are called by the

source module but should not be linked. Linking will occur in the
compilation of other source code. The Linkedit Parm “NCAL” should be
added to the Link Step.
IE740010
MH545010
*************************************************************************************************
*****************************

MH580010
MH580010
*************************************************************************************************
*****************************
----------- COMPILE AND LINK EDIT MH580010 ---------------------
//LSYSIN DD *
NAME MH580010(R)
/*
*************************************************************************************************
*****************************
MH590010
*************************************************************************************************
*****************************
----------- COMPILE AND LINK EDIT MH590010 --------------------
//LSYSIN DD *
NAME MH590010(R)
/*

compilation of other source code. The Linkedit Parm “NCAL” should be
added to the Link Step.
IE740010
MH545010
MH580010
*************************************************************************************************
*****************************

MH560010
MH560010
*************************************************************************************************
*****************************
--------------- COMPILE AND LINK EDIT MH560010 ---------------------
//LSYSIN DD *
NAME MH560010(R)
/*
compilation of other source code. The Linkedit Parm “NCAL” should
be added to the Link Step.
CR99XXXX
IE740010
MH545010
MH590010
*************************************************************************************************
*****************************
MH600010
*************************************************************************************************
*****************************
----------------- COMPILE AND LINK EDIT MH600010 -------------------
//LSYSIN DD *
NAME MH600010(R)
/*
Note: As a programming reference, the following programs are called by

the source module but should not be linked. Linking will occur in the
compilation of other source code. The Linkedit Parm “NCAL” should
be added to the Link Step.
IE740010
MH545010

MH500010
MH550010
*************************************************************************************************
*****************************
MH500010
*************************************************************************************************
*****************************
------- COMPILE AND LINK EDIT MH500010 -------
//LSYSIN DD *
INCLUDE SYSLMOD (CR99XXXX)
INCLUDE SYSLMOD (IE740010)
INCLUDE SYSLMOD (MH545010)
ENTRY MH500010
NAME MH501010(R)
/*
*************************************************************************************************
*****************************
NOTE:
MHPF was designed to use the load name MH501010 when compiling the program
MH500010.
Member Host module MH501010 and all the variants of it will link as an RMODE=24 module
due to the inclusion of the IE740010 module.

Member Profile Extract File
Member Profile Extract File

The Member Profile Extract file contains a variety of records that are delivered on
a daily basis to the Mastercard interface processor (MIP) via the Mastercard
Worldwide Network bulk ID T007. This bulk type must be unloaded each day the
Member Host Preparation Facility Software (MHPF) software utilities are
scheduled to process files.
The Member Profile Extract file provides the following information:
• Currency code values supported by Mastercard
• Valid bulk files processed
• Current version numbers for the MHPF modules
Daily Member Profile Extract Upload Job

The Mastercard Parameter Extract file contains 60-byte records. The block
contains 16 records, totaling a block size of 960. To unload this file, use a non-
clearing MHPF job stream indicating T007 as the bulk type in the control card.
The format of the data in both IPM clearing messages and IPM MPE messages
(both full file and updates) is Variable Blocked Spanned (VBS). Therefore,
messages can be longer than the Mastercard Network constraint of 1014 bytes. To
accommodate customers delivering and receiving these messages over the
Mastercard Network and via Mastercard File Express, a four-byte Record
Descriptor Word field immediately preceding each IPM message holds the length
of the data in each message. The MHPF MIP load and unload modules handle the
Record Descriptor Word (RDW) in the IPM clearing messages and in the IPM MPE
messages correctly. For more information about the Record Descriptor Word, see
the GCMS Reference Manual.
Packed Records
The record format is represented by:
• N=Numeric
• P=Packed
• AN=Alphanumeric
Member Profile Extract File Record Types

The following tables provide a brief description and layout of each Member Profile
Extract file record.
The first byte of each record identifies the record (for example, the Member Profile
Bulk Type record has a “6” in position one).

Member Profile 5—Currency Conversion Values, ISO Code, ISO Rate, and Rate Exponent
Record Description
Member Profile 5—Currency Conversion Identifies all currency code values supported
Values, ISO Code, ISO Rate, and Rate by Mastercard.
Exponent
Member Profile 6—Bulk Type Identifies all valid bulk files.
Type 6 records in the MPE are no longer used
in the MHPF program to validate bulk types.
Member Profile 8—MHPF Current Program Lists the MHPF programs and the current
Version Numbers version of each program.
Member Profile 5—Currency Conversion Values, ISO Code, ISO Rate, and Rate
Exponent
Customers use the Member Profile 5—Currency Conversion Values, ISO Code, ISO
Rate, and Rate Exponent record to identify all currency conversion values, ISO
codes, rates, and exponent values supported by Mastercard. There will be as many
type five records as needed to accommodate all ISO codes that Mastercard
supports. Mastercard supports as many as 196 ISO codes.

Record Type 1 1 AN Constant—5 (Currency
Conversion Values, ISO Code,
ISO Rate, and Rate Exponent)
Filler 2–7 6 N Constant—Zeros
Sequence Number 8–9 2 N Values = 00–40
ISO Currency Exponent 10–14 5 N Corresponds to the five ISO
Codes entry occurrences in positions
15–59.
ISO Code (1) 15–17 3 N
ISO Code (1) Rate and 18–23 6 P The currency mid rate is found
Rate Exponent in the 10 high-order positions
and the currency rate
exponent is in the low-order
position of the field.
ISO Code (2) 24–26 3 N
ISO Code (2) Rate and 27–32 6 P See comment associated with
Rate Exponent ISO Code (1).
ISO Code (3) 33–35 3 N

Member Profile 6—Bulk Type

ISO Code (4) 42–44 3 N
ISO Code (5) 51–53 3 N
Filler 60 1 AN

Customers use the Member Profile 6—Bulk Type record to identify all valid
Mastercard bulk files that are unloaded from a customer’s Mastercard interface
processor (MIP).

Record Type 1 1 AN Constant—6 (Bulk Type
Record)
Filler 2–7 6 AN
Sequence Number 8–9 2 N Values =1–99
Bulk Type (1)
Bulk Type 10–12 3 AN
Bulk Routing 13 1 AN T = Transmitted from
Mastercard
R = Received by Mastercard
Bulk Type (2)
Mastercard
Bulk Type (3)
Mastercard


Bulk Type (4)
Mastercard
Bulk Type (5)
Mastercard
Bulk Type (6)
Mastercard
Bulk Type (7)
Mastercard
Bulk Type (8)
Mastercard
Bulk Type (9)
Mastercard
Bulk Type (10)

Member Profile 8—MHPF Current Program Version Numbers

Mastercard
Bulk Type (11)
Mastercard
Bulk Type (12)
Mastercard
Filler 58–60 3 AN

Customers use the Member Profile 8—MHPF Current Program Version Numbers
record to identify the most current versions of all MHPF programs. It is important
for customers to use this record when Mastercard releases a new version of MHPF
programs to ensure that the most current versions of the programs are accessed.

Record Type 1 1 AN Constant—8 (Program Version
Numbers)
Filler 2–7 6 AN
Sequence Number 8–9 2 N Values = 1–99
Programs (1)
Program Name 10–14 5 AN
Program Version 15–16 2 AN
Programs (2)
Programs (3)


Programs (4)
Programs (5)
Programs (6)
Programs (7)
Filler 59–60 2 AN

JCL Setup
JCL Setup
Sample JCL procedures used to load and unload bulk files from the Mastercard
interface processor (MIP) are provided, as well as flow charts illustrating these
procedures.
SMH1002R
A sample of OS JCL for the edit and load of non-clearing files is provided.
Sample OS JCL Load of Non-Clearing Files

SMH1002R

SMH1002R
Non-Clearing Load Flow

SMH1003R
SMH1003R
A sample of OS JCL for loading variable length bulk types to a MIP is provided.
NOTE: These JCL procedures are intended for use by customers creating files in the IPM
format. For further instructions, see the Clearing Optimizer—Mainframe for further
instructions.
Sample OS JCL Load of Variable Length Bulk Types

SMH1003R

SMH1003R
IPM Variable Length Data Load

SMH2001R
SMH2001R
A sample of OS JCL for the unload of clearing and non-clearing files is provided.
Sample OS JCL Unload of Clearing and Non-Clearing Files

SMH2001R

SMH2001R

SMH2001R
Clearing/Non-Clearing Unload

SMH2003R
SMH2003R
A sample of OS JCL for unloading variable length bulk types from a MIP is
provided.
Sample OS JCL Unload of Variable Length Bulk Types

SMH2003R

SMH2003R

SMH2003R
IPM Variable Length Data Unload

MIP Bulk File Advisement
Appendix C MIP Bulk File Advisement

This appendix explains the console used to view available files on a MIP. For customers
sharing a MIP that may not have control permissions, this console enables searching the
MIP for bulk files (for a specific endpoint) that have been returned to a MIP from
Mastercard.
About MIP Bulk File Advisement Program...............................................................................119

Current Environment.................................................................................................................... 119
How It Works..................................................................................................................................119
Customer Internal System Enhancement Options................................................................120
Customer-Defined Parameters..................................................................................................120
Parameter Control Card File Queries.................................................................................. 121
JCL Setup (SMR4001R)............................................................................................................... 123
Parameter Control Card File (MH410010).............................................................................. 124
MIP Bulk File Advisement File Layout (MH410010)...............................................................125
Bulk File Advisement Report (MH410010-AA)........................................................................127
MH410 Console Messages...........................................................................................................130

About MIP Bulk File Advisement Program
About MIP Bulk File Advisement Program

The MIP Bulk File Advisement program is a host-based, parameter-driver program
that informs a member when bulk files are available to be unloaded from its
Mastercard interface processor (MIP).
Customers that choose to use this program can enhance their internal processing
systems to automatically initiate their bulk file unload processes. When used, the
program queries the MIP to determine the presence of Mastercard bulk files.
Current Environment
The Mastercard Network delivers many different types of bulk files to MIPs located
at member sites. Each type of bulk file contains different data (for example, fraud
data, clearing data, and billing data). A bulk file ID identifies the type of data
contained in a bulk file.
Customers typically initiate unload jobs based on the time of day they expect bulk
files to be available. If the requested bulk files are not present on the MIP for
unloading, the unload job will abnormally end (abend).
To avoid receiving the abend message from Member Host Preparation Facility
(MHPF), customers periodically may query their MIPs to determine when bulk files
are available to be unloaded and processed. When customers observe that a
particular type of bulk file is present, they manually initiate a process to unload the
file from the MIP to their host computers for processing through their internal
applications. Customers often wait for several files of one type (such as four
clearing files) to be present on their MIPs before unloading and processing.
Customers may have their MIPs and host computers at different physical
locations. If this is the case, deciding when to initiate unloads of Mastercard bulk
files may involve several telephone calls between sites.
How It Works
The MIP Bulk File Advisement program generates a report and a file that identifies
the availability of bulk files on the MIP. Both the report and the file contain the
same information.
When the MIP Bulk File Advisement program is run, it generates the Bulk File
Advisement Report (MH410010–AA). Customers use the report to determine
whether specific files are available on the MIP and, regardless of the location of
the MIP, determine the appropriate internal jobs to run.
The MIP Bulk File Advisement program also generates a file that consists of a
record for each bulk file that meets the request criteria. Each record contains the

Customer Internal System Enhancement Options
bulk file identification, status, source, blocks, and file creation data. If there are no
files on the MIP that meet the request criteria, a null file is created.
Customer Internal System Enhancement Options

Customers have the option to modify their internal systems automatically to run
the MIP Bulk File Advisement program to determine when specific bulk files have
been loaded to their MIPs.
Customers also can modify their internal systems to automatically unload the bulk
files when the MIP Bulk File Advisement program determines that specific types of
bulk files are present on their MIPs.
The customer’s internal program can receive a specific return code identifying that
certain bulk files are present. This allows the job stream to continue processing or
be canceled, depending on whether certain conditions are met. An example would
be when a member wants to start the unloading and processing of Mastercard
IPM format data only after all six GCMS clearing files are received (six T112 files in
a staged status). Customers can run the MIP Bulk File Advisement program as
often as needed.
Customer-Defined Parameters
Customers determine the extent to which the MIP Bulk File Advisement program
queries the MIP by submitting a Parameter Control Card file each time they run
the MIP Bulk File Advisement program.
Customers use the Parameter Control Card file to specify the criteria the MIP Bulk
File Advisement program will use to identify the availability of bulk files on the MIP.
The criteria may include specific bulk file type, status, or unique file name.
The Parameter Control Card file also allows customers to request a complete
directory that identifies all bulk files on the MIP, regardless of file type, status, or
unique file name. Customers can submit as many as five Parameter Control Cards
with a single execution of the program. For the file layout, see Parameter Control
Card File (MH410010).
NOTE: The MH410010 program is a constant value in positions 65–72 of the Parameter
Control Card file.

Parameter Control Card File Queries

The Parameter Control Card file allows customers to initiate several types of
queries.
Query for All Files with a Specific Bulk File Type (Both Clearing and Non-Clearing)
To determine, for example, the presence of bulk files with a file type of T on the
MIP for unloading, a member should submit two Parameter Control Card files as
follows.
• The first two positions must contain (..).

• The T in position 3 of the first card denotes a request for all T files on the MIP
• The MH410010 starting in position 65 of every control card file denotes a
request to run the MIP Bulk File Advisement program
• All other Bulk File Parameters subfields on both control cards should be blank
Query for all Files with a Specific File Status (Both Clearing and Non-Clearing)
To determine the presence of staged bulk files on the MIP for unloading, a member
should submit one Parameter Control Card file as follows.
• The S in position 35 denotes a file that is in a staged status on the MIP.

• All Bulk File Parameters subfields on the control card should be blank.
Query for a Complete Directory

To retrieve a complete directory of all bulk files on the MIP, a member should
submit one Parameter Control Card file as follows.
All Bulk File Parameters subfields should be blank.

Query for a Specific Bulk File in a Particular Status

To determine, for example, the presence of a GCMS outbound (Mastercard-to-
member) file on the MIP, a member should submit one Parameter Control Card file
as follows.

• The T in position 3 denotes a request for outbound (Mastercard-to-member)
files
• The 112 starting in position 4 denotes a GCMS inbound (Mastercard-to-
member) file.
• The S in position 35 denotes a file that is in a staged status on the MIP
• The T, the 112, and the S should be the only Bulk File Parameters subfields
supplied
Query for a Specific File Type and Name

To determine the presence of a specific clearing GCMS inbound (Mastercard-to-
member) file on the MIP, a member should submit one Parameter Control Card file
as follows.

• The T in position 3 denotes a request for outbound (Mastercard-to-member)
files
• The 112 starting in position 4 denotes a request for a GCMS outbound
(Mastercard-to-member) file
• A specific Bulk File ID starting in position 7 denotes a request to determine the
presence of a specific bulk file (by name) on the MIP. In this example, the specific
bulk ID is EEEEEJJJCC (EEEEE = endpoint, JJJ = Julian date, and CC = clearing
cycle number).
• The S in position 35 denotes a file that is in a staged status on the MIP.
• The T, the 112, unique file name, and the S are the only Bulk Type fields supplied.

JCL Setup (SMR4001R)
JCL Setup (SMR4001R)

To run the MIP Bulk File Advisement program, a member supplies a sample JCL.
The member may need to adjust certain values in the sample JCL below and also
will need to replace the MIP Unit Number with its actual MIP number.
//
*************************************************************************************************
*****
STEP000 - SORT INITIALIZE
/*
/*
//
*************************************************************************************************
*****
//STEP000EXEC PGM=SORT//SYSOUTDD SYSOUT=*//SORTIN DD DATA,//SORTOUT DD
DSN=MEMBER.MH.REQUEST.CARDS,// UNIT=DISK,SPACE=(TRK,1),//
DCB=(RECFM=FB,LRECL=80,BLKSIZE=32000),// DISP=(,CATLG,DELETE)//SYSIN DD * SORT
FIELDS=COPY//STEP001 EXEC PGM=MH410010//SYSPRINT DD SYSOUT=*//SYSOUT DD
SYSOUT=*//SYSUDUMP DD SYSOUT=D//SYS001 DD DSN=MEMBER.MH.REQUEST.CARDS,DISP=SHR//
SYS050 DD UNIT=MIP UNIT NUMBER// DD DUMMYUSE THIS DUMMY STATEMENT WHEN VTAM
//
*************************************************************************************************
*****
//*Include the DD statement for SYSTCPD when using TCP/IP protocol//*For any
other protocol, it must be removed
//*For any other protocol, it must be removed
//
*************************************************************************************************
*****
//SYSTCPD DD DSN=MEMBER TCPIP PARMS DATASET(member),DISP=SHR//SYS201 DD
DSN=MEMBER.MH.BULK.FILE.ADVISEMT,// UNIT=DISK,SPACE=(CYL,(10,5),RLSE),//
DCB=(RECFM=FB,LRECL=120,BLKSIZE=24000),// DISP=(NEW,CATLG,DELETE)//SYS202 DD
SYSOUT=*,DCB=(RECFM=FBA,BLKSIZE=133)/*
//
*************************************************************************************************
*****

Parameter Control Card File (MH410010)
Parameter Control Card File (MH410010)

The Parameter Control Card file is used to indicate the bulk file information for
which the MIP Bulk File Advisement program will query on the MIP. The Bulk File
Advisement report (MH410010–AA) and file are generated each time the member
runs the MIP Bulk File Advisement program.
The record format is represented as follows:
• C = Compressed
• N = Numeric
• P = Packed
• S = Signed
• AN = Alphanumeric

Record Type 1–2 2 AN Constant—Must contain two blank
spaces
Bulk File Parameters
File Type 3 1 AN Must contain an “R,” “T,” or space
T = Inbound File Types
(Mastercard-to-member)
R = Outbound File Types
(Member-to-Mastercard)
Spa = All File Types
ce
Bulk Type 4–6 3 AN Must contain a valid MIP bulk type
value or spaces. Three-digit value
denoting the assigned file number.
(For example: 112 = GCMS inbound
file-–Mastercard-to-member.)
Unique Name 7–34 28 AN Must contain a valid MIP file name or
spaces. A single execution of
MH410010 supports as many as five
control card records. A complete
directory request can be submitted
only on the first card. For the File
Type A, the Bulk Type field is four
positions, 8–11, and Unique Name
field is 27 positions, 12–38.
File Status 35 1 AN Must contain one of the following
values or a blank space.

MIP Bulk File Advisement File Layout (MH410010)

NCR database
D = File is complete to
destination, delivered
E = File is pended with edit errors
network
P = File use complete, can delete
(purgeable)
X = File being processed by engine
W = File is being written for log
Node name for S/1 36–43 8 AN VTAM only
Channel
VTAM Application 44–51 8 AN VTAM only
Name
Filler 52–64 14 AN Must contain blank spaces
Program Name 65–72 8 AN Must contain MH410010
Filler 73–80 8 AN Must contain blank spaces

The following information explains the MIP Bulk File Advisement (MH410010) file
layout.
Customers can change their internal systems to automatically run the MIP Bulk
File Advisement program and automatically initiate bulk file process:
• Automatically run the MIP Bulk File Advisement program
• Automatically initiate bulk file processing when files are ready to be unloaded


Bulk file ID 1–32 32 AN
File status 33 1 AN
File Status Description 34–63 30 AN Status codes will be expanded to the
following explanations:
NCR database
D = File is complete to destination,
delivered
E = File is pended with edit errors
network
P = File use complete, can delete
(purgeable)
X = File being processed by engine
W = File is being written for log
Field Status Source 64 1 AN Source of this file
H = Member host
N = Network
D = Database
L = Logger
File dimensions for
receiver:
Destination blocks 65–72 8 AN
Creation day (Julian) 73–75 3 N
Receive day (Julian) 76–78 3 N
Receive time 79–84 6 N
(HHMMSS)

Bulk File Advisement Report (MH410010-AA)

Send day (Julian) 85–87 3 N
Send time (HHMMSS) 88–93 6 N

The Bulk File Advisement program generates the Bulk File Advisement Report
(MH410010-AA) and file.
This report identifies the status of bulk files on the member MIP. This report can be
used by member personnel to know when bulk files are available for unloading and
processing through the Member Host Preparation Facility, even if the person
initiating bulk file processing is in a different location than the MIP.
Title: Bulk File Advisement Report (MH410010–AA)

Generated by: A customer’s mainframe
Purpose: To identify for member personnel the status of Mastercard bulk files
on the member MIP.
Description: Provides the status of all bulk files on the member MIP so that,
regardless of the MIP’s location, an individual can initiate the
unloading and processing of Mastercard bulk files.
Frequency: Each time the member executes the MIP Bulk File Advisement
program.
Distribution: Not applicable. The report is generated on the mainframe at the
customer’s site.


Field Descriptions
Following are the field descriptions for the Bulk File Advisement Report
(MH410010-AA).
Field Description
Run Date Date the member executed the MIP Bulk File Advisement
program in MMDDYY format.
Bulk Type Specific bulk file requested for unload by the Bulk File
Advisement execution; for example, T, R, or A file.
Unique or Partial Name Bulk file names requested with the execution.
Status Bulk file status requested with the execution.
Bulk File Advisement Heading that precedes the requested bulk file information.
Response
Bulk File ID Unique file name for each bulk file that currently resides
on the MIP. If there is more than one bulk file on the MIP
that meets the requested requirements, the bulk files are
listed in alphanumeric order.
File Status Status or message of the bulk file execution. Valid
messages include:
• File being read to update NCR database
• File use complete (purgeable)
• File is complete, delivered
• File is staged and available
• File appended with edit errors
• File in progress to host
• File in progress from host
• File transfer interrupted
• Database session initiated
• File being processed by engine
• Log file in progress
• File is being written for log
• File in progress through network
File Source Indicates the origin of the bulk file; for example member
host, logger, or network.
Receiver Blocks Indicates the size of the bulk file in 4096 character blocks.
Creations Day Indicates the Julian date the bulk file was created or last
modified.
Receive Day Julian date the bulk file was received at the member site.
Receive Time Time the bulk file was received in HHMMSS format.

MH410 Console Messages
Field Description
Send Day Julian date the bulk file was sent.
Send Time Time the bulk file was sent in HHMMSS format.
Generic Bulk Type The requested bulk file type that was entered by the
member on the Control Card file.

Console messages display are messages that display on the customer’s mainframe
console and on the JCL reports. These messages identify a processing error while
attempting to execute the MIP Bulk File Advisement program.
Message Number Message Action

MH410–3001 Control card missing Supply the parameter control
cards for request.
MH410–3002 First two positions of control card Correct the first two
must contain two blank spaces positions of the control card
and re-execute.
MH410–3003 Program number MH410010 Supply the program number
missing in positions 65–72 and re-execute.
MH410–3004 Program number in positions 65–72 Correct program number and
is invalid re-execute.
MH410–3005 Control card contains spaces in the Blank bulk type and status
bulk type and file status only valid on first request,
correct control card and re-
execute.
MH410–3006 Maximum of five requests Correct control cards and re-
exceeded execute.
MH410–3007 Control card contains non-numeric Correct control card and re-
bulk type execute.
MH410–3008 Control card contains invalid file Correct control card and re-
type execute.
MH410–3009 Control card contains invalid file Correct control card and re-
status execute.
MH410–3010 201 message is corrupt (for Contact a Mastercard
example, missing or invalid header representative.
information, invalid data length)

Message Number Message Action

MH410–3011 Transmission Error Contact a Mastercard
representative.
MH410–3012 No bulk files to satisfy the request Validate the requested card
specified in the 201 message parameters. If parameters
are correct, the MIP has not
received the file from
Mastercard.
MH410–3013 Invalid request returned from the Re-execute. If problem
MIP continues, contact a
Mastercard representative.
MH410–3014 Cannot open communication with Contact a Mastercard
the MIP representative.
MH410–3015 Cannot close communication with Contact a Mastercard
the MIP representative.
MH410–3016 MIP communication received Contact a Mastercard
representative.
MH410–3017 MIP returned reverse error Contact a Mastercard
representative.
MH410–3018 MIP returned length error Contact a Mastercard
representative.
MH410–3098 The following control cards were Refer to the individual control
rejected (a specific control card card errors, correct the
error message will follow for each control card, and re-execute.
control card error.)
MH410–3099 Communications lost between host Re-execute. If problem
and MIP job continues, contact a
Mastercard representative.

Testing Procedures
Appendix D Testing Procedures

Customers should perform periodic testing on their networks. This appendix contains
overviews and checklists for testing.
About Testing Procedures............................................................................................................133

Priority of Testing Activities........................................................................................................ 133
Installing MHPF..............................................................................................................................134
Testing Procedures for MIP/MHPF Customers....................................................................... 135
Pended Transmissions.................................................................................................................. 136
Testing Procedure for Third Party File SFTP Client............................................................... 136
Production.................................................................................................................................. 137
Testing the domain name service for attended or unattended production URL...137
Testing SFTP Connection.............................................................................................. 137
MTF..............................................................................................................................................138
Testing the domain name service for attended or unattended MTF URL.............. 138
Testing SFTP Connection.............................................................................................. 138

Testing Procedures
About Testing Procedures
About Testing Procedures

Bulk testing requires ongoing communication between member personnel and
Customer Implementation Services. The team agrees on testing objectives and
schedules, resolves issues, and targets production cutover activities.
Priority of Testing Activities

There are two major priorities for testing activities: the exchange of clearing and
settlement data and the exchange of non-clearing files.
The exchange of clearing and settlement data is the most important testing
priority.
Customers determine which non-clearing files to test based on the probability that
they will use them. Although the Customer Implementation Services specialists will
provide a list of minimum requirements, customers are responsible for forecasting
their potential needs.
Testing again at a later time may incur additional expense to customers.
Bulk File testing

Bulk File testing validates that if you are using a Mastercard Network-based file
transfer protocol (Connect:Direct and MFTS), you can successfully exchange bulk
files with Mastercard. The Mastercard CTC Admin Group will assist you with bulk
file testing, as described below.
Bulk File Transfer testing

Exchange connectivity test bulk files in the Mastercard Test Facility (MTF)
environment You will exchange the following test bulk files with Mastercard:
• R699 (MTF-MBR to GFT-Connectivity Testing): Mastercard receiving files from
the customer
• T700 (MTF-GFT to MBR-Connectivity Testing): Mastercard transmitting files to
the customer
Exchange connectivity test bulk files in the Mastercard production environment.
You will exchange the following test bulk files with Mastercard:
• R205 (MBR to GFT-CONNECT:Direct-Connectivity Testing): Mastercard
receiving files from the customer
• T206 (GFT to MBR-CONNECT:Direct-Connectivity Testing): Mastercard
transmitting files to the customer
Once the Mastercard Tester is satisfied with the testing results, they will notify
your Mastercard Implementation Manager.

Testing Procedures
Installing MHPF
NOTE: The CTC Admin Group will be engaged in testing with customers using
Connect:Direct and situations where Mastercard pushes files, or the customer pushes files,
to exchange security parameters.
File Transfer testing completed

This completes configuration of your file transfer method. Your next steps are to
either:
• Proceed with application testing,
• Begin transmitting production files
NOTE: If you want to test additional bulk files associated with the Mastercard products
and services you will be supporting, your assigned Mastercard Tester will assist you.
Installing MHPF
The initial setup for installation of Member Host Preparation Facility (MHPF)
includes the following process.
Procedure
1. Receive software from Mastercard.
2. Compile and link software.
3. Set up JCL procedures to:
– Unload MPE file using SMH2001R
– Load any non-clearing files that you process using SMH1002R
– Unload any non-clearing files that you process using SMH2001R
– Run Bulk File Advisement program (optional)
– Load any GCMS clearing files that you process using SMH1003R
– Unload any GCMS clearing files that you process using SMH2003R
The SMH1003R and SMH2003R JCL sets are intended for use by customers
creating files in the IPM format. For additional instructions, see Clearing
Optimizer—Mainframe.
What to do next
Mastercard has established production and test bulk types for all bulk files sent
through the Mastercard Network. It is important to use TEST bulk types when
processing files for testing purposes to avoid potential production problems. See
specific guidelines for control card and setup to produce TEST bulk types.

Testing Procedures
Testing Procedures for MIP/MHPF Customers
Testing Procedures for MIP/MHPF Customers

To test procedures, follow these steps.
Procedure
1. Load the clearing file.
Following initial setup, proceed by testing a Global Clearing Management
System (GCMS) clearing file sent to Mastercard. Create a test file
representative of a clearing file from your internal operations department and
send it to Mastercard. This file should emphasize records to be used in
production and should contain a reasonable number of records.
Perform a load of the IPM format data to your MIP:
– Run the SMH1003R JCL.
– Indicate R119 in the first four positions of the control card.
2. Load the non-clearing bulk file.
– Obtain a copy of a file that is blocked less than 1014 bytes.
– Perform a load of non-clearing data to your MIP using bulk ID R601 or R603.
– Run the SMH1002R JCL.
– Indicate R601 in the first four positions of the control card if you are loading
General Bulk Data.
3. Load non-clearing bulk file (optional).
– Perform this step for any daily processed file that is sent to Mastercard, such
as a fraud file. Use the instructions in step 2.
– Indicate the selected bulk type in the first four positions of the control card.
4. Upon successful completion of the previous steps, notify your Customer
Implementation Services specialist of the full transmission IDs. The test system
will:
– Unload the customer’s files sent to Mastercard.
– Produce an in-house settlement edit report using the test IPM format data
file. Any discrepancies will be noted.
– Return a T120 Bulk File of TEST clearing and settlement data to the
customer.
– Return the same data that the customer sent in the outbound general bulk
file (R601) to the customer in an inbound general bulk file (T602).
– Return the same data that the customer sent in the outbound GCMS
general bulk file (R603) to the customer in an inbound GCMS general bulk
file (T604).
Customer Implementation Services will inform you of the complete
transmission IDs of the files sent. Verify the data contained in specified non-
clearing bulk files.
5. Unload clearing files.

Testing Procedures
Pended Transmissions
–Perform an unload of IPM format data from your MIP.

–Run the SMH2003R JCL indicating either tape or direct attached.
–Indicate T120 in the first four positions of the control card.
–If your Customer Implementation Services specialist indicated that the T120
would be based upon your R119 transmission, verify that the data received is
the same as the production data you previously received for this clearing
transmission.
6. Unload non-clearing files.
– Perform an unload of non-clearing data from your MIP for each non-clearing
file received.
– Run the SMH2001R JCL indicating either tape or direct attached.
Indicate the bulk ID in the first four positions of the control card. Check bulk ID
list to identify the test bulk ID of the application, or use one of the generic bulk
file types (either T602 or T604).
7. Run optional MIP Bulk File Advisement. (See About MIP Bulk File Advisement
Program.)
Mastercard will request bulk ID R601 (non-VBS format) or R603 (VBS format)
to assist with a problem.
Pended Transmissions
The following conditions can cause non-clearing bulk files to be marked as
“PENDED.”
• At least one record in the file is not blocked at the proper logical record length
• Invalid transaction code
• Sequence errors
The MHPF program listing will indicate that the file has been marked as PENDED
and will indicate the errors. The customer may choose to correct these errors and
resubmit the MHPF load JCL or may indicate a “P” in column 34 of control card
MH501010 and rerun the MHPF load JCL without correcting the errors. It will be
sent to Central Site and processed, and any errors will be noted.
Testing Procedure for Third Party File SFTP Client

The steps that can help to troubleshoot the SFTP connectivity issues.
NOTE: Contact Network Administrator for testing the SFTP connection for production and
MTF environment.

Testing Procedures
Production
Production
Testing the domain name service for attended or unattended production URL
Procedure
1. From the Windows Start menu, click Run.
The Run dialog box appears.
2. In the Open box, type “cmd”, and then click OK.
The Command Prompt window appears.
3. Run the command “nslookup files.mastercard.com”.
The output display the following text:
NOTE: In case, output displays:
Non-existent domain?
Contact your Network Administrator to diagnose why your network’s DNS is not able
to resolve the Mastercard File Express URL to its IP address.
What to do next
Once you have resolved the DNS host name for “files.mastercard.com” to IP
Address 216.119.219.66, , and still cannot authenticate, proceed to the Testing
SFTP Connection section.
Testing SFTP Connection
Perform the test to verify whether a SFTP connection can be made to the
Mastercard File Express server using the host name “files.mastercard.com” and
port 15022 for attended and 16022 for unattended.
About this task
Procedure
Run the command “telnet files.mastercard.com 15022” for testing attended SFTP
and the command "telnet files.mastercard.com 16022" for testing unattended
SFTP.
The output will display the following text: “SSH-2.0-SSHD”.

Testing Procedures
MTF
NOTE: If unable to connect to port 15022 (attended)/ 16022 (unattended), Network

Administration should diagnose why SFTP connection denies access to your system.
Probably, the network firewalls or routers are preventing your system from connecting to
“files.mastercard.com” on port 15022 (attended)/ 16022 (unattended).
MTF
Testing the domain name service for attended or unattended MTF URL
Procedure
3. Run the command “nslookup mtf.files.mastercard.com”.
The output display the following text:
NOTE: In case, output displays:
Non-existent domain?
Contact your Network Administrator to diagnose why your network’s DNS is not able
to resolve the Mastercard File Express URL to its IP address.
What to do next
Once you have resolved the DNS host name for “mtf.files.mastercard.com” to IP
Address 216.119.218.19 and still cannot authenticate, proceed to the Testing SFTP
Connection section.
Perform the test to verify whether a SFTP connection can be made to the
Mastercard File Express server using the host name “mtf.files.mastercard.com”
and port 15022 for attended and 16022 for unattended.
About this task
Procedure

Testing Procedures

3. Run the command “telnet mtf.files.mastercard.com 15022” for testing
attended SFTP and the command "telnet mtf.files.mastercard.com 16022" for
testing unattended SFTP.
The output will display the following text: “SSH-2.0-SSHD”.
NOTE: If unable to connect to port 15022 (attended)/ 16022 (unattended), Network

Administration should diagnose why SFTP connection denies access to your system.
Probably, the network firewalls or routers are preventing your system from connecting
to “mtf.files.mastercard.com” on port 15022(attended)/ 16022 (unattended).

Contact and Support
Contact and Support

For requests for new file transfer setups: contact your regional Mastercard
representative.
• For support during implementation of your File Transfer setup: contact your
assigned Mastercard Implementation Manager.
• For support with existing file transfer setups: contact Mastercard Global
Customer Service at customer_support@mastercard.com.

Notices
Notices
Following are policies pertaining to proprietary rights, trademarks, translations,
and details about the availability of additional information online.
Proprietary Rights
The information contained in this document is proprietary and confidential to Mastercard
International Incorporated, one or more of its affiliated entities (collectively “Mastercard”), or
both.
This material may not be duplicated, published, or disclosed, in whole or in part, without the
prior written permission of Mastercard.
Trademarks
Trademark notices and symbols used in this document reflect the registration status of
Mastercard trademarks in the United States. Please consult with the Global Customer Service
team or the Mastercard Law Department for the registration status of particular product,
program, or service names outside the United States.
All third-party product and service names are trademarks or registered trademarks of their
respective owners.
Disclaimer
Mastercard makes no representations or warranties of any kind, express or implied, with
respect to the contents of this document. Without limitation, Mastercard specifically disclaims
all representations and warranties with respect to this document and any intellectual property
rights subsisting therein or any part thereof, including but not limited to any and all implied
warranties of title, non-infringement, or suitability for any purpose (whether or not Mastercard
has been advised, has reason to know, or is otherwise in fact aware of any information) or
achievement of any particular result. Without limitation, Mastercard specifically disclaims all
representations and warranties that any practice or implementation of this document will not
infringe any third party patents, copyrights, trade secrets or other rights.
Translation
A translation of any Mastercard manual, bulletin, release, or other Mastercard document into a
language other than English is intended solely as a convenience to Mastercard customers.
Mastercard provides any translated document to its customers “AS IS” and makes no
representations or warranties of any kind with respect to the translated document, including,
but not limited to, its accuracy or reliability. In no event shall Mastercard be liable for any
damages resulting from reliance on any translated document. The English version of any
Mastercard document will take precedence over any translated version in any legal proceeding.
Information Available Online

Mastercard provides details about the standards used for this document—including times
expressed, language use, and contact information—on the Publications Support page available
on Mastercard Connect™. Go to Publications Support for centralized information.


File Transfer Manual

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

File Transfer Manual

Uploaded by

Copyright:

Available Formats

File Transfer Manual

Summary of Changes, 22 June 2020............................................................... 6

Chapter 1: File Transfer Overview.................................................................... 7

Chapter 2: File Transfer Mechanisms........................................................... 10

Chapter 3: Getting Started................................................................................ 20

Chapter 4: Proprietary Mastercard Bulk File Transfer

©2020 Mastercard. Proprietary. All rights reserved.

Successful Transfer Dialog..................................................................................... 36

Chapter 5: Third-Party File Transfer Mechanisms and

Chapter 6: Global File Transfer Endpoint and Bulk File Naming

©2020 Mastercard. Proprietary. All rights reserved.

Chapter 7: Mastercard Processing Environments................................. 77

Appendix A: Recovery and Resumption of Service................................ 79

Appendix B: Member Host Preparation Facility..................................... 82

©2020 Mastercard. Proprietary. All rights reserved.

Appendix C: MIP Bulk File Advisement...................................................... 118

Appendix D: Testing Procedures.................................................................... 132

Contact and Support........................................................................................... 140

©2020 Mastercard. Proprietary. All rights reserved.

Summary of Changes, 22 June 2020

Description of Change Where to look at

©2020 Mastercard. Proprietary. All rights reserved.

Chapter 1 File Transfer Overview

About File Transfer............................................................................................................................ 8

©2020 Mastercard. Proprietary. All rights reserved.

About File Transfer

©2020 Mastercard. Proprietary. All rights reserved.

• Endpoints–destination points for customer files (similar in concept to mailbox

File Transfer Reference Information

Mastercard File Express Products

©2020 Mastercard. Proprietary. All rights reserved.

Chapter 2 File Transfer Mechanisms

About File Transfer Mechanisms.................................................................................................. 11

©2020 Mastercard. Proprietary. All rights reserved.

About File Transfer Mechanisms

File Transfer Mechanisms

©2020 Mastercard. Proprietary. All rights reserved.

Mastercard File Express Client

©2020 Mastercard. Proprietary. All rights reserved.

Mastercard File Express Scheduler

©2020 Mastercard. Proprietary. All rights reserved.

Mastercard Interface Processor

©2020 Mastercard. Proprietary. All rights reserved.

IBM – Sterling Connect:Direct

©2020 Mastercard. Proprietary. All rights reserved.

NOTE: Connect:Direct customers wanting transport encryption must order the

Mastercard Data Exchange

©2020 Mastercard. Proprietary. All rights reserved.

Third Party SFTP Client

©2020 Mastercard. Proprietary. All rights reserved.

Secure Delivery File Push (SD File Push)

©2020 Mastercard. Proprietary. All rights reserved.

• Support for SCP with password/SSH Key based authentication.

Comparison of File Transfer Methods

©2020 Mastercard. Proprietary. All rights reserved.

Chapter 3 Getting Started

About File Transfer Options ......................................................................................................... 21

©2020 Mastercard. Proprietary. All rights reserved.

About File Transfer Options

File Transfer Option Selection

About Bulk File Types

©2020 Mastercard. Proprietary. All rights reserved.

File Transfer System Implementation

Step 1—Contact the Customer Operations Services Team