Creditor FI Incoming Response to Request for Payment (TCH)

The main Creditor FI Incoming Response to Request for Payment flow.

Use case summary

The Response to Request for Payment is an optional response that is initiated by a (debtor) client to inform the Creditor that the Request for Payment was accepted or rejected by the Debtor. Alternatively, a payment can be initiated by a (debtor) client as a positive response to a Request for Payment. This alternative is covered by the Outgoing Credit Transfer use case. In the case of the accept or reject response, the response is delivered by the debtor financial institution (FI) to the clearing and settlement mechanism (CSM). The CSM delivers the response to the creditor FI, who can pass the response to their (creditor) client.

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

The creditor FI incoming Response to Request for Payment case consists of the following processing steps:
  • FTM for Immediate Payments receives a response from the CSM.
  • The response is validated, checked for duplicates, and correlated to the outgoing Request for Payment.
  • If the response has already been received by the creditor FI and the possible duplicate flag is set, the acknowledgment for the original response is sent to the CSM again and the process completes.
  • If the previous validation step is successful, a notification is sent to the channels interface, which in turn may provide a notification to the (creditor) client.
  • FTM for Immediate Payments sends an acknowledgment to the CSM to confirm the acceptance of the response.
  • An 'accept' or 'reject' event is raise to allow the outgoing Request for Payment transaction to move to an appropriate 'accept' or 'reject' state.

Use case high-level sequence diagram

The high-level sequence diagram for the creditor FI incoming Response to Request for Payment case is shown in the following figure:
Figure 1. Creditor FI Incoming Response to Request for Payment - high-level sequence diagram
fxrfnctcreditortchincomingresponsetorequestforpaymenthighlevel.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. Creditor FI Incoming Response to Request for Payment - Good
fxrfnctcreditortchincomingresponsetorequestforpaymentdsd1.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. Creditor FI Incoming Response to Request for Payment
fxrfnctcreditortchincomingresponsetorequestforpaymentold1.png