0% found this document useful (0 votes)
7 views5 pages

Payment Systemm

The document outlines the development of a Payment Gateway API designed to enhance e-commerce transactions by providing various services such as user management, wallet operations, and transaction handling. It emphasizes the importance of security through user authentication using hashing algorithms and discusses the technologies and methodologies employed, including microservice architecture and Java with SpringBoot. The project aims to improve user experience by streamlining the checkout process and consolidating transaction data for better business insights.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
7 views5 pages

Payment Systemm

The document outlines the development of a Payment Gateway API designed to enhance e-commerce transactions by providing various services such as user management, wallet operations, and transaction handling. It emphasizes the importance of security through user authentication using hashing algorithms and discusses the technologies and methodologies employed, including microservice architecture and Java with SpringBoot. The project aims to improve user experience by streamlining the checkout process and consolidating transaction data for better business insights.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 5

provide the services to the various online purchasing e-commerce companies and

more.

1.3 Objectives

• The goal of the undertaking is to offer a fee gateway API version to correctly test
and maintain the API and make the API capable of work smoothly. in this work,
we gift a semi-supervised gaining knowledge of method that outperforms, even
greater, the performance of API in terms of the modelling of the API and the
relationship between the two APIs which is established thru the relaxation
Template. There are distinctive functions that can or won't be to be had,
depending at the API and processing platform. as an example, there’s the
capability to save transactions offline and feature them processed whilst capability
is restored. Or the API can be able to aid a diverse array of diverse transaction
types past the fundamental card manufacturers and not unusual charge strategies.

• furthermore, a rate API can be able to consolidate all the statistics transmitted via
the platform, thereby providing useful statistics that has the potential to inform
business organization and advertising and advertising and marketing choices.

• The security is one of the most important aspect of any API or a website. For
authentication purposes, it is also necessary to use some technology to
authenticate the user in the APIs. For this objective, I have used the hashing
algorithms in both the APIs.

1.4 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 :

4
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 fundamental gain of a rate API is that it may beautify a client’s shopping enjoy
through doing away with the want to fill out checkout bureaucracy, a tedious challenge -
especially on a telephone - that may result in shopping cart abandonment. thanks to the
capacity to reuse stored rate information, customers can complete a purchase on a cell
device with only a few taps.

Figure 2. Different services to be used in the API


5
1.5 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

• Hashing Algorithm

• Authentication

Technologies Used:

• Java

• SpringBoot

• Swaggers

• Hibernate

• Rest Template

• Actuators

• MySQL

Every of the technologies are freely to be had and the technical capabilities required are
attainable. Time obstacles of the product development and the benefit of implementing
the usage of those technologies are synchronized. From these it’s clean that the
assignment is technically feasible.

6
2. Chapter-2: LITERATURE SURVEY
Price Gateway APIs

A fee gateway API integrated with present virtual methods can connect a checkout system to

a fee community.

Advantages of a price Gateway API

Figure 3. Benefits of payment Gateway API


7
The widespread adoption of virtualization, microservices, and cloud-native technologies has
made API-based interaction between service entities the standard. Due to commercial needs,
many platforms still maintain a huge number of obsolete APIs. Simultaneously, many new APIs
are increasingly becoming available. If your API communicates with a third-party app, you
should be curious in how that app distributes data to the Internet. For example, you might not be
concerned about someone learning the contents of your refrigerator, but you might be if that
individual can use the same API to locate you. So, the one of the important things to give an
attempt to have a secure adaption of the API.

One of the most critical aspects of any API or website is security. It is also required to employ
some technique to authenticate the user in the APIs for authentication reasons. I used the hashing
techniques in both APIs to achieve this goal.

Figure 4. flow chart of the authentication implementation

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy