Iso8583 1993

INTERNATIONAL
STANDARD
Second edition
1993-12-15
Financial transaction card originated

messages - Interchange message
specificatiorls
Messages initie’s par carte de transaction financi&re - Spkifications

d’khange de messages
Reference number
IS0 8583:1993(E)
IS0 8583 : 1993 (E)
Contents
Page
Foreword ...................................................................................................... iv
Introduction ................................................................................................. V
Scope ................................................................................................. 1
Normative references ....................................................................... 1
Definitions ......................................................................................... 1
Message structure ............................................................................ 3

4.1 General ........................................................................................ 3
4.2 Bit maps ...................................................................................... 13
4.3 Data element directory ............................................................... 28
4.4 Requirements for data elements ............................................... 36
Message and transaction flows ....................................................... 41

5.1 General ........................................................................................ 41
5.2 Message flow diagrams ............................................................. 41
5.3 Transaction flow diagrams ........................................................ 48
Message and transaction matching ................................................ 50

6.1 General ........................................................................................ 50
6.2 Message matching ..................................................................... 50
6.3 Transaction matching ................................................................ 50
Maintenance Agency and Registration Authority .......................... 50

7.1 Maintenance of codes ................................................................ 50
7.2 IS0 8583 Institution identification codes .................................. 50
7.3 All other IS0 8583 codes ............................................................ 51
Guidance on the use of this International Standard ....................... 51

8.1 Additional message types .......................................................... 51
8.2 Additional data elements ........................................................... 51
8.3 Mandatory and conditional data elements ............................... 51
8.4 Unintentional introduction of control characters ..................... 51
@ IS0 1993
All rights reserved. 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 the publisher.
International Organization for Standardization
Case postale 56 CH-1211 Genbve 20 Switzerland
l l
Printed in Switzerland
ii
ISO8583:1993(E)
Figures
1 Bit maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . 13
2 Reconciliation example ..*............................................................... 49
Tables
1 Amounts in types of authorization messages ............................... 4
2 Amounts in types of financial transaction messages ................... 5
3 Amounts in reversal messages ...................................................... 6
4 Financial transactions ..................................................................... 6
5 Amounts in chargeback messages ................................................ 7
6 Message type identifiers ................................................................. 9
7A Bit maps (in numerical order) ......................................................... 15
7B Bit maps (by message type) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..*.................. 19
8 Conditions used in table 7B . . . . . . ..*................................................... 27
9 Data element directory ................................................................... 29
10 Usage of institution identification codes ....................................... 37
11 Reconciliation calculation ............................................................... 39
Annexes
A Code listings .................................................................................... 52

A.1 Action codes .................................................................................... 53
A.2 Amount type codes ......................................................................... 55
A.3 Authorization life cycle codes ........................................................ 55
A.4 Card acceptor business codes ........................................................ 55
A.4.1 Card acceptor business codes (numerically) ................................ 55
A.4.2 Card acceptor business codes (alphabetically) ............................. 59
A.5 Fee type codes ................................................................................. 63
A.6 Function codes ................................................................................ 64
A.7 Message reason codes ................................................................... 65
A.8 Point of service data code ............................................................... 68
A.9 Processing codes ............................................................................ 70
B Conversion guide . . ..I....................................................................... 72

B.l Introduction . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
8.2 Purpose . .. . .. . .. . .. . .. . .. . .. . .. . ... .. .. . .. .. . . .. . .. . . . . .. . .. . .. . .. . .. . .. . .. .. . .. . .. . .. . .. . .. . .. . .. . 73
B.3 Differences between 1987 and 1993 editions of IS0 8583 . . . . . . . . . . . . . . 73
B.3.1 General ..*.*.............................................,......................................... 73
B.3.2 Definitions . . .. . .. . .. . .. . .. . .. . .. . .. . .. .. . .. . .. . .. . .. . .. . .. . . . . .. . .. . .. . .. .. . . . . .. . .. . .. . .. . .. . .. . 74
B.3.2.1 Additions . . . . . . . . ..I.............................................................................. 74
B.3.2.2 Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
8.3.2.3 Deletions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
. ..
III
IS0 8583 : 1993 (E)
B.3.3 Message structure .......................................................................... 75

B.3.4 Message types ................................................................................ 75
8.3.5 Data elements ................................................................................. 83
B.3.5.4 Additions ......................................................................................... 83
B.3.5.2 Changes ........................................................................................... 84
B.3.5.3 Deletions .......................................................................................... 85
B.3.5.4 Action, function and message reason code mapping .................. 86
B.3.5.5 Point of sevice data code mapping ................................................ 90
B.3.6 Usage of data elements .................................................................. 92
B.3.7 Message flows ................................................................................ 107
B.3.7.1 Authorization messages ................................................................. 107
B.3.7.2 Financial messages ......................................................................... 107
B.3.7.3 File action messages ...................................................................... 107
B.3.7.4 Reversal messages ......................................................................... 107
B.3.7.5 Chargeback messages .................................................................... 107
B.3.7.6 Reconciliation messages ................................................................ 108
B.3.7.7 Administrative messages ............................................................... 108
B.3.7.8 Fee collection messages ................................................................ 108
B.3.7.9 Network management messages .................................................. 108
B.3.7.10 Exception message flows ............................................................... 109
B.4 Further advice ................................................................................. 109
B.4.1 Usage of amount data elements .................................................... 110
B.4.1.1 General ............................................................................................ 110
B.4.1.2 Authorizations ................................................................................. 110
B.4.1.3 Financial transactions ..................................................................... 111
B.4.1.4 Reversals ......................................................................................... 111
B.4.1.5 Chargebacks .................................................................................... 111
B.4.2 Reconciliation processing .............................................................. 112
B.4.2.1 General ............................................................................................ 112
B.4.2.2 Accumulation .................................................................................. 112
B.4.3 Fee collection .................................................................................. 113
B.4.4 Usage of fee amount data elements .............................................. 116
Tables
B.l Comparison of message classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
B.2 File update code (1987) mapped to function code (1993) .,....,..... 86
B.3 Network management information code (1987) mapped to
function code (1993) . . . . . . . . . . . . ..*................................................*....... 87
B.4 Response code (1987) mapped to message reason code and
action code (1993) . . . . . . . . . . . . . . . . . . . . . . . . . . ..*...........................*.................. 88
B.5 Settlement code (1987) mapped to action code (1993) ..,... . . . . . . . . . . 90
B.6 Point of service PIN capture code (1987) mapped to point of
service data (1993) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
B.7 Point of service condition code (1987) mapped to point of
service data (1993) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
B.8 Point of service entry mode (1987) mapped to point of service
data (1993) . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . .. . . 92
B.9 Data elements by message class . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . .. . . . . . 93
B.10 Reconciliation processing examples ..11.........,....,.,.,.,..,,.,,....,......,. 114
C Forms for application for institution identifiers and codes . . . . . . . . . . 117

IS0 8583 : 1993 (E)
IS0 (the International Organization for Standardization) is a worldwide

federation of national standards bodies (IS0 member bodies). The work of
preparing International Standards is normally carried out through IS0 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. IS0 collaborates closely with the
International Electrotechnical Commission (IEC) on all matters of
electrotechnical standardization.
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.
International Standard IS0 8583 was prepared by Technical Committee lSO/rC 68,
Banking and related financial services, subcommittee SC 6, Financial
transaction cards, related media and operations.
This second edition cancels and replaces the first edition (IS0 858319871, of
which it constitutes a technical revision.
Annex A forms an integral part of this International Standard. Annexes B and C

are for information only.
V
IS0 8583:1993(E)
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 introduces the concept of a message version

number to distinguish between messages which comply with this or
subsequent editions of the Standard, and those complying with the 1987
edition.
This International Standard uses a concept called bit map, whereby each data
element is assigned a position indicator in a control field, or bit map. The
presence of a data element in a specific message is indicated by a one in the
assigned position; the absence of a data element is indicated by a zero in the
assigned position.
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.
VI
INTERNATIONAL STANDARD IS0 8583 : 1993 (E)
Financial transaction card originated messages -

Interchange message specifications
1 Scope IS0 4909:1987, Bank cards - Magnetic stripe data

content for track 3.
This International Standard addresses the following: IS0 7372:1986, Trade data interchange - Trade data
elements directory (Endorsement of UNECEFDED,
a) Interchange Message Specifications
sections 1,2,3,4 and 9).
This International Standard specifies a common
IS0 7810:1985, Identification cards - Physical
interface by which financial transaction card
characteristics.
originated messages may be interchanged between
acquirers and card issuers. It specifies message IS0 78 12: 1987, Identification cards - Numbering
structure, format and content, data elements and values system and registration procedure for issuer
for data elements. The method by which settlement identification.
takes place is not within the scope of this standard.
b) Registration Authority IS0 78 13: 1990, /den tification cards - Financial

transaction cards.
This International Standard specifies a numbering
system for institution identification codes for IS0 8601:1988, Data elements and interchange
financial institutions which do not have an IS0 7812 formats - Information interchange - Representation
of dates and times.
institution identification number. It also specifies
the procedures used for the registration of
IS0 9564-1:1991, Banking - Persona/ identification
institution identification codes.
Number management and security - Part I: PIN
c) Maintenance Agency of Codes protection principles and techniques.
This International Standard establishes procedures IS0 9807: 199 1, Banking and related financial services
for a Maintenance Agency for codes used in this -Requirements for message authentication (retail).
standard, the method of applying for codes and the
method of obtaining lists of codes. IS0 1OZOZ- 1: 199 1, Financial transaction cards -
Security architectures of financial transaction systems
using integrated circuit cards - Part I: Card life cycle.
2 Normative references
3 Definitions
The following standards contain provisions which,
through reference in this text, constitute provisions of
this International Standard. At the time of publication, For the purpose of this International Standard, the
the editions indicated were valid. All standards are following definitions apply.
subject to revision, and parties to agreements based
on this International Standard are encouraged to 3.1 acquirer: Financial institution (or its agent) which
investigate the possibility of applying the most recent acquires from the card acceptor the data relating to
editions of the standards indicated below. Members the transaction and initiates that data into an
of IEC and IS0 maintain registers of currently valid interchange system. The acquirer remains unchanged
International Standards. throughout the transaction.
IS0 3166: 1988, Codes for the representation of names

3.2 advice: A message where the sender notifies the
of countries.
receiver of an activity that has been taken, requiring
no approval but requiring a response.
IS0 4217:1990, Codes for the representation of
currencies and funds.
1
IS0 8583 : 1993 (E)
33 authorization: The approval o r guarantee of funds 3.18 message: A set of data elements used to
give n by the card issuer to the acq uirer (see 4. 1.3.1). exchange information between institutions (or their
agents). No communications (header/trailer, protocol,
3.4 authorizing agent: An institution that acts on or character code) or security implications are
behalf of and with the authority of the card issuer. assumed or identified.
3.5 bit map: A series of 64 bits used to identify the 3.19 message class: The set of messages which
presence (denoted by 1) or absence (denoted by 0) of describes the specific activit ies bein g performe d.
each data element in a message (see 4.2).
3.20 message function: The identification of the
36 card acceptor: Party accepting the card and purpose of a message and the activity involved.
pie senting transacti on data to an acqu irer.
3.21 notification: A message where the sender
3.7 cardholder: Customer associated with the notifies the receiver of an activity taken, requiring no
primary account number requesting the transaction approval or response.
from the card acceptor.
3.22 payment: A movement of funds from a cardholder
3.8 (card) issuer: Financial institution (or its agent) account to another party, e.g., a utility bill payment.
which issues the financial transaction card to the
cardholder. The card issuer remains unchanged 3.23 point of service: Card acceptor locat ion wh ere
throughout a transaction. the cardholder agrees the transaction takes place.
3.9 chargeback: A transaction from the card issuer to 3.24 receiving institution: Institution within a
the acquirer used to partially or completely reverse a transaction flow that receives a message before it
previously completed financial transaction (see reaches the final destination (see 4.4.4).
4.1.3.5).
3.25 reconciliation: An exchange of messages between
3.10 credit transaction: A claim for funds by the two institutions (acquirer, card issuer or their agents)
cardholder for the credit of his account. At the same to reach agreement on financial totals (see 4.1.3.6).
time it provides details of funds acknowledged as
payable by the acquirer (and/or the card acceptor) to
3.26 registration authority: Entity under the
the card issuer.
authority of the IS0 Council designated to allocate
institution identification codes and maintain the
3.11 debit transaction: An approval by the register of those codes.
cardholder of the debit to his account. At the same
time it provides a claim of funds made by the acquirer
(and/or the card acceptor) against the card issuer. 3.27 replacement authorization: An authorization
used when a previous authorization was approved
and a subsequent authorization is required because
3.12 financial transaction: A transaction from the the amount, transaction is now different from the
acquirer to the card issuer containing all the originally approved amount (see 4.1.3.1).
necessary data elements for authorization, posting
and reconciliation (see 4.1.3.2).
3.28 representment: A financial transaction
originated by an acquirer to partially or wholly
3.13 file action: A transaction used to add, change, recover funds charged back to the acquirer by a card
delete or replace a file or a record (see 4.1.3.3). issuer in a chargeback (see 4.1.3.2).
3.14 forwarding institution: Institution within a 3.29 request: A message where the sender informs
transaction flow that sends a message forward from the receiver that a transaction is in progress and a
the originating institution (see 4.4.4). response is required to complete the activity.
3.15 inquiry: An authorization transaction that

3.30 resubmission: The reentry of a request message
requests information.
which was previously denied or rejected (see 4.1.3.1
and 4.1.3.2).
3.16 institution identification code: Unique number
assigned to an institution participating in financial card
3.31 reversal: A transaction from the acquirer to the
originated message interchange (see 4.4.4and 4.4.16).
card issuer informing the card issuer that the
3.17 maintenance agency: Entity under the authority previously initiated transaction cannot be processed
of the IS0 Council responsible for maintaining the list as instructed, i.e., is undeliverable, unprocessed or
of codes within this International Standard. cancelled by the receiver (see 4.1.3.4).
2
IS0 8583 : 1993 (El
3.32 settlement: A transfer of funds to complete one 4.1 .l Message

r type identifier structure
or more prior transactions made, subject to final
accounting. The message type identifier is a four-digit numeric
field identifying each message version number,
message class, message function and transaction
3.33 settlement institution: Financial institution (or originator. Every message shall begin with a message
its agent) at which the accounts are held by the type identifier. Version numbers shall not be assigned
parties settling. This institution, acting on information as the result of editorial or code list changes.
provided by the parties, transfers the appropriate
funds between the accounts. First Position -Version Number
0 - IS0 8583:1987
3.34 supplementary authorization: An authorization 1 - IS0 8583:1993
used when a previous authorization was approved
2-7 - reserved for IS0 use
and one or more subsequent authorizations are
required for additional amounts (see 4.1.3.1). 8- reserved for national use
9- reserved for private use
3.35 transaction: One or more related messages Where the first position is 1, the second through
within the same message class designed to complete fourth posit ions shall be defined as follows:
(insofar as this is possible) the intention of the sender
of the original message. Second Position - Message Class
O- reserved for IS0 use
3.36 transaction destination institution: The final l- authorization
institution receiving the request, advice or notification 2 - financial
message in a transaction. The transaction
3 - file action
destination remains unchanged throughout the
transaction. 4- reversaI/chargeback
5- reconciliation
3.37 transaction originator institution: The 6- administrative
institution initiating the request, advice or notification 7 -fee collection
message in a transaction. The transaction originator 8- network management
remains unchanged throughout the transaction, 9 - reserved for IS0 use
Third Position - Message Function

3.38 transfer: The movement of funds by a
cardholder from one of its accounts to another of the 0 - request
cardholder’s accounts both of which are held by the 1 -request response
same financial institution. 2- advice
3- advice response
3.39 version: A description of interchange message 4- notification
formats that distinguishes between different
5-9 - reserved for IS0 use
arrangements of data elements within bit maps (i.e.,
where the data elements are added, deleted or their Fourth Position -Transaction Originator
meaning, position or format changes or the message
0 - acquirer
flows are modified) resulting from revisions of this
’ standard (see 4.1.1). 1 - acquirer repeat
2 -card issuer
3 -card issuer repeat
4 Message structure 4- other
5 -other repeat
4.1 General 6-9 - reserved for IS0 use
Each message identified in this International 4.1.2 Message Repeats

Standard shall be constructed in the following
sequence: message type identifier, (see 4.1.1), one In 4.1.3, whenever a repeat message is identified, that
or two bit maps (see 4.2) and a series of data repeat message shall be identical to its original
elements in the order of the bit map representation message with the exception of the message type
(see 4.3). Clause 5 shows the circumstances when a identifier and, if necessary, date and time,
message shall (or may) be sent, and the relationship transmission and the message authentication code
between messages. data elements.
4.1.3 Message Type Identifier Descriptions e) Authorization notification messages shall be
used to inform the card issuer of an authorization
Table.6 identifies the message types supported for transaction which has completed at the point of
each message class. Each of the following message service. There is no response message to an
classes support a particular activity: authorization notification message.
4.1.3.1 Authorization message class f) The function code data element shall be used to
indicate the type of authorization required (see table 1)
An authorization is an approval or guarantee of funds
and whether the amount, transaction is accurate or
given by the card issuer to the acquirer. Authorization
estimated. If the final amount, transaction is
messages are not intended to permit the application
available the amount, transaction shall be an
of the approved transaction amount to the
accurate amount. If the final amount, transaction
cardholder’s account for billing or posting.
cannot be determined until later, the amount,
transaction shall be an estimated amount.
The following applies to all authorizations:
g) The following types of authorizations are
a) Authorization request messages shall be used defined:
when the transaction cannot complete at the point of
service until the response message is received i) Original authorization - the first or only
indicating the action to be taken. The use of an authorization used.
authorization request message does not imply that the
cardholder is present (e.g. telephone or mail order). ii) Replacement authorization - an authorization
used when a previous authorization was
b) An authorization request response message shall approved and a subsequent authorization is
be sent in response to an authorization request required to replace the previously authorized
message. Itindicates the approval or guarantee of amount because the amount of the transaction is
funds or the action to be taken as specified in the now greater or less.
action code data element.
iii) Resubmission authorization - an
c) Authorization advice messages shall be used to inform authorization used to reenter a previous
the card issuer of an authorization transaction which authorization that was denied or rejected.
has completed at the point of service.
iv) Supplementary authorization - an
d) An authorization advice response message shall authorization used when one or more previous
be sent in response to an authorization advice authorizations were approved and a further
message. An authorization advice response authorization is required for an additional
message indicates if the card issuer accepts or amount (see table 1).
rejects the transfer of financial liability.
Table 1 - Amounts in types of authorization messages
In request, advice and notification messages:
Authorization type Function code Amount, transaction Original amount, transaction
original 100,101 transaction amount ma
replacement 102,103 new amount originally authorized amount
resubmission 104,105 transaction amount --
I supplementary 1 106,107 I additional amount I sum of previous approvals, if I

I available
In response messages:
.
Authorization type Function code Amount, transaction Original amount, transaction
L
full approval a- transaction amount mm
part;al approval we approved amount originally requested amount
I decline/reject , -- , I zero I originally requested amount I

h) The following types of authorization decisions approval or guarantee of funds or the action to be
are defined: taken as specified in the action code data element.
i) Full approval - an authorization where the c) Financial advice messages shall be used to
response from the card issuer indicates approval inform the card issuer of a financial transaction
of the requested amount. which has completed at the point of service.
ii) Partial approval - an authorization where the d) A financial advice response message shall be
response from the card issuer indicates approval sent in response to a financial advice message. A
of an amount less than the originally requested financial advice response message indicates if the
amount (see table 1). card issuer accepts or rejects the transfer of
iii) Declined or rejected - an authorization financial liability.
where the request for approval is declined or the e) Financial notification messages shall be used to
authorization request or advice message is inform the card issuer of a financial transaction
rejected (see table 1). which has completed at the point of service. There is
no response message to a financial notification
Table 1 identifies the usage of amount, transaction message.
and original amount, transaction within these
authorization message types. f) The function code shall be used to indicate the
type of financial transaction and whether the
amount, transaction is the same or different from
4.1.3.2 Financial message class any previously authorized amount (see table 2).
A financial transaction permits the application of the g) The following types of financial transactions are
approved transaction amount to the cardholder’s defined:
account for billing or posting. i) Original - first or only financial transaction
used.
The following applies to all financial transactions:
ii) Previously authorized - a financial
a) Financial request messages shall be used when transaction used when an authorization was
the transaction cannot complete at the point of previously approved (see table 2).
service until the response message is received
indicating the action to be taken. The use of a iii) Resubmission - a financial transaction used
financial request message does not imply that the to reenter a previous financial transaction that
cardholder is present, (e.g. telephone or mail order). was denied or rejected (see table 2).
iv) Representment - a financial transaction

b) A financial request response message shall be
sent in response to a financial request message. A originated by an acquirer to partially or wholly
financial request response message indicates the recover funds charged back to the acquirer by a
card issuer in a chargeback (see table 2).
Table 2 -Amounts in types of financial transaction messages
In request, advice and notification messages:
I Financial type I Function cod2 I Amount, transaction I Original amount, transaction I

original 200 transaction amount --
previously 201,202 new amount originally authorized amount

authorized
resubmission 203,204 transaction amount
representment 205,2@6,207 transaction amount amount of chargeback
In response messages:
.
Financial type Function code Amount, transaction Original amount, transaction
full approval ww transaction amount -w
partial approval -w approved amount originally requested amount
decline/reject Be zero originally requested amount
5.
IS0 8583 : 1993 (E)
h) The following types of financial transaction d) A reversal advice response message shall be sent
decisions are defined: to a reversal advice message. A reversal advice shall
not be declined by the card issuer, except for
i) Full approval - a financial transaction where specific reasons as defined in clause A. 1.
the response from the card issuer indicates
approval of the originally requested amount (see e) A reversal shall not be reversed.
table 2).
f) The processing code in a reversal advice or
ii) Partial approval - a financial transaction notification shall be the same as presented in the
where the response from the card issuer original message. If the original transaction was a
indicates approval of an amount less than the debit, the reversal also indicates debit; if the original
originally requested amount (see table 2). transaction was a credit, the reversal also indicates
a credit.
iii) Declined or rejected - a financial transaction
where the request for approval is declined or the Table 3 shows the use of amounts in reversal
financial request or advice message is rejected messages:
(see table 2).
Table 3 -Amounts in reversal messages
Table 2 identifies the usage of amount, transaction
and original amount, transaction within these
financial message types.
, -. 4
4.1.3.3 File action message class Type of Amount, Original

reversal transaction amount,
A file action message shall be used to add, change, transaction
delete or replace a file or record. In addition, file action
full amount --
messages may be used to inquire into a file or perform
reversed
card administration (e.g., report lost or stolen cards).
The data record data element shall be used to convey
specific file action record or file information.
4.1.3.4 Reversal message class
A reversal shall be used to partially or completely II

nullify the effects of a previous financial or
authorization transaction. All reversals shall use the
14xx message series.
g) Only 1 lxx or 12xx transactions shall be reversed.
A reversal shall use the advice or notification h) Table 4 shows 12xx financial transactions that
messages since the activity has already occurred. The are not reversals :
following applies to all reversals:
Table 4 - Financial transactions
a) A reversal advice or notification shall be initiated
by an acquirer. Message reason codes are used to
indicate the reason for the reversal (see clause A.7). I I
b) The amount, transaction data element in a It I Irl
reversal
amount
advice or notification shall contain the
to be reversed and shall be less than or
II Function
I
Processing
code I
Function
code II
equal to the original amount as shown in table 3. II adjustment I 02,22 I 200 II
c) Whenever the acquirer times out waiting for a return 20 200

response to an authorization or financial transaction
.I representment 205, 206, 207
request or advice, a reversal advice or notification of
the transaction shall be sent (see 5.2.12).
4.1.3.5 Chargeback message class charged back. If the original transaction was a
debit, the chargeback shall also indicate a debit.
A chargeback shall be used to partially or completely If the original transaction was a credit, the
nullify a previous 12xx financial transaction. All chargeback shall also indicate a credit.
chargebacks shall use the 14xx message series.
ii) to cancel, either partially or completely, a
A chargeback shall be an advice or notification as the previous chargeback that was submitted in error,
activity has already occurred. the card issuer shall initiate a subsequent
chargeback containing one of the two
The following applies to all chargebacks: adjustment processing codes. If the original
transaction was a debit, this subsequent
a) A chargeback advice or notification shall only be chargeback shall indicate a credit. If the original
initiated by the card issuer. It shall be used when the transaction was a credit, this subsequent
card issuer determines that a customer dispute chargeback shall indicate a debit.
exists, or that an error or a violation of rules has been
committed. Message reason codes are used to indicate f) If the transaction that is being charged back
the reason for the chargeback (see clause A.7). requires a response, this response message shall be
sent before the chargeback is generated.
b) A chargeback advice or notification shall be
generated only if the original transaction had g) A card issuer may charge back an original
financial impact on the cardholder’s net position. A transaction plus any subsequent representment
chargeback shall not be used to cancel a balance submitted by the acquirer. A separate chargeback
inquiry, account transfer or an authorization message shall be used for each.
transaction.
h) This International Standard specifies no limits on
c) A chargeback advice response shall be sent in the timeframe or the number of chargebacks and
response to a chargeback advice message. A representments that may be exchanged between an
chargeback advice shall not be declined by the acquirer and card issuer.
receiver except for specific reasons as defined in
clause A.1 although the original transaction may be 4.1.3.6 Reconciliation message class
represented by the acquirer.
A reconciliation transaction provides financial totals
d) The amount, transaction data element in a between one acquirer and one card issuer. The
chargeback shall be the amount to be charged back following applies to all reconciliation messages:
and shall be less than or equal to the original
amount, transaction as shown in table 5 following: a) Reconciliation request messages request the
reconciliation totals (number and value).
Table 5 -Amounts in charge back messages
b) A reconciliation request response message shall
be sent in response to a reconciliation request
message. A reconciliation request response
Type of Amount, Original amount, message shall contain the requested totals, if
chargeback transaction transaction available. The totals contained in a reconciliation
request response message shall be used to indicate
full amount charged -w
back the originating institution’s position as either
acquirer or card issuer (but not both) as defined by
partial amount charged original the message type identifier.
back transaction
amount c) Reconciliation request response messages shall
indicate one of the following results:
i) Totals provided - all amounts and number

data elements shall be returned with the values
e) The processing code in a chargeback may be from the institution sending the reconciliation
used to indicate an adjustment where the card request response message.
issuer corrects a chargeback, partially or
ii) Totals not available - all amount and number
completely, that was submitted in error. All card
data elements shall be returned with zero values.
issuer initiated adjustments are chargeback (14~~)
transactions. The processing code in a chargeback d) Reconciliation advice messages request the
may differ from the value in the original confirmation of totals (number and value). The
transaction.The processing code used in a totals contained in a reconciliation advice message
chargeback shall be selected as follows: indicates an originating institution’s position as
either an acquirer or card issuer (but not both) as
i) to charge back a 12xx financial transaction, the
defined by the message type identifier.
chargeback shall contain the same processing
code value as the transaction that is being
7
IS0 8583 : 1993 (E)
e) A reconciliation advice response message shall I) Reconciliation in multiple currencies shall use a
be sent in response to a reconciliation advice separate reconciliation transaction for each
message. currency.
f) Reconciliation advice response m essages shall

4.1.3.7 Administrative message class
indicate one of th 18following results:
Administrative messages shall be used when two
i) Reconciled, in balance - only the amount, net
institutions have identified a need for the exchange of
reconciliation data element shall be returned in
information e.g., retrieval requests.
the reconciliation advice response message.
ii) Reconciled, out of balance - all amount and 4.1.3.8 Fee collection message class
number data elements shall be returned with the Fee collection messages shall be used to collect or
values from the institution sending the
disburse miscellaneous service fees. All fee collection
reconciliation advice response message. messages shall use the 17xx messages series.
iii) Totals not available-all amount and number
The following applies to all fee collection messages:
data elements shall be returned with zero values.
g) Reconciliation notification messages shall be a) Fee collection messages may be in either directi on;
used to provide totals (number and value). A acquirer to card issuer or card issu er to acquirer.
response message shall not be sent.
b) A fee collection message shall not be declined by
h) Two types of reconciliation transactions are the receiver except for specific reasons as defined in
defined: clause A. 1.
i) A checkpoint reconciliation transaction shall be c) Fee collection messages have a financial impact
indicated by the function code “501” or “503”. A and affect reconciliation totals (see table 11). They
checkpoint reconciliation period shall be shall not affect a cardholder account.
identified with the reconciliation indicator. The
date, reconciliation remains unchanged in a d) To cancel, either partially or completely, a
checkpoint reconciliation. previous fee collection transaction that was
submitted in error, a subsequent fee collection
ii) A final reconciliation shall be indicated by the transaction shall be sent using function code 701.
function code “500” or “502”. A final
reconciliation period shall be identified with the 4.1.3.9 Network management message class
date, reconciliation. A final reconciliation period
may contain any number of checkpoint Network management messages shall be used to
reconciliation periods. control the system security and operating condition of
the interchange network and may be initiated by any
The final reconciliation amounts shall be the sum interchanging The types of network
PaflY.
of all the financial amounts from the individual management messages are:
transactions identified with the same date,
reconciliation. The final reconciliation counts a) system condition messages - may be used to
shall be the number of transactions identified establish and report system availability and to give
with the same date, reconciliation. instructions pertaining to message handling during
i) A checkpoint reconciliation transaction may be periods of system unavailability. These messages
preceded by a network management transaction may be used as part of normal system initialization
(18~~) indicating checkpoint and the next or shutdown or as part of a failure recovery scheme.
reconciliation indicator. Any transaction initiated b) system security messages - may be used to
after completion of the network management control security aspects of the interchange system such
transaction indicating checkpoint shall contain the as key and password management and security alerts.
new reconciliation indicator (see 5.32, figure 2). These messages may be used as part of a security
j) A final reconciliation transaction may be procedure (e.g., automatic periodic key changes).
preceded by a network management transaction c) system accounting messages - may be used to
(18~~) indicating cutover and the new date, identify the end of a reconciliation period. These
reconciliation. Any transaction initiated after messages may be used as part of a reconciliation
completion of the network management transaction process (see 5.3.2). System accounting messages
indicating cutover shall contain the new date, shall not be declined by the receiver unless for
reco’nciliation (see 5.3.2, figure 2). specific reasons as defined in clause A.I.,
k) The calculation of amount, net reconciliation shall d) system audit control messages - may be used to
be achieved by netting the debit and credit amounts test integrity of interchange links and/or used as part
in the reconciliation message (see table 11). of an integrity check or failure recovery scheme.
8
IS0 8583 : 1993 (E)
Table 6 - Message type identifiers
MT! MESSAGE PURPOSE FROM TO USAGE
1100 authorization request requests approval for an acquirer issuer

authorization transaction
1101 authorization request repeat
1110 authorization request response carries the answer to an issuer acquirer shall be sent in
authorization request response to a 1100
or a 1101
1120 authorization advice advises of an authorization acquirer issuer

carried out on behalf of the card
issuer
1121 authorization advice repeat
1130 authorization advice response carries the answer to an issuer acquirer shall be sent in
authorization advice response to a 1120
or a 1121
1140 authorization notification notifies of an authorization action acquirer issuer
. il
MT1 MESSAGE PURPOSE FROM TO USAGE

.I
1200 financial request requests approval for a financial acquirer issuer -w
transaction
1201 financial request repeat
1210 financial request response carries the answer to a financial issuer acquirer shall be sent in
request response to a 1200
or a 1201
1220 financial advice advises of a financial transaction acquirer issuer

carried out on behalf of the card
issuer
1221 financial advice repeat
1230 financial advice response carries the answer to a financial issuer acquirer shall be sent in
advice response to a 1220
of a 1221
1240 financial notification notifies of a financial action acquirer issuer
9
608583:1993(E)
Table 6 - Message type identifiers, continued
MTI MESSAGE PURPOSE 1 FROM 1 TO I USAGE
file action request requests a file be updated sender receiver w-
file action request repeat
file action request response carries the answer to a file action receiver sender shall be sent in
request response to a 1304
or a 1305
1324 file action advice advises of what was added, sender receiver
deleted or replaced in a file or
record
1325 file action advice repeat
1334 file action advice response carries the answer to a file action rece iver sender shall be sent in
or a 1325
1344 file action notification notifies of a fiie action sender receiver
MTI MESSAGE PURPOSE FROM TO USAGE

b n
1420 reversal advice reverses an earlier authorization acquirer issuer --

or financial transaction
1421 reversal advice repeat
1430 reversal advice response carries the answer to a reversal issuer acquirer shall be sent in
or a 1421
1440 reversal notification nctifies of a reversal action acquirer issuer
1422 chargeback advice charges back an earlier financial issuer acquirer --

transaction
1423 chargeback advice repeat
1432 chargeback advice response carries the answer to a acquirer issuer shall be sent in
chargeback advice response to a 1422
or a 1423
1442 chargeback notification notifies of a chargeback action issuer acquirer
10
IS0 8583 : 1993 (El
\
L
1500 acquirer reconciliation request acquirer requests card issuer’s acquirer issuer --
totals (number and value) for the
last reconciliation period
1501 acquirer reconciliation request repeat
1510 acquirer reconciliation request carries card issuer’s totals issuer acquirer shall be sent in
response (number and value) in response response to a 1500
to a reconciliation request or a 1501
message
1520 acquirer reconciliation advice advises of acquirer’s totals acquirer issuer

(number and value) for the last
reconciliation period
1521 acquirer reconciliation advice repeat
1530 acquirer reconciliation advice carries the answer to a issuer acquirer shall be sent in
response reconciliation advice message response to a 1520
or a 1521
1540 acquirer reconciliation notification notifies the card issuer of the acquirer issuer
acquirer’s totals (number and
value) for the last reconciliation
period
1502 card issuer reconciliation request card issuer requests acquirer’s issuer acquirer
totals (number and value) for
the last reconciliation period
1503 card issuer reconciliation request repeat
1512 card issuer reconciliation request carries acquirer’s totals acquirer issuer shall be sent in
response (number and value) in response response to a 1502 or
to a reconciliation request a 1503
message
1522 card issuer reconciliation advice advises of card issuer’s totals issuer acquirer
(number and value) for the last
reconciliation period
1523 card issuer reconciliation advice repeat
1532 card issuer reconciliation advice carries the answer to a acquirer issuer shall be sent in
response reconciliation advice message response to a 1522 or
a 1523
1542 card issuer reconciliation notification notifies the acquirer of the card issuer acquirer
issuer’s totals (number and
value) for the last reconciliation
period
11

1604 administrative request requests information to support sender receiver --
the interchange network
1605 administrative request repeat
1614 administrative request response carries the answer to an receiver sender shall be sent in
administrative request response to a 1604 or a
1605
1624 administrative advice advises of information to support sender receiver

the interchange network
1625 administrative advice repeat
1634 administrative advice response carries the answer to an receiver sender shall be se71 in
administrative advice response to a 1624 or a
1625
16;4 administrative notification notifies of an administrative sender receiver

action
.
1720 acquirer fee collection advice advises of a service fee due to acquirer issuer ww
be couected
1721 acquirer fee collection advice repeat
1730 acquirer fee collection advice carries the answer to an acquirer issuer acquirer shall be sent in
response fee collection advice response to a 1720
or a 1721
1740 acquirer fee collection notification notifies of a service fee due to be acquirer issuer
collected
1722 issuer fee co lection advice advises of a service fee due to issuer acquirer
be collected
1723 issuer fee co lection advice repeat
1732 issuer fee co llection advice response carries the answer to an issuer acquirer issuer shall be sent in
fee collection advice response to a 1722
or a 1723
1742 issuer fee collection notification notifies of a service fee due to be issuer acquirer
collected
12
IS0 8583 : 1993 (E)
Table 6 - Message type identifiers, concluded
MTI MESSAGE PURPOSE FROM TO ,,,,,I
1804 network management request requests a network management sender receiver

activity
1805 network rnanagement request repeat
1814 network management request carries the answer to a network receiver sender shall be sent in
response management request response to a 1804
or a 1805
1824 network management advice advises of a network sender receiver

management activity
1825 network management advice repeat
1834 network management advice carries the answer to a network receiver sender shall be sent in
response management advice response to a 1824
or a 1825
1844 network management notification notifies of a network sender receiver

management action
4.2 Bit maps The primary bit map (bits 1-64) shall always be
present, and the most frequently used data elements
The second message component is one or two are indexed from these bit positions. Infrequently
bit maps each consisting of 64 bits. Each bit used data elements are indexed from the secondary
signifies the presence (1) or the absence (0) in bit map (bits 65-128). The presence of the secondary
the message of the data element associated with bit map shall be signified by a “1” in bit 01 of the
that particular bit. primary bit map (see figure 1).
Bit map primary only

data elements
lo I< >I
Bit position: (64)
Bit map primary and secondary
data elemc.nts
11 lo I<
I 4
1
Bit position: WI (6w----- (128)
Figure 1 - Bit maps
13
IS0 8583 I 1993 (E)
Table 7A shows: ans = alphabetic, numeric and special characters
a) the data element assignment to each bit; MM = Month, 01 through 12
b) the data element length, format and attribute DD = Day, 01 through 31

specification as outlined in 4.3 and in the legend
YY = Year, 00 through 99
preceding the table.
hh = Hour, 00 through 23
Table 79 shows:
mm = Minute, 00 through 59
a) the mandatory or conditional presence
ss = Second, 00 through 59
specification for each message type identifier. “M”
(mandatory) signifies that the data element is LL = length of variable data element that follows,
required in that message. “ME” (mandatory echo) 01 through 99
signifies the contents shall be returned unaltered in
a response message. LLL = length of variable data element that follows,
001 through 999
b) the conditional status, shown as “nn” which
referencestable8. lfthecondition identified in table8 VAR = variable length data element
applies, then the data element shall be present, 3 = fixed length of three characters
otherwise its inclusion in a message is subject to
bilateral agreement. ..I7 = variable length up to maximum 17
characters. All variable length fields shall in
Nothing in table 79 prohibits the use of any data addition contain two or three positions at the
element within any message. Messages may include beginning of the data element to identify the
additional data elements to those specified as number of positions following to the end of
mandatory and/or conditional. The use of these that data element.
additional data elements in a message is subject to x = “C” for credit, “D” for debit and shall always
bilateral agreement. be associated with a numeric amount data
element, i.e., x+ n 16 in amount, net
Legend for abbreviations used under attribute in reconciliation means prefix “c” or “D” and 16 digits
Tables 7A and 9 (see IS0 7372): of amount, net reconciliation.
a = alphabetical characters, A through Z and a
through z b = binary representation of data
n = numeric digits, 0 through 9 Z = Tracks 2 and 3 code set as defined in IS0 4909
and IS0 7813.
P = pad character, space
S = special characters NOTE - All fixed length “n” data elements are assumed to be
right justified with leading zeroes. All other fixed length data
an = alphabetic and numeric characters elements are left justified with trailing spaces. In all “b” data
as = alphabetic and special characters elements, blocks of 8 bits are assumed to be left justified with
trailing zeroes.
ns = numeric and special characters
All data elements are counted from left to right, i.e. the
anp = alphabetic, numeric and space leftmost position is num ber 1.
(pad)characters
IS0 8583 : 1993 (EI
Table 7A - Bit maps (in numerical order)
Bit Data Element Name Format Attribute

1
1 (see 4.2 for usage) I I b8 ~-~
2 primary account number LLVAR n..l9
3 processing code n6
4 amount, transaction I 1 n 12
5 amount, reconciliation I n 12
6 amount, cardholder billing I n 12
7 date and time, transmission MMDDhhmmss n 10
8 amount, cardholder billing fee n8
9 conversion rate, reconciliation n8
IO conversion rate, cardholder billing I I n8

I’ 11 systems trace audit number n6
II 12 I date and time, local transaction I YYMMDDhhmmss I n 12
II 13 I date, effective I YYMM I n4
14 date, expiration YYMM n4
15 date, settlement YYMMDD n6
16 date, conversion
17 date, capture
I’ 18 merchant type n4
II country code, acquiring institution I I n3
20 country code, primary account number I

I I
I n3
21 country code, forwarding institution n3
II 22 I point of service data code I I an 12
23 card sequence number n3
24 function code n3
25 message reason code n4
26 card acceptor business code n4
27 approval code length nl
28 date, reconciliation YYMMDD n6
II 29 I reconciliation indicator I I n3
I’ 30 amounts, original n 24
31 acquirer reference data LLVAR ans.99
15
IS0 8583 : 1993 (E)
Table 7A - Bit maps (in numerical order), continued
Data Element Name Forr nat Attribute
32 acquirer institution identification code I LLVAR I n..ll
t- 33 forwarding institution identification code I LLVAR I n..ll
34 primary account number, extended LLVAR ns..28

r
35 track 2 data LLVAR z.37
r
36 track 3 data LLLVAR 2.104
37 retrieval reference number anp 12
il 38 approval code I Ianp 6
II 39 action code I I n3
L
40 service code I I n3
41 card acceptor terminal identification I I ans 8
,
42 card acceptor identification code I I ans 15
r
43 card acceptor name/location . / LLVAR I ans..99
\
44 additional response data I LLVAR I ans..99
45 track 1 data I LLVAR I ans. .76
46 amounts, fees I LLLVAR I aw.204
47 additional data - national LLLVAR ans..999

--
i
I 48 additional data - private LLLVAR ! ans..999
1
i
currency code, transaction a 3 0: n 3
currency code, reconciliation a3orn3
currency code, cardholder billing a3orn3
personal identification number (PIN) data b8
security related control information LLVAR b..48
amounts, additional LLLVAR ans.. 120
F 55
56
integrated circuit card system related data
original data elements
authorization life cycle code

LLLVAR
LLVAR
b. ,255
n..35
n3
I 58 authorizing agent institution identification code LLVAR n..ll
transport data LLLVAR ans..999
I 60-61 reserved for national use LLLVAR ans. ,999’
reserved for private use LLLVAR ans..999’
message authentication code field b8
reserved for IS0 use 1=8
16
IS0 8583 : 1993 (E)
Table 7A - Bit maps (in numerical order), continued
66 amounts, original fees LLLVAR ans. ,204

1
67 extended payment data n2
I
68 country code, receiving institution n3
69 country code, settlement institution n3
70 country code, authorizing agent institution n3
71 message number n8
r
72 data record LL! VAR ans. .999
73 date, action YYMMDD n6
74 credits, number n 10
75 credits, reversal number n 1C
76 debits, number n 10
77 debits, reversal number n 10
78 transfer, number n 10
79 transfer, reversal number n 10
80 inquiries, number n 10
81 authorizations, number n 10
82 inquiries, reversal number n 70
83 payments, number n 10
I
84 payments, reversal number n 10
II I
85 fee collections, number I I n 10
II 86 I
credits, amount I I n 16
87 credits, reversal amount n 16
88 debits, amount n 16
89 debits, reversal amount n 16
90 authorizations, reversal number n 10
91 country code, transaction destination institution n3
92 country code, transaction originator institution n3
93 transaction destination institution identification code LLVAR n..ll

L
94 transaction originator institution identification code LLVAR n.11
95 card issuer reference data LLVAR ans. .99
96 key management data LLLVAR b. ,999
17
IS0 8583 t 1993 (E)
Table 7A - Bit maps (in numerical order), concluded
97 I
amount, net reconciliation I I
x+n16
98 I
payee I
ans 25
99 I
settlement institution identification code ILLVAR I
an..1 1
100 I
receiving institution identification code ILLVAR I
n..ll
I
101 file name ILLVAR I
ans..l7
102 I
account identification 1 ILLVAR I
ans..28
103 I
account identification 2 ILLVAR I
ans. .28
104 I
transaction description ILLLVAR I
ans..lOO
I
1OS credits, chargeback amount I I
n 16
106 I
debits, chargeback amount I I
n 16
107 I
credits, chargeback number I I
n 10
108 I
debits, chargeback number I I
n 10
109 I
credits, fee amounts ILLVAR I
ans..84
110 I
debits, fee amounts ILLVAR I
ans..84
11 l-1 15 reserved for IS0 use LLLVAR ans..999l
116-l 22 reserved for national use LLLVAR ans..999 1
123-127 reserved for private use LLLVAR ans..999l
128 message authentication code field b8
’ Attribute for each bit.

ISO8583:1993(E)
Table 78 - Bit maps (by message type)
AUTHORIZATION MESSAGES I MESSAGE TYPE IDENTIFIERS

BIT DATA ELEMENT NAME
1 I (see 4.2 for usage) I

2 primary account number 07 16 07 16 07
3 processing code M 27 M 27 M
4 amount, transaction 26 26 26 26 26
11 systems trace audit number M ME M ME M
,
12 date and time, local transaction M ME M ME M
13 date, effective 02 02 02
i 14 1 date, expiration I 02 I I 02 I I 02
22 point of service data code M M ! M
23 card sequence number 02 02 02
24 function code M M M
26 card acceptor business code M M M
27 approval code length 18
28 date, reconciliation 12 12 12
29 I reconciliation indicator I 114 I I 14 I 23

30 I amounts, original I 08 I 21 I 08 I I 08
32 acquiring institution identification code M
forwarding institution identification code 10 10 10 10 10

I
34 primary account number, extended 15 16 15 16 15
35 track 2 data 06 06 06
36 I track 3 data ~~~
I 06 I I 06 I I 06
39 1 action code -7 I M I M IM IM
40 1 service code I 02 I I 02 I I 02
41 card acceptor terminal identification 16 16
42 card acceptor identification code 16 16
45 track 1 data 06 06 06
46 amounts, fees 01 01 01 01 01
49 currency code, transaction 26 l6 26 16 26
58 authorizing agent institution identification code 20 20 20
59 transport data 16 16
100 receiving institution identification code 19 19 19 19 19
19
Table 7B - Bit maps (by message type), continued
I
FINANCIAL MESSAGES I MESSAGE TYPE I IENTIFIERS
DATA ELEMENT NAME 1200 1210 1220 1230 1240
1201 I 1221
1 (see 4.2 for usage)
12 ~primary account number 07 16 07
L
13 processing code M 27 M
I
4 amount, transaction M M M M M
I
amount, reconciliation 05 05 05
9 conversion rate, reconciliation 05 05 05
10 conversion rate, cardholder billing I 04 I 04 I 04 04 04
11 systems tract audit number I M I ME I M ME M
12 date and time, local transaction I M I ME I M ME M
13 date, effective I 02 I 02 02
14 date, expiration I 02 I 02 * 02
16 date, conversion 05 05 05
s
17 date, capture 22 22
22 point of service data code M M M
~23 card sequence number 02 02 02
, 24 function code IM M M
' 26
c
card acceptor business code IM I I M IM I
27 approval code length I 18 I I
j 28 date, reconciliation I I 12 I 12 I 12 I
/ 29 reconciliation indicator I I 14 I 14 23
30 amounts, original I 08 I 21 I 08 08
32 acquiring institution identification code I M I ME IM ME M
33 fowarding institution identification code 10 10 I 10 10 10
34 primary account number, extended 15 16 I 15 16 15
35 track 2 data 06 I 06 06
I
36 track 3 data 06 I 06 06
37 retrieval reference number 16 I 16
39 action code M M
40 sewice code 02
41 card acceptor terminal identification 16 I
42 card acceptor identification code 16 I
43 card acceptor name/location M IM
45 track 1 data 06 I 06
46 amounts, fees 01 01 I 01
L
49 currency code, transaction M ME IM
~50 currency code, reconciliation 05 I
51 currency code, cardholder billing 04 04 I 04
58 authorizing agent institution identification code 20 I 20
59 transport data 16
100 receiving institution identification code 19 19 19
20
ISO8583:1993(E)
FILE ACTION MESSAGES MESSAGE TYPE IDENTIFIERS

/
BIT DATA ELEMENT NAME 1304 1314 1324 1334 1344
1305 1325
I
2 primary account number pppp[-28 1 16 1 iii 16 28
11 systems trace audit number -----~(ME[r ME M
12 date and time, local transaction I M I ME I M ME M
24 function code IM I IM M
25 message reason code I 28 I I 28 28
33 forwarding institution identification code ~ 10 10 10 10 10
~ 39 action code M M M M
59 transport data 16 16
71 message number 16 16
72 data record 29 29 29
93 transaction destination institution identification code IM I ME I M ME M
94 transaction originator institution identification code I M I-Iii ---rir- ME M
L
100 receiving institution identification code I 19 m]pim 19 19
101 file name 29 29 29
IS0 8583 : 1993 (E)
REVERSAL MESSAGES I MESSAGETYPEIDENTIFIERS

BIT DATA ELEMENT NAME 1420 1430 1440
1421
I
2 primary account number 07 16 07
3 processing code 03 16 03
1
4 amount, transaction M M M
5 amount, reconciliation 05 05
9 conversion rate, reconciliation 05 05
10 conversion rate, cardholder billing 04 04 04
11 systems trace audit number M ME M
12 date and time, local transaction M ME M
16 date, conversion 05 05
24 function code M M
28 date, reconciliation 12 12
29 reconciliation indicator 14 23
30 amounts, original 08 08
32 acquiring institution identification code M ME M
33 forwarding institution identification code 10 10 10
34 primary account number, extended 15 16 15
38 approval code 17 17
39 action code M M
41 card acceptor terminal identification 16
42 card acceptor identification code 16
46 amounts, fees 01 01 01
49 currency code, transaction 03 16 03
50 currency code, reconciliation 05 05
51 currency code, cardholder billing 04 04 04
56 original data elements M M
58 authorizing agent institution identification code 17 17
A
94 transaction-originator institution identification code 09 16 09
IS0 8583 : 1993 (E)
CHARGEBACK MESSAGES dESSAG ETYPE IDENTIFIERS
1
BIT
(see 4.2 for usage)

DATA ELEMENT NAME 1422
1423
1432 1442
I -I
2 1 P’rlmary account number 07 16 07 I
3 I processing code M ME M I
4 -1amount, transaction M M M I
5 I amount, reconciliation 05
9 I conversion rate, reconciliation 05
y[<ystemstrace-kdit number M ME
12 I date and time, local transaction M ME M I
16 1 date, conversion 05
24 1 function code M
28 1 date, reconciliation 12
2g I reconciliation (ndicator 14
30 I amounts, original 08
32 acquiring institution identification code M ME
33 forwarding institution identification code 10 10
34 primary account number, extended 15 16
37 retrieval reference number 17
39 action code M
46 amounts, fees 01 01
49 currency code, transaction 03 16
50 currency code, reconciliation 05
56 original data elements M
94 transaction originator institution identification code 11 16
100 receiving institution identification code 19 19
-
IS0 8583 : 1993 (E)
RECONCILIATION MESSAGES MESSAG : TYPE IENTIFIERS
BIT DATA ELEMENT NAME 1500 1510 1520

1501 1521
1502 1512 1522
1503 1523
2 primary account number M I ME M ME I M
11 systems trace audit number M I ME M ME I M
12 date and time, local transaction M I ME M ME I M
24 function code M I M IM
28 date, reconciliation M I ME M ME IM
29 reconciliation indicator 23 I 16 23 16 I 23
32 acquiring institution identification code M I ME M ME IM
33 forwarding institution identification code 10 I 10 10 10 I 10
39 ~ action code IM M I
50 currency code, reconciliation M I ME M ME IM
59 transport data I 16 16 I
74 credits, number IM M 13 IM
75 credits, reversal number IM M 13 I M
76 debits, number I M M 13 I M
77 debits, reversal number IM M 13 I M
86 credits, amount IM M 13 IM
87 credits, reversal amount IM M 13 IM
88 debits, amount IM M 13 IM
89 debits, reversal amount IM M 13 IM
97 amount, net reconciliation IM M M IM
100 receiving institution identification code 19 I 19 19 19 I 19
105 credits, chargeback amount I M M 13 IM
106 debits, chargeback amount IM M 13 IM
107 credits, chargeback number IM M 13 IM
108 debits, chargeback number 13 IM
109 credits, fee amounts
110 debits, fee amounts
24
I
ISO8583:1993 (El
ADMINISTRATIVE MESSAGES MESSAGE TYPE IDENTIFIERS

BIT DATA ELEMENT NAME 1604 1614 1624 1634 1644
1605 1625
11 systems trace audit number IM ME M ME M
12 date and time, local transaction I M ME M ME M
24 function code IM M M
33 forwarding institution identification code I 10 10 10 10 10
39 action code M M M M
59 transport data I 16 16
72 data record IM M M
93 transaction destination institution identification code IM ME M ME M
94 transaction originator institution identification code IM ME M ME M
100 receiving institution identification code I 19 19 19 19 19
FEE COLLECTION MESSAGES MESSAGE TYPE IDENTIFIERS

BIT
1 1 (see 3.2 for usage)

DATA ELEMENT NAME
1
1722
1723 I I 1732 1742
2 primary account number IM I ME I M M I ME M

11 systems trace audit number IM I ME I M M I ME M
12 date and time, local transaction IM I ME I M M I ME M
24 function code I M I I M M I M
28 date, reconciliation I I 12 I 12 I 12 12
29 reconciliation indicator I I 14 I 23 I 14 23
32 acquiring institution identification code IM I ME IM M I ME M
33 forwarding institution identification code I 10 I 10 I 10
39 action code I IM IM
46 amounts, fees IM I ME IM
59 transport data I I 16 I
ISO8583:1993(E)
Table 7B - Bit maps (by message type), concluded
NE-WORK MANAGEMENT MESSAGES I MESSAGE TYPE IDENTIFIERS

DATA ELEMENT NAME 1 ;;;; 1 1814 1 ;W”, 1 1834 1 1844 1 1
1 1 (see 4.2 for usage) I I

~~
11 I systems trace audit number IM I ME I M IME I M I I
12 I date and time, local tlransaction IM I ME IM I ME IM I I
24 If unction code IM I IM I IM I I
28 1 date, reconciliation I 24 I 16 I 24 I 16 I 24 I I
29 -Ireconciliation indicator I 25 I 16 I 25 I 16 I 25 I I
33 1 forwarding institution identification code I 10 I 10 I 10 I 10 I 10 I I
39 I action code I IM IM IM IM I I
59 I transport data I I 16 I I 16 I I I
93 I transaction destination institution identification code I M IME I M IME I M I I
94 1 transaction originator institution identification code IM I ME I M I ME I M I I
100 I receiving institution identification code I 19 I 19 I 19 I 19 I 191 I
26
IS0 8583 : 1993 (E)
Table 8 - Conditions used in table 7B
Code Condition
SW
Optional
L
M Mandatory
ME Mandatory echo, shall echo the same data as the original message.
00 Reserved for IS0 use.
01 Mandatory if fees affect reconciliation.
II 02 I Mandatory if information is available and not present in the track 1, track 2 or track 3 data.
II 03 I Mandatory, shall contain the same data as the original authorization (1 lxx) or financial (12~~) message.
II 04 I Mandatory if amount, cardholder billing or amount, cardholder billing fee is present.
II I
II
05
06
Mandatory when the reconciliation
in the request or advice message.
and transaction
I Mandatory if track data is captured at the point of service.

currencies differ and this data element was not provided
II 07 I Mandatory if the primary account number conforms to IS0. 7812.
II I 08 Mandatory in a replacement transaction, previously authorized transaction, representment,

partial chargeback. Mandatory irl a supplementary authorization, if available.
partial reversal or
II 09 I Mandatory when the transaction originator institution is not the same as the acquiring institution.
II 10 I Mandatory when the forwarding institution is not the same as the institution originating the message.
II I 11 Mandatory when the transaction

PAN or PAN extended.
originator institution is not the same as the institution identified in either the
II I 12
13
Mandatory if transaction
advice message.
affects reconciliation and this data element was not provided in the request or
Mandatory if the reconciliation is not in balance; contains the value calculated by the institution sending the
reconciliation advice response.
14 Mandatory if the transaction affects reconciliation and checkpoint reconciliation is used and this data element
was not provided in the request or advice message.
15 Mandatory when the primary account number begins with “59” as defined in IS0 4909 and therefore has a
field separator.
16 Mandatory in a response message if the data element was present in the original request or advice message.
I If present, it shall contain the same data as the original message.
17 Mandatory in the advice/notification if the data element was present in the original authorization/ financial
request/advice notification message. If present, it shall contain the same data as the original message.
18 I Mandatory if the approval code is required to be less than six characters.
19 I Mandatory when the receiving institution is not the same as the final destination of the message.
20 Mandatory when the institution that processed (approved or denied) an authorization or financial transaction
is not the same institution identified in either the primary account number or the primary account number,
extended.
21 I Mandatory if a partial approval, declined or rejected transaction.
22 I Mandatory if different from date and time, local transaction.
23 1 Mandatory if transaction affects reconciliation and checkpoint reconciliation used.
24 I Mandatory if this message is used for cutover or checkpoint reconciliation.
25 I Mandatory if this message is used for checkpoint reconciliation.
26 I Mandatory for alI processing codes except for inquiry services, i.e., processing code 3xxxxx.
27 I Mandatory, shall echo the first two positions of the processing code in the original message.
28 I Mandatory if function code indicates card administration.
29 Mandatory if function code is other than card administration.
27
4.3 Data element directory The actual length of any given variable length data
element shall be provided in its fixed length prefix.
The third message component and its data content is
made up of series of data elements. Table 7B specifies The message structure does not preclude the use of
those data elements which are present, according to additional data elements in a message as required for
the message type identifier. national interchange or private use.
Messages are reconstructed using the bit map as The data elements in table 9 shall be used in the
index of data elements that are present. Some data messages specified in table 7B
elements are of fixed length; some of variable length.
28
Table 9 - Data element directory
Name Description Representation Bit

Account identification 1 A series of digits and/or characters used to identify a customer ans. ,28 102
account or relationship (e.g., for the “from” account). (see 4.4.1 and
4.4.5)
Account identification 2 A series of digits and/o r characters used to identify a customer ans..28 103
account or relationship (e.g., for the “to” account). (see 4.4.1 and
4.4.5)
Account type, additional Code used to describe the accounts affested. Contained in n2 54l
amounts amounts, additional data element (see 4.4.12)
Acquirer reference data Data supplied by an acquirer in an authorization or financial ans.99 31
request, advice or notification that may be required to be
provided in a subsequent transaction.
Acquiring institution Code identifying the acquirer. n.11 32
identification code (see 4.4.1, 4.4.4
and 4.4.16)
Action code A code which defines the action or to be taken as well as n3 39
the reason for taking this action. (see 4.4.7, 4.4.15
and A.l)
Additional data - national Reserved for national organizations to define data unique to ans. .999 47
country applications. (see 4.4.2)
The use of this
data element is
under the control
of national bodies.
Additional data - private Reserved for private data. ans..999 48
(see 4.4.2)
The use of this
data element is
determined by
bilateral
agreement.
Other data (e.g., a telephone number) required in response. ans. .99 44
(see 4.4.1)
Amount contained in the amounts, additional data element. x + n 12 54l
(see 4.4.8 and
4.4.12)
Amount, cardholder billing Amount billed to the cardholder in the currency of the cardholder n 12 6
account exclusive of cardholder billing fees. (see 4.4.8 and
4.4.13)
Amou nt, cardholder billing Fee to be bi lled to the cardhol der by the card issuing institution n8 8
fee in the same curren cy as amou nt, cardholder billing (see 4.4.8 and
4.4.13)
Amount, Amount of the fee within the fee type code. Contained in the x+ n8 46l
amounts, fees data element. (see 4.4.17)
Amount, fee total The sum amount of all fees of the fee type specified. Contained n 12 109l
in the credits, fee amounts and debits, fee amounts data (see 4.4.11 and llol
elements. 4.4.19)
Amount, net reconciliation The net value of all gross amounts. x + n 16 97
(see 4.4.8, and
4.4.11)
Amount, reconciliation Funds to be transferred between the acquirer and card issuer n 12 5
equal to the amount, transaction in the currency of reconciliation. (see 4.4.8 and
4.4.11)
Amount, reconciliation fee Fee to be transferred between the acquirer and card issuer equal x+n8 46l
to the amount, fee in the currency of reconciliation. Contained in (see 4.4.8, 4.4.11
the amounts, fees data element. and 4.4.17)
29
IS0 8583 : 1993 (E)
Table 9 - Data element director, continued
Description Representation Bit

Amount, transaction Funds requested by the cardholder in the local currency of the n 12 4
acquirer or source location of the transaction, exclusive of (see 4.4.8 and
amounts, fees. 4.4.11)
Amount type, additional Identifies the kind of amount contained in the amounts, additional n2 54l
amounts data element. (see 4.4.8, 4.4.12,
4.4.15 and A.2)
Amounts, additional Information on up to six amounts and related account data for and 20 54
which specific data elements have not been defined. (see 4.4.2, 4.4.8,
4.4.12 and 4.4.15)
Amounts, fees Fees associated with this transaction. ans. ,204 46
(see 4.4.2, 4.4.8,
4.4.11, 4.4.17,
4.4.18 and A.5)
Amounts, original The amount data elements from the original transaction (see n 24 30
Tables 1, 2, 3 and 5). (see 4.4.8 and
4.4.10)
Amounts, original fees The original amounts, fees necessary to perform a partial ans. ,204 66
reversal, partial chargeback or partial approval or to replace or (see 4.4.8, 4.4.11,
supplement a previously authorized transaction. 4.4.18 and A.5)
Approval code Code assigned by the authorizing institution indicating approval. anp 6 38
Approval code length Maximum length of the approval code which the acquirer may nl 27
accommodate. The card issuer or agent shall limit the approval
code to this length.
Authorization life cycle code A value in calendar days, hours or minutes which defines the n3 57
time period for which the acquirer is requesting guarantee of (see A.3 and
funds, or that the card issuer shall guarantee funds for a financial 4.4.15)
transaction which may follow.
Authorizations, number The sum number of all authorization transactions. n 10 81
(see 4.4.11)
Authorizations, reversal The sum number of all reversal transactions processed where the n 10 90
number message type identifier in the original data elements indicated an
authorization (1xxx).
Authorizing agent institution Code identifying the authorizing agent institution. n.11 58
and 4.4.16)
Card acceptor business code Code classifying the type of b‘usiness being done by the card n4 26
acceptor for this transaction. (see A.4 and
4.4.15)
Card acceptor identification Code identifying the card acceptor. ans 15 42
code
Card acceptor name/location The name and location of the card acceptor as known to the ans. .99 43
cardholde (see 4.4.1 and
4.4.9)
Card acceptor terminal Unique code identifying a terminal at the card acceptor location. ans 8 41
identification
Card issuer reference data Data supplied by a card issuer in an authorization or financial 95
response message, or in a chargeback, that may be required to
be provided by the acquirer in subsequent transactions.
Card sequence number A number distinguishing between separate cards with the same n3 23
primary account number or primary account number extended
(see IS0 4909).
30
IS0 8583 :, 1993 (EI
Table 9 - Data element directory, continued

Conversion rate, cardholder The factor used in the conversion from transaction to cardholder n8 10
billing billing amount. The amount, transaction is multiplied by (see 4.4.14)
conversion rate, cardholder billing to determine amount,
cardholder billing.
Conversion rate, fee The factor used in the conversion from fee amount to n8 46l
reconciliation fee amount. The amount, fee is multiplied by (see 4.4.14 and
conversion rate, fee to determine the amount, reconciliation fee. 4.4.17)
Contained in the amounts, fees data element.
Conversion rate, The factor used in the conversion from transaction to n8 9
reconciliation reconciliation amount. The amount, transaction is multiplied by (see 4.4.14)
conversion rate, reconciliation to determine the amount,
reconciliation.
Country code, acquiring The code of the country where the acquiring institution is located n3 19
institution (see IS0 3166). (see 4.4.4)
Country code, authorizing The code of the country where the authorizing agent institution is n3 70
agent institution located (see 3166). (see 4.4.4)
Country code forwarding The code of the country where forwarding institution is located n3 21
institution (see IS0 3166). (see 4.4.4)
Country code, primary The code of the country where the card issuing institution is n3 20
account number(PAN) located (see IS0 3166). (see 4.4.4)
Country code, receiving The code of the country where receiving institution is located (see n3 68
institution IS0 3166). (see 4.4.4)
Country code , settlement The code of the country where settlement institution is located n3 69
institutio n (see IS0 3166). (see 4.4.4)
Country code, transaction The code of the country where the transaction destination n3 91
destination institution located (see IS0 3166). (see 4.4.4)
Country code, transaction The code of the country where the transaction origi n3 92
originator institution located (see IS0 3166). (see 4.4.4)
Credits, amount The sum amount of amount, transaction in all financial n 16 86
transactions exclusive of any fees where positions 1-2 of the (see 4.4.8 and
processing code in the financial transaction indicated a credit 4.4.11)
(20-29).
Credits, chargeback amount The sum amount of amount, transaction in all chargeback n 16 105
processing code in the chargeback transaction indicated a debit 4.4.11)
(00-l 9).
Credits, chargeback number The sum number of all chargeback transactions where positions n 10 107
1-2 of the processing code in the chargeback transaction (see 4.4.11)
indicated a debit (00-l 9).
Credits, fee amounts The sum amount of amounts, fees in all authorization, financial ans.. 84 109
reversal and fee collection transactions where the amount, fee, x, (see 4.4.8, 4.4.11,
indicated a c redit, “C”. 4.4.19 and A.5)
Credits, number The sum number of all financial transactions where positions 1-2 n 10 74
of the processing code in the financial transaction indicated a (see 4.4.11)
credit (20-29).
Credits, reversal amount The sum amount of amount, transaction of all reversal n 16 87
processing code in the reversal transaction indicated a debit 4.4.11)
(Oil-19).
Credits, reversal number n 10 75
(see 4.4.11)
31
IS0 18583:1993(E)

Currency code, additional Code defining the currency of the amount contained in the a3orn3 54l
amounts amou nts, additional data element (see IS0 4217). (see 4.4.8 and
4.4.12)
Currency code, cardholder Code defining currency of amount, cardholder billing and a3orn3 51
billing amount, cardholder billing fee (see IS0 4217).
Currency code, fee Code defining currency of amount, fee contained in the amounts, a3orn3 46l
fees data element (see IS0 4217). (see 4.4.17)
Currency code, reconciliation Code defining currency of reconciliation (see IS0 4217). a3orn3 50
(see 4.4.11)
Currency code, reconciliation Code defining the currency of amount, reconciliation fee in the a3orn3 46l
fee amounts, fees data element (see IS0 4217). (see 4.4.17)
Currency code, transaction The local currency of the acquirer or source location of the a3orn3 49
transaction. Currency used in amount, transaction (see IS0
4217).
Data record Other data required to be passed to support an administrative or ans. ,999 72
file action message. (see 4.4.2)
Date, action A date for a future action or a specific date such as a birth date. n6 73
YYMMDD
Date and time, local The local year, month, day and time the transaction takes place n 12 12
transaction at the card acceptor location in authorization and financial YYMMDDhhmmss
messages.
In file action, reversal, chargeback, reconciliation, administrative,

fee collection and network management transactions, it is the
year, month, day and time set by the initiator of the first message
in the transaction.
Date and time, transmission Date and time this message is sent by the message initiator. To n 10 7’
be expressed in Coordinated Universal Time (UTC) (see IS0 MMD Dhhmmss
8601); formerly known as Greenwich Mean Time (GMT).
Date, capture The month and day the transaction data was processed by the n4 17
acquirer. MMDD
Date, conversion The month and day the conversion rate is effective tc convert the n4 16
transaction amount from the original to reconciliation currency. MMDD
Date, effective The year and month in which the card becomes effective. n4 13
YYMM
Date, expiration The year and month after which the card expires. n4 14
YYMM
Date, reconciliation The year, month and day for which financial totals are reconciled n6 28
between the acquirer and the card issuer. YYMMDD
Date, settlement The year, month and day for which funds shall be transferred n6 15
between acquirer and card issuer. YYMMDD
Debits, amount The sum amount of amount, transaction in all financial n 16 88
processing code in the financial transaction indicated a debit 4.4.11)
(00-l 9).
Debits, chargeback amount The sum amount of amount, transaction in all chargeback n 16 106
processing code in the chargeback transaction indicated a credit 4.4.11)
Debits, chargeback number The sum number of all chargeback transactions where positions n 10 108
1-2 of the processing code in the chargeback transaction (see 4.4.11)
indicated a credit (20-29).
32
IS0 8583 : 1993 (E)

Debits, fee amounts The sum amount of amount, fee in all authorization, financial, ans.. 84 110
reversal and fee collection messages where the amount, fee, x, (see 4.4.8, 4.4.11,
indicated a debit, “D”. 4.4.19 and A.5)
Debits, number The sum number of all financial transactions where positions 1-2 n 10 76
of the processing code in the financial transaction indicated a (see 4.4.11)
debit (00-l 9).
Debits, reversal amount The sum amount of amount, transaction of all reversal n 16 89
transactions exclusive of any fees where positions l-2 of the (see 4.4.8 and
processing code in the reversal transaction indicated a credit 4.4.11)
(20-29).
Debits, reversal number The sum number of all reversal transactions where positions l-2 n 10 77
of the processing code in the reversal transaction indicated a (see 4.4.11)
credit (20-29).
Extended payment data Number of months that the cardholder prefers to pay for this item n2 67
if permitted by the card issuer.
Fee collections, number The sum number of all fee collection transactions. n 10 85
(see 4.4.11)
Fee type code Code indicating the type of fee. Contained in the data elements n2 46l
amounts, fees; credits, fee amounts; and debits, fee amounts. (see 4.4.15, 4.4.17, 109 i
4.4.19 and A.5) and
IlO
File name The actual or abbreviated name of the file being accessed. ans.17 101
(see 4.4.1)
Forwarding institution Code identifying the fowarding institution. n..ll 33
and 4.4.16)
Function code Code indicating the specific purpose of the message within its n3 24
message class. (see A.6 and
4.4.15)
Inquiries, number The sum number of all authorization transactions processed n 10 80
where positions l-2 of the processing code in the authorization (see 4.4.11)
transaction indicated an inquiry (30-39).
Inquiries, reversal number The sum number of all reversal transactions processed where n 10 82
positions l-2 of the processing code in the reversal transaction (see 4.4.11)
indicated an inquiry (30-39).
Integrated circuit card (ICC) Contains data related to integrated circuit card systems. The b..255 55
system related data structure of this data element is described in IS0 10202. (see 4.4.3)
Key management data Contains data related to key management. b..999 96
(see 4.4.3)
Merchant type The classification of the merchant’s type of business product or n4 18
service. Codes to be developed within each country.
Message authentication code Used to validate the source and the text of the message between b8 64 or
(MAC) field the sender and receiver. (see 4.4.3) 128
The last bit position within any bit map shall be reserved for the
MAC field data element. If authentication is to be used on a
message, the MAC field data element shall be represented by the
final bit in the final bit map of that message. The final bit of the
previous bit map shall contain zero, i.e., only one MAC field data
element per message and the MAC field data element shall be
the last data element of the message. (See IS0 9807.)
A number assigned to a message by the transaction originator n8 71
and used to monitor the integrity and continuity of the data being
exchanged.
33
IS0 8583 : 1993 (El

Message reason code Provides the receiver of a request, advice or notification message n4 25
with the reason, or purpose, of that message. (see A.7 and
4.4.15)
For original authorizations and financial transactions identifies
why the type of message was sent (e.g., why an advice versus a
request); for other messages, states why this action was taken.
Number, fee total The count of all fees of the fee type specified. Contained in the n 10 109l
credits, fee amounts and debits, fee amounts data elments. (see 4.4.19) or
llol
Original acquiring institution The acquiring instituti on identification code of the original n..ll 56l
identification code financial transaction. Contained in the original data elements. (see 4.4.1, 4.4.4,
4.4.6 and 4.4.16)
Original amount, fee The origin al amount of the fee in a reversal, c harg eback or partial x+n8 66l
approval. Contained in the amounts, original fees data element. (see 4.4.8, 4.4.11
and 4.4.18)
Original amou nt, The original amount of the transaction expressed in the n 12 301
reconciliation reconciliation currency (see tables 2,3 and 5). Contained in the (see 4.4.8, 4.4.10
amounts, original data element. and 4.4.11)
Original amount, The original amount of the fee expressed in the reconciliation x+n8
reconciliation fee currency (see tables 2,3 and 5). Contained in the amounts, (see 4.4.8, 4.4.11
original fees data element. and 4.4.18)
Original amount, transaction The original amount of the transaction (see Table 2, 3 and 5). n 12
Contained in the amounts, original data element. (see 4.4.8 and
4.4.10)
Original conversion rate, fee The factor used in the conversion from transaction to n8
reconciliation fee amount. The original amount fee is multiplied (see 4.4.14 and
by original conversion rate, fee to determine original amount, 4.4.18)
reconciliation fee. Contained in the amounts, original fees data
element.
Original currency code, fee Code defining cu rrency of original amount, fee. Contained in the a3orn3
amounts, original fees data element (see IS0 42 17). (see 4.4.18)
Original currency code, Code defining currency of original amount, reconciliation fee. a3orn3
reconciliation fee Contained in the amounts, original fees data element (see IS0 (see 4.4.18)
4217).
Original data elements The data elements contained in the original message, intended n..35 56
for transaction matching. (see 4.4.1 and
4.4.6)
Original date and time, local The local date and time of the original transaction. Contained in n 12 56l
transaction the original data elements. (see 4.4.6)
Original fee type code Code used to indicate the type of fee. Contained in the original n2
amounts, fees data element. (see 4.4.15, 4.4.18
and A.5)
Original message type The message type identifier of the original transaction. n4 56’
identifier Contained in the original data elements. (see 4.4.6)
Original system trace audit The system trace audit number of the original transaction. 56l
number Contained i n the original data elements. (see 4.4.6)
Payee The third party beneficiary in a financial transaction where ans 25 98
processing code indicates a payment (50-59).
Payments, number The sum number of all financial transactions processed where n 10 83
positions l-2 of the processing code in the financial transaction (See 4.4.11)
indicated a payment (50-59).
Payments, reversal number The sum number of all reversal transactions processed where n 10
positions l-2 of the processing code in the reversal transaction (see 4.4.11)
indicated a payment (50-59).
IS0 8583 : 1993 (E)

Personal identification Used to the cardholder at the point of setvice. (See IS0 b8 52
number (PIN) data 9564-l .) (see 4.4.3)
Point of service data code A series of codes intended to identify termina ,I capability, terminal an 12 22
environment and presentation security data. It shall be used to (see A.8 and
indicate specific conditions that are (or were) present at the time 4.4.15)
a transaction took place at the point of service and/or when the
transaction has been initiated.
Primary account number A series of digits used to identify ac ustomer account or m.19 2
(PAN) relationship. (see 4.4.1 and
4.4.5)
In reconciliation or fee collection messages this data element
contains the card issuer’s institution identification number only.
(See IS0 7812.)
Primary account number Used only when the primary account number begins with “59” ns. .28 34
(PAN), extended and contains a field separator as defined in IS0 4909 and shall (see 4.4.1 and
be used to identify a customer account or relationship. 4.4.5)
Processing code Code used to describe the effect of a transaction on the customer n6 3
account and the accounts affected. (see A.9 and
4.4.15)
Receiving institution Code identifying the receiving institution. n..l 1 100
and 4.4.16)
Reconciliation indicator A value used to allow reconciliation of time periods within a n3 29
reconciliation date, the value being subject to bilateral
agreement.
Retrieval reference number A reference supplied by the system retaining the original source anp 12 37
information and used to assist in locating that information or a
copy thereof.
Security related control Identifies security management information used in the current b..48 53
information transaction or specifies security management information to be (see 4.4.3)
used in future transactions.
Service code An identification of geographic/service availability (see IS0 7813). n3 40
Settlement institution Code identifying settlement institution or its agent. an..1 1 99
identification code (see 4.4.1)
Systems trace audit number A number assigned by a transaction originator to assist in n6 11
identifying a transaction uniquely. The trace number remains
unchanged for all messages within the transaction.
Track 1 data The information encoded on track 1 of the magnetic stripe as ans. .76 45
defined in IS0 7813, including field separators but excluding (see 4.4.1)
beginning and ending sentinels and longitudinal redundancy
check characters as defined therein.
Track 2 data The information encoded on track 2 of the magnetic stripe as 2. .37 35
defined in IS0 7813, excluding beginning and ending sentinels (see 4.4.1)
and longitudinal redundancy check characters as defined therein.
Track 3 data The information encoded on track 3 of the magnetic stripe as z.104 36
defined in IS0 4909, including field separators, but excluding (see 4.4.2)
beginning and ending sentinels and longitudinal redundancy
check characters as defined therein.
Transaction description Data describing additional characteristics of the transaction for ans..lOO 104
billing, fee collection or representment purposes. This data (see 4.4.2)
element can be used to provide information about merchandise
in an authorization or a financial transaction e.g., airline
itineraries.
IS0 8583 : 1993 (E)
Table 9 -Data element directory, concluded

Transaction destination Code identifying the institution that is the transaction destination n..l 1 93
institution identification code (see 4.4.1, 4.4.4
and 4.4.16)
Transaction originator Code identifying the institution that is the transaction originator n..l 1 94
institution identification (see 4.4.1, 4.4.4
and 4.4.16)
Transfer, number The sum number of all financial transactions processed where n 10 78
positions 1-2 of the processing code in the financial transaction (see 4.4.11)
indicated a transfer (40-49).
Transfer, reversal number The sum number of all reversal transactions processed where n 10 79
positions 1-2 of the processing code in the reversal transaction (see 4.4.11)
indicated a transfer (40-49).
Transport data Contains data from the originator of the message that shall be ans..999 59
returned unaltered in a response message. (see 4.4.2)
Bit position of the data element in which this data element is contained.
4.4 Requirements for data elements 4.4.3 Binary data elements
4.4.1 Variable length data elements less than 100 Binary data shall be grouped into blocks of 8 bits. The
length attribute defines the number of such blocks
For any variable length data element with a maximum present (e.g., the personal identification number data
length of less than 100 characters, an additional two data element has an attribute “b 8”, i.e. 64 bits of data).
numeric positions shall prefix the data element and In all “b” data elements, blocks of 8 bits are assumed
shall give its length. to be left-aligned with trailing zeroes.
The format shall be LLVAR. None of the variable If the format indicates a variable length (LLVAR or
length data element definitions in this International LLLVAR) the first two or three numeric positions
Standard include the two numeric positions of length contain the length in 8 bit blocks of the binary data
in the representation column in table 9. element which follows. Binary data elements shall
have a length which is a multiple of 8 bits.
All length attributes shall be right-aligned and zero
filled, e.g., primary account number 123456789012 is
represented by 12123456789012. The first “12” 4.4.4 Identification of institutions
indicates 12 digits to follow.
Card issuing institutions and their country codes shall
be identified by the procedure specified in IS0 7812,
4.42 Variable length data elements less than 1000
IS0 3166 and annex A of IS0 4909. If the major
For any variable length data element with a maximum industry identifier “59” is used, then the associated
length of less than 1 000 characters, an additional country code data element shall be used. Institutions
three numeric positions shall prefix the data element that are not card issuers shall be identified by a six
and shall give its length. digit code as defined in 4.4.16.
The format shall be LLLVAR. None of the variable In a transaction from acquirer or transaction
length data element definitions in this International originator to card issuer or transaction destination the
Standard include the three numeric positions of values for these fields shall be as shown in table 10.
length in the representation column in table 9. The acquirer and card issuer remain the same for the
life of the transaction. The authorizing agent shall be
All length attributes shall be right-aligned and zero used in the response message to indicate where an
filled, e.g., if Track 3 was included in a message and agent stands in for the card issuer.
Track 3 contained only 70 characters of information,
the data element would be represented as Where the transaction originator and transaction
O’lOnnn...nnn. The “070” indicates 70 characters to destination are used, they remain unchanged for the
follow. life of the transaction.
IS0 8583 : 1993 (E)
Table 10 - Usage of institution identification codes
For request, advice or notification messages:

I I I I
Institution identification code Acquirer to A A to B B to C C to Card Issuer
acquirer or transaction originator remains the same throughout the transaction
card issuer or transaction destination remains the same throughout the transaction
forwarding institution (acquirer) A B C
receiving institution A B C (card issuer)
For a response message:

-r 4
Institution identification code Issuer to C C to B B to A A to Acquirer
acquirer or transaction originator remains the same throughout the transaction
card issuer or transaction destination remains the same throughout the transaction
forwarding institution (card issuer) C B A

I
receiving institution C B A (acquirer)
Note: A, B and C represent potential agents that may be present between acquirers and card issuers
4.4.5 Identification of account numbers c) Original date and time, local transaction n 12;
The following data elements shall contain account d) Original acquiring institution identification code
numbers used to identify a customer account or n..ll (LLVAR).
relationship and shall remain unchanged for the life of
a transaction: Absence of data shall be indicated by zeroes.
a) Primary account number (PAN) or

4.4.7 Action code
b) Primary account number, (PAN) extended.
The numbering scheme for action codes shall be
The PAN or PAN, extended shall be present in a based upon the type of action and has no direct
message but not both. correlation to the message type identifier. The action
codes are grouped as follows:
The following data elements shall be used to identify oxx - authorization/financial transaction approved
specific accounts held by the cardholder at the card
lxx - authorization/financial transaction denied
issuer and if present, they shall remain unchanged for
the life of a transaction : 2xx - authorization/financial transaction denied,
pick up card
c) Account identification 1
3xx - file actions
d) Account identification 2
4xx - reversal or chargeback actions
4.4.6 Original data elements 5xx - reconciliation actions

6xx - administrative actions
These four data elements are in variable length format
totalling a maximum of 35 numerics, including the 7xx -fee collection actions
length attribute of the original acquiring institution
identification code: 8xx - network management actions
9xX - error/response actions
a) Original message type identifier n 4;
b) Original system trace audit number n 6; The action code values are in clause A. 1.
IS0 8583 : 1993 (E)
4.4.8 Expression of amounts 4.4.11 Reconciliation
The amount shall be expressed in the currency of the All amounts in the reconciliation messages are in the
associated currency code data element. Where a currency of reconciliation. The “x” portion of the fee
minor unit of currency applies, amounts shall be data element, defined as x + n 8, shall contain a “D” if
expressed in the minor unit of currency, without a the fee is due to the acquirer or a “C” if the fee is due
decimal separator. For example, an amount value of from the acquirer.
100 in US currency signifies one US dollar, but 100 in
Italian currency signifies 100 lire. For the purposes of table 11 it is assumed that the
transaction currency is the same currency as that of
4.4.9 Card acceptor name/location reconciliation. If the currency of reconciliation is
different from that of the transaction, then the
The card acceptor name/location data element shall reconciliation amounts and fees shall be added to the
consist of six data elements totalling up to 99 reconciliation data elements in place of the
characters. The first three data elements are of transaction amounts and fees.
variable length, separated from the remaining data
elements and each other by a back slash (\). The The first portion of table 11 identifies how the specific
remaining three data elements are fixed format as amount data elements from individual authorization,
shown below: financial, reversal, chargeback and fee collection
transactions shall be computed for reconciliation. The
a) name\street\city\ ans..83; second portion identifies how the reconciliation
counts shall be accumulated for inquiries,
b) postal code ans 10; authorizations, payments, transfers, financials,
c) region ans 3; reversals, chargebacks and fee collections.
d) country code a 3. A repeat (xxx1 or xxx3) message is not added to

reconciliation totals unless the original message was
The last three positions shall contain the three not received.
character country code as defined in IS0 3166.
For calculation of amount, net reconciliation:
add the sum of:

4.4.10 Original amounts
credits, fee amounts
The amounts, original data element shall consist of credits, amount
two data elements in fixed length format totalling credits, reversal amount
24 digits: credits, chargeback amount
a) Original amount, transaction n12; less the sum of:

b) Original amount, reconciliation n12. debits, fee amounts
debits, amount
debits, reversal amount
Absence of data shall be indicated by zeroes. These
debits, chargeback amount
data elements shall be used when attempting to
partially reverse or partially chargeback a previous
equals:
transaction or to perform a partial approval and
shall contain the original amounts. They shall also amount, net reconciliation
be used when performing replacement or
supplementary authorizations. The new transaction If the amount, net reconciliation after completing the
amounts shall be in the appropriate data elements. computation above results in a negative value the
These amounts are for information only and shall character “D” shall be inserted into the “x” portion of
not be used in the calculation of reconciliation amount, net reconciliation otherwise the character “C”
totals. shall be inserted in the “x” portion.
38
ISO8583:1993(E)
Table 11 - Reconciliation calculation
I Amount Calculations
MTI *x* portion of Add data To data element:
amounts, fees element:
11xX, 12xX, Cl amount, fee total of credits, fee amounts
14xX, 17xx amount, fee of
11xX, 12xX, 14xX, D amounts, fees amount, fee total of debits, fee amounts
17xx
, MTI Original Processing Add data To data element
I I MTI Code element:
l2xxI -- 00-l 9 debits, amount
20-29 credits, amount
00-l 9 amount, credits, reversal amount
14x0 1 12xx 20-29 transaction debits, reversal amount
14x2 1 -0 00-l 9 credits, chargeback amount
14x2 1 -- 20-29 debits, chargeback amount
II Count Calculations
MTI “x” portion of To data element:
I amounts, I Add
I fees I
number, fees total of credits, fee amounts
number, fees total of debits, fee amounts
MTI 1 O$rig;al 1 Proczgng 1 Add To data element:
1lxxI - 1 00-29 I authorizations, number

11xX 1 -- I 30-39 I inquiries, number
12xx I -- I 00-l 9 I debits, number
12xx I -- I 20-29 I credits, number
12xx I -- I 40-49 I transfers, number
payments, number
credits, reversal number
I
numeric value of
14x0 12xX 20-29 . debits, reversal number
14x2 1 12xx I 00-l 9 I I credits, chargeback number
14x2 1 12xx I 20-29 I debits, chargeback number
14x0 I llxx I 00-29 I authorizations, reversal number
,.14xX I -- I 30-39 I inquiries, reversal number
14xx 1 -- 1 40-49 I transfers, reversal number
14xX I -- I 50-59 I I-- payments, reversal number
17xx -- n/a fee collections, number
IS0 8583 : 1993 (E)
4.4.12 Additional amounts code. An institution involved in financial transaction

interchange that does not have an identification
The amounts, additional data element shall consist of number assigned through IS0 7812, shall apply for a
up to six sets of values. Each set of values shall consist number using the procedures described in clause 7.2.
of four parts in the following order :
4.4.17 Amounts, fees
a) Account type, additional amounts, n2 as defined
in positions 3 and 4 or positions 5 and 6 of the The amounts, fees data element shall consist of up
processing code data element. to six sets of values. Each set of values shall consist
of six data elements in fixed length format totalling
b) Amount type, additional amounts, n2. Amount 34 characters as follows:
type code values are in clause A.2.
c) Currency code, additional amounts, n3 or a3. a) fee type code, n 2
d) Amount, additional amounts, x + n12. b) currency code, fee, n 3 or a 3
c) amount, fee, x + n 8
4.4.13 Use of Cardholder Billing Information
d) conversion rate, fee, 8
Amount, , cardholder billin cl and amount cardholder
billing fe e may be use Id to: e) amount, reconciliation fee, x + n 8
f) currency code, reconciliation fee, n 3

a) provi de cardholde r fee informat ion in a financial
tra nsact ion response (e . g ‘I for print ing on a receipt),
4.4.18 Amounts, original fees
b) provide the amount, transaction expressed in the
currency of the cardholder in a response message The amounts, original fees data element shall consist
(e.g., for printing on a receipt), of up to six sets of values. Each set of values shall
consist of six data elements in fixed length format
c) provide the amount, transaction expressed in the totalling 34 characters as follows:
currency of the cardholder in a request, advice or
notification message when it is different from both a) original fee type code, n 2
the currency of transaction and currency of
reconciliation. b) original currency code, fee, n 3 or a 3
c) original amount, fee, x + n 8

4.4.14 Conversion Rates
d) original conversion rate, fee, n 8
<The leftmost digit denotes the number of positions the
decimal separator shall be moved from the right. e) original amount, reconciliation fee, x + n 8
Position 2-8 is the rate, e.g., a conversion’rate value of f) original currency code, reconciliation fee, n 3
91234567 would equate to 0,001234567.
The maximum number of digits to the right of the These data elements shall be used when attempting to
decimal separator is 9, provided the first two digits to partially reverse or partially chargeback a previous
the right of the decimal separator are zeroes. transaction, or to perform a partial approval and shall
contain the original fee amounts. The new fee
4.4.15 Maintenance of codes amounts shall be in the appropriate data elements.
The original fee amounts are for information only and shall
Any institution or organization using this International not be used in the calculation of reconciliation totals.
Standard may submit an application to the IS0
Secretariat of the Maintenance Agency for an 4.4.19 Fee amounts in reconciliation
additional code value for each data element
referenced by this note. Fees are accumulated for reconciliation in one of
two data elements. The credits, fee amounts and
The need for an additional code value shall be debits, fee amounts data elements shall consist of
evidenced by a substantiated application, which may up to six sets of values. Each set of values shall
be submitted from any source (see clause 7). consist of three data elements in fixed length format
totalling 24 characters as follows:
4.4.16 Maintenance of institution identification
codes a) fee type code, n 2
Any institution already holding an identification b) amounts, fee total, n 12

number assigned through IS0 7812 shall use that c) number, fee total, n 10
identification number as their institution identification
40
-
ISO8583:1993 (E)
5 Message and transaction flows
5.1 General
This International Standard specifies a message protocol i.e., the circumstances under which particular
messages/transactions shall (or may) be sent, the relationship between one message and another, but not the
commercial responsibilities which flow from a particular message/transaction being transmitted, The following
shows mandatory and optional message and transaction sequences:
5.2 Message flow diagrams

The following symbols are used in the message flow diagrams:
II institution
I I
mandatory message with

> message type
optional message with

-w-w--ww > message type
mandatory
response
Time
message sequence
5.21 Authorization transactions
acquirer card issuer

I I 1100 or 1120 I 1
I I
\
I T ime
I I I I I I
I I 1101 or 1121 1 ( I I
I I - - - - - - - - - -1 I I
I I 1110 or 1130 ] ] I I
I I< \/ J I I
I I I ’ v
1100/l 101 authorization request/authorization request repeat

1110 authorization request response
1120/l 121 authorization advice/authorization advice repeat

1130 authorization advice response

I 1 1140 I 1 Time
I > I I
L 1 I ’ v
1140 authorization not if icat ion

ISO8583:1993(E)
5.22 Financial transactions

I 1 1200 or 1220 I 1
I I 1 I Time
1 1201 or 1221 I I I I
I - - - - - - - - - -I I I
1 1210 or 1230 I I I I
I< \/ I I
1 I I ’ v
1200/l 201 financial request/financial request repeat

1210 financial request response
1220/l 221 financial advice/financial advice repeat

1230 financial advice response

1240 I 1 Time
II 1
1 I > I I
I I I 1 v
1240 financial notification
5.2.3 File action transactions
sender receiver
r 1 1304 or 1324 1 1
I I \ I Time
I I I I I I
I 1 1305 or 1325 I I I I
I I >---I I I
I I- ;3;4-0; r3;4- - 1 1 I I
I I< \/ I I
I J I ’ v
1304/l 305 file action request/file action request repeat

1314 file action request response
1324/l 325 file action advice/file action advice repeat

1334 file action advice response

1 I 1344 I 1 Time
I I > I I
L I I ’ v
1344 file action notification
42
IS0 8583 : 1993 (E)
5.24 Reversal transactions

I I 1420 I 1
I I \/ 1 I T ime
I I I I I I
I I 1421 I I I I
I I - - - - - - - - - t--l I I
I I 1430 I I I I
1 I< \0 I I
I J I ’ v
1420/l 421 reversal advice/reversal advice repeat

1430 reversal advice response
I 1 Time
1440 I I I
> I I
1 ’ v
1440 reversal notification
5.25 Chargeback transactions
card issuer acquirer

I I 1422 I 1
I I \/ [ I Time
I I I I I I
I I 1423 I I I I
I I - - - - - ,- a - - t-l I I
I I 1432 I I I I
I I< \0 ’ I I
I I I ’ v
1422/l 423 chargeback advicelchargeback advice repeat

1432 chargeback advice response

F 1 I 1 Time
I I 1442 I I I
I I > I I
1 I I ’ v
1442 chargeback notification
43
52.6 Acquirer reconciliation transactions

I 1 1500 or 1520 I 1
I I \ I Time
I 1 1501 or 1521 ] 1 I I
I I - - - - - 0 0 0 0 >---I I I
I / 1510 or 1530 I I I I
I I< \0 I I I
1 I I ’ v
1500/l 501 acquirer reconciliation request/acquirer reconciliation request repeat

1510 acquirer reconciliation request response
1520/l 521 acquirer reconciliation advice/acquirer reconciliation advice repeat

1530 acquirer reconciliation advice response

I 1 1 1 Time
I I 1540 I I I
I I > I I
1 I I ’ v
1540 acquirer reconciliation notification
5.2.7 Card issuer reconciliation transactions

I 1 1502 or 1522 I 1
I I /\ 1 I Time
I 1 1503 or 1523 I ] I I
I I - -1 I I
I I- r5;2-0; ;5;2- 1 1 I I
I I< \0 I I
I I I ’ v
1502/l 503 card issuer reconciliation request/card issuer reconciliation request repeat
1512 card issuer reconciliation request response
1522/l 523 card issuer reconciliation advice/card issuer reconciliation advice repeat
1532 card issuer reconciliation advice response

I I r 1 Time
I I 1542 I I I
I I > I I
I I 1 ’ v
1542 card issuer reconciliation notification

5.2.8 Administrative transactions
sender receiver
I 1 1604 or 1624 1 I
I I \/ 1 I Time
I I I I I I
I I 1605 or 1625 I I I I
I I 0 0 0 0 0 0 0 0 0 >---I I I
I I 1614 or 1634 I 1 I I
I I< J I I
1 I I J v
1604/l 605 administrative request/administrative request repeat

1614 administrative request response
1624/l 625 administrative advice/administrative advice repeat

1634 administrative advice response
sender receiver
I I 1644 f 1 Time
I > I I
1 I I ’ v
1644 administrative notification
5.2.9 Acquirer fee collection transactions

1720 I 1
I I I Time
I I 1721 I I I I
I I 0 0 0 0 0 0 0 0 0 >---I I I
I I 1730 I I I I
I I< \ 0
I I
I 1 l- ’ v
1720/l 721 acquirer fee collection advice/acquirer fee collection advice repeat
1730 acquirer fee collection advice response

I 1 1740 i 1 Time
I > I I
I I I I I
I I I ’ v
1740 acquirer fee collection notification
45
IS0 8583 : 1993 (El
5.2.10 Card issuer fee collection transactions

I I 1722 I I
I I \/ 1 I Time
I I 1723 I I I I
I I 0 0 0 0 0 0 0 0 0 *I I I
I I 1732 I I I I
I I< \ 0
I I
I I ’ v
1722/1723 card issuer fee collection advice/card issuer fee collection advice repeat
1732 card issuer fee collection advice response

I 1 1742 I 1 Time
1
I I > I I
i
I I I I I
’ v
1742 card issuer fee collection notification
5.2.11 Network management transactions
sender receiver
I I 1804 or 1824 I 1
I I \/ ’ I The
I I I I I I
I I 1805 or 1825 I / I I
I I 0 0 0 0 0 0 0 0 0 >---I I I
I 1814 or 1834 I I I I
II I< \ 1 0
I I
1 I I ’ v
1804/l 805 network management request/network management request repeat

1814 network management request response
1824/l 825 network management advice/network management advice repeat

1834 network management advice response
sender receiver
I 1 Time
1844 I I I
I I
1844 network management notification
46
ISO8583:1993(E)
5.2.12 Exception Message Flows
If the original request/advice/repeat sequence is not responded to for whatever reason, the acquirer shall send a
reversal. If the acquirer stands-in for the card issuer, the advice follows the reversal. A late response shall be
ignored by the acquirer because a reversal (and possibly an advice) has been sent.
acquirer request/advice card issuer

I 1 ( and repeats ) 1 I
I 1 llxx or 12xx I I
I I > not received, I T
I I I no response or I 1
i I I late response I M
I I I I E
I I 1420 I I
I I I I I
I reversal advice ] ] I 1
I I I I I I
I I 1430 I I I I
I< \
0
I I
I reversal
I
advice I I I
response 1 ' v
If a message cannot be identified (e.g., the message type identifier cannot be determined) the receiver may send a
1644 administrative notification message with a function code of “650” indicating inability to parse the original
message.
sender receiver
r 1 any message r I
> unable to I T
I parse message I I
I I M
I I I I E
I I 1644 I I I
I< I I I
I administrative 1 I I
notification L ’ v
47
5.3 Transaction flow diagrams
The following symbols are used in the transaction flow diagrams :
I I transaction
I I
II indicates the order in which
II transactions shall occur
V
I indicates the order in which

I transactions may occur
V
5.3.1 Transaction flows for llxx, 12xx, 14xx transactions
The following shows possible sequences of transactions relating to a single instance of business at a point of
sertiice in a full implementation of this standard.
start sequence
it 11
II II
II II T
V II
II
Iauthorization I,-, II I
I I v v
I I
t I
II I 1 financial I M
II I L
II I I II
II I r---- i II E
II V V V II
II I I II I
II I reversal I lchargeback I II I
II - I II I
II II II II I
II II II II I
II V 'V II V
L> end sequence <A
48
IS0 8583 : 1993 (E)
5.3.2 Transaction flows for reconciliation
If the network management messages are used to initiate cutover, the following applies:
a) The receiver of the network management request or advice message indicating cutover or checkpoint shall
initiate new transactions with the new date, reconciliation or reconciliation indicator (as indicated in the network
management request or advice message) only after sending the network management response message.
b) The sender of the network management request or advice message indicating cutover or checkpoint shall
initiate new transactions with the new date, reconciliation or reconciliation indicator only after receiving the
network management response message.
c) The reconciliation request or advice message shall be sent with the previous date reconciliation or
reconciliation indicator only after receiving (or sending) the network management response message (see
figure 2).
reconcilation card
acquirer date (YY/MM/DD) issuer
1804 network management request (93/01/02)

- - - - 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 ->----1
1200 financial request (93/01/01) I

-11
1422 chargeback advice (93/01/01) I I
\0
I I
I I
1814 network management response (93/01/02) I I
< ’ I
I
1210 financial request response (93/01/01) I
<
1220 financial advice (93/01/02)
\ I
1432 chargeback advice response (93/01/01) I
> I
1230 financial advice response (93/01/02) I
1500 request or 1520 advice (93/01/01)

\ 1
1510 or 1530 response (93/01/01) I
<
OR
1502 request or 1522 advice (93/01/01)

\
1512 or 1532 response (93/01/01)
.. Figure 2 - Reconciliation example
49
6 Message and transaction matching b) to define the necessary conditions to be fulfilled
for a code value to be allocated;
6.1 General c) to ensure publication and dissemi of
listings.
Where matching is required it is achieved by reference
to a set of fixed unchanged data elements. Two types
of matching are defined: 7.12 Maintenance Agency functions
Functions are divided into two categories :

a) matching within a transaction and
W matching between transactions. a) Those relating to IS0 8583 institution
identification codes, which are entrusted to the
Registration Authority (see 7.2).
6.2 Message matching
b) Those relating to all other IS0 8583 codes, which
In order to match messages within a transaction, the
are entrusted to the Maintenance Agency and its
response message shall return the data elements
Secretariat (see 7.3).
needed for matching. These are identified by
condition codes ME, 16 and 27 in table 78. Any or all of
these data elements may be used by the originator of
the transaction for matching. 7.2 IS0 8583 Institution identification codes
6.3 Transaction matching 7.2.1 Registration Authority
on matching any or all of For the purposes of this International Standard and
In order to achieve transacti
may be used according to the rules for designation and
the following data elements
operation of registration authorities in the IS0
a) Primary account number (PAN). Directives, the IS0 Council has appointed the
American Bankers Association to act as
b) Original data elements as contained in the Registration Authority.
transaction being matched (see 4.4.6).
c) Retrieval reference number of the original 7.22 Registration Authority functions
transaction.
These relate to codes to be used to identify institutions
d) Approval code. involved in financial transaction interchange within
the scope of this standard and that are not eligible for
Conditions for these data elements are specified in an issuer identification number (IIN) assigned through
Table 7B. the procedures specified in IS0 7812. The functions
are as follows:
a) to allocate one institution identification code per

7 Maintenance Agency and Registration applicant, as required, for immediate use and to
Authority notify the applicant;
b) to prepare regular updating reports on

7.1 Maintenance of codes
applications and code assignments to the IS0 8583
A Maintenance Agency established by IS0 Council Registration Management Group;
shall act in accordance with the procedures specified c) to maintain a register of the n umbers assigned as
in this International Standard. Membership shall instit ution identi fication co des.
consist of representatives of interested bodies
appointed by Technical Committee lSO/TC 68.
7.23 Applications for IS0 8583 institution
identification codes
7.1.1 Maintenance Agency responsibilities
An institution shall apply for an institution
These relate to all codes within this standa rd and are
identification code using the form shown in annex C.
as follows:
The application shall be made to their national
processing standards body, who will forward it to the Registration
a) to develop the procedures for
Authority.
submitted appl ications;
50
ISO8583: 1993(E)
7.3 All other IS0 8583 codes amendment to this International Standard, or by use of the
national or private series of message type identifiers
7.3.1 Maintenance Agency Secretariat within the terms of this International Standard.
For the purposes of this International Standard and
according to IS0 Directives, the IS0 Council has 8.2 Additional data elements
designated AFNOR Association Francaise de
Normalisation to act as the Secretariat for the This International Standard is constructed so that new
Maintenance Agency. data elements may be added. An unassigned bit shall
be required. Such assignment shall be made either by
7.32 Secretariat functions amendment to this International Standard or by
national or private agreement within the terms of this
Under the authority of the IS0 Council, the Secretariat International Standard.
to the Maintenance Agency shall be entrusted with the
following functions: The addition of a new data element is facilitated by
the assignment of that data element to a position in
a) to maintain the list of codes current ly assigned the bit map and the use of that position to indicate
withi n this standard (se le annex A); the presence or absence of the new data element. In
conjunction with the bit map technique, each data
b) to consult the Maintenance Agency and then element is either fixed in length or preceded by a
process all submitted applications for new code fixed length attribute “LL” or “LLL” indicating the
values, inform the applicants whether their request length of the variable data to follow. The length
has been granted and where appropriate make attribute and data consume only one bit position in
additions and changes to the list of codes; the bit map.
c) to establish in the normal course of work,
additional rules for the practical application of the 8.3 Mandatory and conditional data elements
principles for assigning codes within this standard.
The designation of a data element within a message
as mandatory (M) is based upon one criterion ; the
7.3.3 Applications for new code values data element so designated is one that shall be
An institution shall apply for new code values using the present to support the purpose of the message. This
form shown in annex C. The application shall be made designation may, in some cases, conflict with
to their national standards body, who will forward it to existing system capability or the needs of potential
the Maintenance Agency. The application shall users of this International Standard. To avoid
provide the following information: unnecessary controversy over these designations, it
shall be understood that the designations apply to
a) date of application; interchange messages between two or more
systems or networks. If a self-contained network
b) name of the applicant; chooses to modify these designations for
intrasystem use, this would not constitute a
c) name of data element; violation of this International Standard. If, however,
d) definition and proposed use; a message is sent from one system to another, all
parties in the system shall be prepared to meet the
e) if applicable, description of mandatory or mandatory requirements unless these designations
conditional use of new value; are bilaterally modified during the course of normal
business negotiations by the systems involved.
f) if applicable, describe impact on other data
elements; The designation of a data element within a message
as Conditional (nn) is based upon one criterion : the
g) date of impleme Nntation (indicate if special
data element so designated is one that shall be
conditions of urgency apply);
present if the condition specified in table 8 is
h) address fo r correspondence (name , address, satisfied.
telephone a nd fax/telex numbers, etc., of applicant).
8.4 Unintentional introduction of control
characters
8 Guidance on the use of this International
A bit stream, such as a bit map, PIN or password data
Standard
elements in the International Standard, may
unintentionally introduce a control character into the
8.1 Additional message types transmission stream under certain communications
protocols. Users of such protocols should take steps
This International Standard is so constructed th at new
to avoid this occurrence.
message type identifiers may be added by e ither
51
IS0 8583 : 1993 (E)
Annex A
(normative)
Code listings
52
A.1 Action codes 123 exceeds withdrawal frequency limit
Code Description 124 violation of law

125 card not effective
000-099 Used in 1110, 1120, 1121, 1140 and 1210, 126 invalid PIN block
1220, 1221 and 1240 messages to indicate 127 PIN length error
that the transaction has been approved.
128 PIN key synch error
129 suspected counterfeit card
000 approved
130-159 reserved for IS0 use
001 honour with identification
160-179 reserved for national use
002 approved for partial amount
180-l 99 reserved for private use
003 approved (VIP)
004 approved, update track 3
200-29s Used in 1110, 1120, 1121, 1140 and 1210,
005 approved, account type specified by card 1220, 1221 and 1240 messages to indicate
issuer that the transaction has been processed for
006 approved for partial amount, account type authorization by or on behalf of the card
specified by card issuer issuer and has been denied requiring the
007 approved, update ICC card to be picked up.

200 do not honour
201 expired card
080-099 reserved for private use
202 suspected fraud
100499 Used in 1110, 1120, 1121, 1140 and 1210, 203 card acceptor contact acquirer
1220, 1221 and 1240 messages to indicate 204 restricted card
that the transaction has been processed for 205 card acceptor call acquirer’s security
authorization by or on behalf of the card department
issuer and has been denied (not requiring a
206 allowable PIN tries exceeded
card pick-up)
207 special conditions
100 do not honour 208 lost card
101 expired card 209 stolen card
102 suspected fraud 210 suspected counterfeit card
103 card acceptor contact acquirer 211-259 reserved for IS0 use
104 restricted card 260-279 reserved for national use
105 card acceptor call acquirer’s security 280-299 reserved for private use
department
106 allowable PIN tries exceeded 300-39s Used in 1314, 1324, 1325 and 1344
messages to indicate the result of the file
107 refer to card issuer
action.
108 refer to card issuer’s special conditions
109 invalid merchant 300 successful
110 invalid amount 301 not supported by receiver
111 invalid card number 302 unable to locate record on file
112 PIN data required 303 duplicate record, old record replaced
113 unacceptable fee 304 field edit error
114 no account of type requested 305 file locked out
115 requested function not supported 306 not successful
116 not sufficient funds 307 format error
117 incorrect PIN 308 duplicate, new record rejected
118 no card record 309 unknown file
119 transaction not permitted to cardholder 3 1o-359 reserved for IS0 use
120 transaction not permitted to terminal 360-379 reserved for national use
121 exceeds withdrawal amount limit 380-399 reserved for private use
122 security violation I
53
IS0 8583 : 7993 (E)
400-49s Used in 1430, 1432, 1440 and 1442 860-879 reserved for national use
messages to indicate the result of the 880-899 reserved for private use
reversal or chargeback.
900 Advice acknowledged, no financial liability
accepted
400 accepted
901 Advice acknowledged, financial liability
40 l-459 reserved for IS0 use accepted
480-499 reserved for private use 902-949 Used in request response and advice
response messages to indicate transaction
Used in 1510, 1512, 1530 and 1532 could not be processed.
messages to indicate the result of a
reconciliation. 902 invalid transaction
903 re-enter transaction
500 reconciled, in balance 904 format error
501 reconciled, out of balance 905 acquirer not supported by switch
502 amount not reconciled, totals provided 906 cutover in process
503 totals not available 907 card issuer or switch inoperative
504 not reconciled, totals provided 908 transaction destination cannot be found for
505-559 reserved for IS0 use routing
560-579 reserved for national use 909 system malfunction
580-599 reserved for private use 910 card issuer signed off
911 card issuer timed out
Used in 1614, 1624, 1625, and 1644 912 card issuer unavailable
messages
913 duplicate transmission
914 not able to trace back to original
600 accepted
transaction
601 not able to trace back original transaction
915 reconciliation cutover or checkpoint error
602 invalid reference number
916 MAC incorrect
603 reference number/PAN incompatible
917 MAC key sync error
604 POS photograph is not available
918 No communication keys available for use
605 item supplied
919 encryption key sync error
606 request cannot be fulfilled -required/
920 security software/hardware error - try
requested documentation is not available
again
921 security software/hardware error - no
660-679 reserved for national use action
680-699 reserved for private use 922 message number out of sequence
923 request in progress
700-79s Used in 1720, 1721, 1740, 1722, 1723 and
92 4-929 reserved for IS0 use
1742 messages.
700 accepted 940-949 reserved for private use
950-999 Used in advice response messages (1x3x)
to indicate the reason for rejection of the
770-799 reserved for private use transfer of financial liability.
Used in 1814, 1824, 1825 and 1844 950 violation of business arrangement
messages.
984-99 1 reserved for national use
800 accepted
54
IS0 8583 : 1993 (H
A.2 Amount type codes Position 2-3 -time interval
Code Description
Code Description
00-W Account related balances

01-99 A value of 01 through 99 indicating the number
00 Reserved for IS0 use of reiterations indicated in position 1.
01 Account ledger balance

02 Account available balance A.4 Card acceptor business codes
03 Amount owing
The following codes are used to classify the type of
04 Amount due business being done by the card acceptor for a
05 Account available credit transaction.
06-10 Reserved for IS0 use
A.4.1 Card acceptor business codes (n umerica 11
ly)
II-15 Reserved for national use
16-19 Reserved for private use Agricultural service
20-39 Card related amounts Code Description
20 Amount remaining this cycle 0742 Veterinary services

21-30 Reserved for IS0 use 0763 Agricultural cooperatives
31-35 Reserved for national use 0780 Landscaping and horticultural services
36-39 Reserved for private use
Contracted services
40-59 Transaction related amounts
Code Description
40 Amount cash
41 Amount goods and services
1520 General contractors-Residential buildings
1711 Heating, plumbing, air conditioning
51-55 Reserved for national use
contractors
1731 Electrical contractors
1740 Masonry, stonework, tile setting, plastering,
insulation contractors
1750 Carpentry
1761 Roofing, siding, sheet metal work
1771 Concrete work
A.3 Authorization life cycle codes 1799 Special trade contractors, not elsewhere
classified
Position 1 -time code
Code Description Transportation
Code Description
0 Reserved for IS0 use
1 calendar days
4011 Railroads
2 hours
4111 Local and suburban commuter passenger
3 minutes
transportation, including ferries
4119 Ambulance services
4121 Taxicabs, limousines
4131 Bus lines, charters, tour buses
55
IS0 8583 : 1993 (E)
4214 Motor freight carriers, trucking- local and 5451 Dairy products stores
long distance, moving and storage 5462 Bakeries
companies, local delivery Miscellaneous food stores-specialty markets,
5499
4215 Courier services -Air and ground, freight convenience
forwarders
5511 Automobile and truck dealers (new and used)
4225 Public warehousing - Farm products, sales, service, parts
refrigerated goods, household goods,
5521 Automobile and truck dealers (used only)
storage
sales
4411 Steamships, cruise lines
5531 Auto stores, home supply stores
4457 Boat rentals, boat leases
5532 Automotive tire stores
4468 Marinas, marine service-supplies
5533 Automotive parts, accessories stores
4511 Airlines, air carriers
5541 Service stations
4582 Airports, flying fields, airport terminals
5542 Automated gasoline dispensers
4722 Travel agencies
5551 Boat dealers
4761 Telemarketing: travel related services,
5561 Recreational and utility trailers, camper
vitamins
dealers
4784 Tolls, bridge fees
5571 Motorcycle dealers
4789 Transportation services, not elsewhere
5592 Motor home dealers
classified
5598 Snowmobile dealers
5599 Miscellaneous automotive dealers, not
Utilities elsewhere classified
5611 Men’s and boy’s clothing and accessory
Code Description stores
5621 Women’s ready to wear stores
4812 Telecommunication equipment including 5631 Women’s accessory and specialty stores
telephone sales
5641 Children’s and infant’s wear stores
4814 Telecommunication service including local
5651 Family clothing stores
and long distance calls, credit card calls, calls
through use of magnetic stripe reading 5655 Sports apparel, riding apparel stores
telephones, fax services. 5661 Shoe stores
4821 Telegraph services 5681 Furriers, fur shops
4829 Wire transfer, money orders 5691 Men’s and women’s clothing stores
4899 Ca bl e services 5697 Tailors, seamstresses, mending, alterations
4900 Utilities - electric, gas, water, sanitary 5698 Wig and toupee stores
5699 Miscellaneous apparel and accessory stores
Retail Stores 5712 Furniture, home furnishings and equipment
stores, except appliances
Code Description 5713 Floor covering stores
5714 Drapery, window coverings, upholstery
5211 Lumber, building materials stores 5718 Fireplace, fireplace screens and accessories
5231 Glass, paint, wallpaper stores stores
5251 Hardware stores 5719 Miscellaneous home furnishing specialty
stores
5261 Nurseries, lawn, garden supply stores
5722 Household appliance stores
5271 Mobile home dealers
5732 Radio, television and stereo stores
5310 Discount stores
5733 Music stores, musical instruments, pianos,
5311 Department stores
sheet music
5331 Variety stores
5734 Computer software stores
5399 Miscellaneous general merchandise stores
5735 Record stores
5411 Grocery stores, supermarkets
5811 Caterers
5422 Freezer, locker meat provisioners
5812 Eating places, restaurants
5441 Candy, nut, confectionery stores
56
IS0 8583 : 1993 (E)
5813 Drinking places (alcoholic beverages) -bars, Service providers

taverns, nightclubs, cocktail lounges,
discotheques Code Description
5814 Fast food restaurants
5912 Drug stores, pharmacies 6010 Financial institutions - Manual cash
5921 Package stores, beer, wine, liquor disbursements
5931 Used merchandise stores, second hand stores 6011 Financial institutions- Automated cash
5932 Antique shops disbursements
5933 Pawn shops 6012 Financial institutions - Merchandise and
services
5935 Wrecking and salvage yards
6051 Non financial institutions - Foreign
5937 Antique reproduction stores
currency, money orders (not wire transfer),
5940 Bicycle shops- sales and service scrip, travelers’ checks, postage stamps
5941 Sporting goods stores 6211 Securities - brokers and dealers
5942 Book stores 6300 Insurance - sales and underwriting
5943 Stationery, office and school supply stores 6381 Insurance premiums
5944 Jewelry, watches, clocks and silverware 6399 Insurance, not elsewhere classified
stores
6611 Overpayments, reclamation
5945 Hobby, toy and game stores
6760 Savings bonds
5946 Camera and photographic supply stores
7011 Lodging-hotels, motels, resorts
5947 Gift, card, novelty and souvenir stores
7032 Sporting and recreational camps, boys’ and
5948 Luggage and leather goods stores girls’ camps
5949 Sewing, needlework, fabric and piece goods 7033 Trailer parks and campgrounds
stores
5950 Glassware and crystal stores
Personal service providers
5961 Mail order houses including catalog order
stores, book‘and record clubs
Code Description
5963 Direct selling establishments, door-to-door
sales
5970 Artist supply and craft stores 7210 Laundry, cleaning and garment services
5971 Art dealers and galleries 7211 Laundry services - family and commercial
5972 Stamp and coin stores-Philatelic and 7216 Dry cleaners
numismatic supplies 7217 Carpet and upholstery cleaning
5973 Religious goods stores 7221 Photographic studios
5974 Rubber stamp stores 7230 Beauty shops, barber shops
5975 Hearing aids-sales, service, supply stores 7251 Shoe repair shops, shoe shine parlors, hat
5976 Orthopedic goods - Artificial limb stores cleaning shops
5977 Cosmetic stores 7261 Funeral service and crematories
5978 Typewriter stores - sales, service, rentals 7273 Dating and escort services
5983 Fuel dealers - Fuel oil, wood, coal, liquified 7276 Tax preparation service
petroleum 7277 Counseling service - marriage, personal
5992 Florists 7278 Buying and shopping services, clubs
5993 Cigar stores and stands 7279 Debt counseling
5994 News dealers and newsstands 7280 Hospital patient personal funds withdrawal
5995 Pet shops, pet food and supplies accounts
5996 Swimming pools - sales and supplies 7295 Babysitting services
5997 Electric razor stores - sales and service 7296 Clothing rental - costumes, uniforms
5998 Tent and awning stores - 7297 Massage parlors
5999 Miscellaneous and specialty retail stores 7298 Health and beauty spas
7299 Miscellaneous personal services, not
elsewhere classified
57
IS0 8583 : 1993 (E)
Business services 7692 Welding

7699 Miscellaneous repair shops and related
Code Description services
7311 Advertising services Amusement and entertainment

7321 Consumer credit reporting agencies
7322 Debt collection agencies Code Description
7332 Blueprinting and photocopying services
7333 Commercial photography, art, graphics 7832 Motion picture theaters
7338 Quick copy and reproduction services 7833 Motion picture theaters (quick payment
services)
7339 Stenographic services
7841 Video rental stores
7341 Window cleaning services
7911 Dance halls, studios, and schools
7342 Exterminating and disinfecting services
7922 Theatrical producers (except motion
7349 Cleaning and maintenance, janitorial services
pictures), ticket agencies
7361 Employment agencies, temporary help
7929 Bands, orchestras, entertainers
services
7932 Billiard and pool establishments
7372 Computer and data processing services
7933 Bowling alleys
7389 Telemarketing other than travel related
services 7941 Commercial sports, professional sports clubs,
athletic fields, sports promoters
7392 Management, consulting, public relations
services 7991 Tourist attractions and exhibits
7393 Detective agencies, protective agencies, 7992 Golf courses - public
security services, including armored cars, 7993 Video amusement game supplies
guard dogs Video game arcades and establishments
7994
7394 Equipment rental and leasing services, tool Betting (including lottery tickets, casino
7995
rental, Furniture rental, appliance rental
Gaming chips, off track betting, and wagers at
7395 Photorefinishing laboratories, photo race tracks)
developing 7996 Amusement parks, circuses, carnivals,
7399 Business services - not elsewhere classified fortune tellers
7512 Automobile rental and leasing 7997 Membership clubs (sports, recreation,
7513 Truck and utility trailer rental athletic), country clubs, private golf courses
7519 Motor home and recreational vehicle rental 7998 Aquariums, seaquariums, dolphinariums
7523 Automobile parking lots and garages 7999 Recreation services (including swimming
pools, miniature golf and driving ranges, ski
slopes, sport and games instruction, boat
Repair services rentals and aircraft rentals)
Code Description
Professional services and membership organization
7531 Automotive body repair shops

Code Description
7534 Tire retreading and repair shops
7535 Automotive paint shops 8011 Doctors
7538 Automotive repair shops (non-dealer) 8021 Dentists, orthodontists
7542 Car washes 8031 Osteopathic physicians
7549 Towing services 8041 Chiropractors
7622 Radio, television and stereo repair shops 8042 Optometrists, ophthalmologists
7623 Air conditioning and refrigeration repair 8043 Opticians
shops
8044 Optical goods and eyeglasses
7629 Electrical and small appliance repair shops
8049 Chiropodists, podiatrists
7631 Watch, clock and jewelry repair shops
8050 Nursing and personal care facilities
7641 Reupholstery and furniture repair, furniture
8062 Hospitals
refinishing
8071 Medical and dental laboratories
58
IS0 8583 : 1993 0
8099 Medical services, health practitioners, not 4582 Airports, flying fields, airport terminals
elsewhere classified 4119 Ambulance services
8111 Legal services, attorneys 7999 Amusement and recreation services,
8211 Elementary and secondary schools (including swimming pools, miniature golf
8220 Colleges, universities, professional schools and driving ranges, ski slopes, sport and
and Junior colleges games instruction, and boat rentals)
8241 Correspondence schools 7996 Amusement parks, circuses, carnivals,
fortune tellers
8244 Business and secretarial schools
5937 Antique reproduction stores
8249 Vocational and trade schools
5932 Antique shops
8299 Schools and educational services, not
elsewhere classified 7394 Appliance rental
8351 Child care services 7998 Aquariums, seaquariums dolphinariums
8398 Charitable and social service organizations 597 1 Art dealers and galleries
8641 Civic, social and fraternal associations 5970 Artist supply and craft stores
8651 Political organizations 5531 Auto stores, home supply stores
8661 Religious organizations 5542 Automated gasoline dispensers
8675 Automobile associations 5511 Automobile and truck dealers-(new and
used)-sales, service, parts
8699 Membership organizations, not elsewhere
classified 5521 Automobile and truck dealers-(used only)
sales
8911 Architectural, engineering, and surveying
services 8675 Automobile associations
8931 Accounting, auditing and bookkeeping 7523 Automobile parking lots and garages
services 7512 Automobile rental and leasing
8999 Professional services, not elsewhere 7531 Automotive body repair shops
classified 7535 Automotive paint shops
5533 Automotive parts, accessories stores
Government services 7538 Automotive repair shops (non-dealer)
5532 Automotive tire stores
Code Description
9211 Court costs, including alimony and child

Code Description
support
9222 Fines
7295 Babysitting services
9223 Bail and bond payments
9223 Bail and bond payments
9311 Tax payments
5462 Bakeries
9399 Government services, not elsewhere
7929 Bands, orchestras, entertainers
classified
5813 Bars
9401 Food stamps
7230 Beauty shops, barber shops
9411 Government loan payments
7995 Betting (including lottery tickets, casino
gaming chips, off track betting, and wagers at
race tracks)
A.4.2 Card acceptor business codes (alphabetically)
5940 Bicycle shops- sales and service
7932 Billiard and pool establishments
7332 Blueprinting and photocopying services
Code Description 5551 Boat dealers
4457 Boat rentals, boat leases
8931 Accounting, auditing and bookkeeping
5942 Book stores
services
7933 Bowling alleys
7311 Advertising services
4131 Bus lines, charters, tour buses
0763 Agricultural cooperatives
8244 Business and secretarial schools
7623 Air conditioning and refrigeration repair
shops 7399 Business services, not elsewhere classified
4511 Airlines, air carriers 7278 Buying and shopping services, clubs
59
ISO8583:1993(E)
mC- 5963 Direct selling establishments, door-to-door

sales
Code Description
5813 Discotheques
4899 Cable services 5310 Discount stores
5946 Camera and photographic supply stores 8011 Doctors
5441 Candy, nut, confectionery stores 5714 Drapery
7542 Car washes 5813 Drinking places (alcoholic beverages) -bars,
taverns, nightclubs, cocktail lounges,
1750 Carpentry
discotheques
7217 Carpet and upholstery cleaning
5912 Drug stores, pharmacies
5811 Caterers
7216 Dry cleaners
8398 Charitable and social service
organizations
Child care services mE -
8351
5641 Children’s and infants’wear stores Code Description
8049 Chiropodists, podiatrists
8041 Chiropractors 5812 Eating places, restaurants
5993 Cigar stores and stands 5997 Electric razor stores - sales and service
8641 Civic, social and fraternal associations 7629 Electrical and small appliance repair shops
7349 Cleaning and maintenance, janitorial 1731 Electrical contractors
services 8211 Elementary and secondary schools
7296 Clothing rental - costumes, uniforms 7361 Employment agencies, temporary help
5813 Cocktail lounges services
8220 Colleges, universities, professional 8911 Engineering, architectural and surveying
schools and junior colleges services
7333 Commercial photography, art and 7394 Equipment rental, and leasing services, tool
graphics rental, furniture rental and appliance rental
7941 Commercial sports, professional sports 7342 Exterminating and disinfecting services
clubs, athletic fields, sports promoters
7372 Computer and data processing services li F-
5734 Computer software stores
Code Description
'm23 Consumer credit reporting agencies
1771 Concrete work
5651 Family clothing stores
8241 Correspondence schools
5814 Fast food restaurants
5977 Cosmetic stores
6011 Financial institutions - automated cash
7279 Counseling service - debt disbursements
7277 Counseling service - marriage, personal 6010 Financial institutions - manual cash
4215 Courier services - air, ground, freight disbursements
forwarders 6012 Financial institutions - Merchandise and
9211 Court costs, including alimony and child services
support 9222 Fines
5718 Fireplace, fireplace screens and accessories
I D- stores
5713 Floor covering, rug and carpet stores
Code Description
5992 Florists
5451 Dairy products stores 9401 Food stamps
7911 Dance halls, studios, and schools 5422 Freezer, locker meat provisioners
7273 Dating and escort services 5983 Fuel dealers -fuel oil, wood, coal, liquified
petroleum
7322 Debt collection agencies
7261 Funeral service and crematories
8021 Dentists, orthodontists
5712 Furniture, home furnishings and equipment
5311 Department stores
stores, except appliance
7393 Detective agencies, protective agencies, and
7394 Furniture rental
security services including armored cars,
guard dogs 5681 Furriers, fur shops
60
-G- 4111 Local and suburban commuter passenger
transportation, including ferries
Code Description
7011 Lodging - hotels, motels, resorts
1520 General contractors-residential buildings 5948 Luggage and leather goods stores
5947 Gift, card, novelty and souvenir stores 5211 Lumber, building materials stores
5231 Glass, paint, wallpaper stores
5950 Glassware and crystal stores -M-
7992 Golf courses - public Code Description
9411 Government loan payments
9399 Government services, not elsewhere 5961 Mail order houses including catalog order
classified stores, book and record clubs
5411 Grocery stores, supermarkets 7392 Management, consulting, public relations
services
4468 Marinas, marine service-supplies
I)
H -
1740 Masonry, stonework, tile setting, plastering,

Code Description insulation contractors
7297 Massage parlors
5251 Hardware stores
8071 Medical and dental laboratories
7298 Health and beauty spas
8099 Medical services, health practitioners, not
5975 Hearing aid sales, service, supply stores elsewhere classified
1711 Heating, plumbing, air conditioning 7997 Membership clubs (sports, recreation,
contractors athletic), country clubs, private golf courses
5945 Hobby, toy and game stores 8699 Membership organizations; not elsewhere
8062 Hospitals classified
7280 Hospital patient personal funds withdrawal 5611 Men’s and boys’ clothing and accessory
account stores
5722 Household appliance stores 569 1 Men’s and women’s clothing stores
5999 Miscellaneous and specialty retail stores
I)I - 5699 Miscellaneous apparel and accessory stores
Code Description 5599 Miscellaneous automotive dealers, not
elsewhere classified
6399 Insurance, not elsewhere classified 5499 Miscellaneous food stores-specialty, markets,
convenience
6300 Insurance - sales and underwriting
5399 Miscellaneous general merchandise stores
6381 Insurance premiums
5719 Miscellaneous home furnishing specialty
stores
I
J -
7299 Miscellaneous personal services, not

Code Description elsewhere classified
7699 Miscellaneous repair shops and related
7349 Janitorial services services
5944 Jewelry, watches, clocks and silverware 5271 Mobile home dealers
stores 7832 Motion picture theaters
7833 Motion picture theaters (quick payment
I
L - service)
Description 4214 Motor freight carriers, trucking- local and long

Code
distance, moving and storage companies,
local delivery
0780 Landscaping and horticultural services
7519 Motor home and recreational vehicle rental
7211 Laundry services - family and commercial
5592 Motor home dealers
7210 Laundry, cleaning and garment services
5571 Motorcycle dealers
8111 Legal services, attorneys
5733 Music stores, musical Instruments, pianos,
sheet music
61
IS0 8583 : 1993 (E)
-N- I)
R -
Code Description Code Description
5994 News dealers and newsstands 7622 Radio, television and stereo repair shops
5813 Nightclubs 5732 Radio, television and stereo stores
6051 Non financial institutions -foreign currency, 4011 Railroads
money orders (not wire transfer), scrip 5735 Record stores
travelers checks, postage stamps, and
5561 Recreational and utility trailers, camper
quasi cash
dealers
5261 Nurseries, lawn, garden supply stores
5973 Religious goods stores
8050 Nursing and personal care facilities
8661 Religious organizations
5812 Restaurants
-00 7641 Reupholstery and furniture repair, furniture
Code Description refinishing
1761 Roofing and siding, sheet metal work
8044 Optical goods and eyeglasses 5974 Rubber stamp stores
8043 Opticians
8042 Optometrists, ophthalmologists II S -
5976 Orthopedic goods - artificial limb stores
Code Description
8031 Osteopathic physicians
6611 Overpayments 6760 Savings bonds
8299 Schools and educational services, not
I
P - elsewhere classified
Code Description 6211 Securities - brokers and dealers

5541 Service stations
5921 Package stores, - beer, liquor, wine 5949 Sewing, needlework, fabric and piece goods
5933 Pawn shops stores
8050 Personal care services 7251 Shoe repair shops, shoe shine parlors, hat
cleaning shops
5995 Pet shops, pet food and supplies
5661 Shoe stores
7395 Photorefinishing laboratories, photo
developing 5598 Snowmobile dealers
7221 Photographic studios 1799 Special trade contractors, not elsewhere

classified
8651 Political organizations
7032 Sporting and recreational camps, boys’ and
8999 Professional services, not elsewhere girls’ camps
classified
5941 Sporting goods stores
4225 Public warehousing -farm products,
refrigerated goods, household goods, storage 5655 Sports apparel, riding apparel stores
5972 Stamp and coin stores - philatelic and
numismatic supplies
-Q- 5943 Stationery, office and school supply stores
Code Description 4411 Steamships, cruise Lines
7339 Stenographic services
7338 Quick copy and reproduction services
5996 Swimming pools - sales and supplies
mT - 7994 Video game arcades and establishments
Code Description 7841 Video rental stores
8249 Vocational and trade schools
5697 Tailors, seamstresses, mending, alterations
5813 Taverns -W-
9311 Tax payments Code Description
7276 Tax preparation service
4121 Taxicabs limousines 7631 Watch, clock and jewelry repair shops
4821 Telegraph services 7692 Welding
4761 Telemarketing: travel related services, 5698 Wig and toupee stores
vitamins 7341 Window cleaning services
4814 Telecommunication service including local 5714 Window covering upholstery services
and long distance calls, credit card calls, calls
through use of magnetic stripe reading 4829 Wire transfer, money orders
telephones, fax service 5631 Women’s accessory and specialty stores
4812 Telecommunication equipment including 5621 Women’s ready to wear stores
telephone sales 5935 Wrecking and salvage yards
7361 Temporary help services
5998 Tent and awning stores
A.5 Fee type codes
7922 Theatrical producers (except motion
pictures), ticket agencies Code Description
7534 Tire retreading and repair shops
4784 Tolls, bridge fees 00 transaction fee
7394 Tool rental 01 transaction processing fee
7549 Towing services 02 fee collection fee
7991 Tourist attractions and exhibits 03 file action fees
7033 Trailer parks and campgrounds 04 telex, telephone and cable charges
4011 Trains 05 auto-telex charges
4789 Transportation services, not elsewhere 06 lost/stolen card report fees
classified 07 merchant service fees
4722 Travel agencies 08 recovered card awards
9700 Travellers cheques, foreign currency, money, 09 invalid chargeback handling fee
scrip, precious metals 10 recovery of copy/original fees
7513 Truck and utility trailer rental 11 returned guaranteed cheque
5978 Typewriter stores - sales, service, rentals 12 emergency cash disbursement handling fee
13 arbitration cash disbursement handling fee
-U- 14 incorrect merchant identification /
Code Description transaction data handling fee
15 currency conversion fee
5931 Used merchandise stores, second hand stores 16 special handling fee
4900 Utilities - electric, gas, water, san itary 17 investigation fees
18 emergency card replacement fee
mV - 19 warning bulletin handling fee
Code Description 20 good faith acceptance

21 collection letters
5331 Variety stores 22-39 reserved for IS0 use
0742 Veterinary services 40-69 reserved for national use
7993 Video amusement game supplies 70-99 reserved for private use
63
IS0 8583 : 1993 (E)
A.6 Function codes 302 change record (see note 1)
Description 303 delete record

Code
304 replace record
000-099 reserved for IS0 use 305 inquiry
306 replace file
100499 Usedin 1100,1101,1120,1121 and 1140 307 add file
messages
308 delete file
309 card administration
100 original authorization - amount accurate
101 original authorization - amount estimated
102 replacement authorization - amount
accurate 380-399 reserved for private use
103 replacement authorization -amount
estimated 400449 Used in 1420,1421 and 1440 messages to
indicate the function of the reversal
104 resubmission - amount accurate
105 resubmission - amount estimated
400 full reversal, transaction did not complete
106 supplementary authorization - amount as approved
accurate
401 partial reversal, transaction did not
107 supplementary authorization - amount complete for full amount
estimated
108 inquiry
180499 reserved for private use 450-49s Used in 1422,1423 and 1442 messages to
indicate the function of the chargeback
200-299 Used in 1200,1201,1220,1221 and 1240
messages 450 first chargeback, full
451 second chargeback, full
200 original financial request/advice
452 third or subsequent chargeback, full
2.01 previously approved authorization -
453 first chargeback, partial
amount same
454 second chargeback, partial
previously approved authorization -
amount differs 455 third or subsequent chargeback, partial
203 resubmission of a. previously denied 456-469 reserved for IS0 use
financial request 470-489 reserved for national use
204 resubmission of a previously reversed 490-499 reserved for private use
financial transaction
205 first representment 500-59s Used in 1500,1501,1502,1503,1520,1521,
206 second representment 1522,1523,1540 and 1542 messages
207 third or subsequent representment
500 final reconciliation
208-259 reserved for ISO,use
501 checkpoint reconciliation
502 final reconciliation in a specified currency
503 checkpoint reconciliation in a specified
currency
300-399 Used in 1304,1305,1324,1325and 1344
messages 504 request for reconciliation totals
300 unassigned . 540-569 reserved for national use
301 add record 570-599 reserved for private use
64
ISO8583:1993(E)
600-649 Usedin1604,1605,1624,1625and1644 815-820 reserved for IS0 use

messages for retrievals 821 system accounting/cutover
822 system accounting/checkpoint
600 original receipt, retrieval request
601 original receipt, repeat retrieval request
831 system audit control/echo test
602 original receipt, fulfillment
603 copy, retrieval request
604 copy, repeat retrieval request
605 copy, fulfillment
606 vehicle rental agreement
607 hotel charge detail
608 POS photograph
NOTE 1 To be used when fields within a record are being
609 proof of delivery
replaced; if the entire record is being changed code 304 is
610 imprint recommended.
630-639 rese rved for national use
A.7 Message reason codes
640-649 rese rved for private use
Code Description
650-699 Used in 1604,1605,1624,1625 and 1644
messages for administrative messages 0000-0999 reserved for IS0
650 unable to parse message 1000-1499 Reason for an advice/notification

651-669 reserved for IS0 use message rather than a request message

1000 stand-in processing at the card issuer’s
689-699 reserved for private use option
1001 card issuer signed off
700-79s Used in 1720,1721,1740,1722,1723 and
1742 messages 1002 card issuer timed out on original request
1003 card issuer unavailable
700 fee collection message 1004 terminal processed
701 fee collection cancellation, full/partial 1005 ICC processed
702-759 reserved for IS0 use 1006 under floor limit
760-779 reserved for national use 1007 stand-in processing at the acquirer’s
780-799 reserved for private use option
Used in 1804,1805,1824,1825and 1844 1151-1375 reserved for national use
messages 1376-1499 reserved for private use
800 reserved for IS0 use 1500-1999 Reason for a request message rather
801 system condition/sign-on than an advice/notification message
802 system condition/sign-off
803 system condition/target system 1500 ICC application, common data file
unavailable unable to process
system condition/message originator’s 1501 ICC application, application data file
804
system in backup unable to process
system condition/special instruction 1502 ICC random selection
805
806 system condition/initiate alternate routing 1503 terminal random selection
reserved for IS0 use 1504 terminal not able to process ICC
807-810
system security/key chang,e 1505 on line forced by ICC (CDF or ADF)
811
system security/security alert 1506 on line forced by card acceptor
812
system security/password change 1507 on line forced by CAD to be updated
813
1508 on line forced by terminal
814 system security/device authentication
65
IS0 8583 : 1993 (El
1509 on line forced by card issuer 4006 response received too late
1510 over floor limit 4007 card acceptor device unable to complete
1511 merchant suspicious transaction
1512-1650 reserved for IS0 use 4008 deposit out of balance
1651-1775 reserved for national use 4009 no check in envelope
17764999 reserved for private use 4010 payment out of balance
4011 deposit out of balance/applied contents
Reason for a representment 4012 payment out of balance/applied
contents
general - invalid chargeback 4013 unable to deliver message to point of
invalid acquirer reference number on service
chargeback 4014 suspected malfunction/card retained
2002 non-receipt of required documentation 4015 suspected malfunction/card returned
to support chargeback 4016 suspected malfunction/track 3 not
2003 correct transaction date provided updated
2004 correct merchant description provided 4017 suspected mal In/no cash
(DW dispensed
2005 correct merchant location provided 4018 timed-out at taking money/no cash
2006 incorrect transaction date provided on dispensed
chargeback 4019 timed-out at taking card/card retained
2007 transaction did not exceed merchant and no cash dispensed
floor limit 4020 invalid response, no action taken
2008 transaction authorized by issuer 4021 timeout waiting for response
2009 no error in addition of sale - amount 4022-4199 reserved for IS0 use
correct in original transaction 4200-4350 reserved for national use
2010 no proof of altered amount (customer 4351-4499 reserved for private use
stated in chargeback that amount had
been altered)
4500-4999 Reason for a chargeback
2011 credit previously issued
2012 original transaction was valid 4500 invalid merchant
2013-2399 reserved for IS0 use 4501 invalid transaction
2400-2699 reserved for national use 4502 customer dispute
2700-2999 reserved for private use 4503 expired card
4504 transaction not permitted to terminal
Reason for a file action
4505 security violation
4506 system malfunction
3000 lost card
4507 disputed transaction amount
3001 stolen card
4508 authorized amount exceeded
3002 undelivered card
4509 authorized time limit exceeded
3003 counterfeit card
4510 credit submitted as a debit
4511 debit submitted as a credit
4512 duplicate processing of transaction
4513 credit not received
Reason for a reversal 4514 fraudulent transaction
4515 cardholder denies transaction was
4000 customer cancellation finalized
4001 unspecified, no action taken 4516 non-fulfillment of request for
information
4002 suspected malfunction
4517 non-fulfillment of request, illegible copy
4003 format error, no action taken
4518 cardholder does not recognize merchant
4004 completed partially
description
4005 original amount incorrect
66
IS0 8583 : 1993 (E)
4519 stand-in processing not allowed 5000-5999 Reason for a reconciliation

4520 stand-in processing criteria not fulfilled
4521 transaction exceeds floor limit 5000-5299 reserved for IS0 use
4522 declined authorization 5300-5599 reserved for national use
4523 non-matching account number 5600-5999 reserved for private use
4524 error in addition

6000-6499 Reason for a retrieval request
4525 altered amount
4526 missing signature 6001 cardholder request or dispute
4527 missing card imprint 6002 cardholder demand
4528 canceled preauthorized transaction 6003 chargeback documentation
4529 delinquent reconciliation 6004 legal or fraud investigation
4530 currency conversion errors 6005 legal request
4531 claim or defense on receipt of goods 6006 fraud analysis
4532 defective merchandise 6007 handwriting/paper analysis
4533 fraudulent transaction prior to 6008 cardholder requests copy bearing
embossed valid date signature
4534 imprint of multiple slips 6009 request for T&E document (e.g., car
4535 warning bulletin/exception file rental)
6010 original lost in transit
4536 late presentment
6011 written cardholder demand for original
4537 no show disputed
6012 legal process (e.g., subpoena) specifies
4538 advance lodging deposit
original
4539 cardholder disputes transaction date
6013 copy previously sent illegible
4540 card not yet effective
6014 cardholder does not recognize
4541 illegible data transaction
4542 transaction not received 6015 cardholder does not agree with
4543 duplicate processing by multiple transaction amount
institutions 6016 cardholder needs for personal records
4544 cancelling recurring transaction 6017 legal/fraud analysis - signature
4545 currency conversion not allowed verification
4546 mail/telephone order transaction 6018 legal/fraud analysis - amount
unauthorized purchaser verification
4547 card listed on warning bulletin 6019 legal/fraud analysis - imprint
verification
4548 cardholder dispute-transaction under
merchant floor limit
4549 incorrect account number
4550 cardholder disputes card activated
telephone transaction
6500-6999 Reason for an administrative message
4551 original transaction currency not
provided
4552 mail/telephone order on expired card
4553 transaction not as described
4554 non-receipt of merchandise
4555 services not rendered 7000-7999 Reason for a fee collection message
4556 merchandise not as described
4557-4649 reserved for IS0 use 7000-7299 reserved for IS0 use
4650-4749 reserved for national use 7300-7599 reserved for national use
4750-4999 reserved for private use 7600-7999 reserved for private use
67
IS0 8583 : 1993 (E)
Reason for a rk manage 4 biographic

message 5 electronic authentication inoperative
6 other
7 reserved for IS0 use
8 reserved for national use
9 reserved for private use
A-l reserved for IS0 use
J-R reserved for national use
s-z reserved for private use
Position 3 -Card capture capability

A.8 Point of service data code
Indicates whether or not the terminal has the ability to
Position 1- Card data input capability
capture a card.
Indicates the primary mea ns of g etting
informati on on the card into the termin al. Code Description
Code Description 0 none

1 capture
0 unknown 2-4 reserved for IS0 use
1 manual, no terminal 5-7 reserved for national use
2 magnetic stripe read 8-9 reserved for private use
3 bar code A-l reserved for IS0 use
4 OCR J-R reserved for national use
5 ICC (see note 1) s-z reserved for private use
6 key entered
8 reserved for national use Position 4- Operating environment (see note 2)
Indicates if the terminal is attended by the card
A;1 reserved for IS0 use
acceptor and its location.
s-z reserved for private use Code Description
0 no terminal used
Position 2 -Cardholder authentication capability 1 on premises of card acceptor, attended
2 on premises of card acceptor, unattended
Indicates the primary means of verifying the
cardholder at this terminal. When no order of 3 off premises of card acceptor, attended
priorities can be made, value “6” shall be used. 4 off premises of card acceptor, unattended
5 on premises of cardholder, unattended
Code Description 6-7 reserved for IS0 use
0 no electronic authentication
1 PIN
2 electronic signature analysis
3 biometrics
68
Position 5- Cardholder present 7 reserved for IS0 use
Indicates if the cardholder is present at the point of
service or not and if not why not.
Code Description J-R reserved for national use
cardholder present
cardholder not present, unspecified
cardholder not present, mail order Position 8 -Cardholder authentication method
cardholder not present, telephone
Indicates the method for verifying the cardholder
cardholder not present, standing identity.
authorization
5-6 reserved for IS0 use Code Description
9 reserved for private use not authenticated
A-l reserved for IS0 use PIN
J-R reserved use
for national electronic signature analysis
s-z reserved for private use biometrics
biographic
manual signature verification
Position 6- Card present other manual verification (e.g., drivers
license)
Indicates if the card is prese nt at the point of service or
not.
Code Description 9 reserved for private use
0 card not present A-l reserved for IS0 use
1 card present J-R reserved for national use
2-4 reserved for IS0 use s-z reserved for private use
A-I reserved for IS0 use Position 9 -Cardholder authentication entity
J-R reserved for national use Indicates the entity verifying the cardholder identity.
Code Description
Position 7- Card data input mode not authenticated

ICC (see note 1)
Indicates method used to input the information from
CAD (see note 1)
the card to the terminal
authorizing agent (identified in auth,oriting
agent institution identification code)
Code Description
4 by merchant
0 unspecified 5 other
1 manual, no terminal 6 reserved for IS0 use
2 magnetic stripe read 7 reserved for national use
3 bar code 8-9 reserved for private use
OCR , A-l reserved for IS0 use
4
5 ICC (see note 1) J-R reserved for national use
6 key entered s-z reserved for private use
69
IS0 8583 : 1993 (El
Position 10 -Card data output capability 9 nine characters

A ten characters
Indicates the ability of the terminal to update the card.
B eleven characters
C twelve characters
Code Description
D-l reserved for IS0 use
0 unknown J-R reserved for national use
1 none s-z reserved for private use
2 magnetic stripe write
3 ICC (see note 1) NOTES
1 CAD, ICC, ADF and CDF are terms defined in IS0 10202.
6-7 reserved for national use For the purposes of this International Standard, CAD
8-9 reserved for private use shall be synonymous with terminal.
2 If both values 4 and 5 apply, 5 shall be used.
A.9 Processing codes
Positions 1 and 2 are two digits that describe a specific
Position 11 -Terminal output capability transaction.
Indicates the ability of the terminal to print/display Code Description

messages.
00-l 9 Debits
Code Description
00 Goods and service
0 unknown
01 Cash
1 none
02 Adjustment
2 printing
03 Cheque guarantee (funds guaranteed)
3 display
04 Cheque verification (funds available but not
guaranteed)
05 Eurocheque
06 Traveller cheque
9 reserved for private use 07 Letter of credit
A-l reserved for IS0 use 08 Giro (postal banking)
J-R reserved for national use 09 Goods and services with cash disbursement
s-z reserved for private use 10 Non-cash financial instrument (e.g., wire
transfer)
11 quasi-cash and scrip
Position 12 - PIN capture capability 12-13 Reserved for IS0 use
Indicates the length of PIN which the terminal is
capable of capturing.
20-29 Credits
Code Description
20 Returns
0 no PIN capture capability
21 Deposits
1 device PIN capture capability unknown
22 Adjustment
23 Cheque deposit guarantee
4 four characters
24 Cheque deposit
5 five characters
6 six characters
27 Reserved for national use
7 seven characters
8 eight characters
70
IS0 8583 : 1993 (E)
30-39 Inquiry services These two codes are allocated as follows:
30 Available funds inquiry Code Description

31 Balance inquiry
32-35 Reserved for IS0 use 00 Default - unspecified
36-37 Reserved for national use 01-02 Default - Reserved for IS0 use
38-39 Reserved for private use 03-07 Default - Reserved for national use
08-09 Default - Reserved for private use
40-49 Transfer services
10 Savings account-default
40 Cardholder accounts transfer 11-12 Savings account - Reserved for IS0 use
41-45 Reserved for IS0 use 13-17 Savings account-Reserved for national use
46-47 Reserved for national use 18-19 Savings account - Reserved for private use

20 Cheque account-default
21-22 Cheque account - Reserved for IS0 use
50-59 Payment services
23-27 Cheque account - Reserved for national use
50 Payment 28-29 Cheque account - Reserved for private use
30 Credit Facility - default
31-32 Credit Facility - Reserved for IS0 use
33-37 Credit Facility - Reserved for national use
38-39 Credit Facility - Reserved for private use
60-99 Reserved
40 Universal account - default

41-42 Universal account - Reserved for IS0 use
43-47 Universal account - Reserved for national
90-99 Reserved
_--- for .private use
use
48-49 Universal account - Reserved for private use
50 Investment account - default

51-52 Investment account - Reserved for IS0 use
53-57 Investment account - Reserved for national
use
Positions 3 and 4 are a two digit code describing the 58-59 Investmentaccount-Reservedforprivateuse
account type affected for debits and inquiries and the
“from” account for transfers. 60-69 Reserved for IS0 use
Positions 5 and 6 are a two digit code describing the
account type affected for credits and the “to” account
for transfers. 90-99 Reserved for private use
71
IS0 8583 : 1993 (E)
Annex B
(informative)
Conversion guide
72
B.l Introduction B.2 Purpose
This International Standard was first published in This annex provides guidance and assistance to those
1987. It has been implemented by a number of concerned with compatibility and equivalency
national and international institutions and, is now between the 1987 and 1993 editions of this
in widespread use. Among the various financial International Standard. It outlines the differences
networks, the standard brought a higher level of between the two editions and provides equivalency
commonality and interoperability. Considerable charts. The authors of IS0 8583 (1993) recognized that
efficiencies were realized by using a common set there would be a transitional period during which
of message types, message flows, message both editions of the standard would be in use. During
contents, formats and vocabulary terms. this transitional period there should be some direction
available to assist users in evaluating and converting
After some experience with the first edition of this to IS0 8583 (1993). This annex fulfills that need and is
International Standard had been gained, it was intended for use mainly by those concerned with
recognized that there were some inconsistencies converting systems from the first to the second
among the various implementations. This was edition. It should also be useful to operators of
mainly due to the many options that were left to switches that support both versions simultaneously.
the discretion of each system implementor. This
International Standard was intentionally designed IS0 8583 (1993) is a completely self contained
to provide sufficient flexibility. to accommodate the standard. It is not necessary for any user of the
unique business requirements of individual standard to refer to this Conversion Guide for
implementations. This International Standard also explanations or information about the standard. This
included some definitions that were sufficiently Conversion Guide will be useful only to those users
imprecise to be subject to varying interpretations. who need to be aware of the differences between the
These factors combined to produce some first and second editions.
implementations that were incompatible with each
other even though they complied with the NOTE - This annex is for information only and does
standard. Although a degree of standardization has not constitute part of this International Standard. The
been achieved, it was clear that comprehensive annex will not be re-issued. Future changes in the
inter-network compatibility had not been achieved. Code Tables associated with IS0 8583 can be obtained
The net result was that the experience gained from the IS0 8583 Maintenance Agency or from
during implementation uncovered some national standards bodies (see clause 7). To utilize the
opportunities for additional standardization that Conversion Guide, reference to both editions of IS0 8583
could be of further benefit to users. will be required.
Towards this end, a Working Group was formed in

1988 to enhance and refine this International
Standard. This Working Group used the collective B.3 Differences between 1987 and 1993 editions
implementation experience gained to produce a of IS0 8583
new edition. This second edition is an
enhancement of the first edition, rather than a B.3.1 General
completely new standard. It builds upon the first
edition to further promote standardization and The scope and field of application remains largely
inter-network compatibility. Messages based on the unchanged between the two editions. This
1993 edition are distinguished from those which International Standard is intended to provide a common
follow the 1987 edition by means of a version interface bywhich financial transaction card originated
number, incorporated as the first position of a messages may be interchanged between systems.
restructured Message Type Identifier (MTI). Both the 1987 and 1993 editions specify message
structure, format and content, data elements and
Like the first edition, this second edition is values for data elements. Neither edition address:
designed as an interface specification enabling
messages to be exchanged between systems -communication protocols;
adopting a variety of application specifications.
specifications - data representation;
Designers of application have
complete design freedom within the overall - batch communications;
constraint that messages shall be convertible to
the interface format in order that international -the method of settlement b8tW@8n interchange
interchange may take place. parties.
73
IS0 8583 : 1993 (E)
There are notable improvements contained in IS0 8583 fi le action;

(1993). These include:
fi nancial transaction;
- simplification of message type identifiers; -forwarding institution;
- more detailed description of message classes; - inquiry;
- restructuring of reversal processing, with clear - institution identifier;
distinction made between reversals and
chargebacks; -maintenance agency;
- inclusion of integrated circuit card data elements - message class;

(as defined by lSO/TC 68/SC 6/VVG 7);
-message function;
- inclusion of security data elements (as defined by
lSO/TC 68/SC 6/#/G 6); - notification;
extension of message series to cover - payment;

co Ilections; - receiving institution;
-provision of a mechanism for updating and - reconciliation;
maintaining the code tables given in this
International Standard; - registration authority;
- provision of a m echanis for registering -replacement authorization;

institution id entifi cation codes;
- representment;
- restructuring of reconciliation processing;
-resubmission;
- specific advice on exception processing;
- supplementary authorization;
-guidance on transaction and message matching;
-transaction destination institution;
- consistency in the use of amount data elements;
-transaction originator institution;
- support for payment transactions.
-version.
The following additional standards are now
referenced; IS0 7372, IS0 8601, IS0 9564, IS0 9807 and B.3.2.2 Changes
IS0 10202. References to IS0 7580 have been deleted.
The revised standard is drafted and presented in The following definitions in IS0 8583 (1987) have been
accordance with the latest edition of the lSO/IEC modified to further clarify intentions of messages sent
Directives. and to augment previous definitions:
-acquirer;
B.3.2 Definitions
The following additions, changes and deletions were - advice;
made to the definitions section: - authorization;
-cardholder accounts transfer

B.3.2.1 Additions
(renamed ‘transfer’);
The following definitions in IS0 8583 (1993) have been -card issuer;
addedtoclarifytypesoftransactionsnot previouslydefined,
to define composition of message type identifiers and - point of service;
to define otherterms not previously addressed:
I request;
- bit map (formerly defined in Data Element
- reversal;
Directory);
- settlement institution;
- authorizing agent;
-transaction.
- chargeback;
-codes management group;
74
ISO8583:1993(E)
B.3.2.3 Deletions which MTI should be utilized in any particular

situation.
The following definitions have been deleted:
The revised MTI structure is described in 4.1.1 of the
- interactive message; standard. The incorporation of a version number, as
the first position of the MTI, provides a means of
- intermediate network facility;
identifying messages exchanged under the respective
- non-interactive message; editions of the standard. Version is defined in 3.39 of
IS0 8583 (1993).
- processing code;
In consequence of these revisions, certain MTl’s have
- reversal credit;
been eliminated or renamed. All MTl’s have been
- reversal debit; renumbered.
- reversal transfer; A general overview of improvements is given below.
- routing; a) MTl’s have been eliminated or modified when

their usage was imprecise or addressed by other
-transaction fee.
message sets.
The reasons for the deletions are: b) MTl’s which supported three legged transactions
have been eliminated.
a) The revised message type identifier (MTI)
expanded the identification of the purpose and c) All completion messages have been eliminated
activity involved, rather than restricting messages as part of the removal of thre e legged transactions.
to two types - interactive and non-interactive. d) Message functions within each message class have
b) Reversal credit, reversal debit and reversal been standardized to facilitate the full range of message
transfer have been deleted because Processing Code processing scenarios, e.g. request - request
describes the financial effects of these transactions. response, advice - advice response, notification.
c) IS0 8583 (1993) specifies the circumstances in e) Reference to interactive and non-interactive
which particular messages/transactions shall (or messages has been removed. Request and advice
may) be sent; it does not address commercial messages have, however, been re-defined as
(routing) responsibilities. follows:
d) Processi w code is defined in the data element Request: A message where the se lnder asks the
directory. receiver for an action to be taken.
e) lntermedi ate network facility is no longer used Advice: A message where the sender notifies
an ywhere in the standard. the receiver of an activity that has been taken,
requiring no approval but requiring a response.
B.3.3 Message Structure
f) Notification messages have been added. These
The components of message structure are unchanged are messages where the sender notifies the receiver
from the 1987 to the 1993 edition of the standard. of an activity taken, requiring no approval or
response (as distinct from an advice).
Each message is constructed in the same sequence,
namely message type identifier (MTI), the bit maps g) A new 17XX message series has been added to
and a series of data elements in the order of bit map accommodate the collection of miscellaneous
representation. service fees (e.g. request for copy fees).
h ) Reversal messa ges have been refined to

B.3.4 Message Types d istinguish between reversals a nd chargebacks.
The four-digit numeric message type identifiers
(MTl’s) specified in IS0 8583 (1987) have been The rema inder of this annex describes the changes by
restructured to give each digitposition a specific message class.
meaning thus providing an easy method of determining
75
Table B.1 - Comparison of message classes
Message name I lvm I hm Message name I
authorization request I 0100 I 1100 authorization request
authorization request repeat I 0101 I 1101 authorization request repeat
authorization completion confirmation I 0102 I -
authorization completion confirmation repeat I 0103 I -
authorization request response I 0110 I 1110 authorization request response
authorization completion response I 0112 I -
authorization advice I 0120 I 1120 authorization advice
authorization advice repeat I 0121 I 1121 authorization advice repeat
authorization advice completion confirmation I 0122 I -

authorization advice completion confirmation
repeat
authorization advice response I 0130 I 1130 authorization advice response -1
authorization advice completion response I 0132 I -
- 1140 authorization notification

.
Notes:
a) Elimination of authorization completion messages removes 0102, 0103, 0112, 0122, 0123, 0132
b) Addition of authorization notification message 1140.
76
IS0 8583 : 1993 (E)
Table B.l - Comparison of message classes, continued
IS0 8583 (1987) IS0 8583 (1993)
Message name MTI Message name
financial transaction request 1200 financial request
financial transaction
~~ ~~~~
request repeat I 0201 I 1201 I financial request repeat 1
financial transaction completion confirmation I 0202 --I - I - 1
financial transaction completion confirmation I 0203 I - I I I
repeat
financial transaction request response 0210 1210 financial request response
financial transaction completion response 0212 -
financial transaction advice I 0220 I 1220 I financial advice I
financial transaction advice repeat 0221 1221 financial advice repeat
financial transaction advice completion 0222 -

confirmation
financial transaction advice completion

confirmation repeat I Ozz3 I - I - I
financial transaction advice response I 0230

I 1230 I financial advice response -7
~ financial transaction advice completion 1 0232 1 - 1 - -1

i response
I - I 1240 I financial notification I
Notes:
a) Elimination of financial transaction completion messages removes 0202, 0203, 0212, 0222, 0223, 0232.
b) Addition of financial notification message 1240.
c) Message names changed to remove word @transaction”.
77
IS0 8583 : 1993 (E)
I ?’
IS0 8583 (1987) IS0 8583 (1993)
Message name I MTI I MTI I Message name
acquirer file update request 0300 - 0

L
card issuer file update request 0302 -
1304 file action request
I - I I 1305 file action request repeat I
acquirer file update request response I I I

0310 - I
card issuer file update request response I I I
0312 - I
I - I 1314 I file action request response -7
acquirer file update advice I 0320
I - I T
I
card issuer file update advice I 0322
~~ - -7
I - I 1324 I file action advice I
1325 file action advice repeat
acquirer file update advice response 0330 - 0

4
card issuer file update advice response 0322 -
I - I 1334 I file action advice response I

I - I 1344 I file action notification II
Notes:
a) Removed acquirer and card issuer MTI designations as new data elements, transaction originator institution identification
code and transaction destination institution identification code, were added to the messages.
b) Addition of repeat MTI’s if no response received by originator.
c) Addition of file action notification 1344.
d) Message names changed to replace “update” with “action”.
78
IS0 8583 : 1993-(E)
IS0 8583 (1987) IS0 8583 (1993)
Message name MTI M-l-l Message name
acquirer reversal request o400 - -

I
acquirer reversal request repeat 0401 -
r
card issuer reversal request 0402 -
II
II
card issuer reversal request repeat --Li0403-
I
1
I
- 1
I
-
IL acquirer reversal request response
card issuer request response I

0410
0412 I
-
- I
I acquirer reversal advice

I
0420 1420 reversal advice
II acquirer reversal advice repeat 1 0421 1 1421 1 reversal advice repeat
II card issuer reversal advice I 0422 1 1422 1 chargeback advice
card issuer reversal advice repeat I 0423 1423 1 chargeback advice repeat
acquirer reversal advice response I 0430 I 143c reversal advice response
II card issuer reversal advice response I 0432 I 1432 I chargeback advice response
I -
I
I
I
1440 I reversal notification
1442 chargeback notification

2’
Note:
a) Reversals can only be initiated by an acquirer and responded to by a card issuer.
b) Chargebacks can only be initiated by a card issuer and responded to by an acquirer.
4 Removal of request MTI’s as reversals and chargebacks have been redefined as advices only.
d) Message names changed to reflect new MTI definitions.
e) Addition of reversal notification message 1440 and chargeback notification message 1442.
IS0 8583 : 1993 (E)
Table 8.1 - Comparison of message classes, continued
IS0 8583 (1987) IS0 8583 (1993)

Message name I MTI MTI I Message name
acquirer reconciliation request I 0500 1500 I acquirer reconciliation request
acquirer reconciliation request repeat I 0501 1501 I acquirer reconciliation request repeat
card issuer reconciliation request I 0502 1502 I card issuer reconciliation request
card issuer reconciliation request repeat I 0503 1503 I card issuer reconciliation request repeat
acquirer reconciliation request response I 0510 1510 I acquirer reconciliation request response
card issuer reconciliation request response I 0512 1512 I card issuer reconciliation request response
acquirer reconciliation advice I 0520 1520 I acquirer reconciliation advice
acquirer reconciliation advice repeat I 0521 1521 I acquirer reconciliation advice repeat
card issuer reconciliation advice I 0522 1522 I card issuer reconciliation advice
card issuer reconciliation advice repeat I 0523 1523 I card issuer reconciliation advice repeat
acquirer reconciliation advice response I 0530 1530 I acquirer reconciliation advice response
card issuer reconciliation advice response I 0532 1532 I car issuer reconciliation advice response
I - 1540 I acquirer reconciliation notification
1542 card issuer reconciliation notification
Note:
a) Numbering changed.
b) Addition of reconciliation notification messages.
IS0 8583 : 1993 (E)
Table B.1 -Comparison of message classes, continued
IS0 8583 (1967) IS0 8583 (1993)

Message name MTI Message name
administrative request 1 1604 I administrative request
administrative request repeat 0601 1605 administrative request repeat
administrative request response 0610 1614 administrative request response

I
administrative advice administrative advice
administrative advice repeat response 0621 1625 administrative advice repeat
administrative advice response 1634 administrative advice response
I - I 1644 administrative notification
Notes:
a) Addition of administrative notification message 1644.
IS0 6563 (1967) IS0 8583 (1993)
Message name MTI MTI Message name
1720 acquirer fee collection advice
1721 acquirer fee collection advice repeat
1730 acquirer fee collection advice response
1740 acquirer fee collection notification
1722 card issuer fee collection advice
- 1723 card issuer fee collection advice repeat
1732 card issuer fee collection advice response
1742 card issuer fee collection notification
Notes:
a) New message series.
b) Messages are generated by either the acquirer or the card issuer and are restricted to advices and notifications.
81
ISO8583:1993 (E)
Table B.1 - Comparison of message classes, concluded
IS0 8583 (1987) IS0 8583 (1993)

~~~~
Message name MTI I M-l-1 Message name I
network management request 1804 network management request
network management request repeat 0801 1805 network management request repeat
network management request response I

0810 1814 network management request response
network management advice I

0820 1824 network management advice
network management advice repeat I

0821 1825 network management advice repeat
network management advice response - I 1834 network management advice response
- I 1844 network management notification
Note:
a) Addition of network management notification message 1844.
82
IS0 8583 : 1993. (E)
B.3.5 Data elements j) Card acceptor business code (bit 26) -Added to
provide an international classification of merchant
The following additions, changes and deletions were
type (bit 18). A list of code values for this data
made to the data element directory:
element was added to Annex A.
k) Country code, authorizing agent institution (bit

B.3.5.1 Additions
70) ’ country code, transaction destination
The following data elements (in alphabetical order) institution (bit 91) l country code, transaction
have been added to IS0 8583 (1993). originator institution (bit 92) - Added in
conjunction with new institution identification
a) Acquirer reference data (bit 31) - Added to codes.
indicate the reference data supplied by an acquirer
I) Credits, chargeback amount (bit 105) ; Credits,
for its own transaction matching.
chargeback number (bit 107) - Added because
b) Action code (bit 39) -Added to define the action chargebacks are card issuer to acquirer generated
taken or the action to be taken as well as the reason as opposed to reversals, which are acquirer to card
for taking the action. Incorporates information issuer generated. Use of these data elements in the
previously contained in response code and reconciliation process is explained in B.4.2.
settlement code (now both deleted). A mapping of
m) Credits, fee amounts (bit 109) - Added to
the new and former data elements is given in
indicate (by fee type) the sum of all fee amounts fees
B.3.5.4.
due from the Acquirer. Use of this data element in
c) Amounts, fees (bit 46) -Added to denote all fees the reconciliation process is explained in B.4.2.
affecting reconciliation. Indicates the type of fee, the
n) Currency code, fee (bit 46) - Added, in
fee amount, currency code, conversion rate and
conjunction with new amounts, fees data element.
amount reconciliation fee (if the transaction
currency is different from the reconciliation o) Data record (bit 72) - Added to support an
currency). Incorporates information previously administrative or file action message.
contained in amount transaction fee, amount
transaction processing fee, amount settlement fee, p) Date and time, local transaction (bit 12) -
amount settlement processing fee, conversion rate Incorporates information previously contained in
transaction fee, conversion rate transaction date, local transaction and time, local transaction.
processing fee, currency code transaction fee and The date representation now includes “YY”.
currency code transaction processing fee. Use of
q) Date, effective (bit 13) - Added because of its
this data element is explained in B.4.4.
increasing usage.
d) Amounts, original (bit 30) - Added to indicate
r) Date, reconciliation (bit 28) - Added to indicate
original amounts, where appropriate in
the applicable reconciliation period.
authorization, financial, reversal and chargeback
messages. Not used in reconciliation processing. s) Debits, chargeback amount (bit 106) ; debits,
Advice on the usage of amount data elements is chargeback number (bit 108) - Added because
given in 8.4.1. chargebacks are card issuer to acquirer generated
as opposed to reversals, which are acquirer to card
e) Amounts, original fees (bit 31) - Added to
Issuer generated. Use of these data elements in the
indicate original fee amounts (as distinct from
reconciliation process is explained in B.4.2.
original amounts). Not used in reconciliation
processing. Use of this data element is explained in t) Debits, fee amounts (bit 110) - Added to
B.4.4. indicate (by fee type) the sum of all fee amounts due
to the acquirer. Use of this data element in the
f) Authorizing agent institution identification code
reconciliation process is explained in B.4.2.
(bit 58) - Added to indicate the institution that
processed an authorization or financial transaction u) Fee collections, number (bit 85) - Added to
if different from that identified in either the PAN or support a reconciliation count of fee collections.
PAN extended data elements.
v) Function code (bit 24) - Added to indicate the
g) Authorization life cycle code (bit 57) -Added to specific purpose of the message within its message
indicate how long an authorization request will class (e.g. a retrieval request as a type of
remain outstanding. administrative message).
h) Authorization, reversal number (bit 90) -Added Incorporates information previously contained in
to support a reconciliation count of authorization
file update code, network management information
transactions.
code and some response codes (now all deleted). A
i) Card issuer reference data (bit 95) - Added to comparison of the new and former data elements is
indicate the reference data supplied by a card issuer given in B.3.5.4.
for its own transaction matching.
83
IS0 8583 : 1993 (E)
w) Inquiries, reversal number (bit 82) - Added to c) The primary and secondary bit map indicators (P
allow cancellation of any fees associated with the and S) have been removed. Bit map positions are
inquiry. expressed only as a number between 1 and 128.
Sub-data elements are so noted.
x) Integrated circuit card (ICC) system-related data
(bit 55) - Added to meet processing needs relating
The following data elements that appeared in IS0 8583
to use of integrated circuit cards (ICC&
(1987) have been changed in some way. Modifications
y) IKey management data (bit 96) -Added because are varied and include changes to title, description
former security related data elements are and/or representation.
insufficient to convey key management data.
a) Additional response data (bit 44) l -
z) Message reason code (bit 25) - Provides the Representation is changed from ‘ans..25’ to
card issuer with the reason an advice or notification ‘ans..99’.
message is sent rather that a request message or
vice versa. b) Amounts, additional (bit 54) - Formerly
additional amounts.
aa) Payments, number (bit 83) ; payments, reversal
c) Approval code - (bit 38) - Formerly authorization
number (bit 84) -Added to support a reconciliation
identification response. Representation is changed
count of payment transactions.
from ‘an’ to ‘anp’.
ab) Point of service data code (bit 22) - Added to d) Approval code length (bit 27) - Formerly
provide more information to support authorization authorization identification response length.
decisions. Incorporates information previously
contained in point of service condition code, point of e) Authorizations, number (bit 81) - Description
service entry mode and point of service PIN capture modified.
code (now all deleted). A mapping of the new and
former data elements is given in B.3.5.5. f) Bit map extended (bit 65) - No longer a data
element. Position reserved.
ac) Reconciliation indicator (bit 29) - Added to
g) Card acceptor name/location (bit 43) -
support a checkpoint reconciliation within a
Designated a variable length data element. A field
reconciliation period.
separator character (/) was added to delineate
sub-fields within this data element.
ad) Transaction destination institution identification
code (bit 93) ; Transaction originator institution h) Country code, acquiri ng instituti on (bit 19) -
identification code (bit 94) - Added to support Fo rmerly acquiter instituti on country code.
general message routing.
i) Country code, forwarding institution - (bit 21) -
ae) Transport data (bit 59) - Added to support Formerly forwarding institution country code.
remapping and retrieval of transaction originator
information. j) Country code, primary account number (PAN)
(bit 20) - Formerly primary account number (PAN)
extended, country code.
8.3.5.2 Changes
k) Credits, amount - (bit 86) - Description
For t ease of u pdat :ing and reference, the coded values expanded.
for data elem ents were m oved to annex A.
I) Date, expiration - (bit 14) - Description
Attention is drawn to three gene ral changes in the modified.
representation of data eleme nts :
m) Date and time, transmission (bit 7) - Formerly
transmission date and time. Greenwich Mean Time
a) Binary data is now considered to be grouped into
(GMT) is replaced by Coordinated Universal Time
blocks of 8 bits e.g. b8 refers to 64 bits of data. If the
(UTC).
format indicates a variable length (LLVAR or
LLLVAR) the first two or three positions contain in n) Date, reconciliation - (bit 28) - Representation
character form the length in 8-bit blocks of the is changed from “n 4” to “n 6” and “YY” is added.
binary data element which follows. It is not
permitted to have a binary data element with a o) Date, settlement - (bit 15) - Description
length which is not a multiple of 8 bits. excludes reference to intermediate network facility,
which has been deleted from the standard.
b) A new representation ‘anp’ is specified. This Representation is changed from “n 4” to “n 6” and
allows use of alphabetic, numeric and space. (pad) “YY” is added.
characters.
ISO8583:1993(E)
p) Debits, amount (bit 88) ; debits, number (bit 76) ; z) Retrieval reference number (bit 37) -
debits, reversal amount (bit 89) ; debits, reversal Representation is changed from ‘an’to ‘anp’.
number (bit 89) - Descriptions expanded in overall
attempt to better describe reconciliation data aa) Security related control information (bit 53) -
elements. Description modified. Representation is changed
from ‘n16’to ‘b..48’.
q) Forwarding institution identification code (bit 33)
- Description simplified. 4.4.4 of IS0 8583 (1993) ab) Settlement institution identification code (bit 99)
describes the relationship and intended use of all - Representation is changed from ‘n..ll’ to ‘an..1 I’.
institution identification codes.
ac) Service code (bit 40) - Formerly service
r) Inquiries, number (bit 80) - Description restriction code. Representation is changed from
modified to include reference to processing codes “an” to “n”. Refers to value specified in amendment
(30-39) as opposed to processing code 30 only. to IS0 7813.
Inquiries are considered to be authorization
transactions. ad) Transaction description (bit 104) - Description
modified to describe additional characteristics of a
s) Message authentication code (bit 64 or bit 128)
transaction, not only for billing, but also for fee
- Reference is made in the description to IS0 9807
collection and representment purposes. This data
which provides details of the MAC technique to be
element can be used to provide information about
used in retail banking.
merchandise in an authorization or a financial
The representation for binary data is expressed as a transaction e.g. airline itineraries.
block of 8 bits.
ae) Transfer, number (bit 78) ; transfer, reversal
t) Original data elements (bit 56) - Description number (bit 79) - Description modified. Transfers
modified. Bit position re-assigned. are considered to be financial transactions.
Representation reduced from 42 fixed length

numeric digits to 35 variable numeric digits. The B.3.5.3 Deletions
data element is variable because of changes to the The following data elements, that appeared in IS0 8583
acquiring institution identification code. (1987)’ have been deleted.
Descritption of contents modified.
a) Amount, transaction fee ; amount, transaction
Original transmission date and time and original
processing fee ; amount, settlement fee ; amount,
forwarding institution identification code are no
settlement processing fee ; conversion rate,
longer required for transaction matching. Original
transaction fee - Incorporated within consolidated
date and time, local transaction is, however,
amounts, fees (bit 46).
intended for transaction matching.
b) Credits, transaction fee amount ; credits,
u) Personal identification number (PIN) data (bit 52)
transaction processing fee amount - Incorporated
- Reference is made in the definition to IS0 9564
within consolidated credits, fee amounts (bit 109).
which provides details of the PIN block formats to be
used in retail banking. The representation for binary c) Da te, local transaction - Incorporated with in
data is expressed as a block of 8 bits. cons0 lidated date and time, local transaction (bit 12 1.
v) Primary account number (PAN) (bit 2) - d) Debits, transaction fee amount ; debits,
Description simplified. transaction processing fee amount - Incorporated
within consolidated debits, fee amounts (bit 110).
w) Primary account number (PAN) extended
(bit 34) - Description modified to include e) File security code - No evidence of international
reference to IS0 4909. need/u sage identified.
x) Processing code (bit 3) - An additional code is f) File update code - Incorporated within new
specified in positions 1 and 2, namely IO (non-cash function code (bit 24) (see B.3.5.4).
financial instrument e.g. wire transfer). Positions 3,
4 and 5 re-structured. Code range (50-59) assigned g) lnterme diate network facility - No longer
for payment services e.g. a utility bill payment referenced in the standard.
where the card issuer debits the cardholder account
h) Message security code ; message number last ;
and credits the utility company.
network international identifier - No evidence of
y) Receiving institution identification code (bit 100) international need/usage identified.
- Description simplified. Subclause 4.4.4 of IS0 8583
i) Network management information code -
(1993) describes the relationship and intended
Incorporated within new function code (bit 24) (see
use of all institution identification codes.
B.3.5.4).
85
j) Point of service condition code ; point of service Where codes have been deleted, there may be no
entry mode ; point of service PIN capture code - direct mapping of new function and action codes,
Incorporated within new point of service data code which are more precise. In these cases the new code
(bit 22) (see B.3.5.5). closest in meaning has been indicated.
k) Replacement amounts - Included in amount, A complete listing of function and action codes is
transaction (bit 4)’ the use of which has been given in annex A of IS0 8583 (1993).
modified. Advice on the usage of amount data
elements is given in B.4.1.
Table B.2 - File update code (1987)
I) Response code - Incorporated within new mapped to function code (1993)
function code (bit 24) and action code (bit 39) (see
8.3.5.4).
b 1
m) Response indicator - Incorporated within an Code Description Code
action code (bit 39). (1993)
WW
n) Service indicator - No evidence of international II 0 I unassigned I --=-II
need/usage identified. 1 1 add record
o) Settlement code - Incorporated within new 2 change record
action code (bit 39) (see B.3.5.4). 3 delete record
p) Time, local transaction - Incorporated within 4 bulk replacement

consolidated date and time, local transaction (bit 12). 5 inquiry
6 delete record, system purge
B.3.5.4 Action, function and message reason code 7 add file
mapping
II 8 I delete file I30811
The following Tables show the mapping of: II 9 I unassigned I -=----II
a) The former file update code, which is replaced by
4-F I reserved for IS0 use I 3093591
the newly defined function code, values 300-399; II G-N f reserved for national use I 360-3791
b) The former network management information
II 0-z I resewed for private use 1380-39911
code, which is replaced by the newly defined
function code, values 800-899;
c) The former response code, which is replaced by

the newly defined message reason codes and/or
action codes;
d) The former settlement code, which is replaced by

the newly defined action code, values 500-599.
IS0 8583 : 1993 (E)
Table B.3 - Network management information code (1987) mapped to function code (1993)
Code (1987) Description Code (1993)
system condition/reserved
001 system condition/sign-on 801
002 system condition/sign-off 002
003 system condition/target system unavailable 803
system condition/message originator’s system in back-up

mode
005 system condition/special instructions 805
system condition/initiate atternative routing
007-039 system condition/reserved for IS0 use 807-809
100 system security/reserved 810
101 system security/key 811
102 system security/security alert 812
103 system security/password change 813
104 system security/device authentication 814
105-l 39 system security/reserved for IS0 use 815-819
system accounting/reserved 820
201 system accounting/initiate cut-off 821
202 system accounting/cut-off complete
203-239 system accounting/reserved for IS0 use 823-829
system audit control/echo test 831
302-339 system audit control/reserved for IS0 use 832-85s
o40-059
140459
240-259 reserved for national use 860-879
340-359
600-799
160499
360-399
800-999
87
IS0 8583 : 1993 (E)
Table B.4 - Response code (1987) mapped to message reason code and action code (1993)
Code response code/action code (1987 message reason action code

code (1993) (1993)
1 00 approved or completed successfully/approve
01 refer to card issuer/decline 107
02 refer to card issuer special conditions 108
03 invalid merchant 4500 109 (in

(chargebacks) authorization and
financial
transactions)
04 I pick-up/pick -up I I
05 do not honour 100
06 error 913
07 I pick-up .card, special condition/pick-up I I 207
08 honour with identification/approve 001
09 request in progress 901
10 approved for partial amount/approve
11 approved (‘VIP)/approve 003
12 invalid transaction 4501 902 (in response

(chargebacks) messages)
13 I invalid amount 7 110
14 I invalid card number (no such number) I I 111
15 no such issuer/decline I I
16 approved, update track 3Japprove
17 customer cancellation
18 customer dispute 4502
19 reenter transaction/decline I I 903
20 I invalid response I 1-
21 I no action taken I 4001 I
22 suspected malfunction 4014, 4015,

I I 4016,4017 I
23 unacceptable transaction fee/decline
24 file action not supported by receiver
25 unable to locate record on file
26 duplicate file action record, old record replaced
27 file action field edit error
88
IS0 8583 : 1993 (E)
Table B.4- Response code (1987) mapped to message reason code and action code (1993), continued
Code response code/action code (1987) message reason action code

code (1993) (1993)
28 file action file locked out
29 file action not successful/contact Acquirer
30 format error
31 bank not supported by switch/decline
32 completed partially
33 expired card/pick-up
34 suspected fraud/pick-up
35 card acceptor contact acquirer/pirk-up
36 restricted card/pick-up
37 card acceptor call acquirer secur*w/pick-up
38 allowable PIN tries exceeded/pick-up
39 no credit account/decline 114
40 requested function/not supported/decline
41 lost card/pick-up
42 no universal account/decline 114
43 stolen card, pick-up/pick-up
44 no investment account/decline 114
51 no sufficisnt funds/decline 116
52 no cheque account/decline 114
53 no savings account/decline 114
54 expired card/decline 101

I
55 incorrect PIN/decline 117
i
56 no card record 118
57 transaction not permitted to cardholder/decline 119
58 transaction not permitted to terminal/decline 120
59 suspected fraud/decline 102
60 card acceptor contact acquirer/decline 103
61 exceeds withdrawal amount limit/decline I 121
62 restricted card/decline 104
63 security violation 122
64 original amount incorrect/decline 4005 110
65 exceeds withdrawal frequency limit/decline 123
66 card acceptor call acquirer’s security department/decline 105
89
IS0 8583 : 1993 (E)
Table B.4 - Response code (1987) mapped to message reason code and action code (1993), concluded
Code response code/action code (1967) message reason action code

I code (1993) I (1993)
67 hard capture (requires that card be picked-up at ATM/pick-up)
68 response received too late
75 allowable number of PIN tries exceeded/decline
90 cut-off is in process (Switch ending a day’s business and starting

the next. Transaction can be sent again in a few minutes).
91 issuer or switch is inoperative/decline
92 financial institution or intermediate network facility cannot be

found for routing/decline
93 transaction cannot be completed. Violation of law/decline 124
94 duplicate transmission 913
95 reconcile error 915
96 system malfunction
Table 8.5 - Settlement code (1987) Where codes have been deleted, there may be no
mapped to action code (1993) direct mapping of new codes. In these cases, the new
code closest in meaning has been indicated.
A complete listing of codes specified under point of
II 1 in balance
Description
I Code
(IQ=)
service data codes is given in annex
(1993).
A of IS0 8583
II 2 out of balance I 501 II Table B.6 - Point of service PIN capture code (1987)
mapped to point of service data (1993)
II 4 not reconciled, totals provided 1

,
504
l
4-5 reserved for IS0 use 505559 1967 Description

1
1 Code Code Position 12

6-7 resewed for national use 560-579
o-3 resewed for IS0 23 resented for IS0
8-9 resewed for private use 580-599 use I use II
. .
412 the code ’ 4-c the code indicates
indicates the the maximum
maximum number number of PIN
of PIN characters characters
accepted by the accepted by the
B.3.5.5 Point of service data code mapping
point of service point of service
device device
The following tables show the mapping of:
a) The former point of service PIN capture code and

the corresponding values in the newly defined point
13-59 resewed for IS0
use I D-l resewed for IS0
use II
of service data. II 60-79
80-99
reserved for
national use
reserved for
I
J-R reserved for
national use II
b) The former point of service condition code and s-z resewed for private
the corresponding values in the newly defined point private use use
c \
of service data.
c) The former point of service entry mode and the
corresponding values in the newly defined point of
service data.
90
IS0 8583 : 1993 (EI
Table B.7 - Point of service condition code (1987) mapped to point of service data (1993)
Code Description Code Description

00 normal presentment (see note 1)
01 customer not present position 5=1-4 cardholder not present
02 unattended terminal able to retain card position 3= 1 capture
position 4= 1 unattended, on premises
position 4=3 unattended, off premises
03 merchant suspicious (see note 5)
04 electronic cash register interface (see note 2)
05 customer present, card not present position 5=0 cardholder present
position 6=0 card not present
06 pre-authorized request (see note 3)
07 telephone device request position 4 = 1 on premises of card acceptor, attended
position 4=3 off premises of card acceptor, attended
08 mail and/or telephone order position 5=2 mail order
position 5=3 telephone order
09 security alert (see note 5)
10 customer identity verified position 8= 1 PIN, electronic signature analysis,
through 6 biometrics, biographic, manual, other
11 suspected fraud (see note 5)
12 security reasons (see note 5)
13 representation of item (see note 3)
14 public utility terminal (see note 2)
15 customer terminal (home terminal) position 4 =4 off premises of card acceptor, unattended
16 administration terminal (see note 2)
17 returned item (chargeback) (see note 4)
16 no cheque in envelope/all returned (see note 5)
19 deposit out of balance/all returned (see note 5)
20 payment out of balance/all returned (see note 5)
31 manual reversed (see note 4)
22 terminal error/counted (see note 3)
23 terminal error/not counted (see note 3)
24 deposit out of baiance (applied contents) (see note 5)
25 payment out of balance (applied contents) (see note 5)
26 withdrawal had error/reversed (see note 4)
27 unattended terminal unable to retain card position 3=0 no capture
position 4 =2 on premises of card acceptor, unattended
position 4 =4 off premises of card acceptor, unattended
Note 1 - “Normal presentment” dependent upon type of transaction as defined by processing code and point of service data.
Note 2 - There is no matching code as no standard terminal classification exists.
Note 3 - Handled via the function code.
Note 4 - Handled via the message type identifier (MTI).
Note 5 - Handled vai the message reason code.
91
IS0 8583 : 1993 (E)
Table B.8 - Point of service entry mode (1987) A This is a message matching data element and
mapped to point of service data (1993) must be the same as in the original request or
advice (see 5.2 of IS0 8583:1993).
?
I
B This is not a message matching data element and
Code Positions 1 and 2 Code Position 7 is therefore optional or conditional in a response
(see 5.2 of IS0 8583: 1993).
II 00 unspecified I0 unknown II
01 manual 1 manual - C This is replaced by date and time, local
embossed transaction as a matching data element.
6 manual - key
entered D Added to support reconciliation or reconciliation
02 magnetic stripe 2 magnetic stripe of fees.
7
03 bar code 3 bar code E Point of service data code incorporates the former
II 04 OCR I 4 OCR II point of service condition code, point of service
05 ICC 5 ICC
entry mode and point of service PIN capture code.
F No international usage/requirement identified.

position 3 position 12
L 1 G Addedto support international usage/requirement.
0 unspecified entry 1 device PIN
capture H Function code incorporates former file update
capability code, network management information code and
unknown some response codes.
1 PIN capability
I I Acquirer may not have information.
2 no PIN entry 0 no PIN capture J This is a transaction matching data element and is
capability capability therefore not required in a response (see 5.3 of
Lb
IS0 8583: 1993).
K Revised use of amount and fee data elements.
L Generic message is now used.
M This is not a transaction matching data element.

B.3.6 Usage of data elements
N Identifies the card issuer.
The following tables provide comparison, for each
message class, of the mandatory and conditional data 0 Optional for reconciliation.
elements required under the 1987 edition with those
P Action code incorporates former settlement code.
required under the 1993 edition of this International
Standard. The reasons for changing the usage of data R Reason for file action message and PAN affected.
elements are given in following notes:
92
Table B.9 - Data Elements by Message Class, continued
I Condition Codes (1987) I I I Condition Codes (1993) IN
Bit Bit 0
Financial messages
(‘987) 0200 0202 0210 0212 0220 0222 0230 0232 (1993) 1200 1210 1220 1230 1240 T
0210 0203 0221 0223 1201 1221 E
1 l-i I t
1 11 11 11 11 11 11 11 1” 1bit map extended I 1 I
2 07 07 07 07 07 07 07 107 1primary account number I 2 lo7 16 07 16 07 A
L
3 M M M M M M M IM I processing code I 3 IM 27 M ME M A
4 M M M M M M M IM I amount, transaction I 4 IM M M M M
I
5 05 105 IO5 IO5 IO5 IO5 05 IO5 1amount, reconciliation I 5 I 05 05 05 I
7 M IM IM IM IM IM M IM 1date and time, transmission I 7 I C
k
9 05 105 105 105 105 --~
105 05 105 I conversion rate, reconciliation I g I 05 05 05
10 conversion rate, cardholder billing 10 04 04 04 04 04
,
11 M M M M M M M M systems trace audit number 11 M ME M ME M
I I date and time, local transaction I 12 IM ME M ME M
I Jdate, GffectivC --~ I 13 102 02 02 G
O2 I I I 102 I I 1date, expiration I 14 102 02 02
ii 16 05 05 05 05 05 05 05 105 1date, conversion I 16 I 05 05 05
II l7 M I I date, capture I 17 I I22 I 122
II 19 09 09 09 09 09 09 09 109 1country code, acquiring institution I 19 I
II 20 09 09 09 OS 09 09 09 109 1country code, primary account number I 20 I
21 09 09 09 09 09 09 09 109 1country c,rfe, forwarding institution I 2’ I
--_
II-- 22 08 108 1 I IO8 I08 point of service entry mode E
point of service data code 22 M E
I
23 02 116 02 16 card sequence number 23 02 02 02 is-

24 I16 16 16 16 network international identifier F
I
function code 24 M H
25 02 02 point of service condition code E
c
26 14 14 14 14 point of service PIN capture code E v,
L A
card acceptor business code 26 M I IM I IM EG 0
00
cn
00
w
..
5w
E
v,
0
E
60
cl4
..
Tablt ! B.9 - Data Elements by Message Class, continu zd
Condition Codt 5
edition Codes (19 17) I I w
Bit Bit
Financial messages, continued E
~ (‘987) 0200 0202 0210 ~0212 0220 (1993) 1200 1210 1220 1230 1240
0201 0203 I 0221 1201 I 1221 I
11 27 18 I I18 I I 1approval code length 1 27 18
I I I date, reconciliation r 28 12 I 12 I12 0
I I I reconciliation indicator ----I 29 14 I 14 I23 D
I I I amounts, original 08 21 lo8 I08 K
f- ~~ ~
I= 32 M M M M IM M IM IM I acquiring institution identification code I 32 M ME jM ME IM A
I 33 10 10 10 10 I 10 10 IlO 110 1forwarding institution identification code 1 33 10 10 I10 10 IlO
I 34 15 15 15 15 115 15 I15 I15 I primary account number, extended I 34 15 16 I15 16 I15 A
-
I 35 I I 1track 2 data 1 06
36 track 3 data 36 06 I06 I06 G
-
37 02 16 I02 16 retrieval reference number 37 16 I
I= 39 17 M M M M M action code (was response code) 39 M 1M
I 40 service code (was service restriction code) 40 02 02
Fk-I I02
I 41 16 ‘6 I 16 16 card acceptor terminal identification 41 16 1 16
I 42 card acceptor identification code 42 16 16
I 43 M IM I card acceptor name/location 43 M M M
I I ltrack 1 data I 45 06 06 06 G
I I I amounts, fees I 46 01 01 01 01 01 D
M M IM IM 1currency code, transaction I 49 M ME M ME M
05 05 105 105 1currency code, reconciliation I 50 05 05 05 li-
-
I I 1currency code, cardholder billing ~ I 51 04 04 04 04 04
I I I authorizing agent institution identification code 1 20 20 20 jo
I
transport data 59 16 ~16
. LG
09 09 09 country code, receiving institution 66 I .
19 I19 I19 I receiving institution identification code I 100 19 1’9 19 19 19
, 1
I12 12 ,l2 12 account identification 1 102
L 1 r I
‘12 12 12 12 account identification 2 103
Table ‘09 - Data Elements by Message Cla ss, continuei
E
COI dition Codes ( ‘87) Condition Cod1 6 (1993 N

Bit Bit 0
File action messages
(‘987) 0300 0310 0320 0330 (1993) 1304 1314 1324 1334 1344 T
0301 0312 I 0322 0332 1305 I I 1325 E
-
1 M 11 IM 11 bit map extended I 1
!
2 primary account number I 2 28 116 128 16 28 R
7 M M IM M date and time, transmission I 7 c
11 M M IM M systems trace audit number I 11 M I ME IM ME M A
12+13 date and time, local transaction I 12 M IME IM ME M A
function code I 24 M I lM M H
message reason code I 25 28 I I28 28 R
33 10 10 10 forwarding institution identification code 33 10 10 10
-
I10 I I10 I10
39 M I M action code (was response code) I 39 IM IM M M
transport data I 59 I 16 I 16 G
-
66 09 09 I09 09 country code, receiving institution I 66
71 M M message number I 71 I16 I 16
data record 1 72 29 I I29 29 G
91 M IM file update code ii
transaction destination institution identification 93 M ME M ME M r
code I I I
transaction originator institution identification 94 ME M i
code I I-
100 19 119 receiving institution identification code I 100 19
file name 101 29
4
\
Condition Codes (1987) Condition Codes N
Bit Bit (1993) 0
. . Reversal messages L 1
(1987) 0400 0410 0420 0430 (1993) 1420 1430 1440 T
0401 0421 1421 E
II 1 IM 111 IM 111 I bit map extended I 1 I I I ~~~ 1-

II 2 107 107 107 107 I primary account number I 2 107 116 107 IA
II 3 103 116 103 116 I processing code I 3 103 116 103 IA
4 03
I I16 I03 I 16 Iamount, transaction I 4 IM lM IM -I-
ll 5 104 116 I04 116 I amount, reconciliation I 5 I lo5 105 II
II 7 IM IM IM IM I date and time, transmission 171 I I --l-F
II 9 104 116 104 116 I conversion rate, reconciliation I 9 I 105 105 --r
II 10 I I I I 1conversion rate, cardholder billing I 10 I04 104 104 I
II 11 IM IM IM IM Isystems trace audit number I 11 IM IME IM IA
1 1date and time, local transaction I 12 IM IME IM --k
II 16 lo4 116 104 116 I date, conversion I 16 I 105 105 -r
II 19 109 109 10.9 109 I country code, acquiring institution I 19 I I I I
II 20 109 109 109 109 lcwntry code, primary account number I 2o I I I I
21 09 09 I09 09 country code, forwarding institution I 21 I I
L
22 04 104 point of service entry mode I I I E

1
23 04 16 104 16 card sequence number 1231 I F

24 16 I 16 network international identifier I I I F
1
function code 24 M M H
,
25 04 104 point of service condition code E

28 04 16 amount, transaction fee I I I
.
reconciliation indicator I 29 I 114 23 D

date, reconciliation I 28 I P 12 D
amounts, original I 30 108 I 08 K
32 IM M IM M /acquiring institution identification code I 32 IM IME M A
L
33 I10 110 IlO 10 jforwardingnstitution identification code 1 33 I10 I10 10

1
34 115 116 115 16 /primary account number, extended 1 34 115 I16 15 A

37 16 / retrieval reference number I 37 I I M
, ~
I
Condition Codes (1 w dition Codes
Bit Bit
Reversal messages, continued
W7) 0400 0410 0420 0430 (1993) 1420 1430 1440
0401 I I 0421 1421
38 03 03 approval code (was authorization identification 38 17 17 M
I response) I
39 M M action code (was response code) I 39 M
IM
IIM IIM
41 16 card acceptor terminal identification I 41
42 card acceptor identification code I 42 16 I -
43 card acceptor name/location I 43
I amounts, fees I 46 01 01 lo1 D
49 03 I 03 I03 currency code, transaction I 49 03 16 I03
50 04 I 04 I 04 04 currency code, reconciliation 05 I05
51 currency code, cardholder billing I 51 04 04 I04
90 M original data elements I 56 M IM J
v--F authorizing agent institution identification code I 58 17 117
transport data I 59 16 I G
66 09 I09 I09 09 country code, receiving institution I 66
transaction originator institution identification 94 09 16
code I I09
95 06 I03 I06 03 amounts, replacement
100 19 I19 I 19 19 receiving institution identification code 100 ~19
102 account identification 1 102
r
103 04 account identification 2 103
,
z-f+- L
l .
,

I Condition Codes (1987) 1 I Condition Codes
Bit
Chargeback messages
(1987) &4;; 10412 104;; 10432
II
II 1 IM Ill IM Ill 1bit map extended I 1 I I I I II
II 2 I07 I07 I07 I07 I primary account r,Jmber I 2 107 I16 107 IA II
3 03 16 processing code
03 I16 I03 I16 Iamount, transaction I 4 IM IM IM I II
04 I16 amount, reconciliation 5 I I05 I05 I II
II 7 IM IM IM IM I date and time, transmission I 7 I I I IC II
II 9 104 116 b 116 I conversion rate, reconciliation I 9 I 105 105 I II
II 11 IM IM IM IM Jsystems trace audit number I 11
IM IME IM IA II
103 1 ldate and time, local transaction I 12 IM IME IM IA II
II 16 104 I16 104 I16 I date, conversion 1 16 1 105 105 I II
country code, acquiring institution
09 09 09 09 country code, primary account number 20
,
09 09 09 09 country code, forwarding institution 21
II 23 I04 I16 I04 I16 I card sequence number I=1 I I IF II
24 I 116 1 116 I network international identifier I I I I IF II
1function code I 24 IM I
104 1 point Of s8rViC8 condition code
26 04 16 04 16 amount, transaction fee I
date, reconciliation I 28 12 12 D
29 04 16 04 16 amount, settlement fee I
reconciliation indicator I 29 14 23 D
amounts, original 30 ii8 K
32 M M M acquiring institution identification code 32 M ME A
10 10 10 forwarding institution identification code I 33 10 10
16 15 16 primary account number, extended I 34 15 16 ~15 A
k3
d
Condition Codes (1987) I I Condition Codes
Chargeback messages, continued

Bfi(1993)
(1993) 1422 1432
1423
04 I16 104 116 retrieval reference num her I 37 117~~ ]iF[-ll
I~~~~~-
38 03 I I03-m-I--pipauthorization id’entification response 1381 I I IM II
M IM IM IM I action code (was response code) I 39 I IM IM I II
I16 I I-- card acceptor terminal identification
16 _ r- 1411 I I IM II
03 03 I card acceptor name/location 1431 I I I
amounts, fees 1 46 101 lo1 lo1 hi
03 03 I currency code, transaction 1 49 lo3 116 lo3 I
04 04 I04 currency code, reconciliation 50 05 05
M Ioriginal data elements 56 M M
--~
~transport data 1591 116 I I
09 09 country code, receiving institution 66 G
transaction originator institution identification 94 11 16 11 J
code
06 03 06 I03 amounts, replacemen; I I I I I
19 19 19 119 receiving institution identification code 1 100 119 119 I19 1
04 104 04 I04 ~account identification 1 11021 Kim I
04 ,04 104 account identification 2 1103l I I I
IS0 8583 : 1993 (E)
S C
- E F
- a- a - 0- 0- -
- r- 0
- z- - =E
-
c9
- si
-
0
- s- - -T-
- t- 0
T- z- - z-
- g- O
- ii- - 2-
0
- z- - z- - -
- N
F- 3 55 8 2s ii3
- - - - - -
-zi
gt3> -ti
: uo
iz E 5
-7
iiE .-5 -e
t!! .z
5
2
.-
E
G
.- 5 7s
c
.-
.-
3 F E l=
.-Q
.-
.- i; 45
.- iii
.-
P
.- 5
E 2
.- .-5
E
.-> 2
8 w .-s5 5 8
L 3L ii z
ti! .-C .Z .e
E
z .-z g 9& Ec
v)
5
.-5 .-c fi 2E .-E
z
.--
F .-?
z
c z
5
.-
E
‘C
.- T
a
6
c
EL g
ii
.-
.-; ‘C
.-s
0) 2
5 2 k -z
8 iii 0
-
2 z --8 .-z- -2 -z
cll
3002 c9 c9
- -c9 c9
0
T- =E
-
T- V- -7
-
O
7 r
- -z z -z -2
OCV
m c9
- -c9 c9
gg 0
- z
-
- ‘c --
0
-
-z r -2 -z
2 z 8 zii z!3
= C C C
Table B.9 - Data Elements by Message Cla :ontinuec
Condition Codes (1987) Condition Cod s (1993) IN
0
Bit 1510 1520 1530 1540 T
Reconciliation messages, continued E
(1987) I 1521 -T-i
1502 1512 1522 1532 1542
1503 1523 I I
87 M I13 IM 113 I credits, reversal amount I 87 M
IIM
86 M 113 IM 113 I debits, amount I 88 M IM
89 M I13 IM I13 I debits, reversal amount I 89 M IM 13 IM
I authorizations, reversal number I 90 M IM
97 M IM ~ IM IM Iamount, net reconciliation I 97 M IM M M
v_
99 M Ih IM IM ISettlement institution identification code I 99
100 19 19 19 19 receiving institution identification code 100 19 19 i19 ~19 19
credits, chargeback amount 105 M IM 13 IFJI I
I I I debits, chargeback amount I 106 M IM 13 IM I
I I I I credits, chargeback number I !07
I I 1debits, chargeback number I 108 13 IM I
I I I I credits, fee amount I 109 13 I01 I
I I I I debits, fee amount I 110 01 lo1 13 lo1 I
v,
0
..
--
Ta' Ae 3.9 l mData Elements by Message Clas continued
Sf
tdition C ,des (1 w Condition Cod
Bit Bit
Administrative messages
WV 0610 0620 0630 (1993)
0621
1 M 11 M 11 bit map extended 1
7 M M M M date and time, transmission 7 ----tl-
11 M M M M systems trace audit number 11 M IME -w lnl
12+13 date and time, local transaction 12 ME IM
20 09 09 country code, primary account number 20
21 09 09 country code, forwarding institution 21
function code 24
33 10 10 10 10 forwarding institution identification code 33 v
39 action code (was response code) 39
transport data 59
66 09 09 09 09 country code, receiving institution ~ 66
data record 1 72
transaction destination institution identification
code
, MElM ILII
transaction originator institution identification code / 94 ME IM
100 19 119 19 19 receiv tng institution identification code 1 loo
1
,

Condition Cone tion C ,des (1993)
codes
Bit Bit
(1987) Fee Collection Messages
(1987) (1993)
1720 1730 1742
n/a
t- 1721 I
1 I bit map extended I 1
2 I primary account number I 2 M IME M M ME
l1 I systems trace audit number I 11 M IME M +M ME

12+13 1 date and time, local transaction I 12 M IME M M IME
15 I function code I 24 M I M M I
date, reconciliation I 28 I12 12 I12
reconciliation indicator I 29 I14 23 I14 23
32 I acquiring institution identification code I 32 M ME M M IME
33 I forwarding institution identification code I 33 +10 10 10 10 110
action code (was response code) I 39 IM M IM
amounts, fees I 46 M IME M M IME
transport data I 59 116 I 116
I
I 100I receiving institution identification code 100 119 119 19 119 119
. -
IS0 8583 : 1993 (E)
Z E C
-a -n -J -J
-r -z
0
T- z
<DO 2 2
r”
- -- -
3- 0
-if2 -V- z z
to si s
--
0
-g -
-2
0
-kc -e- r r
T ii? s
- tc 3
- -
z
g
.-5 .-5
s
s5
.- 5
.-
.=
:
-0
.-
5 E 45
.-5 .-E .-s .- g
45
.-E
5
.t: 3 3 .-s 5
.-sor -cI
.-0 .e 5
5 % .-5 z .r: .t: 2
.-
.-5
E 5
z E .-E .-E z.-c .=
z
.-E?
.-iii
k 2 -E! z 45.- .-F z5 ir 3
E
.= -5 aa. 2 .-5E .2 3
-0 .-E .- .-2 c .-55
.-ul
2 0 0L
f
b 3
.- -E
.- 0% % .- 22
Q, .- c .-I! z 5 .-zc
.-E : .-z E 0
.- %
G i=
5
0
.-3 .-P fi .-5 5 F
.=
F ‘i; l=
.->
f 2
ti 5 -z
Q, a LD 2 .-
3
aI iz 5 6 i
r 5 5-g 2 0
7J 2;
- - -0 m
-
3
-
i!!
-
0
-8 20 i=
0
z -r -
-
2- - -
0
- t3
0
-
- -
0
-
-
8
IS0 8583 : 1993 (E)
B.3.7 Message flows B.3.7.3 File action messages
The principal differences in message flow are: Generic routing is used.
a) Advice response messages 1x3x are no longer

optional. A distinction is made between advices
request advice notification
1x2x, to which a response 1x3x must be given and
notifications 1x4x, to which a response must not be 1304 1324 1344
given. -> -> ->
b) Where message routing is not clearly acquirer to
1314 1334 (no response)
card issuer or vice versa (e.g., network management <- <-
messages), generic routing is introduced i.e.,
transaction originator to transaction destination. (response (response
mandatory) mandatory)
c) There are no completion messages.
The implications of these differences by message

class are shown below. For the sake of clarity repeat
messages have been omitted from the following B.3.7.4 Reversal messages
series of diagrams.
There are no reversal request messages. Reversals
are sent from the acquirer to the card issuer.
8.3.7.1 Authorization messages
The possible message sets are:

1420 1440
request advice notification -> ->
1100 1120 1140 1430 (no response)

-> -> -> <-
1110 1130 (no response) (response

mandatory)
B.3.7.5 Chargeback messages
There are no chargeback request messages.

B.3.7.2 Financial messages Chargebacks are sent from the card issuer to the
acquirer.
The flow is equivalent to the 1 lxx class.
request advice notification request advice notification
1200 1220 1240 1422 1442

-> -> -> -> ->
1210 1230 (no response) 1432 (no response)

<-
mandatory) mandatory) (response

mandatory)
107
ISO8583:1993(E)
B.3.7.6 Reconciliation messages B.3.7.8 Fee collection messages
Reconciliation messages can be generated by the There are no fee collection request messages. Fee
acquirer as in (i) or by the card issuer as in (ii). collection messages can be generated by the acquirer
as in (i) or by the card issuer as in (ii).

(3I
1500 1520 1540 (3I
-> -> ->
1720 1740
-> ->
<- <-
1730 (no response)
<-
(response (response
(response
mandatory)
00
1502 . 1522 1542
-> -> -> (ii)
1722 1742
-> ->
<- <-
1732 (no response)

(response (response
<-
(response
mandatory)
B.3.7.7 Administrative messages

B.3.7.9 Network management messages
Generic routing is used.
Generic routing is used.

1604 1624 . 1644
-> -> -> 1804 1824 1844
-> -> ->
<- <- 1814 1834 (no response)
<- <-
(response (response
mandatory) mandatory) (response (response
mandatory) ma;rdatoryj
108
ISO8583: 1993(E)
B.3.7.10 Exception message flows Case 4 : Acquirer does not receive 1110 response.
Acquirer stands in for card issuer. Full reversal
IS0 8583 (1993) addresses exception message flows followed by advice for the stand-in transaction.
(see 5.2.12 of the IS0 8583:1993). The following cases
are considered. Acquirer Card
Issuer
Case 1 : Acquirer receives 1110 response. Transaction 1100 -----> original request
is not completed at the point of service. Full reversal.
1420 ----->
< ---- Id&30 reversal
Acquirer Card
Issuer 1120 ----->
< ---- 1130 advice
1 loo -0---> original
transaction
< --- 1110 Notes:
1420 -00-0> Cases I and 2 cover the situations where the transaction fails
< ---- 1430 reversal completely, either on the acquirer side (I), e.g., the customer
went away, or the card issuer side (2), e.g., the card issuer host
is unavailable.
If stand-in is provided by the acquirer in Case 2, the 1120 can

be used to advise the card issuer of the stand-in authorization,
Case 2 : Acquirer does not receive 1110 response. No the 1420 having nullified the original authorization request.
stand in. Full reversal.
Case 3 is the situation where the card issuer has approved the
transaction but this completes only partially, e.g., the
authorization request is for French Francs 2000 but the
Acquirer Card
customer only receives French Francs 1500 worth of services.
Issuer Note that a partial reversal may be used only if the 1110 has
been received from the card issuer.
1100 -----> original request
Case 4 occurs when the card issuer 1110 response is not
received and the acquirer is allowed to stand-in for the card issuer.
1420 -----> The 1420 nullifies the original authorization request and the
< ---- 1430 reversal 1120 advises the card issuer of the stand-in authorization.
Technically the 1120 could additionally be used in Case 3 as an

advice of the result of the partial transaction. The end result on
the customer’s open-to-buy is the same. There is, however, an
issue of responsibility in that the 1120 is a separate
Case 3 : Acquirer receives 1110 response. Transaction transaction, and therefore strictly speaking not covered by the
partially completed at the point of service. Partial approval given by the card issuer in the 1110.
reversal.
B.4 Further advice

Acquirer Card
Issuer Further advice is given with regard to:
1100 -----> original transaction a) usage of amou nt data elements in auth orizat ion,
fin ancial, reversal and chargeback transact ions;
< ---- 1110
b) reconciliation processing;
1420 -----> c) fee collections;
< ---- 1430 partial reversal
d) usage of fee amount data elements in
authorization, financial, reversal, chargeback and
fee collection messages.
These are areas in IS0 8583:1993 which have been

substantially changed or are completely new,
109
IS0 8583 : 1993 (E)
B.4.1 Usage of amount data elements authorized amount (US $100) becomes the original
amount, transaction.
B.4.1.3 General
The new amount (US $80) could be an accurate
Amount data elements are used differently in IS0 8583:1993.
amount or an estimated amount depending upon
The amount, transaction data element now contains
whether the function code appearing in the
the actual amount transaction in authorization and
authorization request message is 102 or 103.
financial messages and the amount to be reversed or
charged back in 14xx messages. c) Re-submission - if an authorization is
re-submitted (because the previous authorization
This was not always the case in IS0 8583:1987. has been denied or rejected) the amount,
transaction (US $100) remains the same. This could
In authorization and financial messages, the amount, be an accurate or an estimated amount depending
transaction data element was formerly used to send on whether the function code appearing in the
the originally requested amount with declines or authorization request message is 104 or 105.
rejected advices. Under the revised standard, the
amount, transaction data element contains zero, with d) Supplementary Authorization - If a supplementary
the originally requested amount sent in original authorization is required (because an additional
amount, transaction (contained within a new data amount needs to be approved) then the incremental
element, amounts, original). amount (e.g. US $50) is sent in the amount,
transaction data element. This could be an accurate
In reversal messages (both issuer and acquirer or an estimated amount depending on whether the
generated) the actual amount transaction was function code appearing in the authorization
formerly sent in the replacement amount data request message is 106 or 107.
element. The originally approved amount was sent in
the amount, transaction data element. Under the The previous approved amount (US $100) may be
revised standard, the amount to be reversed or sent in the original amount, transaction data
charged back is now sent in the amount, transaction element. If a further supplementary authorization is
data element and the originally approved amount in required (e.g. US $70) the amount in the original
original amount, transaction. The replacement amount, transaction data element will be the sum of
amounts data element has been deleted from the the previous approved amounts (US $150).
revised standard.
e) Partial Approval - Where the card issuer cannot
approve the full amount contained in the
B.4.1.2 Authorizations authorization request message, two amount data
elements are returned in the authorization response
The follow ing types of authorization transacti ons are message.
defi ned:
The amount, transaction data element is used to
a) Original Authorization - For an original indicate the amount which the Issuer is prepared to
authorization only one amount data element is approve (e.g. US $60). The original amount,
used, namely amount, transaction (e.g., US $100). transaction data element is used to indicate the
originally requested amount (US $100).
This could be an accurate amount or an estimated
amount depending upon whether the function code For a partial approval, action code 002 or 006 are
appearing in the authorization request message is 100 required.
or 101. If the final amount, transaction is available,
the amount, transaction is always an accurate f) Declined or rejected authorizations -Where the
amount. This applies to all types of authorization. card issuer declines an authorization request or
rejects an authorization advice, two amount data
b) Replacement Authorization - If a replacement elements are returned in the relevant response
authorization is required (because the transaction message. The amount, transaction data element
amount is now different than that previously contain zero. The original amount, transaction data
authorized) the new amount (e.g., US $80) becomes element must contain the originally requested
the amount, transaction and the previously amount (US $100).
110
IS0 8583 : 1993 (E)
B.4.1.3 Financial transactions f) Declined or rejected financial transaction -

Where the card issuer declines the financial request or
The following types of financial transactions are rejects the financial advice, two amount data elements
defined: are returned in the relevant response message. The
amount, transaction data element contains zero.
a) Original financial transaction e- For an original The original amount, transaction data element
financial request message, only 0 ne data element is contains the originally requested amount (US $120).
used, namely amount, transaction (e.g. US $120).
For an original financial request message, Function B.4.1.4 Reversals

Code 200 is used.
The following types of reversal transactions are
b) Previously authorized financial transaction - For defined:
a previously authorized financial request message
(where the amount is the same as that previously a) Full reversal - For a full reversal, only one
authorized - as indicated by Function Code 201) amount data element is required, namely amount,
only one amount data element is required, namely transaction (e.g. US $200). This contains the amount
original amount, transaction. This contains the to be reversed. A full reversal uses message reason
amount previously authorized (US $120). codes 4000-4020 (except 4004).
For a previously authorized financial request b) Partial reversal - For a partial reversal, two
message (where the amount is not the same - amount data elements are used. The amount,
as indicated by Function Code 202), two amount transaction data element is used to indicate the
data elements are used. The amount, transaction amount to be reversed (e.g. US $150). This amount
data element is used to indicate the new amount is always less than the original amount. The original
(e.g. US $90). The original amount, transaction amount, transaction data element is used to indicate
data element is used to indicate the previously the amount, originally approved (US $200). A partial
authorized amount (US $120). reversal uses message reason code 4004.
c) Re-submission - If a financial request is A partial reversal should never be used for a full
re-submitted (because the previous request has reversal. Amount, transaction and original amount,
been denied or rejected) the amount, transaction transaction cannot be equal in that case.
(US $120) remains the same. For a resubmitted
financial request, function code 203 is used.
B.4.1.5 Chargebacks
d) Representment - For a representment, two
amount data elements are used. The amount, The following types of chargeback transactions are
transaction data element is used by the acquirer to defined:
indicate funds to be recovered from the card issuer.
The original amount, transaction data element is a) Full chargeback - For a full chargeback, only one
used by the acquirer to indicate the original amount data element is required, namely amount,
chargeback amount. transaction (e.g. US $200). This contains the amount
to be charged back and is always equal to the
Function codes 205,206 or 207 are used to indicate amount originally approved (US $200). A full
the first, second or subsequent representment. chargeback uses message reason codes 4500-4999
and function codes 450-452.
e) Partial approval - Where the card issuer cannot
approve the full amount contained in the financial b) Partial chargeback - For a partial chargeback,
request message, two amount data elements are two amount data elements are required. The
returned in the financial request response message. amount, transaction data element is used to indicate
The amount, transaction data element is used to the amount to be charged back (e.g. US $150). This
indicate the amount the card issuer is prepared to amount is always less than the original amount. The
approve (e.g. US $80). The original amount, original amount, transaction data element is used to
transaction data element is used to indicate the indicate the amount originally approved (US $200).
originally requested amount (US $120). For partial A partial chargeback uses message reason codes
approvals, action code 002 is required. 4500-4999 and function codes 453-455.
111
ISO8583:1993(E)
B.4.2 Reconciliation processing d) For all reversal (14X0) messages with an original
processing code of 20-29 and original MTI = 12Xx:
B.4.2.1 General
add 1 to the debits, reversal number and add the
IS0 8583:1993 provides a simplified and consistent amount, transaction to the debits, reversal amount.
structure for performing reconciliation for both
transactions and fees. e) For all chargeback (14X2) messages with an
original processing code of 00-19:
A summary of the main improvements in the revised
standard is given below: add 1 to the credits, chargeback number and add the
amount, transaction to the credits, chargeback
- Clarification of the terms reconciliation and amount.
settlement as used by the standard.
f) For all chargeback (14X2) messages with an
- Consolidation of fee-related data elements. original processing code of 20-19:
- lncorportation of fee collections and payment add 1 to the debits, chargeback number and add the
transactions into the reconciliation process. amount, transaction to the debits, chargeback
-A revised and more detailed description of the amount.
processes involved in calculating reconciliation g) For all fee collection (17Xx) messages:
amounts and counts.
If the amount, fee X is C:
- Provision of a mechanism for performing
checkpoint reconciliation.
add the amount, fee to the credits, fee amount
(based on fee type).
B.4.2.2 Accumulation If the amount, fee X is D:
The acquirer and card issuer (or their agents) add the amount, fee to the dedits, fee amount
accumulate counts and amounts of transactions (based on fee type).
and/or fees during message processing. A net amount
is then calculated by each reconciliation entity for the h) For all other fees associated with 1 IXX, 12XX and
reconciliation period. 14XX messages :
Several examples are given in Table B.10 to illustrate If the amount, fee X is C:
the revised structure in IS0 8583:1993 used for add the amount, fee to the credits, fee amount
reconciliation processing. (based on fee type).
The following general rules apply to the reconciliation If the amount, fee X is D:
process:
add the amount, fee to the dedits, fee amount
a) For all financial (12Xx) messages, with a (based on fee type).
processing Code of 00-19 (debit):
i) Reconciliation records are always to be in the
same currency. Multi-currency reconciliation
add 1 to the debits, number and add the amount,
necessitates different records for each currency.
transaction to the debits, amount.
b) For all financial (12Xx) messages, with a j) If the currency of reconciliation is different from
processing code of 20-29 (credits): the transaction currency, the amount, reconciliation
is used instead of amount, transaction.
add 1 to the credits, number and add the amount, k) If the amounts, fees contains an amount,
transaction to the credits, amount. reconciliation fee sub-element (i.e. the currency
c) For all reversal (14X0) messages, with an original code, fee is different from the currency of
processing code of 00-19 and original MTI = 12Xx: reconciliation), this is used in reconciliation in place
of the amount, fee.
add 1 to the credits, reversal number and add the
I) Amounts, original and amounts, original fees are
amount, transaction to the credits, reversal amount.
not used in the reconciliation process.
112
IS0 8583 : 1993 (E)
B.4.3 Fee collection card issuer or from the card issuer to the acq uirer,
inde penden t of ‘who sent the o lriginal message.
IS0 8583:1993 includes a new message series (17Xx)
for the collection of fees. The types of fee supported by fee collection messages
are denoted by the fee type code (contained within the
Fee collection messages can be in either direction ;
amounts, fees data element). The list of fee type codes
acquirer to card issuer or card issuer to acquirer. A list
can be found in clause A.6.
of message types in the 17XX series can be found in
Table B.9. Fee collections cannot be denied or reversed.
However, an acquirer or a card issuer can send a
A list of mandatory and conditional data elements subsequent fee collection message with a different X
associated with 17XX messages can be found in
indicator (i.e. C or D) associated with the amounts,
Table B.9. fees data element. A debit is a fee due to the acquirer.
A credit is a fee due from the acquirer.
Fee collections have a financial impact and affect
reconciliation (see table B.lO). Fee collections do not
A fee toll ection, number is available to provide a
affect the cardholder account.
reconciliat ion cou nt of fee c ,011ections.
For information on the usage of the amounts, fees data
Fee collection messages can be used, if required, to
element, which is mandatory for fee collection messages,
consolidate fees for reconciliations separately from
see B.4.4. Fee collection messages may contain multiple
related transaction amounts.
fees. These fees may be due from the acquirer to the
113
Table B.10 - Reconciliation processing examples
(Example 1)
I I
T credits debits
e
c I C
T c r c
proc amt, amt, fee 0 e h o e h
fee type comments u v amt amt
code txn fecon amount g amt u v g amt
n # b amt amt fees n#b fees
t k t k
# #
3. ,
1100 00 5ooo 00 D50 authorization with transaction fees 50
1
1220 20 financial advice 1 2500
4 1
1220 00 00 DlOO financial advice with transaction 1 100
fee
A.
1422 20 2500 01 C25 full chargeback of (2) by the 25 1 2500
issuer, with processing fee
.I 4
1720 O? fee collection by acquirer with
15 D1300 mulitiple fees
11 0500
-- .L 4
1420 00 5000 Cl00 full reversal of (3) including 1 5ooo 100
transaction fee
3.
1200 00 3ooo 1000 financial advice, currency differs
from reconciliation currency
1
partial chargeback of (4) 1 I400
TOTALS 1 1 1 2500 5ooo 1400 125 t-l3950
.e- -
Online accumulation after each event is: Amount net reconciliation is :
1) D50 5) D 8925 , 2500+5000+400+125 LESS 6000 + 2500 t 3950 EQUALS D 4425

2) C 2450 6) D 3825
3) D 2650 7) D 4825
4) D 5125 8) D 4425
Table B.10 - Reconciliation processing examples
(Example 2)
- ---
credits T debits
- -
r C c r C
8 h 0 e h
proc amt, amt, fee
MT-I fee type comments V 8 rev chgbk amt U V 9 rev chgbk amt
code txn recon amount amt amt
# b amt amt fees n # b amt amt fees
k t k
# #
-- -
1 1220 00 8000 00 075 financial advice with transaction T- 75
fee
-
2 1420 00 2500 00 c75 partial reversal of (1) reverse 2500 75 50
01 D50 transaction fee; charge processing
fee
- -
3 1722 01 Cl000 fee collection by issuer, multiple 1000
15 0500 fees
- -
4 1200 20 01 DlOO financial request with proc=et-sing
fee
-
5 1420 20 1000 01 Cl00 partial reversal of (4) with reversal 100 1ooo
processing fee
-
6 1200 00 8ooo 2000 financial advice currency differs
from reconciliation currency
~- ~ _~
7 1200 20 4509 00 Cl00 financial request with transaction 4500 100
fee
-
8 1420 iD1OO full reversal of (7) including 4500
transaction fee
TOTALS <1 1275 14506 1006 0 825
Z -7500-2500 0 - - -
Online accumulation after each event is: Amount net reconciliation is :
1) D 8075 5) D 3050 7500 t 2500 + 1275 LESS 14500 t 1000 t 825 EQUALS D 5050
2) D 5550 6) D 5050
3) D5050 7) D 0450
4) D 2150 8) D5050
IS0 8583 : 1993 (E)
B.4.4 Usage- of fee amount data elements b) If amounts, fees is used it may affect
reconciliation.
The following data elements have been deleted and
replaced by the new data element amounts, fees: c) If the original authorization or financial
transaction is reversed, the amounts, fees in the
- amount, transaction fee; reversal contains the new fee amounts. The new
- amount, transaction processing fee; fee amounts may be greater than, less than or
equal to the amounts of the original fees.
-amount, settlement fee;
- amount, settlement processing fee. d) The amounts, original fees in a reversal is used to
indicate the amounts of the original fees.
The following data elements which were part of e) The amounts, fees and amounts, original fees
replacement amounts, have been deleted and replaced data elements consist of six sub-elements:
bythe new data element, amounts, original fees:
-fee type code;
- actual amount, transaction fee;
-currency code;
- actual amount, settlement fee.
- amount, fee;
In addition, these two new data elements allow for
-conversion rate, fee;
fees to be expressed in a currency other than that of
either the transaction or reconciliation. - amount reconciliation fee;
Amounts, fees and amounts, original fees are used as -currency code, reconciliation.
described below:
Six different sets of values can be included in the
a) Amounts, fees is optional in authorization, amounts, fees or amounts, original fees data
financial, reversal and chargeback transactions. It is elements.
mandatory in fee collection transactions.
116
ISO8583:1993(E)
Annex C
(informative)
Forms for application for institution

identification codes and all other codes
Form 1 : Application for Institution Identification codes
Form 2 : Request for codes within IS0 8583
117
ISO8583:1993 (E)
Application for Institution Identification code
This application is submitted in accordance with IS0 8583.
‘he proposal (to be completed by applicant):
Institution name:
Address to be registered (maximum two lines, 30 characters per line):
Principal contact in institution:
Telephone Number: Fax/Telex number:
Address for correspondence/billing: Address to return application:
Anticipated first use:
Check Institution Identification code data elements applicable:
Acquiring Authorizing Forwarding Receiving
Settlement Transaction Destination Transaction originator
To be completed by IS0 8583 Registration Authority:
Application approved by:
Date: Signature:
Institution Identification Code or other action taken:
RETURN TO : American Bankers Association

c/o ASC X9 Secretariat
1120 Connecticut Avenue, N.W.
Washington, D.C. 20036 U.S.A.
118
ISO8583:1993 (El
Request for codes for use within IS0 8583
This application is submitted in accordance with IS0 8583.
The proposal (to be completed by applicant):
Institution name:
Codes requested (include data element name, code value and code description, attach a seperate list, if
necessary):
Principal contact in institution:
Telephone Number: Faflelex number:
Address for correspondence/billing: Address to return application:
Anticipated first use:
To be completed by IS0 8583 Codes Maintenance Agency:
Codes approved by:
Date: Signature:
To be completed by IS0 8583 Codes Maintenance Agency Secretariat:
Codes approved or other action taken:
RETURN TO : Association Francaise de Normalisation

Tour Europe - Cedex 7
92049 Paris La Defense - France
119
This page intentionally left blank
This page intentionally left blank
IS0 8583:1993(E)
UDC 336.722.24:681.327.638
DescrOptors: banking, banking documents, financial documents, identity cards, credit cards, information interchange, processing,
storage devices, magnetic recording, messages, specifications, structures, formats, data, coded representation.
Price based on 119 paaes

Iso8583 1993

Uploaded by

Copyright:

Available Formats

You might also like

Iso8583 1993

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Iso8583 1993

Uploaded by

Copyright:

Available Formats

INTERNATIONAL

Financial transaction card originated

Messages initie’s par carte de transaction financi&re - Spkifications

Normative references ....................................................................... 1

Message structure ............................................................................ 3

Message and transaction flows ....................................................... 41

Message and transaction matching ................................................ 50

Maintenance Agency and Registration Authority .......................... 50

Guidance on the use of this International Standard ....................... 51

A Code listings .................................................................................... 52

B Conversion guide . . ..I....................................................................... 72

B.3.3 Message structure .......................................................................... 75

C Forms for application for institution identifiers and codes . . . . . . . . . . 117

IS0 (the International Organization for Standardization) is a worldwide

Draft International Standards adopted by the technical committees are

Annex A forms an integral part of this International Standard. Annexes B and C

This International Standard introduces the concept of a message version

Data representation used in individual systems is subject to the commercial

Financial transaction card originated messages -

1 Scope IS0 4909:1987, Bank cards - Magnetic stripe data

b) Registration Authority IS0 78 13: 1990, /den tification cards - Financial

IS0 3166: 1988, Codes for the representation of names

3.15 inquiry: An authorization transaction that

3.32 settlement: A transfer of funds to complete one 4.1 .l Message

Third Position - Message Function

Each message identified in this International 4.1.2 Message Repeats

Table 1 - Amounts in types of authorization messages

In request, advice and notification messages:

Authorization type Function code Amount, transaction Original amount, transaction

original 100,101 transaction amount ma

replacement 102,103 new amount originally authorized amount

resubmission 104,105 transaction amount --

I supplementary 1 106,107 I additional amount I sum of previous approvals, if I

part;al approval we approved amount originally requested amount

I decline/reject , -- , I zero I originally requested amount I

iv) Representment - a financial transaction

Table 2 -Amounts in types of financial transaction messages

In request, advice and notification messages:

I Financial type I Function cod2 I Amount, transaction I Original amount, transaction I

previously 201,202 new amount originally authorized amount

resubmission 203,204 transaction amount

representment 205,2@6,207 transaction amount amount of chargeback

full approval ww transaction amount -w

partial approval -w approved amount originally requested amount

decline/reject Be zero originally requested amount

4.1.3.3 File action message class Type of Amount, Original

4.1.3.4 Reversal message class

A reversal shall be used to partially or completely II

equal to the original amount as shown in table 3. II adjustment I 02,22 I 200 II

c) Whenever the acquirer times out waiting for a return 20 200

i) Totals provided - all amounts and number

f) Reconciliation advice response m essages shall

Table 6 - Message type identifiers

MT! MESSAGE PURPOSE FROM TO USAGE

1100 authorization request requests approval for an acquirer issuer

1101 authorization request repeat

1120 authorization advice advises of an authorization acquirer issuer