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 Optional

When 1 (true), transaction history endpoint will be called sequentially for each account, merge results and order chronologically.

When 0 (false), the system displays the transactions for only one account.
5 Mandatory This is the url where the user is redirected after the process of Online User Migration.
6 Mandatory It sets the default exchange rate type to be used with the approval identification process (for comparing security profile limits).
7 Optional

YES/NO applicable for all foreign currency payments with request Create and confirm foreign currency transfer for all editable fields on the Make a payment form to contain Cyrillic characters.

If no, the system displays a message: Only Latin characters allowed because the core banking system rejects the payment.
8 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.
9 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.
10 Modified for each bank The first bank account category.
11 Modified for each bank The second bank account category.
12 Modified for each bank The third bank account category.
13 Modified for each bank The fourth bank account category.
14 Modified for each bank The fifth bank account category.
15 Modified for each bank The sixth bank account category.
16 Modified for each bank The seventh bank account category.
17 Modified for each bank The eighth bank account category.
18 Modified for each bank The first bank account category name.
19 Modified for each bank The second bank account category name.
20 Modified for each bank The third bank account category name.
21 Modified for each bank The fourth bank account category name.
22 Optional The transaction types used in Reports and Logs to distinguish active users from passive users.
23 Modified for each bank The name of the Transaction Type that is needed in order to authorize payments with isBudget = 1.
24 Optional The status of the bulk file.
25 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
26 Modified for each bank The system used for bulk payments.
27   The letters symbolizing the category purpose.
28 Modified for each bank The bank can define the fail status of Core Banking when making a payment.
29 Modified for each bank The status of Core Banking.
30 Modified for each bank The code of the country.
31 Modified for each bank The default role attached to the system user which is created automatically via the Create and Activate a User custom flow.
32 Modified for each bank

Redirection URI after the automatic creation and activation of a user.

Format: '/Main#/entity/*entityName*/list'.

If left empty, it will redirect to ebs.getBaseUrl().
33 Mandatory The exchange rate types used for the two step transformation for exchange with currencies different than local currency. Separte the values using a comma.
34 Modified for each bank This parameter marks whether the "Redo Payment" functionality is available to the users both in List of Orders and Transaction History. If the value is 0, the button is displayed only in list of orders. If the value is 1, button is also be displayed in both, including transaction history.
35 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 tabBack-Office Administration. 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.
36 Optional This parameter hides/displays in the UI the links for the acquire of services deposits, goals, and savings.
37 Optional This system parameter marks whether to display the settlement type for the types of payments SEPA and Target2.
38 Optional This parameter changes the behavior for the Redo Payment. If the value is 0, button is displayed in list of orders. If the value is 1, the button is displayed in transaction history.
39 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.
40 Modified for each bank This parameter marks whether or not the server-side log are active.
41 Modified for each bank It is applicable for all transfers with conversions (including foreign exchange operations).
42 Modified for each bank It is the exchange rate type.
43 Modified for each bank It is applicable for all transfers with conversions (including foreign exchange operations).
44 Optional Chanage the colours to match the banks branding.
45 Optional It marks the colours for the whitelabel Online and Mobile Banking application.
46 Optional The list of currencies used in Exchange Rates.
47 Optional It marks the colours for the cards on the homepage.
48 Optional It marks the colours for the cards on the homepage for the whitelabel product.
49 Optional It populates the field paymentReason for the times when the type is connected to the foreign exchange.
50 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.
51 Optional This parameter holds the number of templates to be displayed.
52 Optional This parameter selects the mechanism used for the setting of the execution date.
53 Optional Marks whether the integration mock is active or not.
54 Optional The status of the mass payment in Core Banking.
55 Optional The status of the mass payment in the Innovation Studio.
56 Optional The status of the payment in Core Banking.
57 Optional The status of the payment in the Innovation Studio.
58 Optional This parameter enables the logs for the mock integration.
59 Optional Enables or not the logs.
60 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.
61 Mandatory This marks whether or not the environment is the white-label product.
62 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).
63 Optional Marks whether the signing order is valid or not.
64 Modified for each bank This parameter holds the types of loans.
65 Modified for each bank The first loan category.
66 Modified for each bank The second loan category.
67 Modified for each bank The third loan category.
68 Modified for each bank The fourth loan category.
69 Optional The status of a approved loan.
70 Optional The maximum number or emails send during the Online User Enrolment Request process.
71 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.
72 Optional The maximum number a user can retry for the process of Online and Mobile Banking Application
73 Optional The maximum number of retries a user can make to verify the email existence.
74 Optional The number of times the system sends to Core Banking an instant payment during the weekend.
75    
76 Optional This parameter is used for populating the value in table FTOS_IB_FCYPaymentExt, attribute organisationIdentificationId.
77 Optional It is the length of the -EbsAuthorization.AuthRequestSession-.
78 Modified for each bank The text for the One-Time-Password sent via SMS.
79 Optional The status of the payment when the authorization is required.
80 Optional This parameter marks the obligatory type of transaction a user must have to initiate a payment.
81 Modified for each bank This parameter is used in the field when creating a payment.
82 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.
83 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)
84 Optional This parameter marks whether the item is processed on the date it was executed.
85 Optional It marks the business workflow status in which a payment must be to be eligible for the redo functionality.
86 Optional The category used in the Inbox for the Online and Mobile Banking Application.
87 Optional This parameter simulates the date of the core banking system. If it is empty, it takes the values of the actual API. It is used for the queuing payments.
88 Modified for each bank The status of the server.
89 Optional Marks whether the SWIFT schema is displayed for local currency payments.
90 Optional The body of the SMS.
91 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.
92 Optional It is the name of the default value for the field Back-Office Administration.
93 Optional The name of the error code returned by the API that needs to be handled to display the fees.
94 Optional It is the name of the transaction report based on the culture. This is the Bulgarian name.
95 Optional It is the name of the transaction report based on the culture. This is the English name.
96 Optional It is the name of the transaction report based on the culture. This is the Romanian name.
97 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.
98 Optional The number of times the user can try to sign using the OTP code.
99 Optional The name of the user type for account holder.
100 Optional The name of the user type for representative.
101 Optional The name of the user type for SMEs.
102 Optional This parameter marks one minute.
103 Optional The obligatory type of transaction a user must have to initiate a utility payment.
104 Optional The number of tries the system allows for the Easy Pay integration.
105 Optional This parameter marks the number of minutes.
106 Optional The name of the third-party payment provider.
107 Optional The status required for a utility payment.
108 Optional The time interval after which the utility bill reverses.
109 Optional The type of utility transaction payment.
110 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.
111 Mandatory The abreviation of the local currency name.
112 Optional The maximum numbers of retries of a payment that does not have sufficient founds.
113 Optional It sets the length of time the OTP sent via SMS is valid for (measured in minutes).
114 Mandatory The prefix for the queue transaction ID.
115 Optional

The system records the number of times the user tries to insert the code in the attribute changePassRetryNo . When the value in this attribute is the same as the value of this parameter, the system displays an error message for the user to go to the branch to change the password.

When the password is changed from the back-office, the parameter FTOS_IB_changePassRetryNo is 0.