ATM USER GUIDE R20

Introduction to ATM Framework

ATM Framework provides a structure to define ISO message fields, provide information for mapping the
ISO message fields to Temenos Transact, define the way the ATM Transactions updates Temenos
Transact, the ISO response code to be sent back to the Switch, etc,. The Structure of the ISO Message
to be sent from the Switch and the way ATM Transactions updates are done in Temenos Transact can be
customized using the framework.

Background
The ATM Interface has been widely used across all Temenos Transact installations. ATM Framework
provides required tables to customise the ISO message according to the requirement of the ATM Switch
used by the Bank.

The ATM Interface is developed as a middle layer between the ATM SWITCH and Temenos
Transact. The interface consists of a plug-in for Application Server to receive the messages via a
dedicated port and translate the ISO messages. Application Server sends the ISO message to Temenos
Transact, where the ISO message is converted to OFS message format based on the mapping files
specified in the interface. After the transaction has been completed at Temenos Transact, the response
ISO messages are formatted within the scope of the ATM Interface. The response messages are
indicated with the appropriate error or ok status depending upon the Temenos Transact applications reply
status requested in the framework.

The protocol used for communication between the host and the switch is usually TCP/ IP via sockets.
ATM interface provide a high performance multi-threaded synchronous socket listener that has custom
functionality/ intelligence built-in for handling ISO messages with length prefix through TCP/ IP.

The Application Server can be configured for listening ISO messages on any number of ports as required
by the load on the site. However, a judicious choice should be made considering the load so that not to
leave too many ports listening idle. The switch should try to throw open multiple sockets/ connections on
the same port(s) when the load increase

ATM Framework supports all standard ATM Transactions like Cash withdrawal, Point of Sale, Balance
enquiry, Mini statement, Statement request, Account transfer, Cash Deposit and Cheque Book Request.

ATM Interface supports ISO 8583:87 and ISO 8583:93 versions only. Support to different version will
require modification to the ISO message parser routines. The application servers supported by ATM
interface is TC Server, Jboss, Websphere and Weblogic.

In addition to the core ATM framework, the latest release also support the ATMFRM for a Enterprise
Service Bus (ESB) implementation as well. Currently, its implemented through IBM Integration Bus V9.
This implementation is currently configured to communicate over the MQ queues. It can be configured to
TCP/ IP port as well.
New Functionality
 A parameter table to capture the ATM message type to be processed, the type of log to be
updated, the location where the log is to be updated, the versions that are to be used to rrase ISO
request from Temenos Transact, the default Terminal id’s to use for identifying the account for
posting transactions, etc

 A parameter table to capture the ISO Response message for success and failure transactions
and for failed transactions, the code to be used for each type of error faced

 A parameter table to capture the Charge conditions

 Additional parameter table to capture extra charges to be posted

 A parameter table to capture the skeleton of the ISO message to be used

 A parameter table to capture the ISO message field and it’s mapping to Temenos Transact fields
for each type of ATM transaction and the acquirer of the ATM/ POS machine

 A Template to capture the ATM transaction details from information purpose and for retrieval
during Reversal request

 Several mapping routines for converting the data in the ISO message to Temenos
Transact recognizable value or for mapping it with the required Temenos Transact table

 Routines for parsing the ISO message and generating the required Temenos
Transact transaction and forming the response message in return to the Switch, depending on
the success or failure of the ATM Transaction and the required response codes mapped in the
system

 Routines to generate Charges as part of the ATM Transaction being processed or raise them as
a separate transaction

 Utility Routine to parse the ISO Request and Response message from Temenos Transact for
enquiry purpose

 Java Components for Listeners

 A New Application Template (ATM.ISO.MESSAGE) been created to store and process ATM ISO
request & response message from & to ATM Switch. This Application will act as a gateway for
ATM message flow from /to ATM Switch

 Parsing and Routing logic been handled as part of middleware ESB (right now planning for
solution with IBM Integration Bus along with Temenos Transact IIB Outbound Adapter)

 MQ’s for Listeners, There is an option to have TCPIP for Listener

Benefits
 ATM Framework is a Gpack offering and is used in many Temenos Transact installations. By
adding the functionaltity as part of Core will enable delivery through Builds and source code
maintenance will be simple

 Any enhancements to the development, will be available for other clients during their upgrade or
new installation

 ATMFRM can be implemented through ESB (Currently ISO8583 Compatibilities only). And IBM
Integration Bus compatible package will be available for clients during their upgrade or new
Installation. Easy in implementing similar approach with other ESB’s Oracle service Bus or
BizTalk

Configuring ATM Framework

The following configurations are required for ATM Framework:

Configuring the ATM/ BASE24/ PHOENIX

NOTE:

Please find the below explanation about additional parameters used in the iso listener and all parameters
are mandatory.

 HEADERTYPE – DECIMAL

 HEADERLENGTH – 4 (i.e. 0074 represents length of the message in decimal)

 IGNORENEXTHEADERBYTE - Here no characters has to be ignored

 CONSTHEADERLEN - Here constant header length is 19 (i.e. 1204 120412040000 N)

 BITMAP – message bitmap (Here it is a HEXA)

1. The <PARAMETER> tag needs to contain the OFS.SOURCE record to be used by this adapter.
The record is supplied along with the package.

2. Restart tc (stop and start) so that it will load the new configuration and the plugin.

3. Once the listener is identified as a valid plug-in it will be listed along with all other listeners when
the tc is started in the global.log file under tcserver/log.
 4. After this, there will be an entry for this listener in tcslog.properties file under /conf which will
decide what should be logging level for this listener. The same can be changed to DEBUG during
the installation/ setup.

5. The following screen-shot shows the tcslog.properties some of the entries shown will appear after
the first run of the interface.

Testing the Listener Configuration

Logging Setup

Configuring the INTRF.MESSAGE Application

This application facilitates capturing the ISO message skeleton as per the ATM Switch vendor. The ISO
fields that will be expected in the message and their lname, length, parsing logic, etc, are defined in this
table

Below is a setup for ISO Base II type message.

1. ISO field name, their position in the message, the length, type, etc are defined in the table. For
variable length fields, the length of the field will be specified in the ISO message, followed by the
field value.

2. For fields with variable length, the fields will be dynamically parsed based on the information in
the field type and length. Eg, bitmap, Account number, etc. The account number length can vary
from place to place. In the position defined for Account number, the switch will send the length for
account number, followed by the account number itself. The ISO parsing routine will have to
process the ISO field of variable length by reading the account length in the defined position, and
then reading the number of characters after the field, as per the field length.

3. Where required, the values in ISO fields can be converted to Temenos Transact identified values
by attaching a routine to the field in Transaction field position . eg, Currency code. The ISO
Currency code passed in the system is converted using a routine to ISO Currency by reading
the NUMERIC.CURRENCY table in Temenos Transact. Any such conversion required can be done
by attached a routine to the mentioned field.

Configuring the INTRF.MAPPING Application

This table defines how the ATM Transaction updates Temenos Transact. Based on the information
received in the ISO message, the type of transaction to be processed is identified and the required
transaction is processed in Temenos Transact based on the information provided in this table.

The mapping record to be picked for processing the ISO message is determined by the parsing routine by
reading the Mapping ID processing logic defined in ATM.PARAMETER table. The model bank setup is
defined as below.
 rd th
The ID will be formed by concatenating the 3 and 70 field, which is the MTI and the processing code
respectively, from the incoming ISO message.

Below are the list of MTI and supported in Temenos Transact, for which mapping records are available.

Transaction Type

Message Type [ISO 8583:87/93]

Processing Code

Purchase

0100/0200/0220/0420
1100/1200/1220/1420

00xx00

Withdrawal

0100/0200/0220/0420

1100/1200/1220/1420

01xx00

Fund Transfer

0200/0220/0420

1200/1220/1420

40xxyy

Balance Inquiry

0200

1200

30xx00

Mini Statement

0200

1200

38xx00

Cash Deposit

0200/0220/0420

1200/1220/1420

21xx00
Cheque Deposit

0200/0220/0420

1200/1220/1420

24xx00

Statement Request

0200/0220

1200/1220

35xx00

Cheque Issue

0200/0220

1200/1220

91xx00

Utility Bill Payment

0200/0220/0420

1200/1220/1420

50xx00

Network Message

0800

1800

-NA-
AUTHORISATION REQUEST

CASH WITHDRAWAL REQUEST

POS SALE REQUEST

CASH DEPOSIT REQUEST

CHEQUE DEPOSIT REQUEST

ACCOUNT BALANCE ENQUIRY REQUEST

MINI STATEMENT TXN REQUEST

STATEMENT REQUEST
 FUNDS TRANSFER REQUEST

ATM UTILITY PAYMENT REQUEST

ATM PAYMENT REQUEST USING THIRD PARTY

CASH DEPOSIT REVERSAL

NETWORK MESSAGE

Configuring the ATM.PARAMETER Application

This is the parameter table which governs the way the ATM Interface will work in relation to identifying the
message format, log messages, default terminal id’s etc, amount formatting rules etc,.

Configuring the ATM.RES.CODE.TABLE Application

This application defines the ERROR CODE RESPONSE for all the transactions.

Configuring the ATM.MTI Application

This application is used for capturing the supported ISO MTI’s. It is held for information only.

Configuring the ATM.PROCESSING.CODE Application

This application is held for capturing the valid processing codes system supports and the valid account
types that can process the captured processing code.

1. The valid account types are captured in table ATM.TERMINAL.ACCOUNT where the Terminal ID
or POS machine ID is recorded with the default account’s to be used. The account default can be
done depending on the account type (captured in field ACCT.TYPE or DEFAULT.ACCT.TYPE in
the table ATM.TERMINAL.ACCT).

2. While setting up the default accounts for processing code, the valid account types for which the
processing code can be provided will be validated using the information from this table.

EXAMPLE:

Cash deposit request is allowed only for our bank bin’s. So the account type mapped in the record ISO.21
is OUR.BIN. Hence in the table ATM.TERMINAL.ACCT, the account numbers to be used can be defaulted
by processing code only when the account type is set as ‘OUR.BIN’.

The following process types are available:

 WITHDRAWAL REQUEST

 CASH DEPOSIT

 CASH DEPOSIT

 CHEQUE DEPOSIT
  BALANCE ENQUIRY

 STATEMENT REQUEST

 MINI STATEMENT

 FUNDS TRANSFER

 UTILITY BILL PAYMENT

 PHOENIX WITHDRAWAL REQUEST

 PHOENIX CREDIT CARD PAYMENT

 PHOENIX BALANCE ENQUIRY

 PHOENIX FUNDS TRANSFER

 PHOENIX MINI STATEMENT

Configuring the ATM.CHG.TABLE Application

ATM.CHG.TABLE is used to specify the charges applicable for ATM transactions. Th ID needs to be
SYSTEM.

1. Charges can be specified as by BIN no, processing code, MTI, PROC, MTI.PROC.BIN,
MTI.PROC.BIN.CCY, MTI.PROC.CCY,NETWORK,NETWORK.CCY, PROC.NETWORK.CCY, by
currency, from the ISO message etc.

2. On verify the ATM.CHG.TABLE application, it will built the records in ATM.CHG.DETAIL as per
configurations.

3. Then system will post the charge for the respective setup through application in case of financial
transaction.

4. In order to raise charge Non-Financial, set the field Separate Ft as Yes and attach the rtn
AT.POST.CHG.TXN.RTN to the field PRE.RTN in the response mapping record
of INTRF.MAPPING.

NOTE:

Separate Ft is not applicable for the financial transaction like cash withdrawal ,cash deposit etc. For
financial transactions, separate entries can be achieved through setup in FT.GROUP.CONDITION:

PROC – processing Code (ISO,Field-3) , MTI - message type indicator (ISO-Field-0)

BIN – Bank IMD field in ATM.PARAMETER

NETWORK - Network IMD field in ATM.PARAMETER

Top up charges can be added by capturing the charge details in ATM.SPLIT.CHG.TABLE and linking
them to ATM.CHG.TABLE.
Configuring the ATM.CHG.DETAIL Application
Once the ATM.CHG.TABLE is updated & verified ATM.CHG.DETAIL table will update by quick reference
by charge processing routines.

Configuring the ATM.SPLIT.CHG.TABLE Application

This application is used to capture any additional charges required on top of transaction charges.

The record will be linked to ATM.CHG.TABLE for collecting additional charges.

Configuring the ATM.TERMINAL.ACCT Application

This application is used to capture the account numbers to be used for transaction processing.

Account numbers can be provided by currency or by processing code.

Our Bin

Our POS

Other Bank Bin

Other Bank Pos

Merchant Account

ATM Parametrization
The ATM Parametrization is described below:
INTRF.MESSAGE

INTRF.MAPPING

ATM.PARAMETER

ATM.TERMINAL.ACCT

ATM.TRANSACTION

ATM.DUAL.TRANSACTION

ATM.RES.CODE.TABLE

ATM.STMT.REQ

ATM.CHG.TABLE

ATM.CHG.DETAIL

ATM.SPLIT.CHG.TABLE
 ATM.PROCESSING.CODE

ATM.MTI

VERSIONS

ENQUIRES

SERVICES

Main Subroutines Descriptions

Formatting Transaction Messages

Below you can find details on how transaction messages are formatted.

Base24/ISO Transaction Message

The following messages are described below:

Message Header

Bitmap Message Format

PHOENIX Transaction Message

Formatting the ISO Message Field

Below you will find details on formatting the ISO Message field.
Base24/ ATM

Phoenix

Working with ATM Framework

This topic helps the user to work with the ATM Framework functionality.

General Flow Diagram

 How it works?
Purpose
Message Processing in Temenos Transact

Workflow by Transactions
Below are the transactions supported in Generic ATM Interface:

 Network Messages

 Balance Enquiry

 Cash Withdrawal Transactions

 Mini Statement Messages

 Statement Request*

 POS Transactions

 Intra Bank Funds Transfer Transactions

 Cash Deposit*

 Cheque Issue*

 Cheque Deposit*

 Utility Bill Payments*

 Cash Withdrawal Reversal

  Intra Bank Funds Transfer Reversal

 POS Reversal

 Cash deposit Reversal*

 Cheque Deposit Reversal*

 Utility Bill Payments Reversal*

NETWORK MESSAGES
BALANCE ENQUIRY
CASH WITHDRAWAL
MINI STATEMENT
STATEMENT REQUEST*
PURCHASE TRANSACTIONS
INTRABANK TRANSACTIONS
CASH DEPOSIT*
UTILITY BILL PAYMENT*
CHEQUE DEPOSIT*
CHEQUE BOOK REQUEST*
FULL REVERSALS
PARTIAL REVERSALS
PAYMENT VIA TELLER*

Tasks for ATM Framework

The following tasks are available for ATM Framework:

Core Deal Processing

The INTERFACE.TO field in ATM.PARAMETER table indicates whether the deal processing will be in FT
(Funds Transfer) or OFS clearing transaction mode.
Funds Transfer

Intra- Bank Funds Transfer

Point Of Sale (POS) Transaction

Account Statement Request

Cheque Request

OFS Clearing
Deal Processing through ESB
ISO Message and their updates to ATM.ISO,MESSAGE.IF.
Balance Enquiry

Outputs for ATM Framework

The following outputs are available for ATM Framework:

 View ATM statement requests;

 View ATM transactions;

 View failed transactions;

 View reversed transactions.