ISO 8583-1:2003

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

• Status: Withdrawn
• Publication Date: 16-Jun-2003
• ICS: 35.240.15 - Identification cards. Chip cards. Biometrics
• Technical Committee: ISO/TC 68/SC 9 - Information exchange for financial services
• Drafting Committee: ISO/TC 68/SC 9 - Information exchange for financial services
• Current Stage: 9599 - Withdrawal of International Standard
• Start Date: 18-Jul-2023
• Completion Date: 13-Dec-2025

Relations

• Revises: ISO 8583:1993/Cor 1:1999 - Financial transaction card originated messages - Interchange message specifications - Technical Corrigendum 1: .
• Effective Date: 16-Oct-2025
• Revised: ISO 8583:2023 - Financial-transaction-card-originated messages - Interchange message specifications
• Effective Date: 23-Apr-2020
• Revises: ISO 8583:1993 - Financial transaction card originated messages - Interchange message specifications
• Effective Date: 15-Apr-2008

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 [e-mail]
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.79
8.4.1 Financial presentment description.79
8.4.2 Financial presentment message rules .79
8.4.3 Financial presentment message type identifiers.81
8.4.4 Financial presentment mandatory and conditional data elements.82
8.4.5 Financial presentment message flows .83
8.5 Financial accumulation presentment.83
8.5.1 Financial accumulation presentment description .83
8.5.2 Financial accumulation presentment message rules.83
8.5.3 Financial accumulation presentment message type identifiers.84
8.5.4 Financial 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 identifiers.87
8.6.4 File action 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
iv © ISO 2003 — All rights reserved

8.7.4 Reversal mandatory and conditional 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. 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 calculation. 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 Administrative 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 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 mandatory 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 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 elements . 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 message 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. 119
8.17.1 File transfer description . 119
8.17.2 File transfer message rules.120
8.17.3 File transfer message type identifiers.120
8.17.4 File transfer mandatory and conditional data elements.121
8.17.5 File transfer message flows .121
9 Message and 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 8583.125
11 Guidance on the use of this part of ISO 8583.125
11.1 Additional message types .125
11.2 Additional data elements.125
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.159
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
Bibliography.194

vi © ISO 2003 — All rights reserved

Foreword
ISO (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 committee 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 electrotechnical 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 member 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 identifying 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 — 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
Introduction
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 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 that 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 in 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 to
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 undertaken 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 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 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.

viii © ISO 2003 — All rights reserved

INTERNATIONAL STANDARD ISO 8583-1:2003(E)

Financial 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 8583.
NOTE With the proliferation of technology available to financial institutions to offer services to customers, a range of
tokens (financial transaction cards, digital certificates etc.) now exist for identifying account relationships. In order to
maintain clarity, this part of ISO 8583 will continue to refer only to financial transaction cards as the token. However,
readers should be aware that the actual token issued by a financial institution may be different.
2 Normative references
The following referenced documents are indispensable for the application of this document. For dated
references, only the edition cited applies. For undated references, the latest edition of the referenced
document (including any amendments) applies.
ISO 3166 (all parts), Codes for the representation of names of countries and their subdivisions
ISO 4217, Codes for the representation of currencies and funds
ISO 4909, Bank cards — Magnetic stripe data content for track 3
ISO 7372, Trade data interchange — Trade data elements directory
ISO 7811-2, Identification cards — Recording technique — Part 2: Magnetic stripe — Low coercivity
ISO 7812-1, Identification cards — Identification of issuers — Part 1: Numbering system
ISO 7813, Identification cards — Financial transaction cards
ISO 7816-6, Identification cards — Integrated circuit(s) cards with contacts — Part 6: Interindustry data
elements
ISO 8583-2, Financial transaction card originated messages — Interchange message specifications — Part 2:
Application and registration procedures for Institution Identification Codes (IIC)
1)
ISO 8583-3:— , Financial transaction card originated messages — Interchange message specifications —
Part 3: Maintenance procedures for messages, data elements and code values
ISO 8601, Data elements and interchange formats — Information interchange — Representation of dates and
times
ISO 8825 (all parts), Information technology — ASN.1 encoding rules
ISO 9564-1, Banking — Personal Identification Number (PIN) management and security — Part 1: Basic
principles and requirements for online PIN handling in ATM and POS systems
ISO 9807, Banking and related financial services — Requirements for message authentication (retail)
ISO 13492, Banking — Key management related data element (retail)
2)
ISO 18245:— , Retail financial services — Merchant category codes
3 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
3.1
acquirer
financial institution (or its agent) which acquires from the card acceptor the data relating to the transaction and
initiates that data into an interchange system
NOTE The acquirer remains unchanged throughout a transaction.
3.2
address verification
process of comparing data from the point of service (POS) with that held by the card issuer to verify the
cardholder's billing address
3.3
advice
message where the sender notifies the receiver of an activity that has been taken, requiring no approval but
requiring a response
3.4
aggregation
total amount of a number of transactions where details of the individual transactions that make up the total are
not provided or recoverable
3.5
attended transaction
transaction where the acquirer has indicated that the card, cardholder and card acceptor representative are all
present at the time of the transaction
3.6
authentication
action of proving that someone or something is genuine

1) To be published. (Revision of ISO 8583-3:1998)
2) To be published.
2 © ISO 2003 — All rights reserved

3.7
authorizing agent
institution that acts on behalf of and with the authority of the card issuer
3.8
card acceptor
party accepting the card and presenting transaction data to an acquirer
3.9
cardholder
customer associated with the primary account number requesting the transaction from the card acceptor
3.10
card issuer
financial institution (or its agent) which issues the financial transaction card to the cardholder
NOTE The card issuer remains unchanged throughout a transaction.
3.11
card issuer back up total
total amount for all transactions (for an agreed set of parameters) provided when the detail of each transaction
has been lost
3.12
credit transaction
claim for funds by the cardholder for the credit of his account
NOTE At the same time, the transaction provides details of funds acknowledged as payable by the acquirer (and/or
the card acceptor) to the card issuer.
3.13
dataset
group of related sub-elements within a composite data element
NOTE See 5.4.4.1.
3.14
dataset bit map
DBM
bit map used to identify the presence (denoted by 1) or absence (denoted by 0) of sub-elements within a
dataset
NOTE See 5.4.4.4.
3.15
debit transaction
approval by the cardholder of the debit to his account
NOTE At the same time, the transaction provides a claim of funds made by the acquirer (and/or the card acceptor)
against the card issuer.
3.16
electronic purse
application within an integrated circuit card (ICC)
NOTE The application allows the cardholder to have electronic value stored in the purse.
3.17
fallback
transaction that is processed using a card reading technology that is not the card issuer's preferred card
reading technology
NOTE This might be where a magnetic stripe is used, although the card has an ICC containing the same application
as identified on the magnetic stripe, and the POS has an ICC reader or the magnetic stripe read failed and the card details
were keyed into the POS.
3.18
file
collection of Data record data elements
3.19
forwarding institution
institution within a transaction flow that sends a message forward from the originating institution
NOTE See 6.2.5.
3.20
inquiry
message (from the authorization message class) that requests information
3.21
institution identification code
unique number assigned to an institution participating in financial card originated message interchange
NOTE See 6.2.5 and 10.2.
3.22
instruction
message where the sender notifies the receiver of an activity to be taken
NOTE An instruction acknowledgement is not sent unless the receiver specifically requests one.
3.23
instruction acknowledgement
message where the receiver notifies the sender that one or more instruction messages has been received
NOTE No financial liability is implied in sending the instruction acknowledgement message.
3.24
linked load
electronic purse load transaction where the account providing the electronic purse is the same as the account
providing the funds
NOTE Only one transaction is sent to the institution to both authenticate the purse and to secure the value for the
load.
3.25
load transaction
transaction performed whereby value from the cardholder's source of funds (e.g. the funding account or cash)
is transferred to an electronic purse
NOTE In return, the electronic purse card issuer receives payment from the cardholder's funding source.
4 © ISO 2003 — All rights reserved

3.26
maintenance agency
MA
group responsible for the administrative duties related to the maintenance of this part of ISO 8583, excluding
the institution identification code
NOTE See Clause 10.
3.27
message
set of data elements used to exchange information between institutions (or their agents)
NOTE No communications (header/trailer, protocol, or character code) or security implications are assumed or
identified.
3.28
message bit map
series of bits used to identify the presence (denoted by 1) or absence (denoted by 0) of each data element in
a message
NOTE See 5.3.
3.29
message class
set of messages which supports the specific activities being performed
3.30
message function
identification of the purpose of a message and the activity involved
3.31
notification
message where the sender notifies the receiver of an activity taken
NOTE A notification acknowledgement is not sent unless the receiver specifically requests one.
3.32
notification acknowledgement
message where the receiver notifies the sender that one or more notification messages has been received
NOTE No financial liability implied in sending the notification acknowledgement.
3.33
payment
movement of funds from a cardholder account to another party
EXAMPLE A utility bill payment.
3.34
point of service
POS
card acceptor location where the cardholder agrees the transaction takes place
3.35
receiving institution
institution within a transaction flow that receives a message before it reaches the final destination
NOTE See 6.2.5.
3.36
registration authority
group responsible for the administrative duties related to the maintenance of institution identification codes
NOTE See Clause 10.
3.37
registration and maintenance management group
RMMG
group responsible for the allocation of institution identification codes (as specified in ISO 8583-2) and the
approval of changes to this part of ISO 8583 (as specified in ISO 8583-3)
NOTE See Clause 10.
3.38
repeat
resending of a request or advice message for which no response was received within the expected time
3.39
replacement authorization
authorization used when a previous authorization was approved and a subsequent authorization is required
NOTE This is used when, for example, the Amount transaction is now differe
...