Bank of America Merchant Services MultiLink Message Specification Authorization Formats for Debit, Credit, EBT, Check Acceptance and POS Check

Bank of America Merchant Services MultiLink Message Specification Authorization Formats for Debit, Credit, EBT, Check Acceptance and POS Check Version 4.02 Document creation date: March 28, 2002 Last modification date: August 12, 2009 Original document author: Monte D. Shuck Last modified by: Monte D. Shuck

BANK OF AMERICA MERCHANT SERVICES CONFIDENTIALITY REQUIREMENTS...7 OVERVIEW...8 1.0 TRANSACTIONS SUPPORTED...9 1.1 DEBIT TRANSACTIONS... 9 Debit Purchase... 9 Debit Purchase with Cash Back... 9 Debit Preauthorized Purchase and Completion... 9 Debit Preauthorized Purchase and Completion with Cash Back... 9 Debit Return... 9 Debit Balance Inquiry... 9 Debit Bill Payment... 10 Debit Reversal... 10 1.2 EBT TRANSACTIONS... 11 EBT Food Stamp Purchase... 11 EBT Food Stamp Return... 11 EBT Food Stamp Electronic Voucher... 11 EBT Cash Benefit Purchase... 11 EBT Cash Benefit Purchase with Cash Back... 11 EBT Cash Benefit Cash Withdrawal... 11 EBT Food Stamp Balance Inquiry... 11 EBT Cash Benefit Balance Inquiry... 11 EBT Reversal... 12 1.3 CREDIT TRANSACTIONS... 13 Credit Purchase... 13 Credit Purchase with Cash Back... 13 Credit Merchandise Return... 13 Credit Card Verification... 13 Credit Balance Inquiry... 13 Credit Advice... 13 Credit Bill Payment... 13 Credit Healthcare Auto-Substantiation... 14 Credit Reversal... 14 CHECK TRANSACTIONS... 15 Check Acceptance... 15 POS Check... 15 1.4 SETTLEMENT TRANSACTIONS... 16 Settlement Request/Response... 16 1.6 NETWORK MANAGEMENT... 17 Network Management Dynamic Key Exchange Messages... 17 Network Management Health Message ( ECHOTEST )... 17 Network Management LOGON Message... 17 Network Management LOGOFF Message... 18 1.7 CONTACTLESS PAYMENT PROGRAM... 19 General Description:... 19 Modifications to support contactless payment:... 19 Supported transactions:... 19 Changes to the Response Message:... 19 1.8 PIN TRANSLATION TRANSACTIONS... 20 1.9 TEST TRANSACTIONS... 21 Version 4.02 Page 2 Last modified August 12, 2009

1.10 REAL TIME CLEARING TRANSACTIONS... 22 2.0 MESSAGES FORMATS (GENERAL)...23 2.1 BIT MAPS... 23 2.2 MESSAGE HEADER... 24 2.3 NUMERIC PACKED DATA... 24 2.4 GUIDE TO TRANSACTION ATTRIBUTES AND FORMATS... 25 2.5 HEADER FORMAT... 27 3.0 DEBIT, CREDIT, EBT AND CHECK MESSAGE FORMATS...28 3.1 DEBIT AND EBT REQUEST MESSAGE... 28 3.2 DEBIT AND EBT RESPONSE MESSAGE... 33 3.3 DEBIT PREAUTHORIZED PURCHASE REQUEST MESSAGE... 36 3.4 DEBIT PREAUTHORIZED PURCHASE RESPONSE MESSAGE... 40 3.5 DEBIT PREAUTHORIZED PURCHASE COMPLETION REQUEST MESSAGE... 42 3.6 DEBIT PREAUTHORIZED PURCHASE COMPLETION RESPONSE MESSAGE... 45 3.7 DEBIT BILL PAYMENT REQUEST MESSAGE... 47 3.8 DEBIT BILL PAYMENT RESPONSE MESSAGE... 51 3.9 DEBIT AND EBT REVERSAL REQUEST MESSAGE... 54 3.10 DEBIT AND EBT REVERSAL RESPONSE MESSAGE... 59 3.11 CREDIT REQUEST MESSAGE... 62 3.12 CREDIT RESPONSE MESSAGE... 68 3.13 CREDIT BILL PAYMENT REQUEST MESSAGE... 73 3.14 CREDIT BILL PAYMENT RESPONSE MESSAGE... 79 3.15 CREDIT REVERSAL REQUEST MESSAGE... 83 3.16 CREDIT REVERSAL RESPONSE MESSAGE... 89 3.17 CREDIT ADVICE REQUEST MESSAGE... 92 3.18 CREDIT ADVICE RESPONSE MESSAGE... 97 3.19 CHECK ACCEPTANCE REQUEST MESSAGE... 100 3.20 CHECK ACCEPTANCE RESPONSE MESSAGE... 102 3.21 POS CHECK REQUEST MESSAGE... 104 3.22 POS CHECK RESPONSE MESSAGE... 107 3.23 POS CHECK REVERSAL REQUEST MESSAGE... 109 3.24 POS CHECK REVERSAL RESPONSE MESSAGE... 112 3.25 REAL TIME CLEARING REQUEST MESSAGE... 114 3.26 REAL TIME CLEARING RESPONSE MESSAGE... 118 3.27 REAL TIME CLEARING PREAUTHORIZED PURCHASE REQUEST MESSAGE... 121 3.28 REAL TIME CLEARING PREAUTHORIZED PURCHASE RESPONSE MESSAGE... 125 3.29 REAL TIME CLEARING PREAUTHORIZED PURCHASE COMPLETION REQUEST MESSAGE... 128 3.30 REAL TIME CLEARING PREAUTHORIZED PURCHASE COMPLETION RESPONSE MESSAGE... 132 3.31 REAL TIME CLEARING REVERSAL REQUEST MESSAGE... 135 3.32 REAL TIME CLEARING REVERSAL RESPONSE MESSAGE... 139 4.0 SETTLEMENT MESSAGE FORMATS...142 4.1 SETTLEMENT REQUEST... 142 4.2 SETTLEMENT RESPONSE... 144 5.0 NETWORK MANAGEMENT FORMATS...146 5.1 NETWORK MANAGEMENT REQUEST... 146 5.2 NETWORK MANAGEMENT RESPONSE... 148 6.0 PIN TRANSLATION FORMATS...149 Version 4.02 Page 3 Last modified August 12, 2009

6.1 PIN TRANSLATION REQUEST MESSAGE... 149 6.2 PIN TRANSLATION RESPONSE MESSAGE... 153 7.0 REJECTED MESSAGES...155 8.0 MESSAGE FLOWS...160 8.1 TRANSACTION MESSAGE FLOWS... 160 8.1.1 Debit & EBT Transaction Message Flows... 160 8.1.2 Credit Transaction Message Flows... 161 8.1.3 Check Acceptance Transaction Message Flows... 163 8.1.4 Settlement Transaction Message Flows... 164 8.2 NETWORK MANAGEMENT MESSAGE FLOWS... 165 8.3 PIN TRANSLATION MESSAGE FLOWS... 168 9.0 SUBMISSION & RESUBMISSION PROCESSING...169 9.1 OVERVIEW... 169 9.2 BANK OF AMERICA MERCHANT SERVICES SUPPORTED TRANSACTIONS... 169 9.3 MESSAGE ELEMENTS... 169 9.4 BANK OF AMERICA MERCHANT SERVICES NETWORK RULES... 170 APPENDIX A BIT INFORMATION...171 APPENDIX A BIT INFORMATION...171 MESSAGE TYPE... 171 SECONDARY BIT MAP (BIT 1)... 172 PRIMARY ACCOUNT NUMBER (BIT 2)... 173 PROCESSING CODE (BIT 3)... 174 AMOUNT 1 (BIT 4)... 175 TRANSMISSION DATE AND TIME (BIT 7)... 176 SYSTEM TRACE AUDIT NUMBER (BIT 11)... 177 LOCAL TIME (BIT 12)... 178 LOCAL DATE (BIT 13)... 179 EXPIRATION DATE (BIT 14)... 180 MERCHANT TYPE (BIT 18)... 181 ACQUIRING INSTITUTION COUNTRY CODE (BIT 19)... 182 POS ENTRY MODE (BIT 22)... 183 POS CONDITION CODE (BIT 25)... 184 POS PIN CAPTURE CODE (BIT 26)... 185 TRANSACTION FEE AMOUNT (BIT 28)... 186 ACQUIRING INSTITUTION ID CODE (BIT 32)... 187 FORWARDING INSTITUTION ID (BIT 33)... 188 TRACK 2 DATA (BIT 35)... 189 RETRIEVAL REFERENCE NUMBER (BIT 37)... 190 AUTH ID RESPONSE (BIT 38)... 191 RESPONSE CODE (BIT 39)... 192 CARD ACCEPTOR TERM ID (BIT 41)... 194 CARD ACCEPTOR ID CODE (BIT 42)... 195 CARD ACCEPTOR NAME / LOCATION (BIT 43)... 196 ADDITIONAL RESPONSE DATA (BIT 44)... 197 TRACK 1 DATA (BIT 45)... 200 ADDITIONAL DATA PRIVATE (BIT 48)... 201 POS Check usage... 204 Version 4.02 Page 4 Last modified August 12, 2009

TRANSACTION CURRENCY CODE (BIT 49)... 207 PIN DATA (BIT 52)... 208 SECURITY-RELATED CONTROL INFORMATION (BIT 53)... 209 ADDITIONAL AMOUNT (BIT 54)... 210 EBT Transactions... 210 Credit Healthcare Auto-Substantiation Purchase... 211 Transactions Involving Partial Authorization... 212 Debit and Credit Balance Inquiries... 212 Debit and Credit Financial Transactions... 213 EM AND CHIP DATA (BIT 55)... 214 NATIONAL POS GEOGRAPHIC DATA (BIT 59)... 215 ADDITIONAL POS INFORMATION (BIT 60)... 216 OTHER TRANSACTION AMOUNT (BIT 61.1)... 219 PAYMENT SERVICE FIELDS (BIT 62)... 220 PRIVATE-USE FIELD (BIT 63)... 223 TERTIARY BIT MAP (BIT 65)... 227 SETTLEMENT CODE (BIT 66)... 228 NETWORK MANAGEMENT INFORMATION CODE (BIT 70)... 229 CREDITS, NUMBER (BIT 74)... 230 CREDITS, REVERSAL NUMBER (BIT 75)... 231 DEBITS, NUMBER (BIT 76)... 232 DEBITS, REVERSAL NUMBER (BIT 77)... 233 CREDITS, AMOUNT (BIT 86)... 234 CREDITS, REVERSAL AMOUNT (BIT 87)... 235 DEBITS, AMOUNT (BIT 88)... 236 DEBITS, REVERSAL AMOUNT (BIT 89)... 237 ORIGINAL DATA ELEMENTS (BIT 90)... 238 REPLACEMENT AMOUNTS (BIT 95)... 239 MESSAGE SECURITY CODE (BIT 96)... 240 AMOUNT, NET SETTLEMENT (BIT 97)... 241 SETTLEMENT INSTITUTION ID CODE (BIT 99)... 242 RECEIVING INSTITUTION ID CODE (BIT 100)... 243 ACCOUNT ID 1 (BIT 102)... 244 TRANSACTION DESCRIPTION (BIT 104)... 245 DOUBLE-LENGTH DES KEY (BIT 105)... 246 ADDITIONAL PRIVATE DATA (BIT 111)... 247 TRANSPORT DATA (BIT 114)... 248 INTERCHANGE REFERENCE NUMBER (BIT 115)... 250 ADDRESS VERIFICATION DATA (BIT 123)... 251 SUPPORTING INFORMATION (BIT 125)... 252 Unformatted or parsed MICR data for POS Check transactions (usage 9)... 252 VISA PRIVATE USE FIELDS (BIT 126)... 254 PRIVATE USE DUKPT (BIT 127)... 258 NTIA COUPON DATA (BIT 163)... 259 LARGE PRIVATE DATA 1 (BIT 164)... 260 LARGE PRIVATE DATA 2 (BIT 165)... 261 LARGE PRIVATE DATA 3 (BIT 166)... 262 LARGE PRIVATE DATA 4 (BIT 167)... 263 ACQUIRER TRACE DATA (BIT 168)... 264 PAYEE PHONE (BIT 169)... 265 PRIVATE USE CARD ACCEPTOR STREET ADDRESS (BIT 170)... 266 PRIVATE USE GENERAL (BIT 171)... 267 POINT OF SERVICE DATA CODE (BIT 172)... 269 SETTLEMENT DATA (BIT 173)... 270 SUPPLEMENTAL DATA (BIT 177)... 274 PROMOTIONAL PROGRAM DATA (BIT 178)... 278 Version 4.02 Page 5 Last modified August 12, 2009

MESSAGING DATA (BIT 179)... 279 APPENDIX B KEY CHANGE MESSAGE OVERVIEW...280 APPENDIX C PROTOCOLS SUPPORTED...281 APPENDIX D TLV-FORMAT PROCESSING...282 APPENDIX E CHANGES TO THIS VERSION OF THE SPECIFICATION...284 Version 4.02 Page 6 Last modified August 12, 2009

This document contains information that is proprietary to Bank of America Merchant Services. This document may not be duplicated, used, or disclosed by the recipient for a purpose other than to evaluate the specifications described herein for the explicit purposeof transmitting authorizations to Bank of America Merchant Services MultiLink. The recipient must obtain written approval from Bank of America Merchant Services before disclosing the contents of this document to any third parties. Version 4.02 Page 7 Last modified August 12, 2009

Overview Bank of America Merchant Services is pleased to introduce you to the Bank of America Merchant Services MultiLink Authorization System. Bank of America Merchant Services MultiLink has been developed in the same quality fashion as Bank of America Merchant Services s entire family of products. Bank of America Merchant Services MultiLink authorization processing along with Bank of America Merchant Services s time-tested acquirer processing provides merchants with a complete Debit card, Credit card, EBT (Electronic Benefits), Check Acceptance and POS Check solution. This message specification outlines the requirements for Debit, Credit and EBT, Check Acceptance and POS Check authorization through the Bank of America Merchant Services MultiLink System. Several items will be covered: definitions of transaction types and how they are used, the Bank of America Merchant Services MultiLink format for synchronous communication, message types, message flows and data elements (bits), and appendices which give further details about the message types, individual fields and supported protocols. This manual makes use of the Microsoft Word Hyperlink feature to help you find information. If you are viewing an electronic copy of the manual with standard Word options set, hyperlinked data will appear underlined and in blue. Clicking on the hyperlinked text will take you to an area in the manual that will provide more information about the data. Also, the page numbers in the table of contents can be clicked on to go directly to that page (although the table of contents function of Word does not show these numbers in blue or underlined). If you have clicked on a hyperlink to take you to a particular place in the manual, you can return to where you came from by holding down the alt key and pressing the left-arrow key. If you are using a paper copy of the manual, data for which you can find additional information elsewhere will generally appear as underlined text. The most common use of this feature is the various bits in the detail message formats that are hyperlinked to Appendix A. Notice Bank of America Merchant Services reserves the right to make changes to specifications at any time and without notice. The information furnished in this publication is believed to be accurate and reliable; however, no responsibility is assumed by Bank of America Merchant Services for its use. See Appendix E for specific changes made to this version of the specification. Version 4.02 Page 8 Last modified August 12, 2009

1.0 Transactions Supported 1.1 Debit Transactions Debit Purchase The Purchase (or Sale) transaction is the most basic and common transaction, used for the purchase of goods or services. In a Purchase, the authorizing agent s system compares the cardholder s funds availability to the amount specified in the transaction. If the amount is available, the card issuer transmits an approval message to Bank of America Merchant Services. Bank of America Merchant Services sends the approval message to the point of sale (POS) device. If the amount is not available, Bank of America Merchant Services forwards the denial response from the card issuer to the merchant host. Bank of America Merchant Services also transmits error messages, time-outs or invalid PIN messages when received from the card issuer. These messages are relayed in the form of a two position response code. These response codes are listed in detail in Appendix A. This is a mandatory Debit transaction. Debit Purchase with Cash Back The Debit Purchase with Cash Back transaction allows a cardholder to purchase goods and receive cash through a single debit transaction. If a merchant chooses to offer this option, the merchant must prompt the cardholder for the desired cash back amount and allow the cardholder to verify the total amount being debited from their account. The cash back amount must be included in the transaction amount being approved and stored separately in an additional amount field per debit network regulations. This is an optional Debit transaction. Debit Preauthorized Purchase and Completion The Preauthorized Purchase transaction allows retailers to put a hold on a customer s funds for a specified amount that is preset by the merchant s POS. The Preauthorized Purchase Completion transaction completes the transaction for which funds have previously been placed on hold. The completion amount specified can be any amount up to that specified in the approved preauthorization. The preauthorization holds the funds; the completion is the act of removing the funds up to the preauthorization amount from the customer's account. This is an optional Debit transaction, but if the merchant chooses to support the transaction, all conditions listed above must be met. Debit Preauthorized Purchase and Completion with Cash Back The Debit Preauthorized Purchase and Completion with Cash Back transaction allows a cardholder to purchase goods and receive cash back. If a merchant chooses to offer this option, the merchant must prompt the cardholder for the desired cash back amount and allow the cardholder to verify the total amount being debited from their account. The cash back amount must be included in the transaction amount being approved and stored separately in an additional amount field per debit network regulations. This is an optional Debit transaction, but if the merchant chooses to support the transaction, all conditions listed above must be met. Debit Return By entering a return transaction the merchant electronically refunds the cardholder s debit account. It would be used, for example, when a customer returns merchandise or if a Purchase transaction was completed in error. Debit card returns must be performed on-line and requires the entry of the cardholder PIN. Note: Not all networks allow this type of transaction. Please contact your Bank of America Merchant Services Relationship Manager for specifics. This is an optional Debit transaction. Debit Balance Inquiry The issuer has the option of returning multiple balances in the balance inquiry transaction (e.g. current ledger and/or available balances for checking, savings, etc.). It is entirely up to the issuer as to what and how many balances are returned. There type of balance and account are indicated in the response message. Version 4.02 Page 9 Last modified August 12, 2009

Debit Bill Payment The Debit Bill Payment transaction is a 3 rd -party payment, such as a utility or other bill. This transaction is unique among debit transactions in that it does not include a PIN. It is always a manual entry transaction (either VRU or Internet). There are several fields that are required for Debit Bill Payment that are not used for other Debit transactions. This is an optional Debit transaction and is only available by prior arrangement with your Bank of America Merchant Services representative. Debit Reversal Debit Purchase Debit Purchase with Cash Back Debit Preauthorized Purchase Debit Preauthorized Purchase with Cash Back Debit Preauthorized Completion Debit Preauthorized Completion with Cash Back Debit Return Debit Bill Payment System or communication reversals are generated due to a problem in successfully delivering the response to the merchant host, either because of a device or line problem or a late or missing response from the back-end authorizer. Debit card reversal requests are immediately switched back to the issuer. A debit purchase transaction immediately followed by a successful debit reversal should have no net financial effect on the cardholder account. This is a mandatory Debit transaction. Version 4.02 Page 10 Last modified August 12, 2009

1.2 EBT Transactions EBT Food Stamp Purchase In a food stamp purchase transaction, the cardholder presents his state-issued electronic benefits card for the eligible purchase of merchandise. The merchant swipes (or key enters) the card and the cardholder enters his PIN number. The transaction is switched through the Bank of America Merchant Services MultiLink network to the EBT provider processor. The EBT provider processor makes the approval/decline decision and forwards the response back to Bank of America Merchant Services. The Bank of America Merchant Services MultiLink system in turn sends the response to the merchant host. The balance remaining on the account may be present in the response message and printed on the cardholder receipt for approved transactions. This is a mandatory EBT transaction. EBT Food Stamp Return By entering a food stamp return transaction the merchant electronically refunds the cardholder s EBT account. It would be used, for example, when a customer returns merchandise or if a Purchase transaction was completed in error. Food Stamp returns must be performed on-line and the original card must be present to complete this transaction. This transaction requires the entry of the cardholder s PIN number. This is a mandatory EBT transaction. EBT Food Stamp Electronic Voucher If an EBT card is presented for a purchase and the merchant host is temporarily unable to connect with the EBT network, a voice approval may be obtained. Some states require that the manual draft be mailed in, while others require that the transaction be sent electronically (similar to a credit card force transaction, however, it will dial out to the EBT network.) This transaction is mandatory if a voice approval is obtained. Please contact your Bank of America Merchant Services Relationship Manager for details on states' requirements. EBT Cash Benefit Purchase This transaction operates in the same manner as the EBT Food Stamp Purchase, however, the cardholder has less restrictions on the merchandise purchased. This is a mandatory EBT transaction. EBT Cash Benefit Purchase with Cash Back This transaction operates in the same manner as the EBT Cash Benefit Purchase, however, the cardholder may purchase goods and receive cash through a single transaction. The cash back option must be prompted on each transaction, similar to debit. In the message to the Bank of America Merchant Services MultiLink system, the cash back amount must be segregated from the merchandise amount. This is a mandatory EBT transaction. EBT Cash Benefit Cash Withdrawal This transaction operates in the same manner as the EBT Cash Benefit Purchase, except that no goods are purchased. This is an optional EBT transaction. EBT Food Stamp Balance Inquiry The EBT Food Stamp Balance Inquiry transaction allows the cardholder to request information on the amount of funds available in the account that funds the EBT card. This is an optional EBT transaction. EBT Cash Benefit Balance Inquiry The EBT Cash Benefit Balance Inquiry transaction allows the cardholder to request information on the amount of funds available in the account that funds the EBT card. This is an optional EBT transaction. Version 4.02 Page 11 Last modified August 12, 2009

EBT Reversal EBT Food Stamp Purchase EBT Food Stamp Return EBT Cash Benefit Purchase EBT Cash Benefit Purchase with Cash Back EBT Cash Benefit Cash Withdrawal System or communication reversals are generated due to problems in successfully delivering the response to the merchant host, either because of a device or line problem or a late or missing response from the back-end authorizer. EBT reversal requests are immediately switched back through the EBT network. An EBT transaction immediately followed by a successful EBT system reversal should have no net financial effect on the cardholder account. This is a mandatory EBT transaction. Version 4.02 Page 12 Last modified August 12, 2009

1.3 Credit Transactions Credit Purchase The Purchase (or Sale) transaction is the most basic and common transaction, used for the purchase of goods or services. In a Purchase, the authorizing agent s system compares the cardholder s remaining credit limit to the amount specified in the transaction. If the amount is available, the card issuer transmits an approval message to Bank of America Merchant Services. Bank of America Merchant Services sends the approval message to the point of sale (POS) device. If the amount is not available, Bank of America Merchant Services forwards the denial response from the card issuer to the merchant host. Bank of America Merchant Services also transmits error messages or time-outs when received from the card issuer. These messages are relayed in the form of a twoposition response code. These response codes are listed in detail in Appendix A. This is a mandatory Credit transaction. Credit Purchase with Cash Back The Credit Purchase with Cash Back transaction allows a cardholder to purchase goods and receive cash through a single credit transaction. If a merchant chooses to offer this option, the merchant must prompt the cardholder for the desired cash back amount and allow the cardholder to verify the total amount being debited from their account. The cash back amount must be included in the transaction amount being approved and stored separately in an additional amount field per credit network regulations. This is an optional Credit transaction. Credit Merchandise Return The Merchandise Return transaction is a standalone transaction resulting from the return of merchandise to the point of purchase. The net result of a completed Merchandise Return will be to increase the customer s available credit by the amount of the return (after settlement). It should not be confused with a reversal, which is generated as a result of an inability to generate a timely approval or an immediate cancellation of the transaction at the merchant host. See below for a description of reversal transactions. This is a mandatory Credit transaction. Credit Card Verification The Card Verification transaction gives the merchant a means of verifying the validity of a card without performing a financial transaction. This is an optional Credit transaction. Credit Balance Inquiry The issuer has the option of returning multiple balances in the balance inquiry transaction (typically, credit amount available to customer open to buy and credit limit). It is entirely up to the issuer as to what and how many balances are returned. The type of balance is indicated in the response message. Credit Advice The Credit Advice transaction allows merchants utilizing Bank of America Merchant Services 's Host Capture product to submit transactions for settlement that have been authorized via another means other than MultiLink. These offline transactions were performed either by voice authorization or through an alternative authorization platform. No further authorization processing is performed on Credit Advice transactions. This is an optional Credit transaction. Credit Bill Payment The Credit Bill Payment transaction is a 3 rd -party payment, such as a utility or other bill. It is always a manual entry transaction (either VRU or Internet). There are several fields that are required for Credit Bill Payment that are not used for other Credit transactions. This is an optional Credit transaction and is only available by prior arrangement with your Bank of America Merchant Services representative. Version 4.02 Page 13 Last modified August 12, 2009

Credit Healthcare Auto-Substantiation Auto-Substantiation is the real-time process of verifying that purchase transactions are for expenses permitted and eligible under IRS regulations for Flexible Spending Accounts (FSA) and Health Reimbursement Arrangements (HRA). It provides a cost effective way of substantiating purchases of over-the-counter (OTC) qualified healthcare products made with FSA/HRA cards, improving efficiency for benefit administrators and reducing requests for paper documentation. The Healthcare Auto-Substantiation Transaction permits employers and their third-party benefit administrators to approve qualified healthcare expenses at the time of purchase at participating merchants. Auto- Substantiation is supported for Purchase, Merchandise Return and Reversal transactions. Additional fields needed for Auto-substantiation are included within the Credit Purchase, Credit Merchandise Return and Credit Reversal message format sections. Use of these transactions requires prior arrangement with your Bank of America Merchant Services representative. Credit Reversal Credit Purchase Credit Merchandise Return Credit Bill Payment System or communication reversals are generated due to problems in successfully delivering the response to the merchant host, either because of a device or line problem or a late or missing response from the back-end authorizer. Credit reversal requests are immediately switched back through the Credit network. A Credit transaction immediately followed by a successful Credit system reversal should have no net financial effect on the cardholder account. A reversal of a partially-authorized Credit transaction is mandatory, but all other Credit reversals are optional transactions. Version 4.02 Page 14 Last modified August 12, 2009

Check Transactions Check Acceptance Bank of America Merchant Services s MultiLink processing platform supports a form of check verification and guarantee called check acceptance. When a merchant receives payment in the form of a check, the checking account number and the transaction amount, along with some customer identification information, is passed to the MultiLink platform for authorization. The information is reformatted and passed to the appropriate check acceptance vendor for authorization and the response is sent back to the merchant. POS Check The VISA POS Check Service offers merchants the ability to accept consumer and business checks as source documents and convert the paper checks to electronic transactions at the point of sale, and from mail, telephone or electronic commerce merchants. When a customer pays for a purchase with a paper check, the sales clerk informs the customer that the check is being used as a source document to convert it to an electronic transaction by passing the check through a check reader. It captures checking account information from the Magnetic Ink Character Recognition (MICR) line of data encoded on a customer s check. The service offers three options for converting checks at the point of sale: Conversion only, in which the authorization request is routed to the participating drawee financial institution or a third-party authorizing agent, which approves or declines the transaction by checking the status of the account. The merchant retains the risk of loss. Verification with conversion, in which the authorization request is routed to the participating drawee financial institution or a third-party authorizing agent for verification of the probability that the transaction will be paid by the customer. The participating drawee financial institution makes an approval or decline decision based on access to the demand deposit account and information on funds availability at the time of the request. The third-party authorizing agent makes an approval or decline decision based on its risk management database. The merchant retains the risk of loss. Guarantee with conversion, in which the authorization request is routed to the participating drawee financial institution or a third-party authorizing agent to guarantee the transaction. If the transaction is approved, the risk of loss is transferred to the participating drawee financial institution or third-party authorizing agent, provided all merchant acceptance criteria have been met. The guarantor bears the risk of loss. The VISA POS Check Service is a separate service with different message formats and processing requirements from the Check Acceptance, service described previously. Informaton in this manual will be specifically referenced by check acceptance or POS Check to differentiate between the services. Please contact your Bank of America Merchant Services representative for more information on either of these services. Version 4.02 Page 15 Last modified August 12, 2009

1.4 Settlement Transactions Settlement Request/Response The Settlement Request transaction is an optional transaction that the merchant may send to indicate that end-ofday has occurred for a store or for their system. This transaction may be used in conjunction with Bank of America Merchant Services s fixed end-of-day processing time or it may replace that time. The merchant may choose to send end-of-day transaction totals in the Settlement Request. The Settlement Request transaction is acknowledged by a Settlement Response transaction from Bank of America Merchant Services. The Settlement Response transaction echoes any totals sent by the Settlement Request transaction back to the merchant. Use of these transactions requires special arrangement with Bank of America Merchant Services. Contact your account representative for more information about the use of this transaction. Version 4.02 Page 16 Last modified August 12, 2009

1.6 Network Management Network management processing aids in ensuring that maximum connectivity is maintained between all network end points. Network management is an essential function, allowing the network to quickly identify and resolve communication problems as they may arise. Bank of America Merchant Services supports the following Network Management messages: Key Change Echotest Logon Logoff Network Management Dynamic Key Exchange Messages If the merchant chooses to utilize Dynamic Key Exchange, there are several options for initiating the key exchange and more than one option may be utilized. Bank of America Merchant Services can send a new PIN Encryption key after a LOGON message has been processed, after a specified number of minutes/hours/days has elapsed and/or via an operator command. The merchant can request a new PIN encryption key at any time. If the merchant initiates the request, a Network Management Dynamic Key Exchange Request message is sent by the merchant to request a new PIN Encryption Key. This message is acknowledged by Bank of America Merchant Services with a Network Management Dynamic Key Exchange Request Response message, followed by a Network Management Dynamic Key Exchange message containing the new key. The merchant acknowledges receipt of the key with a Network Management Dynamic Key Exchange Response message. If the key exchange is initiated by Bank of America Merchant Services (either at logon, by timer or operator command), Bank of America Merchant Services will send the Network Management Dynamic Key Exchange message and the merchant will acknowledge receipt of the key with a Network Management Dynamic Key Exchange Response message. Please refer to the Network Management Formats section (Section 4.0) for further information on the message details, Appendix A Bit Information for specific field values and Appendix B Key Change Message Overview for additional information. Network Management Health Message ( ECHOTEST ) The Network Management Health message or echotest is sent by Bank of America Merchant Services and is answered by the merchant to determine connectivity status. The receipt of a response validates that the connection is still active and the lack of traffic is not the result of a communication problem. At the merchant s option, the merchant may also send a Network Management Health message and have it answered by Bank of America Merchant Services. Bit 070, the Network Management Information identifies which type of task is required. Please refer to Appendix A Bit Information for further information on the values which may be sent in this bit. The Bank of America Merchant Services-initiated Health message and merchant response is a mandatory transaction. Network Management LOGON Message The Network Management Logon message is sent by either Bank of America Merchant Services or the merchant to indicate the beginning of transaction processing. Functionally, a logon message is identical to an echo test message. The receipt of a response validates that the connection is active and processing of traffic is ready to commence. Bit 070, the Network Management Information identifies which type of task is being requested. Please refer to Appendix A Bit Information for further information on the values which may be sent in this bit. The Bank of America Merchant Services-initiated Logon message and merchant response is a mandatory transaction. Version 4.02 Page 17 Last modified August 12, 2009

Network Management LOGOFF Message The Network Management Logoff message is sent by either Bank of America Merchant Services or the merchant to indicate that transaction processing is ending or being suspended. Typically a Logoff message is sent when the network or merchant plan on stopping their applications for any reason. This reduces unnecessary concerns over communication issues arising as a result of the application not being available. The receipt of a response validates that the processing of traffic is suspended. Bank of America Merchant Services will decline transaction traffic received when the merchant is not logged onto the network. Bit 070, the Network Management Information identifies which type of task is being requested. Please refer to Appendix A Bit Information for further information on the values that may be sent in this bit. The Bank of America Merchant Services-initiated Logoff message and merchant response is a mandatory transaction. Version 4.02 Page 18 Last modified August 12, 2009

1.7 Contactless Payment Program General Description: Bank of America Merchant Services is pleased to provide support for contactless payment (also referred to as RFID or proximity payments). This method of payment is one where a wireless technology is used to transmit data from the payment device (usually a chip card) to a contactless payment terminal. There are two forms of transmission from the payment device one that processes Track2 data that is normally retrieved from the magnetic stripe (magnetic stripe data rules), and one that supports an enhanced process that utilizes the computer embedded on the chip card to improve the security of the transaction (chip data rules). This initial implementation will support the magnetic stripe data rules where Track2 data is processed. Future implementations will support the chip data rules (i.e. Visa Smart Debit Visa Smart Credit (VSDC) cards). Contactless payments support both credit or debit transactions. A standard Multilink message is utilized to support the payment with some minor modifications. Modifications to support contactless payment: First and foremost, new POS entry mode values are required. Two new values are supported 91 and 07. (The value 07 is reserved for use with the enhanced smart cards and is not part of this initial implementation.) The values of the POS entry mode have the following meanings: 07 - Contactless chip transaction using chip data rules; 91 - Contactless transaction originated using magnetic stripe data rules; CVV or dcvv check is possible. A complete Track2 must be sent on the transaction in field 35. A contactless payment transaction utilizes a dynamic Track2. It includes issuer discretionary data (IDD) and an account transaction counter (ATC). The payment device may also generate a dynamic card verification value (dcvv) that is included in the Track2 data. This data must be provided on the authorization request in its entirety and without modification. The contactless payment device generates the dcvv by using a Unique Derived Key (UDK) which was generated by using the account number (PAN) and the PAN sequence number along with a unique cryptographic key embedded on the chip. This method provides a different key for calculating the dcvv for each transaction, enhancing the security of the card. The merchant must identify that a terminal is capable of processing contactless payments even if the payment from a contactless payment device is processed using a magnetic stripe read. This is indicated by entering a value of 8 in Terminal Entry Capability (Bit 60.2). Supported transactions: Contactless payment is supported in credit authorizations (0100), advices (0120) and reversals (0400). It is also supported in debit preauthorizations (0100), original financial requests (0200), purchase with cash back (0200), balance inquiry (0200), preauthorization completions (0220), and authorization reversals (0400). Changes to the Response Message: The issuer is responsible for verifying the dcvv in a transaction where the Track2 data contains the contactless indicator. CVV results code (Bit 44.5) will contain a 2 (passed) if the dcvv is correct. This field will contain a 1 (failed) if the dcvv does not pass. The response code (Bit 39) for a failure to authenticate dcvv is a general decline (05). Version 4.02 Page 19 Last modified August 12, 2009

1.8 PIN Translation Transactions PIN Translation transactions provide the ability for the merchant to have the transaction s PIN block encrypted under the merchant s standard key translated by Bank of America Merchant Services to encryption under a different key and returned to the merchant. No authorization is performed when using this transaction. Please contact your Bank of America Merchant Services representative for more information on this service. Version 4.02 Page 20 Last modified August 12, 2009

1.9 Test Transactions The test transaction is a facility by which the merchant can initiate a transaction that will validate the capabilities of a card. Although the amount field is set to $1.00, this is a non-financial transaction that will have no settlement impact. The only currently-supported implementation of the test transaction is the MasterCard recurring payment test transaction. An approved recurring payment test transaction response indicates that the card is capable of accepting recurring payments. Version 4.02 Page 21 Last modified August 12, 2009

1.10 Real Time Clearing Transactions Real Time Clearing is a signature-based processing model to support the unique needs of fuel merchants, designed to enhance the consumer and merchant experience at Automated Fuel Dispensers. This product will potentially reduce chargebacks and increase average purchase amounts through lower incidence of pump shut-offs. It provides extended chargeback protection and interchange qualification for fuel transactions. Transactions supported under this service are: Real Time Clearing Purchase (in-store at fuel merchant) Real Time Clearing Merchandise Return Real Time clearing Preauthorization and Completion Real Time Clearing Reversal for each transaction listed above Merchants will indicate their desire to have a particular transaction processed as real time clearing by setting a field in the request message. If the transaction is eligible for real time clearing, Bank of America Merchant Services will indicate this with an entry in the same field, as well as indicating the entity (VISA, etc. that performed the real time clearing). If the transaction is not eligible for real time clearing, this will also be indicated in the response. Note: Not all authorizers support real time clearing at this time. If Bank of America Merchant Services indicates in the response that a transaction is not eligible for real time clearing, then the merchant must include this transaction in their offsite settlement file (if they do not participate in Bank of America s Host Draft Capture program). Version 4.02 Page 22 Last modified August 12, 2009

2.0 Messages Formats (GENERAL) Bank of America Merchant Services MultiLink supports Bank of America Merchant Services s bit-mapped message format for all messages. This message format maximizes efficiency of transaction data by the use of bit mapping. The bit map or maps define the presence of data fields within a message. Data fields not applicable to a particular transaction are simply not sent and their corresponding bit in the bit map is turned off (set to zero). There is no need to delimit the fields not present with a string of field separators. The fields within a message may be fixed or variable in length. If fixed, numeric fields must be right-justified, zero-filled and alphanumeric fields leftjustified and space-filled, unless specifically noted. If variable, the length of the field is defined by a length field before the data field itself.. All fields are designated in the tables below as req (required for this message), cond (conditional may be required, depending on the specifics of the transaction. See details in the description column and/or in Appendix A), opt (optional may be sent at the discretion of the merchant or if available. See details in the description column and/or in Appendix A) or N/A (not applicable Not currently used, but included in this document so that merchant processors can at least code for the length of the field, should it ever be present). IMPORTANT: Not all fields defined in the tables below are in current use. However, it is very important that merchant processors be capable of receiving all listed fields in any message sent by Bank of America Merchant Services. Bank of America Merchant Services MultiLink messages use the EBCDIC character set. 2.1 Bit Maps This message format utilizes bit maps to define which data fields are present in a message. If a bit is set to on, the data element corresponding to that bit number is present in the message. If a bit is set to off, the data element corresponding to that bit number is not present in the message. Bit maps are made up of 64 binary characters, with a 0 indicating the bit is off and a 1 indicating the bit is on. For example, if the first 8 bits, depicted in binary, of the bit map are 10001101, this signifies that bits, 1,5,6 and 8 are present and bits 2,3,4 and 7 are not utilized. Bank of America Merchant Services MultiLink utilizes primary, secondary and tertiary bit maps. The primary bit map represents data fields 2 through 64. The secondary bit map represents bits 66 through 128. The tertiary bit map represents bits 130 through 192. Data fields 1, 65 and 129 can not exist, as these bits are used to indicate presence of subsequent bit maps. In the message formats below, the secondary bit map is listed as bit number 001, since its presence is indicated by bit 1. The tertiary bit map is listed as bit number 065, since its presence is indicated by bit 65 (bit 1 of the secondary bit map). The secondary bit map is only required if data elements represented by bits 66 through 128 or the tertiary bit map are to be used in a particular message. Likewise, the tertiary bit map is only required if data elements represented by bits 130 through 192 are to be used in a particular message. Bit 1 of the primary bit map indicates the presence or absence of the secondary bit map. Bit 1 of the secondary bit map indicates the presence or absence of the tertiary bit map. Bit 1 of the tertiary bit map indicates the presence or absence of the (currently unused) quaternary bit map. Version 4.02 Page 23 Last modified August 12, 2009

2.2 Message Header All messages are made up of two parts: the header and the actual message (unique format and variable length for each message type). The header does not have a bit map associated with it, as all fields are required. The only exception to this is the case of a rejected message, which will contain two additional fields in the header. See Section 2.5 (Header Format) and Section 5 (Rejected Messages) for details on rejected messages. 2.3 Numeric Packed Data In order to minimize the size of transmitted messages, some numeric fields are designated as Numeric Packed (also referred to as Binary d Decimal). This technique consists of using 4 bits for each numeric character or hex character A through F (as field separator). Odd-length fields are padded with a leading zero. For example, the numeric field 1234 would be represented in Numeric Packed format as %H12 34 (binary 00010010 00110100), 678 would be represented as %H06 78 (binary 00000110 01111000), while 23F1 would be represented as %H23 F1 (binary 00100011 11110001). Version 4.02 Page 24 Last modified August 12, 2009

2.4 Guide to Transaction Attributes and Formats Attribute Description Explanation Anx Alpha-numeric (x indicates number of bytes). Nx Numeric (x indicates number of bytes) NPx Numeric packed (Binary d Decimal) (x indicates number of characters, not bytes). An odd number will be padded with a leading zero. NSx Numeric with special characters (x indicates number of bytes) ANSx Alpha-numeric with special characters (x indicates number of bytes) Bx Binary (x indicates number of bytes) TLV(xy)zzz Tag-Length-Value format. (x indicates length of each tag, y indicates length of each each tag length field and z indicates the total number of bytes). Note there are also some non-standard TLV-format fields supported. These are indicated by TLV(**)zzz. See individual field descriptions in Appendix A for more information. Format Description Fixed LLVAR LLLVAR BBVAR BBBVAR Explanation Fixed length field. Variable length field where the maximum size of the field is 255 characters and LL represents a one-byte binary field indicating the length of the data to follow, expressed as the number of characters. If a field contains subfields, regardless of the attributes of each subfield, the length is instead expressed as the number of bytes. Variable length bit where the maximum size of the field is 999 characters and LLL represents a two-byte binary field indicating the length of the data to follow, expressed as the number of characters. If a field contains subfields, regardless of the attributes of each subfield, the length is instead expressed as the number of bytes. Variable length field where the maximum size of the field is 255 characters and BB represents a one-byte binary field indicating the length of the data to follow, expressed as the number of bytes. Variable length field where the maximum size of the field is 999 characters and BBB represents a two-byte binary field indicating the length of the data to follow, expressed as the number of bytes. Version 4.02 Page 25 Last modified August 12, 2009

Notes: NPx (numeric packed) fields with an odd length (e.g. NP3) will be padded with a leading zero. For example, an NP3 field with a value of 246 would be represented as hexadecimal 02 46. NPx (numeric packed) fields of variable length with length expressed as number of characters (format LLVAR or LLLVAR) will have the length field containing the actual number of packed characters. In the case of an odd actual number of characters, the length field will contain this odd number (it will not include the leading zero in the count). Version 4.02 Page 26 Last modified August 12, 2009

2.5 Header Format All messages begin with a fixed-length and fixed-format header, as follows: Field Data Element Description Format Attr Presence Number Name 1 Header Length Specifies the number of bytes in this header. Fixed B1 Req Value: 16 (hex) for normal messages; 1A (hex) for rejected messages. See Section 5 for details on rejected messages. 2 Header Flag Specifies the presence or absence of a Fixed B1 Req and Format message header following this header, and the format of this message header, if present. Value: 1 (hex) if no header following this header; 81 (hex) if another header following this one (indicates a rejected message). 3 Text Format Specifies message data field format. Value: 2 Fixed B1 Req 4 Total Message Length 5 Destination Station ID 6 Source Station ID 7 Round Trip Control Information (hex). Specifies the total length of this message in bytes, from the start of the header to the end of the message. The station number to which this message is routed. Must be a defined station number on the Bank of America Merchant Services network. The station number used to send this message (generally, the same as header field 5). Must be a defined station number on the Bank of America Merchant Services network. Fixed B2 Req Fixed NP6 Req Fixed NP6 Req Reserved. Value: 0 (hex). Fixed B1 Req 8 BASE I Flags Reserved. Value: 0 (hex). Fixed B2 Req 9 Message Used to control processing of message. Fixed B3 Req Status Flags Value: 0 (hex). 10 Batch Number Reserved. Value: 0 (hex). Fixed B1 Req 11 Reserved Reserved. Value: 0 (hex). Fixed B3 Req 12 User Information A value defined by the acquirer that can be used as needed to facilitate processing. Fixed B1 Req Value: 0 (hex). 13 Bit Map Only present in rejected messages. The high-order bit will be = 1, indicating the presence of field 14. See Section 6 for details on rejected messages. 14 Bit Map Reject Data Group Only present in rejected messages. Contains a 4-digit reject code. See Section 6 for details on rejected messages and valid reject codes. Fixed B2 Cond Fixed B2 Cond Version 4.02 Page 27 Last modified August 12, 2009

3.0 Debit, Credit, EBT and Check Message Formats 3.1 Debit and EBT Request Message 3.1.1 Debit Purchase 3.1.2 Debit Purchase with Cash Back 3.1.3 Debit Return 3.1.4 Debit Balance Inquiry 3.1.5 EBT Food Stamp Purchase 3.1.6 EBT Cash Benefit Purchase 3.1.7 EBT Cash Benefit Purchase with Cash Back 3.1.8 EBT Cash Benefit Cash Withdrawal 3.1.9 EBT Food Stamp Return 3.1.10 EBT Food Stamp Balance Inquiry 3.1.11 EBT Cash Benefit Balance Inquiry 3.1.12 EBT Food Stamp Electronic Voucher This message is used to send a request message from the POS to Bank of America Merchant Services MultiLink for a Debit, EBT Food Stamp or EBT Cash Benefit transaction. The Debit and EBT Cash Benefit transactions may be with or without cash back. The Processing field (bit 3) differentiates the transaction type. The chart below describes: Bit Numbers and Names of all possible data elements for this message If constant, the value to be placed in the field A description of how each data element is used The format and attributes of each data element Required, Optional, Conditional or Not Applicable status of each data element Bit Number Data Element Name Message Type Description Format Attr Presence Value to represent the type of message Value: 0200. See Appendix A. Fixed NP4 Req Represents the presence of secondary bit Fixed B8 Req map and data elements in bits 2 through 64. Represents the presence of tertiary bit map Fixed B8 Cond and data elements in bits 66 through 128. Represents the presence of data elements in Fixed B8 Cond bits 130 through 192. Contains the cardholder account number. LLVAR NP19 Req Primary Bit Map 001 Secondary Bit Map 065 Tertiary Bit Map 002 Primary Account Number 003 Processing Defines the type of transaction. See Appendix A. 004 Amount 1 Transaction Amount. Assumes a 2 position decimal, right-justified, zero filled. This field contains the total amount including the purchase amount and cash back if indicated. Transactions settled through Bank of America Merchant Services s settlement system are limited to 7 characters ($99,999.99). Fixed NP6 Req Fixed NP12 Req Version 4.02 Page 28 Last modified August 12, 2009

Debit and EBT Request Message (Continued) Bit Data Element Number Name 007 Transmission Date and Time Description Format Attr Presence Date and Time transaction is sent through the network assigned by the originator. Expressed in GMT MMDDhhmmss. A number assigned by the message initiator 011 System Trace Audit Number that identifies a cardholder transaction. 012 Local Time Time of the transaction, in merchant s local time. This value stays constant throughout the life of the transaction. This field must be sent in the settlement file. Expressed as hhmmss. For submissions and resubmissions, this is the time of the original transaction. 013 Local Date Date of the transaction, in merchant s local date. This value stays constant throughout the life of the transaction. This field must be sent in the settlement file. Expressed as MMDD. For submissions and resubmissions, this is the date of the original transaction. 014 Expiration Date 018 Merchant Type 019 Acquiring Institution Country 022 POS Entry Mode 025 POS Condition 026 POS PIN Capture 032 Acquiring Institution ID 033 Forwarding Institution ID Contains the expiration date on the card. If the card does not have an expiration date, do not send this bit. Expressed as YYMM. Merchant Category (MCC). Bank of America Merchant Services-assigned value. Identifies the country of the location where the transaction occurred. See Appendix A for values. Defines the method of data entry of the account number and whether a PIN was entered on this transaction. See Appendix A for values. Describes the condition under which the transaction takes place at the point of service. See Appendix A for values. Contains a value indicating the maximum number of PIN characters that can be accepted by the point-of-service device. See Appendix A. Identifies the financial institution acting as the acquirer of this transaction. Value is constant for all transaction requests and responses. This is an Bank of America Merchant Services -assigned identification number. Value 45592900000. Identifies the processor that forwards the request to Bank of America Merchant Services, if that processor is different from the institution indicated in field 032. This is an Bank of America Merchant Servicesassigned identification number. Fixed NP10 Req Fixed NP6 Req Fixed NP6 Req Fixed NP4 Req Fixed NP4 Cond Fixed NP4 Req Fixed NP3 Req Fixed NP4 Req Fixed NP2 Req Fixed NP2 Cond LLVAR NP11 Req LLVAR NP11 Cond Version 4.02 Page 29 Last modified August 12, 2009

Debit and EBT Request Message (Continued) Bit Data Element Description Format Attr Presence Number Name 035 Track 2 Data Unaltered contents of the data read off Track LLVAR NP37 Cond 2 of the mag stripe, excluding the beginning and ending sentinels and LRC characters. Required for Debit transactions. This field is only present when Track 2 has been read or assembled via a contactless means at the terminal. 037 Retrieval Reference Number A number used with other data elements as a key to identify and track all messages related to a given customer transaction or series of system messages. The format for this field is YDDDHHNNNNNN, where YDDD is the date in Julian format, HH is the hour and N-N is a Fixed AN12 Req 038 Auth ID Response 041 Card Acceptor Term ID 042 Card Acceptor ID 043 Card Acceptor Name / Location 049 Transaction Currency 6 digit transaction number. The authorization code provided by the issuer when a transaction is approved. Will only be present for EBT transactions that were previously authorized offline. Unique terminal/device ID. Merchant-defined value. Merchant ID. Assigned by Bank of America Merchant Services. See Appendix A. Name and location of the card acceptor where the transaction occurred. See Appendix A. Positions: 1-25 Card acceptor name 26-38 City name 39-40 Alpha country code ISO defined code representing the currency of this transaction. 052 PIN Data Contains a PIN or password, encrypted and formatted as a block of 16 hexadecimal digits or contains the 16 hexadecimal digits of a DUKPT PIN block (depending on what is specified in field 53). If a DUKPT PIN block is used, the Key Serial Number is passed in field 127. See Appendix A. 053 Security- Related Control Information 055 EM and Chip Data 059 National POS Geographic Data Data used by the issuer to process PINs. See Appendix A for field details. Electronic Magnetic Signature and chip data. See Appendix A. A field to describe the location of the card acceptor within the country. See Appendix A for values. Fixed AN6 Req for EBT offline auth only Fixed ANS8 Req Fixed Fixed ANS 15 ANS 40 Req Req Fixed NP3 Req Fixed B8 Req (N/A for EBT Voucher, Debit Resubmission) Fixed NP16 Req (N/A for EBT Voucher, Debit Resubmisision) BBVAR LLVAR TLV (**) 255 ANS 14 Cond Cond Version 4.02 Page 30 Last modified August 12, 2009

Debit and EBT Request Message (Continued) Bit Data Element Number Name 060 Additional POS Info 060.1 Terminal Type 060.2 Terminal Entry Capability 060.3 Chip Condition 060.4 Special Condition Indicator Existing Debt 060.5 Merchant Group Indicator 060.6 Chip Transaction Indicator 060.7 Chip Authentication Reliability Indicator 060.8 Mail Order / Telephone Order / Electronic Commerce Indicator Description Format Attr Presence A group of subfields that provide additional information about the point of service. See Appendix A for values. Identifies the point-of-service terminal. See Appendix A for values. Identifies the terminal s capability to electronically read account numbers and expiration dates from cards. See Appendix A for values. Provides information about VSDC cards when read at VSDC terminals. See Appendix A for values. Indicates whether a payment is being made on an existing debt. See Appendix A for values. Identifies the general category of the card acceptor and transaction. See Appendix A for values. Set when message from the terminal is for a VSDC transaction. See Appendix A for values. Indicates the reliability of a transaction in the VSDC environment. See Appendix A for values. Identifies the type of mail or telephone order or the level of security used in en e- commerce transaction over an open network. See Appendix A for values. BBVAR Var. by use Req Fixed NP1 Req Fixed NP1 Req Fixed NP1 Cond Fixed NP1 Cond Fixed NP2 Cond Fixed NP1 Cond Fixed NP1 Cond Fixed NP2 Cond 060.9 Cardholder ID Identifies the method of transaction Fixed NP1 Cond Method authentication. See Appendix A for values. 060.10 Partial Indicates whether the device supports partial Fixed NP1 Cond Authorization / Balance Indicator authorizations and whether the merchant desires balances to be returned on debit financial transactions. See Appendix A for values. 061.1 Other Contains the cash back amount, if any. If the BBVAR NP12 Cond Transaction Amount transaction does not include cash back, this field is not sent. 063 Private-use Used for identifying the acquirer s network ID, LLVAR Var. Req Field as well as various reason codes. See Appendix A. by use 063.0 Bit Map Indicates presence of subfields. Fixed B3 Req 063.1 Network ID Fixed NP4 Req A code that specifies the network to be used for authorization of the message. See Appendix A for values. Version 4.02 Page 31 Last modified August 12, 2009

Debit and EBT Request Message (Continued) Bit Data Element Number Name 063.3 Message Reason 111 Additional Data Acquirer 114 Transport Data 127 Private Use DUKPT 170 Private Use Card Acceptor Street Address 171 Private Use General Description Format Attr Presence Only sent in a submission or resubmission transaction. See Appendix A. Used to house the EBT FNS# and/or the EBT Voucher number or the EBT case number. See Appendix A for field use. A value assigned by the merchant. It is returned in the response message. See Appendix A. Contains hexadecimal digits of the Key Serial Number (KSN or IKSN) for a DUKPT PIN block. The length byte contains the length of the Key Serial Number. (Valid length is a minimum of 10 digits and a maximum of 20 digits.) Otherwise, not used. See Appendix A. Contains the street address of the card acceptor the location where the transaction occurred. See Appendix A. Fields unique to Bank of America Merchant Services processing. See descriptions of subfields below and in Appendix A. Fixed NP4 Cond LLVAR ANS 32 Req for EBT only LLVAR TLV (**) 255 Opt LLVAR NP20 Req for DUKPT only (N/A for EBT Voucher, Debit Resubmission) Fixed ANS 25 LLLVAR B8 + var. by use 171.0 Bit Map Indicates presence of subfields. Fixed B8 Req 171.6 Auth Only Fixed AN1 Cond Indicator 171.8 Transaction Subtype Applicable for Debit test transactions only. Used by Host Capture merchants to indicate to Bank of America Merchant Services to not capture and create settlement for this transaction. A value of N indicates to Bank of America Merchant Services to not capture the transaction. Merchants not using Bank of America Merchant Services s Host Capture product may either send this field with a value of N for all transactions or omit sending the field (as they are set up for non- Host-Capture in Bank of America Merchant Services s settlement system). See Appendix A. Used to indicate various transaction situations. See Appendix A. Req Fixed AN1 Cond Cond (Req for Card Not Present, Host Capture) Version 4.02 Page 32 Last modified August 12, 2009

3.2 Debit and EBT Response Message 3.2.1 Debit Purchase 3.2.2 Debit Purchase with Cash Back 3.2.3 Debit Return 3.2.4 Debit Balance Inquiry 3.2.5 EBT Food Stamp Purchase 3.2.6 EBT Cash Benefit Purchase 3.2.7 EBT Cash Benefit Purchase with Cash Back 3.2.8 EBT Cash Benefit Cash Withdrawal 3.2.9 EBT Food Stamp Return 3.2.10 EBT Food Stamp Balance Inquiry 3.2.11 EBT Cash Benefit Balance Inquiry 3.2.12 EBT Food Stamp Electronic Voucher This message is used to send a response message from Bank of America Merchant Services MultiLink to the POS for a Debit, EBT Food Stamp or EBT Cash Benefit transaction. The Debit and EBT Cash Benefit transactions may be with or without cash back. The Processing field (bit 3) differentiates the transaction type. The chart below describes: Bit Numbers and Names of all possible data elements for this message If constant, the value to be placed in the field A description of how each data element is used The format and attributes of each data element Required, Optional, Conditional or Not Applicable status of each data element Bit Number Data Element Name Message Type Primary Bit Map 001 Secondary Bit Map 065 Tertiary Bit Map 002 Primary Account Number 003 Processing Description Format Attr Presence Value to represent the type of message. Value: 0210. See Appendix A. Represents the presence of secondary bit map and data elements in bits 2 through 64. Represents the presence of tertiary bit map and data elements in bits 66 through 128. Represents the presence of data elements 130 through 192. Contains the cardholder account number. Copied from the request message. Defines the type of transaction. Copied from the request message. See Appendix A for values. 004 Amount 1 Transaction Amount. Copied from request message. Exception: For Debit transactions, if the merchant has indicated support for partial approvals and the transaction is approved for less than the requested amount, this field will contain the approved amount and bit 54 will contain the original amount. Must be sent in the settlement file. Fixed NP4 Req Fixed B8 Req Fixed B8 Cond Fixed B8 Cond LLVAR NP19 Req Fixed NP6 Req Fixed NP12 Req Version 4.02 Page 33 Last modified August 12, 2009

Debit and EBT Response Message (Continued) Bit Data Element Number Name 007 Transmission Date and Time Description Format Attr Presence Date and Time transaction is sent through the network. Expressed in GMT MMDDhhmmss. Fixed NP10 Req 011 System Trace Audit Number 019 Acquiring Institution Country 025 POS Condition 032 Acquiring Institution ID 037 Retrieval Reference Number 038 Auth ID Response 039 Response 041 Card Acceptor Term ID 042 Card Acceptor ID 044 Additional Response Data 044.1 Response Source / Reason 049 Transaction Currency A number assigned by the message initiator that identifies a cardholder transaction. Copied from request message. Identifies the country of the location where the transaction occurred. Copied from request message. Describes the condition under which the transaction takes place at the point of service. Copied from request message. See Appendix A. Identifies the financial institution acting as the acquirer of this transaction. Value is constant for all transaction requests and responses. Copied from request message. A number used with other data elements as a key to identify and track all messages related to a given customer transaction or series of system messages. The format for this field is YDDDHHNNNNNN, where YDDD is the date in Julian format, HH is the hour and N-N is a 6 digit transaction number. Copied from request message. The authorization code provided by the issuer when a transaction is approved. Will only be present for approved transactions. A code that defines the disposition of the transaction. See Appendix A for values. Unique terminal/device ID. Merchant-defined value. Merchant ID. Assigned by Bank of America Merchant Services. See Appendix A. Miscellaneous data needed in the response. Not used in card verification. See Appendix A. Identifies entity responding to request. Not used in card verification. See Appendix A. ISO defined code representing the currency of this transaction. Copied from request message. Fixed NP6 Req Fixed NP3 Req Fixed NP2 Req LLVAR NP11 Req Fixed AN12 Req Fixed AN6 Cond Fixed AN2 Req Fixed ANS8 Req Fixed ANS 15 Req LLVAR AN25 Cond (N/A card verification) Fixed AN1 Cond (N/A card verification) Fixed NP3 Req Version 4.02 Page 34 Last modified August 12, 2009

Debit and EBT Response Message (Continued) Bit Data Element Description Format Attr Presence Number Name 054 Add l Amount For EBT transactions, represents the LLVAR ANS Cond remaining balance on the EBT account. Value varies dependent on type of EBT account. For Debit financial transactions in which the merchant has indicated support for partial approvals, contains the original requested amount. If the merchant has indicated the desire to receive balances on Debit financial transactions, may contain one or more balances. For Debit balance inquiry transactions, the type of balance(s) will be indicated within the type of amount subfield(s) multiple instances are possible. See Appendix A for a full description. 120 063 Private-use Used for identifying the acquirer s network ID, LLVAR Var. Req Field as well as various reason codes. See Appendix A. by use 063.0 Bit Map Indicates presence of subfields. Fixed B3 Req 063.1 Network ID A code that specifies the network used for authorization of the message. See Appendix A for values. Fixed NP4 Req 102 Account ID 1 A number that identifies an account or LLVAR ANS Opt customer relationship. 28 114 Transport A value assigned by the merchant. Copied LLVAR TLV Cond Data from request message. See Appendix A. (**) 255 171 Private Use Fields unique to Bank of America Merchant LLLVAR B8 + Cond General Services processing. See descriptions of subfields below and in Appendix A. var. by use 171.0 Bit Map Indicates presence of subfields. Fixed B8 Req 171.8 Transaction Subtype Used to indicate various transaction situations. See Appendix A. Fixed AN1 Cond Version 4.02 Page 35 Last modified August 12, 2009

3.3 Debit Preauthorized Purchase Request Message 3.3.1 Debit Preauthorized Purchase 3.3.2 Debit Preauthorized Purchase with Cash Back This message is used to send a request message from the POS to Bank of America Merchant Services MultiLink for a Debit Preauthorized Purchase transaction, with or without cash back. The chart below describes: Bit Numbers and Names of all possible data elements for this message If constant, the value to be placed in the field A description of how each data element is used The format and attributes of each data element Required, Optional, Conditional or Not Applicable status of each data element Bit Data Element Description Format Attr Presence Number Name Message Type Value to represent the type of message. Fixed NP4 Req Value: 0100. See Appendix A. Primary Bit Represents the presence of secondary bit Fixed B8 Req Map map and data elements in bits 2 through 64. 001 Secondary Bit Represents the presence of tertiary bit map Fixed B8 Cond Map and data elements in bits 66 through 128. 065 Tertiary Bit Represents the presence of data elements in Fixed B8 Cond Map bits 130 through 192. 002 Primary Contains the cardholder account number. LLVAR NP19 Req Account Number 003 Processing Defines the type of transaction. See Fixed NP6 Req Appendix A. 004 Amount 1 Transaction amount to be authorized. Fixed NP12 Req 007 Transmission Date and Time transaction is sent through Fixed NP10 Req Date and Time the network assigned by the originator. Expressed in GMT MMDDhhmmss. 011 System Trace A number assigned by the message initiator Fixed NP6 Req Audit Number that identifies a cardholder transaction. 012 Local Time Time of the transaction, in merchant s local Fixed NP6 Req time. This value stays constant throughout the life of the transaction. This field must be sent in the settlement file. Expressed as hhmmss. 013 Local Date Date of the transaction, in merchant s local date. This value stays constant throughout the life of the transaction. This field must be sent in the settlement file. Expressed as Fixed NP4 Req 014 Expiration Date 018 Merchant Type MMDD. Contains the expiration date on the card. If the card does not have an expiration date, do not send this bit. Expressed as YYMM. Merchant Category (MCC). Bank of America Merchant Services-assigned value. Fixed NP4 Cond Fixed NP4 Req Version 4.02 Page 36 Last modified August 12, 2009

Debit Preauthorized Purchase Request Message (Continued) Bit Data Element Number Name 019 Acquiring Institution Country 022 POS Entry Mode 025 POS Condition 032 Acquiring Institution ID Description Format Attr Presence Identifies the country of the location where the transaction occurred. See Appendix A for values. Defines the method of data entry of the account number and whether a PIN was entered on this transaction. See Appendix A for values. Describes the condition under which the transaction takes place at the point of service. See Appendix A. Identifies the financial institution acting as the acquirer of this transaction. Value is constant for all transaction requests and responses. Value 45592900000. 035 Track 2 Data Unaltered contents of the data read off Track 2 of the magnetic stripe, excluding the beginning and ending sentinels and LRC characters. 037 Retrieval Reference Number 041 Card Acceptor Term ID 042 Card Acceptor ID 043 Card Acceptor Name / Location 049 Transaction Currency A number used with other data elements as a key to identify and track all messages related to a given customer transaction or series of system messages. The format for this field is YDDDHHNNNNNN, where YDDD is the date in Julian format, HH is the hour and N-N is a 6 digit transaction number. Unique terminal/device ID. Merchant-defined value. Merchant ID. Assigned by Bank of America Merchant Services. See Appendix A. Name and location of the card acceptor where the transaction occurred. See Appendix A. Positions: 1-25 Card Acceptor name 26-38 City Name 39-40 Alpha Country code ISO defined code representing the currency of this transaction. 052 PIN data Contains a PIN or password, encrypted and formatted as a block of 16 hexadecimal digits or contains the 16 hexadecimal digits of a DUKPT PIN block (depending on the value of field 53). If a DUKPT PIN block is used, the Key Serial Number is passed in field 127. See Appendix A. Fixed NP3 Req Fixed NP4 Req Fixed NP2 Req LLVAR NP11 Req LLVAR NP37 Req Fixed AN12 Req Fixed ANS8 Req Fixed Fixed ANS 15 ANS 40 Req Req Fixed NP3 Req Fixed B8 Req Version 4.02 Page 37 Last modified August 12, 2009

Debit Preauthorized Purchase Request Message (Continued) Bit Data Element Number Name 053 Securityrelated Control Information 055 EM and Chip Data 059 National POS Geographic Data 060 Additional POS Info 060.1 Terminal Type 060.2 Terminal Entry Capability 060.3 Chip Condition 060.4 Special Condition Indicator Existing Debt 060.5 Merchant Group Indicator 060.6 Chip Transaction Indicator 060.7 Chip Authentication Reliability Indicator 060.8 Mail Order / Telephone Order / Electronic Commerce Indicator 060.9 Cardholder ID Method 060.10 Partial Authorization / Balance Indicator Description Format Attr Presence Data used by the issuer to process PINs. See Appendix A for field details Electronic Magnetic Signature and chip data. See Appendix A. A field to describe the location of the card acceptor within the country. See Appendix A for values. A group of sub fields that provide additional information about the point of service. See Appendix A for values Identifies the point-of-service terminal. See Appendix A for values Identifies the terminal s capability to electronically read account numbers and expiration dates from cards. See Appendix A for values. Provides information about VSDC cards when read at VSDC terminals. See Appendix A for values. Indicates whether a payment is being made on an existing debt. See Appendix A for values. Identifies the general category of the card acceptor and transaction. See Appendix A for values. Set when message from the terminal is for a VSDC transaction. See Appendix A for values. Indicates the reliability of a transaction in the VSDC environment. See Appendix A for values. Identifies the type of mail or telephone order or the level of security used in en e- commerce transaction over an open network. See Appendix A for values. Identifies the method of transaction authentication. See Appendix A for values. Indicates whether the device supports partial authorizations and whether the merchant desires balances to be returned on debit financial transactions. See Appendix A for values. Fixed NP16 Req BBVAR LLVAR BBVAR TLV (**) 255 ANS 14 Var. by use Cond Cond Req Fixed NP1 Req Fixed NP1 Req Fixed NP1 Cond Fixed NP1 Cond Fixed NP2 Cond Fixed NP1 Cond Fixed NP1 Cond Fixed NP2 Cond Fixed NP1 Cond Fixed NP1 Cond Version 4.02 Page 38 Last modified August 12, 2009

Debit Preauthorized Purchase Request Message (Continued) Bit Data Element Number Name 061.1 Other Transaction Amount 063 Private-use Field Description Format Attr Presence Contains the cash back amount, if any. If the transaction does not include cash back, this field is not sent. Used for identifying the acquirer s network ID, as well as various reason codes. See Appendix A. BBVAR NP12 Cond LLVAR Var. by use 063.0 Bit Map Indicates presence of sub fields. Fixed B3 Req 063.1 Network ID A code that specifies the network used for Fixed NP4 Req authorization of the message. Must be 063.2 Preauth Time Limit 114 Transport Data 127 Private Use DUKPT 170 Private Use Card Acceptor Street Address 0000 in a request. See Appendix A. The time (in hours) the issuer agrees to hold funds for an acquirer. For merchant use. This field will be echoed back in the response to this transaction. See Appendix A. Contains hexadecimal digits of the Key Serial Number (LKSN) for a DUKPT PIN block. The length byte contains the length of the Key Serial Number. (Valid length is a minimum of 10 digits and a maximum of 20 digits. See Appendix A. Contains the street address of the card acceptor the location where the transaction occurred. See Appendix A. Req Fixed NP4 Req LLVAR TLV (**) 255 Opt LLVAR NP20 Req for DUKPT only Fixed ANS 25 Req Version 4.02 Page 39 Last modified August 12, 2009

3.4 Debit Preauthorized Purchase Response Message 3.4.1 Debit Preauthorized Purchase 3.4.2 Debit Preauthorized Purchase with Cash Back This message is used to send a response message from Bank of America Merchant Services MultiLink to the POS for a Debit Preauthorized Purchase transaction, with or without cash back. The chart below describes: Bit Numbers and Names of all possible data elements for this message If constant, the value to be placed in the field A description of how each data element is used The format and attributes of each data element Required, Optional, Conditional or Not Applicable status of each data element Bit Number Data Element Name Message Type Description Format Attr Presence Value to represent the type of message. Value: 0110. See Appendix A. Represents the presence of secondary bit map and data elements in bits 2 through 64. Represents the presence of tertiary bit map and data elements in bits 66 through 128. Represents the presence of data elements in bits 130 through 192. Contains the cardholder account number. Copied from request message. Primary Bit Map 001 Secondary Bit Map 065 Tertiary Bit Map 002 Primary Account Number 003 Processing Defines the type of transaction. Copied from request message. See Appendix A. 004 Amount 1 The authorized amount. This value may be less than the original preauth request amount. Merchants supporting preauthorization are required to support this lesser amount approval. In addition, a merchant may indicate in bit 60.10 full support for lesser amount approvals. In this case, they will receive the original requested amount in bit 54. See bits 54 and 60.10 in Appendix A for details. 007 Transmission Date and Time 011 System Trace Audit Number 019 Acquiring Institution Country 025 POS Condition Fixed NP4 Req Fixed B8 Req Fixed B8 Cond Fixed B8 Cond LLVAR NP19 Req Fixed NP6 Req Fixed NP12 Req Copied from the request Fixed NP10 Req A number assigned by the message initiator that identifies a cardholder transaction. Copied from request message. Identifies the country of the location where the transaction occurred. Copied from request message. Describes the condition under which the transaction takes place at the point of service. Copied from request message. See Appendix A. Fixed NP6 Req Fixed NP3 Req Fixed NP2 Req Version 4.02 Page 40 Last modified August 12, 2009

Debit Preauthorized Purchase Response Message (Continued) Bit Data Element Number Name 032 Acquiring Institution ID 037 Retrieval Reference Number 038 Auth ID Response 039 Response 041 Card Acceptor Term ID 042 Card Acceptor ID 044 Additional Response Data 044.1 Response Source / Reason 049 Transaction Currency Description Format Attr Presence Identifies the financial institution acting as the acquirer of this transaction. Value is constant for all transaction requests and responses. Copied from request message. A number used with other data elements as a key to identify and track all messages related to a given customer transaction or series of system messages. The format for this field is YDDDHHNNNNNN, where YDDD is the date in Julian format, HH is the hour and N-N is a 6 digit transaction number. From the original request. The authorization code provided by the issuer when a transaction is approved. Will only be present for approved transactions. A code that defines the disposition of the transaction. See Appendix A for values Unique terminal/device ID. Merchant-defined value. Copied from the request. Merchant ID. Assigned by Bank of America Merchant Services. Copied from the request. See Appendix A. Miscellaneous data needed in the response. Not used in card verification. See Appendix A. Identifies entity responding to request. Not used in card verification. See Appendix A. ISO defined code representing the currency of this transaction. Copied from request message. 054 Add l Amount For transactions in which the merchant has indicated support for partial approvals, contains the original requested amount. If the merchant has indicated the desire to receive balances on financial transactions, may contain one or more balances. See Appendix A for a full description. 063 Private-use Field Used for identifying the acquirer s network ID, as well as various reason codes. See Appendix A. LLVAR NP11 Req Fixed AN12 Req Fixed AN6 Req Fixed AN2 Req Fixed ANS8 Req Fixed ANS 15 Req LLVAR AN25 Cond (N/A card verification) Fixed AN1 Cond (N/A card verification) Fixed NP3 Req LLVAR LLVAR ANS 120 Var. by use 063.0 Bit Map Indicates presence of sub fields. Fixed B3 Req 063.1 Network ID Fixed NP4 Req 114 Transport Data A code that specifies the network used for authorization of the message. This code must be used in the merchant settlement file. See Appendix A. For merchant use. Copied from the request. See Appendix A. LLVAR TLV (**) 255 Cond Req Cond Version 4.02 Page 41 Last modified August 12, 2009

3.5 Debit Preauthorized Purchase Completion Request Message 3.5.1 Debit Preauthorized Purchase 3.5.2 Debit Preauthorized Purchase with Cash Back This message is used to send a completion request message from the POS to Bank of America Merchant Services MultiLink for a Debit Preauthorized Purchase transaction, with or without cash back. The chart below describes: Bit Numbers and Names of all possible data elements for this message If constant, the value to be placed in the field A description of how each data element is used The format and attributes of each data element Required, Optional, Conditional or Not Applicable status of each data element Bit Data Element Description Format Attr Presence Number Name Message Type Value to represent the type of message. Fixed NP4 Req Value: 0220. See Appendix A. Primary Bit Represents the presence of secondary bit Fixed B8 Req Map map and data elements in bits 2 through 64. 001 Secondary Bit Represents the presence of tertiary bit map Fixed B8 Cond Map and data elements in bits 66 through 128. 065 Tertiary Bit Represents the presence of data elements in Fixed B8 Cond Map bits 130 through 192. 002 Primary Contains the cardholder account number. LLVAR NP19 Req Account Number 003 Processing Defines the type of transaction. See Fixed NP6 Req Appendix A. 004 Amount 1 Completed amount. Fixed NP12 Req 007 Transmission Date and Time Date and Time transaction is sent through the network assigned by the originator. Will not have the same value as bit 007 in preauth request. Expressed in GMT Fixed NP10 Req 011 System Trace Audit Number MMDDhhmmss. A number assigned by the message initiator that identifies a cardholder transaction. Copied from preauth request. 012 Local Time Time of the transaction, in merchant s local time. This value stays constant throughout the life of the transaction. This field must be sent in the settlement file. Expressed as hhmmss. 013 Local Date Date of the transaction, in merchant s local date. This value stays constant throughout the life of the transaction. This field must be sent in the settlement file. Expressed as MMDD. 014 Expiration Date Contains the expiration date on the card. If the card does not have an expiration date, do not send this bit. Expressed as YYMM. Fixed NP6 Req Fixed NP6 Req Fixed NP4 Req Fixed NP4 Cond Version 4.02 Page 42 Last modified August 12, 2009

Debit Preauthorized Purchase Completion Request Message (Continued) Bit Number Data Element Name 018 Merchant Merchant Category (MCC). Bank of Type America Merchant Services-assigned value. 019 Acquiring Identifies the country of the location where Institution the transaction occurred. See Appendix A Country for values. 022 POS Entry Defines the method of data entry of the Mode account number and whether a PIN was entered on this transaction. See Appendix A for values. 025 POS Condition Must contain a value of 06 to indicate a preauthorization completion. See Appendix A. 032 Acquiring Identifies the financial institution acting as the Institution ID acquirer of this transaction. Value is constant for all transaction requests and responses. Value 45592900000. 035 Track 2 Data Unaltered contents of the data read off Track 2 of the magnetic stripe, excluding the beginning and ending sentinels and LRC characters. 037 Retrieval Reference Number 041 Card Acceptor Term ID 042 Card Acceptor ID 043 Card Acceptor Name / Location 049 Transaction Currency Description Format Attr Presence A number used with other data elements as a key to identify and track all messages related to a given customer transaction or series of system messages. The format for this field is YDDDHHNNNNNN, where YDDD is the date in Julian format, HH is the hour and N-N is a 6 digit transaction number. Copied from preauth request. Unique terminal/device ID. Merchant-defined value. Merchant ID. Assigned by Bank of America Merchant Services. See Appendix A. Name and location of the card acceptor where the transaction occurred. See Appendix A. Positions: 1-25 Card Acceptor name 26-38 City Name 39-40 Alpha Country code ISO defined code representing the currency of this transaction. 052 PIN data Contains a PIN or password, encrypted and formatted as a block of 16 hexadecimal digits or contains the 16 hexadecimal digits of a DUKPT PIN block (depending on the value of field 53). If a DUKPT PIN block is used, the Key Serial Number is passed in field 127. See Appendix A. Fixed NP4 Req Fixed NP3 Req Fixed NP4 Req Fixed NP2 Req LLVAR NP11 Req LLVAR NP37 Opt (see Appendix A for details if not sent) Fixed AN12 Req Fixed ANS8 Req Fixed Fixed ANS 15 ANS 40 Req Req Fixed NP3 Req Fixed B8 Opt Version 4.02 Page 43 Last modified August 12, 2009

Debit Preauthorized Purchase Completion Request Message (Continued) Bit Data Element Number Name 053 Securityrelated Control Information 059 National POS Geographic Data 060 Additional POS Info 060.1 Terminal Type 060.2 Terminal Entry Capability 061.1 Other Transaction Amount 063 Private-use Field Description Format Attr Presence Data used by the issuer to process PINs. See Appendix A for field details A field to describe the location of the card acceptor within the country. See Appendix A for values. A group of sub fields that provide additional information about the point of service. See Appendix A for values Identifies the point-of-service terminal. See Appendix A for values Identifies the terminal s capability to electronically read account numbers and expiration dates from cards. See Appendix A for values. Contains the cash back amount, if any. If the transaction does not include cash back, this field is not sent. Used for identifying the acquirer s network ID, as well as various reason codes. See Appendix A. Fixed NP16 Opt LLVAR BBVAR ANS 14 Var. by use Cond Req Fixed NP1 Req Fixed NP1 Req BBVAR NP12 Cond LLVAR Var. by use 063.0 Bit Map Indicates presence of sub fields. Fixed B3 Req 063.1 Network ID A code that specifies the network used for Fixed NP4 Req authorization of the message. Must be 063.2 Preauth Time Limit 090 Original Data Elements 114 Transport Data 127 Private Use DUKPT 170 Private Use Card Acceptor Street Address 0000 in a request. See Appendix A. The time (in hours) the issuer agrees to hold funds for an acquirer. Information for tracking the current message back to the original preauthorization. See Appendix A for description. For merchant use. This field will be echoed back in the response to this transaction. See Appendix A. Contains hexadecimal digits of the Key Serial Number (LKSN) for a DUKPT PIN block. The length byte contains the length of the Key Serial Number. (Valid length is a minimum of 10 digits and a maximum of 20 digits. See Appendix A. Contains the street address of the card acceptor the location where the transaction occurred. See Appendix A. Req Fixed NP4 Req Fixed NP42 Req LLVAR TLV (**) 255 Opt LLVAR NP20 Opt for DUKPT only Fixed ANS 25 Req Version 4.02 Page 44 Last modified August 12, 2009

3.6 Debit Preauthorized Purchase Completion Response Message 3.6.1 Debit Preauthorized Purchase 3.6.2 Debit Preauthorized Purchase with Cash Back This message is used to send a completion response message from Bank of America Merchant Services MultiLink to the POS for a Debit Preauthorized Purchase transaction, with or without cash back. The chart below describes: Bit Numbers and Names of all possible data elements for this message If constant, the value to be placed in the field A description of how each data element is used The format and attributes of each data element Required, Optional, Conditional or Not Applicable status of each data element Bit Number Data Element Name Message Type Primary Bit Map 001 Secondary Bit Map 065 Tertiary Bit Map 002 Primary Account Number 003 Processing 007 Transmission Date and Time 011 System Trace Audit Number 019 Acquiring Institution Country 025 POS Condition 032 Acquiring Institution ID Description Format Attr Presence Value to represent the type of message. Value: 0230. See Appendix A. Represents the presence of secondary bit map and data elements in bits 2 through 64. Represents the presence of tertiary bit map and data elements in bits 66 through 128. Represents the presence of data elements in bits 130 through 192. Contains the cardholder account number. Copied from request message. Defines the type of transaction. Copied from request message. See Appendix A. Original transmission date and time. Copied from the completion request A number assigned by the message initiator that identifies a cardholder transaction. Copied from request message. Identifies the country of the location where the transaction occurred. Copied from request message. Describes the condition under which the transaction takes place at the point of service. Copied from request message. See Appendix A. Identifies the financial institution acting as the acquirer of this transaction. Value is constant for all transaction requests and responses. Copied from request message. Fixed NP4 Req Fixed B8 Req Fixed B8 Req Fixed B8 Cond LLVAR NP19 Req Fixed NP6 Req Fixed NP10 Req Fixed NP6 Req Fixed NP3 Req Fixed NP2 Req LLVAR NP11 Req Version 4.02 Page 45 Last modified August 12, 2009

Debit Preauthorized Purchase Completion Response Message (Continued) Bit Data Element Number Name 037 Retrieval Reference Number 039 Response 041 Card Acceptor Term ID 042 Card Acceptor ID 044 Additional Response Data 044.1 Response Source / Reason 063 Private-use Field Description Format Attr Presence A number used with other data elements as a key to identify and track all messages related to a given customer transaction or series of system messages. The format for this field is YDDDHHNNNNNN, where YDDD is the date in Julian format, HH is the hour and N-N is a 6 digit transaction number. From the original request. A code that defines the disposition of the transaction. See Appendix A for values. Unique terminal/device ID. Merchant-defined value. Copied from the request. Merchant ID. Assigned by Bank of America Merchant Services. Copied from the request. See Appendix A. Miscellaneous data needed in the response. Not used in card verification. See Appendix A. Identifies entity responding to request. Not used in card verification. See Appendix A. Used for identifying the acquirer s network ID, as well as various reason codes. See Appendix A. Fixed AN12 Req Fixed AN2 Req Fixed ANS8 Req Fixed ANS 15 Req LLVAR AN25 Cond (N/A card verification) Fixed AN1 Cond (N/A card LLVAR Var. by use 063.0 Bit Map Indicates presence of sub fields. Fixed B3 Req 063.1 Network ID Fixed NP4 Req 063.2 Preauth Time Limit 090 Original Data Elements 114 Transport Data A code that specifies the network used for authorization of the message. This code must be supplied in the merchant settlement file. See Appendix A. The time (in hours) the issuer agrees to hold funds for an acquirer. Copied from completion request message. Copied from the completion request. See Appendix A. For merchant use only. Copied from the request. See Appendix A. Fixed NP4 Req Fixed NP42 Req LLVAR TLV (**) 255 verification) Req Cond Version 4.02 Page 46 Last modified August 12, 2009

3.7 Debit Bill Payment Request Message 3.7.1 Debit Bill Payment This message is used to send a request message from the POS to Bank of America Merchant Services MultiLink for a Debit Bill Payment transaction. The Processing field (bit 3) identifies the transaction type. The chart below describes: Bit Numbers and Names of all possible data elements for this message If constant, the value to be placed in the field A description of how each data element is used The format and attributes of each data element Required, Optional, Conditional or Not Applicable status of each data element Bit Number Data Element Name Message Type Description Format Attr Presence Value to represent the type of message Value: 0200. See Appendix A. Fixed NP4 Req Represents the presence of secondary bit Fixed B8 Req map and data elements in bits 2 through 64. Represents the presence of tertiary bit map Fixed B8 Cond and data elements in bits 66 through 128. Represents the presence of data elements in Fixed B8 Cond bits 130 through 192. Contains the cardholder account number. LLVAR NP19 Req Primary Bit Map 001 Secondary Bit Map 065 Tertiary Bit Map 002 Primary Account Number 003 Processing Defines the type of transaction. See Appendix A. 004 Amount 1 Transaction Amount. Assumes a 2 position decimal, right-justified, zero filled. This field contains the total amount including the purchase amount and cash back if indicated. Transactions settled through Bank of America Merchant Services s settlement system are limited to 7 characters ($99,999.99). 007 Transmission Date and Time Date and Time transaction is sent through the network assigned by the originator. Expressed in GMT MMDDhhmmss. 011 System Trace Audit Number A number assigned by the message initiator that identifies a cardholder transaction. 012 Local Time Time of the transaction, in merchant s local time. This value stays constant throughout the life of the transaction. This field must be sent in the settlement file. Expressed as hhmmss. For submissions and resubmissions, this is the time of the original transaction. Fixed NP6 Req Fixed NP12 Req Fixed NP10 Req Fixed NP6 Req Fixed NP6 Req Version 4.02 Page 47 Last modified August 12, 2009

Debit Bill Payment Request Message (Continued) Bit Data Element Description Format Attr Presence Number Name 013 Local Date Date of the transaction, in merchant s local Fixed NP4 Req date. This value stays constant throughout the life of the transaction. This field must be sent in the settlement file. Expressed as MMDD. For submissions and resubmissions, this is the date of the original transaction. 014 Expiration Date Contains the expiration date on the card. If the expiration date is not available, do not Fixed NP4 Cond 018 Merchant Type 019 Acquiring Institution Country 022 POS Entry Mode 025 POS Condition 028 Transaction Fee Amount 032 Acquiring Institution ID 033 Forwarding Institution ID 037 Retrieval Reference Number 041 Card Acceptor Term ID 042 Card Acceptor ID send this bit. Expressed as YYMM. Merchant Category (MCC). Specific values are needed for the Bill Payment transaction. Bank of America Merchant Services-assigned value. Identifies the country of the location where the transaction occurred. See Appendix A for values. Defines the method of data entry of the account number and whether a PIN was entered on this transaction. See Appendix A for values. Describes the condition under which the transaction takes place at the point of service. See Appendix A for values. Contains an acquirer-assessed transaction fee. The fee amount is not included in field 4. The first character is C for credit, or D for debit, as appropriate. Identifies the financial institution acting as the acquirer of this transaction. Value is constant for all transaction requests and responses. This is an Bank of America Merchant Services assigned identification number. Value 45592900000. Identifies the processor that forwards the request to Bank of America Merchant Services, if that processor is different from the institution indicated in field 032. This is an Bank of America Merchant Servicesassigned identification number. A number used with other data elements as a key to identify and track all messages related to a given customer transaction or series of system messages. The format for this field is YDDDHHNNNNNN, where YDDD is the date in Julian format, HH is the hour and N-N is a 6 digit transaction number. Unique terminal/device ID. Merchant-defined value. Merchant ID. Assigned by Bank of America Merchant Services. See Appendix A. Fixed NP4 Req Fixed NP3 Req Fixed NP4 Req Fixed NP2 Req Fixed ANS9 Cond LLVAR NP11 Req LLVAR NP11 Cond Fixed AN12 Req Fixed ANS8 Req Fixed ANS 15 Req Version 4.02 Page 48 Last modified August 12, 2009

Debit Bill Payment Request Message (Continued) Bit Data Element Number Name 043 Card Acceptor Name / Location 049 Transaction Currency 059 National POS Geographic Data 060 Additional POS Info 060.1 Terminal Type 060.2 Terminal Entry Capability Description Format Attr Presence Name and location of the card acceptor where the transaction occurred. See Appendix A. Positions: 1-25 Card acceptor name 26-38 City name 39-40 Alpha country code ISO defined code representing the currency of this transaction. A field to describe the location of the card acceptor within the country. See Appendix A for values. A group of subfields that provide additional information about the point of service. See Appendix A for values. Identifies the point-of-service terminal. See Appendix A for values. Identifies the terminal s capability to electronically read account numbers and expiration dates from cards. See Appendix A for values. Contains authorizations characteristics to the back-end authorizer. See Appendix A. Fixed ANS 40 Req Fixed NP3 Req LLVAR BBVAR ANS 14 Var. by use Cond Req Fixed NP1 Req Fixed NP1 Req 062 Payment LLVAR B8 + Req Service Fields AN59 062.0 Bit Map Indicates presence of subfields. Fixed B8 Req 062.1 Authorization Characteristic Indicator 062.4 Market- Specific Data Identifier 063 Private-use Field Used by the acquirer processor to indicate a recurring bill payment. See Appendix A. Identifies the industry for which marketspecific data has been provided. See Appendix A. Used for identifying the acquirer s network ID, as well as various reason codes. See Appendix A. Fixed AN1 Cond Fixed AN1 Req LLVAR Var. by use 063.0 Bit Map Indicates presence of subfields. Fixed B3 Req 063.1 Network ID A code that specifies the network to be used Fixed NP4 Req for authorization of the message. See 063.6 Chargeback Reduction Flags 104 Transaction Description Appendix A for values. Contains seven indicators, also used in the BASE II System to assist in the Visa effort to reduce the number of chargebacks. See Appendix A. Contains additional billing or reporting information about transaction or message processing. See Appendix A. Req Fixed ANS7 Req LLVAR ANS 100 Req Version 4.02 Page 49 Last modified August 12, 2009

Debit Bill Payment Request Message (Continued) Bit Data Element Number Name 164 Large Private Data 1 165 Large Private Data 2 166 Large Private Data 3 167 Large Private Data 4 168 Acquirer Trace Data Description Format Attr Presence Information to be moved between the acquirer and the issuer. Contains multiple tag-identified subfields. See Appendix A for subfield definitions and uses. (Reserved for future use) Information to be moved between the acquirer and the issuer. Contains multiple tag-identified subfields. (Reserved for future use) Information to be moved between the acquirer and the issuer. Contains multiple tag-identified subfields. (Reserved for future use) Information to be moved between the acquirer and the issuer. Contains multiple tag-identified subfields. Contains the payee name. Format is 1- character identifier (=0), followed by the name. 169 Payee Phone Contains the payee s phone/pager number. For regulatory purposes, periodic statements are expected to disclose the phone number if the consumer has questions about the payment. 170 Private Use Card Acceptor Street Address Contains the street address of the card acceptor the location where the transaction occurred. See Appendix A. LLVAR LLVAR LLVAR LLVAR LLVAR LLVAR Fixed TLV (**) 255 TLV (**) 255 TLV (**) 255 TLV (**) 255 ANS 61 ANS 25 ANS 25 Req N/A (reserved for future use) N/A (reserved for future use) N/A (reserved for future use) Req Req Req Version 4.02 Page 50 Last modified August 12, 2009

3.8 Debit Bill Payment Response Message 3.8.1 Debit Bill Payment This message is used to send a response message from Bank of America Merchant Services MultiLink to the POS for a Debit Bill Payment transaction. The Processing field (bit 3) identifies the transaction type. The chart below describes: Bit Numbers and Names of all possible data elements for this message If constant, the value to be placed in the field A description of how each data element is used The format and attributes of each data element Required, Optional, Conditional or Not Applicable status of each data element Bit Number Data Element Name Message Type Primary Bit Map 001 Secondary Bit Map 065 Tertiary Bit Map 002 Primary Account Number 003 Processing Description Format Attr Presence Value to represent the type of message. Value: 0210. See Appendix A. Represents the presence of secondary bit map and data elements in bits 2 through 64. Represents the presence of tertiary bit map and data elements in bits 66 through 128. Represents the presence of data elements 130 through 192. Contains the cardholder account number. Copied from the request message. Defines the type of transaction. Copied from the request message. See Appendix A for values. 004 Amount 1 Transaction Amount. Copied from request message. Must be sent in the settlement file. 007 Transmission Date and Time transaction is sent through Date and Time the network. Expressed in GMT 011 System Trace Audit Number 019 Acquiring Institution Country 025 POS Condition 028 Transaction Fee Amount MMDDhhmmss. A number assigned by the message initiator that identifies a cardholder transaction. Copied from request message. Identifies the country of the location where the transaction occurred. Copied from request message. Describes the condition under which the transaction takes place at the point of service. Copied from request message. See Appendix A. Contains an acquirer-assessed transaction fee. The fee amount is not included in field 4. The first character is C for credit, or D for debit, as appropriate. If present, must be sent in settlement file. Fixed NP4 Req Fixed B8 Req Fixed B8 Cond Fixed B8 Cond LLVAR NP19 Req Fixed NP6 Req Fixed NP12 Req Fixed NP10 Req Fixed NP6 Req Fixed NP3 Req Fixed NP2 Req Fixed ANS9 Cond Version 4.02 Page 51 Last modified August 12, 2009

Debit Bill Payment Response Message (Continued) Bit Data Element Number Name 032 Acquiring Institution ID Description Format Attr Presence Identifies the financial institution acting as the acquirer of this transaction. Value is constant for all transaction requests and responses. Copied from request message. LLVAR NP11 Req 037 Retrieval Reference Number 038 Auth ID Response A number used with other data elements as a key to identify and track all messages related to a given customer transaction or series of system messages. The format for this field is YDDDHHNNNNNN, where YDDD is the date in Julian format, HH is the hour and N-N is a 6 digit transaction number. Copied from request message. The authorization code provided by the issuer when a transaction is approved. Will only be present for approved transactions. A code that defines the disposition of the transaction. See Appendix A for values. Unique terminal/device ID. Merchant-defined value. Merchant ID. Assigned by Bank of America Fixed AN12 Req Fixed AN6 Cond 039 Response Fixed AN2 Req 041 Card Acceptor Fixed ANS8 Req Term ID 042 Card Acceptor Fixed ANS Req ID Merchant Services. See Appendix A. 15 044 Additional Miscellaneous data needed in the response. LLVAR AN25 Cond Response See Appendix A. Data 044.1 Response Identifies entity responding to request. See Fixed AN1 Cond Source / Appendix A. Reason 049 Transaction ISO defined code representing the currency Fixed NP3 Req Currency of this transaction. Copied from request message. 062 Payment Contains authorizations characteristics to the LLVAR B8 + Req Service Fields back-end authorizer. See Appendix A. AN59 062.0 Bit Map Indicates presence of subfields. Fixed B8 Req 062.1 Authorization Characteristic Indicator 063 Private-use Field Present only if acquirer processor sent the field, indicating a recurring bill payment. See Appendix A for values. Used for identifying the acquirer s network ID, as well as various reason codes. See Appendix A. Fixed AN1 Cond LLVAR Var. by use 063.0 Bit Map Indicates presence of subfields. Fixed B3 Req Req 063.1 Network ID A code that specifies the network used for authorization of the message. See Appendix A for values. Fixed NP4 Req Version 4.02 Page 52 Last modified August 12, 2009

Debit Bill Payment Response Message (Continued) Bit Data Element Number Name 063.6 Chargeback Reduction Flags 104 Transaction Description 164 Large Private Data 1 165 Large Private Data 2 166 Large Private Data 3 167 Large Private Data 4 Description Format Attr Presence Contains seven indicators, also used in the BASE II System to assist in the Visa effort to reduce the number of chargebacks. See Appendix A. Contains additional billing or reporting information about transaction or message processing. Copied from request. See Appendix A. Information to be moved between the acquirer and the issuer. Contains multiple tag-identified subfields. See Appendix A for subfield definitions and uses. (Reserved for future use) Information to be moved between the acquirer and the issuer. Contains multiple tag-identified subfields. (Reserved for future use) Information to be moved between the acquirer and the issuer. Contains multiple tag-identified subfields. (Reserved for future use) Information to be moved between the acquirer and the issuer. Contains multiple tag-identified subfields. Contains the payee name. Copied from 168 Acquirer Trace Data request. 169 Payee Phone Contains the payee s phone/pager number. Copied from request. Fixed ANS7 Req LLVAR LLVAR LLVAR LLVAR LLVAR LLVAR LLVAR ANS 100 TLV (**) 255 TLV (**) 255 TLV (**) 255 TLV (**) 255 ANS 61 ANS 25 Req Req N/A (reserved for future use) N/A (reserved for future use) N/A (reserved for future use) Cond Req Version 4.02 Page 53 Last modified August 12, 2009

3.9 Debit and EBT Reversal Request Message 3.9.1 Debit Purchase 3.9.2 Debit Purchase with Cash Back 3.9.3 Debit Preauthorized Purchase 3.9.4 Debit Completion 3.9.5 Debit Bill Payment 3.9.6 Debit Preauthorized Purchase with Cash Back 3.9.7 Debit Completion with Cash Back 3.9.8 Debit Return 3.9.9 EBT Food Stamp Purchase 3.9.10 EBT Food Stamp Return 3.9.11 EBT Cash Benefit Purchase 3.9.12 EBT Cash Benefit Purchase with Cash Back 3.9.13 EBT Cash Benefit Cash Withdrawal This message is used to send a Reversal request message from the POS or Merchant Host to Bank of America Merchant Services MultiLink for a Debit, EBT Food Stamp or Cash Benefit Purchase transaction. Most of the data from the original request will be required in this reversal request message. The chart below describes: Bit Numbers and Names of all possible data elements for this message If constant, the value to be placed in the field A description of how each data element is used The format and attributes of each data element Required, Optional, Conditional or Not Applicable status of each data element Bit Number Data Element Name Message Type Primary Bit Map 001 Secondary Bit Map 065 Tertiary Bit Map 002 Primary Account Number 003 Processing Description Format Attr Presence Value to represent the type of message Value: 0400. See Appendix A. Fixed NP4 Req Represents the presence of secondary bit Fixed B8 Req map and data elements in bits 2 through 64. Represents the presence of tertiary bit map Fixed B8 Cond and data elements in bits 66 through 128. Represents the presence of data elements in Fixed B8 Cond bits 130 through 192. Contains the cardholder account number. LLVAR NP19 Req Defines the type of transaction. Copied from original request. See Appendix A. 004 Amount 1 Transaction Amount. This field contains the total amount including the purchase amount and cash back if indicated. From original request. Exception: If the transaction was authorized for a lesser amount than the original requested amount, this field contains the authorized amount. Fixed NP6 Req Fixed NP12 Req Version 4.02 Page 54 Last modified August 12, 2009

Debit and EBT Reversal Request Message (Continued) Bit Data Element Number Name 007 Transmission Date and Time 011 System Trace Audit Number Description Format Attr Presence Date and Time transaction is sent through the network assigned by the originator. Expressed in GMT MMDDhhmmss. A number assigned by the message initiator that identifies a cardholder transaction. From original request. 012 Local Time Time of the transaction, in merchant s local time. This value stays constant throughout the life of the transaction. This field must be sent in the settlement file. Expressed as hhmmss. From the original request. 013 Local Date Date of the transaction, in merchant s local date. This value stays constant throughout the life of the transaction. This field must be sent in the settlement file. Expressed as MMDD. From original request. 014 Expiration Date 018 Merchant Type 019 Acquiring Institution Country 022 POS Entry Mode 025 POS Condition 028 Transaction Fee Amount 032 Acquiring Institution ID Contains the expiration date on the card. If the card does not have an expiration date, do not send this bit. Expressed as YYMM. Required if present in original request. Merchant Category (MCC). Bank of America Merchant Services-assigned value. From original request. Identifies the country of the location where the transaction occurred. From original request. Defines the method of data entry of the account number and whether a PIN was entered on this transaction. See Appendix A for values. From original request. Describes the condition under which the transaction takes place at the point of service. From original request. See Appendix A. Contains an acquirer-assessed transaction fee. The fee amount is not included in field 4. The first character is C for credit, or D for debit, as appropriate. Identifies the financial institution acting as the acquirer of this transaction. Value is constant for all transaction requests and responses. From original request. Fixed NP10 Req Fixed NP6 Req Fixed NP6 Req Fixed NP4 Req Fixed NP4 Cond Fixed NP4 Req Fixed NP3 Req Fixed NP4 Req Fixed NP2 Req Fixed ANS9 Cond for Bill Payment only LLVAR NP11 Req Version 4.02 Page 55 Last modified August 12, 2009

Debit and EBT Reversal Request Message (Continued) Bit Data Element Number Name 037 Retrieval Reference Number 038 Auth ID Response 041 Card Acceptor Term ID 042 Card Acceptor ID 043 Card Acceptor Name / Location 049 Transaction Currency 059 National POS Geographic Data 060 Additional POS Info 060.1 Terminal Type 060.2 Terminal Entry Capability 061.1 Other Transaction Amount 062 Payment Description Format Attr Presence A number used with other data elements as a key to identify and track all messages related to a given customer transaction or series of system messages. The format for this field is YDDDHHNNNNNN, where YDDD is the date in Julian format, HH is the hour and N-N is a 6 digit transaction number. From original request. The authorization code provided by the issuer when a transaction is approved. (Only an approved transaction can be reversed Unique terminal/device ID. Merchant-defined value. Merchant ID. Assigned by Bank of America Merchant Services. See Appendix A. Name and location of the card acceptor where the transaction occurred. See Appendix A. Positions: 1-25 Card acceptor name 26-38 City name 39-40 Alpha country code From original request. ISO defined code representing the currency of this transaction. A field to describe the location of the card acceptor within the country. See Appendix A for values. A group of subfields that provide additional information about the point of service. See Appendix A for values. Identifies the point-of-service terminal. From original request. See Appendix A for values. Identifies the terminal s capability to electronically read account numbers and expiration dates from cards. From original request. See Appendix A for values. Contains the cash back amount, if any. If the transaction does not include cash back, this field is not sent. Contains authorizations characteristics to the Fixed AN12 Req Fixed AN6 Opt (N/A Returns) Fixed ANS8 Req Fixed Fixed ANS 15 ANS 40 Req Req Fixed NP3 Req LLVAR BBVAR ANS 14 Var by use Cond Req Fixed NP1 Req Fixed NP1 Req BBVAR NP12 Cond LLVAR B8 + Req for Bill Service Fields back-end authorizer. See Appendix A. AN59 Payment only 062.0 Bit Map Indicates presence of subfields. Fixed B8 Req for Bill Payment only Version 4.02 Page 56 Last modified August 12, 2009

Debit and EBT Reversal Request Message (Continued) Bit Data Element Number Name 062.4 Market- Specific Data Identifier 063 Private-use Field Description Format Attr Presence Identifies the industry for which marketspecific data has been provided. Copied from original request. See Appendix A. Used for identifying the acquirer s network ID, as well as various reason codes. See Appendix A. Fixed AN1 Req for Bill Payment only LLVAR Var. by use 063.0 Bit Map Indicates presence of subfields. Fixed B3 Req 063.1 Network ID A code that specifies the network to be used Fixed NP4 Req for authorization of the message. See 063.2 Preauth Time Limit 063.3 Message Reason 063.6 Chargeback Reduction Flags 090 Original Data Elements 104 Transaction Description 111 Additional Data Acquirer 114 Transport Data 164 Large Private Data 1 165 Large Private Data 2 166 Large Private Data 3 Appendix A for values. The time (in hours) the issuer agrees to hold funds for an acquirer. Used only in preauth and completion reversals. Explains the reason for sending the reversal. See Appendix A for values. Contains seven indicators, also used in the BASE II System to assist in the Visa effort to reduce the number of chargebacks. From original request. See Appendix A. Information for tracking the current message back to prior messages for the same cardholder transaction. See Appendix A for detailed field layout. Contains additional billing or reporting information about transaction or message processing. Copied from request. See Appendix A. Used to house the EBT FNS# and/or the EBT Voucher number or the EBT case number. See Appendix A for field use. A value assigned by the merchant. It is returned in the reversal response message. See Appendix A. Information to be moved between the acquirer and the issuer. Contains multiple tag-identified subfields. From original request. See Appendix A for subfield definitions and uses. (Reserved for future use) Information to be moved between the acquirer and the issuer. Contains multiple tag-identified subfields. From original request. (Reserved for future use) Information to be moved between the acquirer and the issuer. Contains multiple tag-identified subfields. From original request. Req Fixed NP4 Req preauth rev, completion rev only Fixed NP4 Req Fixed ANS7 Req for Bill Payment only Fixed NP42 Req LLVAR LLVAR LLVAR LLVAR LLVAR LLVAR ANS 100 ANS3 2 TLV (**) 255 TLV (**) 255 TLV (**) 255 TLV (**) 255 Req for Bill Payment only Req for EBT only Opt Cond for Bill Payment only N/A (reserved for future use) N/A (reserved for future use) Version 4.02 Page 57 Last modified August 12, 2009

Debit and EBT Reversal Request Message (Continued) Bit Data Element Number Name 167 Large Private Data 4 Description Format Attr Presence (Reserved for future use) Information to be moved between the acquirer and the issuer. Contains multiple tag-identified subfields. From original request. Contains the payee name. From original request. 168 Acquirer Trace Data 169 Payee Phone Contains the payee s phone/pager number. From original request. 170 Private Use Contains the street address of the card Card Acceptor acceptor the location where the transaction Street occurred. See Appendix A. Address LLVAR LLVAR LLVAR Fixed TLV (**) 255 ANS 61 ANS 25 ANS 25 N/A (reserved for future use) Cond for Bill Payment only Req for Bill Payment only Req Version 4.02 Page 58 Last modified August 12, 2009

3.10 Debit and EBT Reversal Response Message 3.10.1 Debit Purchase 3.10.2 Debit Purchase with Cash Back 3.10.3 Debit Preauthorized Purchase 3.10.4 Debit Completion 3.10.5 Debit Bill Payment 3.10.6 Debit Preauthorized Purchase with Cash Back 3.10.7 Debit Completion with Cash Back 3.10.8 Debit Return 3.10.9 EBT Food Stamp Purchase 3.10.10 EBT Food Stamp Return 3.10.11 EBT Cash Benefit Purchase 3.10.12 EBT Cash Benefit Purchase with Cash Back 3.10.13 EBT Cash Benefit Cash Withdrawal This message is used to send a reversal response message from Bank of America Merchant Services MultiLink to the POS for a Debit, EBT Food Stamp or Cash Benefit Reversal. The chart below describes: Bit Numbers and Names of all possible data elements for this message If constant, the value to be placed in the field A description of how each data element is used The format and attributes of each data element Required, Optional, Conditional or Not Applicable status of each data element Bit Data Element Description Format Attr Presence Number Name Message Type Value to represent the type of message. Fixed NP4 Req Value: 0410. See Appendix A. Primary Bit Represents the presence of secondary bit Fixed B8 Req Map map and data elements in bits 2 through 64. 001 Secondary Bit Represents the presence of tertiary bit map Fixed B8 Cond Map and data elements in bits 66 through 128. 065 Tertiary Bit Represents the presence of data elements in Fixed B8 Cond Map bits 130 through 192. 002 Primary Contains the cardholder account number. LLVAR NP19 Req Account Number Copied from request message. 003 Processing Defines the type of transaction. Copied from Fixed NP6 Req request message. See Appendix A. 004 Amount 1 Transaction amount. Copied from request Fixed NP12 Req message. 007 Transmission Date and Time Date and Time transaction is sent through the network assigned by the originator. Fixed NP10 Req 011 System Trace Audit Number Expressed in GMT MMDDhhmmss. A number assigned by the message initiator that identifies a cardholder transaction. Copied from request message. Fixed NP6 Req Version 4.02 Page 59 Last modified August 12, 2009

Debit and EBT Reversal Response Message (Continued) Bit Data Element Number Name 019 Acquiring Institution Country 025 POS Condition 028 Transaction Fee Amount 032 Acquiring Institution ID 037 Retrieval Reference Number 039 Response 041 Card Acceptor Term ID 042 Card Acceptor ID 049 Transaction Currency 063 Private-use Field Description Format Attr Presence Identifies the country of the location where the transaction occurred. Copied from request message. Describes the condition under which the transaction takes place at the point of service. Copied from request message. See Appendix A. Contains an acquirer-assessed transaction fee. The fee amount is not included in field 4. The first character is C for credit, or D for debit, as appropriate. Identifies the financial institution acting as the acquirer of this transaction. Value is constant for all transaction requests and responses. Copied from request message. A number used with other data elements as a key to identify and track all messages related to a given customer transaction or series of system messages. The format for this field is YDDDHHNNNNNN, where YDDD is the date in Julian format, HH is the hour and N-N is a 6 digit transaction number. From the original request. A code that defines the disposition of the transaction. See Appendix A for values. Unique terminal/device ID. Merchant-defined value. Merchant ID. Assigned by Bank of America Merchant Services. See Appendix A. ISO defined code representing the currency of this transaction. Copied from request message. Used for identifying the acquirer s network ID, as well as various reason codes. See Appendix A. Fixed NP3 Req Fixed NP2 Req Fixed ANS9 Cond for Bill Payment only LLVAR NP11 Req Fixed AN12 Req Fixed AN2 Req Fixed ANS8 Req Fixed ANS Req 15 Fixed NP3 Req LLVAR Var. by use 063.0 Bit Map Indicates presence of subfields. Fixed B3 Req 063.1 Network ID A code that specifies the network used for Fixed NP4 Req authorization of the message. Copied from 063.2 Preauth Time Limit 090 Original Data Elements the request message. See Appendix A. The time (in hours) the issuer agrees to hold funds for an acquirer. Used only in preauth and completion reversals. Information for tracking the current message back to prior messages for the same cardholder transaction. See Appendix A for detailed field layout. Copied from the request message. Req Fixed NP4 Req preauth rev, completion rev only Fixed NP42 Req Version 4.02 Page 60 Last modified August 12, 2009

Debit and EBT Reversal Response Message (Continued) Bit Data Element Number Name 114 Transport Data Description Format Attr Presence A value assigned by the merchant. Copied from reversal request message. See Appendix A. LLVAR TLV (**) 255 Cond Version 4.02 Page 61 Last modified August 12, 2009

3.11 Credit Request Message 3.11.1 Credit Purchase 3.11.2 Credit Purchase with Cash Back 3.11.2 Credit Merchandise Return 3.11.3 Credit Card Verification 3.11.4 Credit Balance Inquiry This message is used to send a request message from the POS to Bank of America Merchant Services MultiLink for a Credit Purchase, Merchandise Return or Card Verification. The Processing field (bit 3) differentiates the transaction type. The chart below describes: Bit Numbers and Names of all possible data elements for this message If constant, the value to be placed in the field A description of how each data element is used The format and attributes of each data element Required, Optional, Conditional or Not Applicable status of each data element Bit Number Data Element Name Message Type Description Format Attr Presence Value to represent the type of message Value: 0100. See Appendix A. Fixed NP4 Req Represents the presence of secondary bit Fixed B8 Req map and data elements in bits 2 through 64. Represents the presence of tertiary bit map Fixed B8 Cond and data elements in bits 66 through 128. Represents the presence of data elements in Fixed B8 Cond bits 130 through 192. Contains the cardholder account number. LLVAR NP19 Req Primary Bit Map 001 Secondary Bit Map 065 Tertiary Bit Map 002 Primary Account Number 003 Processing Defines the type of transaction. See Appendix A. 004 Amount 1 Transaction Amount. Assumes a 2 position decimal, right-justified, zero filled. This field contains the total amount including the purchase amount and cash back if indicated. Cashback amount only supported for Discover cards. Transactions settled through Bank of America Merchant Services s settlement system are limited to 7 characters ($99,999.99). 007 Transmission Date and Time Date and Time transaction is sent through the network assigned by the originator. Expressed in GMT MMDDhhmmss. 011 System Trace Audit Number A number assigned by the message initiator that identifies a cardholder transaction. 012 Local Time Time of the transaction, in merchant s local time. This value stays constant throughout the life of the transaction. This field must be sent in the settlement file. Expressed as hhmmss. Fixed NP6 Req Fixed NP12 Req Fixed NP10 Req Fixed NP6 Req Fixed NP6 Opt (Req for Card Not Present) Version 4.02 Page 62 Last modified August 12, 2009

Credit Request Message (Continued) Bit Data Element Description Format Attr Presence Number Name 013 Local Date Date of the transaction, in merchant s local date. This value stays constant throughout the life of the transaction. This field must be Fixed NP4 Opt (Req for Card Not Present) sent in the settlement file. Expressed as MMDD. 014 Expiration Date The year and month after which the card expires. Format: YYMM. If not available, Fixed NP4 Req 018 Merchant Type 019 Acquiring Institution Country 022 POS Entry Mode 025 POS Condition 032 Acquiring Institution ID enter 4912. A code describing the merchant s type of business, product or service. Bank of America Merchant Services-assigned value. Identifies the country of the location where the transaction occurred. See Appendix A for values. Defines the method of data entry of the account number and whether a PIN was entered on this transaction. See Appendix A for values. Describes the condition under which the transaction takes place at the point of service. See Appendix A for values. Identifies the financial institution acting as the acquirer of this transaction. Value is constant for all transaction requests and responses. This is an Bank of America Merchant Services assigned identification number. Value 45592900000. 035 Track 2 Data Contents of Track 2 as read from the magnetic stripe of the card, excluding the beginning and ending sentinels and LRC characters. Present only if Track 2 is read or assembled via a contactless means at the terminal. 037 Retrieval Reference Number 041 Card Acceptor Terminal ID 042 Card Acceptor ID A number used with other data elements as a key to identify and track all messages related to a given customer transaction or series of system messages. The format for this field is YDDDHHNNNNNN, where YDDD is the date in Julian format, HH is the hour and N-N is a 6 digit transaction number. Unique terminal/device ID. Merchant-defined value. Merchant ID. Assigned by Bank of America Merchant Services. See Appendix A. Fixed NP4 Req Fixed NP3 Req Fixed NP4 Req Fixed NP2 Req LLVAR NP11 Req LLVAR NP37 Cond Fixed AN12 Req Fixed ANS8 Req Fixed ANS 15 Req Version 4.02 Page 63 Last modified August 12, 2009

Credit Request Message (Continued) Bit Data Element Number Name 043 Card Acceptor Name / Location Description Format Attr Presence Name and location of the card acceptor where the transaction occurred. See Appendix A. Positions: 1-25 Card acceptor name 26-38 City name 39-40 Alpha country code 045 Track 1 Data Contents of Track 1 as read from the magnetic stripe of the card, excluding the beginning and ending sentinels and LRC characters. Present only if Track 1 read. 048 Additional Data Private 049 Transaction Currency Used for miscellaneous information (multiple uses and field formats). See Appendix A. ISO defined code representing the currency of this transaction. 054 Add l Amount For Healthcare Auto-Substantiation transactions, contains one or more amounts for various classes of healthcare purchases. See Appendix A for a full description. 055 EM and Chip Data 059 National POS Geographic Data 060 Additional POS Info 060.1 Terminal Type 060.2 Terminal Entry Capability 060.3 Chip Condition 060.4 Special Condition Indicator Existing Debt 060.5 Merchant Group Indicator 060.6 Chip Transaction Indicator Electronic Magnetic Signature and chip data. See Appendix A. A field to describe the location of the card acceptor within the country. See Appendix A for values. Provides additional information about the point of service. See Appendix A for details. Identifies the point-of-service terminal. See Appendix A for values. Identifies the terminal s capability to electronically read account numbers and expiration dates from cards. See Appendix A for values. Provides information about VSDC cards when read at VSDC terminals. See Appendix A for values. Indicates whether a payment is being made on an existing debt. See Appendix A for values. Identifies the general category of the card acceptor and transaction. See Appendix A for values. Set when message from the terminal is for a VSDC transaction. See Appendix A for values. Fixed LLVAR ANS 40 ANS 76 Req Cond LLVAR Var. Cond by use Fixed NP3 Req LLVAR BBVAR LLVAR ANS 120 TLV (**) 255 ANS 14 Req for Healthcare Auto- Substantiation only Cond Cond BBVAR NP6 Req Fixed NP1 Req Fixed NP1 Req Fixed NP1 Cond Fixed NP1 Cond Fixed NP2 Cond Fixed NP1 Cond Version 4.02 Page 64 Last modified August 12, 2009

Credit Request Message (Continued) Bit Data Element Number Name 060.7 Chip Authentication Reliability Indicator 060.8 Mail Order / Telephone Order / Electronic Commerce Indicator 060.9 Cardholder ID Method 060.10 Partial Authorization / Balance Indicator 061.1 Other Transaction Amount 062 Payment Service Fields Description Format Attr Presence Indicates the reliability of a transaction in the VSDC environment. See Appendix A for values. Identifies the type of mail or telephone order or the level of security used in en e- commerce transaction over an open network. See Appendix A for values. Identifies the method of transaction authentication. See Appendix A for values. Indicates whether the device supports partial authorizations and whether the merchant desires balances to be returned on credit financial transactions. See Appendix A for values. Contains the cash back amount, if any. If the transaction does not include cash back, this field is not sent. Contains authorizations characteristics to the back-end authorizer. See Appendix A. 062.0 Bit Map Indicates presence of subfields. Not used for card verification. 062.1 Authorization Characteristic Indicator 062.4 Market- Specific Data Identifier 114 Transport Data 123 Address Verification Data 126 Private-Use Fields Used by the acquirer processor to request Custom Payment Services (CPS) and MasterCard recurring payments. Not used for card verification. See Appendix A. Identifies the industry for which marketspecific data has been provided. See Appendix A. A value assigned by the merchant. It is returned in the response message. See Appendix A. Contains selected portions of the cardholder s address for verification. See Appendix A. Used for VISA epay, VISA Secure Electronic Commerce and CVV2 services. See Appendix A. Fixed NP1 Cond Fixed NP2 Cond Fixed NP1 Cond Fixed NP1 Cond BBVAR NP12 Cond LLVAR B8 + AN59 Req (N/A card verification) Fixed B8 Req (N/A card verification) Fixed AN1 Req (N/A card verification) Fixed AN1 Req for Healthcare Auto- Substantiation and Ecommerce Aggregation only LLVAR TLV Opt (**) 255 LLVAR ANS Cond 29 LLVAR B8 + var. by use Cond 126.0 Bit Map Indicates presence of subfields. Fixed B8 Req 126.8 Transaction ID Unique number (XID) generated by the Fixed B20 Cond (VSEC) merchant server to identify the transaction. Version 4.02 Page 65 Last modified August 12, 2009

Credit Request Message (Continued) Bit Data Element Description Format Attr Presence Number Name 126.9 CAVV Data Contains Cardholder Authentication Fixed NP40 Cond Verification Value. See Appendix A. 126.10 CVV2 Contains VISA or Diners Club CVV2, Fixed AN6 Cond Authorization Request Data MasterCard CVC2 or Discover or American Express CID data. See Appendix A. 126.15 UCAF Indicates presence of MasterCard Universal Fixed AN1 Cond Indicator Card Authentication Field. See Appendix A. 126.16 UCAF Value MasterCard Universal Card Authentication LLVAR AN32 Cond Field value generated by merchant server to identify the transaction. 163 NTIA Coupon UPC/SKU data for digital-to-analog converter LLVAR AN34 Cond Data 170 Private Use Card Acceptor Street Address 171 Private Use General box. See Appendix A. Contains the street address of the card acceptor the location where the transaction occurred. See Appendix A. Fields unique to Bank of America Merchant Services processing. See descriptions of subfields below and in Appendix A. Fixed ANS 25 LLLVAR B8 + var. by use 171.0 Bit Map Indicates presence of subfields. Fixed B8 Req 171.1 Merchant A unique value assigned by the merchant. Fixed ANS Order Number See Appendix A. 16 171.2 Merchant Reference Number 171.4 Sales Tax Amount 171.5 Customer A unique non-zero number assigned by the merchant to be used for transaction tracking. See Appendix A. Assumes 2 decimal places, right-justified zero filled. Contains amount of tax associated with transaction. This value will be captured and logged for settlement processing. Maximum number of digits for MasterCard transactions = 7. See Appendix A. Applicable in commercial card transactions only. A code that may be given to the merchant by a cardholder customer. This field may be reported back on reporting provided to a cardholder and may represent a general ledger number or cost center number to be associated with the purchase being made. See Appendix A. Opt Cond (Req for Card Not Present, Host Capture) Cond (Req for Card Not Present) Fixed N8 Cond (Req for Card Not Present) Fixed NP8 Req for Host Capture only Fixed AN17 Req for Host Capture only Version 4.02 Page 66 Last modified August 12, 2009

Credit Request Message (Continued) Bit Data Element Number Name 171.6 Auth Only Indicator 171.8 Transaction Subtype 173 Settlement Data 177 Supplemental Data 178 Promotional Program Data 179 Messaging Data Description Format Attr Presence Applicable for Credit purchase and test transactions only. Used by Host Capture merchants to indicate to Bank of America Merchant Services to not capture and create settlement for this transaction. A value of N indicates to Bank of America Merchant Services to not capture the transaction. Merchants not using Bank of America Merchant Services s Host Capture product may either send this field with a value of N for all transactions or omit sending the field (as they are set up for non-host-capture in Bank of America Merchant Services s settlement system). See Appendix A. Used to indicate various transaction situations. See Appendix A. Data needed to settle the transaction. See Appendix A. Various supplementary information about the transaction. See Appendix A. Information related to promotional programs for which the card qualifies. See Appendix A. An area where the merchant and the issuer may exchange message data. See Appendix A. Fixed AN1 Cond Fixed AN1 Cond BBB VAR BBB VAR BBB VAR BBB VAR TLV (21) 999 TLV (21) 999 TLV (21) 999 TLV (21) 999 Cond Cond Cond Cond Version 4.02 Page 67 Last modified August 12, 2009

3.12 Credit Response Message 3.12.1 Credit Purchase 3.12.2 Credit Purchase with Cash Back 3.12.3 Credit Merchandise Return 3.12.4 Credit Card Verification 3.12.5 Credit Balance Inquiry This message is used to send a response message from Bank of America Merchant Services MultiLink to the POS for a Credit Purchase or Merchandise Return. The Processing field (bit 3) differentiates the transaction type. The chart below describes: Bit Numbers and Names of all possible data elements for this message If constant, the value to be placed in the field A description of how each data element is used The format and attributes of each data element Required, Optional, Conditional or Not Applicable status of each data element Bit Number Data Element Name Message Type Description Format Attr Presence Value to represent the type of message Value: 0110. See Appendix A. Primary Bit Represents the presence of secondary bit Map map and data elements in bits 2 through 64. 001 Secondary Bit Represents the presence of tertiary bit map Map and data elements in bits 66 through 128. 065 Tertiary Bit Represents the presence of data elements in Map bits 130 through 192. 002 Primary Contains the cardholder account number. Account Copied from request message. Number 003 Processing Defines the type of transaction. Copied from request message. See Appendix A. 004 Amount 1 Transaction Amount. Copied from request message. Exception: If the merchant has indicated support for partial approvals and the transaction is approved for other than the requested amount, this field will contain the approved amount and bit 54 will contain the original amount. 007 Transmission Date and Time 011 System Trace Audit Number 019 Acquiring Institution Country Date and Time transaction is sent through the network assigned by the originator. Expressed in GMT MMDDhhmmss. A number assigned by the message initiator that identifies a cardholder transaction. Copied from request message. Identifies the country of the location where the transaction occurred. Copied from request message. Fixed NP4 Req Fixed B8 Req Fixed B8 Cond Fixed B8 Cond LLVAR NP19 Req Fixed NP6 Req Fixed NP12 Req Fixed NP10 Req Fixed NP6 Req Fixed NP3 Req Version 4.02 Page 68 Last modified August 12, 2009

Credit Response Message (Continued) Bit Data Element Number Name 025 POS Condition 032 Acquiring Institution ID 037 Retrieval Reference Number 038 Authorization ID Response 039 Response 041 Card Acceptor Terminal ID 042 Card Acceptor ID 044 Additional Response Data 044.1 Response Source / Reason 044.2 Address Verification Result Description Format Attr Presence Describes the condition under which the transaction takes place at the point of service. Copied from request message. See Appendix A. Identifies the financial institution acting as the acquirer of this transaction. Value is constant for all transaction requests and responses. Copied from request message. A number used with other data elements as a key to identify and track all messages related to a given customer transaction or series of system messages. The format for this field is YDDDHHNNNNNN, where YDDD is the date in Julian format, HH is the hour and N-N is a 6 digit transaction number. Copied from request message. The authorization code provided by the issuer when a transaction is approved. Only present in approved transactions. A code that defines the disposition of the transaction. See Appendix A for values. Unique terminal/device ID. Merchant-defined value. Merchant ID. Assigned by Bank of America Merchant Services. See Appendix A. Miscellaneous data needed in the response. Not used in card verification. See Appendix A. Identifies entity responding to request. Used only for VISA cards. Any value other than 5 indicates that VISA has stood in. Not used in card verification. See Appendix A. Describes the address verification result. See Appendix A for values. Not used in card verification. 044.3 Present and space-filled only if subsequent subfields needed. 044.4 Present and space-filled only if subsequent subfields needed. Fixed NP2 Req LLVAR N11 Req Fixed AN12 Req Fixed AN6 Cond Fixed AN2 Req Fixed ANS8 Req Fixed ANS 15 Req LLVAR AN25 Req (N/A card verification) Fixed AN1 Req (N/A card verification) Fixed AN1 Req (N/A card verification) Fixed AN1 Cond (if subsequent subfields needed) Fixed AN1 Cond (if subsequent subfields needed) 044.5 CVV Results See Appendix A for values. Fixed AN1 Cond 044.6 Present and space-filled only if subsequent subfields needed. Fixed AN2 Cond (if subsequent subfields needed) Version 4.02 Page 69 Last modified August 12, 2009

Credit Response Message (Continued) Bit Data Element Description Format Attr Presence Number Name 044.7 Present and space-filled only if subsequent subfields needed. Fixed AN1 Cond (if subsequent subfields needed) 044.8 Present and space-filled only if subsequent subfields needed. Fixed AN1 Cond (if subsequent subfields 044.9 Present and space-filled only if subsequent subfields needed. 044.10 CVV2 Result See Appendix A for codes. Used for VISA and Diners Club CVV2, MasterCard CVC2, and AMEX and Discover CID. Not used in card verification. 044.11 Present and space-filled only if subsequent subfields needed. 044.12 Present and space-filled only if subsequent subfields needed. 044.13 CAVV Result Contains the 3-D Secure Cardholder Authentication Verification Value results code. See Appendix A. Used for miscellaneous information (multiple uses and field formats). See Appendix A. ISO defined code representing the currency of this transaction. Copied from request message. 048 Additional Data Private 049 Transaction Currency 054 Add l Amount For transactions in which the merchant has indicated support for partial approvals, contains the original requested amount. If the merchant has indicated the desire to receive balances on financial transactions, may contain one or more balances. For balance inquiry transactions, the amount type subfield(s) will indicate the type(s) of balances returned multiple balances are possible. See Appendix A for a full description. 062 Payment Service Fields Contains authorizations characteristics to the back-end authorizer. See Appendix A. 062.0 Bit Map Indicates presence of subfields. Not used for card verification. needed) Fixed AN1 Cond (if subsequent subfields needed) Fixed AN1 Opt (N/A card verification) Fixed ANS2 Cond (if subsequent subfields needed) Fixed ANS1 Cond (if subsequent subfields needed) Fixed ANS1 Cond LLVAR Var. Cond by use Fixed NP3 Req LLVAR ANS 120 LLVAR B8 + AN59 Cond Req (N/A card verification) Fixed B8 Req (N/A card verification) Version 4.02 Page 70 Last modified August 12, 2009

Credit Response Message (Continued) Bit Data Element Number Name 062.1 Authorization Characteristic Indicator 062.2 Transaction Identifier 062.3 Validation 062.4 Market- Specific Data Identifier 062.17 MasterCard Compliance Info Description Format Attr Presence Indicates level of qualification for Custom Payment Services (CPS). See Appendix A for values. Not used for card verification. Issuer-generated identifier unique for each original transaction. Not used for card verification. A code calculated to ensure that key fields in the 0100 authorization message match their respective fields in the deferred clearing message. Not used for card verification. Identifies the industry for which marketspecific data has been provided. See Appendix A. Contains qualification information for the MasterCard Interchange Compliance program. Not used for card verification. See Appendix A. 062.23 Card Results Indicates the card program that the card used in the transaction is signed up for. See Appendix A. 114 Transport Data 115 Interchange Reference Number 171 Private Use General A value assigned by the merchant. Copied from request message. See Appendix A. The retrieval reference number assigned in the switch interchange. Used for optional reversal processing. Contact your Bank of America Merchant Services account representative for use. See Appendix A. Fields unique to Bank of America Merchant Services processing. See descriptions of subfields below and in Appendix A. Fixed AN1 Req (N/A card verification) Fixed NP15 Cond (N/A card verification) Fixed AN4 Cond (N/A card verification) Fixed AN1 Req for Healthcare Auto- Substantiation and Ecommerce Aggregation only Fixed AN15 Cond (N/A card verification) Fixed AN2 Cond LLVAR LLVAR TLV (**) 255 ANS 12 LLLVAR B8 + var. by use 171.0 Bit Map Indicates presence of subfields. Fixed B8 Req 171.1 Merchant A unique value assigned by the merchant. Fixed ANS Order Number Copied from request. See Appendix A. 16 171.2 Merchant Reference Number 171.3 Merchant Advice A unique non-zero number assigned by the merchant to be used for transaction tracking. Copied from request. See Appendix A. Contains recurring payments response information. See Appendix A. Cond Opt Cond (Req for Card Not Present, Host Capture) Cond (Req for Card Not Present) Fixed N8 Cond (Req for Card Not Present) Fixed ANS2 Cond (Req for Card Not Present) Version 4.02 Page 71 Last modified August 12, 2009

Credit Response Message (Continued) Bit Data Element Number Name 171.4 Sales Tax Amount 171.5 Customer 171.8 Transaction Subtype 172 Point of Service Data 177 Supplemental Data 178 Promotional Program Data 179 Messaging Data Description Format Attr Presence Contains amount of tax associated with transaction. Copied from request. See Appendix A. Applicable in commercial card transactions only. A code that may be given to the merchant by a cardholder customer. Copied from request. See Appendix A. Used to indicate various transaction situations. See Appendix A. A series of codes that identify the transaction at the point of service in a format unique to the authorizing switch interface. Must be sent in the settlement file. See Appendix A. Various supplementary information about the transaction. See Appendix A. Information related to promotional programs for which the card qualifies. See Appendix A. An area where the merchant and the issuer may exchange message data. See Appendix A. Fixed NP8 N/A (Req for Host Capture) Fixed AN17 N/A (Req for Host Capture) Fixed AN1 Cond Fixed AN12 Cond BBB VAR BBB VAR BBB VAR TLV (21) 999 TLV (21) 999 TLV (21) 999 Cond Cond Cond Version 4.02 Page 72 Last modified August 12, 2009

3.13 Credit Bill Payment Request Message 3.13.1 Credit Bill Payment This message is used to send a request message from the POS to Bank of America Merchant Services MultiLink for a Credit Bill Payment. The Processing field (bit 3) identifies the transaction type. The chart below describes: Bit Numbers and Names of all possible data elements for this message If constant, the value to be placed in the field A description of how each data element is used The format and attributes of each data element Required, Optional, Conditional or Not Applicable status of each data element Bit Number Data Element Name Message Type Description Format Attr Presence Value to represent the type of message Value: 0100. See Appendix A. Fixed NP4 Req Represents the presence of secondary bit Fixed B8 Req map and data elements in bits 2 through 64. Represents the presence of tertiary bit map Fixed B8 Cond and data elements in bits 66 through 128. Represents the presence of data elements in Fixed B8 Cond bits 130 through 192. Contains the cardholder account number. LLVAR NP19 Req Primary Bit Map 001 Secondary Bit Map 065 Tertiary Bit Map 002 Primary Account Number 003 Processing Defines the type of transaction. See Appendix A. 004 Amount 1 Transaction Amount. Assumes a 2 position decimal, right-justified, zero filled. Transactions settled through Bank of America Merchant Services s settlement system are limited to 7 characters ($99,999.99). 007 Transmission Date and Time Date and Time transaction is sent through the network assigned by the originator. Expressed in GMT MMDDhhmmss. 011 System Trace Audit Number A number assigned by the message initiator that identifies a cardholder transaction. 012 Local Time Time of the transaction, in merchant s local time. This value stays constant throughout the life of the transaction. This field must be sent in the settlement file. Expressed as hhmmss. 013 Local Date Date of the transaction, in merchant s local date. This value stays constant throughout the life of the transaction. This field must be sent in the settlement file. Expressed as MMDD. Fixed NP6 Req Fixed NP12 Req Fixed NP10 Req Fixed NP6 Req Fixed NP6 Opt Fixed NP4 Opt Version 4.02 Page 73 Last modified August 12, 2009

Credit Bill Payment Request Message (Continued) Bit Data Element Number Name 014 Expiration Date 018 Merchant Type 019 Acquiring Institution Country 022 POS Entry Mode 025 POS Condition 028 Transaction Fee Amount 032 Acquiring Institution ID 037 Retrieval Reference Number 041 Card Acceptor Terminal ID 042 Card Acceptor ID 043 Card Acceptor Name / Location Description Format Attr Presence The year and month after which the card expires. Format: YYMM. If not available, do not send this bit. Merchant Category (MCC). Specific values are needed for the Bill Payment transaction. Bank of America Merchant Services-assigned value. Identifies the country of the location where the transaction occurred. See Appendix A for values. Defines the method of data entry of the account number and whether a PIN was entered on this transaction. See Appendix A for values. Describes the condition under which the transaction takes place at the point of service. See Appendix A for values. Contains an acquirer-assessed transaction fee. The fee amount is not included in field 4. The first character is C for credit, or D for debit, as appropriate. Identifies the financial institution acting as the acquirer of this transaction. Value is constant for all transaction requests and responses. This is an Bank of America Merchant Services assigned identification number. Value 45592900000. A number used with other data elements as a key to identify and track all messages related to a given customer transaction or series of system messages. The format for this field is YDDDHHNNNNNN, where YDDD is the date in Julian format, HH is the hour and N-N is a 6 digit transaction number. Unique terminal/device ID. Merchant-defined value. Merchant ID. Assigned by Bank of America Merchant Services. See Appendix A. Name and location of the card acceptor where the transaction occurred. See Appendix A. Positions: 1-25 Card acceptor name 26-38 City name 39-40 Alpha country code Fixed NP4 Req Fixed NP4 Req Fixed NP3 Req Fixed NP4 Req Fixed NP2 Req Fixed ANS9 Cond LLVAR NP11 Req Fixed AN12 Req Fixed ANS8 Req Fixed Fixed ANS 15 ANS 40 Req Req Version 4.02 Page 74 Last modified August 12, 2009

Credit Bill Payment Request Message (Continued) Bit Data Element Number Name 049 Transaction Currency 059 National POS Geographic Data 060 Additional POS Info 060.1 Terminal Type 060.2 Terminal Entry Capability 060.3 Chip Condition 060.4 Special Condition Indicator Existing Debt 060.5 Merchant Group Indicator 060.6 Chip Transaction Indicator 060.7 Chip Authentication Reliability Indicator 060.8 Mail Order / Telephone Order / Electronic Commerce Indicator Description Format Attr Presence ISO defined code representing the currency of this transaction. A field to describe the location of the card acceptor within the country. See Appendix A for values. Provides additional information about the point of service. See Appendix A for details. Identifies the point-of-service terminal. See Appendix A for values. Identifies the terminal s capability to electronically read account numbers and expiration dates from cards. See Appendix A for values. Provides information about VSDC cards when read at VSDC terminals. See Appendix A for values. Indicates whether a payment is being made on an existing debt. See Appendix A for values. Identifies the general category of the card acceptor and transaction. See Appendix A for values. Set when message from the terminal is for a VSDC transaction. See Appendix A for values. Indicates the reliability of a transaction in the VSDC environment. See Appendix A for values. Identifies the type of mail or telephone order or the level of security used in en e- commerce transaction over an open network. See Appendix A for values. 060.9 Cardholder ID Method Identifies the method of transaction authentication. See Appendix A for values. 060.10 Pad Present and value = 0 only if 060.9 is present (to fill the byte of data). 061.1 Other Contains the cash back amount, if any. If the Transaction transaction does not include cash back, this Amount field is not sent. Fixed NP3 Req LLVAR ANS 14 Cond BBVAR NP6 Req Fixed NP1 Req Fixed NP1 Req Fixed NP1 Cond Fixed NP1 Cond Fixed NP2 Cond Fixed NP1 Cond Fixed NP1 Cond Fixed NP2 Cond Fixed NP1 Cond Fixed NP1 Cond BBVAR NP12 Cond 062 Payment Contains authorizations characteristics to the LLVAR B8 + Req Service Fields back-end authorizer. See Appendix A. AN59 062.0 Bit Map Indicates presence of subfields. Fixed B8 Req Version 4.02 Page 75 Last modified August 12, 2009

Credit Bill Payment Request Message (Continued) Bit Data Element Number Name 062.1 Authorization Characteristic Indicator 062.4 Market- Specific Data Identifier 104 Transaction Description 123 Address Verification Data 126 Private-Use Fields Description Format Attr Presence Used by the acquirer processor to request Custom Payment Services (CPS) and MasterCard recurring payments. See Appendix A. Identifies the industry for which marketspecific data has been provided. See Appendix A. Contains additional billing or reporting information about transaction or message processing. See Appendix A. Contains selected portions of the cardholder s address for verification. See Appendix A. Used for VISA epay, VISA Secure Electronic Commerce and CVV2 services. See Appendix A. Fixed AN1 Req Fixed AN1 Req LLVAR LLVAR ANS 100 ANS 29 LLVAR B8 + var. by use Req Cond Cond 126.0 Bit Map Indicates presence of subfields. Fixed B8 Req 126.8 Transaction ID Unique number (XID) generated by the Fixed B20 Cond (VSEC) merchant server to identify the transaction. 126.9 CAVV Data Contains Cardholder Authentication Fixed NP40 Cond Verification Value. See Appendix A. 126.10 CVV2 Authorization Request Data Contains VISA or Diners Club CVV2, MasterCard CVC2 or Discover or American Express CID data. See Appendix A. Fixed AN6 Cond 126.15 UCAF Indicator Indicates presence of MasterCard Universal Card Authentication Field. See Appendix A. 126.16 UCAF Value MasterCard Universal Card Authentication Field value generated by merchant server to identify the transaction. 164 Large Private Data 1 165 Large Private Data 2 166 Large Private Data 3 167 Large Private Data 4 168 Acquirer Trace Data Information to be moved between the acquirer and the issuer. Contains multiple tag-identified subfields. See Appendix A for subfield definitions and uses. (Reserved for future use) Information to be moved between the acquirer and the issuer. Contains multiple tag-identified subfields. (Reserved for future use) Information to be moved between the acquirer and the issuer. Contains multiple tag-identified subfields. (Reserved for future use) Information to be moved between the acquirer and the issuer. Contains multiple tag-identified subfields. Contains the payee name. Format is 1- character identifier (=0), followed by the name. Fixed AN1 Cond LLVAR AN32 Cond LLVAR LLVAR LLVAR LLVAR LLVAR TLV (**) 255 TLV (**) 255 TLV (**) 255 TLV (**) 255 ANS 61 Req N/A (reserved for future use) N/A (reserved for future use) N/A (reserved for future use) Req Version 4.02 Page 76 Last modified August 12, 2009

Credit Bill Payment Request Message (Continued) Bit Data Element Description Format Attr Presence Number Name 169 Payee Phone Contains the payee s phone/pager number. LLVAR ANS Req For regulatory purposes, periodic statements are expected to disclose the phone number if the consumer has questions about the payment. 25 170 Private Use Card Acceptor Street Address Contains the street address of the card acceptor the location where the transaction occurred. See Appendix A. Fixed ANS 25 Opt 171 Private Use General Fields unique to Bank of America Merchant Services processing. See descriptions of subfields below and in Appendix A. LLLVAR B8 + var. by use Cond 171.0 Bit Map Indicates presence of subfields. Fixed B8 Req 171.1 Merchant A unique value assigned by the merchant. Fixed ANS Cond Order Number See Appendix A. 16 171.2 Merchant Reference Number A unique non-zero number assigned by the merchant to be used for transaction tracking. See Appendix A. Fixed N8 Cond 171.5 Customer 171.6 Auth Only Indicator 173 Settlement Data 177 Supplemental Data 178 Promotional Program Data Applicable in commercial card transactions only. A code that may be given to the merchant by a cardholder customer. This field may be reported back on reporting provided to a cardholder and may represent a general ledger number or cost center number to be associated with the purchase being made. See Appendix A. Applicable for Credit purchase transactions only. Used by Host Capture merchants to indicate to Bank of America Merchant Services to not capture and create settlement for this transaction. A value of N indicates to Bank of America Merchant Services to not capture the transaction. Merchants not using Bank of America Merchant Services s Host Capture product may either send this field with a value of N for all transactions or omit sending the field (as they are set up for non- Host-Capture in Bank of America Merchant Services s settlement system). See Appendix A. Contains data needed for transaction settlement. See Appendix A. Various supplementary information about the transaction. See Appendix A. Information related to promotional programs for which the card qualifies. See Appendix A. Fixed AN17 Cond Fixed AN1 Cond BBB VAR BBB VAR BBB VAR TLV (21) 999 TLV (21) 999 TLV (21) 999 Cond Cond Cond Version 4.02 Page 77 Last modified August 12, 2009

Credit Bill Payment Request Message (Continued) Bit Data Element Number Name 179 Messaging Data Description Format Attr Presence An area where the merchant and the issuer may exchange message data. See Appendix A. BBB VAR TLV (21) 999 Cond Version 4.02 Page 78 Last modified August 12, 2009

3.14 Credit Bill Payment Response Message 3.14 Credit Bill Payment This message is used to send a response message from Bank of America Merchant Services MultiLink to the POS for a Credit Bill Payment. The Processing field (bit 3) identifies the transaction type. The chart below describes: Bit Numbers and Names of all possible data elements for this message If constant, the value to be placed in the field A description of how each data element is used The format and attributes of each data element Required, Optional, Conditional or Not Applicable status of each data element Bit Data Element Description Format Attr Presence Number Name Message Type Value to represent the type of message Fixed NP4 Req Value: 0110. See Appendix A. Primary Bit Represents the presence of secondary bit Fixed B8 Req Map map and data elements in bits 2 through 64. 001 Secondary Bit Represents the presence of tertiary bit map Fixed B8 Cond Map and data elements in bits 66 through 128. 065 Tertiary Bit Represents the presence of data elements in Fixed B8 Cond Map bits 130 through 192. 002 Primary Contains the cardholder account number. LLVAR NP19 Req Account Number Copied from request message. 003 Processing Defines the type of transaction. Copied from Fixed NP6 Req request message. See Appendix A. 004 Amount 1 Transaction Amount. Copied from request Fixed NP12 Req message. 007 Transmission Date and Time Date and Time transaction is sent through the network assigned by the originator. Fixed NP10 Req 011 System Trace Audit Number 019 Acquiring Institution Country 025 POS Condition 028 Transaction Fee Amount 032 Acquiring Institution ID Expressed in GMT MMDDhhmmss. A number assigned by the message initiator that identifies a cardholder transaction. Copied from request message. Identifies the country of the location where the transaction occurred. Copied from request message. Describes the condition under which the transaction takes place at the point of service. Copied from request message. See Appendix A. Contains an acquirer-assessed transaction fee. The fee amount is not included in field 4. The first character is C for credit, or D for debit, as appropriate. Identifies the financial institution acting as the acquirer of this transaction. Value is constant for all transaction requests and responses. Copied from request message. Fixed NP6 Req Fixed NP3 Req Fixed NP2 Req Fixed ANS9 Cond LLVAR N11 Req Version 4.02 Page 79 Last modified August 12, 2009

Credit Bill Payment Response Message (Continued) Bit Data Element Number Name 037 Retrieval Reference Number 038 Authorization ID Response 039 Response 041 Card Acceptor Terminal ID 042 Card Acceptor ID 044 Additional Response Data 044.1 Response Source / Reason 044.2 Address Verification Result Description Format Attr Presence A number used with other data elements as a key to identify and track all messages related to a given customer transaction or series of system messages. The format for this field is YDDDHHNNNNNN, where YDDD is the date in Julian format, HH is the hour and N-N is a 6 digit transaction number. Copied from request message. The authorization code provided by the issuer when a transaction is approved. Only present in approved transactions. A code that defines the disposition of the transaction. See Appendix A for values. Unique terminal/device ID. Merchant-defined value. Merchant ID. Assigned by Bank of America Merchant Services. See Appendix A. Miscellaneous data needed in the response. See Appendix A. Identifies entity responding to request. Used only for VISA cards. Any value other than 5 indicates that VISA has stood in. See Appendix A. Describes the address verification result. See Appendix A for values. 044.3 Present and space-filled only if subsequent subfields needed. 044.4 Present and space-filled only if subsequent subfields needed. Fixed AN12 Req Fixed AN6 Cond Fixed AN2 Req Fixed ANS8 Req Fixed ANS Req 15 LLVAR AN25 Req Fixed AN1 Req Fixed AN1 Req Fixed AN1 Cond (if subsequent subfields needed) Fixed AN1 Cond (if subsequent subfields needed) 044.5 CVV Results See Appendix A for values. Fixed AN1 Cond 044.6 Present and space-filled only if subsequent subfields needed. Fixed AN2 Cond (if subsequent subfields needed) 044.7 Present and space-filled only if subsequent subfields needed. 044.8 Present and space-filled only if subsequent subfields needed. Fixed AN1 Cond (if subsequent subfields needed) Fixed AN1 Cond (if subsequent subfields needed) Version 4.02 Page 80 Last modified August 12, 2009

Credit Bill Payment Response Message (Continued) Bit Data Element Description Format Attr Presence Number Name 044.9 Present and space-filled only if subsequent subfields needed. Fixed AN1 Cond (if subsequent subfields needed) 044.10 CVV2 Result See Appendix A for codes. Used for VISA and Diners Club CVV2, MasterCard CVC2, Fixed AN1 Opt and AMEX and Discover CID. 044.11 Present and space-filled only if subsequent subfields needed. 044.12 Present and space-filled only if subsequent subfields needed. 044.13 CAVV Result 049 Transaction Currency 062 Payment Service Fields Contains the 3-D Secure Cardholder Authentication Verification Value results code. See Appendix A. ISO defined code representing the currency of this transaction. Copied from request message. Contains authorizations characteristics to the back-end authorizer. See Appendix A. Fixed ANS2 Cond (if subsequent subfields needed) Fixed ANS1 Cond (if subsequent subfields needed) Fixed ANS1 Cond Fixed NP3 Req LLVAR B8 + Req AN59 062.0 Bit Map Indicates presence of subfields. Fixed B8 Req 062.1 Authorization Characteristic Indicator 062.2 Transaction Identifier 062.3 Validation 062.17 MasterCard Compliance Info Indicates level of qualification for Custom Payment Services (CPS). See Appendix A for values. Issuer-generated identifier unique for each original transaction. A code calculated to ensure that key fields in the 0100 authorization message match their respective fields in the deferred clearing message. Contains qualification information for the MasterCard Interchange Compliance program. See Appendix A. 062.23 Card Results Indicates the card program that the card used in the transaction is signed up for. See Appendix A. 104 Transaction Description Contains additional billing or reporting information about transaction or message processing. Copied from request. See Appendix A. Fixed AN1 Req Fixed NP15 Cond Fixed AN4 Cond Fixed AN15 Cond Fixed AN2 Cond LLVAR ANS 100 Req Version 4.02 Page 81 Last modified August 12, 2009

Credit Bill Payment Response Message (Continued) Bit Data Element Number Name 164 Large Private Data 1 165 Large Private Data 2 166 Large Private Data 3 167 Large Private Data 4 Description Format Attr Presence Information to be moved between the acquirer and the issuer. Contains multiple tag-identified subfields. See Appendix A for subfield definitions and uses. (Reserved for future use) Information to be moved between the acquirer and the issuer. Contains multiple tag-identified subfields. (Reserved for future use) Information to be moved between the acquirer and the issuer. Contains multiple tag-identified subfields. (Reserved for future use) Information to be moved between the acquirer and the issuer. Contains multiple tag-identified subfields. Contains the payee name. Copied from request. 168 Acquirer Trace Data 169 Payee Phone Contains the payee s phone/pager number. Copied from request. 171 Private Use Fields unique to Bank of America Merchant General Services processing. See descriptions of LLVAR LLVAR LLVAR LLVAR LLVAR LLVAR TLV (**) 255 TLV (**) 255 TLV (**) 255 TLV (**) 255 ANS 61 ANS 25 LLLVAR B8 + Cond var. by subfields below and in Appendix A. use 171.0 Bit Map Indicates presence of subfields. Fixed B8 Req 171.1 Merchant A unique value assigned by the merchant. Fixed ANS Cond Order Number Copied from request. See Appendix A. 16 Fixed N8 Cond 171.2 Merchant Reference Number 171.3 Merchant Advice 171.5 Customer 172 Point of Service Data 177 Supplemental Data 178 Promotional Program Data 179 Messaging Data A unique non-zero number assigned by the merchant to be used for transaction tracking. Copied from request. See Appendix A. Contains recurring payments response information. See Appendix A. Applicable in commercial card transactions only. A code that may be given to the merchant by a cardholder customer. Copied from request. See Appendix A. A series of codes that identify the transaction at the point of service in a format unique to the authorizing switch interface. Must be sent in the settlement file. See Appendix A. Various supplementary information about the transaction. See Appendix A. Information related to promotional programs for which the card qualifies. See Appendix A. An area where the merchant and the issuer may exchange message data. See Appendix A. Req N/A (reserved for future use) N/A (reserved for future use) N/A (reserved for future use) Cond Req Fixed ANS2 Cond (Req for Card Not Present) Fixed AN17 Cond Fixed AN12 Cond BBB VAR BBB VAR BBB VAR TLV (21) 999 TLV (21) 999 TLV (21) 999 Cond Cond Cond Version 4.02 Page 82 Last modified August 12, 2009

3.15 Credit Reversal Request Message 3.15.1 Credit Purchase 3.15.2 Credit Purchase with Cash Back 3.15.3 Credit Merchandise Return 3.15.4 Credit Bill Payment This message is used to send a reversal request message from the POS to Bank of America Merchant Services MultiLink for a Credit Reversal. The chart below describes: Bit Numbers and Names of all possible data elements for this message If constant, the value to be placed in the field A description of how each data element is used The format and attributes of each data element Required, Optional, Conditional or Not Applicable status of each data element Bit Number Data Element Name Message Type Description Format Attr Presence Value to represent the type of message. Value: 0400. See Appendix A. Fixed NP4 Req Represents the presence of secondary bit Fixed B8 Req map and data elements in bits 2 through 64. Represents the presence of tertiary bit map Fixed B8 Cond and data elements in bits 66 through 128. Represents the presence of data elements in Fixed B8 Cond bits 130 through 192. Contains the cardholder account number. LLVAR NP19 Req Primary Bit Map 001 Secondary Bit Map 065 Tertiary Bit Map 002 Primary Account Number 003 Processing Defines the type of transaction. Copied from original request. See Appendix A. 004 Amount 1 Transaction Amount. From original request. Exception: If the transaction was authorized for a lesser amount than the original requested amount, this field contains the authorized amount. 007 Transmission Date and Time 011 System Trace Audit Number Date and Time transaction is sent through the network assigned by the originator. Expressed in GMT MMDDhhmmss. A number assigned by the message initiator that identifies a cardholder transaction. From original request. 012 Local Time Time of the transaction, in merchant s local time. This value stays constant throughout the life of the transaction. This field must be sent in the settlement file. Expressed as hhmmss. From the original request. 013 Local Date Date of the transaction, in merchant s local date. This value stays constant throughout the life of the transaction. This field must be sent in the settlement file. Expressed as MMDD. From the original request. Fixed NP6 Req Fixed NP12 Req Fixed NP10 Req Fixed NP6 Req Fixed NP6 Cond (Req for Card Not Present) Fixed NP4 Cond (Req for Card Not Present) Version 4.02 Page 83 Last modified August 12, 2009

Credit Reversal Request Message (Continued) Bit Data Element Number Name 014 Expiration Date 018 Merchant Type 019 Acquiring Institution Country 022 POS Entry Mode 025 POS Condition 028 Transaction Fee Amount 032 Acquiring Institution ID 037 Retrieval Reference Number 038 Authorization ID Response 041 Card Acceptor Terminal ID 042 Card Acceptor ID 043 Card Acceptor Name / Location 049 Transaction Currency Description Format Attr Presence The year and month after which the card expires. Format: YYMM. A code describing the merchant s type of business, product or service. Bank of America Merchant Services-assigned value. Identifies the country of the location where the transaction occurred. See Appendix A for values. Defines the method of data entry of the account number and whether a PIN was entered on this transaction. See Appendix A for values. From original request. Describes the condition under which the transaction takes place at the point of service. From original request. See Appendix A. Contains an acquirer-assessed transaction fee. The fee amount is not included in field 4. The first character is C for credit, or D for debit, as appropriate. Identifies the financial institution acting as the acquirer of this transaction. Value is constant for all transaction requests and responses. From original request. A number used with other data elements as a key to identify and track all messages related to a given customer transaction or series of system messages. The format for this field is YDDDHHNNNNNN, where YDDD is the date in Julian format, HH is the hour and N-N is a 6 digit transaction number. From original request. The authorization code provided by the issuer when a transaction is approved. (Only an approved transaction can be reversed). Unique terminal/device ID. Merchant-defined value. Merchant ID. Assigned by Bank of America Merchant Services. See Appendix A. Name and location of the card acceptor where the transaction occurred. See Appendix A. Positions: 1-25 Card acceptor name 26-38 City name 39-40 Alpha country code From original request. ISO defined code representing the currency of this transaction. Fixed NP4 Req Fixed NP4 Req Fixed NP3 Req Fixed NP4 Req Fixed NP2 Req Fixed ANS9 N/A (Cond for Bill Payment) LLVAR N11 Req Fixed AN12 Req Fixed AN6 Opt Fixed ANS8 Req Fixed Fixed ANS 15 ANS 40 Req Req Fixed NP3 Req Version 4.02 Page 84 Last modified August 12, 2009

Credit Reversal Request Message (Continued) Bit Data Element Number Name 059 National POS Geographic Data 060 Additional POS Info 060.1 Terminal Type 060.2 Terminal Entry Capability 060.3 Chip Condition 060.4 Special Condition Indicator Existing Debt 060.5 Merchant Group Indicator 060.6 Chip Transaction Indicator 060.7 Chip Authentication Reliability Indicator 060.8 Mail Order / Telephone Order / Electronic Commerce Indicator 061.1 Other Transaction Amount Description Format Attr Presence A field to describe the location of the card acceptor within the country. See Appendix A for values. A group of subfields that provide additional information about the point of service. See Appendix A for values. Identifies the point-of-service terminal. From original request. See Appendix A for values. Identifies the terminal s capability to electronically read account numbers and expiration dates from cards. From original request. See Appendix A for values. Provides information about VSDC cards when read at VSDC terminals. From original request. See Appendix A for values. Indicates whether a payment is being made on an existing debt. From original request. See Appendix A for values. Identifies the general category of the card acceptor and transaction. From original request. See Appendix A for values. Set when message from the terminal is for a VSDC transaction. From original request. See Appendix A for values. Indicates the reliability of a transaction in the VSDC environment. From original request. See Appendix A for values. Identifies the type of mail or telephone order or the level of security used in en e- commerce transaction over an open network. From original request. See Appendix A for values. Contains the cash back amount, if any. If the transaction does not include cash back, this field is not sent. Contains authorizations characteristics to the back-end authorizer. See Appendix A. LLVAR BBVAR ANS 14 Var by use Cond Req Fixed NP1 Req Fixed NP1 Req Fixed NP1 Cond Fixed NP1 Cond Fixed NP2 Cond Fixed NP1 Cond Fixed NP1 Cond Fixed NP2 Cond BBVAR NP12 Cond 062 Payment Service Fields LLVAR B8 + AN59 Cond 062.0 Bit Map Indicates presence of subfields Fixed B8 Req 062.1 Authorization Used by the acquirer processor to request Fixed AN1 Opt Characteristic Custom Payment Services (CPS). Indicator Value: Y. See Appendix A. 062.2 Transaction Identifier Issuer-generated unique identifier for each original transaction. Only present if returned in response. Fixed NP15 Cond Version 4.02 Page 85 Last modified August 12, 2009

Credit Reversal Request Message (Continued) Bit Data Element Number Name 062.4 Market- Specific Data Identifier 090 Original Data Elements 095 Replacement Amounts 095.1 Actual Transaction Amount 095.2 Actual Settlement Amount 095.3 Actual Transaction Fee Amount 095.4 Actual Settlement Fee Amount 104 Transaction Description 114 Transport Data 115 Interchange Reference Number 126 Private-Use Fields Description Format Attr Presence Identifies the industry for which marketspecific data has been provided. Copied from original request. See Appendix A. Information for tracking the current message back to prior messages for the same cardholder transaction. See Appendix A for detailed field layout. Contains the corrected amount of a transaction in a partial reversal. Defined as a fixed-length with four subfields, but only the first 12-character subfield is used. Used for VISA cards only. The corrected actual amount of the cardholder s transaction. Fixed AN1 Req for Bill Payment, Healthcare Auto- Substantiation only Fixed NP42 Req Fixed AN42 Cond Fixed AN12 Cond Unused. Value = 000000000000. Fixed AN12 Cond Unused. Value = 000000000. Fixed AN9 Cond Unused. Value = 000000000. Fixed AN9 Cond Contains additional billing or reporting information about transaction or message processing. See Appendix A. A value assigned by the merchant. It is returned in the reversal response message. See Appendix A. The retrieval reference number assigned in the switch interchange. Copied from response message. Used for optional reversal processing. Contact your Bank of America Merchant Services account representative for use. See Appendix A. Used for VISA epay, VISA Secure Electronic Commerce and CVV2 services. See Appendix A. LLVAR LLVAR LLVAR ANS 100 TLV (**) 255 ANS 12 LLVAR B8 + var. by use N/A (Req for Bill Payment) Opt Opt Cond 126.0 Bit Map Indicates presence of subfields. Fixed B8 Req 126.8 Transaction ID Unique number (XID) generated by the Fixed B20 Cond (VSEC) merchant server to identify the transaction. 126.9 CAVV Data Contains Cardholder Authentication Fixed NP40 Cond Verification Value. See Appendix A. 163 NTIA Coupon Data UPC/SKU data for digital-to-analog converter box. See Appendix A. LLVAR AN34 Cond Version 4.02 Page 86 Last modified August 12, 2009

Credit Reversal Request Message (Continued) Bit Data Element Number Name 164 Large Private Data 1 165 Large Private Data 2 166 Large Private Data 3 167 Large Private Data 4 168 Acquirer Trace Data Description Format Attr Presence Information to be moved between the acquirer and the issuer. Contains multiple tag-identified subfields. See Appendix A for subfield definitions and uses. (Reserved for future use) Information to be moved between the acquirer and the issuer. Contains multiple tag-identified subfields. (Reserved for future use) Information to be moved between the acquirer and the issuer. Contains multiple tag-identified subfields. (Reserved for future use) Information to be moved between the acquirer and the issuer. LLVAR LLVAR LLVAR LLVAR TLV (**) 255 TLV (**) 255 TLV (**) 255 TLV (**) 255 Contains multiple tag-identified subfields. Contains the payee name. LLVAR ANS 61 169 Payee Phone Contains the payee s phone/pager number. From original request. 170 Private Use Card Acceptor Street Address 171 Private Use General Contains the street address of the card acceptor the location where the transaction occurred. See Appendix A. Fields unique to Bank of America Merchant Services processing. See descriptions of subfields below and in Appendix A. LLVAR Fixed ANS 25 ANS 25 LLLVAR B8 + var. by use 171.0 Bit Map Indicates presence of subfields. Fixed B8 Req 171.1 Merchant Fixed ANS Order Number 16 A unique value assigned by the merchant. Copied from original request. See Appendix A. N/A (Cond for Bill Payment) N/A (reserved for future use) N/A (reserved for future use) N/A (reserved for future use) N/A (Cond for Bill Payment) N/A (Req for Bill Payment) Opt Cond (Req for Card Not Present, Host Capture) Cond (Req for Card Not Present) 171.2 Merchant Reference Number 171.4 Sales Tax Amount A unique non-zero number assigned by the merchant to be used for transaction tracking. Copied from original request. See Appendix A. Assumes 2 decimal places, right-justified zero filled. Contains amount of tax associated with transaction. This value will be captured and logged for settlement processing. Maximum number of digits for MasterCard transactions = 7. See Appendix A. Fixed N8 Cond (Req for Card Not Present) Fixed NP8 N/A (Req for Host Capture) Version 4.02 Page 87 Last modified August 12, 2009

Credit Reversal Request Message (Continued) Bit Data Element Number Name 171.5 Customer 171.6 Auth Only Indicator 173 Settlement Data 177 Supplemental Data 178 Promotional Program Data 179 Messaging Data Description Format Attr Presence Applicable in commercial card transactions only. A code that may be given to the merchant by a cardholder customer. This field may be reported back on reporting provided to a cardholder and may represent a general ledger number or cost center number to be associated with the purchase being made. See Appendix A. Applicable for Credit purchase transactions only. Used by Host Capture merchants to indicate to Bank of America Merchant Services to not capture and create settlement for this transaction. A value of N indicates to Bank of America Merchant Services to not capture the transaction. Merchants not using Bank of America Merchant Services s Host Capture product may either send this field with a value of N for all transactions or omit sending the field (as they are set up for non- Host-Capture in Bank of America Merchant Services s settlement system). See Appendix A. Contains data needed for transaction settlement. See Appendix A. Various supplementary information about the transaction. See Appendix A. Information related to promotional programs for which the card qualifies. See Appendix A. An area where the merchant and the issuer may exchange message data. See Appendix A. Fixed AN17 N/A (Req for Host Capture) Fixed AN1 Cond BBB VAR BBB VAR BBB VAR BBB VAR TLV (21) 999 TLV (21) 999 TLV (21) 999 TLV (21) 999 Cond Cond Cond Cond Version 4.02 Page 88 Last modified August 12, 2009

3.16 Credit Reversal Response Message 3.16.1 Credit Purchase 3.16.2 Credit Purchase with Cash Back 3.16.3 Credit Merchandise Return 3.16.4 Credit Bill Payment This message is used to send a reversal response message from Bank of America Merchant Services MultiLink to the POS for a Credit Reversal. The chart below describes: Bit Numbers and Names of all possible data elements for this message If constant, the value to be placed in the field A description of how each data element is used The format and attributes of each data element Required, Optional, Conditional or Not Applicable status of each data element Bit Data Element Description Format Attr Presence Number Name Message Type Value to represent the type of message. Fixed NP4 Req Value: 0410. See Appendix A. Primary Bit Represents the presence of secondary bit Fixed B8 Req Map map and data elements in bits 2 through 64. 001 Secondary Bit Represents the presence of tertiary bit map Fixed B8 Cond Map and data elements in bits 66 through 128. 065 Tertiary Bit Represents the presence of data elements in Fixed B8 Cond Map bits 130 through 192. 002 Primary Contains the cardholder account number. LLVAR NP19 Req Account Number Copied from request message. 003 Processing Defines the type of transaction. Copied from Fixed NP6 Req request message. See Appendix A. 004 Amount 1 Transaction Amount. Copied from request Fixed NP12 Req message. 007 Transmission Date and Time Date and Time transaction is sent through the network assigned by the originator. Fixed NP10 Req 011 System Trace Audit Number 019 Acquiring Institution Country 025 POS Condition 028 Transaction Fee Amount Expressed in GMT MMDDhhmmss. A number assigned by the message initiator that identifies a cardholder transaction. Copied from request message. Identifies the country of the location where the transaction occurred. Copied from request message.. Describes the condition under which the transaction takes place at the point of service. From original request. See Appendix A. Contains an acquirer-assessed transaction fee. The fee amount is not included in field 4. The first character is C for credit, or D for debit, as appropriate. Fixed NP6 Req Fixed NP3 Req Fixed NP2 Req Fixed ANS9 N/A (Cond for Bill Payment) Version 4.02 Page 89 Last modified August 12, 2009

Credit Reversal Response Message (Continued) Bit Data Element Number Name 032 Acquiring Institution ID 037 Retrieval Reference Number Description Format Attr Presence Identifies the financial institution acting as the acquirer of this transaction. Value is constant for all transaction requests and responses. Copied from request message. A number used with other data elements as a key to identify and track all messages related to a given customer transaction or series of system messages. The format for this field is YDDDHHNNNNNN, where YDDD is the date in Julian format, HH is the hour and N-N is a 6 digit transaction number. Copied from request message. A code that defines the disposition of the transaction. See Appendix A for values. Unique terminal/device ID. Merchant-defined value. Merchant ID. Assigned by Bank of America LLVAR N11 Req Fixed AN12 Req 039 Response Fixed AN2 Req 041 Card Acceptor Fixed ANS8 Req Terminal ID 042 Card Acceptor Fixed ANS Req ID Merchant Services. See Appendix A. 15 049 Transaction ISO defined code representing the currency Fixed NP3 Req Currency of this transaction. Copied from request message. 062 Payment Contains authorizations characteristics to the LLVAR B8 + Cond Service Fields back-end authorizer. See Appendix A. AN59 062.0 Bit Map Indicates presence of subfields. Fixed B8 Req 062.1 Authorization Indicates level of qualification for Custom Fixed AN1 Opt Characteristic Payment Services (CPS). See Appendix A Indicator for values. 062.2 Transaction Identifier 090 Original Data Elements 114 Transport Data 171 Private Use General Issuer-generated unique identifier for each original transaction. Information for tracking the current message back to prior messages for the same cardholder transaction. Copied from request message. See Appendix A. A value assigned by the merchant. Copied from reversal request message. See Appendix A. Fields unique to Bank of America Merchant Services processing. See descriptions of subfields below and in Appendix A. Fixed NP15 Opt Fixed NP42 Req LLVAR TLV (**) 255 LLLVAR B8 + var. by use 171.0 Bit Map Indicates presence of subfields. Fixed B8 Req 171.1 Merchant A unique value assigned by the merchant. Fixed ANS Order Number Copied from reversal request. See Appendix 16 171.2 Merchant Reference Number A. A unique non-zero number assigned by the merchant to be used for transaction tracking. Copied from reversal request. See Appendix A. Cond Cond (Req for Card Not Present, Host Capture) Cond (Req for Card Not Present) Fixed N8 Cond (Req for Card Not Present) Version 4.02 Page 90 Last modified August 12, 2009

Credit Reversal Response Message (Continued) Bit Data Element Number Name 171.4 Sales Tax Amount 171.5 Customer Description Format Attr Presence Contains amount of tax associated with transaction. Copied from request message. See Appendix A. Applicable in commercial card transactions only. A code that may be given to the merchant by a cardholder customer. Copied from request message. See Appendix A. Fixed NP8 N/A (Req for Host Capture) Fixed AN17 N/A (Req for Host Capture) Version 4.02 Page 91 Last modified August 12, 2009

3.17 Credit Advice Request Message 3.17.1 Credit Purchase This message is used to send an advice message from the POS to Bank of America Merchant Services MultiLink for a Credit Purchase. The advice message is used for the final sale of a fuel pump transaction, and can also be used when the merchant has chosen to perform stand-in for the transaction. The preferred method in a stand-in situation is for the merchant to send a credit request once the system is back online. If that request is declined, then the merchant should send a credit advice. The Processing field (bit 3) differentiates the transaction type. The chart below describes: Bit Numbers and Names of all possible data elements for this message If constant, the value to be placed in the field A description of how each data element is used The format and attributes of each data element Required, Optional, Conditional or Not Applicable status of each data element Bit Number Data Element Name Message Type Description Format Attr Presence Value to represent the type of message Value: 0120. See Appendix A. Fixed NP4 Req Represents the presence of secondary bit Fixed B8 Req map and data elements in bits 2 through 64. Represents the presence of tertiary bit map Fixed B8 Cond and data elements in bits 66 through 128. Represents the presence of data elements in Fixed B8 Cond bits 130 through 192. Contains the cardholder account number. LLVAR NP19 Req Primary Bit Map 001 Secondary Bit Map 065 Tertiary Bit Map 002 Primary Account Number 003 Processing Defines the type of transaction. See Appendix A. 004 Amount 1 Transaction Amount. Assumes a 2 position decimal, right-justified, zero filled. This field contains the total amount including the purchase amount and cash back if indicated. Cashback amount only supported for Discover cards. Transactions settled through Bank of America Merchant Services s settlement system are limited to 7 characters ($99,999.99). 007 Transmission Date and Time 011 System Trace Audit Number 014 Expiration Date 018 Merchant Type Date and Time transaction is sent through the network assigned by the originator. Expressed in GMT MMDDhhmmss. A number assigned by the message initiator that identifies a cardholder transaction. The year and month after which the card expires. Format: YYMM. A code describing the merchant s type of business, product or service. Bank of America Merchant Services-assigned value. Fixed NP6 Req Fixed NP12 Req Fixed NP10 Req Fixed NP6 Req Fixed NP4 Req Fixed NP4 Req Version 4.02 Page 92 Last modified August 12, 2009

Credit Advice Request Message (Continued) Bit Data Element Number Name 019 Acquiring Institution Country 022 POS Entry Mode 025 POS Condition 032 Acquiring Institution ID Description Format Attr Presence Identifies the country of the location where the transaction occurred. See Appendix A for values. Defines the method of data entry of the account number and whether a PIN was entered on this transaction. See Appendix A for values. Describes the condition under which the transaction takes place at the point of service. See Appendix A for values. Identifies the financial institution acting as the acquirer of this transaction. Value is constant for all transaction requests and responses. This is an Bank of America Merchant Services assigned identification number. Value 45592900000. 035 Track 2 Data Contents of Track 2 as read from the magnetic stripe of the card, excluding the beginning and ending sentinels and LRC characters. Present only if Track 2 is read or assembled via a contactless means at the terminal. 037 Retrieval Reference Number 038 Authorization ID Response 039 Response 041 Card Acceptor Terminal ID 042 Card Acceptor ID 043 Card Acceptor Name / Location A number used with other data elements as a key to identify and track all messages related to a given customer transaction or series of system messages. The format for this field is YDDDHHNNNNNN, where YDDD is the date in Julian format, HH is the hour and N-N is a 6 digit transaction number. The authorization code provided by the issuer when a transaction is approved. Only present in approved transactions. A code that defines the disposition of the transaction. See Appendix A for values. Unique terminal/device ID. Merchant-defined value. Merchant ID. Assigned by Bank of America Merchant Services. See Appendix A. Name and location of the card acceptor where the transaction occurred. See Appendix A. Positions: 1-25 Card acceptor name 26-38 City name 39-40 Alpha country code 045 Track 1 Data Contents of Track 1 as read from the magnetic stripe of the card, excluding the beginning and ending sentinels and LRC characters. Present only if Track 1 read. Fixed NP3 Req Fixed NP4 Req Fixed NP2 Req LLVAR NP11 Req LLVAR NP37 Cond Fixed AN12 Req Fixed AN6 Cond Fixed AN2 Req Fixed ANS8 Req Fixed Fixed LLVAR ANS 15 ANS 40 ANS 76 Req Req Cond Version 4.02 Page 93 Last modified August 12, 2009

Credit Advice Request Message (Continued) Bit Data Element Number Name 049 Transaction Currency 055 EM and Chip Data 059 National POS Geographic Data 060 Additional POS Info 060.1 Terminal Type 060.2 Terminal Entry Capability 060.3 Chip Condition 060.4 Special Condition Indicator Existing Debt 060.5 Merchant Group Indicator 060.6 Chip Transaction Indicator 060.7 Chip Authentication Reliability Indicator 060.8 Mail Order / Telephone Order / Electronic Commerce Indicator Description Format Attr Presence ISO defined code representing the currency of this transaction. Electronic Magnetic Signature and chip data. See Appendix A. A field to describe the location of the card acceptor within the country. See Appendix A for values. A group of subfields that provide additional information about the point of service. See Appendix A for values. Identifies the point-of-service terminal. See Appendix A for values. Identifies the terminal s capability to electronically read account numbers and expiration dates from cards. See Appendix A for values. Provides information about VSDC cards when read at VSDC terminals. See Appendix A for values. Indicates whether a payment is being made on an existing debt. See Appendix A for values. Identifies the general category of the card acceptor and transaction. See Appendix A for values. Set when message from the terminal is for a VSDC transaction. See Appendix A for values. Indicates the reliability of a transaction in the VSDC environment. See Appendix A for values. Identifies the type of mail or telephone order or the level of security used in en e- commerce transaction over an open network. See Appendix A for values. 060.9 Cardholder ID Method Identifies the method of transaction authentication. See Appendix A for values. 060.10 Pad Present and value = 0 only if 060.9 is present (to fill the byte of data). 061.1 Other Contains the cash back amount, if any. If the Transaction transaction does not include cash back, this Amount field is not sent. 062 Payment Service Fields Contains authorizations characteristics to the back-end authorizer. See Appendix A. Fixed NP3 Req BBVAR LLVAR BBVAR TLV (**) 255 ANS 14 Var. by use Cond Cond Req Fixed NP1 Req Fixed NP1 Req Fixed NP1 Cond Fixed NP1 Cond Fixed NP2 Cond Fixed NP1 Cond Fixed NP1 Cond Fixed NP2 Cond Fixed NP1 Cond Fixed NP1 Cond BBVAR NP12 Cond LLVAR B8 + AN59 Req Version 4.02 Page 94 Last modified August 12, 2009

Credit Advice Request Message (Continued) Bit Data Element Description Format Attr Presence Number Name 062.0 Bit Map Indicates presence of subfields. Fixed B8 Req 062.1 Authorization Characteristic Indicator Used by the acquirer processor to request Custom Payment Services (CPS). Value: Y. See Appendix A. Fixed AN1 Req 062.17 MasterCard Compliance Info 114 Transport Data 126 Private-Use Fields Contains qualification information for the MasterCard Interchange Compliance program. See Appendix A. A value assigned by the merchant. It is returned in the response message. See Appendix A. Used for VISA epay, VISA Secure Electronic Commerce and CVV2 services. See Appendix A. Fixed AN15 Req for MasterCard Private Label only. LLVAR TLV (**) 255 LLVAR B8 + var. by use Opt Cond 126.0 Bit Map Indicates presence of subfields. Fixed B8 Req 126.8 Transaction ID Unique number (XID) generated by the Fixed B20 Cond (VSEC) merchant server to identify the transaction. 126.9 CAVV Data Contains Cardholder Authentication Fixed NP40 Cond Verification Value. See Appendix A. 126.10 CVV2 Authorization Request Data Contains VISA or Diners Club CVV2, MasterCard CVC2 or Discover or American Express CID data. See Appendix A. Fixed AN6 Cond 126.15 UCAF Indicator Indicates presence of MasterCard Universal Card Authentication Field. See Appendix A. 126.16 UCAF Value MasterCard Universal Card Authentication Field value generated by merchant server to identify the transaction. 170 Private Use Card Acceptor Street Address 171 Private Use General Contains the street address of the card acceptor the location where the transaction occurred. See Appendix A. Fields unique to Bank of America Merchant Services processing. See descriptions of subfields below and in Appendix A. Fixed AN1 Cond LLVAR AN32 Cond Fixed ANS 25 LLLVAR B8 + var. by use 171.0 Bit Map Indicates presence of subfields. Fixed B8 Req 171.1 Merchant A unique value assigned by the merchant. Fixed ANS Order Number See Appendix A. 16 171.2 Merchant Reference Number 171.4 Sales Tax Amount A unique non-zero number assigned by the merchant to be used for transaction tracking. See Appendix A. Assumes 2 decimal places, right-justified zero filled. Contains amount of tax associated with transaction. This value will be captured and logged for settlement processing. Maximum number of digits for MasterCard transactions = 7. See Appendix A. Opt Cond (Req for Card Not Present, Host Capture) Cond (Req for Card Not Present) Fixed N8 Cond (Req for Card Not Present) Fixed NP8 Cond Version 4.02 Page 95 Last modified August 12, 2009

Credit Advice Request Message (Continued) Bit Data Element Number Name 171.5 Customer 173 Settlement Data 177 Supplemental Data Description Format Attr Presence Applicable in commercial card transactions only. A code that may be given to the merchant by a cardholder customer. This field may be reported back on reporting provided to a cardholder and may represent a general ledger number or cost center number to be associated with the purchase being made. See Appendix A. Contains data needed for transaction settlement. See Appendix A. Additional data needed on this particular transaction. See Appendix A. Fixed AN17 Cond BBB VAR BBB VAR TLV (21) 999 TLV (21) 999 Cond Cond Version 4.02 Page 96 Last modified August 12, 2009

3.18 Credit Advice Response Message 3.18.1 Credit Purchase This message is used to send a response message from Bank of America Merchant Services MultiLink to the POS for a Credit Purchase advice. The Processing field (bit 3) differentiates the transaction type. The chart below describes: Bit Numbers and Names of all possible data elements for this message If constant, the value to be placed in the field A description of how each data element is used The format and attributes of each data element Required, Optional, Conditional or Not Applicable status of each data element Bit Data Element Description Format Attr Presence Number Name Message Type Value to represent the type of message Fixed NP4 Req Value: 0130. See Appendix A. Primary Bit Represents the presence of secondary bit Fixed B8 Req Map map and data elements in bits 2 through 64. 001 Secondary Bit Represents the presence of tertiary bit map Fixed B8 Cond Map and data elements in bits 66 through 128. 065 Tertiary Bit Represents the presence of data elements in Fixed B8 Cond Map bits 130 through 192. 002 Primary Contains the cardholder account number. LLVAR NP19 Req Account Number Copied from request message. 003 Processing Defines the type of transaction. Copied from Fixed NP6 Req request message. See Appendix A. 004 Amount 1 Transaction Amount. Copied from request Fixed NP12 Req message. 007 Transmission Date and Time Date and Time transaction is sent through the network assigned by the originator. Fixed NP10 Req 011 System Trace Audit Number 019 Acquiring Institution Country 025 POS Condition 032 Acquiring Institution ID Expressed in GMT MMDDhhmmss. A number assigned by the message initiator that identifies a cardholder transaction. Copied from request message. Identifies the country of the location where the transaction occurred. Copied from request message. Describes the condition under which the transaction takes place at the point of service. Copied from request message. See Appendix A. Identifies the financial institution acting as the acquirer of this transaction. Value is constant for all transaction requests and responses. Copied from request message. Fixed NP6 Req Fixed NP3 Req Fixed NP2 Req LLVAR N11 Req Version 4.02 Page 97 Last modified August 12, 2009

Credit Advice Response Message (Continued) Bit Data Element Number Name 037 Retrieval Reference Number 039 Response Description Format Attr Presence A number used with other data elements as a key to identify and track all messages related to a given customer transaction or series of system messages. The format for this field is YDDDHHNNNNNN, where YDDD is the date in Julian format, HH is the hour and N-N is a 6 digit transaction number. Copied from request message. A code that defines the disposition of the transaction. Copied from request message. See Appendix A. Unique terminal/device ID. Merchant-defined value. Merchant ID. Assigned by Bank of America Fixed AN12 Req Fixed AN2 Req 041 Card Acceptor Terminal ID Fixed ANS8 Req 042 Card Acceptor Fixed ANS Req ID Merchant Services. See Appendix A. 15 049 Transaction ISO defined code representing the currency Fixed NP3 Req Currency of this transaction. Copied from request message. 062 Payment Contains authorizations characteristics to the LLVAR B8 + Req Service Fields back-end authorizer. See Appendix A. AN59 062.0 Bit Map Indicates presence of subfields. Fixed B8 Req 062.1 Authorization Indicates level of qualification for Custom Fixed AN1 Req Characteristic Payment Services (CPS). See Appendix A Indicator for values. 062.17 MasterCard Compliance Info 114 Transport Data 171 Private Use General Contains qualification information for the MasterCard Interchange Compliance program. See Appendix A. A value assigned by the merchant. Copied from request message. See Appendix A. Fields unique to Bank of America Merchant Services processing. See descriptions of subfields below and in Appendix A. Fixed AN15 Req for MasterCard Private Label only. LLVAR TLV (**) 255 LLLVAR B8 + var. by use 171.0 Bit Map Indicates presence of subfields. Fixed B8 Req 171.1 Merchant A unique value assigned by the merchant. Fixed ANS Order Number Copied from request. See Appendix A. 16 171.2 Merchant Reference Number 171.3 Merchant Advice 171.4 Sales Tax Amount A unique non-zero number assigned by the merchant to be used for transaction tracking. Copied from request. See Appendix A. Contains recurring payments response information. See Appendix A. Contains amount of tax associated with transaction. Copied from advice request. See Appendix A. Cond Cond (Req for Card Not Present) Cond (Req for Card Not Present) Fixed N8 Cond (Req for Card Not Present) Fixed ANS2 Cond (Req for Card Not Present) Fixed NP8 Cond Version 4.02 Page 98 Last modified August 12, 2009

Credit Advice Response Message (Continued) Bit Data Element Number Name 171.5 Customer 172 Point of Service Data Description Format Attr Presence Applicable in commercial card transactions only. A code that may be given to the merchant by a cardholder customer. Copied from advice request. See Appendix A. A series of codes that identify the transaction at the point of service in a format unique to the authorizing switch interface. Must be sent in the settlement file. See Appendix A. Fixed AN17 Cond Fixed AN12 Cond (present only on Merchandise Return responses to non-host Draft Capture merchants) Version 4.02 Page 99 Last modified August 12, 2009

3.19 Check Acceptance Request Message 3.19.1 Check Acceptance Request This message is used to send a check acceptance request. The following chart describes: Bit Numbers and Names of all possible data elements for this message If constant, the value to be placed in the field A description of how each data element is used The format and attributes of each data element Required, Optional, Conditional or Not Applicable status of each data element Bit Data Element Description Format Attr Presence Number Name Message Type Value to represent the type of message. Fixed NP4 Req Value: 0100. See Appendix A. Primary Bit Represents the presence of secondary bit Fixed B8 Req Map map and data elements in bits 2 through 64. 001 Secondary Bit Represents the presence of tertiary bit map Fixed B8 Cond Map and data elements in bits 66 through 128. 065 Tertiary Bit Represents the presence of data elements in Fixed B8 Cond Map bits 130 through 192. 003 Processing Defines the type of transaction. Fixed NP6 Req Value: 030000. See Appendix A. 004 Amount 1 Transaction amount to be authorized. Fixed NP12 Req 007 Transmission Date and Time transaction is sent through Fixed NP10 Req Date and Time the network assigned by the originator. Expressed in GMT MMDDhhmmss. 011 System Trace A number assigned by the message initiator Fixed NP6 Req Audit Number that identifies a cardholder transaction. 012 Local Time Time of the transaction, in merchant s local Fixed NP6 Req time. This value stays constant throughout the life of the transaction. This field must be sent in the settlement file. Expressed as hhmmss. 013 Local Date Date of the transaction, in merchant s local Fixed NP4 Req date. This value stays constant throughout the life of the transaction. This field must be sent in the settlement file. Expressed as MMDD. 018 Merchant Merchant Category (MCC). Fixed NP4 Req Type 025 POS Condition 032 Acquiring Institution ID Describes the condition under which the transaction takes place at the point of service. 10 to indicate customer identity has been verified. See Appendix A. Identifies the financial institution acting as the acquirer of this transaction. Value is constant for all transaction requests and responses. Fixed NP2 Req LLVAR NP11 Req Version 4.02 Page 100 Last modified August 12, 2009

Check Acceptance Request Message (Continued) Bit Data Element Number Name 037 Retrieval Reference Number 041 Card Acceptor Term ID 042 Card Acceptor ID 043 Card Acceptor Name / Location 048 Additional Data 049 Transaction Currency 114 Transport Data 170 Private Use Card Acceptor Street Address Description Format Attr Presence A number used with other data elements as a key to identify and track all messages related to a given customer transaction or series of system messages. The format for this field is YDDDHHNNNNNN, where YDDD is the date in Julian format, HH is the hour and N-N is a 6 digit transaction number. Unique terminal/device ID. Merchant-defined value. Merchant ID. Assigned by Bank of America Merchant Services. See Appendix A. Name and location of the card acceptor where the transaction occurred. See Appendix A. Positions: 1-25 Card Acceptor name 26-38 City Name 39-40 Alpha Country code Customer identity information (see below). See Appendix A. ISO defined code representing the currency of this transaction. For merchant use (contents are echoed back on response). See Appendix A. Contains the street address of the card acceptor the location where the transaction occurred. See Appendix A. Fixed AN12 Req Fixed AN8 Req Fixed AN15 Req Fixed AN40 Req LLVAR AN Req 256 Fixed NP3 Req LLVAR Fixed TLV (**) 255 ANS 25 Opt Opt Version 4.02 Page 101 Last modified August 12, 2009

3.20 Check Acceptance Response Message 3.20.1 Check Acceptance Response This message is returned on a check acceptance request. The chart below describes: Bit Numbers and Names of all possible data elements for this message If constant, the value to be placed in the field A description of how each data element is used The format and attributes of each data element Required, Optional, Conditional or Not Applicable status of each data element Bit Data Element Description Format Attr Presence Number Name Message Type Value to represent the type of message. Fixed NP4 Req Value: 0110. See Appendix A. Primary Bit Represents the presence of secondary bit Fixed B8 Req Map map and data elements in bits 2 through 64. 001 Secondary Bit Represents the presence of tertiary bit map Fixed B8 Cond Map and data elements in bits 66 through 128. 065 Tertiary Bit Represents the presence of data elements in Fixed B8 Cond Map bits 130 through 192. 003 Processing Defines the type of transaction. Copied from Fixed NP6 Req request message. See Appendix A. 004 Amount 1 The authorized amount. Fixed NP12 Req 007 Transmission Copied from the request Fixed NP10 Req Date and Time 011 System Trace Audit Number A number assigned by the message initiator that identifies a cardholder transaction. Fixed NP6 Req 025 POS Condition 032 Acquiring Institution ID 037 Retrieval Reference Number 038 Auth ID Response 039 Response Copied from request message. Describes the condition under which the transaction takes place at the point of service. Copied from request message. See Appendix A. Identifies the financial institution acting as the acquirer of this transaction. Value is constant for all transaction requests and responses. Copied from request message. A number used with other data elements as a key to identify and track all messages related to a given customer transaction or series of system messages. The format for this field is YDDDHHNNNNNN, where YDDD is the date in Julian format, HH is the hour and N-N is a 6 digit transaction number. From the original request. The authorization code provided by the issuer when a transaction is approved. Will only be present for approved transactions. A code that defines the disposition of the transaction. See Appendix A for values Fixed NP2 Req LLVAR NP11 Req Fixed AN12 Req Fixed AN12 Cond Fixed AN2 Req Version 4.02 Page 102 Last modified August 12, 2009

Check Acceptance Response Message (Continued) Bit Data Element Number Name 041 Card Acceptor Term ID 042 Card Acceptor ID 048 Additional Data 049 Transaction Currency 114 Transport Data Description Format Attr Presence Unique terminal/device ID. Merchant-defined value. Copied from the request. Merchant ID. Assigned by Bank of America Merchant Services. Copied from the request. See Appendix A. Text information returned from the check vendor relating to the authorization. See Appendix A. ISO defined code representing the currency of this transaction. Copied from request message. For merchant use. (Contents echoed back from the request.). See Appendix A. Fixed AN8 Req Fixed AN15 Req LLVAR ANS 256 Opt Fixed NP3 Req LLVAR TLV (**) 255 Cond Version 4.02 Page 103 Last modified August 12, 2009

3.21 POS Check Request Message 3.21.1 POS Check Request This message is used to send a POS check request. The following chart describes: Bit Numbers and Names of all possible data elements for this message If constant, the value to be placed in the field A description of how each data element is used The format and attributes of each data element Required, Optional, Conditional or Not Applicable status of each data element Bit Data Element Description Format Attr Presence Number Name Message Type Value to represent the type of message. Fixed NP4 Req Value: 0200. See Appendix A. Primary Bit Represents the presence of secondary bit Fixed B8 Req Map map and data elements in bits 2 through 64. 001 Secondary Bit Represents the presence of tertiary bit map Fixed B8 Cond Map and data elements in bits 66 through 128. 065 Tertiary Bit Represents the presence of data elements in Fixed B8 Cond Map bits 130 through 192. 003 Processing Defines the type of transaction. See Fixed NP6 Req Appendix A. 004 Amount 1 Transaction amount to be authorized. Fixed NP12 Req 007 Transmission Date and Time transaction is sent through Fixed NP10 Req Date and Time the network assigned by the originator. Expressed in GMT MMDDhhmmss. 011 System Trace A number assigned by the message initiator Fixed NP6 Req Audit Number that identifies a cardholder transaction. 012 Local Time Time of the transaction, in merchant s local Fixed NP6 Req time. This value stays constant throughout the life of the transaction. This field must be sent in the settlement file. Expressed as hhmmss. 013 Local Date Date of the transaction, in merchant s local Fixed NP4 Req date. This value stays constant throughout the life of the transaction. This field must be sent in the settlement file. Expressed as MMDD. 018 Merchant Merchant Category (MCC). Fixed NP4 Req Type 019 Acquiring Institution Country 022 POS Entry Mode 025 POS Condition Identifies the country of the location where the transaction occurred. See Appendix A for values. Defines the method of data entry of the account number and whether a PIN was entered on this transaction. Value = 8400. Describes the condition under which the transaction takes place at the point of service. Value = 52. See Appendix A. Fixed NP3 Req Fixed NP4 Req Fixed NP2 Req Version 4.02 Page 104 Last modified August 12, 2009

POS Check Request Message (Continued) Bit Data Element Number Name 032 Acquiring Institution ID 037 Retrieval Reference Number 041 Card Acceptor Terminal ID 042 Card Acceptor ID 043 Card Acceptor Name / Location 048 Additional Data Private 049 Transaction Currency 059 National POS Geographic Data 060 Additional POS Info 060.1 Terminal Type 060.2 Terminal Entry Capability 061.1 Other Transaction Amount 063 Private-use Field Description Format Attr Presence Identifies the financial institution acting as the acquirer of this transaction. Value is constant for all transaction requests and responses. A number used with other data elements as a key to identify and track all messages related to a given customer transaction or series of system messages. The format for this field is YDDDHHNNNNNN, where YDDD is the date in Julian format, HH is the hour and N-N is a 6 digit transaction number. Unique terminal/device ID. Merchant-defined value. Merchant ID. Assigned by Bank of America Merchant Services. See Appendix A. Name and location of the card acceptor where the transaction occurred. See Appendix A. Positions: 1-25 Card acceptor name 26-38 City name 39-40 Alpha country code Used for miscellaneous information (multiple uses and field formats). See Appendix A. ISO defined code representing the currency of this transaction. A field to describe the location of the card acceptor within the country. See Appendix A for values. Provides additional information about the point of service. See Appendix A for details. Identifies the point-of-service terminal. See Appendix A for values. Identifies the terminal s capability to electronically read account numbers and expiration dates from cards. See Appendix A for values. Contains the cash back amount, if any. If the transaction does not include cash back, this field is not sent. Used for identifying the acquirer s network ID, as well as various reason codes. See Appendix A. LLVAR NP11 Req Fixed AN12 Req Fixed ANS8 Req Fixed Fixed ANS 15 ANS 40 Req Req LLVAR Var. Cond by use Fixed NP3 Req LLVAR ANS 14 Cond BBVAR NP6 Req Fixed NP1 Req Fixed NP1 Req BBVAR NP12 Cond LLVAR Var. by use 063.0 Bit Map Indicates presence of subfields. Fixed B3 Req 063.1 Network ID Fixed NP4 Req A code that specifies the network to be used for authorization of the message. See Appendix A for values. Req Version 4.02 Page 105 Last modified August 12, 2009

POS Check Request Message (Continued) Bit Data Element Number Name 063.3 Message Reason 063.6 Chargeback Reduction / BASE II Flags 100 Receiving Institution ID 125 Supporting Information Description Format Attr Presence Only sent in a submission or resubmission transaction. See Appendix A. Contains indicators used in the effort to reduce chargebacks. See Appendix A. A message routing field that contains a code that identifies the institution that should receive the request. See Appendix A for values. A multi-use field. In this case, contains the raw MICR information from the customer s check. See Appendix A. Fixed NP4 Cond Fixed ANS7 Req LLVAR NP11 Req LLVAR Var. by use Req Version 4.02 Page 106 Last modified August 12, 2009

3.22 POS Check Response Message 3.22 1 POS Check Response This message is used to send a POS check response. The following chart describes: Bit Numbers and Names of all possible data elements for this message If constant, the value to be placed in the field A description of how each data element is used The format and attributes of each data element Required, Optional, Conditional or Not Applicable status of each data element Bit Data Element Description Format Attr Presence Number Name Message Type Value to represent the type of message. Fixed NP4 Req Value: 0210. See Appendix A. Primary Bit Represents the presence of secondary bit Fixed B8 Req Map map and data elements in bits 2 through 64. 001 Secondary Bit Represents the presence of tertiary bit map Fixed B8 Cond Map and data elements in bits 66 through 128. 065 Tertiary Bit Represents the presence of data elements in Fixed B8 Cond Map bits 130 through 192. 003 Processing Defines the type of transaction. See Fixed NP6 Req Appendix A. 004 Amount 1 Transaction Amount. Copied from request Fixed NP12 Req message. 007 Transmission Date and Time Date and Time transaction is sent through the networkexpressed in GMT Fixed NP10 Req 011 System Trace Audit Number 019 Acquiring Institution Country 025 POS Condition 032 Acquiring Institution ID MMDDhhmmss. A number assigned by the message initiator that identifies a cardholder transaction. Copied from request message. Identifies the country of the location where the transaction occurred. Copied from request message. Describes the condition under which the transaction takes place at the point of service. Copied from request message. See Appendix A. Identifies the financial institution acting as the acquirer of this transaction. Value is constant for all transaction requests and responses. Copied from request message. Fixed NP6 Req Fixed NP3 Req Fixed NP2 Req LLVAR NP11 Req 037 Retrieval Reference Number A number used with other data elements as a key to identify and track all messages related to a given customer transaction or series of system messages. The format for this field is YDDDHHNNNNNN, where YDDD is the date in Julian format, HH is the hour and N-N is a 6 digit transaction number. Copied from request message. Fixed AN12 Req Version 4.02 Page 107 Last modified August 12, 2009

POS Check Response Message (Continued) Bit Data Element Number Name 038 Auth ID Response 039 Response 041 Card Acceptor Terminal ID 042 Card Acceptor ID 044 Additional Response Data 044.1 Response Source / Reason 044.12 Check Settlement Description Format Attr Presence The authorization code provided by the issuer when a transaction is approved. Will only be present for approved transactions. A code that defines the disposition of the transaction. See Appendix A for values. Unique terminal/device ID. Merchant-defined value. Merchant ID. Assigned by Bank of America Merchant Services. See Appendix A. Miscellaneous data needed in the response. See Appendix A. Identifies entity responding to request. See Appendix A. Provided by VISA to indicate the settlement disposition of the transaction. Not present if the transaction will not be settled. See Appendix A. Used for miscellaneous information (multiple 048 Additional Data Private uses and field formats). See Appendix A. 049 Transaction ISO defined code representing the currency Currency of this transaction. Copied from request message. 062 Payment Contains authorizations characteristics to the Service Fields back-end authorizer. See Appendix A. 062.0 Bit Map Indicates presence of subfields. Not used for card verification. 062.2 Transaction Contains an identifier unique for each Identifier authorization and financial request. 063 Private-use Used for identifying the acquirer s network ID, Field as well as various reason codes. See Fixed AN6 Cond Fixed AN2 Req Fixed ANS8 Req Fixed ANS Req 15 LLVAR AN25 Cond Fixed AN1 Cond Fixed AN1 Cond LLVAR Var. Cond by use Fixed NP3 Req LLVAR B8 + Cond AN59 Fixed B8 Req Fixed NP15 Req LLVAR Var. Req by use Appendix A. 063.0 Bit Map Indicates presence of subfields. Fixed B3 Req Fixed NP4 Req 063.1 Network ID 100 Receiving Institution ID 125 Supporting Information A code that specifies the network to be used for authorization of the message. See Appendix A for values. A message routing field that contains a code that identifies the institution that should receive the request. Copied from request. See Appendix A for values. A multi-use field. In this case, contains the MICR information from the customer s check. If the transaction is approved or is declined by the back end interchange, the MICR data will be parsed. If it is declined by Bank of America Merchant Services prior to routing to the back end interchange, the MICR data will be in raw format. See Appendix A. LLVAR NP11 Cond LLVAR Var. by use Cond Version 4.02 Page 108 Last modified August 12, 2009

3.23 POS Check Reversal Request Message 3.23.1 POS Check Reversal Request This message is used to send a Reversal request from the POS or Merchant Host to Bank of America Merchant Services MultiLink for a POS check transaction. Most of the data from the original request will be required in this reversal request message. The following chart describes: Bit Numbers and Names of all possible data elements for this message If constant, the value to be placed in the field A description of how each data element is used The format and attributes of each data element Required, Optional, Conditional or Not Applicable status of each data element Bit Data Element Description Format Attr Presence Number Name Message Type Value to represent the type of message. Fixed NP4 Req Value: 0400. See Appendix A. Primary Bit Represents the presence of secondary bit Fixed B8 Req Map map and data elements in bits 2 through 64. 001 Secondary Bit Represents the presence of tertiary bit map Fixed B8 Cond Map and data elements in bits 66 through 128. 065 Tertiary Bit Represents the presence of data elements in Fixed B8 Cond Map bits 130 through 192. 003 Processing Defines the type of transaction. See Fixed NP6 Req Appendix A. 004 Amount 1 Transaction amount. From original request. Fixed NP12 Req 007 Transmission Date and Time Date and Time transaction is sent through the network assigned by the originator. Fixed NP10 Req 011 System Trace Audit Number Expressed in GMT MMDDhhmmss. A number assigned by the message initiator that identifies a cardholder transaction. From original request. 012 Local Time Time of the transaction, in merchant s local time. This value stays constant throughout the life of the transaction. This field must be sent in the settlement file. Expressed as hhmmss. From original request. 013 Local Date Date of the transaction, in merchant s local date. This value stays constant throughout the life of the transaction. This field must be sent in the settlement file. Expressed as MMDD. From original request. 018 Merchant Type 019 Acquiring Institution Country 022 POS Entry Mode Merchant Category (MCC). From original request. Identifies the country of the location where the transaction occurred. From original request. Defines the method of data entry of the account number and whether a PIN was entered on this transaction. From original request. Fixed NP6 Req Fixed NP6 Req Fixed NP4 Req Fixed NP4 Req Fixed NP3 Req Fixed NP4 Req Version 4.02 Page 109 Last modified August 12, 2009

POS Check Reversal Request Message (Continued) Bit Data Element Number Name 025 POS Condition 032 Acquiring Institution ID 037 Retrieval Reference Number 038 Auth ID Response 041 Card Acceptor Terminal ID 042 Card Acceptor ID 043 Card Acceptor Name / Location 048 Additional Data Private 049 Transaction Currency 059 National POS Geographic Data 060 Additional POS Info 060.1 Terminal Type 060.2 Terminal Entry Capability Description Format Attr Presence Describes the condition under which the transaction takes place at the point of service. Value = 52. See Appendix A. From original request. Identifies the financial institution acting as the acquirer of this transaction. Value is constant for all transaction requests and responses. From original request. A number used with other data elements as a key to identify and track all messages related to a given customer transaction or series of system messages. The format for this field is YDDDHHNNNNNN, where YDDD is the date in Julian format, HH is the hour and N-N is a 6 digit transaction number. From original request. The authorization code provided by the issuer when a transaction is approved. (Only an approved transaction can be reversed). Unique terminal/device ID. Merchant-defined value. Merchant ID. Assigned by Bank of America Merchant Services. See Appendix A. Name and location of the card acceptor where the transaction occurred. See Appendix A. Positions: 1-25 Card acceptor name 26-38 City name 39-40 Alpha country code Used for miscellaneous information (multiple uses and field formats). See Appendix A. ISO defined code representing the currency of this transaction. A field to describe the location of the card acceptor within the country. See Appendix A for values. Provides additional information about the point of service. See Appendix A for details. Identifies the point-of-service terminal. From original request. See Appendix A for values. Identifies the terminal s capability to electronically read account numbers and expiration dates from cards. From original request. See Appendix A for values. Fixed NP2 Req LLVAR NP11 Req Fixed AN12 Req Fixed AN6 Opt Fixed ANS8 Req Fixed Fixed ANS 15 ANS 40 Req Req LLVAR Var. Cond by use Fixed NP3 Req LLVAR ANS 14 Cond BBVAR NP6 Req Fixed NP1 Req Fixed NP1 Req Version 4.02 Page 110 Last modified August 12, 2009

POS Check Reversal Request Message (Continued) Bit Data Element Description Format Attr Presence Number Name 061.1 Other Contains the cash back amount, if any. If the BBVAR NP12 Cond Transaction Amount transaction does not include cash back, this field is not sent. 062 Payment Contains authorizations characteristics to the LLVAR B8 + Opt Service Fields back-end authorizer. See Appendix A. AN59 062.0 Bit Map Indicates presence of subfields Fixed B8 Req 062.2 Transaction Contains an identifier unique for each original Fixed NP15 Opt Identifier transaction. 063 Private-use Used for identifying the acquirer s network ID, LLVAR Var. Req Field as well as various reason codes. See Appendix A. by use 063.0 Bit Map Indicates presence of subfields. Fixed B3 Req 063.1 Network ID A code that specifies the network to be used Fixed NP4 Req for authorization of the message. See Appendix A for values. 063.3 Message Only sent in a submission or resubmission Fixed NP4 Req Reason 063.6 Chargeback Reduction / BASE II Flags 090 Original Data Elements 100 Receiving Institution ID 125 Supporting Information transaction. See Appendix A. Contains indicators used in the effort to reduce chargebacks. See Appendix A. Information for tracking the current message back to prior messages for the same cardholder transaction. See Appendix A for detailed field layout. A message routing field that contains a code that identifies the institution that should receive the request. Copied from request. See Appendix A for values. A multi-use field. In this case, contains the raw MICR information from the customer s check. See Appendix A. Fixed ANS7 Req Fixed NP42 Req LLVAR NP11 Req LLVAR Var. by use Req Version 4.02 Page 111 Last modified August 12, 2009

3.24 POS Check Reversal Response Message 3.24.1 POS Check Reversal Response This message is used to send a Reversal response from Bank of America Merchant Services MultiLink to the POS or Merchant Host for a POS check transaction. Much of the data from the original request will be returned in this reversal response message. The following chart describes: Bit Numbers and Names of all possible data elements for this message If constant, the value to be placed in the field A description of how each data element is used The format and attributes of each data element Required, Optional, Conditional or Not Applicable status of each data element Bit Data Element Description Format Attr Presence Number Name Message Type Value to represent the type of message. Fixed NP4 Req Value: 0410. See Appendix A. Primary Bit Represents the presence of secondary bit Fixed B8 Req Map map and data elements in bits 2 through 64. 001 Secondary Bit Represents the presence of tertiary bit map Fixed B8 Cond Map and data elements in bits 66 through 128. 065 Tertiary Bit Represents the presence of data elements in Fixed B8 Cond Map bits 130 through 192. 003 Processing Defines the type of transaction. Copied from Fixed NP6 Req request message. See Appendix A. 004 Amount 1 Transaction amount. Copied from request Fixed NP12 Req message. 007 Transmission Date and Time Date and Time transaction is sent through the network assigned by the originator. Fixed NP10 Req 011 System Trace Audit Number 019 Acquiring Institution Country 025 POS Condition 032 Acquiring Institution ID Expressed in GMT MMDDhhmmss. A number assigned by the message initiator that identifies a cardholder transaction. Copied from request message. Identifies the country of the location where the transaction occurred. From original request. Describes the condition under which the transaction takes place at the point of service. Value = 52. See Appendix A. From original request. Identifies the financial institution acting as the acquirer of this transaction. Value is constant for all transaction requests and responses. From original request. Fixed NP6 Req Fixed NP3 Req Fixed NP2 Req LLVAR NP11 Req Version 4.02 Page 112 Last modified August 12, 2009

POS Check Reversal Response Message (Continued) Bit Data Element Number Name 037 Retrieval Reference Number Description Format Attr Presence A number used with other data elements as a key to identify and track all messages related to a given customer transaction or series of system messages. The format for this field is YDDDHHNNNNNN, where YDDD is the date in Julian format, HH is the hour and N-N is a 6 digit transaction number. From original request. A code that defines the disposition of the transaction. See Appendix A for values. Unique terminal/device ID. Merchant-defined value. Merchant ID. Assigned by Bank of America Merchant Services. See Appendix A. Used for miscellaneous information (multiple uses and field formats). See Appendix A. Contains authorizations characteristics to the back-end authorizer. See Appendix A. Fixed AN12 Req 039 Response Fixed AN2 Req 041 Card Acceptor Fixed ANS8 Req Terminal ID 042 Card Acceptor Fixed ANS Req ID 15 048 Additional LLVAR Var. Cond Data Private by use 062 Payment LLVAR B8 + Opt Service Fields AN59 062.0 Bit Map Indicates presence of subfields Fixed B8 Req 062.2 Transaction Contains an identifier unique for each original Fixed NP15 Opt Identifier transaction. 063 Private-use Used for identifying the acquirer s network ID, LLVAR Var. Req Field as well as various reason codes. See by use Appendix A. 063.0 Bit Map Indicates presence of subfields. Fixed B3 Req 063.1 Network ID A code that specifies the network to be used Fixed NP4 Req for authorization of the message. See 090 Original Data Elements 100 Receiving Institution ID 125 Supporting Information Appendix A for values. Information for tracking the current message back to prior messages for the same cardholder transaction. See Appendix A for detailed field layout. A message routing field that contains a code that identifies the institution that should receive the request. Copied from request. See Appendix A for values. A multi-use field. In this case, contains the raw MICR information from the customer s check, echoed from the reversal request. See Appendix A. Fixed NP42 Req LLVAR NP11 Cond LLVAR Var. by use Cond Version 4.02 Page 113 Last modified August 12, 2009

3.25 Real Time Clearing Request Message 3.25.1 Real Time Clearing Purchase 3.25.2 Real Time Clearing Merchandise Return 3.25.3 Real Time Clearing Balance Inquiry This message is used to send a request message from the POS to Bank of America Merchant Services MultiLink for a Real Time Clearing transaction. The chart below describes: Bit Numbers and Names of all possible data elements for this message If constant, the value to be placed in the field A description of how each data element is used The format and attributes of each data element Required, Optional, Conditional or Not Applicable status of each data element Bit Number Data Element Name Message Type Description Format Attr Presence Value to represent the type of message Value: 0200. See Appendix A. Fixed NP4 Req Represents the presence of secondary bit Fixed B8 Req map and data elements in bits 2 through 64. Represents the presence of tertiary bit map Fixed B8 Cond and data elements in bits 66 through 128. Represents the presence of data elements in Fixed B8 Cond bits 130 through 192. Contains the cardholder account number. LLVAR NP19 Req Primary Bit Map 001 Secondary Bit Map 065 Tertiary Bit Map 002 Primary Account Number 003 Processing Defines the type of transaction. See Appendix A. 004 Amount 1 Transaction Amount. Assumes a 2 position decimal, right-justified, zero filled. This field contains the total amount including the purchase amount and cash back if indicated. Transactions settled through Bank of America Merchant Services s settlement system are limited to 7 characters ($99,999.99). 007 Transmission Date and Time Date and Time transaction is sent through the network assigned by the originator. Expressed in GMT MMDDhhmmss. 011 System Trace Audit Number A number assigned by the message initiator that identifies a cardholder transaction. 012 Local Time Time of the transaction, in merchant s local time. This value stays constant throughout the life of the transaction. This field must be sent in the settlement file. Expressed as hhmmss. Fixed NP6 Req Fixed NP12 Req Fixed NP10 Req Fixed NP6 Req Fixed NP6 Req Version 4.02 Page 114 Last modified August 12, 2009

Real Time Clearing Request Message (Continued) Bit Data Element Description Format Attr Presence Number Name 013 Local Date Date of the transaction, in merchant s local Fixed NP4 Req date. This value stays constant throughout the life of the transaction. This field must be sent in the settlement file. Expressed as MMDD. 014 Expiration Contains the expiration date on the card. If Fixed NP4 Cond Date the card does not have an expiration date, do not send this bit. Expressed as YYMM. 018 Merchant Merchant Category (MCC). Bank of Fixed NP4 Req Type 019 Acquiring Institution Country 022 POS Entry Mode 025 POS Condition 032 Acquiring Institution ID 033 Forwarding Institution ID America Merchant Services-assigned value. Identifies the country of the location where the transaction occurred. See Appendix A for values. Defines the method of data entry of the account number and whether a PIN was entered on this transaction. See Appendix A for values. Describes the condition under which the transaction takes place at the point of service. See Appendix A for values. Identifies the financial institution acting as the acquirer of this transaction. Value is constant for all transaction requests and responses. This is an Bank of America Merchant Services -assigned identification number. Value 45592900000. Identifies the processor that forwards the request to Bank of America Merchant Services, if that processor is different from the institution indicated in field 032. This is an Bank of America Merchant Servicesassigned identification number. 035 Track 2 Data Unaltered contents of the data read off Track 2 of the mag stripe, excluding the beginning and ending sentinels and LRC characters. This field is only present when Track 2 has been read or assembled via a contactless means at the terminal. 037 Retrieval Reference Number 041 Card Acceptor Term ID 042 Card Acceptor ID A number used with other data elements as a key to identify and track all messages related to a given customer transaction or series of system messages. The format for this field is YDDDHHNNNNNN, where YDDD is the date in Julian format, HH is the hour and N-N is a 6 digit transaction number. Unique terminal/device ID. Merchant-defined value. Merchant ID. Assigned by Bank of America Merchant Services. See Appendix A. Fixed NP3 Req Fixed NP4 Req Fixed NP2 Req LLVAR NP11 Req LLVAR NP11 Cond LLVAR NP37 Cond Fixed AN12 Req Fixed ANS8 Req Fixed ANS 15 Req Version 4.02 Page 115 Last modified August 12, 2009

Real Time Clearing Request Message (Continued) Bit Data Element Number Name 043 Card Acceptor Name / Location 049 Transaction Currency 059 National POS Geographic Data 060 Additional POS Info 060.1 Terminal Type 060.2 Terminal Entry Capability 060.3 Chip Condition 060.4 Special Condition Indicator Existing Debt 060.5 Merchant Group Indicator 060.6 Chip Transaction Indicator 060.7 Chip Authentication Reliability Indicator 060.8 Mail Order / Telephone Order / Electronic Commerce Indicator 060.9 Cardholder ID Method Description Format Attr Presence Name and location of the card acceptor where the transaction occurred. See Appendix A. Positions: 1-25 Card acceptor name 26-38 City name 39-40 Alpha country code ISO defined code representing the currency of this transaction. A field to describe the location of the card acceptor within the country. See Appendix A for values. A group of subfields that provide additional information about the point of service. See Appendix A for values. Identifies the point-of-service terminal. See Appendix A for values. Identifies the terminal s capability to electronically read account numbers and expiration dates from cards. See Appendix A for values. Provides information about VSDC cards when read at VSDC terminals. See Appendix A for values. Indicates whether a payment is being made on an existing debt. See Appendix A for values. Identifies the general category of the card acceptor and transaction. See Appendix A for values. Set when message from the terminal is for a VSDC transaction. See Appendix A for values. Indicates the reliability of a transaction in the VSDC environment. See Appendix A for values. Identifies the type of mail or telephone order or the level of security used in en e- commerce transaction over an open network. See Appendix A for values. Identifies the method of transaction authentication. See Appendix A for values. Fixed ANS 40 Req Fixed NP3 Req LLVAR BBVAR ANS 14 Var. by use Cond Req Fixed NP1 Req Fixed NP1 Req Fixed NP1 Cond Fixed NP1 Cond Fixed NP2 Cond Fixed NP1 Cond Fixed NP1 Cond Fixed NP2 Cond Fixed NP1 Cond Version 4.02 Page 116 Last modified August 12, 2009

Real Time Clearing Request Message (Continued) Bit Data Element Description Format Attr Presence Number Name 060.10 Partial Indicates whether the device supports partial Fixed NP1 Cond Authorization / Balance Indicator authorizations and whether the merchant desires balances to be returned. See Appendix A for values. 062 Payment Contains authorizations characteristics to the LLVAR B8 + Req Service Fields back-end authorizer. See Appendix A. AN59 062.0 Bit Map Indicates presence of subfields. Not used for Fixed B8 Req card verification. 062.1 Authorization Characteristic Indicator Used by the acquirer processor to request Custom Payment Services (CPS) and MasterCard recurring payments. See Fixed AN1 Req 063 Private-use Field Appendix A. Used for identifying the acquirer s network ID, as well as various reason codes. See Appendix A. LLVAR Var. by use 063.0 Bit Map Indicates presence of subfields. Fixed B3 Req 063.1 Network ID A code that specifies the network to be used Fixed NP4 Req for authorization of the message. See 063.11 Reimbursement Attribute 114 Transport Data 123 Address Verification Data 170 Private Use Card Acceptor Street Address 171 Private Use General Appendix A for values. A value based on the transaction qualification criteria. See Appendix A for values. A value assigned by the merchant. It is returned in the response message. See Appendix A. Contains selected portions of the cardholder s address for verification. See Appendix A. Contains the street address of the card acceptor the location where the transaction occurred. See Appendix A. Fields unique to Bank of America Merchant Services processing. See descriptions of subfields below and in Appendix A. Req Fixed AN1 Req for Merch. LLVAR LLVAR Fixed TLV (**) 255 ANS 29 ANS 25 LLLVAR B8 + var. by use Return only Opt Cond 171.0 Bit Map Indicates presence of subfields. Fixed B8 Req 171.8 Transaction Used to indicate various transaction Fixed AN1 Cond Subtype situations. See Appendix A. 173 Settlement Data Data needed to settle the transaction. See Appendix A. BBB VAR Cond TLV (21) 999 Req Req Version 4.02 Page 117 Last modified August 12, 2009

3.26 Real Time Clearing Response Message 3.26.1 Real Time Clearing Purchase 3.26.2 Real Time Clearing Merchandise Return 3.26.3 Real Time Clearing Balance Inquiry This message is used to send a response message from Bank of America Merchant Services MultiLink to the POS for a Real Time Clearing transaction. The chart below describes: Bit Numbers and Names of all possible data elements for this message If constant, the value to be placed in the field A description of how each data element is used The format and attributes of each data element Required, Optional, Conditional or Not Applicable status of each data element Bit Number Data Element Name Message Type Primary Bit Map 001 Secondary Bit Map 065 Tertiary Bit Map 002 Primary Account Number 003 Processing Description Format Attr Presence Value to represent the type of message Value: 0210. See Appendix A. Represents the presence of secondary bit map and data elements in bits 2 through 64. Represents the presence of tertiary bit map and data elements in bits 66 through 128. Represents the presence of data elements 130 through 192. Contains the cardholder account number. Copied from the request message. Defines the type of transaction. Copied from the request message. See Appendix A for values. 004 Amount 1 Transaction Amount. Copied from request message. Exception: If the transaction is approved for other than the requested amount, this field will contain the approved amount and bit 54 will contain the original amount. Must be sent in the settlement file. 007 Transmission Date and Time 011 System Trace Audit Number 019 Acquiring Institution Country 025 POS Condition Date and Time transaction is sent through the network. Expressed in GMT MMDDhhmmss. A number assigned by the message initiator that identifies a cardholder transaction. Copied from request message. Identifies the country of the location where the transaction occurred. Copied from request message. Describes the condition under which the transaction takes place at the point of service. Copied from request message. See Appendix A. Fixed NP4 Req Fixed B8 Req Fixed B8 Cond Fixed B8 Cond LLVAR NP19 Req Fixed NP6 Req Fixed NP12 Req Fixed NP10 Req Fixed NP6 Req Fixed NP3 Req Fixed NP2 Req Version 4.02 Page 118 Last modified August 12, 2009

Real Time Clearing Response Message (Continued) Bit Data Element Number Name 032 Acquiring Institution ID 037 Retrieval Reference Number 038 Auth ID Response Description Format Attr Presence Identifies the financial institution acting as the acquirer of this transaction. Value is constant for all transaction requests and responses. Copied from request message. A number used with other data elements as a key to identify and track all messages related to a given customer transaction or series of system messages. The format for this field is YDDDHHNNNNNN, where YDDD is the date in Julian format, HH is the hour and N-N is a 6 digit transaction number. Copied from request message. The authorization code provided by the issuer when a transaction is approved. Will only be present for approved transactions. A code that defines the disposition of the transaction. See Appendix A for values. Unique terminal/device ID. Merchant-defined value. Merchant ID. Assigned by Bank of America Merchant Services. See Appendix A. Miscellaneous data needed in the response. See Appendix A. 039 Response 041 Card Acceptor Term ID 042 Card Acceptor ID 044 Additional Response Data 044.1 Response Identifies entity responding to request. See Source / Appendix A. Reason 044.2 Address Describes the address verification result. Verification See Appendix A for values. Result 044.5 CVV Results 049 Transaction ISO defined code representing the currency Currency of this transaction. Copied from request message. 054 Add l Amount For financial transactions in which the merchant has indicated support for partial approvals, contains the original requested amount. If the merchant has indicated the desire to receive balances on financial transactions, may contain one or more balances. See Appendix A for a full description. LLVAR NP11 Req Fixed AN12 Req Fixed AN6 Cond Fixed AN2 Req Fixed ANS8 Req Fixed ANS Req 15 LLVAR AN25 Cond Fixed AN1 Cond Fixed AN1 Cond See Appendix A for values. Fixed AN1 Cond Fixed NP3 Req LLVAR 062 Payment Contains authorizations characteristics to the LLVAR B8 + Req Service Fields back-end authorizer. See Appendix A. AN59 062.0 Bit Map Indicates presence of subfields. Fixed B8 Req ANS 120 Cond 062.1 Authorization Characteristic Indicator Indicates level of qualification for Custom Payment Services (CPS). See Appendix A for values. Fixed AN1 Req Version 4.02 Page 119 Last modified August 12, 2009

Real Time Clearing Response Message (Continued) Bit Data Element Description Format Attr Presence Number Name 062.2 Transaction Issuer-generated identifier unique for each Fixed NP15 Cond Identifier original transaction. 062.23 Card Results Indicates the card program that the card Fixed AN2 Cond used in the transaction is signed up for. See Appendix A. 063 Private-use Used for identifying the acquirer s network ID, LLVAR Var. Req Field as well as various reason codes. See Appendix A. by use 063.0 Bit Map Indicates presence of subfields. Fixed B3 Req 063.1 Network ID 063.19 Fee Program Indicator 063.21 Charge Indicator A code that specifies the network used for authorization of the message. See Appendix A for values. A value that indicates the specific interchange fee program that was applied to the transaction. See Appendix A. Identifies the type of international Service Assessment Fee (ISA) that will be assessed to the transaction. Fixed NP4 Req Fixed AN3 Req Fixed ANS1 Cond 102 Account ID 1 A number that identifies an account or LLVAR ANS Opt customer relationship. 28 171 Private Use Fields unique to Bank of America Merchant LLLVAR B8 + Cond General Services processing. See descriptions of subfields below and in Appendix A. var. by use 171.0 Bit Map Indicates presence of subfields. Fixed B8 Req 171.8 Transaction Subtype Used to indicate various transaction situations. See Appendix A. 173 Settlement Data Data needed to settle the transaction. See Appendix A. 177 Supplemental Data Additional data needed on this particular transaction. See Appendix A. Fixed AN1 Cond BBB VAR BBB VAR TLV (21) 999 TLV (21) 999 Cond Cond Version 4.02 Page 120 Last modified August 12, 2009

3.27 Real Time Clearing Preauthorized Purchase Request Message 3.27.1 Real Time Clearing Preauthorized Purchase This message is used to send a request message from the POS to Bank of America Merchant Services MultiLink for a Real Time Clearing Preauthorized Purchase transaction. The chart below describes: Bit Numbers and Names of all possible data elements for this message If constant, the value to be placed in the field A description of how each data element is used The format and attributes of each data element Required, Optional, Conditional or Not Applicable status of each data element Bit Number Data Element Name Message Type Description Format Attr Presence Value to represent the type of message Value: 0100. See Appendix A. Fixed NP4 Req Represents the presence of secondary bit Fixed B8 Req map and data elements in bits 2 through 64. Represents the presence of tertiary bit map Fixed B8 Cond and data elements in bits 66 through 128. Represents the presence of data elements in Fixed B8 Cond bits 130 through 192. Contains the cardholder account number. LLVAR NP19 Req Primary Bit Map 001 Secondary Bit Map 065 Tertiary Bit Map 002 Primary Account Number 003 Processing Defines the type of transaction. See Appendix A. 004 Amount 1 Transaction Amount. Assumes a 2 position decimal, right-justified, zero filled. This field contains the total amount including the purchase amount and cash back if indicated. Transactions settled through Bank of America Merchant Services s settlement system are limited to 7 characters ($99,999.99). 007 Transmission Date and Time Date and Time transaction is sent through the network assigned by the originator. Expressed in GMT MMDDhhmmss. 011 System Trace Audit Number A number assigned by the message initiator that identifies a cardholder transaction. 012 Local Time Time of the transaction, in merchant s local time. This value stays constant throughout the life of the transaction. This field must be sent in the settlement file. Expressed as hhmmss. 013 Local Date Date of the transaction, in merchant s local date. This value stays constant throughout the life of the transaction. This field must be sent in the settlement file. Expressed as MMDD. Fixed NP6 Req Fixed NP12 Req Fixed NP10 Req Fixed NP6 Req Fixed NP6 Req Fixed NP4 Req Version 4.02 Page 121 Last modified August 12, 2009

Real Time Clearing Preauthorized Purchase Request Message (Continued) Bit Data Element Number Name 014 Expiration Date 018 Merchant Type 019 Acquiring Institution Country 022 POS Entry Mode 025 POS Condition 032 Acquiring Institution ID Description Format Attr Presence Contains the expiration date on the card. If the card does not have an expiration date, do not send this bit. Expressed as YYMM. Merchant Category (MCC). Bank of America Merchant Services-assigned value. Identifies the country of the location where the transaction occurred. See Appendix A for values. Defines the method of data entry of the account number and whether a PIN was entered on this transaction. See Appendix A for values. Describes the condition under which the transaction takes place at the point of service. See Appendix A. Identifies the financial institution acting as the acquirer of this transaction. Value is constant for all transaction requests and responses. Value 45592900000. 035 Track 2 Data Unaltered contents of the data read off Track 2 of the magnetic stripe, excluding the beginning and ending sentinels and LRC characters. 037 Retrieval Reference Number 041 Card Acceptor Term ID 042 Card Acceptor ID 043 Card Acceptor Name / Location 049 Transaction Currency 059 National POS Geographic Data 060 Additional POS Info A number used with other data elements as a key to identify and track all messages related to a given customer transaction or series of system messages. The format for this field is YDDDHHNNNNNN, where YDDD is the date in Julian format, HH is the hour and N-N is a 6 digit transaction number. Unique terminal/device ID. Merchant-defined value. Merchant ID. Assigned by Bank of America Merchant Services. See Appendix A. Name and location of the card acceptor where the transaction occurred. See Appendix A. Positions: 1-25 Card Acceptor name 26-38 City Name 39-40 Alpha Country code ISO defined code representing the currency of this transaction. A field to describe the location of the card acceptor within the country. See Appendix A for values. A group of sub fields that provide additional information about the point of service. See Appendix A for values Fixed NP4 Cond Fixed NP4 Req Fixed NP3 Req Fixed NP4 Req Fixed NP2 Req LLVAR NP11 Req LLVAR NP37 Req Fixed AN12 Req Fixed ANS8 Req Fixed Fixed ANS 15 ANS 40 Req Req Fixed NP3 Req LLVAR BBVAR ANS 14 Var. by use Cond Req Version 4.02 Page 122 Last modified August 12, 2009

Real Time Clearing Preauthorized Purchase Request Message (Continued) Bit Data Element Number Name 060.1 Terminal Type 060.2 Terminal Entry Capability 060.3 Chip Condition 060.4 Special Condition Indicator Existing Debt 060.5 Merchant Group Indicator 060.6 Chip Transaction Indicator 060.7 Chip Authentication Reliability Indicator 060.8 Mail Order / Telephone Order / Electronic Commerce Indicator 060.9 Cardholder ID Description Format Attr Presence Identifies the point-of-service terminal. See Appendix A for values Identifies the terminal s capability to electronically read account numbers and expiration dates from cards. See Appendix A for values. Provides information about VSDC cards when read at VSDC terminals. See Appendix A for values. Indicates whether a payment is being made on an existing debt. See Appendix A for values. Identifies the general category of the card acceptor and transaction. See Appendix A for values. Set when message from the terminal is for a VSDC transaction. See Appendix A for values. Indicates the reliability of a transaction in the VSDC environment. See Appendix A for values. Identifies the type of mail or telephone order or the level of security used in en e- commerce transaction over an open network. See Appendix A for values. Identifies the method of transaction Method authentication. See Appendix A for values. 060.10 Partial Indicates whether the device supports partial Authorization / authorizations and whether the merchant Balance desires balances to be returned on debit Indicator financial transactions. See Appendix A for values. 062 Payment Contains authorizations characteristics to the Service Fields back-end authorizer. See Appendix A. 062.0 Bit Map Indicates presence of subfields. Not used for card verification. 062.1 Authorization Used by the acquirer processor to request Characteristic Custom Payment Services (CPS). See Indicator Appendix A. 063 Private-use Field Used for identifying the acquirer s network ID, as well as various reason codes. See Appendix A. Fixed NP1 Req Fixed NP1 Req Fixed NP1 Cond Fixed NP1 Cond Fixed NP2 Cond Fixed NP1 Cond Fixed NP1 Cond Fixed NP2 Cond Fixed NP1 Cond Fixed NP1 Cond LLVAR B8 + Req AN59 Fixed B8 Req Fixed AN1 Req LLVAR Var. by use 063.0 Bit Map Indicates presence of sub fields. Fixed B3 Req 063.1 Network ID Fixed NP4 Req A code that specifies the network used for authorization of the message. Must be 0000 in a request. See Appendix A. Req Version 4.02 Page 123 Last modified August 12, 2009

Real Time Clearing Preauthorized Purchase Request Message (Continued) Bit Data Element Number Name 063.2 Preauth Time Limit 114 Transport Data 123 Address Verification Data 170 Private Use Card Acceptor Street Address 171 Private Use General Description Format Attr Presence The time (in hours) the issuer agrees to hold funds for an acquirer. For merchant use. This field will be echoed back in the response to this transaction. See Appendix A. Contains selected portions of the cardholder s address for verification. See Appendix A. Contains the street address of the card acceptor the location where the transaction occurred. See Appendix A. Fields unique to Bank of America Merchant Services processing. See descriptions of subfields below and in Appendix A. Fixed NP4 Req LLVAR LLVAR Fixed TLV (**) 255 ANS 29 ANS 25 LLLVAR B8 + var. by use Opt Cond 171.0 Bit Map Indicates presence of subfields. Fixed B8 Req 171.8 Transaction Used to indicate various transaction Fixed AN1 Cond Subtype situations. See Appendix A. 173 Settlement Data Data needed to settle the transaction. See Appendix A. BBB VAR Cond TLV (21) 999 Req Req Version 4.02 Page 124 Last modified August 12, 2009

3.28 Real Time Clearing Preauthorized Purchase Response Message 3.28.1 Real Time Clearing Preauthorized Purchase This message is used to send a response message from Bank of America Merchant Services MultiLink to the POS for a Real Time Clearing preauthorized Purchase transaction. The chart below describes: Bit Numbers and Names of all possible data elements for this message If constant, the value to be placed in the field A description of how each data element is used The format and attributes of each data element Required, Optional, Conditional or Not Applicable status of each data element Bit Number Data Element Name Message Type Primary Bit Map 001 Secondary Bit Map 065 Tertiary Bit Map 002 Primary Account Number 003 Processing Description Format Attr Presence Value to represent the type of message Value: 0110. See Appendix A. Represents the presence of secondary bit map and data elements in bits 2 through 64. Represents the presence of tertiary bit map and data elements in bits 66 through 128. Represents the presence of data elements 130 through 192. Contains the cardholder account number. Copied from the request message. Defines the type of transaction. Copied from the request message. See Appendix A for values. 004 Amount 1 Transaction Amount. Copied from request message. Exception: If the transaction is approved for less than the requested amount, this field will contain the approved amount and bit 54 will contain the original amount. Must be sent in the settlement file. 007 Transmission Date and Time 011 System Trace Audit Number 019 Acquiring Institution Country 025 POS Condition 032 Acquiring Institution ID Date and Time transaction is sent through the network. Expressed in GMT MMDDhhmmss. A number assigned by the message initiator that identifies a cardholder transaction. Copied from request message. Identifies the country of the location where the transaction occurred. Copied from request message. Describes the condition under which the transaction takes place at the point of service. Copied from request message. See Appendix A. Identifies the financial institution acting as the acquirer of this transaction. Value is constant for all transaction requests and responses. Copied from request message. Fixed NP4 Req Fixed B8 Req Fixed B8 Cond Fixed B8 Cond LLVAR NP19 Req Fixed NP6 Req Fixed NP12 Req Fixed NP10 Req Fixed NP6 Req Fixed NP3 Req Fixed NP2 Req LLVAR NP11 Req Version 4.02 Page 125 Last modified August 12, 2009

Real Time Clearing Preauthorized Purchase Response Message (Continued) Bit Data Element Number Name 037 Retrieval Reference Number 038 Auth ID Response Description Format Attr Presence A number used with other data elements as a key to identify and track all messages related to a given customer transaction or series of system messages. The format for this field is YDDDHHNNNNNN, where YDDD is the date in Julian format, HH is the hour and N-N is a 6 digit transaction number. Copied from request message. The authorization code provided by the issuer when a transaction is approved. Will only be present for approved transactions. A code that defines the disposition of the transaction. See Appendix A for values. Unique terminal/device ID. Merchant-defined value. Merchant ID. Assigned by Bank of America Merchant Services. See Appendix A. Miscellaneous data needed in the response. See Appendix A. 039 Response 041 Card Acceptor Term ID 042 Card Acceptor ID 044 Additional Response Data 044.1 Response Identifies entity responding to request. See Source / Appendix A. Reason 044.2 Address Describes the address verification result. Verification See Appendix A for values. Result 044.5 CVV Results 049 Transaction ISO defined code representing the currency Currency of this transaction. Copied from request message. 054 Add l Amount For financial transactions in which the merchant has indicated support for partial approvals, contains the original requested amount. If the merchant has indicated the desire to receive balances on financial transactions, may contain one or more balances. See Appendix A for a full description. Fixed AN12 Req Fixed AN6 Cond Fixed AN2 Req Fixed ANS8 Req Fixed ANS Req 15 LLVAR AN25 Cond Fixed AN1 Cond Fixed AN1 Cond See Appendix A for values. Fixed AN1 Cond Fixed NP3 Req LLVAR 062 Payment Contains authorizations characteristics to the LLVAR B8 + Req Service Fields back-end authorizer. See Appendix A. AN59 062.0 Bit Map Indicates presence of subfields. Fixed B8 Req ANS 120 Cond 062.1 Authorization Characteristic Indicator 062.2 Transaction Identifier Indicates level of qualification for Custom Payment Services (CPS). See Appendix A for values. Issuer-generated identifier unique for each original transaction. Fixed AN1 Req Fixed NP15 Cond Version 4.02 Page 126 Last modified August 12, 2009

Real Time Clearing Preauthorized Purchase Response Message (Continued) Bit Data Element Number Name 062.3 Validation Description Format Attr Presence A code calculated to ensure that key fields in the 0100 authorization message match their respective fields in the deferred clearing message. 062.23 Card Results Indicates the card program that the card used in the transaction is signed up for. See Appendix A. 063 Private-use Field Used for identifying the acquirer s network ID, as well as various reason codes. See Appendix A. Fixed AN4 Cond Fixed AN2 Cond LLVAR Var. by use 063.0 Bit Map Indicates presence of sub fields. Fixed B3 Req 063.1 Network ID Fixed NP4 Req A code that specifies the network used for authorization of the message. This code must be used in the merchant settlement file. See Appendix A. 063.2 Preauth Time The time (in hours) the issuer agrees to hold Fixed NP4 Req Limit funds for an acquirer. Copied from request. 102 Account ID 1 A number that identifies an account or LLVAR ANS Opt customer relationship. 28 171 Private Use Fields unique to Bank of America Merchant LLLVAR B8 + Cond General Services processing. See descriptions of subfields below and in Appendix A. var. by use 171.0 Bit Map Indicates presence of subfields. Fixed B8 Req 171.8 Transaction Used to indicate various transaction Fixed AN1 Cond Subtype situations. See Appendix A. 177 Supplemental Data Additional data needed on this particular transaction. See Appendix A. BBB VAR Cond TLV (21) 999 Req Version 4.02 Page 127 Last modified August 12, 2009

3.29 Real Time Clearing Preauthorized Purchase Completion Request Message 3.29.1 Real Time Clearing Preauthorized Completion This message is used to send a completion request message from the POS to Bank of America Merchant Services MultiLink for a Real Time Clearing Preauthorized Purchase transaction. The chart below describes: Bit Numbers and Names of all possible data elements for this message If constant, the value to be placed in the field A description of how each data element is used The format and attributes of each data element Required, Optional, Conditional or Not Applicable status of each data element Bit Number Data Element Name Message Type Description Format Attr Presence Value to represent the type of message Value: 0220. See Appendix A. Fixed NP4 Req Represents the presence of secondary bit Fixed B8 Req map and data elements in bits 2 through 64. Represents the presence of tertiary bit map Fixed B8 Cond and data elements in bits 66 through 128. Represents the presence of data elements in Fixed B8 Cond bits 130 through 192. Contains the cardholder account number. LLVAR NP19 Req Primary Bit Map 001 Secondary Bit Map 065 Tertiary Bit Map 002 Primary Account Number 003 Processing Defines the type of transaction. See Appendix A. 004 Amount 1 Completed Amount. Assumes a 2 position decimal, right-justified, zero filled. This field contains the total amount including the purchase amount and cash back if indicated. Transactions settled through Bank of America Merchant Services s settlement system are limited to 7 characters ($99,999.99). 007 Transmission Date and Time 011 System Trace Audit Number Date and Time transaction is sent through the network assigned by the originator. Will not have the same value as bit 007 in preauth request. Expressed in GMT MMDDhhmmss. A number assigned by the message initiator that identifies a cardholder transaction. Copied from preauth request. 012 Local Time Time of the transaction, in merchant s local time. This value stays constant throughout the life of the transaction. This field must be sent in the settlement file. Expressed as hhmmss. Fixed NP6 Req Fixed NP12 Req Fixed NP10 Req Fixed NP6 Req Fixed NP6 Req Version 4.02 Page 128 Last modified August 12, 2009

Real Time Clearing Preauthorized Purchase Completion Request Message (Continued) Bit Data Element Description Format Attr Presence Number Name 013 Local Date Date of the transaction, in merchant s local Fixed NP4 Req date. This value stays constant throughout the life of the transaction. This field must be sent in the settlement file. Expressed as MMDD. 014 Expiration Contains the expiration date on the card. If Fixed NP4 Cond Date the card does not have an expiration date, do not send this bit. Expressed as YYMM. 018 Merchant Merchant Category (MCC). Bank of Fixed NP4 Req Type 019 Acquiring Institution Country 022 POS Entry Mode 025 POS Condition 032 Acquiring Institution ID America Merchant Services-assigned value. Identifies the country of the location where the transaction occurred. See Appendix A for values. Defines the method of data entry of the account number and whether a PIN was entered on this transaction. See Appendix A for values. Must contain a value of 06 to indicate a preauthorization completion. See Appendix A. Identifies the financial institution acting as the acquirer of this transaction. Value is constant for all transaction requests and responses. Value 45592900000. 035 Track 2 Data Unaltered contents of the data read off Track 2 of the magnetic stripe, excluding the beginning and ending sentinels and LRC characters. 037 Retrieval Reference Number 041 Card Acceptor Term ID 042 Card Acceptor ID 043 Card Acceptor Name / Location A number used with other data elements as a key to identify and track all messages related to a given customer transaction or series of system messages. The format for this field is YDDDHHNNNNNN, where YDDD is the date in Julian format, HH is the hour and N-N is a 6 digit transaction number. Copied from preauth request. Unique terminal/device ID. Merchant-defined value. Merchant ID. Assigned by Bank of America Merchant Services. See Appendix A. Name and location of the card acceptor where the transaction occurred. See Appendix A. Positions: 1-25 Card Acceptor name 26-38 City Name 39-40 Alpha Country code Fixed NP3 Req Fixed NP4 Req Fixed NP2 Req LLVAR NP11 Req LLVAR NP37 Opt (see Appendix A for details if not sent) Fixed AN12 Req Fixed ANS8 Req Fixed Fixed ANS 15 ANS 40 Req Req Version 4.02 Page 129 Last modified August 12, 2009

Real Time Clearing Preauthorized Purchase Completion Request Message (Continued) Bit Data Element Number Name 049 Transaction Currency 059 National POS Geographic Data 060 Additional POS Info 060.1 Terminal Type 060.2 Terminal Entry Capability 060.3 Chip Condition 060.4 Special Condition Indicator Existing Debt 060.5 Merchant Group Indicator 060.6 Chip Transaction Indicator 060.7 Chip Authentication Reliability Indicator 060.8 Mail Order / Telephone Order / Electronic Commerce Indicator Description Format Attr Presence ISO defined code representing the currency of this transaction. A field to describe the location of the card acceptor within the country. See Appendix A for values. A group of sub fields that provide additional information about the point of service. See Appendix A for values Identifies the point-of-service terminal. See Appendix A for values Identifies the terminal s capability to electronically read account numbers and expiration dates from cards. See Appendix A for values. Provides information about VSDC cards when read at VSDC terminals. See Appendix A for values. Indicates whether a payment is being made on an existing debt. See Appendix A for values. Identifies the general category of the card acceptor and transaction. See Appendix A for values. Set when message from the terminal is for a VSDC transaction. See Appendix A for values. Indicates the reliability of a transaction in the VSDC environment. See Appendix A for values. Identifies the type of mail or telephone order or the level of security used in en e- commerce transaction over an open network. See Appendix A for values. 060.9 Cardholder ID Method Identifies the method of transaction authentication. See Appendix A for values. 060.10 Partial Indicates whether the device supports partial Authorization / authorizations and whether the merchant Balance desires balances to be returned on debit Indicator financial transactions. See Appendix A for values. 062 Payment Contains authorizations characteristics to the Service Fields back-end authorizer. See Appendix A. 062.0 Bit Map Indicates presence of subfields. Not used for card verification. Fixed NP3 Req LLVAR BBVAR ANS 14 Var. by use Cond Req Fixed NP1 Req Fixed NP1 Req Fixed NP1 Cond Fixed NP1 Cond Fixed NP2 Cond Fixed NP1 Cond Fixed NP1 Cond Fixed NP2 Cond Fixed NP1 Cond Fixed NP1 Cond LLVAR B8 + Req AN59 Fixed B8 Req Version 4.02 Page 130 Last modified August 12, 2009

Real Time Clearing Preauthorized Purchase Completion Request Message (Continued) Bit Data Element Number Name 062.1 Authorization Characteristic Indicator 062.2 Transaction Identifier 063 Private-use Field Description Format Attr Presence Used by the acquirer processor to request Custom Payment Services (CPS). See Appendix A. Issuer-generated identifier unique for each original transaction. Used for identifying the acquirer s network ID, as well as various reason codes. See Appendix A. Fixed AN1 Req Fixed NP15 Cond LLVAR Var. by use 063.0 Bit Map Indicates presence of sub fields. Fixed B3 Req 063.1 Network ID A code that specifies the network used for Fixed NP4 Req authorization of the message. Must be 063.2 Preauth Time Limit 090 Original Data Elements 0000 in a request. See Appendix A. The time (in hours) the issuer agrees to hold funds for an acquirer. Information for tracking the current message back to the original preauthorization. See Appendix A for description. 114 Transport Data For merchant use. This field will be echoed back in the response to this transaction. See Appendix A. 170 Private Use Card Acceptor Street Address 171 Private Use General Contains the street address of the card acceptor the location where the transaction occurred. See Appendix A. Fields unique to Bank of America Merchant Services processing. See descriptions of subfields below and in Appendix A. Req Fixed NP4 Req Fixed NP42 Req LLVAR Fixed TLV (**) 255 ANS 25 LLLVAR B8 + var. by use Opt Req Cond 171.0 Bit Map Indicates presence of subfields. Fixed B8 Req 171.8 Transaction Used to indicate various transaction Fixed AN1 Cond Subtype situations. See Appendix A. 173 Settlement Data Data needed to settle the transaction. See Appendix A. BBB VAR Cond TLV (21) 999 Version 4.02 Page 131 Last modified August 12, 2009

3.30 Real Time Clearing Preauthorized Purchase Completion Response Message 3.30.1 Real Time Clearing Preauthorized Completion This message is used to send a completion response message from Bank of America Merchant Services MultiLink to the POS for a Real Time Clearing Preauthorized Purchase transaction. The chart below describes: Bit Numbers and Names of all possible data elements for this message If constant, the value to be placed in the field A description of how each data element is used The format and attributes of each data element Required, Optional, Conditional or Not Applicable status of each data element Bit Number Data Element Name Message Type Primary Bit Map 001 Secondary Bit Map 065 Tertiary Bit Map 002 Primary Account Number 003 Processing Description Format Attr Presence Value to represent the type of message Value: 0230. See Appendix A. Represents the presence of secondary bit map and data elements in bits 2 through 64. Represents the presence of tertiary bit map and data elements in bits 66 through 128. Represents the presence of data elements 130 through 192. Contains the cardholder account number. Copied from the request message. Defines the type of transaction. Copied from the request message. See Appendix A for values. 004 Amount 1 Transaction Amount. Copied from request message. Exception: If the transaction is approved for less than the requested amount, this field will contain the approved amount and bit 54 will contain the original amount. Must be sent in the settlement file. 007 Transmission Date and Time 011 System Trace Audit Number 019 Acquiring Institution Country 025 POS Condition 032 Acquiring Institution ID Date and Time transaction is sent through the network. Expressed in GMT MMDDhhmmss. A number assigned by the message initiator that identifies a cardholder transaction. Copied from request message. Identifies the country of the location where the transaction occurred. Copied from request message. Describes the condition under which the transaction takes place at the point of service. Copied from request message. See Appendix A. Identifies the financial institution acting as the acquirer of this transaction. Value is constant for all transaction requests and responses. Copied from request message. Fixed NP4 Req Fixed B8 Req Fixed B8 Cond Fixed B8 Cond LLVAR NP19 Req Fixed NP6 Req Fixed NP12 Req Fixed NP10 Req Fixed NP6 Req Fixed NP3 Req Fixed NP2 Req LLVAR NP11 Req Version 4.02 Page 132 Last modified August 12, 2009

Real Time Clearing Preauthorized Purchase Completion Response (Continued) Bit Data Element Number Name 037 Retrieval Reference Number 038 Auth ID Response Description Format Attr Presence A number used with other data elements as a key to identify and track all messages related to a given customer transaction or series of system messages. The format for this field is YDDDHHNNNNNN, where YDDD is the date in Julian format, HH is the hour and N-N is a 6 digit transaction number. Copied from request message. The authorization code provided by the issuer when a transaction is approved. Will only be present for approved transactions. A code that defines the disposition of the transaction. See Appendix A for values. Unique terminal/device ID. Merchant-defined value. Merchant ID. Assigned by Bank of America Fixed AN12 Req Fixed AN6 Cond 039 Response Fixed AN2 Req 041 Card Acceptor Fixed ANS8 Req Term ID 042 Card Acceptor Fixed ANS Req ID Merchant Services. See Appendix A. 15 049 Transaction ISO defined code representing the currency Fixed NP3 Req Currency of this transaction. Copied from request message. 062 Payment Contains authorizations characteristics to the LLVAR B8 + Req Service Fields back-end authorizer. See Appendix A. AN59 062.0 Bit Map Indicates presence of subfields. Fixed B8 Req 062.1 Authorization Characteristic Indicator 062.2 Transaction Identifier 062.3 Validation Indicates level of qualification for Custom Payment Services (CPS). See Appendix A for values. Issuer-generated identifier unique for each original transaction. A code calculated to ensure that key fields in the 0100 authorization message match their respective fields in the deferred clearing message. 062.23 Card Results Indicates the card program that the card used in the transaction is signed up for. See Appendix A. 063 Private-use Field Used for identifying the acquirer s network ID, as well as various reason codes. See Appendix A. Fixed AN1 Req Fixed NP15 Cond Fixed AN4 Cond Fixed AN2 Cond LLVAR Var. by use 063.0 Bit Map Indicates presence of sub fields. Fixed B3 Req 063.1 Network ID Fixed NP4 Req 063.2 Preauth Time Limit 171 Private Use General A code that specifies the network used for authorization of the message. This code must be used in the merchant settlement file. See Appendix A. The time (in hours) the issuer agrees to hold funds for an acquirer. Copied from request. Fields unique to Bank of America Merchant Services processing. See descriptions of subfields below and in Appendix A. Req Fixed NP4 Req LLLVAR B8 + var. by use Cond Version 4.02 Page 133 Last modified August 12, 2009

Real Time Clearing Preauthorized Purchase Completion Response (Continued) Bit Data Element Description Format Attr Presence Number Name 171.0 Bit Map Indicates presence of subfields. Fixed B8 Req 171.8 Transaction Used to indicate various transaction Fixed AN1 Cond Subtype situations. See Appendix A. 173 Settlement Data Data needed to settle the transaction. See Appendix A. BBB VAR TLV (21) 999 Cond Version 4.02 Page 134 Last modified August 12, 2009

3.31 Real Time Clearing Reversal Request Message 3.31.1 Real Time Clearing Purchase 3.31.2 Real Time Clearing Merchandise Return 3.31.3 Real Time Clearing Preauthorized Purchase 3.31.4 Real Time Clearing Preauthorized Completion This message is used to send a reversal request message from the POS to Bank of America Merchant Services MultiLink for a Real Time Clearing transaction. Most of the data from the original request will be required in this reversal request message. The chart below describes: Bit Numbers and Names of all possible data elements for this message If constant, the value to be placed in the field A description of how each data element is used The format and attributes of each data element Required, Optional, Conditional or Not Applicable status of each data element Bit Number Data Element Name Message Type Description Format Attr Presence Value to represent the type of message Value: 0400. See Appendix A. Fixed NP4 Req Represents the presence of secondary bit Fixed B8 Req map and data elements in bits 2 through 64. Represents the presence of tertiary bit map Fixed B8 Cond and data elements in bits 66 through 128. Represents the presence of data elements in Fixed B8 Cond bits 130 through 192. Contains the cardholder account number. LLVAR NP19 Req Primary Bit Map 001 Secondary Bit Map 065 Tertiary Bit Map 002 Primary Account Number 003 Processing Defines the type of transaction. Copied from original request. See Appendix A. 004 Amount 1 Transaction Amount. This field contains the total amount including the purchase amount and cash back if indicated. From original request. Exception: If the transaction was authorized for a lesser amount than the original requested amount, this field contains the authorized amount. 007 Transmission Date and Time 011 System Trace Audit Number Date and Time transaction is sent through the network assigned by the originator. Expressed in GMT MMDDhhmmss. A number assigned by the message initiator that identifies a cardholder transaction. From original request. 012 Local Time Time of the transaction, in merchant s local time. This value stays constant throughout the life of the transaction. This field must be sent in the settlement file. Expressed as hhmmss. From the original request. Fixed NP6 Req Fixed NP12 Req Fixed NP10 Req Fixed NP6 Req Fixed NP6 Req Version 4.02 Page 135 Last modified August 12, 2009

Real Time Clearing Reversal Request (Continued) Bit Data Element Description Format Attr Presence Number Name 013 Local Date Date of the transaction, in merchant s local Fixed NP4 Req date. This value stays constant throughout the life of the transaction. This field must be sent in the settlement file. Expressed as MMDD. From original request. 014 Expiration Date Contains the expiration date on the card. If the card does not have an expiration date, do not send this bit. Expressed as YYMM. Fixed NP4 Cond 018 Merchant Type 019 Acquiring Institution Country 022 POS Entry Mode 025 POS Condition 032 Acquiring Institution ID 037 Retrieval Reference Number 038 Auth ID Response 041 Card Acceptor Term ID 042 Card Acceptor ID Required if present in original request. Merchant Category (MCC). Bank of America Merchant Services-assigned value. From original request. Identifies the country of the location where the transaction occurred. From original request. Defines the method of data entry of the account number and whether a PIN was entered on this transaction. See Appendix A for values. From original request. Describes the condition under which the transaction takes place at the point of service. From original request. See Appendix A. Identifies the financial institution acting as the acquirer of this transaction. Value is constant for all transaction requests and responses. From original request. A number used with other data elements as a key to identify and track all messages related to a given customer transaction or series of system messages. The format for this field is YDDDHHNNNNNN, where YDDD is the date in Julian format, HH is the hour and N-N is a 6 digit transaction number. From original request. The authorization code provided by the issuer when a transaction is approved. (Only an approved transaction can be reversed Unique terminal/device ID. Merchant-defined value. Merchant ID. Assigned by Bank of America Merchant Services. See Appendix A. Fixed NP4 Req Fixed NP3 Req Fixed NP4 Req Fixed NP2 Req LLVAR NP11 Req Fixed AN12 Req Fixed AN6 Opt Fixed ANS8 Req Fixed ANS 15 Req Version 4.02 Page 136 Last modified August 12, 2009

Real Time Clearing Reversal Request (Continued) Bit Data Element Number Name 043 Card Acceptor Name / Location 049 Transaction Currency 059 National POS Geographic Data 060 Additional POS Info 060.1 Terminal Type 060.2 Terminal Entry Capability Description Format Attr Presence Name and location of the card acceptor where the transaction occurred. See Appendix A. Positions: 1-25 Card acceptor name 26-38 City name 39-40 Alpha country code From original request. ISO defined code representing the currency of this transaction. A field to describe the location of the card acceptor within the country. See Appendix A for values. A group of subfields that provide additional information about the point of service. See Appendix A for values. Identifies the point-of-service terminal. From original request. See Appendix A for values. Identifies the terminal s capability to electronically read account numbers and expiration dates from cards. From original request. See Appendix A for values. Contains authorizations characteristics to the back-end authorizer. See Appendix A. Fixed ANS 40 Req Fixed NP3 Req LLVAR BBVAR ANS 14 Var by use Cond Req Fixed NP1 Req Fixed NP1 Req 062 Payment Service Fields LLVAR B8 + AN59 Req 062.0 Bit Map Indicates presence of subfields. Fixed B8 Req 062.1 Authorization Used by the acquirer processor to request Fixed AN1 Req Characteristic Custom Payment Services (CPS). From Indicator original request. See Appendix A. 062.2 Transaction Identifier 063 Private-use Field Issuer-generated identifier unique for each original transaction. Used for identifying the acquirer s network ID, as well as various reason codes. See Appendix A. Fixed NP15 Cond LLVAR Var. by use 063.0 Bit Map Indicates presence of sub fields. Fixed B3 Req 063.1 Network ID A code that specifies the network used for Fixed NP4 Req authorization of the message. Copied from 063.2 Preauth Time Limit 063.3 Message Reason original request. See Appendix A. The time (in hours) the issuer agrees to hold funds for an acquirer. Copied from original request. Describes the specific reason code associated with the transaction. See Appendix A. Req Fixed NP4 N/A (Req for preauth, completion reversal) Fixed NP4 Req Version 4.02 Page 137 Last modified August 12, 2009

Real Time Clearing Reversal Request (Continued) Bit Data Element Number Name 090 Original Data Elements 114 Transport Data 170 Private Use Card Acceptor Street Address 171 Private Use General Description Format Attr Presence Information for tracking the current message back to prior messages for the same cardholder transaction. See Appendix A for detailed field layout. A value assigned by the merchant. It is returned in the reversal response message. See Appendix A. Contains the street address of the card acceptor the location where the transaction occurred. See Appendix A. Fields unique to Bank of America Merchant Services processing. See descriptions of subfields below and in Appendix A. Fixed NP42 Req LLVAR Fixed TLV (**) 255 ANS 25 LLLVAR B8 + var. by use Opt Req Cond 171.0 Bit Map Indicates presence of subfields. Fixed B8 Req 171.8 Transaction Used to indicate various transaction Fixed AN1 Cond Subtype situations. See Appendix A. 173 Settlement Data Data needed to settle the transaction. See Appendix A. BBB VAR Cond TLV (21) 999 Version 4.02 Page 138 Last modified August 12, 2009

3.32 Real Time Clearing Reversal Response Message 3.31.1 Real Time Clearing Purchase 3.31.2 Real Time Clearing Merchandise Return 3.31.3 Real Time Clearing Preauthorized Purchase 3.31.4 Real Time Clearing Preauthorized Completion This message is used to send a reversal response message from Bank of America Merchant Services MultiLink to the POS for a Real Time Clearing transaction. Most of the data from the original request will be required in this reversal request message. The chart below describes: Bit Numbers and Names of all possible data elements for this message If constant, the value to be placed in the field A description of how each data element is used The format and attributes of each data element Required, Optional, Conditional or Not Applicable status of each data element Bit Number Data Element Name Message Type Description Format Attr Presence Value to represent the type of message Value: 0410. See Appendix A. Fixed NP4 Req Represents the presence of secondary bit Fixed B8 Req map and data elements in bits 2 through 64. Represents the presence of tertiary bit map Fixed B8 Cond and data elements in bits 66 through 128. Represents the presence of data elements in Fixed B8 Cond bits 130 through 192. Contains the cardholder account number. LLVAR NP19 Req Primary Bit Map 001 Secondary Bit Map 065 Tertiary Bit Map 002 Primary Account Number 003 Processing Defines the type of transaction. Copied from original request. See Appendix A. 004 Amount 1 Transaction Amount. This field contains the total amount including the purchase amount and cash back if indicated. From original request. Exception: If the transaction was authorized for a lesser amount than the original requested amount, this field contains the authorized amount. 007 Transmission Date and Time 011 System Trace Audit Number 019 Acquiring Institution Country Date and Time transaction is sent through the network assigned by the originator. Expressed in GMT MMDDhhmmss. A number assigned by the message initiator that identifies a cardholder transaction. Copied from request message. Identifies the country of the location where the transaction occurred. Copied from request message. Fixed NP6 Req Fixed NP12 Req Fixed NP10 Req Fixed NP6 Req Fixed NP3 Req Version 4.02 Page 139 Last modified August 12, 2009

Real Time Clearing Reversal Response (Continued) Bit Data Element Number Name 025 POS Condition 032 Acquiring Institution ID 037 Retrieval Reference Number 039 Response 041 Card Acceptor Term ID 042 Card Acceptor ID 049 Transaction Currency 055 EM and Chip Data 063 Private-use Field Description Format Attr Presence Describes the condition under which the transaction takes place at the point of service. Copied from request message. See Appendix A. Identifies the financial institution acting as the acquirer of this transaction. Value is constant for all transaction requests and responses. Copied from request message. A number used with other data elements as a key to identify and track all messages related to a given customer transaction or series of system messages. The format for this field is YDDDHHNNNNNN, where YDDD is the date in Julian format, HH is the hour and N-N is a 6 digit transaction number. From the original request. A code that defines the disposition of the transaction. See Appendix A for values. Unique terminal/device ID. Merchant-defined value. Merchant ID. Assigned by Bank of America Merchant Services. See Appendix A. ISO defined code representing the currency of this transaction. Copied from request message. Electronic Magnetic Signature and chip data. See Appendix A. Used for identifying the acquirer s network ID, as well as various reason codes. See Appendix A. Fixed NP2 Req LLVAR NP11 Req Fixed AN12 Req Fixed AN2 Req Fixed ANS8 Req Fixed ANS Req 15 Fixed NP3 Req BBVAR LLVAR TLV (**) 255 Var. by use 063.0 Bit Map Indicates presence of subfields. Fixed B3 Req 063.1 Network ID A code that specifies the network used for Fixed NP4 Req authorization of the message. Copied from 063.2 Preauth Time Limit 090 Original Data Elements 114 Transport Data the request message. See Appendix A. The time (in hours) the issuer agrees to hold funds for an acquirer. Used only in preauth and completion reversals. Information for tracking the current message back to prior messages for the same cardholder transaction. See Appendix A for detailed field layout. Copied from the request message. A value assigned by the merchant. Copied from reversal request message. See Appendix A. Cond Req Fixed NP4 Req preauth rev, completion rev only Fixed NP42 Req LLVAR TLV (**) 255 Cond Version 4.02 Page 140 Last modified August 12, 2009

Real Time Clearing Reversal Response (Continued) Bit Data Element Number Name 171 Private Use General Description Format Attr Presence Fields unique to Bank of America Merchant Services processing. See descriptions of subfields below and in Appendix A. LLLVAR B8 + var. by use Cond 171.0 Bit Map Indicates presence of subfields. Fixed B8 Req 171.8 Transaction Used to indicate various transaction Fixed AN1 Cond Subtype situations. See Appendix A. 173 Settlement Data Data needed to settle the transaction. See Appendix A. BBB VAR Cond TLV (21) 999 Version 4.02 Page 141 Last modified August 12, 2009

4.0 Settlement Message Formats 4.1 Settlement Request 4.1.1 Settlement Request The Settlement Request message is used by the merchant to notify Bank of America Merchant Services that a particular store or the merchant s system has gone through end-of-day. The message can be used to send totals or simply as an end-of-day notification, in which case all totals are set to zero. If totals are sent, credit transactions are defined as transactions having a credit effect on the cardholder s account (Debit and Credit Merchandise Return), debit transactions are those having a debit effect on the cardholder s account (Debit, EBT and Credit Purchase, Debit and EBT Purchase with Cash Back, Debit Purchase Completion, EBT Electronic Voucher, EBT Cash Withdrawal), credit reversal transactions are those having a credit effect on the cardholder s account (Reversal of: Debit, EBT and Credit Purchase, Debit and EBT Purchase with Cash Back, Debit Purchase Completion, EBT Electronic Voucher, EBT Cash Withdrawal) and debit reversal transactions are those having a debit effect on the cardholder s account (Reversal of: Debit and Credit Merchandise Return). The chart below describes: Bit Numbers and Names of all possible data elements for this message If constant, the value to be placed in the field A description of how each data element is used The format and attributes of each data element Required, Optional, Conditional or Not Applicable status of each data element Bit Number Data Element Name Message Type Primary Bit Map 001 Secondary Bit Map 065 Tertiary Bit Map 007 Transmission Date and Time 011 System Trace Audit Number 070 Network Management Information 074 Credits, Number Description Format Attr Presence Value to represent the type of message Value: 0520. See Appendix A. Represents the presence of secondary bit map and data elements in bits 2 through 64. Represents the presence of tertiary bit map and data elements in bits 66 through 128. Represents the presence of data elements in bits 130 through 192. Date and Time transaction is sent through the network assigned by the originator. This value will vary between the auth request and response. Expressed in GMT MMDDhhmmss. A number assigned by the message initiator that identifies a cardholder transaction. Specifies the type of network management task required. See Appendix A for values. Contains the total number of credit transactions, other than reversals, processed since the last cutoff. Fixed NP4 Req Fixed B8 Req Fixed B8 Cond Fixed B8 Cond Fixed NP10 Req Fixed NP6 Req Fixed NP3 Req Fixed NP10 Req Version 4.02 Page 142 Last modified August 12, 2009

Settlement Request Message (continued) Bit Data Element Number Name 075 Credits, Reversal Number 076 Debits, Number 077 Debits, Reversal Number 086 Credits, Amount 087 Credits, Reversal Amount 088 Debits, Amount 089 Debits, Reversal Amount 097 Amount, Net Settlement 099 Settlement Institution Identification Description Format Attr Presence Contains the total number of reversal credit transactions processed since the last cutoff. Contains the total number of debit transactions, other than reversals, processed since the last cutoff. Contains the total number of reversal debit transactions processed since the last cutoff. Contains the totaled amount of credit transactions, other than reversals, processed since the last cutoff. Contains the totaled amount of reversal credit transactions processed since the last cutoff. Contains the totaled amount of debit transactions, other than reversals, processed since the last cutoff. Contains the totaled amount of reversal debit transactions processed since the last cutoff. Contains the Gross Interchange Value, which is the net of all gross credit and debit amounts for a specific settlement entity. The first byte of this field contains a sign ( C for credit or D for debit). The amount is in the remaining 16 bytes, right-justified, zero-filled. Contains a code that identifies the financial entity for which settlement information is being provided. This field should contain the first 11 digits of the Merchant ID as assigned by Bank of America Merchant Services for a store settlement. For a merchant settlement, this field should contain the 3-digit Bank of America Merchant Services ID followed by 8 zeros. Fixed NP10 Req Fixed NP10 Req Fixed NP10 Req Fixed NP16 Req Fixed NP16 Req Fixed NP16 Req Fixed NP16 Req Fixed ANS 17 Req LLVAR NP11 Req Version 4.02 Page 143 Last modified August 12, 2009

4.2 Settlement Response 4.2.1 Settlement Response The Settlement Response message is sent by Bank of America Merchant Services to acknowledge receipt of a Settlement Request message. The chart below describes: Bit Numbers and Names of all possible data elements for this message If constant, the value to be placed in the field A description of how each data element is used The format and attributes of each data element Required, Optional, Conditional or Not Applicable status of each data element Bit Number Data Element Name Message Type Primary Bit Map 001 Secondary Bit Map 065 Tertiary Bit Map 007 Transmission Date and Time 011 System Trace Audit Number 066 Settlement 070 Network Management Information 074 Credits, Number 075 Credits, Reversal Number 076 Debits, Number 077 Debits, Reversal Number Description Format Attr Presence Value to represent the type of message Value: 0530. See Appendix A. Represents the presence of secondary bit map and data elements in bits 2 through 64. Represents the presence of tertiary bit map and data elements in bits 66 through 128. Represents the presence of data elements in bits 130 through 192. Date and Time transaction is sent through the network assigned by the originator. This value will vary between the auth request and response. Expressed in GMT MMDDhhmmss. A number assigned by the message initiator that identifies a cardholder transaction. Contains a code indicating whether or not Bank of America Merchant Services agrees with the totals sent in the Settlement Request message. Value = 9, indicating no reconciliation is performed. Specifies the type of network management task required. See Appendix A for values. Contains the total number of credit transactions, other than reversals, processed since the last cutoff. Copied from request. Contains the total number of reversal credit transactions processed since the last cutoff. Copied from request. Contains the total number of debit transactions, other than reversals, processed since the last cutoff. Copied from request. Contains the total number of reversal debit transactions processed since the last cutoff. Copied from request. Fixed NP4 Req Fixed B8 Req Fixed B8 Cond Fixed B8 Cond Fixed NP10 Req Fixed NP6 Req Fixed NP1 Req Fixed NP3 Req Fixed NP10 Req Fixed NP10 Req Fixed NP10 Req Fixed NP10 Req Version 4.02 Page 144 Last modified August 12, 2009

Settlement Response Message (continued) Bit Data Element Number Name 086 Credits, Amount 087 Credits, Reversal Amount 088 Debits, Amount 089 Debits, Reversal Amount 097 Amount, Net Settlement 099 Settlement Institution Identification Description Format Attr Presence Contains the totaled amount of credit transactions, other than reversals, processed since the last cutoff. Copied from request. Contains the totaled amount of reversal credit transactions processed since the last cutoff. Copied from request. Contains the totaled amount of debit transactions, other than reversals, processed since the last cutoff. Copied from request. Contains the totaled amount of reversal debit transactions processed since the last cutoff. Copied from request. Contains the Gross Interchange Value, which is the net of all gross credit and debit amounts for a specific settlement entity. Copied from request. Contains a code that identifies the financial entity for which settlement information is being provided. Copied from request. Fixed NP16 Req Fixed NP16 Req Fixed NP16 Req Fixed NP16 Req Fixed ANS 17 Req LLVAR NP11 Req Version 4.02 Page 145 Last modified August 12, 2009

5.0 Network Management Formats 5.1 Network Management Request 5.1.1 Network Management Key Change 5.1.2 Network Management Health Message (Echotest) 5.1.3 Network Management Logon Message 5.1.4 Network Management Logoff Message The 0800 Network Management request message is used by any two communicating endpoints to coordinate system or network events or tasks, and to communicate network status conditions. The recipient of an 0800 Network Management Request message must reply with an 0810 Network Management Response message within a specified time interval. The chart below describes: Bit Numbers and Names of all possible data elements for this message If constant, the value to be placed in the field A description of how each data element is used The format and attributes of each data element Required, Optional, Conditional or Not Applicable status of each data element Bit Number Data Element Name Message Type Primary Bit Map 001 Secondary Bit Map 065 Tertiary Bit Map 007 Transmission Date and Time 011 System Trace Audit Number 037 Retrieval Reference Number 048 Additional Data Private Description Format Attr Presence Value to represent the type of message Value: 0800. See Appendix A. Represents the presence of secondary bit map and data elements in bits 2 through 64. Represents the presence of tertiary bit map and data elements in bits 66 through 128. Represents the presence of data elements in bits 130 through 192. Date and Time transaction is sent through the network assigned by the originator. This value will vary between the request and response. Expressed in GMT MMDDhhmmss. A number assigned by the message initiator that identifies a cardholder transaction. A number used with other data elements as a key to identify and track all messages related to a given customer transaction or series of system messages. The format for this field is YDDDHHNNNNNN, where YDDD is the date in Julian format, HH is the hour and N-N is a 6 digit transaction number. Used for miscellaneous information. Used here to hold the Dynamic Key Exchange Working Key Check Value. See Appendix A. Fixed NP4 Req Fixed B8 Req Fixed B8 Cond Fixed B8 Cond Fixed NP10 Req Fixed NP6 Req Fixed AN12 Req LLVAR Var. by use N/A (Req Dynamic Key Exchange) Version 4.02 Page 146 Last modified August 12, 2009

Network Management Request Message (continued) Bit Data Element Number Name 070 Network Management Information 096 Message Security 105 Double-Length DES Key Description Format Attr Presence Specifies the type of network management task required. See Appendix A for values. Contains the PIN encryption working key when single-length keys are used. In a key change request exactly one of bits 096 or 105 must be present. Contains the PIN encryption working key when double-length keys are used. In a key change request exactly one of bits 096 or 105 must be present. Fixed NP3 Req Fixed B8 N/A (Cond Dynamic Key Exchange) Fixed B16 N/A (Cond Dynamic Key Exchange) Version 4.02 Page 147 Last modified August 12, 2009

5.2 Network Management Response 5.2.1 Network Management Key Change 5.2.2 Network Management Health Message (Echotest) 5.2.3 Network Management Logon Message 5.2.4 Network Management Logoff Message An 0810 Network Management Response is sent to confirm the receipt of an 0800 Network Management request message. The chart below describes: Bit Numbers and Names of all possible data elements for this message If constant, the value to be placed in the field A description of how each data element is used The format and attributes of each data element Required, Optional, Conditional or Not Applicable status of each data element Bit Number Data Element Name Message Type Primary Bit Map 001 Secondary Bit Map 065 Tertiary Bit Map 007 Transmission Date and Time 011 System Trace Audit Number 037 Retrieval Reference Number 039 Response 070 Network Management Information Description Format Attr Presence Value to represent the type of message Value: 0810. See Appendix A. Represents the presence of secondary bit map and data elements in bits 2 through 64. Represents the presence of tertiary bit map and data elements in bits 66 through 128. Represents the presence of data elements in bit maps 130 through 192. Date and Time transaction is sent through the network assigned by the originator. This value will vary between the request and response. Expressed in GMT MMDDhhmmss. A number assigned by the message initiator that identifies a cardholder transaction. Copied from request message. A number used with other data elements as a key to identify and track all messages related to a given customer transaction or series of system messages. The format for this field is YDDDHHNNNNNN, where YDDD is the date in Julian format, HH is the hour and N-N is a 6 digit transaction number. Copied from request message. A code that defines the disposition of the transaction. See Appendix A for values. Specifies the type of network management task required. Copied from request message. See Appendix A. Fixed NP4 Req Fixed B8 Req Fixed B8 Cond Fixed B8 Cond Fixed NP10 Req Fixed NP6 Req Fixed AN12 Req Fixed AN2 N/A (Req Dynamic Key Exchange) Fixed NP3 Req Version 4.02 Page 148 Last modified August 12, 2009

6.0 PIN Translation Formats 6.1 PIN Translation Request Message 6.1.1 PIN Translation Request for card activation 6.1.2 PIN Translation Request for card authorization This message is used to request translation of a PIN block encrypted under the merchant s standard key to encryption under an alternate key. The Processing field (bit 3) determines the transaction type. The chart below describes: Bit Number and Names of all possible data elements for this message If constant, the value to be placed in the field A description of how each data element is used The format and attributes of each data element Required, Optional, Conditional or Not Applicable status of each data element Bit Number Data Element Name Message Type Description Format Attr Presence Value to represent the type of message Value: 0900. See Appendix A. Fixed NP4 Req Represents the presence of secondary bit Fixed B8 Req map and data elements in bits 2 through 64. Represents the presence of tertiary bit map Fixed B8 Cond and data elements in bits 66 through 128. Represents the presence of data elements in Fixed B8 Cond bits 130 through 192. Contains the cardholder account number. LLVAR NP19 Req Primary Bit Map 001 Secondary Bit Map 065 Tertiary Bit Map 002 Primary Account Number 003 Processing Defines the type of transaction. See Appendix A. 004 Amount 1 Transaction Amount. Assumes a 2 position decimal, right-justified, zero filled. This field contains the total amount including the purchase amount and cash back if indicated. Transactions settled through Bank of America Merchant Services s settlement system are limited to 7 characters ($99,999.99). 007 Transmission Date and Time 011 System Trace Audit Number Date and Time transaction is sent through the network assigned by the originator. Expressed in GMT MMDDhhmmss. A number assigned by the message initiator that identifies a cardholder transaction. Fixed NP6 Req Fixed NP12 Req Fixed NP10 Req Fixed NP6 Req Version 4.02 Page 149 Last modified August 12, 2009

PIN Translation Request Message (Continued) Bit Data Element Description Format Attr Presence Number Name 012 Local Time Time of the transaction, in merchant s local Fixed NP6 Req time. This value stays constant throughout the life of the transaction. This field must be sent in the settlement file. Expressed as hhmmss. For submissions and resubmissions, this is the time of the original transaction. 013 Local Date Date of the transaction, in merchant s local Fixed NP4 Req date. This value stays constant throughout the life of the transaction. This field must be sent in the settlement file. Expressed as MMDD. For submissions and resubmissions, this is the date of the original transaction. 014 Expiration Contains the expiration date on the card. If Fixed NP4 Cond Date the card does not have an expiration date, do not send this bit. Expressed as YYMM. 018 Merchant Merchant Category (MCC). Bank of Fixed NP4 Req Type 019 Acquiring Institution Country 022 POS Entry Mode 025 POS Condition 026 POS PIN Capture 032 Acquiring Institution ID 033 Forwarding Institution ID America Merchant Services-assigned value. Identifies the country of the location where the transaction occurred. See Appendix A for values. Defines the method of data entry of the account number and whether a PIN was entered on this transaction. See Appendix A for values. Describes the condition under which the transaction takes place at the point of service. See Appendix A for values. Contains a value indicating the maximum number of PIN characters that can be accepted by the point-of-service device. See Appendix A. Identifies the financial institution acting as the acquirer of this transaction. Value is constant for all transaction requests and responses. This is an Bank of America Merchant Services -assigned identification number. Value 45592900000. Identifies the processor that forwards the request to Bank of America Merchant Services, if that processor is different from the institution indicated in field 032. This is an Bank of America Merchant Servicesassigned identification number. Fixed NP3 Req Fixed NP4 Req Fixed NP2 Req Fixed NP2 Cond LLVAR NP11 Req LLVAR NP11 Cond Version 4.02 Page 150 Last modified August 12, 2009

PIN Translation Request Message (Continued) Bit Data Element Description Format Attr Presence Number Name 035 Track 2 Data Unaltered contents of the data read off Track LLVAR NP37 Req 2 of the mag stripe, excluding the beginning and ending sentinels and LRC characters. Required for Debit transactions. This field is only present when Track 2 has been read or assembled via a contactless means at the terminal. 037 Retrieval A number used with other data elements as a Fixed AN12 Req Reference Number key to identify and track all messages related to a given customer transaction or series of system messages. The format for this field is YDDDHHNNNNNN, where YDDD is the date in Julian format, HH is the hour and N-N is a 6 digit transaction number. 041 Card Acceptor Unique terminal/device ID. Merchant-defined Fixed ANS8 Req Term ID value. 042 Card Acceptor Merchant ID. Assigned by Bank of America Fixed ANS Req ID 043 Card Acceptor Name / Location 049 Transaction Currency Merchant Services. See Appendix A. Name and location of the card acceptor where the transaction occurred. See Appendix A. Positions: 1-25 Card acceptor name 26-38 City name 39-40 Alpha country code ISO defined code representing the currency of this transaction. 052 PIN Data Contains the 16 hexadecimal digits of a DUKPT PIN block. See Appendix A. 053 Security- Data used by the issuer to process PINs. Related See Appendix A for field details. Control Information 059 National POS Geographic Data 060 Additional POS Info 060.1 Terminal Type 060.2 Terminal Entry Capability A field to describe the location of the card acceptor within the country. See Appendix A for values. A group of subfields that provide additional information about the point of service. See Appendix A for values. Identifies the point-of-service terminal. See Appendix A for values. Identifies the terminal s capability to electronically read account numbers and expiration dates from cards. See Appendix A for values. Fixed 15 ANS 40 Req Fixed NP3 Req Fixed B8 Req Fixed NP16 Req LLVAR BBVAR ANS 14 Var. by use Cond Req Fixed NP1 Req Fixed NP1 Req Version 4.02 Page 151 Last modified August 12, 2009

PIN Translation Request Message (Continued) Bit Data Element Number Name 061.1 Other Transaction Amount 063 Private-use Field Description Format Attr Presence Contains the cash back amount, if any. If the transaction does not include cash back, this field is not sent. Used for identifying the acquirer s network ID, as well as various reason codes. See Appendix A. BBVAR NP12 Cond LLVAR Var. by use 063.0 Bit Map Indicates presence of subfields. Fixed B3 Req 063.1 Network ID A code that specifies the network to be used Fixed NP4 Req for authorization of the message. See 114 Transport Data 127 Private Use DUKPT 170 Private Use Card Acceptor Street Address Appendix A for values. A value assigned by the merchant. It is returned in the response message. See Appendix A. Contains hexadecimal digits of the Key Serial Number (KSN or IKSN) for a DUKPT PIN block. The length byte contains the length of the Key Serial Number. (Valid length is a minimum of 10 digits and a maximum of 20 digits.) Otherwise, not used. See Appendix A. Contains the street address of the card acceptor the location where the transaction occurred. See Appendix A. Req LLVAR TLV (**) 255 Opt LLVAR NP20 Req Fixed ANS 25 Req Version 4.02 Page 152 Last modified August 12, 2009

6.2 PIN Translation Response Message 6.2.1 PIN Translation Request for card activation 6.2.2 PIN Translation Request for card authorization This message is used to send a PIN translation response back to the merchant. The Processing field (bit 3) determines the transaction type. The chart below describes: Bit Number and Names of all possible data elements for this message If constant, the value to be placed in the field A description of how each data element is used The format and attributes of each data element Required, Optional, Conditional or Not Applicable status of each data element Bit Number Data Element Name Message Type Primary Bit Map 001 Secondary Bit Map 065 Tertiary Bit Map 002 Primary Account Number 003 Processing Description Format Attr Presence Value to represent the type of message. Value: 0910. See Appendix A. Represents the presence of secondary bit map and data elements in bits 2 through 64. Represents the presence of tertiary bit map and data elements in bits 66 through 128. Represents the presence of data elements 130 through 192. Contains the cardholder account number. Copied from the request message. Defines the type of transaction. Copied from the request message. See Appendix A for values. 004 Amount 1 Transaction Amount. Copied from request message. Must be sent in the settlement file. 007 Transmission Date and Time transaction is sent through Date and Time the network. Expressed in GMT 011 System Trace Audit Number 019 Acquiring Institution Country 025 POS Condition 032 Acquiring Institution ID MMDDhhmmss. A number assigned by the message initiator that identifies a cardholder transaction. Copied from request message. Identifies the country of the location where the transaction occurred. Copied from request message. Describes the condition under which the transaction takes place at the point of service. Copied from request message. See Appendix A. Identifies the financial institution acting as the acquirer of this transaction. Value is constant for all transaction requests and responses. Copied from request message. Fixed NP4 Req Fixed B8 Req Fixed B8 Cond Fixed B8 Cond LLVAR NP19 Req Fixed NP6 Req Fixed NP12 Req Fixed NP10 Req Fixed NP6 Req Fixed NP3 Req Fixed NP2 Req LLVAR NP11 Req Version 4.02 Page 153 Last modified August 12, 2009

PIN Translation Response Message (Continued) Bit Data Element Number Name 037 Retrieval Reference Number 038 Auth ID Response Description Format Attr Presence A number used with other data elements as a key to identify and track all messages related to a given customer transaction or series of system messages. The format for this field is YDDDHHNNNNNN, where YDDD is the date in Julian format, HH is the hour and N-N is a 6 digit transaction number. Copied from request message. The authorization code provided by the issuer when a transaction is approved. Will only be present for approved transactions. A code that defines the disposition of the transaction. See Appendix A for values. Unique terminal/device ID. Merchant-defined value. Merchant ID. Assigned by Bank of America Merchant Services. See Appendix A. ISO defined code representing the currency of this transaction. Copied from request message. 039 Response 041 Card Acceptor Term ID 042 Card Acceptor ID 049 Transaction Currency 052 PIN Data Contains a translated PIN, encrypted and formatted as a block of 16 hexadecimal digits. See Appendix A. 063 Private-use Field Used for identifying the acquirer s network ID, as well as various reason codes. See Appendix A. Fixed AN12 Req Fixed AN6 Cond Fixed AN2 Req Fixed ANS8 Req Fixed ANS Req 15 Fixed NP3 Req Fixed B8 Req LLVAR Var. by use 063.0 Bit Map Indicates presence of subfields. Fixed B3 Req 063.1 Network ID A code that specifies the network used for Fixed NP4 Req authorization of the message. See Appendix 114 Transport Data A for values. A value assigned by the merchant. Copied from request message. See Appendix A. LLVAR TLV (**) 255 Req Cond Version 4.02 Page 154 Last modified August 12, 2009

7.0 Rejected Messages A reject message may be sent by Bank of America Merchant Services in response to an UNRECOGNIZED message or because of an error in parsing a message. To determine if an incoming message contains a reject message header, check two fields, as follows: The length in header field 1 will be 26 or higher The first bit of header field 13 will be 1 (which means that the header includes field 14) Field 14 contains a 4-digit reject code describing the error (see below). Please note: the value of field 14 will be hexadecimal as indicated by the B2 field attribute. For your convenience, field values are shown in both decimal and hexadecimal in the table below. NOTE: An incoming rejected message contains the reject message header plus the original message header and data. Value Value Field Description (decimal) (hex) 0001 0001 002 Invalid length 034 0002 0002 002 Invalid value 034 0003 0003 Header 5 Invalid value 0004 0004 Header 6 Invalid value 0008 0008 003 Invalid value 0009 0009 004 Invalid value 0010 000A 007 Invalid value 0011 000B 011 Invalid value 0012 000C Header 1 Invalid value 0013 000D Header 2 Invalid value 0014 000E 014 Invalid value 0015 000F Header 3 Invalid value 0016 0010 Header 4 Invalid value 0017 0011 018 Invalid value 0018 0012 025 Invalid value 0019 0013 022 Invalid value 0020 0014 032 Invalid length 0021 0015 Header 6 PIN present, but station not certified for PIN processing 032 0022 0016 Header 7 Invalid value in request 0023 0017 Header 8 Invalid value 0024 0018 035 Invalid length 0025 0019 Header 9 Invalid value 0026 001A 061 Invalid length 0027 001B 035 Bad track data 045 0028 001C 059 Invalid length 0029 001D 019 Invalid value 059 0030 001E Header 10 Invalid value Version 4.02 Page 155 Last modified August 12, 2009

Value Value Field Description (decimal) (hex) 0031 001F Header 11 Invalid value 0033 0021 019 033 Invalid value (019) Field missing (033) 0034 0022 038 Invalid value 0035 0023 020 Invalid value 0036 0024 026 Invalid value 0037 0025 049 Invalid value 050 0038 0026 015 Invalid value 0042 002A 070 Invalid value 0055 0037 090 Invalid value 0056 0038 033 Invalid length 0057 0039 033 Invalid value 0058 003A 099 Invalid length 0062 003E 063.1 Invalid value 0063 003F 048 Invalid length 0070 0046 026 Invalid value 0071 0047 044 Invalid length 0072 0048 060 Invalid length 0082 0052 100 Invalid value 0087 0057 039 Invalid value 0088 0058 053 Invalid value 0090 005A 012 Invalid value 0091 005B 013 Invalid value 0092 005C 023 Invalid value 0094 005E 037 Invalid value in first four digits 0095 005F 037 Invalid value 0096 0060 042 Invalid value 0100 0064 100 Invalid length 0102 0066 045 Invalid length 0105 0069 060 Invalid value 0106 006A 061 Invalid amount (nonnumeric) 0111 006F 111 Invalid length 0113 0071 063.2 Invalid value 0114 0072 063.3 Invalid value 0115 0073 095 Invalid value or value greater than field 004 0118 0076 021 Invalid value 0119 0077 068 Invalid value 0120 0078 069 Invalid value 0123 007B 123 Invalid length 0125 007D 125 Invalid length 0126 007E 095 Value not numeric, or the field 095 value is equal or greater than the field 004 transaction amount 0127 007F 044.2 Invalid value 0130 0082 063.6 Invalid value 0134 0086 028 Invalid value 0135 0087 063.7 Invalid value 0137 0089 123 Invalid length Version 4.02 Page 156 Last modified August 12, 2009

Value Value Field Description (decimal) (hex) 0142 008E 014 Invalid value on track 2 read/track 1 read 022 035 045 0148 0094 126.10 Invalid value (position 1) 0149 0095 044.10 Invalid value 126.10 0151 0097 062 Invalid length 0152 0098 062.1 Invalid value 0153 0099 062.2 Invalid value 0155 009B 062.11 Invalid value 0169 00A9 043 Invalid value 0170 00AA 041 Invalid value 0180 00B4 126.0 Invalid bitmap 0181 00B5 126.1 Invalid field 0182 00B6 126.2 Invalid field 0192 00C0 055 Invalid value 0215 00D7 115 Invalid length 0226 00E2 126 Invalid length 0249 00F9 054 Invalid length 0250 00FA 054 Field missing 0251 00FB 002 Field missing 034 0259 0103 Header 8 Field missing 0260 0104 Header 9 Field missing 0274 0112 003 Field missing 0275 0113 004 Field missing 0276 0114 007 Field missing 0277 0115 011 Field missing 0278 0116 012 Field missing 0279 0117 013 Field missing 0280 0118 014 Field missing 0283 011B 018 Field missing 0284 011C 025 Field missing 0285 011D 022 Field missing 0287 011F 032 Field missing 0289 0121 041 Field missing 0291 0123 035 Field missing 0293 0125 038 Field missing 0294 0126 039 Field missing 0295 0127 052 Field missing 0301 012D 059 Length attribute missing or field missing 060 0302 012E 059 Field missing or field invalid 060 0306 0132 019 Field missing 0310 0136 037 Field missing 0311 0137 042 Field missing 0312 0138 043 Field missing 0314 013A 020 Field missing Version 4.02 Page 157 Last modified August 12, 2009

Value Value Field Description (decimal) (hex) 0315 013B 049 Field missing 0319 013F 063.1 Field missing 0321 0141 070 Field missing 0334 014E 100 Field missing 0336 0150 090 Field missing 0345 0159 063.2 Field missing 0346 015A 063.3 Field missing 0360 0168 060 Field missing 0364 016C 126.1 Field missing 0365 016D 126.2 Field missing 0379 017B 044 Field missing 044.2 0384 0180 053, 127 Field missing or invalid value 0400 0190 063.0 Parse error or invalid length. The absence of this field may result in other reject codes 0452 01C4 021 Field missing 0453 01C5 068 Field missing 0454 01C6 069 Field missing 0455 01C7 033 Field missing 0458 01CA 063.8 Field missing 0483 01E3 062.1 Field missing 062.2 0485 01E5 063.6 Field missing 0488 01E8 063.6 Ecommerce indicator missing or invalid 0514 0202 032 Response value does not match request value 037 0517 0205 054 Value for account type does not match value in field 003 account type 061 0518 0206 022 040 Field not allowed in message (022, 054, 060) Inconsistent data elements (040) 054 060 0519 0207 Header 2 Invalid header format 0521 0209 002 Track 2 account number is missing or does not agree with field 002 035 0526 020E 126.6 Invalid length 0528 0210 003 Invalid from account code 0529 0211 003 First two digits of reply not same as request 0530 0212 049 Nondomestic currency 051 0538 021A 101 Invalid length 0590 024E 039 Invalid value (value should be 00 or 55 and is not) 63.6 0591 024F 045 Track 1 account number does not agree with field 002 or 034 0592 0250 025 Value is 01 or 08, but a PIN is present 052 0593 0251 022 Invalid code (not compatible with field 025) 025 0596 0254 022 025 Consistency error: message is for a different cardholder function type than other records in transaction set Version 4.02 Page 158 Last modified August 12, 2009

Value Value Field Description (decimal) (hex) 0599 0257 Header 9 003 Field or message consistency error: response values do not match corresponding request 0600 0258 002 Consistency error: The account number does not match that already in the transaction set 0602 025A Header 9 Consistency error: message is out of sequence with previously processed messages for same cardholder transaction 0603 025B Header 9 Consistency error: One of the following fields does not match between request and response: account number, transaction amount, processing code; or the time value is present in the request, but not the response; or the message type in the response is not the proper one for the request 0604 025C Header 9 Consistency error: Duplicate response 0606 025E Header 6 Not signed on 0607 025F 070 Invalid value in reply 0608 0260 022 Position 3 = 8 when a PIN is present in a stand-alone transaction 0610 0262 003 First two digits not compatible with field 018 018 0611 0263 022 Positions 1-2 = 01 when magnetic stripe data is present in a request 0619 026B Header 7 Not returned in response 0623 026F 028 Field present when not allowed 0626 0272 126.7 Invalid length 0628 0274 063.8 Invalid value (non-numeric) 0643 0283 043 Invalid national POS geographic code 059 0647 0287 025 Consistency error: POS condition code in the response does not match the 0648 0288 062.1 062.11 062.15 value in the request Invalid value for merchandise return 0649 0289 063.3 Invalid chargeback 0677 02A5 179 Invalid length or data 0678 02A6 178 Invalid length or data 0679 02A7 173 Invalid length or data 0689 02B1 177 Invalid length or data 0690 02B2 163 Invalid length 0691 02B3 169 Invalid length 0692 02B4 168 Invalid length 0693 02B5 164 Invalid length 0694 02B6 104 Invalid length 0695 02B7 171 Invalid length 0696 02B8 171.2 Invalid value 0697 02B9 126.16 Invalid length 0698 02BA 123 Invalid value 0699 02BB 127 Invalid length Version 4.02 Page 159 Last modified August 12, 2009

8.0 Message Flows 8.1 Transaction Message Flows These examples each show how individual message flow through the MultiLink system. A merchant must, however, be capable of processing multiple messages through a single connection at the same time. They must be able to send a request for a second transaction before receiving a response from the first, as well as processing network management messages interleaved with transactions. 8.1.1 Debit & EBT Transaction Message Flows 8.1.1.1 Debit, EBT and POS Check Normal Transaction Acquiring Processor 1 0200 Request BA Merchant Services 2 Request Issuing Processor 0210 Response 4 Response 3 8.1.1.2 Debit, EBT and POS Check Transaction with Reversal Acquiring 1 Processor 0200 Request 0210 Response BA Merchant Services 2 4 Request Response 3 Issuing Processor 5 0400 Reversal 0410 Reversal Response 6 7 Reversal Response 8 Version 4.02 Page 160 Last modified August 12, 2009

8.1.1.3 Debit, EBT and POS Check Transaction with Reversal (acquirer times out before response received) Acquiring Processor 1 3 0200 Request 0400 Reversal 0410 Reversal Response BA Merchant Services 4 2 Request Response (late) Issuing Processor 6 Reversal 5 Response 7 8.1.1.4 Debit & EBT Submission/Resubmission Acquiring Processor 0200 Request BA Merchant Request Issuing 1 0210 Resp (NSF) Services 2 Response (NSF) Processor (Same Day) 4 3 0200 Submission Req Request 5 0210 Resp (NSF) 6 Response (NSF) (Day 2) 8 7 0200 Resubmission Req Request 9 10 0210 Resp (apprvd) Response (approved) 12 11 8.1.2 Credit Transaction Message Flows 8.1.2.1 Credit Normal Transaction Acquiring Processor 1 0100 Request BA Merchant Services 2 Request Issuing Processor 0110 Response 4 Response 3 Version 4.02 Page 161 Last modified August 12, 2009

8.1.2.2 Credit Transaction with Reversal Acquiring Processor 1 0100 Request 0110 Response BA Merchant Services 4 2 Request Response 3 Issuing Processor 5 0400 Reversal 0410 Reversal Response 6 7 Reversal Response 8 8.1.2.3 Credit Transaction with Reversal (acquirer times out before response received) Acquiring Processor 1 3 0100 Request 0400 Reversal 0410 Reversal Response BA Merchant Services 4 2 Request Response (late) Issuing Processor 6 Reversal 5 Response 7 Version 4.02 Page 162 Last modified August 12, 2009

8.1.2.4 Credit Advice Transaction Acquiring Processor 1 0120 Advice BA Merchant Services 0130 Advice Response 2 8.1.3 Check Acceptance Transaction Message Flows 8.1.3.1 Check Acceptance Normal Transaction Acquiring Processor 1 0100 Request BA Merchant Services 2 Request Check Processor 0110 Response 4 Response 3 Version 4.02 Page 163 Last modified August 12, 2009

8.1.4 Settlement Transaction Message Flows 8.1.4.1 Settlement Request Transaction Acquiring Processor 1 0520 Request BA Merchant Services 0530 Response 2 Version 4.02 Page 164 Last modified August 12, 2009

8.2 Network Management Message Flows 8.2.1 Merchant-Initiated Logon Acquiring Processor 1 0800 Acquirer Logon (bit 70 = 001) BA Merchant Services 0810 Response 2 8.2.2 Bank of America Merchant Services-Initiated Logon Acquiring Processor 0800 Issuer Logon (bit 70 = 001) BA Merchant Services 1 2 0810 Response 8.2.3 Merchant-Initiated Logoff Acquiring Processor 1 0800 Acquirer Logoff (bit 70 = 002) BA Merchant Services 0810 Response 2 Version 4.02 Page 165 Last modified August 12, 2009

8.2.4 Bank of America Merchant Services-Initiated Logoff Acquiring Processor 0800 Issuer Logoff (bit 70 = 002) BA Merchant Services 1 2 0810 Response 8.2.5 Merchant-Initiated Echo Test Acquiring Processor 1 0800 Echo Test (bit 70 = 001) BA Merchant Services 0810 Response 2 8.2.6 Bank of America Merchant Services-Initiated Echo Test Acquiring Processor 0800 Echo Test (bit 70 = 001) 1 BA Merchant Services 2 0810 Response Version 4.02 Page 166 Last modified August 12, 2009

8.2.7 Merchant-Initiated Key Change Acquiring Processor 1 4 0800 Request for Key Change (bit 70 = 160) 0810 Response 0800 Key Change (bit 70 = 162) 0810 Response 2 3 BA Merchant Services 8.2.8 Bank of America Merchant Services-Initiated Key Change Acquiring Processor 0800 Key Change (bit 70 = 162) BA Merchant Services 1 2 0810 Response Version 4.02 Page 167 Last modified August 12, 2009

8.3 PIN Translation Message Flows 8.3.1 PIN Translation Request and Response Version 4.02 Page 168 Last modified August 12, 2009

9.0 Submission & Resubmission Processing 9.1 Overview Bank of America Merchant Services s Authorization Network is configured to provide the maximum opportunity for a merchant transaction to be authorized. Bank of America Merchant Services has implemented Submission & Resubmission processing to address those situations where the merchant is unable to transmit the transaction to Bank of America Merchant Services, the card issuer is not available to authorize the transaction at the time it is taking place, or the transaction is declined for non-sufficient funds or because daily approval limits would be exceeded. Submission & Resubmission processing allows the merchant to assume the risk of approving selected debit transactions, which had previously been declined with specific response codes. These transactions may then be sent to Bank of America Merchant Services to attempt to secure an online authorization. The first time a declined transaction is re-presented to Bank of America Merchant Services, it is called a Submission. Any subsequent representments are called Resubmissions. Transactions may be submitted and resubmitted according to Bank of America Merchant Services Network Rules (see below). The merchant must store the original PIN data in a secure format and send the encrypted PIN to Bank of America Merchant Services under the current key value on the Submission. PIN data is not sent on Resubmissions. 9.2 Bank of America Merchant Services Supported Transactions Bank of America Merchant Services supports Submission & Resubmission processing for the following transaction types: Transaction Type Debit Debit Purchase with Cash Back Debit Return and for the following response codes: Decline Description 19 Retry Transaction 51 Insufficient funds 61 Over Limit Amount 65 Limit Exceeded 91 Network Unavailable 92 Bank Unavailable 96 System malfunction 9.3 Message Elements For Submission & Resubmission transactions the debit request (0200) message is used, with a value of 5202 (Submission) or 5204 (Resubmission) in field 63.3. See Section 3.1 Debit and EBT Request Message and Appendix A Field 63.3. Version 4.02 Page 169 Last modified August 12, 2009

9.4 Bank of America Merchant Services Network Rules Transactions that are declined for one of the listed decline codes may be submitted once during the same day as the original transaction. Submitted transactions that are declined for one of the listed decline codes may be resubmitted once per day for up to nine days. Version 4.02 Page 170 Last modified August 12, 2009

Appendix A Bit Information Message Type Each message is assigned a 4-character message ID. This message ID categorizes the type of transaction to be executed. The table below gives a representation of the definition of each position within the message ID. Bank of America Merchant Services MultiLink does not support all of these values. The values for each supported message are listed with the detail transactions defined in section 3. Message Class Message Function Transaction Originator 00 Reserved 0 Request 0 Acquirer 01 Authorization 1 Request Response 1 Acquirer Repeat 02 Financial 2 Advice 2 Card Issuer 03 File Action 3 Advice Response 3 Card Issuer Repeat 04 Reversal/Chargeback 4 Notification 4 Other 05 Reconciliation 5 Reserved 5 Other Repeat 06 Administrative 6 Reserved 6 Reserved 07 Fee Collection 7 Reserved 7 Reserved 08 Network Management 8 Reserved 8 Reserved 09 Reserved 9 Reserved 9 Reserved Version 4.02 Page 171 Last modified August 12, 2009

Secondary Bit Map (bit 1) Bank of America Merchant Services MultiLink utilizes primary, secondary and tertiary bit maps. The primary bit map represents data fields 2 through 64. The secondary bit map represents bits 66 through 128. The tertiary bit map represents bits 130 through 192. Data fields 1, 65 and 129 can not exist, as these bits are used to indicate presence of subsequent bit maps. The secondary bit map is only required if data elements represented by bits 66 through 128 or the tertiary bit map are to be used in a particular message. Examples: Transport Data (bit 114) and Private Use DUKPT (bit 127) are needed in a message. The Secondary Bit Map will look like this in hexadecimal representation: 0000000000004002 And this in binary representation (spaces provided only for clarity): 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0100 0000 0000 0010 No data elements represented by the Secondary Bit Map are needed in a message. However, data elements represented by the Tertiary Bit Map are needed. The Secondary Bit Map will look like this in hexadecimal representation: 8000000000000000 And this in binary representation (spaces provided only for clarity): 1000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 Version 4.02 Page 172 Last modified August 12, 2009

Primary Account Number (bit 2) This field contains a number identifying the customer account or relationship. If track data appears in the message, the account number in this field must match the account number in Track 2 Data (bit 35) and/or Track 1 Data (bit 45). Version 4.02 Page 173 Last modified August 12, 2009

Processing (bit 3) The Processing field specifically defines the action to be taken with the message as well as the type of account affected. Values for Bit 3 are as follows: Positions 1 and 2 Describes the transaction type (NP2) Description 00 Purchase of Goods and/or Services (also Card Verification) 01 Cash Withdrawal 03 Check Acceptance, POS Check Guarantee with Conversion 04 POS Check Verification with Conversion 18 POS Check Conversion Only 20 Return 30 Balance Inquiry 50 Bill Payment 70 PIN Translation for card activation (only valid for PIN Translation message types) 71 PIN Translation for card authorization (only valid for PIN Translation message types) Positions 3 and 4 Describes the Account Type ( from account type for transfers) (NP2) Description 00 Default (also referred to as Primary or Funding Account) 96 Cash Benefit Account (EBT only) 98 Food Stamp Account (EBT only) Positions 5 and 6 Describes the Account Type ( to account type for transfers) (NP2) Description 00 Default (also referred to as Primary or Funding Account) 96 Cash Benefit Account (EBT only) 98 Food Stamp Account (EBT only) Version 4.02 Page 174 Last modified August 12, 2009

Amount 1 (bit 4) This field contains the transaction amount, including any cashback amount. No decimal point appears in the field. Two decimal places are assumed. Card verification transactions (without authorization) will have all zeros in Amount 1. Partial authorization responses will have the authorized amount in Amount 1. Version 4.02 Page 175 Last modified August 12, 2009

Transmission Date And Time (bit 7) This field contains the date and time, expressed in GMT, of the transaction. It will be set by the message initiator in each original message. The value must be saved by the recipient of the message and returned in the response to that message. This field is a key element to matching a response to an original message. The merchant should enter a new value each time an original message is generated. The format of the field is MMDDhhmmss, where: MM = two-digit month DD = two-digit day hh = two-digit hour mm = two-digit hour ss = two-digit second Examples of sequences of messages that will have a common Transmission Date And Time: Debit request debit response Credit request credit response Debit reversal request debit reversal response (note that the Transmission Date And Time of the reversal request will not match the Transmission Date And Time of the original request-response sequence Debit preauth request debit preauth response Debit preauth completion request debit preauth completion response (note that the Transmission Date And Time of the completion request will not match the Transmission Date And Time of the preauth request that precedes it Network management request network management response (can be intiated by the merchant or Bank of America Merchant Services) Version 4.02 Page 176 Last modified August 12, 2009

System Trace Audit Number (bit 11) This field contains a number assigned by the message intitator that identifies the message and any related messages that follow. This field is a key element to matching related messages. The value must be saved by the recipient of the message and returned in the response to that message. Further, the same value must be used by the message initiator in any related messages. Examples of related messages that must share a common System Trace Audit Number: Debit request debit response debit reversal request debit reversal response Credit request credit response credit reversal request credit reversal response Debit preauth request debit preauth response debit preauth completion request debit preauth completion response (and any attendant reversals) Network management request network management response (can be intiated by the merchant or Bank of America Merchant Services) Version 4.02 Page 177 Last modified August 12, 2009

Local Time (bit 12) The time of the transaction, expressed in the merchant s local time. The format is hhmmss, where hh = two-digit hour mm = two-digit minute ss = two-digit second The value must remain constant through all related messages. Examples of related messages that must share a common Local Time: Debit request debit reversal request Credit request credit reversal request Debit preauth request debit preauth completion request (and any attendant reversals) If this field is present in the message, it must be sent in the settlement file, if settling with Bank of America Merchant Services. Version 4.02 Page 178 Last modified August 12, 2009

Local Date (bit 13) The date of the transaction, expressed in the merchant s local time. The format is MMDD, where MM = two-digit month DD = two-digit day The value must remain constant through all related messages. Examples of related messages that must share a common Local Date: Debit request debit reversal request Credit request credit reversal request Debit preauth request debit preauth completion request (and any attendant reversals) If this field is present in the message, it must be sent in the settlement file, if settling with Bank of America Merchant Services. Version 4.02 Page 179 Last modified August 12, 2009

Expiration Date (bit 14) This field contains the date after which the customer s account expires. It is expressed as YYMM, where: YY = two-digit year MM = two-digit month If the particular message specifies that the field is required and no expiration date is available, the value 4912 should be sent in this field. Version 4.02 Page 180 Last modified August 12, 2009

Merchant Type (bit 18) This field contains a 4-digit code that describes the merchant s type of business, product or service. These codes are based on the Merchant Classification Guideline and are assigned by Bank of America Merchant Services. Version 4.02 Page 181 Last modified August 12, 2009

Acquiring Institution Country (bit 19) This field contains the country code representing the location where the transaction took place (as opposed to the country code of the merchant headquarters, processing center, etc.). Frequently-used countries and country codes (if you need a code for a country not listed here, please contact your Bank of America Merchant Services representative): Country Country Canada 124 Guam 316 Northern Mariana Islands 580 Puerto Rico 630 United States 840 U.S. Virgin Islands 850 Version 4.02 Page 182 Last modified August 12, 2009

POS Entry Mode (bit 22) The POS Entry Mode defines the manner in which the transaction was entered into the POS device or transaction site and whether PIN encryption was used. Position 1 & 2 Transaction Entry Mode (NP2) Value Description 00 Unknown or terminal not used (valid for Bill Payment) 01 Manual 06 Key-entered PAN (Bill Payment only) 07 Contactless chip transaction using chip data rules (reserved for future use) 84 MICR read 90 Magnetic Stripe Read (CVV check possible) 91 Contactless transaction using magnetic stripe data rules; CVV or dcvv check possible) Position 3 PIN Entry Mode (NP1) Value Description 0 Unknown 1 Terminal can accept PINs 2 Terminal cannot accept PINs (required value for Debit Bill Payment) 8 Terminal PIN pad is down 9 Reserved for future use Position 4 Fill (NP1) Value Description 0 Unused Version 4.02 Page 183 Last modified August 12, 2009

POS Condition (bit 25) This field contains a code identifying transaction conditions at the point of service. Description 00 Normal transaction of this type 01 Customer not present 02 Unattended customer-operated terminal 03 Merchant suspicious of transaction (or card) 05 Customer present, Card Not Present 06 Preauthorized request completion 07 Telephone device 08 Mail/telephone order 09 Security alert 10 Customer identity verified 11 Suspected fraud 12 Security 15 Customer terminal (home terminal) 51 Card Verification transaction set Amount to 0 52 POS Check transaction 55 Request for telecode verification without authorization 59 E-commerce request (through public network) 71 Card present, magnetic stripe read failed (key entered) Version 4.02 Page 184 Last modified August 12, 2009

POS PIN Capture (bit 26) This field contains a value indicating the maximum number of PIN characters that can be accepted by the point-ofservice device. This field is present if the device cannot accept the standard maximum PIN length of 12. If the field is present, the value must be 00 (unknown or unspecified) or between 04 and 12. Version 4.02 Page 185 Last modified August 12, 2009

Transaction Fee Amount (bit 28) This field contains an acquirer-assessed transaction fee. The fee amount is not included in Transaction Amount (bit 4). The format of the field is: 1-character sign C for credit, D for debit 8-character amount Version 4.02 Page 186 Last modified August 12, 2009

Acquiring Institution ID (bit 32) This field identifies the acquirer of the transaction. The value is constant for all transactions to and from this acquirer and must be equal to 45592900000. Version 4.02 Page 187 Last modified August 12, 2009

Forwarding Institution ID (bit 33) This field identifies the processor that forwards the message to Bank of America Merchant Services, if that processor is different from the acquirer of the transaction. This is a Bank of America Merchant Services-assigned identification number. Version 4.02 Page 188 Last modified August 12, 2009

Track 2 Data (bit 35) This field contains the unaltered contents of the data read off Track 2 of the magnetic stripe, excluding the beginning and ending sentinels and LRC characters. This field is only present when Track 2 has been read or assembled via a contactless means at the terminal. Important note concerning Track 2 Data in Debit Preauth Completion request transactions: This field is listed as optional for inclusion in Debit Preauth Completion requests. At this time, not all authorizing entities support Debit Preauth Completions without Track 2 data. Check with your account representative before sending Debit Preauth Completion transactions without Track 2 data. Version 4.02 Page 189 Last modified August 12, 2009

Retrieval Reference Number (bit 37) This field contains aq number used with other data elements as a key to identify and track all messages related to a given customer transaction or series of system messages. The format for this field is YDDDHHNNNNNN, where: Y is the low-order digit of the year DDD is the three-digit number of the day of the year HH is the two-digit hour NNNNNN is a six-digit transaction number The value must be saved by the recipient of the message and returned in the response to that message. Further, the same value must be used by the message initiator in any related messages. Examples of related messages that must share a common Retrieval Reference Number: Debit request debit response debit reversal request debit reversal response Credit request credit response credit reversal request credit reversal response Debit preauth request debit preauth response debit preauth completion request debit preauth completion response (and any attendant reversals) Network management request network management response (can be intiated by the merchant or Bank of America Merchant Services) Version 4.02 Page 190 Last modified August 12, 2009

Auth ID Response (bit 38) This field contains the authorization code provided by the issuer when a transaction is approved. The field will be present in approved responses, reversal requests and requests for transaction that have previously been approved by another means than through an online Multilink authorization. Version 4.02 Page 191 Last modified August 12, 2009

Response (bit 39) This field contains a code that defines the response to a request. 00 indicates both approval (a positive authorization decision) and acceptance (acknowledgement that a transaction or message was received). Response Info 00 Approved/Completed/Dynamic Key accepted 01 Refer to card issuer for check acceptance transaction, see text reason in bit 48 02 Refer to card issuer, special condition 03 Invalid merchant or service provider 04 Pick up card 05 Do not honor for check acceptance transaction, see text reason in bit 48 06 Error 07 Pick up card, special condition (other than lost/stolen card) 10 Approved for partial amount 11 Approved V.I.P. (debit only) 12 Invalid transaction 13 Invalid amount 14 Invalid account number (no such number) 15 No such issuer 19 Re-enter transaction 21 No action taken (reversal for declined or timed-out transaction) 25 Unable to locate record in file 28 File is temporarily unavailable 39 No credit account 41 Pick up card (lost card) 43 Pick up card (stolen card) 51 Insufficient funds 52 No checking account 53 No savings account 54 Expired card 55 Invalid PIN 57 Transaction not permitted to cardholder 58 Transaction not allowed at terminal (credit only) 61 Exceeds withdrawal amount limit (activity amount limit exceeded), for check acceptance transaction, amount of check exceeds maximum authorization amount 62 Restricted card 63 Security violation 65 Activity count limit exceeded 75 PIN tries exceeded 76 Unable to locate original message 77 Repeat original message or reversal message data inconsistent with original message 79 Already reversed 80 No financial impact (debit/ebt only) 80 Invalid date (credit only) 81 PIN cryptographic error found 82 Incorrect CVV 85 No reason to decline a request for address verification 86 Cannot verify PIN 91 Network unavailable Version 4.02 Page 192 Last modified August 12, 2009

Response (bit 39) (Continued) Response Info 92 Destination cannot be found for routing 93 Transaction cannot be completed; violation of law 96 System malfunction N7 Decline for CVV2 failure R0 Stop payment order (recurring payments) R1 Revoke authorization order (recurring payments) R3 Revoke all authorization orders (recurring payments) Version 4.02 Page 193 Last modified August 12, 2009

Card Acceptor Term ID (bit 41) This field contains a unique, merchant-defined terminal or device ID. Version 4.02 Page 194 Last modified August 12, 2009

Card Acceptor ID (bit 42) This field contains the Bank of America Merchant Services assigned Card Acceptor ID in the following format: Positions Description 1-3 Bank of America Merchant Services assigned merchant ID 4-10 Merchant store number 11 Mod 10 check digit for store number 12-15 Space-filled Version 4.02 Page 195 Last modified August 12, 2009

Card Acceptor Name / Location (bit 43) This field contains the name and location of the card acceptor. This location should be the city and country of the actual location where the transaction occurred. The field is subdivided as follows: Position Description 1-25 Card acceptor name 26-38 Card acceptor city name 39-40 Card acceptor alpha country code* *Card acceptor alpha country codes Country Value Canada CA Guam GU Northern Mariana Islands MP Puerto Rico PR United States US U.S. Virgin Islands VI Version 4.02 Page 196 Last modified August 12, 2009

Additional Response Data (bit 44) This field contains miscellaneous data needed in a response. Unused fields prior to fields that are in use must be present and space-filled. Bit 44.1 Response Source/Reason (AN1) Value Description 0 Advice of Exception File change 1 Response provided by STIP because the request was timed out by Switch 2 Response provided by STIP because the transaction amount was below issuer limit 3 Response provided by STIP because the issuer is in Suppress Inquiries mode 4 Response provided by STIP because issuer not available 5 Response provided by issuer 6 Enhanced STIP reason code provided on behalf of third-party processor 7 Reversal advice provided by VISA to identify a potential duplicate transaction 8 Reversal advice provided by VISA to identify a probable duplicate authorization 9 Enhanced STIP reason code provided by the VISA International Automated Referral Service A Response provided by a third-party authorizing agent (POS Check) Space Field not used Fill for subsequent positions that are present Bit 44.2 Address Verification Result (AN1) Value Description A Address matches, ZIP does not B Address matches, ZIP not verified due to incompatible format C Address and ZIP not verified due to incompatible formats D Street and postal codes match (international) F Street and postal codes match (U. K. only) G Address information not verified for international transaction I Address information not verified for international transaction M Street and postal codes match (international) N No: Neither address or ZIP matches P Postal code match. Street address not verified due to incompatible format R Retry: System unavailable or timed out U Address information unavailable Y Exact: Address and ZIP match Z ZIP matches, address does not Space Field not used Fill for subsequent positions that are present Bit 44.3 Telecode Verification Result (AN1) Value Description Space Field not used Fill for subsequent positions that are present Bit 44.4 Reserved for Future Use (AN1) Value Description Space Field not used Fill for subsequent positions that are present Version 4.02 Page 197 Last modified August 12, 2009

Additional Response Data (bit 44) (Continued) Bit 44.5 CVV/dCVV Results (AN1) Value Description 1 CVV/dCVV failed verification 2 CVV/dCVV passed verification Space CVV/dCVV not verified or fill for subsequent positions that are present Bit 44.6 PACM Diversion Level (AN2) Value Description Space Field not used Fill for subsequent positions that are present Bit 44.7 PACM Diversion Reason (AN1) Value Description Space Field not used Fill for subsequent positions that are present Bit 44.8 Card Authentication Results (AN1) Value Description Space Field not used Fill for subsequent positions that are present Bit 44.9 LAC Response (AN1) Value Description Space Field not used Fill for subsequent positions that are present Bit 44.10 CVV2 Result (AN1) Used for VISA and Diners Club CVV2, MasterCard CVC2, and American Express and Discover CID. Value Description M CVV2 match N CVV2 no match P Not processed S The CVV2 should be on the card, but the merchant indicates it is not Space Field not used Fill for subsequent positions that are present Bit 44.11 Original Response (AN2) Value Description Space Field not used Fill for subsequent positions that are present Bit 44.12 Check Settlement (AN1) Description 1 VISA settlement code 2 ACH settlement code Version 4.02 Page 198 Last modified August 12, 2009

Additional Response Data (bit 44) (Continued) Bit 44.13 Card Authentication Verification Value (CAVV) Results (AN1) Value Description Space CAVV not present 0 CAVV not validated due to erroneous data submitted 1 CAVV failed validation authentication 2 CAVV passed validation authentication 3 CAVV passed validation attempt. A 3-D Secure authentication value of 7 from the issuer s ACS indicates that authentication was attempted. (Determined that the issuer s ACS generated this value from the use of the Issuer s CAVV key[s]) 4 CAVV failed validation attempt. A 3-D Secure authentication value of 7 from the issuer s ACS indicates that authentication was attempted. (Determined that the issuer s ACS generated this value from the use of the Issuer s CAVV key[s]) 5 Not used (reserved for future use) 6 CAVV not validated, issuer not participating in CAVV validation 7 CAVV failed validation attempt. A 3-D Secure authentication value of 7 from VISA s ACS indicates that an authentication attempt was performed. (Determined that the VISA generated this value from the use of VISA s CAVV key[s]) 8 CAVV passed validation attempt. A 3-D Secure authentication value of 7 from VISA s ACS indicates that an authentication attempt was performed. (Determined that the VISA generated this value from the use of VISA s CAVV key[s]) 9 CAVV failed validation attempt. A 3-D Secure authentication value of 8 from VISA s ACS indicates that authentication attempt was performed when the issuer s ACS was not available. (Determined that VISA generated this value from the use of the VISA CAVV key[s]) A CAVV passed validation attempt. A 3-D Secure authentication value of 8 from VISA s ACS indicates that authentication attempt was performed when the issuer s ACS was not available. (Determined that VISA generated this value from the use of the VISA CAVV key[s]) B CAVV passed validation information only, no liability shift. When the ECI equals 7 and CAVV is present, the CAVV will be validated but no liability shift will occur. VISA will generate this value for card or transaction types that are not eligible for the 3-D Secure service C CAVV was not validated attempt. The issuer did not return a CAVV results code in the authorization response D CAVV was not validated authentication. The issuer did not return a CAVV results code in the authorization response Version 4.02 Page 199 Last modified August 12, 2009

Track 1 Data (bit 45) This field contains the unaltered contents of the data read off Track 1 of the magnetic stripe, excluding the beginning and ending sentinels and LRC chanracters. This field is only present when Track 1 has been read at the terminal. Version 4.02 Page 200 Last modified August 12, 2009

Additional Data Private (bit 48) This field has multiple uses. Each use is designated by a field identifier. Currently supported uses are: Check Acceptance Request Check Acceptance Response Commercial Card Type Request Dynamic Key Exchange Working Key Check Value POS Check Check Acceptance Request (usage 6) This usage is the mechanism for providing the check acceptance information, such as driver s license, employee ID, raw MICR data, etc.. The field consists of several tagged subfields which are defined below. Each of these subfields begin with a two-character subfield data type followed by a 3 character numeric subfield length followed by the variable length subfield content. This is called TLV format. The maximum length of the field is 255 characters. Important note: See Appendix D for tips on proper TLV-format coding. Data Type Identifier Length Contents AB Fixed 9 characters Routing Transit Number AN Variable maximum 19 characters Customer deposit account number CA Variable maximum 30 Check writer address characters CI Variable maximum 40 characters Customer Identification (see table below for Customer Identification values). Field is formatted as follows: CI999xxdddd where 999 is the length of the data contents including the xx type, xx is the identification type (from table below) and dddd is the identification data. CK Variable maximum 10 Check serial number characters CM Variable maximum 15 characters CN Variable maximum 30 characters Merchant ID for the selected check acceptance provider. This ID is assigned by the check acceptance provider. (See note below regarding default values for this data item.) Check writer name Version 4.02 Page 201 Last modified August 12, 2009

Additional Data Private (bit 48) (Continued) Data Type Identifier Length Contents CP Variable maximum 2 characters Check acceptance provider: 01 = Telecheck 02 = Certegy 03 = Certegy 04 = JBS 05 = ECHO 06 = BankServ 07 = E-Funds (See note following table regarding default values for this data item.) (Note: MultiLink only supports Telecheck at this time) CT Fixed 1 character Type of check submitted: P personal C company X Travelers Check S Payroll M Cash T Two party check G Government check DB Fixed 6 characters Customer Date of birth MMDDYY EN Variable maximum 10 Employee ID number characters PH Fixed 10 characters Check writer phone number RM Variable maximum 55 characters Raw MICR data As an example, the following data represents valid contents of field 48 for a check acceptance request using a customer s driver s license as the method of identification and passing raw MICR as read from the check reader: <length>@mci01540r961365264998db006030965rm027t0123456780t1234567890o0101 The <length> is a one character binary field that would have a value of 65 (hex 41) representing the overall length of the data that follows. The first two characters of the data ( @M ) represent the field identifier, indicating that check acceptance data follows. Following that is a series of tagged data elements. The first is the data type of CI (customer identification). The data type indicator is followed by a 3 character numeric length 015 that represents the length of the data field that immediately follows. For the data type CI the first two characters of the data field indicate the identification type (see following tables of identification types). In this example, those two characters are 40 indicating a Michigan driver s license. The rest of the field contains the actual identification data (i.e. the driver s license identification R961365264998 ). The next field in the stream contains the data type of DB (date of birth) followed by the length of the data 006 followed by the actual date of birth data. The last subfield in the example is data type RM (raw micr) with a length of 027 followed by twenty-seven characters as read from the MICR check reader device. ** Note: Bank of America Merchant Services has the ability to associate the check service provider (CP) and check service merchant ID (CM) values for each merchant ID associated with a particular merchant interface process. If this is configured then there is no requirement to send this information on the request. If, however, the CP and CM fields are sent on the request they will override any values configured for that retailer at Bank of America Merchant Services. Version 4.02 Page 202 Last modified August 12, 2009

Additional Data Private (bit 48) (Continued) Customer Identification Tables US Driver s License Table 25 Alabama 52 Louisiana 65 Oklahoma 55 Alaska 56 Maine 67 Oregon 27 Arkansas 79 Maryland 78 Pennsylvania 20 Arizona 87 Massachusetts 70 Puerto Rico 23 California 40 Michigan 74 Rhode Island 26 Colorado 64 Minnesota 72 South Carolina 28 Connecticut 77 Mississippi 73 South Dakota 93 Dist. Of Columbia 66 Missouri 86 Tennesee 33 Delaware 68 Montana 89 Texas 35 Florida 63 Nebraska 88 Utah 42 Georgia 38 Nevada 83 Vermont 44 Hawaii 47 New Hampshire 82 Virginia 43 Idaho 53 New Jersey 92 Washington 45 Illinois 39 New Mexico 98 West Virginia 46 Indiana 69 New York 94 Wisconsin 49 Iowa 75 North Carolina 99 Wyoming 57 Kansas 36 North Dakota 59 Kentucky 60 Ohio Canadian Driver s License Table 21 Alberta 31 Newfoundland 81 Prince Edward Island 54 British Columbia 37 Northwest Territories 71 Quebec 61 Manitoba 41 Nova Scotia 58 Saskatchewan 95 New Brunswick 51 Ontario 91 Yukon Other ID types GV US Government ID ML US Military ID CG Canadian Government ID NOTE: ID strings can contain letters, digits, and asterisks (*). Spaces and dashes should be ignored (not entered). Check Acceptance Response (usage 6) On a check acceptance response field 48 (if present) contains the text that should be displayed at the point-of-sale terminal. For authorized responses this text will generally be *APPROVAL. For declines this text will contain the reason for the decline. The following are examples of the content for F48 on a check acceptance response: *APPROVAL *CODE 4 John Rejected *Error Retry *Call Center *LOST/STOLEN John B. Stealing *CODE 3 John Don t Know *CODE 47 John Not Approved *CODE 4 *STORE NOT ACTIVE Version 4.02 Page 203 Last modified August 12, 2009

Additional Data Private (bit 48) (Continued) Commercial Card Type Request (usage 11) This usage requests/returns the type of VISA commercial purchasing card being used at the point of sale or service. The field consists of a one-byte length and two subfields: field identifier (ANS3) and Commercial Card type request/response (ANS1). Field identifier =!01 (length = 3) Commercial Card type (length = 1) (overall field length = 4) Field identifier value =!01 in request and response. Commercial Card type request/response value Value Description 0 Value sent in request; returned if not commercial card or if transaction not approved B Business card R Corporate card S Purchasing card Dynamic Key Exchange Working Key Check Value (usage 14) This usage holds the 4-digit check value to verify the receipt of a new working key. The field consists of a one-byte length and two subfields: field identifier (ANS1) and Working Key Check Digits (ANS4). Field identifier = & (length = 1) Working Key Check Digits (length = 4) (overall length = 5) Field identifier value = & Working Key Check Digits = The first four hexadecimal digits of the output resulting from encrypting zeros with the newly issued key in Field 96 Message Security. POS Check usage This usage is provided to enable merchants and third-party authorizers to exchange information specific to their participation in the POS Check Service. For example, if the service option is Guarantee with Conversion and the drawee financial institution does not support it, information in bit 48 contains data that goes to the third-party authorizing agent, to support all three service types. Merchants and acquirers may submit any combination of subfields in bit 48, within the defined maximum length, when originating requests. Following the field identifier, subfields may appear in any order within bit 48. The format of data subfields is xx999d-d, where xx is the subfield identifier (called a tag), 999 is the subfield length (always 3 digits, regardless of value) and d-d is the data. This is called TLV format. Important note: See Appendix D for tips on proper TLV-format coding. Field Name Positions Data Content Usage Bit 48 Additional Data 1-255 Variable, depending on requirements of authorizing agents Depends on the requirements of participating merchants, acquirers and third-party authorizing agents. Length 1 Contains the length of the data contents in the entire field. Version 4.02 Page 204 Last modified August 12, 2009

Additional Data Private (bit 48) (Continued) POS Check usage (Continued) Field Name Positions Data Content Usage Field Identifier 2-3 $V Identifies use of the field as POS Check. Following the field identifier, subfields may appear in any order within bit 48. Callback Information Any CI999d-d Contains non-bank authorizer name, address and customer service telephone number. The field is returned only by nonbank authorizers on declines of original requests. Format for data must be: name/address/telephone number. Street, city, state and ZIP must be separated by a back slash (\), with a space between street name and number. The format for telephone number must be AAANNNNNNN, where the first three positions are the area code, followed by the 7-digit local number. Date of Birth Any DB999d-d Identifies a date of birth. Date format must be mmddccyy, where mm = month, dd = day, cc = century and yy = year. Dial Terminal Identification Information Any DT999@d-d Identifies a dial terminal. @ represents a terminal information flag and is included in the length of the data field. Free Format Text Any FX999d-d Identifies free format text, where 999 = length of associated data field, and d-d = data content. The length designator must always be three numeric characters. ID Type and Number Any IC999d-d Identifies the type and number of the customer identification presented at the point of sale. This field may be repeated as often as necessary, if information from multiple ID types is captured at the point of sale. The first two data positions in this field must be a valid state code, ID type or state abbreviation as listed in the Bit 48 POS Check U.S. State s and Abbreviations table (which follows this table). If the value in the first two data positions is a valid state code or state abbreviation, then the number following it must be either a valid driver s license number or State ID. If the value in the first two data positions is a valid ID type, then the number following it must correspond to the ID type presented. Proprietary Response Information Any RC999d-d Identifies proprietary response information defined by an authorizing agent. Receipt Information Any RP999d-d Identifies customer receipt information. Reference Number Any RN999d-d Identifies a reference number of any type. Version 4.02 Page 205 Last modified August 12, 2009

Additional Data Private (bit 48) (Continued) POS Check usage (Continued) Field Name Positions Data Content Usage Telephone Number Any PH999d-d Identifies a telephone number. Number format must be AAANNNN, where the first three positions are the area code, followed by the 7-digit local number. Bit 48 POS Check U.S. State s and Abbreviations State Name State State Abbreviation State Name State State Abbreviation Alabama 01 AL New Hampshire 33 NH Alaska 02 AK New Jersey 34 NJ Arizona 04 AZ New Mexico 35 NM Arkansas 05 AR New York 36 NY California 06 CA North Carolina 37 NC Colorado 08 CO North Dakota 38 ND Connecticut 09 CT Ohio 39 OH Delaware 10 DE Oklahoma 40 OK District of Columbia 11 DC Oregon 41 OR Florida 12 FL Pennsylvania 42 PA Georgia 13 GA Rhode Island 44 RI Hawaii 15 HI South Carolina 45 SC Idaho 16 ID South Dakota 46 SD Illinois 17 IL Tennessee 47 TN Indiana 18 IN Texas 48 TX Iowa 19 IA Utah 49 UT Kansas 20 KS Vermont 50 VT Kentucky 21 KY Virginia 51 VA Louisiana 22 LA Washington 53 WA Maine 23 ME West Virginia 54 WV Maryland 24 MD Wisconsin 55 WI Massachusettes 25 MA Wyoming 56 WY Michigan 26 MI Courtesy Card 90 N/A Minnesota 27 MN Military ID 91 N/A Mississippi 28 MS Social Securtity 92 N/A Number Missouri 29 MO Proprietary Card 93 N/A Montana 30 MT Puerto Rico 99 PR Nebraska 31 NE U.S. military base, 99 N/A embassy, traveling merchant Nevada 32 NV Version 4.02 Page 206 Last modified August 12, 2009

Transaction Currency (bit 49) An ISO defined code representing the currency of this transaction. Supported currencies are: Country Value Canada 124 United States 840 Version 4.02 Page 207 Last modified August 12, 2009

PIN Data (bit 52) This field is only present if a PIN is being sent. If a 16-character PIN block is used, this field contains those 16 hexadecimal digits. If a DUKPT key is used, this field contains the Expanded Encrypted PIN block data as 16 hexadecimal digits. Additional DUKPT data is sent in bits 53 and 127. Version 4.02 Page 208 Last modified August 12, 2009

Security-Related Control Information (bit 53) This field is divided into the following subfields: Description Positions 1 & 2 Security Format (NP2) 20 Zone encryption Positions 3 & 4 PIN Encryption Algorithm Identifier (NP2) 01 ANSI DES 02 DUKPT Positions 5 & 6 PIN Block Format (NP2) 00 Derived unique key expanded encrypted PIN block data (DUKPT). 01 Format is based on the PIN, the PIN length, selected rightmost digits of the account number, and the pad characters 0 and F, combined through an exclusive OR operation. Positions 7 & 8 PIN Zone Key Index (NP2) 00 DUKPT. 01 Working key 1 is to be used (ANSI DES) Positions 9 & 10 describes the use of field 52 (NP2) 00 PIN is present in Field 52. Positions 11 through 16 future use (NP6) 000000 Future use Version 4.02 Page 209 Last modified August 12, 2009

Additional Amount (bit 54) Positions 1 & 2 Type of account affected (ANS2) Account Description 00 Not specified 10 Savings 20 Checking 30 Credit Card 40 Universal Account 96 EBT Cash Benefit Account 98 EBT Food Stamp Account Positions 3 & 4 Type of amount represented (ANS2) Amount Description Present in Request Present in Response 00 Unspecified amount N Y 01 Debit/EBT Account Ledger Balance or Credit Amount remaining N Y for Customer (Open to Buy) 02 Debit/EBT Account Available Balance or Credit Account Limit N Y 18 Account Beginning Balance N Y 40 Amount cashback N Y 4S Amount Healthcare Y N 4U Amount Prescription/Rx Y N 4V Amount Vision/Optical Y N 4W Amount Clinic/Other Qualified Medical Y N 4X Amount Dental Y N 53 Original cashback amount N Y 57 Original amount N Y Positions 5-7 (ANS3) represent the currency code (US, which is 840 ) Position 8 (ANS1) indicates a credit (C) or debit (D) balance. Positions 9-20 (ANS12) represent the amount. These strings of data can be repeated up to 6 times within this single field. See each specific transaction type for examples. EBT Transactions This field is used to represent subsets of amount 1 (bit 4). In addition to the amount, this field contains the account type and amount type. An example containing a cash benefit account balance and a food stamp account balance: 9600840C0000000052839802840C000000014311 (total length = 40) 96 = EBT Cash Benefit Account 00 = Unspecified amount 840 = US currency C = Credit balance 000000005283 = $52.83 98 = EBT Food Stamp Account Version 4.02 Page 210 Last modified August 12, 2009

Additional Amount (bit 54) (Continued) 02 = EBT Available balance 840 = US currency C = Credit balance 000000014311 = $143.11 Credit Healthcare Auto-Substantiation Purchase This field is required in Auto-Substantiation requests and must contain at least an entry for amount type 4S (Amount Healthcare). The amount sent for amount type 4S represents the total of all the various classes of healthcare purchases (Prescription/Rx 4U; Vision/Optical 4V; Clinic/Other Qualified Medical 4W; Dental 4X; and Over- The-Counter, for which there is no designation or separate entry). The merchant may, at their option, additionally send entries for Prescription/Rx, Vision/Optical, Clinic/Other Qualified Medical and/or Dental. The total of these amount, plus any Over-The-Counter healthcare purchases will be equal the amount associated with the Amount Healthcare entry. The account type in all cases will be 00 Not Specified. An example of a request containing only the Amount Healthcare: 004S840C000000006793 (total length = 20) 00 = Unspecified account (only valid value) 4S = Amount Healthcare 840 = US currency C = Credit amount 000000006793 = $67.93 (total of all healthcare purchase, including any over-the-counter) An example of a request containing multiple amounts: 004S840C000000016458004U840C000000009209004V840C000000003977 (total length = 60) 00 = Unspecified acoount (only valid value) 4S = Amount Healthcare 840 = US currency C = Credit amount 000000016458 = $164.58 (total of all healthcare purchase, including any over-the-counter) 00 = Unspecified account (only valid value) 4U = Amount Prescription/Rx 840 = US currency C = Credit amount 000000009209 = $92.09 (total of all prescription/rx purchase) 00 = Unspecified account (only valid value) 4V = Amount Vision/Optical 840 = US currency C = Credit amount 000000003977 = $39.77 (total of all vision/optical purchase) Note: In this example, the sum of prescription/rx and vision/optical ($131.86) is less than the Amount Healthcare value ($164.58). The difference ($32.72) is the amount of over-the-counter healthcare purchase. Please refer to the Inventory Information Approval System (IIAS) specifications (available from the IIAS Standards Committee Hannaford Bros. Co.) for additional details and examples. Note: Merchants utilizing Healthcare Auto-Substantiation should be IIAS-certified and must indicate this by sending a value of M in Merchant-Specific Data Indicator (bit 62.4). If they are not IIAS-certified, they should not send bit 62.4. Version 4.02 Page 211 Last modified August 12, 2009

Transactions Involving Partial Authorization This field can be sent in responses from issuers when the merchant has indicated that their device can support partial authorizations, the issuer also supports partial authorizations and the full amount of the transaction is not available. The issuer can respond with 10 in bit 39 and place the authorized amount in bit 4. The original requested amount will appear in bit 54. An example containing only the originally-requested amount: 2057840C000000005000 (total length = 20) 20 = Checking account 57 = Original amount 840 = US currency C = Credit amount 000000005000 = $50.00 (from bit 4 in request) An example containing originally-requested amount and balances: 2057840C0000000045002001840C0000003629432002840C000000000000 (total length = 60) 20 = Checking account 57 = Original amount 840 = US currency C = Credit amount 000000004500 = $50.00 (from bit 4 in request) 20 = Checking account 01 = Debit ledger balance 840 = US currency C = Credit amount 000000362943 = $3,629.43 20 = Checking account 02 = Debit available balance 840 = US currency C = Credit amount 000000000000 = $0.00 Debit and Credit Balance Inquiries This field contains one or more balances returned by the issuer. An example: 3001840C0000000150003002840C000000500000 (total length = 40) 30 = Credit card account 01 = Credit amount remaining for customer (open to buy) 840 = US currency Version 4.02 Page 212 Last modified August 12, 2009

Additional Amount (bit 54) (Continued) C = Credit amount 000000015000 = $150.00 30 Credit card account 02 = Credit account limit 840 = US currency C = Credit amount 000000500000 = $5,000.00 Debit and Credit Financial Transactions If the merchant has indicated a desire for balances to be returned on financial transactions (see bit 60.10), this field may contain one or more balances returned by the issuer. An example: 0000840C000001438234 (total length = 20) 00 = Unspecified account 00 = Unspecified amount 840 = US currency C = Credit amount 000001438234 = $14,382.34 Please note: It is possible for multiple occurrences of the subfields to exist in a transaction. For example, the merchant indicates support for partial authorizations and for balances to be returned on a financial transaction. On a given purchase, the full requested amount is not available, so the approved amount is returned in bit 4 and the original requested amount is returned in one set of subfields of bit 54. In addition, the issuer chooses to return a ledger balance for the account in another set of bit 54 subfields. The merchant should be prepared to receive up to 6 sets of bit 54 subfields (120 bytes) whenever the field is present. Version 4.02 Page 213 Last modified August 12, 2009

EM and Chip Data (bit 55) This field may contain integrated circuit card (ICC)-related data that is transmitted from the ICC to the card issuer and from the card issuer to the ICC. It may also contain Electronic Magnetic Signature (EM) data captured at specially equipped reader heads that generate a signature based on the unique fingerprint of the magnetic stripe. The usage is defined by the Dataset ID. The field can contain multiple pieces of data. The format of the field is referred to as TLV (Tag, Length, Value). Each of these is identified by a tag, which is defined below. Important note: See Appendix D for tips on proper TLV-format coding. Note: At this time, the only use implemented for bit 55 is for Electronic Magnetic Signature (EM) data. Dataset Dataset Dataset Elements ID Length Tag 1 Length 1 Value 1 Tag x Length x Value x 1 byte 1 byte 1 or 2 bytes 1 byte 1-252 bytes 1 or 2 bytes 1 byte 1 252 bytes Byte 1 Byte 2 Byte 3 Byte 4 (or 5) Bytes 5 to n (or 6 to n) Byte n+1 Byte n+2 (or n+3) Byte n+3 to z (or n+4 to z) For Electronic Magnetic Signature ID, there will be a single set of Tag, Length and Value. All data is in hexadecimal. Dataset ID: x 56 Dataset Length (length of the data following this field): x 43 Dataset Elements: Tag 1: x 9F52 (two-byte tag) Length 1: x 40 Value 1: 64 hexadecimal bytes (128 characters) of data Example Electronic Magnetic Signature entry (all data is in hexadecimal): 56439F52400123456789ABCDEFFEDCBA987654321000112233445566778899AABBCCDDEEFF0123456789AB CDEFFEDCBA987654321000112233445566778899AABBCCDDEEFF Version 4.02 Page 214 Last modified August 12, 2009

National POS Geographic Data (bit 59) Used to define the geographic location of the POS device or other transaction site. Only present if the transaction site is in the U.S. or Canada. Positions 1 & 2 (ANS2) State/Province State/Province Alabama 01 New York 36 Alaska 02 North Carolina 37 Arizona 04 North Dakota 38 Arkansas 05 Ohio 39 California 06 Oklahoma 40 Colorado 08 Oregon 41 Connecticut 09 Pennsylvania 42 Delaware 10 Rhode Island 44 District of Columbia 11 South Carolina 45 Florida 12 South Dakota 46 Georgia 13 Tennessee 47 Hawaii 15 Texas 48 Idaho 16 Utah 49 Illinois 17 Vermont 50 Indiana 18 Virginia 51 Iowa 19 Washington 53 Kansas 20 West Virginia 54 Kentucky 21 Wisconsin 55 Louisiana 22 Wyoming 56 Maine 23 Alberta 60 Maryland 24 British Columbia 61 Massachusetts 25 Manitoba 62 Michigan 26 New Brunswick 63 Minnesota 27 Newfoundland 64 Mississippi 28 Northwest Territories 65 Missouri 29 Nova Scotia 66 Montana 30 Nunavut 72 Nebraska 31 Ontario 67 Nevada 32 Prince Edward Island 68 New Hampshire 33 Quebec 69 New Jersey 34 Saskatchewan 70 New Mexico 35 Yukon 71 Positions 3-5 contain the county code and are zero-filled. Positions 6-10, 6-11 or 6-14 contain the POS location zip code, depending on whether a 5- or 9-digit US ZIP code or 6- or 9-digit Canadian Postal is present. Send only the actual number of characters in the zip code (no padding). For instance, if the US 5-digit ZIP code is present, send only 5 characters for this subfield and 10 characters for the entire field. Version 4.02 Page 215 Last modified August 12, 2009

Additional POS Information (bit 60) This field is defined to contain additional point-of-sale or point-of-service information. A variable number of subfields follow the length subfield. Unused subfields that precede used subfields should contain zero. Also, if subfield 60.3, 60.6 or 60.9 is the last used subfield, the next following subfield must be included with a value of zero to fill the last byte. Length Position 1 Position 2 Position 3 Position 4 Position 5-6 60.2 Terminal 60.3 Chip 60.5 Merchant Entry Capability Condition Group Indicator 60.1 Terminal Type 60.4 Special Condition Indicator Existing Debt Byte 1 Byte 2 Byte 3 Byte 4 Position 7 Position 8 Position 9-10 Position 11 Position 12 60.6 Chip Transaction Indicator 60.7 Chip Authentication Reliability Indicator 60.8 Mail Order / Telephone Order / Electronic Commerce 60.9 Cardholder ID Method 60.10 Partial Authorization / Balance Indicator Indicator Byte 5 Byte 6 Byte 7 Bit 60.1 Terminal Type (NP1) Value Description 0 Unspecified; or Mail Order and Internet (POS Check only); or fill for subsequent positions that are present 1 Limited amount terminal 2 Unattended terminal (ATM) 3 Unattended terminal; Automated dispensing machine or self-service terminal 4 Electronic cash register 5 Customer-owned device (including personal computers, personal digital assistants, interactive televisions and telephones) 7 Merchant-owned device (including VRUs, Call Centers, etc.) 8 Reserved 9 Cardholder-activated terminal level 4 Bit 60.2 Terminal Entry Capability (NP1) Value Description 0 Unknown; or Mail Order and Telephone Order (POS Check only); or fill for subsequent positions that are present 1 Terminal not used; or Internet (POS Check only) 2 Magnetic stripe read capability 3 Bar code read capability 4 OCR read capability 5 Chip read capability 6 MICR read capability 7 MICR read and image-capable 8 Proximity read capability (for contactless payments transactions) 9 Terminal does not read card data; or POS key-entry (POS Check only) Version 4.02 Page 216 Last modified August 12, 2009

Additional POS Information (bit 60) (Continued) Bit 60.3 Chip Condition (NP1) Value Description 0 Service does not begin with 2 or 6; or fill for subsequent positions that are present 1 Service code begins with 2 or 6; last read at the chip capable terminal was successful, or was not a chip transaction, or unknown 2 Service code begins with 2 or 6; last transaction at the chip capable terminal was an unsuccessful chip read Bit 60.4 Special Condition Indicator Existing Debt (NP1) Value Description 0 Default value; or fill for subsequent positions that are present, or if subfield 60.3 is last subfield used 9 Existing debt indicator not currently used Bit 60.5 Merchant Group Indicator (NP2) This field is currently not used. Fill with zero only if subsequent positions are used. Value Description 00 Fill for subsequent positions that are present Bit 60.6 Chip Transaction Indicator (NP1) Value Description 0 Non-VSDC transaction; or fill for subsequent positions that are present 1 The acquirer identified transaction as a VSDC transaction Bit 60.7 Chip Authentication Reliability Indicator (NP1) Value Description 0 Fill for subsequent positions that are present, or if 60.6 is last subfield used 1 Acquirer indicates that Card Authentication may not be reliable Bit 60.8 Mail Order/Telephone Order/Electronic Commerce Indicator (NP2) Value Description 00 Fill for subsequent positions that are present 01 Telephone order 02 Recurring transaction 03 Installment payment 04 Mail order 05 Secure electronic commerce transaction 06 Non-authenticated security transaction at a 3-D Secure-capable merchant, and merchant attempted to authenticate the cardholder using 3-D Secure (an electronic commerce transaction that has been authenticated using an authentication method) 07 Non-authenticated Security Transaction (an electronic commerce transaction that uses data encryption for security but is not authenticated using 3-D Secure (a.k.a. Verified by VISA) 08 Non-secure transaction (an electronic commerce transaction that uses data encryption for security but is not authenticated using an authentication method) 09 Non-authenticated security transaction at a SET-capable merchant (an electronic commerce transaction that has no data protection) Version 4.02 Page 217 Last modified August 12, 2009

Additional POS Information (bit 60) (Continued) Bit 60.8 Mail Order/Telephone Order/Electronic Commerce Indicator (NP2) (continued) Value Description 98 Subscription transaction 99 Live agent Bit 60.9 Cardholder ID Method (NP1) Value Description 0 Unknown 1 Signature 2 PIN 3 Unattended terminal 4 Mail/Phone order Bit 60.10 Partial Authorization / Balance Indicator (NP1) Value Description 0 Device does not support partial authorizations; balances on credit/debit financial transactions not desired; OR pad if 60.9 is last subfield used 1 Device supports partial authorizations; balances desired on credit/debit financial transactions 2 Device does not support partial authorizations; balances on credit/debit financial transactions desired If the merchant indicates that the device supports partial authorizations, issuers that support partial authorizations can respond with field 39 = 10 (partial approval) to indicate that partial amount approval was provided. The approved amount is in field 4 of the response. The original amount is in field 54. If the merchant indicates a desire for balances on credit/debit financial transactions, and the issuer returns one or more balances, these balances will be provided in bit 54 (Additional Amounts), along with any qualifying information (account type, balance type). It is entirely up to the issuer whether any balance information is returned. If the value of 60.10 would be zero (the merchant s device does not support partial authorizations and no balances are desired) and bit 60.9 does not need to be sent in the message, bit 60.10 also does not need to be sent. Version 4.02 Page 218 Last modified August 12, 2009

Other Transaction Amount (bit 61.1) This field contains the cash back amount. No decimal point appears in the field. Two decimal places are assumed. This amount is also included in the Transaction Amount (bit 4). Version 4.02 Page 219 Last modified August 12, 2009

Payment Service Fields (bit 62) A private-use field used for VISA Custom Payment Services (CPS) and MasterCard Interchange Compliance programs. Bit 62.0 Bit Map (B8) This subfield indicates the presence of Payment Service Fields subfields that follow. If any data fields are present, the entire bit map must be present. Note: the bit map provides support for up to 64 subfields, although fewer than that are supported at this time. Example: Subfield Authorizations Characteristics (bit 62.1) is needed. The bit 62.0 Bit Map would appear as follows in hexadecimal representation: 8000000000000000 and like this in binary representation (spaces included only for readability): 1000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 Bit 62.1 Authorizations Characteristics (AN1) Value Sent on Received Description Request? on Response? A No Yes Card present; magnetic stripe read or stripe not included but other submission requirements met; signature obtained; CVV requested if magnetic stripe present C No Yes Meets requirements for A, plus merchant name, location present, and cardholder-activated terminal indicator set; but no signature required E No Yes Meets requirements for A, plus merchant owner name and location present F No Yes Meets CPS/Account Funding requirements. K No Yes Card present with key entry M No Yes Meets national payment service requirements with no address verification N No Yes Not qualified P No Yes Card not present; preferred customer participation requested R Yes Yes Indicates recurring or installment payment (no response R returned in response) S No Yes Meets requirements for E-Commerce 3-D Secure attempt transaction. U No Yes Meets basic CPS/E-Commerce requirements and 3-D Secure CAVV data is present. V No Yes Meets address verification requirements; verification requested for Card Not Present transactions W No Yes Meets basic CPS/E-Commerce requirements but transmission was nonverified 3-D Secure CAVV transmission. Y Yes Conditional In Request, indicates that an Authorizations Characteristics response is desired. If present in Response, indicates that an Authorizations Characteristics response was not applicable. Bit 62.2 Transaction Identifier (NP15) This field contains an issuer-generated identifier unique for each original transaction. Version 4.02 Page 220 Last modified August 12, 2009

Payment Service Fields (bit 62) (Continued) Bit 62.3 Validation (AN4) This field contains a code calculated to ensure that key fields in the authorization message match their respective fields in the deferred clearing message. Bit 62.4 Market-Specific Data Identifier (AN1) This subfield identifies the industry for which market-specific data has been provided. Value A B E H M N Description Auto rental Bill payment Electronic Commerce transaction aggregation Hotel IIAS-certified (Healthcare only) Not IIAS-certified (Returned in healthcare responses only), Not eligible for aggregation (Returned in Electronic Commerce aggregation transactions only) Bit 62.17 MasterCard Compliance Info (AN15) This field contains qualification information for the MasterCard Interchange Compliance program. The format of the field is MMDDRRRRRRRRRBB, where: MM is the two-digit month DD is the two-digit day RRRRRRRRR is the nine-digit BankNet Reference Number BB is two spaces When sent in MasterCard Private Label Advice Request messages, RRRRRRRRR is reformatted to PPP999999, where: PPP is the three-character Private Label BIN participated in 999999 is a literal 6 9s Bit 62.23 Card Results (AN2) This subfield indicates the card program that the card used in the transaction is signed up for. Byte 1 Byte 2 Description Value Value A Space VISA Traditional A X American Express B Space VISA Traditional Rewards C Space VISA Signature D Space VISA Signature Preferred D I Discover E Space Reserved F Space Reserved G Space VISA Business G 1 VISA Signature Business G 2 VISA Business Check Card H Space VISA Check Card I Space VISA Commerce Version 4.02 Page 221 Last modified August 12, 2009

Payment Service Fields (bit 62) (Continued) Byte 1 Byte 2 Description Value Value J Space Reserved J 1 VISA General Prepaid J 2 VISA Prepaid Gift J 3 VISA Prepaid Healthcare J 4 VISA Prepaid Commercial K Space VISA Corporate K 1 VISA GSA Corporate T & E L Space Reserved M Space MasterCard/EuroCard and Diners N Space Reserved O Space Reserved P Space Reserved Q Space Private Label Q 1 Private Label Prepaid R Space Proprietary S Space VISA Purchasing S 1 VISA Purchasing with Fleet S 2 VISA GSA Purchasing S 3 VISA GSA Purchasing with Fleet T Space Reserved/Interlink U Space VISA TravelMoney V Space Reserved The values listed in the above table are determined by VISA. Others may be added at any time. The merchant should be able to accept any alphanumeric value in this field. VISA returns these values for U.S. cards only. Version 4.02 Page 222 Last modified August 12, 2009

Private-Use Field (bit 63) Bit 63.0 Bit Map (B3) This subfield indicates the presence of Private Use Fields subfields that follow. If any data fields are present, the entire bit map must be present. Note: the bit map provides support for up to 24 subfields, although fewer than that are supported at this time. Example: Subfields Network ID (bit 63.1) and Message Reason (bit 63.3) are needed. The bit 63.0 Bit Map would appear as follows in hexadecimal representation: A00000 and like this in binary representation (spaces included only for readability): 1010 0000 0000 0000 0000 0000 Bit 63.1 Network ID (NP4) 0000 is sent in the request and/or reversal. The value indicating the network actually used for authorization is returned in this field in the response. Description 0000 Priority routing (Bank of America Merchant Services determines the network and program rules) only valid value in request (0200) and reversal (0400) message 0001 Interlink 0002 Money Station 0003 Star West 0004 Maestro 0005 Magic Line 0006 Star Northeast 0007 NYCE 0008 Pulse 0009 Star Southeast 0010 Accel 0011 TYME 0012 MOST 0014 Shazam 0015 Honor West 0016 Cash Station 0017 Gulfnet 0018 Access24 0023 Alert 0024 Alaska Option 0025 Banco Popular 0026 AFFN 0090 Interlink Direct 0091 Star West Direct 0092 Star Southeast Direct 0093 Star Northeast Direct 0094 NYCE Direct 0095 Pulse Direct 0096 Banco Popular Direct Version 4.02 Page 223 Last modified August 12, 2009

Private Use Fields (bit 63) (Continued) Bit 63.1 Network ID (Continued) Description 0097 Maestro Direct 0129 QUEST EBT 0152 Deluxe EBT (San Bernadino and San Diego Counties CA) 0153 Northrup Grumman (Texas) 0157 CITI (North Dakota/South Dakota) 0160 DXI EBT 0162 Northrup Grumman (Illinois) 0163 Shazam EBT 0164 Northeast Coalition of States (NCS) EBT 0165 Western States (WSEA) EBT 0166 Southeast Coalition of States (SAS) EBT 0167 Lockheed EBT 0169 EDS Direct through MultiLink 0175 Deluxe EBT (Sacramento CA) 0179 EBT (AR, IA, MA, ME, MS, NJ) 0182 EDS EBT 0196 Banco Popular EBT Bit 63.2 Preauth Time Limit (NP4) This field contains the time (in hours) the issuer agrees to hold funds for an acquirer. Bit 63.3 Message Reason (NP4) Description 2501 Transaction voided by customer 2502 Transaction has not completed 2503 No confirmation from point of service 2547 Potential duplicate 2548 Duplicate 5202 Online submission 5204 Online resubmission Bit 63.6 Chargeback Reduction Base II Flags (ANS7) This field contains seven indicators used to assist in the effort to reduce chargebacks. The subfields are: Position 1 2 3 4 5 6 7 Floor limit CRB STIP Mail/Phone/E- Special Special Condition Commerce Chargeback RIS Merchant Descriptions and values for the subfields are: Position 1, Floor Limit Indicator: This subfield describes the relationship of the transaction amount to the floor limit in effect for that transaction. Value = space. Position 2, CRB Indicator: This subfield describes whether the account number was listed in a Card Recovery Bulletin that was in effect for the merchant location on the purchase date. Value = space. Version 4.02 Page 224 Last modified August 12, 2009

Private Use Field (bit 63) (Continued) Position 3, STIP Indicator: This subfield indicates that the authorization code (if any) was not generated by STIP. Value = space. Position 4, Mail/Phone/Electronic Commerce Indicator: This subfield distinguishes the type of mail or telephone order, or indicates the security level of an electronic commerce transaction. Value Description Space POS customer present * 1 Telephone order * 2 Recurring transaction 3 Installment payment 4 Mail order * 5 Secure electronic commerce transaction 6 Non-authenticated security transaction at a 3-D capable merchant, and merchant attempted to authenticate with cardholder using 3-D secure. 7 Non-authenticated security transaction 8 Internet/Non-secure transaction * 9 Non-authenticated security transaction at a SET-capable merchant A Live agent 126. Please note: the only valid values for POS Check transactions are Space, 1, 4 and 8. Position 5, Special Chargeback Indicator: This subfield supplies extra information regarding chargebacks validation requests and advices). Value = space. Position 6, Special Condition Indicator, RIS: This subfield supports the Risk Identification Service (RIS) and must be placed in transactions when a merchant has been identified as highly suspect. Value = space. Position 7, Special Condition Indicator, Merchant: This subfield describes selected special conditions at the point of sale. Value = space. Bit 63.11 Reimbursement Attribute (ANS1) Description 0 Standard Issuer s/interchange Reimbursement Fee or Cash Disbursement Fee 1 N/A 2 N/A 3 EPS U.S. only 4 Supermarket Incentive Program U.S. only 5 Transition Incentive Interchange Fee (TIIF1) U.S. only 6 VISA Electron Interchange Reimbursement Fee/VISA Electron Card Transaction U.S. only 7 Relates to specific reduced reimbursement fees for intraregional transactions only 8 JC Penney U.S. only 9 Member-operated data capture (Asia-Pacific only) A Payment Service Interchange Reimbursement Fee (PSIRF) Brazil, Germany, Malaysia and U.S. B Interregional Pre-PS2000 C CEMEA Airline Transition Rate D Reserved: Delta-only merchant standard Interchange Reimbursement Fee-U.K. only E Reserved F Delta-only merchant Electronic Interchange Reimbursement Fee (EIRF)-U.K. only G N/A Version 4.02 Page 225 Last modified August 12, 2009

Private Use Field (bit 63) (Continued) Bit 63.11 Reimbursement Attribute (Continued) H I J K L M N-S T-V W-Z Description N/A Reserved for future use: BASE II draft data transactions only Electronic Interchange Reimbursement Fee (EIRF)-U.S. only Key-entered Payment Service Reimbursement Fee-U.S. only (for select developing markets only) Reserved for future use: BASE II Draft data transactions only VISA check card II Interchange Reimbursement fee-u.s. only Reserved for future use: BASE II Draft data transactions only Reserved Not applicable Version 4.02 Page 226 Last modified August 12, 2009

Tertiary Bit Map (bit 65) Bank of America Merchant Services MultiLink utilizes primary, secondary and tertiary bit maps. The primary bit map represents data fields 2 through 64. The secondary bit map represents bits 66 through 128. The tertiary bit map represents bits 130 through 192. Data fields 1, 65 and 129 can not exist, as these bits are used to indicate presence of subsequent bit maps. The tertiary bit map is only required if data elements represented by bits 130 through 192 are to be used in a particular message. Bit 129, which would indicate the presence of the Quaternary Bit Map, is not used at this time. All bit maps that are present in the message are grouped at the beginning of the message, immediately following the Message Type. Although the Tertiary Bit Map is designated as Bit 65, it physically resides immediately after the Secondary Bit Map in the message, rather than between bits 64 and 66. Example: NTIA Coupon Data (bit 163) and Private Use Card Acceptor Street Address (bit 170) are needed in a message. The Tertiary Bit Map will look like this in hexadecimal representation: 0000000020400000 and like this in binary representation (spaces provided only for readability): 0000 0000 0000 0000 0000 0000 0000 0000 0010 0000 0100 0000 0000 0000 0000 0000 Version 4.02 Page 227 Last modified August 12, 2009

Settlement (bit 66) This field contains a code indicating whether Bank of Amercia Merchant Services agrees with the totals sent in the Settlement Reqest message. Definition 1 In balance 2 Out of balance 9 Acknowledgement without reconciliation Version 4.02 Page 228 Last modified August 12, 2009

Network Management Information (bit 70) This field contains a code to indicate the type of network management to be performed. Value Function 001 Logon/echo test 002 Logoff 160 Request for new key 162 Deliver new key 265 System end-of-day totals (from merchant) 266 Store end-of-day totals (from merchant) 267 System end-of-day only no totals (from merchant) 268 Store end-of-day only no totals (from merchant) Version 4.02 Page 229 Last modified August 12, 2009

Credits, Number (bit 74) This field contains the total number of credit transactions, other than reversals, processed since the last settlement cutoff. Credit transactions are defined as transactions having a credit effect on the cardholder s account. Version 4.02 Page 230 Last modified August 12, 2009

Credits, Reversal Number (bit 75) This field contains the total number of reversal credit transactions processed since the last settlement cutoff. Reversal credit transactions are defined as reversals having a credit effect on the cardholder s account. Version 4.02 Page 231 Last modified August 12, 2009

Debits, Number (bit 76) This field contains the total number of debit transactions, other than reversals, processed since the last settlement cutoff. Debit transactions are defined as transactions having a debit effect on the cardholder s account. Version 4.02 Page 232 Last modified August 12, 2009

Debits, Reversal Number (bit 77) This field contains the total number of reversal debit transactions processed since the last settlement cutoff. Reversal debit transactions are defined as reversals having a debit effect on the cardholder s account. Version 4.02 Page 233 Last modified August 12, 2009

Credits, Amount (bit 86) This field contains the totaled amount of credit transactions, other than reversals, processed since the last settlement cutoff. Credit transactions are defined as transactions having a credit effect on the cardholder s account Version 4.02 Page 234 Last modified August 12, 2009

Credits, Reversal Amount (bit 87) This field contains the totaled amount of reversal credit transactions processed since the last settlement cutoff. Reversal credit transactions are defined as reversals having a credit effect on the cardholder s account. Version 4.02 Page 235 Last modified August 12, 2009

Debits, Amount (bit 88) This field contains the totaled amount of debit transactions, other than reversals, processed since the last settlement cutoff. Debit transactions are defined as transactions having a debit effect on the cardholder s account Version 4.02 Page 236 Last modified August 12, 2009

Debits, Reversal Amount (bit 89) This field contains the totaled amount of reversal debit transactions processed since the last settlement cutoff. Reversal debit transactions are defined as reversals having a debit effect on the cardholder s account. Version 4.02 Page 237 Last modified August 12, 2009

Original Data Elements (bit 90) This field contains information for tracking the current message back to prior messages for the same customer transaction. It is a fixed-length field with five subfields. Positions Description 1-4 Original message type 5-10 Original trace number 11-20 Original transmission date/time 21-31 Original acquirer ID 32-42 Original forwarding institution ID Version 4.02 Page 238 Last modified August 12, 2009

Replacement Amounts (bit 95) This field contains the corrected amount of a transaction in a partial reversal. The field consists of 4 fixed-length subfields, only one of which is used at this time. Bit 95.1 - Actual Transaction Amount (AN12) The corrected actual amount of the cardholder s transaction in the transaction currency. The field does not contain a decimal point. The field cannot be greater than or equal to Amount 1 (bit 4), nor can it be equal to zero. Two decimal places are assumed. Bit 95.2 Actual Settlement Amount (AN12) - The corrected actual amount of the cardholder s transaction in the settlement currency. The field does not contain a decimal point. Two decimal places are assumed. This field is not currently used. Value = 000000000000. Bit 95.3 Actual Transaction Fee Amount (AN9) - The corrected actual amount of the fee for the cardholder s transaction in the transaction currency. The field contains a leading sign (C = Credit, D = Debit), but does not contain a decimal point. Two decimal places are assumed. This field is not currently used. Value = D00000000. Bit 95.4 Actual Settlement Fee Amount (AN9) - The corrected actual amount of the fee for the cardholder s transaction in the settlement currency. The field contains a leading sign (C = Credit, D = Debit), but does not contain a decimal point. Two decimal places are assumed. This field is not currently used. Value = D00000000. Version 4.02 Page 239 Last modified August 12, 2009

Message Security (bit 96) This field contains the PIN encryption working key when single-length keys are used. Double-Length DES Key (Bit 105) is used when double-length keys are used. In a key change request exactly one of bits 96 or 105 must be present. Version 4.02 Page 240 Last modified August 12, 2009

Amount, Net Settlement (bit 97) This field contains the Gross Interchange Value, which is the net of all gross credit and gross debit amounts for a specific settlement entity. Fees and charges are not included. The first byte is a sign (C = Credit, D = Debit). There is not decimal point. Two decimal places are assumed. Version 4.02 Page 241 Last modified August 12, 2009

Settlement Institution ID (bit 99) This field contains a code that identifies the financial entity for which settlement information is being provided. For a store settlement, the field should contain the first 11 digits of the Merchant ID as assigned by Bank of America Merchant Services. For a merchant settlement, this field should contain the first 3 digits of the Merchant ID as assigned by Bank of America Merchant Services, follwed by 8 zeros. Version 4.02 Page 242 Last modified August 12, 2009

Receiving Institution ID (bit 100) This field must contain the BIN ID of the third-party authorizing agent that the originator wants to receive the transaction. If the check is drawn on a participating drawee financial institution, and that institution supports the requested service option, the transaction is routed to that institution. Otherwise the transaction is sent to the designated third-party authorizing agent. The BIN Ids for current third-party authorizing agents are: BIN ID Authorizing Agent 763057 BankServ 418532 Certegy 763060 ECHO Version 4.02 Page 243 Last modified August 12, 2009

Account ID 1 (bit 102) This field contains a number identifying an account or customer relationship in cardholder transactions. The issuer has the option to place a posting account number in this field of the response, but only if the account to which the transaction will be posted differs from that in Primary Account Number (bit 2). Version 4.02 Page 244 Last modified August 12, 2009

Transaction Description (bit 104) This field contains additional billing or reporting information about transaction or message processing. It consists of three subfields: Intended Use Flag, Business Flag and EMS Trace Number. Positions 1-8 Positions 9-11 Positions 12-26 Intended Use Flag Business Flag EMS Trace Number Intended Use Flag (AN8) (Left-justified, space-filled) Value Description ME2ME Movement of funds between two accounts owned by a single consumer but housed at different inistitutions ME2YOU Movement of funds between accounts owned by two separate consumers PAYRPMT Payer-initiated payment PAYEPMT Payee-initiated payment VERIFY Account verification inquiry ACTBAL Generic account balance inquiry Business Flag (AN3) Value Description Money Transfer Transactions AUC Auction (account to account, auction sale) BUS Business (business to business) PER Person (account to account, nonauction sale) Payer- and Payee Initiated Payments, Account Inquiries BRK Brokerage CCI Credit card issuer (e.g., Amex, Visa, MC issuer) GOV Government INS Insurance premiums LON Various consumer loans (e.g., mortgages, installment loans) OTH Other PLC Private label cards (e.g., JC Penney, Sears) Payments only UTL Utility (e.g., cable, electric, oil, telephone) EMS Trace Number (AN15) The EMS Trace Number is assigned by the acquirer and is left-justified and space-filled. The number must remain the same over the life of the transaction, including all requests, responses and reversals. Version 4.02 Page 245 Last modified August 12, 2009

Double-Length DES Key (bit 105) This field contains the PIN encryption working key when double-length keys are used. Message Security (Bit 96) is used when single-length keys are used. In a key change request exactly one of bits 96 or 105 must be present. Version 4.02 Page 246 Last modified August 12, 2009

Additional Private Data (bit 111) Used to house the EBT FNS# and/or the EBT Voucher number or the EBT case number. See the table below for details on the layout. This data is required in the merchant settlement file. Position Description 1-2 FNS data ID, value = EB 3-5 FNS data length 6-12 FNS number (left-justified, space filled) 13-14 Voucher number data ID, value = VN 15-17 Voucher number data length 18-32 Voucher number (left-justified, space filled) For EBT Cash Benefit transactions, this field is also required. It will be 12 digits long and will either contain a valid FNS number or zero in the FNS number field (voucher information may not be sent). Version 4.02 Page 247 Last modified August 12, 2009

Transport Data (bit 114) This optional field may be sent by the merchant in Debit, EBT or Credit Requests, Reversals or Advices. If sent, the value will be returned unchanged in the Debit, EBT or Credit Response, Reversal Response or Advice Response. There are two formats for this field: Free-form text untagged format The data consists of up to 32 characters, which may be alpha, numeric and/or special characters. The only restriction on the data is that the first character cannot be the special character ampersand ( @ ). Bank of America Merchant Services does not capture or edit this field. This format should be used only to hold data that the merchant wishes to have returned in the response, with no processing by Bank of America Merchant Services. This format is considered obsolete, but will continue to be supported by Bank of America Merchant Services at this time. New merchants and merchants making changes to their applications should use the tagged format. Tagged format The field consists of one or more subfields, each of which is made up of a two-character tag, a two character length field and the actual data. The data may be alpha, numeric and/or special characters. This is called TLV format. This format should be used if the merchant has a need to pass data to Bank of America Merchant Services for Settlement processing, in addition to having the data returned in the response message. Note that this format supports both data to be captured and processed by Bank of America Merchant Services, then returned in the response message; as well as data to only be returned in the response. As such, this format is more robust that free-form text format and is the preferred format for all merchants. Important note: See Appendix D for tips on proper TLV-format coding. Tag Data Bank of America Merchant Services data handling Length @1 1-10 Bank of America Merchant Services will capture and record the last instance of each of these @2 11-20 tagged data fields. The data will be made available to Bank of America Merchant Services @3 21-30 settlement processing. In addition, the field will be echoed back in the appropriate response message. @7 1-99 Bank of America Merchant Services will only echo back the field in the appropriate response @8 1-99 message. These tagged fields are provided to merchants who may want to send data that is @9 1-99 not to be captured by Bank of America Merchant Services along with data to be captured. Some examples of tagged data: @105ABCDE Tag = @1 Length = 05 Data = ABCDE This data will be captured by Bank of America Merchant Services and made available to the Bank of America Merchant Services Settlement System. In addition, the entire field will be returned to the merchant in the response message. @212a1b2c3d4e5$@@70512345 Version 4.02 Page 248 Last modified August 12, 2009

Transport Data (bit 114) (Continued) Tag = @2 Length = 12 Data = a1b2c3d4e5$@ Tag = @7 Length = 05 Data = 12345 The 12 characters of data following the @2 tag will be captured by Bank of America Merchant Services and made available to the Bank of America Merchant Services Settlement System. The 5 characters following the @7 tag will not be captured. The entire field will be returned to the merchant in the response message. @103zyx@108abcdefgh Tag = @1 Length = 03 Data = zyx Tag = @1 Length = 08 Data = abcdefgh As there are two instances of the @1 tag, the data following the first instance ( zyx ) will be ignored for purposes of capture and forwarding to the Bank of America Merchant Services Settlement System. Only the data following the second instance ( abcdefg ) will be captured and forwarded. The entire field will be returned to the merchant in the response message. Version 4.02 Page 249 Last modified August 12, 2009

Interchange Reference Number (bit 115) This optional field is used in credit transaction responses and reversal requests to hold the retrieval reference number used by the interchange module (as opposed to the retrieval reference number sent by the merchant in field 37). The field is only used by and for merchants that want the ability to send partial reversals more than 24 hours after the original authorization was received. Use of this service requires that the merchant have a method of storing the Interchange Reference Number sent on each response and returning it on any subsequent partial reversal. Please note: Partial reversals (reversals containing a replacement amount field 95) may only be sent for credit transactions on VISA cards. It is the merchant s responsibility to ensure that partial reversals are not sent for other card types or for debit or EBT transactions. Field 115 should not be sent on any debit or EBT reversals or any full credit reversals (those not containing field 95). If this optional service is being used by the merchant, Field 115 should be sent for all partial reversals for credit transactions involving a VISA card, regardless of the elapsed time between the approval and the reversal. Use of this field requires prior arrangement with your Bank of America Merchant Services account representative. Version 4.02 Page 250 Last modified August 12, 2009

Address Verification Data (bit 123) This field is used in credit transaction requests to send selected portions of the cardholder s postal code and street address for verification. The field is formatted as follows: Bytes 1-9 Bytes 10-29 Postal code Street address Positions 1-9, Postal code: This value is the 5-digit postal or ZIP code (left-justified, space filled), 6-character Canadian postal code (left-justified, space filled) or 9-digit postal or ZIP code. Positions 10-29, Street address: This subfield contains up to 20 characters of street address. The acquirer converts spelled-out numbers to digits. The field is left-justified, space filled. Examples of street addresses are: Actual Address Subfield Entry One Elm St 1 Elm St 123 First St 123 1 st St 89 25 th Ave 89 25 th Ave 22 Walnut St #23 22 Walnut St #23 P.O. Box 12345 P. O. Box 12345 (note insertion of spaces) Version 4.02 Page 251 Last modified August 12, 2009

Supporting Information (bit 125) This is a multi-use field containing additional information for various kinds of transactions. The uses supported at this time are: Unformatted or parsed MICR data for POS Check transactions (usage 9) Unformatted or parsed MICR data for POS Check transactions (usage 9) When capturing MICR data, merchants must capture the MICR data electronically through a check-reading device. The merchant must capture the MICR data in its entirety, including the Routing Transit Number, the customer s Check Account Number and the Check Serial Number. POS Check request messages must contain unformatted (raw) MICR. Approved POS Check responses will contain parsed MICR. Depending on where and why the transaction was declined, declined POS Check responses may contain parsed or raw MICR. For instance, if the transaction is declined at Bank of America Merchant Services prior to routing to the back end interchange because the link is down, raw MICR is returned. But if the transaction is declined by the back end interchange because of a duplicate check number, the MICR will be parsed in the response. POS Check reversal requests must contain raw MICR and raw MICR will be returned in POS Check reversal responses. The MICR data field contains customer financial institution account information captured from the MICR line on customer s checks. Unformatted MICR Field Name Position Size Data Content Format Length 1 1 Contains the length of the data contents in the entire field. Field Identifier 2-3 2 $V Identifies use of the field as POS Check. Data Type Identifier 4-5 2 RM Must be present in the request and the MICR data that follows must be unformatted. RM identifies the data contents as unformatted MICR information. Data Length Identifier 6-8 3 999 Indicates the length of the MICR data contained in the field. Version 4.02 Page 252 Last modified August 12, 2009

Supporting Information (bit 125) (Continued) Parsed MICR Field Name Position Size Data Content Format Unformatted MICR Information 9 Var Must contain the entire unaltered contents of the MICR line, with spaces preserved, read from the customer s check by a terminal. At a minimum, the Routing Transit Number and Customer Account Number (on-us field) must be present. The unformatted MICR data is the exact MICR line from the check, including spaces, except that the MICR symbols are replaced as follows ( raw TOAD format): The Transit symbol (I) must be replaced by the letter T in either upper or lower case. The On-Us symbol (II) must be replaced by the letter O in either upper or lower case. The Dash symbol (-) must be replaced by the letter D in either upper or lower case. Length 1 1 Contains the length of the data contents in the entire field. Field Identifier 2-3 2 $V Identifies use of the field as POS Check. Following the field identifier, subfields may appear in any order within field 125. Routing Transit Number Customer Account Number Check Serial Number Any 9 The drawee financial institution s Routing Transit Number (ABA Number) Any Any Var (max 19) Var (max 15) The customer deposit account number. The check serial number of the check being converted. The Routing Transit Number must be formatted as follows: AB999dddd, where AB identifies the subfield, 999 the length of the data, ad dddd, the actual data content. The customer deposit account number must be present, a maximum of 19 characters and formatted as follows: AN999d-d, where AN identifies the subfield, 999 the length of the data, and d-d, the actual data content. The check serial number, when present, is a maximum of 15 characters, and is formatted as follows: CK999d-d, where CK identifies the subfield, 999 the length of the data, and d-d, the actual data content. Any of the alpha characters sent in this field in the request message ( t, d ) must be stripped out when the field is in parsed MICR. Note: The check serial number is optional for Internet, Mail Order or Telephone Order request messages. Version 4.02 Page 253 Last modified August 12, 2009

VISA Private Use Fields (bit 126) This is a bit-mapped, private use field for VSEC program fields and CVV2 services. Bit 126.0 Bit Map (B8) This subfield indicates the presence of VISA Private Use Fields subfields to follow. If any data fields are present, the entire bit map must be present. Note: the bit map provides support for up to 64 subfields, although fewer than that are supported at this time. Example: Cardholder Serial Number (bit 126.6) is needed. The bit 126.0 Bit Map would appear as follows in hexadecimal representation: 0400000000000000 and like this in binary representation (spaces included only for readability): 0000 0100 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 Bit 126.6 Cardholder Serial Number (B17) A value assigned to a SET cardholder certificate issued by the issuer s certificate authority. The number s specific size and data type are not defined by the SET standard. The first byte contains the number of significant hexadecimal digits from 1 to 32. The number is right-justified and zero-filled if less than 16 bytes binary. If the cardholder certificate does not appear in the SET transaction, this field must not be sent. Bit 126.7 Merchant Serial Number (B17) A value assigned to a SET merchant certificate issued by the acquirer s certificate authority. The number s specific size and data type are not defined by the SET standard. The first byte contains the number of significant hexadecimal digits from 1 to 32. The number is right-justified and zero-filled if less than 16 bytes binary. Bit 126.8 Transaction ID (VSEC) (B20) A unique number (XID) generated by the merchant server to identify the transaction. This field is used in conjunction with Bit 126.9 CAVV Data. Bit 126.9 CAVV Data (NP40) This field contains the Cardholder Authentication Verification Value (CAVV). The CAVV is a cryptographic value calculated by the issuer s Access Control Server (ACS) using the issuer s encryption key and related elements and is returned to the merchant as part of VISA s 3-D Secure process. The CAVV is unique to the cardholder and to the transaction that was authenticated. The acquirer transfers the ACS data to this field when preparing the request. It consists of the following subfields: Position 1 Position 2 Position 3 Position 4 Position 5 Position 6 Position 7 Authentication Second CAVV Key CAVV Unpredictable Authentication Reserved Results Indicator Factor Authentication Indicator Value Number Tracking Number Byte 1 Byte 2 Byte 3 Bytes 4-5 Bytes 6-7 Bytes 8-15 Bytes 16-20 Version 4.02 Page 254 Last modified August 12, 2009

VISA Private Use Fields (bit 126) (Continued) Bit 126.9 CAVV Data (Continued) 126.9 Position 1 Authentication Results Indicator (NP2) Value Description 00 Authentication successful 05 Authentication could not be performed 06 ACS system error 09 Authentication failed 126.9 Position 2 Second Factor Authentication (NP2) Value Description 00 Not present 11 VSDC card used; cryptogram failed 12 VSDC card used; cryptogram passed 126.9 Position 3 CAVV Key Indicator (NP2) Value Description 01 CAVV key set 1 02 CAVV key set 2 126.9 Position 4 CAVV Value (NP4) The 3 digit code generated by the Issuer s ACS that may be used by the issuer to validate the authentication response during authorization. A leading zero is required to pad the first unused half-byte. VISA Private Use Fields (bit 126) (Continued) 126.9 Position 5 Unpredictable Number (NP4) A 4-digit code used by the issuer s ACS to generate the CAVV. When a 3D-Secure transaction involves another method of authentication, such as a VSDC card, the next two fields are formatted as shown below. Otherwise, they are zero-filled. 126.9 Position 6 Authentication Tracking Number (NP16) A 16-digit code that is generated by the issuer s ACS to identify the transaction. 126.9 Position 7 Reserved (NP10) Zero filled. Bit 126.10 CVV2 Authorization Request Data (AN6) This field contains CVV2 data. It is used for VISA or Diners Club CVV2, MasterCard CVC2, and Discover or American Express CID data. It consists of 3 subfields: Presence Indicator (AN1), Response Type (AN1) and CVV2 Value (AN4 right-justified, blank filled). Presence Indicator (AN1) Value Description 0 CVV2 value is deliberately bypassed or is not provided by the merchant. 1 CVV2 value is present. 2 CVV2 value is on the card but is illegible. 9 Cardholder states that the card has no CVV2 imprint. Version 4.02 Page 255 Last modified August 12, 2009

VISA Private Use Fields (bit 126) (Continued) Bit 126.10 CVV2 Authorization Request Data (Continued) Response Type (AN1) Value Description 0 Only the normal response code in field 39 should be returned. 1 The normal response code in field 39 and the CVV2 result in field 44.10 should be returned. Bit 126.12 Service Indicators (B3) This is a VISA private-use service development field. Members must be certified to send and receive this field in its entirety whether or not they participate in any of its service applications. The field is made up of three bytes, divided into 8 bit indicators each. Position 1 Position 2 Position 3 Position 4-24 Transponder Indicator Relationship Indicator Deferred Billing Indicator Reserved (all zeros) Byte 1, bit 1 Byte 1, bit 2 Byte 1, bit 3 Byte 1, bits 4-8, Bytes 2-3 Transponder Indicator: To identify participating member transactions that use radio frequency (RF) devices to exchange information in certain attended and unattended environments. This is valid for MasterCard and American Express transactions as well as VISA. Value Description 0 Not provided 1 Transponder initiated Relationship Indicator: To identify transactions originating from merchants participating in the VISA U.S.A. Relationship manager Service that regularly collect recurring payments from customers. Value Description 0 Not provided 1 Relationship participant Deferred Billing: To identify transactions from participating U.S. region members that use deferred billing. Participating and nonparticipating acquirers alike may include the field in requests. Value Description 0 Not provided 1 Deferred billing transaction Bit 126.14 Payment Guarantee Option (AN1) This field is a VISA private-use VISA Commerce field. It is used to indicate whether the seller requires a payment guarantee as a precondition to filling the order. Value Option Description 1 Open account/open trade The seller does not require a payment guarantee as a precondition for filling the order 2 Payment guarantee trade The seller does require a payment guarantee as a precondition for filling the order Version 4.02 Page 256 Last modified August 12, 2009

VISA Private Use Fields (bit 126) (Continued) 126.15 Universal Card Authentication Field Indicator (AN1) Value Description 0 Universal Card Authentication Field data collection is not supported by the merchant. Field 126.16 is not present. 1 Universal Card Authentication Field data collection is supported by the merchant, but UCAF data was not populated. Field 126.16 is not present. 2 Universal Card Authentication Field data collection is supported by the merchant and UCAF data was populated. Field 126.16 is present. 126.16 UCAF Value (AN32) This field contains the MasterCard Universal Card Authentication Field value generated by the merchant server to identify the transaction. This field is used in conjunction with Universal Card Authentication Field Indicator (bit 126.15). Version 4.02 Page 257 Last modified August 12, 2009

Private Use DUKPT (bit 127) This field is only present if DUKPT PIN encryption is used. It contains the Key Serial Number (KSN) that was generated from the Initial Key Serial Number and an encryption counter. The Key Serial Number is used to derive the associated PIN encryption key. Valid lengths are 10 through 20. There is a leading 1 byte binary length character that indicates the length of the KSN. The KSN must be byte-aligned. (The KSN is right-justified with a leading 0 when an odd length KSN is specified.) Version 4.02 Page 258 Last modified August 12, 2009

NTIA Coupon Data (bit 163) Merchants who have chosen to participate in the National Telecommunications and Information Administration (NTIA) coupon program utilize this field to send the UPC or retailer-specific SKU data associated with a digital-toanalog converter box. This field will only be used on credit requests and full reversals of $40.00 or less using BIN 589732. Use of this field requires prior arrangement with your Bank of America Merchant Services representative. Version 4.02 Page 259 Last modified August 12, 2009

Large Private Data 1 (bit 164) This field, along with bits 165 through 167, is used to move information between the acquirer and the issuer. It is made up of multiple variable-length tag-identified subfields. Each subfield consists of three parts: a 5-character tag, a 4-character length and a variable data area. This is called TLV format. Subfield details follow. Important note: See Appendix D for tips on proper TLV-format coding. This table details in which kinds of transactions a given subfield may be used. Tag Max Data Len Description Allowed in Money Transfer *NA*\ 25 Payee billing account number. This is the consumer s account number at the payee. *NB*\ 40 Receiver phone/pager number. Format is device code (T=telephone, P=pager, F=FAX), followed by the full number, pass code, etc. Allowed in Payer Initiated Payment Allowed in Payee Initiated Payment No Yes Yes Yes No No *NC*\ 60 Receiver s email address Yes No No *ND*\ 60 Sender s email address Yes No No *NE*\ 50 Sender text; a short free-form message from the sender Yes No No to the receiver *NF*\ 25 Payee invoice number. No Yes Yes *NG*\ 60 Payee s email address. No Yes Yes *NH*\ 50 Payee description. No Yes Yes If a subfield may be used in a transaction, this table details in which messages within that transaction sequence the subfield may/must be present. Tag Description Presence in Request Presence in Response Presence in Reversal Request Presence in Reversal Response *NA*\ Payee billing account number. This is the Req Req Req N/A consumer s account number at the payee. *NB*\ Receiver phone/pager number. Format is device Opt Opt Opt N/A code (T=telephone, P=pager, F=FAX), followed by the full number, pass code, etc. *NC*\ Receiver s email address Opt Opt Opt N/A *ND*\ Sender s email address Opt Opt Opt N/A *NE*\ Sender text; a short free-form message from the Opt Opt Opt N/A sender to the receiver *NF*\ Payee invoice number. Opt Opt Opt N/A *NG*\ Payee s email address. Opt Opt Opt N/A *NH*\ Payee description. Opt Opt Opt N/A Example: *NA*\0012987654321098*NF*\000813572468 *NA*\ is a tag indicating the following subfield is the payee billing account number. 0012 is the length of the payee billing account number. 987654321098 is the payee billing account number data. *NF*\ is a tag indicating the following field is the payee invoice number. 0008 is the length of the payee invoice number. 13572468 is the payee invoice number data. Version 4.02 Page 260 Last modified August 12, 2009

Large Private Data 2 (bit 165) Information to be moved between the acquirer and the issuer in Bill Payment transactions. Contains multiple tagidentified subfields. This field is reserved for future use. Version 4.02 Page 261 Last modified August 12, 2009

Large Private Data 3 (bit 166) Information to be moved between the acquirer and the issuer in Bill Payment transactions. Contains multiple tagidentified subfields. This field is reserved for future use. Version 4.02 Page 262 Last modified August 12, 2009

Large Private Data 4 (bit 167) Information to be moved between the acquirer and the issuer in Bill Payment transactions. Contains multiple tagidentified subfields. This field is reserved for future use. Version 4.02 Page 263 Last modified August 12, 2009

Acquirer Trace Data (bit 168) This field contains the payee name. The format of the field is a 1-character identifier (=0), followed by up to 60 characters of data. Example: If the payee name is CITY POWER, the field would be formatted as follows: 0CITY POWER (total length = 11) Version 4.02 Page 264 Last modified August 12, 2009

Payee Phone (bit 169) This field contains the payee s phone or pager number. For regulatory purposes, periodic statement are expected to disclose the phone number if the consumer has questions about the payment. Version 4.02 Page 265 Last modified August 12, 2009

Private Use Card Acceptor Street Address (bit 170) This field contains the street address of the card acceptor. This address should be the street address of the actual location where the transaction occurred. Version 4.02 Page 266 Last modified August 12, 2009

Private Use General (bit 171) This field contains several optional subfields unique to Bank of America Merchant Services processing. If none of the subfields are needed, the field will not be present. The format of the field is as follows: overall field length attribute, bit map indicating presence of subfields, followed by the subfields themselves, which may each be fixed or variable length (in which case they will be preceded by a length attribute). Bit 171.0 Bit Map (B8) This subfield indicates the presence of Private Use - General subfields that follow. If any data fields are present, the entire bit map must be present. Note: the bit map provides support for up to 64 subfields, although fewer than that are supported at this time. Example: Merchant Order Number (bit 171.1) and Customer (bit 171.5) are needed. The bit 171.0 Bit Map would appear as follows in hexadecimal representation: 8800000000000000 and like this in binary representation (spaces included only for readability): 1000 1000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 Bit 171.1 Merchant Order Number (ANS16) A unique value defined by the merchant that is used to identify the transaction. This data will be returned to the merchant on the response, but is not used internally for processing. Bit 171.2 Merchant Reference Number (N8) A number assigned by the merchant, which must be greater than zero. This is a unique key for transaction processing identification. This data will be returned to the merchant on the response and will be recorded internally for backend processing. Bit 171.3 Merchant Advice (ANS2) Present for recurring payments only. Merchant requests this code by setting field 60 Mail Order/Telephone Order/Electronic Commerce Indicator = 02 and field 62.1 = R. Value Description 01 New account information available 02 Try authorization again later 03 Do not try again; account no longer valid 21 Stop recurring payment service R0 Stop payment order R1 Revocation of authorization order R3 Revocation of all authorizations order Bit 171.4 Sales Tax Amount (NP8) Assumes 2 decimal places, right-justified zero filled. Contains amount of tax associated with transaction. This field will be captured and logged for settlement processing. Version 4.02 Page 267 Last modified August 12, 2009

Private Use General (bit 171) (Continued) Bit 171.5 Customer (AN17) Applicable in commercial card transactions only. A code that may be given to the merchant by a cardholder customer. This field may be reported back on reporting provided to a cardholder and may represent a general ledger number or cost center number to be associated with the purchase being made. This field will be captured and logged for settlement processing. Bit 171.6 Auth Only Indicator (AN1) Applicable for Credit purchase transactions and Debit and Credit test transactions (see Bit 171.8 below) only. Used by Host Capture merchants to indicate to Bank of America Merchant Services to not capture and create settlement for this transaction. A value of N indicates to Bank of America Merchant Services to not capture the transaction. Merchants not using Bank of America Merchant Services s Host Capture product may either send this field with a value of N for all transactions or omit sending the field (as they are set up for non-host-capture in Bank of America Merchant Services s settlement system). Bit 171.7 Card FIID (AN4) Obsolete. This field is no longer supported. Bit 171.8 Transaction Subtype (AN1) Used to indicate various specialized transaction situations. Value Description Rqst/Resp C Real time clearing transaction. This will be either a Real Time Clearing preauth/completion Both (0100/0220) transaction set or a Real time Clearing purchase (0200) transaction without PIN. In the request, it indicates the merchant s desire to have this transaction considered for real time clearing. In the response and any subsequent reversal request/response, it indicates the transaction is eligible for real time clearing. N Real time clearing not eligible. This will be either a Real Time Clearing preauth/completion Resp only (0100/0220) transaction set or a Real Time Clearing purchase (0200) transaction without PIN. It indicates the transaction is not eligible for real time clearing. P Real time clearing no CPS program found. This will be either a Real Time Clearing Resp only preauth/completion (0100/0220) transaction set or a Real Time Clearing purchase (0200) transaction without PIN. It indicates the transaction is eligible for real time clearing, but no CPS program was found for the card. The result will be a higher-than-expected processing fee associated with the transaction. The merchant should contact their Bank of America Merchant Services representative to determine how to correct this situation. Q Real time clearing not qualified for CPS. This will be either a Real Time Clearing Resp only preauth/completion (0100/0220) transaction set or a Real Time Clearing purchase (0200) transaction without PIN. It indicates the transaction is eligible for real time clearing, but the card used is not qualified for CPS. The result will be a higher-than-expected processing fee associated with the transaction. The merchant should contact their Bank of America Merchant Services representative to determine how to correct this situation. T Test transaction. Transaction amount will be set to $1.00. Card capabilities are checked. Transaction has no settlement impact. Currently only valid for MasterCard credit transactions. Both Version 4.02 Page 268 Last modified August 12, 2009

Point of Service Data (bit 172) This field is a series of codes that identify terminal capability, security data, and specific conditions present at the time a transaction occurred at the point of service. The data is unique to the switch interchange that routed/authorized the transaction. This field must be sent on the settlement file. Please note: The format of the data that must be sent on the settlement file varies, based on the switch interchange that authorized the transaction. Please contact your Bank of America Merchant Services representative for the details of how to format this data. Version 4.02 Page 269 Last modified August 12, 2009

Settlement Data (bit 173) This field contains information needed for settlement of the transaction. It is a variable-length field composed of 1 or more TLV data items. Each TLV data item contains a tag identifier, data length information and the data itself. This is called TLV format. Many of the subfields are shown as having a maximum length of 255 bytes. Actual current usage may be less than 255 bytes, but the merchant is advised to code for maximum values. Keep in mind that the maximum length of the Settlement Data field itself is 999 bytes. Important note: See Appendix D for tips on proper TLV-format coding. Tag Field Description Field Length and Type Field Usage 13 State Tax Indicator ID 2 bytes alphanumeric Real Time Clearing State Tax Indicator Length (value = 1) 1 byte binary transaction. State / State Tax Indicator (value = 1 state/provincial tax included) 1 byte numeric Provincial tax is included and Business or Corporate card used. If tax is separate, do not send this tag and send the tax amount in bit 171.4. Present in preauthorization completion request, response, original financial request, response and attendant reversal request and response. 1C Additional Level 3 Data Indicator ID 2 bytes alphanumeric Real Time Clearing Additional Level 3 Data Indicator Length (value = 1 byte binary 1) Additional Level 3 Data Indicator (value = Y) 1 byte alphanumeric transaction. Level 3 and electronic with data when Purchasing non-fleet card used. If merchant uses Host Draft Capture, will also need to send tags 6U-6Z). Present in preauthorization completion request, original financial request and attendant reversal request. 61 Call Initiation Date ID 2 bytes alphanumeric Telephone-related Call Initiation Date Length (value = 8) 1 byte binary Call Initiation Date (yyyymmdd) 8 bytes numeric transaction. Present in original financial request, response, reversal request and response. 62 Local Time of Call ID 2 bytes alphanumeric Telephone-related Local Time of Call Length (value = 6) 1 byte binary Local Time of Call (hhmmss) 6 bytes alphanumeric transaction. Present in original financial request, response, reversal request and response. 63 Length of Call ID 2 bytes alphanumeric Telephone-related Length of Call Length (value = 1 to 255) 1 byte binary Length of Call (expressed in minutes) 1 to 255 bytes numeric transaction. Present in original financial request, response, reversal request and response. Version 4.02 Page 270 Last modified August 12, 2009

Settlement Data (bit 173) (Continued) Tag Field Description Field Length and Type Field Usage 64 Initiating Phone Number ID 2 bytes alphanumeric Telephone-related Initiating Phone Number Length (value = 1 to 255) 1 byte binary transaction. Present in Initiating Phone Number - If a U.S. or Canadian number, includes area code. Otherwise, includes full phone number with country code, city code and local number. 1 to 255 bytes alphanumeric original financial request, response, reversal request and response. 65 Initiating City ID 2 bytes alphanumeric Telephone-related Initiating City Length (value = 1 to 255) 1 byte binary Initiating City 1 to 255 bytes alphanumeric transaction. Present in original financial request, response, reversal request and response. 66 Initiating State or Country ID 2 bytes alphanumeric Telephone-related Initiating State or Country Length (value = 1 to 1 byte binary 255) Initiating State or Country Two-character 1 to 255 bytes alphabetic state code (if U.S.) or three-character alphabetic alphabetic country code (if non-u.s.). See bit 48 POS Check U.S. State s and Abbreviations for state codes and below for country codes. transaction. Present in original financial request, response, reversal request and response. 67 Destination Phone Number ID 2 bytes alphanumeric Telephone-related Destination Phone Number Length (value = 1 to 1 byte binary 255) Destination Phone Number - If a U.S. or Canadian 1 to 255 bytes number, includes area code. Otherwise, includes alphanumeric full phone number with country code, city code and local number. transaction. Present in original financial request, response, reversal request and response. 68 Destination City ID 2 bytes alphanumeric Telephone-related Destination City Length (value = 1 to 255) 1 byte binary Destination City 1 to 255 bytes alphanumeric transaction. Present in original financial request, response, reversal request and response. 69 Destination State or Country ID 2 bytes alphanumeric Telephone-related Destination State or Country Length (value = 1 to 1 byte binary 255) transaction. Present in original financial request, response, reversal request and response. 1 to 255 bytes alphanumeric 6E Gratuity ID 2 bytes alphanumeric Restaurant transaction. Gratuity Length (value = 1 to 255) Gratuity 1 byte binary 1 to 255 bytes numeric Present in original financial request, response, reversal request and response 6S Unique Invoice Number ID 2 bytes alphanumeric Private Label transaction for Unique Invoice Number Length (value = 1 to 255) 1 byte binary HDC merchants. The Unique Invoice Number 1 to 255 bytes numeric unique number associated with the transaction provided by the card acceptor. Version 4.02 Page 271 Last modified August 12, 2009

Settlement Data (bit 173) (Continued) Tag Field Description Field Length and Type Field Usage 6T Card Acceptor Reference Number ID 2 bytes alphanumeric Private Label transasction Card Acceptor Reference Number Length (value 1 1 byte binary for HDC merchants. to 255) Card Acceptor Reference Number 1 to 255 bytes Transaction-specific reference number used by merchants and issuers to identify individual transactions. Facilitates card acceptor/corporation communication and record keeping. 6U Type of Purchase ID 2 bytes alphanumeric Real Time Clearing Type of Purchase Length (value = 1) 1 byte binary transaction. Level 3 and Type of Purchase (1 = fuel & non-fuel, 3 = fuel) 1 byte numeric electronic with data when Purchasing non-fleet card used. Present in preauthorization completion request, original financial request and attendant reversal request. 6V Fuel Type ID 2 bytes alphanumeric Real Time Clearing Fuel Type Length (value = 2) 1 byte binary transaction. Level 3 and Fuel Type (contact your Bank of America Merchant Services Account Representative for a current list of valid values) 2 bytes alphanumeric electronic with data when Purchasing non-fleet card used. Present in preauthorization completion request, original financial request and attendant reversal request. 6W Gross Fuel Purchase ID 2 bytes alphanumeric Real Time Clearing Gross Fuel Purchase Length (value 1 to 255) 1 byte binary Gross Fuel Purchase (total cost of fuel purchased, 1 to 255 bytes numeric 2 decimal positions implied) transaction. Level 3 and electronic with data when Purchasing non-fleet card used. Present in preauthorization completion request, original financial request and attendant reversal request. 6X Unit of Measure Fuel ID 2 bytes alphanumeric Real Time Clearing Unit of Measure Fuel Length (value = 1) 1 byte binary Unit of Measure Fuel (G = U.S. gallon, I = Imperial 1 byte numeric gallon, L = liter) transaction. Level 3 and electronic with data when Purchasing non-fleet card used. Present in preauthorization completion request, original financial request and attendant reversal request. Version 4.02 Page 272 Last modified August 12, 2009

Settlement Data (bit 173) (Continued) Tag Field Description Field Length and Type Field Usage 6Y Quantity of Fuel ID 2 bytes alphanumeric Real Time Clearing Quantity of Fuel Length (value = 1 to 255) 1 byte binary transaction. Level 3 and Quantity of Fuel (number of units see Unit of Measure Fuel above of fuel purchased, 2 decimal positions implied) 1 to 255 bytes numeric electronic with data when Purchasing non-fleet card used. Present in preauthorization completion request, original financial request and attendant reversal request. 6Z Miscellaneous Fuel Tax Exemption Status ID 2 bytes alphanumeric Real Time Clearing Miscellaneous Fuel Tax Exemption Status Length 1 byte binary Miscellaneous Fuel Tax Exemption Status (0 = 1 byte numeric non-exempt, 1 = exempt) transaction. Level 3 and electronic with data when Purchasing non-fleet card used. Present in preauthorization completion request, original financial request and attendant reversal request. C2 Customer ID 2 bytes alphanumeric Real Time Clearing Customer Length (value = 1 to 255) 1 byte binary Customer 1 to 255 bytes numeric transaction. May consist of vehicle ID, driver ID or generic ID. Purchasing non- Fleet card used. Present in preauthorization requests, completion requests and reversal requests. TE State Tax Exempt ID 2 bytes alphanumeric Present if transaction is State Tax Exempt length (value = 1) 1 byte binary exempt from state sales tax. State Tax Exempt (value = 1) 1 byte numeric Frequently-Used Country s Country Canada CAN Guam GUM Northern Mariana Islands MNP Puerto Rico PRI U.S. Virgin Islands VIR (if you need a code for a country not listed here, please contact your Bank of America Merchant Services representative) Version 4.02 Page 273 Last modified August 12, 2009

Supplemental Data (bit 177) This field contains various items of supplemental information about the transaction. It is a variable-length field composed of 1 or more TLV data items. Each TLV data item contains a tag identifier, data length information and the data itself. This is called TLV format. Some data will only be present in the message from the merchant to Bank of America Merchant Services (inbound), some only present in the message from Bank of America Merchant Services to the merchant (outbound) and some in both messages. The intended presence is noted in the table. Many of the subfields are shown as having a maximum length of 255 bytes. Actual current usage may be less than 255 bytes, but the merchant is advised to code for maximum values. Keep in mind that the maximum length of the Supplemental Data field itself is 999 bytes. Fields described as Switch contain data that was either received from the backend interchange (VISA, MasterCard, NYCE, STAR, etc.) or that was sent by Bank of America Merchant Services to that backend interchange for purposes of processing the transaction. This data is in its unaltered, untranslated form as it was received from or sent to the backend interchange. Important note: See Appendix D for tips on proper TLV-format coding. Tag Field Description Field Length and Type Field Usage Inbound/ Outbound 01 BAMS Network ID ID 2 bytes alphanumeric Identifies the Outbound BAMS Network ID Length (value = 1 to 1 byte binary network ID of the 255) BAMS Network ID 1 to 255 (currently 4) bytes alphanumeric authorizer of the transaction. 02 Switch Trace Number ID 2 bytes alphanumeric Trace number Switch Trace Number Length (value = 1 1 byte binary to 255) Switch Trace Number 1 to 255 bytes alphanumeric 71 Switch Processing ID 2 bytes alphanumeric Processing code Switch Processing Length (value = 1 to 255) Switch Processing 1 byte binary returned from the authorizing interface. returned from the authorizing interface. 1 to 255 bytes alphanumeric 72 Switch POS Entry Mode ID 2 bytes alphanumeric POS entry mode Switch POS Entry Mode Length (value = 1 to 255) Switch POS Entry Mode 1 byte binary returned from the authorizing interface. 1 to 255 bytes alphanumeric 73 Switch POS Data Info ID 2 bytes alphanumeric POS data code Switch POS Data Info Length (value = 1 to 255) Switch POS Data Info 1 byte binary returned from the authorizing interface. 1 to 255 bytes alphanumeric 74 Switch Acquirer ID ID 2 bytes alphanumeric Acquirer ID returned Switch Acquirer ID Length (value = 1 to 255) Switch Acquirer ID 1 byte binary 1 to 255 bytes alphanumeric from the authorizing interface. Outbound Outbound Outbound Outbound Outbound Version 4.02 Page 274 Last modified August 12, 2009

Supplemental Data (bit 177) (Continued) Tag Field Description Field Length and Type Field Usage Inbound/ Outbound 75 Switch Forwarding ID ID 2 bytes alphanumeric Forwarding ID Outbound Switch Forwarding ID Length (value = 1 1 byte binary returned from the to 255) Switch Forwarding ID 1 to 255 bytes alphanumeric authortizing interface. 76 Switch Acceptor ID ID 2 bytes alphanumeric Switch acceptor ID Outbound Switch Acceptor ID Length (value = 1 to 1 byte binary returned from the 255) authorizing interface. Switch Acceptor ID 1 to 255 bytes alphanumeric 81 Switch AVS Response ID 2 bytes alphanumeric AVS response code Outbound Switch AVS Response Length 1 byte binary value returned from (value = 1) Switch AVS Response 1 to 255 bytes alphanumeric the authorizing interface. 82 Switch CVV Response ID 2 bytes alphanumeric CVV response code Outbound Switch CVV Response Length 1 byte binary value returned from (value = 1) the authorizing Switch CVV Response 1 to 255 bytes interface. alphanumeric 83 Switch CVV2 Response ID 2 bytes alphanumeric CVV2 response Outbound Switch CVV2 Response Length 1 byte binary code value returned (value = 1) from the authorizing Switch CVV2 Response 1 to 255 bytes interface. alphanumeric 84 Switch Network Transaction ID ID 2 bytes alphanumeric Network transaction Outbound Switch Network Transaction ID Length 1 byte binary ID value returned (value = 1 to 255) from the authorizing Switch Network Transaction ID 1 to 255 bytes interface. alphanumeric 91 Discover and Affiliates (Diners Intl. and 2 bytes alphanumeric Track1 and track2 Outbound JCB) Track Condition s ID condition codes Discover and Affiliates (Diners Intl. and 1 byte binary JCB) Track Condition s Length (value = 2) Discover and Affiliates (Diners Intl. and JCB) Track Condition s 1 to 255 bytes alphanumeric A1 Store Number ID 2 bytes alphanumeric Merchant store Inbound Store Number Length (value = 1 to 255) 1 byte binary number. Store Number 1 to 255 bytes alphanumeric A2 Mall Name ID 2 bytes alphanumeric Name of mall where Inbound Mall Name Length (value = 1 to 255) 1 byte binary merchant s store is Mall Name 1 to 255 bytes located. alphanumeric Version 4.02 Page 275 Last modified August 12, 2009

Supplemental Data (bit 177) (Continued) Tag Field Description Field Length and Type Field Usage Inbound/ Outbound A3 Phone Number ID 2 bytes alphanumeric Contact phone Inbound Phone Number Length (value = 1 to 255) 1 byte binary number at location Phone Number (in location of POS device) 1 to 255 bytes alphanumeric of merchant s POS device. A4 Aggregator Seller/Vendor ID 2 bytes alphanumeric Payment Service Inbound Aggregator Seller/Vendor Length 1 byte binary Provider Aggregator (value = 1 to 255) Aggregator Seller/Vendor 1 to 255 bytes alphanumeric data. Currently used for AMEX transactions only. I1 Total Amount ID 2 bytes alphanumeric Total amount of all Inbound Total Amount Length (value = 12) 1 byte binary payments. Zerofilled. Total Amount 12 bytes numeric Right-justified. Two decimal places implied. Used for Installment Payments. I2 Currency ID 2 bytes alphanumeric Currency code of the Inbound Currency Length (value = 3) 1 byte binary payment submitted. Currency 3 bytes numeric Used for Installment Payments. I3 Number Of Installments ID 2 bytes alphanumeric Number of Inbound Number Of Installments Length (value = 1 byte binary installment 3) Number Of Installments 3 bytes numeric payments that will occur. Zero-filled. Right-justified. Used for Installment Payments. I4 Amount Of Each Installment ID 2 bytes alphanumeric The amount of each Inbound Amount Of Each Installment Length 1 byte binary installment payment. (value = 12) Amount Of Each Installment 12 bytes numeric Zero-filled. Rightjustified. Two decimal places implied. Used for Installment Payments. I5 Installment Payment Number ID 2 bytes alphanumeric The number of the Inbound Installment Payment Number Length 1 byte binary installment payment. (value = 3) Installment Payment Number 3 bytes numeric Zero-filled. Rightjustified. Used for Installment Payments. I6 Frequency Of Installments ID 2 bytes alphanumeric The frequency of the Inbound Frequency Of Installments Length (value 1 byte binary installment = 1) Frequency Of Installments 1 byte alphanumeric payments. B = Bi-weekly M = Monthly W = Weekly Version 4.02 Page 276 Last modified August 12, 2009

Supplemental Data (bit 177) (Continued) Tag Field Description Field Length and Type Field Usage Inbound/ Outbound Z1 Switch Response ID 2 bytes alphanumeric Response code Outbound Switch Response Length (value = 1 byte binary value returned from 1 to 255) authorizing interface. Switch Response 1 to 255 bytes alphanumeric Version 4.02 Page 277 Last modified August 12, 2009

Promotional Program Data (bit 178) This field contains information related to promotional programs for which the card qualifies. It is a variable-length field composed of 1 or more TLV data items. Each TLV data item contains a tag identifier, data length information and the data itself. This is called TLV format. Many of the subfields are shown as having a maximum length of 255 bytes. Actual current usage may be less than 255 bytes, but the merchant is advised to code for maximum values. Keep in mind that the maximum length of the Supplemental Data field itself is 999 bytes. Important note: See Appendix D for tips on proper TLV-format coding. Tag Field Description Field Length and Type B1 Promotional Program Info 1 ID 2 bytes alphanumeric Promotional Program Info 1 Length (value = 1 to 255) 1 byte binary Promotional Program Info 1 1 to 255 bytes alphanumeric B2 Promotional Program Info 2 ID 2 bytes alphanumeric Promotional Program Info 2 Length (value = 1 to 255) 1 byte binary Promotional Program Info 2 1 to 255 bytes alphanumeric B3 Promotional Program Info 3 ID 2 bytes alphanumeric Promotional Program Info 3 Length (value = 1 to 255) 1 byte binary Promotional Program Info 3 1 to 255 bytes alphanumeric B4 Promotional Program Info 4 ID 2 bytes alphanumeric Promotional Program Info 4 Length (value = 1 to 255) 1 byte binary Promotional Program Info 4 1 to 255 bytes alphanumeric B5 Promotional Program Info 5 ID 2 bytes alphanumeric Promotional Program Info 5 Length (value = 1 to 255) 1 byte binary Promotional Program Info 5 1 to 255 bytes alphanumeric Version 4.02 Page 278 Last modified August 12, 2009

Messaging Data (bit 179) This field provides an area where the merchant and the issuer may exchange message data. It may only be used if the merchant and issuer have made a prior arrangement to do so. It is a variable-length field composed of 1 or more TLV data items. Each TLV data item contains a tag identifier, data length information and the data itself. This is called TLV format. Many of the subfields are shown as having a maximum length of 255 bytes. Actual current usage may be less than 255 bytes, but the merchant is advised to code for maximum values. Keep in mind that the maximum length of the Supplemental Data field itself is 999 bytes. Important note: See Appendix D for tips on proper TLV-format coding. Tag Field Description Field Length and Type E1 Merchant Message Data ID 2 bytes alphanumeric Merchant Message Data Length (value = 1 to 255) 1 byte binary Merchant Message Data 1 to 255 bytes alphanumeric F1 Issuer Message Data ID 2 bytes alphanumeric Issuer Message Data Length (value = 1 to 255) 1 byte binary Issuer Message Data 1 to 255 bytes alphanumeric Version 4.02 Page 279 Last modified August 12, 2009

Appendix B Key Change Message Overview Bank of America Merchant Services supports the dynamic (changed randomly) key to encrypt PINs for Debit and EBT transactions. Following are general guidelines for the dynamic key method. Master File Key A secure hardware device will be initialized with its own Master File Key (MFK), which should never be known in its entirety to any single employee of the processing company. Key Encryption Key Key Encryption Keys (KEK) are to be stored in an encrypted form using variant 0 of the device MFK. PIN Encryption Keys are sent in key change messages encrypted using variant 1 of the KEK. Message Processing Key Change Messages are used to send a unique PIN Encryption Key (KPE) to Merchant Processors. Merchant Processors are to use the KPE when creating the PIN data field in an authorization request message Bank of America Merchant Services always sends the KPE and is referred to as the master of the key change process. Whenever a new key is sent, the message also contains check digits for use in verifying the key upon receipt. The check digits are the result of encrypting 16 zeroes using the KPE in that message. A processor should send the new key and check digits to its hardware device with the appropriate command for key verification. If the check digits returned match those sent, an 0810 message with a response code value of 00 should be sent to Bank of America Merchant Services. If the check digits differ, the response code value should indicate a key synchronization error (76). Following a key change failure, Bank of America Merchant Services will send a new key change message. The old KPE should remain available for use in transaction processing until a new key has been verified. Bank of America Merchant Services requires that the merchant use the KEK and KPE provided by Bank of America Merchant Services for the express purpose of communicating with Bank of America Merchant Services. These keys or their individual components should not be used for any other processing except by accidental generation. Key Change Frequency Key change is dynamic and can therefore occur at any time. Key changes commonly occur automatically following successful processor sign on at startup and after scheduled outages. Key change messages will be sent by Bank of America Merchant Services automatically or at the request of the processor. Version 4.02 Page 280 Last modified August 12, 2009

Appendix C Protocols Supported This list contains the standard protocols supported by Bank of America Merchant Services. Contact Bank of America Merchant Services to discuss the possibility of support of protocols that do not appear here. Protocols Supported: TCP/IP SDLC SNA X.25 Bisync point-to-point Version 4.02 Page 281 Last modified August 12, 2009

Appendix D TLV-Format Processing The use of TLV-format fields, when properly coded for in the merchant s application, gives Bank of America Merchant Services the ability to add new subfields that not all merchants currently use, and protects the merchant from problems with any subfields of which they may not need or be aware. In order for this to work properly, it is very important that the merchant write their code to parse for known tags, and have the ability to skip any unknown tags. This is relatively easy to do, since each TLV entry provides a length, which the merchant can use to bypass any tags that are not identified. For example, assume a TLV format of two-byte alphanumeric tags, one-byte binary lengths and various lengths and formats of data. To start with, there are three defined tags: Tag Field Description Field Length and Type 11 Field 11 ID 2 bytes alphanumeric Field 11 Length (value = 8) 1 byte binary Field 11 8 bytes numeric 22 Field 22 ID 2 bytes alphanumeric Field 22 Length (value = 1 to 5) 1 byte binary Field 22 1 to 5 bytes alphanumeric 33 Field 33 ID 2 bytes alphanumeric Field 33 Length (value = 10) 1 byte binary Field 33 10 bytes alphabetic The merchant should code to loop through the field in the following manner (language syntax will vary): (Beginning of loop) If tag = 11 then (do whatever is needed with Field 11 for Field 11 Length bytes) Else If tag = 22 then (do whatever is needed with Field 22 for Field 22 Length bytes) Else If tag = 33 then (do whatever is needed with Field 33 for Field 33 Length bytes) Else (skip unknown data for unknown data length) If end of data is not reached, go back to beginning of loop The last else and skip are very important, as is illustrated if Bank of America Merchant Services adds a new subfield: Tag Field Description Field Length and Type 25 Field 25 ID 2 bytes alphanumeric Field 25 Length (value = 4) 1 byte binary Field 25 4 bytes numeric Now, when the merchant s logic is executed and tag 25 is encountered, it can be skipped without knowing anything about it except its format, because there is enough information provided in the field to do so: the tag is always 2 bytes and has been identified as unknown and therefore not one the merchant cares about, the next byte contains the length of the data field (4, in this example). So the entire field can be skipped with no additional coding needed to do so. Version 4.02 Page 282 Last modified August 12, 2009

Appendix D TLV-Format Processing (Continued) Also, the merchant must never assume that tags will appear in a particular order within a TLV-format field. Bank of America Merchant Services resesrves the right to send tags in any order and to change the order in which tags are sent without notice. It is very important that merchants not assume the length of a TLV-format field or tags within it. Always use the length subfields provided to determine the length of the data. Tag IDs within a given TLV-format field will, of course, be unique within that field. It may not always be true, however, that a tag ID will be unique throughout all TLV-format fields. For example, there may exist a tag Z7 in two different TLV-format fields, and their uses and values will be different. They must each be treated as unique tags. Note that some TLV-format fields will have a leading Dataset ID and Dataset length, which denotes the overall use of the field, while others omit these fields. See individual field descriptions in Appendix A for the details of each field format. Version 4.02 Page 283 Last modified August 12, 2009

Appendix E Changes to this Version of the Specification Page Change Change Description Type 14 Change Modify description of Credit Healthcare Auto-Substantiation transaction. 68 Change Modify description of bit 4. 96 Change Modify description of bit 177. 118 Change Modify description of bit 4. 120 Change Modify description of bit 177. 127 Change Modify description of bit 177. 216 Change Add value for CAT4 terminal to bit 60.1 table. 239 Change Add additional information to description of bit 95.1. 275 Change Modify field description of tag 91. 276 Add Add new tags I1-I6 in bit 177 in support of installment payments. Version 4.02 Page 284 Last modified August 12, 2009