This variation of the main Debtor FI Outgoing Credit Transfer flow showing scenarios where the
payment may be rejected.
Use Case Summary
There are two variants of the debtor FI outgoing credit transfer bad case, depending on whether the debtor
and creditor accounts belong to the same financial institution. This special case is called an On Us
payment, and the payment does not need to be sent to the CSM for further processing. Such a payment is
recognised if the bank code for the creditor FI matches a configured value.
The debtor FI outgoing credit transfer bad case consists of the following processing steps:
Not On Us payment
FTM for Immediate Payments receives an immediate payment Credit Transfer Request from the
Channels interface on behalf of a (debtor) client.
The payment is validated and checked for duplicate.
If the previous validation step is successful, the set of services that are configured for the Pre-Check
Not On Us set are invoked. This set should just perform validation checks to determine whether the payment can
be accepted for submission.
If the Pre-Check Not On Us services complete successfully, the set of services (if any) that are
configured for the Pre-Submit set are invoked.
If the Pre-Submit services complete successfully, 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 unsuccessful processing, responds with a
negative acknowledgment. A check is performed here to see if the Credit Transfer is sent in response to a
Request for Payment, and if so, an event is raised to signal the Request for Payment process.
Regardless of which of the previous steps failed, FTM for Immediate Payments sends a negative
acknowledgment to the Channels interface, which in turn may provide a notification to the (creditor) client,
confirming that the payment has been rejected, with appropriate reason information.
If in the previous steps an Accounting Debit, or an Accounting Reserve Funds request completed
successfully, an Accounting Debit Reversal request is issued.
On Us payment
FTM for Immediate Payments receives an immediate payment Credit Transfer Request from the
Channels interface on behalf of a (debtor) client.
The payment is validated and checked for duplicate.
If the previous validation step is successful, the set of services that are configured for the Pre-Check
On Us set are invoked. This set should just perform validation checks to determine whether the payment can be
accepted for submission.
If the Pre-Check On Us services complete successfully, the Accounting DebitCredit request is invoked to
charge the debtor's account and book funds to the creditor's account. The Accounting service replies with an
unsuccessful response. .
Regardless of which of the previous steps failed, FTM for Immediate Payments sends a negative
acknowledgment to the Channels interface, which in turn may provide a notification to the (creditor) client,
confirming that the payment has been rejected, with appropriate reason information.
Use Case High-Level Sequence Diagram
The high-level sequence diagram for the debtor FI outgoing credit transfer bad cases looks as shown in the
following figure:
Note: The diagram illustrates sets of optional services within parallel groups for each of
the service sets Pre-Check On Us, Pre-Check Not On Us, Pre-Submit. 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.
Figure 1. Debtor FI Outgoing Credit Transfer Bad - high-level sequence diagram
