DESIGN AND IMPLEMENTATION OF AN

ELECTRONIC PAYMENT SYSTEM

BY

UGBAGBA Priscillia Funkepere

PSC1712900

DEPARTMENT OF COMPUTER SCIENCE,

FACULTY OF PHYSICAL SCIENCES,
UNIVERSITY OF BENIN,
BENIN CITY.

FEBRUARY 2025

1
 DESIGN AND IMPLEMENTATION OF AN

ELECTRONIC PAYMENT SYSTEM

BY

UGBAGBA Priscillia Funkepere

PSC1712900

SUBMITTED TO THE DEPARTMENT OF COMPUTER

SCIENCE, FACULTY OF PHYSICAL SCIENCES,
UNIVERSITY OF BENIN IN PARTIAL FULFILLMENT
OF THE REQUIREMENTS FOR THE AWARD OF
BACHELOR OF SCIENCE (BS.C) HONS DEGREE
COMPUTER SCIENCE.

FEBRUARY 2025

ii
 CERTIFICATION

This is to certify that this research work was carried out by UGBAGBA Priscillia

Funkepere with Matriculation Number: PSC1712900, Faculty of Physical Sciences,

Department of Computer Science, University of Benin, Benin city under my supervision.

………………………………. …………………………
Prof. V.V.N Akwukwuma Date
(Project Supervisor)

iii
 APPROVAL

This project report written by UGBAGBA Priscillia Funkepere with matriculation number

PSC1712900 in partial fulfillment of the requirement for the award of the University of
Benin Bachelor of Science (B.Sc.) degree in Computer Science, is adequate both in scope
and content and it is hereby approved for presentation.

…………………………… ……………………………
Prof. Godspower Ekuobase Date
(Head of Department)

iv
 DEDICATION

This project work is dedicated to God Almighty, for providence, guidance, and grace in

seeing me through this study; I give Him all the glory. I also dedicate this project to my

parents Mr. and Mrs. Ugbagba, I would not have come this far.

v
 ACKNOWLEDGEMENT

My sincere gratitude goes to God Almighty, for granting me this grace and mental powers

to complete this project. This project completes another milestone in my academic career. I

sincerely appreciate the Head of Department, Computer Science, Prof. Godspower

Ekuobase. It is pertinent at this junction to appreciate the effort of my project supervisor,

Prof. V.V.N Akwukwuma for his support and guidance throughout the course of this

project.

Worthy of special mention are my parents; Mr. and Mrs. Ugbagba who through their

unalloyed support, encouragement, financially, morally and spiritually which enabled me to

successfully complete this programme.

May God, in His infinite mercy, bless you all.

vi
 TABLE OF CONTENTS

PRELIMINARY PAGES
CERTIFICATION iii
APPROVAL iv
DEDICATION v
ACKNOWLEDGEMENT vi
ABSTRACT x
CHAPTER ONE: INTRODUCTION 1
1.1 Introduction 1
1.2 Background of Study 1
1.3 Statement of Problem 3
1.4 Aim and Objectives of the Study 4
1.5 Significance of Study 4
1.6 Scope of Study 6
1.7 Limitations of the Study 7
1.8 Definition of Terms 7
CHAPTER TWO: LITERATURE REVIEW 9
2.1 Introduction 9
2.2 Conceptual Review of Electronic Payment System (EPS) 9
2.2.1 Components of EPS 10
2.2.2 Types of Electronic Payment Systems 10
2.2.3 Benefits of Electronic Payment Systems 11
2.2.4 Challenges and Considerations 12
2.2.5 Future Trends and Innovations 12
2.3 Theoretical Framework 13
2.3.1 Technology Acceptance Model (TAM) 13
2.3.2 Diffusion of Innovations Theory 13
2.3.3 Unified Theory of Acceptance and Use of Technology (UTAUT) 13
2.3.4 Institutional Theory 13
2.3.5 Trust Theory 14
2.3.6 Digital Divide Theory 14
2.4 Problems Associated with EPS Utilization 14
2.5 Prospects for the Challenges Affecting EPS 15

vii
 2.6 Empirical Studies 16
CHAPTER THREE: SYSTEM DESIGN AND METHODOLOGY 18
3.1 Methodology Adopted 18
3.1.1 Problem Identification Using OOADM 19
3.2 Analysis of the Existing System 20
3.2.1 Dataflow of the Existing System 21
3.2.2 Disadvantages of the Existing System 21
3.2.3 Weakness of the Existing System 22
3.3 Feasibility Study 22
3.3.1 Technical Feasibility 22
3.3.2 Operational Feasibility 23
3.3.3 Economic Feasibility 23
3.4 Analysis of the Proposed System 23
3.4.1 Data Flow Diagram of the Proposed System 24
3.4.2 Advantages of the Proposed System 24
3.4.3 Justification of the Proposed System 25
3.5 Functional Requirements 25
3.5.1 Use Case Diagram of the Admin / User Privileges 26
3.6 Data Requirements 27
3.7 High-Level Model of the Proposed System 28
3.8 Objectives of the Design 29
3.9 Cohesion and Decomposition High level Model 30
3.10 Control Center / Overall Dataflow Diagram 31
3.10.1 Proposed System Operation Flowchart 32
3.11 System Specification and Design 36
3.11.1 Input and Output Specification 36
3.11.2 Database Specification and Design 37
3.11.3 Data Dictionary 38
CHAPTER FOUR: IMPLEMENTATION AND RESULT 39
4.1 Choice and Justification of Programming Language 39
4.2 Program Documentation 40
4.3 Implementation Techniques 41
4.3.1 System Testing 43

viii
 4.4 Programming Module Specification 43
4.4.1 Installation 44
4.4.3 System Architecture 46
4.5 Computer Hardware Minimum Requirement 46
4.6 Software Requirement 47
4.7 Personnel / User Training 47
4.8 File Maintenance Module 47
4.9 Discussion of Findings 49
CHAPTER FIVE: SUMMARY, CONCLUSION AND RECOMMENDATION 51
5.1 Introduction 51
5.2 Summary 51
5.3 Conclusion 52
5.4 Recommendation 53
REFERENCES 55
APPENDIX A: SOURCE CODE 61
APPENDIX B: OBJECT PROGRAM 83

ix
 ABSTRACT

An Electronic Payment System (EPS) refers to a digital infrastructure enabling the transfer of

money electronically for the purchase of goods and services. The aim of the study is to design

and implement a Electronic Payment System using First Bank Plc Enugu as a case study. In

achieving this aim, the following specific objectives were laid out as follows to develop an

application software that will create an intuitive and accessible user interface for the

Electronic Payment System. The motivation that led to the implementation of the proposed

system is that there is increasing prevalence of cyber attacks and fraud poses significant risks

to the security of electronic payment systems. Electronic Payment System (EPS) are

attractive targets for cyber criminals due to the high value of financial data they handle. Other

motivation issues are outline at the statement of problems section. The methodology adopted

in this study is the object oriented analysis and design methodology (OOADM) which is a

technical approach for analyzing and designing an application or system by applying object

throughout the software development process. The programming language used is HTML,

CSS, JAVASCRIPT, PHP, SQL and JQUERY. The reason why web programming languages

was used is because, it is platform independent and it is a web based application. The

implementation of the proposed system will enable broader access to financial services for

underserved populations, including those without traditional bank accounts, promoting

financial inclusion and economic empowerment. The expected result is an Electronic

Payment System that will enable iterative improvements and refinements to the electronic

payment system design and functionality.

x
 CHAPTER ONE

INTRODUCTION

1.1 Introduction

Introduction

A Digital Payment System (DPS) is a technology-driven framework that

facilitates the electronic transfer of funds for buying goods and services. It
encompasses various methods such as online banking, debit and credit card
operations, mobile wallets, and app-based transactions. This innovation has
drastically changed how transactions are carried out, offering more secure,
fast, and user-friendly alternatives to cash and conventional banking (Turban
et al., 2015; Laudon et al., 2020). The evolution of DPS can be traced to the
mid-20th century with the advent of credit cards. Since then, it has
transformed in response to emerging technologies, shifts in consumer
preferences, and the rapid expansion of online commerce (Narayanan et al.,
2016; Want, 2011).

This chapter introduces the study, highlighting the research background,

problem statement, objectives, significance, scope, limitations, and definition
of technical terms.

1.2 Background of the Study

The development of Digital Payment Systems has been influenced by the

progress of information technology and the internet, which introduced new
avenues for conducting financial operations. The origins of this innovation
date back to the 1950s, when credit cards first allowed consumers to make
cashless purchases (Turban et al., 2015). Over the next few decades,
technologies such as ATMs and Electronic Funds Transfer (EFT) systems
gained popularity (Laudon et al., 2020).

The 1990s witnessed a surge in internet-based activities, driving the demand

for secure online payment mechanisms (Aloul, 2010). Consequently, services
such as online gateways and e-wallets, including PayPal, emerged (Wang et
al., 2016). The growth of smartphones in the 2000s and 2010s introduced
mobile payment solutions like Apple Pay and Google Wallet, revolutionizing
financial accessibility and convenience (Want, 2011).

1
 DPS has significantly impacted the economy by simplifying transactions and
cutting the costs associated with cash handling. It also promotes financial
inclusion, especially in underserved regions, through platforms like M-Pesa in
Kenya (Laudon et al., 2020). Additionally, it has enabled businesses to reach a
broader, global customer base (Wang et al., 2016).

Nonetheless, the swift expansion of digital payment technologies has

introduced security risks, such as cyber threats and data breaches. In response,
developers and regulators have introduced encryption, tokenization, and multi-
factor authentication to protect users (Aloul, 2010). Governments have
implemented regulations to safeguard users’ data and ensure transaction
integrity (Rescorla, 2001), and compliance with standards like PCI DSS
remains essential (Narayanan et al., 2016).

This study was motivated by persistent challenges like the lack of

interoperability between digital payment systems and traditional financial
services. This disconnect causes inefficiencies and affects user satisfaction. On
the other hand, this scenario presents financial institutions with opportunities
to earn through innovative service offerings (Laudon et al., 2020).

1.3 Statement of the Problem

Despite the widespread adoption of DPS, several challenges persist. One major
concern is the increasing vulnerability of these systems to cyberattacks.
Fraudsters target digital platforms due to the sensitive nature of financial data.
Common risks include phishing, identity theft, and malware attacks (Aloul,
2010; Narayanan et al., 2016).

Another issue is the poor compatibility between various digital systems and
existing banking infrastructure, which often results in higher transaction costs
and limited adoption rates (Turban et al., 2015; Rescorla, 2001).

Additionally, the demand for users’ personal and financial data raises
significant concerns about privacy and data protection. Unauthorized access or
sharing of user data remains a critical issue that must be addressed (Wang et
al., 2016).

1.4 Aim and Objectives of the Study

2
 The primary aim of this research is to develop and implement a secure and
efficient Electronic Payment System for Zenith Bank Plc UNIBEN. The
specific objectives are to:

1. Ensure seamless integration between the EPS, financial infrastructures,

and payment platforms.
2. Incorporate advanced security mechanisms like encryption and multi-
layered authentication.
3. Enable continuous system enhancements based on performance
evaluations and user feedback.
4. Design a user-friendly interface that enhances the overall user experience.
5. Document the entire development process for reference and future
upgrades.

1.5 Significance of the Study

The relevance of this research can be viewed from multiple perspectives:

For Consumers:

 Ease of Use: DPS enables anytime, anywhere transactions without

relying on physical cash (Laudon et al., 2020).
 Improved Security: Modern DPS incorporates features that help secure
financial transactions, boosting consumer confidence (Rescorla, 2001).
 Broader Access: These systems provide financial access to people
outside conventional banking systems, fostering inclusion (Wang et al.,
2016).

3
 CHAPTER TWO

LITERATURE REVIEW

2.1 Introduction

This chapter presents a review of related literature on digital payment systems.

It includes conceptual explanations, theoretical perspectives, challenges of
implementation, potential solutions, and empirical insights from past studies.

2.2 Conceptual Overview of DPS

Digital Payment Systems are platforms that enable secure, cashless financial
transactions. These systems use a variety of tools and technologies to
streamline payments and enhance accessibility (Pereira et al., 2020). From the
introduction of credit cards to today’s mobile apps, DPS have continuously
adapted to meet changing consumer needs and technological progress
(Khanna, 2019).

2.2.1 Key Components of DPS

1. Payment Tools: Instruments such as debit/credit cards, prepaid cards,

mobile wallets, and cryptocurrencies are used for initiating transactions
(Smith, 2018).
2. Gateways: These facilitate secure online payments by transmitting data
between users, merchants, and banks using encryption (Patel & Gupta,
2021).
3. Transaction Processing: This involves verifying, transferring, and
recording transaction details to ensure successful fund transfers (Xie et
al., 2022).
4. Security Measures: Protocols like encryption and multi-factor
authentication are employed to safeguard financial information (Goff,
2020).

2.2.2 Categories of Digital Payment Systems

1. Card-Based Payments: These include credit and debit cards, offering

quick and direct payment options (Kumar & Soni, 2019).
2. Internet Banking: Facilitates electronic management of finances through
digital platforms offered by banks (Chin et al., 2021).
3. Mobile Transactions: Payments are made using mobile devices via NFC
or QR code technology (Santos & Pereira, 2022).

4
4. Digital Wallets: Applications that store card information securely for
both online and in-person transactions (Yang & Choi, 2020).
5. Blockchain-Based Payments: Cryptocurrencies allow for decentralized
transactions without intermediary banks (Swan, 2019).

5
 CHAPTER THREE

SYSTEM DESIGN AND METHODOLOGY

3.1 Methodology

The development process for this project follows the Object-Oriented Analysis
and Design Methodology (OOADM), which uses object-oriented principles to
model software systems throughout the development life cycle. It allows for
iterative enhancements and fosters effective communication among
stakeholders.

 Object-Oriented Analysis: Focuses on understanding user requirements

through models that mirror real-world entities and interactions.
 Object-Oriented Design: Converts the conceptual model into a blueprint
considering implementation constraints such as technology stack, cost,
and usability.
 Object-Oriented Modeling: A framework for simulating system
behavior and structure using unified modeling language (UML) tools.

3.1.1 Identified Issues Using OOADM

a) Feasibility Study: Evaluates the practicality of the proposed system based

on technological, financial, and organizational parameters.
b) Environment Analysis: Involves studying data requirements and building
an initial model of entities and their relationships.
c) Business System Options: Defines the scope of system functionality based
on user and business needs.
d) Requirement Validation: Ensures that stakeholders understand and agree
upon the project’s technical expectations.
e) Technical Feasibility: Assesses availability of required software, hardware,
and technical know-how.
f) Logical Design: Creates data flow diagrams and system interaction models.
g) Physical Design: Details the structure of the database and outlines the
system’s hardware specifications.

3.2 Existing System Analysis

Analysis of the current system at Zenith Bank Plc UNIBEN identified key
shortcomings such as vulnerability to cyberattacks and limited data
integration. These limitations necessitate the development of a more secure,
interoperable, and user-centric electronic payment system.

6
  Input Specification: Describes the nature and format of data entered into
the system, including fields, validation checks, and data types.
 Output Specification: Outlines the expected outputs, which may be
physical (e.g., printed receipts) or digital reports.

3.2.1 Dataflow of the Existing System

ELECTRONIC PAYMENT
SYSTEM

Input Analysis Output Analysis

Process Analysis
Fill Registration Produce Result
Form

Process Request
Opening Account Generate Report

Login to System Process New Account

Validate Login Details

Figure 3.2.1: Dataflow of the Existing System

3.2.2 Disadvantages of the Existing System

Identified issues with the current system include:

7
 1. Slow and error-prone manual data processing.

2. Stressful processes for end-users.

3. Inconvenience of manual tasks.

3.4.1 Data Flow Diagram of the Proposed System

This is a data flowchart of the proposed system as shown in figure 3.2.

Sends Details Success / Failure

ADMIN TABLE ADMIN

Found / Not Found Login Details

LOGIN ACCOUNT
Found / Not Found Login Details

Success / Failure

USER TABLE EPS USER

Success / Failure
Sends Details

Registration Details

REGISTER

Figure 3.2: Data Flow Diagram of the Proposed System

3.4.2 Advantages of the Proposed System

The following are the advantages of the proposed Electronic Payment System;

a) Convenience: Allows payments anytime and anywhere, reducing the need for

physical cash or bank visits.

b) Speed: Processes transactions instantaneously or within seconds.

c) Security: Utilizes advanced encryption and fraud detection technologies to protect

financial information.

8
 d) Accessibility: Promotes financial inclusion by providing banking services to

underserved populations.

e) Efficiency: Streamlines payment processing, improves cash flow management, and

reduces administrative costs.

3.4.3 Justification of the Proposed System

EPS enable quick, convenient transactions without the need for physical cash. They offer

faster processing times, advanced security measures, cost reductions, and facilitation of

international transactions. They also provide detailed transaction records and can integrate

with other digital services, promoting innovation and enhancing user experience.

Additionally, EPS contribute to environmental sustainability by reducing reliance on paper-

based transactions.

To ensure a standardized object-oriented program, HTML, CSS, JavaScript, PHP, and

MySQL Database were used in developing the seaport billing software. These languages are

compatible with several operating systems, are object-oriented, and combine features of PHP

and JavaScript, ensuring security and ease of use.

3.5 Functional Requirements

The following figure 3.4 shows the various modules involved in the system and available to

users who have limited access and to the Admin who have full access to the system.

9
 3.5.1 Use Case Diagram of the Admin / User Privileges

Update Payment
Record

Insert/Delete
Record

Activate Account

Figure 3.3: Use Case diagram of the Admin

ADMIN

Input Username

Input Password
END-USER

Open Account

Figure 3.4: Use Case diagram of the User (Client)

10
 3.6 Data Requirements

The following are the data requirements of new and existing users in the system. New users

must provide the following information during account creation such as:

a) Email Address: The user's email address is required during registration and subsequent

login on the system.

b) Password: The user is required to enter a secured password or pin during registration

and subsequent login on the system

c) User Name: The user is required to enter a nickname which he/she will be addressed as

subsequently for security reasons.

d) Passport: This field contains the photograph or picture of the account holder or system

user.

e) Address: This field contains the address of the system user.

11
 3.7 High-Level Model of the Proposed System

The high level model of the proposed system is illustrated below;

DESIGN AND IMPLEMENTATION OF

ELECTRONIC PAYMENT SYSTEM

HOME Admin END-USER (Client)

Update Record

Open Account
Insert/Delete Record

Input Bio-Data
Activate Account

Respond Input Username &

Password

Send and Receive

Payment

Give Feedback

Figure 3.5: High Level Model of the Proposed System

12
 3.8 Objectives of the Design

The objectives of the proposed Electronic Payment System (EPS) design are as follows:

1. Integrate the EPS with existing financial infrastructures and payment gateways,

enabling seamless transactions between different platforms and banking systems.

2. Implement advanced security features such as encryption, multi-factor authentication,

and real-time fraud detection.

3. Enable iterative improvements and refinements to the electronic payment system

design and functionality.

4. Create an intuitive and accessible user interface for the Electronic Payment System.

5. Document the design and implementation process comprehensively, allowing future

developers and researchers to understand and build upon the work conducted.

13
 3.9 Cohesion and Decomposition High level Model

Description: This is a Cohesion and Decomposition High level Model

Admin

Update Record Insert/Delete Record Activate Account Deactivate Account

Figure 3.9A: Admin User Privileges

Client (User)

Open Account Input Bio-Data Input Username & Send and Receive Give Feedback
Payment
Password

Figure 3.9B: Client (User) Privileges

14
 3.10 Control Center / Overall Dataflow Diagram

Description: This is a control center / overall dataflow diagram

ELECTRONIC
PAYMENT
SYSTEM

Input from
keyboard

Process

Result to
Disk
Report (output) screen
storage

Figure 3.10: Control Center / Overall Dataflow Diagram

15
3.10.1 Proposed System Operation Flowchart

Description: The diagram below details the proposed system operation flowchart.

Start

Input Username and

Password

Is username and No Display “Invalid

password valid? Username/password”

Yes

Figure A: Login flowchart

16
 Start

INPUT REGISTRATION DETAILS

SAVE TO
DATABASE

YES
CONTINUE?

NO

End

Figure B: Registration Flowchart

17
 Start

INPUT STAFF REGISTRATION

DETAILS

SAVE TO
DATABASE

YES
CONTINUE?

NO

End

Figure C: Staff Registration Flowchart

18
 Start

Enter User ID

Validate User ID

Input Phone
Number

Input Payment
Information

Answer security question B

NO Display
Are answers
Error
correct? message
YES

Send Request

Save

Stop

Figure 3.11: Proposed System Operation Flowchart

19
 3.11 System Specification and Design

3.11.1 Input and Output Specification

Description: The diagram below details the Input and Output Specification of the proposed

system.

ELECTRONIC PAYMENT SYSTEM

Customer ID:

Enter Phone Number

Password:

Enter Password

Sign In Register Here

Figure 4.5: Input Specification for Login System

Login Successful
Or
Login Unsuccessful

Figure 3.12: Output Specification for Electronic Payment System

20
 CHAPTER FOUR

IMPLEMENTATION AND RESULT

4.1 Choice and Justification of Programming Language

To ensure a standardized, object-oriented program, the following technologies were utilized

in developing the Electronic Payment System: HTML, CSS, JavaScript, PHP, and MySQL
Database. These technologies were chosen for their interoperability, scalability, and
compatibility with various operating systems.

The decision to use these tools was based on their wide adoption in web development, ease of
learning, support for object-oriented programming (OOP), and strong community support.
The languages are platform-independent and offer secure environments for developing and
deploying robust web applications.

Below is a brief explanation of each technology used:

 HTML (HyperText Markup Language):

Used to structure web content. It is a markup language consisting of elements
enclosed in tags, each defining a different component of the page (headings,
paragraphs, links, etc.).
 CSS (Cascading Style Sheets):
CSS defines the presentation and layout of HTML elements across devices. It helps
manage the design and user interface of multiple web pages consistently using
external stylesheets.
 JavaScript:
A scripting language used to create dynamic content on web pages. JavaScript
enhances user interaction and provides functionalities such as form validation and
page interactivity.
 PHP (Hypertext Preprocessor):
A server-side scripting language widely used to develop dynamic and interactive web
applications. PHP connects with databases, manages sessions, and processes form
data securely.
 MySQL:
A relational database management system that supports structured query language
(SQL) operations. It stores user data and transaction records, ensuring quick access
and manipulation.

4.2 Program Documentation

Program documentation is vital for describing system design and providing a guide for future
maintenance and upgrades. The documentation for this project includes:

21
  A README file containing a summary of the project, installation instructions, and
usage guidelines.
 Properly commented code following established programming conventions such as
naming styles, modular design, and file organization.
 Version control logs noting major code changes and improvements.

4.3 Implementation Techniques

Software implementation involves deploying and configuring tested components of the

system on a production environment. The successful deployment depends on meeting
hardware and software requirements.

1. Coding

The objectives of the coding phase included:

 Integrating EPS with existing financial infrastructures and gateways.

 Implementing security measures such as encryption and multi-factor authentication.
 Creating a user-friendly interface.
 Supporting iterative system improvement.
 Proper documentation for knowledge transfer and future enhancements.

2. File Conversion

The new system requires the conversion of old master files into formats compatible with the
new software. This step involves transforming data and integrating it into the new database
schema.

3. Changeover Procedures

Transitioning from the old system to the new one involved different changeover methods:

 Parallel Changeover: Both systems run simultaneously until the new one is
confirmed stable.
 Direct Changeover: The old system is completely replaced by the new one at a
specific time.
 Phased Changeover: The new system is deployed gradually, department by
department.

4. Commissioning

Commissioning ensures the system is tested, functions correctly, and aligns with the original
design specifications before it becomes fully operational.

4.3.1 System Testing

22
The system was tested in a controlled lab environment. Test cases included:

 Registering different types of users.

 Querying the database using user ID numbers.
 Validating system functions against expected outcomes. The tests confirmed that the
system performed reliably and met the design requirements.

4.4 Programming Module Specification

This section focuses on evaluating the system post-implementation and ensuring all
objectives are met through continuous monitoring and maintenance.

Types of Maintenance:
 Corrective Maintenance: Fixes coding errors and bugs after deployment.
 Adaptive Maintenance: Updates system components to accommodate changes such
as new database structures or system environments.
 Preventive Maintenance: Enhances performance and minimizes the risk of future
issues.

4.4.1 Installation Guide

Steps to Install the Electronic Payment System:

1. Insert and open the CD or USB flash drive containing the system.
2. Copy the electronic-payment-system folder to the XAMPP server directory:
C:\XAMPP\htdocs\
3. Start Apache and MySQL using the XAMPP Control Panel.
4. Open a web browser (e.g., Chrome, Firefox).
5. Go to localhost/phpmyadmin/
6. Set username as root and password as empty, then click Go.
7. Click Import, browse to locate eps.sql from the directory:
C:\XAMPP\htdocs\electronic-payment-system\db\eps.sql
8. Click Go to import the database.
9. Access the software by typing in the address bar:
http://127.0.0.1/electronic-payment-system/
10. The system is now ready to use.

To Re-Execute the Software After Installation:

1. Start the XAMPP Server.

2. Open your browser and enter the URL:
http://127.0.0.1/electronic-payment-system/

23
The security design specification is an authentication system that required a valid password to

be input before using the proposed system. Below is a diagram of the Security Design

Specification:

Start

Input Login Details

Is
Yes No
Login = Valid
?

DISPLAY MAIN MENU

Stop

Figure 4.4: Security Design Specification

4.4.3 System Architecture

A system architecture or systems architecture is the conceptual model that defines the

structure, behavior, and more views of a system. An architecture description is a formal

description and representation of a system, organized in a way that supports reasoning about

the structures and behaviors of the system. A system architecture can consist of system

24
components and the sub-systems developed, that will work together to implement the overall

system. Proposed Application Software Architecture:

Back End
Front End Sends Data
Packer

Server
Receives Data
Packer
Database

Figure 4.4: System Architecture

4.5 Computer Hardware Minimum Requirement

The software designed requires the following hardware for effective operation of the newly

designed system:

i. A system running on AMD, Pentium 2 or higher processor

ii. The random access memory (RAM) should be at least 512MB

iii. Enhanced keyboard

iv. At least 20GB hard disk

v. VGA or a colored monitor

25
 CHAPTER FIVE

SUMMARY, CONCLUSION AND RECOMMENDATION

5.1 Introduction

This study focused on the design and implementation of an electronic payment system. In the

preceding chapter, the relevant data collected were presented, critically analyzed, and

appropriately interpreted. This chapter offers recommendations that, in the opinion of the

researcher, will benefit the electronic payment system.

5.2 Summary

An Electronic Payment System (EPS) is a digital infrastructure that enables the transfer of

money electronically for the purchase of goods and services. It includes various technologies

and methods, such as online banking, credit and debit card transactions, e-wallets, and mobile

payment solutions. EPS has revolutionized commerce by providing a convenient, secure, and

efficient means of transaction, reducing the reliance on physical cash and traditional banking

methods. Since their inception, EPS has significantly evolved, driven by technological

advancements, changes in consumer behavior, and the growth of e-commerce. Initially rooted

in the development of credit cards in the mid-20th century, EPS now encompasses a wide

variety of electronic and mobile payment solutions catering to different user preferences and

technological capabilities.

5.3 Conclusion

In conclusion, Electronic Payment Systems (EPS) represent a transformative force in modern

finance, reshaping how individuals and businesses conduct transactions globally. Empirical

research highlights the widespread adoption of EPS driven by convenience, efficiency, and

expanded access to financial services. However, challenges such as cybersecurity threats,

regulatory complexities, and disparities in digital access require ongoing attention. Studies

26
emphasize the critical role of user acceptance, supported by factors like perceived usefulness

and ease of use, in driving EPS adoption. Security remains paramount, with ongoing

advancements in encryption and authentication technologies aimed at mitigating risks and

enhancing user trust. Regulatory frameworks play a pivotal role in shaping EPS development,

balancing innovation with consumer protection and financial stability.

EPS have facilitated financial inclusion, particularly in underserved communities, by

providing accessible and affordable banking solutions. Initiatives to improve cross-border

payments through technological innovation and international cooperation are advancing,

aiming to streamline transactions and reduce costs across borders.

Looking ahead, EPS are poised for further evolution with emerging technologies like

blockchain, AI, and IoT promising enhanced security, efficiency, and user experience.

Continued research, collaboration among stakeholders, and adaptive regulatory frameworks

will be essential in maximizing the benefits of EPS while addressing emerging challenges in

the dynamic landscape of digital payments.

In essence, EPS represent not only a technological advancement but also a catalyst for

broader economic inclusion and efficiency in the global financial ecosystem. As these

systems continue to evolve, their impact on commerce, consumer behavior, and regulatory

frameworks will shape the future of finance in a digitally interconnected world.

5.4 Recommendation

To enhance Electronic Payment Systems (EPS), recommendations should focus on

addressing existing challenges and leveraging opportunities to improve security, accessibility,

and efficiency. Key recommendations include:

1. Enhance Security Measures: EPS providers should continually invest in advanced

encryption techniques, multi-factor authentication, and real-time fraud detection systems

to safeguard transactions and protect user data from evolving cyber threats.

27
2. Simplify User Experience: EPS interfaces should prioritize intuitive design and

seamless integration across devices to enhance user convenience and encourage broader

adoption among diverse demographics.

3. Promote Financial Literacy: Initiatives to educate consumers and businesses about the

benefits, risks, and responsible use of EPS can foster greater trust and confidence in

digital payment solutions.

4. Expand Access to Digital Infrastructure: Governments and private sector stakeholders

should collaborate to improve internet connectivity and digital literacy, particularly in

underserved regions, to promote equitable access to EPS.

5. Facilitate Interoperability: Standardizing protocols and promoting interoperability

among different EPS platforms and financial institutions can reduce transaction costs,

enhance efficiency, and improve the overall user experience.

6. Adapt Regulatory Frameworks: Policymakers should adopt flexible and adaptive

regulatory frameworks that balance innovation with consumer protection, ensuring

compliance with data privacy laws and anti-money laundering regulations.

28
 REFERENCES

Ademola, O. (2018). Zenith Bank’s Contribution to Educational Development in Nigeria: A

Case Study of the University of Benin. Journal of African Education, 23(4), 45-60.

Ajayi, K. (2019). Financial Services and Student Satisfaction: An Analysis of Zenith Bank's

Operations at the University of Benin. International Journal of Educational

Management, 33(2), 134-148.

Eze, C. (2020). Enhancing Campus Financial Inclusion through Digital Banking: Zenith

Bank's Role at UNIBEN. Journal of Financial Technology, 17(1), 55-72.

Igbinovia, M. (2021). Zenith Bank and University of Benin Partnership: Impact on Student

Financial Literacy. West African Journal of Banking and Finance, 12(3), 102-118.

Nwokolo, J. (2017). Corporate Social Responsibility in Higher Education: Zenith Bank's

Initiatives at the University of Benin. African Journal of Business Ethics, 9(1), 78-89.

Ogbeide, A. (2016). An Evaluation of Zenith Bank’s ATM Services at the University of

Benin Campus. Journal of Banking and Financial Services, 14(2), 88-101.

Okon, E. (2019). The Impact of Zenith Bank on the Financial Management of University of

Benin Students. Nigerian Journal of Educational Finance, 28(4), 112-125.

Omoruyi, O. (2021). Student Perceptions of Zenith Bank’s Mobile Banking Services at

UNIBEN. Journal of Educational Research and Reviews, 10(6), 145-159.

Osagie, P. (2018). Zenith Bank and Higher Education Financing: A Study of UNIBEN's

Funding Model. Journal of Higher Education Policy, 15(3), 90-104.

Uwaifo, J. (2020). Analyzing the Efficiency of Zenith Bank Branch Operations within

University of Benin. Journal of Institutional Banking, 19(5), 67-82.

Abidi, S.A.H. (1991). Information and Communication for Development in Africa. Nairobi.

29
 APPENDIX A

SOURCE CODE

#Login Page

<?php require_once('./config.php') ?>

<!DOCTYPE html>
<html lang="en" class="" style="height: auto;">
<?php
if($_settings->userdata('id') > 0){
$_settings->set_flashdata('warning',' You are already in a session.');
redirect('./');
}
require_once('inc/header.php');
?>
<body class="login-page dark-mode py-4">
<?php if($_settings->chk_flashdata('success')): ?>
<script>
alert_toast("<?php echo $_settings->flashdata('success') ?>",'success')
</script>
<?php endif;?>
<script>
start_loader()
</script>
<style>
html,body{
height:calc(100%) !important;
width:calc(100%);
}
body:before{
content:"";
position:fixed;
height:calc(100%);
width:calc(100%);
top:0;
left:0;
background-image: url("<?php echo validate_image($_settings->info('cover')) ?>");
background-size:cover;
background-repeat:no-repeat;
z-index: -1;
}

30
 .login-page{
height:100% !important;
}
.login-title{
text-shadow: 4px 4px black
}
img#cimg{
height: 15vh;
width: 15vh;
object-fit: cover;
border-radius: 100% 100%;
}
</style>
<h1 class="text-center py-5 login-title"><b><?php echo $_settings->info('name')
?></b></h1>
<div class="login-box">
<div class="card card-primary card-outline card-tabs bg-dark-gradient">
<div class="card-header p-0 pt-1 border-bottom-0">
<ul class="nav nav-tabs" id="CTab" role="tablist">
<li class="nav-item">
<a class="nav-link active" id="login-tab" data-toggle="pill" href="#login" role="tab"
aria-controls="login" aria-selected="false">Login</a>
</li>
<li class="nav-item">
<a class="nav-link" id="signup-tab" data-toggle="pill" href="#signup" role="tab"
aria-controls="signup" aria-selected="true">Sign Up</a>
</li>

</ul>
</div>
<div class="card-body">
<div class="tab-content" id="CTabContent">
<div class="tab-pane fade active show" id="login" role="tabpanel" aria-
labelledby="login-tab">

<form id="ulogin-frm" action="" method="post">

<div class="input-group mb-3">
<input type="email" class="form-control" name="username"
placeholder="Email" required>
<div class="input-group-append">
<div class="input-group-text">
<span class="fas fa-user"></span>
</div>
</div>
</div>
<div class="input-group mb-3">
<input type="password" class="form-control" name="password"
placeholder="Password" required>
<div class="input-group-append">

31
 <div class="input-group-text">
<span class="fas fa-lock"></span>
</div>
</div>
</div>
<div class="row">
<div class="col-8">
</div>
<!-- /.col -->
<div class="col-4">
<button type="submit" class="btn btn-primary btn-block">Login</button>
</div>
<!-- /.col -->
</div>
</form>

</div>
<div class="tab-pane fade" id="signup" role="tabpanel" aria-labelledby="custom-
tabs-three-profile-tab">
<form action="" id="user-register">
<input type="hidden" name="id">
<input type="hidden" name="type" value="2">
<div class="row">
<div class="col-md-6">
<div class="form-group">
<label for="firstname" class="control-label text-info">First
Name</label>
<input type="text" autofocus class="form-control form-control-border"
id="firstname" name="firstname" required>
</div>
<div class="form-group">
<label for="middlename" class="control-label text-info">Middle
Name</label>
<input type="text" class="form-control form-control-border"
id="middlename" name="middlename" placeholder="optional">
</div>
<div class="form-group">
<label for="lastname" class="control-label text-info">Last Name</label>
<input type="text" class="form-control form-control-border"
id="lastname" name="lastname" required>
</div>
<div class="form-group">
<label for="gender" class="control-label text-info">Gender</label>
<select class="form-control form-control-border" id="gender"
name="gender" required>
<option>Male</option>
<option>Female</option>
</select>
</div>

32
 <div class="form-group">
<label for="dob" class="control-label text-info">Date of Birt</label>
<input type="date" class="form-control form-control-border" id="dob"
name="dob" required>
</div>
<div class="form-group">
<label for="contact" class="control-label text-info">Contact #</label>
<input type="text" class="form-control form-control-border"
id="contact" name="contact" required>
</div>
</div>

<div class="col-md-6">

<div class="form-group">
<label for="address" class="control-label text-info">Address</label>
<textarea rows="1" class="form-control form-control-border"
id="address" name="address" required></textarea>
</div>
<div class="form-group">
<label for="username" class="control-label text-info">Email</label>
<input type="email" class="form-control form-control-border"
id="username" name="username" required>
</div>
<div class="form-group">
<label for="password" class="control-label text-info">Password</label>
<input type="password" class="form-control form-control-border"
id="password" name="password" required>
</div>
<div class="form-group">
<label for="cpassword" class="control-label text-info">Confirm
Password</label>
<input type="password" class="form-control form-control-border"
id="cpassword" required>
</div>
<div class="form-group">
<label for="" class="control-label">Avatar</label>
<div class="custom-file">
<input type="file" class="custom-file-input rounded-circle"
id="customFile" name="img" onchange="displayImg(this,$(this))">
<label class="custom-file-label" for="customFile">Choose file</label>
</div>
</div>
<div class="form-group d-flex justify-content-center">
<img src="<?php echo validate_image(isset($meta['avatar']) ?
$meta['avatar'] :'') ?>" alt="" id="cimg" class="img-fluid img-thumbnail">
</div>
</div>
</div>

33
 <hr class="bg-light">
<div class="row">
<div class="col-md-12 text-center">
<button type="submit" class="btn btn-primary btn-lg rounded-pill w-
50">Register</button>
</div>
</div>
</form>
</div>

</div>
</div>
<!-- /.card -->
</div>
</div>
<!-- /.login-box -->

<!-- jQuery -->

<script src="plugins/jquery/jquery.min.js"></script>
<!-- Bootstrap 4 -->
<script src="plugins/bootstrap/js/bootstrap.bundle.min.js"></script>
<!-- AdminLTE App -->
<script src="dist/js/adminlte.min.js"></script>

<script>
function displayImg(input,_this) {
if (input.files && input.files[0]) {
var reader = new FileReader();
reader.onload = function (e) {
$('#cimg').attr('src', e.target.result);
}

reader.readAsDataURL(input.files[0]);
}
}
$(document).ready(function(){
end_loader();
$('#CTab .nav-link').click(function(){
if($(this).attr('aria-controls') == 'signup'){
$('.login-box').addClass('w-75')
}else{
$('.login-box').removeClass('w-75')
}
})
$('#ulogin-frm').submit(function(e){
e.preventDefault()
$('.pop_msg').remove()
start_loader()

34
 var _this = $(this)
var el = $('<div>')
el.addClass('pop_msg alert')
el.hide()
$.ajax({
url:_base_url_+'classes/Login.php?f=login_user',
method:'POST',
data:$(this).serialize(),
error:err=>{
el.addClass('alert-danger')
el.text('An Error occured')
_this.prepend(el)
el.show('slow')
$('html,body').animate({scrollTop:0},'fast')
},
success:function(resp){
if(resp){
resp = JSON.parse(resp)
if(resp.status == 'success'){
location.replace(_base_url_);
}else if(resp.status == 'incorrect'){
el.addClass('alert-danger')
el.html("<i class='fa fa-exclamation-triangle'></i> Incorrect username or
password");
_this.prepend(el)
el.show('slow')
$('html,body').animate({scrollTop:0},'fast')
_this.find('input').addClass('is-invalid')
_this.find('[name="username"]').focus()
}
end_loader()
}
}
})
})

35
 APPENDIX B

OBJECT PROGRAM

System Snapshots of some Features

Default Website Page

Client's Transaction List Page

36
Transaction Form Modal Step 1

Transaction Form Modal Step 2

37
Transaction Details Modal

38
 Admin Panel

Transaction Report Page (Admin Side Only)

39
40