Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                

Design and Implementation of Mobile Banking System

Download as odt, pdf, or txt
Download as odt, pdf, or txt
You are on page 1of 25

CHAPTER ONE

INTRODUCTION

1.1 Background of the study

The need for information that is accurate when they are needed is one of the major problems
of management, as they are often used in the making of vital decisions. Consequently wrong
or delayed information can lead to very costly mistakes which may cost the firm or the
individual a lot thereby portraying bad or poor managerial ability.

In the financial sector, there is need for efficient, accurate and automated analysis of such
business. Transactions should be conducted in a more convenient and comfortable mood.

Hence the need for mobile banking is considered to be solution to this needs identified. The
present system of bank transactions bears a lot of negative effect to the customers,
especially to the incident that demands urgent attention.

The mobile banking system is the most modern banking system. This system was built to
perform balance checks and other banking transactions through a mobile device.

1.2 Statement of the problem

Some problems were encountered during the development of this project. The main problem
this project seeks to address includes;

i) The problem of time wastage

ii) The problem of unnecessary delays in performing banking transactions.

1.3 Aim and objectives of the study

Aim

The aim of this project is to develop a software that can support the usage of mobile devices
such as mobile phone or personal Digital Assistant for banking transactions like account
transactions, payments, credit applications and etc.

1
Objectives include:

i)To create a system that will bridge the mobile gap between big banks and small banks

ii) To enable more people have access to mobile banking facility

iii) To encourage the transition to cashless society

1.4 Scope and limitations of the study

The project is fully and working banking solution/application or software that can run on
mobile devices, capable of holding daily transactions. This project will also show the
limitations on the operation and suggest computer –aided solutions to the problems.

Limitations

Handset operability is one of the limitations of this project because there are large numbers
of different mobile phone devices and it is a big challenge for banks to offer mobile banking
solutions on any type of device.

Security of financial transactions, being executed over the air, is the most complicated
challenges that need to be addressed.

Authentication of the devices with service provider before initiating a transaction.

2
CHAPTER TWO

LITERATURE REVIEW

2.1 Mobile banking

Mobile banking (also known as M-Banking, mbanking, SMS Banking) is a term used for
performing balance checks, account transactions, payments, credit applications and other banking
transactions through a mobile device such as a mobile phone or Personal Digital Assistant (PDA).
The earliest mobile banking services were offered over SMS. With the introduction of the first
primitive smart phones with WAP support enabling the use of the mobile web in 1999, the first
European banks started to offer mobile banking on this platform to their customers.

Mobile banking has until recently (2010) most often been performed via SMS or the Mobile Web.
Apple's initial success with iPhone and the rapid growth of phones based on Google's Android
(operating system) have led to increasing use of special client programs, called apps, downloaded to
the mobile device.

2.2 A mobile banking conceptual model

In one academic model,[2] mobile banking is defined as: Mobile Banking refers to provision and
avail]ment of banking- and financial services with the help of mobile telecommunication0

devices. The scope of offered services may include facilities to conduct bank and stock market
transactions, to administer accounts and to access customized information."

According to this model Mobile Banking can be said to consist of three inter-related concepts:

• Mobile Accounting

• Mobile Brokerage

• Mobile Financial Information Services

Most services in the categories designated Accounting and Brokerage are transaction-based. The
non-transaction-based services of an informational nature are however essential for conducting
transactions – for instance, balance inquiries might be needed before committing a money
remittance. The accounting and brokerage services are therefore offered invariably in combination
with information services. Information services, on the other hand, may be offered as an
independent module.

Mobile phone banking may also be used to help in business situations


3
2.3 Trends in mobile banking

The advent of the Internet has enabled new ways to conduct banking business, resulting in the
creation of new institutions, such as online banks, online brokers and wealth managers. Such
institutions still account for a tiny percentage of the industry.

Over the last few years, the mobile and wireless market has been one of the fastest growing markets
in the world and it is still growing at a rapid pace. According to the

GSM Association and Ovum, the number of mobile subscribers exceeded 2 billion in

September 2005, and now (2009) exceeds 2.5 billion (of which more than 2 billion are GSM).

According to a study by financial consultancy Client, 35% of online banking households will be
using mobile banking by 2010, up from less than 1% today. Upwards of 70% of bank center call
volume is projected to come from mobile phones. Mobile banking will eventually allow users to
make payments at the physical point of sale. "Mobile contactless payments” will make up 10% of
the contactless market by 2010. Another study from 2010 by Berg Insight forecasts that the number
of mobile banking users in the US will grow from 12 million in 2009 to 86 million in 2015. The
same study also predicts that the European market will grow from 7 million mobile banking users in
2009 to 115 million users in 2015.

Many believe that mobile users have just started to fully utilize the data capabilities in their mobile
phones. In Asian countries like India, China, Bangladesh, Indonesia and Philippines, where mobile
infrastructure is comparatively better than the fixed-line infrastructure, and in European countries,
where mobile phone penetration is very high (at least 80% of consumers use a mobile phone),
mobile banking is likely to appeal even more. The population of the world mobile phone user has
rising to 87 percent as of January. Nigeria is rank number 10 in the world. With total number of
90,583,306 mobile phone user, with a population of 140,000,000 people which approximately 64.7
percent of the population.

2.4 Mobile banking business models

A wide spectrum of Mobile/branchless banking models is evolving. However, no matter what


business model, if mobile banking is being used to attract low-income populations in often rural
locations, the business model will depend on banking agents, i.e., retail or postal outlets that process
financial transactions on behalf telecoms or banks.

The banking agent is an important part of the mobile banking business model since customer care,
service quality, and cash management will depend on them. Many Telco will work through their
4
local airtime resellers. However, banks in Colombia, Brazil, Peru, and other markets use
pharmacies, bakeries, etc.

These models differ primarily on the question that who will establish the relationship (account
opening, deposit taking, lending etc.) to the end customer, the Bank or the
Non-Bank/Telecommunication Company (Telco). Another difference lies in the nature of agency
agreement between bank and the Non-Bank. Models of branchless banking can be classified into
three broad categories - Bank Focused, Bank-Led and Nonbank-Led.

Bank-focused model

The bank-focused model emerges when a traditional bank uses non-traditional low-cost delivery
channels to provide banking services to its existing customers.

Examples range from use of automatic teller machines (ATMs) to internet banking or mobile phone
banking to provide certain limited banking services to banks’ customers. This model is

Additive in nature and may be seen as a modest extension of conventional branch-based banking.

Bank-led model

The bank-led model offers a distinct alternative to conventional branch-based banking in that
customer conducts financial transactions at a whole range of retail agents (or through mobile phone)
instead of at bank branches or through bank employees. This model promises the potential to
substantially increase the financial services outreach by using a different delivery channel (retailers/
mobile phones), a different trade partner (telco / chain store) having experience and target market
distinct from traditional banks, and may be significantly cheaper than the bank-based alternatives.
The bank-led model may be implemented by either using correspondent arrangements or by
creating a JV between Bank and Telco/non-bank. In this model customer account relationship rests
with the bank

Non-bank-led model

The non-bank-led model is where a bank has a limited role in the day-to-day account management.
Typically its role in this model is limited to safe-keeping of funds. Account management functions
are conducted by a non-bank (e.g. Telco) who has direct contact with individual customers.

2.5 Mobile Banking Services

Mobile banking can offer services such as the following:

Account Information

1. Mini-statements and checking of account history


5
2. Alerts on account activity or passing of set thresholds

3. Monitoring of term deposits

4. Access to loan statements

5. Access to card statements

6. Mutual funds / equity statements

7. Insurance policy management

Mobile banking 3

8. Pension plan management

9. Status on cheque, stop payment on cheque

10. Ordering cheque books

11. Balance checking in the account

12. Recent transactions

13. Due date of payment (functionality for stop, change and deleting of payments)

14. PIN provision, Change of PIN and reminder over the Internet

15. Blocking of (lost, stolen) cards

Payments, Deposits, Withdrawals, and Transfers

1. Domestic and international fund transfers

2. Micro-payment handling

3. Mobile recharging

4. Commercial payment processing

5. Bill payment processing

6. Peer to peer payments

7. Withdrawal at banking agent

8. Deposit at banking agent

6
A specific sequence of SMS messages will enable the system to verify if the client has
sufficient funds in his or her wallet and authorize a deposit or withdrawal transaction at the
agent. When depositing money, the merchant receives cash and the system credits the
client's bank account or mobile wallet. In the same way the client can also withdraw

Money at the merchant: through exchanging sms to provide authorization, the merchant
hands the client cash and debits the merchant's account.

Investments

1. Portfolio management services

2. Real-time stock quotes

3. Personalized alerts and notifications on security prices

Support

1. Status of requests for credit, including mortgage approval, and insurance coverage

2. Check (cheque) book and card requests

3. Exchange of data messages and email, including complaint submission and tracking

4. ATM Location

Content Services

1. General information such as weather updates, news

2. Loyalty-related offers

3. Location-based services

Based on a survey conducted by Forrester, mobile banking will be attractive mainly to the
younger, more "tech-savvy" customer segment. A third of mobile phone users say that they
may consider performing some kind of

Financial transaction through their mobile phone. But most of the users are interested in
performing basic transactions such as querying for account balance and making bill
payment.

Future functionalities in Mobile Banking

7
Based on the 'International Review of Business Research Papers' from World business
Institute, Australia, following are the key functional trends possible in world of Mobile
Banking.

With the advent of technology and increasing use of Smartphone and tablet based devices,
the use of Mobile Banking functionality would enable customer connect across entire
customer life cycle much comprehensively than before.

With this scenario, current mobile banking objectives of say building relationships, reducing
cost, achieving new revenue stream will transform to enable new objectives targeting higher
level goals such as building brand of the banking organization. Emerging technology and
functionalities would enable to create new ways of lead generation,

Prospecting as well as developing deep customer relationship and mobile banking world
would achieve superior customer experience with bi-directional communications.

Illustration of objective based functionality enrichment In Mobile Banking

• Communication enrichment: - Video Interaction with agents, advisors.

• Pervasive Transactions capabilities: - Comprehensive “Mobile wallet”

• Customer Education: - “Test drive” for demos of banking services

• Connect with new customer segment: - Connect with Gen Y – Gen Z using games and
social network ambushed to surrogate bank’s offerings

• Content monetization: - Micro level revenue themes such as music, e-book downloads

• Vertical positioning: - Positioning offerings over mobile banking specific industries

• Horizontal positioning: - Positioning offerings over mobile banking across all the
industries

• Personalization of corporate banking services: - Personalization experience for multiple


roles and hierarchies in corporate banking as against the vanilla based segment based
enhancements in the current context.

• Build Brand: - Built the bank’s brand while enhancing the “Mobile real estate”.

2.6 Challenges for a Mobile Banking Solution

Key challenges in developing a sophisticated mobile banking application are:

8
Handset operability

There are a large number of different mobile phone devices and it is a big challenge for
banks to offer mobile banking solution on any type of device. Some of these devices support
Java ME and others support SIM Application Toolkit, a WAP browser, or only SMS. Initial
interoperability issues however have been localized, with countries like India using portals
like R-World to enable the limitations of low end java based phones, while focus on areas
such as South Africa have defaulted to the USSD as a basis of communication achievable
with any phone. The desire for interoperability is largely dependent on the banks
themselves, where installed applications (Java based or native) provide better security, are
easier to use and allow development of more complex capabilities similar to those of
internet banking while SMS can provide the basics but becomes difficult to operate with
more complex transactions. There is a myth that there is a challenge of interoperability
between mobile banking applications due to perceived lack of common technology
standards for mobile banking. In practice it is too early in the service lifecycle for
interoperability to be addressed within an individual country, as very few countries have
more than one mobile banking service provider. In practice, banking interfaces are well
defined and money movements between banks follow the IS0-8583 standard. As mobile
banking matures, money movements between service providers will naturally adopt the
same standards as in the banking world. On January 2009, Mobile Marketing Association
(MMA) Banking Sub-Committee, chaired by Cell Trust and VeriSign Inc., published the
Mobile Banking Overview for financial institutions in which it discussed the advantages and
disadvantages of Mobile Channel Platforms such as Short Message Services (SMS), Mobile
Web, and Mobile Client Applications, SMS with Mobile Web and Secure SMS.[5]

Security

Security of financial transactions, being executed from some remote location and
transmission of financial information over the air, are the most complicated challenges that
need to be addressed jointly by mobile application developers, wireless network service
providers and the banks' IT departments (clifford, 2015).

The following aspects need to be addressed to offer a secure infrastructure for financial
transaction over wireless network:

9
1. Physical part of the hand-held device. If the bank is offering smart-card based security,
the physical security of the device is more important.

2. Security of any thick-client application running on the device. In case the device is stolen,
the hacker should require at least an ID/Password to access the application.

3. Authentication of the device with service provider before initiating a transaction. This
would ensure that unauthorized devices are not connected to perform financial transactions.

4. User ID / Password authentication of bank’s customer.

5. Encryption of the data being transmitted over the air.

6. Encryption of the data that will be stored in device for later / off-line analysis by the
customer (foster, 2019).

One-time passwords (OTPs) are the latest tool used by financial and banking service
providers in the fight against cyber fraud [6]. Instead of relying on traditional memorized
passwords, OTPs are requested by consumers each time they want to perform transactions
using the online or mobile banking interface. When the request is received the password is
sent to the consumer’s phone via SMS. The password is expired once it has been used or
once its scheduled life-cycle has expired.

Because of the concerns made explicit above, it is extremely important that SMS gateway
providers can provide a decent quality of service for banks and financial institutions in
regards to SMS services. Therefore, the provision of service level agreements (SLAs) is a
requirement for this industry; it is necessary to give the bank customer delivery

Guarantees of all messages, as well as measurements on the speed of delivery, throughput,


etc. SLAs give the service parameters in which a messaging solution is guaranteed to
perform.

Scalability & Reliability

Another challenge for the CIOs and CTOs of the banks is to scale-up the mobile banking
infrastructure to handle exponential growth of the customer base. With mobile banking, the
customer may be sitting in any part of the world (true anytime, anywhere banking) and
hence banks need to ensure that the systems are up and running in a true 24 x 7 fashion. As
customers will find mobile banking more and more useful, their expectations from the
solution will increase. Banks unable to meet the performance and reliability expectations
10
may lose customer confidence. There are systems such as Mobile Transaction Platform
which allow quick and secure mobile enabling of various banking

Services. Recently in India there has been a phenomenal growth in the use of Mobile
Banking applications, with leading banks adopting Mobile Transaction Platform and the
Central Bank publishing guidelines for mobile banking operations. (Bank marketing
strategy, 2017)

Application distribution

Due to the nature of the connectivity between bank and its customers, it would be
impractical to expect customers to regularly visit banks or connect to a web site for regular
upgrade of their mobile banking application (O.M, 2017). It will be expected that the mobile

application itself check the upgrades and updates and download necessary patches (so-
called "Over the Air" updates). However, there could be many issues to implement this
approach such as upgrade /synchronization of other dependent components.

Personalization

It would be expected from the mobile application to support personalization such as:

1. Preferred Language

2. Date / Time format

3. Amount format

4. Default transactions

5. Standard Beneficiary list

6. Alerts

2.7 Mobile banking in the world

Mobile banking is used in many parts of the world with little or no infrastructure, especially
remote and rural areas. This aspect of mobile commerce is also popular in countries where
most of their population is unbanked. In most of these places, banks can only be found in
big cities, and customers have to travel hundreds of miles to the nearest bank. In Iran, banks
such as Parsian, Tejarat, Mellat, Saderat, Sepah, Edbi, and Bankmelli offer the service.
Banco Industrial provides the service in Guatemala. Citizens of Mexico can access mobile
banking with Omnilife, Bancomer and MPower Venture. Kenya's Safaricom (part of the
11
Vodafone Group) has the M-Pesa Service, which is mainly used to transfer limited amounts
of money, but increasingly used to pay utility bills as well. In 2009, Zain launched their own
mobile money transfer business, known as ZAP, in Kenya and other African countries. In
Somalia, the many telecom companies provide mobile banking, the most prominent being
Hormuud Telecom and its ZAAD service (Rashid ol, 2018).

Telenor Pakistan has also launched a mobile banking solution, in coordination with Taameer
Bank, under the label Easy Paisa, which was begun in Q4 2009. Eko India Financial
Services, the business correspondent of State Bank of India (SBI) and ICICI Bank, provides
bank accounts, deposit, withdrawal and remittance services, micro-insurance, and micro-
finance facilities to its customers (nearly 80% of whom are migrants or the unbanked
section of the population) through mobile banking. (AA Saikh, 2015)

In a year of 2010, mobile banking users soared over 100 percent in Kenya, China, Brazil
and USA with 200 percent, 150 percent, 110 percent and 100 percent respectively.[8]

Dutch-Bangla Bank (www.dutchbanglabank.com) launches the very first mobile banking


service in Bangladesh on 31 March, 2011. This service is launched with ‘Agent’ and
‘Network’ support from mobile operators, Banglalink and Citycell. Sybase 365, a subsidiary
of Sybase, Inc. has provided software solution. There are around

160 million people in Bangladesh, of which, only 13 per cent have bank accounts.

With this solution, Dutch-Bangla Bank can now reach out to the rural and unbanked
population, of which, 45 per cent are mobile phone users. Under the service, any mobile
handset with subscription to any of the six existing mobile operators of Bangladesh would
be able to utilize the service. Under the mobile banking services, bank-nominated ‘Agents’
perform banking activities on behalf of the banks, like opening mobile banking account,
providing cash services (receipts and payments) and dealing with small credits. Cash
withdrawal from a mobile account can also be done from an ATM validating each
transaction by ‘mobile phone & PIN’ instead of ‘card & PIN’. Other services that are being
delivered through mobile banking system are person-to-person (e.g. fund transfer), person-
to-business (e.g. merchant payment, utility bill payment), business-to-person (e.g.
salary/commission disbursement), government-to-person (disbursement of government
allowance) transactions (Odewale, 2018).

CHAPTER THREE
12
RESEARCH METHODOLOGY

3.1 Introduction

This chapter focuses on the procedures used in the collection of data for the study. The setting of the
study, the study design, data sources, the sampling procedures, and the data collection technique,
the instrument of data collection, the data processing and analysis are discussed. Futhermore, this
research consists of phases which will guide the system developer in the choice of
techniques that might be appropriate at each stage of the project.

These includes piece of information from:

i) Textbooks

ii) Journals

iii) Seminar papers

iv) Materials from internet.

3.2 System Investigation

System investigation is a thorough study of the present system to know its strength, faults,
benefits and weakness. The present system under study is manual hence the reason for the
automation.

The researcher’s objective is to monitor all investigations carried out in the bank and
develop a system that can take care of all important transactions to improve reliability and
speed in carrying out banking transactions (JAMES E, 2015).

 During an official examination of the fact about banking operations, it has been noticed that
the process is slow. The research work will involve sharing of resources that are important
for more efficiency in the development of mobile system for the various bank transactions.

3.3 System Design

3.3.1 Use Case Design

13
A use case diagram is a representation of a user interaction with the system that shows the
relationship between the user and the different use cases in which the user is involved (sl, 2016).
The use case is representing this system is shown below. In the development of the “Citi-Bank”
mobile app, we used Java, Firebase, Using XML (Extended markup language) for the frontend. All
such systems are characterized by the use of single processes that work together to form the system
solution.

FIGURE 3.1 : Use case Diagram of mobile banking system

3.4 System Class Diagram

A class diagram is used to show the relationships between the entities involved in the system
together with their attributes and indicate the number of occurences an entity can exist for a single
occurence of a related entity (Ele, at al, 2017 global scientific journals). The class diagram of the
system is shown below

14
FIGURE 3.2: Class diagram of Mobile banking system

3.5 System Data Model Design

Citi-bank is a mobile-based application to be run on an android device that communicates with


firebase database server. The firebase admminstrator is an online database that accepts request using
sql.

The CitiBank mobile banking system consist of one part, which is Administrator Interface

3.5.1 Data Model Design

The Administrator interface allows the administrator to create a new account, change account
password, update account details, etc.

3.5.2 Input Specification

This is an interface between the user and the system that allow the user to enter data. Data input is
generally done through the standard keyboard of the phone and clicks in case of combo boxes,
option lists. At this stage, different screen ( window or forms ) will be desgned to guide data entry
procedure. This inut variables needed for this work will be based on one category of the user:

15
3.5.3 Administrator

Login form that requires Email and password, also “create account link” that directs user to register
page, which collects : Email, full-name, password, phone number. After logging in, the dashboard
of the mobile app would be shown.

3.5.4 System Architecture

This provides an interface that restricts an unauthorised user from accessing the application, its
obective is to validate and authenticate a user before granting access to him/her based on his/her
access level (i.e Administrator) so as to access different aspect of the application, depending on
their priviledges defined by the application. It also allows new user that have being created by the
administrator to register and use application.

FIGURE 3.3: System Archiecture

FIELD NAME DATA TYPE CONSTRAINT


Account_no int(30) NOT NULL
Fullname Text(25) NOT NULL
Email Varchar(25) NOT NULL
Phone_number int(12) NOT NULL
Password Varchar(10) NOT NULL
Figure 3.4: Database structure for Register and login

FIELD NAME DATATYPE CONSTRAINT


16
Account_no int(30) NOT NULL
Amount int(100) NOT NULL
Figure 3.5: Database structure for user

CHAPTER FOUR

SYSTEM ANALYSIS AND RESULTS


17
4.1 Introduction

Ths chapter is intended to give the main findings derived from this research study. I concentrate the
survey results and the discussions. I conclude by discussing resonate matters concerning the system
implementation results. Within this section i show and identify a fully documented operational
system that is implemented on a computer system. By so doing, the following activities would be
carried out; Development of mobile application software. To test-run the computer program with
capture data to ensure proper execution and preparing the documentation.

4.2 Research objectives

For a computing service to support the mission aims and strategic direction of its instituition, its
support devices must be responsive to and flexible in meeting the needs of those who are their
customers and it must undertake research into what is required of them. In order to achieve
reasonable success in implementing this project, the following must be considered.

4.3 System Implementation

As discussed earlier in the previous chapter about the module i have in program, i shall review them
by starting the program one by one, to really see how each module is implemented.

Using the Graphical User Interface Forms

A very good example of a graphical user interface (GUI) form is the Dashboard page. This serves as
a link/platform between the user and the database. This page provides all the functionalities admin
can perform i.e check Balance, see previous transactions, e.t.c.

This is the main home page of the whole app; this page directs the user to all the various
functionalites the app provides. On the login page, after entering the right details and clicking the
login button takes users to the main page.

4.4 System screenshot

18
Figure 4.1: showing the login page

A login page is a type of graphical interface that allows users to access their account using their
Email and password as shown in the above diagram. This page is connected to the database
(Firebase) which verifies if the data entered in the Email text field and the password text field
correlate with what is in the database.

Figure 4.2: Home page(Main page)

19
The home page can also be called “Dashboard”. It provides the user the balance of his/her account,
buttons that direct users to other pages, and history of his/her previous transactions.

It has buttons that serve as link to other pages or functions in the app such as the transfer button,
mobile topup button, loan page button, loan application page, etc.

Figure 4.3: Transfer page of the app

On clicking the Trasfer button, the transfer page is displayed. The transfer page collects the
recievers Account number, bank name, amount, and description for the transfer as shown in figure
4.3. it is responsible for deducting the amount stated in the amount text field from the original
balance of the sender(original balance of the user hompage) and crediting the recever.

20
Figure 4.4: Mobile topup page

Mobile topup page is the page that comes up after clicking on the mobile topup button. This page
recharges the user mobile line or any recipients number inputed in the mobile number text field by
the amount inputed in the amoun text field.

Figure 4.5: Loan Application page

This page is the loan application page that contains a slider connected to a text view which selects
the amount of money to be borrowed. It contains a dropdown menu that allow user to select whether
21
the loan would be paid in weeks, months or years, and also a text field that allows user to enter the
tenure limit for the loan.

Figure 4.6: Loan home page

This page is referred to as the loan page, in this page the loan balance is displayed. The loan balance
is gotten from the loan application page. Any amount selected in the slider in the loan application is
displayed in the loan balance.

4.5 System requirement

4.5.1 Functional Reqirements

The system shall accept valid input of registered.

The system shall allow sending of money, mobile topup and other functions.

The system shall show the transactions carried out in the app.

4.5.2 Non Functional Requirements

The system should be easy to maintain.

The system should be compatible with any android.

The system should be secure

The system should be easy to learn by both novice and sophisticated users.

22
The system should have a standard graphical interface that allows for local data entry, editing, and
deleting of data wth much ease.

The system should provide easy, navigable and user-friendly interfaces.

4.6 Hardware and Software requirement

4.6.1 Hardware Requirement

The Citi-bank mobile app can be implemented on any android phone with the following capacities:

A storage space of 1GB, 1GB RAM memory and above, android version 5.0 and above should be
used to run this software. Java is suitable with android so running apps like this on android phones
with the aforementioned specifications should be easy.

4.6.2 Software Requirement

The Citi-bank mobile app can be implemented on any ndroid phone with the following software
capacities: any Android phone suitable with java is generally suitable with the app.

CHAPTER FIVE

RECOMMENDATION AND CONCLUSION

23
5.1 Summary of achievement

In summary, mobile banking system is assumed to be the best and easy method of carrying out bank
transactions. In the existing process, there is delay in attending to customers and at times, the
customers’ files are not secure. Mobile banking system is safe and cannot be manipulated by an
unauthorized person. Only authorised users wtih a login email and password can have access to the
mobile app.

5.2 Conclusion

This researcher highlights the development of mobile banking system which allows easy
manipulation, stress free and timely dissemination of information to customers via mobile devices.
It also gives room for fast and accurate processing. Furthermore, this technology or software will
ensure better functionality of the bank. It will reduce delay in the current system (which is the
bank)and ensure better functionality. Finally I hereby conclude that mobile banking system is the
best method of carrying out bank transaction.

5.3 Recommendation

Based on the findings and conclusions of the study, the following recommendation can be made to
help improve banking activites. It would also ensure better functionality of the mobile
application.There is need for speed, accuracy, efficiency and convenience in all managerial
operation. Based on this and other factors surrounding the existing system, the writer recommends
mobile banking system as the best method of carrying out bank transaction.

5.4 Suggestion of further studies

There is need to be improving or upgrading the mobile banking system to enable the bank to serve
its numerous customers better.The researcher there for suggests to future researchers to go into
broader research into all aspects of IDS.

References
1. AA Saikh, H. K. (2015). Telematics and informatics. Elseivier.
2. Bank marketing strategy. (2017, febuary 15th). Banking sector , p. 50.
24
3. clifford, J. F. (2015). Fundamentals of technology. Technology enhancement , 105.
4. foster, A. (2019). DESIGN AND IMPLEMENTATION OF AN ONLINE BANKING SYSTEM.
CHICAGO: EMERALD WORKS.
5. JAMES E, O. (2015). ANALYSIS OF A MOBILE BANKING SYSTEM. JJ WORKS PRESS.
6. O.M, p. (2017). Banking in the 21st century. Emerald.com.
7. Odewale, J. J. (2018). Banking . Philephedia: Eternal works press.
8. Rashid ol, d. (2018). banking and informatics. improving technological sectors, 70.
9. sl, e. e. (2016). international journal of banking structure. emerald academy, 120.

25

You might also like