Payment Gateway App

Project report submitted in partial fulfillment of the requirement for the

degree of Bachelor of Technology

in

Computer Science and Information Technology

By

Arpit Thakur (181411)

Shivansh Thakur (181428)

Under the supervision of

Dr. Rajani Mohana

to

Department of Computer Science & Engineering and Information

Technology
Jaypee University of Information Technology Waknaghat, Solan-
173234, Himachal Pradesh
 Candidates’ Declaration

We hereby declare that the work presented in this report entitled “Payment Gateway App” in
partial fulfillment of the requirements for the award of the degree of Bachelor of Technology in
Computer Science and Engineering/Information Technology submitted in the department of

Computer Science & Engineering and Information Technology , Jaypee University of

Information Technology Waknaghat is an authentic record of our own work carried out over a
period from August 2021 to December 2021 under the supervision of Dr. Rajani Mohana
(Associate professor, CSE Department).
The matter embodied in the report has not been submitted for the award of any other
degree or diploma.

Arpit Thakur, 181411 Shivansh Thakur, 181428

This is to certify that the above statement made by the candidate is true to the best of my
knowledge.

Dr. Rajani Mohana

Associate Professor
Computer Science and Information Technology
Dated: 03/12/2021

(i)
 Acknowledgement

The success and final outcome of this project required a lot of guidance and assistance from
many people and we are extremely privileged to have got this all along the completion of our
project. All that we have done is only due to such supervision and assistance and we feel a deep
sense of gratitude towards them.

We are very grateful to Ms. Rajani Mohana, for providing us an opportunity to do the
project work and giving us all support and guidance which enabled us to complete the project
duly. We are extremely thankful to her for providing such a great support and guidance, although
she had busy schedule managing the university affairs.

We are thankful and consider ourselves fortunate enough to get constant encouragement,
support and guidance from our family and friends who also contributed to the successful
completion of our project work

Arpit Thakur, 181411

Shivansh Thakur, 181428

(ii)
 Table of Contents
Declaration by Candidate I
Certificate by Supervisor II
Acknowledgement III
List of Figures and Tables V
Abstract VI

1 Chapter No. 1: Introduction 1-7

.
1.1 Introduction 1-4
1.2 Problem Statement 4-5
1.3 Objective of Minor Project 5
1.4 Methodology 5-6
1.5 Organization 6-7

2 Chapter No. 2: Literature Survey 8-9

.

3 Chapter No. 3: System Development 10-17

.
3.1 Design 10-11
3.2 Designing Procedure 11
3.3 Model Development 11-17

4 Chapter No. 4: Performance Analysis 18-26

.
4.1 Analysis 18-19
4.2 Results 19
4.3 Screenshots of Various Stages of Project 20-25
4.4 Comparisons 26

5 Chapter No. 5: Conclusions 27-29

.
5.1 Conclusions 27
5.2 Future Work 27-29
5.3 Applications 29

References 30-32
Appendices 33-34
(iii)
 Abstract

The records era (IT) has revolutionizedthe diverse factors of our lives; specifically it has
provided an easy way to go for digital payments. during the Demonetization period, the
government of India compelled the human beings at once or indirectly to do all industrial
transactions through virtual mode. The common people started to move from conventional
payment system closer to virtual bills systems which ensured secure, at ease and
convenience.With large technological leaps inside the clever phone and clean net access has led
Indian market to simply accept digital bills.the proportion of the virtual payments via other
modes is likewise increasing in a sizable speed.The objective of the existing examine is to
recognise approximately the numerous types of digital price transactions which are used by the
commonplace people in their day-today's lives. This have a look at is mainly primarily based on
Secondary statistics. result shows that the virtual revolution has made the cash much less
transaction an clean one. As a result that in 2015-2016, a total of 4018 billion has been transacted
through cell banking whilst in comparison to 60 billion in 2012-thirteen.The reach of cellular
community, net and energy is likewise expanding digital bills to remote areas. So, it's far
definitely said that destiny transaction device is cashless transaction.

As on-line transactions maintain to increase and become a sizable a part of the worldwide
financial system, the potential to just accept payments on line becomes extra critical for
businesses. This paper evaluates the literature and affords current records for IS researchers and
teachers specializing in digital commerce. in this paper, we discover the components of e-credit
companies (conventional, person-to-person, and 1/3-party) and provide an explanation for how
every system methods a unmarried transaction. We then analyze numerous market leaders in
every section and summarize the strengths and weaknesses of each organisation. We provide
hints for deciding on an e-credit company and highlight the alternatives that apply best to online
businesses. subsequently, we define potential areas of destiny studies and provide a easy tutorial
on creating a enterprise account with PayPal internet site bills preferred for instance of a web fee
provider.

(iv)
1. Chapter-1: INTRODUCTION

1 Introduction

Patron spending via the internet is growing at a sizeable fee. on-line spending these days
noticed global double-digit increase nearing 50% on a 12 months-to-year foundation, and
inside the India by myself spending is anticipated to reach $three.5 trillion in 2006 [Rob
& Opara, 2003, p. 1]. those traits are fueled by using worldwide economic enlargement.
They can be expected to retain in the future. The boom in spending on the net,
collectively with the underlying want for comfy transactions, will increase the
significance of on-line fee structures. on-line charge systems can be broadly described
because the means and techniques worried in carrying out transactions online; however,
this description may be improved to encompass the online financial connections among
sellers, buyers, economic establishments, and intermediaries. online fee systems had been
round for numerous years, yet at the moment are becoming ubiquitous with the increased
common use of the net. a number of the advantages furnished by on-line fee systems
encompass improved coins go with the flow efficiency, guaranteed transactions,
decreased expenses, expanded protection of touchy records, and multiplied safety of the
fee provider. given that fraud is a conventional issue with on-line transactions,
comfortable on line price structures are mainly important. in spite of the growth and
importance of on-line fee within the contemporary international economy, little
instructional literature exists on this place that integrates the disparate research streams
about on line fee structures and describes their implementation. in addition, online price
approaches are largely not noted by means of conventional textbooks, but it's miles
important for college students to understand on line payment because it represents the
most extensive shift in charge in the last hundred years.

Benefits of Global Payments Integrated’s APIs

Worldwide payments included gives strong, bendy APIs which might be clean and fast to
combine, no matter your integration approach. This reduces velocity-to-market and eases
the improvement cycles for builders. We additionally have the potential to do the
development for you if that is the route you favor to take.
as an instance, for our cellular solutions, you're able to ship, acquire, and connect with
our API seamlessly. here’s how it works:

ship API Request - Your software sends all non-sensitive parameters to the embedded
SDK.

process the Request - the global bills integrated API communicates with the PIN pad
device to prompt for card insertion, tap, swipe or manual access, before gathering
encrypted card information and acting an authorization request through the worldwide
bills included Platform.
 capture consequences - the global payments integrated SDK will offer you with the non-
sensitive charge effects such as the bank approval code, last four card digits, and an
encrypted token that can be used for next payments.

Print Receipt or send eConfirmation - Our solution provides your utility the ability of
showing or sending payment affirmation to the customer.

Figure 1. Payment API model

2 Problem Statement

The Task of this project is to come up with the designing and developing the online
Payment API which will be east to test and maintain. And the API should be able to
provide the services to the various online purchasing e-commerce companies and
more.

1 The acronym "API" stands for "Application Programming Interface." An API is a

written instruction that enables two devices, databases or applications to connect and
 share information. In other words, it’s the behind-the-scenes software language that
makes it easier for us to do things online or with our smartphones.

1 We utilize APIs all the time, whether we’re conscious of it or not. For example, when we
buy an airline ticket through a third-party travel reservations site, an API powers the
communication between the airline and the travel provider. Or if we have a Wi-Fi
thermostat in our home, an API is facilitating the communication that allows it to
remotely adjust the temperature in an individual room
The Task of this project is to come up with the designing and developing the online
Payment API which will be east to test and maintain. And the API should be able to
provide the services to the various online purchasing e-commerce companies and
more.

1 Objectives

The objective of the project is to provide a payment gateway API model to accurately
test and maintain the APIand make the API able to work smoothly. In this work, we
present a semi-supervised learning approach that outperforms, even more, the
performance of API in terms of the modelling of the API and the connection between the
two APIs which is established through the Rest Template. There are different functions
which could or might not be available, depending on the API and processing platform. for
instance, there’s the capacity to save transactions offline and have them processed when
functionality is restored. Or the API can be able to aid a various array of various
transaction types beyond the major card manufacturers and commonplace price
techniques.
moreover, a charge API may be able to consolidate all the information transmitted via the
platform, thereby supplying useful facts that has the capacity to tell commercial
enterprise and advertising and marketing decisions.

2 Methodology

The idea is to build an API for the Payment API Gateway. For this purpose, there is two
separate APIs built to perform the complete two different services. The different service
would be :

User_Service : It’s main tasks would be

-create a new user.
-Get all the users
-Get user by Id.

Wallet_Service : It’s main tasks would be

-Update the wallet.
-Create Wallet.
-Get wallet, if required.

Transaction_Service : It’s main tasks would be

-We should be able to send money from one user to another.
-We should be able to get the money.
-We should be able to sent transaction to the user if he wants on their mail.

One major gain of a charge API is that it can enhance a consumer’s purchasing
experience via casting off the want to fill out checkout forms, a tedious venture - mainly
on a smartphone - which can lead to purchasing cart abandonment. thanks to the ability to
reuse saved charge statistics, clients can entire a purchase on a cellular tool with just a
few faucets.

Figure 2. Different services to be used in the API

3 Organization

This Project is completely based on backend working. The main methods, technologies
and tools that are associated with this project are:

Methods Used:

 Microservice Architecture
  Object Relational Mapping
 Auto Configuration

Technologies Used:
 Java
 SpringBoot
 Swaggers
 Hibernate
 Rest Template
 Actuators
 MySQL

Each of the technologies are freely available and the technical skills required are
manageable. Time limitations of the product development and the ease of implementing
using these technologies are synchronized. From these it’s clear that the project is
technically feasible.
2. Chapter-2: LITERATURE SURVEY

Payment Gateway APIs

A payment gateway API integrated with existing digital processes can connect a checkout
system to a payment network.

Benefits of a Payment Gateway API

Figure 3. Benefits of payment Gateway API

The primary gain of using a fee gateway API is that it can simplify the charge technique (request,
authorization, receipt and affirmation). The way a fee API typically works is that an application
transmits a message/request to the API, which relays it to the price processing network, which in
flip approaches the request and responds to the API, which then relays the response to the utility.

Improved User Experience

One main benefit of a price API is that it may improve a purchaser’s shopping experience by
way of doing away with the want to fill out checkout paperwork, a tedious assignment -
particularly on a cellphone - which could cause buying cart abandonment. thanks to the
capability to reuse stored charge facts, clients can entire a purchase on a mobile tool with only a
few faucets.

Innovation

Every other advantage of a payment API is that it lets in a service provider to innovate. typically,
a fundamental API charge integration is simple, clean to check and with ease carried out.
however if your business enterprise has modern ideas - and a developer who has the technical
know-how to do the customization - an API can be custom designed in your heart’s content
material, via integrating outside applications, for instance. in the meantime, a payment API
probably lets in a commercial enterprise to preserve steady branding and consumer experience
throughout channels.

Security and Fraud Prevention

Ultimate, however genuinely now not least, any other core gain of a fee API relates to protection
and fraud prevention, which in flip eases regulatory compliance. That’s because consumer facts
and price facts is typically stored by the host (not the service provider), retaining that touchy
information out of the hands of a service provider. This makes it less difficult for a service
provider to stay PCI compliant and EMV®-ready at a time whilst failing to accomplish that can
result in sizeable exposure to monetary liability.

Additional Benefits

There are other features that may or may not be available, depending on the API and processing
platform. For example, there’s the ability to store transactions offline and have them processed
when functionality is restored. Or the API may be able to support a diverse array of different
transaction types beyond the major card brands and common payment methods.
Moreover, a payment API may be able to consolidate all of the data transmitted through the
platform, thereby providing helpful data that has the potential to inform business and marketing
decisions.
Further, software providers have found that integrating a payment API into its software has the
potential to provide an incremental revenue stream via revenue sharing with the payment
processor.

Benefits of Global Payments Integrated’s APIs

Global Payments Integrated offers robust, flexible APIs that are easy and fast to integrate,
regardless of your integration method. This reduces speed-to-market and eases the development
cycles for developers. We also have the ability to do the development for you if that is the route
you prefer to take.

As an example, for our mobile solutions, you are able to send, receive, and connect to our API
seamlessly. Here’s how it works:
 Send API Request - Your application sends all non-sensitive parameters to the
embedded SDK.
 Process the Request - The Global Payments Integrated API communicates with the PIN
pad device to prompt for card insertion, tap, swipe or manual entry, before collecting
encrypted card data and performing an authorization request through the Global
Payments Integrated Platform.
 Capture Results - The Global Payments Integrated SDK will provide you with the non-
sensitive payment results such as the bank approval code, last 4 card digits, and an
encrypted token that can be used for subsequent payments.
 Print Receipt or Send eConfirmation - Our solution provides your application the
flexibility of displaying or sending payment confirmation to the customer.

Transactions User Interface (Transactions UI) From Global Payments Integrated

ISVs can now take the complexities out of their payment integration with our new Transactions
User Interface (Transactions UI). This interface allows ISVs to make a single API call to support
multiple payment types, as well as split the payment amounts into several transactions for a
simple, single omni-channel experience.

This allows ISVs to stay within their environment, programming language, and operating system
while speeding up time to market, allowing international expansion and expanding product
differentiation.
Transactions UI Features

 All functionality through one API without the complexities of custom integrations
 New value-added products and features in the future with little to no development effort
 Cloud-based service to monetize payments and scale to a broader customer base

Benefits to ISVs’ Customers

 Decreased time and effort required for accepting payments

 Simplified reconciliation with the addition of a new cash tender type and reporting
 Streamlined payments workflow with an easy to use interface for capturing transactions
 Increased likelihood of customers paying for goods and services with the ability to accept
multiple payment methods in the same transaction
To learn more about the benefits of Global Payments Integrated’s APIs or our new Transactions
User Interface (Transactions UI), contact us today.

3. Chapter-3: SYSTEM DEVELOPMENT

Digital commerce reports are increasingly more stepping out of doors the boundaries of the
legacy computer-first web sites. To make more recent touchpoints consisting of cell apps, in-
keep digital, interactive show, wealthy content material, and IoT natively shoppable or assist
one-touch, gesture or voice-enabled transactions, traders want to increase price processing
everywhere.
The key to reaching omnichannel trade is API-pushed systems that allow applications to share
and manner information. Many companies have followed ecommerce microservices as a bendy
way to increase, customize and scale their trade functionality to suit the new world of shoppable
touchpoints.
Microservices are small programs constructed around precise business capability decoupled
from different pieces of your commerce platform. Their independence and committed APIs
permit them to integrate with numerous touchpoints and be scaled, up to date, and removed with
out impacting website overall performance, the database, or code of your middle commerce
platform. They’re specifically useful when you want to fulfill specific use cases without the
chance of “breaking your build.”

3.1 Design:

To build a microservice architecture or to design a microservice architecture we need to

make a different API for every different service in the application we are going to include.
The two services have to run as two different APIs but have to be connected through a
gateway, which can help an API to borrow some data from another API . Both have to be
connected through a single gateway. For this purpose , the Rest Template comes into play.
The use of Rest Template is done to connect the functionality of two APIs being separated.

Figure 4. Design of an API in microservice architecture

In this case, beginning from the pinnacle left nook, a user sends an occasion or message to
execute a payment as an access point. The customers can be cellular, internet, or any outside
tool / utility that acts as the entry factor with the groups payments structure.
This request to execute bills connects to your services thru the bills API. this is the bridge to
the internal relevant payments occasion streams, where streams are managed to decide what
selection or sub-choice of moves need to be taken. For practical functions, we'll proceed thru
this architecture as if all alternatives are necessary to make sure coverage of all elements and
offerings.
the first motion taken is validation of the incoming bills request, the usage of the validation
microservices presenting integration to all wanted systems in an corporation to validate
finances, customers (users), and more. as soon as validation is completed a message is sent
back to the payments event streams for similarly processing.
the following two levels of the bills architecture are not constantly necessary as they rely
upon validation consequences. If there are any issues or flags raised on a payment request
then the subsequent step could be to trigger using the anti-cash laundering (AML)
microservices or fraud detection microservices. every of those collections decide if action
desires to be taken, if payment requests want to be blocked, if the consumer wishes to be
suggested, and in all likelihood blocking funds. both of these service regions are leveraging
information caching to ensure current information is available to the selection control tooling
used to lower back those processing levels. Any consequences are then pushed lower back to
the bills occasion streams for in addition processing.
Following the procedure elements to the proper we're going to arrive on the clearing
microservices in which processing for actual payment budget planning wherein accounts are
debited earlier than routing the price range to the requested events. these outcomes are sent
back to the bills event streams for in addition processing.
subsequently, routing microservices are accessed to ensure the price range from the
processed bills are distributed to the indicated parties thru the to be had bills community.
notice that the bills community is shown as an external secure cloud element, supposed to
suggest only that it's an external network and dependent on the place the answer is being
deployed in for specifics as to the connection and information protocols used.
the second discern at the proper here is labeled as a direct bills facts instance and is meant to
offer greater insights into the motion of event streams and glide of statistics through the
above described system of executing on a bills request. Exploring the information of this
figure is left to the reader.

3.2 Designing Procedure:

 Start
 Go to the Spring Initializr website.
 Include the dependencies like MySQL Driver, JPA /Hibernate, Spring web, etc.
 After that click on build Spring Boot application.
 Then, open the project in IntellIJ.
  Then build controllers, model of the API, Repositories, and Services.
 Then connect the MySQL database to the application using JPA/Hibernate.
 Then write GetMapping , PutMapping, etc. to perform functions in the API.
 Built another API with same Configuration.
 Then, use Rest Template to connect between two or more APIs.
 End

3.3 Model Development:

Microservices architecture scalability is terrific for permitting aid for a huge variety of
platforms and devices as internet, mobile and IoT backend can be deployed, constant, and up
to date independently of every different. Microservices are small and flexible, which means
that you don’t should have interaction with a large code base on every occasion your crew
wants to make a change within the code. alternatively, development groups can choose
exactly the portions of code they need to engage with and enhance each productiveness and
maintainability. eventually, it promotes the idea of groups reusing each other’s code as
opposed to developing independently and from scratch.

Microservices structure is especially vital for DevOps groups because it gives accelerated
agility so the group can roll updates out lots faster--and extra tailor-made to every crew’s
timeline--because of shorter build, take a look at, and installation cycles. Reliability is also
increased seeing that an issue with one microservice only influences that microservice, no
longer the complete application. This substantially reduces any opportunity of the complete
software failing. Microservices are also extraordinarily modifiable, providing teams the
ability to apply new frameworks, libraries, and records resources. the main concept is that
microservices architecture intentionally leverages agile concepts, in which the development
attempt is unfold across go-purposeful teams that work extra independently.
Classification Setup: -

The idea is to build an API for the Payment API Gateway. For this purpose, there is two
separate APIs built to perform the complete two different services. The different service
would be :

User_Service : It’s main tasks would be

-create a new user.
-Get all the users
-Get user by Id.

Wallet_Service : It’s main tasks would be

-Update the wallet.
-Create Wallet.
-Get wallet, if required.

Transaction_Service : It’s main tasks would be

-We should be able to send money from one user to another.
-We should be able to get the money.
-We should be able to sent transaction to the user if he wants on their mail.

One major gain of a charge API is that it can enhance a consumer’s purchasing
experience via casting off the want to fill out checkout forms, a tedious venture - mainly
on a smartphone - which can lead to purchasing cart abandonment. thanks to the ability to
reuse saved charge statistics, clients can entire a purchase on a cellular tool with just a
few faucets.

Figure 5. Different services to be used in the API

The below are the some glimpses of the code written to make an API functional :

Figure 6. Code for Controller class

The above class is a controller class. The most of the functions or the requests which are
passed to the API are functional here. The controller class is for the user_service API.
1. The first request in above code if the @GetMapping , which returns all the users
to the client in the form of JSON or XML.
2. The second request is the @PostMapping , which is to register a new user into the
MySQL database.
3. The third and the last request is the @GetMapping for finding the user by id.

Whenever the function is called, the controller is called by the main class to function, and the
identity of the controller class is recognized by the @RestController annotation of the java
class.
 Figure 7. Model class of the API

The above class is the model class named User.java. The structure of an API and data
consumed by the API is all designed in this class. @Entity is used for Object Relational
Mapping in this class.

The below image is the complete structure of the User_Service API .The controller and
model class is discussed above. The Repository class is the class which connects the MySQL
database to the application .The functionality of each package is given below:

1. Controller- It contains classes for request mapping.

2. Exception- It contains classes for exception handling in the project.
3. Model- It contains the classes defining the model structure of the API.
4. Repository- It contains the classes which connects the database with the particular
model class.
Figure 8. Project Structure of an API