Debtor FI to FI Outgoing Credit Transfer Good (TCH)
The main Debtor FI to FI Outgoing Credit Transfer flow.
Use Case Summary
The debtor FI to FI outgoing credit transfer good case consists of the following processing
steps:
- FTM for Immediate Payments receives an immediate payment Credit Transfer Request (FI) from the Channels interface on behalf of a (debtor FI) client.
- The payment is validated and checked for duplicate.
- Next, the set of services that are configured for the Pre-Check (FI) set are invoked. This set should just perform validation checks to determine whether the payment can be accepted for submission.
- On successful completion of the Pre-Check (FI) services, the set of services (if any) that are configured for the Pre-Submit (FI) set are invoked.
- On successful completion of the Pre-Submit (FI) services, the payment is accepted for submission, and a credit transfer request is created to submit to the CSM.
- The credit transfer request is sent to the CSM, which, after successful processing, responds with a positive acknowledgment.
- Next, the set of services that are configured for the Post-Submit Accept (FI) set are invoked.
- On successful completion of the Post-Submit Accept (FI) services, FTM for Immediate Payments updates the position and completes the SLA (not implemented yet) and sends an acknowledgment to the Channels interface, which in turn may provide a notification to the (creditor FI) client.
Use Case High-Level Sequence Diagram
Refer to the high-level sequence diagram of the debtor FI outgoing credit transfer good use case.
The FI to FI outgoing transfer good use case is very similar, except for the following differences:
- A pacs.009 is used instead of a pacs.008.
- On-us transactions are not applicable.
- There is no ACWP response.
- Non-payment transactions (remittance advice, request for information, request for payment, etc) are not supported.
Use Case Detailed Sequence Diagram
The detailed sequence diagram is split into three parts.