Configuration values

General configuration

Bank and process configuration

On-us bank codes

Typically, these configuration values need to be changed to values that are appropriate for your environment.

The ONUS_BANK_CODE category is used to define bank codes that, for the purposes of outgoing payments, can be settled internally without interaction with the CSM. Typically, this category is an enumeration of all the BIC or routing numbers for the bank. If these numbers are defined, they are checked against the DEST_BANK_CODE of the outgoing credit transfer transactions. When the BIC or routing numbers match, the prechecks that match the values in the HVP_OUTGOING_PRE_CHECK/ONUS key for the value table category HVP_PROCESS_ONE_STEP_ACCNT or HVP_PROCESS_TWO_STEP_ACCNT are done. This situation typically means that an on-us payment doesn't require a call to the sanction screening service or require a reservation of funds and the CSM interaction is avoided.

Add a new key entry for each bank code. The value can be any non-null value. A null value can be used to disable the bank code from the check.

Duplicate checks

The mappers set the ID references. If a mapper or post-mapper sets an ID reference, the reference can be added to the list and is checked. If an ID reference is in the list but it wasn't set by a mapper, the reference is not checked for duplicates.

Timeouts

Typically, you can use the defaults for these configuration values.

Accounting process models

These key values define the different stages of the one-step and two-step accounting process.

In addition to the predefined service names, the list can contain any custom action that you define. You must adhere to a few simple rules when it is called.

Routing

Typically, you can use the defaults for these configuration values.

Standard FTM routing mechanisms are used. The value table category ROLE_FOR_TXN_TYPE is used to define a Service Participant role for each outbound transaction type. When an outbound transaction is being created, the generic routing algorithm locates the outbound channel from the Service Participant whose role matches that defined for the TRANSACTION.SUBTYPE.

Map configuration

Typically, you can use the defaults for these configuration values.

These entries are used to define message-specific mapping configuration for a channel or mapper that can process multiple message types. Essentially, it allows a common or channel map to be used and have the configuration entries control key attributes such as the mapper, transaction, or message types.

<msgTypeCfg>
   <class>PACS008</class>
   <subType>HVP_TO_CSM_INSTR</subType>
   <extendedCfg>
      <name>MASTER_FLAG</name>
      <value>N</value>
   </extendedCfg>
   <pt>
      <class>PACS008</class>
      <subType>HVP_TO_CSM_INSTR</subType>
   </pt>
   <mapName>ISFToPacs008Mapper</mapName>
   <type>pacs.008.001.08</type>
</msgTypeCfg>

Finite state machine (FSM)

Typically, you can use the defaults for these configuration values. Changing them might cause the high value payments application FSMs to fail.

These configuration values are used to set the OBJ_CLASS of the status message that is sent back to the CSM in the Incoming Credit Transfer use case. The current scheme is used as the key to look up the configuration value to return and use as the OBJ_CLASS. This category is used to configure whether to wait for a response to the status message or not. Use the OUT_TXN_NOWAIT value when you want to wait for a response. Use the OUT_TXN_NOWAIT_COMPLETE value when you don't need to wait for a response from the CSM.

Message enrichment

For an outgoing message to the network, CSM, or Gateway, many fields are populated according to enrichment configuration. This configuration allows the high value payments application to generate scheme-compliant values to be used in the outgoing message, which is usually the default behavior. Or, a value that is provided by the channel interface can be used without modification.

Channel-specific configuration entries take priority over non-channel-specific configuration entries. Usage of any specific configuration value is covered in the relevant functional flows topic for that use case.

Status codes to the channel

The default channel rank value that is used for the product is CHANNEL1. Therefore, the example category pattern of CHANNEL1_TARGET2_PMT_STSCDS provides the configuration for status messages to Channel1 for an outgoing payment to T2.

To determine whether a status is sent to the channel, the status code itself is checked against the keys in the relevant CHANNEL_SCHEME_USECASE_STSCDS category. If the value of the status code has a corresponding key, the status is sent. When the status code does not have a corresponding key, the status to the channel is suppressed instead.

When a status is to be sent to the channel, the status code in the message can be determined from the status code that was received in the message from CSM. For each configuration entry, the key represents the status code from CSM and the value represents the code that is used in the message to the channel. In the first row of the following table, both the key and value are ACSC. Therefore, the message is sent to the channel with the status code unchanged.

CSM status response configuration

For example, category TARGET2_PMT_CSM_ACK_VALUES provides the configuration for response acknowledgment messages from T2, for an outgoing payment.

The keys in these categories are defined as the subtype of the incoming acknowledgment and the value that is contained in the message, separated by a comma. For example, the key HVP_FROM_CSM_PSTAT,ACSC provides configuration for a pacs.002 response that contains status code ACSC.

If a response message is handled as an interim acknowledgment, a status update can be sent to the originating client. After that update is sent, the process continues to wait for a final acknowledgment before it proceeds to the post-submit stage.

Channel configuration

The keys in these categories are the subtype of the incoming message. The value is the channel to use to send the notification.

HVPS+ usage rules configuration

HVPS+ user exit configuration

Load Gateway Server configuration