Functional

Specification
Document
Middleware
For HDFC Bank Credit Card

1 | Page

P. T . O .

July 12

2014

Revision History
Name

Date

Reason For Changes

Version

Mukesh Singh

12/07/2014

First draft

1.0

Mukesh Singh

24/07/2014

Second draft

1.1

Mukesh Singh

31/07/2014

Third draft

1.2

HDFC

14/08/2014

HDFC Review comments (BPRG team)

1.2

Mukesh Singh

22/08/2014

Third draft as 22/08/2014 FTL

Comments

1.3

2 | Page

P. T . O .

Contents
No

Topic

Page

Introduction

Data Transfer (Master Import)

5-6

Master Download

Allocation Upload

Re-Allocation

Pick up

10

HHT and SIM Stock In

11

Agency Import

12

Collection Executive Enrollment

13-15

10

Tele Caller Enrollment

16

11

HHT Transfer Process

17-18

12

HHT Allocation and Re-Allocation

19-20

13

HHT Surrender

21-22

14

HHT Repair

23

15

HHT Re-Stock

24-25

16

HHT Confirmation

26-27

17

Master Locking

28-29

18

Modify Business Rules

30-31

19

Lost HHT

32-33

20

User Registration

34

21

Middleware User Password

35

3 | Page

P. T . O .

22

Lock and unlock User

36

23

Map User to Agency

37

23

Permissions

38

24

Report and CSV Format

39

25

Payment Authorization

40-41

1. Introduction
1.1 Purpose
This document elaborates the software requirements for a web based middle-ware
application designed for HDFC Bank. All feature requirement, flow diagrams etc.
are covered here.
Contents detailed explicitly in this document only will be considered as final scope for software
delivery.

The release version for this software would be 1.0

1.2 Intended Audience
This document is intended for software developers, project managers and users.
1.3 Project Scope
The middle-ware would to be used as an interface to enable seamless
communication between HDFC banks Vision+ Collection module & the HHT.
It would reside on a server and can be accessed from a browser.
1.4 References
DLRD shared on 01/07/14
Meeting on 07/07/2014
F2F Meeting on 31/07/2014

4 | Page

P. T . O .

2. Data Transfer (Master Import)

1. At the beginning of the month the entire allocation data would be pushed
from Collections system to Mobility System middleware. Thereafter,
incremental data will be pushed on a daily basis.
2. Online data transfer using the web-service of mobility solution for triggering
of pick up cases especially for Inflows
3. CC Number to be masked in collection terminals, reports, screens and in
database as per PCIDSS standards. Phase II
4. Data exchange between CC Web Collections & MW should comply with
PCIDSS standards. Phase II
BPRG Comments : Pls specify data purging period and frequency, data types
of master import and incremental transfer for reallocations. PCIDSS needs to
be taken up in Phase 1. The card number should be masked in reports and
HHT

22/08/2014 FTL Comments:

HDFC CC Asst_v_1
6.xls

It was cleared FTL does not have to do any special certification of PCI DSS.
Above embedded document is the high level HDFC ISG checklist. Section
A-B-C were all delivered as part of HDFC Retail Asset Phase-1 delivery,
with some items accepted by HDFC IT team as exceptions. These exceptions
will continue to remain same for HDFC Credit Card delivery. Section D
specifically covers PCI-DSS related items, against which our comments are
added.
Section D issues if any raised by HDFC ISG team, will be taken up for
investigating resolving when it is shared. Earliest detection of these issues
5 | Page

P. T . O .

would not be possible as special tools to test all sections A-B-C-D are not
available with us.

Description:
This is a windows scheduler which runs once daily & fetches master data from
HDFCs Vision+ web collection module. At the beginning of the month old data
(previous month) will be purge from mobility system and entire allocation data
would be pushed from Collections system to Mobility System middleware.
Thereafter, incremental data will be pushed on a daily basis.
Web service for pick up case is a complex requirement, we recommend to put this
in phase 2 (IT/Vendor comments (07/07/2014))
CC Number masking: HHT and Report will have Masking Data for display.
Masking pattern will be First 6 and last 4 digit number of CC number are unmask,
rest all number will be mask and will be shown as x. Phase II
PCI DSS standards: We understand that V+ & CC web collections are not PCI
compliant still in such case data in this system will come in clear text. Please
highlight specifically what all details we need to encrypt / mask. (IT/Vendor
comments (07/07/2014)) Phase II

References:
Schema mentioned in Mobility Table. The 2 tables are Allocation details, Trail
History

6 | Page

P. T . O .

Process:

7 | Page

P. T . O .

3. Master Download
Description:
Agency Supervisor may view and download master data.
Process:
8 | Page

P. T . O .

4. Allocation Upload
Description:
Allocation can be done in bulk and Single format. A CSV file containing a
collection executives allocation would be uploaded. Interface will be provided for
9 | Page

P. T . O .

Single allocation. Agency supervisor can also view and download current
allocations.
BPRG Comments : The upload happens in excel and download in csv. The single
allocation interface should have option to enter Collection Id against each
collection.
22/08/2014 FTL Comments: Ok

Accessed By: Agency Supervisor

Masters: Allocation, Trail: Allocation History
Process:

5. Re-Allocation
Description:

10 | P a g e

P. T . O .

This is a web-based page using which only allocated cases can be re-allocated to
another collection Executive. Drop-down/auto-suggest to have collection executive
ID. Any allocated data cant be re- allocated more than 2 times. Phase I
BPRG Comments : The reallocations to be pushed to HHT immediately using web
service.Allocation count of the selected executive should be shown.
Referral has been parked for Phase 2
22/08/2014 FTL Comments: Reallocations will be available on HHT when HHT initiates the
sync feature with middleware. It would not be possible to push reallocations from
middleware to HHT.

Accessed By: Agency Supervisor

Masters: Allocation, Trail: Allocation History
Wireframe:

6. Pick up Phase I
Description:
11 | P a g e

P. T . O .

This is a web-based page using which allocated and unallocated cases can be
closed by Tele-Callers raise as Pick up case and Executive can also closed
Allocated Payment data as a pick up case. Pick up case will be assign to all
Reporting CLMs.
Bank User (CLM) will assign these cases to other or same agency as a Pick up
case. Agency Supervisor will able to assign pick up cases to Non DRA User only.
Accessed By: Agency Supervisor, CLM

7. HHT & SIM Stock In

Description:
12 | P a g e

P. T . O .

This interface allows a bank admin to take new HHTs or SIM cards into stock by
filling up a web form or uploading a CSV file.
Accessed By: Bank Admin
Masters: HHT Master, SIM Master - Trail: HHT History
Process:

8. Agency Import
Description:
13 | P a g e

P. T . O .

This interface allows a bank admin to take bulk uploading agency through CSV
file and web form to be fill at the time of single Agency creation
Accessed By: System
Masters: Agency Master
Process:

Bank
Admin
upload
agency
sheet
Re-enter
data

Agenc
y
Uniqu
e?

Agency
Created

9. Collection Executive Enrollment (DRA and Non DRA Phase I)

14 | P a g e

P. T . O .

Description:
An enrollment form will be filled up by an Agency supervisor where a machine
will be assigned to both type of collection Executive. Enrollment would be
approved by Agency Owner and Collection Manager. Collection Executive will be
segregated by Tier logic and DRA ID Number (DRA Id number will not be
mandatory for Non DRA executive). There will be four type of tier available i.e.
Tier 1,2,3,4. Wallet limit will be considered on the bases of Tier level. All alerts
would be sent using SMS and EMAIL.
Non DRA Executive an only Collect the pickup cases where as DRA can collect
Payment trail and follow up cases.
BPRG Comments : Only staff with DRA ID can be termed as Field executives.
DRA executives will get permanent allocation and non DRA will get temporary
allocation(pickups) which should be readily viewable by bank users for surprise
audits and checks, After filling the form a unique reference no is to be generated
for the agent id by the system, the ID created is the agent id of the agency staff. A
HHT can be assigned to a user only if ID card is issued to him, Rights for
executive creation should be with bank only, There should be a duplication check
on Employee id and email address of the executives. The SIM No and Machine no
should be entered while registration and only the registered employee should be
able to login into that HHT. There should be a age check and candidates above 18
yrs are eligible. After the executive is enrolled the agency manager has to review
and authorize the details. Upon authorization the details should flow to the central
support team who will inturn do relevant checks like CIBIL AND Dedupe. All
good cases are approved in system to which ID card to be generated. All existing
ID card number have to be uploaded in the mobility system and upon renewal the
new template id number shall be used for the same.

22/08/2014 FTL Comments: HHT will be assigned to DRA and Non DRA executive.

Accessed By: Agency Supervisor, Agency Owner, Collection Manager

Master: Collection Executive, Trail: Collection Executive Enrollment Log

15 | P a g e

P. T . O .

Process:

16 | P a g e

P. T . O .

17 | P a g e

P. T . O .

18 | P a g e

P. T . O .

10. Tele Caller Enrollment Phase I

Description:
An enrollment form will be filled up by an Agency supervisor for Tele Caller User.
Enrollment would be approved by Collection Manager. All alerts would be sent
using SMS and EMAIL.
Tele Caller User will have login in Middleware. They will close any call from
unallocated or Allocated Data.
BPRG Comments : They can also upload trails and assign pickups.
22/08/2014 FTL Comments: Telecaller will do only upload trails. Assigning pickup case to
agent will be done by Agency Supervisor.

Accessed By: Agency Supervisor, Agency Owner, Collection Manager

Master: Collection Executive and Tele Caller, Trail: Collection Executive
Enrollment Log/ Tele caller creation log
Process:

Agency
Supervisor
Login

Input
Detail
Form

Email
Sent to
CLM for
Approval

Rejectio
n Email
notificati
on sent
to AS

Rejected

19 | P a g e

Decisi
on

P. T . O .

Approved

Email
notificati
on sent
to Tele
Caller

11. HHT Transfer Process

Description:
An HHT transfer could be part of an enrollment or be directly initiated by a Bank
Admin.
Accessed By: Agency Owner, Bank Admin
Master: HHT Transfer, HHT Master, Trail: HHT History
Process:

20 | P a g e

P. T . O .

21 | P a g e

P. T . O .

12. HHT Allocation/Re-Allocation

Description:
This module allows an Agency Supervisor to Allocate / Re-Allocate HHTs to
Collection Executives
Accessed By: Agency Supervisor
Master: Collection Executive, HHT Master Trail: HHT History
Process:

22 | P a g e

P. T . O .

23 | P a g e

P. T . O .

13. HHT Surrender

Description:
This module allows a Collection Executive to surrender a machine to an agency
supervisor.
Accessed By: Agency Supervisor
Master: Collection Executive, HHT Master Trail: HHT History
Process:

24 | P a g e

P. T . O .

25 | P a g e

P. T . O .

BPRG Comments : Pls include option for HHT surrender in case of Employee
leave. In case of HHT not working the HHT Serial No should be disabled for
allocation.
22/08/2014 FTL Comments: Ok

14. HHT Repair

Description:
This module allows an Agency Supervisor to hand over a faulty machine to the
service support team & keep track of the same.
Accessed By: Agency Supervisor Master: HHT Master Trail: HHT History
Process:

26 | P a g e

P. T . O .

27 | P a g e

P. T . O .

15. HHT Re-Stock

Description:
This module allows an Agency Supervisor to receive a rectified HHT back from
the vendors service support team & take it back into stock.
Accessed By: Agency Supervisor
Master: HHT Master Trail: HHT History
Process:

28 | P a g e

P. T . O .

29 | P a g e

P. T . O .

16. HHT Confirmation

Description:
This module allows an Agency Supervisor to confirm that he has physically seen
the machine & confirms its presence. Un-confirmed machines would be locked.
Accessed By: Agency Supervisor
Master: HHT Master Trail: HHT Confirmation
Process:

30 | P a g e

P. T . O .

31 | P a g e

P. T . O .

17. Master Locking

Description:
This module allows a Bank Admin to lock any Collection Executive on field.
BPRG Comments : There are two cases. Auto lock and manual lock.
Cases when User Id should get auto - locked
The due date and wallet limit shall be applied at HHT level only.
User id will get locked in case of wrong password being entered for more
than 5 times consecutively.
User Id shall get locked if due date of 3 days have crossed for unauthorized
collections.
The user id shall get locked if wallet limit has crossed.
When a user is terminated the HHT shall get locked.
When terminals battery is less than 15% no transactions should be allowed.
Cases when User Id should get manually locked

The HHT machine is lost

The HHT machine is stolen
The collection executive is absconding
A fraud has been committed
Other (Remark field is mandatory in this case)

For manually locking and unlocking a screen should be provided to bank user. This
will involve a maker checker process allowed only to bank admin users. On
successful Lock / Unlock appropriate message should be displayed.
Following field values should be displayed on the Lock Machine Screen on
selecting the agency and executive code.

Agency
Executive Code
Executive Name
Executive Mobile No
Machine Sr No

32 | P a g e

P. T . O .

 Wallet Limit
Wallet Balance
Pending Receipt Date
Reason for locking
Remark
Following field values should be displayed on the Unlock Machine Screen.
Agency
Executive Code
Executive Name
Executive Mobile No
Machine Sr No
Wallet Limit
Wallet Balance
Pending Receipt Date
Remark
22/08/2014 FTL Comments: Ok

Accessed By: Bank Admin

Master: HHT Master Trail: HHT History, Locking/Unlocking Logs
Process:

33 | P a g e

P. T . O .

34 | P a g e

P. T . O .

18. Modify Business Rules

Description:
This module allows changing wallet limits & due days.
BPRG Comments : Bank user authorization is required for creation and
modification.
22/08/2014 FTL Comments: Ok

Accessed By: Agency Supervisor, Collection Manager and Tele Caller

Master & Trail: Modification of Business Rules
Process:

35 | P a g e

P. T . O .

36 | P a g e

P. T . O .

19. Lost HHT

Description:
This module allows an agency owner to declare a HHT as lost.
Accessed By: Agency Owner, Bank Admin
Master: HHT Master Trail: HHT History, Lost Machines
Process:

37 | P a g e

P. T . O .

38 | P a g e

P. T . O .

20. User Registration Phase I

Description:
This module allows a Bank admin or UAM User to register new users on the
middle-ware. An excel upload feature would be provided to upload multiple users
and web form will be provide to fill data for individual user creation. A registered
user can have only one active login session at a time. This would be applicable
across browsers as well.
BPRG Comments : This involves a maker checker process.
22/08/2014 FTL Comments: Ok

List of User can be register by Bank admin on Middleware.

i.
ii.
iii.
iv.
v.
vi.
vii.

Bank Admin/ UAM

NCM
RCM
ACM
CLM
Agency Owner
Agency Supervisor

List of User can be register by Agency on Middleware.

i. Tell Caller
ii. DRA Executive
iii. Non DRA Executive

Accessed By: Agency Owner, Bank Admin, UAM User

Masters: User Login, Registration Trail: User Registration Trail, Login Trail: Login
History

39 | P a g e

P. T . O .

Wireframe:

40 | P a g e

P. T . O .

21. Middleware User Password:

Description:
First time User will be forced to change his Password at login.
Change Password feature will be provided to user.
User will be forced to change his password at specified interval.
User new password will be validated with his last 10 Password.
Password Policy:
i. Password length will be minimum 8 characters.
ii. Password should have at least one Capital Alphabet and 1
numeric character.
iii. Space is not allowed rest all special character can include.
iv. 3 time incorrect password will lock the User.

41 | P a g e

P. T . O .

22. Lock & Unlock User:

Description:
This module allows Admin to lock and unlock the User. Web page will be provided
to admin from where admin can lock or unlock the users.
Accessed By: Bank Admin

23. Map User to Agency

Description:
This module allows a Bank admin or UAM user to map users to one or multiple
agencies. Their reports would be filtered accordingly.
Accessed By: Bank Admin, UAM User
Masters and Trail: Map user to branch
Wireframe:

42 | P a g e

P. T . O .

24. Permissions
Description:
This module allows a Bank admin and UAM to set permissions for a Role and
User.
Accessed By: Bank Admin
Masters: UAM page on the masters document.

43 | P a g e

P. T . O .

Wireframe:

25. Report and CSV Format

Description:

44 | P a g e

P. T . O .

ALL reports and CSV will be same as Retail Collection. Only fields in all type of
transactions related report and CSV will be different. Detail list will be provided by
BPRG. Rest all reports will have same fields as in Retail Collection.
At initial date range for all reports will be 15 days. If server performance get
reduce then, we have to reduce date range. i.e. 7 days.
All report will be filter on the bases of Transaction date field.
New type of report will be providing in Phase II.
List of Reports:

Agency master report

SIM master report
HHT master report
HHT transfer report
Middleware user master report
Middleware user roles report (UAM report for access rights)
Locked Middleware user report
Master allocation report Summary & detailed
Re-allocation log/report
Transaction/payments reports (agency wise/collector wise) date filter to be
basis Collection date
Unauthorized payments report
Transaction cancellation report
Number of reprints report
Batch not closed (EOD not done) reports
Trail logs
Wallet limit & due days limit change logs
Location report (Location tracked for each payment done in HHT.
Zero collections done for a day report (HHT wise)

26. Payment Authorization & Recon (Phase II)

Description:

45 | P a g e

P. T . O .

Using this module, an Agency Supervisor marks a transaction has authorized after
receiving payment from the Collection Executive.
Reject option will be provide in authorization module. So Agency Supervisor can
Authorize or Reject any transaction.
Daily scheduler will run at midnight and authorize all transactions which are
pending for more than 1 day.
Recon and Shopping format will be parked for Phase II also needs clarification on
it.
Accessed By: Agency Supervisor
Masters: Transaction. Updates the DepositDate, Deposited By, PostDate &
PostedBy fields.
Process:

46 | P a g e

P. T . O .

47 | P a g e

P. T . O .