Functional Requirements

It is common for business applications to create transactions that are forward dated, that is, they are intended to be processed and acted upon at some point in the future. In addition, a number of clearing and settlement mechanisms only allow acceptance and ingestion of transaction messages within the bounds of a certain time window during a working day. As a result, these transactions messages will need to be held and stored until this window opens.

FTM is able to facilitate the storing functionality through the use of a holding state in the finite state machine of the transaction message and is able to facilitate the releasing functionality of those held transaction message at a later time through the use of Scheduler Tasks in FTM.

The diagram below shows the system interactions of the components in the sample application. The diagram illustrates a high-level view of the systems interacting in this sample application.

Figure 1. Store and Release system interaction

The client can submit a single payment for processing. The payment is processed as follows:

Single Payment: The payment is mapped and checked to see if it should be stored for processing later, or submitted to the payment gateway. For payments that are stored, a scheduler task is created to check stored payments if they are ready for release. If so, the payments are submitted to the payment gateway.