System Administrative Transactions

Administrative Transactions

Following transactions are present on the System Administrator dashboard and in the menu:

On-boarding
(a) User Management

User Management function enables the System Administrator to onboard and manage users along with their login credentials for channel banking access. This module facilitates channel banking access to the bank’s internal users (administrators) and external users (customers).

User will get access to all the entities and clients mapped to it. Also the limit packages can get assigned once the user selects the accessible entities.

(b) Merchant Management

Merchant Management facilitates System Administrator to set up and maintain merchants using channel banking platform. This is to enable the customers to initiate merchant based payments using channel banking facility. This option allows the administrator to create / onboard new merchants, view existing merchants and modify their details, if required.

(c) Party Preferences (Through Toggle menu)
Party Preferences maintenance enables Bank administrator to define certain parameter values as per the corporate entities requirements. Following preferences can be set for a corporate party:
- Cumulative Daily/Monthly limits per transaction.
- Transaction limits for users.
- Approval flow – Parallel or Sequential or none.
- To enable Channel access or not.
- To enable Forex Deal creation or not.
- To enable a Corporate Administrator or not.
- Group Corporate Mapping.
(d) Group Corporate Onboarding
Group Corporate Onboarding maintenance enable the administrator to onboard the Group Corporate on OBAPIS in a single flow. Following steps can be followed during Group Corporate onboarding and send the same as a single approval:
- Group Corporate Profiling
- Party Account Access
- User Onboarding
- User Group
- User Account Access
- Report Mapping
- Workflow Management
- Approval Rules
Mapping of Parties belonging to different entities under a Group Corporate ID is allowed.

(e) Biller Onboarding

Using Biller Onboarding, System Administrators can create billers. The system administrator defines payment methods accepted by biller (e.g. Current and Savings Account, Credit Card, Debit Card etc.) while creating a biller. He also maintains category of the biller, full address of the biller and location/ area in which the biller operates or provides his services.

System Administrator creates billers, which are then made available to the customers to register themselves with these billers to receive and pay bills online.
Communications
(a) User Group Subject Mapping

This maintenance facilitates mapping of subjects, to user groups in the bank, to streamline communication between the bank’s users and its end customers.

Once User Groups are mapped to certain transactions or modules, users, in that group can reply to communication pertaining to the specific subject. The communication channel used is the bank’s secure mailbox.

This option allows the System Administrator to search and view existing User Group – Subject mapping, modify the existing mapping and to create a new User Group – Subject mapping.

(b) Alert Maintenance

Alerts maintenance allows the System Administrator to define required parameters for each alert that is to be sent to the banks customers.

This option allows the System Administrator to search and view existing alerts, create a new alert and modify or delete an existing alert.

(c) Mailers

Mailers are information or a messages published by the Bank, to communicate about the Banks Products, services and other information to its users. A Bank may send mailers to announce a limited period promotional offer, launch of a product or service, etc.

The System Administrator creates Mailers which are sent to specific users, parties or user segments (all Retail / Corporate / Admin) users. Mailers can be customized to reach some or all users, to be sent now or on a specific date and time, in the future.
Configuration
(a) System Configuration

Using thisoption System Administrator defines the basic components of this application which is necessary to run the application. The creating of system configuration is done at 'Day 0' configuration.

(b) System Rules

System rules are defined to set different parameters for each enterprise role. The parameters that can be set for each enterprise role (Retail or Corporate Users) are Party Mapping, Limits Check, Party Preferences Check, Account Transaction Mapping, and Approvals Check, Group Corporate Check. If these parameters are enabled, application will check for a fulfillment of the maintenances, before final processing.

E.g. if Approval check flag is enabled for ‘Corporate User’ type of enterprise role; then transactions initiated by corporate type of users will follow the approval maintenance for a party mapped to user and vice versa.

The flag ‘Group Corporate’ is applicable only for Corporate User’ type of enterprise role. This flag in System Rules screen defines the mode of corporate onboarding.

If Group Corporate flag is set ON then Bank administration will be able to onboard Group Corporate. The Group Corporate flag is enabled by default and always “ When in the Enterprise Role field user type is selected as Corporate User then the Group Corporate flag will get displayed in non editable mode.

(c) Transactions Aspects

Using this option, System Administrator can define the aspects for a transaction. Depending on the aspects defined for a transaction through this maintenance, the transaction will be available/unavailable for selection in the respective maintenance screen.

User can view the aspects for a selected transaction and also edit the aspects i.e. enable/disable the aspects for the selected transaction.

(d) ATM/ Branch Maintenance

ATM Branch Locator feature available to the bank customers enables the users to locate the bank’s ATMs/ branches available within a specific radius of his current location.

For the customers, to fetch the relevant information related to ATMs and Branches, system administrator maintains the data at their local databases. The basic details of ATMs and Branches are fetched from the core banking application, which is further enriched and stored in local database. This is a one-time activity at the time of implementation. Subsequently, as and when branches and ATMs are added, or any details regarding them updated, the administrator performs the necessary updates to the bank database.

Using this option, the System Administrator can search and view the ATM/ branch and its details (Fetched from Core Banking application) which include branch/ ATM id, branch name, address details, phone number, work timings and services offered by the bank. New ATM and branch details can also be manually added, viewed and edited.

The bank administrator can manually add new branch/ ATM details one by one, or add multiple branches / ATMs details simultaneously through file upload.

(e) Product Mapping

Product Mapping feature allows the System Administrator to map products with the channel. The business users will be able to access accounts related to the products mapped to the channel.

The System Administrator will be allowed to register the banks products to be made available to bank users for opening further accounts.

(f) User Profile Maintenance

This function enables the System/ Bank Administrator user to manage the user profile details that needs to be shown and needs to be made available for modification for Retail users. Details maintained on user profile includes date of birth, PAN card number, Aadhar number, passport number, national ID, driving license, communication address, email ID, and contact number, fax number, etc.

In a multi entity scenario, Administrator can do this setup for each entity by selecting the entity.

(g) First Time login

Using this option System administrator can configure the steps for banks business users to follow when the first-time login into the application. This step includes accepting Terms and Conditions, Setting up Security Questions, My profile, and limit information. The first-time login events are configurable at the Entity Level. Bank Admin would be able to define the mandatory and skippable steps for each entity. Post first-time login to the application, the system will check the configured steps for the logged-in entity and will be displayed to the user.
Security
(a) Authentication

Passwords are the most common form of authentication used in the world today. But passwords are commonly forgotten and easily compromised. Two-factor authentication (2FA) adds an extra layer of security by requiring users to use two different authentication factors to verify user’s identity.

The two step verification or Two Factor Authentication is an extra layer of security that is a subset of "multi factor authentication" that requires not only a password and username but also something that user has or something user knows or something they are e.g. tokens, OTP, biometrics etc. Using a Two Factor Authentication process can help to lower the number of cases of identity theft on the Internet, as well as phishing via email. For security reason authentication is used by user (Retail/ Corporate) while performing transactions through internet channel.

The two factor Authentication requires two different kinds of evidences before executing any transaction successfully. This option enables the system administrator to maintain authentication pattern for each transaction of a specific user segment.
The types of two factor authentication used in the application are as follows:
- Security Question
- Soft Token
- One Time Password (OTP)
(b) Security Question Maintenance

Application allows the System Administrator user to set up security questions, which will then be used as another layer of security (Over and above the Login credentials), before a user (Retail/ Corporate) can complete transactions through the internet channel.

Through the Manage Security Questions functionality, the administrator user can create and modify security questions that need to set and answered by user for completing any transaction. Administrator can add the security questions, if required.

(c) Password Policy Maintenance
Password policymaintenance enables System Administrator to define password parameters for users. Using this option System Administrator create, view and edit password policy for different user role/segments (Admin, Retail, and Corporate). Password policy maintenance contains following sections:
- Password Validators: This section contains the validations for a password. The validations include minimum and maximum length of the password, allowed characters in a password, repetitive and successive characters allowed, details to be excluded in the password like, date of birth, first and last name, user ID and party ID, and bank defined restricted passwords. User can also define number of successive incorrect attempts allowed, and number of previous password disallowed.
- Password Expiry Parameters: This section contains details about password expiry period, first password expiry period, and whether to force user to change password if there is a change in password policy (so that users can change their password as per the new password policy).
(d) Security Keys (Through Toggle menu)

Security key includes:

Password Encryption and Decryption with Public and Private Key Pairs:

Encryption and decryption allow communication between two parties to disguise information. The sender encrypts information before sending it and the receiver decrypts the information after receiving it. While in transit, the information is encrypted to ensure that it is protected from an intruder.
- Public and Private key pair helps to encrypt information that ensures sensitive data is protected during transmission. Whatever is encrypted with a Public Key can only be decrypted by its corresponding Private Key and vice versa.
- JWT Encryption Key: A JSON web token is a JSON object to represent a set of information. On sign in, user is authenticated and JWT token is generated. This JWT is subsequently passed to make API calls. To keep sensitive information hidden from the bearer (client) or third parties, JWT should be encrypted. A single key can be used to encrypt the data, if the JWT is encrypted with the key then the data can be decrypted using the same key.
Payments
(a) Payee Restrictions

Payee Restriction Set up maintenance allows System Administrator to restrict the number of payees that a retail user can create for each payment network per day.

System Administrator can also restrict the total number of payees irrespective of payment network that the retail user can create per day.

This option allows the administrator to create payee restriction maintenance, View and Edit existing maintenance.

(b) Biller Category Maintenance

System Administrator creates new biller categories and map it to the billers. E.g. administrator can create biller category as ‘Insurance’ and use it as Biller Category when creating billers related to insurance.

The System administrators can change the order of the categories as per their priority by dragging the categories. In the business user screen, these categories appear in the same order for selection to the customers, as defined by the administrators.

(c) Forex Deal Maintenance

Using Forex Deal Maintenance option, System Administrator can maintain currency pair. The maintained currency pairs are made available to corporate users to book deals and utilize those while making payments. Based on the treasury system, timer window can also be set for each currency pair so that the deal expires after the setup time, which helps corporate user to get the latest rate possible.
Personal Finance
(a) Spend Category Maintenance

Using this option, the System Administrator can maintain the spend categories. Spend Category maintenance allows the administrator to create, modify or expire categories under which user can map expenses.

(b) Goal Category Maintenance

Goal Category maintenance allows the System Administrator to create, modify or expire goal categories. This maintenance is done only for Retail users and is not applicable to corporate.
The System Administrator created categories are linked with a product which will decide the other key parameters which will govern the Goal category. These parameters could be:
- Goal Amount Range ( Minimum and Maximum Value)
- Interest Rate Offered
- Tenure Range ( Minimum and Maximum)
The System Administrator can search and view goal categories, create a new goal category, and modify an existing goal category.

(c) External Bank Maintenance

The account aggregation feature empowers customers to view information of financial accounts that are external to OBAPIS, in addition to the customer’s OBAPIS accounts. This feature also provides the customer with a consolidated view of accounts, net worth and recent transactions, across OBAPIS and external bank accounts.

To enable a retail user to access external bank accounts, and aggregate accounts with OBAPIS, the system administrator has to perform External Bank Maintenance.
Authorization and Access Controls
(a) Touch Points

Touch Points are different channels/ medium through which transactions or inquiries can be performed in OBAPIS. These can be created or modified under this section.

Touch Points in OBAPIS are of type ‘Internal’ and ‘External’. Internal Touch Points are defined as part of Day 0 definition whereas External Touch Points are typically third party applications that can be defined by the System/ Bank Administrator as part of onboarding in OBAPIS.

(b) Touch Points Groups

Touch Points are different channels e.g. Internet, Mobile, SMS, Third Party applications etc. through which the OBAPIS services can be accessed. This maintenance enables the System Administrator user to group two or multiple touch points together for the purpose of defining common limits for a transaction accessed from any touch point grouped together.

(c) Role Transaction Mapping

This function enables System Administrator to create Application Role and transaction mapping to application roles will be done for Touch Points. Administrator can create the application roles for the User Segments (Retail/ Corporate/ Administrator) and map the transactions to the application roles for internal as well as external touch points. The benefit of mapping the transactions on a touch point is that the Bank can control transaction access at each touch point.

(d) Entitlements

Entitlements are the transactions that the user can perform. Each Entitlement is linked to a single or group of resources.

Using this transaction user can view and edit the services and UI components linked to an entitlement for different actions i.e. Perform, Approve, and View.

(e) User Segment Maintenance

In order to offer appropriate product and services to the customers, banks can employ some method of segmentation. Banks can group customers into different segments based on different attributes of the customer; it could be demographic information, geographical information, behavioral information etc.

Banks can have different communication mailers, authentication mechanisms transaction limits and branding aspects based on customer segmentation.

User segment maintenance screen, allows the system administrator to create new segments and subsequently use these segments to define specific maintenances at user segment level. Limits can also be defined specific to a user segment. Within each user segment, limits package can be associated to different touch points.
Limits
(a) Limit Definition

Limits are defined by the bank to set up amount and duration based restrictions on the transactions that can be carried out by the user.
As part of Limits Definition maintenance, the System Administrator can define:
- Transaction Limits: It is the initiation limit with minimum and maximum amount, defined typically for a user with role ‘Maker’.
- Cumulative Limits: It is the collective transaction amount limit for all the transactionsthat can be performed during a day and maximum number of transactions in a day.
- Cooling Period Limits: It is the time set by the bank during which fund transfer is not allowed to a newly added payee.
This option allows the System Administrator to search and view limits, create limits and edit / delete existing limits.

(b) Limits Package Management

As part of the Limits Package definition, the created limits can be mapped to relevant transactions and/or roles.

The Limits Packages once created can be associated at User Level, Party Level and Role Level at an touch point level.

This option allows the System Administrator to search and view Limit Package, create a new Limit Package, and edit / delete existing Limit Package.

(c) Transaction Group Maintenance (Through Toggle menu)

Transaction group maintenance enables the System Administrator user to create and maintain group of transactions. Administrator can maintain a transaction group for the purpose of defining consolidated transaction limits. Once limits are assigned at transaction group, these limits acts as collective limit for selected transactions in a group.

(d) User Limits

This option allows the System Administrator to view the current available and utilized limits of specific retail user and also can modify (increase or decrease) the limits as per the requirement.

The user limits can be set for specific transaction level or at transaction group level or for a specific channel or for a group of channels.

The different types of limits are as follows:
- Daily Count- Permitted number of transactions in a day
- Daily Amount- Cumulative amount of transactions in a day
- Monthly Count- Permitted number of transactions in a month
- Monthly Amount- Permitted number of transactions in a month
Templates
(a) Service Request Form Builder

Service Request Form Builder transaction allows the system administrator to define service requests by defining its attributes and by building the form (Request page that should be available to business user) which are then available for Retail users for creating a new Service Request.

(b) Feedback Template

Using this option, the System Administrator can maintain the feedback templates by defining the feedback question, selecting the rating scale, adding new questions along with new options, selecting the transactions for which feedback capture needs to be enabled.

The administrator can also decide whether an additional question is to be asked for a scale weight and select the applicable options for the question.

(c) SMS and Missed Call Banking
Using this option, the System Administrator can maintain the sms and missed call templates. The templates can be defined as:
- SMS: You can set the template / format of the message, which the account holder will be sending to the bank to receive the information in a specified format.
- Missed Call: You can set the template / format the account holder will receive, once he / she gives a miss call on the specified phone number.
(d) Manage Brand

Banks can have varied requirements with regards to the theme and for look and feel of the application.

Manage Brand is an administrative maintenance that allows the System Administrator to define the preferred theme for the application.

There is a list of categories on the left of the screen to choose from. System administrator can click and navigate the categories to upload their bank logo, select the preferred colors of the headers, back ground, Font, label, buttons etc. System administrator can also set the font style and font size.

(e) Dashboard Builder

Dashboard Builder is an administrative maintenance that allows the System Administrator to create and configure dashboard templates for Retail and Corporate users.

System Administrator can configure new dashboards by dragging and dropping the desired widget at desired location in template. And also can add and edit rows and columns while configuring new dashboard to add more widgets. Facility is also provided to search, view, edit and delete the configured dashboards.

These configured dashboards are responsive and can adapt to any type device that Bank wants to enable it to the customers’ i.e. desktop, mobile and tablet. System allows the user to design new template and preview on different types of devices before enabling it.

The administrator can define multiple dashboards with the various attributes/ widgets. Further these templates can be mapped to the user segment, party or even to a specific user.
Controls & Monitoring
Transaction Blackout

The System Administrator can maintain a transaction blackout, for a period, when transaction/s are not accessible to users of the bank’s retail and corporate or even to Bank administrators, for a preset time period.

The administrator may use the time, when a transaction is blacked-out, to do necessary maintenances.

Through this maintenance, the System Administrator can create a transaction blackout, User can search and view existing blackouts, and modify these if required. User can delete future dated blackouts.

(b) Transaction Working Window

A working window is maintained, by the System Administrator for each transaction for which a value date is applicable for processing. In order to enable such transactions on the channel, it is mandatory to define a working window for all the days of a week as Day 0 Maintenance. By performing this maintenance, the System Administrator defines the channel working window for each day of the week for a specific transaction.

Further, administrator can also define the processing pattern if the transaction is initiated by customers after the window is closed. Through this maintenance, the System Administrator can create a working window for a transaction, and also can create an exception to the normal window. User can search and view existing maintenances, and modify these if required.

(c) Audit Log

Audit log is set of records that provide information about operations performed in the application and details of the user who has performed it along with date and time when it was performed. The System Administrator can search and view the Audit Log.

(d) Feedback Analytics

Using this option, the System Administrator can analyze the feedback for different transactions. System Administrator can view top and bottom three transactions based on average customer review or he can search for individual transactions for a selected time period. Feedback Analytics gives the bank a quick analysis of the feedback information collected. The analytics covers information the average of feedback ratings transactions have got, trends in how the average ratings have changes, the top and bottom transactions in terms of ratings etc. The analytics helps banks in quickly identifying the pain points in customer journeys in the system points out the specific areas for improvement and action.

Using this option, the System Administrator can analyze the feedback given by users of the system.

(e) Relationship Mapping

Customer Relationship Maintenance enables the System Administrator to set up the transaction access logic for Bank’s retail customers from Digital Banking Platform based on their account - mode of operation or relationship.

E.g. If a customer relationship (Mode of operation) is ‘Either or Survivor’, provide an access of all transactions whereas, if a customer relationship (Mode of operation) is ‘Jointly’, provide an access of all Inquiries and restrict all financial transactions from Digital Banking Platform. Such account and transaction access rules can be set up by the System Administrator using ‘Relationship Maintenance Module’.

(f) Relationship Matrix

Relationship Matrix maintenance allows the System Administrator to define the transaction access based on the account relationships. Administrator can enable or disable each transaction for each relationship code. OBAPIS first checks if the transaction is enabled in a role attached to a user and then if it is enabled in relationship matrix. If both the conditions are satisfied, an access of a transaction and of an account is provided to the user.

Additional options accessible via Menu

Access Management
Resource Access

(a) Party Resource Access

As part of Resource Access Management, administrator can define access on resources other than account like Remitter List from Virtual Account Management for a Corporate Party.

(b) User Resource Access

As part of Resource Access Management, administrator can define access on resources other than account like Remitter List from Virtual Account Management for a specific corporate user.
Approvals
(a) Workflow Management

Approval workflows are created to support requirements where multiple levels of approval are required in a specific sequence for a transaction/maintenance. Each workflow can be configured to have up to 5 levels of approval with a specific user or a user group configured at each level.

System Administrator can search and view approval workflows maintained and create new workflows. As a part of creating workflows, user can add various levels of approvals and map users or user groups to each level. User can also modify workflows maintained.

(b) Rules Management

The Administrator, can set up rules for approvals. Applying a rule makes the requirement for an approval more customized. For instance, through this screen, the bank administrator can create a rule, so that all administrator maintenances initiated by a certain user-group, always require approval.
Reports
(a) Report Generation

Using this option, the System Administrator, can generate various adhoc reports. Application provides an option to generate reports using Oracle Analytics Publisher and / or by using an internal application.

(b) My Reports

On accessing ‘My Reports’ menu, the System Administrator, can view the last 10 reports generated with the respective report status. He can choose to search a specific report using the search criteria or can opt to view/ download detailed report.

(c) User Report Mapping

The user report mapping maintenance allows the Bank Administrators to map the report or set of reports to a specific corporate user. The corporate users can generate and view the reports which they have an access to.

Bank administrator searches a corporate user based on the party id and view the reports mapped to him, he can also un-map the reports from specific corporate user so that access of the specific report/ s can be removed to that corporate user.

The System Administrator can also map the accounts of primary and linked parties for which the reports can be generated by a corporate user, so that corporate user can generate the report only for the accounts mapped to him.
File Upload
(a) File Identifier Maintenance

System Administrator, can create file identifiers (FI) for a corporate entity. A File Identifier is always mapped to a specific single file template. It permits configuration of corporate preferences like approval type (file level/ record level) for a particular type of file. This is a pre-requisite for the File Uploads functionality, for a corporate.

(b) User File Identifier Mapping

Through this option Administrator, can map a file identifier to a user to grant access rights to the user, for this specific file type. This maintenance enables a user to upload a specific file, approve the uploaded file and view its status. System administrator can map / un-map file identifiers to a User. Further, user can enable or disable the sensitive data check. This is a pre-requisite maintenance, for the File Uploads functionality, for a corporate.

(c) File Upload

This option allows the System administrator user to upload the files containing EBPP Billers. Billers uploaded will be available for retail users to register and make online bill payment & pre-paid recharge transactions.

(d) Uploaded File Inquiry
Through this option the user can view the Billers file uploaded and their status.
- The search can be filtered on various parameters like status and file reference ID.
- The user can track the status of the file and if there is an error in the file, he / she can download the error file to arrive at the exact reason for error.
- For files in the ‘Processed’ status, the user can download Response file, to vet status of processing (in the host) for each record, of the file.
- The user can track file history and also check Individual record details.
OAuth
(a) Identity Domain Maintenance

The Identity Domain corresponds to the notion of a tenant and each identity domain corresponds to an identity store. All artifacts such as resource server and client needs to be created under an identity domain.

As part of the Identity Domain definition, Identity store as well as token settings can be defined.

Currently only ‘Embedded LDAP’ i.e. DB Authenticator as Identity Store is supported.

(b) Resource Server Maintenance

The resource server is the server that contains the user's information that is being accessed by the third party application and handles authenticated requests after the application has obtained an access token.

Resource Server is always associated to one Identity Domain. Through this maintenance, the administrator can define scopes for the resource server. Scopes are transactions or inquiries that are provided to the client so that the TPP/client can transact or inquire on behalf of the customer with an access token provided the customer has provided consent to the TPP.

(c) Client Maintenance

Clients are Third Party Provides (TPPs) that can access information from the resource server on behalf of the user provided the user has provided consent to the TPPs. As part of this definition, the administrator can define client details i.e. client ID, client name, scopes, redirect URLs etc.
Others
(a) User Group Management

The System Administrator, can create administrator user groups with two or more users. User can search and views already maintained groups, and also modify these. The maintained administrator user groups are used for further maintenances like – User Group Subject Mapping or while creating approval rules.

(b) Print Password

When a new user opens an account in the bank and registers for internet banking, the bank sends the printed password along with some other documents like Welcome letter, Terms & Conditions document and applicable promotional offers to the registered user via courier or post. This screen allows the Bank Administrator to print the password along with these documents for new users as well as for existing users who have requested for reset password.

(c) User Alerts Subscription

The System Administrator, can subscribe users to mandatory alerts, through this option. In addition, Retail and Corporate users of the bank, can subscribe to alerts, and choose whether they want alerts delivered through Email, SMS or in their secured mailbox. The bank administrator processes the subscription request, received from customers. (For non-mandatory alerts).

(d) Request Processing

Service requests allows the System Administrator to search and view all the service requests that have been initiated by the Bank customers and are available with various statuses like Open, Completed and Rejected. Bank Administrator can search the service requests with specific search criteria and can update the status of open service requests.

(e) User Help Desk

This option enables the Administrator to create business user's session and perform the transaction requested by business user if he has forgotten his internet banking password or is unable to perform a transaction using his internet banking.

To authenticate the user, system will send an OTP to the customer and the same OTP needs to be communicated to the administrator user so that he can enter it on the screen to create user’s session.

(f) Message Maintenance

Using this option, System Administrator can inquire the existing Error Messages defined in the system for an OBAPIS error code. It also allows you to modify the text defined for a message code for a particular Language.

(g) Group Corporate Alert Subscription

Using this option the System/Bank Administrator can subscribe alerts at the Group Corporate level for selected events. The Bank Administrator subscribes the Corporate Party associated with Group Corporate to alerts, delivered through Email, SMS, through push notification or in their on-screen mailbox. This functionality is applicable for non-mandatory alerts.
Notifications
The notification section allows the System Administrator user to view last ‘N’ number of notifications sent by the bank. Click View All to view all the notifications sent by the bank.
Note:
1. If the setup requires an approval workflow, it will be initiated. Once approved by the required number of approvers, the maintenance will be effective.
2. If the setup does not require an approval workflow or is self / auto approved, the maintenance will come into effect on confirmation.