Detecting E-banking Phishing Using

Classification Data Mining Algorithm

Under the Guidance of

• Dr. P.EDITH LINDA
• ASSISSTANT PROFESSOR
• Dr. G.R. DAMODARAN COLLEGE OF SCIENCE
• DEPARTMENT OF COMPUTER SCIENCE

Submitted by :
Sivaprakash
1. ORGANIZATION
 1.1 About Organization
Censoware Technologies is a tech-savvy, futuristic software and
mobile application development company.

The Organization is located in Ramanathapuram near Gem

Hospital.

The clients and projects are given high focus, irrespective of

size and volume.

The management focus is to deliver quality services under

highly experienced and qualified teams.
2. INTRODUCTION
2.1 Abstract
The credit card fraud detection features uses user behavior
and location scanning to check for unusual patterns.

These patterns include user characteristics such as user

spending patterns as well as usual user geographic
locations to verify his identity.

If any unusual pattern is detected, the system requires re-

verification.
In this project we present a behavior and Location Analysis
(BLA), which does not require fraud signatures and yet is
able to detect frauds by considering a cardholder’s
spending habit.

In this project the process of Cryptography has been

followed, it is one of the most important security
technologies which used to secure the data transmission and
the data itself.
3. SYSTEM ANALYSIS
3.1 Existing System
In the existing system, the encrypted key is send with
the document.

Any user can view the encrypted document with that

key.

. It means the security provided for the encryption is

not handled properly.
3.1.1 Drawbacks
The fraud is detected after the fraud is done that is, the
fraud is detected after the complaint of the card holder.

Card holder faces a lot of trouble before the investigation

get over.

Lot of online purchase are made, so we don’t know the

person how is using the card online.

Need a help from the cyber crime to investigate the fraud.

3.2 Proposed System
In proposed system, whenever a new user registers, the
credit card and debit card details are cross checked and then
only the user id is generated.

The credit card number will be encrypted before leaving the

browser, so hacker cannot able to chase the credit card
number.

Cryptography algorithm is used in this system which

provides better performance as compared to other
traditional classifications algorithms.
3.2.1 Advantages
Drastic reduction in the number of false positive
transactions identified as malicious by an FDS.

The Credit card and Debit card details will be in

encrypted form, only the card holders and bank
officials can decrypt.

Can easily identify the fraudster by the behavior and

location analysis.
4. MODULES
4.1 Modules
 Register

 Login

 Account Master

 Credit Card Manager

 Transaction Manager

 Block Transaction (Cryptography Algorithm)

4.1 Modules
 Register : The user registers themselves by giving all the
personal information, including the credit/debit card
details. The system cross checks the details of the user like
sending OTP, Email verification etc.

 Login : After registration the user uses his/her username

and password to get login to the system.

 Account Master : The credit card and debit card number

gets encrypted automatically when he/she uses any
browser, it is decrypted only when the user provides
correct details.
 Credit Card Manager : In this module, the card details
are shown. The user can change or update the card details,
here also the system cross checks all the details of the user.

 Transaction Manager : The transaction history can be

viewed.

 Block Transaction (Cryptography Algorithm) :

Fraudulent is identified by the behavior and location
analysis of the user. Triple Data Encryption Standard
algorithm is used in this module.
5. SYSTEM SPECIFICATION
5.1 HARDWARE REQUIREMENT
Processor : Pentium IV

Hard Disk : 40GB

RAM : 512MB or more

Mouse : Optical

Printer : HP Laser
5.2 SOFTWARE REQUIREMENT
Operating System : Windows 10

User Interface : HTML, CSS

Client-side Scripting : JavaScript

Programming Language : PHP

Database : MYSQL

Server Deployment : Apache

6. SYSTEM DESIGN
6.1 DFD DIAGRAM
6.2 ER DIAGRAM
7. TABLE DESIGN
User Registration:
Field Name Data Type Size Null
ID Int 10 Not Null

Name Varchar 30 Not Null

Email Varchar 30 Not Null

Contact Number Int 15 Not Null

Username Varchar 30 Not Null

Password Varchar 30 Not Null

Login:

Field Name Data Type Size Null

ID Int 10 Not Null

Username Varchar 30 Not Null

Password Varchar 30 Not Null

 Credit/Debit Card:
Field Name Data Type Size Null
ID Int 10 Not Null

Allowed Branch Varchar 30 Not Null

Account Number Varchar 30 Not Null

Pin Int 15 Not Null

Account ID Varchar 30 Not Null

Branch Details:
Field Name Data Type Size Null

ID Int 10 Not Null

Branch Name Varchar 30 Not Null

Branch Location Varchar 30 Not Null

 Account Details:
Field Name Data Type Size Null
ID Int 10 Not Null
User ID Int 10 Not Null
Branch ID Int 30 Not Null

Balance Int 15 Not Null

Transaction Limit Varchar 30 Not Null

Block History:
Field Name Data Type Size Null

ID Int 10 Not Null

Account ID Int 10 Not Null

Created_At Date 30 Not Null

Branch Id Int 15 Not Null

Account Details:

Field Name Data Type Size Null

ID Int 10 Not Null

Account ID Int 10 Not Null

Branch ID Int 30 Not Null

Amount Int

Created_At Date 15 Not Null

8. TESTING AND SYSTEM
IMPLEMENTATION
8.1 Objective of Testing:
The major objectives of Software testing are as follows:

 Finding defects which may get created by the programmer

while developing the software.

 Gaining confidence in and providing information about the

level of quality.

 To make sure that the end result meets the business and
user requirements.

 To gain the confidence of the customers by providing them a

quality product.
8.2 Test Plan:
Test Plan is essential for the following reasons :

 Existence of program detects of inadequacies

 A software behavior as intended by its designer.

 Assess the operational reliability of the system.

 Reflect the frequency of actual user inputs.

 Find the faults, which causes the output anomaly.

 9. CONCLUSION
 It has been successfully designed and developed to
fulfilling the necessary requirements, as identified in the
requirements analysis phase, such as the system is very
much user friendly, form level validation and field level
validation are performing very efficiently.

 The system results in quick retrieval of information that is

very vital for the progress of any organization.

 Burden of manual work is reduced as whenever transaction

takes place, there is no need to record it in many places
manually.
THANK U…
THE END