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.

No.	Modification level	Description
1	Optional	Parameter used in FTOS_IB_fo_usersenrollment form driven flow, step 1.
2	Optional	The system displays the list of transactions in the Account Details page from the past number of days inserted here.
3	Optional	The number of transactions displayed on the homepage.
4	Mandatory	This is the url where the user is redirected after the process of Online User Migration.
5	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.
6	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.
7	Modified for each bank	The first bank account category.
8	Modified for each bank	The second bank account category.
9	Modified for each bank	The third bank account category.
10	Modified for each bank	The fourth bank account category.
11	Modified for each bank	The first bank account category name.
12	Modified for each bank	The second bank account category name.
13	Modified for each bank	The third bank account category name.
14	Modified for each bank	The fourth bank account category name.
15	Optional	The transaction types used in Reports and Logs to distinguish active users from passive users.
16	Optional	The status of the bulk file.
17	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
18	Modified for each bank	The system used for bulk payments.
19		The letters symbolizing the category purpose.
20	Modified for each bank	The bank can define the fail status of Core Banking when making a payment.
21	Modified for each bank	The status of Core Banking.
22	Modified for each bank	The code of the country.
23	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.
24	Optional	This parameter hides/displays in the UI the links for the acquire of services deposits, goals, and savings.
25	Optional	This system parameter marks whether to display the settlement type for the types of payments SEPA and Target2.
26	Modified for each bank	This parameter marks whether or not the server-side log are active.
27	Modified for each bank	It is applicable for all transfers with conversions (including foreign exchange operations).
28	Modified for each bank	It is the exchange rate type.
29	Modified for each bank	It is applicable for all transfers with conversions (including foreign exchange operations).
30	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.
31	Optional	Chanage the colours to match the banks branding.
32	Optional	It marks the colours for the whitelabel Online and Mobile Banking application.
33	Optional	The list of currencies used in Exchange Rates.
34	Optional	It marks the colours for the cards on the homepage.
35	Optional	It marks the colours for the cards on the homepage for the whitelabel product.
36	Optional	It populates the field paymentReason for the times when the type is connected to the foreign exchange.
37	Mandatory	This parameter marks the number of days to compare the date when the last line becomes inactive (it must be before the currant date minus the parameter value), to decide if the records should be anonymized.
38	Optional	This parameter holds the number of templates to be displayed.
39	Optional	Marks whether the integration mock is active or not.
40	Optional	The status of the mass payment in Core Banking.
41	Optional	The status of the mass payment in the Innovation Studio.
42	Optional	The status of the payment in Core Banking.
43	Optional	The status of the payment in the Innovation Studio.
44	Optional	This parameter marks the usage of the logs.
45	Optional	Enables or not the logs.
46	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.
47	Mandatory	This marks whether or not the environment is the white-label product.
48	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 skipping the API (false).
49	Optional	Marks whether the signing order is valid or not.
50	Modified for each bank	This parameter holds the types of loans.
51	Modified for each bank	The first loan category.
52	Modified for each bank	The second loan category.
53	Modified for each bank	The third loan category.
54	Modified for each bank	The fourth loan category.
55	Optional	The status of a approved loan.
56	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.
57	Optional	The number of times the system sends to Core Banking an instant payment during the weekend.
58	Optional	This parameter is used for populating the value in table FTOS_IB_FCYPaymentExt, attribute organisationIdentificationId.
59	Modified for each bank	These are the code separates for the OTP sent.
60	Optional	The status of the payment when the authorization is required.
61	Optional	This parameter marks the obligatory type of transaction a user must have to initiate a payment.
62	Modified for each bank	This parameter is used in the field when creating a payment.
63	Optional	This parameter triggers how the payment is done: createAndConfirm: trigger the endpoint to create and confirm the payment. justCreate: trigger the endpoint to create a payment. simpleCreateAndConfirm: trigger the endpoint to create and endpoint to confirm the payment.
64	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)
65	Optional	This parameter marks whether the item is processed on the date it was executed.
66	Optional	This parameter simulates the date of Core banking system. If it is empty, it takes the values of the actual API.
67	Modified for each bank	The status of the server.
68	Optional	Marks whether the SWIFT schema is displayed for local currency payments.
69	Optional	The body of the SMS.
70	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.
71	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.
72	Optional	The number of times the user can try to sign using the OTP code.
73	Optional	This parameter marks one minute.
74	Optional	The obligatory type of transaction a user must have to initiate a utility payment.
75	Optional	The number of tries the system allows for the Easy Pay integration.
76	Optional	This parameter marks the number of minutes.
77	Optional	The name of the third-party payment provider.
78	Optional	The status required for a utility payment.
79	Optional	This is the timeout for the utility reverse bill.
80	Optional	This is the type of utility transaction payment.
81	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.
82	Optional	The maximum numbers of retries of a payment that does not have sufficient founds.
83	Mandatory	This is the prefix used for the transcationID within the queue.