Creditor FI use cases

This section describes the detail of the process that is orchestrated by FTM for High Value Payments to support the creditor financial institution (FI) role for each of the FTM for High Value Payments use cases.

In each case, the process manages the message exchange with the clearing and settlement mechanism (CSM) and manages the interaction with other systems in the bank. FTM for High Value Payments provides a number of pre-built integration points to a set of key systems; channels, accounting, fraud screening, and sanction screening. The integration points are built around sets of services, which may be provided by these systems, and are invoked by the FTM for High Value Payments process. See the section Integration Overview for more details on these services and how to integrate with systems in a bank.

To provide flexibility, and the ability for a bank to tailor and extend the process to suit their needs, most of the steps that are performed within the FTM for High Value Payments process may be controlled by configuration. Many of the process flows define named sets of services that are orchestrated at different stages of the process. For example, the Creditor FI Incoming Credit Transfer Good use case defines the three sets of services, Pre-Check, Pre-Accept, and Post-Accept. For each of these sets the actual services that are invoked are determined by configuration settings.

A set may specify zero or more services that may be invoked in parallel, serially, or combinations of parallel and serial. The set completes normally (succeeds) when all the services complete successfully. A set completes unsuccessfully if any service completes unsuccessfully. A set may also complete after a timeout. The implication of a timeout depends on the use case and set.

For the incoming credit transfer use cases, different sets of configuration are provided that arrange the services differently to support alternate accounting models:
  • One Step – each normal successful payment involves one call to the accounting system
  • Two Step – each normal successful payment involves two calls to the accounting system

The One Step model is more efficient, but may require the reversal of bookings in the case of unsuccessful payments. The Two Step model involves more service calls to the accounting system, but booking to customer accounts is only performed after confirmation of settlement.

The following table lists the service sets that apply to the incoming credit transfer use cases and for each accounting model, the services that are included in each set.
Service set Two Step Accounting One Step Accounting

Pre-Check Services

Sanction Screening

Accounting Inquiry

Sanction Screening

Pre-Accept Services

  

Accounting Credit

Post-Accept Services

Accounting Credit

Credit Notification

Credit Notification

See the section Setup and Customization for more details on how to configure the sets of services and how to define and add new services.