1

BASE 24 Training Material

BASE 24

www.cognizant.com
 2
BASE 24 Training Material

INDEX
SL NO TOPIC PAGE

1. Day 1 ---------
------------------------------------------------------------------------- 4
1.1 Introduction ------------------------------------------------------------------------------------ 4
2. Day 2 ---------
-------------------------------------------------------------------------- 6
2.1 Abbreviation for Base 24 -------------------------------------------------------------------- 6
2.2 ATM – Base 24 ------------------------------------------------------------------------------- 8
3. Day 3 ---------
-------------------------------------------------------------------------- 11
3.1 POS- Base 24 ---------------------------------------------------------------------------------- 11
3.2 ATM – Detailed Transaction ---------------------------------------------------------------- 13
3.3 POS- Detailed Transaction ----------------------------------------------------------------- 14
4. Day 4 ---------
-------------------------------------------------------------------------- 15
4.1 Base 24 Sub-volumes (naming convention) --------------------------------------------- 15
5. Day 5 ----------------------------------------------------------------------------------- 17
5.1 Compiler Procedures ------------------------------------------------------------------------- 17
6. Day 6 ---------------------------------------------------------------------------------
-- 18
6.1 Message Types ------------------------------------------------------------------------------- 18
7. Day 7 ----------------------------------------------------------------------------------- 19
7.1 Request Path for ATM Device Handler (C1000) ----------------------------------------- 19

7.2 Response Path for ATM Device Handler (C1000) --------------------------------------- 20

7.3 Request Path for ATM Device Handler (N50) -------------------------------------------- 21

7.4 Response Path for ATM Device Handler (N50) ------------------------------------------ 22

8. Day 8 ----------------------------------------------------------------------------------- 23
8.1 Request Path for AUTH ---------------------------------------------------------------------- 23
9. Day 9 ------------------------------------------------------------------------------------ 24
9.1 Request Path for HISO
------------------------------------------------------------------------ 24
9.2 Few File Details -------------------------------------------------------------------------------- 24
10. Day 10------------------------------------------------------------------------------------ 26

10.1 Different Base 24 Files ------------------------------------------------------------------------ 26

10.2 Authorization Options ------------------------------------------------------------------------- 27
10.3 Authorization Levels --------------------------------------------------------------------------- 27
10.4 Some more Files -------------------------------------------------------------------------------- 46
10.5 Refresh Process --------------------------------------------------------------------------------- 53
10.6 Extract Process ----------------------------------------------------------------------------------
54

www.cognizant.com
 3
BASE 24 Training Material

10.7 Interchange Interface Process ----------------------------------------------------------------- 55

www.cognizant.com
 4
BASE 24 Training Material

Change history:
Version Date Prepared by Reviewed By Comments
1.0 13/12/2007 Samarpita Deb Gaurav Kothari

www.cognizant.com
 5
BASE 24 Training Material

Day: 1 Date: 21.11.2007

: INTRODICTION :

 Base 24 is an application.

 Base 24 is based on the following configuration:

1. Hardware : TANDEM
2. Database : ENSCRIBE
3. Language : TAL, COBOL, SCOBOL
4. Tools : PATHCOM, FUP
5. Important component: XPNET.

 Base 24 also works as a middleware.

ATM BASE 24 HOST

 Some major parts of BASE24:

 ATM
 POS
 TELLER
 FHM
 REFRESH
 EXTRACT

 There are some base files which is common for all kind of channels [such as
ATM, POS etc].

 Generally there are 3 modules for ATM and 2 modules for POS reside within a
BASE 24.

 Also, a switch, INTERCHANGE is another major thing to be considered while

dealing with Base 24. It is used when BASE 24 is connected to some other BASE
24.

www.cognizant.com
 6
BASE 24 Training Material

 The message types for Base 24 are as follows:

Native BASE 24 External
ATM Mode Message HOST
Within BASE 24 Internal
Message Message (STM) (ISO)
(NMM)

 From ATM native mode message goes to B24. There, it converts the NMM to
internal message format, STM. When after routing it is destined for a particular
host, then it goes out as an External Message following the ISO message type.
While, getting response it follows the reverse route.

 The codes which are ACI made are known as Vanilla Code. And generally
we modify or enhance some vanilla codes according to customer’s need.

www.cognizant.com
 7
BASE 24 Training Material

Day: 2 Date: 22.11.2007

: ABBREVIATION FOR BASE 24:

PBF : Positive Balance File

FUP : File Utility Program
DH : Device Handler
ATD : ATM Terminal Data
TLF : Transaction Log File
CPF : Card Prefix File
CAF : Cardholder Authorization File
FIID : Financial Institution ID
HCF : Host Configuration File
HISO : Host Interface following ISO Standards
STM : Standard Internal Message
SEM : Standard External Message
IDF : Institution Definition File
DPC : Data Processing Center
HCF : Host Configuration File
ICF : Interchange Configuration File
BICI : Base24 Interchange Interface
RTAU : Route Authorization
EMV : Europay, Master Card and Visa
KEYI : ICC Key File
MAC : Message Authentication Code
LCONF : Logical Network Configuration File
PTD : Pos Terminal Data
ATC : Application Transaction Counter
HSM : Hardware Security Module
NSP : Network Supervisor
PSTM : Pos Standard International Message
PAN : Primary Account Number
POS : Point Of Sale
IAD : Issuer Application Data
ICC : Integrated Circuit Card
LCOL : LWR Consec Limit
HPDH : Hypercom Device Handler
LWR : Log Writer
PRE-AUTH : Pre- authentication
ILF : Interchange Log File

www.cognizant.com
 8
BASE 24 Training Material

SAF : Store and Forward File

EMF : External Message File
IIP : Interchange Interface Process
NEG : Negative Card File
UAF : Usage Accumulation File
SPROUTE : SPAN Routing File
KEYA : Key Authorization File
KEYF : KeyF File
ECF : Extract Configuration File

www.cognizant.com
 9
BASE 24 Training Material

: ATM- BASE 24 :

BASE24-atm Processes

Along the transaction path, processing is carried out in stages by several BASE24-atm
processes, each of which has its own responsibilities. The BASE24-atm processes that
can be involved in transaction processing are listed below:
1) Device Handler processes
2) Authorization processes
3) Host Interface processes
4) Interchange Interface processes
5) BIC Interface processes

TLF PBF

0200
0200 15
0200 0200
STM
NMM 4 STM 7
NMM ISO ISO
1 2 D 10 11
ATM stn AUTH HISO stn HOST
18
17 H 16 13 12
NMM NMM 0210 0210 0210
14
0210
STM 6 ISO ISO
5 STM
9
3 IDF 8

ATD CPF HCF EMF

CAF PBF

BASE 24 ATM

 There are mainly three types of ATM: NCR, Diebold, and Wincor.

 The entire Base 24 is controlled by a single XPNET. Here in the above figure
XPNET is not mentioned, but it is omnipresent in the base 24 application.

www.cognizant.com
 10
BASE 24 Training Material

 1 2: Now, first ATM generates a request message in the NMM format, and
through a station it goes inside the base 24.

 At the very beginning the device handler changes the native code to base 24
understandable standard internal messages, STM.

 2  3: Then it sends the message to ATD or ATM Terminal Data.

 When a Device Handler process receives a message from an ATM, it verifies

that it is supposed to receive messages from that particular ATM. It does this
based on the value in the DH PROCESS NAME field on screen 1 of the
BASE24-atm Terminal Data files (ATD) record for that ATM. If its name is
not in the DH PROCESS NAME field, the Device Handler process logs an
event message indicating the situation and drops the incoming message.

 ATD also controls the ATM screen display.

 3  4: After checking with ATD, the message enters the AUTH process as
0200 STM.

 4  5: Within AUTH the message goes to CPF or the Card Prefix File. The
Card Prefix File (CPF) defines each card prefix that can be processed within a
BASE24 logical network. One record must exist in the CPF for each card
prefix to be processed. If one prefix is used with primary account number
(PAN) lengths, multiple records must exist in the CPF—one for each PAN
length.

 If within the CPF the prefix doesn’t match with the existing prefix, then the
message is routed to some other routing methods to channel it towards proper
direction.

 In CPF the message is searched with respect to a primary key which is made
of the Prefix. With the help of that prefix it then searches for the FIID
[Financial Institution ID].

 Then it checks the IDF.

 5  6: The Institution Definition File (IDF) contains one record for each
institution participating in the logical network and defines processing for each
institution. The IDF contains routing tables for transaction routing within a
BASE24 product and each institution’s parameters for cards, dates, processing
control, and sharing. The key to records in the IDF is the FIID for the

www.cognizant.com
 11
BASE 24 Training Material

financial institution. For the help the FIID, it gets the DPC number HISO
process where it is to be destined.

 After IDF check, the CAF [Card Authorization File] and the PBF [Positive
Balance File] is also checked (only for offline transaction).

 The CAF checks for the Expiry date and the card limit.

 The PBF checks for the Offline approval.

 6  7: From AUTH the message goes to HISO.

 7  8 & 8 9: In HISO it goes to HCF [Host Configuration File] and EMF
[External Message File].

 HCF checks the information of the host.

 EMF checks the bit set.

 9  10 & 10 11: Then to that particular host the message is routed and
when it goes out HISO converts the Internal Standard Message to ISO
Standard message which is acceptable for that particular host.

 12  15: The Host receives the ISO message and sends a response via the
vice-versa route.

 15  16: After reaching the AUTH while returning the response, the message
updates the TLF [Transaction Log File] and in turn updates the PBF too.

 16  18: Finally via DH and station the card-holder at the ATM side gets the
response about the transaction.

 NOTES: Generally, the screen formatting files are: EMT (for NCR) and
ANTIBOLD (for Diebold).

www.cognizant.com
 12
BASE 24 Training Material

Day: 3 Date: 23.11.2007

: POS – BASE 24 :
EMBED PowerPoint.Slide.8

HPDH 0200
0200
PSTM
0200
ISO
NMM NMM PSTM

POS stn RTAU HISO stn HOST

0210
0210
NMM NMM 0210 ISO
AUTH PSTM
PSTM

PTD PTLF HCF EMF

BICI

CPF IIP ICF

CAF
ICF ILF
IDF
PBF
VISA/MC

o For POS transaction flows goes almost same as ATM except the following
exceptions.

o For POS the HPDH (i.e., the device handler) and the AUTH nodules reside
together as a single unit.

o ATD file for ATM is PTD [POS Transaction Data] for POS.

o TLF file for ATM is PTLF [POS Transaction Log File] for POS.

o The Request that comes to the DH is changed into PSTM or POS Standard
Internal Message format and its processing goes on.

www.cognizant.com
 13
BASE 24 Training Material

o If after searching the CPF, it is found that the request doesn’t belong to
particular acquirer, then the RTAU or the router directs it to either BICI or
IIP.

o If the transaction is made within the network where the acquirer and the issuer
both reside, then BICI do the needed routing and updates the ICF [Interchange
Configuration File].

o If the acquirer and issuer networks are not same, then the IIP [Interchange
Interface Process] does the routing and updates the ICF as well as the ILF
[Interchange Log File].

www.cognizant.com
 14
BASE 24 Training Material

ATM-Detailed Transaction
EMBED Visio.Drawing.11
Station
name as
Derived
from
ICF

Reads SPROUTE file if the

prefix is not found in the
CPF file.SPROUTE has data
From 2 files
SPREFIX and PREMAP.
Interchange
From PREMAP it gets the
Interface
Process name. With process
Flow
Name it finds the station
Name in ICF file

MSG TYPE 0200 Station

name as
Derived
from
ICF

Host
X X Interface
NCR/
Device P P - Following Bank
DIEBOLD
Handler N Authorization N ISO Host
( DH ) E Process E Standard
ATM
T T ( HISO )

Station
name as
Derived
MSG TYPE 0210 from
HCF

Writes into
TLF on its
Return path Reads HCF with DPC Station
and process name and
name as
Finds out the station name
Reads ATD for Derived
(to which the bank host is
Terminal ID and from
Connected via TCP/IP)
Glossary the type of type of ICF
ATM
ATD = ATM Terminal
data
CPF = Card Prefix
Reads CPF,1st 6 digits
File
(prefix) + next 4 digits
STM = Standard
(branch id) is used to BICI
Internal Message
Locate the FID
SEM = Standard
External Message
TLF = Transaction
BICI
Log file
(Used for clearing etc.)
CAF = Card Account
File
IDF = Institution
Definition File
FID = Financial
Institution ID
PBF = Positive
Balance File FID is used to find out CAF is read to find out PBF is read to ascertain
DPC = Data DPC number and the Vital information about The balance data. In the
Processing Center Process name from expiry and card limit return path,this file
HCF = Host IDF etc. Is also updated
Configuration File
ICF = Interchange
Configuration file
BICI = Base24
Interchange Interface

www.cognizant.com
 15
BASE 24 Training Material

POS- Detailed Transaction

EMBED Visio.Drawing.11
Station
name as
derived
from
ICF
Reads SPROUTE file if the
prefix is not found in the
CPF file.SPROUTE has data
From 2 files
SPREFIX and PREMAP.
From PREMAP it gets the
Process name. With process
Name it finds the station Interchange
Name in ICF file Interface
Process

Station
M M name as
E E derived
from
E S ICF
S S
A A
G G
E E
X
I Hypercon P Host
I
N Device Interface N
POS Handler
N - Following
Bank
Host
P (HPDH) E Standards S
(HISO)
O T E
S M

F F Station
O O name as
R R derived
from
M M HCF
A A
Glossary T T

CPF = Card Prefix

File
STM = Standard HPDH
Internal Message Reads HCF with DPC
SEM = Standard and process name and
Auth
Finds out the station name
External Message (to which the bank host is Station
DPC = Data Connected via TCP/IP) name as
Processing Center derived
HCF = Host from
ICF
Configuration File
ICF = Interchange
Configuration File
RTAU
RTAU = Route
Authorization BICI
BICI = Base24
Interchange BICI
Interface

Interchange
Interface
Process

www.cognizant.com
 16
BASE 24 Training Material

Day: 4 Date: 26.11.2007

: BASE 24 SUB-VOLUMES (NAMING CONVENTION) :

Consider the following convention:

Here we use the above naming convention for the sub-volumes.

The first two digits signify the module name. Module name can be of the following types:
BA - Base
AT - ATM
PS - POS
SW - Switch
FH - FHM

The third and fourth digits signify the version name. e.g.,
60 - Version 6.0
53 - Version 5.3
61 - Version 6.1

The last four digits basically denote the file type of that particular sub-volume. But there
may be a case where only last three letters are used or last four letters are used as follows:
HISO - For HISO files
AUTH - For AUTH files
SRC - For Source Files
DDL - DDLs
AFT - Requester/ server
UTIL - Utilities
OBJ - Objects
LIB - Libraries
RTAU - Router
N50 - For NCR Device Handler

www.cognizant.com
 17
BASE 24 Training Material

1000 - For Diebold Device Handler

Within the sub-volume there reside many files. They also follow a typical naming
convention.

Especially the last letter or group of the very last three or four letters signify the file type
as follows:
S - Source File
G - Global Variables
LIB - Library file (of that module)
M - Macro File (stores the abbreviations)
MM - Details of the abbreviations.
COB - For COBOL reference
TAL - For TAL reference
FUP - To create a file

For Interchanges we can also use the following convention:

VISA - For Visa network
MDS - For Master Card Network
BICI - For Base 24 Switch
EMV - Europay, Master Card, Visa

www.cognizant.com
 18
BASE 24 Training Material

Day: 5 Date: 27.11.2007

: COMPILER PROCEDURES :

Files needed for Compilation:

-ALLMACS
-CUSTMACS
-…………M
-……….MM

-ALLMACS
It consists of compilers and compiler paths (i.e., system related compile paths)

-CUSTMACS
=> CUSTMACS calls ALLMACS.
=> All product information is available.
=> Also base file information is available.

-……..M
We use the vanilla code for the M files.

-…....MM
=> If some modification has been made to any code the in the MM files the new paths
are included.
=> While compiling the CUSTMACS file takes out the details from the MM file.

www.cognizant.com
 19
BASE 24 Training Material

Day: 6 Date: 28.11.2007

: MESSAGE TYPES :

Use of Message types:

- Each message structure is accompanied with one message type.
- Each message type is of 4 bytes.
- Every case there is one message type for request and corresponding
one message type for response.

Different Message Types:

 Financial Transaction :-
- 0200 : Request
- 0210 : Response

 Reversal :-
- 0420 : Request
- 0421 : Repeat reversal
- 0430 : Response

 Handshaking or log on request / response:-

- 0800 : Request
- 0810 : Response

 SAF advice Message :-

- 0220 : From issuer (request)
- 0221 : Reversal request
- 0230 : From Acquirer

 0205 : Mini statement Request

 0215 : Mini statement Response

 9901 : Surcharge (i.e., if it is a not-on-us transaction, then debit the amount

from the owner’s account)

 9906 : For multiple account selection

 5400 : Adjustment request
 0500: Batch / shift / day close request

www.cognizant.com
 20
BASE 24 Training Material

Day: 7 Date: 29.11.2007

: REQUEST PATH FOR ATM DEVICE HANDLER (C1000) :

 Dry Run
 Find the process
 Set Break points there
C1000S^60^21
15 1

14 DD_Procs_Input_Msg
2
Ddh-write-atd 13
3
Ddb_Procs_atm_input

12
4 Ddaa_Read_ATD

Ddba_Procs_Customer_Request 5

6
Ddbai_Set_op_code_flgs

7
Ddbaa_Initialize_Auth_Msg
Ddbab_Procs_track2_data 6.1
8

Ddbac_Procs_track3_data AU_Initialize_Auth_Msg
9

10 Ddbad_procs_operation_keys

11 Ddbac_procs_amount

Ddbah_send_auth_request_msg
11.1
Ddbahc_compute_tran_allowed

www.cognizant.com
 21
BASE 24 Training Material

: RESPONSE PATH FOR ATM DEVICE HANDLER (C1000) :

C1000S^60^21
1

Dd_procs_input_msg
5
Ddh_write_atd
4 2

Ddc_send_atm_resp_msg

3
3

Ddca_format_multi_acct_scn
Ddcc_format_atm_resp_msg

3.1 3.1

Ddcf_send_appl_msg_to_atm

www.cognizant.com
 22
BASE 24 Training Material

: REQUEST PATH FOR ATM DEVICE HANDLER (N50) :

N50S^60^20
1
15

Dd_input_msg
14 2

13
Ddb_atm_input
3

12 4
Ddh_ATD_write Ddaa_ATD_Read
Ddba_customer_request
5
6

Ddbad_operation_keys
7 Dh_auth_msg_init
Ddbad_track2_data 5.1
8

Au_initialize_auth_msg
Ddbac_track3_data
9

10 Ddbae_amount 10.1 Ddban_descr_tkn_add

Ddbah_send_auth_request_msg
11
10.2 Ddda_stm_tkn_data_save
Ddbak_TLF_tkn_add

www.cognizant.com
 23
BASE 24 Training Material

: RESPONSE PATH FOR ATM DEVICE HANDLER (N50) :

N50S^60^20
7 1
2
Ddh_atd_write Dd_input_msg Dd_auth_resp
6
2.1
5 3

Ddaa_atd_read
2.2
Ddc_send_atm_resp_msg
Dda_stm_tkn_data_save
4
4.1
4
Ddcd_format_balance_scn
Ddca_format_mult_acct_scn
Ddcc_format_atm_resp_msg
4.1
4.2
4.2

Ddcaa_format_mult_acct_scn
Ddccd_format_customer_receipt

4.3 Ddcf_send_appl_msg_to_atm

Ddcf_send_appl_msg_to_atm

www.cognizant.com
 24
BASE 24 Training Material

Day: 8 Date: 03.12.2007

: REQUEST PATH FOR AUTH :

AUTH^60^17
1

AUTH^JRNL^MSG^ROUTER
2 2 2
2

Handle^Request Handle^Resp Handle^Rvsl Handle^…..

3
3 3
3

B10^AUTH^MGR
4
4 4
4
AUTH^L3 AUTH^L3 AUTH^L3 AUTH^L3
5
5 5

5
R500^RQST^T3L3 R560^RESP^T3L3 R580^RVSL^T3L3

6 6

R520^CAF^AUTH^T3L3 R540^RQST^FAIL^T3L3
R570^CAF^PBF^T3L3

www.cognizant.com
 25
BASE 24 Training Material

Day: 9 Date: 04.12.2007

: REQUEST PATH FOR HISO :

1
Bahiso^60^65
14 2
Util^station^index
Base^^Input^from^process
3
13
4
ATM^^Input^from^process
7 6

STM^0200^Request STM^frmt^B24^to^ATM^Sem
5
9 11 5

ATM^Util^send^Sem Util^station^avail Util^frmt^inst^id

10

Util^send^sem 9 11

10
12 STM^0200^Route

ATM^Util^send^STM
7
8
STM^0220^Completion
9

10 Util^saf^add STM^frmt^b24^to^atm^0220

Util^send^sem

: FEW FILE DETAILS :

DBOLD:
 C1000S
 C1000G
 C100NAMS
 RCPTDEFS

NCR:
 N50S
 N50G
 N50NAMS
 RCPTDEFS

www.cognizant.com
 26
BASE 24 Training Material

AUTH:
 AUTHS
 AUTHG
 AUTHLIBS
 AUTHTBL

HISO:
 BAHISOS
 BAHISOG
 ATHISOS
 ATHISOG

DDL FILE:
 DDLACNST (ATM)
 DDLBCNST (BASE)
 DDLPCNST (POS)
 DDLATTKN (TOKEN FILE ATM)
 DDLBATKN ( ,, ,, BASE)
 DDLPSTKN ( ,, ,, POS)
 ATTKNID (TOKEN ID FILE ATM)
 BATKNID ( ,, ,, ,, BASE)
 PSTKNID ( ,, ,, ,, POS)

www.cognizant.com
 27
BASE 24 Training Material

Day: 10 Date: 06.12.2007

: DIFFERENT BASE 24 FILES:

Institution Definition File

IDF

o Authorization Routing Table

o Prescreening Checks
o Card Processing Parameters
o Processing Date Parameters

IDF Routing Table

ATM ROUTING TABLE

PRIMARY SYMBOLIC ACCT PRFX AUTH AUTH
DPC NAME TYPE RTG TYPE (DESCR) LVL (DESCR)
0001 P1A^HISF 11 2 0 (HOST) 1(ONLINE)
0002 P1A^HISF 31 3 2 (CAF) 3(ON/OFFL)
0003 P1A^HISF 01 1 3 (CAF/PBF) 3(ON/OFFL)
0001 P1A^HISF 11 A 3 (CAF/PBF) 3(ON/OFFL)
NO HOST ROUTING AL A 1 (NEG/UAF) 2(OFFLINE)

www.cognizant.com
 28
BASE 24 Training Material

AUTH :-> Institution Definition File (IDF): - The IDF contains one record for each
institution participating in the logical network. Each record establishes how processing is
handled for that institution and includes routing tables for transaction routing within
BASE24 products and parameters for cards, dates, processing control, and sharing.
The authorization level is specified in the AUTH LVL fields on IDF screen 9. The
possible authorization levels are online authorization (level 1), offline authorization (level
2), and online/offline authorization (level 3). [Include Screen 9 & Screen 2]
Contains authorization file names, card parameters, processing and withdrawal period
parameters, routing table, processing dates and sharing information.

Authorization Options
PBF
CAF CAF

UAF
NEG NEG

o Positive Authorization
o Positive Balance Authorization
o Negative Authorization
o Negative Authorization with Usage Accumulation

: AUTHORIZATION LEVELS :
Online Authorization

- Online authorization is also referred to as level 1 authorization.

- At this level, the host performs all transaction authorizations. If the host is offline
and, therefore, unable to authorize transactions, the Authorization process
declines all transaction requests.
- Typically, BASE24 does not maintain cardholder account files at this level of
authorization.
- Online authorization can be used only with the online host processing
authorization method.

www.cognizant.com
 29
BASE 24 Training Material

Offline Authorization

- Offline authorization is also referred to as level 2 authorizations.

- At this authorizations are performed by BASE24; no authorization requests are to
the host.
- With the offline authorization level, BASE24 must maintain cardholder in its
database. These account files, as well as transaction log files, are periodically
extracted to tape or disk and used to update host files.
- These are also refreshed periodically using information from host files.

Online/Offline Authorization

- Online/offline authorization is also referred to as level 3 authorizations.

- At this level, BASE24 optionally screens transactions based on prescreening
settings in the IDF and forwards those transactions that pass the screening checks
to the host for final approval.
- The Authorization process declines transactions that do not pass the screening
checks.
- The Authorization process also stands in for the host and authorizes transactions
when communications to the host are down.
- The transactions BASE24 authorizes are then stored and forwarded to the host
when communications with the host are restored.
- With the online/offline authorization level, BASE24 must maintain cardholder
account files in its database. These account files, as well as transaction log files,
are periodically extracted to tape or disk and used to update host files.
- These accounts are also refreshed periodically using information from host files.

www.cognizant.com
 30
BASE 24 Training Material

Card Prefix File

CPF

o Card Track Information

o Prefix Routing Code
o Activity Limits
o PIN and Card Verification
Parameters

AUTH :-> Card Prefix File (CPF)[Card and Cardholder Limits]: -> The CPF
contains one record for each card prefix used in a BASE24 logical network. CPF records
define the characteristics of each prefix and contain prefix-specific parameters that can be
used to control aspects of authorization processing at the prefix level. The CPF also
allows institutions to establish authorization parameters for selected prefix groups.

The Card Prefix File (CPF) defines each card prefix that can be processed within the
BASE24 logical network. One record exists in the CPF for each card prefix to be
processed. Each CPF record contains processing parameters and authorization limits for
that specific card prefix. [Deposit Credit Limits]

Contains Track I and II information, processing information, withdrawal limits, PIN

information and deposit credit limits.

www.cognizant.com
 31
BASE 24 Training Material

Cardholder Authorization File

CAF

o Card Type and Card Status

o PIN Offset/PVV
o Card Usage Control
o Activity This Period
o Associated Application Accounts

AUTH-> Cardholder Authorization File (CAF): - The Cardholder Authorization File

(CAF) contains one record for each cardholder whose card-issuing institution uses the
Positive Authorization method or Positive Balance Authorization method. Each CAF
record contains authorization parameters and usage accumulation information for a
specific cardholder. The Positive Authorization method uses the Cardholder
Authorization File (CAF). The Authorization process authorizes transactions using
positive identification.
Contains card usage controls, withdrawal limits, and deposit credit limits, accounts
associated with the cardholder and card usage accumulation.

www.cognizant.com
 32
BASE 24 Training Material

Positive Balance File

PBF

o Account Type and Account Status

o Ledger Balance/Credit Limit
o Available Balance/Available Credit
o Amount on Hold/Credit Balance
o Overdraft Limit
o Last Deposit and Withdrawal Dates and Amounts

AUTH: -> Positive Balance File (PBF): - The PBF contains one record for each
application account whose issuer uses the Positive Balance Authorization method,
Parametric Authorization method, or Positive Customer with Balances/History
Authorization method. Each PBF record contains available and ledger balances for the
account. The PBF is used to authorize transaction requests without having to forward
them to a back-end host authorization system. Institutions can maintain up to three
different PBFs: one for checking accounts (DDAs), one for savings (SAV) accounts, and
one for credit (CCD) accounts.

The Positive Balance Authorization method uses the Cardholder Authorization File
(CAF) and the Positive Balance File (PBF).

Institutions can establish an overdraft limit for a particular account using the
OVERDRAFT LIMT field on screen 1 of the PBF. This amount is added to the amount
in the AVAILABLE BALANCE/AVAILABLE CREDIT field in the PBF to obtain the
maximum transaction amount available to an accountholder. This field makes it possible
for an accountholder to perform transactions even when the transaction amount exceeds
the balance in the AVAILABLE BALANCE/AVAILABLE CREDIT field.
Contains available and ledger balances, overdraft limits and amounts on hold.

www.cognizant.com
 33
BASE 24 Training Material

Negative Card File

NEG

o Card Type and Capture Code

o Reason on File
o Restriction Expiration File
o Date Added to File

AUTH: -> Negative Card File (NEG): - The NEG contains one record for each special-
status card whose card issuer uses a negative authorization method. The NEG is used to
flag cards that require special processing, such as restricted cards (lost or stolen), VIP
cards, administrative cards, and deposit-only cards. The Authorization process checks
this file to determine whether a transaction request should be approved and, if not, what
action should be taken with the card.

The Authorization process authorizes transactions using negative identification. If a

record is found in the NEG, the Authorization process takes the action specified in the
record. The Negative Authorization without Usage Accumulation method uses the
Negative Card File (NEG). If a record is found in the NEG, the Authorization process
takes the action specified in the NEG record. [Include Screen 1]
Contains card type, capture code, and reason for restriction.

www.cognizant.com
 34
BASE 24 Training Material

Usage Accumulation File

UAF

o Number of Times Used

o Activity for Current Period
o Bad PIN Attempts

AUTH: -> Usage Accumulation File (UAF): - The UAF, which is used for usage
accumulation with the Negative Authorization with Usage Accumulation method,
contains one record for each cardholder who has had a transaction authorized by the
BASE24-atm or BASE24-pos products during the current usage accumulation period.
Cardholder usage is tracked, or accumulated, based on the institution’s business day,
which is the time period from one usage period to the next. UAF records contain such
information as withdrawal amounts and bad PIN tries. This information enables BASE24
products to determine when a cardholder has reached the institution’s usage limits for a
given period.

www.cognizant.com
 35
BASE 24 Training Material

SPAN Routing File

SPROUTE

o All Network Prefixes

o External Prefixes for Interchanges
o Algorithm Routing Information
o Alternate Routing Information

SPROUTE File: -The SPROUTE File contains all of the information needed and
available to determine proper destinations for transactions with prefixes that are not
recognized y an Authorization process.

www.cognizant.com
 36
BASE 24 Training Material

Key Authorization File

KEYA

o Clear/Encrypted Keys
o PIN Verification Tables
o Record Type
o Begin/End Dates
o Decimalization Table

AUTH :-> Key Authorization File (KEYA): - The KEYA contains one record for each
financial institution or data processing center (DPC) associated with a BASE24
transaction processing system. KEYA records contain specific key processing
information for each of these entities, including parameters for the PIN verification that
BASE24 authorization processes must perform.
PIN verification controlled at the institution level requires a record in the Key
Authorization File (KEYA) for each institution performing PIN verification. PIN
verification controlled at the card prefix level requires a record in the KEYA that
corresponds with the KEYA group identified in the PIN VERIFICATION KEYA
GROUP field in the CPF. PIN verification information is maintained on screens 2
through 5 of the KEYA in addition to the IDF, CPF, and TDF screens mentioned earlier.

www.cognizant.com
 37
BASE 24 Training Material

Transaction Log File

TLF

o Audit Trail
o Online Perusal
o Used by BASE24 Reporting
o Extract for Host Batch Processing
o Retention Period

AUTH: ->Transaction Log File (TLF): - The TLF contains one record for each
transaction occurring at an ATM in the logical network and each transaction processed by
the BASE24 transaction processing system during a business day. TLF records are
maintained for both cardholder transactions and terminal balancing transactions. One
TLF is maintained for each business day, and each TLF can be saved for the number of
days specified in the Logical Network Configuration File (LCONF). The TLF provides
an audit trail of ATM activity.
The BASE24-atm Authorization process logs all of the transactions it processes to the
Transaction Log File (TLF).
Contains TLF records for every cardholder transaction and for every terminal balancing
transaction.

www.cognizant.com
 38
BASE 24 Training Material

Host Configuration File

HCF

o Timer Limits
o Store-and-Forward Method
o DPC Type
o Message Format
o Protocol Type
o Station Table

HISO:- >Host Configuration File (HCF): - The HCF contains one record for each
unique data processing center (DPC) and Host Interface process pair in the logical
network. Each record contains pertinent information about host message formats, timer
limits, and request/response sequences. The HCF is used to establish BASE24-to-host
communication links for transaction message traffic routed to a host authorization
system.
It does this based on an internal table of stations that it builds at initialization from the
STATION fields on screen 2 of its records in the Host Configuration File (HCF). There
various timers are set in the Host Configuration File (HCF).
Contains timer limits, processing flags and stations.

www.cognizant.com
 39
BASE 24 Training Material

External Message File

EMF

o Message Type
o Inbound-Outbound
Indicator
o Token Group
o Message Elements
o MACing Elements

HISO:->External Message File (EMF): - The EMF can contain up to one record for
each BASE24 external message type available to each data processing center (DPC),
BASE24 process, and BASE24 product combination.
The BASE24 process can be an ISO Host Interface, BIC ISO Interchange Interface, and
From Host Maintenance, BASE24 Remote Banking Standard Interface, or BASE24-pos
NCR NDP Device Handler process. EMF records specify the data elements that should
be included in the BASE24 External Message. The EMF is used by the ISO Host
Interface process, BIC ISO Interchange Interface process, From Host Maintenance
process, BASE24 Remote Banking Standard Interface process, and BASE24-pos NCR
NDP Device Handler process to determine how to create the external messages they send
and interpret the external messages they receive.
Contains timer limits, processing flags and stations.

www.cognizant.com
 40
BASE 24 Training Material

Store and Forward File

SAF

o Temporary Storage of Messages

o Extractable

HISO:->Store and Forward File (SAF): - Contains approved transactions and reversals
when the host communications link to BASE24 is down.

www.cognizant.com
 41
BASE 24 Training Material

KeyF File

KEYF

o Host Encrypt Type

o BASE24 Encrypt Type
o Keys
o MAC Type

HISO :-> Key File (KEYF): - The KEYF contains one record for each Host Interface
process or Interchange Interface process associated with a BASE24 transaction
processing system. KEYF records contain specific key processing information for both of
these entities, including parameters for PIN encryption and decryption and key
management throughout the BASE24 transaction processing system.

www.cognizant.com
 42
BASE 24 Training Material

Interchange Configuration File

ICFE

o Settlement Information
o Supported Transactions
o Timer Limits
o Station Related information

Switch :-> Enhanced Interchange Configuration File (ICFE): - Like the Interchange
Configuration File (ICF), the ICFE is used by the institution to define institution and
terminal interchange sharing, holidays, transaction handling in offline and online
situations, and settlement handling. However, the ICFE uses transaction profiles instead
of the hard-coded tables used in the ICF to define the transactions allowed.
Contains Interchange characteristics, settlement information, timer options, processing
parameters, sharing information and Interchange specific information. The following
Interchange Interface processes support the ICFE:
Banknet PLUS ISO/PISI
BIC ISO VisaNet/VISI/VISP
MDS/MDSM

www.cognizant.com
 43
BASE 24 Training Material

Interchange Log File

ILF

o Reflects Interchange Settlement Day

o Used to Create Reports
o One ILF Per Interchange
o Extractable

Interchange Log Files (ILFs): - The Interchange Interface processes and BIC Interface
processes log all the transactions they process to the appropriate Interchange Log Files
(ILFs) Interchange Log Files (ILFs).

Contains Interchange characteristics, settlement information, timer options, processing

parameters, sharing information and Interchange specific information.

www.cognizant.com
 44
BASE 24 Training Material

On-Line Maintenance File

OMF

o Stores Activity History done thru

Pathway
o Keeps after & before image of changed
record
o Logs with UserID, Date & Time
o Extractable

On-Line Maintenance History File (OMF): -

Contains a record of all file maintenance activity performed to the database and logons
and logoffs.

www.cognizant.com
 45
BASE 24 Training Material

ATM Terminal Data

ATD
o Keep record for each Terminal
o Device Type Configuration
o Sharing Information
o ATM cash information
o Transaction totals
o Capture cards history
o Date Parameters
o Transaction & Receipt Profiling

DH-> BASE24-atm Terminal Data files (ATD): - The Terminal Data files define the
characteristics of the terminal, including the transaction security parameters, sharing
parameters, transaction totals, terminal owner, and device-dependent data. They are also
used to preserve transaction context. Data entered on ATD screens is stored in different
files, depending on the type of terminal being defined. For Diebold 10XX/478X and
NCR 5XXX terminals, dynamic and static data is stored in the ATM Terminal Data
Dynamic File— general data (ATDD1) and ATM Terminal Data Static File—general
data (ATDS1), respectively. For all other types of ATM terminals, data is stored in the
ATM Terminal Data File (TDF).
Contains the characteristics of the terminal, sharing information, hopper contents, activity
performed at the terminal and device specific information.
- ATDD1
- ATDD2
- ATDS1

www.cognizant.com
 46
BASE 24 Training Material

LNCF

LNCF

o Assigns & Parameters

o Mapping table for Files
logical name & disk location
o Mapping table for reports &
location on TANDEM
o Prams keeps values for
various parameters needed
by application

Logical Network Configuration File (LCONF or LNCF): - The LCONF is the central
location of file information and processing information. One LCONF exists for each
logical network. Records in the LCONF are classified as either assigns or params,
depending on their function. Assigns link the physical names of objects in the logical
network to names used in BASE24 code. Params set processing values at the logical
network level. The LNCF is used to modify assigns and params.

These various timers are set in the Logical Network Configuration File (LCONF). The
ATM-DH-STALE-RQSTTIMEOUT param in the LCONF specifies the number of
seconds an incoming transaction request can remain in the Device Handler process queue
before being discarded by the Device Handler process. This controls the number of
consecutive Message Authentication Code (MAC) errors that can occur before the
Device Handler process sends a shutdown message to the ATM.

www.cognizant.com
 47
BASE 24 Training Material

: SOME MORE FILES :

1. Administrative Card File (ADMN): -

The administrative card transaction profile defines the administrative transactions
supported at POS devices for an administrative card. The administrative card transaction
profile at this level overrides the default administrative card transaction profile defined at
the terminal owner level in the IDF.

2. AUTH-> Acquirer Processing Code File (APCF): -

The APCF defines the ISO processing codes allowed by various transaction acquirers.
The APCF contains one record for each combination of acquirer transaction profile,
message category, and ISO processing code that is supported by a BASE24-atm or
BASE24-pos acquirer endpoint in the system.
Each acquirer transaction profile defines a set of transactions supported for an acquiring
interchange, retailer, terminal owner, or terminal.

3. Account Routing File (ARF): -

The ARF provides routing information to supplement the account information entered at
a teller terminal or ATM so that the account can be located on the BASE24 database. The
ARF is used in interbank routing for the BASE24-teller product and in self-service
banking (SSB) for the BASE24-atm product.

4. AUTH->Account Type Table File (ATT): -

Contain current & saving a/c information
The ATT contains one record for each valid account type in the BASE24 network. Each
ATT record contains an ISO code and a corresponding description.

5. Bin Sort File (BSF): -

Accesses the Bin Sort File (BSF), which is used with the BASE24-atm self service (SSB)
banking product. The BSF defines the terminal check sorting mechanism based on the
check issuer and the check amount.

6. Corporate Check File (CCF): -

Accesses the Corporate Check File (CCF), which is used with the BASE24-atm self
service banking (SSB) product. The CCF defines check authorization parameters based
on the institution that owns the accounts.

7. Check Status File (CSF): -

Accesses the Check Status File (CSF), which is used with the BASE24-atm self service
banking (SSB) product. The CSF defines the current status of specific checking accounts
used in check-related transaction authorizations.

8. Derivation Key File (KEYD): -

www.cognizant.com
 48
BASE 24 Training Material

The Derivation Key File (KEYD) contains 32-byte derivation keys used by ACI Standard
POS terminals to derive a unique PIN encryption key for each transaction sent to the
BASE24 system. The BASE24-pos Standard POS Device Handler (SPDH) module uses
these keys to translate the derived unique key per transaction (DUKPT)-encrypted PIN
block received from the terminal into a single-length Master/Session key PIN block,
which the Router/Authorization module can verify normally.

The 32-byte derivation keys stored in the KEYD must be encrypted under a double-
length Master File Key (MFK) for Atalla security devices or a double length Local
Master Key (LMK) pair variant of 28–29 for Thales e-Security (Racal) security devices
before they are manually entered into the file.
The primary key to the KEYD is a combination of the RETAILER ID, KEYD GRP, and
TERMINAL ID fields.

9. Extract Configuration File (ECF): -

The ECF contains one record for each type of extract an institution wants to perform in a
particular logical network. ECF records are used to set extract processing parameters,
including the name of the file or files to be extracted and the tape or disk location to
which the extract is to be performed. ECF records can also specify that an extract is to be
performed automatically at a set time each day.

10. Exchange Rate File (ERF): -

The ERF is used with the BASE24 Multiple Currency add-on product. It contains one
record for each currency used by BASE24 except the Base currency. All exchange rates
in the ERF are used in the relationship of the Base currency to a specific currency rate.
Information in the ERF is used by the currency conversion utilities to convert amount
fields within BASE24 from one currency to another.

11. Issuer Processing Code File (IPCF): -

The IPCF contains one record for each combination of issuer transaction profile, message
category, and ISO processing code that is supported by a BASE24-atm or BASE24-pos
card issuer in the BASE24 system. Each issuer transaction profile defines a set of
cardholder transactions supported for an institution, card prefix, or individual cardholder
account. For interchanges, each BASE24-atm or BASE24-pos issuer transaction profile
defines a set of transactions allowed to be sent (outbound) to the issuer interchange.

12. ICC Key File (KEYI): -

This file is used with the BASE24 EMV add-on product. The file contains multiple
authentication keys used for Authorization Request Cryptogram (ARQC) verification and
Authorization Response Cryptogram (ARPC) generation. The file also contains a double
length DES key used for Secure Messaging for Message Integrity, (i.e., the generation of
the Issuer Script message authorization code (MAC)).
(Contain the information about smart card, visa card, European card, master card)

www.cognizant.com
 49
BASE 24 Training Material

13. KEY 6 FILE (KEY6): -

The Key 6 File (KEY6) contains the information and parameters required by release 6.0
BASE24 Host Interface and Interchange Interface processes running in release 5.x or 6.0
networks for PIN encryption, PIN translation, message authentication, and dynamic key
management. The KEY6 allows for double length encryption keys, which are required
when translating PINs from encryption under a double length key using the Triple Data
Encryption algorithm (3DEA) to encryption under a single length key using the Data
Encryption algorithm (DEA) and vice versa.

The 32-byte double-length keys stored in the KEY6 must be encrypted under a double-
length Master File Key (MFK) for Atalla security devices or a double length Local
Master Key (LMK) pair variant of 28–29 for Thales e-Security (Racal) security devices
before they are manually entered into the file.
The ISO Host Interface process and Interchange Interface processes use the KEY6
instead of the KEYF when the LCONF param DES-TRIPLE-SINGLE param is set to a
value of Y. Otherwise, these processes use the KEYF.

The KEY6 contains one record for each data processing center (DPC) number and Host
Interface process combination defined in the Host Configuration File (HCF) and one
record for each Interchange FIID and Interchange Interface process combination defined
in the Interchange Configuration File (ICF) or Enhanced
Interchange Configuration File (ICFE), allowing for individual control of the above-
mentioned processing for each of these entities.

14. Network Control Supervisor Profile File (NCSP): -.

The NCSP allows you to set up network control command profile records. The command
profile records indicate whether each network command can be executed and whether the
command is audited when it is executed. After you have created a command profile and
stored it in the NCSP, you can associate it with the security record for one or more users.

15. Operator Identification File (OIF): -

The OIF contains one record for each operator that services Diebold 10XX/478X ATMs
with the optional host-controlled, solenoid-activated lock feature. OIF records specify
whether the operator has access to the ATM chest door.

16. Processing Code Description File (PDF): -

The PDF is an optional file that contains the descriptions of each processing code
description tag used in the Acquirer Processing Code File (APCF) or Issuer Processing
Code File (IPCF). Each description tag record in the PDF defines a long description and
an optional short description. These descriptions are displayed on various screens
whenever a record with the corresponding description tag is read.

www.cognizant.com
 50
BASE 24 Training Material

The primary key to the PDF is the DESCRIPTION TAG field.

17. Prefix File (PRE): -

Accesses the Prefix File Build Utility (PRE) screen. The PRE screen is used to create and
maintain Interchange Prefix Files (IPFs) when prefix tapes are not provided by an
interchange. The prefixes maintained in the IPF are used for routing with the logical
network (LGNT) routing method.
(Checks for prefix visa)

18. POS Retailer Definition File (PRDF): -

The acquirer transaction profile defines the BASE24-pos cardholder transaction
supported for an acquiring retailer. The acquirer transaction profile at this level overrides
the default BASE24-pos acquirer transaction profile defined at the terminal owner level
in the IDF. The retailer transaction profile defines the transactions for which the retailer
is required to use an administrative card. The retailer transaction profile at this level
overrides the default retailer transaction profile defined at the terminal owner level in the
IDF.

19. BASE24-pos Terminal Data files (PTD): -

The acquirer transaction profile defines the BASE24-pos cardholder transactions
supported for an acquiring POS device. The acquirer transaction profile at this level
overrides the BASE24-pos acquirer transaction profile defined at the retailer level in the
PRDF.

20. DH: -> Receipt File (RCPT): -

The Receipt File (RCPT) is used to support the configurable receipt option, which
provides you with the ability to establish ATM receipt formats that are unique to the
institution. In addition, this customization option supports the display of an informational
or marketing message on the cardholder receipt, the use of flexible monetary symbols,
and multiple languages. The configurable receipt option includes approved and denied
financial transaction receipts as well as administrative receipts.
Receipt configuration is supported by device type, receipt group, transaction type,
language code, card issuer FIID, from and to account type, and printer type. Receipt
groups allow the use of a single receipt format for a group of ATMs rather than
configuring receipts for an individual terminal.

The Receipt File (RCPT) is the primary file used to configure receipts. It contains receipt
templates that define the actual text and format to use for the various types of receipts.

The Device Handler process retrieves receipt templates in the RCPT from the RCPT
extended memory table and then uses that information for creating receipts. Initially, the
RCPT contains default templates for each of the receipt types. You can use these default

www.cognizant.com
 51
BASE 24 Training Material

templates as they are, or you can modify the templates to print the information you want
on the receipt.

Note: Every time the RCPT is modified, the RCPT extended memory table file must be
rebuilt using the Base Extended Memory Table Build utility. After the RCPT extended
memory table file is rebuilt, the Device Handler process must reallocate the table. You
can reallocate the RCPT extended memory table by using the ALTERATTRIBUTE
command from the EMT Control Command screen (screen 5) in the Device Control
Terminal (DCT). You can also enter the ALTERATTRIBUTE command manually from
a network control facility to warmboot an extended memory table for an individual
process.

Note that when you enter the command from the DCT, all processes that use the RCPT
extended memory table are warmbooted. If you use the network control facility to issue
the command, you can specify a specific process for the RCPT extended memory table.

The RCPT contains configuration information for ATM receipt formats that are unique to
an institution. One RCPT screen is used to configure one receipt template for each receipt
type and language indicator.

21. DH->ATM Report (RPT): -

Accesses the ATM Report (RPT) screens. The RPT screens are used to peruse BASE24
settlement and statistical reports, which contain information from the Transaction Log
File (TLF) for each terminal and institution in the logical network.

Used to peruse the BASE24 settlement and statistical reports. These reports contain
information from the TLF for each terminal and institution in the Logical Network

22. Security File (SEC) [CRT User Security File]: -

Accesses the four screens used to maintain BASE24 security. These screens allow you to
change security records in the Security File (SEC), User/FIID Relation File (UFIR),
User/Product File Relation File (UPFR), and Network Control Security Specification File
(NCSS). The SEC, UFIR, UPFR, and NCSS contain one record for each authorized
BASE24 user. Security records restrict BASE24 CRT access by user name, time of day,
terminal, XPNET node, financial institution identifier, region, branch, and screen. Screen
use is further restricted to read, add, delete, or update privileges or a combination of
these. In addition, security records restrict access to text commands initiated via any
network control facility. See section 5 of this manual for more information on BASE24
security.
Contains user access to financial institutions, regions, branches, XPNET Nodes,
terminals, file screens, and time of day access.

23. Stop Payment File (SPF): -

www.cognizant.com
 52
BASE 24 Training Material

The SPF contains one record for each institution- or customer-initiated stop payment
request that has been issued in the logical network. SPF records are used to stop payment
of bad checks, which is a feature of the BASE24-atm self-service banking (SSB) add-on
product and the BASE24-teller product.

24. Switch: -> Switch Terminal File (STF): -

The STF contains one record for each terminal that is required by any interchange to
transmit an interchange assigned identification rather than the BASE24 terminal
identification. One screen is used to access records in the STF.

25. Surcharge File (SURF): -

The SURF contains information about whether transactions are charged an additional
surcharge fee for the use of your terminal. The SURF determines when and how much
the surcharge is applied to a transaction. Surcharges can either be calculated as a flat
amount per transaction or a percentage of the transaction amount requested.

26. Token File (TKN): -

The TKN contains records that indicate which of the data tokens carried in the internal
messages will be logged to the various log files, extracted by the Super Extract process,
or sent in external messages created by the ISO Host Interface and BASE24 Interchange
(BIC) Interface processes. The information in the TKN also determines the order of data
tokens being logged, extracted, or sent.

The Token File (TKN) controls which tokens in the internal message are logged to the
TLF or ILF. BASE24-atm processes use the Token File (TKN) to determine which
tokens are logged, extracted, or sent by way of the ISO Host Interface and ISO BASE24
Interchange (BIC) Interface processes to other entities.

27. Transaction Code File (TCF): -

The TCF contains the text description of each ISO transaction code used in the Acquirer
Processing Code File (APCF), Issuer Processing Code File (IPCF), or Terminal Receipt
File (TRF).
Each transaction code record in the TCF defines a text description for the two character
transaction code. This description is displayed on the APCF, IPCF, and TRF screens
whenever a record with the corresponding transaction code is read or verified.
The primary key to the TCF is the TRANSACTION CODE field.

28. DH: -> Terminal Receipt File (TRF): -

The Terminal Receipt File (TRF) contains receipt print options for approved and denied
transactions. The TRF contains one record for each terminal receipt profile, message
category (the second digit of the message type), and ISO processing code. The terminal
receipt profile defines the receipt requirements for various transaction types and in
defined in the BASE24-atm Terminal Data files (ATD).

www.cognizant.com
 53
BASE 24 Training Material

The TRF defines the receipt options for approved and denied transactions that occur at
devices with the specified terminal receipt profile defined in the BASE24-atm Terminal
Data File (ATD). The TRF contains one record for each terminal receipt profile, message
category, and processing code combination in the system.

29. Terminal Data File (TDF): -

Updating the accumulator fields and status flags in the Terminal Data File (TDF) record
for each ATM.
One record for every terminal managed by the 6.0 Compatible Device Handlers in the
Logical Network. Contains the characteristics of the terminal, sharing information,
hopper contents, activity performed at the terminal, transactions allowed by foreign
cardholders at the ATM, receipt print configuration, and device specific information.

30. Template Files: -

A number of files are created routinely by a BASE24 system. For example, some files,
such as the Online Maintenance File (OMF), transaction log files, and the Report File
(RPT), are created daily by a BASE24 system. Other files, such as the Positive Balance
File (PBF), the Cardholder Authorization File (CAF), and the Negative Card File (NEG),
must be recreated during full-file refreshes.

A BASE24 system uses template files to create and recreate files. Template files contain
no records; they are used simply to determine attributes for each of the files that must be
created. Template files must reside on the same volume as the files created from them.
The recommended name of the subvolume in which template files reside is xxxxTPLT
(where xxxx indicates the name of the logical network).

www.cognizant.com
 54
BASE 24 Training Material

: REFRESH PROCESS :

Refresh Operator Procedures

o Initiate Refresh from NCS or

NCPCOM

o Initiate Refresh from REFR

Screen

Refresh Processing

Disk Refresh
Refresh
File
Host Refresh
Tape

Customer
File

Customer
File

Authorization
Authorization

www.cognizant.com
 55
BASE 24 Training Material

: EXTRACT PROCESS :

Extract Configuration File

ECF

o Extracts on Tape or Tandem

Disk
o Based on Timers or Manually
o Files Selection

Log Files Extract Processing

Yesterday’
Yesterday’s
TLF Extract
Extract

Disk
Extract
File
Extract
Tape
Tape
Host

www.cognizant.com
 56
BASE 24 Training Material

: INTERCHANGE INTERFACE PROCESS [IIP]:

Suppose, the card holder is making a not-on-us transaction. Here the card used at an
ATM is issued by a different institution from that which owns the ATM.

When the request is received at the Base 24 application, the DH after transforming the
NMM to STM, sends the request to the AUTH.

In the AUTH, the CPF or the Card Prefix File checks for the prefix, to find out the FIID.
Now here in the not-on-us transaction, in the CPF if it is found that the transaction
doesn’t belong to that particular acquirer, i.e. the prefix doesn’t match, and then it sends
the request to the Interchange process.

In the interchange process, the process chooses the routing method with the help of the
SPROUTE table (file).

The SPROUTE table consists of two files: 1. SPREFIX and 2. PREMAP. With the help
of PREGEN utility this files are accessed.

SPREFIX will contain all the CPF information of that logical network.
PREMAP contains the logic of routing.

Then it checks the Interchange Configuration File ICF and gets the station name where
the request is to be routed. ICF uses the FIID and the routed process name as the primary
key and yields the station name where the request ought to be destined.

Then the interchange process routes the request to that particular station, then station
directs it to the particular process i.e. VISA/MC/AMEX etc. And again, via that network
the request goes to the issuer network and starts interacting from the AUTH onwards.

www.cognizant.com
 57
BASE 24 Training Material

AUTH

CPF

IIP STN
SPROUTE

SPREFIX PREMAP

ICF
VISA/MC

INTERCHANGE PROCESS

www.cognizant.com
 58
BASE 24 Training Material

: NOTES :

www.cognizant.com