Scribd
Upload
81 views

Developing A Scalable Payment Gateway Using Scala

This document summarizes a project to develop a scalable payment gateway using Scala. The project aims to address limitations of existing payment gateways like low success rates (<50%) and high fees. By using Scala's actors model and immutability, the project intends to boost scalability, improve reliability, and increase transaction success rates. It will divide work across a merchant side, payment gateway, and bank side. The goals are defined as using Scala to boost scalability and increase overall system reliability and development productivity.

Uploaded by

Tarika
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
81 views

Developing A Scalable Payment Gateway Using Scala

This document summarizes a project to develop a scalable payment gateway using Scala. The project aims to address limitations of existing payment gateways like low success rates (<50%) and high fees. By using Scala's actors model and immutability, the project intends to boost scalability, improve reliability, and increase transaction success rates. It will divide work across a merchant side, payment gateway, and bank side. The goals are defined as using Scala to boost scalability and increase overall system reliability and development productivity.

Uploaded by

Tarika
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

SYNOPSIS

1 Group Id
Group Id:24

2 Project Title
Developing a scalable payment gateway using scala.

3 Project Option
Industry sponsored

4 Internal Guide
Prof. M. R. Patil

5 Sponsorship and External Guide


Sponsored by Persistent Systems Ltd.
External Guide : Ms. Tejaswini Pethe

6 Technical Keywords (As per ACM Keywords)


1) Payment Gateway
2) Play Framework
3) Actors Model

7 Problem Statement
We all want an online transaction system providing maximum reliability in trans-
actions.Today we have too many payment gateways with far less success rate than
what ideally should be. The existing system has many loopholes because it cannot
handle a large amount of traffic, which results in many rollback failures. Improv-
ing the scalability of the system will increase the success rate and reliability of
the system thereby increasing the overall experience of the customer. We will use
Scala technology to improve the scalability of the payment gateway.
SYNOPSIS

8 Abstract
• With expansion of the Internet, many electronic commerce systems have
been developed and put into practice. At the same time, several electronic
payment gateways are introduced. The current payment gateways in India
provide the success rates of less than 50 percent only. The proposed pay-
ment gateway will overcome the drawbacks of the existing payment gate-
ways by using scalable language like Scala. Scala is an object-oriented
language which uses immutability to handle concurrency. Also, the setup
and transaction discount rate (TDR) fees in the current payment gateways
are high which makes it difficult for start-up companies to access them.

9 Goals and Objectives


• Using Scala we are trying to boost applications scalability. Thus, increasing
overall reliability of the system and development productivity.

10 Relevant mathematics associated with the Project


System Description:
• Input:
S = C,P,PC
C= C1, C2, C3, —C gives the customer details
P = V1, V2, V3, — P gives the product details
PC = K1, K2, K3, — PC gives the product cost
• Output:
S = St
St = St1, St2, St3, — St gives the status of the transaction.
• Identify data structures, classes, divide and conquer strategies to exploit dis-
tributed/parallel/concurrent processing, constraints:
The Project is divided into three modules. First is the merchant side, second
is the payment gateway side and third is the bank side. The Merchant side
and the payment gateway side uses a single database for the customer vali-
dation and storage of the customer details. The application uses the model
view controller software architecture for implementing user interfaces. It
divides a given software application into three interconnected parts, so as
to separate internal representations of information from the ways that infor-
mation is presented to or accepted from the user.
SYNOPSIS

• Functions :
S = C, P, A, F
F = F1(), F2(), F3(), F4(), F5()
F1 (C):: Fetch customer details .
F2 (P):: Product details
F3 (A):: Authenticates Customer
F4 (F):: display the transaction details

• Mathematical formulation if possible

• Success Conditions: When the transaction status is returned to the merchant


system. The number of users that the system can handle is a bit more than
20,000. And the transaction is securely implemented. And transaction is
atomic in nature.

• Failure Conditions:If the Load handling capacity of the system fails. That is
if the number of users accessing the payment gateway is more than 30,000
at the same time. And security of the system is compromised.

11 Names of Conferences / Journals where papers


can be published
• IEEE/ACM Conference/Journal 1

• Conferences/workshops in IITs

• Central Universities or SPPU Conferences

• IEEE/ACM Conference/Journal 2

12 Review of Conference/Journal Papers support-


ing Project idea
1)Journal paper from IEEE 2003 by Bo Meng and Qianxing Xiong
In this paper working of electronic payment model working is described.
2)Paper by Heiko, Andrei and Hans-Jorg IEEE 2000
In this paper, automatic generation of reliable e-commerce payment processes are
discussed.
3)Research paper on secure Payment system for electronic transaction by Ajit
Singh, Karan Singh, Shahazad and M.H.Khan:
SYNOPSIS

In this paper, a review of secure electronic payment system for an internet trans-
action is given.
4)Journal Paper from IEEE 2006
This paper proposes WhoPay, a peer to peer payment system that provides ano-
nymity or scalability.

13 Plan of Project Execution

Activities Start Date End Date


Requirement analysis 10-8-15 15-8-15
Project analysis 16-8-15 19-8-15
Project Design 21-8-15 2-9-15
Feasibility Study 4-9-15 6-9-15
Documentation SEM I 26-9-15 7-10-15
Development Setups 20-12-15 30-12-15
Coding 2-1-16 28-2-16
Testing 3-3-16 16-3-16
Bug Fixing 20-3-16 10-4-16
Documentation SEM II 15-4-16 15-5-15

Table 1: Project Planner

You might also like