The lifecycle for each object in FTM is defined by a finite state machine
(FSM) model.
The following table shows the FSMs that are used to manage the lifecycle of the
FTM
objects for the
CPS reference application.
Table 1. Corporate Payment Services reference application finite state machines used
| FSM |
Type |
Object |
| Generic : Inbound Physical Transmission |
PT |
Payment origination |
| Inbound Payment Transmission |
PT |
Payment origination |
| Inbound Payment Batch |
Batch |
Payment origination |
| Inbound Payment Transaction |
Transaction |
Payment origination |
| Generic : Outbound Transaction |
Transaction |
Ingest physical transmission request |
| Generic : Outbound Physical Transmission |
PT |
Ingest physical transmission request |
| None |
Transaction |
Outbound bulk payment |
| Outbound Payment Batch |
Batch |
Outbound bulk payment |
| Generic : Outbound Physical Transmission |
PT |
Outbound bulk payment |
| Generic : Inbound Physical Transmission |
PT |
Release physical transmission request |
| Outbound Distribution Transaction |
Transaction |
Release physical transmission request |
| Generic : Outbound Transaction |
Transaction |
Update Distribution request |
| Generic : Outbound Physical Transmission |
PT |
Update Distribution request |
The generic finite state machines handle most of the objects that are used by the
CPS reference application. An FSM is needed for each of the objects that are shown in the following
table.
Table 2. Objects that need a Corporate Payment Services reference application FSM
| Object |
FSM |
| Payment origination transmission |
Inbound Payment Transmission |
| Payment origination batch |
Inbound Payment Batch |
| Payment origination transaction |
Inbound Payment Transaction |
| Outbound bulk batch |
Outbound Payment Batch |
| Release physical transmission request transaction |
Outbound Distribution Transaction |