The debtor FI incoming return good case consists of the following processing steps:
FTM for Immediate Payments receives a return from the CSM.
The return is validated and checked for duplicate.
Next, the set of services that are configured for the Pre-Check (Return) set are invoked. This set should just
perform validation checks to determine whether the return can be accepted.
On successful completion of the Pre-Check services, the set of services (if any) that are configured for
the Pre-Accept set are invoked.
On successful completion of the Pre-Accept (Return) services, for TCH, FTM for Immediate Payments sends a
positive acknowledgment to the CSM, confirming that the return has been accepted by the bank. This step doesn't
happen for SCTInst.
For TCH, FTM for Immediate Payments waits for an acknowledgement status message from the CSM.
For both schemes, FTM for Immediate Payments invokes the services configured for the Post-Accept (Return) set. This will
typically include a service to send a notification to the Channels interface, which in turn may provide a
notification to the (debtor) client.
Use Case High-Level Sequence Diagram
The high-level sequence diagram for the creditor FI incoming return good case follows the same High-Level
Sequence Diagram as the creditor FI incoming Credit Transfer good use case.
Note: The diagram illustrates sets of
optional services within parallel groups for each of the service sets Pre-Check, Pre-Accept, Post-Accept. The
services shown depict services that may typically be included in the set. The actual services to be invoked, and
whether they are invoked in parallel or serially is determined by configuration
Use Case Detailed Sequence Diagram
The detailed sequence diagram is split into three parts.Figure 1. Valid Incoming Return: Part 1 of 3
