100% found this document useful (1 vote)
1K views3 pages

Whatsapp Pay: Stakeholders

The document describes WhatsApp Pay, a proposed payment feature within WhatsApp. It outlines the various stakeholders that would be involved, including WhatsApp users, banks, and credit/debit card providers. It also discusses potential risks, performs a SWOT analysis, and outlines functional and non-functional requirements for the system. Key aspects of the proposed system include a user-friendly interface, ability to link bank accounts and make payments to contacts via UPI.

Uploaded by

Manik Manchanda
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
100% found this document useful (1 vote)
1K views3 pages

Whatsapp Pay: Stakeholders

The document describes WhatsApp Pay, a proposed payment feature within WhatsApp. It outlines the various stakeholders that would be involved, including WhatsApp users, banks, and credit/debit card providers. It also discusses potential risks, performs a SWOT analysis, and outlines functional and non-functional requirements for the system. Key aspects of the proposed system include a user-friendly interface, ability to link bank accounts and make payments to contacts via UPI.

Uploaded by

Manik Manchanda
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

WhatsApp Pay

STAKEHOLDERS

ACTOR What he can do on the Software Created


WhatsApp  Users can send messages and receive messages instantly
users without any extra cost
 Users can add privacy lock to their application
 Users can do good quality video call and voice call without
paying any extra charges
 Users can make payment to their contacts and on other UPI
through WhatsApp pay feature
 Users can update status for their contacts to pass on the
information to everyone in their contact list
 Users can create backup of their chats if anything happens to
device so that they can recover chats.
 User can share media, files and even their live locations also.

Banks  Multiple bank account can be linked so that the payment can be
made directly through account to another account.

Credit card  Credit card should be linked with account so that the UPI
providers registration process can be completed.

Bank (debit  Debit card should be linked with account so that the UPI
card provider) registration process can be completed.

Risk Identification

 Identify and mention the risks that might occur in the system and process.

SWOT Analysis of WhatsApp pay

Perform SWOT Analysis for the system.


Strengths:
Weakness:
Opportunity:
Threat:
PROPOSED SYSTEM

What is the proposed solution or system? Mention in points how the system itself will be for the
user.

● User friendly interface


● …
● …

SCOPE using Use Case Diagram (UML)

Create a use case diagram including all the actors and processes for an end to end process of the
system.

IN SCOPE

The In-scope requirements are as follows: 1. New Payment Feature for WhatsApp user 2. Add New
Payment Option 3. Remove Payment Option 4. Scan QR code for making payment option 5. Approve
Payment Request 6. Reject Payment Request 7. Report an Issue 8. View Transaction History both
overall and per user.

OUT OF SCOPE

The out-of-scope requirements are as follows: 1. New Bank Account Creation 2. Virtual Wallet
Money in form of virtual points 3. Money Transfer without linking payment methods/account (at
receiver’s end) 4. Transfer money to non-WhatsApp QR codes

Business Requirements:

Business Objective: • Have at least 1 million users use WhatsApp pay feature within the first 3
months of launch. • Over 1 year of its launch have 30% of user base using WhatsApp pay. • Be
among top-5 market players in the first year of launching

FUNCTIONAL REQUIREMENTS

1. New Payment Feature for WhatsApp user 2. Create Pin 3. Change Pin 4. Add New
Payment Option 5. Remove Payment Option 6. Block a Contact 7. Un-block a Contact 8.
Scan QR code for making payment option 9. Approve Payment Request 10. Reject
Payment Request 11. Report an Issue 12. View Transaction History both overall and per
user. 13. Change Language Feature
NON-FUNCTIONAL REQUIREMENTS
Write all the nonfunctional requirements for the system.

System Requirement:

1. Existing WhatsApp Chat platform technology should be used to develop the WhatsApp Pay as well
to ensure tight integration between the two. 2. Feature should be available in multiple languages
and should support transactions in different currencies 3. Strong Encryption Technologies should be
used as user PI data would be stored 4. The transactions should be end to end secured via secured
Internet Protocols and encryption 5. The backend data base should be highly scalable and should use
redundancy and mirroring to ensure availability of services all the time 6. The system performance
should be optimized and should not degrade considerably based on the internet speed fluctuation of
the user

Usability:

1. The screens should be self-explanatory and very user friendly. 2. Screens should use the current
WhatsApp aesthetics and themes in the WhatsApp Pay pages as well to ensure user familiarity. 3.
There should be FAQ section available to answer generally asked queries

Screen Wireframes
Create wireframes for every screen that will appear to the users.

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