Settlement

Return to Menu

Information about this Replacement Replacement

The October 2006 MDS Settlement and Reports replaces replaces your existing manual.

What is in the new version?

This new version reflects changes effective with MDS Release 06.3. Please refer to: •

•

“Summary of Changes” Changes” for a comprehensive list of changes reflected in this update. “Using this Manual” Manual ” for a complete list of the contents of this manual.

Billing

MasterCard will bill bill principal members members for this document. Please refer to the appropriate MasterCard Consolidated Billing System manual for billing-related information.

Questions?

If you have questions about this manual, please contact the Customer Operations Services team or your regional help desk. Please refer to “Using “ Using this Manual” Manual” for more contact information.

MasterCard is Listening…

Please take a moment to provide us with your feedback about the material and usefulness of the MDS Settlement and Reports using using the following e-mail address: [email protected] We continually strive strive to improve our publications. publications. Your input will help us accomplish our goal of providing you with the information you need.

Summary of Changes MDS Settlement and Reports, October 2006 To locate these changes online —search on the date next to the the revision bar. On the Adobe Reader Reader

toolbar, click Search. Search. In the Search pane, type type Oct 2006 and then click Search. Search. Change Summary Description of Change

Where to Look

Changed name

Entire manual

Added process flow

Reorganized chapter

Changed references to “MasterCard International” with “MasterCard Worldwide”. Added a description and flowchart fl owchart describing the current settlement processing option using the Settlement Account Management (S.A.M.) system. Also modified the processing processing option using GCMS.

Chapter 1

Reorganized chapter 2, Batch Data File, to show the 250-byte Chapter 2 batch data file first, followed by the older 5200 record file format. Also added record headings heading s so that the records will wil l now list in the table of contents.

Updated Batch Data File

Removed switch fees references from the FREC/NREC (Financial/Non-Financial records) and STRL (Settlement Trailer Record) in the Batch Data File. References to switch fees in the the tables have been replaced with ‘Reserved for Future Use’. Noted in the MDS Release 06.3 Document.

Chapter 2 Chapter 3

Modified report SWCHD143

Removed the print line “Debit MasterCard Transactions” on report SWCHD143, Maestro POS Daily Processing Summary.

Chapter 3

Modified the following report samples to display the new BIN Number field supporting Multiple Currency Settlement.:

Chapter 3

Added field to the SWCHD363 and SWCHD412 reports Obsolete report

•

SWCHD363, Daily Control report

•

SWCHD412, Daily Interchange report

Added a note stating that the SWCHD57 and SWCHD108, Chapter 3 Transaction Audit reports reports are obsolete. Members should reference the Batch Data File for the information currently provided on these two reports.

1 of 1

MDS Settlement and Reports October 2006

Copyright The information contained in this manual is proprietary and confidential to MasterCard International Incorporated Incorporated or one of its affiliated affil iated entities (collectively “MasterCard”) and its customer financial institutions. This material may not be duplicated, published, or disclosed, in whole or in part, without the prior written permission of MasterCard. Trademarks Trademark notices and symbols used in this manual reflect the registration status of MasterCard MasterCard trademarks in the United States. Please consult with with the Customer Operations Services team or the MasterCard Law Department for the registration status of particular product, program, or service names outside the United States. All third-party product and and service names names are trademarks trademarks or registered trademarks of their respective owners. Media This document is available: •

On MasterCard OnLine ®

•

On the MasterCard Electronic Library (CD-ROM)

•

On the MDS Suite (CD-ROM)

•

Translated into Spanish

•

Translated into Portuguese

MasterCard Worldwide 2200 MasterCard Boulevard O’Fallon MO 63368-7263 USA 1-636-722-6100 www.mastercard.com www.mastercard.c om

©2006 MasterCard MDS Settlement and Reports

•

October 2006

Publication Code: CN

Table of Contents

Using this Manual Purpose...................................................................................................................1 Audience................................. Audience........ .................................................. .................................................. ................................................. .............................. ...... 1 Overview ................................................................................................................1 Excerpted Text .......................................................................................................2 Language Use ................................................... ......................... ................................................... ................................................... ............................. ... 2 Times Expressed.....................................................................................................2 Revisions.................................................................................................................3 Related Information................................................................................................3 ISO Specifications...................................................................................................4 Support ...................................................................................................................5 Member Relations Representative ...................................................................6 Regional Representative...................................................................................6

Chapter 1

Settlement and Reconciliation Overview .............................................................................................................1-1 Settlement ............................................... ...................... .................................................. ................................................. .................................... ............ 1-1 Processors Connected Connected to the MDS through the Banknet Telecommunications Network......................................................................1-1 Processors Connected Directly to the MDS .............................................. ...................... ........................... ...1-1 1-1 Reconciliation ............................................. ..................... ................................................ ................................................ ................................. ......... 1-2 MDS Settlement Process......................................................................................1-2 MDS End of Day Settlement ...............................................................................1-4 Transaction Settlement Amounts ............................................ .................... ............................................... ............................ .....1-4 1-4 Settling Financial Transactions .....................................................................1-4 Settling Non-financial Transactions.................... Transactions .......................................... .......................................... .................... 1-5 Automated Clearing House House (ACH) and Fedwire Fedwire Settlement Account Account Information..........................................................................................................1-5 ACH Settlement Account Account Information............................. Information.. ..................................................... ............................. ...1-5 1-5 Fedwire Settlement Account Information ....................................................1-6


•

October 2006

i

Table of Contents

GCMS Routing Process........................................................................................1-7 MDS ISO 8583 (1987) 02xx Processor Settlement (GCMS)................................1-7 Settlement Position Record Summaries........................................................1-8 Daily Control Report.....................................................................................1-9 MDS ISO 8583 (1987) 02xx Processor Settlement (S.A.M) ................................1-9 S.A.M Settlement Processing.........................................................................1-9 Daily Control Report...................................................................................1-10 CIS ISO 8583 (1987) 01xx Processor Settlement..............................................1-11 Settlement Total Definitions..............................................................................1-12

Chapter 2

Batch File Specifications Overview .............................................................................................................2-1 MDS Batch Files ..................................................................................................2-1 MDS Report Transmission File .....................................................................2-1 MDS Transaction Detail File ......................................................................... 2-1 General Procedures for Batch Files....................................................................2-2 MDS Batch File Transmission .............................................................................2-2 Data Transmissions ....................................................................................... 2-2 Banknet Network MIP Batch File Transmission ................................................2-3 Dial-Up Data Communication Hardware ...........................................................2-4 Dial-Up Data Communication Software ............................................................. 2-4 Batch File Retransmission ................................................................................... 2-5 Leased Line Processors ................................................................................. 2-5 Virtual Private Network (VPN) or Banknet Connected Processors.............2-5 Batch Data Format/250-byte Record Size...........................................................2-6 Batch Transaction Detail File........................................................................2-6 Batch Record Formats.................................................................................2-12 Previous Batch Data File...................................................................................2-41 MDS Record Formats ..................................................................................2-41 File Structure ...............................................................................................2-42 File Options.................................................................................................2-43 File Update Record—Optional (FIT File)...................................................2-44

ii

October 2006

•


Table of Contents

Sequence of Transmission File...................................................................2-45 MDS Codes..................................................................................................2-48 Batch Message Formats...............................................................................2-53 Batch FIT Data Formats/80-byte Record Size ..................................................2-74

Chapter 3

Reports Overview .............................................................................................................3-1 Report Transmission .....................................................................................3-1 Settlement Reports...............................................................................................3-4 Daily Control Report—SWCHD363 .............................................................. 3-5 Daily Interchange Report—SWCHD412.....................................................3-29 Monthly Control Report—SWCHM363.......................................................3-47 Monthly Interchange Report—SWCHM412................................................3-48 Debit MasterCard Inbound/Outbound Fee Report—SWCHD586-A ......... 3-49 Detail Activity Reports.......................................................................................3-55 Captured Card Report—SWCHD51–Removed...........................................3-57 Exception Audit Report—SWCHD53..........................................................3-58 Detailed Suspect Items Report—SWCHD55...............................................3-67 Transaction Audit Reports—SWCHD57 and SWCHD108..........................3-74 Retrieval Request/Fulfillment Report—SWCHD118...................................3-83 Account File Updates—SWCHD141-1........................................................ 3-89 Account Management File Updates—SWCHD141-2.................................. 3-93 Recurring Payment Cancellation Service—SWCHD141-3..........................3-97 Maestro® POS Transaction Audit Report—SWCHD144..........................3-100 Negative File Updates—SWCHD147-1.....................................................3-105 VIP File Updates—SWCHD147-2 ............................................................. 3-108 Statistical Reports.............................................................................................3-112 Financial Institution Table Report (FIT)—SWCHD15-X .......................... 3-114 Institution Definition File (IDF)—SWCHD35...........................................3-117 Daily Processing Summary Report—SWCHD61 ...................................... 3-119 Monthly Availability Report—SWCHD73 ................................................. 3-125 Daily Cardholder Performance Report—SWCHD127-1...........................3-129 Daily Cardholder Performance Variance Report—SWCHD127-2............ 3-132 Maestro POS Daily Processing Summary—SWCHD143.......................... 3-134 Daily Processor Performance Report—SWCHD320-1 ............................. 3-140


•

October 2006

iii

Table of Contents

Processor Peak Performance Report—SWCHD321-1.............................. 3-144 Processor Daily Summary Performance Report—SWCHD321-2.............3-148 Transaction Interchange Month-to-Date—SWCHM03 ............................. 3-151 Month-to-Date Processing Summary Report—SWCHM06.......................3-155 Month-to-Date Denial Summary Report—SWCHM07 .............................3-161 ISIS Reports......................................................................................................3-164 Stand-In Reports..............................................................................................3-166 Related Reports .........................................................................................3-166 Stand-In Transaction Audit Report—SWCHD149 .................................... 3-168 Processor Availability Reports.........................................................................3-172 Daily Processor Up Time Report (Settlement Date)—MS1100BB...........3-174 Daily Processor Up Time Report (Calendar Date)—MS1100DD.............3-177 Monthly Processor Up Time Report —MS1101AA ..................................3-179 Month-to-Date Report—MS1101BB..........................................................3-181

iv

October 2006

•


Using this Manual This chapter contains information that helps you understand and use this document.

Purpose...................................................................................................................1 Audience.................................................................................................................1 Overview ................................................................................................................1 Excerpted Text .......................................................................................................2 Language Use .........................................................................................................2 Times Expressed.....................................................................................................2 Revisions.................................................................................................................3 Related Information................................................................................................3 ISO Specifications...................................................................................................4 Support ...................................................................................................................5 Member Relations Representative ...................................................................6 Regional Representative...................................................................................6


•

October 2006

i

Using this Manual Purpose

Purpose The MasterCard MDS Settlement and Reports manual is one of the four manuals comprising the MasterCard® Debit Switch Suite. The MasterCard® Debit Switch Suite consists of: •

MDS Online Specifications

•

MDS Programs and Services

•

MDS Settlement and Reports

•

NICS Users’ Guide

The MDS Settlement and Reports manual serves as one of the primary technical references for all debit programs and services supported by MasterCard.

Audience MasterCard provides this manual for members and their authorized agents. Specifically, the following personnel should find this manual useful: •

MasterCard members directly connected to the MasterCard® Debit Switch

•

Third party processors directly connected to the MasterCard ® Debit Switch

Overview The following table provides an overview of this manual: Chapter

Description

Table of Contents

A list of the manual’s chapters and subsections. Each entry references a chapter and page number.

Using this Manual

A description of the manual’s purpose and its contents.

1

Settlement and Reconciliation

Illustrates and describes the settlement and reconciliation processes for debit MasterCard®, Cirrus®, and Maestro® transactions.

2

Batch File Specifications

Defines options and formats for receiving batch data fi les to assist in settlement, reconciliation, and reporting at the processor or institution level.

3

Reports

Provides detailed description and examples of reports produced by the MasterCard® Debit Switch.


•

October 2006

1

Using this Manual Excerpted Text

Excerpted Text At times, this document may include text excerpted from another document. A note before the repeated text always identifies the source document. In such cases, we included the repeated text solely for the reader’s convenience. The original text in the source document always takes legal precedence.

Language Use The spelling of English words in this manual follows the convention used for U.S. English as defined in Merriam-Webster’s Collegiate Dictionary . MasterCard is incorporated in the United States and publishes in the United States. Therefore, this publication uses U.S. English spelling and grammar rules. An exception to the above spelling rule concerns the spelling of proper nouns. In this case, we use the local English spelling.

Times Expressed MasterCard is a global company with locations in many time zones. The MasterCard operations and business centers are in the United States. The operations center is in St. Louis, Missouri, and the business center is in Purchase, New York. For operational purposes, MasterCard refers to time frames in this manual as either “St. Louis time” or “New York time.” Coordinated Universal Time (UTC) is the basis for measuring time throughout the world. You can use the following table to convert any time used in this manual into the appropriate time in another zone:

Standard time

St. Louis, Missouri USA

Purchase, New York USA

Central Time

Eastern Time

09:00

10:00

15:00

09:00

10:00

14:00

UTC

(last Sunday in October to the first Sunday in April a) Daylight saving time

(first Sunday in April to last Sunday in October) a

2

For Central European Time, last Sunday in October to last Sunday in March.

October 2006

•


Using this Manual Revisions

Revisions MasterCard periodically will issue revisions to this document as we implement enhancements and changes, or as corrections are required. With each revision, we include a “Summary of Changes” describing how the text changed. Revision markers (vertical lines in the right margin) indicate where the text changed. The month and year of the revision appear at the right of each revision marker. Occasionally, we may publish revisions or additions to this document in a Global Debit Operations Bulletin or other bulletin. Revisions announced in another publication, such as a bulletin, are effective as of the date indicated in that publication, regardless of when the changes are published in this manual.

Related Information The following documents and resources provide information related to the subjects discussed in this manual. For descriptions of these documents, please refer to the List of Manuals in the Member Publications product on MasterCard OnLine®. 2

• • • • • • • • • • • •

Chargeback Guide Cirrus ® Worldwide Operating Rules Data Communications Manual Maestro ® Global Rules MasterCard Consolidated Billing System MasterCard Debit Financial Simulator MasterCard Member ICC Testing Procedures—Debit MDS Online Specifications MDS Programs and Services NICS Users’ Guide Payment Card Industry PIN Security Requirements Settlement Manual

Debit members that also process transactions using the Authorization (01xx) message format should reference the above manuals and the following manuals: • •

Authorization System Manual Account Management User Manual


•

October 2006

3

Using this Manual ISO Specifications

Members that use the Cirrus® service and logo or that process online debit transactions should refer to the debit processing manuals recommended by the Customer Operations Services team. For definitions of key terms used in this document, please refer to the MasterCard Dictionary on the Member Publications home page (on MasterCard OnLine® and the MasterCard Electronic Library CD-ROM). To order MasterCard manuals, please use the Ordering Publications service on MasterCard OnLine®, or contact the Customer Operations Services team.

ISO Specifications

Oct 2006

The message format specifications used by MasterCard Worldwide are based on the International Organization for Standardization (ISO) 8583-1987. These message specifications also comply with the recommendations of the American National Standards Institute (ANSI) committees for electronic funds interchange, where their recommendations are appropriate and do not conflict with the international scope of MasterCard Worldwide business and operational requirements.

4

October 2006

•


Using this Manual Support

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

Phone:

1-636-722-6292 (Spanish language support) 1-636-722-7192

Fax:

Canada, Caribbean, Latin America, South Asia/Middle East/Africa, and U.S.

E-mail:

[email protected]

Asia/Pacific: Australia and New Zealand

[email protected]

China, Hong Kong, and Taiwan

[email protected]

South East Asia

[email protected]

Japan/Guam Korea

[email protected] [email protected]

Europe

[email protected]

Spanish language support

[email protected]

Vendor Relations, all regions [email protected] Address:

MasterCard Worldwide Customer Operations Services 2200 MasterCard Boulevard O’Fallon MO 63368-7263 USA

Telex:

434800 answerback : 434800 ITAC UI


•

October 2006

5

Using this Manual Support

Member Relations Representative Member Relations representatives assist U.S. members with marketing inquiries. They interpret member requests and requirements, analyze them, and if approved, monitor their progress through the various MasterCard departments. This does not cover support for day-to-day operational problems, which the Customer Operations Services team addresses. For the name of your U.S. Member Relations representative, contact your local Member Relations office: Atlanta Chicago Purchase San Francisco

1-678-459-9000 1-847-375-4000 1-914-249-2000 1-925-866-7700

Regional Representative The regional representatives work out of the regional offices. Their role is to serve as intermediaries between the members and other departments in MasterCard. Members can inquire and receive responses in their own languages and during their offices’ hours of operation. For the name of the location of the regional office serving your area, call the Customer Operations Services team at: Phone:

1-800-999-0363 or 1-636-722-6176 1-636-722-6292 (Spanish language support)

6

October 2006

•


1

Settlement and Reconciliation This chapter provides a description of the settlement and reconciliation processes of MasterCard ATM, Debit MasterCard, Cirrus, and Maestro financial and non-financial transactions.

Overview ............................................................................................................. 1-1 Settlement ............................................................................................................ 1-1 Processors Connected to the MDS through the Banknet Telecommunications Network...................................................................... 1-1 Processors Connected Directly to the MDS ................................................. 1-1 Reconciliation ...................................................................................................... 1-2 MDS Settlement Process...................................................................................... 1-2 MDS End of Day Settlement ............................................................................... 1-4 Transaction Settlement Amounts ........................................................................ 1-4 Settling Financial Transactions ..................................................................... 1-4 Settling Non-financial Transactions.............................................................. 1-5 Automated Clearing House (ACH) and Fedwire Settlement Account Information.......................................................................................................... 1-5 ACH Settlement Account Information.......................................................... 1-5 Fedwire Settlement Account Information .................................................... 1-6 GCMS Routing Process........................................................................................ 1-7 MDS ISO 8583 (1987) 02xx Processor Settlement (GCMS)................................1-7 Settlement Position Record Summaries........................................................ 1-8 Daily Control Report..................................................................................... 1-9 MDS ISO 8583 (1987) 02xx Processor Settlement (S.A.M.) ...............................1-9 S.A.M Settlement Processing......................................................................... 1-9 Daily Control Report................................................................................... 1-10 CIS ISO 8583 (1987) 01xx Processor Settlement..... ......................................... 1-11 Settlement Total Definitions.............................................................................. 1-12


•

October 2006

1-i

Settlement and Reconciliation Overview

Overview The MDS Settlement and Reports manual for the settlement and reconciliation process describes MasterCard ATM, Debit MasterCard®, Cirrus®, and Maestro® financial and non-financial transactions.

Settlement Acquirer and issuer processors are responsible for individual settlement with terminal owners and card issuers; the MDS settles only with each processor, unless the processor supports the Member Level Settlement option. Refer to the MDS Programs and Services manual for additional information on member level settlement. Chapter 3 of this document describes MDS Settlement reports.

Oct 2006

Oct 2006

Processors Connected to the MDS through the Banknet Telecommunications Network Each CPS connected to the MDS through an online Customer Interface Specification (CIS) interface to the Banknet® telecommunications network receives Integrated Product Messages (IPM) clearing data reflecting settlement data in accordance with standard MasterCard procedures.

Oct 2006

Processors Connected Directly to the MDS Each CPS connected directly to the MDS must perform clearing and settlement determination processing in accordance with the procedures established by the MDS.


•

October 2006

1-1

Oct 2006

Settlement and Reconciliation Reconciliation

Reconciliation The MDS provides reconciliation data for processors through batch detail transmission files (raw data files) and various MDS transaction detail reports (pre-formatted bulk file reports). In this manual, Chapter 2 describes the file format specifications for the MDS batch detail transmissions and Chapter 3 describes the MDS reports.

Oct 2006

MasterCard encourages processors to develop an automated process to compare batch detail files (generated and transmitted by MDS) to the internal batch records (maintained by the processor). The automated compare process will highlight any balancing differences the member can research using the MDS reports. Each processor is responsible for a daily reconciliation of its internal batch totals to the settlement totals provided by MDS.

MDS Settlement Process For specific information about settlement options and processing, refer to the MasterCard Settlement Manual . The following options are available in the MDS Settlement process. •

Regional Settlement −

ACH Clearing Account Available to Maestro® and Cirrus® processors and members connected to MDS who settle in U.S. dollars.

−

MasterCard’s Settlement Account Management (S.A.M.) Available to Maestro®, Cirrus®, and Debit MasterCard® processors and members who wish to settle in U.S. dollars or one of the other settlement currencies supported by MasterCard.

•

Intracurrency Settlement −

−

1-2

Processors/members must participate in GCMS clearing May receive IPM clearing Financial Detail/1240 message or IPM clearing Fee Collection/1740 message.

October 2006

•


Oct 2006

Settlement and Reconciliation MDS Settlement Process

Depending upon the online interface, the MDS can settle with each processor in one of the following ways. Table 1.1—Settlement /Clearing Options Settlement Process ACH Clearing Account Settlement Account Management system (S.A.M.) Fedwire Account

Description Maestro® and Cirrus® processors and members connected to MDS settling in U.S. dollars. •

MDS will send daily settlement positions directly to S.A.M. for processors that use MDS ISO 8583 Financial Transaction/0200 messages through the Banknet network and participating in the MDS multiple currency option. Refer to the MDS Programs and Services manual for additional information on the MDS multiple currency settlement option.

•

MDS will send daily settlement positions using IPM formatted Miscellaneous Summary (1740) records to GCMS for processors that use MDS 8583 Financial Transaction/0200 messages through the Banknet network and not participating in the MDS multiple currency option. GCMS will pass the settlement positions to S.A.M. Refer to the MDS Programs and Service s manual for additional information on the MDS multiple currency settlement option.

•


•

October 2006

For processors using the CIS ISO 8583 Authorization Request/0100 messages through the Banknet network. Settlement will result from GCMS processing GCMS Financial Detail records (1240) and passing the settlement positions to S.A.M.

1-3

Oct 2006

Settlement and Reconciliation MDS End of Day Settlement

MDS End of Day Settlement The MDS settles transactions received after the settlement day end on the next MDS business day.

Oct 2006

Table 1.2—MDS Settlement Day Ends Debit MasterCard®

07:00 New York time

Maestro®/Cirrus®

15:00 New York time

Settlement Service (Brazil intracurrency)

23:00 New York time Oct 2006

Processors must reconcile with the MDS based upon the MDS end of day settlement date transmitted in the online transaction request message. It is the responsibility of the processor to maintain any necessary reconciliation files. Processors may find the settlement totals presented by the MDS differ from their calculated settlement totals. In these instances, the processor must accurately account for any unreconciled items.

Transaction Settlement Amounts The transaction settlement amount is the amount of the transaction settled between processors. The MDS calculates this amount during offline batch processing.

Settling Financial Transactions The settlement amount calculation uses the following formula f or financial transactions: Credit Acquiring Processor Interchange Settlement

(Financial Settlement +/- Reversal + Interchange fees) minus Debit Issuing Processor Interchange Settlement

(Financial Settlement +/- Reversal + Interchange fees) equals Net Settlement Amount



1-4

Note

Refer to the SWCHD363 Daily Control Report for a detailed calculation of the net settlement amount.

October 2006

•


Oct 2006

Settlement and Reconciliation Automated Clearing House (ACH) and Fedwire Settlement Account Information

Settling Non-financial Transactions The settlement amount for non-financial transactions (balance inquiries, transfers and denials) are calculated using the following formula: Settlement Amount = transaction interchange fee amounts.



Note

For ATM transactions, the acquirer receives interchange fees and the issuer is charged interchange fees. In a POS environment, the issuer is credited interchange fees, and the acquirer pays interchange fees.

Automated Clearing House (ACH) and Fedwire Settlement Account Information The following sections provide information about Automated Clearing House (ACH) and Fedwire settlement accounts.

ACH Settlement Account Information Oct 2006

Automated Clearing House (ACH) payments system is an association of financial institutions that have networked together to exchange (clear and settle) electronic transactions. Processors electing to receive settlement through the ACH service must provide the following settlement account information on the Processor Information Questionnaire (PIQ) to the MDS during the sign-up and implementation process: •

•

•



Note

Name of the receiving financial institution Federal Reserve route and transit number of the receiving financial institution Account number to be used as the “settlement clearing” account

Processors must select a settlement bank in the United States to establish an ACH account.


•

October 2006

1-5

Settlement and Reconciliation Automated Clearing House (ACH) and Fedwire Settlement Account Information

Fedwire Settlement Account Information The Fedwire funds transfer system is owned and operated by the Federal Reserve System (the United States Central Bank). A financial institution that maintains an account with a Federal Reserve Bank may become a Fedwire participant. Participants use Fedwire to instruct a reserve bank to debit funds from their account and to credit the reserve account of another participant.

Oct 2006

Debit MasterCard processors receive settlement through a Fedwire. These processors provide the following settlement account information on the Net Settlement Agreement (NSA) to the MDS during the sign-up and implementation process: •

•

•



Note

Name of the receiving financial institution Federal Reserve routing and transit number of the receiving financial institution Account number to be used as the “settlement clearing” account

Processors must select a settlement bank in the United States that is a participant of the Central Bank. For details on completing an NSA form, refer to the MasterCard Manual .

Settlement

Figure 1.1 shows the settlement process for processors settling through ACH or Fedwire. Figure 1.1—Settlement Routing Process Using ACH or Fedwire

MDS

1-6

ACH/Fedwire

ACH/Fedwire

ACH/Fedwire

CR/DR

CR/DR

CR/DR

Fed er al R es er ve B an k

Se tt lem en t I ns ti tu ti on

October 2006

•

APS/IPS


Oct 2006

Settlement and Reconciliation GCMS Routing Process

Oct 2006

GCMS Routing Process GCMS is a centralized clearing facility owned and operated by MasterCard for the daily processing and routing of worldwide financial transactions between MasterCard and its members. To use GCMS, the processor must supply an ICA number. The member ID/ICA number is a unique six-digit identification number assigned by MasterCard to a processor or institution. Figure 1.2 shows the settlement information routing process for processors settling through GCMS. Figure 1.2—Settlement Position Routing Process Using GCMS

Oct 2006

MDS ISO 8583 (1987) 02xx Processor Settlement (GCMS) Processors connected through the Banknet ® telecommunications network and not participating in MDS multiple currency settlement processing will receive settlement information through the IPM 1740 Fee Collection record totals. Processors receive their net financial settlement totals and net interchange fee totals in individual GCMS records. GCMS records are contained in R111 bulk files.



Note

Processors connected to the Banknet telecommunications network, and electing to receive IPM 1740 may use the Processor Information Questionnaire (PIQ) to sign-up for these records.


•

October 2006

1-7

Settlement and Reconciliation MDS ISO 8583 (1987) 02xx Processor Settlement (GCMS)

The processor’s bulk file may contain up to five records summarizing the processor’s activity for the settlement day. Two for the processor’s acquiring activity and three for the processor’s issuing activity. The number of records depends on whether the processor is an issuer, an acquirer, or both. The MDS’ ICA is 2202 and is always the sending ICA. The MDS’ ICA generates the GCMS 1740 and transmits the settlement record to the processor’s receiving ICA. MasterCard collectively refers to these settlement records as the Daily Records and includes them in the bulk file. Each Daily Record contains the following identifying fields: •

Transaction Originator Institution ID Code (DE 94) = 2202

•

Message Reason Code (DE 25) = 7804

•

Oct 2006

Oct 2006

Processing Code (DE 3, subfield 1) = 19 to indicate a credit to the receiving member’s ICA Or,

•



Note

Processing Code (DE 3, subfield 1) = 29 to indicate a debit to the receiving member’s ICA

01xx interface issuers will see settlement records named Fees for Financial and Non-financial Transactions Settlement Fees. Intracurrency settlement members will see settlement records for net of financial settlement amounts, NETAM (acquirer and issuer side), and interchange fees (acquirer and issuer side).

Oct 2006

Settlement Position Record Summaries Table 1.3 lists the settlement position record summaries. Table 1.3—Transaction Settlement Record Summaries

1-8

Summary Information Provided in Record

IPM Heading Data Record (DE 72)

Maestro/Cirrus Acquiring—Net Transaction Amount

NETAQ

Cirrus Acquiring—Interchange Fee

FEEAQ

Maestro/Cirrus Issuing—Net Transaction Amount

NETAM

Cirrus Issuing—Interchange Fee

FEES

October 2006

Oct 2006

•


Settlement and Reconciliation MDS ISO 8583 (1987) 02xx Processor Settlement (S.A.M.)



Note

The “NETAQ” and “NETAM” 1740 records in the R111 file integrate the Maestro financial transaction settlement with the Cirrus financial transaction settlement.

Daily Control Report Processors should reconcile to the MDS Daily Control Report (SWCHD363) contained in their T461 bulk file (for settlement amounts as an acquiring or issuing processor, or both). The settlement amounts on the report should match the amounts transmitted in the settlement records. Refer to the Reports chapter of this manual for field descriptions and sample report layouts for the SWCHD363 report.

MDS ISO 8583 (1987) 02xx Processor Settlement (S.A.M.) Processors connected through the Banknet ® telecommunications network using the MDS multiple currency settlement process receive settlement through the Settlement Account Management (S.A.M.) system.

S.A.M Settlement Processing Settlement Account Management (S.A.M.) system is a Windows®-based clientserver software application designed to streamline the process of moving funds. Funds are exchanged based on the net value of all cleared financial transactions for each settlement day. The net value may include the following: •

Transaction amounts processed through the clearing system(s)

•

Cash disbursement and ATM cash disbursement accommodation fees

The MDS multiple currency settlement process enables MasterCard to convert the transaction amounts received into the member’s selected settlement currency, and then send the converted amounts directly to the MasterCard Settlement Account Management (S.A.M) system, eliminating the need for GCMS records.


•

October 2006

1-9

Oct 2006

Settlement and Reconciliation MDS ISO 8583 (1987) 02xx Processor Settlement (S.A.M.)

Oct 2006

Figure 1.3 shows the data flow for processing directly with S.A.M. Figure 1.3—Settlement Process Using S.A.M.

T461 (Batch)

T462 (Report)

T461 (Batch)

Banknet Network

T462 (Report)

APS/IPS MIP

MDS



Note

Settlement

S.A.M.

This option is not available for intracurrency settlement activity.

Daily Control Report Processors should reconcile to the MDS Daily Control Report (SWCHD363) contained in their T461 bulk file (for settlement amounts as an acquiring or issuing processor, or both). The settlement amounts on the report should match the amounts on the settlement advisement. Refer to the Reports chapter of this manual for field descriptions and sample report layouts for the SWCHD363 report.

1-10

October 2006

•


Settlement and Reconciliation CIS ISO 8583 (1987) 01xx Processor Settlement

CIS ISO 8583 (1987) 01xx Processor Settlement Processors using the CIS ISO 8583 Authorization Request/0100 message series for MasterCard/Cirrus ATM transaction activity receive settlement through IPM 1240 First Presentment records. These records are used to post transactions to cardholders’ accounts. Processors may request these records by using the Processor Information Questionnaire. The processor must supply an ICA number for each FIT/institution prefix. Figure 1.4 shows the data flow for processors settling through IPM detail.

Oct 2006

Figure 1.4—Settlement Process

Processors using 01xx messages receive settlement through IPM 1740 Fee Collection record totals. These records include the financial and non-financial transaction interchange fees for MasterCard ATM transactions.


•

October 2006

1-11

Settlement and Reconciliation Settlement Total Definitions

Settlement Total Definitions Table 1.4 describes the settlement totals calculations. Table 1.4—Settlement Totals Calculations Term

Definition

Total debit amount

The sum of transaction completion amounts from debit financial transactions.

Total credit amount

The sum of transaction completion amounts from credit financial transactions.

Reversal debit amount

The sum of reversal amount debits from reversal transactions.

Reversal credit amount

The sum of reversal amount credits from reversal transactions.

Table 1.5 describes the interchange totals for the acquirer processing system calculations. Table 1.5—Interchange Totals for the Acquirer Processing System Calculations Term

Definition

Interchange amount-CR

The sum of settlement amounts from credit financial transactions and credit reversal transactions.

Interchange amount-DR

The sum of settlement amounts from debit financial transactions, debit reversal transactions, and inquiry transactions.

Table 1.6 describes the interchange totals for the issuer processing system calculations. Table 1.6—Interchange Totals for the Issuer Processing System Calculations

1-12

Term

Definition

Interchange amount-DR

Sum of settlement amounts from debit financial transactions, debit reversal transactions, and inquiry transactions.

Interchange amount-CR

The sum of settlement amounts from credit financial transactions and credit reversal transactions.

October 2006

•


2

Batch File Specifications This chapter describes the two different types of batch data files provided to the Customer Processing System (CPS).

Overview .............................................................................................................2-1 MDS Batch Files ..................................................................................................2-1 MDS Report Transmission File .....................................................................2-1 MDS Transaction Detail File .........................................................................2-1 General Procedures for Batch Files....................................................................2-2 MDS Batch File Transmission .............................................................................2-2 Data Transmissions .......................................................................................2-2 Configuration Options............................................................................2-3 Banknet Network MIP Batch File Transmission ................................................2-3 Dial-Up Data Communication Hardware ...........................................................2-4 Dial-Up Data Communication Software .............................................................2-4 Batch File Retransmission ...................................................................................2-5 Leased Line Processors .................................................................................2-5 Virtual Private Network (VPN) or Banknet Connected Processors.............2-5 Batch Data Format/250-byte Record Size...........................................................2-6 Batch Transaction Detail File........................................................................2-6 Batch File Structure.................................................................................2-7 Sequence of Transmission File...............................................................2-8 Batch Record Formats.................................................................................2-12 File Header Record (FHDR)—Required...............................................2-12 Settlement Header Record (SHDR)—Required....................................2-13 Financial (FREC)/Non-financial (NREC) Records—Required..............2-14 Financial/Non-financial Posting Addendum Record (FPST) —Optional.............................................................................................2-19 Financial/Non-financial Fee Addendum Record (FEER) —Optional.............................................................................................2-20 Financial/Non-financial Debit MasterCard Addendum Record (DBMC)—Optional ...............................................................................2-21


•

October 2006

2-i


Financial/Non-financial Debit MasterCard Airline Ticket Addendum Record (AIRA)—Optional .................................................2-23 Financial/Non-financial Parcelas Addendum Record (PARC) —Optional.............................................................................................2-24 Financial/Non-financial Maestro CDC Addendum Record (MCDC)—Optional ...............................................................................2-25 Financial/Non-financial Maestro Post Dated Addendum Record (MPDT)—Optional...................................................................2-26 Financial/Non-financial Maestro Installment Addendum Record (MIST)—Optional..................................................................................2-27 Financial/Non-financial Additional Data Addendum Record (ADDR)—Optional................................................................................2-29 Financial/Non-financial Exception Record (EREC)—Required...........2-30 Financial/Non-financial Exception Record (EPST)—Optional............2-34 Settlement Trailer Record (STRL)—Required.......................................2-36 Interchange Compliance Issuer Detail Adjustment Record (INTC)—Required.................................................................................2-39 File Trailer Record (FTRL)—Required..................................................2-40 Previous Batch Data File...................................................................................2-41 MDS Record Formats ..................................................................................2-41 File Structure ...............................................................................................2-42 File Header Record—Required.............................................................2-42 Financial/Non-financial and Exception Item Record ..........................2-42 File Options.................................................................................................2-43 File Control Record—Required ............................................................2-44 Settlement Record—Required...............................................................2-44 File Update Record—Optional (FIT File)...................................................2-44 Full File Replacement ...........................................................................2-44 File Update Versions.............................................................................2-44 Sequence of Transmission File...................................................................2-45 MDS Codes ..................................................................................................2-48 Response Codes....................................................................................2-48 Processing Codes..................................................................................2-50 Completion Codes ................................................................................2-52 Completion Code Position Status...................................................2-52 Completion Code Values................................................................2-52 Batch Message Formats...............................................................................2-53 File Header Record...............................................................................2-53 Financial/Non-financial (5220) Record ................................................2-54 Airline Ticket Number and Additional Itinerary Data .........................2-59

2-ii

October 2006

•



Exception Transaction (5240) Record..................................................2-60 File Control (5499) Record ...................................................................2-66 Settlement (5500) Record .....................................................................2-67 80-byte FIT File with Country Code (5300) Record ............................2-69 80-byte FIT File without Country Code (5300) Record.. .....................2-72 Batch FIT Data Formats/80-byte Record Size ..................................................2-74 FIT Header Record (FITH)—Required.................................................2-75 FIT Data Records (FITD)—Optional....................................................2-75 FIT Trailer Record (FITT)—Required...................................................2-78


•

October 2006

2-iii

Batch File Specifications Overview

Overview The MasterCard®D ebit Switch (MDS) provides two different types of batch data files to the customer processing system (CPS) that participates in one or more electronic file transfer (EFT) programs offered by the MDS. The MDS provides this batch file data to assist CPS and individual EFT program members with their internal Customer Service, Settlement, and Reconciliation operations.

MDS Batch Files The two types of batch files provided by the MDS are: •

MDS Report Transmission Files

•

MDS Transaction Detail Files

MDS Report Transmission File The MDS Report Transmission File is a preformatted print-output file of the daily and month-to-date MDS-generated reports. A single MDS Report Transmission File format is used to create the MDS reports for the processor processing through the Banknet telecommunications network (Chapter 3 of this manual details the actual MDS reports). The processor will receive: •

Production Bulk ID T461

•

MDS Member Test Bulk ID T467

MDS Transaction Detail File The MDS produces a daily file of all transaction activity for each CPS participating in an EFT program. These records, including summary “count and amount” totals and daily settlement records, are available to CPS for their use in settlement reconciliation processing. Processors that process through the Banknet telecommunications network will receive: •


•

MDS Member Test Bulk ID T468


•

October 2006

2-1

Batch File Specifications General Procedures for Batch Files

General Procedures for Batch Files MDS batch data files transmit no earlier than 10:00 p.m. U.S. Eastern Time (3:00 a.m. UT) seven days a week. The MDS transmits data using dial up lines from the MDS, leased lines, or the Banknet network bulk data transfer facility. To assist in data recovery, the MDS maintains “cycles” (for example, business days) of transaction detail and report data for each CPS in production. If a processor encounters problems, they can request a retransmission of data files (report and detail) for the specific cycle where the problem occurred.

MDS Batch File Transmission The MDS provides optional electronic transmission of transaction detail and report data files.

Data Transmissions The MDS supports external complex-to-complex batch file data transmission with various MasterCard supported protocols. A proprietary data communication software product developed by MasterCard, MasterCard File Express, enables processors to download and upload production and test files from the MDS to CPS, retrieve archived files, generate a file transmission report, and print the file transmission report to the CPS printer or preview it from the MasterCard File Express application. Following is a list of file transfer products used for data transmissions: File Transfer Products developed by MasterCard •

MasterCard File Express Client

•

MasterCard File Express Scheduler (batch mode only)

File Transfer Products developed by Sterling Commerce •

Connect: Direct (also known as NDM)

•

Connect: Enterprise (also known as SuperTRACs)

•

Connect: Gateway (Connect: Gateway add-on product for ASCII file transfers)

File Transfer Product developed by Computer Associates •

2-2

CA-XCOM (also known as XCOM 6.2)

October 2006

•


Oct 2006

Batch File Specifications Banknet Network MIP Batch File Transmission

Configuration Options 1. Connect: Direct-to-Connect: Direct (all leased line network connections) •

Mainframe-to-Mainframe VPN over TCP/IP (preferred option)

•

Mainframe-to-Mainframe SNA/SNI over VPN (next best option)

•

Mainframe-to-Mainframe SNA/SNI (Token-Ring, bisync)

•

Mainframe-to-Mainframe TCP/IP over Ethernet

2. Connect: Enterprise-to-Connect: Enterprise •

Leased Line (Mainframe-to-Mainframe SNA/SNI, bisync)

•

Dial Line (bisync)

3. Connect: Mailbox-to-Other 2780/3780 Emulators •

Leased Line (Mainframe-to-Mainframe SNA/SNI, bisync)

•

Dial Line (bisync)

4. Connect: Gateway-to-ASCII Servers or PC Workstations Leased Line or Dial (Mainframe-to-ASYNC server using the following ASCII protocols: Kermit, Zmodem, Ymodem, and Xmodem) 5. MFE-to-PC Workstations Dial Line, Internet, or VPN using MasterCard Online®E nterprise Edition (data exchanged using TCP protocol, data encrypted at 128-bit key encryption, data compressed using Run Length Encoding algorithm, users authenticated through SecurID token)

Banknet Network MIP Batch File Transmission Customer processing systems that use the Banknet network MIP Bulk Data Facility (T461/T462 files) for batch data file transmission must refer to the Data Communications Manual for all technical specifications. Refer to the “Using this Manual” chapter of this publication for information on how to obtain copies of the Data Communications Manual .


•

October 2006

2-3

Batch File Specifications Dial-Up Data Communication Hardware

Dial-Up Data Communication Hardware MDS batch data file transmissions operate at nominal rates of 9.6 to 19.2 KBPS in the dial-up mode. The MDS bases the acceptability of a CPS data communication modem for data transfer on results of communication testing that the MDS conducts during CPS acceptance testing. Processors must complete all acceptance testing before production processing of batch file data. Any changes to a CPS facility’s modem equipment requires additional acceptance testing with the MDS.

Dial-Up Data Communication Software CPS facilities that want batch data file transmission using 3780/2780 communication must employ software subsystems that are fully compatible with the IBM 3780/2780 communication standard. The MDS requires that the processor test the 3780/2780 software used by a CPS for suitability and compatibility before production data file transmission. The MDS bases the acceptability of data communication software on results of communication testing that the MDS conducts during acceptance testing. If serious performance problems or errors occur after the processor initiates production processing, the MDS may require a CPS facility to perform additional acceptance testing of its data transmission software with the MDS.

2-4

October 2006

•


Batch File Specifications Batch File Retransmission

Batch File Retransmission The following information applies to retransmission of data files.

Leased Line Processors After a data transmission failure, a processor can request the retransmission of the production file within 30 calendar days of the original transmission date. For acceptance testing, there is a five-day window for retransmission. Processors should contact MasterCard Worldwide Customer Operations Services to request a retransmission.

Oct 2006

Phone: 1-636-722-6405

Virtual Private Network (VPN) or Banknet Connected Processors After a data transmission failure, a processor can request the retransmission of the production file within 30 calendar days of the original transmission date. For acceptance testing, there is a 30-day window for retransmission. Processors in the U.S. should contact MasterCard Worldwide Customer Operations Services to request a retransmission. Phone: 1-636-722-6405

Processors in all other regions should contact their Regional Help Desk to request a retransmission.


•

October 2006

2-5

Oct 2006

Batch File Specifications Batch Data Format/250-byte Record Size

Batch Data Format/250-byte Record Size This chapter provides detail record layouts for the 250-byte Batch Data File and the layout for the Financial Institution Table (FIT) 80-byte Data File. Processors using the 250-byte Batch Data File must receive the 80-byte FIT Data File. Processors may receive the 80-byte FIT Data File before completing the conversion to the 250-byte Batch Data File. The 250-byte format supports financial, non-financial, and addendum records. Each record layout is displayed with the appropriate fields and corresponding attributes from the online transaction processing log file used to create the records. The values in the Comments and Values column are generated from the online messages, unless otherwise indicated, except interchange fees which are calculated in batch. Transaction records are sorted by settlement currency, PAN, and Switch Serial Number.



Note

The 250-byte Batch Data File records are provided to processors in the credit/debit position of the transactions as they are settled to either the acquirer or issuer. Debits to issuers are presented as credits to acquirers, and credits to issuers are presented as debits to acquirers. The 250-byte Batch Data File also provides a n et settlement record in addition to the acquirer and issuer settlement records in the file. When the file contains both acquirer and issuer activity, the net settlement record represents the net of both these positions. This net settlement record provides information useful for reconciling and validating to MasterCard Debit Switch (MDS) reports.

Batch Transaction Detail File The 250-byte Batch Data File is available for each CPS participating in an EFT program. Processors that process through the Banknet telecommunications network will receive the Batch Data Files as:

2-6

•


•

Member Test Bulk ID T470

October 2006

•


Oct 2006

Oct 2006


Batch File Structure Each record in the 250-byte Batch Data File format is identified by a Message Type Indicator (MTI) in the first four (4) positions of the record. The following MTI’s indicate standardr ecords and are always provided in the Batch Data File when it contains records. Table 2.1—Valid Values for Message Type Indicators (MTI)—Standard Value

Message Type Indicators

FHDR

File Header Record

FREC

Financial Record

NREC

Non-financial Record

EREC

Exception Record

SHDR

Settlement Header Record

STRL

Settlement Trailer Record

INTC

Interchange Compliance Record

FTRL

File Trailer Record

FITH

FIT Header Record

FITD

FIT Data Record

FITT

FIT Trailer Record

The following addendum records are optional. These records are provided only if the processor has chosen to receive them. The values for the addendum indicators in positions 1–4 are as follows: Table 2.2—Valid Values for Message Type Indicators (MTI)—Optional Addendum Segments Value


FPST

Financial/Non-financial Posting Addendum Record

EPST

Financial Exception Posting Addendum Record

FEER

Financial/Non-financial Fee Addendum Record

DBMC

Financial/Non-financial Debit MasterCard Addendum Record

AIRA

Financial/Non-financial Debit MasterCard Airline Ticket Addendum Record

PARC

Financial/Non-financial Parcelas Addendum Record (Available For Brazil Only)


•

October 2006

2-7

Oct 2006


Value


MCDC

Financial/Non-financial Maestro CDC Addendum Record (Available For Brazil Only)

MPDT

Financial/Non-financial Maestro Post Dated Addendum Record (Available for Brazil Only)

MIST

Financial/Non-financial Maestro Installment Payment Addendum Record (Available for Brazil Only)

ADDR

Financial/Non-financial Additional Data Addendum Record

Sequence of Transmission File The Batch Data File transmission lists the acquirer information, followed by the issuer information. A separate Settlement Trailer record is present for each currency with representative transaction settlement. Processors receiving the file as both an acquirer and issuer receive one Settlement Trailer record as acquirer, one Settlement Trailer record as issuer, and one Settlement Trailer record with the net of acquirer and issuer positions reported. Each record is identified as A (acquirer), I (issuer), or N (net) settlement. This information is essential to the reconciliation process used by processors. Financial, Nonfinancial, and Exception Records appear in the file as records for a particular settlement date. Table 2.3—Sample Transmission without Transactions

2-8

Description

Comments

File Header Record (FHDR)

This required record contains processor i dentification data.

Settlement Trailer Record (STRL)

This record contains settlement position at a processor level by settlement currency. This record will be represented as N net settlement position.

Financial Trailer Record (FTRL)

This record contains the total number of records in file.

October 2006

•



Table 2.4—Sample Transmission with Financial, Non-financial, Exception Transactions Description

Comments


This required record contains processor i dentification data.

Settlement Header Record (SHDR)

This required record contains the currency of settlement data. There will be a Settlement Header record (SHDR) to identify each settlement currency represented in the activity f or the processor.

Financial Record (FREC)

This required record contains detailed financial transaction data.

Non-financial Record (NREC)

This required record contains detailed non-financial data.

Exception Record (EREC)

This required record contains adjustment, chargeback and representment data.


This required record contains settlement position at a processor level by settlement currency. The identifier of A (Acquirer) indicates acquirer settlement position. The I (Issuer) indicates issuer settlement position, and the N (Net) settlement of the acquirer and issuer. Each transmission will contain one of the following Settlement Trailer Records (STRL) combinations: •

Acquirer and Net (A & N)

•

Issuer and Net (I & N)

Acquirer, Issuer, and Net (A, I, & N) There will be a Settlement Trailer Record (STRL) for each settlement currency represented in the activity for the processor. •

Interchange Compliance Issuer Detail Adjustment Record (INTC)

This record is dynamic. When this record is created it is forwarded to the MDS from GCMS through the MasterCard File Express or Bulk File. Once received, the MDS will identify the receiving processor by identifying the ICA number with the IPT (ICA Processor Table). This record, when received, will provide issuers and acquirers with information to determine the effect of interchange compliance on their net settlement.

File Trailer Record (FTRL)

This record contains the total number of records in the file.


•

October 2006

2-9


Table 2.5—Sample Transmission with Financial, Non-financial, Exception and Optional Addendum records Description

Comments


This required record contains processor identification data.

Settlement Header Record (SHDR)

This required record contains currency of settlement data.

Financial Record (FREC) /Non-financial Record (NREC)

This required record contains detailed financial/nonfinancial transaction data.

Exception Record (EREC)

This required record contains adjustment, chargeback and representment detail information.

Financial/Non-financial Addendum Record Force Post (FPST)

This optional addendum record will be in the file following the core Financial Record (FREC). This record is used for posting customer information.

Financial/Non-financial Addendum Record Exception Force Post (EPST)

This optional addendum record will be in the file following core FREC Financial record, and the FPST Force Post record. This record contains adjustment, chargeback and representment detail information.

Financial/Non-financial Addendum Record (FEER)

This optional addendum record will be in the file following core FREC Financial record, and any Force Post FPST addendum records.

Financial/Non-financial Addendum Record (DBMC)

This optional addendum record follows the core FREC Financial and any FPST Force Post, EPST Exception Posting record, and FEER Fee addendum records.

Financial/Non-financial Addendum Record (AIRA)

This optional addendum record follows the core FREC Financial record, FPST Force Post or EPST Exception posting records, FEER Fee records, and DBMC Debit MasterCard records.

Financial/Non-financial Addendum Record (PARC)

This optional addendum record is for Parcelas and is available for Brazil processors only. This record follows the core FREC, Financial and any FPST Force Post and/or FEER Fee addendum records.

(Brazil Only)

Financial/Non-financial Addendum Record (MCDC) (Brazil Only)

Financial/Non-financial Addendum Record (MPDT) (Brazil Only)

2-10

This optional addendum record is for the Maestro CDC information and is available for Brazil Processors only. This record follows the core FREC Financial and any FPST Force Post and/or FEER Fee addendum records. This optional addendum record is for the Maestro Post Dated transaction information and is available for Brazil processors only. This record follows the core FREC Financial and any FPST Force Post and/or FEER Fee addendum records.

October 2006

•



Description

Comments

Financial/Non-financial Addendum Record (MIST)

This optional addendum record is for the Maestro Installment transaction information and is available for Brazil processors only. This record follows the core FREC Financial and any FPST Force Post and/or FEER Fee addendum records.

(Brazil Only)

Financial/Non-financial Addendum Record (ADDR)

This optional addendum record will be in the file following core FREC/EREC Financial record, FPST Force Post or EPST Exception Posting records, FEER Fee records, DBMC Debit MasterCard records, and AIRA Airline Ticket addendum records.


This required record reports the settlement position at the processor level by settlement currency. The Settlement trailer record will be created for the Acquirer settlement. A separate settlement trailer record will be created if the processor has Issuer activity. A Net Settlement record will be created to report the net position of the acquirer and issuer totals. If there is only acquirer or only issuer activity to report, the acquirer or issuer record will be followed by a Net Settlement trailer record.

Interchange Compliance Issuer Detail Adjustment Record (INTC)

This record is dynamic. When this record is created it is forwarded to the MDS from GCMS via MasterCard File Express or Bulk File. Once received the MDS will identify the receiving processor or by identifying the ICA number via the IPT (ICA Processor Table). This record when received, will provide issuers and acquirers with information to determine the effect of i nterchange compliance on their net settlement.

File Trailer Record (FTRL)

This record contains the processor ID and the total f ile record count.


•

October 2006

2-11


Oct 2006

Batch Record Formats File Header Record (FHDR)—Required The File Header Record is the leading record in the file and provides the processor with identifying record information. Table 2.6—File Header Record (FHDR)

Position

ISO DE# /Subfield

Message Type Indicator

1–4

N/A

Settlement Date

5–10

15

6n

Format: MMDDYY

Processor ID

11–20

N/A

10 n

MDS-assigned Processor ID

Record Size

21–23

Description

File Type

Attribute Comments and Values

4a

FHDR( File Header)–identifies

Processor File Data information

24

N/A

3n

250

1 an

M Member Testing File P

Production File

Version

25–34

N/A

10 an

Current version number of the Batch Data File. The value may increment with changes implemented on a per-release basis.

Filler

35–250

N/A

216 an

Spaces

2-12

October 2006

•


Oct 2006


Oct 2006

Settlement Header Record (SHDR)—Required The Settlement Header Record represents the count and dollar totals from the online message reported through the Batch Transaction Journal File. The Settlement Header Record is required when there is activity on the file. It specifies the settlement currency of the transactions, so it is possible to have multiple Settlement Header Records on the file. To define each settlement currency. Table 2.7—Settlement Header Record (SHDR)

Position

ISO DE# /Subfield


1–4

N/A

Settlement Service Number

5–7

N/A

3n

MDS-assigned settlement time identifier

Intra-Currency Agreement Number

8–11

N/A

4 an

Reserved for future use

Settlement Currency Code

12–14

50

3n

Settlement Currency Code

Implied DecimalSettlement

15

N/A

1n

Implied decimal of the currency which the acquirer or issuer has selected as their settlement currency (DE 50).

Processor-Acquirer or Issuer

16

N/A

1a

Type of processor listed in the FHDR record. Valid values are: A= Acquirer I = Issuer

Reserved

17–26

N/A

10 an


Filler

27–250

N/A

224 an

Spaces

Description



4a

SHDR( File Header)–Contains processor

ID and settlement currency and service information.

•

October 2006

2-13


Financial (FREC)/Non-financial (NREC) Records—Required This record layout reflects the core format of an MDS financial/non-financial transaction, which contains data elements of both the online ISO message, and batch calculated settlement. These data elements provide information that can be used by the MDS processor for reconciliation and reporting purposes. The transaction records are sorted by settlement currency, PAN, and Switch Serial Number. Table 2.8—Financial (FREC)/Non-financial (NREC)

Position

ISO DE# /Subfielda


1–4

N/A

Switch Serial Number

5–13

63/3

9n

From online message

Processor—Acquirer or Issuer

14

N/A

1a

Type of Processor listed in the FHDR record: A= Acquirer

Description


4a

FREC( Financial) or NREC (Non-

Financial) record

I = Issuer

Processor ID

15–18

N/A

4n

MDS assigned acquirer or issuer processor ID. If the receiver of the file is the acquirer in the transaction, the four positions of the Processor ID field will contain the issuer processor ID (not found in the ISO online message unless the processor requests it). The issuer processor ID appears in the last four positions of DE 100 in the online ISO message.

If the receiver of the file is the issuer in the transaction, the four positions of the Processor ID field will contain the acquirer processor ID. The acquirer processor ID appears in the last four positions of DE 33 in the ISO online message or as a processor option.

Transaction Date

2-14

19–24

13

6n

Local date from the acquirer Format is: MMDDYY

October 2006

•


Oct 2006


Position

ISO DE# /Subfielda

Transaction Time

25–30

12

PAN Length

31–32

Primary Account Number (PAN)

33–51

2

19 an

Processing Code

52–57

3

6n

From online message

Trace Number

58–63

11

6n

From online message

Merchant Type (MCC)

64–67

18

4n

From online message

POS Entry

68–70

22

3n

From online message

Reference Number

71–82

37

12 an

From online message

Acquirer Institution ID

83–92

32

10 n

From online message The ISO 8583 institution ID is preceded by the number 1 because the ISO DE 32 is 9 digits long and the bulk file field is 10 digits long.

Terminal ID

93–102

41

10 an

From online message

Response Code

103–104

39

2n

From online message

Product Code

105–107

63/1

3 an

From online message Includes product code and interchange type

Advice Reason Code

108–114

60

7 an

From online 0220/0420 message Contains blanks when the transaction completes as requested

ISIS Agreement Code

115–118

N/A

4 an

If present, represents the currency in which the transaction will settle. Settlement (DE 50)

Authorization ID

119–124

38

6 an

From online message when available or blanks

Currency Code— Transaction

125–127

49

3n

From online message

128

N/A

1n

Implied decimal of Currency Code—Transaction (DE 49)

Description

Implied Decimal— Transaction


•

October 2006


6n

Local time from the acquirer Format is: HHMMSS

2n

Length of significant number of Primary Account Number (PAN) digits From online message Left justified, blank filled

2-15


Description

Position

ISO DE# /Subfielda

Completed Amt Trans—Local

129–140

4

12 n

From online message in currency of DE 49. When an 0220/0230 or 04XX message pair follow the original transaction, the value used is that from DE 95, Position 1–12 of the ISO 8583 message.

141

N/A

1a

Indicates if the value is a Credit ( C) or Debit (D) to the receiver.

Completed Amount Transaction—Local DR/CR Indicator

Cash Back Amt—Local


When the Completed Amount Transaction–Local is zero, this field will be populated with a D. 142–153

54/5

12 n

From online message, subfield 5, pos 9–20 in the currency of DE 49.

154

N/A

1a


155–162

28

8n

Fee charged for the transaction activity expressed in the currency of DE 49

163

28

1a


164–166

50

3n

From online message

Implied Decimal— Settlement

167

N/A

1n

Implied decimal of DE 50, Currency Code – Settlement.

Conversion Rate— Settlement

168–175

9

8n

From online message. This rate is the reciprocal of the online rate. The online rate is represented as settlement units to local, while this rate is represented as local units to settlement.

Completed Amt— Settlement

176–187

4/5

12 n

Completed amount in settlement currency of DE 50. This field contains zeros when the first two positions of the Processing Code are 40 (Transfer). When 04XX message pairs follow the original transaction, the value used is from DE 95, Position 13–24 of the ISO 8583 message.

Cash Back Amount— Local DR/CR Indicator Access Fee—Local

Access Fee—Local DR/CR Indicator Currency Code— Settlement

2-16

October 2006

•



Position

ISO DE# /Subfielda

188

N/A

1a

Indicates if the value is a Credit ( C) or Debit (D) to the receiver. When the Completed Amt– Settlement is zero, this field will be populated with a ( D).

Interchange Fee

189–198

N/A

10 n

Batch generated—same currency as DE 50

Interchange Fee DR/CR Indicator

199

N/A

1a


Reserved for Future Use

200–202

N/A

3n

This field is populated with 840.


203

N/A

1n

This field is populated with 2.


204–213

N/A

10 n

Zero filled.


214

N/A

1a

This field is populated with a D.

Positive ID Indicator

215

N/A

1n

Valid values are: 0 Indicates not supported 1 Positive ID is in the issuers online message; and the FIT value is greater than zero. 2 Positive ID is in the issuers online message; and the FIT value is equal to zero. 3 Positive ID is not present in the online message; and the FIT value is greater than zero. 4 Positive ID is not present in the online message; and the FIT value is equal to zero.

Future Service Filler

216

N/A

1a

Reserved for future use.

Cross Border Indicator

217

126

1a

Valid values are: Y Transaction qualifies as a cross border transaction N Transaction does not qualify as cross border transaction

Description

Completed Amount Settlement DR/CR Indicator


•

October 2006


Oct 2006

2-17


Position

ISO DE# /Subfielda

Cross Border Currency Indicator

218

126

VISA International Service Assessment (ISA) Fee Indicator

219

Description

110/4


1a

Valid values are: X Transaction does not qualify as cross border transaction Y Transaction was submitted in the currency of the country where the merchant or ATM is located N Transaction was not submitted in the currency of the country where the merchant or ATM is located

1n

Indicates whether the ISA fee is applied to the transaction. Value values are: 0 1 2

Filler a

220–250

N/A

31 ans

No international fee International fee debited International fee credited

Spaces

Refer to the MDS Online Specifications manual for detailed data element descriptions.

2-18

October 2006

•



Oct 2006

Financial/Non-financial Posting Addendum Record (FPST)— Optional Table 2.9—Financial/Non-financial Posting Addendum Record (FPST)—Optional

Description


Position

ISO DE# /Subfielda

1–4

N/A


4a

FPST

The FPST record is created when one of the following criteria is met: •

The FPST PDF flag is turned on, or

•

The STND PDF flag is turned on and the Response Code is ‘STND’, or

The MMBH PDF flag is turned on and the Response Code is ‘MMBH’ When created, this record follows the corresponding ‘FREC’. This addendum record should be used only by members needing to post from this file. •


5–13

63/3

9n

POS Data

14–24

61

11 an

From online message. MDS only reports the first 11 characters of the online message

Card-Issuer Institution

25–34

N/A

10 n

From online message

Account 1 Length

35–36

Account 1 “From”

37–55

102

19 an

From online message. Left justified, blank filled.

Filler

56–64

N/A

9 an


Account 2 Length

65–66

Account 2 “To”

67–85

103

19 an

From online message. Left justified, blank filled..

Filler

86–94

N/A

9 an


Card Acceptor Name/Address

95–116

43

22 ans

From online message

Card Acceptor City

117–132

43

16 ans

From online message

Card Acceptor State or Country Code

133–135

43

3 ans

From online message


•

October 2006

From online message

2n

2n

2-19


Description

Position

ISO DE# /Subfielda


Stand-In Transaction

136

1a

Valid values are: Y Yes N No

Debit MasterCard Off-Line

137

1a


Merchant ID

138–152

42

15 an

From online message. This field will only be present when the Product type is NOT MD.

Filler

153–250

N/A

98 an

Spaces

a

Refer to the MDS Online Specifications m anual for detailed data element descriptions.

Financial/Non-financial Fee Addendum Record (FEER)—Optional Table 2.10—Financial/Non-financial Fee Addendum Record (FEER)—Optional

Description

Position

ISO DE# /Subfielda



1–4


5–13

63/3

9n

Fee Description

14–53

N/A

40 an

Batch generated to identify the type of interchange fee applied to the transaction

Merchant Tier

54–56

N/A

3a

Batch generated classification for U.S. Maestro POS transactions.

POS-Merchant ID

57–62

110

6n

Maestro POS Merchant ID processed by the acquirer.

Filler

63–250

N/A

188 ans

a

4a

FEER( Fee Record)–Optional

When created this record follows the corresponding FREC, NREC, or EREC core records or any corresponding FPST or EPST addendum records. From online message

Spaces


2-20

October 2006

•


Oct 2006


Oct 2006

Financial/Non-financial Debit MasterCard Addendum Record (DBMC)—Optional Table 2.11—Financial/Non-financial Debit MasterCard Addendum Record (DBMC)—Optional

Description

Position

ISO DE# /Subfielda



1–4


5–13

63/3

9n

From online message

Merchant ID

14–28

42

15 an

From online message

Banknet Reference Number

29–37

63/4

9 an

From online message

Acquirer’s Reference Number (ARN)

38–60

63/5

23 an

From online message

GCMS—Settlement Date

61–66

63/6

6 an

Format: MMDDYY

GCMS—Settlement Cycle Number

67–68

63/6

2n

Valid values are 1–6

GCMS Card Authentication Method

69

110/5

1 ans

From online message

GCMS Cardholder Authentication Entity

70

110/5

1 ans

From online message

GCMS Card Data Output Capability

71

110/5

1 ans

From online message

GCMS Terminal Data Output Capability

72

110/5

1 ans

From online message

GCMS PIN Capture Capability

73

110/5

1 ans

From online message

GCMS PAN Sequence Number

74–76

23

3 an

When present, distinguishes separate cards having the same Primary Account Number (PAN).

GCMS Program Registration ID

77–79

110/2

3 an

Indicates participation in special brand specific promotion programs such as Quick Payment Services, Supermarket, Gaming.


4a

DBMC (Debit MasterCard)–Optional.

The product type must be MD for this addendum record to be created

•

October 2006

2-21


Description

GCMS Card Acceptance Program

Position

ISO DE# /Subfielda

80–82

110/7


3 an

Identifies the Card Program to which the transaction belongs. Valid values are: DMC

GCMS Business Service Level Code

83

110/7

1 ans

Debit MasterCard

Business relationship between the acquirer and issuer and the interchange rules governing the participants in the transaction. Valid values are: 1 = Interregional 2 = Intraregional 3 = Intercountry Intracountry 4= 8 = Member-to-member

GCMS Business Service ID Code

84–89

110/7

6 ans

Business service to which the transaction is assigned.

GCMS Interchange Rate Designator

90–91

110/7

2 ans

Interchange rate and editing rules applied to the transaction.

GCMS Settlement Service Level Code

92

110/7

1 an

Identifies the settlement level of the settlement service. Valid values are: 1= Regional Intraregional 2=

GCMS Settlement Service ID Code

93–102

110/7

10 ans

Settlement service based on the settlement service ID selected by the receiving member.

GCMS Settlement Date

103–108

110/7

6 ans

If the Debit MasterCard issuer’s settlement bank is closed on the date the transaction is received, this date will be the next open date for the settlement bank. Format: YYMMDD

GCMS Settlement Cycle

109–110

110/7

2 ans

The settlement cycle is a two-digit field that identifies the settlement cycle of the transaction. Valid values are Cycle 1 01= 02= Cycle 2 03= Cycle 3 Cycle 4 04= 05= Cycle 5 Cycle 6 06=

2-22

October 2006

•



Description

Position

ISO DE# /Subfielda

Filler

111–250

N/A

a


140 an

Spaces


Financial/Non-financial Debit MasterCard Airline Ticket Addendum Record (AIRA)—Optional Table 2.12—Financial/Non-financial Debit MasterCard Airline Ticket Addendum Record (AIRA)— Optional

Description

Position


ISO DE# /Subfielda

1–4


4a

AIRA( Airline Ticket Required for Debit

MasterCard) When created this record follows any corresponding FPST, FEER and/or DBMS addendum records.


5–13

63/3

9n

Passenger Name

14–38

N/A

25 an

Passenger Name

Ticket Number

39–53

48/93

15 an

Ticket Number

Travel Date

54–59

N/A

6n

Format: MMDDYY

Carrier Code

60–61

N/A

2 an

Carrier Code

Service Class

62–63

N/A

2 an

Service Class

64

N/A

1 an

Stop over Code

City of Origin

65–69

N/A

5 an

Origin City

City of Destination

70–74

N/A

5 an

Destination city

Filler

75–250

N/A

176 an

Stop Over Code

a

From online message




•

October 2006

2-23

Oct 2006


Financial/Non-financial Parcelas Addendum Record (PARC)— Optional Table 2.13—Financial/Non-financial Parcelas Addendum Record (PARC)—Optional

Description

Position


1–4


5–13

Identifier

ISO DE# /Subfielda


4a

PARC( Parcelas)

63/3

9n

From online message

14–15

112

2n

Valid values are: 21 Parcelas transaction 50 Construcard Transaction 60 Trishop transaction

Number of Installments

16–17

112

2n

Number of chosen installments, from inquiry requests When the transaction identifier is 50 or 60, this field will not be populated.

Installment Interest

18–29

N/A

12 n

Estimated installment amount with interest When the transaction identifier is 50 or 60, this field will not be populated.

Purchase Price with Interest

30–41

112

12 n

Total amount of transactions with interest When the transaction identifier is 50 or 60, this field will not be populated.

Annual Interest Rate

42–45

112

4n

Annual Interest Rate When the transaction identifier is 50 or 60, this field will not be populated.

Filler

46–250

N/A

205 an

a

Spaces


2-24

October 2006

•


Oct 2006


Financial/Non-financial Maestro CDC Addendum Record (MCDC)— Optional Table 2.14—Financial/Non-financial Maestro CDC Addendum Record (MCDC)—Optional

Description

Position

ISO DE# /Subfielda



1–4

4a

MCDC( Maestro CDC–Optional)


5–13

63/3

9n

From online message

Identifier

14–15

112/1

2n

Valid value:

When created this record follows any corresponding FPST and/or FEER addendum records..

20 CDC transaction


16–17

112/2

2n

Number of chosen installments, from inquiry requests

Estimated Installment Amount

18–28

112/11

11 n

Estimated installment amount for number of installments chosen.

29

N/A

1a


30–40

112/11

11 n

41

N/A

1a


Monthly Interest Rate

42–46

112/11

5n

Monthly Interest Rate


47–51

112/11

5n


TAC

52–59

112/11

8n

Two decimal position – Registration Fee

# of New Options Offered

60–61

112/11

2n

Number of additional installment options offered

62

N/A

1a

Valid values are: C CDC Purchase I Inquiry

63–250

N/A

188

Spaces

Estimated Installment Amount DR/CR Indicator Total Amount Total Amount DR/CR Indicator

CDC Identifier

Filler a

Total to be repaid via installments



•

October 2006

2-25

Oct 2006


Financial/Non-financial Maestro Post Dated Addendum Record (MPDT)—Optional Table 2.15—Financial/Non-financial Maestro Post Dated Addendum Record (MPDT)—Optional

Description

Position

ISO DE# /Subfielda



1–4

4a

MPDT( Maestro Post Dated–Optional)


5–13

63/3

9n

From online message

Service Code

14–15

112/1

2n

Valid values are:

When created this record follows any corresponding FPST and/or FEER addendum records.

30 Guaranteed 31 non-guaranteed

Guarantee

16

112/18

1a

Contains Y or Nf or guarantee status of transaction:

Guarantee Amount

17–24

112/18

8n

Contains the amount of the guarantee in local currency; zero if no guarantee

Proposed Settlement Date

25–30

112/18

6n

MMDDYY of proposed settlement date (expected date for completion message arrival)

Original MDS Settlement Date

31–36

112/18

6n

MMDDYY; MDS Settlement date of original preauthorization; contains zeros for preauthorization message.

Original Switch Serial Number

37–45

112/18

9n

Original switch serial number assigned by MDS to original pre-authorization request; contains zeros on preauthorization message

Interchange Amount

46–53

112/18

8n

Interchange amount associated with the completion message with debit/credit indicator; two decimal positions; contains zeros on preauthorization request

Interchange Amount DR/CR Indicator

54

112/18

1a


Authorization Code

55–60

112/18

6n

The online authorization code provided by the issuer on the original pre-authorization request

2-26

October 2006

•


Oct 2006


Description

Position

Pre Auth or Completion Completi on

61

Filler a

ISO DE# /Subfielda

62–250

N/A


1a

P Preauthorization A Completion

189

Spaces

Refer to the MDS Online Specifications m anual for detailed data element descriptions. descriptions.

Financial/Non-financial Maestro Installment Addendum Record (MIST)—Optional

Oct 2006

Table 2.16—Financial/Non-financial Maestro Installment Addendum (MIST)—Optional

Description

Position

ISO DE# /Subfielda



1–4


5–13

63/3

9n

From online message

Service Code

14–15

112/1

2n

Valid values are: 40 for guaranteed non-guarantee d 41 for non-guaranteed

MIST (Maestro Installment–Optional) Installment–Optional)

16

112/19

1a

Contains Y or Nf or guarantee status of transaction.

Guarantee Amount

17–24

112/19

8n

Contains the amount of the guarantee in local currency; zero if i f no guarantee


25–26

112/19

2n

Number of requested installments

Number of This Installment

27–28

112/19

2n

Number in sequence of this completion transaction; zero for pre-authorization pre-authorization request

Date of First Installment

29–34

112/19

6n

Contains zeros for completion messages Format: MMDDYY

Original MDS Transaction Date

35–40

112/19

6n

MDS settlement date of original preauthorization request; contains zeros on pre-authorization message Format: MMDDYY

When created this this record follows any any corresponding FPST and/or FEER addendum records.

Guarantee


4a

•

October 2006

2-27


Position

ISO DE# /Subfielda

Original Switch Serial Number

41–49

112/19

9n

Original switch serial number assigned by the MDS to original pre-authorization request; contains zeros on pre-authorization message

Interchange Amount

50–57

112/19

8n

Interchange amount associated with completion message with debit/credit indicator; contains zeros on preauthorization message; two decimal position.

Interchange Amount DR/CR Indicator

58

112/19

1a


Authorization Code

59–64

112/19

6n

Contains the the online authorization authorization code provided by the issuer on the original preauthorization preauthorization request

1a

P Preauthorization A Completion

Description

Pre-Auth or Completion Filler a

65 66–250

N/A


185 an

Spaces


2-28

October 2006

•

©2006 MasterCard MDS Settlement Settlement and Reports


Financial/Non-financial Additional Data Addendum Record (ADDR)—Optional

Oct 2006

Table 2.17—Financial/Non-financial Additional Data Addendum Record (ADDR)—Optional

Description

Position

ISO DE# /Subfielda



1–4


5–13

63/3

9n

From online message

Currency Code, Currency Conversion Assessment

14–16

N/A

3n

From online message

(Additional Data Record– ADDR (Additional

17

N/A

1n

From online message

Amount, Currency Currency Conversion Assessment

18–29

111

12 n

The amount calculated by the MDS resulting from applying the Currency Conversion Assessment to the transaction.

Amount, Currency Currency Conversion Assessment DR/CR Indicator

30

N/A

1a



31–33

111

3n

This field will always be populated with 840.


34

1n

This field will always be populated with a 2.


35–42

8

8n

Zero-filled


43

N/A

1a

This field will always be populated with a D.

44–250

N/A

207 an

Optional) When created, this this record follows the the corresponding FREC, NREC, or EREC core records or any corresponding FPST or EPST addendum records.

Implied Decimal, Currency Conversion Assessment

Filler a

4a

Spaces



•

October 2006

2-29


Financial/Non-financial Exception Record (EREC)—Required Table 2.18—Financial/Non-financial Exception Record (EREC)—Required

Description

Position


1–4


5–13

Processor–Acquirer Processor–Acquirer or Issuer

14

ISO DE# /Subfielda

63/3

Attribute Comments Comments and Values

4a

An Exception Record (EREC) is created when a reversal adjustment, adjustment, chargeback, or representment record is received

9n

From original online message

1a

A or I, identifies type of processor

listed in processor ID in the Header Record. A acquirer I issuer

Processor ID

15–18

N/A

4n

The MDS populates this field with the acquirer or issuer processor ID. If the receiver of the file is the acquirer in the transaction, the four positions of the Processor ID field will contain the issuer processor ID (not found in the ISO online message unless the processor requests it.) The issuer processor ID appears in the last four positions of DE 100 in the ISO online message. If the receiver of the f ile is the issuer of the transaction, the four position Processor ID field will contain the acquirer processor ID. The acquirer processor ID appears in the last four positions of DE 33 in the ISO online message or as a processor option.

Transaction Date

19–24

13

6n

Original local date from acquirer; Format: MMDDYY

Transaction Time

25–30

12

6n

Original local time from acquirer; Format: HHMMSS

Primary Account Number (PAN-) Length

31–32

2n

Length of significant number of PAN digits

PAN

33–51

19 an

From online message. Left justified, Blank filled

2-30

2

October 2006

•


Oct 2006


Position

ISO DE# /Subfielda

Processing Code

52–57

3

6n

From online message

Trace Number

58–63

11

6n

From online message

Merchant Type (MCC)

64–67

18

4n

From online message

POS Entry

68–70

22

3n


Reference Number

71–82

37

12 an

From online message

Acquirer Institution ID

83–92

32

10 n

From online message. The ISO 8583 institution ID is preceded by the number 1 because the ISO DE 32 is 9-digits long and the bulk file field is 10 digits long.

Terminal ID

93–102

41

10 an

From online message. Left justified, blank-filled

Response Code

103–104

39

2n

From online message

Product Code

105–107

63/1

3 an

From online message. Includes product code and interchange type

Advice Reason Code

108–114

60

7 an

From exception online 0420/0220 message

ISIS Agreement Code

115–118

N/A

4 an

If present, represents in which currency the transaction will be settled (DE 50)

Authorization ID

119–124

38

6 an

From online message message when available available or zeros

Currency Code Transaction

125–127

49

3n

From online message

128

N/A

1n

Implied decimal of Currency Code – Transaction

129–140

4

12 n

From original online message. In currency of DE 49. When an 0220/0230 or 04XX message pair follow the original transaction, the value used is that that from DE 95, position position 1–12 of the ISO 8583 message.

141

N/A

1a


142–153

54/5

12 n

From original online message. In currency of DE 49

Description

Implied Decimal Transaction Completed Amt Trans - Local

Completed Amount Transaction–Local DR/CR Indicator Cash Back Amt - Local


•

October 2006

Attribute Comments Comments and Values

2-31


Position

ISO DE# /Subfielda

154

N/A

1a


Access Fee–Local

155–162

28

8n

From online message. In currency of DE 49

Access Fee–Local DR/CR Indicator

163

28

1a


Currency Code— Settlement

164–166

50

3n

From online message


167

N/A

1n

Implied decimal of Currency Code – Settlement (DE 50)

Conversion Rate— Settlement

168–175

9

8n

This rate is the reciprocal of the online rate. The online rate is represented as settlement units/local while this rate is represented as local units to settlement.

Completed Amt— Settlement

176–187

5

12 n

Original Completed amount in settlement currency of DE 50

Completed Amt— Settlement DR/CR Indicator

188

N/A

1a


189–198

N/A

10 n

199

N/A

1a


New Advice Reason Code

200–206

60

7 an

From exception online 0420/0220 message

Replacement Amount— Local

207–218

95/1

12 n

From 0420/0220 online message. In currency of DE 49

219

N/A

1a


220–231

95

12 n

From 0420/0220 online message. In currency of DE 50

232

N/A

1a


233–238

N/A

6n

Formatted as MMDDYY. The MDS retrieves the month and day from batch processing and adds the year.

Description

Cash Back Amount –Local DR/CR Indicator

Interchange Fee Interchange Fee DR/CR Indicator

Replacement Amount Local DR/CR Indicator Replacement Amt— Settlement Replacement Amount Settlement DR/CR Indicator Original Settlement Date

2-32


Will be same currency as DE 50

October 2006

•


Oct 2006


Description


Position

ISO DE# /Subfielda

239

N/A


1n

Valid values are: 0 Not Supported 1 Positive ID is in the issuers online message and the FIT value is greater than zero. 2 Positive ID is in the issuers online message and the FIT value is equal to zero. Positive ID is not present in the online message and the FIT value is greater than zero. 4 Positive ID is not present in the online message and the FIT value is equal to zero. 3


240

N/A

1a

Space

Cross Border Indicator

241

126

1a

Valid values are: Y Transaction qualifies as a cross border transaction. N Transaction does not qualify as cross border transaction.

Cross Border Currency Indicator

242

126

1a

Valid values are: X Transaction does not qualify as cross border transaction Y Transaction was submitted in the currency of the country where the merchant or ATM is located N Transaction was not submitted in the currency of the country where the merchant or ATM is located

ISA Fee Indicator

243

110

1a

Fixed Length International Fee (ISA) Indicator. Valid values are: 0 No international fee 1 International fee debited 2 International fee credited

244–250

N/A

7 ans

Filler a

Spaces



•

October 2006

2-33


Financial/Non-financial Exception Record (EPST)—Optional Table 2.19—Financial/Non-financial Exception Posting Record (EPST)—Optional

Description

Position

ISO DE# /Subfielda



1–4

4a

EPST (Exception Posting Record–


5–13

63/3

9n

POS Data

14–24

61

11 an



25–34

58

10 n

From original online message. The ISO 8583 institution ID is preceded by a 1 because the ISO DE 32 is 9-digits.

Account 1 Length

35–36

N/A

2n

Account 1 “From”

37–55

102

19 an

From online message; left justified, zero filled.

Filler

56–64

N/A

9 an


Account 2 Length

65–66

N/A

2n

Account 2 “To”

67–85

103

19 an

From online message; left justified, zero filled.

Filler

86–94

N/A

9 an

From online message

Card Acceptor Name/Address

95–116

43

22 ans

From online message

Card Acceptor City

117–132

43

16 ans

From online message

Card Acceptor State or Country Code

133–135

43

3 ans

From online message

Stand-In Transaction

136

Optional) From online message

1a

Stand-In (from original financial transaction). Valid value are: Y Yes N No

Adjustment Date

137–142

N/A

6n

MDS Date; Format: MMDDYY

Adjustment Time

143–148

N/A

6n

MDS Time; Format: HHMMSS

Adjusted Amt—Local

149–160

N/A

12 n

Generated from MDS internal exception process. In the local currency of the acquirer or source location of the transaction (DE 49).

2-34

October 2006

•


Oct 2006


Description

Position

Adjusted Amt—Local DR/CR Indicator

ISO DE# /Subfielda


161

N/A

1a


162–173

N/A

12 n

Generated from MDS internal exception process. In currency the acquirer or issuer has selected as their settlement currency (DE 50).

Adjusted Amount— Settlement DR/CR Indicator

174

N/A

1a



175

N/A

1n

Valid values are:

Adjusted Amt— Settlement

0 1

2

3

4

Indicates “not supported” Positive ID is in the issuers online message and the FIT value is greater than zero. Positive ID is in the issuers online message and the FIT value is equal to zero. Positive ID is not present in the online message and the FIT value is greater than zero. Positive ID is not present in the online message and the FIT value is equal to zero.

Merchant ID

176–190

42

15 an

From online message This field will only be present when the Product type is NOT MD.

Filler

191–250

N/A

60 an

Spaces

a



•

October 2006

2-35


Oct 2006

Settlement Trailer Record (STRL)—Required Table 2.20—Settlement Trailer Record (STRL)—Required

Position

ISO DE# /Subfield


1–4

N/A

Settlement Service Number

5–7

N/A

3n

MDS Assigned Settlement Indicator

Intra-currency Agreement Number

8–11

N/A

4 an


Currency Code— Settlement

12–14

50

3n

Settlement Currency Code There will be a separate STRL for each currency represented in the transaction file.


15

N/A

1n

Implied decimal of local settlement currency DE 50

Processor—Acquirer or Issuer

16

N/A

1a

Acquirer, Issuer, or Net identifies

Description


4a

STRL( Settlement Trailer)

Used to reflect the settlement position at a processor level by settlement currency.

settlement position of the processor listed in the processor ID in the Header Record. Each file will contain one of the following Settlement Trailer Record combinations: •

Acquirer and Net (A & N)

•

Issuer and Net (I & N)

Acquirer, issuer, and Net (A, I, & N) The Ni ndicator in the record denotes that this is the Net settlement to the processor. The Net Settlement Trailer record represents the Net amount that is settled to the member. The Net record contains the final settlement amount only. •

Filler

2-36

17–26

N/A

10 an


October 2006

•



Position

ISO DE# /Subfield

Total Debit Amount— Settlement

27–40

N/A

14 n

Calculated in batch processing. The sum of all FRECdebit records. Debit records contain a Di n the settlement indicator field. The totals reported for the acquirer are presented in the true settlement position for the transactions (debits to issuers will be credits to acquirers.)

Number of Debit Items

41–48

N/A

8n

Calculated in batch processing. The number of FRECd ebit records. The number of debits will not be incremented for transactions when the first two positions of the Processing Code are equal to 40 (Transfer).

Total Credit Amount— Settlement

49–62

N/A

14 n

Calculated in batch processing. The sum of all FRECcredit records. Credit records contain a Ci n the settlement indicator field.

Description


The totals reported for the acquirer are presented in the true settlement position for the transactions (debits to issuers will be credits to acquirers.) Number of Credit Items

63–70

N/A

8n

Calculated in batch processing. The number of FRECc redit records. The number of credits will not be incremented for transactions when the first two positions of the Processing Code are equal to 40 (Transfer).

Total Reversal Debit Amount

71–84

N/A

14 n

Calculated in batch processing. The sum of all EREC debit records. Debit records contain a Di n the settlement indicator field. The totals reported for the acquirer are presented in the true settlement position for the transactions. Debits to issuers will be credits to acquirers.

Number of Debit Reversals

85–92

N/A

8n

Calculated in batch processing. The number of ERECd ebit records.


•

October 2006

2-37


Position

ISO DE# /Subfield

Total Reversal Credit Amount

93–106

N/A

14 n

Calculated in batch processing. The sum of all credit ERECrecords. Credit records contain a Ci n the settlement indicator field. The totals reported for the acquirer are presented in the true settlement position for the transactions. Debits to issuers will be credits to acquirers.

Number of Credit Reversals

107–114

N/A

8n

Calculated in batch processing. The number of ERECc redit records.

Number of Non-financial

115–122

N/A

8n

Calculated in batch processing. The number of non-financial NRECr ecords. Non-financial records are transaction where no card settlement value is interchanged through the MDS. These include balance inquiries, funds transfers, denials, and electronic commerce certificate requests.

Total Interchange Fees - Debits

123–134

N/A

12 n

Calculated in batch processing. The sums of all debit interchange from FREC, NREC, and ERECrecords. Debit records contain a Di n the interchange indicator field.

Total Interchange Fees - Credits

135–146

N/A

12 n

Calculated in batch processing. The sums of all credit interchange from FREC, NREC, and ERECrecords. Credit records contain a Ci n the interchange indicator field.


147–149

N/A

3n

This field is populated with ‘840’.


150

N/A

1n

This field is populated with a ‘2”.


151–162

N/A

12 n

Zero filled.


163

N/A

1a

This field is populated with a ‘D’.

Total Net Settlement

164–177

N/A

14 n

Total Net Settlement DR/CR Indicator

178

N/A

1a

179–250

N/A

72 an

Description

Filler

2-38


Processor Settlement position Indicates if the value is a Credit ( C) or Debit (D) to the receiver. Spaces

October 2006

•


Oct 2006


Interchange Compliance Issuer Detail Adjustment Record (INTC)— Required Table 2.21—Interchange Compliance Issuer Detail Adjustment Record (INTC)—Required

Position

ISO DE# /Subfield


1–4

N/A

Acceptance Brand ID

5–7

N/A

3 ans

Identifies the acceptance brand or financial network to which a transaction belongs

8

N/A

1 ans

The Business Service Arrangement Type assigned to the transaction in GCMS.

Business Service ID

9–14

N/A

6 ans

The Business Service ID assigned to the transaction in GCMS.

Interchange Rate Designator

15–16

N/A

2 an

The IRD that was originally submitted and processed through GCMS

Business Date

17–22

N/A

6n

The clearing system’s processing date expressed in the local time zone of the clearing system’s processing center. Format: YYMMDD

Business Cycle

23–24

N/A

2n

A two-digit numeric subfield which represents the clearing cycle.

Member ID

25–35

N/A

11 n

The issuer’s MasterCard member identification number

PAN—Primary Account Number

36–51

N/A

16 n

Received in the GCMS record sent.

Filler

52–54

N/A

3 an

Spaces

Amount Transaction (Clearing)

55–66

N/A

9(10)v99 n Transaction amount submitted by the acquirer in the first presentment message

Revised Interchange Fee Amount

67–74

N/A

9(6)v99 n

Revised Interchange Rate Designator

75–76

N/A

2 an

Description

4a

INTC( Interchange Compliance Record)

Created when a file is received from GCMS.

Business Service Arrangement Type



•

October 2006

Interchange fee amount after adjustment by the interchange compliance process. Interchange rate designator to which the transaction was adjusted by the interchange compliance process.

2-39

Oct 2006


Position

ISO DE# /Subfield

Banknet Reference Number (BRN)

77–85

N/A

9 an

Assigned by the MasterCard Authorization System at the acquirer MIP

Banknet Date

86–89

N/A

4n

Date of the transmission from the authorization log. Format: MMDD MM=MONTH, DD=DAY

Filler

90–250

N/A

161 an

Description


Spaces Oct 2006

File Trailer Record (FTRL)—Required Table 2.22—File Trailer Record (FTRL)—Required

Description

Position


1–4

Processor ID

5–14

Total Recon Count

15–25

Filler

26–250

2-40

ISO DE# /Subfield

N/A

N/A


4a

FTLR (File Trailer Record)

10 n

Same as file header record (FHDR)

11 n

Total number of all records including file header record, addendums, financial control records and file trailer.

225 an

Spaces

October 2006

•


Batch File Specifications Previous Batch Data File

Oct 2006

Previous Batch Data File This section provides record format and file structure for the batch data file being replaced by the 250-byte batch data file. Members should be migrating to the newer 250-byte batch data file structure.

MDS Record Formats This section provides detail record layouts for the MDS Report Transmission File and the MDS Transaction Detail File. Table 2.23—Report Transmission File Header Record Format Description

Attribute

Comment


4n

5200

Settlement Date

6n

YYMMDD

Record Segment Size

3n

Transmit Record Size

Total Record Size

3n

Logical Record Size

File Type

1 an

C

Filler

116 an

Total

133

Certification File P Production File Blank Fill

Table 2.24—Report Transmission File Detail Record Format Description

Print Control Character

Attribute

1 an

Comment

Position 1 contains a carriage control character: space 1 line 1 skip to new page 0 space 2 lines - space 3 lines blank

Report Line Data

Total


132 an

The first line of the reports will always include positions 1 through 4 printed as SWCH. A processor uses this field to key in from generating reports or microfiche.

133

•

October 2006

2-41


File Structure The following pages provide details about the records contained in the batch data file being replaced.

File Header Record—Required The File Header (5200) Record will provide the processor with the following information: •

Settlement date

•

Processor ID

•

Record segment size (which represents the record size of the transmission file to the processor)

Financial/Non-financial and Exception Item Record The Financial/Non-financial (5220) Record and Exception Item (5240) Record contain information sufficient to marry a transaction (for example, the individual’s account number, the amount requested in the transaction, and the settlement date). When an advice or reversal message (full or partial) follows the original authorization request and approval, the MDS updates the original 5220 record to reflect the adjusted values. Therefore, a single 5220 record appears in the bulk file rather than in two 5220 records. The MDS generates a 5240 record because of an adjustment, chargeback, or representment.

2-42

October 2006

•



File Options Table 2.25 lists the available file options. Table 2.25—File Options Option

Description

Transaction Posting

•

Used by Authorization Request/01xx processors only

•

Contains four 80-character segments for every transaction

•

Five 80-character segments for every exception transaction

•

Used by Financial Transactions/02xx processors that perform logging functions that capture all online message contents

•

Contains one 80-character segment for each completed transaction

•

Two 80-character segments for each suspect and international transaction

•


•

Used by Financial Transactions/02xx processors that perform logging functions that capture minimum online message contents

•

Contains two 80-character segments for every completed transaction

•


Dynamic Transaction Validation

Transaction Reconciliation


•

October 2006

2-43


File Control Record—Required The File Control Record represents the count and dollar total (batch totals) of all entries (total debit and total credit) contained in the file.

Settlement Record—Required The Settlement Record represents the count and dollar totals that are sent daily to the processor to settle on the transaction date indicated in the record.

File Update Record—Optional (FIT File) The File Update Record contains product and processor routing information of prefixes loaded at the MDS for routing. These records are available to processors on a weekly (every Thursday evening) or daily basis.

Full File Replacement The full file update record transmission contains existing prefixes as well as any additional prefixes added, deleted, and modified since the previous transmission. This is a full file replacement.

File Update Versions There are two versions of the File Update Record available. The first version of the file contains the country code information for each prefix; the second version does not contain the country code information. U.S. acquirers that assess ATM access charges must use the first (and preferred) version of the file.



2-44

Note

Processors implementing new connection to the MDS must use the File Update Record version that contains the country code information.

October 2006

•



Sequence of Transmission File Financial/Non-financial Records and Exception Records appear in the file as records for the particular settlement date. Table 2.26—Transmission without Transactions Description

Segments

File Header Record File Control Record



Note

Settlement Record

1 of 2 (acquirer)

Settlement Record

2 of 2 (acquirer)

Settlement Record

1 of 2 (issuer)

Settlement Record

2 of 2 (issuer)

Processors will not receive the issuer and acquirer settlement record in a specific order.

Table 2.27—Sample Transmission using Dynamic Transaction Validation Description

Segments

File Header Record Transaction Validation Record

1 of 1

Reconciliation Record

1 of 2


2 of 2

Transaction Validation Record

1 of 1


1 of 2


2 of 2


1 of 1


1 of 2


2 of 2


1 of 1

Exception Record

1 of 5

Exception Record

2 of 5


•

October 2006

2-45


Description

Segments

Exception Record

3 of 5

Exception Record

4 of 5

Exception Record

5 of 5

Exception Record

1 of 5

Exception Record

2 of 5

Exception Record

3 of 5

Exception Record

4 of 5

Exception Record

5 of 5

File Control Record Settlement Record

1 of 2 (acquirer)

Settlement Record

2 of 2 (acquirer)

Settlement Record

1 of 2 (issuer)

Settlement Record

2 of 2 (issuer)

File Update Records (optional)

Table 2.28—Sample Transmission using Transaction Reconciliation Description

Segments

File Header Record

2-46


1 of 2


2 of 2


1 of 2


2 of 2


1 of 2


2 of 2


1 of 2


2 of 2

Exception Record

1 of 5

Exception Record

2 of 5

Exception Record

3 of 5

Exception Record

4 of 5

Exception Record

5 of 5

October 2006

•



Description

Segments

Exception Record

1 of 5

Exception Record

2 of 5

Exception Record

3 of 5

Exception Record

4 of 5

Exception Record

5 of 5


1 of 2 (acquirer)

Settlement Record

2 of 2 (acquirer)

Settlement Record

1 of 2 (issuer)

Settlement Record

2 of 2 (issuer)


Table 2.29—Sample Transmission using Transaction Posting Description

Segments

File Header Record Posting Record

1 of 4

Posting Record

2 of 4

Posting Record

3 of 4

Posting Record

4 of 4

Posting Record

1 of 4

Posting Record

2 of 4

Posting Record

3 of 4

Posting Record

4 of 4

Exception Record

1 of 5

Exception Record

2 of 5

Exception Record

3 of 5

Exception Record

4 of 5

Exception Record

5 of 5


1 of 2 (acquirer)

Settlement Record

2 of 2 (acquirer)


•

October 2006

2-47


Description

Segments

Settlement Record

1 of 2 (issuer)

Settlement Record

2 of 2 (issuer)


MDS Codes The following tables list responses, processing, and completion codes. Members use the EX9.2 values to translate and interpret auto reconciliation files.

Response Codes The following table (Table 2.30—Response Codes) provides a list of response codes that the MDS uses. Table 2.30—Response Codes

2-48

EX9.2 Codes

ISO Codes

Description

01

00

Transaction Approved

00

Required Value

01

Refer to Card Issuer

05

Decline (For MDS Use Only)

10

Partial Approval

25

Unable to Locate Card on File (no action taken)

27

File Maintenance Error

11

30

Format Error

12

12

Invalid Transaction (For MDS use only)

14

14

Invalid Cardholder Number

31

92

Invalid Acquirer, Unable to Route Transaction

40

Requested Function Not Supported

41

41

Lost Card

43

43

Stolen Card

51

51

Insufficient Funds

54

54

Expired Card

55

55

Invalid PIN, Allow Customer Retry

October 2006

•



EX9.2 Codes

ISO Codes

Description

56

78

Cardholder Not on File

57

57

Invalid Transaction Selection, Transaction not Permitted to Issuer or Cardholder

58

Invalid Transaction Selection, Transaction not Permitted to Acquirer or Cardholder

61

61

Exceeds Withdrawal Limits

62

62

Restricted Card

63

Error in Decryption of PIN Block

65

Exceeds Withdrawal Count Limits

68

Response Received Late

04

Capture Card

71

Message Out of Exception Cycle Sequence

72

Exception Cycle Time Expired; for example, chargeback more than 45 days after presentment

75

PIN Tries Exceeded

76

Invalid “To” Account Specified

77

Invalid “From” Account Specified

76

13

Invalid Interchange Amount

77

79

Key exchange Validation Failed

77

05

Do Not Honor

78

00

Account 1 Positive—Account 2 Positive

79

00

Account 1 Positive—Account 2 Negative

80

00

Account 1 Negative—Account 2 Positive

81

00

Account 1 Negative—Account 2 Negative

82

96

Unable to Process, System Error

83

80

ATM Processor Inoperative

85

Valid for AVS Requests Only

91

Cardholder Processor Inoperative, Destination Processor (CPS or INF) not Available

94

Duplicate Transaction Detected

15

Cardholder Processor Not Found

67

75

91

92


•

October 2006

2-49


Processing Codes The following table (Table (Table 2.31—Processing Codes) Codes) provides a list of processing codes that the MDS uses. Table 2.31—Processing Codes ISO Codes

Description

0010

001000

Purchase—Savings Purchase—Savings

0020

002000

Purchase—Checking Purchase—Checking

0040

000000

Purchase—No Account Specified

0110

011000

Withdrawal—Savings Withdrawal—Savings

0120

012000

Withdrawal—Checking Withdrawal—Checking

0130

013000

Withdrawal—Credit

0140

010000

Withdrawal—No Account Specified

1140

2-50

Oct 2006

Ex9.2 Codes

Oct 2006

Scrip transaction—No transaction—No Account Specified

2010

201000

POS Online Refund—Savings

2020

202000

POS Online Refund—Checking

2040

200000

POS Online Refund—No Account Specified

2110

210010

ATM Deposit—Savings Deposit—Savings

2120

210020

ATM Deposit—Checking

300000

Balance Inquiry—No Account Specified

2310

231000

Credit Adjustment—Savings Adjustment—Savings

2320

232000

Credit Adjustment—Checking Adjustment—Checking

2340

230000

Credit Adjustment—No Account Specified

2810

280010

Payment—Savings Payment—Savings

2820

280020

Payment—Checking Payment—Checking

2830

280030

Payment—Credit Payment—Credit

2840

280000

Payment—No Account Specified

4011

401100

Transfer—Savings to Savings

4012

401020

Transfer—Savings to Checking

4021

402010

Transfer—Checking to Savings

4022

402200

Transfer—Checking to Checking

4031

403100

Transfer—Credit to Savings

October 2006

•



Oct 2006

Ex9.2 Codes

ISO Codes

Description

4032

403200

Transfer—Credit to Checking

5010

501000

Bill Payment—Savings Payment—Savings

5020

502000

Bill Payment—Checking Payment—Checking

5030

503000

Bill Payment—Credit Payment—Credit

5040

500000

Bill Payment—No Account Specified

5110

001000

Cash Back—Savings

5120

002000

Cash Back—Checking

5130

003000

Cash Back—Credit

5140

000000

Cash Back—No Account Specified

9010

901000

Electronic Commerce—Savings, Commerce—Savings, Certificate Request

9020

902000

Electronic Commerce—Checking, Commerce—Checking, Certificate Request

9030

903000

Electronic Commerce—Credit, Certificate Request

9040

900000

Electronic Commerce—No Account Specified, Certificate Request

9510

301000

Balance Inquiry—Savings

9520

302000

Balance Inquiry—Checking

9530

303000

Balance Inquiry—Credit


•

October 2006

Oct 2006

2-51


Completion Codes The MDS displays the completion code as a five-position five-position value. Completion Code Position Status

The following table (Table (Table 2.32—Completion Codes) Codes) provides a list of completion code position statuses. Table 2.32—Completion Codes Position

Status

Value

First position

Completion Status

0 1

Second and Third Position

Transaction Status

See “Completion Code Values.”

Fourth Position

Card Status

0 1

Card Returned Card Captured

Fifth Position

Additional Information

0 1 2 4

Online From store-and-forward store-and-forward Possible Duplicate Transmission Transaction Adjusted

Completed as requested Not completed as requested

Completion Code Values

The following table (Table (Table 2.33—Completion Code Values) Values) provides a list of completion code values. Table 2.33—Completion Code Values

2-52

EX9.2

ISO (DE 60)

Description

00

0000

Completed as requested

10

4510010 4511010

Partial Dispense: Card returned Partial Dispense: Card retained

11

4500011 4501011

Zero Dispense: Card returned; no receipt issued Zero Dispense: Card retained; no receipt issued

18

4500018 4501018

Zero Dispense: Card returned; ATM failure Zero Dispense: Card retained; ATM failure

19

4500019 4501019

Zero Dispense: Card returned; ATM timeout Zero Dispense: Card retained; ATM timeout

October 2006

•



EX9.2

ISO (DE 60)

Description

40

4500041 4501040

Zero Dispense: Card returned; cardholder timeout Zero Dispense: Card retained; cardholder timeout

41

4530040

Financial Transaction Cancellation: Card returned

4531041

Financial Transaction Cancellation: Card retained

80

4020090

Network Advice: IPS timeout error

90

4550090

APS timeout: timeout: Card returned

4551090

APS timeout: timeout: Card retained

91

--

N/A

92

--

N/A

93

--

N/A

99

--

N/A

Batch Message Formats File Header Record Table 2.34—File Header Record Description

Attribute

Comment


4n

5200

Settlement Date

6n

YYMMDD

Processor ID

10 n

Same as 10-digit NCID from online message

Record Size

3n

080

File Type

1 an

Certification File P Production File

Filler

56 an

Blank Fill

Total

80


•

October 2006

C

2-53


Financial/Non-financial (5220) Record Table 2.35—Financial/Non-financial (5220) Record, Segment No. 1

Description

Attribute

ISO 8583 /Subfield

Comment


4n

5220

Segment No.

1n

1

Total No. of Segments Equals

1n

Number of segments associated with this transaction: 1 Dynamic Transaction Validation Record Format 2 Transaction Reconciliation Record Format 4 Transaction Posting Record Format

Processor–acquirer or issuer

1a

A or I identifies type of processor listed in processor ID in Header Record 5200

Processor ID

3n

33

The MDS populates this field with the acquirer or issuer processor ID. •

If receiver of the fil e is the acquirer in the transaction, the last three positions of element 4 will contain the issuer issuer processor ID (not found in the ISO online message).

•

If receiver of the fil e is the issuer in the transaction, the last three positions of element 4 will contain the acquirer acquirer processor ID.

•

The acquirer processor ID appears in the last three positions of DE 33 in the ISO online message.

Transaction Date

6n

13

Local date and time from acquirer Format is: MMDDYY

Transaction Time

6n

12

Local date and time from acquirer Format is: HHMMSS

PAN

19 n

2

Primary Account Number. From online message

Processing Code

4n

3

Amount Settlement Settlement

8n

4/5

Trace Number

6n

11

2-54

From online message

October 2006

•



Description

Attribute

ISO 8583 /Subfield

10 n

32

Acquirer Institution Institution ID

Terminal ID

10 an

Filler

1 an

Total

80

Comment •

From online message

•

The ISO 8583 institution ID is preceded by a 1 because the ISO DE 32 is 9 digits long and the bulk file field is 10 digits long

41 Blank Fill

Table 2.36—Financial/Non-financial (5220) Record, Segment No. 2

Description

Attribute

ISO 8583 /Subfield

Comment


4n

5220

Segment No.

1n

2


1n

Number of segments associated with this transaction: 2 Transaction Reconciliation Record Format Transacti on Posting Record Format 4 Transaction

Response Code

15 an

39

For Stand-In transactions, transactions, positions 5–8 contain STND

Completion Code

10 an

60

From online message


3 an

49

From online message

Conversion Rate–Acq.

8n

9

From online message

Completed Trans Amt— Local

12 n

4

•

From online message

•

When an 0220/0230 or or 04XX message message pair follow the original transaction, the value used is that from DE 95, positions 1–12 of the ISO 8583 message

ATM Access Fee—USD Fee—USD

5 an

28

Interchange Fee

8 an

N/A

Calculated in the Batch Fee Matrix File Can be either U.S. dollars or local currency (ISIS)

Filler

5 an

N/A

Blank fill.


•

October 2006

Oct 2006

From online message message

Oct 2006

2-55


Description

Attribute

ISO 8583 /Subfield

Product Code

3 an

63/1

Filler

5 an

Comment

From online message Cash Back Amount MasterCard will only populate the last fiv e positions of the Cash Back amount.

Total

80

Table 2.37—Financial/Non-financial (5220) Record, Segment No. 3

Description

Attribute

ISO 8583 /Subfield Comment


4n

5220

Segment No.

1n

3


1n

Number of segments associated with this transaction 4 Transaction Transacti on Posting Record Format

Currency Code

3 an

Conversion Conversio n Rate

8n

Condition Code

3n

N/A

Reference Number

12 an

37


10 n

N/A

From internal process by the MDS

Account 1 “From” “From”

19 n

102


Account 2 “To” “To”

19 n

103


Total

From online message

80

Table 2.38—Financial/Non-financial (5220) Record, Segment No. 4 Description

Attribute

ISO 8583 /Subfield

Comment


4n

5220

Segment No.

1n

4


1n

Number of segments associated with this transaction 4 Transaction Posting Record Format

Merchant Type (MCC)

4n

2-56

18

From online message

October 2006

•



Description

Attribute

ISO 8583 /Subfield

Comment

Acq. Institution Name

41 an

43

From online message

Acq. City/State or Country

19 an

43

From online message


9 an

63/2

From online message

Filler

1 an

Total

80

Blank fill

Table 2.39—Financial/Non-financial (5220) Record, Segment No. 5 (Dynamic)

Description

Attribute

ISO 8583 /Subfield

Comment


4 an

5220

Segment No.

1n

5


1n

Number of segments associated with this transaction 5

Merchant ID

15 an

42

From online message

Banknet Reference Number

9 an

63/4

From online message

Acquirer’s Reference Number (ARN)

23 an

63/5

From online message

Filler

26 an

Segment Format Type

1a

Total

80

blank filled M Debit MasterCard

Table 2.40—Financial/Non-financial (5220) Record, Segment No. 5 (Parcelas)

Description

Attribute

ISO 8583 /Subfield

Comment


4 an

5220

Segment No.

1n

Relative segment number


•

October 2006

2-57


Description

Attribute


ISO 8583 /Subfield

1n

Comment

Number of segments associated with this transaction: 2 Validation 3 5

Reconciliation Posting note

Parcelas Identifier

2n

112

21 Value


2n

112

Number of chosen installments

Installment Interest

12 n

112

Estimated installment amount with interest

Purchase Price with Interest

12 n

112

Total amount of transactions with interest


4n

112

Annual interest rate

41 an

N/A


Parcelas Identifier

1a

N/A

P

Total

80

Filler



2-58

Note

Parcelas

Members that receive a two-segment auto reconciliation file and a 5220 addendum record will receive the addendum record segment in the format of a segment 3. Members that receive a four-segment auto reconciliation file and a 5220 addendum record will receive the addendum record segment in the format of a segment 5.

October 2006

•



Table 2.41—Financial/Non-financial (5220) Record, Segment No. 5 for Maestro CDC

Description

Attribute

ISO 8583 /Subfield

Comment


4 an

5220

Segment No.

1n



1n

Number of segments associated with this transaction 2 Validation 3 Reconciliation 5 Posting note

Parcelas Identifier

2n

112

Value = 20


2n

112

Number of requested installments (from inquiry requests)

Estimated Installment Amount

9n

112

Estimated installment amount for number of installments chosen

Total Amount

12 n

112

Total to be repaid via installments


5n

112

Annual interest rate

43 an

N/A


1a

N/A

C

Filler CDC Identifier

I Total

CDC purchase CDC inquiry

80

Airline Ticket Number and Additional Itinerary Data MasterCard will provide the airline ticket number and additional itinerary information in the daily batch auto-reconciliation file (80-byte format only). MasterCard will maintain this data in a new record type 5220 segment that will be generated after the financial 5220 segments. The layout of the new segment follows:


•

October 2006

2-59


Table 2.42—Financial/Non-financial (5220) Record, Airline Ticket Number Segment

Description

Attribute



4n

5220

Segment No.

1n



1n

Number of segments associated with this transaction

Passenger Name

25 an

N/A

Passenger name

Ticket Number

15 an

48

Ticket number

Travel Date

6n

N/A

Travel date in MMDDYY format

Carrier Code

2 an

N/A

Carrier code

Service Class

2 an

N/A

Service class

Stop Over Code

1 an

N/A

Stop over code

City of Origin

5 an

N/A

Origin city

City of Destination

5 an

N/A

Destination city

Spaces

12 an

N/A

Reserved

Airline Indicator

1 an

N/A

A Airline

Exception Transaction (5240) Record Table 2.43—Exception Transaction (5240) Record, Segment No. 1

Description

Attribute



4n

5240

Segment No.

1n

1


1n

Number of segments associated with this transaction 5 Exception Transaction Posting Record Format

Processor–acquirer or issuer

1a

A or I identifies type of processor listed in processor ID in Header Record 5200

Processor ID

3n

2-60

33

•

If receiver of the file is the acquirer in the transaction, the last three positions of element “4” will contain the issuer processor ID.

•

If receiver of the file is the issuer in the transaction, the last three positions of element “4” will contain the acquirer processor ID.

October 2006

•



Description

Attribute

Reversal Date

6n

Reversal Time


6n

13

12

Format is: MMDDYY •

Switch date and time of 0422 (acquirer) message.

•

Switch date and time of 0420 (issuer) message.

Format is: HHMMSS •

Switch date and time of 0422 (acquirer) message.

•

Switch date and time of 0420 (issuer) message.

PAN

19 n

2

Processing Code

4n

3

Org Settlement Amt

8n

4/5

Trace Number

6n

11

From online message

10 n

32

•

From online message

•

Acquirer Institution ID: The ISO 8583 institution ID is preceded by a 1 because the ISO DE 32 i s 9 digits long and the bulk file field is 10 digits long.

Acq. Institution ID

Terminal ID

10 an

Filler

1 an

Total

80


•

October 2006

41

Primary Account Number. From online message

From online message Blank Fill

2-61


Table 2.44—Exception Transaction (5240) Record, Segment No. 2

Description

Attribute

ISO 8583 /Subfield

Comment


4n

5240

Segment No.

1n

2


1n


Response Code

15 an

39

For Stand-In transactions, positions 5–8 contain STND

Completion Code

10 an

60

Oct 2006

•

From online message

•

For Debit MasterCard (MD) transactions: −

Position 8 = Usage Code

−

Position 9 = Document Indicator

Position 10 = Future Use “blank” For more information on Debit MasterCard exception items refer to DE 60 in the MDS Online Specifications manual. −


3 an

49

From online message

Conversion Rate—Acq.

8n

9

From online message

Org. Comp. Trans. Amt—Local

12 n

4

•

From online message

•

When an 0220/0230 or 04XX message pair follow the original transaction, the value used is that from DE 95, positions 1–12 of the ISO 8583 message.

ATM Access Fee—USD

5 an

28

Interchange Fee

8 an

N/A

Calculated in the Batch Fee Matrix File. Can be either U.S. dollars or local currency (ISIS)

Filler

5 an

N/A

Blank fill

Product Code

3 an

63/1

From online message

Filler

5 an

Total

80

2-62

From online message

Oct 2006

Blank Fill

October 2006

•




Description

Attribute



4n

5240

Segment No.

1n

3


1n


Reversal Reason Code

2n

N/A

From online message

New Completed AmountLocal

12 n

95

From online message

Amount Settlement

8n

95

From online message

Reversal Amount

10 n

N/A

From online message

Reversal Amount Credit/Debit Indicator

1 an

N/A

enotes net credit or debit amount from the C or Dd

Original Switch Serial No.

9n

63/3

Original Reconciliation Date

6n

90/3

Original Transaction Date

6n

13

Original Transaction Time

6n

90

Original Acq. Processor

3n

90/5

The last three positions of subfield 5 are used.

Original Iss. Processor

3n

N/A

This value does not appear in ISO 8583 messages.

Filler

8 an

Total

80


issuer’s settlement position.

•

October 2006

•

MMDDYY

•

The MDS retrieves the month and day from the online message. The MDS adds the year value.

Filler

2-63



Description

Attribute



4n

5240

Segment No.

1n

4


1n


Currency Code

3 an

N/A

From online message

Conversion Rate

8n

9

From online message

Condition Code

3n

N/A

From online message

Reference Number

12 an

37

From online message

Card-Issuing Institution

10 n

N/A

From online message

Account 1

19 n

ISIS Reversal Amount

12 n

N/A

From online message

Reversal Credit/Debit

1 an

N/A

C or D; credit or debit from issuers’ perspective

Filler

6 an

Total

80

2-64

102 of From online message original transaction

Blank Fill

October 2006

•




Description

ISO 8583 /Subfield

Attribute

Comment


4n

5240

Segment No.

1n

5

Total No. of Segments

1n


Exception Transaction Posting Record Format

Merchant Type (MCC)

4n

18 of original From online message transaction

Acq. Institution Name

41 an


Acq. City/State or Country

19 an


New Switch Serial Number

9n

Filler

1 an

Total

80


•

October 2006

N/A

From online message Blank Fill

2-65


File Control (5499) Record Table 2.48—File Control (5499) Record Description

Attribute


4n

Processor ID

3n

Total Debit Amount

11 n


Total Credit Amount

Number of Credit Items

Reversal Debit Amount


Reversal Credit Amount

2-66

6n

11 n

6n

10 n

6n

10 n

Comment

5499

•

Calculated in batch processing

•

The sum of all debit 5220 records in the batch file. Debit records contain processing codes that result in a debit to the cardholder’s account.

•

A transaction with a zero settlement (full reversal of an ATM withdrawal) is treated as a debit record.

•


•

The number of debit 5220 records in the batch file

•


•

The sum of all credit 5220 records in the batch file

•

Credit records contain processing codes that result in a credit to the cardholder’s account.

•


•


•


•

The sum of all debit 5420 records in the batch file

•

Debit records contain processing codes that result in a debit to the cardholder’s account.

•


•


•


•

The sum of all credit 5240 records in the batch file

•

Credit records contain processing codes that result in a credit to the cardholder’s account.

October 2006

•



Description

Attribute


Comment

6n

Number of Non-financial

6n

Filler

1 an

Total

80

•


•

The number of credit 5240 records in the batch file

•


•

The number of non-financial 5220 records in the batch file. Non-financial records contain processing codes that result in neither a credit or debit to the cardholder’s account. These include balance inquiries, funds transfers, and electronic commerce certificate requests.

Blank Fill

Settlement (5500) Record Table 2.49—Settlement (5500) Record, Segment No. 1

Attribute

ISO 8583 APS/IPS


4n

N/A

5500

Segment No.

1n

N/A

1


1n

N/A

Number of segments associated with this transaction

Description

Comment

2

Processor–Acq. or issuer

1a

N/A

Transaction Time

6n

7

From online message

Total Debit Amount

11 n

88

From online message


6n

76

From online message

Total Credit Amount

11 n

86

From online message

Number of Credit Items

6n

74

From online message

Filler

33 an

N/A

Total

80


•

October 2006

A or I

Blank Fill

2-67


Table 2.50—Settlement (5500) Record, Segment No. 2

Description

Attribute

ISO 8583 APS/IPS Comment


4n

N/A

5500

Segment No.

1n

N/A

2


1n

N/A


Reversal Debit Amount

10 n

89

From online message


6n

77

From online message

Reversal Credit Amount

10 n

87

From online message


6n

75

From online message

Net Interchange Amount

11 n

97

From online message

Interchange–Credit or Debit

1 an

97

enotes net credit or debit amount from C or Dd the acquirer’s or issuer’s settlement position.

Filler

30 an

Total

80

2-68

N/A

Blank Fill

October 2006

•



80-byte FIT File with Country Code (5300) Record



Note

All U.S. processors and new processor connections must use this record. Each record contains two BIN descriptions and country code. This is not available in the 120 byte or 160 byte record formats. MasterCard will change all new processors or any existing processors changing their bulk files to the 80-byte FIT File with Country Code.

The MDS creates a condensed FIT file containing only the MasterCard, Maestro, or Cirrus BIN records. In some cases, a FIT record for these programs will have the PLUS or Visa product activated. MasterCard does not support the FIT File with Country Code (5300) Record in the 120-byte or 160-byte record formats.

Warning

MasterCard does not supply PLUS/Visa-only BIN records in this file. Members that depend on the MDS to supply PLUS/Visa-only BIN records must make other arrangements to receive this data.

Table 2.51—80 Byte FIT File with Country Code (5300) Record Description

Attribute

Comment

Message Type ID

4n

5300

Maintenance Function

1A

R Replace

ID Length

2n

Identifier

11 n

Processor ID

3n

PAN Length

2n

Not currently used, zero filled

Cirrus Flag

1n

0 1

N Y

MasterCard Flag

1n

0 1

N Y

PLUS Flag

1n

0 1

N Y

Visa Flag

1n

0 1

N Y

Maestro®F lag

1n

0 1

N Y


•

October 2006

Prefix

2-69


Description

2-70

Attribute

Comment

Debit MasterCard Flag

1n

0 1

N Y

Master Banking Flag

1 an

Blank filled not used

Stand-In Flag

1n

0 1

Country Code

3n

If ≠8 40, no ATM access fees allowed

American Express Flag

1n

0 1

N Y

Mondex®Flag

1n

0 1

N Y

Visa Cash Flag

1n

0 1

N Y

Diners

1n

0 1

N Y

Discover

1n

0 1

N Y

MOPP

1n


Filler

1 an

Blanks


1A

R Replace

ID Length

2n

Identifier

11 n

Processor ID

3n

PAN Length

2n

Not currently used, zero filled

Cirrus Flag

1n

0 1

N Y

MasterCard Flag

1n

0 1

N Y

PLUS Flag

1n

0 1

N Y

VISA Flag

1n

0 1

N Y

Maestro Flag

1n

0 1

N Y

debit MasterCard Flag

1n

0 1

N Y

N Y

Prefix

October 2006

•



Description

Attribute

Comment

Master Banking Flag

1n

0 1

N Y

Stand-In Flag

1n

0 1

N Y

Country Code

3n

If ≠8 40, no ATM access fees allowed

American Express Flag

1n

0 1

N Y

Mondex Flag

1n

0 1

N Y

Visa Cash Flag

1n

0 1

N Y

Diners

1n

0 1

N Y

Discover

1n

0

N

1

Y

MOPP

1n


Filler

1 an

Blanks

Filler

2 an

Blanks

Total

80


•

October 2006

2-71


80-byte FIT File without Country Code (5300) Record



Note

Supported only for existing MDS processors.

The MDS creates a condensed FIT file containing only the MasterCard, Maestro, or Cirrus BIN records. In some cases, a FIT record for Cirrus, Maestro, and MasterCard programs will have the PLUS or Visa product activated.

Warning

MasterCard does not supply PLUS/Visa-only BIN records in this file. Members that depend on the MDS to supply PLUS/Visa-only BIN records must make other arrangements to receive this data.

Table 2.52—80-byte FIT File without Country Code (5300) Record Description

2-72

Attribute Comment


4n

5300


1a

R Replace

Identifier Length

2n

Identifier

11 n

Processor ID

3n

Cirrus Flag

1n

0 1

N Y

MasterCard Flag

1n

0 1

N Y

PLUS Flag

1n

0 1

N Y

Visa Flag

1n

0 1

N Y

Maestro Flag

1n

0 1

N Y


1n

0 1

N Y

Master Banking

1 an


Stand-In

1n

0 1

Prefix Value

N Y

October 2006

•



Description

Attribute Comment


1a

Identifier Length

2n

Identifier

11 n

Processor ID

3n

Cirrus Flag

1n

0 1

N Y

MasterCard Flag

1n

0 1

N Y

PLUS Flag

1n

0 1

N Y

Visa Flag

1n

0 1

N Y

Maestro Flag

1n

0 1

N Y

Debit MasterCard Flag

1n

0 1

N Y

Master Banking

1 an


Stand-In

1n

0 1


1a

R Replace

Identifier Length

2n

Identifier

11 n

Processor ID

3n

Cirrus Flag

1n

0 1

N Y

MasterCard Flag

1n

0 1

N Y

PLUS Flag

1n

0 1

N Y

Visa Flag

1n

0 1

N Y

Maestro Flag

1n

0 1

N Y

debit MasterCard

1n

0

N

1

Y

Master Banking


•

October 2006

1 an

R Replace

Prefix Value

N Y

Prefix Value

Blank filled, not used

2-73

Batch File Specifications Batch FIT Data Formats/80-byte Record Size

Description

Attribute Comment

Stand-In

1n

0 1

N Y

Filler

1 an

Blank Fill

Total

80

Batch FIT Data Formats/80-byte Record Size This documentation describes the data elements and file layout used to create a batch Financial Institution Table (FIT) data file from the online database. These FIT data files can be sent to members for full FIT file loads and additional product information. Two FIT Data Files are available for members to receive. The FullF IT Data File contain all fields present in the online FIT record. The Full FIT Data File also includes Visa only, PLUS only, or Visa/PLUS BIN records. The IT File contains all of the fields present in the online FIT record, AbbreviatedF but it does not contain the Visa only, PLUS only or Visa/PLUS BIN records. Members can receive the 80-byte FIT data file and the 250-byte Batch Data File at the same time, or if they elect, they can receive only the FIT Data file prior to receiving both the 250-byte Batch Data File and the FIT Data File. Processors that process through the Banknet telecommunications network receive the FIT Data Files as Full or Abbreviated 80-byte FIT files:



Note

•

Production Bulk ID (T458)

•

Member Test Bulk ID (T459)

For Brazil only: 80 Byte FIT File:

2-74

•

Production BULK ID (T408)

•

Member Test Bulk ID (T409)

October 2006

•



Oct 2006

FIT Header Record (FITH)—Required Table 2.53—FIT Header Record (FITH)

Position

ISO DE# /Subfield


1–4

N/A

4a

FITH (FIT Header)

File Date

5–10

15

6n

Format: MMDDYY

Record Size

11–13

3n

080

1 an

M Member Testing File

Description

File Type

14

N/A


P

Production File

Version

15–24

N/A

10 an

This field displays the current version number of the Batch Data File. The value may increment with changes implemented on a per-release basis.

Filler

25–80

N/A

56 an

Spaces

FIT Data Records (FITD)—Optional

Oct 2006

Table 2.54—FIT Data Record (FITD)—Optional

Description


Position

ISO DE# /Subfield

1–4

N/A


4a

FITD( FIT Data Record–Optional)

This file can be sent either daily or weekly. Additionally, the file may include all BINs or all BINs less PLUS and Visa ID Length

5–6

N/A

2n

Identifier

7–17

N/A

11 an

Issuer Processor ID

18–21

N/A

4n

MDS-assigned processor ID

PAN – Primary Account Number, Length

22–23

N/A

2n

If a prefix has multiple PAN lengths, then the file will contain a FITD for each different length up to three.

Stand-In Flag

24

N/A

1 an

Valid values are : Y Yes N No

Country Code

25–27

N/A

3n

If it is not equal to 840, no ATM access fees are allowed


•

October 2006

Oct 2006

Valid values are from 01–11 Prefix—Left Justified, right spaces

2-75


Description

Position

ISO DE# /Subfield

Region Code

28–29

N/A


2n

Valid values are : 01 02 03 04 05 06

United States Canada Latin America/Caribbean Asia/Pacific Europe Middle East/Africa

Effective Date

30–35

N/A

6n

Format: YYMMDD If effective type is Ct hen this field will contain the original date added to FITD File. Future use; If effective type is A, then this field will contain a future effective add date. Processors must add this FITD on the effective date. If effective type is D, then this field will contain a future delete date. Processors must delete this FITD on the effective date. (A)dd and ( D)elete dates will always be > than the file header date.

Effective Type

36

N/A

1a

C = Current Active FIT (All FITD records contain a Ca t this time)

Future use: A Add FIT D Delete FIT State Code

37–38

N/A

2 an

Used to identify the U.S. region state associated with the issuer bank identification number (BIN).

Filler

39

N/A

1 an

Space

Cirrus Flag

40

N/A

1a


MasterCard Flag

41

N/A

1a


Maestro® Flag

42

N/A

1a


2-76

October 2006

•



Description


Position

ISO DE# /Subfield

43

N/A


1a


PLUS Flag

44

N/A

1a


Visa Flag

45

N/A

1a

Future Product Flag

46

N/A

1 an

Not currently used, blank filled

Future Product Flag

47

N/A

1 an


Future Product Flag

48

N/A

1 an


Future Product Flag

49

N/A

1 an


Future Product Flag

50

N/A

1 an


Future Product Flag

51

N/A

1 an


Future Product Filler

52–55

N/A

4 an


MS-ISIS – ICA

56–61

N/A

6n

Spaces (for Brazil Only) ISIS ICA of Processor’s BIN

62

N/A

1a

(for Brazil Only)

Positive ID Flag


Valid values are: Y Yes N No Default Space= Filler Post Dated Flag

63–64

N/A

2 an

Reserved for future use Spaces

65

N/A

1a

Valid values are: Y Yes N No Space= Default

66

N/A

1a

Valid values are: Y Yes N No Default Space=

(for Brazil Only)

Installment Flag (for Brazil Only)


•

October 2006

2-77


Description

Position

ISO DE# /Subfield

Parcelas Flag

67

N/A


1a

(for Brazil Only)

Valid values are: Y Yes N No Space= Default

CDC Flag

68

N/A

1a

Valid values are: Y Yes N No Default Space=

N/A

1a


N/A

1a


(for Brazil Only)

Preferred Routing Indicator (ATM) 69 Preferred Routing Indicator (POS) 70 Future Service Filler

71

N/A

1a

Space


72–76

N/A

5 an


BIN Reference Number

77–80

N/A

4n

MDS Assigned Value Oct 2006

FIT Trailer Record (FITT)—Required Table 2.55—FIT Trailer Record (FITT)—Required

Position

ISO DE# /Subfield


1–4

N/A

4a

Total Recon Count

5–15

N/A

11 n

Total number of FIT file records including the FIT header and FIT trailer records.

Filler

16–80

N/A

65 an

Spaces

Description

2-78

Attribute Comments and Values FITT (FIT Trailer Record)

October 2006

•


3

Reports This chapter provides a description of the reports included in the MDS Report Transmission File.

Overview .............................................................................................................3-1 Report Transmission .....................................................................................3-1 Settlement Reports...............................................................................................3-4 Daily Control Report—SWCHD363 ..............................................................3-5 Enhancements with this update:............................................................3-6 Daily Control Report—SWCHD363—ISIS Transactions ......................3-19 Daily Control Report—SWCHD363—Institution Level Transactions ..........................................................................................3-25 Daily Interchange Report—SWCHD412.....................................................3-29 Enhancements with this update:..........................................................3-30 Daily Interchange Report—SWCHD412—ISIS Transactions...............3-38 Daily Interchange Report—SWCHD412—Institution Level Transactions ..........................................................................................3-42 Monthly Control Report—SWCHM363.......................................................3-47 Monthly Interchange Report—SWCHM412................................................3-48 Debit MasterCard Inbound/Outbound Fee Report—SWCHD586-A.........3-49 Detail Activity Reports.......................................................................................3-55 Captured Card Report—SWCHD51–Removed...........................................3-57 Exception Audit Report—SWCHD53..........................................................3-58 Detailed Suspect Items Report—SWCHD55...............................................3-67 Acquiring Processor and Cardholder Processor ..................................3-67 Transaction Audit Reports—SWCHD57 and SWCHD108..........................3-74 Acquiring Processor and Cardholder Processor ..................................3-79 Retrieval Request/Fulfillment Report—SWCHD118...................................3-83 Cardholder Processor............................................................................3-83 Account File Updates—SWCHD141-1........................................................3-89 Account Management File Updates—SWCHD141-2..................................3-93 Recurring Payment Cancellation Service—SWCHD141-3..........................3-97 Maestro® POS Transaction Audit Report—SWCHD144..........................3-100 Negative File Updates—SWCHD147-1.....................................................3-105 VIP File Updates—SWCHD147-2 .............................................................3-108


•

October 2006

3-i

Reports

Statistical Reports.............................................................................................3-112 Financial Institution Table Report (FIT)—SWCHD15-X ..........................3-114 FIT by Identifier and FIT by Processor..............................................3-114 Institution Definition File (IDF)—SWCHD35...........................................3-117 Daily Processing Summary Report—SWCHD61 ......................................3-119 Acquiring Processor and Card Processor...........................................3-119 Monthly Availability Report—SWCHD73 .................................................3-125 Cirrus Network and Processor ...........................................................3-125 Daily Cardholder Performance Report—SWCHD127-1...........................3-129 Cardholder Processor..........................................................................3-129 Daily Cardholder Performance Variance Report—SWCHD127-2............3-132 Cardholder Processor..........................................................................3-132 Maestro POS Daily Processing Summary—SWCHD143 ..........................3-134 Acquiring Processor and Cardholder Processor ................................3-134 Daily Processor Performance Report—SWCHD320-1 .............................3-140 Acquiring Processor and Issuing Processor.......................................3-140 Processor Peak Performance Report—SWCHD321-1..............................3-144 Processor Daily Summary Performance Report—SWCHD321-2............. 3-148 Transaction Interchange Month-to-Date—SWCHM03 .............................3-151 Acquiring Processor and Cardholder Processor ................................3-151 Month-to-Date Processing Summary Report—SWCHM06.......................3-155 Acquiring Processor and Cardholder Processor ................................3-155 Month-to-Date Denial Summary Report—SWCHM07 .............................3-161 Issuer ...................................................................................................3-161 ISIS Reports......................................................................................................3-164 Stand-In Reports ..............................................................................................3-166 Related Reports .........................................................................................3-166 Stand-In Transaction Audit Report—SWCHD149 ....................................3-168 Processor Availability Reports.........................................................................3-172 Daily Processor Up Time Report (Settlement Date)—MS1100BB........... 3-174 Daily Processor Up Time Report (Calendar Date)—MS1100DD.............3-177 Monthly Processor Up Time Report —MS1101AA ..................................3-179 Month-to-Date Report—MS1101BB..........................................................3-181

3-ii

October 2006

•


Reports Overview

Overview

Oct 2006

The MDS produces transaction processing summary and detail reports for all products the MDS supports. These reports assist CPS personnel in daily settlement, reconciliation, system management, customer support functions, and provide processor performance statistics.



Note

Oct 2006

All report data in this chapter is fictitious and does not reflect the activity of actual processors.

Report Transmission Members can access MDS reports through two methods: Global File Transfer or MasterCard eService. Members request reports in the form which best suits their business. Refer to Table 3.2 and Table 3.3 for a list of MDS reports. Table 3.1—Report Transmission Timeframes Transmission

Timeframe

Communication line

Monday through Sunday

Banknet in the T461 bulk files

Monday through Saturday

All reports except the four Processor Availability reports are available through Global File Transfer. The MDS transmits reports through Global File Transfer to processors at the end of each settlement day All reports except for SWCHD53, Exception Audit Report, are available through the MasterCard OnLine eService product accessible through MasterCard OnLine®. Members with access to MasterCard OnLine® can view the online MDS reports using their billing ICA. The online reports are available for viewing in eService for a period of 13 months from the original date of publication. The MDS presents all report data in ISO message format. This chapter lists ISO data element numbers next to the field names


•

October 2006

3-1

Reports Overview

The MDS generates the following reports for issuer and acquirer processing systems. Table 3.2—MDS Daily Reports Number

Report Name

Report Type

MS1100BB a

Daily Processor Up Time Report (Settlement Date)

Processor Availability

MS1100DD a

Daily Processor Up Time Report (Calendar Date)


MS1101BB a

Month-to-Date Report


SWCHD15-X

Financial Institution Table Report (FIT)

Statistical

SWCHD35

Institution Definition File (IDF)

Statistical

SWCHD53 c

Exception Audit Report

Detail Activity

SWCHD55

Detailed Suspect Items Report

Detail Activity

SWCHD57/ SWCHD108

Transaction Audit Report (These reports are obsolete

Detail Activity

SWCHD61

Daily Processing Summary Report

Statistical

SWCHD73 b

Monthly Availability Report

Statistical

SWCHD118

Retrieval Request/Fulfillment Report

Detail Activity

SWCHD127-1

Daily Cardholder Performance Report

Statistical

SWCHD127-2

Daily Cardholder Performance Variance Report

Statistical

SWCHD141-1

Account File Updates

Detail Activity

SWCHD141-2

Account Management File Updates

Detail Activity

SWCHD141-3

Recurring Payment Cancellation Service

Detail Activity

SWCHD143

Maestro® POS Daily Processing Summary

Statistical

SWCHD144

Maestro POS Transaction Audit Report

Detail Activity

SWCHD147-1

Negative File Updates

Detail Activity

SWCHD147-2

VIP File Updates

Detail Activity

SWCHD149

Stand-In Transaction Audit Report

Detail Activity (Stand-In)

SWCHD320-1

Daily Processor Performance Report

Statistical

SWCHD321-1

Processor Peak Performance Report

Statistical

SWCHD321-2

Processor Daily Summary Performance Report

Statistical

SWCHD363

Daily Control Report

Settlement

SWCHD412

Daily Interchange Report

Settlement

3-2

but can be requested until April 2007)

October 2006

•


Oct 2006

Oct 2006 Oct 2006

Oct 2006

Reports Overview

Number

Report Name

Report Type

SWCHD586

Debit MasterCard Inbound/Outbound Fee

Settlement

a

Processor Availability reports are not available through Global File Transfer.

b

Reports produced daily with month-to-date totals

c

SWCHD53 is not available via the MasterCard OnLine eService product.

Oct 2006

Table 3.3—MDS Monthly Reports Number

Report Name

Report Type

MS1101AA a

Monthly Processor Up Time Report


SWCHM03 b

Transaction Interchange Month-to-Date

Statistical

SWCHM06 b

Month-to-Date Processing Summary Report

Statistical

SWCHM07 b

Month-to-Date Denial Summary Report

Statistical

SWCHM363

Monthly Control Report

Settlement

SWCHM412

Monthly Interchange Report

Settlement

a

Processor Availability reports are not available through Global File Transfer.

b

Reports produced daily with month-to-date totals.


•

October 2006

Oct 2006

Oct 2006

3-3

Reports Settlement Reports

Settlement Reports The MDS produces settlement reports daily to assist processors in reviewing and reconciling the exchange of funds that has occurred each day through the MDS settlement process. Table 3.4 lists the MDS Settlement reports name and purpose by report number. Table 3.4—MDS Settlement Reports

3-4

Number

Name

Purpose

SWCHD363

Daily Control Report

The MDS generates this report in the acquirer or issuer processor’s designated settlement currency to validate the processor’s daily net settlement position to the processor’s settlement account.

SWCHM363

Monthly Control Report

The MDS generates this report to validate the processor’s monthly net settlement position to the processor’s settlement account.

SWCHD412

Daily Interchange Report

This report assists members with the reconciliation process by providing enhanced fee reporting.

SWCHM412

Monthly Interchange Report


SWCHD586

Debit MasterCard Inbound/ Outbound Fee

Debit MasterCard processors can use this report to track and monitor miscellaneous inbound and outbound fees incurred through the submission of various fee collection messages.

October 2006

•


Oct 2006


Daily Control Report—SWCHD363 Purpose:

The MDS generates this report in the acquirer or issuer processor’s designated settlement currency to validate the processor’s daily net settlement position to the processor’s settlement account.

Description:

This report provides summary detail in the designated settlement currency of the acquirer or issuer processor.

Oct 2006

It is produced by transaction type within product type and includes the following transaction information: •

financial counts for approved and denied,

•

financial amount of transaction,

•

•

financial and non-financial counts and amounts for interchange fee categories, and counts and total amounts for exception items by product.

A Net Settlement Summary page lists the net settlement of transactions, exception items and interchange fees separated by debit, credit, and net for both the acquirer and the issuer. It also provides a final combined net settlement disposition for the Automated Clearing House System (ACH) and the Global Clearing Management System (GCMS). ISIS transactions are detailed on this report. The ISIS Agreement Number and Settlement Service information are included in the header to identify ISIS transaction information. Pages break by currency type within processor, and then by Routing and Transit number (Institution ID) within processor if the processor participates in member level settlement. This report is based upon activity. Therefore, if a transaction type has “0” activity, it is not reported. Refer to Table 3.5 for a description of the SWCHD363 report fields. Frequency: Availability:



Note

Daily Available through Global File Transfer and eService on MasterCard OnLine.

There is also a month-end version of this report (Monthly Control Report— SWCHM363).


•

October 2006

3-5


Oct 2006

Enhancements with this update: Effective with the MDS 06.3 Release, October 2006 the following enhancements have been made to the SWCHD363 Daily Control report. •

•

•

A separate line has been added to show cash disbursement transactions, designated by processing code 17 which is entered in DE 3, (Processing Code), subfield 1, (Cardholder Transaction Type). This new line displays under the “Debit MasterCard Auth”, “Debit MasterCard Clearing”, and “Grand Totals” columns. A separate line has been added under the “Debit MasterCard Auth” column for Healthcare eligibility transactions. This line displays for both Acquiring and Issuing processors and lists the following totals: −

Number Approved transactions

−

Number Denied transactions

−

Financial Total amount

−

Interchange Financial counts, (% Based, Non-Financials, non-billable)

−

Interchange Debit and Credit amounts

A separate Bin Number field has been added and appears under the Report Heading information and to the right of the Institution ID field. This new field contains the six-digit BIN and allows members the ability to sort the report information by BIN, as well as processor ID and institution ID.

For additional information on these three enhancements, refer to the MDS Release 06.3 Document or contact your Customer Operations Services team representative. Table 3.5—SWCHD363 Fields Field

Description

Header Fields—Display at the top of all pages of the report

PROCESSOR

The processor name.

PROCESSOR ID

The MDS assigned processor/member identification number.

INSTITUTION ID

The Routing and Transit number for the institution. This field is included only for processors that participate in member level settlement.

BIN NUMBER

Six-digit number that allows members to sort the report number by a specific bank identification number.

3-6

October 2006

•


Oct 2006


Field

Description

SETTLEMENT SERVICE

The Settlement Service agreed to by participating members. The Settlement Service ID identifies a specific Settlement Service with a cutoff time agreed to by a participating member. Settlement Service IDs are listed below: •

000 MDS Default

•

001 Brazil ISIS

•

002 MDS Debit MasterCard

Settlement Service cutoff times are determined by the Interchange Type, ISIS Agreement Number, and the Product. A service may be in U.S. dollars, local currency, or intra-currency. This field is included only for ISIS activity detail. ISIS AGREEMENT NUMBER

The MDS assigned ISIS Agreement number. This field is included only for ISIS activity detail.

CURRENCY

The currency selected by the acquirer or issuer processor as the currency of settlement. This field displays both the currency name and numeric code.

SETTLEMENT ICA

The unique 6-digit number assigned by MasterCard that identifies a member or processing endpoint for settlement.

Column Headings—Display across the page, just below the Header fields for both acquirers and issuers

TRANSACTION DESCRIPTION

Transaction Type/Account Type designation. Transaction types with all zeros are suppressed.

FINANCIAL NUMBER APPROVED NUMBER DENIALS

The number of approved and denied transactions by Processing Code within each product.

FINANCIAL AMOUNT TRANS

Total amount for cash withdrawals or purchases, or both, by Processing Code within each product.

INTERCHANGE COUNTS NUMBER FINANCIAL NUMBER % BASED NUMBER NONFIN NUMBER NONBILL

Number of interchange fees debited or credited to a transaction. Number of transactions with financial interchange fee. Number of transactions with percentage based i nterchange fee. Number of transactions with non-financial interchange fee. Number of non-billable transactions.

INTERCHANGE AMOUNTS The total amount for transaction interchange fees separated by debits and credits. DEBITS CREDITS


•

October 2006

3-7


Field

Description

Total Fields—Display to the left of the page. All items under Column Headings total for these headings

SUBTOTALS

Totals by each product for all transaction types with activity. This total is by financial and interchange categories (includes transaction counts, amounts, and interchange counts and amounts).

EXCEPTION ITEMS

Total counts and amounts of exception items processed by product, and the counts and amounts of fees debited or credited to a transaction because of an Exception Item. When the MDS reverses a transaction, it adjusts the full amount of the interchange fee from the fi nancial to the non-financial amount.

TOTALS

Totals by each product for all transaction types with activity. This total is by all Financial, Interchange, and exception i tem categories.

GRAND TOTALS

Totals of all transactions by type for all products, financial counts and amounts, and interchange counts and amounts.

SUBTOTALS

Totals of all transactions for all products, financial counts and amounts, and interchange counts and amounts.

EXCEPTION ITEMS

Total number and amount of all exception items for all products, including Interchange.

TOTAL

Totals of all transactions including exception items.

Settlement Fields—Display to the left of the page of acquirer or issuer se ttlement information. Acquirer or issuer settlement information displays on a separate page of the report, but does not have a separate page title.

FINANCIAL SETTLEMENT EXCEPTION ITEMS

Total number and amount of financial transaction processed, separated into debits and credits. •

•

•

•

Total number and dollar amounts of exception items processed, separated into debits and credits. Separate totals for Same Day (Code 09) and Non-Same Day exception items. The MDS processes same day exception items online within the same settlement window as the original transaction. All exception items processed via NICS™ are included in Non-Same Day exception item totals.

SETTLEMENT

Total of Same Day and Non-Same Day exception items.

TOTAL FINANCIAL SETTLEMENT

Total amount of Financial and exception item settlements.

TOTALS FEES SETTLEMENT

Total Net Fees associated with the transactions processed on the settlement date.

INTERCHANGE SETTLEMENT

Net result of the financial settlement, exception items, and total interchange fee settlement.

3-8

October 2006

•


Oct 2006


Field

Description

ATM ACCESS CHARGE

Total of all ATM Access Fees. For reporting purposes only. This amount is included in the financial settlement.

SURCHARGE FREE ALLIANCE

Total of all ATM Surcharge Free Alliance Transactions. This information is only reported on the acquiring side of the transaction.

Net Settlement Summary Headings—Display to the left of the Net Settlement Summary page

TOTAL CURRENCY CONVERSION ASSESSMENT

Total of all Currency Conversion Assessments included in the financial settlement.

ACQUIRER SETTLEMENT SUMMARY

Amounts for financial transactions, exception items, interchange fees, combined total separated by debits and credits providing acquirer net amount. When the net amount is a credit, the MDS displays a CR after the total.

ISSUER SETTLEMENT SUMMARY

Amounts for financial transactions, exception items, interchange fees, combined total separated by debits and credits providing the issuer net amount. When the net amount is a credit, the MDS displays CR after the total.

NET SETTLEMENT TOTAL

Net total amount of all acquiring and issuing activity.

NET SETTLEMENT (ACH)

Amount of the combined settlement net totals from the Acquirers Settlement Summary and the Issuers Settlement Summary. The final net total of both represents the ACH settlement position. When the net amount is a credit, the MDS displays CR after the total.

NET SETTLEMENT (GCMS)

Amount of the combined settlement net totals from the Acquirers Settlement Summary and the Issuers Settlement Summary. These amounts represent the GCMS settlement position.

GCMS Headings—Display across the page, next to the Net Settlement (GCMS) heading at the bottom of the Net Settlement Summary page.

NETACQ

Amounts for financial transactions, exception items, and combined total separated by debits and credits providing acquirer net amount for the GCMS settlement position.

FEEACQ

Acquirer interchange fees associated with the transactions processed on the settlement date.

NETISS

Amounts for financial transactions, exception items, and combined total separated by debits and credits providing the issuer net amount for t he GCMS settlement position.

FEEISS

Issuer interchange fees associated with the transactions processed on the settlement date.

ICA

The unique 6-digit number assigned by MasterCard that identifies a member or processing endpoint for settlement. A member can be a processor, institution, or both. Applies to GCMS settlement data only. Displays below the Net Settlement (GCMS) field.


•

October 2006

3-9

Oct 2006


Figure 3.4—SWCHD363 Daily Control Report (4 of 9)—Acquiring Processor Oct 2006

6 0 4 / 1 0 / 9 : 0 E G : A F P O K R O W

T N U O M A

7 0 . 5 4 9 , 5

0 0 0 6 0 0 0 3 . . . . 6 0 6 1 6 6 9 7 , 5

5 7

3 0 3

0 1 . 0 0 2

1 0 1 6 0 6 . . . 9 0 9 1 1

3 1

1 0 1

0 4 . 6 5

9 0 5 0 . . 8 0 2 8 , 5

S T I D E R C H C T T R R I O O W P S S E S R E T C I L O B O R E R P D T N G D O N R C I A R C Y I R L U E I Q T A C S D A A M

9 9 9 9 9 9 ; R E B M U N N I B

K N A B Y T I C r a T l S l E o T D 9 9 . K 9 9 S N 9 9 . A 9 9 U B 0 0 1 0 0 1 T 0 0 1 S 0 0 0 1 E 0 0 4 0 T 9 0 8 0 : : : : :

3 6 3 D H C W S

D A I C D I I N O T R R I N O O T Y E S S U C M S S T N E E E I E L C C T R T O O S R T R R N U E P P I C S


R E B M U N

T N U O M A

0

7 1 . 9 1

0 0 . 0

S T I B E D R E B M U N

N O I T P I R C S E D

•

0 0

T N E M E L ) T 9 T 0 E S E E G S D L R M O Y A A E E C A I H E T T ( D T C T T C R N I N N N E N F E Y E E A S E G E S L M N A M M N E M N M S E A E O D A E I E E A E E G I L I S L F F L H L C R C T T E - T T C T C A N T P M N T L L T R T A H A E E A O E A A E E E C N S C S N S T T S T S M R I X O O N T U F E T T I A S

October 2006

3-13


Figure 3.5—SWCHD363 Daily Control Report (5 of 9)—Net Settlement Summary Oct 2006

6 0 4 / 1 0 / 9 : 0 E G : A F P O K R O W T E N

R R R C C C 9 1 5 3 8 1 7 5 . . . . 3 4 0 0 1 2 2 1 0 1 1 0 , , 2 2 1 1

T 0 0 0 0 E 0 0 0 0 N . . . . 0 0 0 0

R C 3 5 . 0 1 0 , 2 1 S S I E E F

Y H R C T A T R M I O M W P U S E S R T T I L N B O E E R M D T E N L D O T R C T A E C Y S R L E I T T A E S D N A M

9 9 9 9 9 9 : R E B M U N N I B

K N A B Y T I C r a T l S l E o T D 9 9 . K 9 9 S N 9 9 . A 9 9 U B 0 0 1 0 0 1 T 0 0 1 S 0 0 0 1 E 0 0 4 0 T 9 0 8 0 : : : : :

3 6 3 D H C W S

3-14


T I D E R C

9 0 5 4 8 0 7 6 . . . . 3 0 1 5 1 2 3 0 1 1 , , 2 2 1 1

T 0 0 0 0 I 0 0 0 0 D . . . . E 0 0 0 0 R C

S S I T E N

Q C A E E F T I B E D

0 1 0 1 0 1 0 1 . . . . 0 4 1 5 2 2 1 1

S S E M E E F S T R N I E E O G R I N N I T O A U C I H Q A T C C S P R A N E E A C T L R X N A T E I T O T

0 0 . 0

R C 5 7 . 0 2 1

T 0 0 0 0 I 0 0 0 0 B . . . . E 0 0 0 0 D

Q C A T E N

Y R A M M U S T N E M E L T T E S R E R I U Q C A

0 0 . 0

Y R A M M U S S T S E N M E E E F M S T E N I E L O G R T I N N E T T O A U E C I H S S A T C S S P R I R N E E E A C T L U R X N A S T E I T S O I T

L ) A H T C O A T ( T T N N E E M M E E L L T T T T E E S S T T E E N N

) S M C G ( T N E M E L T T E S T E N

R C 8 7 . 9 8 8 , 1 1

1 1 1 1 0 0 : A C I

October 2006

•



Figure 3.8—SWCHD363 Daily Control Report (8 of 9)—Acquiring Processor

Oct 2006

6 0 3 / 1 0 / 9 : 0 E G : A F P O K R O W

T N U O M A

0 0 . 8 7 7

0 0 0 0 0 0 0 0 . . . . 0 0 0 1 4 3

8 2

0 0 0

0 0 . 7 3 4

0 0 0 0 0 0 . . . 0 0 0

7 1

0 0 0

0 5 . 5

2 0 6 0 . . 6 0 3 3

S T I D E R C H C T T R R I O O W P S S E S R E T C I L O B O R E R P D T N G D O N R C I A R C Y I R L U E I Q T A C S D A A M

R E B M U N

9 9 9 9 9 9 : R E B M U N N I B

T N U O M A

0

8 8 . 9

0 0 . 3 9

S T I B E D

r a l l o D 9 9 . 9 9 S Q 9 9 . C 9 9 U A 9 0 7 9 0 6 T 9 0 5 S 9 0 0 4 E 9 0 4 0 T 9 0 8 0 : : : : :

3 6 3 D H C W S

R E B M U N

D A I C D I I N N O T O R R I N I O O T Y E T S S U C M P S S T N E I E E I E L R C C T R T C O O S R T S R R N U E E P P I C S D


•

2 0 6

T N E M E L ) T 9 T 0 E S E E G S D L R M O Y A A E E C A I H E T T ( D T C T T C R N I N N N E N F E Y E E A S E G E S L M N A M M N E M N M S E A E O D A E I E E A E E G I L I S L F F L H L C R C T T E - T T C T C A N T P M N T L L T R T A H A E E A O E A A E E E C N S C S N S T T S T S M R I X O O N T U F E T T I A S

October 2006

3-17


Figure 3.9—SWCHD363 Daily Control Report (9 of 9)—Net Settlement Summary 6 0 5 / 1 0 / 9 : 0 E G : A F P O K R O W T E N

0 0 0 0 0 0 0 0 . . . . 0 0 0 0

R C T 1 2 0 9 E 1 7 5 8 N . . . . 3 7 4 9 5 5 1 0 1 1 4 4 , , , 7 0 7 8 1 9 8 8 , , 1 1

9 8 . 9 0 4 , 7 9 8 , 1 S S I E E F


9 9 9 9 9 9 : R E B M U N N I B

K N A B K Y N T A I B C r a T T l S S l E E o T T D L 9 9 . A 9 9 S I 9 9 . C 9 9 U R 0 9 9 E 0 0 9 M 0 0 9 M 0 0 0 9 O 0 0 4 0 C 9 0 8 0 : : : : :

3 6 3 D H C W S

3-18

T I D E R C

0 0 0 0 0 0 0 0 . . . . 0 0 0 0

T 0 1 0 1 I 0 2 0 2 D . . . . E 0 1 1 2 R 1 1 C 3 3

S S I T E N


Y R A M M U S T N E M E D A L I C T D I T I N E O T S R R I N O O T Y E R S S U C M E S S T N E R E E I E L I C C T R T U O O S R T Q R R N U E C P P I C S A

0 0 0 0 0 0 0 0 . . . . 0 0 0 0


T 1 9 0 0 I 1 4 5 1 B . . . . E 3 3 5 2 D 5 5 1 2 1 1 4 7 , , , 7 0 7 8 1 9 8 8 , , 1 1


Q C A T E N



0 5 . 4 1 4 , 0 1

9 3 . 5 9 9 , 6 8 8 , 1

0 0 . 0

0 0 . 0

9 9 9 9 0 0 : A C I

October 2006

•


Oct 2006


Daily Control Report—SWCHD363—ISIS Transactions The following pages provide an example of the Daily Control Report— SWCHD363 with ISIS transactions detailed on the report. The ISIS Agreement Number and Settlement Service information are included in the header to identify ISIS transaction information.


•

October 2006

3-19


Figure 3.11—SWCHD363 Daily Control Report—ISIS Transactions (2 o f 5)—Acquiring Processor

Oct 2006

6 0 8 / 4 1 0 / 9 : 0 E G : A F P O K R O W

T N U O M A

2 0 7 : Y R T N U O C

H C T T R R I O O P S W S E S R E T C I L O B O R E R P D T N G D O N R C I A R C Y I R L U E I Q T A C S D A A M

3 6 3 D H C W S

0 0 . 0 0 2 , 6 1

0 0 0 0 0 0 0 0 . . . . 0 0 0 0 0 2 , 6 1

0 0 . 0 6

0 0 . 0 6 2 , 6 1

0 0 . 0

S T I D E R C 9 9 9 9 9 9 : R E B M U N N I B

K N A B r a Y l T l I o C D 1 T e R S r O E o S T p S a E 9 9 g C 9 9 n O 9 9 i R 9 9 S P 0 9 9 0 0 9 T 0 2 0 9 S 0 0 0 0 2 9 E 0 0 7 0 0 0 T 9 0 C 0 7 0 : : : : : : : E R C B I N V R T D A E N I C D S E I I M N T E O T R R N E I N O O E R T Y E S S M G U C M S S E A T N E E E L I E L C C T S T R T O O T I S R T R R E S N U E P P S I I C S


R 0 E 3 B M U N

0 0 0

0 0 . 0

0 0 0 0 0 0 . . . 0 0 0

R 0 E B M U N

0 0 0

T N U O M A

0

0 0 . 0

0 0 . 0

S T I B E D


•

T N E M E L ) T 9 T 0 E S E S D L M O Y A E C A I T T ( D T C N I N N E Y E E A L M N A M M N A E O D A E I I L I S L F C T T E - T N T P M N T L A E E A O E A N S C S N S T I X O F E T

October 2006

0 0

E G R A E H E T T C R N E N F S E G E S E M N M S E E E A E E G F L H L C R T C T C A L T R T A H A E E E C T S T S M R O N T U T I A S

3-21


Figure 3.13—SWCHD363 Daily Control Report—ISIS Transactions (4 of 5)—Issuing Processor

Oct 2006

6 0 4 / 1 0 / 9 : 0 E G : A F P O K R O W

T N U O M A

0 0 . 7 3 4

0 0 0 0 0 0 . . . 0 0 0

7 1

0 0 0

0 0 . 8 7 7

0 0 0 0 0 0 0 0 . . . . 0 0 0 1 4 3

8 2

0 0 0

8 8 . 9

0 0 0 0 0 0 . . . 0 0 0

S T I D E R C H C T T R R I O O W P S S E S R E T C I L O B O R E R P D T N G D O N R C I A U C Y S R L S E I I T A S D A M

9 9 9 9 9 9 : R E B M U N N I B

K N A B Y T I C r a T l S l E o T D R E 9 9 . U 9 9 S S 9 9 . S 9 9 U I 9 9 0 9 0 0 T 9 0 0 S 9 0 0 0 E 9 0 4 0 T 9 0 8 0 : : : : :

3 6 3 D H C W S

R E B M U N

T N U O M A

0

0 5 . 5

2 0 0 0 6 0 0 0 . . . . 6 3 0 0 3 9 3

S T I B E D R E B M U N

D A I C D I I N N O T O R R I N I O O T Y E T S S U C M P S S T N E I E E I E L R C C T R T C O O S R T S R R N U E E P P I C S D


•

2 6

0

T N E M E L ) T 9 T 0 E S E E G S D L R M O Y A A E E C A I H E T T ( D T C T T C R N I N N N E N F E Y E E A S E G E S R L M N A M M N E M N M S A C E A E O D A E I E E A E E C C G I L I S L F F L H L C C I R C T T E - T T C T C A N T P M N T L L T R T A L L H A E E A O E A A E E E A A C N S C S N S T T S T S M T T R I X O O N T O O U F E T T I A T T S

October 2006

3-23


Figure 3.14—SWCHD363 Daily Control Report—ISIS Transactions (5 o f 5)—Net Settlement Summary 6 0 0 / 1 1 0 / 9 : 0 E G : A F P O K R O W T E N

R R R C C C 0 0 0 0 0 0 7 7 . . . . 0 0 3 3 5 9 4 7 4 2 , , 3 4 9 9

T 0 0 0 0 E 0 0 7 7 N . . . . 0 0 9 9 4 5 9 1 2 3 , , 8 8 4 4

R C 0 0 . 4 4 8 , 5 4 S S I E E F

2 0 7 : Y R T N U O C Y H R C T A T R M I O M W P U S E S R T T I L N B O E E R M D T E N L D O T R C T A E C Y S R L E I T T A E S D N A M

3 6 3 D H C W S

3-24

9 9 9 9 9 9 : R E B M U N N I B

K N A B r a Y l T l I o C D 1 T e R S r O E o S T p S a E 9 9 g C 9 9 n O 9 9 i R 9 9 S P 0 9 9 0 0 9 T 0 2 0 9 S 0 0 0 0 2 9 E 0 0 7 0 0 0 T 9 0 C 0 7 0 : : : : : : : E R C B I N V R T D A E N I C D S E I I M N T E O T R R N E I N O O E R T Y E S S M G U C M S S E A T N E E E L I E L C C T S T R T O O T I S R T R R E S N U E P P S I I C S

T I D E R C

0 0 0 0 0 0 7 7 . . . . 0 0 3 3 5 9 4 7 4 2 , , 3 4 9 9

T 0 0 0 0 I 0 0 0 0 D . . . . E 0 0 0 0 R C

S S I T E N

0 7 . 9 5 2

0 0 . 0 4 1 , 8 4

R C 0 Q 7 C . A 3 E 9 E 4 F T 0 0 0 0 I 0 0 0 0 B . . . . E 0 0 0 0 D



T 0 0 0 0 I 0 0 7 7 B . . . . E 0 0 9 9 D 4 5 9 1 2 3 , , 8 8 4 4


R C 0 Q 0 C . A 0 T 5 E 7 N , 3 9



9 9 9 9 0 0 : A C I

October 2006

•


Oct 2006


Daily Control Report—SWCHD363—Institution Level Transactions The following pages provide an example of the Daily Control Report— SWCHD363 with Institution Level transactions detailed on the report. This report will page break by currency type within processor, and then by Routing and Transit number within processor if the processor participates in member level settlement.


•

October 2006

3-25


Figure 3.16—SWCHD363 Daily Control Report—Institution Level Trans (2 of 3)—Acquiring Processor 6 0 4 / 1 0 / 9 : 0 E G : A F P O K R O W

T N U O M A

0 6 . 7 6 5 , 1

0 0 0 0 0 0 0 6 . . . . 0 0 0 7 6 5 , 1

5 7 . 6

5 3 . 4 7 5 , 1

0 0 . 0

4

0 0 0

0 0 . 0

0 0 0 0 0 0 . . . 0 0 0

0

0 0 0

0 0

T N E M E L ) T 9 T 0 E S E S D L M O Y A E C A I T ( D T C I N N Y E E A N A M M N O D A E I I S L F T E - T P M N T L E A O E A C S N S T X O E T

E G R A E H E C R F S S E E G C R C A A H C M R T U A S

S T I D E R C

H T C R R T O O I P S W E S S R E C T L O I O R B R P E T D N G O N D C I R R A Y I C L U R I Q E A C T D A S A M

R E B M U N

9 9 9 9 9 9 : R E B M U N N I B

T N U O M A

R E B M U N

D D A I I C D I I N N O O T R R I I N O O T T Y E S S U U C M S S T T N E E E I I E L C C T T R T O O S S R T R R N N U E P P I I C S


0 0 . 0

0 0 . 0

S T I B E D

K K N N A A B B Y Y T T I I C C r a T T l S S l E E o T T D 9 2 9 . K 9 2 9 S N 9 2 9 . A 9 2 9 U B 0 2 9 9 0 0 0 9 T 0 0 0 9 S 0 0 0 0 9 E 0 0 0 4 0 T 9 1 0 8 0 : : : : : :

3 6 3 D H C W S

0


•

T N E L M A E I L C T N T A E N S I F

October 2006

T N S E E M E E F L T L T A E T S O T

T E N G E N M A E H L C T R T E E T S N I

3-27

Oct 2006


Figure 3.17—SWCHD363 Daily Control Report—Institution Level Trans (3 of 3)—Net Settle Summary 6 0 5 / 1 0 / 9 : 0 E G : A F P O K R O W T E N

R R C C 5 0 5 5 0 2 . . . 9 0 8 9 4 5 , 4

R C 0 8 . 7 4 6 , 4

T 0 0 0 E 0 0 0 N . . . 0 0 0

0 0 . 0

R R C C 0 0 8 8 . . 7 7 4 4 6 6 , , 4 4

S S I E E F


9 9 9 9 9 9 : R E B M U N N I B

K K N N A A B B Y Y T T I I C C r a T T l S S l E E o T T D 9 2 9 . K 9 2 9 S N 9 2 9 . A 9 2 9 U B 0 2 9 9 0 0 0 9 T 0 0 0 9 S 0 0 0 0 9 E 0 0 0 4 0 T 9 1 0 8 0 : : : : : :

3 6 3 D H C W S

3-28

D D A I I C D I I N N O O T R R I I N O O T T Y E S S U U C M S S T T N E E E I I E L C C T T R T O O S S R T R R N N U E P P I I C S

T I D E R C

5 0 5 5 0 2 . . . 9 0 8 9 4 5 , 4

0 8 . 7 4 6 , 4

T 0 0 0 I 0 0 0 D . . . E 0 0 0 R C

0 0 . 0

S S I T E N


0 0 0 0 0 0 . . . 0 0 0

0 0 . 0

T 0 0 0 I 0 0 0 B . . . E 0 0 0 D

0 0 . 0

Q C A T E N


S S E M E E F S T N I E O G I N N T O A C I H A T C S P R N E E A C T R X N T E I

R E R I U Q C A L A T O T

Y R A M M U S S T S E N M E E E F M S T E N I E L O G T I N N T T O A E C I H S A T C S P R R N E E E A C T U R X N S T E I S I

R E U S S I L A T O T



October 2006

9 9 9 9 0 0 : A C I

•


Oct 2006


Daily Interchange Report—SWCHD412 Purpose:


Description:

This report provides each fee record description alphabetically by product and the interchange fee record within the product category. Amounts are presented in the designated settlement currency of the processor. The MDS divides the Daily Interchange Report into three sections. •

fee description by category,

•

transaction volume by category, and

•

interchange fees for each category.

The report shows all fee counts, separated by Financial, Percentage-based, Non-financial, and Non-billable categories. The MDS segregates this report according to acquiring and issuing processor. The report page breaks on currency types within processors. The Net Interchange Summary page lists the acquirer and issuer’s net interchange fees. The information is also listed by acquirer and issuer on the Net Settlement Summary page of the Daily Control Report—SWCHD363. This report is activity driven. If a fee does not have activity, it is not shown. ISIS appearing in the FEE DESCRIPTION field identifies the ISIS

transactions. Refer to Table 3.6 for a description of the SWCHD412 report fields. Frequency: Availability:


•


October 2006

3-29

Oct 2006


Oct 2006

Enhancements with this update: Effective with the MDS 06.3 Release, October 2006 the following enhancement has been made to the SWCHD412 Daily Interchange report. •

A separate Bin Number field has been added and appears under the Report Heading information and to the right of the Institution ID field. This new field contains the six-digit BIN and allows members the ability to sort the report information by BIN, as well as processor ID and institution ID.

For additional information on this enhancement, refer to the MDS Release 06.3 Document or contact your Customer Operations Services team representative.



Note

Line calculations for interchange fees can not be validated due to percentage based interchange for Maestro POS calculations. Line calculations for acquirer generated interchange cannot be validated because the interchange values differ for each transaction. There is a month-to-date version of this report (Monthly Interchange Report— SWCHM412).

Table 3.6—SWCHD412 Fields Field

Description

Header Fields—Display at top of all pages of the report. Oct 2006

PROCESSOR

The processor name.

PROCESSOR ID

The MDS-assigned processor/member identification number.

INSTITUTION ID

The Routing and Transit number for the institution. This field is included only for processors that participate in member l evel settlement.

BIN NUMBER

Six-digit number that allows members to sort the report number by a specific bank identification number.

SETTLEMENT SERVICE

The Settlement Service agreed to by participating members. The Settlement Service ID identifies a specific Settlement Service with a cutoff time agreed to by a participating member. Settlement Service IDs are listed below: MDS Default 000 001 Brazil ISIS MDS Debit MasterCard 002 Settlement Service cutoff times are determined by the Interchange Type, ISIS Agreement Number, and the Product. A service may be in U.S. dollars, local currency, or intra-currency. This field is included only for ISIS activity detail.

3-30

October 2006

•



Field

Description

ISIS AGREEMENT NBR

The MDS-assigned ISIS Agreement number. This field is included only for ISIS activity detail.

FX

The exchange rate used for the settlement currency.

CURRENCY

The currency selected by the acquirer or issuer processor as the currency of settlement. The field displays both the currency name and numeric code.

SETTLEMENT ICA

The unique 6-digit number assigned by MasterCard that identifies a member or processing endpoint for settlement.

Oct 2006

Oct 2006

Column Headings—Display across the page just below the Header fields for both acquirers and issuers.

FEE DESCRIPTION

Provides the name of each fee record and the corresponding interchange fees associated with the applicable product.

FIN

Financial Interchange Fee is the amount the issuer (ATM transaction) pays to the acquirer or the acquirer (POS transaction) pays to the issuer for financial transactions.

PCT

The Percentage Based Interchange Fee is the amount the issuer (ATM transaction) pays to the acquirer, or the acquirer (POS transaction) pays to the issuer for percentage based transactions.

NON FIN

Non-financial Interchange Fee is the amount the issuer (ATM transaction) pays to the acquirer or the acquirer (POS transaction) pays to the issuer on non-financial transactions.

MIN

Minimum Interchange Fee (if applicable).

MAX

Maximum Interchange Fee (if applicable)

COUNTS FINANCIAL % BASED NON-FINANCIAL NON-BILL AMOUNTS DEBIT CREDIT

Total number of financial transactions assessed an interchange fee. Total number of percentage based transactions assessed an interchange fee. Total number of non-financial transactions assessed an interchange fee. Total number of financial and non-financial transactions not assessed an interchange fee. Total monetary amounts for interchange fees separated by debits and credits.

Total Fields—Display to the right of the product name along the left side of the page. All items under Column Headings total for these headings.

SUBTOTAL

Total counts and amounts of fee categories by product.

EXCEPTION ITEMS

Total counts and fee amounts of Exception Items by product.

TOTAL

Total counts and amounts of interchange fees by product.


•

October 2006

3-31


Field

ACQUIRER/ISSUER TOTAL

Description

Total interchange fee counts and amounts for all categories as acquirer or issuer. Heading depends on whether the page heading indicates ACQUIRING PROCESSOR or ISSUING PROCESSOR.

Net Interchange Summary Headings—Display to the left of the NET INTERCHANGE SUMMARY page.

ACQUIRER SETTLEMENT SUMMARY

The counts and amounts for ATM and POS interchange fees separated by debits and credits, providing the acquirer net amount. The net amount has a Credit (CR) or Debit (DB) indicator after the total.

ISSUER SETTLEMENT The counts and amounts for ATM and POS interchange fees separated by debits and SUMMARY credits, providing the issuer net amount. The net amount has a Credit (CR) or Debit (DB) indicator after the total. NET INTERCHANGE The final net Credit (CR) or Debit (DB) total of acquirer and issuer summary net SETTLEMENT totals. This heading displays at the bottom of the page.

3-32

October 2006

•


Oct 2006


Figure 3.20—SWCHD412 Daily Interchange Report (3 of 5)—Acquiring Processor 6 3 0 / 1 0 / 9 0 : : F E O G A K P R O W

T H R C O T P R I E O W R S S S E E T G C I N O B A R E H P D C R G D E N R T I A N R C I I R U E Y Q T L C S I A A A M D

9 9 9 9 9 9 : R E B M U N N I B

K N A B Y T I C R A T L S L E O T D 9 9 . 9 9 S K 9 9 . N 9 9 U A 0 9 9 B 0 0 9 T 0 0 9 S 0 0 0 9 E 0 0 4 9 T 9 0 8 9 : : : : :

2 1 4 D H C W S



- T - I - D - E - R - C S T N U O M A - T - I - B - E - D - L - L - I - B - N - O - N - L - A - I - C - N - A - N - I - F - N S - O T - N N U O C - D - E - S - A - B - % - L - A - I - C - N - A - N - I - F -

N O I T P I R C S E D E E F

•

- X - A - M - N - I - M - N - I - F - N - O - N - T - C - P - N - I - F -

5 2 . 2

0 0 . 0

0

2

0

4

0

0

D 5 2 C I T S 0 E 0 M . O D 1 D # 0 5 L P

October 2006

- 5 - 2 - . - 2 - 0 - 0 - . - 0 - 0 - 2 - 0 - 4 - L - A - T - O - T - B - U - S - S - U - L - P -

0 0 . 0

0 0 . 0

0

0

0

0

S M E T I N O I T P E C X E

S U L P

- 5 - 2 - . - 2 - 0 - 0 - . - 0 - 0 - 2 - 0 - 4 - L - A - T - O - T - S - U - L - P -

Oct 2006

- 0 - 5 - . - 0 - 3 - 6 - 0 - 0 - . - 0 - 0 - 7 - 5 - 4 - 0 - 2 - 1 - 0 - , - 1 - L - A - T - O - T - R - E - R - I - U - Q - C - A -

3-35


Figure 3.21—SWCHD412 Daily Interchange Report (4 of 5)—Issuing Processor 6 4 0 / 1 0 / 9 0 : : F E O G A K P R O W

T H R C O T P I E R W R O S S E S T G E I N C B A O E H R D C P R D E G R T N A N I C I U R S E Y S T L I S I A A M D

9 9 9 9 9 9 : R E B M U N N I B


2 1 4 D H C W S

3-36


- T - I - D - E - R - C S T N U O M A - T - I - B - E - D - L - L - I - B - N - O - N - L - A - I - C - N - A - N - I - F S - N T - O N - N U O C - D - E - S - A - B - % - L - A - I - C - N - A - N - I - F

- X - A - M - N - I - M - N - I - F - N - O N - N O I T P - T I - C R - P C S E D - N - I E - F E F -

1 6 . 2

0 0 . 0

0 0 . 0

0 0 . 0

0 0 . 0

5 2 . 5 7 3 , 2

5 2 . 2 5 1

0 0 . 4 5

0

0

0

0

2

3 8 1 , 1

1 2

2 2

1 1

0

0

0

0

1 6 1 , 4

8 1 1

9 3

C 0 5

0

0

0

C I 0 T S E M O D C 5 E 7 S . A H C R C U 5 P 1 I C

D 5 2 C I T S E M 0 O 0 D . M T A D 0 1 5 # I C

0

0

0 R 0 E R I U Q D C D 5 A 5 2 2 L T N I L T 0 A 0 N 0 L 0 I . . M M T T A A D D 5 5 5 1 2 1 2 # 1 # 1 I I C C

- 1 - 6 - . - 2 - 0 - 5 - . - 1 - 8 - 5 - , - 2 - 0 - 8 - 2 - 2 - , - 1 - 1 - 1 - 8 - 1 - 3 - , - 4 - L - A - T - O - T - B - U - S - S - U - R - R - I - C -

5 2 . 1

5 2 . 0

0

0

0

7

S M E T I N O I T P E C X E

S U R R I C

- 6 - 8 - . - 3 - 5 - 7 - . - 1 - 8 - 5 - , - 2 - 0 - 8 - 2 - 2 - , - 1 - 1 - 1 - 5 - 2 - 3 - , - 4 - L - A - T - O - T - S - U - R - R - I - C -

- 6 - 8 - . - 3 - 5 - 7 - . - 1 - 8 - 5 - , - 2 - 0 - 8 - 2 - 2 - , - 1 - 1 - 1 - 5 - 2 - 3 - , - 4 - L - A - T - O - T - R - E - U - S - S - I -

October 2006

•


Oct 2006


Figure 3.22—SWCHD412 Daily Interchange Report (5 of 5)—Net Interchange Summary 6 5 0 / 1 0 / 9 0 : : F E O G A K P R O W

T H R Y C O R T P A I E M W R M S U E S T G I N E B A G E H N D C A R H D E C R T R A N E C I T R N E Y I T L S I T A A E M D N

9 9 9 9 9 9 : R E B M U N N I B


2 1 4 D H C W S


- T - E - N - T - I - D - E - R - C S T N U O M A - T - I - B - E - D -

R C 0 0 5 0 . . 0 0 3 6

L - L - I - B - N - O - N - L - A - I - C - N - A - N - I - F - N - O S - N T N - D U - E O - S C - A - B - % - L - A - I - C - N - A - N - I - F Y R A M M U S R E R I U Q C A -

0 0


•

0 0 5 0 . . 0 0 3 6

0 0 0 0 . . 0 0

7 0 5 4

0 0

2 0 1 0 , 1

S N O I T C A S N A R T M T A

S N O I T C A S N A R T S O P

October 2006

- R - C - 0 - 5 - . - 0 - 3 - 6 - 0 - 5 - . - 0 - 3 - 6 - 0 - 0 - . - 0 - 0 - 7 - 5 - 4 - 0 - 2 - 1 - 0 - , - 1 - L - A - T - O - T

- T - E - N - T - I - D - E - R - C S T N U O M A - T - I - B - E - D - L - L - I - B - N - O - N - L - A - I - C - N - A - N - I - F - N - O S - N T N - D U - E O - S C - A - B - % - L - A - I - C - N - A - N - I - F Y R A M M U S R E U S S I -

B D 0 5 . 0 8 5 , 2

R C 1 6 . 2

5 1 2 6 . . 1 2

5 0 7 0 . . 1 0 8 5 , 2

0 0

6 2 2 2 , 1

0 1 1

5 0 2 3 , 4



- B - D - 9 - 8 - . - 7 - 7 - 5 - , - 2 - 6 - 8 - . - 3 - 5 - 7 - . - 1 - 8 - 5 - , - 2 - 0 - 8 - 2 - 2 - , - 1 - 1 - 1 - 5 - 2 - 3 - , - 4 - L - A - T - O - T

Oct 2006

B D 9 3 . 7 4 9 , 1

T N E M E L T T E S E G N A H C R E T N I T E N

3-37


Daily Interchange Report—SWCHD412—ISIS Transactions The following pages provide an example of the Daily Interchange Report— SWCHD412 with ISIS transactions detailed on the report. The ISIS Agreement Number and Settlement Service information are included in the header to identify ISIS transaction information.

3-38

October 2006

•



Figure 3.25—SWCHD412 Daily Interchange Report—ISIS Transactions (3 of 3)—Net Intrch Summary 6 2 0 2 / 1 0 / 9 0 : : F E O G A K P R O W

T R Y H C O R T P A I E M W R M S U E S T G I N E B A G E H N D C A R H E C D R T R A N E C I T R N E Y I T L S I T A A E D M N

2 1 4 D H C W S

- T - E - N - T - I - D - E - R - C S T N U O M A - T - I - B - E - D -

9 9 9 9 9 9 : R E B M U N N I B

- L - L - I - B - N - O - N - L - A - I - C - N - A - N - I - F - N - O S - N T N - D U - E O - S C - A - B - % - L - A - I - C - N - A - N - I - F Y R A M M U S R E R I U Q C A -

K N A A B L E Y U T Z I E C N E T V S E R F T A O V 9 9 I K 9 9 L N 9 9 O A 9 9 B B 0 9 9 0 0 9 T 0 2 0 9 S 0 0 6 0 2 9 E 0 0 8 0 6 0 T 9 0 C 0 8 0 : : : : : : : E R C B I N V R T D A E N I C D S E I I M N T E O T R R N E I N O O E R T Y E S S M G U C M S S E A T N E E E L I E L C C T S T R T O O T I S R T R R E S N U E P P S I I C S


•

R C 0 0 . 0 6 6 , 7

R C 0 0 . 0 0 8 , 1

0 0 . 0 6 6 , 7

0 0 . 0 0 8 , 1

0 0 0 0 . . 0 0

0 0

9 8 0 0 1 5

0 0

4 6 1 4 3 , 2



October 2006

- R - C - 0 - 0 - . - 0 - 6 - 4 - , - 9 - 0 - 0 - . - 0 - 6 - 4 - , - 9 - 0 - 0 - . - 0 - 0 - 7 - 1 - 6 - 0 - 0 - 6 - 3 - , - 2 - L - A - T - O - T


B D 0 0 0 0 . . 0 0 0 2 , 6

0 0 0 0 . . 0 0

0 0 0 0 . . 0 0 0 2 , 6

0 0

0 0 3 5 2

0 0

8 9 5 8 5 , 1



- B - D - 0 - 0 - . - 0 - 0 - 2 - , - 6 - 0 - 0 - . - 0 - 0 - 0 - . - 0 - 0 - 2 - , - 6 - 0 - 0 - 8 - 2 - 0 - 7 - 4 - 6 - , - 1 - L - A - T - O - T

R C 0 0 . 0 6 2 , 3


3-41

Oct 2006


Daily Interchange Report—SWCHD412—Institution Level Transactions The following pages provide an example of the Daily Interchange Report— SWCHD412 with Institution Level transactions detailed on the report. This report will page break by currency type within processor, and then by Routing and Transit number within processor if the processor participates in member level settlement.

3-42

October 2006

•



Figure 3.27—SWCHD412 Daily Interchange Report—Institution Level Trans (2 of 4)—Acq. Processor 6 9 0 3 / 1 0 / 9 0 : : F E O G A K P R O W

T H R C O T P R I E O W R S S S E E T G C I N O B A R E H P D C R G D E N R T I A N R C I I R U E Y Q T L C S I A A A M D

9 9 9 9 9 9 : R E B M U N N I B

K N A B Y T I C R A T L R S L O E O S T D S E 8 9 . C 8 9 S O 8 9 . R 8 9 U P 0 9 0 0 0 0 T 0 0 0 S 0 0 0 0 E 0 0 4 0 T 9 0 8 0 : : : : :

2 1 4 D H C W S

3-44

- T - I - D - E - R - C S T N U O M A - T - I - B - E - D - L - L - I - B - N - O - N - L - A - I - C - N - A - N - I - F S - N T - O N - N U O C - D - E - S - A - B - % - L - A - I - C - N - A - N - I - F

- X - A - M - N - I - M - N - I - F - N - O N - N D A O I C I D I T I N P - T O T I - C R R I N R - P O O T Y E C S S U C M S S S T N E E E E I E L D - N C C T R T - I O O S R T E - F R R N U E E P P I C S F -

0 5 . 1

5 7 . 5 7

0 5 . 7

0 0 . 0

0 0 . 0

0 0 . 0

0

0

0

6

8

0

0

0

0

0

9 5

6

0

0

0

0 Q C A L D T 5 N 2 I A L I 0 B 0 . M T A D 5 5 1 2 # S M

6 0 0 0 & 5 1 0 D I 5 S 2 F 4 0 9 # 0 0 O . O F M D T 5 A 2 1 S M

7 0 0 0 & 5 1 0 D I 5 S 2 F 5 0 9 # 0 0 O . O F M D T 5 A 2 1 S M

- 0 0 - 0 - 5 0 - 5 - . . - . - 8 0 - 8 - 1 - 1 - 2 - 2 - 0 0 - 0 - 0 0 - 0 - . . - . - 0 0 - 0 - 0 0 - 0 - 9 0 - 9 - 4 - 4 - 0 0 - 0 - 5 0 - 5 - 6 - 6 - 1 - 1 - L S - L - A M - A - T E - T - O T - O - T I - T - B - U N - S O - I - T - P - E - C - X - E - M M - M - T T - T - A A - A - O O - O - R R - R - T T - T - S S - S - E E - E - A A - A - M M - M -

- 5 - 7 - . - 9 - 1 - 3 - 0 - 0 - . - 0 - 0 - 4 - 9 - 0 - 1 - 4 - 2 - L - A - T - O - T - R - E - R - I - U - Q - C - A -

October 2006

•


Oct 2006


Figure 3.29—SWCHD412 Daily Interchange Report—Institution Level Trans (4 of 4)—Net Inter. Sum. 6 1 0 4 / 1 0 / 9 0 : : F E O G A K P R O W

T H R Y C O R T P A I E M W R M S U E S T G I N E B A G E H N D C A R H D E C R T R A N E C I T R N E Y I T L S I T A A E M D N

9 9 9 9 9 9 : R E B M U N N I B

K N A B Y T I C R A T L R S L O E O S T D S E 6 9 . C 8 9 S O 8 9 . R 8 9 U P 8 9 0 0 0 0 T 0 0 0 S 0 0 0 0 E 0 0 4 0 T 9 0 8 0 : : : : : 2 1 4 D H C W S

3-46


- T - E - N - T - I - D - E - R - C S T N U O M A - T - I - B - E - D - L - L - I - B - N - O - N - L - A - I - C - N - A - N - I - F - N - O S - N T N - D U - E O - S C - A - B - % - L - A - I - C - N - A - N - I - F Y R A M M U S R E R I U Q C A -

R C 5 0 7 0 . . 9 0 1 3

5 0 7 0 . . 9 0 1 3

0 0 0 0 . . 0 0

0 0

4 0 9

0 0

1 0 4 2



- R - C - 5 - 7 - . - 9 - 1 - 3 - 5 - 7 - . - 9 - 1 - 3 - 0 - 0 - . - 0 - 0 - 4 - 9 - 0 - 1 - 4 - 2 - L - A - T - O - T


B D 5 7 . 9 5 1

R C 2 1 . 3

0 2 0 1 . . 0 3

5 0 7 0 . . 9 0 5 1

0 0

4 3 3 1

0 7

1 0 0 1



October 2006

- B - D - 3 - 6 - . - 6 - 5 - 1 - 2 - 1 - . - 3 - 5 - 7 - . - 9 - 5 - 1 - 0 - 7 - 3 - 1 - 7 - 1 - 0 - 1 - L - A - T - O - T

•

R C 2 1 . 3 6 1



Oct 2006


Monthly Control Report—SWCHM363 Purpose:

The MDS generates this report to validate the processor’s monthly net settlement position to the processor’s settlement account.

Description:

This report is a month-end version of the Daily Control Report—SWCHD363. This report provides summary detail by transaction type within product type and includes the following transaction information: •

financial quantity for approved and denied

•

financial amount of transaction and fees, and

•

reversal quantity and net amount of transactions and fees.

The MDS provides totals derived from the Batch Data File settlement messages for acquiring and issuing processors. The Net Settlement Summary page lists the net settlement of transactions, reversals, and fees separated by debit, credit, and net for both the acquirer and the issuer. It also provides a final combined net settlement disposition for the Automated Clearing House System (ACH) and the Global Clearing Management System (GCMS). This report is based upon activity. Therefore, if a transaction type has “0” activity, it is not reported. Frequency: Availability:



Note

Monthly Available through Global File Transfer and eService on MasterCard OnLine.

For a sample of this report, refer to the Daily Control Report —SWCHD363 subsection.


•

October 2006

3-47

Oct 2006


Monthly Interchange Report—SWCHM412 Purpose:


Description:

This report is a month-end version of the Daily Interchange Report—SWCHD412. The MDS divides the Monthly Interchange Report into three sections. •

fee description by category

•

transaction volume by category, and

•

total dollar amounts by category.

Oct 2006

The fee description by category reflects the supported feesharing indices of the Customer and Technology. The report shows all transaction counts, separated by Financial and Non-financial, Billable and Non-billable categories. The actual dollar amount of fees are applied to interchange by product and then totaled in the “Total Net” column. The MDS segregates this report according to acquiring and issuing processor. The Daily Control Report—SWCHD363 lists the net total of fees in the field entitled “total fees settlement.” This report is activity driven. If a transaction type has “0” activity, it is not shown. Frequency: Availability:



3-48

Note

Monthly Available through Global File Transfer and eService on MasterCard OnLine

For a sample of this report, refer to the Daily Interchange Report—SWCHD412 subsection.

October 2006

•


Oct 2006


Debit MasterCard Inbound/Outbound Fee Report— SWCHD586-A



Note

For more information, refer to the IPM Clearing Formats manual.

Purpose:

Debit MasterCard processors can use this report to track and monitor miscellaneous inbound and outbound fees incurred through the submission of various fee collection messages.

Description:

Members must settle all miscellaneous fees and charges by use of the IPM Retrieval and Fee Collection/1740 message. The fee collection message contains the information required for members to process the miscellaneous fees and charges identified and is used for a number of diverse applications. The MDS generates this report to provide a summary detail of Retrieval and Fee Collection messages received on the GCMS Debit MasterCard inbound and outbound IPM format file. This report includes various fee collection types with the following Message Type Identifiers and Function Codes: •

•

•

•

Retrieval Request Fees (1644 MTI-603 FNC) Record Clearing Fees–member-and system-generated (1740 MTI- 700/783 FNC) Handling Fees–member-generated (1740 MTI -700, 780-782 FNC) Interchange Compliance Fees–system-generated (1740 MTI -783 FNC)

The MDS also will provide a Net Fees Report Summary page per processor, which lists the combined fee amounts incurred inbound and outbound with a Net total of the inbound and outbound fee amounts. This report is by ICA number within processor number order. This report is based upon activity. Therefore, if a fee collection type has no activity, it will not be reported.


•

October 2006

3-49


Daily

Frequency:

Available through Global File Transfer and eService on MasterCard OnLine.

Availability:



Note

There is a month-to-date version of this report (Debit MasterCard Miscellaneous Billing Report—SWCHM501).

Refer to Table 3.7 for a description of the SWCHD586-A report fields. Table 3.7—SWCHD586-A Fields Field

Description

Header Field—Displays at the top of all pages of the report

PROCESSOR

The MDS assigned processor/member identification number and the processor name.

Column Headings—Display across the page, just below the Header fields

MTI

The Message Type Identifier (MTI) identifies the general classification of a standard ISO message type being interchanged. For retrieval and fee collection messages: 1644 Retrieval Request Message–sent to acquirer by issuer 1740 Retrieval Fee Billing Message–submitted by acquirer Together with Function Code (IPM DE 24) in t he next column, these identifiers uniquely identify all transaction functions the clearing system performs.

FNC

Function Code, indicates a message’s specific purpose. The following retrieval and fee collection messages, from IPM DE 24, are included in this report. •

603 Retrieval Request

•

700 Fee Collection (member-generated)

•

780 Fee Collection Return

•

781 Fee Collection Resubmission

•

782 Fee Collection Arbitration Return

•

783 Fee Collection (clearing system-generated)

Together with the MTI, these data elements uniquely identify all transaction unctions the clearing system performs.

ACQUIRING ICA

3-50

The Interbank Card Association (member ID/ICA) number assigned by MasterCard to identify a member that maintains the merchant relationship and acquires the data relating to a transaction.

October 2006

•


Oct 2006


Field

Description

ISSUING ICA

The Interbank Card Association (member ID/ICA) number assigned by MasterCard to identify a member or processing endpoint of the card issuing processor or institution.

PAN

Primary Account Number. This is the cardholder number used to identify the account being accessed during the transaction.

USAGE CODE

Indicates the funds movement direction of a Fee Collection transaction on a customer account. Valid values are: 19 credit to transaction originator 29 debit to transaction originator

REASON CODE

Provides the message receiver with the reason that the message was sent. For detailed reason code (DE 25) information, refer to the IPM Clearing Formats manual.

FEE AMOUNT

Represents all fee amounts associated with a transaction type, in USD currency

REVERSAL INDICATOR

Originator must provide if this message is a single item reversal within a normal clearing file. Valid values are: R if message is a reversal of a previous message with no R. Space

MESSAGE TEXT

if message is a reversal of a previous message with an R.

Message Text enables the member to provide additional data applicable to a specific transaction type. This information displays beneath the related information in the above columns.

Total Field—Displays in the center at the bottom of the page

TOTAL


Net amount of all retrieval and fee collection charges incurred.

•

October 2006

3-51

Oct 2006


Figure 3.32—SWCHD586-A Net Fees Report (3 of 3) 5 7 0 / 9 1 / 3 0 E G F A O P K R O W

L L A H E C L T T C I R Y 0 W O 4 C 8 S P Y E T D C R I R N B A S E E C E R D R E R E F U D T C R T S A E A C N M R E T T I S B A E M D

3 2 : 0 3 : 5 0 5 0 / 0 1 2 . / 4 3 0 0 S M : C E G M I A T 6 D E 8 6 T 5 9 A D 2 D H 3 C S N W M U S S R

3-54

R E B M E M T S E T 5 2 1 2 1 0 0 0 0 9 : R O S S E C O R P

S L A T O T T E N

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

R C 7 0 9 0 . . 5 0 2 5 1 2 , 1

7 9 . 5 7 8

5 5 2 2 1 1 2 2 1 1 0 0 0 0 0 0 0 0 9 9

5 2 1 2 1 0 0 0 0 9

D D N N U U O O B B T N U I O L L A A T T O O T T

L A T O T T E N

October 2006

•


Reports Detail Activity Reports

Detail Activity Reports Detail activity reports list the details of all financial and non-financial transaction activity, regardless of the settlement day completion status that occurred on the settlement day. The MDS provides these reports to assist processors in research, tracking capabilities and transaction analysis. Table 3.8 Lists the MDS Detail Activity reports name, and purpose by report number. Table 3.8—MDS Detail Activity Reports Number

Name

Purpose

SWCHD53

Exception Audit Report

Processors use this reports to ensure the MDS has processed all exception items and to track incoming and outgoing exception items for the processor. Processors should use the report to initiate the research for representments and to monitor for excessive chargebacks that could be subject to sanction.

SWCHD55

Detailed Suspect Items Report

Processors use this enriched report to determine why a transaction failed. This report can assist in the reconciliation process by identifying the differences between the processor’s internal reports and the MDS reports.

SWCHD57/ SWCHD108

Transaction Audit Reports


•

These reports are obsolete but can be requested until April 2007.

October 2006

With MDS Release 06.3, MasterCard will no longer send the Transaction Audit Reports—SWCHD57 and SWCHD108 to members. These reports are obsolete and will not be updated or modified in future releases. Members may use the 250-byte Batch Data File as an alternate reference to locate information that was previously found in the Transaction Audit Reports. To allow more time to convert to the 250-byte Batch Data File format, members may request to continue to receive uninterrupted delivery of these reports through 3 April 2007.

3-55

Oct 2006


Number

Name

Purpose

SWCHD118

Retrieval Request/ Fulfillment Report

Debit MasterCard processors can use this report to track and monitor retrievals, and to ensure that acquirers have processed and fulfilled retrievals.

SWCHD141-1

Account File Updates

This report gives MDS connected issuer processors the ability to review modifications made to card adjustment files for card numbers residing on the Banknet Stand-In Account file.

SWCHD141-2

Account Management File Updates

This report gives MDS-connected issuer processors the ability to review modifications made to card adjustment files for card numbers residing in the MDS Banknet AMS (Account Management System) repository.

SWCHD141-3

Recurring Payment Cancellation Service

This report gives MDS-connected issuer processors the ability to identify and review all additions and changes to Recurring Payment Cancellation Service records.

SWCHD144

Maestro POS Transaction Audit Report

For issuers, the report sequence provides tracking capabilities and session reporting analysis. For acquirers, the report sequence enables processors with multiple corresponding members to review transactions by Institution and Term ID.

SWCHD147-1

Negative File Updates

This report gives members the ability to track changes made to the MDS Stand-In Negative Card file.

SWCHD147-2

VIP File Updates

SWCHD149

3-56

Stand-In Transaction Audit Report

This report gives members the ability to track changes made to the MDS Stand-In VIP file. For issuers, the report provides tracking capabilities for all transactions that the MDS routed to Debit Stand-In during periods the processor was unavailable

October 2006

•


Oct 2006


Captured Card Report—SWCHD51–Removed



Note

Report SWCHD51–Captured Card Report is obsolete and has been removed from this manual.


•

October 2006

3-57


Exception Audit Report—SWCHD53 Purpose:

Processors use this report to ensure the MDS has processed all exception items and to track incoming and outgoing exception items for the processor. Processors should use the report to initiate the research for representments and to monitor for excessive chargebacks that could be subject to sanction.

Description:

This report details all exception items including same day Reversal (auto-reversal) Adjustments, Chargebacks, and Representments. The report contains summary totals (by product, for all the exception items). Exception items are included in the processor’s net daily settlement and in the Daily Control Report—SWCHD363. Exception items do not appear on the Transaction Audit Report. The MDS sequences the transactions in reversal code order and segregates the report by acquiring and issuing processor. Interchange type 2 appearing in the PROD TYPE field identifies the ISIS transactions. STND appearing in the RESP CODE field identifies the Stand-in

transactions. Refer to Table 3.9 for a description of the SWCHD53 report fields. Frequency: Availability:

Oct 2006

Daily Available through Global File Transfer. Oct 2006

3-58

October 2006

•




ISO DE Description

Header Fields—Display at the top of all pages of the report.

PROCESSOR

N/A

The processor name.

PROCESOR ID

N/A


Body Fields—Display in the body of the report. These fields repeat for each exception item.

PAN

2

Primary Account Number. This is the cardholder number used to identify the account accessed during the transaction.

PROD TYPE

63

This field identifies the product accessed and the related interchange rate. Valid product type codes are: MC MasterCard

Oct 2006

CI Cirrus® MS Maestro® MD Debit MasterCard® MX Mondex™ chip card PL PLUS VI Visa

Valid interchange rate codes are: 0 U.S. and Canada Regions 1 Asia Pacific, Europe, Latin America and Middle East/Africa Regions 2 Intracountry (ISIS) format Only products with activity display on the report. MESS TYPE

NA

The identifier of the financial message type

CURR DATE

13

The calendar date the exception item occurred on the MDS. Format: MM-DD

CURR TIME

12

The start and end time for the exception item to complete on the MDS system. Format: HHMMSS

CURRENCY

49

The ISO-assigned currency code. Indicates the local currency used at the terminal.

ADV REASON

60

Advice Reason Code. Indicates the specific purpose of an advice message.

SWCH DATE

7

The date the transaction was processed on the MDS system Format: MM-DD

SWCH TIME

7

The start and end time for the transaction to complete. Format: HHMMSS

ORG SWCH SER

NA


•

Oct 2006

Oct 2006

The unique MDS assigned number for each transaction the system processes.

October 2006

3-59


Field

ISO DE Description

SWCH SERIAL

63

The unique MDS-assigned number identifying this adjustment.

STLMT DATE

15

System settlement date of the exception item

PROC CODE

3

The Processing Code describes the effect of a transaction on a cardholder account, and the account type affected for the original transaction.

CONV RATE-A

NA

Currency Conversion rate used to convert local currency to settlement currency where applicable. The MDS does not provide this information for balance inquiry transactions.

TRACE NO.

11

The message initiator assigns a unique Trace Number to identify a transaction. This represents the trace number of the original transaction.

ORG DATE

90

The date on which the transaction originally occurred on the MDS system.

ORG TIME

90

The time at which the transaction originally occurred on the MDS system. Format: HHMMSS

ORG AMT

90

The amount settled in the original transaction. For the acquirer this amount displays in the designated acquirer processor settlement currency, and for the issuer, the amount displays in the designated issuer processor settlement currency.

REFERENCE NO

37

Identifies the serial number printed on the customer receipt.

ACQ REC DATE

NA

The original settlement date.

ACQ INST NAME

NA

The name of the bank/processor, including ATM and POS terminals, acquiring the transaction.

NEW AMT

95

The amount to affect the exception item. This amount displays to the acquirer in the acquirer processor’s designated settlement currency, and to the issuer in the issuer processor’s designated settlement currency.

RESP CODE-A

NA

The response code of the original transaction. Refer to the NICS Users’ Guide for a response code listing.

TERMINAL ID

41

The unique ID assigned by the acquirer to each terminal.

NA

The physical location of the ATM or POS terminal.

REV DR AMT

NA

The amount reversed in the original transaction that results in a debit to the cardholder, reporting in the issuer processor’s designated settlement currency to the issuer, and in the acquirer processor’s designated settlement currency to the acquirer.

RESP CODE - I

NA

The response code of the exception item.

ISS INST ID

NA

The issuing processor’s Routing and Transit Number (also known as the ABA Number). This number identifies the card processor to the MDS.

ACQ LOC

3-60

October 2006

•


Oct 2006


Field

ISO DE Description

ACQ INST ID

32

The acquirer processor’s Routing and Transit Number (also known as the ABA Number). This number identifies the acquirer to the MDS. It can identify either an ATM or POS processor.

REV CR AMT

NA

The amount reversed in the original transaction that results in a credit to the cardholder, displaying in the issuer processor’s designated settlement currency to the issuer, and in the acquirer processor’s designated settlement currency to the acquirer.

60

The original Advice Reason Code indicating the specific purpose of an advice message received for a transaction that did not complete as authorized.

ISS PROC ID

NA

The MDS assigned processor number of the issuer involved in the transaction.

ACQ PROC ID

33

The MDS assigned processor number of the acquirer involved in the transaction.

NA

The new settlement amount after the adjustment. The settlement amount will report to the acquirer in the acquirer processor ‘s settlement currency, and to the issuer in the issuer processor’s settlement currency.

60


ORG ISS ID

NA

The cardholder processor number contained in the original transaction.

ORG ACQ ID

33

The acquirer processor number contained in the original transaction.

STLMT CURRENCY

NA

The currency of the amount being settled to the acquirer or issuer processor. The currency associate with the STLMT AMT.

ADV REASON-A

STLMT AMT

ADV REASON-1

USAGE CODE a

Identifies the current cycle of the chargeback. Valid values are: 1 First Chargeback 2 Second Presentment 3 Arbitration Chargeback 6 Retrieval Request 7 Fulfillment

DOC IND a

Specific requirements based on the cycle of the chargeback determines the need for a member to provide supporting documentation. Valid values are: Blank No documentation will follow 1 Documentation will follow

REJ CODE a



•

October 2006

3-61


Field

ISO DE Description

COND CODE a

The condition code denotes how the acquirer originally processed the transaction. Valid values are: 00 Online authorization, no PIN, PAN entry unknown 13 Online authorization, no PIN, PAN entry via magnetic stripe 18 Online authorization, no PIN, PAN entry via hand key

ADDITIONAL DATA a

Used by the operator processing the adjustment to provide the receiving member with specific information about the transaction. Can be the contact name and number.

MERCH CODE a EXCEPTION ITEM TYPE

The Merchant Code is a classification code used to identify the type of merchant. NA

TOTAL PRODUCT

Total of all exception item types within a specific product type. NA

TOTAL CASH BACK

a

Identifies the type of exception item processed.

Product under which original transaction occurred. Represents the total of all product types within a specific exception item type.

54

The Cash Back amount information on a purchase transaction. Cash back may be expressed in both local and designated acquirer or issuer settlement currency. This field displays only under certain conditions. If a transaction has an Amount Type of 40 (in ISO DE 54), this field displays. If there is no Cash Back activity, this field does not display.

The product type determines if this field is present on the report.

3-62

October 2006

•



Figure 3.34—SWCHD53 Exception Audit Report (2 of 4)—Acquiring Processor 6 2 0 / 0 1 / 3 0 F E O G A K P R O W

H T C R T O I R P W O E S S R S T E T I C I B O D E R U D P A D G N R N O A I I C R T R I P E U E T Q C S C X A A E M

R O S S E 2 C 1 O 1 R 0 P 0 0 T 0 S 0 E 0 T 9 : : D I R R O O S S S S E E C C O O R R P P 3 5 D H C W S

3-64

D 1 0 3 0 0 0 0 0 6 0 0 S 4 0 0 0 0 0 0 3 4 0 M 8 0 0 . . . . . 8 . 0 0 0 0 0 9 0 0 0 0 0 0 9 0 0 0 2 1 1 1 2 1 0 1 4

L 1 4 5 A T O T

0 0 0 T Y N S C K E L R N C M A E E A T S S T T R B N R E E M M T R E E Y H T A A M U H S V P A C S E E Y C C A T T T N W R M M R R A R R E S A A D C T T C P D R V M M E O R G N G W V V L L G R R U R O R E E E T T R P C O C O N R R S S O

H S E I N M 0 0 I 0 0 H 0 0 D 0 0 2 2 2 0 0 - 0 1 1 0 0 2 1 1 K 1 0 0 6 6 0 5 N 1 0 0 5 5 0 2 A 2 0 0 8 8 0 1 B Y 1 0 0 0 0 1 5 O 1 0 0 0 0 0 7 S R 0 0 0 0 0 0 0 U T 1 9 9 E M A D D N I I D E E E I M M D E T T C I I O M S C S O Q T T C I N O N R C T I L I P A R H C R C O G Q Q Q Q G U W R R C C C C R C S P O A A A A O 6 3 3 0 1 1 3 1 1 1 0 0 1 0 0 0 0 0 2 2 0 3 0 0 1 1 1 0 0 1 1 0 0 - - - - - J 1 0 0 3 3 3 3 3 D 0 0 0 0 0 0 0 0 A 1 9 9 E T D D D D E A I I I I E E T D T T A E L T C A A D T C A S O S D D A E N N R S T D R I I P I R H M M R C L G Q R S S G U W T R C E S S R C S S O A T I I O 5 0 0 0 0 0 0 0 0 0 0 2 0 0 0 2 6 5 0 0 1 0 1 3 1 0 0 0 3 0 6 0 0 0 3 9 0 5 0 3 0 8 4 2 0 1 0 0 8 8 9 0 0 1 4 9 0 1 0 0 9 3 0 4 4 0 0 4 1 0 1 0 A I 0 O - 0 L N A I 0 N A - - N N E O I E E E O O P S R O C D D S S Y A E N N O O A A T E S E C C E E R E R R R S H C E P P N S V C A F S S V V A E D W R E E E D D P M A S T R R R A A

S 0 0 0 T N E M T N E S E R P E R

S 0 0 0 K C A B E G R A H C

S 1 4 5 T N E M T S U J D A

S 0 0 0 L A S R E V E R O T U A

O S R U T L R S A R E T I A O C M T

October 2006

•



Figure 3.36—SWCHD53 Exception Audit Report (4 of 4)—Issuing Processor 6 2 0 / 0 1 / 3 0 F E O G A K P R O W

H T C R T O R I P O W E S S R S E T T C I I O B D R E U P D A D N R G O A N I C I T R U P E S E T S C S I X A E M

, ,

3 5 D H C W S

3-66

R O S S E 3 C 1 O 1 R 0 P 0 0 T 0 S 0 E 0 T 9 : : D I R R O O S S S S E E C C O O R R P P

1 0 3 0 0 0 S 4 0 0 0 0 M 8 0 0 . . 0 0 0 0 0 0 0 0 0 0 2 1 2 1 0 1 4

R E S E E P Y H T Y C C A T T T N W R M M E S A A D R V O R G N G W R U R O R E P C O C O N

H S E N 6 7 I 5 5 H 8 8 D 0 0 0 0 0 0 K 6 6 0 5 N 5 5 0 2 A 8 8 0 1 B 0 0 1 5 0 0 0 7 S 0 0 0 0 U E M A N E E E M M D E T I I O M S T T C I N T I R H C R C O G Q U W R R C C S P O A

0 0 0 2 2 1 1 1 0 0 - - - - 3 3 3 3 3 0 0 0 0 0 E T E A E E T D T T A E A A D T C D D A E T D R R H M R C L G Q U W T R C C S S O A 5 0 0 0 0 4 0 0 2 6 0 1 0 1 0 0 0 3 0 0 0 3 9 0 0 0 8 4 2 3 2 0 8 8 9 1 4 9 0 1 0 1 0 4 4 0 0 3 1 1 O 0 L N 0 N A 0 E O I E P S R O C Y A E N N T E S E R E R S H C E S V C A F N E D W R E A M A S T R P

October 2006

•



Detailed Suspect Items Report—SWCHD55 Purpose:

Processors should use this enriched report to determine why a transaction failed. This report can assist in the reconciliation process by identifying the differences between the processor’s internal reports and the MDS reports.

Description:

This report is used to research transactions that did not complete as requested, because of a denial by the processor or the MDS, or a reversal by a processor as indicated by the completion code. These transactions are included in the Transaction Audit Report. One of the following scenarios determines the failure of the transaction: •

•

When transactions report to the Transaction Audit Report with response codes of “00” (approved) but did not complete as authorized as indicated by the Advice reason code. When transactions report to the Transaction Audit Report with a denial response code indicating authorization has been denied.

Not all response code scenarios report to the SWCHD55. Response codes with an Online Status of “S” (switch denied), do not report to the SWCHD55. Both can be used to investigate the date and time sequence of ATM and POS transactions. The MDS sequences the suspect transactions in response code, current date, and switch date order. The time stamp shown on the report can assist the processor in determining at which step the transaction failed. Interchange type 2 appearing in the PROD TYPE field identifies the ISIS transactions. Frequency: Availability:


Acquiring Processor and Cardholder Processor Refer to Table 3.10 for a description of the SWCHD55 report fields.


•

October 2006

3-67

Oct 2006



ISO DE Description

Header Fields—Display at top of all pages of the report.

PROCESSOR

The processor name.

PROCESSOR ID


Body Fields—Display in the body of the report. These fields repeat for each transaction.

PAN

2


PROD TYPE

63

This field identifies the product accessed and the related interchange rate. Valid product type codes are: MC MasterCard CI Cirrus® MS Maestro® MD Debit MasterCard® MX Mondex™ chip card PL PLUS VI Visa

Valid interchange rate codes are: 0 U.S. and Canada Regions 1 Asia Pacific, Europe, Latin America and Middle East/Africa Regions 2 Intracountry (ISIS) format Only products with activity display on the report. MESS TYPE

mx

CURR DATE

7

The calendar date on which the transaction occurred on the MDS system Format: MM-DD

CURR TIME

7

The start and end time for the transaction item to complete on the MDS system. Format: HHMMSS

CURRENCY

49

The ISO-assigned currency code. It indicates the local currency used at the terminal.

SWCH SERIAL

63

The unique MDS-assigned number for each transaction that the system processes.

SWCH DATE

7

The date the transaction was processed on the MDS system Format: MM-DD

SWCH TIME

7


3-68


October 2006

•


Oct 2006


Field

ISO DE Description

CONV RATE - A

9


TRACE NO

11

The message initiator assigns a unique Trace Number to identify a transaction.

7

The original settlement date Format: MM-DD

PROC CODE

3

The Processing Code describes the effect of a transaction on a cardholder account and the account type affected.

REFERENCE NO

37

The serial number printed on the customer receipt.

STLMT DATE

7

The date the transaction was processed on the MDS system.

ACQ INST NAME

43

The name of the bank/processor, including ATM and POS terminals, acquiring the transaction.

INTERCHG AMT

29

The Interchange Fee is the transferred fee between acquiring and card processor in the currency of the acquirer settlement currency for the acquirer, and the issuer settlement currency for the issuer.

ACQ REC DATE


•

October 2006

3-69


Field

RESP CODE

ISO DE Description

39

The Response Code defines the disposition of a message. Possible response codes are listed below: 00 Approved or completed successfully 04 Capture card 12 Invalid transaction 13 Invalid amount 14 Invalid card number 15 Invalid issuer 30 Format error 41 Lost card 43 Stolen card 51 Insufficient funds/over credit limit 54 Expired card 55 Invalid PIN 57 Transaction not permitted to issuer/cardholder 61 Exceeds withdrawal amount limit 62 Restricted card 75 Allowable number of PIN tries exceeded 78 Invalid or nonexistent account specified (general) 79 Invalid business date 80 System not available 91 Destination processor (customer processor system) not available 92 Unable to route transaction

Oct 2006

96 System error

ADDITNL RESP

44

This displays additional supporting data pertaining to the response code associated with the transaction.

ACQ LOC

43

The physical location of the ATM or POS terminal

4

The completed amount of the transaction in local currency. Local currency is the currency of the acquirer. This amount does not include fees.

60

The Advice Reason Code indicates the specific purpose of an advice message sent by the issuer.

ISS INST ID

mx

The issuing processor’s Routing and Transit (ABA Number). This number identifies the issuing processor to the MDS.

ACQ INST ID

32

The acquirer processor’s Routing and Transit Number; this is also known as the ABA Number. This number identifies the acquirer to the MDS. It can identify either an ATM or POS processor.

COMP AMT LOCAL ADV REASON-A

3-70

October 2006

•



Field

COMP AMT

ISO DE Description

5

Completed amount in the designated acquirer settlement currency for the acquirer, and the designated issuer settlement currency for the issuer. The amount of funds to be transferred between the acquiring and cardholder processor.

60

The Advice Reason Code indicates the specific purpose of an advice message sent by the acquirer.

ISS PROC ID

mx

The MDS-assigned processor number of the issuer involved in the transaction

ACQ PROC ID

33

The MDS-assigned processor number of the acquirer involved in the transaction

STLMT AMT

mx

The amount settled to the acquirer or issuer processor. This field may contain a settlement value in addition to interchange fees.

POS ENTRY

22

The Point of Service entry mode indicates the method used to enter the PAN into the terminal device and the PIN entry capability of that device.

TERMINAL ID

41


POS DATA

61

The Point of Service (POS) data codes identify specific conditions present at the point of service at the time a transaction takes place:

ADV REASON-I

•

Customer presence indicator

•

Card presence indicator

•

Card retention indicator

•

Transaction status indicator

•

Transaction security indicator

•

Transaction routing indicator

•

Cardholder-activated terminal level indicator

•

Card data terminal input capability indicator

•

STLMT CURRENCY

mx


•

Authorization life cycle indicator

•

Country code indicator

•

Postal code indicator

The currency of the amount being settled to the acquirer or issuer processor. The currency associated with STLMT AMT.

October 2006

3-71


Transaction Audit Reports—SWCHD57 and SWCHD108



Note

With MDS Release 06.3, MasterCard will no longer send the Transaction Audit Reports—SWCHD57 and SWCHD108 to members. These reports are obsolete and will not be updated or modified in future releases. Members may use the 250-byte Batch Data File as an alternate reference to locate information that was previously found in the Transaction Audit Reports—SWCHD57 and SWCHD108. To allow more time to convert to the 250-byte Batch Data File format, members may request to continue to receive uninterrupted delivery of these reports through 3 April 2007.

Purpose:

For issuers, the report sequence provides tracking capabilities and session (multiple transaction by account number) reporting analysis. For acquirers, the report sequence allows processors to review transactions by institution and Terminal ID. (This may be helpful for marketing analysis.)

Description:

This report details all the financial and non-financial transactions, regardless of completion status, that occurred on the settlement day. The report is an audit listing of the data elements contained in transaction messages. Processors choosing not to receive this report will find the same information in the auto-reconciliation file. The SWCHD57 reports two lines of transaction information detail, and the SWCHD108 reports one line of transaction information detail. Interchange type 2 appearing in the PROD TYPE field identifies the ISIS transactions.

Frequency: Availability:



Note

Daily Available through Global File Transfer.

There are two versions of the Transaction Audit Report, the SWCHD57 two-line format, and the SWCHD108 one-line format.

Refer to Table 3.11—SWCHD57 Fields for a description of the SWCHD57 report fields.

3-74

October 2006

•


Oct 2006



ISO DE Description


PROCESSOR

The processor name.

PROCESSOR ID



REC DATE

7

The date the transaction was processed on the MDS system

SWCH TIME

7

The time the transaction was processed on the MDS system

SWCH SERIAL NUMBER

63

The unique number assigned by the MDS to each transaction that the system processes.

42

The name of the bank/processor acquiring the transaction. This includes both ATM and POS terminals.

PROC CODE

3

Describes the effect of a transaction on a cardholder account and the account type affected

TRACE NO.

11


REF NO.

37


43


PAN

2


TERM ID

41


ADV REASON

60

The Advice Reason Code indicates the specific purpose of an advice message.

CASH BACK

54

The Cash Back amount information on a purchase transaction

28

U.S. only acquirers may apply an additional fee or a surcharge to an ATM transaction. The acquirer must clearly present the surcharge amount to the cardholder before completing the transaction. The surcharge is reported in the Issuer settlement currency on the Issuer report, and in the Acquirer settlement currency on the Acquirer report. The “C” or “D” indicates a Credit or Debit surcharge amount.

PRO

33

The MDS-assigned processor number of the issuer and acquirer involved in the transaction.

ISS INST

MX

The card processor’s Routing and Transit Number (also known as the ABA Number). This number identifies the card processor to the MDS.

ACQ INST

32

The acquirer processor’s Routing and Transit Number (also known as the ABA Number). This number identifies the acquirer to the MDS. It can identify either an ATM or POS processor.

ACQ NAME

ACQ LOCATION

ACC CHG


•

October 2006

3-75


Field

PROD

ISO DE Description

63


Valid interchange rate codes are: 0 U.S. and Canada Regions Asia Pacific, Europe, Latin America and Middle East/Africa Regions 2 Intracountry (ISIS) format Only products with activity display on the report. 1

CC

49

The ISO-assigned currency code. It indicates the local currency used at the terminal.

CONV RATE ISSI

9

Currency conversion rate used to convert local currency to issuer processor settlement currency where applicable. The MDS does not provide this information for balance inquiry transactions.

CONV RATE ACQ

9

Currency conversion used to convert local currency to acquirer processor settlement currency where applicable. The MDS does not provide this information for balance inquiry transactions.

CP LOC

4


SETT

5

The settlement amount of the transaction in the settlement currency of the Issuer for the Issuer report, and the Acquirer for the Acquirer report. This amount includes fees. “C” or “D” indicates a credit or debit to the processor indicated in the report title (such as cardholder or acquiring processor).

SETL CURR

49


COMP

MX

Completed amount in the settlement currency. On the Issuer report it is the completed amount in Issuer settlement currency, and on the Acquirer report it is the Acquirer settlement currency. The amount of funds to be transferred between the acquiring and cardholder processor.

INT

29

The Interchange Fee transferred between the acquirer and card processor displayed in the currency of the settlement amount where applicable. “C” or “D” indicates Credit or Debit fee.

RESP CD

39

The Response Code defines the disposition of a message.

3-76

October 2006

•


Oct 2006


Acquiring Processor and Cardholder Processor Sort sequences are as follows: •

For acquiring processors: Acquiring Routing/Transit Number

−

•

−

Terminal ID

−

Date

−

Time

For cardholder processors: −

PAN

−

Date

−

Time order

Refer to Table 3.12 for a description of the SWCHD108 report fields. Table 3.12—SWCHD108 Fields Field

ISO DE Description Oct 2006


PROCESSOR

The processor name.

PROCESSOR ID



ACQ INST

32


TERM ID

41


ISS PRO/ACQ PRO

33

The MDS assigned processor number of the issuer or acquirer involved in the transaction.

DATE/TIME

7

The date and time the transaction occurred on the MDS system.

PAN

2


PROC CD

3

The Processing Code describes the effect of a transaction on a cardholder account and the account affected.

TRACE

11



•

October 2006

3-79


Field

RESP CODE

ISO DE Description

39


60

The Advice Reason Code defines the specific purpose of an advice message.

CMP AMT SETTLEMENT

5

The completed amount in the settlement currency. On the Issuer report it is the Issuer settlement currency, and on the Acquirer report, it is the Acquirer settlement currency. The amount of funds transferred between the acquiring and cardholder processor. This amount does not include fees.

SETTLEMENT CC

49

The ISO assigned currency code. It indicates the settlement currency of the issuer in the issuer report, and the acquirer in the acquirer report.

CMP AMT LOCAL

4


PROD CODE

63

This field identifies the product accessed and the related interchange rate. Valid product type codes are:

ADVICE REASON

MC MasterCard CI Cirrus® MS Maestro® MD Debit MasterCard® MX Mondex™ chip card PL PLUS VI Visa

Valid interchange rate codes are: 0 U.S. and Canada Regions 1 Asia Pacific, Europe, Latin America and Middle East/Africa Regions 2 Intracountry (ISIS) format Only products with activity display on the report. ACCESS CHARGE

INTER FEE

3-80

28

U.S. only acquirers may apply an additional fee or a surcharge to an ATM transaction. The acquirer must clearly present the surcharge amount to the cardholder before completing the transaction. The surcharge is reported in the Issuer settlement currency on the Issuer report, and in the Acquirer settlement currency on the Acquirer report. The “C” or “D” indicates a Credit or Debit surcharge amount.

29

The Interchange Fee is the transferred fee between acquiring and card processor in the settlement currency of the Issuer on the Issuer report, and in the settlement currency of the Acquirer on the Acquirer report. “C” or “D” indicates a Credit or Debit fee.

October 2006

•


Oct 2006


Retrieval Request/Fulfillment Report—SWCHD118 Purpose:

Debit MasterCard processors can use this report to track retrievals, to monitor retrievals, and to ensure that acquirers have processed and fulfilled retrievals.

Description:

This report details retrieval requests and fulfillments, and contains summary totals, by product, for all the items. The MDS sequences the transactions according to reversal code.



Cardholder Processor Refer to Table 3.13 for a description of the SWCHD118 report fields. Table 3.13—SWCHD118 Fields Field

ISO DE Description


PROCESSOR

The processor name.

PROCESSOR ID


Body Fields—Display in the body of the report. These fields repeat for each item.

PAN

2


Primary Account Number. This is the cardholder number used to identify the transaction’s assessed account.

•

October 2006

3-83


Field

PROD TYPE

ISO DE Description

63



MESS TYPE

NA


CURR DATE

13

The calendar date the exception item occurred on the MDS.

CURR TIME

12

The start and end time for the exception item to complete on the MDS system. Format: HHMMSS

CURRENCY

49

The ISO assigned currency code. It indicates the local currency used at the terminal.

ADV REASON

60

Advice Reason Code. Indicates the specific purpose of an advice message. The last two digits of the Advice Reason Code indicates the Reversal Reason Code.

SWCH DATE

7


SWCH TIME

7


ORG SWCH SER

NA

The unique number assigned by the MDS to each transaction processed in the system.

SWCH SERIAL

63

The unique number assigned by the MDS to identify this adjustment.

STLMT DATE

15

System settlement date of the exception item

PROC CODE

3

The Processing Code describes the effect of a transaction on a cardholder account, and the account type affected for the original transaction.

CONV RATE-A

3-84

NA


October 2006

•


Oct 2006


Field

ISO DE Description

TRACE NO.

11

The message initiator assigns a unique Trace Number to identify a transaction. This represents the trace no. of the original transaction.

ORG DATE

90

The date on which the transaction originally occurred on the MDS system

ORG TIME

90

The time at which the transaction originally occurred on the MDS system The format is HHMMSS

REFERENCE NO

37


ACQ REC DATE

NA

The original settlement date

ACQ INST NAME

NA


ORG AMT

90

The amount that was settled in the original transaction

RESP CODE-A

NA

The response code of the original transaction.

TERMINAL ID

41


ACQ LOC

NA


NEW AMT

95

The amount to affect the exception item. This will be the acquirer processor settlement currency for the acquirer, and the issuer processor settlement currency for the issuer.

RESP CODE - I

NA

The response code of the exception item

ISS INST ID

NA

The issuing processor’s Routing and Transit (ABA Number.) This number identifies the issuing processor to the MDS.

ACQ INST ID

32


REV DR AMT

NA

The amount reversed in the original transaction that results in a debit to the cardholder, reporting in the issuer processor’s settlement currency to the issuer, and in he acquirer processor’s settlement currency to the acquirer.

ORG ADV RSN-A

60


ISS PROC ID

NA

The MDS assigned processor number of the issuer involved in the transaction.

ACQ PROC ID

33

The MDS assigned processor number of the acquirer involved in the transaction.

NA

The new settlement amount after the adjustment. The settlement amount will report to the acquirer in the acquirer processor’s settlement currency, and to the issuer in the issuer processor’s settlement currency. The settlement amount includes the reimbursed portion of the interchange fee.

STLMT AMT


•

October 2006

3-85


Field

ISO DE Description

REV CR AMT

NA

The amount reversed in the original transaction that results in a credit to the cardholder, reporting in the issuer processor’s settlement currency to the issuer, and in the acquirer processor’s settlement currency to the acquirer.

ORG ADV RSN-I

60


ORG ISS ID

NA

The cardholder processor number contained in the original transaction

ORG ACQ ID

33

The acquirer processor number contained in the original transaction

STLMT CURRENCY

NA


USAGE CODE a

The usage code is used to identify the current cycle of the chargeback. 6 Retrieval Request 7

Fulfillment

DOC IND a

Specific requirements based on the cycle of the chargeback determines the need for a member to provide supporting documentation. Blank No documentation will follow 1 Documentation will follow

REJ CODE a


COND CODE a

The condition code denotes how the acquirer originally processed the transaction. 00 Online authorization, no PIN, PAN entry unknown 18 Online authorization, no PIN, PAN entry via magnetic stripe Online authorization, no PIN, PAN entry via hand key

ADDITIONAL DATA a

Used by the operator processing the adjustment to provide the receiving member with specific information about the transaction. Can be the contact name and number.

MERCH CODE a

The Merchant Code is a classification code used to identify the type of merchant.

Total Fields—Display across the bottom of the page for each item.

EXCEPTION ITEM TYPE RETRIEVAL REQUESTS FULLFILLMENTS TOTAL a

NA

Identifies the type of exception item processed. Retrieval Requests-Provides the number of retrieval requests for the Debit MasterCard and a grand total. Fulfillments-Provides the number of fulfilled retrieval requests for Debit MasterCard and a grand total. Provides the total amount number of retrieval requests and fulfillments for Debit MasterCard and a grand total amount

The product type determines if this field is present on the report.

3-86

October 2006

•



Figure 3.43—SWCHD118 Retrieval Request/Fulfillment Report (Page 1 of 2)—Acquiring Processor 5 1 0 / 3 2 / 3 0 F E O G A K P R O W

T R O P E R H T C N T E I R M W O L S S L S I T E F I C L B O U E R F D P / T D G S R N E A I U C R Q R I E E U R T Q S C L A A A M V E I 1 R R T O S E S E 1 R C 1 O 1 R 1 P 1 1 T 0 S 0 E 0 T 9 : : D I R R O O S S S S E E C C O O R R P P 8 1 1 D H C W S

D 0 0 1 0 0 0 0 0 0 0 0 D 4 4 0 0 0 0 0 0 4 9 M 8 6 0 . . . . . 8 0 3 0 0 0 9 3 0 0 0 0 0 0 0 0 0 5 1 , , 0 0 2 1 1 1 1 1 2 1 0 0 6 Y E C D R N O E E C S T T R E E E M M T R E D P Y H T A A M U D O Y C C A T T A C O C T N W R M M R R C E S A A D C T T H D R V M M D C O R G N G W V V L L N R R U R O R E E E T T O E P C O C O N R R S S C M

2 N O H I O 5 8 T 1 1 U 6 6 T 4 4 I 7 7 7 3 3 T 7 7 7 1 1 S N 7 7 7 N O 7 7 7 5 5 0 9 I T 7 7 7 1 1 0 2 L 7 7 7 6 6 0 9 T I 7 0 0 4 4 0 1 S M 7 0 0 3 3 0 9 E A 0 0 0 1 1 0 0 T H 1 9 9 E M A D D N I I D E E E I M M D E T T C E I I O M S C S O Q D T T C I N O N R C O T I L I P A C R H C R C O G Q Q Q Q G J U W R R C C C C R E C S P O A A A A O R 1 1 1 1 1 1 9 1 1 1 9 1 1 1 9 1 1 1 2 2 3 8 1 9 1 1 1 2 2 2 1 1 9 1 0 0 - - - - - 9 1 0 0 3 3 3 3 3 9 0 0 0 0 0 0 0 0 9 1 9 9 2 E T D D D E A I I I D E E T D I T T A E L T C A A D T C A S O S D D D A E N N R S N T D R I I P I I R H M M R C L G Q R S S G C U W T R C E S S R O C S S O A T I I O D 0 0 0 0 0 0 0 0 1 0 K 1 0 A 1 2 K D 1 1 1 3 A R 4 1 4 8 D 3 0 1 0 3 9 R A 0 1 0 9 9 3 0 1 0 9 9 A 1 7 1 2 7 8 9 0 0 8 1 4 8 2 9 4 A 1 0 4 4 9 0 0 6 T 1 0 3 A I A 1 O - - D 1 L N A I 1 N A - - N N E L 1 E O I E E E O O D A 0 P S R O C D D S S O N 0 Y A E N N O O A A C O 0 T E S E C C E E I R E R R R E T S H C E P P G I S V C A F S S V V A D E D W R E E E D D S D N M A S T R R R A A U A A P


•

L 1 1 A T O T

S 0 0 T N E M L L I F L U F

S 1 1 T S E U Q E R L A V E I R T E R T I B E D D R A C R E L T A S T A O M T

October 2006

3-87


Figure 3.44—SWCHD118 Retrieval Request/Fulfillment Report (Page 2 of 2)—Issuing Processor 5 2 0 / 3 2 / 3 0 F E O G A K P R O W

D 1 8 2 8 2 2 0 0 0 0 0 D 7 1 2 9 9 0 0 0 4 9 M 9 4 7 . . . . . 8 0 1 1 7 7 0 9 8 3 3 0 4 5 6 6 0 0 7 , , 0 2 2 0 2 2 1 1 4 1 8 0 5 Y E C D R N O E E C S T T R E E E M M T R E D P Y H T A A M U D O Y C C A T T A C O C T N W R M M R R C E S A A D C T T H D R V M M D C O R G N G W V V L L N R R U R O R E E E T T O E P C O C O N R R S S C M

T R O P E R H T C N T E I M W L S L R I O T F S I L S B U E E F C D / O T R D S P R E A U G C Q N R E I E R U T S S L S A A I M V E I R T E R

8 1 1 D H C W S

3-88

5 N O A I R 5 1 T F 4 5 U 0 0 T 0 0 I 5 7 7 2 2 T 5 7 7 1 1 S 5 7 7 N S 5 7 7 5 5 0 2 I I 5 7 7 4 4 0 0 R 5 7 7 0 0 0 7 T A 5 0 0 0 0 0 1 S P 5 0 0 2 2 0 6 E 5 0 0 0 1 1 0 0 T 7 1 9 9 E M A D D N I I D E E E I M M D E T T C E I I O M S C S O Q D T T C I N O N R C O T I L I P A C R H C R C O G Q Q Q Q G J U W R R C C C C R E C S P O A A A A O R 3 3 3 3 3 3 1 3 3 3 2 3 3 3 0 3 3 3 6 6 7 2 0 2 3 3 3 1 1 1 2 2 0 3 0 0 - - - - - 0 3 0 0 5 5 5 4 4 1 0 0 0 0 0 0 0 0 0 1 9 9 1

2 R O S S E 7 C 7 O 7 R 7 P 7 7 T 0 S 0 E 0 T 9 : : D I R R O O S S S S E E C C O O R R P P

E T D D D E A I I I D E E T D I T T A E L T C A A D T C A S O S D D D A E N N R S N T D R I I P I I R H M M R C L G Q R S S G C U W T R C E S S R O C S S O A T I I O D 0 0 0 0 0 0 0 0 2 0 3 2 0 0 2 7 3 9 2 2 2 2 0 5 4 2 4 7 9 7 0 2 0 7 9 5 3 0 2 0 7 9 7 0 2 0 2 9 3 1 7 2 0 7 8 9 0 0 8 2 4 8 2 9 4 A 2 0 4 4 9 0 6 T 2 0 A I A 2 O - - D 2 L N A I 2 N A - - N N E L 2 E O I E E E O O D A 0 P S R O C D D S S O N 0 Y A E N N O O A A C O 0 T E S E C C E E I R E R R R E T S H C E P P G I S V C A F S S V V A D E D W R E E E D D S D N M A S T R R R A A U A A P

L 2 2 A T O T

S 0 0 T N E M L L I F L U F

S 2 2 T S E U Q E R L A V E I R T E R T I B E D D R A C R E L T A S T A O M T

October 2006

•



Account File Updates—SWCHD141-1 Purpose:

This report gives MDS-connected issuer processors the ability to review modifications made to card adjustment files for card numbers residing on the Banknet Stand-In Account File.

Description:

This report provides an audit trail of Online File Update messages sent to the Banknet® telecommunications network by NICS™ or Online message sending methods. Card number records added, changed, or deleted by the MDS, appear daily in this report. The report logs record updates by Processor ID if multiple processors are owned, and then by PAN and Switch Date/Time values in ascending order.



Refer to Table 3.14 for a description of the SWCHD141-1 report fields. Table 3.14—SWCHD141-1 Fields Field

ISO DE Description


PROCESSOR

The processor name.

PROCESSOR ID


Column Headings—Display across the page, just below the Header fields.

PAN

2

The column lists the Primary Account Number associated with the card record that was updated.

TRACE NUMBER

11

Every file update request message is assigned a unique identification number called a Trace Number. This number provides a message trail between message initiators and the Banknet ® telecommunications network and MDS Stand-In processes.


•

October 2006

3-89


Field

TYPE OF UPDATE (ADDITIONAL RESPONSE DATA)

ISO DE Description

91

This column specifies the action that issuing processors took in regard to card number records residing in the Banknet Stand-In Account File and AMS repository. Valid update types include: MCC102 Add, Change, and Delete ADDITIONAL RESPONSE DATA If an error condition exists, ERROR, appears in this column. Error Codes 120001 •

The PAN received was not numeric.

•

The BIN in the PAN was not on file.

•

The BIN did not belong to the message initiator.

•

The check digit of the PAN was incorrect .

•

The PAN received was not on the account file.

120002 •

The Entry reason was not P, L, S, X, O, F, V, G, C, or U.

120005 •

The PIN length was not numeric or contained spaces.

120006 •

REASON CODE

120

The Entry Reason was “V”, but the VIP Transaction Amount was not numeric.

This column lists the reason why the card number was reported. Valid Reason Codes for MCC102 File Updates C Credit F

Fraud G Gold L Lost O Other P Capture Card S

Stolen U Unauthorized V VIP Status X Counterfeit MCI CUST ID

120

This column displays the Issuer ICA number that MasterCard assigned.

SWITCH DATE

7

This is the date that the update was made to the file (format: MM/DD/YY).

SWITCH TIME

7

This is the time of the day that the update was made to the file (format: HHMMSS).

VIP TRANS AMOUNT

3-90

120

This column displays the maximum monetary amount that can be authorized by MasterCard Stand-In processing in a four-day period. This amount is set in the MCC102 Banknet ® telecommunications network file.

October 2006

•



Field

ISO DE Description

CURRENCY CODE

120

An ISO currency code appears in this field and indicates the currency of the money reported in the VIP TRANS AMOUNT column. This currency is set in the MCC102 Banknet ® telecommunications network file.

RESP CODE

120

This column displays the issuer’s response code. Issuer Response Codes 00 Completed successfully 25 Unable to locate record on file 27 File update field edit error 30 Format error 40 Requested function not supported 80 Duplicate add, action not performed 96 System error

MESSAGE SOURCE

NA

There are two methods for updating the Banknet ® telecommunications network AMS and MDS Stand-In database files. The first method is to make card adjustments using the NICS ™ application (MASTERCARD DEBIT HOTCARD FACILITY). The second method allows issuing processors to bypass the NICS ™ application and send 0302 online messages directly to the Banknet ® telecommunications network through the MDS. Interface Values NICS™ A NICS ™ user performed the file update. ONLINE A processor sent the file update to the MDS or Banknet®

telecommunications network through a 0302 online message. GROUP NUMBER

NA

This column applies only to file updates with a “NICS ™” Message Source, and identifies the NICS ™ user group responsible for the file update.

USER NUMBER

NA

This column applies only to file updates with a “NICS ™” Message Source, and identifies the NICS ™ user who made the file update.


•

October 2006

3-91


Figure 3.45—SWCHD141-1 Banknet AMS, Account File Updates Report 5 1 0 / 5 2 / 4 0 F E O G A K P R O W

R - 9 9 E - 9 9 R B - 9 9 E M S U U N R - 9 9 P E - 9 9 U B - 9 9 O M - 9 9 R U G N E G E A C S R - S S S U - C C E O - I I M S - N N P E S D - 7 7 E O - 2 2 R C Y C N E E D R O R C U C T M N U E S O P M T E I A V S T S N Y A A R S D T S P T M U H - 3 4 I C E - 4 3 A T M - 6 5 B I I - 5 5 E W T - 2 2 E T S - 1 1 L D E - 5 5 I - 0 1 0 6 N H - / 0 / 0 D F C E - 5 0 5 0 K T T - 2 0 2 0 R I A - / 2 / 2 N W D - 4 1 4 1 A T S - 0 6 0 6 A - 0 0 C N B D - 2 : 2 : R U I - 0 A 0 A I - 2 T 2 T E O C T - 2 A 2 A M S - 0 D 0 D T C U - 0 0 C - E E S C - S S - N N A A - O O N - P P M O E - S S S D - E E A O - S R L R E C R - L L - A A - N N - O O F - * I * I O E - T T T - R I R I E A - O D O D P D - R D R D Y P - R A R A T U - E E - * * 1 R - 3 7 # E E - 1 0 5 C B - 0 0 K 9 A M - 4 4 N 9 R U - 6 6 A 9 T N - 3 3 B 9 0 T 0 S 0 E 0 - 5 6 T 9 - 1 1 - 0 0 : : - 4 4 D - 3 3 I - 4 4 1 - 3 3 R R - 2 2 1 O O - 1 1 4 S S - 2 2 1 S S - 1 1 D E E - 2 2 H C C - 1 1 C O O N - 1 1 W R R A - 4 4 S P P P - 5 5

3-92

October 2006

•



Account Management File Updates—SWCHD141-2 Purpose:

This report gives MDS-connected issuer processors the ability to review modifications made to card adjustment files for card numbers residing in the MDS Banknet AMS (Account Management System) repository.

Description:

This report provides an audit trail of Online File Update messages sent to the Banknet® telecommunications network by NICS™ or Online message sending methods. Card number records that were added, changed, or deleted appear daily in this report. The report logs record updates by Processor ID if multiple processors are owned, and then by PAN and Switch Date/Time values in ascending order.


Daily Available through Global File Transfer and eService on MasterCard OnLine


ISO DE Description


PROCESSOR

The processor name.

PROCESSOR ID



PAN

2


TRACE NUMBER

11

Every file update request message is assigned a unique identification number called a Trace Number. This number provides a message trail between message initiators and the Banknet ® telecommunications network and MDS Stand-In processes.


•

October 2006

3-93


Field

TYPE OF UPDATE

ISO DE Description

91/44

(Additional Response Data)

This column specifies the action that issuing processors took in regard to card number records residing in the Banknet Stand-In Account File and AMS repository. Valid update types include: MCC103 (DE91) Add/Change and Delete ADDITIONAL RESPONSE DATA If an error condition exists, ERROR, appears in this column. Error Codes (DE 44) 120001 •

The PAN received was not numeric.

•

The BIN in the PAN was not on file.

•

The BIN did not belong to the message initiator.

•

The check digit of the PAN was incorrect .

•

The PAN received was not on the account file.

120002 •

Issuing ICA (member ID) is not associated with primary account number’s BIN.

120003 •

Product type is not equal to MCB, MCC, MCD, MCF, MCG, MCS, MCW, MNS, MPL, or OTH.

120004 •

Response code not equal to 04–capture card

120005 •

The Entry reason was not C, X, O, or F.

120006 •

Regional indicator is not equal to 1, A, B, C, D, or E.

120007

REASON CODE

120

•

Region-requested purge date invalid

•

Region-requested purge date not equal to current or future date

This column lists the reason why the card number was reported. Valid Reason Codes for MCC103 File Updates C Credit F

Fraud O Other X Counterfeit MCI CUST ID

120

This column displays the Issuer ICA number that MasterCard assigned.

SWITCH DATE

7


SWITCH TIME

7

This is the time of the day that the update was made to the file (format: HHMMSS).

3-94

October 2006

•



Field

REGIONAL INFO

ISO DE Description

120

The first character shown in this column depicts the region code of the account listing. The next six digits depict the date the entry was requested to be purged from the Electronic Warning Bulletin file. For example, if the REGIONAL INFO value is “1030102”, then the l isted region is United States (1030102), and the account listing entry will no longer be in effect on Jan 2, 2003 (1030102). Valid Region Codes

United States A Canada 1

Caribbean, Central America, Mexico, and South America C Asia and Pacific D Europe B

Middle East and Africa The date format is: YYMMDD For regions A-E, the actual purge date will align with the printing schedule of the Warning Bulletin . E

RESP CODE

120

This column displays the issuer’s response code. Issuer Response Code 00 Completed successfully 27 File Update field error 30 Format error 40 Requested function not supported 63 Security Violation 96 System error

MESSAGE SOURCE

NA

There are two methods for updating the Banknet AMS repository. The first method is to make card adjustments using the NICS ™ application (MASTERCARD DEBIT HOTCARD FACILITY). The second method allows issuing processors to bypass the NICS ™ application and send 0302 online messages directly to the Banknet® telecommunications network through the MDS gateway. Interface Values NICS™ A NICS ™ user performed the file update. ONLINE A processor sent the file update to the MDS or Banknet®

telecommunications network through a 0302 online message. GROUP NUMBER

NA

This column applies only to file updates with a “NICS ™” Message Source, and identifies the NICS ™ user group responsible for the file update.

USER NUMBER

NA

This column applies only to file updates with a “NICS ™” Message Source, and identifies the NICS ™ user who made the file update.


•

October 2006

3-95


Figure 3.46—SWCHD141-2 Banknet AMS, Account Management File Updates Report 5 1 0 / 9 2 / 6 0 F E O G A K P R O W

R - 9 9 E - 9 9 R B - 9 9 E M S U U N R - 8 8 P E - 8 8 U B - 8 8 O M - 8 8 R U G N E G E A C S R - S S S U - C C E O - I I M S - N N P E S S D - 0 0 M E O - 0 0 E R C E T L T A - 1 1 1 1 1 A N - 3 3 3 3 3 S O - 0 0 0 0 0 D I O - 1 1 1 1 1 Y G F - 5 5 5 5 5 P E N - 0 0 0 0 0 C S R I - 1 B 1 B U S T M H - 0 8 I E C E - 2 5 A T M - 5 5 B L I I - 2 2 W T - 5 5 E T I S - 1 1 E F D - 5 5 - 0 0 N H - / / D T C E - 8 8 K T T - 2 2 R G I A - / / N W D - 6 6 A M S - 0 0 A C B T D - 2 2 R I - 0 0 N I - 2 2 E C T - 2 2 U M S - 0 0 T U - 0 0 O C S C A C N M O E A S D A O - F F E C R - E E - G G - N N F - A A O E - H H T - C C E A - / / P D - D D N Y P - D D O T U - A A I T U R - 2 6 T E E - 2 2 I 5 C B - 1 1 M - 4 4 T 5 A U - 9 9 S 5 R N 4 T N - 3 3 I 4 0 T 0 S 0 E 0 - 1 1 T 9 - 0 0 - 0 0 : : - 0 0 D - 0 0 I - 4 4 2 - 0 0 R R - 8 7 1 O O - 9 9 4 S S - 8 7 1 S S - 9 9 D E E - 8 7 H C C - 9 9 C O O N - 1 1 W R R A - 4 4 S P P P - 5 5

3-96

October 2006

•



Recurring Payment Cancellation Service—SWCHD141-3 Purpose:

This report gives MDS-connected issuer processors the ability to identify and review all additions and changes to Recurring Payment Cancellation Service records.

Description:

This report provides an audit trail of Online File Update messages sent to the Banknet® telecommunications network by NICS™. Recurring Payment Cancellation Service records that were added, changed, or deleted appear daily in this report. The report logs record updates by Processor ID if multiple processors are owned, and then by PAN and Switch Date/Time values in ascending order.


Daily Available through Global File Transfer and eService on MasterCard OnLine

Refer to Table 3.16—SWCHD141-3 Fields for a description of the SWCHD141-3 report fields. Table 3.16—SWCHD141-3 Fields Field

ISO DE Description


PROCESSOR

The processor name.

PROCESSOR ID



PRIMARY ACCT NO

2

The column lists the Primary Account Number (16 digits) associated with the card record that was updated.

ACQ CUST ID

The 6-digit institution ID truncated from the 10-digit Institution ID shown on the Transaction Processing screen.

CARD ACPT ID CODE

The Merchant ID. This number identifies the business where the transaction occurred.


•

October 2006

3-97


Field

TYPE OF UPDATE

ISO DE Description

91/44

This column specifies the action that issuing processors requested. Valid update types include: Add, Change, Delete or Error

ADDITIONAL RESPONSE DATA If an error condition exists, ERROR, appears in this column. Error Codes (DE 44) 06120000 06120001 06120002 06120003 06120004 06120006 06120007

Pan record is a duplicate Error on PAN Error on Entry Reason Error on Purge Date Error on Acquirer ICA Error on Transaction Low Amount Error on Transaction High Amount

LOW TRAN AMOUNT

The amount on which the cancellation request will be matched or the starting point of a range.

HIGH TRAN AMOUNT

The amount on which the cancellation request will be matched or the ending point of a range.

SWITCH DATE

7


SWITCH TIME

7

This is the time of the day that the update was made to the file (format: HHMMSS)

MESSAGE SOURCE

NA

The method for updating the Banknet AMS repository is to make card adjustments using the NICS ™ application (MASTERCARD DEBIT HOTCARD FACILITY). Interface Values NICS™ A NICS™ user performed the file update.

GROUP NUMBER

NA

This column identifies the NICS ™ user group responsible for the file update.

USER NUMBER

NA

This column identifies the NICS ™ user who made the file update.

3-98

October 2006

•



Figure 3.47—SWCHD141-3 Banknet AMS, Recurring Payment Canc ellation Service Report 6 1 0 / 0 1 / 3 0 F E O G A K P R O W

R R E E S B U M U N R P E U B O M R U G N E E G C A R S U S O E S M H E C M T I I T W S H C E T T I A W D S

E C I V R E S M N E O T I S T Y A S L S L T M E I A C B N E T A D E C N D K T R N N A A E C B M R Y E A T P S A G M N I R R U C E R

N A T R N T U O H M G A I H

N T A N R U T O M W A O L

F E O T A E D P P Y U T T P E C D A O C D R D A I C

3 1 4 1 D H C W S

T A S S U U 9 C D I 9 K 9 Q N 9 C A 9 A B 9 T 9 S 9 E 9 T 9 O N : : D T I C C R R A O O S S Y S S R E E A C C M O O I R R R P P P

-

8 0 7

8 1 1 1 1 0 0 0 0 0 7 7 7 7 7

8 0 7

8 8 0 0 7 7

8 0 7

9 9 9 9

9 8 8 8 8 9 8 8 8 8 9 8 8 8 8 9 8 8 8 8

9 9 9 9

9 9 9 9 9 9 9 9

9 9 9 9

S C I N

S S S S S C C C C C I I I I I N N N N N

S C I N

S C I N

7 2 4 5 6 0

5 7 7 9 2 1 2 0 1 4 5 4 4 5 6 5 3 4 4 4 6 9 9 9 9 0 0 0 0 0

3 2 5 3 0 1

6 0 / 0 1 / 3 0

6 6 6 6 6 0 0 0 0 0 / / / / / 0 0 0 0 0 1 1 1 1 1 / / / / / 3 3 3 3 3 0 0 0 0 0

6 0 / 0 1 / 3 0

S S C C I I N N , 7 2 1 1 6 7 3 0 0 1 1 1 , 6 6 0 0 / / 0 0 1 1 / / 3 3 0 0

0 0 . 0 2

0 0 0 0 0 0 0 0 0 0 . . . . . 0 5 5 5 5 2 7 7 7 7 1

0 0 . 0 2

0 0 0 0 . . 0 1 2 2

0 0 . 1 2

0 0 . 0 1

0 0 0 0 0 0 0 0 0 0 . . . . . 0 0 0 0 0 1 1 1 1 5 1

0 0 . 1 1

0 0 0 0 . . 1 0 1 2

0 0 . 0 2

9 1 7 0 1 1 6 0 / 0 1 / 3 0

3 3 3 3 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 2 2 2 2 2 1 1 1 1 1 6 6 6 6 6 0 0 0 0 0 : : : : : A A A A A T T T T T A E E A A A A * D G T * D * D * D * D D D N E D R E D D A L R E R E D R E R E O S A A H E O S O S A O S O S R N C D R N R N R N R N R O R O R O R O R O E P E P E P E P E P S S S S S E 9 E E E E V R V R R R 5 R F R F F R F R O O 6 6 6 4 R R R R M L M E E E 0 L J L J J L J L 7 A 7 0 0 0 3 A 2 A 2 2 A 2 A 7 N 7 7 7 7 0 N 0 N 0 0 N 0 N 5 O 5 0 0 0 3 O 0 O 0 0 O 0 O 3 I 3 1 1 1 9 I 0 I 0 0 I 0 I 4 T 4 3 3 3 4 T 8 T 8 8 T 8 T 0 I 0 1 1 1 9 I 4 I 4 4 I 4 I 4 D 4 3 3 3 0 D 2 D 2 2 D 2 D 8 D 8 2 2 2 1 D 7 D 7 7 D 7 D 1 A 1 6 6 6 3 A 2 A 2 2 A 2 A 7 7 0 0 0 5 0 0 0 0 0 * 0 0 0 0 3 * 0 * 0 0 * 0 * 1 1 1 1 1 7 3 3 3 3 0 0 0 0 0 2 3 3 3 3 6 6 6 6 6 5 3 3 3 3 1 1 1 1 1 1 6 6 6 6 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 6 6 0 0 6 6 0 0 6 4 4 0 1 4 5


•

0 0 0 0 0 6 6 6 6 6 6 6 6 6 6 0 0 0 0 0 0 0 0 0 0 6 6 6 6 6 6 6 6 6 6 0 0 0 0 0 0 0 0 0 0 6 6 6 6 6 4 4 4 4 4 4 4 4 4 4 0 0 0 0 0 1 1 1 1 1 4 4 4 4 4 5 5 5 5 5

October 2006

0 6 6 0 0 6 6 0 0 6 4 4 0 1 4 5

0 0 6 6 6 6 0 0 0 0 6 6 6 6 0 0 0 0 6 6 4 4 4 4 0 0 1 1 4 4 5 5

0 6 6 0 0 6 6 0 0 6 4 4 0 1 4 5

3-99


Maestro® POS Transaction Audit Report—SWCHD144 Purpose:

For issuers the report sequence provides tracking capabilities and session reporting analysis. For acquirers, the report sequence allows processors with multiple corresponding members to review transactions by Institution and Term ID.

Description:

This report details Maestro International (only) financial and non-financial transactions, regardless of completion status, that occurred on the settlement day. Intra-country (ISIS) transactions are not included in this report. International Maestro® interchange fees are not online and not reflected on this report. The MDS sequences all transactions for: •

•

The cardholder in PAN, date, and time order, and sequences transactions The acquirer in routing transit number, terminal ID, date and time order

Processors choosing not to receive this report will find the same information in the auto-reconciliation file. Frequency: Availability:


Refer to Table 3.17 for a description of the SWCHD144 report fields.



3-100

Note

The display sequence of the fields on the SWCHD144 report will vary according to the type of processor order (acquiring or issuing).

October 2006

•


Oct 2006



ISO DE Description


PROCESSOR

The processor name.

PROCESSOR ID



ACQ INST

32

TERM ID

41


ISS PRO/ACQ PRO

33

The MDS assigned processor number of the issuer and acquirer involved the transaction.

PAN

2

Primary Account Number. The MDS uses the cardholder number to identify the account being accessed during the transaction.

PROC CODE

3

The Processing Code describes the effect of a transaction on a cardholder account and the account type affected.

TRACE

11


RESP CODE

39


ADV REASON

60

The Advice Reason Code indicates the specific purpose of an advice message. The last two digits of the Advice Reason Code can indicate the reversal reason code.

CMP AMT SETTLEMENT

mx

Completed amount in the designated settlement currency of the acquirer processor for the acquirer, and the settlement currency of the issuer processor for the issuer. The amount of funds to be transferred between the acquiring and issuer processor.

STL CC

NA

Currency code of the completed amount being settled.

CMP AMT LOCAL

The acquirer processor’s Routing and Transit Number (also known as the ABA Number). This number identifies the acquirer to the MDS and can identify either an ATM or POS processor.

4



•

October 2006

3-101


Field

PROD CODE

ISO DE Description

63



ACCESS CHARGE

INTER FEE

SUSPECT TRANSACTION FOLLOWS

S

3-102

28

The additional fee or surcharge to an ATM transaction. This will report in the acquirer processor’s designated settlement currency for the acquirer, and the issuer processor’s designated settlement currency for the issuer.

29

The Interchange Fee is the transferred fee between acquiring and card processor in the settlement currency of the acquirer processor for the acquirer, and the issuer processor’s settlement currency for the issuer. The transaction following this message is a partial dispense, indicating this transaction did not complete per the amount authorized. This message is triggered from the Advice Reason Code (DE 60), subfield named Condition Code, that is generated by the MDS online to the batch. This will occur for an approved financial transaction that completed for an amount other than what was requested. The “S” that appears on the Issuer report in the first column designates that the condition code indicator reflects No PIN Entered on Transaction.

October 2006

•


Oct 2006


Figure 3.48—SWCHD144 Maestro POS Transaction Audit Report (1 of 2)—Issuing Processor 5 0 1 / 8 1 / 7 0 : E E G T A A P D T N E M E L T T E S

R H O C S T S I T R E W O P C S E R O T T R I I D P U B A E N O D I T G C D A N S R N I A A R U T C S S R O S P E I O T R T S S E A A M M 1 R O S S E 9 C 9 O 8 R 8 P 0 0 T 0 S 0 E 0 T 9 : : D I R R O O S S S S E E 1 C C O O R R T P P R O 4 P 4 E 1 R D H C W S . . . .

R E E C C C T E 0 2 2 0 0 0 N F 0 0 0 0 0 0 I . . . . . . S E S G E R C A C H A C D E O D R O P C T M L A A C P O M L C

0 0 0 0 0 0 0 0 0 0 0 0 . . . . . . 1 1 1 1 1 1 S S S S S S M M M M M M 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 1 1

L T C 0 0 0 0 0 0 S C 4 4 4 4 4 4 8 8 8 8 8 8 T T N 3 3 3 0 0 0 M E 2 3 3 0 0 0 A M . . . . . . E 2 2 P L M T C T E S E N C O I S V A D E A R P E S D R C E C A R T

0 1 0 0 1 5 4 0 0 0 4 4 4 0 0 0 1 1 1 8 8 4 8 3 9 0 2 3 3 4 4 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

D I M R E T

D D D D D D G G G G G G 0 0 0 0 0 0 2 2 2 2 2 2 1 1 1 1 1 1 D 3 3 3 3 3 3 I * 2 2 2 2 2 2 - * 1 1 1 1 1 1 T * 0 0 0 0 0 0 Q S * 0 0 0 0 0 0 C N * 0 0 0 0 0 0 A I 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 E S M W 1 8 9 0 2 8 I O 2 3 3 4 4 4 T L 0 0 0 0 0 0 / L 0 0 0 0 0 0 E O 5 5 5 5 5 5 T F 0 0 0 0 0 0 A 8 8 8 8 8 8 D N 1 1 1 1 1 1 O 7 7 7 7 7 7 I 0 0 0 0 0 0 Q O T C R C 0 0 0 0 0 0 A P A 2 2 2 2 2 2 S 1 1 1 1 1 1 N C E A 0 0 0 0 0 0 O D R 0 0 0 0 0 0 R O T 0 0 0 0 0 0 P C 1 1 1 1 1 1 T 0 0 0 0 0 0 C 0 0 0 0 0 0 E P 8 8 8 8 8 8 S 0 0 0 0 0 0 U 0 0 0 0 0 0 S 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 * 0 0 0 0 0 0 N * 0 0 0 0 0 0 A * 0 0 0 0 0 0 P * 1 1 1 1 1 1 * 2 2 2 2 2 2 1 1 1 1 1 1 3 3 3 3 3 3 2 2 2 2 2 2 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 . . 0 0 0 0 0 0


•

October 2006

3-103


Figure 3.49—SWCHD144 Maestro POS Transaction Audit Report (2 of 2)—Acquiring Processor 5 0 1 / 8 1 / 7 0 : E E G T A A P D T N E M E L T T E S

H R C O T S I S T W R E O S P C E R O T T R I I D P B U A E N G D O I N T D C I A R S R N A A I R C T U R S Q O E P C T O A R S T S A E A M M

1 T R 4 O 4 P 1 E D R H C W S

3-104

R O S S E 9 C 9 O 9 R 9 P 0 0 T 0 S 0 E 0 T 9 : : D I R R O O S S S S E E C C O O R R P P

R E E T E N F I S E S G E R C A C H A C D E O D R O P C T M L A A C P O M L C

C C C 0 2 2 0 0 0 0 0 0 0 0 0 . . . . . .

0 0 0 0 0 0 0 0 0 0 0 0 . . . . . . 1 1 1 1 1 1 S S S S S S M M M M M M 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 1 1

L T C S C

0 0 0 0 0 0 4 4 4 4 4 4 8 8 8 8 8 8

T T N M E A M E P L M T C T E S

3 1 1 0 0 0 2 3 3 0 0 0 . . . . . . 2 2

0 1 0 0 1 5 4 P E 0 0 0 4 4 4 S D 0 0 0 1 1 1 R C 8 8 4 8 3 9 E 0 2 3 3 4 4 C 0 0 0 0 0 0 A 0 0 0 0 0 0 R 0 0 0 0 0 0 T 0 0 0 0 0 0 0 0 0 0 0 0 C E 0 0 0 0 0 0 O D 0 0 0 0 0 0 R O 1 1 1 1 1 1 P C 0 0 0 0 0 0 0 0 0 0 0 0 8 8 8 8 8 8 0 0 0 0 0 0 0 0 0 0 0 0 * 0 0 0 0 0 0 * 0 0 0 0 0 0 * 0 0 0 0 0 0 * 0 0 0 0 0 0 * 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 N S 2 2 2 2 2 2 A W 1 1 1 1 1 1 P O 3 3 3 3 3 3 L 2 2 2 2 2 2 L 1 1 1 1 1 1 O 0 0 0 0 0 0 F 0 0 0 0 0 0 0 0 0 0 0 0 N E O 1 8 9 0 2 8 M I 2 3 3 4 4 4 I T 0 0 0 0 0 0 T C 0 0 0 0 0 0 / A 5 5 5 5 5 5 E S 0 0 0 0 0 0 T N 8 8 8 8 8 8 A A 1 1 1 1 1 1 D R 7 7 7 7 7 7 T 0 0 0 0 0 0 S O T 1 1 1 1 1 1 S R C 2 2 2 2 2 2 I P E 1 1 1 1 1 1 P S D U I S D D D D D D M G G G G G G R 0 0 0 0 0 0 E * 2 2 2 2 2 2 T * 1 1 1 1 1 1 * * 3 3 3 3 3 3 T * 2 2 2 2 2 2 S 1 1 1 1 1 1 N 0 0 0 0 0 0 I 0 0 0 0 0 0 0 0 0 0 0 0 Q 0 0 0 0 0 0 C 0 0 0 0 0 0 A 0 0 0 0 0 0 E N C O I S V A D E A R

October 2006

•



Negative File Updates—SWCHD147-1 Purpose:

This report gives members the ability to track changes made to the MDS Stand-In Negative Card file.

Description:

This report provides an audit trail of MDS Negative Card file records that were recently added, changed, or deleted by NICS™ or online message sending methods. Only updates affecting the MDS Negative Card file appear in this report. The report logs record updates by Processor ID if multiple processors are owned, and then by PAN and Switch Date/Time values in ascending order.




Description


PROCESSOR

The processor name.

PROCESSOR ID



PAN


INST ID

This column displays the card issuer’s Institution ID (BIN or Routing and Transit number).

Card Status

This column reveals the reason for the card being reported to the MDS Hot Card Facility. Valid Hot Card Status Codes F L O P S U X V

Fraud Lost Other Capture Stolen Unauthorized Counterfeit VIP


•

October 2006

3-105


Field

Description

SWITCH DATE

This is the date that the update was made to the MDS Stand-In Negative file (format: MM/DD/YY).

SWITCH TIME

This is the time of the day that the update was made to the MDS Stand-In Negative file (format: HHMMSS).

PURGE DATE

The date that the MDS purges the account number record from the MDS Stand-In Negative file (format: YYMMDD).

TYPE OF UPDATE This column specifies the action that issuing processors took in regard to card number records residing in the MDS Stand-In Negative Card file. Valid update types include: Add, Delete, and Change. UPDATE SOURCE (i.e. this is the same data as Message Source)

There are two methods for updating MDS Stand-In database files. The first method is to make card adjustments using the NICS ™ application (STAND-IN NEGATIVE CARD FACILITY). The second method allows issuing processors to bypass the NICS ™ application and send 0302 online messages directly to MDS. The online method cannot currently be used to change the MDS Stand-In VIP file. Interface Values NICS™

A NICS ™ user performed the file update.

ONLINE A processor sent the file update to the MDS or Banknet ® telecommunications

network through a 0302 online message. GROUP NUMBER This column identifies the NICS ™ user group responsible for the file update. It applies only to NICS™ users (i.e. “NICS ™” Update Source). USER NUMBER

This column identifies the NICS ™ user who made the file update. It applies only to NICS™ users (“NICS ™” Update Source).

TOTAL EXCEPTION COUNT

The total number of Stand-In exception records for a processor. This number comes from the Processor Data File (PDF). Only those records having 840 Country Codes (U.S. Region) are counted.

3-106

October 2006

•



Figure 3.50—SWCHD147-1 MDS Stand-in, Negative File Updates Report 5 1 0 / 4 0 / 7 0 F E O G A K P R O W

M S E E T T S A Y D S N P I T U I D B N E E A L T I D S F D R S E A D V C M I R T E A T G S E A N M

1 7 4 1 D H C W S

9 K 9 N 9 A 9 B 9 0 T 0 S 0 E 0 T 9 : : D I R R O O S S S S E E C C O O R R P P

R E R B E M S U U N

_ _ _ _ _ _ _ _ _ _ R _ P E _ U B _ O M _ R U _ G N _ _ _ E E _ T C _ A R _ D U _ P O _ U S _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ F _ O E _ T _ E A _ P D _ Y P _ T U _ _ _ _ _ _ ) _ D _ E D _ G E M _ R T M _ U A Y _ P D Y _ ( _ _ _ _ _ _ H _ C E _ T M _ I I _ W T _ S _ _ _ _ ) _ Y _ H Y _ C E / _ T T D _ I A D _ W D / _ S M _ M _ ( _ _ _ S _ U _ D T _ R A _ A T _ C S _ _ _ _ _ _ D _ I _ _ T _ S _ N _ I _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ N _ A _ P _

E E E E E E E E E E N N N N N N N N N N I I I I I I I I I I L L L L L L L L L L N N N N N N N N N N O O O O O O O O O O

4 0 8 2 0 0 0 0

D D D D D D E D D D D D D D D D G D D D A A A A A A N A A A A H C 1 1 4 4 4 4 4 4 1 1 3 3 0 0 0 0 0 0 3 3 2 2 1 1 1 1 1 1 2 2 1 1 0 0 0 0 0 0 1 1 9 9 6 7 7 7 8 6 9 9 4 4 0 0 0 0 0 0 4 4

9 9 5 4 4 7 4 7 9 5 5 5 1 4 3 0 0 1 1 0 0 9 9 4 2 7 1 3 0 4 0 4 1 3 1 4 5 0 5 0 0 0 5 2 0 2 7 7 1 6 1 1 1 1 0 0 0 1 1 0 5 5 5 5 5 5 5 5 5 5 0 0 0 0 0 0 0 0 0 0 / / / / / / / / / / 4 4 4 4 4 4 4 4 4 4 0 0 0 0 0 0 0 0 0 0 / / / / / / / / / / 7 7 7 7 7 7 7 7 7 7 0 0 0 0 0 0 0 0 0 0

F F U U U U S U L U

3 9 8 2 3 2 5 1 5 9 4 8 7 3 4 1 3 2 6 8 3 9 9 2 3 2 5 1 6 8 4 8 8 3 4 1 3 2 4 8 3 9 7 2 3 2 5 1 4 7 4 1 9 3 3 1 3 2 4 7 3 2 8 2 2 2 1 1 4 7 2 2 2 2 2 2 2 3 4 4 1 1 1 1 1 1 1 2 2 2

7 2 6 2 4 6 8 4 8 5 6 1 6 2 3 5 8 4 9 4 5 9 6 2 3 6 8 4 8 4 9 9 6 2 3 5 8 4 9 4 8 9 6 2 3 6 8 4 8 4 7 9 6 2 3 5 8 4 9 4 6 9 6 2 3 6 8 4 8 2 5 9 6 2 3 5 8 4 9 2 4 9 6 2 3 6 8 4 8 2 3 9 6 2 3 5 8 4 9 2 2 9 6 2 3 6 8 4 8 2 1 9 6 2 3 5 8 4 9 2 2 9 6 2 3 6 8 4 8 2 1 9 6 2 3 5 1 4 9 2 4 9 5 1 3 4 4 2 4 2 5 5 5 5 5 5 5 5 5 5


•

T N U O C N O I T P E C X E L A T O T

October 2006

3-107


VIP File Updates—SWCHD147-2 Purpose:

This report gives members the ability to track changes made to the MDS Stand-In VIP file.

Description:

This report provides an audit trail of MDS VIP Card file records that were recently added, changed, or deleted by NICS™. There is currently no ONLINE method for updating this file. Only updates affecting the MDS VIP Card file appear in this report. The report logs record updates by Processor ID if multiple processors are owned, and then by PAN and Switch Date/Time values in ascending order.


Daily Available through Global File Transfer.


Description


PROCESSOR

The processor name.

PROCESSOR ID



PAN


INST ID

This column displays the card issuer’s Institution ID (BIN or Routing and Transit number).

Card Status

This column reveals the reason for the card being reported to the MDS Hot Card Facility. Valid Hot Card Status Codes F L O P S U X

3-108

Fraud Lost Other (Used for VIP status only) Capture Stolen Unauthorized Counterfeit.

October 2006

•



Field

Description

SWITCH DATE

This is the date that the update was made to the MDS Stand-In VIP file (format: MM/DD/YY).

SWITCH TIME

This is the time of the day that the update was made to the MDS Stand-In VIP file (format: HHMMSS).

PURGE DATE

The date that the MDS purges the account number record from the MDS Stand-In VIP file (format: YYMMDD).

TYPE OF UPDATE This column specifies the action that issuing processors took in regard to card number records residing in the MDS Stand-In VIP Card file. Valid update types include: Add, Delete, and Change. UPDATE SOURCE (i.e. this is the same data as Message Source)

There are two methods for updating MDS Stand-In database files. The first method is to make card adjustments using the NICS ™ application (STAND-IN VIP CARD FACILITY). The second method allows issuing processors to bypass the NICS ™ application and send 0302 online messages directly to MDS. The online method cannot currently be used to change the MDS Stand-In VIP file. Interface Values

A NICS ™ user performed the file update.

NICS

ONLINE A processor sent the file update to the MDS or Banknet ® telecommunications

network through a 0302 online message. GROUP NUMBER This column identifies the NICS ™ user group responsible for the file update. It applies only to NICS™ users (i.e. “NICS ™” Update Source). USER NUMBER

This column identifies the NICS ™ user who made the file update. It applies only to NICS™ users (i.e. “NICS™” Update Source).

Second Column Headings—Display across the page below the first column headings. Data displays below the related data identified by the First Column Headings.

TOT CNT

This column displays the maximum number transactions that Stand-In will process from combined ATM and POS transactions in a single settlement day.

TOT AMT

This column reports the maximum amount of money that Stand-In will debit from combined ATM and POS transactions in a single settlement day.

ATM CNT

This column displays the number of ATM transactions that was processed by Stand-In processes in one day.

ATM AMT

This column reports the amount of money in ATM withdrawals that was processed by Stand-In processes in one day.

SAV CNT

This column displays the number of ATM withdrawals from Savings that was processed by Stand-In processes in one day.

SAV AMT

This column reports the amount of money in ATM withdrawals from savings.

DDA CNT

This column displays the number of ATM withdrawals from credit card accounts that was processed by Stand-In in processes one day.

DDA AMT

This column reports the amount of money in ATM withdrawals from DDA/checking that was processed by Stand-In processes in one day.


•

October 2006

3-109


Field

Description

CCD CNT

This column displays the number of ATM withdrawals from credit card accounts that was processed by Stand-In processes in one day.

CCD AMT

This column reports the amount of money in ATM cash disbursements from credit card accounts processed by Stand-In processes in one day.

NAS CNT

This column displays the number of ATM withdrawals from No Account Specified (NAS) processed in Stand-In processes in one day.

NAS AMT

This column reports the amount of money in ATM withdrawals from No Account Specified (NAS) processed by Stand-In processes in one day.

POS CNT

This column displays the number of Point of Sale (POS) purchases, regardless of account type, processed by Stand-In processes in one day.

POS AMT

This column reports the number of Point of Sale (POS) purchases, regardless of account type, processed by Stand-In processes in one day

Total Field—Displays at the bottom of the report.

TOTAL EXCEPTION COUNT

3-110

The total number of Stand-In exception records for a processor. This number comes from the Processor Data File (PDF). Only those records having 840 Country Codes (U.S. Region) are counted.

October 2006

•



Figure 3.51—SWCHD147-2 MDS Stand-in, VIP File Updates Report 5 1 0 / 7 1 / 6 0 F E O G A K P R O W

M E T S S Y E S N T I A T D I D P B N U E A D T E S D L R S I A D F C M R P E I T V S A M

2 7 4 1 D H C W S

8 K 8 N 4 A 3 B 2 1 T 0 S 0 E 0 T 9 : : D I R R O O S S S S E E C C O O R R P P

R E R B E M S U U N

_ T _ M _ A _ _ S _ O _ P _ _ _ R T _ P E N _ U B C _ O M _ R U S _ G N O _ P _ _ E E _ T C _ A R T _ D U M _ P O A _ U S _ S _ A _ N _ _ _ T _ N _ C _ _ S _ A _ N _ _ _ _ T _ M _ A _ _ D _ C _ C _ F _ O E _ T T _ E A N _ P D C _ Y P _ T U D _ C _ C _ _ _ _ ) T _ D M _ E D A _ G E M _ R T M A _ U A Y D _ P D Y D _ ( _ _ T _ N _ C _ _ H A _ C E D _ T M D _ I I _ W T _ S _ T _ M _ A _ ) _ Y V _ H Y A _ C E / S _ T T D _ I A D _ W D / T _ S M N _ M C _ ( _ V _ A _ S S _ U _ D T _ R A _ A T T _ C S M _ A _ _ M _ T _ A _ D _ I _ T _ T N _ S C _ N _ I M _ T _ A _ _ _ _ T _ M _ A _ _ T _ O _ T _ _ _ T _ N _ C _ _ N T _ A O _ P T _

9 9 9 0 9 0 9 0 9 0 1 1

1 1 2 2 1 0 1 0 2 1 2 1

S C I N

S C I N

E G N A H C

E G N A H C

1 3 2 1 9 4

1 3 2 1 9 4

8 2 6 0 7 1

4 2 7 0 0 1

5 0 / 6 1 / 6 0

5 0 / 7 1 / 6 0

1 0 0 0 0 0 0 0

L L

8 8 2 1 2 1 2 1 9

8 1 2 1 2 1 2 1 9

T N U O C N O I T 5 0 5 0 P 0 0 0 0 E 4 1 4 1 C 8 8 X 0 0 E 0 0 0 7 L 0 6 A 2 5 T 1 4 O 2 3 T 1 0 2 0 2 1 1 1 1 5 8 8 5 5


•

October 2006

3-111

Reports Statistical Reports

Statistical Reports Statistical reports summarize the processor’s activity and performance as acquirer and issuer. The MDS generates these reports daily and monthly. Processors can use these reports to analyze their performance to ensure that they continue to comply with network standards. Table 3.20 lists the MDS Statistical reports name, and purpose by report number. Table 3.20—MDS Statistical Reports

3-112

Number

Name

Purpose

SWCHD15-X

Financial Institution Table (FIT) report

Processors can use this report to update acquirer routing tables. The MDS provides indicators for each identifier to determine if the identifier has been added (A) or deleted (D) since the last update.

SWCHD35

Institution Definition File (IDF)

Processors can use this report to review and manage routing and transit numbers.

SWCHD61

Daily Processing Summary report

Processors should use this report to monitor their performance rates to ensure they comply with network standards and to highlight the differences in debit and credit performance. Processors can use this report to identify problems such as PIN failures, invalid account selection, format errors, and the need for increased cardholder education.

SWCHD73a

Monthly Availability Report

Members should use this report to track member performance on a month-to-month basis to ensure that the issuing processor complies with network performance standards.

SWCHD127-1

Daily Cardholder Performance Report

The MDS generates this report for each processor to assist in focusing on those card portfolios that do not meet product performance standards.

SWCHD127-2

Daily Cardholder Performance Variance Report

Issuers can use this report to identify problems with a particular BIN.

October 2006

•


Oct 2006


Number

Name

Purpose

SWCHD143

Maestro® POS Daily Processing Summary

Processors should use this report to monitor their performance rates to ensure that they comply with network standards. Processors can use this report to identify problems such as PIN failures, invalid account selection, format errors, and the need for increased cardholder education.

SWCHD320-1

Daily Processor Performance Report

Processors can use this report to track performance trends and to plan possible corrective actions.

SWCHD321-1

Processor Peak Performance Report


SWCHD321-2

Processor Daily Summary Performance Report


SWCHM03a

Transaction Interchange Month-to-Date

The acquiring report reflects the types of transactions other cardholders performed at the processor’s terminals. The cardholder report reflects the types of transactions that the processor’s cardholders performed at other processor’s terminals. (This may be helpful for marketing analysis.)

SWCHM06a

Month-to-Date Processing Processors should use this report to Summary Report monitor their performance rates to ensure that they comply with network standards and to highlight the differences in debit and credit performance. Processors can use this report to identify problems such as PIN failures, invalid account selection, format errors, and the need for increased cardholder education.

SWCHM07a

Month-to-Date Denial Summary Report

Processors use this report to evaluate performance

a Reports produced daily with month-to-date totals .


•

October 2006

3-113

Oct 2006


Financial Institution Table Report (FIT)—SWCHD15-X Purpose:

Processors can use this report to update acquirer routing tables. The MDS provides indicators for each identifier to determine if the identifier has been added (A) or deleted (D) since the last update.

Description:

This report is available by identifier for all products and by processor for the products supported. The report by BIN identifier provides the following information: identifier (BIN), identifier length, processor number associated with the identifier, and the currency code associated with the identifier.

Frequency:

Daily

Availability:



Note

Available through Global File Transfer.

The MDS can send the FIT as either a print image report or data file.

FIT by Identifier and FIT by Processor Refer to Table 3.21 for a description of the SWCHD15-X report fields. Table 3.21—SWCHD15-X Fields Field

Description

Header Field—Displays at top of all pages of the report. For reports by p rocessor.

PROCESSOR ID


Column Headings—Display across the page.

REC ID

Indicates the table ID for the Financial Institution Table

F IDENTIFIER

The prefix of the card that participates in this product. This entry can be 4 to 11 digits in length.

LEN

The length of the card prefix

PROC

The MDS assigned processor Number for the BIN.

CUR

The ISO assigned currency code. Indicates the local currency used at the terminal.

3-114

October 2006

•



Figure 3.53—SWCHD15-X Financial Institution Table by Processor Report (2 of 2) 5 2 0 / 5 0 / 7

R E I 0 5 0 F 2 2 2 I 2 1 0 2 I T 5 6 6 1 0 4 0 I N 4 5 9 3 0 3 7 E 4 7 0 3 0 8 0 0 K D 9 1 0 3 8 9 0 5 C I 1 3 7 0 1 2 6 8 A 1 4 4 5 5 5 5 5 R T H T G 6 9 4 9 7 9 6 6 N 0 0 0 0 0 0 0 0 E L

F E O G A K P R O W

H C T I W S

R E I 3 4 F 7 2 7 I 1 1 0 1 I T 8 7 6 6 3 0 3 0 I N 1 8 6 9 1 3 3 0 E 2 3 8 3 0 3 0 7 K D 1 3 9 3 0 8 7 3 C I 0 2 4 0 1 1 4 8 A 1 4 4 5 5 5 5 5 R T H T G 9 6 6 9 8 6 6 7 N 0 0 0 0 0 0 0 0 E L

E L B A T

N O I R T T T O I N U S B I S T S E R U I E D P R T C R S O D E I N R R L C I P A I C F L Y R A B E I T C S N A A M N I F

1 5 1 D H C W S

3-116

R E 0 I 4 3 3 1 0 F 5 3 2 2 7 0 0 I 9 1 5 1 8 8 0 I T 0 1 3 6 7 4 9 0 I N 0 7 0 9 7 6 4 8 E 0 1 6 3 8 0 0 4 K D 1 1 3 3 3 8 0 1 C I 0 0 4 0 0 1 4 8 A 1 3 4 5 5 5 5 5 R T H T G 9 9 8 9 8 0 6 9 N 0 0 0 0 0 1 0 0 E L R E I 9 1 F 2 4 3 6 0 I 1 8 3 0 8 I T 0 9 3 6 3 4 0 6 I N 0 7 0 9 0 6 9 9 E 0 4 6 3 8 0 9 0 K D 1 2 3 3 3 8 4 1 C I 0 7 4 0 0 1 3 8 A 1 2 4 5 5 5 5 5 R T H T G 9 8 8 8 6 9 6 6 N 0 0 0 0 0 0 0 0 E L

R E I F 4 1 7 I 3 0 5 1 I T 0 6 6 6 2 0 0 I N 0 2 0 9 9 3 3 0 E 9 9 6 3 3 0 5 7 K D 4 3 3 3 3 8 1 3 C I 7 1 4 0 0 1 3 6 A 0 2 4 5 5 5 5 5 R T H T 1 - G 8 6 5 8 8 6 6 7 9 - N 0 0 0 0 0 0 0 0 9 - E 0 - L 0 0 0 0 0 - R 9 - E - I 0 : - F 5 2 2 D - I 2 2 4 4 I - I T 0 6 1 6 1 1 3 8 - I N 0 5 8 7 9 3 0 8 5 R - E 9 7 2 7 3 0 8 4 8 O - K D 4 1 0 0 3 8 9 0 5 S - C I 7 3 4 0 0 1 2 6 8 S - A 0 1 4 5 5 5 5 5 5 E - R C - T H O - T R - G 8 9 5 6 8 7 9 6 6 P - N 0 0 0 0 0 0 0 0 0 E L

October 2006

•



Institution Definition File (IDF)—SWCHD35 Purpose:

Processors can use this report to review and manage routing and transit numbers.

Description:

This report provides Customer and Technology Support information for each of the processor’s routing and transit numbers.

Frequency:

Daily

Availability:



Description


PROCESSOR

The processor name.

PROCESSOR ID



INST NO ACQ PROD

The Routing and Transit Number assigned to the processor. A “Y” indicates the processor supports the product. A blank indicates the processor does not support the product. The products listed are: C Cirrus P PLUS M MasterCard V Visa


•

October 2006

3-117


Figure 3.54—SWCHD35 Institution Definition Report 1 5 0 / 5 0 / 7 E F G O A P K R O W

D V O R M P P Q C C A O N T S N I D V O R M P P Q C C A O N T S N I

H C T N I O W I S T I T N I T I B N F E I E D R D P D R N E A O L C I I R T F E U T T S I A T M S N I

D V O R M P P Q C C A O N T S N I D V O R M P P Q C C A O N T S N I D V O R M P P Q C C A O N T S N I

5 3 D H C W S

3-118

K R O W T 0 E 0 D V N 0 O 0 R M S 0 P U 0 P R 0 Q R 0 C C I 0 A C 9 : : O D N I T R R S O O N S S I S S E E C C O O R R P P

Y Y 3 1 7 0 0 4 0 0 2 0 0 1 0 0 0 0 0 4 4 0 2 3 4 1 4 7 9

8 8 3 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 9 3 9 3 7 8

9 3 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 4 6 6 5 7 3 6 8

Y Y 4 7 9 5 6 0 0 8 6 0 0 1 5 0 0 8 5 0 0 0 4 0 2 8 4 0 0 1 3 5 3 8 3 6 8 9

6 2 7 7 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 4 8 6 8 2 4 7 9

0 0 0 6 6 0 0 0 3 0 0 0 5 0 0 0 2 0 0 0 0 0 0 2 0 0 1 2 0 4 4 7 0 4 7 9

F F F F D D D D I I I I * * * *

October 2006

•



Daily Processing Summary Report—SWCHD61 Purpose:


Description:

This report provides a daily summary of the processor’s performance by response code and completion code. This report lists a count of Stand-In transactions that occurred at the time of MDS Stand-In processing support by transaction type. The MDS segregates this report into acquirer and issuer activity, and then into debit and credit activity based on the prefix (BIN) functionality.



Acquiring Processor and Card Processor Refer to Table 3.23 for a description of the SWCHD61 report fields. Table 3.23—SWCHD61 Fields Field

Description Oct 2006


PROCESSOR

The processor name.

DEBIT or CREDIT (Heading)

The MDS generates separate reports for debit and credit activity. This heading displays at the top of the page beside the Processor Name to identify the report.

PROCESSOR ID



DESCRIPTION TRANSACTION APPROVED TRANSACTIONS NOT APPROVED

The explanation of transaction types by the Response Code and Advice Reason Code.

ADVICE REASON

The number assigned to each transaction type description.

Each category has a subtotal providing total for trans counts and percentages.


•

October 2006

3-119


Field

Description

RESPONSE CODE

The Response Code number assigned to each description. An (S) indicates that the MDS generated the response.

TRANS COUNT

Number of transactions

% OF TOTAL

Percentage of total transactions by response and completion code

STAND-IN COUNT

Number of transactions processed by MDS Stand-In

TOTAL COUNT

The combined total of transactions and Stand-In counts per transaction type description.

% OF TOTAL

Percentage of total transactions by response and completion code.

Total Fields—Display at the bottom of the page.

TOTAL

TOTAL DEBIT/CREDIT DEBIT FAIL % / CREDIT FAIL %

The combined counts, percentages, and Stand In, for transactions approved and rejected. This field displays on each page of the report.

Oct 2006

Total number of debit/credit transactions This field displays on the last page of the Acquiring Processor and Issuing Processor report. •

The credit and debit fail percentages for acquiring processors are calculated as: [Format error (S11) + Invalid dollar amount (S13) + ATM proc or owning invalid (S31) + ATM processor inoperative (S83)] divided by [Total transaction count cardholder proc not found (S92)].

The credit and debit fail percentages for card processors are calculated as: [cardholder proc timeout (S91) + cardholder proc inoperative billable (S91) + cardholder proc inoperative non-billable (S91)] divided by [Total transaction count - cardholder proc non found (S92)]. This field displays on each page of the report. •

DEBIT/CREDIT FAIL %

•

Oct 2006

The debit/credit fail percentage for acquiring processors is calculated as: [Format error (S11) + Invalid dollar amount (S13) + ATM proc or owning invalid (S31) + ATM processor inoperative (S83) {for both debit and credit}] divided by total debit/credit.

The debit/credit fail percentage for card processors is calculated as: [cardholder proc timeout (S91) + cardholder proc inoperative billable (S91) + cardholder proc inoperative non-billable (S91) {for both debit and credit}] divided by total debit/credit. This field displays on the last page of the Acquiring Processor and Issuing Processor report. •

MASTERCARD DEBIT This is the count total of MasterCard debit transactions. These numbers are not TRANSACTIONS included in the report computations. This field displays on each page of the report. SYSTEM DENIAL RATE FINANCIAL

3-120

Is calculated as: [Unable to process financial (82) + cardholder proc inoperative financial (91)] divided by [Total transaction count - cardholder proc inoperative inquiry (82) {for both debit and credit].

October 2006

•


Oct 2006

Oct 2006


Figure 3.55—SWCHD61 Daily Processing Summary Reports (1 of 4)—Acquiring Processor 6 0 / 1 8 2 / 3 0 E G F A O P K R O W

Y H R C A T M R I M O W U S S S S E T C G I O N B R I E P S D S E G D C N R O I A R R C P I R U E Q Y T C L S A I A A M D

3 T R O P 1 E 6 R D H C W S

T I B E D -

A S U 9 9 K 9 N 9 A 9 B 9 T 9 S 9 E 9 T 9 : : D I R R O O S S S S E E C C O O R R P P

F L O A T % O T

8 0 1 0 9 6 3 4 . . . . 9 8 0 0 7

9 2 . 9 8

3 7 6 8 4 2 . . . 2 0 7 3

7 5 . 0 4

0 0 . 0 0 1

L T A N T U O O T C

8 7 3 4 5 1 7 9 7 0 , , 8 2 1

2 4 9 , 0 2

6 1 9 7

6 8

2 1 2

F L O A T % O T

6 0 0 0 0 0 0 0 . . . . 0 0 0 0

6 0 . 0

0 0 0 0 0 0 . . . 0 0 0

0 0 . 0

0 0 . 0

3 0 0 0 1

3 1

0 0 0

0

0

F L O A T % O T

2 0 1 0 9 6 3 4 . . . . 9 8 0 0 7

3 2 . 9 8

3 7 6 8 4 2 . . . 2 0 7 3

7 5 . 0 4

0 0 . 0 0 1

S T N N A U R O T C

5 7 3 4 4 1 7 9 7 0 , , 8 2 1

9 2 9 , 0 2

6 1 9 7

6 8

2 1 2

N I T N D U N O A C T S

E S N E O D P O S C E R E N C O I S V A D E A R



) 0 1 , 0 0 (

0

% L I A F T I B E D

S N O I T C A S N A R T T I B E D D R A C R E T S A M

2 0 5 1 3 5 ) ) S S ( ( 0 8 1 1 0 0 0 0

L A T O T B D U E S V O D D R E E E P V S V P O N O A R E R P P P T P S E P O A I R A N D U N L N N O E L I O O I L C A A I I T A N I F T T C M A T C C A R L R M A A S O A A T S S N N B P A N N A A A R R R T T T

•

7 4 . 0

October 2006

Y R T L E A R I C R N E A M N O I T F S U N C O I W T O C L A L S A N R , A O N R R I T R P E D D I T I L A L A M A V R V N O N I F I

L A T O T B U S D E V O R P P A T O N N O I T C A S N A R T

L A T O T

3-121


Figure 3.56—SWCHD61 Daily Processing Summary Reports (2 of 4)—Acquiring Processor 6 0 / 2 8 2 / 3 0 E G F A O P K R O W

Y H R C A T M R I M O W U S S S S E T C G I O N B R I E P S D S E G D C N R O I A R R C P I R U E Q Y T C L S A I A A M D


3-122

T I D E R C -


F L O A T % O T

7 3 3 6 1 3 1 2 . . . . 3 5 0 0 6

0 9 . 8 6

7 7 6 6 . . 6 6 1 1

3 3 . 3 3

0 0 . 0 0 1

L T A N T U O O T C

7 1 4 8 0 6 9 1 , 1

0 8 0 , 2

2 2 4

2 1

F L O A T % O T

0 0 0 0 0 0 0 0 0 0 . . . . . 0 0 0 0 0

0 0 0 0 0 0 . . . 0 0 0

0 0 . 0

0 0 0 0 0

0 0 0

0


F L O A T % O T

7 3 3 6 1 3 1 2 . . . . 3 5 0 0 6

0 9 . 8 6

7 7 6 6 . . 6 6 1 1

3 3 . 3 3

0 0 . 0 0 1

S T N N A U R O T C

7 1 4 8 0 6 9 1 , 1

0 8 0 , 2

2 2 4

2 1



) 0 1 , 0 0 (

4 2 2

0

4 0 0 0 2 0 0 2 . . 0 0

2 5 1 5 ) S ( 0 8 1 1 0 0 0 0

D E E V S O N R E P P P S E A I R D U N L O E L I I L C A A T A N I F C M A T A R L R M S O A A T N N B P A A R T

L A T O T B D U E S V O D R E P V P O A R P T P O A N N N O O I I T T C C A A S S N N A A R R T T

Y R T L E A R I C R N E A M N O I T F S U N C O I W T O C L A L S A N , A N R I T P D D I I L L A A V V N N I I


T I D E R C / T I B E D L A T O T

% % L L I I A A F F T T I I D D E E R R C C / T I L B E A D T O T


October 2006

•



Figure 3.57—SWCHD61 Daily Processing Summary Reports (3 o f 4)—Issuing Processor 6 0 / 3 8 2 / 3 0 E G F A O P K R O W

Y H R C A T M R I M O W U S S S S E T C G I O N B R T I E P I S D B S E E D D C G R O N A R I C P U R S E S Y T I L S I A A M D



F L O A T % O T

5 2 8 1 6 0 . . . 6 4 3 4

L T A N T U O O T C

F L O A T % O T

5 1 . 6 4

0 0 . 0 0 1

0 3 2 5 3 3

2 8 0 2 3

5 6

0 0 0 0 0 0 0 0 . . . . 0 0 0 0

0 0 0 0 0 0 . . . 0 0 0

0 0 . 0

0 0 0 0

0 0 0

0

F L O A T % O T

5 2 8 6 1 0 . . . 6 4 3 4

8 8 0 0 . . 3 3 4

5 1 . 6 4

0 0 . 0 0 1

S T N N A U R O T C

0 3 2 5 3 3

2 8 0 2 3

5 6


5 8 . 3 5

5 8 . 3 5

E S N E ) O D 0 P O 1 S C , E 0 R 0 ( E N C O I S V A D E A R

8 8 0 0 . . 3 3 4

0 0 0 0 0 . . 0 0

2 5 1 5 ) S ( 0 1 0 0

L Y A R T T O L L E T A A R B T I U O C R S T N E B D A M D U E N O E S V I T V O F S O N D D R U R O E E E P N C P I V S V P O P T O N O A I W A P R E R T O I P P P T C L T R P S P O A L O C A I A N S A N S D N , E N N N A N N D O E L O O R I O I L C A I I T P I T A N I T T T C M A T C C D D C A R L R A A I I A S O A A S S L L S N N B P N N A A N A A A V V A R R R N N R T T T I I T


•

October 2006

L A T O T

% L S A N L I O I C I A N T F A C N A T I S I F N B A E E R D T T A R T I L B A E I D N E D D R A M C E R T E S T Y S S A M

3-123


Figure 3.58—SWCHD61 Daily Processing Summary Reports (4 o f 4)—Issuing Processor 6 0 / 4 8 2 / 3 0 E G F A O P K R O W

Y H R C A T M R I M O W U S S S S E T C G I O N B R I E P S D S E D C G R O N A R I C P U R S E S Y T I L S I A A M D


3-124

T I D E R C -


F L O A T % O T

3 3 3 7 3 3 3 6 . . . . 3 8 8 6 3 1

7 6 . 6 6

7 7 6 6 . . 6 6 1 1

3 3 . 3 3

0 0 . 0 0 1

L T A N T U O O T C

4 1 1 2

8

2 2

4

2 1

F L O A T % O T

0 0 0 0 0 0 0 0 . . . . 0 0 0 0

0 0 . 0

0 0 0 0 . . 0 0

0 0 . 0

0 0 . 0

0 0 0 0

0

0 0

0

0

F L O A T % O T

3 3 3 7 3 3 3 6 . . . . 3 8 8 6 3 1

7 6 . 6 6

7 7 6 6 . . 6 6 1 1

3 3 . 3 3

0 0 . 0 0 1

S T N N A U R O T C

4 1 1 2

8

2 2

4

2 1



) 0 1 , 0 0 (

6 2

0

6 2

0 0 0 0 . . 0 0

0 0 . 0

0

T I D E R C / T I B E D

% % L L I I A A F F T T I I D D E E R R C C / T I B E D

L A I C N A N I F E T A R L A I N E D M E T S Y S


2 5 1 5 ) S ( 0 9 1 1 0 0 0 0

L A T O T B U S N D D O E E E I V S V T O N O P R E R I P P P R P S T P C A I U A S D O E N E N D O E L M O I L C A I I T A N I T T C M A T C A R L R M A S O A A T S N N B P A N A A R R T T

D E V O R P P A T O N N O I T C A S N A R T

Y R T L E A R I C R N E A M N O I T F S U N C O I W T O C L A L S A N , A N R I T P D D I I L L A A V V N N I I


L A T O T

L A T O T

October 2006

•



Monthly Availability Report—SWCHD73 Purpose:

Members should use this report to track member performance on a month-to-month basis to ensure that the issuing processor complies with network performance standards.

Description:

This report summarizes the total down time, adjusted down time, and percentage of the time the processor is available to authorize transactions. This report reflects the availability of the cardholder’s processor and includes the current and prior month’s data.




Note


The MDS sends this report to cardholder processors daily.

Cirrus Network and Processor Refer to Table 3.24 for a description of the SWCHD73 report fields. Table 3.24—SWCHD73 Fields Field

Description

Header Field—Displays at top of all pages of the report.

PROCESSOR

The MDS-assigned processor/member identification number and processor name.

Column Headings—Displays across the page, just below the Header fields.

DATE

The system date that the downtime occurred

TIME

The system time that the downtime occurred

DOWNTIME

The duration of the downtime


•

October 2006

3-125


Field

Description

REASON

The cause of the downtime: A Application E Encryption H Hardware Line S Software M Modem D Scheduled L

P ?

EXPLANATION

Processor Unclassified

Indicates the cause of the problem

Total Fields—Displays to the left of the page.

TOTALS FOR MONTH Lists the amount of time the processor was down and the downtime classification. It also indicates the percentage of total downtime associated with each classification. TOTAL TIME

The total downtime for the month

ADJUSTED TIME

The total time from the processor category Processor—sum of downtime indicated with a status code of ‘P’. Network—sum of downtime indicated with a status code of ‘H’, ‘S’, and ‘?’.

AVAILABILITY

Total hours per month downtime less the total hours divided by the total hours per month multiplied by 100

ADJUSTED AVAILABILITY

Total hours per month downtime less the Adjusted time divided by the total hours per month multiplied by 100

3-126

October 2006

•



Figure 3.59—SWCHD73 Monthly Availability Report (1 of 2) 5 1 0 / 2 0 E / G 8 A 0 P : E T A D 6 0 : 1 0 : 3 2 : E M I T

H C T I W S T T R O I P E B R E Y T D I L I B D A L R I A A V A C Y R L H E T N T O M S A M

5 0 / 2 0 / 8 0 : N E O T I A T D A N T A K N L N E P A M X B E E L L T A T N N E O O S S I A T E A R N E R M E I B T 9 M N 9 E W 9 T O 0 P D 0 E 0 S 0 0 : E 0 E M 9 T I A T : D R O O S T S E H C T E O N T R O A P M D

. T U O D E K C A B E R E W S E G N A H C . S N O I T A C I F I D O M M E T S Y S O T E U D S R O R R E Y E K

. E C N A N E T N I A M R O F E G A T U O D E L U D E H C S

% % 1 0 8 9 . . 9 9 9 9 0 0 Y T I L I B A L I Y A T V I A L I D B E A T S N 0 0 8 2 0 L U W E 0 0 3 6 0 I J O M . . . . . A D D I 0 0 9 0 0 V T 0 0 4 5 0 A A F 0 0 0 0 0 O % 1 0 4 0 0 0 1 0 2 : : E 0 0 4 4 0 1 M : : : : : 0 0 I 0 0 0 0 0 0 T 0 0 0 0 0

S

D

0 4 : 0 0

1 4 : 0 0 H T N O M 4 1 R : O 4 F 0 S L 5 A 0 T / O 5 T 1 / 6 0

0 0 : 7 1 5 0 / 7 1 / 6 0

. M A R G O R P E C A F R E T N I 0 0 2 I E H T O T N I S E G A S S E M E G A B R A G D E V I E C E R D E D O N

N O I T A N A L P X E N O S A E R

E M E D I M N E E T I O I M D T I D F E T N T E E E I I S W A R R L S T T U O E C A A U S L S G D P I W W D A A U U Y L D T E L T J A D T P R F H C O A P A O C N T : E A H S S U E M T I A T E D D O A H S D ? O C T H T E N T O A M D

. G N I D N O P S E R T O N

% 2 9 . 9 9 0

Y T I L I B N 0 0 0 0 0 A W E 0 0 0 0 0 L O M . . . . . I D I 0 0 0 0 0 A T 0 0 0 0 0 V F 1 0 0 0 0 A O % 5 0 0 0 0 5 E 3 0 0 0 0 3 M : : : : : : I 0 0 0 0 0 0 T 0 0 0 0 0 0

% 0 0 . 0 0 1 Y T I L I B A L I A V A D E T S U J D A 0 0 : 0 0

A

5 3 : 0 0 H T N O M 5 2 R : O 3 F 1 S L 5 A 0 T / O 6 T 0 / 5 0

D N E O I E I D F M T E E E I I A R R L S T E C A A U S P I W W D A L Y L D T E L A T P R F H C T P A O C N O A H S S U T

E M I T D E T S U J D A

E D O A H S D ? C

3 7 D H C W S


•

October 2006

3-127


Figure 3.60—SWCHD73 Monthly Availability Report (2 of 2) 5 0 0 9 / 2 0 E / G 8 A 0 P : E T A D 6 5 : 3 0 : 1 0 : E M I T

H C T I W S T T R O I P E B R E Y T D I L I B D A L R I A A V A C Y R L H E T N T O M S A M

5 0 / 2 0 / 8 0 : E N T O A I T D A T N N A E L K M P N E X A L E B T T L E N A S O N S O A I E T R A N E R M E I B T 9 M N 9 E W 9 T O 0 P D 0 E 0 S 0 0 : E 0 E M 9 T I A T : D R O O S T S E H C T E O N T R O A P M D

. E T O M E R T A M E L B O R P M E T S Y S . G N I D N O P S E R T O N

% 3 3 6 6 . . 9 9 9 9 0 0 Y T I L I B A L I Y A T V I A L I D B E A T N 0 0 0 0 0 0 L S W E 0 0 0 0 0 0 I U O M . . . . . . A J D I 0 0 0 0 0 0 V D T 0 0 0 0 0 0 A A F 0 0 0 0 0 1 O % 8 8 0 0 0 0 0 8 3 3 : E 0 0 0 0 0 3 : 2 M : : : : : : 2 I 0 0 0 0 0 2 0 0 T 0 0 0 0 0 0

P

8 3 : 2 0 H T N O M 2 0 R : O 1 F 1 S L 5 A 0 T / O 1 T 0 / 3 0

N O I T A N A L P X E

. . E E T T O O . M . . . M S E E E E E U R T T T R R O O O R T M M M T I A E E E A C R R R E E F C T T T C F N A A A N O A A N M M M N D E E E E E E T L L L T G N B B B N G I O O O I O A R R R A L M P P P M R M M M M M O E E E E E S T T T T T S S S S S S E Y Y Y Y Y C S S S S S O R . . . . P . G G G G G N N N N N I I I I . I D D D D N D N N N N W N O O O O O O P P P P D P S S S S S E E E E D E R R R R E R K T T T T R T O O O O A O N N N N M N

N O S A P P P D D D E R

E M E I M D E E T I N I M T O D F R I D T N I E I O T E S W T L S S T U O E P U S S L S G D P Y M D A E A U U Y R E E E L C T J A D T C N D H C O O A N I O C N R T : E E L M S U P E M T I A T E D D O E L M D ? P O C T H T E N T O A M D

% % 3 6 1 3 . . 8 9 9 9 0 0 Y T I L I B A L I Y A T V I A L I D B E N 0 0 0 2 0 8 A T W E 0 0 0 9 0 0 L S O M . . . . . . I U D I 0 0 0 5 0 4 A J T 0 0 0 6 0 3 V D F 0 0 0 0 0 0 A A O % 0 0 0 7 0 7 4 7 E 0 0 0 1 0 1 3 1 M : : : : : : : : I 0 0 0 8 0 4 2 4 T 0 0 0 0 0 0 1 0

3 2 2 5 7 5 1 1 5 3 1 2 : : : : : : 0 3 0 3 1 3 0 0 0 0 0 0 H T N O M 5 2 8 9 3 3 4 0 0 2 0 0 R : : : : : : O 3 0 5 0 0 0 F 0 1 1 1 1 1 S L 5 5 5 5 5 5 A 0 0 0 0 0 0 T / / / / / / O 6 2 8 5 8 1 T 2 2 1 1 0 0 / / / / / / 2 2 2 2 2 2 0 0 0 0 0 0

E D M E I N I E T O D F R M I E I O I D T L S S T E E P U S S T P Y M D A E L S Y R E E E L C A U T C N D H C O T J N I O C N R O D E L M S U P T A E D O E L M D ? P C

3 7 D H C W S

3-128

October 2006

•



Daily Cardholder Performance Report—SWCHD127-1 Purpose:

The MDS generates this report for each processor to assist in focusing on those card portfolios that do not meet product performance standards.

Description:

This report will display any debit or credit BIN with an approval rate below standard (currently set at 70%). Transaction counts and percentages by response code are reported in addition to the percentage of approved transactions. The report displays approval and denial rates that are percentages of total volume.

Frequency:

Daily

Availability:


Cardholder Processor Refer to Table 3.25 for a description of the SWCHD127-1 report fields. Table 3.25—SWCHD127-1 Fields Field

Description


PROCESSOR

The processor name.

PROCESSOR ID



CR/DB

This column indicates whether the BIN is a credit BIN or a debit BIN.

TOTAL VOLUME

This column represents the daily total transaction volume per BIN.

INVALID TRANS SELECTION (12, s12, 57)

The percentage of total transaction volume per BIN for these response codes

EXCEEDS USAGE (61)

The percentage of total transaction volume per BIN for this response code

INVALID PIN (55, 75)


BAD, HOT, EXPIRED ACCOUNT SELECTION (14, 41, 43, 54, 56, 62, 67)



•

October 2006

3-129


Field

Description

INSUFFICIENT FUNDS (51)


DO NOT HONOR (77)


OTHER (11, s11, 13, s13, s31, 76, s83, 85, s92)


PROCESSOR SYSTEM DENIALS (82, s91, 91)


TOTAL APPROVED (01, 78, 80, 81)


Category Fields—Display to the left of the page below the column he adings.

FINANCIAL IN#

The Routing and Transit number assigned to the Bank Identification Numbers (BINs).

TOTAL

The total items per category, according to the routing and transit, and percentage of total transactions

3-130

October 2006

•


Oct 2006


Daily Cardholder Performance Variance Report—SWCHD127-2 Purpose:

Issuers can use this report to identify problems with a particular BIN.

Description:

This report provides information on BINs with a variance of 10% higher or lower than its normal approval rate.

Frequency:

Daily

Availability:


Cardholder Processor Refer to Table 3.26 for a description of the SWCHD127-2 report fields. Table 3.26—SWCHD127-2 Fields Field

Description


PROCESSOR

The processor name.

PROCESSOR ID



BIN

Lists the BINs that exceed a variance parameter of 10%

APPROVAL RATE

Provides the BINs approval rate from totals reported on the Daily cardholder Performance Report (SWCHD127-1). The MDS calculates the approval rate based on response codes 01, 78, 79, 80, and 81 divided by the total volume.

AVERAGE APPROVAL RATE

Month-to-date average approval rate that is recalculated daily

VARIANCE

Difference between the approval rate and the average approval rate

Data Fields—Display to the left of the page below the Column headings.

FINANCIAL IN #

3-132

Routing and Transit number assigned to the Bank Identification Number (BIN).

October 2006

•


Oct 2006


Figure 3.62—SWCHD127-2 Daily Cardholder Performance Variance Report 5 1 0 / 5 0 / 7 E 0 G A F P O K R O W

T R O P E R E C N A H I C R T A I V W S E T C I N B A E M D R O D F R R A E C P R E R T E S D A L M O H D R A C 2 K 8 N 8 Y A 9 B 9 L 0 T 0 I S 0 E 0 A T 9 D : : D I R R O O S S S S E E C C O O R R 2 P P 7 2 1 D H C W S

E C N A I R A V E T A E R G A L R A E V V O A R P P A L A V E O T R A P R P A R E B M U N N I B -

3 4 . 1 2 -

3 4 . 8 2 -

0 0 . 0 0 1

0 0 . 0 0 1

7 5 . 8 7 2 1 2 3 4 5 6 7 8 1 # N I L A I C N A N I F

7 7 7 7 7 5


5 6 1 1 1 1 1 1 9 1 # N I L A I C N A N I F

•

7 5 . 1 7

5 6 5 6 1 5

9 0 2 2 2 2 2 2 9 1 # N I L A I C N A N I F

9 9 . 2 1 -

0 9 . 5 6 +

1 3 . 7 8

0 0 . 0

2 3 . 4 7

0 9 . 5 6

3 3 2 3 2 5

October 2006

7 6 3 3 3 3 3 3 9 1 # N I L A I C N A N I F

8 2 1 2 1 5

3-133


Maestro POS Daily Processing Summary—SWCHD143 Purpose:

Processors should use this report to monitor their performance rates to ensure that they comply with network standards. Processors can use this report to identify problems such as PIN failures, invalid account selection, format errors, and the need for increased cardholder education.

Description:

This report provides a month-to-date summary of the processor’s Maestro performance by response code and completion code. Only transactions with the MS product code are included. The MDS segregates this report into debit and credit activity based on the prefix (BIN) functionality as an acquirer and card processor.


Daily, with month-to-date totals Available through Global File Transfer and eService on MasterCard OnLine.

Acquiring Processor and Cardholder Processor Refer to Table 3.27 for a description of the SWCHD143 report fields. Table 3.27—SWCHD143 Fields Field

Description


PROCESSOR

The processor name.


The MDS generates separate reports for debit and credit activity. This heading displays at the top of the page beside the Processor name to identify the report.

PROCESSOR ID



DESCRIPTION

The explanation of transaction types by the Response Code and Completion Code. •

Transaction Approved

Transaction Not Approved – with Subtotal Each category will have a Subtotal providing total for trans counts and percentages. •

ADVICE REASON RESPONSE CODE

3-134

The number assigned to each transaction type description. The Response Code number assigned to each description. An (S) indicates that the MDS generated the response.

October 2006

•


Oct 2006


Field

Description

TRANS COUNT


% OF TOTAL

Percentage of total transactions by Response and Completion Code

STAND-IN COUNT

Number of transactions processed by MDS Stand-In.

TOTAL COUNT



TOTAL

The combined counts, percentages, and Stand In, for transactions approved and rejected.

TOTAL DEBIT/CREDIT

Total number of debit/credit transactions.

DEBIT FAIL % or CREDIT FAIL %

•

•

DEBIT/CREDIT FAIL %

•

•

SYSTEM DENIAL RATE FINANCIAL

The credit and debit fail percentages for acquiring processors are calculated as: [Format error (S30) + Invalid dollar amount (S13) + ATM proc or owning invalid (S92) + ATM processor inoperative (S80)] divided by [Total transaction count cardholder proc not found (S15)]. The credit and debit fail percentages for card processors are calculated as: [cardholder proc timeout (S91) + cardholder proc inoperative billable (S91) + cardholder proc inoperative non-billable (S91)] divided by [Total transaction count - cardholder proc non found (S15)]. The debit/credit fail percentage for acquiring processors is calculated as: [Format error (S30) + Invalid dollar amount (S13) + ATM proc or owning invalid (S92) + ATM processor inoperative (S80) {for both debit and credit}] divided by total debit/credit. The debit/credit fail percentage for card processors is calculated as: [cardholder proc timeout (S91) + cardholder proc inoperative billable (S91) + cardholder proc inoperative non-billable (S91) {for both debit and credit}] divided by total debit/credit.

Is calculated as: [Unable to process financial (82) + cardholder proc inoperative financial (91)] divided by [Total transaction count - cardholder proc inoperative inquiry (82) {for both debit and credit].


•

October 2006

3-135

Oct 2006


Figure 3.63—SWCHD143 Maestro POS Daily Processing Summary Report (1 of 4)—Acq. Processor 6 0 / 1 1 0 / 9 0 E G F A O P K R O W

H C T R I Y R O W A M S S M U S S E G T N C I I S O S B E R C E O P R D P Y L G I D A N D R I S A O R P C I O R R U T E S Q E T A C M S A A M

3 T R O 3 P 4 E 1 R D H C W S

3-136

T I B E D -


F L O A T % O T

6 6 0 0 . . 7 7 4 4

6 8 8 8 3 7 8 8 8 5 . . . . . 1 5 5 5 3 1 2

4 9 . 2 5

0 0 . 0 0 1

L T A N T U O O T C

8 8

2 1 1 1 4

9

7 1

F L O A T % O T

9 9 2 2 . . 5 5 3 3

6 0 8 8 0 7 0 8 8 0 . . . . . 1 0 5 5 0 1

3 5 . 3 2

2 8 . 8 5

6 6

2 0 1 1 0

4

0 1

F L O A T % O T

6 6 7 7 . . 1 1 1 1

0 8 0 0 3 0 8 0 0 5 . . . . . 0 5 0 0 3 2

1 4 . 9 2

8 1 . 1 4

S T N N A U R O T C

2 2

0 1 0 0 4

5

7




) 0 1 , 0 0 (

5 3 1 1 1 0 6 9 9 9 ) ) ) S S S ( ( (

L A T O T B U S D D E E V V O O R R P P P P A A N N O O I L I T A T C M C A R A S O S N N N A A R R T T

E K L C B O L A L A E L B I L L C B I N N A B I A L P N L N I I O F F B N O P P P N O O O O N N N I I I I T P C C C Y O O O R R R R R C P P P O E N D R R R O E E E H N D D D I L L L T O O O O R H H H N O D D D R R R R O R A A A D E C C C



Oct 2006

0 0 . 0

% L I A F T I B E D L A T O T

October 2006

•



Figure 3.65—SWCHD143 Maestro POS Daily Processing Summary Report (3 of 4)—Issuing Processor Oct 2006

6 0 / 1 3 0 / 9 0 E F G O A P K R O W

H C T I Y W R R A S M O M U S S S T G N E I I S C B S E O E C O R D R P P Y L D I G A R D N A S I O C P U R O S R E T S S T E I A S M A M

3 T R O 3 P 4 E 1 R D H C W S

3-138

F L O A T % O T

9 1 5 4 . . 2 7 9

0 0 . 0 0 1

0 0 . 0

0 0 . 0 0 1

L T A N T U O O T C

5 2 2

7 2

0

7 2

F L O A T % O T

0 0 0 0 . . 0 0

0 0 . 0

0 0 . 0

0 0 . 0

0 0

0

0

0

F L O A T % O T

9 1 5 4 . . 2 7 9

0 0 . 0 0 1

0 0 . 0

0 0 . 0 0 1

S T N N A U R O T C

5 2 2

7 2

0

7 2

N I T N D U N O A C T S T I B E D -




0 0 . 0

0 0 . 0

% L I A F T I B E D

L A I C N A N I F E T A R L A I N E D M E T S Y S

) 0 1 , 0 0 ( 0 0 0 0

A T A D D I D L E A V V O N R I P P D A E I N N O E I L D T A C M H A R C S O W N N S A R T

L A T O T B U S D E V O R P P A N O I T C A S N A R T



L A T O T

October 2006

•



Daily Processor Performance Report—SWCHD320-1 Purpose:


Description:

This report indicates a processor’s acquiring and issuing performance. It identifies processor level transaction volume, response time to authorization requests, and processor availability, on an hourly basis.

Frequency:

Daily

Availability:


Acquiring Processor and Issuing Processor Refer to Table 3.28 for a description of the SWCHD320-1 report fields. Table 3.28—SWCHD320-1 Fields Field

Description


PROCESSOR

The processor name.

PROCESSOR ID



TIME

The hour the statistics were collected

FINANCIAL TRANS

Total number of financial transactions per hour

INQUIRE TRANS

Total number of balance inquiry transactions per hour

FAILED

Total number of denied transactions per hour

TOTAL

The total number of transactions per hour (financial, inquiries, and denials)

PERCENT AVAILABLE

The percentage of time per hour that the processor is available

COUNT

The total transaction count per hour per category

RESP TIME

The average response time (in seconds) for the total transaction count for each hour

3-140

October 2006

•



Field

Description

Total Fields—Display at the bottom of each page.

TOTAL

Total number of transactions and average response time per category

PEAK MINUTE/ TRANSACTION

The minute the processor had the highest volume and the transaction count

PEAK HOUR/ TRANSACTION

The hour the processor has the highest volume and the transaction count

AVAILABILITY AVAILABILITY % LOW

The hour the processor has the lowest percent availability

AVAILABILITY AVAILABILITY % HIGH

The hour the processor has the highest percent availability


•

October 2006

3-141


Processor Peak Performance Report—SWCHD321 R eport—SWCHD321-1 -1 Purpose:

Description:

Processors can use this report to track performance trends and to plan possible corrective actions. This report shows the processor’s highest level of transaction volume for the day listed on the report. It identifies processor processor level transaction volume, response time to authorization requests, and processor availability, on an hourly basis. The report contains separate pages for the processor as acquirer and issuer.


Daily Available through through Global File Transfer Transfer and eService eService on MasterCard OnLine.


Description


PROCESSOR

The processor name.

PROCESSOR ID

The MDS-assigned processor/member processor/member identification number.


TIME

The hour the statistics were collected.

FINANCIAL TRANS

Total number of financial transactions per hour.

COUNT

The total transaction count per hour per category.

RESP TIME

The average response time (in seconds) for the total transaction count for each hour.

INQUIRE TRANS

Total number of balance inquiry transactions per hour.

COUNT


RESP TIME


FAILED TRANS COUNT

Total number of denied transactions per hour.

TOTAL TRANSACTIONS

The total transaction per hour (financial, inquiries and denials).

COUNT


RESP TIME


3-144

October 2006

•



Field

PERCENT AVAILABLE AVAILABLE

Description

The percentage of time per hour that the processor is available.

Total Fields – Display at the bottom of each page




The hour the processor has the highest volume and the transaction count.

AVAILABILITY AVAILABILITY % LOW

The hour the processor has the lowest percent availability.

AVAILABILITY AVAILABILITY % HIGH

The hour the processor has the highest percent availability.


•

October 2006

3-145


Processor Daily Summary Performance Report—SWCHD321-2 Purpose:

Description:

Processors can use this report to track performance trends and to plan possible corrective actions. This report shows the processor’s highest level of transaction volume for the day listed on the report. It identifies processor level transaction volume, response time to authorization requests, and processor availability, on an hourly basis. This report combines acquirer and issuer transaction activity.




Description


PROCESSOR

The processor name.

PROCESSOR ID



TIME

The hour the statistics were collected

FINANCIAL TRANS

Total number of financial transactions per hour

COUNT


RESP TIME


INQUIRE TRANS

Total number of balance inquiry transactions per hour

COUNT


RESP TIME


FAILED TRANS COUNT

Total number of denied transactions per hour

TOTAL TRANSACTIONS

The total transaction per hour (financial, inquiries, and denials)

COUNT


RESP TIME


3-148

October 2006

•



Field

PERCENT AVAILABLE

Description

The percentage of time per hour that the processor is available

Total Fields—Display at the bottom of each page.




The hour the processor has the highest volume and the transaction count

AVAILABILITY % LOW

The hour the processor has the lowest percent availability

AVAILABILITY % HIGH

The hour the processor has the highest percent availability

PEAK PROCESSOR CAPACITY UTILIZATION

The utilization is computed by estimating the peak transactions per hour that a processor can perform, based on that processor’s network configuration and calculating the actual peak hour transactions against the value for a percentage used during that hour.


•

October 2006

3-149


Transaction Interchange Month-to-Date—SWCHM03 Purpose:

The acquiring report reflects the types of transactions other cardholders performed at the processor’s terminals. The cardholder report reflects the types of transactions that the processor’s cardholders performed at other processor’s terminals. (This may be helpful for marketing analysis.)

Description:

This report provides summary information on the number of transactions interchanged with other processors connected to the MDS by product. The MDS produces this report daily with month-to-date totals. The report lists the processors on the left side in processor number order.



Acquiring Processor and Cardholder Processor Refer to Table 3.31 for a description of the SWCHM03 report fields. Table 3.31—SWCHM03 Fields Field

Description


PROCESSOR

The processor name.

PROCESSOR ID


Fields—Display to the left of the page.

DDA W/D

Cash withdrawal from a demand deposit account (DDA) or checking account

SAV W/D

Cash withdrawal from savings

CCD W/D

Cash advance from credit card

NO ACCT

Cash withdrawal—No Account Specified. The issuer will determine which account to debit.

TRANSFERS

Funds transferred between checking (DDA) and savings (SAV).

INQUIRY

Account balance transactions

REVERSAL

List of exception items processed through MDS

DENIED

Includes all transactions denied by the issuer or the MDS


•

October 2006

3-151


Field

Description

FOREIGN CARDS

All transactions that are routed to the MDS, but do not participate in the products supported by the MDS

PUR C/B

POS purchase with cash back

PUR SCRIP

Purchases made with a voucher dispensed by a scrip terminal (POS only)

PUR

Purchases made at a POS terminal

CORRECTION

Transactions that correct an error that the merchant discovers after the cardholder has left the Point-of-Sale device

LOAD

Load cash onto Mondex ® chip card

UNLOAD

Unload cash from Mondex ® chip card

RISK M

Risk Management transaction for the Mondex chip card

3-152

October 2006

•



Month-to-Date Processing Summary Report—SWCHM06 Purpose:

Processors should use this report to monitor their performance rates to ensure that they comply with network standards and to highlight the differences in debit and credit performance. Processors can use this report to identify problems such as PIN failures, invalid account selection, format errors, and the need for increased cardholder education.

Description:

This report provides a month-to-date summary of the processor’s performance by response code and completion code. This report lists a count of stand-in transactions that occurred at the time of MDS Stand-In processing support by transaction type. The MDS segregates this report into debit and credit activity based on the prefix (BIN) functionality as an acquirer and card processor.


Daily with month-to-date totals Available through Global File Transfer and eService on MasterCard OnLine.

Acquiring Processor and Cardholder Processor Refer to Table 3.32 for a description of the SWCHM06 report fields. Table 3.32—SWCHM06 Fields Field

Description


PROCESSOR

The processor name.


The MDS generates separate reports for debit and credit activity. This heading displays at the top of the page beside Processor name to identify the report.

PROCESSOR ID



DESCRIPTION

The explanation of transaction types by the Response Code and Completion Code. Transaction Approved

•

Transaction Not Approved – with Subtotal Each category will have a Subtotal providing total for trans counts and percentages. •

ADVICE REASON

The number assigned to each transaction type description.


•

October 2006

3-155


Field

Description

RESPONSE CODE

The Response Code number assigned to each description. An (S) indicates that the MDS generated the response.

TRANS COUNT


% OF TOTAL

Percentage of total transactions by Response and Completion Code

STAND-IN COUNT

Number of transactions processed by MDS Stand-In.

TOTAL COUNT



TOTAL

The combined counts, percentages, and Stand In, for transactions approved and rejected.

TOTAL DEBIT/CREDIT Total number of debit/credit transactions. DEBIT FAIL % or CREDIT FAIL %

•

•

DEBIT/CREDIT FAIL %

•

•

MASTERCARD DEBIT TRANSACTIONS

The credit and debit fail percentages for acquiring processors are calculated as: [Format error (S30) + Invalid dollar amount (S13) + ATM proc or owning invalid (S92) + ATM processor inoperative (S80)] divided by [Total transaction count - cardholder proc not found (S15)]. The credit and debit fail percentages for card processors are calculated as: [cardholder proc timeout (S91) + cardholder proc inoperative billable (S91) + cardholder proc inoperative non-billable (S91)] divided by [Total transaction count - cardholder proc non found (S15)]. The debit/credit fail percentage for acquiring processors is calculated as: [Format error (S30) + Invalid dollar amount (S13) + ATM proc or owning invalid (S92) + ATM processor inoperative (S80) {for both debit and credit}] divided by total debit/credit. The debit/credit fail percentage for card processors is calculated as: [cardholder proc timeout (S91) + cardholder proc inoperative billable (S91) + cardholder proc inoperative non-billable (S91) {for both debit and credit}] divided by total debit/credit.

This is the count total of MasterCard debit transactions. These numbers are not included in the report computations.

SYSTEM DENIAL RATE Is calculated as: [Unable to process financial (96) + cardholder proc inoperative FINANCIAL financial (91)] divided by [Total transaction count - cardholder proc inoperative inquiry (96) {for both debit and credit].

3-156

October 2006

•



Month-to-Date Denial Summary Report—SWCHM07 Purpose:

Processors use this report to evaluate performance.

Description:

This report is a summary of all the denial response codes issued to the issuing processor. In each column listed across the top of the report is the number of transactions and percentages to correspond with each response code. (The report separates them in Debit, Credit, and Total.) This report accumulates totals to date on a daily basis.




Note


This report only logs the transaction detail for the issuing processor.

Issuer Refer to Table 3.33 for a description of the SWCHM07 report fields. Table 3.33—SWCHM07 Fields Field

Description


PROCESSOR

The processor name.

PROCESSOR ID


Data Fields—Display to the left of the page.

TOTAL CARDHOLDER FAILURES

Includes timeouts and inoperative (S91) responses.

TOTAL TERMINAL PROCESSOR FAILURES

These totals reflect the processor’s cardholders at other network processors Terminals. Includes format errors (30, S30, 92, S92) and inoperative (S80).

TOTAL FAILURES

This represents a sub-total of transactions for Total Cardholder Failures and Total Terminal processor Failures.


•

October 2006

3-161


Field

Description

TOTAL SYSTEMATIC PROCESSOR DENIALS

Includes Inoperative (91), and Unable to Process (96).

TOTAL POLICY PROCESSOR DENIALS

It is the sum of transactions with the following Response Codes: •

Invalid Transaction Selection (12, S12, 57, 58)

•

Invalid Dollar Amount (13, S13)

•

Exceeds Withdrawal Limit (61)

•

Invalid PIN (55, 75)

•

Bad Account Selection (14, 78)

•

Hot Account (41, 43, 62, 04)

•

Expired Card (54)

•

Insufficient Funds (51)

•

Invalid Interchange

•

Do Not Honor (01, 05)

TOTAL DENIALS

A subtotal transaction count and percent by debit and credit, and a combined total for systematic processor denials and policy processor denials.

TOTAL TURNDOWNS

A subtotal of transaction count and percent by debit and credit, and a combined total for cardholder failures, terminal processor failures, systematic processor denials, and policy processor denials.

TOTAL APPROVED TRANSACTIONS

This total represents a sum of all approved transactions including: financials, balances, and address verifications. •

Transactions Approved (00)

•

Balance Inquiries (00)

•

TOTAL TRANSACTIONS

3-162

AVS/EC Certificate Auth Approval (85)

The total number of all transactions for the month to date. Including all declined and approved transaction counts and percent by, debit and credit, and a combined total.

October 2006

•


Reports ISIS Reports

ISIS Reports ISIS supports the settlement of local transactions submitted in currencies other than U.S. dollars. It also supports intra-currency settlement. It enables participating members to establish unique interchange fees for their intracurrency arrangement transactions and to operate on their own holiday schedule.

Oct 2006

ISIS transactions are displayed on the reports in the designated currency of the ISIS agreement. The SWCHD363 Daily Control Report will detail each ISIS settlement currency supported within a processor. ISIS Agreement detail, settlement service information, settlement currency and country information are reported to further define ISIS financial and interchange totals. Refer to Table 3.5 for a description of the SWCHD363 report fields. Report samples follow the table. The SWCHD412 Daily Interchange Report will also detail interchange information for each ISIS processor by the designated settlement currency. Detail transaction interchange counts and amounts will be reported on the SWCHD412 report. Refer to Table 3.6 for a description of the SWCH412 report fields. Report samples follow the table. Related ISIS reports are detailed in Table 3.34. These reports enable members to research, identify and reconcile; transactions, fees, and their net settlement as reported in their 1740 IPM settlement record. ISIS transactions are identified by the PROD TYPE field on the report. The third position of this field will contain a 2 to uniquely identify the ISIS transactions. Table 3.34—ISIS Related Reports

3-164

Report Number

Name

Purpose

SWCHD53

Exception Audit

Processors use this report to ensure the MDS has processed all exception items and to track incoming and outgoing exception items for the processor. Processors should use the report to initiate the research for representments and to monitor for excessive chargebacks that could be subject to sanction.

October 2006

•


Oct 2006

Reports ISIS Reports

Report Number

Name

Purpose

SWCHD55

Detailed Suspect Items

Processors should use this enriched report to determine why a transaction failed. This report can assist in the reconciliation process by identifying the differences between the processor’s internal reports and the MDS reports.

SWCHD57, SWCHD108

Transaction Audit Reports

With MDS Release 06.3, MasterCard will no longer send the Transaction Audit Reports—SWCHD57 and SWCHD108 to members. These reports are obsolete and will not be updated or modified in future releases. Members may use the 250-byte Batch Data File as an alternate reference to locate information that was previously found in the Transaction Audit Reports. To allow more time to convert to the 250-byte Batch Data File format, members may request to continue to receive uninterrupted delivery of these reports through 3 April 2007.

These reports are obsolete but can be requested until April 2007.



Note

SWCHD118

Retrieval Request Fulfillment

Debit MasterCard processors can use this report to track and monitor retrievals, and to ensure that acquirers have processed and fulfilled retrievals.

SWCHD144

Maestro POS Transaction Audit

For issuers, the report sequence provides tracking capabilities and session reporting analysis. For acquirers, the report sequence enables processors with multiple corresponding members to review transactions by Institution and Term ID.

Full descriptions of these reports and report examples are found in the Detail Activity Reports section of this manual.


•

October 2006

3-165

Oct 2006

Reports Stand-In Reports

Stand-In Reports Stand-In reports assist processors in monitoring their system’s percentage of availability, withdrawal limits, usage counts, and card statuses for all transactions the MDS routed to Debit Stand-In during periods the processor was unavailable. There are two types of Stand-In reports: •

NICS Database File reports —These reports provide the status information of

the VIP Card file and the Hot Card file records. −

−

•

VIP is any MasterCard® Card selected by the member to receive higher withdrawal limits and usage counts for the individual VIP accounts during Stand-In activity. They are listed in the Account File with an entry reason code of V. A Hot Card is a card being used on an account on which excessive purchasing is taking place. This may indicate a lost or stolen card or other unauthorized purchasing.

Stand-In Transaction report—SWCHD149 —This report provides the details of

financial transaction activity during Stand-In processing. It is documented on the following pages.

Related Reports Additional Stand-In information may be present within other reports. Stand-In transactions are identified by STND in the RESP Code field on the related report. Table 3.35—Stand-In Related Reports

Number

SWCHD53

3-166

Name

Manual Section

Purpose

Exception Processors use this reports to ensure Audit Report the MDS has processed all exception items and to track incoming and outgoing exception items for the processor. Processors should use the report to initiate the research for representments and to monitor for excessive chargebacks that could be subject to sanction.

October 2006

•

Detail Activity Reports


Oct 2006


Manual Section

Number

Name

Purpose

SWCHD61

Daily Processing Summary


SWCHD147-1

Negative File This report gives members Updates the ability to track changes made to the MDS Stand-In Negative Card file.


SWCHD147-2

VIP File Updates


This report gives members the ability to track changes made to the MDS Stand-In VIP file.

SWCHD149

Stand-In For issuers, the report provides Transaction tracking capabilities for all Audit Report transactions that the MDS routed to Debit Stand-In during periods the processor was unavailable

SWCHM06

Month-to-Date Processors should use this report to Statistical Processing monitor their performance rates to Reports Summary ensure that they comply with Report network standards and to highlight the differences in debit and credit performance. Processors can use this report to identify problems such as PIN failures, invalid account selection, format errors, and the need for increased cardholder education.


•

October 2006

Oct 2006

Statistical Reports

Stand-In Reports

3-167


Stand-In Transaction Audit Report—SWCHD149 Purpose:

For issuers, the report provides tracking capabilities for all transactions that the MDS routed to Debit Stand-In during periods the processor was unavailable.

Description:

This is a two-line report used by switch time (SWCH TIME) order. It details all the financial transactions that were processed in debit Stand-In. These transactions may be approved or declined depending on the disposition of the transaction indicated by the response code.

Frequency:

Daily

Availability:



ISO DE Description


PROCESSOR

The processor name.

PROCESSOR ID


Column Headings—Display across the top of the page. Data related to these headings display first for each transaction.

REC DATE

7


SWCH TIME

7

The time the transaction was processed on the MDS system.

SWCH SERIAL

63

The unique number assigned by the MDS to each transaction processed in the system.

43


PROC CODE

3

The Processing Code describes the effect of a transaction on a cardholder account, and the account type affected.

TRACE NO.

11


REF NO.

37


43

The physical location of the ATM or POS terminal.

2


ACQ NAME

ACQ LOCATION PAN

3-168

October 2006

•



Field

TERM ID

ISO DE Description

41


ADV REASON

60

The Advice Reason Code indicates the specific purpose of an advice message.

CASH BACK

54

Provides the cash back amount information on a purchase transaction. This field will be reported in the acquirer processor’s settlement currency for the acquirer, and the issuer processor’s settlement currency for the issuer.

ACCESS INT

28

An additional fee or a surcharge to an ATM transaction. This field will be reported in the acquirer processor’s settlement currency for the acquirer, and the issuer processor’s settlement currency for the issuer. The acquirer must clearly present the surcharge amount to the cardholder before completing the transaction.

ISS INST

mx

The Card processor’s Routing and Transit (ABA number.) This number identifies the card processor to the MDS.

ACQ INST

32

The acquirer processor’s Routing and Transit Number (ABA number). This number identifies the acquirer to the MDS. It can identify either an ATM or POS processor.

PRODUCT

63


Valid interchange rate codes are: 0 U.S. and Canada Regions 1 Asia Pacific, Europe, Latin America and Middle East/Africa Regions 2 Intracountry (ISIS) format Only products with activity display on the report. CC TRAN

49

The ISO assigned currency code. It indicates the local currency used at the terminal.

CC STL

NA

The ISO assigned settlement currency.

CONV RT

9

Currency Conversion rate used to convert local currency to issuer processor settlement currency amount. The MDS does not provide this information for balance inquiry transactions.

CMP LOCAL

4



•

October 2006

3-169

Oct 2006


Field

CMP SETL

ISO DE Description

5

The completed amount in the settlement currency. The amount of funds to be transferred between acquirer and issuer processor.

COMPLETED

MX

Completed amount in the settlement currency of the acquirer processor for the acquirer, and the settlement currency of the issuer processor for the issuer.

INT

29

The Interchange Fee is the transferred fee between acquiring and issuer processor in the settlement currency of the acquirer processor for the acquirer, and the settlement currency of the issuer processor for the issuer.

RESP

39

The Response Code defines the disposition of a message. Refer to the MDS Online Specifications manual for additional information about response codes.

3-170

October 2006

•



Figure 3.79—SWCHD149 Stand-in Transaction Audit Report—Issuing Processor 5 1 0 / 8 1 / 7 0 E : G E A T P A D T N E M E L T T E S

T R O P E R H C T T I I D R W U O S A S T S I N E B O C E I O D T R C P D A R S G A N N C A I R R U E T S T S S N I A I M D N R A O S T S E 1 S C 2 O 1 R 2 P 1 0 T 0 S 0 E 0 T 9 : : D I R R O O S S S S E E C C O O R R P P 9 4 1 D H C W S

D D D D D - S T 0 5 0 5 0 D - S N 0 2 0 2 0 5 - E I . . . . . 2 . - C 1 1 1 - C - A - D K 0 0 0 0 0 0 - E C 0 0 0 - T A . . . S E B 0 0 0 T L 2 2 0 N P H 2 U M S O O A M C C A - L D D D - A L 0 5 0 5 0 5 - C T 0 2 0 2 0 2 - O E 0 . 0 . 0 . - L S 2 1 2 1 0 1 2 2 2 0 - P P 2 - M M - C C 0 0 0 T T 0 0 0 C R 0 0 0 U 1 0 1 0 1 0 D V C 0 C 0 C 0 O N M 0 M 0 M 0 R O 1 1 1 P C 1 1 1 N L 0 0 0 0 0 0 C R T 4 4 4 4 4 4 C T S 8 8 8 8 8 8 T T 0 8 0 8 0 8 S S 0 0 0 0 0 0 N N 6 1 6 1 6 1 I I 0 1 0 1 0 1 1 1 1 1 1 1 S Q 6 1 6 1 6 1 S C 0 1 0 1 0 1 I A 1 1 1 1 1 1 0 0 0 0 0 0 Q N 1 1 1 C S 1 1 1 A R 1 1 1 P V S D 0 0 0 E A 0 0 0 R 9 9 9 0 0 0 D 0 0 0 I 0 0 0 0 D 0 D 0 D M 1 G 1 G 1 G R 1 1 1 1 1 1 E 1 1 1 1 1 1 T 1 1 1 1 1 1 1 1 1 1 I 1 I 1 I 4 M 4 M 4 M 0 0 0 1 1 1 4 4 4 5 5 5 N 0 0 0 A 0 0 0 P C 0 T 0 T 0 T O I I I . L 3 O 7 O 5 O O 0 R 0 R 0 R N Q 0 T 0 T 0 T C 5 E 0 E 5 E F A 0 D 1 D 9 D E 8 8 7 R 0 0 0 0 0 0 E 9 1 3 C . 2 3 3 A O 0 0 0 R N 0 0 0 T 0 0 0 0 H 0 H 0 H S S S C E 0 E 0 E 0 E O D 0 N 0 N 0 N R O 0 I 0 I 0 I P C 1 H 1 H 1 H E 1 D 1 D 1 D M 0 0 0 A N 9 9 9 L 4 K 4 K 4 K H A Q 0 N 0 N 0 N C I C 0 A 5 A 5 A W R A 2 B 2 B 0 B S E 3 2 2 S 2 S 3 S 4 S E 0 U 0 U 0 U M 4 4 4 I T 8 3 8 7 8 9 E 1 4 1 5 1 3 C T H / 0 / 3 / 0 E A C 7 1 7 1 7 2 R D W 0 2 0 2 0 2 S 0 0 0


•

October 2006

3-171

Reports Processor Availability Reports

Processor Availability Reports The MDS creates a series of daily reports (based on Issuer transactions) and that are indexed by Processor number. The four reports available to members (through eService) showing processor availability are: •

MS1100BB—Daily Processor Up Time Report (Settlement Date)

•

MS1100DD—Daily Processor Up Time Report (Calendar Date)

•

MS1101AA—Monthly Processor Up Time Report

•

MS1101BB—Month To Date Report

Refer to Table 3.37—Processor Availability Reports Fields for a description of the report fields for these reports. The field descriptions are the same for all four reports. Table 3.37—Processor Availability Reports Fields Field

Description

Header Fields—Display at the top of all pages of the report.

PROCESS DATE WORK OF:

The date that the report was created. The date/time period that covers the reported information.

PROCESSOR:

The processor name.

PROCESSOR ID:


PROCESSOR COUNTRY:

The country where the processor is located.

PROCESSOR REGION:

The numeric region code assigned per the Processor Quick Reference Booklet.

BUSINESS ENTITY:

The name of the business entity that the Processor Number is associated with. A single business entity can have several different Processor Names and Numbers associated with it.

Column Headings—Display across the top of the page

APPROVED TRANSACTIONS:

The number of approved transactions during that hour that were logged by the MDS.

DENIED TRANSACTIONS:

The number of rejected transactions during that hour that were logged by the MDS.

COMM RELATED TIME-OUTS:

Transactions that were identified by the MDS as network errors.

3-172

October 2006

•



Field

Description

NON-COMM RELATED TIME-OUTS:

Transactions that were identified by the MDS that had a Response Code of 91, 91(s), or 96.

TOTAL TRANSACTIONS

The total count of approved, denied, Comm Related, and Non-Comm Related Transactions.

STAND-IN TRANSACTIONS:

The total number of Stand-In transactions.

UP TIME PERCENTAGE:

The formula for this field is: Total Transactions – Non-Comm Related Time Outs/Total Transactions.

DOWN TIME PERCENTAGE

The formula for this field is: 1.0 – Up Time Percentage.

Total Field—Displays at the bottom of the page.

Total



The complete totals for each column.

Note

Total line is the same as above except it uses the complete totals for each column.


•

October 2006

3-173


Daily Processor Up Time Report (Settlement Date)—MS1100BB Purpose:

The MDS generates this report on a daily basis for all issuing processors. The report displays processor activity by settlement cut-off time, broken down by hour and settlement date.

Description:

This report provides summary availability data for each hour of that settlement period. If a processor settles at 15:00 (CT) daily, then the details are from 15:00 (CT) of the first day until 14:00 (CT) of the next day. The report displays the date that the MDS job processed (Process Date) and the date of the data/work that was processed (Work of). This is displayed in the MM/DD/YYYY format. Since the data covers a 24 hour period, the report is broken down to cover the starting and ending dates for the data. The top section of the report describes: Who the processor is The Processor ID (processor number) The Processor Country The Processor Region The Business Entity that the processor is associated with • • • • •

The next section identifies the: Number of Approved Transactions Denied Transactions Comm Related Time-outs (network communication errors) Non-Comm Related Time-outs (RC 91, RC91(s) and RC96 errors) Total Transaction Stand-In Transactions Up Time Percentage Down Time Percentage. • • • •

• • • •

The last line is a total of all of the transactions for the 24 hour period displayed and the calculated percentages for the UP and Down times. Frequency: Availability:

Daily Available only through eService on MasterCard OnLine.

Refer to Table 3.37—Processor Availability Reports Fields for a description of the MS1100BB report fields.

3-174

October 2006

•



Daily Processor Up Time Report (Calendar Date)—MS1100DD Purpose:

The MDS generates this report on a daily basis for all issuing processors. The report displays a processor’s activity for a 24hour period, broken down by hour and calendar date.

Description:

This report provides summary availability data, by hour, for the 24-hour calendar date. The report displays the date that the MDS job processed (Process Date) and the date of the data/work that was processed (Work of). This is displayed in the MM/DD/YYYY format. The top section of the report describes: • • • • •

Who the processor is The Processor ID (processor number) The Processor Country The Processor Region The Business Entity that the processor is associated with

The next section identifies the: • • • •

• • • •

Number of Approved Transactions Denied Transactions Comm Related Time-outs (network communication errors) Non-Comm Related Time-outs (RC 91, RC91(s) and RC96 errors) Total Transaction Stand-In Transactions Up Time Percentage Down Time Percentage



Refer to Table 3.37—Processor Availability Reports Fields for a description of the MS1100DD report fields.


•

October 2006

3-177


Monthly Processor Up Time Report —MS1101AA Purpose:

The MDS generates this report on a monthly basis for all issuing processors. The report displays monthly totals by each processor, broken down by hour and calendar date for the complete month.

Description:

This report provides monthly summary availability data, by hour, for the 24-hour calendar date period. The report displays the date that the MDS job processed (Process Date) and the date of the data/work that was processed (Work of). This is displayed in the MM/YYYY format. The top section of the report describes: • • • • •



• • • •

Number of Approved Transactions Denied Transactions Comm Related Time-outs (network communication errors) Non-Comm Related Time-outs (RC 91, RC91(s) and RC96 errors) Total Transaction Stand-In Transactions Up Time Percentage Down Time Percentage.


Monthly – run on the second day of the month. Available only through eService on MasterCard OnLine.

Refer to Table 3.37—Processor Availability Reports Fields for a description of the MS1101AA report fields.


•

October 2006

3-179


Month-to-Date Report—MS1101BB Purpose:

The MDS generates this report on a daily basis for all issuing processors. The report displays month-to-date totals, broken down by hour and calendar date from the first day of the month to current “Work Of” date.

Description:

This report provides month-to-date summary availability data, by hour, for the 24-hour calendar date period. The report displays the date that the MDS job processed (Process Date) and the date of the data/work that was processed (Work of). This is displayed in the MM/YYYY format. The top section of the report describes: • • • • •



• • • •

Number of Approved Transactions Denied Transactions Comm Related Time-outs (network communication errors) Non-Comm Releated Time-outs (RC 91, RC91(s) and RC96 errors) Total Transaction Stand-In Transactions Up Time Percentage Down Time Percentage.



Refer to Table 3.37—Processor Availability Reports Fields for a description of the MS1101BB report fields.



Note

The month-end version of this report is the MS1101AA.


•

October 2006

3-181

Settlement

Recommend Documents