ANSI X9.105-1 : 2009
Superseded
A superseded Standard is one, which is fully replaced by another Standard, which is a new edition of the same Standard.
FINANCIAL TRANSACTION CARD ORIGINATED MESSAGES - INTERCHANGE MESSAGE SPECIFICATIONS - PART 1: MESSAGES, DATA ELEMENTS AND CODE VALUES
04-11-2019
12-01-2013
Foreword
Introduction
1 Scope
2 Normative references
3 Terms and definitions
4 Symbols (and abbreviated terms)
4.1 Representation abbreviations
4.2 Abbreviated terms
5 Message structure
5.1 Message components
5.1.1 Sequence
5.1.2 Message type
5.2 Message repeats
5.3 Message bit maps
5.4 Data elements
5.4.1 Data element types
5.4.2 Primitive data elements
5.4.3 Constructed data element
5.4.4 Composite data elements
6 Data elements
6.1 Data element directory
6.2 General requirements for data elements
6.2.1 Variable length data elements
6.2.2 Binary data
6.2.3 Expression of amounts
6.2.4 Conversion rates
6.2.5 Identification of institutions and routing
6.2.6 Identification of account numbers
6.2.7 Tag length value (TLV) data
6.3 Specific requirements for primitive data elements
6.3.1 Date and time transmission (bit 7)
6.3.2 Action code (bit 39)
6.3.3 Message authentication code (MAC) (bit 64/128)
6.4 Specific requirements for constructed data elements
6.4.1 Processing code (bit 3)
6.4.2 Amount transaction (bit 4)
6.4.3 Amount reconciliation (bit 5)
6.4.4 Amount cardholder billing (bit 6)
6.4.5 Amount cardholder billing fee (bit 8)
6.4.6 Date and time local transaction (bit 12)
6.4.7 Message error indicator (bit 18)
6.4.8 Transaction life cycle identification data (bit 21)
6.4.9 Point of service data code (bit 22)
6.4.10 Point of service capability (bit 27)
6.4.11 Amounts original (bit 30)
6.4.12 Acquirer reference number (bit 31)
6.4.13 Amounts fees (bit 46)
6.4.14 Amounts additional (bit 54)
6.4.15 Original data elements (bit 56)
6.4.16 Amounts original fees (bit 66)
6.4.17 Batch/file transfer message control (bit 68)
6.4.18 Batch/file transfer control data (bit 69)
6.4.19 File transfer description data (bit 70)
6.4.20 Reconciliation data primary (bit 74)
6.4.21 Reconciliation data secondary (bit 75)
6.4.22 Amount net reconciliation (bit 97)
6.4.23 Reconciliation fee amounts (bit 109/110)
6.5 Specific requirements for composite data elements
6.5.1 Electronic commerce data (bit 34)
6.5.2 Card acceptor name/location (bit 43)
6.5.3 Additional response data (bit 44)
6.5.4 Verification data (bit 49)
6.5.5 Integrated circuit card (ICC) related data
(bit 55)
6.5.6 Transaction specific data (bit 104)
7 Messages and transactions
7.1 Message protocol
7.1.1 General
7.1.2 Mandatory and conditional data elements
7.1.3 Message flows
7.1.4 Message errors
7.1.5 Exception message flows
7.1.6 Transaction relationships
8 Message class definitions
8.1 General
8.2 Authorization message class
8.2.1 Authorization description
8.2.2 Authorization message rules
8.2.3 Authorization message type identifiers
8.2.4 Authorization mandatory and conditional data
elements
8.2.5 Authorization message flows
8.3 Verification messages
8.3.1 Verification description
8.3.2 Verification message rules
8.3.3 Verification message type identifiers
8.3.4 Verification mandatory and conditional data elements
8.3.5 Verification message flows
8.4 Financial presentment message class
8.4.1 Financial presentment description
8.4.2 Financial presentment message rules
8.4.3 Financial presentment message type identifiers
8.4.4 Financial presentment mandatory and conditional
data elements
8.4.5 Financial presentment message flows
8.5 Financial accumulation presentment
8.5.1 Financial accumulation presentment description
8.5.2 Financial accumulation presentment message rules
8.5.3 Financial accumulation presentment message type
identifiers
8.5.4 Financial accumulation presentment mandatory and
conditional data elements
8.5.5 Financial accumulation presentment message flows
8.6 File action message class
8.6.1 File action description
8.6.2 File action message rules
8.6.3 File action message type identifiers
8.6.4 File action mandatory and conditional data elements
8.6.5 File action message flows
8.7 Reversal message class
8.7.1 Reversal description
8.7.2 Reversal message rules
8.7.3 Reversal message type identifiers
8.7.4 Reversal mandatory and conditional data elements
8.7.5 Reversal message flows
8.8 Chargeback message class
8.8.1 Chargeback description
8.8.2 Chargeback message rules
8.8.3 Chargeback message type identifiers
8.8.4 Chargeback mandatory and conditional data elements
8.8.5 Chargeback message flows
8.9 Reconciliation message class
8.9.1 Reconciliation description
8.9.2 Reconciliation message rules
8.9.3 Reconciliation message type identifiers
8.9.4 Reconciliation mandatory and conditional data
elements
8.9.5 Reconciliation message flows
8.9.6 Reconciliation calculation
8.9.7 Reconciliation transaction flows
8.10 Administrative message class
8.10.1 Administrative description
8.10.2 Administrative message rules
8.10.3 Administrative message type identifiers
8.10.4 Administrative mandatory and conditional data
elements
8.10.5 Administrative message flows
8.11 Retrieval and retrieval fulfilment
8.11.1 Retrieval and retrieval fulfilment description
8.11.2 Retrieval and retrieval fulfilment message rules
8.11.3 Retrieval and retrieval fulfilment message type
identifiers
8.11.4 Retrieval and retrieval fulfilment mandatory and
conditional data elements
8.11.5 Retrieval and retrieval fulfilment message flows
8.12 Error messages
8.12.1 Error messages description
8.12.2 Error messages message rules
8.12.3 Error messages message type identifiers
8.12.4 Error messages mandatory and conditional data
elements
8.12.5 Error messages message flows
8.13 Fee collection message class
8.13.1 Fee collection description
8.13.2 Fee collection message rules
8.13.3 Fee collection message type identifiers
8.13.4 Fee collection mandatory and conditional data
elements
8.13.5 Fee collection message flows
8.14 Network management message class
8.14.1 Network management description
8.14.2 Network management message rules
8.14.3 Network management message type identifiers
8.14.4 Network management mandatory and conditional
data elements
8.14.5 Network management message flows
8.15 Key management
8.15.1 Key management description
8.15.2 Key management message rules
8.15.3 Key management message type identifiers
8.15.4 Key management mandatory and conditional
data elements
8.15.5 Key management message flows
8.16 Batch transfer
8.16.1 Batch transfer description
8.16.2 Batch transfer message rules
8.16.3 Batch transfer message type identifiers
8.16.4 Batch transfer mandatory and conditional
data elements
8.16.5 Batch transfer message flows
8.17 File transfer
8.17.1 File transfer description
8.17.2 File transfer message rules
8.17.3 File transfer message type identifiers
8.17.4 File transfer mandatory and conditional
data elements
8.17.5 File transfer message flows
9 Message and transaction matching
9.1 General
9.2 Message matching
9.3 Transaction matching
10 Registration and maintenance management group (RMMG)
10.1 General
10.2 Allocation of institution identification codes
10.3 Development of this part of X9.105-1:2003
Identical to ISO 8583-1:2003
11 Guidance on the use of this part of X9.105-1:2003
Identical to ISO 8583-1:2003
11.1 Additional message types
11.2 Additional data elements
11.3 Mandatory and conditional data elements
11.4 Unintentional introduction of control characters
Annex A (normative) Code listings
Annex B (normative) Data elements in bit number order
Annex C (informative) Data transparency
Annex D (informative) Examples of batch transfer
Annex E (informative) Examples of file transfer
Annex F (informative) Summary of changes made to ISO 8583:1993
Bibliography
Describes a common interface by which financial transaction card-originated messages can be interchanged between acquirers and card issuers.
Committee |
X9
|
DocumentType |
Standard
|
PublisherName |
American Bankers Association
|
Status |
Superseded
|
Access your standards online with a subscription
Features
-
Simple online access to standards, technical information and regulations.
-
Critical updates of standards and customisable alerts and notifications.
-
Multi-user online standards collection: secure, flexible and cost effective.