ISO 8583
Financial transaction card originated messages - Interchange message specifications (Second edition 1993-12-15)
1 Scope
2 Normative references
3 Definitions
4 Message structure
4.1 General
4.1.1 Message type identifier structure
4.1.2 Message Repeats
4.1.3 Message Type Identifier Descriptions
4.1.3.1 Authorization message class
Table 1 - Amounts in types of authorization messages
* In request, advice and notificalion messages:
* In response messages:
4.1.3.2 Financial message class
Table 2 - Amounts in types of financial transaction messages
* In request, advice and notification messages:
* In response messages:
4.1.3.3 File action message class
4.1.3.4 Reversal message class
Table 3 - Amounts in reversal messages
Table 4 - Financial transactions
4.1.3.5 Chargeback message class
Table 5 - Amounts in charge back messages
4.1.3.6 Reconciliation message class
4.1.3.7 Administrative message class
4.1.3.8 Fee collection message class
4.1.3.9 Network management message class
4.2 Bit maps
Figure 1 - Bit maps
Table 7A - Bit maps (in numerical order)
Table 7A - Bit maps (by message type)
Table 8 - Conditions used in table 7B
4.3 Data element directory
Table 9 - Data element directory
4.4 Requirements for data elements
4.4.1 Variable length data elements less than 100
4.4.10 Original amounts
4.4.11 Reconciliation
Table 11 - Reconciliation calculation
* Amount Calculations
* Count Calculations
4.4.12 Additional amounts
4.4.13 Use of Cardholder Billing Information
4.4.14 Conversion Rates
4.4.15 Maintenance of codes
4.4.16 Maintenance codes of institution identification
4.4.17 Amounts, fees
4.4.18 Amounts, original fees
4.4.19 Fee amounts in reconciliation
4.4.2 Variable length data elements less than 1000
4.4.3 Binary data elements
4.4.4 Identification of institutions
Table 10 - Usage of institution identification codes
* For request, advice or notification messages:
* For a response message:
4.4.5 Identification of account numbers
4.4.6 Original data elements
4.4.7 Action code
4.4.8 Expression of amounts
4.4.9 Card acceptor name/location
5 Message and transaction flows
5.1 General
5.2 Message flow diagrams
5.2.1 Authorization transactions
5.2.2 Financial transactions
5.2.3 File action transactions
5.2.4 Reversal transactions
5.2.5 Chargeback transactions
5.2.6 Acquirer reconciliation transactions
5.2.7 Card issuer reconciliation transactions
5.2.8 Administrative transactions
5.2.9 Acquirer fee collection transactions
5.2.10 Card issuer fee collection transactions
5.2.11 Network management transactions
5.2.12 Exception Message Flows
5.3 Transaction flow diagrams
5.3.1 Transaction flows for 11xx. 12xx, 14xx transactions
5.3.2 Transaction flows for reconciliation
Figure 2 - Reconciliation example
6 Message and transaction matching
6.1 General
6.2 Message matching
6.3 Transaction matching
7 Maintenance Agency and Registration Authority
7.1 Maintenance of codes
7.1.1 Maintenance Agency responsibilities
7.1.2 Maintenance Agency functions
7.2 ISO 8583 Institution identification codes
7.2.1 Registration Authority
7.2.2 Registration Authority functions
7.2.3 Applications for ISO 8583 institution identification codes
7.3 All other ISO 8583 codes
7.3.1 Maintenance Agency Secretariat
7.3.2 Secretariat functions
7.3.3 Applications for new code values
8 Guidance on the use of this International Standard
8.1 Additional message types
8.2 Additional data elements
8.3 Mandatory and conditional data elements
8.4 Unintentional introduction of control characters
A Code listings
A.1 Action codes
* Code Description
* 000-099 Used in 1110, 1120, 1121, 1140 and 1210, 1220, 1221 and 1240 messages to indicate that the transaction has been approved.
* 100-199 Used in 1110, 1120, 1121, 1140 and 1210, 1220, 1221 and 1240 messages to indicate that the transaction has been processed for authorization by or on behalf of the card issuer and has been denied (not requiring a card pickup)
* 200-299 Used in 1110, 1120, 1121, 1140 and 1210,1220, 1221 and 1240 messages to indicate that the transaction has been processed for authorization by or on behalf of the card issuer and has been denied requiring the card to be picked up.
* 300-399 Used in 1314, 1324, 1325 and 1344 messages to indicate the result of the file action.
* 310-359 reserved for ISO use
* 360-379 reserved for national use
* 380-399 reserved for private use
* 400-499 Used in 1430, 1432, 1440 and 1442 messages to indicate the result of the reversal or chargeback.
* 500-599 Used in 1510, 1512, 1530 and 1532 messages to indicate the result of a reconciliation.
* 600-699 Used in 1614, 1624, 1625, and 1644 messages
* 700-799 Used in 1720, 1721, 1740, 1722, 1723 and 1742 messages.
* 800-899 Used in 1814, 1824, 1825 and 1844 messages.
* 902-949 Used in request response and advice response messages to indicate transaction could not be processed.
* 950-999 Used in advice response messages (1x3x) to indicate the reason for rejection of the transfer of financial liability.
A.2 Amount type codes
* Code Description
* 00-19 Account related balances
* 20-39 Card related amounts
* 40-59 Transaction related amounts
A.3 Authorization life cycle codes
* Position 1 - time code
* Code Description
* Position 2-3 -time interval
* Code Description
A.4 Card acceptor business codes
A.4.1 Card acceptor business codes (numerically)
* Agricultural service
* Contracted services
* Transportation
* Utilities
* Retail Stores
* Service providers
*Personal service providers
* Business services
* Repair services
* Amusement and entertainment
* Professional services and membership organization
* Government services
A.4.2 Card acceptor business codes (alphabetically)
A.5 Fee type codes
A.6 Function codes
A.7 Message reason codes
A.8 Point of service data code
* Position 1 - Card data input capability
* Position 2 - Cardholder authentication capability
* Position 3 - Card capture capability
* Position 4 - Operating environment (see note 2)
* Position 5 - Cardholder present
* Position 6 - Card present
* Position 7 - Card data input mode
* Position 8 - Cardholder authentication method
* Position 9 - Cardholder authentication entity
* Position 10 - Card data output capability
* Position 11 - Terminal output capability
* Position 12 - PIN capture capability
A.9 Processing codes
* 00-19 Debits
* 20-29 Credits
* 30-39 Inquiry services
* 40-49 Transfer services
* 50-59 Payment services
* 60-99 Reserved
B Conversion guide
B.1 Introduction
B.2 Purpose
B.3 Differences between 1987 and 1993 editions of ISO 8583
B.3.1 General
B.3.2 Definitions
B.3.2.1 Additions
B.3.2.2 Changes
B.3.2.3 Deletions;The following definitions have been deleted:
- interactive message;
- intermediate network facility;
- non-interactive message;
- processing code;
- reversal credit;
- reversal debit;
- reversal transfer;
- routing;
- transaction fee.
B.3.3 Message structure
B.3.4 Message types
Table B.1 - Comparison of message classes
B.3.5.1 Additions
B.3.5.2 Changes
B.3.5.3 Deletions
B.3.5.4 Action, function and message reason code mapping
B.3.5.5 Point of service data code mapping
B.3.6 Usage of data elements
B.3.7 Message Flow
B.3.7.1 Authorization messages
B.3.7.2 Financial messages
B.3.7.3 File action messages
B.3.7.4 Reversal messages
B.3.7.5 Chargeback messages
B.3.7.6 Reconciliation messages
B.3.7.7 Administrative messages
B.3.7.8 Fee collection messages
B.3.7.9 Network management messages
B.3.7.10 Exception message flows
B.4 Further advice
B.4.1 Usage of amount data elements
B.4.1.1 General
B.4.1.2 Authorizations
B.4.1.3 Financial transactions
B.4.1.4 Reversals
B.4.1.5 Chargebacks
B.4.2 Reconciliation processing
B.4.2.1 General
B.4.2.2 Accumulation
B.4.3 Fee collection
B.4.4 Usage of fee amount data elements
Appendix C - Forms for application for institution identifiers and codes
Foreword
Introduction
Table 6 Message type identifiers
Table B.2 File update code (1987) mapped to function code (1993)
Table B.3 Network management information code (1987) mapped to function code (1993)
Table B.4 Response code (1987) mapped to message reason code and action code (1993)
Table B.5 Settlement code (1987) mapped to action code (1993)
Table B.6 Point of service PIN capture code (1987) mapped to point of service data (1993)
Table B.7 Point of service condition code (1987) mapped to point of service data (1993)
Table B.8 Point of service entry mode (1987) mapped to point of service data (1993)
|