Sender FI Outgoing Request for Information (TCH)

The main Sender FI Outgoing Request for Information flow.

Use case summary

The Request for Information is initiated by a client or client's financial institution (FI) who requires further information about a payment or a request for payment that was received. The request is delivered by the client's FI to the clearing and settlement mechanism (CSM). The CSM delivers the request to the FI, which initiated the payment or request for payment, who can pass the request to their client.

After the Request for Information request was sent to the CSM, the sender FI times out if it does not receive a status confirmation from the CSM within the defined period. Now, it resends the request with a possible duplicate flag. It continues waiting for the status confirmation, and, possibly, resends again after further timeouts. An option is provided for operations to manually cancel the request. This would normally only be used in the case of a prolonged outage of communication to the CSM, when it can also be confirmed that the request was never delivered to, and processed by, the CSM.

The sender FI outgoing Request for Information case consists of the following processing steps:
  • FTM for Immediate Payments receives a request from
    • the channel interface on behalf of a client or an FI agent to initiate a Request for Information.
    • an operator command to trigger an FI initiated Request for Information. This can be issued from the FTM for Digital Payments user interface.
  • The request is validated, checked for duplicates, and correlated to the original payment or payment request.
  • If the previous validation step is successful, a configurable set of pre-check services is invoked. This set can be defined differently for FI initiated and client initiated requests. It can also be empty, which is the default.
  • After the pre-checks are complete, a Request for Information message is sent to the CSM.
  • FTM for Immediate Payments then waits for the confirmation status message from the CSM.
  • If the status message is not received within a defined timeout limit, the request times out and is resent with a possible duplicate flag to the CSM. The timer is restarted, and continues waiting. This step can repeat until either a status confirmation is received from the CSM or the operator cancel is issued.
  • If the request was received from the channel interface, FTM for Immediate Payments sends an acknowledgment to the channel interface, which, in turn, can provide a notification to the client.

Use case high-level sequence diagram

The high-level sequence diagram for the sender FI outgoing Request for Information case is shown in the following figure:
Figure 1. Sender FI Outgoing Request for Information - high-level sequence diagram
fxrfnctcreditortchoutgoingrequestforinformationhighlevel.png

Use case detailed sequence diagram

FTM for Immediate Payments, which is represented by one lifeline in the preceding high-level sequence diagrams, has been divided into multiple lower-level lifelines in the following series of sequence diagrams. The lower level lifelines are grouped by yellow boxes.

Figure 2. Sender FI Outgoing Request For Information - Good
fxrfnctcreditortchoutgoingrequestforinformationdsd1.png
Table 1. Links to the diagrams for the referenced interactions
Referenced interaction Reference link
Log and Map Single Txn Log and map single transaction diagram
Inline Send Txn (Expect Ack) Send transaction expect acknowledgment diagram
Inline Send Txn (Fire and Forget) Send transaction fire and forget diagram

Use case simple object lifecycle diagram

Figure 3. Sender FI Outgoing Request For Information
fxrfnctcreditortchoutgoingrequestforinformationold1.png