• There are no items in your cart

AS 2805.12.1-1999

Superseded

Superseded

A superseded Standard is one, which is fully replaced by another Standard, which is a new edition of the same Standard.

View Superseded by

Electronic funds transfer - Requirements for interfaces Message content - Structure and format

Available format(s)

Hardcopy , PDF 1 User , PDF 3 Users , PDF 5 Users , PDF 9 Users

Superseded date

21-05-2024

Superseded by

AS 2805.12.1-2004

Language(s)

English

Published date

01-01-1999

€92.72
Excluding VAT

1 - AS 2805.12.1-1999 ELECTRONIC FUNDS TRANSFER-REQUIREMENTS FOR INTERFACES - MESSAGE CONTENT-STRUCTURE AND FORMAT
4 - PREFACE
5 - CONTENTS
6 - FOREWORD
7 - 1 SCOPE
7 - 2 REFERENCED DOCUMENTS
7 - 3 DEFINITIONS
7 - 3.1 Acquirer
8 - 3.2 Advice
8 - 3.3 Authorization
8 - 3.4 Authorizing agent
8 - 3.5 Bitmap
8 - 3.6 Card acceptor
8 - 3.7 Cardholder
8 - 3.8 (Card) issuer
8 - 3.9 Chargeback
8 - 3.10 Credit transaction
8 - 3.11 Debit transaction
8 - 3.12 Financial transaction
8 - 3.13 File action
8 - 3.14 Forwarding institution
8 - 3.15 Inquiry
8 - 3.16 Institution identification code
8 - 3.17 Maintenance agency
8 - 3.18 Message
8 - 3.19 Message class
8 - 3.20 Message function
8 - 3.21 Notification
8 - 3.22 Payment
9 - 3.23 Point of service
9 - 3.24 Receiving institution
9 - 3.25 Reconciliation
9 - 3.26 Registration authority
9 - 3.27 Replacement authorization
9 - 3.28 Representment
9 - 3.29 Request
9 - 3.30 Resubmission
9 - 3.31 Reversal
9 - 3.32 Settlement
9 - 3.33 Settlement institution
9 - 3.34 Supplementary authorization
9 - 3.35 Transaction
9 - 3.36 Transaction destination institution
9 - 3.37 Transaction originator institution
9 - 3.38 Transfer
9 - 3.39 Version
10 - 4 MESSAGE STRUCTURE
10 - 4.1 General
10 - 4.2 Message type identifier
10 - 4.3 Message type identifier structure
10 - 4.4 Message repeats
11 - 4.5 Message type identifier descriptions
11 - 4.6 Authorization message class
12 - 4.7 Financial message class
13 - 4.8 File action message class
13 - 4.9 Reversal message class
14 - 4.10 Chargeback message class
15 - 4.11 Reconciliation message class
16 - 4.12 Administrative message class
17 - 4.13 Fee collection message class
17 - 4.14 Network management message class
21 - 4.15 Bitmaps
35 - 4.16 Data element directory
45 - 4.17 Requirements for data elements
45 - 4.17.1 Variable length data elements less than 100
46 - 4.17.2 Variable length data elements less than 1000
46 - 4.17.3 Binary data elements
46 - 4.17.4 Identification of institutions
47 - 4.17.5 Identification of account numbers
47 - 4.17.6 Original data elements
48 - 4.17.7 Action code
48 - 4.17.8 Expression of amounts
48 - 4.17.9 Card acceptor name/location
48 - 4.17.10 Amounts, original
48 - 4.17.11 Reconciliation
51 - 4.17.12 Additional amounts
51 - 4.17.13 Use of cardholder billing information
51 - 4.17.14 Conversion rates
51 - 4.17.15 Maintenance of codes
51 - 4.17.16 Maintenance of institution identification codes
51 - 4.17.17 Amounts, fees
52 - 4.17.18 Amounts, original fees
52 - 4.17.19 Fee amounts in reconciliation
52 - 5 MESSAGE AND TRANSACTION FLOWS
52 - 5.1 General
52 - 5.2 Message flow diagrams
53 - 5.3 Authorization transactions
53 - 5.4 Financial transactions
54 - 5.5 File action transactions
54 - 5.6 Reversal transactions
54 - 5.7 Chargeback transactions
55 - 5.8 Acquirer reconciliation transactions
55 - 5.9 Card issuer reconciliation transactions
56 - 5.10 Administrative transactions
56 - 5.11 Acquirer fee collection transactions
56 - 5.12 Card issuer fee collection transactions
57 - 5.13 Network management transactions
57 - 5.14 Exception message flows
58 - 5.15 Transaction flow diagrams
58 - 5.16 Transaction flows for 11xx, 12xx, 14xx transactions
58 - 5.17 Transaction flows for reconciliation
59 - 6 MESSAGE AND TRANSACTION MATCHING
59 - 6.1 General
59 - 6.2 Message matching
59 - 6.3 Transaction matching
60 - 7 GUIDANCE ON THE USE OF THIS STANDARD
60 - 7.1 Additional message types
60 - 7.2 Additional data elements
60 - 7.3 Mandatory and conditional data elements

Specifies a common interface by which financial transaction card-oriented messages may be interchanged. Specifies message structure, format and content, data elements and values for data elements. The method by which settlement takes place is not within the scope of this Standard.

Committee
IT-005
DocumentType
Standard
ISBN
0 7337 2563 5
Pages
54
PublisherName
Standards Australia
Status
Superseded
SupersededBy
Supersedes
UnderRevision

This Standard specifies a common interface by which financial transaction card-originated messages may be interchanged. It specifies message structure, format and content, data elements and values for data elements. The method by which settlement takes place is not within the scope of this Standard.

First published as AS 2805.12.1-1999.

AS 3521-1988 Identification cards - Physical characteristics
AS 3525-1988 Bank cards - Magnetic stripe data content for Track 3
AS 3524-1988 Identification cards - Financial transaction cards
AS 3523.2-1998 Identification cards - Identification of issuers - Application and registration procedures
AS 3523.1-1998 Identification cards - Identification of issuers Numbering system

AS 2805.4.2-2001 Electronic funds transfer - Requirements for interfaces Message authentication - Mechanisms using a hash-function
AS 2805.12.2-1999 Electronic funds transfer - Requirements for interfaces Message content - Codes
AS 2805.6.2-2002 Electronic funds transfer - Requirements for interfaces Key management - Transaction keys (Reconfirmed 2013)
AS 2805.9-2000 Electronic funds transfer - Requirements for interfaces Privacy of communications (Reconfirmed 2013)
AS 2805.12.3-1999 Electronic funds transfer - Requirements for interfaces Message content - Maintenance of codes
AS 2805.6.5.1-2000 Electronic funds transfer - Requirements for interfaces Key management - TCU initialization - Principles
AS 2805.6.4-2001 Electronic funds transfer - Requirements for interfaces Key management - Session keys - Terminal to acquirer
AS 2805.4.1-2001 Electronic funds transfer - Requirements for interfaces Message authentication - Mechanisms using a block cipher (Reconfirmed 2016)

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.