Business Requirement Specification – Retail App

Prepared For: All

Prepared By:
Padam Jain
 Table of Contents
Table of Contents....................................................................................................................ii
Table of Figures....................................................................................................................v
1. Introduction.....................................................................................................................3
1.1 Intended Audience..............................................................................................................4
1.2 Impacted Business Function & User Groups........................................................................4
1.3 Definition & Acronyms........................................................................................................4

2. Business Processes...........................................................................................................5
1.4 GSM Sales & Services...........................................................................................................5
1.4.1 Recharge Sales................................................................................................................5
1.4.1.1 Process Flow............................................................................................................................................5
1.4.1.2 Process Summary....................................................................................................................................5
1.4.2 Recharge Sales Reversal.................................................................................................6
1.4.2.1 Process Flow............................................................................................................................................6
1.4.2.2 Process Summary....................................................................................................................................6
1.4.3 Bundles Sale Reversal.....................................................................................................7
1.4.3.1 Process Flow............................................................................................................................................7
1.4.3.2 Process Summary....................................................................................................................................7
1.4.4 Bundles Sale...................................................................................................................8
1.4.4.1 Process Flow............................................................................................................................................8
1.4.4.2 Process Summary....................................................................................................................................8
1.5 My Stock - GSM...................................................................................................................9
1.5.1 Check EVD Balance.........................................................................................................9
1.5.1.1 Process Flow............................................................................................................................................9
1.5.1.2 Process Summary..................................................................................................................................10
1.5.2 Stock Request - EVD.....................................................................................................10
1.5.2.1 Process Flow..........................................................................................................................................10
1.5.2.2 Process Summary..................................................................................................................................10
1.5.3 Send EVD to Retailer using AM.....................................................................................11
1.5.3.1 Process Flow..........................................................................................................................................11
1.5.3.2 Process Summary..................................................................................................................................11
1.5.4 Buy EVD – Own Account using AM & Other Payment Option......................................11
1.5.4.1 Process Flow..........................................................................................................................................11
1.5.4.2 Process Summary..................................................................................................................................11
1.6 AM Sales & Services...........................................................................................................12
1.6.1 Cash In..........................................................................................................................12
1.6.1.1 Process Flow..........................................................................................................................................12
1.6.1.2 Process Summary..................................................................................................................................12
1.6.2 Cash Out – CP Initiated.................................................................................................13
1.6.2.1 Process Flow..........................................................................................................................................13
1.6.2.2 Process Summary..................................................................................................................................13
1.6.3 Cash Out – Customer Initiated Using Agent Code........................................................14
1.6.3.1 Process Flow..........................................................................................................................................14
1.6.3.2 Process Summary..................................................................................................................................14
1.6.4 Cash Out – Customer Initiated Without Agent Code....................................................15
1.6.4.1 Process Flow..........................................................................................................................................15

Confidential Page 2
 1.6.4.2 Process Summary..................................................................................................................................15
1.6.5 AM Transaction Reversal..............................................................................................16
1.6.5.1 Process Flow..........................................................................................................................................16
1.6.5.2 Process Summary..................................................................................................................................16
1.6.6 Agent Float Deposit – Parent to Child...........................................................................17
1.6.6.1 Process Flow..........................................................................................................................................17
1.6.6.2 Process Summary..................................................................................................................................17
1.6.7 Agent Float Deposit – Child to Parent...........................................................................19
1.6.7.1 Process Flow..........................................................................................................................................19
1.6.7.2 Process Summary..................................................................................................................................19
1.6.8 Agent Float Withdraw..................................................................................................20
1.6.8.1 Process Flow..........................................................................................................................................20
1.6.8.2 Process Summary..................................................................................................................................20
1.7 My Stock - AM...................................................................................................................21
1.7.1 Check AM Wallet Balance.............................................................................................21
1.7.1.1 Process Flow..........................................................................................................................................21
1.7.1.2 Process Summary..................................................................................................................................21
1.7.2 Stock Request - AM......................................................................................................22
1.7.2.1 Process Flow..........................................................................................................................................22
1.7.2.2 Process Summary..................................................................................................................................22
1.7.3 Agent to Agent Float Transfer......................................................................................22
1.7.3.1 Process Flow..........................................................................................................................................22
1.7.3.2 Process Summary..................................................................................................................................22
1.8 Support Function...............................................................................................................23
1.8.1 Change EVD PIN............................................................................................................23
1.8.1.1 Process Flow..........................................................................................................................................23
1.8.1.2 Process Summary..................................................................................................................................23
1.8.2 Unblock EVD PIN...........................................................................................................24
1.8.2.1 Process Flow..........................................................................................................................................24
1.8.2.2 Process Summary..................................................................................................................................24
1.8.3 Change AM PIN.............................................................................................................24
1.8.3.1 Process Flow..........................................................................................................................................24
1.8.3.2 Process Summary..................................................................................................................................24
1.8.4 Reset AM PIN................................................................................................................25
1.8.4.1 Process Flow..........................................................................................................................................25
1.8.4.2 Process Summary..................................................................................................................................25
1.8.5 Unblock AM PIN............................................................................................................26
1.8.5.1 Process Flow..........................................................................................................................................26
1.8.5.2 Process Summary..................................................................................................................................26
1.9 My Account.......................................................................................................................26
1.9.1 Password Reset............................................................................................................26
1.9.1.1 Process Flow..........................................................................................................................................26
1.9.1.2 Process Summary..................................................................................................................................26
1.10 Service Request................................................................................................................27
1.10.1 Service Request............................................................................................................27
1.10.1.1 Process Flow..........................................................................................................................................27
1.10.1.2 Process Summary..................................................................................................................................27
1.11 Report..............................................................................................................................28
1.11.1 Retail App.....................................................................................................................28
1.11.1.1 My Activity............................................................................................................................................28
1.11.1.2 Commission Earned Report...................................................................................................................28

Confidential Page 3
 1.11.1.3 Commission Payout Report...................................................................................................................29
1.11.1.4 My Service Request...............................................................................................................................30
1.12 Appendix..........................................................................................................................31
1.12.1 Future Scope.................................................................................................................31
1.12.2 Open Point....................................................................................................................31

3. Assumptions and Tradeoffs.............................................................................................32

4. Dependencies.................................................................................................................33

Confidential Page 4
 Table of Figures
1. RECHARGE SALES - PROCESS FLOW........................................................................................5
2. RECHARGE SALES REVERSAL - PROCESS FLOW...........................................................................6
3. BUNDLES SALE REVERSAL - PROCESS FLOW..............................................................................7
4. BUNDLES SALE - PROCESS FLOW............................................................................................8
5. CHECK EVD BALANCE - PROCESS FLOW..................................................................................9
6. EVD STOCK REQUEST - PROCESS FLOW................................................................................10
7. SEND EVD TO RETAILER USING AM - PROCESS FLOW..............................................................11
8. BUY EVD FOR SELF USING AM - PROCESS FLOW....................................................................11
9. AM CASH IN - PROCESS FLOW...........................................................................................12
10. AM CASH OUT – CP INITIATED - PROCESS FLOW...................................................................13
11. AM CASH OUT WITH USING AGENT CODE – CUSTOMER INITIATED - PROCESS FLOW......................14
12. AM CASH OUT WITHOUT USING AGENT CODE – CUSTOMER INITIATED - PROCESS FLOW................15
13. AM TRANSACTION REVERSAL - PROCESS FLOW.......................................................................16
14. AGENT FLOAT DEPOSIT – PARENT TO CHILD - PROCESS FLOW...................................................17
15. AGENT FLOAT DEPOSIT – CHILD TO PARENT - PROCESS FLOW...................................................19
16. AGENT FLOAT WITHDRAWAL - PROCESS FLOW........................................................................20
17. CHECK AM WALLET BALANCE - PROCESS FLOW......................................................................21
18. AM STOCK REQUEST - PROCESS FLOW.................................................................................22
19. AGENT TO AGENT FLOAT TRANSFER - PROCESS FLOW..............................................................22
20. CHANGE EVD PIN - PROCESS FLOW....................................................................................23
21. UNBLOCK EVD PIN - PROCESS FLOW...................................................................................24
22. CHANGE AM PIN - PROCESS FLOW......................................................................................24
23. CHANGE AM PIN - PROCESS FLOW......................................................................................25
24. UNBLOCK AM PIN - PROCESS FLOW....................................................................................26
25. NON AIRTEL EMPLOYEE PASSWORD RESET - PROCESS FLOW.......................................................26
26. RAISE SERVICE REQUEST - PROCESS FLOW.............................................................................27

Confidential Page 5
Change Record
Date Author Version Change Reference

8 July 2020 Padam Jain 0.1 Initial Draft

Contact Persons
# Person Email Telephone/Ext
1 Padam Jain Padam.jain@afirca.airtel.com +91 9999017943

Confidential Page 1
Document Approval

DOCUMENT REVIEW

File Name Name of Document Version XXX

Role Names Signature Date

XXXXXX
Reviewed By
XXXXXX

DOCUMENT APPROVAL

Names Designation Signature Date

XXXXXX

Confidential Page 2
1. Introduction
Retail app is a group initiative, which automate the complete new connection, SIM SWAP and tertiary sales
processes.
The solution will streamline, automate and report the following primary transactions and support processes:
Prioritizatio
Feature Sub Feature
n
New connection Prepaid mobile with FRC 1
New connection Postpaid/ Hybrid mobile 2
New connection HBB, Mifi 2
New connection MNP 3
Product sales Recharge (EVD/ AM) 1
Product sales Bundles - Data, Combo, Voice 1
Bundles - International calling, roaming, HBB
Product sales 3
packs
Product sales Segmented offer - voice, data, combo  
Servicing Edit Information 1
Servicing SIM SWAP 1
Servicing Overscratch 1
Servicing Group CI, CO (UG only) 3
Servicing AM based EVD sales to retailer 1
Servicing AM biller payment 2
Servicing IMT pick up (code based) 3
Servicing Viral voucher pick up - offnet cash out 2
Servicing OTT service tax collection (UG only) 2
Servicing CI, CO 1
Servicing Activities/ Search Records 1
Servicing Existing Customer - Airtel Money Registration 1
Servicing Agent to Agent float transfer  
Basics Auto detection of Country 1
Basics Auto detection of Language 1
Basics Change Language 1
Basics Offline Synchronization 1
Basics Login/ Logout 1
Basics Registration 2
My account Commission rules 1
My account Edit profile 3
My account Add shop tellers 3
My account Change shift  
My account Buy recharge 1
My account EVD/ AM PIN reset 1
My account Accept pull & push of AM 1
My account Retailer app password reset 1
My account Last 5 transactions - recharge sales, AM 1
My account Retailer hierarchy with contact details 2
My account Network coverage & send info to Network team 3
My account Bank to wallet, wallet to bank 3
My account Loan 2

Confidential Page 3
 My account e- learning module 2
My account SIM stock view 3
My account HBB/ Mifi stock view 3
My account AM/ EVD balance 1
Notifications New retailer scheme, New product info, others 2
Service requests AM reversal 1
Service requests ATM withdrawal 2
Service requests Recharge reversal 1
Service requests Stock request - SIM, HBB, Mifi, EVD, AM 2
Service requests SR status & tracking 1
Service requests Payment issue 1
Reports Product/ service wise transactions 1
Reports Product/ Service wise commission MTD, LMTD 1
Reports Payout 1
Promos Digital apps download - Airtel TV, Self-care app 2

1.1 Intended Audience

 BA / Architecture team – for peer review
 SMEs – for validating the requirements
 ARB team – for review and approval
 PMO team – for CR tracking purposes
 Engineering Team – for development

1.2 Impacted Business Function & User Groups

 Sales and Distribution
 Revenue Assurance
 Finance

1.3 Definition & Acronyms

Acronym/Abbreviatio Definitions
n

AM Airtel Money
DOB Date of Birth
CP Channel Partner
CPM Channel Partner Management
EVD Electronic Voucher Distribution
KYC Know Your Customer
LMTD Last Month to Date
MSISDN Mobile Station International Subscriber Directory Number
MTD Month to Date
OTP One Time Password

Confidential Page 4
RCV Recharge Voucher

Confidential Page 5
2. Business Processes
This section gives the detail of each of the required process.

1.4 GSM Sales & Services

1.4.1 Recharge Sales

1.4.1.1 Process Flow

1. Recharge Sales - Process Flow

1.4.1.2 Process Summary

Brief Description Describe the process of performing recharge on customer mobile.

CP must have enough balance either in his EVD or AM agent wallet for recharge.
Precondition
Customer visit CP and ask for recharge.
Business Trigger

Process Details 1) This process detail out the steps where CP performs recharge on self or on
customer mobile number.
2) CP may have EVD or AM or both wallets associated to his service number.
3) CP can perform the recharge using either EVD or AM depending upon the
available balance in respective wallets.
4) System should allow CP to take mobile number for recharge.
5) Upon entering the customer MSISDN, system will show the segmented offers
first and bundles before actual recharge transfer:
a. System will check with respect to segmented offers:
i. If customer has any segmented & non-segmented offer going to
expire in less than 10 days (configurable number of days). Show
segment offer.
ii. If customer has any segmented & non-segmented offer going to
expire in greater than 10 days (configurable number of days). Do
not show the segmented offer.
iii. If customer does not have any segmented offer or bundle offer.
Show available segmented offers for the customer.
iv. System should allow CP to select segmented offer for customer
or dismiss the popup.
v. System should also show the applicable commission given to CP
for each segmented offers.
6) In case, customer does not agree for any segmented offers. CP can dismiss the
popup of segmented offers and proceed to next step.
7) On the next step, system should check with respect to bundle offers:
a. Show available bundle offers in various categories (voice, data, roaming,
combo etc.)

Confidential Page 6
 b. If customer is agreeing for bundle offers – Refer section number 1.4.3
(step number 7 onwards).
8) In case, customer does not agree for any bundle offers. CP will enter the
preferred recharge amount and proceed.
9) Depending upon the applicability of the EVD or AM wallet, system should show
the available balance of wallets and allow CP to choose anyone to recharge.
10) If any of the wallet does not have sufficient balance for requested amount,
system should not allow recharge from that particular wallet or allow CP to
change the preferred recharge amount.
11) System should ask for the PIN to complete the transaction based on the selected
wallet.
a. In case, CP enters the wrong PIN for three / five times. PIN will be
blocked.
b. Refer section 1.8.2 or 1.8.5 for unblocking the PIN.
12) Upon successful recharge, update CP and customer main bucket balance.
13) System should show the commission earned by the CP for recharge transaction
(if any).

Post Condition Upon recharge, update customer and CP main bucket balance.
System will show CP to dismiss the page (so that he can go to main screen) or
otherwise do another recharge.

1.4.2 Recharge Sales Reversal

1.4.2.1 Process Flow

2. Recharge Sales Reversal - Process Flow

1.4.2.2 Process Summary

Brief Description Describe the process of recharge reversal.

CP initiated recharge transaction and now wants to reverse that transaction.
Precondition
CP identified wrong recharge transaction.
Business Trigger

Process Details 1) This process detail out the steps where CP performs recharge reversal on self-
numbers.
2) This process is only applicable for transactions performed by CP on his registered
number only.
3) Following are few scenarios where CP can initiate reversal:
a. Entered wrong recharge amount
4) Reversal can be full or partial.
5) System should have a provision against the recharge transactions to perform
reversal.

Confidential Page 7
 6) System should allow CP to perform reversal (partial or full). CP can initiate
multiple partial reversal (as long as full amount is not yet covered).
a. In case of partial, system should ask CP to enter reversal amount. By
default, system should populate the applicable reversal amount.
i. E.g., Transaction amount was 100, CP has already reversed 50
then at the time of new reversal request, and system should
populate only 50.
b. Reversal amount should be less or equal to transaction amount.
c. System should ask for the PIN to complete the transaction depending
upon the source of recharge (EVD or AM).
i. In case, CP enters the wrong PIN for five times. PIN will be
blocked.
ii. Refer section 1.8.2 or 1.8.5 for unblocking the PIN.
7) Upon submission, system should initiate USSD push notification to mapped
mobile beneficiary number of the transaction for confirmation. Following are the
possible scenarios from customer response perspective:
a. Confirm:
i. Sufficient Balance: CP will get the amount back.
ii. Insufficient Balance: Partial amount will be reversed (whatever
available in customer main bucket balance).
b. No Response – System will wait for USSD session time out before
marking, it “Cancelled”.
8) In the middle of any reversal on a given transaction Id, system should not allow
any other reversal transaction until it is closed. In case of no response from
customer (USSD confirmation) then system should auto close the transaction
after a configurable time.
9) System should indicate following for transaction against which reversal initiated:
a. Transaction ID, Reversal Amount (asked and provided), SR Date & Time,
SR Status.
10) Once full reversal done, system should not allow any further reversal transaction.
11) Recharge reversal is applicable either the recharge was done through EVD or AM.
12) System should allow reversal of last 7 days transactions only.

Post Condition Upon customer response (Y), reversal should be successful or on customer response
(N), reversal should not take place.

1.4.3 Bundles Sale Reversal

1.4.3.1 Process Flow

3. Bundles Sale Reversal - Process Flow

1.4.3.2 Process Summary

Brief Description Describe the process of bundle sales reversal.

Confidential Page 8
 CP initiated bundle sales transaction and now wants to reverse that transaction.
Precondition
CP identified wrong bundle sales transaction.
Business Trigger

Process Details 1) This process detail out the steps where CP performs bundle sales reversal on self-
numbers.
2) There will be not partial reversal for bundle sales.
3) This process is only applicable for transactions performed by CP on his registered
number only.
4) System should have a provision against the recharge transactions to perform
reversal.
5) System should allow CP to perform reversal (full).
a. System should ask for the PIN to complete the transaction depending
upon the source of recharge (EVD or AM).
i. In case, CP enters the wrong PIN for five times. PIN will be
blocked.
ii. Refer section 1.8.2 or 1.8.5 for unblocking the PIN.
6) Upon submission, system should initiate USSD push notification to mapped
beneficiary mobile number of the transaction for confirmation. Following are the
possible scenarios from customer response perspective:
a. Confirm:
i. Unused Bundle: CP will get the amount back.
ii. Partially used bundle: no amount will be reversed
b. No Response – System will wait for USSD session time out before
marking, it “Cancelled”.
7) In the middle of any reversal on a given transaction Id, system should not allow
any other reversal transaction until it is closed. In case of no response from
customer (USSD confirmation) then system should auto close the transaction
after a configurable time.
8) System should indicate following for transaction against which reversal initiated:
a. Transaction ID, Reversal Amount (asked and provided), SR Date & Time,
SR Status.
9) Once full reversal done, system should not allow any further reversal transaction.
10) Recharge reversal is applicable either the recharge was done through EVD or AM.
11) System should allow reversal of last 7 days transactions only.

Post Condition Upon customer response (Y), reversal should be successful or on customer response
(N), reversal should not take place.

1.4.4 Bundles Sale

1.4.4.1 Process Flow

4. Bundles Sale - Process Flow

Confidential Page 9
1.4.4.2 Process Summary

Brief Description Describe the process of performing bundles sale on customer mobile.
CP must have enough balance either in his EVD or AM wallet for bundles sale.
Precondition
Customer visit CP and ask for bundles.
Business Trigger

Process Details 1) System should allow CP having recharge selling profile to perform sale of bundles
on customer mobile numbers.
2) CP may have EVD or AM or both wallets associated to his service number.
3) CP can sell bundles using either EVD or AM depending upon the available balance
in respective wallets.
4) System should allow CP to take mobile number for bundles sale.
5) Upon entering the MSISDN, system should show any segmented offers available
for the customer.
6) In case, customer does not agree for any segmented offers. CP can bypass
(dismiss the popup) of segmented offers and proceed to next step.
7) On the next step, system should show all the applicable bundles available on the
given mobile number.
8) For each bundles, system should show daily, weekly, monthly packs.
9) For each bundles, system should show available on-net min, off net min, SMS,
Data & pricing.
10) System should allow CP to select the preferred bundle.
11) Depending upon the applicability of the EVD or AM wallet, system should show
the available balance of wallets and allow CP to choose anyone for bundles sale.
12) If any of the wallet does not have sufficient balance for requested bundle, system
should not allow sales from that particular wallet or allow CP to change the
preferred bundle.
13) System should ask for the PIN to complete the transaction.
a. In case, CP enters the wrong PIN for five times. PIN will be blocked.
b. Refer section 1.8.2 or 1.8.5 for unblocking the PIN.
14) Upon successful transaction, update CP balance.
15) Upon successful transaction, provision bundle on customer mobile number.
16) System should show the commission earned by the CP for bundles sale
transaction (if any).

Post Condition In case of successful transaction, provision bundle on customer mobile and update
CP’s balance. Otherwise, CP should get error message.

Confidential Page 10
1.5 My Stock - GSM

1.5.1 Check EVD Balance

1.5.1.1 Process Flow

5. Check EVD Balance - Process Flow

1.5.1.2 Process Summary

Brief Description Describe the process of checking EVD balance of CP MSISDN.

CP performed any transaction. CP wants to check the updated balance.
Precondition
CP performed any transaction. CP wants to check the updated balance.
Business Trigger

Process Details 1) This process detail out the steps where CP can check his latest EVD balance.
2) This process is only applicable when the CP is having EVD wallet.
3) System should allow CP to check his EVD balance.
4) System should not ask PIN to check his EVD balance.

Post Condition System should show the current EVD balance.

1.5.2 Stock Request - EVD

1.5.2.1 Process Flow

6. EVD Stock Request - Process Flow

1.5.2.2 Process Summary

Brief Description Describe the process of raising EVD stock request to parent.
CP should exist on Pretups and running out of EVD balance.
Precondition
CP running out of EVD balance.
Business Trigger

Process Details 1) System should allow CP having EVD wallet to raise the request for EVD.
2) System should allow CP to enter the preferred EVD amount and proceed.
3) System should ask for the PIN to complete the transaction.
a. In case, CP enters the wrong PIN for five times. PIN will be blocked.
b. Refer section 1.8.2 for unblocking the PIN.
4) Upon successful submission of the request, system should send the SMS
notification to parent with following details:
a. Sender MSISDN

Confidential Page 11
 b. Requested EVD Amount
5) Actual EVD transfer will be the offline process.

Post Condition Upon submission, send SMS notification to parent for EVD fulfillment.

1.5.3 Send EVD to Retailer using AM

1.5.3.1 Process Flow

7. Send EVD to Retailer Using AM - Process Flow

1.5.3.2 Process Summary

Brief Description Describe the process of performing AM based EVD sales to retailer.
CP must have enough balance in his AM wallet to EVD sales to retailer.
Precondition
Retailer ask for EVD load.
Business Trigger

Process Details 1) System should allow CP having “AM Agent” profile to EVD sales to retailer.
2) System should allow CP to take retailer’s EVD mobile number for EVD sales.
3) Based on the retailer MSISDN, system should populate the retailer name and
validate whether the retailer exist in EVD platform or not.
a. If retailer exists in the EVD platform, process will continue.
b. If retailer does exist in the EVD platform, process will stop here.
4) System should allow CP to enter preferred EVD sales amount proceed.
5) System should show the available balance of AM agent’s wallet.
6) If wallet does not have sufficient balance for requested amount, system should
not allow EVD sales or allow CP to change the EVD amount.
7) System should ask for the PIN to complete the transaction.
a. In case, CP enters the wrong PIN for five times. PIN will be blocked.
b. Refer section 1.8.5 for unblocking the PIN.
8) Upon entering the PIN, system will perform following checks:
a. Sender has sufficient balance or not.
9) Upon successful EVD sell transaction, update CP’s AM wallet balance and
retailer’s EVD balance.
10) AM agent upon successful EVD sell, will see commission earned as well (if any).

Post Condition Upon EVD sales, update CP’s AM wallet balance and retailer’s EVD balance.

Confidential Page 12
1.5.4 Buy EVD – Own Account using AM & Other Payment Option

1.5.4.1 Process Flow

8. Buy EVD for Self Using AM - Process Flow

1.5.4.2 Process Summary

Brief Description Describe the process of buying EVD using AM for self.
CP must have enough balance in his AM wallet to EVD sales for self.
Precondition
CP needs EVD load.
Business Trigger

Process Details 1) System will allow EVD retailer to buy EVD using AM/ debit/ credit card etc.
2) System should allow CP to enter preferred EVD sales amount proceed.
3) Retailer will select the mode of payment.
4) If he selects AM, System should show the available balance of AM agent’s wallet.
5) If wallet does not have sufficient balance for requested amount, system should
not allow EVD sales or allow CP to change the EVD amount.
6) System should ask for the PIN to complete the transaction.
a. In case, CP enters the wrong PIN for five times. PIN will be blocked.
b. Refer section 1.8.5 for unblocking the PIN.
7) Upon entering the PIN, system will perform following checks:
a. Sender has sufficient balance or not.
8) If he selects debit/ credit card/ others, then he will be routed to payment
gateway page for payment processing.
9) Upon successful AM/ other payments, update CP’s AM wallet balance and EVD
balance, as applicable.

Post Condition Retailer EVD balance to be updated as per purchase value

1.6 AM Sales & Services

1.6.1 Cash In

1.6.1.1 Process Flow

9. AM Cash In - Process Flow

1.6.1.2 Process Summary

Brief Description Describe the process of performing cash-in on customer wallet.

CP must have enough balance in his AM wallet to perform cash-in on customer
Precondition
wallet.

Confidential Page 13
 Customer visit CP and ask for cash-in.
Business Trigger

Process Details 1) System should allow CP having “AM Agent” profile to perform cash-in on
customer wallet.
2) Cash-In: It increases the customer wallet balance and decreases agent wallet.
Debit will happen from Agent wallet and credit will happen to customer wallet.
3) This process detail out the steps where the cash-in initiated by CP.
4) System should allow CP to take customer mobile number and preferred cash-in
amount.
5) System should show the available balance of AM agent’s wallet.
6) If wallet does not have sufficient balance for requested amount, system should
not allow cash-in or allow CP to change the preferred cash-in amount.
7) System should ask for the PIN to complete the transaction.
a. In case, CP enters the wrong PIN for five times. PIN will be blocked.
b. Refer section 1.8.5 for unblocking the PIN.
8) Upon entering the PIN, system will perform following checks:
a. Sender has sufficient balance or not.
b. Receiver’s wallet balance limit, if exceeds then reject.
c. Checks receiver’s (daily cap, weekly CAP, monthly cap). Transaction
Count & Transaction Amount.
9) Upon successful cash-in, update CP and customer wallet balance.
10) System should show the commission earned by the CP for cash-in transaction (if
any).

Post Condition Upon cash-in, update customer and CP wallet balance.

1.6.2 Cash Out – CP Initiated

1.6.2.1 Process Flow

10. AM Cash Out – CP Initiated - Process Flow

1.6.2.2 Process Summary

Brief Description Describe the process of performing cash-out from customer wallet by CP.
Customer must have enough balance in his wallet to perform cash-out by CP.
Precondition
Customer visit CP and ask for cash-out.
Business Trigger

Process Details 1) Cash out can happen in 3 ways:

a. Customer initiated (with agent code)
b. Customer initiated w/o agent code
c. Agent initiated
2) System should allow CP having “AM Agent” profile to perform cash-out from

Confidential Page 14
 customer wallet.
3) Cash-Out: It decreases the customer wallet balance & increases the agent wallet.
Debit will happen from customer wallet and credit will happen to agent wallet.
4) This process detail out the steps where the cash-out initiated by CP.
5) System should allow CP to take customer mobile number and cash-out amount.
6) Based on the customer MSISDN, system should populate the customer Name. (In
order to verify the customer).
7) Upon submission, system should initiate USSD push on customer mobile number
for confirmation. Following are the possible scenarios from customer response
perspective:
a. Confirm – If customer confirm by entering his MPIN.
i. System will check the subscriber wallet balance, if enough cash
then allow cash-out.
ii. System will check the (daily cap, weekly CAP, monthly cap) of the
subscriber. Transaction Count & Transaction Amount. Once
success then allow cash-out.
iii. System will get the cash-out confirmation.
iv. Upon successful cash-out, update CP and customer wallet
balance.
v. CP will get cash-out notification via SMS and system should
update the transaction status.
vi. CP gives cash to customer.
b. No Response – System will wait for configurable time. Before marking, it
“Cancelled”.
8) In the middle of any cash-out transaction on customer mobile number, system
should not allow any other cash-out transaction until it is closed.

Post Condition Upon cash-out, update customer and CP wallet balance.

1.6.3 Cash Out – Customer Initiated Using Agent Code

1.6.3.1 Process Flow

11. AM Cash Out With Using Agent Code – Customer Initiated - Process Flow

1.6.3.2 Process Summary

Brief Description Describe the process of performing cash-out from customer wallet by Customer.
Customer must have enough balance in his wallet to perform cash-out by customer.
Precondition
1) Customer will initiate the request from USSD or self-care app, entering following
details:
a. Agent Code (CP)
b. Amount
c. PIN

Confidential Page 15
 2) Upon submission of the cash-out request. System will perform following checks:
a. System will check the subscriber wallet balance, if enough cash then
allow cash-out.
b. System will check the (daily cap, weekly CAP, monthly cap) for the AM
agent. Transaction Count & Transaction Amount. Once success then
allow cash-out.
c. System will get the cash-out confirmation.
d. Upon successful cash-out, update CP and customer wallet balance.
Customer visit CP and ask for cash-out.
Business Trigger

Process Details 1) System should allow customer to initiate cash-out using recipient agent’s code.
2) Cash-Out: It decreases the customer wallet balance & increases the agent wallet.
Debit will happen from customer wallet and credit will happen to agent wallet.
3) This process detail out the steps where the cash-out initiated by customer using
agent’s code.
4) CP will get cash-out notification via SMS & app notification.
5) CP gives cash to customer.

Post Condition Upon cash-out, update customer and CP wallet balance.

1.6.4 Cash Out – Customer Initiated Without Agent Code

1.6.4.1 Process Flow

12. AM Cash Out Without Using Agent Code – Customer Initiated - Process Flow

1.6.4.2 Process Summary

Brief Description Describe the process of performing cash-out from customer wallet by Customer.
Customer must have enough balance in his wallet to perform cash-out by Customer.
Precondition
1) Customer will initiate the request from USSD or self-care app, entering following
details:
a. Agent Code (CP)
b. Amount
2) Upon submission of the cash-out request. System will perform following checks:
a. System will check the subscriber wallet balance, if enough cash then
allow cash-out.
b. System will check the (daily cap, weekly CAP, monthly cap). Transaction
Count & Transaction Amount. Once success then allow cash-out.
c. Upon successful cash-out, system will generate a unique voucher code
and update customer wallet balance. System should block the money in
customer wallet.

Confidential Page 16
 Customer visit CP and ask for cash – out.
Business Trigger

Process Details 1) System should allow customer to initiate cash-out without knowing the recipient
agent code.
2) Cash-Out: It decreases the customer wallet balance & increases the agent wallet.
Debit will happen from customer wallet and credit will happen to agent wallet.
3) This process detail out the steps where the cash-out initiated by customer
without using agent’s code.
4) Customer will visit any CP and share this unique voucher code for cash-out.
5) System should allow agent to enter the cash-out voucher code. System will
perform following checks:
a. Voucher Code Valid:
i. If the voucher code is valid (not yet expired) or not yet used,
system should increase the CP wallet balance.
ii. CP gives cash to customer.
iii. Once voucher is used, system should not allow using it again.
b. Voucher Code Invalid / Used:
i. System should return appropriate error message.

Post Condition Upon cash-out, update customer and CP wallet balance.

1.6.5 AM Transaction Reversal

1.6.5.1 Process Flow

13. AM Transaction Reversal - Process Flow

1.6.5.2 Process Summary

Brief Description Describe the process of reversal of AM transactions.

CP initiated any AM transaction and now wants to reverse that transaction.
Precondition
CP identified wrong transaction.
Business Trigger

Process Details 1) System should allow CP having “AM Agent” profile to perform transaction
reversal.
2) This process is only applicable for transactions performed by CP.
3) Following are the type of transactions whose reversal can be initiated:
a. Individual:
i. Cash In
ii. Cash Out
iii. Recharge
iv. Cash Transfer (agent to agent)
v. EVD Sale
b. Billers:

Confidential Page 17
 i. Merchant Payments
4) Following are few scenarios where CP can initiate reversal:
a. Entered wrong customer mobile number
b. Entered wrong transaction amount
5) Reversal can be full or partial.
6) System should have a provision against the transactions to perform reversal.
7) System should allow CP to perform reversal (partial or full). CP can initiate
multiple partial reversal (as long as full amount is not yet covered).
a. In case of partial, system should ask CP to enter reversal amount. By
default, system should populate the applicable reversal amount.
i. E.g., Transaction amount was 100, CP has already reversed 50
then at the time of new reversal request, and system should
populate only 50.
b. Reversal amount should be less or equal to transaction amount.
c. System should ask for the PIN to complete the transaction.
i. In case, CP enters the wrong PIN for five times. PIN will be
blocked.
ii. Refer section 1.8.5 for unblocking the PIN.
d. In case, reversal is for biller transactions (merchant payments). System
should raise SR for manual closure.
i. SR need to be resolved at the backend. System should show
resolution time and SR no to retailer.
8) Upon submission, system should initiate USSD push notification to mapped
mobile number of the transaction for confirmation. Following are the possible
scenarios from customer response perspective:
a. Confirm – If customer confirm by entering his MPIN.
i. Sufficient Balance: CP will get the amount back.
ii. Insufficient Balance: Partial amount will be reversed (whatever
available in customer main bucket balance).
b. No Response – System will wait for configurable time. Before marking, it
“Cancelled”.
9) In the middle of any reversal on a given transaction Id, system should not allow
any other reversal transaction until it is closed. In case of no response from
customer (USSD confirmation) then system should release the transaction after a
configurable time.
10) System should indicate following for transaction against which reversal initiated:
a. Transaction ID, Reversal Amount, SR Date & Time, SR Status.
11) Once full reversal done, system should not allow any further reversal transaction.
12) System should allow reversal of last 7 days transactions only.

Post Condition Upon customer response (Y), reversal should be successful or on customer response
(N), reversal should not take place.

Confidential Page 18
1.6.6 Agent Float Deposit – Parent to Child

1.6.6.1 Process Flow

14. Agent Float Deposit – Parent To Child - Process Flow

1.6.6.2 Process Summary

Brief Description Describe the process of pushing AM to AM agents by parent to child.

Parent must have enough balance in his AM wallet to transfer to his AM agents.
Precondition
Parent wants to push AM to AM agents.
Business Trigger

Process Details 1) System should allow CP having access right to push AM to AM agent’s wallet.
2) Push AM: It increases the AM agent’s wallet and decreases parent’s wallet. Debit
will happen from parent’s wallet and credit will happen to AM agent wallet.
3) Push AM - Parent
a. Parent should be able to push AM from either Retailer App or USSD.
b. Retailer App:
i. System should allow parent to push AM to his hierarchy or
outside the hierarchy.
ii. System should allow parent to enter AM agent mobile number.
iii. Upon entering the mobile number, system should the available
balance. (This is only applicable in case receiver is part of
sender’s hierarchy).
iv. System should allow parent to enter preferred push amount.
v. If wallet does not have sufficient balance for requested amount,
system should not allow transfer or allow parent to change the
amount.
vi. System should ask for the PIN to complete the transaction.
1. In case, CP enters the wrong PIN for five times. PIN will
be blocked.
2. Refer section 1.8.5 for unblocking the PIN.
vii. Upon entering the PIN, system will perform following checks:
1. Sender has sufficient balance or not.
2. Receiver’s wallet balance limit, if exceeds then reject.
3. Checks receiver’s (daily cap, weekly CAP, monthly cap).
Transaction Count & Transaction Amount.
viii. Upon successful push AM, system should block the money in
parent’s wallet and notify AM agent to accept the float.
c. USSD:
i. Follow as-is process of pushing AM to agents.
4) Accept Push AM - Child
a. Retailer App:
i. System should show pending push float transactions which are

Confidential Page 19
 yet to be accepted by AM Agent.
ii. System should allow AM agent to accept the float. Agent has to
enter the PIN to accept.
iii. Upon successful acceptance, system should update the balance
of both sender and receiver.
iv. System should notify both upon successful acceptance.

Post Condition Agent should be notified for push float for acceptance; upon successful acceptance,
balance of both the parties should be updated.

1.6.7 Agent Float Deposit – Child to Parent

1.6.7.1 Process Flow

15. Agent Float Deposit – Child To Parent - Process Flow

1.6.7.2 Process Summary

Brief Description Describe the process of pushing AM balance to parent by child.

AM agents must have enough balance in his AM wallet to transfer to his parent.
Precondition
AM agents wants to push AM to Parent.
Business Trigger

Process Details 1) System should allow CP having “AM Agent” profile to push AM to parent wallet.
2) Push AM: It decreases the AM agent’s wallet and increases parent’s wallet. Debit
will happen from AM agent’s wallet and credit will happen to parent’s wallet.
3) Push AM - Child
a. Retailer App:
i. System should allow AM agent to push AM to his parent.
ii. System should allow AM agent to enter parent’s mobile number.
iii. Upon entering the mobile number, system should validate
whether the given number is parent number or not.
1. If parent exists in the AM platform, process will continue.
2. If parent does exist in the AM platform, process will stop
here.
iv. System should allow AM agent to enter preferred push amount.
v. If wallet does not have sufficient balance for requested amount,
system should not allow transfer or allow agent to change the
amount.
vi. System should ask for the PIN to complete the transaction.
1. In case, CP enters the wrong PIN for five times. PIN will
be blocked.
2. Refer section 1.8.5 for unblocking the PIN.
vii. Upon entering the PIN, system will perform following checks:

Confidential Page 20
 1. Sender has sufficient balance or not.
2. Receiver’s wallet balance limit, if exceeds then reject.
3. Checks receiver’s (daily cap, weekly CAP, monthly cap).
Transaction Count & Transaction Amount.
viii. Upon successful push AM, system should block the money in AM
agent’s wallet and notify parent to accept the float.
4) Accept Push AM - Parent
a. Parent should be able to accept push AM from either Retailer App or
USSD.
b. Retailer App:
i. System should show pending push float transactions which are
yet to be accepted by parent.
ii. System should allow parent to accept the float. Parent has to
enter the PIN to accept.
iii. Upon successful acceptance, system should update the balance
of both sender and receiver.
iv. System should notify both upon successful acceptance.
c. USSD:
i. Follow as-is process of accepting push AM from agents.

Post Condition Parent should be notified for push float for acceptance; upon successful acceptance,
balance of both the parties should be updated.

1.6.8 Agent Float Withdraw

1.6.8.1 Process Flow

16. Agent Float Withdrawal - Process Flow

1.6.8.2 Process Summary

Brief Description Describe the process of withdrawing balance from AM agent’s wallet.
AM agents has balance and parent wants to withdraw.
Precondition
Parent wants to pull AM from AM agents.
Business Trigger

Process Details 1) System should allow CP having access rights to withdraw balance from AM
agent’s wallet.
2) Pull AM: It increases the parent wallet and decreases AM agent’s wallet. Debit
will happen from AM agent’s wallet and credit will happen to parent’s wallet.
3) Pull AM - Parent
a. Parent should be able to withdraw balance from either Retailer App or
USSD.

Confidential Page 21
 b. Retailer App:
i. System should allow parent to withdraw balance from his
hierarchy or outside the hierarchy.
ii. System should allow parent to enter AM agent mobile number.
iii. Upon entering the mobile number, system should the available
balance. (This is only applicable in case receiver is part of
sender’s hierarchy).
iv. System should allow parent to pull full or partial amount.
v. System should not allow parent to enter the amount greater
than the AM agent’s available balance.
vi. System should ask for the PIN to complete the transaction.
1. In case, CP enters the wrong PIN for five times. PIN will
be blocked.
2. Refer section 1.8.5 for unblocking the PIN.
vii. Upon entering the PIN, system will perform following checks:
1. Sender has sufficient balance or not.
2. Receiver’s wallet balance limit, if exceeds then reject.
3. Checks receiver’s (daily cap, weekly CAP, monthly cap).
Transaction Count & Transaction Amount.
viii. Upon successful pull AM, system should block the money in AM
agent’s wallet and notify AM agent to accept the pull float
request.
c. USSD:
i. Follow as-is process of withdrawing balance from agents.
4) Accept Pull AM - Child
a. System should show pending pull float transactions which are yet to be
accepted by AM Agent.
b. System should allow AM agent to accept the pull float request. Agent has
to enter the PIN to accept.
c. Upon successful acceptance, system should update the balance of both
sender and receiver.
d. System should notify both upon successful acceptance.

Post Condition Agent should be notified for pull float for acceptance; upon successful acceptance,
balance of both the parties should be updated.

1.7 My Stock - AM

1.7.1 Check AM Wallet Balance

1.7.1.1 Process Flow

17. Check AM Wallet Balance - Process Flow

Confidential Page 22
1.7.1.2 Process Summary

Brief Description Describe the process of checking AM balance of CP MSISDN.

CP performed any transaction. CP wants to check the updated balance.
Precondition
CP performed any transaction. CP wants to check the updated balance.
Business Trigger

Process Details 1) System should allow CP to check his AM balance.

2) System should show the current AM balance of all the associated wallets to
MSISDN.
3) There can be multiple wallets associated to one MSISDN.

Post Condition System should show the current AM balance of all associated wallets.

1.7.2 Stock Request - AM

1.7.2.1 Process Flow

18. AM Stock Request - Process Flow

1.7.2.2 Process Summary

Brief Description Describe the process of raising AM stock request to parent.

CP should exist on AM platform and running out of AM balance.
Precondition
CP running out of AM balance.
Business Trigger

Process Details 1) System should allow CP having AM wallet to raise the request for AM load.
2) System should allow CP to enter the preferred AM load amount and proceed.
3) System should ask for the PIN to complete the transaction.
a. In case, CP enters the wrong PIN for five times. PIN will be blocked.
b. Refer section 1.8.5 for unblocking the PIN.
4) Upon successful submission of the request, system should send the SMS
notification to parent with following details:
a. Sender MSISDN
b. Requested AM Amount
5) Actual AM transfer will be the offline process.

Post Condition Upon submission, send SMS notification to parent for AM fulfillment.

Confidential Page 23
1.7.3 Agent to Agent Float Transfer

1.7.3.1 Process Flow

19. Agent to Agent Float Transfer - Process Flow

1.7.3.2 Process Summary

Brief Description Describe the process of performing agent-to-agent AM transfer.

CP must have enough balance in his AM wallet to perform transfer to another agent.
Precondition
Customer visit CP and ask for cash-in.
Business Trigger

Process Details 1) System should allow CP having access right to perform agent-to-agent AM
transfer.
2) Agent-to-Agent Transfer: It increases the receiver’s wallet balance and decreases
sender’s wallet. Debit will happen from sender’s wallet and credit will happen to
receiver’s wallet.
3) System should allow CP to take agent’s mobile number and preferred transfer
amount.
4) System should show the available balance of sender’s wallet.
5) If wallet does not have sufficient balance for requested amount, system should
not allow transfer or allow CP to change the transfer amount.
6) System should ask for the PIN to complete the transaction.
a. In case, CP enters the wrong PIN for five times. PIN will be blocked.
b. Refer section 1.8.5 for unblocking the PIN.
7) Upon entering the PIN, system will perform following checks:
a. Sender has sufficient balance or not.
b. Receiver’s wallet balance limit, if exceeds then reject.
c. Checks receiver’s (daily cap, weekly CAP, monthly cap). Transaction
Count & Transaction Amount.
8) Upon successful transfer, update CP and receiver’s wallet balance.
9) System should show the commission earned by the CP for agent-to-agent
transfer transaction (if any).

Post Condition Upon agent-to-agent transfer, update sender and receiver wallet balance.

1.8 Support Function

1.8.1 Change EVD PIN

1.8.1.1 Process Flow

20. Change EVD PIN - Process Flow

Confidential Page 24
1.8.1.2 Process Summary

Brief Description Describe the process of changing the EVD PIN.

CP must have his current PIN and wants to change the PIN.
Precondition
Due to regular PIN expiry or CP wants to change PIN in between.
Business Trigger

Process Details 1) System should allow CP to change his EVD PIN.

2) PIN – It is a four digit (numeric) value used to complete the EVD transaction.
3) System should allow CP to enter following information in order to change the
PIN:
a. Old PIN
b. New PIN
c. Re Enter New PIN
4) Upon entering the above details. Following are the possible scenarios:
a. Success – In case, PIN changes successfully in Pretups, System should
show confirmation message “PIN Changed Successfully”.
b. Failure – In case, of any failure, system should show the failure reason.
5) Retail App should not save the CP’s PIN in any circumstances.

Post Condition In case of success, EVD PIN should change otherwise system should give error
message.

1.8.2 Unblock EVD PIN

1.8.2.1 Process Flow

21. Unblock EVD PIN - Process Flow

1.8.2.2 Process Summary

Brief Description EVD PIN reset has to be done by the operator today. This can be automated for the
retailer app by using retailer choosing to answer select personal questions.

Precondition 1) In “My Profile” section, agent has chosen to set standard answers to the pre-
defined questions.
PIN is locked and retailer wants to unlock it.
Business Trigger

Process Details 1) If retailer’s PIN is locked due to 3 wrong attempts then he can select to answer 2
questions to get it answered correctly, he will get option to reset his PIN by
entering the PIN twice.
2) If he cannot answer correctly then Airtel admin will help him unlock.

Post Condition Retailer EVD PIN will be reset.

Confidential Page 25
1.8.3 Change AM PIN

1.8.3.1 Process Flow

22. Change AM PIN - Process Flow

1.8.3.2 Process Summary

Brief Description Describe the process of changing the AM PIN.

CP must have his current PIN and wants to change the PIN.
Precondition
Due to regular PIN expiry or CP wants to change PIN in between.
Business Trigger

Process Details 1) System should allow CP to change his AM PIN.

2) PIN – It is a four digit (numeric) value used to complete the AM transaction.
3) Change PIN is required when CP knows his current PIN and wants to change it.
4) System should allow CP to enter following information in order to change the
PIN:
a. Old PIN
b. New PIN
c. Re Enter New PIN
5) Upon entering the above details. Following are the possible scenarios:
a. Success – In case, PIN changes successfully in AM, System should show
confirmation message “PIN Changed Successfully”.
b. Failure – In case, of any failure, system should show the failure reason.
6) Retail App should not save the CP’s PIN in any circumstances.

Post Condition In case of success, AM PIN should change otherwise system should give error
message.

1.8.4 Reset AM PIN

1.8.4.1 Process Flow

23. Change AM PIN - Process Flow

1.8.4.2 Process Summary

Brief Description Describe the process of resetting the AM PIN.

CP forgets his current PIN and wants to reset.
Precondition
CP does not able to use his current PIN.
Business Trigger

Confidential Page 26
 Process Details 1) System should allow CP to reset his AM PIN.
2) PIN – It is a four digit (numeric) value used to complete the AM transaction.
3) Reset is required when CP does not remember his current PIN.
4) System should allow CP to enter following information in order to reset the PIN:
a. Select secret word
b. Enter secret word
5) Upon entering the above details. Following are the possible scenarios:
a. Success – In case, answer matches then system will allow setting up new
PIN:
i. System will ask PIN & ask to confirm pin as well
ii. If does not match then ask to enter again.
b. Failure – In case, answer does not match, system should show the failure
reason.

Post Condition In case of success, AM PIN should reset otherwise system should give error message.

1.8.5 Unblock AM PIN

1.8.5.1 Process Flow

24. Unblock AM PIN - Process Flow

1.8.5.2 Process Summary

Brief Description AM account unlock has to be done by the operator today. This can be automated for
the retailer app by using retailer choosing to answer select personal questions.

Precondition In “My Profile” section, agent has chosen to set standard answers to the pre-defined
questions.
PIN is locked and retailer wants to unlock it.
Business Trigger

Process Details 1) If retailer’s PIN is locked due to 3 wrong attempts then he can select to answer 2
questions to get it answered correctly, he will get option to reset his PIN by
entering the PIN twice.
2) If he cannot answer correctly then Airtel admin will help him unlock.

Post Condition Retailer AM PIN will be reset.

1.9 My Account

1.9.1 Password Reset

1.9.1.1 Process Flow

25. Non Airtel Employee Password Reset - Process Flow

Confidential Page 27
1.9.1.2 Process Summary

Brief Description Describe the process of resetting the password for non – Airtel users.
CP exist in system. CP not able to login in system because of incorrect password.
Precondition
CP forgot his password.
Business Trigger

Process Details 1) System should allow non – Airtel users to reset their password.
2) Non – Airtel users login with their registered mobile number.
3) In order to reset the password, user has to provide following information
associated with their registered mobile number:
a. DOB
b. ID Number
4) Upon entering the above details. Following are the possible scenarios:
a. Success:
i. System will send the OTP on the registered mobile number.
ii. User should be able to reset the password using the OTP.
iii. User should be able to login into system with new password.
b. Failure:
i. Use can try again giving the above details or contact retailer
helpdesk / system admin.

Post Condition In case of success, non – Airtel user should get OTP and should be able to reset the
password.

1.10 Service Request

1.10.1 Service Request

1.10.1.1 Process Flow

26. Raise Service Request - Process Flow

1.10.1.2 Process Summary

Brief Description Describe the process of raising the service request for any commission payout issue.
CP identified the issue in commission payout. CP seeks help from Airtel on
Precondition
commission payout.
CP identified the issue in commission payout.
Business Trigger

Process Details 1) System should allow CP to view the commission payout report. CP should be able
to raise service request in case of any dispute of commission payout.
2) System should have a provision against the commission payment reference to

Confidential Page 28
 raise service request.
3) System should allow CP to enter the problem statement against the selected
payment reference number.
4) Upon submission, system should generate the service request number for further
tracking.
5) In case any open, SR against the payment reference number, system should not
allow any other SR creation.
6) System should indicate following for transaction against which service request
initiated:
a. Transaction ID, SR Date & Time, SR Status.

Post Condition Upon submission, SR should be created for the given commission payout reference
number.

1.11 Report

1.11.1 Retail App

1.11.1.1 My Activity

Objective of this report is to view his activities on the App. CP can view his activities on daily, weekly,
monthly or based on any date range.
Daily – Current Day
Weekly – Current Day + Last 6 Days
Monthly – Current Day + 29 Days
Date Range – Difference between start date and end date should not be greater than 30 days.
CP can also search based on the activity type (Recharge, Cash-In, Cash-Out, Bundles, Segmented Offer, Agent
Float, and EVD Sales), transaction status & transaction number.

Transaction Transaction Transaction Transaction Commission Initiate

Transaction
Number Date & MSISDN Status Earned Reversal
Type Amount
Time

1.11.1.2 Commission Earned Report

Objective of this report is to view his commission earrings on the App. CP can view his commission earnings
on daily, weekly, monthly, LMTD, MTD, or based on any date range.
Daily – Current Day
Weekly – Current Day + Last 6 Days
Monthly – Current Day + 29 Days

Confidential Page 29
Date Range – Difference between start date and end date should not be greater than 30 days.
LMTD VS MTD – Last Month to Date (today is 8 July 2020), and then report should populate the data from 1 st
of the previous month to 8 th of the previous month VS. Data from 1 st of the current month to 8th of the
current month.
MTD – Month to Date (today is 8 th July 2020), then report should populate the data from 1 st of the month to
8th of the month.
CP can also search based on the activity type (Recharge, Cash-In, Cash-Out, Bundles, Segmented Offer, Agent
Float, and EVD Sales), transaction status & transaction number.

Transaction Type Total Transaction Count Successful Transaction Count Commission to be Paid

GA - KYC

GA - FRC

GA - AM first CI

CI

CO

EVD sales

Bundles

Segmented offer
Sales

Total transaction number will be a hyperlink and by clicking on it, system should show individual transactions
in below format.

Transaction M Transaction Commission Commissio

Number S Status Earned n Rejection
Transaction
Transaction I Transaction Reason
Date &
Type S Amount
Time
D
N

1.11.1.3 Commission Payout Report

Objective of this report is to view his commission payouts on the App. CP can view his commission payouts
on daily, weekly, monthly, LMTD, MTD, 3 Months, or based on any date range.
Daily – Current Day
Weekly – Current Day + Last 6 Days

Confidential Page 30
Monthly – Current Day + 29 Days
3 Months – Monthly View of 3 months
Date Range – Difference between start date and end date should not be greater than 90 days.
LMTD VS MTD – Last Month to Date (today is 8 July 2020), and then report should populate the data from 1 st
of the previous month to 8 th of the previous month VS. Data from 1 st of the current month to 8th of the
current month.
MTD – Month to Date (today is 8 th July 2020), then report should populate the data from 1 st of the month to
8th of the month.
CP can also search based on the activity type (Recharge, Cash-In, Cash-Out, Bundles, Segmented Offer, Agent
Float, and EVD Sales), transaction status & transaction number.

Transaction Type Total Transaction Count Successful Transaction Count Commission Payout

GA - KYC

GA - FRC

GA - AM first CI

CI

CO

EVD sales

Bundles

Segmented offer
Sales

Total transaction number will be a hyperlink and by clicking on it, system should show individual transactions
in below format.

Transaction M Transaction Co Commission Claw

Number S Status mm Payout Back
Transaction
Transaction I Transaction issi
Date &
Type S Amount on
Time
D Ear
N ned

1.11.1.4 My Service Request

Objective of this report is to view his SR on the App. CP can view his all Service Request on daily, weekly,
monthly or based on any date range.

Confidential Page 31
Following are the service request considered here:
 Stock Request (EVD, AM)
 Payment Issue
 AM Transaction Reversal
 Recharge Reversal
 Bundle Sales Reversal
 Agent Float Deposit – Child to Parent
 EVD Purchase - Self
Daily – Current Day
Weekly – Current Day + Last 6 Days
Monthly – Current Day + 29 Days
Date Range – Difference between start date and end date should not be greater than 6 months.
CP can also search based on the SR Number, SR Type & SR Status.

SR Number SR Type SR Creation Date & Time SR Status Remarks

1.12 Appendix

1.12.1 Future Scope

Sr No Requirement Phase

1.

1.12.2 Open Point

Sr No Point Resolution Status

1. Can one service number have both EVD and AM Yes Open
profile?

2. Will EVD PIN blocked after giving 3 or 4 times 3 times Open

wrong.

3. Will AM PIN blocked after giving 3 or 4 times After 5 times Open

wrong.

Confidential Page 32
3. Assumptions and Tradeoffs
 In case of dual SIM device, Retail app can be configured only on one mobile number.
 System will not generate sales receipt for any sales transaction.
 CP should be able to see all his activities regardless of the channel used to perform activity e.g. CP
can cash-in using the USSD or retailer App. However, retailer app should have the visibility of all the
transactions.

Confidential Page 33
4. Dependencies
 KYC
 AM

*** end of document ***

Confidential Page 34