FLEXCUBE ATM INTERFACE

ISO 8583 (1993) MESSAGE FORMAT

COPYRIGHT (C) 2004 Oracle Financial Services Software Ltd.

All rights reserved. No part of this work may be reproduced, stored in a retrieval system, adopted
or transmitted in any form or by any means, electronic, mechanical, photographic, graphic, optic
recording or otherwise, translated in any language or computer language, without the prior written
permission of ofss.

Due care has been taken to make this as accurate as possible. However, ofss solutions limited
makes no representation or warranties with respect to the contents hereof and shall not be
responsible for any loss or damage caused to the user by the direct or indirect use of this and the
accompanying software package. Furthermore, ofss reserves the right to alter, modify or
otherwise change in any manner the content hereof, without obligation of ofss to notify any
person of such revision or changes.

All company and product names are trademarks of the respective companies with which they are
associated.
Document Control

FileName: ATM_Interface_ISO8583_1993.doc Creation Date: 26 March 2018

Author: Harish Nittam Last Saved By: Harish Nittam
Group: BPD Last Saved On: 26 March 2018
Revision No: 4

TABLE OF CONTENTS

1.1 Introduction 4
1.1.1 Document Scope 4
1.1.2 Acronyms and Abbreviations 4
1.1.3 Overview of the Proposed System 5
1.2.1 Types of transaction 5
1.2.2 Classification of Transaction 5
1.3 Flexcube Interface Specification 7
1.3.1 Overview 7
1.3.2 Protocol 7
1.3.3 Message types supported 8
1.3.4 Bitmap 8
2. Message Formats 8
2.1 Network Messages 8
2.2 ATM Transaction Messages 9
3. ISO Field Descriptions 16

1.1 Introduction

1.1.1 Document Scope

This document covers the interface specifications that must be supported by any switch to
integrate with Flexcube. The document aims at covering the exception behavior and frequently
asked questions about the ATM / POS interface that Flexcube provides.

1.1.2 Acronyms and Abbreviations

ATM Automated Teller Machine.

POS Point of Sale Machine
GL General Ledger.
Acquirer The institution, which accepts the card for performing the transaction.
Issuer The institution which has issued the card and to which the account
belongs.
Forwarder The institution, which is responsible for forwarding the transaction from the
acquirer to the issuer (Example: Master Card, Visa).
CASA Current account, Savings account
CMS Card Management System (Credit Card)
BANK_INST_ID A unique ID maintained in Flexcube for the Bank
1.2 Overview of the Proposed System

1.2.1 Types of transaction

With reference to Flexcube (Debit cards), there are three types of transaction, which will exist in
the ATM/POS network for any bank

1. Onus Transactions: When the debit cardholder of the bank transacts from an ATM or
POS terminal belonging to the bank, the transaction is an onus transaction.

2. Remote Onus Transactions: When the Debit cardholder of the bank transacts from an
ATM/POS not belonging to the bank then the transaction is remote onus transaction
(Switched transaction). This transaction is settled with an external entity called the
Forwarder (VISA, Master Card etc.).

3. Off-us Transaction: When a cardholder other than Debit cardholders of the bank
transact from an ATM or POS belonging to the bank then this transaction is an off-us
transaction. This transaction is settled with an external entity called the Forwarder.

1.2.2 Classification of Transaction

Every financial transaction, which enters the Flexcube system, will have to be classified as one of
the above transaction types. This is required because the transaction posting and accounting
entries are done automatically by the Flexcube system depending upon the transaction type and
the associated details of the transaction. Flexcube uses the following two fields to classify the
transaction
1. Acquiring Institution ID (Field #32)
2. Forwarding Institution ID (Field #33)

The Institution ID of BANK (BANK_INST_ID) is maintained in the Flexcube System.

Flexcube classifies the transaction in the following manner

1. Onus Transactions: If the Acquiring Institution ID of the transaction is BANK_INST_ID

and the Forwarding institution ID is empty (or defaulted to zeroes) then the transaction is
an Onus transaction. The transaction will be settled against the terminal associated with
the Onus transaction.

2. Remote Onus Transactions: If the Acquiring Institution ID of the transaction is not

BANK_INST_ID, then the transaction is a Remote Onus transaction, routed through the
forwarder represented by the Forwarding Institution ID. This transaction will be settled
with the forwarder represented by the Forwarding Institution ID.

3. Offus Transactions: If the Acquiring Institution ID of the transaction is BANK_INST_ID

and the Forwarding institution ID is not empty (or not defaulted to zeroes) then the
transaction is an Offus transaction. The transaction will be settled against the terminal
associated with the Offus transaction.
1.3 Flexcube Interface Specification

1.3.1 Overview
The Flexcube ATM / POS (Debit) servers support the ISO 8583 (1987) interfaces. In the
Flexcube interface, the primary account number (PAN) refers to the Flexcube account number
on which the transaction is being executed and not the card number. Flexcube hosts a
different server for ATM transactions and a different server for POS transactions. This is
because the functionality of the ATM transactions differs from the functionality of the POS
transactions. Because of the above, it is required that the switch should route the ATM and
the POS transactions to different ports. The Flexcube ATM and POS interface is configured as
a server and hence there will be no request originating from the ATM / POS interface of
Flexcube (like SIGN ON / LOG OFF). The interface will only respond to the requests sent by
the switch.

1.3.2 Protocol
The interface to Flexcube will be over TCP/IP. The application data will be prefixed by either
one of the following
1. 2-byte length header field (Binary) indicating the length of the application data to
follow.
2. 4-byte length header field (ASCII) indicating the length of the application data to
follow.

1.3.3 Message types supported

The Following request message types will be supported in the Debit Interface
Message Type Request Response
Financial transaction request 0200 0210
Financial transaction Advice 0220 0230
Financial transaction Advice repeat 0221 0230
Reversal Advice request 0420 0430
Reversal Advice request repeat 0421 0430
Network management request (Echo, 0800 0810
Logon/Logoff initiated by the switch)
1.3.4 Bitmap
Flexcube supports the following ISO bitmap representations
1. Binary: This is either an 8 byte or 16 byte bitmap representation
2. ASCII: This is either and 16 or 32 byte representation of the bitmap in Hex.

2. Message Formats
2.1 Network Messages

2.1.1 Echo Test/SignOn/SignOff Request Message Format

Bit Name Format Attr Values Remarks
Message Type n4 1800 / 1801 / 1820 /
1821
1 BIT MAP b1
7 Transmission Date & Time MMDDhhmmss n 10
11 System Trace Audit Number n6
70 Network Management n3 301 / 001 / 002
Information Code

2.1.2 Echo Test/SignOn/SignOff Response Message Format

Bit Name Format Attr Values Remarks
Message Type n4 0810 / 0830
1 BIT MAP b1
7 Transmission Date & Time MMDDhhmmss n 10 Same as request msg
11 System Trace Audit Number n6 Same as request msg
39 Response Code an 2
70 Network Management n3 301 / 001 / 002
Information Code
2.2 ATM Transaction Messages
Following are the formats for all messages received by ATMS for processing.

2.2.1 Cash Withdrawal Request Message Format

Bit Name Format Attr Values Remarks
Message Type n4 1200 / 1220 / 1201 /
1221 / 1400 / 1420 /
1401 / 1421
1 BIT MAP b1 Mandatory
2 Primary, Account Number LLVAR n...19 Mandatory
3 Processing Code n6 011000 / 012000 Mandatory
4 Amount, Transaction n 12 Mandatory
5 Amount, Settlement n 12
7 Transmission Date & Time MMDDhhmmss n 10 Mandatory
9 Conversion Rate, Settlement n8
10 Conversion Rate, Cardholder Billing n8
11 System Trace Audit Number n6 Mandatory
12 Time, Local Transaction hhmmss n6 Mandatory
13 Date, Local Transaction MMDD n4 Mandatory
15 Date, Settlement MMDD n4 Mandatory
17 Date, Capture MMDD n4 Mandatory
28 Amount, Transaction Fee x+n8
29 Amount, Settlement Fee x+n8
30 Amount, Transaction Processing Fee x+n8
31 Amount, Settlement Processing Fee x+n8
32 Acquiring Institution Identification LLVAR n.. 11 Mandatory
Code
33 Forwarding Institution Identification LLVAR n.. 11
Code
41 Card Acceptor Terminal ans 8 Mandatory
Identification
42 Card Acceptor Identification Code ans 15 Mandatory
49 Currency Code, Transaction n3 Mandatory
50 Currency Code, Settlement n3
90 Original Data Elements Mandatory in case message
- Org Message Type n4 type is 1400 / 1420 / 1401 /
- Org STAN n6 1421
- Org Xmit Date & Time MMDDhhmmss n 10
- Org Acq. Inst. Code n 11
- Org Fwd. Inst. Code n 11
95 Replacement Amounts Present in case message type
- Actual Amt., Transaction n 12 is 1400 / 1420 / 1401 / 1421
- Actual Amt., Settlement n 12
- Actual Amt., Txn. Fee x+n8
- Actual Amt., Stl. Fee x+n8
- Actual Amt, Txn. Proc. Fee x+n8
- Actual Amt, Stl. Proc. Fee x+n8
102 From Account Number LLVAR Ans..28 Mandatory

2.2.2 Cash Withdrawal Response Message Format

Bit Name Format Attr Values Remarks
Message Type n4 0210 / 0230 / 0410 /
0430
1 BIT MAP b1
2 Primary, Account Number LLVAR n...19 Same as request msg
 3 Processing Code n6 Same as request msg
4 Amount, Transaction n 12 Same as request msg
5 Amount, Settlement n 12
6 Amount, Cardholder Billing n 12
7 Transmission Date & Time MMDDhhmmss n 10 Same as request msg
8 Amount, Cardholder Billing Fee n8
9 Conversion Rate, Settlement n8
10 Conversion Rate, Cardholder Billing n8
11 System Trace Audit Number n6 Same as request msg
12 Time, Local Transaction hhmmss n6 Same as request msg
13 Date, Local Transaction MMDD n4 Same as request msg
15 Date, Settlement MMDD n4 Same as request msg
17 Date, Capture MMDD n4 Same as request msg
28 Amount, Transaction Fee x+n8
29 Amount, Settlement Fee x+n8
30 Amount, Transaction Processing Fee x+n8
31 Amount, Settlement Processing Fee x+n8
32 Acquiring Institution Identification LLVAR n.. 11 Same as request msg
Code
33 Forwarding Institution Identification LLVAR n.. 11
Code
39 Response Code an 2
41 Card Acceptor Terminal ans 8 Same as request msg
Identification
42 Card Acceptor Identification Code ans 15 Same as request msg
49 Currency Code, Transaction n3 Same as request msg
50 Currency Code, Settlement n3
51 Currency Code, Cardholder Billing n3
54 Additional Amounts LLVAR an ..120
- Net Available Balance n2+n2+n3+x+n12
- Uncleared Funds n2+n2+n3+x+n12
- Ledger Balance n2+n2+n3+x+n12
60 Reserved Private ans...999
- Year, Transaction YYYY n4 Same as request msg
- Year, Settlement YYYY n4 Same as request msg
- Year, Capture YYYY n4 Same as request msg
- Year, Transmission YYYY n4 Same as request msg
90 Original Data Elements Present in case message type
- Org Message Type n4 Same as request msg is 1400 / 1420 / 1401 / 1421
- Org STAN n6 Same as request msg
- Org Xmit Date & Time MMDDhhmmss n 10 Same as request msg
- Org Acq. Inst. Code n 11 Same as request msg
- Org Fwd. Inst. Code n 11 Same as request msg
95 Replacement Amounts Present in case message type
- Actual Amt., Transaction n 12 is 1400 / 1420 / 1401 / 1421
- Actual Amt., Settlement n 12
- Actual Amt., Txn. Fee x+n8
- Actual Amt., Stl. Fee x+n8
- Actual Amt, Txn. Proc. Fee x+n8
- Actual Amt, Stl. Proc. Fee x+n8
102 From Account Number LLVAR Ans..28 Mandatory

2.2.3
Bit Name Format Attr Values Remarks
Message Type n4 1200 / 1220 / 1201 /
1221 / 1400 / 1420 /
1401 / 1421
1 BIT MAP b1 Mandatory
2 Primary, Account Number LLVAR n...19 Mandatory
 3 Processing Code n6 211000/212000 Mandatory
4 Amount, Transaction n 12 Mandatory
5 Amount, Settlement n 12
7 Transmission Date & Time MMDDhhmmss n 10 Mandatory
9 Conversion Rate, Settlement n8
10 Conversion Rate, Cardholder Billing n8
11 System Trace Audit Number n6 Mandatory
12 Time, Local Transaction hhmmss n6 Mandatory
13 Date, Local Transaction MMDD n4 Mandatory
15 Date, Settlement MMDD n4 Mandatory
17 Date, Capture MMDD n4 Mandatory
28 Amount, Transaction Fee x+n8
29 Amount, Settlement Fee x+n8
30 Amount, Transaction Processing Fee x+n8
31 Amount, Settlement Processing Fee x+n8
32 Acquiring Institution Identification LLVAR n.. 11 Mandatory
Code
33 Forwarding Institution Identification LLVAR n.. 11
Code
41 Card Acceptor Terminal ans 8 Mandatory
Identification
42 Card Acceptor Identification Code ans 15 Mandatory
49 Currency Code, Transaction n3 Mandatory
50 Currency Code, Settlement n3
90 Original Data Elements Mandatory in case message
- Org Message Type n4 type is 1400 / 1420 / 1401 /
- Org STAN n6 1421
- Org Xmit Date & Time MMDDhhmmss n 10
- Org Acq. Inst. Code n 11
- Org Fwd. Inst. Code n 11
95 Replacement Amounts Present in case message type
- Actual Amt., Transaction n 12 is 1400 / 1420 / 1401 / 1421
- Actual Amt., Settlement n 12
- Actual Amt., Txn. Fee x+n8
- Actual Amt., Stl. Fee x+n8
- Actual Amt, Txn. Proc. Fee x+n8
- Actual Amt, Stl. Proc. Fee x+n8
103 To Account Number LLVAR Ans..28 Mandatory

2.2.4 Balance Enquiry Request Message Format

Bit Name Format Attr Values Remarks
Message Type n4 1200 / 1220 / 1201 /
1221 / 1400 / 1420 /
1401 / 1421
1 BIT MAP b1 Mandatory
2 Primary, Account Number LLVAR n...19 Mandatory
3 Processing Code n6 301000 / 312000 Mandatory
4 Amount, Transaction n 12 000000000000
5 Amount, Settlement n 12
7 Transmission Date & Time MMDDhhmmss n 10 Mandatory
9 Conversion Rate, Settlement n8
10 Conversion Rate, Cardholder Billing n8
11 System Trace Audit Number n6 Mandatory
12 Time, Local Transaction hhmmss n6 Mandatory
13 Date, Local Transaction MMDD n4 Mandatory
15 Date, Settlement MMDD n4 Mandatory
17 Date, Capture MMDD n4 Mandatory. This date is
passed to back-end modules
as the value date associated
 with the transaction
28 Amount, Transaction Fee x+n8
29 Amount, Settlement Fee x+n8
30 Amount, Transaction Processing Fee x+n8
31 Amount, Settlement Processing Fee x+n8
32 Acquiring Institution Identification LLVAR n.. 11 Mandatory
Code
33 Forwarding Institution Identification LLVAR n.. 11
Code
41 Card Acceptor Terminal ans 8 Mandatory
Identification
42 Card Acceptor Identification Code ans 15
49 Currency Code, Transaction n3 Mandatory
50 Currency Code, Settlement n3
60 Reserved Private LLLVAR ans...999 Mandatory
(Network info ) ans 4 (ONUS / VISA / MAST )

90 Original Data Elements Mandatory in case message

- Org Message Type n4 type is 1400 / 1420 / 1401 /
- Org STAN n6 1421
- Org Xmit Date & Time MMDDhhmmss n 10
- Org Acq. Inst. Code n 11
- Org Fwd. Inst. Code n 11
95 Replacement Amounts Present in case message type
- Actual Amt., Transaction n 12 is 1400 / 1420 / 1401 / 1421
- Actual Amt., Settlement n 12
- Actual Amt., Txn. Fee x+n8
- Actual Amt., Stl. Fee x+n8
- Actual Amt, Txn. Proc. Fee x+n8
- Actual Amt, Stl. Proc. Fee x+n8
102 From Account Number LLVAR Ans..28 Mandatory
2.2.5 Balance Enquiry Response Message Format
Bit Name Format Attr Values Remarks
Message Type n4 0210 / 0230 / 0410 /
0430
1 BIT MAP b1
2 Primary, Account Number LLVAR n...19 Same as request msg
3 Processing Code n6 Same as request msg
4 Amount, Transaction n 12 Same as request msg
5 Amount, Settlement n 12
6 Amount, Cardholder Billing n 12
7 Transmission Date & Time MMDDhhmmss n 10 Same as request msg
8 Amount, Cardholder Billing Fee n8
9 Conversion Rate, Settlement n8
10 Conversion Rate, Cardholder Billing n8
11 System Trace Audit Number n6 Same as request msg
12 Time, Local Transaction hhmmss n6 Same as request msg
13 Date, Local Transaction MMDD n4 Same as request msg
15 Date, Settlement MMDD n4 Same as request msg
17 Date, Capture MMDD n4 Same as request msg
28 Amount, Transaction Fee x+n8
29 Amount, Settlement Fee x+n8
30 Amount, Transaction Processing Fee x+n8
31 Amount, Settlement Processing Fee x+n8
32 Acquiring Institution Identification LLVAR n.. 11 Same as request msg
Code
33 Forwarding Institution Identification LLVAR n.. 11 Same as request msg
Code
39 Response Code an 2
41 Card Acceptor Terminal ans 8 Same as request msg
Identification
42 Card Acceptor Identification Code ans 15 Same as request msg
49 Currency Code, Transaction n3 Same as request msg
50 Currency Code, Settlement n3
51 Currency Code, Cardholder Billing n3
54 Additional Amounts LLVAR an ..120
- Net Available Balance n2+n2+n3+x+n12
- Uncleared Funds n2+n2+n3+x+n12
- Ledger Balance n2+n2+n3+x+n12
60 Reserved Private LLLVAR ans...999 Mandatory
(Network info ) ans 4 (ONUS / VISA / MAST )

90 Original Data Elements Present in case message type

- Org Message Type n4 Same as request msg is 1400 / 1420 / 1401 / 1421
- Org STAN n6 Same as request msg
- Org Xmit Date & Time MMDDhhmmss n 10 Same as request msg
- Org Acq. Inst. Code n 11 Same as request msg
- Org Fwd. Inst. Code n 11 Same as request msg
95 Replacement Amounts Present in case message type
- Actual Amt., Transaction n 12 is 1400 / 1420 / 1401 / 1421
- Actual Amt., Settlement n 12
- Actual Amt., Txn. Fee x+n8
- Actual Amt., Stl. Fee x+n8
- Actual Amt, Txn. Proc. Fee x+n8
- Actual Amt, Stl. Proc. Fee x+n8
102 From Account Number LLVAR Ans..28 Mandatory
2.2.6 Mini Statement Enquiry Request Message Format
Bit Name Format Attr Values Remarks
Message Type n4 1200 / 1220 / 1201 /
1221 / 1400 / 1420 /
1401 / 1421
1 BIT MAP b1 Mandatory
2 Primary, Account Number LLVAR n...19 Mandatory
3 Processing Code n6 381000 / 382000 Mandatory
4 Amount, Transaction n 12 000000000000
5 Amount, Settlement n 12
7 Transmission Date & Time MMDDhhmmss n 10 Mandatory
9 Conversion Rate, Settlement n8
10 Conversion Rate, Cardholder Billing n8
11 System Trace Audit Number n6 Mandatory
12 Time, Local Transaction hhmmss n6 Mandatory
13 Date, Local Transaction MMDD n4 Mandatory
15 Date, Settlement MMDD n4 Mandatory
17 Date, Capture MMDD n4 Mandatory. This date is
passed to back-end modules
as the value date associated
with the transaction
28 Amount, Transaction Fee x+n8
29 Amount, Settlement Fee x+n8
30 Amount, Transaction Processing Fee x+n8
31 Amount, Settlement Processing Fee x+n8
32 Acquiring Institution Identification LLVAR n.. 11 Mandatory
Code
33 Forwarding Institution Identification LLVAR n.. 11
Code
41 Card Acceptor Terminal ans 8 Mandatory
Identification
42 Card Acceptor Identification Code ans 15
49 Currency Code, Transaction n3 Mandatory
50 Currency Code, Settlement n3
60 Reserved Private LLLVAR ans...999 Mandatory
(Network info ) ans 4 (ONUS / VISA / MAST )

90 Original Data Elements Mandatory in case message

- Org Message Type n4 type is 1400 / 1420 / 1401 /
- Org STAN n6 1421
- Org Xmit Date & Time MMDDhhmmss n 10
- Org Acq. Inst. Code n 11
- Org Fwd. Inst. Code n 11
95 Replacement Amounts Present in case message type
- Actual Amt., Transaction n 12 is 1400 / 1420 / 1401 / 1421
- Actual Amt., Settlement n 12
- Actual Amt., Txn. Fee x+n8
- Actual Amt., Stl. Fee x+n8
- Actual Amt, Txn. Proc. Fee x+n8
- Actual Amt, Stl. Proc. Fee x+n8
102 From Account Number LLVAR Ans..28 Mandatory
2.2.7 Mini Statement Enquiry Response Message Format
Bit Name Format Attr Values Remarks
Message Type n4 0210 / 0230 / 0410 /
0430
1 BIT MAP b1
2 Primary, Account Number LLVAR n...19 Same as request msg
3 Processing Code n6 Same as request msg
4 Amount, Transaction n 12 Same as request msg
5 Amount, Settlement n 12
6 Amount, Cardholder Billing n 12
7 Transmission Date & Time MMDDhhmmss n 10 Same as request msg
8 Amount, Cardholder Billing Fee n8
9 Conversion Rate, Settlement n8
10 Conversion Rate, Cardholder Billing n8
11 System Trace Audit Number n6 Same as request msg
12 Time, Local Transaction hhmmss n6 Same as request msg
13 Date, Local Transaction MMDD n4 Same as request msg
15 Date, Settlement MMDD n4 Same as request msg
17 Date, Capture MMDD n4 Same as request msg
28 Amount, Transaction Fee x+n8
29 Amount, Settlement Fee x+n8
30 Amount, Transaction Processing Fee x+n8
31 Amount, Settlement Processing Fee x+n8
32 Acquiring Institution Identification LLVAR n.. 11 Same as request msg
Code
33 Forwarding Institution Identification LLVAR n.. 11 Same as request msg
Code
39 Response Code an 2
41 Card Acceptor Terminal ans 8 Same as request msg
Identification
42 Card Acceptor Identification Code ans 15 Same as request msg
49 Currency Code, Transaction n3 Same as request msg
50 Currency Code, Settlement n3
51 Currency Code, Cardholder Billing n3
54 Additional Amounts LLVAR an ..120
- Net Available Balance n2+n2+n3+x+n12
- Uncleared Funds n2+n2+n3+x+n12
- Ledger Balance n2+n2+n3+x+n12
60 Reserved Private LLLVAR ans...999 Mandatory
(Network info ) ans 4 (ONUS / VISA / MAST )

90 Original Data Elements Present in case message type

- Org Message Type n4 Same as request msg is 1400 / 1420 / 1401 / 1421
- Org STAN n6 Same as request msg
- Org Xmit Date & Time MMDDhhmmss n 10 Same as request msg
- Org Acq. Inst. Code n 11 Same as request msg
- Org Fwd. Inst. Code n 11 Same as request msg
95 Replacement Amounts Present in case message type
- Actual Amt., Transaction n 12 is 1400 / 1420 / 1401 / 1421
- Actual Amt., Settlement n 12
- Actual Amt., Txn. Fee x+n8
- Actual Amt., Stl. Fee x+n8
- Actual Amt, Txn. Proc. Fee x+n8
- Actual Amt, Stl. Proc. Fee x+n8
127 Reserved Private n ..999 Present in case message type
- No of entries n2 is 1200 / 1201 / 1220 / 1221
The following details appear ‘No of
Entries’ times :
 - Org. Branch Code n4
- Transaction Literal an 3
- Txn Amount Sign a1
- Txn Amount n 12
- Debit/Credit Flag x
- Value Date DDMMYYYY n8
- Transmission Date DDMMYYYY n8
- Txn. STAN n6
102 From Account Number LLVAR Ans..28 Mandatory

3. ISO Field Descriptions

This chapter provides a description of the fields used in an ISO 8583 compliant message1.

3.1 Message Type

Field No Format Attr
n4

This field indicates the type of the message received for processing. For details of all possible
list of message types, refer to the ISO 8583 - Bank Card Originated Messages - Interchange
message specifications - Content for financial transactions document.

3.2 BIT MAP

Field No Format Attr
1 b1

This field, 128 bits (16 bytes) in length, is used as a bit field with the bits numbered from the
left starting at 1. Each bit indicates the presence (1) or the absence (0) in the message of the
data element associated with that particular bit. Bit 1 (used to indicate the presence of the
secondary bitmap2) should always be set.

3.3 Field #2 - Primary, Account Number

Field No Format Attr
2 LLVAR n ..19

This field contains the primary account number (PAN).

3.4 Field #3 - Processing Code

Field No Format Attr
3 n6

Positions 1 and 2 describe a specific message.

00-19 Debits
20-29 Credits
30-39 Enquiries

1
Before proceeding with this chapter, the reader should be conversant with the ISO 8583 message format. To get details of the
ISO 8583 message format, refer to the ‘INTERNATIONAL STANDARD - ISO 8583 - Bank Card Originated Messages -
Interchange Message Specifications - Content for Financial Transactions’ document
2
Refer to the ISO Standard for a complete description of the bitmap.
 40-49 Transfers

Positions 3 and 4 describe the account type affected for debits, credits, enquiries and the
debit account for transfers. Positions 5 and 6 describe the account type affected for credits
and the credit account for transfers.
10 Savings
20 Current

3.5 Field #4 - Amount, Transaction

Field No Format Attr
4 n 12

This field contains the transaction amount in the transaction currency. This amount is
expressed in lowest denominations.

3.6 Field #5 - Amount, Settlement

Field No Format Attr
5 n 12

This field contains the transaction amount in the local currency. This amount is expressed in
lowest denominations. This field is not supported as of now

3.7 Field #6 - Amount, Billing

Field No Format Attr
6 n 12

This field contains the transaction amount in the PAN currency. This amount is expressed in
lowest denominations. This field is not supported as of now

3.8 Field #7 - Transmission Date and Time

Field No Format Attr
7 MMDDhhmmss n 10

The client stamps the date and time in this field before transmitting the message.

3.9 Field #8 - Amount, Cardholder Billing Fee

Field No Format Attr
8 n8

This field contains the total fee charged to the PAN in the PAN currency. This field is not
supported as of now

3.10 Field #9 - Conversion Rate, Settlement

Field No Format Attr
9 n8
This field contains the factor used in conversion from a transaction currency amount to a local
currency amount. The left most digit indicates the number of decimal places from the right.

3.11 Field #10 - Conversion Rate, Billing

Field No Format Attr
10 n8

This field contains the factor used in conversion from a transaction currency amount to a PAN
currency amount. The left most digit indicates the number of decimal places from the right.
This field is not supported as of now

3.12 Field #11 - System Trace Audit Number

Field No Format Attr
11 n6

This field contains a running sequence number maintained by a client. This number is
stamped by the client when the message is transmitted.

3.13 Field #12 - Time, Local Transaction

Field No Format Attr
12 hhmmss n6

This field contains the local time at which the transaction associated with the message
occurred at the client.

3.14 Field #13 - Date, Local Transaction

Field No Format Attr
13 MMDD n4

This field contains the local date at which the transaction associated with the message
occurred at the client.

3.15 Field #15 - Date, Settlement

Field No Format Attr
13 MMDD n4

This field contains the date on which settlement between the gateway and intermediate
network facilities will be done. This field is not supported as of now

3.16 Field #17 - Date, Capture

Field No Format Attr
13 MMDD n4

This field contains the date on which the transaction was processed by the acquirer. This field
is not supported as of now
3.17 Field #28 - Amount, Transaction Fee
Field No Format Attr
28 x+n8

This field contains the fee charged by the acquirer (in the transaction currency) for transaction
activity.

3.18 Field #29 - Amount, Settlement Fee

Field No Format Attr
29 x+n8

This field contains the fee charged by the acquirer (in the local currency) for transaction
activity.

3.19 Field #30 - Amount, Transaction Processing Fee

Field No Format Attr
30 x+n8

This field contains the fee charged (in the transaction currency) for the handling and routing of
messages (forwarder fee).

3.20 Field #31 - Amount, Settlement Processing Fee

Field No Format Attr
31 x+n8

This field contains the fee charged (in the local currency) for the handling and routing of
messages (forwarder fee).

3.21 Field #32 - Acquiring Institution Identification Code

Field No Format Attr
32 LLVAR n.. 11

This field contains the code identifying the acquiring institution.

3.22 Field #33 - Forwarding Institution Identification Code

Field No Format Attr
33 LLVAR n.. 11

This field contains the code identifying the institution forwarding a message (forwarder) in an
interchange system.

3.23 Field #39 - Response Code

Field No Format Attr
39 an 2
ATMS sends back the status of a message processed in this field 3.

3.24 Field #41 - Card Acceptor Terminal Identification

Field No Format Attr
42 ans 8

This field contains a unique code identifying a terminal at the card acceptor location.

3.25 Field #42 - Card Acceptor Identification Code

Field No Format Attr
42 An 15

This field contains a code identifying the card acceptor, which defines the point of the
transaction.

3.26 Field #48 - Additional Data - Private

Field No Format Attr
48 LLVAR ans...999

This field is used internally in FLEXCUBE.

3.27 Field #49 - Currency Code, Transaction

Field No Format Attr
49 n3

This field contains the code of the currency in which the transaction took place.

3.28 Field #50 - Currency Code, Settlement

Field No Format Attr
50 n3

This field contains the code of the local currency. This field is not supported as of now

3.29 Field #51 - Currency Code, Cardholder Billing

Field No Format Attr
51 n3

This field contains the currency code of the PAN. This field is not supported as of now

3.30 Field #54 - Additional Amounts

Field No Format Attr
54 LLVAR an...120

This field contains information on up to six amounts and related account data. An amount is
represented as :
3
Refer to the ISO Standard for a list of response codes sent back by ATMS
n2 (A/c Type) + n2 (Amt. Type) + n3 (Currency Code)+ x (Debit / Credit) + n12 (Amt.)

with the break-up of the field as follows :

3.30.1 Account Type (n2)

As defined in position 3 and 4 or 5 and 6 of processing code

3.30.2 Amount Type (n2)

01 Ledger Balance
02 Net Available Balance
03 Uncleared Funds

3.30.3 Currency Code (n3)

3.30.4 Debit/Credit Code (x)

D Debits
C Credits

3.30.5 Amount ( n12)

3.31 Field #60 - Reserved Private –Network Information

Field No Format Attr
60 LLLVAR ans...999

Network information will be sent by NOMAD CORTEX in 4 digit length. Hence the any of the
following are expected.

004ONUS
004VISA
004MAST

3.32 Field #70 – Network Management Information Code

Field No Format Attr
70 n3

This field is used in conjunction with Network Management Messages (message types 1800,
1801, 1820, 1821) to indicate the network status. FLEXCUBE will support the following values
in this field :

Value Meaning
301 Echo Test
001 SignOn
002 SignOff
3.33 Field #90 - Original Data Elements
Field No Format Attr
90 n 42

This field contains the basic details of the original message in case of reversal messages
(1400 / 1401 / 1420 / 1421). This field contains the following subfields (all subfields are of
fixed length with an absence of data indicated by zeros) :

Name of Subfield Format Attr

Original Message Type n4
Original STAN n6
Original Transmission Date & Time MMDDhhmmss n 10
Original Acquiring Institution Code n 11
Original Forwarding Institution Code n 11

3.33.1 Original Message Type

This subfield contains the message type of the message being reversed. Original STAN
This subfield contains the STAN of the message being reversed.

3.33.2 Original Transmission Date & Time

This subfield contains the transaction date and time of the message being reversed.

3.33.3 Original Acquiring Institution Code

This subfield contains the acquiring institution identification code of the message being
reversed.

3.33.4 Original Forwarding Institution Code

This subfield contains the forwarding institution identification code of the message being
reversed.

3.34 Field #95 - Replacement Amounts

Field No Format Attr
95 n 42

This field is used when attempting to partially or wholly reverse a message ( 1400 / 1420). The
original message amounts will be present in the appropriate data elements. This field contains
the following subfields4 (all subfields are of fixed length with an absence of data indicated by
zeros) :

Name of Subfield Format Attr

Actual Amount, Transaction n 12
Actual Amount Settlement n 12
Actual Amount, Transaction fee x+n8
Actual Amount, Settlement fee x+n8
Actual Amount, Transaction Processing Fee x+n8
Actual Amount, Settlement Processing Fee x+n8

4
The format of field #95 deviates from the format specified in the ISO standard. This is done to incorporate the replacement
forwarder fees.
3.34.1 Actual Amount, Transaction
This subfield contains the actual transaction amount in the transaction currency.

3.34.2 Actual Amount, Settlement

This subfield contains the actual transaction amount in the local currency.

3.34.3 Actual Amount, Transaction fee

This subfield contains the actual fee, in the transaction currency, charged by the acquirer.

3.34.4 Actual Amount, Settlement fee

This subfield contains the actual fee, in the local currency, charged by the acquirer.

3.34.5 Actual Amount, Transaction Processing fee

This subfield contains the actual fee, in the transaction currency, charged by the forwarder.

3.34.6 Actual Amount, Settlement Processing fee

This subfield contains the actual fee, in the local currency, charged by the forwarder.

3.35 Field #102 - Account Identification 1

Field No Format Attr
102 LLVAR ans..28

Debit Account number used in debit transaction types

3.36 Field #103 - Account Identification 2

Field No Format Attr
103 LLVAR n..28

Credit Account number used in credit transaction types

3.37 Field #127 - Reserved Private

This field will be used to send back details for the purpose of mini-statement enquiries. This
field contains the following subfields :

Name of Subfield Format Attr

No of entries n2
The following details are
repeated ‘No of Entries’ times:
Originating Branch Code n3
Transaction Literal an 3
Transaction Amount Sign a1
Transaction Amount n 12
Debit / Credit Flag X
Value Date DDMMYYYY n8
Transmission Date DDMMYYYY n8
Transaction STAN n6
3.37.1 No of entries
This subfield contains the number of mini-statement entries that are being sent back in the
message. The actual mini-statement entries follow this subfield.

3.37.2 Originating Branch Code

This subfield contains the originating branch code associated with the transaction.

3.37.3 Transaction Literal

This subfield contains the literal associated with the transaction.

3.37.4 Transaction Amount Sign

This subfield contains the transaction amount sign (‘+’ or ‘-’).

3.37.5 Transaction Amount

This subfield contains the amount associated with the transaction. The amount is expressed
in lowest denominations.

3.37.6 Debit/Credit Flag

This subfield is associated with the transaction amount and indicates whether the amount is a
debit or a credit (‘D’ or ‘C’).

3.37.7 Value Date

This subfield contains the date on which the transaction was processed by the acquirer. This
date is used by the FLEXCUBE back-end for the processing of the transaction.

3.37.8 Transmission Date

This subfield contains the date the message associated with the transaction was transmitted
by the client to FLEXCUBE

3.37.9 Transaction STAN

This subfield contains STAN of the message associated with the transaction

**********************

Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores, CA 94065
U.S.A.

Worldwide Inquiries:
Phone: +1.650.506.7000
Fax: +1.650.506.7200
oracle.com

Copyright © 2017, Oracle and/or its affiliates. All rights reserved.

This document is provided for information purposes only and the contents hereof are subject
to change without notice.

This document is not warranted to be error-free, nor subject to any other warranties or
conditions, whether expressed orally or implied in law, including implied warranties and
conditions of merchantability or fitness for a particular purpose. We specifically disclaim any
liability with respect to this document and no contractual obligations are formed either directly
or indirectly by this document. This document may not be reproduced or transmitted in any
form or by any means, electronic or mechanical, for any purpose, without our prior written
permission.

Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may
be trademarks of their respective owners.