Requirement Specification

Oneload MiniApp Integration

EP-Systems

By

Oneload MiniApp RS Page 1

Document Overview

Title Requirement Specification Versio 1.0

n
Project Oneload MiniApp Status Approved
Client E-Processing Systems Pvt. Type Internal/
Ltd. External
Doc # EP-Systems Doc November 15,
Date 2023
Author Saif ur Rehman Last December 08,
Save 2023

Description:

The purpose of this document is to record and present a detailed description of the process to
provide Oneload MiniApp to Partner’s App.

Oneload MiniApp RS Page 2

Revision History

Ver. # Rev Author Distributi Brief Description

Dat on Date
e

Approved By

Name Role Version

Muhammad Bin Director Digital Version 1.0
Zaheer Enablement

Oneload MiniApp RS Page 3

Table of Contents

PURPOSE

OVERVIEW OF DOCUMENT

SCOPE

CLIENT REQUIREMENTS
EXISTING PROCESS
PROBLEMS SUMMARY

SOFTWARE REQUIREMENTS
FUNCTIONAL REQUIREMENTS

E- Load
Validations
Error Messages

Bill Payment
Use Case
Validations
Error Messages
Transport
Use case

Telemart
Use Case

Oneload MiniApp RS Page 4

INTRODUCTION

PURPOSE

The purpose of this document is to outline the comprehensive requirements for the development
of the OneLoad as Mini App, a prepaid load/bundles, Ecommerce, transport, bill payments and all
upcoming services available to Oneload retailers, distributors and individual customer in Pakistan
extend to Partner’s app and using Partner’s Wallet for transactions. This document serves as a
roadmap for the development team, ensuring a high level understanding of the features set ,
functionalities, and user expectations for the successful implementation of the OneLoad as Mini
App.

DESCRIPTION
The OneLoad Mini App is designed to be a versatile platform offering a prepaid load/bundles,
Ecommerce, transport, bill payments, and all upcoming services to the Parent’s/ Partner’s App.
The app will be replica of current Oneload App and will facilitate users in seamlessly top up their
mobile, purchasing bundles, settling various utility bills and other services offered on onload
Platform within a user-friendly interface and without any account/login credentials of Oneload.
Key features include:

 E-Load Services:
o Mobile top-up and bundles for all telecom operators

 Bill Payment:
o Utility bill payments, including electricity, water, gas, and others currently available via
Nadra or 1 link.
 Transport:
o Purchasing bus tickets for now, and whenever other transport options will be viable to
Oneload, they will be shown to partner’s users using MiniApp.

Oneload MiniApp RS Page 5

  Telemart:
o Users will be able to buy Telemart products online termed as Ecommerce using the
Partner’s Wallet as Payment Method. The entire flow will remain the same as it has
already been integrated in the Oneload App.

Partner readiness documents:

There will be two documents provided by tech which the partner needs to comply.
1. Onboarding document

Partner Onboarding:
Partner A/c along with wallet id will be registered on Oneload before technical integration
process initiated between parties for this Partner needs to sign NDA, commercial
agreement, agreeing the defined terms and providing below details for the A/c creation

i. Company Name
ii. Company POC name
iii. Contact Number
iv. Oneload Salesperson name
v. Oneload salesperson ID
vi. Wallet ID/MSISDN
vii. Company NTN
viii. Company registration document
ix. Agreement and NDA soft copy to be uploaded.

 Services check
Jazz
1. Load
2. Bundles
Telenor
1. Load
2. Bundles
Ufone
1. Load
2. Bundles
Zong

Oneload MiniApp RS Page 6

 1. Load
2. Bundles
Bookme
1. Transport (Bus)
Ecommerce:
Telemart
Etc
Bill Payments:
 Utility
 Government
 Internet bills
 Supply payments
 Loan Payments
 Other Bill

2. Technical document:
Tech will prepare and share a document accordingly which partner will ready his services
for integration with Oneload.

Oneload MiniApp RS Page 7

SOFTWARE REQUIREMENTS

FUNCTIONAL REQUIREMENTS

The section will discuss in detail the functional requirements of this project, initial version of the
document will also include interface and transaction flow. Development of this functionality will
enable Partner application to consume all the services offered OneLoad by acquiring a Oneload
Miniapp for the services provided in real time using the Partner’s wallet.

MiniApp Technical Functionality

1. Oneload as a Provider Platform

 Oneload as a provider Platform will provide services to enable its partner’s

(OneZapp) where Oneload will act as a service provider via its responsive
designed based application.
 Both platforms will communicate using the Authentication token-based
mechanics.
 The client’s users will login to their local environment using and adhering to the
security/login mechanics of the local platform.
 After that the client user will be able to login and navigate its way to the
designated area.
 The Provider of the Mini App will allow access to mini app (read webpages).

Oneload MiniApp RS Page 8

 2. How Transaction will take place:

 Client’s user will opt for any merchandise.

 Client Platform will fetch the required information (availability, price, any discount
etc.)
 Oneload will get the confirmation along with necessary information for processing
of the order in case physical shipment is being required to make.
 The client will deduct the required amount / balance from its customer.
 Upon the processing of the order the Oneload platform will provide the client with
Tracking / Order / ID

Control Account need to be maintained between Provider and Client for Book-Keeping.
OneZapp (Payable Account) Amount which OZ need to pay to OL Debit
Oneload (Receivable Account) Amount that OL will be receiving Credit

 Upon any kind of transaction,

User Wallet (Partner’s Environment) Debit

MiniApp OZ Wallet ???? (Finance) Credit

While at the same time in General Ledger Account, (Account Statement)

OneZapp (Partner’s Debit
Wallet)
Oneload Wallet Credit

 Upon any kind of situational errors during transaction, certain messages will be shown to
the user.
 Client’s account will be created.

Oneload MiniApp RS Page 9

E- Load
Use case.
Use Case # E-LOAD-001
Description User buys e-Load
Actors Partner Eligible User
Prerequisites The user already logged in to Partner Wallet/Account
Trigger User selects Mobile E-Load from the main screen and then selects the
service provider (Zong, Jazz, Telenor, and Ufone) to proceed further
(All the functionalities are replica of Oneload App)
User Flow
1) By clicking on the Buy Load button displayed to the user requesting
the following details.
a. Load Amount
o Users have the option to either manually input the
load amount or choose from pre-configured
bundles.
b. Subscriber Number
2) A review screen will pop up where users will be asked to review the
selected bundle/load and the click on the Confirm and Cancel button.

Note: System will validate inputs according to the validations defined below, please refer the
validations table for details.

Oneload MiniApp RS Page 10

Validations
Data Element Description Format
Amount The value/amount of e-Load String, min 2 chars, max 5
Required chars, each char is a digit
from [0-9]
Mobile Number The destination cell number String, min/max 11 chars,
for the Prepaid Voucher each char is a digit from [0-
9]

Error Messages
Data Field Error Message
Amount Please enter a valid amount.

Destination Mobile Please enter a valid destination number.

No.

Oneload MiniApp RS Page 11

Bill Payment
Use Case
Use Case # Pay BILL OLD-001

Description Users select bill Payment

Actors Partner Eligible User

Prerequisites The user already logged in to partner wallet/Account

Trigger User selects Bills from the Main screen then selects the Bill
categories
User Flow
1. By selecting the bill category (Utility bills, Government bills etc),
the user is requested to fill the following detail:
a. Select Bill type.
b. Select Service Provider
c. Consumer No.
2. User provides the required details and selects View Bill button
and bill details will be displayed to the user to review and confirm
the transaction.

Make Payment

Note: System will validate inputs according to the validations defined below, please refer the
validations table for details.

Oneload MiniApp RS Page 12

Validations
Data Element Description Format
Consumer The consumer number allotted String, min/max 20 chars,
Number to services consumer alphanumeric characters allowed
only

Error Messages
Data Field Error Message
Consumer Enter a valid consumer number.
Number.

Oneload MiniApp RS Page 13

Transport
Use case
Use Case # Buy-ticket001

Description Users select Transport

Actors Partner Eligible User

Prerequisites The user is already logged-in to partner wallet/ account

Trigger User selects Transport from main screen then choose Ride Type
>> Bus.

User flow
1. Booking Details will be displayed to the user requesting the
details of journey.
a. Departure City
b. Destination City
c. Departure Date
d. Bus Service
e. Bus Route
2. By clicking on the Schedule button, choose your Bus Time screen
will pop up where user will select the desired time of the bus.
3. User then selects their preferred seat, (min 1, max multiple) and
enter customer details (Name, Gender, Phone Number, CNIC,
Age) then prompt to the review screen where user clicks on buy
button.

Oneload MiniApp RS Page 14

 4.1.1.1 Validations

Data Description Format

Element

Contact Customer String, 13 chars, each char is a numeric value

CNIC CNIC [0-9]
Number

Contact e- Customer E- String, Standard e-mail validations

Mail Mail ID

Passenger Full Name String, 255 chars, each char is an alpha-

Name numeric value

Age Passenger String, 2 chars, each char is a numeric value

Age [0-9]

Gender Passenger String (Either 0 or 1 Female=0, Male=1)

Gender

Note: Field validations need to be discussed (TBD)

4.1.1.2 Data Field Error Messages

Data Field Scenario Error Message

Passenger Invalid Input Please enter a valid Name.

Name
No Input/Empty Field Passenger Name field cannot be

Oneload MiniApp RS Page 15

 empty.

4.1.1.1 Bus Ticket Request Error Messages

Success When transaction is Your payment request has been processed

processed successfully successfully.
Inactive When requested Requested channel is not available now or
Channel channel status is inactive, the transaction cannot be processed,
blocked in Web please try again later.
Service
Internal/ When service is We are sorry, the transaction cannot be
Unspecified not responding in processed the moment, please try again later.
Error due time or is
not available
Internal / When Sorry, there seems to be a problem with the
Unspecified application payment service provider. Please try again
Error crashes due to later.
any

reason
Some Error If any error has Sorry, there seems to be a problem at the
Occurred in occurred in the utility service provider. Please try again later.
Web- web service

services of the respective

bus company

Oneload MiniApp RS Page 16

Telemart

Use Case

Use Case # Telemart-001

Description Users select telemart/Online Shopping

Actors Partner Eligible User

Prerequisites The user has already logged into partner wallet/Account.

Trigger User selects telemart from the Main screen, then selects the
desired product from the shop by category.

User Flow
1. By selecting category, the user is displayed with the variety of
products, the user will select the product of choice.
2. User clicks add to cart/buy now.
3. User prompt to the My cart screen then user click checkout
button.
4. The user provides the required details (Name, Phone number,
CNIC) and then order details will be displayed to the user to
review and confirm the payment.
5. All scenarios will be replica of Oneload App

Oneload MiniApp RS Page 17

Make Payments

Use Case # Payments-001

Description Making a Purchase Using Partner’s App's Wallet in Miniapp

Actors Partner’s System

Prerequisites The user is logged-in to Partner wallet

Trigger By clicking on the confirm button of Load, Bills, telemart/online

shopping, and transport transactions, a screen will pop up where PIN
will be required to complete the transaction. This pin will be the user
account login credential either pin or password or face detection or
fingerprint of Partner’s App.
User Flow 1. The Miniapp sends a request to the Partner’s server, asking for
authorization to proceed with the payment.
2. The Partner’s server authenticates the user and prompts the user to
confirm the payment.
3. The Partner’s server securely processes the payment transaction,
deducting the purchase amount.
4. The Partner’s server sends a confirmation message back to the
Miniapp, indicating a successful transaction.

Oneload MiniApp RS Page 18

MINIAPP TRANSACTION FLOW:

Oneload MiniApp RS Page 19

Other Requirements:

 All these requirements should be configurable for multiple partners, which service should
be given or not. Like for some partners Load and Bills would be visible while other
services like Bookme and Telemart wouldn’t. But all the services might be visible to
some partners. So, the functionality should be developed at the backend.

 Commission against every transaction should be configurable for the Partner. For
instance, if user purchases 500 bundle, then X% of the commission will go to the partner
and remaining will be with Oneload. This should be reflected in the daily transaction
report.

 Platform fees should be configurable for each service for each partner. For instance, load
transactions will have platform fee for partner X but will be free for partner Y. Both
partners can have different platform fees.

 Bills include UBP and 1-bill billers.

 Every new bundle addition, biller addition should be automatically available in the Mini-
App.

 Daily Transaction report should be like this:

DateTim Partner Partner_I Transaction_ Servic Subcatego Produ Pric Quantit OL Partner's
e Name d id e ry ct e y Commission Commission

Oneload MiniApp RS Page 20