Retail User Activities

The retail user logs into the e-Banking application through the Retail User ID and password created by the bank. The user is prompted to change the password after the first login. The user must change the password set by the bank and use the changed password for subsequent logins.

The Signon password should be different from the Transaction password (depends on the parameter set by the Bank whether to allow or disallow).

Once successfully logged in, the user can perform various activities. The user activities are limited to the profile set by the administrator.

After logging-in to the application, the customer details and account list is fetched online (through FI,) that is, from CIF database and account details are fetched from the Core database.

On the Dashboard screen of the retail user, the ‘Last Logged on’ time of the user is displayed. Apart from the displayed time the user also can choose the time zone of user’s choice and get the ‘Last logged on’ time in the selected time zone. The user is provided with the list of time zones to choose. The user needs to select the time zone and click Go to view the ‘Last logged on’ time in the selected time zone.

Whenever a user logs into the e-Banking application for the first time, system will force the user to change the default passwords given by the bank. However user will have the option to change the “Transaction Password” in later point of time. If the user opts to change the ‘transaction password’ at a later point of time, e-Banking application restricts the user from authenticating any transaction using the default transaction password.

User can postpone the activity of changing the transaction password even when there is a periodic password change scheduled. The system behavior will be same as the first time bypassing of change password.

Finacle e-Banking has a provision to reset the DBTS (Database Time Stamp) entries for each user. For each successful login, the DBTS count will get increased. When the DBTS count reaches the set value e-Banking application will automatically reset the count so that the user can continue login.

DBTS entry keeps a count of the number of updates done by the user which updates the CUSR table.
Any personal data update done on the user by personal profile will update the DBTS value
With any action or login performed by the user, which will update the CUSR table, the DBTS count is increased by 1.
The maximum value for DBTS will be based on the database length defined for the DBTS. Currently the database length is set to 5 in the solution. (This means the maximum value of DBTS can be 99999).
When the DBTS value reaches the set count (in this example 999999) e-Banking application will automatically reset the DBTS value to one for CUSR table.