FEDERAL UNIVERSITY OYE EKITI

DEPARTMENT OF COMPUTER SCIENCE

CSC 320 - SOFTWARE LAB PROJECT REPORT

PROJECT TOPIC:

ONLINE PAYMENT SYSTEM

PRESENTED BY

SOGUNLE OLUWABOLAKUNMI ISAAC CSC/2020/1164

OGUNMOLA WINSTON AJIBOLA CSC/2020/1120

DANJUMA MITCHELL OSHOMA CSC/2020/1069

UNDER THE SUPERVISION OF

DR LAWRENCE ADEWOLE

DATE

July 2024

1
 TABLE OF CONTENTS

CHAPTER ONE

1.0 Introduction

1.1 Statement of the Problem

1.2 Aim of the Study

1.3 Objectives of the Study

CHAPTER TWO

2.0 Overview of Existing System

2.1 Overview of Proposed System

2.2 Functional & Non-Functional Requirements

2.3 Methodology

2.3.1 Requirement Assessment

2.3.2 Application Program

2.3.3 Testing and Development

2.3.4 Documentation and Training

CHAPTER THREE

3.0 Implementation Tools

3.1 Hardware and Software Requirements

3.2 Description of New System & Result

CHAPTER FOUR

4.0 Conclusion

4.1 Recommendations

REFERENCES

2
 CHAPTER ONE

1.0 Introduction
Over the years there have many definition of payment system; Shon and Swatman
(1998, p. 203) define payment systems as “any conventional or new payment system which
enables financial transactions to be made securely from one organization or individual to
another over the Internet”. Briggs and Brooks (2011, p. 1) describe an electronic payment
system in a very similar way as “a form of IOS for monetary exchange, linking many
organizations and individual users”. Khan et al. (2017, p. 257) use electronic payment and
online payment interchangeably and define both as “a type of inter-organizational
information system (IOS) for money related transactions, connecting numerous associations
and individual clients”. Neuman and Medvinsky (1995) describe internet payment systems as
electronic currencies and state that credit-debit instruments currently represent this form of
payment. Abrazhevich (2004) divides electronic payment systems into electronic cash
systems and account-based systems. In simpler terms, a payment system is a mechanism
established to facilitate the clearing and settlement of monetary and other financial
transaction.
Developments in Information and Communication Technologies (ICTs) have made
impact in all sectors of the society, including education. In higher education, application of
ICTs in form of e-learning is changing the mode of learning and teaching processes. School
management is now done online, records are being kept in databases that are accessible
through the web. Also Registration, payment of schoolfees, generating timetables and much
more are done using the web. The world of IT has gone far and wide that now makes us see
the importance of using automated system rather than manual system.
Referring to the problem of faculty and department due as the Online Payment
System problem (OPS). Given the large number of students that are typically involved in
such problem, there is a growing interest in automating the process of payment using
centralized matching schemes that incorporate efficient algorithms for OPS. Examples of
similar automated systems are in use in several universities.
In recent years, the advancement of technology has thus brought us into a new era of
Web based systems. These systems are also known as enquiry systems and have the ability to
input data, with a guaranteed response time and an assurance that the information is accurate
and timely, then one is said to have a “Real Time System” [6]. A real time system is also a
Web based system and comprises mainly of four (4) main components:

3
 i. A data-gathering component that collects data from the external environment.
ii. An analysis component that transforms the received information as required
by the application.
iii. A control component that responds to the external environment.
iv. A monitoring component that co-ordinates all other form of these components
so that real-time response can be achieved.

Due to these advancements, organization need no longer be centralized when information

services can reach the home and offices for processing from a number of geographical
locations. However, Web based systems have helped tremendously in every field of human
existence today. Hence this project work provides and creates an Online Payment System
(OPS) to the Federal University of Oye-Ekiti through the development of a Web based system
that will in turn improve the efficiency and effectiveness of the university.

1.1 Statement of the Problem

The current method for processing faculty and department dues at The Federal
University of Oye-Ekiti is both inefficient and susceptible to errors. Faculty members must
visit the finance office in person to make payments, which often leads to long wait times and
delays in administrative processing. The finance department manually records each
transaction, a time-consuming task that increases the likelihood of mistakes, such as incorrect
entries or misplaced records. Additionally, the manual generation of receipts complicates the
process, delaying payment confirmations and reducing transparency. Faculty members often
struggle to track their payment history and dues status, leading to confusion and potential
errors.
To resolve these issues, we propose creating an Online Payment System (OPS) tailored
to our school's needs. This system will feature a secure, user-friendly online portal for faculty
and departments to make payments via credit/debit cards. The OPS will automatically
generate and email receipts upon payment completion, ensuring immediate acknowledgment
and accurate record-keeping. With real-time tracking and reporting, the system will enhance
transparency, allowing faculty to easily access their payment history and enabling the finance
department to produce comprehensive reports. Automating these processes will reduce errors,
improve efficiency, and provide a convenient platform for managing dues, ultimately
enhancing the school's financial management.

4
1.2 Aim of the Study

The aim of the project is to develop an Online Payment System that allows students
securely and comfortably pay their faculty and departmental dues.

1.4 Objectives of the Study

i. Create an Application based system that will solve the problems of the existing
system being used for faculty and departmental dues.
ii. Allow students to pay their faculty and departmental due anywhere and anytime
iii. Ease and speed up registration of students every session.

5
 CHAPTER TWO
2.0 Overview of Existing System
Federal University of Oye-Ekiti has a financial system that records, monitors, and
reports about student fees payment transactions and other finances in the university. Fees
payments by students are made through cash deposits, electronic funds transfer and bank
drafts to the university’s accounts in specific bank branches and later reflected which
integrates with an Information system that provides information on students. These methods
of paying fees have not been efficient enough especially during periods of registration and
preparation for examinations. The process of fees payment in such periods is characterized by
long queues, too much waiting by students, delay in collecting receipts and congestion at
banks network (In cases of bank transfer) where payments are made. This process has always
resulted in students being stressed as they have to line up in unending queues at the various
payment centers in each faculty.
A recent survey taken of FUOYE students from various faculties show an alarming
rate of dislike for the current stressful payment system.

2.1 Overview of Proposed System

The proposed system aims to modernize the payment of the faculty and department
dues at Federal University of Oye-Ekiti by transiting from a manual, paper based system to a
fully automated online payment platform system to ensure efficiency, accuracy and
convenience for all stakeholders (Students and Financial officers at the University). This
digital platform will allow students to securely log in, view their outstanding views and make
payment directly through the system using integrated payment gateways like Paystack. The
system will automatically generate receipts to users upon successful transactions,
significantly reducing the administrative burden, stress on students and potential errors
associated with manual generation of receipts.
This transition to a digital payment system will not only save time but also improve
the overall user experience by offering a seamless and secure method for managing our
university dues.

6
 2.2 Functional and Non-Functional Requirements
Functional Requirements
i. The system shall accept valid input of registered students’ payment details from users
intending to pay fees online.
ii. The system shall process fees payment transactions so that student fees accounts are
credited with the specified amount in each transaction.
iii. The system shall produce a receipt as a proof of payment for every transaction made.
iv. The system shall produce a listing of transaction information to students.
v. The system shall provide feedback to the student describing the status of the
transaction.
vi. The system shall be able to generate payment reports to students.

Non-Functional Requirements

i. The system should be easy to maintain.

ii. The system should be compatible with different platforms.
iii. The system should be fast as customers always need speed.
iv. The system should always be available online all times.
v. The system should be secure.
vi. The system should be accessible to online users.
vii. The system should be easy to learn by both sophisticated and novice users.
viii. The system should provide easy, navigable and user friendly interfaces.

The system should have a standard graphical user interface that allows for the on-line data
entry, editing, and deleting of data with much ease

2.4 METHODOLOGY
The proposed research method that would be adopted is as follows;

2.3.1 Requirement Assessment

A thorough assessment of the current existing system will be carried out and the requirements of the new

system will be clearly defined by interviewing some students and lecturers

Stakeholder Identification

7
 Internal Stakeholders: These include university administration, department heads, and IT

staff. They are responsible for overseeing the system's implementation and ensuring it meets

the university's needs.

External Stakeholders: These are the primary users of the system, including students who

need to pay their dues and faculty who may need to manage their department’s finances.

Financial institutions involved in processing transactions are also considered external

stakeholders.

Requirement Gathering

User Interviews: We conducted surveys using google form with students to understand their

specific needs and expectations from the payment system.

2.3.2 Application Program

At this stage, the design work flow will be converted to code and debugged.

System Architecture

Backend: Develop the server-side components using languages like Node.js. Manage data

using a robust database system like MySQL

Frontend: Design the user interface using React.js, ensuring it is responsive and accessible.

API Integration: Integrate the system with existing university financial systems and third-

party payment gateways like Paystack to facilitate secure and efficient transactions.

Development Process

Agile Methodology: We adopted an iterative development approach with regular sprints and

8
 continuous feedback to ensure the system meets user needs and can adapt to changes quickly.

Version Control: Use Git for managing source code and tracking changes, facilitating

collaboration among developers.

2.3.3 Testing and Development

The completed application will be tested and deployed on remote web host, ready for use.

Testing Strategies

Unit Testing: Test individual components of the system to verify they work as expected in

isolation.

Integration Testing: Ensure that different modules of the system, such as the backend and

frontend, work together seamlessly.

System Testing: Conduct comprehensive testing of the entire system in an environment that

simulates production to identify and fix any issues before deployment.

Security Testing

Penetration Testing: Simulate attacks to identify and address vulnerabilities in the system.

Compliance Testing: Verify that the system adheres to university policies, financial

regulations, and data protection standards.

Performance Testing

Load Testing: Evaluate system performance under normal operating conditions to ensure it

can handle the expected transaction volume.

Stress Testing: Test the system under peak load conditions to identify and address potential

performance bottlenecks.

Scalability Testing: Assess the system’s ability to scale up as demand increases, ensuring it

9
 can handle future growth.

Deployment

Environment Setup: Configure separate environments for development, testing, and

production to ensure smooth deployment and maintenance processes.

Monitoring and Maintenance: Implement monitoring tools to track system performance and

availability, and establish maintenance procedures to address issues and apply updates

promptly.

2.3.4 Documentation and Training

At this stage the system is fully tested and then the training of stakeholders (Student and

Administrative officers) will begin to learn how to use this platform efficiently

User Documentation

User Manuals: Create detailed guides to help students and faculty navigate the system and

use its features effectively.

FAQs: Develop a list of common issues and their solutions to assist users in troubleshooting

problems on their own.

Developer Documentation

API Documentation: Provide detailed documentation of the system’s APIs to facilitate future

development and integration with other systems.

Code Comments: Ensure that the code base is well-documented with in-line comments to

make it easier for developers to understand and maintain.

Training

10
Workshops: Conduct training sessions for users and administrators to familiarize them with

the system and its features.

Tutorials: Create online tutorials and webinars to provide ongoing support and training for

new users and updates.

Fig
1: Data Flow diagram for Online Payment System

11
Fig 2: Backend documentation page

Fig 3: Frontend documentation page

12
 CHAPTER THREE

3.0 Implementation Tools

With the following Implementation tools, we’re to build an Online Payment System that
allows students to pay their Faculty and Departmental dues easily and effectively
i. Node.js for the backend
ii. React.js for the frontend
iii. Mongodb/MySql for taking nte of students information and transactions
iv. Paystack and the use of credit/debit cards for the payment option

3.1 Hardware and Software Requirements

Hardware: Operating System (Windows 7, 8 and 10 (32-bit and 64-bit) or Mac OS

Processor; Minimum of Core i3
Ram: At least 4GB, recommended

Software: IDEs like Visual studio

Node.js
Paystack
React.js
Mongodb/MySql

3.2 Description of New System and Result

This payment system is comprised of several tools that make it easier and more convenient

for students to use, while also making it easier for administrators to document and secure.

The system is designed to reduce stress, theft, and loss of accounts, and to ensure accurate

tracking and safekeeping of payments.

The system consists of the following components:

- User Authentication:

A secure login system that verifies the identity of students and administrators, ensuring that

only authorized users can access the system.

13
- Payment Processing:

A secure and efficient system for processing payments, which can be done online or offline.

This component ensures that payments are processed accurately and in real-time.

- Students Dashboard:

A user-friendly interface that allows students to view their payment history, check their

account balance, and make payments online.

Additional features of the system include:

- Real-time database storage, ensuring that all transactions are recorded and stored securely

- Automatic generation of transaction receipts, providing a paper trail for each payment

- Easy storage and retrieval of payment records, making it simple to track and verify

payments

- Reduced risk of theft and loss, thanks to the secure and encrypted nature of the system

Overall, this payment system is designed to provide a convenient, secure, and efficient way

for students to make payments, and for administrators to manage and track those payments."

14
 CHAPTER FOUR

4.0 Conclusion
Advancement in technology is making automation of mechanical activities become a
very important aspect of our daily lives. Since the use of computers is now widespread, the
adoption of this system will make life become easier for us all.
The project sought to develop an online fees payment system that provides relief of the long
endured problems of the current modes of paying fees in Federal University of Oye-Ekiti.
Problems that students faced regarding paying fees to the university were identified and a
solution was designed. A web based system that enables students and their sponsors to pay
university fees was developed. This system was welcomed by all its users who believed it
would solve most of the problems and improve conditions regarding paying fees in Federal
University of Oye-Ekiti. The project achieved all its objectives and as a result, APPS was
designed, developed, tested and validated with real users. Hence, it was proved that this
online system was fit to be implemented.

4.1 Recommendations
Having met the specified objective of the proposed project and after a profound
evaluation of the developed system, I will like to suggest the following recommendations for
further research work and improvement opportunities
i Federal University of Oye-Ekiti should embrace and implement the developed system

as it will improve the conditions of dues payment.

ii The researchers acknowledge that security is a threat to every system and therefore

encourage that maximum effort be dedicated to ensure security of the online

transactions through establishment of sound security infrastructure.

iii A mobile version of the system should be created to allow user access the system

from any device other than a computer thus improving the mobility of the device.

15
REFERENCES
1. Abrazhevich, D. (2004). Electronic payment systems: A user-centered
perspective and interaction design. Eindhoven: Technische University,
Eindhoven.
2. Akampwera G., Ashaba J., Lwanga N., Sekibira R. (2013),
Online fees payment system for Makerere University (muk-ofps); Undergraduate
Project, Makerere University.
3. Chou, Y., Lee, C. and Chung, J. (2004). Understanding M-commerce payment
systems through the analytic hierarchy process. Journal of Business Research
57, 1423–1430.
4. E-Commerce Payment Systems (2014). http://www.tutorialspoint.com
[Online] Available
http://www.tutorialspoint.com/e_commerce/e_commerce_payment_systems.ht
m (September 3, 2014).
5. Fisser, P. (2001) “Using Information and Communication Technology”. Ph.D.
thesis, Netherlands: University of Twente.

16
6. Laplante, Philip A., “Real-time systems design and analysis – An Engineer’s
Handbook, 2nd ed. IEEE Press, Piscataway, NJ, USA, http://www.ieee.org,
1997”
7. Harris, H., Guru, B., and Avvari, M. (2011). Evidence of firms‟ perceptions
toward electronic payment systems (EPS) in Malaysia. International Journal of
Business and Information 6(2).
8. James, A. (2009). Management Information Systems, Accounting information
systems: Oxford University Press.
9. Kalakota, R. and Whinston, A. (1997). Electronic commerce: a manager's
guide. Addison- Wesley.
10. Luke Welling, Laura Thompson, (2003). PHP and MYSQL Wed Development:
Second Edition, Sams Publishing.
11. Mohammad, A. and Emmanuel, U. (2003). Online credit card processing
models: critical issues to consider by small merchants. Human systems
management 22(3), 133-142.
12. Shon, T. and Swatman, P.M. (1998). Identifying effectiveness criteria for
Internet payment systems, Internet Research: Electronic Networking
Applications and Policy 8(3), 202- 218.
13. Singh, M.P. (2004). Information Systems. Practical Handbook of Internet
Computing. University of Toronto.
14. Taiwo Olufemi, Asaolu Tajudeen and John Ayoola., (2011) Electronic
Payment System in Nigeria: Implementation, Constraints and Solutions,
Journal of Management and Society, Vol. 1, No 2, pp. 16-21.

17