Creditor FI Outgoing Request for Payment Cancellation (TCH)
The main Creditor FI Outgoing Request for Payment Cancellation flow.
Use case summary
The Request for Payment Cancellation is initiated by a (creditor) client who requires a RFP Cancellation from a debtor. The request is delivered by the creditor financial institution (FI) to the clearing and settlement mechanism (CSM). The CSM delivers the request to the debtor FI, who can pass the request to their (debtor) client.
Having delivered the Request for Payment Cancellation request to the CSM, the creditor FI times out if it does not receive a status confirmation from the CSM within the defined period. At this time, it re-sends the request with a possible duplicate flag, continues waiting for the status confirmation, and, possibly, re-sends again after further time outs. 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.
- FTM for Immediate Payments receives a request from the channels interface on behalf of a (creditor) client to initiate a Request for Payment Cancellation. Alternatively a RFP Cancel request can be initiated from the OAC by an operator, using a 'Cancel RFP' action for an existing outgoing RFP that is waiting for a response.
- The request is validated, which can include duplicate checking and correlation to an original RFP.
- If the previous validation step is successful, the set of services that are configured for the pre-check set are invoked.
- If the pre-checks are successful, a Request for Payment Cancellation request 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 creditor FI times out and re-sends the request with a possible duplicate flag to the CSM, restarts the timer, and continues waiting. This step can repeat until either a status confirmation is received from the CSM or the operator cancel is issued.
- Next, FTM for Immediate Payments raises an 'RFP Cancel Received' event for the associated RFP and then sends an acknowledgment to the channels interface, which, in turn, may provide a notification to the (creditor) client.
Command | ||
Cancel RFP | ||
Parameters | CancellationReasonCode | Y |
CancellationReasonInformation | Y | |
CancellationOriginatorAgent | Optional, max of one to be provided | |
CancellationOriginatorName |
Use case high-level sequence diagram
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.
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 |