SAA HB 1291999

This is a free 12 page sample. Access the full version at http://infostore.saiglobal.com.

Handbook
Electronic funds transfer Implementing message content StandardsInterchange Handbook

This is a free 12 page sample. Access the full version at http://infostore.saiglobal.com.

Electronic funds transfer Implementing Message content Standards

Interchange Handbook

First published as SAA HB1291999.

PUBLISHED BY STANDARDS AUSTRALIA PO Box 1055 Strathfield NSW 2135

ISBN 0 7337 2562 7

SAA HB1291999

ii

PREFACE
This Handbook was prepared by the Standards Australia Committee IT/5, Electronic Funds Transfer, to address the implementation requirements for the AS 2805.12 series of Standards on electronic funds transfer (EFT)requirements for interfaces. The Standards in the AS 2805 series are as follows: AS 2805 2805.1 2805.2 2805.3 2805.4 2805.5.1 2805.5.2 2805.5.3 2805.6.1 2805.6.2 2805.6.3 2805.6.4 2805.6.5.1 2805.6.5.3 2805.9 2805.10 2805.12.1 2805.12.2 2805.12.3

This is a free 12 page sample. Access the full version at http://infostore.saiglobal.com.

Electronic funds transferRequirements for interfaces Part 1: Communications Part 2: Message structure, format and content Part 3: PIN management and security Part 4: Message authentication Part 5.1: CiphersData encipherment algorithm 1 (DEA 1) Part 5.2: CiphersModes of operation for a n-bit block cipher algorithm Part 5.3: CiphersData encipherment algorithm 2 (DEA 2) Part 6.1: Key managementPrinciples Part 6.2: Key managementTransaction keys Part 6.3: Key management Session keysNode to node Part 6.4: Key management Session keysTerminal to acquirer Part 6.5.1: Key management TCU initializationPrinciples Part 6.5.3: Key management TCU initializationAsymmetric Part 9: Privacy of communications Part 10: File transfer integrity validation Part 12.1: Message content Structure and format Part 12.2: Message content Codes Part 12.3: Message content Maintenance of codes

The following handbooks relate to AS 2805 series of Standards: SAA HB127 SAA HB128 SAA HB129 Electronic funds transferImplementing message content StandardsConversion Handbook (changing from AS 2805.2 to the AS 2805.12 series) Electronic funds transferImplementing message content StandardsTerminal Handbook Electronic funds transferImplementing message content StandardsInterchange Handbook (this Handbook)

Copyright STANDARDS AUSTRALIA Users of Standards are reminded that copyright subsists in all Standards Au stralia publications and software. Except where the Copyright Act allows and except where provided for below no publications or software produced by Standards Australia may be reproduced, stored in a retrieval system in any form or transmitted by any means without prior permission in writing from Standards Australia. Permission may be conditional on an appropriate royalty payment. Requests for permission and information on commercial software royalties should be directed to the head office of Standards Australia. Standards Australia will permit up to 10 percent of the technical content pages of a Standard to be copied for use exclusively in-house by purchasers of the Standard without payment of a royalty or advice to Standards Australia. Standards Australia will also permit the inclusion of its copyright material in computer software programs for no royalty payment provided such programs are used exclusively in-house by the creators of the programs. Care should be taken to ensure that material used is from the current edition of the Standard and that it is updated whenever the Standard is amended or revised. The number and date of the Standard should therefore be clearly identified. The use of material in print form or in computer software programs to be used commercially, with or without payment, or in commercial contracts is subject to the payment of a royalty. This policy may be varied by Standards Australia at any time.

iii

SAA HB1291999

CONTENTS 1 2
2.1 2.1.1 2.1.2 2.1.3 2.1.4 2.2 2.2.1 2.2.2
This is a free 12 page sample. Access the full version at http://infostore.saiglobal.com.

SCOPE DATA REPRESENTATION

STRUCTURE OF AN AS 2805.12 MESSAGE Transport header Message type Bitmap Data fields DATA TYPES Binary data Numeric data Signed numeric data Character data FIELD REPRESENTATION 2.3.1 2.3.2 2.4 Variable length field representation Justification and filling DATE FIELDS

1 1
1 1 1 1 2 2 2 2 2 3 3 3 4 4

2.2.3 2.2.4 2.3

3
3.1 3.2

Field usage
TERMINAL IDENTIFICATION MATCHING OF MESSAGES AND TRANSACTIONS 3.2.1 3.2.2 3.3 3.3.1 3.3.2 3.3.3 3.3.4 3.3.5 3.3.6 3.3.7 3.3.8 3.3.9 3.3.10 3.3.11 3.3.12 3.3.13 3.3.14 3.3.15 3.3.16 3.3.17 3.3.18 Message matching Transaction matching FIELD REQUIREMENTS Extended bitmap (Field 1) Pan (Field 2) Processing code (Field 3) Amount, transaction (Field 4) Amount, reconciliation (Field 5) Amount, cardholder billing (Field 6) Date and time, transmission (Field 7) Amount, cardholder billing fee (Field 8) Conversion rate, reconciliation (Field 9) Conversion rate, cardholder billing (Field 10) Systems trace audit number (Field 11) Date and time, local transaction (Field 12) Date, effective (Field 13) Date, expiration (Field 14) Date, settlement (Field 15) Date, conversion (Field 16) Date, capture (Field 17) Merchant type (Field 18)

4
4 4 5 5 5 5 5 6 6 6 6 6 7 7 7 7 7 8 8 8 8 8 8

SAA HB1291999

iv 8 8 8 9 9 9 9 9 10 10 10 10 10 11 11 11 11 11 11 11 11 12 12 12 12 13 13 13 13 14 14 15 15 15 15 15 15 15 16

3.3.19 3.3.20 3.3.21 3.3.22 3.3.23 3.3.24 3.3.25 3.3.26 3.3.27 3.3.28
This is a free 12 page sample. Access the full version at http://infostore.saiglobal.com.

Country code, acquiring institution (Field 19) Country code, primary account number (Field 20) Country code, forwarding institution (Field 21) Point of service data code (Field 22) Card sequence number (Field 23) Function code (Field 24) Message reason code (Field 25) Card acceptor business code (Field 26) Approval code length (Field 27) Date, reconciliation (Field 28) Reconciliation indicator (Field 29) Amounts, original (Field 30) Acquirer reference data (Field 31) Acquiring institution identification code (Field 32) Forwarding institution identification code (Field 33) Primary account number, extended (Field 34) Track 2 data (Field 35) Track 3 data (Field 36) Retrieval reference number (Field 37) Approval code (Field 38) Action code (Field 39) Service code (Field 40) Card acceptor terminal identification (Field 41) Card acceptor identification code (Field 42) Card acceptor name/location (Field 43) Additional response data (Field 44) Track 1 data (Field 45) Amounts, fees (Field 46) Additional data, national (Field 47) Additional data, private (Field 48) Currency code, transaction (Field 49) Currency code, reconciliation (Field 50) Currency code, cardholder billing (Field 51) Personal identification number (PIN) data (Field 52) Security related control information (Field 53) Amounts, additional (Field 54) Integrated circuit card system related data (Field 55) Original data elements (Field 56) Authorization life cycle code (Field 57)

3.3.29 3.3.30 3.3.31 3.3.32 3.3.33 3.3.34 3.3.35 3.3.36 3.3.37 3.3.38 3.3.39 3.3.40 3.3.41 3.3.42 3.3.43 3.3.44 3.3.45 3.3.46 3.3.47 3.3.48 3.3.49 3.3.50 3.3.51 3.3.52 3.3.53 3.3.54 3.3.55 3.3.56 3.3.57

v 3.3.58 3.3.59 3.3.60 3.3.61 3.3.62 3.3.63 3.3.64 3.3.65 3.3.66 3.3.67 3.3.68
This is a free 12 page sample. Access the full version at http://infostore.saiglobal.com.

SAA HB1291999

Authorizing agent institution identification code (Field 58) Transport data (Field 59) Reserved for national use (Field 60) Reserved for national use (Field 61) Reserved for private use (Field 62) Reserved for private use (Field 63) Message authentication code (Field 64) Reserved for ISO use (Field 65) Amounts, original fees (Field 66) Extended payment data (Field 67) Country code, receiving institution (Field 68) Country code, settlement institution (Field 69) Country code, authorizing agent institution (Field 70) Message number (Field 71) Data record (Field 72) Date, action (Field 73) Credits, number (Field 74) Credits, reversal number (Field 75) Debits, number (Field 76) Debits, reversal number (Field 77) Transfer, number (Field 78) Transfer, reversal number (Field 79) Inquiries, number (Field 80) Authorizations, number (Field 81) Inquiries, reversal number (Field 82) Payments, number (Field 83) Payments, reversal number (Field 84) Fee collections, number (Field 85) Credits, amount (Field 86) Credits, reversal amount (Field 87) Debits, amount (Field 88) Debits, reversal amount (Field 89) Authorizations, reversal number (Field 90) Country code, transaction destination institution (Field 91) Country code, transaction originator institution (Field 92) Transaction destination institution identification code (Field 93) Transaction originator institution identification code (Field 94) Card issuer reference data (Field 95)

16 16 16 16 16 17 17 17 17 17 17 18 18 18 18 18 18 18 18 18 18 18 18 18 19 19 19 19 19 19 19 19 19 19 19 19 20 20

3.3.69 3.3.70 3.3.71 3.3.72 3.3.73 3.3.74 3.3.75 3.3.76 3.3.77 3.3.78 3.3.79 3.3.80 3.3.81 3.3.82 3.3.83 3.3.84 3.3.85 3.3.86 3.3.87 3.3.88 3.3.89 3.3.90 3.3.91 3.3.92 3.3.93 3.3.94 3.3.95

SAA HB1291999

vi 20 20 20 20 20 20 20 20 20 20 21 21 21 21 21 21 22 22 22

3.3.96 3.3.97 3.3.98 3.3.99

Key management data (Field 96) Amount, net reconciliation (Field 97) Payee (Field 98) Settlement institution identification code (Field 99)

3.3.100 Receiving institution identification code (Field 100) 3.3.101 File name (Field 101) 3.3.102 Account identification 1 (Field 102) 3.3.103 Account identification 2 (Field 103) 3.3.104 Transaction description (Field 104) 3.3.105 Credits, chargeback amount (Field 105) 3.3.106 Debits, chargeback amount (Field 106)
This is a free 12 page sample. Access the full version at http://infostore.saiglobal.com.

3.3.107 Credits, chargeback number (Field 107) 3.3.108 Debits, chargeback number (Field 108) 3.3.109 Credits, fee amounts (Field 109) 3.3.110 Debits, fee amounts (Field 110) 3.3.111 Reserved for ISO use (Fields 111-115) 3.3.112 Reserved for national use (Fields 116-122) 3.3.113 Reserved for private use (Fields 123-127) 3.3.114 Message authentication code (Field 128)

4
4.1

MESSAGE PROCESSING
MAGNETIC STRIPE INITIATED MESSAGES 4.1.1 4.2 4.3 4.4 4.5 4.6 Tracks 1, 2 and 3 ICC INITIATED MESSAGES MANUALLY ENTERED MESSAGES ELECTRONIC FALLBACKS KEY MANAGEMENT ISSUES REJECTED MESSAGES

22
22 22 23 23 23 24 24

5
5.1

AUTHORIZATIONS
PRE-AUTHORIZATIONS 5.1.1 5.1.2 5.1.3 5.2 5.2.1 5.2.2 Fuel dispensers Card phones Hotel pre-authorizations FUNDS INQUIRIES Critical fields Reconciliation

26
26 27 27 28 28 29 29

6
6.1

FINANCIAL TRANSACTIONS
PURCHASES 6.1.1 6.1.2 6.2 Critical fields Reconciliation CASH-OUTS

29
30 31 31 31

vii 6.2.1 6.2.2 6.3 6.3.1 6.3.2 6.4 6.4.1 6.4.2 6.5 6.5.1 6.5.2 6.6
This is a free 12 page sample. Access the full version at http://infostore.saiglobal.com.

SAA HB1291999

Critical fields Reconciliation COMBINED PURCHASE AND CASH OUT Critical fields Reconciliation CARD ACCEPTOR BILL PAYMENTS Critical fields Reconciliation CHEQUE DISHONOURS Critical fields Reconciliation REFUNDS

32 32 33 33 33 34 34 34 35 35 35 36 36 36 36 37 37 38 38 38 38 39 39 39 40 40 40 40 41

6.6.1 6.6.2 6.7 6.7.1 6.7.2 6.8 6.8.1 6.8.2 6.9 6.9.1 6.9.2 6.10 6.11 6.11.1 6.11.2 6.12 6.13

Critical fields Reconciliation DEPOSITS (CASH AND/OR CHEQUES) Critical fields Reconciliation FUNDS TRANSFERS Critical fields Reconciliation ADJUSTMENTS Critical fields Reconciliation TIPS CARD ISSUER BILL PAYMENTS Critical fields Reconciliation REFERRED TRANSACTIONS CARDHOLDER COMPLETION TRANSACTIONS

7
7.1 7.2

FILE ACTIONS
NORMAL PROCESSING BATCH TRANSFERS 7.2.1 7.2.2 7.2.3 7.2.4 Batch open Data delivery Re-synchronization Batch close

41
41 41 42 42 42 42

8
8.1

REVERSALS AND CHARGEBACKS

REVERSALS 8.1.1 8.1.2 8.2 8.2.1 Where reversals are used Restrictions CHARGEBACKS Acquirer adjustment requests

42
42 42 43 44 44

SAA HB1291999

viii 44 45 45 46 46 48 48

8.2.2 8.2.3 8.2.4 8.2.5 8.2.6 8.2.7 8.2.8

Merchant adjustment requests Acquirer chargeback Retrievals Prerequisites Chargeback categories Acquirer to merchant Chargeback categories Merchant to acquirer Chargeback reversal requests

9
9.1 9.2

RECONCILIATION
THE RECONCILIATION PROCESS UPDATING RECONCILIATION TOTALS 9.2.1 9.2.2 Authorizations and financial requests Advice messages Repeat messages Reversal messages DIFFERENCES BETWEEN NODES FEE CALCULATIONS TYPES OF RECONCILIATION MESSAGES 9.5.1 9.5.2 9.6 9.6.1 9.6.2 9.6.3 Checkpoint reconciliation Final reconciliation END OF DAY PROCESS Impact on checkpoint reconciliation Independent cut-over process Synchronized cut-over process

49
50 50 50 51 51 51 51 52 52 52 53 53 53 53 56

This is a free 12 page sample. Access the full version at http://infostore.saiglobal.com.

9.2.3 9.2.4 9.3 9.4 9.5

10 NETWORK MANAGEMENT
10.1 10.2 10.2.1 10.2.2 10.3 10.3.1 10.3.2 10.3.3 10.4 10.4.1 10.4.2 10.5 10.6 10.7 10.7.1 10.7.2 10.7.3 10.7.4 ENCIPHERMENT TERMS USED INTERCHANGE KEY EXCHANGE DEA 2 key generation DEA 2 key loading KEY ENCIPHERMENT KEY EXCHANGE KEK exchange advice KEK exchange advice response KEK exchange advice response processing ESTABLISHING A SESSION Session key change Establishing a link ECHO TEST SIGN-ON SIGN-OFF Data requirements Message flows Issuer sign-off Message flows

56
57 58 58 58 58 59 59 59 60 60 61 62 62 62 63 63 63 63

ix 10.8 10.8.1 10.8.2 SETTLEMENT DATE CUT-OVER Data requirements Message flows

SAA HB1291999

64 64 65

11 FEE COLLECTION 12 USAGE OF FEE AMOUNT DATA ELEMENTS

65 69

This is a free 12 page sample. Access the full version at http://infostore.saiglobal.com.

SAA HB1291999

FOREWORD
Australia has embraced the ISO 8583 Standard since its development in the early 1980s and it has been included in the Australian AS 2805 series of Standards which covers communications, data content and security requirements of the EFT network. The first Australian version of AS 2805.2 was released in 1985, two years before ISO 8583:1987 was published. The AS 2805 series is now in use on virtually all ATM and EFTPOS interchanges in Australia, and it is also used in New Zealand and as the basis for several Asian systems. The Standards are also used on several interchanges for domestic switching of credit and charge cards. Although ISO 8583:1987 relates to interfacing between interchanges, Australia quickly adapted the Standard for use in terminals, with the introduction of AS 2805.71986 describing POS message content. Since that time, all new EFTPOS terminals have supported the ISO style message format. By using the ISO Standard for both interchanges and terminals, the level of understanding of the requirements of the Standard has been greatly expanded. Unfortunately, both AS 2805 and ISO 8583 allow distinct interpretations, which caused many issues for connectivity. To help address these issues, ISO reviewed the 8583 Standard and carried out a major revamp of the Standard. In the light of these changes, Standards Australia initiated updates to the current version of AS 2805 in the form of a maintenance update to clarify the Standard. This was released as AS 2805.21996 and replaced the previous Part 2, as well as Parts 2805.7 and 2805.8. Also, ISO 8583:1993 has been adopted as AS 2805.12.11999. This Handbook is a guide for those who are implementing the AS 2805.12 series, or who work closely with it. Although this Handbook is not part of the Standard, it has been developed to show users of the Standard how the messages required to support the Australian EFT environment should be implemented. By adopting the processing described here, the interface will be consistent with other users of the Standard. Any questions about the AS 2805 series or this Handbook should be made in writing to: Standards Australia IT/5/3 Project Manager PO Box 1055 Strathfield NSW 2135

This is a free 12 page sample. Access the full version at http://infostore.saiglobal.com.

SAA HB1291999

STANDARDS AUSTRALIA Electronic funds transferImplementing message content StandardsInterchange Handbook

SCOPE

This Handbook is an implementation guide which addresses the following: (a)

This is a free 12 page sample. Access the full version at http://infostore.saiglobal.com.

Node-to-node message specifications This Handbook provides a guide for the implementation of a common interface by which financial cards originated messages may be passed between acquirer, intermediate and issuer systems. It specifies data representation, condition codes, typical message content and field usage. Message application This Handbook documents the recommended application of messages between nodes. They include pre-authorization, financial, reversal, charge-back, fee collection, network management, administrative, file action and settlement messages.

(b)

DATA REPRESENTATION

Data representation used in individual systems is subject to the commercial relationships between the parties contracting to each system. The message formats given in this Handbook are designed to ensure that compatibility between systems conforming to this Handbook is always feasible. The data fields within AS 2805 may be represented using a variety of data formats which are determined by the type of information that the field may contain. Each data field has a single definition for the format of that field.

2.1
2.1.1

STRUCTURE OF AN AS 2805.12 MESSAGE

Transport header

Transport headers are inserted at the front of an AS 2805 message to allow intermediate switches and communications systems to store routing information. Generally, transport headers are not supported on interchanges, but are supported for certain terminal systems. Transport headers must be agreed upon on a bilateral basis.

2.1.2

Message type

The message type describes the basic functionality of a message and the type of impact that the message will have on the destination system. For example, some of the message types describe whether a message is for interface control, financial transactions or file updates.

2.1.3

Bitmap

The bitmap field contains flags or indicators which are used to describe which data fields are present in the message. By having a table of indicators at the front of the message, the message originator may send only those fields which are relevant to the current message and leave out fields which are irrelevant or do not contain valid data. Note that there is a minimum data content required for each message type. The Standard defines those fields which are believed to be the required minimum fields. However, applications between interchange partners may have special requirements and although it is recommended that all users adhere to the defined message contents, the final decision on the content will be made on a bilateral basis.

COPYRIGHT

This is a free preview. Purchase the entire publication at the link below:

This is a free 12 page sample. Access the full version at http://infostore.saiglobal.com.

HB 129-1999, Electronic funds transfer Implementing message content Standards Interchange Handbook

Looking for additional Standards? Visit SAI Global Infostore Subscribe to our Free Newsletters about Australian Standards in Legislation; ISO, IEC, BSI and more Do you need to Manage Standards Collections Online? Learn about LexConnect, All Jurisdictions, Standards referenced in Australian legislation Do you want to know when a Standard has changed? Want to become an SAI Global Standards Sales Affiliate? Learn about other SAI Global Services: LOGICOM Military Parts and Supplier Database Metals Infobase Database of Metal Grades, Standards and Manufacturers Materials Infobase Database of Materials, Standards and Suppliers Database of European Law, CELEX and Court Decisions

Need to speak with a Customer Service Representative - Contact Us