Synopsis for Google pay(Gpay). You will get a basic idea for the srs of Google pay application.

1. Synopsis
For
By
Siddharth Kumar
Reg. no.-11807346
Section-K18HA
Roll no.-59
Submitted to:- Manik Sir

2. Table of contents
1. Introduction
1. 1 Purpose
1.2 Scope
1.3 Overview
2. Functional requirements
2.1 Registering feature
2.2 Adding Bank account
2.3 Identify the location at the time of
Transaction.
2.4 Cash mode
2.5 Notification
2.6 Shopping
3. Non-functional requirements
3.1 Availability
3.2 Performance
3.3 Modifiability
3.4 Reliability
3.5 Security

3. Introduction
Purpose
Google pay, this application helps the users for online
payment and tap to pay purchases on mobile devices, which
allow users to pay on a single tap. Other advantages are that
users can also pay bills, they can shop, too.
Scope
• There is one basic user here that is registered
customers.
• At the time of registering customer is asked to link
the bank to simplify online payments.
• Here customers can send and receive money and
they can also shop online from ecommerce
websites and much more for online transactions.
• Customers also get cashback offer on special online
transactions.
Overview
Drawbacks
• People who doesn’t have knowledge of
computer and internet cannot use the system.

4. Functional requirement
1. Registering feature: GPay allows you to register with
your phone number and preferred language. Once
you are signed up it will send you an OTP to confirm
your number then it will confirm your Gmail account.
2. Adding Bank account: This allows users to do the
transaction directly from the bank which makes it
different from others. You can add more than one
bank account in a single GPay account.
3. Identify the location at the time of transaction: GPay
obtains the geographic location of a device to give
additional security on transactions.
4. Cash mode: It features a technology called audio QR
that allows users to transfer money using sounds to
pair two devices.
5. Notification: you get a notification after each
transaction whether the transaction is completed or
not.
6. Shopping: the users can shop here and pay bills.
Non-functional requirements
Availability:

5. • The application should be available for 24 hours
• The web server should support every platform and could
be opened on mobile phones, tablets, and PC
Performance:
• The application should be fast and respond to users
within 1 second
Modifiability:
• The application should provide user to modify and
manage data
Reliability
• The system should update and show transactions real-
time
Security:
• Security requirements ensure that the software is
protected from unauthorized access to the system and its
stored data. It also includes protection against viruses
and malware attacks.