Overview

The Transaction Server manages the processing and completion of transactions that are ingested in Payment Feature Services. Transaction data, and any associated images, are stored by Transaction Server for other processes to use. As transactions reach different states, the Transaction Server initiates state change events based on the scheduled configuration. Messages are sent to other components so they can further process the transaction. The components then access the transaction data and images stored by Transaction Server, and can cause transaction states to be changed. Transaction Server initiates any additional state change events required.

Transaction data comes from the IBM® 3890/XP Document Processor, the IBM 3897 Model-4 Image Capture System, other 3890/XP compatible reader and sorter devices, and non-sorter input. The non-sorter data may originate from any of the following sources (with or without images): electronic transaction files such as image cash letters (ICLs), branch capture devices, Automated Teller Machines (ATMs), or other item capture and exchange applications. Typically, Gateway loads non-sorter transactions into Transaction Server.

All the transaction information stored in the Transaction Server is indexed by site, business day date, and business category. This allows for the retention of several days’ worth of transaction information. The retention period is entirely at the customer’s discretion, but is primarily driven by storage availability.