1、 Reference number ISO 8583-1:2003(E) ISO 2003INTERNATIONAL STANDARD ISO 8583-1 First edition 2003-06-15 Financial transaction card originated messages Interchange message specifications Part 1: Messages, data elements and code values Messages initis par cartes de transaction financire Spcifications
2、dchange de messages Partie 1: Messages, lments de donnes et valeurs de code ISO 8583-1:2003(E) PDF disclaimer This PDF file may contain embedded typefaces. In accordance with Adobes licensing policy, this file may be printed or viewed but shall not be edited unless the typefaces which are embedded a
3、re licensed to and installed on the computer performing the editing. In downloading this file, parties accept therein the responsibility of not infringing Adobes licensing policy. The ISO Central Secretariat accepts no liability in this area. Adobe is a trademark of Adobe Systems Incorporated. Detai
4、ls of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In the unlikely event that a problem re
5、lating to it is found, please inform the Central Secretariat at the address given below. ISO 2003 All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, wi
6、thout permission in writing from either ISO at the address below or ISOs member body in the country of the requester. ISO copyright office Case postale 56 CH-1211 Geneva 20 Tel. + 41 22 749 01 11 Fax + 41 22 749 09 47 E-mail copyrightiso.org Web www.iso.org Published in Switzerland ii ISO 2003 All r
7、ights reservedISO 8583-1:2003(E) ISO 2003 All rights reserved iiiContents Page Foreword. vii Introduction . viii 1 Scope 1 2 Normative references . 1 3 Terms and definitions. 2 4 Symbols (and abbreviated terms) . 8 4.1 Representation abbreviations . 8 4.2 Abbreviated terms. 9 5 Message structure 9 5
8、.1 Message components. 9 5.1.1 Sequence . 9 5.1.2 Message type. 9 5.2 Message repeats . 10 5.3 Message bit maps . 10 5.4 Data elements 11 5.4.1 Data element types . 11 5.4.2 Primitive data elements 11 5.4.3 Constructed data element 11 5.4.4 Composite data elements 11 6 Data elements 14 6.1 Data elem
9、ent directory . 14 6.2 General requirements for data elements39 6.2.1 Variable length data elements . 39 6.2.2 Binary data. 39 6.2.3 Expression of amounts 40 6.2.4 Conversion rates. 40 6.2.5 Identification of institutions and routing 40 6.2.6 Identification of account numbers 44 6.2.7 Tag length val
10、ue (TLV) data . 44 6.3 Specific requirements for primitive data elements . 44 6.3.1 Date and time transmission (bit 7) 44 6.3.2 Action code (bit 39). 44 6.3.3 Message authentication code (MAC) (bit 64/128) 45 6.4 Specific requirements for constructed data elements 45 6.4.1 Processing code (bit 3). 4
11、5 6.4.2 Amount transaction (bit 4) . 45 6.4.3 Amount reconciliation (bit 5) . 45 6.4.4 Amount cardholder billing (bit 6) 45 6.4.5 Amount cardholder billing fee (bit 8) 46 6.4.6 Date and time local transaction (bit 12) 46 6.4.7 Message error indicator (bit 18) 46 6.4.8 Transaction life cycle identifi
12、cation data (bit 21).48 6.4.9 Point of service data code (bit 22). 49 6.4.10 Point of service capability (bit 27). 51 6.4.11 Amounts original (bit 30) 52 6.4.12 Acquirer reference number (bit 31) . 52 6.4.13 Amounts fees (bit 46) 52 6.4.14 Amounts additional (bit 54) 53 6.4.15 Original data elements
13、 (bit 56). 53 ISO 8583-1:2003(E) iv ISO 2003 All rights reserved6.4.16 Amounts original fees (bit 66)53 6.4.17 Batch/file transfer message control (bit 68) .54 6.4.18 Batch/file transfer control data (bit 69) .54 6.4.19 File transfer description data (bit 70) 54 6.4.20 Reconciliation data primary (b
14、it 74) 54 6.4.21 Reconciliation data secondary (bit 75)55 6.4.22 Amount net reconciliation (bit 97) .55 6.4.23 Reconciliation fee amounts (bit 109/110)56 6.5 Specific requirements for composite data elements.56 6.5.1 Electronic commerce data (bit 34).56 6.5.2 Card acceptor name/location (bit 43) 57
15、6.5.3 Additional response data (bit 44).58 6.5.4 Verification data (bit 49)58 6.5.5 Integrated circuit card (ICC) related data (bit 55).59 6.5.6 Transaction specific data (bit 104) 60 7 Messages and transactions .67 7.1 Message protocol67 7.1.1 General .67 7.1.2 Mandatory and conditional data elemen
16、ts .67 7.1.3 Message flows .70 7.1.4 Message errors70 7.1.5 Exception message flows.70 7.1.6 Transaction relationships.71 8 Message class definitions 71 8.1 General .71 8.2 Authorization message class.72 8.2.1 Authorization description.72 8.2.2 Authorization message rules .72 8.2.3 Authorization mes
17、sage type identifiers 74 8.2.4 Authorization mandatory and conditional data elements.75 8.2.5 Authorization message flows.76 8.3 Verification messages 76 8.3.1 Verification description 76 8.3.2 Verification message rules.76 8.3.3 Verification message type identifiers77 8.3.4 Verification mandatory a
18、nd conditional data elements.78 8.3.5 Verification message flows 79 8.4 Financial presentment message class79 8.4.1 Financial presentment description79 8.4.2 Financial presentment message rules 79 8.4.3 Financial presentment message type identifiers.81 8.4.4 Financial presentment mandatory and condi
19、tional data elements82 8.4.5 Financial presentment message flows .83 8.5 Financial accumulation presentment83 8.5.1 Financial accumulation presentment description .83 8.5.2 Financial accumulation presentment message rules83 8.5.3 Financial accumulation presentment message type identifiers.84 8.5.4 F
20、inancial accumulation presentment mandatory and conditional data elements .84 8.5.5 Financial accumulation presentment message flows .86 8.6 File action message class 86 8.6.1 File action description 86 8.6.2 File action message rules.86 8.6.3 File action message type identifiers87 8.6.4 File action
21、 mandatory and conditional data elements 88 8.6.5 File action message flows 89 8.7 Reversal message class .89 8.7.1 Reversal description .89 8.7.2 Reversal message rules .90 8.7.3 Reversal message type identifiers 90 ISO 8583-1:2003(E) ISO 2003 All rights reserved v8.7.4 Reversal mandatory and condi
22、tional data elements. 91 8.7.5 Reversal message flows. 92 8.8 Chargeback message class . 92 8.8.1 Chargeback description . 92 8.8.2 Chargeback message rules . 92 8.8.3 Chargeback message type identifiers 93 8.8.4 Chargeback mandatory and conditional data elements . 93 8.8.5 Chargeback message flows.
23、 94 8.9 Reconciliation message class . 95 8.9.1 Reconciliation description . 95 8.9.2 Reconciliation message rules . 95 8.9.3 Reconciliation message type identifiers 96 8.9.4 Reconciliation mandatory and conditional data elements . 98 8.9.5 Reconciliation message flows. 99 8.9.6 Reconciliation calcu
24、lation 99 8.9.7 Reconciliation transaction flows. 102 8.10 Administrative message class. 102 8.10.1 Administrative description. 102 8.10.2 Administrative message rules . 102 8.10.3 Administrative message type identifiers 103 8.10.4 Administrative mandatory and conditional data elements. 104 8.10.5 A
25、dministrative message flows 104 8.11 Retrieval and retrieval fulfilment . 105 8.11.1 Retrieval and retrieval fulfilment description. 105 8.11.2 Retrieval and retrieval fulfilment message rules . 105 8.11.3 Retrieval and retrieval fulfilment message type identifiers 105 8.11.4 Retrieval and retrieval
26、 fulfilment mandatory and conditional data elements. 106 8.11.5 Retrieval and retrieval fulfilment message flows 107 8.12 Error messages . 107 8.12.1 Error messages description 107 8.12.2 Error messages message rules. 107 8.12.3 Error messages message type identifiers 108 8.12.4 Error messages manda
27、tory and conditional data elements. 108 8.12.5 Error messages message flows 109 8.13 Fee collection message class 109 8.13.1 Fee collection description 109 8.13.2 Fee collection message rules 109 8.13.3 Fee collection message type identifiers. 110 8.13.4 Fee collection mandatory and conditional data
28、 elements 110 8.13.5 Fee collection message flows . 111 8.14 Network management message class 112 8.14.1 Network management description 112 8.14.2 Network management message rules. 112 8.14.3 Network management message type identifiers . 113 8.14.4 Network management mandatory and conditional data e
29、lements 114 8.14.5 Network management message flows 114 8.15 Key management 115 8.15.1 Key management description 115 8.15.2 Key management message rules 115 8.15.3 Key management message type identifiers . 115 8.15.4 Key management mandatory and conditional data elements 116 8.15.5 Key management m
30、essage flows 116 8.16 Batch transfer 116 8.16.1 Batch transfer description . 116 8.16.2 Batch transfer message rules 117 8.16.3 Batch transfer message type identifiers. 117 8.16.4 Batch transfer mandatory and conditional data elements . 117 8.16.5 Batch transfer message flows. 118 8.17 File transfer
31、 119 8.17.1 File transfer description . 119 ISO 8583-1:2003(E) vi ISO 2003 All rights reserved8.17.2 File transfer message rules120 8.17.3 File transfer message type identifiers.120 8.17.4 File transfer mandatory and conditional data elements121 8.17.5 File transfer message flows .121 9 Message and
32、transaction matching 122 9.1 General .122 9.2 Message matching 122 9.3 Transaction matching .123 10 Registration and maintenance management group (RMMG) .124 10.1 General .124 10.2 Allocation of institution identification codes .125 10.3 Development of this part of ISO 8583125 11 Guidance on the use
33、 of this part of ISO 8583.125 11.1 Additional message types 125 11.2 Additional data elements125 11.3 Mandatory and conditional data elements .126 11.4 Unintentional introduction of control characters 126 Annex A (normative) Code listings .127 Annex B (normative) Data elements in bit number order.15
34、9 Annex C (informative) Data transparency 169 Annex D (informative) Examples of batch transfer .173 Annex E (informative) Examples of file transfer 185 Annex F (informative) Summary of changes made to ISO 8583:1993 .190 Bibliography194 ISO 8583-1:2003(E) ISO 2003 All rights reserved viiForeword ISO
35、(the International Organization for Standardization) is a worldwide federation of national standards bodies (ISO member bodies). The work of preparing International Standards is normally carried out through ISO technical committees. Each member body interested in a subject for which a technical comm
36、ittee has been established has the right to be represented on that committee. International organizations, governmental and non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely with the International Electrotechnical Commission (IEC) on all matters of electrote
37、chnical standardization. International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2. The main task of technical committees is to prepare International Standards. Draft International Standards adopted by the technical committees are circulated to the memb
38、er bodies for voting. Publication as an International Standard requires approval by at least 75 % of the member bodies casting a vote. Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. ISO shall not be held responsible for identifyi
39、ng any or all such patent rights. ISO 8583-1 was prepared by Technical Committee ISO/TC 68, Banking, securities and other financial services, Subcommittee SC 6, Retail financial services. ISO 8583 consists of the following parts, under the general title Financial transaction card originated messages
40、 Interchange message specifications: Part 1: Messages, data elements and code values Part 2: Application and registration procedures for Institution Identification Codes (IIC) Part 3: Maintenance procedures for messages, data elements and code values ISO 8583-1:2003(E) viii ISO 2003 All rights reser
41、vedIntroduction Services of the financial industry include the exchange of electronic messages relating to financial transactions. Agreements on application specifications are generally at a private level. This International Standard is designed as an interface specification enabling messages to be
42、exchanged between systems adopting a variety of application specifications. The application specification may remain at the private level. Designers of such applications have complete design freedom within the overall constraint that messages shall be convertible to this interface format in order th
43、at international interchange may take place. This International Standard uses a concept called a bit map, whereby each data element is assigned a position indicator in a control field, or bit map. A one in the assigned position indicates the presence of a data element in a specific message. A zero i
44、n the assigned position indicates the absence of a data element in a specific message. Data representation used in individual systems is subject to the commercial relationships between the parties contracting to each system. The message formats specified in this International Standard are designed t
45、o ensure that compatibility between systems conforming to this International Standard is always feasible. In a number of cases, the names of data elements and message classes can become confusing when used in descriptive paragraphs. The word authorization is a typical example. It is an activity unde
46、rtaken by a card issuer, it is the name of a message class where an acquirer requests a card issuer to undertake the activity and it is also a word used in many data element names. To aid clarity, the following conventions are followed within this International Standard: data element names have the
47、first letter capitalized; data element names are shown in italics except when used in tables or figures; message class names are shown capitalized when the context refers to their use in messages or transactions. ISO 8583:1993 has been revised to be published in three parts. A number of changes have
48、 been made to accommodate the latest advances in payment technologies and the opportunity has also been taken to improve the layout and readability. A summary of the most significant changes between ISO 8583:2003 (all parts) and ISO 8583:1993 is provided in Annex F. INTERNATIONAL STANDARD ISO 8583-1
49、:2003(E) ISO 2003 All rights reserved 1Financial transaction card originated messages Interchange message specifications Part 1: Messages, data elements and code values 1 Scope This part of ISO 8583 specifies a common interface by which financial transaction card-originated messages can be interchanged between acquirers and card issuers. It specifies message structure, format and content, data elements and values for data elements. The method by which settlement takes place is not within the scope of this part of ISO 85
