Parameterization
This page explains in-depth some settings that can be tweaked to fit your desires and choose between various options. Each part of the Online and Mobile Banking has parametrization implemented which at any point can be modified to fit the business requirements.
The following parameters may have to be modified. Some need to be modified right after deployment, then some need to be modified for each bank, and finally, some are optional for modification.
When the parameter has the value 1 it is active or displays something, when it is 0 the setting is not active, it hides UI elements.
| No. | Name |
Modification level |
Description | Parameter Value |
|---|---|---|---|---|
| 1 | FTOS_IB_AccountType | Optional | Parameter used in FTOS_IB_fo_usersenrollment form driven flow, step 1. | INDIVIDUAL PERSON;LEGAL PERSON |
| 2 | FTOS_IB_AccTran_DefaultDaysFrom | Optional | The system displays the list of transactions in the Account Details page from the past number of days inserted here. | 90 |
| 3 | FTOS_IB_AccTran_DefaultNoTransactionsHomePage | Optional | The number of transactions displayed on the homepage. | 9 |
| 4 | FTOS_IB_afterUserMigrationURL |
Mandatory |
This is the url where the user is redirected after the process of Online User Migration. | http://mibdev.westeurope.cloudapp.azure.com/MobileBankDev_FO/Main#/page/home/index |
| 5 | FTOS_IB_BankAccount_BankName |
Mandatory |
System parameter used to mention the bank where all the bank accounts & loans are populated in the database, since from the API we cannot revert with the bank linked to the bank account/loan. | (The name of the bank) |
| 6 | FTOS_IB_BankAccountCategories |
Modified for each bank |
These are the types of liabilities a customer can have displayed in the solution for the user in Online and Mobile Banking Application. | Basic,Standard,Savings,Term Deposits |
| 7 | FTOS_IB_BankAccountCategory1 | Modified for each bank | The first bank account category. | Basic |
| 8 | FTOS_IB_BankAccountCategory2 | Modified for each bank | The second bank account category. | Standard |
| 9 | FTOS_IB_BankAccountCategory3 | Modified for each bank | The third bank account category. | Savings |
| 10 | FTOS_IB_BankAccountCategory4 | Modified for each bank | The fourth bank account category. | Term Deposits |
| 11 | FTOS_IB_BankAccountCategoryName1 | Modified for each bank | The first bank account category name. | Current Account |
| 12 | FTOS_IB_BankAccountCategoryName2 | Modified for each bank | The second bank account category name. | Current Account |
| 13 | FTOS_IB_BankAccountCategoryName3 | Modified for each bank | The third bank account category name. | Savings Account |
| 14 | FTOS_IB_BankAccountCategoryName4 | Modified for each bank | The fourth bank account category name. | Term Deposit |
| 15 | FTOS_IB_BO_ClientReportTransactions | Optional | The transaction types used in Reports and Logs to distinguish active users from passive users. | Account Balance & Details,Account Statement |
| 16 | FTOS_IB_BulkFiles_AuthRequiredStatus | Optional | The status of the bulk file. | Validated Core |
| 17 | FTOS_IB_BulkPayment_FileExtension | Optional | This parameter limits the type of file which can be imported into the system to Initiating and Authorizing a Utility Payment. The parameter value is : txt, xlx, xlxs, cvs. Only these types can be imported into the FintechOS Portal | txt|csv|xls|xlsx |
| 18 | FTOS_IB_BulkPaymentSystem |
Modified for each bank |
The system used for bulk payments. | БИСЕРА,РИНГС |
| 19 | FTOS_IB_CategoryPurpose_Letters |
|
The letters symbolizing the category purpose. | G,H,I,J,E |
| 20 | FTOS_IB_CoreBankingStatusFail | Modified for each bank | The bank can define the fail status of Core Banking when making a payment. | SettlementProcedures |
| 21 | FTOS_IB_CoreBankingStatusOperational | Modified for each bank | The status of Core Banking. | DailyProcedures |
| 22 | FTOS_IB_CountryCode | Modified for each bank | The code of the country. | BULGARIA |
| 23 | FTOS_IB_DefaultValueNewAccAddedAutomatically |
Modified for each bank |
If this parameter is true, then the checkbox in the grid Current Modifications List has the default value unchecked and the maker can check/un-check the option in the back-office, on the section tab. If this parameter is false, then the checkbox in the grid for any user has the default value checked and the maker can uncheck the field. It applies only for the new added bank accounts from the moment the parameter was changed, not the existing accounts prior to the change of the parameter. |
true |
| 24 |
FTOS_IB_DisplayOpenDepositLinks |
Optional |
This parameter hides/displays in the UI the links for the acquire of services deposits, goals, and savings. |
1 |
| 25 | FTOS_IB_DisplaySettlementTypeForSepaAndTarget | Optional | This system parameter marks whether to display the settlement type for the types of payments SEPA and Target2. | 1 |
| 26 | FTOS_IB_EnableServerSideLogs |
Modified for each bank |
This parameter marks whether or not the server-side log are active. | 1 |
| 27 |
FTOS_IB_ExchangeRateTypeBuyNonCash |
Modified for each bank |
It is applicable for all transfers with conversions (including foreign exchange operations). |
buyNonCash |
| 28 |
FTOS_IB_ExchangeRateTypeFixRate |
Modified for each bank |
It is the exchange rate type |
fixRate |
| 29 |
FTOS_IB_ExchangeRateTypeSellNonCash |
Modified for each bank |
It is applicable for all transfers with conversions (including foreign exchange operations). |
sellNonCash |
| 30 | FTOS_IB_DisplaySettlementTypes_SWIFTOnly | Mandatory | The parameter configures the behavior of the settlement type attribute in a payment. When the value is 1, settlementType is displayed for SWIFT payment type. When the value is 0, settlementType is displayed for SWIFT, SEPA Credit and TARGET2 payment types. | 0 |
| 31 | FTOS_IB_FO_AccountCardColors | Optional | Chanage the colours to match the banks branding. | #EC7423,#F5A50C,#4A849C,#909090 |
| 32 | FTOS_IB_FO_AccountCardColors_WL | Optional | It marks the colours for the whitelabel Online and Mobile Banking application. | #1952CA,#009366,#009EBA |
| 33 | FTOS_IB_FO_ExchangeRateItems | Optional | The list of currencies used in Exchange Rates. | EUR,CHF,JPY,USD,CAD,PLN,GBP,RON,SEK |
| 34 | FTOS_IB_FO_LoanCardColors | Optional | It marks the colours for the cards on the homepage. | #E74C3C,#D36426,#C19B2B,#923D00 |
| 35 | FTOS_IB_FO_LoanCardColors_WL | Optional | It marks the colours for the cards on the homepage for the whitelabel product. | #002ABD,#21007D,#4F006B |
| 36 | FTOS_IB_FXPaymentReason | Optional | It populates the field paymentReason |
FX transaction |
| 37 | FTOS_IB_GDPRDaysAfterInactive |
Mandatory |
This parameter marks the number of days to compare the date when the last line |
100 |
| 38 | FTOS_IB_GetTemplate_Count |
Optional |
This parameter holds the number of templates to be displayed. | 6 |
| 39 | FTOS_IB_IntegrationMock | Optional | Marks whether the integration mock is active or not. | 0 |
| 40 | FTOS_IB_IntegrationMock_MassPayment_CoreStatus | Optional | The status of the mass payment in Core Banking. | Validated Core |
| 41 | FTOS_IB_IntegrationMock_MassPayment_FTOSStatus | Optional | The status of the mass payment in the Innovation Studio. | SentToCorebanking |
| 42 | FTOS_IB_IntegrationMock_Payment_CoreStatusCode | Optional | The status of the payment in Core Banking. | ACSC |
| 43 | FTOS_IB_IntegrationMock_Payment_FTOSStatus | Optional | The status of the payment in the Innovation Studio. | SentToCorebanking |
| 44 | FTOS_IB_IntegrationMockLogs | Optional | This parameter marks the usage of the logs. | 0 |
| 45 | FTOS_IB_IntegrationsVCS_EnableLogs | Optional | Enables or not the logs. | 1 |
| 46 | FTOS_IB_InternalBankAccountIndicator |
Optional |
This parameter has the value a substring of the IBAN to be checked in the beneficiary bank account. If it is a match, then the account is intra-bank. If this substring is matched in the beneficiary IBAN on positions 4 to 7, the API integration is called and it is considered that the account is internal. | Bank Identifier |
| 47 | FTOS_IB_IsWhiteLabelMode |
Mandatory |
This marks whether or not the environment is the white-label product. | false |
| 48 |
FTOS_IB_isEnabledCustomerSyncAPI |
Optional |
This parameter enables the syncronization of data for the search for the user/customer either in data from C360 (true) or in the FintechOS database |
true |
| 49 | FTOS_IB_KeepSigningOrder | Optional | Marks whether the signing order is valid or not. | 0 |
| 50 | FTOS_IB_LoanCategories | Modified for each bank | This parameter holds the types of loans. | Personal loans,Overdrafts,Credit Cards,Mortgages |
| 51 | FTOS_IB_LoanCategory1 | Modified for each bank | The first loan category. | Personal loans |
| 52 | FTOS_IB_LoanCategory2 | Modified for each bank | The second loan category. | Overdrafts |
| 53 | FTOS_IB_LoanCategory3 | Modified for each bank | The third loan category. | Credit Cards |
| 54 | FTOS_IB_LoanCategory4 | Modified for each bank | The fourth loan category. | Mortgages |
| 55 | FTOS_IB_Loans_ApprovedStatus | Optional | The status of a approved loan. | Одобрен |
| 56 | FTOS_IB_maxRetryMinutesMigration | Optional | This parameter holds the value of the maximum number of retries a user can launch to migrate to the new Online and Mobile Banking as described in Online User Migration. | 15 |
| 57 |
FTOS_IB_NoRetriesInstantPymts |
Optional |
The number of times the system sends to Core Banking an instant payment during the weekend. |
3 |
| 58 | FTOS_IB_OrganisationIdentificationIdSWIFT | Optional | This parameter is used for populating the value in table FTOS_IB_FCYPaymentExt, attribute organisationIdentificationId. | SWIFT |
| 59 | FTOS_IB_OTPCodeSeparators |
Modified for each bank |
These are the code separates for the OTP sent. | ["code is ", "OTP = "] |
| 60 | FTOS_IB_Payment_AuthRequiredStatus | Optional | The status of the payment when the authorization is required. | AuthorizationRequired |
| 61 | FTOS_IB_Payment_MandatoryUserTransactionType | Optional | This parameter marks the obligatory type of transaction a user must have to initiate a payment. | Account Balance & Details |
| 62 | FTOS_IB_PaymentBankAccountCategories |
Modified for each bank |
This parameter is used in the field when creating a payment. | Basic,Standard,Savings |
| 63 | FTOS_IB_PaymentStyle |
Optional |
This parameter triggers how the payment is done:
|
createAndConfirm |
| 64 |
FTOS_IB_PaymentQueueIgnoreInterval |
Modified for each bank |
Interval of time before current date when job will ignore the payments expressed in miliseconds (1 minute = 60.000 ms). Hint: this should be smaller than the period when the job is run. (e.g., if the job runs every 5 minutes, this parameter should be < 300.000) |
59000 |
| 65 | FTOS_IB_ProcessQueueItemOnExecutionDate | Optional | This parameter marks whether the item is processed on the date it was executed. | true |
| 66 | FTOS_IB_ServerStatus_AccountDate | Optional | This parameter simulates the date of Core banking system. If it is empty, it takes the values of the actual API. | |
| 67 | FTOS_IB_ServerStatus_Status |
Modified for each bank |
The status of the server. | DailyProcedures |
| 68 | FTOS_IB_ShowSWIFTForLCY | Optional | Marks whether the SWIFT schema is displayed for local currency payments. | 0 |
| 69 | FTOS_IB_SMSNotification | Optional | The body of the SMS. | Vashiyat kod za dostyp do sistemata e {otp} |
| 70 | FTOS_IB_TimeZoneOffset |
Modified for each bank |
The value is the GMT for this solution. Change this value to 2 for no summer time or the value to fit your country. | 3 |
| 71 | FTOS_IB_updateExecutionDate |
Optional |
This parameter updates the execution date of a payment with the current banking date and storing the initial execution date of the payment. It is used in the authorization step of a payment, when the execution date is passed. | YES |
| 72 | FTOS_IB_UserSignMaxRetryNo | Optional | The number of times the user can try to sign using the OTP code. | 5 |
| 73 | FTOS_IB_Utility_bigInterval | Optional | This parameter marks one minute. | 60 |
| 74 | FTOS_IB_Utility_MandatoryUserTransactionType | Optional | The obligatory type of transaction a user must have to initiate a utility payment. | Domestic Payments |
| 75 | FTOS_IB_Utility_numberOfAttemptsEasyPay | Optional | The number of tries the system allows for the Easy Pay integration. | 5 |
| 76 | FTOS_IB_Utility_smallInterval | Optional | This parameter marks the number of minutes. | 2 |
| 77 | FTOS_IB_Utility3rdPartyPaymentProvider | Optional | The name of the third-party payment provider. | EasyPay |
| 78 | FTOS_IB_UtilityPaymentContract_AuthRequiredStatus | Optional | The status required for a utility payment. | AuthorizationRequired |
| 79 | FTOS_IB_UtilityReverseBillTimeout | Optional | This is the timeout for the utility reverse bill. | 15 |
| 80 | FTOS_IB_UtilityTransactionPaymentType | Optional | This is the type of utility transaction payment. | D |
|
81 |
isEnabledCustomerSyncAPI |
Mandatory |
If the value is true, then the system calls the API to syncronize data from C360 when searching users/customers. If the value is false, then the system skips the API sync and finds the data in FTOS database. |
TRUE |
|
82 |
maxNoRetriesQueueing |
Optional |
The maximum numbers of retries of a payment that does not have sufficient founds. |
15 |
|
83 |
queueTransactionIdPrefix |
Mandatory |
This is the prefix used for the transcationID within the queue. |
VCS_DEV |
User Enrollment
System parameter: FTOS_IB_CountryCode
| Field | Value |
|---|---|
| Name | FTOS_IB_CountryCode |
| Parameter Value | BULGARIA |
System parameter: FTOS_IB_GDPRDaysAfterInactive
This parameter marks the number of days to compare the date when the last line in FTOS_IB_UserXCustomer became inactive (it must be before the currant date minus the parameter value), to decide if the records should be anonymized.
| Field | Value |
|---|---|
| Name | FTOS_IB_GDPRDaysAfterInactive |
| Parameter Value | 100 |
System parameter: FTOS_IB_maxRetryMinutesMigration
This parameter holds the value of the maximum number of retries a user can launch to migrate to the new Online and Mobile Banking as described in Online User Migration.
| Field | Value |
|---|---|
| Name | FTOS_IB_maxRetryMinutesMigration |
| Parameter Value | 15 |
Payments
System parameter: FTOS_IB_InternalBankAccountIndicator
This parameter has the value a substring of the IBAN to be checked in the beneficiary bank account. If it is a match, then the account is intra-bank, and the integration API is called in order to get the account currency.
| Field | Value |
|---|---|
| Name | FTOS_IB_InternalBankAccountIndicator |
| Parameter value | This value varies from bank to bank. It is a part of the IBAN. |
System parameter: FTOS_IB_PaymentBankAccountCategories
This parameter is used in the field when creating a payment.
| Field | Value |
|---|---|
| Name | FTOS_IB_PaymentBankAccountCategories |
| Parameter value | Basic,Standard,Savings |
System parameter: FTOS_IB_ServerStatus_AccountDate
This parameter simulates the date of Core banking system. If it is empty, it takes the values of the actual API.
| Field | Value |
|---|---|
| Name | FTOS_IB_ServerStatus_AccountDate |
| Parameter value | 10/01/2021 12:00:00 PM |
System parameter: FTOS_IB_updateExecutionDate
This parameter updates the execution date of a payment with the current banking date and storing the initial execution date of the payment. It is used in the authorization step of a payment, when the execution date is passed.
| Field | Value |
|---|---|
| Name | FTOS_IB_updateExecutionDate |
| Parameter value | YES |