1、 ASC X9, Inc. 2004 All rights reserved American National Standard for Financial Services X9.104-2:2004 Financial transaction card originated messages Card acceptor to acquiring host messages Part 2: Convenience store and petroleum marketing industry Accredited Standards Committee X9, Incorporated Fi
2、nancial Industry Standards Date Approved: 10/6/2004 American National Standards Institute ANS X9.104-2:2004 ii ASC X9, Inc. 2004 All rights reservedContents Page Foreword.viii Introduction .x 1 Scope . 14 2 Normative references . 14 3 Terms and definitions 14 4 Symbols and abbreviated terms . 15 5 D
3、ata elements 15 5.1 Point of service data code usage 15 5.2 Card data usage 16 5.3 Transaction specific data. 16 5.4 Sample data element values 21 6 Authorization and financial transaction message examples . 23 6.1 Indoor post-pay sale (credit card). 23 6.2 Indoor post-pay sale (debit card with PIN)
4、. 25 6.3 Indoor fleet card sale (customer data entry) 27 6.4 Indoor prepay (card verify using Track 2 card data). 29 6.5 Indoor prepay funds reservation (debit card with PIN). 31 6.6 Indoor prepay (fleet card) 33 6.7 Outdoor prepay (RFID transponder). 35 6.8 Return/refund 38 6.9 Adjustment (return w
5、ith matched transaction)39 6.10 Store and forward transactions. 41 6.11 Check authorization/guarantee (drivers license and MICR data) . 46 6.12 Cash sale . 48 6.13 Indoor purchase with address verification 49 6.14 Indoor purchase with card verification data 51 7 Reconciliation message examples . 53
6、7.1 Batch reconciliation/transmittal 53 8 Host-based stored value message examples 62 8.1 Stored value card activation 63 8.2 Stored value card load . 65 8.3 Stored value card balance inquiry 67 8.4 Stored value card sale 68 8.5 Stored value card authorization (approved for lesser amount). 70 9 Bill
7、 payment message examples. 72 9.1 Bill payment. 72 9.2 Bill payment inquiry . 75 10 File action message examples 77 10.1 File download 77 11 Message error handling examples 81 11.1 Failed debit transaction with reversal (timeout) 81 11.2 Pre-authorization or funds reservation request and reversal 84
8、 ANS X9.104-2:2004 ASC X9, Inc. 2004 All rights reserved iii11.3 Error response for unrecognized message type .86 11.4 Error response for bad message reason code.87 11.5 Error response for multiple errors.89 12 Administrative message examples91 12.1 Email message from POS system/device example91 12.
9、2 Email message request from POS system/device example93 13 Network management message examples .94 13.1 Dial statistics .94 Annex A (informative) Comparative message sizes97 A.1 General .97 Annex B (informative) Prepaid phone account transaction data .98 B.1 General .98 Figures Figure 1 Indoor post
10、-pay sale (credit card) message flow.24 Figure 2 Indoor post-pay sale (debit card with PIN) message flow .25 Figure 3 Indoor fleet card sale (customer data entry) message flow .28 Figure 4 Indoor prepay (card verify using Track 2 card data) message flow .30 Figure 5 Indoor prepay funds reservation (
11、debit card with PIN) message flow31 Figure 6 Indoor prepay (fleet card) message flow .33 Figure 7 Outdoor prepay (RFID transponder) message flow 35 Figure 8 Return/refund message flow38 Figure 9 Adjustment (return with matched transaction) message flow40 Figure 10 Store and forward message flow.42 F
12、igure 11 Check authorization/guarantee message flow 46 Figure 12 Cash sale message flow48 Figure 13 Indoor purchase with address verification message flow50 Figure 14 Indoor purchase with card verification data message flow52 Figure 15 Reconciliation in balance message flow54 Figure 16 Reconciliatio
13、n out of balance message flow .57 Figure 17 Stored value activation message flow .63 Figure 18 Stored value card load message flow .65 Figure 19 Stored value card balance inquiry message flow67 ANS X9.104-2:2004 iv ASC X9, Inc. 2004 All rights reservedFigure 20 Stored value card sale message flow .
14、69 Figure 21 Stored value card authorization (approved for lesser amount) message flow 71 Figure 22 Bill Payment message flow 73 Figure 23 Bill payment Inquiry message flow 75 Figure 24 File download message flow. 77 Figure 25 Failed debit transaction with reversal (time-out) 82 Figure 26 Error resp
15、onse for unrecognized message type message flow 84 Figure 27 Error response for unrecognized message type message flow 86 Figure 28 Error response for bad message reason code message flow 88 Figure 29 Multiple error message flow 89 Figure 30 Administrative email sent message flow 92 Figure 30 Admini
16、strative email inquiry message flow 93 Figure 31 Dial statistics message flow. 95 Tables Table 1 Product data (bit 63). 17 Table 2 Fleet card data (bit 104-78) 18 Table 3 Sample data element values used in message examples. 21 Table 4 Indoor post-pay sale (credit card) request message (200) 24 Table
17、 5 Indoor post-pay sale (credit card) response message (210) . 24 Table 6 Indoor post-pay sale (debit card with PIN) request message (200). 26 Table 7 Indoor post-pay sale (debit card with PIN) response message (210) 27 Table 8 Indoor fleet card sale (customer data entry) request message (200)28 Tab
18、le 9 Indoor fleet card sale (customer data entry) response message (210) . 29 Table 10 Indoor prepay (card verify using Track 2 card data) request message (100) 30 Table 11 Indoor prepay (card verify using Track 2 card data) response message (110) 31 Table 12 Indoor prepay funds reservation (debit c
19、ard with PIN) request message (100) . 32 Table 13 Indoor prepay funds reservation (debit card with PIN) response message (110) 33 ANS X9.104-2:2004 ASC X9, Inc. 2004 All rights reserved vTable 14 Indoor prepay (fleet card) request message (100) .34 Table 15 Indoor prepay (fleet card) response messag
20、e (110) 34 Table 16 Outdoor prepay (RFID transponder) request message (100) 36 Table 17 Outdoor prepay (RFID transponder) response message (110)36 Table 18 Outdoor prepay (RFID transponder) advice message (220) 37 Table 19 Outdoor prepay (RFID transponder) advice response message (230) 37 Table 20 R
21、eturn/refund request message (200)39 Table 21 Return/refund response message (210).39 Table 22 Adjustment (return with matched transaction) advice message (220) .40 Table 23 Adjustment (return with matched transaction) advice response message (230) .41 Table 24 Store and forward financial presentmen
22、t advice message (220) .43 Table 25 Store and forward financial presentment advice response message (230) .44 Table 26 Store and forward financial presentment advice message (220) .44 Table 27 Store and forward financial presentment advice response message (230) .45 Table 28 Store and forward financ
23、ial presentment advice message (220) .45 Table 29 Store and forward financial presentment advice response message (230) .45 Table 30 Check authorization/guarantee request message (100) 47 Table 31 Check authorization/guarantee response message (110)47 Table 32 Cash sale request message (200)49 Table
24、 33 Cash sale response message (210).49 Table 34 Indoor purchase with address verification request message (200)50 Table 35 Indoor purchase with address verification response message (210) .51 Table 36 Indoor purchase with card verification data request message (200)52 Table 37 Indoor purchase with
25、card verification data response message (210).53 Table 38 Reconciliation in balance request (504) 55 Table 39 Reconciliation in balance response (514)55 Table 40 Reconciliation out of balance request (504) .58 ANS X9.104-2:2004 vi ASC X9, Inc. 2004 All rights reservedTable 41 Reconciliation out of b
26、alance response (514) 59 Table 42 Transaction advice message (220) 60 Table 43 Transaction advice response message (230) 60 Table 44 Reconciliation advice message (524) 60 Table 45 Reconciliation in balance response (534) 61 Table 46 Stored value activation request message (200). 64 Table 47 Stored
27、value activation response message (210) 64 Table 48 Stored value card load request message (200). 66 Table 49 Stored value card - load response message (210) 66 Table 50 Stored value card balance inquiry request message (200) 68 Table 51 Stored value card balance inquiry response message (210) 68 Ta
28、ble 52 Stored value card sale request message (200) . 69 Table 53 Stored value card sale response message (210) . 70 Table 54 Stored value card authorization (approved for lesser amount) request message (100) 71 Table 55 Stored value card (approved for lesser amount) response message (110) 72 Table
29、56 Bill Payment request message (200) 73 Table 57 Bill Payment response message (210) 74 Table 58 Bill payment inquiry request message (100) 76 Table 59 Bill payment Inquiry response message (110). 76 Table 60 File download (first) request message (2304) 78 Table 61 File download (first) response me
30、ssage (2314). 78 Table 62 File download (last) request message (2304) 79 Table 63 File download (last) response message (2314). 79 Table 64 Example POS configuration data in request message 80 Table 65 Example POS configuration data in response . 80 Table 66 Failed debit request message (200) 82 Tab
31、le 67 Time-out reversal advice message (420). 83 ANS X9.104-2:2004 ASC X9, Inc. 2004 All rights reserved viiTable 68 Time-out reversal advice response message (430) .83 Table 69 Failed authorization or funds reservation request message.85 Table 70 Time-out reversal advice message (420) .85 Table 71
32、Time-out reversal advice response message (430) .86 Table 72 Unrecognized message type (9200).87 Table 73 Error with unrecognized message type response (644).87 Table 74 Bad message reason code request message (200).88 Table 75 Error with bad message reason code response (644)89 Table 76 Multiple er
33、ror request message (200).90 Table 77 Multiple error response (644)91 Table 78 Administrative email sent request message (1604)92 Table 79 Administrative email sent request response message (1614)93 Table 78 Administrative email inquiry request message (1604)94 Table 79 Administrative email inquiry
34、request response message (1614)94 Table 80 Dial statistics advice message (1824) 95 Table 81 Dial statistics advice response message (1834) 96 Table A.1 Comparison of typical message sizes.97 Table B.1 Prepaid phone account data .98 ANS X9.104-2:2004 viii ASC X9, Inc. 2004 All rights reservedForewor
35、d This part of X9.104 provides examples of common messages in the convenience store/petroleum marketing industry and its component business operations. It defines data elements and code values used in the messages and explanations of common business practices. ANSI X9.104 consists of the following p
36、arts, under the general title Financial transaction messages - Card acceptor to acquiring host messages: - Part 1: Messages, data elements and code values - Part 2: Convenience store and petroleum marketing industry examples Subsequent parts may be published to define card acceptor to acquiring host
37、 messages for other industries. To aid clarity the following conventions are followed within this part of X9.104. Data element names have the first letter capitalized Data element names are shown in italics except when used in tables or figures. Approval of an American National Standard requires ver
38、ification by ANSI that the requirements for due process, consensus, and other criteria for approval have been met by the standards developer. Consensus is established when, in the judgment of the ANSI Board of Standards Review, substantial agreement has been reached by directly and materially affect
39、ed interests. 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; thei
40、r existence 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 n
41、o circumstances 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
42、 secretariat 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
43、 part of 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 ANS X9.104-2:2004 ASC X9, Inc. 2004 All rights reserved ixCopyright 2004 ASC
44、X9, Inc. All rights reserved. No part of this publication may be reproduced 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-2:2004 x ASC X9, Inc. 2004 All rights reservedIntroduction
45、 The National Association of Convenience Stores (NACS) convened its Payment Systems Committee as part of an overall Technology Standards Project in November 1995. Among the first priorities of that Committee was to consider development of a common format for all payment messages. Although there was
46、strong sentiment for a possible standard for messages flowing from the card acceptor to the ensuing host processing system, the NACS Committee determined that existing standards did not serve this purpose. Therefore, NACS convened a working group within X9A to develop a set of guidelines based on th
47、e international acquirer to issuer standard, ISO 8583: 1993, specifically designed for the convenience store and petroleum marketing industry. That guidance document was adopted by X9 in 1999. ASC X9-TG23-1999 Implementation guide for ISO 8583-based card acceptor to host messages Part 1: Convenience
48、 store and petroleum marketing industry (TG-23). Despite Y2K and the economic downturn, a number of implementations of TG-23 have been documented. However, because TG-23 was based on ISO 8583, and that international standard was undergoing its five-year review process, many others interested in adop
49、ting TG-23 were inclined to delay significant implementation efforts pending the update of the base standard. In 2003, ISO 8583-1: Financial transaction card originated messages Interchange message specifications Part 1: Messages, data elements and code values was published. To enable TG-23 to remain aligned with ISO 8583,
