585019496-CBE-BASE24-Eps-ISO-8583-1993-Host-External-Message-Specification
advertisement
ISO 8583:1993 Host External Message Specification BASE24-eps® Release Version Independent May 17, 2019 Notices ACI Worldwide Offices in principal cities throughout the world www.aciworldwide.com Americas +1 402 390 7600 Asia Pacific +65 6334 4843 Europe, Middle East, Africa +44 (0) 1923 816393 © Copyright ACI Worldwide, Inc. 2019 All information contained in this documentation, as well as the software described in it, is confidential and proprietary to ACI Worldwide, Inc., or one of its subsidiaries, is subject to a license agreement, and may be used or copied only in accordance with the terms of such license. Except as permitted by such license, no part of this documentation may be reproduced, stored in a retrieval system, or transmitted in any form or by electronic, mechanical, recording, or any other means, without the prior written permission of ACI Worldwide, Inc., or one of its subsidiaries. ACI, ACI Worldwide, the ACI logo, ACI Universal Payments, UP, the UP logo and all ACI product/solution names are trademarks or registered trademarks of ACI Worldwide, Inc., or one of its subsidiaries, in the United States, other countries or both. Other parties' trademarks referenced are the property of their respective owners. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 2 Contents About this publication..................................................................................................... 12 What's new in this publication........................................................................................13 Release 3.0.2 (May 2019)....................................................................................................................13 Release 3.0.1 (February 2019)............................................................................................................ 13 Release 3.0 (December 2018)............................................................................................................. 14 Release 2.1.12 (November 2018)........................................................................................................ 15 Section 1: BASE24-eps ISO 8583:1993 host external message............................................................... 16 External message components and structure......................................................................................16 BASE24-eps variations from the ISO standard....................................................................................18 BASE24-eps ISO 8583:1993 host external message licensing........................................................... 19 Configuring the external message....................................................................................................... 20 Setting up an ISO message profile............................................................................................20 Assigning the ISO Message profile to the ISO 93 Host Interface..............................................22 Message authentication code (MAC) support...................................................................................... 22 Value Added Tax (VAT) support.................................................................................................22 Network management message support............................................................................................. 23 Open account relationship (OAR) support........................................................................................... 25 Statement print transactions................................................................................................................ 25 File update transactions....................................................................................................................... 26 Card data source updates and inquiries....................................................................................26 Positive Balance data source updates...................................................................................... 29 Check Status data source updates and inquiries...................................................................... 29 Stop Payment data source updates.......................................................................................... 30 Preauthorization Hold data source update (preauthorization hold deletion)............................. 30 Interchange file updates............................................................................................................ 31 Managed list data source updates and inquiries....................................................................... 33 MDS dispute processing transactions..................................................................................................33 Visa SMS dispute transactions............................................................................................................ 38 Processing messages with no primary account number (PAN)................................................ 49 Unmatched reversals........................................................................................................................... 50 Handling request timeouts................................................................................................................... 51 Section 2: Supported message types......................................................................................................... 54 Message type documentation conventions.......................................................................................... 55 Authorization messages.......................................................................................................................56 Financial transaction messages...........................................................................................................58 File action messages........................................................................................................................... 60 Reversal messages..............................................................................................................................62 Administrative messages..................................................................................................................... 64 Network management messages.........................................................................................................64 Product-specific messages.................................................................................................................. 65 Section 3: Data element defaults.................................................................................................................67 Bit map presence indicator codes........................................................................................................ 67 Authorization Request/Repeat (MTI 1100/1101).................................................................................. 68 Authorization Request Response (MTI 1110).......................................................................................68 Authorization Advice/Repeat (MTI 1120/1121).....................................................................................70 BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 3 Contents Authorization Advice Response (MTI 1130).........................................................................................74 Authorization Notification (MTI 1140)................................................................................................... 76 Financial Request/Repeat (MTI 1200/1201)........................................................................................ 79 Financial Request Response (MTI 1210).............................................................................................81 Financial Advice/Repeat (MTI 1220/1221)...........................................................................................84 Financial Advice Response (MTI 1230)............................................................................................... 87 Financial Notification (MTI 1240)......................................................................................................... 90 File Action Request/Repeat (MTI 1304/1305)......................................................................................92 File Action Request Response (MTI 1314).......................................................................................... 97 File Action Advice/Repeat (MTI 1324)................................................................................................. 98 File Action Advice Response (MTI 1334).............................................................................................98 Reversal Advice/Repeat (MTI 1420/1421)........................................................................................... 99 Chargeback Advice (MTI 1422)......................................................................................................... 103 Chargeback Advice Repeat (MTI 1423).............................................................................................105 Reversal Advice Response (MTI 1430)............................................................................................. 108 Chargeback Advice Response (MTI 1432)........................................................................................ 110 Reversal Notification (MTI 1440)........................................................................................................112 Chargeback Notification (MTI 1442)...................................................................................................114 Administrative Request (MTI 1604)....................................................................................................117 Administrative Request Response (MTI 1614)...................................................................................118 Administrative Notification (MTI 1644)............................................................................................... 118 Network Management Request/Repeat (MTI 1804/1805)..................................................................119 Network Management Request Response (MTI 1814)......................................................................120 Administrative Fraud Report (MTI 9620)............................................................................................121 Administrative Fraud Report Response (MTI 9630)...........................................................................122 Section 4: Data element definitions.......................................................................................................... 123 General data element specifications.................................................................................................. 123 Fixed-length data elements..................................................................................................... 123 Variable-length data elements.................................................................................................123 Zero-length data elements...................................................................................................... 124 Tagged and subtagged data....................................................................................................124 Generic data mapping............................................................................................................. 125 Data element documentation conventions......................................................................................... 125 P-1: Secondary Bit Map..................................................................................................................... 127 P-2: Primary Account Number........................................................................................................... 127 P-3: Processing Code........................................................................................................................ 127 Transaction codes supported by BASE24-eps........................................................................128 From and To account types supported by BASE24-eps..........................................................132 P-4: Amount, Transaction...................................................................................................................133 P-5: Amount, Reconciliation...............................................................................................................134 P-7: Transmission Date and Time......................................................................................................134 P-9: Conversion Rate, Reconciliation................................................................................................ 135 P-6: Amount, Cardholder Billing.........................................................................................................135 P-10: Conversion Rate, Cardholder Billing........................................................................................ 135 P-11: Systems Trace Audit Number................................................................................................... 136 P-12: Date and Time, Local Transaction............................................................................................136 P-13: Date, Effective.......................................................................................................................... 136 P-14: Date, Expiration........................................................................................................................ 136 P-15: Date, Settlement.......................................................................................................................137 P-16: Date, Conversion......................................................................................................................137 P-17: Date, Capture........................................................................................................................... 137 P-18: Merchant Type..........................................................................................................................138 P-19: Country Code, Acquiring Institution.......................................................................................... 138 BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 4 Contents P-21: Country Code, Forwarding Institution....................................................................................... 138 P-22: Point of Service Data Code...................................................................................................... 138 P-23: Card Sequence Number...........................................................................................................143 P-24: Function Code.......................................................................................................................... 143 Function codes supported by BASE24-eps.............................................................................144 P-25: Message Reason Code............................................................................................................ 149 Message reason codes supported by BASE24-eps................................................................149 P-26: Card Acceptor Business Code................................................................................................. 155 P-27: Approval Code Length..............................................................................................................155 P-28: Date, Reconciliation..................................................................................................................155 P-29: Reconciliation Indicator............................................................................................................ 155 P-30: Amounts, Original..................................................................................................................... 156 P-32: Acquirer Institution ID Code......................................................................................................156 P-33: Forwarding Institution ID Code................................................................................................. 156 P-34: Primary Account Number, Extended........................................................................................ 157 P-35: Track 2 Data............................................................................................................................. 157 P-36: Track 3 Data............................................................................................................................. 157 P-37: Retrieval Reference Number.................................................................................................... 158 P-38: Approval Code..........................................................................................................................158 P-39: Action Code.............................................................................................................................. 158 P-40: Service Code............................................................................................................................ 164 P-41: Card Acceptor Terminal Identification.......................................................................................164 P-42: Card Acceptor Identification Code............................................................................................164 P-43: Card Acceptor Name/Location................................................................................................. 165 P-44: Additional Response Data........................................................................................................ 167 P-45: Track 1 Data............................................................................................................................. 168 P-46: Amounts, Fees......................................................................................................................... 168 P-48: Additional Data – Private Data Element................................................................................... 170 P-48: Tag 01, PayPass Mapping Information.......................................................................... 171 P-48: Tag 02, Account Detail...................................................................................................172 P-48: Tag 03, Multiple Account Inquiry....................................................................................173 P-48: Tag 04, Billpay Inquiry....................................................................................................174 P-48: Tag 05, e-Wallet Data.................................................................................................... 174 P-49: Currency Code, Transaction.....................................................................................................175 P-50: Currency Code, Reconciliation................................................................................................. 175 P-51: Currency Code, Cardholder Billing........................................................................................... 176 P-52: Personal Identification Number (PIN) Data.............................................................................. 176 P-54: Amounts, Additional..................................................................................................................176 P-55: Integrated Circuit Card System Related Data.......................................................................... 178 P-56: Original Data Elements.............................................................................................................182 P-57: Authorization Life Cycle Code.................................................................................................. 182 P-58: Authorizing Agent Institution ID Code.......................................................................................183 P-59: Transport Data..........................................................................................................................183 P-60: CSM Reserved......................................................................................................................... 183 P-62: Primary Reserved Private.........................................................................................................184 P-62: Tag 01, PIN Change – PIN Offset..................................................................................184 P-62: Tag 02, PIN Change – Encrypted PIN........................................................................... 184 P-62: Tag 03, Depository Type................................................................................................ 185 P-62: Tag 04, Terminal Branch................................................................................................ 185 P-62: Tag 05, Terminal Region................................................................................................ 185 P-62: Tag 06, Multiple Account Select Indicator......................................................................186 P-62: Tag 07, Transaction Originator.......................................................................................186 P-62: Tag 08, Instrument Type................................................................................................ 186 P-62: Tag 09, Visa Data.......................................................................................................... 186 P-62: Tag 0A, Acquirer and Issuer Network ID........................................................................189 BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 5 Contents P-62: Tag 0B, MasterCard Original Advice Data..................................................................... 189 P-62: Tag 0C, Strong Cardholder Authentication (SCA) Indicators.........................................190 P-62: Tag 0D, Strong Cardholder Authentication (SCA) Exemptions .....................................190 P-62: Tag 10, Fee Program Indicator...................................................................................... 190 P-62: Tag 11, Merchant Region...............................................................................................190 P-62: Tag 12, Merchant Group................................................................................................ 191 P-62: Tag 13, Additional Statement Print Information............................................................. 191 P-62: Tag 14, Context Cookie................................................................................................. 192 P-62: Tag 15, Non-Currency Dispense....................................................................................192 P-62: Tag 16, Network Original Processing Code................................................................... 192 P-62: Tag 17, Acquiring Interface Name................................................................................. 192 P-62: Tag 18, Channel Time Offset......................................................................................... 192 P-62: Tag 19, Original PVV..................................................................................................... 193 P-62: Tag 20, Acquirer Institution ID/Logical Network............................................................. 193 P-62: Tag 21, Issuer Institution ID/Logical Network.................................................................193 P-62: Tag 22, Digital Audio Service (DAS) Indicator............................................................... 194 P-62: Tag 23, Capture Mode................................................................................................... 194 P-62: Tag 24, Network ID........................................................................................................ 194 P-62: Tag 25, Card Level Results............................................................................................194 P-62: Tag 26, Program Identification....................................................................................... 195 P-62: Tag 27_ Invoice Number................................................................................................195 P-62: Tag 30, Merchant ID...................................................................................................... 195 P-62: Tag 31, Cross-Border Transaction Pricing..................................................................... 195 P-62: Tag 32, Switch Acquirer ID............................................................................................ 196 P-62: Tag 33, Promotion Data................................................................................................. 196 P-62: Tag 34, Contact Information...........................................................................................197 P-62: Tag 35, Intra-Country Data - Japan............................................................................... 198 P-62: Tag 36, Free Format Text...............................................................................................198 P-62: Tag 38, Source of Funds................................................................................................198 P-62: Tag 39, Business Application ID.................................................................................... 199 P-62: Tag 40, Sender Data (Original Credits)..........................................................................199 P-62: Tag 41, Market-Specific Data.........................................................................................200 P-62: Tag 42, Acquirer Reference Data, Transaction Identifier............................................... 200 P-62: Tag 43, Visa Risk Information........................................................................................ 201 P-62: Tag 44, Advanced Authorization Service Data.............................................................. 201 P-62: Tag 51, Bunch Note Acceptor Indicator......................................................................... 203 P-62: Tag 52, PRM Response.................................................................................................203 P-62: Tag 53, Voice Referral Indicator.....................................................................................204 P-62: Tag 54, Fraud Indicator..................................................................................................205 P-62: Tag 55, AS2805 National Data...................................................................................... 205 P-62: Tag 56, Transaction Description.................................................................................... 206 P-62: Tag 57, Address Change Notification............................................................................ 207 P-62: Tag 58, Batch Authorization...........................................................................................207 P-62: Tag 59, Subscription Indicator....................................................................................... 207 P-62: Tag 60, Voice Authorization Indicator............................................................................ 208 P-62: Tag 61, Switch Assigned ID........................................................................................... 208 P-62: Tag 62, Generic Risk Data.............................................................................................208 P-62: Tag 63, Informational Text..............................................................................................216 P-62: Tag 65, Money Transfer Data........................................................................................ 216 P-62: Tag 66, Watch List Management Data...........................................................................221 P-62: Tag 67, Visa Merchant Verification Value.......................................................................222 P-62: Tag 68, Banknet Reference Number............................................................................. 222 P-62: Tag 69, Dynamic Currency Conversion Indicator.......................................................... 223 P-62: Tag 70, Trace ID............................................................................................................ 223 P-62: Tag 71, Transit Program................................................................................................ 223 BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 6 Contents P-62: Tag 72, Authorizing Agent ID Code............................................................................... 223 P-62: Tag 73, Charity Giving Information................................................................................ 224 P-62: Tag 74, Unformatted Visa Text.......................................................................................224 P-62: Tag 76, Fraud Notification Information...........................................................................224 P-62: Tag 77, Customer 1 ID...................................................................................................225 P-62: Tag 78, Customer 2 ID...................................................................................................226 P-62: Tag 79, Visa V.me Data ................................................................................................ 226 P-62: Tag 80, Bank ID............................................................................................................. 227 P-62: Tag 82, PIN Data .......................................................................................................... 227 P-62: Tag 83, Preauth Sequence Number.............................................................................. 228 P-62: Tag 84, Authorization Message Indicator.......................................................................228 P-62: Tag 85, Acquirer Transaction ID.................................................................................... 228 P-62: Tag 86, Card Acceptor ID Code.....................................................................................228 P-62: Tag 87, Pseudo Terminal Identifier................................................................................ 229 P-62: Tag 88, VisaNet Data Element 48..................................................................................229 P-62: Tag 89, Security Control Information............................................................................. 229 P-62: Tag 90, Key Index.......................................................................................................... 229 P-62: Tag 91, Multi Clearing Sequence...................................................................................229 P-62: Tag 92, SPAN2 Data......................................................................................................229 P-62: Tag 93, Source Original Data.........................................................................................230 P-62: Tag 94, Additional Merchant Data..................................................................................230 P-62: Tag 95, Mixed Media Deposits.......................................................................................230 P-62: Tag 96, EMV Application PAN Sequence Number (APSN)........................................... 231 P-62: Tag 97, Log Only Transaction Description..................................................................... 231 P-62: Tag 98, Acquirer Amount Data.......................................................................................231 P-64: Primary Message Authentication Code.................................................................................... 232 S-66: Amounts, Original Fees............................................................................................................ 232 S-67: Extended Payment Data...........................................................................................................234 S-68: Country Code, Receiving Institution......................................................................................... 234 S-70: Country Code, Authorizing Agent Institution.............................................................................234 S-71: Message Number..................................................................................................................... 235 S-72: Data Record............................................................................................................................. 235 S-72: Tag 01, Card Data Source Updates and Inquiries......................................................... 235 S-72: Tag 02, Positive Balance Data Source Updates............................................................ 267 S-72: Tag 04, Negative File Updates (Star Systems and Visa DPS)...................................... 279 S-72: Tag 05, Visa Stop Payment Order................................................................................. 284 S-72: Tag 06, Visa Card Recovery Bulletin............................................................................. 287 S-72: Tag 07, Banknet File Updates........................................................................................289 S-72: Tag 10, Preauthorization Hold Deletion Information...................................................... 298 S-72: Tag 11, RuPay File Updates.......................................................................................... 299 S-72: Tag 13, AEGN Negative File Updates........................................................................... 299 S-72: Tag 14, NYCE Negative File Updates............................................................................299 S-72: Tag 15, Fifth Third ISO Interface Response Code.........................................................300 S-72: Tag 16, SHAZAM Interface File Updates.......................................................................301 S-72: Tag 17, NETS Negative File Updates............................................................................ 302 S-72: Tag 18, Presto (Publix) Negative File Updates.............................................................. 303 S-72: Tag 19, EPOC Interface File Updates............................................................................304 S-72: Tag 20, MDS Dispute Processing Data......................................................................... 306 S-72: Tag 21, CO-OP File Updates......................................................................................... 307 S-72: Tag 22, MasterCard Debit System (MDS) File Updates................................................ 308 S-72: Tag 23, e-rsb File Updates.............................................................................................315 S-72: Tag 24, PRICE File Updates..........................................................................................317 S-72: Tag 25, SPAN2 Dispute Processing Identifier................................................................319 S-72: Tag 26, Check Status Data Source Updates and Inquiries............................................319 S-72: Tag 27, Stop Payment Data Source Updates and Inquiries.......................................... 321 BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 7 Contents S-72: Tag 28, Visa Dispute Data............................................................................................. 325 S-72: Tag 34, Managed List Data............................................................................................326 S-72: Tag 35, Customer Table.................................................................................................329 S-72: Tag 36, Customer Card Relation Table..........................................................................354 S-72: Tag 48, Elan File Update Information............................................................................ 355 S-72: Tag 49, FIS ISO File Update..........................................................................................356 S-72: Tag 50, Interac Exceptions Browser Information........................................................... 357 S-72: Tag 51, Application PAN Relation Data Source Updates...............................................357 S-72: Tag 52, CUP Stand-in Parameter Update......................................................................358 S-72: Tag 53, Visa Token File..................................................................................................359 S-72: Tag 54_Visa PAN File.................................................................................................... 360 S-72: Tag 99, Failed Message Data........................................................................................ 360 S-72: Tag BB, Reserved..........................................................................................................361 S-93: Transaction Destination Institution Identification Code.............................................................361 S-94: Transaction Originator Institution Identification Code............................................................... 361 S-96: Key Management Data.............................................................................................................361 S-100: Receiving Institution Identification Code.................................................................................363 S-102: Account Identification 1.......................................................................................................... 363 S-103: Account Identification 2.......................................................................................................... 363 S-123: Reserved for Private Use....................................................................................................... 363 S-123: Tag 01, Address Verification Data................................................................................364 S-123: Tag 02, Card Verification Data..................................................................................... 368 S-123: Tag 03, Manual CVD (CVD2).......................................................................................371 S-123: Tag 04, Manual CID..................................................................................................... 371 S-123: Tag 05, Visa CPS Data................................................................................................ 371 S-123: Tag 06, MasterCard Interchange Compliance Information.......................................... 376 S-123: Tag 07, E-Commerce Indicator.................................................................................... 377 S-123: Tag 08, Secure Internet Validation...............................................................................378 S-123: Tag 09, Secure E-Commerce Data..............................................................................379 S-123: Tag 10, UCAF Data......................................................................................................380 S-123: Tag 11, Recurring Payment Indicator...........................................................................382 S-123: Tag 12, Point of Service Additional.............................................................................. 382 S-123: Tag 13, Visa Indicator.................................................................................................. 384 S-123: Tag 14, Internet IP Address......................................................................................... 385 S-123: Tag 15, Merchant Advice Code....................................................................................385 S-123: Tag 16, American Express Customer ID Number........................................................385 S-123: Tag 17, American Express Auto Rental Data.............................................................. 386 S-123: Tag 18, American Express Lodging Data.................................................................... 387 S-123: Tag 19, American Express General Retail Data.......................................................... 388 S-123: Tag 20, American Express Restaurant Data................................................................389 S-123: Tag 21, American Express Oil Data.............................................................................391 S-123: Tag 22, Terminal Type..................................................................................................392 S-123: Tag 23, OAR Maximum Accounts Data....................................................................... 393 S-123: Tag 24, Acquirer Interface Action Code....................................................................... 393 S-123: Tag 25, Issuer Interface Action Code...........................................................................393 S-123: Tag 26, Prepay Transaction Data................................................................................ 393 S-123: Tag 27, Language Code.............................................................................................. 394 S-123: Tag 29, International Service Assessment Flag...........................................................394 S-123: Tag 30, Partial Authorization Indicator......................................................................... 395 S-123: Tag 31, Visa Gateway Transaction Identifier............................................................... 395 S-123: Tag 32, Purchase Amount Only Indicator.................................................................... 396 S-123: Tag 33, Dynamic Card Verification Results..................................................................396 S-123: Tag 35, Voice Authorization Transaction Identification................................................ 397 S-123: Tag 36, EMV Status Data............................................................................................ 398 S-123: Tag 37, MDS Intermediate Network Facility Data........................................................ 401 BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 8 Contents S-123: Tag 38, MDS Network Data......................................................................................... 401 S-123: Tag 39, MDS Processor Private Data.......................................................................... 401 S-123: Tag 40, Acquirer Forwarding Institution Identification.................................................. 401 S-123: Tag 41, Issuer Capture Date........................................................................................401 S-123: Tag 42, MasterCard POS Entry Mode......................................................................... 402 S-123: Tag 43, MasterCard POS PIN Capture Mode..............................................................402 S-123: Tag 44, MasterCard POS Data.................................................................................... 402 S-123: Tag 45, AMEX POS Data Code................................................................................... 402 S-123: Tag 46, Mastercard On-behalf Services Data..............................................................403 S-123: Tag 47, MasterCard On-behalf Services Issuer Chip Authentication Data.................. 403 S-123: Tag 48, MasterCard On-behalf Services Chip CVR/TVR Bit Error Results................. 403 S-123: Tag 49, Dynamic Card Verification Authorization System ATC Value..........................404 S-123: Tag 50, Dynamic Card Verification ATC Synchronization Digits.................................. 404 S-123: Tag 51, Dynamic Card Verification Regenerated ATC.................................................404 S-123: Tag 52, Dynamic Card Verification ATC Discrepancy Indicator................................... 404 S-123: Tag 53, Dynamic Card Verification ATC Discrepancy Value........................................ 405 S-123: Tag 54, Destination Customer Name...........................................................................405 S-123: Tag 55, Billpay Information.......................................................................................... 405 S-123: Tag 56, Additional Payment Information...................................................................... 405 S-123: Tag 57, Shipping Information....................................................................................... 409 S-123: Tag 58, Internet Information.........................................................................................409 S-123: Tag 59, Travel and Entertainment Information.............................................................410 S-123: Tag 60, Installment Payment Information.....................................................................411 S-123: Tag 61, MICR Data...................................................................................................... 412 S-123: Tag 62, Check Retention Flag..................................................................................... 412 S-123: Tag 63, Transaction Subtype....................................................................................... 413 S-123: Tag 64, Discover Clearing Data................................................................................... 413 S-123: Tag 65, Retail Class Code........................................................................................... 413 S-123: Tag 66, PRICE Transaction Block ID........................................................................... 414 S-123: Tag 67, PRICE Commission Information..................................................................... 414 S-123: Tag 69, Split Deposit Amount...................................................................................... 414 S-123: Tag 70, Additional Verification Information...................................................................415 S-123: Tag 71, MasterCard Authorization Advice Date/Time.................................................. 416 S-123: Tag 72 Pre-Pay Generic Receipt Data.........................................................................416 S-123: Tag 73, Pre-Pay Top-Up Receipt Data.........................................................................417 S-123: Tag 74, Pre-Pay Top-Up Data......................................................................................417 S-123: Tag 75, Pre-Pay Response Data................................................................................. 421 S-123: Tag 76, Pre-Pay Voucher Format 1 Receipt Data........................................................423 S-123: Tag 77, Pre-Pay Online Receipt Data..........................................................................423 S-123: Tag 78, Inventory Voucher Data.................................................................................. 424 S-123: Tag 79, MasterCard Program Participation Indicator...................................................425 S-123: Tag 80, Member to Member Data................................................................................ 426 S-123: Tag 81, Stored Value Pre-Registered Service Indicator.............................................. 426 S-123: Tag 82, MasterCard POS Transaction Status Indicator............................................... 427 S-123: Tag 83, MasterCard Promotion Code.......................................................................... 427 S-123: Tag 84, Five Digit Card Security Code.........................................................................427 S-123: Tag 85, Payment Initiation Channel Information.......................................................... 427 S-123: Tag 86, Visa Custom Payment Service Additional Data.............................................. 427 S-123: Tag 87, China UnionPay (CUP) Data.......................................................................... 429 S-123: Tag 88, NYCE Data..................................................................................................... 434 S-123: Tag 89, Visa Data........................................................................................................ 435 S-123: Tag 90, Additional Card Data Input Capability............................................................. 436 S-123: Tag 91, Brazil BNDES Transactions............................................................................ 436 S-123: Tag 92, MasterCard Installment Data.......................................................................... 438 S-123: Tag 93, Mobile Payment Data......................................................................................439 BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 9 Contents S-123: Tag 94, Airline Industry-Specific Data..........................................................................439 S-123: Tag 95, Passenger Transport Ancillary Data............................................................... 441 S-123: Tag 96, Network Token Service................................................................................... 444 S-123: Tag 97, CUP Recurring Data....................................................................................... 451 S-123: Tag 98, Region Specific Payment Data....................................................................... 452 S-123: Tag 99, Healthcare Services........................................................................................455 S-123: Tag 0A, PULSE Data................................................................................................... 456 S-123: Tag 0B, American Express Additional Card Information..............................................456 S-123: Tag 0C, Security Services............................................................................................457 S-123: Tag 0D, MasterCard Indicators.................................................................................... 457 S-123: Tag 0E, Authentication Indicator.................................................................................. 458 S-123: Tag 0F, Merchant On-Behalf Services......................................................................... 458 S-123, Tag 0G, Time Validation Information............................................................................458 S-123: Tag 0H, Transaction Integrity Class............................................................................. 458 S-123: Tag 0I, STAR Access Data.......................................................................................... 459 S-123: Tag 0J, Advice Reason Detail Code............................................................................ 460 S-123: Tag 0M, Secure E-commerce Indicators......................................................................460 S-123: Tag 0N, RuPay e-Commerce Indicators...................................................................... 461 S-123: Tag 0P, Terminal Conversion Rate...............................................................................461 S-124: Reserved for Private Use....................................................................................................... 462 S-124: Tag 01, Acquirer Data ................................................................................................. 462 S-124: Tag 02_HISO 1993 Data..............................................................................................464 S-124: Tag 03, Visa Data........................................................................................................ 464 S-124: Tag 04, MasterCard Data.............................................................................................465 S-124: Tag 05, CBAE Data......................................................................................................466 S-124: Tag 06, Fraud Enhanced Data.....................................................................................466 S-124: Tag 08, PROSA Data...................................................................................................467 S: 124: Tag 09, LINK LIS5.......................................................................................................467 S-124: Tag 10, RuPay............................................................................................................. 468 S-124: Tag 11, Additional Cardholder Verification................................................................... 470 S-124:Tag 12, SAMA SPAN2 Data..........................................................................................470 S-124: Tag 13, FIS PayNet Payment Data..............................................................................471 S-124: Tag 14, FIS DE-109 Data.............................................................................................471 S-124: Tag 15, FIS DE-110 Data.............................................................................................473 S-124: Tag 16, FDR 184 Data................................................................................................. 475 S-127: Reserved for Private Use....................................................................................................... 475 S-127: Tag 01, Statement Print Data.......................................................................................476 S-127: Tag 02, Open Account – From.....................................................................................477 S-127: Tag 03, Open Account – To......................................................................................... 478 S-127: Tag 04, Fleet Card Data...............................................................................................479 S-127: Tag 05, Fleet Product Codes....................................................................................... 480 S-127: Tag 06, Fleet Tax Data.................................................................................................482 S-127: Tag 07, MasterCard Fleet Data....................................................................................485 S-127: Tag 08, Visa Fleet Data............................................................................................... 486 S-127: Tag 10, Card Data Source Updates and Inquiries....................................................... 487 S-127: Tag 11, Card Data Source CSM Buffer........................................................................ 487 S-127: Tag 12, Positive Balance Data Source CSM Buffer.....................................................488 S-127: Tag 13, Visa Fleet Additional Data...............................................................................488 S-127: Tag 14, Check Status Inquiry Response Data............................................................. 489 S-127: Tag 15, Stop Payment Inquiry Response Data............................................................489 S-127: Tag 16, Context Cookie Data.......................................................................................490 S-127: Tag 17, CARDNET Data.............................................................................................. 490 S-127: Tag 18, CARDNET Payment Data...............................................................................491 S-127: Tag 19, Cancellation/Return Category.........................................................................492 S-127: Tag 20, JIS2 Track....................................................................................................... 492 BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 10 Contents S-127: Tag 21, Visa Fleet Data for Commercial Card Data.....................................................492 S-127: Tag 22, Visa Fleet Data for Expanded Non-Fuel......................................................... 493 S-127: Tag 24, CBAE Additional Response Data....................................................................496 S-127: Tag 25, CBAE Additional National Data.......................................................................496 S-127: Tag 26, CBAE National Data....................................................................................... 497 S-127: Tag 27, CBAE Funds Transfer Data............................................................................ 498 S-127: Tag 29, Italian Security Information............................................................................. 499 S-127: Tag 30, Italian Identifier ...............................................................................................499 S-128: Secondary Message Authentication Code............................................................................. 500 BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 11 About this publication This publication contains specifications for the BASE24-eps® ISO 8583:1993 host external message, which is the message the BASE24-eps system supports for communicating with ISO 8583:1993-based host processors. The BASE24-eps ISO 8583:1993 host external message specifications are based on the ISO 8583:1993 message standards developed by the International Organization for Standardization (ISO). Audience This manual is a reference source for persons responsible for the message interface between an ISO 8583:1993based host and the BASE24-eps system. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 12 What's new in this publication Here is what’s new in this publication. Release 3.0.2 (May 2019) Here are the topics and changes made for release 3.0.2. Managed list data source updates and inquiries Adds new section about performing file updates using file partitioning. Authorization Advice/Repeat (MTI 1120/1121) Adds data element 54. P-62: Tag 0C, Strong Cardholder Authentication (SCA) Indicators Adds tag 0C and subtags 01-03 to support strong cardholder authentication (SCA) indicators. P-62: Tag 0D, Strong Cardholder Authentication (SCA) Exemptions Adds tag 0D and subtags 01-07 to support strong cardholder authentication (SCA) exemptions. S-96: Key Management Data Updates the description for tag 04 to indicate that the key length for TR-31 Key Block is either 80 or 96. S-123: Tag 07, E-Commerce Indicator Adds indicator value I for e-commerce 3DS 2.0 transactions. Release 3.0.1 (February 2019) Here are the topics and changes made for release 3.0.1. Reversal Advice/Repeat (MTI 1420/1421) Adds data element 54 as conditional for MTI 1420/1421 messages. Message reason codes supported by BASE24-eps Adds code 1776 (Request - deferred authorization). P-22: Point of Service Data Code Redefines value 8 of Position 8 - Cardholder AUthentication Method to E-commerce or mobile. S-96: Key Management Data • • Updates the format of tag 02 to AN1. Adds data to tag 04 about how to determine if the key is a TR-31 key block key. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 13 What's new in this publication S-123: Tag 12, Point of Service Additional Adds values 4 and 5 to position 8. S-123: Tag 13, Visa Indicator Expands the length to 7 characters to add the Visa Special Conditions Code and Digitial Commerce Indicator. S-123: Tag 60, Installment Payment Information Adds tags 26 - 32 for AMEX GNS to process deffered payment plans. S-123: Tag 81, Stored Value Pre-Registered Service Indicator Updates tag 81 to allow multiple valid values. S-123: Tag 83, MasterCard Promotion Code Adds additional supported values and clarifies values used for incoming messages. S-123: Tag 84, Five Digit Card Security Code Updates the values that are supported. S-123: Tag 87, China UnionPay (CUP) Data Updates the length of subtag 42, Usage ML: Multi Language Merchant Name and Address, to ANS 80. S-123: Tag 95, Passenger Transport Ancillary Data Corrects the length of subtag OE to AN..108. S-123: Tag 96, Network Token Service • • • • Adds SAMA SPAN2 mapping. Adds subtag 1J - Token update reason text. Adds to subtag 28, new value 0 = failed. Changes the length of subtag 36 to AN 8. S-123: Tag 98, Region Specific Payment Data Adds subtags 32 and 33. Release 3.0 (December 2018) Following are the topics and the changes made for release 3.0. S-124: Tag 13, FIS PayNet Payment Data Adds this new tag. S-124: Tag 14, FIS DE-109 Data Adds this new tag. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 14 What's new in this publication S-124: Tag 15, FIS DE-110 Data Adds this new tag. Release 2.1.12 (November 2018) Here are the topics and changes made for release 2.1.12. P-62: Tag 79, Visa V.me Data Subtag 02 (Additional Authorization Method) is now reserved for future use. P-62: Tag 83 Preauth Sequence Number Redefines the length from AN 12 to AN .. 12. S-123: Tag 96, Network Token Service Adds information about the SAMA SPAN2 interface and subtags 1G, 1H, and 1I. S-124: Tag 16, FDR 184 Data Adds this new tag. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 15 Section 1: BASE24-eps ISO 8583:1993 host external message BASE24-eps ISO 8583:1993 host external message The BASE24-eps ISO 8583:1993 host external message is the message the BASE24-eps system supports for exchanging transaction information with ISO 8583:1993-based host systems. The BASE24-eps ISO 8583:1993 host external message specifications are based on the ISO 8583:1993 message standards developed by the International Organization for Standardization (ISO). The message is a variable-length, variable-content message that can be configured based on the type of message being sent. Note: The BASE24-eps ISO 8583:1993 host external message is the message used by the BASE24-eps ISO 93 Host Interface component. For information about this interface, see the BASE24-eps ISO Host Interface User Guide. External message components and structure The BASE24‑eps ISO 8583:1993 host external message is made up of a message type identifier, primary bit map, and data element, structured as shown below. BASE24-eps ISO 8583:1993 host external message components Component Length Required Message type identifier 4 bytes Yes Primary bit map 16 bytes Yes Data elements Variable length Based on the message type Message type identifier The message type identifier is a four-digit code identifying the general function of the message. It is required in all messages. Refer to “Supported Message Types” or “Data Element Defaults” for additional information about the message types supported by BASE24-eps Primary bit map The primary bit map is a 16-position field required in all messages. It represents 64 bits of data used to identify the presence (denoted by 1 or bit on) or absence (denoted by 0 or bit off) of the first 64 data elements in the message. Sixty-four bits are converted to and from 16 bytes of display data using hexadecimal (hex) equivalents. It is the hexadecimal equivalents that are carried in the bit map of the external message. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 16 BASE24-eps ISO 8583:1993 host external message To convert 64 bits to 16 bytes, the 64 bits are first divided into 16 groups of four. Then, each group of four bits is assigned a hexadecimal equivalent according to the following table. Conversion table Bit value Hex value Bit value Hex value 0000 0 1000 8 0001 1 1001 9 0010 2 1010 A 0011 3 1011 B 0100 4 1100 C 0101 5 1101 D 0110 6 1110 E 0111 7 1111 F The following is an illustration of how 64 bits are converted to 16 bytes for placement in the external message. Bits are numbered from left to right, starting with 1. In the example, the bit map would contain 221A430005236FBD. There are two bit maps used in the BASE24‑eps ISO 8583:1993 host external message: the primary bit map and the secondary bit map. The primary bit map controls the presence or absence of data elements 1 through 64. The secondary bit map controls the presence or absence of data elements 65 through 128. The primary bit map precedes the data elements in a message. The secondary bit map is itself a data element (P-1) and its existence is controlled by the primary bit map. When present, it immediately follows the primary bit map. Data elements The BASE24‑eps ISO 8583:1993 host external message allows for the transmission of all 128 data elements that are a part of the ISO 8583:1993 standard. Not all of these data elements are used for processing by BASE24-eps, however. In fact, many times only a small number are required. A primary advantage of the BASE24‑eps ISO 8583:1993 host external message is that a data element need not be included in the external message if it is not needed for processing. Hosts are given the option of configuring the data elements in their messages—within the bounds of BASE24-eps and ISO processing requirements—such that only those elements needed are included. Refer to “Data Element Defaults” for a summary of the data elements required by BASE24-eps. Refer to “Data Element Definitions” for detailed information about each data element. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 17 BASE24-eps ISO 8583:1993 host external message BASE24-eps variations from the ISO standard The BASE24‑eps ISO 8583:1993 host external message varies from the ISO standard in several respects. Binary data transmission The BASE24‑eps ISO 8583:1993 host external message varies from the ISO standard in that it does not use binary data fields. Several elements in the ISO external message have been standardized as binary fields, but the BASE24-eps external message is sent entirely in character format. This is because BASE24-eps does not support transparent communications with its hosts, so the use of binary data could cause the unintentional introduction of control characters into the data transmission stream. Also, a predominant number of hosts expect their data in Extended Binary Coded Decimal Interchange Code (EBCDIC) code, but the native code of some BASE24-eps platforms is ASCII. With the message entirely in character format, the translation from ASCII to EBCDIC and back can be performed by a communications controller. If some data fields in the message were binary, the translation would have to be performed by the BASE24-eps application, which would require CPU rather than controller resources. The ISO data elements affected by BASE24-eps external message being sent entirely in character format are as follows: • • • • • Primary and secondary bit maps S-128: Secondary Message Authentication Code P-64: Primary Message Authentication Code P-52: Personal Identification Number (PIN) Data S-96: Key Management Data_DO_NOT_USE Rejected messages The ISO 8583:1993 standard does not specify a procedure for identifying rejected messages. BASE24-eps requires specific handling for rejected messages. If the BASE24-eps ISO 93 Host Interface component or the host receives an external message that it cannot process because of a severe data format error, it rejects the message as follows: • • • Changes the message type to 1644 (Administrative Notification). Sets Tag 99 (Failed Message Data) in S-72 Data Record with the first 999 bytes of the message that could not be parsed. Returns the message to the sender (either the BASE24-eps ISO 93 Host Interface component returns the message to the host, or the host returns the message to the BASE24-eps system). Text-level acknowledgments are not to be sent in response to receipt of a 1644 message. Note: These actions are taken on any message type that cannot be processed, not just those that require a response. Primary Account Number (P-2) and Extended Primary Account Number (P-34) data elements The ISO 8583:1993 standard requires either the Primary Account Number (P-2) data element or the Extended Primary Account Number (P-34) data element for all authorization, financial transaction, and reversal messages. • • When the primary account numbers do not begin with the digits 59, the ISO 8583:1993 standard requires data element P-2. When the primary account numbers do begin with the digits 59, the ISO 8583:1993 standard requires data element P-34. BASE24-eps also uses data element P-2 or P-34 for the primary account number, depending on the length of the primary account number. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 18 BASE24-eps ISO 8583:1993 host external message • • If the primary account number contains up to 19 digits, P-2 is used. If the primary account number contains more than 19 digits or starts with the digits 59, P-34 is used. Processing Code (P-3) data element BASE24-eps supports alphanumeric characters in the Processing Code (P-3) data element instead of the strict numeric characters prescribed by the ISO 8583:1993 standard. Card Acceptor Terminal Identification (P-41) data element The P-41: Card Acceptor Terminal Identification data element value is 16 positions in length rather than the eight positions prescribed by ISO. This length allows for the 16-position channel IDs supported by BASE24-eps. Private use data elements The ISO 8583:1993 standard includes several private use data elements that can be defined in any manner by an organization implementing the standard. BASE24-eps products use a number of these data elements to carry pieces of information that are required for processing by BASE24-eps applications but are not specifically defined by the ISO 8583:1993 standard. These data elements include the following: • • • • P-62: Primary Reserved Private S-123: Reserved for Private Use Reserved for Private Use - 124 (S-124) Reserved for Private Use - 127 (S-127) Note: BASE24-eps has reserved the P-60: CSM Reserved data element for use in customer specific modifications (CSMs). BASE24-eps ISO 8583:1993 host external message licensing The following three licensing modules are provided to package BASE24‑eps ISO 8583:1993 host external message functionality for different ACI customer requirements. The module IDs are provided in parentheses. • • • BASE24-eps ISO Host Interface (BASE24-eps ISO 1993 format) ( x EE-IS300) File Update Interface ( x EE-SE450) ACI Generic File Update Interface to BASE24-eps ( x EE-SE452) The x in the module identifier is a character representing the hardware platform on which the module is run. Both the File Update Interface ( x EE-SE450) and ACI Generic File Update Interface to BASE24-eps ( x EESE452) modules are delivered with the BASE24-eps ISO Host Interface module product code; however, you must license one or the other before you can use File Action (13xx-series) messages in processing. You should license the x EE-SE452 module if the File Action messages are from another ACI Payments Framework application (e.g., ACI Payments Manager). Otherwise, you should license the x EE-SE450 module. Note: Once you have licensed the x EE-SE450 module, you do not need to license the x EE-SE452 module if you begin to receive file update messages from another ACI application. BASE24-eps ISO Host Interface ( x EE-IS300) The BASE24-eps ISO Host Interface ( x EE-IS300) module provides a base online message interface between the BASE24-eps system and a front-end transaction acquiring system or a back-end host application for issuing based on the ISO 8583:1993 message standard. The xEE-IS300 module provides support for all types of messages (i.e., 11xx-, 12xx-, 14xx-, 16xx-, 17xx-, and 18xx-series), except for File Action (13xx-series) messages. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 19 BASE24-eps ISO 8583:1993 host external message File Update Interface ( x EE-SE450) The File Update Interface ( x EE-SE450) module provides a bi-directional interface between BASE24-eps and another application (e.g., a host system of record) for updating files. File update functionality is used for card and account updates as well as for updating interchange bulletins, account management files, and negative files. The File Update Interface ( x EE-SE450) module licenses File Action (13xx-series) messages for use in processing. You would license this module if you need to process updates to data sources residing on the BASE24-eps system or pass on updates to files (e.g., negative card file or warning bulletin) on another system or interchange. In addition to the update functionality, this module also supports inbound inquiries on the BASE24-eps Card data source which allows hosts to query on specific information resident in the BASE24-eps Card data source. ACI Generic File Update Interface to BASE24-eps ( x EE-SE452) The ACI Generic File Update Interface to BASE24-eps ( x EE-SE452) module also licenses File Action (13xxseries) messages to support real time Card and Account database updates other ACI applications, including Proactive Risk Manager (PRM) and Payments Manager Account Management. These applications can forward file update messages (also known as Tieback messages in PRM) to BASE24-eps, which will impact the data maintained in the BASE24-eps Card and Card Account data sources or be passed through BASE24-eps to an interchange, providing card data updates to the switch. This module should be licensed when file update messages are sent between BASE24-eps and Payments Manager or between BASE24-eps and PRM, but only if the customer has not already licensed the File Update Interface ( x EE-SE450) to forward file update messages between BASE24-eps and another host (e.g. deposit application host). Configuring the external message BASE24-eps provides the capability to configure the data elements included in the external message and, if MACing is used, the message data to be used to create the message authentication codes (MACs) for the external message. External message configuration is accomplished by creating an ISO Message profile, which contains the message configuration you want to use. The ISO Message profile is then assigned to the interface component that will use it. This configuration capability gives hosts the flexibility to modify the external message according to the data elements they need and those they do not. What is a profile? Profiles are named sets of parameter values and settings that can be assigned as a group and shared amongst multiple entities. Profiles enable configuration and reuse of common values, saving time in setup and adding consistency. Setting up an ISO message profile ISO Message profiles contain external message specifications to be used by one or more interfaces. ISO Message profiles are created and viewed on the ISO Message Profile Configuration window on the ACI desktop user interface ( Configuration > ISO > Message Profile) . Data entered on this window is stored in the ISO Message and ISO Field data sources (ISO_Message and ISO_Field) and accessed during processing from external memory tables (ISO_Message_OLTP and ISO_Field_OLTP). Profile name Each ISO Message profile must be identified by a profile name which is used to identify the profile throughout the BASE24-eps system. The name is a required value and is entered in the ISO Message Profile field on the ISO Message Profile Configuration window. This name is used to assign the profile to the interfaces that will use it. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 20 BASE24-eps ISO 8583:1993 host external message Adding message types An ISO Message profile defines the message types to be sent and received by an interface. The ISO version (87, 93 or both) to be assumed is selected by clicking an ISO Message Type radio button. Click ISO 93 when configuring the ISO 8583:1993 host external message. Once the ISO version is selected, you can add the messages types to be included in the profile. Clicking the icon to the right of the Message Type field provides a list of different message types supported in the Prefill Bit Maps from Template window. You can select one of the messages types, which adds the message type to the profile along with the default bit map information (i.e., mandatory, conditional, or echo) defined for the message type by BASE24-eps. The message type defaults to used for the ISO 8583:1993 host external message are prefixed with INTFHI93 in the selection window. Configuring data elements for inclusion The data elements predefined by BASE24-eps to be included in inbound and outbound message are populated as each message type is added to the profiles. However, you can change these presets as you deem necessary. Refer to “Data Element Defaults” for the message types and bit map defaults defined by BASE24-eps. CAUTION: Care must always be taken when making profile changes to the data elements included in the external message since an incorrect setting could eliminate a data element needed for processing. Before eliminating data elements from a message, a host should check to determine whether they are required by BASE24-eps for processing. Including data elements in the MAC The Bit Position values on the Message Type Bit Maps tab enable you to select the data elements to be included in creating a MAC for each message type. A check mark in the MAC field corresponding to the data element bit position means the data element will be included in the MAC. A blank means that the data element will not be included in the MAC. By default, no data elements are included. You can include any data element in message authentication as long is it is also configured as mandatory or conditional. The Primary Message Authentication Code (P-64) and Secondary Message Authentication Code (S-128) data elements are not used in message authentication, regardless of the settings on the Message Type Bit Maps tab of the ISO Message Configuration window. These data elements hold the result of message authentication, and therefore cannot be used in the calculation. Including other message data in the MAC You can include the data that precedes the data element in the message if you choose. The following fields in the MAC Indicators area of the Message Types Bit Map tab of the ISO Message Profile Configuration window are used to configure the inclusion of the data in the MAC. Field Description Message Header Not used for the BASE24-eps ISO 8583:1993 host external message. The message contains is MAC no header data other than the message type identifier and the primary bit map. Message Type Identifier is MAC Place a check mark in this field if you want the message type identifier included in the calculation of the message authentication code (MAC). Primary Bit Map is MAC Place a check mark in this field if you want the primary bit map included in the calculation of the message authentication code (MAC). BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 21 BASE24-eps ISO 8583:1993 host external message BCD/MAC tab settings The External Character Set and MAC Character Set fields on the BCD/MAC Information tab of the ISO Message Profile Configuration window are used by the ISO 93 Host Interface component to determine the character set (ASCII or EBCDIC) used in the ISO 8583:1993 host external message. The External Character Set field specifies the character set for the message (except the MAC data elements). The MAC Character Set field specifies the character set of the data elements—including the Message Type Identifier, Primary Bit Map and Message Header —used to generate the MAC for the message. The character set fields enable the ISO 93 Host Interface component to create, parse, and interpret the external message and the MAC data correctly for the host system with which it is communicating. The Binary Coded Decimal (BCD) fields on the BCD/MAC Information tab are not used by the ISO 93 Host Interface component. Assigning the ISO Message profile to the ISO 93 Host Interface Once an ISO Message profile is created, it can be assigned to an interface component. To assign an ISO Message profile to the BASE24-eps ISO 93 Host Interface component, place the name of the profile in the ISO Message Profile field on the Processing Tab of the BASE24-eps ISO8583 (93) Host Interface Configuration window ( Configuration > Interface > Host > ISO 8583 (93) Host Interface) . Note: In order to function, the BASE243-eps ISO 93 Host Interface component requires that an ISO Message profile be assigned. Message authentication code (MAC) support Message authentication ensures transaction messages are received exactly as created by the legitimate originator. Message authentication protects messages against accidental or deliberate alteration. The message authentication code (MAC) is generated by the originator of the message, based upon message elements identified in advance by the originator and recipient, and included with the message. The MAC is verified by the recipient, based on the same criteria as was used in its generation. Message authentication is done prior to normal processing of the message. The BASE24-eps ISO 93 Host Interface component supports message authentication on all message types. You specify which of the 128 data elements are to be included when authenticating each external message in the ISO Message profile for the interface. Besides the data elements, you can also specify in the ISO Message profile whether the message type identifier and primary bit map (that precede the data elements) are included in the MAC calculation. Refer to “Configuring the external message” for information about setting up MACing for external messages. For more information on how BASE24-eps supports message authentication, refer to the BASE24-eps transaction security manual . Value Added Tax (VAT) support The ISO 8583:1993 standard supports a value added tax (VAT), which can be combined with or kept separate from the transaction amount and the surcharge amount in transactions sent through the host. For messages sent outbound to the host, the interface component checks for the presence of the VAT and VAT Data TDEs. If present and the VAT amount type is the surcharge amount, the component performs the following: If the VAT issuer indicator is combined (which is the default value), the calculated VAT amount is included in both DE 4 (transaction amount) and DE 46 (amount fees), including in reversal transactions. In the case of a partial reversal of a cash dispense, DE 30 (original transaction amount) will also contain the VAT original amount. The VAT Data TDE contains the VAT reversal code indicator, which determines whether the VAT needs to be recalculated on partial reversals. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 22 BASE24-eps ISO 8583:1993 host external message If the VAT issuer indicator is separate, the calculated VAT amount is not applied to DE 4 or DE 46. The fee type is set to a value of 74. If the VAT issuer indicator is undefined, the calculated VAT amount is not applied to DE 4 or DE 46. Network management message support The BASE24-eps ISO 93 Host Interface components support the following network management messages: logon and logoff messages, echo-test messages, and change key and new key messages. Network management messages are sent as 1804/1805 messages and require 1814 messages in response. Their function is identified by the value set in data element P-24 (Function Code). Logon messages Logon messages are network management messages used to initiate communications access between the BASE24-eps system and a host station. They can be sent from or to a host as 1804/1805 messages and require 1814 messages in response. Logon messages are distinguished by one of the following values in data element P-24 (Function Code) of the external message. Code Description 801 System condition/sign-on 819 System condition/sign-on acquirer 820 System condition/sign-on issuer Logoff messages Logoff messages are network management messages used to stop communications access between the BASE24-eps system and a host station. They can be sent from or to a host as 1804/1805 messages and require 1814 messages in response. Note: BASE24-eps continues to process responses for transactions currently in progress when the log off message is received even though the station is marked down and logged off. Logoff messages are distinguished by one of the following values in data element P-24 (Function Code) of the external message. Code Description 802 System condition/sign-off 823 System condition/sign-off acquirer 824 System condition/sign-off issuer Echo-test messages Echo-test messages are network management messages used to establish whether a party is available for message processing. They can be sent from or to a host as 1804/1805 messages and require 1814 messages in response. Note: After a connection failure, BASE24-eps does not use the connection until a successful echo-test has been performed. In addition, BASE24-eps always responds to echo-test requests, regardless of the station's logon state. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 23 BASE24-eps ISO 8583:1993 host external message Echo-test messages are distinguished by a value of 831 (system audit control/echo test) in data element P-24 (Function Code) of the external message. Change key messages A change key message requests that a processor generate a new inbound or outbound PIN encryption or message authentication key. The key-generating processor sends a response to the change key message and then, in a separate action, generates the new key and sends it to the requesting processor in a new key message. The requesting processor sends this type of message to a key-generating processor when the requesting processor has determined that the key needs to be changed. The requesting processor can request to change the inbound key, the outbound key, or both the inbound and outbound key. The change key message can use the following function codes: 811, 817, or 818. Change key messages are distingished by one of the following values in data element P-24 (Function Code) of the external message. Code Description 811 System security/key change (inbound and outbound keys) 817 System security/key change (inbound key) 818 System security/key change (outbound key) New key message A new key message carries a new PIN encryption or message authentication key between processors. The keyusing processor verifies and begins using the new key and returns a response to the key-generating processor indicating that the new key has been implemented. A key-generating processor sends this type of message to a key-using processor when the key-generating processor has either determined that the key needs to be changed. A new key message uses the 809 function code for an inbound key and the 810 function code for an outbound key. New key messages are distingished by one of the following values in data element P-24 (Function Code) of the external message. Code Description 809 System security/key request (inbound key) 810 System security/key request (outbound key) Main key processor When the ISO 93 Host Interface component is the main key processor and is configured for two keys, it sends two new key messages to the secondary key processor (one for the key used by the main key processor as its outbound key and one for the key used by the main key processor as its inbound key). Secondary key processor When the ISO 93 Host Interface component is the secondary key processor and is configured for two keys, it sends two change key messages to the main key processor (one for the key used by the secondary key processor as its outbound key and one for the key used by the secondary key processor as its inbound key). The main key processor responds by sending a new key message for each key. Note: If a key management message is being generated by the main processor for key management, the main processor simply sends an 1804/1805 message to the secondary processor with the new key in the Key Management Data element (S-96). The secondary processor then responds to the main processor. If BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 24 BASE24-eps ISO 8583:1993 host external message the secondary processor requests a key change, the main processor replies with an 1814 response message and then generates a separate 1804/1805 network management request message with the new key. The secondary processor replies with an 1814 message. This is required so that the main processor does not start using a key prior to the secondary processor acknowledging and accepting the new key. Open account relationship (OAR) support The following paragraphs describe how a host must support open account relationship (OAR) from the BASE24eps system. When the host receives a transaction that does not contain an application account number (data elements S-102 and S-103) in the appropriate data element and the acquirer supports multiple account selection (in tag 06 of data element P-62), the host must determine whether multiple accounts apply for either the from -side or to -side of the transaction. If the cardholder has multiple accounts for either the from -side or to -side of the transaction, and the specific account(s) have not been selected, the host can return multiple accounts for selection by the cardholder. From -side accounts must be completely handled first. If multiple accounts exist for the from -side and an account is not identified in data element S-102, the host must place the available from accounts in tag 02 of data element S-127. The number of accounts returned in tag 02 of data element S-127 must not exceed the OAR maximum number of accounts per send value supported by the acquirer in tag 23 of data element S-123. If to accounts also need to be returned, the host must also check the OAR acquirer capabilities value also carried in tag 23 of data element S-123. If the to accounts can also be returned, based on the OAR acquirer capabilities value and the OAR maximum accounts per send value (this value specifies the total number of accounts, which can be a combination of from and to accounts), the host places the to accounts in tag 03 of data element S-127. The host must set the action code in data element P-39 to a value of 83 (Approved, OAR). In addition, the host must include a context cookie in tag 14 of P-62 if additional accounts are available for either the from -side or to side of the transaction. If only the from -side of the transaction can or needs to be sent, the host must include the from accounts in tag 02 of data element S-127, the action code set to a value of 83 (Approved, OAR) in P-39, and the context cookie in tag 14 of P-62 if additional from accounts exist. The BASE24-eps system will send another request to the host to retrieve additional accounts that will include the context cookie in tag 14 of P-62 (data element S-102 will not be present or will not contain an account number if additional from accounts are to be returned). If only the to -side of the transaction can or needs to be sent, the host must include the to accounts in tag 03 of data element S-127, the action code set to a value of 83 (Approved, OAR) in P-39, and the context cookie in tag 14 of P-62 if additional to accounts exist. The BASE24-eps system will send another request to the host to retrieve additional accounts that will include the context cookie in tag 14 of P-62 (data element S-102 or S-103, whichever applies to the to account, will not be present or will not contain an account number if additional to accounts are to be returned). Statement print transactions Statement print transactions can be sent to or received from the host. The following paragraphs describe how a host would support open account relationship (OAR) and statement print transactions from the BASE24-eps system. Statement print transactions are supported as 11xx messages. On first sending the transaction, if an account type is defined but a specific account is not selected, the host must determine whether OAR needs to be invoked (based on whether the acquirer supports OAR and whether multiple from accounts exist). If multiple from accounts exist, the host returns the applicable accounts in tag 02 of the Reserved for Private Use (S-127) data element. The host should limit the number and type of accounts sent based on what the acquirer allows (see tag 23 of S-123). BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 25 BASE24-eps ISO 8583:1993 host external message If all of the accounts are sent back, the action code must be set to 83 (Approved, OAR) and no context cookie should be sent back (see tag 14 of P-62). A subsequent message is sent to the host for the statement data, which includes an account number in S-102. If all of the accounts are not sent back, the action code should be set to 83 (Approved, OAR) and the context cookie should be sent back in P-62 (indicating to the host where it left off in processing OAR data rather than statement data). A subsequent message that includes the context cookie can then be sent from the BASE24-eps system to the host to retrieve the additional accounts. If additional accounts are not required, the BASE24-eps system sends a subsequent message to the host for the statement data, which includes an account number in S-102. Additional messages can be sent to the host for additional statement data as required. These messages will include the context cookie received in the previous response from the host as well as the account number in S-102. If OAR is not supported and the transaction is approved, the host returns the applicable statement data in S-127 and includes the context cookie in P-62 if additional data is to be returned (set the action code to approval or denial as required). The host should not send the context cookie if additional statement data is not available. For the first retrieval of statement print data for a statement print transaction, a flag is set in tag 13 of P-62. The maximum statement data per send length specified in tag 13 of P-62 indicates the maximum number of bytes of statement print data that can be carried in a single message. File update transactions The BASE24-eps ISO 93 Host Interface component can accept file update transactions from a host system if the File Update Interface module has been licensed. File update transactions represent real-time data source updates/actions that can be carried out against certain BASE24-eps data sources or by certain interchanges. File update transactions are supported as 1300-series messages. File Update requests are sent from the host as 1304/1305 (File Action Request/Repeat) messages, and the response/query data is returned as 1314 (File Action Request Response) messages. Each 1304 message can contain updated data for one or more records in one or more of the data sources. The only restrictions are that the updates are for the same primary account (data element P-2) and that all of the data source update data fit in the data elements passed in the message. Note: In all cases, in order for file update transactions to be processed by BASE24-eps, appropriate routing must be set up. For information on setting up routing, refer to the BASE24-eps Transaction Processing User Guide . Card data source updates and inquiries BASE24-eps supports updates and inquiries to the following Card-related data sources. Data source Data source content Card (CARD) Card data and information for up to 10 associated accounts. The associated accounts are identified as accounts 1 through 10 Card Acccount (CARD_ACCOUNT) Information for up to 70 additional accounts associated with the card. The accounts are identified as accounts 11 through 80. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 26 BASE24-eps ISO 8583:1993 host external message Data source Data source content Card Account Multibyte (CARD_ACCOUNT_MBYTE) Certain fields in the Card and Card Account data sources have corresponding multibyte versions. These corresponding multibyte versions are contained in the Card Account Multibyte data source. Updates and inquiries are sent in 1304/1305 (File Action Request/Repeat) messages, and the response/query data is returned in 1314 (File Action Request Response) messages. The primary account number (PAN) contained in P-2 or P-34 is used to identify the Card and Card Account records to which an update or inquiry applies. The PAN is the card number displayed in the Card Number field on the Card Management window of the ACI desktop user interface. Subtags identifying the specific Card, Card Account, and Card Account Multibyte data source fields to be updated or queried are included in data element S-72 tag 01 or data element S-127 tag 10 or both. For descriptions of the individual subtags, see S-72: Tag 01, Card Data Source Updates and Inquiries. Note: File updates of the Card, Card Account, and Card Account Multibyte data sources are performed by the Card component, and the exact same Card component processing is used for both partial refreshes and online file updates of these data sources. The same subtags are used to identify Card, Card Account, and Card Account Multibyte data for both partial refreshes and online file updates. Adding, updating, and deleting Card data The Card record is always read for a file update of Card, Card Account, and Card Account Multibyte information even if an action only affects the Card Account or Card Account Multibyte records (i.e., the only subtags present in the file update message are for accounts 11 and above or for multibyte data). For add actions, the Card component creates a Card record if 10 or fewer accounts are included in the file update message. If more than 10 accounts are included, the Card component creates both a Card record and corresponding Card Account record. If multibyte information is present, the Card component creates a Card Account Multibyte record as well. For delete actions, the Card component deletes the Card data source record and the associated Card Account and Card Account Multibyte data source records if they exist. Depending on the number of accounts associated with a card, it may not be possible to include all Card, Card Account, and Card Account Multibyte data in a single file update message. Therefore, multiple file update messages may be needed to add/update all of the necessary information. Adding, updating, and deleting card accounts The Total Number of Accounts field in the Card record sets the index value of the last account associated with the card. This value tells the system how many account instances it will find. For example, if the Total Number of Accounts field is set to 35, the system assumes there are 35 accounts associated with the card, with 10 in the Card record and 25 in the Card Account record—regardless of whether there are actual processing values in all of the 35 instances (i.e., some accounts may be set to spaces intentionally for future use or other business purposes). During a file update, the number of accounts associated with a card can be changed. If the number of accounts increases to 11 or more, the Card component creates a Card Account record. Conversely, if the number of accounts drops to 10 or fewer, the Card component deletes the corresponding Card Account record. Adding and updating card accounts Card accounts can be added or updated by including the corresponding subtag data in the file update message. For example, assume a Card record has 10 accounts associated with it and you want to add five more (as accounts 11–15). BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 27 BASE24-eps ISO 8583:1993 host external message In this case, you would create an update with tag data for the new accounts (subtags B0–BJ) and a value of 15 in the Number of Accounts subtag (09). The Card component would in turn create a Card Account record (because the number of accounts exceeds 10) and add the new account information to it. Later if you wanted to update the status for account 12, you would create an update containing tag data for Account 12 status (B6). Now suppose in the original example, you wanted to add the five new accounts as the first five accounts (accounts 1–5). In this case, you would create an update with subtag data included for all 15 accounts as follows: • • • The information currently on file for accounts 1–10 would be provided as subtag data for accounts 6–15. The new account information would be provided as subtag data for accounts 1–5. The Number of Accounts subtag (09) would be provided with a value of 15. Deleting card accounts Accounts can be deleted from the Card or Card Account record using file update messages in a couple of ways. For example, assume a Card record has 20 accounts associated with it: 10 accounts in the Card record and 10 accounts in the corresponding Card Account record (the latter indexed as accounts 11–20). If you wanted to delete the 15th account associated with the card—the fifth account in the Card Account record (i.e., account index 15)—the following methods could be used. Method 1: Include space-filled subtags for the account fields to be deleted. In this case, a file update would be performed for the Card record including subtags BG, BH, BI, and BJ set to spaces. The file update does not automatically compress the card account entries in the Card and Card Account records, so there would still be 20 accounts associated with the Card record. The 15th would simply be blank. Method 2: Provide compressed account data. In this case, a file update would provide replacement data for accounts 15–20 as follows: • • • • • • • Account 15 subtags (BG, BH, BI, and BJ) would contain the data for what is currently in the Account 16 fields on disk. Account 16 subtags (BK, BL, BM, and BN) would contain the data for what is currently in the Account 17 fields on disk. Account 17 subtags (BO, BP, BQ, and BR) would contain the data for what is currently in the Account 18 fields on disk. Account 18 subtags (BS, BT, BU, and BV) would contain the data for what is currently in the Account 19 fields on disk. Account 19 subtags (BW, BX, BY, and BZ) would contain the data for what is currently in the Account 20 fields on disk. Account 20 subtags (C0, C1, C2, and C3) would contain spaces. The Number of Accounts subtag (09) would contain a value of 19. In this case, there would be 19 accounts associated with the Card record. Adding, updating, and deleting multibyte card data Multibyte card data—carried in the Card Account Multibyte data source—can be added, updated, or deleted without regard for the existence of corresponding nonmultibyte card data in the Card or Card Account data sources. For example, multibyte account descriptions could be added for accounts 5 through 25, even if the accounts 5 through 25 were not explicitly defined for the card (in the Card and Card Account data sources). The only requirement is that a Card record must exist in order to add multibyte data. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 28 BASE24-eps ISO 8583:1993 host external message Card, Card Account, and Card Account Multibyte data source inquiries Card, Card Account, and Card Account Multibyte data source inquiries can request specific data by specifying the subtags of the data to be returned. In this case, the subtags to be inquired on should be included with a zero length and no data. For example, to inquire on Instrument Status, subtag 02 would be included as 02000. Card, Card Account, and Card Account Multibyte data source inquiries can also return a default set of Card data. In this case, the 1304/1305 message request can be sent with no subtags—instead, S-72 tag 01 or S-127 tag 10 should be included with a zero length and no data. The default set of data returned includes the following subtags: 2, 6–18, 22–23, 29–64, A0–A9, and AA–AV. No data is returned from the Card Account or Card Account Multibyte data sources in this case. All inquiry response information is carried in the 1314 message, as subtag data, in S-127 tag 10, and in all cases, data is only returned in a subtag if there is corresponding data in the Card, Card Account, or Card Account Multibyte data source. Inquiry success is indicated by the values in the P-39 (Action Code) and P-44 (Additional Response Data) data elements. The File Update Interface component does not broadcast the results of an inquiry to external entities. Card and Card Account CSM buffers If present in the Card and Card Account data sources, the Card CSM buffer and Card Account CSM buffer can be updated or queried using file update transactions. CSM buffers are variable-length buffers used for custom software modifications (CSMs). For information on the content and structure of the Card and Card Account CSM buffers, refer to subtags 19 and JW, under the S-72, tag 01 data element description. Positive Balance data source updates BASE24-eps supports updates to the Positive Balance data source, but does not support inquiries. The account number in S-72, tag 02, subtag 01 is used to identify the Positive Balance data source record to be updated. This is the account number displayed in the Account Number field on the Positive Balance Management window of the ACI desktop user interface. Subtags identifying the specific Positive Balance data source fields to be updated are included in data element S-72, tag 02. For descriptions of the individual subtags, refer to data element S-72, tag 02. Update response information is carried in the 1314 message. Update success is indicated by the values in the P-39 (Action Code) and P-44 (Additional Response Data) data elements. If present in the Positive Balance data source, the Positive Balance CSM buffer can be updated using file update transactions. CSM buffers are variable-length buffers used for custom software modifications (CSMs). For information on the content and structure of the Positive Balance CSM buffer, refer to subtag 10 under the S-72, tag 02 data element description. Check Status data source updates and inquiries BASE24-eps supports updates and inquiries on records in the Check Status data source. Subtags identifying the specific Check Status data source fields to be updated or inquired on are included in data element S-72, tag 26. For descriptions of the individual subtags, refer to data element S-72, tag 26. The Check Status records are identified using the following key values carried in the indicated data elements in the 1304 or 1305 message. Key values Data element Routing and transaction number S-100 (Receiving Institution ID Code) BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 29 BASE24-eps ISO 8583:1993 host external message Key values Data element Checking account number S-102 (Account Identification 1) Cardholder PAN or default value of all 9s P-2 (Primary Account Number) Member number P-23 (Card Sequence Number) Response information is carried in the 1314 message. Update success is indicated by the values in the P-39 (Action Code) and P-44 (Additional Response Data) data elements. Inquiry response subtags are all carried in data element S-127, tag 14. Stop Payment data source updates BASE24-eps supports updates and inquiries on records in the Stop Payment data source. Subtags identifying the specific Stop Payment data source fields to be updated or inquired on are included in data element S-72, tag 27. For descriptions of the individual subtags, refer to data element S-72, tag 27. The Stop Payment records are identified using the following key values carried in the indicated data elements in the 1304 or 1305 message. Key values Data element Institution S-72, tag 27, subtag 01 (Institution ID) Account number P-2 (Primary Account Number) Account Type S-72, tag 27, subtag 02 (Account Type) High Check Number S-72, tag 27, subtag 03 (High Check Number) Low Check Number S-72, tag 27, subtag 03 (Low Check Number) The High Check Number and Low Check Number are optional values. If you do not include them, multiple records can be found in an inquiry. Refer to data element S-72, tag 27 for information about how these values can be used. Response information is carried in the 1314 message. Update success is indicated by the values in the P-39 (Action Code) and P-44 (Additional Response Data) data elements. Inquiry response subtags are all carried in data element S-127, tag 15. If multiple records are found for an inquiry, context cookie data will be returned in data element S-127, tag 16. Preauthorization Hold data source update (preauthorization hold deletion) BASE24-eps supports the capability to delete preauthorization holds through file update. Preauthorization hold records are identified using the following key values carried in the indicated data elements in the 1304 or 1305 message. Holds can be at the card or account level. Hold type Key values Data element Card or Account Institution ID Derived from P-3 (Primary Account Number) Card or Account Preauth Hold ID S-72, tag 10, subtag 01 (Hold ID) unless the transaction is a Visa increment authorization transaction, in which case, S-72, tag 10, subtag 03 (Transaction ID) is used. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 30 BASE24-eps ISO 8583:1993 host external message Hold type Key values Data element Card Card Number P-3 (Primary Account Number) Member Number P-23 (Card Sequence Number) Account Number S-102 (Account ID 1) Account Type S-72, tag 10, subtag 02 (Account Type) Account Update response information is carried in the 1314 message. Update success is indicated by the values in the P-39 (Action Code). Interchange file updates The BASE24-eps ISO 93 Host Interface component can accept different types of interchange file update transactions from a host which are passed through to the appropriate interchange. The following table lists the types of interchange file update transactions the host can send, along with the corresponding data elements used to carry the interchange-specific file update information for the transactions. Interchange file update Data element America Express Global Network Solutions (AEGN) Negative File Updates Data element S‑72, tag 13 Banknet File Updates Data element S‑72, tag 07 CO-OP File Updates Data element S‑72, tag 21 Elan File Updates Data element S‑72, tag 48 EPOC Negative File Updates Data element S‑72, tag 19 Fifth Third ISO Interface Response Code Data element S‑72, tag 15 MasterCard Debit System (MDS) File Updates Data element S‑72, tag 22 NETS Negative File Updates Data element S‑72, tag 17 NYCE Negative File Updates Data element S‑72, tag 14 Presto (Publix) Negative File Updates Data element S‑72, tag 18 PRICE File Updates Data element S‑72, tag 24 SHAZAM File Updates Data element S‑72, tag 16 Star Systems Negative File Updates Data element S‑72, tag 04 Visa Card Recovery Bulletin Data element S‑72, tag 06 Visa DPS Negative File Updates Data element S‑72, tag 04 Visa Stop Payment Order Data element S‑72, tag 05 Interchange file update processing The following steps describe how interchange file updates that originate through the ISO 93 Host Interface component are processed by BASE24-eps. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 31 BASE24-eps ISO 8583:1993 host external message Step Actor Description 1 Host Sends an interchange file update to the ISO 93 Host Interface component as a 1304 message. 2 ISO 93 Host Interface component 3 Passes the 1304 message to the File Update Router component. File Update Router Passes the 1304 message to the appropriate interchange interface component component. 4 Interchange Interface component Converts the 1304 message to an external message and writes it to the Store-and-Forward (SAF) data source. The external message is based on the format required by the interchange (e.g., ISO8583:1993-based interchanges would receive1304 messages, whereas ISO8583:1987-based interchanges would receive 0302 messages). 5 ISO 93 Host Interface component Once the Interchange Interface component and File Update Router component complete their processing, the ISO 93 Host Interface component creates a 1314 response, journals it, and sends it to the host. 6 SAF Manager Sends the external message to the interchange but does not delete the SAF record. 7 Interchange Sends a response message, which is received by the interchange interface component. The response message is based on the format required by the interchange (e.g., ISO8583:1993-based interchanges would send 1314 messages, whereas ISO8583:1987-based interchanges would send 0312 messages). 8 Interchange Interface component Uses the response message to locate the transaction in the Journal data source and passes the message to the ISO 93 Host Interface component. 9 ISO 93 Host Interface component Creates a 1324 message, journals it, sends it to the host, and writes it to the SAF. 10 Interchange Interface component Once the ISO 93 Host Interface component has completed its processing, the interchange interface component journals the original response from the interchange and notifies the SAF Manager component to delete the original SAF record for the file update request (from step 4). 11 SAF Manager component 12 Host 13 ISO 93 Host Interface component 14 SAF Manager component Deletes the original file update request record. Responds with a 1334 acknowledgement message, which is received by the ISO 93 Host Interface component. Notifies the SAF Manager component to delete the 1324 SAF record (from step 9). Deletes the 1324 SAF record. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 32 BASE24-eps ISO 8583:1993 host external message Managed list data source updates and inquiries Perform file updates and partical refreshes for managed lists by replacing the file and using file partitioning. ACI delivers a set of metadata that includes file partitioning for some files. This can be used to do a full file replacement on any files, including those without file partitioning, using MetaMan changes as necessary and the required file partitioning configuration. Inquiries are supported for managed lists. MDS dispute processing transactions The ISO 93 Host Interface component supports MasterCard Debit Switch (MDS) dispute processing transactions to and from a host. MDS dispute processing transactions are as follows: Transactions Description Chargebacks An issuer-generated reversal advice message that informs an acquirer that a previously completed charge to a cardholder's account is not valid and that the acquirer will be charged back that amount. A chargeback results in a credit to the issuer and a debit to the acquirer. Hosts send MDS chargebacks to BASE24-eps as 1422 messages with data element P-24 set to 450 (First full chargeback) or 453 (First partial chargeback). BASE24-eps does not send MDS chargebacks to the host. Incoming chargebacks from MDS are simply journalled. Adjustments An acquirer-generated reversal advice message that corrects the amount settled in a previously completed transaction. An adjustment may result in either a debit or credit to the issuer. Hosts send MDS adjustments to BASE24-eps as 1220 or 1221 messages with data element P-24 set to 200 (original financial request/advice). BASE24-eps sends all MDS adjustments to the host as 1220 messages. MDS does not support repeat messages, so the host will not receive any 1221 messages. Representments An acquirer-generated reversal advice message that informs an issuer that a previous chargeback from the issuer is not valid and the transaction is being re-presented for settlement. A representment results in a debit to the issuer and a credit to the acquirer. Hosts send MDS representments to BASE24-eps as 1220 or 1221 messages with data element P-24 set to 205 (first representment). BASE24-eps sends all MDS representments to the host as 1220 messages. MDS does not support repeat messages, so the host will not receive any 1221 messages. MDS chargeback handling MDS chargebacks sent from an issuer host are handled by BASE24-eps as described in the following table. MDS chargebacks from an issuer host Step Actor 1 Issuer Host BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 Description Sends a chargeback as a 1422 message to the ISO 93 Host Interface component. 33 BASE24-eps ISO 8583:1993 host external message MDS chargebacks from an issuer host Step Actor Description 2 ISO 93 Host Interface component Passes the 1422 message to the File Update Router component. 3 File Update Router component Passes the 1422 message to the MDS Interface component. 4 MDS Interface component Converts the message to a 0422 message and writes it to the Storeand-Forward data source. 5 ISO 93 Host Interface component Once the MDS Interface component and File Update Router component complete their processing, the ISO 93 Host Interface component creates a 1432 response, journals it, and sends it to the host. 6 SAF Manager component 7 MDS Interchange Responds with a 0432 response message, which is received by the MDS Interface component. 8 MDS Interface component Uses the 0432 message to locate the transaction in the Journal data source and passes the message to the ISO 93 Host Interface component. 9 ISO 93 Host Interface component Creates a 1442 message, journals it, and sends it to the host. 10 MDS Interface component Once the ISO 93 Host Interface component completes its processing, the MDS Interface component notifies the SAF Manager component to delete the SAF record (from step 4) and journals the 0432 response message. 11 SAF Manager component Deletes the 0422 SAF record. Sends the 0422 message to the MDS Interchange but does not delete the SAF record. Chargebacks sent by an MDS issuer are handled by BASE24-eps as described in the following table. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 34 BASE24-eps ISO 8583:1993 host external message MDS chargebacks from an MDS issuer Step Actor Description 1 MDS Interchange An issuer sends a chargeback through the MDS Interchange, which routes it as a 0422 message to the MDS Interface component. 2 MDS Interface component Converts the 0422 message to a 1422 message, journals the message, and returns a 0432 response to the MDS Interchange. No further processing is performed. The 1422 message is not routed to the host. MDS adjustment and representment handling MDS adjustments and representments from an acquirer host are handled by BASE24-eps as described in the following table. MDS adjustments and representments from an acquirer host Step Actor 1 Acquirer Host 2 ISO 93 Host Interface component 3 File Update Router component 4 MDS Interface component Converts the message to a 0420 message (repeats are not supported by MDS) and writes it to the Store-and-Forward data source. 5 ISO 93 Host Interface component Once the MDS Interface component and File Update Router component complete their processing, the ISO 93 Host Interface component creates a 1230 response, journals it, and sends it to the host. 6 SAF Manager component 7 MDS Interchange BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 Description Sends the adjustment or representment as a 1220 or 1221 message to the ISO 93 Host Interface component. Passes the 1220/1221 message to the File Update Router component. Passes the message to the MDS Interface component. Sends the 0420 message to the MDS Interchange but does not delete the SAF record. Responds with a 0430 response message, which is received by the MDS Interface component. 35 BASE24-eps ISO 8583:1993 host external message MDS adjustments and representments from an acquirer host Step Actor Description 8 MDS Interface component Uses the 0430 message to locate the transaction in the Journal data source and passes the message to the ISO 93 Host Interface component. 9 ISO 93 Host Interface component Creates a 1240 message, journals it, and sends it to the host. 10 MDS Interface component Once the ISO 93 Host Interface component completes its processing, the MDS Interface component notifies the SAF Manager component to delete the SAF record (from step 4) and journals the 0430 response. 11 SAF Manager component Deletes the 0420 SAF record. Adjustments and representments from MDS are processed by BASE24-eps as described in the following table. MDS adjustments and representments from an MDS acquirer Step Actor Description 1 MDS Interchange An acquirer sends an adjustment or representment through the MDS Interchange, which routes as a 0420 message to the MDS Interface component. 2 MDS Interface component Converts the 0420 message to a 1220 message and passes it to the ISO 93 Host Interface component. 3 ISO 93 Host Interface component 4 MDS Interface component Once the ISO 93 Host Interface component completes its processing, the MDS Interface component journals the 1220 message and creates a 0430 response and sends it to the MDS Interchange. 5 SAF Manager component Sends the 1220 message to the issuer host. 6 Issuer Host BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 Writes the 1220 message to the Store-and-Forward data source. Responds with a 1230 response message, which is received by the ISO 93 Host Interface component. 36 BASE24-eps ISO 8583:1993 host external message MDS adjustments and representments from an MDS acquirer Step Actor Description 7 ISO 93 Host Interface component 8 SAF Manager component Journals the 1230 response and notifies the SAF Manager component to delete the 1220 SAF record (from step 3). Deletes the 1220 SAF record. MDS dispute data MDS-specific dispute data is carried in the following data elements. Data is mandatory (M) or optional (O) as follows for chargebacks (C/B), adjustments (Adj), and representments (Rep) to and from the host. DE Tag Sub-tag Data C/B Adj From host From host S-72 20 Rep To host From host 01 Advice Reason Code M M M 02 Advice Reason Detail Code O O O 03 Advice Reason Detail Text O O O 04 Original Processin g Code 05 Advice Reason Additional Text To host M O BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 O O 37 BASE24-eps ISO 8583:1993 host external message DE Tag Sub-tag Data C/B Adj From host From host S-123 Rep To host From host To host 37 Intermedia te Network Facility Data O O O O O 38 Network Data M M M M M 39 Processor Private Data O O O O O 40 Acquirer Forwardin g Institution Identificati on M 41 Issuer Capture Data M M Visa SMS dispute transactions The ISO 93 Host Interface component supports the following Visa SMS dispute transactions to and from a host. Dispute transactions are exception-related transactions that do not require authorization and cannot be declined. Transactions Chargebacks Description An issuer-generated advice message that informs an acquirer that a previously completed charge to a cardholder's account is not valid and that the acquirer will be charged back that amount. A chargeback results in a credit to the issuer and a debit to the acquirer. Hosts send Visa SMS chargebacks to BASE24-eps as 1422 messages with data element P-24 set to 450 (First full chargeback) or 453 (First partial chargeback). BASE24-eps sends the transaction to the Visa Interchange and returns a 1432 response message to the host. BASE24-eps does not send incoming Visa SMS chargebacks to the host. Incoming Visa SMS chargebacks are just journalled as 1422 messages. Chargeback Reversals An issuer-generated advice message that informs an acquirer that a previous chargeback transaction was sent in error and is to be reversed. A chargeback reversal results in a debit to the issuer and a credit to the acquirer. Hosts send Visa SMS chargeback reversals to BASE24-eps as 1422 messages with data elements P-24 set to 450 (First full chargeback) and P-25 set to 4506 (Reversal chargeback). BASE24-eps sends the transaction to the Visa Interchange and returns a 1432 response message to the host. BASE24-eps does not send incoming Visa SMS chargeback reversals to the host. Incoming Visa SMS chargeback reversals are just journalled as 1422 messages. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 38 BASE24-eps ISO 8583:1993 host external message Transactions Description Adjustments An acquirer-generated advice message that corrects the amount settled in a previously completed transaction. An adjustment may result in either a debit or credit to the issuer. Hosts send Visa SMS adjustments to BASE24-eps as 1220 or 1221 messages with data element P-24 set to 200 (Original financial request/advice). In this case, the first two characters of data element P-3 (Processing Code) would be set to 02 for a debit adjustment or 22 for a credit adjustment. BASE24-eps sends the transaction to the Visa Interchange and returns a 1230 response message to the host. BASE24-eps sends all incoming Visa SMS adjustments to the host as 1220 messages and expects 1230 messages in response from the host. Visa SMS does not support repeat messages, so the host will not receive any 1221 messages. Representments An acquirer-generated advice message that informs an issuer that a previous chargeback from the issuer is not valid and the transaction is being re-presented for settlement. A representment results in a debit to the issuer and a credit to the acquirer. Hosts send Visa SMS representments to BASE24-eps as 1220 or 1221 messages with data element P-24 set to 205 (First representment). BASE24-eps sends the transaction to the Visa Interchange and returns a 1230 response message to the host. BASE24-eps sends all incoming Visa SMS representments to the host as 1220 messages and expects 1230 messages in response from the host. Visa SMS does not support repeat messages, so the host will not receive any 1221 messages. Fee Collection An issuer- or acquirer-generated advice message used to collect miscellaneous fees. A fee collection transaction results in a debit to the transaction recipient and a credit to the transaction sender. Issuer hosts send Visa SMS fee collection transactions to BASE24-eps as 1422 messages with the first two characters of data element P-3 set to 0B (Debit - Fee Collection). BASE24-eps sends the transaction to the Visa Interchange and returns a 1432 response message to the host. BASE24-eps does not send incoming Visa SMS fee collection transactions from Visa issuers to the host. These transactions are just journalled as 1422 messages. Acquirer hosts send Visa SMS fee collection transactions to BASE24-eps as 1220 or 1221 messages with the first two characters of data element P-3 set to 0B (Debit - Fee Collection). BASE24-eps sends the message to the Visa Interchange and returns a 1230 response message to the host. BASE24-eps sends incoming Visa SMS fee collection transactions from Visa acquirers to the host as 1220 messages with the first two characters of data element P-3 set to 19 (Debit - private use) and expects 1230 messages in response from the host. Visa SMS does not support repeat messages, so the host will not receive any 1221 messages. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 39 BASE24-eps ISO 8583:1993 host external message Transactions Funds Disbursement Description An issuer- or acquirer-generated advice message used to remit miscellaneous fees. A funds disbursement transaction results in a credit to the transaction recipient and a debit to the transaction sender. Issuer hosts send Visa SMS fund disbursement transactions to BASE24-eps as 1422 messages with the first two characters of data element P-3 set to 2A (funds disbursement). BASE24-eps sends the transaction to the Visa Interchange and returns a 1432 response message to the host. BASE24-eps does not send incoming Visa SMS fund disbursement transactions from Visa issuers to the host. These transactions are just journalled as 1422 messages. Acquirer hosts send Visa SMS fund disbursement transactions to BASE24-eps as 1220 or 1221 messages with the first two characters of data element P-3 set to 2A (funds disbursement). BASE24-eps sends the transaction to the Visa Interchange and returns a 1230 response message to the host. BASE24-eps sends incoming Visa SMS fund disbursement transactions from Visa acquirers to the host as 1220 messages with the first two characters of data element P-3 set to 2A (funds disbursement) and expects 1230 messages in response from the host. Visa SMS does not support repeat messages, so the host will not receive any 1221 messages. Request for Copy An issuer-generated administrative message members use to process Visa POS and Visa Electron requests for documentation. An issuer uses a request for copy to request documentation from an acquirer before initiating a chargeback. Issuer hosts send Visa SMS Request for Copy messages to BASE24-eps as 1604 messages with data element P-24 set to 600 (request for original) or 603 (request for copy). BASE24-eps does not send incoming Visa SMS Request for Copy messages to the host. Incoming request for copy messages are journalled as 1604 messages. Text Message An issuer- or acquirer-generated administrative message used to convey information from a sender (identified by the code in data element P-33 - Forwarding Institution Identification Code) to a receiver (identified by the code in data element S-100 Receiving Institution Identification Code). Acquirers and issuers can communicate with each other and can get general information from each other by sending Text Messages. Hosts send Visa SMS Text Messages to BASE24-eps as 1604 messages with data element P-24 set to 989 (text message) and with the text of the message in data element P-62 subtag 74. BASE24-eps does not send incoming Visa SMS Text Messages to the host. Incoming text messages are journalled as 1604 messages. Fraud Reporting An issuer- or acquirer-generated administrative message used to report a fraudulent transaction to the Visa Fraud Reporting System (FRS). Hosts send Visa SMS Fraud Reporting messages to BASE24-eps as 9620 messages with data element P-24 set to 994 (fraud report from acquirer), 995 (fraud report from issuer), 996 (fraud report to acquirer), or 997 (fraud report to issuer). BASE24-eps does not send incoming Visa SMS Fraud Reporting messages to the host. Incoming fraud reporting messages are journalled as 9620 messages. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 40 BASE24-eps ISO 8583:1993 host external message Visa SMS chargebacks, chargeback reversals, fee collections, and funds disbursements from an issuer host Visa SMS chargebacks, chargeback reversals, fee collections, and funds disbursements sent from an issuer host are handled by BASE24-eps as described in the following table. From an issuer host Step Actor Description 1 Issuer Host Sends the transaction as a 1422 message to the ISO 93 Host Interface component. 2 ISO 93 Host Interface component Passes the 1422 message to the File Update Router component. 3 File Update Router component Passes the 1422 message to the Visa Interface component. 4 Visa Interface component Converts the message to a 0422 message and writes it to the Storeand-Forward data source 5 ISO 93 Host Interface component Once the Visa Interface component and File Update Router component complete their processing, the ISO 93 Host Interface component creates a 1432 response, journals it, and sends it to the host. 6 SAF Manager component 7 Visa Interchange Responds with a 0432 response message, which is received by the Visa Interface component. 8 Visa Interface component Uses the 0432 message to locate the transaction in the Journal data source and passes the message to the ISO 93 Host Interface component. 9 ISO 93 Host Interface component Creates a 1442 message, journals it, and sends it to the host. Sends the 0422 message to the Visa Interchange but does not delete the SAF record. Note: This is only done if the flag to send notification messages to the host is set. 10 Visa Interface component BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 Once the ISO 93 Host Interface component completes its processing, the Visa Interface component notifies the SAF Manager component to delete the SAF record (from step 4) and journals the 0432 response message. 41 BASE24-eps ISO 8583:1993 host external message From an issuer host Step Actor 11 SAF Manager component Description Deletes the 0422 SAF record. Visa SMS chargebacks, chargeback reversals, fee collections, and funds disbursements from a Visa issuer Visa SMS chargebacks, chargeback reversals, fee collections, and funds disbursements sent from a Visa issuer are handled by BASE24-eps as described in the following table. From a Visa issuer Step Actor Description 1 Visa Interchange An issuer sends a 0422 message to Visa Interchange which routes the message to the Visa Interface component. 2 Visa Interface component Converts the 0422 message to a 1422 message, journals the message, and returns a 0432 response to the Visa Interchange. No further processing is performed. The 1422 message is not routed to the host. Visa SMS adjustments, representments, fee collections, and funds disbursements from an acquirer host Visa SMS adjustments, representments, fee collections, and funds disbursements from an acquirer host are handled by BASE24-eps as described in the following table. From an acquirer host Step Actor Description 1 Acquirer Host Sends the transaction as a 1220 or 1221 message to the ISO 93 Host Interface component. 2 ISO 93 Host Interface component Passes the 1220/1221 message to the File Update Router component. 3 File Update Router component 4 Visa Interface component Converts the message to a 0220 message (repeats are not supported by Visa) and writes it to the Store-and-Forward data source. 5 ISO 93 Host Interface component Once the Visa Interface component and File Update Router component complete their processing, the ISO 93 Host Interface component creates a 1230 response, journals it, and sends it to the host. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 Passes the message to the Visa Interface component. 42 BASE24-eps ISO 8583:1993 host external message From an acquirer host Step Actor Description 6 SAF Manager component 7 Visa Interchange Responds with a 0230 response message, which is received by the Visa Interface component. 8 Visa Interface component Uses the 0230 message to locate the transaction in the Journal data source and passes the message to the ISO 93 Host Interface component. 9 ISO 93 Host Interface component Creates a 1240 notification message, journals it, and sends it to the host. Sends the 0220 message to the Visa Interchange but does not delete the SAF record. Note: This is only done if the flag to send notification messages to the host is set. 10 Visa Interface component Once the ISO 93 Host Interface component completes its processing, the Visa Interface component notifies the SAF Manager component to delete the SAF record (from step 4) and journals the 0230 response. 11 SAF Manager component Deletes the 0220 SAF record. Visa SMS adjustments, representments, fee collections, and funds disbursements from a Visa acquirer Visa SMS adjustments, representments, fee collections, and funds disbursements from a Visa acquirer are processed by BASE24-eps as described in the following table. From a Visa acquirer Step Actor Description 1 Visa Interchange An acquirer sends a 0220 message to the Visa Interchange which routes the message to the Visa Interface component. 2 Visa Interface component Converts the 0220 message to a 1220 message and passes it to the ISO 93 Host Interface component. 3 ISO 93 Host Interface component BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 Writes the 1220 message to the Store-and-Forward data source. 43 BASE24-eps ISO 8583:1993 host external message From a Visa acquirer Step Actor Description 4 Visa Interface component Once the ISO 93 Host Interface component completes its processing, the Visa Interface component journals the 0220 message, creates a 0230 response and sends the response to the Visa Interchange. 5 SAF Manager component Sends the 1220 message to the issuer host. 6 Issuer Host Responds with a 1230 response message, which is received by the ISO 93 Host Interface component. 7 ISO 93 Host Interface component Journals the 1230 response and notifies the SAF Manager component to delete the 1220 SAF record (from step 3). 8 SAF Manager component Deletes the 1220 SAF record. Visa SMS request for copy and text messages from an issuer host Visa SMS request for copy and text messages sent from an issuer host are handled by BASE24-eps as described in the following table. From an issuer host Step Actor 1 Issuer Host Sends the transaction as a 1604 message to the ISO 93 Host Interface component. 2 ISO 93 Host Interface component Passes the 1604 message to the File Update Router component. 3 File Update Router component Passes the 1604 message to the Visa Interface component. 4 Visa Interface component Converts the message to a 0600 message and writes it to the Storeand-Forward data source 5 ISO 93 Host Interface component Once the Visa Interface component and File Update Router component complete their processing, the ISO 93 Host Interface component creates a 1614 response, journals it, and sends it to the host. 6 SAF Manager component BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 Description Sends the 0600 message to the Visa Interchange but does not delete the SAF record. 44 BASE24-eps ISO 8583:1993 host external message From an issuer host Step Actor Description 7 Visa Interchange Responds with a 0610 response message, which is received by the Visa Interface component. 8 Visa Interface component Uses the 0610 message to locate the transaction in the Journal data source and passes the message to the ISO 93 Host Interface component and notifies the SAF Manager to delete the entry in the SAF. 9 SAF Manager component Deletes the 0600 SAF record. Visa SMS text messages from an acquirer host Visa SMS text messages from an acquirer host are handled by BASE24-eps as described in the following table. From an acquirer host Step Actor 1 Acquirer Host Sends the transaction as a 1604 message to the ISO 93 Host Interface component. 2 ISO 93 Host Interface component Passes the 1604 message to the File Update Router component. 3 File Update Router component Passes the 1604 message to the Visa Interface component. 4 Visa Interface component Converts the message to a 0600 message (repeats are not supported by Visa) and writes it to the Store-and-Forward data source. 5 ISO 93 Host Interface component Once the Visa Interface component and File Update Router component complete their processing, the ISO 93 Host Interface component creates a 1614 response, journals it, and sends it to the host. 6 SAF Manager component 7 Visa Interchange BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 Description Sends the 0600 message to the Visa Interchange but does not delete the SAF record. Responds with a 0610 response message, which is received by the Visa Interface component. 45 BASE24-eps ISO 8583:1993 host external message From an acquirer host Step Actor Description 8 Visa Interface component Uses the 0610 message to locate the transaction in the Journal data source and passes the message to the ISO 93 Host Interface component and notifies the SAF Manager to delete the entry in the SAF. 9 SAF Manager component Deletes the 0600 SAF record. Visa SMS request for copy and text messages from a Visa issuer Visa SMS request for copy and text messages sent from a Visa issuer are handled by BASE24-eps as described in the following table. From a Visa issuer Step Actor Description 1 Visa Interchange An issuer sends a 0600 message to Visa Interchange which routes the message to the Visa Interface component. 2 Visa Interface component Converts the 0600 message to a 1604 message, journals the message, and returns a 0610 response to the Visa Interchange. No further processing is performed. The 1604 message is not routed to the host. Visa SMS text messages from a Visa acquirer Visa SMS text messages sent from a Visa acquirer are handled by BASE24-eps as described in the following table. From a Visa acquirer Step Actor Description 1 Visa Interchange An acquirer sends a 0600 message to Visa Interchange which routes the message to the Visa Interface component. 2 Visa Interface component Converts the 0600 message to a 1604 message, journals the message, and returns a 0610 response to the Visa Interchange. No further processing is performed. The 1604 message is not routed to the host. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 46 BASE24-eps ISO 8583:1993 host external message Visa SMS fraud reporting messages from an issuer host Visa SMS fraud reporting messages sent from an issuer host are handled by BASE24-eps as described in the following table. From an issuer host Step Actor Description 1 Issuer Host Sends the transaction as a 9620 message to the ISO 93 Host Interface component. 2 ISO 93 Host Interface component Passes the 9620 message to the File Update Router component. 3 File Update Router component Passes the 9620 message to the Visa Interface component. 4 Visa Interface component Converts the message to a Visa 9620 message and writes it to the Store-and-Forward data source 5 ISO 93 Host Interface component 6 SAF Manager component 7 Visa Interchange Responds with a 9630 response message, which is received by the Visa Interface component. 8 Visa Interface component Uses the 9630 message to locate the transaction in the Journal data source and passes the message to the ISO 93 Host Interface component and notifies the SAF Manager to delete the entry in the SAF. 9 SAF Manager component Deletes the 9620 SAF record. Once the Visa Interface component and File Update Router component complete their processing, the ISO 93 Host Interface component creates a 9630 response, journals it, and sends it to the host. Sends the 9620 message to the Visa Interchange but does not delete the SAF record. Visa SMS fraud reporting messages from an acquirer host Visa SMS fraud reporting messages from an acquirer host are handled by BASE24-eps as described in the following table. From an acquirer host Step Actor 1 Acquirer Host BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 Description Sends the transaction as a 9620 message to the ISO 93 Host Interface component. 47 BASE24-eps ISO 8583:1993 host external message From an acquirer host Step Actor Description 2 ISO 93 Host Interface component Passes the 9620 message to the File Update Router component. 3 File Update Router component Passes the 9620 message to the Visa Interface component. 4 Visa Interface component Converts the message to a Visa 9620 message (repeats are not supported by Visa) and writes it to the Store-and-Forward data source. 5 ISO 93 Host Interface component Once the Visa Interface component and File Update Router component complete their processing, the ISO 93 Host Interface component creates a 9630 response, journals it, and sends it to the host. 6 SAF Manager component 7 Visa Interchange Responds with a 9630 response message, which is received by the Visa Interface component. 8 Visa Interface component Uses the 9630 message to locate the transaction in the Journal data source and passes the message to the ISO 93 Host Interface component and notifies the SAF Manager to delete the entry in the SAF. 9 SAF Manager component Deletes the 9620 SAF record. Sends the 9620 message to the Visa Interchange but does not delete the SAF record. Visa SMS fraud reporting messages from a Visa issuer Visa SMS fraud reporting messages sent from a Visa issuer are handled by BASE24-eps as described in the following table. From a Visa issuer Step Actor Description 1 Visa Interchange An issuer sends a Visa 9620 message to Visa Interchange which routes the message to the Visa Interface component. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 48 BASE24-eps ISO 8583:1993 host external message From a Visa issuer Step Actor Description 2 Visa Interface component Converts the Visa 9620 message to a BASE24-eps 9620 message, journals the message, and returns a 9630 response to the Visa Interchange. No further processing is performed. The 9620 message is not routed to the host. Visa SMS fraud reporting messages from a Visa acquirer Visa SMS fraud reporting messages sent from a Visa acquirer are handled by BASE24-eps as described in the following table. From a Visa acquirer Step Actor Description 1 Visa Interchange An acquirer sends a Visa 9620 message to Visa Interchange which routes the message to the Visa Interface component. 2 Visa Interface component Converts the Visa 9620 message to a BASE24-eps 9620 message, journals the message, and returns a 9630 response to the Visa Interchange. No further processing is performed. The 9620 message is not routed to the host. Processing messages with no primary account number (PAN) In general, inbound messages received by the BASE24-eps ISO Host Interface require a Primary Account Number (PAN) to be processed; however, in certain Visa SMS exception/dispute messages, a PAN may not present in the message (data element P-2). In these cases, the host interface provides a standard substitute PAN to allow the message to be routed and journalled. Transactions Involved PAN substitution is performed where necessary for incoming fee collection, funds disbursements, and text message transactions. If a PAN is not available, the BASE24-eps ISO Host Interface will check the MTI, Processing Code, and Function Code TDEs for the transaction and create a substitute PAN for any of the combinations in the following table. MTI Transaction Code Function Code 1220 0B (Debit - Fee Collection) <any value> 2A (Funds Disbursement) <any value> 0B (Debit - Fee Collection) <any value> 2A (Funds Disbursement) <any value> 1422 BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 49 BASE24-eps ISO 8583:1993 host external message MTI Transaction Code Function Code 1604 <any value> 600 (Original Receipt retrieval requestion) <any value> 603 (Copy, retrieval request) <any value> 989 (Text Message) Substitute PAN The BASE24-eps ISO Host Interface creates a 16-digit substitute PAN of 1111111111111111 and uses it to populate the Primary Account Number TDE. This PAN is then used to route the message as needed and also gets journalled as part of the message. Routing required In order to use a substitute PAN, an appropriate Destination Routing Profile must be set up to allow for it. Unmatched reversals In general, when processing reversals from one of its acquiring endpoints, BASE24-eps expects to find the original transaction—the one being reversed—in the Journal data source. If the original transaction cannot be found in the Journal data source, BASE24-eps cannot validate it as an actual reversal of a previous transaction. These unmatched reversals are handled as described below. Matching reversals When a reversal is received from a BASE24-eps acquiring endpoint, BASE24-eps uses the information in the reversal message to identify the original transaction in the Journal data source. If the original transaction is found, BASE24-eps processes the transaction as a reversal. If the original transaction is not found, BASE24-eps processes the unmatched reversal based on the acquirer and issuer processing controls described below. The following are typical situations in which matching transactions will not be found for reversals: • • The original transaction occurred prior to the time period allowed for by the current journal (i.e., the journal information containing the original transaction has been removed from the system). A partial reversal is used to adjust an incremental authorization (for example, from a hotel or rental car merchant). Since the original amount is part of the key to the Journal data source, an original record for a different amount will not be found. Acquirer processing controls The PROCESS_UNMATCHED_RVSL environment attribute controls how unmatched reversals are handled for all acquirers connected to BASE24-eps (including channel devices and acquirer hosts). A value of Y allows all unmatched reversals to be processed and sent to the issuer as reversals—although they are only sent if their issuer processing controls are set up to allow for it. A value of N defaults to standard BASE24-eps processing for unmatched reversals. In this case, BASE24-eps converts unmatched point-of-sale (POS) partial reversals to adjustments and processes them as adjustments. Other unmatched reversals are simply journalled as unmatched reversals. POS partial reversals are reversals to incremental authorizations. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 50 BASE24-eps ISO 8583:1993 host external message Issuer processing controls Issuer hosts connected to BASE24-eps using the ISO 93 Host Interface component can choose whether or not to accept unmatched reversals using the Unmatched Reversal Processing, Send to Issuer field on the Message Management tab of the ISO8583(93) Host Interface Configuration window. If this field contains a check mark, the ISO 93 Host Interface component allows unmatched reversals to be sent to the host (assuming the PROCESS_UNMATCHED_RVSL environment attribute is also set to Y to allow acquirers to send unmatched reversals). This setting allows any unmatched reversal to be sent to the host. If this field does not contain a check mark, the ISO 93 Host Interface component does not allow unmatched reversals to be sent to the host. In this case, unmatched POS partial reversals are converted and sent as adjustments to the host—regardless of how the PROCESS_UNMATCHED_RVSL environment attribute is set. Other unmatched reversals intended for the host are simply journalled as unmatched reversals. Converting unmatched reversals to adjustments Reversals are converted to adjustments by modifying the following transaction information: • • • • Message Type Indicator is changed to 1120 or 1220. Processing code is changed to 22, Credit Adjustment, if the original amount was more than the completed transaction amount. Otherwise, the processing code is changed to 02, Debit Adjustment. Transaction amount is set to the difference between the original amount and the completed transaction amount. For adjustments, the transaction amount contains the amount to be replaced. For reversals, the transaction amount contains the completed transaction amount. Unmatched Reversal TDE is set to identify the adjustment as being created from an unmatched reversal. Responses to the acquirer Acquirers receive a normal reversal response in response to an unmatched reversal. An action code of 400 (Reversal accepted) is returned if the transaction is sent to the issuer as a reversal or an adjustment. An action code of 481 (Reversal, original transaction not found) is returned if the transaction is not sent to the issuer. Journalling unmatched reversals Unmatched reversals are journalled as reversals if they are sent to the issuer as reversals. They are journalled as adjustments if they are sent to the issuer as adjustments. Handling request timeouts When the ISO 93 Host Interface component sends a request to a host, it sets an outbound request timer to limit the amount of time it will wait for a response. If the host does not respond before the outbound request timer expires, the ISO 93 Host Interface component automatically activates the Route component to reroute the request based on the routing configuration for your system. At the same time, as an option, it can also automatically create a reversal and send it to notify the host to reverse the request. Note: If you choose not to generate an automatic reversal on timeout, the ISO 93 Host Interface component can still generate a reversal to the host in certain situations if it receives late responses. Configuring the reversal option Reversal processing on a request timeout is configured using the Reversal Option field on the Host tab of the ISO8583 (93) Host Interface Configuration window of the ACI desktop user interface ( Configure > Interface > Host -> ISO8583 (93) Host Interface) . Values are as follows: • 0 = Reversal on late response. The only time the ISO 93 Host Interface component generates a reversal is when it receives a late response from a host (i.e., the corresponding request has already timed out). BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 51 BASE24-eps ISO 8583:1993 host external message • 1 = Reversal on timeout. The ISO 93 Host Interface component automatically generates a reversal for any request that times out (i.e., the host has not responded in time). The option is used for both POS and ATM transactions. The value is stored in the HISO93 Interface data source (HISO93_Interface: rvsl_opt) and its corresponding OLTP table. Setting the request timeout settings The number of seconds used for the outbound request timeout is set in the Outbound field on the Message Management tab of the ISO8583 (93) Host Interface Configuration window of the ACI desktop user interface ( Configure > Interface > Host -> ISO8583 (93) Host Interface) . The option is stored in the Interface Manager data source (Interface_Manager: outbnd_auth_rqst_tim_lmt). Reversing a request at timeout When an outbound request to a host times out, the ISO 93 Host Interface component automatically activates the Route component to reroute the request based on the routing configuration for your system. It also takes these additional steps to optionally generate and send a reversal to the host. 1. 2. Adds the Message Substate TDE to the transaction indicating a timeout (“transaction times out”). Checks the reversal option flag in the HISO93 Interface data source OLTP. • 3. 4. 5. 6. If the flag is set to 0 (reversal on late response), no further action is taken (i.e., no reversal is generated at this time). • If the flag is set to 1 (reversal on timeout), the ISO 93 Host Interface component continues with the next step. Updates the transaction with reversal data. Updates the transaction responder TDE. Writes the reversal to the Store-and-Forward (SAF) for the host. Journals the reversal. Journaling the reversal provides a record of the reversal and also enables the ISO 93 Host Interface component to determine a reversal has been sent in the event a corresponding late response is received. Reversing a late response The Host Interface component performs as follows when it receives a late response from the host. If the transaction is approved and has not already been reversed (as would be the case if requests are reversed at timeout), the Host Interface component will create a reversal for the late response. 1. 2. Determines whether the transaction is approved. If not, no reversal is required and the late response is dropped without journaling. Retrieves the original transaction from the Journal. • 3. 4. 5. If the Journal record is not found, the late response is written to the Journal with a substate of “original not found”. • If the Journal record is found and the message type indicates a reversal or reversal repeat, the late response has already been reversed. In this case, the late response is dropped without journaling. • If the Journal record is found and the message type indicates that it is not a reversal or a reversal repeat, the ISO 93 Host Interface component continues with the next step. Uses the data from the Journal record and late response to format a reversal to send to the host. Writes the reversal to the Store-and-Forward (SAF) for the host. Writes the reversal to the Journal data source. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 52 BASE24-eps ISO 8583:1993 host external message Maximum number of timeouts When the maximum number of consecutive timeouts is exceeded (configured in the Maximum Consecutive Timeouts field on the Message Management tab), BASE24-eps marks the station as down and begins sending echo-test requests. The connection is not marked as up until BASE24-eps receives a response for an echo-test request. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 53 Section 2: Supported message types Supported message types BASE24-eps supports the message types shown in the following table for both inbound and outbound host external messages. The message types in the table are divided according to the ISO standard message classes. Message class Type Description Authorization 1100 Authorization Request 1101 Authorization Request Repeat 1110 Authorization Request Response 1120 Authorization Advice 1121 Authorization Advice Repeat 1130 Authorization Advice Response 1140 Authorization Notification 1200 Financial Transaction Request 1201 Financial Transaction Request Repeat 1210 Financial Transaction Request Response 1220 Financial Transaction Advice 1221 Financial Transaction Advice Repeat 1230 Financial Transaction Advice Response 1240 Financial Notification 1304 File Action Request 1305 File Action Request Repeat 1314 File Action Request Response 1324 File Action Advice 1325 File Action Advice Repeat 1334 File Action Advice Response 1420 Reversal Advice 1421 Reversal Advice Repeat 1422 Chargeback Advice 1430 Reversal Advice Response 1432 Chargeback Advice Response 1440 Reversal Notification 1442 Chargeback Notification Financial Transaction File Action Reversal BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 54 Supported message types Message class Type Description Administrative 1604 Administrative Request 1614 Administrative Request Response 1644 Administrative Notification 1804 Network Management Request 1805 Network Management Request Repeat 1814 Network Management Request Response 9620 Administrative Fraud Report 9630 Administrative Fraud Report Response Network Management Product-Specific Message type documentation conventions Host external message types are documented using several standard fields (an example is shown here), followed by a description of how the message type is used. The standard fields are described below. Category: Interactive Routing: From acquirer to issuer Direction: Both inbound and outbound messages supported Category There are two general categories into which messages fall: interactive and noninteractive. Interactive messages are those message types transmitted and responded to while a transaction is taking place. Noninteractive messages are those message types transmitted after a transaction has taken place and where there is no urgency implied for the response. Routing Routing indicates the direction of the message type within the transaction context. Where there is a delineated acquirer or issuer in a transaction, those terms are used to identify how the message type is sent (i.e., from the acquirer to the issuer or from the issuer to the acquirer). Where there is no delineated acquirer or issuer associated with the message (e.g., for file action or administrative messages), the terms sender and receiver are used to denote a relative direction. Direction Direction identifies whether BASE24-eps supports the message type inbound or outbound or both. Inbound refers to messages received by BASE24-eps from the host, and outbound refers to messages sent by BASE24-eps to the host. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 55 Supported message types Authorization messages 1100 Authorization Request Category: Interactive Routing: From acquirer to issuer Direction: Both inbound and outbound messages supported An Authorization Request (1100) message requests approval authorization or guarantee for the transaction to proceed. It is not intended to permit the application of this transaction to the instrument holder (e.g., cardholder) account for the purpose of issuing a bill or statement, except surcharges. An Authorization Request Response (1110) message is expected in return for the 1100 message, either approving or denying the request. 1101 Authorization Request Repeat Category: Interactive Routing: From acquirer to issuer Direction: Both inbound and outbound messages supported If the acquirer is unsuccessful in sending a 1100 message to the issuer, it resends the message as an Authorization Request Repeat (1101). An Authorization Request Repeat (1101) message is identical to an Authorization Request (1100) message, except that it denotes to the receiver that it is a possible duplicate message. An 1101 message is used when a response was expected to an 1100 message but never received. ATM and POS devices can generate 1101 messages. When the ISO 93 Host Interface component receives an 1101 message, it is passed through as a possible duplicate transaction. An action code of 913 (Duplicate transmission) can also indicate a duplicate transaction, however, a duplicate transaction may not always have an action code of 913. An Authorization Request Response (1110) message is expected in return for the 1101 message, either approving or denying the request. 1110 Authorization Request Response Category: Interactive Routing: From issuer to acquirer Direction: Both inbound and outbound messages supported An Authorization Request Response (1110) message is returned in response to an Authorization Request (1100) or Authorization Request Repeat (1101) message to approve or deny the request. 1120 Authorization Advice Category: Interactive Routing: From acquirer to issuer Direction: Both inbound and outbound messages supported BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 56 Supported message types An Authorization Advice (1120) message advises of a transaction authorized on behalf of the instrument issuer. It is not intended to permit application of the transaction to the instrument holder (e.g., cardholder) account for the purpose of issuing a bill or statement, except surcharges. The ISO 93 Host Interface component sends 1120 messages under the following circumstances: • • • When the transaction is authorized on the BASE24-eps system and an advice is configured to be sent to the host for approved transactions, denied transactions, or both approved or denied transactions. When the BASE24-eps system stands in to authorize a transaction for an unavailable host and an advice is configured to be sent to the host for approved transactions, denied transactions, or both approved or denied transactions. When the acquiring entity (e.g., POS device or acquirer interchange) authorizes a transaction, forwards the advice to the BASE24-eps system, and an advice is configured to be sent to the host for approved transactions, denied transactions, or both approved or denied transactions. The ISO 93 Host Interface component stores the 1120 message in the Store-and-Forward data source (Store_and_Forward). The 1120 message is sent to the host during normal store-and-forward processing. An Authorization Advice Response (1130) message is expected in return for the 1120 message. 1121 Authorization Advice Repeat Category: Noninteractive Routing: From acquirer to issuer Direction: Both inbound and outbound messages supported If the acquirer is unsuccessful in sending an 1120 message to the issuer, it resends the message as an Authorization Advice Repeat (1121). An Authorization Advice Repeat (1121) message is identical to an Authorization Advice (1120) message, except that it denotes to the receiver that it is a possible duplicate message. An action code of 913 (Duplicate transmission) can also indicate a duplicate message, however, a duplicate message may not always have an action code of 913. An 1121 message is used when a response was expected to an 1120 message but never received. The ISO 93 Host Interface component changes the 1120 message to an 1121 message and stores it in the Storeand-Forward data source (Store_and_Forward). The 1121 message is sent to the host during normal store-andforward processing. An Authorization Advice Response (1130) message is expected in return for the 1121 message. 1130 Authorization Advice Response Category: Noninteractive Routing: From issuer to acquirer Direction: Both inbound and outbound messages supported An Authorization Advice Response (1130) acknowledges the receipt of an Authorization Advice (1120) message or an Authorization Advice Repeat (1121) message. If the host returns an error response (that is, if P-39 is set to 909), BASE24-eps does not delete the message from the Store-and-Forward data source, and BASE24-eps continues to send the message to the host for processing based on the defined SAF processing limits. 1140 Authorization Notification Category: Noninteractive BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 57 Supported message types Routing: From acquirer to issuer Direction: Both inbound and outbound messages supported An Authorization Notification (1140) message notifies the receiver of an action taken, requiring no approval or response. Authorization notification messages are used to inform the instrument issuer of an authorization transaction that has completed at the point of service. No response message or text-level acknowledgment messages are expected in response to an 1140 message. When BASE24-eps receives an 1140 message, it simply journals the message. No other processing of the message is performed. Financial transaction messages 1200 Financial Transaction Request Category: Interactive Routing: From acquirer to issuer Direction: Both inbound and outbound messages supported A Financial Transaction Request (1200) message requests approval for a transaction that, if approved, can be immediately applied to the account of the customer for billing or statement purposes. A Financial Transaction Request Response (1210) message is expected in return for the 1200 message, either approving or denying the request. 1201 Financial Transaction Request Repeat Category: Interactive Routing: From acquirer to issuer Direction: Both inbound and outbound messages supported If the acquirer is unsuccessful in sending a 1200 message to the issuer, it resends the message as a Financial Transaction Request Repeat (1201). A Financial Transaction Request Repeat (1201) message is identical to a Financial Transaction Request (1200) message, except that it denotes to the receiver that it is a possible duplicate message. A 1201 message is used when a response was expected to a 1200 message but never received. ATM and POS devices can generate 1201 messages. When the ISO 93 Host Interface component receives a 1201 message, it is passed through as a possible duplicate transaction. An action code of 913 (Duplicate transmission) can also indicate a duplicate transaction, although a duplicate transaction may not always have an action code of 913. A Financial Transaction Request Response (1210) message is expected in return for the 1201 message, either approving or denying the request. 1210 Financial Transaction Request Response Category: Interactive Routing: From issuer to acquirer Direction: Both inbound and outbound messages supported BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 58 Supported message types The Financial Transaction Request Response (1210) message is returned in response to a Financial Transaction Request (1200) or Financial Transaction Request Repeat (1201) message to approve or deny the request. 1220 Financial Transaction Advice Category: Noninteractive Routing: From acquirer to issuer Direction: Both inbound and outbound messages supported A Financial Transaction Advice (1220) message advises of a previously completed financial transaction. The ISO 93 Host Interface component sends 1220 messages under the following circumstances: • • • When the transaction is authorized on the BASE24-eps system and an advice is configured to be sent to the host for approved transactions, denied transactions, or both approved or denied transactions. When the BASE24-eps system stands in to authorize a transaction for an unavailable host and an advice is configured to be sent to the host for approved transactions, denied transactions, or both approved or denied transactions. When the acquiring entity (e.g., POS device or acquirer interchange) authorizes a transaction, forwards the advice to the BASE24-eps system, and an advice is configured to be sent to the host for approved transactions, denied transactions, or both approved or denied transactions. A 1220 message can also be sent by a host to the BASE24-eps system. In this case, it is regarded as a force post transaction. The ISO 93 Host Interface component stores the 1220 message in the Store-and-Forward data source (Store_and_Forward). The 1220 message is sent to the host during normal store-and-forward processing. A Financial Transaction Advice Response (1230) message is expected in response for the 1220 message. 1221 Financial Transaction Advice Repeat Category: Noninteractive Routing: From acquirer to issuer Direction: Both inbound and outbound messages supported If the acquirer is unsuccessful in sending a 1220 message to the issuer, it resends the message as a Financial Transaction Advice Repeat (1221). A Financial Transaction Advice Repeat (1221) message is identical to a Financial Transaction Advice (1220) message, except that it denotes to the receiver that it is a possible duplicate message. An action code of 913 (Duplicate transmission) can also indicate a duplicate message, although a duplicate message may not always have an action code of 913. A 1221 message is used when a response was expected to a 1220 message but never received. The ISO 93 Host Interface component changes the 1220 message to a 1221 message and stores it in the Storeand-Forward data source (Store_and_Forward). The 1221 message is sent to the host during normal store-andforward processing. A 1221 message can also be sent by a host to the BASE24-eps system. In this case, it is regarded as a force post transaction. A Financial Transaction Advice Response (1230) message is expected in response for the 1221 message. 1230 Financial Transaction Advice Response Category: Noninteractive BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 59 Supported message types Routing: From issuer to acquirer Direction: Both inbound and outbound messages supported A Financial Transaction Advice Response (1230) message acknowledges the receipt of a Financial Transaction Advice (1220) or Financial Transaction Advice Repeat (1221) message. 1240 Financial Notification Category: Noninteractive Routing: From acquirer to issuer Direction: Both inbound and outbound messages supported A Financial Notification (1240) message notifies the receiver of an action taken that impacts the instrument holder’s account. No approval or response is required for this message. Financial notification messages are used to inform the instrument issuer of a financial transaction that has completed at the point of service. No response message or text-level acknowledgement messages are expected in response to a 1240 message. When BASE24-eps receives a 1240 message, it simply journals the message. No other processing of the message is performed. File action messages 1304 File Action Request Category: Interactive Routing: From sender to receiver Direction: Both inbound and outbound messages supported A File Action Request (1304) message contains instructions to change a data source or a record or to inquire on the Card data source. A File Action Request Response (1314) message is expected in return to the 1304 message, either approving or denying the request. 1305 File Action Request Repeat Category: Interactive Routing: From sender to receiver Direction: Both inbound and outbound messages supported If the sender is unsuccessful in sending a 1304 message to the issuer, it resends the message as a File Action Request Repeat (1305). A File Action Request Repeat (1305) message is identical to a File Action Request (1304) message, except that it denotes to the receiver that it is a possible duplicate message. An action code of 913 (Duplicate transmission) can also indicate a duplicate message, however, a duplicate message may not always have an action code of 913. A 1305 message is used when a response was expected to a 1304 message but never received. A File Action Request Response (1314) message is expected in return for the 1305 message, either approving or denying the request. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 60 Supported message types 1314 File Action Request Response Category: Interactive Routing: From receiver to sender Direction: Both inbound and outbound messages supported A File Update Request Response (1314) message is returned in response to a File Update Request (1304) or File Update Request Repeat (1305) message to approve or deny the request. Success is determined by the values in the P-39 (Action Code) and P-44 (Additional Response Data) data elements. If the host returns an error response (that is, if P-39 is set to 306), BASE24-eps does not delete the message from the Store-and-Forward data source, and BASE24-eps continues to send the message to the host for processing based on the defined SAF processing limits. 1324 File Action Advice Category: Noninteractive Routing: From receiver to sender Direction: Outbound messages only supported A File Action Advice (1324) message provides confirmation to a host as to whether an update to a file maintained by Visa or MasterCard was successfully completed or rejected. A File Action Advice Response (1334) message is expected in response to the 1324 message. 1325 File Action Advice Repeat Category: Noninteractive Routing: From receiver to sender Direction: Outbound messages only supported If the sender is unsuccessful in sending a 1324 message to the issuer, it resends the message as a File Action Advice Repeat (1325). A File Action Advice Repeat (1325) message is identical to a File Action Advice (1324) message, except that it denotes to the receiver that it is a possible duplicate message. An action code of 913 (Duplicate transmission) can also indicate a duplicate message, although a duplicate message may not always have an action code of 913. A 1325 message is used when a response was expected to a 1324 message but never received. A File Action Advice Response (1334) message is expected in response to the 1325 message. 1334 File Action Advice Response Category: Noninteractive Routing: From sender to receiver Direction: Inbound messages only supported A File Action Advice Response (1334) message acknowledges the receipt of a File Action Advice (1324) or File Action Advice Repeat (1325) message. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 61 Supported message types Reversal messages 1420 Reversal Advice Category: Noninteractive Routing: From acquirer to issuer Direction: Both inbound and outbound messages supported A Reversal Advice (1420) message reverses an earlier authorization or financial transaction. The ISO 93 Host Interface component sends 1420 messages in the following circumstances: • • An Authorization Request (1100) message or Financial Transaction Request (1200) message was approved by a host, but the transaction did not complete as approved. An Authorization Advice (1120) message or Financial Transaction Advice (1220) message was sent to a host to notify it of a completed transaction, but then the transaction did not actually complete as the host was advised. A 1420 message can also be sent from the host to the BASE24-eps system. The ISO 93 Host Interface component stores a 1420 message in the Store-and-Forward data source (Store_and_Forward). The 1420 message is sent to the host during normal store-and-forward processing. A Reversal Advice Response (1430) message is expected in response for the 1420 message. 1421 Reversal Advice Repeat Category: Noninteractive Routing: From acquirer to issuer Direction: Both inbound and outbound messages supported If the acquirer is unsuccessful in sending a 1420 message to the issuer, it resends the message as a Reversal Advice Repeat (1421). A Reversal Advice Repeat (1421) message is identical to a Reversal Advice (1420) message, except that it denotes to the receiver that it is a possible duplicate message. An action code of 913 (Duplicate transmission) can also indicate a duplicate message, although a duplicate message may not always have an action code of 913. A 1421 message is used when a response was expected to a 1420 message but never received. The ISO 93 Host Interface component changes the 1420 message to a 1421 message and stores it in the Storeand-Forward data source (Store_and_Forward). The 1421 message is sent to the host during normal store-andforward processing. A 1421 message can also be sent by a host to the BASE24-eps system. A Reversal Advice Response (1430) message is expected in response for the 1421 message. 1422 Chargeback Advice Category: Noninteractive Routing: From issuer to acquirer Direction: Inbound only A Chargeback Advice (1422) message notifies an acquirer that a previously completed charge to a cardholder account is not valid and that the acquirer will be charged back that amount. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 62 Supported message types A Chargeback Advice Response (1432) message is expected in response for the 1422 message. The ISO 93 Host Interface component does not send 1422 messages to the host, but can accept 1422 messages from the host for processing chargeback, fee collection, and funds disbursement transactions. The ISO 93 Host Interface component returns a 1432 message in response to a 1422 message. 1430 Reversal Advice Response Category: Noninteractive Routing: From issuer to acquirer Direction: Both inbound and outbound messages supported A Reversal Advice Response (1430) message acknowledges a Reversal Advice (1420) message or a Reversal Advice Repeat (1421) message. 1432 Chargeback Advice Response Category: Noninteractive Routing: From acquirer to issuer Direction: Outbound messages only A Chargeback Advice Response (1432) message acknowledges a Chargeback Advice (1422) message. 1440 Reversal Notification Category: Noninteractive Routing: From issuer to acquirer Direction: Both inbound and outbound messages supported A Reversal Notification (1440) message notifies the receiver of an action taken that reverses a previously authorized transaction (financial or nonfinancial). No approval or response is required for this message. Reversal notification messages are used to inform the transaction acquirer of an authorization or financial transaction that has been reversed. No response message or text-level acknowledgement messages are expected in response to a 1440 message. When BASE24-eps receives a 1440 message, it simply journals the message. No other processing of the message is performed. 1442 Chargeback Notification Category: Noninteractive Routing: From acquirer to issuer Direction: Outbound messages supported A Chargeback Notification (1442) message notifies an issuer of the acquirer’s response to the chargeback reversal advice. No approval or response is required for this message. Chargeback notification messages are used to inform the transaction acquirer of an completed charge that has been charged back to the acquirer. No response message or text-level acknowledgement messages are expected in response to a 1442 message. When BASE24-eps receives a 1442 message, it journals the message. No other processing of the message is performed. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 63 Supported message types Administrative messages Administrative messages are messages associated with an administrative transaction, which is used when two institutions have identified the need for an exchange of information. 1604 Administrative Request Category: Interactive Routing: Sender to Receiver Direction: Inbound only An Administrative Request (1604) message requests information to support an interchange network. An Administrative Request Response (1614) message is expected in return for the 1604 message. 1614 Administrative Request Response Category: Interactive Routing: Receiver to Sender Direction: Outbound only An Administrative Request Response (1614) message carries the answer to an administrative request; it is sent in response to a 1604 message. 1644 Administrative Notification Category: Noninteractive Routing: Sender to Receiver Direction: Both inbound and outbound messages supported An Administrative Notification (1644) message notifies the sender of a message that was rejected due to a severe format error (e.g., the receiver was unable to parse the original message). No response message or text-level acknowledgement messages are expected in response to a 1644 message. Network management messages 1804 Network Management Request Category: Interactive Routing: Between any two communicating parties (acquirer, issuer, or intermediate network facility) Direction: Both inbound and outbound messages supported A Network Management Request (1804) message is used to send echo-test, dynamic key management, logon, and logoff messages. The ISO 93 Host Interface component sends 1804 messages only if the Network Management Messages Enabled flag is checked on the Message Management tab of the ISO 93 Host Interface Configuration window. A Network Management Request Response (1814) message is expected in response to the 1804 message. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 64 Supported message types 1805 Network Management Request Repeat Category: Interactive Routing: Between any two communicating parties (acquirer, issuer, or intermediate network facility) Direction: Both inbound and outbound messages supported If the acquirer is unsuccessful in sending an 1804 message to the issuer, it resends the message as a Network Management Request Repeat (1805). A Network Management Request Repeat (1805) message is identical to a Network Management Request (1804) message, except that it denotes to the receiver that it is a possible duplicate message. An action code of 913 (Duplicate transmission) can also indicate a duplicate message, although a duplicate message may not always have an action code of 913. An 1805 message is used when a response was expected to an 1804 message but never received. For key processing only, the ISO 93 Host Interface component changes the 1804 message to an 1805 message and stores it in the Store-and-Forward data source (Store_and_Forward). The 1805 message is sent to the host during normal store-and-forward processing. A Network Management Request Response (1814) message is expected in response for the 1805 message. 1814 Network Management Request Response Category: Interactive Routing: Between any two communicating parties (acquirer, issuer, or intermediate network facility) Direction: Both inbound and outbound messages supported A Network Management Request Response (1814) message is returned in response to a Network Management Request (1804) or Network Management Request Repeat (1805) message. Product-specific messages Product-specific messages are messages associated with actions outside the ISO industry standard for transaction processing. The BASE24-eps ISO 93 Host Interface component supports these product-specific message types. 9620 Administrative Fraud Report Category: Interactive Routing: Sender to Receiver Direction: Inbound only An Administrative Fraud Report (9620) message is used to report a fraudulent transaction to the Visa Fraud Reporting System (FRS). An Administrative Fraud Report Response (9630) message is expected in return for the 9620 message. 9630 Administrative Fraud Report Response Category: Interactive Routing: Receiver to Sender Direction: Outbound only BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 65 Supported message types An Administrative Fraud Report Response (9630) message is used to respond to a 9620 message. 1644 Administrative Notification Category: Noninteractive Routing: Sender to Receiver Direction: Both inbound and outbound messages supported An Administrative Notification (1644) message notifies the sender of a message that was rejected due to a severe format error (e.g., the receiver was unable to parse the original message). No response message or text-level acknowledgement messages are expected in response to a 1644 message. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 66 Section 3: Data element defaults Data element defaults The data elements included in each inbound and outbound BASE24‑eps ISO 8583:1993 host external message are configured individually for each external message type in an ISO Message profile. ACI provides a standard profile at installation called HISO93_MSG_PRFL. It contains predefined defaults for the message types and data elements that it sends to and expects from a host. These defaults are based on the BASE24-eps processing requirements for the various message types. You must change these defaults to match your host's or ISO 8583:1993-based system's processing requirements. For example, if you are using the P-60 (CSM Reserved) data element to carry CSM data in any of your supported message types, you must modify those bit maps in the HISO93_MSG_PRFL or in a profile based on the default HISO93_MSG_PRFL to set P-60 as Conditional or Mandatory as required. Bit map presence indicator codes BASE24‑eps uses the following codes to denote whether a data element should be present in its external message. These codes are used in the Bit Position fields on the Message Type Bit Maps tab of the ISO Message Profile Configuration window ( Configure > ISO > Message Profile) . Code C Description Conditional. The element is mandatory under certain conditions. Inclusion of the element is determined by BASE24-eps, message-by-message, based on specific conditions documented for the data element. A host must be prepared to send and receive conditional elements. On incoming messages, a conditional data element must be present if BASE24-eps requires the conditional element for processing. If it is not present in a message from a host, the transaction is denied when an authorization script determines it needs the information for processing. The data element descriptions indicate when a conditional element is required by BASE24-eps. A conditional element is mapped to transaction data elements (TDEs) if the element is included in the incoming message, there is an equivalent internal message field, and the element does not contain zeros or spaces. On outgoing messages, a conditional element is included in the message only if the element contains data and the data is valid. If the element contains blanks, it is not sent. E Echo. In response messages, this code indicates that the response message sender must include the same value it received in the data element in the associated request message. In other words, the responder must echo back the data element if it is present in the request message. Certain data elements in response messages must echo back the same value provided in the data element in the associated request message. These data elements must be configured as echo in the response message on the ISO Message Profile Configuration window. M Mandatory. The element is required in the message. On incoming messages, a mandatory data element must always be present. If a mandatory element is not present in a message from a host, the message is rejected and returned to the host. On outgoing messages, a mandatory data element is always present. If BASE24-eps does not have the appropriate information for the element, BASE24-eps fills the field with zeros or blanks or sets the length indicator to zero. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 67 Data element defaults Code Description blank Not used. The element is not included in the message. Under certain conditions, a blank can be changed to an M or a C if a host wants to receive the element. However, the ability of BASE24-eps to carry the value internally may dictate whether an element can be included in the message. Refer to the individual data element documentation for information on how the element value is handled internally by BASE24eps. Authorization Request/Repeat (MTI 1100/1101) Authorization Request Response (MTI 1110) The following table describes the BASE24-eps data element defaults for Authorization Request Response (1110) messages. Note: You must license the ISO 93 Host Financial Interface module before you can use 11xx-series messages. Bit Data element name In Out 1 Secondary Bit Map C C 2 Primary Account Number C C 3 Processing Code M M Must echo the first two positions of the processing code in the original message. 4 Amount, Transaction C E Include for all processing codes except inquiries, statement print, mini-statements, PIN change, and PIN verify. An amount can be present for non-financial transactions if surcharged. 5 Amount, Reconciliation C C 6 Amount, Cardholder Billing C C 7 Date and Time, Transmission M M 9 Conversion Rate, Reconciliation C C 10 Conversion Rate, Cardholder Billing C C 11 Systems Trace Audit Number M E 12 Date and Time, Local Transaction M E 13 Date, Effective C C Include if present in the request. 14 Date, Expiration C C Include if present in the request. 15 Date, Settlement C C BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 Notes Include if a data element greater than 64 is present. 68 Data element defaults Bit Data element name In Out 17 Date, Capture C C 18 Merchant Category Code C C 19 Country Code, Acquiring Institution C C 22 Point of Service Data Code C C 23 Card Sequence Number C C Include if present in the request. 24 Function Code C C Include if present in the request. 26 Card Acceptor Business Code C C Include if present in the request. 28 Date, Reconciliation C C Include if transaction affects reconciliation and this data element was not provided in the request or advice message. 29 Reconciliation Indicator C C Include if the transaction affects reconciliation and this data element was not provided in the request or advice message. (future) 30 Amounts, Original C C Include if a partial approval, declined or rejected transaction. 32 Acquirer Institution ID Code M E 33 Forwarding Institution ID Code C C Include when the forwarding institution is not the same as the institution originating the message. 34 Primary Account Number, Extended C C Include if present in the request 35 Track2 Data C C Include if present in the request. 36 Track3 Data C C Include if present in the request. 37 Retrieval Reference Number M M 38 Approval Code C C 39 Action Code M M 41 Card Acceptor Terminal ID C C Include if present in the request. 42 Card Acceptor ID Code C C Include if present in the request or advice message. Echo back. 45 Track1 Data C C Include if present in the request. 46 Amounts, Fees C C Include if fees affect reconciliation. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 Notes 69 Data element defaults Bit Data element name In Out Notes 48 Additional Data – Private C C Include tag 01 (PayPass Mapping Service) for a contactless magnetic stripe transaction if using the MasterCard PayPass Mapping Service. 49 Currency Code, Transaction C C Include if P-4 (Amount, Transaction) or P-30 (Amounts, Original) are included in the message. 51 Currency Code, Cardholder Billing C C Include if P-6 (Amount, Cardholder Billing) is included in the message. 54 Amounts, Additional C C 55 Integrated Circuit Card System Related Data C C 57 Authorization Life Cycle Code C C 58 Authorizing Agent Institution ID Code C C Include when the institution that processed an authorization is not the same institution identified in the primary account number. 59 Transport Data C C Include if present in the request. 62 Primary Reserved Private – 62 C C 67 Extended Payment Code C C Include to specify a repayment period for MasterCard cardholders to make deferred payments for a transaction. 100 Receiving Institution ID Code C C Include when the receiving institution is not the same as the final destination of the message. 102 Account Identification 1 C C 103 Account Identification 2 C C 123 Primary Reserved Private – 123 C C 127 Primary Reserved Private – 127 C C Include for EMV transactions. Authorization Advice/Repeat (MTI 1120/1121) The following table describes the BASE24-eps data element defaults for Authorization Advice (1120) and Authorization Advice Repeat (1121) messages. Note: You must license the ISO 93 Host Financial Interface module before you can use 11xx-series messages. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 70 Data element defaults Bit Data element name In Out 1 Secondary Bit Map C C Include if a data element greater than 64 is present. 2 Primary Account Number C C Include if present, conforms to ISO 7812, and is less than 20 characters in length. 3 Processing Code M M 4 Amount, Transaction C C 5 Amount, Reconciliation C C 6 Amount, Cardholder Billing C C 7 Date and Time, Transmission M M 9 Conversion Rate, Reconciliation C C 10 Conversion Rate, Cardholder Billing C C 11 Systems Trace Audit Number M M 12 Date and Time, Local Transaction M M 13 Date, Effective C C 14 Date, Expiration C C 15 Date, Settlement C C 17 Date, Capture C C 18 Merchant Category Code C C 19 Country Code, Acquiring Institution C C 22 Point of Service Data Code M M 23 Card Sequence Number C C 24 Function Code M M 25 Message Reason Code C C 26 Card Acceptor Business Code M M BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 Notes 71 Data element defaults Bit Data element name In Out 27 Approval Code Length C C 30 Amounts, Original C C 32 Acquirer Institution ID Code M M 33 Forwarding Institution ID Code C C Include when the forwarding institution is not the same as the institution originating the message. 34 Primary Account Number, Extended C C Include when the primary account number is present, begins with “59” as defined in ISO 4909 and therefore has a field separator, or is greater than 19 characters in length. 35 Track 2 Data C C Include if track data is captured at the point of service. 36 Track 3 Data C C Include if track data is captured at the point of service. 37 Retrieval Reference Number M M 38 Approval Code C C 1120 messages: include when present. M M 1121 messages 39 Action Code M M 40 Service Code C C BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 Notes Include in a replacement transaction, previously authorized transaction, representment, partial reversal or partial chargeback. Mandatory in a supplementary authorization, if available. 72 Data element defaults Bit Data element name In Out 41 Card Acceptor Terminal ID M M 42 Card Acceptor ID Code C C 43 Card Acceptor Name/Location M M 45 Track 1 Data C C Include if track data is captured at the point of service. 46 Amounts, Fees C C Include if fees affect reconciliation. 48 Additional Data – Private C C 1120 messages: include tag 01 (PayPass Mapping Service) for a contactless magnetic stripe transaction if using the MasterCard PayPass Mapping Service. blank blank C C 1120 messages: Include if P-4 (Amount, Transaction) or P-30 (Amounts, Original) are included in the message. M M 1121 messages C C Include if P-6 (Amount, Cardholder Billing) is included in the message. 49 Currency Code, Transaction 51 Currency Code, Cardholder Billing 54 Amounts, Additional 56 Original Data Elements C C 57 Authorization Life Cycle C C Notes 1121 messages C BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 73 Data element defaults Bit Data element name In Out 58 Authorizing Agent Institution ID Code C C 59 Transport Data C C 62 Primary Reserved Private – 62 C C 67 Extended Payment Code C C blank blank 100 Receiving Institution ID Code C C 102 Account Identification 1 C C 103 Account Identification 2 C C 123 Primary Reserved Private – 123 C C 124 Primary Reserved Private – 124 C C 127 Primary Reserved Private – 127 C C Notes Include when the institution that processed an authorization is not the same institution identified in the primary account number. 1120 messages: include to specify a repayment period for MasterCard cardholders to make deferred payments for a transaction. 1121 messages Include when the receiving institution is not the same as the final destination of the message. Authorization Advice Response (MTI 1130) The following table describes the BASE24-eps data element defaults for Authorization Advice Response (1130) messages. Note: You must license the ISO 93 Host Financial Interface module before you can use 11xx-series messages. Bit 1 Data element name In Out Secondary Bit Map C C BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 Notes Include if a data element greater than 64 is present. 74 Data element defaults Bit Data element name In Out 2 Primary Account Number C E Include if present in the request. 3 Processing Code M E Must echo the first two positions of the processing code in the original message. 4 Amount, Transaction C E Include for all processing codes except inquiries. 7 Date and Time, Transmission M M 11 Systems Trace Audit Number M E 12 Date and Time, Local Transaction M E 18 Merchant Category Code C C 22 Point of Service Data Code C C 24 Function Code C E Include if present in advice. 28 Date, Reconciliation C C Include if transaction affects reconciliation and this data element was not provided in the request or advice message. 29 Reconciliation Indicator C C Include if the transaction affects reconciliation and this data element was not provided in the request or advice message. (future) 32 Acquirer Institution ID Code M E 33 Forwarding Institution ID Code C C Include when the forwarding institution is not the same as the institution originating the message. 34 Primary Account Number, Extended C E Include if present in the advice message. 35 Track2 Data C E Include if present in the advice. 36 Track3 Data C E Include if present in the advice. 37 Retrieval Reference Number C E Include if present in the advice. 39 Action Code M M 41 Card Acceptor Terminal ID C E Include if present in the advice. 42 Card Acceptor ID Code C E Include if present in the advice. 45 Track 1 Data C E Include if present in the advice. 46 Amounts, Fees C C Include if fees affect reconciliation. 48 Additional Data – Private C C Include tag 01 (PayPass Mapping Service) for a contactless magnetic stripe transaction if using the MasterCard PayPass Mapping Service. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 Notes 75 Data element defaults Bit Data element name In Out Notes 49 Currency Code, Transaction C E Include if P-4 (Amount, Transaction) or P-30 (Amounts, Original) are included in the message. 50 Currency Code, Reconciliation C C Include if P-5 (Amount, Reconciliation) is included in the message. 51 Currency Code, Cardholder Billing C C Include if P-6 (Amount, Cardholder Billing) is included in the message. 59 Transport Data C E Include if present in the advice. 62 Primary Reserved Private – 62 C C 67 Extended Payment Code C C Include to specify a repayment period for MasterCard cardholders to make deferred payments for a transaction. 100 Receiving Institution ID Code C C Include when the receiving institution is not the same as the final destination of the message. 102 Account Identification 1 C C 103 Account Identification 2 C C 123 Primary Reserved Private – 123 C C Authorization Notification (MTI 1140) The following table describes the BASE24-eps data element defaults for Authorization Notification (1140) messages. Note: You must license the ISO 93 Host Financial Interface module before you can use 11xx-series messages. Bit Data element name In Out 1 Secondary Bit Map C C Include if a data element greater than 64 is present. 2 Primary Account Number C C Include if the primary account number is present, conforms to ISO 7812, and is less than 20 characters in length. 3 Processing Code M M 4 Amount, Transaction C C 5 Amount, Reconciliation C C 6 Amount, Cardholder Billing C C 7 Date and Time, Transmission M M 9 Conversion Rate, Reconciliation C C BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 Notes Include for all processing codes except for non-financials where surcharging did not apply. 76 Data element defaults Bit Data element name In Out 10 Conversion Rate, Cardholder Billing C C 11 Systems Trace Audit Number M M 12 Date and Time, Local Transaction M M 13 Date, Effective C C 14 Date, Expiration C C 17 Date, Capture C C 19 Country Code, Acquiring Institution C C 22 Point of Service Data Code M M 23 Card Sequence Number C C 24 Function Code M M 26 Card Acceptor Business Code M M 28 Date, Reconciliation C C Include if transaction affects reconciliation and this data element was not provided in the request or advice message. 29 Reconciliation Indicator C C Include if transaction affects reconciliation. (future) 30 Amounts, Original C C Include in a replacement transaction, previously authorized transaction, representment, partial reversal or partial chargeback. Mandatory in a supplementary authorization, if available. 32 Acquirer Institution ID Code M M 33 Forwarding Institution ID Code C C Include when the forwarding institution is not the same as the institution originating the message. 34 Primary Account Number, Extended C C Include when the primary account number is present, begins with “59” as defined in ISO 4909 and therefore has a field separator, or is greater than 19 characters in length. 35 Track 2 Data C C Include if track data is captured at the point of service. 36 Track 3 Data C C Include if track data is captured at the point of service. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 Notes 77 Data element defaults Bit Data element name In Out 37 Retrieval Reference Number M M 38 Approval Code C C 39 Action Code M M 40 Service Code C C 41 Card Acceptor Terminal ID C C 42 Card Acceptor ID Code C C 43 Card Acceptor Name/Location C C 45 Track 1 Data C C Include if track data is captured at the point of service. 46 Amounts, Fees C C Include if fees affect reconciliation. 49 Currency Code, Transaction C C Include if P-4 (Amount, Transaction) or P-30 (Amounts, Original) are included in the message. 50 Currency Code, Reconciliation C C Include if P-5 (Amount, Reconciliation) is included in the message. 51 Currency Code, Cardholder Billing C C Include if P-6 (Amount, Cardholder Billing) is included in the message. 56 Original Data Elements C C 58 Authorizing Agent Institution ID Code C C 59 Transport Data C C 62 Primary Reserved Private – 62 C C 100 Receiving Institution ID Code C C 102 Account Identification 1 C C 123 Primary Reserved Private – 123 C C 127 Primary Reserved Private – 127 C C BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 Notes Include when the institution that processed an authorization is not the same institution identified in the primary account number. Include when the receiving institution is not the same as the final destination of the message. 78 Data element defaults Financial Request/Repeat (MTI 1200/1201) The following table describes the BASE24-eps data element defaults for Financial Request (1200) and Financial Request Repeat (1201) messages. Note: You must license the ISO 93 Host Financial Interface module before you can use 12xx-series messages. Bit Data element name In Out 1 Secondary Bit Map C C Include if a data element greater than 64 is present. 2 Primary Account Number C C Include if the primary account number is present, conforms to ISO 7812, and is less than 20 characters in length. 3 Processing Code M M 4 Amount, Transaction M M 6 Amount, Cardholder Billing C C 7 Date and Time, Transmission M M 10 Conversion Rate, Cardholder Billing C C 11 Systems Trace Audit Number M M 12 Date and Time, Local Transaction M M 13 Date, Effective C C 14 Date, Expiration C C 15 Date, Settlement C C 17 Date, Capture C C 18 Merchant Category Code C C 19 Country Code, Acquiring Institution C C 22 Point of Service Data Code M M 23 Card Sequence Number C C 24 Function Code M M 26 Card Acceptor Business Code M M 27 Approval Code Length C C BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 Notes Include if the Amount, Cardholder Billing data element or the Amount, Cardholder Billing Fee data element is present. 79 Data element defaults Bit Data element name In Out 30 Amounts, Original C C 32 Acquirer Institution ID Code M M 33 Forwarding Institution ID Code C C Include when the forwarding institution is not the same as the institution originating the message. 34 Primary Account Number, Extended C C Include when the primary account number is present, begins with “59” as defined in ISO 4909 and therefore has a field separator, or is greater than 19 characters in length. 35 Track 2 Data C C Include if track data is captured at the point of service. 36 Track 3 Data C C Include if track data is captured at the point of service. 37 Retrieval Reference Number M M 40 Service Code C C 41 Card Acceptor Terminal ID M M 42 Card Acceptor ID Code C C 43 Card Acceptor Name/Location M M 45 Track 1 Data C C Include if track data is captured at the point of service. 46 Amounts, Fees C C Include if fees affect reconciliation. 48 Additional Data – Private Data Element C C 49 Currency Code, Transaction M M 51 Currency Code, Cardholder Billing C C 52 Personal Identification Number data C C 54 Amounts, Additional C C 55 Integrated Circuit Card System Related Data C C BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 Notes Include in a replacement transaction, previously authorized transaction, representment, partial reversal or partial chargeback. Mandatory in a supplementary authorization, if available. Include if P-6 (Amount, Cardholder Billing) is included in the message. Include for EMV transactions. 80 Data element defaults Bit Data element name In Out 59 Transport Data C C 62 Primary Reserved Private – 62 C C 100 Receiving Institution ID Code C C 102 Account Identification 1 C C 103 Account Identification 2 C C 123 Primary Reserved Private – 123 C C 124 Primary Reserved Private – 124 C C 127 Primary Reserved Private – 127 C C Notes Include when the receiving institution is not the same as the final destination of the message. Financial Request Response (MTI 1210) The following table describes the BASE24-eps data element defaults for Financial Request Response (1210) messages. Note: You must license the ISO 93 Host Financial Interface module before you can use 12xx-series messages. Bit Data element name In Out 1 Secondary Bit Map C C Include if a data element greater than 64 is present. 2 Primary Account Number C M Include if present in the request. 3 Processing Code M M Must echo the first two positions of the processing code in the original message. 4 Amount, Transaction M E 5 Amount, Reconciliation C C 6 Amount, Cardholder Billing C C 7 Date and Time, Transmission M M 9 Conversion Rate, Reconciliation C C BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 Notes Include when the reconciliation and transaction currencies differ and this data element was not provided in the request or advice message. Include when the reconciliation and transaction currencies differ and this data element was not provided in the request or advice message. (future) 81 Data element defaults Bit Data element name In Out 10 Conversion Rate, Cardholder Billing C C 11 Systems Trace Audit Number M E 12 Date and Time, Local Transaction M E 13 Date, Effective C C Include if present in request. 14 Date, Expiration C C Include if present in request. 15 Date, Settlement C C 16 Date, Conversion C C 17 Date, Capture C C 18 Merchant Category Code C C 19 Country Code, Acquiring Institution C C 22 Point of Service Data Code M M 23 Card Sequence Number C C Conditional. Include if present in the request. 28 Date, Reconciliation C C Include if transaction affects reconciliation and this data element was not provided in the request or advice message. 29 Reconciliation Indicator C C Include if the transaction affects reconciliation and this data element was not provided in the request or advice message. (future) 30 Amounts, Original C C Include if a partial approval, declined or rejected transaction. 32 Acquirer Institution ID Code M E 33 Forwarding Institution ID Code C C Include when the forwarding institution is not the same as the institution originating the message. 34 Primary Account Number, Extended C C Include if present in the request. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 Notes Include if the Amount, Cardholder Billing data element or the Amount, Cardholder Billing Fee data element is present. Include when reconciliation and transaction currencies differ and this data element was not provided in the request or advice message. (future) 82 Data element defaults Bit Data element name In Out 35 Track 2 Data C C Include if present in the request. 36 Track 3 Data C C Include if present in the request. 37 Retrieval Reference Number M M 38 Approval Code M C 39 Action Code M M 41 Card Acceptor Terminal ID C C Include if present in the request. 42 Card Acceptor ID Code C C Include if present in the request. 45 Track 2 Data C C Include if present in the request. 46 Amounts, Fees C C Include if fees affect reconciliation. 48 Additional Data – Private Data Element C C 49 Currency Code, Transaction M E 50 Currency Code, Reconciliation C C Include if P-5 (Amount, Reconciliation) is included in the message. 51 Currency Code, Cardholder Billing C C Include if P-6 (Amount, Cardholder Billing) is included in the message. 54 Amounts, Additional C C Include if present in the request 55 Integrated Circuit Card System Related Data C C Include for EMV transactions. 58 Authorizing Agent Institution ID Code C C Include when the institution that processed an authorization is not the same institution identified in the primary account number. 59 Transport Data C C 62 Primary Reserved Private – 62 C C 100 Receiving Institution ID Code C C 102 Account Identification 1 C C 103 Account Identification 2 C C BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 Notes Include when the receiving institution is not the same as the final destination of the message. 83 Data element defaults Bit Data element name In Out 123 Reserved for Private Use – 123 C C 127 Reserved for Private Use - 127 C C Notes Include for the statement print or mini-statement processing codes or OAR. Financial Advice/Repeat (MTI 1220/1221) The following table describes the BASE24-eps data element defaults for Financial Advice (1220) and Financial Advice Repeat (1221) messages. Note: You must license the ISO 93 Host Financial Interface module before you can use 12xx-series messages. Bit Data element name In Out 1 Secondary Bit Map C C Include if a data element greater than 64 is present. 2 Primary Account Number C C Include if the primary account number is present, conforms to ISO 7812, and is less than 20 characters in length. 3 Processing Code M M 4 Amount, Transaction M M 5 Amount, Reconciliation C C 6 Amount, Cardholder Billing C C 7 Date and Time, Transmission M M 9 Conversion Rate, Reconciliation C C 10 Conversion Rate, Cardholder Billing C C 11 Systems Trace Audit Number M M 12 Date and Time, Local Transaction C M 1220 messages M M 1221 messages BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 Notes Include if the Amount, Cardholder Billing data element or the Amount, Cardholder Billing Fee data element is present. 84 Data element defaults Bit Data element name In Out 13 Date, Effective C C 14 Date, Expiration C C 15 Date, Settlement C C 17 Date, Capture C C 18 Merchant Category Code C C 19 Country Code, Acquiring Institution C C 22 Point of Service Data Code C M 23 Card Sequence Number C C 24 Function Code M M 25 Message Reason Code C C 26 Card Acceptor Business Code C M 27 Approval Code Length C C 30 Amounts, Original C C 32 Acquirer Institution ID Code C M 33 Forwarding Institution ID Code C C BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 Notes Include if different from date and time, local transaction. Include in a replacement transaction, previously authorized transaction, representment, partial reversal or partial chargeback. Mandatory in a supplementary authorization, if available. Include when the forwarding institution is not the same as the institution originating the message. 85 Data element defaults Bit Data element name In Out Notes 34 Primary Account Number, Extended C C Include when the primary account number is present, begins with “59” as defined in ISO 4909 and therefore has a field separator, or is greater than 19 characters in length. 35 Track 2 Data C C Include if track data is captured at the point of service. 36 Track 3 Data C C Include if track data is captured at the point of service. 37 Retrieval Reference Number M M 38 Approval Code C C 39 Action Code C M 40 Service Code C C 41 Card Acceptor Terminal ID C M 1220 messages M M 1221 messages 42 Card Acceptor ID Code C C 43 Card Acceptor Name/Location C C 1220 messages M M 1221 messages 45 Track 1 Data C C Include if track data is captured at the point of service. 46 Amounts, Fees C C Include if fees affect reconciliation. 48 Additional Data – Private Data Element C C 49 Currency Code, Transaction M M 51 Currency Code, Cardholder Billing C C 54 Amounts, Additional C C BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 Include if P-6 (Amount, Cardholder Billing) is included in the message. 86 Data element defaults Bit Data element name In Out 56 Original Data Elements C C 58 Authorizing Agent Institution ID Code C C 59 Transport Data C C 62 Primary Reserved Private – 62 C C 72 Data Record C blank 1220 messages: required for MDS adjustments or representments. blank blank 1221 messages 100 Receiving Institution ID Code C C 102 Account Identification 1 C C 103 Account Identification 2 C C 123 Primary Reserved Private – 123 C C 124 Primary Reserved Private – 124 C C 127 Primary Reserved Private – 127 C C Notes Include when the institution that processed a financial transaction is not the same institution identified in the primary account number. Include when the receiving institution is not the same as the final destination of the message. Financial Advice Response (MTI 1230) The following table describes the BASE24-eps data element defaults for Financial Advice Response (1230) messages. Note: You must license the ISO 93 Host Financial Interface module before you can use 12xx-series messages. Bit 1 Data element name In Out Secondary Bit Map C C BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 Notes Include if a data element greater than 64 is present. 87 Data element defaults Bit Data element name In Out 2 Primary Account Number C E 3 Processing Code M E 4 Amount, Transaction M E 5 Amount, Reconciliation C C 6 Amount, Cardholder Billing C C 7 Date and Time, Transmission M M 9 Conversion Rate, Reconciliation C C Include when the reconciliation and transaction currencies differ and this data element was not provided in the request or advice message. (future) 10 Conversion Rate, Cardholder Billing C C Include if the Amount, Cardholder Billing data element or the Amount, Cardholder Billing Fee data element is present. 11 Systems Trace Audit Number M E 12 Date and Time, Local Transaction M E 16 Date, Conversion C C 18 Merchant Category Code C C 19 Country Code, Acquiring Institution C C 28 Date, Reconciliation C C Include if transaction affects reconciliation and this data element was not provided in the request or advice message. 29 Reconciliation Indicator C C Include if the transaction affects reconciliation and this data element was not provided in the request or advice message. (future) 30 Amounts, Original blank C 32 Acquirer Institution ID Code M E BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 Notes Include if present in the request. Include when the reconciliation and transaction currencies differ and this data element was not provided in the request or advice message. Include when reconciliation and transaction currencies differ and this data element was not provided in the request or advice message. (future) 88 Data element defaults Bit Data element name In Out 33 Forwarding Institution ID Code C C Include when the forwarding institution is not the same as the institution originating the message. 34 Primary Account Number, Extended C E Include if present in the advice. 35 Track 2 Data C E Include if present in the advice. 36 Track 3 Data C E Include if present in the advice. 37 Retrieval Reference Number C E 39 Action Code M M 41 Card Acceptor Terminal ID C E Include if present in the advice. 42 Card Acceptor ID Code C E Include if present in the advice. 45 Track 1 Data C E Include if present in the advice. 46 Amounts, Fees C C Include if fees affect reconciliation. 48 Additional Data – Private Data Element C C 49 Currency Code, Transaction M E 50 Currency Code, Reconciliation C C Include if P-5 (Amount, Reconciliation) is included in the message. 51 Currency Code, Cardholder Billing C C Include if P-6 (Amount, Cardholder Billing) is included in the message. 54 Additional Amounts C C 59 Transport Data C E 62 Primary Reserved Private – 62 C C 72 Data Record C blank 100 Receiving Institution ID Code C C 102 Account Identification 1 C C 103 Account Identification 2 C C 123 Primary Reserved Private – 123 C C 127 Primary Reserved Private – 127 C C BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 Notes Include if present in the advice. Include when the receiving institution is not the same as the final destination of the message. 89 Data element defaults Financial Notification (MTI 1240) The following table describes the BASE24-eps data element defaults for Financial Notification (1240) messages. Note: You must license the ISO 93 Host Financial Interface module before you can use 12xx-series messages. Bit Data element name In Out 1 Secondary Bit Map C C Include if a data element greater than 64 is present. 2 Primary Account Number C C Include if the primary account number is present, conforms to ISO 7812, and is less than 20 characters in length. 3 Processing Code M M 4 Amount, Transaction M M 5 Amount, Reconciliation C C 6 Amount, Cardholder Billing C C 7 Date and Time, Transmission M M 9 Conversion Rate, Reconciliation C C Include when the reconciliation and transaction currencies differ and this data element was not provided in the request or advice message. (future) 10 Conversion Rate, Cardholder Billing C C Include if the Amount, Cardholder Billing data element or the Amount, Cardholder Billing Fee data element is present. 11 Systems Trace Audit Number M M 12 Date and Time, Local Transaction M M 13 Date, Effective C C 14 Date, Expiration C C 16 Date, Conversion C C Include when the reconciliation and transaction currencies differ and this data element was not provided in the request or advice message. (future) 17 Date, Capture C C Include if different from date and time, local transaction. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 Notes Include when the reconciliation and transaction currencies differ and this data element was not provided in the request or advice message. 90 Data element defaults Bit Data element name In Out 19 Country Code, Acquiring Institution C C 22 Point of Service Data Code M M 23 Card sequence Number C C 24 Function Code M M 26 Card Acceptor Business Code M M 28 Date, Reconciliation C C Include if transaction affects reconciliation and this data element was not provided in the request or advice message. 29 Reconciliation Indicator C C Include if transaction affects reconciliation and checkpoint reconciliation used. (future) 30 Amounts, Original C C Include in a replacement transaction, previously authorized transaction, representment, partial reversal or partial chargeback. Mandatory in a supplementary authorization, if available. 32 Acquirer Institution ID Code M M 33 Forwarding Institution ID Code C C Include when the forwarding institution is not the same as the institution originating the message. 34 Primary Account Number, Extended C C Include when the primary account number is present, begins with “59” as defined in ISO 4909 and therefore has a field separator, or is greater than 19 characters in length. 35 Track 2 Data C C Include if track data is captured at the point of service. 36 Track 3 Data C C Include if track data is captured at the point of service. 37 Retrieval Reference Number M M 38 Approval Code C C 39 Action Code M M 40 Service Code C C 41 Card Acceptor Terminal ID C C 42 Card Acceptor ID Code C C 43 Card Acceptor Name/Location M M BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 Notes 91 Data element defaults Bit Data element name In Out Notes 45 Track 1 Data C C Include if track data is captured at the point of service. 46 Amounts, Fees C C Include if fees affect reconciliation. 48 Additional Data – Private Data Element C C 49 Currency Code, Transaction M M 50 Currency Code, Reconciliation C C Include if P-5 (Amount, Reconciliation) is included in the message. 51 Currency Code, Cardholder Billing C C Include if P-6 (Amount, Cardholder Billing) is included in the message. 54 Additional Amounts C C 56 Original Data Elements C C 58 Authorizing Agent Institution ID Code C C 59 Transport Data C C 62 Primary Reserved Private – 62 C C 100 Receiving Institution ID Code C C 102 Account Identification 1 C C 103 Account Identification 2 C C 123 Primary Reserved Private – 123 C C 127 Primary Reserved Private – 127 C C Include when the institution that processed a financial transaction is not the same institution identified in the primary account number. Include when the receiving institution is not the same as the final destination of the message. File Action Request/Repeat (MTI 1304/1305) The following table describes the BASE24-eps data element defaults for File Action Request (1304) and File Action Request Repeat (1305) messages. Note: You must license the File Update Interface module before you can use 13xx-series messages. Bit 1 Data element name In Out Secondary Bit Map C C BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 Notes Include if a data element greater than 64 is present. 92 Data element defaults Bit 2 Data element name In Out Primary Account Number M M Notes For stop payment orders, this data element must contain the account number for which the stop payment order is requested if the account number is not specified in S-102 or S-103. For file updates to the Stop Payment data source, this data element will contain the checking account number of the customer’s account at the institution that has a stop payment on the check. For file updates to the Check Status data source, if this record is for a registered check for a specific cardholder, this data element will contain the primary account number of the cardholder. If this record is for a pre-approved or pre-declined check, this data element requires default values of all 9s. 4 Amount, Transaction C C 7 Date and Time, Transmission M M 11 Systems Trace Audit Number M M 12 Date and Time, Local Transaction M M 14 Date, Expiration C C Include for file updates to the American Express Global Network Solutions (AEGN) Network Exception File. 19 Country Code, Acquiring Institution C C For stop payment orders, this field is mandatory if the type of stop payment order is R0 or R1. In this case, the field contains the acquiring institution country code from a prior recurring or installment payment transaction for the cardholder. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 Include when a stop payment order is for a specific amount. 93 Data element defaults Bit Data element name In Out 23 Card Sequence Number C C Notes Include for a Card data source update if present (used for journaling and reading data records). Mandatory for file updates sent from a host to the Elan interchange. Mandatory for file updates to the Check Status data source. If the record is for a registered check for a specific cardholder, this data element must contain the member number of the cardholder. If this record is for a pre-approved or pre-declined check, this data element requires default values of all 9s. 24 Function Code M M Valid values are as follows: 301 = Add record 1 302 = Change record 303 = Delete record 304 = Replace record 305 = Inquire on the record 1 For file updates to the AEGN Network Exception File, this code represents an add or update. 25 Message Reason Code C C 32 Acquirer Institution ID Code M M 33 Forwarding Institution ID code C C Include for file updates to the American Express Global Network Solutions (AEGN) Network Exception File. Include when the forwarding institution is not the same as the institution originating the message. Include for file updates to the American Express Global Network Solutions (AEGN) Network Exception File. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 94 Data element defaults Bit Data element name In Out Notes 34 Primary Account Number, Extended C C Include when the primary account number is present, begins with “59” as defined in ISO 4909 and therefore has a field separator, or is greater than 19 characters in length (used for journaling and reading data records). 42 Card Acceptor Identification Code C C For stop payment orders, this field is required to add or replace a stop payment order for a recurring or installment payment (i.e., the Function Code (P-24) data element is set to a value of 301 or 304) if the Card Acceptor Name/Location (P-43) data element and merchant verification value (in S-72 data element, tag 05, subtag 02) are not present. In this case, this field contains the card acceptor identification code from a prior recurring or installment payment transaction for the cardholder. This field is not allowed if the type of stop order is set to a value of R3 (Revocation of all authorizations). 43 Card Acceptor Name/Location C C For stop payment orders, this field is required to add or replace a stop payment order for a recurring or installment payment (i.e., the Function Code (P-24) data element is set to a value of 301 or 304) if the Card Acceptor Identification Code and merchant verification value (in S-72 data element, tag 05, subtag 02) are not present. This field should not be included when deleting or inquiring on a stop payment order (i.e., the Function Code (P-24) data element is set to a value of 303 or 305). This field is not allowed if the type of stop order is R3 (Revoke all authorizations). BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 95 Data element defaults Bit Data element name In Out 49 Currency Code, Transaction C C 59 Transport Data C C 72 Data Record C C Notes Include if P-4 (Amount, Transaction) or P-30 (Amounts, Original) are included in the message. Include for updates to all data sources other than the Card data source. Include for updates or inquiries to the Card data source if card data is to be carried in S-72. Card data can be carried in S-72 or S-127. Include for updates or inquiries to the Check Status and Stop Payment data sources. Include for all stop payment orders. 93 Transaction Destination Institution ID Code C C 94 Transaction Originator Institution ID Code C C 100 Receiving Institution ID Code C C Include when the receiving institution is not the same as the final destination of the message. Include for file updates to the Check Status data source. This field must contain the routing and transit number of the checkissuing institution or checkissuer identification number. 102 Account Identification 1 C C Include if a Positive Balance file update. (used for journaling) For stop payment orders, this data element must contain the account number for which the stop payment order is requested if the account number is not specified in P-2 or S-103. Include for file updates to the Check Status data source. This field must contain the checking account number. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 96 Data element defaults Bit Data element name In Out Notes 103 Account Identification 2 C C For stop payment orders, this data element must contain the account number for which the stop payment order is requested if the account number is not specified in P-2 or S-102. 127 Reserved for Private Use C C Include for updates or inquiries to the Card data source if card data is to be carried in S-127. Card data can be carried in S-72 or S-127. File Action Request Response (MTI 1314) The following table describes the BASE24-eps data element defaults for File Action Request Response (1314) messages. Note: You must license the File Update Interface module before you can use 13xx-series messages. Bit Data element name In Out Notes 1 Secondary Bit Map C C Include if a data element greater than 64 is present. 2 Primary Account Number C E Include if present in request. 7 Date and Time, Transmission M M 11 Systems Trace Audit Number M E 12 Date and Time, Local Transaction M E 23 Card Sequence Number C E 32 Acquirer Institution ID Code M E 33 Forwarding Institution ID Code C C Include when the forwarding institution is not the same as the institution originating the message. 34 Primary Account Number, Extended C E Include if present in request. 39 Action Code M M Examples: Include if present in request. 000 – Approved 118 – No Card Record 300 – Inquiry Successful 44 Additional Response Data C C 59 Transport Data C E BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 Contains File Update action codes. 97 Data element defaults Bit Data element name In Out 93 Transaction Destination Institution ID Code C E 94 Transaction Originator Institution ID Code C E 100 Receiving Institution ID Code C C Notes Include when the receiving institution is not the same as the final destination of the message. File Action Advice/Repeat (MTI 1324) File Action Advice Response (MTI 1334) The following table describes the BASE24-eps data element defaults for File Action Advice Response (1334) messages. Note: You must license the File Update Interface module before you can use 13xx-series messages. Bit Data element name In Out Notes 1 Secondary Bit Map C blank 2 Primary Account Number M blank 7 Date and Time, Transmission M blank 11 Systems Trace Audit Number M blank 12 Date and Time, Local Transaction M blank 23 Card Sequence Number C blank Include if a Card data source update (used for journaling and reading data records). 24 Function Code M blank Valid values are as follows: Include if a data element greater than 64 is present. 301 = Add record 302 = Change record 303 = Delete record 304 = Replace record 305 = Inquire 32 Acquirer Institution ID Code M BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 blank 98 Data element defaults Bit Data element name In Out Notes 34 Primary Account Number, Extended C blank Include when the primary account number is present, begins with “59” as defined in ISO 4909 and therefore has a field separator, or is greater than 19 characters in length (used for journaling and reading data records). 39 Action Code M blank Examples: 300 – Successful 306 – Not Successful 59 Transport Data C blank 93 Transaction Destination Institution ID Code C blank 94 Transaction Originator Institution ID Code C blank Reversal Advice/Repeat (MTI 1420/1421) The following table describes the BASE24-eps data element defaults for Reversal Advice (1420) and Reversal Advice Repeat (1421) messages. Bit Data element name In Out 1 Secondary Bit Map C C Include if a data element greater than 64 is present. 2 Primary Account Number C C Include if the primary account number is present, conforms to ISO 7812, and is less than 20 characters in length. 3 Processing Code M M Must contain the same data as the original authorization (11xx) or financial (12xx) message. 4 Amount, Transaction M M 6 Amount, Cardholder Billing C C 7 Date and Time, Transmission M M BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 Notes 99 Data element defaults Bit Data element name In Out 10 Conversion Rate, Cardholder Billing C C 11 Systems Trace Audit Number M M 12 Date and Time, Local Transaction M M 13 Date, Effective C C 14 Date, Expiration C C 15 Date, Settlement C C 17 Date, Capture M M 18 Merchant Category Code C C 19 Country Code, Acquiring Institution C C 23 Card Sequence Number C C 24 Function Code M M Notes Include if the Amount, Cardholder Billing data element or the Amount, Cardholder Billing Fee data element is present. Valid values are as follows: 400 = Full reversal 401 = Partial reversal 25 Message Reason Code C C 30 Amounts, Original C C 32 Acquirer Institution ID Code M M BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 Include in a replacement transaction, previously authorized transaction, representment, partial reversal or partial chargeback. Mandatory in a supplementary authorization, if available. 100 Data element defaults Bit Data element name In Out 33 Forwarding Institution ID Code C C Include when the forwarding institution is not the same as the institution originating the message. 34 Primary Account Number, Extended C C Include when the primary account number is present, begins with “59” as defined in ISO 4909 and therefore has a field separator, or is greater than 19 characters in length. 35 Track 2 Data C C 36 Track 3 Data C C 37 Retrieval Reference Number M M 38 Approval Code C C 41 Card Acceptor Terminal ID M M 42 Card Acceptor ID Code C C 43 Card Acceptor Name/Location M M 45 Track 1 Data C C 46 Amounts, Fees C C BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 Notes Include in the advice/notification if the data element was present in the original authorization/ financial request/ advice notification message. Echo back. Include if fees affect reconciliation. 101 Data element defaults Bit Data element name In Out 48 Additional Data – Private C C blank blank Notes 1420 messages: include tag 01 (PayPass Mapping Service) for a contactless magnetic stripe transaction if using the MasterCard PayPass Mapping Service. 1421 messages 49 Currency Code, Transaction M M Must contain the same data as the original authorization (11xx) or financial (12xx) message. 51 Currency Code, Cardholder Billing C C Include if P-6 (Amount, Cardholder Billing) is included in the message. 54 Amounts, Additional C C 56 Original Data Elements M M 57 Authorization Life cycle Code C C 58 Authorizing Agent Institution ID Code C C 59 Transport Data C C 62 Primary Reserved Private – 62 C C BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 Include in the advice/notification if the data element was present in the original authorization/ financial request/ advice notification message. If present, it must contain the same data as the original message. 102 Data element defaults Bit Data element name In Out 67 Extended Payment Code C C blank blank 94 Transaction Originator Institution ID C C 100 Receiving Institution ID Code C C 102 Account Identification 1 C C 103 Account Identification 2 C C 123 Primary Reserved Private – 123 C C 124 Primary Reserved Private – 124 C C 127 Primary Reserved Private – 127 C C Notes 1420 messages: Include to specify a repayment period for MasterCard cardholders to make deferred payments for a transaction. 1421 messages Include when the receiving institution is not the same as the final destination of the message. Chargeback Advice (MTI 1422) The following table describes the BASE24-eps data element defaults for Chargeback Advice (1422) messages. Bit Data element name In Out 1 Secondary Bit Map C C Include if a data element greater than 64 is present. 2 Primary Account Number C C Include if the primary account number is present. 3 Processing Code M M 4 Amount, Transaction M M 5 Amount, Reconciliation C C 6 Amount, Cardholder Billing C C 7 Date and Time, Transmission M M 9 Conversion Rate, Reconciliation C C BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 Notes 103 Data element defaults Bit Data element name In Out 10 Conversion Rate, Cardholder Billing C C 11 Systems Trace Audit Number M M 12 Date and Time, Local Transaction C M 13 Date, Effective C C 14 Date, Expiration C C 15 Date, Settlement C C 17 Date, Capture C C 18 Merchant Category Code C C 19 Country Code, Acquiring Institution C C 22 Point of Service Data Code C 23 Card Sequence Number C C 24 Function Code M M Notes Valid values are as follows: 450 = First full chargeback 453 = First partial chargeback 25 Message Reason Code C 26 Card Acceptor Business Code C 30 Amounts, Original C C 32 Acquirer Institution ID Code C M 33 Forwarding Institution ID Code C C Include when the forwarding institution is not the same as the institution originating the message. 34 Primary Account Number, Extended C C Include when the primary account number is present, begins with “59” as defined in ISO 4909 and therefore has a field separator, or is greater than 19 characters in length. 35 Track 2 Data C C 36 Track 3 Data C C 37 Retrieval Reference Number M M 38 Approval Code C C 39 Action Code C C 41 Card Acceptor Terminal ID C M BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 C Include in a partial chargeback. Include if the data element was present in the original financial transaction. 104 Data element defaults Bit Data element name In Out Notes 42 Card Acceptor ID Code C C 43 Card Acceptor Name/Location C M 45 Track 1 Data C C 46 Amounts, Fees C C Include if fees affect reconciliation. 49 Currency Code, Transaction M M Must contain the same data as the original financial message. 50 Currency Code, Reconciliation C C Include if P-5 (Amount, Reconciliation) is included in the message. 51 Currency Code, Cardholder Billing C C Include if P-6 (Amount, Cardholder Billing) is included in the message. 54 Amounts, Additional C C 56 Original Data Elements C M 58 Authorizing Agent Institution ID Code C C 59 Transport Data C C 62 Primary Reserved Private – 62 C C 72 Data Record C blank 94 Transaction Originator Institution ID C C 100 Receiving Institution ID Code C C 102 Account Identification 1 C C 103 Account Identification 2 C C 123 Primary Reserved Private – 123 C C 127 Primary Reserved Private – 127 C C Include if the data element was present in the original financial transaction. Include when the receiving institution is not the same as the final destination of the message. Chargeback Advice Repeat (MTI 1423) The following table describes the BASE24-eps data element defaults for Chargeback Advice (1423) messages. Bit Data element name In Out 1 Secondary Bit Map C blank 2 Primary Account Number C blank BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 Notes Include if a data element greater than 64 is present. 105 Data element defaults Bit Data element name In Out 3 Processing Code M blank 4 Amount, Transaction M blank 5 Amount, Reconciliation C blank 6 Amount, Cardholder Billing C blank 7 Date and Time, Transmission M blank 9 Conversion Rate, Reconciliation C blank 10 Conversion Rate, Cardholder Billing C blank 11 Systems Trace Audit Number M blank 12 Date and Time, Local Transaction M blank 13 Date, Effective C blank 14 Date, Expiration C blank 15 Date, Settlement C blank 17 Date, Capture C blank 18 Merchant Category Code C blank 19 Country Code, Acquiring Institution C blank 23 Card Sequence Number C blank 24 Function Code M blank Notes Valid values are as follows: 450 = First full chargeback 453 = First partial chargeback 25 Message Reason Code C blank 30 Amounts, Original C blank 32 Acquirer Institution ID Code M blank 33 Forwarding Institution ID Code C blank Include when the forwarding institution is not the same as the institution originating the message. 34 Primary Account Number, Extended C blank Include when the primary account number is present, begins with “59” as defined in ISO 4909 and therefore has a field separator, or is greater than 19 characters in length. 35 Track 2 Data C blank 36 Track 3 Data C blank 37 Retrieval Reference Number M blank BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 Include in a partial chargeback. 106 Data element defaults Bit Data element name In Out 38 Approval Code C blank 39 Action Code C blank 41 Card Acceptor Terminal ID M blank 42 Card Acceptor ID Code C blank 43 Card Acceptor Name/Location M blank 45 Track 1 Data C blank 46 Amounts, Fees C blank Include if fees affect reconciliation. 49 Currency Code, Transaction M blank Must contain the same data as the original financial message. 50 Currency Code, Reconciliation C blank Include if P-5 (Amount, Reconciliation) is included in the message. 51 Currency Code, Cardholder Billing C blank Include if P-6 (Amount, Cardholder Billing) is included in the message. 54 Amounts, Additional C blank 56 Original Data Elements M blank 58 Authorizing Agent Institution ID Code C blank 59 Transport Data C blank 62 Primary Reserved Private – 62 C blank 72 Data Record C blank 94 Transaction Originator Institution ID C blank 100 Receiving Institution ID Code C blank 102 Account Identification 1 C blank 103 Account Identification 2 C blank 123 Primary Reserved Private – 123 C blank 127 Primary Reserved Private – 127 C blank BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 Notes Include if the data element was present in the original financial transaction. Include if the data element was present in the original financial transaction. Include when the receiving institution is not the same as the final destination of the message. 107 Data element defaults Reversal Advice Response (MTI 1430) The following table describes the BASE24-eps data element defaults for Reversal Advice Response (1430) messages. Bit Data element name In Out 1 Secondary Bit Map C C 2 Primary Account Number C E 3 Processing Code M M 4 Amount, Transaction M E 5 Amount, Reconciliation C C 6 Amount, Cardholder Billing C C 7 Date and Time, Transmission M M 9 Conversion Rate, Reconciliation C C Include when the reconciliation and transaction currencies differ and this data element was not provided in the request or advice message. (future) 10 Conversion Rate, Cardholder Billing C C Include if the Amount, Cardholder Billing data element or the Amount, Cardholder Billing Fee data element is present. 11 Systems Trace Audit Number M E 12 Date and Time, Local Transaction M E 13 Date, Effective C C 14 Date, Expiration C C 15 Date, Settlement C C 16 Date, Conversion C C 17 Date, Capture M E 18 Merchant Category Code C C 19 Country Code, Acquiring Institution C C BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 Notes Include if a data element greater than 64 is present. Include when the reconciliation and transaction currencies differ and this data element was not provided in the request or advice message. Include when reconciliation and transaction currencies differ and this data element was not provided in the request or advice message. (future) 108 Data element defaults Bit Data element name In Out 23 Card Sequence Number C C 28 Date, Reconciliation C C Include if transaction affects reconciliation and this data element was not provided in the request or advice message. 29 Reconciliation Indicator C C Include if the transaction affects reconciliation and checkpoint reconciliation is used and this data element was not provided in the request or advice message. (future) 32 Acquirer Institution ID Code M E 33 Forwarding Institution ID Code C C Include when the forwarding institution is not the same as the institution originating the message. 34 Primary Account Number, Extended C E Include in a response message if the data element was present in the original request or advice message. Echo back. 37 Retrieval Reference Number M M 39 Action Code M M 41 Card Acceptor Terminal ID C E 42 Card Acceptor ID Code C E 46 Amounts, Fees C C Include if fees affect reconciliation. 48 Additional Data – Private C C Include tag 01 (PayPass Mapping Service) for a contactless magnetic stripe transaction if using the MasterCard PayPass Mapping Service. 49 Currency Code, Transaction C C Include if P-4 (Amount, Transaction) or P-30 (Amounts, Original) are included in the message. 50 Currency Code, Reconciliation C C Include if P-5 (Amount, Reconciliation) is included in the message. 51 Currency Code, Cardholder Billing C C Include if P-6 (Amount, Cardholder Billing) is included in the message. 59 Transport Data C E BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 Notes 109 Data element defaults Bit Data element name In Out 62 Primary Reserved Private – 62 C C 94 Transaction Originator Institution ID C E 100 Receiving Institution ID Code C C 102 Account Identification 1 C C 103 Account Identification 2 C C 123 Primary Reserved Private – 123 C C 127 Primary Reserved Private – 127 C C Notes Include when the receiving institution is not the same as the final destination of the message. Chargeback Advice Response (MTI 1432) The following table describes the BASE24-eps data element defaults for Chargeback Advice Response (1432) messages. Bit Data element name In Out 1 Secondary Bit Map C C 2 Primary Account Number C E 3 Processing Code M E 4 Amount, Transaction M E 5 Amount, Reconciliation C C 6 Amount, Cardholder Billing C C 7 Date and Time, Transmission M M 9 Conversion Rate, Reconciliation C C 10 Conversion Rate, Cardholder Billing C C 11 Systems Trace Audit Number M E 12 Date and Time, Local Transaction M E 13 Date, Effective C C 15 Date, Settlement C C 16 Date, Conversion C C 18 Merchant Category Code C C 19 Country Code, Acquiring Institution C C 28 Date, Reconciliation C C BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 Notes Include if a data element greater than 64 is present. Include if the Amount, Cardholder Billing data element is present. 110 Data element defaults Bit Data element name In Out 29 Reconciliation Indicator C C 30 Amounts, Original blank C 32 Acquirer Institution ID Code M E 33 Forwarding Institution ID Code C C 34 Primary Account Number, Extended C E 37 Retrieval Reference Number C E 39 Action Code M M 41 Card Acceptor Terminal ID C C 42 Card Acceptor ID Code C C 46 Amounts, Fees C C 49 Currency Code, Transaction M E 50 Currency Code, Reconciliation C C Include if P-5 (Amount, Reconciliation) is included in the message. 51 Currency Code, Cardholder Billing C C Include if P-6 (Amount, Cardholder Billing) is included in the message. 59 Transport Data C C 62 Primary Reserved Private – 62 C C 94 Transaction Originator Institution ID C C 100 Receiving Institution ID Code C C 102 Account Identification 1 C C 103 Account Identification 2 C C 123 Primary Reserved Private – 123 C C 127 Primary Reserved Private –127 C C BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 Notes Include in a response to a partial chargeback. Include when the forwarding institution is not the same as the institution originating the message. Include if fees affect reconciliation. Include when the receiving institution is not the same as the final destination of the message. 111 Data element defaults Reversal Notification (MTI 1440) The following table describes the BASE24-eps data element defaults for Reversal Notification (1440) messages. Bit Data element name In Out Notes 1 Secondary Bit Map C C Include if a data element greater than 64 is present. 2 Primary Account Number C C Include if the primary account number is present, conforms to ISO 7812, and is less than 20 characters in length. 3 Processing Code M M Must contain the same data as the original authorization (11xx) or financial (12xx) message. 4 Amount, Transaction M M 5 Amount, Reconciliation C C 6 Amount, Cardholder Billing C C 7 Date and Time, Transmission M M 9 Conversion Rate, Reconciliation C C Include when the reconciliation and transaction currencies differ and this data element was not provided in the request or advice message. (future) 10 Conversion Rate, Cardholder Billing C C Include if the Amount, Cardholder Billing data element or the Amount, Cardholder Billing Fee data element is present. 11 Systems Trace Audit Number M M 12 Date and Time, Local Transaction M M 16 Date, Conversion C C 19 Country Code, Acquiring Institution C C 24 Function Code M M Include when the reconciliation and transaction currencies differ and this data element was not provided in the request or advice message. Include when reconciliation and transaction currencies differ and this data element was not provided in the request or advice message. (future) Valid values are as follows: 400 = Full reversal 401 = Partial reversal BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 112 Data element defaults Bit Data element name In Out 28 Date, Reconciliation C C Include if transaction affects reconciliation and this data element was not provided in the request or advice message. 29 Reconciliation Indicator C C Include if transaction affects reconciliation and checkpoint reconciliation used. (future) 30 Amounts, Original C C Include in a replacement transaction, previously authorized transaction, representment, partial reversal or partial chargeback. Mandatory in a supplementary authorization, if available. 32 Acquirer Institution ID Code M M 33 Forwarding Institution ID Code C C Include when the forwarding institution is not the same as the institution originating the message. 34 Primary Account Number, Extended C C Include when the primary account number is present, begins with “59” as defined in ISO 4909 and therefore has a field separator, or is greater than 19 characters in length. 37 Retrieval Reference Number C C 38 Approval Code C C 39 Action Code M M 46 Amounts, Fees C C Include if fees affect reconciliation. 49 Currency Code, Transaction M M Must contain the same data as the original authorization (11xx) or financial (12xx) message. 50 Currency Code, Reconciliation C C Include if P-5 (Amount, Reconciliation) is included in the message. 51 Currency Code, Cardholder Billing C C Include if P-6 (Amount, Cardholder Billing) is included in the message. 56 Original Data Elements M M BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 Notes Include in the advice/notification if the data element was present in the original authorization/ financial request/advice notification message. Echo back. 113 Data element defaults Bit Data element name In Out Notes 58 Authorizing Agent Institution ID Code C C 59 Transport Data C C 62 Primary Reserved Private – 62 C C 94 Transaction Originator Institution ID C C Include when the transaction originator institution is not the same as the acquiring institution. 100 Receiving Institution ID Code C C Include when the receiving institution is not the same as the final destination of the message. 102 Account Identification 1 C C 103 Account Identification 2 C C 123 Primary Reserved Private – 123 C C 127 Primary Reserved Private – 127 C C Include in the advice/notification if the data element was present in the original authorization/ financial request/advice notification message. If present, it must contain the same data as the original message. Chargeback Notification (MTI 1442) The following table describes the BASE24-eps data element defaults for Chargeback Notification (1442) messages. Bit Data element name In Out Notes 1 Secondary Bit Map blank C Include if a data element greater than 64 is present. 2 Primary Account Number blank C Include if the primary account number is present, conforms to ISO 7812, and is less than 20 characters in length. 3 Processing Code blank M Must contain the same data as the original financial (12xx) message. 4 Amount, Transaction blank M 5 Amount, Reconciliation blank C 6 Amount, Cardholder Billing blank C BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 Include when the reconciliation and transaction currencies differ and this data element was not provided in the request or advice message. 114 Data element defaults Bit Data element name In Out Notes 7 Date and Time, Transmission blank M 9 Conversion Rate, Reconciliation blank C Include when the reconciliation and transaction currencies differ and this data element was not provided in the request or advice message. (future) 10 Conversion Rate, Cardholder Billing blank C Include if the Amount, Cardholder Billing data element or the Amount, Cardholder Billing Fee data element is present. 11 Systems Trace Audit Number blank M 12 Date and Time, Local Transaction blank M 16 Date, Conversion blank C 19 Country Code, Acquiring Institution blank C 24 Function Code blank M Include when reconciliation and transaction currencies differ and this data element was not provided in the request or advice message. (future) Valid values are as follows: 450 = First full chargeback 453 = First partial chargeback 28 Date, Reconciliation blank C Include if transaction affects reconciliation and this data element was not provided in the request or advice message. 29 Reconciliation Indicator blank C Include if transaction affects reconciliation and checkpoint reconciliation used. (future) 30 Amounts, Original blank C Include in a replacement transaction, previously authorized transaction, representment, partial reversal or partial chargeback. Mandatory in a supplementary authorization, if available. 32 Acquirer Institution ID Code blank M 33 Forwarding Institution ID Code blank C BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 Include when the forwarding institution is not the same as the institution originating the message. 115 Data element defaults Bit Data element name In Out 34 Primary Account Number, Extended blank C 37 Retrieval Reference Number blank C 38 Approval Code blank C 39 Action Code blank M 46 Amounts, Fees blank C Include if fees affect reconciliation. 49 Currency Code, Transaction blank M Must contain the same data as the original financial (12xx) message. 50 Currency Code, Reconciliation blank C Include if P-5 (Amount, Reconciliation) is included in the message. 51 Currency Code, Cardholder Billing blank C Include if P-6 (Amount, Cardholder Billing) is included in the message. 56 Original Data Elements blank M 58 Authorizing Agent Institution ID Code blank C 59 Transport Data blank C 62 Primary Reserved Private – 62 blank C 94 Transaction Originator Institution ID blank C Include when the transaction originator institution is not the same as the acquiring institution. 100 Receiving Institution ID Code blank C Include when the receiving institution is not the same as the final destination of the message. 102 Account Identification 1 blank C 103 Account Identification 2 blank C BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 Notes Include when the primary account number is present, begins with “59” as defined in ISO 4909 and therefore has a field separator, or is greater than 19 characters in length. Include in the advice/notification if the data element was present in the original authorization/ financial request/advice notification message. If present, it must contain the same data as the original message. Include in the advice/notification if the data element was present in the original authorization/ financial request/advice notification message. If present, it must contain the same data as the original message. 116 Data element defaults Bit Data element name In Out 123 Primary Reserved Private – 123 blank C 127 Primary Reserved Private – 127 blank C Notes Administrative Request (MTI 1604) The following table describes the BASE24-eps data element defaults for Administrative Request (1604) messages. This message type is used to request information as part of an an administrative transaction. Administrative transactions are used when two institutions have identified a need for an exchange of information (e.g., retrieval requests). Bit Data element name In 1 Secondary Bit Map C Include if a data element greater than 64 is present. 2 Primary Account Number C Include if the primary account number is present, conforms to ISO 7812, and is less than 20 characters in length. 3 Processing Code C 4 Amount, Transaction C 7 Date and Time, Transmission M 11 Systems Trace Audit Number M 12 Date and Time, Local Transaction C 19 Country Code, Acquiring Institution C 24 Function Code M 26 Card Acceptor Business Code C 32 Acquirer Institution ID Code C 33 Forwarding Institution ID Code C 37 Retrieval Reference Number M 43 Card Acceptor Name/Location C 49 Currency Code, Transaction C 59 Transport Data C 62 Primary Reserved Private — 62 M 68 Country Code, Receiving Institution C BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 Out Notes The only valid value is 650 (Unable to parse message). Include when the forwarding institution is not the same as the institution originating the message. 117 Data element defaults Bit Data element name In 72 Data Record M 100 Receiving Institution ID Code C 123 Primary Reserved Private—123 C Out Notes Include when the receiving institution is not the same as the final destination of the message. Administrative Request Response (MTI 1614) The following table describes the BASE24-eps data element defaults for Administrative Request Response (1614) messages. Bit Data element name In Out 1 Secondary Bit Map C 2 Primary Account Number E 3 Processing Code E 4 Amount, Transaction E 7 Date and Time, Transmission M 11 Systems Trace Audit Number E 19 Country Code, Acquiring Institution E 24 Function Code E 32 Acquirer Institution ID Code E 37 Retrieval Reference Number M 39 Action Code M 49 Currency Code, Transaction E 59 Transport Data C 62 Primary Reserved Private — 62 C 68 Country Code, Receiving Institution C 100 Receiving Institution ID Code C 123 Primary Reserved Private—123 C Notes Include if a data element greater than 64 is present. Include when the receiving institution is not the same as the final destination of the message. Administrative Notification (MTI 1644) The following table describes the BASE24-eps data element defaults for Administrative Notification (1644) messages. This message type is used for rejected messages. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 118 Data element defaults Bit Data element name In Out Notes 1 Secondary Bit Map C C 7 Date and Time, Transmission M M 11 Systems Trace Audit Number M M 12 Date and Time, Local Transaction M M 24 Function Code M M The only valid value is 650 (Unable to parse message). 33 Forwarding Institution ID Code C C Include when the forwarding institution is not the same as the institution originating the message. 39 Action Code M M 62 Primary Reserved Private — 62 C C 72 Data Record C C 93 Transaction Destination Institution ID Code C C 94 Transaction Originator Institution ID Code C C 100 Receiving Institution ID Code C C Include if a data element greater than 64 is present. Include when the receiving institution is not the same as the final destination of the message. Network Management Request/Repeat (MTI 1804/1805) The following table describes the BASE24-eps data element defaults for Network Management Request (1804) and Network Management Request Repeat (1805) messages. Bit Data element name In Out 1 Secondary Bit Map C C 7 Date and Time, Transmission M M 11 Systems Trace Audit Number M M 12 Date and Time, Local Transaction M M BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 Notes Include if a data element greater than 64 is present. 119 Data element defaults Bit Data element name In Out 24 Function Code M M Notes Valid values are as follows: 801 = Sign on combined (iss/acq) 802 = Sign off combined (iss/acq) 809 = Key request inbound key 810 = Key request outbound key 811 = Key change both keys 817 = Key change inbound 818 = Key change outbound 819 = Sign on acquirer only 820 = Sign on issuer only 823 = Sign off acquirer only 824 = Sign off issuer only 831 = Echo test 28 Date, Reconciliation C C Include if this message is used for cutover or checkpoint reconciliation. 29 Reconciliation Indicator C C Include if this message is used for checkpoint reconciliation. (future) 33 Forwarding Institution ID Code C C Include when the forwarding institution is not the same as the institution originating the message. 93 Transaction Destination Institution ID Code C C 94 Transaction Originator Institution ID Code C C 96 Key Management Data C C 100 Receiving Institution ID Code C C Include when the receiving institution is not the same as the final destination of the message. Network Management Request Response (MTI 1814) The following table describes the BASE24-eps data element defaults for Network Management Request Response (1814) messages. Bit Data element name In Out 1 Secondary Bit Map C C 7 Date and Time, Transmission M M BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 Notes Include if a data element greater than 64 is present. 120 Data element defaults Bit Data element name In Out 11 Systems Trace Audit Number M E 12 Date and Time, Local Transaction M E 24 Function Code M E 28 Date, Reconciliation C E 29 Reconciliation Indicator C E 33 Forwarding Institution ID Code C C 39 Action Code M M 59 Transport Data C E 93 Transaction Destination Institution ID Code C E 94 Transaction Originator Institution ID Code C E 96 Key Management Data C C 100 Receiving Institution ID Code C C Notes Include when the forwarding institution is not the same as the institution originating the message. Include when the receiving institution is not the same as the final destination of the message. Administrative Fraud Report (MTI 9620) The following table describes the BASE24-eps data element defaults for Administrative Fraud Report (9620) messages. Bit Data element name In 1 Secondary Bit Map C 2 Primary Account Number M 4 Amount, Transaction C 7 Date and Time, Transmission M 11 Systems Trace Audit Number M 12 Date and Time, Local Transaction C 14 Date, Expiration C 22 Point of Service Data Code C 24 Function Code M BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 Out Notes Include if a data element greater than 64 is present. The only valid value is 650 (Unable to parse message). 121 Data element defaults Bit Data element name In 26 Card Acceptor Business Code C 32 Acquirer Institution ID Code C 33 Forwarding Institution ID Code C 37 Retrieval Reference Number M 41 Card Acceptor Terminal ID C 42 Card Acceptor ID Code C 43 Card Acceptor Name/Location M 49 Currency Code, Transaction M 54 Additional Amounts C 62 Primary Reserved Private — 62 M 72 Data Record M 100 Receiving Institution ID Code M 123 Primary Reserved Private—123 M Out Notes Include when the forwarding institution is not the same as the institution originating the message. Include when the receiving institution is not the same as the final destination of the message. Administrative Fraud Report Response (MTI 9630) The following table describes the BASE24-eps data element defaults for Administrative Fraud Report Response (9630) messages. Bit Data element name In Out 1 Secondary Bit Map C 2 Primary Account Number E 7 Date and Time, Transmission M 11 Systems Trace Audit Number E 32 Acquirer Institution ID Code E 37 Retrieval Reference Number M 39 Action Code M 62 Primary Reserved Private — 62 C 100 Receiving Institution ID Code C 123 Primary Reserved Private—123 C BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 Notes Include if a data element greater than 64 is present. Include when the receiving institution is not the same as the final destination of the message. 122 Section 4: Data element definitions Data element definitions The BASE24-eps ISO 8583:1993 host external message contains primary and secondary data elements. • • Primary data elements are data elements P-1 through P-64. They are called primary because their presence in the message is controlled by the primary bit map of the message. Secondary data elements are data elements S-65 through S-128. They are called secondary because their presence in the message is controlled by the secondary bit map of the message (data element P-1). General data element specifications General specifications are provided here about how different types of data elements must be populated. Fixed-length data elements Data placed in numeric, fixed-length data elements must be right-justified, with leading zeros. Data placed in all other fixed-length data elements must be left-justified, with trailing blanks. Variable-length data elements Data placed in variable-length data elements can vary in length from zero positions up to the individual maximum length stated for the data element. The actual length of the data placed in a variable-length data element must always be specified in a fixed-length prefix immediately preceding the data. This fixed-length prefix is known as the data element length indicator. • • • For variable-length data elements with a maximum length of less than 100 characters, a two-position data element length indicator precedes the data element. For variable-length data elements with a maximum length greater than 99 and less than 1,000 characters, a three-position data element length indicator precedes the data element. For variable-length data elements with a maximum length greater than 999 and less than 10,000 characters, a four-position data element length indicator precedes the data element. These prefixes must be right-justified and zero filled. For example, if a variable-length data element could be up to 200 characters, but only seven characters were actually to be loaded into the element, the required data element length indicator would be 007. In this case, if the seven characters were 1234567, the entire data element to be included in the external message would be 0071234567—ten positions in all. Otherwise, if the data element had been limited to a maximum of less than 100 characters, the data element length indicator would be 07, and the entire data element would be 071234567—nine positions in all. In the data element documentation, the required presence of a data element length indicator is denoted using an LLVAR, LLLVAR, or LLLLVAR notation in the Format field. The LL, LLL, and LLLL represent the two-, three-, or four-position data element length indicators and the VAR represents the data itself (which could consist of one or more fields). Note: The data element length indicator itself is not included in the documented size of the data element data. The following table provides several examples of how data element data is documented. Format Indicator Length Data Size Total Data Element Length LLVAR AN ..37 2 37 39 LLLVAR ANS ..500 3 500 503 BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 123 Data element definitions Format Indicator Length Data Size Total Data Element Length LLLVAR ANS ..999 3 999 1,002 LLLLVAR ANS ..9999 4 9,999 10,003 Zero-length data elements BASE24‑eps can include zero-length data elements if a host has inadvertently made mandatory a data element that BASE24‑eps does not support. If a BASE24‑eps application has no data to place in a mandatory data element, it simply sets the data element length indicator to zeros (00, 000, or 0000) and sends the indicator. Tagged and subtagged data A number of data elements use a tag and subtag scheme for identifying the information they carry: • • • • • • • P-44: Additional Response Data P-62: Primary Reserved Private S-72: Data Record S-96: Key Management Data S-123: Reserved for Private Use S-124: Reserved for Private Use S-127: Reserved for Private Use Tagged data Using a tag scheme, each piece of information that can be carried in the data element is defined individually and identified by a two-digit tag. In this case, each data item that can be included in the data element is structured in the following manner: a tag identifying the type of data, followed immediately by a length indicator identifying the length of the data, followed immediately by the data itself. (Depending on the size of the data element, the length indicator for a tag can be two, three, or four digits.) The following illustration depicts the format of a tagged piece of data (in this case, with a three-digit length indicator): Because tagged data items are self-contained and uniquely identified by their tags, they can be included as needed and in any order within a data element. Tags are defined specifically for those data elements that support them. Refer to the data element descriptions for information on their supported tags. Subtagged data The contents of certain tags (for example, tags 01 and 02 of the S-72 data element) are further defined using a subtag scheme. In this case, the various pieces of information that can be carried in a particular tagged data item are themselves defined individually and identified by one or two-position subtags. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 124 Data element definitions Subtags allow specific pieces of information to be included in tags in the same way that tags allow specific pieces of information to be included in data elements. Each piece of subtagged data is structured in the following manner: the subtag identifying the type of data, followed immediately by a three-digit length indicator identifying the length of the subtag data, followed immediately by the subtag data itself. (Note that the length indicator for a subtag is always three digits.) Because subtagged data items are self-contained and uniquely identified by their subtags, they can be included as needed and in any order within the tag for which they are defined. Subtags are defined specifically for those tags that support them. Refer to the tag descriptions for information on any supported subtags. Generic data mapping The Reserved for Private Use (S-124) data element is used to pass unmapped data fields as received from network interfaces (such as Visa and Banknet) through to the host. This data is predominately obtained from the Generic Data TDE in which it is stored using an outer key indicating the interface (or, in the case where ISO standard fields are used, a generic tag of "ACQ_DATA") and an inner key with a descriptive label of the field. These labels are mapped to 2-character tags and subtags using 2 new data sources. The mapping between the tag and Generic Data TDE outer key is configured in the Genrc_Data_Outer_Tag data source, and the mapping between the subtag and the Generic Data TDE inner key is configured in the Genrc_Data_Inner_Tag data source. Data element documentation conventions Data elements are documented using two standard fields (an example is shown here), followed by a description of how the data element is used and the applicable codes and values that can be used to populate the data element. The contents of the standard fields are described below. Format: AN 16 TDEs: ISO 93 Format States the attributes for the data element. The values used to represent the attributes (shown here) are based on the ISO 8583:1993 standards: Attribute values Value Description A Alphabetic characters N Numeric characters P Space (pad) characters S Special characters AN Alphabetic and numeric characters AS Alphabetic and special characters NS Numeric and special characters ANS Z Alphabetic, numeric, and special characters Track 2 and 3 code set as defined in ISO 4909 and ISO 7813. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 125 Data element definitions Attribute values Value Description LLVAR Indicates that the data element is variable length and that the variable-length data (VAR) must be prefixed by a two-position length indicator (LL). This notation is used when the variable-length data can be 01–99 in length. LLLVAR Indicates that the data element is variable length and that the variable-length data (VAR) must be prefixed by a three-position length indicator (LLL). This notation is used when the variable-length data can be 001–999 in length. LLLLVAR Indicates that the data element is variable length and that the variable-length data (VAR) must be prefixed by a four-position length indicator (LLLL). This notation is used when the variable-length data can be 0001–9999 in length. For fixed-length fields, the characters listed above are followed by the number of characters in the field. For example, N 19 is a numeric field that contains 19 bytes always, padded to the left with zeros when applicable; AN 19 is an alphanumeric field that contains 19 bytes always, left justified with trailing spaces. For variable-length fields, the characters listed above are followed by two dots and the maximum number of characters that can be carried in the field (for example, N ..19 indicates that the field is a variable-length, numeric field, that can be from zero to 19 characters in length; ANS ..999 indicates that the field is a variable-length field containing alphabetic, numeric, and special characters, that can be from zero to 999 characters in length). X+ is used with some amounts to indicate that they must be preceded by a minus sign (–) or the value C if the amount is a credit or a plus sign (+) or the value D if the amount is a debit. The exact values used are described in individual data element descriptions. Note that this adds one to the given length of the field. Date and time formats are shown using the following values: Date and time formats Value YY or YYYY Description Year MM Month DD Day HH Hour MM Minute SS Second hh Hundredths of a second mmmmmm Microseconds (millionths of a second) TDEs Lists the Transaction Data Elements (TDEs) used by the BASE24-eps system to carry the data internally. For inbound messages, the external data element is mapped to these TDE(s). For outbound messages, these TDE(s) are mapped to the external data element. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 126 Data element definitions Required blank spaces Throughout the documentation when discussing the impact of required blanks or spaces in entered field data, an italicized b is used to denote a required blank character or space. P-1: Secondary Bit Map Format: AN 16 TDEs: ISO 93 Identifies the presence or absence of data elements 65 through 128 in the BASE24-eps ISO ‘93 host external message. This data element functions the same as the primary bit map for the message, except that the primary bit map identifies the presence or absence of data elements 1 through 64, and the secondary bit map identifies the presence or absence of data elements 65 through 128. This data element is required if any of data elements 65 through 128 are included in the message. Otherwise, it is not used. The presence or absence of this data element is identified by bit position 1 in the primary bit map. Data elements 65 through 128 cannot be included in the message if the secondary bit map is not present. P-2: Primary Account Number Format: LLVAR N ..19 TDEs: PAN (tde.pan) Contains the primary account number (PAN) of the cardholder account involved in the transaction or update request being processed. In reconciliation or fee collection messages, this data element contains the card issuer’s institution identification number only. P-3: Processing Code Format: AN 6 TDEs: Processing Code (tde.proc_cde, tde.proc_cde_txn_cde, tde.proc_cde_acct1_typ, tde.proc_cde_acct2_typ) Network Original Processing Code (tde.netwk_orig_proc_cde) Contains the processing code associated with the transaction. This data element is mandatory for all messages except network management and file update messages. The first two characters of this data element contain a transaction code that describes the specific transaction. The third and fourth characters of this data element identify the customer account type affected for debits and inquiries or the from account for transfers. The fifth and sixth characters of this data element identify the customer account type affected for credits or the to account for transfers and payments. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 127 Data element definitions Transaction codes supported by BASE24-eps Transaction codes are two-position values that identify the basic type of transaction being processed. Transaction codes are the first two positions of the transaction processing code. BASE24-eps supports the transaction code values listed in the following table. Not all acquirers and issuers support all of the transaction codes listed. Nor do all acquirers and issuers support all transaction code and account type combinations that could be included in a processing code recognizable to BASE24-eps. Refer to the vendor documentation for your acquiring and issuing endpoints to determine the processing codes (transaction code and account type combinations) supported by the endpoint. Table Key: The Transaction Code column identifies the transaction code. The Description column describes the action represented by the transaction code. The Define Name column lists the define name used for the transaction code by BASE24-eps. Transacti Description on code Define name blanks Blank – No Transaction Code tc_space_d 00 Debit – Goods and Services tc_db_goods_svc_d 01 Debit – Cash tc_db_cash_d 02 Debit – Adjustment tc_db_adj_d 03 Debit – Check Guarantee (funds guaranteed) tc_db_chq_guar_d 04 Debit – Check Verification (funds available but not guaranteed) tc_db_chq_vrfy_d 05 Debit – Eurocheque tc_db_euro_chq_d 06 Debit – Travelers Check tc_db_tchq_d 07 Debit – Letter of Credit tc_db_letter_cr_d 08 Debit – Giro (Postal Banking) tc_db_giro_d 09 Debit – Goods and Services with Cash Disbursement tc_db_goods_svc_cb_d 0A Private – Phone Top-Up tc_prvt_phn_top_up_d 0B Debit – Fee Collection tc_db_fee_collection_d 0C 0C – Transfer FROM tc_xfer_db_d 10 Debit – Non-cash Financial Instrument (e.g., Wire Transfer) tc_db_non_cash_d 11 Debit – Quasi-cash and Scrip tc_db_scrip_d 17 Debit – Fast Cash tc_db_fast_cash_d 18 Debit – Private Use tc_db_prvt_18_d 19 Debit – Private Use tc_db_prvt_19_d 20 Credit – Return tc_cr_return_d 21 Credit – Deposit tc_cr_dep_d 22 Credit – Adjustment tc_cr_adj_d 23 Credit – Check Deposit Guarantee tc_cr_chq_dep_guar_d BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 128 Data element definitions Transacti Description on code Define name 24 Credit – Check Deposit tc_cr_chq_dep_d 28 Credit – Deposit with Cash Back tc_cr_dep_cb_d 29 Credit – Check Deposit with Cash Back tc_cr_chq_dep_cb_d 2A Funds Dispursement tc_funds_disburse_d 2B Credit – Prepaid Load tc_cr_pre_pd_load_d 2C Original Credits tc_orig_cr_d 2D Cash Deposit with Cash Back tc_cr_cash_dep_cb_d 2E Cash Deposit tc_cr_cash_dep_d 2F Split Deposit tc_split_deposit_d 2G Transfer TO tc_xfer_cr_d 2H Automated Deposit tc_cr_adep_d 30 Inquiry – Available Funds Inquiry tc_inq_avail_funds_d 31 Inquiry – Balance Inquiry tc_inq_bal_d 38 Card Verification tc_inq_crd_vrfy_d 39 Statement Print (inbound/outbound) tc_inq_stmt_prnt_d 3A Mini-Statement Inquiry Check Clear (inbound/outbound) tc_inq_chq_clr_d 3B Mini-Statement Inquiry Last Debit/Credit (inbound/ outbound) tc_inq_last_dbcr_d 3C Mini-Statement Inquiry Last Source (inbound/outbound) tc_inq_last_src_d 3D Mini-Statement Inquiry Last Check (inbound/outbound) tc_inq_last_chq_d 3E Mini-Statement Inquiry Last Debit (inbound/outbound) tc_inq_last_db_d 3F Mini-Statement Inquiry Last Credit (inbound/outbound) tc_inq_last_cr_d 3G Mini-Statement Inquiry Last Transfer (inbound/ outbound) tc_inq_last_xfer_d 3H Inquiry – Customer Vendor tc_inq_cust_vndr_d 3J Inquiry – Scheduled Payment tc_inq_sched_pmnt_d 3K Inquiry – Scheduled Transfer tc_inq_sched_xfer_d 3L Inquiry – Last Payment and Transfer tc_inq_last_pmnt_and_xfer_d 3M Inquiry – Scheduled Transaction tc_inq_sched_txn_d 3N Inquiry – Account List tc_inq_acct_list_d 3R Preferred Transaction Inquiry tc_inq_prfr_txn_inq_d 3S Multiple Account Inquiry tc_inq_mult_acct_bal_d 3T Billpay ID Inquiry tc_inq_billpay_id_d 3U Account Detail Inquiry tc_inq_acct_detl_d BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 129 Data element definitions Transacti Description on code Define name 3V Deposit Verification tc_inq_adep_vrfy_d 40 Transfer – Cardholder Accounts Transfer tc_xfer_acct_d 48 Transfer – Private Use tc_xfer_prvt_48_d 49 Transfer – Private Use tc_xfer_prvt_49_d 4A Transfer – Future tc_xfer_acct_futr_d 4B Transfer – Recurring tc_xfer_acct_recur_d 50 Payment (can include both a from and to account type) tc_pmnt_d 56 Payment to (only a to account is present) tc_pmnt_to_d 58 Payment Enclosed tc_pmnt_enclose_d 59 Payment – Private Use tc_pmnt_prvt_59_d 5A Payment – Payment Future tc_pmnt_futr_d 5B Payment – Recurring tc_pmnt_recur_d 5C Bulk Authorization tc_pmnt_bulk_auth_d 5D Return Payment tc_pmnt_rtrn_d 5E Scheme Return Payment tc_pmnt_schme_rtrn_d 5F Corporate Dated Payment tc_pmnt_corp_futr_d 5G Payment To Third Party tc_pmnt_to_thrd_prty_d 5H Payment From Third Party tc_pmnt_from_thrd_prty_d 5I QR Payment, private tc_pmnt_prvt_qr 7S Private Use – PIN Unblock tc_pin_unblk_d 7T Private Use – EMV Management PIN Change tc_prvt_emv_mgmt_pin_chng_d 7U Private Use – EMV Management PIN Unblock tc_prvt_emv_mgmt_pin_unblk_d 90 PIN Change tc_prvt_pin_chng_d 91 PIN Verify tc_prvt_pin_vrfy_d 92 Private Use – Close Batch tc_prvt_setl_btch_clos_d 93 Private Use – Close Day tc_prvt_setl_dly_clos_d 94 Private Use – Close Shift tc_prvt_setl_shift_clos_d 95 Private Use – Batch Subtotals tc_prvt_setl_ttls_d 95 Private Use – Administrative Subtotals tc_prvt_admin_subttl_d 95 Private Use – Network Management Message tc_prvt_nmm_d 96 Private Use – Administrative Load tc_prvt_admin_load_rqst_d 97 Private Use – Initial Cash tc_prvt_setl_init_cash_d 98 Private Use – Add Cash tc_prvt_setl_add_cash_d BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 130 Data element definitions Transacti Description on code Define name 99 Private Use – EMV Script Management tc_prvt_emv_script_mgmt_d 9A Private Use – Scheduled Payment tc_prvt_sched_pmnt_d 9B Private Use – Scheduled Future Payment tc_prvt_sched_pmnt_futr_d 9C Private Use – Scheduled Recurring Payment tc_prvt_sched_pmnt_recur_d 9D Private Use – Scheduled Future Transfer tc_prvt_sched_xfer_futr_d 9E Private Use – Scheduled Recurring Transfer tc_prvt_sched_xfer_recur_d 9F Private Use – Delete Scheduled Payment tc_prvt_sched_pmnt_del_d 9G Private Use – Delete Scheduled Transfer tc_prvt_sched_xfer_del_d 9H Private Use – Change Scheduled Payment tc_prvt_sched_pmnt_chng_d 9I Private Use – Administrative Check Proof List tc_prvt_cpl_prnt_d 9J Private Use – Change Scheduled Transfer tc_prvt_sched_xfer_chng_d 9K Private Use – Customer Add tc_prvt_cust_sign_up_d 9L Private Use – Customer Inquiry tc_prvt_cust_info_inq_d 9M Private Use – Customer Update tc_prvt_cust_info_chng_d 9N Private Use – Customer Vendor Add tc_prvt_cust_vndr_add_d 9P Private Use – Customer Vendor Delete tc_prvt_cust_vndr_del_d 9Q Private Use – Customer Vendor Update tc_prvt_cust_vndr_chng_d 9R Private Use – Master Vendor List Inquiry tc_prvt_mstr_vndr_inq_d 9S Private Use – Master Vendor Add tc_prvt_mstr_vndr_add_d 9T Private Use – Customer Vendor Master List tc_prvt_cust_vndr_mstr_list_d 9U Private Use – Phone Top-Up tc_prvt_phn_crd_pur_d 9V Private Use – Loan Application tc_prvt_loan_appl_d 9W Private Use – Message to Bank tc_prvt_msg_to_bnk_d 9X Private Use – History Inquiry – All Transactions tc_prvt_hist_inq_d 9Y Private Use – Administrative Balance Standard Cash tc_prvt_admin_bal_std_cash_d 9Z Private Use – Administrative Balance Current Cash tc_prvt_admin_bal_cur_cash_d A0 Private Use – Prepaid Activation tc_prvt_pre_pd_actvty_d A1 Private Use – Log Only tc_prvt_log_only_d A2 Private Use – Check Cashing tc_prvt_chq_cash_d A3 Private Use – Card Capture tc_prvt_crd_captr A4 Private Use – Card Return tc_prvt_crd_rtrn A5 Private Use – EMV Log Only tc_prvt_emv_log_only_d BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 131 Data element definitions Transacti Description on code Define name A6 Private Use – Online Personalization Terminal (OPT) transaction tc_prvt_german_opt_d A7 Private Use – GeldKarte transaction tc_prvt_german_gdk_d A8 Private Use – Preferred Transaction Set-Up tc_prvt_prfr_txn_setup_d A9 Private Use – Passbook Update tc_prvt_psbk_updt_d AA Private Use – Stored Value Full Redemption tc_prvt_sv_full_rdmp_d AB Private Use – Stored Value Replenishment tc_prvt_sv_rplnsh_d AC Private Use – Stored Value Card Activation tc_prvt_svc_actvtn_d AD Private Use – Stored Value Add Card Activation tc_prvt_svc_add_actvtn_d AE Instrument Settlement Totals tc_prvt_setl_instrm_ttls_d AF Clerk Settlement Totals tc_prvt_setl_clerk_ttls_d AH Private Token Request tc_prvt_tkn_rqst_d AJ Tokenization Provisioning Authorization tc_prvt_tknztn_auth_prvsn_d AK Tokenization Provisioning Notification tc_prvt_tknztn_ntfy_prvsn_d P Private Use – CSM Use tc_prvt_rpq_2_d Q Private Use – CSM Use tc_prvt_rpq_3_d R Private Use – CSM Use tc_prvt_rpq_1_d U User defined. Can be any value that starts with a “U” (U0-UZ). These can include log-only transactions. tc_prvt_user_def_d X Private Use – Channel Use tc_prvt_dist_1_d Y Private Use – Channel Use tc_prvt_dist_2_d Z Private Use – Channel Use tc_prvt_dist_3_d From and To account types supported by BASE24-eps From account types and to account types are two-position values that identify the account types involved in a transaction: from account type, the type of account from which funds are being taken by the transaction; to account type, the type of account to which funds are being added by the transaction. From account types are the third and fourth positions of the transaction processing code. To account types are the fifth and sixth positions of the transaction processing code. BASE24-eps supports the from and to account values listed in the following table. Not all acquirers and issuers support all of the account types listed. Nor do all acquirers and issuers support all transaction code and account type combinations that could be included in a processing code recognizable to BASE24-eps. Refer to the vendor documentation for your acquiring and issuing endpoints to determine the processing codes (transaction code and account type combinations) supported by the endpoint. Table Key: The Code column identifies the account type. The Description column describes the account type. Code Description 00 Not specified BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 132 Data element definitions Code Description 10 Savings 20 Checking (DDA) 30 Credit 38 Credit line 40 Universal account 50 Investment account 58 CD 59 IRA 60 Stored Value – Reloadable cash card account (transfer value) 67 Stored Value – Disposable cash card 90 NOW 9A Commercial loan 9B Installment loan 9C Mortgage loan 9M Other P-4: Amount, Transaction Format: N 12 TDEs: Transaction Amount (tde.txn_amt_crncy_cde, tde.txn_amt, tde.txn_amt_set) Contains the amount of funds requested (either for debit or credit) in the currency used by BASE24-eps for processing the transaction. • • In the case of an inbound transaction from an acquirer host, this is the transaction amount in the currency used by BASE24-eps for processing the transaction ( such as prescreening and logging). In the case of an outbound transaction to an issuer host, this is the transaction amount in the currency used by BASE24-eps for processing the transaction, which may or may not be the amount and currency in which the transaction was acquired (for example, in the case of transactions from an acquiring interchange). The transaction amount includes the amount of any surcharge assessed to the transaction. If the surcharge has a value added tax (VAT) that applies to it, the VAT amount can also be added to the transaction amount, but only if the VAT issuer indicator is set to combine. • • • For fully- or partially-approved transactions, this data element contains the authorized amount, including the surcharge amount and VAT. (The requested amount for a partially approved transaction is carried in the P-30: Amounts, Original data element.) For declined transactions, this data element contains a value of zero. (The requested amount for a declined transaction is carried in the P-30: Amounts, Original data element.) For full reversal transactions, this data element contains the original transaction amount, including the surcharge amount, and the VAT amount if it was combined with the transaction amount in the original transaction. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 133 Data element definitions • • For partial reversal transactions, this data element contains the completed transaction amount, including or not including the surcharge amount and VAT amount. The surcharge amount and VAT amount can be included on inbound transactions and excluded on outbound transactions as required by the external entity. For a stop payment order, this data element can contain the specific amount that the issuer has identified as the stop payment amount. If this data element is not provided for a stop payment order, payment is stopped for any amount from the specified merchant. Stop payment orders are currently supported as pass-through transactions only on the BASE24-eps system. Note: Two-sided transactions (transfers) with a surcharge must subtract the surcharge amount from the transaction amount when applying the amount to the to side of the transaction. The surcharge amount could be positive or negative. The from side of a two-sided transaction should use the transaction amount as is with the surcharge included. Decimalization of the amount is implied by the P-49: Currency Code, Transaction data element. For example, if the currency code indicates U.S. dollars, 000000001000 would indicate $10.00. However, if the currency code indicates a currency with three decimal positions, such as the Kuwaiti dinar, 000000001000 would indicate 1.000 dinars. The amount carried in this data element is exclusive of all fees applied to the transaction except for a surcharge and possibly the VAT, which is included in the amount. Transaction fee amounts are carried in the P-46: Amounts, Fees data element. The amount of the surcharge and VAT is also provided in P-46: Amounts, Fees even though it can be included in the P-4: Amount, Transaction data element. P-5: Amount, Reconciliation Format: N 12 TDEs: Settlement Amount (tde.amt_stl) or Issuer Settlement Amount (tde.amt_iss_setl) Contains the amount of funds to be transferred between the acquirer and card issuer—equal to the amount of funds carried in the Amount, Transaction data element in the currency of reconciliation. On outbound transactions for an acquirer interface, this field is set from the Settlement Amount TDE. This TDE contains the acquirer settlement amount in acquirer settlement currency. It may contain the completed settlement amount for partial reversals, although support for completed settlement amount varies. This amount includes the transaction amount and may include additional fees. Although this amount is mainly used for informational purposes, to save and echo back, it can be used for settlement. On outbound transactions for an issuer interface, this field is set from the Issuer Settlement Amount TDE. This TDE contains the issuer settlement amount in issuer settlement currency. It may contain the completed issuer settlement amount for partial reversals, although support for completed settlement amount varies. This amount includes the transaction amount and may include additional fees. Normally, the issuer generates the amount. Although this amount is mainly used for informational purposes, to save and echo back, it can be used for settlement. P-7: Transmission Date and Time Format: N 10 (MMDDhhmmss) TDEs: Transmission Date and Time (tde.xmit_dat_tim) BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 134 Data element definitions Contains the date and time the message is initiated by the message originator. This time is set for each outgoing message and is expressed in Greenwich Mean Time (GMT). The Transmission Date and Time data element is mandatory for all message types. For inbound messages, this data element is dropped. On outbound messages, the BASE24-eps ISO 93 Host Interface component invokes the Time object for the date and time sent in this data element. P-9: Conversion Rate, Reconciliation Format: N8 TDEs: Settlement Amount (tde.ccr_stl) or Issuer Settlement Amount (tde.ccr_iss_setl) Contains the factor used in the conversion from transaction to reconciliation amount. The amount of the transaction (carried in the Amount, Transaction data element) is multiplied by this factor to obtain the reconciliation amount (carried in the Amount, Reconciliation data element). The leftmost digit (i.e., position 1) of this data element denotes the number of positions the decimal separator must be moved from the right. Positions 2–8 of this data element specify the rate. For example, a conversion rate value of 91234567 in this data element would equate to 0.001234567. The maximum number of digits to the right of the decimal separator is 9, provided the first two digits to the right of the decimal separator are zeros. P-6: Amount, Cardholder Billing Format: N 12 TDEs: Cardholder Billing Information (tde.amt_chb, tde.amt_chb_set) This TDE may contain the completed cardholder billing amount for partial reversals, although support for completed cardholder billing amount varies. It includes the transaction amount and may include additional fees. Although this TDE is mainly used for informational purposes, to save and echo back, it can be used for authorization. Contains the amount billed to the cardholder in the currency of the cardholder account and exclusive of cardholder billing fees. P-10: Conversion Rate, Cardholder Billing Format: N8 TDEs: Cardholder Billing (tde.chb_info) Contains the factor used in the conversion from transaction to cardholder billing amount. The amount of the transaction (carried in the Amount, Transaction data element) is multiplied by this factor to obtain the cardholder billing amount (carried in the Amount, Cardholder Billing data element). The leftmost digit (i.e., position 1) of this data element denotes the number of positions the decimal separator must be moved from the right. Positions 2–8 of this data element specify the rate. For example, a conversion rate value of 91234567 in this data element would equate to 0.001234567. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 135 Data element definitions The maximum number of digits to the right of the decimal separator is 9, provided the first two digits to the right of the decimal separator are zeros. P-11: Systems Trace Audit Number Format: N6 TDEs: Issuer STAN (tde.iss_stan) or Acquirer STAN (tde.acq_stan) For stop payment order requests, this data element is also mapped to the Sequence Number TDE if the Retrieval Reference Number (P-37) data element is not present in the message. Contains a number that must be set by a message sender and echoed by a message receiver. It is used for matching responses to original messages, and there is no requirement to maintain the same value throughout the life of a transaction (for example, a reversal might not have the same number as the original transaction). The Systems Trace Audit Number data element is mandatory for all messages to and from BASE24-eps. P-12: Date and Time, Local Transaction Format: N 12 (YYMMDDhhmmss) TDEs: Local Date and Time (tde.local_dat_tim) Contains the local date and time at which the transaction began at the card acceptor location. Since a terminal can be geographically removed from the BASE24-eps system by one or more time zones, BASE24-eps maintains time zone offsets for terminals defined to the system. These offsets enable BASE24-eps applications to compute local transaction times and dates for transactions originating at BASE24-eps terminals. The time zone offset for a terminal is applied to the system date and time to derive the local date and time for the transaction. When a transaction originates at an acquirer host, it is assumed that the content of this data element is the terminal’s local date and time. P-13: Date, Effective Format: N 4 (YYMM) TDEs: Effective Date (tde.eff_dat) Contains the year and month in which the instrument (e.g., card) becomes effective. P-14: Date, Expiration Format: N 4 (YYMM) TDEs: Expiration Date (tde.exp_dat) Contains the year and month after which an instrument (e.g., card) expires. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 136 Data element definitions This data element is mandatory for 1100, 1101, 1120, 1121, 1140, 1200, 1201, 1220, 1221, and 1240 messages, based on availability. It is optional for 1304/1305 messages. For updates to the American Express Global Network Solutions (AEGN) Network Exception File, this data element indicates the date on which a record is to be removed from the file. P-15: Date, Settlement Format: N 6 (YYMMDD) TDEs: Acquirer Switch Capture Date (tde.acq_captr_dat) Issuer Switch Capture Date (tde.iss_capture_date) This data element is mapped to and from the Acquirer Switch Capture Date TDE for an acquirer interface or the Issuer Switch Capture Date TDE for an issuer interface. The Acquirer Switch Capture Date TDE is used for settlement with the acquiring entity. This is the acquirer that is communicating with the BASE24-eps system, which is not necessarily the original transaction acquirer. The Issuer Switch Capture Date TDE is used for settlement with the instrument issuer. This is the issuer that is communicating with the BASE24-eps system, which is not necessarily the actual instrument issuer. Contains the year, month, and day on which funds are transferred between the transaction acquirer and the instrument (e.g., card) issuer. This is the date on which an interchange settles with the BASE24-eps system. Internally, BASE24-eps carries this date as eight characters (YYYYMMDD). P-16: Date, Conversion Format: N 4 (MMDD) TDEs: Conversion Date (tde.conversion_date) Contains the month and day the conversion rate is effective to convert the transaction amount from the original to the reconciliation currency. P-17: Date, Capture Format: N 4 (MMDD) TDEs: Capture Date (tde.captr_dat) This data element is mapped from the Capture Date TDE on outbound transactions. For inbound transactions, this data element is set in the Capture Date TDE. If this data element is not present in the transaction, the Capture Date TDE is set by the system, based on the LGNT-CUTOVER Environment attribute. For five-day settlement processing, this data element must be set by the host. The Capture Data TDE determines to which Journal data source (Journal) a transaction is written. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 137 Data element definitions Contains the month and day the transaction data was logged to the Journal data source (Journal) on the BASE24eps system. This data element is only used when the Endpoint Type field on the ISO8583 (93) Host tab of the ISO Host Interface Configuration window is set to “Host”. P-18: Merchant Type Format: N4 TDEs: Merchant Type (tde.mrch_typ) Contains the Standard Industrial Classification (SIC) code of the retailer involved in the transaction. P-19: Country Code, Acquiring Institution Format: N3 TDEs: Country code in the Acquirer TDE (tde.acq_cntry_cde) Contains the country code of the country where the acquiring institution is located (see ISO 3166). P-21: Country Code, Forwarding Institution Format: N3 TDEs: Country code in the Forwarding Institution TDE (tde.frwd_inst_cntry_cde) Contains the country code of the country where the forwarding institution is located (see ISO 3166). P-22: Point of Service Data Code Format: AN 12 TDEs: Point of Service (tde.pt_cmpnt_crd_captr_cap, tde.pt_cmpnt_crd_input_cap, tde.pt_cmpnt_crd_input_mde, tde.pt_cmpnt_crd_output_cap, tde.pt_cmpnt_crd_prsn, tde.pt_cmpnt_crdhldr_auth_cap, tde.pt_cmpnt_crdhldr_auth, tde.pt_cmpnt_crdhldr_auth_method, tde.pt_cmpnt_crdhldr_prsn, tde.pt_cmpnt_oper_envmt, tde.pt_cmpnt_pin_captr_cap, tde.pt_cmpnt_term_output_cap) Contains the point of service data associated with the transaction. This data is used to indicate specific conditions that are (or were) present at the time a transaction took place at the point of service or when the transaction was initiated. Note: Some other alphabetic values are supported in the ISO specification for the given positions of the point of service data code. These are all reserved values for ISO, national or private use fields. These values can be passed through the system if received from an acquirer by BASE24-eps. Only the numeric and known values are represented below. Position 1 – Card Data Input Capability Position 1 contains a code indicating the primary means of getting the card information into the terminal. Valid values are: BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 138 Data element definitions Code Description 0 Unknown 1 Manual 2 Magnetic stripe read 3 Bar code 4 OCR 5 ICC 6 Key Entry 7 Proximity ICC 8 Proximity magnetic stripe Position 2 – Cardholder Authentication Capability Position 2 contains a code indicating the primary means of verifying the cardholder at this terminal. Valid values are: Code Description 0 No electronic authentication 1 PIN 2 Electronic signature analysis 3 Biometrics 4 Biographic 5 Electronic authentication inoperative 6 Other 7 Reserved for ISO use 8 Reserved for national use 9 Reserved for private use A mPOS software PIN entry capability Position 3 – Card Capture Capability Position 3 contains a code indicating whether the terminal has the ability to capture a card. Valid values are: Code Description 0 None 1 Capture 2–4 Reserved for ISO use 5–7 Reserved for national use 8–9 Reserved for private use BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 139 Data element definitions Position 4 – Operating Environment Position 4 contains a code indicating whether the terminal is attended by the card acceptor and its location. Valid values are: Code Description 0 No terminal used 1 On premises of card acceptor, attended 2 On premises of card acceptor, unattended 3 Off premises of card acceptor, attended 4 Off premises of card acceptor, unattended 5 On premises of cardholder, unattended 6 Off premises of cardholder, unattended 7 Reserved for ISO use 8 Reserved for national use 9 Reserved for private use Z Transit terminal Position 5 – Cardholder Present Position 5 contains a code indicating whether the cardholder is present at the point of service and if not, why not. Valid values are: Code Description 0 Cardholder present 1 Cardholder not present, unspecified 2 Cardholder not present, mail order 3 Cardholder not present, telephone 4 Cardholder not present, standing authorization 5 Cardholder electronic order 6 Reserved for ISO use 7–8 Reserved for national use 9 Reserved for private use S Cardholder Installment Payment Position 6 – Card Present Position 6 contains a code indicating whether the card is present at the point of service. Valid values are: Code Description 0 Card not present 1 Card present BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 140 Data element definitions Code Description 2–4 Reserved for ISO use 5–7 Reserved for national use 8–9 Reserved for private use Position 7 – Card Data Input Mode Position 7 contains a code indicating the method used to input the information from the card to the terminal. Valid values are: Code Description 0 Unspecified 1 Manual 2 Magnetic stripe read 3 Bar code 4 OCR 5 ICC 6 Key entered 7 Complete magnetic stripe 8 Electronic commerce 9 Proximity ICC A Proximity magnetic stripe B Voice PAN Position 8 – Cardholder Authentication Method Position 8 contains a code indicating the method for verifying the cardholder identity. Valid values are: Code Description 0 Not authenticated 1 PIN 2 Electronic signature analysis 3 Biometrics 4 Biographic 5 Manual signature verification 6 Other manual verification (e.g., drivers license). 7 Reserved for ISO use 8 E-commerce or mobile 9 Reserved for private use BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 141 Data element definitions Position 9 – Cardholder Authentication Entity Position 9 contains a code indicating the entity verifying the cardholder identity. Valid values are: Code Description 0 Not authenticated 1 ICC 2 CAD 3 Authorizing agent 4 By merchant 5 Other 6 Reserved for ISO use 7 Reserved for national use 8–9 Reserved for private use Position 10 – Card Data Output Capability Position 10 contains a code indicating the ability of the terminal to update the card. Valid values are: Code Description 0 Unknown 1 None 2 Magnetic stripe write 3 ICC 4–5 Reserved for ISO use 6–7 Reserved for National use 8–9 Reserved for Private use Position 11 – Terminal Output Capability Position 11 contains a code indicating the ability of the terminal to print or display messages. Valid values are: Code Description 0 Unknown 1 None 2 Printing 3 Display 4 Printing and display 5–6 Reserved for ISO use 7–8 Reserved for national use 9 Reserved for private use BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 142 Data element definitions Position 12 – PIN Capture Capability Position 12 contains a code indicating the length of PIN that the terminal is capable of capturing. Code Description 0 No PIN capture capability 1 Device PIN capture capability unknown 2 Reserved for ISO use 3 Three characters 4 Four characters 5 Five characters 6 Six characters 7 Seven characters 8 Eight characters 9 Nine characters A Ten characters B Eleven characters C Twelve characters D–I Reserved for ISO use J–R Reserved for national use S T–Z Verify Reserved for private use P-23: Card Sequence Number Format: N3 TDEs: Card Sequence Number (tde.crd_seq_num) Contains a card sequence number used to distinguish between separate cards with the same primary account number. Within BASE24-eps applications, the card sequence number is also referred to as the member number. The card sequence member number must be right-justified and zero filled or must contain three zeros. P-24: Function Code Format: N3 TDEs: Function Code (tde.fnct_cde) Contains the function code associated with the transaction—indicating the specific purpose of the message within its message class. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 143 Data element definitions Function codes supported by BASE24-eps Function codes are grouped based on the transaction messages with which they can be used. Each group is described below, along with values that BASE24-eps supports. Table Key: The Code column identifies the function codes used by BASE24-eps. The Description column describes the function code. The Define Name column lists the define name used for the code by BASE24-eps. 100-series function codes 100-series function codes are used in authorization (1100-series) messages. Code Description Define name 100 Original authorization – amount accurate fnct_auth_orig_amt_accurate 101 Original authorization – amount estimated fnct_auth_orig_amt_estimate 102 Replacement authorization – amount accurate fnct_auth_rplmt_amt_accurate 103 Replacement authorization – amount estimated fnct_auth_rplmt_amt_estimate 104 Resubmission – amount accurate fnct_auth_rsubm_amt_accurate 105 Resubmission – amount estimated fnct_auth_rsubm_amt_estimate 106 Supplementary authorization – amount accurate fnct_auth_sup_amt_accurate 107 Supplementary authorization – amount estimated fnct_auth_sup_amt_estimate 108 Inquiry fnct_auth_inq 172 Recurring Payment fnct_recur_pmnt 173 Partial/split shipment fnct_partial_shipment 174 Re-authorize for full amount fnct_reauth_full_amt 200-series function codes 200-series function codes are used in financial transaction (1200-series) messages. Code Description Define name 200 Original financial request/advice fnct_fncl_orig 201 Previously approved authorization – amount same fnct_fncl_auth_apprv_amt_ok 202 Previously approved authorization – amount differs fnct_fncl_auth_apprv_amt_eif 203 Resubmission of a previously denied financial request fnct_fncl_rsubm_deny 204 Resubmission of a previously reversed financial transaction fnct_fncl_rsubm_rvsl 205 First representment fnct_fncl_rprsmt_1 206 Second representment fnct_fncl_rprsmt_2 207 Third or subsequent representment fnct_fncl_rprsmt_3 300-series function codes 300-series function codes are used in file action (1300-series) messages. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 144 Data element definitions Code Description Define name 300 File unassigned fnct_file_unassign 301 Add record fnct_file_rec_add 302 Change record fnct_file_rec_chng 303 Delete record fnct_file_rec_del 304 Replace record fnct_file_rec_rplmt 305 Inquire fnct_file_inq 306 Replace file fnct_file_rplmt 307 Add file fnct_file_add 308 Delete file fnct_file_del 309 Card administration fnct_file_crd_admin 400-series function codes 400-series function codes are used in reversal and chargeback (1400-series) messages. Code Description Define name 400 Full reversal, transaction did not complete as approved fnct_rvsl_full 401 Partial reversal, transaction did not complete for full amount fnct_rvsl_part 450 First full chargeback fnct_chrgbck_full_1 451 Second full chargeback fnct_chrgbck_full_2 452 Third full chargeback fnct_chrgbck_full_3 453 First partial chargeback fnct_chrgbck_part_1 454 Second partial chargeback fnct_chrgbck_part_2 455 Third partial chargeback fnct_chrgbck_part_3 500-series function codes 500-series functions codes are used in reconciliation (1500-series) messages. Code Description Define name 500 Final reconciliation fnct_rcncl_final 501 Checkpoint reconciliation fnct_rcncl_chkpt 502 Final reconciliation in a specified currency fnct_rcncl_final_crncy 503 Checkpoint reconciliation in a specified currency fnct_rcncl_chkpt_crncy 504 Request for reconciliation totals fnct_rcncl_ttl_rqst 570 Batch close fnct_rcncl_btch_clos 571 Shift close fnct_rcncl_shift_clos 572 Daily close fnct_rcncl_dly_clos BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 145 Data element definitions Code Description Define name 573 Clerk totals fnct_rcncl_clerk_ttls 574 Batch subtotals fnct_rcncl_btch_subttls 575 Shift subtotals fnct_rcncl_shift_subttls 576 Daily subtotals fnct_rcncl_dly_subttls 585 Issuer stand-in totals unavailable fnct_rcncl_iss_standin_ttls_unavail 586 Acquirer stand-in totals unavailable fnct_rcncl_acq_standin_ttls_unavail 587 Acquirer settlement totals unavailable fnct_rcncl_acq_setl_ttls_unavail 588 Acquirer switch totals available fnct_rcncl_acq_switched_avail 589 Acquirer stand-in totals available fnct_rcncl_acq_standin_avail 590 Issuer switch totals available fnct_rcncl_iss_switched_avail 591 Issuer stand-in totals available fnct_rcncl_iss_standin_avail 592 Acquirer gross interchange value totals fnct_rcncl_acq_giv_avail 593 Acquirer gross interchange value totals unavailable fnct_rcncl_acq_giv_unavail 594 Issuer gross interchange value totals fnct_rcncl_iss_giv_avail 595 Issuer gross interchange value totals unavailable fnct_rcncl_iss_giv_unavail 596 Acquirer switch totals unavailable fnct_rcncl_acq_switched_unavail 597 Acquirer stand-in totals unavailable fnct_rcncl_acq_standin_unavail 598 Issuer switch totals unavailable fnct_rcncl_iss_switched_unavail 599 Issuer stand-in totals unavailable fnct_rcncl_iss_standin_unavail 600-series function codes 600-series functions codes are used in administrative (1600-series) messages. Code Description Define name 600 Original receipt, retrieval request fnct_admin_orig_rqst 601 Original receipt, repeat retrieval request fnct_admin_orig_rqst_repeat 602 Original receipt, fulfillment fnct_admin_orig_rqst_conf 603 Copy, retrieval request fnct_admin_cpy_rqst 604 Copy, repeat retrieval request fnct_admin_cpy_rqst_repeat 605 Copy, fulfillment fnct_admin_cpy_rqst_conf 650 Unable to parse message fnct_admin_parse_fail 651 MAC verification error fnct_admin_mac_vrfy_err 689 Logon fnct_admin_logon 690 Logoff fnct_admin_logoff 691 Load request fnct_admin_load BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 146 Data element definitions Code 692 Description Define name Handshake request fnct_admin_handshake 800-series function codes 800-series function codes are used in network management (1800-series) messages. Code Description Define name 801 System condition/sign-on fnct_nmm_sys_cond_signon 802 System condition/sign-off fnct_nmm_sys_cond_signoff 803 System condition/unavailable fnct_nmm_sys_cond_unavail 804 System condition/message originator's system in backup fnct_nmm_sys_cond_backup 805 System condition/special instruction fnct_nmm_sys_cond_instruct 806 System condition/initiate alternate routing fnct_nmm_sys_cond_alt_rte 809 System security/key request (inbound key) fnct_nmm_sys_sec_key_rqst_in 810 System security/key request (outbound key) fnct_nmm_sys_sec_key_rqst_out 811 System security/key change (both keys) fnct_nmm_sys_sec_key_chng 812 System security/security alert fnct_nmm_sys_sec_alert 813 System security/password change fnct_nmm_sys_sec_pswd_chng 814 System security/device authentication fnct_nmm_sys_sec_dev_auth 817 System security/key change (inbound key) fnct_nmm_sys_sec_key_chng_in 818 System security/key change (outbound key) fnct_nmm_sys_sec_key_chng_out 819 System condition/sign on acquirer-only processor fnct_nmm_sys_cond_signon_acq 820 System condition/sign on issuer-only processor fnct_nmm_sys_cond_signon_iss 821 System accounting/cutover (future) fnct_nmm_sys_acct_cutover 822 System accounting/checkpoint (future) fnct_nmm_sys_acct_chkpt 823 System condition/sign off acquirer-only processor fnct_nmm_sys_cond_signoff_acq 824 System condition/sign off issuer-only processor fnct_nmm_sys_cond_signoff_iss 825 Update acquirer key fnct_nmm_sys_sec_key_chng_acq 826 Update issuer key fnct_nmm_sys_sec_key_chng_iss 831 System audit control/echo test fnct_nmm_sys_aud_echo_test 832 Acquirer system audit control/echo test fnct_nmm_sys_aud_echo_test_acq 833 Issuer system audit control/echo test fnct_nmm_sys_aud_echo_test_iss 834 Message not accepted – bad format fnct_nmm_sys_cond_msg_err 880 Prefix sign-on fnct_nmm_sys_cond_signon_cmn 881 Sign-on fnct_nmm_sys_cond_signon_sngl BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 147 Data element definitions Code Description Define name 882 Prefix sign-off fnct_nmm_sys_cond_signoff_cmn 883 Sign-off fnct_nmm_sys_cond_signoff_sngl 884 Process next advice fnct_nmm_sys_pro_nxt_advc 885 SAF end-of-file fnct_nmm_sys_saf_eof 887 Sign-off from recovery fnct_nmm_sys_saf_stop_sngl Codes 887 and 889 should be used only for advice recovery. 888 Start SAF messages fnct_nmm_sys_saf_start_cmn 889 Sign-on to recovery. fnct_nmm_sys_saf_start_sngl Codes 887 and 889 should be used only for advice recovery. 890 Enter SI mode fnct_nmm_enter_si_mode 891 Exit SI mode fnct_nmm_exit_si_mode 892 Online request for current day’s settlement totals fnct_nmm_cur_recon 893 Online request for previous day’s settlement totals fnct_nmm_setl_recon 894 Start dual SAF mode fnct_nmm_sys_saf_start_dual 895 Key Repeat – inbound key fnct_nmm_sys_sec_key_repeat_in 896 Key Repeat – outbound key fnct_nmm_sys_sec_key_repeat_out 897 Key Verify – inbound key fnct_nmm_sys_sec_key_vrfy_in 898 Key Verify – outbound key fnct_nmm_sys_sec_key_vrfy_out 899 New Key Request – inbound and outbound keys fnct_nmm_sys_sec_key_rqst 900-series function codes 900-series function codes can be used in various messages. These function codes are for general use and typically defined when more specific function codes are not appropriate. Code Description Define name 940 Unsolicited message fnct_admin_unsol_msg 970 Multiple Account Select – More Account 1 data available fnct_prvt_more_acct1 971 Multiple Account Select – More Account 2 data available fnct_prvt_more_acct2 972 Multiple Account Select – No more account data available fnct_prvt_more_none 973 Customer List – More data available fnct_prvt_more_cust 974 Key Repeat – inbound and outbound keys fnct_nmm_sys_sec_key_repeat 975 Key Verify – inbound and outbound keys fnct_nmm_sys_sec_key_vrfy BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 148 Data element definitions Code Description Define name 985 Non-VSS Funds Transfer Totals fnct_admin_non_vss_xfer_tot 986 VCRSF non-fulfillment fnct_admin_vcrsf_non_fulfillment 987 VCRSF issuer dispute fnct_admin_vcrsf_dispute_iss 988 VCRSF acquirer dispute fnct_admin_vcrsf_dispute_acq 989 Text message fnct_admin_text_msg 990 VIFD alert fnct_admin_chris_alrt 991 CVV Generate request fnct_admin_cvv_gen_rqst 992 CVV2 generate request fnct_admin_cvv2_gen_rqst 993 VSS Funds Transfer Totals fnct_admin_vss_xfer_tot 994 Acquirer-generated fraud advice fnct_admin_fm_acq_fraud_advc 995 Issuer-generated fraud advice fnct_admin_fm_iss_fraud_advc 996 Fraud advices destined for acquirers fnct_admin_to_acq_fraud_advc 997 Fraud advices destined for issuers fnct_admin_to_iss_fraud_advc 998 VCRSF dispute fnct_admin_vcrsf_dispute 999 Issuer authentication failure or issuer script results advice fnct_admin_script_auth_fail P-25: Message Reason Code Format: N4 TDEs: Message Reason Code (tde.msg_rsn_cde) Contains the message reason code—providing the receiver of a request, advice, or notification message with the reason, or purpose, of that message. For original authorization, financial, and file action transactions, the message reason code identifies why the type of message was sent (e.g., why an advice was sent instead of a request); for other messages, this code indicates why this action was taken. Message reason codes supported by BASE24-eps BASE24-eps supports the message reason codes listed in the following table. Table key: The Code column identifies the message reason code. The Description column describes what the message reason code means. The "Define Name" column lists the define name used within BASE24-eps to denote the message reason code. Code Description Define Name 1000 Advice – stand in for issuer mrc_advc_stand_in_iss 1001 Advice – issuer signed off mrc_advc_iss_signoff 1002 Advice – issuer timeout original request mrc_advc_iss_timeout_rqst 1003 Advice – issuer unavailable mrc_advc_iss_unavail BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 149 Data element definitions Code Description Define Name 1004 Advice – terminal processed mrc_advc_term_proc 1005 Advice – ICC processed mrc_advc_icc_proc 1006 Advice – under floor limit mrc_advc_under_flr_lmt 1007 Advice – stand-in acquirer mrc_advc_stand_in_acq 1008 Advice - Exception item mrc_advc_excep_item 1376 Advice - Token create mrc_advc_tkn_create 1377 Advice - Token deactivate mrc_advc_tkn_deactv 1378 Advice - Token suspend mrc_advc_tkn_susp 1379 Advice - Token resume mrc_advc_tkn_resume 1380 Advice - Device provisioning result mrc_advc_dev_prvsn_rslt 1381 Advice - One Time Password verification result mrc_advc_pswd_vrfy_rslt 1382 Advice - Mobile banking app activation mrc_advc_mob_bnk_app_actv 1383 Advice - Replenishment confirmation of limiteduse keys mrc_advc_luk_replenish 1384 Advice - Token expiry update mrc_advc_tkn_expr_updt 1385 Advice - Chip data suspect mrc_advc_icc_suspect 1500 Request – ICC application, common file error mrc_rqst_icc_cmn_file_err 1501 Request – ICC application file error mrc_rqst_icc_appl_file_err 1502 Request – ICC random selection mrc_rqst_icc_random_selct 1503 Request – terminal random selection mrc_rqst_term_random_selct 1504 Request – terminal error ICC mrc_rqst_term_err_icc 1505 Request – online forced by ICC mrc_rqst_onl_icc 1506 Request – online card acceptor mrc_rqst_onl_crd_accpt 1507 Request – online forced by CAD to be updated mrc_rqst_onl_cad_updt 1508 Request – online forced by terminal mrc_rqst_onl_term 1509 Request – online forced by card issuer mrc_rqst_onl_iss 1510 Request – over floor limit mrc_rqst_over_flr_lmt 1511 Request – merchant suspicious mrc_rqst_mrch_suspect 1512 Request - refund mrc_rqst_rfnd_aft 1776 Request - deferred authorization mrc_rqst_deferred_auth 2000 Representment – general invalid chargeback mrc_rprsnt_general_invld_chrg 2001 Representment – invalid acquirer reference number mrc_rprsnt_invld_acq_ref_num 2002 Representment – no documentation for chargeback mrc_rprsnt_no_doc_for_chrgbk BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 150 Data element definitions Code Description Define Name 2003 Representment – correct transaction date provided mrc_rprsnt_txn_dat_provid 2004 Representment – correct merchant description mrc_rprsnt_mrch_descr_provid 2005 Representment – correct merchant location mrc_rprsnt_mrch_loc_provid 2006 Representment – incorrect tran date on chargeback mrc_rprsnt_txn_dat_incor_chrg 2007 Representment – tran less than merchant floor mrc_rprsnt_txn_less_mrch_floor 2008 Representment – tran authorized by issuer mrc_rprsnt_txn_auth_by_iss 2009 Representment – no error, amount correct mrc_rprsnt_no_err_amt_correct 2010 Representment – no altered amount mrc_rprsnt_no_alter_amt 2011 Representment – credit previously issued mrc_rprsnt_crdit_prev_issued 2012 Representment – original tran was valid mrc_rprsnt_orig_txn_valid 3000 File action – lost card mrc_file_crd_lost 3001 File action – stolen card mrc_file_crd_stolen 3002 File action – undelivered card mrc_file_crd_undeliver 3003 File action – counterfeit card mrc_file_crd_cntrft 4000 Reversal – customer cancellation mrc_rvsl_cust_cancel 4001 Reversal – unspecified, no action taken mrc_rvsl_unspecified_no_act 4002 Reversal – suspected malfunction mrc_rvsl_mlfnct_suspect 4003 Reversal - format error, no action taken mrc_rvsl_frmt_err_no_act 4004 Reversal – completed partially mrc_rvsl_compl_part 4005 Reversal – original amount incorrect mrc_rvsl_orig_amt_bad 4006 Reversal – response received too late mrc_rvsl_resp_late 4007 Reversal – card acceptor device error mrc_rvsl_crd_accpt_dev_err 4008 Reversal – deposit out of balance mrc_rvsl_dep_out_of_bal 4009 Reversal – no check in envelope mrc_rvsl_no_chq 4010 Reversal – payment out of balance mrc_rvsl_pmnt_out_of_bal 4011 Reversal – deposit out of balance, applied mrc_rvsl_dep_out_bal_appl 4012 Reversal – payment out of balance, applied mrc_rvsl_pmnt_out_bal_appl 4013 Reversal – unable to deliver message to point of service mrc_rvsl_deliver_fail_pt_svc 4014 Reversal – suspected malfunction/card retained mrc_rvsl_mlfnct_suspect_keep 4015 Reversal – suspected malfunction/card returned mrc_rvsl_mlfnct_suspect_rtrn 4016 Reversal – suspected malfunction/track 3 not updated mrc_rvsl_mlfnct_suspect_trk3 BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 151 Data element definitions Code Description Define Name 4017 Reversal – suspected malfunction/no cash dispensed mrc_rvsl_mlfnct_suspect_no_cash 4018 Reversal – timeout at taking money/no cash dispensed mrc_rvsl_timeout 4019 Reversal – timeout at taking card/no cash dispensed mrc_rvsl_timeout_keep 4020 Reversal – invalid response, no action taken mrc_rvsl_resp_invld_no_act 4021 Reversal – timeout waiting for response mrc_rvsl_timeout_resp 4351 Reversal – suspicious reversal mrc_rvsl_mlfnct_suspect_cash 4352 Reversal – suspicious reversal – amount known mrc_term_excpt_amt_known 4353 Reversal – suspicious reversal – amount unknown mrc_term_excpt_amt_unknown 4354 Reversal – suspicious reversal – amount known mrc_cons_excpt_amt_known 4355 Reversal – suspicious reversal – amount unknown mrc_cons_excpt_amt_unknown 4356 MAC failure mrc_mac_failure 4357 MAC Key Sync Error mrc_mac_key_sync_err 4358 Invalid MAC value mrc_invld_mac_val 4359 Data Encryption error mrc_data_encrpt_err 4360 Data encryption key sync error mrc_data_encrpt_key_sync_err 4361 Data encryption/decryption failed mrc_invld_data_encrpt_val 4362 Reversal – cash retained mrc_cash_ret_aft_cons_access 4363 Reversal – system malfunction mrc_rvsl_sys_mlfnct 4364 Customer cancelled transaction (e.g., cancelled an interactive message flow such as surcharging) mrc_cust_cancel 4365 Hardware Security Module (HSM) error mrc_sec_dev_fail 4366 PIN key sync error mrc_pin_key_sync_err 4367 PIN length error mrc_pin_lgth_err 4368 Reversal – duplicate transaction mrc_rvsl_dup_txn 4369 Reversal – reconciliation error mrc_rvsl_rcncl_err 4370 Invalid merchant mrc_advc_invld_mrch 4371 Invalid PIN index mrc_pin_invld_idx 4372 Reversal - suspected fraud mrc_rvsl_suspect_fraud 4506 Reversal – chargeback mrc_rvsl_netwk_advc_chrgbck 4500 Chargeback – invalid merchant mrc_chrgbck_invld_mrch BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 152 Data element definitions Code Description Define Name 4501 Chargeback – invalid transaction mrc_chrgbck_invld_txn 4502 Chargeback – customer dispute mrc_chrgbck_cust_dspt 4503 Chargeback – expired card mrc_chrgbck_exprd_crd 4504 Chargeback – transaction not permitted to terminal mrc_chrgbck_txn_not_prmit_to_term 4505 Chargeback – security violation mrc_chrgbck_sec_violation 4506 Chargeback – system malfunction mrc_chrgbck_sys_malfnct 4507 Chargeback – disputed transaction amount mrc_chrgbck_dspt_txm_amt 4508 Chargeback – authorized amount exceeded mrc_chrgbck_auth_amt_excd 4509 Chargeback – authorized time limit exceeded mrc_chrgbck_auth_tim_lim_excd 4510 Chargeback – credit submitted as a debit mrc_chrgbck_cr_sbmt_as_db 4511 Chargeback – debit submitted as a credit mrc_chrgbck_db_sbmt_as_cr 4512 Chargeback – duplicate processing of a transaction mrc_chrgbck_dup_pro_txn 4513 Chargeback – credit not received mrc_chrgbck_cr_not_rcv 4514 Chargeback – fraudulent transaction mrc_chrgbck_fraud_txn 4515 Chargeback – cardholder denies transaction was mrc_chrgbck_crdhldr_dny_txn_final finalized 4516 Chargeback – non-fulfillment of request for information mrc_chrgbck_nonfulfil_rqst_for_info 4517 Chargeback – non-fulfillment of request, illegible copy mrc_chrgbck_nonfulfil_illeg_cpy 4518 Chargeback – cardholder does not recognize merchant description mrc_chrgbck_crdhldr_invld_merch_des 4519 Chargeback – stand-in processing not allowed mrc_chrgbck_stand_in_pro_not_alwd 4520 Chargeback – stand-in processing criteria not fulfilled mrc_chrgbck_stand_in_pro_not_fulfil 4521 Chargeback – transaction exceeds floor limit mrc_chrgbck_txn_excd_flr_lmt 4522 Chargeback – declined authorization mrc_chrgbck_dcln_txn 4523 Chargeback – non-matching account number mrc_chrgbck_non_mtch_acct_num 4524 Chargeback – error in addition mrc_chrgbck_err_in_add 4525 Chargeback – altered amount mrc_chrgbck_altr_amt 4526 Chargeback – missing signature mrc_chrgbck_missing_sig 4527 Chargeback – missing card imprint mrc_chrgbck_missing_crd_imprnt 4528 Chargeback – cancelled preauthorized transaction mrc_chrgbck_cncld_preauth_txn 4529 Chargeback – delinquent reconciliation mrc_chrgbck_delinq_recon BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 153 Data element definitions Code Description Define Name 4530 Chargeback – currency conversion errors mrc_chrgbck_crncy_conv_err 4531 Chargeback – claim or defense on receipt of goods mrc_chrgbck_clm_on_rspt_gds 4532 Chargeback – defective merchandise mrc_chrgbck_dfct_mrchndse 4533 Chargeback – fraudulent transaction prior to embossed valid date mrc_chrgbck_fraud_txn_prior_dat 4534 Chargeback – imprint of multiple slips mrc_chrgbck_imprnt_mult_slps 4535 Chargeback – warning bulletin/exception file mrc_chrgbck_warn_bulltn 4536 Chargeback – late presentment mrc_chrgbck_late_prsnt 4537 Chargeback – no show disputed mrc_chrgbck_no_show_dsptd 4538 Chargeback – advance lodging deposit mrc_chrgbck_adv_lodg_dep 4539 Chargeback – cardholer disputes transaction date mrc_chrgbck_crdhldr_dspt_txn_dat 4540 Chargeback – card not yet effective mrc_chrgbck_crd_not_eff 4541 Chargeback – illegible data mrc_chrgbck_illeg_data 4542 Chargeback – transaction not received mrc_chrgbck_txn_not_recv 4543 Chargeback – duplicate processing by multiple institutions mrc_chrgbck_dup_pro_mult_inst 4544 Chargeback – cancelling recurring transaction mrc_chrgbck_cncl_recur_txn 4545 Chargeback – currency conversion not allowed mrc_chrgbck_crncy_conv_not_alwd 4546 Chargeback – mail/telephone order transaction unauthorized purchaser mrc_chrgbck_phn_ord_txn_unauth_pur 4547 Chargeback – card listed on warning bulletin mrc_chrgbck_crd_on_warn_bulltn 4548 Chargeback – cardholder dispute - transaction under merchant floor limit mrc_chrgbck_crdhldr_dspt_txn_flr_lmt 4549 Chargeback – incorrect account number mrc_chrgbck_incorr_acct_num 4550 Chargeback – cardholder disputes card activated telephone transaction mrc_chrgbck_crdhldr_dspt_phn_txn 4551 Chargeback – original transaction currency not provided mrc_chrgbck_orig_txn_crncy_not_prsn 4552 Chargeback – mail/telephone order on expired card mrc_chrgbck_phn_ord_exp_crd 4553 Chargeback – transaction not as described mrc_chrgbck_txn_not_as_dscrb 4554 Chargeback – non-receipt of merchandise mrc_chrgbck_non_rcpt_mrchndse 4555 Chargeback – services not rendered mrc_chrgbck_svrc_not_rndrd 4556 Chargeback – merchandise not as described mrc_chrgbck_mrchndse_not_as_dscrb 6001 Retrieval request – cardholder request or dispute mrc_admin_crdhldr_rqst_or_dspt BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 154 Data element definitions Code Description Define Name 6499 Fulfillment notification mrc_admin_fulfillment 9600 Check book order mrc_prvt_cheque_book_order 9601 Statement order mrc_prvt_stmt_order 9602 Response format error mrc_prvt_resp_frmt_err 9603 Migration log only mrc_prvt_migr_log_only 9604 Migration re-route mrc_prvt_migr_re_rte P-26: Card Acceptor Business Code Format: N4 TDEs: Card Acceptor Business Code (tde.crd_accpt_bus_cde) Contains a code classifying the type of business being done by the card acceptor for this transaction. Refer to section A.4 of the ISO 8583 (second edition 1993-12-15) Financial Transaction Card Originated Messages - Interchange Message Specifications for supported values. P-27: Approval Code Length Format: N1 TDEs: Approval Code (tde.apprv_cde) Contains the maximum length of the approval code that the acquirer can accommodate. The card issuer or agent must limit the approval code to the length specified in this data element. Approval codes that exceed the maximum length are truncated from the left (only the right-most digits are retained). P-28: Date, Reconciliation Format: N 6 (YYMMDD) TDEs: Reconciliation Date (tde.recon_dat) Contains the year, month, and day for which financial totals are reconciled between the acquirer and the card issuer. P-29: Reconciliation Indicator Format: N3 TDEs: Not applicable BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 155 Data element definitions Contains a value used to allow reconciliation of time periods within a reconciliation date, the value being subject to bilateral agreement. This data element is currently reserved for future use. P-30: Amounts, Original Format: N 24 TDEs: Original Transaction Amount (tde.amt_orig, tde.amt_orig_set) Contains the amount data elements from the original transaction. The amount must be expressed in the currency of the associated currency code data element. Where a minor unit of currency applies, amounts must be expressed in the minor unit of currency, without a decimal separator. For example, an amount value of 100 in US currency signifies one US dollar, but 100 in Italian currency signifies 100 lire. The Amounts, Original data element must consist of two data elements in fixed-length format totaling 24 digits. • • Original Amount, Transaction (N 12) Original Amount, Reconciliation (N 12) Absence of data is indicated by zeros. These data elements must contain the original amounts when attempting to partially reverse or partially charge back a previous transaction or when performing a partial approval. They should also be provided when performing replacement or supplementary authorizations. These amounts are for information only and cannot be used in the calculation of reconciliation totals. The new transaction amounts must be provided in their appropriate data elements. If the partial reversal is on a transaction that has a value added tax (VAT) combined with the original amount and the surcharge, then the VAT TDE and VAT Data TDE will be used to determine whether the VAT amount should be removed from the original amount. P-32: Acquirer Institution ID Code Format: LLVAR N ..11 TDEs: Acquirer (tde.acq_id_cde) Contains a code that identifies the acquiring institution for the transaction, or its agent. The acquiring institution may be different from the card acceptor. When a transaction originates at a terminal connected to the BASE24-eps system, the BASE24-eps application sets the acquiring institution identification code value in the Acquirer TDE from its terminal data source records. In the United States, this value is normally used for a U.S. Federal Reserve routing number that uniquely identifies financial institutions within the country. P-33: Forwarding Institution ID Code Format: LLVAR N ..11 TDEs: Forwarding Institution Acquirer (tde.frwd_inst_acq_id_cde) or Forwarding Institution Issuer (tde.frwd_inst_iss_id_cde) BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 156 Data element definitions Contains a code that identifies the forwarding institution (or service provider). For file updates to the American Express Global Network Solutions (AEGN) Network Exception File, this data element contains the five-byte organization identifier assigned during participant setup, right-justified and zerofilled to 11 bytes. P-34: Primary Account Number, Extended Format: LLVAR NS ..28 TDEs: PAN (tde.pan) Contains a number that identifies the customer account or relationship involved in the transaction or update request being processed. This data element is used only when the primary account number begins with 59 and contains a field separator or is greater than 19 digits in length. P-35: Track 2 Data Format: LLVAR Z ..37 TDEs: Track 2 (tde.trk2, tde.is_trk2_expired, tde.is_trk2_lgth_valid, tde.trk2_crd_seq_num_lgth, tde.trk2_crd_seq_num_ofst, tde.trk2_cvd_ofst, tde.trk2_exp_dat_ofst, tde.trk2_max_lgth, tde.trk2_min_lgth, tde.trk2_pin_algo_ofst, tde.trk2_pvv_ofst) Contains the information encoded on Track 2 of the magnetic stripe on the back of the card originating the transaction, excluding start and end sentinel and longitudinal redundancy check (LRC) characters. The content of Track 2 data is specified in the ISO 7813 standard, Identification Cards—Financial Transaction Cards. The general format of information in this data element includes the following: Primary account number (PAN), left justified (up to 19 digits) Field separator (“=” or “D”) Expiration date (YYMM) Service code (if present; 3 digits) Discretionary data (balance of available space, includes the PIN offset, PIN Verification Number (PVN), or the PIN Verification Key Indicator (PVKI) and PIN Verification Value (PVV), and card verification value). Information from this data element that may be required by BASE24-eps includes the PAN, card sequence (member) number, PIN verification data, expiration date, CVD, and service code. P-36: Track 3 Data Format: LLLVAR Z ..104 TDEs: Track 3 (tde.trk3, tde.is_trk3_expired, tde.is_trk3_lgth_valid, tde.trk3_crd_seq_num_lgth, tde.trk3_crd_seq_num_ofst, tde.trk3_cvd_ofst, tde.trk3_exp_dat_ofst , tde.trk3_max_lgth, tde.trk3_min_lgth, tde.trk3_pin_algo_ofst, tde.trk3_pvv_ofst, tde.trk3_svc_cde_ofst) BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 157 Data element definitions The Track 3 Data element contains the information encoded on track 3 of the magnetic stripe as defined in ISO 4909, including field separators, but excluding beginning and ending sentinels and longitudinal redundancy check characters as defined therein. For specifications on the standard ISO requirements for Track 3 data, refer to the ISO 4909 standard, Magnetic Stripe Data Content for Track 3. P-37: Retrieval Reference Number Format: ANP 12 TDEs: Sequence Number (tde.seq_num) Contains a number assigned by the message initiator to uniquely identify a transaction. This number remains unchanged for all messages throughout the life of a transaction. P-38: Approval Code Format: ANP 6 TDEs: Approval Code (tde.apprv_cde) Contains a code assigned by the authorizing institution indicating approval. The Issuer Authorization component places a character of B in the leftmost significant character of the approval code (based on the length of the approval code being generated) if the transaction was authorized on the BASE24-eps system. The BASE24-eps system calculates the approval code as follows: 1. 2. 3. Retrieves the transaction time and extracts the hhmmss as a binary field. Adds the amount of the transaction to the binary field. Adds each digit of the PAN to the binary field. The result of this calculation is the generated approval code. If the host needs to recreate and verify the approval code, the same calculation should be used. If the approval code is all zeroes, a value of 1 is used as the approval code so zeroes will never be generated. The transaction date and time for the transaction can be obtained from the transaction statistics and should be within a second so a recreated approval code value may be off 1 from the approval code originally generated. The approval code is truncated from the left to the approval code length requested by the acquirer in the Approval Code Length (P-27) data element. Thus, an approval code generated by the BASE24-eps system will be in the format of Bxxxxx where xxxxx are the right-most digits based on the approval code length minus 1 from the generated computation for the letter “B”. P-39: Action Code Format: N3 TDEs: Action Code (tde.act_cde , tde.act_cde_set) Action codes in this data element are mapped to and from the Action Code TDE as configured for the action code profile defined for the BASE24-eps ISO 93 Host Interface component on the Action Code Profile Configuration window of the ACI desktop user interface. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 158 Data element definitions Contains the action code associated with the transaction—defining the action taken or to be taken as well as the reason for taking this action. The numbering scheme for action codes is based upon the type of action and has no direct correlation to the message type identifier. Action codes are grouped as follows: Range Description 000–099 Authorization/financial transaction approved 100–199 Authorization/financial transaction denied 200–299 Authorization/financial transaction denied, pick up card 300–399 File actions 400–499 Reversal or chargeback actions 500–599 Reconciliation actions 600–699 Administrative actions 700–799 Fee collection actions 800–899 Network management actions 900–999 Error/response actions. Refer to section A.1 of the ISO 8583 (second edition 1993-12-15) Financial Transaction Card Originated Messages - Interchange Message Specifications for all of the ISO values. Note: For reversal requests transactions, the BASE24-eps ISO 93 Host Interface component always responds to the host with an action code of 400 (Reversal Accepted), regardless of the BASE24-eps processing result. This value indicates to the host that the reversal was successfully received. The component also sets the Action Code TDE to a value of 400 (Reversal Accepted). If an error occurs while processing the reversal, the error details are recorded in the Message Substate TDE. The following values are currently supported by BASE24‑eps: Code Description 000 Approved 001 Honor with identification 002 Approved for partial amount 003 Approved (VIP) 004 Approved, update Track 3 005 Approved, account type specified by card issuer 006 Approved for partial amount, account type specified by card issuer 007 Approved, update ICC 070–079 Reserved range for customer-specific approval codes 080 Approved, backup 081 Approved, overdraft 082 Approved, surcharge 083 Approved, OAR BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 159 Data element definitions Code Description 084 Approved, no EMV script 092 Conditional approval, private 100 Denied, do not honor 101 Denied, expired card 102 Denied, suspected fraud 103 Denied, card acceptor contact acquirer 104 Denied, restricted card 105 Denied, card acceptor call acquirer’s security department 106 Denied, allowable PIN tries exceeded 107 Denied, refer to card issuer 108 Denied, refer to card issuer’s special conditions 109 Denied, invalid merchant 110 Denied, invalid amount 111 Denied, invalid card number 112 Denied, PIN data required 113 Denied, unacceptable fee 114 Denied, no account of type requested 115 Denied, requested function not supported 116 Denied not sufficient funds 117 Denied, incorrect PIN 118 Denied, no card record 119 Denied, transaction not permitted to cardholder 120 Denied, transaction not permitted to terminal 121 Denied, exceeds withdrawal amount limit 122 Denied, security violation 123 Denied, exceeds withdrawal frequency limit 124 Denied, violation of law 125 Denied, card not effective 126 Denied, invalid PIN block 127 Denied, PIN length error 128 Denied, PIN key synchronization error 129 Denied, suspected counterfeit card 131 Denied, Domain Restriction 168 ARQC failed, decline, return card BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 160 Data element definitions Code Description 169 ARQC failed, refer 170 CVR failed, decline, return card 171 CVR failed, refer 172 TVR failed, decline, return card 173 TVR failed, refer 174 ATC failed, decline, return card 175 ATC failed, refer 176 Denied, fallback check 177 Referred, fallback check 180 Denied, amount not found 181 Denied, PIN change required 182 Denied, new PIN invalid 183 Denied, issuer/bank not found 184 Denied, issuer/bank not effective 185 Denied, customer/vendor not found 186 Denied, customer/vendor not effective 187 Denied, customer/vendor account invalid 188 Denied, vendor not found 189 Denied, vendor not effective 190 Denied, vendor data invalid 191 Denied, payment data invalid 192 Denied, personal information not found 193 Denied, scheduled transaction already exists 194 Denied, user not allowed to perform the requested function 195 Denied, print mini-statement instead 196 Denied, no statement data available 200 Retain card, do not honor 201 Retain card, expired card 202 Retain card, suspected fraud 203 Retain card, card acceptor contact acquirer 204 Retain card, restricted card 205 Retain card, card acceptor call acquirer’s security department 206 Retain card, allowable PIN tries exceeded 207 Retain card, special conditions BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 161 Data element definitions Code Description 208 Retain card, lost card 209 Retain card, stolen card 210 Retain card, suspected counterfeit card 280 ARQC failed, decline, retain card 281 CVR failed, decline, retain card 282 TVR failed, decline, retain card 283 ATC failed, decline, retain card 284 Fallback check, decline, retain card 300 Successful 301 Not supported by receiver 302 Unable to locate record on file 303 Duplicate record, old record replaced 304 Field edit error 305 File locked out 306 Not successful 307 Format error 308 Duplicate, new record rejected 309 Unknown file 400 Reversal accepted 481 Reversal, original transaction not found 484 Reversal, original transaction not approved 500 Reconciled, in balance 501 Reconciled, out of balance 502 Amount not reconciled, totals provided 503 Totals not available 504 Not reconciled, totals provided 600 Accepted 601 Not able to trace back original transaction 602 Invalid reference number 603 Reference number/PAN incompatible 604 POS photograph is not available 605 Item supplied 606 Request cannot be fulfilled—required/requested documentation is not available 607 Out of window BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 162 Data element definitions Code Description 700 Accepted 751 Approved, exceeded limit 800 Accepted 900 Advice acknowledged, no financial liability accepted 901 Advice acknowledged, financial liability accepted 902 Invalid transaction 903 Re-enter transaction 904 Format error 905 Acquirer not supported by switch 906 Cutover in process 907 Card issuer or switch inoperative 908 Transaction destination cannot be found for routing 909 System malfunction 910 Card issuer signed off 911 Card issuer timed out 912 Card issuer unavailable 913 Duplicate transmission 914 Not able to trace back to original transaction 915 Reconciliation cutover or checkpoint error 916 MAC incorrect 917 MAC key synchronization error 918 No communication keys available for use 919 Encryption key synchronization error 920 Security software/hardware error, try again 921 Security software/hardware error, no action 922 Message number out of sequence 923 Request in progress 940 Database error 941 Currency code not supported 942 Amount format error 943 Customer/vendor format error 944 Data format error 945 Name format error 946 Account format error BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 163 Data element definitions Code Description 947 Recurring data error 948 Update not allowed 949 Invalid capture (posting) date 950 Violation of business arrangement 992 Vendor authorization failed 993 Vendor authorization rejected 994 Vendor customer ID invalid 995 Vendor customer account limit reached 996 Vendor system unavailable P-40: Service Code Format: N3 TDEs: Service Code (tde.svc_cde) Contains the service code associated with the transaction—identifying geographic/service availability (see ISO 7813). P-41: Card Acceptor Terminal Identification Format: ANS 16 TDEs: Terminal Identifier (tde.term_id) Contains a unique code identifying the terminal at the card acceptor location. Note: BASE24-eps applications use 16 bytes for terminal identification, instead of the 8 bytes specified by ISO 8583. When the transaction-originating terminal is directly connected to the BASE24-eps system, the code for this data element is taken from the channel ID configured for the terminal on the ACI desktop user interface. P-42: Card Acceptor Identification Code Format: ANS 15 TDEs: Card Acceptor Identification Code (tde.crd_accpt_id_cde, tde.alt_crd_accpt_id_cde) Contains a code used to identify the card acceptor in a transaction if the card acceptor is different from the acquiring institution. For adding or replacing a stop payment order, this data element identifies the merchant for which recurring or installment transactions originating from this merchant will be stopped if the merchant verification value is not present in the message. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 164 Data element definitions P-43: Card Acceptor Name/Location Format: LLVAR ANS ..99 TDEs: Card Acceptor Name/Location (tde.crd_accpt_loc_city, tde.crd_accpt_loc_cntry_cde, tde.crd_accpt_loc_nam, tde.crd_accpt_loc_postal_cde, tde.crd_accpt_loc_regn, tde.crd_accpt_loc_street) Contains the name and location of the card acceptor as known to the cardholder. The Card Acceptor Name/Location data element consists of six data elements totaling up to 99 characters. The first three data elements (Name, Street, and City) are of variable length, separated from the remaining data elements and from each other by a back slash (\). These data elements can contain up to 83 characters. The remaining three data elements (postal code, region, and country code) are in fixed format as shown below: • • • Postal code (ANS 10) Region (ANS 3) Country code (A 3) The last three positions must contain the three-character country code as defined in ISO 3166, Codes for the Representation of the Names of Countries and Their Subdivisions. If the Card Acceptor Name/Location TDE is not present for the transaction, as might be the case for transactions acquired through a gateway, the ISO 93 Host Interface component creates the P-43 data element with default values as follows: • • • Uses a "\" to represent the missing name, street, and city fields (the three fields are presented as \\\). Fills the postal code and region fields with spaces. Sets the country code field to the logical network country code. If the country code is for the U.S. or Canada, a left-justified two-character state or province code can be provided in the region field. State and province codes are shown in the following table. Code Description AB Alberta AK Alaska AL Alabama AR Arkansas AZ Arizona BC British Columbia CA California CO Colorado CT Connecticut DC District of Columbia DE Delaware FL Florida GA Georgia HI Hawaii BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 165 Data element definitions Code Description IA Iowa ID Idaho IL Illinois IN Indiana KS Kansas KY Kentucky LA Louisiana MA Massachusetts MB Manitoba MD Maryland ME Maine MI Michigan MN Minnesota MO Missouri MS Mississippi MT Montana NB New Brunswick NC North Carolina ND North Dakota NE Nebraska NH New Hampshire NJ New Jersey NL Newfoundland and Labrador NM New Mexico NS Nova Scotia NT Northwest Territories NU Nunavut NV Nevada NY New York OH Ohio OK Oklahoma ON Ontario OR Oregon PA Pennsylvania BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 166 Data element definitions Code Description PE Prince Edward Island PR Puerto Rico QC Quebec RI Rhode Island SC South Carolina SD South Dakota SK Saskatchewan TN Tennessee TX Texas UT Utah VA Virginia VI Virgin Island VT Vermont WA Washington WI Wisconsin WV West Virginia WY Wyoming YT Yukon 99 US Military Base / Embassies / Traveling Merchants P-44: Additional Response Data Format: LLVAR ANS ..99 TDEs: Additional Response Data Contains up to ten action codes associated with a file update message (13xx). The action codes correspond, in order, to the associated tagged items in the Data Record (S-72) data element. This data element must be space filled for any tagged items up to ten that were not sent in the request message in the Data Record (S-72) data element. Use of tags This data element carries a single tagged data item with a tag of 01 and a length of 30 characters. The structure of the tagged data item is as follows: the tag value, followed by a three-digit length, followed by the tag data (in this case, consisting of file update action codes). The tag data is space filled up to a length of 30 characters characters (or the field to a length of 35 characters). 01 + 030 + tag data. The following is an example of the P-44 data element, including the field length, assuming two tagged items were sent in the S-72 data element in the request message: BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 167 Data element definitions Note: In this example, there are 24 trailing spaces to pad the tag data out to 30 characters. 3501030300308 bbbbbbbbbbbbbbbbbbbbbbbb Key Value Description 35 The two-position data element length indicator. 01 The tag identifier. 030 The length of the tag 01 data. 300 The action code for the first tagged item in the S-72 data element. 308 The action code for the second tagged item in the S-72 data element. b Blanks padding the tag data to a length of 30 characters. P-45: Track 1 Data Format: LLVAR ANS ..76 TDEs: Track 1 (tde.trk1, tde.is_trk1_expired, tde.is_trk1_lgth_valid, tde.trk1_crd_seq_num_lgth, tde.trk1_crd_seq_num_ofst, tde.trk1_cvd_ofst, tde.trk1_exp_dat_ofst, tde.trk1_max_lgth, tde.trk1_min_lgth, tde.trk1_pin_algo_ofst, tde.trk1_pvv_ofst) The Track 1 Data element contains the information encoded on Track 1 of the magnetic stripe of the card being used for the transaction, including start and end sentinel and longitudinal redundancy check (LRC) characters. The content of this data element is specified in the ISO 7813 standard, Identification Cards—Financial Transaction Cards. The general format of information in this data element is shown below. • • • • • • • • • Start sentinel (%) Format code (B for credit cards is the only format code defined) Primary account number (PAN), left justified (up to 19 digits) Field separator (^) Name (up to 26 characters) Field separator (^) Expiration date (YYMM) Service code (if present; 3 digits) Discretionary data (up to 21 characters) End sentinel (?) Longitudinal redundancy check character P-46: Amounts, Fees Format: LLLVAR ANS ..204 TDEs: Transaction Fee (tde.txn_fee_amt, tde.txn_fee_crncy_cde, tde.txn_fee_conv_rate, tde.txn_fee_rcncl_amt, tde.txn_fee_rcncl_crncy_cde, tde.txn_fee_set) Contains the fees associated with this transaction. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 168 Data element definitions This data element contains completed fees for partial reversals. The amount is expressed as a whole number. Where a minor unit of currency applies, amounts are expressed in the minor unit of currency without a separator. For example, an amount value of 100 in US currency signifies one US dollar, but 100 in Italian currency signifies 100 lire. Other systems, such as the host system or the interchange, are responsible for correctly placing the separator. All amounts in reconciliation messages are in the currency of reconciliation. This functionality is reserved for future use. If the VAT issuer indicator in the VAT TDE is set to combine, the VAT amount will be combined with the surcharge amount and the fee type will be 00. If the VAT issuer indicator is set to separate, the VAT amount will be in a separate value from the surcharge amount with a fee type of 74. The Amounts, Fees data element consists of up to six sets of values for the following fees. The fee type code associated with each fee is provided in parentheses. • • • • • • • • • Transaction fee (surcharge) (00) Transaction processing fee (01) Currency conversion fee (15) International Service Assessment (ISA) fee (70) Cardholder billing fee (71) Issuer transaction fee (72) Overdraft fee (73) Value added tax (VAT) fee (74) Online billpay fee (75) Each set of values consists of six data elements in fixed length format totaling 34 characters as follows: • • • • • • Fee Type Code (N 2) Currency Code, Fee (N 3 or A 3) Amount, Fee (x + N 8, where x represents C for credit or D for debit) Conversion rate, fee (N 8) Amount, Reconciliation Fee (x + N 8, where x represents C for credit or D for debit) Currency Code, Reconciliation Fee (N 3) The valid fee type codes listed in ISO 8583 (second edition 1993-12-15) Financial Transaction Card Originated Messages - Interchange Message Specifications are as follows: Code Description 00 Transaction fee 01 Transaction processing fee 02 Fee collection fee 03 File action fees 04 Telex, telephone and cable charges 05 Auto-telex charges 06 Lost/stolen card report fees 07 Merchant service fees 08 Recovered card awards 09 Invalid chargeback handling fee 10 Recovery of copy/original fees BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 169 Data element definitions Code Description 11 Returned guaranteed check 12 Emergency cash disbursement handling fee 13 Arbitration cash disbursement handling fee 14 Incorrect merchant identification/transaction data handling fee 15 Currency conversion fee 16 Special handling fee 17 Investigation fees 18 Emergency card replacement fee 19 Warning bulletin handling fee 20 Good faith acceptance 21 Collection letters 22–39 Reserved for ISO use 40–69 Reserved for national use 70–99 Reserved for private use P-48: Additional Data – Private Data Element Format: LLLVAR ANS..999 TDEs: Varies by tag Used for a number of purposes, depending on the information carried. Use of tags This data element carries tagged data items. The tags defined for this data element are listed below. Tagged data items are structured in the following manner: a tag identifying the type of data, followed immediately by a three-digit length (LLL) identifying the length of the data, followed immediately by the data itself. The data type can be alphanumeric or special characters, but ACI recommends using alphanumeric characters. Tag + LLL + data. Tagged data varies in length depending on the tag, and multiple tagged data items can be included in any order within the data element. Use of subtags Some tags use subtags to identify the various data fields involved in the file action. Refer to the specific tag documentation for descriptions of the supported subtags and their purposes. Subtag data is structured as follows: the subtag identifying the type of field data, followed immediately by a threedigit length (LLL) identifying the length of the field data, followed immediately by the field data itself. Subtag + LLL + field data. Multiple subtags can be present within a single tag, and can be in any order within the tag. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 170 Data element definitions P-48: Tag 01, PayPass Mapping Information Format: Variable based on the subtags included TDEs: PayPass/Virtual Card Number For contactless magnetic stripe requests, this tag contains the PayPass account number and PayPass card/ device expiration date. For contactless magnetic stripe responses, this tag contains the primary account number (PAN) and expiration date that is mapped to the PayPass account number in the PayPass Mapping File (MCC106). The PayPass Mapping Service is an optional service provided by MasterCard (Banknet) that helps issuers process PayPass transactions by translating PayPass account numbers into primary account numbers that issuers can process with minimal impact. A PayPass account number is a unique number encoded on the proximity chip of a PayPass card or device that the PayPass Mapping Service associates with a PAN. For transactions initiated through MasterCard PayPass Online (PPOL), a PPOL value created and populated by the PayPass wallet must be passed by merchants and acquirers indicating how the wallet data was created. The structure of this tag is as follows: Tag 01: PayPass Mapping Information Subtag 01 Description Account Number Indicator. Format A1 Values: C = MasterCard Digital Enablement Service Secure Element Device Token E = Embossed Account Number Provided by Issuer F = MasterCard Digital Enablement Service Card on File Token H = MasterCard Digital Enablement Service CloudBased Payments Device Toke L = Pay with Rewards Loyalty Program Operator [LPO] Card M = Primary account number (PAN) P = Contactless Account Number R = Pay with Rewards Card V = Virtual Card Number 02 Account Number. The PayPass account number or the mapped PAN. 03 Expiration Date (in YYMM format) for the PayPass account number or the PAN. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 N 19 N4 171 Data element definitions Tag 01: PayPass Mapping Information Subtag Description Format 04 PayPass product code for the PayPass account number. AN 3 05 PPOL (MasterCard PayPass Online) program data. Values: AN 3 101 = PPOL remote. Wallet data was created by the cardholder manually key entering the data at a consumer controlled device (for example, computer, tablet, or phone). 102 = PPOL remote NFC payment. Wallet data was initially created by the cardholder tapping their PayPass card or device at a contactless card reader (for example, a PayPass card reader or an ultrabook enabled to read PayPass cards). 103 = Reserved for future use. Banknet: The data in this subtag maps to and from data element 48 subelement 26 (PPOL Program Data) in the Banknet transaction message. For information about the Banknet transaction message refer to the appropriate Banknet technical specifications. P-48: Tag 02, Account Detail Format: Variable based on the subtags included TDEs: Additional Data Returns account details for the account contained in Account 1. A single response is received and sent back to the acquirer. The structure of this tag is as follows: Tag 02: Account Detail Subtag Description 01 Account Number 02 Account Description Format AN 28 ANS 10 A brief description or nickname for the account. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 172 Data element definitions Tag 02: Account Detail Subtag Description Format 03 Account Type N2 04 Balance Date N 14 (yyyymmddhhmmss) 05 Account Locator 06 View Balance Flag A1 07 View Transaction Flag A1 08 Debit Flag A1 09 Credit Flag A1 10 Bill Flag A1 11 Available/Credit Balance N 12 12 Ledger Balance N 12 13 Credit Limit N 12 14 Overdraft Limit N 12 15 Next Payment Amount N 12 16 Next Payment Date 17 Overdue Payment N 12 18 Default Balance N 12 19 Alpha Currency Code 20 Original Amount ANS 28 N 8 (yyyymmdd) A3 N 12 The amount with which the account was opened. 21 Payoff Amount N 12 22 Maturity Date N 8 (yyyymmdd) 23 Interest Rate N6 24 Email address ANS 40 25 Message ANS 80 A message related to the account. 26 RDC Deposit Limit N 12 The maximum amount allowed for Remote Deposit Capture (RDC) deposits to this account. P-48: Tag 03, Multiple Account Inquiry Format: Variable based on the subtags included TDEs: Account List BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 173 Data element definitions This tag returns all accounts according to the specified account type; if no type is specified, all accounts are returned. The fields for this tag occur 1 to n times. The structure of this tag is defined in the following table. Tag 03: Multiple Account Inquiry Description Format Account Type AN 2 Account Number AN 28 Account Status AN 2 Primary Indicator A1 Two Sided Indicator A1 Description ANS 20 Currency Code A3 Ledger Balance N 12 Available Balance N 12 P-48: Tag 04, Billpay Inquiry Format: Variable based on the subtags included TDEs: Additional Data This field returns information about any applicable billpay service associated with the customer. Tag 04: Billpay Inquiry Subtag Description Format 01 Billpay Service ANS..12 02 Billpay ID ANS..28 P-48: Tag 05, e-Wallet Data Format: ANS Variable based on the subtags included TDEs: NYCE Data, Acquirer POS Entry Mode Acquirer POS Entry Mode ERSB National Data Wallet Information For NYCE mobile access transactions, this tag contains the network ID, which is always 03 (NYCE) and the eWallet ID, which identifies the type of e-Wallet used for the transaction. For French transactions, this tag contains the digital wallet name, e-Wallet indicator, additional e-Wallet data and e-Wallet identifier. The structure of this tag is as follows: BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 174 Data element definitions Tag 05: e-Wallet Data Subtag Description 01 Network ID. Values: Format ANS 2 03 = NYCE 02 e-Wallet ID. Values: ANS 2 84=NYCE Mobile Access merchant wallet 85=NYCE Mobile Access - FI wallet 03 Digital Wallet Name AN 2 CBAE field 59 tag 0415 04 Electronic Commerce Indicator AN 2 CBAE field 59 tag 0416 05 Additional Data e-Wallets AN 12..24 CBAE field 59 tag 0417 06 Identifier Wallet N6 CBAE field 59 tag 0418 07 Cryptogram Processing Information ANP 1 CBAE Field 59 tag 0409 08 Cryptogram Calculation Method AN 1 CBAE Field 59 tag 0411 09 e-Commerce Cryptogram AN 40..80 P-49: Currency Code, Transaction Format: A 3 or N 3 TDEs: Transaction Amount (tde.txn_amt_crncy_cde) Contains the currency of the amount carried in the Amount, Transaction (P-4) data element. This is the transaction currency used internally by BASE24-eps, which is the cardholder billing currency if the acquiring interchange has already performed currency conversion on behalf of the issuer. Refer to ISO 4217 for a list of all valid ISO currency codes. P-50: Currency Code, Reconciliation Format: A 3 or N 3 TDEs: Settlement Amount (tde.crncy_cde_stl) or BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 175 Data element definitions Issuer Settlement Amount (tde.crncy_cde_iss_setl) Contains the code defining the currency of reconciliation. This is the currency of the amount carried in the Amount, Reconciliation (P-5) data element. Refer to ISO 4217 for a list of all valid ISO currency codes. P-51: Currency Code, Cardholder Billing Format: A 3 or N 3 TDEs: Cardholder Billing (tde.chb_info_tag) Contains the currency code defining the currency of the amounts carried in the Amount, Cardholder Billing (P-6) and Amount, Cardholder Billing Fee (P-8). This is the issuer's currency configured in BASE24-eps. Refer to ISO 4217 for a list of all valid ISO currency codes. P-52: Personal Identification Number (PIN) Data Format: AN 16 TDEs: PIN Data (tde.pin_verified) Contains the Personal Identification Number (PIN) assigned to a customer intended to uniquely identify that customer at the point of service. This data element can contain the PIN itself or a derivative (i.e., the PIN block). See ISO 9564-1. If this data element contains 16 hexadecimal F characters in the clear, it signifies that the PIN has already been verified. P-54: Amounts, Additional Format LLLVAR ANS ..120 TDEs Cash Back (tde.amt_cb_set, tde.amt_cb, tde.amt_cb_crncy_cde) or Balance (tde.bal_acct_typ, tde.bal_amt, tde.bal_amt_by_acct_typ, tde.bal_crncy_cde, tde.bal_dat, tde.bal_set) or Generic Data (Outer key: TRAILING_TXN, Inner key: ORIG_TTL_AMT) Contains cash back, balance amounts, or the trailing transaction original total transaction amount for the transaction. For transactions with cash back, the cash back amount is carried in this data element as an amount type of 40 and is moved to and from the Cash Back TDE. For transactions carrying balances (for example, ledger and available balances), these balances are moved to and from the Balance TDE. Balances are typically carried in transaction responses where BASE24-eps maintains account balance information on the system and its authorization scripts are set up to return balances. The actual balances carried in data element P-54 depend on how you have set up balances to be handled by BASE24-eps and how you are using the Balance TDE. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 176 Data element definitions For trailing transactions, the original total transaction amount is carried in this data element as an amount type of 60 and is moved to and from the Generic Data TDE. Amount occurrences Each amount occurrences is 20 characters in length as described here. Data element P-54 can contain up to six separate amounts totaling a maximum of 120 characters. Position 1–2 Description Format Account type associated with the amount. N2 See data element P-3: Processing Code for a list of account types supported by BASE24-eps. 3–4 Amount type. N2 Amount types recognized by BASE24-eps are provided under "Amount Types" below. 5–7 Currency code. A3 The currency code for balances does not have to match the currency code specified in data element P-49: Currency Code, Transaction. 8–20 Amount x + N 12 Amounts must be expressed in the currency of the currency code associated with the amount. Where a minor unit of currency applies, amounts are expressed in the minor unit of currency, without a decimal separator. For example, an amount value of 100 in US currency signifies one US dollar, but 100 in Italian currency signifies 100 lire. where x represents C for credit or D for debit Amount types The Balance TDE accepts any two-digit numeric value. BASE24-eps has defined and reserved the amount types in the following table, although not all are currently used. Amount type Description Define name 01 Account 1 Ledger Balance bu_bal_typ_acct1_ledg_bal 02 Account 1 Available Balance bu_bal_typ_acct1_avail_bal 03 Amount Owing bu_bal_typ_amt_owing 04 Amount Due bu_bal_typ_amt_due 05 Available Credit bu_bal_typ_avail_cr 16 Account 2 Ledger Balance bu_bal_typ_acct2_ledg_bal 17 Account 2 Available Balance bu_bal_typ_acct2_avail_bal 18 Credit Limit bu_bal_typ_amt_cr_lmt 19 Available Credit Overdraft bu_bal_typ_avail_cr_ovrdft 36 Co-Payment bu_bal_typ_amt_co_pmnt 40 Cash bu_bal_typ_amt_cash 43 Accumulated Auth Amount bu_bal_typ_amt_accum_auth BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 177 Data element definitions Amount type Description Define name 44 Gratuity Amount bu_bal_typ_amt_gratuity 56 Max Approval Amount bu_bal_typ_amt_max_apprv 57 Original Amount bu_bal_typ_amt_orig 58 Transit Amount bu_bal_typ_amt_transit 59 Healthcare Amount bu_bal_typ_amt_healthcare 60 Trailing Transaction Original Total Transaction Amount Not applicable 90 Original Total Amount bu_bal_typ_amt_orig_ttl_amt 93 Mixed Media Deposit Cash Amount bu_bal_typ_amt_cash_dep 94 Check Deposit Amount bu_bal_typ_amt_check_dep 95 Point of Interaction (POI) Amount bu_bal_typ_amt_poi P-55: Integrated Circuit Card System Related Data Format LLLVAR ANS ..510 Transaction data elements (TDEs) EMV Discretionary Data EMV Generic Data EMV Request EMV Response EMV Script EMV Script Results EMV Status Contains EMV data. The EMV data in this data element is structured in the following tag-length-value format: <2-or-4-character tag><2-character length field><variable length data> • • The 2-byte or 4-byte tag is an EMV tag in hexadecimal format that uniquely identifies the data content of the P-55 fields. The 2-digit length field defines the length of the variable-length data that follows it. The length specifies the number of hexadecimal values represented in the data part, the actual string is twice as long as the length specifies. The format of the length field is binary converted to a hexadecimal string. For example, 0x1F is represented as “1F”. The variable-length data for a tag cannot exceed the maximum specified length specified for the data. When the variable length data is longer than the defined maximum length for the tag value, it is truncated. Because the ISO 93 Host Interface component does not support binary data, binary EMV data is sent as packed (hexadecimal) characters in the BASE24-eps ISO 8583:1993 host external message. EMV tags adhere to the tag definitions specified in the ISO 7816 Part 4: Interindustry Commands for Interchange specification and in the ISO/IEC 8825 standard, Information technology -- ASN.1 encoding rules: Mapping W3C XML schema definitions into ASN.1 specification. The following table describes the following information: • • each of the EMV tags that can be carried in the P-55 data element the maximum length for each tag value BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 178 Data element definitions • • the transaction data elements (TDEs) to which each tag is mapped flags indicating whether the tag data is required (Y), optional (N), or not applicable (N/A) for requests and responses When building the P-55 data element for requests, all tags that are present in the EMV Generic Data TDE and that are not specifically listed below are added to the field. When parsing the P-55 data element for requests, all tags that are present in the field and that are not specifically listed below are populated in the EMV Generic Data TDE. All non-listed tag values are assumed to represent EMV binary data. They are represented as hexadecimal characters in the message. Note: In this table, the maximum length of a tag value specified in the “Max Length” column is represented as H<n>. This representation indicates the type and maximum length of the tag value. • • “H” indicates that the tag value is hexadecimal represented in ASCII. <n> indicates the maximum length of the tag value. It can be from 00–256. For example, a Cryptogram Information Data (tag 9F27, maximum length of H1) tag value of 0x13 results in a string value of “9F270113” in the P-55 data element. EMV tag Description Max length TDE Required Request Response 4F Application ID H32 EMV Generic Data N N 50 Application Label H32 EMV Generic Data N N 71 Issuer Script H128 EMV Script N/A N 72 Issuer Script H128 EMV Script N/A N 82 Application Interchange Profile H2 EMV Request Y N/A 84 Dedicated File Name H16 EMV Discretionary Data N N/A 91 Issuer Authentication Data H32 EMV Response N/A N 95 Terminal Verification Results H5 EMV Request Y N/A 9A Transaction Date H3 EMV Request Y N/A 9C Transaction Type H1 EMV Request Y N/A 5F24 Application Expiration Date H3 EMV Generic Data N N 5F2A Transaction Currency Code H2 EMV Request Y N/A 5F34 Application PAN Sequence Number H1 EMV Status N N BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 179 Data element definitions EMV tag Description Max length TDE Required Request Response 9F02 Transaction Amount H6 EMV Request Y N/A 9F03 Amount, Other 1 H6 EMV Request N1 N/A 9F06 Application identifier, dedicated filename H32 EMV Discretionary Data N N/A 9F09 Application Version Number H2 EMV Discretionary Data N N/A 9F10 Issuer Application Discretionary Data H32 EMV Request Y N/A 9F12 Application Preferred Name H32 EMV Generic Data N N 9F1A Terminal Country Code H2 EMV Request Y N/A 9F1E Interface Device Serial Number AN 8 EMV Discretionary Data N N/A 9F26 Authorization Request Cryptogram H8 EMV Request Y N/A 9F27 Cryptogram Information Data H1 EMV Request Y N/A 9F33 Terminal Capabilities H3 EMV Discretionary Data N N/A 9F34 Cardholder Verification Method Results H3 EMV Discretionary Data N N/A 9F35 Terminal Type H1 EMV Request N N/A 9F36 Application Transaction Counter (ATC) H2 EMV Request N N/A 9F37 Unpredictable Number H4 EMV Request Y N/A 9F41 Transaction Sequence Counter H8 EMV Generic Data N N/A BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 180 Data element definitions EMV tag Description Max length TDE Required Request Response 9F53 Transaction Category Code H1 EMV Generic Data N N/A 9F5B Issuer Script Results H20 EMV Script Results N N/A 9F6E Third Party Data H32 EMV Generic Data N N/A 1 Amount, Other (Tag 9F03) is mandatory when there is a cash back amount. When there is no cash back amount, 9F03 can be absent or present with a zero value. The following tags may also be present for Cartes Bancaires Acquéreur-Emetteur (CBAE) messages: Table 1: CBAE-specific EMV tags EMV tag Description Max length TDE Required Request Response 56 Track 1 equivalent data read in contactless mode H76 EMV Generic Data N N/A 57 Track 2 equivalent data H19 EMV Generic Data N N/A 9F66 Terminal Transaction Qualifiers (TTQ) H4 EMV Generic Data N N/A 9F6B Track 2 equivalent data read in contactless mode H19 EMV Generic Data N N/A 9F7C Customer Exclusive Data (CED) H32 EMV Generic Data N N/A DF68 Kernel ID Used H1 (This is a repeatable tag in CBAE messages, but in the Generic EMV Data TDE, the P-55 data element may contain multiple H1 values concatenated under a single DF80 tag.) EMV Generic Data N N/A BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 181 Data element definitions EMV tag Description Max length TDE Required Request Response DF80 Results of integrated circuit processing H1 EMV Generic Data N N/A DF81 Card application type H1 EMV Generic Data N N/A DF85 Terminal Processing Results H5 EMV Generic Data N N/A DF86 Contactless Device H35 EMV Generic Data N N/A DFC0 EMV Acquisition Mode H1 EMV Generic Data N N/A P-56: Original Data Elements Format: LLVAR N ..35 TDEs: Original Data Contains data elements from the original message intended for transaction matching. These four data elements are in variable length format totaling a maximum of 35 numeric characters, including the length attribute of the original acquiring institution identification code: • • • • Original message type identifier (N 4) Original system trace audit number (N 6) Original date and time, local transaction (N 12) Original acquiring institution identification code (N ..11) Absence of data must be indicated by zeros. P-57: Authorization Life Cycle Code Format: N3 TDEs: Pre-Authorization (tde.pre_auth_exp_ts, tde.pre_auth_tim_cde, tde.pre_auth_tim_interval) Contains a value in calendar days, hours, or minutes which defines the time period for which the acquirer is requesting guarantee of funds, or that the card issuer will guarantee funds for a financial transaction which may follow. The first position of this data element indicates whether the authorization life cycle is in calendar days, hours, or minutes. Valid values are as follows: Code Description 0 Reserved for ISO use 1 Calendar days BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 182 Data element definitions Code Description 2 Hours 3 Minutes 4–5 Reserved for ISO use 6–7 Reserved for national use 8–9 Reserved for private use Positions 2 and 3 indicate the number of calendar days, hours, or minutes for the authorization life cycle. Valid values are 01–99. P-58: Authorizing Agent Institution ID Code Format: LLVAR N ..11 TDEs: Authorizing Agent Institution (tde.auth_agent_inst_id_cde) Contains a code identifying the authorizing agent institution. P-59: Transport Data Format: LLLVAR ANS ..999 TDEs: Transport Data Issuer Transport Data Transport data is used by processors to send and receive private business-related data in selected messages. When this data element is built, the data comes from the Transport Data TDE, which is transport data provided by the Acquirer. When this data element is received, the received data is stored depending on whether the interface is Issuer or Acquirer facing. If Acquirer facing (that is, receiving a request), it stores the data in the Transport Data TDE. If Issuer facing (that is, receiving a response) in the Issuer Transport Data TDE. VisaNet: The data in this tag maps to and from data element 104, usage 2, dataset 65 (MasterCard Member Defined data) in the VisaNet transaction message. For information about the VisaNet transaction message, refer to the appropriate VisaNet technical specifications. MDS: The data in this tag maps to and from data element 124 (Member Defined Data) in the MDS transaction message. For information about the MDS transaction message, refer to the appropriate MDS technical specifications. P-60: CSM Reserved Format: LLLVAR ANS ..999 TDEs: Based on the CSM The CSM Reserved data element is reserved for use in customer specific modifications (CSMs). BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 183 Data element definitions The structure and format of the data element is flexible and can be defined as needed by the customer (e.g., fixed length, variable length, with a tag/subtag structure, etc.). P-62: Primary Reserved Private Format: LLLVAR ANS ..999 TDEs: Varies by tag Used for a number of purposes, depending on the information carried. Required when Tags 77 (Customer 1 ID) and 78 (Customer 2 ID) are present in the original request. Use of tags This data element carries tagged data items. The tags defined for this data element are listed below. Tagged data items are structured in the following manner: a tag identifying the type of data, followed immediately by a three-digit length (LLL) identifying the length of the data, followed immediately by the data itself. The data type can be alphanumeric or special characters, but ACI recommends using alphanumeric characters. Tag + LLL + data. Tagged data varies in length depending on the tag, and multiple tagged data items can be included in any order within the data element. Use of subtags Some tags use subtags to identify the various data fields involved in the file action. Refer to the specific tag documentation for descriptions of the supported subtags and their purposes. Subtag data is structured as follows: the subtag identifying the type of field data, followed immediately by a threedigit length (LLL) identifying the length of the field data, followed immediately by the field data itself. Subtag + LLL + field data. Multiple subtags can be present within a single tag, and can be in any order within the tag. Note: Although subtags are generally optional, some subtags are required to read the Card or Positive_Balance data sources and are thus mandatory in the file action message. P-62: Tag 01, PIN Change – PIN Offset Format: AN 16 TDEs: PVV (tde.pvv) PVV Admin (tde.pvv_admin) Tag 01 contains the PIN offset (left-justified, blank-filled) that is calculated when a cardholder selects or changes a PIN. It allows the new PIN offset value to be transmitted to the host, in order to keep the database up-to-date. The PIN offset is 16 characters in length. If the PVV is padded with any pad characters (e.g., hexadecimal F characters), the pad characters are stripped out when building this tag. P-62: Tag 02, PIN Change – Encrypted PIN Format: AN 16 TDEs: PIN Change BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 184 Data element definitions Tag 02 contains the encrypted PIN that is generated when a cardholder selects or changes a PIN. It allows the new encrypted PIN to be transmitted to the host for the purpose of keeping the database up-to-date and generating a PIN offset. The encrypted PIN is 16 characters in length. P-62: Tag 03, Depository Type Format: AN 1 TDEs: Depository Type In requests, tag 03 contains the depository type, which indicates the types of depositories available. Valid values are as follows: Code Description 0 Normal Envelope 1 Commercial 2 Both envelope and commercial In responses, tag 03 indicates whether the depository should be opened. Valid values are as follows: Code Description 0 No, do not open the depository. 1 Yes, open the depository. In all other applicable messages, tag 03 indicates whether the depository is used. Valid values are as follows: Code Description 0 No, the depository is not used. 1 Yes, the depository is used. In all messages, tag 03 contains one character. P-62: Tag 04, Terminal Branch Format: AN 4 TDEs: Terminal Branch Tag 04 contains the branch ID for the branch in which the terminal is located. The terminal branch ID is four characters in length. P-62: Tag 05, Terminal Region Format: AN 4 TDEs: Terminal Region Tag 05 contains the region ID for the region in which the terminal is located. The terminal region ID is four characters in length. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 185 Data element definitions P-62: Tag 06, Multiple Account Select Indicator Format: N1 TDEs: Multiple Account Select Tag 06 contains a flag indicating whether multiple account selection is supported at the acquirer. Valid values are as follows: Code Description 0 No, multiple account selection is not supported at the acquirer. 1 Yes, standard multiple account selection is supported at the acquirer. 2 Yes, indexed multiple account selection is supported at the acquirer. P-62: Tag 07, Transaction Originator Format: N1 TDEs: Transaction Originator (tde.txn_orig) Tag 07 contains the transaction originator code, which identifies where the transaction originated in the BASE24‑eps system. Valid values are as follows: Code Description 0 Originating terminal 1 Originating terminal component 2 Originating interface 3 Originating interface component 4 Originating authorization component 5 Originating billpay server 6 Originating contingency interface P-62: Tag 08, Instrument Type Format: AN 2 TDEs: Instrument Type Tag 08 contains a two-character code identifying the type of instrument used for the transaction. The instrument type is obtained from the Prefix, Interchange Prefix, or System Prefix data sources. P-62: Tag 09, Visa Data Format: AN 202 TDEs: Visa SMS Data Tag 09 contains data for Visa and Visa SMS transactions. The structure of this data is as follows. Refer to Visa and Visa SMS reference documentation for detailed information about these fields. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 186 Data element definitions Position 1 Description Additional Data Indicator Length 1 A code assigned to a non-T&E commercial card transaction containing enhanced data (sales tax and/or customer-provided accounting code) in the original transaction. Valid values are as follows: 0 = No additional data received. 1 = Yes, additional data received. 2–8 Chargeback Reduction Base II Flags 7 Chargeback Reduction Base II flags used to reduce the number of chargebacks. Positions 1–7 of this field contain the following, respectively: floor limit indicator, CRB indicator, STIP indicator, Mail/ Phone/Electronic Commerce indicator, Special Chargeback indicator, Special Condition indicator, RIS, and Special Condition indicator, Merchant. 9–14 Decimal Positions Indicator 6 Specifies the number of decimal positions in transaction amounts fields, settlement amount fields, and cardholder amounts fields. Positions 1 and 2 specify the decimal positions in transaction amounts fields. Positions 3 and 4 specify the decimal positions in settlement amounts fields. Positions 5 and 6 specify the decimal positions in cardholder amounts fields. Valid values for each position set are as follows: 00 = Currency has no minor units. 02 = Currency has two minor units. 03 = Currency has three minor units. 99 = Currency not applicable in this message. 15–28 Fraud Data 14 Fraud Data information for reporting fraudulent activity to Visa’s Fraud Reporting System. Positions 1–3 of this field contain the following, respectively: fraud type, fraud notification type, and check fraud indicator. Positions 4–14 are reserved. 29–34 VIEW Station BIN address 6 The BIN station address of a View Image Exchange Workstation (VIEW) for a specific issuer or acquirer to which a chargeback or representment advice is directed. This address is used by the VisaNet Documentation Automation Service (VDAS). BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 187 Data element definitions Position 35–70 Description Issuer Currency Conversion Data Length 36 This field is part of the optional Currency Conversion Fee Service, which is available for Visa multicurrency participants. This field contains the fees associated with a transaction that undergoes currency conversion. Positions 1–9 contain the settlement amount issuer currency conversion fee. Positions 10–18 contain the settlement amount issuer currency conversion allocation. Positions 19–27 contain the cardholder billing amount, issuer currency conversion fee. Positions 28–36 contain the cardholder billing amount, optional issuer fee. 71–72 Merchant Volume Indicator 2 A code assigned by the acquirer to transactions from merchants eligible for the volume-tier program. 73–76 Message Reason Code 4 A code explaining the reason for sending one of the following: • • • • An acquirer-generated advice, reversal, cancellation, adjustment, or chargeback (validation request or advice) A chargeback reversal or representment (validation request or advice) A Visa fee collection or funds disbursement A copy request (validation request or advice), downtime transaction, or resubmission 77–80 Network IDA code specifying the network (e.g., Cirrus, Plus, Interlink, etc.) to be used for transmission of the message, which determines the program rules that apply to the transaction. 81–144 Network Participation Flags 4 64 Network participation flags. This field is not currently used. 145–150 Plus Property Member Center ID 6 The Plus Property Member Center ID. 151 Reimbursement Attribute 1 A code that identifies the applicable interchange reimbursement fee for a purchase transaction. 152–160 Settlement Amount 9 The settlement amount. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 188 Data element definitions Position Description 161–190 Length Sharing Group Code 30 An optional field used in the U.S. only by POS Integrated Debit participants (merchants and acquirers) to specify the network access priority and determine the routing priority of financial POS requests. This code is sent from the merchant location to V.I.P. The sharing group code is left-justified and can contain up to 30 network designators. All unused positions to the right of the code must be filled with spaces. 191–194 STIP Switch Reason Code 4 A code indicating why SMS STIP responded for the issuer or why the SMS Switch generated an advice. 195–202 Visa Acquirer Business ID 8 The Visa-assigned business ID of the acquirer that signed the merchant for processing purchase or mail/phone order transactions. In this case, the acquirer is referred to as the merchant sponsor. P-62: Tag 0A, Acquirer and Issuer Network ID Format: Variable based on the subtags included TDEs: Acquirer Network ID TDE Issuer Network ID TDE Tag 0A contains data identifying the acquirer and issuer network for a transaction. Subtag Description Format 01 Acquirer Network ID AN 3 02 Issuer Network ID AN 3 P-62: Tag 0B, MasterCard Original Advice Data Format: Variable based on the subtags included TDEs: Banknet Information TDE Tag 0B contains data for MasterCard original advice messages. Subtag Description Format 01 MasterCard Original Advice Network Data AN..9 02 MasterCard Original Advice Settlement Date AN 4 BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 189 Data element definitions P-62: Tag 0C, Strong Cardholder Authentication (SCA) Indicators Format: Variable based on the subtags included TDEs: Strong Cardholder Authentication (SCA) Tag 0C contains Strong Cardholder Authentication (SCA) indicators. Subtag Description Format 01 Single Tap Transaction N1 02 Response to SCA PIN Request N1 03 Issuer requests SCA PIN data N1 P-62: Tag 0D, Strong Cardholder Authentication (SCA) Exemptions Format: Variable based on the subtags included TDEs: Strong Cardholder Authentication (SCA) TDE Tag 0D contains Strong Cardholder Authentication (SCA) exemptions. Subtag Description Format 01 Low Value Payment N1 02 Transaction Risk Analysis N1 03 Trusted Merchant N1 04 Secure Corporate Payment N1 05 Recurring Payment N1 06 Other Merchant-Initiated Transaction N1 07 SCA Delegation N1 P-62: Tag 10, Fee Program Indicator Format: AN 3 TDEs: Fee Program Tag 10 contains the fee program indicator. The fee program indicator is three characters in length. P-62: Tag 11, Merchant Region Format: AN 4 TDEs: Merchant Region Tag 11 contains the merchant region associated with the transaction. The merchant region is four characters in length. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 190 Data element definitions P-62: Tag 12, Merchant Group Format: AN 4 TDEs: Merchant Group Tag 12 contains the merchant group associated with the transaction. The merchant group is four characters in length. P-62: Tag 13, Additional Statement Print Information Format: AN 12 TDEs: Additional Statement Print Information Tag 13 contains additional statement print information sent by the acquirer to assist in formatting the statement data. This data is structured as defined below. Position 1 Description Retrieval of Statement Data Page Indicator Length 1 A number indicating the page of statement data retrieved for a statement print transaction. For the first send of statement print data, this field should be set to 1. The acquirer can increment this number for each subsequent page retrieved. This field is primarily used to avoid double posting a surcharge for multiple-leg statement print transactions. 2–5 Max Statement Data Per Send Length 4 The maximum number of bytes (up to 9992) of statement print data that can be sent in a single message. 6 Supported Statements Indicator 1 A code indicating whether both full and mini statements are supported at the acquirer or whether just one type of statements is supported. Valid values are as follows: B = Both full and mini statements F = Full statements only. M = Mini-statements only. b = Unknown 7 Printer Device Type 1 A code identifying the printer device type. Alphanumeric. 8–10 Number of Characters per Line 3 The number of characters that can be printed per line. Numeric. 11–12 Number of Lines per Page 2 The number of lines that can be printed per page. Numeric. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 191 Data element definitions P-62: Tag 14, Context Cookie Format: AN ..99 TDEs: Context Cookie Tag 14 contains a cookie that is generated by the host and returned by the BASE24-eps system when requesting more statement data or Open Account Relationship (OAR) data. This tag can contain up to 99 alphanumeric characters. The format of this tag is determined by the data formatter (issuer). P-62: Tag 15, Non-Currency Dispense Format: AN 8 TDEs: Non-Currency Dispense Tag 15 contains non-currency dispense information as described below. Position 1–6 Description Item Quantity Length 6 The number of items being purchased. 7–8 Hopper Contents 2 A code that identifies the item dispensed by the ATM. Valid values are any two alphanumeric characters, including codes for LINK noncash products. The value 02 is reserved for travelers checks. LINK: This tag maps to data element 123, sub-field 001 (Product Type, value “LM”) in the LINK MPT transaction message. P-62: Tag 16, Network Original Processing Code Format: AN 6 TDEs: Network Original Processing Code Tag 16 contains the original processing code for the transaction on the external acquirer’s network. P-62: Tag 17, Acquiring Interface Name Format: AN 16 TDEs: Acquiring Interface Generic Data Tag 17 contains the name of the interface that acquired the transaction. For inbound transactions, this value will also be stored in the Generic Data TDE with an outer key of HISO93 and an inner key of ACQ_INTF_NAM. P-62: Tag 18, Channel Time Offset Format: AN 5 BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 192 Data element definitions TDEs: Channel Time Offset Tag 18 contains the time difference, in minutes, between the ATM or POS device location and the BASE24-eps system location. P-62: Tag 19, Original PVV Format: AN 16 TDEs: Original PVV (tde.pvv_orig) Tag 19 contains the original PIN offset (left-justified, blank-filled) prior to a PIN change update. It is used for reversals of PIN change transactions. The script for a PIN change transaction should place the original PVV in the PVV Original TDE and update the Card data source (Card) with the new PIN's offset. When a PIN change reversal is received, the script should simply replace the PIN offset in the Card with the PIN offset from the PVV Original TDE (provided it is present). The original PVV (PIN offset) is 16 characters in length. If the original PVV is padded with any pad characters (e.g., hexadecimal F characters), the pad characters are stripped out when building this tag. P-62: Tag 20, Acquirer Institution ID/Logical Network Format: AN 24 TDEs: Acquirer (tde.acq_id_cde, tde.acq_lgnt) Tag 20 data is structured as follows: Position 1–20 Description Length Acquirer Institution ID 20 The acquirer institution’s routing and transit number or acquirer identification number. 21–24 Logical Network ID 4 The logical network ID of the acquirer institution. P-62: Tag 21, Issuer Institution ID/Logical Network Format: AN 24 TDEs: Issuer (tde.iss_inst_id, tde.iss_lgnt) Tag 21 data is structured as follows: Position 1–20 Description Issuer Institution ID Length 20 The issuer institution’s routing and transit number or issuer identification number. 21–24 Logical Network ID 4 The logical network ID of the issuer institution. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 193 Data element definitions P-62: Tag 22, Digital Audio Service (DAS) Indicator Format: AN 1 TDEs: Digital Audio Service Indicator Tag 22 contains a one-byte flag indicating whether the NCR Digital Audio Service (DAS) was provided for a customer at an NCR ATM. Valid values are as follows: Code Description Y Yes, DAS was provided. N No, DAS was not provided. P-62: Tag 23, Capture Mode P-62: Tag 24, Network ID Format: AN 4 TDEs: Network ID Tag 24 contains four alphanumeric characters identifying the network (e.g., AMXb for American Express) for a transaction. P-62: Tag 25, Card Level Results Format: AN 2 TDEs: Card Level Results Tag 25 contains a two-byte alphanumeric value that identifies card level information, such as the card product associated with the cardholder’s account. If a card product is represented by a single character, it is followed by a blank space. The card level is similar to the instrument type, except it is set by individual card instead of by BIN or account range. For issuers, this field identifies the appropriate card product at the card account level on each transaction and saves issuers from having to reissue a consumer’s card each time the consumer changes card products. Interchanges can populate this field prior to sending a message to the issuer for approval. Issuers and their processors who participate in this program must use the value to correctly populate the authorization code in approved 0110 and 0210 messages. In this case, BASE24-eps must set the sixth position of the Approval Code TDE to the first position of the Card Level Results TDE. Acquirers can optionally receive this field. Examples of values for Visa include the following: Code Description A Visa Traditional B Visa Traditional Rewards C Visa Signature D Visa Infinite BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 194 Data element definitions P-62: Tag 26, Program Identification Format: AN 6 TDEs: Program Identification Tag 26 contains a six-byte alphanumeric value that identifies a card program such as a rewards program. This field allows issuers and acquirers to receive a program identifier in authorization and clearing messages. P-62: Tag 27_ Invoice Number Format: AN 16 TDEs: Invoice Number TDE Tag 27 contains a 16-byte alphanumeric invoice number associated with this transaction, if the invoice number is sent from the terminal. For ATM terminals, invoice numbers are typically used to identify bill payment transactions. For point-of-sale terminals, an invoice number is commonly preprinted on the charge slip used for this transaction. The use of invoice numbers is optional and determined by retailers. P-62: Tag 30, Merchant ID Format: AN 20 TDEs: Switch Merchant ID Tag 30 contains a 20-byte alphanumeric merchant or institution ID sent by the acquirer to identify a specific merchant or institution for interchange calculations. P-62: Tag 31, Cross-Border Transaction Pricing Format: AN 2 TDEs: Cross-Border Transaction Pricing Tag 31 contains two one-byte flags indicating whether this transaction qualifies as a cross-border transaction and could be subject to cross-border transaction pricing. A cross-border transaction is any transaction in which the country location of the merchant or the ATM acquirer differs from the country location of the cardholder’s issuer. Position 1 Description Cross-Border Transaction Indicator Length 1 A flag indicating whether this transaction qualifies as a cross-border transaction. Valid values are as follows: Y = Yes, this transaction qualifies as a cross-border transaction. N = No, this transaction does not qualify as a cross-border transaction BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 195 Data element definitions Position 2 Description Length Cross-Border Currency Indicator 1 A flag indicating whether this transaction was submitted in the local currency of the merchant or does not qualify as a cross-border transaction. Valid values are as follows: Y = Yes, the transaction was submitted in the local currency of the merchant. N = No, the transaction was not submitted in the local currency of the merchant. X = The transaction does not qualify as a cross-border transaction. P-62: Tag 32, Switch Acquirer ID Format: AN ..11 TDEs: Switch Acquirer ID This tag is mapped to and from the Switch Acquirer TDE. For an outbound message, the value of the Visa DPS interface name is mapped to this field if the Switch Acquirer TDE does not exist. Tag 32 contains the acquirer fee tier ID for Visa’s U.S. domestic ATM reimbursement fees. Visa provides tiered reimbursement levels, with tiered qualification determined at the institution level. Institutions that maintain more secure, higher cost ATM portfolios that deliver greater cardholder value qualify for the current ATM interchange reimbursement fee (Tier 1). A lower interchange reimbursement fee (Tier 2) applies for transactions acquired by institutions that deploy less expensive ATMs that generally provide consumers a lower level of value. For Visa/Plus ATM traffic, an acquirer ID is used to designate which tiered interchange is applied. For Principal Plus members, the acquirer ID is assigned by Visa and can either be established within the Plus network system, or the acquirer can send the value to Visa DPS in field 122 of the online message. For Visa DPS-sponsored Plus members, Visa DPS has two acquirer IDs: • • 408815 (Tier 1) 408909 (Tier 2) P-62: Tag 33, Promotion Data Format: AN 52 TDEs: Promotional Data Tag 33 contains promotion data associated with a transaction that is eligible for a promotion, reward, or loyalty program. Position 1–2 Description Promotion Type Format AN 2 A code that indicates the type of promotion (e.g., purchase rebate or discount, sweepstakes, bonusing) associated with this transaction. Visa has reserved position 1 of this field for characters V–Z and position 2 for characters 1–9 and A–Z. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 196 Data element definitions Position 3–27 Description Promotion Code Format AN 25 A value referring to a specific promotion or loyalty program for which this transaction qualifies. Visa has reserved position 1 of this field for characters V–Z and positions 2–25 for characters 1–9 and A–Z. 28–52 Promotion Description AN 25 Free form text providing additional information on the promotion. This field is carried in authorization messages only and provides text information about the promotion that, for example, could be printed on the cardholder receipt. P-62: Tag 34, Contact Information Format: AN 58 or AN 83 TDEs: Contact Information, Contact Information 2 Tag 34 contains contact information for chargebacks, representments, and adjustment transactions. Contact information consists of a back office contact name and phone number for the person at the financial institution who submits the transaction. The length of tag 34 varies depending on whether additional message text is present. Position 1 Description Usage Code Format AN 1 A one-digit code that identifies the message as a chargeback, representment, or adjustment. Valid values are as follows: 0 = Adjustment 1 = First chargeback 2 = First representment 2 Documentation Indicator AN 1 A one-digit code that identifies the status of supporting documentation. Valid values are as follows: Space = No supporting documentation required. 0 = No supporting documentation provided. 1 = supporting documentation to follow. 2 = Invalid acquirer reference number used in prior chargeback record; no supporting documentation was required or received. 3 = Invalid acquirer reference number used in prior chargeback record and supporting documentation was received. 4 = No supporting documentation received for prior chargeback. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 197 Data element definitions Position 3–8 Description Format Chargeback Reference Number AN 6 A six-digit code assigned by issuers to chargebacks. Acquirers that submit representments must include the number in the representment message. Zero-fill if not provided. 9–23 Contact Name AN 15 A contact name at the originating institution. 24–33 Contact Phone Number AN 10 A contact telephone number at the originating institution. 34–58 or 34–83 Message Text AN 25 or AN 25 Unformatted text that describes a chargeback or representment. If additional message text is present in the Contact Information 2 TDE, then the length is 50, otherwise the length is 25. P-62: Tag 35, Intra-Country Data - Japan Format: AN 236 TDEs: Intra-Country Data Tag 35 contains a 236-byte alphanumeric private national-use field entered by acquirers and issuers in Japan for Japan-domestic (intra-country) authorizations. P-62: Tag 36, Free Format Text Format: AN ..233 TDEs: Free Format Text Tag 36 contains free format text that can be used differently depending on the type of transaction. For Visa transactions, tag 36 contains Contact Information for Japan: a 135-byte alphanumeric Japanesedomestic, private-use field for use by issuers in Japan. For Interac administrative transactions, tag 36 is variable length and contains up to 233 characters of free format text. P-62: Tag 38, Source of Funds Format: AN 1 TDEs: Source of Funds Tag 38 contains a 1-byte alphanumeric code indicating the source of funds for prepaid load transactions. This information maps to Field 104, Dataset ID 57 in the VisaNet external message. Valid values are as follows: Code Description 1 Cash 2 Check BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 198 Data element definitions Code 3 Description Card P-62: Tag 39, Business Application ID Format: AN 2 TDEs: Business Application Identifier Tag 39 contains a 2-byte alphanumeric code indicating the business application identifier for original credits and payment transactions. Original credits enable funds to be sent to an account in support of numerous business opportunities. VisaNet external message: maps to Field 104, Dataset ID 57 STAR external message: maps to DE 107, Tag SD, Subtag 01 and DE 109, Tag GI FDR 184 external message: maps to DE 105 position 1-2. Values Description FD Funds Disbursement (General) GD Government Disbursement (General) MD Merchant Disbursement PA Payment Transaction PD Payroll/Pension Disbursement OG Online Gambling Payout GP Gambling Payout (Other than online gambling) MI Money Transfer – Merchant-Initiated BI Money Transfer – Bank Initiated CP Card Bill Payment PS Payment for Goods and Services (General) PG Payment to Government VC Visa Commerce P-62: Tag 40, Sender Data (Original Credits) Format: AN ..50 TDEs: Sender Data Tag 40 contains up to 50 bytes of variable length sender data for original credit money transfer transactions. Sender data consists of the sender’s account number or transaction reference number and primary residential address. STAR: The data in this tag maps to and from data element 107, Tag SD, subtag 12 (General Information) in the STAR external message. For information about the STAR transaction message, refer to the appropriate STAR technical specification. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 199 Data element definitions P-62: Tag 41, Market-Specific Data Format: AN ..210 TDEs: Market Specific Data Tag 41 contains up to 210 alphanumeric bytes of market-specific data that provides additional transaction information. Representatives of the market define and maintain the structure and content of the Market-Specific Data elements. This tag is used primarily by the American Express Global Network Solutions (AEGN) interface. Position 1–3 Description Length Variable Length Indicator AN 3 The number of bytes contained in this tag. This field is not mapped to the Market Specific Data TDE. 4–5 Market Specific Data Indicator AN 2 A code of “MS” indicating market specific data. This field is not mapped to the Market Specific Data TDE. 6–8 Market ISO Country Code AN 3 The three-digit ISO country code for this market. 9–10 Market Specific Data Version Indicator AN 2 A two-character code indicating the version of this market specific data. 11–210 Market Specific Data Elements AN 200 Market specific data elements defined by representatives of the market. P-62: Tag 42, Acquirer Reference Data, Transaction Identifier Format: AN 15 TDEs: Acquirer Transaction ID Tag 42 contains a 15-byte numeric transaction identifier (TID), which is a unique number assigned by American Express Global Network Solutions (AEGN) to identify a transaction throughout its life cycle. Position 1–12 Description Unique Random Number Length N 12 A unique random number assigned to this transaction. 13–14 Source Indicator N2 A two-digit number identifying the source of this transaction. 15 Check Digit N1 A check digit for the TID. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 200 Data element definitions P-62: Tag 43, Visa Risk Information Format: AN 10 TDEs: Visa Risk Information Tag 43 contains Visa advanced authorization online risk assessment condition codes, a reason code, and a risk score to indicate the degree of risk associated with a transaction. Position 1–2 Description Length Risk Condition Code 1 AN 2 An alphanumeric code to describe high risk event information. 3–4 Risk Condition Code 2 AN 2 An alphanumeric code to describe high risk event information. 5–6 Risk Condition Code 3 AN 2 An alphanumeric code to describe high risk event information. 7–8 Risk Reason Code AN 2 An alphanumeric combination that explains the risk score. 9–10 Risk Score AN 2 A score indicating the degree of risk associated with a transaction. P-62: Tag 44, Advanced Authorization Service Data Format: Variable based on the subtags included TDEs: Risk Data Tag 44 contains Visa advanced authorization service data used to evaluate risk for the transaction. The tag consists of subtagged data that is mapped to Visa DPS and other Visa messages as shown in the table below. For information on the Visa DPS message and the information carried in these fields, refer to the Visa DPS ISO 8583 technical specifications supplement . For information on other Visa messages, refer to their respective specifications. The subtag data is shown below. Subtag 01 Description Score Source Format AN 1 Defines the processing option used. Visa DPS Interchange Message: This field maps to the Source Score field (position 1) in the Risk Data (Field 63.8) sub-element. 02 Score Value AN 4 Numeric score generated by a fraud system, ranging from 0000 to 0999. Higher scores indicate a greater likelihood of fraud. Visa DPS Interchange Message: This field maps to the Score Value field (positions 2–5) in the Risk Data (Field 63.8) sub-element. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 201 Data element definitions Subtag 03 Description Response Code Format AN 1 Response code generated by a fraud system. Visa DPS Interchange Message: This field maps to the Response Code field (position 6) in the Risk Data (Field 63.8) sub-element. 04 Reason 1 AN 2 Reason code generated by a fraud system when the score is above the explanation threshold. Visa DPS Interchange Message: This field maps to the reason 1 field (positions 7–8) in the Risk Data (Field 63.8) sub-element. 05 Reason 2 AN 2 Reason code generated by a fraud system when the score is above the explanation threshold. Visa DPS Interchange Message: This field maps to the reason 2 field (positions 9–10) in the Risk Data (Field 63.8) sub-element. 06 Reason 3 AN 2 Reason code generated by a fraud system when the score is above the explanation threshold. Visa DPS Interchange Message: This field maps to the reason 3 field (positions 11–12) in the Risk Data (Field 63.8) sub-element. 07 Risk Score AN 2 Part of the Visa Advanced Authorization Service data: a value that indicates the degree of risk associated with the transaction. Higher values indicate higher authorization risk. Visa DPS Interchange Message: This field maps to the Visa Risk Score field (positions 13–14) in the Risk Data (Field 63.8) subelement. Other Visa Interchange Messages: This field maps to the Risk Score field (positions 1–2) in the Transaction and Account-Level Risk (field 62.21) sub-element. 09 Compromised Account Risk Condition Code AN 2 Part of the Visa Advanced Authorization Service data: a value that provides risk information regarding high risk events, when applicable to the authorization request. Visa DPS Interchange Message: This field maps to the Visa Risk Condition Code 1 field (positions 17–18) in the Risk Data (Field 63.8) subelement. Other Visa Interchange Messages: This field maps to the Compromised Account Risk Condition Code field (positions 1–2) in the Event-Level Risk (field 62.22) sub-element. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 202 Data element definitions Subtag 10 Description Format Compromised Event Reference ID AN 2 Part of the Visa Advanced Authorization Service data: a value used to associate a compromised account with its specific Compromised Account Management System (CAMS) compromised event. Visa DPS Interchange Message: This field maps to the Visa Risk Condition Code 2 field (positions 19–20) in the Risk Data (Field 63.8) subelement. Other Visa Interchange Messages: This field maps to the Compromised Event Reference ID field (positions 3–4) in the EventLevel Risk (field 62.22) sub-element. 12 Risk Condition Code Rank 1 AN 1 Part of the Visa Advanced Authorization Service data: a grouping value assigned to the Compromised Account Risk Condition Code in subtag 9. Visa DPS Interchange Message: This field maps to the VAA Risk Condition Code 1 Rank field (position 23) in the Risk Data (Field 63.8) subelement. 13 Suspect Fraud AN 1 A suspect fraud flag that is set to indicate whether fraud is suspected in the transaction. Visa DPS Interchange Message: This field maps to position 24 in the Risk Data (Field 63.8) subelement. P-62: Tag 51, Bunch Note Acceptor Indicator Format: AN 1 TDEs: Bunch Note Acceptor Deposit Tag 51 is a one-position indicator (a value of 1) used with deposit transactions (processing code 21) from ATM (Java) Device Handler processes. Its purpose is to differentiate, for these transactions, cash from noncash deposits. The presence of this tag indicates that the transaction is a noncash deposit. P-62: Tag 52, PRM Response Format: Variable depending on the subtags included TDEs: PRM Response Tag 52 contains response information received for the transaction from the Proactive Risk Management (PRM) product. This tag carries subtag data as shown in the table below. This information is only available if BASE24-eps is configured to send transactions to PRM in real-time. Subtag 01 Description Real-Time Request Type Format AN 1 The type of real-time request. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 203 Data element definitions Subtag 02 Description Format PRM Interface Processing Response Request AN 1 The type of message that should be returned to the authorizing system. 03 Real-Time Status AN 1 An alphanumeric code identifying the PRM processing status of the transaction. 04 Real-Time Fraud Score AN 3 Numeric score generated by PRM, ranging from 000 to 999, indicating the degree of risk associated with a transaction. 05 Real-Time Rule Fired AN 4 The real-time rule number executed for transaction. 06 Real-Time Rule Disposition AN 1 An alphanumeric code identifying the outcome of the transaction. P-62: Tag 53, Voice Referral Indicator Format: AN 12 TDEs: Acquirer POS Entry Mode Tag 53 contains—for voice referral transactions only—the Point of Service Data Codes values carried by the American Express Global Network Solutions (AEGN) Interchange in its 1100 message. The values in this tag are mapped from Field 22 (Card Acceptor Identification Code) in the AEGN 1100 message and are only populated when position 7 (Card Data Input Mode) is set to V, indicating a voice referral. If position 7 is not set to V, the tag is not included. The structure of Tag 53 is shown in the table below. For information about these values, refer to the American Express reference documentation. Position Description Length 1 Card Input Capability Code AN 1 2 Cardmember Authentication Capability AN 1 3 Card Capture Capability AN 1 4 Operating Environment AN 1 5 Cardmember Present AN 1 6 Card Present AN 1 7 Card Data Input Mode, “V” indicates voice referral AN 1 8 Cardmember Authentication AN 1 9 Cardmember Authentication Entity AN 1 10 Card Data Output Capability AN 1 11 Terminal Output Capability AN 1 BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 204 Data element definitions Position 12 Description Length PIN Capture Capability AN 1 P-62: Tag 54, Fraud Indicator Format: AN 18 TDEs: Fraud Indicator Tag 54 contains fraud indicator data used by the American Express Global Network Solutions (AEGN) Interchange in its 1100 and 1200 messages. The values in this tag are structured as shown in the table below. These values are mapped from field 62 in the AEGN 1100 and 1200 messages. For information about these values, refer to the American Express Network reference documentation. Position Description Length 1–3 Variable Length Indicator AN 3 4–5 Service Indicator (AX = American Express) AN 2 6–8 Request Type Identifier AN 3 9–10 Two-digit 5CSC Indicator AN 2 11–15 Probability Score (blank in 1200 message) AN 5 16–18 Dynamic Rule Recommendation Codes (blank in 1200 message) AN 3 AEVV Validation Result AN 1 AEIPS and Expresspay Cryptogram Validation Result AN 2 19 20-21 P-62: Tag 55, AS2805 National Data Format: Variable based on the subtags included TDEs: AS2805 Data Tag 55 contains national data required by the AS2805 message standard. A host may need to send or receive this information when transactions are sent or received through a BASE24-eps interface supporting the AS2805 message standard. This tag carries subtag data as shown in the table below. These values are mapped to and from corresponding values in data element 47 (Additional National Data) of the AS2805 message standard. For information about these values, refer to the AS2805 message specifications documentation. Subtag 01 Description Fallback Indicator. Format AN 1 An indicator used to define the transaction as Electronic Fallback.This value maps to subtag FBK in the data element 47 of the AS2805 message standard. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 205 Data element definitions Subtag 02 Description Format Faulty Card Read. AN 1 An indicator used to specify that the card data was unable to be read or processed by the card-accepting device.This value maps to subtag FCR in the data element 47 of the AS2805 message standard. 03 Verified Enrollment Response. AN 1 An indicator that can be included when a transaction involves the use of an authentication method for internet transactions.This value maps to subtag VER in the data element 47 of the AS2805 message standard. 04 Payer Authentication Response. AN 1 An indicator that can be included when a transaction involves the use of an authentication method for internet transactions.This value maps to subtag PAR in the data element 47 of the AS2805 message standard. P-62: Tag 56, Transaction Description Format: Variable based on the subtags included TDEs: Varies by subtag Tag 56 contains transaction description data used by the STAR ISO interchange. This tag carries subtag data as shown in the table below. Star ISO Interchange Note: These values are mapped to and from data element 104 (Transaction Description) in the STAR ISO messages. For information about these values, refer to the STAR ISO specifications documentation. Subtag 01 Description Interlink Interchange Group Identifier Format AN 1 TDE: Star Reimbursement Attributes 02 STAR Interchange Group Identifier AN ..3 TDE: Interchange Group ID 03 Aggregation Indicator AN 1 TDE: Aggregation Indicator 04 Authentication Program. A value identifying the authentication method used by the acquirer. AN 1 TDE: Star Data Field 05 Transaction Subtype. A transaction descriptor. AN 1 TDE: Star Data Field BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 206 Data element definitions Subtag 06 Description Product Identifier. A value identifying the product/transaction suite. Format AN 1 TDE: Star Data Field 07 Additional Network Data. Contain the entire STAR Access DE 104 layout. See the STAR ISO specification document for more information. AN 20 TDE: Transaction Description P-62: Tag 57, Address Change Notification Format: AN 3 TDEs: Address Change Notification Tag 57 contains the number of days since an address change occurred on the cardholder account involved in the transaction. This tag can be used in processing interchange transactions, and its use can vary depending on the interchange involved in the transaction. Discover Interchange: For the Discover interchange, this value maps to and from data element 044 (Additional Data) in the Discover transaction message. Issuers provide this information in response messages when an address verification service response is required. Acquirers accept this information when requiring an address verification service response from the issuer. For information on Discover transaction messages, refer to the appropriate Discover technical specification. P-62: Tag 58, Batch Authorization Format: AN 2 TDEs: Batch Authorization Tag 58 contains a two-character alphanumeric value indicating whether or not the transaction originated as a batch authorization transaction. This tag can be used in processing interchange transactions, and its use can vary depending on the interchange involved in the transaction. Discover Interchange: For the Discover interchange, this value maps to and from data element 022 (POS Entry Mode) in the Discover transaction message. Acquirers can provide this information in requests to indicate the card number was entered through batch authorization. For information on Discover transaction messages, refer to the appropriate Discover technical specification. P-62: Tag 59, Subscription Indicator Format: AN 1 TDEs: Subscription Tag 59 contains a one-character alphanumeric value indicating whether or not the transaction is a subscription transaction. Tag values are as follows: Code Description 0 Not a subscription 1 Subscription BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 207 Data element definitions This tag can be used in processing interchange transactions, and its use can vary depending on the interchange involved in the transaction. Discover Interchange: For the Discover interchange, this value is set based on a value of 16 (Paying for a subscription on a regular basis) in data element 003 (Processing Code) of the Discover transaction message. An acquirer host could also send this tag with a value of 1 to identify subscription payment transactions to the Discover interchange. For information on Discover transaction messages, refer to the appropriate Discover technical specification. P-62: Tag 60, Voice Authorization Indicator Format: AN 2 TDEs: Voice Authorization Tag 60 contains a two-character alphanumeric value indicating whether or not the transaction originated as a voice authorization transaction. This tag can be used in processing interchange transactions, and its use can vary depending on the interchange involved in the transaction. Discover Interchange: For the Discover interchange, this value maps to and from data element 022 (POS Entry Mode) in the Discover transaction message. Acquirers can provide this information in requests to indicate the card number was entered through voice authorization. For information on Discover transaction messages, refer to the appropriate Discover technical specification. P-62: Tag 61, Switch Assigned ID Format: AN ..999 (typically, 6 characters) TDEs: Assigned ID Tag 61 contains switch identification data that is moved to and from the BASE24-eps Assigned ID TDE. This tag can be used in processing interchange transactions, and its use can vary depending on the interchange involved in the transaction. Banknet Interchange Note: For Banknet transactions, this value is a MasterCard-assigned ID identifying merchants that can submit transactions for processing under the Maestro Advanced Registration Program. It is mapped to and from data element 48 (Additional Data—Private Use), subelement 32 (Mastercard Assigned ID) in the Banknet messages. For information about this value, refer to the Banknet specifications documentation. Discover Interchange Note: For Discover transactions, this value is a unique 15-numeric ID generated by Discover that remains unchanged for the life of the card transaction. This tag is built outbound on 1110, 1130 and 1210 responses from the Assigned ID TDE, which is built from DE 48, positions 11-25 in the Discover external message. When the ISO 93 Host Interface component processes inbound 1100 requests, this tag is mapped to the Assigned ID TDE, and ultimately, DE 106 Dataset 64 Tag 01 in the Discover external message. P-62: Tag 62, Generic Risk Data Format: Variable based on the subtags included TDEs: Generic Risk Data Tag 62 contains data built from the Generic Risk Data TDE. This tag can be used in processing interchange transactions, and its use can vary depending on the interchange involved in the transaction. Tag 62 carries subtag data as shown in the table below. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 208 Data element definitions Tag 62: Generic Risk Data Subtag 01 Description Scoring Result Format AN 1 Banknet and MDS Interchanges: This value is set with the value from DE 48 (Additional Data - Private Use), subelement 71 (On-behalf Service Indicator), subfield 2 (Onbehalf Result 1) when DE 48 (Additional Data - Private Use), subelement 71 (On-behalf Service Indicator), subfield 1 indicates that the MasterCard On-behalf Service 18 (Fraud Scoring Service) was performed on the transaction. Valid values are: C - Expert Monitoring Fraud Scoring Service was performed successfully U - Expert Monitoring Fraud Scoring Service was not performed successfully BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 209 Data element definitions Tag 62: Generic Risk Data Subtag 02 Description Score Format AN 3 A score value from 000 to 999. If subtag 01 is set to 0, this value must be set to zero. This value is used with MasterCard’s Expert Monitoring Real-time Fraud Scoring Service. Banknet Interchange: For Banknet transactions, this value is mapped from data element 48 (Additional Data—Private Use), subelement 75 (Fraud Scoring Data), subfield 1 (Fraud Score Data) in the Banknet messages. For information about this value, refer to the Banknet specifications documentation. MDS Interchange: For MDS transactions, this value is mapped from data element 48 (Additional Data—Private Use), subelement 75 (Fraud Assessment Prediction Information), subfield 1 (Fraud Assessment Score) in the MDS messages. For information about this value, refer to the MDS specifications documentation. VisaNet Interchange: For VisaNet transactions that have the VEAS indicator set, this value is mapped from field 104, dataset 64, subtag 02 in the VisaNet messages. For information about this value, refer to the VisaNet specifications documentation. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 210 Data element definitions Tag 62: Generic Risk Data Subtag 03 Description Score Reason Code This value is used with MasterCard’s Expert Monitoring Real-time Fraud Scoring Service. Format AN 2 (for MDS and Banknet) AN 2 - 12 (for VisaNet with VEAS indicator set) Banknet Interchange: For Banknet transactions, this value is mapped from data element 48 (Additional Data—Private Use), subelement 75 (Fraud Scoring Data), subfield 2 (Score Reason Code) in the Banknet messages. For information about this value, refer to the Banknet specifications documentation. MDS Interchange: For MDS transactions, this value is mapped from data element 48 (Additional Data—Private Use), subelement 75 (Fraud Assessment Prediction Information), subfield 2 (Score Reason Code) in the MDS messages. For information about this value, refer to the MDS specifications documentation. VisaNet Interchange: For VisaNet transactions that have the VEAS indicator set, this value is mapped from field 104, dataset 64, subtag 03 in the VisaNet messages. For information about this value, refer to the VisaNet specifications documentation. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 211 Data element definitions Tag 62: Generic Risk Data Subtag 04 Description Rule Adjusted Score Format AN 3 This value is used with MasterCard’s Expert Monitoring Business Rules Management Service. Banknet Interchange: For Banknet transactions, this value is mapped from data element 48 (Additional Data—Private Use), subelement 75 (Fraud Scoring Data), subfield 3 (Rule Adjusted Score) in the Banknet messages. For information about this value, refer to the Banknet specifications documentation. MDS Interchange: For MDS transactions, this value is mapped from data element 48 (Additional Data—Private Use), subelement 75 (Fraud Assessment Prediction Information), subfield 3 (Rule Adjusted Score) in the MDS messages. For information about this value, refer to the MDS specifications documentation. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 212 Data element definitions Tag 62: Generic Risk Data Subtag 05 Description Rule Reason Code 1 Format AN 2 This value is used with MasterCard’s Expert Monitoring Business Rules Management Service. Banknet Interchange: For Banknet transactions, this value is mapped from data element 48 (Additional Data—Private Use), subelement 75 (Fraud Scoring Data), subfield 4 (Rule Reason Code 1) in the Banknet messages. For information about this value, refer to the Banknet specifications documentation. MDS Interchange: For MDS transactions, this value is mapped from data element 48 (Additional Data—Private Use), subelement 75 (Fraud Assessment Prediction Information), subfield 4 (Rule Reason Code 1) in the MDS messages. For information about this value, refer to the MDS specifications documentation. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 213 Data element definitions Tag 62: Generic Risk Data Subtag 06 Description Rule Reason Code 2 Format AN 2 This value is used with MasterCard’s Expert Monitoring Business Rules Management Service. Banknet Interchange: For Banknet transactions, this value is mapped from data element 48 (Additional Data—Private Use), subelement 75 (Fraud Scoring Data), subfield 5 (Rule Reason Code 2) in the Banknet messages. For information about this value, refer to the Banknet specifications documentation. MDS Interchange: For MDS transactions, this value is mapped from data element 48 (Additional Data—Private Use), subelement 75 (Fraud Assessment Prediction Information), subfield 5 (Rule Reason Code 2) in the MDS messages. For information about this value, refer to the MDS specifications documentation. 07 Risk Indicator Data AN 6 VisaNet Interchange: For VisaNet transactions that have the VEAS indicator set, this value is mapped from field 104, dataset 64, subtag 01 in the VisaNet messages. For information about this value, refer to the VisaNet specifications documentation. 08 Authorization Decision Recommendation AN 2 VisaNet Interchange: For VisaNet transactions that have the VEAS indicator set, this value is mapped from field 104, dataset 64, subtag 04 in the VisaNet messages. For information about this value, refer to the VisaNet specifications documentation. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 214 Data element definitions Tag 62: Generic Risk Data Subtag 09 Description Merchant Fraud Score Format AN 3 Banknet interchange: For Banknet transactions, this value is mapped from data element 48 (Additional Data - Private Use), subelement 55 (Merchant Fraud Scoring Data), subfield 1 in the Banknet messages. For information about this value, refer to the Banknet specifications document. 10 Merchant Score Reason AN 2 Banknet interchange: For Banknet transactions, this value is mapped from data element 48 (Additional Data - Private Use), subelement 55 (Merchant Fraud Scoring Data), subfield 2 in the Banknet messages. For information about this value, refer to the Banknet specifications document. 11 Merchant Transaction Fraud Scoring Indicator AN 1 Banknet interchange: For Banknet transactions, this value is mapped from data element 48 (Additional Data - Private Use), subelement 61 (POS Data Extended Condition Codes), subfield 4 (Merchant Transaction Fraud Scoring Indicator) in the Banknet messages. This will be the only subtag parsed inbound. Valid values are: 0 - No action required 1 - Transaction to be scored For information about this value, refer to the Banknet specifications document. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 215 Data element definitions Tag 62: Generic Risk Data Subtag Description 12 Format Account Compromise Information ANS 30 Banknet and MDS interchanges: For Banknet and MDS transactions, this value is mapped from data element 48 (Additional Data Private Use), subelement 71 (Onbehalf Services), subfield 2 for service 25 in the Banknet and MDS messages. For information about this value, refer to the Banknet or MDS specifications document. P-62: Tag 63, Informational Text Format: AN ..300 TDEs: Informational Text Tag 63 contains informational text used with Visa SMS dispute processing. In an 0220 or 0422 fee collection or funds disbursement advice, this tag contains the reason for the message. The data in this tag is mapped to and from field 48 (Usage 5—Visa Fee Collections/Funds-Disbursements) in the Visa SMS message. For information about the Visa SMS message, refer to the V.I.P. System SMS POS (Visa & Visa Electron) technical specifications . P-62: Tag 65, Money Transfer Data Format: Variable based on the subtags included TDEs: Transfer Sender Data Tag 65 contains sender data used in enhanced money transfer Original Credit (OCT) transactions. PULSE: The data in this tag maps to and from fields in the PULSE transaction message as noted in the table below. For information about the PULSE transaction message, refer to the appropriate PULSE technical specifications. STAR: The data in this tag maps to and from data elements in the STAR transaction message as noted in the table below. For information about the STAR transaction message, refer to the appropriate STAR technical specifications. VisaNet: The data in this tag maps to and from fields in the VisaNet transaction message as noted in the table below. For information about the VisaNet transaction message, refer to the appropriate VisaNet technical specifications. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 216 Data element definitions Tag 65: Money Transfer Data Subtag 01 Description Sender Reference Number Format AN 16 VisaNet: Maps to field 104, usage 2 (Transaction-Specific Data), dataset ID 5F (Money Transfer Data), tag 01 (Sender Reference Number) of the VisaNet transaction message. 02 Sender Account Number AN 34 VisaNet: Maps to field 104, usage 2 (Transaction-Specific Data), dataset ID 5F (Money Transfer Data), tag 02 (Sender Account Number) of the VisaNet transaction message. STAR: Maps to DE 107, Tag SD, subtag 03 (Account Number) and DE 109, Tag AN (Account Number) of the STAR transaction message. Discover: Maps to DE 104, dataset ID 57 (Funds Transfer Data), tag 08 (Account Number) of the Discover transaction message. 03 Sender Name AN..40 VisaNet: Maps to field 104, usage 2 (Transaction-Specific Data), dataset ID 5F (Money Transfer Data), tag 03 (Sender Name) of the VisaNet transaction message. STAR: Maps to DE 107, Tag SD, subtag 04 (Sender Name) and DE 109, Tag N1 (Sender Name) of the STAR transaction message. Discover: Maps to DE 104, dataset ID 57 (Funds Transfer Data), tag 03 (Sender's Name) of the Discover transaction message. 04 Sender Address AN 35 VisaNet: Maps to field 104, usage 2 (Transaction-Specific Data), dataset ID 5F (Money Transfer Data), tag 04 (Sender Address) of the VisaNet transaction message. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 217 Data element definitions Tag 65: Money Transfer Data Subtag 05 Description Sender City Format AN 25 VisaNet: Maps to field 104, usage 2 (Transaction-Specific Data), dataset ID 5F (Money Transfer Data), tag 05 (Sender City) of the VisaNet transaction message. STAR: Maps to DE 107, Tag SD, subtag 06 (Sender City) and DE 109, Tag A3 (Sender City) of the STAR transaction message. Discover: Maps to DE 104, dataset ID 57 (Funds Transfer Data), tag 05 (Sender's City) of the Discover transaction message. 06 Sender State AN 2 VisaNet: Maps to field 104, usage 2 (Transaction-Specific Data), dataset ID 5F (Money Transfer Data), tag 06 (Sender State) of the VisaNet transaction message. STAR: Maps to DE 107, Tag SD, subtag 07 (Sender State) and DE 109, Tag A7 (Sender State) of the STAR transaction message. 07 Sender Country AN 3 VisaNet: Maps to field 104, usage 2 (Transaction-Specific Data), dataset ID 5F (Money Transfer Data), tag 07 (Sender Country) of the VisaNet transaction message. STAR: Maps to DE 107, Tag SD, subtag 08 (Sender Country) and DE 109, Tag A8 (Sender Country) of the STAR transaction message. Discover: Maps to DE 104, dataset ID 57 (Funds Transfer Data), tag 06 (Sender's Country) of the Discover transaction message. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 218 Data element definitions Tag 65: Money Transfer Data Subtag 08 Description Source of Funds Format AN 2 VisaNet: Maps to field 104, usage 2 (Transaction-Specific Data), dataset ID 5F (Money Transfer Data), tag 08 (Source of Funds) of the VisaNet transaction message. STAR: Maps to DE 107, Tag SD, subtag 10 (Source of Funds) and DE 109, Tag SF (Source of Funds) of the STAR transaction message. Discover: Maps to DE 104, dataset ID 57 (Funds Transfer Data), tag 09 (Source of Funds) of the Discover transaction message. 09 Recipient Name AN 30 VisaNet: Maps to field 104, usage 2 (Transaction-Specific Data), dataset ID 5F (Money Transfer Data), tag 0A (Recipient Name) of the VisaNet transaction message. STAR: Maps to DE 107, Tag SD, subtag 11 (Recipient Name ) of the STAR transaction message. Discover: Maps to DE 104, dataset ID 57 (Funds Transfer Data), tag 11 (Recipient's Name) of the Discover transaction message. 10 Sender Birth Date AN 8 VisaNet: Maps to field 48, usage 37 of the VisaNet transaction message. STAR: Maps to DE 107, Tag SD, subtag 13 (Sender Date of Birth) and DE 109, Tag DB (Date of Birth) of the STAR transaction message. Discover: Maps to DE 104, dataset ID 57 (Funds Transfer Data), tag 10 (Sender's Date of Birth) of the Discover transaction message. 11 Claim Code AN 20 VisaNet: Maps to field 104, usage 2 Dataset ID 5F, tag 09 of the VisaNet transaction message. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 219 Data element definitions Tag 65: Money Transfer Data Subtag 12 Description Extended Unique Reference Number Format AN 19 PULSE: Maps to field 109, Tag R1 of the PULSE ACT/AFT transaction messages. STAR: Maps to DE 107, Tag SD, subtag 02 (Unique Transaction Reference) and DE 109, Tag R1 (Unique Transaction Reference) of the STAR transaction message. Discover: Maps to DE 104, dataset ID 57 (Funds Transfer Data), tag 02 (Unique Reference Number) of the Discover transaction message. 13 Extended Sender's Address AN 50 PULSE: Maps to field 109, Tag A1 of the PULSE ACT/AFT transaction messages. STAR: Maps to DE 107, Tag SD, subtag 05 (Sender Address) and DE 109, Tag A1 (Sender Address) of the STAR transaction message. Discover: Maps to DE 104, dataset ID 57 (Funds Transfer Data), tag 04 (Sender's Address) of the Discover transaction message. 14 Sender's Postal Code AN 15 PULSE: Maps to field 109, Tag A4 of the PULSE ACT/AFT transaction messages. STAR: Maps to DE 107, Tag SD, subtag 09 (Sender Postal Code) and DE 109, Tag A4 (Sender Postal Code) of the STAR transaction message. Discover: Maps to DE 104, dataset ID 57 (Funds Transfer Data), tag 07 (Sender's Postal Code) of the Discover transaction message. 15 Customer Phone Number AN 16 VisaNet: Maps to field 125, usage 2, dataset ID 04, tag 01 (Customer Phone Number) of the VisaNet transaction message. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 220 Data element definitions Tag 65: Money Transfer Data Subtag Description 16 Customer Email Address Format AN 99 VisaNet: Maps to field 125, usage 2, dataset ID 04, tag 02 (Customer Email Address) of the VisaNet transaction message. 17 Payment Type AN 3 Discover: Maps to DE 104, dataset ID 57 (Funds Transfer Data), tag 01 (Payment Type) of the Discover transaction message. 18 Merchant Sender Tax ID AN 4 VisaNet: Field 104, Usage 2Transaction-Specific Data in TLV format, Dataset ID 63-Non-IndustrySpecific Data, tag 05 in the VisaNet transaction message. 19 Individual Sender Tax ID AN 4 VisaNet: Field 104, Usage 2Transaction-Specific Data in TLV format, Dataset ID 63-Non-IndustrySpecific Data, tag 06 in the VisaNet transaction message. 20 Receiver Account Number AN 34 NYCE: Maps to NYCE field 110, subtag AN (Account Number). P-62: Tag 66, Watch List Management Data Format: Variable based on the subtags included TDEs: Watch List Management Data Tag 66 contains watch list scoring information provided by Visa for use with enhanced money transfer Original Credit (OCT) transactions. This tag also is used by the FDR 184 interface for OCT transactions. VisaNet: The data in this tag maps from fields in the VisaNet transaction message as noted in the table below. For information about the VisaNet transaction message, refer to the appropriate VisaNet technical specifications. FDR 184: The data in this tag maps from fields in the FDR 184 transaction message as noted in the table below. For information about the FDR 184 transaction message, refer to the appropriate FDR 184 specifications. The subtag data is shown below. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 221 Data element definitions Tag 66: Watch List Management Data Subtag Description 01 Format Validation Code AN 4 VisaNet: Maps from field 48, usage 37 (Visa Money Transfer), positions 5–8 (WLM Validation Code) in the transaction message. 02 Results Code AN 3 VisaNet: Maps from field 48, usage 37 (Visa Money Transfer), positions 9–11 (WLM Results Code) in the transaction message. FDR 184: Maps from field 123 type code WS. 03 Activity Code AN 1 VisaNet: Maps from field 48, usage 37 (Visa Money Transfer), position 12, (VMT Activity Check Result) in the transaction message. P-62: Tag 67, Visa Merchant Verification Value Format: N10 or AN10 TDEs: Merchant Verification Value Tag 67 contains the Merchant Verification Value (MVV) used to identify merchants that participate in Select Merchant Fee (SMF) programs. This value is required in all Visa transactions. This field maps to data element 62 (Custom Payment Service Fields), subfield 20 (Merchant Verification Value), as N10 in the Visanet transaction message. For information about Visa transaction messages, refer to the appropriate Visanet technical specifications. Banknet supports this value for Visa in data element 48, subelement 36 (Visa defined Data), subfield 1—Merchant Verification Value with a format of AN10. Note: When this data is present, it must be all numeric unless the host can determine the issuer of message, in which case, either N10 or AN10 can be sent. P-62: Tag 68, Banknet Reference Number Format: AN.. 9 TDEs: Banknet Information Class Tag 68 contains the Banknet reference number associated with the transaction. Banknet Interchange: This field maps from data element 63 (Network Data), subfield 2 (Banknet Reference Number) in the Banknet transaction message. For information about Banknet transaction messages, refer to the appropriate Banknet technical specifications. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 222 Data element definitions P-62: Tag 69, Dynamic Currency Conversion Indicator Format: AN 1 TDEs: Dynamic Currency Conversion Indicator Tag 69 can contain a Dynamic Currency Conversion Indicator—a value of 1—which indicates to Visa that the merchant involved in the transaction has performed a local currency conversion for the transaction at the point-ofsale (called Dynamic Currency Conversion) and the transaction is being submitted in the cardholder’s billing currency. VisaNet Interchange: This value maps to and from data element 126 (Visa Private Use Fields), subfield 19 (Dynamic Currency Conversion Indicator) in the VisaNet transaction message. For information about VisaNet transaction messages, refer to the appropriate VisaNet technical specifications. P-62: Tag 70, Trace ID Format: AN 15 TDEs: BankNet Information Tag 70 can contain a trace ID used by acquirers with travel and entertainment (T&E) transactions to identify incremental authorization messages and link them to the original authorization for the T&E event. MDS Interchange: This value maps from (not to) data element 48 (Additional Data), subfield 63 (Trace ID) in the MDS transaction message. For information about MDS transaction messages, refer to the appropriate MDS technical specifications. Banknet Interchange: This value maps to and from data element 48 (Additional Data), subfield 63 (Trace ID) or data elements 63 (Network Data) and 15 (Date, Settlement) in the Banknet transaction message. For information about Banknet transaction messages, refer to the appropriate Banknet technical specifications. P-62: Tag 71, Transit Program Format: AN 4 TDEs: BankNet Information Tag 71 can contain a transit program identifier used by MasterCard to clearly identify transit transactions in authorization, clearing, and financial transaction messages. The transit program value is made up of two two-byte subfields: Transit Transaction Type and Transportation Mode. MDS Interchange: This value maps to and from data element 48 (Additional Data), subfield 64 (Transit Program) in the MDS transaction message. For information about MDS transaction messages, refer to the appropriate MDS technical specifications. P-62: Tag 72, Authorizing Agent ID Code Format: AN 6 TDEs: Authorizing Agent ID Tag 72 contains an authorizing agent ID, which is used when processing MasterCard automated fuel dispenser (AFD) transactions through VisaNet. VisaNet Interchange: This value maps to and from data element 104, Usage 2 (Transaction-Specific Data), Dataset 65 (MasterCard Member-Defined Data), tag 03 (Authorizing Agent ID Code) in the VisaNet transaction BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 223 Data element definitions message. For information about VisaNet transaction messages, refer to the appropriate VisaNet technical specifications. CUP Interface: The Issuer's IIN is mapped to this tag. P-62: Tag 73, Charity Giving Information Format: AN.. 60 TDEs: Person to Person Tag 73 can contain charity giving bilateral data used by the Link interchange to identify the charity being paid for charity giving transactions or to identify the third party ID for Link non-cash products. For outgoing messages, tag 73 is built if the Person to Person TDE is present, its third party ID data member is set, its intended use flag data member is set to 2 (payer initiated payment) and its business use flag data member is set to F (charity giving transaction). Otherwise, the tag is not built. For incoming messages, if tag 73 is present, the Person to Person TDE is created and the tag data is moved to the third party ID data member in the TDE. In addition the intended use flag data member is set to 2 and the business use flag data member is set to F. Link Interchange: This value maps to and from data element 123, subfield 018 (charity giving bilateral data) in the Link transaction message. For information about Link transaction messages, refer to the appropriate Link technical specifications. P-62: Tag 74, Unformatted Visa Text Format: LLLVAR ANS.. 254 TDEs: Visa Unformatted Text Tag 74 contains unformatted Visa text, which is used in administrative text messages to convey unformatted text between processors. It is also used to carry data for unformatted text in authorization and reversal messages. VisaNet: Maps to and from data element 048 usage 9A (Text Message) in the VisaNet transaction message. For information about the VisaNet transaction message, refer to the appropriate VisaNet technical specifications. It can also map to DE 48 usage 2 (Unformatted Text in Authorization/Reversal Messages). P-62: Tag 76, Fraud Notification Information Format: LLVAR AN...23 TDEs: Fraud Indicator Tag 76 contains MasterCard fraud notification information—data necessary to provide acquirers with the date of a second fraud-related chargeback, as well as an accurate count of total fraud-related chargebacks related to the same PAN and expiration date. The data in this tag maps to and from fields in the MasterCard transaction message as noted in the table below. For information about the MasterCard transaction message, refer to the appropriate MasterCard technical specifications. The subtag data is shown below. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 224 Data element definitions Tag 76: Fraud Notification Information Subtag Description 01 Fraud Notification Service Date— sent by MasterCard to the acquirer. Format AN 6 MasterCard: Maps to and from data element 48 subelement 19 (Fraud Notification Information) field 1 (Fraud Notification Service Date) in the transaction message. 02 Fraud Notification Service Chargeback Counter—sent by MasterCard to the acquirer. AN 2 MasterCard: Maps to and from data element 48 subelement 19 (Fraud Notification Information) field 2 (Fraud Notification Service Chargeback Counter) in the transaction message. 03 Fraud Notification Second Presentment Rights Indicator—sent by the acquirer to MasterCard. AN 3 MasterCard: Maps to and from data element 48 subelement 19 (Fraud Notification Information) field 3 (Fraud Notification Second Presentment Rights Indicator) in the transaction message. P-62: Tag 77, Customer 1 ID Format: Positions 1-2: Customer ID type (NN) Positions 3-38: Customer ID AN..36 TDEs: Customer ID Tag 77 contains Customer ID information. If necessary, a second Customer ID is stored in Tag 78. The first two positions of this tag are two digits that identify the type of customer ID. Customer ID types are user defined and can range from 01-99. For example, 01 could be defined as an email address. In this case, the tag might contain "01john.banker@aciworldwide.com", where "01" is the customer ID type and "john.banker@aciworldwide.com" is the customer ID value (the customer's email address . If you define a customer ID type of 02 to represent a mobile phone number, the tag might contain "021234567890", where "02" is the customer ID type and "1234567890" is the customer ID value (the customer's mobile phone number) . This tag is used for the following Acquirer and Issuer transactions: • • If the from account is card-initiated, this tag is used for the to account. If the from account is customer-initiated and only one Customer ID is used to transfer between accounts belonging to that customer, this tag is used to determine the from and to accounts. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 225 Data element definitions • • If the from account is customer-initiated and the to account is with a separate Customer ID, this tag is used for the from account and Tag 78 (Customer 2 ID) is used for the to account. This tag is present whenever the transaction is customer-initiated. For all other transactions, this tag must contain customer ID information if the PAN is not present. Note: File update transactions for Customer data are journaled under the customer ID specified in data element P-62, tag 77 (Customer 1 ID). The customer ID value in P-62, tag 77 must be a valid customer ID and may be different from the customer ID value provided in data element S-72, tag 35 (Customer Table) if multiple customer IDs are to be updated. If P-62, tag 77 is not present for an update or delete to a Customer, Customer Account, or Customer Multibyte data source record, the file update transaction is denied. P-62: Tag 78, Customer 2 ID Format: Positions 1-2: Customer type (NN) Positions 3-38: Customer ID AN..36 TDEs: Customer ID 2 Tag 78 is used to store customer ID information, in addition to Tag 77, if necessary. The first two positions of this tag are two digits that identify the type of customer ID. Customer ID types are user defined and can range from 01-99. For example, 01 could be defined as an email address. In this case, the tag might contain "01john.banker@aciworldwide.com", where "01" is the customer ID type and "john.banker@aciworldwide.com" is the customer ID value (the customer's email address . If you define a customer ID type of 02 to represent a mobile phone number, the tag might contain "021234567890", where "02" is the customer ID type and "1234567890" is the customer ID value (the customer's mobile phone number) . This tag is used in Acquirer transactions when the from account is customer-initiated and the to account is with a separate Customer ID. Tag 77 (Customer ID) is used for the from account and this tag is used for the to account. P-62: Tag 79, Visa V.me Data Format: Variable based on the subtags included TDEs: PayPass Tag 79 contains data specific to transactions initiated under the V.me by Visa brand. VisaNet: The data in this tag maps to and from fields in the VisaNet transaction message as noted in the table below. For information about the VisaNet transaction message, refer to the appropriate VisaNet technical specifications. The subtag data is shown below. Tag 79: Visa V.me Data Subtag 01 Description Agent Unique Account Result Format AN 5 VisaNet: Maps to and from data element 126 subelement 18 (Agent Unique Account Result) in the transaction message. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 226 Data element definitions Tag 79: Visa V.me Data Subtag Description 02 Format Additional Authorization Method AN 2 Reserved for future use. 03 Additional Authorization Reason Code AN 2 VisaNet: Maps to and from data element 126 subelement 21 (Additional Authorization Reason Code) in the transaction message. P-62: Tag 80, Bank ID Format: N (type) AN..34 TDEs: Bank Indicator Tag 80 contains Bank ID information. This tag is used for the following Acquirer transactions: • If the from account is card-initiated or customer-initiated, this tag is used for the to account. This tag is used for the following Issuer transactions: • If the to account is initiated with a bank account number and account number, this tag must be present. P-62: Tag 82, PIN Data Format: Variable based on the subtags included TDEs: NYCE Tag 82 contains data specific to the NYCE interface. NYCE: The data in this tag maps to and from fields in the NYCE transaction message as noted in the table below. For information about the NYCE transaction message, refer to the appropriate NYCE technical specifications. The subtag data is shown below. Tag 82: PIN Data Subtag 01 Description Program Description Data Format AN 2 NYCE: Maps to and from data element 124 in the transaction message. 02 PIN Indicator Data AN 1 NYCE: Maps to and from data element 124 in the transaction message. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 227 Data element definitions P-62: Tag 83, Preauth Sequence Number Format: AN .. 12 TDEs: Pre-Authorization Tag 83 contains the transaction sequence number for preauthorizations so that the current transaction can be matched with its associated preauth correctly. P-62: Tag 84, Authorization Message Indicator Format: AN 1 TDEs: Banknet Information TDE Tag 84 contains the an indicator specifying the type of authorization message. Valid values are: Code Description 0 Normal Authorization 1 Final Authorization P-62: Tag 85, Acquirer Transaction ID Format: AN 16 TDEs: Acquirer Transaction ID Tag 85 contains a 16-byte transaction ID that maps to and from the Acquirer Transaction ID TDE for PULSE interface transactions. Tag 85: Acquirer Transaction ID Subtag Description 01 Transaction ID Format AN 16 PULSE: Maps to and from the “TR” subtag of data elements 124 and 125 in the PULSE ISO external message. P-62: Tag 86, Card Acceptor ID Code Format: AN 15 TDEs: Card Acceptor ID Code Tag 86 contains a 15-byte code that maps to and from the Card Acceptor ID Code TDE. If the Card Acceptor ID Code TDE is present and the Card Acceptor ID code variable is present, then the value in the Card Acceptor ID code will be moved to the Alternate Card Acceptor ID code. The value in tag 86 is always populated in Card Acceptor ID code in the Card Acceptor ID Code TDE. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 228 Data element definitions P-62: Tag 87, Pseudo Terminal Identifier Format: AN 16 TDEs: Pseudo Terminal Identifier Tag 87 contains a 16-byte code that maps to and from the Pseudo Terminal Identifier TDE for GCC-Net interface transactions. P-62: Tag 88, VisaNet Data Element 48 Format: AN ..255 TDEs: Visa Data Element 48 TDE VisaNet Data Element 48 is a multi use field and can contain up to 255 AN bytes depending on the usage. For more information on supported usages, refer to the Visa specifications documentation. P-62: Tag 89, Security Control Information Format: ANS 2 TDEs: Security Control Information TDE Tag 89 contains the acquirer or issuer zone key index value from the Security Control TDE. The zone key index is 2 characters in length. P-62: Tag 90, Key Index Format: N2 TDEs: Key Index TDE Tag 90 contains the destination MAC Key Index associated with the transaction. The key index is 2 numeric characters in length. P-62: Tag 91, Multi Clearing Sequence Format: ANS 2 TDEs: Multi Clearing Sequence TDE Tag 91 contains the multi clearing sequence information associated with the transaction. The multi clearing sequence is 2 characters in length. P-62: Tag 92, SPAN2 Data Format: Variable based on the subtags included TDEs: SPAN2 Data TDE BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 229 Data element definitions Tag 92 contains data used by the SAMA SPAN2 interface. Tag 94: Mobile Payment Data Subtag Description Format 01 Original STAN ANS 6 02 Original RRN ANS 12 03 Settlement Date ANS 4 P-62: Tag 93, Source Original Data Format: ANS 42 TDEs: Source Original Data TDE Tag 93 contains the acquiring network's original data associated with the transaction in the acquiring network's format. The data is taken from the Source Original Data TDE, which is set when receiving a message containing DE 90 (for ISO 8583 1987 based messages) or DE 56 (for ISO 8583 1993 based messages), and will contain that format. The source original data is 42 characters in length. P-62: Tag 94, Additional Merchant Data Format: Variable based on the subtags included TDEs: POS Merchant TDE Tag 94 contains additional merchant data used by the BankNet Interface and MasterCard Debit Switch (MDS). Tag 94: Mobile Payment Data Subtag Description Format 01 Payment facilitator ID ANS 11 02 Independent sales organization ID ANS 11 03 Sub-merchant ID ANS 15 04 Additional Response Code ANS 25 P-62: Tag 95, Mixed Media Deposits Format: AN 68 TDEs: Mixed Media Deposit Detail Tag 95 contains mixed media deposit details for NCR Scalable Deposit Module (SDM) by North American NCR Aptra Edge Standard Message Interface (SMI) application customers. Tag 95: Mixed Media Deposits Position 1-2 Description Number of checks deposited BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 Length N2 230 Data element definitions Tag 95: Mixed Media Deposits Position Description 3-4 Number of bill denominations deposited 5-68 Mixed media bill collection • • • • Length N2 variable Length of key (currency code + bill denomination) - N2 Currency code - N3 Bill denomination - variable Bill count for this denomination N2 Occurs up to 8 times. P-62: Tag 96, EMV Application PAN Sequence Number (APSN) Format: AN 2 TDEs: EMV Status TDE Tag 96 contains the APSN for a specific application on a multi-application EMV card. This tag is used for file updates using the APSN as the card sequence number to differentiate among multiple applications on the EMV card with the same primary PAN. P-62: Tag 97, Log Only Transaction Description Format: ANS ..20 TDEs: Log Only Transaction Description TDE Tag 97 contains the optional transaction description for log only transactions. For ATM log only transactions, this can be mapped from the ATM Operation Code Mapping using the OpCdeLogOnly operation code task. For RuPay log only transactions, this can be mapped from the Log Only Mapping Profile Configuration window. P-62: Tag 98, Acquirer Amount Data Format: Variable based on the subtags included TDEs: Acquirer Amount Original Acquirer Amount Tag 98 contains acquirer amount information that the acquiring interface can send to the host. This tag is structured as follows. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 231 Data element definitions Tag 98: Acquirer Amount Data Subtag Description 01 Format Acquirer Amount N15 The acquirer amount contains the following subfields: Amount (N12) Currency Code (N3) 02 Original Acquirer Amount N15 The original acquirer amount contains the following subfields: Amount (N12) Currency Code (N3) P-64: Primary Message Authentication Code Format: AN 16 TDEs: Not applicable Carries the message authentication code (MAC) for the message. Inclusion of this data element is subject to the following conditions: • • • Message authentication has been configured for the interface on the ISO8583 (93) Host Interface Configuration window. This data element is specified as conditional in the ISO message profile for the interface. No secondary data elements (S-65 through S-128) are included in the message. If the message contains secondary data elements, data element S-128 is used to carry the message authentication code. If the message authentication code is carried in data element S-128, data element P-64 is not included in the message. S-66: Amounts, Original Fees Format: LLLVAR ANS ..204 TDEs: Transaction Fee, Original (tde.org_fee_amt, tde.org_fee_crncy_cde, tde.org_fee_conv_rate, tde.org_fee_rcncl_amt, tde.org_fee_rcncl_crncy_cde) Contains the original fees associated with this transaction. These fees can be used when attempting to partially reverse or partially chargeback a previous transaction, or to perform a partial approval. These amounts are for information only and are not used in the calculation of reconciliation totals. The amount is expressed in the currency of the associated currency code data element. Where a minor unit of currency applies, amounts are expressed in the minor unit of currency, without a decimal separator. For example, an amount value of 100 in US currency signifies one US dollar, but 100 in Italian currency signifies 100 lire. All amounts in reconciliation messages are in the currency of reconciliation. This functionality is reserved for future use. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 232 Data element definitions If the VAT issuer indicator in the VAT TDE is set to combine, the VAT amount will be combined with the surcharge amount and the fee type will be 00. If the VAT issuer indicator is set to separate, the VAT amount will be in a separate value from the surcharge amount with a fee type of 74. The Amounts, Original Fees data element consists of up to six sets of values for the following fees. The fee type code associated with each fee is provided in parentheses. • • • • • • • • Transaction fee (surcharge) (00) Transaction processing fee (01) Currency conversion fee (15) International Service Assessment (ISA) fee (70) Cardholder billing fee (71) Issuer transaction fee (72) Overdraft fee (73) Value added tax (VAT) (74) Each set of values consists of six data elements in fixed length format totaling 34 characters as follows: • • • • • • Original Fee Type Code (N 2) Original Currency Code, Fee (N 3 or A 3) Original Amount, Fee (x + N 8, where x represents C for credit or D for debit) Original Conversion rate, fee (N 8) Original Amount, Reconciliation Fee (x + N 8, where x represents C for credit or D for debit) Original Currency Code, Reconciliation Fee (N 3) The valid fee type codes listed in ISO 8583 (second edition 1993-12-15) Financial Transaction Card Originated Messages - Interchange Message Specifications are as follows: Code Description 00 Transaction fee 01 Transaction processing fee 02 Fee collection fee 03 File action fees 04 Telex, telephone and cable charges 05 Auto-telex charges 06 Lost/stolen card report fees 07 Merchant service fees 08 Recovered card awards 09 Invalid chargeback handling fee 10 Recovery of copy/original fees 11 Returned guaranteed check 12 Emergency cash disbursement handling fee 13 Arbitration cash disbursement handling fee 14 Incorrect merchant identification/transaction data handling fee 15 Currency conversion fee 16 Special handling fee BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 233 Data element definitions Code Description 17 Investigation fees 18 Emergency card replacement fee 19 Warning bulletin handling fee 20 Good faith acceptance 21 Collection letters 22–39 Reserved for ISO use 40–69 Reserved for national use 70–99 Reserved for private use S-67: Extended Payment Data Format: N2 TDEs: Extended Payment Code The Extended Payment Code (S-67) data element contains a repayment period (in months) for MasterCard cardholders to make deferred payments for a transaction. The acquirer is responsible for populating this data element in an authorization request with the correct value based on the cardholder’s request. Valid repayment periods are: 03, 06, 12, 18, 24, 36, and 48 months. Thus, valid extended payment codes for this data element are: 03, 06, 12, 18, 24, 36, and 48. The issuer is responsible for managing the cardholder agreement, including the interest assessment and determination of monthly payment. MasterCard does not perform interest calculations or determine the amount of monthly payments. Since this cardholder payment agreement is managed directly by the issuer, the process of clearing and settling these transactions with merchants/acquirers is not impacted. S-68: Country Code, Receiving Institution Format: N3 TDEs: Receiving Institution (tde.rcv_inst_cntry_cde, tde.rcv_inst_id_cde) The Country Code, Receiving Institution data element contains the code of the country where the receiving institution is located (see ISO 3166). S-70: Country Code, Authorizing Agent Institution Format: N3 TDEs: Authorizing Agent Institution (tde.auth_agent_inst_cntry_cde, tde.auth_agent_inst_id_cde) The Country Code, Authorizing Agent Institution data element contains the code of the country where the authorizing agent institution is located (see ISO 3166). BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 234 Data element definitions S-71: Message Number Format: N8 TDEs: Not applicable The Message Number data element contains a number assigned to a message by the transaction originator that is used to monitor the integrity and continuity of the data being exchanged. This data element is reserved for future use. S-72: Data Record Format: LLLVAR ANS ..999 TDEs: Data Record (no exported operators) This data element is mapped to and from the Data Record TDE, unless a different TDE is explicitly stated for a particular field. The Data Record data element contains other data required to be passed to support an administrative or file action message. All tags sent for any given 1304/1305 message must be associated with the same Primary Account Number (PAN) contained in P-2 or P-34. Use of tags This data element carries tagged data items. The tags defined for this data element are listed below. Tagged data items are structured in the following manner: a tag identifying the type of data, followed immediately by a three-digit length (LLL) identifying the length of the data, followed immediately by the data itself. The data type can be alphanumeric or special characters, but ACI recommends using alphanumeric characters. Tag + LLL + data. Tagged data varies in length depending on the tag, and multiple tagged data items can be included in any order within the data element. Use of subtags Some tags use subtags to identify the various data fields involved in the file action. Refer to the specific tag documentation for descriptions of the supported subtags and their purposes. Subtag data is structured as follows: the subtag identifying the type of field data, followed immediately by a threedigit length (LLL) identifying the length of the field data, followed immediately by the field data itself. Subtag + LLL + field data. Multiple subtags can be present within a single tag, and can be in any order within the tag. Note: Although subtags are generally optional, some subtags are required to read the Card or Positive_Balance data sources and are thus mandatory in the file action message. S-72: Tag 01, Card Data Source Updates and Inquiries Format: Variable based on the subtags included BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 235 Data element definitions TDEs: Data Record Tag 01 contains fields in the Card, Card Account, and Card Account Multibyte data sources to be updated or inquired on in a file action request message sent from the ISO 93 host to the BASE24-eps system. Each field that can be updated or inquired on in the Card, Card Account, and Card Account Multibyte data sources is identified using a subtag. These subtags can be carried—in any combination and any order—in this S-72 data element tag or in tag 10 of the S-127 data element. These subtags are formatted in exactly the same way whether they are carried in the S-72 or S-127 data elements, and they are combined from both data elements for processing, so it does not matter in which data element they are carried, as long as they are not duplicated and the maximum size allowed for the data element is not exceeded. Required subtags for a Card, Card Account, or Card Account Multibyte data source update Inclusion of subtags depends on the type of update function being performed. Function Add Required subtags Subtags must be supplied for any data source fields that need to be set to specific values. Data source fields not included will be set to default values in the new record. Note: If 10 or fewer accounts are associated with a Card record, only a Card data source record is created. If more than 10 accounts are associated with the Card record, a corresponding Card Account data source record is created as well—with any fields not supplied set to their default values. If any multibyte fields are included, a corresponding Card Account Multibyte record is created. Replace The replace function is handled as an add or change function depending on the situation. If a specified record does not exist, the function is treated as an add. If a specified record does exist, the function is treated as an update. Subtags should be supplied accordingly. Update Subtags need only be supplied for those fields in a record to be updated. If a subtag is not supplied, the corresponding field in the record is not affected. To remove a specific field value, include the applicable subtag set to the appropriate default value. This will update the corresponding field in the record to the supplied default values. Delete No subtags are required or processed. Although no subtags are required to delete a record, you must still provide S-72, tag 01 (with a blank value) in the file update message. Card, Card Account, or Card Account Multibyte data source inquiries Card, Card Account, or Card Account Multibyte data source inquiries can request specific data by specifying the subtags of the data to be returned. In this case, specified subtags should be included with a zero length and no data. For example, subtag 02 should be included as 02000. Card data source inquiries can also return a default set of data. In this case, no subtags should be included. Instead, S-72 tag 01 or S-127 tag 10 should be submitted with a zero-length and no data. For example, S-72 tag 01 would be sent as 01000 or S-127 tag 10 would be sent as 100000. The default set of data returned includes the following subtags: 2, 6–18, 22–23, 29–64, A0–A9, and AA–AV. No data is returned from the Card Account or Card Account Multibyte data source in this case. All inquiry response information is carried as subtag data in S-127 tag 10, and in all cases, data is only returned in a subtag if there is data in the corresponding Card, Card Account, or Card Account Multibyte data source field. Subtag definitions Subtag definitions are provided below for all of the Card, Card Account, and Card Account Multibyte subtags. The subtags have been grouped as follows: BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 236 Data element definitions • • • • • Basic Card Subtags CSM Buffer Subtags Card Limit Subtags Card Account Subtags Card Account Multibyte Subtags Subtag definitions – basic Card subtags The following is a list of basic Card subtags. All of these subtags represent data carried in the Card data source. Data length and type is provided for each. Tag 01: Card data source updates and inquiries – basic Card subtags Subtag 01 Description Instrument Type Format AN 2 One or two alphanumeric characters used to identify branding of the card. Examples include Visa Credit (Vb), Visa Debit (VD), American Express Credit (AX), MasterCard Credit (Mb), Proprietary (P*), where b denotes a blank space. 02 Instrument Status AN 2 Two user-defined alphanumeric characters indicating the current status of the primary card. Currently defined values include: 00–15 = Open 60 = Denied-Lost 70 = Denied-Stolen 80 = Denied-Closed To specify a change date to be associated with this status, subtag 26 must be included. 03 PIN Verification Value AN 12 The PIN verification value (PVV) for the card. To specify a change date to be associated with this value, subtag 27 must be included. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 237 Data element definitions Tag 01: Card data source updates and inquiries – basic Card subtags Subtag 04 Description Effective Date Format N8 The date, in YYYYMMDD format, the primary instrument (e.g., card) becomes effective. To specify a change date to be associated with this value, subtag 72 must be included. 05 Secondary Effective Date N8 The date, in YYYYMMDD format, the secondary instrument (e.g., card) becomes effective. 06 Expiration Date N6 The date, in YYYYMM format, on which the instrument expires. To specify a change date to be associated with this value, subtag 71 must be included. 07 Secondary Expiration Date N6 The date, in YYYYMM format, on which the secondary instrument expires. 08 Secondary Instrument Status AN 2 Two user-defined alphanumeric characters indicating the current status of the secondary card. Currently defined values include: 00–15 = Open 60 = Denied-Lost 70 = Denied-Stolen 80 = Denied-Closed To specify a change date to be associated with this status, subtag 28 must be included. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 238 Data element definitions Tag 01: Card data source updates and inquiries – basic Card subtags Subtag 09 Description Number of Accounts Format N2 The total number of accounts associated with the card. Up to 80 accounts can be associated with a Card record. Thus, this field must be set to a value of 00–80 or contain blanks when an add is performed.This value is an index to the last account defined for the Card record. Since accounts need not all be populated with data, this value may not be equal to the number of accounts actually in use. 22 Default Primary Account Type AN 2 The default account type used to determine the default account. 23 Limit Profile AN 16 The limit profile assigned to this card. The limit profile is used as part of the key to the Limits data source (Limits). 24 Address Verification Flag N1 A code indicating whether address verification should be performed for this card. Valid values are as follows: 0 = No, address verification should not be performed (default). 1 = Yes, address verification should be performed. 25 Customer ID If the Customer ID Type subtag (75) is set to zeros, this field contains the customer ID associated with a particular PAN/member number. AN 36 (If using Card v6 data source. Introduced in 2.0.) AN 28 (If using Card v5 or earlier data source. 11.1 and earlier.) If the Customer ID Type subtag (75) is set to a non-zero value, this field contains the customer ID associated with a particular PAN/ member number and with the customer ID type. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 239 Data element definitions Tag 01: Card data source updates and inquiries – basic Card subtags Subtag 26 Description Instrument Status Change Date Format N 12 The date and time, in YYMMDDhhmmss format (Greenwich Mean Time), the instrument status was last changed. You can include this subtag in conjunction with subtag 02 to specify a specific status change date. If this subtag is not included, but subtag 02 is, the status change date will be set to the current system time. If subtag 02 is not included, this subtag is ignored. 27 PIN Change Date N 12 The date and time, in YYMMDDhhmmss format (Greenwich Mean Time), the PIN was last changed. You can include this subtag in conjunction with subtag 03 to specify a specific verification value change date. If this subtag is not included, but subtag 03 is, the change date will be set to the current system time. If subtag 03 is not included, this subtag is ignored. 28 Secondary Instrument Status Change Date N 12 The date and time, in YYMMDDhhmmss format (Greenwich Mean Time), the secondary instrument status was last changed. You can include this subtag in conjunction with subtag 08 to specify a specific status change date. If this subtag is not included, but subtag 08 is, the status change date will be set to the current system time. If subtag 08 is not included, this subtag is ignored. 65 Address 1 AN 25 The first line of the address associated with this instrument. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 240 Data element definitions Tag 01: Card data source updates and inquiries – basic Card subtags Subtag 66 Description Address 2 Format AN 25 The second line of the address associated with this instrument. 67 Postal Code N 10 The postal code of the address associated with this instrument. 68 Depository Type N1 A code indicating the preferred depository type when a deposit is made to distinguish between business deposits and normal deposits. Valid values are as follows: 0 = Use standard depository. 1 = Use commercial depository. 69 ATC Reset Flag N1 A flag indicating whether or not Application Transaction Count (ATC) usage is to be reset. Valid values are as follows: 0 = ATC usage should not be reset. 1 = ATC usage should be reset. When performing a file update or partial-file refresh, a value of 1 causes the ATC usages to be reset at the time of the file update or partial refresh. For information on ATC usage and ATC usage resets, refer to the BASE24-eps EMV support guide . To specify a change date to be associated with this value, subtag 70 must be included. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 241 Data element definitions Tag 01: Card data source updates and inquiries – basic Card subtags Subtag 70 Description ATC Reset Flag Change Date Format N 12 The date and time, in YYMMDDhhmmss format (Greenwich Mean Time), the ATC Reset Flag was last changed. You can include this subtag in conjunction with subtag 69 to specify a specific ATC Reset Flag change date. If this subtag is not included, but subtag 69 is, the ATC Reset Flag change date will be set to the current system time. If subtag 69 is not included, this subtag is ignored. 71 Expiration Date Change Date N 12 The date and time, in YYMMDDhhmmss format (Greenwich Mean Time), the Expiration Date was last changed. You can include this subtag in conjunction with subtag 06 to specify a specific Expiration Date change date. If this subtag is not included, but subtag 06 is, the Expiration Date change date will be set to the current system time. If subtag 06 is not included, this subtag is ignored. 72 Effective Date Change Date N 12 The date and time, in YYMMDDhhmmss format (Greenwich Mean Time), the Effective Date was last changed. You can include this subtag in conjunction with subtag 04 to specify a specific Effective Date change date. If this subtag is not included, but subtag 04 is, the Effective Date change date will be set to the current system time. If subtag 04 is not included, this subtag is ignored. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 242 Data element definitions Tag 01: Card data source updates and inquiries – basic Card subtags Subtag 73 Description Check Base Flag Format N1 A flag indicating whether transactions involving checks—not defined in the Check Status data source—should be included in Total Cash Advance/Total Withdrawal usages and checked against Total Cash Advance/Total Withdrawal limits. This value can override the corresponding prefix-level setting for a specific cardholder. Valid values are as follows: 0 = No 1 = Yes 2 = Use Prefix value (default) 74 Check Status Check Base Flag N1 A flag indicating whether transactions involving checks— defined in the Check Status data source—should be included in Total Cash Advance/Total Withdrawal usages and checked against Total Cash Advance/Total Withdrawal limits. This value can override the corresponding prefix-level setting for a specific cardholder. Valid values are as follows: 0 = No 1 = Yes 2 = Use Prefix value (default) 75 Customer ID Type N2 Indicates the type of entity represented by the customer ID. Valid values are defined by the financial institution and may range from 01 to 99. A value of 00 indicates that no Customer ID was used. 79 Primary PAN AN 28 The primary PAN associated with a multi-application EMV chip card. Requires the AS215 - EMV MultiApplication Support module license. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 243 Data element definitions Tag 01: Card data source updates and inquiries – basic Card subtags Subtag 80 Description Primary PAN Sequence Number Format AN 3 The primary PAN sequence number associated with a multi-application EMV chip card. Requires the AS215 - EMV Multi-Application Support module license. 81 EMV Application Block Flag AN 1 Indicates whether an EMV Application Block script should be sent to a multi-application EMV chip card. Requires the AS215 - EMV Multi-Application Support module license. 82 EMV PUT DATA Script Flag AN 1 Indicates if an EMV PUT DATA script should be sent to the EMV card to reset the Lower Consecutive Offline Limit. 83 Timestamp of EMV PUT DATA Script Flag Last Change N 12 (yymmddhhmmss) Timestamp of the last time the Send Put Data LCOL flag was changed. 84 Timestamp EMV PUT DATA Script Last Sent N 12 (yymmddhhmmss) Timestamp of the last time the Send Put Data LCOL script was sent to the EMV chip card. 86 Card Last Script Originator N1 Identifies whether BASE24-eps or an EMV Script Manager originated the last issuer script sent to this EMV card or application on a multiapplication EMV card in a transaction response. 87 Card Last Script Originator Change Date N 12 (yymmddhhmmss) Timestamp of the last time the Card Last Script Originator was changed. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 244 Data element definitions Tag 01: Card data source updates and inquiries – basic Card subtags Subtag 88 Description PIN Change Support Indicator Format N1 Specifies whether synchronization of the online and offline PIN is required for this EMV card. Subtag definitions – CSM buffer subtags The following are CSM buffer subtags. Data length and type is provided for each. CSM buffers are variable-length buffers for custom software modifications (CSMs). These CSM buffers must begin with a three-digit length prefix indicating the length of the data to follow (i.e., CSM buffers are formatted as <LLL><data>). For example, subtag 19 carrying 10 bytes of actual CSM data would be formatted as <subtag><subtag data length><csm data length><csm data>. Example: 190130101234567890 The length of a CSM buffer (when added to the other included subtag fields) cannot exceed allowable maximums for the message and data elements. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 245 Data element definitions Tag 01: Card/Card Account data source updates and inquiries – CSM buffer subtags Subtag 19 Description CSM Buffer - Card Data Source A variable-length buffer for custom software modifications (CSMs) to the Card data source. The data in this buffer cannot contain any embedded binary values. For update or inquiry requests, the Card CSM buffer can be placed in S-72 tag 01, S-127 tag 10, or S-127 tag 11, but not in more than one of those locations. In addition, for inquiry requests, the Card CSM buffer can only be carried in S-127 tag 11 if there is at least one other subtag being carried in S-72 tag 01 or S-127 tag 10. For inquiry responses, the Card CSM buffer is always returned as subtag 19 in S-127 tag 10. Length/Type AN ..999 (including the 3-digit length prefix) TDE Storage: If S-127 tag 11 is present in the file update message, the Card CSM buffer from that tag is stored in the Card CSM Buffer TDE. In this case, if the Card CSM buffer subtag 19 is also present in S-72 tag 01 or S-127 tag 10, the subtag 19 buffer information is not saved. If S-127 tag 11 is not present in the file update message but the Card CSM buffer subtag 19 is present in S-72 tag 01 or S-127 tag 10, the subtag 19 buffer data is stored along with the other subtag information in the Data Record TDE —unless the combined length of all of the subtag data from S-72 tag 01 and S-127 tag 10 exceeds the length of the Data Record TDE (999 bytes). In this case, the subtag 19 buffer data is stored in the Card CSM Buffer TDE instead of the Data Record TDE. Card CSM buffer data must be in TLV format to be displayed on the UI and manipulated by auth scripts. Each piece of data is assigned a 3 digit tag ID, and they are stored BASE24-eps® Release Version Independent together with the 2-digit length and ISO 8583:1993 Host External Messagevalue Specification - Mayin17, 2019in the of each data a string CSM buffer field. For example, tag 246 Data element definitions Tag 01: Card/Card Account data source updates and inquiries – CSM buffer subtags Subtag JW Description CSM Buffer - Card Account Data Source Length/Type ANS ..999 (including the 3-digit length prefix) A variable-length buffer for custom software modifications (CSMs) to the Card Account data source. The data in this buffer cannot contain any embedded binary values.For update or inquiry requests, the Card Account CSM buffer can be placed in S-72 tag 01 or S-127 tag 10, but not in both. For inquiry responses, the Card Account CSM Buffer is always returned as subtag JW in S-127 tag 10. TDE Storage: If subtag JW is present in S-72 tag 01 or S-127 tag 10, this buffer data is stored along with the other subtag information in the Data Record TDE. Card limit definitions The fields described in the following table are standard fields for each of the six limits that can be associated with a Card data source. The subtags representing these fields are included following the table. Field definitions Limit Name – The name assigned to the specified limit for a payment instrument. Limit Maximum – The maximum count or amount limit assigned to the corresponding limit name. For an amount limit, the decimal point is implied based on the currency code of the limit. Limit Currency Code – The three-digit currency code associated with the limit amount for the corresponding limit name. If the limit is a count, you must set the corresponding currency code field to all zeros. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 247 Data element definitions Field definitions Limit Period – A code specifying the usage period for the corresponding limit. Valid values are as follows: 0 = Usages not cleared. 1 = Fixed number of days. (Default) 2 = One week. 3 = Two weeks. 4 = First and fifteenth of each month. 5 = Every month. 6 = Every three months. 7 = Every six months. 8 = Every year. 9 = Daily, except for Saturdays, Sundays, and holidays. 10 = Daily, except for Sundays and holidays. 11 = Daily, except for Saturdays and holidays. 12 = Fixed number of hours. 20 = Rolling number of minutes. 21 = Rolling number of 2-minute intervals. 22 = Rolling number of hours. 23 = Rolling number of days. 24 = Rolling number of weeks. 25 = Rolling number of months. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 248 Data element definitions Field definitions Limit Period Additional Data – A value further defining the usage period value for the corresponding limit. If the corresponding Limit Period field is set to a value of 1, this field specifies the number of days for the usage period. The default is three days. If the corresponding Limit Period field is set to a value of 2 or 3, this field indicates the day of the week on which the usage period begins. Valid values are as follows: 1 = Sunday (Default) 2 = Monday 3 = Tuesday 4 = Wednesday 5 = Thursday 6 = Friday 7 = Saturday If the corresponding Limit Period field is set to a value of 5, 6, 7, or 8, this field indicates the day of the month on which the usage period begins. Valid values are 1–28. The default is 1. If the corresponding Limit Period field is set to a value of 12, this field specifies the number of hours for the usage period. Valid values are 1–999. The default is 6. If the corresponding Limit Period field is set to a value of 20, 21, 22, 23, 24 or 25, this field indicates the number of usage accumulation periods associated with the selected rolling limit usage period. Valid values are 1 - 30. If the corresponding Limit Period field is set to a value of 4, 9, 10, or 11, this field does not apply. Limit Expiration Date – The date, in YYYYMMDD format, on which the corresponding limit expires. A value of all spaces in this field indicates that the corresponding limit does not have an expiration date. Subtag definitions – Card limit subtags The following is a list of Card limit subtags. Data length and type is provided for each. Tag 01: Card data source updates and inquiries – Card limit subtags Subtag Description Format 29 Limit 1 Name 30 Limit 1 Maximum 31 Limit 1 Currency Code N3 32 Limit 1 Period N2 33 Limit 1 Period Additional Data N3 59 Limit 1 Expiration Date N8 34 Limit 2 Name 35 Limit 2 Maximum 36 Limit 2 Currency Code N3 37 Limit 2 Period N2 BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 AN 16 N 12 AN 16 N 12 249 Data element definitions Tag 01: Card data source updates and inquiries – Card limit subtags Subtag Description Format 38 Limit 2 Period Additional Data N3 60 Limit 2 Expiration Date N8 39 Limit 3 Name 40 Limit 3 Maximum 41 Limit 3 Currency Code N3 42 Limit 3 Period N2 43 Limit 3 Period Additional Data N3 61 Limit 3 Expiration Date N8 44 Limit 4 Name 45 Limit 4 Maximum 46 Limit 4 Currency Code N3 47 Limit 4 Period N2 48 Limit 4 Period Additional Data N3 62 Limit 4 Expiration Date N8 49 Limit 5 Name 50 Limit 5 Maximum 51 Limit 5 Currency Code N3 52 Limit 5 Period N2 53 Limit 5 Period Additional Data N3 63 Limit 5 Expiration Date N8 54 Limit 6 Name 55 Limit 6 Maximum 56 Limit 6 Currency Code N3 57 Limit 6 Period N2 58 Limit 6 Period Additional Data N3 64 Limit 6 Expiration Date N8 AN 16 N 12 AN 16 N 12 AN 16 N 12 AN 16 N 12 Card account definitions The fields described in the following table are standard fields for each of the 80 accounts that can be associated with the card data source. Accounts 1 through 10 are contained in the Card data source. Accounts 11 through 80 are contained in the Card Account data source. The subtags representing these fields are included following the table. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 250 Data element definitions Field definitions Account Number – The account number of the designated account associated with the instrument. Account Type – A code indicating the type of the designated account. This code is user-defined, but must match the account record in the Positive Balance data source. Examples include 10–19 for savings accounts, 30–39 for credit accounts, and 20–29 for checking accounts. Account Status – A code indicating the current status of the designated account. Currently defined values are 00–15, which indicate that the account is open and will be included in open account relationship (OAR) account selection if applicable, and 90, which indicates that the account is closed. All other account status values are user-defined. Account Description – A user-defined description of the designated account. Subtag definitions – Card account subtags The following is a list of Card account subtags. Data length and type is provided for each. Tag 01: Card data source updates and inquiries – Card account subtags Subtag Description Format 10 Account 1 Number 11 Account 1 Type AN 2 12 Account 1 Status AN 2 AL Account 1 Description AN 10 13 Account 2 Number AN 28 14 Account 2 Type AN 2 15 Account 2 Status AN 2 AM Account 2 Description AN 10 16 Account 3 Number AN 28 17 Account 3 Type AN 2 18 Account 3 Status AN 2 AN Account 3 Description AN 10 A0 Account 4 Number AN 28 A1 Account 4 Type AN 2 A2 Account 4 Status AN 2 AO Account 4 Description AN 10 A3 Account 5 Number AN 28 A4 Account 5 Type AN 2 A5 Account 5 Status AN 2 AP Account 5 Description BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 AN 28 AN 10 251 Data element definitions Tag 01: Card data source updates and inquiries – Card account subtags Subtag Description Format A6 Account 6 Number A7 Account 6 Type AN 2 A8 Account 6 Status AN 2 AQ Account 6 Description AN 10 A9 Account 7 Number AN 28 AA Account 7 Type AN 2 AB Account 7 Status AN 2 AR Account 7 Description AN 10 AC Account 8 Number AN 28 AD Account 8 Type AN 2 AE Account 8 Status AN 2 AS Account 8 Description AN 10 AF Account 9 Number AN 28 AG Account 9 Type AN 2 AH Account 9 Status AN 2 AT Account 9 Description AN 10 AI Account 10 Number AN 28 AJ Account 10 Type AN 2 AK Account 10 Status AN 2 AU Account 10 Description AN 10 B0 Account 11 Number AN 28 B1 Account 11 Type AN 2 B2 Account 11 Status AN 2 B3 Account 11 Description AN 10 B4 Account 12 Number AN 28 B5 Account 12 Type AN 2 B6 Account 12 Status AN 2 B7 Account 12 Description AN 10 B8 Account 13 Number AN 28 B9 Account 13 Type BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 AN 28 AN 2 252 Data element definitions Tag 01: Card data source updates and inquiries – Card account subtags Subtag Description Format BA Account 13 Status BB Account 13 Description AN 10 BC Account 14 Number AN 28 BD Account 14 Type AN 2 BE Account 14 Status AN 2 BF Account 14 Description AN 10 BG Account 15 Number AN 28 BH Account 15 Type AN 2 BI Account 15 Status AN 2 BJ Account 15 Description AN 10 BK Account 16 Number AN 28 BL Account 16 Type AN 2 BM Account 16 Status AN 2 BN Account 16 Description AN 10 BO Account 17 Number AN 28 BP Account 17 Type AN 2 BQ Account 17 Status AN 2 BR Account 17 Description AN 10 BS Account 18 Number AN 28 BT Account 18 Type AN 2 BU Account 18 Status AN 2 BV Account 18 Description AN 10 BW Account 19 Number AN 28 BX Account 19 Type AN 2 BY Account 19 Status AN 2 BZ Account 19 Description AN 10 C0 Account 20 Number AN 28 C1 Account 20 Type AN 2 C2 Account 20 Status AN 2 C3 Account 20 Description BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 AN 2 AN 10 253 Data element definitions Tag 01: Card data source updates and inquiries – Card account subtags Subtag Description Format C4 Account 21 Number C5 Account 21 Type AN 2 C6 Account 21 Status AN 2 C7 Account 21 Description AN 10 C8 Account 22 Number AN 28 C9 Account 22 Type AN 2 CA Account 22 Status AN 2 CB Account 22 Description AN 10 CC Account 23 Number AN 28 CD Account 23 Type AN 2 CE Account 23 Status AN 2 CF Account 23 Description AN 10 CG Account 24 Number AN 28 CH Account 24 Type AN 2 CI Account 24 Status AN 2 CJ Account 24 Description AN 10 CK Account 25 Number AN 28 CL Account 25 Type AN 2 CM Account 25 Status AN 2 CN Account 25 Description AN 10 CO Account 26 Number AN 28 CP Account 26 Type AN 2 CQ Account 26 Status AN 2 CR Account 26 Description AN 10 CS Account 27 Number AN 28 CT Account 27 Type AN 2 CU Account 27 Status AN 2 CV Account 27 Description AN 10 CW Account 28 Number AN 28 CX Account 28 Type BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 AN 28 AN 2 254 Data element definitions Tag 01: Card data source updates and inquiries – Card account subtags Subtag Description Format CY Account 28 Status CZ Account 28 Description AN 10 D0 Account 29 Number AN 28 D1 Account 29 Type AN 2 D2 Account 29 Status AN 2 D3 Account 29 Description AN 10 D4 Account 30 Number AN 28 D5 Account 30 Type AN 2 D6 Account 30 Status AN 2 D7 Account 30 Description AN 10 D8 Account 31 Number AN 28 D9 Account 31 Type AN 2 DA Account 31 Status AN 2 DB Account 31 Description AN 10 DC Account 32 Number AN 28 DD Account 32 Type AN 2 DE Account 32 Status AN 2 DF Account 32 Description AN 10 E0 Account 33 Number AN 28 E1 Account 33 Type AN 2 E2 Account 33 Status AN 2 E3 Account 33 Description AN 10 E4 Account 34 Number AN 28 E5 Account 34 Type AN 2 E6 Account 34 Status AN 2 E7 Account 34 Description AN 10 E8 Account 35 Number AN 28 E9 Account 35 Type AN 2 EA Account 35 Status AN 2 EB Account 35 Description BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 AN 2 AN 10 255 Data element definitions Tag 01: Card data source updates and inquiries – Card account subtags Subtag Description Format EC Account 36 Number ED Account 36 Type AN 2 EE Account 36 Status AN 2 EF Account 36 Description AN 10 EG Account 37 Number AN 28 EH Account 37 Type AN 2 EI Account 37 Status AN 2 EJ Account 37 Description AN 10 EK Account 38 Number AN 28 EL Account 38 Type AN 2 EM Account 38 Status AN 2 EN Account 38 Description AN 10 EO Account 39 Number AN 28 EP Account 39 Type AN 2 EQ Account 39 Status AN 2 ER Account 39 Description AN 10 ES Account 40 Number AN 28 ET Account 40 Type AN 2 EU Account 40 Status AN 2 EV Account 40 Description AN 10 EW Account 41 Number AN 28 EX Account 41 Type AN 2 EY Account 41 Status AN 2 EZ Account 41 Description AN 10 F0 Account 42 Number AN 28 F1 Account 42 Type AN 2 F2 Account 42 Status AN 2 F3 Account 42 Description AN 10 F4 Account 43 Number AN 28 F5 Account 43 Type BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 AN 28 AN 2 256 Data element definitions Tag 01: Card data source updates and inquiries – Card account subtags Subtag Description Format F6 Account 43 Status F7 Account 43 Description AN 10 F8 Account 44 Number AN 28 F9 Account 44 Type AN 2 FA Account 44 Status AN 2 FB Account 44 Description AN 10 FC Account 45 Number AN 28 FD Account 45 Type AN 2 FE Account 45 Status AN 2 FF Account 45 Description AN 10 FG Account 46 Number AN 28 FH Account 46 Type AN 2 FI Account 46 Status AN 2 FJ Account 46 Description AN 10 FK Account 47 Number AN 28 FL Account 47 Type AN 2 FM Account 47 Status AN 2 FN Account 47 Description AN 10 FO Account 48 Number AN 28 FP Account 48 Type AN 2 FQ Account 48 Status AN 2 FR Account 48 Description AN 10 FS Account 49 Number AN 28 FT Account 49 Type AN 2 FU Account 49 Status AN 2 FV Account 49 Description AN 10 FW Account 50 Number AN 28 FX Account 50 Type AN 2 FY Account 50 Status AN 2 FZ Account 50 Description BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 AN 2 AN 10 257 Data element definitions Tag 01: Card data source updates and inquiries – Card account subtags Subtag Description Format G0 Account 51 Number G1 Account 51 Type AN 2 G2 Account 51 Status AN 2 G3 Account 51 Description AN 10 G4 Account 52 Number AN 28 G5 Account 52 Type AN 2 G6 Account 52 Status AN 2 G7 Account 52 Description AN 10 G8 Account 53 Number AN 28 G9 Account 53 Type AN 2 GA Account 53 Status AN 2 GB Account 53 Description AN 10 GC Account 54 Number AN 28 GD Account 54 Type AN 2 GE Account 54 Status AN 2 GF Account 54 Description AN 10 H0 Account 55 Number AN 28 H1 Account 55 Type AN 2 H2 Account 55 Status AN 2 H3 Account 55 Description AN 10 H4 Account 56 Number AN 28 H5 Account 56 Type AN 2 H6 Account 56 Status AN 2 H7 Account 56 Description AN 10 H8 Account 57 Number AN 28 H9 Account 57 Type AN 2 HA Account 57 Status AN 2 HB Account 57 Description AN 10 HC Account 58 Number AN 28 HD Account 58 Type BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 AN 28 AN 2 258 Data element definitions Tag 01: Card data source updates and inquiries – Card account subtags Subtag Description Format HE Account 58 Status HF Account 58 Description AN 10 HG Account 59 Number AN 28 HH Account 59 Type AN 2 HI Account 59 Status AN 2 HJ Account 59 Description AN 10 HK Account 60 Number AN 28 HL Account 60 Type AN 2 HM Account 60 Status AN 2 HN Account 60 Description AN 10 HO Account 61 Number AN 28 HP Account 61 Type AN 2 HQ Account 61 Status AN 2 HR Account 61 Description AN 10 HS Account 62 Number AN 28 HT Account 62 Type AN 2 HU Account 62 Status AN 2 HV Account 62 Description AN 10 HW Account 63 Number AN 28 HX Account 63 Type AN 2 HY Account 63 Status AN 2 HZ Account 63 Description AN 10 I0 Account 64 Number AN 28 I1 Account 64 Type AN 2 I2 Account 64 Status AN 2 I3 Account 64 Description AN 10 I4 Account 65 Number AN 28 I5 Account 65 Type AN 2 I6 Account 65 Status AN 2 I7 Account 65 Description BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 AN 2 AN 10 259 Data element definitions Tag 01: Card data source updates and inquiries – Card account subtags Subtag Description Format I8 Account 66 Number I9 Account 66 Type AN 2 IA Account 66 Status AN 2 IB Account 66 Description AN 10 IC Account 67 Number AN 28 ID Account 67 Type AN 2 IE Account 67 Status AN 2 IF Account 67 Description AN 10 IG Account 68 Number AN 28 IH Account 68 Type AN 2 II Account 68 Status AN 2 IJ Account 68 Description AN 10 IK Account 69 Number AN 28 IL Account 69 Type AN 2 IM Account 69 Status AN 2 IN Account 69 Description AN 10 IO Account 70 Number AN 28 IP Account 70 Type AN 2 IQ Account 70 Status AN 2 IR Account 70 Description AN 10 IS Account 71 Number AN 28 IT Account 71 Type AN 2 IU Account 71 Status AN 2 IV Account 71 Description AN 10 IW Account 72 Number AN 28 IX Account 72 Type AN 2 IY Account 72 Status AN 2 IZ Account 72 Description AN 10 J0 Account 73 Number AN 28 J1 Account 73 Type BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 AN 28 AN 2 260 Data element definitions Tag 01: Card data source updates and inquiries – Card account subtags Subtag Description Format J2 Account 73 Status J3 Account 73 Description AN 10 J4 Account 74 Number AN 28 J5 Account 74 Type AN 2 J6 Account 74 Status AN 2 J7 Account 74 Description AN 10 J8 Account 75 Number AN 28 J9 Account 75 Type AN 2 JA Account 75 Status AN 2 JB Account 75 Description AN 10 JC Account 76 Number AN 28 JD Account 76 Type AN 2 JE Account 76 Status AN 2 JF Account 76 Description AN 10 JG Account 77 Number AN 28 JH Account 77 Type AN 2 JI Account 77 Status AN 2 JJ Account 77 Description AN 10 JK Account 78 Number AN 28 JL Account 78 Type AN 2 JM Account 78 Status AN 2 JN Account 78 Description AN 10 JO Account 79 Number AN 28 JP Account 79 Type AN 2 JQ Account 79 Status AN 2 JR Account 79 Description AN 10 JS Account 80 Number AN 28 JT Account 80 Type AN 2 JU Account 80 Status AN 2 JV Account 80 Description BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 AN 2 AN 10 261 Data element definitions Subtag definitions – Card Account Multibyte subtags The following is a list of Card Account Multibyte subtags. All of these subtags represent data carried in the Card Account Multibyte data source. These values represent multibyte versions of specific Card and Card Account data. Data length and type is provided for each. Note: Multibyte information is carried as binary in the Card Account Multibyte data source. This binary information must be represented in these subtags in a two-character hexadecimal display format. Refer to “Card Account Multibyte Subtag — Two-Character Hexadecimal Display Format” for information about how this hexadecimal display data must be created. Tag 01: Card data source updates and inquiries – Card Account Multibyte subtags Subtag L0 Description Customer ID The multibyte representation (in two-character hexadecimal display format) of the customer ID associated with the payment instrument or with the PAN/member number. This field is a multibyte version of the subtag 25 value. Format AN ..144 (If using Card v6 data source. Introduced in 2.0.) AN ..112 (If using Card v5 or earlier data source. 11.1 and earlier.) If the Customer ID Type subtag (75) is set to zeros, this field contains the multibyte representation of the customer ID associated with a particular PAN/member number. If the Customer ID Type subtag (75) is set to a non-zero value, this field contains the multibyte representation of the customer ID associated with a particular PAN/ member number and with the customer ID type. L1 Address 1 AN ..100 The multibyte representation (in two-character hexadecimal display format) of the first address line associated with the payment instrument. This field is a multibyte version of the subtag 65 value. L2 Address 2 AN ..100 The multibyte representation (in two-character hexadecimal display format) of the second address line associated with the payment instrument. This field is a multibyte version of the subtag 66 value. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 262 Data element definitions Tag 01: Card data source updates and inquiries – Card Account Multibyte subtags Subtag L3 Description Postal Code Format AN ..40 The multibyte representation (in two-character hexadecimal display format) of the postal code associated with the payment instrument. This field is a multibyte version of the subtag 67 value. Subtags L4–NB carry multibyte representations (in two-character hexadecimal display format) of the account descriptions for accounts 1 through 80—associated with a payment instrument. Account descriptions are user-defined descriptions of the corresponding accounts. L4 Account 1 Description AN ..40 L5 Account 2 Description AN ..40 L6 Account 3 Description AN ..40 L7 Account 4 Description AN ..40 L8 Account 5 Description AN ..40 L9 Account 6 Description AN ..40 LA Account 7 Description AN ..40 LB Account 8 Description AN ..40 LC Account 9 Description AN ..40 LD Account 10 Description AN ..40 LE Account 11 Description AN ..40 LF Account 12 Description AN ..40 LG Account 13 Description AN ..40 LH Account 14 Description AN ..40 LI Account 15 Description AN ..40 LJ Account 16 Description AN ..40 LK Account 17 Description AN ..40 LL Account 18 Description AN ..40 LM Account 19 Description AN ..40 LN Account 20 Description AN ..40 LO Account 21 Description AN ..40 BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 263 Data element definitions Tag 01: Card data source updates and inquiries – Card Account Multibyte subtags Subtag Description Format LP Account 22 Description AN ..40 LQ Account 23 Description AN ..40 LR Account 24 Description AN ..40 LS Account 25 Description AN ..40 LT Account 26 Description AN ..40 LU Account 27 Description AN ..40 LV Account 28 Description AN ..40 LW Account 29 Description AN ..40 LX Account 30 Description AN ..40 LY Account 31 Description AN ..40 LZ Account 32 Description AN ..40 M0 Account 33 Description AN ..40 M1 Account 34 Description AN ..40 M2 Account 35 Description AN ..40 M3 Account 36 Description AN ..40 M4 Account 37 Description AN ..40 M5 Account 38 Description AN ..40 M6 Account 39 Description AN ..40 M7 Account 40 Description AN ..40 M8 Account 41 Description AN ..40 M9 Account 42 Description AN ..40 MA Account 43 Description AN ..40 MB Account 44 Description AN ..40 MC Account 45 Description AN ..40 MD Account 46 Description AN ..40 ME Account 47 Description AN ..40 MF Account 48 Description AN ..40 MG Account 49 Description AN ..40 MH Account 50 Description AN ..40 MI Account 51 Description AN ..40 MJ Account 52 Description AN ..40 BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 264 Data element definitions Tag 01: Card data source updates and inquiries – Card Account Multibyte subtags Subtag Description Format MK Account 53 Description AN ..40 ML Account 54 Description AN ..40 MM Account 55 Description AN ..40 MN Account 56 Description AN ..40 MO Account 57 Description AN ..40 MP Account 58 Description AN ..40 MQ Account 59 Description AN ..40 MR Account 60 Description AN ..40 MS Account 61 Description AN ..40 MT Account 62 Description AN ..40 MU Account 63 Description AN ..40 MV Account 64 Description AN ..40 MW Account 65 Description AN ..40 MX Account 66 Description AN ..40 MY Account 67 Description AN ..40 MZ Account 68 Description AN ..40 N0 Account 69 Description AN ..40 N1 Account 70 Description AN ..40 N2 Account 71 Description AN ..40 N3 Account 72 Description AN ..40 N4 Account 73 Description AN ..40 N5 Account 74 Description AN ..40 N6 Account 75 Description AN ..40 N7 Account 76 Description AN ..40 N8 Account 77 Description AN ..40 N9 Account 78 Description AN ..40 NA Account 79 Description AN ..40 NB Account 80 Description AN ..40 Card Account Multibyte subtag — two-character hexadecimal display format Binary data to be carried in the Card Account Multibyte subtags must be represented using a two-character hexadecimal display format. The following diagram illustrates how packed binary data—as it would be carried in the Card Account Multibyte data source—would need to be converted to ASCII two-character hexadecimal display format for carrying in the subtags. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 265 Data element definitions The conversion can be thought of in two steps. The first step converts the binary data to single-character hexadecimal equivalents (in four-bit nibbles). Then, the resulting single-character hexadecimal values are converted to two-character hexadecimal display values that can be carried in the subtags. In this case, the specified 48 bits of binary data would need to be added to the subtags as the specified 24 bytes of data. In this example, the binary data is converted to ASCII values, although they could be converted to EDCDIC values instead depending on the formats you use. BASE24-eps reverses the process to derive the binary data from the subtags for storage in the Card Account Multibyte data source. The following is a conversion table for converting 4-bit binary values to single-character hexadecimal equivalents (as shown in step 1 of the example above). The following is a conversion table for converting single-character hexadecimal values to two-character hexadecimal display equivalents (as shown in step 2 of the example above). BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 266 Data element definitions The following is a conversion table for converting 4-bit binary values directly to their two-character hexadecimal equivalents (combining steps 1 and 2). S-72: Tag 02, Positive Balance Data Source Updates Format: Variable based on the subtags included TDEs: Data Record Tag 02 contains fields in the Positive Balance data source (Positive_Balance) to be updated in a file action request message sent from the ISO 93 host to the BASE24-eps system. Inclusion of subtags depends on the type of update function being performed. Function Required subtags Add Subtags must be supplied for any data source fields that need to be set to specific values. Data source fields not included will be set to default values in the new record. Replace The replace function is handled as an add or change function depending on the situation. If a specified record does not exist, the function is treated as an add. If a specified record does exist, the function is treated as an update. Subtags should be supplied accordingly. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 267 Data element definitions Function Required subtags Update Subtags need only be supplied for those fields in a record to be updated. If a subtag is not supplied, the corresponding field in the record is not affected. To remove a specific field value, include the applicable subtag set to the appropriate default value. This will update the corresponding field in the record to the supplied default values. Delete Subtags 01 (Account Number) and 02 (Account Type) are required. Subtag definitions Subtag definitions are provided below for all of the subtags that can be carried in this tag. The subtags have been grouped as follows: • • • Basic Positive Balance Subtags CSM Buffer Subtag Positive Balance Limit Subtags Subtag definitions – basic Positive Balance subtags The following is a list of basic Positive Balance subtags. Data length and type is provided for each. Tag 02: Positive Balance data source updates – basic Positive Balance subtags Subtag 01 Description Account Number Format AN 28 The account number of the record to be updated in the Positive_Balance. 02 Account Type AN 2 A user-defined code identifying the type of account. This value must match the account type defined for the account in the Card data source (Card). Examples include 10–19 for checking accounts, 30–39 for credit accounts, and 20–29 for savings accounts. 03 Account Category AN 1 A code indicating whether this account is a debit or credit account. Valid values are as follows: 0 = Debit account 1 = Credit account This field defaults to 0. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 268 Data element definitions Tag 02: Positive Balance data source updates – basic Positive Balance subtags Subtag 04 Description Account Status Format N2 A code indicating the current status of the account. Currently defined values are 00–15, which indicate that the account is open and will be included in open account relationship (OAR) account selection if applicable, and 90, which indicates that the account is closed. All other account status values are user defined. To specify a change date to be associated with this status, subtag 12 must be included. This field defaults to spaces. 05 Currency Code N3 A three-digit ISO 4217 code (e.g., 840 for U. S.) indicating the currency of an amount if an amount is present in any of the following fields. This field is required if any of these fields contain an amount. This field defaults to all zeros. 06 Available Balance Start N 12 The start-of-day available balance (for a debit account). The decimal point is implied based on the currency code. This field defaults to all zeros. 07 Ledger Balance Start N 12 The start-of-day ledger balance (for a debit account). The decimal point is implied based on the currency code. This field defaults to all zeros. 08 Available Credit Start N 12 The start-of-day available credit (for a credit account). The decimal point is implied based on the currency code. This field defaults to all zeros. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 269 Data element definitions Tag 02: Positive Balance data source updates – basic Positive Balance subtags Subtag 09 Description Credit Limit Amount Format N 12 The credit limit for a credit account. The decimal point is implied based on the currency code. This field defaults to all zeros. 11 Limit Profile AN 16 The limit profile assigned to this account. The limit profile is used as part of the key to the Limits data source (Limits). This field defaults to all spaces. 12 Account Status Change Date N 12 The date and time, in YYMMDDhhmmss format (Greenwich Mean Time), the status of this account was last changed. You can include this subtag in conjunction with subtag 04 to specify a specific status change date. If this subtag is not included, but subtag 04 is, the status change date will be set to the current system time. If subtag 04 is not included, this subtag is ignored. This field defaults to the current system date. 13 Start-of-Day Balance Date N8 The date, in YYYYMMDD format, of the start-of-day available balance for a debit account. This field defaults to the current system date. This field defaults to the current system date. 14 Ledger Balance Start Date N8 The date, in YYYYMMDD format, of the start-of-day ledger balance for a debit account. This field defaults to the current system date. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 270 Data element definitions Tag 02: Positive Balance data source updates – basic Positive Balance subtags Subtag 15 Description Available Credit Start Date Format N8 The date, in YYYYMMDD format, of the start-of-day available balance for a credit account. This field defaults to the current system date. 16 Last Deposit Amount N 12 The amount of the last deposit to this account. This field defaults to all zeros. 17 Last Deposit Date N 12 The date, in YYMMDDhhmmss format, of the last deposit to this account. This field defaults to the current system date. 18 Last Withdrawal Amount N 12 The amount of the last withdrawal from this account. This field defaults to all zeros. 19 Last Withdrawal Date N 12 The date, in YYMMDDhhmmss format, of the last withdrawal from this account. This field defaults to the current system date. 20 Cash Advance Minimum N6 The minimum cash advance amount, in whole currency units (e.g., U. S. dollars), allowed for this account. A value of 0 in this field indicates that no minimum is used. This field defaults to all zeros. 21 Cash Advance Increment N6 The standard increment, in whole currency units, (e.g., U. S. dollars), over the minimum cash advance amount. This field defaults to all zeros. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 271 Data element definitions Tag 02: Positive Balance data source updates – basic Positive Balance subtags Subtag 22 Description Interest Accrued Current Format N 12 The current amount of accrued interest on this account. This field defaults to all zeros. 23 Interest Accrued Year to Date N 12 The year-to-date amount of accrued interest on this account. This field defaults to all zeros. 24 Minimum Payment Amount N 12 The current minimum payment due for the next payment on this account. This field defaults to all zeros. 25 Next Payment Date N 12 The date, in YYMMDDhhmmss format, the next payment is due for this account. This field defaults to the current system date. 56 Fee Profile AN 16 A fee profile for this account. This profile is used as part of the primary key to the Fee data source (Fees). The Fees is used to calculate a fee for a transaction for a specified fee profile and fee name. This field is reserved for future use. This field defaults to all spaces. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 272 Data element definitions Tag 02: Positive Balance data source updates – basic Positive Balance subtags Subtag 63 Description Intra-Day Available Balance Start Date Format AN 8 The starting calendar date (in GMT YYYYMMDD format) for the transactions contained in the account's Balance_Impacts record that should be retained in the Usages data source for current intra-day balance calculations. In other words, it is the date on which the host stopped collecting transaction activity for inclusion in the refreshed available balance (for a debit account). This could be either the date of the latest extract or the date of a Real Time Feedsubmitted transaction chosen by the host to be the last one included in the refreshed balance. This field defaults to all spaces. 64 Intra-Day Available Balance Start Time N4 The starting time (in HHMM format) for the transactions contained in the account's Balance_Impacts record that should be retained in the Usages data source for current intra-day balance calculations. In other words, it is the time at which the host stopped collecting transaction activity for inclusion in the refreshed available balance (for a debit account). This could be either the time of the latest extract or the time of a Real Time Feedsubmitted transaction chosen by the host to be the last one included in the refreshed balance. This field defaults to all zeros. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 273 Data element definitions Tag 02: Positive Balance data source updates – basic Positive Balance subtags Subtag 65 Description Intra-Day Ledger Balance Start Date Format AN 8 The starting calendar date (in GMT YYYYMMDD format) for the transactions contained in the account's Balance_Impacts record that should be retained in the Usages data source for current intra-day balance calculations. In other words, it is the date on which the host stopped collecting transaction activity for inclusion in the refreshed ledger balance (for a debit account). This could be either the date of the latest extract or the date of a Real Time Feed-submitted transaction chosen by the host to be the last one included in the refreshed balance. This field defaults to all spaces. 66 Intra-Day Ledger Balance Start Time N4 The starting time (in HHMM format) for the transactions contained in the account's Balance_Impacts record that should be retained in the Usages data source for current intra-day balance calculations. In other words, it is the time at which the host stopped collecting transaction activity for inclusion in the refreshed ledger balance (for a debit account). This could be either the time of the latest extract or the time of a Real Time Feed-submitted transaction chosen by the host to be the last one included in the refreshed balance. This field defaults to all zeros. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 274 Data element definitions Tag 02: Positive Balance data source updates – basic Positive Balance subtags Subtag 67 Description Intra-Day Available Credit Start Date Format AN 8 The starting calendar date (in GMT YYYYMMDD format) for the transactions contained in the account's Balance_Impacts record that should be retained in the Usages data source for current intra-day balance calculations. In other words, it is the date on which the host stopped collecting transaction activity for inclusion in the refreshed available credit (for a credit account). This could be either the date of the latest extract or the date of a Real Time Feed-submitted transaction chosen by the host to be the last one included in the refreshed balance. This field defaults to all spaces. 68 Intra-Day Available Credit Start Time N4 The starting time (in HHMM format) for the transactions contained in the account's Balance_Impacts record that should be retained in the Usages data source for current intra-day balance calculations. In other words, it is the time at which the host stopped collecting transaction activity for inclusion in the refreshed available credit (for a credit account). This could be either the time of the latest extract or the time of a Real Time Feed-submitted transaction chosen by the host to be the last one included in the refreshed balance. This field defaults to all zeros. Subtag definitions – CSM buffer subtag The following is the CSM buffer subtag for the Positive Balance data source. Data length and type is provided. CSM buffers are variable-length buffers for custom software modifications (CSMs). CSM buffers must begin with a three-digit length prefix indicating the length of the data to follow (i.e., CSM buffers are formatted as <LLL><data>). For example, subtag 10 carrying 9 bytes of actual CSM data would be formatted as <subtag><subtag data length><csm data length> <csm data>. Example: 10012009123456789 BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 275 Data element definitions The length of a CSM buffer (when added to the other included subtag fields) cannot exceed allowable maximums for the message and data elements. Tag 02: Positive Balance data source updates – CSM buffer subtag Subtag Description 10 CSM Buffer - Positive Balance Data Source Format AN ..999 (including the 3-digit length prefix) A variable-length buffer for custom software modifications (CSMs) to the Positive Balance data source. The data in this buffer cannot contain any embedded binary values. Note: The Positive Balance CSM buffer can be placed in S-72 tag 02 or S-127 tag 12, but not in both.TDE Storage: If S-127 tag 12 is present in the file update message, the PBAL CSM buffer from that tag is stored in the PBAL CSM Buffer TDE. In this case, if the PBAL CSM buffer subtag 10 is also present in S-72 tag 02, the subtag 10 buffer information is not saved. Positive Balance limit definitions The fields described in the following table are standard fields for each of the six limits that can be associated with a Positive Balance data source. The subtags representing these fields are included following the table. Field definitions Limit Name – The name assigned to the specified limit for the account. Limit Maximum – The maximum count or amount limit assigned to the corresponding limit name. For an amount limit, the decimal point is implied based on the currency code of the limit. Limit Currency Code – The currency code associated with the limit amount for the corresponding limit name. If the limit is a count, you must set the corresponding currency code field to all zeros. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 276 Data element definitions Field definitions Limit Period – A code specifying the usage period for the corresponding limit. Valid values are as follows: 0 = Usages not cleared. 1 = Fixed number of days. (Default) 2 = One week. 3 = Two weeks. 4 = First and fifteenth of each month. 5 = Every month. 6 = Every three months. 7 = Every six months. 8 = Every year. 9 = Daily, except for Saturdays, Sundays, and holidays. 10 = Daily, except for Sundays and holidays. 11 = Daily, except for Saturdays and holidays. 12 = Fixed number of hours. 20 = Rolling number of minutes. 21 = Rolling number of 2-minute intervals. 22 = Rolling number of hours. 23 = Rolling number of days. 24 = Rolling number of weeks. 25 = Rolling number of months. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 277 Data element definitions Field definitions Limit Period Additional Data – A value further defining the usage period value for the corresponding limit.If the corresponding Limit Period field is set to a value of 1, this field specifies the number of days for the usage period. The default is three days. If the corresponding Limit Period field is set to a value of 2 or 3, this field indicates the day of the week on which the usage period begins. Valid values are as follows: 1 = Sunday (Default) 2 = Monday 3 = Tuesday 4 = Wednesday 5 = Thursday 6 = Friday 7 = Saturday If the corresponding Limit Period field is set to a value of 5, 6, 7, or 8, this field indicates the day of the month on which the usage period begins. Valid values are 1–28. The default is 1. If the corresponding Limit Period field is set to a value of 12, this field specifies the number of hours for the usage period. Valid values are 1–999. The default is 6. If the corresponding Limit Period field is set to a value of 20, 21, 22, 23, 24 or 25, this field indicates the number of usage accumulation periods associated with the selected rolling limit usage period. Valid values are 1 - 30. If the corresponding Limit Period field is set to a value of 4, 9, 10, or 11, this field does not apply. Limit Expiration Date – The date, in YYYYMMDD format, on which the corresponding limit expires. A value of all spaces in this field indicates that the corresponding limit does not have an expiration date. Subtag definitions – Positive Balance limit subtags The following is a list of Positive Balance limit subtags. Data length and type is provided for each. Tag 02: Positive Balance data source updates – Positive Balance limits subtags Subtag Description Format 26 Limit 1 Name 27 Limit 1 Maximum 28 Limit 1 Currency Code N3 29 Limit 1 Period N2 30 Limit 1 Period Additional Data N3 57 Limit 1 Expiration Date N8 31 Limit 2 Name 32 Limit 2 Maximum 33 Limit 2 Currency Code N3 34 Limit 2 Period N2 35 Limit 2 Period Additional Data N3 BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 AN 16 N 12 AN 16 N 12 278 Data element definitions Tag 02: Positive Balance data source updates – Positive Balance limits subtags Subtag Description Format 58 Limit 2 Expiration Date N8 36 Limit 3 Name 37 Limit 3 Maximum 38 Limit 3 Currency Code N3 39 Limit 3 Period N2 40 Limit 3 Period Additional Data N3 59 Limit 3 Expiration Date N8 41 Limit 4 Name 42 Limit 4 Maximum 43 Limit 4 Currency Code N3 44 Limit 4 Period N2 45 Limit 4 Period Additional Data N3 60 Limit 4 Expiration Date N8 46 Limit 5 Name 47 Limit 5 Maximum 48 Limit 5 Currency Code N3 49 Limit 5 Period N2 50 Limit 5 Period Additional Data N3 61 Limit 5 Expiration Date N8 51 Limit 6 Name 52 Limit 6 Maximum 53 Limit 6 Currency Code N3 54 Limit 6 Period N2 55 Limit 6 Period Additional Data N3 62 Limit 6 Expiration Date N8 AN 16 N 12 AN 16 N 12 AN 16 N 12 AN 16 N 12 S-72: Tag 04, Negative File Updates (Star Systems and Visa DPS) Format: AN 69 TDEs: Data Record Tag 04 contains fields that allow the BASE24‑eps system to notify Star Systems or Visa DPS of a card to be added, updated, or deleted in the negative file. The PAN for the card must also be present in data element P-2 BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 279 Data element definitions and the card sequence number, if applicable, in P-23 of the message. The structure of the data in this tag is as follows. Tag 04: Negative File Updates (Star Systems and Visa DPS) Position 1–2 Description Response Code Format AN 2 A code indicating the outcome of the negative file update request. Valid values are as follows: 24 = File update not supported by receiver 25 = Unable to locate record on file 26 = Duplicate file update record 27 = File update edit error 28 = File update file locked out 29 = File update not successful, contact acquirer 3–42 Issuer Transport Data AN 40 The following issuer transport data must be left-justified and blank filled to the right. The content and format of issuer transport data varies, depending on how Star Systems or Visa DPS sends or uses this data. Star Interchange: The following is the definition for positions 3–42 to be used for Star negative file update messages being sent to Visa on behalf of the card issuer. For more information, refer to Star Systems’ ISO 8583 Processor Interface Specifications. 3–4 Negative File Identifier AN 2 Must be set to a value of NE. 5–8 Expiration Date AN 4 The expiration date in YYMM format. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 280 Data element definitions Tag 04: Negative File Updates (Star Systems and Visa DPS) Position 9–10 Description Action Code Format AN 2 A code indicating the type of action to be taken by the acquirer. Valid values are as follows: 04 = Pick up card 05 = Do not honor 07 = Pick up card, special condition 11 = Approval for VIP 41 = Lost card, pick up 43 = Stolen card, pick up BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 281 Data element definitions Tag 04: Negative File Updates (Star Systems and Visa DPS) Position 11–19 Description Region Code Format AN 9 The regions in which the card is to be listed on the negative file. Values must be left-justified. Valid values are as follows: 0 = Do not list in any Combined Warning Bulletin or any Card Recovery Bulletin (CRB) (most common for U.S.) A = Includes all countries in AsiaPacific region B = Africa and part of the Middle East (includes countries that are part of Visa sub-regions 3 and 5 of the Europe, Middle East, and Africa regions) C = All Canadian CRB regions (regions 1–3) D = National CRB indicator (no longer valid, use 0) E = Europe and part of the Middle East (includes countries in Europe, Middle East, and Africa region not classified as part of CRB region B above) F = Includes all countries in Latin America region X = All Canadian CRB regions (regions 1–9) Y = All non-U.S. CRB regions (regions A, B, C, E, and F) Z = All CRB regions 20–25 Cardholder Spending Amount Limit AN 6 The cumulative dollar limit for this card for one day. This field must be zero-filled for requests with an action code other than 11 (Approval for VIP). For requests with an action code of 11 (Approval for VIP), this field must contain amounts in whole dollars (e.g., 5000 for $5,000.00). BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 282 Data element definitions Tag 04: Negative File Updates (Star Systems and Visa DPS) Position 26–27 Description Cardholder Spending Count Limit Format AN 2 The cumulative number of transactions allowed for this card for one day. This field must be zerofilled for requests with an action code other than 11 (Approval for VIP). For requests with an action code of 11 (Approval for VIP), this field must contain a count (e.g., 6 for 6 transactions). 28–42 43 Filler File Update AN 15 AN 1 A code indicating the action to take on this card. Valid values are as follows: 0 = Unassigned 1 = Add record 2 = Change record 3 = Delete record 4 = Bulk replacement (not supported) 5 = Inquiry 6 = Purge existing records (not supported) 7 = Add file (not supported) 8 = Delete file (not supported) 9 = Unassigned A–F = Reserved for ISO use G–N = Reserved for national use O–Z = Reserved for private use 44–53 Authorization Agent ID Code AN 10 The issuer institution’s nine-digit routing and transit number or issuer identification number, followed by a check digit. BASE24‑eps adds a preceding 1 to this value before it is sent for a total of 11 bytes. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 283 Data element definitions Tag 04: Negative File Updates (Star Systems and Visa DPS) Position Description 54–69 Format Interface Name AN 16 The name of the Star or Visa DPS interface as configured on the BASE24‑eps system. This field is optional and must be space-filled if it is not used. S-72: Tag 05, Visa Stop Payment Order Format: Variable based on the subtags included TDEs: Data Record Tag 05 contains fields that allow the BASE24‑eps system to forward stop payment orders received from the ACI Payments Management product (using the BASE24‑eps ISO 93 Host Interface) to Visa (using the VisaNet Interface). The structure of the data in this tag is as follows. Tag 05: Visa Stop Payment Order Subtag 01 Description Transaction ID Format N 15 A unique transaction ID provided by Visa for submitted stop payment orders. This field is required for a request to change, delete, replace, or inquire on an existing stop payment order (i.e., the Function Code (P-24) data element is set to a value of 302–305). This field is not required for a request to add a stop payment order (i.e., the Function Code (P-24) data element is set to a value of 301). BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 284 Data element definitions Tag 05: Visa Stop Payment Order Subtag 02 Description Merchant Verification Value Format AN 10 The merchant verification value (MVV) of the merchant for which recurring or installment payments will be stopped. The MVV should be provided in a prior recurring or installment payment transaction for the cardholder. This field is required to add or replace a stop payment order for a recurring or installment payment (i.e., the Function Code (P-24) data element is set to a value of 301 or 304) if the Card Acceptor Identification Code (P-42) and the Card Acceptor Name/Location (P-43) data elements are not present.This field is not allowed if subtag 04, Type of Stop Order, is set to a value of R3 (Revocation of all authorizations). 03 Purge Date N6 The date, in YYMMDD format, the cardholder record is to be purged from the Visa Portfolio File in the VIP Cardholder database. This field is required to add or replace a stop payment order (i.e., the Function Code (P-24) data element is set to a value of 301 or 304). This field is not required to delete or inquire on an existing stop payment order (i.e., the Function Code (P-24) data element is set to a value of 303 or 305). BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 285 Data element definitions Tag 05: Visa Stop Payment Order Subtag 04 Description Type of Stop Order Format AN 2 A code indicating the type of stop payment order. Valid values are as follows: R0 = Stop a specific payment. R1 = Revoke authorization for further payments. R3 = Revoke all authorizations. This field is required to add or replace a stop payment order (i.e., the Function Code (P-24) data element is set to a value of 301 or 304). 05 Cardholder Name AN 1–23 The name of the cardholder for this stop payment order. This field is optional. 06 Merchant Account Number AN 1–27 The merchant account number for this stop payment order. This field is optional. 07 File Maintenance Error Code N4 A four-digit file maintenance error code. This field is returned by Visa in the response. Refer to appendix B of the V.I.P. System BASE I Technical Specifications, Volume 2, for descriptions of all possible file maintenance error codes. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 286 Data element definitions Tag 05: Visa Stop Payment Order Subtag Description 08 Format SMS Network ID AN 4 An optional code that specifies the network used for transmitting the message, which determines the program rules that apply to the transaction. Valid values are as follows: 0000 = Generic file update 0002 = Visa card programs 0003 = Interlink 0004 = Plus If this subtag is not provided or contains spaces, the message is processed using the Visa BASE 1 program. S-72: Tag 06, Visa Card Recovery Bulletin Format: Variable based on the subtags included TDEs: Data Record Tag 06 contains fields that allow the BASE24‑eps system to notify Visa of a lost, stolen, or misused card to be listed in BASE I and SMS Exception files for Visa’s Automatic Cardholder Database Update (Auto-CDB) Service. The PAN for the card must also be present in either data element P-2 or P-34 of the message. The structure of tag 06 is as follows. Subtag 01 Description File Name Format AN 2 A code identifying the VIC-resident cardholder file to be accessed by a file update or inquiry, and the update or inquiry request format. This subtag is applicable for the Enhanced Auto-CDB Service only. Valid values are as follows: E2 = BASE I Exception File E3 = BASE I and SMS Exception File E4 = SMS Exception File E9 = BASE I Exception File (for use by Canadian issuers only) BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 287 Data element definitions Subtag 02 Description Purge Date Format N6 The optional date, in YYMMDD, the record is to be purged from the exception file. 03 Action Code AN 2 A code that determines the response and the special (STIP) handling required when the BASE I System at the VIC performs standin authorization on the issuer’s behalf. Valid values are as follows: 01 = Refer to card issuer 04 = Pick up card—non-fraud 05 = Do not honor 07 = Pick up card—fraud 11 = Approval for VIP 41 = Pick up card—lost card—fraud 43 = Pick up card—stolen card— fraud A1–A9 = VIP codes XA, XD = Forward to issuer codes BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 288 Data element definitions Subtag Description 04 Region Codes Format AN 9 One or more (up to nine) CRB region codes that define the distribution of a Visa cardholder account number in CRB files and bulletins. Valid region codes are as follows: A = Asia/Pacific B = Asia/Mid-East C = Canada E = Europe/Mid-East F = Latin America X = All U.S. regions (1–9) Y = All non-U.S. regions (A–F) Z = All regions 1–9 = Specific U.S. regions. These regions do not apply when the File Name field is set to a value of E9. C1–C3X1–X9 = Specific Canadian regions. These regions apply only when the File Name field is set to a value of E9. 05 SMS Network ID AN 4 An optional code that specifies the network used for transmitting the message, which determines the program rules that apply to the transaction. Valid values are as follows: 0000 = Generic file update 0002 = Visa card programs 0003 = Interlink 0004 = Plus If this subtag is not provided or contains spaces, the message is processed using the Visa BASE 1 program. S-72: Tag 07, Banknet File Updates Format: Variable based on the subtags included TDEs: Data Record BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 289 Data element definitions Tag 07 contains fields that allow the BASE24-eps system to send file updates to the Banknet interchange. The structure of tag 07 is as follows. For more information on Banknet file update messages and the contents of this tag, refer to the Banknet message documentation. Tag 07: Banknet File Updates Subtag 01 Description File Name – Name of the Banknet file to be updated. Format AN 6 Banknet File Update Message: This field maps to data element 101 (File Name). 02 File Update Code N1 Banknet File Update Message: This field maps to data element 91 (Issuer File Update Code). 03 Security Code N5 Banknet File Update Message: This field maps to data element 92 (File Security Code). 04 Entry Reason N1 Banknet File Update Message: This field maps to the Entry Reason subelement in data element 120 (Record Data). 05 Customer ID N6 Banknet File Update Message: This field maps to the Customer ID subelement in data element 120 (Record Data). 06 Card Program AN 3 Banknet File Update Message: This field maps to the Card Program subelement in data element 120 (Record Data). 07 Response Code N2 Banknet File Update Message: This field maps to data element 39 (Response Code). BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 290 Data element definitions Tag 07: Banknet File Updates Subtag 08 Description VIP Accumulative Limit Format N 12 Banknet File Update Message: This field maps to data element 120 (Record Data), subelement 6 (Premium Listing Accumulative Limit) in the MCC102 Stand-In Account File format. 09 VIP Limit Currency Code N3 Banknet File Update Message: This field maps to data element 120 (Record Data), subelement 7 (Premium Listing Limit Currency Code) in the MCC102 Stand-In Account File format. 10 Region 1 AN 1 Banknet File Update Message: This field maps to data element 120 (Record Data), subelement 7 (Region) in the MCC104 Local Stoplist File format. 11 Region 1 Purge Date N6 Banknet File Update Message: This field maps to data element 120 (Record Data), subelement 10 (Purge Date) in the MCC104 Local Stoplist File format. 12 Region 1 Country AN 3 Banknet File Update Message: This field maps to data element 120 (Record Data), subelement 8 (Country) in the MCC104 Local Stoplist File format. 13 Region 1 Subcountry AN 2 Banknet File Update Message: This field maps to data element 120 (Record Data), subelement 9 (Subcountry) in the MCC104 Local Stoplist File format. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 291 Data element definitions Tag 07: Banknet File Updates Subtag Description Format Subtags 14–17 carry applicable values for the second region in which the account is to be listed. Accounts can be listed in up to six regions. Banknet File Update Message: These fields map to data element 120 (Record Data), subelements 11–14 in the MCC104 Local Stoplist File format. 14 Region 2 AN 1 15 Region 2 Purge Date 16 Region 2 Country AN 3 17 Region 2 Subcountry AN 2 18 Region 3 AN 1 19 Region 3 Purge Date 20 Region 3 Country AN 3 21 Region 3 Subcountry AN 2 22 Region 4 AN 1 23 Region 4 Purge Date 24 Region 4 Country AN 3 25 Region 4 Subcountry AN 2 N6 Subtags 18–21 carry applicable values for the third region in which the account is to be listed. Accounts can be listed in up to six regions. Banknet File Update Message: These fields map to data element 120 (Record Data), subelements 15–18 in the MCC104 Local Stoplist File format. N6 Subtags 22–25 carry applicable values for the fourth region in which the account is to be listed. Accounts can be listed in up to six regions. Banknet File Update Message: These fields map to data element 120 (Record Data), subelements 19–22 in the MCC104 Local Stoplist File format. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 N6 292 Data element definitions Tag 07: Banknet File Updates Subtag Description Format Subtags 26–29 carry applicable values for the fifth region in which the account is to be listed. Accounts can be listed in up to six regions. Banknet File Update Message: These fields map to data element 120 (Record Data), subelements 23–26 in the MCC104 Local Stoplist File format. 26 Region 5 AN 1 27 Region 5 Purge Date 28 Region 5 Country AN 3 29 Region 5 Subcountry AN 2 30 Region 6 AN 1 31 Region 6 Purge Date 32 Region 6 Country AN 3 33 Region 6 Subcountry AN 2 34 Last Update Activity - Date N6 Subtags 30–33 carry applicable values for the sixth region in which the account is to be listed. Accounts can be listed in up to six regions. Banknet File Update Message: These fields map to data element 120 (Record Data), subelements 27–30 in the MCC104 Local Stoplist File format. N6 N6 Banknet File Update Message: This field maps to the Date-Last-Update Activity subelement in data element 120 (Record Data). 35 Last Update Activity - Time N4 Banknet File Update Message: This field maps to the Time-Last-Update Activity subelement in data element 120 (Record Data). 36 Banknet File Update Error Code N6 Banknet File Update Message: This field maps to data element 44 (Additional Response Data). BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 293 Data element definitions Tag 07: Banknet File Updates Subtag Description 37 Purge Date Format N8 Banknet File Update Message: This field maps to data element 120 (Record Data), subelement 8 (Issuer-defined Purge Date) in the MCC102 Stand-In Account File format. 38 Card Sequence Number N3 Banknet File Update Message: This field maps to data element 120 (Record Data), subelement 9 (Card Sequence Number) in the MCC102 Stand-In Account File format. 39 Card Expiration Date N6 Banknet File Update Message: This field maps to data element 120 (Record Data), subelement 10 (Card Expiration Date) in the MCC102 Stand-In Account File format. 40 Acquirer ID N6 Banknet File Update Message: This field maps to data element 120 (Record Data), subelement 4 (Acquirer ID) in the MCC105 Recurring Payment Cancellation Service format. 41 Card Acceptor AN 15 Banknet File Update Message: This field maps to data element 120 (Record Data), subelement 5 (Card Acceptor ID Code) in the MCC105 Recurring Payment Cancellation Service format. 42 Transaction Amount (Low) N 12 Banknet File Update Message: This field maps to data element 120 (Record Data), subelement 6 (Transaction Amount (Low)) in the MCC105 Recurring Payment Cancellation Service format. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 294 Data element definitions Tag 07: Banknet File Updates Subtag 43 Description Transaction Amount (High) Format N 12 Banknet File Update Message: This field maps to data element 120 (Record Data), subelement 7 (Transaction Amount (High)) in the MCC105 Recurring Payment Cancellation Service format. 44 Low PAN AN 19 Banknet File Update Message: This field maps to data element 120 (Record Data), subelement 1 (Primary Account Number (Low PAN)) in the MCC105 Recurring Payment Cancellation Service format. 45 High PAN AN 19 Banknet File Update Message: This field maps to data element 120 (Record Data), subelement 2 (Primary Account Number (High PAN)) in the MCC107 MasterCard Enhanced Value Platform File format. 46 Account Category AN 1 Banknet File Update Message: This field maps to data element 120 (Record Data), subelement 3 (Account Category) in the MCC107 MasterCard Enhanced Value Platform File format. 47 Program ID AN 6 Banknet File Update Message: This field maps to data element 120 (Record Data), subelement 5 (Program ID) in the MCC107 MasterCard Enhanced Value Platform File format. 48 Product Code AN 3 Banknet File Update Message: This field maps to data element 120 (Record Data), subelement 3 (Graduated Product Code) in the MCC108 MasterCard Product Graduation File format. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 295 Data element definitions Tag 07: Banknet File Updates Subtag 49 Description PayPass Account Number Format AN 19 Banknet File Update Message: This field maps to data element 120 (Record Data), subelement 1 (PayPass Account Number) in the MCC106 PayPass Mapping File format. 50 PayPass Replacement Account Number AN 19 Banknet File Update Message: This field maps to data element 120 (Record Data), subelement 4 (PayPass Account Number (Replacement)) in the MCC106 PayPass Mapping File format. 51 PayPass Replacement PAN AN 19 Banknet File Update Message: This field maps to data element 120 (Record Data), subelement 5 (PAN (Replacement)) in the MCC106 PayPass Mapping File format. 54 Mapping File Indicator AN 1 Banknet File Update Message: This field maps to data element 120 (Record Data). subelement 1(Mapping File Indicator) in the MCC106 PAN Mapping File format for Issuer File Update Request/0302 Messages associated with the MasterCard Digital Enablement Service (MDES) requesting a replacement PAN. 55 Replacement PAN ANS 19 Banknet File Update Message: This field maps to data element 120 (Record Data). subelement 2 (Replacement PAN) in the MCC106 PAN Mapping File format for Issuer File Update Request/0302 Messages associated with the MasterCard Digital Enablement Service (MDES) requesting a replacement PAN. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 296 Data element definitions Tag 07: Banknet File Updates Subtag 56 Description Replacement PAN Expiration Date Format N4 Banknet File Update Message: This field maps to data element 120 (Record Data). subelement 3 (Replacement PAN Expiration Date) in the MCC106 PAN Mapping File format for Issuer File Update Request/0302 Messages associated with the MasterCard Digital Enablement Service (MDES) requesting a replacement PAN. 57 Primary Account Card Sequence Number ANS 3 Banknet File Update Message: This field maps to data element 120 (Record Data). subelement 4 (Primary Account Card Sequence Number) in the MCC106 PAN Mapping File format for Issuer File Update Request/0302 Messages associated with the MasterCard Digital Enablement Service (MDES) requesting a replacement PAN. 58 Notify Wallet Service Provider Indicator N1 Banknet File Update Message: This field maps to data element 120 (Record Data). subelement 5 (Notify Wallet Service Provider Indicator) in the MCC106 PAN Mapping File format for Issuer File Update Request/0302 Messages associated with the MasterCard Digital Enablement Service (MDES) requesting a replacement PAN. 59 Token AN 19 Banknet File Update Message: This field maps to data element 120 (Record Data). subelement 6 (Token) in the MCC106 PAN Mapping File format for Issuer File Update Request/0302 Messages associated with the MasterCard Digital Enablement Service (MDES) requesting a replacement PAN. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 297 Data element definitions Tag 07: Banknet File Updates Subtag Description 60 Format Action Required Banknet File Update Message: This field maps to data element 120 (Record Data). subelement 2 (Action Required) in the MCC106 PAN Mapping File format for Issuer File Update Request/0302 Messages associated with the MasterCard Digital Enablement Service (MDES) requesting suspension, deactivation, or resumption of an MDES token. S-72: Tag 10, Preauthorization Hold Deletion Information Format: Variable based on the subtags included TDEs: Data Record Tag 10 contains fields that, in conjunction with other data elements, enable the BASE24‑eps system to identify preauthorization holds for deletions. The structure of the data in this tag is as follows. Tag 10: Preauthorization Hold Deletion Information Subtag 01 Description Hold ID Format AN 12 The preauthorization hold ID (sequence number) from the original transaction. This value is used as the hold ID unless the original transaction was a Visa incremental authorization transaction (in which case subtag 03 is used instead). 02 Account Type N2 The account type from the original transaction; required if the hold is on an account. 03 Transaction ID AN 15 The preauthorization hold ID (sequence number) identifying the hold if the original transaction was a Visa incremental authorization transaction. This value is the Visa Transaction ID from Token 17 of the original Visa transaction message. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 298 Data element definitions S-72: Tag 11, RuPay File Updates Format: Variable based on the subtags included TDEs: Data Record TDE Issuer Transport Data TDE Tag 11 contains fields that support RuPay updates to the customer account files. The structure of the data in this tag is as follows. Tag 11: RuPay File Updates Subtag Description 01 File Update Code 02 File Name Format AN 1 ANS...17 This subtag is optional. 03 File Maintenance Code AN 2 04 Message Type Function AN 1 05 Message Type Transition Mode AN 1 06 Action Code AN 2 S-72: Tag 13, AEGN Negative File Updates Format: Variable based on the subtags included TDEs: Data Record Tag 13, AEGN Negative File Updates, contains no data. The presence of tag 13 in S-72 indicates a file update from the host to the AEGN Network Exception File maintained by American Express Global Network Solutions (AEGN). The PAN for the card must also be present in data element P-2 of the message as well as the following data elements: • • • • The function code in the Function Code (P-24) data element indicates whether a card is to be added, updated, or deleted in the AEGN Network Exception File. The Message Reason Code (P-25) data element indicates the status to be added to or removed from a card in the AEGN Network Exception File. The Date, Expiration (P-14) data element contains the date on which the card record is to be removed from the AEGN Network Exception File. The Forwarding Institution ID Code (P-33) data element contains the organization identifier. S-72: Tag 14, NYCE Negative File Updates Format: Variable based on the subtags included TDEs: Data Record Tag 14 contains fields that allow the BASE24‑eps system to notify NYCE Payment Systems of a card to be added, updated, or deleted in the NYCE negative file. The PAN for the card must also be present in data element P-2 and the card sequence number, if applicable, in P-23 of the message. The structure of the data in this tag is as follows. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 299 Data element definitions Tag 14: NYCE Negative File Updates Subtag Description 01 Response Code Format AN 2 A code (e.g., 43 for a lost or stolen card) indicating why this card is being added to the NYCE negative file. When performing stand-in processing, NYCE denies transactions for the card with this response code. 02 Authorizing Agent Institution ID Code N 10 A code identifying the institution that issued the card being maintained in the NYCE negative file. 03 Interface Name AN 16 An optional field containing the name of a specific interface to be used to route this file update transaction when multiple interfaces are defined for the NYCE Negative File Update file type on the File Update Router Configuration window. S-72: Tag 15, Fifth Third ISO Interface Response Code Format: Variable based on the subtags included TDEs: Data Record Tag 15, Fifth Third ISO Interface Response Code, contains a two-digit external response code that can be sent as a file update from the ISO host to the Fifth Third ISO Interface. The Fifth Third ISO Interface connects to Fifth Third Bank Processing Solutions, which provides processing for the Armed Forces Financial Network (AFFN), Jeanie network, and the Credit Union 24 (CU24) network. The structure of the data in this tag is as follows. For more information on Fifth Third Bank Processing Solutions file updates and the contents of this tag, refer to the Fifth Third ISO 8583 Message Formats manual. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 300 Data element definitions Tag 15: Fifth Third ISO Interface Response Code Subtag Description 01 Format Response Code N2 The two-digit response code to be used by the Fifth Third ISO Interface when the link between the BASE24‑eps system and Fifth Third Bank Processing Solutions is not available. TDE: This value is mapped to and from the Data Record TDE by the BASE24-eps ISO 93 Host Interface component. The Fifth Third ISO Interface component maps the Data Record TDE value to and from the External Action Code TDE. Interchange Message: This value maps to data element 039 (Response Code) in the Fifth Third card issuer file update message. S-72: Tag 16, SHAZAM Interface File Updates Format: Variable based on the subtags included TDEs: Data Record Tag 16 contains fields that allow the BASE24-eps system to notify the SHAZAM network of a card to be added, updated, or deleted in the SHAZAM positive or negative PAN backup files. These files are used for stand-in authorization processing. The PAN for the card must also be present in data element P-2 of the message. The structure of the data in this tag is as follows. For more information on SHAZAM file updates and the contents of this tag, refer to the SHAZAM ISO 8583 Interface Manual. Tag 16: SHAZAM Interface File Updates Subtag 01 Description PAN Restriction Code Format N2 A two-digit code (e.g., 90 for a hot card) indicating the restrictions to be placed on the card by the SHAZAM interchange. Interchange Message: This field maps to data element 72 (Data Record—File Action Message), subelement 72.5 (PAN Restrictions) in the SHAZAM file update message. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 301 Data element definitions Tag 16: SHAZAM Interface File Updates Subtag Description 02 Debit Action Code Format N2 A two-digit code indicating the debit action for a SHAZAMChek card. Interchange Message: This field maps to data element 123 (Private Use SHAZAMChek Data), subelement 123.2 (Debit Action Codes) in the SHAZAM file update message. 03 Purge Date N6 The date, in YYMMDD format, the card is to be removed from applicable bulletins and exception files—used for Visa or MasterCard SHAZAMChek cards when setting a card status to hot or when updating an existing hot card status. Interchange Message: This field maps to data element 123 (Private Use SHAZAMChek Data), subelement 123.3 (Purge Date) in the SHAZAM file update message. 04 Warning Publication Region AN 5 Up to five one-character codes indicating the warning publication regions in which a Visa or MasterCard SHAZAMChek card with a hot card status is to be listed. Interchange Message: This field maps to data element 123 (Private Use SHAZAMChek Data), subelement 123.1 (Warning Publication Regions) in the SHAZAM file update message. S-72: Tag 17, NETS Negative File Updates Format: Varies based on the subtags included TDEs: Data Record Tag 17 contains fields used to notify NetWorks Systems (NETS) of a card to be added, updated, or deleted in the NETS negative file (NETS stands for Nebraska Electronic Transfer System, Inc. which operates the Network Systems switch network). The NETS negative file is used for stand-in processing when communication is lost between the issuer and NetWorks System. Negative File update messages allow the issuer to maintain the BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 302 Data element definitions Negative File while on-line to NetWorks System. The PAN for the card must also be present in data element P-2 or P-34 and the card sequence number, if applicable, in P-23 of the message. The structure of tag 17 is as follows. For more information on NETS file update messages and the contents of this tag, refer to the Networks ISO Interface Technical Standards manual. Tag 17: NETS Negative File Updates Subtag Description 01 Response Code Format AN 2 The response code NETS is to use when performing stand-in processing, NETS denies transactions for the card with this response code. Interchange Message: This field maps to data element 39 (Response Code) in the NETS file update message. 02 Expiration Date N4 The future date, in YYMM format, on which this card record is to be automatically deleted from the NETS negative file. Interchange Message: This field maps to data element 14 (Expiration Date) in the NETS file update message. 03 Authorizing Agent Institution ID Code N 11 The Authorizing Agent Institution ID Code identifying the institution that issued the card being maintained in the NETS negative file. Interchange Message: This field maps to data element 113 (Authorizing Agent Institution ID Code) in the NETS file update message. S-72: Tag 18, Presto (Publix) Negative File Updates Format: Varies based on the subtags included TDEs: Data Record Tag 18 contains fields used to update the Presto! interchange negative file. The structure of the data in this tag is as follows. For more information on Presto! negative file updates and the contents of this tag, refer to the Presto! ISO Technical Specifications manual. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 303 Data element definitions Note: For add, update, or delete actions on the Presto! interchange negative file, the PAN for the card must also be present in data element P-2 and the card sequence number, if applicable, must be present in P-23 of the message. Tag 18: Presto (Publix) Negative File Updates Subtag Description 01 Action Code Format AN 2 A Presto! ATM or POS response code associated with card. Interchange Message: This field is used to set the capture code subfield in data element S-105 (Addition NEG Information) of the Presto! file update message. The capture code sub-field is set to 1 (capture) for the following action codes: 04 = Capture card 07 = Capture card special condition 41 = Lost card, fraud (pick-up) 43 = Stolen card (pick-up) The capture code sub-field is set to 0 (return card) for any other action codes. 02 Expiration Date N4 The future date, in YYMM format, on which this card record is to be automatically deleted from the Presto! negative file. Interchange Message: This field maps to the record expiration date sub-field in data element S-105 (Addition NEG Information) of the Presto! file update message. S-72: Tag 19, EPOC Interface File Updates Format: Varies based on the subtags included TDEs: Data Record Tag 19 contains file update information for the Enterprise Platform for Online Commerce (EPOC) interface, which is used to access the ACCEL/Exchange network. File update messages are used to change or update the Cardholder Authorization File (CAF)/Debit Authorization File (DAF) records or Authorization Exception File (AEF)/ Debit Exception File (DEF) records maintained by the ACCEL/Exchange network. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 304 Data element definitions The structure of the data in this tag is as follows. For more information on EPOC file updates and the contents of this tag, refer to the EPOC ISO File Action Message addendum to the EPOC ISO 8583 Online Interface Specifications manual. Tag 19: EPOC Interface File Updates Subtag 01 Description Cardholder Record Member Number Format N1 A number from 1 to 9 that is used to differentiate cardholders that have the same PAN. Set this value to 0 (zero) when cardholders share limits. Interchange Message: This field maps to data element 72 (Data Record 1), subelement position 1, of the EPOC file action message. 02 Card Status N9 If member numbers are used for your cardbase, this field should contain an array of codes for up to nine members that indicates the status of the card for each member. The first position in this field represents the card status for the first member, the second position represents the card status for the second member, and so on up to the ninth position for the ninth member. Positions for which no member exists should be filled with a 0. If member numbers are not used for your cardbase, the card status code is in first position and positions 2–9 should be zero-filled. Interchange Message: This field maps to data element 72 (Data Record 1), subelement positions 2 through 10, of the EPOC file action message. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 305 Data element definitions Tag 19: EPOC Interface File Updates Subtag Description 03 PIN Offset Format N4 The four-digit PIN verification value for the card. This subtag is required if the cardholder’s PIN has been changed. Interchange Message: This field maps to data element 72 (Data Record 1), subelement positions 1 through 14, of the EPOC file action message. 04 Card Expiration Date N4 The expiration date of the card in YYMM format. Interchange Message: This field maps to data element 72 (Data Record 1), subelement positions 15 through 18, of the EPOC file action message. 05 Card Capture Code N1 A code indicating whether the card is to be captured (1) or returned (0). Interchange Message: This field maps to data element 72 (Data Record 1), subelement position 19, of the EPOC file action message. 06 Message Reason Code N4 A code that provides the receiver of a request, advice or notification message with the reason, or purpose, of that message. Interchange Message: This field maps to data element 25 (Message Reason Code) of the EPOC file action message. S-72: Tag 20, MDS Dispute Processing Data Format: Variable based on the subtags included TDEs: Data Record Tag 20 contains fields needed to process MasterCard Debit Switch (MDS) dispute transactions (i.e., adjustments, chargebacks, and representments). The structure of tag 20 is as follows. For information on MDS transaction messages, refer to the MDS Online Specifications manual. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 306 Data element definitions Tag 20: MDS Dispute Processing Data Subtag Description 01 Advice Reason Code Format N3 The reason code indicating the general purpose of the MDS advice message. Interchange Message: This field maps to data element 60 (Advice Reason Code), subelement 1, in the MDS transaction message. 02 Advice Reason Detail Code N4 A conditional detail code providing additional specific information regarding the exact purpose of the MDS advice message. Interchange Message: This field maps to data element 60 (Advice Reason Code), subelement 2, in the MDS transaction message. 03 Advice Reason Detail Text AN 53 Optional text, provide supplementary information for the Advice Reason Detail Code. Interchange Message: This field maps to data element 60 (Advice Reason Code), subelement 3, in the MDS transaction message. 04 Original Processing Code N6 The processing code for the transactions. Interchange Message: This field maps to data element 3 (Processing Code) in the MDS transaction message. 05 Additional Advice Reason Text S-72: Tag 21, CO-OP File Updates Format: Variable based on the subtags included TDEs: Data Record Tag 21 contains fields that allow the BASE24‑eps system to send file updates to the CO-OP/eFunds interchange. The structure of tag 21 is as follows. For more information on CO-OP file update messages and the contents of this tag, refer to the eFunds COOP ISO 8583 with Shared Branch PI Specifications manual. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 307 Data element definitions Tag 21: CO-OP File Updates Subtag Description 01 Format Response Code AN 2 The response code used by the processor when a transaction is denied. Interchange Message: This field maps to data element 39 (Response Code) in the CO-OP file update message. 02 Issuer Transport Data AN 40 Interchange Message: This field maps to data element 62 (Issuer Transport Data) in the CO-OP file update message. 03 File Update Code AN 1 A coded indicating the type of file update: add (1), update (2), or delete (3). Interchange Message: This field maps to data element 91 (File Update Code) in the CO-OP file update message. 04 Authorization Agent ID Code AN 10 The institution ID code of the institution that issued the card being maintained. Interchange Message: This field maps to data element 113 (Authorizing Agent Institution ID Code) in the CO-OP file update message. 05 Interface Name AN 16 S-72: Tag 22, MasterCard Debit System (MDS) File Updates Format: Variable based on the subtags included TDEs: Data Record Tag 22 contains fields that allow the BASE24-eps system to notify MDS of a lost, stolen, or misused card to be listed in the MCC102—Account File, MCC103—Account Management File, or MCCNEG—MDS Negative File. The PAN for the card must also be present in either data element P-2 or P-34 of the message. Note: In 1324/1325 and 1334 messages, only subtags 01, 02, and 22–24 are provided. For these message types, subtags 01 and 02 are mandatory while subtags 22–24 are provided only if relevant to the file update. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 308 Data element definitions The structure of tag 22 is as follows. Tag 22: MasterCard Debit System (MDS) File Updates Subtag 01 Description File Name Format AN 6 The name of the MDS file to be updated. Valid values are as follows: MCC102 = Account File MCC103 = Account Management File MCCNEG = MDS Negative File 02 File Update Code N1 A code identifying the file update function to be performed. The valid values depend on the file to be updated. Valid values for the MCC102 and MCCNEG files are as follows: 1 = Add 2 = Change 3 = Delete 5 = Inquiry Valid values for the MCC103 file are as follows: 1 = Add/Change 3 = Delete 03 Security Code N5 A five-character file update security code used to indicate that a message originator is authorized to update a file. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 309 Data element definitions Tag 22: MasterCard Debit System (MDS) File Updates Subtag 04 Description Entry Reason Format AN 1 A code indicating the reason this card is being listed in the MDS file. All codes are valid for the MCC102 file; all codes except for C, G, O, and V are valid for the MCCNEG file. Only codes C, F, O, and X are valid for the MCC103 file. Valid values are as follows: C = Credit F = Fraud G = Gold L = Lost O = Other P = Capture card S = Stolen card U = Unauthorized use V = VIP X = Counterfeit 05 Customer ID/Issuer ICA N6 The MasterCard-assigned customer ID or member number. A MasterCard member may input only an account number with a BIN assigned to it. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 310 Data element definitions Tag 22: MasterCard Debit System (MDS) File Updates Subtag 06 Description Card Program Format AN 3 For the MCC103 file, this field contains a three-character code identifying the type of card bearing the account number. Valid values are as follows: MCB = MasterCard BusinessCard® Card MCC = (mixed BIN) MCD = MasterCard Debit® Card MCF = MasterCard Corporate Fleet Card® MCG = Gold MasterCard Card MCP = MasterCard Corporate Purchasing Card MCS = MasterCard Standard Card MCW = World MasterCard Card MNS = Non-standard MPL = Platinum MasterCard Card OTH = Other 07 Response Code N2 For the MCC103 file, this field contains the response code this account listing should prompt for in an authorization request. The only valid value is 04 (capture card). 08 VIP Accumulative Limit N 12 For the MCC102 file, this field contains the VIP accumulative limit in whole currency units when the Entry Reason field is set to V. Otherwise, this field contains zeros. 09 VIP Limit Currency Code N3 For the MCC102 file, this field contains the currency code of the amount in the VIP Accumulative Limit field when the Entry Reason field is set to V. Otherwise, this field is not valid. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 311 Data element definitions Tag 22: MasterCard Debit System (MDS) File Updates Subtag 10 Description Region 1 Format AN 1 For the MCC103 file, this field contains a code indicating the first region in which this account is to be listed. Accounts can be listed in up to six regions and must be entered in ascending order (i.e., 1, A– E).Valid values are as follows: 1 = United States A = Canada B = Caribbean, Central America, Mexico, South America C = Asia/Pacific D = Europe E = South Asia/Middle East/Africa 11 Region 1 Purge Date N6 For the MCC103 file, this field contains the date, in YYMMDD format, this account is to be purged from the region identified in the Region 1 field. 12 Region 2 AN 1 For the MCC103 file, this field contains a code indicating the second region in which this account is to be listed. Accounts can be listed in up to six regions and must be entered in ascending order (i.e., 1, A–E). Refer to the Region 1 field description above for a list of valid values. 13 Region 2 Purge Date N6 For the MCC103 file, this field contains the date, in YYMMDD format, this account is to be purged from the region identified in the Region 2 field. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 312 Data element definitions Tag 22: MasterCard Debit System (MDS) File Updates Subtag 14 Description Region 3 Format AN 1 For the MCC103 file, this field contains a code indicating the third region in which this account is to be listed. Accounts can be listed in up to six regions and must be entered in ascending order (i.e., 1, A–E). Refer to the Region 1 field description above for a list of valid values. 15 Region 3 Purge Date N6 For the MCC103 file, this field contains the date, in YYMMDD format, this account is to be purged from the region identified in the Region 3 field. 16 Region 4 AN 1 For the MCC103 file, this field contains a code indicating the fourth region in which this account is to be listed. Accounts can be listed in up to six regions and must be entered in ascending order (i.e., 1, A–E). Refer to the Region 1 field description above for a list of valid values. 17 Region 4 Purge Date N6 For the MCC103 file, this field contains the date, in YYMMDD format, this account is to be purged from the region identified in the Region 4 field. 18 Region 5 AN 1 For the MCC103 file, this field contains a code indicating the fifth region in which this account is to be listed. Accounts can be listed in up to six regions and must be entered in ascending order (i.e., 1, A–E). Refer to the Region 1 field description above for a list of valid values. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 313 Data element definitions Tag 22: MasterCard Debit System (MDS) File Updates Subtag 19 Description Region 5 Purge Date Format N6 For the MCC103 file, this field contains the date, in YYMMDD format, this account is to be purged from the region identified in the Region 5 field. 20 Region 6 AN 1 For the MCC103 file, this field contains a code indicating the sixth region in which this account is to be listed. Accounts can be listed in up to six regions and must be entered in ascending order (i.e., 1, A–E). Refer to the Region 1 field description above for a list of valid values. 21 Region 6 Purge Date N6 For the MCC103 file, this field contains the date, in YYMMDD format, this account is to be purged from the region identified in the Region 6 field. 22 Last Update Activity - Date N6 For an inquiry only on the MCC102 file, this field contains the date, in MMDDYY format, of the last maintenance activity occurring on this account in the 1324 advice request message. 23 Last Update Activity - Time N4 For an inquiry only on the MCC102 file, this field contains the time, in hhmm format, of the last maintenance activity occurring on this account in the 1324 advice request message. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 314 Data element definitions Tag 22: MasterCard Debit System (MDS) File Updates Subtag Description 24 MDS File Update Error Code Format N6 When the action code returned in the Action Code (P-39) data element is set to 304 (Field edit error) of a 1324 advice request message, this field contains a sixdigit code that identifies the error. Refer to MasterCard’s Customer Interface Specification for a listing and descriptions of the error codes that can be returned for each file. 25 Purge Date N6 For the MCC103 file, this optional field contains the purge date in YYMMDD format. This date allows the issuer to specify how long each account listing should remain active in the Account Management File. For the MCCNEG file, this optional field contains the issuer-defined purge date in YYMMDD format. If this date is not included, MDS calculates a purge date 180 days from the date of the account listing. This field defaults to all zeros. 26 Capture Code AN 1 For the MCCNEG file, this field contains one of the following codes to indicate whether to capture the card: Y = Yes, capture the card. N = No, do not capture the card. S-72: Tag 23, e-rsb File Updates Format: Varies based on the subtags included TDEs: Data Record Tag 23 contains fields that allow the BASE24-eps system to send file updates to the e-rsb interchange. The structure of tag 23 is as follows. For more information on e-rsb file update messages and the contents of this tag, refer to the e-rsb message documentation. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 315 Data element definitions Tag 23: e-rsb File Updates Subtag 01 Description Reason for Card Stoppage Format AN 2 Interchange Message: This field maps to data element 117 (File Update Data) in the e-rsb message. 02 Validity Date of the Entry AN 6 (yymmdd) Interchange Message: This field maps to data element 117 (File Update Data) in the e-rsb message. 04 Cardholder Title AN ..3 Interchange Message: This field maps to data element 117 (File Update Data) in the e-rsb message. 05 Card Type AN 3 Interchange Message: This field maps to data element 117 (File Update Data) in the e-rsb message. 06 Date Declared AN 6 (yymmdd) Interchange Message: This field maps to data element 117 (File Update Data) in the e-rsb message. 07 Date and Time of Effect AN 10 (yymmddhhmm) Interchange Message: This field maps to data element 117 (File Update Data) in the e-rsb message. 08 Cardholder Name AN ..26 Interchange Message: This field maps to data element 117 (File Update Data) in the e-rsb message. 09 Lost PIN AN 1 Interchange Message: This field maps to data element 117 (File Update Data) in the e-rsb message. 10 Forcing Flag and Origin AN 1 Interchange Message: This field maps to data element 117 (File Update Data) in the e-rsb message. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 316 Data element definitions Tag 23: e-rsb File Updates Subtag Description 11 Loss or Theft Country Code Format N3 Interchange Message: This field maps to data element 117 (File Update Data) in the e-rsb message. 12 Loss or Theft Department Code AN 3 Interchange Message: This field maps to data element 117 (File Update Data) in the e-rsb message. 13 Type of Fraud AN 1 Interchange Message: This field maps to data element 117 (File Update Data) in the e-rsb message. 23 IBAN (International Bank Account Number) AN ..34 Interchange Message: This field maps to data element 117 (File Update Data) in the e-rsb message. 24 File Name AN ..17 Interchange Message: This field maps to data element 101 (File Name) in the e-rsb message. 25 File Update Code N1 Interchange Message: This field maps to data element 91 (File Update Code) in the e-rsb message. 26 Presenter of BCIS Movement ANS ..255 Interchange Message: This field maps to data element 116 (Reserved for National Use) in the e-rsb message. S-72: Tag 24, PRICE File Updates Format: Variable based on the subtags included TDEs: Data Record Tag 24 contains fields that enable the BASE24-eps system to send file updates to the PRICE interchange. The structure of tag 24 is described below. For more information on PRICE file update messages and the contents of this tag, refer to the PRICE message documentation. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 317 Data element definitions Tag 24: Price File Updates Subtag 01 Description File name Format AN 17 Interchange Message: This field maps to and from data element 101 (File Name) in the Price message. 02 Function Code AN 3 Interchange Message: This field maps to and from data element 24 (Function Code) in the Price message. 03 Format Code 04 Exception code AN 3 05 Inclusion Form/Situation in LNI AN 1 06 Expiration (YYMM) 07 Document type 08 Document number 09 Update Date and time in EXCNEG (YYMMDDhhmmss) N 12 10 Update Date and time in LNI (YYMMDDhhmmss) N 12 11 Holder Identification 12 Caller Identification N4 13 Global limit N9 14 Credit limit N9 15 Purchase limit N9 16 Cash limit at cashier on-off, credit N9 17 Cash limit at ATM, credit N9 18 Debit limit N9 19 Purchase limit online N9 20 Cash limit at cashier online N9 21 Cash limit at ATM, debit N9 22 Daily maximum limit at ATM N9 23 Percentage N3 24 Application initial date (YYMMDD) N6 25 Application end date (YYMMDD) N6 26 Update mode N2 BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 N3 N4 AN 3 AN 12 AN 15 318 Data element definitions Tag 24: Price File Updates Subtag Description Format 27 Global Available AN 10 28 Credit Available AN 10 29 Purchase Available AN 10 30 Cash Available at cashier on-off, credit AN 10 31 Cash Available at ATM, credit AN 10 32 Debit Available AN 10 33 Purchase Available online AN 10 34 Cash available at cashier online AN 10 35 Cash available at ATM, debit AN 10 36 Daily maximum available at ATM AN 10 37 Authentication type 38 Card number N ..19 39 Authentication data AN 75 40 Language N2 N2 S-72: Tag 25, SPAN2 Dispute Processing Identifier Format: AN 16 TDEs: Data Record Tag 25 identifies a chargeback or adjustment transaction as needing to be routed to the SPAN2 Interface component for sending to a SPAN2 dispute processor. This tag can be set to any alphanumeric values—the actual contents of the tag are not used by BASE24-eps. The presence of tag 25 in a message allows the ISO 93 Host Interface component to identify it as a transaction that needs to be sent to the SPAN2 Interface component. Hosts must include this tag in any chargeback or adjustment transactions that are to be routed to the SPAN2 Interface for sending to a SPAN2 dispute processor. Because the contents of the field are not used, the host can set the field to any 16 alphanumeric characters; likewise, the host can ignore the contents of the tag should it be received in a message. Note: The SPAN2 Interface component registers with the File Update Router component with tag 25, which allows the ISO 93 Host Interface component to identify it as a routing destination based on the presence of tag 25 in the message. S-72: Tag 26, Check Status Data Source Updates and Inquiries Format: Variable based on the subtags included TDEs: Data Record Tag 26 contains fields in the Check Status data source (check_status) to be updated or inquired on in a file action request message sent from the ISO 93 host to the BASE24-eps system. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 319 Data element definitions Each field that can be updated or inquired on in the Check Status data source is identified using a subtag. These subtags can be carried—in any combination and any order—in this S-72 data element tag. Note: In addition to the subtags carried in tag 26 of the S-72 data element, the following data elements must be present with values in the file action request message: • • • • P-2: Primary Account Number P-23: Card Sequence Number S-100: Receiving Institution Identification Code (Routing transit number) S-102: Account Identification 1 (Checking account number) These data elements provide the primary key fields to Check Status data source records. Check Status data source updates Inclusion of subtags depends on the type of update function being performed. Function Required subtags Add Subtags must be supplied for any data source fields that need to be set to specific values. Data source fields not included will be set to default values in the new record. Replace The replace function is handled as an add or change function depending on the situation. If a specified record does not exist, the function is treated as an add. If a specified record does exist, the function is treated as an update. Subtags should be supplied accordingly. Update Subtags need only be supplied for those fields in a record to be updated. If a subtag is not supplied, the corresponding field in the record is not affected. To remove a specific field value, include the applicable subtag set to the appropriate default value. This will update the corresponding field in the record to the supplied default values. Delete No subtags are required or processed. Check Status data source inquiries Check Status data source inquiries can request specific data by specifying the subtags of the data to be returned. In this case, specified subtags should be included with a zero length and no data. For example, subtag 01 should be included as 01000. All inquiry response information is carried as subtag data in S-127 tag 14. Check Status data source inquiries can also return a default set of data. In this case, no subtags should be included. Instead, S-72 tag 26 should be submitted with a zero length and no data. The default set of data returned includes subtags 01 through 04. In all cases, data is only returned in a subtag if there is corresponding data in the Check Status data source. Subtag definitions The following is a list of Check Status subtags. All of these subtags represent data carried in the Check Status data source. Data length and type is provided for each. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 320 Data element definitions Tag 26: Check Status Data Source Updates Subtag Description 01 Format Check Status AN 1 A code specifying the disposition of checks associated with the Check Status record. Valid values are as follows: 0 = Accept all checks 1 = Deposit only 2 = Deny all checks 02 Check Retain Flag AN 1 A code indicating the retention status for declined transactions for checks associated with the Check Status record. Valid values are as follows: 0 = Return all checks 1 = Retain all checks 03 Check Amount Limit AN 15 The maximum acceptable check amount—expressed as a whole currency value—for checks associated with the Check Status record.Checks above the specified limit are not authorized.This field need not be set if the Check Status field indicates that the checks should be declined. 04 Check Limit Currency Code N3 Currency code for the amount in the Check Amount Limit field.This field need not be set if the Check Status field indicates that the checks should be declined. S-72: Tag 27, Stop Payment Data Source Updates and Inquiries Format: Variable based on the subtags included TDEs: Data Record Tag 27 contains fields in the Stop Payment data source (stop_payment) to be updated or inquired upon in a file action request message sent from the ISO 93 host to the BASE24-eps system. Each field that can be updated or inquired on in the Stop Payment data source is identified using a subtag. These subtags can be carried—in any combination and any order—in this S-72 data element tag. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 321 Data element definitions Note: Stop payments are currently supported for checking accounts only. Stop Payment data source updates Inclusion of subtags depends on the type of update function being performed. Function Add Required subtags Subtags 01, 02, 03, and 04 are required. Otherwise, subtags must be supplied for any data source fields that need to be set to specific values. Data source fields not included will be set to default values in the new record. Replace The replace function is handled as an add or update function depending on the situation. If a specified record does not exist, the function is treated as an add. If a specified record does exist, the function is treated as an update. Subtags should be supplied accordingly. Update Subtags 01, 02, 03, and 04 are required. Otherwise, subtags need only be supplied for those fields in a record to be updated. If a subtag is not supplied, the corresponding field in the record is not affected. To remove a specific field value, include the applicable subtag set to the appropriate default value. This will update the corresponding field in the record to the supplied default values. Delete Subtags 01, 02, 03, and 04 are required. Stop Payment data source inquiries Stop Payment data source inquiries can request specific data by specifying the subtags of the data to be returned. All inquiry response information is carried as subtag data in data element S-127 tag 15. Data element S-127 tag 16 (Context Cookie Data) can also be included if multiple records are identified in an inquiry. This table identifies the subtags that can or must be included in a Stop Payment Data Source inquiry. Subtag Description 01 Institution ID - Required for all inquiries. 02 Account Type - Required for all inquiries. 03–04 Subtags 03 (High Check Number) and 04 (Low Check Number) are optional. If neither subtag 03 nor subtag 04 are provided, inquiries will return the first record that matches the inquiry criteria sent. If multiple records exist, the primary key of the current record will be sent in the response message in data element S-127, tag 16 (Context Cookie Data). This cookie data can then be echoed back in a subsequent inquiry transaction to get the next record. This process can then be repeated for the rest of the matching records. The response with the last matching record will not contain the cookie data. If subtag 03 is provided and subtag 04 is not, the inquiry will return the first record where the High Check Number is greater than or equal to the High Check Number value sent in subtag 03 and the Low Check Number is less than or equal to the High Check Number value sent in subtag 03. Return of multiple records, in this case, is not supported.Subtag 03 is required if subtag 04 is provided. 05–11 12 Optional. Only required if the specific data is to be returned in the inquiry response. In this case, specified subtags should be included with a zero length and no data. For example, subtag 05 would be included as 05000. Return Expired Stop Payment Data Flag - Optional. If not provided, it defaults to 1, allowing expired records to be returned. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 322 Data element definitions Stop Payment data source inquiries can return a default set of data. In this case, no subtags (that are not required) should be included. Instead, S-72 tag 27 should be submitted with the length of the required subtag data and the required subtag data only. The default set of data returned includes subtags 03 through 11. In all cases, data is only returned in a subtag if there is corresponding data in the Check Status data source. Subtag definitions The following is a list of Stop Payment subtags. All of these subtags represent data carried in the Stop Payment data source. Data length and type is provided for each. Tag 27: Stop Payment Data Source Updates Subtag 01 Description Institution ID Format AN 20 The Institution ID of the institution owning the account—the account is specified in data element P‑2 (Primary Account Number) of the file update message. 02 Account Type AN 2 The type of customer account —the account is specified in data element P‑2 (Primary Account Number) of the file update message. 03 High Check Number AN 11 The check number of the stop payment, or for a range of check numbers, the highest check number in the range. The check number is right-justified and zero-filled on the left. 04 Low Check Number AN 11 For a range of check numbers, this field contains the lowest check number in the range. The check number is right-justified and zerofilled on the left.If the stop payment record is for a single check, rather than a range of checks, this field will contain the same value as the High Check Number field. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 323 Data element definitions Tag 27: Stop Payment Data Source Updates Subtag 05 Description Check Amount Format AN 19 The amount of the check, in whole and fractional currency units, for which the stop payment has been issued. The default value is zero.For a range of check numbers, this field must contain a zero. For a single check number (i.e. not a range), this field can contain a value greater than or equal to zero. 06 Check Amount Currency Code AN 3 The ISO currency code of the check amount. The default value is 840 for U.S. 07 Stop Payment Date AN 8 The date (YYYYMMDD) of the stop payment. If this subtag is not provided, the default value is the current system date. 08 Stop Payment Time AN 6 The time (hhmmss) of the stop payment. If this subtag is not provided, the default value is the current system time. 09 Stop Payment Expiration Date AN 8 The expiration date (YYYYMMDD) for the stop payment. If this subtag is not provided, the expiration date is calculated based on the check types defined in the Check Type data source (comparing them to the check type in subtag 10). If no applicable record is found in the Check Type data source, the expiration date is calculated based on the STOP_PMNT_EXP_DAYS environment parameter. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 324 Data element definitions Tag 27: Stop Payment Data Source Updates Subtag 10 Description Check Type Format AN 2 The type of check for which the stop payment is intended. Valid values are 00 to 99 (e.g., 01 could denote a personal check, 02 a business check, etc.). Check type values can differ from institution to institution (e.g., one institution might use 01 to specify a personal check where another institution might use 02 to specify a personal check). If this subtag is not provided, the default value is 00, which indicates no check type value. If subtag 09 (Stop Payment Expiration Date) is not provided, the check type in this subtag is used in conjunction with Check Type data source to create an expiration date. 11 Stop Payment Description ANS 35 A message regarding the stop payment order. This can be any data about the stop payment order that the institution chooses to place on the file. If this subtag is not provided, the default value is spaces. 12 Return Expired Stop Payment Data Flag AN 1 An indicator specifying whether or not to return expired stop payment records in a file update inquiry response. Valid values are as follows: 0 = Do not return expired Stop Payment records 1 = Return expired Stop Payment records (default) S-72: Tag 28, Visa Dispute Data Format: Variable depending on the subtags included BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 325 Data element definitions TDEs: Data Record Tag 28 is used to identify Visa SMS dispute transactions. It is required in all Visa SMS dispute transactions, whether or not actual subtags are included. If no subtags are needed for the Visa SMS transaction, tag 28 must be included as a zero-length tag. The structure of tag 28 is as follows. For information about Visa transaction messages, refer to the appropriate Visanet technical specifications. Tag 28: Visa Dispute Data Subtag Description 01 Not used 02 Merchant Verification value Format AN 10 Contains the Merchant Verification Value (MVV) used to identify merchants that participate in Select Merchant Fee (SMF) programs. This value is required for Visa SMS chargebacks and representments only. Interchange Message:This field maps to data element 62 (Custom Payment Service Fields), subfield 20 (Merchant Verification Value), in the Visanet transaction message. S-72: Tag 34, Managed List Data Format: Variable depending on the subtags included TDEs: Data Record Tag 34 contains fields in the Managed List data source (managed_list) to be updated or inquired upon in a file action request message sent from the ISO 93 host to the BASE24-eps system. Each field that can be updated or inquired on in the Managed List data source is identified using a subtag. These subtags can be carried—in any combination and any order—in this S-72 data element tag. Note: Primary key fields for a Managed List record cannot be updated. Managed List data source updates Inclusion of subtags depends on the type of update function being performed. Function Add Replace Required subtags Subtags 01, 02 and 03 are required. Subtags 04 and 05 are optional; if not present, they default to spaces. Otherwise, subtags must be supplied for any data source fields that need to be set to specific values. Data source fields not included will be set to default values in the new record. The replace function is handled as an add or update function depending on the situation. If a specified record does not exist, the function is treated as an add. If a specified record does exist, the function is treated as an update. Subtags should be supplied accordingly. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 326 Data element definitions Function Required subtags Update Subtags 01, 02 and 03 are required. Subtags 04 and 05 are optional; if not present, they default to spaces. Otherwise, subtags need only be supplied for those fields in a record to be updated. If a subtag is not supplied, the corresponding field in the record is not affected. To remove a specific field value, include the applicable subtag set to the appropriate default value. This will update the corresponding field in the record to the supplied default values. Delete Subtags 01, 02 and 03 are required. Subtags 04 and 05 are optional; if not present, they default to spaces. Subtag Definitions Note: Primary key fields, which cannot be updated, are denoted with an asterisk following the field name. Tag 34: Managed List Data Subtag 01 Description Insitution ID * Format AN 20 The institution ID of the issuer institution to which this managed list belongs. The instution must already be configured in the Institution data source. 02 List Name * AN 30 The name of the managed list. Must be unique within the institution ID specified. 03 List Key 1 * AN 25 The value of the first list key for this managed list. 04 List Key 2 * AN 25 The value of the second list key for this managed list. 05 List Key 3 * AN 25 The value of the third list key for this managed list. 06 Template Name AN 30 The name of the managed list template used for this managed list. 07 List Description AN 50 An optional description of this managed list. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 327 Data element definitions Tag 34: Managed List Data Subtag 08 Description Attribute 1 Format Format N2 The format of the first attribute for this managed list entry. Valid values are: 0 - numeric 1 - alpha 2 - alphanumeric/special 3 - drop-down 4 - date (yyyymmdd) 5 - time (hhmmss) 6 - date and time (yyyymmddhhmmss) 7 - multi-byte (future) 99 - not applicable Default value is 99. 09 Attribute 1 AN 50 The first attribute value for this managed list 10 Attribute 2 Format N2 The format of the second attribute for this managed list entry. See Attribute 1 Format for valid values. 11 Attribute 2 AN 50 The second attribute value for this managed list 12 Attribute 3 Format N2 The format of the third attribute for this managed list entry. See Attribute 1 Format for valid values. 13 Attribute 3 AN 50 The third attribute value for this managed list 14 Attribute 4 Format N2 The format of the fourth attribute for this managed list entry. See Attribute 1 Format for valid values. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 328 Data element definitions Tag 34: Managed List Data Subtag 15 Description Attribute 4 Format AN 30 The fourth attribute value for this managed list 16 Attribute 5 Format N2 The format of the fifth attribute for this managed list entry. See Attribute 1 Format for valid values. 17 Attribute 5 AN 30 The fifth attribute value for this managed list S-72: Tag 35, Customer Table Required subtags for a Customer, Customer Account, or Customer Multibyte data source update Inclusion of subtags depends on the type of update function being performed. Function Add Required subtags Subtags must be supplied for any data source fields that need to be set to specific values. Data source fields not included will be set to default values in the new record. Note: If 5 or fewer accounts are associated with a Customer record, only a Customer data source record is created. If more than 5 accounts are associated with the Customer record, a corresponding Customer Account data source record is created as well—with any fields not supplied set to their default values. If any multibyte fields are included, a corresponding Customer Account Multibyte record is created. Replace The replace function is handled as an add or change function depending on the situation. If a specified record does not exist, the function is treated as an add. If a specified record does exist, the function is treated as an update. Subtags should be supplied accordingly. Update Subtags need only be supplied for those fields in a record to be updated. If a subtag is not supplied, the corresponding field in the record is not affected. To remove a specific field value, include the applicable subtag set to the appropriate default value. This will update the corresponding field in the record to the supplied default values. Delete No subtags are required or processed. Note: File update transactions for Customer data are journaled under the customer ID specified in data element P-62, tag 77 (Customer 1 ID). The customer ID value in P-62, tag 77 must be a valid customer ID and may be different from the customer ID value provided in data element S-72, tag 35 (Customer Table) if multiple customer IDs are to be updated. If P-62, tag 77 is not present for an update or delete to a Customer, Customer Account, or Customer Multibyte data source record, the file update transaction is denied. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 329 Data element definitions Subtag definitions Subtag definitions are provided below for all of the Customer subtags. The subtags have been grouped as follows: • • • Basic Customer Subtags Customer Account Subtags Customer Multibyte Subtags Subtag definitions – basic Customer subtags The following is a list of basic Customer subtags. All of these subtags represent data carried in the Customer data source. Data length and type is provided for each. Subtag 00 Description Customer ID Type Format N2 Indicates the type of entity represented by the customer ID. Valid values are defined by the customer and may range from 01 to 99. A value of 00 indicates that no Customer ID was used. 01 Customer ID AN 36 The value of the ID entered to represent the customer. 02 Customer Status AN 2 The status of the Customer ID. Values are user-defined. Sample values: closed, lost, stolen, open. 03 Customer Status Change Date Timestamp of the last time the customer status was changed. 04 Billpay Service N 12 (yymmddhhmmss) ANS 20 The name of the billpay service the customer has signed up with, if any. 05 Billpay ID ANS 36 The ID used by the billpay service to identify the customer to the service’s system. 06 Institution ID ANS 20 Identifies the institution associated with the customer. This field may not contain embedded spaces. 07 Unused 08 Unused 09 Unused 10 Unused 11 Effective Date N 8 (yyyymmdd) The date the Customer ID becomes effective. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 330 Data element definitions Subtag 12 Description Effective Date Change Date Timestamp of the last time the Effective Date was changed. 13 Expiration Date Format N 12 (yymmddhhmmss) N 8 (yyyymmdd) The expiration date of the Customer ID. 14 Expiration Date Change Date Timestamp of the last time the Expiration Date was changed. 15 Check Base Flag N 12 (yymmddhhmmss) N1 A flag used to indicate whether check transactions involving checks not defined in the Check Status data source should be included in the Total Cash Advance/Withdrawal usages and checked against the Total Cash Advance/Withdrawal limits. Default value is 0; valid values are: • • 16 0 = No, do not include in Total Cash Advance/Withdrawal usages 1 = Yes, include in Total Cash Advance/Withdrawal usages Check Status Check Base Flag N1 A flag used to indicate whether check transactions involving checks defined in the Check Status data source should be included in the Total Cash Advance/Withdrawal usages and checked against the Total Cash Advance/Withdrawal limits. Default value is 0; valid values are: • • 17 0 = No, do not include in Total Cash Advance/Withdrawal usages 1 = Yes, include in Total Cash Advance/Withdrawal usages Address 1 ANS 25 The first line of the address associated with this customer record. 18 Address 2 ANS 25 The second line of the address associated with this customer record. 19 Postal Code ANS 10 The postal code of the address associated with this customer record. This field may not contain embedded spaces. 20 Default Primary Account Type AN 2 Specifies the default account type to be used to determine the default account. 21 Fraud Option AN 1 Indicates whether a fraud system is used. Default value is 0; valid values are: • • • 0 = Do not used fraud system 1 = Score during authorization 2 = Notify after authorization BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 331 Data element definitions Subtag 22 Description Limit Profile Format AN 16 The name of the limit profile. 23 Limit Name 1 AN 16 A name assigned to a specific limit and its associated usage for a customer record. 24 Limit Maximum 1 N 19 The maximum limit amount/count assigned to a specific limit name. Usages can be maintained to compare against the limit. 25 Limit Currency Code 1 N3 The currency code associated with the usage amount. 26 Limit Period Option 1 N3 The usage period for the limit. Default value is 1; valid values are: • • • • • • • • • • • • • • • • • • • 0 = Usages not cleared 1 = Fixed number of days 2 = One week 3 = Two weeks 4 = 1st and 15th of each month 5 = Every month 6 = Every 3 months 7 = Every 6 months 8 = Every year 9 = Daily except Saturdays, Sundays, and holidays 10 = Daily except Sundays and holidays 11 = Daily except Saturdays and holidays 12 = Fixed number of hours 20 = Rolling number of minutes 21 = Rolling number of 2-minute intervals 22 = Rolling number of hours 23 = Rolling number of days 24 = Rolling number of weeks 25 = Rolling number of months BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 332 Data element definitions Subtag 27 Description Limit Period Additional Data 1 Format N3 Further defines the Usage Period Option values. This field is used in the following ways: • • • • • • 28 If the Usage Period Option value is 1, this value specifies the length of the usage period in days. If the Usage Period Option value is 2 or 3, this value indicates the day of the week on which the usage period begins. Default value is 1; valid values are: • 1 = Sunday • 2 = Monday • 3 = Tuesday • 4 = Wednesday • 5 = Thursday • 6 = Friday • 7 = Saturday If the Usage Period Option value is 5, 6, 7, or 8, this value indicates which day of the month the usage period begins. Default value is 1; valid values range from 1 to 28. If the Usage Period Option value is 12, this value specifies the length of the usage period in hours. Default value is 6. If the Usage Period Option value is 20, 21, 22, 23, 24, or 25, this value indicates the number of usage accumulation buckets associated with the selected Rolling Limit usage period. Valid values range from 1 to 30. This field is not applicable for all other Usage Period values. Limit Expiration Date 1 N 8 (yyyymmdd) The date when a limit or limit override expires and is no longer used in processing. Entering spaces instead of numbers indicates that the limit or limit override does not expire. 29 Limit Name 2 AN 16 A name assigned to a specific limit and its associated usage for a customer record. 30 Limit Maximum 2 N 19 The maximum limit amount/count assigned to a specific limit name. Usages can be maintained to compare against the limit. 31 Limit Currency Code 2 N3 The currency code associated with the usage amount. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 333 Data element definitions Subtag 32 Description Limit Period Option 2 Format N3 The usage period for the limit. Default value is 1; valid values are: • • • • • • • • • • • • • • • • • • • 33 0 = Usages not cleared 1 = Fixed number of days 2 = One week 3 = Two weeks 4 = 1st and 15th of each month 5 = Every month 6 = Every 3 months 7 = Every 6 months 8 = Every year 9 = Daily except Saturdays, Sundays, and holidays 10 = Daily except Sundays and holidays 11 = Daily except Saturdays and holidays 12 = Fixed number of hours 20 = Rolling number of minutes 21 = Rolling number of 2-minute intervals 22 = Rolling number of hours 23 = Rolling number of days 24 = Rolling number of weeks 25 = Rolling number of months Limit Period Additional Data 2 N3 Further defines the Usage Period Option values. This field is used in the following ways: • • • • • • If the Usage Period Option value is 1, this value specifies the length of the usage period in days. If the Usage Period Option value is 2 or 3, this value indicates the day of the week on which the usage period begins. Default value is 1; valid values are: • 1 = Sunday • 2 = Monday • 3 = Tuesday • 4 = Wednesday • 5 = Thursday • 6 = Friday • 7 = Saturday If the Usage Period Option value is 5, 6, 7, or 8, this value indicates which day of the month the usage period begins. Default value is 1; valid values range from 1 to 28. If the Usage Period Option value is 12, this value specifies the length of the usage period in hours. Default value is 6. If the Usage Period Option value is 20, 21, 22, 23, 24, or 25, this value indicates the number of usage accumulation buckets associated with the selected Rolling Limit usage period. Valid values range from 1 to 30. This field is not applicable for all other Usage Period values. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 334 Data element definitions Subtag 34 Description Limit Expiration Date 2 Format N 8 (yyyymmdd) The date when a limit or limit override expires and is no longer used in processing. Entering spaces instead of numbers indicates that the limit or limit override does not expire. 35 Limit Name 3 AN 16 A name assigned to a specific limit and its associated usage for a customer record. 36 Limit Maximum 3 N 19 The maximum limit amount/count assigned to a specific limit name. Usages can be maintained to compare against the limit. 37 Limit Currency Code 3 N3 The currency code associated with the usage amount. 38 Limit Period Option 3 N3 The usage period for the limit. Default value is 1; valid values are: • • • • • • • • • • • • • • • • • • • 0 = Usages not cleared 1 = Fixed number of days 2 = One week 3 = Two weeks 4 = 1st and 15th of each month 5 = Every month 6 = Every 3 months 7 = Every 6 months 8 = Every year 9 = Daily except Saturdays, Sundays, and holidays 10 = Daily except Sundays and holidays 11 = Daily except Saturdays and holidays 12 = Fixed number of hours 20 = Rolling number of minutes 21 = Rolling number of 2-minute intervals 22 = Rolling number of hours 23 = Rolling number of days 24 = Rolling number of weeks 25 = Rolling number of months BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 335 Data element definitions Subtag 39 Description Limit Period Additional Data 3 Format N3 Further defines the Usage Period Option values. This field is used in the following ways: • • • • • • 40 If the Usage Period Option value is 1, this value specifies the length of the usage period in days. If the Usage Period Option value is 2 or 3, this value indicates the day of the week on which the usage period begins. Default value is 1; valid values are: • 1 = Sunday • 2 = Monday • 3 = Tuesday • 4 = Wednesday • 5 = Thursday • 6 = Friday • 7 = Saturday If the Usage Period Option value is 5, 6, 7, or 8, this value indicates which day of the month the usage period begins. Default value is 1; valid values range from 1 to 28. If the Usage Period Option value is 12, this value specifies the length of the usage period in hours. Default value is 6. If the Usage Period Option value is 20, 21, 22, 23, 24, or 25, this value indicates the number of usage accumulation buckets associated with the selected Rolling Limit usage period. Valid values range from 1 to 30. This field is not applicable for all other Usage Period values. Limit Expiration Date 3 N 8 (yyyymmdd) The date when a limit or limit override expires and is no longer used in processing. Entering spaces instead of numbers indicates that the limit or limit override does not expire. 41 Limit Name 4 AN 16 A name assigned to a specific limit and its associated usage for a customer record. 42 Limit Maximum 4 N 19 The maximum limit amount/count assigned to a specific limit name. Usages can be maintained to compare against the limit. 43 Limit Currency Code 4 N3 The currency code associated with the usage amount. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 336 Data element definitions Subtag 44 Description Limit Period Option 4 Format N3 The usage period for the limit. Default value is 1; valid values are: • • • • • • • • • • • • • • • • • • • 45 0 = Usages not cleared 1 = Fixed number of days 2 = One week 3 = Two weeks 4 = 1st and 15th of each month 5 = Every month 6 = Every 3 months 7 = Every 6 months 8 = Every year 9 = Daily except Saturdays, Sundays, and holidays 10 = Daily except Sundays and holidays 11 = Daily except Saturdays and holidays 12 = Fixed number of hours 20 = Rolling number of minutes 21 = Rolling number of 2-minute intervals 22 = Rolling number of hours 23 = Rolling number of days 24 = Rolling number of weeks 25 = Rolling number of months Limit Period Additional Data 4 N3 Further defines the Usage Period Option values. This field is used in the following ways: • • • • • • If the Usage Period Option value is 1, this value specifies the length of the usage period in days. If the Usage Period Option value is 2 or 3, this value indicates the day of the week on which the usage period begins. Default value is 1; valid values are: • 1 = Sunday • 2 = Monday • 3 = Tuesday • 4 = Wednesday • 5 = Thursday • 6 = Friday • 7 = Saturday If the Usage Period Option value is 5, 6, 7, or 8, this value indicates which day of the month the usage period begins. Default value is 1; valid values range from 1 to 28. If the Usage Period Option value is 12, this value specifies the length of the usage period in hours. Default value is 6. If the Usage Period Option value is 20, 21, 22, 23, 24, or 25, this value indicates the number of usage accumulation buckets associated with the selected Rolling Limit usage period. Valid values range from 1 to 30. This field is not applicable for all other Usage Period values. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 337 Data element definitions Subtag 46 Description Limit Expiration Date 4 Format N 8 (yyyymmdd) The date when a limit or limit override expires and is no longer used in processing. Entering spaces instead of numbers indicates that the limit or limit override does not expire. 47 Limit Name 5 AN 16 A name assigned to a specific limit and its associated usage for a customer record. 48 Limit Maximum 5 N 19 The maximum limit amount/count assigned to a specific limit name. Usages can be maintained to compare against the limit. 49 Limit Currency Code 5 N3 The currency code associated with the usage amount. 50 Limit Period Option 5 N3 The usage period for the limit. Default value is 1; valid values are: • • • • • • • • • • • • • • • • • • • 0 = Usages not cleared 1 = Fixed number of days 2 = One week 3 = Two weeks 4 = 1st and 15th of each month 5 = Every month 6 = Every 3 months 7 = Every 6 months 8 = Every year 9 = Daily except Saturdays, Sundays, and holidays 10 = Daily except Sundays and holidays 11 = Daily except Saturdays and holidays 12 = Fixed number of hours 20 = Rolling number of minutes 21 = Rolling number of 2-minute intervals 22 = Rolling number of hours 23 = Rolling number of days 24 = Rolling number of weeks 25 = Rolling number of months BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 338 Data element definitions Subtag 51 Description Limit Period Additional Data 5 Format N3 Further defines the Usage Period Option values. This field is used in the following ways: • • • • • • 52 If the Usage Period Option value is 1, this value specifies the length of the usage period in days. If the Usage Period Option value is 2 or 3, this value indicates the day of the week on which the usage period begins. Default value is 1; valid values are: • 1 = Sunday • 2 = Monday • 3 = Tuesday • 4 = Wednesday • 5 = Thursday • 6 = Friday • 7 = Saturday If the Usage Period Option value is 5, 6, 7, or 8, this value indicates which day of the month the usage period begins. Default value is 1; valid values range from 1 to 28. If the Usage Period Option value is 12, this value specifies the length of the usage period in hours. Default value is 6. If the Usage Period Option value is 20, 21, 22, 23, 24, or 25, this value indicates the number of usage accumulation buckets associated with the selected Rolling Limit usage period. Valid values range from 1 to 30. This field is not applicable for all other Usage Period values. Limit Expiration Date 5 N 8 (yyyymmdd) The date when a limit or limit override expires and is no longer used in processing. Entering spaces instead of numbers indicates that the limit or limit override does not expire. 53 Limit Name 6 AN 16 A name assigned to a specific limit and its associated usage for a customer record. 54 Limit Maximum 6 N 19 The maximum limit amount/count assigned to a specific limit name. Usages can be maintained to compare against the limit. 55 Limit Currency Code 6 N3 The currency code associated with the usage amount. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 339 Data element definitions Subtag 56 Description Limit Period Option 6 Format N3 The usage period for the limit. Default value is 1; valid values are: • • • • • • • • • • • • • • • • • • • 57 0 = Usages not cleared 1 = Fixed number of days 2 = One week 3 = Two weeks 4 = 1st and 15th of each month 5 = Every month 6 = Every 3 months 7 = Every 6 months 8 = Every year 9 = Daily except Saturdays, Sundays, and holidays 10 = Daily except Sundays and holidays 11 = Daily except Saturdays and holidays 12 = Fixed number of hours 20 = Rolling number of minutes 21 = Rolling number of 2-minute intervals 22 = Rolling number of hours 23 = Rolling number of days 24 = Rolling number of weeks 25 = Rolling number of months Limit Period Additional Data 6 N3 Further defines the Usage Period Option values. This field is used in the following ways: • • • • • • If the Usage Period Option value is 1, this value specifies the length of the usage period in days. If the Usage Period Option value is 2 or 3, this value indicates the day of the week on which the usage period begins. Default value is 1; valid values are: • 1 = Sunday • 2 = Monday • 3 = Tuesday • 4 = Wednesday • 5 = Thursday • 6 = Friday • 7 = Saturday If the Usage Period Option value is 5, 6, 7, or 8, this value indicates which day of the month the usage period begins. Default value is 1; valid values range from 1 to 28. If the Usage Period Option value is 12, this value specifies the length of the usage period in hours. Default value is 6. If the Usage Period Option value is 20, 21, 22, 23, 24, or 25, this value indicates the number of usage accumulation buckets associated with the selected Rolling Limit usage period. Valid values range from 1 to 30. This field is not applicable for all other Usage Period values. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 340 Data element definitions Subtag 58 Description Limit Expiration Date 6 Format N 8 (yyyymmdd) The date when a limit or limit override expires and is no longer used in processing. Entering spaces instead of numbers indicates that the limit or limit override does not expire. 59 CSM Buffer ANS 1000 Allows customer-specific data to be entered. This field’s length is variable and includes a 3-digit length prefix. 60 CSM Buffer Change Date Timestamp of the last time the CSM Buffer was changed. 61 Account Number Total N 12 (yymmddhhmmss) N2 The total number of accounts associated with an instrument type. Valid values range from 00 to 45. 62 Bank ID Type 1 N2 Bank/Branch Code ID Type associated with the account number. Valid values are: • • • • 63 1 = IBAN 2 = BBAN 3 = BIC 4 = RTTN Bank/Branch Code 1 AN 34 Bank/Branch Code associated with the account number. 64 Account Number 1 AN 28 Account number associated with a Customer ID. 65 Account Type 1 AN 2 The account type of an account number. 66 Account Status 1 AN 2 The status of the account. Values from 00 to 15 indicate an open status; all others are user-defined. 67 Account Description 1 ANS 10 The description of the account. 68 Bank ID Type 2 N2 Bank/Branch Code ID Type associated with the account number. Valid values are: • • • • 1 = IBAN 2 = BBAN 3 = BIC 4 = RTTN BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 341 Data element definitions Subtag 69 Description Bank/Branch Code 2 Format AN 34 Bank/Branch Code associated with the account number. 70 Account Number 2 AN 28 Account number associated with a Customer ID. 71 Account Type 2 AN 2 The account type of an account number. 72 Account Status 2 AN 2 The status of the account. Values from 00 to 15 indicate an open status; all others are user-defined. 73 Account Description 2 ANS 10 The description of the account. 74 Bank ID Type 3 N2 Bank/Branch Code ID Type associated with the account number. Valid values are: • • • • 75 1 = IBAN 2 = BBAN 3 = BIC 4 = RTTN Bank/Branch Code 3 AN 34 Bank/Branch Code associated with the account number. 76 Account Number 3 AN 28 Account number associated with a Customer ID. 77 Account Type 3 AN 2 The account type of an account number. 78 Account Status 3 AN 2 The status of the account. Values from 00 to 15 indicate an open status; all others are user-defined. 79 Account Description 3 ANS 10 The description of the account. 80 Bank ID Type 4 N2 Bank/Branch Code ID Type associated with the account number. Valid values are: • • • • 1 = IBAN 2 = BBAN 3 = BIC 4 = RTTN BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 342 Data element definitions Subtag 81 Description Bank/Branch Code 4 Format AN 34 Bank/Branch Code associated with the account number. 82 Account Number 4 AN 28 Account number associated with a Customer ID. 83 Account Type 4 AN 2 The account type of an account number. 84 Account Status 4 AN 2 The status of the account. Values from 00 to 15 indicate an open status; all others are user-defined. 85 Account Description 4 ANS 10 The description of the account. 86 Bank ID Type 5 N2 Bank/Branch Code ID Type associated with the account number. Valid values are: • • • • 87 1 = IBAN 2 = BBAN 3 = BIC 4 = RTTN Bank/Branch Code 5 AN 34 Bank/Branch Code associated with the account number. 88 Account Number 5 AN 28 Account number associated with a Customer ID. 89 Account Type 5 AN 2 The account type of an account number. 90 Account Status 5 AN 2 The status of the account. Values from 00 to 15 indicate an open status; all others are user-defined. 91 Account Description 5 ANS 10 The description of the account. Customer account definitions The fields described in the following table are standard fields for each of the 45 accounts that can be associated with the Customer data source. Accounts 1 through 5 are contained in the Customer data source. Accounts 6 through 45 are contained in the Customer Account data source. The subtags representing these fields are included following the table. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 343 Data element definitions Field definitions Bank ID Type - Bank/Branch Code ID Type associated with the account number. Valid values are: • • • • 1 = IBAN 2 = BBAN 3 = BIC 4 = RTTN Bank/Branch Code - Bank/Branch Code associated with the account number. Account Number - Account number associated with a Customer ID. Account Type - The account type of an account number. Account Status - The status of the account. Values from 00 to 15 indicate an open status; all others are userdefined. Account Description - The description of the account. Subtag definitions – Customer account subtags The following is a list of Customer account subtags. Data length and type is provided for each. Subtag Description Format 92 Bank ID Type 6 93 Bank/Branch Code 6 AN 34 94 Account Number 6 AN 28 95 Account Type 6 AN 2 96 Account Status 6 AN 2 97 Account Description 6 98 Bank ID Type 7 99 Bank/Branch Code 7 AN 34 A0 Account Number 7 AN 28 A1 Account Type 7 AN 2 A2 Account Status 7 AN 2 A3 Account Description 7 A4 Bank ID Type 8 A5 Bank/Branch Code 8 AN 34 A6 Account Number 8 AN 28 A7 Account Type 8 AN 2 A8 Account Status 8 AN 2 A9 Account Description 8 BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 N2 ANS 10 N2 ANS 10 N2 ANS 10 344 Data element definitions Subtag Description Format AA Bank ID Type 9 AB Bank/Branch Code 9 AN 34 AC Account Number 9 AN 28 AD Account Type 9 AN 2 AE Account Status 9 AN 2 AF Account Description 9 AG Bank ID Type 10 AH Bank/Branch Code 10 AN 34 AI Account Number 10 AN 28 AJ Account Type 10 AN 2 AK Account Status 10 AN 2 AL Account Description 10 AM Bank ID Type 11 AN Bank/Branch Code 11 AN 34 AO Account Number 11 AN 28 AP Account Type 11 AN 2 AQ Account Status 11 AN 2 AR Account Description 11 AS Bank ID Type 12 AT Bank/Branch Code 12 AN 34 AU Account Number 12 AN 28 AV Account Type 12 AN 2 AW Account Status 12 AN 2 AX Account Description 12 AY Bank ID Type 13 AZ Bank/Branch Code 13 AN 34 B0 Account Number 13 AN 28 B1 Account Type 13 AN 2 B2 Account Status 13 AN 2 B3 Account Description 13 B4 Bank ID Type 14 BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 N2 ANS 10 N2 ANS 10 N2 ANS 10 N2 ANS 10 N2 ANS 10 N2 345 Data element definitions Subtag Description Format B5 Bank/Branch Code 14 AN 34 B6 Account Number 14 AN 28 B7 Account Type 14 AN 2 B8 Account Status 14 AN 2 B9 Account Description 14 BA Bank ID Type 15 BB Bank/Branch Code 15 AN 34 BC Account Number 15 AN 28 BD Account Type 15 AN 2 BE Account Status 15 AN 2 BF Account Description 15 BG Bank ID Type 16 BH Bank/Branch Code 16 AN 34 BI Account Number 16 AN 28 BJ Account Type 16 AN 2 BK Account Status 16 AN 2 BL Account Description 16 BM Bank ID Type 17 BN Bank/Branch Code 17 AN 34 BO Account Number 17 AN 28 BP Account Type 17 AN 2 BQ Account Status 17 AN 2 BR Account Description 17 BS Bank ID Type 18 BT Bank/Branch Code 18 AN 34 BU Account Number 18 AN 28 BV Account Type 18 AN 2 BW Account Status 18 AN 2 BX Account Description 18 BY Bank ID Type 19 BZ Bank/Branch Code 19 AN 34 C0 Account Number 19 AN 28 BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 ANS 10 N2 ANS 10 N2 ANS 10 N2 ANS 10 N2 ANS 10 N2 346 Data element definitions Subtag Description Format C1 Account Type 19 AN 2 C2 Account Status 19 AN 2 C3 Account Description 19 C4 Bank ID Type 20 C5 Bank/Branch Code 20 AN 34 C6 Account Number 20 AN 28 C7 Account Type 20 AN 2 C8 Account Status 20 AN 2 C9 Account Description 20 CA Bank ID Type 21 CB Bank/Branch Code 21 AN 34 CC Account Number 21 AN 28 CD Account Type 21 AN 2 CE Account Status 21 AN 2 CF Account Description 21 CG Bank ID Type 22 CH Bank/Branch Code 22 AN 34 CI Account Number 22 AN 28 CJ Account Type 22 AN 2 CK Account Status 22 AN 2 CL Account Description 22 CM Bank ID Type 23 CN Bank/Branch Code 23 AN 34 CO Account Number 23 AN 28 CP Account Type 23 AN 2 CQ Account Status 23 AN 2 CR Account Description 23 CS Bank ID Type 24 CT Bank/Branch Code 24 AN 34 CU Account Number 24 AN 28 CV Account Type 24 AN 2 CW Account Status 24 AN 2 BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 ANS 10 N2 ANS 10 N2 ANS 10 N2 ANS 10 N2 ANS 10 N2 347 Data element definitions Subtag Description Format CX Account Description 24 CY Bank ID Type 25 CZ Bank/Branch Code 25 AN 34 D0 Account Number 25 AN 28 D1 Account Type 25 AN 2 D2 Account Status 25 AN 2 D3 Account Description 25 D4 Bank ID Type 26 D5 Bank/Branch Code 26 AN 34 D6 Account Number 26 AN 28 D7 Account Type 26 AN 2 D8 Account Status 26 AN 2 D9 Account Description 26 DA Bank ID Type 27 DB Bank/Branch Code 27 AN 34 DC Account Number 27 AN 28 DD Account Type 27 AN 2 DE Account Status 27 AN 2 DF Account Description 27 DG Bank ID Type 28 DH Bank/Branch Code 28 AN 34 DI Account Number 28 AN 28 DJ Account Type 28 AN 2 DK Account Status 28 AN 2 DL Account Description 28 DM Bank ID Type 29 DN Bank/Branch Code 29 AN 34 DO Account Number 29 AN 28 DP Account Type 29 AN 2 DQ Account Status 29 AN 2 DR Account Description 29 BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 ANS 10 N2 ANS 10 N2 ANS 10 N2 ANS 10 N2 ANS 10 N2 ANS 10 348 Data element definitions Subtag Description Format DS Bank ID Type 30 DT Bank/Branch Code 30 AN 34 DU Account Number 30 AN 28 DV Account Type 30 AN 2 DW Account Status 30 AN 2 DX Account Description 30 DY Bank ID Type 31 DZ Bank/Branch Code 31 AN 34 E0 Account Number 31 AN 28 E1 Account Type 31 AN 2 E2 Account Status 31 AN 2 E3 Account Description 31 E4 Bank ID Type 32 E5 Bank/Branch Code 32 AN 34 E6 Account Number 32 AN 28 E7 Account Type 32 AN 2 E8 Account Status 32 AN 2 E9 Account Description 32 EA Bank ID Type 33 EB Bank/Branch Code 33 AN 34 EC Account Number 33 AN 28 ED Account Type 33 AN 2 EE Account Status 33 AN 2 EF Account Description 33 EG Bank ID Type 34 EH Bank/Branch Code 34 AN 34 EI Account Number 34 AN 28 EJ Account Type 34 AN 2 EK Account Status 34 AN 2 EL Account Description 34 EM Bank ID Type 35 EN Bank/Branch Code 35 BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 N2 ANS 10 N2 ANS 10 N2 ANS 10 N2 ANS 10 N2 ANS 10 N2 AN 34 349 Data element definitions Subtag Description Format EO Account Number 35 EP Account Type 35 AN 2 EQ Account Status 35 AN 2 ER Account Description 35 ES Bank ID Type 36 ET Bank/Branch Code 36 AN 34 EU Account Number 36 AN 28 EV Account Type 36 AN 2 EW Account Status 36 AN 2 EX Account Description 36 EY Bank ID Type 37 EZ Bank/Branch Code 37 AN 34 F0 Account Number 37 AN 28 F1 Account Type 37 AN 2 F2 Account Status 37 AN 2 F3 Account Description 37 F4 Bank ID Type 38 F5 Bank/Branch Code 38 AN 34 F6 Account Number 38 AN 28 F7 Account Type 38 AN 2 F8 Account Status 38 AN 2 F9 Account Description 38 FA Bank ID Type 39 FB Bank/Branch Code 39 AN 34 FC Account Number 39 AN 28 FD Account Type 39 AN 2 FE Account Status 39 AN 2 FF Account Description 39 FG Bank ID Type 40 FH Bank/Branch Code 40 AN 34 FI Account Number 40 AN 28 FJ Account Type 40 BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 AN 28 ANS 10 N2 ANS 10 N2 ANS 10 N2 ANS 10 N2 ANS 10 N2 AN 2 350 Data element definitions Subtag Description Format FK Account Status 40 FL Account Description 40 FM Bank ID Type 41 FN Bank/Branch Code 41 AN 34 FO Account Number 41 AN 28 FP Account Type 41 AN 2 FQ Account Status 41 AN 2 FR Account Description 41 FS Bank ID Type 42 FT Bank/Branch Code 42 AN 34 FU Account Number 42 AN 28 FV Account Type 42 AN 2 FW Account Status 42 AN 2 FX Account Description 42 FY Bank ID Type 43 FZ Bank/Branch Code 43 AN 34 G0 Account Number 43 AN 28 G1 Account Type 43 AN 2 G2 Account Status 43 AN 2 G3 Account Description 43 G4 Bank ID Type 44 G5 Bank/Branch Code 44 AN 34 G6 Account Number 44 AN 28 G7 Account Type 44 AN 2 G8 Account Status 44 AN 2 G9 Account Description 44 GA Bank ID Type 45 GB Bank/Branch Code 45 AN 34 GC Account Number 45 AN 28 GD Account Type 45 AN 2 GE Account Status 45 AN 2 GF Account Description 45 BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 AN 2 ANS 10 N2 ANS 10 N2 ANS 10 N2 ANS 10 N2 ANS 10 N2 ANS 10 351 Data element definitions Subtag Description GG Format AVS Check AN 1 Indicates if Address Verification should be performed. Default is 0; valid values are: • • GH 0 = No 1 = Yes Deposit Type AN 1 The deposit type associated with the customer. Default is 0; valid values are: • • 0 = Use standard 1 = Use commercial Subtag definitions – Customer Multibyte subtags The following is a list of Customer Multibyte subtags. All of these subtags represent data carried in the Customer Multibyte data source. These values represent multibyte versions of specific Customer and Customer Account data. Data length and type is provided for each. Note: Multibyte information is carried as binary in the Customer Multibyte data source. This binary information must be represented in these subtags in a two-character hexadecimal display format. Refer to “Card AccountMultibyte subtag — Two-Character Hexadecimal Display Format” under S-72, Tag 01 (Card Data Source Updates and Inquiries) for information about how this hexadecimal display data must be created. Subtag M0 Description Customer ID Multi-Byte Format AN ..144 The multibyte representation (in two-character hexadecimal display format) of the customer ID associated with the customer record. M1 Address 1 Multi-Byte AN ..100 The multibyte representation (in two-character hexadecimal display format) of the first address line associated with the customer record. M2 Address 2 AN ..100 The multibyte representation (in two-character hexadecimal display format) of the second address line associated with the customer record. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 352 Data element definitions Subtag M3 Description Postal Code Format AN ..40 The multibyte representation (in two-character hexadecimal display format) of the postal code associated with the customer record. Subtags M4–NC carry multibyte representations (in two-character hexadecimal display format) of the account descriptions for accounts 1 through 80—associated with a customer record. Account descriptions are user-defined descriptions of the corresponding accounts. M4 Account 1 Description AN ..40 M5 Account 2 Description AN ..40 M6 Account 3 Description AN ..40 M7 Account 4 Description AN ..40 M8 Account 5 Description AN ..40 M9 Account 6 Description AN ..40 MA Account 7 Description AN ..40 MB Account 8 Description AN ..40 MC Account 9 Description AN ..40 MD Account 10 Description AN ..40 ME Account 11 Description AN ..40 MF Account 12 Description AN ..40 MG Account 13 Description AN ..40 MH Account 14 Description AN ..40 MI Account 15 Description AN ..40 MJ Account 16 Description AN ..40 MK Account 17 Description AN ..40 ML Account 18 Description AN ..40 MM Account 19 Description AN ..40 MN Account 20 Description AN ..40 MO Account 21 Description AN ..40 MP Account 22 Description AN ..40 MQ Account 23 Description AN ..40 BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 353 Data element definitions Subtag Description Format MR Account 24 Description AN ..40 MS Account 25 Description AN ..40 MT Account 26 Description AN ..40 MU Account 27 Description AN ..40 MV Account 28 Description AN ..40 MW Account 29 Description AN ..40 MX Account 30 Description AN ..40 MY Account 31 Description AN ..40 MZ Account 32 Description AN ..40 N0 Account 33 Description AN ..40 N1 Account 34 Description AN ..40 N2 Account 35 Description AN ..40 N3 Account 36 Description AN ..40 N4 Account 37 Description AN ..40 N5 Account 38 Description AN ..40 N6 Account 39 Description AN ..40 N7 Account 40 Description AN ..40 N8 Account 41 Description AN ..40 N9 Account 42 Description AN ..40 NA Account 43 Description AN ..40 NB Account 44 Description AN ..40 NC Account 45 Description AN ..40 S-72: Tag 36, Customer Card Relation Table Required subtags for a Customer to Card Relation data source update Inclusion of subtags depends on the type of update function being performed. Function Add Required subtags Subtags must be supplied for any data source fields that need to be set to specific values. Data source fields not included will be set to default values in the new record. Replace Not supported for the Customer to Card Relation data source. 1 Update Not supported for the Customer to Card Relation data source. 1 Delete No subtags are required or processed. 1 Because the Customer to Card Relation data source only consists of key fields, you can only add or delete records. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 354 Data element definitions Subtag definitions – Customer to Card Relation subtags The following is a list of Customer to Card Relation subtags. All of these subtags represent data carried in the Customer to Card Relation data source. Data length and type is provided for each. Subtag Description 00 Format Customer ID Type N2 Indicates the type of entity represented by the ID. Valid values are defined by the customer and may range from 01 to 99. A value of 00 indicates that no Customer ID was used. 01 Customer ID AN 36 The value of the ID entered to represent the customer. 02 PAN AN 28 The value of the Primary Account Number. 03 Card Sequence Number AN 3 The number used to identify an individual member when several members have the same card number (or PAN). S-72: Tag 48, Elan File Update Information Format: Variable based on the subtags included TDEs: Data Record Tag 48 contains fields needed to process file updates for the Elan interchange. The structure of tag 48 is as follows. Refer to the Elan reference documentation for information about the Elan transaction messages. Tag 48: Elan File Update Information Subtag 01 Description File Name Format ANS 2 Identifies the type of file being updated. Interchange Message: This field maps to data element 101 (File Name) in the Elan transaction message. 02 File Update Code N1 The type of file update to be done. Interchange Message: This field maps to data element 91 (File Update Code) in the Elan transaction message. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 355 Data element definitions Tag 48: Elan File Update Information Subtag Description 03 Card Type Format ANS 2 Interchange Message: This field maps to data element 120 (FHM Base Segment Info) in the Elan transaction message. 04 Reason Code ANS 2 Interchange Message: This field maps to data element 120 (FHM Base Segment Info) in the Elan transaction message. 05 Capture Code ANS 1 Interchange Message: This field maps to data element 120 (FHM Base Segment Info) in the Elan transaction message. 06 Expiration Date (YYMM) N4 Interchange Message: This field maps to data element 120 (FHM Base Segment Info) in the Elan transaction message. 07 DPC Number ANS 4 Interchange Message: This field maps to data element 60 (From Host Maintenance Data) in the Elan transaction message. 08 Terminal ID ANS 8 Interchange Message: This field maps to data element 60 (From Host Maintenance Data) in the Elan transaction message. 09 Last File Maintenance Time Stamp ANS 14 Interchange Message: This field maps to data element 60 (From Host Maintenance Data) in the Elan transaction message. S-72: Tag 49, FIS ISO File Update Format: Variable based on the subtags included TDEs: Data Record BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 356 Data element definitions Tag 49 contains file update fields that can be sent to Fidelity National Information Services (FIS) using the FIS ISO Interface. The structure of tag 49 is as follows. Tag 49: FIS ISO File Update Subtag Description 01 Response Code 02 Isssuer Transport Data 03 File Update Code 04 Authorization Agent ID Code Format AN 2 AN 40 AN 1 AN 11 S-72: Tag 50, Interac Exceptions Browser Information Format: Variable based on the subtags included TDEs: Data Record Tag 50 contains administrative data being sent to Interac from the Interac Exceptions Browser. This data is moved to the Data Record TDE and sent to the File Update Router, which routes the data to the Interac interface. The structure of tag 50 is as follows. Tag 50: Interac Exceptions Browser Information Subtag Description Format 01 Issuer Node ID N6 02 Admin Type N2 03 Trace/action code N2 04 Original settlement date N6 05 Message class N2 06 Remote node ID N6 S-72: Tag 51, Application PAN Relation Data Source Updates Format: Variable based on the subtags included TDEs: Data Record Tag 51 contains fields in the Application PAN Relation data source to be updated or inquired on in a file action request message sent from the ISO 93 host to the BASE24- eps system. Requires the AS215 - EMV MultiApplication Support module license. The structure of tag 51 is as follows. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 357 Data element definitions Tag 51: Application PAN Relation Data Source Updates Subtag Description 01 Format Institution ID AN 20 A combination of letters and numbers that uniquely identifies the institution that issued the multiapplication EMV card. 02 Primary PAN AN 28 The primary PAN associated with a multi-application EMV chip card. 03 Primary PAN Sequence Number AN 3 The primary PAN sequence number associated with a multi-application EMV chip card. 04 Application PAN AN 28 An application PAN associated with the primary PAN. 05 Application PAN Sequence Number AN 3 An application PAN sequence number (APSN) used to identify an individual application on a multiapplication EMV card. S-72: Tag 52, CUP Stand-in Parameter Update Format: Variable based on the subtags included TDEs: Data Record Tag 52 contains data being sent to the CUP network for Stand In Parameter Update messages. This data is moved to the Data Record TDE and sent to the File Update Router, which routes the data to the CUP Host File Message component. The structure of tag 52 is as follows. Tag 52: CUP Stand-in Parameter Update Subtag 01 Description Parameter type Format A3 STP - synchronize black card list parameter record 02 Issuer's IIN AN 11 The field is padded with blanks if the IIN is less than 11 digits long. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 358 Data element definitions Tag 52: CUP Stand-in Parameter Update Subtag Description 03 Format Description ANS 20 Reserved for use by issuer 04 Expiry date N8 Indicates the date that the record will expire. If the system time is later than the recorded time, the card is regarded as expired and filled with default value as blanks. Valid format: YYYYMMDD. S-72: Tag 53, Visa Token File Format: Variable based on the subtags included TDEs: Network Tokenization Service Tag 53 contains token data being sent to VisaNet for file updates. The structure of tag 53 is as follows. Tag 53: Visa Token File Subtag Description Format 01 Token 02 Token Requester ID N11 03 Token Reference ID AN32 04 Token Type 05 Additional Data 06 Message Reason Code 07 Transaction Identifier N15 08 Token Assurance Level AN2 09 Token Status AN1 10 PAN Reference ID 11 Token Expiration Date 12 RFU AN2 13 Last Updated By AN1 14 Activation Code 15 Activation Code, Expiration Date/ Time 16 Activation Code, Verification Attempts BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 AN13...19 AN2 ANS1...255 N4 ANS32 N4 AN6-8 AN12 N4 359 Data element definitions Tag 53: Visa Token File Subtag Description 17 Number of Activation Codes Issued 18 Device Type 19 Device ID 20 Device Number 21 Device Name 22 Token List Format N4 AN2 ANS1…48 N15 ANS16 AN20...207 This tag maps to Visa field DE123.98.01 where multiple tokens can be returned in a token list inquiry. 23 Token Inquiry Type AN1 Valid values are as follows: 1 = List all by PAN 2 = List all by PAN Reference ID 3 = Detail by Token 4 = Detail by Token Reference 24 Total Number Tokens N4 25 Starting Query Number N4 S-72: Tag 54_Visa PAN File Format: Variable based on the subtags included TDEs: Network Tokenization Service Tag 54 contains PAN data being sent to VisaNet for file updates. The structure of tag 54 is as follows. Tag 53: Visa PAN File Subtag Description Format 01 PAN Reference ID ANS32 02 Replacement PAN AN13…19 03 Replacement PAN N4 04 Error Codes N4 05 Transaction Identifier N15 S-72: Tag 99, Failed Message Data Format: ANS ..994 TDEs: BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 360 Data element definitions Tag 99 contains the first 994 bytes of a message that could not be parsed. This tag is sent in an administrative notification for a failed message. This tag is a variable length field up to 999 characters (including the two-digit tag identifier and three-digit length). S-72: Tag BB, Reserved Format: Currently undefined TDEs: Currently undefined Tag BB is reserved for future use. S-93: Transaction Destination Institution Identification Code Format: LLVAR N ..11 TDEs: Transaction Destination Institution ID Code The Transaction Destination Institution Identification Code data element contains the code identifying the institution that is the transaction destination. S-94: Transaction Originator Institution Identification Code Format: LLVAR N ..11 TDEs: Transaction Originator Institution ID Code The Transaction Originator Institution Identification Code data element contains the code identifying the institution that is the transaction originator. S-96: Key Management Data Format: LLLVAR ANS ..547 TDEs: Tags 01, 03, 04, and 05 are mapped to and from the PIN Key TDE or MAC Key TDE, depending on the key type. Tag 02 is mapped to and from the Security Control Information TDE. The Key Management Data TDE contains several fields associated with the key management messages (such as, 1804, 1805, and 1814). Use of tags This data element carries tagged data items. The tags defined for this data element are listed in the table below. Tagged data items are structured in the following manner: a tag identifying the type of data, followed immediately by a three-digit length (LLL) identifying the length of the data, followed immediately by the data itself. Tag + LLL + data. Tagged data varies in length depending on the tag, and multiple tagged data items can be included in any order within the data element. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 361 Data element definitions Tag Description 01 Format Key Type N2 Variable data 00 = PIN key 01 = MAC key 02 Key Index 03 Key Length AN 1 N1 1, 2, or b, where b denotes a blank space 0, 1 = Single length 2 = Double length 3 = TR-31 length 04 Key AN 16, 32, or 33-512 AN 16 or 32 - key is variant 05 The encrypted key (in hexadecimal characters) of the length specified in the Key Length tag. AN 80 or AN 96 -key is TR-31 Key Block If the length of tag 04 is 80 or 96 bytes, the key is a TR-31 Key Block key. AN 6 4 or 6 hexadecimal check digits or spaces. Check Digits Note: Tag 01 is mandatory in MAC key response messages. Key response messages in which tag 01 is omitted are treated as PIN key response messages. Example data element The following is an example of the S-96 data element for a PIN key change request where the index is 1 and the key length is single-length: 0190100200020011030011 Key Value Description 019 The three-position data element length indicator. 01 The tag identifier for the key type. 002 The length of the tag 01 data. 00 The variable data for tag 01, indicating that a PIN key is being requested. 02 The tag identifier for the key index. 001 The length of the tag 02 data. 1 the variable data for Tag 02, indicating to use a key index of 1. 03 The tag identifier for the key length. 001 The length of the tag 03 data. 1 The variable data for Tag 03, indicating to use a singlelength key. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 362 Data element definitions S-100: Receiving Institution Identification Code Format: LLVAR N ..11 TDEs: Receiving Institution (tde.rcv_inst_cntry_cde, tde.rcv_inst_id_cde) The Receiving Institution Identification Code data element contains a code that identifies the institution receiving a request message. This data element is included because of its potential need by an acquirer host sending a request through BASE24‑eps without knowledge of who the end recipient is to be. S-102: Account Identification 1 S-103: Account Identification 2 Format: LLVAR ANS ..28 TDEs: Account 2 (tde.acct2_num, tde.acct2_typ, tde.acct2_set) The Account Identification 2 data element contains a series of digits and/or characters used to identify a customer account or relationship. This data element always identifies the to account in a transaction (for example, the account being credited in a transfer transaction). S-123: Reserved for Private Use Format: LLLVAR ANS ..999 TDEs: Varies by tag The Reserved for Private Use (S-123) data element is used for a number of purposes, depending on the information carried. Use of tags This data element carries tagged data items. The tags defined for this data element are listed below. Tagged data items are structured in the following manner: a tag identifying the type of data, followed immediately by a three-digit length (LLL) identifying the length of the data, followed immediately by the data itself. The data type can be alphanumeric or special characters, but ACI recommends using alphanumeric characters. Tag + LLL + data. Tagged data varies in length depending on the tag, and multiple tagged data items can be included in any order within the data element. Use of subtags Some tags use subtags to identify the various data fields involved in the file action. Refer to the specific tag documentation for descriptions of the supported subtags and their purposes. Subtag data is structured as follows: the subtag identifying the type of field data, followed immediately by a threedigit length (LLL) identifying the length of the field data, followed immediately by the field data itself. Subtag + LLL + field data. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 363 Data element definitions Multiple subtags can be present within a single tag, and can be in any order within the tag. S-123: Tag 01, Address Verification Data Format: AN 33 TDEs: Address Verification (tde.addr, tde.zip_cde, tde.addr_vfn_typ) This tag contains the following address verification data, as described below. Tag 01: Address Verification Data Position 1–20 Description Address Length 20 The cardholder billing address used when performing address verification. All information that is numeric in nature must be entered as numeric data (e.g., First Street must be entered as 1st Street). 21 Option Code 1 The option code for address verification processing. Valid values are as follows: 0 = Unknown 1 = Open 2 = Address verification data only 3 = Address verification and authorization BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 364 Data element definitions Tag 01: Address Verification Data Position 22 Description Result Code Length 1 A code indicating the result of address verification processing. Valid values are as follows: A = Address matches. ZIP does not. Acquirer rights not implied. B = Visa only. Street address match; postal code not verified due to incompatible formats (Acquirer sent both street address and postal code.) Acquirer rights not implied. C = Visa only. Street address and postal code not verified due to incompatible formats. (Acquirer sent both street address and postal code.) D = Visa only. Street address and postal code match. Acquirer rights not implied. E = Content error. F=Visa only. Street address and postal code match. Applies to U.K. only. G = Visa only. Global non-AVS participant; address is not verified for international transaction. Acquirer rights not implied. I= Visa only. Address information not verified for international transaction. M = Visa only. Street address and postal code match. Acquirer rights implied. N = No match (Acquirer sent postal code only, or street address only, or both postal code and street address) P =Visa only. Postal code match; acquirer sent both postal code and street address, but street address not verified due to incompatible formats. Acquirer rights not implied. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 365 Data element definitions Tag 01: Address Verification Data Position 22 Description Length R = Retry: System unavailable or timed out. (Issuer processor ordinarily performs its own AVS but was unavailable.) Available for U.S. issuers only. S = Not applicable. If present, replaced with U by V.I.P. Acquirer rights not implied. Available for U.S. issuers only. T = Address verification not performed. U = Address not verified. Acquirer rights implied. (e.g., Visa tried to perform check on issuer processor’s behalf but no AVS information was available on record, issuer processor is not an AVS participant, or AVS data was present in the request but issuer did not return an AVS result.) W = Whole ZIP matches, but street address does not. X = Whole ZIP matches. Y = Street address and postal code match. Z = ZIP matches, address does not match or address not included in request. Acquirer rights not implied. 0 = null BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 366 Data element definitions Tag 01: Address Verification Data Position 23 Description Status Code Length 1 A = Address. Addresses matched, but postal codes did not match. E = Error. The transaction was not eligible for address verification or an editing error occurred while attempting to process the message. N = No. Addresses did not match and postal codes did not match. R = Retry. Primary and secondary authorizers were unavailable or declined the transaction and address verification was not performed on the BASE24‑eps system. S = Service not supported. The BASE24‑eps system authorized the transaction, but did not have the component needed for address verification. U = Unavailable. Address information was not available to the processor performing address verification. W = Whole ZIP. Nine-digit postal codes matched, but addresses did not match. X = Exact. Addresses and nine-digit postal codes matched. Y = Yes. Addresses and five-digit postal codes matched. Z = ZIP. Five-digit postal codes matched, but addresses did not match. b = Address verification information was not included in this transaction (b denotes a blank character). 0 = Address verification information was included in this transaction, but was not verified. A transaction to be verified by a host or interchange carries this code. A transaction to be verified on the BASE24‑eps system, but declined before address verification could be performed also carries this code. 24–32 Zip Code 9 The cardholder billing postal code received with the transaction if address verification was performed. When the transaction contains an address verification status code without an address or a postal code, this field contains zeros. If address verification was not performed, this field contains blanks. In the United States, postal code is synonymous with ZIP code. 33 Address Verification Type 1 0 = AVS not supported (avs_typ_not_supported). Default. 1 = Complete address data (avs_typ_compl_addr_data). 2 = Condensed version 2 (avs_typ_condensed_2). 3 = Condensed version 3 (avs_typ_condensed_3). 4 = Condensed version 4 (avs_typ_condensed_4). BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 367 Data element definitions S-123: Tag 02, Card Verification Data Format: AN 9 TDEs: Card Verification (tde.crd_vrfy_rslt, tde.crd_vrfy_disp, tde.crd_vrfy_disp_set) or CID Verification This tag contains the following card verification data, as described below. Tag 02: Card Verification Data Position 1 Description Card Verification Disposition Length 1 A code indicating the disposition of card verification. Valid values are as follows: C = Invalid CVD, continue D = Invalid CVD, deny R = Invalid CVD, referral b = Not applicable (b denotes a blank character). 2 Card Verification Data Presence Indicator 1 A code indicating whether the card verification digits (CVD) are present on the card, and if so, the result of the CVD check. Valid values are as follows: 0 = CVD value is deliberately bypassed or not provided by the merchant. 1 = CVD value is present. 2 = CVD value is on the card, but is illegible. 3 = CVD value is not on the card. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 368 Data element definitions Tag 02: Card Verification Data Position 3 Description Card Verification Result Length 1 A code indicating the result of card verification processing. Valid values are as follows: 0 = Card verification was performed and the CVD was valid. 1 = Card verification was performed and the CVD was invalid. 2 = Authorizing entity has not yet attempted card verification or could not verify the CVD due to a security device error. 3 = Card verification failed. 4 = Card verification failed due to an invalid parameter. 5 = Card verification failed due to a track length error. 6 = Card verification was not performed because the CVD was not on the card. Not all cards have an encoded or printed CVD value. 7 = Card verification was not performed. Either the merchant ignored the CVD on purpose or the cardholder falsely indicated that the CVD was not on the card. 8 = The issuer has not certified or has not provided the encryption keys to the interchange. 9 = Card verification was not performed because the card verification keys were not present. 4 Manual Card Verification Disposition 1 A code indicating the disposition of manual card verification. Valid values are as follows: C = Invalid CVD2, continue D = Invalid CVD2, deny R = Invalid CVD2, referral 5 Manual Card Verification Data Presence Indicator 1 A code indicating whether the manual card verification digits (CVD2) are present on the card, and if so, the result of the CVD2 check. Valid values are as follows: 0 = CVD2 value is deliberately bypassed or not provided by the merchant. 1 = CVD2 value is present. 2 = CVD2 value is on the card, but is illegible. 3 = CVD2 value is not on the card. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 369 Data element definitions Tag 02: Card Verification Data Position 6 Description Manual Card Verification Result Length 1 A code indicating the result of manual card verification processing. Valid values are as follows: 0 = Card verification was performed and the CVD2 was valid. 1 = Card verification was performed and the CVD2 was invalid. 2 = Authorizing entity has not yet attempted card verification or could not verify the CVD2 due to a security device error. 3 = Card verification failed. 4 = Card verification failed due to an invalid parameter. 5 = Card verification failed due to a track length error. 6 = Card verification was not performed because the CVD2 was not on the card. Not all cards have an encoded or printed CVD2 value. 7 = Card verification was not performed. Either the merchant ignored the CVD2 on purpose or the cardholder falsely indicated that the CVD2 was not on the card. 8 = The issuer has not certified or has not provided the encryption keys to the interchange. 9 = Card verification was not performed because the card verification keys were not present. 7 CID Disposition 1 A code indicating the disposition of card verification for an American Express card. Valid values are as follows: C = Invalid CID, continue D = Invalid CID, deny R = Invalid CID, referral 8 CID Presence Indicator 1 A code indicating whether the Card Identifier (CID) codes are present on the card, and if so, the result of the CID check. Valid values are as follows: 0 = CID value is deliberately bypassed or not provided by the merchant. 1 = CID value is present. 2 = CID value is on the card, but is illegible. 3 = CID value is not on the card. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 370 Data element definitions Tag 02: Card Verification Data Position 9 Description Length CID Verification Result 1 A code indicating the result of manual CID card verification processing. Valid values are as follows: 0 = Card verification was performed and the manual CID was valid. 1 = Card verification was performed and the manual CID was invalid. 2 = Authorizing entity has not yet attempted card verification or could not verify the manual CID due to a security device error. 3 = Card verification failed. 4 = Card verification failed due to an invalid parameter. 5 = Card verification failed due to a track length error. 6 = Card verification was not performed because the CID2 was not on the card. Not all cards have an encoded or printed CID2 value. 7 = Card verification was not performed. Either the merchant ignored the CID2 on purpose or the cardholder falsely indicated that the CID2 was not on the card. 8 = The issuer has not certified or has not provided the encryption keys to the interchange. S-123: Tag 03, Manual CVD (CVD2) Format: AN 3 TDEs: Manual CVV (tde.man_cvv) Tag 03 contains the manually entered CVD value (CVD2). Only the leftmost 3 bytes of the CVD2 are used. S-123: Tag 04, Manual CID Format: AN 4 TDEs: CID This tag is currently reserved for future use. Tag 04 contains a manually entered American Express Card Identifier (CID) code value. S-123: Tag 05, Visa CPS Data Format: AN 46 TDEs: Visa Custom Payment Service Tag 05 contains the Visa Custom Payment Service (CPS) fields as described below. Refer to the appropriate Visa documentation for additional information on CPS. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 371 Data element definitions Tag 05: Visa CPS Data Position 1 Description Authorization Characteristics Indicator Length 1 A code used by the acquirer to request CPS qualification. If qualified, VisaNet Integrated Payment System (VIP) changes the code to reflect the results of its CPS Evaluation. Valid values that can be sent by the acquirer are as follows: I = Incremental to previously approved transaction O = Original authorization for which incremental authorizations may be received. P = Preferred customer R = Recurring payment Y = Yes, transaction participation requested Authorization Characteristics Indicator continued Valid values that VIP can return to the acquirer if the request contained a value of Y are as follows. All values, except N, indicate that the transaction is qualified for the reason stated. A = Card present; magnetic stripe read and sent or, for Retail 2 (keyentered) or Commercial Card submissions, the magnetic stripe is not included but other submission requirements are met; signature obtained; CVV requested if magnetic stripe is present: All CPS market segments. C = Meets requirements for A above plus merchant name, location present and cardholder-activated terminal indicator set, but no signature required; AFD. E = Meets requirements for A, plus merchant name and location (enriched name and location data) present; also valid for Retail 2 (keyentered), Commercial Card, and Visa Cash Back submissions. F = Meets requirements for CPS/Account Funding. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 372 Data element definitions Tag 05: Visa CPS Data Position Description Length Authorization Characteristics Indicator continued Valid values that VIP can return to the acquirer if the request contained a value of Y are as follows. All values, except N, indicate that the transaction is qualified for the reason stated. K = Meets requirements for CPS/Retail Key Entry Fee program. This payment service is intended for face-to-face, retail key-entered transactions where the magnetic stripe cannot be read. Although select developing market segments are eligible for this payment service, these transactions are assessed the CPS/Retail 2 fee. M = Meets national payment service requirements with no address verification: Direct Marketing (currently M used for Germany only). N = Transaction is not qualified. U = Meets requirements for Basic CPS/Electronic Commerce program (3-D Secure) V = Meets address verification requirements; verification requested for card-not-present transactions (such as Transport market segments); also meets CPS/card-not-present without SET requirements. W = Meets requirements for Basic CPS/Electronic Commerce program (non-3-D Secure) Authorization Characteristics Indicator continued Valid values that VIP can return to the acquirer if the request contained a value of R are as follows. R = Meets Direct Marketing recurring payment qualification without address verification request. U.S. only; also meets CPS/card-notpresent with SET requirements (no address verification required). N = Transaction is not qualified. Valid values that VIP can return to the acquirer if the request contained a value of I are as follows. I = Incremental authorization qualified for CPS, card may or may not be present: Hotel/Auto Rental N = Transaction is not qualified. Valid values that VIP can return to the acquirer if the request contained a value of P are as follows. P = Meets requirements for Preferred Customer, card not present: Hotel/ Auto Rental and Transport. N = Transaction is not qualified. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 373 Data element definitions Tag 05: Visa CPS Data Position Description Length Authorization Characteristics Indicator continued Valid values that a VIP can return to the acquirer if the request contained a value of ?? are as follows. A = Reauthorize for full amount D = Delayed charges I = Installment Payment N = Incremental authorization P = Reauthorize for partial amount (Partial/Split shipment) R = Recurring Payment S = Resubmission T = Account top-up U = Unscheduled stored credential transaction X = No show 2–3 Chargeback Rights Indicator 2 A code notifying the issuer of the CPS chargeback protection level assigned by BASE II and passed to the issuer in deferred clearing advices. Valid values are as follows: 00 = Card present—non-T&E 01 = Card present—T&E 02 = Card-not-present AVS—non-T&E 03 = Card-not-present AVS—T&E 04 = Card-not-present–Preferred Customer—T&E 05 = Card present–No Signature—non-T&E 08 = Card present/Key-entered CPS/Retail—non-T&E 09 = Card present/Key-entered CPS/Retail—T&E 10 = Card-not-present—T&E, Non-3-D Secure 11 = Card-not-present—non-T&E, Non-3-D Secure 12 = Card-not-present—T&E, 3-D Secure 13 = Card-not-present—non-T&E, 3-D Secure 14 = Card Present—CPS/Small-Ticket/Non-T&E or Contactless Spaces Indicator Not Set 15 = U.S. ATM rules apply 16 = Card Present—PIN-authenticated POS 17 = Card Present—Electronically read (U.S. region only) b = Indicator not set (where b denotes a blank space) bb =U.S. ATM rules not applicable (where b denotes a blank space) 4–5 Duration 2 The number of days (01–99) anticipated for auto rental or hotel stay. For auto rental prepays and hotel deposits, the value reflects the number of days covered by the advance payment. Used only in authorization requests. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 374 Data element definitions Tag 05: Visa CPS Data Position 6 Description Market-Specific Data Identifier Length 1 A code identifying the industry for which market-specific data has been provided in other CPS fields. Used only in authorization requests. Valid values are as follows: A = Auto rental H = Hotel N = Failed market-specific data edit The acquirer sets this field to A or H if a value is present in the Duration field. The acquirer sets this field to H if a value is present in the Prestigious Property Indicator field. V.I.P. sets this field to a value of N if this field, the Duration field, or the Prestigious Property Indicator field are invalid. 7 Prestigious Property Indicator 1 A code used by CPS acquirers in the Visa USA Prestigious Lodging program to identify a property floor limit. Used only in authorization requests. Valid values are as follows: D = Prestigious property with $500 limit B = Prestigious property with $1,000 limit S = Prestigious property with $1,500 limit 8 Requested Payment Service 1 A code for dual-message acquirers that define their choice of a specific custom payment service in the deferred clearing transaction. Valid values for the U.S. region are as follows: A = CPS retail credit card D = CPS retail check card E = CPS retail key entry G = CPS/Electronic commerce—Basic H = CPS/Account funding J = CPS/Electronic commerce—Preferred 1 = CPS passenger transport 2 = CPS passenger transport 2 (good only for exception item processing) 3 = CPS hotel 4 = CPS hotel 2 (good only for exception item processing) 5 = CPS auto rental 6 = CPS auto rental 2 (good only for exception item processing) 7 = CPS card not present 8 = CPS automated fuel dispenser Valid values for non-U.S. regions are as follows: A = CPS retail/petrol B = CPS restaurants C = CPS card not present (Germany only) BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 375 Data element definitions Tag 05: Visa CPS Data Position 9–23 Description Length Transaction Identifier 15 A Visa-generated unique identifier for each original transaction which links original authorization requests to subsequent messages, such as reversals. 24–27 Validation Code 4 A code calculated by the VisaNet Integrated Payment System (VIP) to ensure key fields in the authorization requests match their respective fields in BASE II deferred clearing messages. 28–29 Multiple Clearing Sequence Number 2 Used by the VisaNet Integrated Payment System (VIP) to identify a specific BASE II clearing transaction record when multiple clearing records are submitted for single authorization. This field is used in conjunction with the Multiple Clearing Sequence Count field (positions 30– 31). 30–31 Multiple Clearing Sequence Count 2 Used by the VisaNet Integrated Payment System (VIP) to identify the total number of BASE II clearing transactions when multiple clearing records are submitted for a single authorization. This field is used in conjunction with the Multiple Clearing Sequence Number field (positions 28–29). 32-46 Original Transaction ID 15 A Visa-generated original unique identifier for each original transaction which links original authorization requests to subsequent messages, such as reversals. S-123: Tag 06, MasterCard Interchange Compliance Information Format: AN 15 TDEs: MasterCard Interchange Compliance (tde.mcici_date, tde.mcici_downgrade_rsn_cde, tde.mcici_ref_num) Tag 06 contains MasterCard interchange compliance information, as described below. Tag 06: MasterCard Interchange Compliance Information Position 1–4 Description Date Length 4 The date in MMDD format. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 376 Data element definitions Tag 06: MasterCard Interchange Compliance Information Position 5–6 Description Length Downgrade Reason Code 2 A code indicating the reason the transaction was downgraded when it was intended for CPS qualification but failed to meet the applicable validation criteria. Refer to Visa’s V.I.P. System SMS POS (Visa and Visa Electron) Technical Specifications, Volume 2 for descriptions of valid downgrade reason codes. 7–15 Reference Number 9 The code assigned by the interchange to a transaction that has met the required compliance edits. S-123: Tag 07, E-Commerce Indicator Format: AN 1 TDEs: E-Commerce Tag 07 is a one-digit field that contains the e-commerce indicator. Valid values are: Indicator Description 0 Not an electronic commerce transaction 1 Single mail/telephone order transaction 2 Recurring mail/telephone order transaction 3 Mail/telephone order installment payment 4 Unknown mail/telephone order transaction 5 Secure electronic transaction with cardholder certificate 6 Secure electronic transaction without cardholder certificate 7 Channel-encrypted electronic commerce transaction 8 Nonsecure electronic commerce transaction 9 Non-authenticated security transaction that does not comply with secure electronic transaction and the merchant supports secure electronic transaction A Electronic transaction with digital signature B Secure electronic transaction with channel encryption provided by interchange C Electronic transaction, not secured D MasterPass generated transaction E Digital Secure Remote Payment with Universal Cardholder Authentication Field (UCAF) F Partial Shipment or Recurring Payment G Digital Secure Remote Payment with Full EMV Data I Electronic 3DS 2.0 BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 377 Data element definitions S-123: Tag 08, Secure Internet Validation Format: AN 4 TDEs: Secure Internet Validation • • • • • • • • • • • • • tde.siv_bad_disp tde.siv_bad_disp_set tde.siv_chk tde.siv_chk_set tde.siv_disp tde.siv_disp_set tde.siv_not_prsn_disp tde.siv_not_prsn_disp_set tde.siv_prf tde.siv_prfl_set tde.siv_prsn tde.siv_prsn_set tde.siv_rslt Electronic Commerce Universal Card Authentication Field Tag 08 contains Secure Internet Validation fields as described below. Tag 08: Secure Internet Validation Position 1 Description Secure Internet Validation Disposition Length 1 A code indicating the action to be taken when the CAVV or AAV associated with a transaction request is considered to be invalid. C = Continue processing the transaction. D = Deny the transaction. R = Refer the transaction. 2 Secure Internet Validation Presence Indicator 1 A code indicating whether the CAVV/AAV is present in the transaction, and if so, the result of the SIV check. 0 = CAVV/AAV is deliberately bypassed or not provided by the merchant 1 = CAVV/AAV is available in the transaction 2 = CAVV/AAV is not available in the transaction BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 378 Data element definitions Tag 08: Secure Internet Validation Position 3–4 Description Length Secure Internet Validation Result 2 A code indicating the result of secure internet validation. Valid values are as follows: 0 = No error, CAVV/AAV validated 1 = No error, CAVV/AAV not validated 2 = Security device failure 3 = Verification failure 4 = Invalid parameter 5 = CAVV/AAV not present 6 = CAVV/AAV not validated, data, database or system error 7 = CAVV/AAV not validated, authorization attempt 8 = CAVV/AAV not validated, valid attempt 9 = CAVV/AAV not validated, no issuer participation 10 = CAVV/AAV not validated, issuer error 11 = CAVV/AAV not validated, valid attempt by interchange 12 = CAVV/AAV validated, valid attempt by interchange 13 = CAVV/AAV not validated, valid attempt by issuer 14 = CAVV/AAV validated, valid attempt by issuer 15 = CAVV/AAV validated, information only 16 = CAVV/AAV not validated, attempt 17 = CAVV/AAV not validated, no file 18 = CAVV/AAV not validated, system error8 19 = CAVV/AAV not validated, acquirer participates, issuer does not 20 = Duplicate CAVV/AAV validation 21 = CAVV/AAV not validated, no code sent 22 = CAVV/AAV validated, verify attempts 23 = CAVV was not validated - no keys configured 99 = CAVV not present (SIV initialization value) S-123: Tag 09, Secure E-Commerce Data Format: AN 144 TDEs: Secure E-Commerce (tde.secom_chldr_cert_num, tde.secom_mrch_cert_num, tde.secom_txn_stain, tde.secom_xid) Tag 09 contains secure e-commerce fields, as described below. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 379 Data element definitions Tag 09: Secure E-Commerce Data Position Description 1–32 Length Cardholder Certificate Serial Number 32 The cardholder certificate serial number for secure e-commerce. 33–64 Merchant Certificate Serial Number 32 The merchant certificate serial number for secure e-commerce. 65–104 Transaction Stain 40 A hash value calculated by applying a secure hash algorithm to the XID and CardSecret (a secret SETdefined value known only to the cardholder and the issuer of the cardholder certificate). 105–144 Transaction Identifier (XID) 40 A unique transaction identifier assigned to a SET transaction. S-123: Tag 10, UCAF Data Format: Variable based on the subtags included TDEs: Electronic Commerce Universal Card Authentication Field Tag 10 contains Universal Cardholder Authentication Field (UCAF) information fields, as described below. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 380 Data element definitions Tag 10: UCAF Data Position 1 Description UCAF Indicator Length 1 The authentication collection indicator Valid values: 0 = UCAF data collection is not supported at merchant's website (ucaf_not_sppt). This could also indicate that a downgrade occurred. 1 = UCAF data collection is supported by merchant's website, but UCAF data may not be populated (ucaf_sppt). If UCAF data is present, it should contain an attempt AAV for MasterCard SecureCode. 2 = UCAF data collection is supported by merchant's website, and UCAF data was populated with a fully authenticated AAV (ucaf_populated). 3 = UCAF data collection is supported by the merchant, and UCAF data is present in static AAV form (ucaf_mrch_sppt). 4 = MasterCard risk-based decision-making (ucaf_mc_rsk_dcsn_remt_pmnts) 5 = Issuer risk-based decision-making (ucaf_iss_rsk_dcsn) 6 = Merchant risk-based decision-making (ucaf_mrch_rsk_dcsn) 7 = Partial shipment or recurring payment (ucaf_partial_shipment_recur) 2–33 UCAF Data 32 Universal Cardholder Authentication Field (UCAF) data 34 UCAF Original Indicator 1 Valid values: 0 = UCAF data collection is not supported at merchant's website (ucaf_not_sppt). 1 = UCAF data collection is supported by merchant's website, but UCAF data was not populated (ucaf_sppt). 2 = UCAF data collection is supported by merchant's website, and UCAF data was populated (ucaf_populated). 3 = UCAF data collection is supported by the merchant, and UCAF data is present (ucaf_mrch_sppt). 4 = MasterCard risk-based decision-making (ucaf_mc_rsk_dcsn_remt_pmnts) 5 = Issuer risk-based decision-making (ucaf_iss_rsk_dcsn) 6 = Merchant risk-based decision-making (ucaf_mrch_rsk_dcsn) 7 = Partial shipment or recurring payment (ucaf_partial_shipment_recur) 35 UCAF Downgrade Reason Code 1 Valid values: 0 = Missing Universal Cardholder Authentication Field (UCAF) 1 = Invalid Universal Cardholder Authentication Field (UCAF) BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 381 Data element definitions Tag 10: UCAF Data Position 36 Description Length Program Protocol 1 Valid values: 1 = 3D Secure Version 1.0 (3DS 1.0) 2 = 3D Secure Version 2.0 (3DS 2.0) 37-72 Directory Server Transaction ID 36 S-123: Tag 11, Recurring Payment Indicator Format: AN 1 TDEs: Recurring Payment Data (tde.recur_pmnt_data, tde.recur_pmnt_data_set) Tag 11 contains the one-character Recurring Payment Indicator. Valid values are: • • • • • • • • • • A - Reauthorize for full amount C - Credentials stored from transaction D - Delayed changes I - Installment Payment N - Incremental Authorization P - Reauthorize for partial amount R - Recurring Payment S - Resubmission T - Account top-up X - No Show S-123: Tag 12, Point of Service Additional Format: AN 3 or 6 to 9 TDEs: Point of Service Additional Tag 12 contains the Point of Service Additional field in the ISO format as described below. Tag 12: Point of Service Additional Position 1 Description POS Transaction Security Indicator Length 1 A code indicating the card acceptors security level. 0 - No concern 1- Suspected fraud 2 - ID verified 2 Reserved (a reserved field) BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 1 382 Data element definitions Tag 12: Point of Service Additional Position 3 Description Cardholder Activated Terminal Level Length 1 A code indicating whether the cardholder activated the terminal with the use of the card and the CAT security level. 0 - None 1 - Admin PIN 2 - Self-service terminal 3 - Limited amount terminal 4 - In-flight commerce 5 - Reserved 6 - E-commerce 7 - Transponder 8 - Mobile 9 - MPOS 4 TLE Indicator 1 A code indicating whether or not the POS terminal from which the transaction initiated is Terminal Line Encryption (TLE) certified. 1 = Not certified 2 = Certified Blank = Data is not set (value not mapped to the TDE) 5 UKPT/DUKPT Indicator 1 A code indicating whether or not the POS terminal from which the transaction occurred is Unique Key Per Terminal/Derived Unique Key Per Terminal (UKPT/DUKPT)-certified. 1 = Not certified 2 = Certified Blank = Data is not set (value not mapped to the TDE) 6 Fall Forward to Contact transaction Indicator 1 A code indicating whether or not the current transaction is a fall forward to contact transaction. 1 = mapped to true in the TDE, showing that the transaction is a fall forward to contact 2 = mapped to false in the TDE, showing that the transaction as nonfall forward to contact Blank = Data is not set (value not mapped to the TDE) 7 ATM Outside Home Territory Indicator 1 A code indicating whether the terminal is located outside the Home Territory. Space = Located in Home Territory N = Located in Home Territory Y = Located Outside Home Territory BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 383 Data element definitions Tag 12: Point of Service Additional Position 8 Description Length Additional Card Data Input Mode 1 A code providing additional information about the method used to input the information from the card to the terminal. Valid values are: 0 = Unknown 1 = Interactive Voice Response (IVR) 2 = Pull payments where merchants scan customer information 3 = Push payments where customers scan merchant information 4 = Card Data was key entered with keyed PCSC 5 = Card Data was read from the magnetic stripe with keyed PCSC 9 mPOS Acceptance Device 1 A code indicating the type of mobile point of sale (mPOS) device. Valid values are: 0 = Unknown 1 = Dedicated mPOS Terminal with PCI compliant dongle (with or without key pad) 2 = Off the Shelf Mobile Device S-123: Tag 13, Visa Indicator Format: AN 8 TDEs: Visa Indicator (tde.visa_ind_tag) Tag 13 contains Visa Indicator fields as described below. Tag 13: Visa Indicator Position 1 Description Deferred Billing Indicator Length 1 A code indicating whether billing is deferred for the transaction. The only valid value is D (deferred billing). 2 Existing Debt Indicator 1 A code indicating whether this transaction is a payment on existing debt. The only valid value is 9 (payment on existing debt). 3 Relationship Participant Indicator 1 A code indicating whether the merchant for the transaction participates in the Visa U.S.A. Relationship Manager Service. The only valid value is R (relationship participant). 4 Remote Terminal Indicator 1 A code indicating whether this transaction originated from a remote terminal. The only valid value is 1 (remote terminal). BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 384 Data element definitions Tag 13: Visa Indicator Position 5 Description Length Digital Commerce Program Indicator 1 A code indicating whether the merchant for the transaction participates in the Digital Commerce Program. Valid values are: • • 6 0: Not provided 1: Digital Commerce Program indicator Visa Special Condition Codes 1 Valid values are: • 7-8 7: Purchase of cryptocurrency 2 An indicator specifying that a token-based e-commerce request was initiated using Visa Digital Commerce. Valid values are: • • Spaces: Not set 01: Secure Remote Commerce Indicator S-123: Tag 14, Internet IP Address Format: AN 15 TDEs: Not applicable (reserved for future use) Tag 14 contains the customer’s Internet IP address (in the format of nnn.nnn.nnn.nnn). The format of an IP address is a 32-bit numeric address written as four numbers separated by periods. Each number can be zero to 255. For example, 1.160.10.240 could be an IP address. S-123: Tag 15, Merchant Advice Code Format: AN 1 TDEs: MasterCard Merchant Advice Code (tde.mrch_advc_cde) Tag 15 contains the one-character merchant advice code for recurring payment transactions. Valid values are as follows: Code Description 1 New Account Information 2 Try again later 3 Do not try again (for recurring payments transactions) 4 Cancel recurring payment service S-123: Tag 16, American Express Customer ID Number Format: AN 4 TDEs: American Express Customer ID (tde.amex_cust_id) BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 385 Data element definitions Tag 16 contains the four-character American Express customer ID number. S-123: Tag 17, American Express Auto Rental Data Format: AN 119 TDEs: Amex Auto Rental Tag 17 contains American Express auto rental data, as described below. Tag 17: American Express Auto Rental Data Position 1–9 Description Agreement Number Length 9 The invoice number of the rental agreement (issued by the rental agency) signed by the card member. 10–27 Audit Adjustment Amount 18 The amount of any charges that were added to the contract after the vehicle was checked in (for example, mileage or damages). 28–35 Reference Code 8 A reference number used by American Express to obtain supporting information for a charge from the Service Establishment. 36–53 Rental City 18 The city in which the auto was rented. 54–65 Rental Date and Time 12 The date and time (YYMMDDhhmmss) on which the car was rented. 66–67 Rental State 2 The two-character state code identifying the state in which the auto was rented. 68–87 Renter Name 20 The name of the person who rented the car. 88–105 Return City 18 The city in which the car was returned. 106–117 Return Date and Time 12 The date and time (YYMMDDhhmmss) on which the car was returned. 118–119 Return State 2 The two-character state code identifying the state in which the auto was returned. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 386 Data element definitions S-123: Tag 18, American Express Lodging Data Format: AN 69 TDEs: American Express Lodging (tde.amex_lodging_tag) Tag 18 contains American Express lodging data, as described below. Tag 18: American Express Lodging Data Position 1–6 Description Arrival Date Length 6 The arrival date (MMDDYY) of the guest. 7 Charge Type 1 The type of purchase associated with the charge. Valid values are as follows: 0 = Reserved 1 = Lodging 2 = Restaurant 3 = Gift shop 4–9 = Reserved 8–13 Departure Date 6 The departure date (MMDDYY) of the guest. 14 Program Code 1 Indicates the reason for the charge.If there is no special circumstance, the value 1 must appear in this field. Valid values are as follows: 0 = Reserved 1 = Used if no other code pertains 2 = Assured reservation—no show 3 = CARDeposit 4 = Delayed charge 5 = Express service 6 = Assured reservation 7–9 = Reserved BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 387 Data element definitions Tag 18: American Express Lodging Data Position Description 15–23 Length Reference Code 9 A reference number used by American Express to obtain supporting information for a charge from the Service Establishment. 24–41 Room Rate 18 The per diem rate charged for the customer’s stay at the establishment. 42–51 Record of Charge Number 10 The original Record of Charge (ROC) invoice number, or another number associated with the charge. 52–69 Sales Tax 18 The total tax amount in dollars and cents. S-123: Tag 19, American Express General Retail Data Format: AN 57 TDEs: American Express General Retail Tag 19 contains American Express general retail data, as described below. Tag 19: American Express General Retail Data Position 1–4 Description Charge Code 1 Length 4 A code used to identify the type of purchase associated with the charge. This field is defined by American Express. 5–8 Charge Code 2 4 A code used to identify the type of purchase associated with the charge. This field is defined by American Express. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 388 Data element definitions Tag 19: American Express General Retail Data Position Description 9–12 Length Charge Code 3 4 A code used to identify the type of purchase associated with the charge. This field is defined by American Express. 13–16 Charge Code 4 4 A code used to identify the type of purchase associated with the charge. This field is defined by American Express. 17–20 Charge Code 5 4 A code used to identify the type of purchase associated with the charge. This field is defined by American Express. 21–29 Reference Code 9 A reference number used by American Express to obtain supporting information for a charge from the Service Establishment. 30–39 Record of Charge Number 10 The original Record of Charge (ROC) invoice number, or another number associated with the charge. 40–57 Sales Tax 18 The total tax amount in dollars and cents. S-123: Tag 20, American Express Restaurant Data Format: AN 116 TDEs: American Express Restaurant Data (tde.amex_rest_beverage_amt, tde.amex_rest_charge_cde1, tde.amex_rest_desc_cde, tde.amex_rest_food_amt, tde.amex_rest_ref_cde, tde.amex_rest_tab_roc_id, tde.amex_rest_tag, tde.amex_rest_tax_amt, tde.amex_rest_tip1_amt, tde.amex_rest_tip1_cde, tde.amex_rest_tip2_amt, tde.amex_rest_tip2_cde) Tag 20 contains American Express restaurant data, as described below. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 389 Data element definitions Tag 20: American Express Restaurant Data Position 1–18 Description Beverage Amount Length 18 The total cost of beverages, if itemized separately from the food. 19–22 Charge Code 1 4 Identifies the type of purchase associated with the charge. This field is defined by American Express. 23 Description Code 1 A code defining the type of charge. Valid values are as follows: 0 = Food 1 = Food or beverage 2 = B-MY-GST 3–9 = Arbitrary A–Z = Arbitrary 24–41 Food Amount 18 The total cost of the food, or the food and beverages, if these charges are combined on the original Record of Charge. 42–50 Reference Code 9 A reference number used by American Express to obtain supporting information for a charge from the Service Establishment. 51–60 Record of Charge Number 10 The original Record of Charge (ROC) invoice number, or another number associated with the charge. 61–78 Tax Amount 18 The total tax amount in dollars and cents. 79–96 Tip 1 Amount 18 The amount of the tip given to the employee identified by the Tip 1 Code field. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 390 Data element definitions Tag 20: American Express Restaurant Data Position Description 97–114 Length Tip 2 Amount 18 The amount of the tip given to the employee identified by the TIP2CDE field. 115 Tip 1 Code 1 A code identifying an employee receiving a tip. 116 Tip 2 Code 1 A code identifying an employee receiving a tip. S-123: Tag 21, American Express Oil Data Format: AN 44 TDEs: American Express Oil Data (tde.amex_oil_charge_cde1, tde.amex_oil_ref_cde, tde.amex_oil_tab_roc_id, tde.amex_oil_tax_amt) Tag 21 contains American Express oil data, as described below. Tag 21: American Express Oil Data Position 1–4 Description Charge Code 1 Length 4 A code used to identify the type of purchase associated with the charge. This field is defined by American Express. 5–16 Reference Code 12 A reference number used by American Express to obtain supporting information for a charge from the Service Establishment. 17–26 Record of Charge Number 10 The original Record of Charge (ROC) invoice number, or another number associated with the charge. 27–44 Sales Tax Amount 18 The total tax amount in dollars and cents. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 391 Data element definitions S-123: Tag 22, Terminal Type Format: AN 2 TDEs: Terminal Type Tag 22 contains the POS condition code – terminal type. This field identifies the type of terminal from which the transaction was initiated. Valid values are as follows: Code Description 00 Administrative terminal 01 POS terminal 02 ATM terminal 03 Home terminal 04 ECR 05 Dial terminal 06 Travelers check machine 07 Fuel machine 08 Scrip machine 09 Coupon machine 10 Ticket machine 11 Point-of-Banking (POB) terminal 12 MICR terminal at teller 13 Franchise teller 14 Personal banking 15 Public utility 16 Vending 17 Self-service 18 Authorization 19 Payment 20 VRU unit 21 Smart phone 22 Interactive television 23 Personal Digital Assistant (PDA) 24 Screen phone 25 Internet 26 MICR terminal 27 Mobile POS BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 392 Data element definitions S-123: Tag 23, OAR Maximum Accounts Data Format: AN 4 TDEs: OAR Maximum Accounts Data Tag 23 contains OAR maximum accounts data, as described below. Tag 23: OAR Maximum Accounts Data Position Description 1–3 Length OAR Max Accounts per Send 3 The maximum number of accounts an acquirer can handle per message. 4 OAR Acquirer Capabilities 1 A code indicating whether to send both sides (from and to accounts) at the same time or whether to send one side (from or to accounts) at a time. S-123: Tag 24, Acquirer Interface Action Code Format: AN 6 TDEs: Acquirer Network Action Code This tag is mapped to and from the Acquirer Network Action Code TDE. The original action code value from the endpoint is also retained in this TDE. Tag 24 contains the action code for the acquiring network. This code is sent in P-39 in messages sent to interchanges. S-123: Tag 25, Issuer Interface Action Code Format: AN 6 TDEs: Issuer Network Action Code This tag is mapped to and from the Issuer Network Action Code TDE. The original action code value from the endpoint is also retained in this TDE. Tag 25 contains the action code for the issuing network. This code is received in P-39 in messages received from interchanges. S-123: Tag 26, Prepay Transaction Data Format: AN 70 TDEs: Prepay Transaction Data Tag 26 contains data for a prepay (phone top up) transaction, as described below. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 393 Data element definitions Tag 26: Prepay Transaction Data Position Description 1–20 Activation Phone Number Length 20 The activation phone number for the prepay transaction. 21–36 Activation Code 16 The activation code (PIN) for the transaction. 37–56 Customer Phone Number 20 The customer’s phone number. 57 Approval Code Length 1 The length of the approval code (from the prepay supplier). 58–63 Approval Code 6 The approval code (from the prepay supplier). 64–66 Action Code 3 The action code (from the prepay supplier). 67–70 Activation Code 4 The message reason code (associated with the prepay supplier). S-123: Tag 27, Language Code Format: AN 5 TDEs: Language Code Tag 27 contains a five-byte code indicating the language in which the host should format text in a response (e.g., for a statement print transaction). This code is formatted as ll_CC, where ll is the two-byte alpha language indicator from ISO-639 in lower-case and CC is the two-byte alpha country code from ISO-3166 in upper-case. Note that the language indicator and country code are separated by an underbar (_). The combination of language indicator and country code allows you to differentiate between different usages of a particular language in different countries. For example, a language code of en_US specifies the English language as used in the United States while a code of en_GB specifies the English language as used in the United Kingdom; a language code of es_ES specifies the Spanish language as used in Spain while a code of es_MX specifies the Spanish language as used in Mexico. S-123: Tag 29, International Service Assessment Flag Format: AN 1 BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 394 Data element definitions TDEs: Visa Charge Indicator Tag 29 contains a one-byte code indicating whether an international service assessment (ISA) charge was assessed to the issuer for this transaction. Valid values are as follows, where b denotes a blank space: Code Description C A single currency ISA charge was assessed. R An ISA charge was assessed and rebated. S A multi-currency ISA charge was assessed. b Blank. An ISA charge was not assessed. The absence of this tag also implies that no ISA charge was assessed for the transaction. In request messages sent to the BASE24-eps system, you can either provide this tag set to a blank space, or not provide the tag at all, to indicate that an ISA charge was not assessed for the transaction. In request messages sent from the BASE24eps system to the host, an absence of the tag is used to indicate that an ISA charge was not assessed. BASE24eps never sends requests with this tag set to a blank space. S-123: Tag 30, Partial Authorization Indicator Format: AN 1 TDEs: Partial Authorization Indicator Tag 30 contains a one-byte code indicating whether a terminal acquirer supports partial authorizations. A value of 1 in this tag indicates that the terminal acquirer supports partial authorizations. Any other value in this field or omission of the field indicates that the terminal acquirer does not support partial authorizations. S-123: Tag 31, Visa Gateway Transaction Identifier Format: AN 15 TDEs: MasterCard Interchange Compliance Tag 31 contains acquirer reference data for the Visa authorization gateway for American Express or MasterCard transactions. This tag is required when Visa acquires American Express transactions using the Card Acceptance and Processing Network (CAPN) system message format. It is also required for the MasterCard Interchange Compliance (MIC) program. Tag 31: Visa Gateway Transaction Identifier Position 1–15 Description Gateway Transaction ID Format AN 15 Transaction information from the Visa authorization gateway for American Express tor MasterCard transactions. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 395 Data element definitions S-123: Tag 32, Purchase Amount Only Indicator S-123: Tag 33, Dynamic Card Verification Results Format: AN 3 TDEs: Dynamic Card Verification Results Tag 33 contains dynamic card verification values moved to and from the Dynamic Card Verification Results TDE. Note: Dynamic card verification digits (DCVD) from a contactless transaction are verified using a different algorithm from the standard algorithm used for card verification. For MasterCard PayPass cards, the DCVD is referred to as the CVC3. For Visa Wave cards, the DCVD is referred to as the dCVV. Tag 33: Dynamic Card Verification Results Position Description 1 Card Verification Disposition – Valid values are as follows: Format AN 1 C = Invalid DCVD, continue D = Invalid DCVD, deny R = Invalid DCVD, referral b = Not applicable ( b denotes a blank character) 2 Card Verification Data Presence Indicator – Valid values are as follows: AN 1 0 = DCVD value is deliberately bypassed or not provided by the merchant 1 = DCVD value is present 3 = DCVD value is not on the card BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 396 Data element definitions Tag 33: Dynamic Card Verification Results Position 3 Description Card Verification Result – Valid values are as follows: Format AN 1 0 = Card verification was performed and the DCVD was valid. 1 = Card verification was performed and the DCVD was invalid. 2 = Authorizing entity has not yet attempted card verification or could not verify the DCVD due to a security device error. 3 = Card verification failed. 4 = Card verification failed due to an invalid parameter. 5 = Card verification failed due to a track length error. 6 = Card verification was not performed because the DCVD was not on the card. 8 = The issuer has not certified or has not provided the encryption keys to the interchange. 9 = Card verification was not performed because the card verification keys were not present. 10 = Card verification was not performed due to missing data or because verification has been disabled. 99 = Card verification commands not supported by the HSM. b = No results present ( b denotes a blank character). S-123: Tag 35, Voice Authorization Transaction Identification Format: Variable based on the subtags included TDEs: Varies by subtag Tag 35 includes identification information for transactions generated from the BASE24-eps Voice Authorization user interface. A host can receive this information with transactions initiated using BASE24-eps Voice Authorization. Hosts should not return or send this information in messages to BASE24-eps. Tag 35 carries subtag data as shown in the table below. Note: BASE24-eps Voice Authorization is separately licensable, and this tag information is only present in the system if BASE24-eps Voice Authorization has been licensed. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 397 Data element definitions Tag 35: Voice Authorization Transaction/Screen Identification Subtag Description 01 User ID. The BASE24-eps user ID of the user who initiated the transaction from the Voice Authorization user interface. Format AN 16 TDE: User ID 02 Terminal IP Address of the Voice Authorization user interface that initiated the transaction. AN 20 TDE: User ID 03 Voice Authorization Acquirer/Issuer Transaction Indicator. Indicates whether the transaction is an acquirer or issuer transaction— based on the Voice Authorization window used to create the transaction. Valid values are as follows: N1 0 = Issuer transaction. 1 = Acquirer transaction. TDE: Voice Authorization Acquirer/ Issuer transaction S-123: Tag 36, EMV Status Data Format: AN 7 or 8 TDEs: EMV Status Tag 36 contains up to 8 bytes of EMV status data that is not carried by an EMV tag in the Integrated Circuit Card System Related Data (P-55) data element. The minimum length of the tag is 7 bytes. The length will be 8 bytes depending on the presence of the ATC Verification Result Status in the EMV Status TDE. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 398 Data element definitions Tag 36: EMV Status Data Position 1 Description ARQC Verification Status Format AN 1 A code indicating the result of authorization request cryptogram (ARQC) verification. Valid values are as follows: b = Not set, where b represents a blank space. 0 = ARQC not verified. 1 = ARQC was checked by the acquiring system or switch, but failed verification. 2 = ARQC was checked by the acquiring system or switch and passed verification. 3 = ARQC was checked by the BASE24‑eps or issuer system, but failed verification. 4 = ARQC was checked by the BASE24‑eps or issuer system and passed verification. Note: Values 1 and 2 refer to acquirer verification. Values 3 and 4 refer to issuer verification (if BASE24-eps verifies the ARQC, it is on behalf of the issuer). 2 Data Suspect Flag AN 1 A flag set by the acquirer to indicate whether the card authentication method (CAM) data is reliable. Valid values are as follows: b = Not set, where b represents a blank space 0 = CAM data is assumed to be correct (reliable) 1 = CAM data is unreliable 3 Last EMV Status AN 1 A flag indicating whether the card used to initiate a magnetic stripe transaction is a chip card. Valid values are as follows: b = Not set, where b represents a blank space 0 = Not a chip card 1 = Chip card BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 399 Data element definitions Tag 36: EMV Status Data Position 4–7 Description Reason Online Code Format AN 4 A code indicating the reason the transaction is to be authorized online or why a transaction has been completed locally. Values are defined in the ISO 8583 (1993) standard.In a request message, the valid values are as follows: bbbb = Not set, where b represents a blank space 1500 = ICC application, Common Data File unable to process 1501 = ICC application, Application Data File unable to process 1502 = ICC random selection 1503 = Terminal random selection 1504 = Terminal not able to process ICC 1505 = Online forced by ICC (CDF or ADF) 1506 = Online forced by card acceptor 1507 = Online forced by CAD to be updated 1508 = Online forced by terminal 1509 = Online forced by card issuer 1510 = Over floor limit 1511 = Merchant suspicious In an advice message that the terminal has previously attempted to send to the acquirer as a request message, this field contains the same value as in the original request message. In an advice message that the terminal has not previously attempted to send to the acquirer as a request message, the valid values are as follows: bbbb = Not set, where b represents a blank space 1004 = Terminal processed 1005 = ICC processed 1006 = Under floor limit 1007 = Stand-in processing at the acquirer’s option 8 ATC Verification Result status. 0 = Result not set 1 = Valid 2 = Out of range 3 = Sequence duplication 4 = Not valid BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 400 Data element definitions S-123: Tag 37, MDS Intermediate Network Facility Data Format: AN ..50 TDEs: MDS Maestro Tag 37 contains the Intermediate Network Facility Data used by MasterCard Debit Switch (MDS) for processing the following dispute transactions: adjustments, chargebacks, and representments. The value in this tag consists of alphanumeric characters and is variable-length up to 50 bytes. This tag maps to data element 62 (Intermediate Network Facility Data) in the MDS transaction message. For information about this data element and MDS transaction messages, refer to the MDS Online Specifications manual. S-123: Tag 38, MDS Network Data Format: AN 44 TDEs: MDS Maestro Tag 38 contains the Network Data used by MasterCard Debit Switch (MDS) for processing the following dispute transactions: adjustments, chargebacks, and representments. The value in this tag consists of alpha, numeric, and alphanumeric subelements totalling 44 bytes. This tag maps to data element 63 (Network Data) in the MDS transaction message. For information about this data element and MDS transaction messages, refer to the MDS Online Specifications manual. S-123: Tag 39, MDS Processor Private Data Format: AN ..50 TDEs: MDS Maestro Tag 39 contains the Processor Private Data used by MasterCard Debit Switch (MDS) for processing the following dispute transactions: adjustments, chargebacks, and representments. The value in this tag consists of alphanumeric characters and is variable-length up to 50 bytes. This tag maps to data element 127 (Processor Private Data) in the MDS transaction message. For information about this data element and MDS transaction messages, refer to the MDS Online Specifications manual. S-123: Tag 40, Acquirer Forwarding Institution Identification Format: N 11 TDEs: Acquirer Forwarding Institution Tag 40 contains the Acquirer Forwarding Institution Identification used for processing chargebacks. MasterCard Debit Switch (MDS) Note: This tag maps to data element 33 (Forwarding Institution Identification Code) in the MDS transaction message. For information about this data element and MDS transaction messages, refer to the MDS Online Specifications manual. S-123: Tag 41, Issuer Capture Date Format: N 6 (YYMMDD) TDEs: Issuer Capture Date BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 401 Data element definitions Tag 41 contains the Issuer Capture date field used for processing adjustments and representments. MasterCard Debit Switch (MDS) Note: This tag is mapped to DE 15 (Date, Settlement) in the MDS transaction message. For information on MDS transaction messages, refer to the MDS Online Specifications manual. S-123: Tag 42, MasterCard POS Entry Mode Format: AN 3 TDEs: MasterCard Interchange Compliance Information Tag 42 contains a MasterCard POS Entry Mode value for MasterCard authorization transactions processed through the VisaNet Gateway services. The data in this tag consists of 3 unpacked numeric characters and is required in authorization response (0110) messages only. In authorization request (1100) messages, it passes information from DE 22 received from MasterCard. This tag is mapped from DE 116 (Card Issuer Reference Data), Dataset ID 67 (MasterCard Clearing Data), Tag 01 in the VisaNet transaction message. For information on VisaNet transaction messages, refer to the appropriate VisaNet technical specification. S-123: Tag 43, MasterCard POS PIN Capture Mode Format: N2 TDEs: MasterCard Interchange Compliance Information Tag 43 contains a MasterCard POS PIN Capture Mode value for MasterCard authorization transactions processed through the VisaNet Gateway services. The data in this tag consists of 2 unpacked numeric characters and is required in authorization response (0110) messages only. This tag is mapped from DE 116 (Card Issuer Reference Data), Dataset ID 67 (MasterCard Clearing Data), Tag 02 in the VisaNet transaction message. For information on VisaNet transaction messages, refer to the appropriate VisaNet technical specification. S-123: Tag 44, MasterCard POS Data Format: AN ..26 TDEs: MasterCard Interchange Compliance Information Tag 44 contains MasterCard POS Data for MasterCard authorization transactions processed through the VisaNet Gateway services. The data in this tag is required in authorization response (0110) messages only. In authorization request (1100) messages, it passes information from DE 61 received from MasterCard. This tag is mapped from DE 116 (Card Issuer Reference Data), Dataset ID 67 (MasterCard Clearing Data), Tag 03 in the VisaNet transaction message. For information on VisaNet transaction messages, refer to the appropriate VisaNet technical specification. S-123: Tag 45, AMEX POS Data Code Format: AN 12 TDEs: AMEX Gateway Clearing Data Tag 45 contains AMEX POS Data Code for American Express authorization transactions processed through the VisaNet Gateway services. The data in this tag is required in authorization response (0110) messages only. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 402 Data element definitions This tag is mapped from DE 116 (Card Issuer Reference Data), Dataset ID 66 (American Express Clearing Data), Tag 01 in the VisaNet transaction message. For information on VisaNet transaction messages, refer to the appropriate VisaNet technical specification. S-123: Tag 46, Mastercard On-behalf Services Data Format AN ..40 TDE Mastercard M/Chip On-behalf Services TDE Electronic Commerce Universal Card Authentication Field Tag 46 contains on-behalf services data carried in Mastercard interchange messages. This data is used by Mastercard to identify the on-behalf services performed on a transaction and the results. For example, it could contain the results of PIN validation from stand-in processing by Mastercard. The data in this tag is alphanumeric and variable length up to 40 characters, in multiples of 4-character groups. A host can receive this information in 1100, 1110, 1120, 1220, 1400, and 1420 messages. This tag maps to and from the following: • • • DE 48 (Additional Data—Private Use) SE 71 (On-behalf Services) in outbound 1100 (0100 received from Mastercard) or inbound 1220 (0200 received from Mastercard) DE 48 (Additional Data—Private Use) SE 74 (Additional Processing Information) in outbound 1110 (0110 received from Mastercard) DE 48 (Additional Data—Private Use) SE 74 (Additional Processing Information) in inbound 1110 (0100 received from Mastercard, forwarded to the host (1100), 1110 response containing DE 123.46 received from host, 0110 response sent to Mastercard.) For information on Mastercard transaction messages, refer to the appropriate Mastercard technical specification. S-123: Tag 47, MasterCard On-behalf Services Issuer Chip Authentication Data Format: AN ..32 TDEs: On-behalf Services TDE Tag 47 contains the following data carried in the MasterCard interchange messages: Issuer Chip Authentication. This data is used by MasterCard for cryptogram processing. A host can send this information out in 0110 request messages if passed from the MasterCard interface. This tag is mapped from DE 48 (Additional Data—Private Use), Subelement 72 (Issuer Chip Authentication) in the MasterCard transaction message. For information on MasterCard transaction messages, refer to the appropriate MasterCard technical specification. S-123: Tag 48, MasterCard On-behalf Services Chip CVR/TVR Bit Error Results Format: AN ..50 TDEs: On-behalf Services TDE Tag 48 contains the following data carried in the MasterCard interchange messages: the Terminal Verification Results (TVR) and Card Verification Results (CVR) bitmask and expected values registered by the issuer. This data serves as notification of bit validation errors detected in the CVR/TVR within the issuer application data during M/Chip Cryptogram Validation processing. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 403 Data element definitions BASE24-eps can send this information to a host in 0100 and 0120 messages; BASE24-eps does not accept this information in any messages from a host. This tag is mapped from DE 48 (Additional Data—Private Use), Subelement 79 (Chip CVR/TVR Bit Error Results Listing) in the MasterCard transaction message. For information on MasterCard transaction messages, refer to the appropriate MasterCard technical specification. S-123: Tag 49, Dynamic Card Verification Authorization System ATC Value Format: AN 5 TDEs: Dynamic Card Verification ATC Tag 49 contains the following data carried in the MasterCard interchange messages: the derived full ATC value used in validation. This value is used with PayPass Dynamic CVC 3 On-behalf Services. BASE24-eps can send this information to a host in 0100 and 0120 messages; BASE24-eps does not accept this information in any messages from a host. This tag is mapped from DE 48 (Additional Data—Private Use), Subelement 34 (Dynamic CVC 3 ATC Information), Subfield 1 (ATC Value) in the MasterCard transaction message. For information on MasterCard transaction messages, refer to the appropriate MasterCard technical specification. S-123: Tag 50, Dynamic Card Verification ATC Synchronization Digits Format: Not applicable TDEs: Not applicable Tag 50 is reserved. The data to which this tag corresponds is used internally by BASE24-eps. This tag should not be sent to or received from a host. S-123: Tag 51, Dynamic Card Verification Regenerated ATC Format: Not applicable TDEs: Not applicable Tag 51 is reserved. The data to which this tag corresponds is used internally by BASE24-eps. This tag should not be sent to or received from a host. S-123: Tag 52, Dynamic Card Verification ATC Discrepancy Indicator Format: AN 1 TDEs: Dynamic Card Verification ATC Tag 52 contains the following data carried in the MasterCard interchange messages: the ATC Discrepancy Indicator used with PayPass Dynamic CVC 3 On-behalf Services. BASE24-eps can send this information to a host in 0100 and 0120 messages; BASE24-eps does not accept this information in any messages from a host. This tag is mapped from DE 48 (Additional Data—Private Use), Subelement 34 (Dynamic CVC 3 ATC Information), Subfield 3 (ATC Discrepancy Indicator) in the MasterCard transaction message. For information on MasterCard transaction messages, refer to the appropriate MasterCard technical specification. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 404 Data element definitions S-123: Tag 53, Dynamic Card Verification ATC Discrepancy Value Format: AN 5 TDEs: Dynamic Card Verification ATC Tag 53 contains the following data carried in the MasterCard interchange messages: the ATC Discrepancy value used with PayPass Dynamic CVC 3 On-behalf Services. BASE24-eps can send this information to a host in 0100 and 0120 messages; BASE24-eps does not accept this information in any messages from a host. This tag is mapped from DE 48 (Additional Data—Private Use), Subelement 34 (Dynamic CVC 3 ATC Information), Subfield 2 (ATC Discrepancy Value) in the MasterCard transaction message. For information on MasterCard transaction messages, refer to the appropriate MasterCard technical specification. S-123: Tag 54, Destination Customer Name Format: AN 30 TDEs: Customer Data Tag 54 contains a 30-character destination customer name. It is mapped to and from the Customer Data TDE. S-123: Tag 55, Billpay Information Format: Variable based on the subtags included TDEs: Billpay Transactions Tag 55 contains billpay information mapped to and from the Billpay Transactions TDE. It carries subtag data as shown in the table below. Tag 55: Billpay Information Subtag Description 1 Bill Reference Number 2 Region Code Format AN 11 N2 S-123: Tag 56, Additional Payment Information Format: Variable based on the subtags included TDEs: Payment Additional Information Tag 56 contains additional fields needed in some cases to process payment transactions. This tag carries subtag data as shown in the table below. MDS: This tag is used to process MasterCard Debit Switch (MDS) person-to-person consumer MasterCard MoneySend payment transactions. As specified by MDS, sender information is provided by acquirers in 0200 messages and receiver information is provided by issuers in 0210 messages. For information on MDS transaction messages, refer to the appropriate MDS technical specification. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 405 Data element definitions Tag 56: Additional Payment Information Subtag 01 Description Payment Receiver Reference Number Format AN 19 MDS: For 0210 messages, this tag is mapped to and from DE 124 (Member-defined Data), Subfield 1 (Unique Reference Number) in the MDS transaction message. LINK: Maps to data element 123, sub-field 043 (Transaction Reference) for LINK MPT transactions. 02 Payment Receiver ID AN 46 MDS: For 0210 messages, this tag is mapped to and from DE 124 (Member-defined Data), Subfield 2 (Recipient) in the MDS transaction message. LINK: Maps to data element 123, sub-field 042 (Recipient Proxy) for LINK MPT transactions. 03 Payment Receiver Address AN 91 MDS: For 0210 messages, this tag is mapped to and from DE 124 (Member-defined Data), Subfield 3 (Recipient Address) in the MDS transaction message. LINK: Maps to data element 123, sub-field 053 (Receiver Sort Code) for LINK MPT transactions. 04 Payment Receiver Phone Number AN 20 MDS: Not used. LINK: Maps to data element 123, sub-field 054 (Receiver Account) for LINK MPT transactions. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 406 Data element definitions Tag 56: Additional Payment Information Subtag 05 Description Payment Receiver User Field Format AN 65 MDS: For 0210 messages, this tag is mapped to and from DE 124 (Member-defined Data), Subfield 4 (Reserved Data) in the MDS transaction message. LINK: This tag is mapped to Field 127, subfield 002 in the LINK transaction message. 06 Payment Sender Reference Number AN 19 MDS: For 0200 messages, this tag is mapped to and from DE 124 (Member-defined Data), Subfield 1 (Unique Reference Number) in the MDS transaction message. LINK: Maps to data element 123, sub-field 046 (Payment Reference) for LINK MPT transactions. 07 Payment Sender ID AN 46 MDS: For 0200 messages, this tag is mapped to and from DE 124 (Member-defined Data), Subfield 2 (Sender/Payer Name/User ID) in the MDS transaction message. LINK: Maps to data element 123, sub-field 041 (Sender Proxy) for LINK MPT transactions. 08 Payment Sender Address AN 91 MDS: For 0200 messages, this tag is mapped to and from DE 124 (Member-defined Data), Subfield 3 (Sender/Payer Address) in the MDS transaction message. LINK: Maps to data element 123, sub-field 044 (NSC/BIC) for LINK MPT transactions. 09 Payment Sender Phone Number AN 20 MDS: Not used. LINK: Maps to data element 123, sub-field 045 (Account/IBAN) for LINK MPT transactions. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 407 Data element definitions Tag 56: Additional Payment Information Subtag 10 Description Payment Sender User Field Format AN 65 MDS: For 0200 messages, this tag is mapped to and from DE 124 (Member-defined Data), Subfield 4 (Reserved Data) in the MDS transaction message. LINK: This tag is mapped to Field 127, subfield 001 in the LINK transaction message. 11 Sanction Score Field AN 3 Banknet: For 0100, 0110, and 0120 messages, this tag is mapped to and from DE48, subelement 67, subfield 1 in the Banknet transaction message. MDS: For 0200, 0210, and 0220 messages, this tag is mapped to and from DE48, subelement 67, subfield 1 in the MDS transaction message. 12 Receiver/Recipient Data ANS..322 Banknet and MDS: Holds the complete Receiver/Recipient Data as necessary to format DE 108 SE 01. 13 Sender Data ANS..322 Banknet and MDS: Holds the complete Sender Data as necessary to format DE 108 SE 02. 14 MoneySend Transaction Data ANS..138 Banknet and MDS: Holds the complete Transaction Data as necessary to format DE 108 SE 03. 15 MoneySend Language Description ANS..61 Banknet and MDS: Holds the complete Language Data as necessary to format DE 108 SE 04. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 408 Data element definitions Tag 56: Additional Payment Information Subtag Description 16 Format Digital Account Information ANS 99 Banknet and MDS: Holds the complete Digital Account Information as necessary to format DE 108 SE 05. S-123: Tag 57, Shipping Information Format: Variable based on the subtags included TDEs: Shipping Tag 57 contains shipping information for a transaction. This tag carries subtag data as shown in the table below. It can be used in processing interchange transactions, and its use can vary depending on the interchange involved in the transaction. American Express Card Acceptance and Processing Network (Amex CAPN): Amex CAPN uses this data with purchase transactions involving shipping (e.g., Internet, mail, and telephone purchases). The data in this tag maps to and from data element 47 (Additional Data - National) format ITD and data element 63 (Private Use Data) in the Amex CAPN transaction message. For information on Amex CAPN transaction messages, refer to the appropriate Amex CAPN technical specification. Tag 57: Shipping Information Subtag Description Format 01 Ship-to First Name AN 15 02 Ship-to Last Name AN 30 03 Ship-to Address 04 Ship-to Postal Code N9 05 Ship-to Country Code N3 06 Phone Number 07 Method AN 2 08 Weight ANS 8 09 SKU ANS 50 NS 15 ANS 15 S-123: Tag 58, Internet Information Format: Variable based on the subtags included TDEs: Internet Tag 58 contains Internet information for a transaction. This tag carries subtag data as shown in the table below. It can be used in processing interchange transactions, and its use can vary depending on the interchange involved in the transaction. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 409 Data element definitions American Express Card Acceptance and Processing Network (Amex CAPN): Amex CAPN uses this data with Internet purchase transactions. The data in this tag maps to and from data element 47 (Additional Data - National) format ITD in the Amex CAPN transaction message. For information on Amex CAPN transaction messages, refer to the appropriate Amex CAPN technical specification. Tag 58: Internet Information Subtag Description Format 01 Email Address ANS 60 02 Hostname ANS 60 03 Browser Type ANS 60 04 IP Address NS 15 S-123: Tag 59, Travel and Entertainment Information Format: Variable based on the subtags included TDEs: Travel and Entertainment Tag 59 contains travel and entertainment information for a transaction. This tag carries subtag data as shown in the table below. It can be used in processing interchange transactions, and its use can vary depending on the interchange involved in the transaction. American Express Card Acceptance and Processing Network (Amex CAPN): Amex CAPN uses this data with airline purchase transactions. The data in this tag maps to and from data element 47 (Additional Data - National) format APD in the Amex CAPN transaction message. For information on Amex CAPN transaction messages, refer to the appropriate Amex CAPN technical specification. Tag 59: Travel and Entertainment Information Subtag Description Format 01 Agreement Number ANS 9 02 Airline City Origin ANS 5 03 Airline City Destination ANS 5 04 Airline Passenger Name AN 25 05 Airline Ticket Number 06 Airline Travel Date AN 6 07 Arrival Date AN 6 08 Folio Number 09 T & E Indicator 10 Vehicle Return City ANS 18 11 Cardmember Name AN 40 12 Number of Cities 13 Routing Cities 14 Number of Airline Carriers BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 ANS 15 ANS 10 AN 2 N2 ANS 59 N2 410 Data element definitions Tag 59: Travel and Entertainment Information Subtag Description Format 15 Airline Carriers ANS 53 16 Fare Basis ANS 24 17 Number of Passengers N3 S-123: Tag 60, Installment Payment Information Format: Variable based on the subtags included TDEs: Installment Payment Data Tag 60 contains installment payment information mapped to and from the Installment Payment Data TDE. It carries subtag data as shown in the table below. It can be used in processing interchange transactions, and its use varies depending on the interchange involved in the transaction. AMEX GNS: This tag is used to process deferred payment plans (DPPs). The subtags are mapped to and from DE 48, subfields 2, 3, 5, 8, and 11 in the American Express transaction message. VisaNet: This tag is used to process installment payment transactions. The subtags are mapped to and from corresponding DE 104, dataset 5D tags 01–06 (Installment Payment Data tags) in the VisaNet transaction message. For information on VisaNet installment payment transaction messages, see the appropriate VisaNet technical specifications. Tag 60: Installment Payment Information Subtag Description Format 01 Total Amount of Payments 02 Currency Code of Payments N3 03 Number of Installments N3 04 Amount of each Installment N 12 05 Installment payment number N3 06 Frequency of Installments AN 1 07 Commission fee N 12 08 Item number 09 Date of first installment 10 Total amount funded 11 Percent of amount requested 12 Total expenses 13 Percent of total expenses 14 Total fees 15 Percent of total fees 16 Total taxes BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 N 12 AN 30 N6 N 12 N4 N 12 N4 N 12 N4 N 12 411 Data element definitions Tag 60: Installment Payment Information Subtag Description Format 17 Percent of total taxes N4 18 Total insurance 19 Percent of total insurance 20 Total other costs 21 Percent of total other costs 22 Monthly interest rate N 10 23 Annual interest rate N 10 24 Annual cost of financing N7 25 Installment payment type N2 26 DPP Acquirer/Issuer Identifier AN 4 27 DPP Plan Type AN 4 28 DPP Number of Installments 29 Plan Description 30 Total Tip N 12 31 Total Amount Plus Fees N 12 32 Issuer Transport Data N 12 N4 N 12 N4 N4 AN 20 Max AN 260 S-123: Tag 61, MICR Data Format: ANS ..64 TDEs: MICR Data Tag 61 contains MICR data to be used by a host for processing for check-based transactions (e.g., cash check, deposit check, and deposit check with cash back transactions from an ATM). S-123: Tag 62, Check Retention Flag Format: AN 1 TDEs: Self-Service Banking Check Tag 62 is a one-character alphanumeric field to be used by a host for indicating whether or not checks involved in a check-based transaction (e.g., cash check, deposit check, and deposit check with cash back transactions from an ATM) are to be returned or retained if the transaction is declined. Values are as follows: Value Description 0 Return all checks 1 Retain all checks BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 412 Data element definitions S-123: Tag 63, Transaction Subtype Format: AN 9 Length is based on the subtag ID, data length, and data for subtag 01 (e.g., 01004CI00). TDEs: Transaction Subtype Tag 63 contains a transaction subtype value mapped to and from the Transaction Subtype TDE. This tag can be used in processing interchange transactions, and its use can vary depending on the interchange involved in the transaction. The structure of the data in this tag is as follows. Tag 63: Transaction Subtype Subtag Description 01 Format Transaction Subtype AN 4 Interac Interchange: A transaction subtype of CI00 identifies Interac online bill pay transactions within BASE24-eps. This value is used by BASE24-eps to map internal purchase processing codes to and from the appropriate online bill pay processing codes in the Interac transaction message. For information about Interac transaction messages, refer to the appropriate Interac technical specification. S-123: Tag 64, Discover Clearing Data Format: Variable based on the subtag included TDEs: Discover Clearing Data Tag 64 contains Discover Card clearing data for transactions processed through the VisaNet Gateway services. The structure of the data in this tag is as follows. This tag is mapped from DE 116 (Card Issuer Reference Data), Dataset ID 68 (Discover Clearing Data), Tag 01 in the VisaNet transaction message. For information about VisaNet transaction messages, refer to the appropriate VisaNet technical specification. Tag 64: Discover Clearing Data Subtag Description Format 01 Discover Network Information AN ..29 02 Transaction Qualifier Data AN ..46 S-123: Tag 65, Retail Class Code Format: AN 4 TDEs: Retail Class Code BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 413 Data element definitions Tag 65 contains a four-digit retail class code. This tag can be used in processing interchange transactions, and its use can vary depending on the interchange involved in the transaction Banknet: Tag 65 is used by the Banknet interchange for UK Domestic Maestro (UKDM) Globalization support. A host will need to send and receive this tag in Banknet request messages if the Banknet Interface is configured to support UKDM processing. For Banknet transactions, this value maps to and from data element 112 (Additional Data - National Use), subelement 002 (Retailer Classification Code) in the Banknet UKDM transaction message. For information about the Banknet UKDM transaction messages, refer to the appropriate Banknet interchange technical specification. S-123: Tag 66, PRICE Transaction Block ID Format: AN 2 TDEs: PRICE Transaction Block ID Tag 66 is a two-character transaction block ID used by the PRICE interchange. It is required in second or successive requests (1100 messages) to PRICE for blocks of last movements. The information in this tag maps to and from DE 48 (Additional Private Data), subelement 12 (Identifying of Block of Last Movement) in the PRICE transaction message. For information on PRICE transaction messages, refer to the appropriate PRICE interchange technical specification. S-123: Tag 67, PRICE Commission Information Format: Variable based on the subtags included TDEs: Commission Information Tag 67 contains commission information used by the PRICE Interchange. The structure of the data in this tag is as follows. The information in this tag maps to and from DE 48 (Additional Private Data), subelement 31 (Information on Commissions) in the PRICE transaction message. For information on PRICE transaction messages, refer to the appropriate PRICE interchange technical specification. Tag 67: PRICE Commission Information Subtag Description Format 01 Amount AN 8 02 Currency AN 3 03 Type AN 1 S-123: Tag 69, Split Deposit Amount Format: N 12 TDEs: Split Deposit Amount Tag 66 contains the split deposit amount for split deposit transactions (transaction code 2F). In split deposit transactions, two accounts are identified for the deposit. The split deposit amount is associated with the first account; the deposit amount for the second account is calculated using the total deposit amount minus the split deposit amount. Example: A processing code of 2F2010 identifies a split deposit transaction, depositing funds to a checking account (account type 20) and a savings account (account type 10). The split deposit amount would be deposited BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 414 Data element definitions to the checking account; the remainder of the deposit would go to the savings account (total transaction amount minus the split deposit amount). S-123: Tag 70, Additional Verification Information Format: Variable based on the subtags included TDEs: Additional Verification Info Tag 70 contains a series of response codes used by some interchanges to denote that certain pieces of cardholder data have been verified. American Express Card Acceptance and Processing Network (Amex CAPN): The data in this tag maps to and from the American Express AAV, Billing Telephone Number and E-Mail Address Verification Response Message Subfields—positions 8 through 12—in data element 62 (Private Use Data) of an Amex CAPN transaction message. For information about the Amex CAPN transaction message, refer to the appropriate Amex CAPN interchange technical specifications. Tag 70: Address Verification Information Subtag 01 Description Cardmember Billing Postal Code Length AN 1 Amex CAPN: This value maps to and from data element 62, position 8 (Cardmember Billing Postal Code) in the Amex CAPN transaction message. 02 Cardmember Billing (Street) Address AN 1 Amex CAPN: This value maps to and from data element 62, position 9 (Cardmember Billing (Street) Address) in the Amex CAPN transaction message. 03 Cardmember First and Last Name AN 1 Amex CAPN: This value maps to and from data element 62, position 10 (Cardmember First and Last Name) in the Amex CAPN transaction message. 04 Cardmember Billing Phone Number AN 1 Amex CAPN: This value maps to and from data element 62, position 11 (Cardmember Billing Phone Number) in the Amex CAPN transaction message. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 415 Data element definitions Tag 70: Address Verification Information Subtag Description 05 Length Customer E-mail Address AN 1 Amex CAPN: This value maps to and from data element 62, position 12 (Customer E-mail Address) in the Amex CAPN transaction message. S-123: Tag 71, MasterCard Authorization Advice Date/Time Format: AN 10 (MMDDhhmmss) TDEs: Master Card Interchange Compliance Info Tag 71 contains the date and time a 0120 Confirmation or 0220 Preauthorization completion advice was received by the issuer or MasterCard. This data is used with MasterCard automated fuel dispenser (AFD) transactions processed through the VisaNet MasterCard gateway. VisaNet: The data in this tag maps to and from Field 116 (Card Issuer Reference Data), Dataset ID 67 (MasterCard Clearing Data), Tag 04 (Date and Time) of the VisaNet transaction message. For information about the VisaNet transaction message, refer to the appropriate VisaNet technical specifications. S-123: Tag 72 Pre-Pay Generic Receipt Data Format: Variable based on the subtags included TDEs: Pre-Pay Generic Receipt Tag 72 contains the generic receipt message used for pre-pay top-up transactions. The structure of the data in this tag is as follows. Tag 72: Pre-Pay Generic Receipt Data Subtag Description Format 01 Message Timestamp: A timestamp indicating when the generic receipt message was last changed. N 15 02 Default Receipt Message Flag: A flag indicating whether the default receipt message is used in conjunction with the telco operator message. AN 1 03 Telco-specific Message Length: Length of the generic data in the telco-specific message field (subtag 04). BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 N3 416 Data element definitions Tag 72: Pre-Pay Generic Receipt Data Subtag Description 04 Telco-specific Message: The generic data used as the telcospecific message. The length of the actual message is specified in subtag 03. Format AN 200 S-123: Tag 73, Pre-Pay Top-Up Receipt Data Format: Variable based on the subtags included TDEs: Pre-Pay Top-Up Receipt Tag 73 contains data to populate the receipt for pre-pay top-up transactions. The structure of the data in this tag is as follows. Tag 73: Pre-Pay Top-Up Receipt Data Subtag 01 Description Institution ID: The Institution ID assigned to the mobile operator interface. Format AN 20 Note: This field is currently not populated by BASE24eps. This field is only being used for BASE24 passthrough. 02 Marketing Message: Marketing message as supplied by the mobile operator. AN 200 S-123: Tag 74, Pre-Pay Top-Up Data Format: Variable based on the subtags included TDEs: Pre-Pay Top-Up Tag 74 contains information used for the authorization of pre-pay top-up transactions. The structure of the data in this tag is as follows. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 417 Data element definitions Tag 74: Pre-Pay Top-Up Data Subtag 01 Description Route Method: A code indicating the method used by the acquiring interface to identify the mobile operator (service provider). Valid values are as follows: Format ANS 1 M = PAN for phone top-up card issued by mobile operator (key entered) ; = PAN for phone top-up card issued by mobile operator (swiped) I = Mobile operator ID (IIN) P = Registered customer phone number L = Mobile operator ID (IIN) and registered customer phone number 02 Track 2 Data captured by the acquiring interface. This data is formatted as a track 2 buffer. AN 39 03 Pre-Pay Transaction Code: The external transaction code for the pre-pay top-up transaction, as established by the acquiring interface. AN 2 04 Phone Number to receive the topup. 05 Payment Method: A code indicating the method of payment for the topup transaction by the customer. Valid values are: ANS 20 AN 1 N = No Card Type (Cash) D = Debit Card C = Credit Card U = Unknown Note: This field is currently not populated by BASE24eps. This field is only being used for BASE24 passthrough. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 418 Data element definitions Tag 74: Pre-Pay Top-Up Data Subtag Description Format 06 Reference Data (e.g. Auth Code or Tran ID) issued by the mobile operator in top-up and refund top-up responses. This value may be required for refunds, confirmations, or reversals. AN 15 07 Original Reference: The reference data from the Reference Data field in the original message if the transaction being processed is a refund or reversal. This field is established by the acquiring interface. AN 15 Note: This field is currently not populated by BASE24eps. This field is only being used for BASE24 passthrough. 08 Card type the device handler uses. AN 2 Note: This field is currently not populated by BASE24eps. This field is only being used for BASE24 passthrough. 09 Operator Name: The mobile operator name, for use on receipts. 10 Operator ID: The mobile operator ID. AN 30 AN 4 LINK: This subtag maps to data element 123, sub-field 002 (Product ID, value “4201”) in the LINK MPT transaction message. 11 Mobile Service Balance: The amount (balance) on the phone after the top-up. The Mobile Phone Operator Interface process establishes this field. The operator should return it in an approved topup response. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 AN18 419 Data element definitions Tag 74: Pre-Pay Top-Up Data Subtag 12 Description Other Mobile Service Balance: Value indicating a balance—in addition to the Mobile Service Balance. The Mobile Phone Operator Interface process establishes this field. The operator should return it in an approved topup response. Format AN 18 Note: This field is currently not populated by BASE24eps. This field is only being used for BASE24 passthrough. 13 Activation Code: A code supplied to the customer to activate a top-up. This field is supplied to the customer in the clear. The operator should return it in an approved topup response. AN 16 14 Approval Code: Approval code as supplied in responses from the mobile operator. The Mobile Phone Operator Interface process establishes this field. The operator should return it in an approved topup response. For declined transactions, this field may contain the response code returned from the operator. AN 15 Note: This field is currently not populated by BASE24eps. This field is only being used for BASE24 passthrough. 15 Response Code returned from mobile operator. This code is the operator’s actual response code. AN 5 Note: This field is currently not populated by BASE24eps. This field is only being used for BASE24 passthrough. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 420 Data element definitions Tag 74: Pre-Pay Top-Up Data Subtag Description 16 Mobile Operator Retailer ID used for clearing against the mobile operator. Format AN19 Note: This field is currently not populated by BASE24eps. This field is only being used for BASE24 passthrough. 17 Reversal Code: A code indicating the reason for a reversal. Valid values are as follows: AN 1 blank = Not a reversal S = Reason code A = Mobile Operator denial Note: This field is currently not populated by BASE24eps. This field is only being used for BASE24 passthrough. S-123: Tag 75, Pre-Pay Response Data Format: Variable based on the subtags included TDEs: Pre-Pay Response Tag 75 contains information used in the response of pre-pay top-up transactions. The structure of the data in this tag is as follows. Tag 75: Pre-Pay Response Data Subtag Description 01 Tax Amount to be applied to the topup transaction. This field is available for printing on receipts. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 Format N 19 421 Data element definitions Tag 75: Pre-Pay Response Data Subtag Description 02 Response Indicator specifying the pre-pay notification process required by the Device Handler process. This value is provided by the Telco Interface. Valid values are as follows: Format AN 1 blank = Information request complete. 1 = The Device Handler process presents a tax notification to the cardholder. 2 = The Device Handler process presents a telecommunication provider list to the cardholder and after the carrier is selected, the Device Handler process presents an available amounts list to the cardholder. 3 = The Device Handler process presents an available amounts list to the cardholder. Note: This field is currently not populated by BASE24eps. This field is only being used for BASE24 passthrough. 03 Carrier Code: The telecommunication provider code used by the mobile network to identify a specific carrier. AN 5 Note: This field is currently not populated by BASE24eps. This field is only being used for BASE24 passthrough. 04 Carrier Name: The telecommunication provider name supplied to the customer. This field is available for printing on receipts. 05 Carrier Phone Number: The telecommunication provider's phone number which is supplied to the customer. This field is available for printing on receipts. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 AN 20 ANS 15 422 Data element definitions S-123: Tag 76, Pre-Pay Voucher Format 1 Receipt Data Format: Variable based on the subtags included TDEs: Pre-Pay Voucher Format 1 Receipt Tag 76 contains the pre-pay top-up information used on the receipt of a voucher transaction. The structure of the data in this tag is as follows. Tag 76: Pre-Pay Voucher Format 1 Receipt Data Subtag Description Format 01 Batch ID: A value that identifies the order of the card in the batch load. This field is available for printing on receipts. N 11 02 Internal Card Identifier: The internal card identifier. This field is available for printing on receipts. N 11 03 Expiration Days: The number of days the account expiration date is extended after this replenishment. This field is available for printing on receipts. AN 4 04 Prepaid Card Identification Number used for replenishment of an account not enabled with a real-time recharge. This field is available for printing on receipts. AN 19 05 Shelf Date: The date (YYMMDD) after which the card used in this transaction can no longer be used. This field is available for printing on receipts. AN 6 S-123: Tag 77, Pre-Pay Online Receipt Data Format: Variable based on the subtags included TDEs: Pre-Pay Online Receipt Tag 77 contains the information used on the receipt for online pre-pay top-up transactions. The structure of the data in this tag is as follows. Tag 77: Pre-Pay Online Receipt Data Subtag 01 Description Expiration Date (YYMMDD). Available for printing on receipts. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 Format N6 423 Data element definitions Tag 77: Pre-Pay Online Receipt Data Subtag Description 02 Prepaid Card Identification Number used for replenishment. This field may not be present for every transaction. Format AN 19 Note: This field is currently not populated by BASE24eps. This field is only being used for BASE24 passthrough. S-123: Tag 78, Inventory Voucher Data Format: Variable based on the subtags included TDEs: Inventory Voucher Tag 78 contains information associated with the purchase of pre-pay top-up vouchers. The structure of the data in this tag is as follows. Tag 78: Inventory Voucher Data Subtag Description Format 01 Acquirer Stock Code known by the inventory manager. This field is formatted by the acquiring process. AN 4 02 Issuer Stock Type known by the issuer (telco). This field is formatted by the acquiring process. AN 4 03 Stock Value: The denomination of the voucher, in whole current units. This field is formatted by the acquiring process. AN 19 Note: This field is currently not populated by BASE24eps. This field is only being used for BASE24 passthrough. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 424 Data element definitions Tag 78: Inventory Voucher Data Subtag Description 04 Deliver Sequence Number: The sequence number assigned to this transaction by the acquiring process. This field is formatted by the acquiring process. Format AN 12 Note: This field is currently not populated by BASE24eps. This field is only being used for BASE24 passthrough. 05 Stock Number: The control or serial number associated with the stock item. The value in this field is available for printing on receipts. AN 16 06 Stock Expiration Date: The expiration date (CCYYMMDD) of the stock item. The value in this field is available for printing on receipts. AN 8 07 Reversal Type for the stock item. The inventory manager uses the value in this field to determine whether the stock item can be made available for resale. This value is formatted by the acquiring process. Valid values are as follows: AN 1 0 = Not specified. If a reversal, treat as normal reversal. 1 = Normal reversal. Stock item can be made available for resale. 2 = Doubtful reversal. Stock item should not be made available for resale. Note: This field is currently not populated by BASE24eps. This field is only being used for BASE24 passthrough. S-123: Tag 79, MasterCard Program Participation Indicator Format: AN 20 TDEs: MasterCard Debit Switch/Maestro TDE BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 425 Data element definitions Tag 79 contains program participation indicators used by MasterCard interchanges to monitor and track a participant’s activity in special promotion support programs. Indicators are one alphanumeric character each and supported as described in the following table. Note: The ISO 93 Host Interface process moves data to and from the MasterCard Debit Switch/Maestro TDE as a 20-byte field. Positions are not parsed individually. Position 1 Description Format Card Validation Code 2 (CVC 2) Validation Program Indicator AN 1 MDS Interchange: This value maps to and from data element 48 (Additional Data—Private Use), subelement 94 (Program Participation Indicator), subfield 1 (CVC 2 Program Participation Indicator) in the MDS transaction messages. For information about the MDS transaction message, refer to the MDS message specifications. 2 Quick Payment Service (QPS) Chargeback Eligibility Indicator. AN 1 MDS Interchange: This value maps to and from data element 48 (Additional Data), subelement 94 (Program Participation Indicator), subfield 2 (QPS/PayPass Chargeback Eligibility) in MDS transaction messages. For information about the MDS transaction message, refer to the MDS message specifications. 3–20 Reserved AN 18 S-123: Tag 80, Member to Member Data Format: AN.. 256 TDEs: Member to Member Data Tag 80 contains member to member data used by interchanges. Data is in tag-length-value (TLV) format as defined by an interchange. VisaNet: The data in this tag maps to and from data element 104, usage 2, dataset 71 (Member to Member Data) in the VisaNet transaction message. For information about the VisaNet transaction message, refer to the appropriate VisaNet technical specifications. S-123: Tag 81, Stored Value Pre-Registered Service Indicator Format: AN 1 TDEs: Stored Value Service Indicator Tag 81 contains a Stored Value Preregistered Service Indicator. Valid values are: • • • • b = Single transaction (where b equals a blank space). 0 = First transaction in a series (storing payment details provided by the cardholder). 1 = Subsequent transaction in a series (using previously stored payment details). The original transaction was token-based with a valid cryptogram. 2 = Subsequent transaction in a series (using previously stored payment details). The original transaction may not have been token-based, but cardholder authentication was performed. All valid values (space, 0-2) are mapped to and from the the Stored Value Service Indicator TDE. All other values are not mapped. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 426 Data element definitions Set from incoming network messages based on Point of Service Entry Mode codes indicating that the transaction was initiated using credentials stored on file. Typically when this TDE is set, the Card Data Input Mode in the Point of Service TDE is also set to value 8 (electronic commerce). For outgoing messages when the Card Data Input Mode in the Point of Service TDE is 8 (electronic commerce) and this TDE is present with values of 1 or 2, the Point of Service Entry Mode is set to the network's credential on file corresponding value. S-123: Tag 82, MasterCard POS Transaction Status Indicator Format: AN 1 TDEs: MasterCard Debit Switch/Maestro TDE Tag 82 contains the MasterCard POS Transaction Status Indicator associated with the transaction. MasterCard: The data in this tag is mapped to and from the value in data element 61 (Point-of-Service Data), subfield 7 (POS Transaction Status) of the MasterCard transaction message. For information about the MasterCard transaction message, refer to the appropriate MasterCard technical specifications. S-123: Tag 83, MasterCard Promotion Code Format: AN 6 TDEs: MasterCard Promotion Code TDE Tag 83 contains a MasterCard promotion code to indicate participation in a particular MasterCard program or service. MDS Interchange: The data in this tag is mapped to and from data element 48 (Additional Data), subelement 95 (MasterCard Promotion Code) of the MDS transaction message. For information about the MDS transaction message, see the appropriate MDS technical specifications. S-123: Tag 84, Five Digit Card Security Code Format: AN 5 TDEs: Five Digit Card Security Code TDE Tag 84 contains a Five Digit Card Security Code (5CSC) value, which can be sent under some circumstances in POS authorization requests from the AMEX GNS interchange. Five Digit Card Security Codes are derived by the acquirer of a transaction from the card track data. AMEX GNS Interchange: The data in this tag is mapped from data element 53 (Security Related Control Information) of the AMEX GNS transaction message. For information about AMEX GNS transaction messages, see the appropriate AMEX GNS technical specifications. S-123: Tag 85, Payment Initiation Channel Information S-123: Tag 86, Visa Custom Payment Service Additional Data Format: AN 28 TDEs: Visa Custom Payment Service Additional Data Tag 86 contains information from the Visa Custom Payment Service Additional Data TDE. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 427 Data element definitions VisaNet: The data in this tag maps to and from data element 062 (Visa Custom Payment Service) of the VisaNet transaction message. For information about the VisaNet transaction message, refer to the appropriate VisaNet technical specifications. Tag 86: Visa Custom Payment Service Additional Data Position Description 1-6 Auto rental date or lodging checkout date (YYMMDD). AN 6 Electronic Commerce Goods Indicator. Values: AN 1 7 Length D = Digital goods P = Physical goods 8 Excluded Transaction Identifier Reason Code. Values: AN 1 A = Transaction identifier is not available or not cleared through VisaNet. K = Transaction identifier is not included in the transaction. N = Not provided. 9-14 Extra Charges (There may be up to 6 extra charges, one position each). Values: AN 6 1 = Gasoline (auto rental extra charges). 2 = Extra mileage (auto rental extra charges) / Restaurant or room service (hotel extra charges). 3 = Late return (auto rental extra charges) / Gift shop (hotel extra charges). 4 = One-way service fee (auto rental extra charges) / mini-bar (hotel extra charges). 5 = Parking or moving violation (auto rental extra charges) / Telephone (hotel extra charges). 6 = Other (hotel extra charges). 7 = Laundry (hotel extra charges). 15 No show Indicator. Values: blank or 1 (No show for vehicle or hotel). AN 1 16 Restricted Ticket Indicator. Values: blank or 1 (Restricted ticket). AN 1 BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 428 Data element definitions Tag 86: Visa Custom Payment Service Additional Data Position Description 17-28 Total Amount Authorized. Length AN 12 S-123: Tag 87, China UnionPay (CUP) Data Format: Variable based on the subtags included TDEs: CUP Interface Data, CUP Interface Data 4, CUP Interface Data 5, Generic Data, Chinese Customer ID Tag 87 contains China UnionPay (CUP) data that is passed to and accepted from a host. The structure of the data in this tag is as follows: Tag 87: China UnionPay (CUP) Data Subtag 01 Description Transaction Channel Type Length AN 2 China UnionPay (CUP): This value maps to and from data element 60, field 2, subfield 5 (Transaction Channel Type) in the CUP transaction message. 02 Initiation Method AN 1 China UnionPay (CUP): This value maps to and from data element 60, field 3 subfield 5 (Transaction Initiation Method) in the CUP transaction message. 03 Card Type AN 1 China UnionPay (CUP): This value maps to and from data element 60, field 3, subfield 9 (Card Type) in the CUP transaction message. 04 Card Category AN 2 China UnionPay (CUP): This value maps to and from data element 60, field 3, subfield 10 (Card Category) in the CUP transaction message. 05 Interactive Mode Indicator AN 1 China UnionPay (CUP): This value maps to and from data element 60, field 2, subfield 9 (Interactive Mode Indicator) in the CUP transaction message. 06 CUP Secure Certification Information ANS MAX 255 China UnionPay (CUP): This value maps to and from data element 48, Usage IN in the CUP transaction message. 07 Transaction Relevance Tag AN 2 China UnionPay (CUP): This value maps to and from data element 48, Usage AO in the CUP transaction message. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 429 Data element definitions Tag 87: China UnionPay (CUP) Data Subtag 08 Description Risk Reason Code Length AN 3 China UnionPay (CUP): This value maps to and from data element 48, Usage BC in the CUP transaction message. 09 Risk Level AN 1 China UnionPay (CUP): This value maps to and from data element 48, Usage BC in the CUP transaction message. 10 Risk Rating AN 3 China UnionPay (CUP): This value maps to and from data element 48, Usage BC in the CUP transaction message. 11 Risk Reserved AN 12 China UnionPay (CUP): This value maps to and from data element 48, Usage BC in the CUP transaction message. 12 ID Type AN 2 China UnionPay (CUP): This value maps to and from data element 57, Usage CI in the CUP transaction message. 13 ID Number AN 20 China UnionPay (CUP): This value maps to and from data element 57, Usage CI in the CUP transaction message. 14 Order Number AN 40 China UnionPay (CUP): This value maps to and from data element 48, Usage ON in the CUP transaction message. 15 Secondary Merchant ID AN 15 China UnionPay (CUP): This value maps to and from data element 48, Usage PM in the CUP transaction message. 16 Secondary Merchant Name/Address AN 40 China UnionPay (CUP): This value maps to and from data element 48, Usage PM in the CUP transaction message. 17 Server Sequence Number N6 China UnionPay (CUP): This value maps to and from data element 61, Usage SA in the CUP transaction message. 18 Authentication Time N 19 China UnionPay (CUP): This value maps to and from data element 61, Usage SA in the CUP transaction message. 19 Logistic Delivery ID N1 China UnionPay (CUP): This value maps to and from data element 61, Usage SA in the CUP transaction message. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 430 Data element definitions Tag 87: China UnionPay (CUP) Data Subtag 20 Description Sub-merchant ID Length N8 China UnionPay (CUP): This value maps to and from data element 61, Usage SA in the CUP transaction message. 21 CAVV Arithmetic Method N1 China UnionPay (CUP): This value maps to and from data element 61, Usage SA in the CUP transaction message. 22 Transaction Verification Mode N 16 China UnionPay (CUP): This value maps to and from data element 61, Usage AM in the CUP transaction message. 23 Operation Custom Data ANS 147 China UnionPay (CUP): This value maps to and from data element 61, Usage AM in the CUP transaction message. 24 CUP E-Commerce Indicator N2 China UnionPay (CUP): This value maps to and from data element 60.2.8 (positions 9-10) in the CUP transaction message. 28 Card status AN 3 China UnionPay (CUP): This value maps to and from data element 57, Usage AS, subtag SE in the CUP transaction message. 29 Mobile phone number ANS 20 China UnionPay (CUP): This value maps to and from data element 57, Usage AS, subtag SE in the CUP transaction message. 30 Merchant-specific Currency N1 China UnionPay (CUP): This value maps to and from data element 48, Usage CC in the CUP transaction message. 31 Merchant-specific settlement currency AN 3 China UnionPay (CUP): This value maps to and from data element 48, Usage CC in the CUP transaction message. 32 Original message type for stand-in processing N4 China UnionPay (CUP): This value maps to and from data element 48, Usage SI in the CUP transaction message. 33 Original transaction code for stand-in processing N6 China UnionPay (CUP): This value maps to and from data element 48, Usage SI in the CUP transaction message. 34 Original point of service for stand-in processing N2 China UnionPay (CUP): This value maps to and from data element 48, Usage SI in the CUP transaction message. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 431 Data element definitions Tag 87: China UnionPay (CUP) Data Subtag 35 Description VIP card indication for stand-in processing Length N1 China UnionPay (CUP): This value maps to and from data element 48, Usage SI in the CUP transaction message. 36 Reason of Failure for stand-in processing ANS 2 China UnionPay (CUP): This value maps to and from data element 48, Usage SI in the CUP transaction message. 37 Usage CI: Customer name ANS 20 China UnionPay (CUP): This value maps to and from data element 57, Usage CI in the CUP transaction message. 38 Usage CI: Customer other info ANS 54 China UnionPay (CUP): This value maps to and from data element 57, Usage CI in the CUP transaction message. 39 Usage NM: Remittance cardholder name 1 ANS 30 China UnionPay (CUP): This value maps to and from data element 61, Usage NM in the CUP transaction message. 40 Usage NM: Remittance cardholder name 2 ANS 30 China UnionPay (CUP): This value maps to and from data element 61, Usage NM in the CUP transaction message. 41 Usage VR: Secure Plus Verification Code ANS 20 China UnionPay (CUP): This value maps to and from data element 61, Usage VR in the CUP transaction message. 42 Usage ML: Multi Language Merchant Name and Address ANS 80 China UnionPay (CUP): This value maps to and from data element 117, Usage ML in the CUP transaction message. 43 Usage AS AR: Additional Response Code AN 3 China UnionPay (CUP): This value maps to and from data element 57, Usage AS AR in the CUP transaction message. 44 Usage SI: Payer's Gender ANS 1 China UnionPay (CUP): This value maps to and from data element 104, subelement 04, Usage SI in the CUP transaction message. 45 Usage SI: Payer's Nationality ANS 3 China UnionPay (CUP): This value maps to and from data element 104, subelement 05, Usage SI in the CUP transaction message. 46 Usage SI: Payer's City of Residence. ANS..40 China UnionPay (CUP): This value maps to and from data element 104, subelement 07, Usage SI in the CUP transaction message. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 432 Data element definitions Tag 87: China UnionPay (CUP) Data Subtag 47 Description Usage SI: Payer's Address of Residence Length ANS..80 China UnionPay (CUP): This value maps to and from data element 104, subelement 08, Usage SI in the CUP transaction message. 48 Usage SI: Payer equals Payee Indicator N1 China UnionPay (CUP): This value maps to and from data element 104, subelement 09, Usage SI in the CUP transaction message. 49 Usage BI: Business Type N2 China UnionPay (CUP): This value maps to and from data element 104, Usage BI in the CUP transaction message. 50 Usage SI: Additional Data Required by Regulator ANS..50 China UnionPay (CUP): This value maps to and from data element 104, subelement 11, Usage SI in the CUP transaction message. 51 Usage SI: Note China UnionPay (CUP): This value maps to and from data element 104, subelement 12, Usage SI in the CUP transaction message. 52 Usage BB: B2B - Business Type H..100 Note: “H” indicates that the tag value is hexadecimal represented in ASCII. N2 China UnionPay (CUP): This value maps to and from data element 104, subelement 01, Usage BB in the CUP transaction message. 53 Usage BB: B2B - Payment Medium N1 China UnionPay (CUP): This value maps to and from data element 104, subelement 02, Usage BB in the CUP transaction message. 54 China Union Pay (CUP): This value maps to and from data element 125, Usage QR in the CUP transaction message. This tag is comprised of the following data: ANS..79 QRC use case indicator: ANS 3 QRC voucher number: ANS... 20 C2B payment code: ANS... 34 Wallet ID 1: ANS... 11 Wallet ID 2: ANS... 11 BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 433 Data element definitions Tag 87: China UnionPay (CUP) Data Subtag Description Length 55 China Union Pay (CUP): this value maos to and from data element 61.1 in the CUP transaction message. This tage is comprised of the following data: ANS..23 Chinese customer Id type: N 2 Chinese customer Id: ANS... 20 S-123: Tag 88, NYCE Data Format: Variable based on the subtags included TDEs: NYCE ISO Interface Tag 88 contains NYCE information to be passed to and accepted from a host. The structure of the data in this tag is as follows. Tag 88: NYCE Data Subtag Description 01 NYCE Issuer Interchange Qualifier. Values: Format ANS 1 P = Premier Issuer (Unregulated). 0 (zero) = Non-Premier Issuer (Unregulated). R = Regulated Premier Issuer with Fraud-prevention adjustment. S = Regulated Premier Issuer without Fraud-prevention adjustment. 1 = Regulated Non-Premier Issuer with Fraud-prevention adjustment. 2 = Regulated Non-Premier Issuer without Fraud-prevention adjustment. NYCE: This value maps to and from data element 124 (Text Information) tag NQ (NYCE Qualifier) subtag II (Issuer Interchange) in the NYCE transaction message. For information about NYCE transaction messages, refer to the appropriate NYCE technical specifications. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 434 Data element definitions Tag 88: NYCE Data Subtag Description 02 Format Business Use flag AN 1 NYCE: This value maps to and from the Person to Person (P2P) TDE and is used to map field 104 in the NYCE transaction message. 03 Intended Use flag AN 1 NYCE: This value maps to and from the Person to Person (P2P) TDE and is used to map field 104 in the NYCE transaction message. 04 Trace Number AN 15 NYCE: This value maps to and from the Person to Person (P2P) TDE and is used to map field 104 in the NYCE transaction message. S-123: Tag 89, Visa Data Format: Variable based on the subtags included TDEs: Visa Data Tag 89 contains VisaNet information to be passed to and accepted from a host. For information about VisaNet transaction messages, refer to the appropriate VisaNet technical specifications. The structure of the data in this tag is as follows. Tag 89: Visa Data Subtag 01 Description Format Card Authentication Reliability Indicator ANS 1 Mapped from the Visa Data TDE (crd_auth_rel_ind_) VisaNet: This value maps from data element 60 (Additional POS Information) in the VisaNet transaction message. 02 Spend Qualified Indicator ANS 1 Mapped from the Visa Data TDE (spend_qualified_ind). The host will receive this data, but will not send it. VisaNet: This value maps from data element 62.25 (Spend Qualified Indicator) in the VisaNet transaction message. 03 Multiple Payment Forms (or Split Tender) ANS 1 Mapped from the Visa Data TDE (mult_pmnt_forms). The host will receive this data, but will not send it. VisaNet: This value maps from data element 104, dataset ID 69 (Number of Payment Forms) in the VisaNet transaction message. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 435 Data element definitions Tag 89: Visa Data Subtag 04 Description Travel Tag Format ANS 1 Mapped from the Visa Data TDE (trvl_tag). The host will receive this data, but will not send it. Valid values are as follows: A = Cardholder may be traveling, destination matches purchased travel itinerary B = Cardholder may be traveling, destination unknown VisaNet: This value maps from data element 104, dataset ID 6C (Travel Tag Codes) in the VisaNet transaction message. 05 Visa Merchant Identifier AN 8 VisaNet: This value maps from data element 126, dataset ID 5. 06 Purchase ID ANS 26 VisaNet: This value maps from data element 62.7 S-123: Tag 90, Additional Card Data Input Capability Format: AN 1 TDEs: Point of Service Additional Data (adnl_crd_data_input_cap_data member) Tag 90 contains an Additional Card Data Input Capability value associated with the transaction. This value provides additional information needed to identify the Card Data Input Capability associated with the point of service of the transaction. It is used in combination with the Point of Service TDE (Card Data Input Capability data member). Valid values include: A = Terminal is capable of handling manually entered and contact magnetic stripe (crd_input_cap_manual_mag_stripe). B = Terminal is capable of handling Contact Magnetic Stripe and Contact EMV ICC (crd_input_cap_mag_stripe_and_icc). C = Terminal is capable of handling Manual, Contact Magnetic Stripe and Contact EMV ICC (crd_input_cap_manual_swipe_icc). D = Terminal is capable of handling Contactless Magnetic Stripe and Contactless EMV ICC (crd_input_cap_ctls_swipe_ctls_icc). E = Terminal is capable of handling manually entered and Contact EMV ICC (crd_input_cap_manual_icc). F = Terminal is capable of handling Contactless EMV ICC transactions only (crd_input_cap_icc_only). Discover: The data in this tag is used in mapping values to and from data element 61 position 11 (Card Data Input Capability) in the interchange transaction message. For information about the Discover transaction messages, refer to the appropriate technical specifications. S-123: Tag 91, Brazil BNDES Transactions Format: Variable based on the subtags included BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 436 Data element definitions TDEs: Visa Data Tag 91 contains Brazil BNDES Transaction information to be passed to and accepted from a host. For information about VisaNet transaction messages, refer to the appropriate VisaNet technical specifications.The structure of the data in this tag is as follows. Tag 91: Brazil BNDES Transaction Subtag 01 Description Format Cardholder Tax ID Type ANS 1 Mapped to and from the Visa Data TDE (crdhlder_tax_id_typ). The host will send and receive this data. VisaNet: This value maps to and from data element 104, dataset 6E (Cardholder Tax ID Type) in the VisaNet transaction message. 02 Cardholder Tax ID ANS 15 Mapped to and from the Visa Data TDE (crdhldr_tax_id). The host will send and receive this data. VisaNet: This value maps to and from data element 104, dataset 6E (Cardholder Tax ID) in the VisaNet transaction message. 03 Asset Indicator ANS 1 Mapped to and from the Visa Data TDE (asset_ind). The host will send and receive this data. VisaNet: This value maps to and from data element 104, dataset 6E (Asset Indicator) in the VisaNet transaction message. 04 Loan Type ANS 20 Mapped to and from the Visa Data TDE (loan_typ). The host will send and receive this data. VisaNet: This value maps to and from data element 104, dataset 6E (Loan Type) in the VisaNet transaction message. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 437 Data element definitions Tag 91: Brazil BNDES Transaction Subtag Description 05 Merchant Program Indentifier Format ANS 7 Mapped to and from the Visa Data TDE (merch_prog_id). The host will send and receive this data. VisaNet: This value maps to and from data element 104, dataset 6E (Merchant Program Indentifier) in the VisaNet transaction message. S-123: Tag 92, MasterCard Installment Data Format: Variable depending on the subtags included. TDEs: POS Data 1 Tag 92 supports the Brazilian installment payment transaction (Parcelas Purchase). It maps data to the POS Data 1 TDE. In the Banknet and MDS external messages, it is used to parse and build data element 112, sub-elements 001 and 002. In the VisaNet external message, it is used to parse and build data element 43. Tag 92: MasterCard Installment Data Subtag Description Format 01 Installment plan type ANS 2 02 Number of installments ANS 2 03 Installment amount ANS 12 04 Total amount ANS 12 05 Interest rate ANS 5 06 Interest rate flag ANS 1 07 First payment date (DDMMYY) ANS 6 08 First installment amount ANS 12 09 Fee amount ANS 12 10 Tax amount ANS 12 11 Insurance amount ANS 12 12 Third party amount ANS 12 13 Record amount ANS 12 14 Total effective amount ANS 12 15 Domestic card acceptor tax ID AN 40 16 MasterCard Installment Payment Data 1 AN 3 BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 438 Data element definitions Tag 92: MasterCard Installment Data Subtag Description Format 17 MasterCard Installment Payment Data 2 ANS...720 18 MasterCard Installment Payment Data 3 ANS 38 19 Receipt Free Format ANS 512 20 Cuotas Installment Payment Response Data ANS..55 S-123: Tag 93, Mobile Payment Data Format: ANS 1 TDEs: MDS Maestro Tag 93 contains Mobile Payment Data used by the BankNet Interface and MasterCard Debit Switch (MDS). I This tag maps to data element 48 (Additional Data - Private Use), sub-element 48. For more information about this data element, refer to the BankNet Interface User Guide. Tag 93: Mobile Payment Data Subtag Description Format 01 Mobile payment indicator. Valid values are “1” (Issuer Domain) and “2” (Acquirer Domain). ANS 1 02 Mobile Remote Payment Transaction type, maps to DE 48 SE 48 SF 2. ANS 1 03 Mobile Phone number, maps to DE 48 SE 48 SF 3. 04 Convenience Fee, maps to DE 48 SE 48 SF 4. N 15 ANS 40 S-123: Tag 94, Airline Industry-Specific Data Format: Variable based on the subtags included TDEs: Travel and Entertainment Tag 94 contains airline industry-specific transaction data. Subtags 01-10, 0A, and 0B are mapped to VisaNet Field 104, Dataset ID 6. Subtags 11-14 are mapped to Visa DPS Field 104, Dataset ID 60. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 439 Data element definitions Tag 94: Airline Industry-Specific Data Subtag 01 Description Format Fare Basis Code-Leg 1 AN 6 The fare basis code for the first leg of the trip. 02 Fare Basis Code-Leg 2 AN 6 The fare basis code for the second leg of the trip. 03 Fare Basis Code-Leg 3 AN 6 The fare basis code for the third leg of the trip. 04 Fare Basis Code-Leg 4 AN 6 The fare basis code for the fourth leg of the trip. 05 Computerized Reservation System AN 4 Code indicating the computerized reservation system to make the reservation and purchase the ticket. 06 Flight Number-Leg 1 AN 5 Number of the airline flight to be taken on the first leg of the trip. 07 Flight Number-Leg 2 AN 5 Number of the airline flight to be taken on the second leg of the trip. 08 Flight Number-Leg 3 AN 5 Number of the airline flight to be taken on the third leg of the trip. 09 Flight Number-Leg 4 AN 5 Number of the airline flight to be taken on the fourth leg of the trip. 10 Trip Leg 1 Information. AN 7 Additional information about the first leg of the trip. 11 Trip Leg 2 Information. AN 7 Additional information about the second leg of the trip. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 440 Data element definitions Tag 94: Airline Industry-Specific Data Subtag 12 Description Trip Leg 3 Information. Format AN 7 Additional information about the third leg of the trip. 13 Trip Leg 4 Information AN 7 Additional information about the fourth leg of the trip. 14 Travel Agency Code/Name AN 33 A code indicating the travel agency. 0A Credit Reason Indicator AN 1 Code indicating the reason for a credit to the cardholder. Valid values are: A (Passenger transport ancillary fee cancellation) B (Airline ticket and passenger transport ancillary fee cancellation) C (Airline ticket cancellation) O (Other) P (Partial refund of airline ticket) 0B Ticket Change Indicator AN 1 Code indicating why a ticket was changed. Valid values are: C (Change to existing ticket) N (New Ticket) S-123: Tag 95, Passenger Transport Ancillary Data Format: Variable based on the subtags included TDEs: Travel and Entertainment Tag 95 contains ancillary services and passenger data that is used to parse and build Field 104, Dataset ID 6B in the VisaNet external message. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 441 Data element definitions Tag 95: Passenger Transport Ancillary Data Subtag 01 Description Format Code Format AN 2 Used to indicate which interchange interface set the data. Valid values include “01” (Visa) and “02” (Visa DPS). 02 Ancillary Ticket Document Number AN 15 Contains the form number assigned by the carrier for the transaction. This code is composed of the carrier code, form, and serial number without the check digit. 03 Ancillary Service Category 1 AN 4 (required) Must contain the ancillary service category code for the sole or primary type of service that is being provided 04 Ancillary Service Sub-category 1 AN 4 (optional) If present, it must contain a valid ancillary service subcategory code for the Ancillary Service Category 1 tag. 05 Ancillary Service Category 2 AN 4 (required) Must contain the ancillary service category code for the sole or primary type of service that is being provided 06 Ancillary Service Sub-category 2 AN 4 (optional) If present, it must contain a valid ancillary service subcategory code for the Ancillary Service Category 2 tag. 07 Ancillary Service Category 3 AN 4 (required) Must contain the ancillary service category code for the sole or primary type of service that is being provided BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 442 Data element definitions Tag 95: Passenger Transport Ancillary Data Subtag 08 Description Ancillary Service Sub-category 3 Format AN 4 (optional) If present, it must contain a valid ancillary service subcategory code for the Ancillary Service Category 3 tag. 09 Ancillary Service Category 4 AN 4 (required) Must contain the ancillary service category code for the sole or primary type of service that is being provided 0A Ancillary Service Sub-category 4 AN 4 (optional) If present, it must contain a valid ancillary service subcategory code for the Ancillary Service Category 4 tag. 0B Passenger Name AN 20 This tag must contain either the passenger’s name. If the passenger’s name is unavailable, this field must contain the cardholder’s name. For U.S. National, intra-regional Visa Europe, and domestic Visa Europe transactions, this tag cannot begin with a space on originals and their reversals requesting EIRF or any Custom Payment Service. 0C Issued in Connection with Ticket Number AN 15 If this purchase has a connection or relationship to another purchase, such as a baggage fee from a passenger transport ticket, this tag must contain the ticket document number for the other purchase. For standalone purchases, this tag must contain the same value as the Ancillary Ticket Document Number Tag. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 443 Data element definitions Tag 95: Passenger Transport Ancillary Data Subtag Description 0D Format Credit Reason Indicator AN 1 (optional) If present, this tag must contain one of the following values indicating the reason for the credit to the cardholder: A (Passenger transport ancillary fee cancellation) B (Airline ticket and passenger transport ancillary fee cancellation) O (Other) 0E Ancillary Fee AN..108 The subtag contains up to six instances of the fee and an instance is structured as follows: • • • • Amount Type AN 2 Currency Code N 3 Amount Sign AN 1 (values 'C' or 'D') Amount N 12 This value maps from data element 48, subelement 54, subfields 1 and 2 in the MDS transaction message. S-123: Tag 96, Network Token Service Format: Variable based on the subtags included TDEs: Network Tokenization Service Generic Data Tag 96 contains network token service data that is used to parse and build external messages for various interfaces. The following external messages use Tag 96: Interface External message fields and data elements AMEX GNS DE 34 DE 60 BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 444 Data element definitions Interface External message fields and data elements Banknet DE 48.26, 48.30, 48.33.01, 48.33.02, 48.33.05, 48.33.06, 48.33.07, 48.36, and 48.85 DE 120.1 - 120.7, 120.22, and 120.23 (tokenization complete notification messages) DE 120.1, 120.2, and 120.7 (tokenization activation code notification messages) DE 120.1 - 120.5, and 120.13 (tokenization event notification messages) DE 124 China UnionPay (CUP) DE 63.TK, subtags 01 and 07 CO-OP DE 124, tags T1, T2, T3, T4, T5, T6, T8, T9, TA, TB, and TP. DE 125, tag T9 Discover DE 56.01.01 FIS DE 124, tags T1, T2, T3, T4, T5, T6, T8, T9, TA, TB, and TP DE 125, tags T2, T3, and T4 MDS DE 48.30, 48.33.01, 48.33.02, 48.33.05, 48.33.06, 48.33.08, 48.33.09 DE 120.1 - 120.7, 120.22, and 120.23 (tokenization complete notification messages) DE 120.1 - 120.5, and 120.13 (tokenization event notification messages) NYCE DE 124, tags T1, T2, T3, T4, T6, T8, T9, TB, TC, TP, and TQ PULSE DE 124, tags T1, T2, T3, T5, T6, T8, T9, TA, TB, and TP DE 125, tags T2, T4, T5, and TB SAMA SPAN2 DE 47, tag 02, 07-10 DE 47.2, tags 05 and 06 SHAZAM DE 124, tag T07 STAR DE 107, tag TI DE 124, tags T1, T2, T3, T4, T5, T6, T7, T8, TA, TB, TP, and V1.2 DE 125, tag M5 Visa DPS DE 104, tag $TM BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 445 Data element definitions Interface External message fields and data elements VisaNet DE 44.15 DE 56.01.01 DE 115 DE 120.56 and 120.57 DE 123.67, subtag 03-05 DE 123.68, subtags 01 - 08, 10-14, 0A-0C, 1D, 1F31-1F33, 123.D4, DE 125.01, subtag 01 - 04-07, 125.02, subtags 03 - 09, and 0A DE 127.40, subtags 01 and 02 DE 127.PAN.41 subtags 01 and 02 127.TC.40 subtags 01 and 02 Tag 96: Network Token Service Subtag 01 Description Token data Format N var The token used to replace the cardholder Primary Account Number (PAN). 02 Token assurance level AN 2 The confidence level of the token to PAN/cardholder binding. 03 Token requester ID UN 11 The ID of the token requester. 04 Last 4 digits of PAN UN 4 The last four digits of the cardholder’s PAN. 05 PAN account range N 9 or N 19 The first nine digits of the PAN, or the full Visa cardholder PAN in the authorization response for a transaction initiated with a Visa token. 06 Account status AN 1 The account range’s status as regulated or non-regulated. 07 Token status • • • • • AN 1 1 = Active token 2 = Suspended token 3 = Deactivated token 4 = Expired token 5 = Inactive token BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 446 Data element definitions Tag 96: Network Token Service Subtag 09 Description Action indicator Format AN 1 Indicates the action to be taken on the token provided in DE 2. • • • • • 0 = Inquiry 1 = Suspend token 2 = Deactivate token 3 = Resume token 4 = Update PAN expiration date Note: This data is parsed when received on an inbound message; it is not built on an outbound message. 10 Replacement PAN Expiration Date N4 Expiration date that is replacing the number that is embossed, encoded, or both on the card that represents the cardholder's PAN. Format: YYMM 11 PAN reference number AN var Contains the value used as a substitute for the payment token that does not expose information about the payment token or the PAN that the payment token replaces. Length depends upon the interface using it. 12 Detokenization transaction ID AN var An ID assigned by the Token Service Provider that uniquely identifies the token lookup transaction. Length depends upon the interface using it. 13 Token type • • • • • 14 AN 2 00 = Unknown 01 = Card on file 02 = Secure element 03 = Host card emulation 04 = Quick read PAN information AN var Length depends upon the interface using it. 15 Token transaction identifier AN var Length depends upon the interface using it. 16 Token service provider AN var Indicates the service provider that created the token, for example VI for Visa or MC for MasterCard. Length depends upon the interface using it. 17 Token customer name AN var Length depends upon the interface using it. 18 Token expiration date AN var 19 Token trace ID AN var BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 447 Data element definitions Tag 96: Network Token Service Subtag Description Format 20 Card verification method at device N2 21 Contactless usage N1 Contains value indicating if the token is permitted for use in contactless transactions. • • 22 0 = Token is not permitted for use in contactless transactions 1 = Token is permitted for use in contactless transactions Card on file electronic commerce usage N1 Contains value indicating if the token is permitted for use in card on file electronic commerce transactions. • • 23 0 = Token is not permitted for use in card on file electronic commerce transactions 1 = Token is permitted for use in card on file electronic commerce transactions Mobile/Digital wallet electronic commerce usage • • N1 0 = Token is not permitted for use in mobile/digital wallet e-commerce transactions 1 = Token is permitted for use in mobile/digital wallet e-commerce transactions 24 Correlation ID AN 14 25 Number of active tokens for the primary account number ANS 2 26 Issuer product configuration ID 27 Consumer language 28 Final tokenization decision ANS 10 AN 2 ANS 1 The final tokenization decision that was used in the tokenization of the card. • • • 29 0 = Failed 1 = Approve 2 = Approve, but requires additional authentication Final tokenization decision indicator ANS 1 The element of the service that was responsible for determining the final tokenization decision. • • • • 1 = Tokenization eligibility response 2 = Tokenization authorization response 3 = Issuer predefined tokenization rules 4 = Mobile application 30 T&C identifier ANS 32 31 T&C date and time ANS 10 32 Number of activation attempts BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 ANS1 448 Data element definitions Tag 96: Network Token Service Subtag Description Format 33 Token unique reference 35 Tokenization event indicator 36 Device type AN8 37 Tokenization event reason code AN 2 38 Event requestor 39 PAN source AN 2 40 Device number AN2 42 Device ID 44 Wallet provider ID ANS2…3 45 Wallet account ID ANS32 46 Wallet account email address AN..32 47 Wallet provider tokenization recommendation AN 1 48 Wallet service provider tokenization recommendation standard version AN 2 49 Wallet service provider device score N2 50 Wallet service provider account score N2 51 Wallet service provider tokenization recommendation reason ANS 6 53 Activation code ANS 8 54 Activation code expiration date and time N 10 57 Token activation code verification result AN 1 58 Token storage type AN 2 60 Activation methods AN 286 61 Device name ANS 20 62 Consumer's activation code distribution method preference 63 Device location 64 Device IP address 65 Provisioning message type AN 2 66 Mobile number last 4 digits ANS 4 67 Payment application instance ID 68 Primary account number card sequence number 69 Wallet service provider account ID hash 70 Seller ID AN 20 71 Payment account reference AN 35 72 Token information verification indicator BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 ANS 48 N1 ANS 1 ANS48 ANS 165 ANS 9 ANS 12 ANS 48 AN 3 ANS 64 AN 1 449 Data element definitions Tag 96: Network Token Service Subtag Description Format 73 Token-based QR code data 74 Number of suspended tokens 75 Active account management velocity checking result AN2 76 Issuer special condition codes AN 2 78 Last updated by AN 1 79 Number of inactive tokens N2 80 Number of activation codes Issued N2 81 AKM elapsed total N4 82 AKN NOT N3 83 AKM CTTA N7 84 CVV2 authorization request data response yype 85 Visa token score 86 Visa token decisioning 87 Terms and conditionsverification AN 64 88 Issuer terms and conditions date/time AN 32 89 Token vault PAN update - replacement PAN 90 Activation verification result 91 Starting query number 92 Additional trace data 93 Device IMEI AN 15 94 Android ID AN 16 95 Provisioning attempts on this advice N3 96 Account to device bonding age N5 97 Device country AN 2 98 Protection type N3 99 Presentation type N3 0A Device serial number 0B Location source 0C Device time zone 0D Device time zone setting 0E Device bluetooth MAC 0F OS type 0G OS version BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 AN 32 N2 ANS 2 N2 AN 2 N13..19 AN 1 N4 ANS..24 AN 20 N3 AN 1 N3 AN 16 N3 AN 16 450 Data element definitions Tag 96: Network Token Service Subtag Description Format 0H OS build AN 16 0L Wallet provider PAN age N5 0M User account age N5 0N Wallet account age N5 0P Days since last activity N5 0Q Number of transactions in the last 12 months N5 0R Days since last account N5 0S Suspended cards in account N3 0T Wallet account country 0U Number of active tokens N3 0V Number of devices with active tokens N3 0W Number of active tokens in all devices N3 0X Consumer entry mode N3 0Y Additional transaction analysis data 1A Asset ID 1B Return code AN 2 1C Token effective date AN 4 1D Wallet account email address age AN 4 1E Wallet provider phone score AN 2 1G Tokenized card verification results 1H LUK/SUK replenishment status N 02 1I CDCVM method A A 02 1J Token update reason text AN 2 AN 2 AN 12 AN 02 ANS 100 S-123: Tag 97, CUP Recurring Data Format: Variable based on the subtags included TDEs: CUP Recurring Data Tag 97 contains recurring CUP data that is passed to and from the CUP Recurring Data TDE. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 451 Data element definitions Tag 97: CUP Recurring Data Subtag 01 Description Format User ID Category. ANS 2 China UnionPay (CUP): This value maps to and from data element 48, Usage PZ in the CUP transaction message. 02 User ID Payment Item ANS 40 China UnionPay (CUP): This value maps to and from data element 48, Usage PZ in the CUP transaction message. 03 Payment Method Tag ANS 2 China UnionPay (CUP): This value maps to and from data element 48, Usage PZ in the CUP transaction message. 04 Payment Method Type ANS 40 China UnionPay (CUP): This value maps to and from data element 48, Usage PZ in the CUP transaction message. 05 Time Span of Relationship N3 China UnionPay (CUP): This value maps to and from data element 48, Usage PZ in the CUP transaction message. 06 Maximum Mandatory Amount N 12 China UnionPay (CUP): This value maps to and from data element 48, Usage PZ in the CUP transaction message. 07 Minimum Mandatory Amount N 12 China UnionPay (CUP): This value maps to and from data element 48, Usage PZ in the CUP transaction message. 08 Payment Period ANS 17 China UnionPay (CUP): This value maps to and from data element 48, Usage PZ in the CUP transaction message. S-123: Tag 98, Region Specific Payment Data Format: Variable based on the subtags included TDEs: Region Specific Payment Data Tag 98 contains payment data that is applicable to a country or region, and that is to be passed to and accepted from a host. Tag 98 is in TLV format. The structure of the data in this tag is as follows: Tag 98: Region Specific Payment Data Subtag 01 Description Card Issuer Data This value maps to and from data element 124, subfield 1 in the MDS and Banknet transaction message. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 452 Data element definitions Tag 98: Region Specific Payment Data Subtag 02 Description Tax (IVA) This value maps to and from data element 124, subfield 2 in the MDS and Banknet transaction message. 03 Tax Amount Base This value maps to and from data element 124, subfield 3 in the MDS and Banknet transaction message. 04 Retailer Data This value maps to and from data element 124, subfield 4 in the MDS and Banknet transaction message. 05 Terminal Acquirer Data This value maps to and from data element 124, subfield 5 in the MDS and Banknet transaction message. 06 Original Processing Code This value maps to and from data element 124, subfield 6 in the MDS and Banknet transaction message. 07 Bill Payment/Top up Data This value maps to and from data element 124, subfield 7 in the MDS and Banknet transaction message. 08 Local POS Data This value maps to and from data element 124, subfield 8 in the MDS and Banknet transaction message. 09 Local Response Codes This value maps to and from data element 124, subfield 9 in the MDS and Banknet transaction message. 10 Original Transaction Data This value maps to and from data element 124, subfield 10 in the MDS and Banknet transaction message. 11 Payment Indicator This value maps to and from data element 124, subfield 11 in the MDS transaction message. 12 Interchange Code This value maps to and from data element 124, subfield 12 in the MDS transaction message. 13 Interchange Fixed Amount This value maps to and from data element 124, subfield 13 in the MDS transaction message. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 453 Data element definitions Tag 98: Region Specific Payment Data Subtag 14 Description Interchange Percentage This value maps to and from data element 124, subfield 14 in the MDS transaction message. 15 Local Interchange Group This value maps to and from data element 124, subfield 15 in the MDS transaction message. 16 IAC Tax Amount This value maps to and from data element 124, subfield 16 in the MDS transaction message, or to and from data element 124, subfield 11 in the Banknet transaction. 17 Customer ID This value maps to and from data element 112, subfield 11 in the Banknet transaction message. 18 Merchant Tax ID This value maps to and from data element 112, subfield 29 in the MDS transaction message. 19 Brazil Commercial and Financing Data This value maps to and from data element 112, subfield 12 in the Banknet transaction message. 20 CAFIS POS Data This value maps to and from data element 112, subfield 30 in the Banknet transaction message. 21 CAFIS Response Code This value maps to and from data element 112, subfield 31 in the Banknet transaction message. 22 Additional Installment Payment Response Data This value maps to and from data element 112, subfield 16 in the Banknet transaction message. 23 Brazil Post-Dated Transaction Data This value maps to and from data element 112, subfield 18 in the Banknet transaction message. 24 Cuotas Payment - Installment Payment Response Data This value maps to and from data element 112, subfield 03 in the Banknet transaction message 25 Argentina Domestic - Billing Period This value maps to and from data element 124, subfield 1 in the MDS transaction message. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 454 Data element definitions Tag 98: Region Specific Payment Data Subtag 26 Description Argentina Domestic - Recurrent Payment Reference Number This value maps to and from data element 124, subfield 2 in the MDS transaction message. 27 Argentina Domestic - Card Acceptor Tax ID This value maps to and from data element 124, subfield 3 in the MDS transaction message. 28 Argentina Domestic - Legal Corporate Name This value maps to and from data element 124, subfield 4 in the MDS transaction message. 29 Colombian Domestic Fee Inquiry Mapped to and from data element 112, subfield 35 in the Banknet transaction message. 30 Argentina Domestic - Cardholder Identification Method This value maps to and from data element 124, subfield 5 in the MDS transaction message. 31 Argentina Domestic - POS Invoice Number This value maps to and from data element 124, subfield 6 in the MDS transaction message. 32 Netherlands Primary Cardholder ID This value maps to and from data element 112, subelement 37, subfield 1 in the Banknet transaction message. 33 Netherlands Secondary Cardholder ID This value maps to and from data element 112, subelement 37, subfield 2 in the Banknet transaction message. S-123: Tag 99, Healthcare Services Format: Variable based on the subtags included TDEs: Healthcare TDE Tag 99 contains service information for healthcare transactions, and that is to be passed to and accepted from a host. The structure of the data in this tag is as follows: BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 455 Data element definitions Tag 99: Healthcare Services Subtag Description 01 Length Healthcare Data • • • • AN..95 Provider ID - AN 9 Service Type - AN 2 Payer ID - AN 6 Reason Code - AN 2 Occurs up to 5 times. 02 Inventory Informational Approval System (IIAS) Substantiation Indicator AN 1 0 = An IIAS was not used at the point of sale 1 = An IIAS was used at the point of sale 2 = Merchant is exempt from using an IIAS 4 = Transaction submitted as real-time substantiated but from a non-IIAS certified merchant S-123: Tag 0A, PULSE Data Format: Variable based on the subtags included TDEs: PULSE Data, Multi-Clearing Sequence Number Tag 0A contains data to support Pay Express transactions in the PULSE interface. This tag carries subtag data as shown in the table below. Tag 0A: PULSE Data Subtag Description Format 01 Reference Number AN 9 02 Merchant Transaction ID 03 Multi-clear Sequence Number AN 2 04 Multi-clear Count Number AN 2 AN 16 S-123: Tag 0B, American Express Additional Card Information Format: 0-255, Variable based on the subtags included TDEs: Card Additional Data Tag 0B contains data to support the Goods Sold data in the AMEX CAPN interface. This tag carries subtag data as shown in the table below. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 456 Data element definitions Tag 0B: American Express Additional Card Information Subtag Description 01 American Express Goods Sold Code 02 American Express card present Goods Sold data version 03 Seller ID set to Payment Service Provider's (Aggregators) or OptBlue Participant's specific seller or vendor 04 Seller email address set to the seller email address 05 Seller telephone set to the seller telephone Format AN 4 N2 ANS 20 LLVAR ANS ..40 N 20 S-123: Tag 0C, Security Services Format: 0-96, Variable based on the subtags included TDEs: MasterCard M/Chip On-Behalf Services Tag 0C contains data mapped by the MDS interface to the Security Services Table of the MasterCard M/Chip OnBehalf Services TDE. This tag carries subtag data as shown in the table below, with multiple occurrences of 6 bytes. Tag 0C: Security Services Subtag Description Format 01 Security indicator AN 3 02 Security data AN 3 S-123: Tag 0D, MasterCard Indicators Format: Variable based on the subtags included TDEs: MasterCard Magnetic Stripe Compliance TDE Tag 0D contains MasterCard Indicators, including the MasterCard Magnetic Stripe Compliance indicators. This tag is mapped from DE 48 (Additional Data-Private Use) Subelement 88 (Magnetic Stripe Compliance Status Indicator) and Subelement 89 (Magnetic Stripe Compliance Error Indicator) in the Banknet transaction message. For information on Banknet transaction messages, refer to the appropriate Banknet technical specification. Tag 0D: MasterCard Indicators Subtag Description 01 Magnetic Stripe Compliance Status Indicator BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 Format AN 1 457 Data element definitions Tag 0D: MasterCard Indicators Subtag Description 02 Format Magnetic Stripe Compliance Error Indicator AN 1 S-123: Tag 0E, Authentication Indicator Format: N1 TDEs: Generic Data TDE One numeric character indicating the whether the transaction qualified for Authentication Service Type 1 or Type 2. S-123: Tag 0F, Merchant On-Behalf Services Format: ANS...99 TDEs: MasterCard M/Chip On-Behalf Services TDE Used to parse DE 48, SE 51 (MasterCard M/Chip On-Behalf Services TDE, Merchant On-behalf Services data member) in 0110, 0130 and 0410 messages received inbound from the network to the ISO Host Interface 1993 external data that houses Banknet DE 48, SE 51 (DE 123, Tag 0F). It is also mapped to VisaNet data element 104.65.23. S-123, Tag 0G, Time Validation Information Format: Variable based on the subtags included TDEs: Generic Data TDE Tag 0G contains Time Validation Information data and is mapped to and from MasterCard DE 48.49 and Banknet DE 48.49. The tag is mapped to the Generic Data TDE with the outer key MC_DATA and inner key TIME_VALID_INFO. Tag 0G: Time Validation Information Subtag Description Format 01 Time Value N8 02 Time Discrepancy Value N5 03 Time Discrepancy Indicator AN 2 S-123: Tag 0H, Transaction Integrity Class Format: AN 2 TDEs: Generic Data TDE Tag 0H contains Transaction Integrity Class data and is mapped to and from MasterCard DE 48.52, Banknet DE 48.52, and VisaNet DE 104.65.28. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 458 Data element definitions The tag is mapped to the Generic Data TDE with the outer key MC_DATA and inner key TXN_INTEGRITY_CLASS. S-123: Tag 0I, STAR Access Data Format: ANS...999 TDEs: Generic Data TDE, STAR Data Field TDE Tag 0I contains STAR Access data and is mapped to and from STAR Access DE 110 format AX. Tag 0I: STAR Access Data Subtag 01 Description Access Transaction Sequence Number (ATSN) Format AN 15 Unique identifier assigned by the STAR network upon receipt of an authorization request from the acquirer that can be used to match messages throughout the life cycle of a transaction. 02 Incremental Authorization AN 1 Valid values: • • 03 'I' - Incremental authorization Space - Not an incremental authorization Purchase Identifier AN 26 Represents customer code, rental agreement number, hotel folio number, airline ticket number, etc. 04 Merchant Ship Date N8 The anticipated or true date the merchandise or product is mailed. (YYYYMMDD) 05 Merchant Back Order AN 2 Valid values: • • 06 '00' or space - Not a backordered item '01'- Backordered item Multiple Clearing Transaction Number N3 Indicates transaction is part of multiple shipments, number of anticipated shipments. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 459 Data element definitions Tag 0I: STAR Access Data Subtag Description 07 Multiple Clearing Transaction Count Format N3 Number of this shipment that the record represents. 08 Acquirer Reference Number 09 SMS/DMS Indicator AN 23 AN 3 Set by the network to indicate whether the Acquirer Processor is dual message (DMS) or single message (SMS). 10 Reserved for future use - 11 Reserved for future use - 12 Reserved for future use - 13 Authorized Amount N 12 S-123: Tag 0J, Advice Reason Detail Code Format: Variable based on the subtags included TDEs: MasterCard Advice Detail TDE Tag 0J contains a conditional detail code that provides specific information regarding the exact purpose of the MDS or Banknet Advice message. This field maps to data element 60 (Advice Reason Code), subfield 2, in the MDS and Banknet transaction message. Tag 0J: Advice Reason Detail Code Subtag 01 Description MasterCard Advice Detail Code Format N4 S-123: Tag 0M, Secure E-commerce Indicators Format: Variable based on the subtags included TDEs: Generic Data TDE Tag 0M contains a code indicating whether a card transaction qualifies as a secure e-commerce transaction. For Discover, this code indicates whether the cardholder was authenticated using ProtectBuy. This field maps to data element 61 (Point of Sale Data), position 9 (POS E-commerce Transaction Indicator) in the Discover transaction message. The outer key used to store this data in the Generic Data TDE is PROTECT_BUY. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 460 Data element definitions Tag 0M: Secure E-commerce Indicators Subtag Description 01 Format Discover POS E-commerce Transaction Indicator. Valid values: • • N1 5 = Card Transaction is a secure e-commerce transaction (Cardholder authenticated using ProtectBuy) 6 = Merchant attempted to authenticate the Cardholder information using ProtectBuy, but was not able to complete authentication because the Cardholder or the Issuer does not participate in ProtectBuy. Generic Data TDE - inner key TXN_IND S-123: Tag 0N, RuPay e-Commerce Indicators Format: Variable based on the subtags included TDEs: Generic Data TDE Tag 0N contains codes used for RuPay e-Commerce. The outer key used to store this data in the Generic Data TDE is INTFRPY. Tag 0N: RuPay e-Commerce Indicators Subtag Description 01 Format Encryption Technique Indicator AN 2 Generic Data TDE - inner key ENCRYPT_IND 02 Terminal Operating Environment AN 1 Generic Data TDE - inner key TERM_OPER_ENVMT S-123: Tag 0P, Terminal Conversion Rate Format: N8 TDEs: Conversion Rate TDE Tag 0P contains terminal conversion rate data and is mapped to and from RuPay DE 48.080. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 461 Data element definitions S-124: Reserved for Private Use Format: LLLLVAR ANS ..9999 TDEs: Varies by tag, mainly Generic Data TDE The Reserved for Private Use (S-124) data element is used to pass unmapped data fields as received from network interfaces (such as Visa and Banknet) through to the host. This data element is currently only processed for request and advice request messages and is not processed for response messages. The data is predominately obtained from the Generic Data TDE to build outbound requests and is used to populate the Generic Data TDE on inbound requests. Each tag and subtag is mapped to a corresponding outer key and inner key in the Generic Data TDE. The mapping between the tag and Generic Data TDE outer key is configured in the Genrc_Data_Outer_Tag data source, and the mapping between the subtag and the Generic Data TDE inner key is configured in the Genrc_Data_Inner_Tag data source. Whether a tag or subtag is output in S-124 is governed by whether the mapping is present in the Genrc_Data_Outer_Tag or Genrc_Data_Inner_Tag data sources. Suppression of tags is possible by removing entries from these data sources. These data sources currently do not have a User Interface so any changes must be done using DALCI files. They do have OLTPs and need to be reloaded and warmbooted for changes to take effect. Two-character tags starting with 'P' 'Q' and 'R' have been reserved for use in customer specific modifications (CSMs). When using a custom tag, the two-character sub-tag does not need to use custom values. If an additional custom subtag is required for an existing tag, two-character subtags starting with 'P' 'Q' and 'R' have been reserved for use in CSMs. Use of tags This data element carries tagged data items. The tags defined for this data element are listed below. Tagged data items are structured in the following manner: a tag identifying the type of data, followed immediately by a four-digit length (LLLL) identifying the length of the data, followed immediately by the data itself. The data type can be alphanumeric or special characters, but ACI recommends using alphanumeric characters. Tag + LLLL + data. Tagged data varies in length depending on the tag, and multiple tagged data items can be included in any order within the data element. Use of subtags Some tags use subtags to identify the various data fields involved in the file action. Refer to the specific tag documentation for descriptions of the supported subtags and their purposes. Subtag data is structured as follows: the subtag identifying the type of field data, followed immediately by a threedigit length (LLL) identifying the length of the field data, followed immediately by the field data itself. Subtag + LLL + field data. Multiple subtags can be present within a single tag, and can be in any order within the tag. S-124: Tag 01, Acquirer Data Format: Variable depending on the subtags included BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 462 Data element definitions TDEs: Generic Data Acquirer Component ID Sequential Routing Info Acquirer STAN Acquirer POS Entry Mode VISA Data Acquirer POS Condition Code Tag 01 contains data received from the acquiring endpoint for fields that are defined in ISO8583 (1987 or 1993), and so could be populated by any network. The outer key used to store this data in the Generic Data TDE is ACQ_DATA. The following table describes the subtags and the inner key used to store the data in the Generic Data TDE. When building an outbound request, BASE24-eps may obtain the data from multiple TDEs in the order listed. When parsing an inbound request, BASE24-eps will always populate the Generic Data TDE. Tag 01: Acquirer Data Subtag 01 Description Acquiring endpoint component ID • • • 02 • 03 • 04 • • Variable based on endpoint. Usually AN 3…12 Generic Data TDE - inner key ACQ_POS_ENTRY_MDE Acquirer POS Entry Mode TDE Acquiring endpoint POS Condition Code (ISO DE 25) • N6 Generic Data TDE - inner key ACQ_STAN Acquirer STAN TDE Acquiring endpoint POS Entry Mode (ISO DE 22) • ANS 8 Generic Data TDE - inner key ACQ_CMPNT_ID Sequential Routing Information TDE Acquirer Component ID TDE Acquiring endpoint System Trace Audit Number (ISO DE 11) • Format Variable based on endpoint. Usually AN 2 Generic Data TDE - inner key POS_COND_CDE Visa Data TDE Acquirer POS Condition Code TDE BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 463 Data element definitions Tag 01: Acquirer Data Subtag Description 05 Format Acquiring additional response data (ISO DE 44) • Variable based on endpoint. Usually ANS..99 Generic Data TDE - inner key ADNL_RESP_DATA S-124: Tag 02_HISO 1993 Data Format: Variable depending on the subtags included TDEs: Generic Data Tag 02 contains data received from the acquiring endpoint for fields that are related to HISO 1993. The outer key used to store this data in the Generic Data TDE is HISO93. The following table describes the subtags and the inner key used to store the data in the Generic Data TDE. Tag 02: HISO 1993 Data Subtag Description 01 Acquiring endpoint interface name when received inbound from a HISO 1993 acquiring interface in DE 62 tag 17 Format ANS 16 Generic Data TDE - inner key ACQ_INTF_NAM S-124: Tag 03, Visa Data Format: Variable depending on the subtags included TDEs: Generic Data Tag 03 contains data received from the acquiring endpoint for fields that are related to Visa network data. The outer key used to store this data in the Generic Data TDE is VISA. The following table describes the subtags and the inner key used to store the data in the Generic Data TDE. Tag 03: Visa Data Subtag 01 Description Visa Additional POS Information (Visa DE 60) Format AN 12 Generic Data TDE - inner key ADNL_POS_INFO BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 464 Data element definitions Tag 03: Visa Data Subtag Description 02 Visa Other Amounts (Visa DE 61) Format N ..36 Generic Data TDE - inner key OTHER_AMTS 03 Visa Custom Payment Service Fields Bitmap (Visa DE 62.0) AN 16 Generic Data TDE - inner key CSTM_PMNT_SRVC_FLDS S-124: Tag 04, MasterCard Data Format: Variable based on the subtags included TDEs: Generic Data TDE Tag 04 contains data received from the acquiring endpoint for fields that are related to the MasterCard network data. The outer key is used to store this data in the Generic Data TDE is MC. The following table describes the subtags and the inner key used to store the data in the Generic Data TDE. Tag 04: MasterCard Data Subtag Description 01 MasterCard Processor Pseudo ICA Format N7 Generic Data TDE - inner key PROCESSOR_PSEUDO_ICA 02 MasterCard Transaction Disposition AN 2 Generic Data TDE - inner key TXN_DISP 03 MasterCard Test Results AN..87 Generic Data TDE - inner key TST_RSLT 04 MasterCard Account Data Compromise Information ANS 30 Generic Data TDE - inner key ACCT_DATA_CMPRMS_INFO 05 MasterCard Account Type Indicator ANS 1 Generic Data TDE - inner key ACCT_TYP_IND BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 465 Data element definitions Tag 04: MasterCard Data Subtag Description 06 Banknet Debt Repayment Receiver Last Name Format ANS 35 Generic Data TDE - inner key DEBT_RPMNT_RCV_LAST_NAM 07 Banknet Debt Repayment Receiver Postal Code ANS 10 Generic Data TDE - inner key DEBT_RPMNT_RCV_POSTAL_CD E 08 Banknet Debt Repayment Receiver Date of Birth AN 8 Generic Data TDE - inner key DEBT_RPMNT_RCV_DOB 09 Banknet Debt Repayment Receiver Account Number ANS 20 Generic Data TDE - inner key DEBT_RPMNT_RCV_ACCT_NUM S-124: Tag 05, CBAE Data Format: Variable depending on the subtags included TDEs: Generic Data Tag 05 contains data received from the acquiring endpoint for fields that are related to the French CBAE (Cartes Bancaires Acquéreur-Emetteur, or Cartes Bancaires Acquirer-Issuer) network data. The outer key used to store this data in the Generic Data TDE is CBAE. The following table describes the subtags and the inner key used to store the data in the Generic Data TDE. Tag 05: CBAE Data Subtag Description 01 Format CBAE Acquiring Institution Country N 3 Code (CBAE DE 19) where nonstandard values are used (900-999) Generic Data TDE - inner key ACQ_CNTRY_CDE S-124: Tag 06, Fraud Enhanced Data Format: Variable based on the subtags included TDEs: Generic Data BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 466 Data element definitions Tag 06 contains data specific to fraud. The outer key used to store this data in the Generic Data TDE is ECOM_FRAUD_DATA. The following table describes the subtags and the inner key used to store the data in the Generic Data TDE. Tag 06: Fraud Enhanced Data Subtag Description 01 Last Registered User Profile Change Date Format N 8 (DDMMCCYY) Generic Data TDE - inner key RGSTR_USER_LAST_CHNG_DAT S-124: Tag 08, PROSA Data Format: Variable depending on the subtags included TDEs: Generic Data Tag 08 contains data specific to the PROSA interface. The outer key used to store this data in the Generic Data TDE is PROSA. The inner keys are the same as the subtags. The following table describes the subtags used to store the data in the Generic Data TDE. Tag 08: PROSA Data Subtag Description Format Q1 Authorization Identification Mode ANS 2 Q2 Media Access Indicator AN 2 Q5 Original Amounts AN 104 Q6 Deferred Payments AN 6 QM MasterCard Debit AN 12 QV Mobile Top-up AN 74 S: 124: Tag 09, LINK LIS5 Format: Variable depending on the subtags included TDEs: Generic Data Tag 09 contains data received from the acquiring endpoint for fields that are related to LINK LIS5 network data. The outer key used to store this data in the Generic Data TDE is INTFLIS5. The following table describes the subtags and the inner key used to store the data in the Generic Data TDE. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 467 Data element definitions Tag 09: LINK LIS5 Subtag Description 01 Automated Deposit Type (LIS5 DE 61 subfield 15) Format ANS 1 Generic Data TDE - inner key DEPOSIT_TYPE 02 Device Deposit Capability (LIS5 DE 61 subfield 16) ANS 1 Generic Data TDE - inner key DEPOSIT_CAP S-124: Tag 10, RuPay Format: Variable depending on the subtags included TDEs: Generic Data Tag 10 contains data received from the acquiring endpoint for fields that are related to RuPay network data. The outer key used to store this data in the Generic Data TDE is INTFRPY. The following table describes the subtags and the inner key used to store the data in the Generic Data TDE. Tag 10: RuPay Subtag Description 01 Issuer Supplied ID (RuPay Field 48 Tag 077) Format ANS..40 Generic Data TDE - inner key: IVR_UNIQUE_ID 02 UIDAI Authentication Code (RuPay Field 62) ANS..999 Generic Data TDE - inner key: UIDAI_AUTH_CDE 03 Finger Print Minutiae (RuPay Field 63) ANS..999 Generic Data TDE - inner key: BIOMETRIC_ENCRYPT_DATA 04 Additional Biometric Data 1 (RuPay Field 126) ANS..999 Generic Data TDE - inner key: ADNL_BIOMETRIC_DATA_126 BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 468 Data element definitions Tag 10: RuPay Subtag Description 05 Additional Biometric Data 2 (RuPay Field 127) Format ANS..999 Generic Data TDE - inner key: ADNL_BIOMETRIC_DATA_127 06 ECI Indicators (RuPay Field 48, Tag N 2 056) Generic Data TDE - inner key: E_COM_IND 07 UID Number (RuPay Field 48, Tag 066) N 12 Generic Data TDE - inner key: UID_NUM 08 Income Tax PAN Number (RuPay Field 48, Tag 067) AN 10 Generic Data TDE - inner key: TAX_PAN 09 Customer Telephone Number (RuPay Field 48, Tag 074) N 12 Generic Data TDE - inner key: CUST_PHN_NUM 10 Transaction Identifier (RuPay Field 48, Tag 079 ) AN 4 Generic Data TDE - inner key: TRANS_ID 11 Authorization Response Code (RuPay Field 48, Tag 081) N4 Generic Data TDE - inner key: AUTH_RESP_CDE 12 Source Of Fund (RuPay Field 48, Tag 082) N2 Generic Data TDE - inner key: SRC_FUND 13 OCT - Remitter instrument type (RuPay Field 104, Tag 008) ANS 1 Generic Data TDE - inner key: DE104.008 BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 469 Data element definitions Tag 10: RuPay Subtag Description 14 OCT- Remitter instrument ID (RuPay Field 104, Tag 009) Format ANS 50 Generic Data TDE - inner key: DE104.009 15 OCT - Payload Format Indicator (RuPay Field 104, Tag 013) N2 Generic Data TDE - inner key: DE104.013 16 OCT - Point of initiation method (RuPay Field 104, Tag 014 ) N2 Generic Data TDE - inner key: DE104.014 S-124: Tag 11, Additional Cardholder Verification Format: Variable depending on the subtags included TDEs: Generic Data Tag 11 contains additional cardholder verification data. The outer key used to store this data in the Generic Data TDE is ADNL_CRDHLD_VRFY. The following table describes the subtags and the inner key used to store the data in the Generic Data TDE. Tag 11: Additional Cardholder Verification Subtag Description 01 MasterCard E-ID Format N2 Generic Data TDE - inner key: MC_E_ID S-124:Tag 12, SAMA SPAN2 Data Format: Variable depending on the subtags included TDEs: Generic Data Tag 12 contains eCommerce and mail or telephone order information for SAMA SPAN2. The outer key used to store this data in the Generic Data TDE is INTSPN2. The following table describes the subtags and the inner key used to store the data in the Generic Data TDE. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 470 Data element definitions Tag 12: SAMA SPAN 2 Data Subtag Description Format 01 Merchant Refund / Reversal Indicator A1 02 Transaction Mode Indicator A2 03 Recurring Payment Details AN 10 04 mada PSP Identifier A4 05 eCommerce and MO/TO data Card Scheme Indicator A2 S-124: Tag 13, FIS PayNet Payment Data Format: Variable depending on the subtags included TDEs: Generic Data Tag 13 contains payment data for the FIS Efunds Interface from DE-105 through DE-108. The outer key used to store this data in the Generic Data TDE is INTFFIS_ PMNT . The following table describes the subtags and the inner key used to store the data in the Generic Data TDE. Tag 13: FIS PayNet Payment Data Subtag Description Format 01 Consumer billing account number ANS..25 02 Receiver phone/pager number ANS .. 40 03 Receiver's e-mail address ANS..60 04 Funder's e-mail address ANS..60 05 Funder text ANS..50 06 Merchant/biller invoice number ANS..25 07 Merchant/Biller's email address ANS..60 08 Payment description ANS..50 S-124: Tag 14, FIS DE-109 Data Format: Variable depending on the subtags included TDEs: Generic Data Tag 14 contains Sender data for the FIS Efunds Interface from DE-109 . The outer key used to store this data in the Generic Data TDE is INTFFIS_DE109 . The following table describes the subtags and the inner key used to store the data in the Generic Data TDE. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 471 Data element definitions Tag 14: FIS DE-109 Data Subtag Description Format 01 Sender account number AN..34 02 Sender date of birth AN..08 (MMDDYYYY) 03 Sender e-mail address AN..30 04 Sender funding source AN2 values 01-06 05 Sender general identification AN..50 06 Sender masked PAN AN..19 07 Sender mobile service provider name AN..30 08 Sender optional message AN..37 09 Sender phone number AN..20 10 Sender participation ID AN..30 11 Sender name AN..41 12 Sender street address AN..50 13 Sender city AN..25 14 Sender state/province AN..3 15 Sender country code AN..3 16 Sender postal code AN..10 17 Sender place, apartment, suite, office AN..9 18 Sender country AN..24 19 Sender identification type AN..2 20 Sender identification number ANS..25 21 Sender identification country code ANS..3 22 Sender identification expiration date ANS..8 (MMDDYYYY) 23 Sender nationality ANS..3 24 Sender country of birth ANS..12 25 Sender original date ANS..6 26 Sender name 2 or first name AN..24 27 Sender structured sender namemiddle name ANS..80 28 Sender structured name ANS..80 29 Sender tag OF AN..5 30 Sender tag O1 AN..19 BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 472 Data element definitions Tag 14: FIS DE-109 Data Subtag Description Format 31 Sender cell phone number including AN..20 country and area codes 32 Sender work phone number including country and area codes AN..20 33 Sender fax number including country and area codes AN..20 34 Sender pager number including country and area codes AN..20 35 Sender customer service number including country and area codes AN..20 36 Sender transaction description AN..11 37 Sender transaction purpose AN 2 38 Sender unique reference number AN..19 39 Sender URL of online merchant AN..99 S-124: Tag 15, FIS DE-110 Data Format: Variable depending on the subtags included TDEs: Generic Data Tag 15 contains Receiver data for the FIS Efunds Interface from DE-110 . The outer key used to store this data in the Generic Data TDE is INTFFIS_DE110 . The following table describes the subtags and the inner key used to store the data in the Generic Data TDE. Tag 15: FIS DE-110 Data Subtag Description Format 01 Receiver account number AN..34 02 Receiver date of birth AN..08 (MMDDYYYY) 03 Receiver email address AN..30 04 Receiver general identification AN..50 05 Receiver masked PAN AN..19 06 Receiver mobile service provider name AN..30 07 Receiver optional message AN..45 08 Receiver mobile phone number AN..20 09 Receiver name AN..41 10 Receiver street address AN..50 BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 473 Data element definitions Tag 15: FIS DE-110 Data Subtag Description Format 11 Receiver city AN..25 12 Receiver state/province AN..3 13 Receiver country code AN..3 14 Receiver postal code AN..10 15 Receiver place, apartment, suite, office AN..9 16 Receiver country AN..24 17 Receiver identification type AN..2 18 Receiver identification number ANS..25 19 Receiver identification country code ANS..3 20 Receiver identification expiration date AN..8 21 Receiver nationality ANS..3 22 Receiver country of birth ANS..12 23 Receiver original date ANS..6 24 Receiver name 2 or first name AN..24 25 Receiver structured receiver namemiddle name ANS..80 26 Receiver structured name ANS..80 27 Receiver tag OF AN..5 28 Receiver tag O1 AN..19 29 Receiver cell phone number including country and area codes AN..20 30 Receiver phone number including country and area codes AN..20 31 Receiver fax number including country and area codes AN..20 32 Receiver pager number including country and area codes AN..20 33 Receiver customer service number including country and area codes AN..20 34 Receiver unique reference number AN..19 Enter the actual information in this section (optional). Enter an example to illustrate your reference here (optional). BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 474 Data element definitions S-124: Tag 16, FDR 184 Data Format: Variable depending on the subtags included TDEs: Generic Data Tag 16 contains data received from the acquiring endpoint for fields that are related to FDR 184 network data. The outer key used to store this data in the Generic Data TDE is INTFFDR. The following table describes the subtags and the inner key used to store the data in the Generic Data TDE. Tag 16: FDR 184 Data Subtag Description 01 Detailed Decline Reason Code (FDR 184 DE 123 Tag DR) Format AN 4 Generic Data TDE - inner key DeclineReasonCode S-127: Reserved for Private Use Format: LLLLVAR ANS ..9999 TDEs: Varies by tag The Reserved for Private Use (S-127) data element is used for a number of purposes, depending on the information carried. Use of tags This data element carries tagged data items. The tags defined for this data element are listed below. Tagged data items are structured in the following manner: a tag identifying the type of data, followed immediately by a four-digit length (LLLL) identifying the length of the data, followed immediately by the data itself. The data type can be alphanumeric or special characters, but ACI recommends using alphanumeric characters. Tag + LLLL + data. Tagged data varies in length depending on the tag, and multiple tagged data items can be included in any order within the data element. Use of subtags Some tags use subtags to identify the various data fields involved in the file action. Refer to the specific tag documentation for descriptions of the supported subtags and their purposes. Subtag data is structured as follows: the subtag identifying the type of field data, followed immediately by a threedigit length (LLL) identifying the length of the field data, followed immediately by the field data itself. Subtag + LLL + field data. Multiple subtags can be present within a single tag, and can be in any order within the tag. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 475 Data element definitions S-127: Tag 01, Statement Print Data Format: AN ..9999 TDEs: Statement Print Tag 01 contains statement print data. Tag 14 of P-62 is present in a message received from the host when more statement print data exists. Note: The statement print buffer must be in the format agreed to by both the issuer and acquirer. Binary data should not be passed (only character data). Consider the amount of data the acquirer can support when formatting this data. If too much data is sent, the data will be truncated by the acquirer. This tag applies to a message type of 1110. Statement print control characters The following table describes the statement print control characters that can be embedded by the host in statement print data to control the format and content of the data. These control characters are recognized and acted upon by the BASE24‑eps ATM device handlers prior to sending the statement print data to the ATM. Control characters Description <B> </B> Beginning and ending tags bracketing text that is to be printed in bold format. The device handler replaces these tags with the corresponding start and stop escape sequences for printing bold characters. <D> </D> Beginning and ending tags bracketing text that is to be printed in double-width character format. The device handler replaces these tags with the corresponding start and stop escape sequences for printing double-width characters. <I> </I> Beginning and ending tags bracketing text that is to be printed in italic format. The device handler replaces these tags with the corresponding start and stop escape sequences for printing italic characters. <U> </U> Beginning and ending tags bracketing text that is to be printed in underlined format. The device handler replaces these tags with the corresponding start and stop escape sequences for printing underlined characters. <BR> Specifies the insertion of a line break. The device handler replaces this tag with a line break sequence. <FF> Specifies the insertion of a form feed. The device handler replaces this tag with a form feed sequence. <HT> Specifies the insertion of a horizontal tab. The device handler replaces this tag with a tab sequence. <R nn> <S n> Specifies the insertion of replacement text. The text used to replace the <R nn> tag is taken from those entries in the ATM Consumer Media data source with the following key formats:stmt_prnt_txt_nnThe device handler uses the nn provided in the <R > tag to locate a matching entry in the ATM Consumer Media data source. For example, <R 12> would match stmt_prnt_txt_12. The device handler then replaces the <R > tag with corresponding text from the identified ATM Consumer Media data source entry. Specifies the insertion of n spaces, where n can be a hexadecimal value of 2 through F, representing from 2 to 15 spaces respectively. The device handler replaces this tag with the corresponding number of spaces. The <S > tag is used for space compression. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 476 Data element definitions Mini-statement print data Mini-statement print data provided by hosts for printing at an ATM must contain the proper number of spaces in each line to allow for proper alignment when printed at the ATM. The data must also contain embedded line feed characters to indicate the location of line breaks. The required line feed characters are 0x0A (hexadecimal A). The following is an example of mini-statement print data including the line breaks: <mini stmt line 1>0x0A<mini stmt line 2>0x0A<mini stmt line 3> Printed, the mini-statement data would appear as follows: <mini stmt line 1> <mini stmt line 2> <mini stmt line 3> S-127: Tag 02, Open Account – From Format: AN ..5051 TDEs: OAR Tag 02 contains the accounts associated with the from side of a transaction. The Action Code (P-39) data element must be set to a value of 083 (Approved, OAR) to indicate that multiple accounts are being returned in the response so the acquirer handles the transaction correctly. Consider the amount of data the acquirer can support when formatting this data. If too much data is sent, the data will be truncated by the acquirer. Tag 14 of P-62 is present in a message received from the host when more account data exists. The data carried in this tag is formatted as follows: Tag 02: Open Account – From Position 1–2 Description Number of Accounts Length 2 The number of from accounts carried in this tag. 3–5051 1–2 The following four fields occur 1 to 99 times. Each occurrence contains 51 characters. Account Type 2 A code indicating the type of from account. 3–22 Account Descriptor 20 A free-form text description of the account. 23 Primary or Secondary Flag 1 A flag indicating whether this is a primary or secondary account. Valid values are as follows: 1 = Primary 2 = Secondary BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 477 Data element definitions Tag 02: Open Account – From Position Description 24–51 Length Account Number 28 The account number of the from account. S-127: Tag 03, Open Account – To Format: AN ..5051 TDEs: OAR Tag 03 contains the accounts associated with the to side of a transaction. The Action Code (P-39) data element must be set to a value of 083 (Approved, OAR) to indicate that multiple accounts are being returned in the response so the acquirer handles the transaction correctly. Consider the amount of data the acquirer can support when formatting this data. If too much data is sent, the data will be truncated by the acquirer. Tag 14 of P-62 is present in a message received from the host when more account data exists. The data carried in this tag is formatted as follows: Tag 03: Open Account – To Position 1–2 Description Number of Accounts Length 2 The number of to accounts carried in this tag. 3–5051 1–2 The following four fields occur 1 to 99 times. Each occurrence contains 51 characters. Account Type 2 A code indicating the type of to account. 3–22 Account Descriptor 20 A free-form text description of the account. 23 Primary or Secondary Flag 1 A flag indicating whether this is a primary or secondary account. Valid values are as follows: 1 = Primary 2 = Secondary 24–51 Account Number 28 The account number of the to account. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 478 Data element definitions S-127: Tag 04, Fleet Card Data Format: AN 200 TDEs: Fleet Data Tag 04 contains fleet card data, as described below. Tag 04: Fleet Card Data Position 1–17 Description Customer Reference Indicator Number Length 17 The customer identification number. 18–34 Driver ID Number 17 The driver’s license number. 35–36 Fuel Product Code/Fuel Type 2 A two-digit code indicating the type of fuel purchased. Valid values are 00 through 99. 37–48 Gross Fuel Price 12 The gross fuel price. Two decimal places are implied. 49 Unit of Measure 1 A code indicating the unit of measure. 50–56 Odometer Reading 7 The odometer reading at the time of purchase. 57–68 Product Code 1 12 The product code of the item sold. 69–80 Product Code 2 12 The product code of the item sold. 81–92 Product Code 3 12 The product code of the item sold. 93–104 Product Code 4 12 The product code of the item sold. 105–116 Product Code 5 12 The product code of the item sold. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 479 Data element definitions Tag 04: Fleet Card Data Position Description 117–128 Length Product Code 6 12 The product code of the item sold. 129–140 Product Code 7 12 The product code of the item sold. 141–152 Product Code 8 12 The product code of the item sold. 153–158 Quantity 6 The quantity of fuel purchased. Two decimal places are implied. 159 Service Type 1 The type of service. Valid values are as follows: 1 = Self service 2 = Full service 160–171 Tax Amount 12 The tax amount. Four decimal places are implied. 172–183 Unit Cost 12 The unit cost. Four decimal places are implied. 184–200 Vehicle Number 17 The vehicle number. S-127: Tag 05, Fleet Product Codes Format: AN 656 TDEs: Fleet Product Codes (tde.flt_prod_cdes_descr, tde.flt_prod_cdes_dr_cr_ind, tde.flt_prod_cdes_disc_amt, tde.flt_prod_cdes_disc_ind, tde.flt_prod_cdes_meas_unit, tde.flt_prod_cdes_net_gr_ind, tde.flt_prod_cdes_qty, tde.flt_prod_cdes_tot_nf_pr, tde.flt_prod_cdes_vat_amt, tde.flt_prod_cdes_vat_rate, tde.flt_prod_cdes_vat_typ) Tag 05 contains fleet product codes, as described below. Tag 05: Fleet Product Codes Position 1–656 Description Length The following fields occur eight times. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 480 Data element definitions Tag 05: Fleet Product Codes Position 1–35 Description Description Length 35 The description of the purchased item. 36 A code indicating whether the extended amount is a debit or a credit. Valid values are as follows: 1 C = Credit D = Debit 37–45 Discount Amount 9 The amount of the discount applied to the purchase amount. 46 Discount Indicator 1 A flag indicating whether a discount was applied to the purchase amount. Valid values are as follows: Y = Yes, a discount was applied to the purchase amount. N = No, a discount was not applied to the purchase amount. 47–49 Unit of Measure 3 A code indicating the unit of measure. 50 Net Gross Indicator 1 A flag indicating whether the amount includes a tax. Valid values are as follows: Y = Yes, a tax is included in the amount. N = No, a tax is not included in the amount. 51–55 Quantity 5 The number of items purchased. 56–64 Total Nonfuel 9 The total nonfuel price. Two decimal places are implied. 65–73 VAT Tax Amount 9 The amount of the value-added tax. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 481 Data element definitions Tag 05: Fleet Product Codes Position Description 74–78 Length VAT Tax Rate 5 The value-added tax rate. Five decimal places are implied. 79–82 VAT Tax Type 4 The type of value-added tax. S-127: Tag 06, Fleet Tax Data Format: AN 161 TDEs: Fleet Tax (tde.fleet_tax_stat, tde.fleet_tax_rate, tde.fleet_vat_rate) Tag 06 contains Fleet Tax data, as described below. Tag 06: Fleet Tax Data Position 1–5 Description VAT Tax Rate Length 5 The value-added tax rate. Five decimal places are implied. 6 Miscellaneous Fuel Tax Exemption Status 1 The miscellaneous fuel tax exemption status. Valid values are as follows: 0 = Nonexempt 1 = Exempt 7–18 Miscellaneous Fuel Tax 12 The miscellaneous fuel tax amount. Four decimal places are implied. 19 Miscellaneous Nonfuel Tax Exemption Status 1 The miscellaneous nonfuel tax exemption status. Valid values are as follows: 0 = Nonexempt 1 = Exempt 20–31 Miscellaneous Nonfuel Tax 12 The miscellaneous nonfuel tax amount. Two decimal places are implied. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 482 Data element definitions Tag 06: Fleet Tax Data Position 32 Description Federal Excise Tax Exemption Status - Non Fuel Length 1 The federal excise tax exemption status for nonfuel products. Valid values are as follows: 0 = Nonexempt 1 = Exempt 33–44 Federal Excise Tax - Non Fuel 12 The federal excise tax amount for nonfuel products. Two decimal places are implied. 45 Federal Excise Tax Exemption Status - Fuel 1 The federal excise tax exemption status for fuel. Valid values are as follows: 0 = Nonexempt 1 = Exempt 46–57 Federal Excise Tax - Fuel 12 The federal excise tax amount for fuel products. Two decimal places are implied. 58 State Motor Fuel Tax Exemption Status 1 The state motor fuel tax exemption status. Valid values are as follows: 0 = Nonexempt 1 = Exempt 59–70 State Motor Fuel Tax 12 The state motor fuel tax amount. Two decimal places are implied. 71 County Fuel Sales Tax Exemption Status 1 The county fuel sales tax exemption status. Valid values are as follows: 0 = Nonexempt 1 = Exempt BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 483 Data element definitions Tag 06: Fleet Tax Data Position 72–83 Description County Fuel Sales Tax Length 12 The county fuel tax amount. Two decimal places are implied. 84 Non-Fuel State and Local Sales Tax Exemption Status 1 The nonfuel state and local sales tax exemption status. Valid values are as follows: 0 = Nonexempt 1 = Exempt 85–96 Non-Fuel State and Local Sales Tax 12 The nonfuel state and local tax amount. Two decimal places are implied. 97 County Motor Fuel Tax Exemption Status 1 The county motor fuel tax exemption status. Valid values are as follows: 0 = Nonexempt 1 = Exempt 98–109 County Motor Fuel Tax 12 The county motor fuel tax amount. Two decimal places are implied. 110 City Sales Fuel Tax Exemption Status 1 The city fuel tax exemption status. Valid values are as follows: 0 = Nonexempt 1 = Exempt 111–122 City Sales Fuel Tax 12 The city fuel tax amount. Two decimal places are implied. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 484 Data element definitions Tag 06: Fleet Tax Data Position Description 123 Length City Motor Fuel Tax Exemption Status 1 The city motor fuel tax exemption status. Valid values are as follows: 0 = Nonexempt 1 = Exempt 124–135 City Motor Fuel Tax 12 The city motor fuel tax amount. Two decimal places are implied. 136 Secondary State Fuel Tax Exemption Status 1 The secondary state fuel tax exemption status. Valid values are as follows: 0 = Nonexempt 1 = Exempt 137–148 Secondary State Fuel Tax 12 The secondary state fuel tax amount. Two decimal places are implied. 149 Federal Sales Tax Exemption Status 1 The federal sales tax exemption status. Valid values are as follows: 0 = Nonexempt 1 = Exempt 150–161 Federal Sales Tax 12 The federal sales tax amount. Two decimal places are implied. S-127: Tag 07, MasterCard Fleet Data Format: AN 29 TDEs: MasterCard Fleet Data (tde.fleetm_cust_ref_ind, tde.fleetm_drvr_id_num, tde.fleetm_fuel_typ, tde.fleetm_gross_fuel_price, tde.fleetm_meas_unit, tde.fleetm_odo_rdng, tde.fleetm_fleet_prod_cde, tde.fleetm_fleet_data_qty, tde.fleetm_svce_typ, tde.fleetm_tax_amt , tde.fleetm_unit_cost, tde.fleetm_veh_num, tde.alt_tax_id, tde.mcrd_fleet_brand_cde, tde.mcrd_fleet_dec_rsn_cde, tde.non_fuel_itm_cnt, tde.mcrd_fleet_prod_typ, tde.tax_exempt_amt) BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 485 Data element definitions Tag 07 contains MasterCard Fleet Data, as described below. Tag 07: MasterCard Fleet Data Position Description 1–15 Alternate Tax ID Length 15 A code identifying an alternate tax. 16–19 Brand Code 4 The oil company brand code. 20–21 Decline Reason Code 2 A code indicating the reason the transaction was denied. Valid values are as follows: 01 = Invalid ID number 02 = Invalid drivers license number 03 = Invalid vehicle identification number 22–23 Number of Non-Fuel Items 2 The number of nonfuel items included in the purchase. 24 Product Type 1 A code read from the card track indicating which prompts occur at the POS device. Valid values are as follows: 1 = Prompt for ID number (drivers license number) and odometer reading. 2 = Prompt for vehicle identification number and odometer reading. 3 = Prompt for user-defined driver number and odometer reading. 4 = Prompt for odometer reading only. 5 = No prompt. 25–29 Tax Exemption Amount 5 The tax amount for tax exempt fleets. S-127: Tag 08, Visa Fleet Data Format: AN 37 BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 486 Data element definitions TDEs: Visa Fleet Data (tde.fleetv_cust_ref_ind, tde.fleetv_drvr_id_num, tde.fleetv_fuel_typ, tde.fleetv_gross_fuel_price, tde.fleetv_meas_unit, tde.fleetv_odo_rdng, tde.fleetv_fleet_prod_cde, tde.fleetv_fleet_data_qty, tde.fleetv_svce_typ, tde.fleetv_tax_amt, tde.fleetv_unit_cost, tde.fleetv_veh_num, tde.visa_fleet_data_tag, tde.gross_non_fuel_price, tde.net_non_fuel_price, tde.net_fuel_price, tde.visa_fleet_prod_typ) Tag 08 contains Visa fleet data, as described below. Tag 08: Visa Fleet Data Position Description 1–12 Length Gross Non Fuel Price 12 The gross nonfuel price. 13–24 Net Fuel Price 12 The net fuel price. Four decimal places are implied. 25–36 Net Non-Fuel Price 12 The net nonfuel price. Two decimal places are implied. 37 Purchase Type 1 A code indicating the type of merchandise purchased. Valid values are as follows: 1 = Fuel purchase 2 = Nonfuel purchase 3 = Fuel and nonfuel purchase S-127: Tag 10, Card Data Source Updates and Inquiries Format: Variable based on the subtags included TDEs: Data Record Tag 10 contains fields in the Card, Card Account, and Card Account Multibyte data sources to be updated or inquired on in a file action request message sent from the ISO 93 host to the BASE24‑eps system. All fields carried in this tag are identified by a set of subtags that is common to both this tag and data element S-72 tag 01. In file action request messages, subtag data can be carried in S-72 tag 01 or S-127 tag 10, or both. For information about the subtag data that can be included in this tag, refer to data element S-72 tag 01. For inquiry responses, all Card, Card Account, and Card Account Multibyte data source information is carried, as subtag data, in this tag, and in all cases, data will only be returned in a subtag if there is data in the corresponding data source field. S-127: Tag 11, Card Data Source CSM Buffer Format: Variable based on the subtags included BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 487 Data element definitions TDEs: Card CSM Buffer Tag 11 contains the CSM buffer in the Card data source (Card) to be updated or inquired on in a file action request message sent from the ISO 93 host to the BASE24‑eps system. For any type of file action request, the Card CSM buffer can be placed in S-72 tag 01, S-127 tag 10, or S-127 tag 11, but not in more than one of those locations. For inquiry requests, the Card CSM buffer can be carried in S-127 tag 11 only if there is at least one other subtag being carried in S-72 tag 01 or S-127 tag 10. For inquiry responses, the Card CSM buffer is always returned as subtag 19 in S-127 tag 10. For information on the content and structure of the Card CSM buffer, refer to subtag 19, under the S-72, tag 01 data element description. S-127: Tag 12, Positive Balance Data Source CSM Buffer Format: Variable based on the subtags included TDEs: PBAL CSM Buffer Tag 12 contains the CSM buffer in the Positive Balance data source (PBAL) to be updated in a file action request message sent from the ISO 93 host to the BASE24‑eps system. The Positive Balance CSM buffer can be placed in S-72 tag 02 or S-127 tag 12, but not in both. For information on the content and structure of the Positive Balance CSM buffer, refer to subtag 10, under the S-72, tag 02 data element description. S-127: Tag 13, Visa Fleet Additional Data Format: AN 65 TDEs: VISA Fleet Additional Data (tde.fleetv_adnl_data_ind, tde.fleetv_cust_vat_rgrst_num, tde.fleetv_mrch_vat_rgrst_num, tde.fleetv_msg_id, tde.fleetv_other_tax, tde.fleetv_sum_cmmdty_cde) Tag 13 contains Visa fleet data, as described below. Tag 13: Visa Fleet Additional Data Position 1–12 Description Other Tax Format N 12 The other tax amount.This field is mapped from DE 104, dataset ID 5C, tag 17 (Other Tax) of the VisaNet SMS message. 13–32 Merchant VAT Registration Number AN 20 The merchant VAT registration or single business reference number.This field is mapped from DE 104, dataset ID 5C, tag 18 (Merchant VAT Registration/Single Business Reference Number) of the VisaNet SMS message. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 488 Data element definitions Tag 13: Visa Fleet Additional Data Position Description 33–45 Customer VAT Registration Number Format AN 13 This field is mapped from DE 104, dataset ID 5C, tag 19 (Customer VAT Registration Number) of the VisaNet SMS message. 46–60 Message ID AN 15 An identifier that is used to link the separate line item detail messages.This field is mapped from DE 104, dataset ID 5C, tag 1B (Message Identifier) of the VisaNet SMS message. 61 Additional Data Indicator. AN 1 Y = Additional data is provided separately in Draft Data TC 50 N = Additional data is not providedThis field is mapped from DE 104, dataset ID 5C, tag 1C (Additional Data Indicator) of the VisaNet SMS message. 62–65 Summary Commodity Code N4 This field is mapped from DE 104, dataset ID 5C, tag 1E (Summary Commodity Code) of the VisaNet SMS message. S-127: Tag 14, Check Status Inquiry Response Data Format: Variable based on the subtags included TDEs: Data Record Tag 14 contains response data for Check Status data source inquiries initiated using a file action request message sent from the ISO 93 host to the BASE24‑eps system. All fields carried in this tag are identified by a set of subtags that is common to both this tag and data element S-72 tag 26. In file action request messages, subtag data can be carried in S-72 tag 26 only. For inquiry responses, all Check Status data source information is carried, as subtag data, in data element S-127 tag 14. In all cases, inquiry response data is only returned in a subtag if there is data in the corresponding data source field. For information about the subtag data that can be included in this tag, refer to data element S-72 tag 26. S-127: Tag 15, Stop Payment Inquiry Response Data Format: Variable based on the subtags included TDEs: Data Record BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 489 Data element definitions Tag 15 contains response data for Stop Payment data source inquiries initiated using a file action request message sent from the ISO 93 host to the BASE24‑eps system. All fields carried in this tag are identified by a set of subtags that is common to both this tag and data element S-72 tag 27. In file action request messages, subtag data can be carried in S-72 tag 27 only. For inquiry responses, all Check Status data source information is carried, as subtag data, in data element S-127 tag 15. In all cases, inquiry response data is only returned in a subtag if there is data in the corresponding data source field. For information about the subtag data that can be included in this tag, refer to data element S-72 tag 27. S-127: Tag 16, Context Cookie Data Format: AN ..99 TDEs: Context Cookie Tag 16 contains a context cookie that is generated by BASE24-eps when multiple records exist for a partial key file update inquiry of the Stop Payment data source. In this case, the cookie will contain the primary key data of the current record read. This cookie data is sent back to the host in the file update inquiry response message and should be echoed back in the next file update inquiry request message to inquire on the next Stop Payment record. The cookie data enables the system to locate the next record to return. If this tag is not included, additional records are not available. This tag can contain up to 99 alphanumeric characters. The context cookie for Stop Payment file update inquiries is 72 characters, formatted as follows: Tag 16: Stop Payment Inquiry Context Cookie Format Position Content Format 1–20 Institution ID AN 20 21–48 Account Number AN 28 49–50 Account Type 51–61 High Check Number AN 11 61–72 Low Check Number AN 11 AN 2 S-127: Tag 17, CARDNET Data Format: Variable based on the subtags included TDEs: Japanese Data TDE Tag 17: CARDNET Data Subtag Description Format 01 Merchant Contract Company Code 02 Acquirer Category AN 2 03 Japanese Data Product Code AN 4 04 Merchant Company Code 05 Merchant Terminal Number BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 AN 11 AN 11 AN 8 490 Data element definitions Tag 17: CARDNET Data Subtag Description Format 06 Merchant Number AN 15 07 Domestic Response Code 08 Authorization on Country ID 09 Terminal Output Data AN 147 10 Domestic Use AN 121 11 Japanese Data Extended Usage AN 124 12 Japanese Data Transaction Code AN 4 13 Japanese Data Usage Field AN 2 14 Transaction Serial Number AN 12 AN 5 AN 11 S-127: Tag 18, CARDNET Payment Data Format: Variable based on the subtags included TDEs: Payment TDE Tag 18: CARNET Payment Data Subtag Description Format 10 Lump-sum payment AN 82 15 Acquirer Bank Code AN 4 16 Acquirer Branch Office code AN 4 17 Transaction Category AN 1 21 Lump-sum payment after receiving bonus AN 82 22 Payment afer receiving bonus (frequency specified) AN 82 23 Payment after receiving bonus (month specified) AN 82 24 Payment after receiving bonus (multiple months specified) AN 82 25 Payment after receiving bonus (multiple months specified, amounts specified) AN 82 31 Increased payment made after receiving bonus (start month, frequency specified) AN 82 32 Increased payment made after receiving bonus (start month, frequency, bonus amount specified) AN 82 BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 491 Data element definitions Tag 18: CARNET Payment Data Subtag Description Format 33 Increased payment made after receiving bonus (start month, multiple months specified) AN 82 34 Increased payment made after receiving bonus (start month, frequency, multiple months, amount specified) AN 82 61 Installment (start month, frequency specified) AN 82 62 Installment (start month, frequency, amount specified) AN 82 63 Installment (start month, frequency, initial amount specified) AN 82 69 Second installment (start month, frequency specified) AN 82 80 Revolving AN 82 S-127: Tag 19, Cancellation/Return Category Format: AN 1 TDEs: Payment TDE Tag 19 carries payment cancellation/return category data. S-127: Tag 20, JIS2 Track Format: AN 69 TDEs: JIS2 Track TDE Tag 20 carries JIS2 Track data. S-127: Tag 21, Visa Fleet Data for Commercial Card Data Format: AN 72 TDEs: Visa Fleet Data Tag 21 carries fleet data submitted by fuel merchants in Visa fleet card transactions. VisaNet: The data in this tag maps to and from data element 104, usage 2 (Transaction-Specific Data), dataset 5C (Commercial Card Data) in the VisaNet transaction message. For information about the VisaNet transaction message, refer to the appropriate VisaNet technical specifications. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 492 Data element definitions Tag 21: Visa Fleet Data for Commercial Card Data Position Description Format 1-4 Fuel brand. Corresponds to the VisaNet tag 1F09 ((Fuel brand). AN 4 5-9 Fuel transaction validation results. Corresponds to the VisaNet tag 1F0A (Fuel transaction validation results). AN 5 10 Fuel acceptance mode. Corresponds to the VisaNet tag 1F0B (Fuel acceptance mode). AN 1 11-30 Driver ID. Corresponds to the VisaNet tag 1F0C (Driver ID). AN 20 31-40 Job Number. Corresponds to the VisaNet tag 1F0D (Job number). AN 10 41-48 Fleet Number. Corresponds to the VisaNet tag 1F0E (Fleet number). 49-62 Vehicle Register Number. Corresponds to the VisaNet tag 1F0F (Vehicle register number). 63-68 Product Qualifier. Corresponds to the VisaNet tag 1F10 (Product Qualifier). AN 6 69-72 Expanded Fuel Type. Corresponds to the VisaNet tag 1F11 (Expanded Fuel Type). AN 4 AN 8 AN 14 S-127: Tag 22, Visa Fleet Data for Expanded Non-Fuel Format: AN..280 TDEs: Visa Fleet Data Tag 22 carries additional fleet data submitted by fuel merchants in Visa fleet card transactions. VisaNet: The data in this tag maps to and from data element 125, usage 2 dataset ID 6B (Expanded Fleet Service) in the VisaNet transaction message. For information about the VisaNet transaction message, refer to the appropriate VisaNet technical specifications. Tag 22: Visa Fleet Data for Expanded Non-Fuel Subtag Description 01 Expanded NonFuel Product Code 1. Corresponds to the VisaNet tag 01 (Expanded Non-Fuel Product Code 1) . BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 Format AN 4 493 Data element definitions Tag 22: Visa Fleet Data for Expanded Non-Fuel Subtag Description 02 Expanded Non-Fuel Product Code 1 Quantity. Corresponds to the VisaNet tag 02 (Expanded Non-Fuel Product Code 1 Quantity) N4 03 Expanded Non-Fuel Product Code 1 Unit Cost. Corresponds to the VisaNet tag 03 (Expanded Non-Fuel Product Code 1 Unit Cost). N 12 04 Expanded NonFuel Product Code 2. Corresponds to the VisaNet tag 04 (Expanded Non-Fuel Product Code 2) . AN 4 05 Expanded Non-Fuel Product Code 2 Quantity. Corresponds to the VisaNet tag 05 (Expanded Non-Fuel Product Code 2 Quantity) N4 06 Expanded Non-Fuel Product Code 2 Unit Cost. Corresponds to the VisaNet tag 06 (Expanded Non-Fuel Product Code 2 Unit Cost). N 12 07 Expanded NonFuel Product Code 3. Corresponds to the VisaNet tag 07 (Expanded Non-Fuel Product Code 3) . AN 4 08 Expanded Non-Fuel Product Code 3 Quantity. Corresponds to the VisaNet tag 08 (Expanded Non-Fuel Product Code 3 Quantity) N4 09 Expanded Non-Fuel Product Code 3Unit Cost. Corresponds to the VisaNet tag 09 (Expanded Non-Fuel Product Code 3 Unit Cost). N 12 10 Expanded NonFuel Product Code 4. Corresponds to the VisaNet tag 0A (Expanded Non-Fuel Product Code 4) . AN 4 11 Expanded Non-Fuel Product Code 4 Quantity. Corresponds to the VisaNet tag 0B (Expanded NonFuel Product Code 4 Quantity) N4 12 Expanded Non-Fuel Product Code 4 Unit Cost. Corresponds to the VisaNet tag 0C (Expanded NonFuel Product Code 4Unit Cost). N 12 BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 Format 494 Data element definitions Tag 22: Visa Fleet Data for Expanded Non-Fuel Subtag Description 13 Expanded NonFuel Product Code 5. Corresponds to the VisaNet tag 0D (Expanded Non-Fuel Product Code 5) . 14 Expanded Non-Fuel Product Code 5 Quantity. Corresponds to the VisaNet tag 0E (Expanded NonFuel Product Code 5 Quantity) 15 Expanded Non-Fuel Product Code 5 Unit Cost. Corresponds to the VisaNet tag 0F (Expanded Non-Fuel Product Code 5 Unit Cost). N 12 16 Expanded NonFuel Product Code 6. Corresponds to the VisaNet tag 10 (Expanded Non-Fuel Product Code 6) . AN 4 17 Expanded Non-Fuel Product Code 6 Quantity. Corresponds to the VisaNet tag 11 (Expanded Non-Fuel Product Code 6 Quantity) N4 18 Expanded Non-Fuel Product Code 6 Unit Cost. Corresponds to the VisaNet tag 12 (Expanded Non-Fuel Product Code 6 Unit Cost). N 12 19 Expanded NonFuel Product Code 7. Corresponds to the VisaNet tag 13 (Expanded Non-Fuel Product Code 7) . AN 4 20 Expanded Non-Fuel Product Code 7 Quantity. Corresponds to the VisaNet tag 14 (Expanded Non-Fuel Product Code 7 Quantity) N4 21 Expanded Non-Fuel Product Code 7 Unit Cost. Corresponds to the VisaNet tag 15 (Expanded Non-Fuel Product Code 7 Unit Cost). N 12 22 Expanded NonFuel Product Code 8. Corresponds to the VisaNet tag 16 (Expanded Non-Fuel Product Code 8) . AN 4 23 Expanded Non-Fuel Product Code 8 Quantity. Corresponds to the VisaNet tag 17 (Expanded Non-Fuel Product Code 8 Quantity) N4 BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 Format AN 4 N4 495 Data element definitions Tag 22: Visa Fleet Data for Expanded Non-Fuel Subtag Description 24 Expanded Non-Fuel Product Code 8 Unit Cost. Corresponds to the VisaNet tag 18 (Expanded Non-Fuel Product Code 8 Unit Cost). Format N 12 S-127: Tag 24, CBAE Additional Response Data Format: ANS Variable based on the subtags included TDEs: ERSB Additional Response Data TDE Tag 24 contains the Additional Response Data as specified by the tags in field 44 of the CBAE protocol. Only the field 44 tags applicable to the current CBAE message, which are not supported via existing ISO 8583:1993 Host Interface fields, should be present (see table below). Tag 24 has a TLV (Tag Length Value) structure as follows: • • Subtag: AN 2 Subtag Length: N 3 Note: Subtags AA, AC and AE are repeatable and can occur multiple times within tag 24. Tag 24: CBAE Additional Response Data Subtag Description Format AA Incorrect field ANS 4, 6 or 8 AC Field conversion ANS ..21 AD Reason for declining or approving the transaction ANS 2..5 AE Additional Service(s) Report sent to the acquirer by the network BA Maximum amount for which an authorization can be delivered ANS ..12 BB Telephone number ANS ..21 BD Network equipment identifier BF Minimum amount for which an authorization can be delivered ANS 2..20 ANS 2 ANS ..12 S-127: Tag 25, CBAE Additional National Data Format: ANS Variable based on the subtags included TDEs: ERSB Additional Data TDE BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 496 Data element definitions Tag 25 contains the Additional National Data as specified by the tags in field 47 of the CBAE protocol. Only the tags applicable to the current CBAE message, which are not supported via existing ISO 8583:1993 Host Interface fields, should be present (see table below). Tag 25 has a TLV (Tag Length Value) structure as follows: • • Subtag: AN 2 Subtag Length: N 3 Tag 25: CBAE Additional National Data Subtag Description Format 08 Site type ANS ..8 95 Network data AN ..50 96 SIRET N 14 S-127: Tag 26, CBAE National Data Format: ANS Variable based on the subtags included TDEs: ERSB Additional Data TDE E-Commerce Cardholder Authentication Information TDE Tag 26 contains the National Data as specified by the tags in field 59 of the CBAE protocol. Only the tags applicable to the current CBAE message, which are not supported via existing ISO 8583:1993 Host Interface fields, should be present (see table below). Tag 26 has a TLV (Tag Length Value) structure as follows: • • Subtag: AN 4 (0000-FFFF) Subtag Length: N 3 Note: Subtags 0101 and 0802 are repeatable and can occur multiple times within Tag 26. Tag 26: CBAE National Data Subtag Description Format 0100 Function Code N3 0101 Message Reason Code N4 0102 Year of transaction N2 0200 Transaction Regulatory and Technical Environment (RTE) AN 2 0201 Terminal Application Identifier (TAI) N 12 0202 Acceptor Contract Number / Merchant Identifier N7 0203 Acceptance System Logical Number N3 0204 Point of Acceptance Logical Number N3 BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 497 Data element definitions Tag 26: CBAE National Data Subtag Description Format 0205 Terminal Country Code N3 0207 Cardholder Total Amount 0210 Customer Reference 1 ANS ..22 0211 Customer Reference 2 ANS ..22 0212 Contract Number ANS ..22 0213 VAT amount 0300 Visual Cryptogram Authentication (Subfield 3 of Visual Cryptogram Structure) N1 0301 Visual Cryptogram Processing Information - Response Origin (Subfield 1) N1 0302 Dynamic Virtual Card (CVD) Number N ..19 0303 Dynamic Virtual Card (CVD) Expiration Date N4 0410 Cardholder authentication method used by the issuer 0412 Result of use of secure remote payment architecture AN 8 0413 Modified transaction security mode AN 2 0705 Final authorization indicator presence information (Subfield 1) AN 1 0708 Advice reason code N7 0800 Invoice / Procedure type N1 0802 Risk scoring service 0803 International authorization network identifier 0804 Network rerouting reason N2 0807 Issuer Country Code N3 0808 Message source N 12 N 12 ANS 2 AN ..48 AN 1 AN 1 S-127: Tag 27, CBAE Funds Transfer Data Format: ANS Variable based on the subtags included TDEs: Funds Transfer Data TDE BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 498 Data element definitions Tag 27 contains the Funds Transfer Data as specified by the tags in field 112 of the CBAE protocol only when tag 01 subfield 1 (Nomenclature) is set to 3 (CB). Only the tags applicable to the current CBAE message, which are not supported via existing ISO 8583:1993 Host Interface fields, should be present (see table below). Tag 27 has a TLV (Tag Length Value) structure as follows: • • Subtag: AN 2 Subtag Length: N 3 Tag 27: CBAE Funds Transfer Data Subtag Description Format 01 Sender Identification Data ANS 2..99 02 Additional Data - Transaction ANS 2..99 03 Identifier of the type of application that was the origin of the funds transfer transaction AN 2 S-127: Tag 29, Italian Security Information Format: Variable based on subtags included TDEs: Italian Security Info TDE Tag 29 contains Italian Security Information as specified by tags in field 53 of the ABI Full protocol. Tag 29 has a Tag Length Value (TLV) structure as follows: • • Subtag: N2 Subtag length: N3 Tag 29: Italian Security Information Subtag Description Format 01 PIN Encryption Type N1 02 Dynamic Key AN..32 03 Card PIN Key DES AN 16 04 Random Number 05 Card PIN Key TDES N6 AN 32 S-127: Tag 30, Italian Identifier Format: Variable based on subtags included TDEs: Italian Security Info TDE Tag 30 contains Italian Identifier which specifies if the transaction is Italian domestic. Tag 30 has a Tag Length Value (TLV) structure as follows: • • Subtag: N2 Subtag length: N3 BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 499 Data element definitions Tag 30: Italian Identifier Subtag Description 01 Format Italian Identifier N1 S-128: Secondary Message Authentication Code Format: AN 16 TDEs: Not applicable The Secondary Message Authentication Code data element carries the message authentication code (MAC) for the message, subject to the following conditions: • • • Message authentication has been configured for the interface on the ISO8583 (93) Host Interface Configuration window. This data element is specified as conditional in the ISO message profile for the interface. At least one other secondary data element (S-65 through S-128) is included in the message. If message authentication has been configured and the message does not contain at least one other secondary data element, the MAC is placed in data element P-64. BASE24-eps® Release Version Independent ISO 8583:1993 Host External Message Specification - May 17, 2019 500
