Payment router system property parameters

Below is a list of parameters for setting up the system properties in the payment router API.

Code	Description
DEFAULT_INCOMING_PAYMENT_CHANNEL_CODE	The input defines the default payment channel to use when the incoming payment details do not include a payment channel. Example: ACCOUNT_API
DEFAULT_OUTGOING_PAYMENT_CHANNEL_CODE	The input defines the default payment channel to use when the outgoing payment details do not include a payment channel. Example: ACCOUNT_API
ERROR_PAYMENT_TRANSFER_PROCESSING_ENABLED	Selection determines the subsequent processing of outgoing payment transfers in ERROR status. If set to Yes, the processing of the outgoing payment transfer will continue (e.g. response files). Options: Yes, No.
FX_RATE_PRECISION	The input defines the precision of the exchange rate. Format: Integer, in the most minor currency units. Example: 10 in the case of EUR means 10 eurocents.
INCOMING_PAYMENT_QUEUE_BATCH_DELAY	The input specifies the waiting time between processing queued incoming payments. Format: Integer, in milliseconds. Example: 100.
INCOMING_PAYMENT_QUEUE_BATCH_ENABLED	Selection enables the activation of the batch job, processing payments in the QUEUED status and updating them to the INSERTED status based on predefined rules. If set to Yes, the batch job processing is activated. Options: Yes, No.
INCOMING_PAYMENT_QUEUE_ENABLED	Selection determines the processing of incoming payments. If set to Yes, incoming payments will initially be in the QUEUED status and processed in batches according to the order in which they were received. If set to No, they will be in the INSERTED status and follow the regular payment processing flow. Options: Yes, No.
LIB_NOSTRO_ENABLED	Selection determines the creation of nostro transactions for the payment transfers managed in the payment router. If set to Yes, financial transactions related to payments via the payment router for nostro accounts will be created. Options: Yes, No.
NOSTRO_TRANSACTION_REVERSAL_ENABLED	Selection determines whether the nostro account transaction reversals are permitted. If set to Yes, the nostro account transaction reversals will be permitted. Options: Yes, No.
OUR_BIC	The input defines the BIC (SWIFT) code, which identifies your institution for payments.
PAYMENT_RETURN_AS_OUTGOING_PAYMENT	Selection determines how the returned payment transfers are managed. If set to Yes, they will be returned as regular outgoing payments. If set to No, they will be returned as returned payments. Options: Yes, No.
PAYMENT_ROUTER_API_FINANCE_ENTRIES_ENABLED	Selection determines the creation of financial entries for the payment transfers managed in the payment router. If set to Yes, financial records for payment router transfers will be generated within the Tuum system. If set to No, another system will handle financial records for payment router transfers. Options: Yes, No.
POSTING_DATE_BACK_VALUE_DAYS	The input specifies the maximum number of days that can be deducted from [currentBankingDate according to nostro account time zone] to calculate the earliest permitted postingDate for the nostro account transaction. Format: Integer. Example: 15.
POSTING_DATE_FUTURE_VALUE_DAYS	The input defines the maximum number of days that can be added to the currentBankingDate to calculate the latest permitted postingDate based on settlementDate and valueDate for the incoming payment transfer. Format: Integer. Example: 5.
ROUTER_INTERNAL_POSTING_DATE_BACK_VALUE_DAYS	The input specifies the maximum number of days that can be deducted from the active banking date to determine the earliest permitted settlement date for incoming payment transfers. Format: Integer. Example: 185.
SETTLEMENT_DATE_BACK_VALUE_DAYS	The input specifies the maximum number of days that can be deducted from the current banking date to determine the earliest permissible settlement date for the payment transfer. Format: Integer. Example: 150.
SETTLEMENT_DATE_FUTURE_VALUE_DAYS	The input defines the maximum number of days that can be added to the current banking date to determine the latest permitted settlement date for the payment transfer. Format: Integer. Example: 10.