1 of 25 Spring Mandate Notification - February 28, 2017 2017 Spring Mandate Notification CO-OP Financial Services will implement the code changes required to support card association and EFT network Spring Mandates on Friday, April 21, 2017, 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 ensure their vendor has the information needed to support these changes. If a 3 rd party authorizes transactions on your behalf, often referred to as a service bureau, you should forward this information to them. Please note: DataNavigator will be taken offline at 7 p.m. PT on April 21, 2017, to install the code changes required to support the mandates. DataNavigator will be unavailable for approximately two hours. Questions regarding your credit union network participation should be verified with the sponsorship or contracts administrator within your organization. Some credit unions 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. Please contact Client Services at 800.782.9042, option 2, with any questions.
Transcript
1 of 25
Spring Mandate Notification - February 28, 2017
2017 Spring Mandate Notification
CO-OP Financial Services will implement the code changes required to support card association and EFT network Spring Mandates on Friday, April 21, 2017, 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 ensure 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 them. Please note: DataNavigator will be taken offline at 7 p.m. PT on April 21, 2017, to install the code changes required to support the mandates. DataNavigator will be unavailable for approximately two hours. Questions regarding your credit union network participation should be verified with the sponsorship or contracts administrator within your organization. Some credit unions 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. Please contact Client Services at 800.782.9042, option 2, with any questions.
2
Summary by Association/Network Note: All services are required unless otherwise noted. MoneyPass MoneyPass Deposit Type Indicator - pgs. 3-4 Pulse ATM Deposit Type Indicators – pgs. 4-5 NYCE Payment Account Reference – pgs. 5-6 AVS Response codes Updated for AFD and eCommerce Transactions – pg. 6 MasterCard Safety and Security Roadmap
Credit, Debit, Maestro and Cirrus – pg. 7-8 MasterCard Digital Enablement Service Enhancements (MDES) New Transaction Analysis Capabilities and CVM Models for MCBP Tokens
Credit, Debit and Maestro – pgs. 8-10 MasterCard Validation Services-Affiliate Members - pgs. 10-11 Block Removal on MoneySend Payment Transactions Informational Only – pg.11 Support of Payment Account Reference (PAR) Credit, Debit and Maestro – pgs. 11-12 Chip Liability Shift Delays for U.S. Region Automated Fuel Dispenser Merchants – pg. 12 Visa Expansion of Incremental Authorization Processing – pg. 12 Changes to the Visa Token Service Informational Only – pg. 13 CO-OP - pgs.13-14 STAR STAR Access – pgs. 14-17 ISOI 8583 Data Element Definitions DE111 – Additional Data, Private Acquirer, “ST” Tag Layout – pgs. 18-20 DE111 – Additional Data, Private Acquirer, “MD” and “MC” Tag Layout – pgs. 20-25
3
MoneyPass
MoneyPass Deposit Type Indicator MoneyPass is requiring support of their Deposit Indicator in deposit transactions (processing code 21xxxx). They are requiring that the indicator be passed to issuers in request/reversal messages and sent back in response messages for authorizations and reversals. Issuers are not required to echo back the data, the switch will ensure the data is forwarded to MoneyPass in the 0210/0430 response message. Transactions impacted:
In support of the Deposit Type indicator, mapping will be implemented at the switch to meet the MoneyPass requirement. Mapping information: Acquirer: Amount Types
Note: Intercept processors – Intercept processors will be required to send the appropriate amount type by network when processing a mixed deposit. CO-OP and NYCE networks use “90” for check amount. MoneyPass and Pulse use “94”.
PULSE
ATM Deposit Type Indicators PULSE is enhancing ATM deposit transactions (processing code 21xxxx) to include an indicator that identifies the type of deposit (cash, check, mixed or unknown) and the amount of each type. The ATM Deposit Type indicator will provide data to monitor anti-money laundering (AML) activities. Issuers are not required to echo back the data within DE054 and/or DE104 in the response message.
The deposit transaction description is required. DE104 will include a deposit indicator for cash, checks, mixed or unknown. In support of the Deposit Type indicator, mapping will be implemented at the switch to meet the Pulse requirement. Mapping information: Acquirer: Deposit Type
Mixed Deposit 21xxxx 21xxxx Not present 00 UNKNOWN Not present or MIXDEP
Unknown 21xxxx 21xxxx 00 00 UNKNOWN UNKNOWN
Issuer: Deposit Type
Pulse Process Code
CO-OP Process Code
Pulse DE54 Amt type
CO-OP DE54 Amount Type
Pulse DE104
CO-OP DE104
Check Deposit
21xxxx 21xxxx 94 94 CHECK CHECK
Cash Deposit
21xxxx 21xxxx 93 93 CASH CASH
Mixed Deposit
21xxxx 21xxxx 93 & 94 93 & 94 MIXDEP MIXDEP
Unknown 21xxxx 21xxxx 00 00 UNKNOWN UNKNOWN
NYCE
Payment Account Reference Payment Account Reference (PAR) numbers are entering the payments networks arena as an alternative to the use of the Primary Account Number (PAN) to support consumer loyalty (typically rewards) programs. While the use of a PAR is optional for merchants, POS processors and eCommerce processors are required to support the PAR whenever it is present in a transaction response message. NYCE is positioning the network to fully support use of PAR by requiring POS and eCommerce processors to be able to process response messages that contain PAR values. • The PAR value can be present in response messages for:
o Purchase (02xx) o Merchandise return (02xx) o Purchase preauthorization (01xx) o ZDAV (Zero Dollar Account Verification)
• When present in a response message, PAR will be passed to CO-OP credit unions in the PR data tag in DE124 with a maximum length of 32 characters. • PAR may be present for transactions that used a token PAN as well as transactions that use the customer’s real PAN. The NYCE PAR value will be passed it in DE124 tag “PR” in 01xx and 02xx response messages.
DE124 tag “PR” format:
6
PRnnDDDD
where:
Tag Description
PR Is the 2 byte literal identifying Payment Account Reference Number
nn Is the 2 byte length of Data
DDDD Is the Payment Account Reference Number for variable length, maximum length 32 characters
Example:
PR3212345678901234567890123456789012
The Tag ID is identified as “PR” has a data length of “32” followed by the payment account reference number.
CO-OP will support and accept the PAR data. Credit unions with DE124 enabled should expect to receive this data on/after April 15, 2017. If you would like to enable DE124 and you have verified your core vendor can support this, a service request can be submitted via the CO-OP Extranet; the type will be “Other” and explain that you would like to enable DE124. AVS RESPONSE CODES UPDATED FOR AFD AND eCOMMERCE TRANSACTIONS The NYCE ISO specifications have been updated to clarify the use of response codes (present in DE 039) for PINless POS purchases initiated at Automated Fuel Dispense (AFD) terminals and for eCommerce purchase transactions.
• NYCE Network Operating Rules effective July 1, 2015, required issuers to support authentication of AVS (Address Verification Service i.e. the cardholder’s zip code) data for PINless POS transaction requests initiated at AFD terminals. NYCE is requiring Issuers discontinue the use of response code ‘T8’ effective April 15, 2017.
Note: This has no impact to CO-OP Host Processors. Changes will be made at the switch to ensure “T8” response is not sent to NYCE.
• Effective January 1, 2016, the Rules were amended to require issuer validation of CVV2/CVC2 and AVS whenever present in any Network transaction. This requirement has not changed; however, with respect to eCommerce transactions, issuers may approve the transaction requests, and also indicate that there is an AVS mismatch. In the case where there is a mismatch, the eCommerce merchant has the right to accept the approval or reverse the transaction. The NYCE Network Operating Rules effective January 1, 2017 will reflect this option for eCommerce merchants.
7
MasterCard Safety and Security Roadmap Credit, Debit, Maestro and Cirrus
CO-OP will be adding support for required security-related fields as part of the MasterCard Safety and Security Roadmap. The roadmap encompasses a series of rules and processing requirements for acquirers and issuers to help ensure the continued safety and security of the Mastercard Network and to protect the Mastercard brand.
CO-OP will update DE124 tags “FD” and “FS” with MasterCard Fraud Score Data and Fraud Security Services Data. In addition, this data will be passed in ISO DE111, tags “MC” and “MD”. See data element information below.
The Fraud Score Data will be passed in DE124, tag “FD”. The internal logging of fraud score data will conform to the following format:
DE124 tag “FD” format: FDLLxxyyzzzz
where:
FD Is the 2-byte literal identifying Fraud Score Data
LL Is the length of data that follows
xx Is 2-byte Fraud Product ID (05 = MasterCard)
yy Is 2-bytes containing the length of data to follow
Zzzz When xx = 05 zzzz will contain data in the following format:
FS Is the 2-byte literal identifying Fraud Security Services Data
LL Is the length of data that follows
xx Is 2-byte Fraud Product ID (05 = MasterCard)
8
yy Is 2-bytes containing the length of data to follow
zzzz when xx = 05, zzzz will contain data in the following format:
Position: 1-12 = Security Services Additional Data for Issuers
When no data or data less than 12 bytes, it should be filled with spaces
13-27 = Time Validation Information 28-29 = Transaction Integrity Class 30-59 = Account Data Compromise Information
These new fields, when received will be available in DataNavigator in the long format data.
In addition to support of the security fields supported in DE124 above, as a reminder Mastercard requires participation in the following:
• Transaction Alerts • MasterCard ABU • MasterCard Key Requirements
Mastercard Digital Enablement Service Enhancements (MDES) New Transaction Analysis Capabilities and CVM Models for MCBP Tokens Credit, Debit and Maestro Mastercard is updating the Mastercard Digital Enablement Service (MDES) to support new transaction analysis capabilities, new Cardholder Verification Method (CVM) models, and the delivery of transaction analysis results information to issuers when MCBP (MasterCard Cloud-Based Payments) tokens transact. Mastercard will introduce the following capabilities: Transaction Analysis as part of Transaction Validation As MCBP transactions are processed by Mastercard, a specific set of transaction analysis validations will be performed. MasterCard will provide issuers with a code representing the overall disposition of the transaction based on the applicable transaction validation results and decision matrix. NOTE: Messages from MasterCard that contain Network Additional Transaction Analysis data are considered suspect and the AP Authorization process will deny these transactions. Credit unions that are not utilizing the AP Authorization process should review this information and set the appropriate logic to consider denying these transactions. CO-OP will pass Network Additional Transaction Analysis data in DE124 tags “TQ”. DE 124 - Payment Token Data Tag Description TQ 2 byte literal identifying Network Additional Transaction Analysis data –
Transaction Disposition and Test Results
9
LL Length of Additional Transactions Analysis abc Network Additional Transactions Analysis data – Transactions Disposition
and Test Results Currently this field would contain data from MasterCard DE48.27 Example: 0102CI0206SNAOVP
MasterCard Transaction Disposition Values
MasterCard Test Result Values:
10
MasterCard Validation Services - Affiliate Members Effective April 1, 2017, all Issuers must adopt the validation service(s) in Stand-In processing applicable to each of their programs to help ensure the security and integrity of transactions processed by MasterCard on Issuers’ behalf. Complying with this mandate will require the Issuer to share security keys with MasterCard in order for the network to perform validation in Stand-In processing. The following validation services are included in this mandate: • Card Validation Code 1 (CVC 1) Magnetic Stripe • Card Validation Code 3 (CVC 3) Contactless • SecureCode Accountholder Authentication Value (AAV) Requirements As your network sponsor, CO-OP will extract the applicable keys for each BIN on your institution’s behalf, encrypt them using a Key Encrypting Key (KEK), and share them with MasterCard in a secure manner. MasterCard also requires a test plastic card to be ordered for each BIN to complete validation. In order to avoid noncompliance fines assessed by MasterCard, CO-OP requested that you order a test plastic card to be received at CO-OP with an ETA of February 17, 2017. If you have not already done so, test cards should be ordered using the credit union's standard card ordering process immediately. Please have test plastic cards shipped to: CO-OP Financial Services Attn. OBKM 11313 USA Parkway, Suite E#134 Fishers, IN 46037 MasterCard Noncompliance Fees $ 2,500 Noncompliance Fees per BIN - Stand-In Integrity Fees will be applicable to any BIN range out of compliance as of the effective date of the mandate. MasterCard will bill the fee the month immediately following the effective date of the mandate for three months. The frequency of the billing will increase to weekly thereafter. For other related fees and descriptions that apply to this mandate see CO-OP notification
11
MasterCard Validation Services Mandate dated February 3, 2017 or MasterCard Revised Standards for Validation Services During Stand-In Processing – Update, Global Operations Bulletin No. 11, 1 November 2016. Block Removal on MoneySend Payment Transactions Informational only Effective April 21, 2017 Mastercard will be removing the block on MoneySend payment transactions with cash as the funding source. Issuers in the U.S. region must be prepared to receive MoneySend Payment Transactions with cash as the funding source for receiving cards. MasterCard is removing their edit check on cash as a funding source and the CO-OP switch is prepared to accept these transactions. There should be no impact to core systems. Support of Payment Account Reference (PAR) Credit, Debit and Maestro Mastercard is establishing the necessary business practices and technology changes to support the EMVCo PAR specification across Mastercard brands. The information within this release item is intended to assist customers with preparing their systems to support PAR. All MDES issuers must support new Payment Account Data and Payment Account Reference information. The Payment Account Data is a non-financial reference assigned to each unique PAN and used to link a payment account represented by that PAN. The Payment Account Data from MasterCard will be passed in 0100/0200, 0110/0210 and 0620 (Token Notification Advice for Tokenization Complete Notification) messages in ISO DE124 - “PR” Tag (Payment Account Reference). Note: Issuers are not required to send PR Tag back to FIS in response messages. DE124 tag “PR” Tag Description PR 2 byte literal identifying Payment Account Reference Number LL 2 byte length of data abc Payment Account Reference Number for variable length
Example: PR295001ABCFDEDFSDSDSDSDSDSD1231A
Mastercard will assign a PAR value to MDES tokenized PANs with tokens in Active or Suspended status. MDES issuers must manage the life cycle of the PAN to the PAR value stored by Mastercard. The following options will be available to MDES issuers to assist in managing the assignment of a new PAN to an existing PAR value:
• MDES Customer Service Application or MDES Customer Service API - when an MDES issuer uses the Token Management function to update the PAN to token relationship, Mastercard will link the updated PAN to the PAR.
12
• Automatic Billing Updater—when MDES issuers submit PAN updates using ABU, Mastercard will link the updated PAN to the PAR.
NOTE: Mastercard will introduce support for PAR over multiple releases. Mastercard will include a PAR value to additional messages in future releases. Chip Liability Shift Delays for U.S. Region Automated Fuel Dispenser Merchants Mastercard previously announced that U.S. region AFD merchant locations identified with card acceptor business code (MCC) 5542 (Fuel Dispenser, Automated) will participate in the U.S. region domestic chip and chip/PIN liability shifts and join the Global Chip Liability Shift Program for interregional transactions as of 1 October 2017. To provide additional time for this merchant sector to migrate to EMV1 chip technology, Mastercard is delaying the participation date for U.S. region AFD merchants to 1 October 2020, when the merchant accepts a card issued in the U.S. region. The participation date will remain 1 October 2017 with respect to the acceptance of cards issued outside of the U.S. region. In an effort to minimize fraud exposure in the payments ecosystem during the liability shift extension period, fuel merchants will continue to be evaluated in accordance with the guidelines of the Mastercard Excessive Chargeback Program (ECP). A fuel merchant that is identified in ECP as an Excessive Chargeback Merchant (ECM) will be required to implement the Address Verification Service (AVS) within 60 days of the ECM identification. This requirement will remain in place until the merchant is no longer identified as an ECM for three consecutive months. Additional details about the AVS requirement will be published in a future U.S. Region Operations Bulletin. For more information about the Mastercard ECP, see section 8.3 of the Security Rules and Procedures.
VISA
Expansion of Incremental Authorization Processing Visa will implement changes to expand eligible merchants capable of utilizing estimated, initial, and incremental authorization processing. The following Merchant Category Codes will be eligible. MCC Description
Changes to the Visa Token Service Informational only Visa will implement the following changes that will apply to authorization and purchase request messages submitted as delayed charges and re-authorization merchant-initiated transactions with a payment token:
• Increase the time limit check for payment token delayed charges transactions from 30 days to 90 days
• Increase the time limit check for payment token re-authorization transactions from 30 days to 120 days for select merchant category codes (MCCs)
Impacted MCC codes:
CO-OP
Acquiring networks like MasterCard, Visa or STAR may occasionally authorize a transaction based on their processing rules, like On Behalf of Services or stand-in. Currently when one of these networks authorizes and approves a transaction, there is an advice, 0120/0220, message forwarded to CO-OP and to your host. If MasterCard, Visa or STAR decline a transaction, it may not currently be sent to CO-OP or your host. More and more credit unions are interested in the ability to view and analyze the entire member experience. To that end, after April 21, 2017, CO-OP will begin working with these networks to implement the configuration changes required to receive these denials. A transaction denied by MasterCard, Visa or STAR will be forwarded to CO-OP. The transactions will then be available in DataNavigator.
14
If your host is configured to receive advices on denied transactions, CO-OP will send an advice to your host. If your BIN/host is not set up to receive advices on denied transactions, you will still be able view the transactions in DataNavigator. Since these transactions will now be received and logged by CO-OP, you may see a slight increase in switch fees as a result of these denials. VAU/ABU – see CO-OP VAU/ABU Support published September 30, 2016 Republished with the Spring 2017 Mandate/Q&A notice
STAR
STAR Access In April 2015, the STAR Network launched the first phase of STAR Access. STAR Access is designed to provide convenience and choice for STAR Members and cardholders by expanding support for all debit transactions through all payment channels using all payment devices. The first phase limited functionality to select card-present transactions processing the current Single Message Specification (SMS) environment for purchases, merchandise returns, pre-authorizations and pre-authorization completion. As published in our Fall Mandate document, STAR has announced the full launch of STAR Access to expand the authentication options and processing environments available. This phase will expand the STAR Access footprint into a greater segment of eligible transactions by enhancing the existing SMS environment and message format, as well as introducing a new dual message specification interface and supporting processes. STAR is requiring each STAR Issuer with cards that are capable of performing POS or Internet transactions to participate in STAR Access. As we continue to work with STAR to determine an implementation date there has been a couple additions/changes to the technical specifications so we are republishing the technical information with those changes. The additions and changes are shaded. STAR Access will provide support for Automated Fuel Dispense (AFD) authorization request messages for both Single Message System (SMS) and Dual Message System (DMS) acquirers. Transactions will be identified with MCC 5542, Petroleum Unattended. For SMS acquirers the transaction is initiated with a 0100 pre-authorization request. The request has a life cycle of 2 hours which will be sent in DE057. The transaction can be fully approved or partially approved by the issuer. Support of partial authorizations is required for issuers. Once the cardholder pumps their fuel, the acquirer will send a 0220 completion message with the final purchase amount. For DMS acquirers the transaction is initiated with a 0100 authorization message for $1.00. The request will not contain a life cycle indicator in DE057. The $1.00 represents an authorization of up to $100 if the transaction is fully approved or it could be partially approved by the issuer. Once the cardholder pumps their fuel, the acquirer will send a 0120 completion advice for the full amount of the purchase. This will provide the actual amount that should be held. At a merchant determined time, the acquirer will send a 0220 completion message that will match the amount from the 0120. Typically the completion message should be received the next day.
15
STAR Access will support Balance Inquires initiated from POS terminals for either SMS or DMS acquirers. The Balance Inquires will be 0200 messages with process code 31xx00. Recurring payment transactions are supported and can be identified by the value of “4” in DE058 position 4. Partial authorizations are not permitted on recurring payments. Account Verification transactions are supported and will be sent as 0200 with a process code of 33xx00. These transactions are to verify the validity of a card and may contain AVS and CVV2/CVC2 data. 33xx00 is a new process code for STAR Account Verification. Most other networks use a purchase process code of 00xx00. Please be sure to add process code 33xx00 to your transaction tables. Transit and eCommerce merchants are allowed to originate aggregated transactions. eCommerce transactions must be electronically authorized and settled for the total amount. Transit merchants designated as commuter transit may aggregate small transactions in a face-to-face environment. Transit merchants with the below MCCs are eligible:
• 4111 – Local and Suburban Commuter Passenger Transportation, including Ferries and Railways
• 4112 – Passenger Railways • 4131 – Bus Lines • 4784 – Bridge and Road Fees/Tolls
The permitted Aggregation Period and Aggregation Amount for eCommerce is 3 calendar days and $25, and for Transit merchants, 7 calendar days and $25 dollars. The Aggregation Amount may be less if approved with a partial authorization. To identify aggregated transactions we will be adding a Transaction Aggregation Indicator in a new “ST” tag in DE111 (see layout below), and a new tag of AGGR in DE104. The format of AGGR tag in DE104 is:
AGGR<Interlink Identifier><Aggregate Indicator>; The AGGR tag will appear as “AGGRbY” or “AGGRbN”, where AGGR = Aggregation Tag b = blank Y/N = Merchant Aggregation Indicator
Bill Payments will be supported for SMS and DMS acquirers. SMS acquirers will send a 0200 message with process code 50xx00. DMS acquirers will send a 0100 authorization and 0220 completion with process code 0220. STAR Access will provide support of Incremental Authorizations. Incremental Authorizations will contain the following data from the original authorization transaction to facilitate matching:
• System Trace Audit Number – DE011 • Incremental Authorization Indicator – DE111, “ST” tag • Transaction Identifier (ATSN) - DE111, “ST” tag • Acquirer Reference Number (ARN) - DE111, “ST” tag
16
According to STAR, they will assign a Transaction Identifier (ATSN) for every 0100 authorization request. The ATSN is a number that is should be the same on subsequent incremental authorizations, completions and reversals to assist with matching to the original authorization. Travel Service merchants are permitted to have multiple authorizations and the authorization to transaction amounts are allowed up to a 15% variance. Partial Authorizations are permitted on STAR Access transactions. Issuers should use current partial authorization processing to partially approve a STAR Access transaction. If you have converted to CO-OP’s New Partial Authorization Methodology you will receive the partial authorization eligibility indicator in DE058. STAR Access will allow Multiple Clearing (split shipment) transactions for Airline and card not present/cardholder not present transactions as indicated in DE058. This will allow merchants to process multiple shipments from a single order and send a clearing message after each item is shipped. The first clearing transaction will contain a Multi-Clear Sequence Number in DE124, “SN” tag and a Multi-Clear Count Number DE124, “CN” tag. The Multi-Clear Sequence Number is used to show which clearing transaction out of the total expected clearing transactions. The Count Number is the total expected clearing transactions. The value in the Sequence Number should never be higher than the Count Number. For example, the if two clearing transactions will be sent, the first will have a Sequence Number of “1” and Count Number of “2” and the second (final) will have a Sequence number of “2” and a Count Number of “2”. STAR Access will support gratuity based transactions from restaurants, taxi cabs, bars/taverns, beauty and barber shops, and health and beauty spas. A tip variance of 20% will be supported between the pre-authorization and completion. STAR requires DE038, Authorization ID, to be populated by issuers for STAR Access 0110 and 0210 authorization approvals with response codes of “00” (approval) and “10” (partial approval). If the issuer returns a 0110 or 0210 authorization without DE038 populated, STAR will reverse the 0110/0210 response back to the issuer. STAR Access transactions will have a Network ID of “AXS” in DE063. The following POS Entry Mode values can be sent in DE022 for STAR Access transactions:
STAR Access transactions can include the Device Type, in DE124 Tag D1. Currently, the D1 tag is defined only for Token transactions, but with STAR Access you can receive the D1 tag on a non-token transaction. There will be a new tab added to DataNavigator for STAR Access transactions. The following fields will be present on the new tab:
• ATSN • ARN • Payment Initiation Type • Interchange Program Identifier • Tran 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 STAR and PLUS® format. The layouts for this data follow.
STAR Format
Sub-element Name/Contents Length
FINIPC bit Additional Notes
Data Identifier. Value: ST 2
N/A
Data Length (byte map + variable data)
3
N/A
Data Byte Map - Variable Data (Based on Byte Map)
8 NA
Payment Initiation types Values: 00 = Card 01 = Mobile phone 02 = Fob 03 = Watch 04 = Mobile tag 05 = Wristband 06 = Mobile case 07-99 = Future Use
2 1
Cardholder Identification Method Values: 1 No CIM 2 Reserved for Future Use 3 Signature
1 2
STAR Verification Value 10 3 STAR Assigned value Market Indicator Values: B - Bill pay G - Goods & services H - Healthcare L - Prepaid load
1 4
19
M - Money transfer Q - Quasi cash Merchant Aggregation Indicator Values: Y - Yes, processed by Merchant Facilitator N or space - No
1
5
Transaction Aggregation Indicator Values: N or space = Not Aggregated E = e-commerce T = Transit
1 6
Transaction Description Values: AA - Account-to-Account PP - Person-to-Person BB - Business-to-Business BP - Business-to-Person OG - Online Gambling (Winnings) - For Future Use
2 7
ATSN 15 8 Unique ID assigned by the STAR Network at time of authorization response. ATSN is a lifecycle indicator. The last digit of the 15-byte data element will represent when STAR has assigned it.
Incremental Authorization Indicator Values: Space = Not an incremental authorization I = Incremental authorization
1 9
DE110, Acquirer Reference Number Position 1: ‘8’ = Sale ‘9’ = Refund Positions 2-7: Acquirer ID (BIN) Positions 8-11: Julian Date Positions 12-22: Acquirer Use – (own internal information) Position 23: Check Digit
23 10
Interchange Program Identifier
3 11
Passenger Transport 15 12 Represents the ticket or invoice
20
Ticket Number number for the airline or railway carrier
SMS/DMS Indicator 3 13 Set by STAR to indicate if the acquirer process is Single or Dual Message
MasterCard® MDS Format
Sub-element 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.
21
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
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
