Process a direct debit request

This scenario starts with the indirect participant client posting a pacs.003 direct debit request. This request is processed by the SDD reference application running at a direct participant creditor financial institution. The creditor bank processes the message, causing it to flow to the STEP2 clearing house. STEP2 processes the message, along with other messages, by sending it to the direct participant debtor financial institution. The SDD reference application at the debtor processes the debit request, passing it along to the debtor client. Eventually, settlement occurs and STEP2 notifies both the creditor and debtor of this fact. The SDD reference application at both the creditor and the debtor handles the settlement notifications. The complete process is referred to as the main direct debit flow.

The main direct debit flow is needed before any of the other scenarios can be executed. Each of the other scenarios executes all or part of the main direct debit flow before they execute.

The debits processed during the main creditor flow are passed by STEP2 to the reference application running at the direct participant debtor. The processing of these debits is called the main debtor flow.

A complete end-to-end diagram of the main direct debit flow is shown in the following figure.

When executing this and other flows on a single workstation, either the creditor side or the debtor side should be performed from start to finish. Clear the database after each side is finished. Both the creditor and debtor sides can be executed on a single workstation, but the number and status of transactions seen in the FTM Operations and Administration Console (OAC) may become confusing.