Configuring High Value Payments for the customer

High Value Payments provides a number of configuration elements that need to be customized for each bank.

The tasks that are needed to customize the configuration elements are described in the following sections.

High Value Payments defines a number of configuration categories and entries which must be defined for each customer. In the customer model that was created in earlier setup steps, review the following:

HVP_BANK_CODE entry

High Value Payments defines a number of configuration categories and entries which must be defined for each customer. In the customer model that was created in earlier setup steps, do the following steps:
  1. Copy HVP_CONFIG/HVP_BANK_CODE category/key from the FTM HVP Common model, editing HVP_BANK_CODE to reflect the BIC or routing number that is assigned to the bank..

ONUS_BANK_CODE entries

High Value Payments defines the ONUS_BANK_CODE value category. Under this category, a bank can define name-value pairs to enumerate all BIC or routing numbers that can be settled internally without routing an outgoing payment to the CSM. In the customer model that was created in earlier setup steps, do the following steps:
  1. Copy the ONUS_BANK_CODE category from the FTM HVP App model.
  2. Edit the single value defined under this category to NULL by selecting the Null checkbox.
  3. For each bank code that can be settled internally without the CSM:
    1. Right-click the ONUS_BANK_CODE and select Add FTM > Value Key.
    2. Set the name of the value key to the value of the bank code.
    3. Set the value of the value key to any non-null value. For example, you might want to use the value Y or a description, such as Head Office.

Process configuration

High Value Payments provides a number of finite state machines (FSMs) that define the processes that are used to process payment and related messages. Some of these FSMs define configurable process steps that can be customized by the customer.

Incoming and outgoing payment accounting models

The incoming and outgoing payment processes support a choice of two accounting models, One Step Accounting (HVP_PROCESS_ONE_STEP_ACCNT) or Two Step Accounting (HVP_PROCESS_TWO_STEP_ACCNT). The choice of which accounting model to use is configured per payment scheme. For more information about the accounting models, see Functional flows. Customers need read and understand that section and decide which value is most appropriate for them.

Edit the configuration value described in the following table in the customer model to select the chosen model.
Table 1. Accounting model configuration options
Value categories Value key Value Description
  • CBPR+_CONFIG
  • EURO1_CONFIG
  • NBO_CONFIG
  • RIX_CONFIG
  • KRONOS2_CONFIG
  • TARGET2_CONFIG
 PROCESS_CONFIG_CATEGORY HVP_PROCESS_ONE_STEP_ACCNT Use the One Step Accounting Model:

Outgoing Payment

  • Debit Funds
  • Submit to CSM

Incoming Payment

  • Credit Funds
  • Accept to CSM
HVP_PROCESS_TWO_STEP_ACCNT Use the Two Step Accounting Model:

Outgoing Payment

  • Reserve Funds
  • Submit to CSM
  • Debit Funds

Incoming Payment

  • Account Inquiry
  • Accept to CSM
  • Credit Funds
Any Other Value Use a custom named process model.

Customizing the standard accounting models

Each accounting model defines a finite set of value table keys:
Table 2. Categories: HVP_PROCESS_ONE_STEP_ACCNT and HVP_PROCESS_TWO_STEP_ACCNT
Key Description
HVP_INCOMING_PRE_CHECK Set of actions and services to be started for an incoming payment immediately after it is received from the CSM and validated.
HVP_INCOMING_PRE_CHECK/FI Similar to HVP_INCOMING_PRE_CHECK. Used for FI to FI credit transfers.
HVP_INCOMING_PRE_CHECK/RETURN Similar to HVP_INCOMING_PRE_CHECK. Used for credit returns.
HVP_INCOMING_PRE_ACCEPT Set of actions and services to be started for an incoming payment immediately after prechecks and before the Accept Response is sent to the CSM.
HVP_INCOMING_PRE_ACCEPT/FI Similar to HVP_INCOMING_PRE_ACCEPT. Used for FI to FI credit transfers.
HVP_INCOMING_PRE_ACCEPT/RETURN Similar to HVP_INCOMING_PRE_ACCEPT. Used for credit returns.
HVP_INCOMING_POST_ACCEPT Set of actions and services to be started for an incoming payment after an Accept status response to the CSM. Used for payments that must be settled by using the CSM.
HVP_INCOMING_POST_ACCEPT/ONUS Set of actions and services to be started for an incoming payment after an Accept status response to the CSM. Used for payments that can be settled internally.
HVP_INCOMING_POST_ACCEPT/FI Similar to HVP_INCOMING_POST_ACCEPT. Used for FI to FI credit transfers.
HVP_INCOMING_POST_ACCEPT/RETURN Similar to HVP_INCOMING_POST_ACCEPT. Used for credit returns.
HVP_INCOMING_POST_ACCEPT/RETURN_ONUS Similar to HVP_INCOMING_POST_ACCEPT/RETURN. Used for payments that can be settled internally.
HVP_OUTGOING_PRE_CHECK Set of actions and services to be started for an outgoing payment immediately after it is received from the channel and validated. Used for payments that must be settled by using the CSM.
HVP_OUTGOING_PRE_CHECK/ONUS Set of actions and services to be started for an outgoing payment immediately after it is received from the channel and validated. Used for payments that can be settled internally.
HVP_OUTGOING_PRE_CHECK/FI Similar to HVP_OUTGOING_PRE_CHECK. Used for FI to FI credit transfers.
HVP_OUTGOING_PRE_CHECK/RETURN Similar to HVP_OUTGOING_PRE_CHECK. Used for credit returns.
HVP_OUTGOING_PRE_CHECK/RETURN_ONUS Similar to HVP_OUTGOING_PRE_CHECK/RETURN. Used for payments that can be settled internally.
HVP_OUTGOING_PRE_SUBMIT Set of actions and services to be started for an outgoing payment immediately after it passed prechecks and before the payment is sent to the CSM.
HVP_OUTGOING_PRE_SUBMIT/FI Similar to HVP_OUTGOING_PRE_SUBMIT. Used for FI to FI credit transfers.
HVP_OUTGOING_PRE_SUBMIT/RETURN Similar to HVP_OUTGOING_PRE_SUBMIT. Used for credit returns.
HVP_OUTGOING_POST_SUBMIT Set of actions and services to be started for an outgoing payment immediately after it is sent to the CSM and accepted.
HVP_OUTGOING_POST_SUBMIT/FI Similar to HVP_OUTGOING_POST_SUBMIT. Used for FI to FI credit transfers.
HVP_OUTGOING_POST_SUBMIT/RETURN Similar to HVP_OUTGOING_POST_SUBMIT. Used for credit returns.
Any of the predefined service sets can be customized as follows:
  1. Create in the customer model the relevant Value Category HVP_PROCESS_ONE_STEP_ACCNT or HVP_PROCESS_TWO_STEP_ACCNT.
  2. Copy the key that you want to alter from the FTM HVP Common model.
  3. Edit the value in the copy of the customer model.
  4. See Configuration for more details about the exact syntax of the service definitions.

Custom named process model

The two standard accounting models can be customized to extend or alter the precise set of steps. However, it might be preferred to create a new name for the process model that more accurately reflects the purpose of the configuration set.

A new definition set can be created as follows:
  1. Decide which set HVP_PROCESS_ONE_STEP_ACCNT or HVP_PROCESS_TWO_STEP_ACCNT is closest to the requirement. Copy the selected value category and all its keys into the customer model.
  2. Rename the copied category to a name that reflects the business purpose or context.
  3. Edit the values to meet the requirements.
  4. See Configuration for more details about the exact syntax of the service definitions.
  5. Edit the <scheme>_CONFIG / PROCESS_CONFIG_CATEGORY value entry for the appropriate scheme to have the value match the category name from step 2. <scheme>_CONFIG is one or each of the following schemes.
    • CBPR+_CONFIG
    • EURO1_CONFIG
    • NBO_CONFIG
    • RIX_CONFIG
    • KRONOS2_CONFIG
    • TARGET2_CONFIG
    .