1 of 23

Spring Mandate 2011 - Updated

** As a result of the Mandate Q&A Sessions held last week, this documentation has been

updated to clarify any questions and to provide additional information. Changes have been

highlighted to assist in identifying the updates.

CO-OP Financial Services will implement the code changes required to support card association and EFT

network Spring Mandates on Friday, April 15, 2011. The changes identified in this update go into effect

on April 15, 2011 unless otherwise noted.

CO-OP has identified requirements that may impact your host processor. The requirements in support of

these mandates are detailed in this update. While CO-OP forwards copies of our Hardware/Software

Compliance Updates to our known software vendor contacts, it is up to each credit union to check with

their software vendor to make sure their vendor has the information needed to support these changes. If

a 3rd party authorizes transactions on your behalf, often referred to as a service bureau, you should

forward this information to your service bureau provider.

Please note: DataNavigator will be taken offline at 7 p.m. PT on April 15, 2011, to install the

code changes required to support the mandates. DataNavigator will be unavailable for

approximately 2 hours.

In an effort to make it easier to identify changes and assess the impact to your credit union, a summary

of changes by network is detailed starting on page 2.

In some cases, card logos can help clarify network participation. Questions regarding your credit union

network participation should be verified with the sponsorship or contracts administrator within your

organization. A quick way to check which network changes impact your credit union would be to look at

both your ATM and Debit cards to see which card association and network logos appear on them. The

logos for the networks on your cards would require you review the Issuer changes for each of those

networks. The logos for the networks on your ATMS would require you review Acquirer changes for each

of those networks. If you support both an ATM and a debit card, look to the ATM card to determine

whether or not you are a card Issuer in the Cirrus (MasterCard) or Plus (Visa) network.

Some credit unions may have issued a Debit MasterCard with Plus sponsorship or a Visa Debit card with

Cirrus sponsorship. In these cases, both the MasterCard and Visa changes would apply.

The changes dictated by the card associations and EFT Networks are required to remain in compliance

with each of the networks. The dates for compliance have been set by each card association or network.

Associations rarely offer waivers to mandates so you should pursue these changes with your vendor as

quickly as possible.

If you have any questions please contact Client Services at 800.782.9042, option 2.

Page 2 of 23

Summary by Association/Network CO-OP Network

Software Vendor Audit and Non-Disclosure Follow-up (page 3)

o Applies to all CO-OP Network members

Pulse: New Pulse Fee Reports (page 3)

o Informational for all Pulse participants

(Effective April 4, 2011)

Enhanced Data File (page 3)

o Informational for all Pulse participants

(Effective October 2011)

MasterCard: Account Status Inquiry Service (page 4)

o Required for Maestro and Debit MasterCard

Remote Mobile Payments (pages 4-5)

(Effective June 14, 2011)

o Point of Service Entry Mode

Required for all Issuers

o Remote Payments Program Type Indicator

Required for Mobile Remote Payment Service Participants

o New Device Type Indicators

Required for PayPass Participants

Partial Approval Enhancement (page 5-6)

o Informational Maestro and Debit MasterCard

Revised Test Transactions for Recurring Payment Merchants (page 6)

o Informational Maestro and Debit MasterCard

Visa: Changes to Account Funding Transactions (AFT) (page 6)

o Required for signature debit

New Business Application Identifiers - Visa OCT Transactions (page 6-7)

o Required for signature debit

ISO 8583 Processor Interface Specifications Settlement (page 8)

CO-OP ISO User File Layout Record 9

o Required for Visa AFT

Batching Services (pages 9-11)

Network Addendum Record Layout o Optional for offline Visa signature debit

ISO 8583 Data Element Definitions (pages 12 - 23)

Page 3 of 23

CO-OP Network Software Vendor Review (Informational for all CO-OP Network members and processing clients)

CO-OP Financial Services requires all software vendors to complete a Non-Disclosure Agreement so we

can provide information directly to them with regards to the CO-OP ISO 8583 Specification Manual and

related mandate documentation. CO-OP will be performing an audit of all software vendors on record

and reviewing our executed Non-Disclosure Agreements to ensure our records are up to date.

We encourage our member credit unions to request their software vendors complete the Non-Disclosure

should we need to update our records. The audit will be performed later this month.

For a copy of the Non-disclosure please send an email request to systemsandsupport@co-opfs.org.

Pulse

New Fee Reports (Informational for all Pulse Participants)

Effective April 4, 2011, Pulse is changing the format of their daily and end of month fee reports. Pulse

reports will continue to be received as they are today. The new report IDs are:

DAILY and MONTHLY INSTITUTION FEE SETTLEMENT – Report ID: F0005-RP01

These new report IDs replace the existing reports which are:

INSTITUTION FEE SETTLEMENT REPORT - Report ID: EFFP0130-RP01

If you scrape this report to extract information or upload this report into an internal archive system, be

sure to let the appropriate team members know about the report ID changes as these may require

changes and/or enhancements to your process.

Sample reports are available by following the hyperlink provided in the 2011 Spring Mandate notice.

PULSE has confirmed that there will be no changes to the International Processing Fee Report (PLSIPFR2-

RP01) however; we are still waiting for confirmation that there will be no changes made to the Processor

Fee Summary Report (EFFP0130-RP02). Information will be provided once Pulse has provided confirmation. Enhanced Data File (Required effective October 2011)

PULSE plans to introduce an enhanced funds settlement data file in April 2011. This file will replace the

current funds settlement data file in production today. This file will contain detailed information at the

transaction level matching back to the daily and monthly reports, as well as additional data elements

from the online authorization message.

Although it will be available in production starting in April 2011, the new settlement data file format will

not become mandatory until the settlement system component of the new Pulse Integrated Processing

Platform is launched in October 2011.

This file format is currently under review to determine what if any impact the file will have on the current

settlement process. Further details will be provided as they become available.

Page 4 of 23

MasterCard

MasterCard is changing the name of their MDS system to MasterCard Single Message System and

updating some processor level processing and reporting. The MDS system processes Cirrus and Maestro

transactions. We do not expect any processing impacts as a result of the changes being implemented by

MasterCard.

Account Status Inquiry Service (Applies to Maestro and MasterCard Signature Debit)

MasterCard is implementing functionality to support a new Account Status Inquiry Service that allows

Acquirers to send Account Status Inquiry transactions to validate aspects of a members account.

For software vendor coding purposes, the MasterCard approach is similar to the approach Visa has in

place today. The characteristics of the Account Status Inquiry are:

Message level 0100/0200

Process code is 000000

Transaction amount $0.00

Transaction is a verification only, no completion follows this status verification request

May contain request for AVS or CVV2 validation in DE 123

Will NOT apply to transactions with Merchant Category Code (MCC) 5542 or aggregated

MasterCard Paypass transit transactions.

The MasterCard Account Status Inquiry is a 0100/0200 level message, process code 000000 and

MasterCard will now allow a zero transaction amount in these messages. The Account Status message

will contain a new POS Transaction Status. The POS Transaction Status will be located in Data element

(DE) 111, Subelement 15, value “8” in the “MD” tag which is used for Maestro and in (DE) 111,

Subelement 19 in the “MC” tag which is used for Debit MasterCard.

MasterCard hopes that the use of the new Account Status message will eliminate the unnecessary holds

that the $1.00 Account Check places on members’ accounts for recurring payments when the Account

Check is being used solely to verify an account and is not followed by a subsequent settled amount.

Mobile Remote Payments (Required and Optional - applies to Maestro and Debit MasterCard participants) Maestro and Signature debit authorization support effective June 14, 2011 Debit MasterCard completion support effective April 15, 2011

Credit unions participating in MasterCard Remote Payment Service must support all of the following

changes; however all Issuers must support the new PAN entry mode value.

Point of Service Entry Mode: (Applies to all Maestro and Debit MasterCard participants)

MasterCard is expanding the use of Point-of-Service (POS) Entry Mode to include PAN (Primary Account

Number) Auto Entry via server (Issuer, Acquirer or third party vendor system). In addition, MasterCard is enhancing the ability for members to identify the Service Manager (originator) of the Mobile Remote

Payments program.

Page 5 of 23

The new POS Entry mode value “82” represents PAN Auto Entry via server and will be populated in (DE)

22, Point of Service Entry Mode, subfield 1, POS Terminal Pan Entry Mode, in 0100/0120, 0200/0220 and

0420 messages. All Issuers MUST be able to support a value of “82” in DE 22, subfield 1.

Remote Payments Program Type Indicator: (Optional - applies to Mobile Remote Payment Service Participants)

MasterCard is also introducing the Remote Payments Program Type Indicator. The new Remote Payments

Program Type Indicator value “1” represents Issuer domain and will be found in a 0100/0120, 0200/0220

or 0420 message. The Remote Payments Program Type Indicator will be populated in (DE) 111,

Subelement 16, in the “MD” tag; in (DE) 111, Subelement 20 in the “MC” tag and in the “MI” tag. The

value will be “1” in each of these fields. The Issuer domain refers to the end-point managing the service

like the mobile provider and can be the URL originating the request.

New Device Type Indicators: (Applies to PayPass and Mobile Remote Payment Service participants)

MasterCard is allowing Acquirers to optionally identify the device used in non-card transactions initiated

from a mobile device or other non-card device. New values, identified as Payment Initiation Channel

Device Type will be populated in (DE) 111, Subelement 17, in the “MD” tag and in (DE) 111 Subelement

21 in the “MC” tag and may be present in 0200/0220 and 0420 messages. The valid values are:

00- Card

01- Mobile Phone or Smartphone

02- Key Fob

03- Watch

04- Mobile Tag

05- Wristband

06- Mobile Pone Case or Sleeve

07-99 Reserved for future use

Partial Approval Enhancement (Informational Maestro and Debit MasterCard participants)

MasterCard will begin to allow Issuer’s to provide a partial approval response with an amount that is less

than or equal to the requested amount for restaurant and hotel transactions. Previously, MasterCard

would reject a response if the partial approval amount was equal to the transaction amount. This will

allow Issuer’s to prevent a merchant from adding a gratuity or service fee when the cardholder account

does not have a sufficient balance. If an authorization request is received where a gratuity might be

added to the settled transaction and the member does not have sufficient funds in the account to cover a

gratuity, you can respond with a partial authorization.

Restaurants and hotels are typical service providers that could submit a completion that includes a

gratuity. The Merchant Category Codes for these service providers are:

5812-Eating Placings and Restaurants

5813-Bars, Drink Places

5814-Fast Food Restaurants

3501-3999, 7011-Hotels/Motels/Resorts

The partially authorized amount returned should be equal to the transaction amount to prevent a

potential overdraft. You may want to consider adding a percentage of the requested amount to the

amount of the authorization request before making the determination of how to respond. If the balance is

Page 6 of 23

not sufficient to cover a possible gratuity but can cover the requested amount, then you would return a

partial authorization response with the partial amount equal to the requested amount.

This applies to credit unions using either the new or old Partial Authorization methodology.

Revised Test Transactions for Recurring Payments Merchants (Informational Maestro and Debit MasterCard participants)

In the past, recurring payments merchants would process recurring payment requests using a $1.00

transaction amount. MasterCard is requiring all Recurring Payments Merchants to begin sending the

authorization requests with a zero dollar transaction amount in an effort to reduce excessive holds.

VISA

Changes to Account Funding Transactions (AFT) (Required for Visa signature debit participants)

Visa is going to allow Acquirers the option of assessing two fees to AFT transactions, an optional Money

Transfer Service Fee, similar to the traditional ATM surcharge fee, and a new optional AFT Foreign

Exchange Fee. The assessment of these fees is optional and at the discretion of the Acquirer. The

Acquirer may apply both fees to a single transaction. It is important to note that the Foreign Exchange

Fee is not a currency conversion fee and may be assessed on Domestic transactions and is not exclusive

to International transactions.

The Money Transfer Service Fee (surcharge) will be passed in DE 28 and will not be included in DE 04 or

DE 05. This is how ATM surcharges are processed on the CO-OP switch today.

The Foreign Exchange Fee will be passed in DE 55. The Fee Type indicator value will be “72” and will be

identified as a memo fee. The settlement/Memo indicator in DE 055 position 3 will have a value of “0”.

The Foreign Exchange Fee will be included in DE 04 and DE 05 amounts. The Foreign Exchange Fee is

referred to in the ISO 8583, Batching Services and the ISO User File Specification as an AFT Fee. This is

the same as a CCA fee is processed on a MasterCard Cross border transaction. No transaction will have

both a CCA Fee and an AFT Foreign Exchange Fee.

CO-OP ISO User Files will be updated to reflect the new Foreign Exchange Fee - value “72”. Please see

CO-OP ISO User File Record Part 9 changes identified below.

For CO-OP Complete Authorization credit unions, the AFT Fee will be included in the Network Addendum

Record which is an optional additional record that can be provided with any posting file format in use

today. Please see the Network Addendum Record Layout below.

New Business Application Identifiers - Visa OCT Transactions

Visa is adding new BAI (Business Application Identifiers) which may be used to identify the originator of

an Original Credit Transaction (OCT). The BAI is included in the 0100/0200 message in DE 111, sub

element 30, in the “VD” tag. The BAI value does not have to be returned in the 0110/0210 response

message.

The new values being added are BB and BP and will be associated with process code 55xxxx – Payment

Credit. These transactions should be posted as a credit to your member’s account.

The list of BAI codes you may see in an OCT transactions are:

AA – Account to Account

Page 7 of 23

BB – Business to Business

BI – Money Transfer (bank initiated)

BP – Bill Payment

MI – Money Transfer (merchant initiated)

PP – Person to Person

To provide the time needed to establish compliance and risk parameters, Visa has extended the block on

international Original Credit Transactions (OCTs) until at least October 15, 2011. This means you will

not see cross-border OCTs until that time.

Page 8 of 23

ISO 8583 Processor Interface Specifications

Settlement (User File)

Detail Record Format Bit # ISO Field Name Segment Position Length Notes P-159 001 2 Record Part “9” P-160 003 7 Record Sequence Number P-162 Acq Tran Amt (CC) 010 12 Acquirer Tran Amount (Currency Conv) P-164 Acq Conv Rate (CC) 022 8 Acquirer Conversion Rate (Currency Conv) P-166 Acq Curr Cd 030 3 Acquirer Currency Code (Currency Conv) P-168 Acq Fee Amt 033 9 Acquirer Fee Amount (Currency Conv) P-298 AFT fee Issuer 042 9 AFT Fee Issuer Filler 30 Spaces 80

Page 9 of 23

Batching Services

Network Addendum Record Layout

Additional Addendum Record (All Formats) The Network optional addenda records are created only if requested by setting the CTLCD516 (INST) - POST-ADD2-

FLAG flag to Y or C. Where-

_ Y indicates the addendum record will be created including the cross border flags information (if present) but without cardholder bill amount information. _ C indicates the addendum record will be created including the cross border flags information and the cardholder bill amount information.

Note: Cardholder bill amount will not be present if the cross border information is not present. This record supports data elements such as Cross Border flags and fees for major networks.

Field No. and

Name

Start

Position

No. of

Bytes

Field

Attributes Value/ Description

1 Record Type 1 1 Numeric Value:7

2 Addendum Type 2 2 Numeric Value: 92

3 Change-Ind 4 1 Alpha-Numeric International only: ISA Indicator

For Visa:

Blank = ISA not applicable

R = Rebate

S = ISA is applicable

For Plus:

0 = ISA is not applicable

1 = ISA Fee eligible (debit)

2 = ISA Fee eligible(credit)

For MasterCard

0 = No International Fee

1 = ISA Fee eligible (debit)

2 = ISA Fee eligible(credit)

4 Opt-Iss-Fee-Ch-

Billl

5 9 Numeric Visa OIF amount in cardholder billing

currency (when applicable)

5 Op-Iss-Fee-

Ch=Bill-Sign

14 1 Alpha-Numeric Values:

C if positive

D if negative

Blank when fee not present

Page 10 of 23

6 Curr-Conv-Fee-

Ch-Bill

15 9 Numeric CCA amount in cardholder billing

currency. Blank when Charge-Ind is

present/not blank

7 Curr-Conv-Fee-

Ch-Bill-Sign

24 1 Alpha-Numeric Values:

C if positive

D if negative

Blank when fee not present

8 Curr-Conv-Fee-

settle

25 9 Numeric CCA Amount in Cardholder

settlement currency. Blank when

Charge-Ind is present/not blank

NOTE: This field is also used for

AFFN to pass the Maestro’s CCA fee

for Cross Border transactions

9 Curr-Conv-Fee-

Settle-

34 1 Alpha-Numeric Values:

C if positive

D if negative

Blank when fee not present

NOTE: This field is also used for AFFN

to pass the Maestro’s CCA fee for

Cross Border transactions

10 Cross-border

Transaction

Indicator

35 1 Alpha-Numeric Values:

Y = Transaction qualifies as a cross-

border transaction

N = Transaction does not qualify for

a cross-border transaction

NOTE: This field is also used for

AFFN/Maestro Cross-border Fee pass

through

11 Cross-border

Currency Indicator

36 1 Alpha-Numeric Values:

X or “ ” = Transaction does not

qualify as a Cross-border transaction

Y = Transaction was submitted in the

currency of the merchant’s country

N = Transaction was not submitted in

the currency of the merchant’s

country

12 Ch-Bill-Sign 37 1 Alpha-Numeric Values:

C if positive

Page 11 of 23

D if negative

Blank when fee not present

13 Ch-Bill-Amt 38 13 Numeric Cardholder Billing Amount

NOTE: This field does not contain

any fee amount

14 Poi-Amt-Sign 51 1 Alpha-Numeric Values:

C if positive

D if negative

Blank when fee not present

15 Poi-Amt 52 12 Numeric Poi Amount

16 Poi-Curr-Cd 64 3 Alpha-Numeric Poi Currency Code

17 AFT Fee-Ch-Bill 67 9 Numeric, leading

zeros right

justified, implied

decimal

Account Funding Transaction Fee in

cardholder currency

18 Filler 76 4 Alpha-Numeric Blank

19 Orig-FRDABA 80 8 Numeric FRDABA from type-6record

20 Sequence-

Number

88 7 Numeric Seq-Num from type-6 record

Record length:94

bytes

Page 12 of 23

ISO 8583 Data Element Definitions

028 Amount, Transaction Fee

Attributes:

FIS: x + n 8

ISO: x + n 8

Description:

The fee charged (for example, by the Acquirer) for transaction activity in the currency of

the transaction amount. The fee may be a surcharge, rebate, or transaction fee.

This amount must be the same value in the response as in the request. The value is a

debit for a fee and a credit for a rebate. (The debit or credit reflects the cardholder’s

perspective.)

Notes:

FIS only calculates on-line fees for surcharging.

See the description for data element 055 Additional Fees

Data Edit:

Must be numeric. x must be 0, C, or D.

C = Credit amount

D or 0 = Debit amount

Status:

Refer to the following chart for the FIS data element requirements.

Message Types Status Information

0100, 0120, 0200,

0220, 0420

Conditional. Required when the defined fee is present. Following is additional detail you

need to know.

The value is a debit for a fee and a credit for a rebate.

The sign indicator is reversed to indicate the reversal of a fee.

FIS does not calculate on-line fees, except for surcharges.

0110, 0130, 0210,

0230, 0430

Conditional. Required if the Amount, Transaction Fee is received in the request message.

The response value must be the same as the value in the request.

Page 13 of 23

055 Additional Fees

Format:

LLLVAR

Attributes:

FIS: ans..88

ISO: ans..999

The data element breakdown, occurring four times, is as follows:

Position Data Content/Attributes Notes

1-2 Fee Type (n 2) Values are:

00 Transaction fee

Note: The first amount is in the transaction currency

and the second amount is in the settled currency.

15 Multiple Currency Conversion Rate (MasterCard MCCR)

Note: The first amount is in the cardholder bill

currency and the second amount is in the settled

currency.

70 Surcharge

Note: The first amount is in the transaction currency

and the second amount is in the settled currency.

71 Optional Issuer Fee (Visa OIF)

Note: The first amount is in the cardholder bill

currency and the second amount is 0 because it does

not apply to the settlement amount.

72 Foreign Exchange Fee

Note: The first amount is in the transaction currency

and the second amount is in the settled currency. This

is a memo fee.

3 Settle/Memo Indicator (n 1) Values are:

1 If a surcharge is indicated, then the settle indicator is

set to a value of 1. This causes the funds to be

settled.

0 If a transaction fee is indicated (the fee type is 00, 15,

71 or 72), then the settle indicator is not set,

indicated by a value of 0. This prevents funds from

settling to the cardholder twice.

4 Decimalization Indicator (n 1) Value is 0; reserved for future use.

5-13 Fee Amount (x + n 8)

14-22 Settle Fee Amount (x + n 8)

Page 14 of 23

Description:

Information on up to four fees in addition to the fees defined in data elements 028

(Amount, Transaction Fee) and 029 (Amount, Settlement Fee).

In this specific link, if data element 028 is defined to be used for surcharge amounts

only, then this field must not contain a surcharge. Likewise, if data element 028 is

defined as a transaction fee, then this field must not contain a transaction fee.

Note: FIS does not calculate on-line fees.

Data Edit:

Must be numeric. x must be 0, C, or D.

C = Credit amount

D or 0 = Debit amount

Status:

Refer to the following chart for the FIS data element requirements.

Message Types Status Information

0100, 0120, 0200, 0220,

0420

Conditional. Required when the defined fee is present. Following is additional detail you

need to know.

The value is a debit for a fee and a credit for a rebate.

The sign indicator is reversed to indicate the reversal of a fee.

0110, 0130, 0210, 0230,

0430

Conditional. Required if the Additional Fees is received in the request message. The

response value must be the same as the value in the request.

Page 15 of 23

111 Additional Data, Private Acquirer (FIS-Defined)

Format:

LLLVAR

Attributes:

FIS: ans..255

ISO: ans..999

Description:

This data element is reserved by ISO for private definition and use.

FIS defines this data element as Additional Data, Private Acquirer, which contains

additional information for Visa® DCS, Visa EVES, Visa DCS CRISSM, Benefits Transfer,

MasterCard® CIS, MasterCard IPM and PLUS® format. The layouts for this data follow.

Status

MasterCard® CIS Format (Debit Authorization)

Subelement Name/Contents

Data

Length

MasterCard

Bit No.

FINIPC

Bit No.

Data Identifier. Value: MC 2 NA NA

Data Length plus the variable data. 3 NA NA

Data Byte Map. See FINIPC Bit Number. 8 NA NA

Variable Data: (based on byte map)

Merchant Advice Code 2 48.84 1

Fraud Data. This data contains the following three subfields for a total

length of 9:

2

POS Entry Mode 3 22

Response Code 2 39

POS Data - POS Terminal Attendance

POS Data - POS Cardholder Presence

POS Data - Card-Activated Terminal Level

POS Data - POS Card Data Terminal Input Capability

1

1

1

1

61.1

61.4

61.10

61.11

Page 16 of 23

Advice Detail Code 4 60.2 3

Magnetic Stripe Compliance Status Indicator 1 48.88 4

Magnetic Stripe Compliance Error Indicator 1 48.89 5

Postal Code 10 61.14 6

POS Card Presence

0 = Present

1 = Not Present

1 61.5 7

Payment Type Indicator 3 48.77 8

MC Assigned ID 6 48.32 9

MC Fraud On-Behalf Result 1 48.71.2 10

MC Fraud Score Information 3 48.75.1 11

MC Healthcare IIAS Exemption 1 48.61.3 12

Processor Pseudo ICA 7 48.16 13

Authorization System Advice Date and Time 10 48.15 14

Account Data Compromise Event Messaging Service Data Result 1 48.71.2 15

Account Data Compromise Event Messaging Service Data 30 48.39 16

Partial Approval Terminal Support Indicator 1 48.61.1 17

MC Fraud Score Reason Code 2 48.75.2 18

POS Transaction Status Indicator 1 61.7 19

Remote Payments Program Type Identifier 1 48.48.1 20

Payment Initiation Channel Device Type 2 48.23.1 21

Page 17 of 23

MasterCard® MDS Format (Maestro)

Subelement Name/Contents

Data

Length MasterCard Bit No.

FINIPC

Bit No.

Data Identifier. Value: MD 2 NA NA

Data Length (byte map + variable data) 3 NA NA

Data Byte Map (See FINIPC Bit No.) 8 NA NA

Variable Data (Based on Byte Map)

Tier Merchant ID 6 DE110.1 1

Cross Border Indicator 2 2

Transaction Indicator-Position 1 DE126, position 14

Y = Qualifies as a cross-border transaction

N = Does not qualify as a cross-border transaction

Currency Indicator-Position 2 DE126, position 15

X = Transaction does not qualify as a cross-border

transaction.

Y = Transaction was submitted in the currency of the

country where the merchant is located.

N = Transaction was not submitted in the currency of

the country where the merchant is located.

ISA Flag

0 = No International Fee

1 = International Fee Debited

2 = International Fee Credited

1 DE 110.4 3

Financial Network Code 2 DE63, subfield 1 4

Card Present 1 DE61, position 5 5

Operating Environment 1 DE61, position 3 6

Page 18 of 23

POS Terminal Attendance Indicator 1 DE61, position 1 7

POS Cardholder Presence Indicator 1 DE61, position 4 8

Cardholder Activated Terminal Level Indicator 1 DE61, position 10 9

POS Card Data Terminal Input Capability Indicator 1 DE61, position 11 10

POS Entry Mode 2 DE22 11

Payment Type Indicator 3 48.77 12

MC Assigned ID 6 48.32 13

MC Healthcare IIAS Exemption 1 48.61.3 14

POS Transaction Status 1 61.7 15

Remote Payments Program Type Identifier 1 48.48.1 16

Payment Initiation Channel Device Type 2 48.23.1 17

Page 19 of 23

MasterCard® IPM Format (Debit Completion)

NOTE This format does not apply to the MasterCard 0100 authorization messages.

Subelement Name/Contents

Data

Length MasterCard Bit No.

Data Identifier. Value: MI. 2 NA

Data Length plus the variable data. 3 NA

Processing Code 6 IPM DE 3

POS Condition Code. This data contains the following 12 subfields for a

total length of 12.

IPM DE 22

Card Data Input Capability 1 IPM DE 22-S1

Cardholder Authentication Capability 1 IPM DE 22-S2

Card Capture Capability 1 IPM DE 22-S3

Terminal Operating Environment 1 IPM DE 22-S4

Cardholder Present Data 1 IPM DE 22-S5

Card Present Data 1 IPM DE 22-S6

Card Data Input Mode 1 IPM DE 22-S7

Cardholder Authentication Method 1 IPM DE 22-S8

Cardholder Authentication Entity 1 IPM DE 22-S9

Card Data Output Capability 1 IPM DE 22-S10

Page 20 of 23

Terminal Data Output Capability 1 IPM DE 22-S11

PIN Capture Capability 1 IPM DE 22-S12

Card Acceptor Inquiry Information. This data contains the following

three subfields for a total length of 57:

IPM PDS 0170

Customer Service Phone Number 16 IPM PDS 0170-S1

Card Acceptor Phone Number 16 IPM PDS 0170-S2

Additional Contact Information 25 IPM PDS 0170-S3

Card Acceptor Postal Code 10 IPM DE 43-S4

Local Date and Time 12 IPM DE 12

Airline/Railway Ticket Number 15 IPM PDS 0506

Program Registration ID 3 IPM PDS 0043

Interchange Life Cycle 15 IPM PDS 0263

Cross Border Transaction Indicator 1 IPM PDS 0177-S1

Y = Qualifies as a cross-border transaction

N = Does not qualify as a cross-border transaction

Cross Border Currency Indicator 1 IPM PDS 0177-S2

Blank = Transaction does not qualify as a 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.

Page 21 of 23

MasterCard Assigned ID 6 IPM PDS 0176

Payment Transaction Initiator 3 IPM PDS 0192

CVC 2 Validation Program Indicator 1 IPM PDS 0044 subfield 1

QPS/PayPass Chargeback Eligibility Indicator 1 IPM PDS 0044 subfield 2

Remote Payments Program Type Identifier 1 IPM PDS 0194

Payment Initiation Channel Device Type 2 IPM PDS 0198

Visa® DCS Format

Subelement Name/Contents

Data

Length

Visa Bit

No. FINIPC Bit No.

Data Identifier. Value: VD 2 NA NA

Data Length plus the variable data. 3 NA NA

Data Byte Map. See FINIPC Bit Number. 8 NA NA

Variable Data: (based on byte map)

Authorization Characteristics Indicator 1 62.1 1

Market-Specific Data Indicator 1 62.4 2

Duration 2 62.5 3

Prestigious Property Indicator 1 62.6 4

Purchase Identifier 26 62.7 5

Check In/Check Out Date 6 62.8 6

No Show Indicator 1 62.9 7

Extra Charges 6 62.10 8

Restricted Ticket Indicator 1 62.13 9

Page 22 of 23

Requested Payment Service 1 62.15 10

Chargeback Rights Indicator 2 62.16 11

Electronic Commerce Goods Indicator 2 62.19 12

Merchant Verification Value (MVV) 10 62.20 13

CAVV Result 1 44.13 14

Risk Score 4 62.21 15

Risk Condition Codes 6 62.22 16

Processing Codes 6 3 17

Terminal Type 1 60.1 18

Additional POS Information 2 60.8 19

Excl Transaction ID Reason Code 1 62.18 20

STIP Reason Code 4 63.4 21

Visa Charge Indicator. Value to indicate the International Service

Assessment (ISA).

Blank = Fee Not Assessed

S = Fee Assessed

R = Fee Rebated

1 63.21 22

Latin America Caribbean Optional Issuer International Service

Assessment

15 46 23

Consumer Credit Account-Level Product Identification 2 62.23 24

Cardholder ID Method 1 60.9 25

MIS Reason 4 63.3 25

Recurring Pay Ind. 1 126.13 25

Service Indicators (Deferred Bill) 6 126.12 26

Response Code 2 39 27

Page 23 of 23

Payment Type Indicator (DE104/x"57") reserved 1 104 28 reserved for

future use

DE48 - Usage 4 38 48 29

Business Application Identifier 2 104

usage 2

hex 57

Tag 01

30

Visa AVS Result Value 1 44.2 31

Byte Map 2 8 N/A 32

Dynamic Currency Conversion Indicator 1 126.19 33