ISO 8583-1:2003
(Main)Financial transaction card originated messages — Interchange message specifications — Part 1: Messages, data elements and code values
Financial transaction card originated messages — Interchange message specifications — Part 1: Messages, data elements and code values
ISO 8583-1:2003 specifies a common interface by which financial transaction card originated messages may 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 8583.
Messages initiés par cartes de transaction financière — Spécifications d'échange de messages — Partie 1: Messages, éléments de données et valeurs de code
General Information
Relations
Standards Content (Sample)
INTERNATIONAL ISO
STANDARD 8583-1
First edition
2003-06-15
Financial transaction card originated
messages — Interchange message
specifications —
Part 1:
Messages, data elements and code
values
Messages initiés par cartes de transaction financière — Spécifications
d'échange de messages —
Partie 1: Messages, éléments de données et valeurs de code
Reference number
©
ISO 2003
PDF disclaimer
This PDF file may contain embedded typefaces. In accordance with Adobe's licensing policy, this file may be printed or viewed but
shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In
downloading this file, parties accept therein the responsibility of not infringing Adobe's licensing policy. The ISO Central Secretariat
accepts no liability in this area.
Adobe is a trademark of Adobe Systems Incorporated.
Details 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 relating 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, without permission in writing from either ISO at the address below or
ISO's 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 copyright@iso.org
Web www.iso.org
Published in Switzerland
ii © ISO 2003 — All rights reserved
Contents 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.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 element directory . 14
6.2 General requirements for data elements.39
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 value (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). 45
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 identification 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 (bit 56). 53
6.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 (bit 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
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 protocol.67
7.1.1 General .67
7.1.2 Mandatory and conditional data elements .67
7.1.3 Message flows .70
7.1.4 Message errors.70
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 message 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 identifiers.77
8.3.4 Verification mandatory and conditional data elements.78
8.3.5 Verification message flows .79
8.4 Financial presentment message class.
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.