Detailed Sequence Diagrams

The sequence diagrams below cover the following scenarios:
  1. Payment message is currently eligible to be processed and is sent to the Payment Gateway immediately.
  2. Payment message is currently ineligible to be processed and is put into a holding state.
  3. Payment message is released from held state at a scheduled time and is sent to the Payment Gateway.
  4. Payment message is manually released by an operator and is sent to the Payment Gateway.

Scenario 1

In this scenario, the following process occurs:
  • FTM receives a payment message from the client.
  • The payment message is logged and mapped to ISF, creating an inbound transaction.
  • After the inbound transaction has been mapped, the value date on the payment message and the processing date of the service participant representing the Payment Gateway are compared.
  • The value date is on or before the processing date of the Payment Gateway, so outbound transaction and outbound transmission objects are created for the payment message, resulting in the payment message being sent to the Payment Gateway, with no acknowledgment from the Payment Gateway being expected.
Figure 1. Payment message is currently eligible to be processed and is sent to the Payment Gateway immediately.

Scenario 2

In this scenario, the following process occurs:
  • FTM receives a payment message from the client.
  • The payment message is logged and mapped to ISF, creating an inbound transaction.
  • After the inbound transaction has been mapped, the value date on the payment message and the processing date of the service participant (representing the Payment Gateway) are compared.
  • The value date is after the processing date of the Payment Gateway so the payment inbound transaction object for the payment message is transitioned to a holding state.
Figure 2. Payment message is currently ineligible to be processed and is put into a holding state.

Scenario 3

In this scenario, the following process occurs:
  • The scheduled time to release payments occurs and triggers the scheduler task.
  • The scheduler task locates all held payment messages.
  • It then compares each held payment message value date with the processing date of the service participant (representing the Payment Gateway) and if the value date is on or before the processing date, an outbound transaction and outbound transmission objects are created for the payment message.
  • The payment message is then forwarded to the Payment Gateway, exiting FTM, with no acknowledgment expected.
Figure 3. Payment message is released from held state at a scheduled time and is sent to the Payment Gateway.

Scenario 4

In this scenario, the following process occurs:
  • The operator sends a command transaction, which is logged and mapped to ISF, in order to manually release a held payment message.
  • After the command transaction is mapped, the held payment message that is associated with the command transaction being processed is identified and is transitioned out of the holding state.
  • After being transitioned from the holding state, the outbound transaction and outbound transmission objects for the payment message are created and the payment message is sent to the Payment Gateway for processing, with no acknowledgment expected.
Figure 4. Payment message is manually released by an operator and is sent to the Payment Gateway.