Debtor FI Outgoing Response to Request for Payment (TCH)

The main debtor financial institution (FI) outgoing Response to Request for Payment flow.

Use case summary

The Response to Request for Payment response is initiated by a (debtor) client to accept or reject the Request for Payment that was requested by a creditor. The message is delivered by the debtor financial institution (FI) to the clearing and settlement mechanism (CSM). The CSM delivers the message to the creditor FI, who can pass it to their (creditor) client.

After the Request for Payment response is delivered to the CSM, the debtor FI times out if it does not receive a status confirmation from the CSM within the defined period. Currently, it resends the message with a possible duplicate flag, continues waiting for the status confirmation, and possibly resends again after further timeouts. An option is provided for operations to manually cancel the message, which is normally only used during a prolonged outage of communication to the CSM. When you manually cancel the message, you can also confirm that the message was never delivered to and processed by the CSM before you cancel it.

The debtor FI outgoing Response to Request for Payment case consists of the following processing steps:
  • FTM for Immediate Payments receives a message from the channels interface on behalf of a (debtor) client to initiate a Response to Request for Payment.
  • The message is validated, checked for duplicates, and correlated to the incoming Request for Payment.
  • If the previous validation step is successful, the Request for Payment response 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 debtor FI times out and resends the message with a possible duplicate flag to the CSM. It also restarts the timer and continues waiting. This step can repeat until either a status confirmation is received from the CSM or the operator cancels the message.
  • FTM for Immediate Payments sends an acknowledgment to the channels interface, which in turn might provide a notification to the (debtor) client.

Use case high-level sequence diagram

The high-level sequence diagram for the debtor FI outgoing Response to Request for Payment case is shown in the following figure:
Figure 1. Debtor FI outgoing Response to Request for Payment - high-level sequence diagram
fxrfnctdebtortchoutgoingresponsetorequestforpaymenthighlevel.png

Use case detailed sequence diagram

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

Figure 2. Debtor FI outgoing Response to Request for Payment - good
fxrfnctdebtortchoutgoingresponsetorequestforpaymentdsd1.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. Debtor FI outgoing Response to Request for Payment
fxrfnctdebtortchoutgoingresponsetorequestforpaymentold1.png