Transaction Key Fields

Transaction Key fields are used to reduce data collection processing overheads. In most cases Transaction Manager Collectors will gather data for all fields contained in each record which can lead to high processing costs per record instance. The Transaction Summary records are known as 'Associate Records' and permit the Collectors to gather only the data specified by the nominated Transaction Key fields, thereby reducing the volume of data collection.

Transaction Key fields are defined in the Transaction Manager Configurations (BASE24, B24EPS, CONNEX, IST and POSTILION) and can be used alone or in groups. When combined in groups the Transaction Key fields refine the gathered data providing for effective data analysis.

For example:

To see BIN (Bank Institution Number) usage, set up the configuration file with the 'BIN' Keyword

To see POS Retail usage, set up the configuration file with the Transaction Key combination, RETLFIID+RETLGRP+RETLREGN+RETLID

To see the total of each type of reversal code per ATM by configuring the Transaction Key combination 'ATMID+RVSLCODE' BASE24 BASE24-EPS
To see the total of each type of reversal code per terminal use the Transaction Key combination 'TERMID+MSGRSN' CONNEX POSTILION
To see the total of each type of reversal code per terminal use the Transaction Key combination 'TERMID+REVCODE' IST

Transaction Key combinations can also be used to detect problems. For example,

BASE24 BASE24-EPS

Some cards are always being declined. In order to see which card issuers are having problems, use the Transaction Key combination 'INTERCHG+RESPCODE'. This enables the response codes being received per card issuer to be seen
The problem has been discovered, but it is necessary to know if it affects cards for that ISSUER, or only a particular BIN. Use the Transaction Key combination 'INTERCHG+BIN+RESPCODE' which will isolate the response codes per BIN for a particular issuer

CONNEX POSTILION IST

Some cards are always being declined. In order to see which card issuers are having problems, use the Transaction Key combination 'ISSRINST+RESPCODE'. This enables the response codes being received per card issuer to be seen
The problem has been discovered, but it is necessary to know if it affects cards for that ISSUER, or only a particular BIN. Use the Transaction Key combination 'ISSRINST+BIN+RESPCODE' which will isolate the response codes per BIN for a particular issuer.

There are three types of Transaction Key fields:

Standard Transaction Keys

These are pre-defined Transaction Key fields that are applicable to all transaction environments. These are used to map data fields from the Transaction Summary records. Standard Key fields are added through the Transaction Manager Configuration (for the specific switch) by using the 'Enable Key' statement.

Custom Transaction Keys

These are pre-defined Transaction Key fields that are applicable to specific transaction environments and are used when there are fields in the transaction data files that cannot be successfully mapped to the Standard Transaction Keys. These are also added through the Transaction Manager Configuration by using the 'Enable Key' statement.

User-defined Transaction Keys

When Standard or Custom Transaction Key fields are unsuitable to gather the required data, User-defined Transaction Key fields can be used.

User-defined Transaction Key Fields are not currently supported for IST/Switch.

For details see the following sections: