Introduction to Everlink ATM Interface

The existing interface with Everlink provides a system that has Online with Stand-In processing. This provides customers with near seamless access to their accounts on a 24/7 basis. The Everlink Network expects connectors will be available at least 95% of the time for direct online processing. The Everlink switch aims for 100% availability with a 99% threshold level. Other than a small servicing window on Sunday mornings, the Everlink switch will usually be available for processing.

When the existing HOBS database is available, all transaction requests will be passed through from the Everlink switch to be processed and the resulting acceptance or denial code response is returned to the Everlink switch. When the HOBS database is not available, the Everlink switch will reference the CAF database that is maintained at their site and attempt to complete the process based on the most recent information they have available. As soon as the host database is available, the transactions that had been logged offline will be streamed to the HOBS system for online processing.

When the overnight processing is started a job is run that turns the database writes off for some processing channels so that Operations has a static database for backups and their processes. While in write-off mode, the HOBS will respond to every Everlink request but log the entries in a transaction file for later database updates. After the Overnight is completed, a second job will turn the database writes back on and all the transactions that have been logged will then be posted. Since these logged transactions were previously entered and the customer is not there, the response portion of the transaction is not processed. The interface has parameters that determine where the transaction has originated from so it knows not to respond to a logged transaction but will respond to an online transaction request.

The offline processing by Everlink is only invoked during the rare time that the HOBS system is not connected or there are network problems between the two data centres. The HOBS will normally be online with Everlink, even when the HOBS database is in writes-off mode during the Overnight processes. When Everlink is authorizing transaction requests it will use the CAF database that is maintained at their site. This file identifies which cards are valid, the accounts that each card has assigned and the offline transaction limits that have been granted to that card. The offline limit is an assigned value and does not reflect the actual account balance so when Everlink is left to issue a transaction response, the customer is able to withdraw the full offline limit even if that amount exceeds the actual account balance. This is a key reason to ensure the HOBS system is available as much as possible.

The request and response activity that the transaction handler completes is only a portion of the complete Everlink Node Network system. There is extensive encryption and MAC’ing of transactions at most stages of each entry to ensure the integrity of each transaction. The Everlink system has a database of Card information that is maintained through FHM and CAF updates to be referenced when in offline mode.

All the CFG ATM’s are connected to the Everlink Network and it is from Everlink that all ATM and POS transactions are currently being received. The implementation of Interac ISO 8583 has increased the security so now there is MACing from the ATM or POS to Everlink and also from Everlink to CFG for every financial transaction.

The Everlink processing for ATM and POS both use the same CAF file for offline authorization and processing but none of the security working keys are shared. There are required to be separate channels connecting the ATM and the POS processing so that each channel can be independently activated and authorized by Everlink.

The existing banking platform requires an ever increasing advanced level of security and functionality to interact in the Canadian and International Financial environment. The HOBS connection with Everlink has gone through a full Testing Certification to validate the existing system processes.

The Everlink system will send request to Temenos Transact in the form of ISO8583_1987 version is used messages have to decode these ISO message into OFS message and post into Temenos Transact.

After transaction being processed we get back the results as OFS messages and have to encode these into ISO messages to reply back Everlink system.

Assumptions

• The RAD pack should be already installed
• For all POS transactions the account number should be fetched from CARD.ISSUE using PAN number
• Foreign currency transaction are not used
• FHM is not covered under in this IDD and it will be handled separately
• The alerts are out of Interface scope and hence it is not covered in the IDD. We only maintain those failures in server logs and alerts to be done from there by any 3rd party system, as it is not under our interface scope
• No formats are provided for balancing reports, Mix and Match (Daily) and standard banking reports, hence not covered in this IDD. If report formats are provided then it can be incorporated in IDD
• If the security device is unavailable or broken the jar file will raise a fatal out error the message will be not processed and the response is not sent back to switch
• Temenos Transact will support Thales Security Device Using TCP or IP connection
• Card access application to be setup with appropriate account numbers for interface to be used