Multivalue program parameters
A multivalue program parameter is a program parameter that takes an array as a value. For example, a parameter could take an array of integer values such as [2, 4, 6]. Note that, in some cases, only the first value in the array is actually used. In those cases, any additional values are ignored.
The following table lists the multivalue program parameters that are available on the Pismo platform.
Notes about data types:
- Boolean: Accepts only 'TRUE' or 'FALSE'. (Case is ignored.)
- Integer: Accepts values from -2^63 to (2^63)-1
- String: Maximum 100 characters
- Decimal: Maximum 100 character
Parameter ID | Name | Applies to | Type | Description |
|---|---|---|---|---|
| 1 | IGNORE_ACCRUALS_IF_ONLY_TTS | Setting transaction types to block accrual charges | Integer array | Transaction type IDs for transactions that should not accrue interest and that should not cause the account to be promoted to delinquent if they are the only types of transactions that are overdue. Example: [701, 711, 722] |
| 2 | PAYMENTS_TTS | Payment transactions | Integer array | Transaction type IDs for transactions that should be considered as payments. These types are used to calculate the total amount paid on the invoice and the amount paid by the due date. By default, the platform considers the following transaction types as payments: 201, 244, 255, 276, 282, 320, 342, 701, 711, 721, 2224. If you configure this parameter, you need to list all the transaction types that you want to consider as payments, because this parameter overrides the default platform configuration. Example: [201, 244, 255, 276] |
| 3 | DISCHARGE_PRIORITIZED_TTS_MIGRATION | Discharge process at migration | Integer array | Parameter used during migration to define which credit transaction types should prioritize the discharge of debits based on authorization info. If not configured, the platform applies the default hierarchy. Example: [201, 244] |
| 500 | DELINQUENT_ACCOUNT_CLOSURE_REASON | Credit liquidation | String array of integer values | The external ID of the reason for the account closure. Notes: Only the first value in the array is used. For parameter 500 to work, you must create the reason using the Create status reason endpoint. Although the external_id is not required in the creation of the status reason, it is required to be used in the Creli process. Example: ["12345"] |
| 501 | DELINQUENT_ACCOUNT_CLOSURE_PROCESSING_CODE | Credit liquidation | String array | Processing code for the credit transaction that the delinquent account closure process uses to settle the total due. Note: Only the first value in the array is used. Example: ["004000"] |
| 502 | DELINQUENT_ACCOUNT_CLOSURE_DAYS | Credit liquidation | String array of integer values | The number of days an account must be in delinquency before it can be closed. Note: Only the first value in the array is used. Example: ["60"] |
| 503 | DAYS_BEFORE_TO_WARNING_DELINQUENT_CLOSURE | Credit liquidation | Integer array | The number of days a warning event is generated before a delinquent account is closed. For example, if a delinquent account is due to be closed on the 20th day of the month, and DAYS_BEFORE_TO_WARNING_DELINQUENT_CLOSURE is set to 5, then a warning event is generated starting on day 15 of the month. Another warning event is generated on each subsequent day until the 19th (or until the the account is no longer in delinquency). Note: Only the first value in the array is used. Example: [5,15,20] |
| 504 | RECURRING_CHARGE_FINAL_ACCOUNT_STATUS | Create recurring charge plan | String array | Final account status indicating that both the recurring charge links and the scheduled charges have been canceled. Note: Only the first value in the array is used. Example: ["CANCELLED"] |
| 505 | DELINQUENT_ACCOUNT_CLOSURE_LATE_TRX_DEBIT_PROCESSING_CODE | Credit liquidation | String array | After an account is closed for delinquency, it can still receive late transactions. The Pismo platform creates offsetting transactions to settle these. If a late credit transaction is received, the platform creates a debit transaction to settle it. The first value in the DELINQUENT_ACCOUNT_CLOSURE_LATE_TRX_DEBIT_PROCESSING_CODE array is the processing code for these debit transactions. Note: Only the first value in the array is used. Example: ["004000"] |
| 506 | DELINQUENT_ACCOUNT_CLOSURE_LATE_TRX_CREDIT_PROCESSING_CODE | Credit liquidation | String array | After an account is closed for delinquency, it can still receive late transactions. The Pismo platform creates offsetting transactions to settle these. If a late debit transaction is received, the platform creates a credit transaction to settle it. The first value in the DELINQUENT_ACCOUNT_CLOSURE_LATE_TRX_CREDIT_PROCESSING_CODE array is the processing code for these credit transactions. Note: Only the first value in the array is used. Example: ["004000"] |
| 507 | DELINQUENCY_BUCKETS_PAYMENTS_TRANSACTIONS_TYPES | Get delinquency bucket | Integer array | Acceptable transaction types for discharging a delinquency bucket balance. Example: [201, 200] |
| 508 | DELINQUENT_ACCOUNT_EXCLUDED_STEPS | Credit liquidation | String array | Steps to exclude from the delinquent account flow. Example: ["POST_INTEREST_ACCRUAL", "POST_INSTALLMENT_ADVANCE","POST_CREDIT_TRANSACTION","SET_CARD_AS_BLOCKED"] |
| 509 | DELINQUENT_ACCOUNT_FINAL_ACCOUNT_STATUS | Credit liquidation | String array | Final account status for a delinquent account flow. Note: Only the first value in the array is used. Example: ["CANCELLED"] |
| 510 | DELINQUENT_ACCOUNT_IGNORE_ACCOUNT_STATUS | Credit liquidation | String array | Account statuses that the delinquent account flow should ignore. Example: ["STAND-BY", "BLOCKED"] |
| 511 | DELINQUENT_ACCOUNT_TRANSACTION_TYPES_SEPARATE_CANCELLATION | Credit liquidation | Integer array | Transaction types that should be canceled before account closure. Example: [502, 504] |
| 512 | PAYMENT_AGREEMENT_SIMULATION_INTEREST_CAP_ENABLED — [BETA] | Payment agreements | Boolean (true/false) | Enables or disables the automatic filtering of simulations by the interest cap. Only simulations with interest amounts below the cap are considered. Note: This parameter is still in beta and is only available in certain test environments. Contact your Pismo representative if you have questions. Example: TRUE |
| 513 | PAYMENT_AGREEMENT_SIMULATION_FIRST_INSTALLMENT_AS_DOWNPAYMENT — [BETA] | Payment agreements | Boolean (true/false) | Enables or disables using the first installment amount as a down payment. The amount is also considered in the formula for calculating the interest cap. Note: This parameter is still in beta and is only available in certain test environments. Contact your Pismo representative if you have questions. Example: TRUE |
| 514 | PAYMENT_AGREEMENT_SIMULATION_ENABLED — [BETA] | Payment agreements | Boolean (true/false) | Enables or disables the automatic simulation of invoice installment plans at the end of the program cycle. Note: This parameter is still in beta and is only available in certain test environments. Contact your Pismo representative if you have questions. Example: TRUE |
| 1000 | CHARGE_IOF_INDEPENDENTLY | Accrual generation and reversal | Boolean (true | false) | Enables or disables the generation of IOF accruals regardless of the REFINANCING configuration. That is, when enabled, it generates the IOF accrual even if the REFINANCING rate is zero. Otherwise, it follows the current behavior, where the IOF accrual is only generated if the calculated REFINANCING value is greater than zero. Note: Although this is actually a single value parameter, it's used in conjunction with a multivalue parameter (EXCLUDE_TXN_CATEGORY_CHARGE_IOF_INDEPENDENTLY), so it's included in this list for convenience. Example: TRUE |
| 1001 | CHARGE_FINE_INDEPENDENTLY | Accrual generation and reversal | Boolean (true | false) | Enables or disables the generation of FINE accruals regardless of the OVERDUE configuration. That is, when enabled, it generates the FINE accrual even if the OVERDUE rate is zero. Otherwise, it follows the current behavior, where the FINE accrual is only generated if the calculated OVERDUE value is greater than zero. Note: Although this is actually a single value parameter, it's used in conjunction with a multivalue parameter (EXCLUDE_TXN_CATEGORY_CHARGE_FINE_INDEPENDENTLY), so it's included in this list for convenience. Example: TRUE |
| 1002 | EXCLUDE_TXN_CATEGORY_CHARGE_IOF_INDEPENDENTLY | Accrual generation and reversal | Integer array | Normally, when CHARGE_IOF_INDEPENDENTLY is set to true, IOF charges are generated regardless of the refinancing total (the amount calculated for accruals of the REFINANCING type). You can exclude transaction categories from this behavior using the EXCLUDE_TXN_CATEGORY_CHARGE_IOF_INDEPENDENTLY program parameter.If the ID of a transaction category is included in the EXCLUDE_TXN_CATEGORY_CHARGE_IOF_INDEPENDENTLY array, then the IOF charge for a transaction in that category is generated only if the refinancing amount for that transaction is greater than zero. Example: [811, 812] |
| 1003 | EXCLUDE_TXN_CATEGORY_CHARGE_FINE_INDEPENDENTLY | Accrual generation and reversal | Integer array | Normally, when CHARGE_FINE_INDEPENDENTLY is set to true, fines are generated regardless of the overdue total (the amount calculated for accruals of the OVERDUE type). You can exclude transaction categories from this. behavior using the EXCLUDE_TXN_CATEGORY_CHARGE_FINE_INDEPENDENTLY program parameter.If the ID of a transaction category is included in the EXCLUDE_TXN_CATEGORY_CHARGE_FINE_INDEPENDENTLY array, then the fine for a transaction in that category is generated only if the overdue amount for that transaction is greater than zero. Example: [723, 750] |
Updated 10 days ago