ISO 8583-3:2003
(Main)Financial transaction card originated messages — Interchange message specifications — Part 3: Maintenance procedures for messages, data elements and code values
Financial transaction card originated messages — Interchange message specifications — Part 3: Maintenance procedures for messages, data elements and code values
ISO 8583-3:2003 establishes the role of the maintenance agency (MA) and specifies the procedures for adding messages and data elements to ISO 8583-1 and to codes listed in Annex A of ISO 8583-1. The responsibilities of the MA relate to all message type identifiers and classes, data elements and sub-elements, dataset identifiers and codes within ISO 8583-1, with the exception of Institution Identification Codes.
Messages initiés par cartes de transaction financière — Spécifications d'échange de messages — Partie 3: Procédures de maintenance pour messages, éléments de données et valeurs de code
General Information
Relations
Standards Content (Sample)
INTERNATIONAL ISO
STANDARD 8583-3
Second edition
2003-05-01
Financial transaction card originated
messages — Interchange message
specifications —
Part 3:
Maintenance procedures for messages,
data elements and code values
Messages initiés par cartes de transaction financière — Spécifications
d'échange de messages —
Partie 3: Procédures de maintenance pour messages, éléments de
données et valeurs de code
Reference number
ISO 8583-3:2003(E)
©
ISO 2003
---------------------- Page: 1 ----------------------
ISO 8583-3:2003(E)
PDF disclaimer
This PDF file may contain embedded typefaces. In accordance with Adobe's licensing policy, this file may be printed or viewed but
shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In
downloading this file, parties accept therein the responsibility of not infringing Adobe's licensing policy. The ISO Central Secretariat
accepts no liability in this area.
Adobe is a trademark of Adobe Systems Incorporated.
Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation
parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In
the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below.
© ISO 2003
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means,
electronic or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or
ISO's member body in the country of the requester.
ISO copyright office
Case postale 56 • CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail copyright@iso.org
Web www.iso.org
Published in Switzerland
ii © ISO 2003 — All rights reserved
---------------------- Page: 2 ----------------------
ISO 8583-3:2003(E)
Contents Page
Foreword. iv
1 Scope. 1
2 Normative references . 1
3 Terms and definitions. 1
4 Application procedures. 1
4.1 Application procedure for changes to ISO 8583-1 . 1
4.2 Criteria for approval of an application for changes to ISO 8583-1 . 2
5 Appeal process . 2
5.1 Appeal bodies. 2
5.2 Information to be provided. 3
6 Balloting process . 3
7 Sponsoring authority. 3
7.1 Eligibility to become a sponsoring authority. 3
7.2 Responsibilities. 3
8 Registration and maintenance management group (RMMG) . 4
8.1 Constitution . 4
8.2 Responsibilities. 4
8.3 Voting procedures . 5
9 Maintenance Agency . 5
9.1 Appointment . 5
9.2 Resignation. 5
9.3 Responsibilities. 6
10 Publication of changes to ISO 8583-1. 6
Annex A (normative) Information to be provided for changes to ISO 8583-1 . 7
© ISO 2003 — All rights reserved iii
---------------------- Page: 3 ----------------------
ISO 8583-3:2003(E)
Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards bodies
(ISO member bodies). The work of preparing International Standards is normally carried out through ISO
technical committees. Each member body interested in a subject for which a technical committee has been
established has the right to be represented on that committee. International organizations, governmental and
non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely with the
International Electrotechnical Commission (IEC) on all matters of electrotechnical standardization.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.
The main task of technical committees is to prepare International Standards. Draft International Standards
adopted by the technical committees are circulated to the member bodies for voting. Publication as an
International Standard requires approval by at least 75 % of the member bodies casting a vote.
Attention is drawn to the possibility that some of the elements of this document may be the subject of patent
rights. ISO shall not be held responsible for identifying any or all such patent rights.
ISO 8583-3 was prepared by Technical Committee ISO/TC 68, Banking, securities and other financial
services, Subcommittee SC 6, Retail financial services.
This second edition cancels and replaces the first edition (ISO 8583-3:1998), which has been technically
revised.
ISO 8583 consists of the following parts, under the general title Financial transaction card originated
messages — Interchange message specifications:
Part 1: Messages, data elements and code values
Part 2: Application and registration procedures for Institution Identifier Codes (IIC)
Part 3: Maintenance procedures for messages, data elements and code values
iv © ISO 2003 — All rights reserved
---------------------- Page: 4 ----------------------
INTERNATIONAL STANDARD ISO 8583-3:2003(E)
Financial transaction card originated messages — Interchange
message specifications —
Part 3:
Maintenance procedures for messages, data elements and code
values
1 Scope
This part of ISO 8583 establishes the role of the maintenance agency (MA) and specifies the procedures for
adding messages and data elements to ISO 8583-1 and to codes listed in Annex A of ISO 8583-1.
The responsibilities of the MA relate to all message type identifiers and classes, data elements and sub-
elements, dataset identifiers and codes within ISO 8583-1, with the exception of Institution Identification
Codes.
2 Normative references
The following referenced documents are indispensable for the application of this document. For dated
references, only the edition cited applies. For undated references, the latest edition of the referenced
document (including any amendments) applies.
ISO 8583-1, Financial transaction card originated messages — Interchange message specifications — Part 1:
Messages, data elements and code values
ISO 8583-2, Financial transaction card originated messages — Interchange message specifications — Part 2:
Application and registration procedures for Institution Identification Codes (IIC)
3 Terms and definitions
For the purposes of this document, the following terms and definitions given in ISO 8583-1 and the following
apply.
3.1
sponsoring authority
entity that submits requests for changes to ISO 8583 (all parts) to the RMMG
4 Application procedures
4.1 Application procedure for changes to ISO 8583-1
An applicant shall apply to the appropriate sponsoring authority to request approval of a new message type
identifier or class, data element or sub-element, dataset identifier or code value by providing the information
specified in Annex A.
© ISO 2003 — All rights reserved 1
---------------------- Page: 5 ----------------------
ISO 8583-3:2003(E)
An applicant shall also provide the information specified below:
a) date of request;
b) name of the applicant;
c) address for correspondence (name, address, telephone, email address and fax/telex numbers, etc. of the
applicant);
d) date of implementation (indicate if special conditions of urgency apply).
4.2 Criteria for approval of an application for changes to ISO 8583-1
Any changes approved by the RMMG shall be uniquely identified within a specific edition of the International
Standard so as to allow backwards compatibility with existing implementations of the same version.
Backwards compatibility within a given version of the International Standard is of utmost importance. There
shall be no confusion as to existing message type identifiers or classes, data elements or sub-elements,
dataset identifiers or code values introduced by a proposed change.
The use of bit maps allows for the proper validation and acceptance or rejection of messages by
implementations of ISO 8583 (all parts) for functions that are supported and allows unsupported data
elements and message types to be ignored.
An application for a change to the International Standard shall be approved by the RMMG when the following
conditions exist:
a) the requested message type identifier or class, data element or sub-element, dataset identifier or code
does not duplicate a message type identifier or class, data element or sub-element, dataset identifier or
code value already included in the International Standard;
b) the requested message type identifier or class, data element or sub-element, dataset identifier or code
value is intended for use within an implementation of ISO 8583-1 and is to be included in it;
c) the request does not concern the change in meaning or deletion of an existing message type identifier or
class, data element or sub-element, dataset identifier or code value (this can only be done by a revision
of ISO 8583-1);
d) the request does not concern the change in meaning or deletion of an existing data element condition
code (this can only be done by a revision of ISO 8583-1);
e) the request is not for the reassignment of an existing message type identifier or class, data element or
sub-element, dataset identifier or code value (this can only be done by a revision of ISO 8583-1);
f) the request is consistent with existing relevant International Standard, including those published by other
ISO technical committees;
g) the information provided in the application is complete.
5 Appeal process
5.1 Appeal bodies
Where an application has been rejected by the RMMG, the applicant may appeal to ISO through the
secretariat of ISO/TC 68/SC 6. Applicants may submit, for appeal, applications that have been rejected by
ISO/TC 68/SC 6 to the ISO Central Secretariat.
2 © ISO 2003 — All rights reserved
---------------------- Page: 6 ----------------------
ISO 8583-3:2003(E)
5.2 Information to be provided
Where an application for a new message type identifier or class, data element or sub-element, dataset
identifier or code value has been rejected, the following information shall be provided by the applicant to the
relevant appeal body in support of the appeal:
a) statement for which rejection is disputed and why the applicant believes that the rejected application fulfils
the criteria for acceptance;
b) statement of special circumstances whereby a specific requirement of the rejected application can be met.
6 Balloting process
Where an application for a new message type identifier or class, data element or sub-element or dataset
identifier has been submitted and approved by the RMMG, it shall be necessary to create an amendment to
ISO 8583-1 that documents the changes. The amendment (e.g. technical changes to the document) shall be
balloted to ISO members using the most expeditious ISO amendment procedure.
If the change is only for a new code value for an existing data element documented in Annex A of ISO 8583-1,
the RMMG can approve the request with no need for an ISO ballot.
7 Sponsoring authority
7.1 Eligibility to become a sponsoring authority
The following bodies may act as a sponsoring authority in processing applications for a new message type
identifier or class, data element or sub-element, dataset identifier or code value:
a) any national member body of ISO (or agent appointed to act for its national member body);
b) ISO/TC 68/SC 6.
7.2 Responsibilities
The responsibilities of a sponsoring authority shall be:
a) to fully comply with the procedures for applications described in this part of ISO 8583 for new message
type identifiers or classes, data elements or sub-elements, dataset IDs or code values and to ensure that
the applicant uses ISO 8583-1;
b) to process, within 30 days of receipt of the request, applications for new message type identifiers or
classes, data elements or sub-elements, dataset IDs or code values from within their countries or areas of
responsibility;
c) to notify the applicant in writing, within 30 days of receipt of the application, as to the disposition of their
application;
d) to forward to the MA those sponsored requests for new message type identifiers or classes, data
elements or sub-elements, dataset IDs or code values that shall be used for the purposes described in
this part of ISO 8583 and that meet the approval criteria in 4.2;
e) to respond to general enquiries covering this part of ISO 8583.
© ISO 2003 — All rights reserved 3
---------------------- Page: 7 ----------------------
ISO 8583-3:2003(E)
8 Registration and maintenance management group (RMMG)
8.1 Constitution
In order to effectively manage the contents of ISO 8583-1, TC 68/SC 6 has established an RMMG, which is
empowered to act on its behalf.
The following chart shows the relationship of the RMMG to ISO TC68/SC6, the registration authority that
handles IICs as defined in ISO 8583-2 and the maintenance agency as defined in this part of ISO 8583.
Figure 1 — Relationship of maintenance bodies
The RMMG shall be made up of:
a) a representative of the MA, who shall be a non-voting member of the RMMG and shall be expected to
attend all meetings;
b) the convener;
c) the secretary.
In addition, each member of ISO/TC 68/SC 6 is entitled to nominate one delegate and one alternate to the
RMMG. The alternate may attend all meetings, but is entitled to vote only in the absence of the principal
delegate.
8.2 Responsibilities
The responsibilities of the RMMG shall be:
a) to act on all ap
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.