Receiver FI Incoming Request for Information (TCH)

The main Receiver FI Incoming Request for Information flow.

Use case summary

The Request for Information is initiated by a client or the client's financial institution (FI), who requires further information about a credit transfer (CT) or a request for payment (RFP) that has been received from a debtor (CT) or creditor (RFP) FI. The request is delivered by the CT or RFP receiver's FI to the clearing and settlement mechanism (CSM). The CSM delivers the request to the RFI receiver FI, who can pass the request to their client.

The sending FI may time out if it hasn’t received an acknowledgment for an RFI from the CSM within its time out limit. If this occurs, the FI re-sends the request to the CSM with a possible duplicate flag set. When the CSM has no record of this request, it sends it to the receiver FI as a possible duplicate. If the request is not known to the receiver FI either, it is processed normally. Otherwise, the acknowledgment for the original request is sent a second time.

The receiver FI incoming Request for Information case consists of the following processing steps:
  • FTM for Immediate Payments receives a request from the CSM.
  • The request is validated, checked for duplicates, and correlated to the original payment / request for payment.
  • If the request has already been received by the FI before, and the possible duplicate flag is set, the acknowledgment for the original request is sent to the CSM again and the process completes.
  • If the previous validation step is successful, the set of services that are configured for the pre-check set are invoked. All configurable services can be configured differently for requests initiated from a client and the client's FI (agent).
  • FTM for Immediate Payments sends an acknowledgment to the CSM to confirm the acceptance or rejection of the request.
  • If the pre-check services did not complete successfully, an negative acknowledgment is sent to the CSM, and the process sets a failed status and completes.
  • Otherwise, an acknowledgment is sent to CSM and post-accept services are invoked. By default - for requests initiated from a client - a notification is sent to the channels interface, which in turn may provide a notification to the receiver client.

Use case high-level sequence diagram

The high-level sequence diagram for the receiver FI incoming Request for Information case is shown in the following figure:
Note: The diagram illustrates a set of optional services within a parallel group for the pre-check service set. This group is empty as no services are configured by default. The set is provided as an extension point for customization.
Figure 1. Receiver FI Incoming Request for Information - high-level sequence diagram
fxrfnctdebtortchincomingrequestforinformationhighlevel.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 together by yellow boxes.

Figure 2. Receiver FI Incoming Request for Information - Good
fxrfnctdebtortchincomingrequestforinformationdsd1.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 (Fire and Forget) Send transaction fire and forget diagram

Use case simple object lifecycle diagram

Figure 3. Receiver FI Incoming Request for Information
fxrfnctdebtortchincomingrequestforinformationold1.png