ATM and POS Transaction Manager can be used to assist in the following situations.
Typical usage of Transaction Manager to manage ATM environments
ATM Transaction Manager Solution
Timeout occurring during peak period.
Under normal circumstances a customer complaint is usually relied upon to identify a problem. ATM Transaction Manager has the ability to monitor and threshold/alert on ‘Transaction Rate By FIID’. When alerted, filtering using ‘Transaction Counts By Originator’ data, or another summary can help to make a problem determination.
Detection of different behavior dependent on ATM type.
The display summary by ‘Type of ATM’ for all acquired transactions, is useful for monitoring performance trends. A particular device type may have a higher reversal or average transaction rate, leading to different CPU balancing of device handlers.
Monitoring new software releases of device handler code.
As the type of ATM is associated with a particular ATM device handler, any change to the device handler process can also be targeted for measurement against the pre-installation trend.
Increase in the number of ATMs or new location strategy.
‘Card Acceptor’ reporting is a good indicator of the spread of issued card usage among various acquiring institutions. Total counts indicate queuing at an ATM, suggesting another machine should be installed in the locality. Locations with a larger number of ‘Card Acceptors’ attract more interchange transactions.
Detection/monitoring of regional failures.
ATMs grouped by ‘State Code’ can usually identify a particular communication segment. Monitoring call volumes by ‘State Code’ may detect regional network failure.
Transactions are being declined.
Monitor transaction results with a 'dashboard' type Display in real time. The 'dashboard' can indicate denial rates per FIID and the associated response code that explains the cause of the transaction decline.
Transactions are being reversed.
Monitor transaction reversals. Use an online Display to see reversals as they occur. See ATMID, its location and the reversal reason that explains why the transaction was reversed. View historical reports that show how many reversals have occurred for each ATM. Pinpoint ATMs that are reversing excessive amounts of transactions.
Response time of some transactions is too slow
Monitor response times in real time using 'dashboard' type Display. This can indicate which issuer is affected and whether the slow response is caused by local processing or a slow response time from the issuer side.
Typical usage of Transaction Manager to manage POS environments
POS Transaction Manager Solution
Interchange/switch is denying all saving account transactions.
Under normal circumstances a customer complaint is usually relied upon to identify a problem. POS Transaction Manager provides the ability to monitor and threshold/alert the ‘Transaction Approval Count By Interchange’. When alerted, filtering using ‘Transaction Code Approval Count’, or another summary can help to make a problem determination.
Transactions from a particular source may be experiencing high error rates.
POS Transaction Manager assists to identify the transaction profile, based on origin of the transaction. Acquired transactions may be more critical to business, than transactions originating from the switching partner. Thresholds can be set to monitor the percentage approval, number of timeouts or transaction rates for a specific origin.
Matching of appropriate terminals/functions to a retail location.
Transaction code profiles segregating purchases, merchandise return, adjustments, etc can be historically summarized for trends.
Increase in the number of timeouts (indicating potentially serious performance issues in the future).
The bottleneck may be transactions arriving from a specific host request or switching partner affecting cards of a particular financial institution. Using Transaction Manager, the origin of timeouts can be easily identified.
Launch of a new product (e.g. private label card).
Close monitoring by type of card can be set up to target this highly visible traffic.
Increase in a type of denial in network traffic (indicating a serious authorization problem).
Call centers that receive queries of this nature are often unable to differentiate between a genuine denial and an authorizer-induced denial. The source of the authorizer with high decline rates can be isolated, and the call center can be informed with an accurate response for the impacted customer.