Debtor FI incoming response to recall - good and bad

The main debtor FI incoming response to recall flow.

Use case summary

The incoming response to recall is initiated by a (creditor) client or a creditor financial institution (FI) as a response to the recall request that was initiated by the debtor. The response is delivered by the creditor FI to the clearing and settlement mechanism (CSM). The CSM delivers the response to the debtor FI, who can pass the request to their (debtor) client.

The debtor FI incoming response to recall not on-us case consists of the following processing steps.
  1. FTM for High Value Payments receives an incoming response to recall either from the CSM or initiated by an On Us Outgoing Response to Recall.
  2. The incoming response to recall is validated and checked for duplicates. It is correlated to the original recall request and original payment transaction that the recall request was initiated for. The payment scheme (for example, CBPR+, EURO1, T2) is determined and assigned in the database record. Uncorrelated requests are also allowed.
  3. A default destination for the notification to channel is set by using the priority that is described in the following list.
    1. The default destination is the channel that initiated the original recall request.
    2. The default destination is the default channel that was configured for ROI notification.
  4. If the validation step is successful, the services that are configured for the precheck not on-us set are started.
  5. Following successful completion of the precheck services, the services that are configured for the post-accept set are started.
  6. The default for the configured post-accept service is to send a notification to the channel interface, which might provide a notification to the (debtor) client. The way the channel to use is determined for the different transaction types is shown in the following list.
    • The channel to which the notification is sent is determined by the object value entry where the category is HVP_CORE and the key is NOTIFICATION_DESTINATION. The value that is returned is the notification destination that is set during validation, and matches the value set for the correlated payment. The returned value is matched to a service participant entry with a matching rank and the outbound channel is used for notification. The default category that is used is CHANNEL1.
    • For uncorrelated transactions, the notification channel is determined by the configuration entry where the category is SCHEME_CONFIG and the key is DEFAULT_ROI_NOTIFICATION_DEST. An example of a category for these requests is TARGET2_CONFIG. The returned value is matched to a service participant entry with a matching rank and the outbound channel is used for notification. The default category that is used is CHANNEL1.
The not on-us incoming response to recall can fail in the validation, precheck, or post-accept steps. These failures can provide a negative acknowledgment (NACK) notification to the (debtor) client. Whether the negative acknowledgment is sent or not depends on configuration settings. The incoming response to recall is marked as failed in this case.

The debtor FI incoming response to recall on-us case consists of the following processing steps.
  1. FTM for High Value Payments receives an incoming response to recall that is initiated by an On Us Outgoing Response to Recall.
  2. The services that are configured for the post-accept on-us set are started.
  3. The default for the configured post-accept service is to send a notification to the channel interface, which might provide a notification to the (debtor) client. The way the channel to use is determined for the different transaction types is shown in the following list.
    • The channel to which the notification is sent is determined by the object value entry where the category is HVP_CORE and the key is NOTIFICATION_DESTINATION. The value that is returned is the notification destination for the correlated payment. The default category that is used is CHANNEL1.
    • For uncorrelated transactions, the notification channel is determined by the configuration entry where the category is SCHEME_CONFIG and the key is DEFAULT_ROI_NOTIFICATION_DEST. An example of a category for these requests is TARGET2_CONFIG. The returned value is matched to a service participant entry with a matching rank and the outbound channel is used for notification. The default category that is used is CHANNEL1.
The on-us incoming response to recall can fail in the post-accept steps. These failures can provide a negative acknowledgment (NACK) notification to the (debtor) client. Whether the negative acknowledgment is sent or not depends on configuration settings. The incoming response to recall is marked as failed in this case.

Use case high-level sequence diagram

The high-level sequence diagram for the debtor FI incoming response to recall use case is shown in the following figure.
Figure 1. Debtor FI incoming response to recall - high-level sequence diagram
fxtfnctdebtorincomingresptorecallhighlevel.png

Use case detailed sequence diagrams - good

The detailed sequence diagram for the debtor FI incoming response to recall not on-us good use case is shown in the following figure.
Figure 2. Debtor FI incoming response to recall not on-us - good
fxtfnctdebtorincomingresptorecallgoodnonusdsd.png
The detailed sequence diagram for the debtor FI incoming response to recall on-us good use case is shown in the following figure.
Figure 3. Debtor FI incoming response to recall on-us - good
fxtfnctdebtorincomingresptorecallgoodonusdsd.png

Use case detailed sequence diagrams - bad

The detailed sequence diagram for the debtor FI incoming response to recall bad due to a validation failure use case is shown in the following figure.
Figure 4. Debtor FI incoming response to recall - validation failure
fxtfnctdebtorincomingresptorecallbadvaliddsd.png
The detailed sequence diagram for the debtor FI incoming response to recall bad due to a precheck failure use case is shown in the following figure.
Figure 5. Debtor FI incoming response to recall - precheck failure
fxtfnctdebtorincomingresptorecallbadprecheckdsd.png

Use case simple object lifecycle diagrams

The simple object lifecycle diagram for the debtor FI incoming response to recall not on-us use case is shown in the following figure.
Figure 6. Debtor FI incoming response to recall not on-us
fxtfnctdebtorincomingresptorecallnonusold.png
The simple object lifecycle diagram for the debtor FI incoming response to recall on-us use case is shown in the following figure.
Figure 7. Debtor FI incoming response to recall on-us
fxtfnctdebtorincomingresptorecallonusold.png