E- Payscanning

Dept of Information Technology

Faculty of Computing
International Islamic University Islamabad

Submitted by: (IT kunoichi)

Busra Bibi 766-FOC/BSIT/F22C
Zarfshan Haroon 815-FOC/BSIT/F22C
Rimsha Mushtaq 745-FOC/BSIT/F22C
Mahzaib Fatima 824-FOC/BSIT
/F22C Noor-ul-ain 827-FOC/BSIT/F22C

Submitted to:
Mr. Imran Saeed
About E-payscanner

Table of contents:

Introduction to E-paysanner:
1.1 purpose
1.2 Scope of E-paysacnner:

2.Functional requirements of E-paysanner

software:

1. Payment Request Commencement

2. Epayscanner for payment
3. Epayscanner for payment
4. Processing in batches
3.1User roles and requirements
3.2Core features
Non-functional requirements of Epayscanner

2. USE CASE DIAGRAM

 1. INTRODUCTION TO E-PAYSCANNER:

E-commerce has led to the emergence of new financial desires that weren't there with traditional
payment methods. Many various payment systems and processes were put into place to facilitate
online business transactions as a result of the rise of e-commerce. As a result, the stakeholders
developed new e-payment strategies. Acknowledging this, nearly all interested parties are
investigating various forms of electronic payment systems and issues related to digital currency
and electronic payment systems. Online MasterCard Payment, Online Electronic Money System,
Electronic Cheque, and Cards-based e-Payment System are the four main categories of e-payment
systems. For both buyers and sellers, every payment method has advantages and disadvantages.
Convenience, cost, security, traceability, privacy, acceptability, and control are the edicts of new
payment systems.
Scanners that accept electronic payments provided quick, safe, and easy ways to process
payments. The features of the software are listed in depth in this paper. It makes
understanding the intended user base, suitable user instruction, and requirements for
internal and external interfaces easier..

1.1. PURPOSE:
The purpose of this document is to discuss the standards needed for e-payscanners.

• Offering a smooth, safe, and adaptable way to process electronic payments is the main goal of an
electronic payment scanner.These scanners are designed to streamline the payment acceptance
process for businesses, reducing errors, expediting checkout times, and raising overall customer
happiness. It strives to satisfy the evolving demands of companies and consumers in an
increasingly digital environment by offering a range of payment choices and ensuring usability.
They serve as a conduit between consumers and companies, providing secure methods for
accepting debit, credit, and contactless payments in addition to security features to guard private
financial information.
1.2 Scope of E-pay scanner:

The scope of E pay scanner typically involves security processing electronic transaction
preventing fraudulent activities in online payments . it play a crucial role in facilitating secure
digital transaction and safeguarding sensitive information during online financial transactions.
1 Transaction security:
Encryption: utilize advanced encryption protocol to secure the
transmission of sensitive financial data.
Tokenization: Implements tokenization techniques to replace actual card.
2 Fraud detection and prevention:
Anomaly detection: monitors transactions pattern to identify unusual behavior.
Behavioral Analysis: Analysis user behavior and transection history.
3 Payment integration:
Compatibility: Ensures seamless integration with various payment gateways, cards
, digital wallets and bank transfer.
API Support: provides robust API with e-commerce plateforms and other digital services.
4 Regulation and compliance: The Payment Card Industry Data Security Standard (PCI DSS) is
followed to ensure the safe processing of credit card data.
5 User Authentication: MFA: To improve user identity verification, MFA was implemented.
Biometric integration lowers the possibility of unwanted access by supporting biometric
authentication.
6 Sixth, real-time reporting and monitoring:
Monitoring: continuously keeps an eye on real-time intersection trends. Reporting: produces an
in-depth analysis of transaction patterns.
7 Performability and scalability:
Scalability: Capable of managing different transsection volumes.
8 Using load balancing techniques, loads can be distributed over numerous servers in an
efficient manner.
9 Customization and setup:
Configurability: Provides parameters that can be changed to suit a given situation.
10 Support for mobile and cross-platform:
Ensure that the product is compatible with handheld technology.
11 Cross-platform integration: Facilitates exchanges between different platforms.
12 Customer support and training:
Training resources: provides educational materials and training resources for users and
businesses to maximize the effective use of E-payment scanner.
Customer support: Offers responsive customer support to address queries and provide
timely assistance.
 2. FUNCTIONAL REQUIREMENTS OF E-Pay scanner software:

App can provides to customer the following functions:

Processing in batches :

 creates the batch breakdown based on the rules governing the payments that Financial
Services Providers are entitled to receive, among other things (REQUIRED)

 combines payments made to the same beneficiary with additional payments (REQUIRED)

 Determines the rate of batch failure (REQUIRED)

Batch files are put through one last inspection to make sure they are error-free and consistent, and
if needed, they are cross-checked with other systems:

 Batch processing is queued at high volumes (REQUIRED)

 Low-level verification of the completeness and type of data (REQUIRED)

 Account lookup verification to make sure the data matches what the destination system
wants (REQUIRED)

 Look for discrepancies (REQUIRED)

 As far as possible, auto-correct things; if recipient banks and telecoms need it, consistency
logic can be used to fill in any formatting gaps (REQUIRED)

 Errors are sent back to the program level or (REQUIRED) to an internal data review
process.

Payment Request Commencement:

• An internal or external source may submit a request (REQUIRED)

• Another GovStack Building Block (such as the Registration Building Block, Social
Benefits Registry Building Block, or Payroll) could be an external source. To make
the request, one of the sources needs to be duly approved and authenticated.

• The start can be asynchronous (usually for payments in batches) or synchronous (usually
for a single payment) (REQUIRED)

• The minimal information that must be included in the request is the payer's and payee's
unique transaction IDs, the amount, currency, policy, and starting source. An ID supplied
by the payment orchestration module must be included in the internal payment request
(REQUIRED)

• Proof of intent from the user may be required for some transaction flow procedures, such as
inputting the PIN or password or clicking the "accept" key to start the payment process. For
audit trail purposes, such occurrences and their results ought to be documented. However, it
is NOT RECOMMENDED for PINs and passwords to be kept in logs; instead, they should
 be hashed out.

Event Logging

Every part of the Payments Building Block must to be able to generate transaction logs in addition
to application logs. To make sure that the system can be sufficiently monitored and that
troubleshooting can be done quickly and effectively, this is crucial.

 Application or event logs, which record the actions taken by each

component, must provide the following details (REQUIRED) at the very
least:

 Application/user ID o Time and date of the occurrence

 The IP address or name of the terminal

 Information about the event (message or code)

 The outcome of the event

The components must additionally provide transaction logs that record the minimum amount of
data (REQUIRED) listed below:

 The time and date of the transaction;

 The source and destination of the transaction; o Any supplemental information; o The
transaction status (success, failed, in progress)

 Passwords and other sensitive information shouldn't be recorded in the event or transaction
logs. (REQUIRED)

 Every payment transaction should have its own transaction record. For instance, if a
payment process is carried out in batches, it is advised that separate event logs for each
batch be kept in addition to transaction records for each individual transaction.
Epayscanner for payment:
A payment gateway (REQUIRED) enables data exchange and interaction between different
Financial Service Providers (FSPs) that provide digital services.
• Send and receive transactions (REQUIRED)
• Transactions must be accepted or denied, and client accounts must be credited or debited.
2.1 Roles and requirements for users:
Typical worker:
Typically, clients are not well educated and may not be computer proficient; the user takes orders,
assists customers, and processes payments.
A company that provides electronic payment services, such as easy pasa, jazz cash, google pay,
pay pal, and credit card systems, and that charges a fee for electronic transactions is known as
epayscanner.
System administrator:
Typically users have high level of professional education, are computer literate and receive
training in the product process, these users performs administrative tasks and configuration of
the system.

Epayscanner software:
An electronic server that the payment provider provides, which
communicates with the point of sale for the payment transaction; an API that
enables the point of transfer of funds and transaction payment; these can be
managed by the Epayscanner app, which also features a refunds system and
the ability to accept or reject transactions.
 Capability to scan barcodes, QR codes, and receipts using a variety of
scanners and mobile devices.
 Enable electronic payment processing by offering a range of payment
options, including credit cards, internet transfers, e-wallets, and more.
 Make sure that sensitive payment and scanned document data is
transmitted and stored securely by using data encryption.
 Integration: Capable of integrating for smooth data transmission with databases,
accounting software, and other pertinent systems.
 Efficient storing and retrieval of scanned documents and financial transaction
records is known as search and retrieval.
 Reporting and Analytics: Produce reports and offer data on payments and
document scanning operations.
 2.1 CORE features:
User registration..
When application is installed, the user presented with an initial registration screen prompts the
user to create a account /personal info on the Epayscanner by using the number or addition
choice to add email address(for lose account) complete the process
User Validation:
After process complete for user validation the unique link or code send to user on their number
or a email address whose used in to create account.
Epayments accounts:
 User have to add their all payments accounts like easipaisa, jazzcash, Credit Card
Payments, Bank Transfers, Debit Card Payments, google pay etc
 Transfer money by adding number with more choice like to add bank account details(
attached to banking system)
 EScanner system by QRcode or a barcode to point of product selling.
User stories:
Transfer Money:
When a user of an app wishes to send money to a friend who has an Easypaisa account, they add
the friend's number and the amount they want to transfer, and the app notifies them of the
transaction and displays their current balance. All of the records are saved within the app. The
friend who received the money must show a message to accept or refund it. Not required for both
the sender and the recipient to have the ePayscanner app, but at least one of them must.

Refund system using QR code:

 A client wants his money returned after purchasing some goods and paying with a scanner.
 The consumer visits the record transaction receipt page and shows it to the seller. The seller
then chooses to enter the transaction ID of the customer's receipt and selects the refund
option (the transaction ID can also be obtained from the stored customer's receipt).
 Refund receipts are printed by the point of sale upon transaction acceptance, and
transaction receipts are notified by Epayscanner. If the consumer wants to capture data
physically, they can also print the transaction receipts.
 3. NON FUNCTIONAL REQUIREMENT OF E PAYMENT:

Software engineering, non functional requirement for an electronic payment scanner:

1. Performance:
To reduce transaction delays, make sure that payment information is scanned, processed,
and validation quickly and efficiently
2. Reliability:
From the perspective of the user, dependability is crucial since the availability of the
payment infrastructure is necessary for an organization to function smoothly.
3. Security:
Put strong security measures in place to guard private financial data, such as encrypting data as it
is transferred and stored.
4. Trust:
• Have faith While there are many other characteristics in this system, trust is the most
crucial one. To add the greatest number of properties to the system, proper validation is
necessary. An essential quality is trust. In electronic payment systems, trust is a feature
that guarantees the sharing of personal information, the security of money, and the non-
aggression of parties towards the user. A user's level of confidence in any electronic
payment system is reflected in their level of trust.
• The user has faith in the payment system since they think their money won't be
misappropriated or pilfered. Users are of the opinion that merchants, banks, and credit
card firms won't utilize their information against them, despite the system's imperfections.
Another way to look at trust is to say that other people should also be able to trust the
payment methods that users choose to employ since only then would they be willing to do
business.
5. Scalability:
The need for a payment infrastructure and the demand for internet use for business purposes are
intertwined. To prevent performance degradation, the payment infrastructure needs to be
scalable and able to cope with the addition of merchants and users. Systems that demand
hardware installation and purchases from suppliers and users are the least scalable and impede
the advancement of electronic currency systems. Build the program so that it is adapted to
changing transaction loads and growing usage without sacrificing efficiency.
6. Usability:
 Usability or ease of use: This refers to the simplicity of using an electronic payment system
to make payments. Payments must be error-free, straightforward, and entirely automated.
Usability is a crucial feature that is described as "the extent to which a product can be used
by specified users to achieve specified goals with effectiveness." Since making an
electronic payment is a very responsible duty, there should be minimal factors that could
make the process boring or challenging.
 Make sure that customers can comprehend and utilize the payment scanner software by
designing an intuitive user interface that facilitates easy interaction.
7. Compatibility:
Payment methods are typically selected by users as financial tools based on their
requirements. Different payment schemes cater to different user demands by providing
a range of services and applications. As these schemes have developed, new systems
are likely to arise. Money should be able to move freely between different
 representations. to accommodate several card types, payment methods, and electronic
payment standards.
8.Traceability:
Traceability is a feature that is linked to anonymity. Traceability is the degree to which
monies, money flows, or linkspent funds may be easily traced back to a client through
payment operations. In a number of flicks, including Fast and Furious, authorities are
able to track down those who use credit cards both domestically and abroad. It follows
that credit cards can be tracked down. Privacy and traceability are two crucial qualities
that encourage trust.
USE CASES DIAGRAM:
Transfer money:

Reciver
number validated

accepted
Type amount

reciver
Get money
sender

send

N
ot
if
C ie
h d
e
c
k A
p
b
p
Service al n
administrater a ot
n if
c ie
e d
 Refund system:

Purch
ase
produ
Confi
ct
rm
refun
d
Scan QRcode

App
Confrm notifi
transfer es

Wants refund

Acc
c ept
u requ
s est
Request for
t
refuund
o
m Bill updates
e
r

Product
seller
Proce
ss
refun
d