1、 ASC X9, Inc. 2004 All rights reserved American National Standard for Financial Services X9.104-1:2004 Financial transaction card originated messages Card acceptor to acquiring host messages Part 1: Messages, data elements and code values Accredited Standards Committee X9, Incorporated Financial Ind
2、ustry Standards Date Approved: September 14, 2004 American National Standards Institute ANS X9.104-1:2004 ii ASC X9, Inc. 2004 All rights reservedContents Page Foreword.viii Introduction .x 1 Scope 1 2 Normative references 1 3 Terms and definitions .2 4 Symbols and abbreviated terms 3 5 Environment.
3、3 5.1 General3 5.2 Transaction processing and transaction flow 4 5.3 Administrative processing5 5.4 Multiple currency processing.6 5.5 Message processing .6 5.5.1 Communications infrastructure .6 5.5.2 Message parsing7 5.5.3 Message repeats7 5.6 Message processing rules7 5.6.1 Host control mode .7 5
4、.6.2 Terminal control mode 7 5.6.3 Hybrid control mode8 5.7 Data element structure8 5.7.1 Data element types 8 5.7.2 Primitive data elements.8 5.7.3 Constructed data element.8 5.7.4 Composite data elements .9 6 Data elements 11 6.1 General requirements for data elements 11 6.2 Data element represent
5、ation . 14 6.3 Data elements with pre-defined values 14 6.4 Specific requirements for ISO 8583 data elements. 14 6.4.1 Additional data private (message control data) (bit 48) 14 6.4.2 Verification data (bit 49) . 16 6.4.3 Data record (bit 72) . 17 6.4.4 Account identification 1 (bit 102) 18 6.4.5 Ac
6、count identification 2 (bit 103) 18 6.4.6 Electronic commerce data (bit 34) 18 6.5 Specific requirements for national use data elements . 18 6.5.1 Account bar code data (bit 60) 18 6.6 Specific requirements for private use data elements . 18 6.6.1 Product data (bit 63) . 18 6.6.2 Proprietary reconci
7、liation totals (bit 123). 19 ANS X9.104-1:2004 ASC X9, Inc. 2004 All rights reserved iii6.7 Cardholder account identification.19 6.8 Card acceptor identification.20 6.9 Institution identifiers.20 7 Messages and transactions .20 7.1 Mandatory and conditional data elements .20 7.2 Message types and st
8、ructure.21 8 Message class definitions 22 8.1 General .22 8.2 Authorization message class.22 8.2.1 Authorization description.22 8.2.2 Authorization message rules .23 8.2.3 Authorization request message (100) .23 8.2.4 Authorization request response message (110) 24 8.2.5 Authorization advice (120) a
9、nd advice response (130) messages.25 8.2.6 Authorization notification (140) and notification acknowledgement (150) messages .25 8.3 Verification messages.25 8.3.1 Verification description.25 8.3.2 Verification message rules.26 8.3.3 Verification request message (104).26 8.3.4 Verification request re
10、sponse message (114)26 8.4 Financial presentment message class27 8.4.1 Financial presentment description27 8.4.2 Financial presentment message rules 27 8.4.3 Financial presentment request message (200) 27 8.4.4 Financial presentment request response message (210) .29 8.4.5 Financial presentment advi
11、ce (220) and notification (240) messages.30 8.4.6 Financial presentment advice response message (230).31 8.5 Financial accumulation presentment32 8.6 File action message class 32 8.6.1 File action rules .32 8.6.2 File action request (304) and advice (324) messages32 8.6.3 File action request respons
12、e (314) and advice response (334) messages .33 8.7 Reversal message class .33 8.7.1 Reversal message rules .34 8.7.2 Reversal advice message (420) .34 8.7.3 Reversal advice response message (430) 34 8.8 Chargeback message class .35 8.9 Reconciliation message class .35 8.9.1 Reconciliation message ru
13、les35 8.9.2 Reconciliation request (504) or advice (524) message36 8.9.3 Reconciliation request response (514) and advice response (534) message.37 8.10 Administrative message class .37 8.10.1 Administrative message rules .38 8.10.2 Administrative request (604) and advice (624) message 38 8.10.3 Adm
14、inistrative request response (614) and advice response (634) message 38 8.11 Retrieval and retrieval fulfilment39 8.12 Error messages .39 8.12.1 Error message rules39 8.12.2 Error notification (644) message .39 8.13 Fee collection message class 40 ANS X9.104-1:2004 iv ASC X9, Inc. 2004 All rights re
15、served8.14 Network management message class 40 8.14.1 Network management message rules 40 8.14.2 Network management request (804) and advice (824) messages . 40 8.14.3 Network management request response (814) and advice response (834) messages. 41 8.15 Key management 42 8.16 Batch transfer 42 8.17
16、File transfer . 42 9 Maintenance 42 Annex A (normative) Private values of data elements 43 A.1 General. 43 A.2 Private values for function code (bit 24) 43 A.3 Private values for action code (bit 39) 43 Annex B (normative) National use values of ISO 8583 data elements 44 B.1 General. 44 B.2 National
17、 values for Message reason code (bit 25) 44 B.3 National use values within Message control data (bit 48) 44 B.3.1 Result of previous attempt code. 44 B.3.2 Host connected code . 45 B.3.3 Multiple transaction response indicator 46 B.4 National tag assignments 46 Annex C (normative) Data element usage
18、 in messages.47 C.1 General. 47 Annex D (informative) Migrating from ASC-TG23 -Part 1: 1999 65 D.1 General. 65 D.2 Changes based on the update of ISO 8583 65 D.2.1 Code Values 65 D.2.2 Data elements 65 D.2.3 Messages. 67 D.2.4 New features. 68 D.3 Other differences between X9.104-1 and TG-23 68 D.3.
19、1 Code values. 68 D.3.2 Data elements 68 D.3.3 Messages. 70 D.3.4 Annexes. 70 Bibliography. 71 ANS X9.104-1:2004 ASC X9, Inc. 2004 All rights reserved vFigures Figure 1 Transaction processing components.4 Figure 2 Administrative processing components 6 Figure 3 Structure of a composite data element
20、9 Figure 4 Dataset identifiers 01-70 10 Figure 5 Dataset identifiers 71-FE10 Figure 6 Dataset bit map examples11 ANS X9.104-1:2004 vi ASC X9, Inc. 2004 All rights reservedTables Table 1 Data element directory 12 Table 2 Message control data data elements. 15 Table 3 Verification request data. 16 Tab
21、le 4 Data record datasets . 17 Table 5 POS configuration request data. 17 Table 6 POS configuration response data 17 Table 7 Data element usage classification . 21 Table 8 Allocated message types 21 Table 9 Authorization request message (100) 23 Table 10 Authorization request response message (110).
22、 24 Table 11 Verification request message (104) . 26 Table 12 Verification request response message (114) 26 Table 13 Financial presentment request message (200). 27 Table 14 Financial presentment request response message (210) . 29 Table 15 Financial presentment advice (220) and notification (240)
23、messages. 30 Table 16 Financial presentment advice response message (230) . 31 Table 17 File action request (304) and advice (324) message 32 Table 18 File action request response (314) and advice response (334) 33 Table 19 Reversal advice message (420) 34 Table 20 Reversal advice response message (
24、430). 35 Table 21 Reconciliation request (504) or advice (524) message 36 Table 22 Reconciliation request response (514) and advice response (534) message. 37 ANS X9.104-1:2004 ASC X9, Inc. 2004 All rights reserved viiTable 23 Administrative request (604) and advice (624) message .38 Table 24 Admini
25、strative request response (614) and advice response (634) message .38 Table 25 Error notification (644) message 39 Table 26 Network management request (804) and advice (824) message.40 Table 27 Network management request response (814) and advice response (834) messages.41 Table 28 Function code.43
26、Table 29 Action code private values43 Table B.1 Message reason codes 44 Table B.2 Result of previous attempt codes.44 Table B.3 Host connected codes .45 Table B.4 Multiple transaction response indicator 46 Table B.5 Assigned tag values 46 Table C.1 ISO 8583 data elements by bit map location48 Table
27、D.1 Comparison of Message control data (bit 48)68 Table D.2 Mapping of Fleet card data to TG23 bit 63 - Product code.69 ANS X9.104-1:2004 viii ASC X9, Inc. 2004 All rights reservedForeword Business practices have changed greatly with the introduction of computer-based technologies. The substitution
28、of electronic financial transactions at the point of sale for their paper-based predecessors has reduced costs and improved efficiency. These practices have had a particularly significant impact on the operation of retail businesses. Many stores are now dependent on the use of this technology in the
29、ir daily operations, which applies to credit/debit cards, various proprietary cards, including for use in specialty markets, and for emerging payment methods. This part of X9.104 provides a generic basis for the implementation of a common message exchange infrastructure at the point of sale for use
30、by various verticals within the retail community and their component business operations. Such an infrastructure provides processing efficiencies, a consistent interface with existing host-to-host messaging, and, eventually, lower implementation costs. The infrastructure also provides a high degree
31、of commonality in emerging point-of-sale systems that reduces exceptions and leads to a lesser number of chargebacks. ANSI X9.104 consists of the following parts, under the general title Financial transaction messages - Card acceptor to acquirer messages: - Part 1: Messages, data elements and code v
32、alues - Part 2: Convenience store and petroleum marketing industry Subsequent parts may be published to define card acceptor to acquirer messages for sectors within the retail industry. While the techniques specified in this part of X9.104 are designed to provide common payment system messages betwe
33、en the retail location and the acquirer processor, use of the Standard does not guarantee that a particular implementation provides interoperability. It is the responsibility of the individual implementers to put an overall process in place with the necessary controls to ensure that the process is p
34、roperly implemented. Furthermore, the controls shall include the application of appropriate audit tests in order to verify compliance with this part of X9.104. To aid clarity the following conventions are followed within this part of X9.104. Data element names have the first letter capitalized Data
35、element names are shown in italics except when used in tables or figures. Message class names are shown capitalized when the context refer to their use in messages or transactions. Approval of an American National Standard requires verification by ANSI that the requirements for due process, consensu
36、s, and other criteria for approval have been met by the standards developer. ANS X9.104-1:2004 ASC X9, Inc. 2004 All rights reserved ixConsensus is established in the judgment of the ANSI Board of Standards Review when substantial agreement has been reached by directly and materially affected intere
37、sts. Substantial agreement means much more than a simple majority, but not necessarily unanimity. Consensus requires that all views and objections be considered, and that a concerted effort be made toward their resolution. The use of American National Standards is completely voluntary; their existen
38、ce does not in any respect preclude anyone, whether he has approved the standards or not from manufacturing, marketing, purchasing, or using products, processes, or procedures not conforming to the standards. The American National Standards Institute does not develop standards and will in no circums
39、tances give an interpretation of any American National Standard. Moreover, no person shall have the right or authority to issue an interpretation of an American National Standard in the name of the American National Standards Institute. Requests for interpretation should be addressed to the secretar
40、iat or sponsor whose name appears on the title page of this part of X9.104. CAUTION NOTICE: This American National Standard may be revised or withdrawn at any time. The procedures of the American National Standards Institute require that action be taken to reaffirm, revise, or withdraw this part of
41、X9.104 no later than five years from the date of approval. Published by Accredited Standards Committee X9, Incorporated Financial Industry Standards P.O. Box 4035 Annapolis, MD 21403 USA X9 Online http:/www.x9.org Copyright 2004 ASC X9, Inc. All rights reserved. No part of this publication may be re
42、produced in any form, in an electronic retrieval system or otherwise, without prior written permission of the publisher. Published in the United States of America. ANS X9.104-1:2004 x ASC X9, Inc. 2004 All rights reservedIntroduction The National Association of Convenience Stores (NACS) convened its
43、 Payment Systems Committee as part of an overall Technology Standards Project in November 1995. Among the first priorities that Committee established was the belief that the industry would be best served if a common format for all payment messages could be adopted. There was strong sentiment for a p
44、ossible standard for messages flowing from the card acceptor to the ensuing host processing system. The NACS Committee determined that, since existing standards did not serve this purpose, a set of guidelines should be written based on the international host-to-host standard, ISO 8583: 1993, to ensu
45、re that the convenience store and petroleum marketing industry would be able to adopt a common format for these messages. ASC X9-TG23-1999 Implementation guide for ISO 8583-based card acceptor to host messages Part 1: Convenience store and petroleum marketing industry was produced to address this ne
46、ed. In 2003, ISO 8583-1: Financial transaction card originated messages Interchange message specifications Part 1: Messages, data elements and code values was published. To remain aligned with ISO 8583, ANS X9.104 has been created. It replaces in whole X9-TG23-1999 and incorporates the updated ISO 8
47、583-1 to create a common format for payment messages flowing from the card acceptor to the acquirer. During the discussions leading up to this project, it was agreed that both a generic and an industry specific standard should be developed. Accordingly, Part 1 of X9.104 defines the messages, data el
48、ements and code values generally used in the retail financial transaction processing environment. Part 2 of X9.104 defines specific examples of messages used in the convenience store and petroleum marketing industry. Subsequent parts may be published to define card acceptorto-acquirer messages for o
49、ther retail industries. The data elements in the host-to-host message will conform to the format agreed to by the acquiring host and the receiving host. For messages conforming to ISO 8583, the acquiring host will supply the data elements as required by that standard. These data elements may be present in the message from the card acceptor or may be supplied by the acquiring host. The use of the word “Card“ in this part of X9.104 refers to any device t
