System Design Chapter 4

CHAPTER 4
SYSTEM DESIGN
4.1 ARCHITECTURE OVERVIEW
The Architecture of the System is designed in such a way to enable a User Friendly
User Interface. The Simplicity in Design enables all kinds of Users to work with the Design.
The Architecture is re-engineered to support Quantum Encryption Techniques that enables
High Safety Standards. The OTP is generated first, the OTP is visible to the user only after
he verifies his Fingerprint a second time. The Biometric Data and Account Number of the
Customer is stored in the Database. The User is registered to the Payment Gateway.
The Registration Module supports many other Payment Gateways like Citrus
Avenue, CCPayments and other predominant Gateways. The Payment Gateways are
connected to their official sites via PHP in the background. PHP has been chosen over other
languages considering its feasibility and simplified process.
The Payment Gateway is designed considering the Customers and is designed to be
a Hassle-free but well protected process. This chapter provides the overall design of the
proposed system.
The Registration Module and Payment Module integrate seamlessly with each other
with the Website seamlessly. The Modules are based on the Quantum Cryptographic
System entirely. Hence, the Website is protected and private. The Sensitive Data and details
of the user are never bothered with or eavesdropped. This is a Huge Advantage with the
Website. There are many other security features that can be enhanced. The registration
module and the Payment gateway are integrated in such a way that the Modules are entirely
designed and optimized for a minimal internet usage.
This Quantum Transmission of OTP and Account number cannot be hacked or
misused. It is impossible to hack the transaction. This is highly secured to done the
transaction. The entire Module is highly secured with some Quantum Cryptographic system.
After the payment module the biometric is verified in the user and bank database to send a
OTP to complete the transaction.

14
System Design Chapter 4

Fig 4.1. Payment Gateway Design

There are three components present in the Website Module:

1. Registration Module
2. Payment Gateway Module
3. Finger Print Query for OTP generation Module

15
System Design Chapter 4

4.2 REGISTRATION MODULE

Fig 4.2. Registration Module

The Registration Module has been designed in a light manner to accommodate

maximum number of users in times of site traffic. The Website Traffic is analyzed with
Google Analytics to provide website analytics in order to manage load in the network. This
Module Stores the registered user in the database for the future use. This Module takes the
account number and password purposely for transaction process.

16
System Design Chapter 4

Fig 4.3. Finger Print Registration in Registration Module

The Finger Print Module detects the Biometric Input. Input is transferred to the
Website via a Background Code. The Finger Print is checked with the server and the
matching of the finger print is performed in website. The Finger Print Registration is depicted
in Fig 4.3. Further the Finger print is check in the database in a cryptography encrypted
format and decrypted in the database to match and verify the finger print of the user. If the
fingerprint matches the user transaction is completed. The Biometric Input is to get the
verification OTP via Biometric while transaction process. Thus the user Transaction is
secured and cannot be misused. After entering to this module the user cannot go back
without complete the transaction. This may defend the transaction traffic and help to done
the transaction much easier and in a fast manner.

17
System Design Chapter 4

4.3 PAYMENT GATEWAY MODULE

The Payment Gateway is where the Transactions are performed. The Payment
Gateway is immediately redirected from the Vendor Page once the user initiates a
Transaction. The Payment Gateway is where the user shares his Account Number and
Finger print data.

Fig 4.4. Payment Gateway Module

In Fig 4.4. The Payment Gateway Module is depicted. The User can opt to switch to
other Gateways but without his Biometric Verification. The Finger Print is saved in the
Server. The Website Module is followed by the Database Module developed using Microsoft
Access:

Fig 4.5. Database Module that stores Finger Print and Account Number

18
System Design Chapter 4

In the Fig 4.5., the database is designed in Microsoft Access for its Light Design.
However, the Access Database is not capable of handling larger number of users. The
Database is upgraded to the Oracle Server.

Fig 4.6. Encryption and Decryption

Fig 4.6. Depicts the Encryption and Decryption of the Account Number and Finger
Print. AES standards are used to prevent fatal security errors in the network.

19